Results of other version of libraries

Hi,
Thank you for the open source code.
I reproduce your model with the same libraries with other version
torch                  1.13.0
torch-cluster          1.6.0+pt113cu116
torch-geometric        2.2.0
torch-scatter          2.1.0+pt113cu116
torch-sparse           0.6.16+pt113cu116
torch-spline-conv      1.2.1+pt113cu116
torchmetrics           0.11.4
torchvision            0.14.0
from my case, i get flowing results
F1              Recall        Precision
SWAT  0.778047    0.643728    0.982768
WADI  0.461867    0.349515    0.682105
There is huge deviation at WADI dataset
I can't doubt any cause except library version
I want to make up the environment with your same case
pytorch-geometric can't be installed on pytorch version 1.5.1 now
so would you check your model performance at recent version of libraries?

Sorry for the late reply. It might be a bit troublesome to adapt the codes with recent version of libraries as there seems changes in some API or implementations in the updated libraries. As for the performance, could you check if the data is processed like https://github.com/d-ailin/GDN/tree/main/scripts? It could also probably affect the result. Thanks.

Thank you for your reply
My data have been preprocessed by your code
Could you share your environment by Docker images?

Hi windows7897,
I am trying to reproduce the result as well, but my GPU is not compatible with cuda10.2 It is great that your environment setting is working. Just wondering is it possible that you share your environment with me? And I will keep you updated on the result that I got.
Much appreciate it and looking forward to hearing from you :)


Remove fnameescape call in chdir function

fnameescape is applied when calling gutentags#chdir when called again it can cause the addition of extra escape characters. Resolves issue #277.

Alternatively remove fnameescape from the following lines https://github.com/ludovicchabant/vim-gutentags/blob/8e69652c7a7e7aabd96cff21b6ee6b6a295c901c/autoload/gutentags.vim#L528 and https://github.com/ludovicchabant/vim-gutentags/blob/8e69652c7a7e7aabd96cff21b6ee6b6a295c901c/autoload/gutentags.vim#L540

I went with your other suggestion, editing your commit and merging it. Thanks a lot!


FYI only, feel free to close

Seen tasktxt before? https://youtu.be/HOYO0c_D6w0
Some similar ideas around timers alongside text, maybe something will inspire you.

Thanks for the info! I'll check it out.


Adds the ability to log http requests sent to Elasticsearch

This is helpful when troubleshooting.
Ex.
$ STORAGE_TYPE=elasticsearch java -jar ./zipkin-server/target/zipkin-server-*exec.jar --zipkin.storage.elasticsearch.http-logging=BASIC

2017-05-15 23:05:10.600  INFO 78150 --- [alhost:9200/...] z.s.e.http.ElasticsearchHttpStorage      : --> GET http://localhost:9200/ http/1.1
2017-05-15 23:05:10.617  INFO 78150 --- [alhost:9200/...] z.s.e.http.ElasticsearchHttpStorage      : <-- 200 OK http://localhost:9200/ (16ms, unknown-length body)
2017-05-15 23:05:10.624  INFO 78150 --- [alhost:9200/...] z.s.e.http.ElasticsearchHttpStorage      : --> GET http://localhost:9200/_template/zipkin_template http/1.1
2017-05-15 23:05:10.626  INFO 78150 --- [alhost:9200/...] z.s.e.http.ElasticsearchHttpStorage      : <-- 200 OK http://localhost:9200/_template/zipkin_template (1ms, unknown-length body)
2017-05-15 23:05:10.635  INFO 78150 --- [alhost:9200/...] z.s.e.http.ElasticsearchHttpStorage      : --> POST http://localhost:9200/_bulk http/1.1 (1756-byte body)
2017-05-15 23:05:10.640  INFO 78150 --- [alhost:9200/...] z.s.e.http.ElasticsearchHttpStorage      : <-- 200 OK http://localhost:9200/_bulk (4ms, unknown-length body)

cc @openzipkin/elasticsearch @sirtyro I suspect y'all will find this super handy

Wow, that should be superhelpful! We had some problems with AWS EC2 soon and were like blind kittens trying to understand what's going on. With this debug option it would be much easier.

ps this was originally a desperate option to try and help debug #1594 glad it would be generally helpful!

added env mapping will merge on green


Pacckage.json file unable to create

Issue Type: Feature Request
npm : The term 'npm' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that
the path is correct and try again.
At line:1 char:1

npm -i init

  + CategoryInfo          : ObjectNotFound: (npm:String) [], CommandNotFoundException

VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.18363
Restricted Mode: No

/needsMoreInfo
Looks like you don't have npm in PATH (at least PowerShell doesn't see it).
Not cleat how it's related to VS Cote though. Do you see same error if you run that commend directly in PowerShell (not in internal terminal)


Nested ArgGroups do not enforce mutual dependency

I'm trying to do configure mutual-dependency across nested arg-groups, but either I'm not configuring it quite right, it can't be done, or its not implemented 🤷♂ .
Below is a file with a sample command line, and my expected outputs to good/bad input.
package the.picocli.example;

import picocli.CommandLine;
import picocli.CommandLine.ArgGroup;
import picocli.CommandLine.Option;
import picocli.CommandLine.ParseResult;

public class SampleCmdLine {

  static class OtherOptions {
    @Option(
        names = "--other-option-1",
        arity = "1",
        required = true)
    private String firstOption;

    @Option(
        names = "--other-option-2",
        arity = "1",
        required = true)
    private String secondOption;
  }

  static class MySwitchableOptions {
    @Option(
        names = "--enable-more-options",
        arity = "0",
        required = true)
    private boolean tlsEnabled = false;

    @ArgGroup(exclusive = false)
    private OtherOptions options;
  }

  static class FullCommandLine {
    @ArgGroup(exclusive = false)
    private MySwitchableOptions switchableOptions;
  }

  public static void main(String[] args) {
    final CommandLine commandLine = new CommandLine(new FullCommandLine());
    ParseResult result;

    // Ideally this would FAIL (as the --enable-more-options is not set
    result = commandLine.parseArgs("--other-option-1=firstString", "--other-option-2=secondString");

    // Ideally this would PASS (and the switchableOptions would be null)
    result = commandLine.parseArgs("--enable-more-options");

    // Should fail as other-option-2 is not set (and defined as required)
    result = commandLine.parseArgs("--enable-more-options", "--other-option-1=firstString");
  }
}

Thank you for raising this!
I was able to reproduce the issue (thanks for the clear example).
I believe that your expectation is correct that the first example should fail because --enable-more-options is missing.
I am investigating...

I found the cause.
The CommandLine.ParseResult.GroupMatch.validate() method method oversimplifies things when validating the combination of options and subgroups. It simply counts the required args plus required subgroups, and compares that count with the number of present args and present subgroups, and based on that decides whether an element is missing.
This is an oversimplification, since if a required element is missing, and an optional subgroup is present, that should not cancel each other out.
I will fix this soon, and the fix will be included in the upcoming 4.2 release.

👍 Terrifyingly fast analysis :)

:innocent: Thank you! Please drop picocli a GitHub :stars: star if you like the project.   :wink:

done ;)

The fix has been committed to master.
Thank you again for reporting this!
If you want to verify, and play with the latest features, do this:
git clone https://github.com/remkop/picocli.git
cd picocli
gradlew publishToMavenLocal

That should publish picocli-4.2.0-SNAPSHOT to your local .m2 Maven cache. You can then try this in a project that uses the info.picocli:picocli:4.2.0-SNAPSHOT dependency.

@rain-on, All,
picocli 4.2.0 has been released, including this fix. Enjoy!


Inluce vector in team_tracker.hpp to fix compilation.

Hello Malcolm, thanks for the pull request.
We have included the fix into our internal build. The change will go out with the next release (which is scheduled sometime within the next two weeks).


WIP: Add Android TV functionality to Fire TV component

Description:
Allow for configuring Android TV devices as part of the Fire TV media player component.
This will not pass the build right now because I have not put androidtv 0.0.10 on pypi yet. I put the GitHub link in REQUIREMENTS so that people can test this component.
Android TV vs. Fire TV devices
I haven't documented this yet, but there is a new config parameter device_class. Allowed values are:

auto (default): determine whether it is an Android TV device or Fire TV device (manufacturer == "Amazon")
androidtv: setup an Android TV device
firetv: setup a Fire TV device

@rytilahti this implements phase 1 of what we discussed in https://github.com/home-assistant/home-assistant/pull/21674#issuecomment-470952084.
This builds off the work by @a1ex4 in https://github.com/home-assistant/home-assistant/pull/19157.
Pull request in home-assistant.io with documentation (if applicable): Forthcoming
Example entry for configuration.yaml (if applicable):
# Example configuration.yaml entry
media_player:
  # Use the Python ADB implementation without authentication
  - platform: firetv
    name: Fire TV 1
    host: <IP_ADDRESS>

  # Use the Python ADB implementation with authentication
  - platform: firetv
    name: Android TV 2
    host: <IP_ADDRESS>
    adbkey: "/config/android/adbkey"

  # Use an ADB server for sending ADB commands
  - platform: firetv
    name: Fire TV 3
    host: <IP_ADDRESS>
    adb_server_ip: <IP_ADDRESS>

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Tested this on my 2 shields and fire stick, working as expected.

Just tested this and it works perfectly with both my Shield and Fire TV. Thanks @JeffLIrion 👍

Awesome! @dshokouhi and @arsaboo, did you specify the device_class or let it auto-detect it?

@JeffLIrion i left it on auto detect personally.

@JeffLIrion what should the expected behavior be if the device restarts or we run adb disconnect on the server?

I initially used auto_detect and it worked perfectly. But since I know the devices, I specified the device_class now.

@JeffLIrion what should the expected behavior be if the device restarts or we run adb disconnect on the server?

If the connection gets broken, it should play out like this.

It tries to send an ADB command but fails, so now it knows the device is unavailable.
Update 1: it tries to reconnect, fails, and logs an error message.
Updates 2 and onward: it tries to reconnect and fails, but it doesn't log the error message.

