Variable named await

Describe the bug
technically await is not a reserved keyword so you should be able to use it as a variable name.  However swc throws when you do, I can't easily change this code because it's a dependency
Input code
function timeout(await) {
  // Do stuff
};

Config
{
  "jsc": {
    "parser": {
      "syntax": "ecmascript",
      "jsx": false
    },
    "target": "es2021",
    "loose": true,
    "minify": {
      "compress": false,
      "mangle": {
        "toplevel": true,
        "keep_classnames": true,
        "keep_fnames": true,
        "keep_private_props": true,
        "ie8": true,
        "safari10": true
      }
    }
  },
  "module": {
    "type": "es6"
  },
  "minify": false,
  "isModule": true,
  "env": {
    "targets": "",
    "bugfixes": true
  }
}

Playground link
https://play.swc.rs/?version=1.2.221&code=H4sIAAAAAAAAA0srzUsuyczPUyjJzE3NLy3RSCxPzCzRVKjmUlDQ11dwyVcoLilNS%2BOqteYCAOqwK8MrAAAA&config=H4sIAAAAAAAAA2VPSQ7CMAz8i889AAeE%2BgfegEyYVIFsitOKqsrfSUsLQpxsz2KPJ7qLonaiyEmQ5k5Gn%2FlJLUE5FpVMzNRUWYU0W0FpKHPqkGeJHHaHfaVtCAJqc%2BrRkDPe6HHepYKLCSKrtVLsO4uZyiFaDLCb6QHEi7Is4tlBfmD9D8VkBs6oNcQPY3DaWmHNyex377mUmtqFW7%2FeHiOW9Ecq37hrRCPnVfjeBD8snuXneorqu9e%2B0%2Ba5RSrlBScipgBHAQAA
Expected behavior
I would expect it to allow await as a parameter name.
Actual behavior
No response
Version
1.2.221
Additional context
No response

No you are using es module and await is reserved in a strict mode.


Some documentation for algorithm/implementation

This is the best dawg implementation I can find on the net. There seem to be quite some tricks in the implementation of the tree storage (various bit twiddlings and having the guide class). I would feel much more comfortable to base code on this if there would be some basic docs explaining the rough ideas.

I think I should contact the original author.


Error with the decl'HDF5 plugin in parallel

In GitLab by @tpadioleau on Aug 4, 2022, 14:50
Using the decl'HDF5 along with the MPI plugin, I sometimes get errors like:
[14:43:36][MPI 000000][PDI] *** error: Error while triggering event 'dump': System_error: Filename collision data_000000000.h5': Cannot delete old file.
I am using the replace_and_warn policy. It seems to work well when there are no existing files or with other policies.

In GitLab by @tpadioleau on Feb 6, 2023, 10:04
created branch 428-error-with-the-decl-hdf5-plugin-in-parallel to address this issue

mentioned in commit 0b1937bf3debbb165d8b921aa6b6eeea187cbb2c


add codeclimate badge to readme

if anyone also wanted to know, idk how to get there via the gui but figured out that going to /badges works

Thanks for doing this! Your code climate failure will be fixed in #504 so this is OK to merge.

Ain't no thang, Preston. Woohoo! 🙌 🙌 🙌


Cache Task Instructions - Value cannot be null. Parameter name: securityNamespace

Following instructions on this page on a multi-stage build, I got the error Value cannot be null. Parameter name: securityNamespace on the build.  I found this issue: https://github.com/microsoft/azure-pipelines-tasks/issues/11291 and added a securityNamespace: cache input for the cache tasks and everything worked as expected.

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

ID: 77c20289-dab2-7a6e-4f63-4b30eaff2c71
Version Independent ID: d75cc196-90c1-8291-9907-ff405bde4edf
Content: Pipeline caching - Azure Pipelines
Content Source: docs/pipelines/release/caching.md
Product: devops
Technology: devops-cicd-release
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

@ramiMSFT @msebolt can you please look into this and reopen the issue? I encountered the same issue today
#please-reopen


Use traject's ISO 639-3 language handling for

Background
Bibdata has some custom code to index ISO 639-3 languages into the language_facet field:
https://github.com/pulibrary/bibdata/blob/6f56074913e1e8f210008304c8031e05dbd3ada0/marc_to_solr/lib/traject_config.rb#L739-L741
However, since https://github.com/traject/traject/pull/293 was merged, the traject marc_languages macro includes ISO 639-3 codes, making this redundant.  As of April 11, 2023, there hasn't been a new release of traject, but when it has been released, we should do the following.
Success criteria

Bibdata uses a traject release that includes https://github.com/traject/traject/pull/293
The redundant code is removed from bibdata
All existing tests for the marc_languages field still pass

When there is a new traject release that includes https://github.com/traject/traject/pull/293 then update traject and remove the code we've added in bibdata.


Recovery failure with barman due to max_connections

CNPG version: 1.20.1
I'm trying to recover from a backup that was produced with barmanObjectStore but recovering the primary instance fails.
In postgresql.parameters.max_connections I use a value of 40, and because of that the following error is produced:
"message":"hot standby is not possible because of insufficient parameter settings","detail":"max_connections = 10 is a lower setting than on the primary server, where its value was 40."
Meaning that recovery from a backup must use at least as large max_connections as what was used by the backup.
Tracking down the code I figured that the max_connections=10 setting comes from pg_controldata(src), which strictly overwrites the user setting.
I guess the user should be able to override max_connections when running a recovery to match that was backed up?
I've checked and /var/lib/postgresql/data/pgdata/custom.conf indeed shows max_connections=10.
What's confusing though is that running pg_controldata displays "max_connections setting: 40" so I'm confused where that 10 comes from.
The logs show this: {..., "msg":"enforcing parameters found in pg_controldata","parameters":{"max_connections":"10","max_locks_per_transaction":"64","max_prepared_transactions":"0","max_wal_senders":"10","max_worker_processes":"32"}}

@phisco @gabriele-wolfox @mnencia
I see that this logic was contributed by you in this commit
Unfortunately I couldn't find any explanation why it's in place. Why do we force-override the max_connections and other settings?

After more investigation I found the culprit: there was a max_connection change from 10 to 40 after the base backup was written, so that change is only present in the WAL.
When CNPG initializes the config, it uses pg_controldata to figure the max_connections setting. According to the docs "pg_controldata prints information initialized during initdb", so that's why it returned 10 and then CNPG uses that value to override the setting from the postgresql.parameters stanza.
When barman-cloud-restore gets to the WAL entry of increasing max_connections, it pauses with the error message shown above.
The fix to this problem is to not overwrite the max_connections setting with the value from pg_controldata. If we used the user-specified max_connections setting, things would work fine as the user can pick a high enough max_connections.
My solution for restoring the data was to manually start a postgresql server on a clean machine, do the barman-cloud-restore (had to override restore_command and archive_command in postgresql.auto.conf) and make a pg_dump of the database. Then in CNPG I created a clean db using initdb and pg_restored the data into it using kubectl exec.

@gsimko can you be more explicit with the steps that brought you to this situation?
E.g.:

created first cluster with max_connection yy
backed up first cluster to bucket xxx
set max_connections to zz on first cluster
created second cluster restoring from bucket xxx
…

AFAICT the following steps led to this situation:

created cluster with max_connection=10
created base backup in bucket X
changed max_connection to 40
wrote WAL logs to bucket X
created second cluster restoring from bucket X
initialization of the cluster primary pod failed

The reason for the failure is that the new cluster is initialized with max_connection=10, but when the restoration process gets to the WAL log with max_connection=40 it stops due to not supporting such an increase.
Hope that helps!

But the error message you shared is saying: max_connections = 10 is a lower setting than on the primary server, where its value was 40. So, it looks like it’s trying to go back to 10 for some reason
The second cluster was created with max_connections set to 10 or 40?

On the second cluster I set it at 40.
The reason why it uses 10 - and that's the actual bug - is because CNPG internally overrides the user setting by reading the max_connection setting from pg_controldata, which returns the value at the time when the table was created.

Maybe I got it, it’s set to 10 from the backup, then at some point replaying WALs, it’s set to 40, but we still try to force it back to 10 because pg_controldata says so. I’ll try to reproduce it, thanks!


Nginx friendly URL rewrite issue

Hi,
I'm having issues getting this to work when using the friendly URLs option on nginx with the following rule:

