Deploy webhook by default and enable e2e

@wainersm @stevenhorsman this is an attempt to deploy webhook as part of the installation so that number of peer pods that can be created is constrained by the per node limit. A docker provider specific test is added as well. I can enable the test for other providers but before doing it wanted to get your feedback on the approach.

Do you think this is needed before 0.10.0 release, or can it wait until after?

@stevenhorsman this can wait.

@stevenhorsman @wainersm  I added a commit to use const for some test images and using test images from  quay to avoid the rate limiting. I can create a separate PR as well but thought of including with this as it's being reviewed.
Let me know if you want me to create a separate PR for the above change..

@stevenhorsman @wainersm I added a commit to use const for some test images and using test images from quay to avoid the rate limiting. I can create a separate PR as well but thought of including with this as it's being reviewed. Let me know if you want me to create a separate PR for the above change..

I'm not against it, but pretty disappointed that I made a similar change back in July and you didn't approve it as you wanted them moved out to a separate file and then when I worked on it and hit problems I was ignored 🤷

@stevenhorsman @wainersm I added a commit to use const for some test images and using test images from quay to avoid the rate limiting. I can create a separate PR as well but thought of including with this as it's being reviewed. Let me know if you want me to create a separate PR for the above change..

I'm not against it, but I'm pretty disappointed that I made a similar change back in July and you didn't approve it as you wanted them moved out to a separate file and then when I worked on it and hit problems I was ignored 🤷

Oh sorry about it. I faced so much issues with the docker rate limit that I had to manually create and push the image to quay. I'll remove the changes

Oh sorry about it. I faced so much issues with the docker rate limit that I had to manually create and push the image to quay. I'll remove the changes

For what it's worth, I think the image updates should go in and I think it's better than our current code, which is why I made a similar PR, I regret that it was blocked earlier, not that you've done it here.

@stevenhorsman @wainersm I added a commit to use const for some test images and using test images from quay to avoid the rate limiting. I can create a separate PR as well but thought of including with this as it's being reviewed. Let me know if you want me to create a separate PR for the above change..

I'm not against it, but I'm pretty disappointed that I made a similar change back in July and you didn't approve it as you wanted them moved out to a separate file and then when I worked on it and hit problems I was ignored 🤷

Oh sorry about it. I faced so much issues with the docker rate limit that I had to manually create and push the image to quay. I'll remove the changes

I have removed the commit. And apologise again. I may have thought about moving the image names to a separate file and instead added it as constants to the same file

there seems to be a problem with the cert-manager installation, see test run

there seems to be a problem with the cert-manager installation, see test run

I tried running this manually and it seemed to work, so I'll re-run it just incase there was just some slowness in the CI

So in my gh hosted runner trial, I added trace output and got the following error:
time="2024-10-17T12:43:04Z" level=info msg="Installing cert-manager"
time="2024-10-17T12:43:07Z" level=trace msg="/usr/bin/make -C ../webhook deploy-cert-manager, output: make[1]: Entering directory '/home/runner/work/cloud-api-adaptor/cloud-api-adaptor/src/webhook'\ncurl -fsSL -o cmctl [https://github.com/cert-manager/cmctl/releases/latest/download/cmctl_linux_amd64\nchmod](https://github.com/cert-manager/cmctl/releases/latest/download/cmctl_linux_amd64/nchmod) +x cmctl\n# Deploy cert-manager\nkubectl apply -f [https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml\nerror:](https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml/nerror:) error validating \"[https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml\](https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml/)": error validating data: failed to download openapi: Get \"http://localhost:8080/openapi/v2?timeout=32s\": dial tcp [::1]:8080: connect: connection refused; if you choose to ignore these errors, turn validation off with --validate=false\nmake[1]: *** [Makefile:130: deploy-cert-manager] Error 1\nmake[1]: Leaving directory '/home/runner/work/cloud-api-adaptor/cloud-api-adaptor/src/webhook'\n"
F1017 12:43:07.161828   18745 env.go:369] Setup failure: exit status 2
FAIL	github.com/confidential-containers/cloud-api-adaptor/src/cloud-api-adaptor/test/e2e	419.964s

however I'm not sure if this is helpful and the same issue we might be hitting here as the gh-runner is tight on disk space

So in my gh hosted runner trial, I added trace output and got the following error:
time="2024-10-17T12:43:04Z" level=info msg="Installing cert-manager"
time="2024-10-17T12:43:07Z" level=trace msg="/usr/bin/make -C ../webhook deploy-cert-manager, output: make[1]: Entering directory '/home/runner/work/cloud-api-adaptor/cloud-api-adaptor/src/webhook'\ncurl -fsSL -o cmctl [https://github.com/cert-manager/cmctl/releases/latest/download/cmctl_linux_amd64\nchmod](https://github.com/cert-manager/cmctl/releases/latest/download/cmctl_linux_amd64/nchmod) +x cmctl\n# Deploy cert-manager\nkubectl apply -f [https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml\nerror:](https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml/nerror:) error validating \"[https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml\](https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml/)": error validating data: failed to download openapi: Get \"http://localhost:8080/openapi/v2?timeout=32s\": dial tcp [::1]:8080: connect: connection refused; if you choose to ignore these errors, turn validation off with --validate=false\nmake[1]: *** [Makefile:130: deploy-cert-manager] Error 1\nmake[1]: Leaving directory '/home/runner/work/cloud-api-adaptor/cloud-api-adaptor/src/webhook'\n"
F1017 12:43:07.161828   18745 env.go:369] Setup failure: exit status 2
FAIL	github.com/confidential-containers/cloud-api-adaptor/src/cloud-api-adaptor/test/e2e	419.964s

however I'm not sure if this is helpful and the same issue we might be hitting here as the gh-runner is tight on disk space

May be something is different in the way gh action is running, that's why we see the error only in gh action workflow.
I have added a commit to install cert-manager via kcli_cluster.sh. Let's see.

With this different flow, at least the error seems to be clear
mutatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created
validatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created
error: timed out waiting for the condition on endpoints/cert-manager

Retrying with increased timeout for cert-manager deployment

With this different flow, at least the error seems to be clear
mutatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created
validatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created
error: timed out waiting for the condition on endpoints/cert-manager

Retrying with increased timeout for cert-manager deployment

Initial install of cert-manager succeeded. However when running make -C ../webhook deploy-cert-manager via provision.go failed. This mostly reapplies the yamls which is pretty quick and should have succeeded. Increased the kubectl wait timeout and rechecking.

@stevenhorsman Now I see this error "Error from server: error when creating "https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml": etcdserver: request timed out"
Is installed cert-manager overwhelming the k8s cluster and the config needs to be changed?

@stevenhorsman Now I see this error "Error from server: error when creating "https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml": etcdserver: request timed out" Is installed cert-manager overwhelming the k8s cluster and the config needs to be changed?

I think it's more likely that the runner is struggling - the default kcli set-up is 4 vCPU and 6GB RAM for each of the nodes, but the az-ubuntu-2204 runner only has 4vCPUs available, so maybe the extra stuff means kcli is starting to try and use more that is available?

@stevenhorsman @mkulke tried few options and nothing works in CI w.r.to setting up cert-manager with libvirt. Looks like it's something to do with resource availability (see earlier errors on etcd server timeout). No issues in local runs.
What's the way forward ?

@stevenhorsman @mkulke tried few options and nothing works in CI w.r.to setting up cert-manager with libvirt. Looks like it's something to do with resource availability (see earlier errors on etcd server timeout). No issues in local runs. What's the way forward ?

Could we try using a Standard_D8_v4 VM instead to see if that helps as it might help us rule in/out the resource pressure theory. I guess that would need to updated in garm?
We good also try testing it locally on a 4 vCPU VM to see if we reproduce the errors there?

Do you have the cpu and memory spec of the runner?

Do you have the cpu and memory spec of the runner?

The current runner is: https://cloudprice.net/vm/Standard_D4s_v4

yes, I guess we can do that. but I'm not sure we want the instance to be bumped to 2x the size, I think the same runner pool is also used by a different jobs. we could create a discrete pool az-ubuntu2204-large or something and switch the runner type on the libvirt workflow.
but that puts our plans to switch to github-hosted runners on hold I suppose? I'm a bit surprise to see that we cannot make it work with 16gb of ram.

yes, I guess we can do that. but I'm not sure we want the instance to be bumped to 2x the size, I think the same runner pool is also used by a different jobs. we could create a discrete pool az-ubuntu2204-large or something and switch the runner type on the libvirt workflow.
but that puts our plans to switch to github-hosted runners on hold I suppose? I'm a bit surprise to see that we cannot make it work with 16gb of ram.

I don't know whether the CPU, or RAM is the bottleneck, so I figured just trying 8 and 32GB would let us know if it's resource at all and then (if we can find matching profiles) trying 8 vCPU and 16GB and/or 4 vCPU and 32GB RAM would let us know which one is under pressure. I can try those combinations next week with VMs manually though to see if that gives more info.

I don't know whether the CPU, or RAM is the bottleneck, so I figured just trying 8 and 32GB would let us know if it's resource at all and then (if we can find matching profiles) trying 8 vCPU and 16GB and/or 4 vCPU and 32GB RAM would let us know which one is under pressure. I can try those combinations next week with VMs manually though to see if that gives more info.

I bumped the pools instance type to Standard_D8s_v4