This continues until it successfully reconnects.

This pull request is ready for review! Hopefully it can get into the next release!

@rytilahti are you able to merge this?

IMHO this should no longer be called firetv...
Since it isn't...

IMHO this should no longer be called firetv...
Since it isn't...

As @rytilahti suggested here, this is step 1 of 2:

Add Android TV functionality to the firetv component.
Rename the component to androidtv.

Do you think this should be done as a single pull request?

@JeffLIrion I think so, since well... it is. Even the underlying library has been switched out. Renaming would cause this to become a breaking change but breaking it now or later, wouldn't make a difference.
Please note, this is just my opinion, which might differ from others.

@frenck I prepared branches for the code and documentation that should successfully rename the integration to androidtv. If the consensus is that this pull request should rename the integration, I'll merge those branches into my pull request branches.

@frenck here is a pull request that is a continuation of this one, with the firetv integration renamed to androidtv: https://github.com/home-assistant/home-assistant/pull/21944.
It's probably preferable to merge that PR rather than this one.

I'm closing this PR in favor of https://github.com/home-assistant/home-assistant/pull/21944. If it is decided that renaming the integration from firetv to androidtv should be a separate PR, I'll reopen this.


Do not add transports to default extensions

By running this simple mesh node creates 3 listening sockets: two for TCP and one for UDP:
var th = require("telehash");

th.generate(function(err, id) {
  th.mesh({id: id}, function(err, mesh) {
    console.log(mesh);
  });
});

That's because of the transport extensions added by default on module load.

Should it be the option to disable default extensions without manually removing them?

