fix: allow deployment in scripting

What :computer:

This PR fixes an issue with deploying contracts from scripts

Evidence :camera:
Include screenshots, screen recordings, or console output here demonstrating that your changes work as intended

Notes :memo:

[ ] An issue still exists regarding the nonce in use which prevents transactions from being executed succesfully

I'm able to broadcast successfully with the default address. Had nonce issue with using one of the rich accounts, not sure if perhaps we are missing something in the script setup/env specific for this case (in the script code itself)

@Karrq can you update the output:
Estimated gas price: 3.2 gwei

To reflect the provider gas price.


cache issue on iOS 8 ?

Hi guys,
Is there an issue for caching on 8.x ?
this:
public func URLSession(
            session: NSURLSession,
            dataTask: NSURLSessionDataTask,
            willCacheResponse proposedResponse: NSCachedURLResponse,
            completionHandler: ((NSCachedURLResponse?) -> Void))
        {
            if let dataTaskWillCacheResponse = dataTaskWillCacheResponse {
                completionHandler(dataTaskWillCacheResponse(session, dataTask, proposedResponse))
            } else if let delegate = self[dataTask] as? Request.DataTaskDelegate {
                delegate.URLSession(
                    session,
                    dataTask: dataTask,
                    willCacheResponse: proposedResponse,
                    completionHandler: completionHandler
                )
            } else {
                completionHandler(proposedResponse)
            }
        }

is never called in iOS 8.X but it's is in iOS 9.X...i have nothing in my code to differentiate iOS 8 and 9 (maybe that's the issue)
I'm currently on Alamofire 3.2.1 maybe the 3.3 fixed the issue but i didn't to go to swift 2.2 right now..
Thanks for future answers

Hmmmm....we'll need to look into this @Mycose. Is there any chance you could put together a failing test to demonstrate the issue? That would make it much easier for us to troubleshoot.

Sure but do you have any idea how i can demonstrate the issue ?
I dont have any error in the logs, it's just that the cache worked on iOS 9 and not iOS 8

Thanks for all the info you provided here.
We have a fairly large set of CacheTests to help verify this type of behavior. If you open up the test suite and run this test on iOS 8.x or iOS 9.x and set a breakpoint in the URLSession(_:dataTask:willCacheResponse:completionHandler:) method, you'll see that the breakpoint is being called each time.
I then added your delegate.dataTaskWillCacheResponse override to the test's manager and re-ran. Both the delegate method and the override closure are being called as expected.
The only difference may be that I'm running Alamofire 3.3.1 and you are running 3.2.1. We have made some changes in the 3.3.1 release that fixed some bugs around some of the delegate methods being called, but this particular session delegate method should not have been affected. Additionally, the bugs there should have only affected the 3.3.0 release, not the 3.2.1 release. Either way, I'd encourage you to dig into the tests that I've linked in this comment to see the behavior working for yourself. Then I would update to 3.3.1 and see if that fixes your issue.
If 3.3.1 does not fix your issue, then you'll need to figure out why your logic is different than the logic in the tests. I don't see anything obvious from the code you posted, but that doesn't mean that you don't have something else set that is affecting the behavior that isn't in your example.
At this point, I don't see an issue in Alamofire. All the behavior you've reported is not working seems to be working correctly from what I can tell. Because of this, I'm going to close this issue out for now. If you do still continue to have issues, then please provide a failing test or sample project for us and attach it to this issue. Then we'll gladly re-open the issue and continue to help you investigate further.
Best of luck! 🍻

Hello, thanks for the link to tests, really great
I tried and check a lot with the test to so what the problem was. The test are working great with iOS 8 and 9 so it's not coming from here. So i just the problem is coming from the fact that my response has nothing about cache in the headers
Since i can't touch the server i did a fix by stocking in the NSSharedCache manually the response and it's working ^^

Cool...thanks for the update!


Improve implementation of blacklist

For #59.

Codecov Report

Merging #64 (b8b8d54) into master (69d7c5a) will decrease coverage by 0.04%.
The diff coverage is 16.66%.

@@             Coverage Diff              @@
##             master      #64      +/-   ##
============================================
- Coverage     70.81%   70.77%   -0.05%
- Complexity      506      507       +1
============================================
  Files            87       87
  Lines          1631     1632       +1
  Branches        172      171       -1
============================================
  Hits           1155     1155
- Misses          417      418       +1
  Partials         59       59

Impacted Files
Coverage Δ
Complexity Δ

...seedu/address/logic/commands/BlacklistCommand.java
44.44% <0.00%> (+6.34%)
7.00 <0.00> (+1.00)

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)
1.00 <0.00> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
96.07% <0.00%> (-3.93%)
24.00 <0.00> (ø)

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...c/main/java/seedu/address/model/person/Person.java
90.14% <25.00%> (-3.98%)
23.00 <1.00> (ø)

...ain/java/seedu/address/model/person/Blacklist.java
80.00% <66.66%> (-12.31%)
8.00 <1.00> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 69d7c5a...b8b8d54. Read the comment docs.


bypass dont work

Domain
https://li.web.tr/
Link
https://li.web.tr/gSt9vtBn
Version
end
What browsers are you seeing the problem on?
Chrome
What OS are you seeing the problem on?
Windows
Anything else?
dont skipped

This was working for me.


[Automated] Fix misspellings

Produced via:
export FILES=( $(find . -type f -not -path './vendor/*' -not -path './third_party/*' -not -path './.git/*') )
misspell -w "${FILES[@]}"

Cron. -knative-prow-robot
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads

@evankanderson I thought you have removed the spelling checking for manifests?

@evankanderson I thought you have removed the spelling checking for manifests?


Run Cosmos tests for PRs

Fix some deadlocks in Cosmos Test cleanup by converting sync invocations to async

Were Cosmos.FunctionalTests were supposed to run in this PR? Linux log showed all of them skipped.

@smitpatel I think that's a reporting issue. I can see activity on the Cosmos account.

Fixed


Visual glitch / focus issue with keyboard and Crosswalk

Here we go, this issue has been there for a while and I still haven't seen any solution or attention to it.
The problem is that the whole app view seems to jump/jerk a bit when you tap on an input field or unfocus one.
It is only reproducible with Crosswalk and on an Android device.
To see the problem, create a "blank" template project and add Crosswalk, then add the following in the ion-content section:
<div class="list">
  <label class="item item-input">
    <input type="text" placeholder="First Name">
  </label>
  <label class="item item-input">
    <input type="text" placeholder="Last Name">
  </label>
  <label class="item item-input">
    <textarea placeholder="Comments"></textarea>
  </label>
</div>

Then build / install on an Android device. Try to tap on any input, then out, in, out, you'll notice the issue. Pretty ugly.
I made an APK in case you want to try it directly: http://1drv.ms/1I48X0A
My system information:
Cordova CLI: 5.0.0
Gulp version:  CLI version 3.8.11
Gulp local:   Local version 3.8.11
Ionic Version: 1.0.0
Ionic CLI Version: 1.4.5
Ionic App Lib Version: 0.0.22
ios-deploy version: 1.7.0
ios-sim version: 3.1.1
OS: Mac OS X Yosemite
Node Version: v0.12.4
Xcode version: Xcode 6.3.2 Build version 6D2105
Installed browsers:
For android - crosswalk 12.41.296.5

I am trying to reproduce this issue, but I do not quite understand the phenomenon maybe cause by I couldn't reproduce it. Then I intend to try your apk, but fail to download it since my poor network, could you please share it from another place easier to access?

Yes, the file is about 23MB since Crosswalk is bundled in. While there is nothing I can do about its size or your internet connection you may want to try to download the same from an another download location that I just made available to you:
https://www.dropbox.com/s/lbo6j3c6d7vsjji/kb-problem-debug-unaligned.apk?dl=1
Alternatively you can try to recreate and build the app locally on your computer as I explained in the main description of this issue.

@mhartington Could you please at least reproduce/confirm the issue?

Fortunately, I succeed to download your apk, but cannot find any abnormity when tapping on the input, then out, in, out...
My device is Nexus 5(Android 4.4.2)

See video recoding of the issue here: https://youtu.be/XPDd-ZFIE4k

Hmm, alright seeing this as well. I'll let @tlancina take a look at this.

I can reproduce it now by rotating the screen, I suppose the fix from Crosswalk Webview plugin: https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview/pull/32/ would be helpful since I couldn't reproduce it after applying the patch.
@zarko-tg, could you have a try?

@Honry I just applied that fix and it seems to have resolved the issue for me too

Yep, it seems to solve the issue.
Looking forward to a conclusion on the pull request by @Nielsb85.

I attempted to apply the CrossWalk patch but am still seeing the jump/jerk issue. Can anyone please detail the steps in applying the patch?
Thank you.

Is this still an issue?

A fix was made and taken further within Crosswalk. Thus I'm closing this thread.

@zarko-tg sorry I'm not sure to understand everything with multiple fork, issue, jira but with fresh cordova, crosswalk, ionic I have this glitch yet. And you ?

So @spirylics, pesonally I have patched on of the Crosswalk files locally on my developer machine. Their integration and release procedures are an enigma to me, so I have no idea how or when will their fix arrive. Asking within their Jira case might help you if patching is not an option. I just couldn't afford to wait is the problem has been there for months.

Thanks @zarko-tg

Update / to @spirylics:
The latest version of cordova-plugin-crosswalk-webview is out now (ver. 1.3.1). Among few small changes it configures the ANIMATABLE_XWALK_VIEW preference to false by default. Which is basically the fix for this GitHub issue.
https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview

Thanks @zarko-tg , I tested and it works fine !


Use code blocks for the AND and OR examples

This should make it less likely for the example to break across multiple lines, plus it matches nicer with the other examples in this section 😁
Before:

After:

Agreed! Merging!
Thank you!


Affine transform of RGB image

Hello! Do you have any idea why this basic translation matrix is affecting each channel of an RGB image differently?
img = jp.array(PIL.Image.open('test.png').convert('RGB')) / 255.
print(img.shape)
tx = 100.
ty = 0.
translate_matrix = jp.array([
    [1,0,ty],
    [0,1,tx],
    [0,0,1],
])

