Is this Dev still alive? :)

Just wondering if the Dev of this is still around, or do we need to look at branching off for an update?

Yeah, dev is still alive.


Snapmaker Original

So I'm guessing there's no support for the first Snapmaker right? I wanted to use Cura but without settings it's impossible.

Print settings for Snapmaker Original is shipped with Cura (provided by our users).

Whenever I try to add a printer in Cura the original is the only one missing... Add printer

Print settings for Snapmaker Original is shipped with Cura (provided by our users).
Since original doesn't support network connection, so we didn't add more. If you have any requirements that can't be done with the shipped print settings, please share your needs with us. Hopefully we can find a way to support our original users.

Maybe for old version for Cura, in the 5.6 version the printer Original is not here :

There was previously this resource : https://manual.snapmaker.com/3d_printing/faq/snapmaker-profile-for-cura-and-simplify3d.html but it's not avalable anymore.
@parachvte could you share the process to configure the Original printer and make this possible to use.
Best


This dependency was not found in node_modules

I'm developing a WordPress plugin and I want to use laravel-mix for my js and css. WordPress adds jQuery automatically so I can use it inside my script.
In my main script I simply have:
(function( $ ) {
    'use strict';

    // ...
})( jQuery );

When I run npm run dev I got an error: This dependency was not found in node_modules: * jquery
I know that I have not jquery inside my node dependencies, but I do need that because WordPress already pulled it for me.
How can I fix the issue?
Thank you.

Can you add mix.autoload({}) to your webpack.mix.js file and let me know if that changes things?

@JeffreyWay It works! 👍 Thank you.


[CARBONDATA-3441] Aggregate queries are failing on Reading from Hive

Problem:
Aggregate queries are failing on Reading from Hive, as the table_name, db_name are not set to the conf.
Solution:
Set table_name, db_name to the conf and handle NullPointerException.

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[X] Testing done
Added test case to HiveExample

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3598/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11872/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3806/

LGTM, Please try to add testcase if possible.

LGTM, Please try to add testcase if possible.

Test case added

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3624/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11898/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3831/

retest this please

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11905/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3632/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3838/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11911/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3843/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3686/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11961/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3896/

LGTM


Build from crates.io fails

Looks to be a semver problem in the deps?
(doesnt occur when building from git)
   Compiling harper-ls v0.8.1
error[E0308]: `match` arms have incompatible types
  --> /home/jayvdb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/harper-ls-0.8.1/src/tree_sitter_parser.rs:30:24
   |
18 |           let language = match file_extension {
   |  ________________________-
19 | |             "rs" => tree_sitter_rust::language(),
20 | |             "tsx" => tree_sitter_typescript::language_tsx(),
21 | |             "ts" => tree_sitter_typescript::language_typescript(),
...  |
29 | |             "rb" => tree_sitter_ruby::language(),
   | |                     ---------------------------- this and all prior arms are found to be of type `tree_sitter::Language`
30 | |             "swift" => tree_sitter_swift::language(),
   | |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `tree_sitter::Language`, found a different `tree_sitter::Language`
...  |
34 | |             _ => return None
35 | |         };
   | |_________- `match` arms have incompatible types
   |
   = note: `tree_sitter::Language` and `tree_sitter::Language` have similar names, but are actually distinct types
note: `tree_sitter::Language` is defined in crate `tree_sitter`
  --> /home/jayvdb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tree-sitter-0.22.1/binding_rust/lib.rs:55:1
   |
55 | pub struct Language(*const ffi::TSLanguage);
   | ^^^^^^^^^^^^^^^^^^^
note: `tree_sitter::Language` is defined in crate `tree_sitter`
  --> /home/jayvdb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tree-sitter-0.20.10/binding_rust/lib.rs:43:1
   |
43 | pub struct Language(*const ffi::TSLanguage);
   | ^^^^^^^^^^^^^^^^^^^
   = note: perhaps two different versions of crate `tree_sitter` are being used?

Thank you for bringing this to me attention. I've just pushed a release to crates.io that fixes this issue. Feel free to reopen if this continues to be an issue.


fix: include the sidebar page parameter in the home page

Following up on #709. It seems that the home page is missing the sidebar parameter.

Related issue: #708

Thanks a lot. I forgot that.


Added dark mode

I have added a toggler which makes the website into dark mode.

show the effects

Thanks for your valuable contribution.
Don't forget to star the repo.


Don't add default build deps onto specified build deps when PEP517 bu…

…ild-backend is missing.
fixes #213
Pull Request Check List

[*] A news fragment is added in news/ describing what is new.
[ ] Test cases added for changed code.

Describe what you have changed in this PR.

Thanks 🎉


Models: Navigator isn't navigating

ModelsFoo.zip
Running this project i'm expecting to see "foooooo" on the screen (ClassesPage should have been instantiated).
Unless I've done a mistake or misunderstood how the system works.

There isn't yet a default path on model objects. It's something that still needs to be added. You'll have to manually add a this.$path = "ClassesPage" in the ClassesPage constructor.
WE had an approach where this worked before, but need to change it. Navigation needs a function it can call to get the classname of the model object. Once we have that we can add this feature back.

i though it used the JS class name to instantiate the correct template..? Has this changed?

It will use the ClassName, that is the intent. The mechanism by which that works is mid-progress though now -- it was changed and the change didn't quite complete.
I need a function I can call from PagesMap.GetObjectPath in RouterPage.uno

Does this have an issue somewhere? It doesn't seem to be reflected in the documentation.

like, is this something that will be fixed? or is $path the way to go for the foreseeable future?

It must be fixed before release. I don't know if I added an issue -- probably not, as it was meant to be a quick change. Please add an issue and mark it high priority.  You can refer to the code I mentioned, somebody can fix it while I'm gone next week then.

@mortoray : this was fixed an already merged, right?

yes


0.9.4 log spam

What version of ViaVersion are you using? Type /ver viaversion
0.9.4
What version of Spigot are you using? Type /ver
http://prntscr.com/bjslp3
What plugins are you using? Type /plugins
http://prntscr.com/bjsltk
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
LilyPad
How does this error happen? login? Using an item?
Just randomly spamming my console
Is there an error in the console? Use pastebin.com. Is there a kick message?
http://pastebin.com/qAsP1y0y

One of your plugins is sending invalid metadata. You can disable this warning in the ViaVersion config by changing the 'suppress-metadata-errors' value to true.


Zhiyil/some changes

Checklist:

[x] modify config for ckpt so that last ckpt is saved
[x] fix a few bugs about metrics in code and config
[x] add validation only script
[x] add baseline configs for small dataset
[x] largemix bug fixes
[x] largemix configs: multi-task and single-task

All the changes look good. But there are way too many config files, and they're all copies of each other. This will polute the Repo, especially since it's now public. It is also prone to copy-paste errors and require all the files to change every time there's a code change.
I would request to keep only 1 full config file. For the others, create only a very simple configuration that will overwrite the specific path of the Yaml.
You can use the function merge_dicts and modify it with the option to not raise an error if a value already exists.
Alternatively, you can define bash files with hydra to manage changes between runs.

Yeah that's a very good point. Actually we don't have any results for the largemix and those single tasks yet, I wonder if you are happy if we now only show the toxymix multitask baseline and largemix multitask configs so that people could reproduce the toymix baseline results. For the single task ones, we could leave them out at the moment and add the configs in using the merg_dict method you mentioned above once the results are ready.

Same changes here: https://github.com/datamol-io/graphium/pull/362


added ambient occlusion

Any update on this getting merged? I've been using the branch and it's awesome to have ao with this lib.

By the way @Shirakawa42 the change in src/simple.rs completely breaks meshing for the simple mesh merging strategy. Any plans on implementing ao for simple meshes?

If you don't end up implementing ao for simple voxel merging in the line you commented out just set the ao to be [0; 4]

I have a hacky implementation of ao for the simple mesher here: https://github.com/Vixeliz/HackyBlockMeshAo. its in the block-mesh-rs folder. Its basically just using your calculate ao function slightly modified. It needs to be moved to a function though and a few other things but as a proof of concept it works


Unable to download Forex data for local backtesting

Expected Behavior
Documentation here suggests Forex data (Oanda) can be downloaded from QC Data Library.
Actual Behavior
Fails with error message:
Error: There is no data vendor that sells 'forex/oanda/hour/eurusd.zip'

Reproducing
(Interactive mode)
$ lean data download
$ 1
$ 5
$ 4
$ EURUSD

(Non-interactive mode)
$ lean data download --product "Forex" --organization "MyOrg" --resolution "Hour" --ticker "EURUSD"

System
Lean CLI 1.0.22

Hi @adamw96,
We pushed some changes to the API to fix this issue. If you re-run the command it should work.

Great, confirmed working v1.0.23


Device List empty in node-red

Hi, I have devices set up and working but i am not able to set up new flows because the device list is not populated. is this an issue with the server or something on my side?  i can see devices on the website fine... thanks

Have you hit the refresh button next to the list?
Also is there anything in the Node-RED logs when you hit that button (not the debug sidebar the actual node-red console log)

Also some basic information about your setup would be helpful

NodeJS version
Node-RED version
Node Version
Environment (OS, docker, HA)?

Thanks, I have tried refreshing with the button
I don't see anything coming up in the log when pressing the refresh button either
I'm running on a Pi, node red version 0.20.7
node version 0.0.10
i dont know how to find node js version sorry
updated to node version 0.0.14 and the problem persists

Have you changed your password between setting up the old devices and the new ones?
You can find the NodeJS version by running node --version
Latest version of the node is 0.0.15 (I had forgotten to update flows.nodered.org).
Node-RED will log if there is an error when you push the refresh button but it might not be immediate.
What is the username you have for the service so I can check the logs for when it looks up the device list?

nodejs v8.16.1
username: niblett
i have updated to 0.0.15 now thanks. still nothing in the log and the same issue.
thanks for looking into this for me

The logs so no sign of you even trying to connect to the service to pull the device list down which means something very strange is going on.
Just to prove it is possible to retrieve the list from your machine,  please try and run the following command:
curl<EMAIL_ADDRESS>
replace password with your password
Also please supply the output of lsb_release -a