I think it would make sense to have something like app.use from express.js where the user can register all required extension.
Only the registered extensions should be available. Same for ciphersets and other things.
This would also help in some deployment scenarions (sodium isn't running everywhere).

Yes, I very much want to move to this model here too, it's near the top of my TODO list now so it should happen soon :)


[Component] Textlink

### Tasks
- [x] Component
- [x] Documentation
- [x] Examples
- [x] Screenshot tests
- [ ] Configurator

Testing informations |
-- | --
Risk level ? | high (= must be tested by QAA before release)
Does this ticket need to be design reviewed ? | no ?
Referent designer : |  ?
Spec : | figma
UATs : | confluence
configurator : | confluence

@kazaky as discussed in our meeting, would it be possible to restrict the colours to the spark intents?

@soulcramer Kindly review my latest changes on TextLink branch
and also let me know What do you think of @JeremiasUX Comment?

@kazaky @soulcramer some questions :

on catalog app a space is missing after the first textLink

in specs it's written Since the textlink can be inline, it will inherit color from the text it’s in However in the screenshot above, I noticed that link does not inherit the text's color. i'm wondering if this case is supposed to happen

another detail : according to the specs, default color is basic. I think it should be default color on catalog app as well, for consistancy (at the moment it's main).

Hi Elisa,
Thanks for testing:
1- I made a fix for it
2- Technically it's not possible (We are using annotated String), We don't control how the Text color will be and how link color will be, user has full control to put both colors of full text & link.
3- I changed it as you like

Hi @elisa-hery ,
Thanks for testing:
1- I made a fix for it
2- Technically it's not possible (We are using annotated String), We don't control how the Text color will be and how link color will be, user has full control to put both colors of full text & link.
3- I changed it as you like

Hey @kazaky,
Oops i've missed your comment. On latest version I still can see the small bug :

Also, designers didn't review the component yet : @turolopezsanabria @JeremiasUX @Bibisirius who wants to review it ?
I'm moving the ticket back to "testing" column.

Hey @kazaky, we just did our Design-Review on the component.

We miss the option to disable the "underline" for the link, is that currently possible?
Everything looked good besides that

We miss the option to disable the "underline" for the link, is that currently possible?
Everything looked good besides that
Yes we can remove the underline!

Ok thanks @kazaky !
a request for the future : please let me know everything I should know about testing in your comments (e.g. when it's not available / testable, in which version, etc).
I waste a lot of time launching environments and looking for fixes / features that are not available (not especially with you, but in general)

Yes we can remove the underline!

If this is possible, why can't I see it in the configurator?

We're using annotattedStrings that allow us to correctly support i18n by specifying in a text where the style should go like so:
<string name="spark_text_link_short_example">
	<annotation color="neutral" typography="display2">Learn Kotlin Programming </annotation><annotation color="success" typography="display3">https://kotlinlang.org</annotation>
</string>

Here Learn Kotlin Programming  will be display in  the brand neutral color with the display 2 typo the https://kotlinlang.org link will be styled in the brand success color with the display 3 typo in bold and underlined.
This system supports all styles listed here with the exception of the bullet points and we added the support for spark tokens.
Imo it would be nicer to use if we had predefined styles for text links so that developers would not have to specify the color, underline, typo, font weigh every time and would just have to use something like :
<string name="spark_text_link_short_example">
	Learn Kotlin Programming <annotation link="emphasized" >https://kotlinlang.org</annotation>
</string>

That would use the underline in bold and in basic color for ex.


Add character limit info for "Description"

Update to reflect the character limit of "description"
Many users use this to add information to their action group emails.
Is there any future updates that will be implemented to better tailer this experience?

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

ID: b3eff5cd-b885-2e94-2ea6-3f60154123df
Version Independent ID: ec1862a7-fa36-1ac4-fe68-011ed39c16f3
Content: Overview of alerting and notification monitoring in Azure - Azure Monitor
Content Source: articles/azure-monitor/platform/alerts-overview.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @rboucher
Microsoft Alias: robb

@Mexicoder Thank you for your feedback, we will look into it and get back to you at the earliest.

@Mexicoder Thanks again for your query, i have reached out to our internal team to further information on this. Will keep you updated accordingly.

@Mexicoder - Thank you for being patient on this , post validation with our internal product team it has been called out that below are the limits for the description field
Log Search Alerts – 4096 characters
Other alert rules and Action Rules – 2048 characters
Hope this information helps.We will work with our document author @rboucher to have a back log item to incorporate this information in our existing documentation to reflect the limitation.
Regarding improving the experience in the UI, please use our feedback channel  to  share your feedback so that its open for the user community to upvote & comment on and this allows our team to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
We will go ahead and close this issue, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


feat(ErrorKeyRevoked): reconnect with automatic key addition

Context
When the public key is revoked, instead of manually asking to copy/pasta the key to reconnect the wallet, use KeyAutoAddService to automatically add the key back,
Closes #653 .
EDIT: depends on #742 to be done
Changes proposed in this pull request

add publicKey to wallet automatically (with user's consent) then redirect to welcome page

I would like to merge WICG/webmonetization/481 first,
to test the entire flow one last time


Investigate fuzzing the UI for ALMighty

https://testing.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html

@ldimaggi , can we have some discussion for this task!


Leetcode Question Number 1859

Leetcode Question Number 1859 solution needs to be added in the repo .
The link for the question is this.
Accepted Languages C++ / JAVA .
You Only need to add the  class Solution in the file.
Make Sure you have read the contributions guidelines before creating an PR.

I'd like to make a pr for this issue.


what's the minimum PHP version support

Hi team,
In the readme, it was denoted as  PHP 7.3 as a minimum version but in
composer JSON it was denoted as  5.3.0
Hope the composer json need to be updated,
Please clarify on this

@Thavarajan We recommend using PHP 7.4 until version v2.82 & you must upgrade your PHP in 8.0 if you are using the latest version, v2.8.4. In the latest version, we have already updated the composer


encode str into bytes for _lookup_ctag argument;

check source code of python-ctags and python-ctags3 to see what
argument type is expected (answer: char *);
guess this is python 2 legacy; but now it should work in python 3;

Could you please add a test case exercising this path? I've got no idea where this is triggered :)

I just ran the shipped test file tests/test_html_formatter.py and it failed.
def test_ctags():
    try:
        import ctags
    except ImportError:
        # we can't check without the ctags module, but at least check the exception
        assert pytest.raises(
            RuntimeError, HtmlFormatter, tagsfile='support/tags'
        )
    else:
        # this tagfile says that test_ctags() is on line 165, even if it isn't
        # anymore in the actual source
        fmt = HtmlFormatter(tagsfile='support/tags', lineanchors='L',
                            tagurlformat='%(fname)s%(fext)s')
        outfile = StringIO()
        fmt.format(tokensource, outfile)
        assert 'test_ctags' \
            in outfile.getvalue()

You can probably debug if the problematic value in html.py has type str or bytes. It's str on my machine and that caused the error.

Thanks, merged!


ObjectId is not defined

Thanks for this great Mongo V3 node @ozomer!  One question though, have you seen the Mongo find problem where:
msg.payload = { "_id": ObjectId("5bb59066e7179a6602f38d4e") }

Debug Console --> "ReferenceError: ObjectId is not defined"

I'm having the same trouble.  I've tried stringifying the value:
{ "_id": "ObjectId(\"5bb59066e7179a6602f38d4e\")" }

as well omitting the ObjectId: { "_id": "5bb59066e7179a6602f38d4e" }
Any suggestions?
PS. installing  node-red-contrib-objectid didn't help.

Okay I got it working.  Targetting the id field in node-red-contrib-objectid was the problem.  Thanks.


[Feature Request]: Add a 'favorite' feature

Relevant Scope
angular application
Description
Add a way for users to favorite any element (event, communities, podcasts...) to retrieve them easily.
It involves:

a solution to favorite/unfavorite each element
a solution to save the list for each user (with localstorage)
a solution to list the favorited elements.

Describe the solution you'd like
No response
Describe alternatives you've considered
No response

@geromegrignon that one looks interesting. I would like to develop it

Hi @AdrianRomanski, thanks.
Feel free to add ideas here and some mockups about our vision :)

@geromegrignon
Basic idea
re: a solution to favorite/un-favorite each element

heart icon near date; after click fill or un-fill color

re: a solution to save the list for each user (with localstorage)

after click add/remove favorite item id from local storage (map of ids or array of ids)

re: a solution to list the favorited elements.

another tab [[All], [Conferences], [Meetups], [Favourites]


Allow DB box port config (#198)

This implements enhancement #198 by allowing configuration of the listener and EM Express ports in the Vagrantfiles for the single-instance database boxes.
I've done the following testing:

Built each box twice, once with the default listener and EM Express ports (1521 and 5500), and once with non-standard ports (1522 and 5501).
For each build:

Verified that listener.ora and tnsnames.ora were created with the correct port.
Verified that sqlplus user/pw@localhost:port/service worked both in a guest SSH session and from the host.
Verified that EM Express (https://localhost:port/em) worked. (This step doesn't apply to the 11g XE box.)
Rebooted the box and re-checked steps ii and iii.

I'm happy to make any changes that you'd like and/or do additional testing.
Signed-off-by: Paul Neumann<EMAIL_ADDRESS>

That makes sense. Especially as people can easily ssh into the box and also perhaps start using the GUI, it's probably best to keep all the ports the same and not just the forwarded port.


Wizard example: initial values on one wizard page erases values on another

Hello,
I have an issue with a form separated into multiple wizard pages. All the wizard pages are set to destroyOnUnmount: false. The values are correctly remembered when moving from one page to another, though once we start injecting initial values, values from previous wizard pages are erased.
I 'm not sure if this is a bug or if I am misusing the interface, but here is an example where I added a default email as initial value to the second page :
https://codesandbox.io/s/voAGlOENV
Steps to reproduce the issue

Enter a name and a first name
Click "Next": first name and last name values have disappeared.

Though if you comment out the line adding initial values, values are saved.

In the previous example, setting keepDirtyOnReinitialize: true to the second wizard page solves the issue.
My use case is similar to this one : https://codesandbox.io/s/V4vKVm01
Two wizard pages, both have initial values and must retain their values.
Any help or hints on which part of ReduxForm I am misusing will be greatly appreciated !

Because this issue saw almost no activity for a few months, I'm closing it.


Add general Pagination component

We're using Prisma and React TanStack Query and both have a nice documentation about how to build a pagination system. Prisma explain us how to prepare the query to do our pagination while the TanStack docs teach us how to leverage the useInfiniteQuery hook and the need of a cursor property.
Build a general Pagination component that allow us to separate the content into different pages and filter them at the same time.

We've added pagination for the Transactions page in this PR https://github.com/AndreaBarghigiani/profit-tracker/pull/4 but right now we don't have a 'general' component able to pull this off.
Maybe we will never have one


Add cap and join style to bezier path.

The BezierPath class should support cap style (butt, round or square) and join style (miter, round, bevel).
NSBezierPath implements cap style and join style, so supporting this is a matter of making the attributes available in the appropriate places:

The cap style and join style should be context state variables, available under capstyle() and joinstyle()
The BezierPath should inherit these state variables when creating a new bezier path.
The BezierPath should have getters / setters for cap style and join style.
The BezierPath constructor should accept capstyle and joinstyle arguments.

joinstyle() is working but Path.joinstyle and Path.capstyle are not.
here is the minimum code to reproduce the issue
'''
nofill()
stroke(0)
strokewidth(10)
beginpath(40, 40)
lineto(140, 140)
lineto(280, 140)
path = endpath(draw=False)
#path.capstyle = ROUND
path.joinstyle = ROUND
#joinstyle(ROUND)
drawpath(path)
'''


JIT Client subscriptions Issues

Hello,
When a JIT client is present is obtaining the same subscriptions that real client:
Example:
00-client.json [ Host running sensu-client ]
{
  "client": {
    "name": "host.e.example.com",
    "address": "<IP_ADDRESS>",
    "subscriptions": [
      "system-metrics",
      "deb-system-checks"
    ]
  }
}

00-jit-client.json
{
  "client": {
    "name": "us-west-2.elb.amazonaws.com",
    "address": "unknown",
    "subscriptions": [],
    "keepalives": false
  }
}

98-elb-checks.json
{
  "checks": {
    "check_elb_west_2_middleware_api_health": {
      "command": "/etc/sensu/plugins/check-elb-health.rb -r us-west-2 -n middleware-api",
      "subscribers": [],
      "source": "us-west-2.elb.amazonaws.com",
      "interval": 60,
      "handlers": ["flapjack"]
    }
  }
}

SENSU API Response [ curl http://sensu-api:4567/clients/us-west-2.elb.amazonaws.com ]
{
  "timestamp":<PHONE_NUMBER>,
  "version": "0.19.2",
  "keepalives": false,
  "subscriptions": [
    "system-metrics",
    "deb-system-checks"
  ],
  "address": "unknown",
  "name": "us-west-2.elb.amazonaws.com"
}

Sensu Version
dpkg -l | grep sensu
ii  sensu                            0.19.2-1                            amd64        A monitoring framework that aims to be simple, malleable, and scalable.

You do not configure JIT clients with JSON. Your client configs are simply merging to create a single client config.

You should be able to remove 00-jit-client.json, stop the Sensu client, delete the Sensu client from the registry using the API (or dashboard), and then start the Sensu client.

Thanks, now is working


Remove base and generic prefixes from the algorithms files

I see no purpose for such a prefixes in the file names. New algorithms avoided it and it did not cause any chaos.
Split 'Basin' from 'hopping'. These are two separate words.

 Remove base and generic prefixes from the algorithms files

Why remove prefixes from some files just to add "_impl" suffixes to others? I feel like they add just as little, and I don't see what naming issue it solves to have them.

Algorithms are classes using Pascal casing, but rules share their function names with their corresponding python files. However, I included function rules into the votepy.rules scope, shadowing modules names. There is no way to get other things from these modules. I think it is more natural to import certain function rules from the votepy.rules, without additional layer.

I do however see a person going through these files, seeing an _impl file and then looking for some sort of interface that this _impl implements, just to find out there is none.

Do you prefer different suffix? _impl standed for the _implementation. What do you think about _rule suffix?

Why remove prefixes from some files just to add "_impl" suffixes to others? I feel like they add just as little, and I don't see what naming issue it solves to have them.

Algorithms are classes using Pascal casing, but rules share their function names with their corresponding python files. However, I included function rules into the votepy.rules scope, shadowing modules names. There is no way to get other things from these modules. I think it is more natural to import certain function rules from the votepy.rules, without additional layer.

Ok, I admit I didn't notice that overshadowing with the __init__ file imports, however that stems another issue, since for some rules you can import them as from votepy.rules import bloc while different implementations of CC are not visible in the voting scope at all, leading to inconsistency - and also we are not using these cleaner imports anywhere, opting for the full votepy.rules.bloc_impl name which I just think is too much (and also why I forgot we even had that). I think as a user I wouldn't want to go deeper than votepy.rules, so if we expose all actual voting functions in the rules scope, then the actual file names are not as important anymore.

I do however see a person going through these files, seeing an _impl file and then looking for some sort of interface that this _impl implements, just to find out there is none.

Do you prefer different suffix? _impl standed for the _implementation. What do you think about _rule suffix?

I think that would be better, yes.

Ok, I admit I didn't notice that overshadowing with the __init__ file imports, however that stems another issue, since for some rules you can import them as from votepy.rules import bloc while different implementations of CC are not visible in the voting scope at all, leading to inconsistency - and also we are not using these cleaner imports anywhere, opting for the full votepy.rules.bloc_impl name which I just think is too much (and also why I forgot we even had that). I think as a user I wouldn't want to go deeper than votepy.rules, so if we expose all actual voting functions in the rules scope, then the actual file names are not as important anymore.

Other implementations can be treated as implementation's details and are not part of the public API (maybe they should use __ prefix?). User have access to their functionality via the main rule function and algorithm argument (or votepy.solve).
In case of owa rules, it makes sense to keep them all under an additional owa submodule.

Changed in #39

Ok, I admit I didn't notice that overshadowing with the __init__ file imports, however that stems another issue, since for some rules you can import them as from votepy.rules import bloc while different implementations of CC are not visible in the voting scope at all, leading to inconsistency - and also we are not using these cleaner imports anywhere, opting for the full votepy.rules.bloc_impl name which I just think is too much (and also why I forgot we even had that). I think as a user I wouldn't want to go deeper than votepy.rules, so if we expose all actual voting functions in the rules scope, then the actual file names are not as important anymore.

Other implementations can be treated as implementation's details and are not part of the public API (maybe they should use __ prefix?). User have access to their functionality via the main rule function and algorithm argument (or votepy.solve).
In case of owa rules, it makes sense to keep them all under an additional owa submodule.

 We can merge this for now, but I would like to revisit at some point.


SPIKE: Frontend end-to-end testing

Describe the task
A spike of the end-to-end testing method for our frontend, maybe Cypress? Like how to do configuration, how to use it
Acceptance Criteria

[ ] Got the configuration for the end-to-end testing
[ ] Document how to use it

Cypress Spike
Advantages of Cypress

Cypress framework captures snapshots at the time of test execution that allows QAs or developers to hover over a specific command in the Command Log to see exactly what happened at any particular step;
There is no need to add explicit or implicit wait commands in test scripts, Cypress waits automatically for commands and assertions;
Developers or QAs can use Spies, Stubs, and Clocks to verify and control the behavior of server responses, functions, or timers;
The automatic scrolling operation ensures that an element is in view before performing any action (for example Clicking on a button);
Cypress currently provides support for Chrome, Firefox and Edge browsers;
As the programmer writes commands, Cypress executes them in real-time, providing visual feedback as they run;
Excellent documentation and community support.

Trade-offs

Cypress is not a general purpose automation tool;
Cypress commands run inside of a browser - which can be slower than other testing frameworks;
There will never be support for multiple browser tabs;
You cannot use Cypress to drive two browsers at the same time;
Each test is bound to a single superdomain. Cross-origin navigation inside tests can be enabled by using the cy.origin command;
Cypress doesn’t provide support for browsers like Safari and IE at the moment;
Limited support for iFrames;

Cypress Vs Vitest
Vitest is best used for headless testing. Cypress has the benefit of having browser-based test runner using real browser APIs. There will be a lot of potential issues or bugs that Cypress can cover that Vitest will not be able to.
Cypress offers more visual oriented test development at the cost of speed based on the real browser engine so it is closest it can be possibly be to the user-environment. The confidence in knowing its the closest to the user-environment is the biggest benefit of Cypress.
Installing Cypress
npm install cypress  --save-dev
Running Cypress
npx cypress open
Adding npm Scripts
Add the following line to the scripts section of the package.json file:
{
  "scripts": {
    "cypress:open": "cypress open"
  }
}

Now cypress can be invoked by  the command below from the project frontend folder:
npm run cypress:open
VSCode errors with TypeScript Typings for cy.mount() Commands
When working in TypeScript, it will be needed to add custom typings for your commands to get code completion and to avoid any TypeScript errors.
The typings need to be in a location that any code can access, therefore, it is recommend creating a cypress.d.ts file in the root directory, and use this example as a starting point for customizing your own command:
import { mount } from 'cypress/vue'

type MountParams = Parameters<typeof mount>
type OptionsParam = MountParams[1]

declare global {
  namespace Cypress {
    interface Chainable {
      mount: typeof mount
    }
  }
}

It could also be needed to manually include the cypress.d.ts file in all tsconfig.json files:
"include": ["./src", "cypress.d.ts"]

I have created a branch for this spike with Cypress installed and configured and a test example for the Landing Page:
https://github.com/bcgov/nr-forests-access-management/tree/feat/580-spike-frontend-e2e-testing

Useful links
https://docs.cypress.io/guides/getting-started/installing-cypress
https://docs.cypress.io/guides/end-to-end-testing/writing-your-first-end-to-end-test
https://docs.cypress.io/guides/component-testing/overview
https://docs.cypress.io/guides/continuous-integration/github-actions


DatatypeConverter / DatatypeConverterInterface are underspecified

It doesn't say what happens in case of an error. Does it throw an exception?
Does it just return null?
Environment
Operating System: All
Platform: All
Affected Versions
[2.0 v0.4]

If an error is encountered during conversion, then an IllegalArgumentException, or a subclass of IllegalArgumentException must be thrown by the method.


Option to strip styles

First off, thanks for this, I am a long-time RSS user (rip google reader) and dislike the modern writing-on-the-internet ecosystem's insistence on email newsletters so it solved a huge annoyance for me.
I subscribe to several email newsletters that include


amqp_trx_plugin - transaction in, transaction_trace out

Change Description
New plugin: amqp_trx_plugin

Consumes from AMQP 'trx' queue
Publishes transaction trace results to 'trace' queue with CorrelationID set to transaction id.
If option amqp-trx-publish-all-traces is specified, then all transaction traces from controller applied_transaction signal are published to the trace queue

Binary fc::pack format:
// consume message types
using transaction_msg = fc::static_variant<chain::packed_transaction_v0, chain::packed_transaction>;

// publish message types
struct transaction_trace_exception {
   int64_t error_code; ///< fc::exception code()
   std::string error_message;
};
using transaction_trace_msg = fc::static_variant<transaction_trace_exception, chain::transaction_trace>;

Change Type
Select ONE

[ ] Documentation

[ ] Stability bug fix

[ ] Other

[x] Other - special case

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

eosio::amqp_trx_plugin options

amqp-trx-address

AMQP address: Format: amqp://USER:PASSWORD@ADDRESS:PORT
Will consume from 'trx' queue and publish to 'trace' queue.

amqp-trx-exchange

Existing AMQP exchange to send transaction trace messages.

amqp-trx-publish-all-traces

If specified then all traces will be published; otherwise only traces for consumed 'trx' queue transactions.

I wonder if the more AMQPy way of doing this would be instead of the amqp-trx-exchange config, leveraging the reply-to field of a message. If you have multiple callers this allows you to send the responses back to the individual caller. I'm guessing it's not a huge problem for us in this case though since a submitter likely knows if a response was intended for itself or someone else because it's expecting a particular trxid.

If we use reply-to then we'd still need somewhere to publish transaction traces when amqp-trx-publish-all-traces is on.


API Change detection

Closes https://github.com/adobe/react-spectrum/issues/1954
✅ Pull Request Checklist:

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

📝 Test Instructions:

Pull down branch
Run yarn to get latest deps
Run yarn check-apis
wait a long time, once it's done, it'll spit out a summary of all change to the TS since the last release. above will be more granular notes on the changes. this set will be very large because Responsive Props changed a lot of API's
Of note, there are some things we know for certain, in the colored summary you will see the added and removed exports (if any) and added and removed modules (if any)
🧢 Your Project:

To merge after release


Images not displaying

Tried several books from the IDPF samples, both packaged and unpackaged, but all I get in the images tab are broken file icons.

We are getting the same behavior
Where we are getting no images is on a PC
Windows 10, with Ace GUI App 1.1.2
Exporting the Report does include the data directory with the images so that report.html does work showing the images, just not within the app itself.
On my Mac OS 14.0.3 with Ace 1.1.2 it works fine and images are displayed within the app and are exported correctly.
We are doing a training in Canada and this is making it difficult.
Thanks

Fixed via a custom protocol handler (file:// was blocked due to security restrictions in Electron):
https://github.com/daisy/ace-gui/blob/f16acdaebec27aefba61db8f2e2a44feda1911d7/src/main/main.js#L313-L319


board: emsk: fix the bug in dts

As em7d is configured with HARVARD, CCM will be used not DDR,
SRAM should point to DCCM.
This bug will cause the wrong caculation of heap area,
Signed-off-by: Wayne Ren<EMAIL_ADDRESS>

@ruuddw ,pls review and approve

Codecov Report

Merging #14811 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #14811   +/-   ##
=======================================
  Coverage   52.51%   52.51%
=======================================
  Files         309      309
  Lines       45048    45048
  Branches    10419    10419
=======================================
  Hits        23656    23656
  Misses      16584    16584
  Partials     4808     4808

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 cb44b7e...1493100. Read the comment docs.


Contribute with the localization

I would like to contribute with localization, of course, if it is of interest to you
Thanks!

Hi,
Localization pt-br is done. Other languages remain to be updated:
ar.json
bg.json
de-informal.json
de.json
en.json
es.json
fa.json
fr-informal.json
fr.json
he.json
id.json
it.json
ky.json
lt.json
nl.json
pl.json
pt.json
ro.json
ru.json
tr.json
vi.json
zh-hans.json
zh-hant.json
Dawn-master.zip

Hey @coyoterj, thanks for your support! However, we're keeping our official themes free of translation helpers and localization files in terms of simplicity. You can always add localization to your site on your end.


Submit a Cloud Definition

Do NOT copy/paste a definition from somewhere else. Read about the word you want to define and come up with your own definition. Copy/Paste submissions will be closed and not added.
Fill out the JSON with your submission:
    {
    "word": "GitHub",
    "content": "GitHub is a user-friendly web-based platform that uses the popular version control system Git to store, manage, track changes, collaborate with others and deploy software projects.",
    "learn_more_URL":"https://www.simplilearn.com/tutorials/git-tutorial/what-is-github",
    "tag":"developer tool",
    "abbreviation": "",
    "author_name":"Ifeanyi Otuonye",
    "author_link": "https://www.linkedin.com/in/ifeanyi-otuonye/"
    }

Fill out the JSON below with the following.
Word (REQUIRED)
The word you are defining. Check this URL for all words we currently have.
Content (REQUIRED)
The definition. No more than 3 sentences.
learn more URL (REQUIRED)
Website where people can visit to learn more about the word.
tag (REQUIRED and select one)
Tech category the word fits in. Options:

compute
security
service
general
analytics
developer tool
web
networking
database
storage
devops
ai/ml
identity
iot
monitoring
cost management
disaster recovery

abbreviation (OPTIONAL)
If the word is commonly abbreviated, please provide it. For example, command line interface is often abbreviated as CLI.
author name (REQUIRED)
Your name.
author link (REQUIRED)
The URL you want your name to link to.

Jeez, my system glitched before I could complete this properly.

Fixed.

Hi there!
Is the definition added from the frontend Blazor app?

Hi,
I'm not sure I understand well the question. Do you mean if got the definition from that app? Or if I used that app to create the definition, or If I used the app to submit the definition?

hi @ifeanyiro9 I've added your definition :)
@Acekhing Please checkout https://zealous-flower-0f27b070f.2.azurestaticapps.net/ for all submitted definitions.

Yeah. was asking if you use the app to submit the question. Also is it possible to submit definitions since the issue has already been assigned?

Yeah. was asking if you use the app to submit the question. Also is it possible to submit definitions since the issue has already been assigned?

@Acekhing Please open a new issue to submit a definition.


ENH: expose get_calenadar kwargs including "side" option

@gerrymanoim, would you entertain a PR that introduces a side parameter to get_calendar to determine the minutes when a calendar should be considered open? Options would be as follows with default as "both" such that existing behaviour would remain unchanged:

"left" - treat session open and break_start as open, treat session close and break_end as closed.
"right" - treat session open and  break_start as closed, treat session close and break_end as open.
"both" - treat all of session open, session close, break_start and break_end as open.
"neither" - treat none of session open, session close, break_start or break_end as open.

I feel this would give the user useful flexibility.
I've employed a hack to implement the above on something I'm working on. The implementation's fairly simple (it would also be possible to add a side option to methods such as minutes_in_range and minute_to_session_label to override the global side value for any particular call).
I'd happily offer a PR if you think a side option would be a worthy enhancement?
I notice that you previously got together a PR to expose the get_calendar start and end parameters (as referenced from #24). I could introduce this at the same time.
With regards to the cache, occurs to me to either:

ditch it
keep it but only retrieve from it if kwargs match those of the cached version, otherwise overwrite the cached version with a new calendar instance.

Thoughts?

Interesting. Originally the way exchange calendars worked was to have the first minute be treated as closed, which got changed here: https://github.com/gerrymanoim/exchange_calendars/pull/3/files and required threading that change through in a bunch of places. I don't think I have any functional issue with allowing the flexibility you're proposing, but I worry it will make testing these configurations difficult for a feature that might not have that broad of a use case (vs just having the user handle it in their own context). But I could be wrong!
get_calendar taking start and end params would be a great addition. I'm not really tied to having a cache anymore (calendar construction is reasonably fast and users that do have specific performance requirements can probably handle their own caching as well).

Thanks for the comments. I used to have an ugly module sit on top of trading_calendars to get opens/closes and minutes in the terms I was after. I've since overhauled it for exchange_calendars. I require, in most cases, for minutes to be defined on 'left' which I personally find most logical, although understand different users have different purposes. I've ended up subclassing the dispatcher to override the get_calendar method and then use types.new_class to override the affected ExchangeCalendar methods. Whilst the workaround is pretty complicated the acutal implementation is simple enough. More than once I've found myself saying 'the place for this is in exchange_calendars'.
I had similar thoughts to you regarding testing. I'm thinking I'll work on a PR, see where I get to and push it to see what you reckon(?).
With regards to the start / end parameters, I've probed the bounds of each calendar and seen that there are three main causes of dates being out-of-bounds:

A few calendars explicitly raise errors if the user tries to create a calendar outside of the dates for which the calendar is considered valid (for example, XBOM, XSHG).
Some calendars fail as a result of conflicts between rules, ususally when evaluting special dates (for example XNYS, XKLS).
Most calendars are only restricted by Timestamp.min and Timestamp.max, i.e. you could create calendars for exchanges before the exchange existed.

Having given this some thought, I wonder if the best approach would be to:

define an abstract base implementation for ExchangeCalendar subclasses to raise out-of-bounds errors.
for those calendars without defined bounds:

define default start / end dates within which calendars are considered likely to be reliable. @gerrymanoim, I guess these dates would be the current defaults? Would you have any knowledge of the date range over which quantopian intended the calendars to be accurate?
include a allow_uncharted_waters parameter to let users create calendars outside of these default limits only if they explictly acknowledge what they are asking for.

I had similar thoughts to you regarding testing. I'm thinking I'll work on a PR, see where I get to and offer it to see what you reckon(?).

Yeah - that sounds good to me. If it isn't painful to test all iterations here, I'm open to providing the flexibility.

I guess these dates would be the current defaults? Would you have any knowledge of the date range over which quantopian intended the calendars to be accurate?

I'd also guess that the defaults provide "safe" dates. IIRC quantopian had data going back to 2002-01-03 in the US - not sure about what the coverage was in other countries. My guess is these were mostly chosen arbitrarily: https://github.com/gerrymanoim/exchange_calendars/blob/master/exchange_calendars/exchange_calendar.py#L37-L41.

XBOM/XSHG look like they're raising because of https://github.com/gerrymanoim/exchange_calendars/blob/master/exchange_calendars/precomputed_exchange_calendar.py
Given that - I don't think we need to make it more complicated than the interface in https://github.com/quantopian/trading_calendars/pull/176/files. If you choose dates that break a precomputed calendar, that's a valid ValueError that we raise. Otherwise you're generally using this at your own risk (as is the case now when you accept the arbitrary start/end dates). Thoughts?

Given that - I don't think we need to make it more complicated than the interface in https://github.com/quantopian/trading_calendars/pull/176/files. If you choose dates that break a precomputed calendar, that's a valid ValueError that we raise. Otherwise you're generally using this at your own risk (as is the case now when you accept the arbitrary start/end dates). Thoughts?

Happy to keep it simple! I'll flesh out the documentation.

side option implemented in #71.


Stub out repo with default content

Let's add MAINTAINERS, LICENSE, Makefile, README to start.  Base this on the service-node-red or service-homeassistant repos.

Fixed, closing


Vertical slider is misaligned when dragging not on top of the page

As per title, vertical slider is misaligned when dragging not on top of the page

https://jsfiddle.net/82s1jat4/
v2 had realTime option which I used to fix this before, but now unavailable in v3
Browser is Firefox, haven't tested in Chrome

Thank you for your feedback, fixed in version 3.0.21.

It is indeed, thank you for the quick fix


Create presto cli history file if it doesn't exist

Docker creates an empty directory when an non-existing path is being
mounted. This behaviour can cause an error from presto cli because it
requires .presto_history to be a regular file.

It looks like you need to sign CLA.

Ping me once you are good with CLA

@kokosing CLA signed status is green now.

Merged, thanks!


Update m3x dependency

cc @robskillington @cw9
Update m3x dependency and pin the versions of some packages

Coverage increased (+0.01%) to 78.403% when pulling 36ca3e7dc3fcdcb9dfec159e2789492ea1fa231f on xichen-update-m3x into 36bac0c1565eba55fcbd9883227b59bc09277d0b on dev.


Failing to get any pull requests from remotes

Extension version: 0.52.0
VSCode Version: 1.72.2
d045a5eda657f4d7b676dedbfa7aab8207f8a075
x64
OS: Linux Ubuntu 20.04

Steps to Reproduce:

Clone repo with ssh key with SSO enabled
Get the following error:

[Info] Found GitHub remote
[Info] Unable to resolve remote: HttpError: Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization.
[Info] RateLimit> Rate limit remaining: 201
[Info] RateLimit> Rate limit remaining: 200
[Info] Found GitHub remote
[Info] Found GitHub remote
[Info] Unable to resolve remote: HttpError: Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization.
[Info] Unable to resolve remote: HttpError: Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization.
[Info] RateLimit> Rate limit remaining: 197
[Info] RateLimit> Rate limit remaining: 196
[Info] RateLimit> Rate limit remaining: 195
[Info] RateLimit> Rate limit remaining: 194

This is the same issue listed here.
https://github.com/microsoft/vscode-pull-request-github/issues/2385
This issue was closed as a fix was released. But something must be wrong as I am still having the issue. Referenced fix:
https://github.com/microsoft/vscode-pull-request-github/pull/3154

I tried the workaround listed here:
https://github.com/microsoft/vscode-pull-request-github/issues/2385#issuecomment-801761906
It didn't work. I get "Error signing in to Github".
@alexr00 Can you assist?

It looks like you're on old versions of both VS Code and the extension. Can you update both to the latest and see if the issue still happens there?


add an HTTP port

What have you changed? (mandatory)
This PR adds an HTTP port for TiKV so that Prometheus can pull the metrics from it.
What are the type of the changes? (mandatory)

New feature (non-breaking change which adds functionality)

How has this PR been tested? (mandatory)
manual tests
Refer to a related PR or issue link (optional)
Closes #3838.

yes, we need HTTPS too.

please add test for it.

OK

PTAL. @overvenus

PTAL @breeswish.

PTAL @BusyJay @breeswish

/cc #2999.

PTAL @overvenus @BusyJay

PTAL @breeswish

@overvenus @breeswish PTAL


Normalize order of PO header data lines

Ensure that the lines of a PO header are written in the same canonical
order as in a header generated by xgettext or rearranged by msgmerge.
The actual issue that this commit fixes is: When you open a .po whose
header doesn't contain a "Language:" line, such a line will be written
at save, but it will end up after the "Plural-Forms:" line. The proper
place for it is after "Language-Team:".
Such variation is not dangerous, but causes unnecessary changed lines
in commits, if a file is sometimes last modified by Poedit, sometimes by
msgmerge.

Perfect, thanks a lot for doing this!


Refactor - Structure

Design a new code structure to add features easier

Imitating the implementation of go command line


Actuators msg missing from JointPositionController

Allow for use of actuator message in JointPositionController making HIL simulation easier and models more portable.

Fixed by: #1954


build R-INLA from source without binaries

Hi,
In the directory build-user/linux/Makefile I see that some dependencies are being downloaded as binaries.
I'd like to install R-INLA from source, separately, without any binaries stepping in, while taking care of extensions myself (building them from source as well).
Is there a way to skip downloading all these dependency binary files? Also, is there a file which lists all dependencies and their versions (just like there are typically in conda-recipe/meta.yaml for anaconda or requirements.txt for pip)?
fyi, the purpose of this is to include possibility to build R-INLA with EasyBuild - see https://github.com/easybuilders/easybuild,
where we try to build everything from source - including dependencies.
thank you very much!

well... you can build it almost from source.   see hrue.r-inla-download.org/build64.tgz  which is for Fedora(33).
you have to use the taucs/amd/muparser versions of the libs in there
I set
export INLA_TAG=Version_21.01.18
and do
make update
then it builds it in local/bin
the metis5 library is not needed as its included in the pardiso lib, unless you're on Windows.
you have to include src/libpardiso.o

$ diff inlaprog/Makefile inlaprog/GNUmakefile
79c79
< OBJ = src/inla.o src/dictionary.o  src/iniparser.o  src/strlib.o src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-interface.o src/fgn.o src/quantile-regression.o src/my.o src/stochvol.o src/xerbla.o src/libpardiso.o src/tweedie.o

OBJ = src/inla.o src/dictionary.o  src/iniparser.o  src/strlib.o src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-interface.o src/fgn.o src/quantile-regression.o src/my.o src/stochvol.o src/xerbla.o src/tweedie.o ##src/libpardiso.o

if you do not link with the PARDISO library, and define -DNO_PARDISO_LIB when compiling.
you also need to set cpp var if you link with openblas or Intel MKL; see the Makefile. By default, it will compile both.
I hope this is useful. Its a little messy, and we should rewrite this build system. I know...
H

well... you can build it almost from source.   see hrue.r-inla-download.org/build64.tgz  which is for Fedora(33).
you have to use the taucs/amd/muparser versions of the libs in there
I set
export INLA_TAG=Version_21.01.18
and do
make update
then it builds it in local/bin
the metis5 library is not needed as its included in the pardiso lib, unless you're on Windows.
you have to include src/libpardiso.o

$ diff inlaprog/Makefile inlaprog/GNUmakefile
79c79
< OBJ = src/inla.o src/dictionary.o  src/iniparser.o  src/strlib.o src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-interface.o src/fgn.o src/quantile-regression.o src/my.o src/stochvol.o src/xerbla.o src/libpardiso.o src/tweedie.o

OBJ = src/inla.o src/dictionary.o  src/iniparser.o  src/strlib.o src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-interface.o src/fgn.o src/quantile-regression.o src/my.o src/stochvol.o src/xerbla.o src/tweedie.o ##src/libpardiso.o

if you do not link with the PARDISO library, and define -DNO_PARDISO_LIB when compiling.
you also need to set cpp var if you link with openblas or Intel MKL; see the Makefile. By default, it will compile both.
I hope this is useful. Its a little messy, and we should rewrite this build system. I know...
H

@hrue I'm working together with @deniskristak on this, and we would really like to get a full from-source build working, where we don't use any pre-built libraries. Most of the required dependencies (BLAS/LAPACK via OpenBLAS or MKL, SuiteSparse, METIS, GSL, libRmath, muParser) are already supported in EasyBuild, so we would use those installations (not the ones coming from Fedora or Ubuntu).
We have a lot of experience with complex installations that involve lots of dependencies, so I think we should be able to get this fully working (and make it easy for others to install R-INLA from source).
I think we're slowly figuring things out, but we need some help...
A couple of things we ran into aren't fully clear to use yet:

We plan to use a clone of this repository, at a specific tag (like 21.03.31), as a starting point for the from-source installation, does that make sense?

It looks like the build-user/linux/Makefile specifies to full install procedure, and we should mainly focus on the make bin part of it, which builds taucs, fmesher, GMRFLib, and finally inla. Most of those are basic make/make install procedures, so that shouldn't be too difficult... Is that correct?

For taucs, it seems like you're using a patched version, so we should also use the source tarball available in extlibs?

Do we also need to use the muparser_v2_2_3-with-gamma.tgz tarball in that same directory, or is it OK to use the latest muparser 2.2.5 ?

Can you clarify why $INLA_TAG needs to be set, and where that is picked up?

In which Makefile is it specified that R-INLA is built on top of OpenBLAS or MKL? We want to just build for one of those (at a time).

What's the relevance of the PARDISO library, how is R-INLA different when built with(out) it? And how does that affect the METIS dependency exactly?

How do you recommend we test the resulting R-INLA installation?

Hi.
my comments are below. If there is anything else, let me know
Best
Håvard
On Wed, 2021-04-07 at 03:20 -0700, Kenneth Hoste wrote:
@hrue I'm working together with @deniskristak on this, and we would really like to get a full from-source build working, where we don't use any pre-built libraries. Most of the required dependencies (BLAS/LAPACK via OpenBLAS or MKL, SuiteSparse, METIS, GSL, libRmath, muParser) are already supported in EasyBuild, so we would use those installations (not the ones coming from Fedora or Ubuntu).
We have a lot of experience with complex installations that involve lots of dependencies, so I think we should be able to get this fully working (and make it easy for others to install R-INLA from source).
I think we're slowly figuring things out, but we need some help...
A couple of things we ran into aren't fully clear to use yet:

We plan to use a clone of this repository, at a specific tag (like 21.03.31), as a starting point for the from-source installation, does that make sense?

All tags like Version_21.03.31 defines a build of the package (or a try to in some cases) and this is the one you'll find the the R package INLA_21.03.31

It looks like the build-user/linux/Makefile specifies to full install procedure, and we should mainly focus on the make bin part of it, which builds taucs, fmesher, GMRFLib, and finally inla. Most of those are basic make/make install procedures, so that shouldn't be too difficult... Is that correct?

I'm not sure it really updated, but I uploaded my build directory on my Fedora33 laptop to
hrue.r-inla-download.org/build64.tgz
and you can go from there.
at top, you'll make 'amd' 'muparser_v2_2_3' 'taucs-2.2--my-fix'
which is my patched libraries.
you can use a newer muparser I guess, I just added some more gamma functions to it (and I do not think its really in use...)
src/muParser.cpp- //---------------------------------------------------------------------------
src/muParser.cpp- // misc
src/muParser.cpp: value_type Parser::Lgamma(value_type v) { return lgamma((double)v); }
src/muParser.cpp: value_type Parser::Gamma(value_type v) { return tgamma((double)v); }
src/muParser.cpp: value_type Parser::Digamma(value_type v) { return digamma((double)v); }
src/muParser.cpp: value_type Parser::Trigamma(value_type v) { return trigamma((double)v); }
src/muParser.cpp-
src/muParser.cpp- value_type Parser::Exp(value_type v) { return MathImpl<value_type>::Exp(v); }
src/muParser.cpp- DefineFun(_T("max"), Max);
src/muParser.cpp-
src/muParser.cpp: DefineFun(_T("gamma"), Gamma);
src/muParser.cpp: DefineFun(_T("lgamma"), Lgamma);
src/muParser.cpp: DefineFun(_T("digamma"), Digamma);
src/muParser.cpp: DefineFun(_T("trigamma"), Trigamma);

For taucs, it seems like you're using a patched version, so we should also use the source tarball available in extlibs?

yes

Do we also need to use the muparser_v2_2_3-with-gamma.tgz tarball in that same directory, or is it OK to use the latest muparser 2.2.5 ?

see above

Can you clarify why $INLA_TAG needs to be set, and where that is picked up?

I do from shell
export INLA_TAG="Version_21.03.31"
make update
which will 'git pull' and switch to that tag, and set some GIT cpp variables which is added using 'gcc -D...'
you can do INLA_TAG=devel  f.example

In which Makefile is it specified that R-INLA is built on top of OpenBLAS or MKL? We want to just build for one of those (at a time).

If you will link with OpenBLAS then compile with
-DINLA_LINK_WITH_OPENBLAS
and
-DINLA_LINK_WITH_MKL
for MKL.  There is a function call in openmp.c hat depends on this, and for simplicity I just compile twice. Maybe there is a way to get around it, but...

What's the relevance of the PARDISO library, how is R-INLA different when built with(out) it? And how does that affect the METIS dependency exactly?

tricky. PARDISO is a by far better parallel sparse solver, which require a license to run, which is free for academic++, so I only have access to
a prebuildt version.
The TAUCS library was stopped develloped in about 2003 or so, and is the default one. The PARDISO is faaar better and the only option that scales well to larger models, and runs in parallel etc
by default, the library will not link with PARDISO and a 'fake' PARDISO library is included to account for it, inlaprog/src/libpardiso.c
so I override 'Makefile' with a local copy 'GNUmakefile' to comment out this file from the build:
$ pwd
~/builds/build64/r-inla/inlaprog
@.@.>([tag-Version_21.03.31]): ~/builds/build64/r-inla/inlaprog
$ diff GNUmakefile Makefile
79c79
< OBJ = src/inla.o src/dictionary.o src/iniparser.o src/strlib.o src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-interface.o src/fgn.o src/quantile-regression.o src/my.o src/stochvol.o src/xerbla.o src/tweedie.o ##src/libpardiso.o

OBJ = src/inla.o src/dictionary.o src/iniparser.o src/strlib.o src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-interface.o src/fgn.o src/quantile-regression.o src/my.o src/stochvol.o src/xerbla.o src/libpardiso.o src/tweedie.o

PARDISO comes with its own version of the METIS library, so linking with that one does not require linking with METIS, which you otherwise must link with.

How do you recommend we test the resulting R-INLA installation?

do some of the demos in the R-INLA package, like
inla.setOption(inla.call="path to your binary")
demo(Bym)
etc
--
Håvard Rue
Professor of Statistics
Statistics Program, CEMSE Division
King Abdullah University of Science and Technology
Thuwal 23955-6900, Saudi Arabia
Email: @.***
Office: +966 (0)12 808 0640
Mobile: +966 (0)54 470 0421
Research group: bayescomp.kaust.edu.sa
R-INLA project: www.r-inla.org
Zoom: kaust.zoom.us/my/haavard.rue

I also link with jemalloc library, which has a HUGE impact for some
models on the speed.
On Wed, 2021-04-07 at 20:05 +0300, Haavard Rue wrote:

Hi.
my comments are below. If there is anything else, let me know
Best
Håvard
On Wed, 2021-04-07 at 03:20 -0700, Kenneth Hoste wrote:
All tags like Version_21.03.31 defines a build of the package (or a
try to in some cases) and this is the one you'll find the the R
package INLA_21.03.31
I'm not sure it really updated, but I uploaded my build directory on
my Fedora33 laptop to
hrue.r-inla-download.org/build64.tgz
and you can go from there.
at top, you'll make 'amd' 'muparser_v2_2_3' 'taucs-2.2--my-fix'
which is my patched libraries.
you can use a newer muparser I guess, I just added some more gamma
functions to it (and I do not think its really in use...)
src/muParser.cpp- //--------------------------------------------------
src/muParser.cpp- // misc
src/muParser.cpp: value_type Parser::Lgamma(value_type v) { return
lgamma((double)v); }
src/muParser.cpp: value_type Parser::Gamma(value_type v) { return
tgamma((double)v); }
src/muParser.cpp: value_type Parser::Digamma(value_type v) { return
digamma((double)v); }
src/muParser.cpp: value_type Parser::Trigamma(value_type v) { return
trigamma((double)v); }
src/muParser.cpp-
src/muParser.cpp- value_type Parser::Exp(value_type v) { return
MathImpl<value_type>::Exp(v); }
src/muParser.cpp- DefineFun(_T("max"), Max);
src/muParser.cpp-
src/muParser.cpp: DefineFun(_T("gamma"), Gamma);
src/muParser.cpp: DefineFun(_T("lgamma"), Lgamma);
src/muParser.cpp: DefineFun(_T("digamma"), Digamma);
src/muParser.cpp: DefineFun(_T("trigamma"), Trigamma);
yes
see above
I do from shell
export INLA_TAG="Version_21.03.31"
make update
which will 'git pull' and switch to that tag, and set some GIT cpp
variables which is added using 'gcc -D...'
you can do INLA_TAG=devel  f.example
If you will link with OpenBLAS then compile with
-DINLA_LINK_WITH_OPENBLAS
and
-DINLA_LINK_WITH_MKL
for MKL.  There is a function call in openmp.c hat depends on this,
and for simplicity I just compile twice. Maybe there is a way to get
around it, but...
tricky. PARDISO is a by far better parallel sparse solver, which
require a license to run, which is free for academic++, so I only have
access to
a prebuildt version.
The TAUCS library was stopped develloped in about 2003 or so, and is
the default one. The PARDISO is faaar better and the only option that
scales well to larger models, and runs in parallel etc
by default, the library will not link with PARDISO and a 'fake'
PARDISO library is included to account for it,
inlaprog/src/libpardiso.c
so I override 'Makefile' with a local copy 'GNUmakefile' to comment
out this file from the build:
$ pwd
~/builds/build64/r-inla/inlaprog
@.***([tag-Version_21.03.31]): ~/builds/build64/r-
inla/inlaprog
$ diff GNUmakefile Makefile
79c79
< OBJ = src/inla.o src/dictionary.o src/iniparser.o src/strlib.o
src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o
src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-
interface.o src/fgn.o src/quantile-regression.o src/my.o
src/stochvol.o src/xerbla.o src/tweedie.o ##src/libpardiso.o

OBJ = src/inla.o src/dictionary.o src/iniparser.o src/strlib.o
src/my-fix.o src/spde.o src/spde2.o src/spde3.o src/eval.o
src/interpol.o src/re.o src/ar.o src/bessel.o src/pc-priors.o src/R-
interface.o src/fgn.o src/quantile-regression.o src/my.o
src/stochvol.o src/xerbla.o src/libpardiso.o src/tweedie.o

PARDISO comes with its own version of the METIS library, so linking
with that one does not require linking with METIS, which you otherwise
must link with.
do some of the demos in the R-INLA package, like
inla.setOption(inla.call="path to your binary")
demo(Bym)
etc

--
Håvard Rue
Professor of Statistics
Statistics Program, CEMSE Division
King Abdullah University of Science and Technology
Thuwal 23955-6900, Saudi Arabia
@.***
Office: +966 (0)12 808 0640
Mobile: +966 (0)54 470 0421
Research group: bayescomp.kaust.edu.sa
R-INLA project: www.r-inla.org
Zoom: kaust.zoom.us/my/haavard.rue

If build-user/linux/Makefile is not the latest version of the build procedure, is there another script/Makefile included in the repository that describes all the steps?
We can check the contents of hrue.r-inla-download.org/build64.tgz  for inspiration (if it includes useful stuff next to what's here in the repository), but we can't rely on it since it's not clear which version of R-INLA it provides, how it was built, on which OS, etc.

The makefile in the build64.tgz file is essentially a newr version of the build-user linux makefile. I started working on re-integrating the feautres into the version in the repository, but haven't had time to finish that. In both cases, the file is mostly a wrapper for the individual makefiles in the inlaprog and gmrflib folders of the repository, plus extra compiler flags for finding the libraries and so on.
I also started looking at adding a cmake system to help the builds and clean up the configurations, but again, I haven't had time to work on that recently.

I have a modified version of the build64.tgz makefiles that works more locally to build from a local clone of the gihub repository instead of downloading from github, to enable development testing on my own system. It would be nice to have more of this in the repository itself, to ensure the make system stays in sync with the code, and to support rebuilding older versions more easily, but I haven't had time to work on this in quite a while.

On Wed, 2021-04-07 at 10:44 -0700, Kenneth Hoste wrote:

If build-user/linux/Makefile is not the latest version of the build
procedure, is there another script/Makefile included in the repository
that describes all the steps?

its all there. this is the one I use to compile on Fedora33, and they
are all the same up to some compiler options.
For mac its the same and also windows (which I cross compile from Linux)

We can check the contents of hrue.r-inla-download.org/build64.tgz for
inspiration (if it includes useful stuff next to what's here in the
repository), but we can't rely on it since it's not clear which
version of R-INLA it provides, how it was built, on which OS, etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

--
Håvard Rue
Professor of Statistics
Statistics Program, CEMSE Division
King Abdullah University of Science and Technology
Thuwal 23955-6900, Saudi Arabia
@.***
Office: +966 (0)12 808 0640
Mobile: +966 (0)54 470 0421
Research group: bayescomp.kaust.edu.sa
R-INLA project: www.r-inla.org
Zoom: kaust.zoom.us/my/haavard.rue

As a continuation of this topic, I need to be able to build R-INLA with PARDISO support from source, as the binaries fail on RHEL8 due to its binary build targeting libraries not on the system:
If I try to use the binary version of INLA_22.05.07 (upgraded from 21.05.02) under R-4.0.4, I get:
> inla.pardiso.check()
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /tmp/terjekv/tmp-installs/R-INLA-21.05.02-
foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /tmp/terjekv/tmp-installs/R-INLA-21.05.02-
foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3)
character(0)
attr(,"status")
[1] 1
Warning message:
In system(paste(shQuote(inla.call.no.remote()), "-m pardiso"), intern = TRUE) :
  running command ''/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl.run' -m pardiso' had status 1

If I try upgrade to the testing version INLA_22.12.12-2 I get:
> inla.pardiso.check()
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/first/libRmath.so.1)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/first/libR.so)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libgsl.so.23)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/first/libpardiso.so)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libgfortran.so.5)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libicuuc.so.66)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libicui18n.so.66)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libmvec.so.1)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/first/libRmath.so.1)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/first/libR.so)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libgsl.so.23)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/first/libpardiso.so)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libgfortran.so.5)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libicuuc.so.66)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libicui18n.so.66)
/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/libmvec.so.1)
character(0)
attr(,"status")
[1] 1
Warning message:
In system(paste(shQuote(inla.call.no.remote()), "-m pardiso"), intern = TRUE) :
  running command ''/tmp/terjekv/tmp-installs/R-INLA-21.05.02-foss-2020b-R-4.0.4.eb/software/R-INLA/21.05.02-foss-2020b-R-4.0.4/INLA/bin/linux/64bit/inla.mkl.run' -m pardiso' had status 1

