Permission denied when writing to folder shared with service account

I have a folder in my Google Drive which I have shared with a service account as Editor.
Mounted like so:
google-drive-ocamlfuse -serviceaccountpath key.json -serviceaccountuser<EMAIL_ADDRESS>/tmp/googledrive
Read operations work fine.
My problem is that write operations always fail with "Permission denied".
/tmp/googledrive/.shared/shared_folder$ ls
bar.txt
/tmp/googledrive/.shared/shared_folder$ cp bar.txt foo.txt
cp: cannot create regular file 'foo.txt': Permission denied
-debug logs show nothing insightful:
[1779.889564] TID=301: fopen /.shared/shared_folder/bar.txt O_RDONLY
[1779.889573] TID=301: BEGIN: Getting metadata from context
[1779.889577] TID=301: END: Getting metadata: Valid
[1779.889582] TID=301: BEGIN: Loading resource /.shared/shared_folder/bar.txt (trashed=false) from db
[1779.889593] TID=301: END: Loading resource /.shared/shared_folder/bar.txt (trashed=false) from db: Found (id=897, state=ToDownload)
[1779.889671] TID=302: getattr /.shared/shared_folder/foo.txt
[1779.889679] TID=302: BEGIN: Getting metadata from context
[1779.889683] TID=302: END: Getting metadata: Valid
[1779.889687] TID=302: BEGIN: Loading resource /..shared/shared_folder/foo.txt (trashed=false) from db
[1779.889702] TID=302: END: Loading resource /.shared/shared_folder/foo.txt (trashed=false) from db: Found (id=901, state=NotFound)
[1779.889713] TID=302: File not found: stat /.shared/shared_folder/foo.txt
[1779.889763] TID=303: mknod /.shared/shared_folder/foo.txt 100755
[1779.889772] TID=303: Permission denied: mknod /.shared/shared_folder/foo.txt
Authenticating as myself everything works as expected.
Tried everything I could think of: root/non-root, different machines, checked scopes, checked share permissions...
Any ideas, or suggestions how to debug further?

Thanks for the quick fix @astrada I'll get some time to test that in the next few days.

Thanks for the quick fix @astrada I'll get some time to test that in the next few days.

Sure, thanks! I'm publishing version 0.7.24 that should fix your issue. I wasn't allowing file/folder creation and renaiming in the .shared folder to avoid accidentally messing with shared resources, but with service accounts I don't think there are other workarounds (like add to my drive).

Sure, thanks! I'm publishing version 0.7.24 that should fix your issue. I wasn't allowing file/folder creation and renaiming in the .shared folder to avoid accidentally messing with shared resources, but with service accounts I don't think there are other workarounds (like add to my drive).

Hi @astrada just confirming all working as expected with 0.7.24. Many thanks!

@astrada This issue was also driving me nuts, spent a lot of time trying to figure out why can't the shared file be edited & saved. I wished I had visited this page earlier.


A bug in the platypus wrapper for grch38?

Hello!
In WES multisample calling on grch38, when it comes to
bcftools view -O z  work/platypus/vexomes-vepeffects-filter.vcf.gz -s IV3 > [tmp_folder] IV3-vepeffects-filter.vcf.gz

it throws an error:
Error: subset called for sample that does not exist in header: "IV3". Use "--force-samples" to ignore this error.

Indeed the sample names in vexomes-vepeffects-filter.vcf.gz are IV24-sort, IV3-sort,
instead of IV24, IV3.
The sample names are correct for the other callers: gatk-haplotype,samtools,freebayes.
Could you please check this?
Thanks!
Sergey

Sergey;
Thanks much for the report. I tried to replicate this on a simple test case but Platypus appears to do the right thing for me: it pulls the sample names from the BAM read groups and applies them correctly. A couple of thoughts/ideas for debugging:

Are you running alignment with bcbio so it sets the read groups correctly?
Is it possible you have some older version of platypus on your PATH? The bcbio shipped version (0.8.1) appears to do the right thing.

Any other information you can supply to help replicate would be really helpful. Thanks again for the report and help debugging.

Hi Brad!
Thanks for helping with that issue.

Yes, I'm running bcbio starting from fastq files, so the alignment step has been done with bcbio.
And freebayes uses the same bam file to produce correct sample names in the vcf.
No, I'm using platypus from bcbio and I don't have another one in the PATH.

I hope it is platypus 0.8.1-1:
ls -l `which -a platypus`
/hpf/largeprojects/ccmbio/naumenko/tools/bcbio/bin/platypus -> ../anaconda/bin/platypus

ls -l /hpf/largeprojects/ccmbio/naumenko/tools/bcbio/anaconda/bin/platypus
/hpf/largeprojects/ccmbio/naumenko/tools/bcbio/anaconda/bin/platypus -> ../share/platypus-variant-0.8.1-1/platypus

but in the beginning of the vcf file platypus writes:
gunzip -c platypus.vexomes-chr4_0_36067222.vcf.gz | head -n3
##fileformat=VCFv4.0
##fileDate=2017-06-26
##source=Platypus_Version_<IP_ADDRESS>

Any ideas?
Sergey

Sergey;
Thanks for following up. I read through the Platypus code and it looks like it will fall back to using the filename if parsing the BAM file fails:
https://github.com/andyrimmer/Platypus/blob/master/src/cython/platypusutils.pyx#L142
so that explains what you're seeing but I'm not sure why the parsing of the BAM file fails. If you could manually run one of the platypus callVariants command lines from log/bcbio-nextgen-commands.log and edit to increase verbosity (--logFileName test.log --verbosity=3) then you should hopefully be able to see a log message about why it failed which should give us some clue to debug more. Hope this helps some with identifying the underlying issue.

Thanks so much, Brad, what a brilliant debug!
The platypus error was:
2017-06-27 16:37:48,350 - DEBUG - Error in BAM header sample parsing. Error was
unknown field code 'AH' in record 'SQ'

2017-06-27 16:37:48,350 - DEBUG - Adding sample name IV3-sort

It is hg38. In the bam header there are records like
@SQ	SN:chr1_KI270762v1_alt	LN:354444	AH:*
@SQ	SN:chr1_KI270766v1_alt	LN:256271	AH:*
@SQ	SN:chr1_KI270760v1_alt	LN:109528	AH:*
@SQ	SN:chr1_KI270765v1_alt	LN:185285	AH:*

So the error comes when using platypus with hg38.
Will remove_extracontigs or hg38_noalt help?
Sergey

Sergey;
Thanks so much for the details from the debug log. I sent a PR upstream to Platypus to fix the issue and will work on rebuilding a new bioconda package with the fix after that gets merged. AH values are valid SAM and the parser in Platypus only preceeds them so hopefully adding this all in gets it fixed correctly. Thanks again.

Sergey;
I haven't heard from the Platypus team but pushed a new release to my branch with this fix and updated the bioconda package. If you update your tools (bcbio_nextgen.py upgrade --tools) or just Platypus (bcbio_conda install -c conda-forge -c bioconda platypus-variant) it should give you the fixed version. Removing the platypus directory of the old calls and re-running will hopefully give you output with the correct sample names. Thanks again for the help debugging this.

Thanks, it works - passed the platypus step.
SN


[Admin/Catalog of streetcodes] StreetCodes remain displayed in the list after deletion

Environment: All
Reproducible: Always
Build found: 79fb490
Preconditions

The site is open.
Logged in as an admin.
At least 3 StreetCodes have been created.

Steps to reproduce

Go to the 'Стріткоди' page.
Click on the 'Trash Delete' button for some StreetCodes.
Reload the page.

Actual result
Deleted StreetCodes still appear in the list.
https://github.com/ita-social-projects/StreetCode/assets/135108144/8983e28e-9a70-4934-b856-25e2f6e5b90e
Expected result
Deleted StreetCodes don't appear in the list.
User story and test case links
User story #1160
[Test case] #1078

A streetcode can be deleted if the images from the art gallery are used in the templates. However, if the images remain only in the art gallery and are not added to the templates, the streetcode cannot be removed from the list.

cannot reproduce this bug

Not reproducible .


translate readme.md to indonesian language

Description of the change:
Reason for the change:
Link to original source:

Closes #

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for your contribution. Check out our issues tab for a list of work that needs to be completed.


How to get runame from Ebay Sandbox?

Please explain how to get runame from Ebay Sandbox account

[runame ]
read this

https://developer.ebay.com/my/auth?env=sandbox&index=0&auth_type=oauth


[paho-mqttpp3] Update version to 1.4.1

Fix https://github.com/microsoft/vcpkg/issues/39826

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

All features are tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-stataic


Remove high/critical vulnerabilities in kubeclarity's components

Is your feature request related to a problem? Please describe.
Current version of kubeclarity (2.3.0) has some high and/or critical vulnerabilities in some of its components.
In particular:
❯ grype --add-cpes-if-none --only-fixed --fail-on high ghcr.io/openclarity/kubeclarity:v2.3.0
 ✔ Vulnerability DB        [no update available]
 ✔ Pulled image
 ✔ Loaded image
 ✔ Parsed image
 ✔ Cataloged packages      [164 packages]
 ✔ Scanned image           [3 vulnerabilities]

NAME                              INSTALLED  FIXED-IN  TYPE       VULNERABILITY        SEVERITY
github.com/containerd/containerd  v1.6.0     1.6.1     go-module  GHSA-crp2-qrr5-8pq7  High

❯ grype --add-cpes-if-none --only-fixed --fail-on high docker.io/bitnami/postgresql:11.13.0-debian-10-r40
 ✔ Vulnerability DB        [no update available]
 ✔ Pulled image
 ✔ Loaded image
 ✔ Parsed image
 ✔ Cataloged packages      [122 packages]
 ✔ Scanned image           [254 vulnerabilities]