location` /community {
try_files $uri $uri/ /community/index.php;
}

Any help will be appreciated.
Regards,
FragDeluxe Community

Old rewrite rules:

    location / {
        try_files  $uri $uri/ /index.php;
    }
    location ~^(/page/).*(.php)$ {
        try_files  $uri $uri/ /index.php;
    }

New rewrite rules:
    location / {
        try_files $uri $uri/ /index.php?$args;
    }

That was what was provided by another plugin user.

;P seems to be working fine for me

Hi, thanks for the response but unfortunately I wasn't able to login after making the change.
I'm not too sure what's wrong, most likely something on my end if the above rule is working for you.

try restart nginx after, it's necessary :)

Hi, I did try restarting nginx and it didn't work.
I just tried again now, gave it a couple of restarts and now it's working.
Thanks for your help, this issue is now resolved.


Re-activate the public ("Dictionary") view

We'd like to start using the original Dictionary view again that is accessible to anyone without logging in, but for the moment:

only for NGT, not ASL
only display (and allow searching for) signs that have the tag "Radboud sign"

start using the original Dictionary view again that is accessible to anyone without logging in

When should you see what? I propose: always the detail view when allowed, otherwise the public view. In the detail view is a button to also see what the public view looks like.

only for NGT, not ASL

Okay, so this will be a setting in the settings file.

only display (and allow searching for) signs that have the tag "Radboud sign"

I think we have a field called 'In web dictionary' for this purpose, I propose to use it for this :). Shall I write a script that makes sure everything with the tag Radboud sign is in the web dictionary, and the rest is not? Or do you think we would like to do this more often, and shall I create a feature that allows users to activate and deactivate groups of signs based on their tags?

Proposal on when to see what: agreed.
Proposal for using web dictionary: of course! Thanks for reminding me. Let's just script the Radboud tag to a checkmark for now, and wait with the other feature, I doubt we'll do this again.

Done:

All glosses are now NOT in the web dictionary, unless they had the tag Radboud sign
You no longer need any permission to see the public view of sign if it's in the web dictionary. If you're trying to visit the public view of a sign you're not allowed to see (for example because you're logged out and it's not in the web dictionary), the view does not show any data but instead displays the message 'you're not allowed to see this sign'.

Not done yet:

Normally when you're visiting a page and you're not allowed, you are redirected to the login page when not logged in, or not shown anything when you are. An exception needs to be added to this behavior so that you are redirected to the public view instead when (1) the page was the detail view of a sign and (2) this sign is in the web dictionary.

I think we still need to allow non-logged in users to search / list signs; how would they find sign entries now?
1b) Searching should only be allowed through the two fields in the menu bar. So not using the list view-with-search-fields.
It would be good if non-logged in users were not bothered with entries they cannot see. If someone pastes in a direct link to a detail view of a 'not in dictionary' sign they should see the log in page, but otherwise search results should not refer to any other entry.

I think we still need to allow non-logged in users to search / list signs; how would they find sign entries now? 1b) Searching should only be allowed through the two fields in the menu bar. So not using the list view-with-search-fields.

Aha, so the whole user experience should be accessible, not just the public view :). As far as I can oversee it now, this adds the following items to my to do list:

Make search available without any permissions.
Only show the more complicated search options when you have the permissions.
In the search results, only mention the ones you have permissions to view (that is: if you don't have permission to view detail views, only mention the glosses in the web dictionary).

If someone pastes in a direct link to a detail view of a 'not in dictionary' sign they should see the log in page

This sentence made me realize I'm a bit confused about what should happen when, and when I'm confused I make tables :). I think this is how we want to do it:
When visiting the URL of a detail view:

Gloss in web dictionary

Gloss NOT in web dictionary

Permission for detail view
No permission for detail view
Permission for detail view
No permission for detail view

Logged in
Show detail view
Redirect to public view
Show detail view
Show nothing

Not logged in
Redirect to public view
Redirect to public view
Redirect to login
Redirect to login

When visiting the URL of a public view:

Gloss in web dictionary

Gloss NOT in web dictionary

Permission for detail view
No permission for detail view
Permission for detail view
No permission for detail view

Logged in
Show public view
Show public view
Show public view
Show public view

Not logged in
Show public view
Show public view
Redirect to login
Redirect to login

Done:

Some changes to the second table
Made the redirects work as in the table.

@Woseseltops your tables are awesome! It is so easy for everyone to understand the issue completely very fast. Keep up the good work. :+1:

Changes:

The search page is available without having to log in
The 'form your query' panel is only available if you have the rights, otherwise you don't see it
If you don't have enough rights, there will be an extra (invisible) search filter that filters out all signs not in the web dictionary

To do:

I just noticed that you still get permission problems when using the search fields in the menu bar
The 'total number of signs' mentioned on the page is still the overall total number... maybe we want to display the total number of signs that are available to you ?

Also fixed: 'I just noticed that you still get permission problems when using the search fields in the menu bar'

So this question is open for @ocrasborn : The 'total number of signs' mentioned on the page is still the overall total number... maybe we want to display the total number of signs that are available to you ?

Yes, that would be good. So that would mean 'all sign entries' for users that are logged in, and 'all signs that have the In Dictionary checkmark' for users that are not logged in. At least for now: we will need to revise this when we start distinguishing multiple datasets for different languages, see e.g. #223
(part of https://github.com/Signbank/NGT-signbank/issues?q=is%3Aopen+is%3Aissue+milestone%3A"Multiple+Languages+%2F+Datasets")

See mail from @vanlummelhuizen : the present version of the code also restricted the access for users that were logged in, so he reverted to an older version of the code earlier this week.

Already fixed that yesterday morning (see commit #9631d7b), but forgot to let anyone know about it :)

Done @ocrasborn ?


Can't use custom CA with encrypted key

I have a password on my CA private key (obviously), when trying to use it with:
kube-aws render credentials --ca-cert-path=/root/ca/pki/ca.crt --ca-key-path=/root/ca/pki/private/ca.key

It gives an error.  The error tends to vary slightly - I'm guessing because the system is trying to read an encrypted file as a regular file, so is interpreting essentially garbage data and so will throw whatever validation failure comes up first.  This is the current error:
Generating credentials...
-> Parsing existing TLS CA
Error: failed parsing ca key: asn1: structure error: length too large

Speaking of which, my CA is restricted to the root account for more security, but it would be nice if the generated stack was not owned by the same user.  I.e. if there was a way to specify the owner of the output.

OK, it turns out this causes a validation to fail, as the keys are not encrypted until later for some reason.

Generally CA wouldn't allow key to be exported. Existing CAs can issue certs for you, but CA key is not available to users.

That is the problem.  The tutorial here: https://kubernetes-incubator.github.io/kube-aws/getting-started/step-2-render.html talks about so that's what I was doing.  If there's a way to encrypt everything without using that command, I couldn't find the documentation.


edupont04 from OPS portal: Merge from master to live

Docs Build status updates of commit a20bac6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/whats-new/version-october-2020.md
:bulb:Suggestion
View
Details

dynamics-gp/TOC.md
:white_check_mark:Succeeded
View

dynamics-gp/terms/lifecycle.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/1099-misc-form-updates.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/additional-user-defined-fields-in-general-ledger-transaction-entry.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/automate-financial-full-reconcile.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/bulk-edit-smartlist-columns.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/copypaste-purchasing-transactions-from-excel.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/dba-for-vendor.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/disable-print-dialog-when-printing-word.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/enable-self-service-user-type-access-user-preference.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/exportimport-stock-counts-excel.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/form-1099-nec-now-supported.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/human-resource-social-security-number-mask.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/import-credit-card-transactions.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/match-excel-copy-and-paste-decimal-places-currency-setup.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/maximum-print-output-screen.md
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image1.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image10.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image11.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image12.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image13.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image14.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image15.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image16.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image17.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image18.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image19.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image2.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image20.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image21.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image22.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image23.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image24.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image25.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image26.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image27.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image28.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image29.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image3.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image30.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image31.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image32.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image33.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image34.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image35.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image36.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image37.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image38.png
:white_check_mark:Succeeded
View

dynamics-gp/whats-new/media/image39.png
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

dynamics-gp/whats-new/version-october-2020.md

Line 3, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn about enhancements that were added to the product in this release of Dynamics GP.' is duplicated in 'whats-new/version-october-2019.md(3,14)', 'whats-new/version-october-2020.md(3,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Create Text to ASCII AI Agent

📝 Create Text to ASCII AI Agent
Encode Text to ASCII Code: Encode the given text using ASCII encoding.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information

Dear @zionsenpai , we found you have called {{text}} in your prompt. But the variable name you defined is input. Could you please update it and reply to this comment?
For your reference:


Viet - fix bugs found during my testing

Description

Types of changes

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have checked that unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

This PR includes bug fixes for: Declaration checkbox and values not load properly for PCF and Change request when we navigate between these twos, MTFI current fee verification page is not saved when we hit Next (because beforeRouteLeave for that page is not working), facility name in Change request history table were missing after I updated the backend mapping in my last PR


[master] Auto-update dependencies

Produced via:
./hack/update-deps.sh --upgrade && ./hack/update-codegen.sh
/assign houshengbo
/cc houshengbo

We have another PR merged to sync-up and upgrade the deps.


Allow rebuild command with user created snapshot

Hi, the same way as https://github.com/smdahlen/vagrant-digitalocean/pull/189 ,
Allow Rebuild droplets from user created droplets.

I don't want to be rude, but any progress on this from the maintainers? Without this rebuild is broken for user defined images, and unfortunately vagrant destroy && vagrant up can't be used as a workaround either, as destroy does not wait until the droplet is actually destroyed, as I mentioned here: https://github.com/smdahlen/vagrant-digitalocean/issues/213

thanks @seth-reeser !

thanks.

You got it! Working on releasing on RubyGems now.


Running Functional Threshold Pace Setup

It seems like in the new beta (6.4.0) from 2018/7/7 the conversion from metric to imperial got backwards.
My slow pace of 5:30/km as a reference (entered as 330 sec) is now being converted to 3:25/mi. While that would be nice, it's not even close to reality! It should convert to about 8:52/mi.

Just restart browser to get 6.4.1 ;)
Or force update ;)
Le jeu. 12 juil. 2018 à 22:24, claudermilk<EMAIL_ADDRESS>a
écrit :

It seems like in the new beta (6.4.0) from 2018/7/7 the conversion from
metric to imperial got backwards.
My slow pace of 5:30/km as a reference (entered as 330 sec) is now being
converted to 3:25/mi. While that would be nice, it's not even close to
reality! It should convert to about 8:52/mi.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thomaschampagne/stravistix/issues/630, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAJRpT6Z_pnzozIaOCAXqDTSmYK0Yyagks5uF7CZgaJpZM4VNqUB
.


Flash BeagleBone Black with Driver that takes in a word and WPM rate and flashes the LED

DoD: BeagleBone Black flashed and video of LED's flashing "I love embedded programming"

https://youtu.be/laY0UJMuGS0


Custom 404.html not work for directory!

Hi!
When I request a non-existence directory, it returns your default 404 page instead of my 404.html page.
And it also returns your default 404 page instead of my 404.html when I request an existing directory which don't have an index.html in there.
Please fix it!
Thanks very much for your free dropbox hosting.

@cuongthm fixed! thank you for finding this bug.


Disable all blueprint functionality behind #ifdefs

On a review of the current OSVR-Unreal blueprint functionality, it has become apparent that there may be some design issues, such as only supporting a pre-determined list of paths for some blueprint callable functions. Before too many people start to rely on those functions, we should disable them until a more thorough review and perhaps redesign of the blueprint library can be done.

Implemented in https://github.com/OSVR/OSVR-Unreal/pull/59
I decided to move the deprecated code to /Archive instead of wrapping the functionality in ifdefs. Cleaner that way, and avoids issues with the unreal header tool.

Does this mean, that if I used OSVR Blueprint nodes get data from our motion capture system via VRPN configuration, that this won't work anymore? Do I have to use C++ now, which I know very little about?

I kept the code around in /Archive just in case people still need it. However, there is some code I had to comment out in OSVREntryPoint.cpp, so reopening this issue to wrap the disabled code in a flag to make it easier for people to continue using the BP API.
When this is done, you should be able to copy the code from /Archive back into /OSVRUnreal in your local copy (I kept the same directory structure to make it easier) and set a flag to enable it.

@Vaquero84 OK, I made it a little easier to re-enable the blueprint API. See the note at the end of Documentation.md: https://github.com/OSVR/OSVR-Unreal/blob/master/Documentation.md

Thank you very much!


[TF-TRT] CUDA Lazy Loading Warning Filtered

Add an extra substring to filter CUDA Lazy Loading Warning Messages in TRT 8.5

@bixia1 for review


Not working with Discord 0.0.12 on Ubuntu 20.04.01 LTS

It doesn't throw any errors. It just doesn't show up. Any ideas?

Hello, please check in the plugin settings (File -> Settings -> Discord|File -> Settings -> Other Settings -> Discord) if you do have any red boxes showing up, the text in those red boxes (if any) should tell you what's going wrong.
If you do have difficulties figuring it all out I invite you to join the discord server where can can give further help easier.

Oh. I see the issue now :/


[18.09] cups: add patch for CVE-2018-4700

Motivation for this change
Resolves https://github.com/NixOS/nixpkgs/issues/60106
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

(yeah I know but I have sympathy for people stuck behind for one reason or another - thanks)


BUG-Navbar lov ordering

Description
I have an app with multiple pages and I'm looking to add a navbar element, which automatically uses the pages registered if no list is given. When I use the following code:
<|navbar|>
it seems to order the pages alphabetically, which does not work for my use case (my pages are Home, Forecast, and Parameters where Home always needs to be first obviously, but at the moment Forecast automatically takes the first spot.
Functionally, this navbar works fine: clicking each element opens the relevant page in the same tab, and the current page is always highlighted correctly.
What I tried to do to force the order was to use the lov parameter, like so:
<|navbar|lov={[("home","Home"), ("forecast","Forecast"), ("params","Params")]}|>
This fixes the order issue, but introduces some weird quirks in functionality:

The current page I'm on is not highlighted in the navbar (it's always Home that appears selected)
Clicking any page via the navbar opens it in a new tab (the documentation says this will happen if the IDs begin with http, but that is not the case here)

How to reproduce
This is how my pages are registered:
from pages.params import params_page
from pages.forecast import forecast_page
from pages.home import home_page

pages = {
    'forecast' : forecast_page,
    'home': home_page,
    'params' : params_page
    }

Gui(pages=pages).run(async_mode="threading",use_reloader=True, debug=True, watermark="", dark_mode=True)

My app setup is a main.py file (with the above lines + other functions that are not relevant), and a pages folder with pages\forecast.py, pages\home.py and pages\params.py all imported into the main file as shown.
Expected behavior
A navbar with the intended forced order of items, that updates to highlight the current page, and does not open pages in new tabs.
Runtime environment
Please specify relevant indications.

OS: [e.g. Linux, Windows] and version - Windows 10
Browser: [e.g. Chrome, Edge, Safari] and version - Chrome 108.0.5359.125 (Official Build) (64-bit) (cohort: Stable)
and any other relevant information.

I'm aware I might be using the navbar parameters incorrectly, so would be great to get some help on how I can basically force the order of items without changing any of the functionality - thank you!

Hi Aazim,
and thank you for your feedback.
I just gave this code a try:
from taipy.gui import Gui

pages = {
    "/": "<|navbar|>",
    'home' : "# Home page",
    'forecast' : "# Forecast page",
    'params' : "# Params page",
    }

Gui(pages=pages).run()

Basically, your very code, with the root page ("/") added with the navbar you want.
What I can see is that the order is preserved, and no new tab or new window is created when I select a page.

Can you check on your side?
What version of Taipy are you using?
Thanks.

Hi Aazimh and thank you for your feedback.
We reproduce your problem with the latest version of the Taipy GUI package, and this code:
from taipy.gui import Gui

pages = {
    "/": '<|navbar|lov={[("home","Home"), ("forecast","Forecast"), ("params","Params")]}|>',
    'home' : "# Home page",
    'forecast' : "# Forecast page",
    'params' : "# Params page",
    }

Gui(pages=pages).run(async_mode="threading",use_reloader=True, debug=True, watermark="", dark_mode=True)

We are looking at this.
Thank you

You can fix your program by prepending '/' to all the page names:
from taipy.gui import Gui

pages = {
    "/": '<|navbar|lov={[("/home","Home"), ("/forecast","Forecast"), ("/params","Params")]}|>',
    'home' : "# Home page",
    'forecast' : "# Forecast page",
    'params' : "# Params page",
    }

Gui(pages=pages).run(async_mode="threading",use_reloader=True, debug=True, watermark="", dark_mode=True)

That would work properly.

The doc is wrong, however. The page opens in a new tab if... it's identifier does not start with '/'.
Thanks.

Thank you @FabienLelaquais! I partially used your fix, and it seems to have worked, but I'm not clear how/why it worked.
All I did was add a / before my page names in the navbar definitions in the Markdown on each specific page.
However, you also have added the navbar as the root / page in the pages definition itself like so:
pages = {
    "/": '<|navbar|lov={[("/home","Home"), ("/forecast","Forecast"), ("/params","Params")]}|>',
...

This is throwing me off and it's something I have not done, as to me it indicates the root URL would just redirect to a navbar? Is that all it would do, or is this standard practice for using a navbar? i.e. it needs to be added to the Markdown of each individual page, AND to the pages dictionary at the root URL?
Thank you for the help though, it has solved the problem :) now I just want to complete my understanding of how it works.

You actually should not have more than one place where the navbar is defined.
That would be in the root page (the one registered as '/'). And in the root page only. The provided code shows how to do that.
This code has no navbar anywhere but in that page.
May be the Root page section of the doc would clarify things...
It actually is standard practice to have some sort of a 'main' page that holds all common GUI items (like a banner, a footer, ... and a navbar).
Just close that issue when you think you're good!
Cheers,

@FabienLelaquais Got it, that was a fundamental misunderstanding on my part so thank you for clearing that up! I actually hadn't seen that particular part of the documentation.
Doing it this way also has the added benefit of not reloading the page and having a smooth transition between navbar elements (this is mentioned in the documentation you linked but I had no idea) so it's a win-win :) thank you again!


intended use of f5_cloud_failover_nic_map tags is not documented

The CFE clouddocs state that the f5_cloud_failover_nic_map tags are required:

NIC mapping tag: the name is static but the value is user-provided (f5_cloud_failover_nic_map:) and must match the
corresponding NIC on the secondary BIG-IP. The example below uses f5_cloud_failover_nic_map:external.
This name/value tag will correspond to the name/value tag you use in the failoverAddresses.scopingTags section of
the CFE declaration.

However, their purpose and intended use of these tags is not documented. Furthermore, the current version (v5.7.0) of the AWS CFTs do not set these tags and API-based failover seems to operate successfully without them.
Note that the Azure templates do set these additional tags, see https://github.com/F5Networks/f5-azure-arm-templates/issues/172#issuecomment-610376552

Hi,
This part has been removed from the CFE documentation and was released on clouddocs with CFE 1.2

This name/value tag will correspond to the name/value tag you use in the failoverAddresses.scopingTags section of
the CFE declaration.

We will document the intended scenario/use of f5_cloud_failover_nic_map. We are tracking it with internal ID AUTOSDK-439

@f5-chidambaram
Our documentation has been updated:

documentation has been updated accordingly


json parsing error when questionmi response is not valid

logs screenshot
parsing json response from questionmi server raises error, it could be possible that this part of code breaks whole program few minutes after starting

error was raised when program tried to get json error label from invalid request.


BUG: optimize: Protect _minpack calls with a lock.

This fixes gh-3500, three years overdue!
I just followed @sturlamolden's suggestion to protect all _minpack calls with a lock. This should allow users to call leastsq (and other minpack-based code) from multiple threads without risking memory corruption.

Travis failures are unrelated (see gh-7997).

I think it should use scipy._lib._threadsafety.ReentrancyLock so that you get an error message instead of deadlock if you try to nest MINPACK calls.
Also, if you're up to larger plumbing work, I think this part of code could be converted to using ccallback (similarly as what was done with quad) --- that would probably allow scrapping most of the C code.

Do what @pv suggests. The MINPACK Fortran 77 code is not reentrant. scipy._lib._threadsafety.ReentrancyLock ensures that scipy._lib._threadsafety.ReentrancyError is raised if a nested call is attempted from the thread holding the GIL.
I have not looked at the C code that wraps MINPACK for a long time. Unless it stores shared global state for the various MINPACK functions I would suggest one ReentrancyLock per MINPACK function rather than a single lock for the whole module.
I am not sure we should use ccallback instead of @teoliphant's C code. "If it ain't broken, don't fix it." It has survived years of stress testing. I would not throw away thoroughly tested C code for the sake of having a wrapper that is more pleasant to the eye.

Isn't the minpack fortran code actually threadsafe?
I don't see any save statements there.

IIUC, it is precisely the old C wrappers that are the problem in being not threadsafe.

Fortran allows compilers to assume an implicit SAVE statement. That is one of the reasons recursive functions must be declared as such. Many Fortran 77 compilears saved all local variables by default. gfortran still uses this misfeature, even for Fortran 90, albeit to a lesser extent and it can be controlled with compiler flags. Since the SciPy source cannot assume anything about the compiler and compiler flags passed to the Fortran compiler, we just have to assume that Fortran subroutines are never reentrant.
https://mail.scipy.org/pipermail/scipy-dev/2015-June/020775.html
This misfeature of Fortran can have terrible consequences if we e.g. try to call LAPACK from multiple threads:
http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=1930

Also note that local variables always have implicit SAVE in Fortran when their values are initialised in the declaration.
    double precision foobar = 4.
means that foobar is implicitly saved.

We certainly can assume LAPACK is threadsafe. Its default build configuration sets these flags, and any build that does not do so should be considered deficient.

Moreover, scipy has always assumed that fortran routines (see dblquad in QUADPACK) are callable reentrantly. IIRC, the default flags for gfortran guarantee this, unless you happen to use too large stack arrays. Configurations that do not satisfy this, will fail scipy.integrate tests.

By the way, is there any reason we are not using f2py on MINPACK?

Why f2py is not used is probably only historical reasons. I'd expect it
would work fine here.

@perimosocordiae: can you change it to threading.RLock. I think we can risk considering the minpack fortran code reentrant similarly as we do for quadpack (reentrancy is explicitly handled in the minpack C wrappers, but they're not threadsafe).

Done.

You cannot use RLock. It allows reentrant calls from the same thread.

Yes, but the C wrappers have been written for reentrancy in mind, and we
allow the same for quadpack.

If you want to do have a theoretically correct fix, the recursive
statement can be added to the routines that need them, now that we don't
need to stick with f77 any more.

I'll leave gh-3500 open for now --- we can close it after adding the f90 recursive keywords as appropriate.


Closing alert with JS

With the original sweet alert project, I could say something like the following to close the alert.
swal.close();

This does not seem to be the case with this project and I cannot find documentation and or the code that would do this.  Is this available somewhere and I'm just missing it?

Closing.  I now see that the function as changed to:
swal.closeModal();


Spring cleaning for tokens repo

-Now, every token has its logo in two different sizes: 24x24 and 48x48.
-I also added a 24x24 logo for each token with the name "logo.png" to the assets folder so that nothing breaks on the UI.
-I also went over the token logos just to make sure that they're all up-to-date. (I changed a few in there.)
-The tokens that are not whitelisted no longer have their logos under the assets folder.

Fixed the WAVAX and PNG tokens for the WAGMI chain


Issue running python setup.py build develop

🐛 Bug

To Reproduce
Steps to reproduce the behavior:

Follow instructions in INSTALL.MD to install maskrcnn-benchmark
Install dependencies
python setup.py build develop (in the maskrcnn-benchmark directory)

error: invalid initialization of reference of type ‘const at::Type&’ from expression of type ‘c10::ScalarType’    AT_DISPATCH_FLOATING_TYPES(input.scalar_type(), "ROIAlign_forward", [&] {                                                ^ /home/ahmad/anaconda3/envs/mrcnn2/lib/python3.7/site-packages/torch/lib/include/ATen/Dispatch.h:15:32: note: in definition of macro ‘AT_DISPATCH_FLOATING_TYPES’      const at::Type& the_type = TYPE;                                         \                                 ^ error: command 'gcc' failed with exit status 1
Expected behavior
Successful run of the setup.py script

Environment
Collecting environment information...
PyTorch version: 1.0.1.post2
Is debug build: No
CUDA used to build PyTorch: None
OS: Ubuntu 16.04.5 LTS
GCC version: (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
CMake version: Could not collect
Python version: 3.7
Is CUDA available: No
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
Versions of relevant libraries:
[pip] numpy==1.16.2
[pip] torch==1.0.1.post2
[pip] torchvision==0.2.2
[conda] blas                      1.0                         mkl
[conda] mkl                       2019.1                      144
[conda] mkl_fft                   1.0.10           py37ha843d7b_0
[conda] mkl_random                1.0.2            py37hd81dba3_0
[conda] pytorch-cpu               1.0.1               py3.7_cpu_2    pytorch
[conda] torchvision-cpu           0.2.2                      py_3    pytorch
Additional context

Changing AT_DISPATCH_FLOATING_TYPES(input.scalar_type(), "ROIAlign_forward"..
to AT_DISPATCH_FLOATING_TYPES(input.type(), "ROIAlign_forward"..
seems to solve the problem

#557 gives the recommended solution, thus I am closing the issue.

Duplicate of #567


[Feat] ZUI: implement API key management

The UI needs to implement a way for the user to manage how own API keys.
The UI will leverage the APIs for creating/listing/deleting API keys implemented on the backend, see https://github.com/project-zot/zot/blob/main/examples/README.md#api-keys

Note the backend implementation for listing existing API keys is still WIP at the time of this writing.

This has been unblocked by https://github.com/project-zot/zot/pull/1708.
Note https://github.com/project-zot/zot/pull/1708 implements the API to retrieve the API keys as well as the expiration date feature.


Add Chef::Dist to abstract branding details to a single location

Description
This PR replaces https://github.com/chef/chef/pull/8341 , same stuff, updated with latest information regarding Chef's trademark policy, and moved to a new github org to make collaboration easier.
first steps towards allowing multiple distros of Chef in compliance with the Trademark policy
Issues Resolved
first steps towards https://github.com/chef/chef/issues/8376
Presented as a user story, it could be defined as "As a Chef community member, I would like to create an OSS chef-client distribution in compliance with Chef (the company)'s Trademark policy in a simple, automatable and manageable way. The distribution should be a drop-in replacement for chef-client"
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco
[ ] PR title is a worthy inclusion in the CHANGELOG

so... what's buildkite and should I worry about it? :O

Buildkite is our new CI system, but don't worry about that yet.

I've seen conversations about using an internationalization library instead of a class constant for changing out the user-visible strings. Is that still a pending experiment?

I've seen conversations about using an internationalization library instead of a class constant for changing out the user-visible strings. Is that still a pending experiment?

I won't be looking into that, I thought about it but it just feels conceptually wrong and potentially misleading. Can't speak for other tho, I don't mind waiting to see if someone manifests

Proof of concept of building this PR and patching available on https://gitlab.com/cc-build/client with omnibus patches on branch omnibus patches.
Extract from test in this pipeline:
$ dpkg -i cinc*.deb
Selecting previously unselected package cinc.
(Reading database ... 29705 files and directories currently installed.)
Preparing to unpack cinc_15.0.225+20190420210535-1_amd64.deb ...
removing /opt/cincs...
mv: cannot stat '/opt/cincs': No such file or directory
Unpacking cinc (15.0.225+20190420210535-1) ...
Setting up cinc (15.0.225+20190420210535-1) ...
Thank you for installing cinc, the community build based on Chef!
$ cinc-client --version
Cinc Infra: 15.0.225
$ cinc-solo -l info
[2019-04-20T21:20:16+00:00] WARN: No config file found or specified on command line. Using command line options instead.
[2019-04-20T21:20:16+00:00] WARN: No cookbooks directory found at or above current directory.  Assuming /var/chef.
[2019-04-20T21:20:16+00:00] WARN: *****************************************
[2019-04-20T21:20:16+00:00] WARN: Did not find config file: /etc/chef/client.rb. Using command line options instead.
[2019-04-20T21:20:16+00:00] WARN: *****************************************
[2019-04-20T21:20:16+00:00] INFO: Started chef-zero at chefzero://localhost:1 with repository at /var/chef
  One version per cookbook

Starting Chef Client, version 15.0.225
[2019-04-20T21:20:16+00:00] INFO: *** Cinc Infra 15.0.225 ***
[2019-04-20T21:20:16+00:00] INFO: Platform: x86_64-linux
[2019-04-20T21:20:16+00:00] INFO: Cinc-client pid: 46
/opt/cinc/embedded/lib/ruby/gems/2.6.0/gems/ohai-15.0.32/lib/ohai/mixin/command.rb:35: warning: Insecure world writable dir /usr/local/bundle in PATH, mode 042777

Does it seems a correct first step (I'm assuming chef-zero is to be patched also for a complete unbranding)?

I think all comments at this time have been addressed in the latest commit

@bobchaos Thanks for taking the time to put this together and having patience while we noodle over things on our end.


Improve classify.py

functions up until company_record_linkage() output a dataframe of companies with known classifications. the whole InfoGroup datafile currently has not been read in since I've been testing on 20 chunks. When I attempted to read in the whole file, I got an error on chunk 140 related to the Stock Symbol function w/ requests. I will resolve this for next week. The functions from company_record_linkage() and onwards will be used to classify the companies from the organizations dataframe if there are matches. I'm prioritizing finding the best string similarity metric to match company names for next week. I also forgot to run the pre-linter - sorry!

I will need to run the whole InfoGroup dataframe again to account for adding the parent company and ABI column. I was able to get the parent company name based on the parent ABI and have validated this function on the test set, but I would need to apply it to the whole subsetted InfoGroup dataframe. Next steps would be getting the stock symbol of the companies as well as continuing the company matching function to compare the organizations table with the classified company table.
I'm also not sure why linter is not passing here since the pre-commit was passing locally before pushing.

I added instructions for how to retrieve the datafiles and where to store them. I also added packages to requirements.txt that I had used in the orgs_classification_data_pipeline.py pipeline. Please let me know if you're still not able to run it!

I'm working on refactoring the Splink function in linkage in a notebook locally currently


Send pass-core docker logs to cloudwatch

We want to send pass-core docker logs to cloudwatch.  Here is a link on how to do it: https://docs.docker.com/config/containers/logging/awslogs/.   Note the docker compose section for our configuration.

This is done in PROD


Add yamux as first streamMuxer

Motivation

Noticed to be required in https://github.com/ChainSafe/lodestar/pull/4774 to interop with external assertions

Description
Add yamux as first streamMuxer
TODO
Leaving as draft, since before merging we must assert:

[x] Lodestar can interop in Mainnet correctly
[ ] Memory consumption + CPU performance is similar
[x] Gossip throughput in the same
[x] Gossip scoring appears similar

I've tested this branch on feat2 mainnet node, there's gossip peer scoring issue that cause the node to have lower mesh peers

this branch

feat1 (same to unstable)

all metrics look good except for the memory issue, we resolved with #5001
rebasing to latest stable and deployed to feat for the last test

marking as ready for review, @tuyennhv feel free to :+1: when you're comfortable

Closing for issue https://github.com/ChainSafe/lodestar/issues/5804


add config file support for default / common operations

resolved by https://github.com/cquotient/nemesys/pull/36


fix(fusion): Check for NULL return from NewPYRTexture in NewTextureFromPath (#342)

Check for NULL return from NewPYRTexture in NewTextureFromPath.
Reproduction steps:  The tutorial fies can be used to reproduce the crash.  In the Fusion UI, click the "Open File in Preview" button on the toolbar.  Open the file from the tutorial at /gevol/assets/Resources/Terrain/SFTerrain.ktasset/product.kta/ver001/preview.png.aux.xml.  Before the fix, gefusion would crash.  After the fix, the UI reports "File has unknown problems" and gefusion does not crash.
Tested fix on Ubuntu 16.04.
Fixes #342

Testing with centos 7 STIG machine.

I tested this  with centos 7 STIG machine and it does fix the issue.

The code looks fine. I'm just wondering if you checked out why NewPYRTexture might be returning NULL?

Regarding "why NewPYRTexture might be returning NULL":
NewPYRTexture tries to construct a gstPYRTexture for the file being opened (preview.png.aux.xml).  The constructor calls khRasterProduct::Open() which looks for a header.xml file in the same dir as preview.png.aux.xml.  The header.xml file does not exist.  That results in the gstPYRTexture constructor throwing khException and ultimately results in the NULL texture in NewTextureFromPath().
Should there be a header.xml file in that directory?

I looked at some of the assets I have and they do have a header.xml file, but I'm not sure which directory it's trying to open: ./Blue_Marble2.kiasset/product.kia/ver001/raster.kip/header.xml. Maybe that's worth taking a second look at.

Ok.  Continuing investigation.

The file I used to reproduce the issue was at "./SFTerrain.ktasset/product.kta/ver001/preview.png.aux.xml".  The khRasterProduct::Open() code is looking for a header.xml file in the same dir as preview.png.aux.xml.  There actually is a header.xml one dir down in the raster.ktp dir.  Looking at all the header.xml files in my assets they are all under a dir named raster.k?p, product.k?p, or mask.k?p.
When trying to preview a file in Fusion, by default it lists all files.  When you drop down the list of file types, XML files are not listed which I think reinforces this issue's original title that said the crash happened when trying to preview an unsupported type of file.
Note that there is debug output when fusion is unable to open the file.  It reads, "Fusion Warning: Unable to open "/gevol/assets/Resources/Terrain/SFTerrain.ktasset/product.kta/ver001/preview.png.aux.xml".
I don't think there is anything additional needed for this issue, unless we want additional debug output when it doesn't find the header.xml file.  If so, maybe that should be a separate issue.

OK, I looked at it again and it looks like it's able to successfully open the file if it's a header.xml file with corresponding *.pyr files, so I think this works. Thanks for taking a second look.


Failed at the<EMAIL_ADDRESS>install script.

You'll need to provide more of the log. This error message alone doesn't say anything useful

Closing due to unresponsiveness.


ARC Feedback

Several requirements appear to be duplicative of requirements in other specifications - in
particular, the PCIe Specification. Consider removing these requirements from the
RISC-V Server SoC Specification; instead, simply stating that normative requirements
from certain referenced specifications such as the PCIe Base Specification 6.0 are
incorporated here by reference.

Examples: ACS_050; ECM_070; ECM_090; etc.

The document contains several compound requirements, such as IOM_190 and
ECM_020; consider decomposing these into multiple individual requirements.

SEC_010, SEC_020, SEC_030
The Server SoC specification Incorporates several sections from the
RISC-V Security Model specification by reference as mandatory
requirements; however, the Security Model specification specifically
states that it is not intended to be normative. A normative
specification should not incorporate sections of a non-normative
specification. Either both specifications should be normative, or both
should be non-normative.
Recommend removing normative references to the Security Model
Security Model specification specification until a version is available
that has passed ARC and public review.
The Security Model specification is not on track to be frozen before or
concurrently with the Server SoC specification. It seems unwise to
have a frozen specification incorporating sections of a specification
that has no clear line of sight to exit draft status.
Recommend removing references to the Security Model specification
until a Security Model specification version is available that has
passed ARC and public review.

SEC_060
The use of “such as” renders this requirement weak. Consider either
clarifying what standards are acceptable (e.g., “security standards
from national standards laboratories”), or explicitly listing the
acceptable standards and removing the “such as”.

CTI_010, CTI_020
Clarify whether these requirements are also meant to apply to any
comparators that may take the time CSR value as inputs, e.g., for any
*timecmp registers.

CTI_020
This requirement should specify which power states the time CSR
should continue to appear to function. In its current form, if strictly
construed, the time CSR would need to appear to continue to count
even when the entire system is powered off, which seems like an
unnecessary requirement.
Recommend restricting the scope of the power states for which
CTI_020 would apply. For example, the specification could state that
this requirement applies to CPU complex power states, and that
system power states (such as power-off or hibernation states) may
not guarantee that the time CSR appears to be always-on.

IOM_170, IOM_300
IOM_300 mandates a 20-bit PASID, while IOM_170 allows 8-bit and
17-bit PASIDs.
Recommend reconciling the conflict by removing IOM_170’s
acceptance of 8- and 17-bit PASIDs.

IOM_190
Clarify why “at least 4 event counters” are required. Is there a
rationale behind the number “4” here?

IOM_210
Clarify that this requirement refers to the “DBG field of the IOMMU
capabilities register”

IOM_250
This requirement leaves the details of the PMA and PMP checks
vague. Recommend stating explicitly which PMA/PMP checks are
intended to be performed here.

MMS_030
The normative text in this requirement should clarify that address
ranges corresponding to PCIe BARs with the Prefetchable bit set
MAY have non-cacheable, idempotent, coherent, weakly-ordered
PMAs, rather than placing an exception in the requirement’s non-
normative section.

MMS_040, MMS_050
The language “MUST NOT lead to any other behavior”, if taken at
face value, excludes other possibly useful actions. If the intention
here is to forbid “hangs, deadlocks”, then consider rephrasing this as
“MUST NOT lead to any abnormal behavior (hangs, deadlocks, etc.)”

MSI_020
Unclear what the intention is behind this requirement and this may
unintentionally conflict with IOMMU MSI configuration. Recommend
removing it or clarifying it..

PTM_030
Recommend clarifying that the usage of “time” at the end of this
requirement refers to the RISC-V hart time CSR.

AER_080
Recommend clarifying what must not affect PCIe root port
configuration registers (i.e., “affected by what”)

VSR_020
Clarify that this refers to PCIe configuration space registers

SID_020, MSI_030
The text in SID_020 referring to the INTx virtual wire interrupt
signaling mechanism duplicates the MSI_030 requirement.
Recommend removing the INTx-related text in SID_020.

SPM_010
The definition of “significant caches” is unclear. Recommend defining
it, either here or in the glossary.

SPM_060
Consider replacing the initial “The” with “Any” for clarity

RAS_060
Clarify which “control register” this refers to

QOS_040
Consider pluralizing “the IOMMU”

IOM_300 mandates a 20-bit PASID, while IOM_170 allows 8-bit and 17-bit PASIDs. Recommend reconciling the conflict by removing IOM_170’s acceptance of 8- and 17-bit PASIDs.

IOM_170 requires that 20-bit  PASID be supported but allows an implementation to support 8 and 17 bit PASID configurations in the IOMMU. IOM_300 mandates that the host bridge should not truncate the PASID from the PASID TLP that is input to the IOMMU. Thus they are not at conflict. The requirement IOM_300 enables the IOMMU to detect misconfigurations where a device may be programmed with a PASID wider than that  configured in the pdtp.MODE (8/17/20) in the IOMMU for that device. A clarification is included in IOM_300.

AER_080 Recommend clarifying what must not affect PCIe root port configuration registers (i.e., “affected by what”)

The requirement states that the configuration registers themselves must not be affected. The note following   that requirement further clarifies why losing the root port configurations will cause issues with supporting hot-plug. This requirement  has been placed because this is a commonly encountered integration issue.

MMS_030 The normative text in this requirement should clarify that address ranges corresponding to PCIe BARs with the Prefetchable bit set  MAY have non-cacheable, idempotent, coherent, weakly-ordered PMAs, rather than placing an exception in the requirement’s non-normative section.

PCIe 6.0 does not have the concept of "Prefetchable" bit anymore. The concept of “Prefetchable” MMIO was originally needed to control PCI-PCI Bridges, which were allowed/encouraged to prefetch Memory Read data in prefetchable regions. MMIO that has read side-effects, e.g. locations that auto-increment when read, cannot safely be prefetched from, and so needed to be distinguished from regions that could. While this was intended to specifically focus on PCI behavior it has been a cause of confusion to system software developers and this was eventually fixed in PCIe 6.0 through "Removing Prefetchable Terminology ECN".
The MMS_030 specifically calls attention to “restricted programming model” to indicate the precautions provided by PCIe 6.0 specification when overriding the memory attribute of accesses made to device registers.

IOM_190 Clarify why “at least 4 event counters” are required. Is there a rationale behind the number “4” here?

A typical performance analysis requires counting - translation requests, TLB misses, number of page walks, and possibly average page walk latency - for identifying performance bottlenecks at the top level. The count of 4 was arrived at based on review of HPM in IOMMU with the performance analysis SIG and based on experience with similar architectures. Some notes are in the minutes and follow on discussion.

Several requirements appear to be duplicative of requirements in other specifications - in particular, the PCIe Specification. Consider removing these requirements from the RISC-V Server SoC Specification; instead, simply stating that normative requirements from certain referenced specifications such as the PCIe Base Specification 6.0 are incorporated here by reference. Examples: ACS_050; ECM_070; ECM_090; etc.

The ECM_090 was intended to draw attention to common integration mistakes such as ignoring ARI forwarding when making determination of when to convert type 1 to type 0 configuration requests. Added notes to further clarify.
Merged ECM_070 and ACS_050 into a single requirement on root complex integration - RCI_010

MSI_020 Unclear what the intention is behind this requirement and this may unintentionally conflict with IOMMU MSI configuration. Recommend removing it or clarifying it..

This is removed. The intent was to forbid needing vendor specific programming to route or handle MSIs as has been seen on some implementations.

IOM_250 This requirement leaves the details of the PMA and PMP checks vague. Recommend stating explicitly which PMA/PMP checks are intended to be performed here.

It is not possible to mandate which regions are protected regions for a platform and hence are covered by a PMP. The requirement has been clarified to state that the PMP checks are intended to restrict IOMMU accesses to the same memory that the  software programming the hart can also access.
The IOMMU requires supporting  its data structures  and pages tables in main memory. It is clarified that supporting non main memory access for IOMMU data structures is not required.

Updates in PR #49


Typescript Stickers

Acknowledgement

[X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment
Hey, where can I get a good typescript logo sticker for my laptop?

Can you not use Google?

Instead of using a pair of rhetorical questions meant to shame another person, perhaps you can seek to understand the intent behind the question?
I would like to avoid purchasing an unlicensed sticker, and I couldn’t find an officially sanctioned one. Also, I used the “new issue” flow and selected “other” for a question that didn’t fit into any other category. It ended up in this list.
it would be greatly beneficial if you could link to an official sticker or provide a better venue to ask the question.

There are no sanctioned or official stickers to purchase. And what purchase options you have also heavily depends on your country of residence, which you did not mention.

Thank you.

https://www.typescriptlang.org/branding/, though this page might get deprecated
I did a die-cut sticker from an SVG a few years back; this needs a small bit of manual cleanup but looks nice IMO

Thank you @RyanCavanaugh!


Admin page improvements

Improve admin page ui by :-

making colors correct
making sizes and fonts correct with theme
add some animations to opening sidebar
Add charts

Links (very important) :-

Use this https://davur.dexignzone.com/react/demo/dashboard for improving designs and adding more sections to dashboard.
Use https://recharts.org/en-US/examples for the charts.

i would like to work on this issue can you assign me @Varinder-Dhillon0

Go ahead @venkataraviraja5

hey can you please unassign me i am not familar with charts...sorry for request

ok @venkataraviraja5

Can I work on this issue??

Can I work on this issue??

Sure @Bikram-ghuku

Sorry I wont be able to work on this issue, I have unassigned myself


Adding PT/BR translation to the CONTRIBUTING.md file

Added a new file CONTRIBUTING - PT-BR.md with the translation

Thanks for the PR, we don't have plans to translate this document though. See https://github.com/Microsoft/vscode/pull/61077#issuecomment-430509601


Update not to run depends when running "make clean".

In this pull-request, maybe we might need discussion.
The situation is when run "make clean", ".depend" task is run.
As we know, the task is always run.
I want to change this behavior.
Because when people want to remove files, the dependency installation starts. That's not intuitive.
I like to run the ".depend" when only "make nanopolish" is run.
And considering how to inject "depend" task, I think "make & make test" can be used instead of "make nanopolish & make test" after this pull-request.
How do you think?

It looks good to me but I'd like to test it locally before merging. I am leaving for a trip tomorrow morning so I may not get a chance to look before I am back on Sept 24th.

Okay, that's fine. Thank you.


update(build): updated plugins to latest versions adding platform name to artifact url

Signed-off-by: Federico Di Pierro<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Updates plugins to latest versions; updated libs to latest version.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

@FedeDP: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Closing and reopening to trigger the CI
/close

@leogr: Closed this PR.

In response to this:

Closing and reopening to trigger the CI
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/reopen

@leogr: Reopened this PR.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/milestone 0.31.0

Hey @FedeDP
Could you add a line in the release note block regarding the new driver version? :pray:
(it's likely the last driver bump in this release, so we need it in the changelog)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3185d0ddcb4bba2afca78f05cd2d56beebeaadc6

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


PMF-ResNet50 on SemanticKITTI Validation Set?

Hi~
Thanks for the open-source repo of your excellent work!
I notice that PMF-ResNet50 significantly outperforms PMF-ResNet34 on nuScenes Validation Set, and you even adopt ResNet101 on SensatUrban Test Set.
However, the result of PMF-ResNet50 (or deeper backbone) on SemanticKITTI Validation Set is unavailable. Did you try it before? Intuitively, it will also bring gains. Or did I miss something important?

Unfortunately, using ResNet-50/101/152 on SemanticKITTI did not bring improvements to the model performance as we only use a limited subset (front-view only) of SemanticKITTI for training.
Recently, we found that using conformer as the backbone of the image stream can bring a 2.2% improvement on SemanticKITTI.
You can try more backbones to improve the performance~

The model of conformer is pre-trained on ImageNet-21k and then fine-tuned on ImageNet-1k.

Thanks a lot!
As for your mentioned conformer, I will give it a try :-)

不幸的是，在SemanticKITTI上使用ResNet-50 / 101 / 152并没有提高模型性能，因为我们只使用SemanticKITTI的有限子集（仅前视图）进行训练。
最近，我们发现使用构象作为图像流的主干可以带来2.2%的SemanticKITTI改进。
可以尝试更多骨干网提升性能~

你好，我尝试使用conformer代替原本的resnet34，并且也加载了预训练权重，目前看到一影像流的分割精度很低，比resnet要差，请问您当时是怎样使用conformer的，有什么是我遗漏的吗？希望可以您进一步交流，这是我的qq1254952619


fix: consolidate package setup to pyproject.toml

This was always a good idea, but with the release of setuptools 69.0.1, it became a necessity, as the new version breaks with setup spread out over both setup.cfg and pyproject.toml.

This was primarily done by running ini2toml on setup.cfg and merging the output into pyproject.toml by hand. It ended up moving the long description into a README section that setuptools didn't like at all, so I removed that and added 'readme' value to [project] that points to README.md.
There was some initial confusion about what to do with the version, but it looks like with this configuration setuptools_scm is free to set it. It's possible I'm missing something here, though.


Issue with buttons in profile

Buttons not displaying in the profile page, update them. Enable overflow to the sidebar in search for students option of club page. Search by student name has to come to the centre of the input, but its popping to the left side.

Assigned to Raghavendra Vijaya


Sleeping for another 5 seconds...

为什么在本地ganache部署，运行requestAndReadAPI.js 一直显示Sleeping for another 5 seconds...，无法调用成功

Why is the message Sleeping for another 5 seconds... displayed when running requestAndReadAPI.js in the local ganache deployment, and the call cannot be made successfully?


DTS cleanup for nRF5340 SoC and its IPC nodes

1st commit:
Cleaned up the IPC configuration for nRF5340 SoC in Device Tree. This
change fixes the (simple_bus_reg) warning about the missing or empty
reg/ranges property.
This is a follow-up to commit cf6a58d3f61aa163d149a3c3ff6389285bd09c13.
2nd commit:
Added chosen syntax in Device Tree to abstract the IPC device that is
used with the IPC service module in the Bluetooth HCI RPMsg driver.
Ported affected boards to declare this alias.

Rebasing my commits because of some unrelated CI failures. The PR diff did not change

Pushed a patch to align DTS overlays in the samples/subsys/ipc/ipc_service/ directory with the new IPC description in DTS

PR is missing a description

@Thalley, I added the description for both commits

It seems that CI is happy now. Please rereview


Update sorting for enforcement actions filter page to match publishing date

Fixes an issue where the currently inconsistent date_filed field was causing enforcement actions to appear out of order

Is this a temporary fix, or permanent change? If the latter, could we remove the definition of EnforcementActionsFilterForm.get_page_set since it now duplicates the method inherited from its parent FilterableListForm.get_page_set?

Temporary! date_filed will return in the new year, this is just to keep the sorting accurate until I am available to build then final enforcement data model and transfer all the existing actions to it (but date_filed will be consistent once again in that model, so this will be reverted then)


test(pkg/smi): adds test for smi health checker

Adds unit test for smi.HealthChecker
and resolves #3243
Signed-off-by: Shalier Xia<EMAIL_ADDRESS>
Description:

Affected area:

Functional Area

New Functionality
[ ]

Documentation
[ ]

Install
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Ingress
[ ]

Egress
[ ]

Networking
[ ]

Observability
[ ]

SMI Policy
[ ]

Sidecar Injection
[ ]

Security
[ ]

Upgrade
[ ]

Tests
[x ]

CI System
[ ]

Demo
[ ]

Performance
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

Codecov Report

Merging #3556 (2216de0) into main (b223d9e) will increase coverage by 0.52%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #3556      +/-   ##
==========================================
+ Coverage   66.12%   66.64%   +0.52%
==========================================
  Files         170      173       +3
  Lines        8082     8241     +159
==========================================
+ Hits         5344     5492     +148
- Misses       2708     2719      +11
  Partials       30       30

Flag
Coverage Δ

unittests
66.64% <0.00%> (+0.52%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/smi/health.go
78.57% <0.00%> (+78.57%)
:arrow_up:

pkg/utils/proto.go
63.63% <0.00%> (-6.37%)
:arrow_down:

pkg/injector/envoy_config.go
87.73% <0.00%> (-2.71%)
:arrow_down:

pkg/envoy/bootstrap/config.go
95.83% <0.00%> (ø)

pkg/validator/server.go
43.58% <0.00%> (ø)

pkg/validator/validators.go
92.59% <0.00%> (ø)

cmd/init-osm-controller/init-osm-controller.go
34.09% <0.00%> (+6.81%)
:arrow_up:

Continue to review full report at Codecov.

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


Documentation pages not rendering on iOS 12.5.5

Link:
https://docs.microsoft.com/en-us/azure/architecture/browse/
Azure and other online documentation pages do not render correctly in the browser on ioS 12.5.5 running on iPad Mini 2.
I have tried latest versions of the following supported browsers:
Chrome version: 92.0.4515.90
Safari latest version for iOS 12.5.5
Only the article title and introduction load. Microsoft logo, documentation menu or any other content on the page does not load/display.
Is there a minimum supported browser/iOS version for the online docs published somewhere? Or, are the docs supposed to render correctly in the above iOS/browser versions?

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

Yes, its not working on Ipad mini 2, checked on Edge, Safari and Chrome

Yes, its not working on Ipad mini 2, checked on Edge, Safari and Chrome

I don't have an iPad Mini 2 handy.
Is it always the OS version 12.5.5?
Can you please take a screenshot of the page when its in the broken state and share here. Thanks!

Hi @JasonWHowell ,
I am sharing 2 pics of https://docs.microsoft.com/en-us/learn/modules/scale-apps-app-service/ and https://docs.microsoft.com/en-us/learn/modules/scale-apps-app-service/1-introduction
Observe breadcontrol menu and sign in option does not appear on header. With this, button to navigate to next page does not appear.
Device iPad Mini 2, iOS version: 12.5.5. Checked on Edge, Chrome and Safari, same result.
Its working on Iphone 8, iOS version 15.1

.

Thanks! I'll relay this to the Docs dev team.

arjain18, vishalkalra, just to keep you posted. The issue is being investigated by our doc dev team. As soon as we have more updates, we will relay here. Thanks for reporting this issue.

Thanks for sharing the update.

HI there, has there been any resolution to this issue?

@wibjorn FYI re 538994

@droptable9 sorry, no update yet. We've tracked the bug with our the docs engineering team. Hoping for a better status soon.

Any updates on this issue?


ARM64 Terraform cannot be downloaded if OS reports its arch as Aarch64

I'm attempting to run Terrakube on EKS using ARM-based nodes, and the Executor is unable to download Terraform. Pulling the container logs and I get the following:
[threadPoolTaskExecutor-1] INFO org.terrakube.executor.service.terraform.TerraformExecutorServiceImpl - Terraform Working Directory: /root/.terraform-spring-boot/executor/a682c11d-7fa1-4a20-b73f-4ab488d9cb24/a42c0089-2d52-4f8e-9f27-145b16cbae5b
[threadPoolTaskExecutor-1] INFO org.terrakube.executor.plugin.tfstate.aws.AwsTerraformStateImpl - Generating backend override file for terraform 1.9.8
[threadPoolTaskExecutor-1] WARN org.terrakube.executor.service.terraform.TerraformExecutorServiceImpl - Not using any SSH key to download modules
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformClient - Creating terraform downloader using terraform release URL: https://releases.hashicorp.com/terraform/index.json and tofu release URL: http://terrakube-api-service:8080/tofu/index.json
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Initialize TerraformDownloader using custom URL
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - User Home Directory: /root
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Validate/Create download temp directory: /root/.terraform-spring-boot/download/
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Validate/Create terraform directory: /root/.terraform-spring-boot/terraform/
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - User Home Directory for tofu download: /root
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Validate/Create tofu download temp directory: /root/.terraform-spring-boot/download/tofu/
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Validate/Create tofu directory: /root/.terraform-spring-boot/tofu/
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Downloading terraform releases list
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Deleting Temp /root/.terraform-spring-boot/terraform-10306814652704127386-release
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Found 346 terraform releases
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Downloading tofu releases list
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Deleting Temp /root/.terraform-spring-boot/tofu-18428381804482887821-release
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Found 30 tofu releases
[threadPoolTaskExecutor-1] INFO org.terrakube.terraform.TerraformDownloader - Downloading terraform version 1.9.8 architecture aarch64 Type Linux
[threadPoolTaskExecutor-1] ERROR org.springframework.aop.interceptor.SimpleAsyncUncaughtExceptionHandler - Unexpected exception occurred invoking async method: public void org.terrakube.executor.service.executor.ExecutorJobImpl.createJob(org.terrakube.executor.service.mode.TerraformJob)
java.lang.IllegalArgumentException: Invalid Terraform Version
	at org.terrakube.terraform.TerraformDownloader.downloadTerraformVersion(TerraformDownloader.java:243)
	at org.terrakube.terraform.TerraformClient.getTerraformLauncher(TerraformClient.java:283)
	at org.terrakube.terraform.TerraformClient.run(TerraformClient.java:208)
	at org.terrakube.terraform.TerraformClient.init(TerraformClient.java:104)
	at org.terrakube.executor.service.terraform.TerraformExecutorServiceImpl.executeTerraformInit(TerraformExecutorServiceImpl.java:404)
	at org.terrakube.executor.service.terraform.TerraformExecutorServiceImpl.plan(TerraformExecutorServiceImpl.java:107)
	at org.terrakube.executor.service.executor.ExecutorJobImpl.createJob(ExecutorJobImpl.java:53)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:355)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:196)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
	at org.springframework.aop.interceptor.AsyncExecutionInterceptor.lambda$invoke$0(AsyncExecutionInterceptor.java:113)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

According to this line, the architecture check is a completely strict check, but Terraform lilsts its ARM versions as arm and arm64, so aarch64 will never match. Either how the client checks the OS version needs to change to match dpkg --print-architecture (see below), or a condition similar to the OS ones needs to be performed.
root@terrakube-executor-5654669d77-ksdkm:/workspace# dpkg --print-architecture
arm64
root@terrakube-executor-5654669d77-ksdkm:/workspace# uname -m
aarch64

Hello @fishfacemcgee
I think the library will have to add some condition in the logic to fix that.
Would you like to help with the fix?

@alfespa17 I can write what I think a fix would look ilke (assuming we mean this library and not system utils or something), but I don't have any viable means to test the changes myself.

@alfespa17 I can write what I think a fix would look ilke (assuming we mean this library and not system utils or something), but I don't have any viable means to test the changes myself.

Ok, let me see if I can create a VM that is using aarch64 and test it there because I have some small example to test the library.

Hello @fishfacemcgee I created a new release with your fix, it takes some time to be available in maven central, I will update the library in our Terrakube repo in a couple of hours so I can  create maybe a hotfix 2.23.3


Strange values from the pulse_meter

I can't figure out what I'm doing wrong. The pulse_meter does not count pulses (W) and the total energy increase for each pulse is much higher than expected. Here is the log:
[21:49:13][D][sensor:121]: 'Meter - Total energy': Sending state 0.13467 kWh with 3 decimals of accuracy
[21:49:17][D][binary_sensor:036]: 'Meter pulse': Sending state OFF
[21:49:17][D][sensor:121]: 'Meter - Total energy': Sending state 0.15400 kWh with 3 decimals of accuracy
[21:49:17][D][binary_sensor:036]: 'Meter pulse': Sending state ON
[21:49:17][D][sensor:121]: 'Meter - Total energy': Sending state 0.16333 kWh with 3 decimals of accuracy
[21:49:20][D][binary_sensor:036]: 'Meter pulse': Sending state OFF
[21:49:20][D][sensor:121]: 'Meter - Total energy': Sending state 0.19000 kWh with 3 decimals of accuracy
[21:49:20][D][binary_sensor:036]: 'Meter pulse': Sending state ON
[21:49:24][D][binary_sensor:036]: 'Meter pulse': Sending state OFF
[21:49:24][D][sensor:121]: 'Meter - Total energy': Sending state 0.21467 kWh with 3 decimals of accuracy
[21:49:24][D][binary_sensor:036]: 'Meter pulse': Sending state ON
[21:49:26][D][pulse_counter:159]: 'Pulse Counter': Retrieved counter: 0.00 pulses/min
[21:49:26][D][sensor:121]: 'Pulse Counter': Sending state 0.00000 pulses/min with 2 decimals of accuracy
[21:49:28][D][sensor:121]: 'Meter - Total energy': Sending state 0.24067 kWh with 3 decimals of accuracy
[21:49:32][D][sensor:121]: 'Meter - Total energy': Sending state 0.26600 kWh with 3 decimals of accuracy
[21:49:35][D][sensor:121]: 'Meter - Total energy': Sending state 0.29333 kWh with 3 decimals of accuracy
[21:49:39][D][binary_sensor:036]: 'Meter pulse': Sending state OFF
[21:49:39][D][sensor:121]: 'Meter - Total energy': Sending state 0.32267 kWh with 3 decimals of accuracy
[21:49:39][D][binary_sensor:036]: 'Meter pulse': Sending state ON
[21:49:43][D][sensor:121]: 'Meter - Total energy': Sending state 0.35267 kWh with 3 decimals of accuracy
[21:49:47][D][sensor:121]: 'Meter - Total energy': Sending state 0.38200 kWh with 3 decimals of accuracy
[21:49:50][D][sensor:121]: 'Meter - Total energy': Sending state 0.40667 kWh with 3 decimals of accuracy
[21:49:54][D][binary_sensor:036]: 'Meter pulse': Sending state OFF
[21:49:54][D][sensor:121]: 'Meter - Total energy': Sending state 0.43267 kWh with 3 decimals of accuracy
[21:49:54][D][binary_sensor:036]: 'Meter pulse': Sending state ON
[21:49:58][D][binary_sensor:036]: 'Meter pulse': Sending state OFF
[21:49:58][D][sensor:121]: 'Meter - Total energy': Sending state 0.45800 kWh with 3 decimals of accuracy
[21:49:58][D][binary_sensor:036]: 'Meter pulse': Sending state ON
[21:50:02][D][sensor:121]: 'Meter - Total energy': Sending state 0.48333 kWh with 3 decimals of accuracy
[21:50:02][D][sensor:121]: 'Meter WiFi Signal': Sending state -68.00000 dBm with 0 decimals of accuracy
[21:50:05][D][sensor:121]: 'Meter - Total energy': Sending state 0.50867 kWh with 3 decimals of accuracy

Based on my understanding, each pulse should increase the total kWh by 1/1500 i.e. 0.000667 but as seen above it increases by not equal values and they are much higher (between 0.02 and 0.03)
I've added a binary sensor to the gpio pin to monitor its behavior in HA.
My pulses/kWh is 1500.
Strange thing is that when meter diode is off the binary sensor is On and when the diode lights up the binary sensor is turned off (maybe it should be this way?). Other than that it is fully in sync with the meter diode.
Here is my config:
substitutions:
  device_name: meter
  friendly_name: Meter
  device_description: "Measure your energy consumption with the pulse LED on your smart meter"
  pulse_pin: GPIO4
  # imp/kWh rate #
  pulse_rate: '1500'

esphome:
  name: '${device_name}'
  platform: ESP8266
  board: nodemcuv2

binary_sensor:
  - platform: gpio
    pin: ${pulse_pin}
    name: "Meter pulse"
    id: meter_pulse

sensor:
  - platform: wifi_signal
    name: "Meter WiFi Signal"
    update_interval: 60s

  - platform: pulse_meter
    name: '${friendly_name} - Power consumption'
    id: pulse_meter_id
    unit_of_measurement: 'W'
    state_class: measurement
    device_class: power
    icon: mdi:flash-outline
    accuracy_decimals: 0
    pin: ${pulse_pin}
    filters:
      # multiply value = (60 / imp value) * 1000
      # - multiply: 60
      - lambda: return x * (60.0 / ${pulse_rate} * 1000);
    total:
      name: '${friendly_name} - Total energy'
      unit_of_measurement: 'kWh'
      icon: mdi:circle-slice-3
      state_class: total_increasing
      device_class: energy
      accuracy_decimals: 3
      filters:
        # multiply value = 1 / imp value
        # - multiply: 0.001
        - lambda: return x * (1.0 / ${pulse_rate});

Am I doing something wrong?

OK, I've just realized that the module I have has an LDR (that's what they've had locally, not waiting several weeks for delivery from China). So the question is if it can work with the LDR?

I don't see anything weird in your logs.
I think your expectations are more in line with the pulse_counter component of ESPHome, but the pulse_meter is a combination of the pulse_counter and pulse_width component. So it not only looks at the fixed amount of energy that it should add up, but also determined the value based on the time between the pulses. That is why each measurement in terms of power (W) and counting the total energy (kWh) per pulse can be different.

What is you use this: (1000.0 instead of 1000)
- lambda: return x * ((60.0 / ${pulse_rate}) * 1000.0);

What is you use this: (1000.0 instead of 1000)
- lambda: return x * ((60.0 / ${pulse_rate}) * 1000.0);

Changed it and there is no difference. The Power sensor is not getting updated and total energy updates are too high.
I've created some template sensors in HA based on just the binary_sensor from esphome and they are much more accurate (I just add 1/1500 kWh with every meter pulse to the total energy sensor).
I have also created a pulse_counter sensor in esphome and strangely it is not showing any value neither - stays all the tiime on 0.000. Could this be that it is because the normal level of the gpio is high and goes low when the meter led blinks?

Maybe you need to add this line: https://github.com/klaasnicolaas/home-assistant-glow/blob/master/home_assistant_glow.yaml#L100

Maybe you need to add this line: https://github.com/klaasnicolaas/home-assistant-glow/blob/master/home_assistant_glow.yaml#L100

Looks like that was it! Many thanks. I'll monitor it for a while and report back. If it works it also means that LDR is also good for this project.

Would still not recommend to use the LDR, because of the reliability in terms of measurements. But in the end it is certainly possible to use an LDR.

Anyway I've ordered the photodiode but only available in China so it will take a while. Not sure what is the problem with the photodiode modules availability...


Because no versions of build_runner match >1.2.8 <2.0.0 and build_runner 1.2.8 depends on build_daemon ^0.4.0, build_runner ^1.2.8 requires build_daemon ^0.4.0. So, because build_daemon >=0.2.0 requires SDK version >=2.1.0 <3.0.0 and gsy_github_app_flutter depends on build_runner ^1.2.8, version solving failed.

clone下来运行报如下错误：
Because no versions of build_runner match >1.2.8 <2.0.0 and build_runner 1.2.8 depends on build_daemon ^0.4.0, build_runner ^1.2.8 requires build_daemon ^0.4.0.
So, because build_daemon >=0.2.0 requires SDK version >=2.1.0 <3.0.0 and gsy_github_app_flutter depends on build_runner ^1.2.8, version solving failed.
我应该怎么修改配置呢？

哦，我提重复问题了，关掉吧

怎么解决的呢？我已经切换到redme上说的Flutter SDK 版本 v1.3.2 啦，求解


Minimum configuration for openldap authentification backend

Expected behaviour
Minimum configuration should be suffisant
LDAP_AUTH, LDAP_SERVER, LDAP_START_TLS, LDAP_BIND_TYPE, LDAP_USERNAME, LDAP_PASSWORD, LDAP_USER_BASE_DN, LDAP_USER_FILTER
Actual behaviour
With that configuration and even more, can't connect, and debug log isn't helpfull, I see it can't connect but I don't know why. The ldap log isn't more helpfull.
Steps to reproduce

Configure a openldap with memberof overlay
configure kanboard LDAP AUTH as explained in doc
try to connect a user

Configuration

Kanboard version: v1.0.26-57-g7d7b9f7
Database type and version: sqlite  3.7.13
PHP version: PHPv5.4
OS: debian gnu/linux 8
Browser: Firefox/Chromium

There are more logs from Kanboard if you use enable the debug mode. Maybe that will help you to find the problem.

;-) I told you in the question that i used debug log.

There is now 4 configuration examples for LDAP on the website: https://kanboard.net/documentation/ldap-configuration-examples
I hope you will solve your issue.


TypeError: string argument without an encoding

What happened?
After system reboot replica can't catchup with the leader.
Could see following error in patroni logs.
2024-07-11 15:38:53,527 INFO: master_timeline=6 2024-07-11 15:38:53,537 ERROR: Exception when working with master via replication connection Traceback (most recent call last):   File "/usr/local/lib/python3.6/site-packages/patroni/postgresql/rewind.py", line 197, in _check_timeline_and_lsn     history = bytes(cur.fetchone()[1]).decode('utf-8') TypeError: string argument without an encoding
How can we reproduce it (as minimally and precisely as possible)?
We have seen this issue with:
patroni version: 2.0.2
PostgreSQL version: 15.6
What did you expect to happen?
It seems the issue is in the statement: history = bytes(cur.fetchone()[1], encoding='utf8').decode('utf-8')
When we tried this code, it is giving the error same as the error in patroni log file.
with psycopg2.connect(dbname = dbname, user= user, password=password, replication=replication) as conn:
    conn.autocommit = True
    with conn.cursor() as cur:
        cur.execute('IDENTIFY_SYSTEM')
        master_timeline = cur.fetchone()[1]
        print('master_timeline=', master_timeline)
        cur.execute('TIMELINE_HISTORY %s', (master_timeline,))
        history = bytes(cur.fetchone()[1]).decode('utf-8')
        print('master: history=%s', history)

Error:
master_timeline= 6
Traceback (most recent call last):
  File "test.py", line 15, in <module>
    history = bytes(cur.fetchone()[1]).decode('utf-8')
TypeError: string argument without an encoding`