Would it be possible to provide instructions for adding PARDISO to the building of R-INLA from source?

On Wed, 2021-04-07 at 10:44 -0700, Kenneth Hoste wrote: If build-user/linux/Makefile is not the latest version of the build procedure, is there another script/Makefile included in the repository that describes all the steps?
its all there. this is the one I use to compile on Fedora33, and they are all the same up to some compiler options. For mac its the same and also windows (which I cross compile from Linux)
…

@hrue Should INLA be first built outside of R and then linked into R package? Asking, since rinla has no sources in it.
(Using any binaries is not acceptable option.)

@barracuda156 Yes, one has to first build the binaries, place them in the needed folders (the build scripts I use do that, and I think the ones discussed by @hrue does that as well) and then build the R package.

You can download as described in r-inla.org
After install, you can do
library(INLA)
inla.binary.install()
once only after each upgrade, to chose Fedora 37 builds, which are then
downloaded and installed.
On Tue, 2023-05-02 at 05:19 -0700, NewUser36 wrote:

Hello @finnlindgren, I am trying to install INLA, and unfortunately
since the package is not available on CRAN, the only way I can install
INLA on my computer is by downloading the source code and compiling it
myself.
I am new to compiling packages and I would like to know if there is a
step-by-step guide I could follow on how to compile R-INLA in order to
use the library in R. I have looked online but I haven't been able to
make anything work (I'm not sure which makefile I should use, or
something else entirely...)
I have downloaded the zip file for the code at this commit :
https://github.com/hrue/r-inla/tree/dabdf621046e6fcb22d818d288c679bdb2c938ee
. Which makefile should I use to compile? Is it the one in build-
user/linux, or the one in the first available folder?
I am on Fedora 37 and R 4.2.3.
Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Håvard Rue
Professor of Statistics
Chair of the Statistics Program
CEMSE Division
King Abdullah University of Science and Technology
Thuwal 23955-6900
Kingdom of Saudi Arabia
@.***
Office: +966 (0)12 808 0640
Mobile: +966 (0)54 470 0421
Research group: bayescomp.kaust.edu.sa
R-INLA project: www.r-inla.org
Zoom: kaust.zoom.us/my/haavard.rue
--
This message and its contents, including attachments are intended solely
for the original recipient. If you are not the intended recipient or have
received this message in error, please notify me immediately and delete
this message from your computer system. Any unauthorized use or
distribution is prohibited. Please consider the environment before printing
this email.

