A few observations.

I had a run through with this model classifying comments on a petition that had a lot of traction with antivaxers. The results where pretty mixed.
Some observations.
The model really needs an initial classifier to be run trained to ask a more basic question "Is this comment about covid at all?" I found it gave negative or positive classifiers to comments that really didnt apply (Ie one stating something to the effect of "I havent seen my family in a year because of border restrictions" which I , or the algorithm, really has no way of evaluating for truthfulness).
This is to be expected, as the model is for classifying covid statements and thus has no real frame of reference for dealing with statements that arent actually about covid per se.
What I DID notice, is of those misclassified statements, it seems to be honing in on the hostility of the statements. As the petition is largely about dropping australian border restrictions and vaccine mandates, its to be expected that a large number of signers are antivax activists who have had a a tendency to be somewhat aggressive.  That has me wondering if the model is actually responding to the tone of 'voice' in the comments, producing strong "false" or "misleading" signals if the input text is aggressive in nature?
edit: Oh and further context, the petition was one claiming to be "West australian doctors", a quick plugging in of names into the registar of medical practicioners revealed that the majority of signers are not actually medical practicioners (and worse, theres some evidence that of those that are, at least some might have had their names entered onto the petition without consent w/ data coming from the registry of practicioners) or are practitioners from non-medical fields like chiropractors and other pseudoscience professions, so I'm not sure how that impacts on the result. Perhaps the algorithm is picking up untruthfulness signals that I'm missing myself.

responding to the tone of 'voice' in the comments, producing strong "false" or "misleading" signals if the input text is aggressive in nature?

Sometimes a thorough error analysis is very insightful! Problematic errors are systematic errors and it's important to reveal them/know how they impact the summary statistics.
In general, your definition of "fake" might also overlap partially with "non-rational"/agitated/ALL CAPS comments. So it's worth to conduct a similar analysis on your annotation set. Larger models usually require fewer samples to get to a decent accuracy level, so you might be able to clean your annotation data a bit as well (as long as you're not introducing another bias). This usually has a positive impact on scores because your objective is clearer.
Just some thoughts - good luck with the analysis.

Following up on Martins comments here.
Firstly, the COVID-TWITTER-BERT is starting to get a bit old. It was trained in the beginning of the pandemic. It still does "think" that Malone is a basketball player and that alpha, delta and omikron are letters in the greek alphabet. In some cases the stance/sentiment in a sentence requires you to know the meaning of these words. To fix this, one would have to do some additional pretraining on additional (unannotated) data. Not sure if it would have real impact in your case, just something you should think about.
Another comment is that is the possibility that the model is picking up the "tone of voice" as you describe it during finetuning. Take a minute to think about the process of finetuning a classification task. Lets say you have the task of pro/anti vaccine.  In real life, a lot of these categorisations are really hard. Inter-rater reliability on tasks like this is typically below 0.8. Then you are finetuning your model on this. However, you are no longer finetuning on pro vs anti vaccine.  There are a lot of other ways of recreating these piles, for instance the use of specific words, or their anger, or their use of CAPS LOCK.
There are ways of getting around this problem. One approach is to do the classification target specific (where you hint to the label of the piles to give the classificator a hint about what you are looking for). Another approach is not to train on the classification task, but instead view this as a logical task. We have made an mnli-version of the model that can be used for that.
Best of luck with the competition!


Sprite animation stop before new httprequest

Sprite animation is stopping before the new HTTP request. So I am having 1 frame display for 10 to 20 seconds before new weather information comes in. Trying to find a work around.

Solved but now gstate can change while sprite animation is playing - trying different solutions.

Cleared by extending sprite animation passtime


Ctrl-Shift-v does not work.

Ctrl-Shift-v does not work. I tried to paste text in the computer clipboard to the device, but Ctrl-Shift-v pasted the text in the device clipboard not in the computer clipboard. ("[server] INFO: Device clipboard set" is logged.) I'm using v1.14 on arch linux and android 10. Thanks for the great app!.

Ctrl-Shift-v pasted the text in the device clipboard not in the computer clipboard.

The computer clipboard is updated as soon as the device clipboard changes. So in fact you actually pasted the computer clipboard (which contained the same content as the device clipboard).

The computer clipboard is updated as soon as the device clipboard changes.

I'm not sure what do you mean. Here is what I experienced.

Copy text "copied in the device" in a web browser running in the device by long click and select "copy" (not real device, the screen mirrored to the computer).
Copy text "copied in the computer" in a text editor running in the computer using Ctrl-c.
Click the address bar of the web browser running in the device (again in the mirrored screen) and type Ctrl-Shift-v. This pastes "copied in the device" to the address bar.

I expected "copied in the computer" is pasted as

Ctrl+Shift+v copies the computer clipboard to the device clipboard (and pastes if the device runs Android >= 7)

written in the README. Do I misunderstand the use of Ctrl-Shit-v or is it a bug?

Click the address bar of the web browser running in the device (again in the mirrored screen) and then type Ctrl-Shift-v. This pastes "copied in the device" to the address bar.

I could not reproduce, on my device it pastes copied in the computer.
Anyway, the behavior will probably be changed (again) in the next version. Could you please test #1465?


Create Typescript type definitions

Please publish Typescript type definitions
(4,32): Could not find a declaration file for module 'react-firebaseui/StyledFirebaseAuth'. '/Users/me/myproject/node_modules/react-firebaseui/StyledFirebaseAuth.js' implicitly has an 'any' type.
  Try `npm install @types/react-firebaseui` if it exists or add a new declaration (.d.ts) file containing `declare module 'react-firebaseui';`

+1

I am still in the prototyping step of my project if it goes into production, I will gladly contribute.
Is there a specific reason to do the PR in DefinitelyTyped rather than here ? For instance, firebaseui-web has it included.

I guess Including it in react-firebaseui would save users the trouble of having to install it separately. There could also be some maintenance benefits from including it in the main codebase.

+1

Yea sure, I'm totally fine including it directly into react-firebaseui too :)

Any updates on this?

I'm still waiting for a volunteer to send a PR :)


Latest updates

mobile menu dropdown transition
Top places is responsive from two columns (mobile) to two rows (desktop)
server actions functional
postgres integration for server actions

@robahtou the package updates conflict 📦

@rgreinho should be ok now

🎉 🍰


Generating empty css file

Plugin is generating an empty css file:
This is my configuration:
...
["css-modules-transform", {
  "extensions": [".css", ".scss", ".less"],
  "extractCss": "./dist/stylesheets/theme.css"
}],

I went through the source and my requires do get picked up and get transformed but it seems to fail here:
if (t.isExpressionStatement(path.parent)) {
  //buildClassNameToScope is working
  var p = path.replaceWith(buildClassNameToScopeNameMap(tokens));
  console.log(p)
  return p; // p = undefined :(
} else {
  path.remove();
}

Any idea what could be causing this?

@MatthiasBrandt could you create a simple project you can share to reproduce this error?

@michalkvasnicak I am facing the same issue. This package doesn't seems to be updating the bundle.css file. Anyway to rebuild the file ?

@michalkvasnicak It seems this plugin couldn't parse 'babel-plugin-module-resolver' alias. After I changed module name with relative path from module alias name, it works well.

Yes this package doesn't support aliases because of the order the babel plugins are executed. Maybe there is a way how to somehow resolve this after babel-plugin-module-resolver does its job but I don't have time to investigate this. But I'm happy to accept the PR for this.


OmniLogic Custom Int - stopped working this morning

No changes made on HomeAssistant side, tried to disable/re-enable same issue; Confirmed credential still work on website & mobile app.
2023-05-23 10:36:35.387 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Omnilogic for omnilogic
File "/config/custom_components/omnilogic/__init__.py", line 44, in async_setup_entry
File "/usr/local/lib/python3.10/site-packages/omnilogic/__init__.py", line 166, in connect
File "/usr/local/lib/python3.10/site-packages/omnilogic/__init__.py", line 148, in authenticate
File "/usr/local/lib/python3.10/site-packages/omnilogic/__init__.py", line 143, in _get_new_token
File "/usr/local/lib/python3.10/site-packages/omnilogic/__init__.py", line 129, in _get_token
File "/usr/local/lib/python3.10/site-packages/omnilogic/__init__.py", line 100, in call_api

Working again - either a their issue or mine.


How to connect two or three LT100 or LS100

I made three different ones. LT100, LS100 and NODE PRO all three are visible in iCUE, but if I make another LT or LS, only one is visible, although both are present in the system, this is visible on com ports.
Perhaps somewhere you can fix the ID or PID in the uploaded firmware?
I have 3 monitors and I wanted to make my own ambilight for each.
Thanks for the reply in advance.

Have a look at https://github.com/Legion2/CorsairLightingProtocol#use-of-multiple-devices, you have to set unique IDs for the devices.


There was a problem reading my config.json file

I am a novice with programming and i am trying to connect my nest thermostat to homekit via homebridge. I have checked that it is a valid config.json through JSONLint, which it says it is. However, when i run homebridge through terminal, i get this message:
[1/11/2019, 1:01:28 PM] There was a problem reading your config.json file.
[1/11/2019, 1:01:28 PM] Please try pasting your config.json file here to validate it: http://jsonlint.com
[1/11/2019, 1:01:28 PM]
/usr/local/lib/node_modules/homebridge/lib/server.js:214
throw err;
^
SyntaxError: Unexpected token P in JSON at position 0
at JSON.parse ()
at Server._loadConfig (/usr/local/lib/node_modules/homebridge/lib/server.js:208:19)
at new Server (/usr/local/lib/node_modules/homebridge/lib/server.js:56:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:30:16)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
Can someone please help me overcome this as i am lost as to how to get it to work. Here is the config.json i am using;
{
| "namespace": "tonesto7",
  | "repoOwner": "tonesto7",
  | "repoName": "nest-manager",
  | "repoBranch": "master",
  | "name": "NST Manager",
  | "author": "Anthony S.",
  | "description": "The Best Solution to integrate your Nest Products into the SmartThings Enviroment.",
  | "category": "My Apps",
  | "bannerUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/nst_manager_5_banner.png",
  | "forumUrl": "https://community.smartthings.com/t/release-nst-manager-v5-0/",
  | "docUrl": "http://thingsthataresmart.wiki/index.php?title=NST_Manager",
  | "releaseType": "production",
  | "keywords": [
  | "nest",
  | "thermostat",
  | "nst",
  | "camera",
  | "protect",
  | "smoke",
  | "carbon",
  | "monoxide"
  | ],
  | "notes": "Nothing to show here (yet)",
  | "smartApps": {
  | "parent": {
  | "name": "Nest Manager",
  | "iconUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/nst_manager_5.png",
  | "published": true,
  | "oAuth": true,
  | "version": "5.5.8",
  | "appSettings": {
  | "clientId"<EMAIL_ADDRESS>  | "clientSecret": "__________",
  | "devOpt": "false"
  | },
  | "appUrl": "smartapps/tonesto7/nest-manager.src/nest-manager.groovy"
  | },
  | "children": [{
  | "name": "NST Automations",
  | "iconUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/nst_automations_5.png",
  | "published": true,
  | "oAuth": false,
  | "version": "5.4.9",
  | "appSettings": {},
  | "appUrl": "smartapps/tonesto7/nst-automations.src/nst-automations.groovy",
  | "optional": false
  | }]
  | },
  | "deviceHandlers": [{
  | "name": "Nest Thermostat",
  | "iconUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/thermostat_icon.png",
  | "published": true,
  | "version": "5.4.4",
  | "appUrl": "deviceTypes/tonesto7/nest-thermostat.src/nest-thermostat.groovy",
  | "optional": false
  | },
  | {
  | "name": "Nest Protect",
  | "iconUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/protect_icon.png",
  | "published": true,
  | "version": "5.4.2",
  | "appUrl": "deviceTypes/tonesto7/nest-protect.src/nest-protect.groovy",
  | "optional": false
  | },
  | {
  | "name": "Nest Camera",
  | "iconUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/camera_icon.png",
  | "published": true,
  | "version": "5.4.3",
  | "appUrl": "deviceTypes/tonesto7/nest-camera.src/nest-camera.groovy",
  | "optional": false
  | },
  | {
  | "name": "Nest Presence",
  | "iconUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/presence_icon.png",
  | "published": true,
  | "version": "5.4.2",
  | "appUrl": "deviceTypes/tonesto7/nest-presence.src/nest-presence.groovy",
  | "optional": true
  | },
  | {
  | "name": "Nest Weather",
  | "iconUrl": "https://raw.githubusercontent.com/tonesto7/nest-manager/master/Images/App/weather_icon.png",
  | "published": true,
  | "version": "5.5.0",
  | "appUrl": "deviceTypes/tonesto7/nest-weather.src/nest-weather.groovy",
  | "optional": true
  | }
  | ]
  | }
