Add addresses primary subAttribute

SubAttribute primary was missed in addresses attribute user schema

Hi @giuseppebonanno, thanks for your contribution!
One would think that as addresses is a multi-valued complex attribute, it would also include the "primary" attribute (RFC7643§2.4 - default set of attributes).
However, as per the specification (RFC7643§4.1.2 and RFC7643§8.7.1), the subAttributes of the addresses attribute for the User schema have been otherwise defined, and do not include the "primary" subAttribute.
I agree that it seems to be an omission, however in order to conform to the specification "out of the box", I can't accept your PR.
As an alternative, it is possible to add the "primary" attribute to your User schema for use in your implementation, with the following code:
SCIMMY.Schemas.User.definition.attribute("addresses").subAttributes.push(new SCIMMY.Types.Attribute("boolean", "primary"));

As schema instances are singletons, this will only need to run once during initialisation, and will make the "primary" attribute available anywhere the User schema is used.
Let me know if you have any other questions or comments about the above.
Thanks,
Sam


move functions to python_owl

moved find_max_brightness to python-owl in order to be compatible with analog settings
https://gitlab.com/ramonaoptics/mcam/python-owl/-/issues/783

Tests are failing due to the removal of the find max brightness in the API. Please leave that in.
You can override it in our subclass.
Finally, you can remove the analog one. It was broken anyway

Ok I'll leave those two functions in. We can close this PR then.
When you say "remove the analog one", do you mean the previous PR: #8

Please see new PR. Generally speaking, you cannot simply remove functions from a public API.
People do start to rely on them.
You can however remove broken code that was never working.
For things that are specific to our hardware, we can always overwrite the properties.


Fix error parse of ProxyConfig

Signed-off-by: CalvinNeo<EMAIL_ADDRESS>What problem does this PR solve?
Issue Number: ref https://github.com/pingcap/tiflash/issues/5635
Problem Summary:
ProxyConfig should own submodules: server and raftstore. We can't directly use fields.
See more in issue.
What is changed and how it works?
Check List
Tests

[x] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

[flash]
service_addr = "<IP_ADDRESS>:9998"

[server]
addr = "<IP_ADDRESS>:9000"
advertise-addr = "<IP_ADDRESS>:9000"
engine-addr = "<IP_ADDRESS>:9999"
status-addr = "<IP_ADDRESS>:9001"
advertise-status-addr = "<IP_ADDRESS>:9001"

And it
    {
      "store": {
        "id": 68,
        "address": "<IP_ADDRESS>:9999",
        "labels": [
          {
            "key": "engine",
            "value": "tiflash"
          }
        ],
        "version": "v6.2.0-alpha-159-gcb31596d7-dirty",
        "peer_address": "<IP_ADDRESS>:9000",
        "status_address": "<IP_ADDRESS>:9001",
        "git_hash": "cb31596d7c7bee776517ec2914637752e09675cf",
        "start_timestamp":<PHONE_NUMBER>,
        "deploy_path": "/Users/calvin/.tiup/components/tiflash/v6.1.0/tiflash",
        "node_state": 1,
        "state_name": "Down"
      },
      "status": {
        "capacity": "0B",
        "available": "0B",
        "used_size": "0B",
        "leader_count": 0,
        "leader_weight": 1,
        "leader_score": 0,
        "leader_size": 0,
        "region_count": 0,
        "region_weight": 1,
        "region_score": 0,
        "region_size": 0,
        "slow_score": 0,
        "start_ts": "2022-08-17T13:47:07+08:00",
        "last_heartbeat_ts": "1970-01-01T08:00:00+08:00"
      }
    }


[Bittrex] Examples for v3

End of life for the v1 api is planned for 9/30/2020 and from this date, only v3 calls will be supported.
=> It will be ideal to have the bittrex-example covering v3 specific use/calls.

PR: https://github.com/knowm/XChange/pull/3722


0.5.4

@btford could you please review & release if ok.
Needed for https://github.com/angular/angular/issues/2912

LGTM

Landed. Published to npm as v0.5.4

:+1: Thanks


Why is any TS file will compiled into renderer/main_window/index.js  Not used in time

Preflight Checklist

[ Y] I have read the contribution documentation for this project.
[ Y] I agree to follow the code of conduct that this project follows, as appropriate.
[ Y] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Forge Version:
6.0.0-beta.45

Electron Version:
11.1.1

Operating System:
macOS 11.0.1

Last Known Working Electron Forge version::
6.0.0-beta.45

Expected Behavior

not used ts file don't compiled into renderer/main_window/index.js
Actual Behavior

I just added test.ts,it's not used. but it has compiled  to render/main_window/ index.js.whether it's development mode or production mode.
I hope it don't compiled  to render/main_window/ index.js
How do I do it

To Reproduce

Additional Information
<!--
Add any other context about the problem here.

