[Disk Manager] fix idempotency of DeleteImage task

The TestImageServiceCreateImageFromImage nemesis test failed in the pr https://github.com/ydb-platform/nbs/pull/2294
The root cause of the failure are conflicst of requests of tasks with the same id:
disk_manager_stdout_9io07ym4:2024-11-01T18:48:28.881Z   DEBUG   persistence/ydb_logger.go:70    done    {"SYSLOG_IDENTIFIER": "disk-manager", "COMPONENT": "TASK_RUNNER", "REQUEST_ID":
 "TestImageServiceCreateImageFromImage_5", "SYSLOG_IDENTIFIER": "disk-manager", "COMPONENT": "TASK", "TASK_ID": "ab93fb55-4ac7-4bef-bdd1-f96179cd074c", "COMPONENT": "TASK_SCHEDULER",
"COMPONENT": "TASK_SCHEDULER", "COMPONENT": "YDB", "YDB_LOG_NAME": "ydb.table.do", "latency": "23.805079ms", "idempotent": true, "label": "", "attempts": 1, "error": "non-retryable er
ror occurred on attempt No.1 (idempotent=true): Non retriable error, Silent=false: cannot create task with request=\n+TestImageServiceCreateImageFromImage_image1\u0012\u0006zone-a\u00
18\u0001, because task with same id=52d6ef27-045c-4f9e-9cb9-67a3041bcb1d,\n\t\t\t\t but different request=\n+TestImageServiceCreateImageFromImage_image1\u0012\u0006zone-a\u0018\u0001
\ufffd\ufffd\ufffd\u0014 already exists

The scenario was the following:

storage.ImageDeleted marks the image as deleted and after that the runner fails immediately.
The clearDeletedImages task deletes this image from the database.
The next generation of DeleteImage can not find the image in the database here and returns imageMeta with zero size.
This zero value of the image size is used in the request for RetireBaseDisks task. But on the previous generation, this task was already scheduled with nonzero valie of the image size. The confict happens.

Moreover, the errors of parsing protobufs happened in requests to ydb:
disk_manager_stdout_cx60ds6q:2024-11-01T19:21:25.304Z   INFO    storage/storage_ydb_impl.go:1528        finished updating task with id ab93fb55-4ac7-4bef-bdd1-f96179cd074c     {"SYSLO
G_IDENTIFIER": "disk-manager", "COMPONENT": "TASK_RUNNER", "REQUEST_ID": "TestImageServiceCreateImageFromImage_5", "SYSLOG_IDENTIFIER": "disk-manager"}
disk_manager_stdout_cx60ds6q:2024-11-01T19:21:25.311Z   WARN    persistence/ydb_logger.go:74    failed  {"SYSLOG_IDENTIFIER": "disk-manager", "COMPONENT": "TASK_RUNNER", "REQUEST_ID":
 "TestImageServiceCreateImageFromImage_5", "SYSLOG_IDENTIFIER": "disk-manager", "COMPONENT": "YDB", "YDB_LOG_NAME": "ydb.table.do", "latency": "5.862879049s", "idempotent": true, "lab
el": "", "error": "Retriable error, IgnoreRetryLimit=false: failed: query \n\t\t--!syntax_v1\n\t\tpragma TablePathPrefix = \"/Root/disk_manager/recipe/tasks\";\n\t\tdeclare $values as
 List<Struct<\n\t\tid: Utf8,\n\t\tidempotency_key: Utf8,\n\t\taccount_id: Utf8,\n\t\ttask_type: Utf8,\n\t\tregular: Bool,\n\t\tdescription: Utf8,\n\t\tcreated_at: Timestamp,\n\t\tcrea
ted_by: Utf8,\n\t\tmodified_at: Timestamp,\n\t\tgeneration_id: Uint64,\n\t\tstatus: Int64,\n\t\terror_code: Int64,\n\t\terror_message: Utf8,\n\t\terror_silent: Bool,\n\t\terror_detail
s: String,\n\t\tretriable_error_count: Uint64,\n\t\trequest: String,\n\t\tstate: String,\n\t\tmetadata: String,\n\t\tdependencies: String,\n\t\tchanged_state_at: Timestamp,\n\t\tended
_at: Timestamp,\n\t\tlast_host: Utf8,\n\t\tlast_runner: Utf8,\n\t\tzone_id: Utf8,\n\t\testimated_time: Timestamp,\n\t\tdependants: String,\n\t\tpanic_count: Uint64>>;\n\n\t\tupsert in
to tasks\n\t\tselect *\n\t\tfrom AS_TABLE($values)\n\t: connError{node_id:1,address:'dp774es3d0144t8q93pk.auto.internal:9458'}: transport/Internal (code = 13, source error = \"rpc err
or: code = Internal desc = grpc: error while marshaling: string field contains invalid UTF-8\", address: \"dp774es3d0144t8q93pk.auto.internal:9458\", traceID: \"5430dda3-d03e-4a54-941
6-5645a835ff46\") at `github.com/ydb-platform/ydb-go-sdk/v3/internal/conn.(*conn).Invoke(conn.go:347)` at `github.com/ydb-platform/ydb-go-sdk/v3/internal/balancer.(*Balancer).wrapCall
(balancer.go:351)` at `github.com/ydb-platform/ydb-go-sdk/v3/internal/table.(*session).executeDataQuery(session.go:795)` at `github.com/ydb-platform/ydb-go-sdk/v3/internal/table.(*ses
sion).Execute(session.go:748)` at `github.com/ydb-platform/ydb-go-sdk/v3/internal/table.(*transaction).Execute(transaction.go:80)` at `github.com/ydb-platform/ydb-go-sdk/v3/internal/t
able.do.func1(retry.go:53)`", "retryable": true, "code": 13, "deleteSession": true, "version": "3.54.3"}

The reason of this is error_message field of task state. Here we write request in the message, but request in not a valid utf-8 string.

The fix was merged https://github.com/ydb-platform/nbs/pull/2497
Also need to add test that reproduces the bug more regularly. Work in progress


Nested loop UndefVarError

Hey, thanks for the great library!
I'm not sure if this is a bug, but the following code doesn't work for me for no obvious reason:
function logmean(samples, weights)
    logμ = zero(first(samples))
    n = length(samples)
    k = length(logμ)
    @turbo for i in 1:n
        for j in 1:k
            logμ[j] = logμ[j] + weights[i] * log(samples[i][j])
        end
    end
    return logμ
end

logmean([ [ 1.0, 1.0 ], [ 1.0, 1.0 ] ], [ 0.5, 0.5 ])
UndefVarError: i not defined

Stacktrace:
 [1] logmean(samples::Vector{Vector{Float64}}, weights::Vector{Float64})
   @ Main ./In[15]:5
 [2] top-level scope
   @ In[16]:1
 [3] eval
   @ ./boot.jl:360 [inlined]
 [4] include_string(mapexpr::typeof(REPL.softscope), mod::Module, code::String, filename::String)
   @ Base ./loading.jl:1116

The following version works like a charm:
function logmean(samples, weights)
    logμ = zero(first(samples))
    n = length(samples)
    k = length(logμ)
    for i in 1:n
        @turbo for j in 1:k
            logμ[j] = logμ[j] + weights[i] * log(samples[i][j])
        end
    end
    return logμ
end

I thought LoopVectorization.jl should be able to handle nested loops? Or are there some special requirements for that?

It doesn't handle samples::Vector{Vector{Float64}} at the moment.

I see, thanks for the clarifications! Its up to you then to either close this issue or to keep it for the future reference.

I will keep it open for future reference.


Fix saving product description_plaintext

I want to merge this change because it fixes a bug that was clearing description_plaintext field for a product when description was not provided in the ProductUpdate mutation input. After this change description_plaintext will be cleared only when description is sent with an empty value.
Also migration fixing description_plaintext field when description exists was added.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Reported in: https://saleorcommerce.slack.com/archives/C017L12TRJS/p1681388838457649


make edits in README.md

-"to remove" -> "remove"
-"that little bit faster" -> "faster"
-"some other smaller projects" -> "other smaller projects"
-"Have a read of" -> "Read"
-"something that is incorrectly described" -> "something incorrectly described"
-"the need for or dependence on" -> "depending on"
-"content ... provides" -> "contents ... provide"
-"in function format" -> "function formats"

Thanks 👍


[Discussion] Removal of Azure Functions version 2.0.12808

Discussion issue for removal of Azure Functions version 2.0.12808

I just learned about removal of older versions from production environment because of announcements. Where can I find more about how this works and what happens with running applications? Thank you.

@jeffhollan / @dariagrigoriu this is a reasonable documentation ask. @ggailey777 is this something we can track?


Fix pin matrix does not display

Closes #322
Always_promt is by default False, when is True enables to shows always the pin matrix when is required.

coverage: 93.463%. remained the same
when pulling a2d9716564b0624518739c513cfb186481fa39a6 on fix_missing_pin_matrix
into c21e96cef466706c718e0042901a86737e066ee0 on master.


Login Forgot Password issue

This issue is occurring in FightPandemics page, web and mobile,
and it is occurring in chrome, safari and firefox..
1)Click Login
2)Click Forgot password
3)Observe..
4)The page is blank

Closing this as this will be solved when #651 is merged. The page is blank because it does not exist yet.


Fix formatting from external contribution

Task/Issue URL: https://app.asana.com/0/1125189844152671/1208318107615954/f
Description
Fixes formatting issues
Steps to test this PR
CI passes

#5030  👈
develop

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

Join @marcosholgado and the rest of your teammates on  Graphite


Fixed an issue where the focus was moving to some hidden link showing

Fixed an issue where the focus was moving to some hidden link showing on left panel on documentation page.
Version for V0 : https://github.com/Microsoft/pxt/pull/2923
Related issue : https://github.com/Microsoft/pxt/issues/2795

I managed to support those special cases where there is no link for the header of a menu, but that the markdown parser was still generating a href tag.

Important note
If this PR is approved, I will have to do the same for the master accessibility features.

@veler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Add tag support

This solves the "in which folder to I sort my files" problem. In the long run we will have a large amount of catalogs and the folder concept will reach it limits. It would be nice to have tags to group catalogs into locations, projects, topics and other categories.

How does this work in combination with the new aliases?

Tagged catalogs still need a name. And sometimes (e.g. in case of the HLL), the name is ugly (e.g. an id) and we need a prettier one: the alias.

How does this work in combination with Nexus.Federation?

Aliases cannot be defined from within the sub Nexus to be displayed high in the hierarchy in the main Nexus because currently aliases must be absolute paths beginning with a forward slash.
But main Nexus could define a special plugin which provides all these aliases. Maybe via .json file or web page to let users configure it easily. But this is no important feature right now.
Tags, on the other hand, will work for the main Nexus as well. But a big problem with tags is that catalogs are being loaded lazily and so many catalogs will not appear when doing a tag search :-(
I currently don't know how to solve that (lazy loading vs tags which require eager loading). Maybe Nexus needs some kind of cache of catalogs seen so far which updates itself when trying to actually access that catalog.

Maybe use that catalog cache in general to avoid catalog being loaded before their first access? But that requires the cache to be invalidated when something changes ... just an idea


Bug in F1 score computation

Hello, thank you for releasing the code!
I'm wondering if this line for computing the F1 score is a bug (flipped order of truth and pred), or it's because of how your data is set up. If so, could you elaborate?
A similar issue is raised here.

Hi Trang,
Greetings! Thank you very much for pointing it out -- it is indeed a bug of evaluating the F1 score in MOSEI sentiment and I have corrected the code. Using the correct version, I can obtain an F1 score of over 82% within 20 epochs on MOSEI sentiment, using the default run.sh in the Github page, which is even better than the reported number in the paper (81.8%). More hyper-parameter tuning might help the performance.
Thank you very much for your post!
Sincerely,
Martin


Rails 4.0 upgrade

This PR upgrades Rails from 3.2 to 4.0.13. An upgrade to higher versions of Rails will follow shortly.
The most dramatic change is moving the running of the jasmine specs to the CI build (see 7c45659).
/cc @binaryberry @boffbowsh

This should be ready for another review.

Looks good - would be good to deploy it to preview.

Pushed to preview, seems to have been deployed and running OK.


[release-4.6] Bug 1945149: only override deployment resources when explicitly defined in subscription config

Manual cherry pick of #2036

/hold
I need to backport the operator-framework/api component of this PR to the (currently non-existent) v0.3.x branch and cut a new release. Just want to let CI run to make sure the entire patch set works.

/bugzilla refresh

/test e2e-aws-olm

/test e2e-aws-olm

/hold cancel

/test e2e-upgrade

/test e2e-upgrade

/retest

/test e2e-upgrade

/approve

[patch-manager] :hourglass: This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window.

Score: 0.20
Reason: maximum total for this z-stream is 10

NOTE: This message was automatically generated, if you have questions please ask on #forum-release


Disable Monitoring via detecting Condition

Problem:
Can't completely clean up after disabling cluster monitoring, as the
MonitoringStatus may be nil before disabling Monitoring operation
Solution:
Detect the status of MonitoringEnabled condition
Issue:
https://github.com/rancher/rancher/issues/19645

The key problem is that we don't create a cluster.Status.MonitoringStatus before the prometheus is ready. The code is in https://github.com/rancher/rancher/blob/master/pkg/controllers/user/monitoring/clusterHandler.go#L105-L115. We should also create that status even prometheus is not ready.

LGTM

Closing as the commit was incorporated into daily 2.2 cherry-picks pr https://github.com/rancher/rancher/pull/19923

Change is already in 2.2 branch https://github.com/rancher/rancher/blob/release/v2.2/pkg/controllers/user/monitoring/clusterHandler.go#L136


Invalid address?

I installed the app on Ledger Nano S per your instructions and ran the ElrondTestApp_linux_v1.0.3 on Linux as instructed.  When I do so I get something like:
Nano S app version:  1.0.3
Network: Mainnet ; Contract data: Disabled
Chain ID: 1
Tx version: 1
Retrieving address. Please confirm on your Ledger
Address: erd1r27kar...yq3a8tj0
Sender shard: 0
Balance: 0 ERD
Nonce: 0
Enter destination address:

I assume the [truncated] address erd1r27kar...yq3a8tj0 was my Elrond wallet address for receiving ERD but when I try to transfer ERD into my wallet using that address I get an error saying it isn't a valid Elrond address.  Using the official API I get:
https://api.elrond.com/address/:erd1r27kar...yq3a8tj0
{"data":null,"error":"checksum failed. Expected dls050, got 3a8tj0.","code":"internal_issue"}
Is there another place I should be looking for the receiving address on my Nano Ledger S?

Hello.
This implementation is for native eGLD tokens. I presume you tried to send ERC20 or BEP2 ERD in the address generated by the NanoS, and that's why it said "not a valid Elrond address".
To use the official API, please omit the ":" from the address route.
Looking forward to your feedback after you update to the latest version (Ledger Live 2.9 or 2.10, NanoS firmware 1.6.1, Elrond app version 1.0.4 - Development mode)
Best regards


Stackenetes Entrpoint Image (v0.1.0) does not correctly detect service dependencies with k8s >1.5

Is this a bug report or feature request? (choose one):

Kubernetes Version (output of kubectl version): >=v1.5.0
Helm Client and Tiller Versions (output of helm version): N/A
Development or Deployment Environment?: N/A
Release Tag or Master: N/A
Expected Behavior: For entry-point image to correctly detect service status
What Actually Happened: Image incorrectly resolves services as available when they are not.
How to Reproduce the Issue (as minimally as possible):
Use v0.1.0 image with k8s >v1.5.0
Any Additional Comments:
This can be simply resolved by updating our charts to use v0.1.1 of the kubernetes-entrypoint image.
eg: https://github.com/att-comdev/openstack-helm/blob/master/glance/values.yaml#L24
this:
dep_check: quay.io/stackanetes/kubernetes-entrypoint:v0.1.0

should become:
dep_check: quay.io/stackanetes/kubernetes-entrypoint:v0.1.1

this will need changed in every values.yaml file that uses the kubernetes-entrypoint image.

Are we sure this is the totality of the issue (at least in K8s 1.5.1)? @larryrensing has seen a service object add endpoints that were not yet in a ready state (and allow non-ready service endpoints was not annotated, whatever that annotation is -- on the service).  He's seen this simply using kubectl describe. I believe that would break anything trying to do service type validations.  I am wondering what does 0.1.1 do to address that?

@alanmeadows This bug: https://github.com/stackanetes/kubernetes-entrypoint/pull/21/files#diff-96a47b800d818cc653a127693efd308b
kubernetes-entrypoint was just waiting until any endpoint will appear in the service when we should wait for only ready ones. Patch above fixes that issue.

We need to bump version to 0.1.1

@alanmeadows this will definatly go some way to resolving the issue as @ss7pro has explained much better than I have (should have linked in the original issue...). But I've also seen similar 'phantom' endpoints on occasion which this would not resolve.

If entrypoint actually examines the readiness of the endpoints in the service list, as opposed to just their mere existence, this may mask the K8s phantom issue then.  I wasn't aware it was going to that length.  0.1.1 seems like a good move then.


SSH-Agent socket is not found by the docker/build-push-action step

I'm trying to use the  ssh-agent with docker/build-push-action.
I tested the same Dockerfile with ssh flag localy and it works this way:
eval $(ssh-agent)
ssh-add ~/.ssh/id_rsa
docker build --ssh default=$SSH_AUTH_SOCK -t myacr.azurecr.io/myapp/api:latest .

My workflow.yaml
      - name: Docker Metadata
        id: dockermeta
        uses: docker/metadata-action@v4
        with:
          images: myacr.azurecr.io/myapp/api
          tags: |
            type=sha
            type=ref,event=branch

      - name: Azure Login
        uses: azure/login@v1
        with:
          client-id: 23...8e
          tenant-id: 48..a9
          subscription-id: f9..25

      - name: Login to ACR
        run: az acr login -n appnamespace
        shell: bash

      - name: SSH-Agent setup
        uses<EMAIL_ADDRESS>        with:
            ssh-private-key: ${{ secrets.SSH_PK }}

      - name: Collect Git and SSH config files in a directory that is part of the Docker build context
        run: |
          mkdir root-config
          cp -r ~/.ssh root-config/
         // ~/.gitconfig was removed because it does not exist and cause failure

      - name: Build and push
        uses: docker/build-push-action@v3
        with:
          context: ./back
          ssh: |
            default=${{ env.SSH_AUTH_SOCK }}"
          tags: ${{ steps.dockermeta.outputs.tags }}
          labels: ${{ steps.dockermeta.outputs.labels }}
          push: true

I added this to the Dockerfile:
COPY root-config /root/
RUN sed 's|/home/runner|/root|g' -i.bak /root/.ssh/config

The last step fails with the following error:
ERROR: stat /tmp/ssh-XXXXXX9ilfNL/agent.2354": no such file or directory Error: buildx failed with: ERROR: stat /tmp/ssh-XXXXXX9ilfNL/agent.2354": no such file or directory

You have double quotes " following the ssh argument for the build-push-action, is that intentional?

you're right. thanks a lot. (sometimes we need to sleep and start again)
btw, I removed the  Collect Git and SSH config files.. step and the Dockerfile commands COPY root-config /root/... and it's working fine without them.
you can close as not a 🐞

Yes, you need those files only when using multiple SSH keys (e. g. GitHub deployment keys).


Pagination

Do you plan create pagination ?

Do you plan create pagination ?

Hello, @vizarch. The project has already been paginated since version 3.0.0. Take a look at the '_config.yml' file and look for "Pagination". I hope this helps :)


[PDI-13570] - Regression: Shared DB-connections without .kdb file not sh...

...owing in Spoon 5.3
@mattyb149, @brosander review it please

The class and methods should be public not package-protected

@mattyb149 why do you think so? The collector is a class to be used inside a procedure, I don't really believe it makes any sense to reveal it to the whole world

Our coding standards discourage package protection in favor of explicit protected access. This is usually to make the access level clear. If package-protected is the best choice, then the class and each method must be documented as such (Javadoc)

I recommended public access because it appears generally useful. Even if we only call it once from the same package, other people who embed PDI would be able to use it as they see fit :)

@mattyb149, I've updated the PR

Cool, thanks!


Improvement gsc_high_dim_visu

allow numeric factor for cell coloration based on :

a score thanks to a two columns table
gene expression by looking directly in the expression matrix (be careful, if raw count matrix maybe log transformed the data)

plot PC1 vs PC2 - PC1 vs PC3 - PC2 vs PC3
add axis labels for t-SNE
remove unnecessary parameter : normalize
output cluster table
add clusterR utility to get external validation of clustering (only if the factor table is given & is not numerical)

--> Done : #405

Add UMAP visualisation ?

Sure, but in a new issue. In CI, what is done is done

Ok !


Consider avoiding the build script

I read your blog post through the Rust reddit, and this looks like an amazing piece of work! I just wanted to highlight one potential improvement:
You currently generate code in a build script. As far as I can tell, the code generation step relies only on data that is available in your repository, that is, it does not depend on the build environment or any external input.
In such cases, a build script doesn't seem to be the best way to take care of code generation. Instead, consider adding an integration test that generates the code and store it in the repository. This means that downstream users no longer need to compile the build script and the downloaded resources from crates.io can contain the generated state machine directly instead of having to download all the pattern files. If you do it right, CI can check that the generated code is in sync with the pattern files in the repo.
You can find one example of this approach here: https://github.com/mattsse/chromiumoxide/pull/80. Writing up a blog post on this pattern is on my list, would be interested in your feedback.

I guess you could reference matklad's post on the topic unless you really want to write your own take.

I was definitely going to mention matklad as the inspiration since I originally got the idea from https://github.com/steveklabnik/semver-parser/pull/50, but I think the post you linked to underemphasizes that people should avoid build scripts where possible, and overemphasizes the idea of magic code insertion, where in my experience just generating code into a directory hierarchy in src works well and maybe even better for most of the cases I've encountered (so far I've contributed changes like this to about 5 or 6 projects).

Thanks for the kind words! I'll have a look at this soon.

I usually commit the generated code in the repo. If you accidentally botch some part of the code generation process such that the generated code doesn't build, I usually just comment out a bunch of stuff to make it work again. In my experience, the code generation code doesn't change very often so it's not a big deal -- IMO it's worth not inflicting the extra compile time on downstream users (even without extra dependencies).


Indicate license link to the local file

It works on both web and local renders.

Thx!! @Goooler 🤙🏽🤙🏽


fixed area codes for Italy

I updated the area codes for Italy using http://en.wikipedia.org/wiki/Telephone_numbers_in_Italy as documentation as described in the original code.

Grazie mille! Released in 2.12.4 :)


mgmt/mcumgr: Remove redundant memcpy from buf processing

The commit removes redundant memcpy operations and switches from
using TinyCBOR provided byte order converters to sys_be, native
to Zephyr.
Signed-off-by: Dominik Ermel<EMAIL_ADDRESS>

Converted to draft due to possible alignment issues.


Vs 2022 support

This theme only supports Vs2019. Can you update and add VS2022 support ?

@SinanTaskinlar look at my fork. .VSIX is in the root folder.

@SinanTaskinlar look at my fork. .VSIX is in the root folder, download and install.

I did exactl this AND IT WORKS!!!
Thank you so very much!!


Support dragging in seekbar

Hi, in the seekbar of the current music playing, the only thing you can do is click on a particular instant of the bar and the music starts playing on that moment. Having used a few other players, I think that allowing dragging the seek point in the bar will be a really helpful feature.

Seems like we got a regression here, it's supposed to be supported. Thanks for the report!

Thanks! :slightly_smiling_face:

Btw, I'd love to contribute! This is one of the few music players for Linux with a really good design. I've worked in React as well as Electron before, can you tell where can I get started?

Take a look at starter tasks


Takes very long to load emojis

Hi,
when clicking on the emoji icon in the composer it takes very long to load the actual icon sets. In firefox I get even a "script stop" message.
Using FF 46.01 on arch linux
NodeBB v1.0.3.

This is still happening.  Opening the Emoji box fires of 2500+ HTML requests because it injects EVERY FRIGGIN' EMOJI IMG TAG ALL AT ONCE.
2500+ HTML requests, 4+MB.  Nope!  No no no no no no no.  =(
If it only injected the IMG tags for the ONE tab and ONE page being viewed it wouldn't-- know-- crash the browser.

I also have this issue on FF 50, windows 10. The entire page temporarily locks up and becomes unresponsive.

Please, we have to be able to select which sets to display in the smiley overview popup. This is completely unmanageable - even for sysadmins getting DDOS'sed with smileys ;)


F# doc generation discussion

Continuing discussion from #27

No. Docs is a general term. Frankly I'm not sure what this repo does at this point other than run a tool in CI, but what it emits is very specific: the API reference for FSharp.Core. The repo should be named according to what it does.
fsharp/core-reference
fsharp/core-api-reference
fsharp/api-reference
fsharp/fsharp-core-reference
fsharp/fsharp-core-library-reference
etc.
docs.fsharp.org also doesn't point anywhere.
I think we need to slow down here and assess what it is we're actually trying to accomplish. Taking broad strokes to build and merge and completely change everything without time for feedback that's been asked for shouldn't be done. Is this:

An FSharp.Core API reference?
A more general API reference for other things in F#?
A general documentation site for F# that also includes FSharp.Core, effectively competing with the MS docs?
A stopgap for when FSharp.Core gets properly ingested into docs.microsoft.com?
A place for people to make meaningful contributions to the docs site? (see here: https://github.com/fsharp/docs/issues/30)
An experiment to test FSharp.Formatting?

At this point I'm not clear about it anymore. The original goal was to act as a stopgap to eventually be subsumed by the MS docs site.

Here's my thinking on where we are:
F# language support for docs.  The F# language design and default tools built on FSharp.Compiler.Service should properly support the C# XML doc standard. This includes checking docs at compile time and resolving cref symbols (to allow rename-refactoring to rename the symbols).
Separately we should actively consider putting in support for markdown docs into the core language design and tooling.  It should be experimented with as much as feasible on the outside but delivered in the core tooling.
Doc tooling (library): FSharp.Formatting is both a library and a tool.  The library side is in fairly good shape but in some areas requires continued iteration (especilly ApiDocs).  No one should be picking up a dependency on F#F as a library unless you are building a tool or a very simple API that effectively encapsulates the dependency.
That said, FSharp.Formatting is at the root of the doc-aware universe for F# - just like FSharp.Compiler.Service is at the root of the non-doc-aware universe (note that for API Docs FSharp.Formatting is really a layer over FCS adding doc-awareness).
This means we need to embrace the long term role of F#F and actively improve it, just like we need to embrace the long term rols of FSharp.Compiler.Service and embrace that.  I finally forced myself to do this over the last two months, to rip the stinking mess of Razor out of F#F and iterate until it was usable and half-effective in terms of accurate content.  I will continue to iterate and engage on that because it's just too important, even for a project like DiffSharp.  I believe this may now allow other people to engage at that layer too once the dust settles over the next month or two.
Doc tooling (tool): There is a continuing need for content-driven, stylable, low-dependency tooling that can deliver quality documentation for a typical F# library project with almost no effort. For me, this is how I got into this: I need doc tooling for DiffSharp.

The basic experience should be "install tool and make me the docs"

The docs should be built from content (and optionally a template and styling)

Ideally this should be done without writing any F# scriptsm and avoiding duplicating scripts

This tooling should generate accurate, bug-free doc content and be good enough to generate quality documentation for FSharp.Core, FSharp.Compiler.Service, FSharp.Data and other projects.

The default design styling(s) should be excellent. People who are good at design in the community should be actively improving it at its core.

The literate content should be F# scripts and markdown. The primary outputs for these should be HTML and notebooks.

FSharp.Core docs  Currently there are no FSharp.Core docs by Microsoft at all - the old MSDN docs are no longer found by google search.  Further, I doubt the long term ability to deliver up-to-date doc content for FSharp.Core given that the documentation is, to my understanding, hand-written.  If it happens that's great though it's a shame if the content is not authored in a way that improves doc tooling at its core (e.g. not written using F# language XML doc tooling).
Because of this situation, the FSSF and community should at least have the ability to generate and deliver docs for FSharp.Core. That's what this repo is currently for - to deliver those docs when they are needed and for as long as they are needed.
The doc content in FSharp.Core.xml needs massive improvement.  Actually being able to see the generated docs here is a good step and anything that anyone notices about poor content should be noted ASAP.
FSharp.XYZ* ecosystem docs:  There is a significant set of community components that have doc presence that needs updating (FSharp.Data, FSharp.Compiler.Service, maybe 5-10 other components).  I don't have strong opinions about that except that

I never ever want to see another generate.fsx script in my life - that was an unmaintainable way of generating docs
The docs should use tooling that is content driven and ultra simple (for long term maintenance)
The styling and templating should be magnificent (not something I can do)

Docs on fsharp.org.  I don't have strong opinions about this.

Because of the issues with FSharp.Core docs it seems natural for the FSSF to have the capability to deliver FSharp.Core docs.   Using fsharp.github.io/docs seems a reasonable host link for this, fsharp.github.io/fsharp-core-docs would be OK as well.  It really depends on whether there is longer term intent to expand to have a unified doc presence for other F# libraries.

At the last Dugnad a position put forward was fsharp.org should have a searchable docs experience. This seems a reasonable long term goal but it has ramifications and needs discussion.

Having the technical capability to easily deliver quality API docs from a set of say 10 chosen nuget packages seems like a good thing.

Multi-language docs.  We should make sure we keep the capability to deliver multi-language docs. Please advise on what's the best approach to this.

I think this repo should be strictly about FSharp.Core API reference documentation. Whether or not it eventually gets replaced by the MS docs site can be resolved later, but that was the original scope and I think it should stay that way. A good path forward is to use it as a way to show a great way how to generate it, then work the MS docs owners to incorporate the tools used/built here to generate an API reference in the same way they're ultimately generated here. Since they're entirely OSS anyways, this seems tractable.
Regarding this point in the PR:

Please redesign the core F#F template and/or CSS for it. But aim to get that into FSharp.Formatting, so all docs for all sites can make use of it.

I don't think we can apply a "one size fits all" approach here. Styling and layout should be done in a way that is best for the FSharp.Core reference, not all possible F# libraries. I feel flexible on this position, but at the end of the day what matters is that FSharp.Core has a quality reference people can access, not that we solve the problem of how to generate API references for any arbitrary F# codebase.

at the end of the day what matters is that FSharp.Core has a quality reference people can access

Yes, I do agree with this as the core goal for this repo.  However there was no chance of reaching this goal without a thorough revision of F#F.  We have to build to build on solid foundations.
F#F is not "one size fits all" - it has always had four levels for styling and customization:

Template parameters
CSS
A bespoke template
Use the ApiDocsModel

These involve increasingly more work and are increasingly fragile.
As the current effective maintainer on F#F my position is that the library and tool should at least be provably capable of producing quality docs for FSharp.Core without any special settings.    If it's not capable of that (in terms of content production, search index and basic styling), then no amount of styling will ever give you what you want - not even reverting to level-4 customization (as this repo was previously doing) would have helped - it was just been building on sand.  There is simply no way to work around problems in logical content coming out of F#F except through unmaintainable patch hacks (just as you can't get quality code out of FCS by patching stuff from the outside).
So first we have to get to a point the F#F is giving us the right logical content - based on accurate content in FSharp.Core.xml.  Once that is actually in place and fully stable then people can do Level 1-3 customization (styling and templating) as much as they like, and if really necessary even do Level 4 customization too (though it's likely to break over time).
Whether this repo actually ends up using any customization is another thing - I'd prefer not until we're sure we've got the doc model right - but yes, some customization makes sense.  But first things first.

A good path forward is to use it as a way to show a great way how to generate it, then work the MS docs owners to incorporate the tools used/built here to generate an API reference in the same way they're ultimately generated here. Since they're entirely OSS this seems tractable.

It's a good goal.  However in isolation this is not feasible. This repo - like any Waypoint or MiniScaffold repos - has always has had a massive dependency on FSharp.Formatting (or at least the FSharp.Formatting.ApiDocs part).
That's a dependency on a component that was, until recently, frankly nowhere near what was needed to do quality doc generation for DiffSharp, FSharp.Core or FSharp.Compiler.Service (the three projects I really care about).  It is getting closer now, but there is still much more to do, nearly all of it generic.  We have to get that layer right, which is really what I'm focused on right now.
In terms of handing off to the MS doc owners - please start a new issue on what might be required, what kind of tooling/demonstration you think they might accept, what kind of internationalization and styling options they might need.  If that's one possible end game then we'll need info on what that looks like :-)

In terms of possibly handing off to the MS doc owners - please start a new issue on what might be required, what kind of tooling/demonstration you think they might accept, what kind of internationalization and styling options they might need. If that's one possible end game then we'll need info on what that looks like :-)

There's little required here. Nearly everything you mention here is not a concern of ours or of FSharp.Formatting. The only one worth focusing on is having the tool emit a reference in the structure and file format that the docs system uses. Everything else is handled by the docs system (styles, localization, ensuring it builds with samples, TOC generation, etc.). This should be something that is focused on once the dust settles a little bit and the core formatting engine for FSharp.Formatting is in a good place.
What the MS docs team requires is a tool that can be pointed at all shipped FSharp.Core NuGet packages and generate a reference that follows the structure and file format they use. Otherwise, the only path forward is to manually migrate the old reference markdown files, fix them up, and add new ones manually every time a new FSharp.Core ships.
It can be negotiated that the reference doesn't go back very far since we can't retroactively ship updates to older packages.

The only one worth focusing on is having the tool emit a reference in the structure and file format that the docs system uses.

Sounds like FSharp.Formatting is moving in the direction that's needed.
The ApiDocsModel is getting more and more complete (eg parameter information integrated, example sections available) and it just takes 300 lines or so to generate structured HTML following a particular spec, using particular tags. The cross reference links are probably usable already with the right root. Take a look at GenerateHtml.fs in FSF.
Generating the search material (?) and navigation information (?) will also be important, but overall it sounds like programming up a new version of GenerateHtml.fs in FSF to produce the required structure and CSS tags. A spec of those (or use existing sample pages) would be needed but it wouldn't be hard. If they could provide a sample outer template with associated content  to trial against that would help, or we could piece it together from the existing pages on docs.microsoft.com
I think it would be a new tool (much like fsdocs, you could fork that) or could be added in as an optional HTML generation option and styling to fsdocs. If have no problem with someone doing that

Btw have you got the old reference markdown files? I'd like to start copying out  the best of the content into the Fscore xml docs if you have it.

they are here: https://github.com/dotnet/docs/tree/migration-fsharp/docs/fsharp/library-reference
I migrated some of them by hand but it is a very large task and they are quite messy


improve exceptions

hmmm... getting this in a jest test...
import { ApolloServerTestClient } from 'apollo-server-testing';
import 'reflect-metadata';
import testContext from '../test-fixtures/testContext';
import { Beans } from '../types/Beans';

test('version query', async() => {
  const { query } = await testContext()
    .resolve<Promise<ApolloServerTestClient>>(Beans.APOLLO_TEST_CLIENT);
  const res = await query({ query: '{ version }' });
  expect(res.data).toEqual({ version: 'dev' });
});

it's complaining at test
Error: Failed: "TypeInfo not known for function Object() { [native code] }"
Error:
    at Env.it (/Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:91:24)
    at it (/Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-jasmine2/build/jasmine/jasmineLight.js:93:21)
    at Object.<anonymous> (/Users/calebcushing/IdeaProjects/service-graph/src/__tests__/VersionTest.ts:6:1)
    at Runtime._execModule (/Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-runtime/build/index.js:867:68)
    at Runtime._loadModule (/Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-runtime/build/index.js:577:12)
    at Runtime.requireModule (/Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-runtime/build/index.js:433:10)
    at /Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-jasmine2/build/index.js:202:13
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-jasmine2/build/index.js:27:24)
    at _next (/Users/calebcushing/IdeaProjects/service-graph/node_modules/jest-jasmine2/build/index.js:47:9)

the problem was I didn't include @inject("tag") in my dependencies.
For this ticket I'd like to see an improved exception. At the very least I need to know which class it was trying to inject when it failed, ideally with the type or parameter position trying to be injected, as I had about a dozen. At best I'd like to see the actual source of the resolve in the stacktrace.

here's another
(node:58963) UnhandledPromiseRejectionWarning: Attempted to resolve unregistered dependency token: Symbol(corsOrigin)

https://github.com/microsoft/tsyringe/blob/master/src/dependency-container.ts#L172

I actually just ran into this issue as well, providing null as a managed value.
Minimal reproduction:
import 'reflect-metadata';
import { container } from 'tsyringe';

container.register('foo', { useValue: null });

container.resolve('foo');

Resulting error:
/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:179
            throw new Error(`TypeInfo not known for "${ctor.name}"`);
                  ^
Error: TypeInfo not known for "undefined"
    at InternalDependencyContainer.construct (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:179:19)
    at InternalDependencyContainer.resolveRegistration (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:103:24)
    at InternalDependencyContainer.resolve (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:77:25)
    at Object.<anonymous> (/Volumes/Storage/Documents/Projects/tsyringe/main.ts:6:11)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Module.m._compile (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/ts-node/src/index.ts:814:23)
    at Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Object.require.extensions.(anonymous function) [as .ts] (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/ts-node/src/index.ts:817:12)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)

This was difficult to debug, not knowing that null was an invalid managed value.

Me too, this is bit of a problem. How do we handle optional dependencies?
@chrislambe did you find a solution for it?

@avin-kavish , what is the scenario you have that needs the Optional decorator? I haven't seen the need for it yet, but I do see that Angular has it, and we could follow suit if there were compelling use-cases.

Optional dependencies, I tried to use it to inject the current Principal acting on the resource. And sometimes the request can be from an unauthenticated user. I was planning to use the null value to indicate that.
I did,
container.register(Principal, { useValue: req.user }) // req.user may be null

But I can model the problem differently. I could change it to a wrapper class, similar to ASP.Net Core identity,
class Principal {

  ctor(public user: User)

  isLoggedIn() {
    return !!this.user
  }
}

container.register(Principal, { useValue: new Principal(req.user) })

So yeah, I can't exactly say optional dependencies are needed, but I think having them wouldn't be bad.

@avin-kavish I ended up just doing this:
container.register('foo', { useFactory: instanceCachingFactory(() => possiblyNullValue) });

And it seems to work fine, though I suspect there's probably a reason not to do this.

If that works and the other doesn't, it's a bug.

This issue still persists as of today. For optional dependencies, tsyringe throws  TypeInfo not known for "undefined" error.

I actually just ran into this issue as well, providing null as a managed value.
Minimal reproduction:
import 'reflect-metadata';
import { container } from 'tsyringe';

container.register('foo', { useValue: null });

container.resolve('foo');

Resulting error:
/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:179
            throw new Error(`TypeInfo not known for "${ctor.name}"`);
                  ^
Error: TypeInfo not known for "undefined"
    at InternalDependencyContainer.construct (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:179:19)
    at InternalDependencyContainer.resolveRegistration (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:103:24)
    at InternalDependencyContainer.resolve (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/tsyringe/dist/cjs/dependency-container.js:77:25)
    at Object.<anonymous> (/Volumes/Storage/Documents/Projects/tsyringe/main.ts:6:11)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Module.m._compile (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/ts-node/src/index.ts:814:23)
    at Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Object.require.extensions.(anonymous function) [as .ts] (/Volumes/Storage/Documents/Projects/tsyringe/node_modules/ts-node/src/index.ts:817:12)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)

This was difficult to debug, not knowing that null was an invalid managed value.

working on windows. but not working on docker container. I dont understand this :(


SIM: take timer irq as real timer with WALL_SIGNAL

Summary
SIM: take timer irq as real timer with WALL_SIGNAL
we take the host signal as IRQ in sim with WALL_SIGNAL opened.
Impact
ALL sim
Testing
VELA

I noticed that ostest with 'sim:smp' failed.
nsh> uname -a
NuttX 3.6.1 e34578a3d0 Dec 20 2022 12:37:26 sim sim
nsh> mount
  /proc type procfs
nsh> ps
  PID GROUP CPU PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK   STACK   USED  FILLED COMMAND
    0     0   0   0 FIFO     Kthread N-- Running            00000000<PHONE_NUMBER>76   7.1%  CPU0 IDLE
    1     1   1   0 FIFO     Kthread N-- Assigned           00000000<PHONE_NUMBER>60  10.7%  CPU1 IDLE
    2     2   2   0 FIFO     Kthread N-- Running            00000000<PHONE_NUMBER>20   7.0%  CPU2 IDLE
    3     3   3   0 FIFO     Kthread N-- Running            00000000<PHONE_NUMBER>20   7.0%  CPU3 IDLE
    4     4 --- 255 FIFO     Kthread --- Waiting  Signal    00000000<PHONE_NUMBER>48   1.5%  loop_task
    5     5   1 100 FIFO     Task    --- Running            00000000<PHONE_NUMBER>60   4.6%  nsh_main
nsh> free
                   total       used       free    largest  nused  nfree
        Umem:   67108304     348464   66759840   66759840     60      1
...
nsh> ostest
stdio_test: write fd=1
stdio_test: Standard I/O Check: printf
stdio_test: write fd=2
...
user_main: signal handler test
sighand_test: Initializing semaphore to 0
sighand_test: Unmasking SIGCHLD
sighand_test: Registering SIGCHLD handler
sighand_test: Starting waiter task
waiter_main: Waiter started
sighand_test: Started waiter_main pid=107
waiter_main: Unmasking signal 17
waiter_main: Registering signal handler
waiter_main: oact.sigaction=0 oact.sa_flags=0 oact.sa_mask=0
waiter_main: Waiting on semaphore
sighand_test: Signaling pid=107 with signo=17 sigvalue=42
wakeup_action: Received signal 17
wakeup_action: sival_int=42
wakeup_action: si_code=1
poster_main: Poster started
sighand_test: Started poster_main pid=108
[CPU1] _assert: Assertion failed CPU1 at file:assert/lib_stackchk.c line: 57 task: waiter 0x55d87be7914a
[CPU1] showtasks:    PID    PRI   CPU     STACK      USED   FILLED    COMMAND
[CPU1] dump_task:      0      0     0     66512      4776     7.1%    CPU0 IDLE
[CPU1] dump_task:      1      0     1     66512     12248    18.4%    CPU1 IDLE
[CPU1] dump_task:      2      0     2     66512      7160    10.7%    CPU2 IDLE
[CPU1] dump_task:      3      0     3     66512      7160    10.7%    CPU3 IDLE
[CPU1] dump_task:      4    255     0     67504      1048     1.5%    loop_task
[CPU1] dump_task:      5    100     1     67504      3160     4.6%    nsh_main
[CPU1] dump_task:    107    100     1     73648      1944     2.6%    waiter
[CPU1] dump_task:    108    100     2     73648      1224     1.6%    poster
[CPU1] dump_task:     29    100     0     67504      2008     2.9%    ostest
[CPU1] dump_task:     30    100     0     73600      2152     2.9%    ostest Arg1 Arg2 Arg3 Arg4
*** stack smashing detected ***: <unknown> terminated

@masayuki2009
Thanks for the reviewing & testing.
I think it is a testcase error.
Here is the resolve:
https://github.com/apache/nuttx-apps/pull/1463


Issue with creating database using the OPFS AHP file system

Description
I'm running into an issue when trying to create a new database using the OPFS AHP file system. This snippet
import { PGlite } from "@electric-sql/pglite";

const client = await PGlite.create({
  dataDir: "opfs-ahp://electric.db",
  relaxedDurability: true,
});

is producing this error

I have a minimal-repro repo here that has the issue: https://github.com/TheAndrewJackson/opfs-ahp_bug_repro

https://pglite.dev/examples/opfs
It needs to be somewhere that allows the sync api, so in a web/service (shared?) worker.

Thanks for the report @TheAndrewJackson
The OPFS AHP VFS only works in a dedicated web worker as it requires the sync access handle API which is not available on the main thread, in shared workers, or in service workers.
We should improve the error message on this.

ahh, that makes sense @samwillis. Thanks for the clarification!


Cannot resolve vue file in ts file when extending tsconfig.json

Reproduce:

Extend any config in tsconfig.json
Reload vscode if error doesn't appear

Repo:
https://github.com/pynnl/volar-extend-tsconfig
Use case:
I'd like to use google style in my project.
P/S: Thank you for the great extension.

@pynnl thanks to report! please try to add "rootDir": "."

@johnsoncodehk "rootDir": "." doesn't work for me. I've tried several options but the it seems that only removing extends worked.

I think I parsed tsconfig incorrectly, I'm checking.

should be fix in 0.21.5, please let me know if working or not.

It's working now. Thank you!


Add cape.sh to CNCF landscape

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.    Our project is closed source.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars? our project is closed source
[x] Have you picked the single best (existing) category for your project?   yes
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Deploy preview for landscape ready!
Built with commit 134230f906f8fc5ec48a6f03feb78d71427aa586
https://deploy-preview-1768--landscape.netlify.app

LGTM

Please add a one sentence description to your entry as the description being pulled from Crunchbase doesn't describe Cape.

@dankohn sure, i will add and get back.

@dankohn  changed as per ur comments.  let me know if anything else is needed.


A customized TextField using states to manage values will lose focus every key the user types

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
The custom input field loses focus each time the user presses a key when it is hooked up with states for the value and onChange prop. But works just fine when they aren't hooked up. I have no idea how to solve this issue.
Expected behavior 🤔
Type like any input field smoothly without losing focus and having to click on the input each time
Steps to reproduce 🕹
Steps:

Create custom TextField like in Material UI's docs
Set up the react useState hook to work with the new customied TextField
Type inside the TextField

Context 🔦
import React, {useState} from "react";
import ReactDOM from "react-dom";
import { styled } from "@material-ui/styles";
import TextField from "@material-ui/core/TextField";

const MyComponent = () => {
  const [val, setVal] = useState("");

  const BlackInput = styled(TextField)({
    '& label.Mui-focused': {
      color: 'green',
    },
    '& .MuiInput-underline:after': {
      borderBottomColor: 'green',
    },
    '& .MuiOutlinedInput-root': {
      '& fieldset': {
        borderColor: 'red',
      },
      '&:hover fieldset': {
        borderColor: 'yellow',
      },
      '&.Mui-focused fieldset': {
        borderColor: 'green',
      },
    },
});
    return (
      <form noValidate autoComplete="off" style={{fontFamily:"cursive"}}>
        <BlackInput
          value={val}
          id="fullName"
          label="Full name"
          inputProps={{style: {fontFamily: "cursive"}}}
          onChange={(e) => setVal(e.target.value)}
        />
      </form>
    )
}

ReactDOM.render(<MyComponent />, document.getElementById("app"));

Your environment 🌎
System:
    OS: Linux 5.4 Ubuntu 20.04.3 LTS (Focal Fossa)
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 97.0.4692.99
    Firefox: 99.0

I didn't test ist but BackInput should be defined outside of the Component scope

import React, {useState} from "react";
import ReactDOM from "react-dom";
import { styled } from "@material-ui/styles";
import TextField from "@material-ui/core/TextField";

const BlackInput = styled(TextField)({
    '& label.Mui-focused': {
      color: 'green',
    },
    '& .MuiInput-underline:after': {
      borderBottomColor: 'green',
    },
    '& .MuiOutlinedInput-root': {
      '& fieldset': {
        borderColor: 'red',
      },
      '&:hover fieldset': {
        borderColor: 'yellow',
      },
      '&.Mui-focused fieldset': {
        borderColor: 'green',
      },
    },
});

const MyComponent = () => {
  const [val, setVal] = useState("");

    return (
      <form noValidate autoComplete="off" style={{fontFamily:"cursive"}}>
        <BlackInput
          value={val}
          id="fullName"
          label="Full name"
          inputProps={{style: {fontFamily: "cursive"}}}
          onChange={(e) => setVal(e.target.value)}
        />
      </form>
    )
}

ReactDOM.render(<MyComponent />, document.getElementById("app"));

Hey there @socramm9 thank you so much, it works now. I am using the latest version but I tested the code on a random code sandbox.

I didn't test ist but BackInput should be defined outside of the Component scope

import React, {useState} from "react";
import ReactDOM from "react-dom";
import { styled } from "@material-ui/styles";
import TextField from "@material-ui/core/TextField";

const BlackInput = styled(TextField)({
    '& label.Mui-focused': {
      color: 'green',
    },
    '& .MuiInput-underline:after': {
      borderBottomColor: 'green',
    },
    '& .MuiOutlinedInput-root': {
      '& fieldset': {
        borderColor: 'red',
      },
      '&:hover fieldset': {
        borderColor: 'yellow',
      },
      '&.Mui-focused fieldset': {
        borderColor: 'green',
      },
    },
});

const MyComponent = () => {
  const [val, setVal] = useState("");

    return (
      <form noValidate autoComplete="off" style={{fontFamily:"cursive"}}>
        <BlackInput
          value={val}
          id="fullName"
          label="Full name"
          inputProps={{style: {fontFamily: "cursive"}}}
          onChange={(e) => setVal(e.target.value)}
        />
      </form>
    )
}

ReactDOM.render(<MyComponent />, document.getElementById("app"));

Are you using v4? @material-ui/core is the old package. https://v4.mui.com/components/text-fields/#customized-inputs

Thanks Brother it solved the problem, I was using the StyledTextField which was inside scope of functionalComponent as soon as I moved it away from the scope it started working
Once again Thanks


Bls signatures

Closes #4
This is an implementation to include the BLS threshold scheme of https://github.com/Chia-Network/bls-signatures
This includes:

The binary, src and header files of BLS for easy usage. (Optionally those could be excluded from and the manual install requirements added to the readme file)
Config files that include the necessary BLS keys
A key generator
The necessary PublicKey, PrivateKey, Signature and certificate implementations.

Additionally I had to add a way to load the master public key from file and set it in the replica config accordingly.

While I've been busy recently, could you try to use git submodule to refer to the external BLS library? Copying all the files right into the repo is a huge change... (I saw 79 files are changed..omg)

Okay, will do as soon as I get to it.


Bug: "Removing Tailwind CSS" gives build error

Terms

[X] I have read the guidelines for Contributing to Roots Projects
[X] This request is not a duplicate of an existing issue
[X] I have read the docs and followed them (if applicable)
[X] I have seached the Roots Discourse for answers and followed them (if applicable)
[X] This is not a personal support request that should be posted on the Roots Discourse community

Description
What's wrong?
I've followed the steps under Removing Tailwind CSS to remove Tailwind and use vanilla CSS.
However, upon completing the steps my build fails with Cannot read properties of undefined (reading 'config'). The documentation is likely out of date.
What have you tried?
It should be noted that I am using npm and not yarn. In the first step I used npm uninstall @roots/bud-tailwindcss instead of yarn remove @roots/bud-tailwindcss. Other than that, I've done what the guide says.
What insights have you gained?
None.
Possible solutions
None.
Temporary workarounds
None.
Steps To Reproduce

Create a fresh sage theme using compose.
Install and activate Acorn using as a Wordpress plugin.
Build theme, verify that CSS compilation works as expected.
Remove Tailwind as per the guide linked above.
Try to rebuild, get the error.

Expected Behavior
Should compile successfully without Tailwind after removing Tailwind as per the guide.
Actual Behavior
Build fails with Cannot read properties of undefined (reading 'config')
Relevant Log Output
✘  sage ./public [355b60293243b6655eb2]
│
├─ ✘ error
│  Cannot read properties of undefined (reading 'config')
│
│
├─ ✘ error
│  Cannot read properties of undefined (reading 'config')
│
│
├─ entrypoints
│ ├─ app
│ │ ├─ js/runtime.06fab3.js     1.05 kB
│ │ ├─ js/259.7edc5d.js       314 bytes
│ │ └─ js/app.ccc03f.js         6.63 kB
│ └─ editor
│   ├─ js/runtime.06fab3.js     1.05 kB
│   ├─ js/259.7edc5d.js       314 bytes
│   └─ js/editor.ab6756.js      6.74 kB
│
│
└─ compiled 12 modules in 425ms

Versions
v10.4.0

I'm unable to reproduce this following the steps from the docs
Please create a topic on https://discourse.roots.io/ if you'd like to try to get further support


Disable devicons (nerdfont icons)

Hello. I don't have devicons and nerdfont. I've installed lspsaga and noticed this

Is it any way to disable icons to regular letters which supported by any font?

https://github.com/glepnir/lspsaga.nvim#usage

That doesn't help.

Just read the Usage portion of the doc, I linked to it. The very first code block is what you seem to have missed.

Just read the Usage portion of the doc, I linked to it. The very first code block is what you seem to have missed.

What block you mean? I don't understand.

This blocks explains the configuration parameters, including the sign glyphs.

like doc say

@gshpychka is it possible to add option like disable_iconst = true instead of configure every sign?


Dependencies not found: core-js/modules/es6.array.iterator, etc.

I installed via npm install --save laravel-mix-polyfill
// webpack.mix.js

mix.js('resources/js/app.js', 'public/js')
  .sass('resources/sass/app.scss', 'public/css')
  .polyfill({
      enabled: true,
      useBuiltIns: "usage",
      targets: {"ie": 11},
      debug: true,
      corejs: 2,
   });

// package.json
    "dependencies": {
        "axios": "^0.18",
        "bootstrap": "^4.1.0",
        "cross-env": "^5.1",
        "jquery": "^3.2",
        "laravel-mix": "^4.0.7",
        "lodash": "^4.17.5",
        "popper.js": "^1.12",
        "resolve-url-loader": "^2.3.1",
        "sass": "^1.22.1",
        "sass-loader": "^7.1.0",
        "vue": "^2.5.17",
        "vue-svg-loader": "^0.12.0",
        "vue-template-compiler": "^2.6.10",
        "laravel-mix-polyfill": "^1.0.2",
        "vue-select": "^3.1.0",
        "vuex": "^3.1.1"
    }

Exceptions when running npm run hot
 ERROR  Failed to compile with 11 errors                                                                                13:26:31

These dependencies were not found:

* core-js/modules/es6.array.iterator in ./resources/js/QuestionMixin.js
* core-js/modules/es6.function.name in ./resources/js/QuestionMixin.js
* core-js/modules/es6.number.constructor in ./node_modules/babel-loader/lib??ref--4-0!./node_modules/vue-loader/lib??vue-loader-options!./resources/js/components/MachineInput.vue?vue&type=script&lang=js&, ./node_modules/babel-loader/lib??ref--4-0!./node_modules/vue-loader/lib??vue-loader-options!./resources/js/components/ProgressBar.vue?vue&type=script&lang=js&
* core-js/modules/es6.object.to-string in ./resources/js/app.js, ./resources/js/QuestionMixin.js
* core-js/modules/es6.regexp.match in ./node_modules/babel-loader/lib??ref--4-0!./node_modules/vue-loader/lib??vue-loader-options!./resources/js/components/Overview.vue?vue&type=script&lang=js&
* core-js/modules/es6.regexp.to-string in ./resources/js/app.js, ./resources/js/QuestionMixin.js
* core-js/modules/es7.object.values in ./resources/js/QuestionMixin.js
* core-js/modules/web.dom.iterable in ./resources/js/QuestionMixin.js

To install them, you can run: npm install --save core-js/modules/es6.array.iterator core-js/modules/es6.function.name core-js/modules/es6.number.constructor core-js/modules/es6.object.to-string core-js/modules/es6.regexp.match core-js/modules/es6.regexp.to-string core-js/modules/es7.object.values core-js/modules/web.dom.iterable

@mortenege can you run npm list --depth=0 and post the results?

+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>

Had the same issue, Installing latest core-js and adding the option corejs: 3 fixed it for me.

npm install --save @babel/polyfill then npm run dev again solves this issue.
Just make sure @babel/polyfill is inside the dependencies(not devDependencies) of your package.json and its up-to-date. In my case I'm using the "^7.4.4" and every thing works fine.
// package.json

...
"devDependencies": {
    "laravel-mix": "^4.1.2",
    "laravel-mix-polyfill": "^1.1.0"
}
...
"dependencies": {
    "@babel/polyfill": "^7.4.4"
}
...

The core-js is included in @babel/polyfill, and you don't have to modify the corejs option.
Also make sure the laravel-mix and laravel-mix-polyfill are up-to-date.

None of these solutions worked for me 😞


fix

Hi!
There is a problem in the package when connecting ftp-ssl.
laravel throws an error.
League\Flysystem\UnableToListContents
Unable to list contents for '', shallow listing
Reason: League\Flysystem\Ftp\FtpAdapter::connection(): SSL_read on shutdown: error:0A000126:SSL routines::unexpected eof while reading
at vendor/league/flysystem/src/UnableToListContents.php:17
13▕     {
14▕         $message = "Unable to list contents for '$location', " . ($deep ? 'deep' : 'shallow') . " listing\n\n"
15▕             . 'Reason: ' . $previous->getMessage();
16▕
➜  17▕         return new UnableToListContents($message, 0, $previous);
18▕     }
19▕
20▕     public function operation(): string
21▕     {
—————————


Use extend instead of pushing in a loop

Thanks!
@bors r+

:pushpin: Commit d8c08223fcb375a7cd366e10bfc53f14961fe2fc has been approved by weihanglo

:hourglass: Testing commit d8c08223fcb375a7cd366e10bfc53f14961fe2fc with merge 9cffcfc91eb35219d7ea54d93a5394e2984e8081...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 9cffcfc91eb35219d7ea54d93a5394e2984e8081 to master...


OSM Geolocation implementation

major note: must ask for user permission

Hey, I was just wondering how this was going and if you wanted any help with this - I'm working on bringing some new people on board looking for things to do! Let me know if you want me to point them to you to assist!

Sounds good - I'll see if we can get another set of eyes on this - not to take over but to lend assistance where we can. Thank you!

Got it sorted 👍


[restore data from metadata store] is it possible ? druid version 0.13

Hi,
Below is my use-case;
I have just deleted some part of my data-source by mistake and I have lost its availability around % 12 . I have been querying coordinator APIs from my console as it shows:
curl -X 'GET' 'http://yonett1:8081/druid/coordinator/v1/loadstatus' and the result is
{"reporterwifiusage":100.0,"wifiusage":100.0,"activity3":87.79626432271229,"legacyusage1":100.0}
curl -X 'GET' 'http://yonett1:8081/druid/coordinator/v1/loadstatus?simple'
{"reporterwifiusage":0,"legacyusage1":0,"wifiusage":0,"activity3":1555}
When I querying the below command;
curl -X 'GET' 'http://yonett1:8081/druid/coordinator/v1/metadata/datasources/activity3/segments?full' I found all the metadata segments for this data-source, activity3, as expected and I indeed count all missing segments as 1555.
All above operations I performed with fully understanding however I can not figure out how I restore my missing 1555 segments from metadata source ?
Is it possible to restore data-source from metadata store information or is there a way to delete these metadata store information which is not desired at first place ?
Btw, I've setup HDFS and use it as the file system in my production cluster, and Derby is configured as the metadata storage.

I have been able to drop these segments from metadata store by using this API:
/druid/coordinator/v1/datasources/{dataSourceName}/segments/{segmentId} where segmentId is the id that historical nodes complains about not finding in the path it should be, and for this reason I am closing the issue.


[Feature request] Manually exclude a folder in /config (or elsewhere)

Hello.
First, let me say I appreciate a lot this add-on, working well and veeeeeery useful.
One feature would be amazing to have and is missing to my knowledge : being able to manually exclude from the backups custom folders / files.
For example, for people having GTFS integration setup, it only works with a huge sqlite DB in a config/gtts/ folder (2GB in my case). I currently have no way of excluding that folder specifically. The add-on takes everything.
Regards.

Just saw the discussion panel for new features.


DSC_ImportPfx: Update private key import location for LocalMachine using Import-PfxCertificateEx

Pull Request (PR) description
Importing PFX certificates to the local machine certificate path and the resource uses the function 'Import-PfxCertificateEx' from the common module results in the private key being installed in the users key store location rather than the machine path. The result of using the native 'Import-PfxCertificate' cmdlet is that the private key is stored in the same path as the public key import location.
This Pull Request (PR) fixes the following issues
- Fixes #248

Task list

[x] Added an entry under the Unreleased section of the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in the resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

I've submitted the fix for the CI: https://github.com/dsccommunity/CertificateDsc/pull/251 - Once that PR is through then you can rebase onto it and we'll get this merged.

@PlagueHO, Just merged in the latest changes and all is passing now.  Again thanks for your help!

Hi @39Delta - this PR has conflicts now (due to previous one being merged). Can you resolve and I'll finish review on this one too. Thank you! 😀


Exclude sections from camel/snake case conversion in Mail helper class

 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.

Thanks @simonbelanger!
How did you figure out sections should be excluded?

It wasn't working so I took a look at the payload sent to the API by the package and saw that the sections delimiters were all messed up.

Nice! Thanks!
@adamreisnz LGTM. LGTY? Happy Friday!

Awesome, thanks for checking and fixing this!

Do you have an ETA for the deployment of this fix?

I don't have an ETA just yet, but additional +1's and comments do help issues gain priority in our backlog.

@thinkingserious this can probably be merged safely, as it's essentially a bug fix, for a patch release.

Thanks @adamreisnz! I've got this on the backlog for a release.

@thinkingserious My pleasure! Form filled.


Screen readers can read content outside the "add user" modal

Area or Component
Manage users page - "add user" modal (but probably all modals on the page)
Quick Summary
Screen readers can read content outside the modal for "add users".
Accessibility Violation
Able to browse outside modal with screen reader: https://cdc-devtools.dequecloud.com/rule-help/en/reading-order-browse-outside-modal
Action Requested
All other entries on the page should be aria-hidden:true. See #4075 for more information (and hopefully a solution?)
This needs to be fixed for all modals on the manage users page.
Original Deque Issue
https://docs.google.com/spreadsheets/d/1b6xjubAN5Uw11DV4_B5zvSu7HeDI6Z-DpV4DMcToqAY/edit#gid=1647999156&range=15:15

Based on research done by @mehansen, we think this violation is a false positive. I've confirmed that:

The "Add user" model does use the accessible react-modal component
When testing with a screenreader, I am not able to read outside of the "Add user" modal

Based on this, I'm putting this on hold until we hear back from Deque. See more context in #4053.
cc: @emmastephenson

Further evidence that this is likely a non-issue from running AXE DevTools locally (none of the elements that they list for checking are tabbable):

Also pointing out via the documentation:

It is important for users of screenreaders that other page content be hidden (via the aria-hidden attribute) while the modal is open. To allow react-modal to do this, you should call Modal.setAppElement with a query selector identifying the root of your app. For example, if your app content is located inside an element with the ID root, you could place the following call somewhere in your code before any modals are opened:
Modal.setAppElement('#root');

We currently have Modal.setAppElement('#root'); set in our frontend/src/index.tsx file.

Confirming this a false positive corroborated by #4053, and closing!
cc: @emmastephenson

To do due diligence, we followed up on this ticket by testing with NVDA. We were not able to read outside the modal when using NVDA, see the screen recording for the Add User modal here


assignment of search Filter Function

Is it possible to assign a search filter function to change the way it searches? For instance starts with instead of contains? I tried the normal
filter:search:searchFunction
And place a function in both the directive code and the parent scope but nothing was called.
Thanks

Sure, you just have to change the template. Right now it's piping $viewValue into the filter filter, which will match if the model string is contained in any property. You just need to replace this with your own custom filter.
... | filter: ctrl.myFilter | ...

Controller:
this.myFilter = function() {
    return function(item) {
        return item.myProperty.indexOf(model) == 0;
    }
}

I've tried:
Putting this filter in your Demos "DemoCtrl" and using | filter: DemoCtrl.myFilter |
Putting this filter in the controller inside of the gm.typeaheadDropdown and not knowing what do put in | filter: ???? |
And just as a last resort just putting in | filter: ctrl.myFilter | with the filter in both of the previous locations and it never calls the filter .. or at least doesn't hit my break point on the filter.
It does break the original demo and the auto select when typing doesn't work any more.
Still confused as to how to make this work with your demo specifically..
Thanks for the quick response from the earlier question..

I was able to get it to fire in the debugger and the search works with startWith now, although the matching entry in the list is not highlighted as in the original demo, so the Letters of the list label changes correctly, but the blue highlight doesnt track the matching entry. Close..

I put the filter in
gm.typeaheadDropdown Controller area like this..
$scope.myFilter = function () {
return function (item) {
return item.name.indexOf(model) == 0;
}
};
Then called it from the template with | filter:myFilter |
It fires, but with not hightlighting in the list.. just wanted to be clear.. Thanks

Yes, I realized that because the directive has isolate scope, you'd need to change the directive's controller.
It really should be something passed in, I think, but for now check out this plunk:
http://plnkr.co/edit/6ErzgF?p=preview
You could also consider using the ui-select directive instead of this one. It does kind of the same thing and is more robust, although it could be overkill if you want something simple.

I had to change the template to "| filter:myFilter |"
to get the plnkr to work, but yes, it matches the text correct, but doesn't hightlight the right matching list entry.
And yes, I wanted something super small. I have looked at some of the "KitchenSinkWare" solutions but its just to bloated with excess functionality.

Sorry, I should have explained- I put a new property on the items in the first dropdown called location. Check script.js for the details. It's not highlighting the text because the text doesn't contain the search term, but it should narrow down the matches. For instance, start typing in 'London' and Mary will get selected since that's her location.

OK, I will check it out, thanks!


tests: set OPERATOR variable to true

add OPERATOR set to true for local test running
This is needed for certain tests (sev.bats) to distinguish between the general CI and the operator CI and to set the runtime class accordingly
Signed-Off-By: Ryan Savino<EMAIL_ADDRESS>

/test

Closed this as correct logic is implemented in this PR:
https://github.com/kata-containers/tests/pull/5416


Post tuning Believer parameters

Describe problem solved by this pull request
This updates the believer parameters after the vehicle tuning on 19/Oct/2021
Test data / coverage

Flight Log:
Video:

Additional context
Add any other related context or media.

Notes for parameters

CBRK_SUPPLY_CHK should not be disabled
Auto disarm should be disabled

are @acfloria comments on other state est and failsafe params addressed? (i.e. mirrored from EZG params)

I have not checked these params, but probably there need to be other param changes that should be included in this PR.


TypeScript

I would love to see TypeScript support added as a plugin.

Hi,
This project is currently in maintenance mode, so I can't add any new features right now. If you can add the feature and open a PR, I will gladly take a look and merge it.


merge from arlac77/template-kronos-module

package.json

chore(package): add arlac77/template-kronos-module (template.inheritFrom)

Codecov Report

Merging #906 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #906   +/-   ##
======================================
  Coverage    92.2%   92.2%
======================================
  Files          10      10
  Lines        1373    1373
  Branches      158     158
======================================
  Hits         1266    1266
  Misses        107     107

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 4ff1a62...9b5d12e. Read the comment docs.

:tada: This PR is included in version 8.3.17 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(pinia-orm): Add morphByMany as relation

🔗 Linked issue
resolves #1894

📚 Description
Add the inverse relation type of morphToMany

Codecov Report
Attention: Patch coverage is 98.94737% with 2 lines in your changes missing coverage. Please review.

Project coverage is 99.72%. Comparing base (ba65169) to head (c1ea5da).

Files
Patch %
Lines

...rm/src/model/attributes/relations/MorphedByMany.ts
98.48%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1897      +/-   ##
==========================================
- Coverage   99.75%   99.72%   -0.03%
==========================================
  Files          88       90       +2
  Lines        6078     6268     +190
  Branches      515      525      +10
==========================================
+ Hits         6063     6251     +188
- Misses         13       14       +1
- Partials        2        3       +1

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


AutoReload while coding kills switched app

When you are coding with a switched app and autor-reload enabled, having invalid code (even temporarily while typing) triggers a failed reload which stops/exits the switched container.
One then has to call app switch again which triggers a (possibly lengthy) image build.
Is there a way to make the switched app more robust in that it keeps trying to restart the switched container?

I'd say this is currently not in the scope of Unikube.
We added the --no-build flag in order to skip the Docker build process in case you only changed code. At least, that will speed up the process of starting up a failed switch operation a little bit.


The file file:///C:/Users/X/../../asset.jpeg could not be accessed.

I can access the asset when the app is served on local server like vs code live server. But when I try to open the file directly in the browser I get this error.

Quoting from the readme: "Due to browser security restrictions, a web server must be used locally as well."
Browsers don't allow JavaScript access to local files for security reasons, so you need to run a local server.


The first time "microsoft." is typed into a TextBox control, it will be capitalized for no reason

Describe the bug
The first time "microsoft." is typed into a TextBox control, it will be capitalized for no reason.
This only occurs the first time ever "microsoft." is typed into a particular TextBox control. If you clear the text in the TextBox and type "microsoft." again it will properly remain uncapitalized. On the first time ever "microsoft." is typed into a particular TextBox control the issue repros with 100% reliability.
I have not seen this repro with any other words, and in fact neither "microsofts.", "microsof.", or "microsoft"  repro this issue.
Steps to reproduce the bug

Download and open the WinUI 3 Gallery app and navigate to the TextBox control page or find any other WinUI 3 TextBox control
In a WinUI 3 TextBox control, type "microsoft." notice that it gets capitalized after typing the period. This is unexpected/undesired behavior.

Expected behavior
The expectation is that "microsoft." should not be capitalized for no reason.
Screenshots
After typing "microsoft." this is what my TextBox looked like...
NuGet package version
WinUI 3 - Windows App SDK 1.5.3: 1.5.240428000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

This also reproes for AutoSuggestBox and NumberBox.

This sounds like intentional auto correct. If you set the InputScope of the TextBox to match the kind of input requested, it could turn off auto correct, and you could still override it with IsSpellCheckEnabled="False".

This is default autocorrect behaviour (it detects Microsoft as a proper noun and capitalises it). You can disable this by setting IsSpellCheckEnabled="False"

Aha, thanks! I should have tried more proper nouns. I tried "tony" and just assumed that wasn't a behavior. Will close, seems fine as long as it can be disabled as you mention.


Language-agnostic Plugins

Does Telegraf plan to allow users to write plugins in any language? Being able to quickly write something in Bash or Python would probably make a lot of ops people happy. Quite often I only need to collect a measurement once an hour or so, so the extra overhead would not be an issue at all.
Maybe this could be implemented as a plugin that just runs a configured list of commands with some configuration in env vars.

It could also be nice to be able to specify a different duration between poll for each plugin.

@atmaniak you can do that already, check out Interval under https://github.com/influxdb/telegraf#plugin-options

@trehn It certainly could be implemented via an exec plugin that takes a list of programs to run. If they output JSON to stdout it should be easy enough to allow them to pass any number of values back as well.

Hello
@evanphx is it possible to use an unix socket to do communication between differents langages ?  I think it is a good way to have an universal plugin to gather metrics ?
The problem is for other environnement like windows... but for the moment I use it under MacOS and Linux.
If you like the idea, i could do a pull request about it.
Best regards,
Nicolas

Sounds like a good idea, marking it as an enhancement request

see PR #92


[Fixed: #5217 Velocity Advertisement Images issue.]

Issue Reference

Description

How To Test This?

Documentation

[ ] My pull request requires an update on the documentation repository.

This issue is fixed and can be merged.


Adding the version quick start

Utilizes connection from utilities
Thanks to @mccalluc and @hectorcorrea for getting me started!

I think we have moved on from the python library.  I'm closing it as I do not think we would utilize this code in the future


WIP-Chimp Cucumber smoke tests

What is the context of this PR?
This pull request is for the chimp cucumber smoke tests trello card. A basic test has been added to simply open the author tool and check if the title matches the feature file. #
How to review
Run ./node_modules/.bin/chimp in the terminal to see if the checks pass, also check if travis runs the script

Build failed because it couldn't find chimp. You might need to modify the .travis.yml file to globally install chimp JS. See https://docs.travis-ci.com/user/languages/javascript-with-nodejs/ for an example. See the Ember Apps example, in particular. They seem to have an install: section (which gets run by Travis before after before_install and before scripts  - see https://docs.travis-ci.com/user/customizing-the-build/ for details). Seems like the node dependencies can be installed during install and run during script.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3539ef6). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #107   +/-   ##
=========================================
  Coverage          ?   10.03%
=========================================
  Files             ?      100
  Lines             ?      658
  Branches          ?      217
=========================================
  Hits              ?       66
  Misses            ?      592
  Partials          ?        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 3539ef6...fd29c54. Read the comment docs.

@emilioward @samiwel can we use yarn instead of npm to install stuff on Travis?

 Add smoke tests (5)


Document how to install

Request
The documentation has a Getting Started section that specifies how to integrate Carapace, but does not specify how to install Carapace.
Proposed solution
Document how to install Carapace.
Anything else?
Would love to see HomeBrew formula for this
brew install carapace

I think it's best to remove it from the readme completely and just direct people to Installation.
I've got a homebrew tap.


Update ECP5 with latest progress

Could you add the DCO and then I will merge. Thanks for updating!


Making a GET and PUT request to users/register returns wrong response

I'm submitting a ...

[X] bug report
[ ] new feature / enhancement request
[ ] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[X] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

The users/register endpoint should only allow for POST requests. However, when making a GET request an incorrect error response is returned:
HTTP/1.1 400 Bad Request
{
    "alerts": [
        {
            "text": "id cannot parse to integer",
            "level": "error"
        }
    ]
}

And when making a PUT request this incorrect response is returned:
HTTP/1.1 400 Bad Request
{
    "alerts": [
        {
            "text": "'fullName' cannot be blank, 'username' cannot be blank",
            "level": "error"
        }
    ]
}

Expected / new behavior:

Should return
HTTP/1.1 405 Method Not Allowed
{
    "alerts": [
        {
            "level": "error",
            "text": "Resource not found."
        }
    ]
}

Minimal reproduction of the problem with instructions:

Anything else:

This is because when you do GET /users/register it thinks you're asking for a user with the ID "register". So that's actually an appropriate error message, because "register" is not a valid ID. When you do PUT /users/register it thinks you're trying to edit a user with the ID "register". Ideally I think that'd return the same error message, but the one it gave you isn't wrong either - those request body parameters are required for that endpoint.
Also, no other endpoint supports 405 - that's an API-wide problem that arises from the same root cause of your confusion on this issue: An endpoint is defined as a combination of request method and path. They should actually be defined by paths and those paths should have supported methods. But that's not the world in which we live.


ERROR: Attempt to initialize trace file reader failed with operating system error 0x80004005

Hi this file has full authority for everyone. can you help us identifying this issue
INFO: Starting build of XEL sequence order index
11/08/17 10:37:25.361 [0X000012C0]     XEL INDEXING PROGRESS: 1480 events found and 0 events skipped in c:\temp\pssd\output\IPLC-KNSA-W__pssdiag_xevent_0_131546359772530000.XEL
11/08/17 10:37:25.363 [0X00002EA0]  INFO: Total events indexed: 1480 (Rate: 56000/sec)
11/08/17 10:37:25.366 [0X00002EA0]  INFO: Event range 1 to 1480 for IPLC-KNSA-W__pssdiag_xevent_0_131546359772530000
11/08/17 10:37:25.371 [0X00002EA0] XEL READER ERROR: The tookLock argument must be set to false before calling this method.
11/08/17 10:37:25.371 [0X00002EA0] XEL READER ERROR: Attempt to open file c:\temp\pssd\output\IPLC-KNSA-W__pssdiag_xevent_0_131546359772530000.XEL failed, see previous error(s) for more details.
11/08/17 10:37:25.371 [0X00002EA0] ERROR: Attempt to open c:\temp\pssd\output\IPLC-KNSA-W__pssdiag_xevent_0_131546359772530000.XEL failed.
11/08/17 10:37:25.371 [0X00002EA0] *** ERROR: Attempt to initialize trace file reader failed with operating system error 0x80004005 (Unspecified error)
11/08/17 10:37:25.375 [0X00002EA0] Reads completed - Global Error Status 0xfffffffe

Please send me an email suresh_dot_kandoth_at_microsoft_dot_com for a newer/latest build of ReadTrace fro you to try and see if it resolves this problem.

Please send me an email suresh_dot_kandoth_at_microsoft_dot_com for a newer/latest build of ReadTrace fro you to try and see if it resolves this problem.

Hi Suresh, do you know if this issue is resolved? If not, do you have any work around or when this might be resolved? Thanks 👍

Please use the latest utilities from https://github.com/microsoft/SqlNexus/wiki/RML-Utility


fix: correct typos and cleanup

:wave:
While looking at the vitejs usage I fixed some typos.

🙇♂ 👍 💜


SAK-32315 (Bug fix) : Problem uploading file to Urkund with multipart…

… post http request

Refactor : Included UrkundSubmission object to better manage
parameters

Please squash it in one commit!


Gitlab registry does not support falco artifacts

Describe the bug
I can't push the plugin and rules images to the Gitlab registry. Also, I created a ticket on the GitLab side here.
How to reproduce it
$ crane copy ghcr.io/falcosecurity/rules/falco-rules:1 registry.gitlab.com/x/falcosecurity/rules/k8saudit-rules:1

Expected behaviour
I was expecting to see the images were pushed to the Gitlab registry.

cc @alacuku @loresuso

Thanks to the @developer-guy(Batuhan)'s PR. It will be fixed. The PR has been approved last time we checked. https://gitlab.com/gitlab-org/container-registry/-/merge_requests/1375

The PR got merged and added one of the features will be supported 16.3, yay! We can close this issue if you want folks, or we can keep it to keep updates from GitLab's side.

This issue now fixed. So, I am closing this issue. Thanks for the effort :rocket:


DRILL-4120: Allow implicit columns for Avro storage format

Existing implementation of AvroDrillTabl does not allow dynamic columns discovering. AvroDrillTable.getRowType() method returns RelDataTypeImlp instance with the list of all table columns. It forces validator to check columns from select list in RowType list. It makes impossible to use implicit columns.
This fix replaces the usage of AvroDrillTable by DynamicDrillTable for Avro format and also allows usage of non-existent columns in Avro tables to be consistent with other storage formats.

You are basically reverting changes done in DRILL-3810 to support schema validation in Avro.
Avro format is strict and has schema. Should Drill treat it the same way or do loosen parsing?
We should evaluate the option of leaving schema for avro but adding implicit columns. Maybe the change won't be as easy as changing AvroDrillTable to DynamicDrillTable but it might be more correct.
You can also start mailing thread on dev / user list, asking about treating avro as dynamic format (listing pros and cons) and get feedback from the users.
[1] https://issues.apache.org/jira/browse/DRILL-3810

General comment: if we could move to the new scan framework; it handles implicit columns for all file-based readers. It also handles projection, missing columns, etc...

As @arina-ielchiieva points out, this change backs out plan-time knowledge of schema. This may not affect run-time accuracy. However, it does mean that queries can be planned, based on not knowing types, that fail at runtime when types are learned. This seems more like a bug that a feature. In general, we should use all information available. It is not helpful to ignore information if doing so results in poorer user experience.

Another thought. The removed code is at plan time. Did the original code have to open each file to retrieve schema? If so, does removing the code remove that load? If so, then this change could be a huge performance improvement if avoids the need to open every file in the Foreman.
Then, the the next question is: do we actually do anything with the plan-time type information? Few files have that information. Given that, does the planner actually use the information? Is this something we get for free from Calcite? If we are not using the type information at plan time, then clearly there is no harm in removing the code that retrieves the type information.

@paul-rogers, schema is taken from the first file in the FormatSelection. Therefore for the case, when we have a table with several files with a different scheme, Drill query will fail.
As for the plan-time type information, besides the validation at the stage when a query is converted into rel nodes, field list may be used in project rel nodes instead of the dynamic star for DynamicDrillTable.

@arina-ielchiieva, @paul-rogers, I have reworked this pull request to use AvroDrillTable, as it was before my changes. Also, with AvroDrillTable there is no need to make changes in AvroRecordReader, so I reverted them.
Could you please take a look again?

@vvysotskyi, thanks for addressing the schema issues!

+1. LGTM.


[bug]: Stacked command not working when running locally

Describe the bug
When working on my own fork of stacked-org/cli I got the following error message when running certain commands: FormatException: Could not parse "packages\cli"".
I tracked it down to be caused by
    await _notifyNewVersionAvailable(arguments: arguments);

found here.
What operating system do you use?
Windows 11
Information about the installed tooling
No response
Steps to reproduce the issue

Clone stacked-org/cli to your machine.
Cd to stacked project or create new one.
run "dart run path/to/repo/bin/stacked.dart create view --help

Expected behavior
same as running: "stacked create view --help" when stacked_cli is installed from pub.
Screenshots
No response
Additional Context
No response

@Pebkac03 interesting.
I only develop on Mac so I don't have a windows machine to test this out on.
@ferrarafer maybe you have one?


EVM balance update on transfer

[ ] Telos EVM balance not updating immediately after transfer, refresh required

@Kersten-TCD can you provide clarification and/or reproduction steps on this point of feedback?

@donnyquixotic the native Telos balance updates pretty fast when sending tokens to the Web-Wallet EVM address.
The balance of the web-wallet EVM Telos does take pretty long to update though and sometimes even requires a refresh to update.
Please try sending funds to the EVM account and back to native account, this should show the delay.
It might also be an RPC issue, which I can not tell as I did not check the status of the nodes when testing. Will check next time.

@Kersten-TCD I believe this is resolved, please confirm by testing on production site.

@Kersten-TCD @donnyquixotic is this issue still happening?

@karynemayer testing Chrome on MACOS Ventura, I have tested various times, the balance update is a little "unpredictable" most times it will update immediately, other times only native or EVM will update correctly and require a refresh.
@donnyquixotic is the wallet page refreshed in defined intervals which would update without manual refresh?

unfortunately, the whole user balances solution is kind of a mess. I made a pretty good patch but clearly, this is a patch and needs refactoring. I will leave this as a temporal solution but I am already working on a better design to solve all of these problems and bring a unified solution.


Find a new pip install

Replaced with miditime. Open to other ones, just one that's quick to install. Was going to do beauitful soup, but then you have to explain weird beautifulsoup/bs4 import garbage.


inconsistent NullPointer when calling PrunnerApiService from CLI - Call to a member function getAccountIdentifier() on null

This is the error:
Call to a member function getAccountIdentifier() on null

  Type: Error
  File: Data/Temporary/Production/SubContextPrunner/Cache/Code/Flow_Object_Classes/
        Flowpack_Prunner_PrunnerApiService.php
  Line: 117
Received return code 1, exiting

Imho we need a null check here:

I called the error "inconsistent", since it only ocurred one single time until now. Retrying the Content Release was the Hotfix.
I will provide an PR when I have access to this repo.
cheers