Keep seeing Error Domain=com.google.GIDSignIn Code=-1 "

I followed all the steps for iOS instruction, however, I got these errors. I tried to go through all steps again but no luck. Any leads about this error?
2015-12-07 19:29:13.432 BeaconServiceDemoApp[742:501] <GMR/INFO> App measurement v.1201000 started
2015-12-07 19:29:13.570 BeaconServiceDemoApp[742:138981] Error Domain=com.google.GIDSignIn Code=-4 "The operation couldn’t be completed. (com.google.GIDSignIn error -4.)"
2015-12-07 19:29:28.786 BeaconServiceDemoApp[742:138981] Error Domain=com.google.GIDSignIn Code=-1 "A potentially recoverable error occured. You may try again." UserInfo=0x1777fdc0 {NSLocalizedDescription=A potentially recoverable error occured. You may try again.}
2015-12-07 19:29:38.538 BeaconServiceDemoApp[742:138981] Error Domain=com.google.GIDSignIn Code=-1 "A potentially recoverable error occured. You may try again." UserInfo=0x17781cf0 {NSLocalizedDescription=A potentially recoverable error occured. You may try again.}

Have you gotten past this yet?
This is almost always because the credentials aren't set up correctly/


Make rails dependency an optional

Idea:

[ ] Exception_notifier somehow could be configured to use appropriate mailer. As far as i see, there is no generalized way to provide secitions views to a generic mailer, but i don't sure exception_notifier not locked to ActionMailer descendants, so there probably could be a way to configure all ActionMailers to respec our views. If not, views should be moved to appropriate generators of frameworks
[ ] Load rails-related code via special file lamian/rails.rb, so they could be easily loaded, but only if rails requested
[ ] Probably add hanami/rb / sinatra.rb files for thoose frameworks

@fiscal-cliff offered some help, would you do all this work for me?

@fiscal-cliff, I can do #8 to simplify this task for you

I managed to sort out this issue
First of all, the notifier itself has rails as a dependency. The only way to evade this requirement is to use simple_email_exception_notifier which we use already. The notifier provides plain text formatter which is not compatible with :email notifier. So rendering request_log section inside the notifier turned out to be way harder than I expected. I've patched the notifier as follows
module SimpleNotifierPatch
  def compose_message(exception, env, options)
    SimpleEmailExceptionNotifier::Message.compose do |m|
      m.print_summary(exception)
      m.print_section('Backtrace', exception.backtrace)

      m.print_section('Request log', Lamian.logger.dump.split("\n")) # <<< !!!

      unless env.empty?
        m.print_request(Rack::Request.new(env)) if defined?(Rack::Request)
        m.print_section('Environment', filter_env(env))
      end

      m.print_section('Data', extract_data(env, options))
    end
  end
end

ExceptionNotifier::SimpleEmailNotifier.singleton_class.prepend(SimpleNotifierPatch)

I would advice you to look up alternatives for ExceptionNotifier since this solution looks extremely dirty.

@fiscal-cliff

I would advice you to look up alternatives for ExceptionNotifier since this solution looks extremely dirty.
ExceptionNotifier-related stuff could be moved to rails-only section in this case, same as it's views and rails engine.
Also, consider use Lamian.dump instead of Lamian.logger.dump, because Lamian.logger is part of private api and this comands do same stuff

OK, that's just kinda demo, proof of concept
On Mon, Jan 16, 2017, 00:14 Alexandr Smirnov<EMAIL_ADDRESS>wrote:

@fiscal-cliff https://github.com/fiscal-cliff
I would advice you to look up alternatives for ExceptionNotifier since
this solution looks extremely dirty.
ExceptionNotifier-related stuff could be moved to rails-only section in
this case, same as it's views and rails engine.
Also, consider use Lamian.dump instead of Lamian.logger.dump, because
Lamian.logger is part of private api and this comands do same stuff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JelF/lamian/issues/9#issuecomment-272724249, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFRVLlYXwIhpDzx5KrPqH-GtOly38Mzpks5rSowzgaJpZM4LY0Gt
.

I will not add non-rails support untill i need it in production. However, pull requests are welcome
Core functionality is rails-independent, same is middleware itself. Rails engine should be required in "lamian/rails" and readme should be updated. Exception notifier API is not required in non-rails for oblivious reasons (exception_notifier bound to rails), so i suggest to add API for raven


