Setting Timestamp does not publish custom metric at datetime set in Timestamp property

Setting Timestamp does not publish custom metric at datetime set in Timestamp property

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

ID: 15654394-9de6-0024-2e9b-727f09ff03a0
Version Independent ID: a2554ff1-4e4a-c042-3072-f4b1a75fd47b
Content: MetricTelemetry.Timestamp Property (Microsoft.ApplicationInsights.DataContracts) - Azure for .NET Developers
Content Source: xml/Microsoft.ApplicationInsights.DataContracts/MetricTelemetry.xml
Service: application-insights
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@a30006441 I am not able to reproduce the issue and I could see timestamp being sent to Cutom Metric.  See below

@a30006441 We are proceeding with the closure of this issue as we haven't received any response. Please feel free to open a new issue for any other issues.


Run Travis CI against both JDK 7 and 8.

Also, upgrade to Travis's container-based infrastructure.
Fixes #547

Ping.

LGTM


Add option to configure leaderElection

Kubebuilder-backed controllers are supporting leader election as an option for high availability.
In our cluster, we have a policy that forbids single replica deployments.
It will be great to support leader election on pyrra side

I'm happy to support this.
Sadly I'm not sure how this would be implemented. Would there be a follower-leader type deployment of the Pyrra controller? Like, the leader fails and the follower takes over?
Feel free to propose changes to the code.

kubebuilder controller runtime support leader election. Yes, it will be a follower-leader scheme with locks in the config map.
So the user just runs 2 pods of the controller. The controller on startup trying to acquire a lock. If it is acquired than the controller act as a leader. If not it trying to consequently acquire the same lock with delays.

You can find more info here: https://book.kubebuilder.io/faq.html?highlight=leaderElection#after-make-run-i-see-errors-like-unable-to-find-leader-election-namespace-not-running-in-cluster


Ceph Primary Storage: Unsupported slash character by parser

ISSUE TYPE

Bug Report

COMPONENT NAME

Utils

CLOUDSTACK VERSION

4.18

CONFIGURATION

N/A
OS / ENVIRONMENT

N/A
SUMMARY

Current parser doesn't properly interpret a rbd:// URI with a secret containing a slash "/" character.
STEPS TO REPRODUCE

I've added a testcase that fails here to reproduce: https://github.com/apache/cloudstack/pull/7671

EXPECTED RESULTS

Unit test passes
ACTUAL RESULTS

Unit test fails (also silently fails on a real setup because the URL is incorrect)

fixed by #7708


update from upstream

chore(deps): update rust:1.75.0 docker digest to 87f3b2f
chore(deps): update enricomi/publish-unit-test-result-action action to v2.13.0
chore(deps): update dependency prettier to v3.2.5
chore(deps): lock file maintenance
chore(deps): update actions/download-artifact action to v4.1.2
chore(deps): update actions/upload-artifact action to v4.3.1
chore(deps): update enricomi/publish-unit-test-result-action action to v2.14.0
chore(deps): update dependency semantic-release to v23.0.1
chore(deps): update mcr.microsoft.com/devcontainers/rust:1-1-bullseye docker digest to 64161ff
chore(deps): update actions/setup-node action to v4.0.2
chore(deps): update dependency semantic-release to v23.0.2
chore(deps): update rust to v1.76.0
chore(deps): update returntocorp/semgrep docker tag to v1.60.1
chore(deps): update rust:1.76.0 docker digest to 8e87602
chore(deps): lock file maintenance
chore(deps): update github/codeql-action action to v3.24.1
chore(deps): update rust:1.76.0 docker digest to 3e95fdb
chore(deps): update returntocorp/semgrep docker tag to v1.61.0
chore(deps): update rust:1.76.0 docker digest to 01752fc
chore(deps): update rust:1.76.0 docker digest to 3c1dc1b
chore: fix startColumn/endColumn being 0. Is invalid. Normalize json file for diffing, ignore output. Diff is expected
chore(deps): update node.js to >=20.11.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.268%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
451

Relevant Lines:
1067

💛  - Coveralls

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


Remove user-node-remove on node remove

Issue: #38442

Problem

If a node is provisioned on <v2.5.1, rancher is stopped, and the node is deleted; Remove will not be called for the node causing orphaned v1.Nodes which default unmanaged v3.Nodes are then created for.
Solution

Remove the annotation on sync and v3.Node removal.
Testing

Engineering Testing
Manual Testing

Tested with a 1 etcd, 1 controlplane, 1 worker. On upgrade from v2.5.1 to v2.7-head, the node is properly cleaned up.

@Oats87 I've updated it not update inside the call to userNodeRemoveCleanup, and to just remove the finalizer without checking if the annotation was applied for two reasons:

It's not a very expensive operation for Remove
If for any reason the annotation failed to be applied previously (or someone manually removes it), the finalizer won't be removed.


Upgrade regenerator

regenerator<=v0.5.0 and defs<=1.0.1 require git://github.com/ariya/esprima.git#harmony, that's very slow.

I remove 0.8 0.9 in travis<EMAIL_ADDRESS>is coming!!! https://iojs.org/

ping @TooTallNate

Thanks!

Great! Can you bump a new version?

Hmm, it seems like v0.10 is failing now for some reason. Any ideas? https://travis-ci.org/TooTallNate/gnode/jobs/47008865

That's regenerator's bug, my PR is passed when it's 0.8.3, it's now 0.8.6 https://travis-ci.org/TooTallNate/gnode/jobs/46748339
https://github.com/facebook/regenerator/issues/168

@TooTallNate hi, you can retry it.

Ok good stuff. Thanks for the explanation.

v0.1.1 tagged and published to npm. :beers:

Thx

:+1:

Be sure that regenerator has remove Promise polyfill after 0.8.0, is it break gnode?
https://github.com/facebook/regenerator/releases/tag/v0.8.0


RuntimeError: expected a non-empty list of Tensors

Hello,when I run  python train.py --config config/softgroup_fold5_default_s3dis.yaml,it throw the following error.Could you please tell me how to deal it?
Traceback (most recent call last):
File "test_s3dis.py", line 338, in
test(model, model_fn, data_name, cfg.test_epoch)
File "test_s3dis.py", line 66, in test
preds = model_fn(batch, model, epoch)
File "/home/vipuser/PycharmProjects/pythonProject/SoftGroup_main1/model/softgroup/softgroup.py", line 482, in test_model_fn
ret = model(input_, p2v_map, coords_float, batch_idxs, batch_offsets, epoch, 'test', split=True, semantic_only=semantic_only)
File "/home/vipuser/miniconda3/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 547, in call
result = self.forward(*input, **kwargs)
File "/home/vipuser/PycharmProjects/pythonProject/SoftGroup_main1/model/softgroup/softgroup.py", line 385, in forward
proposals_idx = torch.cat(proposals_idx_list, dim=0)
RuntimeError: expected a non-empty list of Tensors

This error indicates that the proposals_list_list is empty. Did you make any modifications to the training config?

Thanks for your reply! The traning config you said is softgroup_fold5_default_s3dis.yaml?I train the original s3dis dataset ,have not changed it

Did you pretrain the backbone before train softgroup_fold5_default_s3dis.yaml

Yes,I did.
Could you please tell me which modifications to the training config can influence the proposals_idx_list?
Thank you very much.

softgroup.py line336 to line 339.Why did you ignore the floor and wall?

We ignore 2 first classes and derive instances directly from semantic maps since it is common that the scene has only one instance for these classes in S3DIS dataset. In #6, he successfully trained the model on S3DIS. If you didn't change anything, it seems weird that the proposals_idx_list is empty. Btw, does this problem happen at the beginning or middle of the training.

I understand! It is a pretty good job!Thanks a lot!


[enhancement] Add missing bower.json.

Hey, maintainer(s) of cowboy/jquery-outside-events!
We at VersionEye are working hard to keep up the quality of the bower's registry.
We just finished our initial analysis of the quality of the Bower.io registry:
7530 - registered packages, 224 of them doesnt exists anymore;
We analysed 7306  existing packages and  1070 of them don't have bower.json on the master branch ( that's where a Bower client pulls a data ).
Sadly, your library cowboy/jquery-outside-events is one of them.
Can you spare 15 minutes to help us to make Bower better?
Just add a new file bower.json and  change attributes.
{
  "name": "cowboy/jquery-outside-events",
  "version": "1.0.0",
  "main": "path/to/main.css",
  "description": "please add it",
  "license": "Eclipse",
  "ignore": [
    ".jshintrc",
    "**/*.txt"
  ],
  "dependencies": {
    "<dependency_name>": "<semantic_version>",
    "<dependency_name>": "<Local_folder>",
    "<dependency_name>": "<package>"
  },
  "devDependencies": {
    "<test-framework-name>": "<version>"
  }
}

Read more about bower.json on the official spefication and nodejs semver library has great examples of proper versioning.
NB! Please validate your bower.json with jsonlint before commiting your updates.
Thank you!
Timo,
twitter: @versioneye
email<EMAIL_ADDRESS>VersionEye - no more legacy software!

Please include a 'main' attribute in bower.json as well


commit updated ozone version

What changes were proposed in this pull request?
pom.xml changes and release tag for Ozone  1.1.0 release
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5070
How was this patch tested?
Clean build/CI

