Adding dependencies

hey @cloneable thanks for sharing this!
I've been using it for a while, now I wanted to use the Ent approach described here to have a Proto object store/retreived from the DB easily.
To do that, I need to import my proto generated type into my schema file, but entc doesn't seem to see my dependency at all:
entc generation failed, entc/load: parse schema dir: /redacted/schema/myschema.go:8:6: could not import github.com/my/repo/proto/myproto (invalid package name: "")

I've tried to change the rule but I'm a total beginner at writing Bazel rules so I haven't managed, do you have an idea how this could be supported?

I keep hearing good things about Rust :)
The proto is created manually, it's built like this:
proto_library(
    name = "myproto_proto",
    srcs = ["myproto.proto"],
    deps = [
    ],
)

go_proto_library(
    name = "myproto_go_proto",
    importpath = "github.com/my/repo/proto/myproto",
    proto = ":myproto_proto",
    deps = [
    ],
)

But when I import myproto_go_proto in my schema file the Ent generate breaks with the message above.
I tried to debug by listing the path, and it doesn't seem like any of the dependencies are available to entc

Then what you have to do is add myproto_go_proto to deps of the go_ent_library, but I did not plan for further dependencies and go_ent_library doesn't accept deps. This needs to be changed.
Your proto lib needs to make it into this list of deps:
https://github.com/cloneable/rules_ent/blob/7f43ad514f61eb71b64c92181497ddc68af159b4/defs.bzl#L220-L223
... via parameter of the go_ent_library macro:
go_ent_library(
  ...
  deps = [
    ":myproto_go_proto",
  ],
)

I have tried that :/, but it still isn't available to https://github.com/cloneable/rules_ent/blob/7f43ad514f61eb71b64c92181497ddc68af159b4/defs.bzl#L62

Would you happen to have a simplified example project that I can clone and test with? I can't seem to find my old project at the moment. (Probably only on backup after I switched machines last year.)

I've added a PR with an example that reproduces it

Thanks for the example! I took a first look and, yes, you're right the deps are not available to the run_shell action. ctx.attr.schema[GoSource].deps needs to be added to the GOPATH of the generate tool. I'm thinking about how to do that. Maybe recursively list the source files of all deps and copy or symlink them.

I think that's what this rule is for: https://github.com/bazelbuild/rules_go/blob/master/docs/go/core/rules.md#go_path but I didn't manage to get it working!

Nice find! See latest commit in main: https://github.com/cloneable/rules_ent/commit/304143694a222255bd983fa6ecd8d3b2e73bad2d
Worked for me locally. Let me know if this works for you, too. Fyi, the previous commit also updates the dependencies.

I rebased and updated the PR, but I wasn't able to build locally still :/ don't you get the same error with
❯ bazel build //...
INFO: Analyzed 16 targets (182 packages loaded, 11170 targets configured).
INFO: Found 16 targets...
ERROR: /Users/dmateusp/code/rules_ent/example/schema/BUILD.bazel:18:15: Generating Ent files in bazel-out/darwin-fastbuild/bin/example/schema failed: (Exit 1): bash failed: error executing command (from target //example/schema:db_generate) /bin/bash -c ... (remaining 6 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
2023/05/01 17:14:46 entc failed: entc/load: parse schema dir: /private/var/tmp/_bazel_dmateusp/bcd25fcbe2b4fbce9df1fa3134e8a311/sandbox/darwin-sandbox/125/execroot/com_github_cloneable_rules_ent/example/schema/user.go:7:2: could not import github.com/cloneable/rules_ent/example/protos (invalid package name: "")

?

Sorry, while trying out a few things yesterday I noticed that this happens with any transitive dependency and I replaced the proto lib with a regular Go package for faster testing. I did not revert that to test this, but now I know what's wrong: Because the .pb.go file is generated it's not listed like a regular source file in the tree, but under the target dir that produced it: ./bazel-out/darwin_arm64-fastbuild/bin/example/protos/user_settings_go_proto_/github.com/cloneable/rules_ent/example/protos/user_settings.pb.go Makes sense. I can tell go_path to simply zip all needed files. Unzipping that gives me a usable package layout. However, I'd like to try to do this without creating an archive. I will report back soon.

@cloneable could you push the version that works with the zip step maybe? (even if it's on a branch)
I'd be interested in using that patch in the meantime


B-Tree File Project [C++]

Hello
This PR <-> #100  : Too add a new desktop application using C++
The project description in README File
I hope this be useful for beginners
Thanks

Thanks


make numpad enter key work in swaylock

This should fix issue #647.
Also a couple minor, unrelated wording and comment changes.

Thanks!


Feature Request: Section on debugging Kivy apps, esp. kvlang portions, in the Prog. Guide

Hi!  I'd like to suggest/request that a section on methods for debugging Kivy apps, especially those portions that rely on kvlang files, be added to the "Programming Guide."  Example topics: strategic places to put breakpoints; which Python attributes of Kivy objects to "worry" about (i.e., examine the values of); etc.  (Suggestions from people with experience (trying to) debug Kivy apps encouraged.)  Thanks!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8469236-feature-request-section-on-debugging-kivy-apps-esp-kvlang-portions-in-the-prog-guide?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

I second this. I write all my code by hand, because kvlang scares me to the bones after a few bad experiences. It's easier to debug code that you write than to try to understand what magic goes behind the scenes of kv builder.
Can someone add the label important? Because all the questions we have on kivy IRC, are most of the time, kv lang questions. How to do this or that in kv lang... like everyday almost.

This seems to be a duplicate of https://github.com/kivy/kivy/issues/3018
@victor-rene. Please add your suggestions to ticket 3018, but in more concrete form. What exactly do you want if these sections? What is lacking? "How to do this or that" is very vague. What is "this or that'?


[Enhancement] : Tic Tac Toe

Is your feature request related to a problem? Please describe.

In this project Tic-Tac-Toe-game Ui was very poor..

Describe the solution you'd like

I will changed to the perfect User interface Ui design in this game.

Describe alternatives you've considered

Actually in this game not perfect in the Desktop and the mobile site also.

Expected behaviour & UI
Screencast from 2024-05-26 13-38-39.webm
Actual Behaviour & UI
Screencast from 2024-06-07 08-54-16.webm

@Sulagna-Dutta-Roy this is can be totally changed ui then how to level1 this is level2 issue.

Any existing enhancements should be level1 because people will work on CSS only. Not the entire change. @sivaprasath2004


Compute normals.

At the moment, normals are hand-prepared. Think of a way to compute them in runtime.

Done with 017ecfa59500291b9499c4b6c720624c70d2209f.
As a proof of concept, I'm now calculating surface-normal vectors for every vertex forming the polygon's surface. Took a step back, reduced the number of vertices to just 3 to distil the problem, and I now have a working solution which simply needs to be extrapolated across all remaining cube's certices.
I also decided to stop using my rogue "asLines" representation and (top square, bottom square and side lines) as it wasn't suitable for reusable calculation of normals. I plan to cling to triangles (even for the "asLines" representation) to make the calculations more maintainable.


Fix ProfilerOptions() documentation

Fixed a bad link.
Issue #689:
The hyperlink in the below sentence in the Profiler options section of the Data Profiler documentation needs to link to better documentation for more in-depth options documentation.

rebase


Integrate MatrixBenchmarking/analyze into TOPSAIL components

/test rhoai-light kserve

looks good enough. Merging.
Linked with https://issues.redhat.com/browse/PSAP-1504


Toggle CFG_RELEASE_CHANNEL between nightly and stable on Windows, Linux, and Mac CI

Trying to see if I can toggle the CFG_RELEASE_CHANNEL in CI to test some code that is only reachable when CFG_RELEASE_CHANNEL is not set to nightly

It's hitting me now that a downside of the in-test check and bail process we have makes it a bit tricky to know if the test passed after hitting all assertions, or whether it speciously bailed early :thinking:
What would you think about temporarily updating one of the impacted tests so that it'll hit an assertion which we force to fail on stable, just to triple check this? Assuming that shows the expected failed job, we can flip back and move forward, and then perhaps in a followup try to find a different way of conditionally skipping tests dynamically

Perfect, thanks! Feel free to revert the change and commit history, will merge afterwards


S3 BucketPolicy not able to put multiple StringEquals conditions

What happened?
While creating s3.aws.crossplane.io/v1alpha2 BucketPolicy conditions for StringEquals. Seem I can only put 1 key-value pair. As for certain scenario, multi key-value pairs are needed
How can we reproduce it?
Sample manifest:
apiVersion: s3.aws.crossplane.io/v1alpha2
kind: BucketPolicy
metadata:
  name: mybucketname.bucketpolicy
spec:
  forProvider:
    version: "2012-10-17"
    bucketName: mybucketname
    region: us-west-1
    statements:
      - sid: DownloadandUpload
        action:
          - "s3:GetObject"
          - "s3:GetObjectAcl"
          - "s3:GetObjectVersion"
          - "s3:PutObject"
          - "s3:PutObjectAcl"
          - "s3:DeleteObject"
          - "s3:DeleteObjectVersion"
        effect: Allow
        principal:
          allowAnon: true
        resource:
          - "mybucketname"
          - "mybucketname/*"
        condition:
          StringEquals:
            - key: "aws:Key1"
              stringValue: "value1"
            - key: "aws:Key2"
              stringValue: "value2"
            - key: "aws:Key3"
              stringValue: "value3"
            - key: "aws:Key4"
              stringValue: "value4"
  providerConfigRef:
    name: aws-provider
  deletionPolicy: Delete

What environment did it happen in?
Crossplane version: v0.14.0
Provider-aws version: v0.15.0

Some example provided in this link as well for multiple conditions value:
https://aws.amazon.com/blogs/security/working-backward-from-iam-policies-and-principal-tags-to-standardized-names-and-tags-for-your-aws-resources/

@kelvinwijaya I went over the code but saw nothing much suspicious immediately. Could you post the error you're seeing in the status?
@krishchow what would you think about having a spec.forProvider.rawPolicy field that can accept the full JSON untouched and as expected by the AWS CLI? In edge cases like this one or when people already had their policies in that format, they can just use that field. If it's given, controller would directly use that JSON without any serialization.

@muvaf I'll work on a PR that allow users to accept a JSON input similar to the CLI.

Hi @muvaf , yes actually no issue with the current code. it is just not able to include list as part of the condition objects, currently is limited to few data types only
@krishchow . thank you for ur help on the PR

Hi @krishchow
I have some concern regarding putting condition as JSON input
Does that mean i cannot leverage on the mapping feature anymore? As I have use-case that need the fields to be directly mapped or using transform function
Example:
- fromFieldPath: "metadata.labels.mylabel"
- toFieldPath: "spec.forProvider.statements[0].condition.StringEquals.stringValue"

Hi @krishchow
Sorry that i think the use-cases become bigger now.
It seem the condition stringequal or stringnotequals values can be of array type as well. Based on the current design, i don't think we can put duplicate the key with different values to overcome this
For example:
{
    'Effect': 'Deny',
    'Principal': '*',
    'Action': 's3:PutObject',
    "Condition": {
        "StringNotEquals": {
            "s3:x-amz-server-side-encryption": ["AES256", "aws:kms"]}}


feat: Support new Windows Terminal

An upcoming feature of the Windows Terminal preview is that it has full emoji support:

In this PR, the code now checks for the WT_SESSION variable which determines if the current environment is in the Windows Terminal.
A few other concerns:
The full check has been continuously getting out of sync with https://github.com/sindresorhus/log-symbols/blob/master/index.js#L4 so we should probably make a lego brick for this one. I'll make it if you want.
The variable name windows is now slightly misleading since now it only targets unsupported terminals so we should probably rename it to legacy.
cc @sindresorhus

See https://github.com/sindresorhus/figures/pull/27#issuecomment-504764201

Closing this for now until https://github.com/microsoft/terminal/issues/1040 is resolved.


made Pool an interface (pool)

As it stands having Mutex.nodes as a  struct array ([]*redis.Pool) limits the use of this library as it can't be adapted to our more specific pools.

Hi Javier,
Thanks for creating this pull request.
I might be missing something here, but does reducing the Pool type's visibility help here? I think it kind of makes the NewMutexWithPool func unusable from other packages.
https://github.com/golang/go/wiki/InterfaceSlice
So []*redis.Pool will not satisfy that argument's type, since it expects an array of a particular interface. Unless it is possible to construct an array of redsync.Pool from other packages, there won't be much use for NewMutexWithPool func.
It may be a good idea to create a separate func for this as others may already be relying on the current ones and I do not want to abruptly break compatibility for them.
Best regards,
Ridwan

Hi Ridwan,
Just noticed what your point, reverted my visibility changes. Also will commit in a minute a different NewMutexWithPool that maintains backwards compatibility.

@JavierZunzunegui Thank you!


PTR Record

Hi All,
i can't able to create PTR record on dnsmasq config, there are some options or it' not possibile to do that?
Thank you!
Alberto

Currently not supported but feel free to add this feature to the add-on :)


Refactor code to unite BabyBear and KoalaBear under a single struct.

Pull all constants and methods needed to define Abstract Field into a new crate.
Step 1 of code refactoring to reduce duplicate code between BabyBear and KoalaBear.

Note this is very much a work in progress and is not going to be pushed to the Main branch. Currently this is a PR for a branch off the main branch.


Bump runtime version and regenerates the controller with ack-generate v0.3.1

Regenerates the DynamoDB controller with ack-generate v0.3.1
to bring in runtime v0.3.0 improvements and features.
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

/lgtm


Update to new namespaces

Following https://github.com/microsoft/win32metadata/commit/df833c5f4d51659aea57926f0947308a4a9c1fef
I wasn't planning on PR'ing this at all. Well, I took care of the few renames to get the types for HRESULT etc. proper again after using newer bindings... and why not PR those few lines in advance.... turns out that required much more effort than expected, and someone else has probably done the same work already. Here it is anyway, in case it is useful to someone when the next Windows.Win32.winmd is pushed :grimacing:
Note that bindings.rs needs to be regenerated from Windows - I'm currently playing around with this crate on Linux :wink:.

Thanks, I'm not looking forward to this churn... 🤪

No need to maintain this PR - I'll refresh everything when a new winmd is published.

@kennykerr I'm updating this for local purposes, need the new bindings with DXC support :stuck_out_tongue_winking_eye:

Thanks for driving those API additions!

I hope it's still useful though, feel free reopen/cherrypick/force-push once the new winmd is published - I checked Allow edits by maintainers (wasn't checked by default this time) for that reason :)