t_img = pix.affine_transform(img,translate_matrix,mode="constant")
plt.imshow(t_img)

Screenshot of output:

Hi @jloganolson, thanks for reporting this!
Looks a bit strange to me 🤔 I'm looping in @pabloduque0 for this. He might be away atm, but we'll take care to have a look at this asap.

Thanks! Examples like this in the documentation or comments for translate, rotate, shear, and scale would be super-useful (and would have saved me quite a bit of time).  Bonus: an example of combining them, e.g. should I do translation_matrix @ rotation_matrix.T?

Yes, you can indeed combine transformation matrices (with .dot or @ but no need to transpose). Bare in mind that this is a plain affine_transform so would need to adjust such matrix if you want the original input "centered" after combining a set of transformations (see an example from TF) if that is what you want.
Yes, we can add maybe examples for the different transformations somewhere.

Hello @jloganolson !
We updated the documentation with a few basic examples for different transformations.
Hope that helps!

That's awesome - I ended up just brute force learning it but I'm sure this well help the next person who travels this way.

Thanks @pabloduque0 for the PR and thanks @jloganolson for flagging this!
As this is now clarified and https://github.com/deepmind/dm_pix/pull/51 is merged, I'm closing this issue :smile:


UUID encoded canonical output incorrectly uses upper case characters

We've noticed collisions between UUID's (v4) generated by ID128 and other UUID generation tools in our stack. Namely in that when converting ULID <-> UUID ID128 pushes out the encoded UUID in uppercase whereas every other library we use (namely in python) encodes them in lower case.
Looking into this it seems that the specification states encoded strings should be lowercase:
https://datatracker.ietf.org/doc/html/rfc4122#:~:text=The hexadecimal values "a" through "f" are output as
      lower case characters and are case insensitive on input.
I am not an expert in this area but from reading this it suggests that the library is incorrect, albeit it's a relatively minor issue, to encode to upper case?

It's not entirely obvious if that is a formal requirement of UUID or just a way to make a UUID conform to a URN.  Further along it mentions the grammar, which includes both upper and lower hex digits.  I will do a bit more research to see if there's consistency across languages or other major libraries.  If so, i'll likely add the fix to the next major release since others may rely on the lowercasing (Hyrum's Law).  In the meantime, it should always be safe to parse into a UUID and compare the objects or to ensure consisting casing in your own application if you're going to only compare strings.

I am happy to do a PR to make the change if you decide it is the correct approach.

a few resources seem to agree with you:

https://www.postgresql.org/docs/current/datatype-uuid.html
https://www.uuidtools.com/what-is-uuid

next major version will do:

hex format: upper case
uuid format: lowercase

i think i'm also going to add a fromSql/toSql function since that came up in another issue

@aarondcohen would you appreciate a contribution to fix this issue? Or anything else we can do to help 🙏 ?

i'll try to address this during the upcoming winter break.


B19: Can not start theory

After up to B19, several theories ended correctly in Research Table, but new ones can not be started (maybe it not the cause of the version, but before (B17) everything was fine). Click on the question mark on the page does not lead to any reaction. "Scrap" does not give anything.
Sorry. I can't upload the screenshot because of the GitHub problem, in multiple browsers :(

Do you have enough ink and paper? Have you tried removing the table and replacing it?


Informal benchmarking

The "is it worth it" thread.  Informal benchmarks:
macOS process implementation: 10000 reps of getProcesses() with ~500 processes.

OSHI avg: 38.26 ms
OSHI-FFM avg: 7.23 ms (5.3 x faster)
OSHI parallel avg: 10.23 ms
OSHI-FFM parallel avg: 2.35 ms (4.4 x faster)

wait that's pretty fast! would it be useful to create a triggerable benchmark workflow that pulls oshi as well as oshi ffm and runs on both just for logging?

Note the “informal” in the title. :)
Not sure how useful a formal benchmark would be.  Too many variables.  Feel free to try if you want.


[Remote Store] Delete merged away segments in periodic flow

Signed-off-by: Sachin Kale<EMAIL_ADDRESS>Description
In this change, merged away segments are deleted from the remote segment store in async periodic flow. This will help in not blocking the refresh flow unnecessarily.
To achieve this:

After each refresh, we create and upload a metadata file namedremote_segments_metadata to remote segment store.
remote_segments_metadata keeps track of list of segment files at the time of refresh along with metadata including file length, checksum etc.
A periodic thread reads deletes files that are not part of local directory or remote_segments_metadata.

Issues Resolved

https://github.com/opensearch-project/OpenSearch/issues/3142

Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

IMO, this change adds a lot of complexity to the refresh listener. If it really provides a performance improvement, we can include it. Until we get the perf results, putting it in draft mode.

@sachinpkale : Are you still working on this ?

@sachinpkale Closing this PR as it hasn't been worked on in a while. Please feel free to re-open it if you are still working on it.


--raw-tcp/--rawtcp functionality removed

It appears that support for --raw-tcp (apparently now possibly renamed to  --rawtcp) was removed in commit fbaade429845546d751110caa0f886f7b1a62717 citing a move to "explicit control" instead. As far as I can tell it was just removed without a replacement. Was this intentional and, if so, is there any plan to re-add something like it?
Understandably it's difficult to definitely say whether something is raw TCP vs. HTTP but you could check against standard HTTP verbs and fallback to TCP if they're not found.

As far as I understand this commit, only a "automatic detection heuristic" for raw-tcp mode was removed.
RawTCPLayer should still be usable via this and this.

I fully agree that the functionality of --raw-tcp can be partially recreated using --tcp and --ignore but both of those assume that you you know the remote host ahead of time, which is a big assumption. Regardless of what parts can be partially recreated, the program's --help shows --raw-tcp as a valid flag, albeit experimental.
I'm happy to submit a PR that either removes the flag or re-adds a slightly improved heuristic; I think people would prefer having the functionality vs. not.

Let's see what @cortesi has to say, since he originally removed this functionality. I'm fine with both.
/cc @mhils

I think it's generally useful (at least it was to me), but at the same time needs to stay off-by-default when reintroduced.

Due to the determination of RawTCP fallback vs HTTP being iffy at best, I'm with you that it should definitely be off by default.  Is it worth doing a PR to try to re-add it?

Hi @caligato - thanks for triggering a discussion here. Let's see if we can work out how to proceed.
I'd prefer to keep this type of frankly dangerous heuristic out of the codebase if we can, even behind a switch. As the commit says, lets see if we can accomplish the same things in a more explicit fashion. @Caligatio, would you mind telling us about your use-case, please? Could switching based on destination port/host work for you, for instance?
If we find that a hot heuristic is the only approach that works, I'd like to do it properly. That means:

A better name than "rawtcp"
Sound documentation for what this does and how it works
A more sophisticated heuristic than just checking if the first 3 bytes are ASCII
Finally, this belongs in an addon. We should extend the event mechanism to make protocol switching for this sort of use-case possible (and in fact much of the functionality from root_context.py should also move over).

I basically want to blindly send all TCP connections from a particular host (a VM) through mitmproxy to be able to dump the (pre-)master secrets on all TLS connections for later analysis.  I don't know anything about the traffic leaving the VM beforehand so unfortunately port/host filtering/switching doesn't help me much.
My proposed "slightly improved" heuristic would be to replace the previous ASCII check with a peek at the first 7 bytes and do a comparison whether those bytes are a HTTP verb.  Why 7 bytes? It's the length of the longest standard HTTP verb and, since we're going to fallback to HTTP anyways, every HTTP request should have at least 14 bytes (e.g. "GET / HTTP/1.1").  If it matches against a HTTP verb, fallback to HTTP processing like is done now; if it's not a HTTP verb, process it as a RawTCPLayer.
I'm definitely not wedded to the name "rawtcp" but it does kind of get the point across.  Maybe something like "--generic-tcp-proxy" or "--fallback-tcp-proxy" with some appropriate documentation on what it does and its shortcomings?

So, in your scenario you don't actually care about having plain HTTP interpreted as HTTP - you'd be happy if we just forwarded all non-TLS connections through as TCP, is that correct? This would let you pick out the details you need from TLS connections, and everything else just flows through the proxy as a stream.
If that's the case, we don't need the gnarly heuristic at all in your case, we just need to be able to switch the default protocol interpretation from HTTP to RawTCP, which is a much simpler and more consistent piece of functionality.

It would helpful to keep future possibilities open with regards to treating HTTP special and keeping flow scripting.  If absolutely necessary I could chain mitmproxies together, one for TLS dumping and one for HTTP modification, but that's a bit ugly.

Right. Let's do this:

Re-add rawtcp that unambiguously does what it says on the tin, without heuristics (i.e. the default protocol is raw TCP rather than HTTP). This is a two-line patch here, and I'll happily merge it immediately to get you under way.
I'll make sure that we're still flexible by letting an addon hook perform protocol switching. That way addons can arbitrarily switch the protocol on a per-connection basis in whatever way they like so we can safely experiment with heuristics. I'd be happy to have an "autodetect_protocol" addon in core on this basis too.

Ok, so the patch would kick out to RawTCP and then it would be up to an add-on to do HTTP1 identification? Would one do some next_layer hooks like the tls_passthrough.py example except trigger on next_layer being RawTCP?

Yes, that's right. I'd like to sit down and look at that particular part of the addon API to make sure it's consistent and caters for all of these use cases. In fact, I'd like to be able to move the protocol switching mechanism entirely into a built-in addon.

Caveating that I'm not an add-on expert, I think that sounds reasonable. I would make a passing comment though that RawTCP seems like a semi-confusing name as I would think it's the top layer, not necessarily something that could be under TLS and a sibling of HTTP. If you'd be willing to rename it, something like RawPayload might make more sense.
Hopefully last question =) Since I'll be using an add-on to do HTTP1 identification,  can you chain multiple add-ons together using the  add-ons=[] syntax? Looking at the examples, it appears only one is ever used (note I'm on my phone right now so may have missed an example where that is not the case).
Regardless, thank you for the quick replies and help!

