Tarpaulin segfaults on multithreaded raytracer

I suspect this might be related to #190. If so, feel free to close.
I sometimes get a segfault when running Tarpaulin on my multi-threaded raytracer. Here is the link to the exact commit where this is happening: https://github.com/DevJac/rust-raytracer/tree/0c676608b8ee4990369ba7d9129eaf9ffa79b944 It should be a usable test case, there's some hairy math, but it's just boring Rust with a few crates.
Sometimes tarpaulin works correctly, and sometimes it segfaults, and one time it seemed to hang indefinitely. It is random, I would guess it segfaults about 50% of the time or more. I have done a git clean -xdf to ensure I'm starting from a clean slate and I still get the segfault.
cargo test works reliably on the same code base.
My unit tests have been the same for quite awhile, and Tarpaulin has successfully run my tests with all previous version of the code. I recently added multi-threading and now I am seeing this issue. It might be related to the multi-threading?

Yeah this is the same issue as #190 (or at least what #190 revealed in addition to it's initial error). I'm hoping to make some progress with this this weekend so thanks for another test case I can use :+1:

Closing as #190 is closed now


Anymail: Domain Not Found Error

Hi,
Just wanted to report a bug with the anymail integration. I attempted to use anymail and mailgun in production the other day and kept receiving a "Domain Not Found Error". According to the anymail docs, it automatically pulls the domain from the sender (From) address domain. So if your sender address is<EMAIL_ADDRESS>it pulls just xyz.com and not the full domain (with mailgun subdomain) needed to send via mailgun.
I got around this by adding adding another Key Value pair to the ANYMAIL config in production.py so that it reads:
ANYMAIL = {
    "MAILGUN_API_KEY": env('DJANGO_MAILGUN_API_KEY'),
    "MAILGUN_SEND_DEFAULTS":{
        "esp_extra": {"sender_domain": "mailgun.xyz.com"}
    }

I hope this helps someone else if they encounter this issue.

That's odd @mbreisch I don't face these problems you mention. Could this be a DNS Records issue?

@aleprovencio perhaps. But, while following the docs for setting up mailgun I remember it explicitly recommending using a subdomain for the DNS Record required. I followed those recommendations and set it up, with mailgun.mydomain.com. I think anymail expects your DNS Records to have a CNAME for the root domain for mailgun not a subdomain.

I've successfully set mailgun with Route 53, setting the suggested values on the domains:
* txt: mydomain.com and k1._domainkey.mydomain.com
* cname: email.mydomain.com
* mx: mydomain.com

Hope this helps!

@mbreisch @aleprovencio or someone, you have managed to configure mailgun/cookiecuter-django to work without a custom domain ( only using a herokuapp subdomain )

@luzfcb , can't tell about that because I don't heroku, but as you see my settings above I don't use a mailgun subdomain on DNS Records.

@aleprovencio I think I misspoke before regarding the CNAME record, I meant TXT record--it was a long day, I edited that post. I did not set the CNAME or mxrecords as they are optional, I did not need  email tracking or receiving through mailgun. My DNS is Cloudflare and my records for mailgun are:
txt: mailgun.mydomain.com and k1._domainkey.mailgun.mydomain.com.
Thanks for posting your DNS records, I think that pretty much confirms my theory, since the only difference seems to be my use of a subdomain rather than using the root domain for my mailgun txt.
@luzfcb I have not tried this on Heroku itself, but, I've gotten anymail with mailgun to work with a similar PAAS, Flynn, and did not have any issues. I set up mailgun with a domain name I owned that I planned to provide a cname to the Flynn generated subdomain. So I setup the mailgun txt records with mydomain.com and then pointed a cname of mydomain.com to the Flynn url mydomain.flynnhub1.com. Did you setup your environment variables? Are you able to curl to the mailgun api using the credentials you setup with mailgun?

The settings looked like this when this issue was opened:
https://github.com/pydanny/cookiecutter-django/blob/a658339b99a76c8270a9fe418eb3d3edc12a27b2/{{cookiecutter.project_slug}}/config/settings/production.py#L161-L166
Shortly after the last comment, another setting was added to set the domain more easily in https://github.com/pydanny/cookiecutter-django/commit/3d25befb3f43d8965816376a4e64b868e0db6f6d:
https://github.com/pydanny/cookiecutter-django/blob/60ebda8bf7b0cc0c752ff813a125316d3cb79ad3/{{cookiecutter.project_slug}}/config/settings/production.py#L142-L147
Assume this is fixed now, we can re-open if needed.


feat: add GCS support

• added GCS support with service account key
• upgraded version of registry (2.8.2 doesn't have GCS plugin =/)
• added basic docs for GCS support

Thanks for your contribution! It is not our first priority and we need to setup a test environment to validate your work so it will be done but not very soon, but you can hope for end of January I would say.

@Shabablinchikow  @paullaffitte  - it would be great if merge conflicts could be resolved and get this into released version of kuik :+1:

Fixed conflicts

Sorry for the late reply, we had other priority that we had to handle on this project as well as on other ones. I reviewed and tested your code and it works as expected! Thanks for you great work. However your commits doesn't follow conventional commit spec, could you update please so we can merge?

fixed commit message and re-rebased branch

Amazing! Thanks for your quick reply! I'll merge it right now.
PS: I see that you set the registry tag to 2.8.3, we prefer to not lock the patch level so the latest patch level is used by default. I will change that in an another commit after merging.

:tada: This PR is included in version 1.11.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Improve usability for deleting a certificate

Current Implementation
This is a follow-on from https://github.com/corona-warn-app/cwa-app-android/issues/3895 "Cannot remove vaccination certificates"
The app does not describe how to remove a certificate and it is not easy to find the remove menu option for a certificate.
Steps to reproduce

In Android CWA tap on "Certificates" tab
Tap on three-dot symbol and select "Information"
Scroll down to bottom, where it says:"You have the possibility to delete COVID-19 certificates in the app at any time. Until then, the certificates will be stored on your smartphone."There are no instructions here about how to delete a certificate.
Tap "CONTINUE"
Tap Scan button and scan in a certificate
Note that a three-dot symbol appears which contains a menu option "Delete Certificate"
Click back arrow
Now there is no menu available to delete a certificate and no help
With CWA 2.10.1 and later there is however a right arrow to suggest that there is a detailed level which can be called up

Suggested Enhancement

Add some help text about how to delete a certificate
On the view where multiple certificates are listed provide some more obvious way about how to delete a certificate

Expected Benefits

Better user experience. Users should not have to struggle with the simple task of deleting a certificate.

Internal Tracking ID: EXPOSUREAPP-8918

@MikeMcC399 Thanks for the proposal. Internal Tracking ID: EXPOSUREAPP-8918

@MikeMcC399

On the view where multiple certificates are listed provide some more obvious way about how to remove a certificate

Did you know that it's possible to delete certificates from this view?
Here's a screen recording:
https://user-images.githubusercontent.com/67682506/128846627-0f0da3b2-2fd8-46ae-85ea-3fa07ef15adc.MOV

@Ein-Tim
Thanks for the iOS recording. That is interesting to see.
On Android there is no swipe function implemented on individual certificates or right arrow displayed. On Android all you can do is to tap on a certificate which brings the details level of the certificate onto the display where there is no plain text button to remove the certificate. You have to know or guess that the remove function is hidden in the three-dot symbol.

@MikeMcC399
Ah okay, interesting to see that this is only implemented under iOS. Although iOS might be a bit better than Android here, the function to remove certificates is still very hidden.
I hope that the developers find a solution where it's easy for users to remove certificates! Hopefully iOS and Android can also be aligned to each other, this would be nice too!

The in-app documentation and app user interface should be sufficient for users to find how to carry out tasks like removing a certificate.
In the meantime the website FAQs are bridging the information gap:

https://www.coronawarn.app/en/faq/#eu_dcc_remove "How do I remove a certificate from the Corona-Warn-App?"
https://www.coronawarn.app/de/faq/#eu_dcc_remove "Wie kann ich ein Zertifikat aus der Corona-Warn-App entfernen?"

That in itself is a problem because the UI has been changed multiple times over versions staring from 2.3 to the current 2.13 and it becomes overly complicated to try to cover all these versions in one article.
See also:

[ ] https://github.com/corona-warn-app/cwa-website/issues/2030
[ ] https://github.com/corona-warn-app/cwa-website/issues/2032

Changed terms from "remove" to "delete" to correspond to CWA Android 2.15.1 UI.


Drop-down popup flickers when you type a character not available in data

e.g. by pressing "1" on the demo page in the first input control.
http://bevacqua.github.io/horsey/
Chrome, v40

Resolved in v1.0.1


WIP: docs/proposals/receive: Improved routing and distribution config

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
After having run Thanos receive at significant scale for some time, we have come to realize that the way we route series through hashrings has limitations, that we would like to address before moving it out of experimental state.
The general problem is, that any 1 remote write request being sufficiently large produces N internal requests in a hashrings (N being the hashring size). This ultimately results in a hashring only being able to scale to the number of requests a single instance can process.
This is WIP to discuss possible solutions, as to how to distribute series of the same tenant across multiple hashrings. I have sketched out what a potential replacement configuration could look like, which decouples routing from hashring definitions. Essentially first a series traverses the routing tree, to find which hashring-group it should be ingested into, and then using the partition_keys (identifying a labels within those series) that decide which hashring within the hashring group the series is forwarded to and ultimately ingested into. Partitioning rules could become arbitrarily complex but I think we should start with something simple and just concatenate all label-values of the partition_keys and perform consistent hashring to decide which hashring within the hashring-group to choose. The idea being, we want to keep series close to each other if they are of the same origin. A configuration I could image being common could be partition keys being configured to: cluster, instance.
Please let me know your thoughts.
@thanos-io/thanos-maintainers

I guess there are still some things to be renamed etc, let's see if Frederic is going to address them in the future :)

I don't expect myself to get back to this in the short term if anyone wants to take this over, please feel free to do so!

Ack, i'd be happy to take over, I've been doing some thinking on the subject :))