Not needed Anymore.


Improve WebView build system

This is an important rework of how building the WebView assets work.
Considered 'merge-ready', it is the base for further improvements.
This rework now enables the WebView to load its assets (styles, js, potentially fonts) from external files and not need to be built into the single JS file.
This approach is needed so we can embed:

fonts
emoji or other images

Makes it simpler to embed:

polyfills and other vendor JS files
styles that are pre-generated (code-highlighting, LaTeX/KaTeX)

In addition, this makes the reported error line-numbers in JS reliable.
This also adds:

full code-formatting
LaTeX styling

Excellent, thanks @borisyankov ! It'll be great to have this system cleaned up -- I'm already appreciating how it makes the IDE able to highlight and show warnings in theme.css like a normal CSS file. :-)
A few things I'd like to see changed before merging this:

There are a lot of spots where the changes in one commit don't really make sense without the context of some later commit.

For example: one commit adds emoji.css and explains that the point is to stop generating the data dynamically in cssEmojis.js, but it doesn't actually make any changes related to cssEmojis.js. Then a few commits later we stop using cssEmojis.js in css.js, in a commit that's doing a lot of other stuff and doesn't mention that change in its commit message. In the end it looks like the actual cssEmojis.js file sticks around even though it's not used anymore.
An example of what I'd much rather see: one commit (a) adds emoji.css, (b) switches css.js to use it, and (c) deletes cssEmojis.js -- and it doesn't do anything else. I think this would make it a lot easier to follow the changes; it'd probably also make it less likely for something to fall through the cracks like leaving the unused file around, precisely because it's so much easier to look back at and reread.

It's kind of unfortunate to make a bunch of copies of all these files. For one thing, it makes them all look like source files you have to edit when making changes -- and it makes them look like they might differ between the platforms, which would be really complex to read.

There must be some reasonable way we can script this, making these copies happen at build time. E.g. on the Android side, we can add a few lines in the Gradle scripts to just invoke our build-webview.js. Let's do that instead.
I know this was already awkward this way with generatedEs3.js, but it gets a lot worse with so many files, so I'd like to solve the problem properly before doing that.
If there is a generated file we end up keeping in the repo, I'd want it to be super clear (a) that it is generated and (b) how to edit/regenerate it. Like the header I added at the top of generatedEs3.js.

Small Git tip: don't delete a -diff line from .gitattributes. It remains useful when looking at history from before the file was removed -- e.g. when reading this branch, I get a big diff for where you remove that file.

I did undo the removal of the diff line.
codeToCss.js is not deleted because we will use it in future to regenerate the css static file, if the input data changes. I did update the commit message to include that information.

About the duplication of files. I researched today, and while Android is reasonably straight-forward, not so with iOS.
I will continue exploring a solution for both platforms but suggest we do work on merging this first?

codeToCss.js is not deleted because we will use it in future to regenerate the css static file, if the input data changes. I did update the commit message to include that information.

Ah, OK, thanks.
Would you add something in the repo explaining how to do that regeneration? A little script in tools/ would be ideal; but if for any reason it's a pain to script, then some written instructions would be totally fine. I just want to make sure it's easy for any of us (including future-you) to reproduce what you did.
The rest of that example still applies -- I'd be much happier seeing a commit that added emoji.css, switched css.js to use it, and didn't do anything else.
Similarly, I'd like to have one commit (a) add matches-polyfill.js, (b) switch script.js to use it, and (c) remove matchesPolyfill.js. And another commit that does the same thing for smooth-scroll.js / smoothScroll.min.js.
I think a good commit, or series of commits, to start with would be to just switch from generatedEs3.js to the zulip.js resource. That has the fewest moving parts because that's already a generated file; and once that's done, the others can follow by building on the infrastructure for that one. I would gladly merge some commits that do that, as the first N commits on a branch, even before we're done with any revisions on the other changes -- that would help us move things forward.

About the duplication of files. I researched today, and while Android is reasonably straight-forward, not so with iOS.

I will continue exploring a solution for both platforms but suggest we do work on merging this first?

Sure; I'd be OK with merging for now a version with the duplicate files. We can focus first on the other aspects discussed above.

BTW, my current thinking is it'd be good to turn our attention back to this after we complete the RN 0.56 and 0.57 upgrades (#2788 and #2955); we've seen a couple of instances recently of places where it'd be good to have this done.

Bumping the priority because this blocks #2660, which people keep asking for and I just bumped.