We'll workshop the name a bit. There are some variations we can play with - maybe "passthrough"? I actually think rawtcp is reasonable if the functionality is unambiguously to set the default protocol
to raw tcp.
Yes, you can chain together addons. A big drive for me in the next few days is to firm up the addons documentation, and I'll make sure I add something explaining how this works.

Sorry for being unclear, I meant RawTCP as a protocol class name, not as a flag name.  I'm guessing changing the name of RawTCP may break a lot of downstream stuff and probably it's worth doing.

Just a quick note regarding fancy heuristics and HTTP/2:
The first bytes a client sends are PRI * HTTP/2.0\r\n\r\nSM\r\n\r\n.
Not your typical HTTP verb first line, so please be careful.

@Kriechi To be clear, the current logic is something like "try a bunch of tests, default to HTTP1" whereas what we're proposing is "try a bunch of tests, if flag set, go with RawTCP, if flag not set, use HTTP1."  This particular patch/idea doesn't hurt the current situation at all.
I'm trying to read up on TLS/ALPN and HTTP2.  It appears HTTP2 should use TLS and most browsers require TLS to use HTTP2.  Additionally, it appears most browsers implement ALPN.  I realize there are a lot of mosts/shoulds in that sentence but what it means is that the ALPN check should pick up HTTP2 most of the time.

You are right - at the moment mitmproxy only supports HTTP/2 with TLS+ALPN.
So we should be good!

Re-add rawtcp that unambiguously does what it says on the tin, without heuristics (i.e. the default protocol is raw TCP rather than HTTP).

This can already be achieved by --tcp .* or --ignore .*. I don't think it's useful to have a second flag for this.

Yes, that's right. I'd like to sit down and look at that particular part of the addon API to make sure it's consistent and caters for all of these use cases. In fact, I'd like to be able to move the protocol switching mechanism entirely into a built-in addon.

Yes - protocol switching is something that we definitely need to solve properly, especially in the light of sans-io. The problem is a bit more generic than what's mentioned here (see e.g. https://github.com/mitmproxy/mitmproxy/issues/1774), so I propose we move that to a new issue. I'm all in for having addons being able to decide, we also already do that in examples/complex/tls_passthrough for example.
fbaade4 only removed the actual logic, but not the option or the command line argument. I opened https://github.com/mitmproxy/mitmproxy/pull/2499 to temporarily re-add rawtcp mode, until a more refined solution is implemented (see 9ca6785d40ebe0293f36683250d72998f438bba9 for more details on this).


Broken link for APIM 4.1.0 Overview documentation

Description:
When we search WSO2 APIM in google and if we click the Overview - WSO2 API Manager Documentation 4.1.0 it gives a page not found error.

Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

All 4.0.x links are now redirected to their respective pages in the latest documentation. Closing this as a result.


Misc fixes

This PR contains a bunch of smaller fixes and improvements for stuff which I recently stumbled over and which are IMO not enough to open a pull request on their own. Probably the change with most potential for controversy is 298d2c8718ed74e7fb378d156c2f26b7738d5b29, which causes the list tool to treat signal.{initial,invalid,minimum,maximum} as physical values. (The ARXML loader has been doing this for quite some time by now, the other formats will hopefully be switched to using physical quantities for all user-facing values soon.)
Andreas Lauser<EMAIL_ADDRESS>on behalf of MBition GmbH.
Provider Information

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

