add Bloxroute sdk

📝 Summary
Use Bloxroute SDK to listen to new pending transactions from the Bloxroute data feed
⛱ Motivation and Context
Separate Bloxroute and Eden into two components, with this PR.
📚 References

✅ I have run these commands

[x] make lint
[x] make test
[x] go mod tidy

@metachris Please take a look

thanks! will get to it soon

thanks, but not needed anymore, current bloxroute connection was contributed by bloxroute team and works well

@metachris why? BloxRoute created an SDK repository that exposes the API to other services. You still need to manage their logic and it will be broken in the future?
Haha, I don't think it is a good rule for open source repositories but this repository is from you. So thanks

The current bloXroute node connector is written and maintained by the bloXroute team, and it's good for them to have ownership. Feel free to talk to them about changing the implementation.
Nevertheless, thanks for the effort 🙌


[Question] RCTWebView _webView instance var

I'm currently looking at extending RCTWebView to inject an executor styled after RCTWebViewExecutor. Is there any particular reason why the RCTWebView's instance of UIWebView is an instance variable instead of a property?
Would you guys accept a PR that changes _webView to a property from an instance var so that devs like myself who want to extend RCTWebView can have access to the UIWebView instance?
@implementation RCTWebView
{
  RCTEventDispatcher *_eventDispatcher;
  UIWebView *_webView;
}