NAME                            INSTALLED              FIXED-IN                 TYPE       VULNERABILITY        SEVERITY
dpkg                            1.19.7                 1.19.8                   deb        CVE-2022-1664        Unknown
github.com/opencontainers/runc  v1.0.1                 1.1.2                    go-module  GHSA-f3fp-gc8g-vw66  Medium
github.com/opencontainers/runc  v1.0.1                 1.0.3                    go-module  GHSA-v95c-p5hm-xq8f  Medium
gzip                            1.9-3                  1.9-3+deb10u1            deb        CVE-2022-1271        Unknown
libgmp10                        2:6.1.2+dfsg-4         2:6.1.2+dfsg-4+deb10u1   deb        CVE-2021-43618       High
libgssapi-krb5-2                1.17-3+deb10u2         1.17-3+deb10u3           deb        CVE-2021-37750       Medium
libicu63                        63.1-6+deb10u1         63.1-6+deb10u2           deb        CVE-2020-21913       Medium
libk5crypto3                    1.17-3+deb10u2         1.17-3+deb10u3           deb        CVE-2021-37750       Medium
libkrb5-3                       1.17-3+deb10u2         1.17-3+deb10u3           deb        CVE-2021-37750       Medium
libkrb5support0                 1.17-3+deb10u2         1.17-3+deb10u3           deb        CVE-2021-37750       Medium
libldap-2.4-2                   2.4.47+dfsg-3+deb10u6  2.4.47+dfsg-3+deb10u7    deb        CVE-2022-29155       Critical
libldap-common                  2.4.47+dfsg-3+deb10u6  2.4.47+dfsg-3+deb10u7    deb        CVE-2022-29155       Critical
liblzma5                        5.2.4-1                5.2.4-1+deb10u1          deb        CVE-2022-1271        Unknown
libsasl2-2                      2.1.27+dfsg-1+deb10u1  2.1.27+dfsg-1+deb10u2    deb        CVE-2022-24407       High
libsasl2-modules-db             2.1.27+dfsg-1+deb10u1  2.1.27+dfsg-1+deb10u2    deb        CVE-2022-24407       High
libssl1.1                       1.1.1d-0+deb10u7       1.1.1d-0+deb10u8         deb        CVE-2022-0778        High
libssl1.1                       1.1.1d-0+deb10u7       1.1.1n-0+deb10u2         deb        CVE-2022-1292        Critical
libssl1.1                       1.1.1d-0+deb10u7       1.1.1d-0+deb10u8         deb        CVE-2021-4160        Medium
libxml2                         2.9.4+dfsg1-7+deb10u2  2.9.4+dfsg1-7+deb10u4    deb        CVE-2022-29824       Medium
libxml2                         2.9.4+dfsg1-7+deb10u2  2.9.4+dfsg1-7+deb10u3    deb        CVE-2022-23308       High
openssl                         1.1.1d-0+deb10u7       1.1.1d-0+deb10u8         deb        CVE-2021-4160        Medium
openssl                         1.1.1d-0+deb10u7       1.1.1d-0+deb10u8         deb        CVE-2022-0778        High
openssl                         1.1.1d-0+deb10u7       1.1.1n-0+deb10u2         deb        CVE-2022-1292        Critical
zlib1g                          1:1.2.11.dfsg-1        1:1.2.11.dfsg-1+deb10u1  deb        CVE-2018-25032       High

❯ grype --add-cpes-if-none --only-fixed --fail-on high gcr.io/eticloud/k8sec/grype-server:v0.1.2
 ✔ Vulnerability DB        [no update available]
 ✔ Pulled image
 ✔ Loaded image
 ✔ Parsed image
 ✔ Cataloged packages      [133 packages]
 ✔ Scanned image           [11 vulnerabilities]
NAME                              INSTALLED            FIXED-IN  TYPE       VULNERABILITY        SEVERITY
github.com/containerd/containerd  v1.5.9               1.5.10    go-module  GHSA-crp2-qrr5-8pq7  High
github.com/docker/distribution    v2.7.1+incompatible  2.8.0     go-module  GHSA-qq97-vm5h-rrhg  Low
github.com/hashicorp/go-getter    v1.5.9               1.6.1     go-module  GHSA-fcgg-rvwg-jv58  High
github.com/hashicorp/go-getter    v1.5.9               1.6.1     go-module  GHSA-x24g-9w7v-vprh  Critical
github.com/hashicorp/go-getter    v1.5.9               1.5.11    go-module  GHSA-27rq-4943-qcwp  Medium
github.com/hashicorp/go-getter    v1.5.9               1.6.1     go-module  GHSA-28r2-q6m8-9hpx  High
github.com/hashicorp/go-getter    v1.5.9               1.6.1     go-module  GHSA-cjr4-fv6c-f3mv  High