In DAO detail page, my info model, click address, can not open explorer to display address detail

Description
In DAO detail page, my info model, click address, can not open explorer to display address detail
Steps To Reproduce

Enter a DAO detail page
At my info model, click address

Current Behavior

Can not open explorer to display address detail

Expected Behavior

Should open explorer to display address detail after click address

Environment

Platform: PC
Node: v18.18.0
Browser: Chrome 126.0.6478.56

fixed confirm


Make snapshot work for Apple TV

$ snapshot -d "Apple TV 1080p"
...
+----------------+---------+
|     snapshot results     |
+----------------+---------+
| Device         | en-US   |
+----------------+---------+
| Apple TV 1080p |  💚      |
+----------------+---------+

cc #1683

This looks great on the first look, thanks for this pull request 👍
I added a comment, also the tests need to be updated 👍
  1) Snapshot Snapshot::TestCommandGenerator Valid Configuration fixed derivedDataPath uses the fixed derivedDataPath if given
     Failure/Error: command = Snapshot::TestCommandGenerator.generate(device_type: "Something")
     FastlaneCore::Interface::FastlaneError:
       No device found named 'Something' for version '9.3'
     # /Users/distiller/.fastlane_bundle/ruby/2.3.0/gems/fastlane_core-0.48.3/lib/fastlane_core/ui/interface.rb:139:in `user_error!'
     # /Users/distiller/.fastlane_bundle/ruby/2.3.0/gems/fastlane_core-0.48.3/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
     # ./lib/snapshot/test_command_generator.rb:89:in `destination'
     # ./lib/snapshot/test_command_generator.rb:9:in `generate'
     # ./spec/test_command_generator_spec.rb:46:in `block (5 levels) in <top (required)>'

  2) Snapshot Snapshot::TestCommandGenerator Valid Configuration default options uses the default parameters
     Failure/Error: command = Snapshot::TestCommandGenerator.generate(device_type: "Something")
     FastlaneCore::Interface::FastlaneError:
       No device found named 'Something' for version '9.3'
     # /Users/distiller/.fastlane_bundle/ruby/2.3.0/gems/fastlane_core-0.48.3/lib/fastlane_core/ui/interface.rb:139:in `user_error!'
     # /Users/distiller/.fastlane_bundle/ruby/2.3.0/gems/fastlane_core-0.48.3/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
     # ./lib/snapshot/test_command_generator.rb:89:in `destination'
     # ./lib/snapshot/test_command_generator.rb:9:in `generate'
     # ./spec/test_command_generator_spec.rb:20:in `block (5 levels) in <top (required)>'

TestCommandGenerator.generate(device_type: "Something")

How was this working before?

@KrauseFx tests are green!

Perfect, thanks @tmm1. I added some more comments, in particular I'd love some tests for Apple TV and a sample project, so that we don't break Apple TV support in the future 👍

Added sample project + test, and updated the documentation/comments.

Thanks for updating @tmm1, I'm reviewing the PR right now 👍

This is great, it works with no problems. I'd love to add some error handling when the project is a tvOS project, but snapshot runs on the iOS simulator.
Currently when running
snapshot -s "ExampleTV"

it would automatically fetch the simulators
| devices                    | ["iPhone 4s", "iPhone 5", "iPhone 6", "iPhone 6 Plus", "iPad Air", "iPad Pro"] |

instead of fetching all available tvOS simulators.
Is that something you could add? 👍


Profiler: Add slash if there is none between host and path

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets

Documentation

License
MIT

What's in this PR?
See

Looks like in case target doesn't have leading slash, profiler shows strange URL

that is confusing. isn't that a bug in the getRequestTarget implementation, or the underlying Uri implementation? looking at https://github.com/Nyholm/psr7/blob/f734364e38a876a23be4d906a2a089e1315be18a/src/RequestTrait.php#L27 , i don't see why the leading / would get lost.
i am a bit reluctant to merge this, as i don't understand how it can happen without a (more severe) bug in the underlying request / uri implemenation. (or if it gets lost in the collector / stack, we should fix it there, but i had a look at those classes and don't see them changing the request target, they seem just data container).
also, the trim would mis-edit some weird urls like //path with double slash: https://3v4l.org/BR9Lp

It's when path of URI is without leading slash. RequestTrait snippet you posted adds leading slash only when path is empty. And we use Guzzle btw, that also behaves this way.

also, the trim would mis-edit some weird urls like //path with double slash: 3v4l.org/BR9Lp

I've adjusted code for this now

but how can the path be without leading slash?
ah, or does that happen when the uri is created withPath('no-leading/slash'), for example when the domain is configured as base on the client?

correct


private repo makes git fetch --all require credentials

https://github.com/jayaddison/tweets is private so it makes git prompt for username/password when running git fetch --all with that repo as one of the remotes
ideally the follow-everybody script would exclude private repos

cc @jayaddison

@nikolaydubina your repo also seems to be causing this issue jfyi

hey, I actually deleted my repo.. 🙇🏻♂

yeah i was wondering if we could make a script to automatically remove invalid remotes
their http status goes to 404, eg
> curl -I https://github.com/nikolaydubina/tweets/
HTTP/2 404
server: GitHub.com
date: Mon, 07 Nov 2022 11:18:19 GMT
content-type: text/html; charset=utf-8

