Added variables to make customizing the prompt easier.

Added the following variables to $global:GitPromptSettings to make customizing the prompt easier.

AddedText, default '+'

ModifiedText, default '~'

RemovedText, default '-'

ConflictedText, default '!'

It may be noteworthy that LocalWorkingStatusSymbol and ConflictedText will have the same content by default (“!”), as will LocalStagedStatusSymbol and ModifiedText (“~”)—this could lead to confusion. However, I didn’t want to delete existing variables, so I left them alone for the time being.
I also realigned the indenting on the block of stash-related variables within GitPromptSettings.

Thanks for this! Two suggestions:

Add a "File" prefix to these properties to hopefully clear up some of the shared symbol confusion?
Rather than concatenate strings ((" " + $s.AddedText + "$($status.Index.Added.Count)"), it's more idiomatic to use string expansion: (" $($s.AddedText)$($status.Index.Added.Count)").

Okay, fixed that stuff. Check out commit 2e06383ddc4f8991776b07b5905317cdce025943.

Would you mind rebasing this branch on latest master and --force pushing back to this PR branch? Some merge weirdness going on here.

Okay, I believe I rebased it correctly, but check to make sure.

It changed, but still weird:
*   f3b3670 Merge remote-tracking branch 'refs/remotes/origin/promptVariables' into promptVariables
|\
| * 2e06383 Changed variables, string concat to expansion. Added "File" prefix to (now) FileAddedText, FileModifiedText, FileRemovedText, and FileConflictedText--before, LocalWorkingStatusSymbol and ConflictedText had the same content by default ("!"), as did LocalStagedStatusSymbol and ModifiedText ("~").
* | 59069a5 Changed variables, string concat to expansion. Added "File" prefix to (now) FileAddedText, FileModifiedText, FileRemovedText, and FileConflictedText--before, LocalWorkingStatusSymbol and ConflictedText had the same content by default ("!"), as did LocalStagedStatusSymbol and ModifiedText ("~").
* | 6c500d0 Changed variables, string concat to expansion. Added "File" prefix to (now) FileAddedText, FileModifiedText, FileRemovedText, and FileConflictedText--before, LocalWorkingStatusSymbol and ConflictedText had the same content by default ("!"), as did LocalStagedStatusSymbol and ModifiedText ("~").
|/
*   c916d10 Merge branch 'promptVariables' of https://github.com/9999years/posh-git
|\
| * 85a59b5 Added variables to make customizing the prompt easier. Added the following variables to $global:GitPromptSettings to make customizing the prompt easier.      Added "File" prefix to (now) FileAddedText, FileModifiedText, FileRemovedText, and FileConflictedText--before, LocalWorkingStatusSymbol and ConflictedText had the same content by default ("!"), as did LocalStagedStatusSymbol and ModifiedText ("~").
* 6c500d0 Changed variables, string concat to expansion. Added "File" prefix to (now) FileAddedText, FileModifiedText, FileRemovedText, and FileConflictedText--before, LocalWorkingStatusSymbol and ConflictedText had the same content by default ("!"), as did LocalStagedStatusSymbol and ModifiedText ("~").
*   c916d10 Merge branch 'promptVariables' of https://github.com/9999years/posh-git
|\
| * 85a59b5 Added variables to make customizing the prompt easier. Added the following variables to $global:GitPromptSettings to make customizing the prompt easier.     AddedText, default '+'     ModifiedText, default '~'     RemovedText, default '-'     ConflictedText, default '!'
* |   6bd5770 Merge pull request #255 from theaquamarine/keysfix
|\ \

Look somewhat cleaner, is this what you were going for?

Weird...I would expect a linear history:
* 95f6b34 Changed variables, string concat to expansion. Added "File" prefix to (now) FileAddedText, FileModifiedText, FileRemovedText, and FileConflictedText--before, LocalWorkingStatusSymbol and ConflictedText had the same content by default ("!"), as did LocalStagedStatusSymbol and ModifiedText ("~").
* 5321181 Changed variables, string concat to expansion. Added "File" prefix to (now) FileAddedText, FileModifiedText, FileRemovedText, and FileConflictedText--before, LocalWorkingStatusSymbol and ConflictedText had the same content by default ("!"), as did LocalStagedStatusSymbol and ModifiedText ("~").
* ca0d6b4 Added variables to make customizing the prompt easier. Added the following variables to $global:GitPromptSettings to make customizing the prompt easier.     AddedText, default '+'     ModifiedText, default '~'     RemovedText, default '-'     ConflictedText, default '!'

(And really, you can squash the second "Changed variables" commit into the first one.)
I wonder if part of your branch has been merged into your local master (git rev-parse master)? Try git branch -f master 6bd5770bc3d970927886232d82c518db798af247?

Actually, this is fine. Thanks for the contribution!


[README Enhancement]: Children vs Adults Classification

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : README Enhancement: Children vs Adults Classification
:red_circle: Aim : The aim is to enhance the README file and make it eye pleasing, well documented using the given README template.
:red_circle: README to be enhanced : https://github.com/abhisheks008/DL-Simplified/blob/main/Children vs Adults Classification using DL/Model/README.md
:red_circle: README Template : https://github.com/abhisheks008/DL-Simplified/blob/main/.github/readme_template.md

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@abhisheks008 Kindly assign this issue to me. I will make the necessary changes for the README file.
Full name : Vanshika Bisht
GitHub Profile Link : https://github.com/vanshikab52
Email ID<EMAIL_ADDRESS>Participant ID (if applicable): NA
Approach for this Project : To enhance the project's README file using the given template and make it properly well documented and appealing.
What is your participant role? (Mention the Open Source program) : GSSoC'24 Contributor

Issue assigned to you @vanshikab52. Go ahead!


Understanding and planning node.js and PHP servers

@langpavel, I just realized that I need to understand how to dispatch all the setLocal, setMe functions from the client.
There are two options for the serverr setup:

OPTION #1 - using Node.js to server the index.html, and it somehow injects the store into the client.  I do not understand how this works, can you please explain to me in our next session?  Please prepare an explanation so this goes smoothly.  In addition, my API server is PHP serving the API through json web tokens.

OPTION #2 - this uses the PHP as the backend server for index.html and the JWT API PHP.

I was planning on doing OPTION 2, but the code relies on server.js.
Here is a snippet from the code:
 const store = configureStore({}, {
      cookie: req.headers.cookie,
    });

    store.dispatch(setRuntimeVariable({
      name: 'initialNow',
      value: Date.now(),
    }));

    store.dispatch(setRuntimeVariable({
      name: 'availableLocales',
      value: locales,
    }));

    await store.dispatch(setLocale({
      locale,
    }));

I also want to do a store.dispatch(setMe{})  to fetch my PHP servers API to get the "me" info.  This is an example API from the server.  I will use this to help me learn how to fetch other requests and objects from the server as well.
Is it possible to move the stuff from server.js so I can inject the store from my PHP server for OPTION #2?

Hi. You can dispatch for example getUserInfo action on serer which can use isomorphic helper to make a XMLHttpRequest on client or HTTP request from server with JWT token. This way your app can be prerendered on server and client will smoothly mount on state.

Hi @langpavel so I did more of a my homework, it appears that I did not completely understand isomorphic web apps clearly.  Since the components are rendered on the server, then assuming that the PHP serves the HTML is not going to happen.  However, it will serve the API, which is basically OPTION #1 above.


ColumnEncodingUtility is breaking materialized views

Hello,
The ColumnEncodingUtility currently does not make the distinction between a regular table and a materialized view and it ends up breaking the materialized views when being run.
As far as I can see, when creating and refreshing a materialized view,  Redshift seem to do more or less the following (assume the view name is my_materialized_view) :

Create a table mv_tbl__my_materialized_view_0 (owner rdsdb)
Create a view vmy_materialized_view (owner current user) that point to mv_tbl__my_materialized_view_0

The ColumnEncodingUtility is picking up mv_tbl__my_materialized_view_0 since it is a regular table and if compresion is needed :

Create a new migrated mv_tbl__my_materialized_view_0_$mig
DROP CASCADE on mv_tbl__my_materialized_view_0 which in returns drops my_materialized_view
Rename mv_tbl__my_materialized_view_0_$mig to mv_tbl__my_materialized_view_0

Suggestion for a quick fix
Ignore tables where owner is rdsdb and assume Redshift optimized it already.
See : https://github.com/awslabs/amazon-redshift-utils/blob/master/src/ColumnEncodingUtility/analyze-schema-compression.py#L1023
Long term fix
Better handling of both non binding and materialized views and avoid CASCADE DROP.
Thanks you.
cc @IanMeyers

Thanks for raising this issue. We will resolve it in the update of the utility.

Amazon Redshift Column Encoding Utility is now deprecated. Instead, please use Redshift's Automatic Table Optimization features through:
ALTER TABLE table_name ALTER SORTKEY AUTO;
ALTER TABLE table_name ALTER DISTSTYLE AUTO;

https://docs.aws.amazon.com/redshift/latest/dg/t_Creating_tables.html


Verifying account with wrong password/ban/no account

When I try to login with a wrong password, no account, banned account, wrong encryption, it always says: verifying account
https://puu.sh/FILLC/72698dffaa.png
Tested with client 203 and 509

i can confirm.  see from lot time ago.

I make some test:

ClassicUO client not get any problem
Client <IP_ADDRESS> also not any problem

Possible happen only on very old client

Its only working for clients up to 7.
i maked test comment that line:

//if ( GetNetState()->m_clientVersion || GetNetState()->m_reportedVersion )	// only reply the packet to valid clients

and now giving error on 203 of bad password.

After a bit checking, the reason of the issue is really simple, it's because 0xEF packet only sent by 6x+ fully, so older clients doesn't send client data in pre login. So m_reportedVersion never setted for older versions.
I agree the alex solution, because I don't think we need to avoid sending reply that packet comes from client's itself. If some clients (which is made by coders not uo's itself) has issue with this packet, they should care of it. Honestly I don't understand why the developer restricted the reply with 6x+ clients or KR version clients.
As we see information in here; https://docs.polserver.com/packets/index.php?Packet=0xEF
Client datas only sent by KR and Latest 6x+ clients, so using that packet to restricting reply causes this issue, cancelling this line may be the best solution.


Returning normalised data

I have a use case where I want the returned value from the useQuery hook should be the normalised data instead of the reconstructed denormalised data. Would it be possible to configure this kind of behaviour

We have a DuckDB setup in our application with pre-normalized data, and an API that returns denormalized data. We want to use each data source independently based on different conditions, but need a common abstraction so that both sources return the same data structure.
Since denormalizing the DuckDB data at runtime would require too many API calls to the server, we've decided to normalize the API data instead.
The API returns deeply nested data like this:
  "id": "obj_123",
  "type": "primary",
  "parent": {
    "id": "parent_456",
    "type": "container",
    "metadata": {
      "id": "meta_789",
      "reference": "REF-001"
    }
  },
  "assignee": {
    "id": "user_101",
    "details": {
      "id": "profile_202",
      "level": "standard"
    }
  },
  "components": [
    {
      "id": "comp_303",
      "subcomponent": {
        "id": "sub_404",
        "status": "active"
      }
    }
  ],
  "status": {
    "id": "status_505",
    "current": {
      "id": "state_606",
      "name": "in_progress"
    }
  }
}```
While DuckDB contains normalized data like this:
```{
  "id": "obj_123",
  "type": "primary",
  "parent": "parent_456"
  },
  "assignee": "user_101",
  "components": [
    "comp_303"
  ],
  "status": "status_505"
}```

I attempted to use 'normy' to normalize the API data, but when querying through react-query, it still returned the denormalized structure."

What normy does, is that it keeps normalized store separately, outside of useQuery. UseQuery will always return original server data, usually this is what we want. The biggest normy usecase is to normalize data in order to have features like:

automatic data updates
being able to get nodes by id, without even knowing query id
being able to refetch dependent queries, even without knowing what keys to update, as this will be calculated by normy

Did you try to use getNormalizeData I pasted before?


Fix No Elected Primary Cluster Manager

Blocks calls to ServeHTTP until a primary cluster manager is selected.
Adds logic to route request to ourself if we become the leader while blocking.
/cc @wsong
Signed-off-by: Drew Erny<EMAIL_ADDRESS>

/ping @nishanttotla for review

Overall code LGTM (seems to do what we discussed yesterday).
I still need to more carefully look at the test you have created. We also need integration testing for this, either as bats tests or just manually testing out the offending scenarioo.

@nishanttotla @anshulpundir rebased, fixed comment typos, and added a really big comment explaining the use of the RWMutex with the Cond.

@dperny @vikstrous how did the testing on this PR turn out?

DTR has approved the changes: https://github.com/docker/orca/pull/10553


Tron trigger smart contract block decode

decode trigger smart contracts in blocks

Problem Definition / Why?
it does not decode block for TRC20 tokens
Where/how shows?
In Tron Platform
Proposal
It was ignoring blocks for trigger smart contract types

let me to do this if its possible


How WaterLine schema design to embed document?

When I use sails framework with the WaterLine orm , and I use mongodb database,
how can I design embed sub document schema?

It's currently not officially supported in Waterline. You can use type: 'json' to store nested objects but searching them isn't available yet.
You can follow along with progress at: https://github.com/balderdashy/waterline/issues/658


Resolving documantation build warnings

As mentioned in #757, our docs are building successfully, though with several warnings:
reading sources... [  2%] api
Cannot locate code for 'message_ix.models.DEFAULT_CPLEX_OPTIONS' or parent class/module
Cannot locate code for 'message_ix.models.MESSAGE_ITEMS' or parent class/module
Cannot locate code for 'message_ix.macro.MACRO_ITEMS' or parent class/module

reading sources... [100%] whatsnew

/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/checkouts/latest/doc/api.rst:24: WARNING: autosummary: failed to import ixmp.testing.make_dantzig.
Possible hints:
* AttributeError: module 'ixmp' has no attribute 'testing'
* ModuleNotFoundError: No module named 'pytest'
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/checkouts/latest/doc/reporting.rst:282: WARNING: autosummary: failed to import genno.compat.pyam.computations.as_pyam.
Possible hints:
* AttributeError: module 'genno.compat.pyam' has no attribute 'computations'
* AttributeError: module 'message_ix.reporting.computations' has no attribute 'genno'
* ModuleNotFoundError: No module named 'genno.compat.pyam.computations'
* ModuleNotFoundError: No module named 'message_ix.reporting.computations.genno'; 'message_ix.reporting.computations' is not a package

/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.add:8: ERROR: Undefined substitution referenced: "KeyLike".
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.add:8: ERROR: Undefined substitution referenced: "KeyLike".
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.check_keys:1: ERROR: Undefined substitution referenced: "KeyLike".
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.check_keys:19: ERROR: Undefined substitution referenced: "KeyLike".
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.infer_keys:1: ERROR: Undefined substitution referenced: "KeyLike".
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.infer_keys:1: ERROR: Undefined substitution referenced: "KeyLike".
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.infer_keys:17: ERROR: Undefined substitution referenced: "KeyLike".
/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.infer_keys:18: ERROR: Undefined substitution referenced: "KeyLike".

writing output... [100%] whatsnew

/home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.cache:3: WARNING: unknown document: 'cache'
generating indices... /home/docs/checkouts/readthedocs.org/user_builds/iiasa-energy-program-message-ix/envs/latest/lib/python3.11/site-packages/message_ix/reporting/__init__.py:docstring of genno.core.computer.Computer.configure:8: WARNING: unknown document: 'config'

These warnings and errors probably mean that some aspects of our framework are not documented as expected, though most of that seems to be due to erroneous links. We should investigate how these links ought to look so that our documentation can be complete (again).
Possible sources for e.g. ixmp.testing missing:

ixmp might have had a testing module that got renamed
ixmp might have a testing module, but the docs don't have it
the ixmp version installed in the RTD process is a version that doesn't have access to testing

Regarding the first part of the warnings,
reading sources... [  2%] api
Cannot locate code for 'message_ix.models.DEFAULT_CPLEX_OPTIONS' or parent class/module
Cannot locate code for 'message_ix.models.MESSAGE_ITEMS' or parent class/module
Cannot locate code for 'message_ix.macro.MACRO_ITEMS' or parent class/module

they originate from api.rst:L92-L94, as indicated. The issue here is that the sphinx extension directive autosummary mainly supports modules, classes, and functions: things that usually include some source code.
Even with the latest version of sphinx, the objects are correctly identified, because some lines below, the .. autodata:: MESSAGE_DATA (and the rest) are rendered as intended. This is reassuring as the autodata directive is usually mentioned as the correct way to render dicts with sphinx. The only difference to the other things in the .. autosummary:: block in question, then, is that the other things (like MESSAGE and MACRO) are classes in message_ix.models.py.
.. autosummary:: provides a :nosignatures: option to indicate that certain entries should be rendered without without signatures (but still with docstrings). However, I couldn't resolve the warnings by specifying :nosignatures: in the middle of the .. autosummary: nor at the beginning of a new, second one.
There might be an option to use a custom template (e.g. the attribute one) and specify the objtype as data. However, I don't immediately know how to do that (probably involves copying the template file from the autosummary repo, adapating, renaming, and committing that to ours, and hoping that it resolves the warnings as intended) and while looking into this, I noticed that everything seems to be working as intended, despite these first warnings. So for now, I will not further try to resolve them.

Unfortunately, I don't think I have the time now to resolve all of these issues. I've created #759 with some commits containing fixes for the second group of warnings.
The other issues
The third and fourth group of errors/warnings originate from the interplay of message_ix with genno. Both complain about docstrings in genno/core/computer.py.
The third group of erros
One issue is with replacements: genno recently introduced several variables of the sort |Keylike| (e.g. here) that get replaced according to this specification in genno/doc/conf.py:
rst_prolog = """
.. role:: py(code)
   :language: python

.. |KeyLike| replace:: :obj:`~genno.core.key.KeyLike`
"""

Unfortunately, these don't seem to resolve correctly when mentioning :class:'~genno.Computer' (note: adapted to ') in message_ix, which happens in [macro.rst](https://github.com/glatterf42/message_ix/blob/e25f3dc474ff6815478c4d73d41874e09ff08c37/doc/macro.rst#L238) and [reporting.rst](https://github.com/glatterf42/message_ix/blob/e25f3dc474ff6815478c4d73d41874e09ff08c37/doc/reporting.rst#L32) ([twice](https://github.com/glatterf42/message_ix/blob/e25f3dc474ff6815478c4d73d41874e09ff08c37/doc/reporting.rst#L59-L60)). I don't know if there is a way to have message_ix recognize therst_prologof a linked documentation or if it should work out of the box. If this setting needs to be purposefully exposed to other projects, maybe this issue can only be resolved within genno. From the message-side, all references are in a text or table, where no additional information is needed, so there is no necessity to check all docstrings ofgenno.Computeror resolve them correctly as they link to the genno docs, where this problem doesn't exist. So from the message-side, it might suffice to replace the:class:` directive with something that only links to genno's docs.
The fourth group of warnings
The second issue is with references to documents within genno, so most likely the fix should also happen within genno. The references to the documents config and cache in genno/core/computer.py do not resolve successfully in message_ix. This is most likely due to the path being used for that being absolute, which works for the genno docs, but not for the message_ix docs.
I'm not sure about two things: I don't know if these references should resolve correctly. This looks again like a reference within docstrings of genno.Computer, which are not themselves part of the message_ix docs, so it might be safe to ignore them on our side or use just a linking directive rather than :class: as discussed above.
I'm also not sure why these warnings are emitted. First, this happens after all output has been written, apparently while generating indices. Second, the documents that can't be found are simply called 'config' and 'cache', so we try to access them as they are specified within the docstrings of genno.core.computer.py, which in genno get evaluated only with an additional .. currentmodule:: genno. If specifying a different directive doesn't work and they should resolve, maybe the paths in genno have to be adapted.