Much of what this PR aimed to do has now been accomplished with #3636.
There are still some further things to do. I think those will be best tracked as we see things we need (e.g. to complete #2660) rather than based on this prototype PR, so closing it.


Cannot get this to work.

I have Visual Studio installed, and the Team Foundation add-in appears in both MSP Pro 2016 and MS Excel. The Excel integration with Azure DevOps works flawlessly. However, every time I try to connect  to DevOps from MSP Pro 2016, I get error TF80070 "Team Foundation encountered an error while performing the operation. It is recommended that you save your work and restart the application."

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

ID: 4f6edd47-46d7-ab0d-db47-d73bc45d6b43
Version Independent ID: 6ac2ae49-0bd0-2c28-fc87-7f034dd96443
Content: Create your backlog and tasks using Project - Azure Boards
Content Source: docs/boards/backlogs/office/create-your-backlog-tasks-using-project.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

Welp, it started working after a re-install of MS Project Pro 2016.

@okiedude Glad you got it working, I'm assigning this to the author of the article for review before closing the issue.

@okiedude - Thank you for your inquiry, and glad you were able to get it to work. Please note that starting with Visual Studio 2019, the Team Foundation plug-in for Office is deprecating support for Office Project. You will be able to continue to use Office Excel.

Yeah, I picked up on that during my research, which I find very
unfortunate. I will probably have to revert to using MS Project exclusively
if/when that occurs.
VSTS / Azure DevOps is very lacking in long-term planning capabilities.
Cheers though, and thanks for the note.
Andy
On Mon, Feb 4, 2019 at 2:48 PM KathrynEE<EMAIL_ADDRESS>wrote:

@okiedude https://github.com/okiedude - Thank you for your inquiry, and
glad you were able to get it to work. Please note that starting with Visual
Studio 2019, the Team Foundation plug-in for Office is deprecating support
for Office Project. You will be able to continue to use Office Excel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/vsts-docs/issues/3199#issuecomment-460407114,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVkagvU0cPXac_CuxbUj2G_3S-VAR7nks5vKJyVgaJpZM4adGCy
.


TEST for CI! Don't merge.

Issue Number. Is this pull request related to any outstanding issues? If so, list the issue number.
Describe the changes made. A clear and concise description of what the problem is and what you did to fix it. E.g. [...] was happening and I've changed [...] to fix it.
Goals and Outstanding Issues. A clear and concise list of goals (to be) accomplished.

[ ]

Major files changed.

[ ]

Status.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Additional context. Add any other context or screenshots about the pull request here.

Codecov Report

Merging #5 (2444a12) into develop (bcce34d) will decrease coverage by 1.02%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop       #5      +/-   ##
===========================================
- Coverage    41.95%   40.92%   -1.03%
===========================================
  Files          131      131
  Lines        16909    16711     -198
===========================================
- Hits          7094     6839     -255
- Misses        9815     9872      +57

Flag
Coverage Δ

unittests
40.92% <0.00%> (-1.03%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/westpa/core/sim_manager.py
79.05% <0.00%> (ø)

src/westpa/mclib/__init__.py
6.17% <0.00%> (-50.62%)
:arrow_down:

src/westpa/work_managers/zeromq/worker.py
82.54% <0.00%> (-12.76%)
:arrow_down:

src/westpa/work_managers/processes.py
77.86% <0.00%> (-12.30%)
:arrow_down:

src/westpa/cli/tools/w_pdist.py
72.85% <0.00%> (-11.98%)
:arrow_down:

src/westpa/cli/tools/w_direct.py
79.01% <0.00%> (-6.18%)
:arrow_down:

src/westpa/core/trajectory.py
15.95% <0.00%> (-3.84%)
:arrow_down:

src/westpa/cli/tools/w_assign.py
77.38% <0.00%> (-3.41%)
:arrow_down:

src/westpa/tools/wipi.py
24.75% <0.00%> (-2.79%)
:arrow_down:

src/westpa/work_managers/zeromq/core.py
79.33% <0.00%> (-2.33%)
:arrow_down:

... and 30 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Filter + other operators catch too much - should only catch the predicate call

https://github.com/SoftwareAG/apama-rxepl/blob/837feae2d226a4f724f13ad815f9623618905301/src/rx/operators/internals/Filter.mon#L41-L47

Same is true for Map...
https://github.com/SoftwareAG/apama-rxepl/blob/master/src/rx/operators/internals/Map.mon#L40-L45

This might not actually be a problem... I think all exceptions are caught by he subscriber anyway


Install required Atom plugins for new user

When we init a new developer's copy of the Flutter code, we can also install all the appropriate Atom plugins (if the user has Atom installed).
We probably also want to check if Atom is installed, and if not, prompt the user to download it (or, if we can, install it for them).

cc @devoncarew

For info:
apm list -b will show what's already installed, like:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
apm install dartlang will install the plugin.
And apm --version will print the current tool version, and fail nicely if apm is not installed.

We show IDE plugin information in flutter doctor. I don't think this feature is planned. Please reopen if we want to tackle this.


AdMob adaptive banner

Are you willing to add an adaptive banner?

@AdelKanso
There's a similar open feature request describing your case, https://github.com/FirebaseExtended/flutterfire/issues/2003.
Please follow-up there for updates.
Closing this as duplicate.


Unbundle libs

[ ] six
[ ] jdcal
[ ] decorator
[ ] h5io
[ ] tempita

I think we should use system libs for because those are ready for system-installing

I can make patches for you, it will take few hours, but before I want to ensure that you are interested to accept patches.

Not sure what you are proposing. To minimize installation issues we have keep them in externals, I don't see any strong reason to change this, it save's us a lot trouble I think.

On 08 Nov 2015, at 20:10, Igor Gnatenko<EMAIL_ADDRESS>wrote:
six
jdcal
decorator
h5io
tempita
I think we should use system libs for because those are ready for system-installing
—
Reply to this email directly or view it on GitHub.

But when we're talking about packaging into distros (I'm packaging for Fedora) it causes troubles because bundled libraries isn't allowed.

for debian there are some patches that are applied to remove these from the
repo and use system versions. I think you should do the same for fedora.
See :
https://packages.debian.org/sid/python/python-mne

see
http://anonscm.debian.org/cgit/debian-med/python-mne.git

For Fedora I did unbundling, but I'd want to send to upstream. That's why I created this issue and ask developers if they interested.

In ext we could first try to load the system version and fall back to our bundled version. Then the only thing the patch needs to do is exclude certain files from mne/externals/.

I would not change anything to master but apply patches during packaging
for the different distributions. As we do for debian

+100
On Mon, Nov 9, 2015 at 10:09 AM, Alexandre Gramfort <
<EMAIL_ADDRESS>wrote:

I would not change anything to master but apply patches during packaging
for the different distributions. As we do for debian
—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/issues/2600#issuecomment-155002011
.

Closing as we've decided to use the patch-and-package method instead


Can't Update permission dialog message for IOS devices

My Code is
<QRCodeScanner
onRead={(e) => onSuccess(e)}
showMarker={true}
markerStyle={{ borderColor: '#3a82cf' }}
permissionDialogMessage={"Camera access is required to scan the QR code"}
cameraContainerStyle={{ paddingTop: wp('20%') }}
/

I think you can change this on info.plist where you set cammera permissions. permissionDialogMessage is for android only as said in the docs.


[DE-716] Compression of requests and responses

Adding compression of requests and responses, as implemented in https://github.com/arangodb/arangodb/pull/20128
The ArangoClient gets two optional parameters:

request_compression - Represents the compression strategy, None by default. The reason for passing in an object instead of a string (such as deflate) is to allow the client to fine tune the compression algorithm (the compression level).
response_compression - The equivalent of Accept-Encoding. This has no effect unless the server is configured to use encoding.

Codecov Report
Attention: Patch coverage is 93.33333% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 97.97%. Comparing base (ed35c9d) to head (20bef3b).

Files
Patch %
Lines

arango/http.py
88.23%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #328      +/-   ##
==========================================
- Coverage   98.01%   97.97%   -0.04%
==========================================
  Files          26       26
  Lines        4231     4257      +26
==========================================
+ Hits         4147     4171      +24
- Misses         84       86       +2

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


Build discover page in React Native

The discover / landing page will be based on the design prototype. This possibly needs to be broken down further into components depending on our approach.

Sub-issues:
https://github.com/lbryio/lbry-android/issues/24
https://github.com/lbryio/lbry-android/issues/25

Done.


Please make me an author on the AdoptOpenJDK blog

I'd like to contribute an article to the blog at https://blog.adoptopenjdk.net/, but am not an author, so I can't.
Please make me an author.
Thank you.

Me too please

Can you help me with this @tellison?

I think I can add you both, can you DM me your email addresses in Slack?

I am working on getting github oauth working with wordpress. In the mean time you need to go to https://blog.adoptopenjdk.net/wp-login.php?wle to login with wordpress credentials

Both have been added.


Excuse me, if this box is not checked, does it mean that the code for splitting and splitting has not been released yet?

Excuse me, if this box is not checked, does it mean that the code for splitting and splitting has not been released yet?

Yes.

请问什么时候能发布呢哥

Yes.
Excuse me, when will it be released?

We still working on it.

I am closing this issue. Please feel free to reopen it if necessary.


[h264e] LowDelayBRC mode updated for non HRD compatible sync modes

don't merge

PR name and commit name changed. Added description into commit. (this feature does not supported on Linux yet)


rename remaining "evasion or tolerence terms"

GO:0030682    evasion or tolerance of host defenses
GO:0020012    evasion or tolerance of host immune response
-> mitigation of blah

OK all done


Support .kubeconfig files for authentication and cluster settings.

Use the clientcmd API in order to read a kubeconfig file to configure the k8s client.

@sanabby @rombie Authentication is required in order to connect to the openshift API server.
Tested with both k8s and openshift origin.


Refactoring

added some TIGL_EXPORTs
formatting
removed an unnecessary cast
added CTiglUIDManager::SetParentComponents
added CCPACSFuselageProfiles::AddFuselageProfile override
removed CCPACSFuselageSectionElement::GetProfileIndex
prepared code for relative positioning in CTiglRelativelyPositionedComponent

The new Exports in front of the inlined methods have to be removed!  There's already a related PR for your generator that removes these exports.
Just a sidemark: we want to release 3.0 rc1 today, so we won't be able to include this in the release. I will add the missing return statement though.


Is fine tuning with e.g., LORA supported?

It looks like FSDP is a pretty awesome module to distribute the base model, but does this codebase support Lora fine tuning? I think usually what we would like DPO doing is training the adaptor layer not the entire base model. If we can load the model in FSDP way while fine tuning Lora layer only, that would make GPU memory free from even the largest model I guess.

I recently reimplemented DPO with QLoRA on LLaMA-7B model.
The model is already available on huggingface: https://huggingface.co/abaheti95/dpo_qlora_hh
Here is the respective code for implementation: https://github.com/abaheti95/LoL-RL/blob/main/dpo_qlora_llama_hh.py
I hope this helps.


Program to set up ad-hoc wifi network

For users with a "complicated" network, it would be nice for the leader pioreactor to turn into a adhoc wifi network for itself and any other Pioreactor in the cluster. We should make this easy.

RaspAP is pretty good. Some notes:

After installation, it's webgui conflicts with pioreactors gui on port 80. So it should be changed in /etc/lighttpd/lighttpd.conf, see docs here.
SSID and pass can be set to anything.
The leader can still be accessed via hostname.local (Assume you are on the network).

This feels like a good solution for those who will experience network problems (ppl at universities, etc.)

Some notes. Setting up an AP with RaspAP was easy. I changed the port, SSID to pioreactor and password to raspberry. Future clients (workers) could connect to the AP, and pio add-pioreactor worked. Upon job start though, I was getting a MQTT could not connect error. For some reason, ping leader3 would redirect to <IP_ADDRESS> (the worker), but ping leader3.local would resolve correctly. Same with ssh and MQTT publishing.
I think I have a fix: 0ea222ee

One unknown is should we ship our image with the software?

PR here: https://github.com/Pioreactor/CustoPiZer/pull/4


fast/file: formalize wire format

currently saving with ttl to a file fast backend uses an ad-hoc wire format, with the first 23 bytes recording the time when the file was created and the ttl duration. this should be formalized as a spec

closed by e333ce3e5bfa3b9115f10d2102f96ad5ee0b6d54


Add translated enums

Is your feature request related to a problem? Please describe
It would be nice to have examples of how to use parameterized input.
Describe the solution you'd like
One thing that would be great is an example of an enum as a parameter. If you add an enum as a parameter, you just need to add the translations and discord.py will automatically handle them. If you follow this example from the docs, you only need to add apple, banana, and cherry` to the translator:
class Fruits(enum.Enum):
    apple = 1
    banana = 2
    cherry = 3

@app_commands.command()
@app_commands.describe(fruits='fruits to choose from')
async def fruit(interaction: discord.Interaction, fruits: Fruits):
    await interaction.response.send_message(f'Your favourite fruit is {fruits}.')

In this example, (I believe) you only need to replace the names with locale_strs
@app_commands.command()
@app_commands.describe(fruits='fruits to choose from')
@app_commands.choices(fruits=[
    Choice(name='apple', value=1),
    Choice(name='banana', value=2),
    Choice(name='cherry', value=3),
])
async def fruit(interaction: discord.Interaction, fruits: Choice[int]):
    await interaction.response.send_message(f'Your favourite fruit is {fruits.name}.')

Describe alternatives you've considered
n/a
Additional context
Thank you so much for making this project! I'm using this now and learning Fluent to add to my current bot. I hope this project helps a lot of people!

Sorry for taking a while to respond! I've added a new cog to implement the choice example, using the decorator form to help gettext auto-detect the localizations.


Add wrap_lines: bool option allowing wrapping be disabled entirely

Hi!
I want to be able to disable line wrapping entirely for logging runs and for users that would rather rely on their terminal's line wrapping. This pull request introduces a wrap_lines option which disables wrapping. Since textwrap::fill is used insert prefixes as well, this requires a little implementation to preserve that behavior.

Thanks!


Fix/invalid custom events actors when pasting external scripts

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fix

What is the current behavior? (You can also link to an open issue here)

When non-custom events scripts are pasted into custom events
the actor fields referencing scene actors weren't rendered
properly inside the custom event.

What is the new behavior (if this is a feature change)?

This patch adds a fix method that check if the actors are
scene actors and returns "0" (Actor A) if that's the case.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No

Other information:

Thanks @pau-tomas looks good, I think you've just accidentally included the cart size commit in with this PR though.
If you remove that I think this should be good to merge.

Fixed. Thanks!


IGListKitCrashes when used in an iMessages Extension

New issue checklist

[ x] I have reviewed the README and documentation
[x ] I have searched existing issues and this is not a duplicate

General information

Library version(s):1.0.0
XCode:8.0
iOS version(s):10.0.x
Devices/Simulators affected:iPhone 7Plus
Reproducible in the demo project? (Yes/No):Yes

Running iMessage Apps which have IGListKit included via CocoaPods results in the app crashing on launch with the error like the following:  dyld: Library not loaded: @rpath/IGListKit.framework/IGListKit
Referenced from: /Users/demo/Library/Developer/CoreSimulator/Devices/5C343568-A532-405F-8B65-52A049827328/data/Containers/Bundle/Application/AA18B7D3-48C4-4958-A14C-C056A309D6D8/IGListStickerDemo.app/PlugIns/MessagesExtension.appex/MessagesExtension
Reason: image not found
Check out  https://github.com/ishabazz/IGListKitMessagesExtensionDemo  for a sample project that exhibits this error.

I've definitely seen this error before, but that was using a non-Swift library in a Swift app using Buck for dep management. Might be something similar though.

Not clear if this is:

a bug in IGListKit
a bug in CocoaPods
a issue with project setup

Off the bat I get an Xcode warning in the sample project:

ld: warning: linking against a dylib which is not safe for use in application extensions: /Users/rnystrom/Library/Developer/Xcode/DerivedData/IGListStickerDemo-cherwvpgwwdqmjhkvyhkxnqnciyx/Build/Products/Debug-iphonesimulator/IGListKit/IGListKit.framework/IGListKit

After $ pod install I see some weird CocoaPods warnings:
[!] The `IGListStickerDemo [Debug]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-IGListStickerDemo/Pods-IGListStickerDemo.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `IGListStickerDemo [Release]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-IGListStickerDemo/Pods-IGListStickerDemo.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

Ok.  To recap, you removed it from the Podfile, ran pod install and  manually installed the framework?

@ishabazz I actually didn't remove it from the Podfile at first, just added to Linked Libraries and Frameworks. Then I built, got compiler errors, removed the framework from Linked Libraries and Frameworks, then did $ pod install again. This definitely isn't the answer but might be a clue to what's going on.

I looked into that initial compiler warning and it leads here https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/ExtensionOverview.html#//apple_ref/doc/uid/TP40014214-CH2-SW6

Fixing the warning in #79

@ishabazz ok now I can't get it to happen at all anymore. I ran
$ pod deintegrate
$ rm -rf ~/Library/Developer/Xcode/DerivedData
$ pod install

It works and installs on multiple simulators and device.
I believe my Podfile is unchanged from what you originally sent:
target 'IGListStickerDemo' do
  use_frameworks!
  pod 'IGListKit'
end

target 'MessagesExtension' do
  use_frameworks!
  pod 'IGListKit'
end

hmm...tried that but mine still crashes. Your Podifle is the same as mine

@ishabazz a couple other configs I tried that seemed to work:

Remove IGListKit from the main target since its empty
Remove use_frameworks!

Progress!  I can get the demo project to run without crashing.  I get a compiler error when trying "import IGListKit" though.

@ishabazz any update on this? Not really sure what to do here :/

Still a problem. Compiles fine until you try to import IGListKit, then doesn't compile and gives a "No such module 'IGListKit' found"  Did it work for you?

Compiles fine until you try to import IGListKit, then doesn't compile and gives a "No such module 'IGListKit' found"

Hm... 🤔 Sounds like this is probably a project setup issue... ?

Created a very basic example over on my fork (here) of an iMessage extension.
I've also downloaded your demo repository and found the issue: In your "Build Phases" tab you have a run action for '[CP] Copy Pods Resources' but not one for '[CP] Embed Pods Frameworks' hence the error.
I will create a pull request on your demo repository with a fix for this! (Added the missing run script)

@rnystrom Relating to my previous comment, how would you feel about adding extension examples into this repo? Happy to make modifications/make them more useful!
my fork contains an example for both a Today Extension and an iMessage Extension.

Thanks  @Sherlouk!

@Sherlouk yes yes yes yes yes! That would be amazing! Should we clean up and add your fork to the example or should we make something new?

By the way.  When trying to submit the build to TestFlight I ran into this issue  http://stackoverflow.com/questions/40005130/error-itms-90685-cfbundleidentifier-collision-there-is-more-than-one-bundle
Still working on a resolution

@ishabazz -- This should be fixed with CocoaPods 1.1
http://blog.cocoapods.org/CocoaPods-1.1.0/

@rnystrom @ishabazz Flagging to be closed?
There's now an example in the pack, and the issue at hand was seemingly resolved.

👍
will re-open if needed

I'm still getting this warning intermittently. I'm using pods 1.6.1. Why is this happening and how do I fix it.


Please sign the CLA

Hi contributors!
Casdoor has now required all code contributors to sign the CLA. This also includes the contributors in the past. We appreciated your cooperation!
Sign it via: https://cla-assistant.io/casdoor/casdoor
@ffyuanda @chinggg @hyperzlib @zhongjixiuxing @leopku

Done.

@ffyuanda @chinggg @hyperzlib @zhongjixiuxing @leopku


krb5.kdc option should accept an array

The krb5.kdc NixOS option should accept an array so that multiple kdc entries can be specified for a realm. The output would look similar to the snippet at http://web.mit.edu/kerberos/krb5-devel/doc/admin/install_kdc.html#krb5-conf :
[realms]
    ATHENA.MIT.EDU = {
        kdc = kerberos.mit.edu
        kdc = kerberos-1.mit.edu
        admin_server = kerberos.mit.edu
    }

I believe krb5.kerberosAdminServer should also support the same, although I'm not certain of this one. An example of multiple admin_server lines is at: https://help.ubuntu.com/lts/serverguide/kerberos-ldap.html

Pinging @wkennington who performed the last commit on the relevant file.

(triage) Was this solved?

No.

Do you want to create a PR then?

No. I filed this once I became aware of the disconnect between the kdc config and NixOS', but I personally don't use either. Was thinking that the maintainer might care, but I suppose I was wrong.

I suppose we tag this with the good-first-bug thingy. cc @bennofs

Closing this due to lack of interest in fixing it, and I've moved on to another distro.


Added required field indicator for address questions

Description
Added the required field indicator (red asterisk) onto the address question form.
Release notes
Added the required field indicator (red asterisk) onto the address question form.
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
[x] Assigned to a specific person, civiform/developers, or a more specific round-robin list
[ ] Added an additional reviewer from outside your organization as FYI (if the primary reviewer is in the same organization as you)
[x] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[ ] Extended the README / documentation, if necessary

Issue(s) this completes
Fixes #7993

Before:

After:


PRM-823 Updated summary card to display text

Looks good, just some clean-up & formatting tasks

Updated with the suggested changes


Android emulator

I use Chrome version 47.0.2526.111 m (64-bit) and I cannot run Android emulator at all on https://rnplay.org/ .
By the way, this is really a cool work.

Can you try this again? we had an issue with our upstream simulators.

It seems as corrected.


support for ip association in classic model

Problem description
azure-servicemanagement-legacy has no methods to associate / disassociate a reserved ip to a deployment. REST docs: https://msdn.microsoft.com/en-us/library/azure/mt416758.aspx
Solution
I'm going to add support for that in the SDK which will then be used in
https://github.com/SUSE/azurectl
Current state of implementation visible here:

git clone https://github.com/SUSE/azure-sdk-for-python
git checkout reserved_ip_association

Thank you :)

If I only can get the recording to work :) I sent you an e-mail about my issue, hope you don't mind

@schaefi was a crazy day, sorry for the delay in response, but you were right to send me an email :). I look asap.

This PR should allow you to do your testing more easily:
https://github.com/Azure/azure-sdk-for-python/pull/699

Thanks, I merged and rebased my branch so working on top of your changes. However I'm still facing an authentication problem. More details by mail. Thanks for your help

Wonder how the sdk perform the ARM public ip association and disassociation? Please let me know if you have any sample code to reference.
Thanks.
Li

For ARM, just use the NIC sdk:
saved_public_ip = nic_vm1.ip_configurations[0].public_ip_address
nic_vm1.ip_configurations[0].public_ip_address = None
network_client.network_interfaces.create_or_update(rg, name1, nic_vm1)
nic_vm2.ip_configurations[0].public_ip_address = saved_public_ip
network_client.network_interfaces.create_or_update(rg, name2, nic_vm2)

And thanks @lyan-git for your tests on this ;)
This is the same approach than PowerShell:
https://azure.microsoft.com/en-us/documentation/articles/virtual-network-ip-addresses-overview-arm/#comment-2789018446

Released in 0.20.4, I authorize myself to close the issue, please tell me if there is something else to add.
Thanks again for the PR!


Crash when running tensorflow.python.ops.gen_nn_ops.max_pool_grad_with_argmax

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
No
Source
binary
Tensorflow Version
2.10.0
Custom Code
Yes
OS Platform and Distribution
Ubuntu 22.04
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Check failure with the following input arguments.

Standalone code to reproduce the issue
import tensorflow as tf
import numpy as np
from tensorflow.python.ops import gen_nn_ops
try:
  try:
    with tf.device('/CPU'):
      arg_0_tensor = tf.random.uniform([2, 3, 3, 1], dtype=tf.float32)
      arg_0 = tf.identity(arg_0_tensor)
      arg_1_tensor = tf.random.uniform([2, 2, 2, 1], dtype=tf.float32)
      arg_1 = tf.identity(arg_1_tensor)
      arg_2_tensor = tf.random.uniform([2, 2, 2, 1], minval=-256, maxval=257, dtype=tf.int64)
      arg_2 = tf.identity(arg_2_tensor)
      ksize_0 = 1
      ksize_1 = 2
      ksize_2 = 2
      ksize_3 = 1
      ksize = [ksize_0,ksize_1,ksize_2,ksize_3,]
      strides_0 = 1
      strides_1 = 1
      strides_2 = 1
      strides_3 = 1
      strides = [strides_0,strides_1,strides_2,strides_3,]
      padding = "VALID"
      include_batch_in_index = False
      out = gen_nn_ops.max_pool_grad_with_argmax(arg_0,arg_1,arg_2,ksize=ksize,strides=strides,padding=padding,include_batch_in_index=include_batch_in_index,)
  except Exception as e:
    print("Error:"+str(e))
  try:
    with tf.device('/GPU:0'):
      arg_0 = tf.identity(arg_0_tensor)
      arg_0 = tf.cast(arg_0, tf.float32)
      arg_1 = tf.identity(arg_1_tensor)
      arg_1 = tf.cast(arg_1, tf.float32)
      arg_2 = tf.identity(arg_2_tensor)
      arg_2 = tf.cast(arg_2, tf.int64)
      ksize = [ksize_0,ksize_1,ksize_2,ksize_3,]
      strides = [strides_0,strides_1,strides_2,strides_3,]
      gen_nn_ops.max_pool_grad_with_argmax(arg_0,arg_1,arg_2,ksize=ksize,strides=strides,padding=padding,include_batch_in_index=include_batch_in_index,)
  except Exception as e:
    print("Error:"+str(e))
except Exception as e:
  print("Error:"+str(e))

### Relevant log output

```shell
2023-01-21 12:49:08.508138: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-01-21 12:49:08.623891: E tensorflow/stream_executor/cuda/cuda_blas.cc:2981] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2023-01-21 12:49:09.210798: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/lib/
2023-01-21 12:49:09.211024: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/lib/
2023-01-21 12:49:09.211033: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2023-01-21 12:49:09.832017: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:980] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-01-21 12:49:09.861818: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudnn.so.8'; dlerror: libcudnn.so.8: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/lib/
2023-01-21 12:49:09.861835: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1934] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2023-01-21 12:49:09.862084: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-01-21 12:49:09.880100: F tensorflow/core/kernels/maxpooling_op.cc:1065] Check failed: grad_out_index >= output_start && grad_out_index < output_end Invalid output gradient index: 146, 0, 18
Aborted