Ah, apologies for breaking the jankyverse :whale:
GIT_TERMINAL_PROMPT=0 could be one way to resolve this? (git won't attempt to prompt for credentials in that case)


special characters in bundle tags messes with routing

Hello,
My tags names contain "/" (named after their related feature branch feature/featurename).
As a consequence
https://staticdeploy.mydomain.com/bundles/application/feature/featurename shows me "no data". But bundles are properly uploaded and can be used in any entrypoints I want.
Yet, if I manually url-encode the forward slash by replacing it with %2F, everything is fine and my bundles appeared to be properly listed. So I guess, bundle names should be url-encoded before being inserted into the navigation URL ?

Good catch, thanks, definitely a bug.
Yeah, your solution makes sense, encoding them when generating links and decoding them when extracting them from the url. The same thing should be done for bundle names I suppose, while other resources should be fine since they use ids which do not contain slashes.
I'm not able to fix it right away, but I can review / merge a PR if you want to make one. (In case, the changes should be fairly trivial, just need to encode / decode in the bundle-related pages: BundleNamesList/index.tsx, BundleTagsList/index.tsx,  BundlesByNameTag/index.tsx).


xterm-256color support on Bash console?

The xterm console in Bash seems to only support 16 colors.  Change the terminal settings (TERM, TERMCAP, etc) does not seem to result in greater than 16 color support.  When will 256 color support come to Bash and xterm in the Linux subsystem?  Running Win 10 14393.10.

I second this question.  We are on Windows 10 and 2020 is quickly approaching... why is Window's the only OS which doesn't support more than 16 colors in it's terminal.  Currently on 10.0.14901

They are already working on it.
https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13350690-256-color-support

Yea, I'm going to dupe this to #345 and close it, there's quite a bit more discussion in there.


Port number for issuer

Where a Resource Server has no matching public key for a given token, it SHOULD attempt to obtain the missing public key via the the token iss claim as specified in RFC 8414 section 3. In cases where the Resource Server needs to fetch a public key from a remote Authorization Server it MAY temporarily respond with an HTTP 503 code in order to avoid blocking the incoming authorized request.

As iss claim does not providing the port number, where can it be obtained? Or Authorization Server should always be assigned to port 443.

I thought the iss claim should be a URL like <api_proto>://<hostname>:<port>[/<api_selector>]. (The port may be omitted in which case the protocol specifies the default port, e.g. HTTPS = 443.)
Is that not the case?

https://github.com/AMWA-TV/nmos-authorization/blob/v1.0-dev/docs/4.4. Behaviour - Access Tokens.md#iss

So Authorization Server MUST already be on port 443

Yes if it's omitted (and you're not doing something quirky with a protocol other than HTTPS)!

There are some things that may need fixing however... though the spec link above says "MUST be a uri", the example https://github.com/AMWA-TV/nmos-authorization/blob/v1.0-dev/examples/access_token.json has a hostname only, and the schema https://github.com/AMWA-TV/nmos-authorization/blob/v1.0-dev/APIs/schemas/token_schema.json description has only the looser StringOrURI requirement from RFC 7519 Section 4.1.1.

Can be closed as PR #80 merged during today's meeting


It is hard to distinguish vscode from vs2017 in the task bar

Both the shape and the color of the icon is too close to vs2017.
We are forced to watch them carefully to distinguish one from another.
The wrong-side click always irritates us.
I am a newcomer to vscode, and wondered about such a designed feature exists.
I soon understood that you had experienced a long-time journey and may be exhausted.
https://code.visualstudio.com/blogs/2017/10/24/theicon
https://github.com/Microsoft/vscode/issues/35674
https://github.com/Microsoft/vscode/issues/35746
https://github.com/Microsoft/vscode/issues/42836
I am nervous of duplicating this issue.
However, this is not a problem of taste but that of accessibility.
The blue is OK as long as it is possible to identify it easily.

Thanks for the feedback, we already have #44931 where we are tracking this. Please feel free to upvote that issue, will close this issue as a duplicate.


Unclear exception messages

I think it's better to make this message more clear. If the bin folder or path does not exist this exception will occur.
Input bundle file does not exist

Suggestion:
Output bin path does not exist

https://github.com/cafebazaar/bundle-signer/blob/5f0883c5b519874a89fb94ff5d9e24d23c0ea061/src/main/java/ir/cafebazaar/bundlesigner/BundleSignerTool.java#L313
To make things easier you can create the path based on the passed parameter.

Thanks for the report. The next release will fix this issue.

Missing output Bin file path


Return delete requests for better handling of promises and errors

…rrors

Please note:

When returning, the delete requests wont actually return a value, this is essential for the promises to behave expectedly. This approach can be replaced by adding an await instead, but the return is preferred so it gives the users the ability to chain then/catch to the promises.


refactor(consensus): put expectations near the most relevant call site for SHC tests

This is now possible since we no longer put the Context in an Arc, which forced us to
set expectations before doing that. Setting expectations requires .

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

#2239  👈
#2238
#2237
main

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

Join @matan-starkware and the rest of your teammates on  Graphite


File 'src\main.ts' is missing from the TypeScript compilation.

Command
build
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
16
Description
I am running Node v18.17.1 and Angular 17 which I just downloaded yesterday. I created a new project yesterday, it worked fine, went to bed. Got up, went to go keep working on the project, and got the error below (main.ts is missing).
After a while I gave up, decided to just create new project all over again, so I created a new project. (ng new test) and chose scss and no precompile support. When I go to run the project, I get the error again.
- Building...X [ERROR] File 'src\main.ts' is missing from the TypeScript compilation. [plugin angular-compiler]
  Ensure the file is part of the TypeScript program via the 'files' or 'include' property.

Here is my package.json:
{
  "name": "test",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "watch": "ng build --watch --configuration development",
    "test": "ng test"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^17.0.0",
    "@angular/common": "^17.0.0",
    "@angular/compiler": "^17.0.0",
    "@angular/core": "^17.0.0",
    "@angular/forms": "^17.0.0",
    "@angular/platform-browser": "^17.0.0",
    "@angular/platform-browser-dynamic": "^17.0.0",
    "@angular/router": "^17.0.0",
    "rxjs": "~7.8.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.14.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^17.0.1",
    "@angular/cli": "^17.0.1",
    "@angular/compiler-cli": "^17.0.0",
    "@types/jasmine": "~5.1.0",
    "jasmine-core": "~5.1.0",
    "karma": "~6.4.0",
    "karma-chrome-launcher": "~3.2.0",
    "karma-coverage": "~2.2.0",
    "karma-jasmine": "~5.1.0",
    "karma-jasmine-html-reporter": "~2.1.0",
    "typescript": "~5.2.2"
  }
}

I'm not sure how to fix this?
Minimal Reproduction
This happens upon creation of a new project for me.
ng new test
When asked, select "SCSS" for CSS, and "No" to the question of precompilation features.
When the project is complete, change to the newly created "test" folder and run
ng s --o
Error appears during build.
Exception or Error
- Building...X [ERROR] File 'src\main.ts' is missing from the TypeScript compilation. [plugin angular-compiler]
  Ensure the file is part of the TypeScript program via the 'files' or 'include' property.

Your Environment
Angular CLI: 17.0.1
Node: 18.17.1
Package Manager: npm 10.2.3
OS: win32 x64

Angular: 17.0.3
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.1
@angular-devkit/build-angular   17.0.1
@angular-devkit/core            17.0.1
@angular-devkit/schematics      17.0.1
@angular/cli                    17.0.1
@schematics/angular             17.0.1
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2

Anything else relevant?
This was literally working the evening before. The last thing I did before bed was run the app. I woke up this morning, went to go run it again, and this error appeared.
I would also like to note that I have also tried to uninstall (using npm uninstall, plus I cleared the cache) and reinstall Angular, it made no difference.

Mind sharing the broken project please?

Thanks Alan, please tell me the best way to do that? Should I zip up "test" and send it to you? (Perhaps minus the "node_modules")?