But when we changed the statement history = bytes(cur.fetchone()[1]).decode('utf-8') to history = bytes(cur.fetchone()[1], encoding='utf8').decode('utf-8'), it worked fine.
master_timeline= 6
master: history=%s 1	0/80000A0	no recovery target specified

2	0/90000A0	no recovery target specified

3	0/A0000A0	no recovery target specified

4	0/100000A0	no recovery target specified

5	0/130000A0	no recovery target specified

Patroni/PostgreSQL/DCS version

Patroni version: 2.0.2
PostgreSQL version: 15.6

Patroni configuration file
-

patronictl show-config
-

Patroni log files
-

PostgreSQL log files
-

Have you tried to use GitHub issue search?

[X] Yes

Anything else we need to know?
No response

patroni version: 2.0.2

Upgrade ASAP


Remove docs related to deprecated deploy-to-azure vs code extension

The VS Code extension Deploy to Azure has been deprecated. This PR removes the doc related to it.

@bishal-pdMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@bishal-pdMSFT, @juliakm - I'm wondering if this content should be archived instead of just deleted. Unfortunately, we are having some issues with our archive repo, but I can take an action to archive the current copy once that get's addressed.
Also - we should add a redirect link to the .openpublishing.redirection.json file for the deleted file. If there is no article to redirect it to or blog post, then at a minimum it should be redirected to the github issue deprecation notice URL: https://github.com/microsoft/vscode-deploy-azure/issues/239.

