Difference between MALUUBA and MALUUBA_RL

Hi, I'm using commit be13417 and paid attention you made some changes later on. So what is the difference between MALUUBA and RL. Is it just a naming?

The difference is that the _RL model (now RL- models) include the placeholders and losses for policy gradient training. The difference between SEQ2SEQ and MALUUBA model types is the additional layer of condition encoding, which I replaced with the advanced_condition_encoding  flag. If you want to fine tune the model then you need to use an RL model type (even for the first part of the training). Hope that helps.

To replicate the approach used in the paper, run ./train.sh --advanced_condition_encoding --nocontext_as_set. You could also add the flag --model_type RL-MALUUBA if you wanted to give the run a more readable name, but this is optional.

Thank you very much. Can you also list flags that should be used with other
types of approaches you have.
On Fri, Dec 28, 2018 at 2:22 PM Tom Hosking<EMAIL_ADDRESS>wrote:

To replicate the approach used in the paper, run ./train.sh
--advanced_condition_encoding --nocontext_as_set. You could also add the
flag --model_type RL-MALUUBA if you wanted to give the run a more
readable name, but this is optional.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bloomsburyai/question-generation/issues/10#issuecomment-450413440,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Abba1G1scke94raoAmxznJqfYfv7Xz9Fks5u9m95gaJpZM4ZkD60
.

Check flags.py for a full list

Hi Tom,
Would you recommend retraining MPCM.py and language model if I would like
to supplement Squad dataset with my own data. In case you recommend to
retrain those are there any flags/arguments I should use?
Thank you
On Fri, Dec 28, 2018 at 3:14 PM Tom Hosking<EMAIL_ADDRESS>wrote:

Check flags.py for a full list
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bloomsburyai/question-generation/issues/10#issuecomment-450420377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Abba1ChHCHutBhb1ReqIhsqunYtaiZr2ks5u9nu3gaJpZM4ZkD60
.


DRAFT - Tests the solution offered by AWS. Trying first via a new statement.

A reference to the issue / Description of it
{Please write here}
How does this PR fix the problem?
{Please write here}
How has this been tested?
Please describe the tests that you ran and provide instructions to reproduce.
{Please write here}
Deployment Plan / Instructions
Will this deployment impact the platform and / or services on it?
{Please write here}
Checklist (check x in [ ] of list items)

[ ] I have performed a self-review of my own code
[ ] All checks have passed
[ ] I have made corresponding changes to the documentation
[ ] Plan and discussed how it should be deployed to PROD (If needed)

Additional comments (if any)
{Please write here}

Issue still prevelant.


OCommandExecutorNotFoundException while using unionall

Expected behavior and actual behavior
I am trying to make a simple query with unionall function but I get the following error.
Error: com.orientechnologies.orient.core.command.OCommandExecutorNotFoundException: Cannot find a command executor for the command request: sql.unionall($a, $b)
	Storage URL="plocal:/tmp/db/konnect"

Steps to reproduce the problem
orientdb {db=konnect}> begin
orientdb {db=konnect}> let $a = select from person where out("has").email in<EMAIL_ADDRESS>orientdb {db=konnect}> let $b = select from person where out("has").email in<EMAIL_ADDRESS>orientdb {db=konnect}> let $c = unionall($a, $b)
orientdb {db=konnect}> commit

Important Questions
Runninng Mode

[x] Embedded, using PLOCAL access mode
[ ] Embedded, using MEMORY access mode
[ ] Remote

Misc

[ ] I have a distributed setup with multiple servers. How many?
[ ] I'm using the Enterprise Edition

OrientDB Version

[ ] v2.0.x - Please specify last number:
[ ] v2.1.x - Please specify last number:
[x] v2.2.0 - Please specify last number:

Operating System

[ ] Linux
[x] MacOSX
[ ] Windows
[ ] Other Unix
[ ] Other, name?

Java Version

[ ] 6
[x] 7
[ ] 8

Hi @amyth
Try this:
orientdb {db=konnect}> begin
orientdb {db=konnect}> let $a = select from person where out("has").email in<EMAIL_ADDRESS>orientdb {db=konnect}> let $b = select from person where out("has").email in<EMAIL_ADDRESS>orientdb {db=konnect}> let $c = SELECT unionall($a, $b)
orientdb {db=konnect}> commit

Thanks
Luigi

@luigidellaquila Thanks so much for the response. It works absolutely fine if I use it with select.


How to add a custome width height on a image inside a slider

How to add a custome width height on a image inside a slider
here is my HTML

and my jqyuery is
jQuery('#out-of-the-box-demo').slippry();
kindly help me

Hey, I am not sure if I understand your question but probably just add something like:
.sy-slides-wrap img {
 height: 300px; // or a max-height: 300px; or whatever you would like to do!
}

I hope this helps,
cheerio!

Thanks it fixed my issue Thanks for you help @sftsk sftsk


upgrade(installer): Improve APM injection sockets

What does this PR do?