Actually I think I might know what the problem is.
NodeJS version v8.16.1 is too old. (The current LTS version is 16.x)
NodeJS has a built in SSL certificate CA list, and the CA certificate for the Certificate Authority I use for the service changed recently so the version in the baked in CA list will have expired so it can no longer connect to the server.
You REALLY need to upgrade NodeJS (and you should really update Node-RED as well).
As a work around you can try exporting the NODE_TLS_REJECT_UNAUTHORIZED=0 environment variable (beware, this totally disables all certificate checking.

Thank you. I will do an update on both in the next day or so and report back.

Hi, sorry it has been a while but i finally got on to updating everything and the problem persists unfortunately:
current:
nodejs v10.24.0
nodered v1.3.4
lsb_release -a gives the following:
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
curl<EMAIL_ADDRESS>pulls the device list etc so thats clearly working
still nothing in the log
something i may have overlooked before is that the refresh button is not actually clickable next to the device list. the mouse cursor does not change to a hand...

Why/how did you only upgrade to Nodejs v10.24.0 and Node-RED v1.3.4?
As I said latest LTS NodeJS is v16.x and Node-RED is at v2.2.2. The Node-RED install script would have installed script would have installed both of these. You REALLY need to go to a supported version of NodeJS, v10.x is also out of support as can be seen here:
https://nodejs.org/en/about/releases/
At the very least you should be aiming for NodeJS v14.x
The mouse cursor doesn't have to change, the button is clickable


Copy maps before entering Transform stages

Fixes #234

Opening as draft because I haven't tested yet.
I'm only copying maps before Transform, because it's really where we can assume maps will be written, but to be honest I think it would be better to copy between every stage.
cc @eranra @OlivierCazade @mariomac @KalmanMeth what do you think ; does it seem like the right place to do it?

Codecov Report

Merging #239 (a34952f) into main (4b7265e) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #239      +/-   ##
==========================================
+ Coverage   61.22%   61.28%   +0.06%
==========================================
  Files          67       67
  Lines        3863     3869       +6
==========================================
+ Hits         2365     2371       +6
  Misses       1348     1348
  Partials      150      150

Flag
Coverage Δ

unittests
61.28% <100.00%> (+0.06%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/config/generic_map.go
100.00% <100.00%> (ø)

pkg/pipeline/pipeline_builder.go
64.47% <100.00%> (ø)

Continue to review full report at Codecov.

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

I think the copy should be performed by exactly those stages that make changes to the configMap. Each transform receives configMaps, and should treat them as read-only. If any change is made, then the stage should either make a copy or should create its own new array of configMaps.

I agree with Kalman proposal. For performances, we should avoid as much unnecessary copy as possible.

The way the pipeline library works, only when a stage finishes processing a map, it forwards it to the next stage. So in principle we should be sure that only one stage/goroutine has the map at the same time.
However, I was not considering the scenario in which a stage sends the map to two stages, and one of the stages modify the contents. E.g. the ingester sends the map to the transformer and to a stdout logger. This is the only scenario in which I could imagine we could have this kind of concurrent modification.
I guess that for now might be Ok, and for a further optimization, we could improve the pipeline builder to inject a cloning node only if this kind of path forks happen. E.g. normally it would build a map like:
ingest/decode --> transform --> write

But if it detects a fork where one of the destination nodes transform the path, inject a cloner like:
ingest/decode --> stdout_log
              \-> clone --> transform --> write

Closing in favor of #240


[jaeger-v2] Do away with storage.ArchiveFactory

Per comment https://github.com/jaegertracing/jaeger/pull/5152/files#r1501916983
We need to get rid of storage.ArchiveFactory interface because it is conceptually meaningless - archive storage is just a storage that implements SpanStorage interface. It should be the same thing with Factory, just have a storage.Factory that in context can be interpreted as primary or archive. We unnecessarily bundle these two.

I would like to work on this.

Can I work on this issue?

Can I work on this issue?

I am gonna close this as I don't think it's necessary given how v2 storage is evolving. @james-ryans is working on defining a new storage APIs for v2 where there won't be archive storage as an explicit interface.


Statically link binary on Windows MSVC

Allow running prebuilt binary without Microsoft VC++ redistributable

Confirmed that it works as expected.


Only export by default

Hello, i want to use your package for create documentation for a library i have.
Is is possible to set export only by default? Or just generate export stuff only.
Thanks for the job and have a good day

Hello @nicolasgere, can you explain what you mean by "set export only by default"?

@aciccarello i dont want to provide a docs for the internal stuff of the library, just the exported one

@nicolasgere I beleive --excludeNotExported option is what you are looking for. I could not find any mentioning about it in the typedoc docs though so probably this is a documentation issue.

a parameter which not exclude not exported stuff, but check this checkbox by default would be also very helpful

It seems like several things are being discussed in this issue:

The OP is probably interested in the idea of adding a "library" mode which is discussed in #639
If there are issues with the --excludeNotExported option, a new issue should be opened to identify that issue
The easiest way to set that checkbox by default would be to create a custom theme


runc: 1.0.0 -> 1.0.1

Motivation for this change
https://github.com/opencontainers/runc/releases/tag/v1.0.1
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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

[x] Fits CONTRIBUTING.md.

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

9 packages built:

buildah
cri-o
hci
hercules-ci-agent
ignite
k3s
nvidia-podman
podman
runc

Result of nixpkgs-review pr 130379 at cfe4ba2b run on x86_64-linux 1

8 packages built successfully:

buildah
cri-o
hercules-ci-agent
ignite
k3s
nvidia-podman
podman
runc

1 suggestion:

warning: unused-argument
Unused argument: apparmor-parser.
Near pkgs/applications/virtualization/runc/default.nix:9:3:
  |
9 | , apparmor-parser
  |   ^


Recursive build_call_graph does not work

A "nice to have" feature would be the ability for a recursive build_call_graph decomposition to solve for symbolic recurrence relations if solvable.

the argument for show_call_graph is not a bloq, it's the graph returned by bloq.call_graph (e.g. https://qualtran.readthedocs.io/en/latest/bloqs/qft/two_bit_ffft.html#call-graph), if that helps.

Although I'm fairly certain this still won't work as written.

Thanks that was the issue, managed to get it working even with symbolics. @tanujkhattar had mentioned it might be possible to use sympy's symbolic solvers to try and see if a recurrence relation could be solved to give an estimate for the resources used if the recurrence is solvable.

cool


Remove Duplicate "Editor Plugins" Section

Editor Plugins was repeated a second time. with identical content

 You should sign our Contributor License Agreement in order to get your pull request merged.

Thank you so much!
Merged as 1469ce0 (master) and a08ac13 (v0.15.docs).


Add LD_TRUST_TOKEN environment variable

Used for adding a trust_token query param to Mercurial URLs, which Language Depot will use to determine that the request came from the Language Forge server. (IP address checking doesn't work well with Kubernetes deployments, where the IP address can change frequently).
This is https://github.com/sillsdev/LfMerge/pull/126 targeted at fieldworks8-master rather than master.

This change is

Merging without waiting for approval since #126 was already approved.


Stacks - receipt.sh script - multi arch support

Summary

This PR extends receipts.sh script functionality by adding below features:

Multi arch support, is able to produce sbom files for any architecture that is mentioned on the manifests.json of a .oci image. The implementation is based on the current jammy-tiny-stack receipts script https://github.com/paketo-buildpacks/jammy-tiny-stack/blob/main/scripts/receipts.sh
It does not change any of the current functionality for single architectures, and even the output names of the receipts for the amd64 remain the same to keep backwards compatibility with existing workflows.
Using scan command on syft, as packages command is deprecated (see below warning message)

Command "packages" is deprecated, use `syft scan` instead
Flag --file has been deprecated, use: --output FORMAT=PATH

Adds support for ubi-base-stack, as jammy-tiny-stack receipts.sh script does not set proper permissions in case the stacks path is different.

Use Cases

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@ForestEckhardt


Add ReaderAdvice and IOAdvice modules.

SimpleAdvice is not so simple after all (#25) because it relies on coerce and sometimes, especially when there are polymorphic functions afoot, the coercions don't work.
The alternative is using DepT as your monad with the main Advice module. But DepT is a bit weird compared to ReaderT and IO. Introducing it only for the purpose of using advices is overkill.
So let's bite the bullet and write specific modules which advise monadic functions living in ReaderT and IO.
A possible implementation of the ReaderAdvice can be found here.

added


WIP: Develop

Pull Request Test Coverage Report for Build 1233

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.694%

Totals

Change from base Build 1220:
0.0%

Covered Lines:
2096

Relevant Lines:
2613

💛  - Coveralls


Помогите пожалуйста с проблемой!

Godot version
3.5
System information
Windows 10
Issue description
Я хотел повторить ролик на ютубе где он создает 2Д платформер за 10 минут.
Ссылка на ролик: https://www.youtube.com/watch?v=xFEKIWpd0sU
На просмотре 1:34 возникли проблемы.
Автор видео переносит файл .tres в Tile set. Когда я это повторял у меня выдало ПРЕДУПРЕЖДЕНИЕ где написано:
"Выбранные ресурсы (MeshLibrary) не соответствуют типам, ожидаемым для данного свойства (TileSet)."
Что делать?
Steps to reproduce

Minimal reproduction project

Please make reports in English, use translation software if needed, English is the official language of these forums

Translation:
Title: Please help with the problem!
Issue description:
I wanted to replicate a YouTube video where he creates a 2D platformer in 10 minutes.
Link to the video: https://www.youtube.com/watch?v=xFEKIWpd0sU
When watching at 1:34 there was a problem.
The author of the video moves the .tres file to Tile Set. When I repeated this I got a WARNING where it says:
"The selected resource (MeshLibrary) does not match any type expected for this property (TileSet)."
What to do?

@N3TCX Please reopen the issue in English, and make sure to follow the guidelines that the bug report template provides.

Or edit the issue, you can change the text and title

It would be helpful if you attached the zip with your project as Minimal Reproduction Project instead of repeating the screenshot.

This tracker is for reporting bugs in the engine, not for tech support. Please use Community channels to ask for help. See also the User Groups page, which lists Russian local groups too.
As for the error, I think you have created a resource of the wrong type MeshLibrary, while TileSet is expected.

Ah now I noticed the resource icon. Yeah, this is a MeshLibrary. You used wrong type and the error says so correctly.


please add option to export/import data as json

add exporting channels and watch status, tags etc basically all data you put in the app as json and also importing, so if i reinstall or so, my data doesen't get lost

That would be nice to have. Fwiw, settings and data is stored in <App data folder>/space.kasper.kadium


Dealing with exceptions in Realm

How to recover from Realm exceptions?
Imagine the case: you have found a great playlist and listening to track #31. As a user you have performed some subsequent actions which formes the current state of the app. Сoincidentally somewhere else a small object was added to Realm with a duplicate key.. Boom. Crash. Start over. Moderate alert error would be so much better.
Provided realm docs and examples give no clue on how to handle exceptions in production environment. How do I know which methods can throw an exception? Should I wrap each realm call in @try-catch block? Examining the source code shows that there are plenty of vulnerable exceptions, which might not be discovered when an application is being created can pop up in release builds. Even -realmWithPath:error can throw an exception Realm at path already opened.
An example of the API would be nice to have:
[realm beginWriteTransaction];
BOOL added = [realm addObject:object error:&error]; // does NOT trigger an exception under no circumstances
if (!added) {
  // e.g. error = duplicate content, no default value etc
  // report error to some remote service
}
[realm commitWriteTransaction];

Background
Please read Apple's Exception Programming Topics IMPORTANT block, it makes total sence: most of the current RLMExceptions should be catched at the top level of the library and translated them into an appropriate return code or state.

Instead of exceptions, error objects (NSError) and the Cocoa error-delivery mechanism are the recommended way to communicate expected errors in Cocoa applications.

More references below:
Programming with Objective-C • Dealing With Errors

When you’re writing code with Objective-C, exceptions are used solely for programmer errors, like out-of-bounds array access or invalid method arguments. These are the problems that you should find and fix during testing before you ship your app ... All other errors are represented by instances of the NSError class".

Apple's Error Handling Programming Guide
StackOverflow NSError vs NSException StackOverflow Errors vs Exceptions
How others handle it:
FMBD: any method execution returns bool + static last database error
CoreData (reference): errors pop up on

initialization phase: -addPersistentStoreWithType::error:
migration: -migrateStoreFromURL::error:
save and fetch: -save:error -executeFetchRequest:error

I am suprised nobody addressed the problem yet. Realm is such a great framework, but it is just being fragile sometimes. Remember that UITableView's NSInternalInconsistencyException?

Invalid update: invalid number of rows in section 0. The number of rows...

Doesn't it feel insane that the some minor animation stops user experience and crashes the app?
Realm maintainers, please consider the concept above. At least we should also make up basic guidelines on exception handling.

We do strive to follow Apple's guidelines that you quoted: exceptions are used only to indicate misuse of the API, and NSError is used for runtime errors. We strongly discourage trying to catch and handle any exceptions thrown by Realm, and if you find a scenario where it is not possible to avoid having Realm thrown an exception then that is a bug. The two exceptions to this are the convenience overloads of the RLMRealm factory methods which do not take an error out parameter, and a few methods which could potentially fail due to a memory allocation failure but do not have a good way to supply an error parameter (such as the generated property setters for persisted objects).
If you want to add an object without it throwing an exception if an object with that primary key already exists, either use addOrUpdate: if you simply want to replace the existing object, or use objectForPrimaryKey: to check for the object existing first. There's no risk of a race condition where another thread creates the object between the check and when you call addObject: because only one thread can be in a write transaction at a time.


Update nearby.html

The changes made to the HTML page focus on improving both the user experience and the code's maintainability. First, SEO optimization was applied by adding meta description and keywords to make the page more discoverable in search engines. The navigation bar was fixed, specifically correcting the link to the "Nearby" section and ensuring all menu items work as intended. The website's logo was resized to be more responsive, adjusting its appearance across different screen sizes. Additionally, the hospital cards were enhanced with a smoother hover effect, providing a subtle animation when users interact with them, making the design more engaging. The footer was also improved with better padding and alignment to create a more balanced and visually appealing look. Finally, the HTML and CSS were reorganized, with styling adjustments moved into a dedicated section for cleaner code and easier future maintenance.

I’ve made the requested changes, including SEO optimization, navigation link fix, improved responsiveness for the logo, and enhanced hover effects on the hospital cards. The footer has also been refined for better alignment and overall aesthetics. Additionally, I’ve cleaned up the code structure for better readability and maintainability.
Could you please review and merge this as soon as possible? Let me know if any further adjustments are needed.


Generating CSV file upon GET request with appropriate headers

I will gladly help to implement this one and I'd like to know if it's a desirable feature.
My use case is: I want to make some query results available as a CSV for my users, so that they can use this data in spreadsheets.
Possible solutions: I could bring the data in JSON format from PostgREST and assemble a CSV in the browser. But it seems that we could benefit from PostgreSQL amazing performance when executing COPY queries to generate a CSV in the backend. Besides the client-side solution impedes interoperability with other clients that might expect a CSV file.
My proposal: We use the content type provided in the request when executing a GET (this is also useful for a POST but stating with GET sounds easier). If the content type matches text/csv we use the same where clause generated for the JSON response but plug it in a COPY statement.
@begriffs I've noticed you've opened this issue: https://github.com/nikita-volkov/hasql/issues/1 so I guess that there are changes in hasql-postgres needed before anyone can implement this in PostgREST right?

This is an excellent feature, I'd love your help with it. Your approach of using the Accept header in the request sounds perfect.
The issue in Hasql with copy mode came up when I was trying to do bulk inserts. Bulk reads may or may not be easier. For the inserts I ultimately made a workaround by using an insert command with multiple values (suboptimal because not as fast as copy).

I would also like this feature with a slight difference.  I would rather not have users download CSV files and import them.  Instead setting content type to text/csv and returning comma separated rows instead of JSON.  This way I can call the services from excel and return directly into a workbook utilizing excel's background refresh capabilities.

@begriffs unfortunately I've been trying to implement COPY support in hasql-postgres without success. So I was wondering if you would be willing to integrate a PR with this feature using a SELECT statement.


Move builds from TeamCity to AppVeyor

@jonorossi Please confirm that this is something that we can help now.
Related discussion: https://github.com/castleproject/Core/issues/241#issuecomment-294167564
part of #145.

I would fork the project and get something basic working in VS2017 supporting NET45 using a new solution.
Use side-by-side csproj files like I did in Core. The only one I would leave as-is, is the Castle.Facilities.WcfIntegration.Demo.
We should theoretically be able to get a build going in AppVeyor that passes supporting this framework moniker with tests passing without breaking anything in teamcity.
This set's us up nicely to have a FEATURE_BUILD_FLAG discussion for Windsor once we start targetting netstandard1.3, like so https://github.com/castleproject/Core#conditional-compilation-symbols.

I've just created a refactor-build in the Windsor repo to allow the same.

Hi @jeremymeng
Just an update on my work in Castle Core.
@jonorossi - has approved my latest changes in the https://github.com/castleproject/Core/commits/refactor-build branch.
We now have an approved approached for net45 on appveyor. I am busy upgrading NUnit and then I have to start targetting netcoreapp1.0 in Castle Core tests. This is the bulk of the work left, I suspect implementing TravisCI should be the easy part.
If you have any questions please fire away.

What is the plan for the three WcfIntegration projects? Are they going to be removed? @fir3pho3nixx you mentioned about not building Castle.Facilities.WcfIntegration.Demo, however the project Castle.Facilities.WcfIntegration.Tests depends on it. Should the tests that depend on Castle.Facilities.WcfIntegration.Demo be pulled out?
Also I have another question; when getting to build on AppVeyor, how do I know if the TeamCity build was broken or not?

What is the plan for the three WcfIntegration projects? Are they going to be removed?

I'm not sure why @fir3pho3nixx said leave the WCF Demo one as is, it shouldn't be any work to get it building on .NET 4.5 using the new tooling, and it looks like you've already done the work now. I'd like to see the existing WCF projects go across and we can look at reducing them later, however obviously no one is expecting any .NET Core/Standard support for those projects.

Also I have another question; when getting to build on AppVeyor, how do I know if the TeamCity build was broken or not?

We haven't bothered setting up a TeamCity build for the refactor-build branch in Castle Core, and I know some of those embedded resource changes will break the TeamCity build. I don't think it really matters, once we are happy with the new build I assume we'll delete the old files and rename the new csproj files before merging; we've always got git tags for old releases. @fir3pho3nixx is that what you were thinking?

Sorry guys, all I meant was don't upgrade it to the new vs2017 multi targeting format.

@jonorossi - happy to go with a hard cut over for this. Running tests for both takes twice the amount of time.

@jonorossi I've tried to update the Castle.Core version referenced by Windsor from 3.3.0 to 4.0.0, and many tests fail. Are there major breaking changes between these two versions I should be aware of?

I've tried to update the Castle.Core version referenced by Windsor from 3.3.0 to 4.0.0, and many tests fail. Are there major breaking changes between these two versions I should be aware of?

There are some breaking API changes especially around things that were in Castle.Core.Internal that Windsor really shouldn't be using (reason for #163) which is one of the reasons for the major version number change, however generally I don't expect any major functional breaking changes.
Maybe it is best to get these build changes done with Castle Core 3.3.0 as a like-for-like with master's old build scripts, then do the dependency upgrade?

@jonorossi @fir3pho3nixx What is needed at this time on Windsor with regard to Travis CI?

What is needed at this time on Windsor with regard to Travis CI?

I'd say nothing. We currently don't build/test Windsor on Mono with TeamCity so no need to start under this work, it sounds like it'll be much easier in a month or two. It is important for Castle Core because of the wide use of Castle DynamicProxy.

Edited issue title to reflect no need for Travis at the moment.

What's left to do:

Get unit tests showing in "Tests" tab
Versioning
NuGet packaging

This is what the "Pack" configuration on TeamCity does for Windsor, we need to work out what we need and how to do the same hopefully without all the mess.
Artifact Dependencies: Castle.Windsor-NET45-%dep.bt132.build.counter%.zip!/** => .\build\NET45\NET45-Release\pkg -:Castle.Windsor-NET45-%dep.bt132.build.counter%.zip!/bin/*.Demo.*
Parameters:

CastleCoreVersion=1.0.1

text description='Castle Core Version to depend upon' display='hidden' label='Castle Core Version' regexp='\d+\.\d+\.\d+(.+)?' validationMode='regex'

CurrentYear=2000

text description='Copyright Year' display='hidden' label='Copyright Year' regexp='20\d\d' validationMode='regex'

ReleaseVersion=1.0.0

text description='Release version number' display='hidden' label='Version' regexp='\d+\.\d+\.\d+(.+)?' validationMode='regex'

env.release_build=false

checkbox checkedValue='true' description='whether this build is intended for public release (i.e. controls whether a prerelease package is generated)' display='normal' label='release build' uncheckedValue='false'

Build Steps:

PowerShell buildscripts\Get-NuGetVars.ps1
NuGet Pack: "Pack Assembly Packages"

Specification files:

buildscripts/Castle.EventWiringFacility.nuspec
buildscripts/Castle.FactorySupportFacility.nuspec
buildscripts/Castle.LoggingFacility.nuspec
buildscripts/Castle.SynchronizeFacility.nuspec
buildscripts/Castle.WcfIntegrationFacility.nuspec
buildscripts/Castle.Windsor.nuspec

Version: %ReleaseVersion%
Properties

Configuration=Release
CastleWindsorVersion=%ReleaseVersion%
CastleCoreVersion=%CastleCoreVersion%
CurrentYear=%CurrentYear%

NuGet Pack: "Pack Dependency-Only Packages"

Specification files

buildscripts/Castle.Windsor-log4net.nuspec
buildscripts/Castle.Windsor-NLog.nuspec

Version: %ReleaseVersion%
Properties

Configuration=Release
CastleWindsorVersion=%ReleaseVersion%
CastleCoreVersion=%CastleCoreVersion%
CurrentYear=%CurrentYear%

Artifacts:

build/nuget/**
BreakingChanges.txt => Castle.Windsor.%ReleaseVersion%.zip
Changes.txt => Castle.Windsor.%ReleaseVersion%.zip
License.txt => Castle.Windsor.%ReleaseVersion%.zip
buildscripts/ASL - Apache Software Foundation License.txt => Castle.Windsor.%ReleaseVersion%.zip
buildscripts/readme.txt => Castle.Windsor.%ReleaseVersion%.zip
build/NET45/NET45-Release/pkg/bin/Castle.Facilities.* => Castle.Windsor.%ReleaseVersion%.zip!/lib/net45
build/NET45/NET45-Release/pkg/bin/Castle.Windsor.* => Castle.Windsor.%ReleaseVersion%.zip!/lib/net45

A whole bunch of the packaging can be simplified now that we have a single "job" building and packaging, and we can transition from manual nuspecs to the csproj file, hopefully keeping common things in a common file.
I don't think we need the ability to specify the Castle Core version, it should be defined in source control and much of the other manual packaging stuff will be taken care of by MSBuild generating the nupkg.

Great work @alinapopa. Do you need any more info to progress with the remaining items? Can we package Windsor using the .NET CLI?

Change after_build to on_finish
Versioning - control the version number from one place
NuGet packaging - build a nupkg with the .NET 4.5 .dll, .pdb and .xml

@jonorossi under the buildscripts folder there are nuspec files for Castle.Windsor-log4net and Castle.Windsor-NLog. There are no projects in the solution with these names. What are they created from?

Also @jonorossi I am getting a warning for project Castle.Facilities.WcfIntegration that the description is too long:

MSBuild\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets(104,5): warning : Issue found with package 'Castle.WcfIntegrationFacility'.
MSBuild\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets(104,5): warning : Issue: Consider providing Summary text.
MSBuild\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets(104,5): warning : Description: The Description text is long but the Summary text is empty. This means the Description text will be truncated in the 'Manage NuGet Packages' dialog.
MSBuild\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets(104,5): warning : Solution: Provide a brief summary of the package in the Summary field.

And I can't move it in the Summary field because the Summary field is no longer supported
https://docs.microsoft.com/en-us/nuget/schema/msbuild-targets
Please can you reword the description to make it shorter?
Thanks!

under the buildscripts folder there are nuspec files for Castle.Windsor-log4net and Castle.Windsor-NLog. There are no projects in the solution with these names. What are they created from?

As mentioned in https://github.com/castleproject/Windsor/issues/220#issuecomment-297221266 these are "Dependency-Only Packages". I don't know exactly the reason for them, and git history and issues isn't providing much info, I assume they are there to ensure when you install the logging facility the right version of Castle.Core-{log4net,NLog} gets installed to match Castle.Core, but that would only work if you installed that package rather than the logging facility directly, so I guess there usefulness might not be all that great however they are still used by quite a few people looking at nuget.org so we'll want to keep them for now.

I am getting a warning for project Castle.Facilities.WcfIntegration that the description is too long

It looks like the threshold is 300 characters and we've got 401 in the description. I'm happy for the description to get truncated when it is show as the summary, and for the warning to stay for now.

@alinapopa - Your input helped quite a bit when it came to translating the old nuspec properties to the common.props for Castle.Core whilst packaging NuGets. Many thanks!
I have submitted my last PR for tag based publishing Castle.Core using AppVeyor: https://github.com/castleproject/Core/pull/259
There is still a pending discussion about clean up: https://github.com/castleproject/Core/issues/241
Anything I can help out with down here?

This item is pretty much done (the only thing that should be added is the CLSCompliant attribute on the assemblies; using the latest test adapter may not be a good idea at this time because there are some issues with it).
I think it is a good time to discuss what are the next items, to make progress toward porting Windsor to .NET Core.

@alinapopa - How far away are we from publishing the nugets using appveyor?
Once this is done, we are ready to start implementing the build feature symbols like in Core. FEATURE_APPDOMAIN, FEATURE_SERIALIZATION, FEATURE_SECURITY_PERMISSIONS and FEATURE_REMOTING are the big ones I can think of just off the top of my head. This will help us unlock a a version of Windsor that targets netstandard.

@fir3pho3nixx

How far away are we from publishing the nugets using appveyor?

We're three open PR's away:
#233 , #232 , #231

I am free now.
We should try expedite a release of https://github.com/castleproject/Windsor/pull/235.
Can I close https://github.com/castleproject/Windsor/pull/233 and take this one? I have just finished doing it in Castle Core.

@jonorossi - Can we create a milestone with the version number in it (for releasing https://github.com/castleproject/Windsor/pull/235)? I can then tag this issue with that milestone. Can we also add a label to indicate progression from "up for grabs" to "assigned" or something similar? This would be very handy for knowing what is outstanding.

@fir3pho3nixx

Can I close #233 and take this one?

Yes that sounds like a good idea

@jonorossi - Can we change this issue to include TravisCI, this is a solved problem in Castle Core? I plan to implement it here.

Can we create a milestone with the version number in it

Since this version also includes dropping Silverlight, .NET 3.5 and 4.0 support what version number do you want? At first I was going to just go 3.5, but now thinking this is 4.0 and .NET Core support can be in 4.1?

Can we also add a label to indicate progression from "up for grabs" to "assigned" or something similar?

I would think removing the "up-for-grabs" label and assigning the issue to yourself would be the best indication that you are working on it? "up-for-grabs" is the label used for new contributors to the project that would be a good starting point, not just anything that needs to be done. i.e. following the convention many hundreds of projects have been doing over the last 5 or so year, and the web site.

Can we change this issue to include TravisCI, this is a solved problem in Castle Core? I plan to implement it here.

There is likely a heap of failing unit tests on Mono so not just as simple as adding a travis.yml file, I'd prefer if we delayed it to another task to get this work done so we can get the next release out. Thoughts?

Going with version 4.0 sounds perfect.
I mistakenly thought we were good on the mono side, if this is the case, you are right ... let's hold off for now.
Thanks for explaining how the labels work.
I will move on to getting the tag based deployments working after I have resolved the changes needed for my PR in Castle Core.

@jonorossi I think the removal of System.Security.AllowPartiallyTrustedCallers assembly attribute from Windsor should be listed under "Breaking Changes"

I think the removal of System.Security.AllowPartiallyTrustedCallers assembly attribute from Windsor should be listed under "Breaking Changes"

Responded by creating #248.

Just double checking, we are not supporting net35 || net40 for this right?

IMHO - It is a shame we are not harmonising our framework support with castle core here.

Status Update: Have 2 PR's in play https://github.com/castleproject/Windsor/pull/259 && https://github.com/castleproject/Windsor/pull/260
I am getting new internet next week, so hopefully I can pick up the pace soon! :)

Just double checking, we are not supporting net35 || net40 for this right?
IMHO - It is a shame we are not harmonising our framework support with castle core here.

I'm unsure exactly what you are asking. If you want to also support .NET 3.5/4.0 in Windsor just as 3.4 does I don't mind, but obviously it is additional work. We really should keep .NET 3.5/4.0 support in Castle Core for a bit longer.

The conditional compilation symbols for building on 3.5 and 4.0 were removed #185 #195 #197

The conditional compilation symbols for building on 3.5 and 4.0 were removed #185 #195 #197

Thanks, yer we did explicitly make the decision in #185, it wasn't just an off the cuff decision. I think we should continue with .NET 4.5+ only, really don't need that extra work.

@jonorossi not sure if you are checking your mail, my internet is fixed now. Do you think we can do a release and close out the appveyor issues in Core & Windsor? Would like to close these out before I pick up something else.

not sure if you are checking your mail, my internet is fixed now. Do you think we can do a release and close out the appveyor issues in Core & Windsor? Would like to close these out before I pick up something else.

Sorry about that, I started looking into it the other night after your email and found a few problems but didn't get it finished and forget to reply. Will try to sort that out tonight.

No worries, if there is anything I can help with please let me know.

I think we are good to go here. @jonorossi - can we close this out?

Yep, #275 is now merged.


experimental service function for pathfinder & multi-path pathfinder

Summary:
Expose the implementation of Pathfinder and multi-path Pathfinder through service functions.
Description:
Although they are very close, I decided that two service functions would be simpler than one with a few toggles.  The service functions will go in the files

src/stan/services/experimental/pathfinder/pathfinder.hpp.
src/stan/services/experimental/pathfinder/multi_pathfinder.hpp.

The signature of the functions will be as follows (the comments after variable names are the names of the variables in the Pathfinder arXiv paper).
Single-path Pathfinder
/**
 * Run the single-path Pathfinder algorithm for the specified model,
 * using the specified random seed and chain ID, using the specified
 * fixed and random initialization, given the L-BFGS parameters, number
 * of ELBO samples to evaluate, and final sample size to return,
 * writing results to the specified callbacks.
 *
 * From the specified initialization, which may be part or wholly
 * random, Pathfinder runs the limited memory BFGS (L-BFGS) algorithm
 * until the objective (log density) has converged within a specified
 * relative tolerance, or the maximum number of iterations is hit.
 * Then for each point on the optimization trajectory, a multivariate
 * normal with covariance given approximately by L-BFGS, the evidence
 * lower bound (ELBO) is evaluated using a specified number of Monte
 * Carlo draws.  Finally, draws are taken from the normal
 * approxiamtion with highest ELBO and transformed back to the
 * constrained scale to be returned as a sample.
 *
 * Algorithm description and evaluation:
 * Lu Zhang, Bob Carpenter, Andrew Gelman, Aki Vehtari (2022)
 * Pathfinder: parallel quasi-Newton variational inference.  arXiv.
 * https://arxiv.org/pdf/2108.03782.pdf
 *
 * @tparam M type of model class
 * @param model Stan model
 * @param random_seed seed for PRNG
 * @param chain_id chain identifier for multiple chains
 * @param init fixed initial values
 * @param init_radius uniform random initialization bounds
 * @param lbfgs_max_history max history size, determining rank of
 * covariance estimate
 * @param lbfgs_max_iterations maximum iterations for L-BFGS
 * @param lbfgs_rel_tolerarnce relative tolerance on L-BFGS
 * convergence of the log density
 * @param elbo_samples number of Monte Carlo samples used to estimate
 * ELBO
 * @param sample_size number of approximate draws to return
 * @param interrupt callback for interrupting process
 * @param logger callback for writing log messages to console
 * @param init_writer callback for writing initialization
 * @param parameter_writer callback for writing sample draws
 * @param diagnostic_writer callback for writing diagnostics
 */
template <typename M>
int pathfinder(Model& model,
	       unsigned int random_seed,
	       unsigned int chain_id,
	       const stan::io::var_context& init,         // pi_0
	       double init_radius,                        // pi_0
	       double lbfgs_max_history,                  // J
	       unsigned int lbfgs_max_iterations,         // L
	       double lbfgs_rel_tolerance,                // tau_rel
	       unsigned int elbo_samples,                 // K
	       int sample_size,                           // M

	       callbacks::interrupt& interrupt,
	       callbacks::logger& logger,
	       callbacks::writer& init_writer,
	       callbacks::writer& parameter_writer,
	       callbacks::writer& diagnostic_writer);

Multi-path Pathfinder
/**
 * Run the multi-path Pathfinder algorithm for the specified model,
 * using the specified random seed and chain ID, using the specified
 * fixed and random initialization, given the LBFGS parameters, number
 * of ELBO samples to evaluate, and final sample size to return,
 * writing results to the specified callbacks.
 *
 * Multi-path Pathfinder runs a specified number of single-path
 * Pathfinder instances, collecting a specified number of draws per
 * run, then importance resamples a final sample of a specified size.
 * Importance resampling is done with Pareto smoothing to reduce
 * variance.
 *
 * Algorithm description and evaluation:
 * Lu Zhang, Bob Carpenter, Andrew Gelman, Aki Vehtari (2022)
 * Pathfinder: parallel quasi-Newton variational inference.  arXiv.
 * https://arxiv.org/pdf/2108.03782.pdf
 *
 * @tparam M type of model class
 * @param model Stan model
 * @param random_seed seed for PRNG
 * @param chain_id chain identifier for multiple chains
 * @param init fixed initial values
 * @param init_radius uniform random initialization bounds
 * @param lbfgs_max_history max history size, determining rank of
 * covariance estimate
 * @param lbfgs_max_iterations maximum iterations for L-BFGS
 * @param lbfgs_rel_tolerarnce relative tolerance on L-BFGS
 * convergence of the log density
 * @param elbo_samples number of Monte Carlo samples used to estimate
 * ELBO
 * @param sample_size number of approximate draws to return
 * @param interrupt callback for interrupting process
 * @param logger callback for writing log messages to console
 * @param init_writer callback for writing initialization
 * @param parameter_writer callback for writing sample draws
 * @param diagnostic_writer callback for writing diagnostics
 */
template <typename M>
int multi_pathfinder(Model& model,
		     unsigned int random_seed,
		     unsigned int chain,
		     const stan::io::var_context& init,     // pi_0
		     double init_radius,                    // pi_0
		     double lbfgs_max_history,              // J
		     unsigned int lbfgs_max_iterations,     // L
		     double lbfgs_rel_tolerance,            // tau_rel
		     unsigned int elbo_samples,             // K
		     int single_path_runs,                  // I
		     int single_path_sample_size,           // M
		     int sample_size,                       // R

		     callbacks::interrupt& interrupt,
		     callbacks::logger& logger,
		     callbacks::writer& init_writer,
		     callbacks::writer& parameter_writer,
		     callbacks::writer& diagnostic_writer);

Expected Output:
Draws converted back to constrained scale like ADVI sent to parameter_writer, along with whatever diagnostics are available sent to diagnostic_writer (such as ELBO evaluation statistics).
Additional Information:
This is all going in the experimental folder and will be marked as such like ADVI when run.
Current Version:
v2.29.2

What is the rationale for bypassing the current procedures for including a new algorithm, regardless of whether it is accompanied by non-standardized "experimental folder and will be marked as such like ADVI when run”?  There have been no RFCs for this method nor for any procedure for incorporating official experimental methods instead of implementing them in forks as it typical for open source projects.  At the same time I haven’t seen any discussion from the governing body about formalizing any such procedure.

On Apr 11, 2022, at 5:09 PM, Bob Carpenter @.***> wrote:
Summary:
Expose the implementation of Pathfinder and multi-path Pathfinder through service functions.
Description:
Although they are very close, I decided that two service functions would be simpler than one with a few toggles. The service functions will go in the files
src/stan/services/experimental/pathfinder/pathfinder.hpp.
src/stan/services/experimental/pathfinder/multi_pathfinder.hpp.
The signature of the functions will be as follows (the comments after variable names are the names of the variables in the Pathfinder arXiv paper).
Single-path Pathfinder
/**

Run the single-path Pathfinder algorithm for the specified model,

using the specified random seed and chain ID, using the specified

fixed and random initialization, given the L-BFGS parameters, number

of ELBO samples to evaluate, and final sample size to return,

writing results to the specified callbacks.

From the specified initialization, which may be part or wholly

random, Pathfinder runs the limited memory BFGS (L-BFGS) algorithm

until the objective (log density) has converged within a specified

relative tolerance, or the maximum number of iterations is hit.

Then for each point on the optimization trajectory, a multivariate

normal with covariance given approximately by L-BFGS, the evidence

lower bound (ELBO) is evaluated using a specified number of Monte

Carlo draws.  Finally, draws are taken from the normal

approxiamtion with highest ELBO and transformed back to the

constrained scale to be returned as a sample.

Algorithm description and evaluation:

Lu Zhang, Bob Carpenter, Andrew Gelman, Aki Vehtari (2022)

Pathfinder: parallel quasi-Newton variational inference.  arXiv.

https://arxiv.org/pdf/2108.03782.pdf

@tparam M type of model class

@param model Stan model

@param random_seed seed for PRNG

@param chain_id chain identifier for multiple chains

@param init fixed initial values

@param init_radius uniform random initialization bounds

@param lbfgs_max_history max history size, determining rank of

covariance estimate

@param lbfgs_max_iterations maximum iterations for L-BFGS

@param lbfgs_rel_tolerarnce relative tolerance on L-BFGS

convergence of the log density

@param elbo_samples number of Monte Carlo samples used to estimate

ELBO

@param sample_size number of approximate draws to return

@param interrupt callback for interrupting process

@param logger callback for writing log messages to console

@param init_writer callback for writing initialization

@param parameter_writer callback for writing sample draws

@param diagnostic_writer callback for writing diagnostics
*/
template
int pathfinder(Model& model,
unsigned int random_seed,
unsigned int chain_id,
const stan::io::var_context& init,         // pi_0
double init_radius,                        // pi_0
double lbfgs_max_history,                  // J
unsigned int lbfgs_max_iterations,         // L
double lbfgs_rel_tolerance,                // tau_rel
unsigned int elbo_samples,                 // K
int sample_size,                           // M
  callbacks::interrupt& interrupt,
  callbacks::logger& logger,
  callbacks::writer& init_writer,
  callbacks::writer& parameter_writer,
  callbacks::writer& diagnostic_writer);

Multi-path Pathfinder
/**

Run the multi-path Pathfinder algorithm for the specified model,

using the specified random seed and chain ID, using the specified

fixed and random initialization, given the LBFGS parameters, number

of ELBO samples to evaluate, and final sample size to return,

writing results to the specified callbacks.

Multi-path Pathfinder runs a specified number of single-path

Pathfinder instances, collecting a specified number of draws per

run, then importance resamples a final sample of a specified size.

Importance resampling is done with Pareto smoothing to reduce

variance.

Algorithm description and evaluation:

Lu Zhang, Bob Carpenter, Andrew Gelman, Aki Vehtari (2022)

Pathfinder: parallel quasi-Newton variational inference.  arXiv.

https://arxiv.org/pdf/2108.03782.pdf

@tparam M type of model class

@param model Stan model

@param random_seed seed for PRNG

@param chain_id chain identifier for multiple chains

@param init fixed initial values

@param init_radius uniform random initialization bounds

@param lbfgs_max_history max history size, determining rank of

covariance estimate

@param lbfgs_max_iterations maximum iterations for L-BFGS

@param lbfgs_rel_tolerarnce relative tolerance on L-BFGS

convergence of the log density

@param elbo_samples number of Monte Carlo samples used to estimate

ELBO

@param sample_size number of approximate draws to return

@param interrupt callback for interrupting process

@param logger callback for writing log messages to console

@param init_writer callback for writing initialization

@param parameter_writer callback for writing sample draws

@param diagnostic_writer callback for writing diagnostics
*/
template
int multi_pathfinder(Model& model,
unsigned int random_seed,
unsigned int chain,
const stan::io::var_context& init,     // pi_0
double init_radius,                    // pi_0
double lbfgs_max_history,              // J
unsigned int lbfgs_max_iterations,     // L
double lbfgs_rel_tolerance,            // tau_rel
unsigned int elbo_samples,             // K
int single_path_runs,                  // I
int single_path_sample_size,           // M
int sample_size,                       // R
    callbacks::interrupt& interrupt,
    callbacks::logger& logger,
    callbacks::writer& init_writer,
    callbacks::writer& parameter_writer,
    callbacks::writer& diagnostic_writer);

Expected Output:
Draws converted back to constrained scale like ADVI sent to parameter_writer, along with whatever diagnostics are available sent to diagnostic_writer (such as ELBO evaluation statistics).
Additional Information:
This is all going in the experimental folder and will be marked as such like ADVI when run.
Current Version:
v2.29.2
—
Reply to this email directly, view it on GitHub https://github.com/stan-dev/stan/issues/3119, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALU3FS2X2YG3MJZVSAL4ALVESIKBANCNFSM5TENVQWA.
You are receiving this because you are subscribed to this thread.

@betanalpha:  What do you consider to be the current procedure for including a new algorithm?  What about changes to existing algorithms?  Is the process written up somewhere?

There was a detailed procedure on the github wiki, although the wiki no longer seems to be around.  I missed when that happened.
That said the procedure was set up long ago before a lot of the technical governance fell apart.  At this point the only procedure for substantial changes has been the design docs, and even then there’s no formal criteria for acceptance.

@betanalpha if I am not mistaken, you are looking for https://github.com/stan-dev/stan/wiki/Proposing-Algorithms-for-Inclusion-Into-Stan? This page is still there at https://github.com/stan-dev/stan/wiki under Contributing new functions and algorithms. The wiki was reorganized a bit I think a year ago - it was full of outdated clutter.

Yes, thanks Rok!  My apologies for forgetting that the wikis are local to each repo and not the entire stan-dev account.
This is incidental but, given the wealth of information in some of the wikis, it might be useful to link to the main repo wikis on the stan-dev landing page.
The criteria listed in the link are very liberal, and they were largely constructed to formally quantify the many problems with the current ADVI implementation in Stan.  Criteria that ensure reasonable robustness relative to the Hamiltonian Monte Carlo implementation would be much stricter, but we had never had to consider those stricter criteria to that point.  Ultimately the goal was to provide a uniform path for anyone in the community to propose the introduction of a new method while maintaining the robustness of the user experience.

On Jun 1, 2022, at 4:14 AM, Rok Češnovar @.***> wrote:
@betanalpha https://github.com/betanalpha if I am not mistaken, you are looking for https://github.com/stan-dev/stan/wiki/Proposing-Algorithms-for-Inclusion-Into-Stan https://github.com/stan-dev/stan/wiki/Proposing-Algorithms-for-Inclusion-Into-Stan? This page is still there at https://github.com/stan-dev/stan/wiki https://github.com/stan-dev/stan/wiki under Contributing new functions and algorithms. The wiki was reorganized a bit I think a year ago - it was full of outdated clutter.
—
Reply to this email directly, view it on GitHub https://github.com/stan-dev/stan/issues/3119#issuecomment-1143265423, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALU3FRC6MBBBITZT7JOSQTVM4LVBANCNFSM5TENVQWA.
You are receiving this because you were mentioned.


Gaze is adding all folders in HOME to watch list

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Windows 10 (16179)
Hyper.app version: 1.3.1
Link of a Gist with the contents of your .hyper.js: Default
Relevant information from devtools (CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere): N/A
The issue is reproducible in vanilla Hyper.app: Yes

Issue
Relevant to the following hyper issues:

#1688 - Can't install on windows 10
#1568 - EPERM: operation not permitted, lstat
#1499 - Unable to run Hyper 1.1.0 on macOS
#1136 - Unable to launch hyper 1.0.0 even after reinstall in Ubuntu 14.04

Relevant to the following gaze issues:

#214 - Gaze.prototype._addToWatched repeating readDir of same directory on each call
#239 - fs.lstatSync doesn't handle specific Windows REPARSE POINTS

About 2 weeks ago I started seeing the following when starting hyper. I wasn't sure what had changed. It was not a new hyper version, but I had just upgraded to the 16176 Windows Insider build - although I'm also sure that didn't cause it - confused ... I started investigating.

The only item being added to glaze from hyper for watching seems to be the .hyper.js file in the user's HOME folder. But I noticed (after putting tons of logging into glaze) that it added the .hyper.js file to its watch list, but then also added all the sub-folders in my HOME folder too. This is caused by the following logic within glaze:

shama/gaze/blob/v1.1.2/lib/gaze.js#L272-L298

Once glaze starts watching additional folders in the HOME folder, there are a number of permission and other types of errors that start happening for various users. In my case above, the OneDrive folders have a specific REPARSE POINT which causes the fs.lstatSync call made by glaze to throw a EINVAL error. I'm adding issues to the glaze and node repos for this.
If hyper could ensure that only the .hyper.js file was watched, then I believe that all of the referenced issues would be resolved.

With the new configuration setup, this shouldn't cause a problem after https://github.com/zeit/hyper/pull/1509.  (Config files are moving into a directory.)


feat: Improved typing of ModelDictT

Description
Fixes typing issues in service

Closes
https://github.com/litestar-org/advanced-alchemy/issues/265
This still doesn't solve the problem of UnknownVariableType if the subtypes of ModelDictT are not installed (eg: Pydantic)
But at least it solves the problem of incompatibilities when they are installed

@cofin  looks like the failfast checks fail because I changed
try:
    # this is from pydantic 2.8.  We should check for it before using it.
    from pydantic import FailFast  # pyright: ignore[reportAssignmentType]

    PYDANTIC_USE_FAILFAST: Final[bool] = False

to

try:
    # this is from pydantic 2.8.  We should check for it before using it.
    from pydantic import FailFast  # pyright: ignore[reportAssignmentType]

    PYDANTIC_USE_FAILFAST: Final[bool] = True

I am changing it back, but I guess I am confused about why it's always False and what purpose is it actually serving?

@cofin looks like the failfast checks fail because I changed
try:
    # this is from pydantic 2.8.  We should check for it before using it.
    from pydantic import FailFast  # pyright: ignore[reportAssignmentType]

    PYDANTIC_USE_FAILFAST: Final[bool] = False

to
try:
    # this is from pydantic 2.8.  We should check for it before using it.
    from pydantic import FailFast  # pyright: ignore[reportAssignmentType]

    PYDANTIC_USE_FAILFAST: Final[bool] = True

I am changing it back, but I guess I am confused about why it's always False and what purpose is it actually serving?

It's currently set to be permanently disabled.  It was enabled for a short time after this feature came out, but I would intermittently get exceptions when using it.  Because of this, I disabled it until I had time to get a bit more familiar with the feature (and for it to mature a bit).


field details

i want to know about some database fields and what value need to set for that.

in a socket response for positions there is field call outDated=false and valid=true what this means?
what will happen if i will set status=false into device table for device? it will stop recording position for that device or device will no more visible into web-interface?

outdated means that GPS info was taken from older report
valid is a flag reported directly by GPS module
there is no status in the device table

how do i stop device from sending location is there any way to off device?

Only by sending command to the device, if it's supported for the protocol.


Add Dai Nam University

The official website: http://dainam.edu.vn/
Faculty of Information Technology : http://dainam.edu.vn/en/introduction-to-faculty-of-information-technology
Contact info: http://dainam.edu.vn/en/contact

@hung-nguyen-90 Pull request merged. Thank you!


Fixes specifying ruby patch level in gemfile and gemspec

[x] add failing spec
[x] add fix (with passing spec) and more specs to cover edge cases
[x] change error message to a more meaningful one fixed the bug and a meaningful error message is now being shown

spec always passes on 2.2.0p0, probably because the patch version is 0

My findings so far:
(On brach master)
In Bundler::Resolver::SpecGroup#for? (bundler/resolver.rb) in spec_required_ruby_version.satisfied_by?(required_ruby_version.gem_version), spec_required_ruby_version has a ruby version with the patch number, but required_ruby_version.gem_version only contains the version without patch number (is it present in required_ruby_version.patch_version).
@segiddins do you think required_ruby_version.gem_version should include the patch number? I can track down where it is being set and make sure the patch number gets included. I believe this would be the best way to fix this, but as it may also have unintended effects on other parts of the code I could also change Bundler::Resolver::SpecGroup#for? to use a patch version when it is present.
The Gem::Version assumes a patch number of 0, that is why the tests for ruby 2.2.0p0 pass: because Gem::Requirement#satisfied_by? returns true for that case.

@chalkos let's just see if changing gem_version fixes things?

I think this could use some more specs.
The new method in Bundler::RubyVersion could (needs to?) be tested.
Regarding #4593, I think some more tests could be written, specially for some edge cases.

@chalkos is this still WIP?

Yes. I still need to add more specs to cover edge cases and to RubyVersion's new method and change error message to a more meaningful one.

@segiddins after making the changes you suggested, would you like me to separate this in 2 or 3 commits? I think we could have one with the initial specs and then another one or two with the fix and the RubyVersion specs.

@bundlerbot r+

woo bundlerbot! :tada:

@chalkos see https://travis-ci.org/bundler/bundler/jobs/136049835#L3428-L3446

I'll rebase it to reproduce this on my end.

@segiddins turns out ruby 2.4.0dev has a RUBY_PATCHLEVEL of -1
For these versions you can't specify a patchlevel in the gemspec (because it would be -1 and bundler will complain about that). I suggest that affected tests are skipped in such cases.

@chalkos agreed

I rebased on master and added code that should skip the spec on ruby versions with negative patchlevel.
@segiddins is this supposed to fail? https://travis-ci.org/bundler/bundler/jobs/136242613

@homu r+

:pushpin: Commit 4c5d334 has been approved by segiddins

:hourglass: Testing commit 4c5d334 with merge 64edbb8...

:sunny: Test successful - status


Add ChangeDetectionStrategy.OnPush strategy to all components

@Component({
  changeDetection: ChangeDetectionStrategy.OnPush,
})

Double triple check all components are setup to do this

Good stuff :+1:

I ask not do it by default. This performance hit.

@adamdbradley Can you guys add it to ion-select too? I think it could solve an issue I have with: https://forum.ionicframework.com/t/ng2-translate-and-selectedtext-on-ion-select-delayed-translation-until-clicked/96034


Solution of Assignment-3

I have solved the two questions to my best knowled.
I have divided Question#2 in two parts:
part one with visualization Example 1
part two with visualization Example 2

[ ] I can confirm that my changes are working as intended

A3 complete


set a name for the cloud task based on display name and UUID

Gives a more readable name in the Google Tasks console and API.

Thanks!!


Improve tags

I don't think the name should be in the tags but paths should be. I did a search for trails and paths agrc and it showed something from wfrc

It should be catching tags that are in the title. I'll look at the code; it may be hanging up because it's an exact match with the title. Paths being included in the tags is a dataset-specific issue that's probably best tackled in the Porter issue.

So the tags that get applied to agol come from the sgid metadata?

Yes, in part, assuming the SDE metadata is properly set up.
I believe the initial publish procedure tries to populate the AGOL summary, description, use constraints, credits, and tags from the SDE metadata.
Then, when agol-validator is run it creates an arcpy metadata object from the feature class and pulls over anything in its .tags property (so that if tags in the SDE metadata are updated they are propagated to AGOL). It will also keep any additional tags that have been added to AGOL (it gets the list of existing AGOL tags, appends the tags from SDE metadata, and then evaluates each one to see if it should be kept).

I"ll let you close this when the title isn't in the tags :)

Ok, looking at the logs, agol-validator didn't add the Utah Trails and Pathways tag. It probably came over when I manually uploaded the metadata for this AGOL item.
However, now that I think about it, the fact that updating the AGOL metadata pulls any tags from the SDE metadata creates a problem where the validator updates the tags from existing AGOL and metadata tags (and properly removes any that are in the title) and then the tags get promptly overwritten by the metadata fix. I think I need to move the tag fix to occur after the metadata fix.

Hey, look at that, the tags fix is already after the metadata fix (as are the title and description fixes). Guess I figured that out before and then forgot it. I'll add a note for posterity in the code in the next commit about this.
(And I just confirmed, Utah Trails and Pathways is in the SDE metadata for the feature class, so that's most likely where it came from)

So the validator should remove this tag then since it is a duplicate? I've asked @gregbunce to remove it from SDE.

Yeah, it should next time it runs. I've tested the logic (outside of the program, because I don't have tests written for agol-validator) and it should catch it and remove it.

I'll look through the logs to see if there's anything else with the title
in the tags—it should be catching that and reporting it, even if it's
getting overwritten.
On Thu, Jul 9, 2020 at 10:45 AM steveoh<EMAIL_ADDRESS>wrote:

since greg updated sde i don't think it will be a good test. we might want
to look for others with the same issue
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/agrc/agol-validator/issues/21#issuecomment-656234609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJDGLXUHBMW7FZ3IDPAFUCLR2XX2FANCNFSM4OVAO4TA
.

i cleaned up the tags in Internal SDE.  they now follow our guidelines.

since greg updated sde i don't think it will be a good test. we might want to look for others with the same issue. Are you thinking that the validator hadn't been run since trails and pathways was added? Or why wasn't it fixed by the validator already?

It wasn't fixed because I had to manually force the metadata update Tuesday because it was too large so we had to trim it first, and agol-validator hasn't run since then.
I just dumped all the SDE metadata tags out to csv, and it looks like the only possible match is Utah State Courts for 'SGID.SOCIETY.StateCourtDistricts' (http://utah.maps.arcgis.com/home/item.html?id=2938c95d71444c5cb527a2fda25629d9). This tag hasn't been removed because Utah State Courts is not in Utah State Court Districts

Ok, maybe we should simulate the error with a less popular dataset or with a test with modified xml to be sure

Yeah, I've got an AGOL item and faux metatable in my own folders I'm using for testing. I can go back and add a tag to an feature class' SDE metadata and point my item at it to check.

It's working as expected:

(and "Foo" was a pre-existing tag)

Awesome, I'd love to see these tests added to the repository!

TBH, test frameworks are a little outside my wheelhouse right now. This is just from manually running it against the fake metatable (http://utah.maps.arcgis.com/home/item.html?id=e5380e8b57924192a8e39cfe8c6f5a0a) and test item (http://utah.maps.arcgis.com/home/item.html?id=d2ea8eb22aa64d22800bc370bb1b128b) in my AGOL folders, updating the metatable entry for that test item as needed. I'm realizing that my engineering is very tightly coupled, thus making it difficult to test individual components.

well, i'm happy to help expand your wheelhouse. whenever you would like to schedule some time let me know.


Setup build for MacOSX

Tries to fix #1901

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@sharanry For Gensim to support Mac OS X, you will need to plugin Travis, since conda-forge uses different CI builds for different platforms. If you can figure out how to get Travis working without timeout, that would be awesome.

@souravsingh Thanks for the guidance.
I saw that you tried to fix this in an earlier test PR, was Travis's timeout the only problem?

@sharanry Indeed. The Travis times out when running the doc2vec tests.

@souravsingh If resource constraints are cause of the time out, this might be the solution.

Limit Concurrent Jobs is off for the conda-forge builds.

Limit Concurrent Jobs is off for the conda-forge builds.

Shouldn't it be tuned on and fixed to 1?

It is not recommended to edit the Travis YAML files

The builds are failing for Appveyor and Travis. I would suggest to close and reopen again to restart the CI services.

Hi guys @sharanry  @souravsingh, how is going? What's a problem right now?

@sharanry changed permissions of some files looks very suspicious, why this needed?

changed permissions of some files looks very suspicious, why this needed?

This was done automatically by conda-smithy, however i manually removed those changes now

@sahmed95 some tips for you:

try to run MacOSX with the different testing system (default unittest or pytest).
check that file compiled correctly (looks OK in logs, but better to manually check it)

If a test timeouts, then you can disable that test by giving --exclude REGEX to nosetests.

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

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Test doc2vec parallel training is the one taking too long in macos

@sharanry Yup, that's the one that causes the timeout. And we cannot skip it since it is an important test.

@sharanry Yup, that's the one that causes the timeout. And we cannot skip it since it is an important test.

Trying to run tests using pytest on travis ci

There is a mistake in the pytest command.

@sharanry this is really important feature for gensim, please focus on it

@sharanry @souravsingh  Hi, I would also like to help. Travis-ci log for py3.5 and py3.6 failed with error "loader for pytest cannot handle py.test".  It looks like a similar problem as here, have a look.

outdated, closing


Rename Navigation uses of 'location' to 'position'

Contrary to the entire rest of the engine NavigationAgent's decided to deal with locations instead of positions.

How about "destination"? I can see why "position" wasn't used originally, most engine features deal with objects that have a position, but these are e.g. waypoint / path positions (rather than objects), so expressions like "get_next_position()" are a bit vague imo.

We don't seem to have a clear consensus and it's pretty late for this kind of mostly cosmetic/consistency change.
It's mostly your call @smix8, if you feel this is really important to have a sane base to build on in 4.x, we can merge (after rebase). Otherwise I'd just leave it as is.
CC @DarkKilauea @Scony

IMHO having position for consistency is a good idea. As noted by OP, entire engine uses position in similar contexts. I'd add that even 3rd party libraries like Recast/Detour use position rather than some confusing synonyms (see e.g. http://rwindegger.github.io/recastnavigation/structdtCrowdAgent.html ).
Therefore, to avoid painful deprecation process in the future, I'd vote for merging this change ASAP.

I did not rebase this pr on purpose cause I think it is now too late for Godot 4.0 that is soon RC status. It is not worth the friction with users renaming one of the main functions now cause e.g. all the manuals and tutorials need to be rewritten and recent tutorial videos targeting Godot 4 will become partly invalid with this change and this will very much confuse users that already struggle to grasp the new navigation system.
I think now this should be merged later with the next Godot 4 version that allows compatibility breaking, e.g. Godot 4.1 that should possibly include a far larger Navigation rework so compatiblity breaking will be unavoidable for the navigation system.
This rename is also included in the larger avoidance rework pr where I already added compatibility functions for this rename.

@smix8 IMO the Godot 4 beta userbase atm. is a fraction of what it will be after the official 4.0 release. Thus changing the names now may be much less painful overall. But if you're saying 4.1 will be very painful navigation-wise anyway then maybe you're right and it does not matter after all.

I think now this should be merged later with the next Godot 4 version that allows compatibility breaking, e.g. Godot 4.1

Note that when breaking compat in 4.x you would need to provide compatibility code or a clear migration path. Right now this rename can be done as is, without any concern. But, again, this is up to you. We're okay with accepting or rejecting it.

Changed my opinion. Added compatibility functions and migration notes.

If we are going to switch away from location, then we need to be consistent across the entire navigation API.  I'd like to see renames across all the navigation nodes and NavigationServer.

@DarkKilauea A quick search showed that only the new navigation links are left using "location" inside the navigation system. I assume we can rename them without much friction cause they are relatively new.

The signals for waypoint_reached and link_reached also use the term "location" in their dictionaries, should that be changed to position?
If you do change it, remember to update the docs as well with the matching key.

Thanks!


parser fails with error code for long data uri

Using URLs with very long data uri i.e. for an embedded font-face, causes php to exit with an error code during parsing:
for example:
@font-face {   font-family: 'Glyphicons Halflings';   src:url(data:font/opentype;base64,n04AAEFNAA...<snip 26,000 characters>...gKA9IEaYJg); }
A PHPUnit test will abort with the message:
Process finished with exit code -1073741571 (0xC00000FD)
This might also be the cause of #38

Could you pls create PR for this fix?


[Modules] Fixed globalConfiguration property logic for v1 appGw

Description
Recently I was using this module in order to deploy application gateway v1 tier:Standard SKU size:Medium.
Seems like after passing any of v1 SKUs allowed values in "sku" parameter (which are 'Standard_Small', 'Standard_Medium', 'Standard_Large', 'WAF_Medium', 'WAF_Large') module is failing cause "globalConfiguration" property is available only in v2.
Error
I received following error during initial deployment before I have implemented change which I am proposing here:
{
"status": "Failed",
"error": {
"code": "InvalidTemplateDeployment",
"message": "The template deployment 'obscured_deploymentName' is not valid according to the validation procedure. The tracking id is 'obscured'. See inner errors for details.",
"details": [
{
"code": "ApplicationGatewayFeatureCannotBeEnabledForSelectedSku",
"target": "/subscriptions/obscured_subscriptionId/resourceGroups/obscured_resourceGroupName/providers/Microsoft.Network/applicationGateways/obscured_resourceName",
"message": "Application Gateway /subscriptions/obscured_subscriptionId/resourceGroups/obscured_resourceGroupName/providers/Microsoft.Network/applicationGateways/obscured_resourceName does not support GlobalConfiguration for the selected SKU tier Standard. Supported SKU tiers are Standard_v2,WAF_v2.",
"details": []
}
]
}
}
Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change
Please delete options that are not relevant.

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

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (readme)
[x] I did format my code

@microsoft-github-policy-service agree

Hey @hip9k thank you for your contribution. Did you test the new template by any chance? Just want to make sure the test cases continue to work as expected. :)


Added files for docker support

I'm running only containers on my local server and thought it could be helpful for someone else to have support for docker images on this cool project.
I've added a dockerfile, a docker-compose.yaml and updated the documentation. What is missing is a build and publish step for the docker images to Docker Hub container registry. Right now the image needs to be build locally.

This is great! Thanks for the contribution.
Will merge as is. If you want to add the auto-building and publishing, I've done that before for Go projects and it's pretty easy. Here's a template you can borrow from: https://github.com/scosman/zipstreamer/blob/master/.github/workflows/publish.yml

Also: adding Home Assistant docs is really good call 😀


Make use of the controller-runtime helper function to create and update resources

Currently in the controller we wrote code to detect if policy server resource should be create and/or updated. However, this is not necessary because the controller-runtime package has a helper function that does that for us. Therefore, we shoud use and simplify our code. Which makes our life easier in the longer run because we do not need to keep track of the fields that should trigger a resource update.

@kubewarden/kubewarden-developers this is block due an issue in the upgrade process of the controller. As we discussed during one of our daily, I'll work on code to use the createOrUpdate helper function from the controller-runtime package to simplify our code and  workaround this.

Originally posted by @jvanz in #660
Acceptance criteria

Update the controller code and use the function createOrUpdate function to create or update the resources created to make the policy server run.

I'm moving this to block until @flavio is able to review the PR as well.


#43 topography bands and landmask ancils

Plugins and CLI scripts for land mask and topography-band masks ancillary generation. Unittests and CLI tests added. Issue: #43
Landmask:

checks if improver landmask exists and if so (and --force option is not set) does nothing
if improver landmask doesn't exist (or --force is set), reads stage landmask and passes through CorrectLandMask plugin (to remove any non int/boolean values which may be introduced by interpolation, or if land fraction is output by StaGE).

Topography bands:

as above, only generates improver masks where the file doesn't exist or --force option is set.
GenerateOrographyBandAncils plugin loops over dictionary of topography bands, appending masked field for each band to cubelist. Fields are masked over sea, 0 at land points outside the band and 1 inside the band of interest.

Testing:

[ok] Ran tests and they passed OK
[ok] Added new tests for the new feature(s): unittests and CLI tests

In the future we may want to have improver ancillary-generate with some options for the various destinations - but we can get to that if/when we add more ancillary files.

This is ticket is on hold to give @benfitzpatrick a chance to produce improved inputs for the CLI tests.

Follow on issues @bjwheltor @benfitzpatrick

Where will improver ancillaries live?
In addition to StaGE ancillaries, we will need a high resolution orography field (for ex in wind downscaling). Ben has provided a version for testing, however, should this be added to #97 to standardise the generation process?

#127 captures the investigation into internal generation/hosting of ancillaries


Download-BcNuGetPackageToFolder Support package description for app name

Describe the issue
In the new implementation, the title element is required. Would it be possible to check if the title element is available and if not, check if the description field is available? I found a lot of packages, that use the description field for the app name.
https://github.com/microsoft/navcontainerhelper/blob/b4b554d4200c02fbff9058d612ee8dbc214d1c67/NuGet/Download-BcNuGetPackageToFolder.ps1#L149

@freddydk I'm sorry if I tag you here, but it seems like you didn't get assigned automatically and I'm not sure if you see the issues without being assigned or taged in it 😅

Duplicate #3347


update scikit-bio channel to biocore for GenBank parser

Once it has been merged. See PFC.

Taken care of in scikit-bio 0.5.1.


Highlight active section in navigation on scroll

This adds a new module that highlights a section in the left-hand
navigation pane when it is in view.

Yeah, I was intending to add this in another PR now that @thehenster's TOC
generation work has been merged.
On 5 December 2016 at 16:17, Oliver Byford<EMAIL_ADDRESS>wrote:

@36degrees commented on this pull request.
In source/stylesheets/modules/_toc.scss
https://github.com/alphagov/tech-docs-template/pull/13:

@@ -44,3 +44,7 @@
display: none;
}
}

+.toc-link--in-view {
Which, actually, is required to make the letter-spacing fix work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alphagov/tech-docs-template/pull/13, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABQSig9ByijAsEKKczaEU773BmRrL2e1ks5rFDkMgaJpZM4K8koj
.


Predefined ACME error types

A possible solution for #15.
Example usage:
err := client.Register(url, a)
if err, ok := err.(*Error); ok && err.Type == ErrBadCSR {
  // handle urn:acme:error:badCSR error
}

@mbwalas WDYT?

Cool, I think this is closest to perfect we can get, many thanks for doing that!


Better c++ and python examples/tutorials/documentation

Users of the Python API would appreciate example code that demonstrates integration with:

the ROS1 message API
the ROS2 message API
the protobuf API

Closing in favour of more specific tickets


All links should be opened in new tabs

Ref: https://github.com/bigbinary/neeto-quiz-web/issues/2603
While attempting the Ramda quiz by neeto-engineering team, clicking on links in answer explanation is opening links in the same tab.
This is an issue because navigating away from the current path while attempting a quiz leads to attempt termination.
Can we handle this case where links that are copy-pasted into neetoEditor also have a target="_blank" attribute similar to links which are embedded using editor options?

@AbhayVAshokan _a Could you please have a look into this on priority? Since more folks would be attempting this quiz in the coming days.

@gaagul _a please have a look at this issue. Create a fresh quiz in the staging environment and check why links are opening in the same tab.

@gaagul this is causing issues in neetoQuiz as well: https://github.com/bigbinary/neeto-quiz-web/issues/2603
I'm bumping up it to high-priority

In case of neetoQuiz answer explanation, I did some testing and found that the behaviour is changing based on whether we are rendering question.explanation.body vs question.description.body.to_s. It is working as expected and opening links in new tab when rendered using question.explanation.body instead of .to_s so I'm adding a fix for it in neetoQuiz.
This issue can be closed if the above behavior is intentional.
Removing the priority tags for now.
cc: @Amaljith-K @AbhayVAshokan @gaagul

Closing this issue since this will be fixed in PR: https://github.com/bigbinary/neeto-quiz-web/pull/2610


Use Case 12: User Login via Email and Password

User Login via Email and Password
User Story
As a user, I want to log in to the platform using my email and password so that I can securely access my account and view my sensor data.
Description
This use case involves implementing a user login process where users can authenticate themselves using their registered email and password. The system should validate the user's credentials, and if correct, grant access to their account. If the user has not yet confirmed their email during registration, they will not be able to log in. Passwords must be securely checked using best practices, and proper error messages should be displayed for failed login attempts.
Acceptance Criteria

[x] A login page is created where users can enter their email and password.
[x] The system validates the user's credentials:
[ ] Checks if the email exists in the user table.
[ ] Verifies if the password matches the stored (encrypted) password.
[ ] Ensures the user has confirmed their email.
[x] Users are successfully logged in and redirected to the dashboard upon successful login.
[x] Users who have not confirmed their email receive an appropriate error message.
[ ] Failed login attempts show proper error messages (e.g., "Incorrect email or password").
[ ] The system prevents brute-force login attempts by implementing rate-limiting or other security measures.

Testing
Normal Flow of Events
The user navigates to the login page.
The user enters their registered email and password.
The system validates the credentials and checks if the user has confirmed their email.
If everything is correct, the user is logged in and redirected to the dashboard.
The user can now access their account and view their sensor data
Alternate/Exceptional Flows:
S-1: Incorrect email or password
The user enters an incorrect email or password.
The system shows an error message: "Incorrect email or password."
S-2: Unconfirmed email
The user has not confirmed their email after registration.
The system prevents login and shows an error message: "Please confirm your email before logging in."
S-3:  Account is locked after multiple failed attempts
The user attempts multiple failed logins in a short period.
The system locks the account or temporarily blocks further attempts to prevent brute-force attacks.

A login page is created where users can enter their email and password.  The system validates the user's credentials. Checks if the email exists in the user table.  Verifies if the password matches the stored (encrypted) password.  Ensures the user has confirmed their email. Users are successfully logged in and redirected to the dashboard upon successful login.
Users who have not confirmed their email receive an appropriate error message.

A login page is created where users can enter their email and password. The system validates the user's credentials. Checks if the email exists in the user table. Verifies if the password matches the stored (encrypted) password. Ensures the user has confirmed their email. Users are successfully logged in and redirected to the dashboard upon successful login.
Users who have not confirmed their email receive an appropriate error message.