35 of 41 (85.37%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 94.072%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cantools/subparsers/list.py
26
28
92.86%

cantools/database/can/formats/arxml/system_loader.py
9
13
69.23%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
7046

Relevant Lines:
7490

💛  - Coveralls

@zariiii9003 or @juleq: can you have a look at this? For this PR I recommend looking at the patches individually as they are all pretty small and should be self-contained. (in principle, each of them could be done as a separate PR...)

Yes, i wanted to get #536 merged first, i'll get that done today, i think.


Fix for cron resource get confused by environement/property mismatch

Added a warning in case user is using a environment for an entry that can also be specified as a property
Added unit test cases
Ensured chefstyle

Signed-off-by: vijaymmali1990<EMAIL_ADDRESS>Description
When we use environment for an entry that can also be specified as a property i.e. :SHELL :PATH :MAILTO :HOME it causes idempotency issues. Added a warning as idempotency in this case cannot be maintained.
Issues Resolved
Fixes #8241
Check List

[x] New functionality includes tests
[x] All tests pass
[ ] RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Do we need to change the docs for cron resource.

In cron_different? we compare all the properties (f.k.a. attributes) of the current resource with the new resource.
If we have this resource:
cron 'noop' do
  hour '5'
  minute '0'
  command '/bin/true'
  environment({'MAILTO' =><EMAIL_ADDRESS>end

If that cron entry already exists, when we read it we will set the mailto property for current_resource in set_environment_var.
However the mailto property for new_resource will be empty, because the user didn't specify it.
So cron_different? will return true and we will run the action.
The solution to this (99% sure) is to make sure we parse the special variables out of the environment property before/in  cron_different?. Which would look something like this:
  ENVIRONMENT_PROPERTIES = %w{MAILTO PATH SHELL HOME}.freeze

      def cron_different?
        new_resource.environment.each do |name, value|
          if ENVIRONMENT_PROPERTIES.include?(name)
            unless new_resource.property_is_set?(name)
              logger.warn("#{new_resource.name}: the environment property contains the '#{name}' variable, which should be set separately as a property.")
              new_resource.send(name.downcase.to_sym, attr_value.gsub(/^"|"$/, ""))
              new_resource.environment.delete(name)
            else
              raise Chef::Exceptions::Cron, "#{new_resource.name}: the '{name}' property is set and environment property also contains the '#{name}' variable. Remove the variable from the environment property."
            end
          end
        end

        CRON_ATTRIBUTES.any? do |cron_var|
          new_resource.send(cron_var) != current_resource.send(cron_var)
        end
      end

@btm yes we had a thought upon it and yesterday we needed to discuss with you this thing only. Anyways Thank you!
Will test it around and update!

Fixed in #8455


adding second timestamp filter break the enlarged state

step to reproduce:

load any dataset with 2 timestamp column
add a filter on one time
add a filter on the other time

now 2 filters both mark themselves as enlarged internally. but only the first filter is used in the large panel.
if you click to show the second filter, it will hide the enlarged filter instead of switching to the second.

after fixing it in #93, I find more issues that might cause this test case to still not working.
just added another fix in #100


Attachment helper for base64 encoding

We have an example in USE_CASES.md on how to handle attachments.
We need to update the Attachment object such that it can also take in a raw file, rather than a base64 encoded file, and perform the base64 encoding behind the scenes.
Note that the total size of your email, including attachments, must be less than 30MB. The total size is calculated from the entire JSON payload. Note that you will need to handle the case where UTF-8 characters are included.

Hi @thinkingserious, I'm working in this one right now.

See this gist, based on it, which approach do you think suits better here sample1 (read the entire file) or sample2 (read chunks)?
I'm doing this to be synchronous, is it ok?

Hi @spelcaster,
Thanks for the PR, I've added to my backlog for review. My initial thoughts is that it may be useful to provide configurable options to the user with a good default.
That said, @adamreisnz may weigh in before I get a chance to.
With Best Regards,
Elmer

I think that the simpler approach of reading the whole file makes sense here, because it's a helper, and for 98% of the use cases where someone just wants to include a file, it will work. With the email size limit being 30mb anyway, it's unlikely one will try to read files larger than that which would not fit in memory.
For cases where it causes problems, developers could roll their own solution and provide a buffer instead of a file.
With the configuration option and two ways of doing it I think you may run the risk of over complicating things for no real good reason, and it's possible that the chunked way of reading may still not suite everyone's needs.
That's why I think it's best to provide a simple solution that just works in most cases, while giving developers the option to build something themselves. Accepting buffers already does the latter.
Also make sure to use ES6 code style (e.g. using const, let where appropriate instead of var).

I'll stick with the sample1.
How the Attachment should know that it needs to load the file from file system? A new prop in object passed to fromData or a new branch in the Attachment constructor?

Follow #505

Hello @LukeXF,
This is a requirement of the underlying API. The purpose is this issue is to hide that implementation detail from users of this SDK.
With Best Regards,
Elmer

Since there has been no activity on this issue since March 1, 2020, we are closing this issue. Please feel free to reopen or create a new issue if you still require assistance. Thank you!


[Bug] Incremental models on partitioned string column fails

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Given a partitioned on a string column incremental model:
{{
    config(
        materialized='incremental',
        partition_by={'field': 'string_column', 'data_type' : 'string'},
        incremental_strategy='insert_overwrite',
    )
}}

SELECT '20201201' AS string_column

Running incremental dbt run on this model provides erroneous definition of partitions to update. It tries to use non-existent in BigQuery function string_trunc(string_column, day) code in /target/run/ directory:
      ...
      -- 2. define partitions to update
      set (dbt_partitions_for_replacement) = (
          select as struct
              array_agg(distinct string_trunc(string_column, day))  -- HERE NON-EXISTENT FUNCTION
          from MODEL_NAME
      );

      -- 3. run the merge statement
    merge into
    ...
    when not matched by source
         and string_trunc(DBT_INTERNAL_DEST.string_column, day) in unnest(dbt_partitions_for_replacement)  -- HERE NON-EXISTENT FUNCTION
        then delete
        ...

It causes dbt to fail the run with following error
Query error: Function not found: string_trunc at [51:34]
Expected Behavior
As for dbt version 0.18.2 it ran such model correct:
      -- 2. define partitions to update
      set (dbt_partitions_for_replacement) = (
          select as struct
              array_agg(distinct string_column)
          from MODEL_NAME
      );
...
      -- 3. run the merge statement
    merge into MODEL_NAME
    ...

    when not matched by source
         and DBT_INTERNAL_DEST.string_column in unnest(dbt_partitions_for_replacement)
        then delete

    when not matched then insert
    ...

Steps To Reproduce
No response
Relevant log output
No response
Environment
- OS: MacOS 12.0.1
- Python: 3.8.12
- dbt: official docker image version 0.21.0

What database are you using dbt with?
bigquery
Additional Context
No response

@jtcohen6 Thank you for explanation! I wasn't aware about impossibility of creation string-partitioned tables.
Then, I think dbt should at least create warn about this impossibility explicitly.

I think you can partition on anything now. And also under no circumstances should dbt-core be calling a function that's not even supported in bigquery, surely!


Terminal icon and color do not disappear after killing the first terminal in a list

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:

Version: 1.58.0-insider (user setup)
Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6
Date: 2021-07-07T12:09:55.219Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043

Steps to Reproduce:

Add a new terminal (no icon or color is visible)
Add a second terminal (icons and colors are visible for both terminals)
Kill the first terminal
The remaining terminal retains its custom icon and color: I would expect icon and color to disapper, similar to how the terminal looks at point 1
If instead I kill the second terminal, icon and color disappear as expected

My terminal settings:
"terminal.integrated.defaultProfile.windows": "Powershell Preview",
"terminal.integrated.profiles.windows": {
    "Powershell Preview": {
        "path": "C:\\Program Files\\PowerShell\\7-preview\\pwsh.exe",
        "color": "terminal.ansiMagenta"
    },

same root cause as https://github.com/microsoft/vscode/issues/127573

Here's the right issue I think: https://github.com/microsoft/vscode/issues/128236


Disallow to pass PlainOption::Option to operators of PlainResult, and vice versa

Fix https://github.com/karen-irc/option-t/issues/387

This change is

By this reason, I seem Symbol is not good way for this.

I think we should not do this way. See https://github.com/karen-irc/option-t/issues/387#issuecomment-499782943


Q: Number of classes

In the 2. executed box of https://github.com/rykov8/ssd_keras/blob/master/SSD.ipynb
We see that NUM_CLASSES is set to all the len(voc_classes) + 1.
However in the training notebook there's no mention of a +1, neither is there in the xml data-convertion script.
What's up with that? :)

Hello @NegatioN  yes, you always include the + 1 background class for the BBoxUtility and model and the loss. It is not included in the XML parser file. In the training file it is not explicitly stated but it is also there. There are 4 classes including the background class.
This +1 happens explicitly in the BBoxUtility sincethis class assigns the prior/default boxes to its corresponding class including the background, which is later on used for the positive and negative loss in the MultiboxLoss class.

@oarriaga much obliged, I really appreciate your succinct and quick responses. I had a feeling i was missing something.
This is not really mentioned in the paper, but more a part of this implementation? (or the original implementation as well?)

@NegatioN oh thank you, yes I have studied this code and the paper enough so that I could help other people.
Yes I would say this is more part of the implementation and not mentioned in the paper. However, what it is mentioned on the paper is the use of positive and negative loss which are the loss associated to the objects assigned to a class different than the background and objects assigned to the background class respectively.

Thank you for the help @oarriaga :)


Letting the bin/console.php setup command have non-interactive mode

As title, sometimes it should let the bin/console.php setup command run automatically in non-interactive mode.
And it can run above command during the continuous delivery running.
I think it can run automated bin/console.php script when the config/env.php is existed.

Hi! There are different use-cases we should not mix here.
The setup command is only for the developer's local project setup.
For continuous integration or continuous delivery, you should use a build / deployment pipeline instead.

Is there any reference about running the script in the build/deployment pipeline?
I think we should consider using the setup command for the remote development project setup when demonstrating the skeleton application.

The setup command is not intended to be used in a build/deployment pipeline. This command should only be used if you, as a developer, need to create a local development database for this project.
If you have a very specific use-case, like creating a demo-site using the CLEARDB_DATABASE_URL environment variables, then better create a script for this specific task. For example, add the needed commands to your sync.yml file.
For example:
name: Sync original repository

on:
  schedule:
    - cron: '*/10 * * * *'
  workflow_dispatch:

jobs:
  up-and-running:
    runs-on: ubuntu-latest
    steps:
      - name: Get working copy
        uses: actions/checkout@master
        with:
          fetch-depth: 1
      - name: Commit and push if it changed
        run: |
          git config user.name "username"
          git config user.email<EMAIL_ADDRESS>          git add -A
          timestamp=$(date -u)
          git commit -m "Last Commit: ${timestamp}(UTC)" || exit 0
          git pull https://github.com/odan/slim4-skeleton master --no-edit
          git push origin master
          mysql -uroot -proot -e 'CREATE DATABASE IF NOT EXISTS demo CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;'
          composer install --no-dev --optimize-autoloader
          echo "<?php" > config/env.php
          echo "return function (array $settings): array {" >> config/env.php
          echo "\$url = parse_url(getenv('CLEARDB_DATABASE_URL'));" >> config/env.php
          echo "\$settings['db']['host'] = $url['host'];" >> config/env.php
          echo "\$settings['db']['port'] = '3306';" >> config/env.php
          echo "\$settings['db']['username'] = \$url['user'];" >> config/env.php
          echo "\$settings['db']['password'] = \$url['pass'];" >> config/env.php
          echo "\$settings['db']['database'] = substr(\$url['path'], 1);" >> config/env.php
          echo "return \$settings;" >> config/env.php
          echo "};" >> config/env.php

The mysql command creates a database with the name demo. Change that according to your environment.
Note that I use the composer install --no-dev --optimize-autoloader command, because in this very specific case it's actually a deployment to a production server and not a CI environment.
The echo commands are generating the config/env.php file for this specific setup. Usually this env.php should not be store there in production, but for this use-case it's ok.

Thanks. I got it. Let me think about the proper reference for the Heroku deplyment.

@odan, just notice that I've created the deployment.yml and sync.yml to complete the Heroku deployment and sync the original repository. Thanks for your help and appreciate your time and the file contents you can refer are as follows:

deployment.ym
sync.ym

And the demonstration URL is available here.


doc: build: dts: Fix incorrect foreach documentation

Replaced incorrect rst link references in the description of traversing ancestor nodes, along with some conflicting descriptions.

Hmm... It seems that I did not modify the corresponding pointer after copying the rst tag :(


Did not work with me

I have done as the steps in your repo say, and still, I cannot see Authelia login yet
Below is the plugin config from Jellyfin

This is the usual Jellyfin login page when I enter my url, once I login, I am in with no 2FA via Authelia

What am I missing here?
Note, I have Authelia working just perfect with other services, but not this

Hi there!
This is mentioned in the description of this plugin.
There are two ways you can technically integrate Jellyfin with Authelia.

The first approach would be redirected to the Authelia login page and back to Jellyfin. If you want that, you should use SSO plugin instead of this. This way you would get working 2FA, since all that is happening on Authelia's side. This approach does not work for me, since I am not only using the web UI for Jellyfin but also obscure Android clients, which would know nothing about the redirecting thing and will not work with the SSO plugin, since it is not part of Jellyfin API authentication flow.
The alternative approach is using Jellyfin UI and API for login/password, and using Jellyfin as the authentication provider in the backend. This is the approach taken by this plugin. It fits the natural auth flow and works with alternative Jellyfin clients, but since Jellyfin auth flow has no API flow for 2FA, it will log you in without 2FA.

tldr; If you need 2FA, you're better off with SSO plugin

I guess I can add the note about 2FA to the plugin configuration page to not cause confusion


transition.redirect() not passing params

I tried to create a simple auth-flow using a mixin, which passes the attemptedTransition as a param to the login endpoint
<Routes>
        <Route handler={MainApp}>
            <Route handler={DeveloperPortal} username={username}>
                <Route handler={ContentArea}>
                    <Route name="overview" path="/overview" handler={Overview}/>
                    <Route name="apis" path="/apis" handler={Api}/>
                    <Route name="applications" path="/applications" handler={Application}/>
                    <Route name="experiments" path="/experiments" handler={Experiment}/>
                </Route>
            </Route>
            <Route name="login" path="/login" handler={LoginArea}/>
        </Route>
      </Routes>

var AuthenticatedRoute = module.exports = {
	statics: {
		willTransitionTo: function(transition) {
			console.log("AuthenticatedRoute");
			if(!UserStore.isLoggedIn()) {
				transition.redirect('/login', {attemptedTransition: transition});
				console.log(transition);
			}
		}
	}
};

Both "/applications" and "/experiments" use the AuthenticatedRoute mixin, so that when I try to click on links to them they are redirected to login, but when I output the params that should have been passed in the render function of LoginArea they aren't there
render: function () {
        console.log("LoginArea- " + UserStore.isLoggedIn());
        console.log(this.props.params);

        return (
  <Button bsStyle="primary" style={loginButtonStyles} onClick={this.handleClick}>
     Log In
  </Button>
        );
    }

You need to store that transition somewhere in your app and look it up again later

For me one problem is to know what's the best way to store this kind of cross component status in my application. Your auth-flow example is all in the same file. But for me is hard to understand having my code in AMD modules.
@rpflorence can you point to an example of how to use react + react-router and AMD modules to store application state?
Thank you a lot for all the hard work

@andresgutgon Have you solved your problem?
I have same issue with storing somewhere transition and i can't reach this.props.params after transition.redirect was called.

Hi @paraboom I pass the transition to the login view. You can see my code here:
https://github.com/aulasenelaire/binding-vas-experiments/blob/master/src/javascripts/react-mixins/dropbox-auth.js
follow the files :)

Thanx, for answer @andresgutgon. But you pass transition with query (third argument), but what about params, that assigned to this.props.params? I can't do this in my code.

@paraboom what do you have in this.props.params?

@andresgutgon your first question in this thread was about passing parameters to render function, right? I'm asking about that :smile:

Just to note, you won't get this.props.params automatically since RR 0.12, you need to either pass them yourself to <RouteHandler> from state you get in Router.run callback, or use State mixin and this.getParams().

@gaearon, @andresgutgon  Thank you very much, guys! This is exactly what i need.

I think this information should be in documentation

It is. If you see any references in docs to this.props.params, just let us know and we'll update them to current API.


Ignore react-router-dom 6.x versions

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


Feature/postgres db

I solved merge conflicts but we still have different implementations for the users queries.


Phase out SupportsPhase protocol

The use case I have in mind is defining this protocol for SWAP. This is useful, for instance, for the EjectZ optimizer because one can pass a Z gate through a SWAP as follows:
0: ───Z^theta───×───
                │
1: ─────────────×───

=
0: ───×─────────────
      │
1: ───×───Z^theta───

So I think the phase_by function signature should be changed from
def phase_by(val: Any,
             phase_turns: float,
             qubit_index: int,
             default: TDefault = RaiseTypeErrorIfNotProvided):

to
def phase_by(val: Any,
             phase_turns: float,
             qubit_index: int=None,
             qubits: Sequence[cirq.Qid]=None,
             phased_qubit: cirq.Qid=None,
             default: TDefault = RaiseTypeErrorIfNotProvided):

Then phase_by for SWAP would return an OP_TREE.

We could also special case swaps in EjectZ for a quick and dirty solution
@Strilanc what do you think about @kevinsung 's proposed changes? also cc @dabacon

Initially: add in swap gate and fsim gate (with the one theta that works) support as hardcoded cases in EjectZ.
Later: delete phase_by protocol after hardcoding remaining cases.

I'm trying to reconcile the title of this issue with the description which appears to mean to augment the phase_by protocol.
What would be even better is if we could generalize this protocol for describing the logic behind these types of transforms.

@dabacon I think what happened was that we discussed this issue during a Cirq sync and then decided to instead remove the SupportsPhase protocol using the plan in @mpharrigan's comment. Then I changed the title of this issue.

Do we still have this protocol?  If we are still going to remove this, we should do it before 1.0.

Adding back to triage/discuss since @tanujkhattar did not see a reason to deprecate it.

We can probably keep it.  It's an example of a very specific protocol tightly coupled to a particular transformer, which is not great.

It was decided to keep this protocol after all.  The consensus in cirq cync was that this didn't really affect anyone negatively and did provide some small value, so that we would keep it in.
The above functionality to propagate Z's through swaps had already been added to EjectZ.
Closing this issue.


Reproducing the Fold Classification baselines

Hello, thank you for the great and detailed work. I was trying to reproduce the results for fold classification with one model (GCPNet), however, after a few runs it was apparent that it doesn't align with the results presented in the paper. Here is the command used:
# reproduce the baseline tasks sweep (i.e., those performed without pre-training each model)
wandb sweep proteinworkshop/config/sweeps/baseline_fold.yaml

I slightly modified the baseline_fold.yaml to report the results on wandb and only use the GCPNet model. Here is the updated file:
program: proteinworkshop/train.py
method: grid
name: baseline_gc_prediction
metric: # Does not matter, as we are using sweep to run the experiment.
  goal: minimize
  name: val/loss/total

parameters:
  task:
    values: [multiple_graph_classification]

  dataset:
    values: [fold_family, fold_superfamily, fold_fold]

  encoder:
    values: [gcpnet]

  optimiser.optimizer.lr:
    value: 0.0001

  features:
    values: [ ca_seq,ca_bb]

  scheduler:
    values: [plateau]

  extras.enforce_tags:
    value: False

  +aux_task:
    values: [none]

  trainer:
    value: gpu

  trainer.max_epochs:
    value: 150

  test:
    value: True

  name:
    value: "${hydra:runtime.choices.encoder}_${hydra:runtime.choices.features}_${hydra:runtime.choices.dataset}"

  logger:
    value: wandb

command:
  - ${env}
  - HYDRA_FULL_ERROR=1
  - WANDB_START_METHOD=thread
  - python
  - ${program}
  - ${args_no_hyphens}

You can find the results I'm getting below (all 99.99+).

Any suggestions how to correct this issue?

Hi @anonymous-0545
What do the training and validation curves look like?
One possible thing to try is switching the task:
parameters:
  task:
    values: [multiclass_graph_classification]

I don't exactly remember which task name is correct but I'll dig into the logs to confirm. Please do try this and let me know how you get on though.
One more thing to note is that it doesn't look like you're using the hparams (e.g. lr and dropout). See the separate hparams config for those values.

Thank you for the prompt response. The curves start around 99.9, as you can see below:

I've added the lr and dropout to the config as follows:
  optimiser.optimizer.lr:
    value: ${hparams.hparams.lr}

  decoder.graph_label.dropout:
    value: ${hparams.hparams.decoder_dropout}

I've started with multiclass_graph_classification but it would be great if you could confirm which one is used on the experiments. The initial validation accuracies are 0.07, 0.13, 0.18. Also, why is separate training needed for different test sets? Is there a difference in the training or validation set for each?

I've started with multiclass_graph_classification but it would be great if you could confirm which one is used on the experiments.

I checked and it should be multiclass_graph_classification

The initial validation accuracies are 0.07, 0.13, 0.18

That looks like it lines up with my logs :)

Also, why is separate training needed for different test sets? Is there a difference in the training or validation set for each?

No should not be necessary, we initially implemented them separately but since removed the need for separate training.

@anonymous-0545 How did you get on? Can I close the issue?

Closing. Feel free to re-open if not fully addressed.


Request errors never get set on form

Laravel Precognition Plugin Version
0.5.6
Laravel Version
10.48.10
Plugin
Vue w/ Inertia
Description
Validation requests are sent to the server, which responds with the appropriate errors and HTTP status 422.
The errors are visible in the network tab, but they are never set on the Form object itself.
Steps To Reproduce
I'm trying to setup precognition with Vue + Inertia.
The request is being made and the errors are being returned, but it's not populating the form's errors object. It remains as an empty object.
web.php
Route::name('store')
    ->post('/', [CourseAssignmentController::class, 'store'])
    ->middleware([HandlePrecognitiveRequests::class]);

Controller Method Signature
public function store(CreateAssignmentRequest $request)

CreateAssignmentRequest
<?php

namespace App\Http\Requests;

use Illuminate\Foundation\Http\FormRequest;

class CreateAssignmentRequest extends FormRequest
{
    public function rules(): array
    {
        return [
            'title' => 'required|string',
            'overview' => 'string|nullable',
        ];
    }
}

Vue Component
import {useForm} from 'laravel-precognition-vue-inertia';

const form = useForm('post', route('courses.assignment.store', {course: props.course.id}), {
  title: '',
  overview: '',
});

function createAssignment() {
  form.submit({
    preserveScroll: true,
    onSuccess: () => form.reset(),
  });
}

What kind of more info would need @driesvints, @timacdonald ? I could try to get a test app to reproduce, send a loom, or hop on a call.

It would be good to see the entire Vue file and a reproduction repository would be even better. I'm unable to reproduce the issue with what I can see here.

@ncphillips try reproducing the issue on a fresh repo so Tim can have a better look. Thanks!
laravel new bug-report --github="--public"

Interesting! I'll see what I can do.
I feel our setup must have some assumed thing setup incorrectly

Thanks, @ncphillips. Keen to help out where we can to get this sorted for ya.
Let us know how you go.

I haven't had any luck :( I spun a new app up and everything worked fine.
I went back and made sure to upgrade all the inertia, precognition, axios, etc.
I feel like the most likely culprit is our version of laravel ? Really not sure.

I don't believe there has been any changes to the framework's precognition code since 10.11.0.
Could you provide the full vue file you are having issues with?
Do you have any global configuration that could be impacting this?

@ncphillips, I'm gonna close this one. I'm certainly up for helping get to the bottom of it. If you can share any more information we can keep digging in.

That's fair @timacdonald, thanks!

Okay I just tried again from scratch.
Here's the JS package version I got
"laravel-precognition-vue-inertia": "^0.5.6",

I just whipped up a brand new page with this Vue template:
<template>
  <form @submit="submit">

      Name:
      <input id="name" label="Name" v-model="form.name" @change="form.validate('name')" />
      {{ form.errors.name }}

    <button type="submit" :disabled="form.processing">Submit</button>

Validating

Submitting

<data>{{ JSON.stringify(form.errors) }}</data>

  </form>
</template>

These are the routes in my web.php:
Route::get('banana', function () {
    return inertia('Banana');
});

Route::post('banana', function (\App\Http\Requests\BananaRequest $request) {
    return redirect()->back()->with('success', 'Hooray!');
})->middleware([HandlePrecognitiveRequests::class]);

Here is the Request
<?php

namespace App\Http\Requests;

use Illuminate\Foundation\Http\FormRequest;

class BananaRequest extends FormRequest
{
    /**
     * Determine if the user is authorized to make this request.
     */
    public function authorize(): bool
    {
        return true;
    }

    /**
     * Get the validation rules that apply to the request.
     *
     * @return array<string, \Illuminate\Contracts\Validation\ValidationRule|array<mixed>|string>
     */
    public function rules(): array
    {
        return [
            'name' => 'required|min:3'
        ];
    }
}

I do notice that it installed a different version of axios

But once again, I see that it is returning with a 422 and the error messags, but those error messags are not in my form

I copied this all verbatim into a fresh Laravel breeze application using Laravel 10.48.10 and Precognition 0.5.6 and everything seems to be working as expected.
https://github.com/user-attachments/assets/5f9b96c1-d57b-46c5-9282-8bfec7830580
Couple more things I'd love to know:

Could you please share the response headers?
Are there any messages in the JS console?
Do you have any special CORS configuration?

I'm also wondering if you are doing any global configuration in this application that could be impacting this somehow?

I copied this all verbatim into a fresh Laravel breeze application using Laravel 10.48.10 and Precognition 0.5.6 and everything seems to be working as expected.

Me too, it's really weird. I absolutely think it's something to do with our setup. This app's been around a while and has some unconventional things going on in various places.

Could you please share the response headers?

Are there any messages in the JS console?

I'm seeing some cookie warnings. However, I also see them when I submit the form, which works just fine.

Do you have any special CORS configuration?

I am not aware of any special CORS config. Also, I do seem to be getting a valid response? Unless 422 is not what precognition expects.

I'm also wondering if you are doing any global configuration in this application that could be impacting this somehow?

Maybe. But I can't think of what it might be.

Progress!

Our errors are wrappe din another layer of data.
I suspect we have a middleware that wraps all json responses in data

BOOM

We are in the process of moving form a SPA to Inertia. For the SPA we have a custom ExceptionHandler that wraps any thrown exceptions into a palatable data structure.
I just needed to throw a little isPrecognition() check in that thing to get it working!

This is great! Glad to hear you were able to get this working and thanks for the update.
Hope you enjoy the package!

Looks great so far! I think my only complaint is useForm returns any. Might look at contributing an improvement there


Add include files for CXX

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

@conda-forge-admin, please rerender

I tried lint locally and it says the recipe is fine:
conda smithy recipe-lint .
. is in fine form

@ocefpaf and @scopatz can you take a look at this PR?

This looks fine to me, it is probably OK to merge, and fix the linter issues in another PR

@scopatz I am currently doing some last tests in https://github.com/conda-forge/staged-recipes/pull/10403/ because I noticed that the header files are spread over different folders. So maybe give me some more moments.

I currently get the following error:
home/conda/staged-recipes/build_artifacts/parsplice_1575985155642/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/include/dbstl_resource_manager.h:111:3: error: invalid use of member 'dbstl::TlsWrapper<T>::tinst_' in static member function
   tinst_ = objp;
   ^~~~~~
/home/conda/staged-recipes/build_artifacts/parsplice_1575985155642/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/include/dbstl_resource_manager.h:118:30: note: declared here
  static TLS_DECL_MODIFIER T *tinst_;
                              ^~~~~~
make[2]: *** [CMakeFiles/dbextract.dir/build.make:89: CMakeFiles/dbextract.dir/core/LocalStore.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:82: CMakeFiles/dbextract.dir/all] Error 2

To me this sounds like I am missing some links libdb.


PR to add output_auxiliaries functionality for debugging

This PR adds functionality to the elevation functions and CLI workflow to optionally output auxiliary files for debugging.
Setting output_auxiliaries = True in the CLI workflow will output the following four supporting files to assist with debugging of intertidal datasets:

freq, an xr.DataArray showing the frequency of NDWI wetness over time in the area of interest (AOI)
corr, an xr.DataArray showing the correlation between freq and tide height in the AOI
good_mask, renamed as candidate_intertidal_px in the outputs, an xr.DataArray showing pixels that meet the freq and corr criteria for potential inclusion in intertidal analyses
misclassified_ds, renamed as misclassified_px_count, an xr.DataArray counting the number of misclassifications per pixel of the elevation workflow.

Thanks for this @erialC-P! Looking at the code, I think it might be possible to simplify this if we didn't worry about turning the auxiliary creation on and off at the lower level function level (e.g. ds_to_flat, uncertainty). At the moment that's forcing us to have a lot of "if/else" clauses to handle the different outputs we can get from those funcs - instead we could just have those funcs return all outputs by default, and then only export the ones we want at the very end depending on whether output_auxiliaries is True or False. The only disadvantage is that we'd waste a tiny bit of compute calculating the layers which we wouldn't end up using, but it might be worth it for a bit less complexity overall.
If this sounds OK, I might jump into this branch and have a go at updating this?

That's totally ok with me. Concern over that extra bit of compute was why I built it using the if/else's but if you think it would be a minimal cost to reduce the code complexity then I'm happy for you to go ahead. Thanks for looking it through.
Were you happy with the method to extract the count of misclassified pixels? I forgot to check whether misclassified_ds.ndwi.count(dim='time') == misclassified_ds.tide_m.count(dim='time')

Have pushed an update with some changes - the main thing was doing a pretty major refactor to the ds_to_flat func: previously it was returning a mix of flattened and unflattened output, and I think this made it much more difficult to wrangle those datasets further down the workflow. The updated workflow is now:

ds_to_flat returns only flattened (e.g. "z" dimension) outputs, for both the main flat_ds but also corr, freq etc
"auxiliary" outputs like corr and freq are then added to a new flattened ds_aux
ds_aux is then unflattened in a final step just like we do for the main ds
If output_auxiliaries is True, then we use the export_intertidal_rasters func to output those debug files as GeoTIFFs at the very end

I think this should make future changes a bit easier, as we don't need to keep track of which datasets are in 2D vs. flattened throughout the elevation workflow. Keeping things in flattened form might also reduce our memory footprint a bit too (haven't tested this!).


Calender Heatmap not working

I am using this component to render heatmap, but I am unable to do so. I think the component is not accepting my dataset. I have also tried with fixed dataset.
Here is what my component looks like:
<CalendarHeatmap
                  values={this.createTimelineAnalysisData()}
                  showOutOfRangeDays={false}
/>

This will just render a black heatmap with 6 months, it must be the default I think.

what do your values look like - can you give an example? it should be an
array of objects that each have a 'date' attribute. additionally, you'll
need to add some css to make the colors not be the default svg black color

take a look at the readme to see how to get started with some sample css.
let me know if you have further questions!

On Oct 28, 2016 2:58 PM, "Ankit Singhaniya"<EMAIL_ADDRESS>wrote:

I am using this component to render heatmap, but I am unable to do so. I
think the component is not accepting my dataset. I have also tried with
fixed dataset.
Here is what my component looks like:

This will just render a black heatmap with 6 months, it must be the
default I think.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/patientslikeme/react-calendar-heatmap/issues/22, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAYK5q0fAnM9qHgrGhrPljjOfY5Wo53pks5q4Y70gaJpZM4KjGt1
.

Here's a minimal setup of react-calendar-heatmap with create-react-app on CodeSandbox, which should hopefully help show how things are set up: https://codesandbox.io/s/73mk9wlyx


Feat/event capture

This adds two new configuration options to Hammer allowing use of capture based eventing instead of bubbling.  Capture based eventing is often faster and more reliable.

Manager.options.useCapture (default false): specifies whether to use capture based eventing
Manager.options.useCaptureOnRoot (default false): specifies whether to attach all event listeners to the root of the page when useCapture is also true.
[x] This PR needs documentation to go with
[x] Hammer.defaults needs to be updated with jsdocs for these flags.

@runspired looks like you added docs already. as far as jsdoc the website will need an update too but thats a different repo anything else besides a review blocking this?

I think we need a practice of adding docs to the ReadMe, otherwise only review.

looks like your changes to merge / extend got mixed in here. Can you rebase to fix this and any other conflicts?

Hi. Any chance that this PR to be integrated soon ? I would need it and it seems very well done.


[REQUEST] Can the Storage View use the same smart formatting logic that the Event Log uses?

Almost all Values in the Storage Viewer are displayed as hex strings.

No longer applies in latest version


Request minimal size packit-worker-repository-cache PVC

if not with_repository_cache.
So with this change, Hardly, which doesn't use the cache (yet), will still request the claim, but just a minimal size (1Gi) one, which compared to 127Gi storage we already use in all projects is "insignificant" ;-)
I haven't found any easier way how to conditionally (not) include that claim.
Fixes #244

@lbarcziova uh, I knew I was missing something obvious. Thank you!!!


About Tensor Arena Size

Hi, hello world example performs well on my ESP32 CAM, but when I change kTensorArenaSize to about 200k, it occurs error like /.espressif/tools/xtensa-esp32-elf/esp-2021r1-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: region `dram0_0_seg' overflowed by 41976 bytes. It seems that the memory is not enough, but my chip has 500KB internal RAM and 4MB PSRAM. For my application, about 250k arena size is needed. So is that possible to let tensor arena size bigger?

Hi @notplus it is possible to do this.
Instead of going for dram (static buffer), you can allocate this buffer on heap (internal or external depending your requirement) to get more flexibility.
For reference: https://github.com/espressif/tflite-micro-esp-examples/blob/master/examples/person_detection/main/main_functions.cc#L68
Thanks,
Vikram

Hi, thank you for your reply. I tried the code you motioned, but it remain error while running.
Code:
constexpr int kTensorArenaSize = 250*1024;
uint8_t *tensor_arena;

// some code

  if (tensor_arena == NULL) {
    printf("%s: free RAM size: %d, INTERNAL: %d, PSRAM: %d\n", "tag", heap_caps_get_free_size(MALLOC_CAP_8BIT), heap_caps_get_free_size(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL), heap_caps_get_free_size(MALLOC_CAP_8BIT | MALLOC_CAP_SPIRAM));
    tensor_arena = (uint8_t *) heap_caps_malloc(kTensorArenaSize, MALLOC_CAP_INTERNAL | MALLOC_CAP_8BIT);
    // tensor_arena = (uint8_t *) heap_caps_malloc(kTensorArenaSize,MALLOC_CAP_8BIT | MALLOC_CAP_SPIRAM);
  }
  if (tensor_arena == NULL) {
    printf("Couldn't allocate memory of %d bytes\n", kTensorArenaSize);
    return;
  }

Output:
tag: free RAM size: 287300, INTERNAL: 287300, PSRAM: 0
Couldn't allocate memory of 256000 bytes
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.

@notplus
You have not enabled SPIRAM.
You can enable it via menuconfig as follows:
idf.py menuconfig > components > ESP32 specific > SPIRAM
and then rebuild the application with above code
tensor_arena = (uint8_t *) heap_caps_malloc(kTensorArenaSize, MALLOC_CAP_SPIRAM | MALLOC_CAP_8BIT);

Ok, but does this mean that there is no way to allocate 250k internal memory? Other platfom which only has 384 kb SRAM can allocate 250k arena size when run TFLM.

For static memory, ESP32 restrict it below 160KB.
But since, since you have 287300 free at the time,  ideally you should be able to allocate 250KB though via malloc.
Could you please also add prints in your code for largest free block? allocations obviously capped by this number.
heap_caps_get_largest_free_block(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL);
For more details on how 520KB SRAM is organised, you may take a look at this nice blog: https://blog.espressif.com/esp32-programmers-memory-model-259444d89387
Please note that 192KB is reserved for IRAM and remaining (328KB) is used as a DRAM. (ROM functions+Data+BSS+Heap)
To analyse what's eating up memory, you may run idf.py size for basic and idf.py size-components for yet detailed size info of the app.

Ok, I got it. Thank you for your nice reply. Maybe it's better to use esp-dl.  :laughing:


include test from incubator-openwhisk PR#2941

Test addition after https://github.com/apache/incubator-openwhisk/pull/2941/ was merged

won't this test go into incubator-openwhisk in the ApiGwRoutemgmtActionTests test suite.. this way both the REST interface is tested.  then the incubator-openwhisk-cli will pick this test up via ApiGwCliRoutemgmtActionTests extends ApiGwRoutemgmtActionTests

@mdeuser the test was added to  incubator-openwhisk/tests/src/test/scala/whisk/core/cli/test/ApiGwRestBasicTests.scala so I added it here...
If what you say is the "right" way to do this then we need to assess that in a separate PR. Probably another issue even in order to make sure the tests are structured the way you desire.

some tests are currently structured so that both rest and cli tests have shared tests.  for this particular test, i believe the structure is already in place.  there's a ApiGwRoutemgmtActionTests.scala in the incubator-openwhisk that's extended by ApiGwRestRoutemgmtActionTests.scala (incubator-openwhisk) for the rest-ful tests as well as ApiGwCliRoutemgmtActionTests.scala (incubator-openwhisk-cli) for the cli tests

@drcariel  please rebase this PR.

@houshengbo done


no suitable node available for task

When logs is set to debug, user can see many log entries like this:
Jul 13 15:50:42 ucpleader dockerd: time="2018-07-13T15:50:42.940480757Z" level=debug msg="no suitable node available for task" module=node node.id=xjmdhj9quobn9zufkezwlbfng task.id=3h6xnbt75p66i54l5619yp1f7
trying to inspect the task:
[centos@ucpleader ~]$ docker inspect 3h6xnbt75p66i54l5619yp1f7
[]
Error: No such object: 3h6xnbt75p66i54l5619yp1f

Steps To Reproduce:
steps to repro:

set daemon.log to debug
create a service with a node constraint that does not exist:
ex: docker service create -d --constraint 'node.labels.type == queue' alpine sleep 10000
watch the logs, you should see an error
no suitable node available for task
delete the service and invoke the tick() by creating another service; watch the log and notice the same warning taskID in pops up after service is deleted

This PR should address this issue

Addressed by https://github.com/docker/swarmkit/pull/2706


Add github action to auto-message the contributor when their pr is merged

Proposal
(A clear and concise description of what the proposal is.)
Message like -  "Well Done @username !! Looking forward for more such contributions" or any other message as per the mentor's wish
would be sent to the contributor after their pr is merged successfully

I would like to work on this issue

It is not needed as mentors will be commenting and on a successful PR merge the github will send an notification.


docs: reword beforeNavigate description so that it includes navigations to the same URL

closes https://github.com/sveltejs/kit/issues/12863

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

[x] Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

preview: https://svelte-dev-git-preview-kit-13133-svelte.vercel.app/
this is an automated message


How to access the graphical console(vnc) using noVNC

Dear friend
Kubevirt is an excellent project, I am using it. When I start the VM via kubevirt, I found an API.
-----
wss://<IP_ADDRESS>:6443/apis/subresources.kubevirt.io/v1alpha3/namespaces/default/virtualmachineinstances/testvm/vnc
-----
How can I connect to vm using novnc?
Thanks in advance.

Hi @yinjingjiu there is a specific reason you want to use noVNC?
I general we support a vnc connection and also console one using the virtctl command.
Example:
virtctl console centos
Or
virtctl vnc centos
you can download the CLI from the release page https://github.com/kubevirt/kubevirt/releases/tag/v0.17.0

您好@yinjingjiu有一个特殊原因要使用noVNC吗？
我一般我们支持vnc连接，也使用virtctl命令控制一个。
示例：
virtctl console centos
或
virtctl vnc centos
您可以从发布页面下载CLI https://github.com/kubevirt/kubevirt/releases/tag/v0.17.0
Dear @SchSeba
I want to access in the browser, But I don't know how to use this api.
Can you give me a suggestion? thanks.

Hi @yinjingjiu what platform are you using (openshift/k8s) ?
I am not sure if you can access the vnc using only novnc because the url is under the k8s api so you will need to send the kubeconfig for authentication and authorization.
I know that we support vnc in the browser in the openshift-ui related to this PR https://github.com/kubevirt/web-ui/pull/36
maybe @mareklibra can help you?

Dear @SchSeba  @mareklibra
I am using k8s, I have never used openshift, Can you teach me how to access a virtual machine in a browser?
Thank you very much.

Hey @yinjingjiu, did you consider to use the kubevirt web ui? It's a UI which you can install on top of the current openshift UI, with support for for virtual machines, including console/vnc connections. See https://github.com/kubevirt/web-ui.

Dear @slintes , Thank you for your help, I want to implement a vnc connection myself, but using kubevirt web ui requires openshift support. I don't currently plan to use openshift .

Hi @yinjingjiu , the novnc connects to a WSS provided by kubevirt via k8s API subresource.
There's no magic, just a couple of steps to pass. Please have a look at kubevirt-web-ui implementation:

entry point: https://github.com/kubevirt/web-ui/blob/master/frontend/public/kubevirt/components/vmconsoles.jsx
connection details are prepared here. Please note, our application proxies connection to k8s API (and so to the VNC WSS) due to same-origin-policy. Not sure if your application is in similar situation.
Dig deeper to VmConsoles,
till you reach actual novnc use within VncConsole component, check the tear up/down steps there.

The code uses React but I believe it's understandable even without deeper React knowledge.

@mareklibra thank you for your help, I was inspired.  you are a star

that sounds like your question is answered, can we close this? :slightly_smiling_face:

Thanks to every teacher for their help.🙂

I wrote a tool called virtVNC that helps kubevirt users connecting vms using noVNC .🙂

@wavezhang that sounds awesome!
I'm wondering if we should try it and maybe blog about it?
@fabiand @codificat wdyt?

That's really awesome!
And yes, blog sounds pretty good fit for it, as having VNC access is
usually a common request.

Great indeed, thanks for sharing.
@wavezhang if you are willing / available to contribute a blog post about it I'd encourage you to. FYI there are some guidelines on how to contribute content (including blog posts), and you can look at some sample PRs for inspiration.
In any case we'd be happy to try it ourselves and either review the contributed blog post or add one of our own.
/cc @iranzo @ptrnull

OK, I'll add a blog post later.


typo: udpate -> update

@nschonni : Thanks for your contribution! The author, @barbkess, has been notified to review your proposed change.

Verified editorial correction.


Zowe explorer conformance

Zowe Explorer for VS Code conformance added in the Zowe conformance documents.
Signed-off-by: jp669844<EMAIL_ADDRESS>


Generate TLS certs on integration tests

Currently we have in the repo a couple of TLS certificates for those integration tests that require having HTTPS. We should generate them on each execution, and not checked out in the repo.

This is done


Mobius (Bulkrax): properly attach files

Story
Ref:

#27

Mobius' ZIP imports don't format files in the way Bulkrax expects:

Bulkrax expects the zip to have a folder names files/ that contains all the images

Mobius zip files can contain multiple folders of files with names like renamed_jpeg/, renamed_tiff/, renamed_pdf/, etc

Bulkrax expects the CSV to specify which file should attach to the record using the files column

Mobius CSVs don't have a column that specifies which files should attach to the record

However, we can infer which files should attach to the record using the values in the ss_pid column:

Example ss_pid: vital:10206
Example matching filename: vital_10206+SOURCE1+SOURCE1.0.jpeg

Acceptance Criteria
In the following:

<X> represents a uniquely identified numeric

<Y> represents a file extension (e.g. jpeg, tiff, etc)

[ ] When importing a record with an ss_pid value of vital:<X>, the importer should search for a matching file with the name of vital_<X>+SOURCE1+SOURCE1.0.<Y>

[ ] If the file is found, it should attach the file to the created work
[ ] If the file is not found, it should log an error saying so on the record's entry

Testing Instructions and Sample Files
Sample files

Notes

SoftServ QA ✅
Importer
Example work


Energy Dashboard configuration

Hello all,
I was seeking some help regarding the energy dashboard configuration upon which I'm struggling a few days now.
Hardware setup
My system include:

One inverter, linked to two strings
One meter, measuring current incoming and outgoing from the grid
One battery, storing energy not immediately auto-consumed

Software setup
In the Energy dashboard, I put (json slightly edited for brevity):
{   "stat_energy_from_grid": "sensor.meter_1_reverse_active_energy",   "stat_energy_to_grid": "sensor.meter_1_active_energy_forward_active_energy",   "stat_energy_from_solar": [     "sensor.inverter_1_mppt_1_dc_total_yield",     "sensor.inverter_1_mppt_2_dc_total_yield"   ],   "stat_energy_from_battery": "sensor.battery_1_discharging_capacity",   "stat_energy_to_battery": "sensor.battery_1_charging_capacity" }
Everything works well with this settings, as I do not compute energy twice, a thing that would happen using the inverter power into the stat_energy_from_solar field....
Issue
In the energy dashboard, I am using several statistics which are total, and the battery statistics that go to zero each day at midnight.
When I first added HomeAssistant-FusionSolar integration, HA use the first datapoint value as zero-point, meaning that each midnight I get a drop in the statistics, and during the day, the battery in the energy dashboard is meaningless...

See also:

Similar to: https://github.com/tijsverkoyen/HomeAssistant-FusionSolar/issues/18
Anyone has some advice on how to configure it?
Thank you

Every midnight, while other statistics resets to zero (in the frontend, in the backend they are still counting energy), the two battery statistics reset to negative values (in the  frontend, in the backend they are reset to zero as they are daily stats).

In HA documentation they say that they keep the initial value when the statistic is added, as zero-point... Don't know if this may be relevant?

I think I will first need to read up on the documentation.
I don't think the Huawei Fusion Solar API exposes when the data is reset, for probably I will need to recalculate of take the current time or, ...
I don't have much time the coming weeks as I'm busy with other projects. So don't expect a change very soon.
Feel free to create a pull request yourself.

Actually, Home Assistant recognize the "last reset" by looking if a "total increasing" sensor goes to zero. At the end the logic is clear: the sensor starts from zero, it is total and it is INCREASING, so it goes to (say) 20kWh, and if this sensor drops to 0, well that's a reset. HA is intelligent enough for this.
Problem is that there's something in the initialization phase that set the so-called "zero-value" of the sensor to the value that it has in that moment. In this way, when it resets, it goes back to the zero-value (so if you setup this integration at 4PM when you already produced 15kWh, every middnight, the dashboard will display -15kWh).
I need to evaluate a possible solution for this too.
There's no hurry, your work is already excellent as is. Just putting the issue here if anyone would like to contribute. I will, as soon as I manage a possible workaround for this.

Progress so far:

Battery discharge capacity and Battery charge capacity are set to total, while they can set to total_increasing. See attached image. If sensor are kept total (without increasing) we should put in place routines to set last_reset based on drops to 0.

Changing line 134 in realtime_device_data_sensor.py from
https://github.com/tijsverkoyen/HomeAssistant-FusionSolar/blob/master/custom_components/fusion_solar/fusion_solar/realtime_device_data_sensor.py#L134
to STATE_CLASS_TOTAL_INCREASING would solve.
But, I'm not sure if doing so would break other sensors which may be correctly identified as "total" and should not be "total_increasing".

I have merged your PR.
I will create a PR in a few moments


[FLINK-29274][hive] Fix ObjectStore leak when different users has dif…

…ferent config

What is the purpose of the change
Cheery pick the fix #20887

@flinkbot run azure

The failed test is not related to the fix. Merging...


Create a reaper

We need a reaper or janitor process that can periodically cleanup the ETS table.

Addressed here: https://github.com/lirossarvet/honeylixir_tracing/commit/1307a35e14f8e8a5938b36ca7a6571f7e34e3db9


mp_searchdata throws warnings when maxobs exceeded

To reproduce:
%mp_searchdata(lib=sashelp, ds=class, string=l,outobs=5)

Log result:
 WARNING: Statement terminated early due to OUTOBS=5 option.
 NOTE: Table MPSEARCH.CLASS created, with 5 rows and 5 columns.

 Search query for CLASS took       0.00462007522583 seconds
 WARNING: SQLRC=4 when processing CLASS

Expected :  No warnings or errors

:tada: This issue has been resolved in version 2.56.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed typo in README.md

@nikitasavinov  your changes have been merged, thanks for your contribution 👍


build cordova

when using mup deploy, I think mup also build Cordova for mobile again, Is It necessary to build for ?
Also, build for Cordova is much slow down  the speed of build.

There is in my mupx PR the overwriting of the bundled deployed versions platforms file with just "server" & "browser", otherwise remove the platforms before deployment (and restore it if needed later).
meteor remove platform ios android


Hindley-Milner type system

This is also one of the fundamental goals of the project.

Link to the original paper: http://web.cs.wpi.edu/~cs4536/c12/milner-damas_principal_types.pdf

Another useful paper: https://web.archive.org/web/20120324105848/http://www.cs.ucla.edu/~jeff/docs/hmproof.pdf

b112d30df154e175ebfcc1326fbbd31746f6d2f8 provides improvements.


Making Forms

What type of help is needed?

@malikshubham827 We need to first create a basic HTML page for this.
We will have forms in it where we can take responses from students.
To get an idea of form visit the link in readme section

Do you need the link to the forms on the webpage to redirect students or are you creating them from scratch? You have put screenshots of Typeform so I thought you are using them.

We thought of creating it from scratch. Just created type form in order to give a basic idea to contributors how the site would look like.


satisfies for return types

🔍 Search Terms
satisfies
return
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
type AcceptableType = string | number | boolean | undefined | null | object[]

/** `const fn: () => "asdf" | 8 | undefined` */
const fn = (): satisfies AcceptableType => {
  if (someCondition) {
    return "asdf"
  } else if(otherCondition) {
    return 8
  } else {
    return undefined
  }
}

📃 Motivating Example
function getResult(): satisfies { a: string, b: number } {
  // type-errors until `satisfies` condition is met
  return {
    // type-hints and type-checking for:
    // (property) a: string
    // (property) b: number
  }
}

💻 Use Cases
The satisfies operator has been immensely useful for ensuring expressions match some wider type while also inferring their narrower type
However, because satisfies works only on expressions, getting the same behavior on function return types requires workarounds with several drawbacks. For example, if a function has multiple return values, we need to type satisfies SomeType for every single one of them, which is not only cumbersome but also prone to human error
/** `const fn: () => "asdf" | 8 | undefined` */
const fn = () => {
  if (someCondition) {
    return "asdf" satisfies AcceptableType
  } else if(otherCondition) {
    return 8 satisfies AcceptableType
  } else {
    return undefined satisfies AcceptableType
  }
}

playground link
This style is also incompatible with codebases that prefer/require their contributors to declare the return type of their functions (e.g. through eslint)
Another workaround exists by using satisfies on the entire function:
const fn = (() => { /* ... */ }) satisfies () => AcceptableType

playground link
but having to parenthesize the entire function just to be able to operate on it as an expression and then include the function signature in the satisfies type is at best impractical and at worst not even an option, in the case of function fn() { /* ... */ } declarations. Of course, function declarations will be available as expressions after the declaration, at which point satisfies can be used, but not to its full extent because the type-inference will no longer be able to guide the implementation of the function declaration from within the function body
// this correctly errors but...
getResult satisfies () => { a: string, b: number }

function getResult() {
  return {
    // you don't get any type-hints or type-checking here
  }
}

playground link
Being able to specify that the return type of a function satisfies a type would resolve all of the above drawbacks

Duplicate of #51556.

Duplicate of #51556.

@MartinJohns i've seen that issue and i don't think the feature request is the same. #51556 seeks to be able to ensure that an entire function signature satisfies some type, but #59577 seeks only to specify that the function return type (not the entire function signature) satisfies some type

IMO that's a negligible difference. Both issues want the same: The function must satisfy a type. You just don't care about the arguments, so you'd check for satisfies (...args: any[]) => WhateverType. And your problem would be solved with the other approach, while the other wouldn't be solved with yours.
But it's up to the maintainers to decide if it's a duplicate or not.

The same request was made before: #52195
Comment by @RyanCavanaugh:

While I agree with that as being an upside, I don't think it merits the trade-off compared to making a type psuedo-operator that only works in certain places. Tracking the use case at #51556

I would still really love to see this specific syntax to be accepted though 🥲

funny enough, i also requested a proto-version of https://github.com/microsoft/TypeScript/issues/52195 in https://github.com/microsoft/TypeScript/issues/7481#issuecomment-787399912 before the satisfies operator was made available
tbh i still would absolutely love to see https://github.com/microsoft/TypeScript/issues/52195 come to fruition, but maybe the scope/lift for #59577 is smaller and therefore more viable
as an aside, i can see in https://github.com/microsoft/TypeScript/issues/58918#issue-2360893787 and plenty of other feature requests there's a desire to co-opt satisfies in many other contexts. seems like the semantics of an inference-friendly opaque type is proving to be a powerful one. here's to hoping the maintainers give this a real chance 🤞


Redefine backoff strategy for retry middleware

Current implementation of retry middleware use equals intervals between retries. It may be useful to have possibility to redefine policy for retry intervals.
probably we can accept optional argument with a function that will accept 2 parameters with current retry counter and initial retry interval, based on these parameters function should calculate interval that needs to be awaited.

@ksysoev can I take this over? Also I think I don't need to wait for #94 to finish to begin this.

@shan-96 sure


gsudo: Added version 0.4.1

Added gsudo console app: A sudo for windows with similar user experience as *nix sudo and credentials cache (avoid repeated UAC popups)

{
    "version": "0.4.1",
    "description": "A Sudo for Windows - run elevated without spanning a new Console Host Window",
    "homepage": "https://github.com/gerardog/gsudo",
    "url": "https://github.com/gerardog/gsudo/releases/download/v0.4.1/gsudo.v0.4.1.zip",
    "hash": "5a7c2bdaa5e2c399c99bd396fea6e35a3267c62d901e7326959b17b1abaf4a3b",
    "bin": [
        "gsudo.exe",
        [
            "gsudo.exe",
            "sudo"
        ]
    ],
    "checkver": {
        "github": "https://github.com/gerardog/gsudo"
    },
    "autoupdate": {
        "url": "https://github.com/gerardog/gsudo/releases/download/v$version/gsudo.v$version.zip"
    }
}

    "checkver": "github",

P.S. This can be moved to main bucket I guess.

I wish, really. I am the author. At this point it does not fits this main-bucket-criteria:

a reasonably well-known and widely used developer tool

I started this project about a month ago.


Migration

Hello.
I want to use this library.
But I don't understant something.
If I already have a database (that I don't want to reset) can I update it using this library without a base SLQ script? If yes, how?
Thansk.

@byjg I have question about supporting of cross-database migration, I mean do some stuff with data from two or more source, it is available with that library?

@byjg Hello! I mean can we fetch data from one database and based on foreign key relation do update in second database within one migration file?


Blinds work perfect, but slow

Describe The Bug:
Not sure whether it is a bug or whether it is by intention since it is still in experimental state. However, the blinds do work perfect. Only problem is that the command to open or close the blinds shows up only 20 seconds after having pressed the corresponding button in the home app. It is always exact 20 seconds.
To Reproduce:
Press a blinds button in the home app and start the stop watch while observing the homebridge logs.
Expected behavior:
Since anything else runs lightning fast and much better with the former free@home API implementation from Spange I was using, I expected the blinds to react in the same speed like the lights.
Logs:
Nothing special visible in the logs, even in verbose mode nothing.
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
{
"name": "Free@HomeLocalAPI",
"host": "<IP_ADDRESS>",
"user": "xxxxxxxxxxxx",
"password": "yyyyyyy",
"tlsEnabled": false,
"disableCertificateVerification": false,
"verboseErrors": true,
"experimental": true,
"platform": "FreeAtHomeLocalApi"
Environment:

Plugin Version:
v1.8.0
Homebridge Version:
v1.6.1
Node.js Version:
18.12.0
NPM Version:
8.19.2
Operating System:
Raspbian

Looks like it was internal network problem here with me. When I used the home app on iOS everything is fine. Problem only occurred on my Mac.


refactor(cmd): keep all plugins dirname-in-cmd == plugin-name

Signed-off-by: Daniel Hu<EMAIL_ADDRESS>Summary
keep all plugins dirname-in-cmd == plugin-name
Related Issues
#348

Please do not merge before CI is triggered and passed.