For example:
* Console output when you run your `electron-forge` command with the environment variable
  `DEBUG=electron-forge:*`. (Instructions on how to do so
  [here](https://www.npmjs.com/package/debug#usage)). Please include the stack trace if
  one exists.
* Command line arguments you are passing to `electron-forge` (e.g.,
  `electron-forge make --not-a-real-flag`)
* The `config.forge` data in `package.json` or `forge.config.js` in use
* A failing minimal testcase (with a link to the code) or detailed steps to reproduce the problem.
  Using `electron-forge init` is a good starting point, if that is not the source of your problem.

This is more of a Webpack question rather than an Electron Forge specific question.


[Error] could not compile rastra. This function takes 7 arguments but 6 arguments were supplied

Hi, I'm trying to check this project but I'm getting the followging error while compiling with cargo build.
warning: unused import: `LE`
  --> src/main.rs:11:28
   |
11 | use bedrockrs::core::int::{LE, VAR};
   |                            ^^
   |
   = note: `#[warn(unused_imports)]` on by default

error[E0061]: this function takes 7 arguments but 6 arguments were supplied
  --> src/main.rs:48:24
   |
48 |     let mut listener = listener::Listener::new_raknet(
   |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
51 |         100,
   |         --- argument #3 of type `std::string::String` is missing
   |
note: associated function defined here
  --> /home/eptadot/.cargo/git/checkouts/bedrockrs-cdc582742ae1671f/b3baa1d/crates/proto/src/listener.rs:23:18
   |
23 |     pub async fn new_raknet(
   |                  ^^^^^^^^^^
help: provide the argument
   |
48 ~     let mut listener = listener::Listener::new_raknet(_config.display_name, _config.display_sub_name, /* std::string::String */, 0, 100, SocketAddr::V4(SocketAddrV4::new(
49 +             Ipv4Addr::from_str("<IP_ADDRESS>").unwrap(),
50 +             19132,
51 +         )), false)
   |

For more information about this error, try `rustc --explain E0061`.
warning: `rastra` (bin "rastra") generated 1 warning
error: could not compile `rastra` (bin "rastra") due to 1 previous error; 1 warning emitted

Yep RAstra currently doesnt compile, I am trying to fix the mess I created with bedrockrs. It will also have a module called bedrockrs::server, which will lay the foundation for RAstra..


Azure Container App fails to have successful init to a Dapr bindings.azure.blobstorage

Please provide us with the following information:

This issue is a: (mark with an x)

[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
A Container App that is Dapr enabled, and has a bindings.azure.blobstorage component with the Container App Scoped will not sucessfully provision due to an init timeout.
Steps to reproduce

Create a Container App with Ingress enabled in East US 2. My container App is running a .NET webapi with the Dapr.Client nuget package installed, and a single writeblob endpoint on the home controller. (However I don't believe that what is running in the container is relevant to the issue.
Create a simple storage account. And inside the storage account create a container with Public access level Blob
Create an Azure Managed Identity, with the Azure Role Assignments:

Storage Blob Data Contributor on the Resource Group
Contributor on the Resource Group

Add the User assigned identity to the container app.
Enable Dapr, and give the container app an App id, with Protocol HTTP and Log level Debug
Inside the Container Environment, Navigate to Settings -> Dapr components and click add. Create a binding.azure.blobstorage component. that has the following configuration.

name: blob
component type: bindings.azure.blobstorage
version: v1
Metadata

accountName : <storageaccountname>
containerName : <yourblobcontainername>
clientId : UserAssignedIdentityClientId

scope: <yourcontainerapp>

Restart your container app revision.
Allow the provisioning to finish, it will fail and the status will be [x] failed
Navigate to that container app revisions console logs, one of them will read 400 Could not Access Managed Identity
Ok - So managed Identity didn't work. We changed to using storage accounts accountKey in the metadata of the bindings.azure.blobstorage and remove all remnants of the Managed Identity from the resource.
Restart the container again, it will fail and the status will be [x] failed
Navigate to that container app revisions console logs, execute the query below. and look for the Log_s that says  level=fatal msg="process component blob error: init timeout for component blob exceeded after 5s

ContainerAppConsoleLogs_CL
| where RevisionName_s == "[containerRevision]" | where Log_s contains "init"

End Result - No running container App, and Blob storage is not accessible through the Dapr.Client InvokeBinding method.
Expected behavior
I expect Azure Container App to start Up successfully using a managed Identity (or an account key) to initialize a Dapr bindings.azure.blobstorage component.
Actual behavior
Azure container App can not start properly while the Dapr component Blob exists.
Screenshots
n/a
Additional context

Everything was configured via the Portal. No bicep / cli was used.
We also have created a Service Bus Dapr component `s that uses managed Identity and it connects up fine and can send messages

This appears to be due to the dapr Azure Blob Storage binding spec documentation being out of sync with what Azure Container Apps actually supports. Changing the bindings.azure.blobstorage metadata as follows appears to fix the problem:
accountName => storageAccount
accountKey => storageAccessKey
containerName => container

This should be updated to 1.9 please let me know if this issue persists @ceramey1997


[UI-REACT]: Doen't working on Next.JS 15

Describe the bug
App throws random error when using Next.JS 15 and React 19
Expected behavior
Expected to work
Current behavior
Dont work
Steps to Reproduce

Run npx create-next-app@latest and install @tonconnect/ui-react
Project won't start

Environment
It simply doesnt install with React 19, using React 18 and Next 15 - installs but dont work
Additional context
No response

When will the problem be solved?


Sra.extract runs extraction locally

I'm currently trying to run the mapping pipeline on some SRA files. The mapping pipeline appears to be configured to extract these files on the local machine. This means that
a) The process is going very slowly
b) I've been using 4 full cpus on the head node (despite there only being two SRA files??) for nearly 2 hours now.

Thanks. @TomSmithCGAT , can you please have a look? It might be related to you introduction of the SRA module.
Note: SRA.exract should be SRA.extract in PipelineMapping.py?

Note: SRA.exract should be SRA.extract in PipelineMapping.py?

I already fixed this: I’ll push a branch that Tom can work on.
From: Andreas Heger<EMAIL_ADDRESS>Sent: 24 February 2015 17:06
To: CGATOxford/cgat
Cc: Ian Sudbery
Subject: Re: [cgat] Sra.extract runs extraction locally (#151)
Thanks. @TomSmithCGAT https://github.com/TomSmithCGAT , can you please
have a look? It might be related to you introduction of the SRA module.
Note: SRA.exract should be SRA.extract in PipelineMapping.py?
—
Reply to this email directly or view it on GitHub
https://github.com/CGATOxford/cgat/issues/151#issuecomment-75797993.

Okay, I've now pushed a branch fixing_sra with that fix in

Also, because the extraction is done locally, it exacts to a local scratch and then submits to the cluster, which trys to read from the now none existant extracted fastq file.
As I see it, there are three options:

The fastq-dump lines need to be added to the mapping statement in the preprocess stage, rather than actually run at the time of compiling the mapping statement. If this is the case the dump will run each time a mapping is run. This is at least twice, because all mapping runs run the nreads mapper as well as the specified mapper.

The fastqs are dumped at statement compilation time (but please lets run on the cluster), and saved to /ifs/scratch. The only beneift of this over 1 is that it is more in keeping with the current logic.

There is a conversion step that makes a permanent conversion of sra to fastq, saved in the pipeline directory, that can then be used in all down stream mapping tasks: this is the more compute efficient mechanism, but not so space efficient.

The code in the sra module is essentially just a copy of what was previously in PipelineMapping. I don't think I changed the workflow for mapping from .sra files.
My thoughts:

Easy to implement - Just need to change line 472 in PipelineMapping.py
outdir = P.getTempDir() --> outdir = P.getTempDir(/ifs/scratch)

and make Sra.extract return a statement to be added to cmd_preprocess rather than running fastq.dump locally with P.execute().
It does seem very wasteful extracting the files each time a mapper is called though, especially if it's just to count reads!

I'm not sure how this would differ from option 1?

My understanding is that this would need to be implemented in pipeline_mapping.py. Without executing Sra.sneak within the pipeline (i.e outside any decorated functions), I can't see how we can make ruffus  pick up the extracted fastqs for the downstream targets.

Maybe I'm missing something here?

Thanks, @TomSmithCGAT

avoid using /ifs/scratch or similar - use the mechanisms supplied by Pipeline.py. Otherwise your code will not be portable.

disk space is more precious to us than compute.

I think what @IanSudbery means that the extraction is part of the job subscript that is send to the cluster. This is how it used to be. The extract method uses P.execute() which will execute a command locally, i.e. not remotely. You will need to use method 2.
Finally, can you rename Sra.sneak. I am not sure what sneaking means in this context. Typically used is "peek" to look inside a file.
Thanks!

Hi,
The difference between 1 and 2 is that in one, the temporary file is store
on the local scratch space on the node. This is more performant than
storing the files on /ifs/scratch. Indeed so much so that I believe the
fastq mappers actually copy the fastq file to the node before mapping them.
Ian
From: Andreas Heger<EMAIL_ADDRESS>Sent: 26 February 2015 17:04
To: CGATOxford/cgat
Cc: Ian Sudbery
Subject: Re: [cgat] Sra.extract runs extraction locally (#151)
Thanks, @TomSmithCGAT https://github.com/TomSmithCGAT

avoid using /ifs/scratch or similar - use the mechanisms supplied by
Pipeline.py. Otherwise your code will not be portable.

disk space is more precious to us than compute.

I think what @IanSudbery https://github.com/IanSudbery means that the
extraction is part of the job subscript that is send to the cluster. This
is how it used to be. The extract method uses P.execute() which will
execute a command locally, i.e. not remotely. You will need to use method 2.
Finally, can you rename Sra.sneak. I am not sure what sneaking means in
this context. Typically used is "peek" to look inside a file.
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/CGATOxford/cgat/issues/151#issuecomment-76218587.

Indeed. Avoid shared scratch unless absolutely necessary. Almost always use local scratch.

@IanSudbery and @AndreasHeger. Thanks for the clarifications.
I take it from this all I need to do is make Sra.extract() return a statement when called from PipelineMapping to be included in the preprocess portion of the mapping statement. That way the resulting fastqs will be stored on the node scratch where and will be available for the downstream mapping?
I'll rename sneak to peek as well. It looks I was lead astray by the previous comments in PipelineMapping...
"
sneak preview to determine if paired end or single end
P.execute(
"""fastq-dump --split-files --gzip -X 1000
--outdir %(outdir)s %(infile)s""" % locals())
"

Sounds like a suitable solution to me. Do you want me to implement it or
will you?
From: Tom Smith<EMAIL_ADDRESS>Sent: 26 February 2015 17:23
To: CGATOxford/cgat
Cc: Ian Sudbery
Subject: Re: [cgat] Sra.extract runs extraction locally (#151)
@IanSudbery https://github.com/IanSudbery and @AndreasHeger
https://github.com/AndreasHeger. Thanks for the clarifications.
I take it from this all I need to do is make Sra.extract() return a
statement when called from PipelineMapping to be included in the preprocess
portion of the mapping statement. That way the resulting fastqs will be
stored on the node scratch where and will be available for the downstream
mapping?
I'll rename sneak to peek as well. It looks I was lead astray by the
previous comments in PipelineMapping...
"
sneak preview to determine if paired end or single end
P.execute(
"""fastq-dump --split-files --gzip -X 1000
--outdir %(outdir)s %(infile)s""" % locals())
"
—
Reply to this email directly or view it on GitHub
https://github.com/CGATOxford/cgat/issues/151#issuecomment-76222565.[image:
Image removed by sender.]

@IanSudbery I've done it. I'm Just checking it runs OK with one of my .sra files before I push it back

@IanSudbery Another possible issue though. The preprocess statement standardises fastq files to +33 format for the downstream tools which either only accept +33 formatted fastqs (BWA) or default to +33 (Bowtie). Tophat and Tophat2 autodetect format. Not sure about GSNAP, STAR etc.
Should we detect the format from the first 1000 lines within the call to Sra.peek() and then add a call to fastq2fastq if required?

@TomSmithCGAT If the call to sra is added early enough, can we not just use the same process that is used for fastq inputs?

@IanSudbery
Yeah, that's what I did. Sra.peek() now also checks the format of the first fastq file and returns the format along with the fastq names. In PipelineMapping, the format is checked for "Sanger" and a call to fastq2fastq added to the mapping statement if required. The FixSRA branch has been merged back into master.


AboutBox: update copyright, add contributors list

Fixes #9005
New screenshot below.
Old screenshot: screenshot from 2017-05-31 19-43-29

I will try to implement compile-time generation ASAP.

can u give the it a little left margin? The first columns looks too close to the edge.

Screenshot of the latest version. I can't get the margin to work properly so I set the Labels' size flag to expand only and set the HBoxContainer's align to center.

I've done implementing the compile-time generation in '/editor/SCsub'. It will now read 'AUTHORS.md' and generate '/editor/authors.h'. I hope I didn't break anything.
It's still very rough. Please review. Thank you.

Awesome! But wouldn't it be easier to use a regular expression?
\t(.*) that on every line, if it doesn't match then ignore it?

I would add something like
Original Authors:
Juan Linietsky
Ariel Manzur
Development Lead
Juan Linietsky
Project Manager
Remi Verschelde
Core Contributors
Ignacio Roldan (Godot .net)
Thomas Karrofel (GDNative)
Contributors

and so on. And the same in the website.
This should probably help people know who to contact regarding something.

@reduz that should be included in the AUTHORS.md file then so the data can be extracted properly.
cc @akien-mga

The difficulty is defining who are the "Core Contributors" :)

Me, of course.

IMO we should just leave it as original authors, lead, manager and contributors.

Grouping contributors by subject and ordering by number of commits or lines of code may help.

@hubbyist if people want such detailed info they can have a look here https://github.com/godotengine/godot/graphs/contributors

IMO we should just leave it as original authors, lead, manager and contributors.

I agree. While it might not be totally fair to the most involved contributors, defining a limit between what is a "core" or "very involved contributor" and a "normal" or "casual" contributor is very difficult.
For the AUTHORS file I used 10 commits as a limit (so before 10 commits you're not an "author" :)), but of course there are some contributors who did 10 simple commits and from which we never hear anymore, and others who did 10 huge commits that defined a big part of some feature or important bug fixes...
If we want to be slightly fairer to the very active contributors, we could list ordered by number of commits instead of alphabetically - so far I chose not to do this because it might encourage people to increase their number of commits just to up their stats, while we obviously favor quality over quantity (and contributors would get even more annoyed at me asking them to squash commits together :P).

if people want such detailed info they can have a look here https://github.com/godotengine/godot/graphs/contributors

Linking to this in the About dialog for additional info would be good btw.

I'd remove everyone from the about box except the main contributors. Do people really get an ego boost for seeing their name appear? sounds like the wrong reason to want to contribute to the project :)

I'd remove everyone from the about box except the main contributors.

Read above, define "main contributors" in a way that leaves no room for appreciation error and getting people frustrated if they don't make it to that list of VIPs :)

@akien-mga I think you and reduz would easily identify them.  I dont think it can be calculated based on stats, its more subjective.
Also, if people get frustrated because of that, we go back to main point: its the wrong reason to be contributing :)

Having to review the work of all contributors and judge if they are "worthy" of being in the list is a dangerous slope I don't want to tread on. Especially as who we consider today as "core contributors" is different from what we considered 6 months ago, and what we'll consider 6 months from now.
Would people who contributed a lot in 2014 but no longer do be "core contributors"? I'd tend to say no, but then: would we remove from the list people who contribute a lot today and are seen as core contributors, but no longer contribute in 2019?
You shouldn't underestimate the interest that some people may have in a proper attribution and recognition of their work. It's not (only) about ego, it's a fair expectation from someone spending hours contributing to a project pro bono that their work will be acknowledged. Just like it's a fair expectation when you work on a movie or a game that your name will appear in the credits.
Some don't care about it at all, for others it's a strong incentive and they would be less motivated if they see their work as undervalued.

If contribution quality or quantity are not justifiable criteria, then alphabetical order is the best it seems. All other methods will need a very complicated formula to make it explainable I think.

Looks good already, let's merge the current state.

I think the solution would be to list people in the version they contributed.
So if people contributed in the 2014 version they would listed in that one and not in the 2017 version, and thus people who contribute this year should be listed in 3.0 and not in a future version, say 3.1
This way crediting all who deserve credit


Automated cherry pick of #1805: 允许更改openstack存储容量

Cherry pick of #1805 on release/2.10.0.
#1805: 允许更改openstack存储容量

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@64b5c9c). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #1807   +/-   ##
================================================
  Coverage                  ?   7.66%
================================================
  Files                     ?     410
  Lines                     ?   62744
  Branches                  ?       0
================================================
  Hits                      ?    4810
  Misses                    ?   57525
  Partials                  ?     409

Flag
Coverage Δ

#aFlag
7.66% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/storages.go
1.24% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm
/approve


Drop Flink 1.15 and 1.16 support

Fixes #32838 and #32835

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Looks like the last success for the Typescript Tests was last year, if I am reading this right: https://github.com/apache/beam/actions/workflows/typescript_tests.yml?query=branch%3Amaster+is%3Asuccess

LGTM, I created kennknowles#11 to remove a few old version references.

Nice! Love the PR-to-a-PR-branch maneuver. Thank you.


Has this project stagnated?

Hello there! I'm revieweing some controls around alerting/notifying about critical issues and had this project in mind, but it appears that there haven't been any notices for quite some time (nor any code updates here in the repo).
Has BugAlert stagnated?
Thanks!

I think it is 😔


Reintroduce the custom screensaver

fixes #98

Introduce a low cost display
Re-introduce the custom screensaver
Run the custom screensaver 20s after signing if no user action

Did you check with physical nanos? Whether the screensaver goes on after 20s while signing.

Did you check with physical nanos? Whether the screensaver goes on after 20s while signing.

Yes, I did. But if you don't mind, it would be safer if you checked it too.


[Creating new dataset] Not found dataset_info.json

Hi, I am trying to create Toronto Book Corpus. #131
I ran
~/nlp % python nlp-cli test datasets/bookcorpus --save_infos --all_configs
but this doesn't create dataset_info.json and try to use it
INFO:nlp.load:Checking datasets/bookcorpus/bookcorpus.py for additional imports.
INFO:filelock:Lock<PHONE_NUMBER>78640 acquired on datasets/bookcorpus/bookcorpus.py.lock
INFO:nlp.load:Found main folder for dataset datasets/bookcorpus/bookcorpus.py at /home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/datasets/bookcorpus
INFO:nlp.load:Found specific version folder for dataset datasets/bookcorpus/bookcorpus.py at /home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/datasets/bookcorpus/8e84759446cf68d0b0deb3417e60cc331f30a3bbe58843de18a0f48e87d1efd9
INFO:nlp.load:Found script file from datasets/bookcorpus/bookcorpus.py to /home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/datasets/bookcorpus/8e84759446cf68d0b0deb3417e60cc331f30a3bbe58843de18a0f48e87d1efd9/bookcorpus.py
INFO:nlp.load:Couldn't find dataset infos file at datasets/bookcorpus/dataset_infos.json
INFO:nlp.load:Found metadata file for dataset datasets/bookcorpus/bookcorpus.py at /home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/datasets/bookcorpus/8e84759446cf68d0b0deb3417e60cc331f30a3bbe58843de18a0f48e87d1efd9/bookcorpus.json
INFO:filelock:Lock<PHONE_NUMBER>78640 released on datasets/bookcorpus/bookcorpus.py.lock
INFO:nlp.builder:Overwrite dataset info from restored data version.
INFO:nlp.info:Loading Dataset info from /home/yisiang/.cache/huggingface/datasets/book_corpus/plain_text/1.0.0
Traceback (most recent call last):
  File "nlp-cli", line 37, in <module>
    service.run()
  File "/home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/commands/test.py", line 78, in run
    builders.append(builder_cls(name=config.name, data_dir=self._data_dir))
  File "/home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/builder.py", line 610, in __init__
    super(GeneratorBasedBuilder, self).__init__(*args, **kwargs)
  File "/home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/builder.py", line 152, in __init__
    self.info = DatasetInfo.from_directory(self._cache_dir)
  File "/home/yisiang/miniconda3/envs/ml/lib/python3.7/site-packages/nlp/info.py", line 157, in from_directory
    with open(os.path.join(dataset_info_dir, DATASET_INFO_FILENAME), "r") as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/yisiang/.cache/huggingface/datasets/book_corpus/plain_text/1.0.0/dataset_info.json'

btw, ls /home/yisiang/.cache/huggingface/datasets/book_corpus/plain_text/1.0.0/ show me nothing is in the directory.
I have also pushed the script to my fork bookcorpus.py.

I think you can just rm this directory and it should be good :)

@lhoestq - this seems to happen quite often (already the 2nd issue). Can we maybe delete this automatically?

Yes I have an idea of what's going on. I'm sure I can fix that

Hi, I rebase my local copy to fix-empty-cache-dir, and try to run again python nlp-cli test datasets/bookcorpus --save_infos --all_configs.
I got this,
Traceback (most recent call last):
  File "nlp-cli", line 10, in <module>
    from nlp.commands.run_beam import RunBeamCommand
  File "/home/yisiang/nlp/src/nlp/commands/run_beam.py", line 6, in <module>
    import apache_beam as beam
ModuleNotFoundError: No module named 'apache_beam'

And after I installed it. I got this
File "/home/yisiang/nlp/src/nlp/datasets/bookcorpus/aea0bd5142d26df645a8fce23d6110bb95ecb81772bb2a1f29012e329191962c/bookcorpus.py", line 88, in _split_generators
    downloaded_path_or_paths = dl_manager.download_custom(_GDRIVE_FILE_ID, download_file_from_google_drive)
  File "/home/yisiang/nlp/src/nlp/utils/download_manager.py", line 128, in download_custom
    downloaded_path_or_paths = map_nested(url_to_downloaded_path, url_or_urls)
  File "/home/yisiang/nlp/src/nlp/utils/py_utils.py", line 172, in map_nested
    return function(data_struct)
  File "/home/yisiang/nlp/src/nlp/utils/download_manager.py", line 126, in url_to_downloaded_path
    return os.path.join(self._download_config.cache_dir, hash_url_to_filename(url))
  File "/home/yisiang/miniconda3/envs/nlppr/lib/python3.7/posixpath.py", line 80, in join
    a = os.fspath(a)

The problem is when I print self._download_config.cache_dir using pdb, it is None.
Did I miss something ?  Or can you provide a workaround first so I can keep testing my script ?

I'll close this issue because I brings more reports in another issue #249 .


Revisit webviewExternalEndpoint in environment

This PR fixes #118950
@mjbvz my naive attempt to fix this, please have a look and test.

Thanks! This looks good to me. I'll also give it a quick test while working on webview code today


Simple pre-commit settings to maintain parity with rest of the project

Ansible linting is missing for now, as the molecule scenario is throwing errors due to some files being interpreted as playbooks. Fixing the issue without skipping them will take changes to the molecule scenario structure that go beyond the scale of this patch.

IIRC we're considering moving the roles to the ci-framework project. Not sure then if we'll need pre-commit for ansible linting and related.

IIRC we're considering moving the roles to the ci-framework project. Not sure then if we'll need pre-commit for ansible linting and related.

If the code is to be moved directly we should probably try to keep it formatted in a way that is similar to ci-framework, which also has pre-commit.


Git & Windows issue

FYI
In the repo there are at least 4 files that cannot be created on windows (and ruin the git use of the repo as they can't be checked out or in) due to a : (Colon) in the filename. They seem to be checked in accidently.
Example is:
msagljs\website\static\img\undraw_start_building_re_xani.svg:Zone.Identifier

I removed these files. Thank you for pointing out!


Resolve "Add support for Foundry 0.8.x" - [merged]

In GitLab by @Asacolips on May 23, 2021, 11:01
Merges 70-foundry-08x-support -> beta
Closes #70

In GitLab by @Asacolips on May 23, 2021, 11:09
added 1 commit
f1b922ac - Update build script
Compare with previous version

In GitLab by @Asacolips on May 23, 2021, 11:23
mentioned in commit 5cd084e9f968fe0a26c967df5836367b148dec72


Upgrade to VS 2017

WIP: still needs to be verified in VS 2017
cref aspnet/Universe#469

@ryanbrandenburg it looks like tests are failing. I think it's due to a temporary bug in vstest which runs the tests in the wrong working directory. https://github.com/Microsoft/vstest/issues/311 This can usually be worked around by using AppContext.BaseDirectory (netcoreapp) or AppDomain.CurrentDirectory.BaseDirectory (net451) to find test files

superseded by #322


Figure for plotting Pareto frontier (Flops x Perf)

run script, get fig

olmo2.pdf
made changes to achieve look above.

made changes, now looks like:


Tiny refactor

Just to keep consistent with the others.
Signed-off-by: Hu Keping<EMAIL_ADDRESS>

LGTM

LGTM, thanks!


LXD usage with some kind of overlayfs

With LXC I played around with a base image and containers only storing their deltas via overlayfs.
When I updated the base image, all the containers were updated. I think this is a huge profit, as one must no update/manage each container separately.
Is such a constellation also possible with LXD?
THX, Georg

We currently have no plan to support overlayfs due to the various limitations of overlayfs just not fitting with what LXD supports.
We can't stack snapshots properly and then remove some, we can't live migrate or network migrate them, ...
For now we recommend you use btrfs or zfs and in the case of zfs, you can then configure the filesystem to not sync data, giving similar performance to overlayfs.
We may reconsider this at some point when we add per-container storage configuration and once overlayfs has matured a bit more and works properly (thinking of inotify support at least). But that's unlikely to happen in a while.

On Sat, Apr 09, 2016 at 09:19:49AM -0700, Stéphane Graber wrote:

We currently have no plan to support overlayfs due to the various limitations of overlayfs just not fitting with what LXD supports.
We can't stack snapshots properly and then remove some, we can't live migrate or network migrate them, ...
For now we recommend you use btrfs or zfs and in the case of zfs, you can then configure the filesystem to not sync data, giving similar performance to overlayfs.
We may reconsider this at some point when we add per-container storage configuration and once overlayfs has matured a bit more and works properly (thinking of inotify support at least). But that's unlikely to happen in a while.

You could use container-type: "none" when creating things and manage
it all yourself if you really want to use overlayfs, but zfs is
definitely the best option.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/lxc/lxd/issues/1878#issuecomment-207814735


Magazine footer (teaser) isn't showing the link to the subscribe form

Please look into having the Subscribe here link back

Thanks @VarunVAshrit - approved :thumbsup:


Setup Documentation for Automation Manager Droplet

The Automation Manager is the latest name for a Digital Ocean Droplet which currently hosts the following repositories:

https://github.com/Police-Data-Accessibility-Project/health-monitoring
https://github.com/Police-Data-Accessibility-Project/data-sources-mirror
https://github.com/Police-Data-Accessibility-Project/prod-to-dev-migration

Most of the knowledge of how this works exists in my head, which is a dangerous place and also poses the systemic risk of me dropping it in the toilet or something and no one else knowing how this stuff comes together. So documentation needs to be developed and integrated into our overall documentation.
This will probably involve two components:

Information in our Gitbook about the Automation Manager in general
Information in each of the respective Readmes about how they work within the automation manager. Where it is deployed, how often it is triggered, how to verify it is functioning as expected or when it last ran, and so on.

@maxachis thanks—this could be exceedingly simple, just so we have enough breadcrumbs to find the trail!

@josh-chamberlain I created a Gitbook pull request for changes to the Gitbook documentation, referencing Digital Ocean, Droplets, and specifically the Automation Manager droplet. I know you said that I could just merge documentation and reference the merge request, but in this case I'd like a sanity check from you to make sure this is the type of information we want in the Gitbook, and if it's not redundant with anything else.

@maxachis thanks for writing this and running it by! I actually just copied it into the developer resources notion page, digital ocean → droplets. https://www.notion.so/pdap/Digital-Ocean-Hosting-6ca5f9ef9aa04a81a59b080ef55e2233?pvs=4
I think of those notion docs as "internal", for people who need to manage infra. The public docs are more for people who are using PDAP as a service, if that makes sense. I think we could close the gitbook PR now, while still closing this issue! Thank you for that.


Expected/Actual's values are undefined

Describe the bug
After a test fails, a modal is opened with information about expected/actual values but they show as undefined.
To Reproduce
Create a failing test containing expect(input).toHaveValue(value).
The bug doesn't occur when the assertion is using toBe e.g. expect(1).toBe(2).
Expected behavior
It should work in the same way that expect(1).toBe(2) behaves - showing the difference between the 2 values.
Screenshots

Environment

OS: Linux (WSL2 / Windows 10)
VSCode version: 1.70.2
Vitest version: 0.22.1
Vitest plugin version: 0.2.28

Additional context
This is not a bug with the extension, because the data that it receives isn't complete.
We should further investigate why vitest isn't sending the needed data.
// Data received from the websocket using `expect.toHaveValue` - seems incomplete

"pass",
"Error: expect(element).toHaveValue(13372)\n\nExpected the element to have value:\n  13372\nReceived:\n\n",
"expect(element).toHaveValue(13372)\n\nExpected the element to have value:\n  13372\nReceived:\n",
"undefined",
"Error",
"Function<JestExtendError>",
"Function<toString>",

// Data received from the websocket using `expect.toBe` - seems complete

"pass",
"expected '1337' to be '13372' // Object.is equality",
"1337",                    <------------------------------------- missing from the upper example
"13372",                   <------------------------------------- missing from the upper example
"strictEqual",
"AssertionError: expected '1337' to be '13372' // Object.is equality\n
"AssertionError",
"Function<AssertionError>",
"Function<>",
"Function<toString>",

Getting a similar error, expected and actual is undefined but it also shows document is not defined.
Running the test via cli passes without a problem, vitest extension thinks it did not pass. This happens to all of my tests.

I think this was fixed in 0.4.0 at least. The issue is not reproducible anymore.


Error loading npm linked custom library with aot

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Mac OSX, El Capitan
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.24
node: 6.9.2
os: darwin x64
@angular/common: 2.4.1
@angular/compiler: 2.4.1
@angular/core: 2.4.1
@angular/forms: 2.4.1
@angular/http: 2.4.1
@angular/platform-browser: 2.4.1
@angular/platform-browser-dynamic: 2.4.1
@angular/router: 3.4.1
@angular/compiler-cli: 2.4.1

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

From a really fresh angular cli project.
Only adding in app.module.ts :
import { MessageModule } from 'my_lib';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    HttpModule,
    MessageModule.forRoot() // <-- include here
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Adding one of the component in app.component.html
<my-message type="error">This is an error message</my-message>
And running
ng build --aot
The log given by the failure.

Normally this include a stack trace and some more information.

chunk    {0} main.bundle.js, main.bundle.map (main) 1.48 kB {2} [initial] [rendered]
chunk    {1} styles.bundle.css, styles.bundle.map, styles.bundle.map (styles) 1.77 kB {3} [initial] [rendered]
chunk    {2} vendor.bundle.js, vendor.bundle.map (vendor) 1.06 MB [initial] [rendered]
chunk    {3} inline.bundle.js, inline.bundle.map (inline) 0 bytes [entry] [rendered]

ERROR in Error encountered resolving symbol values statically. Calling function 'makeDecorator', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol Injectable in<EMAIL_ADDRESS>resolving symbol OpaqueToken in<EMAIL_ADDRESS>resolving symbol OpaqueToken in<EMAIL_ADDRESS>
ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in '/Users/admin/dev/web-library/ng24/src'
 @ ./src/main.ts 4:0-74
 @ multi main

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '/Users/admin/dev/web-library/ng24/src/$$_gendir' in '/Users/admin/dev/web-library/ng24/node_modules/@angular/core/src/linker'
<EMAIL_ADDRESS>69:15-36 85:15-102
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS> @ ./src/main.ts
 @ multi main

Mention any other details that might be useful.
My message module declare and exports the message component, with inlined css/html.
It's Exported with a forRoot :
export class MessageModule {
  public static forRoot(): ModuleWithProviders {
    return {ngModule: MessageModule, providers: []};
  }
}

my_lib is generated with ngc, with a .metadata.json near each d.ts.
With following tsconfig parameters :
...
    "target": "es5",
    "module": "es2015",
...
  "angularCompilerOptions": {
    "skipTemplateCodegen": true
  }

Thanks! We'll be in touch soon.

Having a very similar issue here with a similar setup.  I'd love to see someone respond to this.

Are tree.

Calling function 'makeDecorator', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function
Where is this makeDecorator function? is it a part of your project?

I had a similar problem and it was caused by a small project which I imported and didn't appear to be prepared for aot yet. The makeDecorator function wasn't part of the project code either.

I have the same problem getting this error. This error is thrown when I try to import a module coming outside my angular-cli root.
E.g. import {TestModule} from '../../../../../../Private/test-share/src/app/test/test.module';

As far as I can tell now, there is definitely a problem with imported modules outside the projects root. When I use yarn link, which creates a symlink, and try to import the module in my project, I get the "Calling function 'makeDecorator'" error. Now if I drag my library into another npm module (e.g. @angular/common) everything works just fine.
This means it is not possible to use self-written libs with angular-cli currently, unless they are already published somewhere. Hope this get fixed soon.

@SebastianSchenk check this one as an example, I had the same issue but this example seems currently working fine.
@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    HttpModule,
    AngularLibExpModule.forRoot()
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

<h1>
  {{title}}:
  {{ 3.23 | roundDown }}

  <cm-display [message]="title"></cm-display>

</h1>

@SebastianSchenk I was having a very similar issue with a feature module I am building under it's own dependency.  With you're hypothesis, I removed my node_modules directory from my feature module before linking it.  After that, everything worked like a charm.
I'm getting a bunch of errors in my feature module since none of it's dependencies are present... but that more or less add to an issue with duplication in the node_modules folder.

@jppellerin I had the same issue, removing node_modules from the feature module fixed it. Thanks for sharing! 👍

It seems like this is a issue caused by Typescript and not by Angular CLI. Typescript has problems resolving dependencies when yarn link or npm link is used, as you can see here #11916 and here #6496. This problem could be solved with Typescript 2.1 (read more here).
For now, I found a good workaround, which doesn't affect the actual code of the library, as it is the case with an empty .forRoot(). Furthermore, you don't have to delete node_modules anymore. Just add a path property with all angular dependencies to the tsconfig file of the Angular CLI project, where you include your library with yarn link or npm link.
Here is my full tsconfig.json:
{
  "compilerOptions": {
    "baseUrl": "",
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": ["es6", "dom"],
    "mapRoot": "./",
    "module": "es6",
    "moduleResolution": "node",
    "outDir": "../dist/out-tsc",
    "sourceMap": true,
    "target": "es5",
    "typeRoots": [
      "../node_modules/@types"
    ],
    "paths": {
      "@angular/common": ["../node_modules/@angular/common"],
      "@angular/compiler": ["../node_modules/@angular/compiler"],
      "@angular/core": ["../node_modules/@angular/core"],
      "@angular/forms": ["../node_modules/@angular/forms"],
      "@angular/platform-browser": ["../node_modules/@angular/platform-browser"],
      "@angular/platform-browser-dynamic": ["../node_modules/@angular/platform-browser-dynamic"],
      "@angular/router": ["../node_modules/@angular/router"],
      "@angular/http": ["../node_modules/@angular/http"]
    }
  }
}

Closing as it has been answered. Great writeup and workaround by @SebastianSchenk !

I edited the title and added the FAQ label to make it easier for people having the same problem to find this.

@SebastianSchenk perhaps worth noting: Your solution (which resolved this issue for me - a million thanks) can be rewritten as:
paths: {       "@angular/*": ["../node_modules/@angular/*"] }

Hi,
Anybody is albe to explain what is the real cause? I have added that path mapping and it resolves my problem. But I think this is not really a solution as more workaround.
When I create new project using ng new XXXX,  simulate identical setup  All is fine and I dont have a issue.
just for my  existing project.

I wasn't able to resolve it via @SebastianSchenk 's workaround. I have the following error:
Error encountered resolving symbol values statically. Calling function 'makeParamDecorator', function calls are not supported.
I'm using Angular 4.1.3 with Angular-CLI 1.0.2 and Ionic 3.4.2.

The workaround does not work here. As soon as i add the
import { localStorageSync } from 'ngrx-store-localstorage';

AND
StoreModule.forRoot(
      reducers, {
        metaReducers: [
          localStorageSync({
            keys: ['auth', 'customer']})
        ]
      }
    ),
```

It fails with the error above. Adding the modules to tsconfig does not solve the problem. As soon as i save the project it compiles successfully.

This paths: { "@angular/": ["../node_modules/@angular/"] } workaround didn't work for me. Please help :(

Building with aot, using npm link.  I have included paths as above.  However this does not work.
If I remove the node_modules dir from the linked library then this does solv the issue.
The error I get (at runtime) is:
compiler.es5.js:1690 Uncaught Error: Unexpected value 'DataTableModule' imported by the module 'MyModule'. Please add a @NgModule annotation.

Workaround with paths variable have not helped me as well. I am trying to create a factory for my @ngrx reducers
export const reducers = {
  tips: collectionReducer('tips'),
  games: collectionReducer('games'),
  eventTypes: collectionReducer('eventTypes'),
}

ERROR in Error: Error encountered resolving symbol values statically. Calling function 'collectionReducer', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol gamesReducer in .....

I've encountered this error when having a dependency installed from the local file directory. NPM5 creates a symlink which doesn't seem to want to play nice with the AOT compiler. I solved it by downgrading to NPM3 with npm install -g npm@3 which will by default install the dependency simulating an install from NPM, and use the package.json and .npmignore files. Alternatively, you may want to try something like the npm package npm install-local https://www.npmjs.com/package/install-local.
Hopefully, this helps someone else down the road.

It looks like npm@5 intentionally broke this: https://github.com/npm/npm/pull/15900

@Polyergic So what would be the fix now? I'm struggling...

@chrillewoodz, for the time being I'm both avoiding file: deps and avoiding AOT, and hoping at least AOT is fixed before I need the performance.  Our internal deps are on our private github, which npm seems to handle correctly, it just makes some debugging tedious.  If you need AOT now, AFAIK you can either just copy them into your tree or try to make them appear as git submodules.

just a note, this "paths" needs to be added to your tsconfig.json on your app , not your library folder, in case you are building a custom module.
SebastianSchenk answer works for me.

SebastianSchenk's answer does not work for me unfortunately. I am on v6.0.0 of everything. The error I am getting is

ERROR in ../@nims/ngutils/lib/collapsible-fieldset/collapsible-fieldset.component.ts(13,2): Error during template compile of 'CollapsibleFieldsetComponent'
Function calls are not supported in decorators but 'ɵmakeDecorator' was called in 'Component'
'Component' calls 'ɵmakeDecorator'.

I am not using npm link per se, but lerna, which internally I think does pretty much the same thing. This error occurs even with the --preserve-symlinks option to ng build, which at one point was suggested as a solution (https://github.com/angular/angular-cli/issues/7097).
The component that it is complaining about is very simple. It just has a couple of @Input() properties and a short template. Looking at the component.js or component.metadata.json reveals nothing obvious.

@rtm
Can you create a minimal repro of your issue?

@alexzuza Thanks for following up, but this problem magically solved itself, no idea how.

I'm still getting the problem even after trying the suggestion from @SebastianSchenk.

ERROR in ../app/src/components/live-button/live-button.component.ts(4,2): Error during template compile of 'LiveButtonComponent'
Function calls are not supported in decorators but 'ɵmakeDecorator' was called in 'Component'
'Component' calls 'ɵmakeDecorator'.

Unfortunately, it's not easy to create a minimal repro of the issue.
It's an Angular CLI project using components from node_modules.

So maybe it's a VS Code thing or npm thing, I don't know, but somehow the file paths to our symlink'ed modules had their direct paths added (../../../patient/node_modules/*). We spent quite awhile trying to hunt down this issue, and apparently an automated process re-wrote the file paths in app.module.ts.
SHOULD BE:
import { BrowserModule } 		from '@angular/platform-browser';
import { NgModule } 			from '@angular/core';
import { RouterModule, Routes } 	from '@angular/router';
import { HttpClientModule } 		from '@angular/common/http';
import { BrowserAnimationsModule }	from '@angular/platform-browser/animations';
import { FlexLayoutModule } 		from '@angular/flex-layout';
import { FormsModule }			from '@angular/forms';

OVERWRITTEN FILE PATHS:
import { BrowserModule } 		from '../../../patient/node_modules/@angular/platform-browser';
import { NgModule } 			from '../../../patient/node_modules/@angular/core';
import { RouterModule, Routes } 	from '../../../patient/node_modules/@angular/router';
import { HttpClientModule } 		from '../../../patient/node_modules/@angular/common/http';
import { BrowserAnimationsModule }	from '../../../patient/node_modules/@angular/platform-browser/animations';
import { FlexLayoutModule } 		from '../../../patient/node_modules/@angular/flex-layout';
import { FormsModule }			from '../../../patient/node_modules/@angular/forms';

For my case it is
"@angular/*": ["./node_modules/@angular/*"]

instead of
"@angular/*": ["../node_modules/@angular/*"]

in tsconfig.json. Then it works. 💯


Run in Node.js

Currently there is a problem with the global object dependency that requires a hack to get Magic Sandbox to generate a string in a Node.js environment.
This is the workaround:
const magicSandbox = require('magic-sandbox')

module.exports = (content, files, origin) => {
  const oldWindow = global.window
  global.window = {
    location: {
      origin
    }
  }

  const html = magicSandbox(content, files)

  global.window = oldWindow

  return html
}

It would be great if this workaround were not necessary, and the global object was gracefully handled bu magic-sandbox in a Node.js environment.

Ran into this again just now.

Proposed fix - Line 144:
  template = "<script>(function(){\n    window.onerror = function(msg, url, lineNumber) {\n      window.parent.postMessage({type: \"runtime-error\", lineNumber:(lineNumber-" + lines + "), message:msg}, \"" + (this.window ? this.window.location.origin : '') + "\")\n      //console.debug('blockbuilder editor error on line: ' + (lineNumber-" + lines + "))\n    }\n  })()</script>" + template;


Automatically build NCA container and push it to a public registry

GitHub's ghcr.io provides 500MB storage for free

Initially let's have a new GitHub Actions flow, triggered manually, that runs a docker build followed by a docker push to the IBM GitHub registry at https://github.com/orgs/IBM/packages (docker://ghcr.io/IBM). If we do not have permissions to write into the IBM registry, we can use the registry at docker://ghcr.io/shift-left-netconfig
We should think how to manage image versions and probably link it somehow to NCA release numbers (which we don't have yet).

See https://docs.github.com/en/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions

Done


client: fix Windows builds

The library currently cannot be built for Windows due to a typo in the Windows-specific code. This fixes the issue.

Oops, thanks!


New version: Ablaze.Floorp version 11.1.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115311&drop=dogfoodAlpha

@wingetbot run


reCAPTCHA v3 score very low

Description
I am running a web app that launches the puppeteer-real-browser instance on demand, i.e. when an API endpoint is hit. The puppeteer should then sign in to a web app that uses CAPTCHAs to protect their sign in page.
I use an extension to solve v2 CAPTCHAs (Capsolver), which does a good job most of the time. But even when it solves it, and I am able to click on the "Log in" button, I get back an error from the web app's API, something like "captcha incorrect"
I suspect it has something to do with the browser's reCAPTCHA v3 score being very low - almost always 0.1 when I check.
What can I do to improve this?
This seems valid for both Docker and local executions.
Full steps to reproduce the issue
Here is how I launch the browser:
    const { browser, page } = await connect(this.getBrowserOptions());

    // Method to retrieve browser launch options
    private getBrowserOptions(): Options {
        const extensionPath = path.join(process.cwd(), 'capsolver', `capsolver_extension_${this.proxyIndex}`);
        if (!fs.existsSync(extensionPath)) {
            throw new Error(`Directory does not exist: ${extensionPath}`);
        }
        if (!fs.existsSync(this.userDataDir)) {
            fs.mkdirSync(this.userDataDir);
        }
        const options: Options = {
            headless: false,
            disableXvfb: false,
            turnstile: true,
            connectOption: {
                defaultViewport: null,
            },
            customConfig: {
                userDataDir: this.userDataDir,
            },
            args: [`--disable-extensions-except=${extensionPath}`, `--load-extension=${extensionPath}`],
        };
        if (this.proxyIndex > 0) {
            const proxyParts = this.proxies[this.proxyIndex - 1].split(':');
            options.proxy = {
                host: proxyParts[0],
                port: parseInt(proxyParts[1]),
                username: proxyParts[2],
                password: proxyParts[3],
            };
        }
        return options;
    }

Issue Type
Performance, Support
Operating System
Linux, Mac OS
Do you use Docker?
I don't use Docker

same issue here

same, recaptcha seems impossible to bypass at a high rate this days, I've tested a lot of proxies

@ottodriver @swanilla are you guys using recaptcha solvers?

@ottodriver @swanilla are you guys using recaptcha solvers?

I use an injected Chrome extension (Capsolver) as part of my browser instance, which seems to operate fine for the v2 reCAPTCHA, but it does not take care of the v3.

Same issue here -- the --user-data-dir argument used to result in better Recaptcha scores earlier, however lately that's also not helping.

have anyone try setting turnstile to false?

Any updates ?, I had the same issue using a similar config

Solved with domestic proxies in my case

Any updates ?, I had the same issue using a similar config

Solved with domestic proxies in my case

By domestic proxies, do you mean residential proxies within your own country? Which proxy service are you using?

https://github.com/ZFC-Digital/puppeteer-real-browser?tab=readme-ov-file#why-cant-i-pass-recaptcha-v3

Any updates ?, I had the same issue using a similar config

Solved with domestic proxies in my case

By domestic proxies, do you mean residential proxies within your own country? Which proxy service are you using?

Not my own country, the target site country. I'm using DI.

@mdervisaygan since you closed this topic but there is no solution provided. Can you tell us what needs to be done?

As clearly stated in the readme file, recaptcha v3 checks browser cookies and gives low scores to browsers that have no history with Google.
This is also clearly discussed in the stackoverflow link in the readme file. You can log in to a Google account and use it.
I can't offer a solution for every issue. I cannot add a built-in Google login module. Some topics need to be searched by people who dislike my comments, hate research and expect everything ready. I clearly added the cause and solution to this problem in the readme file, that's all I can do. I try to spend time on open source projects in my limited time, but when I do, I still get dislikes and requests for solutions even though I have posted the problem and the solution. Please read the link I provided. Everything about the problem is written there.
I hope this long and repetitive explanation answers your questions.
Translated with DeepL.com (free version)


Redeferral and deferred stubs

Do not copy the deferred stub tree to the new ParseableFunctionInfo on redeferral, as nested functions may not be deferred in that case. Recompute them instead if necessary.

@rajatd Could you look at this very small fix? Should fix some web issues. (Thanks.)

:shipit:


Nested snippet transformation is not applied to placeholder variable

Type: Bug
I might've come here to report the same issue as https://github.com/microsoft/vscode/issues/112362 but I'm having trouble understanding that thread. This is my snippet:
{
    "label": {
        "prefix": "l",
        "body": [
            "${1:${TM_SELECTED_TEXT/[\\$_]//g}}: ${1:${TM_SELECTED_TEXT}}"
        ],
    }
}

My issue is, when text is selected, the first $1 transform modifies the second $1. To be specific, selecting $foobar and inserting this snippet removes the $ symbol for both placeholders. I expected it to only remove the $ from the first placeholder:

Expected
foo: $foo

Actual
foo: foo

When I insert the snippet and manually type in the placeholder value, it breaks in a different way. The $1 transformation does not appear to have any effect on either placeholder:

Expected
foo: $foo

Actual
$foo: $foo

VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 7 2700X Eight-Core Processor          (16 x 3700)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.93GB (22.18GB free)

Process Argv

Screen Reader
no

VM
0%

atm all placeholders of the same number are mirrored
with priority given to the first occurrence
eg.
${1:abc}${1:123} results in abcabc
not abc123
maybe VSCode would like to look into this
VSCode already supports multi-cursors decently well, so maybe not too hard?
prob edge cases with choice Placeholders tho

You snippet misses the explicit $, this is how it works (notice the \\$)
"label": {
		"prefix": "l",
		"body": [
			"${1:${TM_SELECTED_TEXT/[\\$_]//g}}: \\$${1:${TM_SELECTED_TEXT}}"
		],
	},

@jrieken that is not what he's asking for
and escaping is not required. since the $ is not followed by any valid snippet syntax.
he wants to programmatically remove $ and _ from the first occurence, but not the second
I suggest using the tabstop transform syntax ${1/regex/format/flags}
${1/[$_]//g}: ${1:${TM_SELECTED_TEXT}}


LINQ to XML consolidation

@dotnet/docs if possible, try to avoid global changes such as https://github.com/dotnet/docs/pull/18724 from touching the LINQ content on the C# and VB folders. Otherwise, it takes a while for me to resolve the merge conflicts since this PR deletes a lot of that content.

@jameshkramer we still have to remove these entries from the C# and VB TOCs correct?
@BillWagner @gewarren do you know if there's a tool to order the entries in the redirect file? I remember I did that once but not sure if I still have the script that I used.

@mairaw @BillWagner @gewarren
I have no plans to alter the TOCs for the C# and VB sections. Instead, a user is redirected to the merged article if he/she selects an article that has been merged and removed. You can try it out here: https://review.docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/linq/?branch=linq-to-xml.
Maira, what did you have in mind for ordering the redirection entries? I have already ordered the C# and VB redirects alphabetically by target. I did this so it would be fairly easy to find all the articles that are redirected to a particular target.
Does anyone want me to rebase linq-to-xml onto the latest master? I would be happy to try, though I understand that this might be something that you should control.

@jameshkramer that file is typically sorted by source_path, so it would be easier to diff if we introduced any bad changes if it had that same sorting as before. I once ran a tool to do that and I believe there are some scripts available to do that.
For TOC, I think we should remove those entries from the C# and VB TOC but I'll let @gewarren and @BillWagner to decide here.

And I've already merged master into this branch, so we're good. No need to rebase.

@billwagner @gewarren @mairaw @tfosmark @marteeleigh
I agree, the ideal would be a sorting tool so that we could sort and compare the before and after redirection files.
I could restore the prior order but the prior order for the redirection entries I added was chronological (the order in which articles were merged), not alphabetical. As for the entries that were already there before this project: I left them in place except the ones for the C# parent node articles that had already been removed. I merged these redirections with the ones that I added for this project, and they are sorted along with the others, alphabetically by target.
It is fine with me to let Genevieve and Bill decide about the C# and VB TOCs. On this issue, I would like to defend myself a bit: what I implemented is (with minor changes) what I proposed in the design document that I attached to the user story back in November. I really did my best to satisfy the needs of this project, and to avoid surprises and late changes.
Jim

You can sort the redirection file using the Docs Authoring Pack: https://review.docs.microsoft.com/en-us/help/contribute/docs-authoring/sort-redirects?branch=master#summary.

And yes, I think we should remove the entries from the C# and VB TOCs in favor of the Standard TOC. In general we don't have more than one TOC entry per article.

I'd be happy to sort and compare two redirection files to more clearly show the changes I made, but at this point I'm not sure which two redirection files to compare. That is, I don't know which commits to take the files from. Maira?
@mairaw @gewarren @BillWagner

Thanks @gewarren, that was easy 😉
@jameshkramer so I think the only thing left is the removal of the TOC entries

Here is what I understand from this: if a file has an name/href in the C# or VB TOC, that name/href should be removed from the TOC (that will include all the files under the LINQ to XML node and, I think, a few others).
Is that right?
@mairaw @gewarren @BillWagner

Well, this work was supposed to just move the entire LINQ to XML node, so I'd just remove those two nodes from the C# and VB TOCs.

Consider https://github.com/dotnet/docs/issues/20270#issuecomment-680032603 before merging to avoid the need of double redirections later.

I'm leaving this as ready for review. The only warnings are about some missing descriptions. Perhaps they were added to the current version of the files now. @jameshkramer not sure if you have one more cycle to spare and copy/add the missing descriptions?

Note: At some point these will need to move to the new fundamentals section. Doing that later will result in double redirection.
Pinging @BillWagner to confirm if this LINQ section is in the plan for the fundamentals sections.

@mairaw, yes, I'll fix these.
Jim

LINQ is certainly fundamental content. If there's a better location for this @BillWagner, please let us know. I agree that it would be easier not have to move this content twice. But also merge conflicts are getting complicated, so I'd like to merge this content soon.

In time, this will end up in "fundamentals".  That said, I agree with @mairaw that this is a huge improvement, and the longer we wait the more merge conflicts we'll have with this PR.
Let's :shipit: as soon as the merge conflicts are fixed (again). I've approved it @mairaw


h5py import error

The version h5py==2.7.1 leads to an import error on Ubuntu 16.04  Python 3.7.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/<username>/programs/anaconda3/envs/python3.7/lib/python3.7/site-packages/h5py/__init__.py", line 36, in <module>
    from ._conv import register_converters as _register_converters
  File "h5py/_conv.pyx", line 1, in init h5py._conv
  File "h5py/h5r.pyx", line 1, in init h5py.h5r
  File "h5py/_objects.pyx", line 1, in init h5py._objects
ImportError: /home/<username>/programs/anaconda3/envs/python3.7/lib/python3.7/site-packages/h5py/defs.cpython-37m-x86_64-linux-gnu.so: undefined symbol: H5Ovisit_by_name```

Could it be that Python 3.6. is required?

The version h5py==2.7.1 leads to an import error on Ubuntu 16.04 Python 3.7.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/<username>/programs/anaconda3/envs/python3.7/lib/python3.7/site-packages/h5py/__init__.py", line 36, in <module>
    from ._conv import register_converters as _register_converters
  File "h5py/_conv.pyx", line 1, in init h5py._conv
  File "h5py/h5r.pyx", line 1, in init h5py.h5r
  File "h5py/_objects.pyx", line 1, in init h5py._objects
ImportError: /home/<username>/programs/anaconda3/envs/python3.7/lib/python3.7/site-packages/h5py/defs.cpython-37m-x86_64-linux-gnu.so: undefined symbol: H5Ovisit_by_name```

Could it be that Python 3.6. is required?

As described in the requirements section of the readme, we've tested the repository with python 3.5. However, I don't know if thats the reason for your error. You might try a different version of h5py. As far as I remember, we ran into issues with h5py as well and thus had to specify this version.

Thanks. I will try it.


Lib code is outdated?

the lib is really outdated and we need to remove leaderboard and useless stuff that uses cpu for no reason ?and the lib protocol/packet is really outdated we need to update them from https://github.com/ClitherProject/Slither.io-Protocol/blob/master/Protocol.md
for example: the cords position misses the players alot when the user is moving alot is it really possible to make it like bagar.io?

Mayed my paypal is setup check you freelancer for ban message

@kurama129 ok wait.

@kurama129 ban said that you never talked to him so please cut this off i already got a team i no longer need u

I did talk with him I just want you to unrat me

@mayed505 can you do that

I deleted the filesame from my computerror now I don't have them so unrat me

If you want me to do my work then unrat me

hahaha

good job mayed

@Wartoz thanks i did rat him since we met since i dont trust him releasing my files to public if he did that i will release all his passwords and personal information :)

@kurama129 like i said i dont need your freakin money i already got a team which are better than you and never scams me what i can say we will release cellcraft.io bots i wont go into detail alot.

 Just Saying even you copied the files to usb thinking ur smart the rat will stay in the USB. Just Saying Stop Fighting i came here to ask for the issue not to fight with out and you keep making stories when paying the freelancer which you got me in trouble with him because of you.

I didn't leak files so why leak mine

And also itwigx is betraying you he's asking for files

Just saying didn't  mean to annoy you

Is there anyway that we could solve this

@kurama129 reply on skype and will sort this out..

@kurama129 i didnt leak any files to anyone its safe on my hard drive

Give you skype I'd I've got new skype

Mayed can you give so I caneed add you

We can sort this out

Added mayed </3 now accepting let's sort this out or send a mail to mewok999@Gmail. Com with id

We can sort out this thing so don't leak :) plz

WTF ?

@mayed505 did u really ratted kurama129?

@MinersMC Yea.... He threatened me to leak my bot script that i worked hard on it he started this drama on github....

did he leak it

@mayed505 wew. glad that i use mac. No Infections such as RAT lel

@MinersMC Use a java rat or a rat for macs. A person with a mac can rat another mac


Vulkan Clustered: TAA on a transparent viewport causes the viewport to turn opaque

Godot version
4.0.beta7
System information
Fedora 36, Vulkan Forward Plus, AMD Radeon RX 6900 XT
Issue description
When enabling temporal antialiasing, the viewport becomes opaque if it's currently transparent.
This does not occur with FXAA and MSAA, both of which support transparent viewports (with some visible artifacts though).

TAA disabled
TAA enabled

If it's not possible to support TAA on transparent viewports, I suggest making the transparent viewport property take priority (so it disables TAA), and print a warning if both TAA and transparent viewport are enabled.
Steps to reproduce

Enable Display > Window > Size > Transparent, Display > Window > Per Pixel Transparency > Allowed and Rendering > Transparent Background in the advanced Project Settings.
Notice how the editor 3D viewport (and the running project) features transparency.
Enable Use TAA in the Project Settings.
Notice how the editor 3D viewport (and the running project) loses transparency.

Minimal reproduction project
test_taa_transparent_viewport.zip

I can confirm this in case it's needed. Happened to me to just yesterday in beta17 win 10 with a subviewport.

From a brief look into it it seems like the TAA resolve step intentionally ignores the alpha component as it resolves the color, tonemapping, history, etc. It seems taking alpha into account would also expand the memory used during execution.
There is no obvious solution as to how to extend this in the shader as it'd need to use a separate path for mixing the alpha (to avoid tonemapping) and would probably need another variant of the shader to not cause a performance impact when transparent output isn't necessary (which is the more common use case).
Adding a warning and disabling TAA for this use case might be the more reasonable approach here.

Also seems to happen with FSR 2. FSR 1 works properly

FSR 1.0 with scale less than 1 also turns background to opaque.
This is my system info:
Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 (NVIDIA; <IP_ADDRESS>61) - AMD Ryzen 9 7900X 12-Core Processor (24 Threads)


Protocol "https:" not supported. Expected "http:"

Getting this error when I run:
npm install angular-carousel
Can someone help me here?

works here, which npm version/os do you have ?
$ npm install angular-carousel
<EMAIL_ADDRESS>/Users/juju/Desktop/tmp/carousel
└──<EMAIL_ADDRESS>extraneous

npm WARN EPACKAGEJSON<EMAIL_ADDRESS>No description
npm WARN EPACKAGEJSON<EMAIL_ADDRESS>No repository field.

I am sorry.. It was totally my fault..
I had previous SSL proxy settings made on NPM..
For future reference:
npm config rm proxy
npm config rm https-proxy
This worked for me.

all good :+1:


Add test coverage for secure routes utilising SslContextParameters

Prompted by this question in relation to wildfly-camel

Camel allows transport security by first defining an 'sslContextParametersRef' then using it in URI:
<route><from uri="jetty:https://localhost:8080/early?sslContextParametersRef=sslContextParameters"/>
This usage of an 'sslContextParameters' argument is different than the way EAP makes use of SSL.  Is this technique still valid with Camel-on-EAP?

Example of sslContextParams with a secure Netty route here.


"Enabling hide enteries already present in library" Option causes infinite loading in source extension.

Steps to reproduce
"Hiding enteries already prsent in library" Option in browser setting option causes this error.
Expected behavior
Browser should be hiding any enteries which are present in any libraries.
Actual behavior
It causes the infinite loading issue in extension from an entry is placed into any library.
Crash logs
No response
Aniyomi version
Aniyomi Preview r6678
Android version
Android 13
Device
Infinix gt10pro
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

There was a similar issue with tachiyomi.
https://github.com/tachiyomiorg/tachiyomi/issues/9924
But It gets fixed in tachiyomi preview r6132.

There was a similar issue with tachiyomi.
tachiyomiorg#9924
But It gets fixed in tachiyomi preview r6132.


[wasi-common] Clean up fd_filestat_get implementation

This commit does 4 things:

Adds yanix::file::fstat, a wrapper around libc::fstat.
It essentially reverts 89fbde2 for Unix hosts -- in other words,
it brings back the use of fstat to obtain libc::stat from a
file descriptor, rather than relying on std::fs::Metadata. This
way, we reuse host_impl::filestat_from_nix in
hostcalls_impl::fd_filestat_get implementation rather than
unnecessarily duplicate code for converting filestats into
__wasi_filestat_t.
Moves crate::helpers::systemtime_to_timestamp to Windows host_impl
module. It does the same thing with helpers which assist in converting
std::fs::Metadata into __wasi_filestat_t. This should retain symmetry
between *nix and Windows impls.
Makes timestamp conversions in host_impl::filestat_from_nix fallible.

Concerning the fstat change, it seems like we could plausibly go the other way too -- use fs::metadata and File::metadata and get to one filestat conversion function by removing filestat_from_nix. Are there any disadvantages to doing it this way?

Concerning the fstat change, it seems like we could plausibly go the other way too -- use fs::metadata and File::metadata and get to one filestat conversion function by removing filestat_from_nix. Are there any disadvantages to doing it this way?

Hmm, yep, that's also a possibility, and I'm happy to go either way. The only disadvantage I currently see is the fact that, on Unix, we will need two syscalls: File::metadata followed by get_socket_type when using std::fs::Metadata to replicate current functionality of fstat + filestat_from_nix since std::fs::Metadata cannot tell us what type of a socket we are. But I'm not sure whether this is a valid concern, or premature optimisation on my part ;-)

Oh, and I forgot that for path_filestat_get we can't use std::fs::Metadata since, in libstd we have no way of calling an equivalent of fstatat; that is, a combo of dirfd and relative path. So in the end I guess we won't be able to get rid of filestat_from_nix and operate on Metadata struct in an easy way (or at all)?

I'm gonna go ahead and merge this one. As usual, if I missed anything, please feel free to open an issue, etc. :-)


chore: improve mocks lib

This PR merges test_utils and mocks into a folder, then renaming to mack_apps and mock_queriers.
Besides, it also improves x/posts and x/reports to have MockQueries struct collecting all mock functions as other modules.

@manu0466 Great thought, that makes more sense.


bug fix

OpenBullet2.Native Worldlists.xaml Text="{Binding SearchString}"  Need Text="{Binding SearchString, UpdateSourceTrigger=PropertyChanged}" and delete Click="Search"(Delete method Search)

OpenBullet2.Native Worldlists.xaml.cs position 137 FileName = path,  Need FileName = path.Replace("\", "/"),

In 0.3.1 there is a bug - telegram hit output not working even if i manually type telegram api it's vanish after saving the settings of runner  (that's why i used to use 0.2.5 but it got lost in void) 😔

@Goku001q you keep writing on other people's issues / pull requests. This is NOT the place. You need to visit this link and click on the button next to Bug Report, then file YOUR OWN bug report.


Adding reranker API

I wanted to use the reranker from Cohere and noticed that the functionality was missing from the JS/TS package (it's only available through Python). I copied the descriptions from your website (same link).
I'm not a TypeScript developer so please test it. That said, I added a test and it seemed to work fine.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi, thanks for this contribution! We are about to switch this repository to be automatically generated from our api specs in #90 . This will mean it is always up to date with our API. As such we are closing existing PRs since they will likely not be compatible with the new changes.


fix: fixed back button to redirect to applications page

added the changes to redirect to application pages instead of going back in the history.
issue: #34431
fixed the navigation to not go back in history
The navigation of the back button used to go back in history. Now it will be redirected to the expected page.
added the test for profile page:

added the tests for settings page:

video:
https://github.com/user-attachments/assets/35a805ec-a579-4571-b4c6-e415f0f5c5f3

Summary by CodeRabbit

New Features

Enhanced navigation for the BackButton in both UserProfile and Settings components, directing users to the applications page and specific workspace pages, respectively.

Bug Fixes

Improved test coverage for BackButton interactions in both UserProfile and Settings components, ensuring correct navigation behavior is verified.

Tests

Expanded test suite for UserProfile and Settings components, incorporating better routing and interaction simulations.

/build-deploy-preview skip-tests=true

@saicharan-zemoso Could you please check and fix the checks that are failing? You will be able to see the errors when you click "Details" for the specific check.

Ok I will check why they are failing

@saicharan-zemoso There are still some failures in prettier and lint checks.

@saicharan-zemoso It's actually not a dot but a single space. If you are using VSCode as your editor, you can install "ESLint" and "Prettier - Code formatter" extensions and that will take care of fixing these errors.

If you're using any other editor, I'm sure there would be a way to get this done automatically on save, you'll just have to search for the same.


fix: 458 handle error format

Addresses #442 and #458
Handles cases where error object is a list instead of a dict.

@jonparrott Do you think this is ready to merge?

Yep, was just waiting on CI.

Thank you.


Fix deadlock during snapshot sync

Committing config logs requires global lock which is taken during snapshot install.
Snapshot install will wait for the commit thread to pause before continuing leading to a deadlock.

Already fixed https://github.com/eBay/NuRaft/pull/426


[Ionic v4] Blank screen when running tabs project on Android without changing code

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
Ionic:

   ionic (Ionic CLI)          : 4.0.1 (/usr/local/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.0
   @angular-devkit/core       : 0.7.0-rc.3
   @angular-devkit/schematics : 0.7.0-rc.3
   @angular/cli               : 6.0.8
   @ionic/ng-toolkit          : 1.0.0
   @ionic/schematics-angular  : 1.0.1

Cordova:

   cordova (Cordova CLI) : 7.1.0
   Cordova Platforms     : android 6.3.0

System:

   ios-deploy : 1.9.2
   ios-sim    : 5.1.0
   NodeJS     : v9.9.0 (/usr/local/bin/node)
   npm        : 6.2.0
   OS         : macOS Sierra
   Xcode      : Xcode 9.2 Build version 9C40b

Environment:

   ANDROID_HOME : not set

Describe the Bug
Unable to build Android app from tabs starter
Steps to Reproduce
Steps to reproduce the behavior:
This works and shows the app running in my browser
ionic start myApp tabs --type=angular
cd myApp/
ionic serve

When running:
ionic cordova run android

With my Android device connected via usb I got a white screen. The console of the Android device gives:
styles.cc30f1d5d0942874a01d.css:1 Failed to load resource: net::ERR_FILE_NOT_FOUND
runtime.5102c7f106242716eaa7.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND
cordova.adc5592093abc0bc2eb2.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND
polyfills.17fd7534d20949996e6f.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND
main.16f37d6c80ab0ae66681.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND
/assets/icon/favicon.png:1 Failed to load resource: net::ERR_FILE_NOT_FOUND

Expected Behavior
To see the tabs app running on the device

same here

I've got the same false.
Post a help in here: https://forum.ionicframework.com/t/blank-page-when-trying-ionic-v4/136761

Found the solution:

cordova-android must be >6.4.0, yours is 6.3.0(just like mine was)
ionic webview must be >2.0.0.beta.2

Yes, upgrade to 6.4.0, it works.
However, some old cordova plugins don't support 6.4.0 well....

@matheusdavidson Great! So basically somehow an old cordova-android version is injected in the package.json during the setup phase of the project when Android is added.

I got the same error, my ionic info:
Ionic:

   ionic (Ionic CLI)          : 4.1.0 (/Users/Marcelo/.npm-global/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.3
   @angular-devkit/core       : 0.7.4
   @angular-devkit/schematics : 0.7.4
   @angular/cli               : 6.1.4
   @ionic/ng-toolkit          : 1.0.7
   @ionic/schematics-angular  : 1.0.5

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : android 7.0.0
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.2, cordova-plugin-ionic-webview 2.1.0, (and 3 other plugins)

System:

   ios-deploy : 1.9.2
   NodeJS     : v10.4.1 (/usr/local/bin/node)
   npm        : 6.1.0
   OS         : macOS High Sierra
   Xcode      : Xcode 9.4.1 Build version 9F2000

Environment:

   ANDROID_HOME : not set

My screen is blank
Error in the console:
The key "viewport-fit" is not recognized and ignored.
vendor.js:69667 Uncaught SyntaxError: Unexpected token function

@copaste, Did you find any solution?

Apparently the problem is with compatibility of asynchronous functions, I'm not sure, but in my case the error is on line 69667 in vendor.js
This corresponds to a util async function of ionic core
I inspected the application from Chrome and found this:
async function attachComponent(delegate, container, component, cssClasses, componentProps) {
...

This function can be found in:
<EMAIL_ADDRESS>
I also did the following test in console:
> var fun = function(){}
< undefined
> fun
< function(){}
> var asyncFun = async function(){}
VM257:1 Uncaught SyntaxError: Unexpected token function  <-------- ERROR

Finally, I checked the browser version:
navigator.userAgent
"Mozilla/5.0 (Linux; Android 6.0.1; SM-G925I Build/MMB29K; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/52.0.2743.98 Mobile Safari/537.36"

Finally I solved the problem by updating the Android System Webview in my Android 6. However, I believe that the ionic code could be transpilated to an previous version of ECMAScript to offer compatibility with previous versions of the Android System Webview, since this is independent of the Android version.
I would like to point out that I did tests with Vanilla Apache Cordova and I did not have problems with the old Android System Webview. Ionic should do the same.

Merging with #15282


Add newtype topic for better library discoverability

I finally found this lib which seems far better than alternatives https://github.com/alexknvl/newtypes , https://github.com/vitorsvieira/dilate , https://github.com/rudogma/scala-supertagged – but i found it accidentally even though I searched actively for ways to get newtypes in scala, adding a newtype, tagged, tagged-types tags might make it easier to discover the lib

@kaishh Great idea! I added the following topics, feel free to let me know if some others might be useful as well.

newtype
scala
tagged
tagged-types


Status & roadmap?

Hi,
First of all, I'd like to thank you for your work, this is fantastic, @Veykril!
It would be great if there was information about the current status of the project, and maybe a roadmap. This would be useful to people who'd like to read the book when it's mostly updated/finished.
This information also would be useful to people who'd like to contribute to the project.
Thanks, again!

Yes I agree, I'll try to compile a list of things that would be nice/are done

Awesome! :)
Maybe you then also could request help in the "help wanted" section of "This week in Rust", if you don't want to implement these updates yourself?

Yes I definitely wanted to ask if the book can be mentioned there, kind of forgot about it 😅. Opened #21 let me know if I missed anything infowise that should be added there still.

Thanks, @Veykril!
Are there any plans to extend the book with information about Procedural Macros?
If you don't plan this yourself, would you welcome contributions from others?
That would be interesting, I think.

Ah yes, I wanted to open an issue about that as well but forgot, thanks for the reminder 😄. I'm definitely interested in adding that as well. I opened #23 for discussion regarding that.


Extra empty package directory

E.g

<EMAIL_ADDRESS>

Huh, weird. I can reproduce on my end, but only in the d3 package. I'm not seeing it elsewhere.


missing quotes in name view [gmsh]

https://github.com/nschloe/meshio/blob/29a2780585205ea92012e2b1aaba9902b07707a1/meshio/gmsh_io.py#L501
should be
fh.write('"{}"\n'.format(name).encode('utf-8'))

Thanks for the report, fixed now.


fix: sha computation of symlinks was failing sometimes

Sometimes linking was failing because we tried to compute the SHA hash of a symlink-file. When computing the hash, we follow the symlink. But since we are symlinking everything at once, and in parallel, the symlinked file is sometimes not yet there.
In that case, the SHA hash computation was failing.
With this PR, we change it so that we always store 000...000 for symlinks.
Conda and mamba 'wait' for the files to be ready and then compute (or find) the hash. We could also do that, but on the other hand the "sha" hash of a symlink doesn't make that much sense anyways.
Thoughts?
ref. https://github.com/prefix-dev/pixi/issues/1309

Note: before, if we had the paths.json, then we would use the SHA hash that is stored in there (which is also not correct if the symlink target file had a prefix replacement).


(PUP-7845) Implement leaf certificate revocation checking

Puppet has always performed chain revocation checking when revocation
checking was enabled, but has never been able to load more than a single
CRL. Because of this Puppet could only be used with a root CA if
revocation checking was desired, and if intermediate CAs were in used
revocation had to be entirely disabled.
This commit sidesteps the issue of loading multiple CRLs by allowing
certificate revocation checking to be performed on the leaf certificate
only. This allows users to revoke certificates with an intermediate CA
that Puppet is managing, which is a definite improvement over not
allowing any revocation checking at all.
For the sake of compatibility certificate_revocation still defaults to
full chain checking; users must opt in to leaf revocation checking.

CLA signed by all contributors.

I need to perform some FR before this gets merged, hold off on merging till that's handled.

I've performed FR on this with mixed results; leaf CRL checking does work if the CRL is present. However my work uncovered another issue in that Puppet can recurse infinitely when trying to fetch the CRL, no CRL is present, and CRL verification is enabled. If the CRL is manually copied in place then revocation checking works This PR can be merged but I'll need to do some follow up work to resolve the recursion issue. I can do that today.

Adding blocked label until we circle back with @adrienthebo on next steps

This ticket should be unblocked. /cc @MosesMendoza @justinstoller


Instance Sizing

An open issue for documenting GKE instance sizing

@adejanovski can you provide some guidance here in line with what's being used for performance testing?
IIRC we were looking at 8-16 vCPUs (leaning towards 16 here) and 64 GB RAM.

Currently we're using e2-highmem-8 (8 vCPUs and 64GB RAM) for perf testing.
e2-highmem-16 (16 vCPUs and 128GB RAM) are also a good fit for larger workloads/density.
General recommendations for running Cassandra in production:

8 to 16 vCPUs
32GB to 128GB RAM (no more than 31GB heap but the rest will be used for offheap memory and file cache)
~2TB of live data per node (not a hard limit, Cassandra can support much more but time to recovery gets fairly high then).

With zero copy streaming in 4.0 (and 10 GbE) I'm curious what the density looks like to match the current time to stream 1-2 TB on 3.11.

Zero copy streaming as it was implemented for 4.0 only works for tables using LCS and requires that there aren't too many vnodes (if at all), which reduces the benefits we can expect from it.
Compaction and repair improvements though should be helpful to handle higher densities. Even without Zero Copy Streaming, I guess the lighter memory footprint of 4.0 should help reducing GC during streaming and make it faster.
It could be interesting to benchmark this specific aspect to compare 4.0 to 3.11 time to recovery.


remove dead link globee.com

Approved

remove from tools also please
https://github.com/monero-project/monero-site/blob/9b562099d0f64c902dc068b7daa472c34fb628ca/resources/tools/index.md?plain=1#L93


Nice output at the end of a test run

It would be nice if there was some brief output at the end of running the tool like:
Number of tests ran: xx
Passed: xx
Failed: xx
So that it is clear that a number of tests have been performed. If there are no failures there is currently nothing in the output and therefore it is unclear if everything went well or no tests were actually run.

See issue #68 ... also Ignored: xx


Running jhipster export-jdl <FILE_NAME> ignores the <FILE_NAME> argument

Overview of the issue

Running jhipster export-jdl <FILE_NAME> ignores the <FILE_NAME> argument and creates an app.jdl file .
Motivation for or Use Case

I was expecting that the file produced would be named  <FILE_NAME>. Its documented at the end of the https://www.jhipster.tech/jdl/getting-started, so it should work.
Reproduce the error

run jhipster export-jdl model-10_29_2019-2.jh, produces app.jdl
Related issues

Yes at https://github.com/jhipster/jhipster-core/issues/362
JHipster Version(s)

Tested with v6.4.1
Browsers and Operating System

Windows 10, WSL Ubuntu

[x] Checking this box is mandatory (this is just to show you read everything)

This is happening because the generator doesn't export to a file when calling JCore. A file must be passed here.


[New Feature]: Write --configure endpoint for management console to set values in the config file

should set a couple of paths potentially and a mandatory github token

/close
un-needed


Update the introductory note on the global Conventions attribute.

Following the inclusion of UGRID-1.0 in CF-1.11 (draft) conventions, we should update the remark concerning the global Conventions attribute. Specifying CF-1.11-draft or later is considered enough.
This pull request addresses issue #68

HI @ChrisBarker-NOAA , Can you check this wording? You've been more involved in the discussion on the CF side. Should we explicitly ask someone else from the CF team to check it as well?

THis looks good to me, except the "draft" part -- as the text says: "as of CF 1.11", I think we can simply use 1.11 -- by definition, they are using the draft if it hasn't been released yet.
@davidhassell: your thoughts?

Hi @ChrisBarker-NOAA, I'm fine with dropping the references to draft. I included those since I noticed that the Overview section of the draft CF-conventions, it is stated:
Files using this version of the CF Conventions must set the NUG defined attribute Conventions to contain the string value "CF-1.11-draft" to identify datasets that conform to these conventions.
So, it seemed to be more accurate at this point in time, but it's probably too detailed and confusing in the long run.

Hi Bert and Chris,
The new text looks good to me. Chris is right, just CF-1.11 is correct, we don't need the "draft" bits.

Good catch -- thanks!


Use inventory links in docs

Documentation

Remove ADTypes documentation
Add external references to ADTypes and SparseConnectivityTracer with the new inventory feature of Documenter v1.3

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.53%. Comparing base (1cc1741) to head (426c190).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #260      +/-   ##
==========================================
- Coverage   95.13%   92.53%   -2.61%
==========================================
  Files          74       16      -58
  Lines        3929     1782    -2147
==========================================
- Hits         3738     1649    -2089
+ Misses        191      133      -58

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

Add external references to ADTypes and SparseConnectivityTracer with the new inventory feature of Documenter v1.3

What did this do?