Describe the solution you'd like
Upgrading postgresql (embedded via bitnami's inner chart) and containerd's vulnerability in main kubeclarity image should solve most vulnerabilities; for grype-server, the issue should be addressed elsewhere (here), I have opened an issue there.
Note that 11.16.0-debian-10-r23 hasn't critical/high vulnerabiities, see:
❯ grype --add-cpes-if-none --only-fixed --fail-on high docker.io/bitnami/postgresql:11.16.0-debian-10-r23

 ✔ Vulnerability DB        [no update available]
 ✔ Pulled image
 ✔ Loaded image
 ✔ Parsed image
 ✔ Cataloged packages      [122 packages]
 ✔ Scanned image           [232 vulnerabilities]

NAME                            INSTALLED  FIXED-IN  TYPE       VULNERABILITY        SEVERITY
github.com/opencontainers/runc  v1.0.1     1.0.3     go-module  GHSA-v95c-p5hm-xq8f  Medium
github.com/opencontainers/runc  v1.0.1     1.1.2     go-module  GHSA-f3fp-gc8g-vw66  Medium

Describe alternatives you've considered
No other solutions for main kubeclarity image; postgresql could be installed stand-alone and connected to kubeclarity (in the following installations I will use that approach).
Additional context
No additional context

@pbalogh-sa can you please address those issues.
I know that during https://github.com/openclarity/kubeclarity/commit/04b4bf2a0a47bb0eb8c3b7ee5178b71272570c3a you've updated the postgresql so just make sure that the new one is not vulnerable with a fixable vulnerability (I think that init container also need to be updated)

In the case of the containerd issue (https://github.com/containerd/containerd/security/advisories/GHSA-crp2-qrr5-8pq7) the kubeclarity isn't affected by this. The vulnerability can cause issues when you're using this package in CRI when it starts containers.


Add option in portal UI and code for MSIX app attach storage

Based on Dean's feedback and team triage, let's add an option in the portal and Bicep/ARM code to deploy storage container for msix.
Code will be similar to what was built for fslogix files share

Feature/Enhancement moved to ADO board for tracking


[#1440] DB image malformed while scanning blocks

These changes move database read accesses from the Android side to the same dispatcher, SdkDispatchers.DATABASE_IO, which is shared with the Rust layer for writing accesses.
All of the reading is done through SupportSQLiteDatabase.queryAndMap that has been changed
Tested with many wallet restorations attempts on different Android SDK levels from 27-34.
Closes #1440

Note
This code review checklist is intended to serve as a starting point for the author and review, altought it may not be appropriate for all types of changes (e.g. fixing a spelling typo in documentation).  For more in-depth discussion of how we think about code review, please see Code Review Guidelines.

Author

[x] Self-review your own code in GitHub's web interface[^1]
[ ] Add automated tests as appropriate
[ ] Update the manual tests[^2] as appropriate
[ ] Check the code coverage[^3] report for the automated tests
[ ] Update documentation as appropriate (e.g README.md, Architecture.md, etc.)
[x] Run the demo app and try the changes
[ ] Pull in the latest changes from the main branch and squash your commits before assigning a reviewer[^4]

Reviewer

[ ] Check the code with the Code Review Guidelines checklist
[ ] Perform an ad hoc review[^5]
[ ] Review the automated tests
[ ] Review the manual tests
[ ] Review the documentation, README.md, Architecture.md, etc. as appropriate
[ ] Run the demo app and try the changes[^6]

[^1]: Code often looks different when reviewing the diff in a browser, making it easier to spot potential bugs.
[^2]: While we aim for automated testing of the SDK, some aspects require manual testing. If you had to manually test
something during development of this pull request, write those steps down.
[^3]: While we are not looking for perfect coverage, the tool can point out potential cases that have been missed. Code coverage can be generated with: ./gradlew check for Kotlin modules and ./gradlew connectedCheck -PIS_ANDROID_INSTRUMENTATION_TEST_COVERAGE_ENABLED=true for Android modules.
[^4]: Having your code up to date and squashed will make it easier for others to review. Use best judgement when squashing commits, as some changes (such as refactoring) might be easier to review as a separate commit.
[^5]: In addition to a first pass using the code review guidelines, do a second pass using your best judgement and experience which may identify additional questions or comments. Research shows that code review is most effective when done in multiple passes, where reviewers look for different things through each pass.
[^6]: While the CI server runs the demo app to look for build failures or crashes, humans running the demo app are
more likely to notice unexpected log messages, UI inconsistencies, or bad output data. Perform this step last, after verifying the code changes are safe to run locally.

The failing CI check test_robo_demo_app is expected to fail. #1326


Add in operator method to PyAny

We don't have a method for x in foo on PyAny.
We have PySequence::contains - probably this just wants to be copied as PyAny::contains, with some tests to check this does behave like Python's in operator.
As per https://github.com/PyO3/pyo3/pull/1844#issuecomment-1002551273

I'm interested to take this on!
For design purposes, the in keyword means two things in Python. This was kind of covered in the linked PR where there was discussion of contains_key but I think it was kept out. The idea here then is to use PySequence_Contains for PyAny::contains, right? Is there any need to do a check first?

Great, thank you!

The idea here then is to use PySequence_Contains for PyAny::contains, right? Is there any need to do a check first?

Yes, I think probably calling PySequence_Contains is all the implementation needs. A few tests should be able to confirm that it behaves as expected.


write error doc for "fetch cannot load localhost:3000"

fetch('localhost:3000').then(response => response.json()).then(json => console.log(json));

solution: prepend http:// to localhost:3000.
https:// will probably throw an SSL error


Add FreeBSD tester to CI

oo

i think it'd be good, not sure i have much in the way of validation that the crate works on those platforms, but happy to merge this in


Commerce

Coverage increased (+0.2%) to 41.054% when pulling 3b9757e60c3cdb3e587329bbdeb3fbd234fc591a on lmazuel:commerce into 60581e46c4afe2ddea0fbf225500a4255dbf7d0f on Azure:dev.


Fix some undefined behavior

redisSSLContextError must always be initialized at defintion,
otherwise when SSL connect succeeds it may not be assigned to a valid error.
Thus the memory trash remains in the variable, which may sign a misleading error.

Closes #960


add detection  result

RepVGG is a great work! A novel method to compress the network! I will try it when I am free.
RepVGG is better than Resnet for classification, but how it does for detection? Is RepVGG a good backbone for detection?

I also wang to know is it a good backbone for segmentation. Thanks.


Expertiza: Refactor update and signup_as_instructor_action methods

Please set the title of your pull request in the following format: [Project id/Independent study/Issue fix/...]. project name, eg., E904. Integrating courses and assignments on Expertiza with Moodle
We suggest you including the below information in your pull request:

A description of the changes proposed in the pull request.
@mentions of the person or team responsible for reviewing proposed changes.

About the Expertiza Bot

If you have any questions about comments given by the expertiza-bot (example), you could create a new comment in your pull request with the content /dispute [UUID1] [UUID2] (example), then the professor and TAs will be notified.
Here is a video about how to communicate to the expertiza-bot.

2 issues has been closed
The update method has been refactored so that only the instance variables needed are kept.
The signup_as_instructor_action function has been refactored with changes in variables name to enhance code readability and redirection statement is made cleaner


Make sx tests works with PyQt4/python2.7 on Windows

This PR fixes tests on sx.contour3d with PyQt4 on Python2.7 on Windows.
closes #1699

LGTM


Modified the interval and data values to see if that fixes those random ...

...test failures.  Not merging this PR yet, this is a test to see if travis holds up for an extended period with these values.

"Flop Show" :)


Hydration mismatch on undefined attribute

Vue version
3.4.10
Link to minimal reproduction
https://stackblitz.com/edit/vue-issues-10081
Steps to reproduce
<template>
  <div>
    <span :draggable="undefined" :disabled="undefined" />
  </div>
</template>

What is expected?
No hydration error
What is actually happening?
Hydration error
System Info
No response
Any additional comments?
No response

Could be related, but looks like the issue below was fixed in the v3.4.10.
With v3.4.9 the code <input :maxlength="undefined" /> also causes the hydration issue
[Vue warn]: Hydration attribute mismatch on <input value>
  - rendered on server: maxlength="undefined"
  - expected on client: maxlength=""

Reproduction link: https://stackblitz.com/edit/nuxt-starter-ginvlp

@manniL yeah, and I can confirm that mine one was just fixed in the v3.4.10 a couple of hours ago 😅


How to remove the progress?

Please help me with removing the progress shown above the seekbar. I have separate TextView's to perform this task.

My need was shown in the above figure rounded. Please tell a way to remove it.
Thanks.

You can disable them from either XML or Java. Check out the demo app.
https://github.com/anothem/android-range-seek-bar/blob/master/rangeseekbar-sample/src/main/res/layout/main.xml#L125

Worked. Thanks.


Add Pricing to Orphaned Azure Services with Retail Rates Prices API to Advisor Cost Optimization Workbook - to justify orphaned service cleanup.

📝 Scenario
Persona: This scenario is for the financial controller of the organization, who is responsible for overseeing the financial health and ensuring cost-effectiveness within the Azure environment.
Action: The financial controller needs to analyze the Cost Optimization Workbook to identify and address the issue of orphaned services, which are incurring unnecessary costs.
Goal: The ultimate goal is to optimize the Azure environment for cost-efficiency, ensuring that resources are utilized effectively, and expenses are justified, leading to a better return on investment (ROI).
Need: This is needed because maintaining financial discipline is crucial for the organization's stability and growth. Identifying and eliminating wasteful expenditure on orphaned services will contribute significantly to the organization's financial health.
💎 Solution
Solution Overview: The solution will utilize the Azure Retail Rates Prices API to provide a high-level estimate of the cost savings achievable by removing identified orphaned services within the organization's Azure environment.
Outcome: The Financial Analyst will receive a report detailing the estimated monthly and annual cost savings that could be realized if the orphaned services are decommissioned. This report will be generated by cross-referencing the list of orphaned services with the pricing data retrieved from the Azure Retail Rates Prices API, considering the specific SKUs and regions applicable to the organization.
Value Proposition: By providing a quantifiable financial impact, the organization can make informed decisions on resource management, leading to improved cost efficiency and a stronger ROI focus.
📋 Tasks
### Required tasks
- [X] Identify Orphaned Services: Compile a comprehensive list of all orphaned services currently running in the Azure environment.
- [X] Gather Service Details: For each orphaned service, collect relevant details such as service type, SKU, and region.
- [ ] Access Azure Retail Rates Prices API: Obtain necessary permissions and access to the Azure Retail Rates Prices API.
- [ ] Retrieve Pricing Data: Use the API to fetch the current retail rates for the identified services based on their SKUs and regions.
- [ ] Calculate Estimated Savings: Cross-reference the orphaned services list with the pricing data to calculate the potential monthly and annual cost savings.
- [ ] Prepare Savings Report: Compile the findings into a clear and concise report, highlighting the estimated cost savings.
- [ ] Review and Validation: Ensure the accuracy of the report by cross-checking the calculations and data used.
- [ ] Decision Making: Based on the report, decide on the next steps for decommissioning the orphaned services.
- [ ] Monitor Impact: After the changes are implemented, monitor the Azure environment to ensure the expected cost savings are realized.

ℹ Additional context
The Azure Retail Rates Prices API was chosen for its ability to provide detailed and up-to-date pricing information, which is essential for accurately estimating the potential cost savings from removing orphaned services. This approach aligns with the goal of providing a clear financial impact assessment to support informed decision-making within the organization.
The parameters needed to call the API are already gathered by the Cost Optimization Workbook. It is now the "simple" task to apply the API next to it.
🙋♀ Ask for the community

Please vote this issue up (👍) to prioritize it and leave your comments below to help us refine our vision.
We're seeking your insights and expertise to enhance our solution for Azure Cost Optimization. Your contributions are vital to refining our approach and ensuring its success.

Adding the blocked status as this is pending on ADX support to be released.


add additional data types allowed

@saraford

@spottedmahn : Thanks for your contribution to the Azure documentation! The author, @swkrish, has been notified to review your proposed change.

@swkrish Please review these changes and sign-off as soon as possible. Thanks.

Sent email to author @swkrish

#sign-off

Page link


Fixes CardFlight integration

This PR unblocks work on our Q4 Kiosk Updates.
This reverts #687. See this Jira ticket for more info. We need to build against Xcode 9 because Xcode 10 removes libstdc++.6.0.9 and CardFlight v3 requires it to link against. To that end, I'm merging into the Xcode-9 branch, which can run parallel to master for now.
In the mean time, this PR also includes a fix for the initial problem that prompted me to upgrade to CardFlight 4:
https://github.com/artsy/eidolon/commit/2a2a48f521c82add23de26dbdb746c71df7f9f2d

Okay..... Circle CI needs upgrading too. I've opened a ticket to track that and have verified that the tests pass locally.


add: language selection

Active language selection: Japanese and Traditional Chinese
Add new menu item: Select Language
PS: Both these CSV will opensource on my personal website base on the GitHub page, just check it if you warning about it, also I can keep maintaining the Traditional Chinese  skill.csv, but for Japanese, I believe that others contributor can take the responsibility :D

Thank you for the addition!


[impeller] OpenGL ES linker failures must dump program info log.

Right now, the only error returned to the caller is a generic "link failed" message. The program info log (obtained via glProgramInfoLog) must be obtained as well.

@bdero I used this to figure out why the Impeller program wasn't linking and now I have nightmares :(

Haha, love it! At a glance, the surface albedo/shadow contribution and noise sampling all look correct. Just the cubemap contribution seems to be broken. Amusingly, the sampled color appears to be largely tied to the underlying fragment block as opposed to the sample direction. Pretty sure I forget something silly when adding the cubemap support blind.


NFR: Add all the icons for Mack trucks in the codebase

Include both empty icons and stroke icons (?)
https://ourbrand.macktrucks.com/mack-brand-identity-guidelines/graphic-elements#Icons1
Figma - Core design kit - Icons
Add only the icons that are required for redesign

@ZoeBeykirch can we get the full list of icons used in redesign? Thank you!


update to 24.0.0

This is a PR with code automatically generated by the PiT script which follows patterns explained in the upgrading guide for v24.
It works in dev-mode mvn, but fails to package for production mvn package -Pproduction,it because of ITs. When packaging for production mvn package -Pproduction it produces a .jar that can be run java -jar target/*.jar but UI does not load after login.
Can @marcushellberg take a look since you recorded the tutorial ?

@manolo I marked this ready. Build now works, even on my mac that had some ChromeDriver issues. Some issue with the TeamCity setup, but I'm claiming it's environment for that (which should probably be fixed).


Fail to decompress buffer

This is really strange, I am able to compress but fail to decompress a "specific" set of data buffer. I am using static linking with following configuration:
#define HEATSHRINK_STATIC_INPUT_BUFFER_SIZE 512
#define HEATSHRINK_STATIC_WINDOW_BITS 10
#define HEATSHRINK_STATIC_LOOKAHEAD_BITS 3

uint8_t compressed[] = {
0x80, 0x80, 0x35, 0x45, 0x01, 0x7B, 0xA9, 0x07, 0x01, 0xF4, 0x01, 0xB0, 0x00, 0xE0, 0xA0, 0x0D,
0x45, 0x80, 0x5E, 0x82, 0x00, 0x35, 0xA8, 0xB7, 0x4F, 0x7E, 0x10, 0x89, 0x10, 0x03, 0x33, 0x3A,
0x2C, 0xBA, 0x21, 0x7C, 0x04, 0x87, 0xE1, 0x42, 0xB2, 0x7C, 0xE7, 0xFF, 0x88, 0x70, 0x26, 0x20,
0x00, 0xC2, 0xE0, 0x70, 0x10, 0x16, 0x82, 0x9F, 0x00, 0x1C, 0x00, 0x70
};

/* Actual input */
uint8_t decompressed[] = {
0x01, 0x00, 0x00, 0x00, 0x45, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xD4, 0x07, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x00, 0x00, 0x00, 0x16, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x04, 0x00, 0x00, 0x00, 0xA8, 0x6E, 0x3D, 0xF0, 0x08, 0x22, 0x3D, 0xF0, 0x33, 0x45, 0x2E, 0x10, 0x7C, 0x01, 0x00, 0xF0, 0x42, 0x64, 0xF3, 0x3F, 0xF8, 0x0E, 0x00, 0x05, 0x05, 0x05, 0x0B, 0x03, 0x01, 0x64, 0xF3, 0x3F, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
};

I have also attached my test application. So problem is:
If I try to "only" decompress the compressed buffer, I run into a never ending loop of poll. However if I first compress the "decompressed" buffer and then decompress in the same application everything works. I am not able to understand why?
to check both usecases, make if 0 @line 202 to 1
test_heatshrink.txt
PS: Rename file to .c

Thanks for providing a detailed test set. I will look into this over the weekend. One more detail: what version of heatshrink are you seeing this behavior in?

I can reproduce the issue with the code you sent. (Again, thanks.) It looks like your test code is getting stuck in the do-while loop on lines 85-91 forever, because you're calling heatshrink_decoder_poll with an out_buf_size argument of 0. It returns HSDR_POLL_MORE, indicating that it needs a fresh buffer. It can't do any further decompression because you've just handed it a buffer with 0 bytes of space left. This isn't an error condition (dpres < 0), but it also doesn't cause any progress, and you keep retrying forever.
Typically, after filling the buffer, its contents would get flushed out to a file / socket / flash ROM / etc., and then heatshrink_decoder_poll would be called with the full buffer available again.
(It looks like when you're also compressing, the buffering is different, so it's not running into the issue.)
This isn't a bug, it's a misuse of the API, but it's a something that could be documented more clearly. Any suggestions?

Thanks for the pointer... I found some issue in the test code.
Issue: outsize was lesser than the required size. inlen is 60 so according to following statement:
outsize = inlen + inlen / 2 + 4;
outsize was always lesser than decompressed size (100 bytes). Hence it loops forever
I did a test by setting outsize to 100 bytes since my final data is 100 bytes as I know. so changing above to:
outsize = 100;
also loops forever, it only works if I set it to 101. So the question why 1 byte extra?
PS: I am using latest git version.

Did you get a chance to test with outsize set to 100?

Not yet.

ok.. just want to summarize, if buffer length == decompressed data length algorithm goes into infinite loop (waiting for buffer I guess).

I think it's still due to misuse of the API. You aren't calling heatshrink_decoder_finish until execution gets outside the loop the code is stuck in, but it can't make progress without extra buffer space (even though it shouldn't be necessary) because it doesn't know that it has all the input. (Except at the end of the stream, it always needs to work with a consistent amount of buffer space - otherwise, working in different chunk sizes would lead to incompatible results.)
The test and CLI code your appears to be based on gets around this problem by putting the output buffer's contents into a file/output stream and resetting it, and by notifying when the end of input is reached.
Essentially, if you call heatshrink_decoder_poll and get a response of HSDR_POLL_MORE, you must flush your output buffer before calling it again.

Ok, I will take a look at the APIs again. There is little documentation so I might have missed something. My application is based on sample codes provided and I used them with little modification.

Replying too late :)
After you explained about API, I made changes to code and found that I was not using it correctly. However I blame ( :p ) the confusing test code for this as I followed it and not much documentation available for this library.
Thanks for your input I am able to get it working perfectly. My example code can be a good starting point for those looking for a simple compress/decompress function. Can I submit it in this library for anyone to use it?