Moves sockets to /var/run/datadog/*.socket
Override the deb agent units to not have a RuntimeConfig (this stops deletion of /var/run/datadog on unit stop)
Remove systemd dependency on the injector install
Adds symlinks for SysVInit variable override as a best effort

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


TextField Label shrinked on state update

Hello guys, I'm making a multi step form where I have the current step in the state and a function that changes the TextFields that are shown accordingly to the step state. The issue that i'm having is if any TextField that inherit the position of a TextField with a startAdornment has is label shrinked.

Steps to Reproduce 🕹
You can reproduce the error on the codesandbox below, just click in the next button https://codesandbox.io/s/suspicious-mestorf-64m8k2mvxr
Thanks for the help and for the awesome project, much love <3

@gfsd3v We have had a similar discussion about the problem in https://github.com/mui-org/material-ui/pull/15386#issuecomment-484404344 cc @eps1lon. In your case, you don't have a choice, the first-row input value is persisted between the two steps. It's wrong. You should add a key to the fragment. Once the key is added to fix the value leak between the two states, the Material-UI problem you describe is gone too: https://codesandbox.io/s/label-shrink-bug-with-start-adornament-376c1.

@oliviertassinari Now I understood what was happening, thank you so much for the help and I'm sorry I wasn't able to find #15386, I'll be more thoroughly in my searches next time, thanks again.

@gfsd3v No problem, no need to be sorry! Well we might be able to find a better solution, but it's not obvious to me.

That's probably one case where we should actually fix it. It's not apparent in the code that react doesn't think it should re-mount those components. The problem is that label can be any renderable node so putting it into effect dependencies might be overzealous.
It's probably best to add a section in our docs since this is a very common issue.

We have explored a solution in #17680 that seems to be good enough, it will likely solve this problem.


New device type in Broadlink component

Question for @felipediel: where are the learned codes stored? Can't file any new file, so they must be stored on the db, which is bad, if I'm right. This, because if you have to wipe your db you loose them, I mean all of them. Can you please clarify?

The codes are inside the .storage folder in the configuration directory. They start with 'broadlink_remote_' and end with the device's MAC address followed by '_codes'. They can be opened by any text editor as they are in JSON format.

Great. That's very good indeed.


not working for me error related to path

not working for me please have look the screenshot.
Somebody help me out.

how did you produce this stacktrace? I too am having issues launching the terminal

@morenoh149  In the atom hit=>   ctrl+shift+i

that doesn't open the console for me. I also used cmd+. to see the key binding and ctrl+shift+I isn't mapped.

@morenoh149 Try these few fixes may be it will help you.
-- Try the same combination Ctrl+Shift+I two times
-- Also try Ctrl+Alt+I
-- If you using Mac try this Cmd+Opt+I

cmd+Opt+I on mac 👍

Please retest again with platformio-atom-ide-terminal 2.9.0 is using node-pty-prebuilt instead unmaintained and outdated pty.js


chore(ghe): move to ghe

Move repo to GHE as requested by @LappleApple or in my personal account.
I like more the second option also because will be easy to maintain the build process more or less untouched on this repo https://github.com/zalando/zalando.github.io.

Pardon this one: https://github.com/zalando-incubator/zalando.github.io-dev


resource group typo

Hi there
You initially create 'myResourceGroup3', but in the cleanup script you remove 'myResourceGroup'.
Is this a typo or am I missing something?
Thanks

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

ID: aefb8656-ab1a-bbde-c2d0-d30e5ed42820
Version Independent ID: c059b9f5-5513-8959-e416-84c801a099cb
Content: Azure PowerShell Script Sample - WordPress
Content Source: articles/virtual-machines/scripts/virtual-machines-linux-powershell-sample-create-vm-wordpress.md
Service: virtual-machines-linux
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

Thanks for the feedback! We are currently investigating and will update you shortly.

@pelagos You are right. That's a typo.

Thanks @jakaruna-MSFT for fixing the issue.
@pelagos the changes should go live in a few hours.


feat(32): Nova versão do destino.

close #32

Codecov Report

Merging #33 (25e8db7) into main (33d5611) will increase coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   96.31%   96.46%   +0.15%
==========================================
  Files          40       38       -2
  Lines         842      878      +36
==========================================
+ Hits          811      847      +36
  Misses         31       31

Files Changed
Coverage Δ

jornada_milhas/core/admin.py
100.00% <ø> (ø)

jornada_milhas/core/serializer.py
100.00% <ø> (ø)

jornada_milhas/core/migrations/0001_initial.py
100.00% <100.00%> (ø)

jornada_milhas/core/models.py
100.00% <100.00%> (ø)

...has/core/tests/api/destination_crud/test_create.py
100.00% <100.00%> (ø)

...ilhas/core/tests/api/destination_crud/test_list.py
100.00% <100.00%> (ø)

...lhas/core/tests/api/destination_crud/test_patch.py
100.00% <100.00%> (ø)

...milhas/core/tests/api/destination_crud/test_put.py
100.00% <100.00%> (ø)

...ilhas/core/tests/api/destination_crud/test_read.py
100.00% <100.00%> (ø)

jornada_milhas/core/tests/conftest.py
100.00% <100.00%> (ø)

... and 2 more

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


Fix bug in classification

When passing symmetric uncertainties for C, N for example and then splitting them up, there's a rare scenario where TypeError does not get raised but the routine invokes an IndexError for splitting up the uncertainties. This is now resolved by checking for both types of exceptions.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.36%. Comparing base (8cdb95f) to head (0d7e5ac).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #39      +/-   ##
==========================================
+ Coverage   81.26%   83.36%   +2.10%
==========================================
  Files          11       11
  Lines         571      571
==========================================
+ Hits          464      476      +12
+ Misses        107       95      -12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Linter rule use-recent-api-versions suggests older api-version

Bicep version
eskillarsen$ bicep --version
Bicep CLI version 0.29.47
VSCode extension shows the same version.
Describe the bug
The linter rule use-recent-api-versions suggests (and accepts) an older api-version that the current one.
Might have something to with -preview versions
bicepconfig.json:
"use-recent-api-versions": {
    "level": "warning",
    "maxAllowedAgeInDays": 730
},

To Reproduce
All files are from the ALZ-Bicep repo

This is a dupe of https://github.com/Azure/bicep/issues/10740.  Yes, the default behavior is to prefer preview versions (it uses the same behavior as the old ARM-TTK tests, which are somewhat complicated).  In #10740, I suggested https://github.com/Azure/bicep/issues/10345 as a way to control this behavior, but haven't had time to fix it.  Please upvote #10740 and #10345, and feel free to add comments there, to increase their priority, thanks!


Add hadoop3 jar to the artifacts

What changes are proposed in this pull request?
Add the alluxio hadoop3 jar client to the artifacts
Why are the changes needed?
Some users may want to use hadoop3
Does this PR introduce any user facing changes?
no

fyi @maobaolong

alluxio-bot, merge this please

@Kai-Zhang could you double check if the new generate-artifact is including hadoop 3.x jar? Thanks a lot!


 This can
recover state machine to the state corresponding to the committed log id upon
system startup.

Re-applied log entries after startup
If the last applied log id is smaller than the committed log id saved in
storage, re-apply log entries from the next index of last applied log id to the
committed log id.

Version 1 storage API RaftStorage and Version 2 storage API
RaftLogStorage both add API save_committed() and read_committed()
to support saving/reading committed log id.
These two new API are optional and provides default dummy
implementation, an application does not need any modifications if it does
not need this feature.

This change is

@schreter
The overhead introduced by calling save_committed() should be minimal: in average, it will be called for every max_payload_entries log entries. Meanwhile I do not quite worry about the penalty, unless there is a measurable overhead.
The reason of adding a persisted committed is to just make things clear. Without persisting committed:

The RaftMetrics.last_applied will fall back upon startup, which may confuse a monitoring service.
The application may depend on the state in the state machine, e.g., by saving node information in the state machine. State falling back may cause a node to try to contact a removed node.
If the application provide stale reading from follower nodes, it's hard for the follower to know how many logs it must apply before serving stale read request.

Although these issues can all be addressed, it introduce more work to make things strictly correct.
A state machine that won't revert to a former state is easier to use:)

@drmingdrmer

The overhead introduced by calling save_committed() should be minimal: in average, it will be called for every max_payload_entries log entries.

Ah, OK, thanks, that is what I was missing. Then, the overhead should be negligible.

The RaftMetrics.last_applied will fall back upon startup, which may confuse a monitoring service.

True. But, OTOH, the metrics is still "correct" :-). After the restart, the state machine needs to be updated.

The application may depend on the state in the state machine, e.g., by saving node information in the state machine. State falling back may cause a node to try to contact a removed node.

Also true. We do store such info in the state machine ourselves, but this is not part of a regular snapshot, rather part of the data directory, which is persisted immediately after a change occurs. So it's fairly easy to handle that.

If the application provide stale reading from follower nodes, it's hard for the follower to know how many logs it must apply before serving stale read request.

Ahhh, that is unsafety in person :-). Reading from follower nodes requires some additional protocol to ensure correctness. For instance, we as a database can use MVCC and then it's fairly easy to check whether the last required commit (from the DB perspective, not from the Raft perspective) made it to the follower already and thus whether we can safely serve proper snapshot of the data for read or not.

A state machine that won't revert to a former state is easier to use:)

That's also true.
I don't have a problem with the change, it just seemed as an unnecessary change. So maybe you could copy&paste the above info to the docs of respective methods and/or to the general docs.
Thanks.

If the application provide stale reading from follower nodes, it's hard for the follower to know how many logs it must apply before serving stale read request.

I was wrong about this: When the follower receives a committed_log_id message from the leader, the committed_log_id is always greater than the last know committed log id before restart.

I don't have a problem with the change, it just seemed as an unnecessary change. So maybe you could copy&paste the above info to the docs of respective methods and/or to the general docs.

You are right. That's what I'm gonna do.


[Test]

|---------------------------------|------------------------------------------- |
| Camera Model                       |  D400
| Firmware Version                   | <IP_ADDRESS>
| Operating System & Version |   Ubuntu 16
| Kernel Version (Linux Only)    | <IP_ADDRESS>
| Platform                                 | NUK
| SDK Version                            |  LRS 2.10.1
Testing ZD change state to Open upon a github update to a Pending state

[Realsense Customer Engineering Team Comment]
Setting to Pending.

This is response to the update to pending.

[Realsense Customer Engineering Team Comment]
Setting to pending again as a test for the final version of the trigger.

This is another comment that should cause the ZD ticket status to be reset to "Open".

[Realsense Customer Engineering Team Comment]
Test is concluded.


portfolio: 0.63.1 -> 0.64.0

Description of changes
https://github.com/buchen/portfolio/releases/tag/0.64.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

1 package built:

portfolio


Remove invisible characters from vscode.d.ts

If you try to copy paste glob pattern from vscode.d.ts - then it simply won't work because it contains invisible characters:
https://github.com/microsoft/vscode/blob/6d913c4c14bc9d7924cef5f502682873c89bab2d/src/vs/vscode.d.ts#L1901
You can search for regular expression: [\u200B-\u200D\uFEFF] or use an extension https://marketplace.visualstudio.com/items?itemName=nhoizey.gremlins to find them.

The problem is that you cannot type */ inside a jsdoc comment. That's why these invisible characters are being used. Open for suggestions


Fix for register namespace via policy part three

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - changeanalysis - mgmt - tests

/azp run java - machinelearning - mgmt - tests

/azp run java - providerhub - mgmt - tests

/azp run java - recoveryservices - mgmt - tests

/azp run java - resourcemover - mgmt - tests

API change check
API changes are not detected in this pull request.


Proper Symlink Support

Description
Symlink files and folders are not shown as .symlink files and the properties information is empty. Whereas in the original windows file explorer, it correctly shows the filetype as .symlink and has properties information like what's the target and path etc.
Also drag and drop functionality is not working on symlink files and folders in the files app, whereas it works in original windows file explorer app.
Steps To Reproduce

Create a symlink for a file or folder
View the filetype and properties in both files app and windows file explorer app

Expected behavior

Proper filetype should be given
Drag and drop support for symlinks should be done

Files Version
v<IP_ADDRESS>
Windows Version
Windows 11 21H2 22000.346
Relevant Assets
Picture of symlinks in Files app

Picture of symlinks in File Explorer app (which is expected)

Picture of symlink properties in Files app vs File Explorer app

Drag & Drop Functionality not working in Files
https://user-images.githubusercontent.com/92441536/142660214-be706681-ce27-47a5-943e-8e51b82446a0.mp4

This issue should be resolved with #7006.


Order all entity queries by id to get deterministic ordering of results

Resolves #1036
Entity queries are each appended with an order by id filter, so query results are always consistent. This is useful for when no order by is specified or the field being ordered by has duplicates.

GraphQL Sorting Filter
SQL Order By

(OrderBy: AttributeName)
ORDER BY 'data'->AttributeName->>'data' ASC, id ASC

()
ORDER BY id ASC

:heart:


Interview-Questions

hey nice content. But there were some grammatical errors that I've corrected.
Please approve the pull request as hacktoberfest is ending.
Thank-you.

Hey @ankitasharma88990, Thanks for scrupulously scouring the repo for grammatical mistakes. But as you would have seen in the contributing guidelines of this repo and even in hacktoberfest quality contribution guideline, typos and whitespace fixes are highly discouraged. Nevertheless, If you can add new questions to any company's article, I would be happy to merge the PR. Top contributors will be mentioned in the home page of this repo.

Okay, Thank-you.
On Mon, Oct 28, 2019 at 5:24 PM Rishabh Maurya<EMAIL_ADDRESS>wrote:

Hey @ankitasharma88990 https://github.com/ankitasharma88990, Thanks for
scrupulously scouring the repo for grammatical mistakes. But as you would
have seen in the contributing guidelines of this repo and even in
hacktoberfest quality contribution guideline, typos and whitespace fixes
are highly discouraged. Nevertheless, If you can add new questions to any
company's article, I would be happy to merge the PR. Top contributors will
be mentioned in the home page of this repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rishabh115/Interview-Questions/pull/91?email_source=notifications&email_token=AHKSCH3CYKYRS4TDISNES3LQQ3HGTA5CNFSM4JFW5AOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECMTUNA#issuecomment-546912820,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKSCH7SMPCYIAHLCCVVHNDQQ3HGTANCNFSM4JFW5AOA
.

If there are any new commits you are going to make, pls see to it by tomorrow.


How to add Unsubscribe URL in email design?

Apologies -  if this is not the right forum to ask this. I checked the entire documentation and could not find this.
I am looking to add an unsubscribe URL to the end of an email template. What is the variable I can use to add it? I assume a variable like "{{ UnsubscribeURL }}" needs to be placed in the email body. Could you please help?

You can access via {{ unsubscribeEmailUrl }} for a direct unsubscribe link, {{ preferencesUrl }} for a link to a preference page to modify their subscription settings

Seems to be working fine! Thank you! Congratulations for making this - we are trying to explore if we can use this with posthog.

