docs: update repository and homepage url

Description
The repository url in the pubspec is broken. I updated it to the master channel of the flutterfire_ui package.

Related Issues
Didn't make an issue for this
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Good spot, thanks for sorting!


Update Adafactor reference on arXiv

gentle ping @mtthss 👍

Thanks for pointing this out! This was fixed by #172 so I am closing this PR.


Fix overlapping day timezones issue

Off peak periods which overlap a day may be hit with a timezone issue now the UK has moved from UTC to BST.

Fixed in #236


Wax integration

@pbinkley It was not and I am not sure why. I accidentally deleted that function when I shouldn't. I have pushed a fix and it should work now after you pull the branch.

I'm on f84f9a8 2021-09-08, which is the latest commit in wax-integration. I
think I must have been looking at an earlier commit, though, when I saw the
duration change - sorry about that. But the escaped json is happening with
the latest version.
On Thu, 9 Sept 2021 at 13:05, dnoneill @.***> wrote:

@.**** commented on this pull request.
In annonatate/flaskserver.py
https://github.com/dnoneill/annonatate-sourcecode/pull/3#discussion_r705619796
:

@@ -615,7 +606,7 @@ def getannotations():
if 'annotime' in session.keys():
now = datetime.now()
duration = (now - session['annotime']).total_seconds()

if 'annotations' not in session.keys() or session['annotations'] == '' or  duration > 35:

if 'annotations' not in session.keys() or session['annotations'] == '' or  duration > 0:

Are you running the most up to date version of this branch? The escaped
JSON is something I swear I fixed and the duration line I can't even find
in the both the code on GitHub or my local version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnoneill/annonatate-sourcecode/pull/3#discussion_r705619796,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCTMFCU3MRMYDYRF3HOY3UBEAODANCNFSM5B454DUQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@pbinkley Try it now. I think I found the problem.

I'm afraid the problem may have happened because of the kludge I introduced to distinguish manifest from stringmanifest - that could probably be refactored and simplified.
I created a new annotation on a different object, and the manifest is ok (not escaped), but it hasn't been changed after the creation of the annotation, so the annotation list isn't linked from the manifest.
From github.com:pbinkley/annonatate-wax
   c28fdea..51aaa3b  main       -> origin/main
Updating c28fdea..51aaa3b
Fast-forward
 .../05d24ba4-acd0-4168-a038-5d16952f9355.json      | 34 ++++++++++++++++++++++
 _annotations/obj12-00-list.json                    |  9 ++++++
 2 files changed, 43 insertions(+)
 create mode 100644 _annotations/05d24ba4-acd0-4168-a038-5d16952f9355.json
 create mode 100644 _annotations/obj12-00-list.json

@pbinkley I am not sure why it is not working for you. Maybe it has to do with the url? I forked your repo and tried it and was able to get it working with the fork. Under this line can you add response.content and tell me what it says?
        ```
        response = github.sendgithubrequest(session, manifestfilename, manifestwithlist)
        print(response.content)
        ```

I'm back on this now. I'm not seeing any output from the print statement but I'm investigating.

I haven't been able to trigger any output from the print statement. I understand better now how the annotations are being matched up to their manifests though. I'm wondering about the annoview template - it contains ruby-style symbols, and I'm not sure why it uses a new html tag  - shouldn't this be a json blob in a

I think this can be merged, and then some refactoring can happen separately. I haven't been able to break anything. I think an option to have it create a local copy of a remote manifest, with the annotations explicitly linked, would be worthwhile, so that my annotations become something I can easily open in a demo instance of Mirador etc. But that's new work.

@pbinkley It looks like the reason you haven't been able to trigger it is you are on your annonatate repo, not the annonatate-wax repo workspace.
The {{}} are how Jekyll handles variables in templating. The script tag is something I have built in Vue.js and is used here: https://ncsu-libraries.github.io/annona/tools/#/tag-builder/. I have taken that bundle and used it for the tag building in annonatate as well.
I agree on the ability to make a copy of an existing manifest. I have been thinking about adding that as an upload function. I will make sure to add it as an issue.

I'm sorry - you had to tell me once before about the workspace. I've tried again with the right workspace, and it updates as it should.
I think it would be good to add an indication of the current workspace at the top of the pages: e.g. "Saving to https://github.com/pbinkley/annonatate-wax", say, so it's clear what the workspace means.
The only thing I'm concerned about now is the placement of the annotations in the /annotations folder instead of with the other IIIF artefacts in img/derivatives/iiif/annotation or img/derivatives/iiif/<object id>. The structure of img is a little clumsy (it goes back to iiif_s3. But having all the iiif stuff in one folder would be convenient.

@pbinkley There should be a workspace indicator at the top of the page but if the browser is tool small it doesn't not show up. I am definitely thinking about how we could make that always showing because I think it is important. I am also working on a fix that when you log back in it will go back to the workspace you were previously working on. That is almost done.
I don't disagree but I haven't figured out a good way of structuring the annotations were they are also very easy to get without having to make a bunch of requests.
It looks like the annotation list is still not being populated on manifests in your wax version. Can you tell me what that print statement says?

@dnoneill I didn't get output from the print statement - here's my session: https://gist.github.com/pbinkley/6bf73ff822950970cc05a550140627d0 . If I render my annonatate-wax repo, I do have annotations/obj11-list.json containing my new annotation, as well as annotations/d1e13ca9-bf66-4e86-994c-f00ac4c1654a.json with the individual annotation. I'll compare with your annonatate-wax - I'm not sure what I'm supposed to see here.
btw in the community call just now there was some discussion of using Github for serving IIIF assets, and they're setting up a slack channel for further discussion.

@pbinkley It looks like something in the code is causing the writing of that list to the manifest to fail. If you could put some print statements in there and tell me where the problem is that would be great. I can't figure out why the annotation list is not updating in your manifest.

OK, I'll put in some diagnostics and see what I can find out. I've got an hour or so this afternoon, which hopefully will be enough.

Sounds good. Thanks.
On Wed, Sep 22, 2021 at 3:34 PM Peter Binkley @.***>
wrote:

OK, I'll put in some diagnostics and see what I can find out. I've got an
hour or so this afternoon, which hopefully will be enough.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnoneill/annonatate-sourcecode/pull/3#issuecomment-925261445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AESJEZ6PCW6LVA4X6NF3MKDUDIVS7ANCNFSM5B454DUQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Niqui O'Neill
Digital Technologies Development Librarian
NC State University Libraries
Office:<PHONE_NUMBER>
My pronouns are she, her, and hers

@dnoneill I've created a branch debug in my fork, which is caught up to your PR, and then added a bunch of diagnostics in createlistpage, and in addAnnotationList and in parseManifest in image.py````. The problem is that it fails to parse the manifest in the first tryinaddAnnotationList- it gets as far as runningManifestReader([here](https://github.com/pbinkley/annonatate-sourcecode/blob/713d86af7f1fd737012c4ce131842f1c82cc02e0/annonatate/utils/image.py#L118) and fails (which causes it to go on and try to parse it as API3). I'm not sure why: the manifest at that point is still the default Wax manifest https://pbinkley.github.io/annonatate-wax/img/derivatives/iiif/obj10/manifest.json , and it validates with the iiif.io validator (with a couple of warnings). I've commented out some [cleanup lines](https://github.com/pbinkley/annonatate-sourcecode/blob/713d86af7f1fd737012c4ce131842f1c82cc02e0/annonatate/utils/image.py#L84-L86) in order to get past this point but I haven't gotparseManifestto not throw it into theexcept```` stanza. I'll put some more time into this tomorrow.

@pbinkley I would change the except statement to except Exception as e: and print e. That might give you a better idea. Maybe prezi didn't get installed in your environment because I re forked your repo and it is working with my forked version, but it would be good to get to the bottom of this. Thanks for the work you have been doing.