</details>

Hi, @nimashiri
Apologies for the delay and I was able to replicate the issue and I observed, Given code is working fine on GPU but same code is crashing on CPU so we have to dig more into this unexpected behaviour for CPU so if you have any idea or thoughts what may be the root cause for crashing code on CPU it will be greatly help us to fix the issue
I have added screenshot where code is running fine on GPU and we'll update soon about this unexpected behaviour issue for CPU. Thank you!

Hi, @nimashiri
Apologize for the delay and I tried to run your given code on Google colab and also on Ubuntu 22.04 with CPU and GPU and in Google colab code is getting crashed so I have attached screenshot of error log below and for Ubuntu 22.04 with CPU and GPU I'm getting the exact same error as you mentioned in your log output. Thank you!
Here is screenshot of error log for Google Colab Run (CPU) :

Here is screenshot of code run on Ubuntu 22.04 with CPU and GPU  and I ran code multiple times but I was getting the same error

This is a real assertion failure that should be fixed. PRs welcome.
Not a vulnerability for which credit would be given though, given it is only an assertion failure, so impact is minimal

(sorry, closed by mistake)

@learning-to-play

@learning-to-play

This bug is not fixed on 2.13.0.

@cantonios This issue seems to be related to TF Ops. Could you help triage?

@dmc1778
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The issue you are getting because the minval and maxval that you are initialising in the arg_2_tensor. The values must be between 0 to 8. Kindly find the gist
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