fix: Various issues from OCADU report

Summary | Résumé
Multiple fixes to issues identified in the OCADU report.
Changes

Typo fixes in documentation (side-nav other name and footer alt text)
Switch styles overview page to use gcds-card

Allows switching the coming soon cards heading to be an h2 to fix https://github.com/cds-snc/design-gc-conception/issues/685

Added role="lisitem" to cards on overview page to solve https://github.com/cds-snc/design-gc-conception/issues/683
Turn colour swatches on colour page to role="img" with colour description alt text to solve https://github.com/cds-snc/design-gc-conception/issues/692

Looks good to me, but I have a question about:

Turn colour swatches on colour page to role="img" with colour description alt text to solve https://github.com/cds-snc/design-gc-conception/issues/692
I understood that more to mean the images on this page https://design-system.alpha.canada.ca/en/styles/design-tokens/. Does this PR intend to close that ticket, or address a part of that ticket?

Looks good to me, but I have a question about:

Turn colour swatches on colour page to role="img" with colour description alt text to solve cds-snc/design-gc-conception#692
I understood that more to mean the images on this page https://design-system.alpha.canada.ca/en/styles/design-tokens/. Does this PR intend to close that ticket, or address a part of that ticket?

You're right it seems I have linked the wrong issue. Right now the issues in github/zenhub are very vague and don't have descriptions but there is an issue in the report that highlights that the colour is never mentioned only the name of the tokens, so this was to help with that. This issue might reflect the work? https://github.com/cds-snc/design-gc-conception/issues/682