Another question - when we click on the unsubscribe URL, it is not counted as a click in the delivery details. Is this by design or we can do something to make this click trackable?

Another question - when we click on the unsubscribe URL, it is not counted as a click in the delivery details. Is this by design or we can do something to make this click trackable?

Few questions:

Do you have link wrapping turned on for your project?
What does the link look like in the generated HTML after it is sent?
Are other links in the same email getting wrapped and tracked properly?

Yes Link wrapping is turned on for the project.
The unsubscribe link looks like this - https://domain.com/unsubscribe/email?u=3G5291K94Y&c=6NMKZ3KEQG
Another link that's tracked properly looks like this - https://domain.com/c?u=3G5291K94Y&c=6NMKZ3KEQG&r=https%253A%252F%252Fmjml.io%252F. It finally redirects to https://mjml.io/

Also, On a side note - I am having a hard time getting the file uploads working. My setup is - parcelyvoy docker  + nginx server. I tried following the steps from here - https://github.com/parcelvoy/platform/issues/381. However not able to get it working since this references caddy server and we are using nginx. Would you have any additional documentation?
Some questions :

The dir-path under the  "volumes: - uploads: " in the docker-compose.yml can be any directory on the disk? Are there any configurations wrt docker for this dir-path? Are there any permission configurations?
In Nginx config, should I use
location /uploads
{ root  }

or use this - https://github.com/parcelvoy/platform/issues/381#issuecomment-1991611239
Thank you for your help!

Also, we tried sending a newsletter to 50k users. It sent around 14K emails and stopped. After checking I realized that we ran out of disk space. I checked the MySQL db size inside docker, and its size crossed 7.3 GB. I had allocated 12GB of disk space for testing. I wanted to understand the expected behaviour here - how much disk space is expected to be used?
Our idea was to start using this for our weekly newsletters + journeys. We tried sending the newsletter first (to 50k first, were going to send to 600K in total) to test and then were going to start experimenting with journeys.

In the future, please open new issues for new topics otherwise it wont be helpful to other folks that might experience the same thing. This thread is going to get quite messy.
For unsubscribe links, this should be resolved in the next release. It looks like we had a check in place to not wrap internal links which the unsubscribe link is considered.
For images:

Please consult the included Nginx config that automatically comes with the frontend portion of the server. https://github.com/parcelvoy/platform/blob/main/apps/ui/docker/nginx/conf.d/default.conf
In theory you can use any folder but you'll need to declare it in Docker compose and make sure the path is pointed exactly to the internal path - uploads:/usr/src/app/public/uploads
We would not recommend using the local image store for anything more than testing, an S3 compatible driver is the preferred route to go for both data resiliency and load times for your users.

Without knowing your setup I can't provide more details unfortunately. In general we would recommend sticking to the provided Docker Compose file.
For database size, that seems a bit high, but I don't know what all you have in there outside of just those emails you are sending. You would have to give me a breakdown of what size each of your tables is. I'm assuming most of that size is probably in the user_events table which is expected to always be the largest since it stores a copy of the message sent to each user so you can preview it. Total amount stored will be proportional to how large your messages are.

Thank you for your reply and my apologies for adding everything in one issue. I will take care henceforth.

We will wait for the next release. This is not a blocker.
We will use the S3 route as suggested.
Here is what we did :
a. Installed Parcelvoy using the docker images.
b. Added a list of 50K users.
c. Sent a newsletter to all users. This is the email. We did not use any user properties in the email. The Mysql DB size reached 7.3GB after sending 14K emails. Since the server ran out of disk space, the rest of the email could not be sent.
d. Would it be possible to have a configuration where a per-user copy of the message is not stored? I ask this because we typically send 3M+ emails every month and were planning to start journeys that would add more emails. Just having the read/open stats per user should be enough. I am afraid that In the current state, we would be using too much disk space as we use this on a consistent basis.

@tanmay-predisai just merged a PR that will let you turn off logging the email preview via an env variable (LOG_COMPILED_MESSAGE). I would still be curious to know the sizes of each of your tables though to validate that that is in fact the table causing issues for you. The users table for example could also be problematic depending on what data you are storing for each user.

Hello, Thank you for this. We tried doing this and here are the updates:

Made a fresh install on a new server instance. We tried adding the variable in .env file - We added the line  LOG_COMPILED_MESSAGE=false at the end of the .env file.
Tried sending 50K emails again. However, the disk size again started increasing. Fortunately, we had made the new server with more disk space so the server did not crash. Here is the screenshot of the table sizes.

Seems we made some mistake in configuring the variable value. Can you please point out how to do this?

@tanmay-predisai can you please provide some examples of what an item in the user_events table looks like? Feel free to scrub any sensitive data, but without knowing what is in there I can't be more helpful

Closing this for now since there has been no new activity, if you have further issues please comment or open a new issue. Thanks!


Add coveralls to CI

Summary
This PR reports test coverage to https://coveralls.io/github/Qiskit-Extensions/qiskit-experiments every time the CI tests are run. Going forward, the coveralls bot should report coverage beneath each PR as a comment. This is done by adding a cover environment to tox that replaces the default env in the CI when running tests + coverage (this avoids having to run tests twice, once for CI and once to generate coverage). It runs the tests and generates a coverage report at coverage.lcov, which is then sent to coveralls using its github action.
Details
Coverage only runs on MacOS—on Windows, coverage doesn't generate the report for some reason, and it also seems unnecessary to generate coverage for multiple OS's.

LGTM, thanks Helena. Can this be merged now?

@eliarbel Great, can you approve it?

The CI failed due to the new scipy 1.11 release causing an incompatibility with cvxpy, so I've pinned the version.


Update sconfig to 1.5.0

Updates org.ekrich:sconfig from 1.4.9 to 1.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.ekrich", artifactId = "sconfig" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #183.


Ensure firewalld is not attempted on el6

I'm seeing an issue were chef provider selection appears to be non-deterministic, depending on whether the firewalld or iptables provider is checked first.
This resulted in firewalld trying to install on EL6 machines.
The included patch ensures that there is no overlap in provider selection.

@glenjamin What version of chef was this one? I'd like to debug it further if possible.

This was seen on a few versions between 12.2.1 and 12.4.1.
I've been unable to find any documentation that indicates how chef selects providers - I added some debug logging into the node block, and it appeared to be based on first-matching.

We're testing against 12.4.1, and I haven't seen this one. I'd like to fix the bug in chef proper, if that's where the problem is. There was definitely a bug in Chef 12.4.0 where the block was never called, so you would have seen the problem on that version for sure.

Could you give me a specific Chef version and distro/version you saw it on, so I could test that?

I saw this on at least  centos 6.6 on azure (open logic) running chef 12.4.1
My initial manual chef-client run correctly selected iptables, but future chef runs and chef-service runs across the estate started failing.
I patched the cookbook with logging of platform version in both the iptables and firewalld provider, and saw only the firewalld provider log "6.6" before beginning its install.
I applied the attached fix to our chef server by uploading the fork and am no longer seeing any issue.

Reading the comment in https://github.com/chef/chef/blob/master/lib/chef/provider_resolver.rb indicates that the selected provider is load order dependent
Is there ever a scenario where firewalld should be selected when platform version is less than 7? If not then I believe this patch is valid, and ensures firewalld will not be considered for auto-selection on older systems.

Hi @glenjamin -- yes, I agree that this would be a valid fix; I was hoping we could understand why it doesn't already work though. I'd like to report the bug upstream if chef isn't behaving correctly. I'll open a separate issue for it...

I think the key phrase is this one:

The first matching Provider in the most recently registered list is selected and returned.

https://github.com/chef/chef/blob/master/lib/chef/provider_resolver.rb#L44
Unless you explicitly load the files in the order you want then you're at the mercy of whatever require_all magic chef uses - which presumably is not strictly defined to be equivalent cross-platform.

I believe chef should also choose providers with blocks before providers without those. That bug I linked was actually about 12.4.0 not doing that, and then they fixed it -- https://github.com/chef/chef/issues/3593.
Specifically, check out this comment from one of the core chef developers:

Both providers match on centos, and for some reason the NodeMap stuff is not considering the filter with the block to be of a 'higher priority' and returning it. Which is a bug in core chef AFAIK (probably something that jkeiser needs to look at).

He goes on to suggest the same solution you've contributed:

But the problem can be resolved here by making the selection of the provider unambiguous. You always want to select sysvinit on centos/scientific/oracle/redhat where pv < 7.0 and always want to select systemd on those when pv >= 7.0 so that is exactly how the provides lines should be fixed to read.

But I still think there's a bug in core chef somewhere, based on that comment.

Cheers for the links, definitely sounds like a bug in the more general case then!

On 29 Sep 2015, at 16:40, Martin Smith<EMAIL_ADDRESS>wrote:
I believe chef should also choose providers with blocks before providers without those. That bug I linked was actually about 12.4.0 not doing that, and then they fixed it -- chef/chef#3593.
Specifically, check out this comment from one of the core chef developers:
Both providers match on centos, and for some reason the NodeMap stuff is not considering the filter with the block to be of a 'higher priority' and returning it. Which is a bug in core chef AFAIK (probably something that jkeiser needs to look at).
He goes on to suggest the same solution you've contributed:
But the problem can be resolved here by making the selection of the provider unambiguous. You always want to select sysvinit on centos/scientific/oracle/redhat where pv < 7.0 and always want to select systemd on those when pv >= 7.0 so that is exactly how the provides lines should be fixed to read.
But I still think there's a bug in core chef somewhere, based on that comment.
—
Reply to this email directly or view it on GitHub.


Broken "goto definition" and annoying reminders

Issue Type: Bug
Issue 1:

Download the latest insider version (code-insider-x64-1607925350.tar.gz) of VScode and install it.
Launch the installed VScode.
If you choose not to let Microsoft collect the usage data, then VScode will remind you to learn how to opt in this collection every time you launch VScode (see attached pictures);
If you choose to let Microsoft collect the usage data, then VScode will remind you to learn how to opt out this collection every time you launch VScode (see attached pictures);
In a word, not matter what you have chosen, VScode just keeps reminding the opposite, and there is not an option to disable it!