that didn't help when re-running the test. I would suggest to copy the workflow, throw everything coco-related out and just try to install cert-manager after kubeadm set up the cluster.

I also checked it locally on a 4 CPU, 16GB VM locally and the cert-manager install worked fine there, so maybe the resource usage idea is a bust?

I also checked it locally on a 4 CPU, 16GB VM locally and the cert-manager install worked fine there, so maybe the resource usage idea is a bust?

I have also been unable to recreate this locally.
The reason for guessing it's due to resource availability is because of etcd server timeout error:
https://github.com/confidential-containers/cloud-api-adaptor/pull/2066#issuecomment-2422275138
@mkulke in one of the previous runs, I had installed cert-manager just after kubeadm cluster install. But the CI provisioner still failed during checking for the service endpoints
https://github.com/confidential-containers/cloud-api-adaptor/pull/2066#issuecomment-2421636234
I added more logs and some hacks to retry. Let's see..

I logged the errors instead of using Trace, and see this. It's trying to access localhost which might indicate issue with kubeconfig.
time="2024-10-21T13:55:30Z" level=info msg="Error  in install cert-manager: exit status 2: make[1]: Entering directory '/home/runner/actions-runner/_work/cloud-api-adaptor/cloud-api-adaptor/src/webhook'\ncurl -fsSL -o cmctl [https://github.com/cert-manager/cmctl/releases/latest/download/cmctl_linux_amd64\nchmod](https://github.com/cert-manager/cmctl/releases/latest/download/cmctl_linux_amd64/nchmod) +x cmctl\n# Deploy cert-manager\nkubectl apply -f [https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml\nerror:](https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml/nerror:) error validating \"[https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml\](https://github.com/jetstack/cert-manager/releases/download/v1.15.3/cert-manager.yaml/)": error validating data: failed to download openapi: Get \"http://localhost:8080/openapi/v2?timeout=32s\": dial tcp <IP_ADDRESS>:8080: connect: connection refused; if you choose to ignore these errors, turn validation off with --validate=false\nmake[1]: *** [Makefile:130: deploy-cert-manager] Error 1\nmake[1]: Leaving directory '/home/runner/actions-runner/_work/cloud-api-adaptor/cloud-api-adaptor/src/webhook'\n"

@mkulke @stevenhorsman the KUBECONFIG setting was the culprit. The previous run was successful. Redoing it again by tidying up the commits.


Server not reading params.switch from POST

When posting to the Docker container using a body such as:
{
    "params": {
        "switch": "on",
    },
    "deviceid": "xxxxxxx"
}

The server crashes and logs the following:
file:///usr/src/app/server/server.js:31
    const requestedActionOnDevice = req.body.params.switch != undefined && req.body.params.switch != "" ? String(req.body.params.switch) : undefined;
                                                    ^