tests: temporarily disable 999-deadlock-check.sh

Signed-off by: Ian Vernon<EMAIL_ADDRESS>

Closing in favor of #2194


Set explicit type for rock directory

Problem
In our CI, rock version comes from:
rock_version=$(yq -r '.version' $GITHUB_WORKSPACE/rock/$file)

#...

upload_item_format='{"source":"%s","commit":"%s","directory":"%s","release":%s}'
upload_item=$(printf "$upload_item_format" \
  "canonical/${{ inputs.rock-name }}-rock" \
  "${{ steps.commit-sha.outputs.commit_sha }}" \
  "$rock_version" \
  "$rock_tags" \
)

oci-factory CI failed because the version "0.120" was parsed as 0.12.
Manually adding quotations helped.
Solution
Adding nested quotes seems tricky so adding an explicit type tag instead.
Ref.

The problem with this is that yq doesn't really pick it up (meaning !!str remains in the final yaml) and I'm concerned it might break CI on the OCI Factory side as that has been a bit too precise in the past.
I'm experimenting locally, and finding that with version yq (https://github.com/mikefarah/yq/) version v4.40.5, the current CI would add quotes. I see that no yq version is explicitly specified, so maybe we're using the wrong one?
I'd ask you to also try the current code locally and see what happens; if can run:
# 1. `cd` to your oci-factory cloned repo
# 2. Make sure you're using `bash` instead of your shell, to be 100% sure
upload_item_format='{"source":"%s","commit":"%s","directory":"%s","release":"%s"}'
upload_item=$(printf "$upload_item_format" "canonical/alertmanager-rock" "89abcd" "0.120" "0.120-22.04")
yq ".upload += $upload_item" ~/Repositories/Canonical/oci-factory-lucabello/oci/alertmanager/image.yaml

You should see directory: "0.120", with the quotes being there.


How to upgrade dark sdk?

The dart sdk included in flutter is 2.1.0-dev.9.4.flutter-f9ebf21297. A plugin stripe_payment need version 2.1.1, I tried to upgrade it but could not find a way. Any idea?

The way to update the Flutter-included Dart SDK is to update Flutter.
There is no way to update the Dart SDK individually.
Please consider asking support questions in one of the other channels listed at http://flutter.io/support .


[GAWB-2498] Notebook Service: poll Dataproc to get cluster IP

https://broadinstitute.atlassian.net/browse/GAWB-2498
Added a ClusterMonitorActor/Supervisor which is responsible for:

monitoring newly created clusters until they reach Running state
monitoring deleting clusters until they reach Deleted state
reacting to errors during cluster initialization, and potentially recreating the cluster

I tested with a local Leo by creating and deleting clusters, and it works as expected. See inline for code-specific comments.
Have you read CONTRIBUTING.md lately? If not, do that first.
I, the developer opening this PR, do solemnly pinky swear that:

[x] I've documented my API changes in Swagger

In all cases:

[ ] Get two thumbsworth of review and PO signoff if necessary
[ ] Verify all tests go green
[ ] Squash and merge; you can delete your branch after this
[ ] Test this change deployed correctly and works on dev environment after deployment

I think I've applied all PR comments so far, if people want to have another look..

@helgridly @jmthibault79 @ansingh7115 ready for re-review!

Done with this round of review.
Is this sequence possible, and therefore something we need to guard against?
Request Cluster deletion
-> calls Google delete
-> sets the DB entry to Deleting
-> starts monitor
...but then Google is slow to update its internal state

Monitor queries Google for cluster status.  result = Running
Monitor sets the DB entry to Running
Monitor stops

Thanks @jmthibault79. Good question. When I've deleted clusters the status update in Google has been very quick, but I agree that might be a race condition. Maybe the CMA could be aware of the cluster status in the DB, and therefore enforce certain status transitions (e.g. Deleting -> Deleted).

Applied latest PR feedback.

Looks great!  💯


Settings

How it works
Allow users to configure the message display, including:

[x] Toggle functionality
[x] Display duration (1 - 20s, default 10s)
[ ] Number of lines displayed (10 - 20, default 15)
[ ] Number of layers allowed (1 - 10, default 3)
[ ] Height of each lines