Issue 2:
"goto definition" is broken in v1.53 (tested with a Python code), this function works with the latest insider version built (Version: 1.52.0-insider, Commit: dbbf7079b20b3036b3ff5ac2e2106b84dd3c6d66, Date: 2020-12-10T16:27:17.115Z, Electron: 9.3.5, Chrome: 83.0.4103.122)
========================================================================================
VS Code version: Code - Insiders 1.53.0-insider (96b426ef1da0f0a51ce9ef1931cd1fd2322547e4, 2020-12-14T05:39:59.827Z)
OS version: Linux x64 3.10.0-693.17.1.el7.x86_64

System Info

Item
Value

CPUs
Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz (32 x 2100)

GPU Status
2d_canvas: enabledgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabled_readbackwebgl2: enabled_readback

Load (avg)
1, 1, 1

Memory (System)
187.41GB (118.97GB free)

Process Argv
--no-sandbox --crash-reporter-id c391a5dd-fd9b-430b-a8f5-6e09b623c3dc

Screen Reader
no

VM
0%

DESKTOP_SESSION
undefined

XDG_CURRENT_DESKTOP
undefined

XDG_SESSION_DESKTOP
undefined

XDG_SESSION_TYPE
undefined

Extensions (5)

Extension
Author (truncated)
Version

python
ms-
2021.1.421359945-dev

vscode-pylance
ms-
2020.12.3-pre.1

jupyter
ms-
2020.12.414227025

cpptools
ms-
1.1.3

material-icon-theme
PKi
4.4.0

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221882
python763:30178808
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
python504:30227505
vswsl492cf:30208930
wsl2promptcf:30219163
vstry244:30230484
pythonvsdeb440:30224570
unusedpromptcf:30219165
folderexplorercf:30219167
openfilemenucf:30219169
pythonvsded773:30223139
core-portspanel:30233467

These issues seems to be solved by setting an newer GCC and GCCLIB** in $PATH.


Methods implementing an interface marked as a step gives duplicate step definition error

Currently there is a technical limitation. Methods of an interface implementations marked as steps gives duplicate step error. Do you think  we should address this?

Which language runner did you check this with? Ideally the annotations should be on the implementation, and not the interface.

In Java, Yes the annotation is on the Methods of interface implementations. Since there are more than one, getting the duplicate step error.

I think the @Step annotation should be present on method implementation only, not on interface methods. Closing this for now. Please re-open if we need to consider this.


Default API base URL to SPA base URL

Same as https://github.com/sqlpad/sqlpad/pull/1138, but with backwards-compatibility.

@masch712 Looks like there are conflicts - I can merge once resolved

@rickbergfalk  conflict resolved

@rickbergfalk  Looks like I didn't resolve conflicts properly; still working on this


Improving / Exposing Git-Trees related features for Git-Trees API.

Additions to allow/improve Git-Trees API.

Exposes TreeEntry.mode through TreeEntry.Mode()
Fixes EntryMode consts (changed to hex)
Added revision parsing for trees (HEAD, HEAD~1, etc).

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@578ad8f). Click here to learn what that means.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master    #123   +/-   ##
========================================
  Coverage          ?   32.9%
========================================
  Files             ?      28
  Lines             ?    1781
  Branches          ?       0
========================================
  Hits              ?     586
  Misses            ?    1118
  Partials          ?      77

Impacted Files
Coverage Δ

tree_entry.go
67.67% <0%> (ø)

repo_tree.go
22.72% <0%> (ø)

tree.go
53.06% <0%> (ø)

Continue to review full report at Codecov.

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


Testing

Solution

Apply example_ynh

PR Status

[ ] Code finished.
[ ] Tested with Package_check.
[ ] Fix or enhancement tested.
[ ] Upgrade from last version tested.
[ ] Can be reviewed and tested.

Package_check results

An automatic package_check will be launch at https://ci-apps-dev.yunohost.org/, when you add a specific comment to your Pull Request: "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!"*

!testme

Own CI result for Revision: 800d11aba1c580cda88ad5def34165f1ae352d9e

!testme

Own CI result for Revision: 5143588a311069152a202a80de48d07fc5f5fca8


Chapta in faucet site does not work through Brave browser

What version of Wallet are you using?
0.0.1
What is happening?
Chapta won't open/doesn't show mission in Faucet website.

steps to reproduce
I load the wallet into the Brave browser. Once the address is created, I press the Faucet button on the wallet and get to the faucet page. Chapta doesn't open on the faucet page and I can't request funds for the test network.
How it should behave?
I was waiting for a button to run Chapta and order test ethers. The button did not appear and the task did not open.
What os are you seeing the problem on?
Windows Desktop
What browser?
Other
What is your browser version?
1.46.144

Thanks for the issue, this error is on our faucet project. We are currently working to improve it. You can keep track of the faucet repo https://github.com/FuelLabs/faucet/.


[dif] Fix autogenerated init unit tests

The first parameter of dif_*_init() functions is a mmio_region_t but autogenerated unit tests pass {.base_addr = dev().region()} instead of simply passing the return value of dev().region(), which is a mmio_region_t. Caught this while trying to measure off-target coverage using clang-13. I'm not sure why this builds without any warnings using gcc, could be a bug, at least the lack of any warnings.
Signed-off-by: Alphan Ulusoy<EMAIL_ADDRESS>

Applied the patch from CI logs. @timothytrippel, this could be due to a clang-format version mismatch but I feel like the initial version that I pushed looked correct to me. Can you take a look when you get the chance?


Game Crashes Upon Attempting to Create Cloned Map

Describe the crash
whenever I try cloning a map, the game will crash immediately after I finish naming my levels/level. i've redownloaded the latest beardlib from github, and the editor along with its package data (which shouldnt even be separate imo)
To Reproduce
just try creating a new cloned map lol
Crashlog
Application has crashed: C++ exception
...Lib-Editor-master/Classes/Project/ProjectLevelEditor.lua:168: attempt to index local 'inner_chain_level' (a number value)
SCRIPT STACK
clbk() @mods/BeardLib-Editor-master/Classes/Project/ProjectLevelEditor.lua:94
run_callback() @mods/BeardLib/Classes/UI/Dialogs/InputDialog.lua:53
hide() @mods/BeardLib/Classes/UI/Dialogs/MenuDialog.lua:183
pre_key_press() @mods/BeardLib/Classes/Managers/MenuDialogManager.lua:138
@mods/BeardLib/Classes/UI/MenuUI/MenuUI.lua:374

Trying to clone san martin bank seems to work fine, what map crashes exactly?

Reopen the issue if this still happens


Add no_prepared_statement to skip prepared statements

Some database/sql drivers do not support prepared statements, and we would like the option to be able to force sql_exporter to not invoke prepared context at all.
This PR adds no_prepared_statement to both metric- and query-config.

I would really like to be able to use this feature for something I'm working on!


heap_caps_check_integrity() with comprehensive heap checking enabled and 4MB spiram causes system pa (IDFGH-219)

I'm calling heap_caps_check_integrity() periodically from the main task. With 4MB spiram and comprehensive heap checking it looks like the heap_caps_check_integrity() is suspending interrupts or otherwise blocking execution. In my use case I'm using a timer to blink a cpu activity light and the blinking is erratic. Behavior not seen if I remove the call to heap_caps_check_integrity() or run on a system with less ram.
Possible to optimize the heap_caps_check_integrity() call to avoid these long delays? I looked but I'm unfamiliar with the code and nothing obvious stood out.

Hi @chmorgan,
I'm really sorry noone ever got back to you about this.
For a combination of thread safety and performance reasons, heap access happens in a critical section with interrupts disabled. If there are a lot of individual allocations in PSRAM (or "Comprehensive" heap checking is turned on) then it can take a long time to check using heap_caps_check_integrity().
Unfortunately there is no solution to this that doesn't slow down the performance of normal heap operations (i.e. we could use a different type of lock like a FreeRTOS mutex that didn't disable interrupts but then all heap operations would incur the overhead of taking/releasing the mutex.)
The expectation is that heap_caps_check_integrity() would normally only be called while debugging a heap issue. Is that the case for you?
Checking integrity in PSRAM can also cause a lot of cache thrashing (because many unrelated PSRAM addresses are read, usually enough to overhwelm the cache). So there is also a performance hit for any other parts of your firmware that use PSRAM.
I don't know if it's useful for your purposes, but changing the caps argument to check MALLOC_CAP_INTERNAL memory only will significantly improve performance. However this won't detect heap corruption in any PSRAM region.

Hi @chmorgan,
I'm really sorry noone ever got back to you about this.
For a combination of thread safety and performance reasons, heap access happens in a critical section with interrupts disabled. If there are a lot of individual allocations in PSRAM (or "Comprehensive" heap checking is turned on) then it can take a long time to check using heap_caps_check_integrity().
Unfortunately there is no solution to this that doesn't slow down the performance of normal heap operations (i.e. we could use a different type of lock like a FreeRTOS mutex that didn't disable interrupts but then all heap operations would incur the overhead of taking/releasing the mutex.)
The expectation is that heap_caps_check_integrity() would normally only be called while debugging a heap issue. Is that the case for you?
Checking integrity in PSRAM can also cause a lot of cache thrashing (because many unrelated PSRAM addresses are read, usually enough to overhwelm the cache). So there is also a performance hit for any other parts of your firmware that use PSRAM.
I don't know if it's useful for your purposes, but changing the caps argument to check MALLOC_CAP_INTERNAL memory only will significantly improve performance. However this won't detect heap corruption in any PSRAM region.


chore: Update CP4D to 4.7.3

Signed-off-by: Denilson Nastacio<EMAIL_ADDRESS>closes: #282
Description of changes:

Update CP4D to 4.7.3

Output of argocd app list command or screenshot of the ArgoCD Application synchronization window showing successful application of changes in this branch.