doc: releaes: remove v3.3.0 from supported releases

As of October 31, 2023, Zephyr v3.3.0 is no longer supported.

I suggest we make an effort to merge the currently open backports against v3.3 prior to merging this PR.

See https://github.com/zephyrproject-rtos/zephyr/pull/60311

@kartben Updated, thanks.


[MTSRE-1471] Fix race condition in objectset handover integration tests

by moving  assertions that should happen after the new object set becomes available after the code that waits for it to become available.
Previous to this fix, testing a cpu-starved PKO would often result in a failure when the tests asserted that object had already fully been handed over, when pko only had reported that the new object set was already created and unavailable due to failing probes on an already existing object.
    hypershift_test.go:91:
        	Error Trace:	/home/erdii/projects/redhat/github.com/package-operator/package-operator/integration/package-operator/objectset_test.go:763
        	           				/home/erdii/projects/redhat/github.com/package-operator/package-operator/integration/package-operator/objectset_test.go:505
        	           				/home/erdii/projects/redhat/github.com/package-operator/package-operator/integration/package-operator/hypershift_test.go:91
        	Error:      	Should be true
        	Test:       	TestHyperShift/ObjectSetHandover
        	Messages:   	controller name of default-test-hc/cm-1 not prefixed with test-rev2
--- FAIL: TestHyperShift (74.36s)
    --- PASS: TestHyperShift/HyperShift_Installation (1.11s)
    --- PASS: TestHyperShift/ObjectSetSetupPauseTeardown (17.16s)
    --- FAIL: TestHyperShift/ObjectSetHandover (2.04s)
FAIL

PS: why does go mod tidy bump a dependency here?

Summary

Change Type

Bug Fix

Check List Before Merging

[x] This PR passes all pre-commit hook validations.
[x] This PR is fully tested and regression tests are included.
[x] Relevant documentation has been updated.

Additional Information

Reproducing the bug can by done by patching the pko deployment template file and removing pko package test-fixtures prior to running the integration tests on main.
Validating the fix can be done by then checking out the fix (while keeping the patched deployment template), and rerunning integration tests (with a cluster teardown in between).
# removing package test fixtures
rm -rf packages/package-operator/.test-fixtures

# patching the deployment template:
git apply <(cat <<EOF
diff --git a/config/packages/package-operator/package-operator-manager.Deployment.yaml.gotmpl b/config/packages/package-operator/package-operator-manager.Deployment.yaml.gotmpl
index 72bc06b..6ff9b6e 100644
--- a/config/packages/package-operator/package-operator-manager.Deployment.yaml.gotmpl
+++ b/config/packages/package-operator/package-operator-manager.Deployment.yaml.gotmpl
@@ -93,10 +93,10 @@ spec:
         # default resources
         resources:
           limits:
-            cpu: 200m
+            cpu: 10m
             memory: 400Mi
           requests:
-            cpu: 200m
+            cpu: 10m
             memory: 300Mi
 {{- end}}
 {{- if hasKey . "environment" }}
EOF
)

# recreating cluster and running integration tests:
./mage dev:teardown dev:integration

Superseded by https://github.com/package-operator/package-operator/pull/495


Add Statbot metric logging

🚀 Deployed on https://6445992234418c04b700b7fd--cozy-fox-0defec.netlify.app


Upgrade to latest Replicate client library, get Llama 3 working

Thanks - I need to upgrade this plugin to the latest Replicate library version and make a bunch of changes.

Originally posted by @simonw in https://github.com/simonw/llm-replicate/issues/24#issuecomment-2068518475