My Goal is to use WebView to render song patterns where react native seems to have trouble (reference: https://www.youtube.com/watch?v=l1YnS9p0hJE)

Bump?
I ended up copying  a lot of code to make this happen.
Please correct me if i'm wrong: Seems like I'm not the only person who is running into this.  The React Native core library seems to limit extensibility by virtue of the code patterns leveraged in its development. :(
https://github.com/facebook/react-native/issues/1908

@jaygarcia - I can't see any reason why such a PR would not be accepted, worth submitting!

^--- Thank you. =D

I don't see any problem with exposing this property. The reason we didn't is simply that I/we consider it good practice to make properties private by default, and ivars carry less runtime overhead than properties, so again, we use ivars by default unless there's a good reason to expose the functionality.
FWI, Objective-C is incredibly flexible, so you can access the private ivars of a class you are subclassing by using [self valueForKey:@"ivarName"], but this is obviously quite kludgy, so if there's a legit reason to expose the property, go ahead and file a PR :-)


No dokan.dll

There's only dokan1.dll after I installed dokany.
Every step I tried to dokan-sshfs raised some crashes - It's too hard to just run it.

dokan-sshfs is only compatible with dokan 0.8.0 for now.
Please remove dokan 1.0.0 that you installed and install 0.8.0

Okay.

Is dokany 0.8.0 supported?

No it is not, dokan-sshfs is not maintained :cry:


license problem (IRIS, Docker) - TESTS!!

Error: Invalid Community Edition license, may have exceeded core limit. - Shutting down the system : $zu(56,2)= 0Starting IRIS
https://github.com/intersystems-community/DeepSeeWeb/actions/runs/3674512494/jobs/6212816395

Every year the issue like that occurs.
In the irishealth-community:2<IP_ADDRESS>.3-zpm image the license is outdated.
Everyone who use this image should switch to use next version of IRIS.

Lets use say "2<IP_ADDRESS>8.0-zpm" version.
Seems to be good.

Solution https://github.com/intersystems-community/DeepSeeWeb/pull/307


change upgrade path to 4.14 (from 4.13) and intensify check

Description
Change upgrade path for image store table
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Test Output:
Before migrate:
MariaDB [cloud]> select * from volume_store_ref\G
*************************** 1. row ***************************
                  id: 8
            store_id: 2
           volume_id: 3
             zone_id: 0
             created: 2020-09-17 10:49:23
        last_updated: NULL
              job_id: NULL
        download_pct: 0
                size: 52428800
       physical_size: 0
      download_state: NULL
            checksum: NULL
           error_str: NULL
          local_path: NULL
        install_path: volumes/2/3/365df8ed-b414-4311-af46-82043ee056af.qcow2
                 url: NULL
        download_url: NULL
               state: Ready
...
*************************** 5. row ***************************
                  id: 22
            store_id: 2
         template_id: 202
             created: 2020-09-17 10:49:26
        last_updated: NULL
              job_id: NULL
        download_pct: 100
                size: 52428800
          store_role: Image
       physical_size: 43646976
      download_state: DOWNLOADED
           error_str: NULL
          local_path: NULL
        install_path: template/tmpl/2/202/6c3ec8aa-77fb-3cac-a74e-70f715361895.qcow2
                 url: NULL
               state: Ready
....
MariaDB [cloud]> select * from snapshot_store_ref\G
************************** 2. row ***************************
                id: 8
          store_id: 2
       snapshot_id: 1
           created: 2020-09-17 10:49:23
      last_updated: NULL
            job_id: NULL
        store_role: Image
              size: 52428800
     physical_size: 43646976
parent_snapshot_id: 0
      install_path: snapshots/2/3/1fae4aa3-270e-490a-9592-3fc3cc40b35a
             state: Ready
      update_count: 2
           ref_cnt: 0
           updated: 2020-09-17 10:49:29
         volume_id: 3

After migration:
MariaDB [cloud]> select * from volume_store_ref\G
*************************** 1. row ***************************
                  id: 9
            store_id: 1
           volume_id: 3
             zone_id: 0
             created: 2020-09-17 10:53:44
        last_updated: NULL
              job_id: NULL
        download_pct: 0
                size: 52428800
       physical_size: 0
      download_state: NULL
            checksum: NULL
           error_str: NULL
          local_path: NULL
        install_path: volumes/2/3/365df8ed-b414-4311-af46-82043ee056af.qcow2
                 url: NULL
        download_url: NULL
               state: Ready

MariaDB [cloud]> select * from template_store_ref\G
*************************** 6. row ***************************
                  id: 25
            store_id: 1
         template_id: 202
             created: 2020-09-17 10:53:51
        last_updated: NULL
              job_id: NULL
        download_pct: 100
                size: 52428800
          store_role: Image
       physical_size: 43646976
      download_state: DOWNLOADED
           error_str: NULL
          local_path: NULL
        install_path: template/tmpl/2/202/6c3ec8aa-77fb-3cac-a74e-70f715361895.qcow2
                 url: NULL
               state: Ready

MariaDB [cloud]> select * from snapshot_store_ref\G
*************************** 2. row ***************************
                id: 9
          store_id: 1
       snapshot_id: 1
           created: 2020-09-17 10:53:44
      last_updated: NULL
            job_id: NULL
        store_role: Image
              size: 52428800
     physical_size: 43646976
parent_snapshot_id: 0
      install_path: snapshots/2/3/1fae4aa3-270e-490a-9592-3fc3cc40b35a
             state: Ready
      update_count: 2
           ref_cnt: 0
           updated: 2020-09-17 10:53:51
         volume_id: 3

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian.  I'll keep you posted as I make progress.

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian.  The tests finished at backend


fix minor it's -> its grammar typo in docs/faq.org

Saw a simple it's to its typo in faq.org that needed fixing.

Hi! Thanks for the PR but I cannot accept it. See reason here: https://github.com/hlissner/doom-emacs/pull/4184#issuecomment-719898404


Error: nil pointer evaluating resource.Resource.Permalink - when the resource is valid

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.89.4-AB01BA6E+extended linux/amd64 BuildDate=2021-11-17T08:24:09Z VendorInfo=gohugoio

Does this issue reproduce with the latest release?
Yes
I have a page bundle, with an image file, profile.jpg, in the page's images subdirectory.  A page template
with this code reports an error (as if the file was not found).
{{ $image := .Resources.GetMatch "images/profile.*" }}
{{ $image.Permalink }}
----
Error: Error building site: failed to render pages: render of "page" failed: execute of template failed: template: testimonials/single.html:11:9: executing "main" at <partial "testimonial" .>: error calling partial: "/home/mckoss/src/ra-website/themes/ra-theme/layouts/partials/testimonial.html:7:9": execute of template failed: template: partials/testimonial.html:7:9: executing "partials/testimonial.html" at <$image.Permalink>: nil pointer evaluating resource.Resource.Permalink

BUT, change the code to this:
{{ $image := .Resources.GetMatch "images/profile.*" }}
{{ with $image }}
    {{ $image.Permalink }}
{{ end }}

Produces NO ERROR - and outputs the permalink just fine (I was originally trying to .Resize this Page resource) - but this test case produces the same result.
I also confirmed in the non-with case that $image is not itself nil:
{{ printf "%#v: ---> %v" $image $image }}
---
&resources.resourceAdapter{commonResource:resources.commonResource{}, resourceTransformations:(*resources.resourceTransformations)(0xc00045f0c0), resourceAdapterInner:(*resources.resourceAdapterInner)(0xc0004defa0)}: ---> images/profile.jpg

So, it seems that the {{ with }} statement (while I agree is better coding practice) - has the side-effect of validating the resource reference.
EXPECT: In the case of a found resource, to be able to reference it's properties and methods WITHOUT having to first
test if the result of GetMatch is non-nil.

Unable to reproduce.
I suspect that one or more of the pages rendered with this code does not have the resource that the code is looking for.
In the future, please use the forum (https://discourse.gohugo.io) for questions and troubleshooting. We prefer to use GitHub for verified bugs and vetted enhancements. Thanks.

@jmooring is right; these things are kind of hard to reason about when we do things in parallel and you have 1000s of something.

If you'd like to see a reproducible case - I created this repro for you.
https://github.com/mckoss/hugo-bug-repro


Some hyperHTML advice

First off: pretty awesome stuff !!!
One thing hard to grasp about hyperHTML though, is the convention to distinguish between HTML and sanitized/raw text content.
For instance, in your test you wrote:
render`<h1>${this.foo}</h1><input value="${this.bar()}" />`;

indicating you want to enable html, nodes, fragments, or arrays, within that h1 tag.
However, the test checks for textContent, so that I am assuming that you really want to be sure no HTML goes into that tag.
render`<h1> ${this.foo} </h1><input value="${this.bar()}" />`;

Can you spot the difference?
While famous  templates have the {{maybe-text}} vs {{{maybe-HTML}}} convention, hyperHTML, and same goes for viperHTML, consider special everything between > and < .
Put just one extra char around that, and it's ensured to be threated as textContent, boosting performance even more, simplifying parsing and also sanitizing automatically through the native DOM.
Recap

This is handled as text <h1> ${this.foo} </h1>
This is handled as html <h1>${this.foo}</h1> or even as an array of nodes, or just a node, everything but "just text"

About the rest of the test component, I love the idea of "starting fresh" but I don't see real-world value, rather a duplicated template.
This, of course, gives you the ability to produce completely different layouts for a single component, but is that actually a good, desired, design goal?
In these cases I would probably do something smarter like creating two wires and swap them instead of trashing the previous layout, but it also covers different needs/scenarios so ... I'd like to udnerstand more about this trashing case, thanks.

About the render method, it looks good but this specific line is not optimal:
template.call(this, hyperHTML.bind(this));

We all know that compared to any DOM operation, creating a new bound function is 100x cheaper, but maybe you could store that bound function once and forget about it forever instead of recreating it N render calls times?
template.call(
  this,
  this._hyperRender || (this._hyperRender = hyperHTML.bind(this))
);

Or any alternative that better satisfies your coding taste 😄

I wasn't aware of the significant difference caused by surrounding tag content with whitespace. Is there a way to support a more explicit syntax for this? I ask because managing/reviewing whitespace presence is a rather tedious task, imo.
The reasoning for multiple template support was that some components may have very different UI representations - consider a <x-clock> component with two template options, digital and analog, which both use the same data, but have a very different content structures for displaying it. While I suppose one can argue you could make that decision with embedded dynamic eval inside one template, I feel it is much cleaner to offer the ability to separate the two. Thoughts?

There's no way I can understand if you want to inject HTML or plain text, it's explained in the deep dive too.
Moreover, 'Hello ${name}' results into a targeted text mode , it wouldn't make sense to have HTML, nodes, or something else there.
Truth is, hyperHTML has only 3 rules.
Other template engines have {{{this}}} instead of {{this}} and I never know if that's HTML or not.
In hyperHTML it's very simple: is that HTML? No spaces or other chars around. Otherwise its text content

I'm not saying I can't live with whitespace being the delineation between the two, just that seems the code review, maintenance, and debugging ergonomics may be negatively impacted.
Either way, I am happy to have a diffing, fast, lightweight option for templating available. I will add a section on hyperHTML when we update the site for 2.0

If you have suggestions on how to instrument template literal son a way as simple and as short as adding one space I'm listening. Spaces means mostly nothing in HTML so ...I think people just need to get used to hyperHTML only thing to remember


Add support for Animated WebP images.

The title says it all.

This is not likely to be implemented.
Paint,NET is not designed for creating or editing animations.


introduce a new function non_negative_difference

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated
[x] Sign CLA (if not already signed)

Can you rebase to a single commit and update the changelog? Then I'll double check that this is OK to merge and hopefully have it done before the end of the day.

@jsternberg Done.

Thanks!


Fix test_sysinfo.TestNetwork.test_interfaces test

This test assumed there's always more than one interface which
may not always be the case.  For example you've shutoff all network
adapters you should be left with one interface alone.  This of course
assumes all hosts have at least the loopback interface.

@guidow, PTAL

Looks okay.


Add Configurable Back Pressure to Batch queue

Add a configurable high water mark for the batch queue which will supply back pressure on batch submission.  This adds a new CLI parameter/toml parameter --maximum-batch-queue-size/maximum_batch_queue_size to configure this value.
Batches are rejected during a batch submit, and a QUEUE_FULL status is returned via the ZMQ component interface.  Inbound (i.e. not requested by the completer) Gossip batch messages are dropped.
The REST API will return a 429: Too Many Requests error.
This is a local configuration option, as node performance will vary based on local limitations, such as hardware configuration.
Additionally:

Fixes an issue with the Dispatcher when a previous handler fails with an exception
Fixes an issue with the intkey-workload, such that any non-202 status code is used to check the batch status later.

Updated description based on new changes

Rebased to pick up network changes for testing

Closing in favor of an adaptive back-pressure solution.


Notification:  NOTICE: Longjohn is known to cause CPU usage .. because of xlib

When I start my node server I get this notification:
NOTICE: Longjohn is known to cause CPU usage due to its extensive data collection during runtime.
It generally should not be used in production applications.
After analyzing it comes out that it is from the xlib dependancy of the phantomjscloud.
Maybe is it posisble to replace this library?

yes, I'm surprised about this, I don't think we actually used longjohn in any version of xlib.      Can you let me know your xlib version  (or PhantomJsCloud) so I can investigate further and fix?  If not I'll assume you are using the latest version of the phantomjscloud-node package and will investigate that in the next few days

@jasonswearingen my version is 3.5.5 I think that is the newest version. To see the error message you need to run the project in production environment (NODE_ENV=production)

I can confirm this issue on v 3.5.5, xlib version 16.5.0, requires "longjohn": "^0.2.12",

Hi, sorry about the delay on getting this fixed.  I am finishing up a basic rewrite of the dependency xlib and have been delayed with other issues for the last few weeks.  I should be able to get this taken care of around this weekend.

hi just a fyi that I'm actively working on this now.


Fix: Zhaxan/gali 932 egress store toggle setting - fix update stack policy in postdeployment step

Issue #, if available:
Description of changes:

fix update stack policy in post deployment step

Checklist:

[x] Have you successfully deployed to an AWS account with your changes?

AS review ticket id:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Needs unit test.


Random Password Generator

Stack - html css js

@swapnilsparsh  bro please assign it's been almost 12 hours now


node-rdbg version issue

hello,
When trying to install I get the following:
npm ERR! notarget No compatible version found<EMAIL_ADDRESS><0.4.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.1","0.0.2","0.1.0","0.2.0","0.2.1","0.3.0","0.3.1","0.3.2"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

I checked the repo for node-rdbg and see that it is at version 3.2 only

Thanks, It's getting late.. been rushing since i saw the traffic spike :wink:
<EMAIL_ADDRESS>is published

no man thank you..this tools looks sweet


Adding retry context on query diagnostics by redesigning retry context logic

This PR include below points.

We will have retry context on the query diagnostics.
Refactor the retry context design to make it scalable, and automatically pick any future retry policy.
Added support for session not found on retry context (It was missing before)
Added support of mix retries for e.g. gone + throttling retries in any order in a single request.

Basic idea behind new design . -

We have singleton retry context from a single request , which will be tossed around different stacks of code.
It is responsibility of retry policy to update retry context in (RetryUtils.Java)
Each retry policy will update retry context only if its own exception and not coming from upstream or downstream policy, avoiding duplicate entries

@mbhaskar  Just curious , why you added "Request Change" , is there any concept/design/critical bug you want me to fix. Or are we following this convention going forward for any regular comment ?

@mbhaskar Just curious , why you added "Request Change" , is there any concept/design/critical bug you want me to fix. Or are we following this convention going forward for any regular comment ?

From my understanding, if there is atleast one change that is required before this PR could be merged, we would go with RequestChanges be it small or big. Any other comments which are suggestions or ideas need not block. In this PR, I have couple of comments which I wanted to be iterated over and thats the reason for requesting changes. Let me know if my understanding is incorrect. If we are supposed to "request changes" only for cricital/design changes then I would follow the same 👍 Thanks

/azp run java - cosmos - ci

/azp run java - cosmos - tests


translated testString and added solution

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closing, as #24583 also includes this change.


Debugger entered--Lisp error: (void-variable apheleia-formatters)

When I add following lines into my init.el file:
(setf (alist-get 'isort apheleia-formatters)
      '("isort" "--stdout" "-"))
(setf (alist-get 'python-mode apheleia-mode-alist)
      '(isort black))

I am getting following error:
Debugger entered--Lisp error: (void-variable apheleia-formatters)
  (assq 'isort apheleia-formatters)
  (if (and nil (not (eq nil 'eq))) (assoc 'isort apheleia-formatters nil) (assq 'isort apheleia-formatters))
  (let* ((p (if (and nil (not (eq nil 'eq))) (assoc 'isort apheleia-formatters nil) (assq 'isort apheleia-formatters)))) (progn
(if p (setcdr p '("isort" "--stdout" "-")) (setq apheleia-formatters (cons (setq p (cons 'isort '...)) apheleia-formatters)))
'("isort" "--stdout" "-")))
  load-with-code-conversion("/home/alper/.emacs" "/home/alper/.emacs" t t)
  load("~/.emacs" noerror nomessage)
  startup--load-user-init-file(#f(compiled-function () #<bytecode 0x10f36531c68d12d2>) #f(compiled-function () #<bytecode
-0x1f3c686ddc0ca9b5>) t)
  command-line()
  normal-top-level()

How can I prevent this error?

You have to modify the variable after apheleia has been loaded.
(with-eval-after-load 'apheleia
(setf (alist-get 'isort apheleia-formatters)
      '("isort" "--stdout" "-"))
(setf (alist-get 'python-mode apheleia-mode-alist)
      '(isort black))
  )

@mohkale Thanks. I have isort installed but I am getting following message now:
$ isort --stdout -

Traceback (most recent call last):
  File "/home/alper/venv/bin/isort", line 8, in <module>
    sys.exit(main())
  File "/home/alper/venv/lib/python3.8/site-packages/isort/main.py", line 343, in main
    SortImports(file_=file_, write_to_stdout=True, **arguments)
TypeError: type object got multiple values for keyword argument 'write_to_stdout'

Command failed with exit code 1.

@avatar-lavventura
I got this error a while back as well. I can't remember what I did to fix it, but try upgrading your isort version.

@mohkale Upgrade solves it :-)

Nice, thanks all!


User Story: As a small business, I need to know which agencies are low on their subcontracting plan targets so that I can grow my business.

User Story: As a small business, I need to know which agencies are low on their subcontracting plan targets so that I can grow my business.  Producing reports and dashboards that would identify large prime contractors in need of small business support in specific categories would make aid in efforts to grow small business and aid large business in connecting to small business to meet their goals.  Ideally, the Subcontract Plan Targets will be added as an element (https://github.com/fedspendingtransparency/fedspendingtransparency.github.io/issues/139); but even without that data element, companies can easily determine shortfalls and opportunities.
Further, flipping this around, creating information displays that show the first tier small (and other socio-economic category) businesses with expertise in areas or agencies would aid large business in finding capable subcontractors and teaming partners.
Flipping this a third way, this information display would enable contracting officers, OSDBU and SBA PSC's in performing market research to support set aside decisions.

Add the story in JIRA: https://federal-spending-transparency.atlassian.net/browse/PUB-78
@HerschelC It seems like the goals (up to 2014) are captured here: https://www.sba.gov/content/small-business-procurement-scorecards-0
Perhaps we could work with SBA to publish these in a machine readable way for ingest into USASpending. I think that these goals are high level and kind of live above the granularity for reported DATA act data.

That's a great idea!  The small business targets, including subcontracting plan, should be easy to pull in and the basis for a dashboard.  These quantitative portions of these reports should be automatically generated from Usaspending.  There's no reason to be posting PDFs when Usaspending could have a dashboard built from facts within the data.  This should be the single source for measurement based upon data facts - what gets measured, gets done.
But something seems to be off - and whatever it is needs to be explained at the point of information delivery to the information consumer.  I picked on USAID since they were listed first on the SBA scorecard website.  The pdf scorecard indicates achievement of the Small Disadvantaged Business metric, more than doubling the target, with $184.3M in subcontracting to Small Disadvantaged Business. I went to Usaspending and downloaded the subcontract award data for FY14.  I filtered for "disadvantaged" in the subawardee business types and came to a subaward total of $11,972,599.64.   This is more than ten times the amount supported by the data.  Why? Is the question that should have an answer at the ready.  This is simple "back of napkin" analysis and it's off by orders of magnitude.  How can the agency have a number that is vastly different than the number reported to the public?  [I'm not asking for an answer, just saying these will be the questions. Queue, data lineage and dictionary conversation.]
Let me touch back on the data element point.  There is a more granular level of detail to which I refer in the proposed element.  Large businesses must submit a subcontracting plan as part of many procurements - I believe based upon size of the procurement.  These plans are actually part of the award evaluation criteria.  Many times these subcontract plans are a simple statements to the effect "we will try our best to find 8a/HUBZone/Small, etc. to complete x% of the work".  This is part of their proposal.  It is this level of granularity that I propose in the new element item 139.  This award/contract-level granularity should roll up to the agency level targets.  This is also where the user story comes from - helping large businesses to meet their subcontracting goals as submitted.


Odd behaviour of Kashtira in multiplayer (using older localfiles trick)

I don't know how much is really the mods fault as this is using the older localfiles from just prior to Konami invalidating the archive that was previously used for unreleased cards, but I figured it should be reported in case it is addressable or persists with the upcoming selection packs release.
So, the issue is that all the Kashtira spells, traps, and monsters are currently being interpreted as 0/0 monsters by the client. This ONLY happens in multiplayer. If you take the same deck into solo mode it works like normal.

The card data for multiplayer does not your LocalData card data. Any cards which were not in the game when I made a given release wouldn't have data values.

well that explains a lot.


misspelt words

hi,
I happened to find that there are some misspelt words in the code, like
ProcessQueue#makeMessageToCosumeAgain, which should be ProcessQueue#makeMessageToConsumeAgain,
and ProcessQueue#takeMessags, which should be ProcessQueue#takeMessages,
and LocalTransactionState.UNKNOW,  which I believe should be LocalTransactionState.UNKNOWN.
RocketMQ version: 4.5.2, current master branch.

@huangzhike some spelling mistakes can correct as some functions only just be used in rocketmq inner, but some spelling mistakes cannot be corrected just because it exposed to users, thus there will be compatibility issues after correct.


[ConstraintSystem] NFC: Fix type variable printing in connected compo…

…ents and constraint system state

@swift-ci please smoke test

Thank you!  Sorry to have regressed this.


Dataset

I download the udd5.rar and find that all pictures of gt folder are black.

The labels are only from 1 to 5, but your visualization space is from 1 to 255, so everything is black.
You should use some visualization tools, like the imagesc function in MATLAB.


feat: Update linked packages in package-lock.json

Hi, I'm making a start for #1842 as this is very important for me.
I'm not fully into the code and this is just the starting point in my opinion.
Would love if someone could assist on this one!
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Addresses #1842 🦕

Updated CLA

This should be the right direction, but I'm still struggling with the test. Any help would be greatly appreciated!

Sorry, I have currently no time to get back to this, could anyone continue on that one?


Release and publish to npm

#200 is causing an error for us. Can we get a release on npm please? :]
cc @vipyne

@toji can you bump the version (npm version patch && git push --tags) and publish 0.9.27 to npm (npm publish)?

I tried but I don't have permission for the npm repo. Paging @borismus to either push or give me permission to do so.

I've pushed 0.9.27 to npm. @toji you should now have the ability to push too.

Awesome! Thanks!

ty !


APIv2: prototext: unmarshal does not preserve negative 0

Text unmarshaling does not preserve the sign of floating point -0.
Test case (in encoding/prototext/decode_test.go):
        }, {
                desc:         "float negative zero",
                inputMessage: &pb3.Scalars{},
                inputText:    "s_float: -0",
                wantMessage: &pb3.Scalars{
                        SFloat: float32(math.Copysign(0, -1)),
                },
        }, {

https://oss-fuzz.com/testcase-detail/5683024310304768

Quite possible this bug exists for protojson too.

Unmarshaling does preserve negative zero when the number is unambiguously floating point: -.0 or -0f.
Marshaling encodes a negative zero as a plain -0, which unmarshal will interpret as an integer, discarding the sign.
I'm not sure what the correct behavior is: Should unmarshal preserve the sign of -0? (Requires understanding that -0 might be an integer or a float.) Or should marshal encode floating point -0 as -.0/-0.0/-0f?

protojson is fine, because JSON only has floating point numbers so there's no point where the sign bit is lost.

I think this is a situation where we should look at what the C++ implementation does? At least until there is a defined standard to follow.
If C++ is printing just a -0 then we have to consider we might be getting simple -0 as an input, no matter what we output from Marshal. So we might have to find some way to keep the value ambiguously, until it is assigned. :weary: We might be able to short-circuit something and dictate that -0 is always a floating point value? Then only when it is assigned into an integer field, it gets properly cast into the expected non-negative 0.
On the other side of the issue, I would probably prefer -0.0 as output from Marshal. As it is the most abundantly clear as to what it is and why it is.

Agreed that we should look to C++'s behavior for guidance.
$ echo 'optional_float:-0' | protoc -Iinternal/testprotos internal/testprotos/test/test.proto --encode=goproto.proto.test.TestAllTypes | protoc -Iinternal/testprotos internal/testprotos/test/test.proto --decode=goproto.proto.test.TestAllTypes
optional_float: -0

I'm not certain if protoc's text (de)serialization uses the standard C++ implementation or not, but it both understands and outputs -0 for negative zero.
So I guess the minimal fix is going to be to decoding.

I just checked C++ behavior.
The TextFormat package defined in google/protobuf/text_format.h does print -0 and parsing does preserve the sign bit.
For the JSON serialization lib in google/protobuf/util/json_util.h, it does print -0 as well.  Parsing double does preserve the sign bit, but parsing float somehow didn't.
https://golang.org/cl/204602  which rewrites internal/encoding/text does fix this for prototext already.  I've incorporated the tests from neild@'s https://golang.org/cl/217501.
And current protojson does not have this issue.


Documentation for automatically clearing the Office cache

The documentation here suggests that it is possible to "configure the Office cache to be cleared automatically every time Office is reopened." At least based on my testing, it appears this is not really true.
The checkbox for "Next time Office starts, clear all previously-started web add-ins cache" does not get preserved after re-opening Excel, so when I re-open a second time, the cache is not cleared (unless I made sure to check the box again).
Is this expected to be the case? If there is a way to clear the cache automatically every time, I would definitely like to know how!

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

ID: 4e273e29-10ac-440e-634e-588b5208e484
Version Independent ID: a5a6dc8a-b504-686e-80ce-45aabd6f832b
Content: Clear the Office cache - Office Add-ins
Content Source: docs/testing/clear-cache.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Hi @romglusker,
Thank you for reporting this. I just checked and am observing the same behavior with the cache-clearing setting. Let me tag @jargil to help investigate.


Feature request: Add support for ESP32 long range mode

ESP32 supports a long-range mode with ~1km line of sight range. This mode was introduced quite a while ago.
Please include an option to enable this mode when using ESP32.
More information can be found here: https://www.hackster.io/news/long-range-wifi-for-the-esp32-9429ab89f450

ESP32 lacks an appropriate high-speed interface for a video stream.

@seeul8er: What is the relation between long-range mode and "high-speed interface for video stream" ? I would like to use DroneBridge for Telemetry with ArduPilot. That does not need to be high-speed. As I understand from the linked page it should be fairly easy to enable the long-range mode and thus I consider it as useful.


Deleted message disappear for a moment when transistioning from offline to online

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

Version Number: 1.4.57-3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1711665611722399?thread_ts=1711571474.268739&cid=C01GTK53T8Q
Action Performed:

Go offline
Send a message
Reply to the message
Delete the message you sent in (2)
Come back online

Expected Result:
While waiting for the network request to process deleted message should appear strikethrough and then deleted message should appear
Actual Result:
While network request from offline to online processes, the message deleted from step 2 will disappear rather than showing [Deleted Message].
Workaround:
unknown
Platforms:

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

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub

Yeah if this is reproducible in both this is not a blocker.

Is this a fire? Does it need to be hourly?

Since this is not a blocker, moving to Daily

Proposal
Please re-state the problem that we are trying to solve in this issue.
Deleted message disappear for a moment when transistioning from offline to online
What is the root cause of that problem?
In here
https://github.com/Expensify/App/blob/99cc0b6f34c477dee40934b0ffb294e5dde1f58a/src/libs/actions/Report.ts#L1315-L1316
We haven't included ADD_COMMENT when the report action is isThreadParentMessage so as we created the report action offline (ADD_COMMENT) the DELETE_COMMENT of the parent message is getting canceled when going online so the isDeletedReportAction is being reset to false and as the message.html is empty it will disappear and not displayed
What changes do you think we should make in order to solve the problem?

We need to add ADD_COMMENT for parent messages too here
https://github.com/Expensify/App/blob/99cc0b6f34c477dee40934b0ffb294e5dde1f58a/src/libs/actions/Report.ts#L1315-L1316
isDeletedParentAction
                        ? [WRITE_COMMANDS.ADD_COMMENT, WRITE_COMMANDS.UPDATE_COMMENT]

What alternative solutions did you explore? (Optional)

@shubham1206agra what do you think of the above proposal?

putting this on HOLD for https://github.com/Expensify/App/issues/39432, as there's a good likelihood this will be fixed over there

Proposal
Please re-state the problem that we are trying to solve in this issue.
Deleted thread parent message disappears when go online instead of showing [Deleted message]
What is the root cause of that problem?
In ReportActionsList, we are filtering out any action that has a pending action of DELETE.
https://github.com/Expensify/App/blob/b0a50cbaf487fa4e2da9e41c3bd912dc353af863/src/pages/home/report/ReportActionsList.tsx#L188-L194
It's not happening while offline because we include isOffline condition on the filter logic. The filter was first introduced in https://github.com/Expensify/App/pull/31670 and the filtered report actions were previously used only in this useEffect.
https://github.com/Expensify/App/blob/b0a50cbaf487fa4e2da9e41c3bd912dc353af863/src/pages/home/report/ReportActionsList.tsx#L218-L229
But after the comment linking, we add ReportActionsUtils.shouldReportActionBeVisible condition and use it to render the list items too. We add ReportActionsUtils.shouldReportActionBeVisible because the report actions from the report screen include all actions.
https://github.com/Expensify/App/blob/b0a50cbaf487fa4e2da9e41c3bd912dc353af863/src/pages/home/ReportScreen.tsx#L707
https://github.com/Expensify/App/blob/b0a50cbaf487fa4e2da9e41c3bd912dc353af863/src/libs/ReportActionsUtils.ts#L609-L619
What changes do you think we should make in order to solve the problem?

First of all, whether we use sortedVisibleReportActions to render the list or not, the first filter condition is not complete
(isOffline || reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE || reportAction.errors)
because we don't consider the case for deleted parent action (isDeletedParentAction).
So, my suggestion is to include ReportActionsUtils.isDeletedParentAction(reportAction) condition.
-(isOffline || reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE || reportAction.errors)
+(isOffline || ReportActionsUtils.isDeletedParentAction(reportAction) || reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE || reportAction.errors)

This is enough, but if we see the above condition, it's similar to shouldReportActionBeVisible.
https://github.com/Expensify/App/blob/b0a50cbaf487fa4e2da9e41c3bd912dc353af863/src/libs/ReportActionsUtils.ts#L500-L502
The main difference is, shouldReportActionBeVisible includes all action with pending action of DELETE. I'm thinking of updating shouldReportActionBeVisible to include pending action of DELETE only while offline so we don't need to use the first condition, but I'm not sure because shouldReportActionBeVisible is being used in many places and I don't know what regression would wait us.

Sure, will do that tomorrow

shouldReportActionBeVisible usage

ReportActionsList - SAFE
extractAttachmentsFromReport - SAFE
SidebarUtils - SAFE
OptionsListUtils - SAFE
shouldReportActionBeVisibleAsLastAction - SHOULD BE SAFE
There are a lot of usages of shouldReportActionBeVisibleAsLastAction and I haven’t check them one by one, but If I read the logic, the output shouldn’t change. Why?

If we proceed to filter out a pending delete action while online in shouldReportActionBeVisible, then the output of new shouldReportActionBeVisible will differ from the current logic in the online case.
Now, here is the logic of shouldReportActionBeVisibleAsLastAction
https://github.com/Expensify/App/blob/f1502291a14d4e15e04249b241109f146bdb512f/src/libs/ReportActionsUtils.ts#L530-L534
Notice that the logic checks for deleted action, but not deleted parent action, doesn't matter whether online or offline. Let's say we pass a report action with a pending action of DELETE while online with the new logic of shouldReportActionBeVisible. shouldReportActionBeVisible will return false, and !(isDeletedAction(reportAction) && !isDeletedParentAction(reportAction)) will also return false.
If we use the current logic of shouldReportActionBeVisible, shouldReportActionBeVisible will return true, and !(isDeletedAction(reportAction) && !isDeletedParentAction(reportAction)) will still return false, so the output of shouldReportActionBeVisibleAsLastAction is the same between new and current shouldReportActionBeVisible usage.

getLastVisibleAction

ReportActionsUtils.getLastVisibleMessage

ReportUtils.getLastVisibleMessage

ReportUtils.shouldReportBeInOptionList

SidebarUtils.getOptionData

IOU.deleteMoneyRequest

IOU.deleteTrackExpense

Report.addActions

Task.deleteTask

ReportUtils.getLastVisibleMessage

Report.deleteReportComment

ReportUtils.getPolicyExpenseChatName

IOU.deleteMoneyRequest

IOU.deleteTrackExpense

Report.addActions, Report.deleteReportComment, Report.editReportComment

Task.deleteTask

getLastMessageTextForReport (for LHN/options last message)

doesReportHaveVisibleActions - SAFE

Task.deleteTask - SAFE

getSortedReportActionsForDisplay (if shouldIncludeInvisibleActions is false)

LHNOptionsList - NOT SURE

Even though most of them are SAFE, I have another concern. Because the new logic of shouldReportActionBeVisible depends on network status (offline/online), it means we need to pass it from the param and that requires a lot of changes. Also, how do we subscribe to network status if shouldReportActionBeVisible is used inside an Onyx callback?
https://github.com/Expensify/App/blob/f1502291a14d4e15e04249b241109f146bdb512f/src/libs/SidebarUtils.ts#L28-L42

Are we still holding for https://github.com/Expensify/App/issues/39432 or are we working on this issue? Asking so that I can update the title appropriately

I think so

This should remain on HOLD for now

It's not related to https://github.com/Expensify/App/issues/39432, so we don't need to hold.

My mistake - @shubham1206agra and @bernhardoj are correct, and I got my wires crossed confusing this with another issue.

next step - waiting for @bernhardoj to open a PR

Sorry for the delay, PR is ready for review
cc: @shubham1206agra

PR was deployed to prod a week ago. Ready to pay.

Payment summary:

@bernhardoj $250 - offer sent
@shubham1206agra $250 - offer sent

@shubham1206agra update :)

paid ✔


User can choose whether to initialize markdown editor with edit mode …

…or preview mode
If Markdown Editor has been initialized with editMode = false,
Just like git, viewer can see the markdown first, and if there is something to update, can edit it

@suziewithz Nice. Looks good to me.
Could we maybe add one/two unit tests?

@suziewithz Let me know if you can add some tests


rust-lld broken on latest x86_64-apple-darwin nightly

rust-lang/rust#76698 is the reason that the CI failed

As workaround we define macOS as experimental platform and our pipeline doesn't longer depend on macOS.

Issue is fixed and macOS is reactivated.


Error: unhandled exception: value out of range: 256 notin 0 .. 255 [RangeDefect]

Happens in: /src/parlexgen/private/utils.nim:64,12.
I think this is an overflow of the number of stored patterns? At least it seems to resolve itself if I remove enough cases from this capture r"(endif|endcase|endfor|endtablerow|endcomment|endraw|endcapture|end)", or if I comment out a number of other expressions anywhere in the lexer definition.
Maybe I'm wrong and this is something else, but I don't think it is something I did 🙂

the error actually doesnt happen there. That utility function just executes some precompiled code at comp-time (which is precompiled for performance reasons). But just from that error I can't tell whats the origin of the error. can you share the stack-trace?

I think I fixed it


Allow unsorted (but still "continuous") index for packing

In src/nested_pandas/series/packer.py we frequently assume index to be sorted, for example here:
https://github.com/lincc-frameworks/nested-pandas/blob/a96a508d906c5c31de06573583ec8c5fd7a2de9b/src/nested_pandas/series/packer.py#L131
https://github.com/lincc-frameworks/nested-pandas/blob/a96a508d906c5c31de06573583ec8c5fd7a2de9b/src/nested_pandas/series/accessor.py#L231
We should make it more flexible and allow "continuous" index.
Before submitting
Please check the following:

[x] I have described the situation in which the bug arose, including what code was executed, information about my environment, and any applicable data others will need to reproduce the problem.
[ ] I have included available evidence of the unexpected behavior (including error messages, screenshots, and/or plots) as well as a description of what I expected instead.
[ ] If I have a solution in mind, I have provided an explanation and/or pseudocode and/or task list.

It is partially replaced with #161, so closing for now


Upgrade Azure Communication Services Phone Numbers to 1.0.17

Description
Upgrade Azure Communication Services Phone Numbers to 1.0.17. The change only includes patch updates.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-communication-phonenumbers


Handle Delete and Ctrl-W events

Add handling for the delete key and for Ctrl+W.

Thanks for the PR! (Sorry for the delay!) I have a question:
Is Ctrl+W a generally-known keyboard shortcut from other readlines? If not, it might make more sense to have it behind a configuration option in case there is a better consensus for what the behavior should be. Currently IIRC, the readline implements some emacs commands, so it might be better to reserve Ctrl+w for the emacs default behavior (delete selection) instead of this PR implementation (delete preceding until space).
Also, in the future if possible, it is generally better to split independent features into multiple PRs (i.e. Delete key and Ctrl+W key can be added separately).

Hm, tbh I didn't consider that since I'm so used to using Ctrl+W in various interactive CLI applications (e.g. bash/fish, Python REPL, vim, ...). Looking at some other readline implementations it seems to be pretty universally accepted:

rustyline (in the common() key handlers)

A readline implementation in go

man 3 readline:

"C-W"  unix-word-rubout

in both Emacs and VI mode bindings.

I have rebased the commits! :tada: (idk why I didn't merge, no matter how much I use git I just can't get used to it :sob:)
Thanks!


cli: colorize CLI output

The click library has built-in support for ANSI terminal colors. For this issue, we will colorize the output of the commands of the CLI.

Hi, I would like to work on this one.
Is there any color scheme decided for the outputs?


MQTT

How could MQTT be used? Is there an example?
Thank you
(I do not speak English)

You need a MQTT broker first, like http://mosquitto.org
My system run on Raspberry Pi
than you can publish the UID to the broker and subscribe it with another application like NodeRed

yo tengo instaldo mosquito en win7 lo que entiendo es que puedo hacer con el, recien instale node red en win y voy a probar pero quisiera alguna ayuda

sorry with win 7 I'm out
-I use Raspberri Pi
-NodeRed
-FHEM

ok entonces supongamos que instalo mosquito y node-js en una vm con ubuntu 16 como se comunica con wemos d1 mini?

@SamNitro Did you have chance to test 0.7's MQTT functionality ?

@omersiar Yes I have ;) and it works :)
@nbaglietto yes it should be work! If you have a MQTT Broker on ubuntu 16, you can read the Topic (message / UID) on win 7 (if win7 have a MQTT client)
The broker have to run 24/7 Hours, that the message can be receive.

Yea! Now my esp-rfid works and I wonder what messages are published via MQTT?
Is there any overview somewhere? I have a home-assistant with mosqitto running and wonder what nice thinks I could do now with esp-rfid...
Thinking about putting a nfc-tag on my LP-cover and instead of playing the LP with the player I could just take the cover and touch the esp-rfid. It triggers the mqtt and home assistant knows to trigger mpd which takes the right album (from the uid) and just play's it...

Everybody tested MQTT with CloudMQTT online? I did not get any message there.
Everytime I reboot the ESP the option for MQTT is disabled.
Version is 0.7 on NodeMCU with RC522 (works correct)
Best regards

@rradar if enabled esp-rfid only publishes scanned rfid tag's uid on given topic. MQTT support is newly changed and we need testers. Feedbacks are welcome.
@thifi Does CloudMQTT supports unencrypted connections? It was working before?

CloudMQTT support 3 different cennections like:
Port | 19977
SSL Port | 29977
Websockets Port (TLS only) | 39977
I used the "normal" port, I think this is unencrypted.
I used it before with ESP-Easy and MQTT with success.

@thifi I do not know how to debug MQTT issues. I do not have MQTT testing environment yet.

Hello, what I do not get is that esp-rfid is connected to my mosquito broker that I have in an ubuntu 16 in esp-rfid fill the subject field I put username and password and the ip address of the broque check the enable button but it does not connect and every time I renicio appears me the disabled mqtt.
(I do not speak English )

@omersiar
I get this message in the log-file of CloudMQTT if I try to connect from the esp-rfid:
2018-03-28 07:13:08: New client connected from <IP_ADDRESS> as ws0.8792021369477999 (c1, k60, u'pkvaifbf').
2018-03-28 07:14:57: Socket error on client ws0.8792021369477999, disconnecting.
I hope you can use it for the search of the problem...

I get feedback!
Settings in esp-rfid:

local mqtt ip adress
local mqtt port
topc: "/esp-rfid"

And a local mosquitto server esp-rfid connects to (without user & password for testing)
To check my success I use mqttbox which looks like this:

@thifi
maybe it's a problem with websocket? I tested with mqtt/tcp (without websocket/without encryption/without user+password) and it worked right away...

Can you flash this and look for event log? https://github.com/omersiar/esp-rfid/blob/dev/bin/firmware.bin

Hi,
restart after flash ok, when I use MQTT data and restart: Exception (29) like on the picture

This is a serial copy, I could not get a webpage after restart with MQTT data.

firmware.zip
Try this one please.

Clear event log and restart.

Clear is ok, after restart the same problem with Please wait while fetching data...
After clear event log and access log there is no RFID Tag readable, no reaction, after reboot also.

firmware2.zip
:) Can you test this one, this should create a event log with a reason

No eventlog at all, I don't whats wrong.
The RFID-Reading doesn't work.

I think I have a hardware problem with 522, with original firmware 0.7 no RFID-reading :-)

ok, no hardware problem, software.
I flashed esp-easy, this formated the memory, then I flashed firmware2,
the esp started but no event-log.
The other points works, ntp, rfid, dhcp, user and access-log ok.

@thifi I couldn't reproduce this issue.  I do not understand why your MQTT service complains about websocket. MQTT simply tries to connect given port via TCP socket.

@SamNitro Hello,
Can you please test latest dev branch MQTT functionality.  To see if events correctly populated? Thank you.

Hello, I was able to test MQTT successfully on the fast, but the event log does not show any data
"Please wait while fetching data..."

I tried to establish MQTT connection in local host, as well as in cloud broker. None of them worked. I have checked the code where it was publishing and have serial printed something to see if the code is reaching there, I found that the code was actually reaching there. I think, the problem could be in the library. If you know some work around or need some help, please do tell. BTW this is a wonderful work you are doing here.

@blmhemu Thank you,
I built my MQTT test environment with mosquito. I am using RC522 reader. UID is publishing and event log works. Cloudmqtt somehow thinks esp tries to connect its Websocket and fails, sometimes Event log mentions MQTT_NOT_AUTHORIZED with cloudmqtt. I do not know why cloudmqtt is failing but esp definitely can not connect to it.  Also on mosquito _sub command lists publishes as like this /esprfid/ 81a5428  there is a space between / and uid, I do not know if this is normal behaviour.
Also it seems onMqttPublish does not work. maybe mosquito does not ack the pusblish.

Hey omersiar. THX you do a great job!
Today I flashed the dev firmware.
-upload the dev fw by using the webpage did not work for me. I got the same error as @thifi

erasing the flash and reflash the dev fw did the trick.
-fix IP works fine
-mqtt enable/disable works fine
-mqtt (mosquitto with user/pw) doesn't work.
-mqtt (mosquitto without user/pw) works

Something fishy is going on between Async Web Server and Async MQTT.  Both depends on Async TCP and i believe there is a TCP client collusion somehow.

@magic-tune
I can confirm this. When I enter usr / pswd from web ui , it doesn't work.
But i did not try doing it from code.


[WIP] Change type for private blog settings

This is done on top of / should be picked into #5688. I've made a few fixes, as well as adding an extra op to change the type of the private blog settings. This needed some updates to the settings model, otherwise the changes weren't made.
The fixes should possibly be merged back into other commits in #5688 and I can rebase this on top / PR the main change direct to @sebgie's branch for #5688. I just wanted to push so I had it all to hand.
Whilst I was looking at this, I came across two other things:

fixture modifications possibly ought to be wrapped in a transaction in an ideal world?
the to003 code in permissions/index.js is horribly broken and I have no idea how it ever worked!

refs #5614 and #5503

update private blog type
add logInfo where missing
switch order of populate settings & update fixtures

Private blog settings should not be returned by public endpoints
therefore they need a type which is not blog or theme.
core doesn't suit either, as those settings don't usually have UI
To resolve this, I created a new type private which can be used
for any setting which has a UI but should not be public data

Any reason this couldn't be resolved with a private boolean field on the
settings model?
On 23 Aug 2015 23:22, "Hannah Wolfe"<EMAIL_ADDRESS>wrote:

This is done on top of / should be picked into #5688
https://github.com/TryGhost/Ghost/pull/5688. I've made a few fixes, as
well as adding an extra op to change the type of the private blog settings.
This needed some updates to the settings model, otherwise the changes
weren't made.
The fixes should possibly be merged back into other commits in #5688
https://github.com/TryGhost/Ghost/pull/5688 and I can rebase this on
top. I just wanted to push so I had it all to hand.
Whilst I was looking at this, I came across two other things:

fixture modifications possibly ought to be wrapped in a transaction
in an ideal world?
the to003 code in permissions/index.js is horribly broken and I
have no idea how it ever worked!

refs #5614 https://github.com/TryGhost/Ghost/issues/5614 and #5503
https://github.com/TryGhost/Ghost/issues/5503

update private blog type
add logInfo where missing
switch order of populate settings & update fixtures

Private blog settings should not be returned by public endpoints
therefore they need a type which is not blog or theme.
core doesn't suit either, as those settings don't usually have UI
To resolve this, I created a new type private which can be used
for any setting which has a UI but should not be public data
You can view, comment on, or merge this pull request online at:
https://github.com/TryGhost/Ghost/pull/5706
Commit Summary

Add the needed table columns for client Oauth.
Add tour field to User; Bump Schema version; Update tests
remove jQuery theme injection in ghost_foot helper and add cdn link
when migrating
Add table columns for OAuth
Update client fixtures
Change type for private blog settings

File Changes

M Gruntfile.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-0 (47)
M core/server/api/notifications.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-1 (7)
M core/server/data/default-settings.json
https://github.com/TryGhost/Ghost/pull/5706/files#diff-2 (16)
M core/server/data/fixtures/fixtures.json
https://github.com/TryGhost/Ghost/pull/5706/files#diff-3 (9)
M core/server/data/fixtures/index.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-4 (117)
M core/server/data/migration/index.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-5 (7)
M core/server/data/schema.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-6 (16)
M core/server/helpers/ghost_foot.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-7 (10)
A core/server/models/client-trusted-domain.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-8 (17)
M core/server/models/client.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-9 (5)
M core/server/models/settings.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-10 (11)
M core/test/integration/api/api_tags_spec.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-11 (6)
M core/test/integration/export_spec.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-12 (6)
M core/test/integration/import_spec.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-13 (22)
A core/test/integration/migration_spec.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-14 (40)
M core/test/unit/migration_spec.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-15 (4)
M core/test/unit/server_helpers/ghost_foot_spec.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-16 (88)
M core/test/utils/api.js
https://github.com/TryGhost/Ghost/pull/5706/files#diff-17 (2)
M package.json
https://github.com/TryGhost/Ghost/pull/5706/files#diff-18 (1)

Patch Links:

https://github.com/TryGhost/Ghost/pull/5706.patch
https://github.com/TryGhost/Ghost/pull/5706.diff

—
Reply to this email directly or view it on GitHub
https://github.com/TryGhost/Ghost/pull/5706.

@halfdan Settings come in various types already, these two should not be set to blog - this was an oversight. blog settings are intended to be those which are publicly available/useful - e.g. can be included in <meta> tags in the frontend or requested from the API without auth. core settings are ones which are internal only, and have no UI, this is a new class or type of setting - one which has a UI in the admin interface, but which should not be public.

This has been updated with:

new jQuery notification message & comment
https link for jQuery
updated client_trusteddomain table to be called client_trusted_domains
fixed an issue with the use of _.extend
new log messages (to be squashed)
updated my fix for settings edit to not ignore empty values (I couldn't empty out ghost_foot, whoops!)

Still @TODO:

Add migration for tags (see #5709)
Test jQuery migration now works from 0.5.5 -> this PR
Test all of these migrations work with sqlite, mysql & postgres
Fix the bug with upgrades from db version 002

I've now completed the following 3 tasks and added them to this PR:

Add migration for tags (see #5709)
Test jQuery migration now works from 0.5.5 -> this PR
Fix the bug with upgrades from db version 002

The tests for the jQuery migration flagged up that we were only populating the databaseVersion setting as part of migrations, rather than adding all missing settings, so I changed the code here
There turned out to be 2 bug fixes for migrating from older pre-multiuser blogs. The first was to fix the horribly broken promise code here. The second was to resolve an issue with the creation of passwords here when there is no owner user present in the DB - this helps with old migrations plus any failed fixture initialisations. More info on that issue can be found here.
I have now tested upgrading from Ghost 0.4.2 and Ghost 0.5.5 with sqlite. What remains is to also test these upgrades on mysql & postgres, as well as testing upgrading from 0.6.0:

Version
DB
Tested By

0.4.2
sqlite
Hannah

0.4.2
mysql

0.4.2
pg

0.5.5
sqlite
Hannah

0.5.5
mysql

0.5.5
pg

0.6.0
sqlite

0.6.0
mysql

0.6.0
pg

Databases for testing upgrading can be found here: https://github.com/TryGhost/Ghost-Config/tree/master/ghost-versions

Updated:

Rebased against current master, inc the tag UI fix
Added both of #5771 & #5773 to this PR
Updated the name of results to hash in Fix upgrade path from really old versions
Updated the jQuery migration to not insert the code if it has already been inserted (meaning running FORCE MIGRATION=true is safe)

TODO:

New post fixture.

Added the new fixture - the content is still WIP, but the general premise of how the fixture is added won't change, so this can be tested.


Release cadence

Hello there,
I'm simply wondering about your release cadence and all !
I'm asking because I am very interested in using https://github.com/distribution/distribution/pull/4096 that was ~merged~ opened days after the last release.
Thanks !!

There is no strict schedule at the moment and probably never will be. We're actively working on releasing v3, though.

FYI: we cut a new release last night https://github.com/distribution/distribution/releases/tag/v3.0.0-alpha.1

awesome! Thanks

Mind closing this issue now then?

Sure, thanks for your time :)


Update reference apps to use Gradle 8.0 / AGP 8

We try to keep the reference apps supporting older versions of Android Studio. Right now the minimum is Android Studio Dolphin, which is five versions behind the current stable, Iguana. I think it's time to update to support Flamingo / AGP 8.0 / Gradle 8.0. This will remove some deprecated build configuration and reduce surprise CI failures that stem from some change being incompatible with the old releases.

This is blocking the upgrade to Compose 1.7.x: #1617


Obtain event object from the event listener

Take the example:
<fab
   :position="position"
   :bg-color="bgColor"
   :actions="fabActions"
   @cache="cache"
   @alertMe="alert"
></fab>

Says I have 5 buttons with alertMe event registered. I want to special handle each button to do something very specify depending on which button it is. Is there a way to know which button is triggering the event listener method via event object?
Maybe something like:
<script>
import fab from 'vue-fab'

export default {
  components: {
    fab
  },
   data(){
      return {
          bgColor: '#778899',
          position: 'top-right',
          fabActions: [
              {
                  name: 'cache',
                  icon: 'cached'
              },
              {
                  name: 'alertMe',
                  icon: 'add_alert'
              }
          ]
      }
  },
  methods:{
      cache(){
          console.log('Cache Cleared');
      },
      alert(event){ // Here is some event info.
         if (event.src.id === 1) { // First button
          alert('Clicked on alert icon');
         }

         if (event.src.id === 2) { // Second button
          alert('Oh no. Something went wrong!');
          // Do something.
         }

      }
  }
}
</script>

I agree on Wei Jye,
We should have a common method to handle multiple buttons. Here's another suggestion where you can pass parameter to event listener. Likewise in the emitter method here
instead having our event emitter calling multiple listeners like below:\ of this:
toParent(name) {
this.$emit(name);
this.toggle = false;
},
I would suggest that we pass parameter like below :
toParent(name) {
this.$emit('button-clicked',name);
this.toggle = false;
},


SQL breaking changes to fix Swagger spec validation errors/warnings

AutoRest enabled several new validation rules which exposed some naming issues in SQL swagger specs. I also noticed that several classes are no longer supported.

Removed unsupported types (e.g. Schema, Table, Column)
Revised import export  operation and class names
Removed unnecessary import export operation results APIs

Corresponding Swagger change: https://github.com/Azure/azure-rest-api-specs/pull/1005

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as a link to the swagger spec, used to generate the code.
[x] The project.json and AssemblyInfo.cs files have been updated with the new version of the SDK.

@jaredmoo,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

This PR should be merged at the same time as https://github.com/Azure/azure-sdk-for-net/pull/2914 and https://github.com/Azure/azure-sdk-for-net/pull/2925

#2914 and #2925 are now combined into this

Swagger changes are all merged now.

btw project.json isn't updated because 1.2.0-preview hasn't been published yet.

@jaredmoo Hey Jared, two quick questions:

Just to be sure, does this spec include all of the changes you originally wanted to make in this PR and the two that you closed?

There are a lot of unnecessary commits, would you mind rebasing to get the number of commits down to 1 or 2?

Yes, since all swagger changes are now merged, all generated files in this change are based on rest-api-specs master branch.
I have squashed into a single commit and described all the breaking changes.

@cormacpayne can I get a review?

UpgradeLog.htm is visual studio junk. Delete it.

@cormacpayne - I have addressed feedback. Not changing project.json since then it doesn't build for me. I think project.json goes away when #2815 is done.

@jaredmoo it looks like there is a merge conflict from a pull request that was merged earlier today

Ok, I reverted my change to this file in order to resolve the conflict.

@cormacpayne ready to merge again :)


Applying sorting on date column:

how can we sort date column Right now date is also sorted as a string value 1st dates of all months display then all 2nd dates of all months.

Hi @sanakalam
You need to use a Date object rather than a String.
As you can see, TableView also compare two date instance.


[WIP] TypeScript

Closes #140.
I had some spare time and wanted to start converting this addon over to TypeScript.
Unfortunately it doesn't fully work yet. But I'd like to gather some feedback already. 😊

@buschtoens Thanks for starting the work on this. I'm very exited to have this addon in TS.
@bgentry I think it would be nice to start a new branch where we can merge the TS work into. That would allow us to move piece by piece, and so, once we are happy with the initial TS refactor, we could cut a beta release.

ember-cli-typescript is available as an alpha for doing the transpilation with Babel. I can upgrade this PR to do that, however I'll then need to replace ember-auto-import with a custom setup, because of the aforementioned incompatibility.

It might be worthwhile to look at adding Babel 7 support to ember-auto-import rather than building custom import stuff here.
@ef4 said here that he'd ultimately like to have auto-import use a Babel plugin for discovering imports, which would avoid having to double-parse everything. That makes a ton of sense as a goal, but will also require some careful caching work to get right.
Maybe separating the Babel 7 support from that work and doing a first pass that continues with the status quo but can work with either the Babel 6 or 7 parser would be a good first step?

:tada: ember-auto-import v1.2.16 has has support for Babel 7. We should be unblocked now to move this PR further.

Awesome! Maybe I can chip in some further work this evening. :)

@buschtoens Thank you for updating this! Is this ready for a review now that it's using the typescript-capable ember-auto-import?
This would actually be my first real experience with TypeScript. Is there anybody with more experience around it that can give this PR a review?

From the technical setup POV this is ready for a review. Only thing missing is failing build for type errors, just because there are so many of them right now.
For all of this to make sense as a whole we also need #139, which can already be shipped before this PR.
The actual source code itself also needs some further TLC. Before merging this, I would like to fail builds for type errors. But until then we can already start reviewing this! :)

Dang, Ember 2.12 is failing. Considering that the LTS schedule for 2.12 has expired, can we just remove it, if fixing this is non-trivial?

@buschtoens For the graphql files, we have a few options to proceed:

Add @ts-ignore to these lines
Add type definitions for these
Allow importing files with .graphql extension (issue in broccoli-graphql-filter)

Here is what a fine definition would look like for the .graphql files
declare module '*.graphql' {
  import { DocumentNode } from 'graphql';
  const defaultDocument: DocumentNode;

  export default defaultDocument;
}

For codegen, I have been using https://graphql-code-generator.com/ for that and works great.

Dang, Ember 2.12 is failing. Considering that the LTS schedule for 2.12 has expired, can we just remove it, if fixing this is non-trivial?

Yes, I am absolutely down with removing old releases that are outside of LTS. I haven't done an ember-cli-update in awhile but that would probably include such a change.

I probably won't get to it in the next day or two, but I'm happy to give this a review next week if it's helpful.

This needs a rebase now that the Ember upgrade has been merged (thanks for that @buschtoens!).
@dfreeman have you or anybody else w/ TypeScript experience gotten to review this?

Good news is: I got *.graphql imports working with https://github.com/csantero/broccoli-graphql-filter/pull/4. Now what's the next step for code gen, @josemarluedke?
Bad news is: I broke the acceptance tests. setup-pretender.js imports graphql and graphql-tools. Since this file is part of the dummy application tree, it is managed by a different instance of ember-auto-import. Importing graphql inside of ember-apollo-client creates a standalone copy of it, that uses the exact same source code, but is not the same identity.
Basically what happens is that the same wrapping module function get executed twice.
This then causes the following error:
Error: Cannot use GraphQLSchema "[object GraphQLSchema]" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.

We need to be able to control where the host app gets its graphql import from. We either do this through or before ember-auto-import.

@buschtoens @josemarluedke are either of you able to summarize the current status of this PR? I'd really like to get it merged, but not actually sure what the remaining issues are. We're still on the 2.x beta series so it would be a good time to get any required breaking changes merged in.
I also merged subscription support so there might be slightly more surface area to convert.

@bgentry I'm really looking forward to move this forward, but we are blocked by this issue in ember-auto-import.
I'm wondering how can we keep moving the codebase for better TS support, a few things come to mind:

Move away from mixins
Convert to native classes
Decorators

I will start working on some of the above. I'm also looking forward to use this addon in Glimmer components (within ember).

If you think that ember-auto-import issue will be fixed soon, definitely ok to wait for that. Otherwise I like the approach you outlined. Don’t need to keep blocking on another issue if we can make obvious incremental improvements sooner.

As this PR stands at the moment, it would be very hard to land as it is. I will close this for now and we will use this as a reference for the TypeScript implementation. We still want to move to TS and with the recent refactorings, this will be easier now.
Thanks @buschtoens for your hard work here.

Awesome 🚀


error：unknown database

我的连接地址是通过vpn连接的，但是使用该软件就不可以，我使用Navicat可以正常连接。
我不知道这是不是bug
My connection address is connected through vpn, but it is not possible to use this software. I can connect normally with Navicat.
I don't know if this is a bug

Is mentioned address used as host? Could you try to use 'localhost' instead?
BTW, what db do you use?
Could you provide steps to reproduce an issue?

there is no update on the issue.
If it is still actual for you - feel free to reopen it with an additional info


Upgrade DBus to 0.7.x

This resolves #64 and obsoletes #63 by updating the dbus dependency to 0.7.
Because dbus 0.7.x was a breaking change from the 0.6.x, there are a couple of minor breaking changes that have to do with non-Mac trait implementations:

MessageItem used to have an impl for From<&NotificationHint> that would produce a MessageItem::DictEntry. DictEntry was removed; the new way to build DBus dicts is by using a tuple of (MessageItem, MessageItem). Therefore, the impl was moved to (MessageItem, MessageItem).
The inverse: NotificationHint used to have an impl for From<&MessageItem> that would only produce a valid hint if called with a DictEntry. It was replaced with a (&MessageItem, &MessageItem).
The FromMessageItem trait was removed. It was replaced with a TryFrom for Timeout.

Although these are breaking changes, it is unlikely that any consumers of the library depended on them. In general, the DBus connection is an implementation detail. Additionally, these traits were not implemented at all on macos.

does this mean we cannot update without a breaking change?

Pretty much. From worst to best:
FromMessageItem was completely removed and replaced with TryFrom. There's nothing we can do about that.
impl From<&NotificationHint> for MessageItem doesn't really have an upgrade path. NotificationHint needs to be converted to a key-value pair. Previously there was a MessageItem::DictEntry that had both the key and the value together, but it was removed and replaced with tuples. There's not really a MessageItem that makes sense to return in this case.
impl From<&MessageItem> for NotificationHint. Previously returned NotificationHint::Invalid for anything except MessageItem::DictEntry. Now that MessageItem::DictEntry is gone, we could add a stub impl that only ever returns Invalid.

ok I guess it's gonna be 4.0.0 then.
Thanks for your work, I hope you get that t-shirt 😁
I'll give it a thorough read this weekend.

Yeah, it's unfortunate that DBus broke API that sharply.
It's also worth pointing out that the DBus maintainer introduced a new API that is apparently better than the MessageItems, and might also be easier to hide. I'm looking into using it for another project, so if it works well I'll pull together a PR that switches over to it.

It's also worth pointing out that the DBus maintainer introduced a new API that is apparently better than the MessageItems, and might also be easier to hide. I'm looking into using it for another project, so if it works well I'll pull together a PR that switches over to it.

That API supports multithreading. Currently, NotificationHandle is !Send, so I'm making a wrapper with an unsafe impl of Send. This seems very fragile, though...

so you suggest switching to that new api all together?

Yes.

I just released another alpha, now hopefully the API is in a shape where we can make changes to dbus under the hood without anybody noticing.
I had to break a few things though and therefore opted to also make all the other breaking changes that were bugging me for some time now. It's mostly renaming and moving things around, please have alook


Onboarding modal doesn't block interactions with the timeline handle

Expected: User shouldn't be able to resize the timeline window while the onboarding modal is open
Actual: User is able to interact with the resize handle while the onboarding modal is open
Video
https://user-images.githubusercontent.com/15959269/187759791-0fa582e0-6359-4576-8f11-6ba118ac3278.mov

By the way, this is an incredible project!
This completely eliminates the need for me to spin up temporary emails to get access to the AfterEffects trial during the two times a year that I do play with it!! 🔥🔥🔥

Possibly the most nitpick non-issue I could imagine, this advanced app and this is the only issue you could find? The 1st issue for library deserves better

@jaril will it be okay if I work on this issue?
Thanks!


{AKS} Update test cases

DO NOT MERGE, TESTING
Description

Add test cases to cover aks update
Update AKSCustomRoleBasedServicePrincipalPreparer
Remove unnecessary @live_only tags and add comments for others

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AKS


Release 0.25.0

Changes Unknown when pulling e21f10f5f26b02d15ed0e73fe4e6476638d991e7 on develop into ** on master**.

Changes Unknown when pulling e21f10f5f26b02d15ed0e73fe4e6476638d991e7 on develop into ** on master**.


fix(component_state_monitor): change pose_estimator_pose rate

Description
I lowered the threshold of pose_estimator_pose because it was triggering too frequently.
related PR https://github.com/autowarefoundation/autoware_launch/pull/910

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@Motsu-san @KYabuuchi  @SakodaShintaro @TaikiYamada4 FYI


Make the menu hotkeys customizable

Perhaps do this through the (legacy) ConfigUI?

In addition to keys I'd suggest the possibility to intercept the VR controller joystick input events for navigating the options (up/down) and for changing settings (left/right). In order to bring up the popup window settings, eventually intercepting VR controller button A event when depressing the CTRL key at the same time, otherwise let it pass through the app?

Yes, this is a great idea. #28 is adding all the hooks to intercept VR controller events (XrAction), so once that is done (which I am working on now), we can use these hooks.

Controller support is a bigger effort, so I've split the request out to #54 and set a later milestone.

Let's try to do this in beta 2.


Support for LEGO 88005 Powered Up Light

Please add support for LEGO 88005 Powered Up Light.
https://www.lego.com/en-us/product/light-88005

Hi, I've just added support for the light, I will get it added to the next pypi release.  You can test it now like so though:
pip3 uninstall buildhat
pip3 install git+https://github.com/RaspberryPiFoundation/python-build-hat.git

Then in your script:
import time
from buildhat import Light
light = Light("D")
light.on()
time.sleep(1)
light.off()

Hi,
Just wondering if you're still having problems with this?
I've just been testing turning on/off the light on a clean boot
and also after unplugging / plugging in the light after.
Thanks

Hi,
sorry for the delay. I checked the latest version with no success. This code:
from buildhat import Hat
hat = Hat()
devices = hat.get()
print(devices)

produces the following output:
{'A': {'typeid': -1, 'connected': False, 'name': 'Disconnected'}, 'B': {'typeid': -1, 'connected': False, 'name': 'Disconnected'}, 'C': {'typeid': -1, 'connected': False, 'name': 'Disconnected'}, 'D': {'typeid': -1, 'connected': False, 'name': 'Disconnected'}}

It is irrelevant at which port the leds are connected. There are not recognized.
I will check now if the leds are working properly.
Cheers

I ordered a replacement. After delivery I will test again.

Light support doesn't work.  This seems to be a firmware problem.  I plugged it into the 51515 hub and was able to set the light levels from 0-10, so the light is not broken.

The old Firmware<PHONE_NUMBER> 2021-08-28T16:45:27+01:00 will power on the lights, but not list them in the device list.

Upgrade to 0.5.7 release but the Light 88005 on port D is not detected.
pi@pi4:~/projects/lego_buildhat $ /bin/python /home/pi/projects/lego_buildhat/hat.py {'A': {'typeid': 75, 'connected': True, 'name': 'Motor'}, 'B': {'typeid': 63, 'connected': True, 'name': 'ForceSensor'}, 'C': {'typeid': 62, 'connected': True, 'name': 'DistanceSensor'}, 'D': {'typeid': -1, 'connected': False, 'name': 'Disconnected'}}
Any hints?

Could everyone tell me what PSU you're using please with the buildhat? I had issues with the lights when using USB-C PSU, but with my own barrel jack PSU, they do work for me.

I am using the official PSU: https://www.raspberrypi.com/products/build-hat-power-supply/.

Thanks, do you mind telling me where you bought the light from? (Just wondering if there maybe more than one version)

From the official Lego online shop.

Lego support tells me, that the product will be available at the end of january. I ordered a replacement in december 2021 for the supposedly defect component.

Official 8V 6A RPi PSU

Also bought the light from lego.com

Thanks all, just ordered some from lego.com to have a look at

Thanks, do you mind telling me where you bought the light from? (Just wondering if there is maybe more than one version) I will see if I could possibly order one from the seller someone here used, to do some more debugging.

From the local lego store - cologne; germany. See attached the bag ...

Official 8V 6A RPi PSU

I am using the official PSU: https://www.raspberrypi.com/products/build-hat-power-supply/.

Same here.

Any news on this?

P0: connected to passive ID 8
Shows up and works with the Light class!
Can you set the brightness levels like you can on the Spike hub?

@mutesplash sure, just added a brightness function:
import time
from buildhat import Light

l = Light('A')
bright = 0
step = 1
while True:
    l.brightness(bright)
    bright += step
    if bright == 100 or bright == 0:
        step *= -1
    time.sleep(0.01)

It uses 0 - 100 for consistency with the brightness on the distance sensor.

I will try to test it tomorrow.
Thanks in advance.

It's working. Great work and thanks again. 👍

@Niwa1980 @joerk Does this work for you? Great success over here!

Yes! Take me some time to setup the local build env. Now I'm prepared for deep dive ;-) Regards Joerk


fix compilation failure with -g flag in substrate integration

This PR fixes compilation error when inserting the -g flag in Substrate integration tests

You've left in a comment which nicely demonstrates the problem.
println!("NEW IS CALLED WITH FILENAME {filename} and NAME: {name}");

The output contains:
NEW IS CALLED WITH FILENAME create_contract.sol and NAME: child
NEW IS CALLED WITH FILENAME runtime_errors.sol and NAME: child

Both these contracts define the contract child. One of those should be renamed.

 One of those should be renamed.

I suspect that the tests pass because it's being compiled with gnu parallel. The test in runtime_errors.sol expect the create_child to fail, however the one in create_contract.sol must be right. So, depending on which gets compiled first this might work or not work.

That is a good finding @seanyoung, I created #1228 to prevent this in the future (can also be enabled for solana integration tests). The CI in this PR should fail now, I'm currently just waiting to check and will then fix the conflicting names in that PR too

Thanks @xermicus , I will change the conflicting names in this PR myself

Very nice, thanks

@salaheldinsoliman the substrate tests fails with:

  33 passing (10s)
  1 pending
  1 failing

  1) Deploy runtime_errors.sol and test the debug buffer
       logs errors to the debug buffer:
     Error: ENOENT: no such file or directory, open 'child.contract'
      at Object.openSync (fs.js:498:3)
      at Object.readFileSync (fs.js:394:35)
      at deploy (index.js:30:39)
      at Context.<anonymous> (runtime_errors.spec.ts:25:42)

The CI tests then doesn't exit, so the test gets cancelled or it timed out

Fixed, thanks


Cache Driver Backups

Description
If our application is unable to connect to Redis, a CriticalError exception is now thrown.
CacheFactory catches the CriticalError exceptions that are thrown when Redis, Memcache and Predis fail to connect, it logs the exception and then attempts to initialize the backup cache driver (and if that fails it initializes dummy).
Checklist:

[ ] Securely signed commits
[ ] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

Hi, just some additional information regarding the pull request.
It's my first time attempting to contribute to an open source project, so apologies if i have missed anything.
I noticed, what i would call an issue with the current version of CI4, when i purposely mis-configured the connection to my Redis server to simulate what would happen if my Redis server went down, the issue was that the whole application would just stop, due to a RedisException been thrown.
I felt that this should be improved, and if the primary cache doesn't work, we should attempt to use the secondary cache, and if that doesn't work, don't use any cache. I feel like this is a better solution than the application no longer working until someone is able to fix the cache.

It sounded like a good addition. Why did you close it? I am out of town and haven’t had a chance to review it yet.

Insecurity of my abilities...
I've been spending the majority of today (4 hours so far) trying to figure out what is going on with the build (I've never used CI before, so I'm learning a lot which I'm quite enjoying).
My current plan is to get a build that passes the tests and also be able to tick off the checklist, then to reopen the pull request.


chore: Allow config path override via command line

coverage: 80.36% (+0.03%) from 80.328%
when pulling 49fa0664acec08a2d875b4b079104cf862efd20b on chore/allow-config-path-via-command-line
into aa3b2fe5a9c0c7584d5ed2e3ad5129742bb44926 on develop.


Projection with _id returns all fields

Versions
commit.txt: a06bd4bf1832bceed7189cff07d788cdb11e2155
version.txt: v0.9.4-1-ga06bd4bf
What did you do?
See repro in #2298.
What did you expect to see?
2 documents returned with just the _id field.
What did you see instead?
All fields.
Environment
- OS: Ubuntu
- Architecture: x86_64
- Version: 22.10
- Go: go version go1.20 linux/amd64
- Git: 2.37.2
- Deployment: Docker
- Deployment details: 23.0.1

See repro in https://github.com/FerretDB/FerretDB/pull/2298.

That PR should be re-opened and updated to check that this issue is indeed fixed


[FLINK-3446] [runtime-web] Don't trigger back pressure sample for archived job

Sampling a back pressure sample when the job has been archived, lead to a NPE being thrown as reported by @rmetzger. Fix is pretty straight forward, waiting for Travis...

Merging this


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

As per exercise instructions the correction made to the validations.py script was set to merge with the base branch


feat: prepHumanModelForftINIT with paths

This PR fixes issue #401 and now allows for specifying the paths to the tasks and reactions.tsv. This is good when using the code for for example Mouse-GEM.
Main improvements in this PR:
prepHumanModelForftINIT supports other models such as Mouse-GEM - the paths to relevant files could not be specified earlier.
I hereby confirm that I have:

[X] Tested my code on my own computer for running the model
[X] Selected develop as a target branch

@haowang-bioinfo @mihai-sysbio Could someone of you review this so I can merge it? It is a small change that makes it possible to run ftINIT properly for Mouse-GEM and similar GEMs.

Hi Mihail Although you have a point, I request that we keep it as it is :) The main reason is that we otherwise break the interface, which for example will stop the code we just submitted for the single-cell modeling paper from working. I also have the argument that I don't think all users will know what a task list is, where to find it etc., and that having to supply these params makes using the function unnecessarily difficult - the first time I used tINIT I didn't know what the task file was and where to find it. The whole code around ftINIT in Human-GEM has that only purpose, to make it easier to use ftINIT - the code is not really needed in that sense, it is just a fairly simple wrapper that removes some normally unwanted reactions and fills in some standard values, such as the path to the task file. The reason for this fix is that I didn't think of the case with the mouse model, and that is why these params are needed.

The main reason is that we otherwise break the interface, which for example will stop the code we just submitted for the single-cell modeling paper from working.

This PR is to the develop branch, which I hope was not referenced in the submission. So it would only become problematic if it gets to main. Another option would be to keep this PR on hold for a few months.

I also have the argument that I don't think all users will know what a task list is, where to find it etc., and that having to supply these params makes using the function unnecessarily difficult - the first time I used tINIT I didn't know what the task file was and where to find it.

This is an important concern. My approach would be to solve this with improved documentation, by continuing to maintain the Human-GEM-guide.

The whole code around ftINIT in Human-GEM has that only purpose, to make it easier to use ftINIT - the code is not really needed in that sense, it is just a fairly simple wrapper that removes some normally unwanted reactions and fills in some standard values, such as the path to the task file.

We are on the same page here. My approach is not to simplify things towards a magical one command that does everything, but to be very clear about what each command will do.

The reason for this fix is that I didn't think of the case with the mouse model, and that is why these params are needed.

Now that this branch exists, it can be used even without merging.

I think you have a point, when I think of it the main concern would be that there is a substantial risk that people now will use the mouse model with another reactions.tsv.

For the Mouse model, when using the Mouse-GEM reactions.tsv, should people be running prepHumanModelForftINIT on Human-GEM or on Mouse-GEM?
And should consider adding an ftINIT page for how to use it with other models, say Mouse-GEM?

So, they should use it with Mouse-GEM, and with that reactions.tsv, although it probably doesn't matter. But using the right model is important.


Update help.md

Could we push this into test please?

What's the most efficient? We can test with the temporary url and if changes are needed, we can update the existing PR.
If we push this PR to test and changes are needed, we create a new PR.
I'm open to whatever is the best approach for text changes.

The temporary url is by far more efficient. It will generate the project in the Dev environment, which for text updates is enough to see the changes. Then if there are any edits to the PR required, you can simply push more changes and generate the temporary url again. Pushing this into the Test environment would require redeploying the Test environment and a new PR each edit.
To generate the temporary url, you can comment /gcbrun, and in a few minutes the link will be created.

/gcburn

/gcbrun

/gcbrun

/gcbrun


XML documentation missing on derived fields

This bug was introduced between rc6 and rc7, I suspect this commit c8faf5efe447da880327c23ae729c39526bb334e
public class A
{
  /// <summary>Bla bla</summary>
  public string Foo { get; set; }
}

public class B : A
{
}

The documentation for foo will not be output on B

found it:
https://github.com/ChilliCream/hotchocolate/commit/c8faf5efe447da880327c23ae729c39526bb334e#diff-dd209d2b6cd474e7b7a36cf53c371fe841c7d8f6076f86b4a3f1acf106fa5042

OK, fixed it.


Implement the beginning of the ModManager Class

ModManager needs to be able to interact with the nlp module.
With this functioning, the c++ core will be able to utilize the python nlp module, connecting the two sections of this program.
To complete this issue, ModManager should be setup so that Engine can call the nlp functions via the ModManager (which calls the appropriate nlp functions from nlp). This delegation will allow all c++ to python integration to take place in only one location for now (ModManager).

I should be able to get this set tomorrow. Leave this to me for now, I don't want to accidentally cause a rough merge conflict between two drastically different implementations.
Once this is up and running, we will need to recreate all of the nlp tests that ran via pytest using a c++ unit test library. This will be it's own issue that I can make, once I have finished with this one. But this is an important step for giving us confidence that the nlp module can properly be called by the Engine.

Part 2 will be completed tomorrow and will require review before merge.


[Missing SNMP Polling Profile] Mellanox SN2700/SN2010

Device Vendor: Mellanox
Device Model: SN2700/SN2010
System Object Identifier (SysOID):
List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations):

Performance Metrics
Interface Metrics
Traffic/Packets/Bandwidth Metrics
Environmental Data

Please provide a public gist with a sanitized (sensitive information removed) SNMP walk of the device. Providing MIB files is not a substitute for an SNMP walk and failure to provide one here will result in delays for closing this issue. The output of these commands shows the "true story" of what a device will respond to in SNMP and is used to ensure that our profiles are efficient and accurate for your devices.
Gist Link: https://gist.github.com/roostergr/44214183eb5b179b37b42c3b3d365cf7

Example SNMP walk commands:
# v2c example
snmpwalk -v 2c -On -c $COMMUNITY_STRING $IP_ADDRESS . >> snmp_walk.out

# v3 example
snmpwalk -v3 -l authPriv -u $USERNAME -a MD5|SHA -A $AUTH_PASS -x DES|AES -X $PRIV_PASS -ObentU -Cc $IP_ADDRESS . >> snmp_walk.out

@roostergr - can you please confirm the walk on this one? The output has ~10,500 rows, but ends at the BRIDGE-MIB with the .<IP_ADDRESS>.2.1.17 root. We'd expect a lot more; the IF-MIB root (where all the interface statistics live) is .<IP_ADDRESS>.2.1.31 for instance.
That's pretty common when a device has a timeout on the walk, you might try again with an additional timeout parameter on the walk command:
snmpwalk -v 2c -t 10 -On -c $COMMUNITY_STRING $IP_ADDRESS . >> snmp_walk.out

@thezackm sending the new walk on your email :)