Like I said, please help!!!
Thanks

You were pointed in a helpful direction but you must look at the readme docs for the plugins to understand how to set them up. If you look at Homebridge-Nest's readme file, it explains to you exactly how you need to have your config file setup. I have included what it should look like below but make sure to read the Homebridge-Nest Readme file as it explains to you how to fill in those values.
{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "031-45-154"
    },
    "accessories": [
        {
        }
    ],

    "platforms": [
       {
   		"platform": "Nest",

   		"token" : "token will be generated upon first run of homebridge without a token",

   		"clientId": "developer Product ID",
   		"clientSecret": "developer Product Secret.",
   		"code": "your Pincode from Nest",

   		"username" : "username",
   		"password" : "password"
   	}
    ]
}

Try deleting everything and starting all over again. That worked for me after trying several times.


Getting started instructions fail

Tried the simple instructions for getting started and the .game(...) method always fails.
>>> from curseforge import CurseClient
>>> from dotenv import dotenv_values
>>> config = dotenv_values()
>>>
>>> curse = CurseClient(config['CURSEFORGE_API_KEY'])
>>>
>>> curse.game(432)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "D:\Work\Gms\CurseForgeAPI\.venv\Lib\site-packages\curseforge\base.py", line 79, in game
    return CurseGame.from_dict(self.fetch(f"game/{game_id}"))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\Work\Gms\CurseForgeAPI\.venv\Lib\site-packages\curseforge\classes\cursegame.py", line 23, in from_dict
    id=data.get("id"),
       ^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get'
>>>
>>> next(curse.games())
CurseGame(id=78135, name='Demeo', slug='demeo', assets=CurseGameAssets(icon_url='iconUrl', tile_url='tileUrl', cover_url='coverUrl'), status=6, api_status=None, date_modified=None)

Tried a number of game IDs, both with and without caching just in case. No luck.
As you can see the .games() call after it works, so the API key is working.

Why the hell doesn't GitHub notify me about this issues, will look into it right away

Ahh, I see  the issue here, the fetch method is requesting the /game path, which does not exist
It should actually fetch /games/{GAME_ID}, so thank you for this issue

PS: I STILL DONT KNOW WHY GITHUB DID NOT NOTIFY ME ABOUT THIS ISSUE, OCT 3rd!! REALLY!!

Run:
pip install --upgrade curseforge


fix: assign binary func to func type var

Only interpreted func could be assigned to func type variables.
Call() can now invoke binary func directly.
Fixes #408

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: mvertes:white_check_mark: ldez:x: traefikerYou have signed the CLA already but the status is still pending? Let us recheck it.


[Fix-6723] Part 1: add more data to API logs + improve completness of tracing logs

This PR is part 1 of the fix for #6723
It lays the groundwork that will be necessary to complete the change in the next PR - the work was split in 2 parts to make reviews easier.
Part 1 contains:

Add more information to API logs for both HTTP and gRPC, including things that are not going to be included in metrics by default anymore:

Response status code
Response size (if possible; for HTTP only)
Latency

When obfuscateURLs is enabled for API logging, in API logs we now include a more descriptive name for the method rather than the path that was matched in the router. The descriptive names map to the names of the methods in gRPC, for example SaveState in place of POST /state/{storeName}/{name}. Since gRPC API logs are always, only "obfuscated" (because the params are in the body and not in the "URL"), this makes HTTP and gRPC API logs more consistent too
Refactors how tracing and API logging (and the API token auth middleware) get the data from the handler/router:

The new approach is a lot more declarative, and less based on heuristics (such as parsing the path from the URL again)
The new approach also reduces the number of maps that are allocated and used in each request, which generally contained duplicate information generated in multiple parts of the code

For both HTTP and gRPC, the way metadata is added to a tracing span has changed and it's now more declarative:

When looking at how tracing spans were composed, the metadata was added in pkg/diagnostics, separately from the endpoints. Only a VERY SMALL number of APIs had proper tracing configured (as a matter of fact, see the number of "TODO"'s in this PR), in large part due to the fact that this was in a separate package. The approach also relied a lot on heuristics.
For HTTP, now the Endpoint struct contains a property to add a function that adds properties to a span for tracing purposes. This lives right next to the handler.
For gRPC, messages defined in the protos whose name ends in "Request" now must define an AppendSpanAttribute method (this is enforced by a unit test)

Update API Allowlisting/Denylisting for HTTP to:

Make sure that the same constants can be used for both HTTP and gRPC, especially versions. Right now, versions are in the format "v1.0-alpha1" for HTTP, and "v1alpha1" for gRPC. This PR changes the HTTP versions to be in the format "v1alpha1" too ("v1.0-alpha1" is preserved for bacwkards-compatibility)
Improved perf of the HTTP Allowlist/Denylist, especially when using the "new" format (e.g. versions with "v1alpha1"): checking the allowlist is now a simple map lookup rather than an iteration over the entire allowlist.

/ok-to-test

/test-sdk-all

/ok-to-test

Including high cardinality disabled by default is important to get in 1.12. However, this PR contains many changes that are out of scope of the issue that this PR is fixing (ie. the "improve completeness of tracing logs" part and other changes).
Here are the relevant parts for 1.12 (pasted from the issue):
1. By default, do not report metrics per each endpoint/path in the HTTP server. Aggregation will stop at the app ID for service invocation.
2. Add an option to the Configuration CRD metrics.highCardinality, disabled by default, to retain the current behavior.
3. Change the API logging middleware to include additional information on each request, including latency and returned status code. These are things that were before included in the metrics. Although API logging aren't a 1:1 replacement for metrics, users can leverage them in tools like Grafana to gather similar insights.

Please revert the changes that do not deal with disabling high cardinality by default and adding latency and status code for API logs. The additional improvements and changes introduced here can easily go into 1.13 with no issues.

@yaron2 Although it's true that this PR includes other things, they are all related.
The things mentioned above are a natural consequence of having expanded the metadata included in the "Endpoints" struct. Those changes are very small. I'd rather not have a separate PR given how if it has to wait for 1-2 months till 1.13, it'd drown in merge conflicts...

@yaron2 Although it's true that this PR includes other things, they are all related.
The things mentioned above are a natural consequence of having expanded the metadata included in the "Endpoints" struct. They help keeping the code well-organized so the next step of the PR is simpler.
Those changes are very small. I'd rather not have a separate PR given how if it has to wait for 1-2 months till 1.13, it'd drown in merge conflicts...

The changes related to tracing can be made on a PR that can be opened at any time during the 1.13 milestone, doesn't even have to now, which I agree will drown in merge conflicts.

The point is that the changes are done and they helped making this PR and tidying things up. Opening it later doesn't change the fact that there'll be significant merge conflicts.
I do want to stress the usefulness of having things tidier. We were checking the route in multiple places and each one had different heuristics. This PR's main contribution was aggregating everything in a struct such as this:
https://github.com/dapr/dapr/pull/6729/files#diff-037644126d1c1589e20eaf7f82ec9c28a40952d9e29344149567ee8af589b8f3R59-R80
This required changing some middlewares to make sure all route metadata is kept in the context, rather than being split in the context and in the "responsewriter" object (and in a bunch of other places). This is what then naturally enabled the other changes to the tracing and API allowlist middlewares, which are really small.
The next step will be to build upon this expanded struct to improve the diagnostics collection. The data sent to the diag methods will be fetched from the same centralized sources.

Alright, keep the PR as is. We'll triage #6723 to 1.13 and can revisit all the changes in this PR as a whole in the next milestone.

Sounds good. We’ll backport this in our distribution for customers who are blocked by the issue and can’t use the OSS version

@ItalyPaleAle the changes in this PR are great, but this release already saw a large amount of different refactors to major parts of the codebase and these risk the release. Our prior experience shows these types of changes are many times the number one cause of patch releases. Changes that fix the original issue alone will be actually prioritized above other PRs (at least as far as I'm concerned).

Thanks, Alessandro and Yaron. I do agree to focus on the original impact on our users prior to refactoring the code. We struggled with that in the past and this is an opportunity to do different. The refactorings should not be bundled with behavior or improvements because it might put the reviewer on the spot to accept the PR because a welcomed change is bundled with changes that will require further discussions.
I think the OSS users also deserve the improvements regarding the original impact described in the issue.


Handling arrays with non-uniform chunking

Currently Zarr handles Arrays with uniform chunking. Meaning all chunks have the same size (excepting end chunks, which can be shorter). It would be nice if Zarr could also handle non-uniform chunking. Meaning that chunks would still live on a grid, but may vary in size based on their location (IOW not only end chunks would have this feature).
Motivating use cases include saving a Dask Array with non-uniform chunking. Admittedly these could be rechunked if the chunk size is known. Though this comes with some overhead compared to not rechunking. When the chunk size is unknown, this cannot be easily accomplished.

cc @martindurant (who may have interest in this)

Also shortening edge chunks described in issue ( https://github.com/zarr-developers/zarr-python/issues/233 ) could be a special case of this


Correcting Example in README.

"Example Test" is missing semicolon after TEST_GROUP. Adding semicolon to example.

Coverage remained the same at 99.846% when pulling<PHONE_NUMBER>23794bddb01c9dde35014670621942 on sbashford:sbashford-readme-10-4-19 into ddc8b56eac203d8daf706ba69946a105225c1283 on cpputest:master.


Split CI in different steps and jobs

[X] Tag issue being addressed
[ ] Add tests
[ ] Update docstrings/documentation, if applicable
[ ] Update changelog

Addresses #561
Proposed split is:

Matrix job (runs on several configs):

Unit tests + Examples (two separate steps for easy diagnosis)

Single config job (Ubuntu, Py37, with rdkit and openeye):

Lint checks (new! run flake8, isort --check and black --check, just to see how it feels)
Documentation (test readme links and build sphinx locally)

Questions

[ ] Do we want Black checks? If so, line length? Maybe the default 88?
[ ] Do we want Flake8 checks?  We'd need to agree on a good config.
[ ] Do we want to turn Sphinx warnings (there are a lot!) into errors?

Do we want Black checks? If so, line length? Maybe the default 88?
Do we want Flake8 checks?  We'd need to agree on a good config.

I would personally like at least flake8 to be implemented eventually and I agree that we need agree on the details before linting the existing code or enforcing it as a check. For example, I like prefer black -S but I may be alone in that. For now, can linters just operate on the diff?
Can we reach a consensus during the developer week?

For example, I like prefer black -S but I may be alone in that. For now, can linters just operate on the diff?

My +1 is to just stick directly to the black defaults and not make any config changes. "Black is opinionated so you don’t have to be."

Okay, I've scaled this back a little just to get it over the finish line (linting will still happen, just splititng this off into smaller PRs)

Uses miniconda action
Install RDKit vs OpenEye array using separate files, not lines in script
Includes openeye-toolkits=2019 pin
Split off tests into a few smaller steps

It's tempting to further split off the unit tests (one for each of the main modules) but I can load up the unit test run without my browser freezing up, so consider that a win.

I realized that this is a lot of really good stuff, but I have just been flying from fire to fire the last few weeks and haven't reviewed this or had bandwidth to discuss the questions above. These changes will make everyone's lives a lot easier, so I don't want to block this any further.
I'm removing myself as reviewer. @mattwthompson can approve+merge this at his discretion! Thanks everyone for the hard work here.


JCL-391: switch env var to new dev

Also, switch log level from info to warn in base module to be consistent in all modules

Also switched to another prod webId.


Events and Some Idea

is it good idea to add events for each created form(JavaScript and Yii2 events)(such as, events can use for payment for forms)? and something else is it better to create model and model search for each created form ? (in the create and update table actions like gii but I think in this way permissions make problem). in this way we can add upload and add rules in the rule function or only just use anonymous class for model and model search class when needed in actions(in this way in the grid view can add search model).

Thank for your ideas. In last month a added many improvements. Additions events and model search for each form, it is to do, but need time.

thanks for your great work and ideas, i think it can be the best extension of Yii2 if it's completed and can make programming with Yii2 easier, faster and add features that can a framework do the cms jobs easier.


Merge master to 2.1.x

Not sure why git couldn't figure out how to ff this, but these were all bug fixes


Multiple variables declaration

When declared and initialize multiple vars. Jshint shows warning like this:

"You might be leaking variable here" it says.

Better complain with jshint itself, we just run the thing and it reports this to us. Go here, seems like there are already issues raised about this: https://github.com/jshint/jshint


docker error

This command
nvidia-docker run -it foresight/sim: bash

spits out an error:
nvidia-docker | 2019/03/12 13:31:02 Error: invalid reference format

I think the correct command is:
nvidia-docker run -it foresight/sim bash

Good catch! I forgot the tag. Below command should work too: (fixed in spec now)
nvidia-docker run -it foresight/sim:latest bash


Not working with latest ui-router

In the current version of ui router a lot has changed (1.x) the transition callbacks are completly different, thus breaking the module.
the $stateChangeStart and more no longer exist.
I could make a pr voor a new version, or fork this and release on Npm?

please do

It's not working here either, also tried ngMeta module but none of them seems to be working with ui-router 1.0. Hope someone forks one of those projects and provide a solution.

Did someone find a solution for meta tags with angular-ui-router 1.x ?

#27 solve this problem.

merged


CI: move env. var & rerun

What does this PR do?
A workaround for #15935 and #15936.
try to bypass app tests faleness
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @carmocca @akihironitta @borda

Is rerunning still necessary considering the linked issues were fixed?

Is rerunning still necessary considering the linked issues were fixed?

I still see it time-to-time on various PRs, but curious why suddenly this has so many failing cases...

FYI, dropping rerun for apps as it has some storage failures across all configurations


[Fix #7958] Properly tag unsafe autocorrections with rubocop:todo when using --autocorrect --disable-uncorrectable

Previously, if a cop was correctable but not corrected due to being unsafe, --autocorrect --disable-uncorrectable would report the offense but not tag it with rubocop:todo. This is now updated, so that unsafe offenses are tagged as well.
In order to do so, we have to treat all cops as "autocorrect_cops" in Team#investigate, since adding the directive is also a correction; otherwise, the offense report will mark the offense as [Todo] but not actually apply the correction.
Fixes #7958.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

I discovered some bugs with --disable-uncorrected, particularly around if multiple offenses need to be todoed on the same line. I am working on a better approach to this that should fix these. I'm going to close this in the meantime.


I have done some experiments on Chinese using bert-base config, the results are not promising

Hi, I have done pretraining on Chinese-dataset(50G) and run downstream finetuning on ChineseClue benchmark, the default hyperparameters ars the same to bert-base:
learning_rate: 3e-5,
epoch: 3 or 5
the finetuning results on benchmark are worse than official Chinese bert-base released by Goolge

Hi, I want to use TTA to do some work about  spelling Error Correction on Chinese,  and did you do some experiments?

Hi, I want to use TTA to do some work about  spelling Error Correction on Chinese,  and did you do some experiments?

no，I could provide you my preteained Chinese tradition base for spell correction or do it together
---Original---
From<EMAIL_ADDRESS>Date: Thu, Jan 28, 2021 20:04 PM
To<EMAIL_ADDRESS>Cc: "yyht"<htxu91<EMAIL_ADDRESS>Subject: Re: [joongbo/tta] I have done some experiments on Chinese using bert-base config, the results are not promising (#6)
Hi, I want to use TTA to do some work about  spelling Error Correction on Chinese,  and did you do some experiments?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

no，I could provide you my preteained Chinese tradition base for spell correction or do it together
---Original---
From<EMAIL_ADDRESS>Date: Thu, Jan 28, 2021 20:04 PM
To<EMAIL_ADDRESS>Cc: "yyht"<htxu91<EMAIL_ADDRESS>Subject: Re: [joongbo/tta] I have done some experiments on Chinese using bert-base config, the results are not promising (#6)
Hi, I want to use TTA to do some work about  spelling Error Correction on Chinese,  and did you do some experiments?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Prevent empty strings for required fields

Several string fields are required, e.g. "id" in item or "description" in Collections.
Although those fields are required, they can be provided as empty strings.
Should we enforce a minimum length of 1 in JSON Schemas for required strings?

I'm +1 on this.

[x] Core
[ ] mgrs
[ ] datacube
[ ] storage
[ ] pointcloud
[ ] label
[ ] version
[ ] sar


MOCs are lost when performing join/crossmatch

Currently crossmatching/joining loses MOC info, since the aligned MOC isn't returned by the hipscat alignment functions. So after crossmatching or joining, the benefits of the MOCs are lost.
I think the best way to fix this is to include a moc attribute in the PixelAlignment class, and use that in the crossmatch/join catalog methods.

This was closed by #438.


Grouping chooser commit on change

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

@leogretz2 -- I wend ahead and merged this with Anselm's doc comment changes.   Please check out those changes -- definitely worth understanding his suggestions and the API docs style we are looking for.


[Package Request]: Playdate Mirror

How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://play.date/mirror/
Publisher: Panic!
Package Name: Playdate Mirror
Description: Mirror is an app that streams gameplay audio and video in real-time from your Playdate to a macOS, Windows, or Linux computer. This makes it super simple to record or stream Playdate games, gives you a giant-sized screen for your Playdate, and, by using standard game controllers or your mouse or PC, allows you to control your Playdate accessibly using alternative inputs.
Package Version: 1.1.0
Installer URL: https://download.panic.com/mirror/Windows/Mirror-latest.exe

Any updates on this?


Update Kubernetes version check to include v1.25

Once we release the K8s 1.25 support, we need to remember to update this guided install check.

Hi @htroisi, Hang in the Virtuoso team duplicated your PR with this one. I think you can close this PR for now.


Replace MerklePathSet with PartialMerkleTree

This PR replaces usage of MerklePathSet with PartialMerkleTree. This PR is needed for the correct work of the following PR in the Miden VM repo.

We should also update the main README file to remove references to MerklePathSet from there.


feat(dashboard): implement sorting feature in trending table

#3667  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joaquim-verges and the rest of your teammates on  Graphite


EMPTY TODO COMMENT

Issue created from code comment with imdone.io

TODO @TypeScript id:59
src/vs/editor/common/core/stringBuilder.ts:9
@imdone - Efficiently manage your project's technical debt. imdone.io

Issue closed by removing a comment.

TODO @TypeScript id:59 gh:61
src/vs/editor/common/core/stringBuilder.ts:9
@imdone - Efficiently manage your project's technical debt. imdone.io


Error with Node

Im trying to use the plugin with the Node and Polyfills.
I getting this error:
node_modules/@bogeychan/elysia-logger/src/types.ts(3,31): error TS2307: Cannot find module 'bun' or its corresponding type declarations.

Hi 👋
this should be fixed with 0.0.16. Let me know if the issue persists.


://prod.msocdn.com/en-USAudio

://prod.msocdn.com/en-USAudio

Can you please add more details on this?


[AMBARI-23111] Additional fixes for service summary page to support NameNode Federation

What changes were proposed in this pull request?

Add mapping of namespace id property from API
Display NameNodes as active and standby ones
Remove tabs to select certain namespace
Add namespace-scoped HDFS checkpoint check and warning message before stopping and restarting NameNodes
Too long namespace id should be cropped with adding ellipsis and beung displayed fully in tooltip

How was this patch tested?
Tested on real clusters with and without NameNode federation
UI unit tests:
21509 passing (24s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/877/
Test PASSed.


Keep footer fixed at the bottom of the screen when keyboard opens

Is there any way this can be accomplished? I tried setting position: absolute; but it seems like the tabs keep wanting to move upwards with keyboard

You could set android:windowSoftInputMode="adjustPan" in your main activity in android/app/src/AndroidManifest.xml. However, this removes the android soft keyboard's behaviour of pushing the view up to make space for the keyboard in the entire app.
Does anyone have a way to prevent only the tab bar from being pushed up?

@Jarrio hi, did you find out any solution? thanks!

android/app/src/AndroidManifest.xml

<activity
.....
android:windowSoftInputMode="stateAlwaysHidden|adjustPan"
.....

worked for me.

+1

You can make fixed height and minHeight for boxes and it will prevent minimizing height of boxes.
Example below:
<View style={{position: 'absolute',bottom: 0, top: 0, width: '100%', height: screen.height, minHeight: screen.height}}>
Content goes here

Any solution for crna?

android/app/src/AndroidManifest.xml

<activity
.....
android:windowSoftInputMode="stateAlwaysHidden|adjustPan"
.....

worked for me.

Thank you very much

You can make fixed height and minHeight for boxes and it will prevent minimizing height of boxes.
Example below:
<View style={{position: 'absolute',bottom: 0, top: 0, width: '100%', height: screen.height, minHeight: screen.height}}>
Content goes here
After struggling for 3 days, I came across this and it worked! Thanks!

Hey, I just released a new alpha 2.0.0-alpha.0 of the library. It's rewritten using react-native-gesture-handler and react-native-reanimated addresses a many platform specific bugs and performance problems. The documentation is updated as well.
Please try the new version and see if it addresses your issue. If not, please open a new issue following the issue template.

This issue is still in android in IOS it's work perfect

stateAlwaysHidden|adjustPan

thanks it's working for me too

stateAlwaysHidden|adjustPan

thanks it's working for me too

Hi, I have a similira Problem with adjustPan property.
if you have TextInput in all tabs at bottom of the page, soft keyboard only pushes up screen to see input in first tab not other tabs. more info at this thread

@cleandersonlobo Thanks, man. It worked for me.

Hi I also have same problem. Although I try stateAlwaysHidden|adjustPan it's not work for me


Handle multiple params of the same name properly

In case we try to call consumer.get('URL?param=1&param=2'), the library
generates incorrect URL. That is because it internally parses the URL so
that the params are actually called param[0] and param[1].
This patch fixed the param names so that the resulting URL is actually
including param=1 and param=2.
This is what was proposed in #71 and it fixes #71 .

Works for me. Tks!


[Stepper] Add iconContainerStyle to StepButton and StepLabel

Currently, it is possible to customize the icon of a StepButton or StepLabel with the icon prop.  However, the <span> container for this icon has a fixed width of 24px.
This change adds the ability to customize the style of this icon container element.

[ ] PR has tests / docs demo, and is linted.
[ ] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[ ] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@lawrence-yu Thanks, that looks good. Still, it would be great to add a simple unit test for this behavior.

I added unit tests in StepButton and StepLabel.

@lawrence-yu Thanks!


Expand Examples of Array Operators

https://www.cockroachlabs.com/docs/stable/array.html
There were no examples of using a specific element in an array, but was able to figure it out with Postgres documentation.
select * from crdb_internal.jobs where job_type = 'CHANGEFEED' and descriptor_ids @> ARRAY[288];

maybe consider an example like so based on the existing docs:
root@:26257/defaultdb> INSERT INTO c VALUES (ARRAY[10,20,30]);
INSERT 1

Time: 11.439951ms

root@:26257/defaultdb> INSERT INTO c VALUES (ARRAY[42,99]);
INSERT 1

Time: 2.646631ms

root@:26257/defaultdb> SELECT * from c where d @> ARRAY[42];
     d
-----------
  {42,99}
(1 row)

Time: 1.274903ms

Thanks, @glennfawcett! @ericharmeling, @awoods187, on to you for further triage and prioritization.

I think this is a great example of a type of enhancement we could make to our docs for some of the bigger features (e.g., JSON, ARRAY). We should provide at least one example query per operator. I'd rate this as more important than general reference information but less important than documenting new features or fully following a jobs-to-be-done approach.

@Amruta-Ranade, can I work on this one?

Addressed in https://github.com/cockroachdb/docs/pull/8697


$10k project idea #3 - WCAG 2.1 & WET

WCAG 2.1 is being adopted in Europe & Australia. What are the implications for the Government of Canada and the existing Web Experience Toolkit?
Evaluate what's new in the guidelines http://davidmacd.com/blog/wcag-2.1-quick-guide.html and where are the areas for improvement that could be adopted.
Contribute those back as issues https://github.com/wet-boew/wet-boew/issues

From Medium post: https://medium.com/@mgifford/i-would-definitely-update-it-with-or-without-covid-19-e326e1882603
Update on issue from May 2020
#3 —WET & WCAG 2.1 AA, this all still needs to be done. There has been a little progress, but WCAG 2.2 should be finalized this fall.

I think this is the meta issue for WET-BOEW:
https://github.com/wet-boew/wet-boew/issues/8602
The first 2.2 draft is up here https://www.w3.org/TR/WCAG22/


Gh pages ev charging env

Markdown for EVCharging site!

Copied modifications of evchargingenv.md into the gh_pages branch. See commit 1fbdf2e.


New exception type thrown when looking up data with an unknown identifier

Something like DataNotFoundException. Currently we throw IllegalArgumentException which means it's impossible to distinguish between looking up data using an unknown ID and passing in genuinely invalid data.
This came up in a conversation about mapping exception types to HTTP errors in a REST framework. It is pretty natural to map IllegalArgumentException to 400 (bad request) and DataNotFoundException to 404 (not found).

Fixed by https://github.com/OpenGamma/Strata/commit/b241971b973c3805ad04147dd5c8765c3e9c703b


fix: improve performance of getReport()

This will improve performance for newer versions of Node.js because this report doesn't need to access the network.

See https://github.com/nodejs/node/pull/51645

Is it just me or is the API we have to use to set excludeNetwork somewhat awkward?

Agreed. Its not just excludeNetwork thats awkward, but every Report configuration: https://nodejs.org/api/report.html#configuration

Thanks for the updates. Let's wait until there's a proper, non-nightly (backported?) release of Node.js with the new flag before merging/releasing.

I'm going to merge this now as the change in #22 means the use of getReport() should now mostly be confined to musl-based Linux.
There are no nightly Node.js builds for musl and the upstream excludeNetwork patch isn't planned for backport, so when Node.js 22 is released we can add it to the test matrix.

Thanks again for the PR, this change was included in v2.0.3.


Unable to install via JSPM 0.17 (beta)

When installing the bridge jspm install aurelia-materialize-bridge --dev I get the error
err  Repo jspm:materialize-css not found. Perhaps try jspm install npm:materialize-css

But I can install materialize-css directly by using jspm install npm:materialize-css --dev
I think the problem is the peerDependency setting in package.json
"peerDependencies": {
    "materialize-css": "^0.98.0"
}

which should be
"peerDependencies": {
    "npm:materialize-css": "^0.98.0"
}

I think you're right, thanks. 👍
The reason might be: until 0.98.0 materialize had an entry in the jspm registry which wasn't refreshed at 0.98.0..

@mreiche try this:
jspm install github:aurelia-ui-toolkits/aurelia-materialize-bridge

@SerkanSipahi Can you explain that to me, why the jspm registry and npm doesn't work anymore?

Still no luck:
Mikes-MacBook-Pro:myty-5 mike$ jspm install github:aurelia-ui-toolkits/aurelia-materialize-bridge --dev

warn Running jspm globally, it is advisable to locally install jspm via npm install jspm --save-dev.
     Updating registry cache...

err  Repo jspm:materialize-css not found. Perhaps try jspm install npm:materialize-css.

warn Installation changes not saved.

@mreiche npm install aurelia-ui-toolkits/aurelia-materialize-bridge has also problems:
see:
`
├──<EMAIL_ADDRESS>(git://github.com/aurelia-ui-toolkits/aurelia-materialize-bridge.git#3ac53aa09301cd8d9adc525e4c05f33b63010fd5)
└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
`

Still no luck:

sometimes it sucks. Try it again.  Try it again. In my env 'MacBookPro' it works.

 Removing JSPM, clearing cache? I'm despared.

Disclaimer: This is a wild guess. 😏
Try to install jspm locally. Your log says it's running from the global jspm.
npm install --save-dev jspm

@Thanood yes, right. I do the same. Then try node_modules/.bin/jspm install whatever-you-want

@SerkanSipahi The NPM peerDependency is actually only a warning to remind users to install "some kind of" Materialize. It's not a hard dependency (which would be pulled automatically) because there are some forks of Materialize which people may want to use.

So this may be the key difference.. 😃

@mreiche i know but maybe jspm cant handle it?!?

I installed jspm@beta locally.
And installed my fork WITHOUT peerDependencies: https://github.com/mreiche/aurelia-materialize-bridge/blob/master/package.json
Mikes-MacBook-Pro:myty-5 mike$ jspm -v
0.17.0-beta.42
Running against local jspm install.
Mikes-MacBook-Pro:myty-5 mike$ jspm install github:mreiche/aurelia-materialize-bridge --dev
     Updating registry cache...

err  Repo jspm:materialize-css not found. Perhaps try jspm install npm:materialize-css.

warn Installation changes not saved.

Wow, that sucks.. 😕

Where does JSPM pull that from? If I'm not completely blind, it's mentioned nowhere..

sure you are using locally? jspm -v is globally and node_modules/.bin/jspm -v is locally

@SerkanSipahi It's running locally. THere is no warning about running it globally like in the first log. Also, JSPM runs the local installation if it finds node_modules/.bin/jspm

I purged node_modules and jspm_packages, uninstalled global jspm.
jspm-clean-install.txt
Can someone test against my package.json, please?
package.txt

no erros:
`
Looking up npm:jspm-nodelibs-assert
Looking up npm:aurelia-animator-css
Looking up npm:aurelia-bootstrapper
Looking up npm:aurelia-fetch-client
Looking up npm:aurelia-framework
Looking up npm:aurelia-history-browser
Looking up npm:aurelia-i18n
Looking up npm:aurelia-loader-default
Looking up npm:aurelia-logging-console
Looking up npm:aurelia-pal-browser
Looking up npm:aurelia-plugins-cookies
Looking up npm:aurelia-polyfills
Looking up npm:aurelia-templating-binding
Looking up npm:aurelia-templating-resources
Looking up npm:aurelia-templating-router
Looking up npm:aurelia-validation
Looking up npm:jspm-nodelibs-buffer
Looking up npm:jspm-nodelibs-child_process
Looking up npm:jspm-nodelibs-constants
Looking up npm:jspm-nodelibs-crypto
Looking up npm:jspm-nodelibs-events
Looking up npm:jspm-nodelibs-fs
Looking up npm:i18next
Looking up npm:i18next-xhr-backend
Looking up npm:intl
Looking up npm:jspm-nodelibs-module
Looking up npm:moment
Looking up npm:jspm-nodelibs-os
Looking up npm:jspm-nodelibs-path
Looking up npm:systemjs-plugin-babel
Looking up npm:jspm-nodelibs-process
Looking up npm:jspm-nodelibs-stream
Looking up npm:jspm-nodelibs-string_decoder
Looking up npm:jspm-nodelibs-util
Looking up npm:jspm-nodelibs-vm
Looking up npm:jspm-nodelibs-zlib
Looking up npm:jquery
Looking up npm:froala-editor
Looking up npm:aurelia-binding
Looking up npm:aurelia-dependency-injection
Looking up npm:aurelia-event-aggregator
Looking up npm:aurelia-history
Looking up npm:aurelia-loader
Looking up npm:aurelia-logging
Looking up npm:aurelia-metadata
Looking up npm:aurelia-pal
Looking up npm:aurelia-path
Looking up npm:aurelia-route-recognizer
Looking up npm:aurelia-router
Looking up npm:aurelia-task-queue
Looking up npm:aurelia-templating
Looking up npm:babel-core
Updating registry cache...
Looking up github:github/fetch
warn Using local override for<EMAIL_ADDRESS>warn Using local override for<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:browserify-zlib
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:font-awesome
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:buffer
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:crypto-browserify
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:os-browserify
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:string_decoder
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:stream-browserify
warn Using local override for<EMAIL_ADDRESS>warn Using local override for<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:readable-stream
Looking up npm:pako
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>ok   Installed<EMAIL_ADDRESS>(1.0.1)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(1.0.3)
ok   Installed<EMAIL_ADDRESS>(1.0.3)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(1.1.1)
ok   Installed<EMAIL_ADDRESS>(1.3.0)
ok   Installed<EMAIL_ADDRESS>(1.3.0)
ok   Installed<EMAIL_ADDRESS>(1.3.0)
ok   Installed<EMAIL_ADDRESS>(1.3.1)
ok   Installed<EMAIL_ADDRESS>(1.3.1)
ok   Installed<EMAIL_ADDRESS>(1.2.0)
ok   Installed<EMAIL_ADDRESS>(1.2.0)
ok   Installed<EMAIL_ADDRESS>(1.2.0)
ok   Installed<EMAIL_ADDRESS>(1.1.0)
ok   Installed<EMAIL_ADDRESS>(1.3.1)
ok   Installed<EMAIL_ADDRESS>(1.3.1)
ok   Installed<EMAIL_ADDRESS>(1.3.0)
ok   Installed<EMAIL_ADDRESS>(1.2.1)
ok   Installed<EMAIL_ADDRESS>(1.2.1)
ok   Installed<EMAIL_ADDRESS>(1.2.1)
ok   Installed<EMAIL_ADDRESS>(1.2.1)
ok   Installed<EMAIL_ADDRESS>(1.4.2)
ok   Installed<EMAIL_ADDRESS>(1.4.2)
ok   Installed<EMAIL_ADDRESS>(1.4.2)
Looking up npm:base64-js
Looking up npm:ieee754
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:browserify-cipher
Looking up npm:browserify-sign
Looking up npm:create-ecdh
Looking up npm:create-hash
Looking up npm:create-hmac
Looking up npm:diffie-hellman
Looking up npm:pbkdf2
Looking up npm:public-encrypt
Looking up npm:randombytes
Looking up npm:inherits
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>warn Main entry point not found for<EMAIL_ADDRESS>Adjust this property in the package.json or with an override, setting "main": false if this is the intention.
 Downloading<EMAIL_ADDRESS>
warn Using local override for<EMAIL_ADDRESS>Looking up github:systemjs/plugin-css
Downloading<EMAIL_ADDRESS>Looking up npm:core-util-is
Looking up npm:isarray
Looking up npm:process-nextick-args
Looking up npm:safe-buffer
Looking up npm:util-deprecate
Looking up npm:util
Looking up github:systemjs/plugin-json
Downloading<EMAIL_ADDRESS>Looking up npm:bn.js
Looking up npm:elliptic
Downloading<EMAIL_ADDRESS>Looking up npm:browserify-aes
Looking up npm:browserify-des
Looking up npm:evp_bytestokey
Downloading<EMAIL_ADDRESS>Looking up npm:browserify-rsa
Looking up npm:parse-asn1
Downloading<EMAIL_ADDRESS>Looking up npm:cipher-base
Looking up npm:ripemd160
Looking up npm:sha.js
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:miller-rabin
Downloading<EMAIL_ADDRESS>warn Main entry point not found for<EMAIL_ADDRESS>Adjust this property in the package.json or with an override, setting "main": false if this is the intention.
warn Main entry point not found for<EMAIL_ADDRESS>Adjust this property in the package.json or with an override, setting "main": false if this is the intention.
warn Using local override for<EMAIL_ADDRESS>warn Main entry point not found for<EMAIL_ADDRESS>Adjust this property in the package.json or with an override, setting "main": false if this is the intention.
warn Main entry point not found for<EMAIL_ADDRESS>Adjust this property in the package.json or with an override, setting "main": false if this is the intention.
warn Main entry point not found for<EMAIL_ADDRESS>Adjust this property in the package.json or with an override, setting "main": false if this is the intention.
 Downloading<EMAIL_ADDRESS> Downloading<EMAIL_ADDRESS>
warn Using local override for<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>ok   Installed<EMAIL_ADDRESS>(5.0.6)
warn Using local override for<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>warn Main entry point not found for<EMAIL_ADDRESS>Adjust this property in the package.json or with an override, setting "main": false if this is the intention.
 Downloading<EMAIL_ADDRESS>
ok   Installed<EMAIL_ADDRESS>(2.0.1)
ok   Installed<EMAIL_ADDRESS>(2.0.1)
Looking up github:jspm/nodelibs-util
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:des.js
Downloading<EMAIL_ADDRESS>Looking up npm:brorand
Looking up npm:hash.js
Looking up npm:hmac-drbg
Looking up npm:minimalistic-assert
Looking up npm:minimalistic-crypto-utils
Downloading<EMAIL_ADDRESS>Looking up npm:buffer-xor
ok   Installed module as<EMAIL_ADDRESS>(0.2.1)
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Looking up npm:asn1.js
Downloading<EMAIL_ADDRESS>Looking up npm:hash-base
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>ok   Installed<EMAIL_ADDRESS>(1.1.8)
ok   Installed<EMAIL_ADDRESS>(1.2.0)
Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>Downloading<EMAIL_ADDRESS>ok   Installed assert as<EMAIL_ADDRESS>(0.2.1)
ok   Installed child_process as<EMAIL_ADDRESS>(0.2.1)
ok   Installed events as<EMAIL_ADDRESS>(0.2.2)
ok   Installed constants as<EMAIL_ADDRESS>(0.2.1)
ok   Installed fs as<EMAIL_ADDRESS>(0.2.1)
ok   Installed path as<EMAIL_ADDRESS>(0.2.3)
ok   Installed vm as<EMAIL_ADDRESS>(0.2.1)
ok   Installed process as<EMAIL_ADDRESS>(0.2.1)
ok   Installed babel as<EMAIL_ADDRESS>(5.8.38)
ok   Installed<EMAIL_ADDRESS>(0.10.3)
ok   Installed util as<EMAIL_ADDRESS>(0.2.2)
ok   Installed<EMAIL_ADDRESS>(0.1.2)
ok   Installed buffer as<EMAIL_ADDRESS>(0.2.3)
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(0.10.31)
ok   Installed<EMAIL_ADDRESS>(2.0.1)
ok   Installed<EMAIL_ADDRESS>(0.3.0)
Looking up github:jspm/nodelibs-os
Looking up github:jspm/nodelibs-buffer
Looking up github:jspm/nodelibs-process
ok   Installed<EMAIL_ADDRESS>(1.1.6)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(4.0.0)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
Looking up github:jspm/nodelibs-crypto
ok   Installed<EMAIL_ADDRESS>(2.0.1)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(1.0.7)
ok   Installed<EMAIL_ADDRESS>(1.0.2)
ok   Installed<EMAIL_ADDRESS>(1.0.2)
ok   Installed<EMAIL_ADDRESS>(4.0.1)
ok   Installed<EMAIL_ADDRESS>(2.0.1)
ok   Installed<EMAIL_ADDRESS>(1.0.3)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(5.1.0)
ok   Installed<EMAIL_ADDRESS>(5.1.0)
ok   Installed<EMAIL_ADDRESS>(2.0.3)
ok   Installed<EMAIL_ADDRESS>(2.0.3)
ok   Installed<EMAIL_ADDRESS>(2.0.5)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(1.1.3)
ok   Installed<EMAIL_ADDRESS>(2.0.2)
ok   Installed<EMAIL_ADDRESS>(1.0.2)
ok   Installed<EMAIL_ADDRESS>(4.11.7)
Looking up github:jspm/nodelibs-constants
Looking up github:jspm/nodelibs-string_decoder
ok   Installed<EMAIL_ADDRESS>(5.0.1)
ok   Installed<EMAIL_ADDRESS>(4.0.0)
ok   Installed<EMAIL_ADDRESS>(5.0.2)
Looking up github:jspm/nodelibs-stream
ok   Installed aurelia-plugins-cookies as<EMAIL_ADDRESS>(2.2.0)
ok   Installed<EMAIL_ADDRESS>(4.0.4)
ok   Installed<EMAIL_ADDRESS>(1.1.0)
ok   Installed<EMAIL_ADDRESS>(3.0.12)
ok   Installed<EMAIL_ADDRESS>(1.0.1)
Looking up npm:process
ok   Installed<EMAIL_ADDRESS>(1.0.1)
ok   Installed i18next-xhr-backend as<EMAIL_ADDRESS>(1.4.2)
ok   Installed<EMAIL_ADDRESS>(1.0.3)
ok   Installed<EMAIL_ADDRESS>(0.1.2)
ok   Installed<EMAIL_ADDRESS>(0.1.1)
ok   Installed string_decoder as<EMAIL_ADDRESS>(0.2.1)
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(0.1.2)
ok   Installed os as<EMAIL_ADDRESS>(0.2.2)
ok   Installed<EMAIL_ADDRESS>(0.1.4)
ok   Installed<EMAIL_ADDRESS>(0.11.10)
Looking up npm:constants-browserify
ok   Installed<EMAIL_ADDRESS>(3.11.0)
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(2.4.8)
Looking up github:jspm/nodelibs-fs
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(1.1.1)
ok   Installed<EMAIL_ADDRESS>(6.4.0)
ok   Installed<EMAIL_ADDRESS>(1.0.6)
ok   Installed<EMAIL_ADDRESS>(0.10.31)
ok   Installed fetch as<EMAIL_ADDRESS>(2.0.3)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
Looking up github:jspm/nodelibs-assert
Looking up github:jspm/nodelibs-events
Looking up github:jspm/nodelibs-vm
Downloading<EMAIL_ADDRESS>ok   Installed<EMAIL_ADDRESS>(2.3.1)
ok   Installed<EMAIL_ADDRESS>(4.9.1)
ok   Installed<EMAIL_ADDRESS>(0.0.1)
ok   Installed<EMAIL_ADDRESS>(1.1.14)
ok   Installed<EMAIL_ADDRESS>(4.0.0)
ok   Installed<EMAIL_ADDRESS>(0.2.9)
ok   Installed<EMAIL_ADDRESS>(0.1.2)
ok   Installed<EMAIL_ADDRESS>(5.1.0)
ok   Installed<EMAIL_ADDRESS>(0.0.1)
ok   Installed<EMAIL_ADDRESS>(1.2.1)
ok   Installed aurelia-pal-browser as<EMAIL_ADDRESS>(1.2.1)
ok   Installed<EMAIL_ADDRESS>(3.5.2)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(1.3.0)
ok   Installed npm:font-awesome (4.7.0)
Looking up npm:events
Looking up npm:assert
Looking up npm:vm-browserify
ok   Installed<EMAIL_ADDRESS>(1.0.2)
ok   Installed<EMAIL_ADDRESS>(1.2.1)
ok   Installed aurelia-polyfills as<EMAIL_ADDRESS>(1.2.1)
ok   Installed<EMAIL_ADDRESS>(0.1.1)
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed aurelia-animator-css as<EMAIL_ADDRESS>(1.0.2)
ok   Installed<EMAIL_ADDRESS>(0.10.3)
Looking up npm:indexof
ok   Installed<EMAIL_ADDRESS>(1.4.1)
ok   Installed<EMAIL_ADDRESS>(1.0.0)
ok   Installed<EMAIL_ADDRESS>(1.0.2)
ok   Installed<EMAIL_ADDRESS>(0.0.4)
ok   Installed plugin-babel as<EMAIL_ADDRESS>(0.0.24)
ok   Installed<EMAIL_ADDRESS>(0.0.1)
ok   Installed i18next as<EMAIL_ADDRESS>(3.5.2)
ok   Installed crypto as<EMAIL_ADDRESS>(0.2.1)
ok   Installed stream as<EMAIL_ADDRESS>(0.2.1)
ok   Installed zlib as<EMAIL_ADDRESS>(0.2.3)
ok   Installed aurelia-fetch-client as<EMAIL_ADDRESS>(1.1.2)
ok   Installed<EMAIL_ADDRESS>(1.1.0)
ok   Installed<EMAIL_ADDRESS>(1.1.2)
ok   Installed aurelia-framework as<EMAIL_ADDRESS>(1.1.2)
ok   Installed<EMAIL_ADDRESS>(0.1.35)
ok   Installed npm:jquery (2.2.4)
ok   Installed jquery as npm:jquery@2 (2.2.4)
ok   Installed<EMAIL_ADDRESS>(1.4.0)
ok   Installed aurelia-bootstrapper as<EMAIL_ADDRESS>(2.1.1)
ok   Installed aurelia-validation as<EMAIL_ADDRESS>(1.0.0)
ok   Installed froala-editor as<EMAIL_ADDRESS>(2.6.1)
ok   Installed moment as<EMAIL_ADDRESS>(2.18.1)
ok   Installed<EMAIL_ADDRESS>(1.2.5)
ok   Installed aurelia-i18n as<EMAIL_ADDRESS>(1.6.1)
Removing unused package.json override<EMAIL_ADDRESS>Removing unused package.json override<EMAIL_ADDRESS> The following new package versions were substituted by install deduping:

   jquery 3.2.1 -> 2.2.4
   inherits 2.0.1 -> 2.0.3

 Installed Forks

                                            npm:inherits 2.0.1 2.0.3
                                             npm:isarray 0.0.1 1.0.0
                                       npm:os-browserify 0.1.2 0.3.0
                                     npm:readable-stream 1.1.14 2.3.1
                                         npm:safe-buffer 5.0.1 5.1.0
                                   npm:stream-browserify 1.0.0 2.0.1
                                      npm:string_decoder 0.10.31 1.0.2

 To inspect individual package constraints, use jspm inspect registry:name.

 Looking up loader files...
   system.js.map
   system.js
   system-csp-production.js.map
   system-polyfills.js
   system.src.js
   system-csp-production.src.js
   system-polyfills.src.js
   system-csp-production.js
   system-polyfills.js.map

 Using loader versions:
<EMAIL_ADDRESS> Looking up npm:babel-runtime
 Looking up npm:core-js
 Looking up github:jspm/nodelibs-path
 Looking up npm:path-browserify

ok   Installed<EMAIL_ADDRESS>(0.1.0)
ok   Installed<EMAIL_ADDRESS>(0.0.0)
ok   Installed babel-runtime as<EMAIL_ADDRESS>(5.8.38)
ok   Installed core-js as<EMAIL_ADDRESS>(1.2.7)
ok   Loader files downloaded successfully
ok   Install complete.

./node_modules/.bin/jspm install github:mreiche/aurelia-materialize-bridge --dev
Looking up github:mreiche/aurelia-materialize-bridge
Updating registry cache...
Looking up npm:aurelia-binding
Looking up npm:aurelia-dependency-injection
Looking up npm:aurelia-logging
Looking up npm:aurelia-metadata
Looking up npm:aurelia-pal
Looking up npm:aurelia-router
Looking up npm:aurelia-task-queue
Looking up npm:aurelia-templating
Looking up github:aurelia-ui-toolkits/aurelia-materialize-bridge
Looking up npm:aurelia-event-aggregator
Looking up npm:aurelia-history
Looking up npm:aurelia-path
Looking up npm:aurelia-route-recognizer
Looking up npm:aurelia-loader
ok   Installed mreiche/aurelia-materialize-bridge as<EMAIL_ADDRESS>(0.28.0)
Installed Forks
                                            npm:inherits 2.0.1 2.0.3
                                             npm:isarray 0.0.1 1.0.0
                                       npm:os-browserify 0.1.2 0.3.0
                                     npm:readable-stream 1.1.14 2.3.1
                                         npm:safe-buffer 5.0.1 5.1.0
                                   npm:stream-browserify 1.0.0 2.0.1
                                      npm:string_decoder 0.10.31 1.0.2

 To inspect individual package constraints, use jspm inspect registry:name.

ok   Install complete.
`

Using loader versions:
<EMAIL_ADDRESS>
JSPM 0.16 uses SystemJS 0.19

@mreiche the description of this issue is Unable to install via JSPM 0.17 (beta) so, 0.17 uses systemjs 0.20

sorry my false, i installed jspm locally but not beta... i have to try it again, sorry

I get the same error but when i run it as single installation it works, strange! node_modules/.bin/jspm install npm:materialize-css

I'm going to try this now.

me, too ! the error is located here: https://github.com/jspm/jspm-cli/blob/master/lib/package.js#L98

@Thanood if you have node 6 its very easy to debug with chrome dev tools:
test.js:
var jspm = require('jspm');
// // reproducible install from package.json
jspm.install(true, { lock: true })

node --inspect --debug-brk test.js

Thanks, I'll try that, too.
So, I installed the bridge with jspm 0.17 and got the same error.
I've cleared my jspm cache, installed again and nothing changed.
So I had a look at the cache (c:\Users\Daniel\AppData\Local\.jspm\packages\npm\).
There is a file called<EMAIL_ADDRESS>with this content:
{
  "dependencies": {
    "aurelia-binding"<EMAIL_ADDRESS>    "aurelia-dependency-injection"<EMAIL_ADDRESS>    "aurelia-logging"<EMAIL_ADDRESS>    "aurelia-metadata"<EMAIL_ADDRESS>    "aurelia-pal"<EMAIL_ADDRESS>    "aurelia-router"<EMAIL_ADDRESS>    "aurelia-task-queue"<EMAIL_ADDRESS>    "aurelia-templating"<EMAIL_ADDRESS>  },
  "peerDependencies": {
    "materialize-css"<EMAIL_ADDRESS>  }
}

Where does that peerDependency come from? It's nowhere in my config and it's also not present in the jspm registry..

@Thanood i believe the jspm npm loader grab it from here -> https://github.com/aurelia-ui-toolkits/aurelia-materialize-bridge/blob/master/package.json#L109

@Thanood its not L109 ! i replace it with an other lib :(

@Thanood its not https://github.com/aurelia-ui-toolkits/aurelia-materialize-bridge/blob/master/package.json#L109 ! i replaced it with an another. Get the same error!

@SerkanSipahi That was @mreiche's initial thought. He removed it from his fork, installed that and nothing happened.
I debugged jspm but tbh I lost track after the 10th or so iteration of loading dependencies of aurelia-something. 😕

@Thanood you are right

@Thanood please look at here -> https://github.com/jspm/jspm-cli/blob/5963d0e7929d5d277f670af64f03ed75743ecc9d/lib/package.js#L614 here is most likely<EMAIL_ADDRESS>created !

Okay, it has a peerDependency and it seems to load from package.json as @mreiche suggested.
@mreiche I'm not sure why installing github:mreiche/aurelia-materialize-bridge didn't change anything for you. I suspect that it reads the dependency configuration from the cached bridge anyway. Because when I deleted it from my cache and installed github:mreiche/aurelia-materialize-bridge it worked.
console log:
$ jspm i
     Updating registry cache...
ok   Peer aurelia-logging to<EMAIL_ADDRESS>(1.3.1)
ok   Peer aurelia-logging-console to<EMAIL_ADDRESS>(1.0.0)
ok   Peer aurelia-path to<EMAIL_ADDRESS>(1.1.1)
ok   Peer aurelia-history to<EMAIL_ADDRESS>(1.0.0)
ok   Peer aurelia-loader to<EMAIL_ADDRESS>(1.0.0)
ok   Peer aurelia-event-aggregator to<EMAIL_ADDRESS>(1.0.1)
ok   Peer aurelia-pal to<EMAIL_ADDRESS>(1.3.0)
ok   Peer aurelia-metadata to<EMAIL_ADDRESS>(1.0.3)
ok   Peer aurelia-loader-default to<EMAIL_ADDRESS>(1.0.2)
ok   Peer aurelia-history-browser to<EMAIL_ADDRESS>(1.0.0)
ok   Peer aurelia-dependency-injection to<EMAIL_ADDRESS>(1.3.1)
ok   Peer aurelia-task-queue to<EMAIL_ADDRESS>(1.2.0)
ok   Peer aurelia-pal-browser to<EMAIL_ADDRESS>(1.2.1)
ok   Peer aurelia-polyfills to<EMAIL_ADDRESS>(1.2.1)
ok   Peer aurelia-route-recognizer to<EMAIL_ADDRESS>(1.1.0)
ok   Peer aurelia-router to<EMAIL_ADDRESS>(1.3.0)
ok   Peer aurelia-binding to<EMAIL_ADDRESS>(1.2.1)
ok   Peer aurelia-templating to<EMAIL_ADDRESS>(1.4.2)
ok   Peer aurelia-templating-router to<EMAIL_ADDRESS>(1.1.0)
ok   Peer aurelia-framework to<EMAIL_ADDRESS>(1.1.2)
ok   Peer aurelia-templating-binding to<EMAIL_ADDRESS>(1.3.0)
ok   Peer aurelia-templating-resources to<EMAIL_ADDRESS>(1.4.0)
ok   aurelia-bootstrapper to<EMAIL_ADDRESS>(2.1.1)
ok   Dev dependency plugin-babel to<EMAIL_ADDRESS>(0.0.24)
ok   aurelia-materialize-bridge to github:mreiche/aurelia-materialize-bridge@master (master)
     Install tree has no forks.

ok   Install complete.

package.json:
{
  "name": "jspm017",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "jspm": "^0.17.0-beta.42"
  },
  "jspm": {
    "name": "jspm017",
    "main": "jspm017.js",
    "dependencies": {
      "aurelia-bootstrapper"<EMAIL_ADDRESS>      "aurelia-materialize-bridge": "github:mreiche/aurelia-materialize-bridge@master"
    },
    "devDependencies": {
      "plugin-babel"<EMAIL_ADDRESS>    },
    "peerDependencies": {
      "aurelia-binding"<EMAIL_ADDRESS>      "aurelia-dependency-injection"<EMAIL_ADDRESS>      "aurelia-event-aggregator"<EMAIL_ADDRESS>      "aurelia-framework"<EMAIL_ADDRESS>      "aurelia-history"<EMAIL_ADDRESS>      "aurelia-history-browser"<EMAIL_ADDRESS>      "aurelia-loader"<EMAIL_ADDRESS>      "aurelia-loader-default"<EMAIL_ADDRESS>      "aurelia-logging"<EMAIL_ADDRESS>      "aurelia-logging-console"<EMAIL_ADDRESS>      "aurelia-metadata"<EMAIL_ADDRESS>      "aurelia-pal"<EMAIL_ADDRESS>      "aurelia-pal-browser"<EMAIL_ADDRESS>      "aurelia-path"<EMAIL_ADDRESS>      "aurelia-polyfills"<EMAIL_ADDRESS>      "aurelia-route-recognizer"<EMAIL_ADDRESS>      "aurelia-router"<EMAIL_ADDRESS>      "aurelia-task-queue"<EMAIL_ADDRESS>      "aurelia-templating"<EMAIL_ADDRESS>      "aurelia-templating-binding"<EMAIL_ADDRESS>      "aurelia-templating-resources"<EMAIL_ADDRESS>      "aurelia-templating-router"<EMAIL_ADDRESS>    }
  }
}

IMO this is a bug in JSPM where it uses the default registry for npm peerDependencies instead of using the npm registry.

Filed an issue: https://github.com/jspm/jspm-cli/issues/2316

@mreiche Please try to clear materialize-bridge from your cache and try to install your fork again.
To save you some time, remove only the necessary files from c:\Users\<yourUserName>\AppData\Local\.jspm\packages\npm\ - which should be aurelia-materialize*

Reopened for discussion. :smiley:
Sent from my Samsung SM-G928F using FastHub

Clearing the caches doesn't help either:
Mikes-MacBook-Pro:myty-5 mike$ rm -rf ~/.jspm/
Mikes-MacBook-Pro:myty-5 mike$ ./node_modules/.bin/jspm cache-clear
ok   Loader file cache cleared.
ok   Package cache cleared.

warn All caches cleared.
     Please post an issue if you suspect the cache isn't invalidating properly.
     jspm install -f is equivalent to running a cache clear for that specific package tree.
Mikes-MacBook-Pro:myty-5 mike$ ./node_modules/.bin/jspm install github:mreiche/aurelia-materialize-bridge -f --dev
     Creating registry cache...
     Downloading<EMAIL_ADDRESS>
[...]

ok   Installed dev dependency<EMAIL_ADDRESS>(1.2.1)

err  Repo jspm:materialize-css not found. Perhaps try jspm install npm:materialize-css.

warn Installation changes not saved.

Mikes-MacBook-Pro:myty-5 mike$ grep -R "materialize-css" ~/.jspm/ | grep "mreiche"
<EMAIL_ADDRESS>   "materialize-css"<EMAIL_ADDRESS>
Im now trying the suggested override in the pull request.

Now, that's strange.. The only reason I can think about here is that your cache was not "really" cleared and materialize-bridge persisted somehow.
I've deleted the file and directory manually several times while debugging. So this may be different from clearing the cache.
Although the log says...
Please post an issue if you suspect the cache isn't invalidating properly.
jspm install -f is equivalent to running a cache clear for that specific package tree.

Hallelujah, it works with override: ./node_modules/.bin/jspm install aurelia-materialize-bridge --dev -o override.json
    Updating registry cache...
     Downloading<EMAIL_ADDRESS>[...]
ok   Installed dev dependency aurelia-materialize-bridge to<EMAIL_ADDRESS>(0.28.0)
     Installed Forks

[...]
ok   Install complete.

override.json
{
        "peerDependencies": {
                "materialize": "npm:materialize-css"
        }
}

I wonder if it works if I add an explicit jspm peerDependency instead of removing the one in npm..
But I think removing it should also be okay.


Playground breakpoints: removal of last breakpoint leads to spurious "Run" action

Here is the sequence. Notice the missing 4 in the last screen shot: Removing the last breakpoint triggered a "Run".

This bug is still there. Just tried. Here is the program:
https://share.sourceacademy.nus.edu.sg/1ijs1

When the number of breakpoints goes from 1 to 0, line 763 is run which clears the REPL output:
https://github.com/source-academy/frontend/blob/5391c8a76bc51822cac281d29b54186c385a8cc4/src/pages/playground/Playground.tsx#L744-L770
The reason this is done is because playground.debuggerContext.result.value is an array of objects used by the stepper (at least in Source 1) when the breakpoint is set:

Whereas without breakpoints, the playground.debuggerContext.result.value is an actual value that the REPL can display:

As such, we are forced to clear the REPL output because if the stepper's playground.debuggerContext.result.value is parsed by the normal REPL, the frontend crashes. @martin-henz It would seem that playground.debuggerContext.result.value is being used for 2 different purposes, and should be refactored into separate variables if we want to fix this bug.

The stepper's use of breakpoints is quite lame right now: It switches to the stepper when a breakpoint is set, but it doesn't do anything with the breakpoints. It seems like the use of breakpoints by stepper wasn't well designed. Would it be a lot of trouble removing breakpoints from the stepper entirely? The loss would be minimal. Then, once we have a clear idea how to make use of breakpoints in the stepper, we can revisit this, hopefully with a better solution.

The stepper's use of breakpoints is quite lame right now: It switches to the stepper when a breakpoint is set, but it doesn't do anything with the breakpoints. It seems like the use of breakpoints by stepper wasn't well designed. Would it be a lot of trouble removing breakpoints from the stepper entirely? The loss would be minimal. Then, once we have a clear idea how to make use of breakpoints in the stepper, we can revisit this, hopefully with a better solution.

It seems that the refactoring might not be as simple as removing breakpoints from the stepper entirely since the debuggerContext.result.value is used by the stepper. In fact, the current design has led to previous bugs such as the one fixed in #2305. There is an issue #2306 that is tracking the same refactoring that is necessary to solve this issue.


Multiecho reporting: Compare closest echo and T2* map

Need to identify the correct echo for comparison.
Original echo will contain out-of-mask voxels; T2* map will contain recovered signal voxels.
This was indicated as nice-to-have, rather than diagnostic.
cc @tsalo for verification

I think you'll need hard-coded values for the standard TEs at different field strengths. Unless there's a pre-existing curve you can use?

I don't have a reference, but will ask around.
Just to get it down, I believe you mentioned 30ms for 3T. I don't know about 1.5T or 7T but presumably can find some papers and get a sense of the range.


[#4910] Add documentation example for Lint/UnneededDisable

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests(rake spec) are passing.
[x] The new code doesn't generate RuboCop offenses that are checked by rake internal_investigation.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

It looks like RuboCop is registering an offense for the example that you provided. Should this be considered a bug in Lint/UnneededDisable?

Ha, no, this is "working as intended". Let me rethink the best way to do an example.

Though disabling Lint/UnneededDisable resolves the internal rubocop offense, it also adds the disable and enable to the documentation. Is there a better mechanism to include an example?

You'll also have to rebase on master.

Done (rebased). PTAL.

Thanks!


[ avcpp ] Update version

updates avcpp. They accepted the "remove problematic compound literal" patch, so we can delete it from vcpkg.

reverted the port version and updated the vcpkg versions.

@barcharcraz ,Please add "vcpkg_cmake_pkgconfig()" in the portfile.cmake

@barcharcraz ，After modifying the content I suggest, we can merge this pr

LGTM, thanks!


SPUserProfileProperty Fix IsSearchable / Add IsReplicable

Pull Request (PR) description
SPUserProfileProperty Fix IsSearchable / Add IsReplicable
This Pull Request (PR) fixes the following issues

Fixes #1164

Task list

[X] Added an entry to the change log under the Unreleased section of the
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
[X] Resource documentation added/updated in README.md.
[X] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[X] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[X] Examples appropriately added/updated.
[X] Unit tests added/updated. See DSC Community Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
[X] New/changed code adheres to DSC Community Style Guidelines.

This change is

A change in one of the CD/CI modules is causing the unit tests to fail. Will submit a PR to have this issue fixed, after which you can update your branch from master.

I was wrong, this wasn't caused by an updated module. You targeted this PR against dev, but we are not using the dev branch anymore. Can you please update from master and retarget the PR to master?

@ykuijs Ok, thanks for the awareness.  I did target Dev thinking that was still the approach.  I will target this against master this evening (and should have a few more items in there as well).

No problem, removing the dev branch is still on my ToDo list :-)

Had to update the PR with recently merged changes. Will merge this PR as soon as the tests complete.


Loading indicator on Recent topics screen for logged out users

The loading indicator appears (and sticks around) in the middle of the Recent topics view for logged out users. We should fix this.

@amanagr FYI

I'm going to go ahead and fix this since it's quick, messy, and it'll be nice to check off.


Delete unnecessary config fields

Codecov Report

Merging #293 into master will decrease coverage by 0.13%.
The diff coverage is 45.45%.

@@            Coverage Diff             @@
##           master     #293      +/-   ##
==========================================
- Coverage   76.69%   76.56%   -0.14%
==========================================
  Files          21       21
  Lines        1399     1408       +9
  Branches      241      241
==========================================
+ Hits         1073     1078       +5
- Misses        326      330       +4

Impacted Files
Coverage Δ

lib/index.js
9.52% <0%> (-0.48%)
:arrow_down:

lib/worker.js
65% <100%> (+1.12%)
:arrow_up:

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 c37f903...de004c8. Read the comment docs.


view mode selector don't work correctly

error on view mode selector buttons functionality

session storage don't save "from" and "to" date

session storage don't save "from" and "to" date


Data Table sortable needs to be set to True

Request Type

[X] Small Fix (wording, errors, typos, etc.)

Description
Documentation states that Data Table "sortable" option default = True. However, sorting does not work unless sortable=true in Data Table.
Either doco error (default = False ?) or fix code.

Hi @mrpanda - I can't reproduce this

What platform is this on?

Hi Archie, I have found the problem. The build process was still running in the background. If I had waited another 5 seconds then I would have seen this. Sorry, the computer must have been slow at that time and I jumped to conclusions, because I added 'sortable=true' and it started working straight away. I have checked several times now before writing this, issue is fine and I am on latest version of Evidence.


resolvePackageSync: fixed infinite loop

Fixes #27
Ref #28

Looks good.

@creationix ;-) So?

Guys, can you merge this, please?
/cc @fjakobs @cadorn

me no have access no more

thanks for fixing this!


Update readme with Taiwan flag

Hi @MattKiazyk ,
Thanks for adding localization contributors section recently. In Traditional Chinese localization, the flag is wrong. So, I change the flag into 🇹🇼 for Traditional Chinese.

Thank you @MattKiazyk !


Geocoders .near method not working

Everytime i do this :
data = Datum.near([-1.381776,36.7689503],300,:units => :km)

I get:
 Datum Load (0.3ms)  SELECT  data.*,<PHONE_NUMBER>4455873 * ABS(data.latitude - -1.381776) * 0.7071067811865475) + (96.29763124613503 * ABS(data.longitude - 36.7689503) * 0.7071067811865475) AS distance, CASE WHEN (data.latitude >= -1.381776 AND data.longitude >= 36.7689503) THEN  45.0 WHEN (data.latitude <  -1.381776 AND data.longitude >= 36.7689503) THEN 135.0 WHEN (data.latitude <  -1.381776 AND data.longitude <  36.7689503) THEN 225.0 WHEN (data.latitude >= -1.381776 AND data.longitude <  36.7689503) THEN 315.0 END AS bearing FROM "data" WHERE (data.latitude BETWEEN -4.079740817756191 AND 1.3161888177561916 AND data.longitude BETWEEN 34.07020071373121 AND 39.46769988626879) ORDER BY distance ASC LIMIT ?  [["LIMIT", 11]]
 => #<ActiveRecord::Relation []>

An empty array,despite the fact that i have so many records in my database,i even increased the limit to 300 still nothing,
=>#<ActiveRecord::Relation[]>
i keep getting this output on the rails  console everytime i run .near method to find all near locations.What could be the issue or what could this output mean?How do i resolve it and get it to return actual data instead of an empty array ?
Environment info

Geocoder version: 1.4.4
Rails version: 5
Database (if applicable): SQLite

I solved this by specifying:
MyModel.geocoded.near(x, y, z)
You must query the geocode of the model, not just the model.
LMK if this helps you.

@kamillamagna What is the difference between MyModel.geocoded.near(x, y, z) and MyModel.near(x, y, z)? I only see .geocode just removes the records where lat and long is NULL. Is there any other differences? Currently I am having some issues with the .near method, and after search I got this issue ticket.


Bug/EPIC: Revitalize data consistency assessment

We have a maybe or maybe-not outdated script for checking pgSQL <--> S3 consistency and finding projects where previous storage hardware incidents caused data loss. This is in the admin-panels, as a jupyter notebook.
After talking to @anderegg we plan to:

Refactor admin-panel code into more atomic, pure python functions
As a PoC, we will tackle only file_meta_data table assessment
We try to put the evaluation of the number of faulty entries into a prometheus metric calculated every hour in the background and exposed by the storage microservice

See: https://git.speag.com/oSparc/osparc-ops-environments/-/issues/164


The issue I encountered while deploying a demo via Helm according to the official documentation

Discussed in https://github.com/open-telemetry/opentelemetry-demo/discussions/1444

Originally posted by caozhangni March  9, 2024
I encountered an issue while deploying a demo via Helm according to the official documentation(https://opentelemetry.io/docs/demo/kubernetes-deployment/#configure-browser-telemetry). The documentation suggests modifying the PUBLIC_OTEL_EXPORTER_OTLP_TRACES_ENDPOINT via env, but I found that this causes some environment variables to be lost, leading to abnormal functioning of the frontend component. The list of environment variables in the container is as follows:

Environment:
OTEL_SERVICE_NAME:                                   (v1:metadata.labels['app.kubernetes.io/component'])
OTEL_COLLECTOR_NAME:                                my-otel-demo-otelcol
OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE:  cumulative
PUBLIC_OTEL_EXPORTER_OTLP_TRACES_ENDPOINT:          http://otel.czn.com/otlp-http/v1/traces
OTEL_RESOURCE_ATTRIBUTES:                           service.name=$(OTEL_SERVICE_NAME),service.namespace=opentelemetry-demo

After replacing it with envOverride, the issue was resolved, and everything worked well:

Environment:
OTEL_SERVICE_NAME:                                   (v1:metadata.labels['app.kubernetes.io/component'])
OTEL_COLLECTOR_NAME:                                my-otel-demo-otelcol
OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE:  cumulative
FRONTEND_PORT:                                      8080
FRONTEND_ADDR:                                      :8080
AD_SERVICE_ADDR:                                    my-otel-demo-adservice:8080
CART_SERVICE_ADDR:                                  my-otel-demo-cartservice:8080
CHECKOUT_SERVICE_ADDR:                              my-otel-demo-checkoutservice:8080
CURRENCY_SERVICE_ADDR:                              my-otel-demo-currencyservice:8080
PRODUCT_CATALOG_SERVICE_ADDR:                       my-otel-demo-productcatalogservice:8080
RECOMMENDATION_SERVICE_ADDR:                        my-otel-demo-recommendationservice:8080
SHIPPING_SERVICE_ADDR:                              my-otel-demo-shippingservice:8080
OTEL_COLLECTOR_HOST:                                $(OTEL_COLLECTOR_NAME)
OTEL_EXPORTER_OTLP_ENDPOINT:                        http://$(OTEL_COLLECTOR_NAME):4317
WEB_OTEL_SERVICE_NAME:                              frontend-web
PUBLIC_OTEL_EXPORTER_OTLP_TRACES_ENDPOINT:          http://otel.czn.com/otlp-http/v1/traces
OTEL_RESOURCE_ATTRIBUTES:                           service.name=$(OTEL_SERVICE_NAME),service.namespace=opentelemetry-demo

This issue is now fixed in docs


Replace String with our own FastString for some cases

Motivation
String and StringBuilder instances are heavy in some cases because they may wrap a large byte array.
And there is a performance problem that Java itself or our deps will copy the underlying byte array when replace, concat, toString(in StringBuilder) and etc, which is a waste and terrible for performance.
Solution
We will implement our own FastString to avoid copying. Furthermore, we can use pools so that we don't even need to create new byte arrays.

Closed for now because we introduce StringUtil which can get the internal bytes of String and create new strings efficiently.


🐛 Bug Report: Workflow annotation closure in python is not cleared on exiting the function

Which component is this bug for?
Traceloop SDK
📜 Description
When you are reporting metrics to Otel in the Python SDK, using the annotations (@workflow and @task) to describe the levels, the Workflow annotation is not cleared when exiting the function.
If no followup workflow annotation is given prior to another task being encountered, the 'traceloop.workflow.name' attribute on subsequent tasks will be the last workflow encountered
👟 Reproduction steps
Using the traceloop-sdk version 0.25.1
Using this example code:
traceloop.workflow.name@task()
def task_wrapper():
    pass
@workflow()
def workflow_wrapper():
    task_wrapper()

@task()
def workflowless_task():
    pass

workflowless_task() #has no workflow when the metric is sent up
workflow_wrapper() #metric sent up has workflow and task wrapper correctly assigned
workflowless_task()# Metric has the workflow from above (incorrect) with the correct task

👍 Expected behavior
workflow should be cleared when exiting the function. It should reset to null
👎 Actual Behavior with Screenshots
The below shows the create a story task being incorrectly assigned a workflow some of the time

🤖 Python Version
3.11
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

@nirga Do we have any plan for the issue? Thanks.   cc @gyliu513


Patron Order PVP gear

When adding a patron order for PVP gear to the craft queue and then create a shopping list, it tries to buy Forged Combatant's Heraldry even though the blue kind is provided.

To add to this bug, when going through the craft queue, these pvp items fail to craft.

should be fixed in 19.4.2

This is still happening in 19.5.0. The Auctioneer shopping list still included the heraldry and the queue thinks it's missing.


python312Packages.pymeteireann: 2021.8.0 -> 2024.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.pymeteireann is: Python module to communicate with the Met Éireann Public Weather Forecast API
meta.homepage for python312Packages.pymeteireann is: https://github.com/DylanGore/PyMetEireann/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.11.0 with grep in /nix/store/kmnrmi8smqz6ngg3rbxlkzn40vzy49l1-python3.12-pymeteireann-2024.11.0
found 2024.11.0 in filename of file in /nix/store/kmnrmi8smqz6ngg3rbxlkzn40vzy49l1-python3.12-pymeteireann-2024.11.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.met_eireann
python311Packages.pymeteireann
python312Packages.pymeteireann

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kmnrmi8smqz6ngg3rbxlkzn40vzy49l1-python3.12-pymeteireann-2024.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.pymeteireann https://github.com/r-ryantm/nixpkgs/archive/c0848e37296b17f98bfde11ec573c23d80028444.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c0848e37296b17f98bfde11ec573c23d80028444#python312Packages.pymeteireann

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kmnrmi8smqz6ngg3rbxlkzn40vzy49l1-python3.12-pymeteireann-2024.11.0
ls -la /nix/store/kmnrmi8smqz6ngg3rbxlkzn40vzy49l1-python3.12-pymeteireann-2024.11.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.met_eireann
python311Packages.pymeteireann
python311Packages.pymeteireann.dist
python312Packages.pymeteireann
python312Packages.pymeteireann.dist

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 358642

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.met_eireann
python311Packages.pymeteireann
python311Packages.pymeteireann.dist
python312Packages.pymeteireann
python312Packages.pymeteireann.dist


Canned (set/template)responses to requests

Create a way that pre-set template messages can be created and then selected as the official reply to a request.

To do this, someone has to create and save these responses (a supervisor/ experienced administrator).
They should be easy to select
There may be many pre-set messages for a certain subject matter eg. covid-19 may have one message for general instructions, one for retired folks, one for pregnant mothers etc.

Example for COVID-19 issue canned response
Thank you for getting in touch with us. We have received your request and will attend to it shortly.
What do I do if I suspect that I have/someone else has COVID-19?
Symptoms of COVID-19 include fever w/ cough, sore throat, and difficulty breathing.
If you have returned from abroad or have associated with someone who has COVID-19 or someone suspected of being infected within the past 14 days, please immediately contact the Public Health Inspector (PHI) or the hotline number below:
Call your area PHI to inform them. You can access a list of PHIs here
Call 1999 hotline for medical and other advice regarding Covid-19.
Call 1990 for ambulance facilities in case of an emergency.
Until you receive assistance and/or are tested, please isolate yourself from others.
Useful Links:
Ministry of Health
Epidemiology Unit updates on COVID-19
PMD News

We have received your request
For assistance regarding COVID-19:
Call 1999 hotline for medical and other advice
Call 1990 for ambulance facilities in case of an emergency