Looks good to me, but I have a question about:

Turn colour swatches on colour page to role="img" with colour description alt text to solve cds-snc/design-gc-conception#692
I understood that more to mean the images on this page https://design-system.alpha.canada.ca/en/styles/design-tokens/. Does this PR intend to close that ticket, or address a part of that ticket?

You're right it seems I have linked the wrong issue. Right now the issues in github/zenhub are very vague and don't have descriptions but there is an issue in the report that highlights that the colour is never mentioned, only the names of the tokens are, so this was to help with that. This issue might reflect the work? cds-snc/design-gc-conception#682

Thanks, do you mind changing the PR summary to reflect #682 instead of #692? After that and Melanie's requests I think it should be good to go 👍


fix: fix broken LinkedEvents URLs in review and testing environments

Description
fix: fix broken LinkedEvents URLs in review and testing environments
left the commented out URLs for LinkedEvents dev/test environments in
the pipeline files if there's a need to test against those environments,
alternatively they could be removed completely for clarity

Unified search sources branch is deployed to platta: https://kuva-unified-search-sources-pr111.api.dev.hel.ninja :rocket::rocket::rocket:

Changed the commented out dev LinkedEvents URL to test LinkedEvents URL and changed the commit message to reflect the change.

Unified search sources branch is deployed to platta: https://kuva-unified-search-sources-pr111.api.dev.hel.ninja :rocket::rocket::rocket:


adding frozen-lockfile?

Feature Request
I think that we should install yarn dependencies with --frozen-lockfile:
https://circleci.com/docs/2.0/yarn/
https://stackoverflow.com/questions/52630404/how-to-install-packages-based-on-the-lock-file-with-yarn
https://yarnpkg.com/lang/en/docs/cli/install/
If you need reproducible dependencies, which is usually the case with the continuous integration systems, you should pass --frozen-lockfile flag.

Any objections?

Good idea. Releasing as a breaking change.


Fixed Return Home post button

@aaronosher please could you review this and decide if you want to merge this change, otherwise I will close this PR

👍


ReDriver2 PSP port?

this is only an question

no.
PS. : pls stop the bots

do you want to create psp port?


Add "type": "module" to package.json

Description
This enables dynamic imports in a node context.
Without the "type": "module" declaration, nodejs tries to import this package as a CommonJS module when using the dynamic import(), resulting in the error "Unexpected token 'export'".
Fixes #2303
Checks

[x] I have read and followed the Contributing Guidelines.

@hodgef Any chance this is going to be merged?

Thanks guys, will check this out later tonight. Need to make sure it won't cause regressions for people bundling with Webpack

Yeah as I suspected the build has failed. Maybe I can edit the bundling config (target) for the layouts instead of adding "type": "module". Will look into it tonight.
[webpack-cli] Failed to load '/home/runner/work/simple-keyboard-layouts/simple-keyboard-layouts/webpack.config.js' config
[webpack-cli] ReferenceError: require is not defined in ES module scope, you can use import instead
This file is being treated as an ES module because it has a '.js' file extension and '/home/runner/work/simple-keyboard-layouts/simple-keyboard-layouts/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.

Hi all, I've added the commonjs layouts in version 3.4.0
https://github.com/simple-keyboard/simple-keyboard-layouts/tree/master/build/commonjs/layouts
Regards,
Francisco Hodge


Decouple from bevy?

I think it might be useful to decouple this library from bevy so we can integrate with other rendering backends

I’d love to see more backends! By default Actuate is completely decoupled from any backends (Bevy requires the ecs feature)


Got an exception when running pnpm download in advisor-guide-fetcher.

I got the Error: Failed to fetch RIS when running the script. It happened when fetching 國立清華大學資訊工程學系. I tried to run it twice and got same error. Please figure out thx.

All right. it's works fine now.


[FEATURE] styling contact us section

Description
I would like to style the contact us section
Screenshots
No response
Additional information
No response

Can you show what you are thinking about the contact us section? @Vanshiii203

Can you show what you are thinking about the contact us section? @Vanshiii203
Hey @Rajdip019
I would like to  add the form in a vertical card having glass effect and would like add a background to that page.
I've Attached an image for your reference.

@Vanshiii203 There image u referenced doesn't go with the theme of our website. Anything else?

@Vanshiii203 There image u referenced doesn't go with the theme of our website. Anything else?

I have just referenced it for the card and glass effect. I'll add a light theme background as the website has a light theme

@Vanshiii203 But in our entire website Glassmorphism isn't used anywhere. So, it will be weird to just add it for the sake of Contact us page.

What do you think about this one?

@Vanshiii203 our's contact us layout is almost same.For now, The contact us layout is good. So, closing this issue


Generate Routes and pass them to Actix/Axum

This PR provides a function to walk the Leptos router's app tree and produce a list of routes. Each integration has conversions to parse them into a format for either Actix or Axum, and then a trait to provide a .leptos_routes() extension for their respective routers.
This lets us avoid any wildcard routes for routing leptos! And allows you to define routes in only one place! We can do some server side error handling, and be a better neighbor for other services.
I also put in the changes from #241 which are simplified by this change. Take a look and let me know if you spot any issues. The Actix version especially needs some prodding, it's got some fairly involved regexs, as its pathing is quite different from leptos_router.
The todo_app_sqlite and todo_app_sqlite_axum extensions have been updated to the new format. I'll update the rest if it looks good. @gbj and @akesson does that look right?

CI is failing on this at the moment
error[E0433]: failed to resolve: use of undeclared crate or module `tokio`
 --> integrations/actix/src/lib.rs:8:5
  |
8 | use tokio::sync::RwLock;
  |     ^^^^^ use of undeclared crate or module `tokio`

Some Actix feedback:

Really neat with the App::new().leptos_routes(.... Great DX.
Makes you dream about having an App::new().leptos_server_functions(... as well 😄
The app is now created twice: let routes = generate_route_list(|cx| view! { cx, <TodoApp/> }); and App::new().leptos_routes(leptos_options.to_owned(), routes.to_owned(), |cx| view! { cx, <TodoApp/> }) which is problematic for me because I pass in some rather heavy owned data at app creation i.e. view! { cx, <MyApp mydata /> }. Would it be possible to do it in one go? Probably not, but asking just in case...
ResponseOptions accessible from cx is really nice

Some Actix feedback:

Really neat with the App::new().leptos_routes(.... Great DX.
Makes you dream about having an App::new().leptos_server_functions(... as well 😄
The app is now created twice: let routes = generate_route_list(|cx| view! { cx, <TodoApp/> }); and App::new().leptos_routes(leptos_options.to_owned(), routes.to_owned(), |cx| view! { cx, <TodoApp/> }) which is problematic for me because I pass in some rather heavy owned data at app creation i.e. view! { cx, <MyApp mydata /> }. Would it be possible to do it in one go? Probably not, but asking just in case...
ResponseOptions accessible from cx is really nice

Glad you like it! I was thinking about server functions, I think routes could be extracted from the register() function. Although I'm not super concerned, as it only requires giving up /app as a route.
Double rendering the app is a bit of a drawback. I could store the results of the render and pass that to all the functions, but I think that's probably unnecessary because we only pay the cost on startup once and rendering is fast.
Sounds like I'm good to go on updating the other examples and docs, I'll get that up soon.
Not sure why CI is failing, leptos_actix is defined in the Cargo.toml for that example, and it compiles fine locally

It's failing on todo_app_sqlite when features = []. Should cargo-all-features try to build features = [] in our case? Probably not, but I haven't figured out how to stop it.
I'd guess leptos_actix is optional = true and gated on the ssr feature, but is imported somewhere that isn't gated.
Actually checks Okay yeah move line 4 in main.rs down into the section that's behind the cfg_if gate for ssr.

Yeah, caught that after I said it. I've updated all the examples. So far so good, I think it's just about ready to merge


Splitting context and question for BERT

The paper suggests that the softmax for start and end logits is computed only over the context hidden states. However, in the code, I could not figure out any place where the hidden states were being split into query and context hidden states. Does that mean that in the code, we are calculating the softmax over the query and context hiddens, and expect the model to learn that the answer lies in context hiddens? Or can you point me to a place, where you are splitting the hidden states and then using the final linear layer only over the context.

You can refer to the function 'write_predictions' in 'run_squad.py'.
Paying attention to the line #L787, it said "We could hypothetically create invalid predictions, e.g., predict that the start of the span is in the question. We throw out all invalid predictions." So the author firstly get n best indexes for start and end, and then just throw out the invalid index in the question. So there is no split operation.


[TrafficControl] Handle forwarded header with or without port

Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

Wrapped into https://github.com/MystenLabs/sui/pull/18699


Wireguard in Kernel 5.4 for Alpha

Current situation
Kernel 5.4 in Alpha does not include Wireguard kernel module, as it was first included in the mainline kernel since 5.6.
So we should create a third-party patch for Kernel 5.4, from wireguard-linux-compat repo.
Also we should add a wireguard command-line tool.
See also what we have done for Edge in the past.

https://github.com/flatcar-linux/coreos-overlay/pull/32
https://github.com/flatcar-linux/coreos-overlay/pull/35

https://github.com/flatcar-linux/coreos-overlay/pull/345 was merged.

It is available since Flatcar Alpha 2513.0.0.
Thanks!


Save and fill website passwords

This is a big ticket: storing, crypto, password field detection, form fill, etc. etc.

Why not delegate all of this to addons like 1password or lastpass?

See https://github.com/mozilla/tofino/issues/1218


Fix the style issue in procfs

Summary

procfs: Add g_ prefix to all procfs_operations
procfs: remove procfs_ from procfs_operations variables
procfs: Make g_procfs_entries in the alphabetic order

Impact
No, code refactor only
Testing
CI

@xiaoxiang781216 Please fix the Code space overflow found by CI.


docker-compose.yml as argument

Register a project, ie a folder with a docker-compose.yml file.
Some services can be a cronjob : it has two labels prefix.cronjob.schedule and prefix.cronjob.command
CPU / RAM use docker settings, MaxExectionTime is set with a label, prefix.cronjob.max_execution_time
POST /api/schedule with a JSON body, with a compose key.

Now that we have a basic docker-compose support, it's time to add specific labels support.

See #8 and #9


remove usage of CHAR5 ( WIP #692 )

@sandraros perhaps not, I saw the aptly named tab in Eclipse and went along with it. I like your suggestion, I'll change this.
To be extra sure, when it comes to where-used, I first cross-check GUI (which supports search areas as $Z*) and Eclipse (which apparently only takes a full package name) and then also run a recursive grep (I keep a local clone because upstream merging using git cmdline is a piece of cake).


Batuhan/TLI-01a-Tab-Order

Implemented tab order which is logical and accessible.

Merges are not present on the main branch. Maybe some later merge overwrote it?


longhorn volume recovery issue?

Describe the bug
I'm doing some simple testing with 1.0.  I have designated 3 worker nodes as replicas, remaining worker nodes for normal workloads.  After creating a volume, and installing an application using this volume, did some disaster type test.

I stopped docker on the 1st replica worker, app still had access to volume as expected (degraded)
I stopped docker on 2nd replica worker, app has access to volume still (degraded)
Finally stop docker on 3rd replica worker, app looses access to volume as expected.

Waited for the pvc in longhorn UI to show all nodes are failed.  Then start docker backup on
one of the replicas.
The PV though still says all replica's are stopped when the node goes from failed to normal 'schedulable' state.
Expected behavior
Is  it expected that Longhorn should be able to autorecover for this?
What is the normal recovery option if not?
Environment:

Longhorn version: 1.0.0
Kubernetes version: 1.17
Node OS type and version: centos 7.7

Additional context
Add any other context about the problem here.

I started docker back on the other 2 nodes, and the volume started to recover.
Since I was staggering the docker stop's on these nodes, the primary replica owner changed.  It seems that only one of these 3 nodes was considered to be a true owner of the replica.
I'm a bit concerned on what to do if all 3 replica nodes crash at same time, or lets say only 2 of the 3 come back and the one which is down was considered to be the last known replica (even though the other 2 may have near full state of the volume).
I'm still getting an understanding of failure modes here and what to expect so any insight appreciated.

Where is the volume attached to? Once you get the docker on the attached node up, Longhorn should automatically start rebuilding (if it's allowed). Longhorn treats all replicas equally. The workload doesn't need to be in the same node that has a replica. But the workload needs to be up for Longhorn volume to be attached, then start the rebuild process.
Also, the failed replica will be automatically removed after staleReplicaTimeout.

hi Sheng.  So in my case, the replicas were on nodes 1,2,3 , my pod which was mounting the pv was on node4.  only node1,2,3 are allowed to have replicas in my test.  Docker was never restarted on node4, only on node1,2,3.

When all 3 nodes are back up, all 3 replicas are on one of the 3 longhorn nodes.

If I understood correctly you are saying all 3 replicas ended up on node x?
Could you share what your replica-node-level-soft-anti-affinity setting is set to?

@mshack70 When all the replica are down, Longhorn will try to auto salvage and re-attach the volume. See https://longhorn.io/docs/1.0.0/high-availability/recover-volume/ . After you bring back the docker on the first node, did you see the volume start to reattach in the Longhorn UI? It might take a moment but if the auto-salvage option is enabled, that should happen.

Yes when all 3 replica nodes were back up, only one of the 3 nodes had all 3 replicas.
replica-node-level-soft-anti-affinity was enabled
When bringing up docker on the 1st replica node, I waited over a minute and the volume did not attach or recover..., not until the the other 2 nodes docker start did the volume recover, and all replicas were on node2.

What happened is, Longhorn assumes the last replica you've shut down contains the latest data of the volume, so unless the last replica is somehow able to be started (e.g. enable docker on the node), the volume won't be recovered since we cannot expect the user to write some data into the volume but lost the data when volume comes back (since other two replicas might not contain stale data).
Also, on v1.0.0, we've disabled node level anti-affinity by default, so the replicas wouldn't end up on the same node.

What would happen if all the replica nodes lost network connectivity at same time, and then recovered later?

if all the replica lost the network at the same time, auto salvage will bring them back and trying to attach the volume to the last known node.
For the best practice, node level soft anti-affinity should be disabled. It's the default value in v1.0.0.


Unable to import after updating from 2.0.13 to 2.2.1

I'm currently using the nuxt-speedkit package in my project and I've encountered some difficulties after recent updates. I have been trying to import specific components and files directly from the package like so:
import SpeedkitImage from 'nuxt-speedkit/components/SpeedkitImage';
import SpeedkitPicture from 'nuxt-speedkit/components/SpeedkitPicture';
import speedkitHydrate from 'nuxt-speedkit/hydrate';

Now I'm having this issue for all these imports:
Unable to resolve path to module 'nuxt-speedkit/hydrate'.eslint[import/no-unresolved](https://github.com/import-js/eslint-plugin-import/blob/v2.27.5/docs/rules/no-unresolved.md)
I've checked the new structure of the nuxt-speedkit package and it seems to have changed significantly, which may be causing the issue. I have tried adjusting the import paths to match the new structure, but I'm still encountering the same problem.
I'm using nuxt 2.15.8.
Could you please provide some guidance on how to import these specific components and files with the new package structure? Are direct file imports supported with the current version of nuxt-speedkit?

This is an internal alias in nuxt.
And should work without any customization.

It's interesting that I had to manually update my ESLint configuration, but now it's finally working correctly.
Nuxt recognizes your path, but ESLint does not. To resolve the path resolution issue, I added the following code to my ESLint configuration:
settings: {
  'import/resolver': {
    alias: {
      map: [
        ['#speedkit', './node_modules/nuxt-speedkit/src/runtime'],
      ],
      extensions: ['.js', '.mjs']
    }
  }
}

And now everything works as intended!

It's interesting that I had to manually update my ESLint configuration, but now it's finally working correctly.
Nuxt recognizes your path, but ESLint does not. To resolve the path resolution issue, I added the following code to my ESLint configuration:
settings: {
  'import/resolver': {
    alias: {
      map: [
        ['#speedkit', './node_modules/nuxt-speedkit/src/runtime'],
      ],
      extensions: ['.js', '.mjs']
    }
  }
}

And now everything works as intended!


JS for files that store only objects

I'd suggest changing these to JSON files, and if you need features like comments use json5. You can even require() JSON files and get just an object with its contents. The major problem with using JS for data-storage is that it's not secure and 100% vulnerable to code injection.

The config file is already JSON and read using JSON.parse.
The devices.js file is part of the code and if you can modify that you could also modify any other part that would allow you to change the code. So there is no code injection vulnerability that would be prevented by changing that file to JSON.


How to get GMC files for other MOT type datasets?

You will need to change and run VideoCameraCorrection/main.cpp.
Its c++ code that use opencv-contrib GMC module.


[v5] Fantomas Updates

Proposed Changes

Update fantomas to the latest version

Add Main.fs files from tests to .fantomasignore. The below code is causing errors with fantomas and thus not being caught. This also prevented us from catching code that needed formatting.
#if !FABLE_COMPILER
open Expecto

[<Tests>] //needed for `dotnet test` to work
#endif
let allTests = testList "All Tests" [ AsyncSeq.allTests ]

build.fs has been updated to fail on uncaught code formatting errors within the else block.

Types of changes
What types of changes does your code introduce to FsToolkit.ErrorHandling?
Put an x in the boxes that apply and remove ones that don't apply

[X] Bugfix (non-breaking change which fixes an issue)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[X] Build and tests pass locally

Further Comments
I made it so that the checkFormatCode step fails if we encounter severe errors within Fantomas, however, I can also see why we may not want to fail here as well. I'm open to reverting/updating the build.fs as needed.

After discussion on the issue thread above, I will make some quick updates later, so the code is not choking up fantomas


stats: add new API to get a Stats::Store from a ServerFactoryContext

Currently the mechanism to add a stats sink predicate is available to applications that create their own main() rather than using source/exe/main.cc, as they will be able to call MainCommon::server().stats().setSinkPredicate.
However, extension-writers don't get any clear method of getting at a Stats::Store  -- they get a ServerFactoryContext.
A possible workaround exists: server_factory_context.getTransportSocketFactoryContext().stats().setSinkPredicates(....) but that is really non-obvious and might even not be the right Stats::Store.
@ravenblackx @pradeepcrao FYI

I had protoyped a solution for this that involves specifying the predicates in the bootstrap as part of the stats config. I can create a PR for further feedback.

I was surprised that sink predicates weren't a config thing, so I'd be very happy for it to be that rather than code as I was thinking of doing. :)

Yeah this is a good time to open your PR to allow configuration of sink-predicates. I'm interested to see what that config will look like if soemone wants to (say) include a few hundred stats that don't have a convenient simple regex that covers them exactly.

Aah, my solution would not solve this. This would still require someone to define the sink predicates in an extension.
What my PR would enable is being able to instantiate such an object using the bootstrap. The PR will also define sink predicates based on the StatsMatcher, that Envoy users can instantiate, without having to write their own predicates in an extension.

For additional context, the conceptual use of this was to allow a sink extension to prevent the StatNames it consumes from being invalidated during its own lifetime. It turned out there were a stack of other problems provoked by this (e.g. the shutdown order of events involves an ASSERT that verifies that StatNames have been destroyed, which occurs before the destruction of sink extensions, so if the StatNames were preserved then shutdown crashes).
My eventual workaround was to key a map on pointers to the Metrics combined with int64 hashes of StatNames, so if they become invalid it just leaves dangling keys in the map (which is better than the use-after-free undefined behavior you get if you use StatNames that got deleted or moved, or the assert-crash-on-shutdown that you get if you try to keep the Metrics or StatNames from being deleted when they normally would be).
Given the complications that are provoked if an extension uses the Stats::Store directly, I think maybe it's not actually a good idea to make using it easier. Certainly it's no longer something I would want to use. :)


Remove bbcode_text from RichTextLabel

This simplyfies the text setting and resolves some bugs as the internal data structure is the same.
It's a draft, since the points below must be discussed first (at least 1 to 3)
Things to discuss:

Make add_text, set_text, get_text private (hide them in their current form)?
Rename set_bbcode, get_bbcode and append_bbcode to set_text, get_text and add/append_text?
Rename bbcode_enabled?
How to parse old scene files (since we should put the bbcode_text into the text, when bbcode_enabled is true)?

fixes #36711
fixes #35553 and therefore supersedes #36037 if merged
fixes partly #18413
#35368 seems related acording to the title, but issue itself is unclear
We could alternativly make the RichTextLabel a base class for multiple parsers and reimplement a BBCodeLabel or go in the direction of https://github.com/godotengine/godot-proposals/issues/826

Current get_text() is actually useful, because it returns the actual text, without bbcodes. This possibility should be preserved somehow.

I thought about having get_parsed_text, or rename the the bbcode text to something like get_raw_text

Merged set_text
Renamed

append_bbcode -> append_text
get_bbcode -> get_raw_text
set_bbcode -> set_text

text property is now set_text and get_raw_text. Maybe a change to get_text and rename of get_text to get_parsed_text is desired for consistency.

rebased and tested.
I don't like having made the text property to set_textand get_raw_text, but I don't know how to phrase get_text_but_without_bbcode. Any ideas?

The _validate_property() can be removed.

done.

As for the naming, getter for text should be called get_text(). I feel like the get_text() and get_raw_text() would be fine swapped 🤔 Other names for no-BBCode could be get_clean_text(), get_final_text(), get_unformatted_text() or get_parsed_text().

I renamed get_raw_text() to get_parsed_text(). However, get_text() returns the raw text, if bbcode_enabled is true and the parsed text if not. Is that desired? It looks like a hack for the text <--> bbcode_text ambigity. I deleted that.

Also the internal variable bbcode could be renamed to text, because it introduces some confusion.

done.

Is this the final resolution about this that everyone agrees to? I remember too many discussions on this topic at this point.

Ok I got confirmation that this is the case, so feel free to rebase and merge.

will do

Rebased. One thing to remember: This will erase all text from RTLs as they are not saved in the text property. Can we add a property upgrade hint somehow?

Rebased. One thing to remember: This will erase all text from RTLs as they are not saved in the text property. Can we add a property upgrade hint somehow?

Yes, see e.g. this:
https://github.com/godotengine/godot/blob/104a6191fd32ca7bd28b28df6de091652c3d92cd/scene/resources/environment.cpp#L1032-L1049

Rebased. One thing to remember: This will erase all text from RTLs as they are not saved in the text property. Can we add a property upgrade hint somehow?

Yes, see e.g. this:
https://github.com/godotengine/godot/blob/104a6191fd32ca7bd28b28df6de091652c3d92cd/scene/resources/environment.cpp#L1032-L1049

Thank you. Done and rebased

Thanks!


boxen not applying $BOXEN_HOME/facts.d facts

I tried adding fact files within $BOXEN_HOME/facts.d directory, and it's not automatically picking them up.  If I manually run the '$BOXEN_HOME/bin/facter --external-dir $BOXEN_HOME/facts.d' it picks up all the fact files properly.
I noticed the following BOXEN ruby script is supposed to override the /etc/facter/facts.d dir, with the $BOXEN_HOME/facts.d.  Are others able to successfully add fact files to $BOXEN_HOME/facts.d?
Thanks,
--Jason Dettbarn

Yeah. Which version of puppet-boxen are you using? This feature only works with 3.8.0+

I'm running 3.10.1
Kind Regards,
--Jason Dettbarn
M:<PHONE_NUMBER>
F:<PHONE_NUMBER>
On 3/30/15 4:37 PM, Rafael Mendonça França wrote:

Yeah. Which version of puppet-boxen are you using? This feature only
works with 3.8.0+
—
Reply to this email directly or view it on GitHub
https://github.com/boxen/boxen/issues/179#issuecomment-87824982.

Actually $BOXEN_HOME/facts.d is not loadable, just $BOXEN_REPO_DIR/facts.d/. See https://github.com/boxen/puppet-boxen#facts


Journal Template Not Applied

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[ ] Views.  Dendron Preview, Tree View, Side Panels in the UI
[x] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[ ] Markdown.  Markdown features, such as syntax support and features

Describe the bug
As of yesterday's patch, my journal template is no longer being applied through my schema.
To Reproduce
I have a journal schema (daily.schema.yml) file like so:
version: 1
imports: []
schemas:
- id: daily
  title: daily
  parent: root
  children:
    - journal
- id: journal
  title: journal
  parent: root
  children:
    - year
- id: year
  title: year
  pattern: "[0-9][0-9][0-9][0-9]"
  children:
    - month
- id: month
  title: month
  parent: year
  pattern: "[0-9][0-9]"
  children:
    - day
- id: day
  title: day
  parent: month
  pattern: "[0-9][0-9]"
  namespace: true
  template:
    id: templates.daily.journal
    type: note

And a journal template (templates.daily.journal.md):
---
id: zDVh8WCuvQXHp9p0wcxsb
title: Daily Journal Template
desc: ''
updated:<PHONE_NUMBER>226
created:<PHONE_NUMBER>001
stub: false
---

## Meetings

- [ ] xxxxxx
- [ ] ... @ hh:mm

## Tasks

- [ ] ...
- [ ] ...

## Notes

- ...

Steps to reproduce the behavior:

Open up the command palette and select "Dendron: Create Daily Journal Notes"
Observe the journal file being created not containing the template.

Expected behavior
Up until yesterday (2022-02-07), the template would populate fine, but since the latest update, this no longer works.
Screenshots
none.
Desktop (please complete the following information)

OS: MacOS Monterey 12.02 (on an M1 MacBook Pro, if that matters)
Browser: Google Chrome
Version: 97.0.4692.99
VSCode: Version 1.64.0

Additional context
None
Dendron Log file
{"level":30,"time":1644343182641,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":[]}
{"level":30,"time":1644343182641,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"undefined"}
{"level":30,"time":1644343182642,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":["/Users/eddy/code/notes/vault/daily.schema.yml"]}
{"level":30,"time":1644343182644,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"/Users/eddy/code/notes/vault/daily.schema.yml"}
{"level":30,"time":1644343184896,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"dendron.createDailyJournalNote:run","msg":"pre-execute"}
{"level":30,"time":1644343184896,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"CreateNoteWithTraitCommand","msg":"enter","opts":{"title":"daily.journal.2022.02.08","fname":"daily.journal.2022.02.08"}}
{"level":30,"time":1644343184903,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"getVaultForOpenEditor","activeDocument":"/Users/eddy/code/notes/vault/daily.schema.yml"}
{"level":30,"time":1644343184903,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"getVaultForOpenEditor","msg":"exit","vault":{"fsPath":"vault"}}
{"level":30,"time":1644343184903,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"daily.journal.2022.02.08","vault":{"fsPath":"vault"},"overrides":{"title":"2022-02-08","traits":[{"id":"journalNote","OnWillCreate":{},"OnCreate":{}}]}},"msg":"enter"}
{"level":30,"time":1644343184914,"pid":24534,"hostname":"Eddys-MacBook-Pro.local","name":"LinkUtils.getLinks","ctx":"getLinks","dlinksLength":0,"noteRefsLength":0,"wikiLinksLength":0}
{"level":30,"time":1644343184921,"pid":24534,"hostname":"Eddys-MacBook-Pro.local","name":"LinkUtils.getLinks","ctx":"getLinks","dlinksLength":0,"noteRefsLength":0,"wikiLinksLength":0}
{"level":30,"time":1644343184931,"pid":24534,"hostname":"Eddys-MacBook-Pro.local","name":"LinkUtils.getLinks","ctx":"getLinks","dlinksLength":0,"noteRefsLength":0,"wikiLinksLength":0}
{"level":30,"time":1644343184940,"pid":24534,"hostname":"Eddys-MacBook-Pro.local","name":"LinkUtils.getLinks","ctx":"getLinks","dlinksLength":0,"noteRefsLength":0,"wikiLinksLength":0}
{"level":30,"time":1644343184969,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":[]}
{"level":30,"time":1644343184969,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"undefined"}
{"level":30,"time":1644343184974,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":["/Users/eddy/code/notes/vault/daily.journal.2022.02.08.md"]}
{"level":30,"time":1644343184975,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"/Users/eddy/code/notes/vault/daily.journal.2022.02.08.md"}
{"level":30,"time":1644343184982,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WorkspaceWatcher:onFirstOpen","msg":"enter","fname":"daily.journal.2022.02.08"}
{"level":30,"time":1644343184983,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WorkspaceWatcher:onFirstOpen","msg":"exit","fname":"daily.journal.2022.02.08"}
{"level":30,"time":1644343184985,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"daily.journal.2022.02.08","vault":{"fsPath":"vault"},"overrides":{"title":"2022-02-08","traits":[{"id":"journalNote","OnWillCreate":{},"OnCreate":{}}]}},"msg":"exit"}
{"level":30,"time":1644343184985,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"CreateNoteWithTraitCommand","msg":"exit"}
{"level":30,"time":1644343184985,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"dendron.createDailyJournalNote:run","msg":"post-execute"}
{"level":30,"time":1644343184992,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"FileWatcher:onDidCreate","fsPath":"/Users/eddy/code/notes/vault/daily.journal.2022.02.08.md"}
{"level":30,"time":1644343185033,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"updateDecorations","payload":{"error":null,"decorationsLength":2,"diagnosticsLength":0}}
{"level":30,"time":1644343185094,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"refreshTree"}
{"level":30,"time":1644343188274,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":[]}
{"level":30,"time":1644343188274,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","editor":"undefined"}
{"level":30,"time":1644343188274,"pid":24525,"hostname":"Eddys-MacBook-Pro.local","name":"dendron","ctx":"WindowWatcher:onDidChangeVisibleTextEditors","editorPaths":["/Users/eddy/Library/Application Support/Code/logs/20220208T114531/exthost4/dendron.dendron/dendron.log"]}

Hey @eddy-murj , Thanks for reporting the bug. Looks like the attached schema is problematic. You would want to update the parent of journal to daily instead of root
version: 1
imports: []
schemas:
- id: daily
  title: daily
  parent: root
  children:
    - journal
- id: journal
  title: journal
  parent: root ----> daily
  children:
    - year

@Harshita-mindfire well, that was silly. That fixed it 😅  Sorry to litter your backlog with what turned out to be aa troubleshooting issue.
Thanks so much for the quick help!


fix(TableCard): encode variables for linkTemplate

Closes #1853
Summary

Theres little control over row-specific variables as they're added in the renderDataFunction and can only use the current rows formatting. For example, if a timestamp is already being formatted in another column, the variable will also be formatted, which could cause problems in the URL. For example 7/20/2020 02:00 is not valid in URLs, but it still needs to be formatted in the other column
This PR solves this issue by first encoding the variable, then passing it to the URL

Acceptance Test (how to verify the PR)

Go to /?path=/story/watson-iot-tablecard--with-row-specific-link-variables and see that the Link values are being formatted with URL encoding

:tada: This PR is included in version 2.141.0-next.38 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.141.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


autolinks ending with * are not parsed correctly

What happened:
The link in **Go ahead and help us spread the word: https://gardener.cloud** is parsed as https://gardener.cloud**
What you expected to happen:
The link should be parsed as https://gardener.cloud
/priority normal

seems like this issue is resolved.


Update an IconButton sample, add RaisedButton sample

Corrects the first IconButton sample, adds a RaisedButton sample.
Fixes https://github.com/flutter/flutter/issues/27168
Fixes https://github.com/flutter/flutter/issues/12382

@HansMuller updated the code :)

It turns out that the snippet does in fact need a build method. I'll fix that up and land this when the build has stabilized.
Once this PR has been landed in the repo it will start running the final testing gauntlet. You can watch its status here: https://flutter-dashboard.appspot.com/build.html

I was wrong, a build method isn't needed. Yes this is confusing (to me).


Bug: Overflow issue

Description
The header and text are not well formatted.
Screenshots

What browsers are you seeing the problem on?
Microsoft Edge
Ready to Work?

[ ] I want to work on this issue

hey @oyepriyansh I want to work on this overflow issue please assign it to me.

hey @oyepriyansh I want to work on this overflow issue please assign it to me.

assigned to you @SAGARSINGH-1.


updated Duration.milliseconds() to return an integer, and added floating point math

I updated duration.milliseconds() to truncate partial milliseconds and return an integer to fix issue https://github.com/moment/moment/issues/4649 while allowing duration.asMilliseconds() to still return a non-integer number.
As I was adding test cases for it, I noticed that some of the calculations were incorrect due to javascript floating point math problems. See: https://github.com/moment/moment/issues/2978 and https://github.com/moment/moment/issues/1867
I added a function (fpMath) to correctly perform floating point calculations, and added test cases around that to make sure everything is behaving as expected. I did not have to modify any existing test cases, so this should not negatively affect any existing functionality.
I only modified files in /src/ and all the tests are passing, but I wasn't sure if I need to also make the changes to /moment.js also or if that file gets built from src somehow.

You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

I signed the CLA, but it says my e-mail address is not linked to my github account. I checked my profile, and it's there...


Add IntermediateCertFile to ServiceServingCertSignerConfig

Required by https://github.com/openshift/service-ca-operator/pull/73
cc: @sttts @deads2k

/hold
I may be wrong but I don't think this is necessary - https://github.com/openshift/service-ca-operator/pull/73#pullrequestreview-303779910

/hold
I may be wrong but this may not be necessary - openshift/service-ca-operator#73 (comment)

As per my reply, I think this is necessary.

/hold
I may be wrong but this may not be necessary - openshift/service-ca-operator#73 (comment)

Though I think the change is necessary, thank you for holding. I did not intend this PR to be reviewed until the openshift/service-ca-operator#73 is otherwise ready to be merged.

Rebased

/hold cancel
/lgtm

/approve


Create grc path

@grcpath thanks for this pull request, but please note that the pull request is empty.
The image in the comment above doesn’t seem to be an original vector but be traced from a jpg/png, can you provide an original vector such as .ai or .svg?

Dear PaulThanks alot for your replyI have attached the SVG file. I will try to add it again and pull request. Best, AliSent from my Galaxy
-------- Original message --------From: Paul van Brouwershaven @.> Date: 2/9/24  10:49 PM  (GMT+03:00) To: "pkic/pkic.org" @.> Cc: grcpath @.>, Mention @.> Subject: Re: [pkic/pkic.org] Create grc path (PR #111)
@grcpath thanks for this pull request, but please note that the pull request is empty.
The image in the comment above doesn’t seem to be an original vector but be traced from a jpg/png, can you provide an original vector such as .ai or .svg?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hi
I had upload ne svg file

Closing, no update from GRC Path to provide a SVG logo.


Run-TestsInBCContainer throws error "Cannot open page 130455"

Issue description
With Run-TestsInBCContainer I want to run all tests in the DEFAULT test suite. When executing the scripts it throws the following error:
Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder C:\ProgramData\NavContainerHelpe
r\Extensions\BC163NPupW1\PsTestTool-6 and retry. You might also have URL or Company name wrong.
at Run-Tests, C:\ProgramData\NavContainerHelper\Extensions\BC163NPupW1\PsTestTool-6\PsTestFunctions.ps1: line 316
at <ScriptBlock>, <No file>: line 57
Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder C:\ProgramData\NavContainerHelp
er\Extensions\BC163NPupW1\PsTestTool-6 and retry. You might also have URL or Company name wrong.
At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\AppHandling\Run-TestsInNavContainer.ps1:415 char:17
+                 throw $_.Exception.Message
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Cannot open pag...any name wrong.:String) [], RuntimeException
    + FullyQualifiedErrorId : Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder
   C:\ProgramData\NavContainerHelper\Extensions\BC163NPupW1\PsTestTool-6 and retry. You might also have URL or Company name wrong.

Page 130455, however does reside in the database. So, questions is what causes this error?
I have been searching through the various existing issues here that relate to "Cannot open page 130455", but I was not able to determine a solution in them.
As a workaround I have run all the tests in DEFAULT suite from the AL Test Tool "manually" without any (technical) problem.
The database is a restored backup of a client with their solution, development license and all test apps installed in it.
Scripts used to run the tests
# container name
$containerName = 'BC163NPupW1-2'
$xunitResultsFile = "c:\programdata\navcontainerhelper\results.xml"

# set credentials for using with NavUserPassword
$login = '.....'
$password = '....'
$securepassword = (ConvertTo-SecureString -String $password -AsPlainText -Force)
$credential = New-Object System.Management.Automation.PSCredential($login, $securepassword)

Run-TestsInBCContainer `
    -containerName $containerName `
    -credential $credential `
    -testSuite 'DEFAULT' `
    -detailed `
    -XUnitResultFileName $xunitResultsFile `
    -debugMode

Debugmode output (including error)
Run-Tests, open page 130455
Title: Dialog
Title: 8da61efd-0002-0003-0507-0b0d1113171d
[
    {
        "type":  "ClientGroupControl",
        "mappingHint":  "GROUP",
        "name":  "contentGroupControl",
        "children":  [
                         {
                             "type":  "ClientGroupControl",
                             "mappingHint":  "LAYOUTGROUP",
                             "name":  "",
                             "children":  [
                                              {
                                                  "identifier":  "",
                                                  "name":  "Info",
                                                  "type":  "ClientImageControl"
                                              },
                                              {
                                                  "type":  "ClientStaticStringControl",
                                                  "name":  "",
                                                  "value":  "The current environment is not set as production.\r\nSome external integrations
are handled differently in this mode. You can change this in page \"NP Retail Setup\"",
                                                  "identifier":  ""
                                              }
                                          ],
                             "caption":  "",
                             "identifier":  "{B178ABC5-D511-462e-B8D1-D08C35BC1113}"
                         }
                     ],
        "caption":  "",
        "identifier":  "{2DD9E973-CD11-40a0-B5CF-6414BD1D3550}"
    },
    {
        "type":  "ClientGroupControl",
        "mappingHint":  "ACTIONBAR",
        "name":  "",
        "children":  [
                         {
                             "caption":  "OK",
                             "type":  "ClientActionControl",
                             "name":  "{B594146A-9CEF-4767-AE76-E9721CD6FB50}",
                             "identifier":  "{B594146A-9CEF-4767-AE76-E9721CD6FB50}"
                         }
                     ],
        "caption":  "",
        "identifier":  "{6B823A4C-719E-4833-975A-1BEFDCBDF389}"
    }
]
Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder C:\ProgramData\NavContainerHelpe
r\Extensions\BC163NPupW1-2\PsTestTool-6 and retry. You might also have URL or Company name wrong.
at Run-Tests, C:\ProgramData\NavContainerHelper\Extensions\BC163NPupW1-2\PsTestTool-6\PsTestFunctions.ps1: line 316
at <ScriptBlock>, <No file>: line 57
at Run-Tests, C:\ProgramData\NavContainerHelper\Extensions\BC163NPupW1-2\PsTestTool-6\PsTestFunctions.ps1: line 316
at <ScriptBlock>, <No file>: line 57
Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder C:\ProgramData\NavContainerHelp
er\Extensions\BC163NPupW1-2\PsTestTool-6 and retry. You might also have URL or Company name wrong.
At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\AppHandling\Run-TestsInNavContainer.ps1:415 char:17
+                 throw $_.Exception.Message
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Cannot open pag...any name wrong.:String) [], RuntimeException
    + FullyQualifiedErrorId : Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder
   C:\ProgramData\NavContainerHelper\Extensions\BC163NPupW1-2\PsTestTool-6 and retry. You might also have URL or Company name wrong.

Scripts used to create container
# set accept_eula to $true to accept the eula found here: https://go.microsoft.comfwlink/?linkid=861843
$accept_eula = $true
$accept_outdated = $true

# container name and version
$containerName = 'BC163NPupW1-2'
$artifactUrl = Get-BCArtifactUrl -type OnPrem -country "w1" -version "16.3"

# set credentials for using with NavUserPassword
$login = '.....'
$password = '.....'
$securepassword = (ConvertTo-SecureString -String $password -AsPlainText -Force)
$credential = New-Object System.Management.Automation.PSCredential($login, $securepassword)

$navContainerHelperConfig.genericImageName = 'mcr.microsoft.com/dynamicsnav:{0}-generic-dev'

$bakfile = 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Backup\MyDatabase.bak'

New-BCContainer -accept_eula:$accept_eula `
                -accept_outdated:$accept_outdated `
                -containerName $containerName `
                -artifactUrl $artifactUrl `
                -auth UserPassword `
                -credential $credential `
                -memoryLimit:10GB `
                -updateHost `
                -shortcuts StartMenu `
                -bakFile $bakfile `
                -dumpEventLog

Output of New-BCContainer
NavContainerHelper is version <IP_ADDRESS>
NavContainerHelper is running as administrator
Host is Microsoft Windows 10 Pro - 2004
Docker Client Version is 18.09.1
Docker Server Version is 18.09.1
Fetching all docker images
Using image mcr.microsoft.com/dynamicsnav:10.0.19041.508-generic-dev
Creating Container BC163NPupW1-2
Version: 16.3.14085.14238-w1
Style: onprem
Platform: 16.0.14073.14195
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.19041.508 (2004)
Host OS Version: 10.0.19041.508 (2004)
Using locale en-US
Using process isolation
Files in C:\ProgramData\NavContainerHelper\Extensions\BC163NPupW1-2\my:
- AdditionalOutput.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container BC163NPupW1-2 from image mcr.microsoft.com/dynamicsnav:10.0.19041.508-generic-dev
ffde34993d4f00424d91f1f1fbc09a415df4c59ecb78b7eb517f8a65c6ceb0b7
Waiting for container BC163NPupW1-2 to be ready
Using artifactUrl https://bcartifacts.azureedge.net/onprem/16.3.14085.14238/w1
Using installer from C:\Run\150-new
Installing Business Central
Installing from artifacts
Starting Local SQL Server
Starting Internet Information Server
Copying Service Tier Files
Copying PowerShell Scripts
Copying dependencies
Copying ReportBuilder
Importing PowerShell Modules
Skipping restore of Cronus database
Modifying Business Central Service Tier Config File for Docker
Creating Business Central Service Tier
Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
Copying Web Client Files
Copying Client Files
Copying ModernDev Files
Copying additional files
Copying ConfigurationPackages
Copying Test Assemblies
Copying Applications
Installation took 18 seconds
Installation complete
Initializing...
Setting host.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
Starting Container
Hostname is BC163NPupW1-2
PublicDnsName is BC163NPupW1-2
Using NavUserPassword Authentication
Using Database .bak file 'C:\ProgramData\NavContainerHelper\Extensions\BC163NPupW1-2\database.bak'
Using database server localhost\SQLEXPRESS
Creating Self Signed Certificate
Self Signed Certificate Thumbprint 6B66A0DA63DB55E192509C07ADB2BBEB72B2BCAD
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Registering event sources
Creating DotNetCore Web Server Instance
Creating http download site
Setting SA Password and enabling SA
Creating NP424246 as SQL User and add to sysadmin
Container IP Address: <IP_ADDRESS>
Container Hostname  : BC163NPupW1-2
Container Dns Name  : BC163NPupW1-2
Web Client          : http://BC163NPupW1-2/BC/
Dev. Server         : http://BC163NPupW1-2
Dev. ServerInstance : BC
Setting BC163NPupW1-2 to <IP_ADDRESS> in host hosts file

Files:
http://BC163NPupW1-2:8080/ALLanguage.vsix

Initialization took 98 seconds
Ready for connections!
Starting EventLog Monitor
Monitoring EventSources from EventLog[Application]:
- MicrosoftDynamicsNAVClientClientService
- MicrosoftDynamicsNAVClientWebClient
- MicrosoftDynamicsNavServer$BC
- MSSQL$SQLEXPRESS

Reading CustomSettings.config from BC163NPupW1-2
Creating Desktop Shortcuts for BC163NPupW1-2
Container BC163NPupW1-2 successfully created

Error in event log
The description for Event ID 216 from source MicrosoftDynamicsNavServer$BC cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Server instance: BC
Tenant ID: default
Environment Name:
Environment Type: Production
Session type: Background
Session ID: 25
User:
Type: Microsoft.Dynamics.Nav.Types.Exceptions.NavNCLDialogException
AutomationId: 8da61efd-0002-0003-0507-0b0d1113171d
SuppressMessage: False
ContainsPersonalOrRestrictedInformation: True
DiagnosticsSuppress: False
DiagnosticsMessage: Use ERROR with a text constant to improve telemetry details
MessageWithoutPrivateInformation: Use ERROR with a text constant to improve telemetry details
SuppressExceptionCreatedEvent: False
FatalityScope: Call
ErrorLevel: Error
Message: Error when downloading dependencies from ground control:
StackTrace:
     at Microsoft.Dynamics.Nav.Runtime.NavDialog.ALError(Guid automationId, String message, NavValue[] values)
     at Microsoft.Dynamics.Nav.BusinessApplication.Codeunit6014627.OnRun_Scope.OnRun()
     at Microsoft.Dynamics.Nav.Runtime.NavMethodScope.Run()
     at Microsoft.Dynamics.Nav.BusinessApplication.Codeunit6014627.OnRun(INavRecordHandle εrec)
     at Microsoft.Dynamics.Nav.Runtime.NavCodeunit.DoRun(DataError errorLevel, NavRecord record)
     at Microsoft.Dynamics.Nav.Runtime.NavCodeunit.InvokeRun(Int32 objectId, Object[] args)
     at Microsoft.Dynamics.Nav.Runtime.ALSession.RunCodeunitAndDisposeSession(NavSession session, Int32 codeUnitId, NavRecord record)
Source: Microsoft.Dynamics.Nav.Ncl
HResult: -2146233088
StackTrace:
     at Microsoft.Dynamics.Nav.Runtime.NavDialog.ALError(Guid automationId, String message, NavValue[] values)
     at Microsoft.Dynamics.Nav.BusinessApplication.Codeunit6014627.OnRun_Scope.OnRun()
     at Microsoft.Dynamics.Nav.Runtime.NavMethodScope.Run()
     at Microsoft.Dynamics.Nav.BusinessApplication.Codeunit6014627.OnRun(INavRecordHandle εrec)
     at Microsoft.Dynamics.Nav.Runtime.NavCodeunit.DoRun(DataError errorLevel, NavRecord record)
     at Microsoft.Dynamics.Nav.Runtime.NavCodeunit.InvokeRun(Int32 objectId, Object[] args)
     at Microsoft.Dynamics.Nav.Runtime.ALSession.RunCodeunitAndDisposeSession(NavSession session, Int32 codeUnitId, NavRecord record)

The request is not supported

Hope I have provided all the info of meaning.

What is the company name in the database?
Do you have more than one company?

Also, you should shift to BcContainerHelper when the time is right (= when you don't have any containers running) - I am not fixing anything in NavContainerHelper anymore and issues found by people are only fixed in BcContainerHelper.

What is the company name in the database?
It's w1 database so Cronus International Ltd.
Do you have more than one company?
Nope, only Cronus
Then maybe specify the companyname as a parameter to run-testsinNavContainer
Will try anyway.

Also, you should shift to BcContainerHelper when the time is right (= when you don't have any containers running) - I am not fixing anything in NavContainerHelper anymore and issues found by people are only fixed in BcContainerHelper.

I know, but hadn't had time to that yet. ;-)

You wrote: As a workaround I have run all the tests in DEFAULT suite from the AL Test Tool "manually" without any (technical) problem.
What does "technical" mean here?
Did you have any issues?
A dialog?
An Error?

You wrote: As a workaround I have run all the tests in DEFAULT suite from the AL Test Tool "manually" without any (technical) problem.
What does "technical" mean here?

Ouch, I was thinking while writing this might lead to a question. It means that there were no issues like the ones I am mentioning above. But there were a lot of failing tests (and that was expected)

Did you have any issues?

The test errors. ;-) Nothing else.

BTW: just reran Run-TestsInBCContainer with company name provided and still same issue.

Can you find the location in the app, where this error pops up:
The current environment is not set as production.
Some external integrations are handled differently in this mode. You can change this in page "NP Retail Setup"
It looks like this dialog pops up and is unhandled.

Great catch. How did you find out? In all the data (above) I could not find anything. Have been trying and searching for days.

You asked how I saw that - in the debugmode output it displays what windows are open at the time of the error. There is a dialog:

Yep, and I saw it some minutes later. As said: "Thanx for your clear view." And sorry for bothering for apparently something so obvious. I have been looking at it over a couple of days and just did not see (or know where to look). Now I surely do.


Ensure all tests of valid source code compare tokenizer output against parse tokens.

This is a work in progress. Wanted to just publish some POC code for testing tokenize() vs. parse().tokens. The tests are failing because it already reveals a bug with tokens in the new Class implementation.
Feedback welcome.

While we have some logic in the tokenizer to infer some sort of context, do we know for sure that the tokens produced by tokenize will match the fidelity of parse? There might be two possibilities if it is not the case:

ES6 syntax requires more context to be inferred in the tokenizer
It is not possible to do so and we have to live the such differences

@ariya we should strive to have equivalent output, and so if that isn't possible in tokenize(), should we consider correctness and always rely on parse?

@mikesherov Depends on the consumer. For correctness, rely only on parse. For other usages (best-effort tokenization for syntax highlighting, auto-complete, etc, tokenize is still useful.

There are a few cases where result of a parse could produce an Identifier where it is producing a Keyword. Both for class and function declaration. That seems to be the extent of it though, given the results of the work I added.

My two cents: Having different tokens returned from each method is confusing as a consumer. If the only argument for differing results is that it's probably "good enough" for some uses, then I'd rather just have tokenize() match what parse() does. If there's a use case where having different outputs is necessary, then it could make sense to differ.

@nzakas It's not a subjective choice, it's the limitation of not knowing the context. In some cases, it can be fixed by inferring enough context. In other cases, it may be impossible to infer (I don't know yet, haven't looked at it in details).
Example (from @mikesherov's description):
> require('./esprima').parse('class A { static(){} }', { tokens: true}).tokens
[ { type: 'Keyword', value: 'class' },
  { type: 'Identifier', value: 'A' },
  { type: 'Punctuator', value: '{' },
  { type: 'Keyword', value: 'static' },
  { type: 'Punctuator', value: '(' },
  { type: 'Punctuator', value: ')' },
  { type: 'Punctuator', value: '{' },
  { type: 'Punctuator', value: '}' },
  { type: 'Punctuator', value: '}' } ]

> require('./esprima').tokenize('class A { static(){} }')
[ { type: 'Keyword', value: 'class' },
  { type: 'Identifier', value: 'A' },
  { type: 'Punctuator', value: '{' },
  { type: 'Identifier', value: 'static' },
  { type: 'Punctuator', value: '(' },
  { type: 'Punctuator', value: ')' },
  { type: 'Punctuator', value: '{' },
  { type: 'Punctuator', value: '}' },
  { type: 'Punctuator', value: '}' } ]

@ariya I understand how basic tokenization is context-free, I've done a fair amount of work in Espree. :) My point is that there is a way to return the same tokens from tokenize() (call parse() internally, then return the context-aware tokens generated), so my opinion is that the decision should be use-case driven.

In my example, not impossible. For non classes, we already return keyword rather than identifier for props that share a name with a keyword.
We should be doing the same for class. That is, dumbing down the parser version to return keyword for consistency.
We could then revisit feasibility of improving both and the tradeoff on speed.

@nzakas I don't follow. Are you saying that we should implement tokenize by wrapping parse and collect the tokens?

@mikesherov The context here is strict mode. Class is parsed with implicit strict and therefore static is recognized/promoted as a keyword instead of a regular identifier. By that time, inside class body handling, the token static has been placed in the token array. To demote static back to an identifier, you probably need to walk back the token array to the closest static.
Unless there is another way, I would say that this is quite a complicated dance and probably not worth it.

I will play around with this, because it potentially addresses a fairly large hole in the existing test infrastructure.

Smarten up tokenizer.
allow the tokensVsTokenize tests to be lenient on identifier/keyword mismatches.
Separate this set of tests out as something we run as a sanity check before release but don't fail Jenkins on.

I'm going to pursue this a bit further to see if I can address the concerns.

@ariya, it also may be as simple as saying lex() instead of scanKeyword() inside class body parsing. I'll dig in a bit here.

@ariya yup, I'm saying do exactly that if that's what people need from tokenize().

@nzakas tokenize caters different use-case: syntax highlighting, auto-complete, etc, where the code is not necessary valid or complete or both.

@mikesherov Technically speaking, we don't have scanKeyword(), only scanIdentifier(). Or perhaps I misunderstand what you are referring to?

@mikesherov This is rather getting outdated already. Do you want to update it again or shall we close it and give it another try at some point?

I'll update it.


Improve GM_xmlhttpRequest support

Summary
GM_xmlhttpRequest and GM.xmlhttpRequest API that are used in List-KR/linkproduct-privacy does not work.
It seems that it is related to lack of AdGuard userscript module's API support.
Used GM.xmlhttpRequest API
details.url, details.method, details.responseType, details.anonymous, details.onload and ResponseObject.finalUrl.
https://violentmonkey.github.io/api/gm/#gm_xmlhttprequest
References

https://github.com/AdguardTeam/CoreLibs/issues/1780
https://github.com/List-KR/linkproduct-privacy (Tested version: modified 1.0.1)

This may be caused by same issue as #1785


force https for the npm ui

To use an userinterface on http to give other services https is a bit odd.
Recommend to use a extra domain for the ui. If the domain is present, force the use this domain with https and prohibit the the serverip:81 path.
Toggling the ui via the docker-compose.yml would be nice to. This configuration will be readonly most ot the time.
btw: npm is set for node package manager. It is a bad decision to use it for another piece of software.

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/182


fossil: 2.3 -> 2.5

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5/bin/fossil --help got 0 exit code
ran /nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5/bin/fossil help got 0 exit code
ran /nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5/bin/fossil version and found version 2.5
ran /nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5/bin/fossil --help and found version 2.5
ran /nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5/bin/fossil help and found version 2.5
found 2.5 with grep in /nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5
found 2.5 in filename of file in /nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5

@grahamcofborg build reposurgeon fossil

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘rcs-5.9.4’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/applications/version-management/rcs/default.nix:19 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
gzipping man pages under /nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28/bin
patching script interpreter paths in /nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28
/nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28/bin/.repotool-wrapped: interpreter directive changed from "/bin/bash" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/bash"
/nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28/bin/.reposurgeon-wrapped: interpreter directive changed from "/usr/bin/env python2" to "/nix/store/7b2z0vfbs9539ga4pxx5gmli47rz5y3n-python-2.7.14/bin/python2"
/nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28/bin/.repodiffer-wrapped: interpreter directive changed from "/usr/bin/env python2" to "/nix/store/7b2z0vfbs9539ga4pxx5gmli47rz5y3n-python-2.7.14/bin/python2"
checking for references to /tmp/nix-build-reposurgeon-3.28.drv-0 in /nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28...
/nix/store/3q6rdwkc830nx8k6ni8gjkggx4yr3cp5-reposurgeon-3.28
/nix/store/14r53ilafr0lhqc5czfifp4bwqk5rh1c-fossil-2.5

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘darcs-2.12.5’ in /var/lib/gc-of-borg/nix-test-rs-2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-2/pkgs/development/haskell-modules/hackage-packages.nix:55350 is not supported on ‘aarch64-linux’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.


Add aria error attributes to field upload client side validation

Description
Manually tested. Before this change, the error was not read out when the button was selected. After this change, it is read out.
Release notes:
[a11y] Add aria error attributes to file upload questions, so screen readers read out the error.
Checklist

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
Fixes #1878

Codecov Report

Merging #3415 (7c0b77d) into main (f220c1f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #3415   +/-   ##
=========================================
  Coverage     80.29%   80.29%
  Complexity     2359     2359
=========================================
  Files           291      291
  Lines          9360     9360
  Branches        627      627
=========================================
  Hits           7516     7516
  Misses         1597     1597
  Partials        247      247

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


init containers in k8sv1.7

I think maybe copy in k8s1.6 to k8s1.7,so fix it !

This change is

No, in v1.6, initContainer is beta. So it is not a typo. remainint it is OK.

i know，in 1.6 is beta ，so in 1.7 is not beta？

Init containers have graduated to GA in 1.6, i.e. exited beta, so we should leave the doc as-is.
See https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.6.md#node-components-1
[stable] Init containers have graduated to GA and now appear as a field.

Ok, I'm closing this PR then.


Fix typo "avaiable"

Hope this helps
¯_(ツ)_/¯

haha, thanks @NicoWeio!

Thanks for the library. I'm just starting out!
And it is always great to see developers care about what they produce :)


add enabled flag for firestore

fetch only if enabled is true,
Coinsider the example
  const [value, loading, error] = useDocument(
    doc(firestore, "users", useruid)
  );

adding  a optional flag to fetch only when useruid is defined
  const [value, loading, error] = useDocument(
    doc(firestore, "users", useruid),
    {
      enabled: useruid,   // make a network request if only Boolean(useruid)  is true
    }
  );

If required, I am willing  to contribute

#110

@hussamkhatib As per #110, the approach used by this library is to support the passing of null / undefined to the hook to prevent loading


[Model Request] Mistral 7B on iOS and iPadOS

⚙  Request New Models

Link to an existing implementation (e.g. Hugging Face/Github): https://huggingface.co/Open-Orca/Mistral-7B-OpenOrca
Is this model architecture supported by MLC-LLM? (the list of supported models)  Yes

Additional context
I think the ability to run a good LLM locally on iOS is the single most important feature of this project. On Macs/Linux/Windows there're other ways to run a local LLMs that work perfectly fine. But on iOS it is not possible -- or extremely hard -- until mlc-llm. Mistral 7B has the potential to be as good as GPT 3.5 Turbo, and potential applications are endless.
Also, please consider iPadOS to be a viable target deserving of separate treatment. iPad Pros now come with M2 chips with a lot of RAM. And running apps get more RAM than iOS.
Finally, please make it easier to download/convert new models in the Mistral family without having to create new iOS libraries.

Mistral on iOS should be supported by this PR: https://github.com/mlc-ai/mlc-llm/pull/1320.
Closing this issue for now; feel free to open another one if there are other questions/requests. Thank you!

@CharlieFRuan that PR was merged a couple of weeks ago. I checked and the MLC Chat app on my iPhone is up to date. Downloading the weights from the URL in the PR description works, but attempting to open a Mistral chat instantly crashes the iOS app. Are we still waiting on the app update to go through App Store review?

@davidpissarra Could you take a look when you get a chance? Thank you!

Hi @coder543 MLC Chat with mistral support is still not upstreamed on the app store. Still, it already supports mistral on the testflight app.


mathjax problem

the mathjax = null in analysis/_output.yaml causes problems when rendering math in html

The problem should be fixed now with "mathjax: default".
MathJax is a Java script for displaying mathematical notations that are written in LaText and MathML in a web browser. We can control how MathJax is included in _output.yaml.
"mathjax: default" includes the MathJax code in the html. This option requires online access.
"mathjax: null" does not include MathJax code in the html. Some of your mathematical notations may not be displayed properly.


Unable to disable alignComments

With this...
"evenBetterToml.formatter.alignComments": false,

...the comments are still aligned.
It seems like this setting is ignored.

This issue helped me, after set up setting and restart VSCode, it works.


Migrationscript doesn't work with oracle database

Migrationscript doesn't work with oracle database, because the constraints like 'ENABLE' doesn't exist in oracle database.
Originally posted by @DK-Stern in https://github.com/adessoAG/budgeteer/commit/c0f8d6f2c0f7b9d9b7118fcdcdb5f2da4dd43aa4#commitcomment-31697714

Migration script 1.1.0 has already been successfuly applied, right? Can you specify which version of the database you are migrating and what errors you are getting. The script seems to be working for me. Furthermore, I believe ENABLE and DISABLE are valid in Oracle as suggested in this post: https://dba.stackexchange.com/questions/57123/what-does-enable-mean-in-oracle-ddl-constraint

You've been right. It was an misunderstandig from me as i wanted to fix the integration tests.