Usage of WebApplicationFactory any ideas?

I am trying to find example usage and some documentation explaining the difference between using TestServer and WebApplicationFactory. I have seen this but I get the failure

System.InvalidOperationException : No method 'public static IWebHostBuilder CreateWebHostBuilder(string[] args)' found on 'AutoGeneratedProgram'. Alternatively, WebApplicationFactory1 can be extended and 'protected virtual IWebHostBuilder CreateWebHostBuilder()' can be overridden to provide your own IWebHostBuilder instance.    at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory1.CreateWebHostBuilder()
at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory1.EnsureServer()    at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory1.CreateDefaultClient(DelegatingHandler[] handlers)
at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory`1.CreateClient(WebApplicationFactoryClientOptions options)

To replicate I installed the package Microsoft.AspNetCore.Mvc.Testing and have the following test.
    public class UnitTest1 : IClassFixture<WebApplicationFactory<UnitTest1.TestStartup>>
    {
        private readonly WebApplicationFactory<TestStartup> _factory;

        public UnitTest1(WebApplicationFactory<TestStartup> factory)
        {
            _factory = factory;
        }

        [Fact]
        public void Test1()
        {
            void ConfigureTestServices(IServiceCollection services) =>
                services.AddSingleton<IRepository>(new Repository());
            var client = _factory
                .WithWebHostBuilder(builder =>
                    builder.ConfigureTestServices(ConfigureTestServices))
                .CreateClient();

            var result = client.GetAsync("api/values").Result;
            Assert.Equal(result.StatusCode, HttpStatusCode.InternalServerError);
        }

Ideally, some documentation on how to use it and possibly the differences between using the two (TestServer and WebApplicationFactory) would be very useful. When would you favour one over the other?

@guardrex  who's the right dev to ping on this?

@javiercn

Ideally, some documentation on how to use it and possibly the differences between using the two (TestServer and WebApplicationFactory) would be very useful.

@OnamChilwan Did u see the integration testing topic? https://docs.microsoft.com/aspnet/core/test/integration-tests

@guardrex I followed the documentation but still have the same issue. I would like to stick to using TestServer but asserting a 500 Internal Server Error is difficult.

@OnamChilwan I can't say. I haven't attempted to implement such a test with the new approach. I suggest that you ask on Stack Overflow. You'll probably get a faster answer there.
TestServer is part of the new testing approach. I'm not aware of interest among the engineers to have either another topic or topic section that addresses using TestServer directly.

WebApplicationFactory is the recommended approach and that's what we want people using. TestServer is just an infrastructure concept at this point, it lacks the setup that WebApplicationFactory does for your tests to behave in a way similar to your app environment.

I'm closing this because it isn't actionable for us. The guidance is clear on what we want devs to do.

I could reproduce the issue mentioned by @OnamChilwan when using a test Startup class defined in the test project itself.
It is probably worth mentioning it in the docs.

I was able to use a Startup class in my test project, but needed to also derive WebApplicationFactory and manually set the content root similar to: https://github.com/aspnet/Docs/issues/7063#issuecomment-414661566.
This works with v2.1.1 of Microsoft.AspNetCore.Mvc.Testing.

I'm struggling with this issue and above doesn't seem to work for me. My case is as follows:

Service under test (MyService.csproj)
Integration test project (MyService.Tests.Functional.csproj)

MyServiceFactory : WebApplicationFactory<TestStartup>
TestStartup : MyService.Startup (I need this so I can override an virtual method in the standard implementation to change the Auth for testing)
ScenariosBase (base class with some helper methods, ctor takes MyServiceFactory)
BookingQueryScenarios : ScenariosBase, IClassFixture<MyServiceFactory>

Unit test

Fails with same exception as above on CreateClient. I've overridden ConfigureWebHost, setting content root with UseSolutionRelativeContentRoot, but it throws before it even gets called.
Tried overridding CreateWebHostBuilder(), doing base.CreateWebHostBuilder().UseStartup<Startup>() (even though it seems redundant) and still the same issue.
Anyone got any suggestions? I'm on 2.2.0.

Hi.
It looks like you are posting on a closed issue!
We're very likely to lose track of your bug/feedback/question unless you:

Open a new issue
Explain very clearly what you need help with
If you think you have found a bug, include detailed repro steps so that we can investigate the problem

Thanks!


Allow dynamic token types and modifiers

Testing #85972
It would be good to allow generating dynamic token types and modifiers and have them match if they are styled.

With the current API all token types and modifiers a provider can return are given by the legend which is passed in when registering the provider.
I'll make the change that accepts all ids listed in the legend
Duplicate of #86314


🎮 Game Request
c4, stands for Connect Four, is a browser game written in TypeScript and utilizes HTML's canvas. Player is playing against an AI that uses Minmax algorithm and alpha-beta pruning. The evaluation function is hard-coded, and hence the AI may not be moving using the most optimal move.
Point down the features
The first player who is going to connect the four dots vertically or horizantally or diagonally will win the game.

Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @U-DAY-333 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @U-DAY-333 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Add support for Cassandra

Add connectors for Cassandra Cluster instances with Java and XML-based configuration. Cassandra configuration is obtained using the single-tenant Datastax/Cassandra tile.

Open issues:

[x] Spring Data Cassandra 1.5 is a milestone release, so this PR should not be merged/released until Spring Data Cassandra is GA.

I upgraded the PR to pick up Spring Data Ingalls' and the latest changes for Spring Data Cassandra.


Rm/fix chart names

Fixes #
Description
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 76.098%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
5562

Relevant Lines:
7309

💛  - Coveralls


Installation error on windows "opencollective postinstall"

When installing via npm there is an error
npm ERR! code 1
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c opencollective postinstall

npm ERR!      C:\Users\User\AppData\Local\npm-cache\_logs\2021-06-30T12_42_07_984Z-debug.log

Your Environment

Obfuscator version used: 2.15.5
Node version used: v15.14.0

Log from npm
https://pastebin.com/54RFgmWX

How did you solve it?

I uninstalled package.json, and reinstalled all the dependencies. This was the only thing that helped.


Switched explorer from position absolute to position fixed. Fixes #2520

Fixing #2520

Merged in ab53b1817f90c0b7055687f9d9b23442b332c147 - thanks!

Unfortunately I've had to revert this due to the issue reported in #2678 - will reopen #2520.


Consider implementing the API for non WASM targets

I am aware of #6 and understand that testing the component requires using wasmtime. However, it would be highly beneficial if waki could support running in non-WASM environments, wrapping one of existing HTTP clients.
This enhancement would allow developers to test and debug components using familiar tools, streamlining the development process and making it more accessible.

Do you think that the behavior of the HTTP client is going to be different all that often? Sure, the host could decide to do something else with the request, and in order to test that, one needs to write an integration test as suggested in #6, but for most cases I think it is safe to assume that the host will forward the request properly.
It could be hidden behind a feature flag to highlight the fact that this is intended for testing.
The scenario I am thinking about is introducing WASM Components to new developers. Not being able to use one of the standard clients (yet) is a hassle, so we should not add more things that look like a barrier.

I would second this feature request.
First of all, great job to the author and maintainers to this repo, same as @tomasol , I came across this repo a few weeks ago, and surprisingly find that how much simpler it makes developing http clients and servers on WASM.
In addition to the testing purpose mentioned in the ticket, If waki can be made to work across WASM and non-WASM targets, it'll be very useful in libraries like Dapr SDKs. Nowadays, WASM developers need to rebuild many wheels simply because libraries like Dapr SDK can't work out of the box in WASM. A generic cross-target http client would help to resolve these cases.
I think the testing perspective is still valid - maybe it's inappropriate to unit test in native Rust because of the potential behavioural difference, but sometimes we want to write somewhat integration-level testing, taking Dapr client again as example, I'm hoping to use testcontainers to startup a datastore and Daprd container and validate that my client is sending the right headers to Dapr and it's able to CRUD the datastore. Mocking waki wouldn't make much sense in such test.


Add assignees template variable

Adds a new template variable, assignees, which should allow a body input like this:
body: |
    :wave: heads up, {{#each assignees}}@{{this}}{{#unless @last}}, {{/unless}}{{/each}}!

cc @imjohnbo for :eyes: since I can't request your review :bow:

cc @imjohnbo for :eyes: since I can't request your review :bow:


Issue with node color and opacity

First of all, I want to point out how valuable is the work that you have done.
Please, allow me a question (maybe it is a dummy one). My issue is that I cannot change the 'color' and 'opacity' attributes for the nodes. I read the API, and especially for the color attribute I have used all the possible variations.
Here is a snippet of my data.json.
 "nodes": [
                {
                    "id": "id1",
                    "name": "name1",
                    "node-color": '0xff0000',
                    "color": 'red', // another approach 0xff0000 // another ff0000 // I tried RGB as well
                    "opacity": 1, // same thing for opacity when I change the values between [0,1]
                    "val": 1
                }
],
"links": [
                {
                    "source": "id1",
                    "target": "id2",
                    "opacity": 1,
                    "color": "#ff0000"
                }
            ]

Same thing applies for links. All of them present with a 'default ' grey color.
I do not know, if I misread something or it is a bug.
Thanks in advance for your help.
Pan

@dpan7 thanks for reaching out. These parameters depend on what is configured using the accessor methods nodeColor, linkColor, nodeOpacity, linkOpacity.
By default, the 'color' attributes are plucked from the node/link objects, so your example should show nodes and links as red. Do you have any modifications to the default on nodeColor/linkColor?
Opacity cannot be set per node/link but is instead a property of the whole graph. It can be set by doing f.e.:
Graph
  .nodeOpacity(0.4)
  .linkOpacity(0.1)

Hi vasturiano,
Sorry for the late reply. I added the code for the opacity to the whole graph as you suggested and it worked!
Still, I cannot manage to make the 'color' to work (all the nodes are showed as black).
I have not made any modifications.
The value at the 'color' attribute should be in HEX?

Good to hear the opacity works. The color field should be a string supporting either rgb, hex or color names. So your data syntax looks correct. Do you have an example online of your code where this is not working?

I have put together a codepen (angular project). Unfortunately, I could not make it work with the imports, but I think that you get the notion of my code.
https://codepen.io/dpan7/project/editor/XWMezP
My goal, is to change the color of each node and later on to group nodes (under an attribute i.e. group or type) with the same color -- you ll see the attributes (gData), but I was not be able to do that either.
Honestly, I do not know what I am doing wrong.
Thanks again for your help. I much appreciated.

Thanks for the example. At a glance, I don't see anything lacking with your code. I would expect the three nodes to each have its own color (since they all have different "group").
Btw, about the imports, I notice you're not actually including the script tag for orbit controls, even though you're importing it. Could that be the issue?

Yes, the desirable outcome will be to see 3 nodes having different color. Moreover, I can see three nodes but in dark-grey color. Same thing applies when I declare the "color" attribute in my json. Again, no color changes detected :-(
Probably,it will be the issue in codepen, but in my local installation orbit controls and the project works fine.

Hi there,
Another issue that I have is that, I cannot change the link distance of a specific link.
Using the following code
this.myGraph.d3Force('link').distance(100);
I was able to change the distance of all links. My goal is to change the distance of a specific link.
However, when I use something like this
this.myGraph.d3Force('link').links(gData.links);
in order to re-compute the links distance, an error of missing node id was prompted.
Changed it to the following the error disappeared, but no changes to link distances occurred.
this.myGraph.d3Force('link').links(gData);
Is it possible to change the distance of a specific link? For example the link of  as stated in my JSON file.
  {
        "source": "id1",
         "target": "id5",
         "distance": 150,
         "type": "1",
         "group": "2"
      }

Do you have any insights? Thanks again for your time.
My JSON file is the following
const gData = {

            "nodes": [
                {
                    "id": "id1",
                    "name": "name1",
                    "description": "Quadtree 1",
                    "type": "1",
                    "group": 1,
                    "val": 1
                },
                {
                    "id": "id2",
                    "name": "name2",
                    "description": "Quadtree 2",
                    "type": "2",
                    "group": 2,
                    "val": 2
                },
                {
                    "id": "id3",
                    "name": "name3",
                    "description": "Quadtree 3",
                    "type": "3",
                    "group": 3,
                    "val": 1
                },
                {
                    "id": "id4",
                    "name": "name4",
                    "description": "Quadtree 1",
                    "type": "1",
                    "group": 1,
                    "val": 1
                },
                {
                    "id": "id5",
                    "name": "name5",
                    "description": "Quadtree 2",
                    "type": "2",
                    "group": 2,
                    "val": 2
                },
                {
                    "id": "id6",
                    "name": "name6",
                    "description": "Quadtree 3",
                    "type": "3",
                    "group": 3,
                    "val": 1
                }
            ],
            "links": [
                {
                    "source": "id1",
                    "target": "id2",
                    "distance": 50,
                    "type": "1",
                    "group": "2"
                },
                {
                    "source": "id2",
                    "target": "id3",
                    "distance": 50,
                    "group": "1",
                    "type": "2"
                },
                {
                    "source": "id4",
                    "target": "id5",
                    "distance": 50,
                    "type": "1",
                    "group": "2"
                },
                {
                    "source": "id5",
                    "target": "id6",
                    "distance": 50,
                    "group": "1",
                    "type": "2"
                },
                {
                    "source": "id1",
                    "target": "id5",
                    "distance": 150,
                    "color": "red",
                    "group": "1",
                    "type": "2"
                }

            ]
        };

@dpan7 great you got the nodes colors working! Makes perfect sense that the MeshLambertMaterial requires light to reflect. I didn't even think of that. Nicely done. :)
About your distance question, that's interesting. Well, by looking at the docs: https://github.com/vasturiano/d3-force-3d#link_distance
It seems like you'd be able to set custom distances per link by passing an accessor function instead of a number constant. Something like:
this.myGraph.d3Force('link').distance(link => link.distance)

No need to call the .links() method as the data should already be bound.
I'm going purely on theory here, haven't empirically tested, so let me know if you get it working. :)

Yes, you were right! It worked like a charm.
Thank you so much.


fix(deps): update dependency puppeteer to v3

This PR contains the following updates:

Package
Type
Update
Change

puppeteer
dependencies
major
2.1.1 -> 3.0.0

Release Notes

puppeteer/puppeteer
v3.0.0
Compare Source
Big changes

Chromium 81.0.4044.0 (r737027)
Puppeteer can now fetch a Firefox Nightly binary for you via PUPPETEER_PRODUCT=firefox npm install. Also, there’s now an example showing how to launch Firefox with Puppeteer.
File uploads are generally more reliable (#5363) and elementHandle.uploadFile(...filePaths) now triggers a change event, matching the old behavior in Puppeteer v1.20.0. (#5389)
Node.js v8.x.x is no longer supported. (#5136)

Behind the scenes

Puppeteer is migrating to TypeScript. Although this doesn't affect the way developers can consume Puppeteer, it improves the quality of the Puppeteer type definitions which can be used by modern editors.
Our custom test runner framework has been removed in favor of Mocha, reducing maintenance overhead.
Our CI setup and the way we deal with test flakiness is being reworked in order to increase our confidence of landing PRs without breaking anything.

Raw notes
6760b92 - chore: mark version v3.0.0 (#5642)
3387aab - feat(chromium): roll Chromium to r737027 (#5644)
c5df490 - docs(readme): update cross-browser FAQ (#5634)
35989a7 - fix: set revision based on PUPPETEER_PRODUCT (#5643)
d817ae5 - fix: update preferred revision after Launcher is created (#5640)
df81250 - chore: update ws library (#5638)
2529ee6 - chore(eslint): add eslint typescript linting (#5635)
88d843d - feat(TypeScript): move DeviceDescriptors to TS (#5595)
1ce4fe7 - chore(deps): update extract-zip to version 2 (#5610)
0bcc5a7 - chore: migrate remaining tests to Mocha (#5616)
17cd870 - chore: migrate unit tests to Mocha (#5600)
262da92 - chore(test): re-enable Firefox testing on CI (#5608)
83d9d53 - chore: update CI to run Travis + Linux + Chromium (#5583)
21c2d31 - docs(api): update another emulateMediaType example (#5607)
fefa8ca - docs(api): update emulateMediaType example (#5606)
bbdaf92 - docs(README): remove unused badges
efe561e - chore: fix DocLint method diffing (#5594)
841c2a5 - chore: fix emulateMedia tests (#5593)
8fa034b - chore: remove flakiness dashboard (#5592)
4ee2c43 - chore: fix Page.emulateMedia doclint failure (#5584)
a99a3cf - chore: skip failing cookie tests in Firefox (#5575)
88446df - chore: fix missed src/ vs lib/ documentation (#5591)
b3b0dc5 - docs: replace invalid device descriptors link (#5589)
99ecdba - docs: fix simple typo (#5585)
7f7887e - docs(puppeteer-firefox): add deprecation warning to README (#5502)
6522e4f - chore: Use expect for assertions (#5581)
4c41421 - chore: run Chromium on Node.js 12 on Travis (#5582)
f434684 - chore: fix link to source files in documentation (#5576)
2b52b86 - chore: remove travis-autodeploy (#5580)
7a2a41f - chore: move code to src/ and emit with TypeScript (#5568)
c82b556 - docs: connect works with any supported browser (#5572)
d678013 - chore: upgrade TypeScript to 3.8 (#5566)
3dff24a - chore: upgrade eslint to v6.8.0 (#5563)
4b0fd8b - chore: upgrade to TypeScript 3.7 (#5562)
29b626a - chore: upgrade TypeScript to 3.6 (#5559)
5e8d79b - chore: upgrade to TypeScript 3.5 (#5556)
b9240b1 - chore: bump rimraf to v3.0.2 (#5431)
067662c - Emit change event on uploadFile calls (#5389)
a3d1536 - Bugfix: Docker build failure (#5400)
33f1967 - (feat) Add option to fetch Firefox Nightly (#5467)
807fbbd - chore: drop Node.js v8 support (#5365)
0b1a9ce - chore: Replace Juggler with Firefox Nightly in CI (#5395)
0b1777e - docs(api) Fix url (#5367)
5ffcde2 - chore: bump version to v2.1.1.-post (#5390)
46386eb - chore: mark version v2.1.1 (#5388)
9923e56 - fix(filechooser): quick fix for the headful file chooser (#5369)
1a1ef83 - Add FAQ entry on cross-browser support (#5360)
0d243b7 - feat: make it possible to run install.js script with puppeteer-core (#5325)
c283fea - docs(api): add example to page.$$eval (#5200)

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

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

v5.0.28
GitHub release

Your semantic-release bot :package::rocket:


Add Serialize/Deserialize for TaprootSpendInfo

I think this is missing -- unless there is a reason not to have it?

builds on #908

Why?
When #908 is merged, #204f77 will be picked up by git and then this will merge cleanly onto that...

Merging #908 and keeping this one will either require rebase and re-ACK by all reviewers - or will create a duplicated commit in the history.

am i missing something about this workflow?
❯ git status
On branch master

No commits yet

nothing to commit (create/copy files and use "git add" to track)
❯ touch fi
❯ git add fi
❯ git commit -m 'A'
[master (root-commit) 22c6070] A
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 fi
❯ git checkout -b A
Switched to a new branch 'A'
❯ echo 'Hello' > fi
❯ git add -u
❯ git commit -m "hello"
[A 6ef0ad5] hello
 1 file changed, 1 insertion(+)
❯ git checkout -b B
Switched to a new branch 'B'
❯ echo 'Bye' >> fi
❯ git add -u
❯ git commit -m "bye"
[B 1270c31] bye
 1 file changed, 1 insertion(+)
❯ git checkout master
Switched to branch 'master'
❯ git merge A
Updating 22c6070..6ef0ad5
Fast-forward
 fi | 1 +
 1 file changed, 1 insertion(+)
❯ git merge B
Updating 6ef0ad5..1270c31
Fast-forward
 fi | 1 +
 1 file changed, 1 insertion(+)
❯ git  log --oneline
1270c31 (HEAD -> master, B) bye
6ef0ad5 (A) hello
22c6070 A

You are missing the fact that both branches should have the same commit, like in our case

❯ git log --oneline B
1270c31 (B) bye
6ef0ad5 (A) hello
22c6070 A
(END)

❯ git log --oneline A
6ef0ad5 (A) hello
22c6070 A
(END)

to be more clear, i've done merges with both #907 and #908 to show the results, either order is fine (altho 1 then 2 creates 1 fewer merge commit).
> git checkout -b master_copy
> git merge patch-2
> git merge patch-1
> git log --oneline
afb9d3e (HEAD -> master_copy) Merge branch 'patch-1' into master_copy
680add7 Merge branch 'patch-2' into master_copy
734b1de (origin/master, origin/HEAD) Merge rust-bitcoin/rust-bitcoin#897: Check
for SIGHASH_SINGLE bug in writer fn
2b942cf (fork/patch-1, patch-1) Add Serialize/Deserialize for TaprootSpendInfo
204f477 (fork/patch-2, patch-2) Add serde to TweakedPublicKey

❯ git checkout -b master_copy2
Switched to a new branch 'master_copy2'
❯ git merge patch-1
Merge made by the 'recursive' strategy.
 src/util/schnorr.rs | 2 ++
 src/util/taproot.rs | 1 +
 2 files changed, 3 insertions(+)
❯ git merge patch-2
Already up to date.

@dr-orlovsky you won't have "a duplicated commit in the history". Git will do the right thing when different PRs share a commit, as long as they are literally the same commit (as they are in this case).

Yep, it worked! I always thought that PRs based on other PRs must be drafts until the underlying PRs got merged... Perfect, thank you!

This feature got introduced about  six months to a year ago if I remember correctly. Also (just FYI for your own projects) in some situations you can target the PR that you depend on then only the relevant patches are shown (I think this is when the branch is on the same repo as master i.e., not a PR from personal fork).

Git has supported this for years, as a basic consequence of its DAG model. I'm not sure how Github could've broken that.


Add Sign in with google functionality

Integrate Google Sign-In to streamline user authentication and enhance security on our website.

Right now we are not integrating Google Sign in due to two different users : Student and Counsellor
You can work on security area , their are still bugs pending !


SourceKit-LSP crashes when selecting non-Xcode toolchain on macOS

Swift version
swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-22-a
Platform
macOS 15.0 beta
Editor
VS Code
Does the issue reproduce with Swift 6?
Yes
Description
I get an error
EverythingButTheBagelCore/Package.swift: {"code":null,"killed":false,"signal":"SIGSEGV","cmd":"/Library/Developer/Toolchains/swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-22-a.xctoolchain/usr/bin/swift package describe --type json"}

EverythingButTheBagelCore is the name of the package.
Steps to Reproduce
Install noted toolchain, switch to it in VS Code selecting workspace
Logging
% sourcekit-lsp diagnose
sourcekit-lsp diagnose collects information that helps the developers of sourcekit-lsp diagnose and fix issues.
This information contains:
- Crash logs from SourceKit
- Log messages emitted by SourceKit
- Versions of Swift installed on your system
- If possible, a minimized project that caused SourceKit to crash
- If possible, a minimized project that caused the Swift compiler to crash

All information is collected locally.

                                          Diagnosing sourcekit-lsp issues
 0% [-------------------------------------------------------------------------------------------------]
Collecting log messageszsh: segmentation fault  sourcekit-lsp diagnose

It does not appear that anything was generated. Where should it be?

Additional output from SourceKit LSP
[Info  - 5:12:33 PM] Connection to server got closed. Server will restart.
true
[Error - 5:12:33 PM] Server process exited with signal SIGSEGV.
[Info  - 5:12:34 PM] Connection to server got closed. Server will restart.
true
[Error - 5:12:34 PM] Server process exited with signal SIGSEGV.
[Info  - 5:12:34 PM] Connection to server got closed. Server will restart.
true
[Error - 5:12:34 PM] Server process exited with signal SIGSEGV.
[Info  - 5:12:35 PM] Connection to server got closed. Server will restart.
true
[Error - 5:12:35 PM] Server process exited with signal SIGSEGV.
[Info  - 5:12:36 PM] Connection to server got closed. Server will restart.
true
[Error - 5:12:36 PM] Server process exited with signal SIGSEGV.
[Error - 5:12:36 PM] Server process exited with signal SIGSEGV.
[Error - 5:12:37 PM] Request textDocument/documentSymbol failed.
Error: Connection is disposed.
	at Lt (/Users/fnord/.vscode/extensions/sswg.swift-lang-1.10.3/dist/extension.js:47:482)
	at Object.sendRequest (/Users/fnord/.vscode/extensions/sswg.swift-lang-1.10.3/dist/extension.js:47:2538)
	at _m.sendRequest (/Users/fnord/.vscode/extensions/sswg.swift-lang-1.10.3/dist/extension.js:55:113948)
	at async u (/Users/fnord/.vscode/extensions/sswg.swift-lang-1.10.3/dist/extension.js:55:55671)
	at async Object.provideDocumentSymbols (/Users/fnord/.vscode/extensions/sswg.swift-lang-1.10.3/dist/extension.js:106:8465)
	at async h.provideDocumentSymbols (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:153:98122)
[Error - 5:13:02 PM] Connection to server got closed. Server will not be restarted.

Synced to Apple’s issue tracker as rdar://130547854

Let me know if I should move this to the VS Code extension repo.

This is an issue in SourceKit-LSP (or the Swift toolchains in general), so SourceKit-LSP is the correct repo.
This started crashing sometime between swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-13-a and swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-18-a.
Finishes fine:
/Library/Developer/Toolchains/swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-13-a.xctoolchain/usr/bin/sourcekit-lsp diagnose --components logs

Crashes:
/Library/Developer/Toolchains/swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-18-a.xctoolchain/usr/bin/sourcekit-lsp diagnose --components logs

There were no changes to SourceKit-LSP between these two tags. Both are referring to 7ad1dcf2675abdc2c0a2dec6bbb95ea388f269f5.
The crash is in withCheckedThrowingContinuation. It seems like there was some change in Swift Concurrency that’s causing the crash. I’m checking with them to see if they know about something.
Thread 1 Crashed:
0   sourcekit-lsp                 	       0x10078d49c specialized withCheckedThrowingContinuation<A>(isolation:function:_:) + 108
1   sourcekit-lsp                 	       0x10078c63d Process.waitUntilExit() + 1
2   sourcekit-lsp                 	       0x1013d4eb5 DiagnoseCommand.addOsLog(toBundle:) + 1
3   sourcekit-lsp                 	       0x1013d929d closure #2 in DiagnoseCommand.run() + 1
4   sourcekit-lsp                 	       0x1013dcaa1 partial apply for closure #2 in DiagnoseCommand.run() + 1
5   sourcekit-lsp                 	       0x1013dc825 specialized DiagnoseCommand.orPrintError(_:) + 1
6   sourcekit-lsp                 	       0x1013d741d DiagnoseCommand.run() + 1
7   sourcekit-lsp                 	       0x1013d9a91 protocol witness for AsyncParsableCommand.run() in conformance DiagnoseCommand + 1
8   sourcekit-lsp                 	       0x10013e371 static AsyncParsableCommand.main() + 1
9   sourcekit-lsp                 	       0x10011cb61 specialized thunk for @escaping @convention(thin) @async () -> () + 1
10  libswift_Concurrency.dylib    	       0x25cef3949 completeTaskAndRelease(swift::AsyncContext*, swift::SwiftError*) + 1

As an aside swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-13-a crashed for me while swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-22-a appears to be working. I do not have the macOS or Xcode betas installed at the moment.

This was caused by https://github.com/swiftlang/swift/pull/74367, the following reduced example crashes on macOS 15.0 beta 2 (24A5279h).
$ cat ./crash.swift
let _: Int = try await withCheckedThrowingContinuation { continuation in
    continuation.resume(returning: 1)
}
$ /Library/Developer/Toolchains/swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-18-a.xctoolchain/usr/bin/swiftc crash.swift -sdk $(sdk); and ./crash
dyld[73180]: Symbol not found: _$ss31withCheckedThrowingContinuation9isolation8function_xScA_pSgYi_SSyScCyxs5Error_pGXEtYaKlF
  Referenced from: <C6DC9B57-F781-322E-BEEC-7E0F9958E6D3> /Users/alex/Desktop/crash
  Expected in:     <82723C8F-3EEF-354B-B355-CE94DA469AEE> /usr/lib/swift/libswift_Concurrency.dylib
fish: Job 1, './crash' terminated by signal SIGABRT (Abort)

The issue here is that the standard library included in macOS 15 beta 2 is incompatible with the standard library contained in swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-18-a – it contains the version of withCheckedContinutation that pre-dates https://github.com/swiftlang/swift/pull/72830, which is ABI-incompatible with the version of withCheckedContinutation included in swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-18-a because it doesn’t contain the isolation parameter. On earlier OSs, the back-deployment checks kick in but here that’s not the case – https://github.com/swiftlang/swift/pull/72830 is marked as being available in SwiftStdlib 6.0, aka macOS 15.0 and macOS 15 beta 2 is … macOS 15.
The best workaround for now is to

Download swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-13-a
Clone sourcekit-lsp
Build sourcekit-lsp using swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-13-a: /Library/Developer/Toolchains/swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-13-a/usr/bin/swift build
When using VS Code, point it to the just-built sourcekit-lsp using by adding the following setting in your settings.json: "swift.sourcekit-lsp.serverPath": "/path/to/sourcekit-lsp/.build/arm64-apple-macosx/debug/sourcekit-lsp". Ignore the deprecation warning that VS Code shows.

This should be fixed with the release of macOS 15. Note that the Swift open source toolchains are currently experiencing https://github.com/swiftlang/swift/issues/76534 but I’m closing this issue because it has been fixed.


clarifying copyright of data files

Hi, could you clarify the copyright or provenance of the data files in vtkplotter_examples/data ?  We need to make sure we're allowed to redistribute them.
grep -Eir '(copyright|©)' * gives a hit on various files apparently not covered by vtkplotter-examples' own MIT licence.
skyscraper.obj and shuttle.obj are the most problematic, since they explicitly indicate copyright "Viewpoint Datalabs International, Inc.  Copyright 1996", but with no indication of Licence to redistribute.
  I've been waiting for it to get processed in the Debian NEW queue. But your files look fine, safe to keep this bug closed.


[TODO] build and publish on npm

build and publish nlpO3-Node.js binding to npm

I found GitHub Action for publishing to NPM. https://github.com/marketplace/actions/npm-publish

Not sure if we need to compile the binaries as well. Never do anything like this before.
This could be useful https://neon-bindings.com/docs/publishing/

Can test it from https://www.npmjs.com/package/nlpo3
I don't think it will work on every platforms.


YADA-Admin :need to be able to delete a data source from the UI.

This will depend on functional security and roles-based ui configuration

current admin tool is obsolete.  deleting a datasource might be a security risk anyway.


how to start training ...

I want to know too, please help me

From the README.md:
How to reproduce?

Comment out these lines

Modify deep_q_network.py's parameter as follow:

OBSERVE = 10000
EXPLORE = 3000000
FINAL_EPSILON = 0.0001
INITIAL_EPSILON = 0.1

Thanks @tnarik ;)

please,what time need in cpu?

Reagan Enoch


Flow takes forever to type check functions with 9 polymorphic parameters

Here is a code snippet:
/* @flow */

type Decoded <value>
  = TypeError
  | value

type Decoder <value> =
  (input:any) =>
  Decoded<value>

export const tuple8 = <a, b, c, d, e, f, g, h, value>
  ( make:(a:a, b:b, c:c, d:d, e:e, f:f, g:g, h:h) => value
  , a:Decoder<a>
  , b:Decoder<b>
  , c:Decoder<c>
  , d:Decoder<d>
  , e:Decoder<e>
  , f:Decoder<f>
  , g:Decoder<g>
  , h:Decoder<h>
  ):Decoder<value> =>
  input => {
    if (Array.isArray(input) && input.length === 8) {
      const a$ = input[0](a)
      if (a$ instanceof TypeError) {
        return a$
      }

      const b$ = b(input[1])
      if (b$ instanceof TypeError) {
        return b$
      }

      const c$ = c(input[2])
      if (c$ instanceof TypeError) {
        return c$
      }

      const d$ = d(input[3])
      if (d$ instanceof TypeError) {
        return d$
      }

      const e$ = e(input[4])
      if (e$ instanceof TypeError) {
        return e$
      }

      const f$ = f(input[5])
      if (f$ instanceof TypeError) {
        return f$
      }

      const g$ = g(input[6])
      if (g$ instanceof TypeError) {
        return g$
      }

      const h$ = h(input[7])
      if (h$ instanceof TypeError) {
        return h$
      }

      return make(a$, b$, c$, d$, e$, f$, g$, h$)
    } else {
      return new TypeError('a Tuple of length 8')
    }
  }

On my 12inch macbook it takes > 10mins to type check.

Patient: "Doctor, it hurts when I do this."
Doctor: "Well, don't do that!"
But seriously, it seems like you're working around the issue from #854, but unfortunately polymorphic functions that are so heavily parameterized do an exponential blowup. It's a pretty well known thing internally, and basically all flow analysis tools suffer from it to some extent.
Hopefully some of the cleverer people on the Flow team will be able to deliver perf improvements there in the long term. In the near term, I'm hoping to deliver some new tools that will let you express the type you really want, instead of what I hope is a workaround. Even that is still months away, though.

It's not workaround for #854 or other issues. I run into this while porting Elm's decoder library:
http://package.elm-lang.org/packages/elm-lang/core/3.0.0/Json-Decode#tuple8


MIPROv2 looks for the single best demonstration instead of the best combination of demonstrations

I was looking at the code of MIPROv2 looking to understand how the Bayesian Optimization problem is formulated.
I was surprised to see that the code is modeling the selection of demo examples as a single categorical variable per predictor. This would translate to trying to find the best single demo example for each predictor. In contrast, in the paper aims to find

combinations of demonstrations (within and across modules)

To model that, I was expecting an array of boolean variables per predictor (one for each demo example). Each variable would map to the corresponding example being selected or not (assuming that order of demonstrations in the prompt does not matter).
The same observations about demo example selection seem to be true about MIPRO as well.
Is MIPRO and MIPROV2 focusing on single example selection intentionally done to reduce the search space? Or is this a bug?

Hey @lamflokas ! For each module, MIPRO has a single categorical variable for demonstration(s). The value is a list of demonstrations, which may have one or more items. This is consistent with the paper and is indeed to cut down the search space.

Thank you for the quick response!


Inconsistent library versions reminder.

Hi. I have implemented a tool to detect library version inconsistencies. Your project have 4 inconsistent libraries and 14 false consistent libraries.
Take javax.annotation:javax.annotation-api for example, this library is declared as version 1.3.2 in instrumentation/grpc, 1.3.1 in instrumentation/jaxrs2 and etc... Such version inconsistencies may cause unnecessary maintenance effort in the long run. For example, if two modules become inter-dependent, library version conflict may happen. It has already become a common issue and hinders development progress. Thus a version harmonization is necessary.
Provided we applied a version harmonization, I calculated the cost it may have to harmonize to all upper versions including an up-to-date one. The cost refers to POM config changes and API invocation changes. Take javax.annotation:javax.annotation-api for example, if we harmonize all the library versions into 1.3.2. The concern is, how much should the project code adapt to the newer library version. We list an effort table to quantify the harmonization cost.
The effort table shows the overall harmonization cost on APIs. It seems your project have no API invokes on this library, which could be safely upgrade to 1.3.2

Index
Module
NA(NAC)
NDA(NDAC)
NMA(NMAC)

1
instrumentation/grpc
0(0)
0(0)
0(0)

2
instrumentation/jaxrs2
0(0)
0(0)
0(0)

Also we provided another table to show the potential files that may be affected due to library API change, which could help to spot the concerned API usage and rerun the test cases.
If you are interested, you can have a more complete and detailed report in the attached PDF file.

hi. This is an instrumentation library, which intentionally supports different libraries with different versions. In general, please read issue template before unsolicited issues. This would have mentioned to come to gitter first with questions. bot-like behavior, even if well intention, can distract folks. No harm done, though and good luck!

Sorry this unsolicited issue...Currently we do not consider project environments, and library runtimes which false positive may arise. Thanks for your reply~ We will improve the tool in the future.

Sorry this unsolicited issue...Currently we do not consider project environments, and library runtimes which false positive may arise. Thanks for your reply~ We will improve the tool in the future.


feat: add oclif

Adds oclif (https://oclif.io/) to default rules

Update this too? https://github.com/keithamus/sort-package-json?tab=readme-ov-file#supported-libraries

Update this too? https://github.com/keithamus/sort-package-json?tab=readme-ov-file#supported-libraries

Done.


Allow executing image specific commands

For example allow prepending @:image_name or something else to identify where the command should be run. Maybe allow grouping like this: @:{image1, image2, image3}

implemented as of #14


[ISSUE #1194] Fix FileWebHookConfigOperation insert error

Fix FileWebHookConfigOperation insert error
Motivation
#1194
Modifications

Fix the FileLock release exception.
Fix queryWebHookConfigByManufacturer iterating condition, endIndex should be the inclusive bound.
Add unit test of insertWebHookConfig

Documentation
None

@horoc there are fail CI taslks needed to be fixed before merged.

@horoc please check the CI fail tasks.

@horoc please check the CI fail tasks.

Fixed, please help to review the changes, lots of thanks.


Unity Test Scene

Struggling to set up a scene to see what this looks like within Unity, would you mind setting up a tiny test scene so I could reverse engineer what's happening in the code?
Thanks!

Well, I was trying to make one, and found out that, because of the asence of custom shader editor, the shader itself is quite broken: normal maps does not work. I will fix this one and then proceed to the test scene.


add excludeFromTabOrder prop for Link and RadioGroup

Closes #6569
Add excludeFromTabOrder prop for Link and RadioGroup.
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

I didn't find that excludeFromTabOrder props appears somewhere in the stories or tests of other components. Let me know if I have to add story or tests.

Thanks for the PR. If you don't mind writing the tests, then you can know we won't accidentally regress in the future.

Added tests.

It's close now, thanks for your patience

It's close now, thanks for your patience

Thanks for the review and attention to detail. Added your code to the PR.

Thanks so much!

Thanks for the spectrum!  I need 1 more reviewer. Who can I add?

Closing for reason outlined here: https://github.com/adobe/react-spectrum/issues/6569#issuecomment-2229959686


Using GitSemVer in TFS builds/releases.

Hi,
I am not greatly familiar with msbuild and TFS, I am trying to use GitInfo semver variables when tagging my builds/releases in TFS. But they're not being resolved. Build runs successfully, just name tagging doesn't work correctly.
Do I need to expose $(GitSemVerMajor) etc as my own variables in .csproj?

Any help would be appreciated!

A diagnostics or detailed build log will show you is the properties are
being populated.
As to how to "tag" your source, the readme shows how to do it in C# and VB.
Otherwise, MSBuild props can be used directly when running other tools.
On Mon, Apr 3, 2017, 1:00 PM Alex March<EMAIL_ADDRESS>wrote:

Hi,
I am not greatly familiar with msbuild and TFS, I am trying to use GitInfo
semver variables when tagging my builds/releases in TFS. But they're not
being resolved. Build runs successfully, just name tagging doesn't work
correctly.
Do I need to expose $(GitSemVerMajor) etc as my own variables in .csproj?
[image: capture]
https://cloud.githubusercontent.com/assets/171876/24618381/c7bd135a-188e-11e7-8c18-0baf4cc4175d.PNG
Any help would be appreciated!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kzu/GitInfo/issues/29, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKW6xDWQ_itoiAPLfau8w8iedr6-Puwks5rsReAgaJpZM4Mxvpw
.

--
--
/kzu from mobile

Closing since I got no further response. Please reopen if after reading the readme, you still have doubts.
Thanks!


Please include option to see AppLocker policies configured via CSP

This commandlet is relying on policy (either local or via GPO). Another option to set AppLocker settings is via Configuration Service Provider (CSP) - please add viewing the settings set via CSP as an option.
Thanks in advance,

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

ID: 4b60297e-1e65-c5a3-5b47-d67a56ca552f
Version Independent ID: e8f885d5-683e-c781-eedf-624314be984a
Content: Get-AppLockerPolicy (applocker)
Content Source: docset/windows/applocker/Get-AppLockerPolicy.md
Product: w10
Technology: powershell-windows
GitHub Login: @andreabarr
Microsoft Alias: v-anbarr

The issue tracker of this repository is intended for product documentation issues.
Please consider consulting PowerShell UserVoice channel regarding your product feedback via the following link,
PowerShell UserVoice
You may also check relevant resources and ask the community for any other inquiries via PowerShell Community,
PowerShell Community
Thank you.


[openssl] Set linux-x32 for emscripten

Fixes https://github.com/microsoft/vcpkg/issues/37069.
Fixes #35688.
Tries to mitigate cmd command line length limitation.

cpr fixes are in #37152.

Thanks :)


⚠ Develop API Endpoint has degraded performance

In 517d551, Develop API Endpoint (https://develop.roblox.com/v1/toolbox/items?category=Hat&keyword=Hat) experienced degraded performance:

HTTP code: 200
Response time: 14904 ms

Resolved: Develop API Endpoint performance has improved in 8f1f02b.


Hide subflow category after deleting subflow

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Fixed https://github.com/node-red/node-red/issues/3979 by this pull request.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 68.257% when pulling 805f8a5ee75d0960374540f213ce76faf78890e0 on kazuhitoyokoi:master-fixpalette into 113d42ef35ccd55cb114c391fa3a55c7b8e94f18 on node-red:master.


brew update has inconsistent enthusiasm

Josephs-MacBook-Pro:Formula joe$ brew update
Already up-to-date!
Already up-to-date.

The first output is probably coming from Git as there's no such string in the Homebrew code. Do you have HOMEBREW_VERBOSE=1 in your environment?

Nope, no HOMEBREW_VERBOSE.

Josephs-MacBook-Pro:~ joe$ strings /usr/bin/git|grep Already
Already on '%s'
Already up-to-date.
Already up-to-date. Yeeah!
Already up-to-date!
Josephs-MacBook-Pro:~ joe$ strings /usr/local/bin/git|grep Already
Already on '%s'
Already up-to-date.
Already up-to-date. Yeeah!
Already up-to-date!
Josephs-MacBook-Pro:~ joe$

So yes, it's coming from git.

It seems to be caused by having an untracked file.

Also need to have HOMEBREW_DEVELOPER set.

It's git stash pop -q.

Closed via #320 2cd81e50513f96a657454031e52fa4aec773ea97


Support for ARM's listCredentials or equivalent

I was porting some ARM logic for provisioning and publishing to an Azure Container Registry (e.g., see this article) and ran into the need for listCredentials, which we don't seem to have an equivalent for (unless I am missing it). (Related to https://github.com/pulumi/pulumi-azure-nextgen/issues/37, however, this is different from many other built-ins, since it's not trivially replaceable by a language or library construct.) Is this something we intend to offer as a built-in function of this package? I can learn how to do it in the Azure SDK for each chosen language, but after a few moments of looking, that doesn't appear to be terribly straightforward.

We do support it.
Docs: https://www.pulumi.com/docs/reference/pkg/azure-nextgen/containerregistry/listregistrycredentials/
Example:  https://github.com/mikhailshilkov/temporal-samples/blob/main/azure-aks/temporal.ts#L53-L59
Unless you mean arm2pulumi issues?

I'll go ahead and close this. Feel free to report and further details / blockers and reopen if needed.


clients: move dummy container creation

This commit moves the dummy container creation task right before the
cephx keys creation task so it can't be run out of time.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1828105
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test centos-container-all_in_one

jenkins test centos-non_container-update


Update .gitattributes

Add working-tree-encoding to tell GitHub to perform the conversion from UTF-8 to CP1252 when cloning or downloading the repo as a .zip file.
This will make sure non-ascii characters don't get turned into �.

Thanks!

I realize that I was under the wrong impression that the files on GitHuhb were encoded in utf-8 while they are actually encoded in cp1252.
I think  the reason I made this mistake is that I tried to use the GitHub feature "Copy raw file"  in order to copy the content inside an existing VBA module. However, when I pasted the content, there were "?" where non-ascii characters should have been.

I don't normally use the "Copy raw file" feature,  so I was unaware that it should be avoided for non utf-8 files.
So, considering that the files are already encoded in cp1252, I would suggest to revert the change I made in this PR. Sorry for the trouble.


Explicitly support absolute swDest paths

R: @addyosmani @gauntface
CC: @freezy
At least one of the two issues reported in https://github.com/GoogleChrome/workbox/issues/1367 are due to webpack hanging when an absolute Windows path is used as a new asset filename. This PR should address that scenario by translating absolute paths into paths that are relative to the output directory.

Coverage increased (+0.03%) to 88.39% when pulling 12127bcabba8e3329e76b956bc7c37fb714407c3 on ensure-swdest-relative into ed2a847baf34c17c0f019d11cdfb1464fe3a9e19 on master.


Move API files to a src folder

Moves the API code into a src folder, to keep things nice and tidy. Also to avoid accidental name collisions etc.

Is it me or the chat.py file still exists in api, but that it's just empty? Or am I pulling incorrectly

nope, it's not you. Try git checkout separate-src && git reset --hard HEAD~4 && git pull

So, right now the structure is this:
.
├── Pipfile
├── Pipfile.lock
├── main.py
├── nixpacks.toml
├── prompteng
│   ├── data
│   │   ├── answers.csv
│   │   └── questions.csv
│   ├── prompteng.py
│   └── readme.md
├── setup.py
└── src
    ├── Stampy_chat.egg-info
    │   ├── PKG-INFO
    │   ├── SOURCES.txt
    │   ├── dependency_links.txt
    │   ├── requires.txt
    │   └── top_level.txt
    └── stampy_chat
        ├── __init__.py
        ├── chat.py
        ├── dataset_dl.py
        ├── env.py
        ├── followups.py
        └── get_blocks.py

And in prompteng/prompteng.py, there's the following code:
from pathlib import Path
import sys

sys.path = [str(Path(__file__).parent.parent)] + sys.path
from env import PINECONE_INDEX
from chat import talk_to_robot_simple, set_debug_print

My IDE is complaining at me. Wouldn't it make more sense to either import like this,
from ..src.stampy_chat.env import PINECONE_INDEX
from ..src.stampy_chat.chat import talk_to_robot_simple, set_debug_print

, or to restructure the code by e.g. moving prompteng in stampy_chat or something like that to make the import nicer?

good catch - it should be better now

I don't get why this would work. My tests seem to show that before the sys.path = [str(Path(__file__).parent.parent)] + sys.path  line, sys.path is "~/stampy-chat/api/prompteng", and after that line, sys.path is "~/stampy-chat/api". So right after when you import the index using from stampy_chat.env import PINECONE_INDEX, how does it find it, when the index is only in src.stampy_chat.env from stampy-chat/api's perspective? In any case, any reason why you think (1) is better than (2)?
(1)
sys.path = [str(Path(__file__).parent.parent)] + sys.path
from stampy_chat.env import PINECONE_INDEX
from stampy_chat.chat import talk_to_robot_simple, set_debug_print

(2)
from ..src.stampy_chat.env import PINECONE_INDEX
from ..src.stampy_chat.chat import talk_to_robot_simple, set_debug_print

sys.path is a list, at least it should be, so this should just prepend the parent folder. Which if you run it as pipenv run python prompteng/prompteng.py shouldn't be needed? I'm guessing this was to get round the python imports being from the parent folder. Which is why I prefer proper, fully qualified imports - you don't have to do this :D
I actually prefer option 3, i.e. just
from stampy_chat.env import PINECONE_INDEX
from stampy_chat.chat import talk_to_robot_simple, set_debug_print

without the path magic, but wanted to change as little as possible here

Ahhh I understand now, that makes sense. Thanks

(though there are still some IDE warnings from from stampy_chat.env import PINECONE_INDEX and from stampy_chat.chat import talk_to_robot_simple, set_debug_print)

I'll get round to those later :D


Libary betterend doesnt show up

Hello,
I tried to make a server with betterend mod but it just doesnt show the libary/crafts so i have to guess recipes and thats just hard to get stuff (could be that i just dont know how to toggle it but i tried nearly everything)

You can use REI to see all recipes


Updated handleClear() method

On click of clear search button, focus should be on Search box. If focus is not on search box, search content popup is not getting closed when clicked outside on page/form.
Steps to reproduce:

Go to demo page: https://codesandbox.io/s/react-multi-select-example-uqtgs
Search any random text in search box
Click on clear search button
Click anywhere outside of multiselect control
Focus is not in search box

In this case the search popup should be closed, which is not working currently.

@ganesh-sanap thanks for the PR but it looks like this doesn't solve complete problem, since focusType.SEARCH is wrongly pointed to -1 from my end, I think there might be another problem as well

@harshzalavadiya In that case, can you please make the changes so that when user clicks on "clear search button", focus should be set to "search textbox" automatically.

@harshzalavadiya Any updates on this?
Can you please make this change? We are using this control in our project & we have some dependencies on this particular issue.

@ganesh-sanap
as of now I'm working towards some major refactoring that will have this problem fixed from the core but it looks like you need this urgently so as of now I have applied following patch and created an canary release for you use react-multi-select-component@canary that should fix this issue
diff --git a/src/select-panel/index.tsx b/src/select-panel/index.tsx
index e19ec7f..c13374f 100644
--- a/src/select-panel/index.tsx
+++ b/src/select-panel/index.tsx
@@ -4,7 +4,7 @@
  * Select-all item, and the list of options.
  */
 import { css } from "goober";
-import React, { useCallback, useEffect, useMemo, useState } from "react";
+import React, { useCallback, useEffect, useMemo, useRef, useState } from "react";

 import { useMultiSelect } from "../hooks/use-multi-select";
 import { cn } from "../lib/classnames";
@@ -68,6 +68,7 @@ const SelectPanel = () => {
     ClearIcon,
     debounceDuration,
   } = useMultiSelect();
+  const searchInputRef = useRef<any>();

   const [searchText, setSearchText] = useState("");
   const [filteredOptions, setFilteredOptions] = useState(options);
@@ -116,6 +117,7 @@ const SelectPanel = () => {
   const handleClear = () => {
     setSearchTextForFilter("");
     setSearchText("");
+    searchInputRef?.current?.focus()
   };

   const handleItemClicked = (index: number) => setFocusIndex(index);
@@ -185,6 +187,7 @@ const SelectPanel = () => {
             onChange={handleSearchChange}
             onFocus={handleSearchFocus}
             value={searchText}
+            ref={searchInputRef}
           />
           <button
             type="button"

closing this for now


Issue with API

api is not working properly getting response like -->
code:"ENOENT"
errno:2
path:"/app/codes/4cfb0f33-3ec6-464e-8eed-be734ed1ab41.py"
status:500
syscall:"open"
timeStamp:1685425605602

i have same issue
is not working but GET list is working well
only POST is notworking
"timeStamp":<PHONE_NUMBER>221,
"status": 500,
"errno": -2,
"syscall": "open",
"code": "ENOENT",
"path": "/app/codes/b2bd8b11-c018-48f1-8218-8ac91a890c6d.java"

I'm facing the same problem. It worked fine like yesterday night. But today morning, it gave me a similar error.
{
  "timeStamp":<PHONE_NUMBER>999,
  "status": 500,
  "errno": -2,
  "syscall": "open",
  "code": "ENOENT",
  "path": "[/app/codes/89dfe7fe-f7c7-4c5a-8b20-4efafec68499.py](http://localhost/app/codes/89dfe7fe-f7c7-4c5a-8b20-4efafec68499.py)"
}

@Jaagrav, I know you're busy ( from your GitHub status). But, please take a look at it...

503 Service Unavailable
now it became code 503
<!DOCTYPE html>
<html lang="en">

<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1" />
	<title>Service Suspended</title>
</head>

<body>
	This service has been suspended.
</body>

</html>

I can confirm. I have the same issue, 'This service has been suspended.'
<!DOCTYPE html>
<html lang="en">

<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1" />
	<title>Service Suspended</title>
</head>

<body>
	This service has been suspended.
</body>

</html>

THE CODEX API IS BACK ONLINE !!!...
I don't know how, but the API has started working again. Maybe the API server might be down for some reason. But It's working now... This is my recent POST request and it turns out to be fine...
{
  "timeStamp":<PHONE_NUMBER>339,
  "status": 200,
  "output": "hello world\n",
  "error": "",
  "language": "py",
  "info": "Python 3.6.9\n"
}

@b-balajis or @Jaagrav, Please close this issue after verifying it...


Add ES Curator script

Cleans up old indices

Coverage remained the same at 100.0% when pulling c587ced97ab11adc2c45a75707cd7b6c59fc10e5 on es-cleanup-script into 3de5c7b5d3f375d67188cbd12c4bbad69c3f8c7f on master.

Coverage remained the same at 100.0% when pulling e7ad19ec50e8508b23e253609a842e9852e068ac on es-cleanup-script into 3de5c7b5d3f375d67188cbd12c4bbad69c3f8c7f on master.

Coverage remained the same at 100.0% when pulling 857bb81e6a8c1ed15ec149ea9454225485df4dff on es-cleanup-script into 3de5c7b5d3f375d67188cbd12c4bbad69c3f8c7f on master.

Coverage remained the same at 100.0% when pulling 778192a0af316ea5aadd6c338efbd134c04e364e on es-cleanup-script into 3de5c7b5d3f375d67188cbd12c4bbad69c3f8c7f on master.


Issue with createEffect using on/untrack on array signals

Describe the bug
After upgrading an app from SolidJs 1.3.13 to 1.6.3, some effects stopped updating/re-running when dependencies are updated. The effects use on() with a dependency list including a signal with an array, and when adding items to the array the effects no longer re-run as they did in 1.3.13. The playground link shows an example of this. The code is a simplified version of the application code, where a store is used to hold an array of objects. The store is updated using the produce() API. The example shows 4 methods to print the length of the array:

Setting a signal in a createEffect block;
Setting a signal in an On() block within createEffect, with the array as dependency
Setting a signal in an untrack() block within createEffect
Derived signal

In 1.3.13, all 4 methods work and clicking the "Test" button in the example updates all 4 printouts. In 1.6.3, methods 2 and 3 no longer work.
I noticed that if you change line 25:
on(items, (newItems) => {    to    on(() => items().map(x => x), (newItems) => {
the effect re-runs correctly on array change.
Your Example Website or App
https://playground.solidjs.com/anonymous/06bb0f7e-b134-48fe-8637-ab8a14fb5d05
Steps to Reproduce the Bug or Issue
Go to the playground link and click the Test button
Expected behavior
All 4 methods should work to detect updates to the array.
Screenshots or Videos
No response
Platform

OS: Windows
Browser: Firefox, Edge
Version: 1.6.3/1.6.4

Additional context
No response

Thanks for reporting. We made some changes in 1.4 to improve the efficiency of stores over notifying. Namely that updating an unrelated property would cause the top level object to notify unnecessarily. When in fact the only case where we wanted to do that is for arrays that change. Immutable changes or tracking length will work, but not tracking length no longer triggers. Let me see if there is a reasonable fix here.
I mean it's an interesting question. Because even patching length, there was some expectation that setting an index wouldn't cause the parent array to notify. Like the thing should list to the indexes it cares about or track the iterator. You should be able to set a new value in the index without everything that listens to a particular different index in the array getting notified.
The short solution is to use the $TRACK symbol..  const items = () => data.items[$TRACK]; but probably not desired as being like the global way to access that state. I'd consider making length special-cased (it already is) but I'm worried it sets up the wrong expectations that it will notify whenever indexes change by saying on items. It is probably worth acknowledging arrays are special but there is a certain question of whether they intentionally are being used like a list, vs some sort of Map-like block storage.
The current solution is more purist in that it only notifies when the items are changed Ie.. swapped. But I understand that isn't the intention here. on and untrack are really those sort of expert type APIs where you need to understand what you are doing since untracking the wrong thing loses reactivity.

Hi Ryan, thanks for the quick reply. I saw there were some fundamental changes with arrays in the versions between 1.3 and 1.6 so I wasn't all that surprised to see something break.
In this case though I don't see how the .length property is affecting this. As you can see in the example, a standard createEffect or a derived signal work just fine (case 1 and 4) to track changes to the array. Printing the length was just for demonstration purposes. And the .length is accessed within the on() and untrack() scopes (in case 2 and 3), so should not be considered for reactive updates. Only changes to the array itself should be notifying of changes, and the array itself (or the signal accessing the array) is the dependency into the on() function.
Here is another example that does not use .length, but copies the store array into the s1-s3 signals, and lists the contents in a  loop: https://playground.solidjs.com/anonymous/c9676aa8-07d7-4217-b382-82aafc23a30b
This is actually closer to the case I have in my application code.
Or am I misunderstanding something here in your explanation/Solid functionality, and the recent changes?

Yeah. When I talk about making length special I meant looking for a certain property to tell the parent to notify. Right now if you subscribe to items for it to trigger it needs to be replaced. Pushing to it will only set the last index, and update the length. So if you aren't subscribed to either of those then it won't re-run which is why the on and untrack versions aren't working.
I was commenting that maybe a length change should be something that triggers the array. But right now every piece is independent. Like if you have something like:
createEffect(() => console.log(items()[2]))

In the current behavior pushing wouldn't retrigger it if the array length is 3 or larger. Whereas triggering on length for example would. Or triggering on any array index would.

I see what you mean now, thanks for the explanation. I have now refactored my code to use ()=> items.().length as a dependency to on() and it works as before. It doesn't look quite as nice though :)
The new behavior makes sense for consistency/purist way as you mentioned, but it would be nice to have a built-in way to subscribe to changes in array structure (from push/pop/index assignment). Something similar could be done for regular objects, if you would like to subscribe to changes to any property on the object. Maybe a consistent API for arrays and objects could be developed here to subscribe to any change to the reactive source. But that may not fit with the fine-grained reactivity concept though, and moving more towards an observable event library.
Anyway I have things working again and understand the new behavior, thanks again for your help.


streams: Pass max-length parameters to stream info modal.

We were not passing max_stream_description_length and max_stream_name_length parameters to change_stream_info_modal template and thus the maxlength attribute was not being set correctly for the stream name and description input.
This PR updates the code to pass these parameters to template. This PR also removes these parameters from the data passed to stream_types template, since these parameters are not required there.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@timabbott this should be quick to review.

Merged, thanks @sahil839!
I wish we had a way to make Handlebars throw an exception if a parameter is missing.


Instructions on this page do not appear to work.

The instructions have either changed since this article was published or are incomplete.
I've setup a simple Chat channel and configured a Pre-Survey with a question key of Name.  Entering the name of a contact in the system does not automatically identify the customer record.
I've also tried the same with the setContextProvider API which does not work either:
<script>
function contextProvider(){
	return {
	 		'Name': {'value': 'Alex Wu', 'isDisplayable': true}
	 };
}

window.addEventListener("lcw:ready", function handleLivechatReadyEvent(){
	Microsoft.Omnichannel.LiveChatWidget.SDK.setContextProvider(contextProvider);
});

window.addEventListener("lcw:error", function handleLivechatErrorEvent(errorEvent){
	// Handle LiveChat SDK error event
	console.log(errorEvent);
});
</script>

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

ID: 9bb63ec2-6675-bfed-4661-edda6c56b488
Version Independent ID: 8f2de20d-a378-f8eb-87dd-b7a9112e189a
Content: Automatically identify customers using pre-chat responses and setContext API method
Content Source: ce/omnichannel/administrator/record-identification-rule.md
Service: dynamics-365-customerservice
GitHub Login: @neeranelli
Microsoft Alias: nenellim

The instructions have either changed since this article was published or are incomplete.
I've setup a simple Chat channel and configured a Pre-Survey with a question key of Name. Entering the name of a contact in the system does not automatically identify the customer record.
I've also tried the same with the setContextProvider API which does not work either:
<script>
function contextProvider(){
	return {
	 		'Name': {'value': 'Alex Wu', 'isDisplayable': true}
	 };
}

window.addEventListener("lcw:ready", function handleLivechatReadyEvent(){
	Microsoft.Omnichannel.LiveChatWidget.SDK.setContextProvider(contextProvider);
});

window.addEventListener("lcw:error", function handleLivechatErrorEvent(errorEvent){
	// Handle LiveChat SDK error event
	console.log(errorEvent);
});
</script>

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

ID: 9bb63ec2-6675-bfed-4661-edda6c56b488
Version Independent ID: 8f2de20d-a378-f8eb-87dd-b7a9112e189a
Content: Automatically identify customers using pre-chat responses and setContext API method
Content Source: ce/omnichannel/administrator/record-identification-rule.md
Service: dynamics-365-customerservice
GitHub Login: @neeranelli
Microsoft Alias: nenellim

@jkovacs-dev agree 100%, i tested the same thing with a simple pre-chat, doesn't work.

@jkovacs-dev
Hello, Jonathon! We have worked with the PMs and have made improvements to https://learn.microsoft.com/en-us/dynamics365/customer-service/configure-pre-chat-survey?tabs=customerserviceadmincenter. Please let me know if following the steps listed in the topic is helpful, or if you're still facing issues.

@jkovacs-dev
I haven't heard back from you and therefore, am closing this issue. Please feel free to reopen or contact me on Teams if you have any further feedback.
Best regards,
Manjusha


Packaging and deploying apps: Deploying self-contained applications

Issue tracking new topic at http://dotnet.github.io/docs/deployment/self-contained-apps.html

@rpetrusha Is this covered by the Deployment Concepts topic?

Yes. It's covered by .NET Core Application Deployment.


Failed to import - node-domexception

Failing module

GitHub: https://github.com/jimmywarting/node-domexception
npm: https://npmjs.com/package/node-domexception

import { something } from "https://esm.sh/node-domexception"

Error message
After onload I got this:
it tries to load an unnecessary worker_thread package that throws an error saying "it's not supported"
throw new Error("[esm.sh] " + "unsupported nodejs builtin module \"worker_threads\" (Imported by \"node-domexception\")")

Additional info

esm.sh version: uhm... current
Browser version: chrome 113.0.5672.92

node-domexception is a rather simple that really only should be imported in a NodeJS context. but that's beside that point i wished that my simple script:
if (!globalThis.DOMException) {
  try {
    const { MessageChannel } = require('worker_threads'),
    port = new MessageChannel().port1,
    ab = new ArrayBuffer()
    port.postMessage(ab, [ab, ab])
  } catch (err) {
    err.constructor.name === 'DOMException' && (
      globalThis.DOMException = err.constructor
    )
  }
}

module.exports = globalThis.DOMException

was more or less converted into something like this conditional top level await instead:
if (!globalThis.DOMException) {
  try {
    const { MessageChannel } = await import('https://esm.sh/error.js?type=unsupported-nodejs-builtin-module&name=worker_threads&importer=node-domexception'),
    port = new MessageChannel().port1,
    ab = new ArrayBuffer()
    port.postMessage(ab, [ab, ab])
  } catch (err) {
    err.constructor.name === 'DOMException' && (
      globalThis.DOMException = err.constructor
    )
  }
}

export default globalThis.DOMException

if that isn't possible then i would wish for dynamic required packages where more or less lazy evaluated instead... they should not be executed directly upon execution
they should look more or less something like this:
function lazySingleton() {
  throw new Error("[esm.sh] " + "unsupported nodejs builtin module \"worker_threads\" (Imported by \"node-domexception\")")
}

// always returns a function without ever executing something.
export default lazySingleton

then the conditional import would look more something like this:
/* esm.sh - esbuild<EMAIL_ADDRESS>es2022 production */
import __1$ from "/error.js?type=unsupported-nodejs-builtin-module&name=worker_threads&importer=node-domexception";
var x = Object.create;
var c = Object.defineProperty;
var d = Object.getOwnPropertyDescriptor;
var M = Object.getOwnPropertyNames;
var _ = Object.getPrototypeOf,
  g = Object.prototype.hasOwnProperty;
var h = (e => typeof require < "u" ? require : typeof Proxy < "u" ? new Proxy(e, {
  get: (o, t) => (typeof require < "u" ? require : o)[t]
}) : e)(function(e) {
  if (typeof require < "u") return require.apply(this, arguments);
  throw new Error('Dynamic require of "' + e + '" is not supported')
});
var m = (e, o) => () => (o || e((o = {
    exports: {}
  }).exports, o), o.exports),
  b = (e, o) => {
    for (var t in o) c(e, t, {
      get: o[t],
      enumerable: !0
    })
  },
  a = (e, o, t, l) => {
    if (o && typeof o == "object" || typeof o == "function")
      for (let s of M(o)) !g.call(e, s) && s !== t && c(e, s, {
        get: () => o[s],
        enumerable: !(l = d(o, s)) || l.enumerable
      });
    return e
  },
  n = (e, o, t) => (a(e, o, "default"), t && a(t, o, "default")),
  p = (e, o, t) => (t = e != null ? x(_(e)) : {}, a(o || !e || !e.__esModule ? c(t, "default", {
    value: e,
    enumerable: !0
  }) : t, e));
var i = m((w, f) => {
  if (!globalThis.DOMException) try {
    let {
      MessageChannel: e
-   } = __1$,
+   } = __1$(),
    o = new e().port1, t = new ArrayBuffer;
    o.postMessage(t, [t, t])
  } catch (e) {
    e.constructor.name === "DOMException" && (globalThis.DOMException = e.constructor)
  }
  f.exports = globalThis.DOMException
});
var r = {};
b(r, {
  default: () => O
});
var D = p(i());
n(r, p(i()));
var {
  default: u,
  ...E
} = D, O = u !== void 0 ? u : E;
export {
  O as
  default
};
/*! Bundled license information:

node-domexception/index.js:
  (*! node-domexception. MIT License. Jimmy Wärting <https://jimmy.warting.se/opensource> *)
*/
//# sourceMappingURL=node-domexception.mjs.map

i think this ☝ would be the correct way of handle dynamically required code if you can't solve things with top level await
the lazySingleton pattern dose not completely demonstrate the full potential.
it should obviously also cache the things that should be exported. so if you had a file that exported the current time:
module.exports = Date.now()

then it would more or less look like:

// always returns all code in a wrapped function without ever executing something.
function lazySingleton() {
  return {
    default: Date.now()
  }
}

let cachedResult
export default () => ( cachedResult ??= lazySingleton() )}

// import __1$ from "/error.js?type=unsupported-nodejs-builtin-module&name=worker_threads&importer=node-domexception";
const  __1$ = new Proxy({
  get() => {
    throw new Error("[esm.sh] " + "unsupported nodejs builtin module \"worker_threads\" (Imported by \"node-domexception\")")
  }
})

does this help?

or we can add a fake polyfill for worker_threads, just like https://github.com/esm-dev/esm.sh/blob/main/server/embed/polyfills/node_fs.js

just realize you're the author of the package, the best resolution is add browser field in your package.json
{
  "name": "node-domexception",
  "browser": {
    "worker_thread": false
  }
}

then esm.sh will handle it smart for browser target

Hmm, 🤔
i don't believe i'm going to do that. cuz as i said. i have found a other approach that don't make use of any worker_thread and instead relies on global atob instead (would require NodeJS v16 tough). And the more time that goes by the less i start to care about node-domexception cuz it's getting less and less irrelevant as it's not needed anymore.
I wish that this issue where more shifted towards "How can we solve lazy / conditional requirement"?

If you are curious what i would do instead then it just basically going to be this:
globalThis.DOMException ??= (() => {
  try { atob(0) } catch (err) { return err.constructor }
})()

No worker_threads 🙂

this feels like an issue from the package rather than the bundler, you really should have defined a custom "browser" field in package.json which would point to a file that simply returns the DOMException


[PoE2] - Unique price-checking

Describe the problem
When price-checking a unique item, you get its flavour text instead of its stats.
Having unique's stats to filter out is more important now in POE2 since corrupted ones can have their values above or below regular range and be worth way more.
To Reproduce
Steps to reproduce the behavior:

Try to price-check any unique
See its flavour text strings as a 'Not recognized modifier'

Expected behavior
Its actual stats with the min/max boxes.
Stats indeed available with the 'hidden' switch, but this feels wrong.
Screenshots

Yep, I just haven't gotten to uniques yet. tbh it just wasn't my priority since usually they are just 1ex max. This was a good note since I hadn't updated my working (#1) and not working (#2) features list in a while. They have now been updated and I'll link them in the pinned issue.
On a more specific note to Uniques, I still haven't looked at them yet. I'm going to leave this issue open as the top level one for uniques but more granular tracking can be found under milestone #4


Couldn't find documentation on buildpack.toml's api field

While creating my builder with pack create-builder, I saw this error:
ERROR: validating buildpacks: buildpack<EMAIL_ADDRESS>(Buildpack API version 0.1) is incompatible with lifecycle 0.4.0 (Buildpack API version 0.2)

However, I couldn't find any documentation that explains that api field should be set in buildpack.toml. If such documentation exists or is later on created, it would be nice to point at it in the warning.

The only reference in the docs currently is here https://buildpacks.io/docs/create-buildpack/building-blocks-cnb/.
It's purpose isn't well described, nor do we have a good documentation around which version of the buildpack interface / set of specified features are represented by buildpack API 0.1 vs 0.2. We should improve this.

However, I couldn't find any documentation that explains that api field should be set in buildpack.toml

Created buildpack/docs#66 to address this.

If such documentation exists or is later on created, it would be nice to point at it in the warning.

This is something we don't currently do but it's an interesting idea. I personally like it. I know of certain CLI tools that do it and it works really well. A concern I can see being voiced would be broken links. We'd have to be more careful about changes to documentation locations or provide redirects when we do make changes. That seems like a minor set back to what the benefits could be.


Uncaught TypeError: _this.notificationEl.querySelector is not a function

[Enter steps to reproduce:]

...
...

Atom: 1.18.0-dev-071ee3a x64
Electron: 1.3.15
OS: Ubuntu 16.04.2
Thrown From: particle-dev-complete package 1.0.1
Stack Trace
Uncaught TypeError: _this.notificationEl.querySelector is not a function
At /home/jules/.atom/packages/particle-dev-complete/node_modules/atom-package-deps/lib/view.js:22

TypeError: _this.notificationEl.querySelector is not a function
    at /packages/particle-dev-complete/node_modules/atom-package-deps/lib/view.js:22:58

Commands

Non-Core Packages
particle-dev-complete 1.0.1

It's possible we need to update atom-package-deps dependency.

What packages are missing? I tried adding the linter and linter-ui-default packages as suggested at the link below, but that didn't help me:
https://github.com/hebaishi/linter-gcc/issues/126

It's pretty annoying, I cannot install Particle IDE at all.

I'm getting the local IDE set up and had the same issue

I got an error which is identical to the one above. I tried installing the dependencies separately and got the following error:
apm install console-panel
Installing console-panel to /home/natalia/.atom/packages ✓
apm install tool-bar
Installing tool-bar to /home/natalia/.atom/packages ✓
apm install particle-dev
Installing particle-dev to /home/natalia/.atom/packages ✗

<EMAIL_ADDRESS>install /tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport
node-pre-gyp install --fallback-to-build

Failed to execute '/usr/share/atom/resources/app/apm/bin/node /usr/share/atom/resources/app/apm/bin/../node_modules/.bin/node-gyp configure --fallback-to-build --module=/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport/build/Release/serialport.node --module_name=serialport --module_path=/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport/build/Release' (1)
/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9
└── (empty)
npm WARN deprecated<EMAIL_ADDRESS>Use particle-api-js instead
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN excluding symbolic link test/server/static/ie8-polyfill.js -> ../../../ie8-polyfill.js
npm WARN excluding symbolic link test/server/static/ie8-polyfill.js -> ../../../ie8-polyfill.js
node-pre-gyp ERR! Tried to download(404): https://github.com/suda/node-serialport/releases/download/4.0.1/serialport-v4.0.1-electron-v1.3-linux-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(electron-v1.3 ABI) (falling back to source compile with node-gyp)
gyp ERR! configure error
gyp ERR! stack Error: Python executable "/usr/share/atom/resources/app/apm/bin/python-interceptor.sh" is v3.5.2, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack     at failPythonVersion (/usr/share/atom/resources/app/apm/node_modules/node-gyp/lib/configure.js:454:14)
gyp ERR! stack     at /usr/share/atom/resources/app/apm/node_modules/node-gyp/lib/configure.js:443:9
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:197:7)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at maybeClose (internal/child_process.js:877:16)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
gyp ERR! System Linux 4.4.0-79-generic
gyp ERR! command "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/.bin/node-gyp" "configure" "--fallback-to-build" "--module=/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport" "--module_path=/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport/build/Release"
gyp ERR! cwd /tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport
gyp ERR! node -v v6.9.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/share/atom/resources/app/apm/bin/node /usr/share/atom/resources/app/apm/bin/../node_modules/.bin/node-gyp configure --fallback-to-build --module=/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport/build/Release/serialport.node --module_name=serialport --module_path=/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport/build/Release' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:877:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
node-pre-gyp ERR! System Linux 4.4.0-79-generic
node-pre-gyp ERR! command "/usr/share/atom/resources/app/apm/bin/node" "/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/node_modules/particle-dev/node_modules/serialport
node-pre-gyp ERR! node -v v6.9.5
node-pre-gyp ERR! node-pre-gyp -v v0.6.36
node-pre-gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open '/tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/package.json'
npm WARN apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9 No description
npm WARN apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9 No repository field.
npm WARN apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9 No README data
npm WARN apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9 No license field.
npm ERR! Linux 4.4.0-79-generic
npm ERR! argv "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/natalia/.atom/.apm/.apmrc" "--userconfig" "/home/natalia/.atom/.apmrc" "install" "/tmp/d-117520-21346-s2jynx.zzifab57b9/package.tgz" "--runtime=electron" "--target=1.3.15" "--arch=x64" "--global-style"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/apm-install-dir-117520-21346-4wjxkf.ub7tgo80k9/npm-debug.log
npm ERR! code 1

I was able to work around by adding all the individual packages one at a time

I was also able to resolve by adding the individual packages. I may have gone a bit overboard, but here are all the packages I installed to get past the error:
apm install linter
apm install linter-ui-default
apm install particle-dev-cloud-functions
apm install particle-dev-cloud-variables
apm install particle-dev-profiles
apm install particle-dev-libraries
# NOTE: I still saw the error here. On boot atom suggested
# installing missing deps: particle-dev, tool-bar. Then it worked.
apm install particle-dev
apm install tool-bar

This error is caused by an outdated version of atom-package-deps package. We've updated it in all our packages so it should go away. There are still 3rd party packages that might have this bug. I created a [PR for linter-gcc(https://github.com/hebaishi/linter-gcc/pull/137) to fix it at least.


Feature Request: Support multiple accounts

It would be nice to have support for multiple accounts. Other clients do this, but am not sure how difficult it would be in the case of Tuuto (haven't dug into the code yet).

Thank you for your attention to this project.
Since I'm not a heavy user of mastodon, this project is not maintained anymore.


Improved Documentation: Added comments in application/worker.py

Added comments in difficult to understand areas in the file application/worker.py

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR introduces code comments to improve code readability and understanding. It doesn't alter the functionality of the code but enhances its documentation.

Why was this change needed? (You can also link to an open issue here)
This change was needed to make the code more comprehensible to developers, both current and future, who may need to work on or maintain this codebase. The added comments clarify the purpose of various code sections and components, making it easier to understand the logic and flow of the code.

Other information:
No other significant changes are introduced in this PR, and it doesn't break any functionality. The goal is to enhance code documentation and maintainability.

@larinam can you also look into this PR?
Thanks

Thank you @holopin-bot @THEGAMECHANGER416


Load data using dbt seed from .tpl file present in repository

Describe the bug
I have different types of files in my repo - .csv and .tpl and I want to run dbt seed command to load the data in snowflake.
When I run the command, it applies all the .csv files and ignores .tpl files.
How can I use dbt seed for other format data files?
Steps To Reproduce
In data folder, add few files with .csv format and some for .tpl
Run dbt seed command, it will apply csv files and igonors the tpl files
Expected behavior
I am looking to load data from different types of files instead of just from .csv
System information
Which database are you using dbt with?

[ ] snowflake

The output of dbt --version:
dbt=0.20.0-b1

@JyotiSingh7 Thanks for opening, you're in good company (https://github.com/dbt-labs/dbt/issues/2365).
I'm not familiar with .tpl-formatted data. (From what I see online, it's a way of storing template information, for web development?) Could you provide an example, or a little more by way of the specific use case you're after?

Hi @jtcohen6
Thanks for your response.
To give more context, I have a data folder which contains .csv & .tpl files. Eg:

File1.csv
File2.csv
File3.csv.tpl

File3.csv.tpl file looks like this:
CONFIG_KEY,CONFIG_VALUE,STATUS,DESCRIPTION
HostIP,{{ HOST_NAME }},Y,This is the APP VM Host Name/IP address.
SSHKeyFilePath,{{ SSH_KEY_PATH }},Y,This is the path on APP VM to the SSH key file for Login User

I want to replace the variables in my files during runtime and then seed all these files into my snowflake database. What is the best way to handle this use-case?

@JyotiSingh7 Got it! Seeds are intended for static data only; they can't take advantage of Jinja templating, as other dbt resources can.
I'd recommend you change File3.csv.tpl to be a model instead, and accomplish the runtime templating via dbt-Jinja functions var or env_var:
-- models/File3.sql

select
    'HostIP' as CONFIG_KEY,
    '{{ env_var('HOST_NAME') }}' as CONFIG_VALUE,
    'Y' as STATUS,
    'This is the APP VM Host Name/IP address' as DESCRIPTION

union all

select
    'SSHKeyFilePath' as CONFIG_KEY,
    '{{ env_var('SSH_KEY_PATH') }}' as CONFIG_VALUE,
    'Y' as STATUS,
    'This is the path on APP VM to the SSH key file for Login User' as DESCRIPTION

You could get fancier by including the static data in a seed, the dynamic inputs in a model, and joining on a common key.
In the meantime, I'm going to close this issue, since we don't plan to make seed files dynamic.


Remotely accessing tool outside LAN

@nmanovic
i want to execute CVAT on my website
i have done following changes on
1)changes in base.py
**line no 28:**
              ALLOWED_HOSTS = os.environ.get('ALLOWED_HOSTS',
                                    'localhost,<IP_ADDRESS>,labelytics.trantorglobal.com').split(',')
**line no 188 to 200:**
              UI_WITHOUT_PORT = UI_URL
              CORS_ORIGIN_WHITELIST = [UI_URL, UI_WITHOUT_PORT]

2)Changes in Docker-compose.yml
**added new code line no 56**
        ALLOWED_HOSTS: '*'
**line no 58**
        UI_HOST: labelytics.trantorglobal.com
**line no 81**
        REACT_APP_API_HOST: labelytics.trantorglobal.com

3)Changes in react_nginx.conf
added new code line no 6
add_header Access-Control-Allow-Origin "*";
if i am giving UI_HOST and REACT_APP_API_HOST as IP address insted of URL it is workig fine but it is not working on URL what should i do
I have attach all file along with server and URL
Please suggest me

@PavneshYadav123
Hi,
Now I can go to URL you specified and get access to your instance of CVAT.
At least login page works fine. The issue is relevant?

@bsekachev i have hosted tool on my site

@PavneshYadav123
I suppose you have solved the issue.
So, I'll close it for now. Don't hesitate reopen it if you have a question


Make build files automatically go into docs folder, not _book

@ericmkeen - glad you figured this out!


WIP: Beam topup plan attempt

Fist pass at making use of a suspender that pauses artemis when beam is being topped up (#127 )
Suspension conditions logic is copied from GDA into a new SynchrotronMonitor device.
A dummy plan that does nothing but print once a second is added; an endpoint is also added so that it can be run as curl -X PUT http://<IP_ADDRESS>:5000/dummy/start. A suspender using the topup_gate_signal signal of the SynchrotronMonitor is added to the run engine before executing the dummy plan. The plan should be paused whenever this signal is True, this sometimes happens, but usually does not. Running the same plan with the same configuration in the __main__ of beam_topup_plan.py gives the same behaviour, but also gives a useful error message:
Subscription value callback exception (Signal(name='monitor_topup_gate_signal', parent='monitor', value=True, timestamp=1663862377.5352824))
Traceback (most recent call last):
  File "/dls/science/users/zzg91958/python-artemis/.venv/lib/python3.10/site-packages/ophyd/ophydobj.py", line 474, in inner
    cb(*args, **kwargs)
  File "/dls/science/users/zzg91958/python-artemis/.venv/lib/python3.10/site-packages/bluesky/suspenders.py", line 145, in __call__
    raise RuntimeError("Could not create the ")
RuntimeError: Could not create the

The above problem Mathew is encountering is from /bluesky/suspenders.py,
`    def __make_event(self):
"""Make or return the asyncio.Event to use as a bridge."""
assert self._lock.locked()
if self._ev is None and self.RE is not None:
th_ev = threading.Event()
        def really_make_the_event():
            self._ev = asyncio.Event()
            th_ev.set()

        h = self.RE.loop.call_soon_threadsafe(really_make_the_event)
        if not th_ev.wait(0.1):
            h.cancel()
        return self._ev`

The wait time being 0.1 causes self._ev to not be set (it seems to not be enough time). Changing this to 1 seconds lets the suspender work fine.

Note: the problem persists with other suspenders - e.g SuspendFloor.

closing as stale but feel free to reopen


basic descriptions page

TP-??? Your PR title here

Why

What

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

Comparison is base (2430c9c) 92.79% compared to head (7e8f37c) 92.80%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1069   +/-   ##
=======================================
  Coverage   92.79%   92.80%
=======================================
  Files         460      460
  Lines       34258    34264    +6
  Branches     2616     2616
=======================================
+ Hits        31791    31797    +6
  Misses       1969     1969
  Partials      498      498

Files
Coverage Δ

commodities/urls.py
100.00% <ø> (ø)

commodities/views.py
99.09% <100.00%> (+0.02%)
:arrow_up:

common/models/trackedmodel.py
94.32% <ø> (ø)

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


feat: chapter 2 - interactive user interfaces

Chapter 2: Interactive User Interfaces
This pull request adds a new feature to the application.
Topics Covered

Creating a New Class
Updating the Layout
Wiring Up the User Interface
Adding an Icon
Screen Pixel Densities

How to Test
To test the new feature, you can do the following:

Clone the repository.
Install the dependencies.
Run the application.
The new feature should be available.

Screenshots

Known Issues
There are no known issues with this pull request.
References
Reviewers
Thanks!

Looks good to me.


adding curser pointer in the footer links

Is your feature request related to a problem? Please describe.
when someone hovers over the footer links. its curser does not change into pointer. so it becomes quite confusing to the user whether is this clickable or not.

Describe the solution you'd like
it would be helpful to users to change the curser into pointer by hover over the likes.
I would like to work on this issue.
kindly assign it to me under GSSOC'23 contributor
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

We appreciate your feedback regarding the issue with the footer links. We have addressed the problem, and the cursor now changes to a pointer on hover. Thank you for bringing this to our attention, and we value your contribution to improving our user experience. If you have any more suggestions or encounter any other issues, please don't hesitate to reach out.


Doesn't work with CDN

Expected Behavior
Should work with CDN
Actual Behavior
Doesn't work with CDN
Reproduction
Steps to reproduce the issue:

check here https://codepen.io/faizanrupani/pen/ExQeQLp

Screenshots

Environment

Browser(s): All
Operating System (e.g. Windows, macOS, Ubuntu): macOS

It doesn't work in the sample you provided because not all the required steps are set. In addition to fetching the lib it needs to be configured as displayed in usage chapter of the README.
You can also check how I do it in the website.
If it still does not work out please let me know, happy to reopen the question / issue if that would be the case.