It looks like the workaround of using the OLM image will not work for CP4D 4.7.3.
The pre-sync-cp4d-cluster-setup Job is accusing this problem and there is no workaround for it at this moment:
cp4d-473.log.zip
...
TASK [utils : print preview check catalog cmd] *********************************
skipping: [localhost]

TASK [utils : Confirm existence of Catalog Source object "ibm-cpd-scheduling-catalog" in namespace "cpd-scheduler"] ***
ok: [localhost]

TASK [utils : Confirm the expect channel is found in the packagemanifest] ******
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: kubernetes.config.config_exception.ConfigException: Invalid kube-config file. No configuration found.
fatal: [localhost]: FAILED! => {"changed": false}

TASK [utils : fail] ************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Timeout of waiting for packagemanifest ibm-cpd-scheduling-operator of component ibm-cpd-scheduling-operator to be refreshed in namespace cpd-scheduler"}

PLAY RECAP *********************************************************************
localhost                  : ok=44   changed=9    unreachable=0    failed=1    skipped=63   rescued=1    ignored=0

+ result=1


Firefox import requires at least one saved password in Firefox

If you don't have at least one saved password in firefox, the import fails because login.json doesn't exist. This should probably be noted in the README somewhere.

I ran into the same error:
ffpass import < ~/Desktop/password.csv
Traceback (most recent call last):
  File "/usr/local/bin/ffpass", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/site-packages/ffpass/__init__.py", line 292, in main
    args.func(args)
  File "/usr/local/lib/python3.7/site-packages/ffpass/__init__.py", line 243, in main_import
    key = getKey(args.directory)
  File "/usr/local/lib/python3.7/site-packages/ffpass/__init__.py", line 72, in getKey
    row = next(c)
StopIteration

Maybe even a cleaner error message would be helpful

I think it would be complicated and unsecure to create the file myself. I'll put an exception.
Could you tell me if the "key4.db" file exists @spencerdcarlson? If not, I'll just check if the file exists.

I'm still getting an AssertionError instead of a friendly message:
python ~/git/ffpass/ffpass/__init__.py import --from /dev/shm/lp.csv
Traceback (most recent call last):
  File "/home/tbraunjones/git/ffpass/ffpass/__init__.py", line 346, in <module>
    main()
  File "/home/tbraunjones/git/ffpass/ffpass/__init__.py", line 337, in main
    args.func(args)
  File "/home/tbraunjones/git/ffpass/ffpass/__init__.py", line 278, in main_import
    key = askpass(args.directory)
  File "/home/tbraunjones/git/ffpass/ffpass/__init__.py", line 245, in askpass
    key = getKey(directory, password)
  File "/home/tbraunjones/git/ffpass/ffpass/__init__.py", line 89, in getKey
    assert row[1] == MAGIC1  # CKA_ID
AssertionError

@nocnokneo I don't know why you get this error, but it's not because your password database doesn't exist.
The code around your error looks like that https://github.com/louisabraham/ffpass/blob/master/ffpass/init.py#L84-L89
The problem is that no row verified the property assert row[1] == MAGIC1, which shouldn't be the case. If your password database is really empty, you should delete key4.db and logins.json.

Hm, I'm not sure what the explanation is, but as soon as I added a password
to Firefox, this error when away.

I think your database might just have been buggy...
Firefox might have recreated it. I can add a friendly message that asks to add a password.


Add change log for June release, include the alpha release logs also.

I have added change log of the backported PRs:
#2052
#2051
#2050
#2049
#2048
#2047
#2044
#2041
Let me know if any other PR is missing. This is possible if it was not tagged with "backport needed"
@jenshnielsen @astafan8  @GateBuilder

You will also need to add a link to the file from the index. Please also build the docs locally and check that they render well

all mentioned PRs were backported to v0.15.x branch. merging this once CI passes


Keep Cassandra storage working even if the annotations query is dropped

It should be possible to drop just the CONTAINS SASI and have Zipkin continue to start up.
(Trying to search by annotation will still ofcourse throw an exception, here a NPE)

Maybe we can ship the NPE as a Server 500 error with a substatus that indicates it's due to SASI being dropped? That could eventually be used in the UI to show a sane error message.

Maybe we can ship the NPE as a Server 500 error with a substatus that indicates it's due to SASI being dropped? That could eventually be used in the UI to show a sane error message.

Good idea. A IllegalStateException with an appropriate message is now thrown.

thx!


fix #25 Allow username entry during definition from quickpick

This PR fixes #25

@daimor I am retrospectively requesting a review of this from you in case the lack of review is what caused the 0.9.0 release CI step to fail.

The issue in changed settings, master branch is protected now. Workflow file have to be updated, and TOKEN variable with token of user with admin access have to be added

@daimor do you mean I need to add a personal access token under Secrets (and name the variable TOKEN)?

Yes, it will help
On Fri, 9 Oct 2020 at 21:33 Raj Singh<EMAIL_ADDRESS>wrote:

@daimor https://github.com/daimor do you mean I need to add a personal
access token under Secrets (and name the variable TOKEN)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/intersystems-community/intersystems-servermanager/pull/26#issuecomment-706339734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJH6W7PTI7ZG3XVJS7G2SDSJ5JPXANCNFSM4RIBL4HQ
.

--
Dmitry Maslennikov
Co-founder, CTO, Developer Advocate
https://caretdev.com/
https://caretdev.com
<EMAIL_ADDRESS>Twitter https://twitter.com/devcaret LinkedIn
https://www.linkedin.com/company/caretdev

@gjsjohnmurray I added a personal access token with the Secret name "TOKEN" to this repo. Hope I gave it the all the needed permissions.


Move applySchemaResolution check to a method

Simply moves the applySchemaResolution check to a method on ModelResolver.
This way we can configure behavior in a custom ModelResolver subclass by overriding the method.

Thanks!


Add combined_source_code field to database

Source codes:
GE = 1
HEX = 10
Map = 100
So can calculate unique combinations e.g. GE + HEX = 11, GE + Map = 101, GE + HEX + Map = 111

1872 map = 1000


IE11 issues

Windows 8.1. IE 11.
The board has the following problems:

The header area is distorted.
The switch project dropdown is broken.
Dragging cards does not work if cursor has been on any of the links on the card. You have to precisely pick an empty space inside the card.
While dragging, selection mode comes up and the whole swimlane of tasks get selected.
After dropping, the position of the card is not saved. Refreshing page shows the cards have not been really moved.

Header problem:

Drag problem:

Cards get into selection mode while dragging:

Are you sure that everything is installed correctly on your server? I cannot reproduce your issue with Win7 and IE11. I will try later with a Windows 8.1 virtual machine...
You must see a Javascript error somewhere in the console...
Do you have the same issue with the demo version of Kanboard, http://demo.kanboard.net/ ?

Found the problem. It happens when Compatibility View settings are turned on in Enterprise policy.
I have added this after  tag in Layout.php and it fixes the problem:

This meta tag is now added in the master branch, thanks.


fix(vscode): improve trigger reload config

#1539

Instead exposing a function, I think it's better to directly expose the array of config file list

fixed


It's WordPress, dangit!

It should be WordPress, not Wordpress. The community is pretty serious about this. :)
Fixes: https://github.com/MaxCDN/bootstrap-cdn/issues/668

Good catch, thank you! Merging releasing to our staging server and once @jdorfman +1's I'll release to prod.
Cheers!


Version: flutter 3.22.1 When developing flutter ios, after jumping to the next page and returning through the left gesture, the focus of the page input box cannot open the mobile phone keyboard

Steps to reproduce
Version: flutter 3.22.1
When developing flutter ios, after jumping to the next page and returning through the left gesture, the focus of the page input box cannot open the mobile phone keyboard
Expected results
Version: flutter 3.22.1
When developing flutter ios, after jumping to the next page and returning through the left gesture, the focus of the page input box cannot open the mobile phone keyboard
Actual results
Version: flutter 3.22.1
When developing flutter ios, after jumping to the next page and returning through the left gesture, the focus of the page input box cannot open the mobile phone keyboard
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

重复了，关闭


Update google-cloud-trace to 2.21.0

About this PR
📦 Updates com.google.cloud:google-cloud-trace from 2.3.7 to 2.21.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-trace" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-trace" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #300.


2-Category is in fact Bicategory

I was looking at Bicategory and realized that what is defined as 2-Category is in fact bicategory, as their difference is merely that in 2-Category equivalence between 1-cells is strict equality while in Bicategory such equivalence becomes natural isomorphism. the current definition of 2-Category lies in the later definition. I propose let's make it clear and rename it to Bicategory.
it appears that in order to define 2-Category in the sense of traditional CT, it requires to express strict categories and comparison for strict equality of functors, and that probably requires K.

I was thinking that that may have been the case. And it would sort of be if Cats as a monoidal category had completely trivial associator and unitors. And you are likely correct that strict equality of functors requires K.
I guess the issue here is that Cats is not strict.  To define 2-Category, one would have to define things over a strict version of Cats.
But note that https://ncatlab.org/nlab/show/1-category and https://ncatlab.org/nlab/show/strict+category seem to be inconsistent!  1-category has talks about 'equality' on Morphisms as the source of strictness, while the latter talks about equality on objects.

yeah at this point I won't rely on nLab for all explanations. I suppose it is good to find out what the literature says. that being said, since bicategory is a more accurate concept for the definition, the renaming can at least prevent further confusion.

Yes, please rename.
Also, I think it would make sense to create a PropCategory (better name? StrictCategory would be misleading) where we don't have Hom-Setoids but Hom sets with propositional equality.  Then 2-Category could be defined to be Enriched over that.  I can try to start formalizing that.

There's useful discussion at https://ncatlab.org/nlab/show/type-theoretic+definition+of+category

This particular issue is taken care of. Remaining issues are documented elsewhere.


"apt update" broken for QEMU stage 1

It appears #1917 is back in QEMU:
$ sudo build-rkt-1.25.0/target/bin/rkt --dns=<IP_ADDRESS> run --interactive --insecure-options=image docker://debian:8 --exec /bin/sh -- -c "apt update"
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
E: Unable to determine file size for fd 9 - fstat (2: No such file or directory)

