.NET Framework v4.7.1 Error message when try to install

I'm trying to install the .NET Framework v4.7.1 on a Windows 7 (64bit) PC, but I keep getting the following error: 'Installation Did Not Suceed' .NET Framework 4.7.1 has not been installed because: The timestamp signature and/or certificate could not be verified or is malformed.'
Does anybody run into this error before? The PC currently has installed a .Net Framework v4.6.2, .NET Framework 4.5 SDK, and .NET Framework 4.5 Multi-Targeting Pack.

Have you installed SHA2 support on your OS?
ref for details over here  https://answers.microsoft.com/en-us/windows/forum/all/the-timestamp-signature-andor-certificate-could/2de7e456-f6df-42a4-82dc-9201eec07c4f


Fix Code scanning issue Set number 4

Tracking issue for:

[ ] https://github.com/NASA-AMMOS/anms/security/code-scanning/37
[ ] https://github.com/NASA-AMMOS/anms/security/code-scanning/36
[ ] https://github.com/NASA-AMMOS/anms/security/code-scanning/38
[ ] https://github.com/NASA-AMMOS/anms/security/code-scanning/39

[]https://www.jetbrains.com/

Error found in files supplied from swagger docs library fix not needed.


Read deployment failure from Kubernetes events

Sometimes deployment of a job gets stuck, if for instance, Kubernetes can't create a new pod due to not enough resources in the cluster. Deployment commands succeeds (kubectl apply), but the real deployment process happens in background later on, and then Kubernetes states that cluster is out of memory and reports an error event. However, Racetrack doesn't know that and still waits patiently until the pod is created, until the timeout occurs. It makes the deployment proceess unnecessarily long in this case.
It would be better to read the k8s events or get notified in this case, to show a meaningful error to a user and abort immediately as the error happens.

Is there a failing example for this issue?
Will $ racetrack deploy job.yaml succeed while kubectl apply runs in the kubernetes plugin? Where is the timeout?
Do we want this feature to be in lifecyle-supervisor, or is it something in kubernetes plugin?

Is there a failing example for this issue?

A sort of. In case of requesting for too many CPU cores, like this:
resources:
  cpu_min: 10M # 10M is not millis, but Mega

Kubernetes says it's okay on kubectl apply stage, but then it's unable to create a pod. So there's a way for an improvement in getting this information back to a user.

Will $ racetrack deploy job.yaml succeed while kubectl apply runs in the kubernetes plugin? Where is the timeout?

racetrack deploy job.yaml will fail, but after 15 mintues (after the timeout).
The timeout comes from the liveness probe check, Lifecycle tries to check the /live endpoint of a job, but since the pod doesn't exist, it waits indefinitely until it appears:
https://github.com/TheRacetrack/racetrack/blob/5bb2f98e7589e5dd549c28c21ea91ff7c29dfe8b/lifecycle/lifecycle/monitor/health.py#L36

Do we want this feature to be in lifecyle-supervisor, or is it something in kubernetes plugin?

Good question. Probably it's going to end up in kubernetes plugin, but if possible we could bring some generic parts into the Lifecycle (in order not to repeat the same thing in many plugins).


Performance