TypeError: Cannot read property 'switch' of undefined
    at file:///usr/src/app/server/server.js:31:53
    at Layer.handle [as handle_request] (/usr/src/app/server/node_modules/express/lib/router/layer.js:95:5)
    at next (/usr/src/app/server/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/usr/src/app/server/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/usr/src/app/server/node_modules/express/lib/router/layer.js:95:5)
    at /usr/src/app/server/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/usr/src/app/server/node_modules/express/lib/router/index.js:335:12)
    at next (/usr/src/app/server/node_modules/express/lib/router/index.js:275:10)
    at jsonParser (/usr/src/app/server/node_modules/body-parser/lib/types/json.js:119:7)
    at Layer.handle [as handle_request] (/usr/src/app/server/node_modules/express/lib/router/layer.js:95:5)```

Turns out the issue was with the Content-Type header in my POST.  This needs to be set to application/json and not text/plain as I had it.

Glad you figured out. Always feel free to report bugs/feature requests etc :)


Add My Projects and New Project pages

Related Issue
this pr fixes issue #172.
Description
I have added a new menu item for view their own projects.
I have created MyProjects.jsx which display the list of projects published.
I have created NewProject.jsx which display a form for uploading a new project.
I have added fields like, project name, repo link, description, image, and skills used. I have implemented validations for input fields as well.
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
https://github.com/SUGAM-ARORA/UniCollab/assets/139672976/fb1fd977-44f0-4f5a-96e1-7acb50bb662a

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[] I have commented my code, particularly in hard-to-understand areas.

Additional context:

@DharshiBalasubramaniyam Update your branch with latest updates. If you face any problem then try these steps:
git checkout main
git pull
git checkout
git merge main
[ ... resolve any conflicts ... ]
git add [files that were conflicted]
git commit
git push

@SUGAM-ARORA I have updated the branch. Kindly please review my pr.

@DharshiBalasubramaniyam Just do branch update once again . I will merge this then

@DharshiBalasubramaniyam Just do branch update once again . I will merge this then

done!


Img previews

of uploaded content
Addresses #4

Would be nice to have something like: http://jslightbox.felixhagspiel.de


I don't understand how to interpret the result from getTextContent

I am using pdf.js to do understand the text layout of pdf documents. However, I am having trouble understanding the information returned by getTextContent.  Sometime it appears that I have to scale the height for each item by the vertical scale in the transform, i.e., transform[3].  Othertimes I don't.  I have no idea how to determine when I have to and when I don't.  Below are two examples from different pdf documents.  In the first, I should not scale the height. In the second, I should.  Does anyone know how I can figure this out?
-- Result from Document 1 (In this case the font is 14pt)

{str:"one two three four",
 dir:"ltr",
 width:151.67308125000002,
 height:20.6625,
 transform:[20.6625,0,0,20.6625,110.854,651.853],
 fontName:"g_d0_f1"}

{fontFamily:"sans-serif",
 ascent:0.694,
 descent:-0.195}

-- Result from Document 2 (In this case the font is 8pt)

{str:"some text goes here to see if 101 and 2011xx: 1–8",
 dir:"ltr",
 width:171.72799999999987,
 height:64,
 transform:[8,0,0,8,30,684.5359],
 fontName:"g_d0_f1"
}

{fontFamily:"serif",
 ascent:0.883,
 descent:-0.217}

(this is also posted on stackoverlow)

1

See https://github.com/mozilla/pdf.js/blob/master/examples/text-only/pdf2svg.js example comments.

@yurydelendik
By pageLoaded, it doesn't mean the whole pdf has to be rendered, right?
function pageLoaded() {
  // Loading document and page text content
  pdfjsLib.getDocument({url: PDF_PATH}).then(function (pdfDocument) {
    pdfDocument.getPage(PAGE_NUMBER).then(function (page) {
      var viewport = page.getViewport(PAGE_SCALE);
      page.getTextContent().then(function (textContent) {
        // building SVG and adding that to the DOM
        var svg = buildSVG(viewport, textContent);
        document.getElementById('pageContainer').appendChild(svg);
      });
    });
  });
}


How do you handle fluctuations in latency measurement?

I noticed that the measured latencies differ substantially from run to run.
For example I get following results at different program runs:

BasicResidual_downup_2x_H24_W24_Cin80_Cout80_stride1: 0.0549 ms
BasicResidual_downup_2x_H12_W12_Cin80_Cout80_stride1: 0.0511 ms
BasicResidual_downup_2x_H24_W24_Cin80_Cout80_stride1: 0.0517 ms
BasicResidual_downup_2x_H12_W12_Cin80_Cout80_stride1: 0.0502 ms
BasicResidual_downup_2x_H24_W24Cin80_Cout80_stride1: 0.0505 ms
BasicResidual_downup_2xH12_W12_Cin80_Cout80_stride1: 0.0513 ms

Note that in the last run the operation on quarter resolution (12x12) took longer than the operation on the base resolution (24x24).
This will substantially influence the network-architecture search as the optimizer will prefer pathes on higher resolutions.
How did you make sure that your measured latencies "make sense"? Did you set static GPU clocks or similar to get stable results?

Hi @maaft !
Feature maps of 12x12 or 24x24 are very small. In Cityscapes, a feature map of 1/32 scale have a size of 32x64. Fluctuations in these feature maps have a small impact on the overall latency of the whole network (1000/163.9 = 6.1ms in our network v.s. ~0.05ms in your case).
As demonstrated in our Figure 3, our latency estimation achieves a very high correlation with real latency. This correlation is verified by sampling 1,000 subnetworks.

Okay, this of course makes latency-based NAS very hard for applications with smaller images.
Until I find a better solution, I will just multiply the height and width during latency measurement with a constant factor (8 in my case) which will result in stable results but will not reflect the real-latency. But at least the relative latencies between different operations are at least correctly estimated.


ssh_exchange_identification: read: Connection reset by peer

$ git push deis-staging master
ssh_exchange_identification: read: Connection reset by peer
fatal: Could not read from remote repository.

Workflow was installed 2 years ago on GKE. How can I debug it and resolve the issue? This issue happened several days ago.

Looks like this issue is related to teamhephy/builder. Should I open the issue there and close it here?

Looks like an ssh connectivity problem. Can you check the SSH key that you are using is valid in pushing to the git deis-builder remote?
Also, it could be that the IP or domain has not changed for the deis-builder git remote.
git remote get-url deis-staging

Another thing to check is to see if the deis remote is correct and the name of the app is still correct in the above output.
Also check if the deis-builder is up and running.
kubectl get pods -n deis | grep -i "deis-builder"

Hi @Cryptophobia. Key is correct. Remote is correct. I can't deploy changes for any app. No one from my team can do it too.
$ kubectl get pods -n deis | grep -i "deis-builder"
deis-builder-1364651073-tmkzz                            0/1     CrashLoopBackOff   2107       548d

$ kubectl --namespace=deis logs deis-builder-1364651073-tmkzz 2019/11/17 19:29:17 Error creating storage driver (googleapi: got HTTP response code 400 with body: )

This seems to be the same error some users are experiencing with deis-builder on off-cluster Google Storage objectstore. Some of them have migrated to S3 in order to mitigate the issue while it is being investigated by the Google Cloud support team.
Are you able to join our Slack channel and see what the latest is on this issue? https://slack.teamhephy.com

@Cryptophobia thanks.

Haven't heard any more information related to this issue so I will go ahead and close it for now. Join our Slack or report another issue if this persists.


Extend available types for safe_save

Saving tensors of certain types (e.g. doubles, bools, shorts) currently fails. I have added a unit test to show that they fail. Adding the missing dtypes to safe_dtypes enables the unit test to run successfully.
Please note that there may be a very good reason that safe_dtypes did not already include the dtypes that I added. Please let me know if that is so. The unit test does assert that the saved and loaded tensors are the same, but maybe I am missing something else.
Please feel free to suggest any modifications.

Nice! No, no reason it didn't, just no-one did it. Thanks for including a test


chore(deps): add some comment

Thanks for the PR.
I don't think this comment is necessary and the git commit message contains enough information.


Adding an off by one mutant

Since mutants are meant to represent common programmer errors, it may be useful to have an off by one mutant. This is not something that can be readily simulated with the mutants currently available in Dredd. This doesn't feel like an unreasonable addition considering we already replace integer and float with the interesting values '0', '1' and '-1'. If Dredd is being used for test case generation, this feels like a mutant that would be necessary to kill with a test.
What do you think @afd, @JonathanFoo0523?

I felt like it would lead to a lot of equivalent mutations or mutations that can already be killed by the readily available mutations. For example:

For integer constants used in array size initialization, mutating to arg + 1 (overallocation) is likely an equivalent mutation, and mutating to arg - 1 (under-allocation) is likely equivalent or killed by mutation to 0.
For integers in comparison operators (a op b), mutation of the integer literal in the comparison is likely subsumed by mutation of the op itself.
An offset-by-one mutation on expressions such as x + 1 might be partially simulated by Dredd's mutation operator on the lvalue (e.g., ++((*x))), or fully simulated if the lvalue is never used again after evaluation of the expression (e.g., an expression in a return statement).
In some programs, integer literals are used to call functions with the appropriate number of arguments (think about the argument to argc in main(int argc, char **argv)). Decrementing the integer argument by 1 likely has the same effect as mutating to 0. Incrementing the integer argument likely leads to invalid/null pointer access, which might be captured by existing safeguarding code, or the test case produced might not always be reproducible to kill the mutant.

There might indeed be cases where the offset mutation might lead to test cases that aren't captured by current mutation functions, and it might be worthy to investigate if this is indeed the case. I don't remember encountering any mutation testing tools that have an offset mutation operator when I did my research for my FYP, and I am not sure if this indicates they are less useful.


GeoCharts

I'm using this library and lovin' it! It actually works, I can render the charts from the examples.
Now I'm trying to render GeoCharts: https://developers.google.com/chart/interactive/docs/gallery/geochart#core
This is my code:
        var options2 = {
          sizeAxis: { minValue: 0, maxValue: 100 },
          region: '155', // Western Europe
          displayMode: 'markers',
          colorAxis: {colors: ['#e7711c', '#4374e0']} // orange to blue
        };

        var rows2 = [[
          ['Germany', 200],
          ['United States', 300],
          ['Brazil', 400],
          ['Canada', 500],
          ['France', 600],
          ['RU', 700]
        ]];

        var columns2 = [        {
                    'type': 'string',
                    'label' : 'Country'
                },
                {
                    'type' : 'number',
                    'label' : 'Number'
                }];

...
                            <Chart chartType = "GeoChart"
                              rows = {rows2}
                              options = {options2}
                              graph_id = "GeoChart"
                              width={"100%"}
                              height={"400px"}  legend_toggle={false} />

I get an empty div, and no errors.
May this be related to the part where google includes external scripts?
Note: GeoCharts require both of the following lines in the <head> section of the page
<script type="text/javascript" src="https://www.gstatic.com/charts/loader.js"></script> <script type="text/javascript" src="https://www.google.com/jsapi"></script>

I found the error. Seems like the "columns" prop is mandatory for react-google-charts to actually draw the charts.
So, with this code:
 var columns = [
       {'a' : 'b'}
     ];
//Just some rubbish columns
...
                            <Chart chartType="GeoChart"
                              width={"100%"}
                              height={"100%"}
                              data={data}
                              columns={columns}
                              options={options}
                              graph_id="GeoChart"
                              legend_toggle={true}/>

This works.

Hey Muntaner,
Yes to initialize the chart you need to either give it rows and columns, or a data object as described in the docs in the format described by the Google Charts API .
Glad it was resolved with you, I'm closing this issue feel free to open another one if you have another problem.
Cheers !

Does this still work for you @Muntaner?  I don't see a way of passing the mapsApiKey they introduced as per the docs


Drive only excutable form install directory and other issues

I installed drive using the instructions however i'm only able to execute it from
/usr/local/go/src/bin/drive
so i can't run it form anywhere using the drive command.
Also i'm unable to push using
./drive push /tmp/drive.txt
I get "no drive context found; run drive init or go into one of the directories (sub directories) that you performed drive init"
The file I want to upload has to be in the /usr/local/go/src/bin/ directory?
Also how do I force an upload with the "Proceed with the changes? [Y/n]:" prompt?

Hello @thetallone welcome to drive!
Now if you installed Go properly you should have set your GOPATH in your env that you can do like this:
$ cat << ! >> ~/.bashrc
> export GOPATH=\$HOME/go
> export PATH=\$GOPATH:\$GOPATH/bin:\$PATH
> !

To make an upload proceed, as asked by the prompt, hit 'y". Also please take a look at the README file.

Hi thanks for the reply, I tried your gopath recommendations and they didn't work. I also tried these are my various paths to go.
/usr/local/go
/usr/local/go/.hg/store/data/src/go
/usr/local/go/.hg/store/data/src/cmd/go
/usr/local/go/.hg/store/data/src/pkg/go
/usr/local/go/.hg/store/data/src/lib/go
/usr/local/go/.hg/store/data/misc/vim/ftplugin/go
/usr/local/go/.hg/store/data/misc/vim/autoload/go
/usr/local/go/bin/go
/usr/local/go/pkg/linux_arm/go
/usr/local/go/src/go
/usr/local/go/src/cmd/go
/usr/local/go/misc/makerelease/darwin/etc/paths.d/go
/usr/bin/go
/usr/lib/go
/usr/lib/go/pkg/linux_arm/go
/usr/share/go
/usr/share/go/src/go
/usr/share/go/src/cmd/go
I also checked the readme before posting this issue and only thing I could find that I thought would relate is -force but this just forces the upload even if they are the same not disabling the prompt.

Why don't you just install Go the proper way as you'll find from here https://golang.org/doc/install or from the README?
If you want to disable the prompt, --no-prompt?
Also this is an issue that has been duplicated before and closed as seen from https://github.com/odeke-em/drive/issues/168 https://github.com/odeke-em/drive/issues/124 and others.

Because it's on a raspberry pi.
In the readme https://github.com/odeke-em/drive/blob/master/README.md it does not mention the --no-prompt command?

I've installed Go on my raspberry pi btw: in fact I use it to test drive quite a bit. I also build Go from source on it :)
True, but the drive push -h, or drive pull -h does show it right?

Oh btw after you've set your GOPATH in your .bashrc I don't think you reloaded it. You can do that by
$ source ~/.bashrc

or by opening a new shell.
I think you might have missed that step.

ok I don't think it's going to work for me i've tried different PATH combinations but 'drive' still doesn't work.
go version go1.4.2 linux/arm

Could you provide the output of these following commands if you don't mind?
$ cat ~/.bashrc | tail -n 6
$ echo $GOPATH
$ whereis go
$ file $GOPATH/bin/drive

cat ~/.bashrc | tail -n 6
alias l='ls $LS_OPTIONS -lA'

Some more alias to avoid making mistakes:
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
(this is probably because I deleted the previous GOPATH entries as it wasn't working)
echo $GOPATH
(blank) desptie setting path?
whereis go
go: /usr/bin/go /usr/lib/go /usr/bin/X11/go /usr/local/go /usr/share/go /usr/share/man/man1/go.1.gz
file $GOPATH/bin/drive
/bin/drive: ERROR: cannot open `/bin/drive' (No such file or directory)

Okay, I don't think you set your GOPATH as I had mentioned in my first comment.
Could you please set it like this in your ~/.bashrc?
export GOPATH=$HOME/go
export PATH=$GOPATH:$GOPATH/bin:$PATH

or follow the instructions I posted above in https://github.com/odeke-em/drive/issues/192#issuecomment-100668680
and once you've saved
$ source ~/.bashrc