@bishal-pdMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Also - we should add a redirect link to the .openpublishing.redirection.json file for the deleted file. If there is no article to redirect it to or blog post, then at a minimum it should be redirected to the github issue deprecation notice URL: https://github.com/microsoft/vscode-deploy-azure/issues/239.

@KathrynEE I made the change for redirect url. But I am not sure if that is correct as all other urls in this file are using relative paths. Is this going to cause problem? Please feel free to update the PR with right url.

@KathrynEE
@juliakm
@pulkitaggarwl
These changes need to be made in the private repo for validation checks.
Could you pull the commits into a new PR in the private repo?
Thanks.

@bishal-pdMSFT - I hadn't noticed that this was in the public repo and not the private repo.
Adding @steved0x - Steve is there an easy way to get this incorporated into the public repo? It's mostly a delete on an article, update redirect, and remove cross links - so there isn't much that needs to be reviewed editorially.

I am not sure which private repo is being talked about here. Please point me and I will raise a PR there. I assume private to public replication will happen automatically?


add icesugar_pro platform file from #197

hey there, this PR adds the linked icesugar_pro platform file, based on #197 with some additions, and pins markupsafe to 2.0.1 as a temporary fix to avoid https://github.com/pallets/markupsafe/issues/282 (so python setup.py test installs a working version).