Step one:
diff --git a/pyproject.toml b/pyproject.toml
index e541b67..c893fdd 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -11,9 +11,9 @@ classifiers = [
 dependencies = [
     "llm",
     "requests-mock",
-    "replicate>=0.9.0",
+    "replicate>=0.25.2",
 ]
-requires-python = ">3.7"
+requires-python = ">3.8"

 [project.optional-dependencies]
 test = ["pytest"]

It supports streaming now:
import replicate

# https://replicate.com/meta/llama-2-70b-chat
model_version = "meta/llama-2-70b-chat:02e509c789964a7ea8736978a43525956ef40397be9033abf9fd2badfe68c9e3"

for event in replicate.stream(
    model_version,
    input={
        "prompt": "Please write a haiku about llamas.",
    },
):
    print(str(event), end="")

It prefers you to use a REPLICATE_API_TOKEN environment variable but you can still create a Client() and pass it api_key= to its constructor I think.

For Llama 3 this post: https://replicate.com/meta/meta-llama-3-70b-instruct?input=python suggests this:
# The meta/meta-llama-3-70b-instruct model can stream output as it's running.
for event in replicate.stream(
    "meta/meta-llama-3-70b-instruct",
    input={
        "top_k": 50,
        "top_p": 0.9,
        "prompt": "Work through this problem step by step:\n\nQ: Sarah has 7 llamas. Her friend gives her 3 more trucks of llamas. Each truck has 5 llamas. How many llamas does Sarah have in total?",
        "max_tokens": 512,
        "min_tokens": 0,
        "temperature": 0.6,
        "prompt_template": "<|begin_of_text|><|start_header_id|>system<|end_header_id|>\n\nYou are a helpful assistant<|eot_id|><|start_header_id|>user<|end_header_id|>\n\n{prompt}<|eot_id|><|start_header_id|>assistant<|end_header_id|>\n\n",
        "presence_penalty": 1.15,
        "frequency_penalty": 0.2
    },
):
    print(str(event), end="")

Note the need for a prompt_template of "<|begin_of_text|><|start_header_id|>system<|end_header_id|>\n\nYou are a helpful assistant<|eot_id|><|start_header_id|>user<|end_header_id|>\n\n{prompt}<|eot_id|><|start_header_id|>assistant<|end_header_id|>\n\n".

https://github.com/meta-llama/llama3?tab=readme-ov-file#instruction-tuned-models says:

The fine-tuned models were trained for dialogue applications. To get the expected features and performance for them, a specific formatting defined in ChatFormat
needs to be followed: The prompt begins with a <|begin_of_text|> special token, after which one or more messages follow. Each message starts with the <|start_header_id|> tag, the role system, user or assistant, and the <|end_header_id|> tag. After a double newline \n\n the contents of the message follow. The end of each message is marked by the <|eot_id|> token.

Useful example code from https://github.com/meta-llama/llama3/blob/87d55e86f7170e31c6f46b8f521ed65242109938/llama/tokenizer.py#L202-L229
class ChatFormat:
    def __init__(self, tokenizer: Tokenizer):
        self.tokenizer = tokenizer

    def encode_header(self, message: Message) -> List[int]:
        tokens = []
        tokens.append(self.tokenizer.special_tokens["<|start_header_id|>"])
        tokens.extend(self.tokenizer.encode(message["role"], bos=False, eos=False))
        tokens.append(self.tokenizer.special_tokens["<|end_header_id|>"])
        tokens.extend(self.tokenizer.encode("\n\n", bos=False, eos=False))
        return tokens

    def encode_message(self, message: Message) -> List[int]:
        tokens = self.encode_header(message)
        tokens.extend(
            self.tokenizer.encode(message["content"].strip(), bos=False, eos=False)
        )
        tokens.append(self.tokenizer.special_tokens["<|eot_id|>"])
        return tokens

    def encode_dialog_prompt(self, dialog: Dialog) -> List[int]:
        tokens = []
        tokens.append(self.tokenizer.special_tokens["<|begin_of_text|>"])
        for message in dialog:
            tokens.extend(self.encode_message(message))
        # Add the start of an assistant message for the model to complete.
        tokens.extend(self.encode_header({"role": "assistant", "content": ""}))
        return tokens

The challenge in implementing this is figuring out what to do about those prompt templates.
I think I need model card support - I need to give users a very quick way to add a model that includes the configured prompt template.
I'm going to delay implementing this until I've figured out the model card mechanism for LLM itself.

Confirmed that this works:
client = replicate.Client(api_token='r8_...')
for event in client.stream(
    "meta/meta-llama-3-70b-instruct",
    input={
        "top_k": 50,
        "top_p": 0.9,
        "prompt": "Work through this problem step by step:\n\nQ: Sarah has 7 llamas. Her friend gives her 3 more trucks of llamas. Each truck has 5 llamas. How many llamas does Sarah have in total?",
        "max_tokens": 512,
        "min_tokens": 0,
        "temperature": 0.6,
        "prompt_template": "<|begin_of_text|><|start_header_id|>system<|end_header_id|>\n\nYou are a helpful assistant<|eot_id|><|start_header_id|>user<|end_header_id|>\n\n{prompt}<|eot_id|><|start_header_id|>assistant<|end_header_id|>\n\n",
        "presence_penalty": 1.15,
        "frequency_penalty": 0.2
    },
):
    print(str(event), end="")

The trickiest bit of the prompt template will be getting conversation mode to work.


Adds a srun launcher for Slurm.

I tried this with my parsl/psij provider, replacing the use of the parsl-side srun launcher with the psij-side srun launcher.
Then I checked that a small parsl workflow on three slurm nodes still uses all three nodes.

In a few situations, I've wanted to add parameters to srun. In parsl, that's provided as an overrides parameter which pastes arbitrary extra stuff into the command line. I'm not sure if this new laucher implementation would let me easily configure those options.
An example from an LSST parsl configuration: launcher=SrunLauncher(overrides='-K0 -k --slurmd-debug=verbose'),


Update README

Current coverage is 63.86% (diff: 100%)

Merging #1817 into master will increase coverage by <.01%

@@             master      #1817   diff @@
==========================================
  Files           354        354
  Lines         17127      17127
  Methods       16760      16760
  Messages          0          0
  Branches        223        223
==========================================
+ Hits          10938      10939     +1
+ Misses         6189       6188     -1
  Partials          0          0

Powered by Codecov. Last update 1147c87...bc8e83d


🌐 Add Portuguese translation for docs/pt/docs/advanced/path-operation-advanced-configuration.md

Thanks for the contribution @Joao-Pedro-P-Holanda :nerd_face:
And thanks for the help @ceb10n @nazarepiedady :rocket:


Set up ESLint, Prettier and Husky

Fixes Issue
This PR fixes the following issues:
#115 [Feature]: Add Husky with Prettier and ESLint Configuration
Changes proposed

Husky Integration: I will integrate Husky to set up Git hooks, specifically the pre-commit hook, to ensure that code is automatically formatted and checked for linting issues before each commit.

Prettier Configuration: I will add a Prettier configuration file to define code formatting rules for the project. This will ensure that all code adheres to a consistent style.

ESLint Configuration: I will add an ESLint configuration file to define linting rules for the project. This will help catch and prevent common JavaScript and TypeScript coding errors.

Here comes all the changes proposed through this PR

Check List (Check all the boxes which are applicable)

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots and video
NA
Add all the screenshots and a video which support your changes

@NewtonFernandis appreciate your efforts but one more merge conflict has just cropped up. kindly resolve

Resolved @pradeeptosarkar, Let me know if you want me to format all files in this PR

@NewtonFernandis pls check one of the two checks is failing


Improve documentations of all packages

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.

This PR improves documentation (*.md) in all packages with:

spelling correction;
grammar correction and minor improvements;
punctuation correction and minor improvements;
correct captialization for Filament's package names ("form builder" -> "Form Builder", "table builder" -> "Table Builder", etc.)

Tool used: PHPStorm's Grazier plugin (both Pro and Lite) and its Proofreading inspection rules for suggestions. Each change was manually verified before being applied.

The following parts in what-the-diff above are not correct as I don't add anything to existing docs:

Included Helpful Methods
Fixed Documentation for Method Names
Enhanced Repeater and TagsInput Fields

This is great! Thank you so much


[#176] New submitCountryCode option

New submitCountryCode option
Issue: #176
New submitCountryCode option to keep a hidden input with the current dial code. Useful when using nationalMode but still want to submit the dropdown country dial code.
Changelog

Added to new options submitCountryCode and submitCountryCodeName.
Hook into _generateMarkup method to create the hidden input with submitCountryCodeName option as input name.
_updateDialCode method will now update the hidden input value as well.
Added example and spec.

PS: I'm no good with jasmine, so you might want to add some more tests to it :smile:

@jackocnr Travis is failling because I didn't commit the build version (it caused merge conflicts). Thanks.

Hi there, thanks for coding this up, but I would like to discuss this in the issue before I consider including it. I'm going to close this for now, but if you reply to my questions in the issue, then we can come back to this. Thanks.


Task Reflection (M1)

For the milestone one, I have learnt how to make use of the GitHub Project Board to list out all of the tasks
that need to be done. It is an easy way for everyone in the team to see what is being done, currently working on, and what is left to do. Also, using the Gantt Chart helps us plan our project timeline to meet the upcoming deadline. The main part I have learnt is the project development life cycle. The requirement gathering can sound easy. But when we are given the initial requirement, we found out that many things we are unclear of. Having the client meeting really helps us clarify our doubts. But not all doubts were being covered as time wasn’t enough. If given a chance to do it again, I will sort the question according to the importance first as there is limited time.

For the milestone one, I have learnt how to make use of the GitHub Project Board to list out all of the tasks that need to be done. It is an easy way for everyone in the team to see what is being done, currently working on, and what is left to do. Also, using the Gantt Chart helps us plan our project timeline to meet the upcoming deadline. The main part I have learnt is the project development life cycle. The requirement gathering can sound easy. But when we are given the initial requirement, we found out that many things we are unclear of. Having the client meeting really helps us clarify our doubts. But not all doubts were being covered as time wasn’t enough. If given a chance to do it again, I will sort the question according to the importance first as there is limited time.


Sync with changes from NEURON for nrnunits.lib

Corresponding commit in nrnhines/nrn is
https://github.com/nrnhines/nrn/commit/e0950a19a722b661882d1609fe7748ec67b68ba8

@nrnhines : I wasn't aware of the changes in NEURON and hence was getting different result for some of simulations with CoreNEURON.


Vite 3 support

add vite 3 support
add vitest (latest) support
fix issues [33, 37, 38]

quick note, its still beeing worked on! I am currently quite busy to tackle this, vite 3 technically works, but it just doesnt have full esm support! (using type module in package.json)

Part of this PR: https://github.com/Subwaytime/vite-aliases/pull/41
There will be upcoming other changes before a new release is triggered

Will this fix the Typescript issues?

Yes, there is already a pre-release, but i am doing some major rewrites, as the comment json package is causing the esm/cjs issue.

Check the v10 - Development Branch! Prerelease v0.9.5 ensures Vite 3 support and should fix the Bugs above, please report any Bugs that are found! As some parts have changed drastically to fully support esm

@Subwaytime How to install the pre-release version ?

There will be an official release for v10 tomorrow!

Thanks!


Add theme TKL

Thank you so much for your contribution.


What are the permissions needed to be able to Test Send?

Can you please elaborate on the permissions needed for a user to be able to use the Test Send feature of the portal? We currently have a user that has that option disabled. He currently is a member of the Reader role for that Resource Group

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

ID: 4f45da7e-b566-ce6e-f2d3-3e929a87172d
Version Independent ID: 7587047c-cafa-8293-e3d5-1ad3f56bf722
Content: Diagnose dropped notifications in Azure Notification Hubs
Content Source: articles/notification-hubs/notification-hubs-push-notification-fixer.md
Service: notification-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

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

Thanks for looking into this @BryanTrach-MSFT! Any updates...?

@BryanTrach-MSFT - Did you guys uncover anything? Thanks for checking into this!

@jstawski @seangriffin2 I apologize for the delay.
Sending a test notification goes beyond simply reading so the reader role will not work. Since sending test notifications has the ability to reach a wide array of customers, you can only use the default RBAC role of contributor. I assume this is too much access for your use case.
The good news is you can create a custom RBAC role to allow the user only the ability to send test notifications. To do this:

Navigate to the portal
Navigate to All Services> Subscriptions> Your subscription> Access Control (IAM)
Select the 'Add' button and then select 'Add custom role'
Give it a name, description, and start from scratch for baseline permissions
Then select the Permissions tab> Add permissions
Search for Notification
Select Microsoft Azure Notification Hub
Under 'Microsoft.NotificationHubs/Namespaces/NotificationHubs' select 'Other : Send a test push notification.' and then select 'Add'
Edit the scope as necessary

Keep in mind the user will still need the reader role to see the resource as well.
I hope this helps you. If not, please tag me in your reply and we can continue the discussion.

Thank you @BryanTrach-MSFT I didn't know we could create custom roles!


automated login flow

We want to use the mocker to entirely automate the login process. Thus we use a combination of mockMvc / resttempalte to

get the redirect including the SAMLrequest parameter (302 based, redirect based)
call that sso url via rest template
(2) will offer us some kind of either redirect or login form to login with the user (since the request / client is yet not authenicated
we would like to post some kind of form-data request via restTemplate to that form, to authenticate the user and retrieve the session cookie
use the target redirect from d (to the ACS) and follow that redirect using mockMVC - retrieve and ensure the user is logged in

This would test the entire SAML flow without any e2e testing tool and ensure the configuration/filter/provider and so forth are all correctly setup (thats the motivation / value).
Could you give us a hint how to do the part '4.' (anything else is no issue).

we assume the SAMLrequest id needs to be part of that post (context) so the SAMLresponse can be created
which endpoint to use?
what form fields to set (should we just reverse engeneer the fields of the mocker login form?)

If you could share some ideas, this would be awesome!

If you are doing this you might not even need Mock SAML, just take the code we use to generate the samlresponse and generate your own. The other option is to use Mock SAML and a headless browser

i understand the alternatives.
Are there any technical issues why we would not be able to simulate the form post via client?

is there a lot of Javascript involved (crypto)?
CSRF token (which we would need to parse from the html first ,which is not too hard)

Could you elaborate, if possible, what the technical reason might be to not being able to simply use a webclient to simulate the headless browser?

@EugenMayer Makes sense. The main motivation and use for Mock SAML was for our public demo where using Okta is not practical since we need to get users to login to an IdP to experience the demo.


Getting error when try to delete two items consecutively

issue solved. it was my mistake in coding.


ci: drop kind tests from Jenkins too

kind tests were dropped from GHA long time ago as they were time consuming and did not improve test coverage.
Jenkins had those tests still running and they worked fine until they were made HW dependent.
This change drops kind tests from CI completely.

Codecov Report

Merging #1503 (0108bbe) into main (dc6979f) will decrease coverage by 0.07%.
The diff coverage is n/a.

:exclamation: Current head 0108bbe differs from pull request most recent head 23ed789. Consider uploading reports for the commit 23ed789 to get more accurate results

@@            Coverage Diff             @@
##             main    #1503      +/-   ##
==========================================
- Coverage   50.10%   50.04%   -0.07%
==========================================
  Files          43       43
  Lines        4884     4884
==========================================
- Hits         2447     2444       -3
- Misses       2299     2301       +2
- Partials      138      139       +1

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


rsa 4.9

Recipe directory diff between current master and this update:
diff --git a/recipe/meta.yaml b/recipe/meta.yaml
index 36ab20d..f5cb2ab 100644
--- a/recipe/meta.yaml
+++ b/recipe/meta.yaml
@@ -1,5 +1,5 @@
 {% set name = "rsa" %}
-{% set version = "4.7.2" %}
+{% set version = "4.9" %}

 package:
   name: {{ name|lower }}
@@ -7,7 +7,7 @@ package:

 source:
   url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz
-  sha256: 9d689e6ca1b3038bc82bf8d23e944b6b6037bc02301a574935b2dd946e0353b9
+  sha256: e38464a49c6c85d7f1351b0126661487a7e0a14a50f1675ec50eb34d4f20ef21

 build:
   number: 1

Jira ticket:  (-)
The upstream data:
Actions:

Notes:
*
Additional info:

Package's statistics

Priority D | effort: easy | Category: other | subcategory:  | pkg_type: python
Outdated platfroms: 'linux-64', 'linux-aarch64', 'linux-ppc64le', 'osx-64', 'osx-arm64', 'win-64'
Latest version: 4.9
Release on PyPi:

version: 4.9
date: 2022-07-20T10:28:36

PyPi history
Popularity:

3 months downloads: 703423.0
All time:  10135684 downloads -  rsa  4.9  Pure-Python RSA implementation

Other checks:

[ ] Check the pinnings

[ ] Verify that the build_number is correct

[ ] Verify if the package needs setuptools

[ ] Verify if the package needs wheel

[x] pip in test

[ ] Verify the test section

[ ] Verify if the package is architecture specific

[ ] Verify that private modules are not mentioned in the recipe For example: (_private_module)

[x] license_file: LICENSE is present

[x] license_family APACHE is present

[x] License: Apache-2.0
[x] License is spdx compliant

Check if the license identifier has correct name from the SPDX License List

Identifier

Apache-2.0

Check dependency issues:

../aggregate/rsa-feedstock/recipe/meta.yaml
Dependencies: ['pyasn1 >=0.1.3', 'python', 'pip']
noarch:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

linux-64:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

linux-ppc64le:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

linux-s390x:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

osx-64:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

osx-arm64:

py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

win-64:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

Package Build Score: 17

Links:

Anaconda Recipes feedstock
Update branch
conda-forge recipe
PyPI
Diff between upstream and feature branch
Diff between origin and feature branch
The last merged PRs

Updating the recipe:
If the recipe needs additional modification the update branch can be modified. Note that the PR diffs are not updated with these changes.
git clone -b 4.9 git@github.com:AnacondaRecipes/rsa-feedstock.git

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8dvdx86jbb/clone/recipe/meta.yaml:27: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_8dvdx86jbb/clone/recipe/meta.yaml:51: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_8dvdx86jbb/clone/recipe/meta.yaml:51: missing_description: The recipe is missing a description
ERROR: /tmp/abs_8dvdx86jbb/clone/recipe/meta.yaml:51: missing_dev_url: The recipe is missing a dev_url
Errors were found


update readme with bypass device instructions

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Quick backstory — I manage Apple developer accounts for ~100 different customers, some organization accounts, some individual accounts. For the individual accounts, I'm forced to access the Apple developer portal using their credentials which means 2FA in most cases. Thankfully, by coordinating with the customer, I can add my phone as a trusted device so that I don't have to contact them each time I need to access their account or generate a session...
But, the problem arises when I try to generate a web session using fastlane spaceauth -u [apple_id_email]. Since most of these Apple accounts have devices other than my phone registered, fastlane never prompts me to choose my phone for sending the code. Looking at the documentation and this closed issue #10790, there is no way to force fastlane to send the code to a certain number. One option would be to remove all the registered devices from the account, leaving only the desired phone number, but this is problematic because many of the customers I work with are using their devices with Apple throughout the day and logging them out would be BAD. The other option is to take the route recommended in this updated documentation:

Attempt to generate a web session with fastlane spaceauth -u<EMAIL_ADDRESS>and wait for security code prompt to appear
Open a browser to appleid.apple.com or an address that requires you to login with your Apple ID; logout of any previous session
Login with your Apple ID, and when prompted for a security code, request a code be sent to the desired phone
Use the code sent to phone with fastlane instead of with the browser

It isn't an open issue, but it still helps with this closed issue https://github.com/fastlane/fastlane/issues/10790.
Description

Changed the documentation to include a way to bypass trusted devices and use a trusted phone number instead.

See the steps listed in the documentation. I've been able to reproduce the steps, and I've successfully generate a web session multiple times using this method.

I signed it!

let me know if you have any questions on the PR 😄

This looks great on the first look, thanks for your contribution. This should also be applied over here, right? https://github.com/fastlane/docs/blob/master/docs/best-practices/continuous-integration.md

cool, didn't know that existed. yep, let me add something there too

@KrauseFx added similar doc changes in https://github.com/fastlane/docs/pull/729

@joshdholtz done! thanks for taking a look :)

updated the paragraph here, and made identical changes on https://github.com/fastlane/docs/pull/729

Is there a specific reason why you log out from Apple only after you got the "push" 6-digit code, or could steps 1 and 2 just be switched?

@janpio not that i can think of. i believe you could switch those steps without issue. have you tried doing that yourself?

Yeah, I am currently looking into https://github.com/fastlane/fastlane/pull/13554 and https://github.com/fastlane/fastlane/pull/13507 (which automate this process and integrate this into the normal flow) and was just wondering if this might have any influence.

@janpio gotcha. i think my initial thinking on having the prompt display first (before attempting to login via the browser) was that perhaps the layers underlying the login mechanism would detect and only accept codes from where the initial request came from. however, if your testing suggests otherwise, then it probably doesn't matter. i think i've swapped steps 1 and 2 before without issue, but id be curious to know what you see 😄


can;t import or save any macro  since the release of shadowlands

since 9.0.2 i can't use the gse,if i try  to use the send button i got a lua error so i can't use gse:(( help  please.

Hi
As my telepathy has limits, could you please tell me what version of GSE are you using and what the lua error is?
TimothyLuke

On 29 Nov 2020, at 12:09 am, zevathyra<EMAIL_ADDRESS>wrote:

since 9.0.2 i can't use the gse,if i try to use the send button i got a lua error so i can't use gse:(( help please.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi, I had the same issues until version 2.6.31, However i doubt it's a gs issue. I was testing out macros at TD's and even though i was not hitting on the dummy i was in combat. When i changed spot and got out of combat. I started to work again. Cound not save or change etc.

Closing as no information to go on


Insecure password warning - text color

I just noticed that in the latest update the "Insecure password warning" text is black on black. See screenshot

https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox

Tested and confirmed fixed so will close but let me know if you still have the problem and I'll reopen.


JS: Allow user to remove books from bookshelf

PR : https://github.com/c-phelps/cozy-bookshelf/pull/44


Check for NaN in loss gradient of PGD attacks and replace with 0.0

Signed-off-by: Beat Buesser<EMAIL_ADDRESS>Description
This pull request check for elements with NaN in the loss gradient of all PGD attacks and replaces them with 0.0. A warning is logged if an element with NaN is detected.
Fixes #824
Type of change
Please check all relevant options.

[x] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Codecov Report

Merging #883 (bbaf302) into dev_1.6.0 (75a4a27) will decrease coverage by 39.58%.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##           dev_1.6.0     #883       +/-   ##
==============================================
- Coverage      62.67%   23.08%   -39.59%
==============================================
  Files            176      176
  Lines          17311    17320        +9
  Branches        3184     3187        +3
==============================================
- Hits           10849     3999     -6850
- Misses          5251    13016     +7765
+ Partials        1211      305      -906

Impacted Files
Coverage Δ

art/attacks/evasion/fast_gradient.py
10.95% <0.00%> (-58.03%)
:arrow_down:

...ient_descent/projected_gradient_descent_pytorch.py
16.53% <0.00%> (-78.63%)
:arrow_down:

...escent/projected_gradient_descent_tensorflow_v2.py
17.88% <0.00%> (-77.12%)
:arrow_down:

...rt/defences/detector/poison/clustering_analyzer.py
8.22% <0.00%> (-86.71%)
:arrow_down:

...ces/detector/evasion/subsetscanning/scanningops.py
11.59% <0.00%> (-85.51%)
:arrow_down:

art/attacks/evasion/carlini.py
8.40% <0.00%> (-80.87%)
:arrow_down:

...defences/detector/poison/ground_truth_evaluator.py
17.80% <0.00%> (-79.46%)
:arrow_down:

art/metrics/verification_decisions_trees.py
13.75% <0.00%> (-73.02%)
:arrow_down:

... and 116 more


Change the api route from export const MSG='/msg if possible

@akashgreninja Can you assign me this?


Doesn't work?

Not sure, I could be doing something wrong. I'm on Sketch 3.4. These are the steps I took:

Created a new sketch file
Added new artboard (Tablet 7" portrait)
Created a shape, renamed it 'block'.
Duplicated shape twice, so there are 3 in total with identical names.
Used "Set Page's Stylesheet" command for plugin and linked a blank stylesheet 'styles.css'.
Opened styles.css in text wrangler and added some selectors for the block elements.
Saved stylesheet.
Saved sketch file to same directory as stylesheet with same name.
Also tried using "Layout Layers" command.

Nothing happens. Screenshot attached.

Does not work.
Downloaded an example > Open example > Map files > Edit LESS and nothing happens!

@chrisjmartini, @Rayraegah : Could you open up Console.app and see if there are any messages that appear? Also please try the latest version of CSSketch (now with 3.5 supp
ort and Sass support)
Also are you trying this on the Mac App Store version?
If it's still not working please try switching your Security & Privacy setting in System Preferences to Allow app downloads from Anywhere

@JohnCoates I'll install the plugin again and test it against the settings you've recommended.

Hello guys!
It seems to be working for me after enabling Allow app downloads from Anywhere in the Mac settings.
Thanks for this!
Cheers


Add LibMan docs

Addresses https://github.com/aspnet/Docs/issues/7246
The LibMan CLI detail will be added after the supporting NuGet package is published.
Internal Review Pages

LibMan landing page
LibMan VS doc

@guardrex Thank you for the thorough review! There will be a doc for the CLI usage. The NuGet package to support the CLI isn't published yet.

Paging @justcla for a final review.


System.IO.Packaging.dll not moved to libraries after publish

Hello guys, and thanks for this usefull library.
I use it for an asp .net core 7.0 project, it work perfectly after publish, but i notice one dll of my project is not move to the libraries folder, System.IO.Packaging.dll.
Do yo have any idea why ?
thanks !

some special dlls are expected as they are designed to not be moved, this depends on:

Deployment Mode
Project Framework(ASP .NET Core or WPF, etc.)
Shared Runtime Mode
Use or not use patch

you can post your config and compiled app so i can double check if it works as excepted for your project.

I can't really post the app because its a commercial app and the source code is private, but this the configuration :
asp.net core 7.0 project, running a blazor server app, the deployment mode is FileSystem, not self contained, runtime identifier win-64, i don't know if you need more informations ? if needed i can try create a repro project, let me know.

the behavior is highly depends on *.deps.json, you can just upload the *.deps.json and *.runtimeconfig.json, they don't have any sensitive contents and safe to upload.

hello, does there any update on this ?

can you try create a minimum reproductable project?

It seem since .net8.0 we "lost" this dependency (but without impact on our app), so the problem solve by itself, im unable to reproduce the problem, i close this issue, but thanks for your help
"DocumentFormat.OpenXml/2.20.0": {
        "dependencies": {
          "System.IO.Packaging": "4.7.0"
        },
        "runtime": {}
      },

please feel free to reopen if issue still exists.


Updating Boilerplate found a new issue, possibly?

In an early release of the boilerplate I could use the CachedDeliveryClient's GetItemAsync method without any parameters:
var response = await DeliverClient.GetItemAsync<FullWidthContentPage>(PageCodeName);
I updated to the latest release code as of yesterday, and now I receive an error on that line: "parameter cannot be null". To get around it I was able to pass in an empty List but that was the only way I could get it to work. Like so:
var response = await DeliverClient.GetItemAsync<FullWidthContentPage>(PageCodeName, new List<IQueryParameter>());
I believe the issue is in how the code is written in KenticoCloudCacheHelper.cs for the GetIdentifiersFromParameters method, but I am not 100%.
I'm hoping someone can validate my findings, or tell me if I am wrong?

@JanLenoch do you have information about this change you did in the following commit?
https://github.com/Kentico/cloud-boilerplate-net/commit/23c78ac85d6d01df8c807835f9699e111843ac79#diff-e1ac2c647007aa447031861b0a9d79c0L118

I can reproduce that behavior, but I'll need to understand why such an exception happens when there's a default parameter value in the DeliveryClient.GetItemAsync method (in the SDK).
Thanks @mcbeev for reporting it! I'll take a look at it.

Thanks Jan and Ondra, Ill update my project this weekend with the changes.

Thanks for the quick patch gentlemen. Every works without passing any params again. Hurray!


ENG-2128 update table header format

Describe your changes and why you are making these changes
Differentiate the header text for better clarity.
Related issue number (if any)
ENG-2128
Loom demo (if any)
Before:

After:

Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[x] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[N/A] If this is a new feature, I have added unit tests and integration tests.
[x] I have run the integration tests locally and they are passing.
[x] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[x] All features on the UI continue to work correctly.
[x] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

@eunice-chan, thanks for doing this! Can we make the text a little smaller still and explore other types of differentiation? Maybe let's try 12px and dark grey color instead of black. @agiron123, any other suggestsions?

@vsreekanti Something like this?

Yes, I think that looks a lot better! Can we try adding the bolding back to just to compare?

Actually @eunice-chan, I was thinking about this some more — can we add a light grey background to the header cell? Maybe gray50? I think that will help differentiate it nicely.

@vsreekanti
Here is the updated look.

Here it is with me hovering over a row

Looks good to me — thanks @eunice-chan!


On-Premise Workshop Documentation

Added On-Premise Workshop Documentation

Updated On-premises Workshop URI to the master repo


Nginx version to support HTTP2

@ctsims @shubham1g5 I think it makes sense to spin up a separate proxy for staging since the instructions included removing nginx on the system. THoughts?
https://github.com/JeffreyBLewis/WebVoteView/wiki/Instructions-for-upgrading-NGINX-to-allow-HTTP2-support-on-Ubuntu-14.04

@emord Yeah. Lets push this code to staging. We can then run all our integration tests against that and see if anything breaks because of this.

This is on softlayer swiss and staging. will deploy to prod, nic and enikshay on monday-ish
Once this is deployed we can remove the line to remove the old nginx repository and start using http2

Just deployed nginx 1.12.2 to all environments. Going to set up another PR to enable HTTP2 to deploy tomorrow (keeping it to one change at a time).
Couple of commits in here that came from differences on ICDS https://github.com/dimagi/commcarehq-ansible/pull/872/commits/5bb29a49475b905025f2d32a3d93fd9b87382ffd https://github.com/dimagi/commcarehq-ansible/pull/872/commits/2dbc0ce884c97356435cf7a46b95a1b6ff3090fb Guessing @calellowitz or @snopoke have the most context on that
also as noted on #devops swiss is currently on 12.04, so I was unable to deploy to that. I added the ubuntu verison as a variable so that I could change what repo to use on each environment


my side of the story

this is my side of the story, please review:)

Hi! Thanks for your submission.
Unfortunately it seems that there were changes in the main that conflict with yours.
Could you please perform a merge as described in Tutorial 5 slides 82-96 and integrate those changes?
Start with synchronizing your local main with my upstream main as described in slide 86.
We do not want to lose any existing content, so you should keep what others have written and add yours.
You're free to reorganize the content blocks so that it still makes a story, but please do minimal changes
to the content of what others have written to integrate them with yours.
You have time until the 18th of October at 17:00.
If you can't make it by that time or you are done before the deadline,
please add a comment in github so that I can progress with another student.

Hi, since you did not complete this task in time I will continue with others students. You will have a chance to try again later during the course.

Hi! Thanks for your submission.
Unfortunately it seems that there were changes in the main that conflict with yours.
Could you please perform a merge as described in Tutorial 5 slides 82-96 and integrate those changes?
Start with synchronizing your local main with my upstream main as described in slide 86.
We do not want to lose any existing content, so you should keep what others have written and add yours.
You're free to reorganize the content blocks so that it still makes a story, but please do minimal changes
to the content of what others have written to integrate them with yours.
The merges will be approved according to arrival time starting from October 26th, 16.00,
so expect that you need to merge again after that time.
If I do not approve the changes you will be asked to update the content.


[Suggestion] OpenComputers support

Being able to write programs for controlling reactors would be quite useful. A program could monitor the energy usage of what the reactor is powering and scale production, and could shut down a reactor that was overheating (and possibly set off alarms). I usually use OC for automation of many machines, allowing for fine-grained control of what is being made.

Definitely something I wanted to get done earlier, but I had a bit of trouble actually implementing the integration. Once I get the steam turbines and new reactors sorted I will come back to OC support and see if I can get it sorted.

Added in version 2.11a :)


Favicon not showing

This is a pretty easy thing to fix. Could I commit this directly to the branch?


feat: use debug for output messages

I don't know. I reviewed the documentation for debug and it seems like it is best fit for actual debug messages that a developer might turn on for debugging purposes. The messages I'm outputting in this library aren't really debug messages for a developer. They are strings that are meant for any consuming application to write to the console to assist the user.
Now, I can see that there'd be a way to use debug for my purposes but it doesn't really seem like it's then being used as intended.
It might actually be a better fit for me to

return library defined error codes for each error we recognize
potentially include a dictionary of strings that correspond to those error code
Update the consuming applications that I have to console.log the strings based on error code

Here's where I see (just from looking at the documentation) some conflicts between debug messages and user error messages:

the scoping of all messages to a namespace. I supposed I could pass empty string
There's a duration appended to each output message

Example output from a sample app:
$ node local/launch.js
  nodekit Error: Unable to login, Please double check you used the correct credentials +0ms

So I think I'd prefer a different solution. Perhaps the one I outlined above. Just define an enumeration of detected errors and then update each method to either a) return ErrorOrValue responses or b) throw errors with error codes as defined by the enumeration.
With specific error codes being return then the client applications can write out whatever they want to the user.

The other reason to not use debug for this use case is that we may want to actually use debug for actual debug messages.

I don't know. I reviewed the documentation for debug and it seems like it is best fit for actual debug messages that a developer might turn on for debugging purposes

agreed, that's exactly the purpose of debug. A developer writing "awesome new UI" for metasys will need to figure out, why a call to one of your function is returning unexpected data (only 10 row, an error , something else).  He/She might have questions like, how much time does it take to get auth token. vs something there code is doing with the auth token.

The messages I'm outputting in this library aren't really debug messages for a developer. They are strings that are meant for any consuming application to write to the console to assist the user

well, if its a "library", then what you are trying to do is difficult, as an author of the "awesome new UI" I would like to control how i communicate details to my users, they might not be looking at console.
However if this code is just a bunch of reference "scripts" and not a npm "library", then may be outputting to console is fine.

Just define an enumeration of detected errors and then update each method to either a) return ErrorOrValue responses.

👍

or b) throw errors with error codes as defined by the enumeration

👎

The other reason to not use debug for this use case is that we may want to actually use debug for actual debug messages

I understood the need mentioned in the https://github.com/metasys-server/nodekit/issues/3 for the use case of helping the developers using this "library" figure out whats wrong.
In essence, I will close the PR, since this is not the use case you where looking for.
FYI, we should be doing all this good conversation in the "issue" rather then the PR, for documentation purpose.

I would like to control how i communicate details to my users,

Exactly! Hence the reason I wrote the issue

FYI, we should be doing all this good conversation in the "issue" rather then the PR, for documentation purpose.

Indeed

I would like to control how i communicate details to my users,

Exactly! Hence the reason I wrote the issue

FYI, we should be doing all this good conversation in the "issue" rather then the PR, for documentation purpose.

Indeed


#49 Add no inputs label

Added no inputs label.
Before:

After:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 73.225%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
2549

Relevant Lines:
3317

💛  - Coveralls


uffizzi project create

Allow users to create a project from the command line with uffizzi project create. This probably requires adding account context to the config so we know which account to create this project within uffizzi config set account Acme:
$ uffizzi config list
server = app.uffizzi.com
username = gadkins
account = Acme
project = foo-asm8jn

The project should be created in the configured account context.
$ uffizzi project create my-project
Switched to project 'my-project'.
Project slug: my-project-h8b3ev

Alternatively
$ uffizzi project create --name="My Project"
Switched to project 'My Project'.
Project slug: my-project-h8b3ev

Set the new config context to the project that was just created:
$ uffizzi config list
server = app.uffizzi.com
username = gadkins
account = Acme
project = my-project-h8b3ev

If a user or account has zero projects, we should create a default one (randomly generate a name)
If a user has exactly one project available to them, we should assume they want to use that unless they specify otherwise

@gadkins Several questions and comments:

As we don't have slugs for accounts, we still need to rely on account id instead of name (the name is only for the user to understand which account it is), so the actual config would look like this:

uffizzi config list =>

server = http://web:7001
username =<EMAIL_ADDRESS>cookie = _uffizzi_app_session=$cookie
account = {"id"=>3, "name"=>"acme"}
project = default

The uffizzi config set command is used to set the user input to config, but in the case of an account we need to make a request to the backend to find the account id and the user needs to be authenticated by that time. So instead of config I suggest a dedicated account command. In this case, the user story can look like this:

uffizzi account list =>

acme
uffizzi

uffizzi account set-default acme =>

The default account has been updated.
The project with slug 'default-slug' was set as default. # Account had the only project and that project was set as default.

uffizzi config list =>

server = http://web:7001
username =<EMAIL_ADDRESS>cookie = _uffizzi_app_session=session_cookie
account = {"id"=>3, "name"=>"acme"}
project = default-slug

@gadkins If we have the account context, it would be more consistent if the project command also works in this context
uffizzi project list => #only lists projects for the current account

default
uffizzi

uffizzi project describe my-project or uffizi project set my-project =>

The project "my-project" does not exists on account "acme"

Okay makes sense. I think this user story is good.
We should ask the user to select the default account after they login. We can also implement set-default

Testing:
uffizzi account list - lists user's accounts
uffizzi account set [NAME]  or uffizzi account set-default [NAME] - checks if account belongs to the user sets an account to the config file
uffizzi project create [SLUG] - creates a project within the given context
uffizzi project list - lists projects in the current account
uffizzi project set [SLUG] should work with all projects to support GHA/Gitlab CI/CD commands

Execute uffizzi account set [NAME] Name = Name of an existing account, belongs to the user

bash-5.1# be uffizzi account list
ElNealo-New
DbpUffizziTest
bash-5.1# be uffizzi account set ElNealo-New
The account with name 'ElNealo-New' was set as default.
CLI Error:
uninitialized constant #<Class:Uffizzi::ProjectHelper>::Faker

Execute uffizzi account set [NAME] Name = Name of the account which does not exist or does not belong to the user

bash-5.1# be uffizzi account set NotExist
CLI Error:
Server Error:
NoTouching
bash-5.1#

Add help for account commands

Help commands added


Bump cli-builder

Codecov Report

Merging #159 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #159   +/-   ##
========================================
  Coverage    88.49%   88.49%
========================================
  Files           12       12
  Lines          852      852
========================================
  Hits           754      754
  Misses          98       98

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 91cebbd...1878944. Read the comment docs.


ZeroDivisionError: float division by zero

Anybody got this error before?
`/home/ubuntu/anaconda2/envs/python3/lib/python3.5/site-packages/evolutionary_search/init.py in _evalFunction(individual, name_values, X, y, scorer, cv, iid, fit_params, verbose, error_score)
98                 score += _score
99                 n_test += 1
--> 100         score /= float(n_test)
101         score_cache[paramkey] = score
102
ZeroDivisionError: float division by zero`
Here is my EASC call:
gscv = EvolutionaryAlgorithmSearchCV(estimator=KnnDtw(),                                    params=param_grid,                                    scoring="f1_weighted",                                    cv=StratifiedKFold(n_splits=10,                                                       shuffle=False,                                                       random_state=SEED).split(X["eda"], y),                                    verbose=1,                                    population_size=50,                                    gene_mutation_prob=0.10,                                    gene_crossover_prob=0.5,                                    tournament_size=3,                                    generations_number=5,                                    n_jobs=-1)

Can you print what was in n_test before?

I got it, if you scroll up a bit and format the code properly, lines 98 and 99 are nested in an if statement. It never adds anything to n_test, because the length of your test set is 0.
This issue can be closed.


Save Online Project Bug

Describe the bug
The site automatically saves the new project although we press cancel button while the alert asks us whether we want to save the project or not
To Reproduce

Go to Simulator
Draw any circuit(not necessary) click on Project/Save Online.
Press cancel.
Although we press cancel we are redirected to a new page, and our project is saved.
Expected behavior
I don't know whether this is expected behavior or not. But the users should have a way to cancel this so that they will not have unnecessary circuits in their name.

Desktop (please complete the following information):
Chrome
Are you working on this issue? (Yes/No)
No

I'm on the bug though I'll like to know if it is really necessary to ask for the name of the project with the help of the prompt during online save, because we ask for it in the next page anyway.

@shubhankarsharma00 We initially create the project using the name and add data to it in simulator_controller#create and then redirect the user to the actual project edit page, where we can add other parameters like description etc. The name is required to initially create the project and add the simulator data which won't be available on the edit page.
There a few replacements for the current flow that I can think of -

After showing the name prompt(if the name isn't already set) we can have another prompt asking the user if he/she wants to continue working on the project or finish it by adding a description etc. (or)
On clicking the save option, we can open a create page in a modal and send all the project params at once to carry out the create (preferably as projects_controller#create)

In the first one, handling the interim project state might be a hassle. After fixing this issue, we can discuss if the current flow needs to be removed or not. :wink:

@ankitkataria the suggestions are actually really good but I think rather then adding new create page or another prompt we can solve this bug easily: from what I could gather even if we leave the field empty there is a default name for every project so

I think one way can be that we don't prompt the user for the name on the simulator edit page and create the project with a default name(Untitled) and change it on the project edit page.

I think one way can be that we don't prompt the user for the name on the simulator edit page and create the project with a default name(Untitled) and change it on the project edit page.

This sounds great!

or we just somehow fix the prompt to return when there is null input because we'll have to do it for offline save anyway.

Let's first start by fixing this bug, we can look into a different flow once this issue is tackled.

sorry, I am not able to work on this I was busy with some internship work please feel free to approach this issue, anyone.

I'm working on this issue.

@tachyons can we reopen this.


ASI exceptions

You list [ and ( as exceptions for starting new lines without semicolon, someone also added the template string backtick `. There is actually more of those:

unary + and - operators:

foo = bar
+new Date

becomes
foo = bar + new Date

the regex /

foo = bar
/baz/g.test('baz')

becomes
foo = bar / baz / g.test('baz')
That makes it a total of 6 exceptions you have to look out for: [, (, `, +, -, /

look out for

Is a strong word,  seeing as all of these emit glaring warnings

All of those examples parse fine and produce valid code, it can fail on execution with an exception, but if you are unlucky enough with variable naming, it can also execute fine and produce unexpected behavior.

Aye, I get that, and it's certainly great to have a tool that statically checks against it. My comment is solely about the readme, apologies if that wasn't clear. I think people should make informed decisions, but that only works if the information you get is accurate.

@maciejhirsz Thanks for your comments. The reason we omitted the other cases in the readme is that they usually don't appear in real code.
foo = bar
+new Date
/baz/g.test('baz')

is most likely to be:
foo = bar
myFn(+new Date)
var isBaz = /baz/g.test('baz')

The full details are explained in RULES.md which is linked at the bottom of the bulleted list in the README.md. See here: https://github.com/feross/standard/blob/master/RULES.md#helpful-reading


Add uniform design for ReactionChips with 10+ reactions

ReactionsChips with 10+ reactions don't respect the paddings.
(Also, the Tooltip looks silly because it's all in one line.)

8px Padding left & right

@SelinaBuff , can I take up this issue to adjust the padding.
And for the tooltips, we can show the initial 2 to 3 person name followed by the count of remaining person. For example for 6 person reactions we can show something like  ->
person1 , person2, +4 .

@dipesh1903 that would be great! Thank you

@SelinaBuff  , I'm unable to assign this ticket to myself, Can you help me here.
Thanks,

done, see https://github.com/inovex/scrumlr.io/pull/4554 and https://github.com/inovex/scrumlr.io/releases/tag/v3.10.0


Documentation update for Twitter backend

Correction of the key names in the settings file.

Those are keys for python-social-auth, not django-social-auth.


use types-psycopg2

Hello @chdsbd,
In https://github.com/python/typeshed/pull/10630 I added a lot of missing annotations to the typeshed stub of psycopg2 and fixed some others. The improved package is now live on PyPI https://pypi.org/project/types-psycopg2/.
Would you like to give this PR another go?
Also if you add "fixes #74" to the PR description it will close the issue automatically when merged.


feat: Copy block reference

"Copy Note Link", "Copy Note Reference", and "Copy Note URL" commands now support block anchors.
I preserved the existing behavior of these commands, but extended them so that:

If an existing block anchor is selected, it will be copied in the link
For "Copy Note Reference", if multiple lines are selected, the command will insert block anchors (or use existing block anchors or headers), which will be copied in the reference as a range.

Also fixed a bug where if there was a header and block anchor within the same line, the block anchor would be parsed as being part of the header, which means the link wouldn't work when used.

Also replaced the UUID package with nanoid as requested.
Additionally, I made 2 changes in the VSCode settings:

Set the tab width for the workspace as 2. Prettier already formats files to that width, and VSCode recognizes the width in the file and uses it automatically. Without this setting however new files will have 4-space width until prettier runs, which is a minor inconvenience.
Set debugging launch options to skip node internals and mocha library code. This makes debugging easier because VSCode will now skip them when stepping through functions, and will hide or de-emphasize them in the stack trace.

Thanks for the feedback!

this probably shouldn't generate a range. default behavior when you dbl click a line is to also select first part of next line : https://www.loom.com/share/8d15b55eb54b4516bf6d2bc4804c6f78

Good catch, I rarely use the mouse so I wasn't aware of this behavior. Fixed.

looks like copy note link is generating an anchor when the next line is selected? https://www.loom.com/share/8460eee51c354069878cc5d350739907

Same as above, should be fixed now.

shouldn't this generate a block reference anchor?: https://www.loom.com/share/a04e3c2e60954b1bb5f8ebfada833184

I was only generating them if multiple lines were selected. Revised to generate if there is some amount of text selected.

* for subsequent commits, can we avoid force pushing? it might be necessary if you've done a rebase from master but in that case, I would just merge from master instead. this is because we lose the ability to see incremental diffs from the last code review

Thanks, I didn't know how the review UI worked. I'll use merge commits instead.

* it looks like there's a bunch of debugger statements in the code. wonder why the pre-push script didn't catch it

This might have to do with rebasing actually. The hook diffs against what would get pushed to upstream, which might not be reliable when rebasing. Not sure how to get around that, but it shouldn't be a problem once I stop rebasing all the time :smile:

* perhaps separate issue by i notice that `GoToNote` command on a relative link with an anchor no longer goes to the part of the document with the anchor. if its a completely separate issue, no need to do the fix in this PR

I think I have been seeing some intermittent issues with that outside of this branch too, usually "Reload Index" fixes it. I think it has something to do with notes not being updated soon enough, since we now rely on note.anchors to be updated (as opposed to the previous behavior of parsing the note at GoToNote`).