ok done it again
cat ~/.bashrc | tail -n 6
export GOPATH=$HOME/go
export PATH=$GOPATH:$GOPATH/bin:$PATH
echo $GOPATH
/root/go
whereis go
go: /usr/bin/go /usr/lib/go /usr/bin/X11/go /usr/local/go /usr/share/go /usr/share/man/man1/go.1.gz
file $GOPATH/bin/drive
/root/go/bin/drive: ERROR: cannot open `/root/go/bin/drive' (No such file or directory)
This would be because go isn't in /root/go as per my previous comment
/usr/local/go
/usr/local/go/.hg/store/data/src/go
/usr/local/go/.hg/store/data/src/cmd/go
/usr/local/go/.hg/store/data/src/pkg/go
/usr/local/go/.hg/store/data/src/lib/go
/usr/local/go/.hg/store/data/misc/vim/ftplugin/go
/usr/local/go/.hg/store/data/misc/vim/autoload/go
/usr/local/go/bin/go
/usr/local/go/pkg/linux_arm/go
/usr/local/go/src/go
/usr/local/go/src/cmd/go
/usr/local/go/misc/makerelease/darwin/etc/paths.d/go
/usr/bin/go
/usr/lib/go
/usr/lib/go/pkg/linux_arm/go
/usr/share/go
/usr/share/go/src/go
/usr/share/go/src/cmd/go

Now that you've set it right
$ go get github.com/odeke-em/drive/drive-gen && drive-gen

go get github.com/odeke-em/drive/drive-gen && drive-gen
go tool: no such tool "5c"

Sorry for the late reply.
This is probably for not installing go right. I'd recommend whenever you have time reinstalling as opposed to guessing the paths to use, it should be a four step process.
In the meantime, if you'd like, I've created for you an ARM binary right off my RaspberryPi and published a special release for you here
https://github.com/odeke-em/drive/releases/tag/v0.2.1-arm-binary
After downloading it, place in your $GOPATH/bin like this
mv drive-arm-binary $GOPATH/bin/drive

Ok thanks I'll give that a go, I have other users on the pi so didn't want
it to install/run from /root/go . Go works it's just the paths are
different.
On May 10, 2015 9:40 PM, "Emmanuel Odeke"<EMAIL_ADDRESS>wrote:

Sorry for the late reply.
This is probably for not installing go right. I'd recommend whenever you
have time reinstalling as opposed to guessing the paths to use, it should
be a four step process.
In the meantime, if you'd like, I've created for you an ARM binary right
off my RaspberryPi and published a special release for you here
https://github.com/odeke-em/drive/releases/tag/v0.2.1-arm-binary
After downloading it, place in your $GOPATH/bin like this
mv drive-arm-binary $GOPATH/bin/drive
—
Reply to this email directly or view it on GitHub
https://github.com/odeke-em/drive/issues/192#issuecomment-100697656.

Yeah the solution provided is user agnostic. However, installing user space programs to root doesn't seem like the best idea :) Please try again probably using a well configured path and then we can resolve this issue.

ok I managed to get the paths sorted with my previous install and now I can
run the drive command from anywhere however when I do a
drive /tmp/drive.txt
I get
no drive context found; run drive init or go into one of the directories
(sub directories) that you performed drive init
On Sun, May 10, 2015 at 10:17 PM, Emmanuel Odeke<EMAIL_ADDRESS>wrote:

Yeah the solution provided is user agnostic. However, installing user
space programs to root doesn't seem like the best idea :) Please try again
probably using a well configured path and then we can resolve this issue.
—
Reply to this email directly or view it on GitHub
https://github.com/odeke-em/drive/issues/192#issuecomment-100703393.

That's good to know you sorted that out!
Run drive init <your_path> and that will be the folder you'll mount your drive e.g
$ drive init ~/personal_drive
# Then after the authorizations, you can use it
$ cd ~/personal_drive
# Now you can do stuff inside drive e.g pull, push etc
$ pwd
$HOME/personal_drive
$ mkdir -p test1/test2/test3 && cd test1/test2/test3
$ date >> flux.txt && drive push flux.txt

Closing this issue since it now requires the user reading the manual.


Add demo test

Signed-off-by: KernelErr<EMAIL_ADDRESS>

Can you have a check on why it failed? @Folyd
If you delete the generated folder build and use zine build to build again. It might fail.

After using par_bridge, copying files may be ahead of creating its directory. I tried to fix this.
https://github.com/zineland/zine/blob/54c4bebcb6048b36f286b05f083189718aee9a5e/src/helpers.rs#L135-L153

Now we don't create the directory if it's empty.


Survival boxes can survive explosions

About the PR

Survival boxes and its variants now provide 90% explosive damage reduction to its contents.
Why / Balance

Survival boxes have an awkward shape (3x3, which is horrible for satchels)
Survival boxes are functionally useless (1:1 storage volume:capacity)
Granting survival boxes explosive damage reduction to contents gives it a functional use besides inventory management and makes for a fun play on words too.
Technical details

YAML warrior
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Nope
Changelog

:cl:

tweak: Survival boxes are better at surviving explosions

Something has gone horribly wrong with the actual files, it seems...


Support for Bluetooth low energy TPMS

Could you kindly look to support BLE (Bluetooth 5 low energy) tyre pressure devices. They use 8 digit hexadecimal identifiers and are normally paired over Bluetooth rather than by scanning a QR code and are paired one by one.
Here are 2 sample IDs, note they aren’t ordered 1,2,3,4 like those already supported.
FD2F46B2
95365F44
Thanks!

Hello and thanks for submitting and issue !
Could you provide me a link where I can show which kind of sensor you're talking about ? I've 2 packs a sensors which uses BLE 5 and both of them are working correctly with TPMS Advanced.

Bluetooth 5.0 2/3/4 TPMS Sensors Motorcycle Car Tire Pressure Monitoring
System 0-100PSI Tyre https://a.aliexpress.com/_mLq6ziA
Regards,
Peter
On Mon, 28 Aug 2023 at 8:14 PM, Vincent Masselis @.***>
wrote:

Hello and thanks for submitting and issue !
Could you provide me a link where I can show which kind of sensor you're
talking about ? I've 2 packs a sensors which uses BLE 5 and both of them
are working correctly with TPMS Advanced.
—
Reply to this email directly, view it on GitHub
https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1695243068,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWA6QBIE5PFEJJEQ5X2W6JDXXRHOPANCNFSM6AAAAAA377WTOY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Here’s the data you requested. I think these are from two of my TPMS.
Let me know what you find.
Regards,
Peter
On Thu, 31 Aug 2023 at 8:00 PM, Vincent Masselis @.***>
wrote:

It's strange, theses sensors looks exactly the same than the one I already
own.
I need some additional information to understand what are the returned
data by theses sensors, could you install the app nRF Connect
https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=en&gl=US,
open it, click on the button "Scan" in the top right corner and search for
your sensor in the list.
Then, click on the button Raw in the sensor's cell:
[image: Screenshot_20230831-091802]
https://user-images.githubusercontent.com/6769250/264575541-ee6b6206-6513-40ba-96c3-427b2aa3c3e6.png
Then, click on the Copy icon in the top right corner of the dialog, It
will copy into your phone clipboard the current data returned by your
sensor:
[image: Screenshot_20230831-091811]
https://user-images.githubusercontent.com/6769250/264575700-5c133c25-aa74-4fdc-8631-ea18093a5281.png
Once copied, paste the data here, in this issue, I will analyse if this
data is something I know or something new for the app. The best thing to do
is copy/paste a returned data for each of your sensor, It will help me.
Regards
—
Reply to this email directly, view it on GitHub
https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1700551486,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWA6QBOQ6CK2J7T7MPEJHLLXYBABFANCNFSM6AAAAAA377WTOY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Unfortunately I can't see any data in your response. Could you consider using the github website directly instead of using mails please ?

Here's the data froimages, apologies they didn't come through to you.
DC:A5:73:92:8D:DB NOT BONDED CONNECT 7-106 dBm # 2005 ms Device type:
UNKNOWN Advertising type: Legacy Flags: GeneralDiscoverable,
BrEdrNotSupported Complete list of 16-bit Service UUIDs: OxFEED Service
Data: UUID: OxFEED Data: Ox0200E14CEA12AE41634C
DC:A5:73:92:8D:DB NOT BONDED CONNECT 7-106 dBm # 2005 ms Device type:
UNKNOWN Advertising type: Legacy Flags: GeneralDiscoverable,
BrEdrNotSupported Complete list of 16-bit Service UUIDs: OxFEED Service
Data: UUID: OxFEED Data: Ox0200E14CEA12AE41634C
Regards,
Peter
On Tue, 5 Sep 2023 at 1:10 AM, Vincent Masselis @.***>
wrote:

Unfortunately I can't see any data in your response. Could you consider
using the github website directly instead of using mails please ?
—
Reply to this email directly, view it on GitHub
https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1705249864,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWA6QBKQ5YEUDVQVYV3B42TXYXHNFANCNFSM6AAAAAA377WTOY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Theses data are unusual, TPMS Advanced used to parse a bloc of 15 bytes while your sample is 10 bytes only. On the "official" app SYTPMS, which data do you have ? Does temperature, pressure and battery are displayed ?
Since the byte array length's is different and the service uuids uses a different key, I think your sensor works with a new format (or an old format) that I've nerver seen.

This is an example of the data I see in the app:
2.6Bar 15.0°C 2.9V
Regards,
Peter
On Tue, 5 Sep 2023 at 9:21 PM, Vincent Masselis @.***>
wrote:

Theses data are unusual, TPMS Advanced used to parse a bloc of 15 bytes
while your sample is 10 bytes only. On the "official" app SYTPMS, which
data do you have ? Does temperature, pressure and battery are displayed ?
Since the byte array length's is different and the service uuids uses a
different key, I think your sensor works with a new format (or an old
format) that I've nerver seen.
—
Reply to this email directly, view it on GitHub
https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1706254270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWA6QBNH3WF7GSTCO2MQOB3XY3VJ7ANCNFSM6AAAAAA377WTOY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm having the same issue with mine, these ones: https://www.aliexpress.com/item/1005005286360131.html
They work in SYTPMS, (but not TPMSII)

nRF Connect gave me this info

Copied raw data for each:
0x0303A5270308425208FF801E1301BE9720
0x0303A5270308425208FF201C1101992FEB

Hello @aetha and thanks for you contribution !
Fortunately I bought one of theses sensors 1 month ago (those with a sticker containing 2 hexa chars on the top and the location on the bottom). I'm still reverse engineering them in order to understand which kind of data is sent through theses sensor.
The compatibility with theses sensors is my next feature :)

Good news, I'm working to manage the sensors both of you are currently using. Theses sensors manufacturer by Pecham are not working like Sysgration does, tyre location is not returned but the sensor itself, it's up to the user to tell where the sensor is located. This said, I'm currently working an a new screen to pair the Pecham sensor is a easy and natural way.
I've a quick question for you @aetha and @psoukal-nonms, to make my sensors visible when attached to a pressured way AND the wheel must be spinning, do your sensors are only visible in this conditions like me ? How did you pair yours when using the """official""" app ?

That’s good news. When do you expect the app to be in the play store?
The sytmps app has you pair an individual sensor at a time.
By screwing in the sensor into a tyre stem it allows it to be pair. If it’s
already on the tyre I unscrew and rescrew it so it becomes pressurised. The
wheel does not need to be spinning to pair.
Does this make sense?
Regards,
Peter
On Wed, 13 Dec 2023 at 4:54 AM, Vincent Masselis @.***>
wrote:

Good news, I'm working to manage the sensors both of you are currently
using. Theses sensors manufacturer by Pecham are not working like
Sysgration does, tyre location is not returned but the sensor itself, it's
up to the user to tell where the sensor is located. This said, I'm
currently working an a new screen to pair the Pecham sensor is a easy and
natural way.
I've a quick question for you @aetha https://github.com/aetha and
@psoukal-nonms https://github.com/psoukal-nonms, to make my sensors
visible when attached to a pressured way AND the wheel must be
spinning, do your sensors are only visible in this conditions like me ? How
did you pair yours when using the """official""" app ?
—
Reply to this email directly, view it on GitHub
https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1852317133,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWA6QBOUPS5JJJNVOBVG5DDYJB43BAVCNFSM6AAAAAA377WTO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGMYTOMJTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

My experience has been the same as @psoukal-nonms, unscrewing & then re-tightening them to cause a pressure fluctuation, forces them to wake up. No need to move the wheels to pair.

Thanks both of you, I'm working on an user experience which match this technical behavior in order to make it as best as possible.

Hey !
I just pushed a release which include a support for the Pecham sensors into the beta channel of the Play Store. If you want to try this new version, follow this link to become a beta tester.


Feature/lesson page use slug

Wire curriculum/[lesson] & review/[lesson] to use the new slug field added in pr #1039
Preview Links:
https://c0d3-app-n7gycibgm-c0d3.vercel.app/review/js0
https://c0d3-app-n7gycibgm-c0d3.vercel.app/curriculum/js0
Other issues included in this pr:

Fixed issues with the LessonCard review count button

Was set to network-only fetch so it didn't show stale data but was causing multiple hits to the graphql api when component would rerender, now only hits once on first mount.  *You can view this bug in production by navigating to https://c0d3.com with your network tab open. if you are logged in it will redirect you to the curriculum page before the getApp fetch has finished and then start the review fetches with will then rerun when the initial fetch finishes (you may have to clear your cache to see it, and easiest to see when you filter graphql requests only)
Converted to next/link to prevent the need to refetch the entire app when clicking the review button.

Refactored LessonTitleCard test file to only be concerned about the component and not the pages it's used in

Fixed issues with the LessonCard review count button
Was set to network-only fetch so it didn't show stale data but was causing multiple hits to the graphql api when component would rerender, now only hits once on first mount.

About this point, on my end it's still calling the API again if I navigate to some other page and then go back to the curriculum page (without full reload, Firefox browser, Ubuntu 20.04).
Checked through the network tab on the developer tools

First Load

Entered a lesson challenges page and clicked the go back link

on my end it's still calling the API again if I navigate to some other page

I believe that is the intended function we wanted. This allows for the user to manually refresh the page and always get the newest submissions for review.
The bug I fixed was the same review fetch getting triggered multiple times on one navigation.
Here i just visited https://c0d3.com (already logged into my account which has the 7 completed lessons)

I didn't highlight all the refetching but you can see the one lesson got hit 3 times. There should only be a total of 9 fetches (7 reviews + getApp + getSession) but I 19.
We could go further and switch it to a polling type behavior but I would make a seperate pr for a change like that.

Oh I see what you meant now, that's cool, nice work.
But yeah having it refresh is the intended way to prevent it showing stale submissions count after submitting a review.

@all-contributors please add @tomrule007 for code and doc


Add optional minimized window

A version used myself which add function asked in #128

Thanks for your contribution!
However, in the existing settings, if you disable System Tray Icon, Starward will minimize to the taskbar after game startup. Add a new setting item for this feature is not necessary, so I won't merge your PR.


feat: use alchemy provider, light account for e2e tests

We should use AlchemyProvider with gas manager for all our e2e tests to less make it flaky.
Also, use light accounts unless for simple account tests.
For Kernel, just utilizing fee data getter override to set test passing variables.

PR-Codex overview
Detailed summary

Deleted several files and directories related to examples and contracts.
Added dependencies: "zod" to packages/core/package.json and packages/aa-simple-dapp/package.json.
Updated dependencies: "@alchemy/aa-core" in packages/alchemy/package.json and packages/accounts/package.json.
Updated devDependencies: "typescript" and "vitest" in packages/alchemy/package.json and packages/accounts/package.json.
Updated devDependencies: "@alchemy/aa-core" in packages/alchemy/package.json and packages/accounts/package.json.
Updated devDependencies: "@alchemy/aa-core" in packages/core/e2e-tests/constants.ts.
Updated devDependencies: "@alchemy/aa-core" in packages/ethers/src/types.ts.
Updated exports in packages/alchemy/src/index.ts and packages/accounts/src/index.ts.
Added dependencies: "@alchemy/aa-accounts", "@alchemy/aa-alchemy", and "@alchemy/aa-core" to examples/alchemy-daapp/package.json.
Updated dependencies: "@alchemy/aa-accounts", "@alchemy/aa-alchemy", and "@alchemy/aa-core" in examples/aa-simple-dapp/package.json.
Updated .gitignore files.
Updated exports in packages/alchemy/src/type.ts and packages/core/src/utils/schema.ts.
Updated exports in site/packages/aa-core/accounts/other/getAddress.md.
Updated exports in site/packages/aa-ethers/provider-adapter/fromEthersProvider.md.
Updated exports in site/packages/aa-alchemy/middleware/introduction.md.
Updated exports in site/snippets/send-uo-example/create-provider.ts.
Updated exports in site/snippets/send-uo-example/send-uo.ts.
Updated exports in site/snippets/ethers-provider.ts.
Updated exports in site/smart-accounts/sponsoring-gas.md.
Updated exports in site/snippets/send-uo-example/calldata.ts.
Updated exports in examples/aa-simple-dapp/src/context/wallet/index.tsx.

The following files were skipped due to too many changes: examples/aa-simple-dapp/src/context/wallet/index.tsx, packages/ethers/src/schema.ts, packages/accounts/src/light-account/e2e-tests/constants.ts, site/packages/aa-alchemy/middleware/withAlchemyGasManager.md, site/smart-accounts/signers/capsule.md, site/smart-accounts/signers/dynamic.md, packages/core/src/types.ts, site/smart-accounts/signers/lit.md, site/snippets/send-uo-example/connect-account.ts, packages/core/src/utils/userop.ts, site/packages/aa-core/accounts/other/getFactoryAddress.md, site/packages/aa-core/accounts/other/getOwner.md, packages/accounts/src/kernel-zerodev/__tests__/account.test.ts, site/packages/aa-core/provider/withFeeDataGetter.md, site/smart-accounts/signers/turnkey.md, site/getting-started.md, site/smart-accounts/signers/portal.md, packages/core/src/__tests__/utils.test.ts, site/snippets/ethers-signer.ts, site/packages/aa-ethers/provider-adapter/introduction.md, packages/core/src/signer/__tests__/local-account.test.ts, site/smart-accounts/signers/magic.md, site/packages/aa-core/accounts/other/getEntryPointAddress.md, site/snippets/privy.ts, site/snippets/particle.ts, site/snippets/core-provider.ts, site/packages/aa-core/utils/getDefaultEntryPointAddress.md, site/index.md, site/packages/aa-core/utils/getDefaultSimpleAccountFactoryAddress.md, site/packages/aa-accounts/utils/getDefaultLightAccountFactoryAddress.md, packages/accounts/src/kernel-zerodev/README.md, site/smart-accounts/signers/web3auth.md, packages/core/src/provider/types.ts, site/packages/aa-core/provider/waitForUserOperationTransaction.md, packages/accounts/src/light-account/utils.ts, site/snippets/provider.ts, README.md, packages/core/src/account/schema.ts, site/packages/aa-core/provider/getEntryPointAddress.md, packages/core/src/account/simple.ts, packages/accounts/src/light-account/__tests__/account.test.ts, site/smart-accounts/signers/fireblocks.md, site/snippets/account-ethers.ts, examples/alchemy-daapp/src/surfaces/onboarding/OnboardingDataModels.tsx, site/snippets/account-alchemy.ts, packages/alchemy/src/middleware/gas-manager.ts, packages/core/src/account/types.ts, site/snippets/account-core.ts, packages/accounts/src/kernel-zerodev/e2e-tests/kernel-account.test.ts, packages/ethers/e2e-tests/simple-account.test.ts, examples/aa-simple-dapp/src/hooks/useAlchemyProvider.ts, packages/core/src/index.ts, site/snippets/send-uo-example/full-example.ts, site/snippets/light-account.ts, packages/core/src/provider/schema.ts, packages/core/src/utils/defaults.ts, packages/ethers/src/provider-adapter.ts, packages/alchemy/src/schema.ts, packages/ethers/src/__tests__/provider-adapter.test.ts, site/packages/aa-ethers/provider-adapter/constructor.md, packages/alchemy/e2e-tests/simple-account.test.ts, packages/core/e2e-tests/simple-account.test.ts, examples/alchemy-daapp/src/surfaces/onboarding/OnboardingController.ts, site/packages/aa-core/provider/constructor.md, site/packages/aa-core/accounts/constructor.md, site/packages/aa-accounts/light-account/constructor.md, packages/alchemy/src/provider.ts, packages/alchemy/src/__tests__/provider.test.ts, site/smart-accounts/signers/particle-network.md, packages/alchemy/src/__tests__/__snapshots__/provider.test.ts.snap, site/packages/aa-alchemy/provider/constructor.md, site/guides/send-user-operation.md, packages/core/src/account/__tests__/simple.test.ts, packages/core/src/provider/__tests__/base.test.ts, packages/core/src/provider/base.ts, packages/accounts/src/light-account/e2e-tests/light-account.test.ts, packages/core/src/account/base.ts, site/.vitepress/config.ts, yarn.lock

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Are all the changes in this PR relevant? Seems like it includes way more than e2e updates?

sorry @denniswon I just rebased dev on main after pulling in the changes for a new version.
make sure to rebase this PR on dev again


Upload frontend source maps to Sentry

It's nice to see some errors showing up in Sentry raised by the frontend! However, they aren't very useful at the moment as any caught errors point to the minified files rather than linked to the relevant point in our frontend source code.
The next step would be to update our build command so it uploads the source maps to Sentry on build, so that hopefully we will get nicer highlights of exactly where things error'ed in our code.

I'll see if I have some time to look at this soon... but putting it as low priority as I think we can live with even having the error messages up there for now, still better than nothing which is what we had before


Update init.py

Replace deprecated hass.config_entries.async_setup_platforms(entry, PLATFORMS)

@b-aeby you closed the PR. Isn't this the correct solution?

Hi,
PR re-open.
It solves this issue but the devices are not consistently available. I'm using RPi4, it has already worked properly but not usable after a SD crash and full re-installation.
Regards
Benjamin
15 mai 2023 09:26 "Frans Saris" @.*** @.@.>)> a écrit:
@b-aeby (https://github.com/b-aeby) you closed the PR. Isn't this the correct solution?
—

Reply to this email directly, view it on GitHub (https://github.com/fsaris/home-assistant-awox/pull/96#issuecomment-1547326509), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AOANOJMZFAP63JA4LAVRJLLXGHLB7ANCNFSM6AAAAAAYBHF6FY).
You are receiving this because you were mentioned.Message ID: @.***>

It works fine with a usb bluetooth dongle!
15 mai 2023 09:26 "Frans Saris" @.*** @.@.>)> a écrit:
@b-aeby (https://github.com/b-aeby) you closed the PR. Isn't this the correct solution?
—

Reply to this email directly, view it on GitHub (https://github.com/fsaris/home-assistant-awox/pull/96#issuecomment-1547326509), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AOANOJMZFAP63JA4LAVRJLLXGHLB7ANCNFSM6AAAAAAYBHF6FY).
You are receiving this because you were mentioned.Message ID: @.***>


E2e notebooks

Description
Added e2e notebooks for Leeds, Marseille and London (incomplete).
Added toml config files for e2e notebooks.
Restructured notebooks/e2e directory.
Motivation and Context
Example e2e notebooks to run pipeline for regions of interest.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Notebooks were run and outputs produced.
Test configuration details:

OS: macOS Ventura
Python version: 3.9
Java version: openJDK 11.0.2
Python management system: pip/conda

Advice for reviewer
To note:

Inputs and outputs are stored in GCP.
None of the notebooks use the currently in development modules for transport network and metrics. They will need to be added later.
London does not include the steps to calculate transport network and metrics as it depends on module development.

Checklist:

[x] My code follows the intended structure of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Additional comments

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

Comparison is base (8bddb14) 97.77% compared to head (4f7d283) 97.77%.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #192   +/-   ##
=======================================
  Coverage   97.77%   97.77%
=======================================
  Files          14       14
  Lines        1171     1171
=======================================
  Hits         1145     1145
  Misses         26       26

Flag
Coverage Δ

unittests
97.77% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Draft. Need to add new analyse_network and metrics modules when ready.


Add youtube-dl Package

Hello,
I can't find the youtube-dl package on winget
Please add it.
https://github.com/ytdl-org/youtube-dl

https://github.com/ytdl-org/youtube-dl/issues/25517

Youtube-DL doesn't have an installer, therefore it's currently incompatible with winget.

They have to first solve this(its in their milestone)
https://github.com/microsoft/winget-cli/issues/361
Till then use Scoop, Scoop-Python or pip
https://www.reddit.com/r/youtubedl/comments/dzj0mr/youtubedl_the_complete_installation_guide_for/

They have to first solve this(its in their milestone) first
microsoft/winget-cli#361
Till then use Scoop, Scoop-Python or pip
https://www.reddit.com/r/youtubedl/comments/dzj0mr/youtubedl_the_complete_installation_guide_for/

OK, Thanks.

https://github.com/microsoft/winget-cli/issues/140

@denelon - https://github.com/microsoft/winget-pkgs/pull/68800


The DNS query name does not exist in Step 4

For some domains I get
Step 4: sort which ones are cyclic
analyzying xxxxxx.zone.. Domain 12 from 14
The DNS operation timed out after 5.1041343212127686 seconds
The DNS operation timed out after 5.105474233627319 seconds
<class 'dns.exception.Timeout'>
The DNS query name does not exist: N.
The DNS query name does not exist: N.
The DNS query name does not exist: X.
The DNS query name does not exist: X.
The DNS query name does not exist: D.
The DNS query name does not exist: D.
The DNS query name does not exist: O.
The DNS query name does not exist: O.
The DNS query name does not exist: M.
The DNS query name does not exist: M.
The DNS query name does not exist: A.
The DNS query name does not exist: A.
The DNS query name does not exist: I.
The DNS query name does not exist: I.
The DNS query name does not exist: N.
The DNS query name does not exist: N.
So it seems that if all NS of a zone do not reply or do not reply with useful data, the script does something not expected or does not have a managed case to handle it?

I tried a quick fix in https://github.com/SIDN/CycleHunter/pull/8

perfect! I merged your PR already, so I'll makr this as fixed


v1.13 Changelog

@enahum FYI, this is still WIP.

This is good for reviews now.

Comments addressed,

@enahum Can you help merge this when you have a chance?

Can this PR be merged and then open a new one for any needed tweaks? v1.13 has been released so people may be looking for this and it also includes the important compatibility note.
Again, I don't have merge permissions.


Populate has_replay in high score import

https://github.com/ppy/osu-web/pull/9216

In addition to the has_replay field, ScoreInfo (I think?) also need to include legacy_score_id for mapping from solo score id to legacy score id

Reopening temporarily, has_replay column isn't being populated as expectd.


AutoSizeColumn became extremely slow after upgrading from npoi 2.6.0 to 2.6.2

we had been stuck for quite a while with npoi 2.6.0 because other package, which depended on Portable.BouncyCastle instead of BouncyCastle.Cryptography. But recently we were able to update to npoi 2.6.2.
But suddenly we experienced an extreme loss of performance in the AutoSizeColumn method. Exports of files with 30000 rows, are now almost impossible taking about 5 minutes, where before it took a few seconds (we did not even bother to measure, because we did not experience AutoSizeColumn as bottleneck). And this with spreadsheets, which don't use formulas and don't use merged cells either.
How can it be, that switching from npoi 2.6.0 which used SixLabors.Fonts in the beta version, to npoi 2.6.2 with SixLabors.Fonts 1.0.0  version causes  such a big loss of performance?
Does anybody even know, why this is so?
TIA, Stefan

The issue is caused by font loading, it was already fixed by adding font caching in #1179
You can check performance with a master branch

Thank you for you reply. When can we expect to benefit from this fix by a published nuget package. In other words, when will npoi 2.7.0 will be available as nuget package?

You can check the milestones of 2.7.0, there are a half of open issues. I don't know the exact release date, but seems not this year

Thanks for pointing this out. And an update 2.6.3 which contains this in my view very important fix is not feasible, either?
I think, updating from 2.6.0 to 2.6.2 and then out of the sudden experiencing such detoriation in existing file exports, certainly would justify a more timely available fix.
We generate excel files for download from  web applications, and suddenly users think the download is broken, because suddenly it take many minutes, instead of seconds. And we are blamed for it.

Let's wait for @tonyqus, he is a maintainer of this project

@Stoffelche I'm the guy making plans for NPOI releases. I'm the project manager and DevOps manager in NPOI project (previously, I'm the major contributor of NPOI). A 2.6.3 release is possible. But I'm still planning and I cannot guaratee anything.
In #1099, someone did raise a hand to ask for increasing the frequency of releases. But I have to tradeoff because each release usually takes me one week to finish everything. It's a standard release process like a software company
It includes the following tasks

Summarize release note for the release (example: #1168)
Test case verifications(about 4000 unit tests) and some regression bug fixes
Release candidate (RC) nuget pakcage test (Sometimes, the nuget package may miss something or not working at all)
A release annoncement and perhaps a post to thank all the contributors ( example post)

You have to understand NPOI is still a hobby project instead of commercial although it looks like a commercial one.  I have to control the contribution time I put on this project per month because I got very little donation (less than 400 USD per year).  To be honest, my family member did have big concern on this project because of very little profits.
As a tradeoff, the current release frequency is 3-4 month (which means 3-4 releases a year). That's maximum release frequency I can provide for now.  NPOI 2.6.2 release happened just less than 2 month ago (on Sep 11). In other words, the next release may happen in Dec, 2023.

@Stoffelche And as a workaround, I do suggest you use predict fixed width for columns instead of calling AutosizeColumn. Automatic column width adjustment is a nice-to-have feature but it does consume CPU and performance. It has no impact on data in the Excel. I guess if you turn AutosizeColumn off, your users will not complain a lot.

Thanks for pointing this out. I generally understand your point.
The only thing is, in this particular situation, there is a deterioration of an existing functioning feature, by orders of magnitude, rendering it practically unusable, where it was working before, thus breaking the code of applications, that already had used it, because it was working before.
Therefore I think it would merit kind of a hotfix or at least being included in a timely minor release follow-up.

As to your suggested workaround, it is kind of not feasible in a situation where many excel files are generated with different contents.
My workaround is to do the AutoSizeColumn after 500 rows were inserted, and then proceed with filling up.
I can live with this workaround for now, so don't bother.
Only, I still think, this should not happen, as it breaks existing working applications.

Only, I still think, this should not happen, as it breaks existing working applications.

I believe you should test your app before publishing in production...

Fixed by #1179


rpm: Update virtualization packages

What this PR does
Update virtualization packages. Specifically:

QEMU (8.2.0 → 9.0.0)
libvirt (10.0.0 → 10.5.0)
EDKII (20231122 → 20240524)
passt (20231204 → 20240624)
virtiofsd (1.10.1 → 1.11.1)

This PR is a superset of #12300.
Release note
This version of KubeVirt includes upgraded virtualization technology based on libvirt 10.5.0 and QEMU 9.0.0.
Each new release of libvirt and QEMU contains numerous improvements and bug fixes.

@jean-edouard can you perhaps approve this one? You had taken a stab at it already, so you should be familiar with the matter :)

Thanks @brianmcarey @jean-edouard!

@andreabolognani @jean-edouard Shouldn't we backport it since the virtualization packages include bug fixes?

@andreabolognani @jean-edouard Shouldn't we backport it since the virtualization packages include bug fixes?

Do you have specific bugs in mind? Maybe the fixes were backported in z-streams upstream and we could target those?
In general, package updates will always contain bug fixes...

@jean-edouard this one:
https://github.com/kubevirt/kubevirt/issues/12519

@jean-edouard this one: #12519

Maybe the fixes were backported in z-streams upstream and we could target those?

Sounds good to me if this is the case

@andreabolognani what do you think? I don't see any z-stream release in download.libvirt.org, does it make sense to upgrade release branche(s) from 10.0 to 10.5? Can that be done without updating the other packages? Backporting this entire PR feels wrong but maybe it is the right thing to do after all...

I don't see any z-stream release in download.libvirt.org

@jean-edouard z-stream is a purely downstream concept. The closest upstream equivalent would be stable/maintenance releases, but in the case of libvirt we only do those extremely rarely.

does it make sense to upgrade release branche(s) from 10.0 to 10.5? Can that be done without updating the other packages? Backporting this entire PR feels wrong but maybe it is the right thing to do after all...

If you have specific, targeted issues that you're concerned about then you might be able to make a case for the fixes being backported from RHEL 9.5 (libvirt 10.5.0) to RHEL 9.4 (libvirt 10.0.0), and then you could pick the new libvirt 10.0.0 package that contains them for use in the stable KubeVirt branch.
Backporting the RPM update in its entirety, or even just bumping libvirt from 10.0.0 to 10.5.0 on its own, seems contrary to the very idea of a stable branch.


looping tasks

Ideally I'd like to do something like this...
1 programming agent creates code
2 testing agent runs code in repl and provides feedback given some example require output
testing passed goes to set 4
3 programming agent takes code from step 2 re-codes and goes to step 2
4 resulting code is presented
so this is 3 tasks really, but in particular step 2 needs a way to complete the whole process and step 3 needs a way to be able to get back to step 2

don't forget we have https://chat.openai.com/g/g-qqTuUWsBY-crewai-assistant to help and also the discord community https://discord.com/invite/X4JWnZnxPb

Hey @chriscamacho ,
I came across your scenario and thought Langraph might be a cool tool to check out. It seems like it could fit the bill for what you're looking for.
Just in case, here's a handy link that shows how to get started with Langraph for Crew.ai: https://github.com/CrewAI-LangGraph .
Hope this helps!

Hey @chriscamacho ,
I came across your scenario and thought Langraph might be a cool tool to check out. It seems like it could fit the bill for what you're looking for.
Just in case, here's a handy link that shows how to get started with Langraph for Crew.ai: https://github.com/joaomdmoura/crewAI-examples/tree/main/CrewAI-LangGraph
Hope this helps!

Check out the task.execute() method.
That's what I use to get the output of a task and then move on to the next task or perform some operations. You can also use task.output which simply just gives you the result of the executed task.

I been trying to figure out how to do the same thing.


Fix in order to allow multiple input shapes.

The MXPredCreate* c++ functions have a bug that prevents them from accepting more than one input shape.
Consequently the comments for these functions are pretty confusing and led to an incorrect implementation of this functionality in this file.
This is the fix for the mxnet code, just fyi.
https://github.com/dmlc/mxnet/pull/5539
@songtianyi

@songtianyi actually on second thought it's possible to get the same results without changing the c++ side, by providing the shapeIdx as {0,2,4} for two two-dimensional shapes.

@sergeykolychev
Hi,
Could you add one test case for your PR. To make sure it will work with future commits.

I am pretty new to golang, so I am not familiar with established practices of the testing in Go.
I can give you a symbol json tomorrow that will work with my fix and fail without, will that suffice ?

@songtianyi Here you go, this simple test.go will work on my branch and will fail on your master
because mxnet needs to know the shape of the softmax_label however current code is incorrectly
delivers this info.
your current code is putting in shapeIdx as {0,2,2} but mxnet is expecting {0,2,4} which is what my fix does.
Here is the code that expecting the shapeIdx to be in this format (it took me a while to track that :-))
https://github.com/dmlc/mxnet/blob/master/src/c_api/c_predict_api.cc#L151


Difficult to set 'contents' boost with search fields option

When searching MS MARCO, it's possible to query over multiple fields using the option -fields <field>=<boost>. The resulting query is a disjunction over the contents field, plus the provided fields with their boosts applied.
This makes it harder to assign a weight to the contents field. Taking the example from #988 where we specify -fields contents=1.0f -fields predictions=2.0f, this would result in a query like
contents:value contents:value (predictions:value)^2.0

which is executed as
(contents:value)^2.0 (predictions:value)^2.0

Maybe the-fields option could be interpreted as fully defining fields + boosts instead of tacking on additional fields (as it is now)?

This is fine with me. The fields option was experimental, and nothing else in the code base depends on it... so okay to redefine the semantics of what the option means.

This is fine with me. The fields option was experimental, and nothing else in the code base depends on it... so okay to redefine the semantics of what the option means.


🐛 BUG: Regression in @astrojs/ts-plugin 1.5.0

Describe the Bug
Once I upgrade from @astrojs/ts-plugin 1.4.0 to 1.5.0, the astro build step starts to complain about encountering TS code inside some <script> blocks that I have in .astro files.
This didn't happen before.
Steps to Reproduce

Start using @astrojs/ts-plugin 1.4.0
Create some .astro file with <script> block in it
Add some TS code in the <script> block
Everything should compile well
Update to 1.5.0
Try to build, and see how now Astro complains

Thought I was losing my mind this afternoon! Tried installing a clean project and all sorts to see if it would recognise the TS stuff.

Ah yes, I can confirm the issue, apologies for the inconvenience. I'll take a look right now!

Should be fixed in the latest version of everything, sorry for the inconvenience!

Can confirm working in 2.7.1! Thanks for sorting so quickly.


run trash empty --all without confirmation

i have removed the trash-cli which provides trash-empty command.
i use that trash-empty command in shell scripts to keep up the system maintenance.
trash-empty doesn't ask for confirmation.
how to replace that command with trash command as it keeps asking for confirmation?

Please consult the help!
trash empty --all --force


Embla UCI for Android by Folkert van Heusden (The Netherlands)

Can you test please the Android version of https://vanheusden.com/Embla/files/ and confirm that Embla UCI works for you?

It works


Prefix Not Showing

Description

I have created some groups using LP but prefixes don't show. I've tried 5 different chat plugins, placeholderapi and vault.
Nothing fixed the issue
Reproduction steps

Make a group
Save changes
Add yourself to the group and type something
Prefix doesn't show

Expected behaviour

I expected the prefix to show.
Environment details

Server type/version: Paper running version 1.8.8 build latest
LuckPerms version: vlatest

Any other relevant details

Does prefix show in /lp user <user> info

Yes. Sent from Mail for Windows 10 From: Ben WooSent: Sunday 9 May 2021 12:34To: lucko/LuckPermsCc: Objectables; AuthorSubject: Re: [lucko/LuckPerms] Prefix Not Showing (#3016) Does prefix show in /lp user  info—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

LuckPerms only acts as the source for prefixes / suffixes, it doesn't actually apply them. You need an appropriately configured chat/tablist formatting plugin for them to be displayed. If the values appear correctly when you run /lp user  info, LuckPerms is doing its job!

https://luckperms.net/wiki/FAQ#why-are-prefixessuffixes-not-working
https://luckperms.net/wiki/Prefixes,-Suffixes-&-Meta#displaying-prefixes-and-suffixes

What chat plugin should I use?Herochat, EssentialsChat, VentureChat and mChat don’t work. Sent from Mail for Windows 10 From: Ben WooSent: Sunday 9 May 2021 12:59To: lucko/LuckPermsCc: Objectables; AuthorSubject: Re: [lucko/LuckPerms] Prefix Not Showing (#3016) LuckPerms only acts as the source for prefixes / suffixes, it doesn't actually apply them. You need an appropriately configured chat/tablist formatting plugin for them to be displayed. If the values appear correctly when you run /lp user info, LuckPerms is doing its job!https://luckperms.net/wiki/FAQ#why-are-prefixessuffixes-not-workinghttps://luckperms.net/wiki/Prefixes,-Suffixes-&-Meta#displaying-prefixes-and-suffixes—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

I'd recommend heading over to the support text channel of the LuckPerms Discord server so we can fully figure out whether this is an actual bug or just a configuration error. Could you ask your question there as well as include any necessary details in the process?


Snakemake Pipeline Issue

Hello together i am using Snakemake to create a tool with my different bash and python scripts. I am really new to Snakemake so i guess i am doing something wrong here. THis is my Skript
input_csv = os.getenv("INPUT_CSV")
output_dir = os.getenv("OUTPUT_DIR")
Motif_list = os.getenv("MOTIF_LIST")
data = pd.read_csv(input_csv)

input_base = os.path.splitext(os.path.basename(input_csv))[0]
updated_csv = os.path.join(output_dir, f"{input_base}_updated.csv")

bed_files = expand(os.path.join(output_dir, "{file_name}.bed"), file_name=data['File_name'].tolist())

rule all:
    input:
        updated_csv,
        bed_files

rule run_python_script:
    input:
        input_csv
    output:
        updated_csv
    shell:
        """
        python /Users/azlannisar/Desktop/Skripts/Check_python_snaky.py {input} {output}
        """

rule run_modkit:
    conda:
        "/Users/azlannisar/Snakemake_project_Mikrob/environment.yaml"
    input:
        csv_file=updated_csv
    output:
        os.path.join(output_dir, "{file_name}.bed")
    params:
        reference_path=lambda wildcards: data[data['File_name'] == wildcards.file_name].iloc[0]['Reference_path'],
        pod5_path=lambda wildcards: data[data['File_name'] == wildcards.file_name].iloc[0]['pod5_path']
    shell:
        """
        modkit pileup {params.pod5_path}/*_sorted.bam {output} --ref {params.reference_path}
        """

rule run_5mC_analysis_script:
    input:
        csv_list="/Users/azlannisar/Snakemake_Test/Data_Test2_updated.csv",
        motif_list="/Users/azlannisar/Motifs_5mC.txt"
    params:
        output_dir="/Users/azlannisar/Snakemake_Test"
    conda:
        "/Users/azlannisar/Snakemake_project_Mikrob/analysis.yaml"
    shell:
        """
        python /Users/azlannisar/Desktop/Skripts/analysis_5mC_script.py {input.csv_list} {params.output_dir} {input.motif_list}
        """

When i run this is runs the first two rules without problems gives me no Error and Skips the last rule. So i am confused why it is doing that. Since if i copy the last rule out into a seperate file and run is there it creates the outputs without problems. Maybe someone with more snakemake experience can help me out. Thanks and kind regards!
 Nor is it picked by all.

@cmeesters  Thanks for ur answer i got it running for a while forgot to close the ticket sry!


[BUGFIX] made adaptions caused by product refactoring

Tasks:

[x] done
[ ] got feedback

Informations:

Q
A

Bug fix?
yes

New feature?
no

Tests pass?
yes

Fixed tickets
none

Doc
none

ack


Login timeout expired

I'm getting this error intermittently.  It happens when I'm working from home, but not when I'm at work and the latency is less.
SQLSTATE[HYT00]: [unixODBC][Microsoft][ODBC Driver 13 for SQL Server]Login timeout expired
Using this:
PHP 7.1
Redhat 7
SQLSRV 4.0.8
MS SQL Driver 13.1.1

Hi @mkeatley17, can you review the following page to see if any applies:
https://technet.microsoft.com/en-us/library/ms190181(v=sql.105).aspx
Are the ping times to your SQL Server high from home?
The high latency could be a reason you get timeout errors.
The default login timeout is 15 seconds. You can increase that via LoginTimeout connection option. For example, maybe try 60 seconds:
$conn = sqlsrv_connect($server, array('UID'=>$uid, 'PWD'=>$pwd, 'Database'=>$database, 'LoginTimeout'=>60));
or
$mspdo1 = new PDO("sqlsrv:Server=$server;Database=$database;LoginTimeout=60", $uid, $pwd);

@mkeatley17 Do you also run into this issue while using sqlcmd?

@mkeatley17 Closing this issue due to inactivity. Feel free to reopen if you still need help 👍


Outdated documentation (email-sign-up)

https://github.com/lynndylanhurley/redux-auth/blob/master/docs/api-expectations/email-sign-up.md#success-response-body-example
Documentation says that successful payload should be:
{
  "status": "success"
}

But, reverse engineering (thanks to the Ng Token Auth project) tells me :
{
  "success": true,
  "data": {}
}

Thank you Guibod
I found you can also add an email address to plug into the dialog
        res.json({
            "success": true,
            "data": {
                "email"<EMAIL_ADDRESS>            }
        });

[emailSignUpActions.EMAIL_SIGN_UP_COMPLETE]: (state, {user}) => state.merge({
    emailSignUpSuccessModalVisible: true,
    emailSignUpAddress: user.email
  }),

Can you send a PR please?


Manually delete cache

If a cache with same key already exists, it never get's overwritten. Consider a situation where during development a wrong cache was created. How to delete it?
We may have cache key and key-COMMITSHA. If key was wrongly created earlier, Actions will always fallback to key in case the current key-COMMITSHA does not exist yet. How to delete the cache with key key?

Dupe of #2?

Close in favor of #2


Sentry tracing integration

There are various Sentry integrations for SPA routers with tracing support, a TanStack Router integration for example. Having one for Stackflow would be very helpful for Sentry users.
Since we already have event-driven plugin architecture, I guess it'd be pretty straightforward to make a plugin for it.

Thanks for the great suggestion Xiniha!
I've had a quick look at it, but I'm not sure what the benefits of integrating router framework with Sentry would be. It looks like it adds navigation tracing, but would that be a big help in tracking errors?
https://github.com/getsentry/sentry-javascript/blob/de9cf8a30b61c652264610a31d0c8322748cb46d/packages/react/src/tanstackrouter.ts#L78-L85

I believe it can be helpful for both performance monitoring and debugging.

Tracking routing and dataloading performances would be important to understand overall performance characteristics of application.
While debugging, it's quite useful to know which route a user was on. However, the builtin tracing feature of Sentry relies on History API tracking and therefore doesn't work well with Stackflow - especially when history sync extension is not / can't be used.

Okay, that makes sense now that I understand the situation “history sync extension can't be used”. I think it's a good suggestion, and since we don't have the resources right now, I'd be happy to contribute to it

I'll look into it when I get some spare time 😅 If anyone is interested in the feature, let me know so I can bump up the priority!

@XiNiHa @tonyfromundefined
Hello! im interested in this issue
I already made minimal version of sentry plugin for stackflow and tested it with local server & sentry. seems working properly!

url navigation logging
pageload transaction logging
error logging

Can i try this feature?

Sounds great 👍