Thanks for your answer, but downloading as explained in https://www.r-inla.org/download-install is not an option, since I do not have access to internet from rstudio on my work computer, which is why I wanted to compile and build everything myself.

If you do not have access to internet from rstudio, then you can
download at some other location,
https://inla.r-inla-download.org/R/stable/src/contrib/INLA_23.04.24.tar.gz
the default binary build is Ubuntu-2004, which will also run on Fedora.
Then you just do
R CMD INSTALL ./INLA_23.04.24.tar.gz

from the cmd line
On Tue, 2023-05-02 at 05:37 -0700, NewUser36 wrote:

Thanks for your answer, but downloading as explained in
https://www.r-inla.org/download-install is not an option, since I do
not have access to internet from rstudio on my work computer, which is
why I wanted to compile and build everything myself.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Håvard Rue
Professor of Statistics
Chair of the Statistics Program
CEMSE Division
King Abdullah University of Science and Technology
Thuwal 23955-6900
Kingdom of Saudi Arabia
@.***
Office: +966 (0)12 808 0640
Mobile: +966 (0)54 470 0421
Research group: bayescomp.kaust.edu.sa
R-INLA project: www.r-inla.org
Zoom: kaust.zoom.us/my/haavard.rue
--
This message and its contents, including attachments are intended solely
for the original recipient. If you are not the intended recipient or have
received this message in error, please notify me immediately and delete
this message from your computer system. Any unauthorized use or
distribution is prohibited. Please consider the environment before printing
this email.