It seems, after a while working with VS Code and several compiles -> Run, the performance is degrading. Resources are available on the Azure VM (using the august image - not docker, since there is some other issue I can't figure out yet). However, once I start making changes (currently trying to add additional fields and groups to a custom page), I am seeing a lot of "red highlights" and errors popping up. It will take several minutes for the system to catch up to me typing and then finally removing the problem reports (those only were, because it was checking unfinished typing). Looking at the task manager, I have the Microsoft.Dynamics.Nav.EditorServices.Host running at 50+% CPU the entire time.
I am not sure what can be improved there, but the issue obviously is somewhere in the "live connection" to the NAV service tier instance and generated latency through this. I am going to keep monitoring this to see, if I can find a pattern when this starts happing. When I restart the service tier and VS Code, it starts working well again. Starting to narrow down the required actions to resolve the issue, but wanted to report it already.

What is the project size approximately? What size of VM are you running on?
Very large projects will put more pressure on the system, but it shouldn't give the experience you are describing. I have worked with a 6000+ object project (W1) on my Surface Pro 4 with a good experience.
With august update we made a number of performance improvements and changed the background compilation service. The language service will wait a second after the last keystroke before doing the first starting the background compilation for the edited document.
I'm very interested if you can narrow down the problem to specific tasks, since I haven't experienced that and I haven't heard anything like that from our internal teams.

I can confirm that this is happening for me as well (local docker-based installation) with a very small project (approx 30 objects). I think it still happened with August update but am not 100% sure

I'm also experiencing this on a Surface Pro 3 and the August update. I had to turn off codelens and then the issue seemed to go away......but I do love codelens so I'd like to keep it on. I have 87 object files currently.

I have August update and probably 50 objects, so very small. The work around is to actually only close out VS Code and start it again. Service tiers, etc. do not need to be restarted. The VM is actually smaller than I thought, it's a D2 - I guess that's standard with the deploy package.
I noticed it happening mainly when working on pages or page extensions, I can get this to happen more often when adding or editing fields. I am trying to work on this a bit more to see, if there is more of a pattern.

Have notice increased memory usage over time?
We will investigate this. If you have more information that can help us reproduce please let us know. E.g. working with certain objects etc.

@pzentner @tfenster can you try to turn CodeLens of? Just add
"editor.codeLens": false

to the settings file? At let me know if it changes something.

When it happens or to prevent it from happening?

I have turned it off and will monitor it. And to answer your other question, I have seen increased memory usage over time, but not on the EditorServices or VSCode, but on the NAV Service Tier - and I would assume that this is from running the navx packages.

I'll keep a better eye on memory usage as I've not been paying that much attention to it. It does look like it's increasing over time. I did look earlier today and the editor service was around 420MB. It's now at 485MB.  It's been at least 2-3 hours since I first looked.
I've been creating a lot of new objects today as I'm building out a new functional area so not exactly sure if a specific scenario is causing it or not.

@tfenster  To prevent it. The CodeLens feature is costly. All other files most be scanned to find the show symbols and VsCode is requesting it fairly often. We may investigate if we should cache/limit the resources spend here.

@MikeGlue More objects/code will create a larger working set, but it should only grow proportionally to the added code. Hard to say what is the right number here.

@esbenk ok, will do. We are kind of finished with development of our first app and the current challenge is more about how to get it published (which is not very well documented, but here is probably the wrong place to discuss that), so not too much coding is currently happening. But there will be bugs to be fixed and improvements to be made and I'll try then and make sure my colleagues do the same

This may or may not be useful, but here's what my last hour looked like. Most of this is what I would expect but looks a bit weird that while I was working in the same objects and reducing the overall compile errors, the memory usage was actually increasing, until I got down to a single compile error. Over the course of the day I can see then how my memory usage got to over 400MB because I was working on a lot of different objects over the day, but I don't understand the memory increase as I am working within the same 2 objects for an hour.
In any case, if useful, here's what I saw while working away. What I was doing was bringing in 2 posting codeunits from my other app into the one I'm currently working on. Obviously that caused compile errors so I was just working my way through the references, etc. to point the functions to the current app.
The one thing I use a lot and have done so today, was using the rename symbol feature, as I'm doing a lot of this type of work today bringing over functionality from one app to another.
4:00pm - 170 MB (fresh launch, 87 objects)
4:07pm - 187 MB (modify 1 page and 1 table)
4:11pm - 198 MB (add 2 codeunits)
4:15pm - 226 MB (copy in functions from other codeunit and change variables, causing large number of compile errors [92] while references are being updated in code via rename symbol, etc.)
4:25pm - 206 MB (updates to new codeunits to reduce compile errors [80])
4:37pm - 248 MB (updates to new codeunits to reduce compile errors [50])
4:48pm - 249 MB (updates to new codeunits to reduce compile errors [31])
4:55pm - 253 MB (updates to new codeunits to reduce compile errors [1])
4:59pm - 236 MB (updates to a table to resolve last compile error)
5:01pm - 241 MB (F5 to compile and publish - no errors, successful deployment)
5:04pm - 170 MB (close and launch VS Code, 89 objects)

I haven't done a lot the rest of the day (was mainly done for today and was working on testing and smaller things), but once codeLense was turned off, it seems like this issue went away. I have monitored it - whenever I did anything in VSCode and the performance overall was better and it didn't seem to get to the point where I would have to wait quite a while for everything to be sorted out.
I will add more comments once I work more again.

I will see if can limit the resource consumption used the CodeLens feature. Unfortunately all the fancy intellisense comes with a CPU cost.

I think, some more advanced caching or limiting of when files are processed seems to be the best option between having the feature and having it perform well. the issue seems like it is a runaway task or something, because it shouldn't happen with such small projects or get worse over time.
So, only limiting resources might not fix the underlying issue, but I can't really point you to the pattern to repo the issue

What I meant was, to be smarter about when we count references for the CodeLens. There may be other thing we can do.
Modern intellisense puts an almost constant load on the cpu - not just for AL. The C# solution I'm working on is also putting a significant load on the cpu in the background.
The important is to be smart about when and what to spend time on - and there may still be some bugs that also adds to the equation.

I can confirm that if I work with about 30 files in one Projects AL start to

show compilations problems, that does not exist. If I click on problem it disappear
slows down
crashes AL sometimes (see https://github.com/Microsoft/AL/issues/540)
I found that it happens when I modify pages and groups mostly

We forgot to update this thread. This issue should have been fixed quite a long time ago.
Please let us know if you're still seeing the problem.


Full Screen button not working on safari

Probably need webkit-prefix ?
https://caniuse.com/#feat=fullscreen

Well spotted, and yes 99% sure that's the fix

Fixed in #296


snippets:xen_dom0:boards:rpi_5: fix addresses for xen_dom0 config

After enabling OPTEE some chunks of memory, allocating for Dom0 by Xen was changed. These addresses are board specific and should be changed manually after each configuration change for the board.

Reviewed-by: Dmytro Semenets<EMAIL_ADDRESS>

NACK/ Pls review https://github.com/xen-troops/zephyr-dom0-xt/pull/18

Closing MR as it was fixed with changes provided in the PR mentioned above.


Feature request Force gossip update

Hi,
Is it possible to force a gossip update so IP address can keep in check?
Thanks

This isn't possible as far as I'm aware so you would need to request in https://github.com/helium/miner or https://github.com/helium/erlang-libp2p or https://github.com/helium/erlang-libp2p/issues/373


Makes cantaloupe URL configurable

DRUPAL_DEFAULT_CANTALOUPE_URL is one of those ISLE environment variables that should change the cantaloupe URL, but doesn't (i.e. it may have effect only upon an initial install).
This PR adds DRUPAL_DEFAULT_CANTALOUPE_URL to the config overrides in settings.local.php, and updates the values in config/sync to bogus values, thus forcing the user to define a  DRUPAL_DEFAULT_CANTALOUPE_URL that overrides these bogus defaults.  these bogus values are intended to be committed to config/sync.  The point is to make sure things break in an obvious way if DRUPAL_DEFAULT_CANTALOUPE_URL is not set
Note:  I'm not including a snapshot in the PR, as it is unnecessary to do so.
To test

make reset
Do make config-import to pull in the bogus openseadragon URLs
If you want, look in the configuration UI and verify that a bogus value of env:DRUPAL_DEFAULT_CANTALOUPE_URL is present.
Add a new repository item (fill in the annoying required fields), make sure it's an Image model, and make sure the openseadragon hint is checked.
Once the repository item is created, add new image media.  Make sure to check original file so that derivatives are generated.
Navigate to the repository item's page (e.g. /node/XYZ),  You should see the openseadragon viewer.  After a delay, you'll see the image pop up in the viewer.  This verifies that Drupal is using the overriden config rather than the bogus values imported.

Resolves jhu-idc/idc-general#336

OK, it seems the cloud instance was using the wrong env var for this, so we need to wait until the instance is unblocked to see whether this was an actual issue or not.
This PR can be closed if the env var works in the cloud instance.  However, I missed the runtime config lines in custom setup (I was looking in the ISLE-authored runtime-parameters-setting code in idc-isle-buildkit).  With hindsight, just setting variables directly in settings.local.php where possible seems so much more straightforward and maintainable.  I'd much prefer we do that for everything we can, but perhaps it's not a good time to rock the boat if the existing mechanism ends up working after all.

The existing DRUPAL_DEFAULT_CANTALOUPE_URL environment variable does work in the cloud, so this PR is not necessary


[GEN-1910]: init workflow for UI E2E tests (using Cypress)

This pull request includes multiple changes to improve the end-to-end (E2E) testing workflow and add Cypress testing capabilities. The most important changes include updates to the E2E workflow configuration, Cypress configuration and tests, and new scripts for managing the Odigos UI.
E2E Workflow Configuration:

.github/workflows/e2e.yaml: Added 'ui' to the test scenarios and removed the installation step for the frontend in certain scenarios. [1] [2]

Cypress Configuration and Tests:

frontend/webapp/cypress.config.ts: Updated the Cypress configuration to use Cypress.ConfigOptions and adjusted the base URL and other settings.
frontend/webapp/cypress/e2e/spec.cy.ts: Added a basic Cypress test to verify the template spec.
frontend/webapp/package.json: Added new scripts for running Cypress tests and updated the Cypress dependency version. [1] [2]

Odigos UI Management:

tests/common/odigos_ui.sh: Added a new script to manage the Odigos UI, including starting, stopping, and testing the frontend and backend processes.

Miscellaneous:

tests/common/.gitignore: Added entries to ignore .pid and .log files.
tests/e2e/ui/cypress-test.yaml: Added a new YAML configuration file for running E2E Cypress tests against the Odigos UI.

PR moved to: https://github.com/odigos-io/odigos/pull/1912


Upgrade recover prechecks

This pull request adds two things:

The fix_failed_prechecks environment variable for mkcloud. If set to 1, mkcloud will attempt to recover from failed prechecks by deleting the offending barclamps, just like a customer would have to do it.

Two additional upgrade jobs for deliberately failing and recovering from failed prechecks that use this mechanism. Only two, because I omitted the without-nodes-upgrade job - the precheck show stoppers only affect the controllers anyway.

Note: this is currently only implemented for the Cloud 8 to Cloud 9 upgrade.

@jgrassler looking at the travis results, it seems that you forgot to add the template files and there is some bash indent fixing to be done

No longer needed: we already tested this to exhaustion manually by now (see Jira ticket for details).


Minor enhancements around aliasing of aggregates

Allows an options object to specify alias (as suggested in https://github.com/tgriesser/knex/issues/3315#issuecomment-507439215) (Closes #3315)
Allows multiple aliases when using object syntax (Closes #2871)

One test is failing on mssql.

@kibertoad this has now been addressed.

I assume this also needsdocumentation update?

Added issue for it.

Yes, I'll take care of that.


fixed retrieving initial value being delayed, set default matchers for s...

...erver side Fixes #104.

Awesome, thank you!


Documentation

The index.rst could benefit from an introduction (re-using the README) explaining the goal of the library, how to use, pointers to the GitHub repository, external links, etc).
A usage section using real-data would be also welcome.

Uhm... The content of the docs folder is created by sphinx automatically to produce the API documentation
http://bruker2nifti.readthedocs.io/en/latest/
I am not sure if the folder docs has to be added to .gitignore or not, as it can be distracting for the
About the real-data, I'm updating the wiki page with some examples!

Still, you can modify the index.rst file since it is the master file (from you conf.py). Not much is needed but the current content is rather minimal.

Done! I'm not sure if it will be overwritten in re-creating the documentation with Sphynx. Will try and find another solution to make this part of the documentation more talkative!

I think the doc is in rst format and you used markdown for links. You need to modify them as:
text -> text <link>_
Apart from that, I think you're good. I would personally extend the index a little bit but it's up to you at this point.

Closing for now.
Feel free to re-open for further suggestions in this thread. Thanks


Add support for setting limit for Tracks.getSimilar()

looks good, thanks

Glad to help, thanks for the great work you are doing!


engine: remove CAP_PERFMON, CAP_BPF, CAP_CHECKPOINT_RESTORE from relnotes

closes https://github.com/docker/docker.github.io/issues/13731
closes https://github.com/docker/docker.github.io/issues/14124

These capabilities were reverted in https://github.com/moby/moby/commit/a38b96b8cdc4d345a050b417c4c492b75329e5a6 (https://github.com/moby/moby/pull/41563),
because the version of containerd and runc that shipped together with
docker 20.10.0 did not support them.
Current versions of containerd and runc support these, so possibly we can
include them again in a patch release, but otherwise support will come in
the next (22.06) release of docker engine.

Proposed changes

Related issues (optional)

No, this is deleting an entry from the release notes, because the new feature was reverted/disabled before the 20.10.0 release, so didn't make it into the release, and should not have been included in the changelog


Separate from jQuery.UI widget

Hey, do you plan on separating the main upload functions away from jQuery UI? This would make it much easier to integrate into for e.g. an app which is primarily using Backbone!

I have no plans to replace the jQuery UI widget factory:
The widget factory is independent from jQuery UI as is has no other dependencies.
It's lightweight and provides a sensible implementation for a stateful jQuery widget.
Here's an insightful presentation about the benefits of the widget factory:
http://ajpiano.com/widgetfactory/
However, I'm open to suggestions for a different implementation for stateful jQuery widgets.


[FancyZones] It puts a default three-column layout on my no-layout screen

Microsoft PowerToys version
0.68.1
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
FancyZones
Steps to reproduce
To me I have only dual screens, both 4K resolution. Screen A is vertical with a custom three-row layout which has no issues. Screen B is horizontal and has "no layout" for the whole time, but if I trigger FZ here (shift + drag or drag + right click), I'll see the default three-column layout with some zone gaps. Tried creating a custom "no layout" and apply to screen B, and set it to the default for horizontal screens, neither helped.
PowerToysReport_2023-03-12-21-38-47.zip
✔ Expected Behavior
No layout is no layout, there shouldn't be a layout forced to exist.
❌ Actual Behavior
A default three-column layout is applied to the screen which is set to use "no layout'.
Other Software
No response

@SeraphimaZykova FYI

This has been fixed on 0.71.0. Please update to the latest PowerToys version.


States panel only shows color attributes for Hue bulbs when I open the color picker on the Hue app

Home Assistant release with the issue:

0.67.1
Last working Home Assistant release (if known):
Not sure when it changed but definitely working in the past.
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io on RPi3
Component/platform:

https://www.home-assistant.io/components/light/
Description of problem:
The states panel only shows color attributes when the color picker is open on my mobile phone.

This is what it looks like.
I then have to open the color picker on my hue app (this screen)

And then the states page magically refreshes with all color attributes.

After closing the color picker within the Hue app, the states page will again refresh back to the original screenshot, without color attributes.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
  bridges:
    - host: <IP_ADDRESS>
      allow_unreachable: true

Traceback (if applicable):

Additional information:

The Hue states will not show color information when a white color (i.e. color_temp) is set.


Add serialization support to chat models #9

connects #9

@kaojohnny
I think the models in Chat Plugins should keep a reference to Skygear Record since the models are backed by Skygear Records. All model serialization can be done by calling fromJson or toJson method of the referred Skygear Record.

@ben181231 Not sure what do you mean, I do use toJson or fromJson, ex:
jsonObject.put(RECORD_KEY, conversation.getRecord().toJson());

in ConversationSerializer.java.
or you want me to remove ConversationSerializer.java?

@kaojohnny What I mean is that the model is actually a Skygear record. There is no need to wrap it. If we keep a reference to it, we can directly use the serialization of Skygear record. i.e. All the serialization method will be:
public JSONObject toJson() {
    return this.record.toJson();
}

Updated. Thanks.


jx boot - Additional property azure is not allowed in vault

Hello,
Thanks for the module, works like a charm. I created cluster on Azure, everything seems to be in order, but when I try to use jx-requirements.yml with jx boot I get following error:
WARNING: validation failures in YAML file ~/jenkins-x-boot-config/jx-requirements.yml: vault: Additional property azure is not allowed
error: unable to load jx-requirements.yml: validation failures in YAML file ~/jenkins-x-boot-config/jx-requirements.yml:
vault: Additional property azure is not allowed

I looked into banzai vault operator, it seems to support Azure Key Vault. But when I looked into jx docs I see message
The Bank-Vaults operator is currently only supported with GKE or EKS., see here: https://jenkins-x.io/docs/reference/components/vault/
Do you have some beta version of jx, where jx boot command works with azure vault?
Or should I open issue on jx?
Thank you

/jenkins-x/jx/#7544

So with using prerelease version of jx, I was able to move forward, but got stucked on this error with vault creation: 503 Service Temporarily Unavailable.
So my vault stetefulset isn't initialized correclty:
$ kubectl logs -n jx jx-vault-asptstsmashin-0 -c bank-vaults
time="2020-09-09T07:45:18Z" level=info msg="initializing vault..."
time="2020-09-09T07:45:18Z" level=info msg="vault metrics exporter enabled: :9091/metrics"
[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
 - using env:	export GIN_MODE=release
 - using code:	gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET    /metrics                  --> github.com/gin-gonic/gin.WrapH.func1 (3 handlers)
[GIN-debug] Listening and serving HTTP on :9091
time="2020-09-09T07:45:22Z" level=fatal msg="error initializing vault: error testing if vault is initialized: Get http://<IP_ADDRESS>:8200/v1/sys/init: dial tcp <IP_ADDRESS>:8200: connect: connection refused"

Do you have any idea why, or should I open issue on banzaicloud/vault?

Yes, exposing ENV_VARS helped, thank you.
Wouldn't it be possible, to configure Vault with secret_ref, and create this secret using kubectl provider?
Thanks
P.S. Issue can be closed.

There will be further changes  in this space in jx3 to optimise how these secret details are passed between terraform and jx to make it more zero touch


Fix sync server issues

Discovery:

edge nodes keep disconnecting from central storage node (ping timeout)
edge nodes are throwing errors

invalid signature errors
too many agents within one account (2)

Clearest indication of data not being saved is: create account, delete local storage, app hangs on load because account isn't synced back from syncing server (was never stored?)

Main issue seems to be a couple problematic CoValues (causing the above exceptions) that completely bring down the storage subsystem on both edge and central servers. The servers keep running though instead of properly crashing and restarting so we get stuck in a state where sync servers are online but not persisting any new values.

While the above isn't addressed yet at the root, another major problem seemed to be around apps requesting a lot of binary data leading to large amounts of buffering as the data can't be sent out over the network quickly enough, resulting in out-of-memory errors.There's a hotfix in place now that applies a simple kind of backpressure in these situations which seems to have alleviated this issue.

After addressing the most pressing out-of-memory problems, my focus today will be on addressing the errors where individual problematic CoValues can bring down the entire storage subsystem. They happen quite rarely, but did happen again overnight (for me). I restarted the sync server so persistence is back online.The first effort towards adding more resilience is making sure we don't throw errors that can crash contexts much higher up. Moving to using Results from neverthrow (https://github.com/gardencmp/jazz/issues/329)

Final update on this

the most pressing issues and sources of crashes have been addressed
things have been running smoothly for a couple days now and that's despite one of you essentially stress-testing the new infrastructure with a mass-ingest of about 300k CoValues ❤

Mini-postmortem, actions taken & future work

this was essentially just tech-debt and fragile MVP architecture catching up with me
I reprioritised a bunch of stuff and fast-tracked important refactors and fixes

if you're interested in details, a lot of this was about isolating failures, introducing important forms of back-pressure and replacing broken async code that was trying to be unnecessarily clever with simpler sync code

my focus this week was to address the immediate problems first and map out improvements to be done on a continuing basis
what really helped was to set up more precise observability that lets me debug the sync status of individual CoValues and run a debugger in the production sync servers if necessary
by making you aware that there might be issues with the infra, you all kindly reported every problem you're encountering

this surfaced a lot of completely unrelated stuff, some of which I fixed immediately, for other stuff I created tickets
this also surfaced that a lot of the higher level API is not very helpful when it comes to partial failures affecting individual CoValues, often making it look like entire collections of CoValues aren't syncing. Expect some improvements very soon in upcoming releases

the need for full-stack integration tests became very clear and we will make use of the example apps for that. I don't want you to be the first to find out about issues with the sync infra

There aren't really any learnings from this deeper than "don't write brittle code", "take distributed systems seriously" and "test everything". It's just early days, all the ways in which we need to do better are obvious and we now have the time and energy to focus on those.
Your patience, understanding and trust means a lot to me. Let's go chase these nine 9's!


Conflation with parpendicular reaches

https://fim.s3.amazonaws.com/stac/dev2/Crystal Creek-West Fork San Jacinto River/WHITE OAK CREEK WEST TRIB NO 1/WHITE OAK CREEK WEST TRIB NO 1-nwm_conflation.png

@mdeshotel lets add tests and documenation as we fix conflation edge cases.

The behavior stems from a similar issue to this edge case: no conflation due to the starting point of the ras models river extending far downstream from the xs’s. (I think🤨)

This should have been closed with release 0.5.0 of ripple1d. This will no longer conflate because the most upstream cross section and most downstream cross section are the same.


Add Bruinwalk popup to the side. But still needs to figure out observer and DOM creation order

could rework the button to show score, and on hover shows "view bruinwalk review"
will get average rating for each class, and will add to backend server instead of having user fetch from bruinwalk because it's difficult to work with chrome.sendmessage() function to fetch bruinwalk html

Looks like you only used jquery on one occasion in line 93 of bruinwalk.js. We can delete jquery and just use normal javascript.

Removed jquery.
Todo:

[ ] add average rating to radar chart
[ ] check frontend compatibility with other devices
[ ] test cases


Understanding the amplify-meta.json file

Amplify CLI Version
11.1.0
Question
Hey there
Im struggling with this error:
amplify-meta.json' does not exist
It seems every time I run amplify pull its not getting generated.
What do I need commands do I need to run when I clone my Github project on different machine or even on a remote machine through a script?

Hey @lindanip, 👋 thank you for reaching out. This message normally occurs on project that has not been init'd amplify init.
Does the repository contain amplify/team-provider-info.json file?
If this a fresh clone of your project, you may need to run amplify init.
Could you reopen the issue with the bug template as this would enable us in collecting additional information such as reproduction steps and environment.

So this is the script I've been trying to run on a remote server where the app apk file will be built, but its not generating the required files. the installation of amplify and AWS cli are successful
`#!/bin/bash
npm install -g @aws-amplify/cli
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
aws configure set aws_access_key_id $AWS_ACCESS_KEY
aws configure set aws_secret_access_key $AWS_SECRET_ACCESS_KEY
aws configure set default.region us-west-2
aws configure set default.output json
amplify init -y
amplify pull --appId  --envName dev
`

Hey @lindanip, thank you for the information. From error message provided the issue occurs when passing a name of the project which does not meet the naming constraint name must be between 2 and 10 characters, and lowercase only.. when running amplify init -y the Amplify cli will refer to the present folder name and create the Amplify project with the name. To verify if the name may be causing this issue could you try creating a new folder with a longer name and lowercase only, then change directory to the folder and run amplify init -y.
Additionally, this issue also occurs when running a init in project that have amplify and amplify-backup folder present from a previous failed pull or init.
I observed that you are pulling in a existing Amplify backend in the script. If the intention is to pull a existing project automatically using the script. After the configure step run we should be able to run  amplify pull --appId <app-id> --envName dev -y for Amplify CLI to generate the required files.
It would be great if you could provide some additional information on use case for the script.

Hey, So my use case
I have an expo managed app that uses the amplify for auth and a post confirmation function.
Im using EAS (Expo application service), to build my app with eas build  but the build fails on the amplify configurations.
Im trying to configure amplify on eas-build-pre-install in the package.json with the script above.
e.g "eas-build-pre-install": "sh ./scripts/eas_pre_build.sh",
note:  /scripts/eas_pre_build.sh this file contains the script`
So all I need for amplify to generate the required files so the app can finally build, its been weeks and Im still struggling, its really frustrating and this app is supposed to test by investors this week, everything else is working just the one problem , we've went through the docs over and over and we don't find any light.
Right now I'm struggling with a new error:
the command that cause it: aws configure set default.output json --profile <aws-profile-name>
the result:
`Could not initialize platform for 'dev': Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
Resolution: Review the error message and stack trace for additional information`

Hey, So my use case
I have an expo managed app that uses the amplify for auth and a post confirmation function.
Im using EAS (Expo application service), to build my app with eas build but the build fails on the amplify configurations.
Im trying to configure amplify on eas-build-pre-install in the package.json with the script above.
e.g "eas-build-pre-install": "sh ./scripts/eas_pre_build.sh", note: /scripts/eas_pre_build.sh this file contains the script`
So all I need for amplify to generate the required files so the app can finally build, its been weeks and Im still struggling, its really frustrating and this app is supposed to test by investors this week, everything else is working just the one problem , we've went through the docs over and over and we don't find any light.
Right now I'm struggling with a new error:
the command that cause it: aws configure set default.output json --profile <aws-profile-name>
the result:
`Could not initialize platform for 'dev': Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
Resolution: Review the error message and stack trace for additional information`

Kindly assist

Hey @lindanip, could you check the amplify -> .config -> local-aws-info.json which should be contain the attribute profileName. Could check if the profile name in the file and the profile name being set on aws configure match.

Hey @ykethan,
I wanted to update you on the progress we've made regarding the issues we were facing. It seems that we have found a solution by using the script provided in the documentation (https://docs.amplify.aws/cli/usage/headless/#amplify-pull-parameters). Additionally, we decided to keep the AWS profile set to default.
Here's the script we used:
`
#!/bin/bash
set -e
IFS='|'
REACTCONFIG="{
"SourceDir":"src",
"DistributionDir":"build",
"BuildCommand":"npm run-script build",
"StartCommand":"npm run-script start"
}"
AWSCLOUDFORMATIONCONFIG="{
"configLevel":"project",
"useProfile":false,
"profileName":"default",
"accessKeyId":"headlessaccesskeyid",
"secretAccessKey":"headlesssecrectaccesskey",
"region":"us-east-1"
}"
AMPLIFY="{
"projectName":"headlessProjectName",
"appId":"amplifyServiceProjectAppId",
"envName":"myenvname",
"defaultEditor":"code"
}"
FRONTEND="{
"frontend":"javascript",
"framework":"react",
"config":$REACTCONFIG
}"
PROVIDERS="{
"awscloudformation":$AWSCLOUDFORMATIONCONFIG
}"
amplify pull
--amplify $AMPLIFY
--frontend $FRONTEND
--providers $PROVIDERS
--yes
`
We're grateful for your assistance throughout this process. Thank you very much.

Hey @lindanip, glad to hear I was able to assist you. Do let us know if you require any further assistance.


feat(pattern): Add a new pattern demonstrating running a lambda schedule

#134
Also, I've updated the architecture diagram to use EventBridge. Looks like there's two ways to accomplish scheduling using EventBridge and CloudWatch.

At first glance looks great, i'll run through and do the due diligence deploy checks etc later today. If that all works I will merge it into a branch and then add in a Python version. Thanks for contributing!

I just updated the PR to remove unused dependencies and some imports in the stack tests.


Add LNURL-withdraw Support

Is your feature request related to a problem? Please describe.
Bitcoin Jungle has some General Bytes BATMs that require a wallet to support LNURL-withdraw in order to buy bitcoin over lightning.
Describe the solution you'd like
When scanning a LNURL-withdraw QR code, it should allow the user to receive bitcoin over lightning.
Additional context
We've written some code for this and is currently in testing. Wondering if Galoy would be interested in a PR for this?

We've written some code for this and is currently in testing. Wondering if Galoy would be interested in a PR for this?

definitively. is it mobile only or do we need to change something on the backend as well?

+1 to be able to receive by scanning an LNURLw string.
On the other hand being able to generate an LNURLw string would allow paying with the link while offline.
It can be loaded to an NFC sticker or card as well for contactless support or just support offline usage of the wallet app.

Turned this feature request into a bounty!

this has been implemented


chore: speed up build time

/gcbrun

/gcbrun

/gcbrun

/gcbrun

Hmm, I didn't dig into this yet, but only the last test working in a parallel set can indicate a range variable that wasn't captured.
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/frontend (590.60s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-ledgerwriter (621.48s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-balancereader (622.21s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-contacts (651.06s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-userservice (653.14s)
Step #32 - "appsource-verify":     --- PASS: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-transactionhistory (806.85s)

Hmm, I didn't dig into this yet, but only the last test working in a parallel set can indicate a range variable that wasn't captured.
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/frontend (590.60s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-ledgerwriter (621.48s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-balancereader (622.21s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-contacts (651.06s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-userservice (653.14s)
Step #32 - "appsource-verify":     --- PASS: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-transactionhistory (806.85s)

Looks like transactionhistory is always being used as the delivery-pipeline
Step #32 - "appsource-verify": TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-contacts 2024-06-11T14:04:32Z command.go:100: Running command gcloud with args [deploy releases list --project=contacts-admin-52b8 --delivery-pipeline=transactionhistory --region=us-central1 --filter=name:c7ee59e --format json]

Hmm, I didn't dig into this yet, but only the last test working in a parallel set can indicate a range variable that wasn't captured.
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/frontend (590.60s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-ledgerwriter (621.48s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-balancereader (622.21s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-contacts (651.06s)
Step #32 - "appsource-verify":     --- FAIL: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-userservice (653.14s)
Step #32 - "appsource-verify":     --- PASS: TestSourceCymbalBank/../../../6-appsource/cymbal-bank/ledger-transactionhistory (806.85s)

Yup, looks like transactionhistory (suffixServiceName) is always being used as the delivery-pipeline Step #32 - "appsource-verify": TestSourceCymbalBank/../../../6-appsource/cymbal-bank/accounts-contacts 2024-06-11T14:04:32Z command.go:100: Running command gcloud with args [deploy releases list --project=contacts-admin-52b8 --delivery-pipeline=transactionhistory --region=us-central1 --filter=name:c7ee59e --format json]

I captured in a map now.

/gcbrun

/gcbrun

/gcbrun


Hantanet- when  a test FASTA is loaded, threshold is displayed as SNPs

When I load my sequences into HantaNet, distance threshold shows up as SNPs although Hantviruses ref set is loaded with TN93

Browser [Chrome]
Version [0.6.2]

Clearing cache poses a fix, meaning it stores in local storage incorrectly at some point. Will look into it.


Fix: docker snapshot restoration

Description
This fixes multiple issues with snapshot restoration in Docker:
ERROR:  cannot drop objects owned by role postgres because they are required by the database system

and
pg_restore: [archiver] unsupported version (1.14) in file header

Checklist

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] Any changes are noted in the changelog
[ ] Code is formatted with fourmolu on version <IP_ADDRESS> (which can be run with scripts/fourmolize.sh)
[x] Self-reviewed the diff

Migrations

[ ] The pr causes a breaking change of type a,b or c
[ ] If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
[ ] Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate
more what the migration achieves, what it cannot achieve or why a migration is not possible.

Note that, once this is merged, we'll probably need to backport and release to at least 13.3 and 13.2


Correct Pie patch to prevent .orig files

Hi,
was annoyed by getting .orig files created, as index was off. This should fix it.
Best
Chris

This is idle for >6 month, I guess it is not needed


Update README to mention some of the new features

Smart boiler support
On/off feature via device construct
Sensor showing whether the boiler's heater is currently working

Note: HACS documentation should also be updated.

Closed with https://github.com/qbaware/homeassistant-eldom/commit/d3eec1ce127452c67f83d8df9057c4733d6d9bd7.


improvement: implement an alternative way to run selected tests rather than specifying a feature only for tests

In runtime Cargo.toml, a feature spiceai-dataset-test is only used in integration test.
There are alternative way to do so.

using env
using different test target
using information exposed from runtime to decide run or not when running
using test name pattern

fixed by #2120


Switching to appium mac2 driver with no action

When i work with Appium Mac Driver i am able to open an app. But when i switch to Appium Mac2 Driver nothing happen even the code [java] shows no error. I have this output in Appium ->
Output:
puresk-MacBook-Pro:~ pure$ [HTTP] --> POST /wd/hub/session
[HTTP] {"desiredCapabilities":{"app":"Activity Monitor","automationName":"mac2","platformName":"mac","deviceName":"Mac","newCommandTimeout":300},"capabilities":{"alwaysMatch":{"appium:app":"Activity Monitor","appium:automationName":"mac2","appium:deviceName":"Mac","appium:newCommandTimeout":300,"platformName":"mac"},"firstMatch":[{}]}}
[debug] [W3C] Calling AppiumDriver.createSession() with args: [{"app":"Activity Monitor","automationName":"mac2","platformName":"mac","deviceName":"Mac","newCommandTimeout":300},null,{"alwaysMatch":{"appium:app":"Activity Monitor","appium:automationName":"mac2","appium:deviceName":"Mac","appium:newCommandTimeout":300,"platformName":"mac"},"firstMatch":[{}]}]
[debug] [BaseDriver] Event 'newSessionRequested' logged at<PHONE_NUMBER>242 (12:30:55 GMT+0100 (Central European Standard Time))
[Appium] Appium v1.20.2 creating new Mac2Driver (v0.8.1) session
[debug] [BaseDriver] W3C capabilities and MJSONWP desired capabilities were provided
[debug] [BaseDriver] Creating session with W3C capabilities: {
[debug] [BaseDriver]   "alwaysMatch": {
[debug] [BaseDriver]     "platformName": "mac",
[debug] [BaseDriver]     "appium:app": "Activity Monitor",
[debug] [BaseDriver]     "appium:automationName": "mac2",
[debug] [BaseDriver]     "appium:deviceName": "Mac",
[debug] [BaseDriver]     "appium:newCommandTimeout": 300
[debug] [BaseDriver]   },
[debug] [BaseDriver]   "firstMatch": [
[debug] [BaseDriver]     {}
[debug] [BaseDriver]   ]
[debug] [BaseDriver] }
[BaseDriver] The following capabilities were provided, but are not recognized by Appium:
[BaseDriver]   app
[BaseDriver] Session created with session id: 79cb81b6-fa5b-43af-bed8-a6450eb83e76
[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://<IP_ADDRESS>:10100/status] with no body
[debug] [WD Proxy] Got response with status 200: {"value":{"message":"WebDriverAgent is ready to accept commands","state":"success","os":{"version":"Version 11.1 (Build 20C69)"},"ready":true,"build":{"time":"Feb  9 2021 11:45:22"}},"sessionId":null}
[WebDriverAgentMac] The host process has already been listening. Proceeding with session creation
[debug] [WD Proxy] Matched '/session' to command name 'createSession'
[debug] [WD Proxy] Proxying [POST /session] to [POST http://<IP_ADDRESS>:10100/session] with body: {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"platformName":"mac","app":"Activity Monitor","automationName":"mac2","deviceName":"Mac","newCommandTimeout":300}}}
[debug] [WD Proxy] Got response with status 200: {"value":{"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3","capabilities":{"CFBundleIdentifier":"com.apple.finder"}},"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3"}
[WD Proxy] Determined the downstream protocol as 'W3C'
[Appium] New Mac2Driver session created successfully, session 79cb81b6-fa5b-43af-bed8-a6450eb83e76 added to master session list
[debug] [BaseDriver] Event 'newSessionStarted' logged at<PHONE_NUMBER>252 (12:30:55 GMT+0100 (Central European Standard Time))
[debug] [W3C (79cb81b6)] Cached the protocol value 'W3C' for the new session 79cb81b6-fa5b-43af-bed8-a6450eb83e76
[debug] [W3C (79cb81b6)] Responding to client with driver.createSession() result: {"capabilities":{"platformName":"mac","app":"Activity Monitor","automationName":"mac2","deviceName":"Mac","newCommandTimeout":300}}
[HTTP] <-- POST /wd/hub/session 200 10 ms - 192
[HTTP]
[HTTP] --> GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76
[HTTP] {}
[W3C (79cb81b6)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76' to command name 'getSession'
[debug] [WD Proxy] Proxying [GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76] to [GET http://<IP_ADDRESS>:10100/session/4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3] with no body
[debug] [WD Proxy] Got response with status 200: {"value":{"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3","capabilities":{"CFBundleIdentifier":"com.apple.finder"}},"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3"}
[WD Proxy] Replacing sessionId 4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3 with 79cb81b6-fa5b-43af-bed8-a6450eb83e76
[HTTP] <-- GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76 200 4 ms - 170
[HTTP]
[HTTP] --> GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76
[HTTP] {}
[W3C (79cb81b6)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76' to command name 'getSession'
[debug] [WD Proxy] Proxying [GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76] to [GET http://<IP_ADDRESS>:10100/session/4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3] with no body
[debug] [WD Proxy] Got response with status 200: {"value":{"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3","capabilities":{"CFBundleIdentifier":"com.apple.finder"}},"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3"}
[WD Proxy] Replacing sessionId 4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3 with 79cb81b6-fa5b-43af-bed8-a6450eb83e76
[HTTP] <-- GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76 200 4 ms - 170
[HTTP]
[HTTP] --> GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76
[HTTP] {}
[W3C (79cb81b6)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76' to command name 'getSession'
[debug] [WD Proxy] Proxying [GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76] to [GET http://<IP_ADDRESS>:10100/session/4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3] with no body
[debug] [WD Proxy] Got response with status 200: {"value":{"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3","capabilities":{"CFBundleIdentifier":"com.apple.finder"}},"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3"}
[WD Proxy] Replacing sessionId 4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3 with 79cb81b6-fa5b-43af-bed8-a6450eb83e76
[HTTP] <-- GET /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76 200 3 ms - 170
[HTTP]
[HTTP] --> POST /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76/timeouts
[HTTP] {"implicit":5000}
[W3C (79cb81b6)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76/timeouts' to command name 'timeouts'
[debug] [Protocol Converter] Will send the following request bodies to /timeouts: [{"implicit":5000}]
[debug] [WD Proxy] Proxying [POST /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76/timeouts] to [POST http://<IP_ADDRESS>:10100/session/4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3/timeouts] with body: {"implicit":5000}
[debug] [WD Proxy] Got response with status 200: {"value":null,"sessionId":"4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3"}
[WD Proxy] Replacing sessionId 4AEBB0F7-1F10-467E-8E92-4F7CE24DA8B3 with 79cb81b6-fa5b-43af-bed8-a6450eb83e76
[HTTP] <-- POST /wd/hub/session/79cb81b6-fa5b-43af-bed8-a6450eb83e76/timeouts 200 4 ms - 65
[HTTP]

[debug] [BaseDriver] W3C capabilities and MJSONWP desired capabilities were provided
[debug] [BaseDriver] Creating session with W3C capabilities: {
[debug] [BaseDriver]   "alwaysMatch": {
[debug] [BaseDriver]     "platformName": "mac",
[debug] [BaseDriver]     "appium:app": "Activity Monitor",
[debug] [BaseDriver]     "appium:automationName": "mac2",
[debug] [BaseDriver]     "appium:deviceName": "Mac",
[debug] [BaseDriver]     "appium:newCommandTimeout": 300
[debug] [BaseDriver]   },
[debug] [BaseDriver]   "firstMatch": [
[debug] [BaseDriver]     {}
[debug] [BaseDriver]   ]
[debug] [BaseDriver] }
[BaseDriver] The following capabilities were provided, but are not recognized by Appium:
[BaseDriver]   app
[BaseDriver] Session created with session id: 79cb81b6-fa5b-43af-bed8-a6450eb83e76

It seems you should provide appium:bundleId instead of appium:app.
https://github.com/appium/appium-mac2-driver#capabilities


[Spaceship] TypeError: no implicit conversion of String into Integer in app_version.rb:641

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
We experienced are crash with spaceship (0.30.0).
Looks like the parsing of the trailers is broken. Was it an array before?
spaceship/tunes/app_version.rb:636 which crashes for us (see the attached stacktrace):
        display_families.each do |display_family|
          trailers = display_family.fetch("trailer", {}).fetch("value")
          next if trailers.nil?

          trailers.each do |trailer|
            trailer_data = trailer["value"]
            next if trailer_data.nil?
            data = {
                device_type: display_family['name'],
                language: row["language"]
            }.merge(trailer_data)
            result << Tunes::AppTrailer.factory(data)
          end
        end

This resolves the crash for us:
        display_families.each do |display_family|
          trailer_data = display_family.fetch("trailer", {}).fetch("value")
          next if trailer_data.nil?
          data = {
              device_type: display_family['name'],
              language: row["language"]
          }.merge(trailer_data)
          result << Tunes::AppTrailer.factory(data)
        end

Fastlane stacktrace
14:48:09 TypeError: [!] no implicit conversion of String into Integer
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:641:in `[]'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:641:in `block (2 levels) in setup_trailers_for'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:640:in `each'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:640:in `block in setup_trailers_for'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:636:in `each'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:636:in `setup_trailers_for'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:625:in `block in setup_trailers'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:623:in `each'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:623:in `setup_trailers'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:304:in `setup'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/base.rb:182:in `initialize'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:158:in `new'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:158:in `factory'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:180:in `find'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/spaceship-0.30.0/lib/spaceship/tunes/application.rb:102:in `edit_version'
14:48:09   Fastfile:330:in `block in parsing_binding'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/lane.rb:33:in `call'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/lane.rb:33:in `call'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/runner.rb:50:in `block in execute'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/runner.rb:46:in `chdir'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/runner.rb:46:in `execute'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/command_line_handler.rb:30:in `handle'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/commands_generator.rb:51:in `block (2 levels) in run'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.50.0/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/commands_generator.rb:248:in `run'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/commands_generator.rb:20:in `start'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/lib/fastlane/cli_tools_distributor.rb:53:in `take_off'
14:48:09   /Library/Ruby/Gems/2.0.0/gems/fastlane-1.99.0/bin/fastlane:5:in `<top (required)>'
14:48:09   /usr/local/bin/fastlane:23:in `load'
14:48:09   /usr/local/bin/fastlane:23:in `<top (required)>'

Environment
fastlane 1.99.0
spaceship 0.30.0
Crash with and without bundle exec.

Hey @HeEAaD, thanks for submitting this issue. It's true, with the latest changes on iTunes Connect we had to re-write how screenshots are parsed, and didn't have the time to update the trailers code yet (see https://github.com/fastlane/fastlane/pull/5646).
Since I don't have access to any trailer-enabled apps right now, do you have the chance to take a dive into fixing this? I assume the code change is very similar to what we did with screenshots on #5646.

Oh wait, does that mean you're not trying to upload a trailer, but deliver just doesn't work, because you have a trailer?

Yes, I was not uploading a trailer.
The easiest ways to reproduce this issue:

open spaceship
try to get the app version infos: Spaceship::Tunes::Application.find(123456789).live_version
exception:

from /usr/local/lib/ruby/gems/2.2.0/gems/spaceship-0.30.0/lib/spaceship/tunes/app_version.rb:641:in `[]'

This code is working for me, as I don't have a trailer. I'll push a hotfix release ASAP 🚀

Just prepared https://github.com/fastlane/fastlane/pull/5661 and https://github.com/fastlane/fastlane/pull/5660 🚀
Once the tests pass, the release will be live

Thanks for the providing the fix @HeEAaD, the new release is live https://github.com/fastlane-old/spaceship/releases/tag/0.31.1. Could you update and let us know if that works for you?

@KrauseFx 0.31.1 is working for me; was running into the same issue.

0.31.1 fixed the issue and is working like charm. Danke Felix!

Yeah, great to hear, thanks everyone for your help 👍


Publish snapshots of native platform from CI

The snapshots would only contain the native integration for the types of agents we use on CI.
/cc @gradle/build-cache

This is option 1) from this list:

Do snapshot releases from CI for the whole distribution, which contains only the binaries for Windows, Linux and macOS. We can use these for Gradle development and periodically do a full release the same way we do now for inclusion in Gradle releases.

Split the distribution into two pieces, one which contains the 'main' platforms of Windows, Linux x64 and maxOS, and one which contains the rest of the platforms. We can release the first distribution from CI and the other in the same way we do now. This will allow us to release for the main platforms more frequently. It could also be an interesting dogfooding opportunity for 'capabilities' in dependency management land.

Split the 'launcher' piece from the APIs + integrations. The 'launcher' is the piece that takes care of finding and installing the correct native library, plus the build logic. Then, we can have the API and the integrations split into several pieces. Initially, we could have all of the existing APIs in one group and the filesystem watching APIs in another group. These would all be releasable separately but can live together so we get early integration.

It looks like this is good enough now. We have a few builds for testing and publishing native platform: https://builds.gradle.org/project/GradleNative_NativePlatform?branch=<default>&buildTypeTab=overview
All of the builds publish build scans to e.grdev.net. The build type for publishing can we used to publish snapshots with a timestamp to ext-snapshots-local.

We can also build pull request builds - automatic builds are only triggered for non-PR branches.

I also built a branch of gradle/gradle using a snapshot version of native platform: https://builds.gradle.org/viewQueued.html?itemId=29043516

The changes on native platform are:

https://github.com/adammurdoch/native-platform/pull/44
https://github.com/adammurdoch/native-platform/pull/45
https://github.com/adammurdoch/native-platform/pull/46

Looks good enough for now.


mongodb full text search and hebrew/arabic

There seems to be a really nasty behavior with the mongodb full text search and hebrew/arabic languages (unsupported by the built in analyzer/stemmer).
In the above languages, some words such as 'of'/'from'/'to' are added to the actual word. So, say - if we take the word 'reserach', to say 'to research' you would kinda glue a different word to the beginning, making it effectively look like 'toresearch'.
Now, because mongo doesn't know any of that - it sees 'research', and 'toresearch' as completely different words, and when I search for 'research' it wouldn't return 'toresearch'.. which then makes it hard to find things..
Would you have any advice on how to go about this?  Is there any way to revert to that (I know that was the old behaviour) for a project?

In other words, is there currently a way to tell mongo "please search the old fashioned way by regex"? Or an easy way to replicate this in a module?

Very reasonable question. You could override apos.get and process
options.search yourself. Also I believe mongo lets you specify the stemming
language, an option we are probably not exposing yet. I don't know if it
has good Hebrew support though.
On Jan 20, 2015 9:43 PM, "Danny Povolotski"<EMAIL_ADDRESS>wrote:

In other words, is there currently a way to tell mongo "please search the
old fashioned way by regex"? Or an easy way to replicate this in a module?
—
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe/issues/185#issuecomment-70775435.

We solved it, and if anybody else needs something similar, here is a little monkey patch:
https://github.com/madebycaffeine/old-school-search
We pad the get with a method that augments the query into a regex search rather than mongo full text.
Thanks for your help Tom! :)

Nice! FYI I don't think your module needs to have a loader method, I think
you have it there doing nothing because you're worried something bad will
happen if you don't (:
On Wed, Jan 21, 2015 at 11:27 AM, Danny Povolotski<EMAIL_ADDRESS>
wrote:

Closed #185 https://github.com/punkave/apostrophe/issues/185.
—
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe/issues/185#event-222424855.

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

Yes! :) I'll remove it. I'm still intimidated by scary things potential to happen if a variable / method is missing in apostrophe modules :P


Scrolling up sometimes stops loading messages

Sometimes scrolling to the top triggers a fetch for new messages, but they're not drawn on the screen.
Steps to reproduce:

Visit https://chat.zulip.org/#
Press home to scroll to top, waiting for the older messages to appear on screen
Press home again to scroll to top, waiting for still-older messages to appear on screen
Press home again (etc)

Sometimes the spinner icon spins then reverts to
 without any messages appearing at the top of the screen.
In dev tools, I can see that a request went out and a response came back with the older message content.
Scrolling  back down (e.g. by pressing j) causes the older messages to then appear.

I just reproduced this in the #integrations stream in Chrome on Linux, exactly as you describe: going down a message makes them appear.  I think this has been around for a long time, since it appears to affect production servers running 1.6, so we'll want to debug this by carefully reading the code path that's supposed to render those messages.  I wonder whether it could be caused by some sort of subtle browser throttling or something, but I think what's most likely is that the home key in particular confuses our navigation logic's sense of motion for updating the render window.

I see similarly wacky behavior (where the z spins, then stops, and no messages load) scrolling up with two-finger-drag on trackpad, and also with up arrow or k. It's not particular to home.

This was just fixed.  Thanks again for the excellent bug report @jmandel!

Super! This is working delightfully on https://chat.zulip.org/#


Syntax Error

Thanks for creating this great add-on.
There is a slight issue when installing it on the latest build of Node-RED.
It comes up with the following error message:
SyntaxError: Unexpected token = (line:7)
SyntaxError: Unexpected token = (line:7)
The affected command is Skoda-Get & Skoda-Set

Hi,
I just updated to Node-Red v1.3.5 and for me it's still working fine.
The SyntaxError indicates that there is a problem with your node js version or your whole installation. I'm using node js v12.22.1.
Hope that helps a little bit

I just had a look on my docker container and you are correct, my version is 10.241.
So I will need to find an image with a more up to date version of Node.js
Thanks for your help, much appreciated.


Versioned docs displaying wrong version in some topics

Bug Report
The versioned v0.10 docs are showing 0.11 in some topics where the following variables are referenced from the config.yaml file:
  release_latest: v0.10.0
  release_latest_no_v: 0.10.0
  pkg_repo_latest: 0.10.0

Even though the values in the config.yaml file are correct at 0.10
https://github.com/vmware-tanzu/community-edition/blob/release-0.10/docs/site/config.yaml
For example:
https://tanzucommunityedition.io/docs/v0.10/getting-started/#deploy-a-package
https://tanzucommunityedition.io/docs/v0.10/cli-installation/
Expected Behavior

Steps to Reproduce the Bug

Screenshots or additional information and context

Environment Details

Build version (tanzu version):
Deployment (Managed/Unmanaged cluster):
Infrastructure Provider (Docker/AWS/Azure/vSphere):
Operating System (client):

Diagnostics and log bundle

based on discussion with @stmcginnis @jonasrosland, self assigning for now to do a hard code fix


Cannot delete topic in metrics

Problem/Motivation

I added some topics to Topic Metrics in Diagnose. But now I cannot delete them when I need them no more.

Expected behavior

I expect to delete them.

Actual behavior

404 API_NOT_EXIST:Request Path Not Found

Steps to reproduce

Add some topics to Diagnose metrics and try to delete them.

Same issue here. Can't remove once added topics from metrics using UI.

As a workaround, it works when you open the admin page directly in a web browser instead of opening it through the HA interface.

Still an issue.

Same problem with "Show Payload" in "Retained Messages"

Same problem still

Still an issue.

Still an issue

I installed the same EMQX version, in standalone mode (not in HA) and traced the calls.

With an external EMQX it works fine, the call done is done via the WebUI port 18083 : http://<IP_ADDRESS>:18083/api/v5/mqtt/topic_metrics/testtopic%2Fbla returns HTTP-200.
With EMQX inside HA, the call is done via HA port 8123 and not directly to the 18083 port : http://<IP_ADDRESS>:8123/api/hassio_ingress/XXXXXXXXXXXXXXXXXXXXXXXX/api/v5/mqtt/topic_metrics/testtopic%2Fbla returns HTTP-404

I think EMQX js part doesn't like this url form ?


Still up to date?

Still up to date?

Still up to date?

Nope, this repo is not up-to-date at the moment


add graph to OTF ADR and tox env for updating plantuml

Description
This PR adds the workflow reference graph from the recent internal presentation to the OTF toolchain ADR, exploring a possible standard way to handle graphs in ADRs.
In addition to embedding plantuml inside the markdown and linking to the generated SVG file, this PR adds tox automation for updating all ADR plantuml graphs in a standardized way. This currently relies on plantuml CLI being pre-installed and is merely one possible way. Alternatives:

https://github.com/danielyaa5/puml-for-markdown: does not allow to embed puml directly inside markdown but creates and embeds / linksJK graphs automatically from links to puml files. It does this by using the plantuml server to create a link to the rendered graph. No storing svg files in the repo.
multiple github actions are available on the Marketplace: https://github.com/marketplace?query=plantuml
potentially other ones listed at https://plantuml.com/running

bors try

Why are CI tests not running in this PR anymore?

No idea, seems to work after another merge with functional.


python312Packages.maya: disable failing tests

Description of changes
Fix build (https://hydra.nixos.org/build/252542875)

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 297653 run on x86_64-linux 1

8 packages failed to build:

marge-bot
marge-bot.dist
python311Packages.flask-common
python311Packages.flask-common.dist
python311Packages.maya
python311Packages.maya.dist
python311Packages.secure
python311Packages.secure.dist

6 packages built:

python312Packages.flask-common
python312Packages.flask-common.dist
python312Packages.maya
python312Packages.maya.dist
python312Packages.secure
python312Packages.secure.dist

Result of nixpkgs-review pr 297653 run on x86_64-linux 1

2 packages failed to build:

marge-bot
marge-bot.dist

12 packages built:

python311Packages.flask-common
python311Packages.flask-common.dist
python311Packages.maya
python311Packages.maya.dist
python311Packages.secure
python311Packages.secure.dist
python312Packages.flask-common
python312Packages.flask-common.dist
python312Packages.maya
python312Packages.maya.dist
python312Packages.secure
python312Packages.secure.dist


Add logo and make title a more awesome font

A couple improvements:

Header should look like https://spring.io/, with a small green bar on top and the background-color of the logo bar the same as https://spring.io/
Font of the title should be Montserrat
Plus bubbles at the bottom should be same color as top bar (darkbrown or green, whatever looks best)

Can the top bar be a bit longer?
Current:

New:


Cant remap thumb buttons

VSCode Version:
OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

/needsMoreInfo
What key code provides click on this button for your mouse?


Add PHP 8.3 support

Q
A

Documentation
no

Bugfix
no

BC Break
no

New Feature
yes

RFC
no

QA
no

Description

Adds support for PHP 8.3.

Nice, thanks!
I'd like to wait until PHP 8.3 RC1 is released and built by sury (which will be today but no clue when the sury build will provide RC1 tho).

https://jenkins.rfc1925.org/view/PHP Engine/job/php_php8.3-binaries/
Most probably, a build from 2023-08-31 or later will indicate that RC1 is available.
I try to check that page regularly to see if its available - in case I do miss it, feel free to ping me here.
Thanks for helping us here, thats really appreciated.

Most probably, a build from 2023-08-31 or later will indicate that RC1 is available. I try to check that page regularly to see if its available - in case I do miss it, feel free to ping me here.

@boesing RC1 packages are available.

Huge. lets wait until the build has finished. I'll take care of the rebuild tomorrow or later this evening (CEST).
Thanks for pinging me ☺

LGTM. Thanks, @MauricioFauth!


Ensure platform_io.loop() runs at least once

Tested this out with V2 commands and saw no new issues, looks good to merge in!


phantomjs doesn't focus  elements even with tabindex

Which version of PhantomJS are you using? Tip: run phantomjs --version.
2.1.1
What steps will reproduce the problem?

Create an chronological list of tabindex element (I checked with inputs)
Make sure one of them is a  element
Send Keydown Tab event and check which is the document.activeElement
Watch as  is ignored

Which operating system are you using?
OS X Yosemite
Did you use binary PhantomJS or did you compile it from source?
binary
Please provide any additional information below.
I am using a dialog that contains few inputs and a label and tab through them.
Using chrome, it works perfectly, when switching to phantom it ignores the label element even though it has the next tabindex value.

Specifically I am using protractor over an Angularjs application.
I have reproduced the problem using only native phantomjs, so protractor isn't the cause.
Illustration:
<input tabindex="1"/>
<input tabindex="2"/>
<label tabindex="3">some text</label>
<input tabindex="4"/>

Sending 4 tab keydown events, focus will go: 1 -> 2 -> 4 -> 1

+1

+1


Snap.path.isPointInside() error

Run the following code in jsFiddle (i tried it in versions 0.1.0 and 0.2.0). isPointInside must return true, but it returns false. For rounded coordinates, it works good. Found this by coincidence.
var s = Snap(640,480);
var p = "M1.4315332974182866,4.405806462382467 L57.26133189673147,176.23225849529868 A185.30156250000002,185.30156250000002 0 0 1 -172.2890356108522,-68.21405480708441 L-4.307225890271305,-1.7053513701771101 A4.6325390625,4.6325390625 0 0 0 1.4315332974182866,4.405806462382467 Z";
var x = -58.296875, y=70.96875;
// It works ok for rounded coordinates though
//var x = -58.3, y=71;
s.g(
s.path(p).attr("fill","#A00000"),
s.circle(x,y,4).attr("fill","#000000")
).transform("t200,200");
alert("You can see the circle IS in path, but isPointInside returns : " + Snap.path.isPointInside(p, x,y).toString());

Updated fix for #248, same error here using closed paths transformed from shapefiles polygons, Snap.path.isPointInside() function is not working at all.
Please see jsfiddle in:
http://jsfiddle.net/ouuou1my/
Thanks.


Don't install Docker Compose

The docker role installs Docker and Docker Compose, because it was meant to be a general purpose role.
Now that's in this repository, we might avoid installing Docker Compose, because it takes a lot of time in the current implementation of the role (we blindly check if the binary we download is the same as the one we already have).
We don't need docker compose, so instead of spending time in refining how we install it, I propose we remove it entirely.
WDYT?
@StefanoSalsano @zvfvrv

strong agreement !


csfm.triangulate_bearings()

In 'reconstruction.py', there is a function called 'e, X = csfm.triangulate_bearings()'. The input of the function is undistorted feature point coordinates and rotation & translation matrix for each image. The output is 'e' and 'X', and then 'X' is added to reconstruction struct. I wonder what the 'X' presents. Is 'X' presents 3D feature points?

Yes, X is the triangulated 3D point

what coordinate is x represented in? And where is the origin (0,0,0) of the coordinate? It is the camera coordinate system of the first image?

@bryanibit X is represented in the world coordinate frame.


Fix some small typos in the Text docs.

Just some tiny spelling errors I noticed while reading :smile:

Cool, thank you!


fix: stop endless loading when dataset not longer exist

SUMMARY
This pr stops the endless loading in the dashboards when a dataset no longer exists and returns proper error info to the user.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
before
https://user-images.githubusercontent.com/17326228/131378812-5f92c50a-434c-48b3-857b-47b52c567976.mov
after
https://user-images.githubusercontent.com/17326228/131379074-cf9d01df-79c1-490e-81a2-9fd49dde63dc.mov
TESTING INSTRUCTIONS
Delete a dataset that has associated chart in a a dashboard.
Go to the dashboard and ensure that the charts do no endlessly load.
ADDITIONAL INFORMATION

[x ] Has associated issue: Fixes https://github.com/apache/superset/issues/16431
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up


Create unit tests

API has standardized - make unit tests for all simple and pure methods

PHPUnit and wp-cli have been integrated and work - 0.8.3 https://github.com/macder/wp-form-validation/pull/48
Creating units in progress


Development: Remove 'tracker' from websocket path

We do not really track something, so the path name is misleading (it was part of the generated Jhipster template)
Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Steps for Testing

Log in to Artemis
Check that web socket messages are sent normally (e.g. results for programming exercises)
Check the browser console network tab if the web socket messages are sent normally

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[x] Test 1
[x] Test 2

Thanks for the reviews so far. We need a couple more until we can merge


Pin the matching openmp variant in run_exports

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

The run_exports currently doesn't specify which openmp variant to pin, this results in the situation where a user may compile using the openmp variant, but then end up runing using the pthreads variant.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [42, 43]

@conda-forge-admin, please rerender


Add Bitbucket plugin

Sorry for the delayed response here.
I don't have an easy way to test that this works, but I'm inclined to merge it and get it out there for those that want it and let them report back any issues. The code looks like a standard porting of the GH plugin. It's unfortunate that adding these is such a copy-and-paste-like operation, but I don't think that fact should hold up additions like these.
WDYT @jferris @jsteiner ?

It is indeed strongly based on the Github plugin. I have to admit I did not look too closely at the other plugins. Would it make sense to designate one of the plugins (e.g. the Github one) as a "model plugin", making sure that it has extensive documentation (more than what would be necessary for just a standard plugin)? Also, would it make sense to move e.g. the API urls somewhere in the beginning of the file, so that they are all collected in the same place to make it easier to change them when creating a new plugin?

I think the GitHub plugin is a good model. I plan on spending some time trying to remove some of the copy-and-paste from the plugins soon. I'm trying to figure out a better way to handle the "extra" data that comes back; I'll open an issue for discussion related to that particular challenge.

@jferris would you consider that discussion and resolution blocking this PR? If not, is there anything you'd like to see done here before merging?

Nope, this looks good to me. Feel free to merge, or I'll do so on Friday.

@pafcu sorry for the delay on this. I merged this into master and will release to Hackage soon.


[RESOLVED] High ICMP ping response time

Problem started at 12:46:33 on 2023.08.04
Problem name: High ICMP ping response time
Host: S100-Santiago
Severity: Warning
Operational data: Value: 187ms
Original problem ID: 34598
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23518&eventid=34598

Problem has been resolved in 1m 0s at 12:47:33 on 2023.08.04
Problem name: High ICMP ping response time
Host: S100-Santiago
Severity: Warning
Original problem ID: 34598


chore: npm audit

Fixes several vulnerabilities, one of which is marked critical
Closes #43

Thank you @CrookedGrandma


Unable to Add multiple where queries in findUser

Hi,
In Finder.php, There is a function as
    public function findUser($condition)
        {
            return $this->userQuery->where($condition);
        }

Now If I initialize userQuery as:-
  $this->userQuery->where = ['status'=>1];

But when during user log-in process, above query is not working.

You should use this:
$user->findUser(['status'=>1]);


{"message": "Too Many Requests", "error": 429} on ramnode server

DB3 is not working in production ramnode server for some reason.
Investigate. In the mean time, run it in my local machine.

I'm sorry I put this on the wrong repo. I will close


feat(docs): Add requirements for usability and humanity

This PR adds the requirements in the usability and humanity section in the SRS.
Resolves #65

This should be ready for review. The only thing unclear in this section at the moment is the accessibility requirements. Put as TBD. They may not be a requirements as it maybe a mandated constraint (see city accessibility standards).


Add goreportcard and coverage

WHAT
Add badges
WHY
To show the project status
Related issue (if exists)

Codecov Report

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

@@           Coverage Diff           @@
##             main      #26   +/-   ##
=======================================
  Coverage        ?   94.75%
=======================================
  Files           ?       11
  Lines           ?      362
  Branches        ?        0
=======================================
  Hits            ?      343
  Misses          ?       13
  Partials        ?        6

Continue to review full report at Codecov.

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


Update SignalR client to Target .Net Standard 2.1

We are currently cross targeting to netcoreapp3.0 for IAsyncEnmerable support. It's included in .Net Standard https://github.com/dotnet/standard/pull/1017 we should move to cross target that instead
https://github.com/aspnet/AspNetCore/blob/507a765dfb078f446c445318e7b55ad9f7f5cbe0/src/SignalR/clients/csharp/Client.Core/src/Microsoft.AspNetCore.SignalR.Client.Core.csproj#L5

This bit of code will cause some problems (and may already be a problem with our current cross-targeting):
https://github.com/aspnet/AspNetCore/blob/efa9a4e530b2e9ebafe672a78b5ecae2e346d19f/src/SignalR/clients/csharp/Http.Connections.Client/src/HttpConnection.cs#L587-L605
The first problem is that right now it means that if you are running the SignalR 3.0 Client on .NET Core 2.1 (a supported scenario since we target .NET Standard 2.0) then we will no longer use WebSockets on Windows 7, despite there being a managed implementation.
The second problem is that if we cross target netstandard2.1 instead of netcoreapp, we lose the ability to do this at all (via #if). We may need to do runtime detection here instead. There's no clean API for that though: https://github.com/dotnet/corefx/issues/17452

Moving to preview7

Acceptance checklist (check one item)

[ ] We decided not to take this fix.
[ ] The fix is tests-only.
[x] The fix contains product changes (check all items below).

[ ] Relevant XML documentation comments for new public APIs are present.
[ ] Narrative docs (docs.microsoft.com) are updated. (check one item below)

[ ] The change requires a new article. An issue with an outline has been filed here: [ISSUE LINK]
[ ] The change requires a change to an existing article. A docs PR with these changes is linked here: [PR LINK]
[x] The change requires no docs changes.

[x] Verification has been completed. (check one item below)

[ ] The change is in the shared framework and was verified against the following versions

SDK installer: [VERSION]
ASP.NET Core Runtime: [VERSION]
.NET Core Runtime: [VERSION]

[x] The change is in an OOB NuGet/NPM/JAR package and was verified against the following version of that package: [Microsoft.AspNetCore.SignalR.Client.Core] [3.0.0-preview7.19326.10]


react_refresh: Don't visit arrow function nodes

Since atoms created in a function context are new atoms, there's nothing in the arrow function sub-tree that we should transform. The default behavior seems to be to visit everything, whereas an empty impl stops the walk.
Another driveby fix: store previous top_level in visit_mut_stmts instead of always resetting it to true.  I don't have a failing test for this (so it might be fine), but it's a pattern that's explicitly called out in the docs 0.
Fixes #36

As it turns out, this also fixes #34


"open anchor app" button is not working

Hi
Following issue https://github.com/greymass/anchor/issues/949
In my case there is no
appimagekit...anchor....desktop
file in ~/.local/share/applications directory and "open anchor app" button is not work
I'm using
linux-anchor-wallet-1.2.2-x86_64.AppImage
Is there any other way to connect site like https://arm.chintai.io/portal to anchor ?

If possible, the deb installer (instead of the AppImage) will setup everything properly. I'm not sure which linux distribution you're using but the AppImage itself is the only one with this problem currently.

Also for reference: https://github.com/greymass/anchor/issues/833
We are tracking this in the above issue.


Unpin matplotlib

The matplotlib package has been pinned to <v3.3.0 to temporarily avoid test failures within iris due to the latest release v3.3.0.
See https://github.com/SciTools/iris/pull/3758.

Should hopefully be addressed by the unpin proj task - see comment on #3154.

The read the docs yml conf file also will need to be unpinned.

Closed by #3811


Problems with Overleaf and "DnD"-commands

While using overleaf the "dnd"-commands doesn't work. This happens with "DndArea", DnDTable" and so on.

This is the result.

This is the overleaf error log. The error is the same for every command.

I think this is probably something i missed following the guide, but i really can't get to it.

Just wanted to let you know that I have seen this. There are parts of LaTeX3 that are still changing, and we have had to replace missing commands for Overleaf before. Overleaf tends to lag behind a bit on keeping up to date because upgrading all their servers takes time, and CTAN packages and TeXLive are updated too frequently for Overleaf to keep everything up to date on a daily basis (plus that would probably frustrate users).
I will try to get some time to take a look at this.

See #197

I imagine Overleaf has the LaTeX3 commands now.


force column size parsing to lower case in Shared Model

Do not merge until we have a decision on #584

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


ClickHouseStatement not load file into table ( file name too long)

version driver clickhouse-jdbc:0.2
I have csv file with columns which have cyrillic (7 columns  which each one have near 40 cyrillic symbols).
Name table is cyillic too.
Request:
                try (InputStream inputStream = Files.newInputStream(file);
                     ClickHouseStatement statement = clickHouseConnection.createStatement()) {
                    statement.write()
                            .table(tableName))
                            .option("format_csv_delimiter", ";")
                            .data(inputStream, ClickHouseFormat.CSV)
                            .send();
                }

Response:

ru.yandex.clickhouse.except.ClickHouseException: ClickHouse exception, code: 76, host: localhost, port: 3307; Code: 76, e.displayText() = DB::ErrnoException: Cannot open file /var/lib/clickhouse/data/goSNynThCyuHpAZGJwCC/%D0%92%D1%8B%D0%B3%D1%80%D1%83%D0%B7%D0%BA%D0%B0%20%D0%B4%D0%BB%D1%8F%20%D0%B4%D0%B0%D1%88%D0%B1%D0%BE%D1%80%D0%B4%D0%B8%D0%BD%D0%B3%D0%B0%2Etxt%281%29/tmp_insert_all_1_1_0/%D0%92%D1%8B%D0%B3%D1%80%D1%83%D0%B7%D0%BA%D0%B0%20%D0%B4%D0%BB%D1%8F%20%D0%B4%D0%B0%D1%88%D0%B1%D0%BE%D1%80%D0%B4%D0%B8%D0%BD%D0%B3%D0%B0%2Etxt%2E%D0%A0%D0%B5%D0%B3%D0%B8%D0%BE%D0%BD%D0%B0%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%84%D0%B8%D0%BB%D0%B8%D0%B0%D0%BB.bin, errno: 36, strerror: File name too long (version <IP_ADDRESS> (official build))

Linux has a maximum filename length of 255 characters for most filesystems (including EXT4), and a maximum path of 4096 characters
Not JDBC issue. CH does not support so long column names.


Frequent "hangs" when typing, and 100% CPU on the electron web-rendering thread.

When I enable the checklist plugin I get "hangs" when typing, and 100+% CPU on the electron web-rendering thread. Basically after about a sentence's worth of typing, the editor hangs, and buffers keystrokes, which show up a second or two later. De-activating the checklist plugin resolves the issue. Also, while indexing about 1500 items a vault, if the plugin is enabled, it takes 40ish minutes. With Checklist deactivated, the indexing takes 5 seconds. I'm not sure how to troubleshoot this further.

Actually, a bit of info. I had removed the todo tag to scan all files in the vault. Adding back a tag speeds things up a bit. So there may be something about how the code is scanning the vault for all the '- [ ] ' strings that is causing the slowdown.

Duplicate of #70


in_syslog: add 'emit_unmatched_lines' option

Fixes #2497
Signed-off-by: Brian Candler<EMAIL_ADDRESS>What this PR does / why we need it:
Many devices emit syslog messages which don't match expected format, and are otherwise thrown away.  Add emit_unmatched_lines as per the equivalent in_tail option.
Docs Changes:
Add new parameter to https://github.com/fluent/fluentd-docs-gitbook/blob/1.0/plugins/input/syslog.md
Release Note:
### Enhancement

* in_syslog: Add `emit_unmatched_lines` to capture lines which don't parse

Thanks!


deploy cluster fail when I customize the calico config in Clusterfile

Sealos Version
v4.2.1
How to reproduce the bug?

5 nodes(3 masters + 2 nodes) with clean OS
generate Clusterfile command:
sealos gen labring/kubernetes:v1.23.17 labring/helm:v3.11.0 labring/calico:v3.24.1 --masters xxx,xxx,xxx --nodes yyy,yyy -p xxx > Clusterfile
append calico configs to Clusterfile

---
apiVersion: apps.sealos.io/v1beta1
kind: Config
metadata:
  name: calico
spec:
  path: charts/calico/values.yaml
  strategy: merge
  data: |
    installation:
      enabled: true
      kubernetesProvider: ""
      calicoNetwork:
        bgp: Disabled
        ipPools:
        - blockSize: 22
          cidr: <IP_ADDRESS>/10
          encapsulation: VXLAN
        nodeAddressAutodetectionV4:
          interface: "bond.*|eth.*|en.*|em.*"
---

run it
sealos apply -f Clusterfile

What is the expected behavior?
No response
What do you see instead?
The instalation will be OK if I do not append the calico config to Clusterfile, but, when I do it, the calico will fail:
log:
<IP_ADDRESS>:22  [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
<IP_ADDRESS>:22  [kubelet-start] Starting the kubelet
<IP_ADDRESS>:22  [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
<IP_ADDRESS>:22  [preflight] Reading configuration from the cluster...
<IP_ADDRESS>:22  [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
<IP_ADDRESS>:22  W0615 02:32:34.488435   10077 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: <IP_ADDRESS>; the provided value is: <IP_ADDRESS>
<IP_ADDRESS>:22  W0615 02:32:34.499627   10077 utils.go:69] The recommended value for "resolvConf" in "KubeletConfiguration" is: /run/systemd/resolve/resolv.conf; the provided value is: /run/systemd/resolve/resolv.conf
<IP_ADDRESS>:22  [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
<IP_ADDRESS>:22  [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
<IP_ADDRESS>:22  [kubelet-start] Starting the kubelet
<IP_ADDRESS>:22  [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
<IP_ADDRESS>:22
<IP_ADDRESS>:22  This node has joined the cluster:
<IP_ADDRESS>:22  * Certificate signing request was sent to apiserver and a response was received.
<IP_ADDRESS>:22  * The Kubelet was informed of the new secure connection details.
<IP_ADDRESS>:22
<IP_ADDRESS>:22  Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
<IP_ADDRESS>:22
2023-06-15T02:32:38 info succeeded in joining <IP_ADDRESS>:22 as worker
<IP_ADDRESS>:22
<IP_ADDRESS>:22  This node has joined the cluster:
<IP_ADDRESS>:22  * Certificate signing request was sent to apiserver and a response was received.
<IP_ADDRESS>:22  * The Kubelet was informed of the new secure connection details.
<IP_ADDRESS>:22
<IP_ADDRESS>:22  Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
<IP_ADDRESS>:22
2023-06-15T02:32:40 info succeeded in joining <IP_ADDRESS>:22 as worker
2023-06-15T02:32:42 info start to sync lvscare static pod to node: <IP_ADDRESS>:22 master: [<IP_ADDRESS>:6443 <IP_ADDRESS>:6443 <IP_ADDRESS>:6443]
2023-06-15T02:32:42 info start to sync lvscare static pod to node: <IP_ADDRESS>:22 master: [<IP_ADDRESS>:6443 <IP_ADDRESS>:6443 <IP_ADDRESS>:6443]
<IP_ADDRESS>:22  2023-06-15T02:32:42 info generator lvscare static pod is success
<IP_ADDRESS>:22  2023-06-15T02:32:42 info generator lvscare static pod is success
2023-06-15T02:32:42 info Executing pipeline RunGuest in CreateProcessor.
Release "calico" does not exist. Installing it now.
Error: template: tigera-operator/templates/tigera-operator/02-tigera-operator.yaml:62:30: executing "tigera-operator/templates/tigera-operator/02-tigera-operator.yaml" at <.Values.tigeraOperator.version>: nil pointer evaluating interface {}.version
2023-06-15T02:32:46 error Applied to cluster error: exit status 1
Error: exit status 1
PS:
All things are OK when I use sealos v4.2.0( even if I append the same calico config to the Clusterfile).
Operating environment
- Sealos version: v4.2.1
- kubernetes version: labring/kubernetes:v1.23.17 OR labring/kubernetes-docker:v1.23.16, both fail
- Operating system: ubuntu20.04
- Runtime environment: virtual machine (openstack 8c8g40g)
- Cluster size: 3masters, 2nodes

Additional information
No response

This issue has been fixed in release V4.2.2