works for me


Allow for omitting date on post

Previously, all posts had to show a date. If the date: attribute was removed from the md file, then something like "0000 Jan 01" would default.
This is use for static pages that are not part of the blog structure, like a separate "about" or "contact" page.

Thanks for the contribution @jdl031 ! Looks good to me.

@all-contributors please add @jdl031 for code


Doc/Quickstart (minor): npm bin deprecated in Node 18.14

Hi. This is just a minor documentation issue.
Step 4 in docs/quickstart.md instructs to do:
"rnuc": "$(npm bin)/rnuc"

But npm bin has been removed in Node 18.14. It could be updated to:
"rnuc": "$(npm bin)/rnuc"

If you are on Node < 18.14, or:
npx rnuc

If you are on Node >= 18.14.
Steps to Reproduce
nvm i v18.16.0
nvm use v18.16.0
npm run rnuc .env

sh: Unknown: command not found

Thank you!

Hi. This is just a minor documentation issue.
Step 4 in docs/quickstart.md instructs to do:
"rnuc": "$(npm bin)/rnuc"

But npm bin has been removed in Node 18.14. It could be updated to:
"rnuc": "$(npm bin)/rnuc"

If you are on Node < 18.14, or:
npx rnuc

If you are on Node >= 18.14.
Steps to Reproduce
nvm i v18.16.0
nvm use v18.16.0
npm run rnuc .env

sh: Unknown: command not found

Thank you!

Thank you, this solve the issue with node v18.17.1


Webmin menu on iOS 16.4

Since upgrading my iPad to iOS 16.4, the webmin menu does not stay on screen to enable user to select menu items.  Webmin interface works ok on PC.

Hello,
This is a known issue. I'm working on resolving this.

Fixed. Details here.