Does anything block merge this proposal? Is the proposal done?

I'm not totally convinced anymore that this is the right thing as opposed to sub-rings like it's done in shuffle-sharding.

@brancz Makes sense, wonder if it makes sense to set status to rejected if that's the case and merge this? (: It's good to document why we did not do some idea (:


Python requests post api

Hello.
I am trying to call the backend using python requests. Few api endpoints work, but requests.post for search is giving error. Any tips?
import requests
body = { "chatModel": { "provider": "ollama", "model": "qwen2.5:1.5b" }, "embeddingModel": { "provider": "ollama",  "model": "nomic-embed-text:latest" },  "focusMode": "webSearch", "query": "What is Perplexica", "history": [ ["human", "Hi, how are you?"],  ["assistant", "I am doing well, how can I help you today?"] ]}
headers = { "Content-Type": "application/json" }
r = requests.post(
url="http://localhost:3001/api/search",
json=body,
headers=headers
)
error: Response 400
error: Unhandled Rejection at: [object Promise], reason: AxiosError: Request failed with status code 400
While some other api endpoints are working fine, such as
models = requests.get("http://localhost:3001/api/models")
models.json()
or
response = requests.options("http://localhost:3001/api/search")
print(response.ok)

Its not an issue related to Perplexica its rather an issue with the model size, these small models don't follow the prompt correctly and start outputting random things, links etc. So try using a different bigger model, feel free to reopen the issue if you face the issue again.


Naming Issue

I've found another issue when downloading certain apps.  This one is how the download gets named.
Steam is an example of one of these.
Here is my json file.
{   "options": {     "outDir": "/home/username/path/repo",     "type": "apk",     "overwrite": false   },   "apps": [     {       "org": "ookla",       "repo": "speedtest",       "arch": "arm64-v8a"     },     {       "org": "valve-corporation",       "repo": "steam"     }   ] }
If I download this manually, the file is named:
com.valvesoftware.android.steam.community_3.9.3-9305784_minAPI23(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk
However with the script it downloads as:
com.valvesoftware.android.steam.community_3.9.3-9305784_minAPI23(arm64-v8a%2Carmeabi-v7a%2Cx86%2Cx86_64)(nodpi)_apkmirror.com.apk
This seems to cause issues with Fdroid repos in particular in my case.  Leaving it as the original name, Fdroid has no problem with the APK, however with the way it gets renamed via the script it won't allow clients to download it.  It seems as if the "," is getting replaced with "%2C".

Thanks for the issue 💯
Should be fixed with (e927493fafcba668850d234e95fb6ffa70647edc) in release v2.0.8 .


win11sdk need to change download url because it cannot get the filename behind re-direct url

Bug Report
Package Name: [name of package which has bug(s)]
Current Behaviour
url_remote_filename function only analysis the url value:
"url": "https://go.microsoft.com/fwlink/?linkid=2237387",
need to change to
https://download.microsoft.com/download/b/8/5/b85bd06f-491c-4c1c-923e-75ce2fe2378e/windowssdk/winsdksetup.exe
raise bug here https://github.com/ScoopInstaller/Scoop/issues/5555

Expected Behaviour

Additional context/output

Possible Solution

System details
Windows version: [e.g. 7, 8, 10]
OS architecture: [e.g. 32bit, 64bit]
PowerShell version: [output of "$($PSVersionTable.PSVersion)"]
Additional software: [(optional) e.g. ConEmu, Git]
Scoop Configuration

//# Your configuration here

Thanks for this there is a bug in the url format. I will close when I confirm the fix.

Thanks,
https://github.com/ScoopInstaller/Scoop/issues/5555#issuecomment-1600296879


Implement staff screen design

Issue

close #358

Overview (Required)

I implemented staff screen design with reference to contributors design.
While loading icon images, the gray background color is displayed.
To use Context in StaffItem, I added fun appComponent(): Context in AppComponent and StaffComponent.

Is this the right way?

Links

Screenshot

Before
After

Movie

👀

Sorry for the late reply.
I committed as below.

merged from master.
get from context from view, no longer have context in constructor.

Am I getting context properly?
I didn't know how to use lazyWithParam. How should I use it...?


geeksoftware.pdf24creator outdated, will downgrade later versions

in winget geeksoftware.pdf24creator is currently on 10.8.0 which is a very old version
winget upgrade --all will detect this software and replace more recent version like 11.x to 10.8.0
request:

please check why the winget repo bot does not detect new version of this software and update the YAMLs

https://creator.pdf24.org/changelog/de.html
Thank you!

How is this related to MSLab? Am I missing something?


pull request for e2e test at 11/11/2016 11:56:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


First Issue: What IAM roles are needed?

deployment:
annotations: {}
# iam.amazonaws.com/role: prometheus

@derrickburns ,
Thanos needs to write in a bucket, so if you are using AWS you need to give a S3 access to the thanos pods (at least for sidecar, store, compact)
Here it's just an annotation example when using kube2iam as an IAM provider.


Update secure-hybrid-access.md

changed links to the F5 tutorials

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions

intended to create a private repo.


Unsubscribing doesn't affect home screen?

CPod version:
v1.27.0
Platform:
Windows 10
Install type (.deb, Snap, etc.):
.exe installer
Description:
Unsubscribing doesn't seem to remove any items from my home screen. All the episodes of the podcast I unsubbed from remain there. I'm assuming this is not the intended behavior?

I was confused by this same issue running on the 1.2.7 release and was about to open a ticket. Nice to see that it's been resolved. Looking forward to seeing this in a release.


Add top-level wasm package

So we can expose multiple modules from the root.
Signed-off-by: Joe Grund<EMAIL_ADDRESS>

Codecov Report

Merging #987 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #987   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

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 a1ca2eb...2de8f1f. Read the comment docs.


fix(error-detector.js): Altered 'checkEvent' Function (fix #11090)

fix #11090

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Thanks but there was https://github.com/vuejs/vue/pull/11143 already


Question on deleting unused layers and self.downsample

Hi, I couldn't understand how the self.downsample parameter was set (why 8 and 16 and how it affects upsampling_in_channels) and why delete_unused_layers is required in the encoder model. I tried to search the efficientnet-pytorch implementation and couldn't find any reference for this operation. Could you explain briefly why this is required? Thank you!

Hi Benjamin,
The encoder is efficient-net and was trained for image classification. As such the whole model contains convolutions to downsample up to a factor of 32 (I think), as well as a flattening layer and a fully-connected layer to predict the 1,000 class probabilities.
The parameter self.downsample in the encoder allows you to control how much you want to downsample your feature spatial size. Then we use the delete_ununsed_layers to get rid of the efficient-net layers that were not used in the process of feature extraction.
I hope that answers your question :)


(PUP-1364) Detect arch argument in yum installs

Checks for arch in package name
Moves to end of install arguments

Originally there was a plan to add an arch parameter (See https://tickets.puppetlabs.com/browse/PUP-3263), but this doesn't help the use case where two packages have to be installed eg. foo-lib.i686 and foo-lib.x86_64 both have to be installed. Having two packages with the same name would be a conflict.

@petems I turned on HoundCI as an experiment, but it's clearly too verbose. Ignore all those bot comments. Cleanup coming.

@kylog No worries, some of them are pretty valid and I can fix! :smile:

Ignore the double quoted string one though (rageface).

Not sure if this is the best way of doing things, but this ticket's fairly old now (2014, imported from RedMine) and could probably do with fixing sooner rather than later?
I made a module as a workaround (https://github.com/petems/petems-yum_arch) that basically follows this behaviour as a dedicated provider.

Also, @petems I think we want to tackle this at the same time that we tackle https://tickets.puppetlabs.com/browse/PUP-6097, https://tickets.puppetlabs.com/browse/PUP-5802, and https://tickets.puppetlabs.com/browse/PUP-5025. We've tentatively scheduled those two sprints out from now, so we'll circle back to this PR around then. It might be good to have some input on use cases for some of this stuff so we might ping you for ideas if you're up for that.

One concern is whether arch should ever be part of the insync comparison? If so then compare_EVR needs to take arch into account. Based on:

That should really also be included in the package identity somehow, as it's perfectly valid to tell yum to install "packagename-1.2.3.x86_64" and "packagename-1.2.3.i686" simultaneously

I think it does need to be part of the insync check. For example, if you only have i686 installed, and you tell puppet to install both, it should recognize that i686 is already installed but x86_64 is not.

@kylog Cool 👍

CLA signed by all contributors.

@joshcooper Are you talking about the usecase of something like:
    package{ 'firefox.x86_64':
      ensure   => 'latest',
      provider => yum_arch,
    }

    package{ 'firefox.i686':
      ensure   => 'latest',
      provider => yum_arch,
    }

With firefox.x86_64 installed and firefox.i686 not? Because that seems to work in my workaround module...

@petems oh interesting. That works because the arch is part of the package name, not the ensure version. So I think that's the big question, should arch always be part of the name? Or part of the ensure version? Would you ever have/want to do something like:
 package{ 'firefox':
   ensure   => '46.0.x86_64',
   provider => yum,
}

package{ 'firefox':
  ensure   => '46.0.i686',
  provider => yum,
}

@joshcooper I don't think so. Packages with a different arch are considered different in yum and and if you want to specify a specifc arch version when doing a yum install you do yum install packagename.arch so it makes sense to keep the arch as the name variable rather than the version:
[root@centos-testing-2gb~]# yum install firefox.i686
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirror.sov.uk.goscomb.net
 * epel: mirrors.coreix.net
 * extras: centos.serverspace.co.uk
 * updates: mirrors.coreix.net
Resolving Dependencies
--> Running transaction check
---> Package firefox.i686 0:45.1.0-1.el6.centos will be installed
--> Processing Dependency: nss >= 3.21.0 for package: firefox-45.1.0-1.el6.centos.i686
--> Processing Dependency: nspr >= 4.11.0 for package: firefox-45.1.0-1.el6.centos.i686
--> Processing Dependency: system-bookmarks for package: firefox-45.1.0-1.el6.centos.i686
--> Processing Dependency: redhat-indexhtml for package: firefox-45.1.0-1.el6.centos.i686
--> Processing Dependency: mozilla-filesystem for package: firefox-45.1.0-1.el6.centos.i686
--> Processing Dependency: libz.so.1 for package: firefox-45.1.0-1.el6.centos.i686

This means you can specify the version and the arch also:
package{ 'firefox.x86_64':
   ensure   => '38.0.1-1.el6.centos',
   provider => yum_arch,
}

BTW my workaround module for it is here, it's basically the code from this PR split off into it's own namespace: https://github.com/petems/petems-yum_arch

@petems cool, thanks! We're working on fixing the yum behavior around epochs when the version is specified in ensure so we're going to want to look at this in conjunction with our other work to ensure everything is in order. We'll review this soon, hopefully within the next few days if all goes well on our end. See https://github.com/whopper/puppet/commit/d76506dd3c941c847c8b4ac0a42a8aa49acbb262.

@petems @joshcooper r.e arch in ensure string, there is one case where arch must be provided in the version string, and that's when the package has an epoch.
For example, if package foo is version 1:1.2.3, the yum commands that would work to install it would be: yum install foo-1.2.3 and yum install foo-1:1.2.3.x86_64. If the epoch is given in that string, then so too must be the arch:
Yum install formats:
name.arch
name-ver
name-ver-rel
name-ver-rel.arch
name-epoch:ver-rel.arch
epoch:name-ver-rel.arch

We'll need to look into the implications of this for the work we're doing around epochs.

@petems we've absorbed your work into https://github.com/puppetlabs/puppet/pull/4926, which rolls the arch detection into a few other fixes. Thanks for the contribution!

Rad 👍


Add missing "canceller" value to suspend timer

Optimize example command and make it more readable.
Simplify some commands.

P.S. I am super grateful that xidlehook exists, nothing else works as well as it does. If this had more exposure I am sure that it would dominate the idle niche. I really want to say thank you as it's saved me tons of headache.

Thank you!


Add filter button for each match row

Filter all apps from a match row. Useful when you want to quickly filter the apps from a trade you just sent.
Clicking the Filter All button will hide visible apps.
Before button click

After button click

Thank you for your contribution! 🏆


fixes typo in scripts/tls/README.md

I don't know what is up with travis and this pr but it seems to refuse to build it. When I get a bit of time I'll dig into it.


[Feature]: Add translations/localization/internationalization to LobbyView

Feature Summary
With the foundations for localization in place in the app, we can start adding translations to individual pages by pulling their text out of the html and into the local files in src/translations. We can now add this to LobbyView.
Detailed Description
Look at src/views/LoginView for an example of a page that is correctly using $i18n to localize/translate content. The user-visible strings have been removed from the <template> code and placed into a "login" section of the translation files in src/translations.
The page then imports and consumes the useI18n() composable to grab the t() function used to render/translate text by pulling from the appropriate language's json file. This is done using a setup() block of the page like so:
  setup() {
    const { t } = useI18n();
    return { t };
  },

From there, we can grab a given string by name in the appropriate locale using {{ t('login.joinDiscord') }} since each translation json in this case has a login attribute for all the text in the login page, with a joinDiscord child attribute for the text to show in the 'Join our discord community' button.
We should do the same thing to the LobbyView, by extracting all the text in the page into a lobby section of each translation json file (e.g. src/translations/en.json) and then configuring LobbyView with the useI18n() composable and rendering all its text with t() to translate it to the user's selected locale.

I'll grab this one :D


A few more issues with JWT 2.0 release

When I tried to do a fix on JWT master branch for attaching source jar for test dir, I noticed a few more issues:

In the past, a few profiles were defined in the tck pom.xml. Now, they were removed. I think the two profiles should be added back in as at least one of them were mentioned in READM.ADOC.
README.ADOC needs to be updated to mention JWT 2.0 as the current version mentions 1.2.
None of the license files were made to any of the jars in api or tck. I think this related to https://github.com/eclipse/microprofile-parent/issues/50.

@sberyozkin can you take a look at the above issues?

@radcortez Hey Roberto, PR where an update to MP 1.3 parent was made got the local licenses removed I believe, see #232, can you please give me a favor and check point 3 above ?
I can take care of points 1/2, will restore the profiles section

Let me have a look.

Are you verifying the license files by building locally? To change to the EF license files you need to run with -Drelease.revision=Final.
I've tried it and it works for me. Can anyone else confirm?

@radcortez I've tried with and without -Drelease.revision=Final and I see tck/target/licensescontaining al-2.0  al-2.0.html  efsl-1.0.html  eftckl-1.0  eftckl-1.0.html - did you mean something else ?

Here is TCK RC1: https://repo1.maven.org/maven2/org/eclipse/microprofile/jwt/microprofile-jwt-auth-tck/2.0-RC1/

@radcortez I've tried with and without -Drelease.revision=Final and I see tck/target/licensescontaining al-2.0 al-2.0.html efsl-1.0.html eftckl-1.0 eftckl-1.0.html - did you mean something else ?

Can you open the test and api javadoc jar and verify the license?

@radcortez I've tried with and without -Drelease.revision=Final and I see tck/target/licensescontaining al-2.0 al-2.0.html efsl-1.0.html eftckl-1.0 eftckl-1.0.html - did you mean something else ?

Yes, all the htmls are copied, what changes is the link used in the javadoc, so you need to open the javadoc and check if the link is correct.

@radcortez I've tried with and without -Drelease.revision=Final and I see tck/target/licensescontaining al-2.0 al-2.0.html efsl-1.0.html eftckl-1.0 eftckl-1.0.html - did you mean something else ?

Can you open the test and api jar and verify the license? I checked again. The license files are not in the TCK jars. See this MP Fault Tolerance 2.0 TCK jar here. You can see the EF license file is under META-INF folder. It was one of the requirements. @radcortez @sberyozkin

I've checked FT, and the issue is that you are missing the marked file (an empty tck file) in src/main/resources/META-INF.

I did more digging and found out that the missing licenses are for all non-final releases. For non-final releases, the jars should use Apache v2 licenses @radcortez .

I've checked FT, and the issue is that you are missing the marked file (an empty tck file) in src/main/resources/META-INF.

I will add the marker file for all of the rest specs. I think a few of them might have missed that marker.

@radcortez @Emily-Jiang
With -Drelease.revision=Final the index.html in the TCK (and also API) javadoc jar links to the EF license, without  -Drelease.revision=Final - to the AF one. This is correct I believe.
After copying https://github.com/eclipse/microprofile-fault-tolerance/tree/master/tck/src/main/licenses to MP JWT,  the TCK jar itself also contains LICENSE if -Drelease.revision=Final is used - but does not have it if -Drelease.revision=Draft is used - MP FT 4.0-RC2 does not have it either so it is consistent.
But API jar does not have LICENSE with or without -Drelease.revision=Final, even after copying licenses folder to api/src/main

But API jar does not have LICENSE with or without -Drelease.revision=Final, even after copying licenses folder to api/src/main

Yes, there is no action associated with a LICENSE and the API jar. The LICENSE needs to be placed in the resources/META-INF folder to be copied to the resulting jar if a LICENSE has to be included (this is standard behaviour of the jar plugin and not related with the settings of the parent pom).
From my understanding, the API jar just needs to ship with whatever LICENSE is present in the resources, no matter if it is Draft or Final. If you look into the contents of the jar pre-parent pom, it has the same behaviour.


Does anyone else want to maintain this package on conda?

👋 all. I put this package on conda-forge a while ago as part of a (unfinished on my part) attempt to get linkml on conda-forge. I'm the only maintainer though, so was wondering if any of the actual maintainers of this package want to be listed as a maintainer at https://github.com/conda-forge/prefixmaps-feedstock?

from dev call:
we'd be happy to have @cmungall added as a maintainer!
and if you have a recipe for doing these updates in conda-forge we'd appreciate it - we are more of a poetry shop, but happy to support other environment managers/etc.


fix issue affecting Ryan @ Imperium of Rain

This reverts commit a6b3d7f4e75e4e50c6ee70979462c8b138a5061d.

the problem was that his proposal description was gigantic


Add text to variables.

Is your feature request related to a problem? Please describe.
I am working on a Pokémon fan game and I need something like this... "What? "variablehere" is Evolving?!"
Describe the solution you'd like
To add text to variables.

Some time ago, I wanted to set up a menu option that could cycle through a list of names, but it just doesn't seem to be possible in GB Studio without coding strings directly into the menu option itself. Even for a one-off menu, it can become convoluted really quickly.
The ideal solution would be to have the ability to define static databases of strings or integers, so that they can be used dynamically using a special syntax, something along the vein of "$list_name(index number or alias)", eg: "$weapon(20)" or "$sign(save_point)". This would be most useful for cases where specific strings will be reused in multiple places (eg: item names, common messages), or when defining stats and variables for things like enemies and items, allowing them to be easily edited all at once just by editing the relevant entry in the database. (For strings, this would also make localization WAY easier,)

Some time ago, I wanted to set up a menu option that could cycle through a list of names, but it just doesn't seem to be possible in GB Studio without coding strings directly into the menu option itself. Even for a one-off menu, it can become convoluted really quickly.
The ideal solution would be to have the ability to define static databases of strings or integers, so that they can be used dynamically using a special syntax, something along the vein of "$list_name(index number or alias)", eg: "$weapon(20)" or "$sign(save_point)". This would be most useful for cases where specific strings will be reused in multiple places (eg: item names, common messages), or when defining stats and variables for things like enemies and items, allowing them to be easily edited all at once just by editing the relevant entry in the database. (For strings, this would also make localization WAY easier,)

Good ideas


Nest 9: Could not resolve dependency: peer<EMAIL_ADDRESS>|| ^8.0.0"

--force must be added to npm i when installing this library in a project with @nestjs/common@^9
$ npm i @lukadriel/nestjs-rabbitmq-transporter
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nestjs/common
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^8.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@lukadriel/nestjs-rabbitmq-transporter
npm ERR!   @lukadriel/nestjs-rabbitmq-transporter@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Hey, It's because I haven't updated the dependencies to nestjs 9 yet, I will try to update it this weekend

@andrucz can you try it now and confirm everything works ?


Fix path resolution errors

This is the real problem with #22 #24 that previous changes didn't fix.
You can end up with //cesium as your link, which is a valid URI and not the same thing the user specified in config.base.
Tested working:
base='', base='./', base='/', base='/foo/'
Using this workaround
I built a version of this plugin to use while we wait for this to merge and release.  Add this to package json.
"vite-plugin-cesium": "git+ssh://git@github.com:subdavis/vite-plugin-cesium.git",

demo/vite.config.js
import { defineConfig } from 'vite';
import cesium from 'vite-plugin-cesium';
export default defineConfig({
  base:'',
  plugins: [cesium()]
});

build result demo/dist/index.html
<!DOCTYPE html>

    <link rel="stylesheet" href="/cesium/Widgets/widgets.css">

    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>cesium-vite</title>

    <link rel="stylesheet" href="assets/index.007faab3.css">

My suggestion is to modify this judgment on top of this
https://github.com/nshen/vite-plugin-cesium/blob/8c3e99826c6d9a06b5269e775082b4a56ed2a2b4/src/index.ts#L36-L39
Modify to
 if (typeof c.base === 'string') {
       base = c.base;
 }

Thank you, I think you are right.


Very low light level readings

Hi,
I need to get small variations in very low light levels to monitor human access in caves. I have configured the TSL2591 with maximum gain and integration time, a persistence of 40 and thresholds between 0 and 5, but sometimes I get erratic readings. Any advice to avoid them and maintain maximum sensitivity?
Thanks !

The first thing that comes to mind is the dark count - the datasheet specifies it as 0 to 20. Are your measurements small enough that this would have an impact?
About the "persistence of 40 and the thresholds between 0 and 5" - I'm not familiar with the term persistence in the context of this sensor, and what is the threshold on? Are you looking at thresholded data, as opposed to the raw values?

I have consulted the datasheet and, indeed, the dark count option appears, but with an integration time of 100 ms and maximum gain, in this case the count is between 0 and 20. But it seems that the maximum sensitivity is obtained with gain maximum and integration time of 600 ms, so I do not quite understand this option. I'll do some tests to see the results
Regarding the use of persistence and threshold data, these are used so that the sensor can sleep and activate an interruption only in the event that the reading is within the upper and lower limits, and after the number of readings exceeds the persistence figure
In my case, I have a setting to activate an interrupt (and wake the microcontroller) after 40 above 0 and below 5. I understand that the persistence data is used to avoid false readings due to noise

I should clarify - dark count is not an option, it is noise that has various causes - for example, part of the dark count is thermal noise. The datasheet specifies that for integration time of 100 ms and maximum gain, the dark count is between 0 and 20. This means the sensor can always report values between 0 and 20, even if there is no light.
For an integration time of 600 ms, I expect the dark count to fall between 0 and 120 (6 times larger). The values you are looking for are very small, and the dark noise looks likely to be causing your problems.
It might be possible to characterize the noise by covering the sensor completely and taking measurements. With a better understanding of it, you may be able to better determine real and fake events. For example - the dark counts might have random time and magnitude, and the real events might have consistent magnitude for a period of time.
Another possibility is to use two sensors and see if the data is correlated. I would expect a real light source to cause similar measurements in multiple sensors, while the dark counts should not correlate well.

Thanks for the clarification about the dark count, I had indeed misinterpreted your previous comment
I will take your advice into account, I need to do more tests to decide the best solution to avoid or minimize false readings
Best regards,

Best of luck. Closing because this issue seems to be inherent to the sensor, as opposed to this code.


Update docker file

I updated the Dockerfile which apparently hasn't been updated in 4 years. The base image provides a functioning working environment, but the goreleaser is having issues.
I needed this so I could use it with JetBrains spaces.

If you really want, I'll downgrade it - but since no one was using it, and the default in alpine is like 1.16, I just went for broke

Give me a moment and I can downgrade it

If you really want, I'll downgrade it - but since no one was using it, and the default in alpine is like 1.16, I just went for broke

It's more of using this Dockerfile and people adding 1.20/1.21 specific code that we can't compile later on.

It's now downgraded to 1.19.2

Yeah, I accidentally deleted the repo when i was getting funny behavior and reforked it. I'll create a new PR from the same code


test: new scenario added for restricted access information field max …

…limit
Ticket Number
UCD-887
Description of change
New scenario added for field validation
Checklist

[ ] Requires infrastructure changes
[ ] If adding or remove environment variables (e.g. in docker-compose.yaml) then I have updated the appropriate Helm chart
[ ] I have updated the documentation accordingly
[ ] My commit history in this PR is linear
[ ] New features have tests
[ ] Breaking change (team conversation required)

Important
Please do not merge from master (please only rebase). This keeps the history linear and easier to debug.

I added the glue code and removed the @wip tag to be sure that the build is green

I added the glue code and removed the @wip tag to be sure that the build is green


Out of memory error when running ch in WSL

I was trying to build and run ChakraCore on Windows Subsystem for Linux. The code is from the master branch (2349c5f), built with ./build.sh --debug. It's built successfully, but when I run ./ch <any js file>, it immediately aborts with an error "Out of Memory". The call stack shows the problem is in function X64WriteBarrierCardTableManager::Initialize() in RecyclerWriteBarrierManager.cpp. At line 279, VirtualAlloc returns nullptr, causing the process to print "Out of Memory" and abort.
My OS is Windows 10 Pro x64 Build 15063. The Linux distribution is Ubuntu 16.04.3 LTS.

This is https://github.com/Microsoft/BashOnWindows/issues/597

Thank you @jianchun! I will try the latest insider preview.


Trigger build

Description of changes

Checklist for things done

[ ] Summary of the proposed changes in the PR description
[ ] More detailed description in the commit message(s)
[ ] Commits are squashed into relevant entities - avoid a lot of minimal dev time commits in the PR
[ ] Contribution guidelines followed
[ ] Ghaf documentation updated with the commit - https://tiiuae.github.io/ghaf/
[ ] PR linked to architecture documentation and requirement(s) (ticket id)
[ ] Test procedure described (or includes tests). Select one or more:

[ ] Tested on Lenovo X1 x86_64
[ ] Tested on Jetson Orin NX or AGX aarch64
[ ] Tested on Polarfire riscv64

[ ] Author has run nix flake check --accept-flake-config and it passes
[ ] All automatic Github Action checks pass - see actions
[ ] Author has added reviewers and removed PR draft status

Testing

/rebase

/rebase


Update top command for cpu.

kubectl top pod POD_NAME --sort-by=cpu  > Gives pod in Ascending order.

LGTM
Please check your cla to get this merged. Thanks

/close


Updating the AIHWKIT  'Read The Doc' Paper references

Related issues

Description
To update the AIHWKIT 'Read the Docs'
Details
Updated the Paper References section, and also the steps to create a Basic Inferencing experiment using AIHWKIT

Thanks @soumyajeet8 please fix the minor typos

Hi @soumyajeet8 did you get a chance to make the requested changed. They are minor changes.

HI @kaoutar55 , I have made the minor typo changes as requested since I was facing issue connecting to WSL so I had to resolve that, before I could access the code-base and make changes. The changes are captured in PR #568


Resolve Inconsistencies in React States While Customer Login

Currently, when customer login from the checkout page itself, there occurs some react state inconsistencies. The checkout form stays in guest checkout mode.

I have tried a few things and currently solved this by doing the following
in react-container.phtml
$viewModel = $block->getViewModel();
$isLoggedIn = $viewModel->customerLoggedIn();
$customerIsLoggedIn = "false";
if ($isLoggedIn) {
$customerIsLoggedIn = "true";
}
?>

and in reactapp/src/context/App/initialState.js
isLoggedIn: document.getElementById('react-checkout').getAttribute('isloggedin'),
This makes sure that this is set correctly when the app launches.

Hi @jladmore, thanks for your inputs. Really appreciate it.
This issue is all about the inconsistencies facing in the checkout page when the user tries to log in from the checkout page itself. Not before reaching the checkout page.
On the checkout page, it will check for the customer token in the local storage mage-cache-storage.customer.signin_token. If it exists, then it will treat the checkout as logged-in checkout. Else, it will be a guest checkout.
So if you set the customer token at mage-cache-storage.customer.signin_token, when the user login from the site, then hyva checkout will work as expected.
Let me know whether this is working for you or not.

There are two issues I see in using the signin_token

There could be case where its defined in the mage-cache-storage, but its not valid. I have seen this in my testing, but this could be due to me having other things going on.
You still need to grab the token and then set the initialState of isLoggedIn to be true. When I was testing if you didn't do this in initialState.js then there could be 1-2 renders where isLoggedIn is false, due to the time it takes to set the variable

This is why I decided to Nail up the initialState of isLoggedIn to be true based on the server render.... you still use the token anyway for all GraphQL queries from this point on.

@jladmore Yes,  your observations are correct. I am adding my 2 cents here on this:
When a customer logged in (not from the checkout page) and has a token is stored at mage-cache-storage.customer.signin_token, then there is a valid session and valid token for the customer. I assume the session is by default one hour lifetime. After one hour, it will get expired. This means both the token and the session will be invalidated after one hour.
If the above hypothesis is true, then you find the token is invalid when you come to the checkout page, then the hyva-checkout will be rendered but, it will be empty. This is because the cartId stored at ``mage-cache-storage.cart.cartId` is now invalid since it is the cart id of the user who logged-in before. Since the token got expired, the cartId is not valid anymore.
So at this time, the safe bet is customer login from the checkout page or login from the site and comes to the checkout page. In both cases, it will update the customer token and with a valid customer token the cartId against the customer is again valid and it will provide the cart data through the graphql query.

This issue with the state inconsistencies occurring while login from the checkout page is resolved with pull request #30
Hence closing the issue


Removed deprecated packaged (gulp-util) and introduced alternative pa…

…ckages (vinyl & plugin-error). Closes #17
Followed the following guide to move away from gulp-util: Guide

Thanks for this 👍


Sample Application for Timestream is Useless

The purpose of sample and reference applications is to clearly expose the working mechanisms of your library, in this case the Timestream Client in Boto3.
What you have built is a demo. Read data from a file and write it to Timestream. All of the useful logic is in 'crud_and_simple_ingestion_example'. Although this is a more professional way of building the code it doesn't fulfill the purpose of the stated purpose of the code.

Thank you for your feedback. If you are looking for specific code samples, can you provide us more details on the scenarios?

I have written a simple TypeScript utility here to deal with parsing TimeStream queries into usable JS objects: https://gist.github.com/cam8001/44babba44cd912093892589640b96dc5


fix(katana-provider): take correct amount of tx

Fixes #1265
Will follow up this PR with proper testing

Works great, domo!


Build static lib of glog in CMake

Fix #615.
After this PR (liblzma.so is brought in by libunwind.so):
$ ldd kvrocks
        linux-vdso.so.1 (0x00007fff165d7000)
        libunwind.so.8 => /usr/lib/libunwind.so.8 (0x00007fa86a7ae000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007fa86a6c6000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007fa86a4bc000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fa86b8d8000)
        liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007fa86a493000)
        libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fa86a48e000)

Merging...
FWIW a discussion (#615) cannot be resolved. You may create an issue from the discussion the next time.

Merging...
FWIW a discussion (#615) cannot be resolved. You may create an issue from the discussion the next time.

My mistake, will open an issue next time :)


test: add auth to api tests

Description
Added authentication retrieving to all endpoints and created new variables to accommodate credentials.
Fixes # (199)
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Tested locally pointing to the environment of PR #42
Checklist

[x] I have read the CONTRIBUTING doc
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[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
[x] Any dependent changes have already been accepted and merged

It would be nice to properly explain all the required parameters used and passed to Newman during tests.
As a suggestion, I would advise on the creation of a docs folder with a wiki-style or even by using the wiki functionality on GitHub to document some of the more technical things involved.

Thanks for the suggestion @paulushcgcj , I will add a task to create the wiki.


Serialized size difference between b".." and "..".as_bytes()

Hi Guys,
why is there a size difference when I do the following?
let size = bincode::serialized_size(b"hellobello").unwrap();
// here the size is 10

let size = bincode::serialized_size("hellobello".as_bytes()).unwrap();
// here the size is 18

So with the following bytes - as valid ASCII characters - should take 1 byte per character, that means 10 char * 1 byte => 10 bytes.
But when I use a &[u8] or a "..".as_bytes(), the size is almost double. Why?
Thank you in advance.

Solved here: https://users.rust-lang.org/t/bincode-serialized-size-difference-between-b-and-as-bytes/48541/2

If you use the bincode varint configuration you can end up reducing the side of the as_bytes() case to 11 bytes in size.


1.5.1 build-optimizer "TypeError: candidate.value.definition is not a function"

Versions
Angular CLI: 1.5.1
Node: 6.11.4
OS: win32 x64
Angular: 5.0.0
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker

@angular/cdk: 5.0.0-rc0
@angular/cli: 1.5.1
@angular-devkit/build-optimizer: 0.0.33
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.36
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.1
@schematics/angular: 0.1.5
typescript: 2.4.2
webpack: 3.8.1

Repro steps

run ng build --prod
don't know what this could be related to, since my project is quite large

Observed behavior
ERROR in main.c625bf1271eaaf6ccac7.bundle.js from UglifyJs
TypeError: candidate.value.definition is not a function
    at collapse (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:8275:61)
    at tighten_body (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:8110:17)
    at eval (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:12402:9)
    at AST_Node.eval [as optimize] (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:7481:23)
    at Object.before (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:7464:24)
    at AST_Node.eval [as transform] (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4559:35)
    at eval (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4688:43)
    at Object.before (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:7459:9)
    at AST_Node.eval [as transform] (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4559:35)
    at eval (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4679:43)
    at Object.before (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:7459:9)
    at AST_Node.eval [as transform] (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4559:35)
    at eval (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4590:31)
    at Object.before (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:7459:9)
    at AST_Node.eval [as transform] (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4559:35)
    at eval (eval at <anonymous> (C:\github\web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:1:0), <anonymous>:4578:25)

It worked with 1.5.0 with --build-optimizer and works with 1.5.1 when specifying --build-optimizer=false.

Having the same issue here using angular-cli 1.5.3
TypeError: candidate.value.definition is not a function
    at collapse (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:8275:61)
    at tighten_body (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:8110:17)
    at eval (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:9710:9)
    at AST_BlockStatement.eval [as optimize] (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:7481:23)
    at Compressor.before (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:7464:24)
    at AST_BlockStatement.eval [as transform] (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:4559:35)
    at eval (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:4606:31)
    at Compressor.before (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:7459:9)
    at AST_For.eval [as transform] (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:4559:35)
    at eval (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:4578:25)
    at doit (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:134:23)
    at MAP (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:160:52)
    at do_list (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:4577:16)
    at eval (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:4674:25)
    at Compressor.before (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:7459:9)
    at AST_Function.eval [as transform] (eval at <anonymous> (C:\dev\Web\node_modules\uglifyjs-webpack-plugin\node_modules\uglify-es\tools\node.js:21:1), <anonymous>:4559:35)```

This is an uglify bug: https://github.com/mishoo/UglifyJS2/issues/2497

Thanks @kzc for letting us know! Do you know how we might implement a workaround for angular cli? Doesn't look like it's straightforward (or even possible?) to pass uglify js options into the build process

As a temporary workaround for this bug you could add collapse_vars: false to the uglify plugin's compress options in your webpack config.
In the case of angular-cli it would use a different syntax due to the way its webpack config file is structured. Try adding the following line after this:
    uglifyCompressOptions.collapse_vars = false;

I'm not an Angular user. @filipesilva Could you please confirm this is the right place for this setting?

Hey @kzc, than you for letting us know! We don't expose Uglify options so this is hard to work around... The file you found is indeed the right place.
For users that want a more CI friendly workaround, you can downgrade from 1.5.x to 1.4.x, since the latter uses uglify-js instead of uglify-es (I assume this bug is only on uglify-es).

The bug is present in both branches - latest uglify-es@3 and uglify-js@3.
You might try using an older version of uglify-es in your npm or yarn lock file.

@filipesilva it would be handy if the uglify options were exposed; we are already tweaking the production.js config for compatibility with another popular web mapping library.

I got this issue too on CLI 1.5.0.
How to override the uglifyCompressOptions.collapse_vars from cli project without webpack.config.js?

I am downgrading to 1.4.x. :disappointed:

<EMAIL_ADDRESS>was released with a fix for this issue. Please try it out.

@kzc awesome, thank you!
For users affected by this problem, here is how you can force your dependencies to use the<EMAIL_ADDRESS>You can't just add it as a dependency with a new version since the uglify-es is not a direct dependency.
To see what version you have, run npm list uglify-es:
$ npm list uglify-es
<EMAIL_ADDRESS>D:\sandbox\master-project
`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>
To force an indirect dependency to use a new version, you'll have to update your cache and remove the any package-locks you have. This series of commands should do it:
// Force update your cache
npm install<EMAIL_ADDRESS>npm uninstall<EMAIL_ADDRESS>// Remove node modules and package locks
rm -rf node_modules package-lock.json yarn.lock
// Reinstall dependencies
npm install

After all of this, you should be able to see the new version:
$ npm list uglify-es
<EMAIL_ADDRESS>D:\sandbox\master-project
`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>
I realize this process is cumbersome. NPM does not offer a good way to force update indirect dependencies.
I've submitted a PR to update our direct dependency (uglifyjs-webpack-plugin): https://github.com/webpack-contrib/uglifyjs-webpack-plugin/pull/176.
Then Angular CLI can update to that version and everyone gets the new version of uglify-es by default.


fix bug in history navigation for tab

fix issue #2997

Hello! Thanks again for the PR! As it has been a little while since there was any activity on this pr, and there are failing tests i will be closing this pr. Please feel free to open more PR's with us in the future!


Add mitochondria training script and info

[ ] Add the training script to https://github.com/computational-cell-analytics/synapse-net/tree/main/scripts/cooper/training
[ ] Collect the info on how many tomograms, annotations and the resolution. I can do this, but I need the location of the tomograms on the cluster.

The training script is here:

https://github.com/computational-cell-analytics/synapse-net/blob/main/scripts/cooper/training/train_mitochondria.py

and the location of the tomograms i sent you in PM


How-To Compile this Project ?

Is there a How-To get this compiled and running ?
Thanks!

Yes, this was a successful build.
Can you upload it to your ESP?
BTW check the selected environment, you built it for ESP8266

Visual Studio Code is running in a virtual machine, recompiled for ESP32.
Using ESP-Flasher-Windows-x64.exe leads to this output:
Using 'COM4' as serial port.
Connecting....
Detecting chip type... ESP32
Connecting....

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-D0WDQ6 (revision 1)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: NO
 - Has Factory-Calibrated ADC: YES
 - MAC Address: 24:62:AB:FC:B5:C0
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
 - Flash Size: 4MB
 - Flash Mode: dio
 - Flash Frequency: 40MHz
Erasing flash (this may take a while)...
Chip erase completed successfully in 7.3s
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x000d2fff...
Compressed 17104 bytes to 11191...
Writing at 0x00001000... (100 %)
Wrote 17104 bytes (11191 compressed) at 0x00001000 in 0.4 seconds (effective 316.5 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 129...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.0 seconds (effective 523.7 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 948.9 kbit/s)...
Hash of data verified.
Compressed 794704 bytes to 458939...
Writing at 0x00010000... (3 %)
...
Writing at 0x000d1eb0... (100 %)
Wrote 794704 bytes (458939 compressed) at 0x00010000 in 11.1 seconds (effective 574.0 kbit/s)...
Hash of data verified.

Leaving...
Hard Resetting...
Hard resetting via RTS pin...
Done! Flashing is complete!

Showing logs:
[21:43:06]ets Jun  8 2016 00:22:57
[21:43:06]
[21:43:06]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[21:43:06]configsip: 0, SPIWP:0xee
[21:43:06]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[21:43:06]mode:DIO, clock div:2
[21:43:06]load:0x3fff0018,len:4
[21:43:06]load:0x3fff001c,len:1044
[21:43:06]load:0x40078000,len:10124
[21:43:06]load:0x40080400,len:5828
[21:43:06]entry 0x400806a8

Is the last part the serial output of the ESP?
If you get this Message after line "Showing logs" continuously, it seems like you are stuck in a boot loop, but i cannot tell from this log.
Are you receiving messages from the ESP?
You can check this by connecting to the serial port on which your ESP is and restart it and you should see messages appear.

Something is missing to get this firmware running.
Flashing Tasmota to this ESP using ESP-Flasher-Windows-x64.exe leads to a running system.
Have no display connected and tested with disconnected / connected M-Bus interface.
Any idea ?

Sorry, i do not really understand what's your problem.
The warnings seen in here can be ignored.
The ESP should print something to the serial port (when booting), with or without the connected hardware. Please check that first.

Fix #3 solved this issue, thanks!


Tfl status sample update

Q
A

Bug fix?
yes

New feature?
yes

New sample?
no

Related issues?
NA

What's in this Pull Request?
Updated the sample to SPFx 1.13.0 and fixed some issues related to the Viva connections mobile app.

Thanks for the update. We'll review and publish shortly.

Thank you Derek. For some reason the svg icons are not loading in the quick view in mobile app. So, I'll take a look at that and add more commits and let you know once done.
I thought I had fixed it by using require. But I see that it worked only when I was developing. After publishing it has stopped working.

@anoopt If you can get an update to me tomorrow I can review and approve it on Monday. If not, no rush. David and I are reviewing the PRs then.

@anoopt Thank you for the update. I have merged this into the main branch.


pdfjet.com

Is this https://pdfjet.com, but MIT licensed instead of $295/$595?

The commercial version at https://PDFjet.com has a few extra features.
If the open source version works for you, just use that one.
Sent from Proton Mail for iOS
On Thu, Nov 2, 2023 at 05:25, jspraul @.***(mailto:On Thu, Nov 2, 2023 at 05:25, jspraul < wrote:

Is this https://pdfjet.com, but for $295/$595 instead of MIT licensed?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Feature Request: Using/Setting more unique variables in Ansible Operators

Feature Request
Is your feature request related to a problem? Please describe.
The Ansible Operator SDK stores things like name in meta.name. Using something as generic and nondescript as that is considered bad Ansible form and style given the engine’s flat namespace and the potential for collision.
Describe the solution you'd like
The idea here would be to transition what’s in stored meta to something like ansible_operator or something else sufficiently unique and descriptive. It's worth noting, Ansible itself uses ansible_* for any variables set by the system so it might be worth consideration here.
I don't know what is the best way to do this without causing some sort of breaks in existing/working operators using Ansible. I think it's important to consider and is better fixed now, pre "1.0" rather than waiting for namespace collisions to happen later when many Operators using Ansible have been deployed are run into collisions.

Just wondering for this—is meta.name a convention across different operator languages (e.g. Go, Java, etc.)? If so, then maybe that's a good reason to stick with it.
Otherwise, one argument against it may be that in an operator context, these variables aren't necessarily ansible-related, but rather operator-related.
But I do see what you're saying, all the 'magic' variables/facts that are available to describe a given environment (e.g. ansible_ipv4, ansible_distribution, etc.) are ansible_-prefixed.

Hi @geerlingguy,
I am not sure if I got this one. Are you looking for all ENV VARs which are used/available to ansible starts with the prefix ansible? Could you please point out some examples over how you are checking it in the project X what you expected to see?
@fabianvf @estroz I am not sure if it is a blocker for 1.0.0. WDYT?

@camilamacedo86 - I know @fabianvf, @tima and I were talking about this, and I think the idea was we'd put these vars behind an ansible_operator_ prefix.
In Ansible itself, there are a variety of environment-based 'facts' Ansible gathers prior to running playbooks (unless you disable fact gathering).
I imagine some things that would be really nice to have available would be things like:

ansible_operator_version (like 1.18.0)
ansible_operator_namespace (the namespace where the operator is currently running)
ansible_operator_cluster_version (k8s or ocp cluster version, e.g. 1.18.1 or 4.3...)
ansible_operator_last_reconciliation (or other timing-related facts?)
ansible_operator_status (with the status/event information that would also be reported when running kubectl describe [operator]).

This is just kind of thinking out loud, though. I think the main goal was to get a structure for facts in place, then over time we could add things to it if desired.

@camilamacedo86 yeah, we're going to get the change from meta to ansible_operator_meta in before 1.0 at least, I was planning to do so immediately after the scaffold changes merge

Thank you for the clarifications :-)

/remove-lifecycle stale


Getting invalid: status.conditions: Forbidden: updates may not add a condition of type "Approved"

When attempting to create a CertificateSigningRequests then approving that request via this api i keep getting
CertificateSigningRequest.certificates.k8s.io "foobar.com" is invalid: status.conditions: Forbidden: updates may not add a condition of type "Approved"

wondering if this is possible or i'm just missing something.

found the issue by just following what kubectl does and using  UpdateApproval

found the issue by just following what kubectl does and using  UpdateApproval

@duhruh can you elaborate 'what kubectl does and using UpdateApproval', having same issue, and not able to figure out whats causing it


Sort and map the emails for better reporting

@steve-norman-rft As we discussed this PR adds the sorting and mapping of users to solve some of the issues commented. It also fixes some new lint rules that were causing some errors
Feel free to test the solution out using the hash of the commit cf119da1671a09ce9720fdb798e7b9ce52154770 so we can verify all is working as expected. If so, I can make another release with these changes

Failed when ran with the latest sha (which won't have the dist updated but I don't think it is that causing it)
2021-08-25T16:21:38.1134879Z ##[group]Run ActionsDesk/enterprise-members-report-action@8022e44a8252d8466869f2bf9f927594e04f248d
2021-08-25T16:21:38.1135912Z with:
2021-08-25T16:21:38.1138207Z   token: ***
2021-08-25T16:21:38.1139272Z   enterprise: ***
2021-08-25T16:21:38.1139757Z   format: html
2021-08-25T16:21:38.1140147Z ##[endgroup]
2021-08-25T16:21:48.7006460Z ##[error]Cannot read property 'trim' of undefined
Please report this to https://github.com/markedjs/marked.
2021-08-25T16:21:48.7270438Z Cleaning up orphan processes

@stoe you're right. I will review also the issue that we are experiencing and see if it's caused by any change here or something else as it looks fishy


pulumi-bin: 3.95.0 -> 3.99.0

Description of changes

https://github.com/pulumi/pulumi/compare/v3.95.0...v3.99.0
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I'm closing this one, cause I'm finally created a new one


Faucet doesn't seem to be working even with my ENS name

Here is my address: 0x320D24BEA15B5A72839d608Dfc95ed85c9d8afc0
I have two ENS domains and neither seemed to work. I do have Kiln set up for metamask. Thanks for any help you can provide.

This is the wrong repository for that kind of issue.

The link on this guide: https://github.com/flashbots/mev-boost/wiki/Testing
directs me here to ask for testnet ETH. If you look at the guide under "Register as a vaalidator" there is a link within the statement:
Get kiln ether from the faucet. When the funds are low, this requires an ENS domain. If you don't have one, ask us for some test ether opening an issue.

Hello @klovertexarkana.
I've sent you 32 kiln test ether. Please let us know how your testing goes :)

Thank you so much!!
Would you mind sending me the transaction hash? I’m so confused bc there isn’t showing any in my metamask account at this time.
Perhaps the faucet is working. I’m on the Kiln network and I copy-pasted my address. I’m not sure why it hasn’t arrived. I hold other assets in mainnet, polygon, goerli, and rinkeby.
Sent from my iPhone

On Jul 11, 2022, at 3:23 PM, Leo Arias @.***> wrote:

Hello @klovertexarkana.
I've sent you 32 kiln test ether. Please let us know how your testing goes :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.


Auto-failover mechnism for vineyard cluster on kubernetes

Describe your problem
Although we have the CRD Backup to back up all objects in vineyard cluster and CRD Recover to recover them, users need to manage it manually. However, we can define some Failover Strategy in Vineyardd CRD as follows.
EnableFailover: true
Backup:
    # Backup the vineyard cluster every 5 min
    period: 5min

The Vineyardd Controller will detect the status of vineyard cluster(Vineyardd) and trigger the failover operation by the two situation:

Node Failure.
Pod Restart.

In addition, when the Recover job finished, the old object id is deleted and a new object will be created. Uers can check the mapping relationship between old and new objects from the statue of Recover CR. In this case, it requires users to look up the mapping relationship every time to obtain the new object id. It will be much more convenient if usesr can obtain the data by reading the old object id.
In summary, the main tasks are as follows:

[ ] Support regular failover in vineyardd controller.
[ ] Support reading old and deleted object during Failover.

Closing as the cronjob is left for the workflow engine on top of vineyard cluster.


Ignore, rather than throwing on, Coding style component (COC) markers in JPEG 2000 images (issue 12752)

Similar to other markers that we currently skip, by ignoring the Coding style component (COC) marker we'll at least prevent outright errors (although some JPEG 2000 images may look slightly wrong).
Fixes #12752

/botio-linux preview

/botio test

Thanks!
/botio makeref


Auth issues

Are you running into similar issues as the ones I'm trying to document in https://github.com/driven-app/porsche-connect/issues/160 ? Wondering if you've having any luck with the root cause analysis!

Yes, issue is/was in this application. I added a 5 times retry for now which fixes most issues. Lets discus on Discord about a proper solution for both applications


Update URL for docker image language mapping

Is there a way to discover this URL (so it won't break again)?


Refactors classes to sub-namespaces

Classes and interfaces have been moved to sub-namespaces for improved organization, instead of having everything in the main Contentful\Managament namespace, as the number of classes keeps growing and things are becoming a bit unwieldy.
Entities managed by Contentful (Asset, ContentType, Entry, EntrySnapshot, Locale, PublishedContentType, Space, Upload, User, Webhook, WebhookCall, WebhookCallDetails, WebhookHealth) are now in the namespace Contentful\Management\Entity.
Behavioral interfaces (Archivable, Creatable, Deletable, Publishable, Updatable) are now in the namespace Contentful\Management\Behavior.
Changes have been made using PHPStorm's "move" functionality, and tests confirm that nothing's broken, so we're 99.9999% sure it's safe.
~As the 3 other PRs currently open (https://github.com/contentful/contentful-management.php/pull/27, https://github.com/contentful/contentful-management.php/pull/26, https://github.com/contentful/contentful-management.php/pull/7)  would be impacted by this, I say we could either merge this and rebase those (which would probably be the cleanest solution) or wait for those to be merged and then rebase this one against master.~
Update: As #27 and #7 have been merged, I've rebased against master and updated this PR.

Update: As #27 and #7 have been merged, I've rebased against master and updated PR,

Just a quick questions: Resource vs Entity why would you choose either?

@mariobodemann they both could be a valid alternative, especially in this context, but the term Entity is commonly used in one of the most used frameworks (Symfony), so I chose a term that already has solid roots in the PHP ecosystem.
Resource is also word that right now is safe, but I think it's one of those "at risk", which could become a reserved keyword somewhere along the way, whereas Entity because of its current status, should be safer...

Updated the PR using Resource instead of Entity.


Problem_Statement_20_Solution

Created PR for Problem_Statement_20 #9
Added By Sravya Srusti

@SravyaSrusti , your code is correct and giving a proper output, but you haven't created the Pull request properly i.e. please mention the issue(#9) in the comment of the pull request.

@SravyaSrusti , your code is correct and giving a proper output, but you haven't created the Pull request properly i.e. please mention the issue(#9) in the comment of the pull request.

Please review the PR, i have edited the comment. @Krush2311

Please approve this PR ASAP if you think everything is alright.
I have also asked for another problem statement (Problem_Statement_54 #36) and I've a working solution of it, on which I've spent quite a bit of time yesterday.
Thank you


Enable global-require, no-buffer-constructor, and no-new-require

For #5456. Bump the version number in preparation to deploy version 2.0.0 of the eslint-config-cesium package.
The new rules pertaining to Node are:

global-require
no-buffer-constructor
no-new-require

Looks good, I'll merge as soon as this goes green.  Thanks @omh1280!


Extract specific GRANT permission from Export-DbaUser

Summary of new feature
Often it happens that grants are given directly in prod to users without starting from the test databases so when we bring new developments these are overwritten. Export-DbaUser it already contains what it would take to restore them but it is together with many other commands that for my daily operations are "too many" and I have to go to extrapolate from the output file the only rows that interest me.

Why don't you just sync permissions from prod to lower environments?

Hi Shawn, often bi manager assigns grants directly in production without aligning the developers and when they bring the changes into production these permissions are lost. People would like to run this script on their own to directly save grants without asking who and when it was modified.

Great idea! We could potentially address this by adding [string[]]Type and then Grant, Revoke, Whatever?. Then set the default to the current output? What you think @ClaudioESSilva?

Being able to deal with filtering based on what was granted I would see being problematic to maintain because those change in both what you assign and syntax by version.
I think limit it to the type of permission will be best. (Just grant and not grant select)

Thinking about this more, should an export command have this level of filtering? We do not allow this level in any of the export commands we have to date.
Would it not be more proper to have you get the permissions you want that a user has assigned and pipe those to an export command?

I think limit it to the type of permission will be best. (Just grant and not grant select)

I guess it is easier to make, however, it would force the user to put his hand to the output to remove the unnecessary grants.

I guess it is easier to make, however, it would force the user to put his hand to the output to remove the unnecessary grants.

Use of Get-DbaPermission solves that problem and I think what you are wanting in this issue as well...based on what I see the code doing.
Having the ownership be on our-side adds overhead of maintaining code that has to account for every feature and permission option in SQL Server for every version we support, including the builds in Azure PaaS. Consider the Get command itself has specific T-SQL to filter out what permissions it is pulling for the database level and this alone may already be out-dated with what is available in SQL Server 2019, and even Azure SQL DB/MI:
https://github.com/sqlcollaborative/dbatools/blob/fb31a745b0ea3554c0ca0a3e77955227c8791f5e/functions/Get-DbaPermission.ps1#L193-L203

Also in this command, however, something is missing that keep out ONLY grants (for example)
Get-DbaPermission -SqlInstance SQLSRV -Database MyDB -Grant(will read from the GrantStatement source)
(extract from Get-DbaPermission)
...
GrantStatement  : GRANT SELECT ON VIEW1  TO [CONTOSO\BI_REPORT]]

That would simply be fixing the query used I'm sure, or how the filter is being applied to the dataset.

@L3onard80
Get-DbaPermission ... | Select grantstatement
or
Get-DbaPermission ... | Where PermState -eq 'GRANT'
won't do?

@L3onard80
Get-DbaPermission ... | Select grantstatement
I LIKE IT! Thanks!
Get-DbaPermission ... | Where PermState -eq 'GRANT'
This DOESN'T work as expected and does an infinite swipe of commands.

@L3onard80
I'm sorry, that was meant as pseudo code.
Be careful: Get-DbaPermission will always create a grantstatement and a revokestatement, even if the actual permstate is DENY or anything else.
You probably want to execute Get-DbaPermission -SqlInstance ... | Where-Object {$_.permstate -eq 'GRANT'} | Select-Object grantstatement
So what this issue concerns, instead of adding this functionality to Export-DbaUser , we probably rather need a 'CurrentStatement' property on Get-DbaPermission ? @potatoqualitee @wsmelton

Perfect works exactly like the first command (Get-DbaPermission ... | Select grantstatement).
Thanks again, Klaas.

I'm not sure if this is still a request for a new feature.
@L3onard80 : Do you still want to have the new parameter -Permission?
At all that have taken part in this issue: Is there a request for a feature inside of the discussion that I've missed? Please repeat here to plan futher steps.
Thanks.

I'm not sure if this is still a request for a new feature.
@L3onard80 : Do you still want to have the new parameter -Permission?
At all that have taken part in this issue: Is there a request for a feature inside of the discussion that I've missed? Please repeat here to plan futher steps.
Thanks.

Hi Andreas, the posts above gave me a workaround solution (that works, btw) but yes, i think having a parameter for the command is really helpfull.

I would agree if such a parameter made the function faster.
If not, filtering should be done with a Where-Object or Where() method.
What I see as added value is an extra property 'AppliedStatement' or something, which would be a copy of either the Grant or the Revokestatement. This would be the easiest way to select all statements that need to be saved or applied in a sync or restore process.

A param of that nature means we also have to clean up additional lines and is not just a string filter.


Cosmetics

Exports all 4 schemes
Re-formats the Sections so they can be de-duplicated in Swiftz

This better be the last time I have to see any of this.  God, we need a real constraints system so bad.

:boat:


Bump stack version

Hi there,
Just updating the buildpack to use the latest version of stack.
Thanks for the buildpack!

Thanks!


DeepLinking to Apps which are not Installed yet?

Is it possible to DeepLink to Apps which are not Installed yet?

Nope - this library is mainly for organizing your app internally, not communicating with other apps


Add Learn Chinese canvas

Zero To Mastery - Canvas 2022 🎉🎉
PR contains:

Add new "Learn Chinese" canvas that depicts a whiteboard with Chinese characters (means "okay" in English) written on it.

Breaking changes

None

Screenshots

Looks good to me, nice job 👍


bacalhau authenication via token CLI borken

I have deployed a cluster, but not authenticated to it yet via the CLI. e.g.
cat ~/.bacalhau/tokens.json
{}

Attempting to run a docker job fails due to invalid token and no prompt is given (as was previous behavior) to enter a token:
bacalhau docker run ubuntu:latest echo hello world
token: Error: Invalid token.
Invalid token.

Using the V2 API does prompt for a token, but it does so twice:
bacalhau job run testdata/jobs/docker-hello.yaml
token: token:

I am unable to enter a token successfully here

On the surface this appears to be related to the update service, e.g.
This fails:
frrist@cypress ~/.bacalhau> pwd
/home/frrist/.bacalhau
frrist@cypress ~/.bacalhau> ls
cert.crt  compute_store  config.yaml  executor_storages  libp2p_private_key  orchestrator_store  plugins  repo.version  tokens.json  user_id.pem
frrist@cypress ~/.bacalhau> bacalhau node list
token: token:

This works because there is an update.json file in the repo node:
```bash
frrist@cypress ~/.bacalhau> echo '{"LastCheck":"2024-04-10T15:37:38.341767311-07:00"}' > update.json
frrist@cypress ~/.bacalhau> bacalhau node list
token:


Origin of get_hwnd() on winit::Window

Hello, I've been learning Ash coming from Vulkano.  I was working with the vulkan-tutorial-rust which uses Ash, but with newer versions of things encountered breaking changes and have been checking out Ash's own example.  I am puzzled by a line 166 in lib.rs, let hwnd = window.get_hwnd() as HWND;
Winit's winit::Window (at version 19.5) has no such function get_hwnd(), so where does that come from ?  By the way, I would like to get this working so am interested in clues to how to generate the hwnd to pass to the creation info constructor.

Hi @kulicuu,
Winit version 0.19.5 has winit::os::windows::WindowExt trait that adds get_hwnd() function to winit::Window (https://docs.rs/winit/0.19.5/i686-pc-windows-msvc/winit/os/windows/trait.WindowExt.html). It was imported to visible space at line 164 in lib.rs so the compiler understood which function to call there.
I'm currently using latest Winit (0.22.1) and it has slightly changed winit::platform::windows::WindowExtWindows trait that adds both hwnd() and hinstance() methods to winit::Window.

Thanks very much, that was very obscure but the direction my research was tending.  Thanks!


the demo example is not working

What operating system, Node.js, and npm version?

system:
mac-os
Node.js
v20.9.0

What happened?
I follow the example here:
https://github.com/aralroca/next-translate?tab=readme-ov-file#with-app-directory-demo
git clone git@github.com:aralroca/next-translate.git
cd next-translate
yarn && yarn example:with-app-directory

but the demo it not working,
the web page with : 'http://localhost:3000/'  is 404

What did you expect to happen?
normal run
Are you willing to submit a pull request to fix this bug?
If I can identify the issue, I am willing to provide a fix.

Nextjs template also dont work

not working either

OMG, do I have to choose another solution? This is terrible. I just tried to do this and it doesn't work.  =_=!!!!


Support for more recent mir-algorithm

How much work would this be? @9il

Np, will update today

https://github.com/kaleidicassociates/influx-d/pull/36


ARTEMIS-1529 Fixing Ref count over asynchronous ack

@tkratky I am adding the test you create through this PR.. attributing the authorship to you.
if you could review please?

@clebertsuconic dothese tests pass with current fixes?

with this fix, yes

please, do not merge this yet

it's fine now.. false alarm


DCOS-10994: Implement declined offers API response transformation

This PR implements the transformation of the /queue API response into a structure that can be consumed by https://github.com/dcos/dcos-ui/pull/1338

@mesosphere-ci test this please

Thanks for the review @MatApple, I addressed all your comments and updated this to work with the latest API changes.

Looks good! Let's not let this be held back by @MatApple being out. @philipnrmn mind giving this a look, if you have time?

Making a few additional changes — sorry! Adding hold merge for now.

@mlunoe @philipnrmn This should be ready for review, now :)

This is great!

As a question, will the /queue "only" cover the tasks that are started by Marathon directly? Or also the case like the Kafka framework, where Marathon starts the scheduler, and the scheduler starts its own broker tasks? Thanks!

@jfurrow ^

@tobilg It is only for tasks started by Marathon directly.


more type improvements

add absoluteRenderBounds type
change Map => Record since JSON API responses can't have Map
add node children helpers

📦 Published PR as canary version: 1.13.3--canary.6.3ddc73b.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in v1.13.3 :rocket:


Revert "Merge pull request #1829 from syed/hvm-volume-attach-restart-fix"

This reverts commit d9bd01266ffb23f591283c058beff6e65d1cc4aa, reversing
changes made to ea7c48cf6127aeb73c1d25d7bcee52120ab85204.

This is not going to fix the build issue. The issue is different. I will open a new PR.


Multiple layouts?

How do I create multiple layouts for different routes? For instance
at http://<IP_ADDRESS>:3000/ - default.vue
at http://<IP_ADDRESS>:3000/about - another.vue
There is no mention about this at all from the doc - https://nuxtjs.org/guide/views#layouts. It would helpful if this guide is included.

Sorry, found it!

How did you solved the issue??

@Shamonshamonsha the answer is on that page actually https://nuxtjs.org/guide/views#layouts, under Custom Layout.


Can you guys maintain your presence in the apt repository.

If you run sudo apt install code-oss in Debian/Ubuntu (Kali in my case), you will get an old version of VSCode (1.55.1 I think, don't quote me on that.) This version of VSCode was prone to constant segfaults.
Are you guys able to get a maintainer for the apt repository, so that VSCode will:

Install as the latest version
Update when I run sudo apt update; sudo apt upgrade

code-oss isn't a product we maintain, only Code and Code Insiders. More details: https://code.visualstudio.com/docs/setup/linux#_debian-and-ubuntu-based-distributions


bootstrap columns offset

I'm brand new to laravel and laracogs so I very well may have missed something, but after initiating a brand new laravel project and adding the laracogs starter and bootstrap I have an issue with the layout where the main column is clearing or being pushed under the side column (screenshot attached). Any thoughts?

did you do the npm install and gulp?

Probably forgot a step. I moved on to try Semantic UI and it works great. I just reverted and retried bootstrap and it's working as well now, so I'm sure (as originally suspected) I was just missing something. Sorry about that, and thanks for your response!


[Bug]

This addon should clean up the added query parameters after navigating away from the story.
We could use the useEffect from @storybook/addons
import { useEffect } from '@storybook/addons';

export const decorator = () => {
  useEffect(() => {
    // add query-parameters from storybook-parameters
    return () => {
      // remove query-parameters we added before
    }
  }, [])
}

We should the following query-parameters from ever being deleted: id, viewmode, args, globals because they are storybook internals.

I encountered this on our project.  Addon is helpful enough and it was even putting the wrong query parameters into snapshots and a few other things, so felt important enough to fix.  Instead we just have our own local decorator (and got rid of this dependency), but it's essentially the same code, so it was relatively easy to pop a PR: https://github.com/storybookjs/addon-queryparams/pull/3

@shilman

would smtg like that work?
const withQuery = (Story, context) => {
  const [, forceRerender] = useState();
  const query = context?.parameters?.query;

  useLayoutEffect(() => {
    const href = window?.location?.href;
    if (!query || !href) return;

    const url = new URL(href);

    for (const [key, value] of Object.entries(query)) {
      url.searchParams.set(key, value);
    }

    window.history.replaceState(window.history.state, "", url.href);
    forceRerender({});

    return () => {
      // restore original url
      window.history.replaceState(window.history.state, "", href);
    };
  }, [query]);

  return <Story {...context} />;
};


Implement DDPM inversion

As discussed previously, I implemented  edit-friendly DDPM inversion drastically reducing runtime for the inversion step.
Additionally, the edit quality/robustness benefits from the inversion guarantees of DDPM, thus eliminating any inversion errors.
Also adding @apolinario.

As discussed previously, I implemented edit-friendly DDPM inversion drastically reducing runtime for the inversion step.
Additionally, the edit quality/robustness benefits from the inversion guarantees of DDPM, thus eliminating any inversion errors.
Also adding @apolinario.

I tried running the demo but got an error soon as i ran python run_tokenflow_pnp.py


While sending message with our own email, app converts email to 'you' in LHN

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Open any report
Send message with your own email eg: Hello this is<EMAIL_ADDRESS>Observe chat in LHN

Expected Result:
App should display message normally on LHN and notification
Actual Result:
App displays 'you' in LHN when we use own email in message
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.9-14
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/236053996-46ff8696-ee69-48b0-9850-ceb4896a44e4.mp4
https://user-images.githubusercontent.com/43996225/236054021-83387d91-16c3-41ea-b4a9-20c19d10c74e.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683083229303039
View all open jobs on GitHub

Triggered auto assignment to @muttmuure (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Dupe: https://github.com/Expensify/App/issues/18374

Hi @muttmuure, you have attached same issue number for dupe, can you check once and update the comment?

Oh yes, good catch. This is being handled internally here: https://github.com/Expensify/App/issues/17231


Bootstrap4

Lots of bootstrap CSS, bootstrap js,  and LESS

Pages:
-Home(index)
-Services
-Appointment/Schedule Appointment(dropdown)


Error cannot import browser lib

I use @dcspark/cardano-multiplatform-lib-nodejs for creating a keyring lib for my wallet (dev on extension and webapp). But there're many conflicts with the browser environment. I tried to replace with @dcspark/cardano-multiplatform-lib-browser but it failed from the import step. Can you help with this @rooooooooob @SebastienGllmt ?

Browser works without any problems, we are using both nodejs and browser in lucid evolution, maybe you can provide more details of your implementation in order to help