Environment
Built with ./configure --with-stage1-flavors=kvm --with-stage1-default-flavor=kvm --with-stage1-kvm-hypervisors=qemu.
rkt Version: 1.25.0
appc Version: 0.8.10
Go Version: go1.7.1
Go OS/Arch: linux/amd64
Features: +TPM +SDJOURNAL
--
Linux 4.8.12-300.fc25.x86_64 x86_64
--
NAME=Fedora
VERSION="25 (Twenty Five)"
ID=fedora
VERSION_ID=25
PRETTY_NAME="Fedora 25 (Twenty Five)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:25"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=25
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=25
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy
--
systemd 231
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

Thanks for the report @tjdett - I'll take a look...

Hi @tjdett I believe this is because we have not merged #3475 yet... I reproduced the issue, and then took the current HEAD, merged that PR in and re-tried and the test worked (apart from I had to use the ubuntu image, as for some reason I could not download and convert debian:8 to an ACI...)
#3475 is pending the status of patches being pushed towards/merged to upstream QEMU - and I've just chased that to see if we have some progress there and hopefully get that PR merged.


test suite: eliminate bug class "stray processes after test exits"

Problem
Some tests leave stay processes behind after they exit.
This is the potential root cause for failed coverage-report generation, as well as other flakiness.
DoD
The Python test suite ensures that after each test function exit, there are no stray subprocesses left.
If there are any, the processes' argv are listed at WARNING level and the test fails, preventing the PR from being merged.
Related Issues
Work
### Implementation
- [ ] https://github.com/neondatabase/neon/pull/6270#issuecomment-1878842496
- [ ] https://github.com/neondatabase/neon/pull/6497
- [ ] https://github.com/neondatabase/neon/pull/6470
- [ ] https://github.com/neondatabase/neon/issues/6487
- [ ] https://github.com/neondatabase/neon/issues/6486
- [ ] https://github.com/neondatabase/neon/issues/6489

Update:

The cgroup approach bumped up against securiy concerns.
Putting on pause.

Paused until https://neondb.slack.com/archives/C059ZC138NR/p1707229781663129?thread_ts=1706265241.134019&cid=C059ZC138NR is resolved

With #8742 it would appear that for a single run, we would no longer leak processes, possibly affected by #8714.


Chern Insulator Examples (3 new models + minor improvements)

Hi Johannes,
I have some additions to the repository that others may find useful.

I have replaced external_flux.py from the advanced examples, with a "chern insulators" directory in the examples folder. In this folder, I include 3 (confirmed working) example chern insulators: the haldane model (https://arxiv.org/abs/1407.6985), the chiral pi flux model (https://arxiv.org/abs/1012.4723), and the generalized (C=3) Haldane model (https://arxiv.org/abs/1205.5792). For each of these we calculate the charge pumping and spectral flow, as before. The corresponding models are now in the models directory, for general use.

I have changed V=1 to V=0 in the Haldane model example, so that it exactly reproduces Fig.2.a,b) from the paper.
You can run each of these examples simultaneously - they should take ~30 minutes to complete with the current parameters (haldane, chiral pi flux, generalized haldane - in order of speed). You can also uncomment a line in the files if you want to plot the hoppings. For the chiral pi flux model, we observe charge pumping with a Chern number of 1, which argees with literature. For C=3 Haldane model, we observe a charge pumping of 3 unit charges, which corresponds to a Chern number of 3, also in agreement with the literature. In all cases, we observe spectral flow - as expected.
Note: For the cases, of chiral pi flux model and generalized haldane model, there are custom lattices included in the model file. One could argue that these custom lattices should be separate in the lattice directory. However, I think that they are not generic enough to be separated out. They merely serve as an example of how one can construct a custom lattice for a specific model.

I have added 4th and 5th nearest neighbors for the Honeycomb lattice because they are useful for people studying twisted bilayer graphene.

Please let me know if anything is unclear.
All the best
Bart

Thank you very much for these examples, they are great! :+1:
I requested a few minor fixes in a pull request to your branch. If you merge them, they will automatically appear hear.
Moreover, I feel like the model folder is getting a bit unstructured.
I would suggest to

combine the files fermions_haldane.py and fermions_haldane_C3.py into a single file called haldane.py (I don't think we need to mention the fermion explicitly...)
move the class definitions from fermions_pi_flux.py  directly into the examples/chiral_pi_flux.py file. They are very particular to this example, so I think it's fair to have them not as general models inside tenpy. (We could do the same for the FermionicC3HaltandeModel as well... But the general Haldane model for sure is usefull inside tenpy.models)

Finally, I'd like you to add a class doc-string to the model classes defined within tenpy.models.
These doc strings appear in the online documentation of the class (which appears on a page not containing the module doc-string). Hence the class doc string should at least reference the papers again such that the Hamiltonian becomes clear.

Thank you for the fixes in the pull request, and for the useful corrections. I have made all of the necessary changes now :-)
As I was making corrections, there were a few things that I noticed:

There is such a thing as a bosonic haldane model, and so we may want to keep the name "fermions_haldane.py" to keep with the convention of "fermions_hubbard.py" and "bose_hubbard.py". On the other hand, "haldane.py" fits with the convention of "hofstadter.py", which has both fermionic and bosonic cases within one file. Is the naming convention inconsistent at the moment?

Why in the class doc string of FermionicHubbardModel does it say Spin-1/2 fermionic Hubbard model in 1D ? Specifically, why the 1D? You can also use this in 2D on a cylinder, right? Otherwise, you could argue that all DMRG is in 1D.

I think that the staggered chemical potential in the Haldane model was actually not a typo, so I have changed it back. It is:

self.add_onsite(mu, 0, 'N', category='mu N')
self.add_onsite(-mu, 1, 'N', category='mu N')
I think that the 1 in the second line means that it is acting on the B site.

Thanks for implementing the requested changes! Regarding your comments:

That's a good point and indeed inconsistent, we should join the Fermi-Hubbard and Bose-Hubbard model into a single file hubbard.py. Since some people might be using it, we should keep it backwards compatible, though, and issue a warning about the movement. Similar as in the bose_hubbard_chain.py. That one should be adjusted as well...
That's a relict of the time when it was only defined in 1D. You're welcome to change it ;-)
The staggered potential is there in the haldane model right now, correct? We need it for the various programs.

As far as I see, the examples actually don't involve interactions, or do they? Should we mention this somewhere? The real power of DMRG is that everything still works if we add interactions.
One last thing: I think that the fourth- and fifth-nearest neighbors will not often be needed. So I'd suggest to instead just set them as self.fourth_nearest_neighbors = ... inside the Honeycomb.__init__ instead of introducing the extra keywords in the Lattice.__init__. Do you agree?

Done
Done
Yes, it's correct now

I have added an interaction term to all of the examples now. However, the default is still V=0, which is how they are intended to be run. As I mentioned before, unfortunately I cannot make it work with interactions...
Agreed, I have changed this.

Thanks a lot for implementing all this!

Glad that I could contribute something :-)
I just realized that I forgot to add "'JW', True" to the end of all my interaction couplings in "chiral_pi_flux.py", "haldane_C3.py", and "models/haldane.py". Does this matter? If so, could you add this on for me?

The interactions are N N terms and don't need an Jordan-Wigner string, adding it would make it wrong.
(And by the way, add_coupling is adding it if necessary, depending on the operators, so no, you don't have to add it manually)

Thanks for clarifying :thumbsup:


feat: add emarsys support

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

6 of 227 (2.64%)  changed or added relevant lines in 20 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.1%) to 14.299%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/provider/googletag/server.go
0
1
0.0%

pkg/tagmanager/web/variable/datalayervariable.go
0
1
0.0%

pkg/utils/structtag.go
0
2
0.0%

cmd/tagmanager/web.go
0
4
0.0%

pkg/provider/googletag/web.go
0
5
0.0%

pkg/provider/emarsys/server/template/emarsysinitalizationclient.go
0
6
0.0%

pkg/provider/emarsys/server/template/emarsyswebextendtag.go
0
6
0.0%

pkg/provider/emarsys/web/template/emarsysinitializationtag.go
0
6
0.0%

pkg/provider/googleanalytics/server/template/googlegtagclient.go
0
6
0.0%

pkg/provider/emarsys/web/tag/emarsysinitialization.go
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

cmd/tagmanager/server.go
1
0.0%

cmd/tagmanager/web.go
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-1.1%

Covered Lines:
302

Relevant Lines:
2112

💛  - Coveralls


AWS access credentials can not be found

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
db4nz94zrbxbj
AWS Region
us-east-1
Amplify Hosting feature
Deployments
Question
Hi,
Thank you so much in advance for taking the time to help me!
question 1:
I'm hosting my NodeJS app on Amplify with auto deployment via GitHub, but after I added a backend to my app (AppSync GraphQL, DynamoDB, and  Storage) and pushed the code changes to GitHub, Amplify build failed because of an access error states: "AWS access credentials can not be found" (screenshot-1 attached).
question 2:
I added a Lambda function to my app via command "amplify add function" to do some price calculation. I chose the "hello world" function. I then added an API Gateway (REST API) trigger to invoke the function, but I don't know how fetch data from the API endpoint from my app. I tried to use "await API.get(apiName, path)" but I got an error states that the url doesn't exist (screenshot-2, screenshot-3 attached). I also tried "await fetch(url, options)" but got an error says that "Origin http:localhost:3000 is not allowed by Access-Control-Allow-Orign. Status code: 200". However CORS is enabled on this API gateway endpoint. (screenshot-4, screenshot-5 attached).
question 3:
is it possible to fetch data directly from a Lambda function URL without having to trigger an API Gateway? if yes, would you please let me know how.
I would really appreciate any help.

Hi @atef-abdellatif, in order for your backend environment to be successfully built during the CI/CD process, you must ensure that your application has a service role attached. The service role gives Amplify permission to access your backend resources. Please review our documentation for how to add a role: https://docs.aws.amazon.com/amplify/latest/userguide/how-to-service-role-amplify-console.html