Prevent `ModuleNotFoundError: No module named 'ray.rllib.agents.callb…

See https://github.com/AIcrowd/neurips2020-procgen-starter-kit/issues/11

thanks for this!

Works for me, too. Thanks!

@laxatives thanks for updating it. We changed the version in requirements.txt but missed in README.md


NexusKitten/moremotion: use exported renderer.Rectangle

(this will wait until after packager update for placeholder & desktop app)


Groq's "name" option within "messages" parameter of the chat endpoint payload

Groq has a really helpful option within the "messages" parameter that one would provide in the payload to their chat completion API that helps the model distinguish between multiple users of the same role.  This is helpful for situations in which a multi-agent conversation is taking place and there is more than one agent in a given role--for example, a roleplay in which we want to differentiate between an assistant representing one personality with it own system prompt talking to another assistant representing another agent with its own system prompt, all chatting with the user role.
For more on this, please see the following link to the Groq docs https://console.groq.com/docs/text-chat under the "messages" parameter.

@pmgh2345, would you know what that actually does? If you asked the question "What is my name" would Groq respond with what was in that field?

@marklysze I believe that is the intention provided that the last message of the payload makes use of this parameter with the "user" role, however, I don't have Groq to confirm whether or not the model will actually discern a conventional "name" as such, or whether it simply uses the different names to discern one point of view vis a vis another in those situations where this is relevant.

Thanks @pmgh2345, sounds interesting...


feat: connect to postgres instance

Via @paulushcgcj:
 @marcionemec-daitan to keep working on making the code connect to postgres and oracle and execute a simple select

Updating escope: First try to connect to Postgres instance and execute a simple select.


FI-1866: Document runnable properties

Summary
This branch adds documentation to various runnable properties which weren't yet documented.
Testing Guidance
bundle exec jekyll s in docs, then go to localhost:4000/inferno-core.

Codecov Report
Base: 73.72% // Head: 94.21% // Increases project coverage by +20.49% :tada:

Coverage data is based on head (5c22ae8) compared to base (fe74113).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #310       +/-   ##
===========================================
+ Coverage   73.72%   94.21%   +20.49%
===========================================
  Files         191      115       -76
  Lines        9305     3078     -6227
  Branches      771      357      -414
===========================================
- Hits         6860     2900     -3960
+ Misses       2037      178     -1859
+ Partials      408        0      -408

Flag
Coverage Δ

backend
94.21% <ø> (ø)

frontend
?

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

Impacted Files
Coverage Δ

lib/inferno/dsl/input_output_handling.rb
92.40% <ø> (ø)

client/src/components/LandingPage/LandingPage.tsx

...mponents/TestSuite/TestRunButton/TestRunButton.tsx

...ite/TestSuiteDetails/TestListItem/RequestsList.tsx

client/src/store/testSession.ts

client/src/hooks/useTimeout.ts

...mponents/RequestDetailModal/RequestDetailModal.tsx

...c/components/SuiteOptionsPage/SuiteOptionsPage.tsx

...components/TestSuite/TestRunProgressBar/styles.tsx

client/src/api/TestRunsApi.ts

... and 67 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


feat(ssi): add expiry handling for ssi

Description

add cleanup process for expired ssi credentials older than x month
add automatic decline process for pending ssi credentials
post generated expiry date to miw
adjust detail versions table for certificates
add seeding for certificate versions

Why
to add the expiry handling for credential ssi's
Issue
Refs: N/A - Jira Issue: CPLP-3398
Corresponding CD PR
#140
Checklist

[x] I have followed the contributing guidelines
[x] I have performed IP checks for added or updated 3rd party libraries
[x] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[x] I have added tests that prove my changes work
[x] I have checked that new and existing tests pass locally with my changes
[x] I have commented my code, particularly in hard-to-understand areas

Looks good in general! Could you please provide the feedback to Gitguardian that the 4 discovered secrets are false positives? And one comment: For the overall consistency it might be better to call the project Credential.App (like it's called in most places) instead of VerifiedCredential.App.

done :)

This PR will be closed since the implementation will happen in the sis-credential-issuer repository

Closing this PR. The changes are included in the new ssi-credential-issuer repo


Programmatically running a task in VS Code Web ignores dependsOn tasks

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

VS Code Version: VS Code Web v1.69.2
OS Version: MacOS

Steps to Reproduce:

Create a custom task provider in an extension (process and shell tasks are unsupported in VS Code Web)
Create a tasks.json file with multiple tasks where one dependsOn the other
Contribute a command which executes the task with the dependency using vscode.tasks.executeTask(...)
Open the extension in VS Code Web and execute the command

Expectation: the dependent task is executed
Outcome: it isn't
Test details...
Executing Run Task... in command pallet to start the task with dependency

VS Code Desktop: Works
vscode-test-web: Works
vscode.dev: Works

Executing task with dependency using custom command with  vscode.tasks.executeTask(...)

VS Code Desktop: Works
vscode-test-web: Does not work (dependent task not executed)
vscode.dev: Does not work (dependent task not executed)

Extension reproducing this issue can be found here:
https://github.com/thegecko/web-extension-tasks

Tasks are currently not supported in the web, so this is expected

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!

Tasks are currently not supported in the web, so this is expected

Tasks run in the web version fine, the feedback is that explicitly shell and process type tasks won't work.
If tasks are not intended to run in the web, then this expectation should be set accordingly by removing the related commands and showing feedback to the user to this affect. Currently the only feedback pertains to none-custom runners.

This might be fixed in insider's tomorrow - there were some changes to the handling of dependent tasks

This might be fixed in insider's tomorrow - there were some changes to the handling of dependent tasks

Thanks @meganrogge
I've re-tested this in vscode.dev insiders (Version: 1.79.0-insider) and unfortunately still see the issue.
In vscode.dev, if you have a task which dependsOn another task, both will be executed if the leaf task is executed with the Tasks: Run Task command, but only one executes if the same task is invoked programmatically using vscode.tasks.executeTask(...).

This bug is also apparent when execution debugging programatically. e.g. any preLaunchTask seems to be ignored


[FEAT] Support sqlalchemy for storing session

Accept another option than Redis for storing session with Flask-Session

Hello. Added to backlog

awesome, I can provide the PR


Handle  memories

If a module needs a memory, it just needs to add a port of type memory to connect to an external memory.
If a submodule's memory ports are left unconnected, they should be brought to the module's interface. Note that all modules except the memory wrapper will do this.

Also produce memory table in docs in the description section, new subsection Memories


weka: 3.6.12 -> 3.8.0

This is my first pull request to NixOS so I hope that I have done it well.
Motivation for this change
Update weka to the last stable version.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Other than my note, this looks superficially okay to me.

Thanks @joachifm for the advise. I think is ready now.

@joachifm, I've noticed that this package hasn't a maintainer. Could be I one? I'm very new to NixOS but I think one newbie is better than no one.

@mimadrid that'd be great. All that is required to be a maintainer is caring about the package.

Pushed to master. Thank you.


build(swagger): Fix argo-server swagger so version does not change.

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I have written unit and/or e2e tests for my change. PRs without these are unlike to be merged.
[x] Optional. I've added My organization is added to the README.
[ ] I've signed the CLA and required builds are green.

This can be merged as soon as green and approved.


Path to FVPs has changed in Keil MDK 5.40

The path to the FVP executables has changed in MDK 5.40, which means that the debug settings in the example projects needs to be updated.
Suggest also adding something similar to the below in the readme(s).
Depending on the version of MDK you have installed, the path to FVP executables may need to be updated.

* MDK versions before 5.37:    `Keil_v5/ARM/FVP`
* MDK versions 5.38, 5.39:     `Keil_v5/ARM/VHT`
* MDK version 5.40 or later:   `Keil_v5/ARM/avh-fvp/bin/models`

I have made fixes into branch https://github.com/ARM-software/CMSIS-DSP/tree/examples
Can you check if it is solving your issues ?

Adding the REMarks in the run batch files probably suffices.


Setup github actions

See: https://docs.github.com/en/actions
Make sure to trigger the CI on push (to master) and on PRs.
As there is no code yet it can run a simple echo "hello world" and exit. The goal here is to prepare the infrastructure to run actual tests at a later stage.

@MaciejFranikowski
From now on, please make sure to create PRs before pushing new code to the master branch.
You can push to a different branch here and create a PR from it, or if you prefer you can create a fork and create a PR from your forks.
BTW. the ci configs you pushed to the repository seem to be some samples copied from the internet. This is ok as long as the licence is compatible with the licence used in this project. Is it? In addition you should have mentioned the source of the configuration in your commit.
Things like this (and other things you missed) can be discussed in PRs, that's why it's crucial you use them.

@tgorochowik
You can be sure that we'll now properly use pushes/PRs.
Regarding CI - this and #3 - we've added two workflows, one as a hello-world-workflow, that starts only on PR/push to master and one linting workflow that starts on push to every branch (source - MIT license).
Is this correct approach? I mean, should we restrict linting only to master and development branch or leave it as it its?

@blazejulanowicz you can indeed mix MIT license with Apache (which we use here), but you have to keep the original license and copyright notice for the imported files.
This is important, please don't ignore licenses in the future. This is especially important when you start working on the code.
I have removed your commits from master and pushed them to a branch here: https://github.com/antmicro-labs/raw-image-data-previewer/tree/ci-copy
It is okay to create a PR based on that (retaining the license information).
But this is really simple stuff, it would be much better if you just wrote this yourself based on the documentation and just push that with the proper license from the start.

@tgorochowik
Thanks for help. From now on we will be more strict when it comes to licenses.
I am going to remove both workflows and create them again - without using any templates.


Vite 3.0.0

Hi, I'm just wondering about<EMAIL_ADDRESS>support, after upgrade I cannot use this plugin anymore:

@matrunchyk we're working on it... just released today, do you have a repo where we can test?

Great news. Unfortunately, I don't have a public repo...
Thank you for your hard work! <3

@matrunchyk the error when installing deps or running dev? can you put here the raw log?

When installing, will attach the log in a few moments

I very apologise @userquin, now it installs correctly with no issues, vite starts successfully. I will check how it works after deploy.
Thanks again!

@matrunchyk I've read the logs and it seemed like a dependency installation problem...

Yeah I think it was because of another package which still not on vite@3 (like vite-plugin-eslint and vite-plugin-html-config)


Non numpy vectorization doc

Being paranoidly explicit about appropriate format of the out object expected from the _evaluate method, per discussion in #372
You may want to do the merge with fastforward/squash, which apparently I can't request on my side.
Thanks again!

Thanks for putting the effort into improving the documentation. I used squash before merging indeed.
The paragraph will be available once I release a new version.

You are most welcome, that was a tiny contribution back to into an excellent project which is giving a good help for my research!


Test failure with more recent github.com/stretchr/testify

The currently vendored version of github.com/stretchr/testify in the rclone repository is at commit https://github.com/stretchr/testify/commit/4d4bfba8f1d1027c4fdbe371823030df51419987 (2017-01-30).
In the meantime, github.com/stretchr/testify has gained commit https://github.com/stretchr/testify/commit/46b3c8225b20f01377eeefe3e6b7b147bb742eff, which breaks your tests:
% go test github.com/ncw/rclone/fs
--- FAIL: TestSetDefaults (0.00s)
	Error Trace:	http_test.go:27
	Error:      	Invalid operation: (func(string, string) (net.Conn, error))(nil) == (func(string, string) (net.Conn, error))(nil) (cannot take func type as argument)
	Messages:   	when checking .Dial
	Error Trace:	http_test.go:28
	Error:      	Invalid operation: (func(string, string) (net.Conn, error))(nil) == (func(string, string) (net.Conn, error))(nil) (cannot take func type as argument)
	Messages:   	when checking .DialTLS

Please fix the test.
Also, in the future, please regularly update the vendored versions of your dependencies (using e.g. dep ensure -update) :)
I noticed this when investigating why the Debian packaging for rclone fails to build (Debian’s github.com/stretchr/testify is more recent than your vendored version, and Debian un-vendors everything).

I re-vendor everything at the start of the release cycle for rclone.  SInce I just released 1.37 that will be shortly!

I noticed this when investigating why the Debian packaging for rclone fails to build (Debian’s github.com/stretchr/testify is more recent than your vendored version, and Debian un-vendors everything).

That policy is bound to cause problems with projects like rclone with lots of dependencies.  I didn't used to use vendoring with rclone and people were always complaining that the rclone build was broken.

I've fixed this now - see above for the commit.

Yep, already uploaded to Debian. Thanks!


Secondary compute nodes (replicas): Add debug instrumentation to catch unsafe buffer lock coupling/crabbing

I recently spoke to @arssher about general issues with supporting secondary compute nodes. Although we don't yet have support for secondary compute nodes, it's certainly on the roadmap. It seems worth noting down some of the ideas that followed from this in-person conversation, in case we forget about them.
Background
My current understanding is that secondary compute nodes will work by having access method code like heapam and nbtree behave as if the system is running in recovery, with hot standby enabled. The secondary compute node (replica) almost always behaves as if there was a local startup process processing WAL records in the usual way. Despite all this, recovery is actually incremental and on-demand, with REDO that takes place on remote page server nodes.
Designs that do this kind of thing are sometimes called "instant recovery", since the perceptible recovery time should be approximately zero seconds (with certain caveats about tail latency from on-demand REDO).
We don't make any strong guarantees about the recency of the point that the secondary node "has recovered up to", except these two:

The LSN that the secondary node considers itself "recovered to" cannot visibly go backwards, since clearly that won't work at all.

Even when the system experiences a hard crash, the log can still only roll forward. (Actually this is really just a special case of 1.)

That might not be enough to avoid what I'll call "physical consistency hazards" on the secondary.
Physical consistency hazards
Our planned approach to simulating hot standby on secondary nodes is not 100% equivalent to Postgres hot standby. In general Zenith compute nodes don't really run REDO routines directly, since that's decoupled -- there is no real startup process that acquires buffer locks, even though in some sense we "pretend" that there is. We therefore need to consider the possibility of bugs involving access method code with:

A REDO routine that couples locks (i.e. holds more than one buffer lock at once) to achieve some kind of exclusionary effect during hot standby. For example, nbtree's btree_xlog_unlink_page() and btree_xlog_split() routines.
Access method code that can run during hot standby, that must itself acquire multiple buffer locks at the same time.

(I would expect to either see both kinds of code together within an access method, or neither.)
This class of bug can be thought of as a failure of the Zenith secondary to simulate some kind of exclusionary effect that the Postgres access method code expects will be enforced to achieve correct behavior. You could also say that such a bug is a failure of Zenith's secondary node to make atomic actions (WAL records) appear as atomic when they happen to affect multiple pages together (multiple-page atomic action WAL records are rare -- but not that rare).
nbtree bugfix commits
When we talk about this problem we tend to talk about things like B-Tree lock coupling/crabbing, which is a classic example of a locking protocol of the kind we're concerned about here. However, this issue is technically broader than any one access method.
Note that nbtree (standard B-Tree access method) doesn't actually use classic lock coupling on its descent of the tree -- it is clever about avoiding lock coupling to increase concurrency. It does still use coupling, including in rare cases across same-level sibling pages. That was enough to cause problems for a proposed amcheck enhancement from Andrey Borodin. That can be treated as a point of reference for understanding the general problem here.
The relevant bug fix Postgres commits are:
postgres/postgres@0a7d771f0f63eb120e7f0a60aecd543ab25ba197
postgres/postgres@9a9db08ae46209edcc5ecb120328a2bf92fd6069
Overall impact
Fortunately, lock coupling in access method code during a read-only query running during hot standby is rare in practice, for reasons that are pretty fundamental to its design -- most of the work is already done. That is, we should already be okay with any code that acquires no more than a single buffer lock at a time, which is very much the common case already. Zenith's basic guarantees are already enough.
It is likely that the aforementioned bug fixes to nbtree REDO routines would never have been needed had it not been for Andrey Borodin's patch. The issue would have remained theoretical if the patch happened to never have been proposed.
Possibly problematic code that I know about already:

Open question: Do we need to be careful with nbtree backwards scans? They only acquire one buffer lock at a time, and so we only have coupling on the write side. Not yet 100% sure that that means we're fine. But I am sure that this is the only problematic case in nbtree.
amcheck code -- Andrey Borodin's patch is worth having in Zenith's amcheck.
GIN, which uses old school lock coupling when descending certain B-Tree structures.

Rather than trying to think of everything, we can detect possibly-problematic cases using instrumentation.
Instrumentation
Both of the relevant code categories (the read side and the redo side) can be detected in a simple and generic way by adding custom instrumentation to bufmgr.c. We can keep track of the count of current held buffer locks by incrementing and decrementing in LockBuffer() and related code. It seems reasonable to assume that any instances of more than one buffer lock being held during hot standby must have something to do with some locking protocol that expects an exclusionary effect. It just wouldn't be sensible to do it for any other reason.
Remediation
We probably need to invent some kind of barrier or fence primitive to force the expected behavior when and where that is deemed truly necessary. This is expected to add a lot of latency in affected code paths. This should be okay because in practice it should be very rare.
Postgres developers already avoid lock coupling in general. And when it is necessary, it is usually only necessary for writers that need to block out other writers. This is what the lock coupling needed when ascending an nbtree index during a page split to insert new downlink is all about. This is why we don't coupling buffer locks across levels inside nbtree REDO routines, and never have -- only original execution needs that particular lock coupling to take place. I'm also pretty sure that it's rare to non-existent in heapam, though I should think about it when the time comes.

One more thing to consider: Do cleanup/super-exclusive buffer locks (needed for pruning by both VACUUM and opportunistic heap cleanup) need to be considered here?
In a certain sense, we need to think about 4 distinct kinds of buffer lock here -- not just 2. These are:

Buffer pin, no buffer lock (actually kind of a lock)
Buffer pin, shared lock
Buffer pin, exclusive lock
Buffer pin, super-exclusive/cleanup lock

@arssher suspects that this is already okay. I tend to think that he is right about that, but want to leave some breadcrumbs about super-exclusive locks. Just to be on the safe side.

Thanks for sharing. I edited commit references to utilize GitHub auto linking, so they were clickable

Thanks for sharing. I edited commit references to utilize GitHub auto linking, so they were clickable. Hope it's fine

Thanks!


netbox: deduplicate drf-nested-routers django4 patches

they are already applied globally in our drf-nested-routers package
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.11 Release Notes (or backporting 23.05 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.

Would you prefer I just leave the let-in with let py = python3; in ... ?

Would you prefer I just leave the let-in with let py = python3; in ... ?

I am completely fine with the change, just in another commit to make the git log / blame clearer


Fix Mendes Benchmark

Fixes the Mendes benchmark and updates ModelingToolkit to allow the use of save_positions kwarg.
A couple of notes:

I explicitly added ModelingToolkit as a dependency to get the correct version. Not sure if that will be an issue in the future or if there was a better way to force that.
I couldn't get the symbol based indexing to work for the Mendes problem, as it appears that the problem from the problem library doesn't use them. I didn't spend too much time looking into it though.

This looks good, I think we need to think about a few of the symbolic indexing issues a bit more. It should just work if you do:
@variables t x(t)
sol[x]

but 🤷 we need some way to better reference the names of the reactions and lower them nicely.

Maybe the variables should be a property of something, like either the System or the Problem? In this case in particular, since we're getting the problem from the problem library, you shouldn't be able to declare an arbitrary variable like @variables t foo(t) and expect sol[foo] to work.
In this case, it appears that the sol doesn't have any indexing symbols, as sol.prob.f.syms is empty. It's kind of strange, because plot(sol) has a legend with u1(t), u2(t), ..., but doing @variables t u1(t) then sol[u1] didn't work for me.


[Bug] App crashed

After that I looked at /var/log/syslog:
kernel: [75058.875322] traps: chat-gpt-next-w[148248] trap int3 ip:7fa730e42167 sp:7fff8f5de9f0 error:0 in libglib-2.0.so.0[7fa730dfe000+8f000]
Errors started with Appimage v2.9.11and continue to appear in v2.9.12, preventing the application launching. In this case, version v2.9.10 started ok.
That's what I did:
sudo apt install --reinstall libglib2.0-0
sudo apt install --reinstall libglib2.0-dev
It didn't help.
Ubuntu Studio 22.04.3 KDE

I don't have an Ubuntu environment to reproduce this error. Please try installing the deb version. If the issue persists, please prioritize using the PWA web version. I don't want to spend more time fixing compatibility issues like this. Thank you for your understanding.


RDS Cluster Support

From spring-cloud-aws created by davidsloan-productlab: spring-cloud/spring-cloud-aws#356
Instead of an RDS instance I'm trying to use an RDS Aurora cluster.
I can use an instance within the cluster using
@EnableRdsInstance
However when trying to use the cluster itself I see an exception with this as the cause:
No database instance with id:'my-cluster-name' found. Please specify a valid db instance
Looking into the code, I can see that in AmazonRdsDataSourceFactoryBean, only instances are queried using AmazonRDS.describeDBInstances
It would be good to either amend this to support a cluster, or introduce a new annotation
@EnableRdsCluster
What do you think the chances are for RDS cluster support in Spring Cloud AWS?

unable to connect to an Aurora RDS Cluster with read replica  (through annotation and through the application.properties file) for spring boot project using spring cloud
Any news Please !

@aravindparappil46 currently you have to do it manually - look at Vlad's post for inspiration: https://vladmihalcea.com/read-write-read-only-transaction-routing-spring/

This has also been reported here: This issue has also been reported here: https://github.com/spring-cloud/spring-cloud-aws/issues/302

Much needed one..
People are now going for serverless RDS, so cluster connection establishment is really required.

Looking forward to the 3.0.0.M1 milestone!
Definitely need this feature to be able to connect to an Aurora RDS Cluster (through annotation and through the application.properties file) for Spring & Spring Boot projects.
Meanwhile, if anyone knows a workaround for connecting to an Aurora cluster in Spring Boot and enabling read replica support, please post here!

I've done it for now using reader/writer datasources +  AOP .
basic idea is here: https://fable.sh/blog/splitting-read-and-write-operations-in-spring-boot/
Looking forward to 3.0.0.M1  milestone!

Do we know if this is on the road map at all?

Vlad's post is interesting and certainly helps for day-to-day running.   But it's of little help to Spring projects that are looking to reap the benefits of Aurora clusters for failover.  The current provision of a retry interceptor isn't really good enough.  Services should be able to connect to a cluster, the SDK should be aware of which instances are write and read-only, and should direct requests accordingly.
Roll on 3.0.0.M1.  Hopefully that addresses the failover issue.

This is unexpected and leads an RDS Aurora MySQL user to consider just preferring a jdbc url to the cluster, which works normally, finds the writeable instance and handles the read/write failover afaiks; unlike the specific RDS support provided here.

@maciejwalkowiak:
is there any update on this issue:
for me currently it looks like this is severe blocker using RDS in combination with spring boot:
the functionality to utilize the read replicas is simple broken in combination with spring-cloud-aws-jdbc?
or am I missing something?

Also most people want to select the connection pool themselves. Spring cloud AWS kind of hard code it to Tomcat's  connection pool.

@dlamblin for the failover scenario, I would also recommend just using plain JDBC url. Read replica support is the interesting feature of Spring Cloud AWS.
@BerndFarkaDyna read replicas do work, just not with Aurora.
@Lucas3oo very much agreed.

I'm trying to switch from RDS Postgresql to Aurora Serverless and I found that it doesn't work with Spring Cloud AWS.
Am I correct in surmising that the reason it doesn't work is that Aurora Serverless only provides a cluster (instead of instance) URL? And therefore, in order to use Aurora Serverless, this issue needs to be fixed?
If so, I think that as a very first step, this should be addressed in the documentation. Perhaps where it says "The minimum configuration parameters are a unique id for the data source, a valid db-instance-identifier attribute that points to a valid Amazon RDS database instance." we should add "Aurora Serverless is currently not supported, because it provides a cluster URL and Spring Cloud AWS does not yet support cluster endpoints."

@fletchgqc both traditional Aurora and Aurora Serverless aren't supported.

@maciejwalkowiak Ahh OK, thanks for the info. Maybe that should be mentioned in the docs? Because Aurora is a part of RDS, and RDS is partly supported.

@fletchgqc you're right https://github.com/awspring/spring-cloud-aws/issues/172

To add some info in general: You can setup Aurora as a cluster with only one instance in it. Then the "endpoint" will be the "writer" endpoint, But the specific "reader" endpoint will in fact be the same hostname in case of a one instance cluster.
So it is perfectly OK to use an Aurora cluster like that from Spring. But Since the failover is done using DNS names you should set the DNS cache TTL in JRE to absolute minimum. Default is cache forever.

Yes having seamless Reader Writer support for Aurora similar to RDS is really important. Please prioritize or provide a workaround.

This kind of works out of the box if you use the MariaDB driver in Aurora mode. When using a readOnly transaction, the driver will choose one of the reader connections instead of using the writer.
https://mariadb.com/kb/en/failover-and-high-availability-with-mariadb-connector-j/#masterslave-connection-selection

Not working for Postgres as expected. All queries directed to Writer.
On Fri, 1 Oct 2021, 01:45 Nick Caballero, @.***> wrote:

This kind of works out of the box if you use the MariaDB driver in Aurora
mode. When using a readOnly transaction, the driver will choose one of the
reader connections instead of using the writer.
https://mariadb.com/kb/en/failover-and-high-availability-with-mariadb-connector-j/#masterslave-connection-selection
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/awspring/spring-cloud-aws/issues/50#issuecomment-931532800,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA75PXZIVPCZLFNAG65P2LUESO2DANCNFSM4XLLFDNA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

+1 to the feature request

Replaced by #322


Ft/docker scripts prune

Add the script to prune containers as part of the codebase

@philbudne any concerns here

Seems fine. Add install to docker/docker-init.sh??

Not sure about this Add install to docker/docker-init.sh?? but working on the principle that this script is executed post docker installations

docker/docker-init.sh is a script I added recently to install docker
on a story-indexer compute server, and init/join a swarm, so I think
your crontab should be installed/updated whenever
docker/docker-init.sh is run.


feat: add schema validation for option values

use fluent-json-schema and ajv to validate option values as per this issue request

cc @simoneb @Eomm

There is a conflict now, could you resolve i?

There is a conflict now, could you resolve i?

Should be fixed and ready to go


Missing mkdirp dependency

Installing this on a clean machine it appears that mkdirp is not installed. I think it will be if it's moved from devDependencies to dependencies.

nice find tom :+1:

Thx. Hope no one else "found" it.
Sent from Outlook Mobilehttps://aka.ms/blhgte
On Fri, Mar 4, 2016 at 6:08 AM -0800, "Gavin Rehkemper" <notifications<EMAIL_ADDRESS>wrote:
nice find tom [:+1:]

Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_generator-2Desri-2Dappbuilder-2Djs_issues_59-23issuecomment-2D192295665&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=uS3o1AxNqYnWewt8EslJZA&m=VcAsOYlNwmda4bLyH9Gvwy-Vv_rg8M5pP6_fUvcxCgg&s=7aauQ7xpmRjnbkv6ahM13te8MiI0vhEFI4M8Gzm2Ni8&e=.


Button inside viewport not receiving input when Camera2D active

Godot version:
3.3
OS/device including version:
Ubuntu 20.04
Issue description:
Button placed inside a Viewport receive mouse clicks normally, but when a Camera2D is active (whether Viewport is a child of the camera or not) the clicks won't register with the button at all.
Steps to reproduce:

Create a new scene.
Place a Camera2D, inside it a ViewportContainer, inside it a Viewport and inside that a Button.
Set sizes appropriately
Run and click on the button. The button reacts to clicks as normal.
Make the Camera2D current. Run the scene again. Now clicking on the button has no effect at all.

The above just looks at the button's normal animation when clicked, but if you connect an event handler to the pressed signal of the button, you see that with the Camera2D current, the signal is not fired either.
Minimal reproduction project:
test-viewport-input.zip

See also https://github.com/godotengine/godot/issues/35965.

These look very much like having the same root cause as my issue. Hard to be sure though. Also, I see that #29750 mentions that for viewports "you have to calculate input offsets yourself", which I don't remember reading anywhere in the docs is that true? And even if it is, with things like button events we don't directly control the offset calculation so there isn't much to be done.

Minimal reproduction project:
test-viewport-input.zip

Can't reproduce the issue. For me it works fine in both cases (Camera2D's current enabled/disabled). Windows 7, 3.3.stable.

I use a tiling window manager (StumpWM) so when I run the game, it opens maximized by default. I tried the test project again in a "float group" which simulates a non-tiling window manager. Upon running, with the Camera2D current, the button seemed to work fine.
Then I resized the window and suddenly it stopped working. So looks like this only happens when the window is resized to something other than the default size. Maybe that's a clue. Not sure.

Also, looks like if I set the stretch mode to 2d and aspect to "keep", the button continues to work fine even after resize. Although I've got another non-minimal project of my own which seems to still have the issue even with stretch settings set to 2d/keep. That one's only tested in the tiling window manager.

2. Place a Camera2D, inside it a ViewportContainer, inside it a Viewport and inside that a Button.

It properly works for me if i order it like this:

Is there an upDate on the issue ?
if a button is inside a viewPort the mouse position is also showing on top left corner when zooming in / out. It only works with the camera zoom set to 1.
if ( wheel_up ):
	myCamera2D.zoom.x -= 0.05;
	myCamera2D.zoom.y -= 0.05;
	camY += 2.3;

	myCamera2D.zoom.x = clamp(myCamera2D.zoom.x, 0.05, 1);
	myCamera2D.zoom.y = clamp(myCamera2D.zoom.y, 0.05, 1);
elif ( wheel_down ):
	myCamera2D.zoom.x += 0.05;
	myCamera2D.zoom.y += 0.05;
	camY -= 2.3;

	myCamera2D.zoom.x = clamp(myCamera2D.zoom.x, 0.05, 1);
	myCamera2D.zoom.y = clamp(myCamera2D.zoom.y, 0.05, 1);
elif ( mouse_buttonMiddle ):
	myCamera2D.zoom.x = 0.3;
	myCamera2D.zoom.y = 0.3;
	#camY = -200;

I have tested the MRP with v4.2.dev3.official [013e8e3af] and I can no longer replicate the bug.
So I'm setting the milestone of this issue to v3.


remove-pages unhandled exception with space in page list

Description
The page remover fails with an error similar to Internal Server Error:For input string: " <number>" when a space is included in the comma-separated list of page numbers to be removed. This appears to affect both single page numbers and page ranges.
Version

Version 0.20.1

### To reproduce

Choose a pdf with a sufficient number of pages, 10 in this example
Enter a list of pages to be deleted, include a white-space before one of the numbers, e.g. 1,2-3, 5
Click Delete Pages

Expected behavior
There is a couple of options:

I think the better way to handle this is to simply trim each item in the comma-separated list before attempting to do the string conversion. Alternatively, all whitespace could be removed from the input string before processing.
At the very least the exception should be handled and a message displayed to the user that they must remove white-space from their list. I don't think most non-technical users will correctly guess the issue with the current information provided.

@sbplat Can you assign this to me

Sure, I've assigned it to you.

@sbplat I have created a PR for this issue. can you please review it.


Asking

Can django run on grumpy? Any tester here?

 Comment by cclauss
Monday May 14, 2018 at 18:17 GMT

@zantdev Could you please change the title of this issue from "Asking" to "Can Django run on Grumpy?"  That change would make it easier for people to discover this issue.
Grumpy is intended to be a near drop-in replacement for CPython 2.7 so that would preclude the use of Django 2 which requires Python 3 but perhaps Django 1.11 could work.

 Comment by alanjds
Friday Aug 03, 2018 at 15:46 GMT

Kamino cloned this issue to grumpyhome/grumpy

@zantdev: No. It does not run Django right now. Some stdlib imports are still missing. For exemple, sockets is yet not provided.


[DONT MERGE] Migration of projectID in etcd keys

Dalsi postup je:

nasadit to postupne na kazdy stack, naprv testing stacks


Need the z-index increased

It looks like the z-index needs increased to something above 20 for the modal.   The vitepress tool bar wasn't greyed out.
Also, in light mode the search item hover turns to white which isn't enough contrast.    Just FYI on both of these.   Great plugin!
Here's the modifications I made locally
.modal-back {
    z-index: 30;
}

.search-item:hover {
    color: var(--vp-c-brand);
}

.search-item:hover > p {
    color: var(--vp-c-brand);
}

Should be fixes in the new version..
they changed the css in vitepress (is in alpha so they can.. 😁)


TextFormField create clickable area for copy paste when selected on iOS which consumes touch events from underlying widgets.

Steps to Reproduce

Create Form with at least one FormTextField
Place a button below the FormTextField
Write at least one character in the FormTextField.
Remove focus from the FormTextField (for example by selecting another TextField)
Return to the FormTextField.
Try clicking the button below the FormTextField.
Instead of clicking the button a "copy/paste" dialog will appear.
This is because a touch field (terminology?) is created from the end of the string to
infinity x and y coordinates.

Here is two images showing the touch field on IOS (left) and Android (right).

Trying to click on the button on iOS results in a copy/paste dialog showing above the insert marker. The next button click dismisses the dialog and the touch field, but the click is still consumed. The third time the button is clicked.
The image below shows the "copy/paste" dialog showing after the first button click attempt.

Code
Runnable project to reproduce the reported behavior.
Show Code
import 'package:flutter/material.dart';

void main() => runApp(MaterialApp(home: Playground()));

class Playground extends StatefulWidget {
  @override
  State<StatefulWidget> createState() => FormTextExampleState();
}

class FormTextExampleState extends State<Playground> {
  final _formKey = GlobalKey<FormState>();
  final _emailController = TextEditingController(text: 'my.email@host.com');
  final _passwordController = TextEditingController(text: 'password');

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Builder(
        builder: (context) {
          return Center(
            child: Form(
              key: _formKey,
              child: Padding(
                padding: EdgeInsets.only(left: 64, right: 64),
                child: Column(
                  crossAxisAlignment: CrossAxisAlignment.center,
                  mainAxisSize: MainAxisSize.min,
                  mainAxisAlignment: MainAxisAlignment.center,
                  children: <Widget>[
                    TextFormField(
                      controller: _emailController,
                      keyboardType: TextInputType.text,
                    ),
                    TextFormField(
                        controller: _passwordController, keyboardType: TextInputType.text),
                    Padding(
                      padding: EdgeInsets.only(top: 16),
                      child: RaisedButton(
                        shape: RoundedRectangleBorder(borderRadius: BorderRadius.circular(5)),
                        color: Colors.red[700],
                        onPressed: () {
                          showSnackBarMessage(context);
                        },
                        child: Text(
                          'Login',
                          style: TextStyle(color: Colors.white),
                        ),
                      ),
                    ),
                  ],
                ),
              ),
            ),
          );
        },
      ),
    );
  }

  void showSnackBarMessage(BuildContext context) {
    Scaffold.of(context).showSnackBar(
      SnackBar(
        content: Text(
          'Button click registered',
          textAlign: TextAlign.center,
        ),
      ),
    );
  }
}

Logs

Flutter analyze
Analyzing brl-birthday-flutter...
No issues found! (ran in 6.4s)

Flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.7.8+hotfix.4, on Mac OS X 10.14.6 18G87, locale en-SE)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/setup/#android-setup for detailed instructions.
[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
[✓] iOS tools - develop for iOS devices
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.36.1)
[✓] Connected device (2 available)

! Doctor found issues in 1 category.

I'm not even sure what this touch field is for or if it should be there on the first place.

Bump.
I can't be the only one affected by this?

Hi @joelbrostrom
I wasn't able to reproduce this issue on latest dev
Are you still experiencing this issue?

flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.4 19E287,
    locale en-GB)
    • Flutter version 1.12.13+hotfix.9 at /Users/taha/Code/flutter_stable
    • Framework revision f139b11009 (3 weeks ago), 2020-03-30 13:57:30 -0700
    • Engine revision af51afceb8
    • Dart version 2.7.2
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1
[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
[✓] VS Code (version 1.44.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1
[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API
      29) (emulator)
• No issues found!

Thank you

I hope it's fixed.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of flutter doctor -v please.

I'm sorry for the lack of response.
I haven't worked with flutter for the past 3 month.
It sounds like you fixed it. Great job!


What is the difference between hootsuite/akka-persistence-redis ?

Hey,
would you please add a paragraph about why should people use this over hootsuite/akka-persistence-redis ?
I'm currently using the above mentioned plugin but for some reason ~ 1 of 1M messages fails to be persisted and I cannot figure out why, so I'm wondering whether to switch to this plugin implementation.

I am not sure I will add such a section because it may be difficult to maintain.
The project was started to add following features that we were missing in the hootsuite persistence plugin:

event tagging
use of akka serialization framework to choose serialization format
implementation of journal queries

Just as @l15k4  I am currently using the hootsuite version. In order to be able to switch (as I am running on Azure), I would need to implement a similar pull request as https://github.com/hootsuite/akka-persistence-redis/pull/21. Would it be something I can try to implement in this component and that would get accepted?

Hi,
From what I see, it means adding a max-replay-message integer configuration key. It would totally be accepted.
Is overriding key namespace also required? I would also accept that, but I would prefer two PR, one for each addition.

Great for the first one, I will start a PR right now.
How are the keys named today? Basically I have several Akka Persistence independent instances writing to the same Redis Cache, so I need to have them writing to different keys.

And just out of curiosity, do you consider this component as production ready? The 0.3.0 version number frightens me a bit :).

For your use you will also need to be able to override the namespace.
I'd say it can be used in production, we use it internally and never experienced problems with medium amount of events per seconds. The version number is low because for the moment, not much features are present, but I think it is quite stable.

Ok thanks. Will start working on the 2 PRs right now :).

Actually it looks like I do not have the issue I had with Azure before, where I needed to have a max-replay-message. And if I understand correctly, I can use the persistenceId to write in different keys. so maybe I do not need any change after all :).


Convert to ES modules

Follow-up to https://github.com/regl-project/regl/issues/118#issuecomment-252243484. Will no doubt require some finessing, but I thought I'd share what progress I've made to open it to discussion.
The headlines: regl.min.js is 5.8% smaller (25,093 bytes zipped, down from 26,641), and initialization time, measured like so...
console.time('parse')
/* contents of regl.min.js */
console.timeEnd('parse')

...is reliably a decent amount faster in all the browsers I've tested (on this machine, drops from ~14ms to ~5ms on Chrome). The tests all pass and as far as I can tell all the gallery examples work as before. No changes required to the code beyond swapping require and module.exports for import and export.
As far as consumers of the library are concerned this shouldn't change anything – it's still creating a UMD bundle that behaves exactly as before. Deep imports (e.g. require('regl/util/raf')) wouldn't work without transpilation but I don't imagine that's a supported use case?
Let me know if you have any thoughts/questions about this approach.

This change is

Oh – a couple of things I forgot to mention. The check-dependencies script doesn't work with import declarations AFAICT, so I had to disable it. I don't know of an equivalent of discify for ES modules, so I disabled that too, but it was only generating a donut chart with one data point anyway.
Also, this turned into a series of slightly messy commits by the end, sorry about that – can rebase etc if nec!
Am looking into the CircleCI failure.

Cool! I'm ok with breaking the discify script as long as all tests pass.  It seems like this is overall a net win and I'm pretty happy with the parse time improvements.

Review status: 0 of 157 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

package.json, line 5 at r2 (raw file):

  "version": "1.2.1",
  "description": "regl is a fast functional WebGL framework.",
  "main": "dist/regl.unchecked.js",

This seems broken.  We should be exporting regl by default so that you get checks in nodejs.  We only want to remove checks in non-debug builds.

Comments from Reviewable

Review status: 0 of 157 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

package.json, line 5 at r2 (raw file):
Previously, mikolalysenko (Mikola Lysenko) wrote…
> This seems broken.  We should be exporting regl by default so that you get checks in nodejs.  We only want to remove checks in non-debug builds.

So it should be `dist/regl.js`? Will change. What about the `browser` field, is it necessary in that case? Not sure what the mechanism for using the debug build would be

Comments from Reviewable

Going through I have some general thoughs:

This build currently removes all checks which is pretty bad.  One of the most important features of regl is that it can give sensible error messages which can also be removed in production.  Taking out error messages for all users is a serious bug and needs to be fixed before this can be merged in.
The whole roll up process is way more complicated and messier.  It will probably slow down regl development, but since things are pretty stable right now I'm ok with this if it gives better results at the end of the day.  That said I want to make sure that we have solid integration tests so that nothing slips through in this one.
Concatenating all scripts for checked builds is not really worth it IMO.  It also makes things harder to debug since you have to step through some inscrutable blob of code if you have an error internaly in regl.  Keeping everything in commonjs format was nicer for the non-roll up builds.  Is there maybe a way we can continue using the require syntax and also take advantage of rollup's improved build capabilities?  It doesn't seem like it would be much trouble to just do that step in a syntax transform and then avoid having to change everything.

This is a big PR, but it is probably worth it if it makes things smaller and load faster.  I like browserify much better from a development perspective, but at the end of the day the numbers here are definitely in favor of rollup.

Thanks for reviewing it and entertaining this idea!

This build currently removes all checks which is pretty bad

Not sure I understand? The checks are all still there in dist/regl.js – regl.js is 9490 lines while dist/regl.unchecked.js is 8211.

The whole roll up process is way more complicated and messier. It will probably slow down regl development

What do you mean by that specifically? If there's something we can change in Rollup to improve the development workflow, let me know. Most people who have made the switch to ES modules have found that their development experience improves, because of the better static analysis etc (e.g. imports with typos are obvious compile-time errors rather than confusing runtime errors.) It just takes some getting used to 😀

It also makes things harder to debug since you have to step through some inscrutable blob of code if you have an error internaly in regl

I'm not sure how that's any different to a CommonJS bundle? If it's about sourcemaps, we can enable them very easily.

Is there maybe a way we can continue using the require syntax and also take advantage of rollup's improved build capabilities?

It does build if you keep it as CommonJS and use a syntax transform (specifically, rollup-plugin-commonjs), but the end result is larger than the pure ES module version, so I'd recommend against it. The concepts (e.g. namespace imports) don't quite translate, and you still have to have the require statements even if they're just translating the statement to a module-local variable declaration. I don't quite follow why CommonJS syntax would be preferable, but if you can explain then we can try and find a solution with the best of both worlds.
🍻

Alright!  I think this looks great, but I do want to fix it up so we aren't using ES6 style modules where it isn't necessary and get that debug build working again.
If you're swamped with stuff I can just do it myself and then merge this in.

Hey – no worries, I have some changes locally which reinstate sourcemaps and the rest of the previous debug behaviour (as far as I can tell). Will push up in a sec.

so we aren't using ES6 style modules where it isn't necessary

Can you elaborate on that? The original motivation for this in #118 was to reduce the size – that's possible because of ES6 modules. Moving the codebase back to CommonJS would undo those benefits and the parse time improvements. If it's about workflow then let me know what your concerns are, there might be something we can do

My thinking is to just use a babel transform to automatically convert the CommonJS modules to ES6.  This doesn't have to be perfect, just good enough to work with the regl code base.  That way we don't have to modify any existing code and still get all the benefits of using rollup's improved bundling.

automatically convert the CommonJS modules to ES6

Unfortunately that's not really a thing – rollup-plugin-commonjs is probably as good a CommonJS -> ES6 converter as you'll find, and the resulting bundle is larger. (I know this because that's what I used so that I could port one module at a time and verify that I wasn't causing any tests to fail, and I watched the filesize drop as I converted each module.) I'm not sure what impact it would have on parse time – it would probably still be quicker than the current build, but not by as much.
I'm still not clear on the goal – what specifically would be the reason for keeping CommonJS modules?

I bet we could do something more specific for regl.    We don't need a general purpose solution for this, just one that works for regl.


Translatable theme

This theme is "official" and really useful but it is not available in french.
I will fork this theme and make it translatable, with at leat fr and en implemented.
Is this something you could potentially merge ? As I will not have time to keep this theme up to date with the new features, I would like to contribute to the official theme.

Hey there, you're very welcome to translate the theme or release your own translated themes! We're not ready to include translations by default in the theme at the moment.


Check .git sync script in WP plugin

Tried to rename a git repo, but reverted it back after some work-streams became more clear.
Need to check that future updates will be visible via git updater.

Finally happening. Safe to close this now.


Hide attributes labels

Hello,
Is there an option to hide attribute texts of entities? All my entities are on/off so it's kind of useless since the color already tell the state
Thanks

It's not possible to hide them. I'm not sure if there is a good general use case for this option and it's not something that is planned at this time.
While the text may be redundant for some specific scenarios, the labels are inline and render only if there's enough space. They don't take away any useful area or make the card bigger. In the vast majority of use cases the state labels are highly useful and even vital for the usage of the card.


Portfolio customisation

it seems you havent deploy your project to appengine?

could you include the pom.xml file to the PR as well?


[Help Wanted]: Xcode plugin gives exteremely poor suggestions in comparison to VSCode. What am  I doing wrong?

Before Reporting

[X] I have checked FAQ, and there is no solution to my issue
[X] I have searched the existing issues, and there is no existing issue for my issue

Describe your issue
I'm struggling to make copilot in the xcode plugin to produce useful results.
It doesn't provide code suggestions from comments, and the overall quality of the copilot suggested results seems extremely poor when compared to the suggestions in VSCode on the same thing.
I feel like I'm doing something wrong. Please assist.
Suggestion in Xcode. A poor suggestion with broken code.
And more often it suggests comments and opening function blocks with {.

Suggestion in VSCode. Exactly what I needed:

Generating code with comment
Try to give it more hints that the next line is code. For example,

add an empty line after the comment:// do something

// cursor here

instruct it to generate code// a function to do something
// cursor here

or// do something
func// cursor here

Broken code
Currently, GitHub Copilot has the ability to generate suggestions based on the opened files in the same workspace. In order for GitHub Copilot to detect an opened file, language server notifications need to be sent to the language server when a file is opened.  It sounds simple, but Copilot for Xcode can't get those notifications from Xcode. As a result, it can only detect that a file is opened when the user manually switches to the tab of the file and clicks into the file (to change focused element, if you are opening a file from the side bar) for the first time.
Additionally, if a file is already open prior to the extension launch, the user will also need to switch to the file manually in order for it to recognize that it is open.

Thank you for the quick response, it's very helpful indeed.
If I understand correctly number 2, if I work on something that depends on 10 other files, and I open all those files, that should be enough to improve copilot results?

Theoretically, yes, but sometimes even with the other files opened, GitHub Copilot can still generate incorrect suggestions even in VSCode.

Thank you 🙏


supersonic.ui.modal.hide() triggers success callback too early

Supersonic windowing APIs trigger success callback too early.
Current behaviour:
Methods such as supersonic.ui.layers.popAll()and supersonic.ui.modal.hide() trigger success callback when the API call has been received in the native wrapper. Ie. the native API call has not yet been executed when the Javascript success callback is invoked.
Expected behaviour:
Success callback should be triggered when the native wrapper API call has been successfully executed.
Workaround:
Use Steroids.js events such as didclose to determine when the native API call has completed.
See Steroids modals and Steroids layers for further documentation.

I am geeting same error from one controller call show tab and navigate to other page and call hide tab
{"datetime":1422601786134,"view":"http://localhost/app/example/using-the-scanner.html","host":"<IP_ADDRESS>:4567","device":"iPhone","level":"error","message":""supersonic.ui.tabs.hide rejected: Cannot hide tab bar while another transition is in progress"","timestamp":"2015-01-30T07:09:31.103Z"}

@aloharavirajp Did you didclose or any other event work for you as a workaround?

I see the same problem with supersonic.ui.tabs.select().  For example,
supersonic.ui.tabs.select(1).then(function(){
	supersonic.ui.layers.pop();
});

I get this error "supersonic.ui.layers.pop rejected: No layers are open".  But, if I add a delay to the pop() call, it works.
Will these be fixed any time soon?


Programmatically close dialog on item click

I am using the sample to create a new blur dialog and everything is working great, when I select an item from the list I start a new activity, and it all works great, but if I hit the back button in the action bar when I get back to the activity that has the blurred dialog the dialog is still open. I have to click somewhere on the screen that is not in the dialog to make it go away.  I can't find a way to programmatically close the dialog when a user selects an item in the dialog list.
I am using the following method to create the dialog in a fragment...
@Override
    @NonNull
    public Dialog onCreateDialog(Bundle savedInstanceState) {
        final AlertDialog.Builder builder = new AlertDialog.Builder(getActivity());
        View view = getActivity().getLayoutInflater().inflate(R.layout.fragment_profile_dialog, null);
        TextView text = (TextView) view.findViewById(R.id.follow_or_unfollow);
        if(isSelf) {
            text.setText("Edit Profile");
        } else {
           text.setText((isFollowing) ? "UnFollow" : "Follow");
        }
        RelativeLayout followButton = (RelativeLayout) view.findViewById(R.id.follow_layout);
        RelativeLayout chatButton = (RelativeLayout) view.findViewById(R.id.chat_layout);

        followButton.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View view) {
                //NEED TO DISMISS DIALOG WINDOW HERE
                if(isSelf) {
                    //activate ProfileEditActivity
                    getActivity().startActivity(new Intent(getActivity(), EditProfileActivity.class));
                } else {
                    Map<String, Object> updates = new HashMap<>();
                    if(isFollowing) {
                        //unfollow
                        updates.put("/following/" + user.getUid() + "/users/" + userID, null);
                        updates.put("/followers/" + userID + "/users/" + user.getUid(), null);
                    } else {
                        updates.put("/following/" + user.getUid() + "/users/" + userID, true);
                        updates.put("/followers/" + userID + "/users/" + user.getUid(), true);
                        //follow
                    }
                    database.getReference().updateChildren(updates);
                    getFragmentManager().beginTransaction().remove(ProfileDialogFragment.this).commit();
                }
            }
        });

        chatButton.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View view) {
                Toast.makeText(getContext(), "Implement the start activity for chat", Toast.LENGTH_SHORT).show();
            }
        });
        builder.setView(view);
        return builder.create();
    }

I don't see any example of how to close the dialog when a user selects an item from the dialog window. Please help, I am still pretty new to android and have no idea how to get this dialog to close once the user selects an item in the dialog. Thank you

Hi (=
First of all, thanks for your interest in this quite old project.
If I understood well, you might simply need to call dismiss() just before/after the startActvity
https://developer.android.com/reference/android/app/DialogFragment.html#dismiss()


build: add CI for OpenBSD and FreeBSD

There are some existing test failures on both OSes, and I've adjusted some of the asserts so it's easier to see why they're failing.
I'll try to find some time to look into the failures, but I thought it would be better to have this up for discussion rather than delay it due to those.
Closes #3510

@jamessan do you still want to pursue this?

Someone more familiar with libuv internals and BSD should take it, or skip the failing tests to establish a baseline.
I don't currently have the time to understand what the tests are trying to validate and why they're failing.  I was hoping to spark some interest in having some BSD CI.
If nothing else, at least the extra diagnostics in the tests should be helpful. :-)

Can we have those jobs added even if we have currently some failing tests?

We could skip failing tests if there aren't too many. I'll rebase and take stock.

freebsd: Terminating VM (during build)
openbsd: /bin/ksh: <stdin>[4]: cmake: not found
Guess that means it's not ready for inclusion in the CI matrix yet.
@jamessan if you can get it to a point where the test runner runs to completion, I can take it from there. Otherwise, I suppose we should close this.

@bnoordhuis The FreeBSD error was further back in the log:
/Users/runner/work/libuv/libuv/src/unix/thread.c:389:9: warning: implicit declaration of function 'sched_getcpu' [-Wimplicit-function-declaration]
  cpu = sched_getcpu();
        ^
1 warning generated.
...
ld: error: undefined symbol: sched_getcpu
>>> referenced by thread.c
>>>               thread.c.o:(uv_thread_getcpu) in archive libuv_a.a
cc: error: linker command failed with exit code 1 (use -v to see invocation)

Looks like that was introduced by https://github.com/libuv/libuv/pull/3803.  As far as I can tell, sched_getcpu() is glibc-specific, so it looks like the checks for when to use it are wrong.

Looks like that was introduced by #3803. As far as I can tell, sched_getcpu() is glibc-specific

I think it was added in FreeBSD 13.1. So this check should be added:
__FreeBSD_version >= 1301000

Ok, @bnoordhuis.  I had to make some changes to the thread affinity support to get libuv to build/run tests on the BSDs.  The remaining test failures appear to be back to what I was seeing when I first opened the PR.

@jamessan could you mark the rest as TEST_SKIP, so we can merge your current work before it gets stale?

I'm considering dropping the freebsd and openbsd buildbots again. They're disproportionally flaky compared to other platforms and no one seems invested enough to investigate so they just end up being a nuisance and a time sink.


Make WeightCollection not a class

Caffe weights should just be a Map[String, List[NDArray]]. Having a class around that obscures what is going on. It'd be better have WeightCollection be an object which just contains a bunch of helpful methods (for adding two weight collections, testing equality, etc).

Addressed by #116.


Redundant slash in  redirect url with basic config no-proxy

Wrong  redirect url with basic config no-proxy
Summary
Gatekeper 2.3.0 running with latest Helm Chart.
discovery-url: {{ $.client_endpoint }}
client-id: {{ $.client_id }}
client-secret: {{ $.secret_oidc }}
listen: :3000
listen-admin: :4000
enable-refresh-tokens: true
encryption-key: {{ $.encryption_key }}
no-proxy: true

Running:
curl http://service.namespace.svc.cluster.local  --header "X-Forwarded-Proto: https" --header "X-Forwarded-Host: my-domain" --header "X-Forwarded-Uri: /"
Expected Results
Server should redirect to:
my-domain/oauth/callback?authorize?state=...
Actual Results
Server should redirect to:
my-domain/oauth//callback?authorize?state=...
(note the slash duplication)
Investigation
Disclaimer: I know nothing in Go.
Looking here:
https://github.com/gogatekeeper/gatekeeper/blob/323f48085dcf08ac4dd22001fa9bb0b18f74d6f5/pkg/config/config.go#L398-L403
here:
https://github.com/gogatekeeper/gatekeeper/blob/323f48085dcf08ac4dd22001fa9bb0b18f74d6f5/pkg/constant/constant.go#L17
and here:
https://github.com/gogatekeeper/gatekeeper/blob/323f48085dcf08ac4dd22001fa9bb0b18f74d6f5/misc.go#L254
I'd say that's pretty logic, but once again, there might be some magic trick I'm not aware of.

thanks for reporting, it is minor issue, will look at it


Super speed on laser, causing missing steps etc on v 0.7

Hi
I've tried cutting and engraving before with no problems. Today I converted a grid pattern to vector engrave to save time. I set to engrave at 50mm/s (settings I used from K40Whisperer) and hit start. The first thing to happen, was the vector engrave, even though I set it to do the raster engrave first. It did not matter at all in this case, but the speed is just crazy. I flung the head so fast that the adjustable focusser lost alignment and it skips steps like crazy.
I did the obvious and reduced speed to like 10mm/s, just a bit faster than cutting speed, but the result is the same. I thought my laptop or controller has gone mad, and reset both with power cycle, same result. I then tried v0.6 and the file seems to work fine.
And maybe as a feature request, please add deeper "Undo" levels. I stuff up too frequently as a newbie!
Many thanks to all the developers for this project!

Please confirm the exact beta version of 0.7.0 you were using and upload a version of the SVG file saved from that version.

50 is fairly quick. The optimization can certainly move those things out of order. My best guess is that it's not doing jogging. So what you get is it moving to the next location at the speed of the object it's going to engrave in this case a fairly fast raster. So it goes to the raster at raster speed, which it really shouldn't do.

Is this a bug in optimiser?

Hi. I'm using v0.7.0 RC-6.
I had to upload as a zip as svg is not supported. The blue lines is my problem.
As mentioned I used speeds that worked for me from K40Whisperer. Raster engrave 250mm/s,  vector engrave (blue lines) as 50mm/s and cut 8mm/s.
The only difference is I used the 'ppi function in Meerk40t to have the "same" power, i.e. 400ppi to get 40% power etc. When the blue lines were "rastered" it worked fine, even though I did not manage to cut right through the plywood as expected, but that is a small issue, probably more to do with my laser's power curve than with the software.
calendar backing.zip

Hi. Just as further information. In Optimizations, I turned off "Rapid moves between objects." But it made no difference.
I just now figured out how to simulate just the blue grid and it basically seems to be as erratic as the actual cut. (At least it did not bang my laptop around! LOL!) But I did expect it to draw the lines one full length at a time in stead of mostly single short lines.

Well, if you turned off optimizations altogether you could likely see if it was caused by optimizations. There's some reasonable chance that it's doing things you generally would not want. I'm not sure this is a bug in optimizer but since that is a major change and something is weird with the ordering it's the number one suspect.

Hi. I am busy with upgrades, so spare laser time is for that! Will try again when it is up and running again. No that the week end is gone, it becomes unlikely this week.

Hi tried tonight with the same file. Turning optimizations off does not do that much better. It stops the "ramming" but I can see how dots looks like it "spreads out" on the work. It seem that after a direction change the dots are spaced further apart, and then gets closer as it appears to break before the next direction change. I don't think dots should be separate trying to vector engrave. I did 50mm/s, then 30mm/s, the issue is the same, only less pronounced.

@bergie5737

Please confirm the problem still exists in RC8.
Please upload your original SVG file and a version of the SVG saved by MeerK40t (which has the operations defined).

Hi
Mine k40 cannot vector ebgrave faster than 30 -35mm/s - most usual it will loose steps on Y axis -and engraving is misplaced :(
I tried acceleration setting reduced to 1 - but it didn't help
also if I take metric ruler to engrave  as vector - at 35mm/s - vertical lines  are wavy - it is vibration from axis  - reducing to 30mm/s helps  keep things straight
and even at 35mm/s   sometimes there is Y axis skip - for example such ruler - it starts engraving scale from 0  to 4 then skips few millimetres and engraves up to 10cm  and then go back  to engrave missing ones  but they are not aligned  - I can provide photo of such result.
I tried to set acceleration reduced to 1 but it doesn't help much.
I tried to  tighten belts, loosing them - no effect, gantry feels rigid - not much play  between ends (cannot be skewed manually  - I cannot feel any play by hand - if enough force is applied - it will skew - always  ;) just a matter of force :P
I had  cleaned and greased  rollers, checked for play on stepper <>axis coupler
I upgraded power supply - nano board with motors is powered from external 24V PSU
what I was able to read somewhere -  k40 parts are on the budget  - cheapest  found in all China ;)
so most likely there is a culprit.
Funny thing is - it can raster engrave even at 400mm/s (not crosshatch) although power has to be increased
I am in the process of converting gantry to V-slots  and maximizing work area to 600x300mm - I will most likely change motors  - and then I will test
Best regards
Mike

@MiBu-dev @tatarize Here is my take on this:
Clearly the steppers are capable of moving the head in both directions at faster than 35mm/s because we raster in those two specific directions at 10x+ that speed.
Whatever speed you choose, the head needs to reach that speed and maintain it for the entirety of the burn - which means that it needs to be able to achieve the acceleration needed on even the smallest / narrowest of curves. It is possible that when you get to sharp corners you stop burning, do a travel and approach from a different direction, and I have seen this happen in practice, though not sure whether this is something that happens automatically in the m2 nano or something that MK explicitly does.
So... it seems to me that:
Suppose you set 100mm/s for a vector burn at 1000 ppi.
It would then be possible to do some paths at 100mm/s at 1000ppi if they were straight or only slightly curved.
And then we could be clever, and burn tighter curves at (say) 30mm/s at 300ppi and get the same strength of burn.
In other words, you MeerK40t could do variable speed vector operations depending on the curvature of the path, and thus reduce the time taken.

@MiBu-dev 0.7.4 / 0.7.5 beta 1 are the current versions.
Default speed for new Engrave operations is 35mm/s but you can change the speed either by double clicking the operation node to open properties or by using a right click menu.
I have also considered changing the 24v supply for the steppers to a separate PSU as my steppers don't seem to have the power I think they should have - but I will not bother given your experiences.
You should also consider setting steps of 2 or 3 on your raster operations to speed them up. In essence IMO you should almost always be burning at 12mA, and using speed and steps (or PPI on rare occasions) to reduce the burn depth where needed. So rather than doing raster engraves every 0.25mm (which is approximately 10 mil) doing 60 sweeps at 35mm/s you can do e.g. steps 5 at 200mm/s and be even faster.

@tatarize  - I will check tension again - although belts are not loose and make sound - not like guitar strings but are tensioned as good  as in my 3d printer - although my k40 worked before in transformer workshop - cutting a lot of parts
I made a plan to test  some speeds  and shapes  - so I will keep you posted.
I will test also Whisper with same files  to be sure
I have checked axle coupler  on the motor - all screws are tight and there is no free play on that axle - gantry with lock enabled doesn't appear to have it also - but those are  minimal resonance  disruptions - same effect is seen with 3D printing - when head is turning 90deg on print appears pattern - because line is not straight  but waving  because of  vibrations
I thought that accel parameter was just like in Marlin firmware for 3D Printers - determining how fast  stepper driver will spin  the motor to achieve full speed  and how fast  to decelerate before direction change - it has quite an impact    called "ringing"  when on object's wall is some detail and print head is making  movement changes  - sometimes it is just  loose belt, sometimes  the mass of the whole bed moving ... not the topic here ;)
@Sophist-UK  - I am using 0.7.4  on Ubuntu 20.04( so I updated wiki  because manual was not up to date  - URL missing )
PSU upgrade  I made  after https://k40.se/k40-laser-electronics/connect-a-24v-external-psu/
and the fact  that previous owner  blow the original one , I had replaced HV transformer but .. PSU exploded after few test (damaged mosfets or something else)  so I replaced whole unit from Cloudray and it is OK.
thanks for the tip about steps - somehow  I did not consider this (maybe as beginner playing with image engraving - this option is grayed out (set to pass through) - that is exactly what I was thinking - instead of glacial line by line - few lines with more power although slower - in such case material is not vaporized but carbonized :) so it is darker  (on some plywood types  engraving  leaves beige   (somewhat darker) marks. Heck  - on stained  plywood i managed even to... engrave in  "white"  - paint was removed and  clear wood  appeared (it was not  as dark as engraving clean plywood (it was stained one side)
I will test steps and do some timings.
I was thinking about automatic hatch infill depending on color  - it can be achieved manually ofc

OK - i recorded video, made some samples, tighten the belt from one side some more,
when running  simple 20mm circle with rectangle inside - almost everything went OK up to 85mm/s (although some waves appear

at 95mm/s it went nuts - at 105 rectangle was misplaced
as gantry  was making some stuttering noises - that's was the reason i suspected  motors
I opened the lid  and started poking around - and... voila - roller in aluminum profile  has worn bearing :(  it has   unexpected play up/down (gantry is not moving  in that plane - it would be Z axis :)
the play is minimal - about 0,5 mm - but wheel is skewing and most likely not turning  and making gantry to catch on one side
as  I am going to gut out everything  inside to make room for new  gantry  from 2020 and 2040 V-slot profiles - there is no point to reanimate this bearing - replacement from Aliexpress would take too long to arrive - and  default work area is ridiculous
Thank you very much for patience and helpful hints.
As for  infill with hatch infill - hmm  - remarks from @Sophist-UK  were quite helpful - I will experiment some more with steps and speed  - hatch infill can be still be useful in some cases (except  that after applying them in Inkscape plugin project become non scalable somewhat

@joerlane What is that? I swear you mentioned something almost exactly like that.
I'm pretty sure there's a hardware issue that exactly matches your results I forget what exactly is though. Something like belts are too tight or something. Joe might know assuming he's not neck deep in his new toy.

Also, most folks stop cutting speeds before going that high, it's sort of hard to keep the machines from getting very iffy above 50mm/s just because of the amount of weight being thrown around.

Also, most folks stop cutting speeds before going that high, it's sort of hard to keep the machines from getting very iffy above 50mm/s just because of the amount of weight being thrown around.

This is true for current MK and @MiBu-dev 's current problem.
But as discussed above, the issue is acceleration on curves - hence my suggestion for a future enhancement which does variable speed cuts, speed of a path-segment varying upon the curvature of the path-segment, and using PPI to compensate for burn depth when the speed is reduced from the Operation speed.

I think if you switch to jog reset it might actually work better at higher speeds. The core idea is that the twitching during a full reset between two different jumps should actually twitch in the correct direction. Then if you're mostly going in an orthogonal or diagonal direction you should decelerate correctly directioned. So rather than bank a turn at speed you'd cut the turn into two different sections where one side would jerk the slowing position and the other would jerk up to speed the other way. I don't know what the gain/loss there might be where you'd basically need to decelerate at every rapid speed switch. For a rectangle as an example you'd go to the right, decel, acel down, go down, decel, acel left, go left etc. So you would avoid any corners if you could avoid them.

The NSE jogs twitch according to the originally set raster direction. Whereas @NSE jogs would terminate and should jog in the direction the stepper motors were currently set. So you should get the 8 different directions of jogging. You'd likely need some code to calculate the current acceleration at any particular point and stop when it gets too high. Acceleration during curves that is as you'd go the same speed but the vector of movement would be changing direction, if you would be jogging entirely x-parallel or y-parallel you that happened to match the major axis for the rastering you could also just do an NSE jog in that direction. The end result is that you could actually go at raster speeds for non-rasters so long as you happened to be going raster directions. But, you'd still need code that could calculate where you'd need to throw in a break especially if that was a corner or corner like part.
The same code thing I'm doing with ruida rasters would sort of apply there. If you just happen to be going a direction where you could apply an accel or decel in a coherent fashion, you could do that selectively. This might be best in cases where you switch from going right to going left. And in those cases you could even call an NSE jog to switch your directionality. In the case where you're going along the would-be raster axis this would correctly switch your directionality. And in cases where your ending directionality isn't along this axis you could just apply an @NSE jog which would twitch in the current direction.
There is also some potential to cut plan this job so that you use a metric where you don't go to the closest point but the point that happens to be along the same directionality. In the cases when your jogging but the jog location is basically in the same line you could continue through there at speed and just start firing the laser on the otherside switching the jogging altogether. If code that did that was a thing optimizing for that would also be reasonable.
So if your next cut requires a turn around and are going the wrong direction you terminate with @NSE and either rapid move or start up at speed going the correct direction (since the rapid might actually be slower than too fast laser head). If you need to turn around and you're going the direction of your major axis you set during the startup you could apply an NSE raster to turn around. You wouldn't even need to do anything you'd just say you're going right, NSE, now you're going left and the turn around would apply a raster twitch turn around which is actually pretty reasonable at high speeds. And if you're going the same direction as the next segment you'd actually just skip that gap completely and never jump out of program mode. You'd maintain your speed and reach the other side of the gap which would need to be more-or-less in the same direction. Then anywhere where you'd apply a rapid change in direction of unknown thresholds or calculations you'd break that turn with some @NSE jogs.


[ISSUE #1535] Fix ha sync transfer timeout

What is the purpose of the change
fix HA sync transfer timeout, see issue 1535
Brief changelog
change the way waitting transfer
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.2%) to 50.418% when pulling 85a6cc1c8ee97fa6dade53971bc3ab5594707c5a on wqliang:develop_fixHaTimeout into 7c469fe949929ea039dfd8a6310db2f350ca316b on apache:develop.

LGTM


Upgrade Mac bots in CI to macOS Sonoma 14.5

Assuming macOS/iOS/Xcode update cadences are the same as they have been in previous years, it is likely that Xcode 16.0 will be released in September 2024, and will require the OS to be on macOS 14.5, which was released today.

Xcode 15 requires a Mac running macOS Ventura 13.5 or later.
Xcode 14 requires a Mac running macOS Monterey 12.5 or later.
Xcode 13 requires a Mac running macOS 11.3 or later.
Xcode 12 requires an Intel-based Mac running macOS Catalina 10.15.4 or later.

Currently, most of the CI bots are running 13.6.*.  If we update chromium and devicelab bots to macOS 14.5 now, it won't block Xcode and iOS updates in September.  It will also give us enough time to compensate for limited infrastructure team help.

@vashworth interested in your opinion about swapping to a spring Mac bot update cadence.

I think we can upgrade bots, but I think we may need to do again later to be able to upgrade to Xcode 16.0 official release.
For example, when Xcode 15 beta 1 was released, it required macOS 13.3. However, the official release required 13.5.
I think would probably be a better use of our time to upgrade a small subset of bots to macOS 14.5 so we can run tests against it and validate they pass before. And then when the beta comes out, we can run tests with the new Xcode beta on those bots as well. Then when the official Xcode 16 is released, do the rest of the bots.
If that sounds okay to you @jmagman I'll create a tracking github issue with steps

I think we may need to do again later to be able to upgrade to Xcode 16.0 official release.

For example, when Xcode 15 beta 1 was released, it required macOS 13.3. However, the official release required 13.5.

I'm hoping the GM non-beta Xcode 16.0 will required macOS 14.5 or lower, so we wouldn't need to upgrade again until next Spring.  Of course I don't know, but historically that seems like a safe bet from:

Xcode 15 requires a Mac running macOS Ventura 13.5 or later.
Xcode 14 requires a Mac running macOS Monterey 12.5 or later.
Xcode 13 requires a Mac running macOS 11.3 or later.
Xcode 12 requires an Intel-based Mac running macOS Catalina 10.15.4 or later.

Closing in favor of https://github.com/flutter/flutter/issues/148870.


⚠ File access has degraded performance

In 06473e3, File access (https://fyle.uk/file/fish) experienced degraded performance:

HTTP code: 503
Response time: 9453 ms

Resolved: File access performance has improved in 0ee6d9a after 8 minutes.


Allow Login to GitHub Container Registry for dependabot PRs

Context
Dependabot pull requests are failing to build as they are not included in the allow list for the github container registry credentials
eg: https://github.com/DFE-Digital/register-trainee-teachers/pull/2117
Changes proposed in this pull request
Initialise the registry credentials for pull requests created by dependabot.
Important business

~Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?~
~Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?~

Closing as there is an alternate approach in the works™


Try flink-crawler with crawler-commons 0.10 release candidate

From Julien:

I have pushed a RC for 0.10
The list of changes can be found here
Artifacts => https://oss.sonatype.org/content/repositories/comgithubcrawler-commons-1006
You can test it with Maven by inserting the following into your pom.xml

<repositories>
    <repository>
      <id>my-repo2</id>
      <name>your custom repo</name>
      <url>https://oss.sonatype.org/content/repositories/comgithubcrawler-commons-1006/</url>
    </repository>
  </repositories>

I have created a branch for this 154_crawlercommons-0.10 and updated the pom to use version 0.10. It seems to be working.

0.10 has been released and the artifact is available via the Maven central repo, so I have updated the pom to remove the sonatype repo. It is working.

Merged change to switch to 0.10 into master, so all good.


Fix: Create an interface from script

Don't call the MonoBehaviour's contructor
Don't call AdvertisePath on Awake, but on Start. If you attach a script to a GameObject, the Awake method is called, so you haven't the time to change the path of the interface.

Sorry for leaving this hanging. Looks OK to me and doesn't break anything. Can you provide a simple test case for how you discovered there was an issue? Were you working on input?

Hi,
The first thing is you can't use a constructor in a MonoBehaviour because Unity doesn't allow/recommand it.
Finally, I've created an InputManager for OSVR and I create some InterfaceGameObjectBase  at runtime. The InterfaceGameObjectBase  script requires the path of the interface but the AdvertisePath() method is called in the Awake method. So if I create a script at runtime, I don't have the time to pass the path and this method is called, resulting to a crash.
That's all ;-)

Yea, I haven't seen a monobehaviour constructor before. Will merge this in soon with the other updates. Thanks.

More informations here (for Unity 5.4 release)


Ideas for a relation embedder rewrite

We've had various discussions about what a "new" relation embedder might look like. We're not planning to work on it imminently; this is a ticket to capture some of those ideas in one place.

An idea to split the current app into a "relation builder" and a "relation embedder": https://wellcome.slack.com/archives/C02ANCYL90E/p1660114172418939

Changing how we store the collection path in Elasticsearch so we only store the prefix: https://wellcome.slack.com/archives/C02ANCYL90E/p1661263053581739