Auto adjusted
Fixed height (Ignore Number of lines displayed config)

[ ] Settings for different types of message

[x] Font color
[x] Font weight
[x] Font border width and color
[ ] Number of lines for super chat messages
[ ] Font family
[ ] Avatar display
[ ] is hidden

Where to show

[x] Shown as modal when click settings button inside the page (In player control / top of live chat)
[ ] Shown as small popup in browser toolbar
[ ] Option page

Notes

[x] Should save to local storage

@thwonghin Thank you so much for this extension.
The idea of making settings page sounds nice, but do you have any special reason for using storage.local instead of storage.sync? I'd love the settings to be synced across devices.

@thwonghin Thank you so much for this extension.
The idea of making settings page sounds nice, but do you have any special reason for using storage.local instead of storage.sync? I'd love the settings to be synced across devices.

@thwonghin Thank you so much for this extension.
The idea of making settings page sounds nice, but do you have any special reason for using storage.local instead of storage.sync? I'd love the settings to be synced across devices.

Thank you for the suggestion.
I don't remember any special reason for not using storage.sync. I will try to include it in next release.

@thwonghin Thank you so much for this extension.
The idea of making settings page sounds nice, but do you have any special reason for using storage.local instead of storage.sync? I'd love the settings to be synced across devices.

Thank you for the suggestion.
I don't remember any special reason for not using storage.sync. I will try to include it in next release.

@thwonghin
I just found out the settings are now synced. Thanks a lot for your work!

@thwonghin
I just found out the settings are now synced. Thanks a lot for your work!


Add Profile-Lookup-cyc

nice solutions but please review the instructions. can you make thef ollowing changes:

1 solution per branch
file names are algorithm-name_github_username.py


Set version v1.3.3

Fix push token exception

Pull Request Test Coverage Report for Build 394

34 of 36 (94.44%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 90.827%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

safe_notification_service/safe/views.py
15
17
88.24%

Totals

Change from base Build 391:
0.3%

Covered Lines:
1109

Relevant Lines:
1221

💛  - Coveralls


model_version not set in inference response unless it is set in request

Triton Version: 20.03.1-py3
API: gRPC
api-version: 2
It appears that the model_version does not appear in the inference response unless it is explicitly set in the request. Here is our response when we DO NOT explicitly set the inference version in the request:
model_name: "mnist"
outputs {
  name: "probabilities"
  datatype: "FP32"
  shape: 1
  shape: 10
  contents {
    raw_contents: "\325\261H7\224\331T;W\024g7\177\256\1778n\204~?u\20588\301\022+9.g\3178\217\265\023:\241\035\320:"
  }
}

And here is the inference response when we DO specify the version in the request:
model_name: "mnist"
model_version: "1"   <========
outputs {
  name: "probabilities"
  datatype: "FP32"
  shape: 1
  shape: 10
  contents {
    raw_contents: "\325\261H7\224\331T;W\024g7\177\256\1778n\204~?u\20588\301\022+9.g\3178\217\265\023:\241\035\320:"
  }
}

It's mainly when no version is specified in the request that we need to know the version actually used for analysis on the client side.

Please try with 20.06 version of Triton.

Verified fixed in 20.06.


Not building: no matching function for call to ‘entwine::Reader::query(...

Running into a compilation error on:

Ubuntu 16.04 64bit
PDAL 1.3.0 with lazperf
entwine build from master without errors in /usr/local/include/entwine/
latest greyhound pull from master

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/greyhound-server
> node-gyp rebuild

make: Entering directory '/usr/local/lib/node_modules/greyhound-server/build'
  CXX(target) Release/obj.target/session/src/session/bindings.o
  CXX(target) Release/obj.target/session/src/session/session.o
../src/session/session.cpp: In member function ‘std::shared_ptr<ReadQuery> Session::query(const entwine::Schema&, bool, double, const entwine::Point&, const entwine::Bounds*, std::size_t, std::size_t)’:
../src/session/session.cpp:203:31: error: no matching function for call to ‘entwine::Reader::query(const entwine::Schema&, const entwine::Bounds&, const size_t&, const size_t&, const double&, const entwine::Point&)’
                         offset)));

Oops, the Greyhound build was out of sync with Entwine's API.  I've merged #32, which syncs them, so please re-pull and try again.  A fresh docker image is currently being pushed (very slowly), and the npm package has been updated.
Can you also clarify - what was your build command to get this error?

Yes, works!
Build was just the npm install on the latest git master, I've attached the full output.
stacktrace_greyhound.txt


Project looks awesome

Hey, I was looking through this project and it's really solid.
I lead engineering at Fey and we're looking for engineers. Wondering if you'd be interested?
Regardless, awesome project. Thanks for maintaining it.

Thank you for the kind words. After taking a look at Fey, and seeing a lot of similarities with the things I already work on and interest me, I'd love to learn more.

Shoot me an email to<EMAIL_ADDRESS>I can tell you more about the role, our team, ambitions, tech stack.


Remove version: Tencent.QQMusic version 18.69

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: http://dldir1.qq.com/music/clntupate/QQMusic_Setup_1869.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 911)

URL: http://dldir1.qq.com/music/clntupate/QQMusic_Setup_1869.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 911)


Update all_to_all op interpreter to fix issue#2433

fixes: https://github.com/openxla/stablehlo/issues/2433
scattered_parts...@receiver = [split_parts...@sender[receiver_index] for sender in process_group] where receiver_index = process_group.index(receiver).

each sender/process from process_group contributes a split_part to the scattered_parts. This PR ensures the order of split_part in scattered_parts matches with the order of the sender/processes within the process_group.

LGTM, no need for approval from me on this one, other reviewers are enough


Fix the instructions that populate the CodeCommit repo

Issue #, if available:
Description of changes:
the instructions for populating the CodeCommit repo needed to be modified to align with the CodeCommit repo name. I set environment variables with the directory names of the GitHub repo and the CodeCommit repo, and modified the instructions that populate the CodeCommit repo to refer to them.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @iamahgoub I did a big refactor, but took your input about using variables here https://github.com/aws-samples/argocd-on-amazon-eks-workshop/pull/13


obtain estimated focal length from robust estimator pose/info

Hello!
Pretty much what the title said, how can i get the estimated focal length from a CameraPose struct when enabling https://arxiv.org/abs/2311.16304 ?
plus: is there a way to estimate focal length with a robust estimator for a single camera absolute pose with this library? Or the only viable solution atm is p4pf?
If it matters i'm on pybind
Thank you!

The CameraPose struct does not provide any information on focal lengths. If you have two images with 2d-2d correspondences and want to get focal lenghts you should

If you have two different cameras - run estimate_fundamental -> focals_from_fundamental_iterative for our method or focals_from_fundamental for the Bougnoux formula
If you have the same cameras you should use estimate_shared_focal_relative_pose

In case you have some 2d-3d correspondences then you should use the p4pf solver. You should check out the dev branch it is still in development, but you may find some code there for bundle adjustment for this problem using different cameras.


mull-cxx cannot found mutants

Description
How to reproduce:
$ git clone https://github.com/tarantool/tarantool
$ cd tarantool
$ git checkout gerold103/gh-5303-p4-raft-tests
$ mkdir build && cd build
$ cmake \
  -DCMAKE_CXX_FLAGS="-fembed-bitcode -g -O0" \
  -DCMAKE_BUILD_TYPE=Debug \
  -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \
  -DCMAKE_C_COMPILER="/usr/bin/clang" \
  -DCMAKE_CXX_COMPILER="/usr/bin/clang++" ..