Thank you so much! I had totally forgotten to attach the role to my app. Appreciate it!

On Feb 14, 2023, at 12:54 AM, hloriana @.***> wrote:
Hi @atef-abdellatif https://github.com/atef-abdellatif, in order for your backend environment to be successfully built during the CI/CD process, you must ensure that your application has a service role attached. The service role gives Amplify permission to access your backend resources. Please review our documentation for how to add a role: https://docs.aws.amazon.com/amplify/latest/userguide/how-to-service-role-amplify-console.html
—
Reply to this email directly, view it on GitHub https://github.com/aws-amplify/amplify-hosting/issues/3303#issuecomment-1428877829, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2HQUI2B5JO3EK2ZVPHG4FTWXLCRVANCNFSM6AAAAAAUZ4NZEU.
You are receiving this because you were mentioned.


Firebase truthy

Codecov Report

Merging #15 into master will increase coverage by 9.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
+ Coverage   77.77%   86.95%   +9.17%
==========================================
  Files          12        4       -8
  Lines          99       69      -30
  Branches        8        3       -5
==========================================
- Hits           77       60      -17
+ Misses         21        8      -13
  Partials        1        1

Impacted Files
Coverage Δ

angular/src/app/navbars/navbar/navbar.component.ts

angular/src/app/navpages/page1/page1.component.ts

angular/src/app/navpages/home/home.component.ts

angular/src/app/navpages/main/main.component.ts

angular/src/app/app.component.ts

angular/src/app/navpages/page0/page0.component.ts

angular/src/app/navpages/auth/auth.component.ts

angular/src/test.ts

Continue to review full report at Codecov.

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


Visualizations: Include documentation on variable constraints in the “Learn more” link

using the WASH-b Kenya study, I made a box plot of LAZ (participant repeated measure entity) for each study arm (community entity). I'd like to overlay this by either "study timepoint" or "diarrhea in last 7 days" (both under participant repeated measure entity) but I can only select overlay variables in the community entity

Variable constraint documentation has been added, but it is out of date now that we are no longer inferring data shape. The text needs to be updated:

Moving this to failed qa for now because I made some changes to the text at https://github.com/VEuPathDB/web-eda/blob/variable-constraints/src/lib/core/components/docs/variable-constraints.tsx.
Danielle will review and submit the pull request.

@d-callan Now when I try to click on the "Learn more" link, I don't get the expected pop-up with the documentation on variable constraints.

its just worked for me on qa.restricted, and appears to have your updates there.. where did you try and what did you get?

it works for me too. @SheenaTomko please provide more info on how to recreate. thanks!

Closing this. Reviewed the page that Danielle provided a link for and the text looks good. Created a separate ticket for the issue with the pop-up not appearing (so far no one else has been able to reproduce)
https://github.com/VEuPathDB/EdaNewIssues/issues/162


Update IAM policy to allow node discovery

This PR updates our EKS IAM policy to allow Expel to query AWS for information on nodes for EKS clusters. We do this by listing nodegroups for an EKS cluster, identifying the associated AutoScalingGroups, and describing those groups to get the instances currently part of the node pool.

Ran Plan for dir: . workspace: default
Plan Error
Show Output
running "/atlantis/bin/terraform0.12.27 init -input=false -upgrade" in "/atlantis/repos/expel-io/terraform-aws-eks/2/default": exit status 1
There are some problems with the configuration, described below.

The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.

Warning: Provider source not supported in Terraform v0.12

  on terraform.tf line 3, in terraform:
   3:     aws = {
   4:       source  = "hashicorp/aws"
   5:       version = ">= 4.0.0"
   6:     }

A source was declared for provider aws. Terraform v0.12 does not support the
provider source attribute. It will be ignored.