FYI, I updated to the latest LTS of Node.js and NPM as well.
$ npm -v
10.2.3
$ node -v
v20.9.0
Angular CLI: 17.0.0
Node: 20.9.0
Package Manager: npm 10.2.3
OS: win32 x64
Angular: 17.0.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router
Package                         Version
@angular-devkit/architect       0.1700.0
@angular-devkit/build-angular   17.0.0
@angular-devkit/core            17.0.0
@angular-devkit/schematics      17.0.0
@angular/cli                    17.0.0
@angular/ssr                    17.0.0
@schematics/angular             17.0.0
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2
When I create a new project now, I see this at the end...
$ ng n test
? Which stylesheet format would you like to use? SCSS   [
https://sass-lang.com/documentation/syntax#scss                ]
? Do you want to enable Server-Side Rendering (SSR) and Static Site Generation
(SSG/Prerendering)? No
CREATE test/angular.json (2756 bytes)
CREATE test/package.json (1035 bytes)
CREATE test/README.md (1058 bytes)
CREATE test/tsconfig.json (877 bytes)
CREATE test/.editorconfig (274 bytes)
CREATE test/.gitignore (548 bytes)
CREATE test/tsconfig.app.json (263 bytes)
CREATE test/tsconfig.spec.json (273 bytes)
CREATE test/.vscode/extensions.json (130 bytes)
CREATE test/.vscode/launch.json (470 bytes)
CREATE test/.vscode/tasks.json (938 bytes)
CREATE test/src/main.ts (250 bytes)
CREATE test/src/favicon.ico (15086 bytes)
CREATE test/src/index.html (290 bytes)
CREATE test/src/styles.scss (80 bytes)
CREATE test/src/app/app.component.html (20884 bytes)
CREATE test/src/app/app.component.spec.ts (910 bytes)
CREATE test/src/app/app.component.ts (363 bytes)
CREATE test/src/app/app.component.scss (0 bytes)
CREATE test/src/app/app.config.ts (227 bytes)
CREATE test/src/app/app.routes.ts (77 bytes)
CREATE test/src/assets/.gitkeep (0 bytes)
√ Packages installed successfully.
warning: in the working copy of '.editorconfig', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of '.gitignore', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of '.vscode/extensions.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of '.vscode/launch.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of '.vscode/tasks.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'README.md', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'angular.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'package-lock.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'package.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/app/app.component.html', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/app/app.component.spec.ts', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/app/app.component.ts', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/app/app.config.ts', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/app/app.routes.ts', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/index.html', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/main.ts', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/styles.scss', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'tsconfig.app.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'tsconfig.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'tsconfig.spec.json', LF will be replaced by CRLF the next time Git touches it
Successfully initialized git.

test.zip
Here is the project, minus the node_modules

The LF will be replaced by CRLF the next time Git touches it is just a warning that can safely be ignored. Regarding the errors I am unable to replicate using the reproduction provided.
ng s -o

Initial Chunk Files | Names         |  Raw Size
polyfills.js        | polyfills     |  82.71 kB |
main.js             | main          |  23.36 kB |
styles.css          | styles        |  96 bytes |

                    | Initial Total | 106.17 kB

Application bundle generation complete. [10.193 seconds]
Watch mode enabled. Watching for file changes...
  ➜  Local:   http://localhost:4200/

Let me ask you this. It's weird that this is happening, and while I understand your comment about the LF's, I noted it to simply point out that something has "changed". I don't normally get those warninigs, and I didn't get them yesterday when I created the initial project which ran just fine... until this morning, when it STOPPED running fine.
Which leads me to wonder if the problem has nothing to with what's on my PC, and perhaps everything to do with NPM? I know you probably aren't an NPM expert, but it is possible that when NPM goes to grab files for a build, that it is getting corrupt files? Does everyone get their NPM files from the same source, or is possible that someone in Boston is getting their files from a different location than someone in Los Angeles? If so, maybe you can't reproduce it because you aren't getting them from the same source as I am?

Let me ask you this. It's weird that this is happening, and while I understand your comment about the LF's, I noted it to simply point out that something has "changed". I don't normally get those warninigs, and I didn't get them yesterday when I created the initial project which ran just fine... until this morning, when it STOPPED running fine.

The mentioned warnings were always present on windows unless core.autocrlf was set to false. (via git config --global core.autocrlf false).

Which leads me to wonder if the problem has nothing to with what's on my PC, and perhaps everything to do with NPM? I know you probably aren't an NPM expert, but it is possible that when NPM goes to grab files for a build, that it is getting corrupt files? Does everyone get their NPM files from the same source, or is possible that someone in Boston is getting their files from a different location than someone in Los Angeles? If so, maybe you can't reproduce it because you aren't getting them from the same source as I am?

The errors you are setting do not seem to be caused by corrupted NPM packages, to be honest I never encountered  corrupted NPM packages being downloaded from public NPM registry. While not everyone get the NPM package from the same server, there are checks in place for that to ensure that the downloaded package is not corrupted.

Thanks. I'm not sure what else to try then? Here is a link to a video I made of what I'm doing, and what I'm seeing, on my end. Maybe this will help?
https://www.youtube.com/watch?v=Ges2910U_gs

PS C:\temp> ng new test
? Which stylesheet format would you like to use? SCSS   [ https://sass-lang.com/documentation/syntax#scss                ]
? Do you want to enable Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering)?
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in .gitignore.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in .vscode/extensions.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in .vscode/launch.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in .vscode/tasks.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in README.md.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in angular.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in package-lock.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in package.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in src/app/app.component.html.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in src/app/app.component.spec.ts.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in src/app/app.component.ts.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in src/app/app.config.ts.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in src/app/app.routes.ts.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in src/main.ts.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in src/styles.scss.
The file will have its original line endings in your working directory
warning: adding embedded git repository: test
hint: You've added another git repository inside your current repository.
hint: Clones of the outer repository will not contain the contents of
hint: the embedded repository and will not know how to obtain it.
hint: If you meant to add a submodule, use:
hint:
hint:   git submodule add <url> test
hint:
hint: If you added this path by mistake, you can remove it from the
hint: index with:
hint:
hint:   git rm --cached test
hint:
hint: See "git help submodule" for more information.
warning: LF will be replaced by CRLF in tsconfig.app.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in tsconfig.json.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in tsconfig.spec.json.
The file will have its original line endings in your working directory
    Successfully initialized git.
PS C:\temp> cd .\test\
PS C:\temp\test> ng s

Initial Chunk Files | Names         |  Raw Size
polyfills.js        | polyfills     |  82.71 kB |
main.js             | main          |  23.36 kB |
styles.css          | styles        |  96 bytes |

                    | Initial Total | 106.17 kB

Application bundle generation complete. [10.011 seconds]
Watch mode enabled. Watching for file changes...
  ➜  Local:   http://localhost:4200/

Thanks, Also, to be fair, I also have a laptop setup for my dev work, so I just copied the files over there (from the original project) and it works just fine. I was also able to create a new project just fine on the laptop. So I guess it is something local to the PC. Do you happen to have any thoughts on where to even start looking?

To be perfectly honest, I have no clue.
But when I see utterly strange behaviour, I would try by reinstalling node.js. I would recommend using NVM.

Ok thank you. You can probably close this ticket in that case. If I discover anything pertinent, I'll still update the ticket. Just FYI, I have seen other tickets about this, so it's something weird. I just don't know what.
https://github.com/angular/angular-cli/issues/26284

https://colin.is/blog/2020/error-main-ts-is-missing-from-the-typescript-compilation/
FYI, still testing, but I think I found the solution (although I can't explain why it worked yesterday).  Adding "preserveSymlinks" in the angular.json file seems to fix the issue.
"architect": {
  "build": {
    "builder": "@angular-devkit/build-angular:browser",
    "options": {
      "preserveSymlinks": true,

Had exactly the same issue, tried re-installing node etc, nothing worked until i too added the  "preserveSymlinks": true, to my angular.json

That is interesting... There is only

I'm facing the same problem, only I still get the same error even after setting "preserveSymlinks": true, but its behavior is strange

At the first initialization of ng serve, everything is fine, there is no error
Then I change some file and save it.
After that moment I get a message in the console with a link to this particular file that I am modifying.

my tsconfig.app
/* To learn more about this file see: https://angular.io/config/tsconfig. */
{
    "extends": "./tsconfig.json",
    "compilerOptions": {
        "outDir": "./out-tsc/app",
        "types": [
            "node"
        ]
    },
    "files": [
        "src/main.ts",
        "src/main.server.ts",
        "server.ts",
    ],
    "include": [
        "src/**/*.d.ts",
        "src/**/*.ts",
    ],
    "exclude": [
        "src/**/*.spec.ts"
    ]
}

I don't always have this problem, i.e. the file can be saved and there can be an error.

https://colin.is/blog/2020/error-main-ts-is-missing-from-the-typescript-compilation/
FYI, still testing, but I think I found the solution (although I can't explain why it worked yesterday). Adding "preserveSymlinks" in the angular.json file seems to fix the issue.
"architect": {
  "build": {
    "builder": "@angular-devkit/build-angular:browser",
    "options": {
      "preserveSymlinks": true,

Thanks, It worked for me as well.

JANK!

That is interesting... Is the app being created in a symlink?

I was using ConEmu as my console if that makes any difference?

Add "preserveSymlinks": true into your angular.json
"architect": {        "build": {                "builder": "@angular-devkit/build-angular:application",                "options": {  		    "preserveSymlinks": true, ...

sudo ng new test
Password:
? Which stylesheet format would you like to use? SCSS   [ https://sass-lang.com/documentation/syntax#scss                ]
? Do you want to enable Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering)?  This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m
Successfully initialized git.
macbook@Macbooks-MBP-2 angular_class % cd test
macbook@Macbooks-MBP-2 test % ng s
? Would you like to share pseudonymous usage data about this project with the Angular Team
at Google under Google's Privacy Policy at https://policies.google.com/privacy. For more
details and how to change this setting, see https://angular.io/analytics. No
An unhandled exception occurred: EACCES: permission denied, open '/Users/macbook/angular_class/test/angular.json'
See "/private/var/folders/0m/wz54_kk524s6pdp4fznrgcw40000gn/T/ng-PzYue2/angular-errors.log" for further details.
macbook@Macbooks-MBP-2 test % ng s
? Would you like to share pseudonymous usage data about this project with the Angular Team
at Google under Google's Privacy Policy at https://policies.google.com/privacy. For more
details and how to change this setting, see https://angular.io/analytics. Yes
An unhandled exception occurred: EACCES: permission denied, open '/Users/macbook/angular_class/test/angular.json'
See "/private/var/folders/0m/wz54_kk524s6pdp4fznrgcw40000gn/T/ng-7AIsdQ/angular-errors.log" for further details.
macbook@Macbooks-MBP-2 test % sudo ng s
? Would you like to share pseudonymous usage data about this project with the Angular Team
at Google under Google's Privacy Policy at https://policies.google.com/privacy. For more
details and how to change this setting, see https://angular.io/analytics. No
Global setting: enabled
Local setting: disabled
Effective status: disabled
⠸ Building...✘ [ERROR] Could not resolve "zone.js"
angular:polyfills:angular:polyfills:1:7:
  1 │ import 'zone.js';
    ╵        ~~~~~~~~~

The Yarn Plug'n'Play manifest forbids importing "zone.js" here because it's not listed as a dependency of this package:
../../.pnp.cjs:89:33:
  89 │           "packageDependencies": [\
     ╵                                  ~~

You can mark the path "zone.js" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
Application bundle generation failed. [2.734 seconds]
Watch mode enabled. Watching for file changes...

deleting Plug'n'Play manifest generated on MAC root deleted and application started working

Thank you! I ran the command above and then attempted to create a new project. No errors this time! :)

Thanks for the confirmation, this will be available on NPM later next week in 17.0.4.
PR that fixes the issue: https://github.com/angular/angular-cli/pull/26453

I'm facing the same problem, only I still get the same error even after setting "preserveSymlinks": true, but its behavior is strange

At the first initialization of ng serve, everything is fine, there is no error
Then I change some file and save it.
After that moment I get a message in the console with a link to this particular file that I am modifying.

my tsconfig.app
/* To learn more about this file see: https://angular.io/config/tsconfig. */
{
    "extends": "./tsconfig.json",
    "compilerOptions": {
        "outDir": "./out-tsc/app",
        "types": [
            "node"
        ]
    },
    "files": [
        "src/main.ts",
        "src/main.server.ts",
        "server.ts",
    ],
    "include": [
        "src/**/*.d.ts",
        "src/**/*.ts",
    ],
    "exclude": [
        "src/**/*.spec.ts"
    ]
}

I don't always have this problem, i.e. the file can be saved and there can be an error.
I use @angular/ssr by default, I don't know if there is such a bug in spa mode

I get the same behaviour. Did you manage to fix it?

I decided to downgrade to v16 for the moment in order to avoid this

@DariusMuscalu, you can still use the webpack based builders with version 17, there is no need to downgrade to version 16.
That said, unfortunately without a minimal reproduction we are not able to further action this problem as it appears that your issue does not share the same root cause of the original reported issue.

@DariusMuscalu, you can still use the webpack based builders with version 17, there is no need to downgrade to version 16.
That said, unfortunately without a minimal reproduction we are not able to further action this problem as it appears that your issue does not share the same root cause of the original reported issue.

Had some problems with firebase also, when I did ng add @angular/fire it was telling me that version 0.0.0 was only found and that's not a valid one. Tried using --force and got the same behavior. So for the moment, I decided to stick to v16.

There was an issue with the firebase release I believe. Until 4 days ago, the latest tag didn't refere to the v17 version.
Did you give it a try since ?

Tried to install specific versions also and it still said it only found 0.0.0 version.

@DariusMuscalu  FWIW, I was able to get AngularFire 17.0.0 working with Angular 17.0.5, although I did create a project with the --no-standalone option in order to add the app.module.ts file to ease setup. It was not easy however and since everything is brand new there isn't much info yet on how to set it up.  Not that I fault you for going back to v16, I was prepared to do the same.

I also had -no-standalone option. This version is still newly released and didn't manage to find anything related on the web, so I've decided to go with v16 as I am still new to angular and so I can speed up my learning.

removing
"aot": false,
from my angular.json config fixed my issue,

Still experiencing this issue with "aot": false. Also it seems like ng serve no longer detects changes at all in .html files.

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 17.0.6
Node: 20.9.0
Package Manager: npm 10.2.3
OS: darwin arm64

Angular: 17.0.6
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.6
@angular-devkit/build-angular   17.0.6
@angular-devkit/core            17.0.6
@angular-devkit/schematics      17.0.6
@schematics/angular             17.0.6
ng-packagr                      17.0.2
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2

I also have the same issue, build doesn't work and the REST API example endpoints in server.ts do not work. There is nothing logged in the console when i hit the endpoints it seems something could be wrong with server.ts


eslint-plugin-import cannot resolve module path on heroku

I am wondering if anyone has met the following error which I extracted from the application logs.
...
2016-06-09T00:56:08.496050+00:00 app[web.1]:
2016-06-09T00:56:08.992304+00:00 app[web.1]:
2016-06-09T00:56:08.992315+00:00 app[web.1]: ><EMAIL_ADDRESS>lint:js /app
2016-06-09T00:56:08.992316+00:00 app[web.1]: > eslint . --ignore-path .gitignore --ignore-pattern internals/scripts
2016-06-09T00:56:08.992317+00:00 app[web.1]:
2016-06-09T00:56:20.052063+00:00 app[web.1]:
2016-06-09T00:56:20.052074+00:00 app[web.1]: /app/app/app.js
2016-06-09T00:56:20.052075+00:00 app[web.1]:   28:20  error  Unable to resolve path to module 'containers/App/styles.css'  import/no-unresolved
2016-06-09T00:56:20.052076+00:00 app[web.1]:   48:37  error  Unable to resolve path to module 'containers/App/selectors'   import/no-unresolved
2016-06-09T00:56:20.052077+00:00 app[web.1]:   54:17  error  Unable to resolve path to module 'containers/App'             import/no-unresolved
2016-06-09T00:56:20.052077+00:00 app[web.1]:
2016-06-09T00:56:20.052078+00:00 app[web.1]: /app/app/components/Footer/index.js
2016-06-09T00:56:20.052079+00:00 app[web.1]:   3:15  error  Unable to resolve path to module 'components/A'  import/no-unresolved
2016-06-09T00:56:20.052080+00:00 app[web.1]:
2016-06-09T00:56:20.052081+00:00 app[web.1]: /app/app/components/Footer/tests/index.test.js
2016-06-09T00:56:20.052081+00:00 app[web.1]:   6:15  error  Unable to resolve path to module 'components/A'  import/no-unresolved
...

This happens when heroku starts the process specified by the Procfile: web: npm run start:production.
It seems the eslint plugin cannot resolve the module path specified by the configuration. And it only happens when I deploy the app on heroku. It seems to have no problem on local machine.

I haven't encountered that yet, but then I also don't use Heroku…
A quick fix would be to disable the rule in your package.json eslintConfig:
"rules": {
  "import/no-unresolved": 0
}

I'm getting this as well recently on my local machine, everything still works though... still trying to track it down!
  ✖  25:26  Unable to resolve path to module 'containers/RepoListItem'      import/no-unresolved
  ✖  26:20  Unable to resolve path to module 'components/Button'            import/no-unresolved
  ✖  27:16  Unable to resolve path to module 'components/H2'                import/no-unresolved
  ✖  28:18  Unable to resolve path to module 'components/List'              import/no-unresolved
  ✖  29:22  Unable to resolve path to module 'components/ListItem'          import/no-unresolved
  ✖  30:30  Unable to resolve path to module 'components/LoadingIndicator'  import/no-unresolved
  ✖  31:23  Unable to resolve path to module 'components/InputText'         import/no-unresolved

This might be because the webpack resolver for eslint-plugin-import doesn't support webpack 2
https://github.com/benmosher/eslint-plugin-import/issues/265


Fix tooltip positioning with regards to viewports

The getPosition function was simplified with a new function,
getViewportBounds, was added to specifically
tackle the cases where we’re looking for the viewport bounds.
‘absolute’ and ‘fixed’ tooltips are now matched against the screen
where other ones are made to fit inside the viewport element.

@twbs-savage Retry

Tests failed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: BUSTED
Commit: bc9a3ad829a05b330ac66161ba4b62b860868c0b
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/45925623
(Please note that this is a fully automated comment.)

@ericmartel I'll just squash the history before merging this. Could you add a commit to fix the rounding problem and address the other minor comments I made?

@cvrebert sorry I think I missed this comment, let me know if I can do anything else to help!

Tests failed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: BUSTED
Commit: 388064a84ed771e47959cfc77b2f47472ab4c56f
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/45946437
(Please note that this is a fully automated comment.)

@cvrebert there seems to be problems with the tests, I doubt it has anything to do with my changelist though :/
Could not connect to Sauce Labs API: Error: read ECONNRESET

@twbs-savage Retry

Tests failed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: BUSTED
Commit: 388064a84ed771e47959cfc77b2f47472ab4c56f
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/45960000
(Please note that this is a fully automated comment.)

@cvrebert thanks for the retry, is there a way to get more details than:
13972015-01-05 15:53:17:344 - info: [IOS_SYSLOG_ROW ] Jan 5 07:53:17 itako36176 assertiond[631]: assertion failed: 13F34 12B411: assertiond + 11523 [3F572A0B-7E12-378D-AFEE-EA491BAF2C36]: 0x1
is there a way to extract which assert failed?
Thank you very much, I'm sorry if I'm being a burden

Should be in the screencast on fe963a60d91d48a999a3a8e750010755

@cvrebert the error seems to come from affix.js, possibly from my bad merge?


Running into issue while Testing Windows AMI

I am trying to create a Microsoft Windows Server 2016 Base  AMI and use Goss for testing it. The same configuration worked fine when I launched Amazon Linux base AMI. However it fails provisioning Goss when I use it for Windows. Am I missing something for Windows server tests using Goss (below scenario).
My Template:
{
  "sensitive-variables": ["aws_access_key", "aws_secret_key", "token", "winrm_username_env", "winrm_password_env"],

  "builders": [{
      "type"                : "amazon-ebs",
      "access_key"          : "{{ user `aws_access_key` }}",
      "secret_key"          : "{{ user `aws_secret_key` }}",
      "token"               : "{{ user `token`}}",

      "region"              : "{{ user `region` }}",
      "instance_type"       : "t2.micro",
      "source_ami"          : "ami-xxx",
      "ami_name"            : "windows-ami-packer--{{timestamp}}",
      "winrm_username"      : "{{ user `winrm_username_env`}}",
      "user_data_file"      : "C:/Users/name/Desktop/packer-build-windows-ami/scripts/bootstrap_win.txt",
      "communicator"        : "winrm",
      "tags":{
        "Name": "windows-image- {{timestamp}}"
        }

  }],

  "provisioners": [
    {
      "type"                : "windows-restart"
    },

    {
      "script": "C:/Users/name/Desktop/packer-build-windows-ami/scripts/scripts.ps1",
      "type": "powershell"
    },

    {
      "type": "powershell",
      "environment_vars": ["WINRMUSER={{ user `winrm_username_env`}}", "WINRMPASS={{ user `winrm_password_env`}}"],
      "inline": [
        "net user $Env:WINRMUSER $Env:WINRMPASS"
      ]
    },
    {
      "type": "goss",
      "tests": [
        "C:/Users/name/Desktop/packer-build-windows-ami/goss/goss.yaml"
      ]
    }
  ]
}

Error:
==> amazon-ebs: Provisioning with Powershell...
==> amazon-ebs: Provisioning with powershell script: C:\Users\name\AppData\Local\Temp\powershell-provisioner014273411
    amazon-ebs: The command completed successfully.
    amazon-ebs:
==> amazon-ebs: Provisioning with Goss
==> amazon-ebs: Configured to run on Linux
    amazon-ebs: Creating directory: /tmp/goss
==> amazon-ebs: Provisioning step had errors: Running the cleanup provisioner, if present...
==> amazon-ebs: Terminating the source AWS instance...
==> amazon-ebs: Cleaning up any extra volumes...
==> amazon-ebs: No volumes to clean up, skipping
==> amazon-ebs: Deleting temporary security group...
==> amazon-ebs: Deleting temporary keypair...
Build 'amazon-ebs' errored after 8 minutes 33 seconds: Error creating remote directory: http response error: 401 - invalid content type

==> Wait completed after 8 minutes 33 seconds

==> Some builds didn't complete successfully and had errors:
--> amazon-ebs: Error creating remote directory: http response error: 401 - invalid content type

You don't have it configured properly for Windows. The out includes Configured to run on Linux.
You need to set the target_os in the provisioner config and the GOSS_USE_ALPHA flag to 1 see: https://github.com/YaleUniversity/packer-provisioner-goss#windows-support
An example configuration can be found at https://github.com/kubernetes-sigs/image-builder/blob/e56122226e1447eb21327f2ac4f98bde0e422b83/images/capi/packer/azure/packer-windows.json#L138

marking this as closed since no follow up


[request] resume playback on startup

[request] resume playback on startup

Would love this - or something to remember where you last were in each track -- would make this a joy to use for podcasts.

Alright, finally got around to adding this -- it'll be available as an "advanced" option in the settings screen called "ResumePlaybackOnStartup". Relevant commit: https://github.com/clangen/musikcube/commit/6fd0c537b4f94534c8f2ca41b555593d87288459

<3
On Sun, Apr 11, 2021, 11:42 PM casey langen @.***>
wrote:

Alright, finally got around to adding this -- it'll be available in the
next release as an "advanced" option in the settings screen called
"ResumePlaybackOnStartup". Relevant commit: 6fd0c53
https://github.com/clangen/musikcube/commit/6fd0c537b4f94534c8f2ca41b555593d87288459
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/clangen/musikcube/issues/284#issuecomment-817499522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEJWBSSJIUWTCZMPDFFNULTIKB6BANCNFSM4JLMUTJA
.

0.96.6 has been released.


setup error

bazel 1.0.0
unbutu: Ubuntu 5.4.0-6ubuntu1~16.04.10
tensorflow: 2.7
python: 3.9.6
When i execute the statement "python3 -m pip install ."  I got the error as follow:
Requirement already satisfied: absl-py in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (1.0.0)
Requirement already satisfied: apache-beam[gcp]>=2.32 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (2.34.0)
Requirement already satisfied: grpcio in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (1.42.0)
Requirement already satisfied: matplotlib in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (3.5.0)
Requirement already satisfied: mock in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (4.0.3)
Requirement already satisfied: networkx in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (2.6.3)
Requirement already satisfied: numpy in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (1.20.3)
Requirement already satisfied: protobuf>=3.17 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (3.19.1)
Requirement already satisfied: pyarrow in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (5.0.0)
Requirement already satisfied: pygraphviz in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (1.7)
Requirement already satisfied: scipy in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (1.7.3)
Requirement already satisfied: six in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (1.16.0)
Requirement already satisfied: tensorflow-cpu>=2.7.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (2.7.0)
Requirement already satisfied: avro-python3!=1.9.2,<1.10.0,>=1.8.1 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (<IP_ADDRESS>)
Requirement already satisfied: crcmod<2.0,>=1.7 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.7)
Requirement already satisfied: dill<0.3.2,>=<IP_ADDRESS> in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (<IP_ADDRESS>)
Requirement already satisfied: fastavro<2,>=0.21.4 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.4.7)
Requirement already satisfied: future<1.0.0,>=0.18.2 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.18.2)
Requirement already satisfied: hdfs<3.0.0,>=2.1.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.6.0)
Requirement already satisfied: httplib2<0.20.0,>=0.8 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.19.1)
Requirement already satisfied: pymongo<4.0.0,>=3.8.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (3.12.1)
Requirement already satisfied: oauth2client<5,>=2.0.1 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (4.1.3)
Requirement already satisfied: pydot<2,>=1.2.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.4.2)
Requirement already satisfied: python-dateutil<3,>=2.8.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.8.2)
Requirement already satisfied: pytz>=2018.3 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2021.3)
Requirement already satisfied: requests<3.0.0,>=2.24.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.26.0)
Requirement already satisfied: typing-extensions<4,>=3.7.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (<IP_ADDRESS>)
Requirement already satisfied: orjson<4.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (3.6.4)
Requirement already satisfied: cachetools<5,>=3.1.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (4.2.4)
Requirement already satisfied: google-apitools<0.5.32,>=0.5.31 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.5.31)
Requirement already satisfied: google-auth<3,>=1.18.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.35.0)
Requirement already satisfied: google-cloud-datastore<2,>=1.8.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.15.3)
Requirement already satisfied: google-cloud-pubsub<2,>=0.39.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.7.0)
Requirement already satisfied: google-cloud-bigquery<3,>=1.6.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.30.1)
Requirement already satisfied: google-cloud-bigquery-storage>=2.6.3 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.10.1)
Requirement already satisfied: google-cloud-core<2,>=0.28.1 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.7.2)
Requirement already satisfied: google-cloud-bigtable<2,>=0.31.1 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.7.0)
Requirement already satisfied: google-cloud-spanner<2,>=1.13.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.19.1)
Requirement already satisfied: grpcio-gcp<1,>=0.2.2 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.2.2)
Requirement already satisfied: google-cloud-dlp<2,>=0.12.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.0.0)
Requirement already satisfied: google-cloud-language<2,>=1.3.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.3.0)
Requirement already satisfied: google-cloud-videointelligence<2,>=1.8.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.16.1)
Requirement already satisfied: google-cloud-vision<2,>=0.38.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.0.0)
Requirement already satisfied: google-cloud-recommendations-ai<=0.2.0,>=0.1.0 in /usr/local/python3/lib/python3.9/site-packages (from apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.2.0)
Requirement already satisfied: fasteners>=0.14 in /usr/local/python3/lib/python3.9/site-packages (from google-apitools<0.5.32,>=0.5.31->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.16.3)
Requirement already satisfied: pyasn1-modules>=0.2.1 in /usr/local/python3/lib/python3.9/site-packages (from google-auth<3,>=1.18.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.2.8)
Requirement already satisfied: setuptools>=40.3.0 in /usr/local/python3/lib/python3.9/site-packages (from google-auth<3,>=1.18.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (56.0.0)
Requirement already satisfied: rsa<5,>=3.1.4 in /usr/local/python3/lib/python3.9/site-packages (from google-auth<3,>=1.18.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (4.8)
Requirement already satisfied: google-resumable-media<3.0dev,>=0.6.0 in /usr/local/python3/lib/python3.9/site-packages (from google-cloud-bigquery<3,>=1.6.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.1.0)
Requirement already satisfied: google-api-core[grpc]<3.0.0dev,>=1.29.0 in /usr/local/python3/lib/python3.9/site-packages (from google-cloud-bigquery<3,>=1.6.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.31.4)
Requirement already satisfied: proto-plus>=1.10.0 in /usr/local/python3/lib/python3.9/site-packages (from google-cloud-bigquery<3,>=1.6.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.19.8)
Requirement already satisfied: packaging>=14.3 in /usr/local/python3/lib/python3.9/site-packages (from google-cloud-bigquery<3,>=1.6.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (21.3)
Requirement already satisfied: googleapis-common-protos<2.0dev,>=1.6.0 in /usr/local/python3/lib/python3.9/site-packages (from google-api-core[grpc]<3.0.0dev,>=1.29.0->google-cloud-bigquery<3,>=1.6.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.53.0)
Requirement already satisfied: libcst>=0.2.5 in /usr/local/python3/lib/python3.9/site-packages (from google-cloud-bigquery-storage>=2.6.3->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.3.23)
Requirement already satisfied: grpc-google-iam-v1<0.13dev,>=0.12.3 in /usr/local/python3/lib/python3.9/site-packages (from google-cloud-bigtable<2,>=0.31.1->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.12.3)
Requirement already satisfied: google-crc32c<2.0dev,>=1.0 in /usr/local/python3/lib/python3.9/site-packages (from google-resumable-media<3.0dev,>=0.6.0->google-cloud-bigquery<3,>=1.6.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.3.0)
Requirement already satisfied: docopt in /usr/local/python3/lib/python3.9/site-packages (from hdfs<3.0.0,>=2.1.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.6.2)
Requirement already satisfied: pyparsing<3,>=2.4.2 in /usr/local/python3/lib/python3.9/site-packages (from httplib2<0.20.0,>=0.8->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.4.7)
Requirement already satisfied: typing-inspect>=0.4.0 in /usr/local/python3/lib/python3.9/site-packages (from libcst>=0.2.5->google-cloud-bigquery-storage>=2.6.3->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.7.1)
Requirement already satisfied: pyyaml>=5.2 in /usr/local/python3/lib/python3.9/site-packages (from libcst>=0.2.5->google-cloud-bigquery-storage>=2.6.3->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (6.0)
Requirement already satisfied: pyasn1>=0.1.7 in /usr/local/python3/lib/python3.9/site-packages (from oauth2client<5,>=2.0.1->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.4.8)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/python3/lib/python3.9/site-packages (from requests<3.0.0,>=2.24.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2021.10.8)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/python3/lib/python3.9/site-packages (from requests<3.0.0,>=2.24.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (1.26.7)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/python3/lib/python3.9/site-packages (from requests<3.0.0,>=2.24.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (3.3)
Requirement already satisfied: charset-normalizer~=2.0.0 in /usr/local/python3/lib/python3.9/site-packages (from requests<3.0.0,>=2.24.0->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (2.0.8)
Requirement already satisfied: h5py>=2.9.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (3.6.0)
Requirement already satisfied: keras<2.8,>=2.7.0rc0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (2.7.0)
Requirement already satisfied: astunparse>=1.6.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (1.6.3)
Requirement already satisfied: termcolor>=1.1.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (1.1.0)
Requirement already satisfied: gast<0.5.0,>=0.2.1 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (0.4.0)
Requirement already satisfied: wrapt>=1.11.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (1.13.3)
Requirement already satisfied: wheel<1.0,>=0.32.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (0.37.0)
Requirement already satisfied: google-pasta>=0.1.1 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (0.2.0)
Requirement already satisfied: flatbuffers<3.0,>=1.12 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (2.0)
Requirement already satisfied: tensorflow-io-gcs-filesystem>=0.21.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (0.22.0)
Requirement already satisfied: opt-einsum>=2.3.2 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (3.3.0)
Requirement already satisfied: tensorflow-estimator<2.8,~=2.7.0rc0 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (2.7.0)
Requirement already satisfied: tensorboard~=2.6 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (2.7.0)
Requirement already satisfied: keras-preprocessing>=1.1.1 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (1.1.2)
Requirement already satisfied: libclang>=9.0.1 in /usr/local/python3/lib/python3.9/site-packages (from tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (12.0.0)
Requirement already satisfied: markdown>=2.6.8 in /usr/local/python3/lib/python3.9/site-packages (from tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (3.3.6)
Requirement already satisfied: google-auth-oauthlib<0.5,>=0.4.1 in /usr/local/python3/lib/python3.9/site-packages (from tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (0.4.6)
Requirement already satisfied: tensorboard-data-server<0.7.0,>=0.6.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (0.6.1)
Requirement already satisfied: tensorboard-plugin-wit>=1.6.0 in /usr/local/python3/lib/python3.9/site-packages (from tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (1.8.0)
Requirement already satisfied: werkzeug>=0.11.15 in /usr/local/python3/lib/python3.9/site-packages (from tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (2.0.2)
Requirement already satisfied: requests-oauthlib>=0.7.0 in /usr/local/python3/lib/python3.9/site-packages (from google-auth-oauthlib<0.5,>=0.4.1->tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (1.3.0)
Requirement already satisfied: importlib-metadata>=4.4 in /usr/local/python3/lib/python3.9/site-packages (from markdown>=2.6.8->tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (4.8.2)
Requirement already satisfied: zipp>=0.5 in /usr/local/python3/lib/python3.9/site-packages (from importlib-metadata>=4.4->markdown>=2.6.8->tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (3.6.0)
Requirement already satisfied: oauthlib>=3.0.0 in /usr/local/python3/lib/python3.9/site-packages (from requests-oauthlib>=0.7.0->google-auth-oauthlib<0.5,>=0.4.1->tensorboard~=2.6->tensorflow-cpu>=2.7.0->tensorflow-gnn==0.1.0) (3.1.1)
Requirement already satisfied: mypy-extensions>=0.3.0 in /usr/local/python3/lib/python3.9/site-packages (from typing-inspect>=0.4.0->libcst>=0.2.5->google-cloud-bigquery-storage>=2.6.3->apache-beam[gcp]>=2.32->tensorflow-gnn==0.1.0) (0.4.3)
Requirement already satisfied: fonttools>=4.22.0 in /usr/local/python3/lib/python3.9/site-packages (from matplotlib->tensorflow-gnn==0.1.0) (4.28.2)
Requirement already satisfied: cycler>=0.10 in /usr/local/python3/lib/python3.9/site-packages (from matplotlib->tensorflow-gnn==0.1.0) (0.11.0)
Requirement already satisfied: pillow>=6.2.0 in /usr/local/python3/lib/python3.9/site-packages (from matplotlib->tensorflow-gnn==0.1.0) (8.4.0)
Requirement already satisfied: setuptools-scm>=4 in /usr/local/python3/lib/python3.9/site-packages (from matplotlib->tensorflow-gnn==0.1.0) (6.3.2)
Requirement already satisfied: kiwisolver>=1.0.1 in /usr/local/python3/lib/python3.9/site-packages (from matplotlib->tensorflow-gnn==0.1.0) (1.3.2)
Requirement already satisfied: tomli>=1.0.0 in /usr/local/python3/lib/python3.9/site-packages (from setuptools-scm>=4->matplotlib->tensorflow-gnn==0.1.0) (1.2.2)
Building wheels for collected packages: tensorflow-gnn
Building wheel for tensorflow-gnn (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-nf5s7_74/setup.py'"'"'; file='"'"'/tmp/pip-req-build-nf5s7_74/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-8jo1b0me
cwd: /tmp/pip-req-build-nf5s7_74/
Complete output (35 lines):
running bdist_wheel
running build
running bazel_build
Starting local Bazel server and connecting to it...
ERROR: Unrecognized option: --experimental_repo_remote_exec
INFO: Writing tracer profile to '/root/.cache/bazel/_bazel_root/958b14b9bd3acfff4092d0b52e211899/command.profile.gz'
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-req-build-nf5s7_74/setup.py", line 152, in
setup(
File "/usr/local/python3/lib/python3.9/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/usr/local/python3/lib/python3.9/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/local/python3/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 299, in run
self.run_command('build')
File "/usr/local/python3/lib/python3.9/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/local/python3/lib/python3.9/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/local/python3/lib/python3.9/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-req-build-nf5s7_74/setup.py", line 86, in run
subprocess.check_call(
File "/usr/local/python3/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/bazel', 'run', '-c', 'opt', '--experimental_repo_remote_exec', '//package:move_generated_files']' returned non-zero exit status 2.
ERROR: Failed building wheel for tensorflow-gnn
Running setup.py clean for tensorflow-gnn
Failed to build tensorflow-gnn
Installing collected packages: tensorflow-gnn
Running setup.py install for tensorflow-gnn ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-nf5s7_74/setup.py'"'"'; file='"'"'/tmp/pip-req-build-nf5s7_74/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-rsfpi3kt/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/python3/include/python3.9/tensorflow-gnn
cwd: /tmp/pip-req-build-nf5s7_74/
Complete output (36 lines):
running install
running build
running bazel_build
ERROR: Unrecognized option: --experimental_repo_remote_exec
INFO: Writing tracer profile to '/root/.cache/bazel/_bazel_root/958b14b9bd3acfff4092d0b52e211899/command.profile.gz'
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-req-build-nf5s7_74/setup.py", line 152, in
setup(
File "/usr/local/python3/lib/python3.9/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/usr/local/python3/lib/python3.9/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/local/python3/lib/python3.9/site-packages/setuptools/command/install.py", line 61, in run
return orig.install.run(self)
File "/usr/local/python3/lib/python3.9/distutils/command/install.py", line 546, in run
self.run_command('build')
File "/usr/local/python3/lib/python3.9/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/local/python3/lib/python3.9/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/local/python3/lib/python3.9/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/local/python3/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-req-build-nf5s7_74/setup.py", line 86, in run
subprocess.check_call(
File "/usr/local/python3/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/bazel', 'run', '-c', 'opt', '--experimental_repo_remote_exec', '//package:move_generated_files']' returned non-zero exit status 2.
----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-nf5s7_74/setup.py'"'"'; file='"'"'/tmp/pip-req-build-nf5s7_74/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-rsfpi3kt/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/python3/include/python3.9/tensorflow-gnn Check the logs for full command output.

Hey, @dmadisetti is absolutely right! It's a bazel build issue but it has a hack-y fix:
Clone the repo locally, go to the package/ directory, and edit your BUILD file. The original content is,
licenses(["notice"])  # Apache 2.0

config_setting(
    name = "windows",
    constraint_values = [
        "@bazel_tools//platforms:windows",
    ],
)

sh_binary(
    name = "move_generated_files",
    srcs = ["move_generated_files.sh"],
    data = [
        "//tensorflow_gnn/proto:examples_pb2.py",
        "//tensorflow_gnn/proto:graph_schema_pb2.py",
        "//tensorflow_gnn/sampler:subgraph_pb2.py",
        "//tensorflow_gnn/sampler:sampling_spec_pb2.py",
        "//tensorflow_gnn/tools:sampled_stats_pb2.py",
    ],
)

The Fix
There's the line "//tensorflow_gnn/sampler:subgraph_pb2.py", that has to be removed. This is because this file was removed in a more recent commit but the bazel build wasn't updated to reflect those changes.
Once you remove this line (while keeping the others), go ahead and python3 -m pip install . again. Your installation should run smoothly.

Check out #7 for more. Hope this helps!

Also see #16
Number #13 also provides a fix

This should now be fixed with the latest update!


Under new SharePoint admin center -> Settings, there is no "classic settings page" option

Also I cannot find how to  show or hide the Create site command.
[Enter feedback here]

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

ID: b29978b1-a400-bacb-1330-55ed3d652053
Version Independent ID: eae9fd16-57fc-1a80-3ce9-9b34b68eb1e0
Content: Manage site creation in SharePoint - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/manage-site-creation.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@legendgod Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


[AutoPR reservations/resource-manager] [Hub Generated] Review request for Microsoft.Capacity to add version preview/2019-04-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7206

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/7362


fix for embedded json in wps request

Overview
This PR is a quick fix to parse an embedded json (complex type) from the wps execute request (xml).
Probably there is more work to do for embedding json in OWSLib and PyWPS. Using CDATA or always use base64 encoding?
Related Issue / Discussion
Additional Information
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[ ] I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
[x ] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

A wps execute request with embedded json looks like this:
<wps100:Execute
  xmlns:wps100="http://www.opengis.net/wps/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  service="WPS"
  version="1.0.0"
  xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd">
  <ows110:Identifier xmlns:ows110="http://www.opengis.net/ows/1.1">orchestrate</ows110:Identifier>
  <wps100:DataInputs>
    <wps100:Input>
      <ows110:Identifier xmlns:ows110="http://www.opengis.net/ows/1.1">workflow</ows110:Identifier>
      <wps100:Data>
        <wps100:ComplexData encoding="utf-8" mimeType="application/json">{"inputs": {"tas": ["CMIP6.ScenarioMIP.MIROC.MIROC6.ssp119.r1i1p1f1.day.tas.gn.v20191016"]}, "steps": {"subset_tas_1": {"run": "subset", "in": {"collection": "inputs/tas", "time": "2016-01-01/2016-03-31"}}}, "outputs": {"output": "subset_tas_1/output"}, "doc": "workflow"}</wps100:ComplexData>
      </wps100:Data>
    </wps100:Input>
  </wps100:DataInputs>
  <wps100:ResponseForm>
    <wps100:ResponseDocument storeExecuteResponse="true" status="true" lineage="false">
      <wps100:Output asReference="true">
        <ows110:Identifier xmlns:ows110="http://www.opengis.net/ows/1.1">output</ows110:Identifier>
      </wps100:Output>
      <wps100:Output asReference="true">
        <ows110:Identifier xmlns:ows110="http://www.opengis.net/ows/1.1">prov</ows110:Identifier>
      </wps100:Output><wps100:Output asReference="true">
        <ows110:Identifier xmlns:ows110="http://www.opengis.net/ows/1.1">prov_plot</ows110:Identifier>
      </wps100:Output>
    </wps100:ResponseDocument>
  </wps100:ResponseForm>
</wps100:Execute>

Good point @huard ; can/should we CDATA the content?

Wait, I got confused, this is already the inside of the CDATA content, correct ?
Is there really something to do in OWSLib, I'm using JSON ComplexInputs in production for a while and everything works fine (using the birdy client).

Coverage decreased (-0.01%) to 75.47% when pulling 71e38d197985288bb978411920c42b56a3602d70 on cehbrecht:fix-json-input into 81bb1e4e1b85ea75d72b33c6f8543752b251830a on geopython:pywps-4.2.

Not sure, I don't see CDATA in the example in https://github.com/geopython/pywps/pull/560#issuecomment-745401805

Not sure, I don't see CDATA in the example in #560 (comment)

Yes, I think there was no CDATA so far. We were just lucky :)

I would need a quick fix for now ... and make it better later.

The code is very tricky here:
https://github.com/geopython/pywps/blob/20e1e254a3f7914e555fa89f363d1f6eb5f3895c/pywps/app/WPSRequest.py#L576-L586
When the base64 decoding fails then it would return the original data. That is why sometimes our json input parameter worked and sometimes not ... depending on the characters.
ping @agstephens

@tomkralidis @huard I'm merging this PR as a quick-fix. Needs to be done right later (#562)

Hello,
As I said in my comment here, in my opinion the proper fix is to not decode string as base64 when the attribute encoding is not base64.
The json embedded data must be properly escaped, using CDATA or XML entities when needed. The etree.parser will remove them properly. Moreover the encoding of such embedded json has to be the same as the XML as far I understand XML.
As side note, json standard does not specify any encoding, it is defined as Unicode code point, thus any encoding of Unicode is a valid choice. In that regards the other option to send json is by specifying charset in the mime type as follow:  mimetype=application/json; charset=utf-8 and using encoding=base64 . But usually the paramter charset of mimetype is used for text mime type not application one.

After a double check even more in WPS 1.0.0, it seems that there is not base64 references, only the WPS 2.0.0 has base64 reference.


segmentation fault on mount

Dear astrada,
I'm trying to run your app on ArchLinux and installed it and it's dependencies via AUR (user repository -- both, version 0.5.15 , which is available there and 0.5.18).
Authorization works fine, but on mounting the app crashes. I cleared the cache and tried to run the app via gdb:
(gdb) ru -d -debug ~/mnt/google
Starting program: /usr/bin/google-drive-ocamlfuse -d -debug ~/mnt/google
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Starting application setup (label=default, base_dir=/home/oleid/.gdfuse).
Opening log file: /home/oleid/.gdfuse/default/gdfuse.log
FUSE library version: 2.9.4
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.23
flags=0x0003f7fb
max_readahead=0x00020000
   INIT: 7.19
   flags=0x00000031
   max_readahead=0x00020000
   max_write=0x00020000
   max_background=0
   congestion_threshold=0
   unique: 1, success, outsize: 40
unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 1492
   unique: 2, error: -38 (Function not implemented), outsize: 16
unique: 3, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 1492
LOOKUP /.Trash
getattr /.Trash
[New Thread 0x7ffff46d5700 (LWP 2485)]
[Thread 0x7ffff46d5700 (LWP 2485) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00000000005c3587 in caml_absf_mask ()
(gdb) backtr
#0  0x00000000005c3587 in caml_absf_mask ()
Backtrace stopped: Cannot access memory at address 0xf4b160d0
(gdb)

This is curl.log:
[0.023671] curl: info:   Trying <IP_ADDRESS>...
[0.047328] curl: info: Connected to www.googleapis.com (<IP_ADDRESS>) port 443 (#0)
[0.048258] curl: info: ALPN, offering http/1.1
[0.048537] curl: info: Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
[0.065566] curl: info: successfully set certificate verify locations:
[0.065586] curl: info:   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
[0.065679] curl: info: TLSv1.2 (OUT), TLS header, Certificate Status (22):

And gdrive.log:
[0.000262] TID=0: Setting up default filesystem...
[0.000299] TID=0: Loading configuration from /home/oleid/.gdfuse/default/config...done
Saving configuration in /home/oleid/.gdfuse/default/config...done
[0.000591] TID=0: Loading application state from /home/oleid/.gdfuse/default/state...done
Current version: 0.5.18
Setting up cache db...done
Setting up CURL...done
Refresh token already present.
[0.004170] TID=0: Starting filesystem /home/oleid/mnt/google
[0.008530] TID=0: init_filesystem
[0.010788] TID=0: getattr /.Trash
Loading metadata from db...not found
Refreshing metadata...

Any suggestion on where to start digging? I've never did any ocaml programming, thus I'm not sure how to get meaningful backtraces.
By the way: it's

libgcrypt-1.6.4-1
libcurl 7.44.0-1

Best,
Olaf

Have you tried setting curl_debug_off to true in config?

I'm not at the same machine at the moment,  but I installed google-drive-ocamlfuse there, too. This time, it's a Gentoo based system. There, I have the same problem, but the program dies with SIGILL instead SIGSEGV.
At least on this machine, setting curl_debug_off to true helps!

Confirmed, curl_debug_off = true helps on ArchLinux, too.

OK, thanks for your feedback.


Feature: "ng generate component" needs a flag to generate routes for standalone components

Command
generate
Description
Running ng generate component users --standalone generates users/users.component.{css,html,spec.ts,ts} files.
For imported or lazy-loaded routes, we can create a users/users.routes.ts that looks like this:
import { Routes } from '@angular/router';
import { UserListComponent, UserDetailsComponent, CreateUserComponent, EditUserComponent } from './users/users.component';

export const routes: Routes = [
    { path: 'list', component: UserListComponent },
    { path: 'details/:id', component: UserDetailsComponent },
    { path: 'create', component: CreateUserComponent },
    { path: 'edit', component: EditUserComponent },
];

...and import it with loadChildren in app.routes.ts, but ng could simplify the process.
Describe the solution you'd like
ng generate component users --standalone --routes could scaffold the users/users.routes.ts file for us, letting us just fill it in as we go.
import { Routes } from '@angular/router';
import * from './users.component';

export const routes: Routes = [
    { path: '', component: UsersComponent },
];

An alternative is ng generate component users --standalone --routes=crud, which generates components and route mappings for each CRUD component.  ng generate component users --standalone --routes=cr would only generates Create and Read components and mappings.
Describe alternatives you've considered
yasnippets with emacs, but ng incorporating this functionality would make life easier.

@alan-agius4 Would you like me to take a shot at adding this functionality?

This is actually something that @AndrewKushnir was looking at sometime ago. We still had some pending design decisions, which required broader discussions with the rest of team.

Thank you for the info.  I'll implement a placeholder in elisp for now.
@AndrewKushnir, I'm here to help if you want when those design decisions are made.


Fix for #34 and some Documentation

Thanks for this PR, it's merged. :)
I shortened your explanations a bit and moved the integration to the setup part.

No problem - thank you I've read the new part and it looks good - please consider changing the version number in ReadMe - Installation with Composer (Option 3) -> the versionnumber is still 0.4^^

Done in 1cb658f :)


[CAMEL-10481] Camel does not expose cassandra-all any more

Thanks for the PR it has been merged. Do you mind closing this?


Make wrist rotation more real when turning the hands backward

Currently, the hand bone is twisted 180 degree to the back, which looks unnatural.

I report this bug  to the 3D designer ，It can be solve by the bone weights setting in model


Attempts to fix a crasher with BloomFilterWrapper in macOS 11.x

Task/Issue URL: https://app.asana.com/0/0/1205931560838491/f
iOS PR:
macOS PR: https://github.com/duckduckgo/macos-browser/pull/1839
What kind of version bump will this require?: Patch
Description
Attempts to provide a fix to a crash that's happening in macOS 11.x systems due to BloomFilterWrapper.
Testing
Just make sure everything builds fine.  There are no logical changes.

Internal references:
Software Engineering Expectations
Technical Design Template

Closing this as it didn't resolve the issue.