Here's the exception:
('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'http://iiif.io/api/presentation/2/context.json', 'cause': TypeError('load_document_local() takes 1 positional argument but 2 were given')}

The CORS header is indeed set on http://iiif.io/api/presentation/2/context.json, and the json is valid. I'm not sure what to make of this. I ran pip install -r requirements.txt again, and it indicates that iiif-prezi has "Requirement already satisfied". I'll try a fresh installation into a venv and see if that makes a difference.

hm, it looks like I've got pyld 2.0.3, so that could be it. I'll try pinning it to 1.0.5 as suggested and see if that works.

It works! I'll go back and test it against the clean PR branch, without my commented out bits.

That works too. Are you ok with pinning the version of pypd in requirements.txt to 1.0.5, if there's no fix in iiif-prezi? (we also need to add python-dotenv to requirements.txt, as I found in doing a fresh install)

@pbinkley Added both to requirements.txt file

I've done fresh installation in venv, and everything works smoothly. I think this can be merged. I'll find the review I started and mark it as approved.

Will deploy this next week.


Swagger Parser doesn't handle relative file $refs in paths according to RFC3986

When traversing $refs to local files, Swagger Parser breaks at the first level of indirection due to not properly adjusting the base path of subsequent $refs. An example might better illustrate it, so let's take the following tree:
├─ openapi
│  ├─ entrypoint.yaml
│  └─ common-params.yaml
│
└─ module-1
   └─ openapi
      ├─ paths
      │  └─ path-1.yaml
      │
      └─ schemas
         └─ schema-1.yaml

We also have the following $refs:

Spec file
Has relative $ref to

openapi/entrypoint.yaml
../module-1/openapi/paths/path-1.yaml#/paths/~1path-1

module-1/openapi/path-1.yaml
../../../openapi/common-params.yaml#/components/parameters/param-1

../schemas/schema-1.yaml#/components/schemas/schema-1

Trying to parse this with the following snippet
var options = new ParseOptions();
options.setResolve(true);

var result = new OpenAPIParser().readLocation("openapi/entrypoint.yaml", null, options);

results in the error message below
Unable to load RELATIVE ref: ../../../openapi/common-params.yaml

I've done some investigation, it seems that once the parser resolves the $ref to ../module-1/openapi/paths/path-1.yaml#/paths/~1path-1, all of its contents are "dumped" to the result object being built, as if they came from the original entrypoint.yaml file. Local $refs within it are correctly updated to account for this change, but relative ones are not, meaning the parser will try to look for ../../../openapi/common-params.yaml starting from openapi/entrypoint.yaml. It could either look for ../../../openapi/common-params.yaml starting from module-1/openapi/paths/ or adjust the $ref to account for using the wrong base path.
I have a local patch in place that fixes this, but it could be a breaking change for anyone that's relying on Swagger Parser's wrong behavior, so I decided to bring it up for discussion before submitting a pull request.

 I would like to test it. I can't find it in your fork.

I have submitted PR#1557 which fixes this issue, the PR includes an additional testcase showing the problem
My fix doesn't seem to break any existing testcases.

It seems that this fix introduced a bug in the OpenAPI Generator.

This also breaks openapi-processor.
I have a test-case with $ref-chains (https://github.com/openapi-processor/openapi-processor-core/blob/master/src/testInt/resources/tests/ref-chain-spring-124.1/inputs/openapi.yaml) (just a link because it is a bit complicated to replicate here) that fails when updating from 2.0.28 to 2.0.29.
What I observe is that the names of the $referenced schemas in the components.schema map changed.
components.schema names with 2.0.28
User
UserPage
user-page
UserSearch
user-search
Pageable
page
user-content

components.schema names with 2.0.29
User
user.model.v1
UserPage
user-page.model.v1
UserSearch
user-search.model.v1
Pageable
pageable.model.v1

With 2.0.28 when the code is traversing the $refs, at some point it will get the $ref #/components/schemas/page which is available in components.schema, i.e. page after stripping the path.
With 2.0.29 it gets the $ref models/page.model.v1.yml instead and is unable to find it in components.schema.
This is probably the same issue why the OpenAPI Generator fails.


Unvoting error

When I unvote someone occasionally it says invalid time stamp. So I update internet time, go back to unvote again and it already unvoted.
So it seems like even though it displays the error message about timestamp it does process the unvote?

I'll try to replicate and screen shot it 🙂

The client is re-sending the unconfirmed txs. That's probably what's happening.

yes, this is what happens, if it did not get through it will automatically resend until got through
I will fix the issue at protocol level (ie on ark-node). Closing this


apply to DiscoArt?

Would be interesting to see it in action, some community member expects that
https://github.com/jina-ai/discoart/issues/162

Thank you for the insightful suggestion. I will try it.

Hi @hanxiao , I've add an example of stable-diffusion at: https://github.com/LuChengTHU/dpm-solver/tree/main/example_v2/stable-diffusion
I will further check the discoart.

Great! btw, are you interested in an intern/full-time position at Jina AI?
This is our company https://jina.ai/
On Fri, 28 Oct 2022 at 19:15, Cheng Lu @.***> wrote:

Hi @hanxiao https://github.com/hanxiao , I've add an example of
stable-diffusion at:
https://github.com/LuChengTHU/dpm-solver/tree/main/example_v2/stable-diffusion
I will further check the discoart.
—
Reply to this email directly, view it on GitHub
https://github.com/LuChengTHU/dpm-solver/issues/1#issuecomment-1295251740,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPSL2UN3SK4MBYHS22ZQ53WFQC4BANCNFSM56DSMWKA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
[image: photo]
Han Xiao
Founder & CEO, Jina AI
@.***
--
CONFIDENTIALITY NOTICE: This e-mail communication and any attachments
may
contain confidential and privileged information for the use of the
designated recipients named above. If you are not the intended recipient,
you
are hereby notified that you have received this communication in error
and that
any review, disclosure, dissemination, distribution or copying of
it or its contents
is strictly prohibited. If you have received this
communication in error, please
notify the sender by return e-mail and
delete and/or destroy all copies of this
communication and any attachments.


Use get_with_expr() instead of mine.get/saltutil.runner

Rationale
We use mine.get in many places just for getting etcd members, k8s masters and minions. However, this does not work in the Salt master, so we must use the saltutil.runner with different arguments for doing the same thing: getting some list of nodes...
So instead of using these two functions (and after some problems with argument in mine.get solved in #496), I think it woud be better to just use the (already present) get_with_expr everywhere (or some shortcuts) for getting nodes.
Changes

New get_etcd_members(), get_masters(), get_minions() for getting the etcd members, k8s masters and minions.
Use these shortcuts as well as get_with_expr() instead of using mine.get().

feature#cleanup

What's the status of this, should we close this PR?


Support Geo entities

The geo_postgis Postgrex extension allows entities from the geo library to be used as PostGIS data types.
It would be nice if the Ecto.DevLogger.PrintableParameter protocol supported that. Will see if I can add this easily.

@tcitworld were you able to figure this out?


Remove solutions from emitter tell() method

This should help simplify the API. Also, the optimizer will no longer need to keep track of the actual solutions.

On the contrary, having solutions may be useful in some cases. For instance, the emitter may deploy many solutions but only receive a few back. For now, I think it is okay to leave it to the optimizer to ensure solutions remain in the same order.


[#158967411] [WIP] add endpoint to retrieve all visibile services

adds an endpoint (controller method) to list all visbile services
adds visibile_service model
adds is_visible flag to services
adds a new function to compute the list of all visible services into a news cosmosdb collection (reacts to cosmosdb change feed -> updates / inserts from services colleoction)
incorporates some documentdb fixes from #311

WIP as it lacks tests but the logic is complete

Warnings

:warning:

Remember to fix the PR title by removing WIP wording when ready

Affected stories

🌟 #158967411: Come SAS voglio poter ottenere la lista completa dei services visibili

  Generated by :no_entry_sign: dangerJS


Move templates to RHEL/CentOS/UBI 8

Already tested in image-ecosystem:
https://github.com/openshift/cluster-samples-operator/pull/319

LGTM


fix: fix scheduled function template to use async

Summary
Without the async keyword, typescript instantly errors as the handler (according to the types
of schedule() ) needs to return a Promise.
I also tried deploying a function that is not async and lambda throws an error.

oof, nice catch! 👏🏻


Add support for Buffered CAN Frames

moves to add api to use TxTransfer objects instead of passing all the info through function arguments.
retains backward compatibility with existing apis albeit with bit more flash cost.

This is done to simplify additions/modifications to the options passed to transmit data.

@bugobliterator do we still want this?

@bugobliterator do we still want this?

Yes, I just need to find time to finish this. Having this will let us have lower RAM footprint.


update MutationGuidance to use filterMutants

as per our conversation.

As discussed in my review to #54, this design is necessarily making the class hierarchy of guidances quite complex. Each filter will need its own Guidance subclass and its own driver to construct the guidance instance. It will be impossible to compose filters.
A better design is to replace the OptimizedMutationGuidance interface with a MutantFilter interface (same method), and create filter instances within the single MutationGuidance class only and selectively filter the set of runMutants based on config parameters passed to the constructor of MutationGuidance. That way, we can easily compose and re-order filters.
If we make such a change, this this PR will mostly be obsolete. But, it is instructive to understand the challenges with design. So, thanks for crafting this!

Is this obsolete now? Should it be closed?


Issue810 GitHub io

Fixes #810 => adds structure for the github.io documentation page.

Checklist before merging:

[ ] Existing tests still work (check by running the test suite, e.g. from RStudio).
[ ] Added tests (if you added functionality) or fixed existing test (if you fixed a bug).
[ ] Updated or expanded the documentation.
[ ] Updated release notes in inst/NEWS.Rd with a user-readable summary. Please, include references to relevant issues or PR discussions.
[ ] Added your name to the contributors lists in the DESCRIPTION and CITATION.cff files.

Codecov Report

Merging #853 (84c22f2) into master (1fc3f21) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 84c22f2 differs from pull request most recent head 88f17d9. Consider uploading reports for the commit 88f17d9 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master     #853   +/-   ##
=======================================
  Coverage   73.68%   73.68%
=======================================
  Files          89       89
  Lines       11914    11914
=======================================
  Hits         8779     8779
  Misses       3135     3135


Added flow execution id to the jobSpecs compiled for a flowSpec

Added flow execution id to the jobSpecs compiled for a flowSpec and related test.

Pair reviewed with Hung. Merging in.


Avatar upload backend

Backend ticket split from #715

Verified in STG as working. user is able to upload images file type. also verified below issues when user try to upload invalid files, refer below image for error validation.


Update dependencies on pillow, factory-boy and django-widget-tweaks

Instead of forcing a version range for theses packages specificy only
the minimal version number. This packages are stable enough and forcing
upper version limits can cause issues with other (non oscar)
dependencies.

Personally I think the oscar releases are too infrequent. Documenting package numbers which are tested by us is imho a better method. I keep running into issues with other dependencies which require a newer version of for example factory boy.


Fix missing blue background on cert & profile buttons

The background style was moved to a separate style when loading indicators were added to discussion forums, but that style was not used in these other places.

@BenjiLee ? @1zaman ?

:+1:


Documentation of Kiwi.Geom.Intersect is incorrect.

lineSegmentToRectangle's method should be called "lineSegmentToRectangle" not "lineSegmentToCircle"

Resolved.


Syntax highlighting

Is it possible to enable the Unity syntax highlighting and the preprocessor directives?

Syntax highlighting should be in already, if the hints to the libraries are there.
Preprocessor directives is a request for the Visual Studio Code team, unfortunately, there isn't much I can do there.


Will this code compile?

struct Person: NSObject {
}

Will the code above compile?
If yes why?
If no why?

No because NSObject is a class and gives you objective c runtime. Structs cannot inherit because it's a value type not a reference type.

Great answer @tseringlamanyc. Also, keep in mind classes in Swift only support single inheritance.


Refactor controller_interface_ret_t and hardware_interface_ret_t usage

Should be merged after https://github.com/ros-controls/ros2_control/pull/114

Codecov Report

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

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
+ Coverage   33.12%   35.44%   +2.32%
==========================================
  Files          12       14       +2
  Lines        1123     1278     +155
  Branches      740      827      +87
==========================================
+ Hits          372      453      +81
+ Misses        103       86      -17
- Partials      648      739      +91

Flag
Coverage Δ

#unittests
35.44% <ø> (+2.32%)
:arrow_up:

Impacted Files
Coverage Δ

...include/joint_trajectory_controller/trajectory.hpp
42.85% <0.00%> (-23.81%)
:arrow_down:

...int_trajectory_controller/test/test_trajectory.cpp
24.71% <0.00%> (-1.66%)
:arrow_down:

...ers/joint_trajectory_controller/src/trajectory.cpp
54.11% <0.00%> (ø)

.../joint_state_controller/joint_state_controller.hpp
100.00% <0.00%> (ø)

...jectory_controller/joint_trajectory_controller.hpp
100.00% <0.00%> (ø)

...te_controller/test/test_joint_state_controller.hpp
100.00% <0.00%> (ø)

...te_controller/test/test_joint_state_controller.cpp
19.65% <0.00%> (ø)

...ory_controller/src/joint_trajectory_controller.cpp
42.47% <0.00%> (+0.78%)
:arrow_up:

...ory_controller/test/test_trajectory_controller.cpp
24.19% <0.00%> (+2.17%)
:arrow_up:

...ectory_controller/test/test_trajectory_actions.cpp
38.49% <0.00%> (+8.24%)
:arrow_up:

... and 1 more

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 d2e940a...230d185. Read the comment docs.


Instead of closing embedded Edge devtools on debug stop, return to previous Live Preview instance

Is your feature request related to a problem? Please describe.

Hi!
I use Live Preview to start a local server and then open Edge devtools inside of VSCode without debugging and connect to localhost:3000 for seeing changes to the HTML, console and so on, it works pretty well. However when I want to debug something and launch the project the non-debug Edge devtools is completely replaced by the debugging version and so when I stop debugging the Edge devtools browser and devtools page disappear.
This is a bit annoying and I think it would be smoother if there was an option for just returning Edge devtools to the Live Preview/Live Server page.
Describe the solution you'd like:

When stopping the debug session Edge devtools should go back to its previous state (attached to a server) instead of completely closing. Closing Edge devtools makes more sense when it is launched in a separate Edge window which isn't really attached to VS Code except for the debugging.
Describe alternatives you've considered:

Having debugging launch Edge in a separate window. For just debugging this kind of works but the Devtools stuff inside of VS Code is completely wasted since it is not connected to the debug session.
Having debugging launch with "--headless" and clicking the inspect button in the debug icons to open Devtools code. This seems like it would work because it doesn't close when you stop debugging but the browser page also completely stops working after debugging stops.

Additional context:

Maybe I'm missing something but I'm just looking for a way to have:

Edge devtools open when not debugging.
Edge devtools switch to a debugging state when starting debugging.
Edge devtools still open when stopping debugging.

Thanks for filing this. I'll make sure this shows up on the team's radar.


Terms definitions and data types, v01

The draft for the terms and data types:

the last version
the commits list to make review and add notes.
the version published at forth-standard.org

See also: comparison to some past proposals.
Rationale
Using of "data type" term
See also data type term in 2.1 Definitions of terms and 3.1 Data types
Lexical context
The same lexeme may have the different semantics in the different states for the system. For example, a lexeme can be resolved into the different words depending on the search order, or into the different numbers depending on the current BASE value. (This subject was also addressed in length in the message<EMAIL_ADDRESS>"Recognizers terminology" on 2020-06-26)
Translation
At the moment, to translate term is only used to simplify other definitions. Also, it much helps in discussions, when an actual operation (interpretation or compilation) does not matter.
Connection with POSTPONE
There is no need to mention a postpone action or something alike in token descriptor or token itself. Formally, POSTPONE just needs to know compilation semantics, and a token determines them.
Some choices consideration

Perhaps some term are superfluous, or  other terms missed. But the first question is correctness, and the second is reasonableness in linking a term and its meaning.

blank character or space character or white space?

Perhaps it's worth to use another term instead of "token". Perhaps the general "tuple" is enough.

Is it worth to use just "descriptor" instead of "token descriptor" ?

"default perceptor" or "initial perceptor"?

tuple of data objects or sequence of data objects? It seems, tuple is more abstract term, while sequence has some connotation to contiguity (or the same logical location of the items) and to less limited length.

A successful result of a single call to find is not a token in the general case (according to the current definition), since on some systems this result might determine either interpretation semantics or compilation semantics depending on the STATE value at the time of the call. Is it acceptable?  If we allow a such result to be a token, an ambiguous condition will exist on translating this token in some cases. See also my FIND clarification proposal.
OTOH if we will not provide a way to translate a token, this nuance does not matter.

"Dynamic context" is too wide (too pervasive) notion in Forth, and too close to "dynamic scope" notion.
Let's use "lexical context" term to denote the part of the system state the recognizers depends on.
(all mentions have been updated)


增加异常日志

增加异常日志-对于由于驱动加载与JAVA版本问题导致的Error无法看到任何日志，导致不好排查问题

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


[HUDI-813] Migrate hudi-utilities tests to JUnit 5

Migrate the test cases in hudi-utilities to JUnit 5.
Follows #1570
Migration status (after merging)

Package
JUnit 5 lib
API migration
Restructure packages

hudi-cli
✅
✅
-

hudi-client
✅
✅
-

hudi-common
✅
🚧
🚧

hudi-hadoop-mr
✅
✅
-

hudi-hive-sync
✅
✅
-

hudi-integ-test
✅
✅
N.A.

hudi-spark
✅
✅
-

hudi-timeline-service
✅
✅
-

hudi-utilities
✅
✅
-

Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1589   +/-   ##
=========================================
  Coverage     71.82%   71.82%
  Complexity      294      294
=========================================
  Files           385      385
  Lines         16549    16549
  Branches       1661     1661
=========================================
  Hits          11886    11886
  Misses         3931     3931
  Partials        732      732

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 506447f...d71d318. Read the comment docs.


Feature: Page Tree REST API

Some use the page tree hierarchy for menu structure, so that the site menu, for example, can be built automagically from the page tree as sometimes it is easier for editors if page tree and main menu are tightly connected.
Alternative Use Case that doesn't require knowledge of the page tree: By creating a custom Plugin called let's say "CustomMenuNodePlugin", hierarchical menus can be built in a djangocms-aliases Alias and from there exposed via the REST API.

The page tree is available including structure. We need an additional endpoint for the menu of a page.

@sourcery-ai plan


Perms not working for jobs

Sponge Version:  1.12.2-2768-7.1.6-RC3616
Forge Version:   2811
Total Economy Version:  1.8.1
Description of issue
Unable to get the job option to work while using luckperms
Tried to add various commands with little success.
Adding - totaleconomy.command.job allows /job command to be used but it still says no permission when clicking on the roles.
Console errors
No permission to click role.
/job unavailable unless totaleconomy.command.job is used.
Steps to reproduce
Related Configuration Files
Create a Gist (https://gist.github.com/) for each configuration file related to this issue
https://gist.github.com/Millificent/d4db5bf2062920b289fcf3589d92a7b4
https://gist.github.com/Millificent/b98f23823aa31673c2d6f744636bba45

Did you check https://github.com/Erigitic/TotalEconomy/wiki/Command-Permissions and set your permissions up accordingly?

Hey Mark,
I’ve tried all the perms I’ve trief the total command and all various separate ones and no matter what a job cannot be picked.
I’d rather use the branches of perms than the wildcard.
I can attack a git of luckperms if it helps?

If you have the implicit wildcard enabled in Luckperms, granting a user  totaleconomy.command.job will allow that user access to every job command (Related issue #205 ). Including totaleconomy.command.job.setother and .reload.
It is very likely you do not want that.
When the implicit wildcard is disabled, a user must be granted totaleconomy.command.job to be allowed to use "/job" at all and totaleconomy.command.job.set in order to be able to set their own job.
In addition, when the configured job requirements in the jobs configuration requires users to have a specified permission, that permission must also be granted in order for a user to be able to select that job.

So the job does not have any specified permission and luck perms has each of the above commands in
https://imgur.com/a/GUm5z4K

https://imgur.com/a/f7jALNy

Can you attach your jobs configuration using a gist.

https://gist.github.com/Millificent/f75a45c2bea705ee5d2b17a145f9a070

Remove the permission requirements from your config and try again.
Permission requirements are evaluated based on a null check and your configuration uses an empty string (which is not the same as null)

You are the hero...honestly 3 of us have played around with this for like a week solid

Glad to have helped 👍
Feel free to close the issue if you don't have any related questions.

@Erigitic //dangling resolved issue :wink:

@MarkL4YG Thanks


chore: Add app viewer related codeowners

Pull Request Template

PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

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 not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Folks, Please do run the build on this once before merging, we want to be sure nothing is breaking because of syntax or otherwise!

Sure @somangshu . But this file is not included in the build. So this should not affect anything.

/ok-to-test

/ok-to-test


[VS Code] RPC connection closed.

@carlosal1015 Thanks for raising the issue.  This is likely a duplicate of #299, #373, or #363. Let's continue the conversation there.  #299 and #373 have a proposed workaround if you are on Debian.
It would be great if you'd attach your logs to one of these issues.  Use the "Live Share: Export Logs" command in Visual Studio Code and drag-and-drop the logs into a comment in one of the issues.  Thanks again!


Central Prometheus to query 2 different k8s clusters

Hey Prometheus Operators,
Quick question: Is there a recommended way to use 1 central Prometheus to aggregate and query the metrics normally found by querying 2 different Prometheus instances in 2 different Kubernetes clusters in 2 different data centers?
If there is, I would love to get some tips on the best way to go about this.
Thank you!

This is generally a question that is worth asking the larger Prometheus community, as it's not really specific to the Prometheus Operator. (https://groups.google.com/forum/#!forum/prometheus-users)
If not absolutely necessary I would actually just keep the instances apart, and just make each of them send their alerts to a single, organization wide Alertmanager cluster. This also still allows you to create dashboards with multiple datasources, one per cluster.
If you absolutely need all data from all Prometheus servers in one, then federation is the answer. If possible I try to stay away from federation though, as it makes the setup often more complex where it doesn't need to be.

Thanks, @brancz!

Closing this here, but let me know if there is anything else :slightly_smiling_face: .


Don't use/verify Cinder capabilities if no backend

Cinder volume and backup should have supported storage backends
configured in order to use and verify volumes/snapshots with a
test VM that we start before adoption.
When the volume backend is not supported, do not attach volumes
and do not create snapshots for the test/bfv VMs.
When the backup backend is not supported, do not create volumes
backups.
Neither verify, if those are still present post-adoption.
Depends-on: https://review.rdoproject.org/r/c/rdo-jobs/+/55084

oops, this needs more testing
TASK [development_environment : pre-launch test VM instance] *******************
fatal: [localhost]: FAILED! => {"msg": "template error while templating string: Could not load \"lowercase\": 'lowercase'. String: {{ shell_header }}\nexport OPENSTACK_COMMAND=\"{{ openstack_command }}\"\nexport CINDER_BACKEND_CONFIGURED=\"{{ cinder_backend_configured | string | lowercase }}\"\n{{ lookup('ansible.builtin.file', prelaunch_test_instance_script) }}\n. Could not load \"lowercase\": 'lowercase'"}

Note, must merge dowstream PR as well, before merging this one!

Not sure why, the tasks wasn't triggered again
TASK [dataplane_adoption : Verify that the volumes and snapshots have correct name, status and size] ***
skipping: [localhost] => {"changed": false, "false_condition": "cinder_volume_backend in supported_volume_backends",
"skip_reason": "Conditional result was False"}

TASK [dataplane_adoption : verify the backup of disk volume] *******************
skipping: [localhost] => {"changed": false, "false_condition": "cinder_backup_backend in supported_backup_backends",
"skip_reason": "Conditional result was False"}

See https://logserver.rdoproject.org/58/658/b54eeb9032adb1c3b7e10cd678544ea94a4eccc4/github-check/adoption-standalone-to-crc-ceph/57b21a4/controller/data-plane-adoption-tests-repo/data-plane-adoption/tests/logs/test_with_ceph_out_2024-10-17T11:24:33EDT.log

recheck

recheck

recheck after https://github.com/openstack-k8s-operators/install_yamls/pull/937 done

The ceph standalone config looks correct https://logserver.rdoproject.org/58/658/b54eeb9032adb1c3b7e10cd678544ea94a4eccc4/github-check/adoption-standalone-to-crc-ceph/bed673c/controller/data-plane-adoption-tests-repo/data_plane_adoption/vars.yaml
So does the deployemnt https://logserver.rdoproject.org/58/658/b54eeb9032adb1c3b7e10cd678544ea94a4eccc4/github-check/adoption-standalone-to-crc-ceph/bed673c/controller/data-plane-adoption-tests-repo/data-plane-adoption/tests/logs/test_with_ceph_out_2024-10-24T09:09:05EDT.log
TASK [dataplane_adoption : Verify that the volumes and snapshots have correct name, status and size] ***
changed: [localhost] => {"attempts": 1, "changed": true, "cmd": "alias openstack=\"oc exec -t openstackclient -- openstack\"

${BASH_ALIASES[openstack]} volume list -c Name -c Status -c Size -f value | grep \"disk in-use 1\"
${BASH_ALIASES[openstack]} volume list -c Name -c Status -c Size -f value | grep \"boot-volume in-use 1\"
${BASH_ALIASES[openstack]} volume snapshot list -c Name -c Status -c Size -f value | grep \"snapshot available 1\"
",
"delta": "0:00:09.402921",
"end": "2024-10-24 10:37:25.909397",
"rc": 0, "start": "2024-10-24 10:37:16.506476",
"stdout": "disk in-use 1
boot-volume in-use 1
snapshot available 1",
"stdout_lines": ["disk in-use 1",
"boot-volume in-use 1",
"snapshot available 1"]}

TASK [dataplane_adoption : verify the backup of disk volume] *******************
changed: [localhost] => {"attempts": 1, "changed": true, "cmd": "alias openstack=\"oc exec -t openstackclient -- openstack\"

@fmount @jistr this one is good to go!

Thanks @bogdando for the work on this.
The changes looks good and the job results verify the expected behavior.
LGTM.

https://review.rdoproject.org/r/c/rdo-jobs/+/55084 was forgotten, needs a fast merge

Included in https://github.com/openstack-k8s-operators/data-plane-adoption/pull/709


fix: refactor process.exit to exception

Description

refactor process.exit to exception

Related Issue
Fixes #

Relates to #
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[ ] Test, docs, adr added or updated as needed
[ ] Contributor Guide Steps followed

Hi @naveensrinivasan, Something really funky is going on.
There is an startup function that is being invoke when you import validateHash from the controller.ts based on how controller is implemented.
I suggest moving validateHash to helpers like in #707 and changing the package.json back. You can use that PR (#707)  as your reference and we can close it afterwards.

addressed in https://github.com/defenseunicorns/pepr/pull/707 I wanted to test something and did not want to pollute your PR. It was passing locally but not in CI. Thank you for the contribution


Cursor Environment Variable is not toggling

When using the CURSOR environment variable is set to false or true the cursor is still showing on the screen.
It seems that the xserver's  xinitrc is not loaded correctly.

Hi @gardlt , I wasn't able to reproduce that (by changing env vars in the compose file). How are you setting environment variables right now?
I made a branch that changes the xinitrc script to add a bash shebang line, maybe the script wasn't correctly converting the variable check into a string? Why don't you go ahead and try it out to tell me if you see a difference: https://github.com/balenablocks/xserver/tree/cursor-variable-toggle

I try to deploy these changes and the cursor is still showing.
We are currently running
balenaOS : balenaOS 2.83.18+rev1
Release: Production
I found a workaround that does work, by updating the entry.sh

@ngmartins the CURSOR variable is set in the Dockerfile as the default option, it will be overridden if set anywhere else

I am unable to reproduce this issue at all still. Setting CURSOR in the docker-compose.yml, on balena dashboard device or fleet variables all have the same result.
For anyone seeing this, it's important to make sure you have all capitol CURSOR as the environment name, and no quotes around true or false values.


run with dependent cells not running dependent cells

Testing #14550

interesting bug, precedent works but dependent doesn't. @amunger the execution counts are 60+, does it fail from the very beginning or only after some repeated execution of these cells.

does not repro consistently


Fix/avx512

In fact this is not finished yet I sent the PR just to see it worked outside of avx512 and there are still some mistakes
I am on it
But all features added are tested in the cpp files


first pass at implementing a base class decoupled from the "Trigger" …

First pass at implementing a base class decoupled from the "Trigger" system context

Figured it might be easier to code something up then try to reason about it in the abstract.
I think this could become the new base class which could be used for dependency inject + other potential built in functionality (like injecting recursion strategies).
From a DX perspective, the only real change is that you need to reference context.newRecords vs trigger.new, etc.
@ralphcallaway when you have a second maybe add me to the repo so I don't have to deal with keeping a fork in sync.


Add german data

Sorry, wrong repository.

I'd love a german random generator if you would like to add it as a separate generator!


[dif/i2c] autogen i2c IRQ DIFs and integrate into src tree

This partially addresses #8142, specifically, the item: "Integrate auto-generated IRQ DIFs into (existing) IP DIFs and deprecate manually implemented IRQ DIFs" --> "i2c".

PR dependency removed. Ready for review.


Specify scheduler in DataFrame assert_eq

Support passing scheduler= to dask.dataframe.utils.assert_eq. By default, assert_eq continues to use the sync scheduler, but this allows specific tests to override that as necessary.
Split out from https://github.com/dask/dask/pull/8392.

[x] Tests added / passed
[x] Passes pre-commit run --all-files

Thanks @gjoseph92! cc @rjzamora who I recall wanted something like this previously


Issue: it's been a while since last stable release

Description
Can another official release be cut? Last release says Dec. 2022. I check the roadmap/breaking changes pinned issues, but those seemed out of date and maybe not-relevant anymore? There's been breaking changes that aren't listed there, and it the issue was closed also. The change in name of 'help' to 'vimdoc' is causing issues over at lazyvim repo and kickstart repo as well, many which could probably be worked around with a better understanding of their config but I digress. What are the blockers for a release?
Neovim version
NVIM Head
Nvim-lspconfig version
No response
Operating system and version
macOS 12.15
Affected language servers
help
Steps to reproduce
Copy default kickstart.nvim template and boot it.
Actual behavior
you get error about no found 'help' server
Expected behavior
Flawless install of kickstart.nvim :)
Minimal config
https://github.com/nvim-lua/kickstart.nvim/blob/master/init.lua

LSP log
not relevant

I am thoroughly confused. Was this meant for the nvim-treesitter repo?

Actually, why open an issue to kickstart.nvim instead?

I think I've confused myself as well, on second read. Closing!


Support arbitrary html comments

One of the main benefits of using pure text formats is ability to use a good text editor. One of the useful features of a good text editor is ability to fold and unfold boring parts of text. For example in vim anything between special tags  {{{ and }}} can be folded into a single line. In most languages you'd use it along with comment specific to that language, in Rust it would be // {{{ and // }}}.
Markdown uses HTML comments and vim automatically inserts them as <!-- {{{ --> and <!-- }}} -->. Sadly this makes presenterm very unhappy...
What I want is to be able to have text like this and presenterm behaving as if comments are not there
thread 'main' has overflowed its stack<!--{{{-->
fatal runtime error: stack overflow<!--}}}-->

Thanks for the report! This is now fixed in master. I'm curious how you got a stack overflow, I couldn't reproduce that.
I did make the change so any comment that contains nothing but a {{{ or }}} (after trimming!) is now ignored. Because comments can contain presenterm commands I need some rule on how to determine they could be commands (and fail if they're bogus). So for now every HTML comment is a presenterm command unless it's a multi-line comment or one of {{{ or }}}.

I'm curious how you got a stack overflow, I couldn't reproduce that.

Stack overflow is just a sample text I used as an example unrelated to your crate :)
Thanks for a quick fix!

lol okay you said "Sadly this makes presenterm very unhappy" so a stack overflow seemed in line. Sweet!

Nah, I was referring to an error message. Btw, this makes it say that there's an error on line 1 column 2. In my file it's line 500+...
<!-- end_slide 1-->

lol nice one. I'll fix this one tomorrow!


Orchestrating S3 Glacier Deep Archive object retrieval using Step Functions

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
By submitting this pull request, I agree to be bound by the Flex Your Skills Terms and Conditions.

@dmahapatro this looks like a CDK based project not a SAM based one. I think this should be in a /cdk sub-directory, no?

@JustinCallison Moved the app under /cdk.


RAYLIB_PATH for templates are incorrect.

I just pulled master as of today Feb 18, 2018 and noticed a problem with the RAYLIB_PATH in each of the MakeFile for the templates. The don’t compile as is on raspberry pi.
Its currently:
RAYLIB_PATH = ..\..

Changed to the following and compilation works.
RAYLIB_PATH = ../..

Thanks @ismyhc for detecting this issue. Reviewed in commit https://github.com/raysan5/raylib/commit/7e32a627e88035c21cd16daddca128a9b6024de9

A question that's really about RAYLIB_RELEASE_PATH. How do you feel about getting the full path with something like:
RAYLIB_PREFIX ?= ../..
RAYLIB_PATH    ?= $( realpath $(RAYLIB_PREFIX)) ?

realpath may be specific to GNU make, which is fine on Linux. I think it's gmake on BSD.
Anyway, I'm using a form of that successfully on my fork. Having the fully qualified path would allow ldconfig to prepare RAYLIB_RELEASE_PATH for run-time linking to the freshly built libraylib.so staged in $(RAYLIB_PATH)/release/libs/linux. It's not really necessary since folks should be make installing anyway. I don't know what other effects it might have. Thanks.


merge branch feature/fpgadcfg to master

Coverage increased (+0.2%) to 81.022% when pulling 3a1688d936f94fe9eb11d502e13941c2a61dbca2 on tswhison/fpgad_merge into 1be4c7623391b606ac654f48e8312f81059b2898 on master.

The pluginmgr_c_p.dummy_plugin test fails on hw. May want to mock only?

Could you copy/paste the failing message?  I'll try to debug it.  skx-p?

/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:461: Failure
Expected: matches
Which is: 105
To be equal to: 99
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:470: Failure
Expected: fpgaReset(handles[i])
Which is: 0
To be equal to: FPGA_NOT_SUPPORTED
Which is: 6
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:472: Failure
Expected: (err.find(err_contains)) != (std::string::npos), actual:<PHONE_NUMBER>3709551615 vs<PHONE_NUMBER>3709551615
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:470: Failure
Expected: fpgaReset(handles[i])
Which is: 1
To be equal to: FPGA_NOT_SUPPORTED
Which is: 6
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:472: Failure
Expected: (err.find(err_contains)) != (std::string::npos), actual:<PHONE_NUMBER>3709551615 vs<PHONE_NUMBER>3709551615
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:468: Failure
Expected: fpgaOpen(t, &handles[i], i)
Which is: 1
To be equal to: FPGA_OK
Which is: 0
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:470: Failure
Expected: fpgaReset(handles[i])
Which is: 1
To be equal to: FPGA_NOT_SUPPORTED
Which is: 6
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:472: Failure
Expected: (err.find(err_contains)) != (std::string::npos), actual:<PHONE_NUMBER>3709551615 vs<PHONE_NUMBER>3709551615
api-shell.c:187:fpgaClose() ERROR : wrapped_handle is NULL
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:473: Failure
Expected: fpgaClose(handles[i++])
Which is: 1
To be equal to: FPGA_OK
Which is: 0
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:468: Failure
Expected: fpgaOpen(t, &handles[i], i)
Which is: 1
To be equal to: FPGA_OK
Which is: 0
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:470: Failure
Expected: fpgaReset(handles[i])
Which is: 1
To be equal to: FPGA_NOT_SUPPORTED
Which is: 6
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:472: Failure
Expected: (err.find(err_contains)) != (std::string::npos), actual:<PHONE_NUMBER>3709551615 vs<PHONE_NUMBER>3709551615
api-shell.c:187:fpgaClose() ERROR : wrapped_handle is NULL
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:473: Failure
Expected: fpgaClose(handles[i++])
Which is: 1
To be equal to: FPGA_OK
Which is: 0
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:468: Failure
Expected: fpgaOpen(t, &handles[i], i)
Which is: 1
To be equal to: FPGA_OK
Which is: 0
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:470: Failure
Expected: fpgaReset(handles[i])
Which is: 1
To be equal to: FPGA_NOT_SUPPORTED
Which is: 6
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:472: Failure
Expected: (err.find(err_contains)) != (std::string::npos), actual:<PHONE_NUMBER>3709551615 vs<PHONE_NUMBER>3709551615
api-shell.c:187:fpgaClose() ERROR : wrapped_handle is NULL
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:473: Failure
Expected: fpgaClose(handles[i++])
Which is: 1
To be equal to: FPGA_OK
Which is: 0
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:468: Failure
Expected: fpgaOpen(t, &handles[i], i)
Which is: 1
To be equal to: FPGA_OK
Which is: 0
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:470: Failure
Expected: fpgaReset(handles[i])
Which is: 1
To be equal to: FPGA_NOT_SUPPORTED
Which is: 6
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:472: Failure
Expected: (err.find(err_contains)) != (std::string::npos), actual:<PHONE_NUMBER>3709551615 vs<PHONE_NUMBER>3709551615
api-shell.c:187:fpgaClose() ERROR : wrapped_handle is NULL
/home/lab/workspace/jelonanx/opae-sdk/testing/opae-c/test_pluginmgr_c.cpp:473: Failure
Expected: fpgaClose(handles[i++])
Which is: 1
To be equal to: FPGA_OK
Which is: 0
[  FAILED  ] pluginmgr_c_p.dummy_plugin (9 ms)
[----------] 1 test from pluginmgr_c_p (9 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (9 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] pluginmgr_c_p.dummy_plugin
I ran it on 37.

@jelonanX, Thanks for the data.  It seems to also fail on master.  Let's not gate this pull based on that.  Will talk to @r-rojo about it tomorrow.


Sift.get() returns null if the app UI hasn't been launched yet

My app has a boot listener so that we can fetch the state of the world from our server and stop/re-start Geofences as needed.  Because of the way the documentation says to initialize Sift, none of my Activity listener stuff has fired yet, because there's no UI yet.  But my User listener fires, and that means I call Sift.get().userId = foo.  Unfortunately this means the app crashes because Sift.get() is null.
What should I do here?  With the way you guys have structured things, it's pretty clear that the Sift lifecycle is supposed to mirror the Activity lifecycle, but that means out-of-band things like this have nowhere to go.

At the very least, Sift.get() should be marked @Nullable

@edenman we've market Sift.get() as nullable and will make a release sometime this week.

Done


Is there any possibility to have route for pop-up?

I'm using TabPage for the whole application and need some tabs to open pop-ups. Is it possible to have such routes or maybe simply add routeless points with custom onTap to tab list?
I've found https://github.com/tomgilder/routemaster/wiki/Path-hierarchy this, but seems it's not gonna work

You can do it with DialogRoute.
Here is an example code.
Maybe this example should on the docs. 😄
late final signOutStateRouteMap = RouteMap(
  onUnknownRoute: (_) => const Redirect('/'),
    routes: {
      '/home/my_dialog': (_) {
         return const MyDialogPage();
      },
   }
);

class MyDialogPage extends Page<void> {
  const MyDialogPage({super.key});

  @override
  String get name => 'my_dialog';

  @override
  Route<void> createRoute(BuildContext context) {
    return DialogRoute(
      context: context,
      barrierDismissible: false,
      builder: (context) => const MyDialog(),
      settings: this,
    );
  }
}

It works, thank you!


Move this repository under Microsoft Docs

Thank you for publishing this great set of Azure Databricks best practices. For the sake of this content's discoverability and consistency with other documentation, wouldn't it be better to move this repository under the official Azure Databricks docs?

Hi Syed, the docs team clarified that they want product documentation in the docs website and have a strict format and requirements and takes some time to publish. Where as this is a deployment guide based on real world strategic customer engagements that we need to update quite often.

@swan-am-i Thanks for clarifying. Is it possible for the docs team to link this repository from the Azure Databricks docs for discoverability?


Previously working _error queue now reporting 312-NO_ROUTE

Contact Details
No response
Version
8.x
On which operating system(s) are you experiencing the issue?
Windows
Using which broker(s) did you encounter the issue?
RabbitMQ
What are the steps required to reproduce the issue?
Not attempted

What is the expected behavior?
Error messages should move to the _error queue
What actually happened?
So I have a windows service used for sending emails and any exceptions thrown in the consumer, (so in my case the email could not be sent), masstransit normally moves the email to the error queue.
This has been working fine for 2 or 3 years now but all of a sudden I am getting 312-NO_ROUTE which is causing the consumer to trigger and try again putting it into a loop.
I haven't changed any configuration or anything apart from adding Quartz and Delayed Redelivery but I removed all of this code and it still does not work, a bit of a head scratcher for me.
Included log with exceptions.
Related log output, including any exceptions
[2024-02-23 10:46:30.494 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - MassTransit.) - {} - Configured endpoint Email, Consumer: EmailService.EmailConsumer
[2024-02-23 10:46:30.522 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - MassTransit.) - {} - Configured endpoint DESKTOP-99KLG9M-DirectEmail, Consumer: EmailService.DirectEmailConsumer
[2024-02-23 10:46:30.692 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.Transports.BusDepot.) - {} - Starting bus instances: IBus
[2024-02-23 10:46:30.697 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Starting bus: rabbitmq://f324e86/
[2024-02-23 10:46:30.720 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Email manager running
[2024-02-23 10:46:30.730 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Subscribing....
[2024-02-23 10:46:30.753 3ee6c40a-8814-42d2-ab9a-47a98ada38db WRN] (   DESKTOP-99KLG9M - MassTransit.) - {} - Start called, but the host was already started: rabbitmq://f324e86/ (Already Started)
[2024-02-23 10:46:30.765 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Connect: ServiceApp@F324E86(:):5672/
[2024-02-23 10:46:30.768 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Returning next host: F324E86:5672
[2024-02-23 10:46:30.964 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Connected: ServiceApp@F324E86(:):5672/ (address: amqp://F324E86:5672, local: 58576)
[2024-02-23 10:46:31.015 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Endpoint Ready: rabbitmq://f324e86/DESKTOP99KLG9M_EmailService_bus_ky1yyygxmpry6gkpbdqdezftge?temporary=true
[2024-02-23 10:46:31.042 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Declare queue: name: DESKTOP-99KLG9M-DirectEmail, durable, consumer-count: 0 message-count: 6
[2024-02-23 10:46:31.042 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Declare queue: name: Email, durable, x-queue-type: quorum, consumer-count: 1 message-count: 0
[2024-02-23 10:46:31.064 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Declare exchange: name: DESKTOP-99KLG9M-DirectEmail, type: direct, durable
[2024-02-23 10:46:31.064 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Declare exchange: name: Email, type: fanout, durable
[2024-02-23 10:46:31.070 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Declare exchange: name: Logwood.MessageBus.Email:StandardEmail, type: fanout, durable
[2024-02-23 10:46:31.070 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Declare exchange: name: Logwood.MessageBus.Email:DirectEmail, type: fanout, durable
[2024-02-23 10:46:31.092 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Bind queue: source: DESKTOP-99KLG9M-DirectEmail, destination: DESKTOP-99KLG9M-DirectEmail
[2024-02-23 10:46:31.092 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Bind queue: source: Email, destination: Email
[2024-02-23 10:46:31.143 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Bind exchange: source: Logwood.MessageBus.Email:DirectEmail, destination: DESKTOP-99KLG9M-DirectEmail
[2024-02-23 10:46:31.143 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Bind exchange: source: Logwood.MessageBus.Email:StandardEmail, destination: Email
[2024-02-23 10:46:31.209 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Consumer Ok: rabbitmq://f324e86/DESKTOP-99KLG9M-DirectEmail?type=direct - amq.ctag-vwsqO6wnF-Zby9Q9QAQ7-Q
[2024-02-23 10:46:31.210 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Consumer Ok: rabbitmq://f324e86/Email - amq.ctag-vqJVdNSW0hcT_nA6b3PNjA
[2024-02-23 10:46:31.211 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Endpoint Ready: rabbitmq://f324e86/DESKTOP-99KLG9M-DirectEmail?type=direct
[2024-02-23 10:46:31.211 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - Endpoint Ready: rabbitmq://f324e86/Email
[2024-02-23 10:46:31.216 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - MassTransit.) - {} - Bus started: rabbitmq://f324e86/
[2024-02-23 10:46:31.216 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - MassTransit.) - {} - Bus started: rabbitmq://f324e86/
[2024-02-23 10:46:31.217 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Ready for messages.
[2024-02-23 10:46:31.227 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - .) - {} - No files to clear.
[2024-02-23 10:46:31.410 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 INF] (   DESKTOP-99KLG9M - .) - {} - Direct email consumer running
[2024-02-23 10:46:31.412 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 DBG] (   DESKTOP-99KLG9M - .) - {} - Adding job to list
[2024-02-23 10:46:31.413 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 DBG] (   DESKTOP-99KLG9M - .) - {} - Waiting for job to finish
[2024-02-23 10:46:31.734 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Processing job
[2024-02-23 10:46:31.737 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Processing email attachment.
[2024-02-23 10:46:31.739 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Email has attachments.
[2024-02-23 10:46:31.740 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Getting attachment: "D:\Temp\Services\KS Reporting Service\EmailAttachments\Late Items By Volume_2024_02_20_638440381576104504.html"
[2024-02-23 10:46:31.745 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {Attempt=1} - Sending Email
[2024-02-23 10:46:32.340 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Requested action not taken: mailbox unavailable
invalid DNS MX or A/AAAA resource record
[2024-02-23 10:46:32.341 3ee6c40a-8814-42d2-ab9a-47a98ada38db ERR] (   DESKTOP-99KLG9M - .) - {ExceptionDetail={["Type"]="System.Exception", ["HResult"]=-2146233088, ["Message"]="Sending Email Failed", ["Source"]=null, ["InnerException"]={["Type"]="System.Exception", ["HResult"]=-2146233088, ["Message"]="Requested action not taken: mailbox unavailable\ninvalid DNS MX or A/AAAA resource record", ["Source"]=null}}} - Error sending email
System.Exception: Sending Email Failed
 ---> System.Exception: Requested action not taken: mailbox unavailable
invalid DNS MX or A/AAAA resource record
   --- End of inner exception stack trace ---
[2024-02-23 10:46:32.350 3ee6c40a-8814-42d2-ab9a-47a98ada38db INF] (   DESKTOP-99KLG9M - .) - {} - Job finished
[2024-02-23 10:46:36.349 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Declare exchange: name: MassTransit:Fault--Logwood.MessageBus.Email:DirectEmail--, type: fanout, durable
[2024-02-23 10:46:36.351 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Declare exchange: name: MassTransit:Fault, type: fanout, durable
[2024-02-23 10:46:36.371 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Bind exchange: source: MassTransit:Fault--Logwood.MessageBus.Email:DirectEmail--, destination: MassTransit:Fault
[2024-02-23 10:46:36.490 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 DBG] (   DESKTOP-99KLG9M - MassTransit.Messages.) - {} - SEND rabbitmq://f324e86/MassTransit:Fault--Logwood.MessageBus.Email:DirectEmail-- 50240000-cf5b-480f-0720-08dc345cb54c MassTransit.Fault<Logwood.MessageBus.Email.DirectEmail>
[2024-02-23 10:46:36.500 7e00b73d-b21a-48e9-b0d2-88c3c0ea77f5 ERR] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {ExceptionDetail={["Type"]="System.Exception", ["HResult"]=-2146233088, ["Message"]="Sending Email Failed", ["Source"]="EmailService", ["TargetSite"]="Void MoveNext()", ["InnerException"]={["Type"]="System.Exception", ["HResult"]=-2146233088, ["Message"]="Requested action not taken: mailbox unavailable\ninvalid DNS MX or A/AAAA resource record", ["Source"]=null}}} - R-FAULT rabbitmq://f324e86/DESKTOP-99KLG9M-DirectEmail?type=direct 04360000-4c7f-509a-bbba-08dc3224fa2f Logwood.MessageBus.Email.DirectEmail EmailService.DirectEmailConsumer(00:00:04.8302923)
System.Exception: Sending Email Failed
 ---> System.Exception: Requested action not taken: mailbox unavailable
invalid DNS MX or A/AAAA resource record
   --- End of inner exception stack trace ---
   at EmailService.DirectEmailConsumer.Consume(ConsumeContext`1 context) in D:\Git Repositories\Current\Services\Email Service\EmailService\DirectEmailConsumer.cs:line 61
   at MassTransit.DependencyInjection.ScopeConsumerFactory`1.Send[TMessage](ConsumeContext`1 context, IPipe`1 next) in /_/src/MassTransit/DependencyInjection/DependencyInjection/ScopeConsumerFactory.cs:line 22
   at MassTransit.DependencyInjection.ScopeConsumerFactory`1.Send[TMessage](ConsumeContext`1 context, IPipe`1 next) in /_/src/MassTransit/DependencyInjection/DependencyInjection/ScopeConsumerFactory.cs:line 22
   at MassTransit.Middleware.ConsumerMessageFilter`2.MassTransit.IFilter<MassTransit.ConsumeContext<TMessage>>.Send(ConsumeContext`1 context, IPipe`1 next) in /_/src/MassTransit/Middleware/ConsumerMessageFilter.cs:line 48
[2024-02-23 10:46:36.526 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Declare queue: name: DESKTOP-99KLG9M-DirectEmail_error, durable, consumer-count: 0 message-count: 0
[2024-02-23 10:46:36.543 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Declare exchange: name: DESKTOP-99KLG9M-DirectEmail_error, type: direct, durable
[2024-02-23 10:46:36.555 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {} - Bind queue: source: DESKTOP-99KLG9M-DirectEmail_error, destination: DESKTOP-99KLG9M-DirectEmail_error
[2024-02-23 10:46:36.605 3ee6c40a-8814-42d2-ab9a-47a98ada38db DBG] (   DESKTOP-99KLG9M - MassTransit.) - {} - BasicReturn: 312-NO_ROUTE 04360000-4c7f-509a-bbba-08dc3224fa2f
[2024-02-23 10:46:36.626 9394d691-36b8-47ea-b200-dea94d722b37 INF] (   DESKTOP-99KLG9M - .) - {} - Direct email consumer running
[2024-02-23 10:46:36.627 9394d691-36b8-47ea-b200-dea94d722b37 DBG] (   DESKTOP-99KLG9M - .) - {} - Adding job to list
[2024-02-23 10:46:36.627 9394d691-36b8-47ea-b200-dea94d722b37 DBG] (   DESKTOP-99KLG9M - .) - {} - Waiting for job to finish
[2024-02-23 10:46:36.620 3ee6c40a-8814-42d2-ab9a-47a98ada38db ERR] (   DESKTOP-99KLG9M - MassTransit.ReceiveTransport.) - {ExceptionDetail={["HResult"]=-2146233088, ["Message"]="exchange:DESKTOP-99KLG9M-DirectEmail_error => The message was returned by RabbitMQ: 312-NO_ROUTE", ["Source"]="System.Private.CoreLib", ["TargetSite"]="Void Throw()", ["Uri"]="exchange:DESKTOP-99KLG9M-DirectEmail_error", ["Type"]="MassTransit.MessageReturnedException"}} - T-FAULT rabbitmq://f324e86/DESKTOP-99KLG9M-DirectEmail?type=direct 04360000-4c7f-509a-bbba-08dc3224fa2f
MassTransit.MessageReturnedException: exchange:DESKTOP-99KLG9M-DirectEmail_error => The message was returned by RabbitMQ: 312-NO_ROUTE
   at MassTransit.Util.ChannelExecutor.<>c__DisplayClass11_0.<<Run>g__RunMethod|0>d.MoveNext() in /_/src/MassTransit/Util/ChannelExecutor.cs:line 114
--- End of stack trace from previous location ---
   at MassTransit.Util.ChannelExecutor.Future`1.Run() in /_/src/MassTransit/Util/ChannelExecutor.cs:line 237
   at MassTransit.Util.ChannelExecutor.Run[T](Func`1 method, CancellationToken cancellationToken) in /_/src/MassTransit/Util/ChannelExecutor.cs:line 128
   at MassTransit.Internals.TaskExtensions.<>c__DisplayClass1_0.<<OrCanceled>g__WaitAsync|0>d.MoveNext() in /_/src/MassTransit.Abstractions/Internals/Extensions/TaskExtensions.cs:line 40
--- End of stack trace from previous location ---
   at MassTransit.Internals.TaskExtensions.<>c__DisplayClass1_0.<<OrCanceled>g__WaitAsync|0>d.MoveNext() in /_/src/MassTransit.Abstractions/Internals/Extensions/TaskExtensions.cs:line 40
--- End of stack trace from previous location ---
   at MassTransit.Util.PendingTaskCollection.Completed(CancellationToken cancellationToken) in /_/src/MassTransit.Abstractions/Util/PendingTaskCollection.cs:line 63
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 67
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168

Link to repository that demonstrates/reproduces the issue
No response

This is not an issue with MassTransit. If you need help, you can go through Commercial Support.


Issue with i386

The lame.framework is not working in simulators using Xcode 12. The following error occurs:
The linked and embedded framework 'lame.framework' is missing one or more architectures required by this target: i386.
Any help?

Hi @rafagan, could you provide project example? Thanks.

Just create an empty project and try to run in iOS simulator with the framework set
On 16 Nov 2020 14:22 -0300, Andrey<EMAIL_ADDRESS>wrote:

Hi @rafagan, could you provide project example? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi @rafagan, Example project is updated, check it.


Add test to NPM scripts

This might be a dumb idea because you do everything via Makefile.
However I haven't found Makefiles to be common in NPM ecosystem so I'd suggest adding at least support for “blessed” npm test (it even has its own command!) just to point people like me to look at the Makefile.

I had considered this the other day :thumbsup:


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_95ee9613-b4b5-4805-bb6e-befeb7b34e88/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_95ee9613-b4b5-4805-bb6e-befeb7b34e88.git

Docs Build status updates of commit e69504e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-11-07-16-03-15 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-11-07-16-03-15

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.


Sending arbitrary files by command

What would you like to see added?
For some workflows (like testing resonances, or logging stuff to a file) it may be useful to be able to attach a file, video or a picture.
This should be a MESSAGE_RESPOND type command, which in turn has a path parameter and errors out, if the file attached is too big. Path validation is done by the user.

Commands examples:
RESPOND PREFIX=tg_send_image MSG="path='../imgs/nosignal.png' message='asd message' "
RESPOND PREFIX=tg_send_video MSG="path='../imgs/nosignal.png' message='asd message' "
RESPOND PREFIX=tg_send_document MSG="path='../imgs/nosignal.png' message='asd message' "

path parameteris required, message is optional

Sending a file which is too large should result in the same error as happens with timelapse, otherwise very nice

Extended syntax added for sending image albums\file groups. Example
RESPOND PREFIX=tg_send_image MSG="path=['../imgs/nosignal.png', '../imgs/nopreview.png', '../imgs/nosignal.png'] message='lala message' "
RESPOND PREFIX=tg_send_video MSG="path=['../imgs/nosignal.png', '../imgs/nopreview.png', '../imgs/nosignal.png'] message='lala message' "
RESPOND PREFIX=tg_send_document MSG="path=['../imgs/nosignal.png', '../imgs/nopreview.png', '../imgs/nosignal.png'] message='lala message' "

the old syntax is still available
RESPOND PREFIX=tg_send_image MSG="path='../imgs/nosignal.png' message='asd message' "
RESPOND PREFIX=tg_send_video MSG="path='../imgs/nosignal.png' message='asd message' "
RESPOND PREFIX=tg_send_document MSG="path='../imgs/nosignal.png' message='asd message' "

Synthax is not conforming with #191, needs to be unified.


Algorithm passed to Hash is only used if algorithm key is provided before hash key

Bug Report

Q
A

Version(s)
2.x

Summary
The order of option keys determines whether the given algorithm is used.
Current behavior
If the algorithm key is passed after the hash key, the algorithm is silently set to crc32 (default).
How to reproduce
// works
new Hash(['algorithm' => 'sha1', 'hash' => 'foo']);
// fails
new Hash(['hash' => 'foo', 'algorithm' => 'sha1']);

Expected behavior
Order of keys in options array is irrelevant.

FWIW, it's gonna be a while before adoption of validator 3.0 gets any traction, so a fix for this in 2.x will get merged and released if you can provide it 👍


Restructure tagpage

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after), along with a short summary of changes:
Issue
Fixes #62
Please Note:
This changes cannot be reflected in feature branch(https://restructure-tagpage--sunstar--sunstar-global.hlx.live), please refer to Adobe github for confirmation https://github.com/hlxsites/sunstar/pull/576
Test URLs:

Original: https://www.sunstar.com/healthy-thinking/tag?feed-tags=education
Before: https://main--sunstar--sunstar-global.hlx.live/healthy-thinking/tag?feed-tags=education
After: https://restructure-tagpage--sunstar--sunstar-global.hlx.live/healthy-thinking/tag/germany

Hello @JiangLong2019 I can't access the after link:

Hi @ehrro, Yes, this ticket requires updating fstab.yaml, fstab.yaml only works on main branch. This is why that feature branch URL doesn't work, it should work after we merge it. For now, I did the complete same change on Adobe github, could you please check the following URL?
https://issue575--sunstar--hlxsites.hlx.live/healthy-thinking/tag/education

Thanks @ehrro, merged.


ghc-mod doesn't build with haskell-ng.packages.ghc7101

On commit
commit 3d60f6401fe698262dfb636c506cc635b1c340dc
Author: Charles Strahan<EMAIL_ADDRESS>Date:   Fri Apr 3 18:54:18 2015 -0400

    haskell: fix GHC version check for GHCJS

I get
[17 of 38] Compiling Language.Haskell.GhcMod.Cradle ( Language/Haskell/GhcMod/Cradle.hs, dist/build/Language/Haskell/GhcMod/Cradle.o )
builder for ‘/nix/store/arwx2pjnhwzqjsgqgb816k044y3ygd00-haskell-ghc-mod-<IP_ADDRESS>.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/ba4q8zmi0x4wikhxz78j2b7mqffpn4fp-ghc-7.10.1.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/ba4q8zmi0x4wikhxz78j2b7mqffpn4fp-ghc-7.10.1.drv’ failed
/home/miguel/.nix-profile/bin/nix-shell: failed to build all dependencies

Here's the relevant issue from upstream: https://github.com/kazu-yamamoto/ghc-mod/issues/437

Apparently, the issue has been fixed upstream and will be shipped in the next version.