Toogle View button displays listings with same price in random order

Toogle View button displays listings with same price in random order. They should be always in same order. This is seen only when visiting other vendor store, on both views. Can't reproduce this when visiting my own store.
Example: ob://QmNXuCT38vxa3dsows3tVcgxPod4DbLksh2czaPPHwmo9u/store

I can't reproduce this issue.


Prevent second 'Enter' or double click when sending messages

Currently in the Inbox, a system user is able to send a message twice (or even three times) if they accidentally click the Send button more than once or press Enter more than once.
We should disable this so that users are prevented from accidentally resending the same message within a few seconds. We could possibly run a script in the background to block the button from being clicked multiple times, possibly within 3 or 5 seconds - happy to discuss this.

A good solution would be to prevent any action to happen when the user clicks on the send button when the input, the templates and selected reply are empty (which means that there isn't anything to send)


Support GHC 9.6.1 and base <IP_ADDRESS>.

Fixed (in principle) by #19, but leaving this issue open until it's possible to add GHC 9.6.1 to the CI build matrix.
(It's currently not possible to build with GHC 9.6.1 without also specifying --allow-newer, as some dependencies still require base < 4.18.)

Fixed by #21.


[DON'T MERGE] Initialization before start proposing

I added an initialization phase to make sure the node is synced before it tries to propose. This hopefully would solve #2642.

This would be closed since a better solution is implemented in #2676


chore(compiler-sfc): enhanced :deep warnings

close: #8313

Why not just modify the text directly?
Change to:
The usage of :deep or ::v-deep as a combinator has been deprecated. Please use :deep() instead.


Finalizing the LupIO Devices

This is the cleaned up version of the current LupIO devices we support in gem5.  The only things not currently added in this pull request is the LupIO-IPI/SMP support, which we are currently finishing up, and the LupIO-SYS device, which I'm just trying to finish fixing some device tree issues with.  At every point in which a device is added to the LupVBoard, it should be able to run, given that the correct disk image and bootloader are provided.  The updated instructions on how to run this LupVBoard are in the README here (https://github.com/darchr/lupio-gem5/blob/configs/README.md), and the only file necessary from the lupio-gem5 repository to run the LupVBoard is the run_riscv.py file on the configs branch.  Once all these changes are finalized, these 6 devices should be ready to push upstream while we finish the last 2.  The only thing I wasn't sure about at this point was if we want to include the run_riscv.py file within gem5 itself, and if so, where.

I added the LupIO-SYS device, so now the LupIO device collection should be complete within gem5! The only thing I was concerned about with the system controller is that it's supposed to be implemented as a write-only device, but running the poweroff -f command within the simulation is causing a read to be issued to the device.  I currently have it implemented so that the read and write functions are identical so it runs, but I wanted a second look at the code in case there was some reason I missed that's causing the device to be read from, instead of written to.

I added the LupIO-SYS device, so now the LupIO device collection should be complete within gem5! The only thing I was concerned about with the system controller is that it's supposed to be implemented as a write-only device, but running the poweroff -f command within the simulation is causing a read to be issued to the device. I currently have it implemented so that the read and write functions are identical so it runs, but I wanted a second look at the code in case there was some reason I missed that's causing the device to be read from, instead of written to.

Thanks for bringing this up. I looked at the Linux kernel device driver for this device (it's a generic driver) and it does issue a read before writing a value. That's because, by default, it allows to only update certain bits to the system controller. Anyway, I've improved the specs to mention that reads are allowed, and they should return 0: https://gitlab.com/luplab/lupio/lupio-specs/-/blob/main/lupio-sys.md.


Add "duplicate import name" and "missing default export" diagnostics

addressing #182
Changes

Add TypeCheckError::DuplicateImportName for reporting diagnostics on importing using an already imported name
Add TypeCheckError::NoDefaultExport for reporting diagnostics on missing, but expected default exports

Examples
// test1.ts
import x from "./test2";
import y, { z } from "./test3";

$ cargo run check ../dump/test1.ts
error:
  ┌─ ../dump/test1.ts:1:8
  │
1 │ import x from "./test2";
  │        ^ Cannot find default export from module './test2'

// test1.ts
import { x } from "./test2";
import x, { z } from "./test3";

$ cargo run check ../dump/test1.ts
error:
  ┌─ ../dump/test1.ts:2:8
  │
1 │ import { x } from "./test2";
  │          - Existing import with same name
2 │ import x, { z } from "./test3";
  │        ^ Cannot import using conflicting name

// test1.ts
import { x as z } from "./test2";
import y, { z } from "./test3";

$ cargo run check ../dump/test1.ts
error:
  ┌─ ../dump/test1.ts:2:13
  │
1 │ import { x as z } from "./test2";
  │          ------ Existing import with same name
2 │ import y, { z } from "./test3";
  │             ^ Cannot import using conflicting name

Appendix

test2.ts
const x: string = "x";

export { x };

test3.ts
const y: string = "y";

export default y;
export const z: string = "z";

Looks good! Diagnostics are great (+1 for labels!) and no more todo!s in modules.rs 🎉
Three things before merge:
Now that functionality exists you can add new tests to specification.md.
For the Cannot find default export from module I would modify https://github.com/NitantP/ezno/blob/import-export-diags/checker/specification/specification.md#import-where-export-does-not-exist to include it
The markdown test becomes something like
```ts
import b, { a } from "./export";

console.log(a.prop);

// in export.ts
export const c = 2;
```

- a not exported from ./export
- Cannot find default export from module './export'

For Existing import with same name you can then add a new test just after https://github.com/NitantP/ezno/blob/import-export-diags/checker/specification/specification.md#import-where-export-does-not-exist with the code in the PR description.
and secondly the CI has flag up three clippy errors: https://github.com/kaleidawave/ezno/actions/runs/10435687493/job/28905892637?pr=192#step:5:187
Just some simple things like renaming _existing to existing and merging the match branches.

Ignore the fuzzing_checker that error is not from this PR

After the two tests are modified/added + clippy errors fixed then should be good to merge!

Thanks, @kaleidawave! I've fixed the clippy errors and extended the specification tests to cover the new diagnostics.

Awesome, all passing! Nice PR. Might build a release this week so will be in a release soon!


Fixed latex

I noticed that there was a warning when we built the latex.
This change fixes the warning.

Thank you @nicholaslegrand102


React with material-ui v1+ and material-ui-datetime-range-picker not work together.

Hi! I'musing react 16 with material-ui v1.3.
And I have to use MuiThemeProvider:
const AppRoot = () => {
  return (
    <MuiThemeProvider theme={ theme }>
      <App />
    </MuiThemeProvider>
  );
};

const StyledAppRoot = withStyles(globalStyle)(AppRoot);

const render = () => {
  ReactDOM.render(
    <Provider store={ store }>
      <ConnectedRouter history={ history }>
        <StyledAppRoot />
      </ConnectedRouter>
    </Provider>,
    MOUNT_NODE
  );
};

I tried to install and use material-ui-datetime-range-picker and have got error:
TypeError: Cannot read property 'prepareStyles' of undefined.

How can I fix it?

Sorry. You support only material-ui 0.20 version :(

While the material-ui-datetime-range-picker is written from the 0.20 version code, you should be able to use it in a project that uses material-ui v1. My project uses v1 inside of a v0.20 MuiThemeProvider so maybe that's the difference? If you could show me how you are trying to use it, I might be able to figure out what's going on.

Hello. Would like to use that component. Started project from scratch using react starter, added the material core dependency and there is no MuiThemeProvider.


Remove .table-dark as table variant

Remove .table-dark as color variant. .table-dark was already used for inverted tables.
Closes https://github.com/twbs/bootstrap/issues/27879

I thought it would change either name to fix conflicts.

I thought it would change either name to fix conflicts.

I agree this would be a better solution

Ideas of the name:

table-highlight-{theme} and table-active
table-variant-{theme} and table-active
table-data-{theme} and table-active

Why not just rename .table-dark to .table-inverted?

Or even better: remove .table-dark entirely since you can do the same with other utility classes?

You can't use the current utility classes to change the border colors. On the other hand, it's not that user friendly if you need to add classes to each cell to override border colors.

I thought it would change either name to fix conflicts.

Any suggestions on this approach? I chose to remove the dark variant since the dark, active and secondary table variants look quite alike.

Any suggestions on this approach? I chose to remove the dark variant since the dark, active and secondary table variants look quite alike.

Please see my above comment.

My point was: do we really need this many shades of gray? https://codepen.io/MartijnCuppens/pen/dyoOpNV

The gray active and secondary are just by default colors. Users can customize the colors, but dark is dark for everyone.

For example, we need to consider users who have active light blue and secondary pink.

Wondering if we can nix the .table-dark that inverts things for a series of utilities:

.bg-dark for the background-color
.text-white for the color change
Add new border color utilities

Thoughts?

Alternate approach opened up at #30342.


Processed Data Files Path Issue

When I create the Datasets from Windows and run the Tests from Mac there is a Problem with finding the Files since the paths behave different between Unix and Windows. Error Code when running the tests:
E           FileNotFoundError: [Errno 2] No such file or directory: 'c:\users\lennart\documents\github\mlops_project\data\external\lego_dataset/test/001.jpg'
E           FileNotFoundError: [Errno 2] No such file or directory: 'c:\users\lennart\documents\github\mlops_project\data\external\lego_dataset/marvel/0001/002.jpg'
E           FileNotFoundError: [Errno 2] No such file or directory: 'c:\users\lennart\documents\github\mlops_project\data\external\lego_dataset/star-wars/0013/004.jpg'
the first part of the Path that's looked up contains a windows path and the second correctly a unix path.

Issue resolved on Merge Unit testing #19 into main


Add an API and Console page to manage linked topic subscriptions

Currently there's no way to manage topic subscriptions, outside of the messaging clients. It'd be useful to have this feature, so that subscriptions could be statically configure together with addresses (topics). This is just a placeholder for this feature request.

@grs I think we can go ahead and close this issue, we have topic subscriptions fully implemented, is there any more to be done for this ?

@RH-sdavey nothing for which there is not another issue, so I agree we can close this