$ make -j
$ mull-cxx -test-framework=CustomTest --reporters=Elements -compdb-path compile_commands.json -compilation-flags="-isystem /usr/local/include -isystem /usr/lib/llvm-10/lib/clang/10.0.0/include  -isystem /usr/include/x86_64-linux-gnu -isystem /usr/include"  -ld-search-path="/usr/lib/x86_64-linux-gnu/" ./test/unit/raft.test
[info] Extracting bitcode from executable (threads: 1)
       [################################] 1/1. Finished in 4ms
[info] Loading bitcode files (threads: 2)
       [################################] 2/2. Finished in 31ms
[info] Compiling instrumented code (threads: 2)
       [################################] 2/2. Finished in 10ms
[info] Loading dynamic libraries (threads: 1)
       [################################] 1/1. Finished in 1ms
[info] Searching tests (threads: 1)
       [################################] 1/1. Finished in 0ms
[info] No mutants found. Mutation score: infinitely high
[info] Total execution time: 77ms
$

sergeyb@pony:~/sources/MRG/tarantool/build$ mull-cxx --version
Mull: LLVM-based mutation testing
https://github.com/mull-project/mull
Version: 0.8.0
Commit: 84f2f4d
Date: 13 Oct 2020
LLVM: 10.0.0

Ubuntu Focal 20.04 x86_64

First of all, here is what happens: Mull tries to find test functions (which in the case of CustomTest is main) but it doesn't find anything. Because of that, it cannot run tests, cannot gather coverage info, and therefore cannot find any mutants.
I didn't double-check, but the hypothesis for why it happens is the following:
you only set -fembed-bitcode for the CXX flags, but not for C flags. Then, Clang compiles just fine, but the resulting bitcode only contains C++ parts of the code. As far as I can see the main is defined at test/unit/raft.c, which is not included in the resulting executable.
This CMake config should fix the issue:
cmake \
  -DCMAKE_CXX_FLAGS="-fembed-bitcode -g -O0" \
  -DCMAKE_BUILD_TYPE=Debug \
  -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \
  -DCMAKE_C_COMPILER="/usr/bin/clang" \
  -DCMAKE_CXX_COMPILER="/usr/bin/clang++" ..

@ligurio I would appreciate it if you can give it a try and let me know if that in fact fixes the issue.
From our side, I think the best we can do is to add a more helpful error/warning message indicating why mutants not found.

I just added a warning that should give a better hint #788

Thanks for a quick answer!

As far as I can see the main is defined at test/unit/raft.c, which is not included in the resulting executable.

it is not so, see in test/unit/CMakeLists.txt:
<snipped>
add_executable(raft.test raft.c raft_test_utils.c core_test_utils.c)
target_link_libraries(raft.test vclock unit fakesys raft_algo)
<snipped>

Looks like provided fix helps:
sergeyb@pony:~/sources/MRG/tarantool/build$ mull-cxx -test-framework=CustomTest --reporters=Elements -compdb-path compile_commands.json -compilation-flags="-isystem /usr/local/include -isystem /usr/lib/llvm-10/lib/clang/10.0.0/include  -isystem /usr/include/x86_64-linux-gnu -isystem /usr/include"  -ld-search-path="/usr/lib/x86_64-linux-gnu/" ./test/unit/raft.test
[info] Extracting bitcode from executable (threads: 1)
       [################################] 1/1. Finished in 23ms
[info] Loading bitcode files (threads: 8)
       [################################] 30/30. Finished in 53ms
[info] Compiling instrumented code (threads: 8)
       [################################] 30/30. Finished in 364ms
[info] Loading dynamic libraries (threads: 1)
       [################################] 1/1. Finished in 1ms
[info] Searching tests (threads: 1)
       [################################] 1/1. Finished in 0ms
[info] Preparing original test run (threads: 1)
[warning] JIT engine could not resolve the following symbols:
fstatat64
pthread_atfork
mknodat

       [################################] 1/1. Finished in 13ms
[info] Running original tests (threads: 1)
[warning] Original test failed
test: main
status: Crashed
stdout: ''
stderr: ''

       [################################] 1/1. Finished in 2518ms
[info] No mutants found. Mutation score: infinitely high
[info] Total execution time: 2987ms
sergeyb@pony:~/sources/MRG/tarantool/build$

Hi @ligurio, the last comment is related to JIT, which is not part of Mull anymore.
Please try the new version (0.9.0) and open another issue if you hit any other problems.


New feature: Storage

Adding thermal and battery storage models as discussed in #1.

Todo

[ ] Cleanup .gitignore (remove outdated items) @tommasomiori
[ ] Store README_storage.md content somewhere else and remove file @stroitzsch
[ ] Move , pricing_method='wholesale_market' to scenario definition @stroitzsch
[ ] Remove self.building_storage_types = pd.read_sql(... (Not needed?) @tommasomiori
[ ] Cleanup comments in set definitions @stroitzsch
[ ] Cleanup self.define_sensible_storage_level() @stroitzsch
[ ] Cleanup self.define_battery_storage_level() @stroitzsch
[ ] Cleanup self.define_output_storage_charge() @stroitzsch
[ ] Cleanup self.define_output_storage_discharge() @stroitzsch
[ ] Remove all latent storage code @tommasomiori
[ ] Cleanup self.define_output_hvac_ahu_electric_power() (Lots of commented code!) @tommasomiori
[ ] Cleanup self.define_output_hvac_tu_electric_power() (Lots of commented code!) @tommasomiori
[ ] Check if code considers possibility of only-AHU and only-TU in zones @stroitzsch
[ ] Cleanup define_output_constraint_timeseries() @stroitzsch

Questions

Whats is 'heating_cooling_session' / where is it used?
Is this still needed:  * (1 + 0.0000001)?

I'm almost done here @tommasomiori and will merge tomorrow. Let me know if you have any last comments!

Remaining issue for future reference: https://github.com/TUMCREATE-ESTL/cobmo/blob/b63fc69d3378ef30e4604e7ad065255cb09909fb/cobmo/controller.py#L197


use only cargo version and export it in version

Currently we have two versions: one in cargo.toml and one in pyproject.toml
We can do like in pydantic-core and use only cargo.toml one as source of truth and export it in a __version__ variable


update npm dependencies

merging to try fixing the failing unit test in https://github.com/abapGit/abapGit/pull/6380


Supported Methods: not accurate..

Shouldn't did:ethr be supported?
Can't we derive this https://github.com/decentralized-identity/universal-resolver-frontend/blob/master/src/components/App.jsx#L12-L31 list from the config ("see configuration") pattern?

At the moment our config for backend and frontend applications are not synced automatically. So it can happen that the API supports a did-method which is not listed in the frontend yet. We are aware of this and have automatic synchronization on our roadmap.


Patched sails-postgresql module to support  >= postgres12

This patch should solve following issues
#649
#646
#631
#487
#457

I added some changes to make it auto patched during  npm postinstall.

Is this ever going to get merged?

Is this ever going to get merged?

@pedrovsn
Ditto. I hope this gets merged soon.

I also hope this gets merged soon @pantsel . I have run into a problem with postgres 14 on konga.

Is there an ETA on merging this ?

please merge at least this PR

@vichaos : How do you set that up? I checked our your PR branch, build the container but still run into the issue.
git checkout add-support-to-postgres12-or-newer
docker build -t konga .

docker run -it \
    --network host \
    -e "NODE_ENV=development" \
    -e "TOKEN_SECRET=123456" \
    -e "HOST=<IP_ADDRESS>" \
    -e "PORT=1337" \
    -e "DB_ADAPTER=postgres" \
    -e "DB_HOST=$KONG_PG_HOST" \
    -e "DB_PORT=$KONG_PG_PORT" \
    -e "DB_USER=$KONG_PG_USER" \
    -e "DB_DATABASE=konga2" \
    -e "DB_PASSWORD=$KONG_PG_PASSWORD" \
    -e "KONGA_HOOK_TIMEOUT=120000" \
    --name konga \
    konga

error: A hook (`orm`) failed to load!
error: error: column r.consrc does not exist
    at Connection.parseE (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:539:11)
    at Connection.parseMessage (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:366:17)
    at Socket.<anonymous> (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:105:22)
    at Socket.emit (events.js:310:20)
    at Socket.EventEmitter.emit (domain.js:482:12)
    at addChunk (_stream_readable.js:286:12)
    at readableAddChunk (_stream_readable.js:268:9)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:186:23)
/app/node_modules/sails-postgresql/lib/adapter.js:158
        var collection = connectionObject.collections[table];
                                          ^

TypeError: Cannot read property 'collections' of undefined

@oborchers, Please take a look at the image I have provided on the first comment.
 Can I give you a coffee?

Hi, any update regarding the merge?

@vichaos Could you push the image in https://hub.docker.com/?

any update?

I build get this errors
/usr/local/lib/node_modules/patch-package/node_modules/yaml/dist/compose/composer.js:33
if (prelude[i + 1]?.[0] !== '#')
^
SyntaxError: Unexpected token '.'
at wrapSafe (internal/modules/cjs/loader.js:1047:16)
at Module._compile (internal/modules/cjs/loader.js:1097:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
at Module.load (internal/modules/cjs/loader.js:977:32)
at Function.Module._load (internal/modules/cjs/loader.js:877:14)
at Module.require (internal/modules/cjs/loader.js:1019:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object. (/usr/local/lib/node_modules/patch-package/node_modules/yaml/dist/index.js:3:16)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: bower --allow-root install && patch-package
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-07-27T07_09_26_624Z-debug.log

SCRAM is very important:

https://github.com/scram-sasl/info/issues/1

@thanhtai9606 I had to use an older version of patch-package
npm install -g<EMAIL_ADDRESS>


add example code for tasks in guide

Describe the feature
Current guide (https://nitro.unjs.io/guide/tasks) contains all info about task except an example of a task.
I would add something like this
// server/tasks/taskGroup/taskName.ts
export default defineTask({
  meta: {
    description: "Example task",
  },
  async run() {
    // add any custom task logic here and set result to return/log
    return result;
  },
});

Additional information

[X] Would you be willing to help implement this feature?

Where did you look? The documentation contains

:rofl:
OMG I read the whole thing like 5 times, and I did not noticed that...


Better NotAction Handling

I have a policy that includes a statement similar to this:
        {
            "Resource": [
                "arn:aws:lambda:us-west-2:012345678901:function:MyFunctionName*"
            ],
            "NotAction": [
                "lambda:Invoke*"
            ],
            "Effect": "Allow"
        }

This policy is intended to grant access to my CI/CD pipeline to make changes to the function, but not to execute the function. When evaluating this policy I get 10K plus lines of permissions, which are mostly inaccurate due to the resource restriction. Ideally the evaluation would identify the limited resource and only show permissions that can be included. I'd even consider it a huge improvement if it just limited the results by the service(s) of the resource arn(s).

Great suggestion @jasonwadsworth,
I'll have to do a bit of research on this as I suspect there may be unexpected inclusions under some circumstances. Will let you know.


Duplicate values in TlvTag

Description
For the TlvTag enum there are InteractionMode and WriteFileMode which both have a value of 0x23. I just want to reassure if that's correct.
There is also a duplicate CardIdManufacturerSignature which is not really an urgent issue but may be a nit to fix with next push.

Thanks for your carelessness. Technically, they are not errors. These are duplicates that need to be removed.

Thanks for your carelessness. Technically, they are not errors. These are duplicates that need to be removed.

Thanks for your quick answer :)
So it is correct, that InteractionMode and WriteFileMode both have the same value or should one have another, or should one be omitted?

Technically, they are not errors - both have the same value.
This will be fixed in the next release.

Fixed in https://github.com/tangem/tangem-sdk-android/pull/192


Module parse failed: Unexpected token on compile

Describe the bug
Compile error happening after using expect() in the storybook Play interaction. I tried changing versions of testing-library as well as adobe/css-tools but to no avail.
If I'm not using expect() everything is working fine.
To Reproduce
Steps to reproduce the behavior:

Install any @storybook/jest version with the below system setup
Create story and simple test using expect from@storybook/jest
Run storybook
See error
ERROR in<EMAIL_ADDRESS>96:23 Module parse failed: Unexpected token (96:23) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See  https://webpack.js.org/concepts#loaders

Expected behavior
Success compile
System
Please paste the results of npx storybook@latest info here.
Environment Info:

  System:
    OS: macOS 12.5.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 16.19.1 - ~/.nvm/versions/node/v16.19.1/bin/node
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.1/bin/npm
  Browsers:
    Chrome: 117.0.5938.92
    Safari: 15.6.1
  npmPackages:
    @storybook/addon-a11y: ^6.5.15 => 6.5.15
    @storybook/addon-actions: ^6.5.15 => 6.5.15
    @storybook/addon-essentials: ^6.5.15 => 6.5.15
    @storybook/addon-interactions: ^6.5.15 => 6.5.15
    @storybook/addon-links: ^6.5.15 => 6.5.15
    @storybook/builder-webpack4: ^6.5.15 => 6.5.15
    @storybook/jest: ^0.2.1 => 0.2.1
    @storybook/manager-webpack4: ^6.5.15 => 6.5.15
    @storybook/preset-scss: ^1.0.3 => 1.0.3
    @storybook/test-runner: ^0.9.4 => 0.9.4
    @storybook/testing-library: ^0.0.13 => 0.0.13
    @storybook/vue: ^6.5.15 => 6.5.15

Additional context

N/A

My guess is that webpack 4 does not support package.json 'exports' fields.  Do you know if it does?
If not, you'll need to use<EMAIL_ADDRESS>or upgrade to Storybook 7 / webpack 5 (though there's another issue with webpack and this package currently, that I need to investigate more).

Makes sense for the webpack 4 as it does not support it. I know they've added it to webpack 5.
I tried using<EMAIL_ADDRESS>but will hit additional errors then like:
ERROR in<EMAIL_ADDRESS>1:121012
Module parse failed: Unexpected token (1:121012)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

(Source code omitted for this binary file)
ERROR in ./node_modules/<EMAIL_ADDRESS>6:3158
Module parse failed: Unexpected token (6:3158)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { global } from '@storybook/global';
|
> var CallStates=(CallStates2=>...}
|
| export { CallStates, EVENTS, instrument };

ERROR in<EMAIL_ADDRESS>96:23
Module parse failed: Unexpected token (96:23)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|                 line: lineno,
|                 column: column
>             }, options?.source || "");
|             whitespace();
|             return node;

If not, you'll need to use<EMAIL_ADDRESS>or upgrade to Storybook 7 / webpack 5 (though there's another issue with webpack and this package currently, that I need to investigate more).

I'm happy to say that this is not the case anymore in version 0.2.3!
@borishuseincehajic are you stuck with Webpack 4 in your project? I'd highly suggest migrating to Webpack5, so you can take full advantage of Storybook 7, but also to keep your project up to date. I know things are not easy in certain projects, but I hope you can!

@borishuseincehajic I'm getting that exact error including the same line number and everything:
Module parse failed: Unexpected token (1:121012)
Were you able to fix it?

@elclanrs for me it was not the issue with that one but webpack not being able to handle certain imports properly. i found that one by someone from webpack repo in the end. My version of webpack is 4.6.x. Since I couldn't change the webpack version I decided to postpone these until I get the possibility to switch from wepback to vite

@elclanrs Did you ever solve this issue?

@IGCraig yes, we updated to the latest storybook and webpack.

@elclanrs sorry for the late reply but did the same as you in the end.

Hey everyone! In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. This issue should be solved or maybe it's not applicable anymore.
When upgrading to Storybook 8 with npx storybook@latest upgrade, you will get prompted and will get an automigration for the new package. Please migrate when you can! Thanks a lot <3


Convert Android's accelerometer and gravity sensors to use g unit

This PR addresses #355
It seems that it's more common to use the "g" unit for accelerometer data rather than Android's m/s².
However, if this PR is merged as is, even though there are no syntactical changes, the values coming from both Accelerometer and Gravity sensors would change for Android apps (eg. a value of 9.81 will, after this is merged, become 1). So maybe this is enough for a major bump?
Alternatively, we could add a flag to allow the user to choose between g unit and "platform default". The default value of that flag would be "platform default", therefore the change wouldn't be so significant. I'm glad to implement that flag in the same PR.
What's your opinion on it?

I'd rather have a second type since I want to expose the direct sensor values. But I can see that this normalized form makes more sense


Fix typos in documentation and filenames

Check List (Check all the applicable boxes)

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

Screenshots
(NA)
Note to reviewers
(NA)

Thanks for the typo fix.


Streams: Add checking for contract type in anyOf expression

This allows more stream results to be quickly rejected
Change-type: patch
Signed-off-by: Lucian Buzzo<EMAIL_ADDRESS>

@balena-ci rebase

@balena-ci I self-certify!


behat 3.0

The composer.json requires behat 2.5. Can behat 3.0 be used? If so can the composer file be updated?

No, the extension has not been migrated yet to Behat 3 (Behat 3 is a complete rewrite of Behat)


Calendar

First PR - just includes days Calendar.
Next pr's will include other modes and browsing.

Calendar is finished.
@hongaar @Stefanwullems
Im not so sure about the way i've implemented mode and initialMode - I quite like using enum types for the inner workings of swithces and so on but right now it means you have to use those as prop value as well (instead of just a string). What do you guys think and do you have any better ideas?


ENYO-5018: Implement PIG Component

Issue Resolved / Feature Added
Implement PIG(Picture in graphic) component for webOS TV only
Resolution
Some App support PIG function. Each App implement this.
Therefore, it is supported as component
Additional Considerations
Links
ENYO-5018
Comments

:tada: Great collaboration on this ticket. Thanks to @xbinary @viodragon2 and @Djspaceg! :tada:


I'm getting an error while trying to use httpVueLoader.langProcessor.scss
I used the README.md example

That sounds like you haven't registered 'scss' with the langProcessor attribute as described?
( the httpVueLoader.langProcessor.scss = function (scssText) { .. part of the example)

@FranckFreiburger Is there an actual example of this working somewhere? I haven't been able to get it working. The docs seem a little unclear.


Add client finished

Add client finish processing in client side.
On client side, after preparing client finish message, send to server side.

Makefile:18: recipe for target 'lib' failed
mingw32-make: *** [lib] Error 2
2021-11-11 08:37:14,700 - MinGW - INFO -
MingW build failed
1 configurations tested, 0 successful
script returned exit code 2"

This looks very much like the issue that has now been fixed (https://github.com/ARMmbed/mbedtls/issues/5146) - however this happened after this branch was created, hence head failing and Merge succeeding. I think this can be ignored.


clang-tidy: modernize-loop-convert

Description: Enable and fix existing cases of modernize-loop-convert. This clang-tidy check looks for raw for-loops that can be replaced with range-based loops.
https://clang.llvm.org/extra/clang-tidy/checks/modernize-loop-convert.html
There are a few configuration options for this check (see above link for more details) but I think the defaults are perfectly suitable.
Risk Level: Low
Testing: Existing
Docs Changes: N/A
Release Notes: N/A
[Optional Fixes #Issue]
[Optional Deprecated:]
Signed-off-by: Derek Argueta<EMAIL_ADDRESS>

/retest


escape-unknown-openstack-stuck-issue

Codecov Report

Merging #214 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #214      +/-   ##
=========================================
- Coverage   62.83%   62.8%   -0.04%
=========================================
  Files          43      43
  Lines        3326    3328       +2
  Branches      384     384
=========================================
  Hits         2090    2090
- Misses       1144    1146       +2
  Partials       92      92

Impacted Files
Coverage Δ

vmpool/clone.py
57.46% <0%> (-0.3%)
:arrow_down:

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 bbcecbc...3128a28. Read the comment docs.