Error: Custom variable validation is experimental

  on variables.tf line 23, in variable "prefix":
  23:   validation {

This feature is currently an opt-in experiment, subject to change in future
releases based on feedback.

Activate the feature for this module by adding variable_validation to the list
of active experiments.

Error: Custom variable validation is experimental

  on variables.tf line 44, in variable "stream_capacity_mode":
  44:   validation {

This feature is currently an opt-in experiment, subject to change in future
releases based on feedback.

Activate the feature for this module by adding variable_validation to the list
of active experiments.

Error: Unsupported argument

  on variables.tf line 53, in variable "stream_shard_count":
  53:   nullable    = true

An argument named "nullable" is not expected here.


Use device type display name instead of device name in g UI

Checklist

[ ] Tests have been written/updated (if necessary)
[ ] All tests are passing
[ ] Docs have been updated (if necessary)
[ ] Updated Linear issue to In Review

Description
In de .env file moet je zelf ook nog even de MANUAL_URL toevoegen, dus deze line:
MANUAL_URL="https://manuals.tst.energietransitiewindesheim.nl/devices/twomes-co2-occupancy-scd41-m5coreink-firmware"
Linked Issues
Additional context

Issue in pull request. New pull request is made. This pull request will be closed.


Api client rate limiting

This allows the client to be well behaved w.r.t. api request rate and also to retry in case of errors. I've tried to put in some sensible defaults, hopefully those do make sense given typical usage

rate limiting for clients based on golang rate.limiter (leaky bucket)
no bursting, clients can specify a max rps as a float which is applied uniformly

at the moment, clients can specify anything (ultimately the api will enforce limits). are there separate limits we should put on this?
default: 4 rps

in case of errors (connection error/5xx/429), the client will retry up to a specified number of times

this is also the default approach taken in the hashicorp retry http library, but I am unsure of this safety-wise. Thoughts??

each time retrying, the client will exponentially backoff (pow 2), starting from a specified minimum time up to a limited specified maximum

defaults: 3 retries, min delay 1 second, max delay 30 seconds (config accepts delays as integer seconds)

Just realized I missed one of the typos. @elithrar is this ok now?

Hi @elithrar, just checking if there is anything else which needs to be done here? Have all the changes been addressed?


[Feature Request]: Adding Persistent Bottom Sheet.

@GoldenSoju suggested on a comment in issue #201
One favor I would like to ask for:
Adding Persistent Bottom Sheet.
At the moment "Get.bottomSheet()" returns a Modal Bottom Sheet, but I was wondering if you could also add the Persistent Bottom Sheet ?
Modal: https://api.flutter.dev/flutter/material/showModalBottomSheet.html
Persistent: https://api.flutter.dev/flutter/material/showBottomSheet.html
Modal Bottom Sheet makes the rest of the screen inactive but
I would need the behavior of the Persistent Bottom Sheet where the user can interact with the rest of the screen when the bottom sheet is shown.
Obs: i am separating feature request in different issues so they can be put in the projects board
@jonataslaw if you don't plan to make this feature, tell me so this issue can be closed and removed from the roadmap
this can be checked here

It is an easy feature to implement, it will be implemented in the short term, after this roadmap:
https://github.com/jonataslaw/get_cli

Adding to projects sounds incredible to me, and it will become more organized than a simple roadmap. Thank you.

@jonataslaw I wanna contribute to this getx should i try to solve this issue

@mohak852 every contribution is very welcomed ❤

@jonataslaw I wanna contribute to this getx should i try to solve this issue

Any progress?

Added https://github.com/jonataslaw/getx/pull/604


Export runfiles environment for non-Windows tests.

Windows runfile support is sufficiently different that it will need a different mechanism.
Part of #182.

The fix for non-Windows is simple, but Windows runfile support is sufficiently different that it will need more work. Added a TODO for this branch.


[wip-markdown/mdx] - incorporate more MDX integration guide content

New or updated content

Incorporates content from the MDX integration guide that can be pulled into Docs proper, especially where usage with Markdown is (nearly) identical.
As this is long with lots of changes here and there, I recommend reading the two pages fresh at first, as "new" documents and respond to what might be missing or terrible.

Layouts page: https://deploy-preview-2054--astro-docs-2.netlify.app/en/core-concepts/layouts/

Now houses the layout-specific content that was on the Markdown/MDX content page and in theMDX integrations guide
Beefier sample that includes both accepting props and using components for Footer and BaseHead
Better surfacing of layout patterns, like one layout for .md, .mdx and .astro files; is now with Nested Layouts.
NOTE: Better organized page to eventually address docs Issue #1479 re: "What goes in my BaseLayout? What's good practice?" (todo)

Markdown/MDX Content page: https://deploy-preview-2054--astro-docs-2.netlify.app/en/guides/markdown-content/

Now has the more "simple" layout example, offloading all the content to the Layouts page
consolidated and organized with Markdown/MDX
examples for components and variables in Markdown, including assigning custom components in MDX
consolidated exported properties, and created sections for Markdown-only and MDX-only for the few that are not identical
included info re: MDX plugins alongside Markdown (since they work the same) and showing how they work together
Updated Syntax highlighting instructions for readability, and outdatedness

Fixes an anchor link in the tutorial after a heading change

(Follow up work will be to remove content from MDX integration guide, once we know what is living in Docs.)

Another pass at markdown-content incoming!

📄 I wonder if our first top-level heading, “Markdown and MDX Pages,” should be the umbrella for so much.
Attempted!

🔩 Relatedly, feels a little odd having so much MDX-specific stuff in this section. Maybe “Variables and Components” could be under a “MDX Features” subhead or something?
Attempted!

🧱 The code examples under “Importing Markdown” are doing a lot at once and it isn’t really explained. I’d lean towards making the initial sample ONLY about showing import and Astro.glob, show other features like MDX exports and frontmatter usage in dedicated examples with explanation below.

I think this is lighter/clearer now?

🗯 Speculation: might the items in “Exported properties” format better as an unordered list?
Done! Yoinked from the Layouts page to see if we like this better.

🔭 Big picture: should “Configuring…” come before “Importing…”?
Gut says no? Importing might be used more than configuring, since no config is actually needed... all the config is optional plugins.

✂ Definitely feel like the reading time example could be yoinked to somewhere else.
Still trying to figure out what to do with this.... worst case, it stays at the end.

Wondering if for search purposes repeating “in MDX” in each of the MDX-only subheadings is overkill: “Using Components” sounds very general, so might be worthwhile even if it’s repetitious.

I know, I've gone back and forth on this! I like shorter, more general names in the sidebar. BUT, the anchor links are useful when more specific (since the page is BOTH markdown and MDX)... I've honestly changed them so many times...  😅
Will revisit the code sample again. I think I gotcha now!

OK, see what you think of the latest code at "Importing Markdown"...

OK, I think this page might be ready for a more nit-picky review. (I'm sure I'll find more stuff, too.)

(Link check is NEVER gonna pass until we decide on headings, lol)

It's Fri-day Merge-Day!


pass ownProps to areStatesEqual

We have a use case when we need to use areStatesEqual and access ownProps at the same time. This PR solves the problem.
function compareStates(paths = [], a, b) {
    return paths.filter((path) => {
        const valueA = get(a, path);
        const valueB = get(b, path);
        return valueA !== valueB;
    });
}

const mapStateToProps = ({
    data: {
        campaign,
    },
}, { data: { id } }) => {
    const campaigns = getEntities(campaign, 'client_id', id);
    return {
        campaigns,
    };
};

export default connect(mapStateToProps, null, null, {
    areStatesEqual(prevState, nextState, { id }) {
        const paths = ['data.campaign.by.client_id.${id}.ids'];
        const differentPaths = compareStates(paths, prevState, nextState);
        const areEqual = differentPaths.length === 0;
        if (!areEqual) {
            console.log('[!] %s are not equal', differentPaths.join());
        }
        return areEqual;
    },
})(Client);

This was already discussed in #781

@timdorr it doesn't make any sense to me why you would not allow to access own properties in this method. The use case is exactly the same as the author you linked, and you're forcing me to run mapStateToProp which I do want to avoid. If your users are asking for it why is it so difficult? What's the argument against it?


Access control AD groups

Would it be possible to add a group instead of a specific user to limit the admin config? Docs are specific to user only. Would be great if this can be enhanced.

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

ID: baa62b58-ede2-2367-5b42-0d00b551c41f
Version Independent ID: 4a806bbd-886e-5061-192e-3c96998bb3b1
Content: Limit access to kubeconfig in Azure Kubernetes Service (AKS)
Content Source: articles/aks/control-kubeconfig-access.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@celamb4 Thanks for the feedback! We are currently investigating and will update you shortly.

@celamb4 We can assign the role "Azure Kubernetes Service Cluster Admin Role" to a group. Then the people who are part of that group can access.
@iainfoulds Please let us know about the possibility of adding examples for adding a group in the document.

Thanks for the feedback, @celamb4. As @jakaruna-MSFT notes, there's nothing specific to a user account here, it's assigning RBAC to a given object would could also (and potentially more commonly) be a group.
I'll add a note that the same process works for adding a group rather than user and how to get a group object ID. I'm hesitant to add a complete example as some people may not have permissions to create an Azure AD group to see it in action.
#in-progress

Tks @iainfoulds! I think just having an example with the group ID or stating it's supported should be enough. Agree that even retrieving the objectId of the group is out of scope.

Thanks @iainfoulds. i will assign this issue to you


Move RateLimits method to a service

I missed the RateLimits method in #2937. It should be moved to a service struct.
Docs are at rate-limit/rate-limit#get-rate-limit-status-for-the-authenticated-user, so according to our existing pattern, we should move it to a new service called RateLimitService and name it Get
Client.RateLimits should be marked as deprecated and its body should be updated to return c.RateLimit.Get(ctx)
This may be a candidate for "good first issue" with the slight complication of creating a new service.
/cc #2936

Hi @WillAbides, can I work on this?

Hi @WillAbides, can I work on this?

Thank you, @nhAnik ! It is yours.


🐛 Bug Report: GCP IAP Provider has wrong provider name in documentation

📜 Description
The docs refer to 'gcp-iap' as the provider string to use in config and on the proxied sign-in page. However, using that will result in a 404 result from the auth-backend. Using 'gcpIap' will succesfully work.
👍 Expected behavior
It should refer to 'gcpIap' as the provider id
👎 Actual Behavior with Screenshots

👟 Reproduction steps
Include this in your backend index.ts
backend.add(import('@backstage/plugin-auth-backend-module-gcp-iap-provider'));
Spin up backend locally
Visit http://localhost:8080/api/auth/gcp-iap/refresh locally, it will return a 404.
Visit http://localhost:8080/api/auth/gcpIap/refresh locally, it will return a 401 as it finds the auth plugin
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

The issue seems bigger than a simple docs fix.
Following the plugin config schema I tried this config
auth:
  environment: production
  providers:
    gcpIap:
      production:
        audience: ${GCP_IAP_AUDIENCE_CODE}
        signIn:
          resolvers:
            # typically you would pick one of these
            - resolver: emailMatchingUserEntityProfileEmail
            - resolver: emailMatchingUserEntityAnnotation

Backstage fails to start with "ForwardedError: Plugin 'auth' startup failed; caused by Error: Failed to initialize gcpIap auth provider, No sign-in resolver configured for proxy auth provider 'gcpIap'".
The following seems to work, despite not being ok with the schema
auth:
  environment: production
  providers:
    gcpIap:
      production:
        audience: ${GCP_IAP_AUDIENCE_CODE}
        signIn:
          resolvers:
            # typically you would pick one of these
            - resolver: emailMatchingUserEntityProfileEmail
            - resolver: emailMatchingUserEntityAnnotation
      audience: ${GCP_IAP_AUDIENCE_CODE}
      signIn:
        resolvers:
          # typically you would pick one of these
          - resolver: emailMatchingUserEntityProfileEmail
          - resolver: emailMatchingUserEntityAnnotation

This gives a 401 error, ""Google IAP token verification failed, Error: Wrong recipient, payload audience != requiredAudience"" - I guess this will be an error on my end.
I tried to figure out where the issue might be, and tested
auth:
  environment: production
  providers:
    gcpIap:
      audience: ${GCP_IAP_AUDIENCE_CODE}
      signIn:
        resolvers:
          # typically you would pick one of these
          - resolver: emailMatchingUserEntityProfileEmail
          - resolver: emailMatchingUserEntityAnnotation

This failed as well with 404 error. (If I remember correctly)
I checked out the codebase, and it seems to be too complex for me to come up with a fix.

Ah yep the config schema is wrong, there's no authEnv for proxy providers. It should be flattened to accept the values at the provider root as you are passing them. Would you like to contribute a fix @nagyv? 🙏

This is fixed now. I bumped to 1.30.1 and removed the workaround, and it worked.


Feature requests: custom window background color, custom assist tick sound file, drag the receptors around, move the info pane around

interested in trying out SMEditor to see if it suits my needs. So far, am very impressed with its customization options
been setting up the desktop app version the way i like it, but there are a few things i can't seem to be able to do but would like to:

be able to change the general window background color
set my own assist tick sound file
be able to drag the receptors around the window like in AV
be able to move this pane around so it isn't covering the notefield, or be able to hide it entirely with a toggle like how the top bar with the Zoom/Playback/Scroll/Speedmod etc options can be hidden:

looking forward to seeing this editor grow even more than it already has

Doing some work


Tidy up comment in database_builder.rs

Small edit I noticed in the docs.

@extua thank you for this fix. Can you rename the commit following the conventional commits?
docs: tidy up comment in database_builder.rs

@extua thank you for this fix! Can you rename the commit following the conventional commits?
docs: tidy up comment in database_builder.rs

Thanks! I've changed that commit message now.

@extua thanks, your changes have been accepted and will be included in this weekend's release :)

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

0.8.0
GitHub release

Your semantic-release bot :package::rocket:


Support an additional folder for 'blog posts'

Hi,
I've just implemented PicoCMS. I've really enjoyed the simplicity in setting it up and it's very nearly perfect for my current requirements.
I really wanted a feature for separating out static content and blog posts. Blog posts can be numerous and I really wanted the flexibility of storing them in a separate location. Additionally I'd enjoy the benefit of parsing them separately from static pages from within my theme templates.
As a first time contributor, I welcome your feedback. If the changes interest you but need further work, I'm happy to take that on board and revise my fork. Otherwise, if this is not something you wish to incorporate into PicoCMS, I'll understand the rejection.
Best wishes
Dan
aka biscuitNinja

I realise now there's actually already a plugin for this
https://github.com/mcbSolutions/Pico-Plugins/tree/master/mcb_Blog


ui-select-no-choice doesn't work for multiselect

Bug description:
while using ui-select-no-choice directive it doesn't apply for multiselect mode (bootstrap theme).
Version of Angular, UI-Select, and Bootstrap/Select2/Selectize CSS
Angular: 1.4.2
UI-Select: 0.17.1

I am getting the same problem occur, but when using the select2 theme. Setting the theme to "bootstrap" solves this for me.


CLI installer inappropriately updates my bash_profile

I've run the amplify installer script a few times. Now, in my ~/.bash_profile I see:
jhwill@9801a7a9c383:~$ cat ~/.bash_profile
. ~/.bashrc

# Added by Amplify CLI binary installer
export PATH="$HOME/.amplify/bin:$PATH"

# Added by Amplify CLI binary installer
export PATH="$HOME/.amplify/bin:$PATH"

# Added by Amplify CLI binary installer
export PATH="$HOME/.amplify/bin:$PATH"

# Added by Amplify CLI binary installer
export PATH="$HOME/.amplify/bin:$PATH"

It should either not update my dot files, or it should ensure only one entry is present.

Thanks for reporting this 👍

Thanks for reporting this 👍

cc @edwardfoyle

cc @edwardfoyle

@jamesonwilliams Once you have installed the packaged CLI once, you should use amplify upgrade to install newer versions. This command will not add duplicates to your bash_profile. However, we can add some logic to prevent the duplicates

@jamesonwilliams Once you have installed the packaged CLI once, you should use amplify upgrade to install newer versions. This command will not add duplicates to your bash_profile. However, we can add some logic to prevent the duplicates