Add variadic tuple overload to Promise.all

Experiment for now. Similar to #39336, but with a different overload definition.

@typescript-bot test this
@typescript-bot user test this
@typescript-bot run dt

@typescript-bot user test this

@rbuckton Interesting that this doesn't seem to break VSCode. In fact, best I can tell, none of the differences in the user tests appear to be caused by adding the extra overload.

@typescript-bot test this
@typescript-bot user test this
@typescript-bot run dt

Latest commit removes the old overloads. This is a breaking change for calls with explicit type arguments, but it may still be worth it for the simplicity and improvement in error reporting that it brings. Re-running tests to see the effects.

I'm still very wary of Awaited<T>. The definition of Awaited<T> has some strange effects when not in strictNullChecks. @jablko also looked at this in several PRs (#35284, #33707, #33055) and made a note here: https://github.com/microsoft/TypeScript/pull/35284/files#diff-a6b488d9bd802977827b535a3011c1f3R1381
Basically, Awaited<undefined> and Awaited<null> return unknown when not in strictNullChecks, which seemed surprising.
I'd also looked into adding Awaited<T> into the core library with a definition that was intended to give a more correct answer WRT non-promise "thenables" in https://github.com/microsoft/TypeScript/pull/21613:
type Awaited<T> =
    T extends { then(onfulfilled: (value: infer U) => any): any; } ? U :
    T extends { then(...args: any[]): any; } ? never :
    T;

This definition represented the minimal case that was consistent with await (aside from recursive unwrap), as the following is currently an error in TypeScript:
declare const p: { then(): void };
async function f() {
  await p; // Type of 'await' operand must either be a valid promise or must not contain a callable 'then' member.
}

Ah, disregard the comment about undefined, as I see that it is included in your changes.
We could theoretically bake in a few levels of nesting. Its fairly trivial to result in Promise<Promise<T>> due to inference, though higher levels are much less frequent. Until such time as we can reconsider awaited, perhaps we should consider a definition like this:
type Awaited<T> =
    T extends undefined ? T :
    T extends PromiseLike<PromiseLike<infer U>> ? U :
    T extends PromiseLike<infer U> ? U :
    U;

While more verbose, it does handle both the common cases (T, Promise<T>) and the frequent doubly-nested promise case due to inference (Promise<Promise<T>>).

This can probably be closed now that https://github.com/microsoft/TypeScript/pull/45350 has been merged.

This experiment is pretty old, so I'm going to close it to reduce the number of open PRs.


Render method is not rendering transition as in Vue2

Version
3.0.9
Reproduction link
https://codesandbox.io/s/vue3-transition-render-inkuj
Steps to reproduce
Render a transition element with the render's 'h' method. Use 'transition' as string parameter for the first parameter given to the h method like h('transition').
What is expected?
The DOM should only display the content of the transition element, including all the transition functionality.
What is actually happening?
A  tag is rendered containing the child component.

To render a transition via h method in Vue2 h('transition') had to be used (see also https://vuejs.org/v2/guide/transitions.html#Reusable-Transitions with the 'createElement' example). Now with Vue3, h(Transition) (component imported from vue) needs to be used. Either this is a bug or it's an undocumented breaking change.
(initially discovered when working with vue-test-utils-next https://github.com/vuejs/vue-test-utils-next/issues/471)

Duplicate of https://github.com/vuejs/vue-next/issues/826#issuecomment-598207464

@posva thanks for the hint to the other issue. Shiuld this be added to the documentation and also be mentioned in the Breaking Changes somehow?

It's documented: https://v3.vuejs.org/guide/migration/render-function-api.html#_2-x-syntax-4


docs: remove distinctState from implementing undo history recipe

Checklist

[x] Is there an existing issue for this PR?

No

[x] Have the files been linted and formatted?

What docs page needs to be fixed?

Section: Recipes
Page: Implementing Undo History

What is the problem?
distinctState() has been deprecated in the redux-undo library used with this example
What changes does this PR make to fix the problem?
Removes the distinctState in the code example, and removes the sentence relating to distinctState.

Thanks!

Thanks!


Remove broken unicode character

Still yet to figure out why these don't render.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/core.c
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/core.c
0.00% <0.00%> (ø)


Support for the experimental syntax 'nullishCoalescingOperator' isn't currently enabled

I am getting the following error when I try to run on an iOS simulator.
I tried adding @babel/plugin-proposal-nullish-coalescing-operator to the plugins section of the babel config, but did not work.
Assistance getting this resolved would be appreciated.

error: bundling failed: SyntaxError: /onfido-sdk-react-native-sample-app-master/node_modules/react-native/node_modules/react-native/Libraries/LayoutAnimation/LayoutAnimation.js: Support for the experimental syntax 'nullishCoalescingOperator' isn't currently enabled (47:23):
45 |   UIManager.configureNextLayoutAnimation(
46 |     config,

47 |     onAnimationDidEnd ?? function() {},
|                       ^
48 |     function() {
49 |       /* unused */
50 |     },

Add @babel/plugin-proposal-nullish-coalescing-operator (https://git.io/vb4Se) to the 'plugins' section of your Babel config to enable transformation.
at Object.raise (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:3831:17)
at Object.expectPlugin (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:5148:18)
at Object.parseExprOp (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:5763:16)
at Object.parseExprOps (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:5739:17)
at Object.parseMaybeConditional (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:5702:23)
at Object.parseMaybeAssign (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:5647:21)
at Object.parseMaybeAssign (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:2621:18)
at Object.parseExprListItem (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:6940:18)
at Object.parseCallExpressionArguments (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:6070:22)
at Object.parseSubscript (/onfido-sdk-react-native-sample-app-master/node_modules/@babel/parser/lib/index.js:5965:29)

After hours wasted trying to get this to work, of course it resolves itself 1 min after submitting this issue. I suspect my packager was not running from the correct folder. Not sure how or why.

I am also having this problem, but even after spending an hour it didn't resolve itself. How can i make sure that the package manager is running from correct folder ? ( I want to open this issue again, may be after 1 min of opening the issue, it will resolve )


Typo "Azure data factory"→"Azure Data Factory"

https://docs.microsoft.com/en-us/azure/data-factory/v1/data-factory-spark

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @hyoshioka0128. Thanks for contributing to the documentation.
Microsoft internal style guidance for referring to an instance of Azure Data Factory vs. the name of the Azure service seems to apply here (Lowercase when referring to an instance (something built using) the service: data factory). We'll close the PR. Thanks.


courier idea

use these guys

remember the mission where you have to go to candle hall and pretend to be the stormcloak courier, yeah 1 is that mission here and 2 use them as the couriers for the letters from commanders

Added to enhancements list.
Essentially I plan to incorporate this https://trello.com/c/4tCOSEk8/42-patch-for-https-wwwnexusmodscom-skyrimspecialedition-mods-81546


Add no_mx_lookups to smtp config

Hello,
I added no_mx_lookups option to smtp config.
This option can help when you don't want to connect to the returned mx's of relay.
The no_mx_lookups is not mentioned in the gen_smtp README, but see https://github.com/Vagabond/gen_smtp/blob/master/src/gen_smtp_client.erl#L136 for more details.
It's now possible to pass this option, but making it clearer in the documentation can help other people.
What do you think? Would it be valid?
Thanks.

I'm not sure about adding it to the documentation, if gen_smtp doesn't mention it.
👍 on adding the option though. @stevedomin what do you think? FYI, the relevant code has been there for at least 7 years. (I couldn't be bothered to blame any further)

I'm ok with having it in the docs, it's a well-known option of gen_smtp, despite being undocumented.

Thanks @sergioaugrod!!


Allow to specify database in mysql connection

The MySql connection should allow to specify a database. This allow queries that were written like this:
SELECT * FROM my_database.my_table

to be written like SELECT * FROM my_table.
Thanks in advance (excellent plugin BTW)

Hi!
Glad you like it :D
I'll look at getting this done when I have the time

[ ] Allow the connection to work with and without a database
[ ] Test the generation of the mysql system command. i.e. is it contstructed properly with and without a database?
[ ] Make sure we don't need to prefix a database in SQHExecute and friends

Hey @petobens
This is done, care to try it out?
https://github.com/joereynolds/SQHell.vim/commit/d1cd6cfd7c5aa84259d2b759cd51f12673339420
Thanks!

Seems to work great! Thanks


choosing aonther month or year doesnt work

when i choosing another month or year is changing only the day but not the month and year.
even in the demo  - https://react-jewish-datepicker.js.org/

Hi user123.3,
Thank you for finding the bug and a special thanks for reporting it.
I have fixed it, added tests and published a new version 1.0.5.
Thank you and have a good day
Shmulik


AnyHashable type-erasing behaves differently on Linux

Description
On the linux build of Swift, AnyHashable does not appear to have the type-erasing semantics that it does on macOS and iOS. On those platforms, any type of integer converted to an AnyHashable can then be converted to any other type of integer (providing it fits), whereas on linux, you can only convert it back to the original type.
Reproduction
let i: Int32 = 1
let a = i as AnyHashable
let oi = a as? Int8 // This conversion succeeds on macOS/iOS, fails on linux

Expected behavior
Expected the as? Int8 to succeed and return Optional<Int8>(1) on all platforms. It only succeeds on macOS and iOS, and returns nil on linux.
Environment
Swift version 5.10.1 (swift-5.10.1-RELEASE)
Ubuntu 22.04.5 LTS
Additional information
Tested using the following github actions job: https://github.com/tomsci/LuaSwift/pull/7
The issue was found during the development of https://github.com/tomsci/LuaSwift/pull/6 which necessitated a lot of additional code to compensate for the difference in behaviour of AnyHashable.

I believe this is a side-effect of Foundation NSNumber support.  NSNumber supports casting to/from every numeric type, and as a side-effect, allows certain other casts to do the same.

Yikes that's a pretty big side effect, modifying the entire runtime's behaviour to support a single Foundation type! It's not like one can avoid using Foundation (in any non-trivial project) and Foundation does exist on Linux but doesn't exhibit this behaviour (I ran the same unit tests on both platforms, explicitly importing Foundation on both) so is the bug here that the linux implementation doesn't faithfully replicate this quirk?
If I'm understanding that right, it's very weird to hear that the way the language is supposed to behave isn't the way it actually behaves in 99% of projects. Is this formalised somewhere? Is the NSNumber modifying other casts behaviour considered a bug? It makes me wonder, why are integers castable to and from NSNumber in Swift? Toll-free-bridging made sense in Objective-C to and from CoreFoundation but I can't really think of any reason why I'd want this in Swift code...?

Differences between Foundation on Linux and macOS should be reported against Foundation, I think.  CC: @parkera


OpenVPN and Homebridge

When OpenVPN and its interfaces / settings is started before homebridge, homebridge does not bind to any network interface and is not reachable.
Expected Behavior
I expect homebridge to start and bind to the network interfaces independent of OpenVPN.
Current Behavior
see above
Steps to Reproduce (for bugs)
see above
Output if homebridge is started before Openvpn
netstat -an | grep 51826
tcp        0      0 <IP_ADDRESS>:51826           <IP_ADDRESS>:*               LISTEN
no output if openvpn is started before, no binding to any interface, not reachable.
Versions

Homebridge: homebridge --version
0.4.45

Node:       node --version
v8.11.1

OS:
Raspberry Pi on Debian 9.6

I think this is a duplicate of #1192 and #2162


Issue#07: Refactoring home fragment

Home fragment requires refactoring :

change the horizontal news recycler adapter to accept just 10 news item. At the tenth element show the see more button rather than scroll to up button.
create the all news fragment , accompanied with search view

Handled by commit 3c06900d . Goof isssue


How to fine-tune the model?

Hey Team,
Thank you for this project! It's been a great help for a task I'm working on. Unfortunately though, the model isn't very accurate for a bunch of stamps that we're trying to detect.
Is there a way in which we could get access to the training module or fine-tune the model further?
Thanks!

Hi @jaipal-staple, the detection model is just a yolov5 model. You can use it to train your own model.


Polar to rectangular and vice versa calculator

Description
Design a calculator which would convert polar co-ordinates to rectangular and vice versa.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[X] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@Rakesh9100 Please assign me under JWoC 24

assign it to me under IWOC plz

Please assign this issue to me under JWOC

okay !!
@Rakesh9100  But it has only rectangular to polar conversion and not polar to rectangular. So can I add polar to rectangular to polar in the existing calculator ?

Yes, you can add vice versa in this existing calculator @pranjal12-web


Add new function RTC_PCF8523::lostPower()

This function mirrors the existing RTC_DS3231::lostPower()
The PCF8523 sets an Oscillator Stopped (OS) flag anytime its oscillator has stopped or been interrupted. This flag offers a way to verify clock integrity, and to know if power was lost.
To purposely set the OS flag, remove the battery and disconnect the RTC from external power supply for ~1 second or more.
When power is re-applied via battery or supply, the OS flag will remain set, even as the oscillator starts and stabilizes.
RTC_PCF8523::lostPower() returns true if the flag is set, and false only after it has been un-set, for example with RTC_PCF8523::Adjust()
This new function is somewhat similar to an existing function:
RTC_PCF8523::initialized() returns true when power management has been configured, for example with RTC_PCF8523::Adjust(), and false when power management configuration is found in 'standby mode', which is the default after power loss.
For many purposes they may be substitutes for each other, but note the inverted relationship of their return values.
These changes tested on Feather M4 Express and Arduino Mega with PCF8523-equipped Adalogger FeatherWing.
From the PCF8523 datasheet:
https://www.nxp.com/docs/en/data-sheet/PCF8523.pdf#page=20
<IP_ADDRESS> Oscillator STOP flag
The OS flag is set whenever the oscillator is stopped. The flag remains
set until cleared by using the interface. When the oscillator is not running, then the OS flag
cannot be cleared. This method can be used to monitor the oscillator.
The oscillator may be stopped, for example, by grounding one of the oscillator pins, OSCI
or OSCO. The oscillator is also considered to be stopped during the time between
power-on and stable crystal resonance. This time may be in a range of 200 ms to 2 s,
depending on crystal type, temperature, and supply voltage. At power-on, the OS flag is
always set.
fixes #128

Hi @drak7 et al,
This PR is really all about 38a17a9. It touches a file that is also in my previous PR #157 which hasn't been merged. So I branched from there attempting to avoid a 3-way merge and an untested code combination going into master, should both PRs be accepted. In hindsight I'm not sure if that was the right way to go. These are trivial changes but I'm trying to learn how to do things right! I'm happy to rearrange things to make it easier on your end, just let me know. Thanks! -Colin

I'm self-taught and pretty bad at reading electronics data sheets but this looks correct. Thank for the great explanations in the commit message and here; very professional.

Looks like it will merge fine with #157 so no problem there.
The 200ms to 2s startup time stuck out to me, it might be worth noting in the library and the example. If the host runs adjust() before the oscillator stabilizes you could end up with OS = 1 even though the oscillator is running and you told it to clear that bit.

@drak7 good point. That could be aggravating! I'll double check my understanding, think about how to word it, and push an update to this PR. Thanks.

Just a note in the comments explaining it would be good, it probably won't affect most users but if someone is depending on the OS bit they could run into that issue.
Thanks!

@drak7 Please feel free to update/edit/move the comments I added just now.
I did try to trigger the scenario I described but I wasn't able to. Hopefully that means it's an unlikely one, but if somebody does hit it, they'll have a hint about it now.


Node 0.6 compatibility

Just needed to bump a couple of versions in package.json. All tests pass.

Yeah, sure. Out of curiosity, what version of Node did you test on?

Thanks! Using v0.6.9 here.


V12/client esm.applications.dice.roll resolver

Resolves #2611

I've fully polluted this pull request - I'm going to try to clean it out


Streamingly read user-logs.

Use akka-streams and its various connectors to read a user's log file in a streaming fashion.
This will not contribute to memory-pressure relief as all the logs still need to be read into memory to write it to the database due to the existing schema.
Alters the existing limit calculation in that the limit is applied to the JSON structure of the log-file rather than only the log message. As a consequence, the perceived log-limit will be lower than the actually defined log-limit.

PG3 1307 🔵

PG4 1032 🔵

As subsequent improvements, as already noted: consider eschewing the JSON parsing with a bespoke parser because the format is quite trivial. Second, for the corner case where the last log line is truncated, consider amending it to the activation logs so that it is not lost. Should we open issues/enhancement requests if you concur?

@rabbah as discussed in person, I don't see much value in adding a truncated last-line (note that we apply the log-limits on the entire JSON structure now, so the user has no way of knowing the exact translation of her log-lines vs. her log limits anyway).
Eschewing the json-parser we can do if necessary. While the format is simple, it ties us even closer to its implementation details (like order of fields).

The docker log driver will flush the bytes comprising the log line but does not necessarily flush a fully formed json object - we've observed this in production for example where eventually with retries the parsing will succeed, or times out. This could be exacerbated by logging large volumes to a single log line (since we don't control when docker does it buffer flush, or, how the action does its logging). For an end user, we should strive to pass on as many of the logs as possible, and I don't see the reason not to do that when we are forced to truncate a single line.

Eschewing the json-parser we can do if necessary. While the format is simple, it ties us even closer to its implementation details (like order of fields).

For docker versions, which we change infrequently, I posit these formats change infrequently enough that if the performance gains are significant, it becomes worthwhile.

PG3/1935 🔵

Merged as https://github.com/apache/incubator-openwhisk/commit/83982f6687252e793c3e0862e8a23a656f76fc2c.


Version 1.2.2 unreleased

Hi guys
In the readme and everywhere states to use 1.2.2 but it looks like this version is not release, latest on https://pub.dartlang.org/packages/fluro is 1.2.1
Was it released? Was a fail release? Or you just bumped the version for the next development iteration? Should bump the version in readme?
Sorry for the poor issue, but I guess you got me :-)

+1

+1 on this. Can't use this until the replacement fix is issued! (Unless I hook into the git directly in my yaml)

version 1.3.0 has now been published. sorry for the delay.


Enhanced Prometheus Remote Storage API

As part of Google's continued commitment to the open source community, Kubernetes and all the CNCF projects, the Google Cloud Management team wants to support seamless, highly-available, and scalable ingestion for Prometheus clients. Our team wants to work closely with the Prometheus community to improve Prometheus' interoperability with public cloud services, by extending its ability to ingest data into other monitoring systems with rich querying and alerting capabilities.
Specifically, we are proposing to extend the Remote Storage API and the data pipeline that flows into it to support the full Prometheus (and eventually OpenMetrics) data model. We understand that this will require ongoing maintenance and we are committed to contribute engineering time to ensure long-term success. We believe that the common extensibility framework we propose will be easily reused by other major cloud providers.
Last, but not least, we see working with the Prometheus community as an extension of our ongoing collaboration on the OpenMetrics standard.
We look forward to engaging with the Prometheus maintainers to further advance Prometheus adoption and benefit the overall open source community. Google would be happy to host a conversation to discuss in more detail and outline possible next steps, whom should we be working with to make that happen?
Mini-design
Many of the technical use cases for wide cloud integration are already addressed by the Prometheus client but not the Prometheus server. We have looked at the remote storage API in Prometheus server, and we determined that Prometheus server and its remote storage API will require enhancement to meet public cloud use cases (see the table below for a full set of requirements). We are willing to contribute the changes needed to make an integration via the remote storage API viable.

Property
Prometheus client exposes
Prometheus server exposes

Element type (int64, double)
double
double

Metric kind (gauge, cumulative/counter, distribution)
Yes
Nothing

Metric and label description
Metric description
Nothing

Samples with monotonically increasing timestamps
Yes, assuming client exposes monotonically increasing timestamps.
Yes, apparently. QueueManager states the need to preserve this invariant on resharding.

Reset timestamp for cumulative metrics
No.
No.

Atomic histogram
Yes, as multiple metrics that can be combined with expfmt.TextParser.TextToMetricFamilies
Sometimes. The metrics that make up a given histogram aren't guaranteed to arrive in a single WriteRequest (see previous row).

Inventory data from discovery stage
N/A
Yes, subject to Prometheus relabelling. Integrations would benefit from access to the unfiltered inventory data.

As I said when you last asked about this 2 months ago, if you want to do this the way to integrate is via the client_golang parser which can be found at https://github.com/prometheus/common/tree/master/expfmt - not via Prometheus itself. It already provides you with everything you ask for, and does not require the deeply invasive changes that what you request implies.
Prometheus is intended to be a monitoring system in and of itself, not merely as the ingestion component to other monitoring systems. Remote write is intended primarily as a way to facilitate long term storage for Prometheus, and does not require the features you mention for this goal.

I think the fundamental point you are trying to make here @brian-brazil is that the remote API is not intended to be stream-out protocol for SaaS integrations to begin with. We are certainly not making this clear enough and see more and more solutions being built onto this by now. It simply results in multiple semantical incorrectness.
So the actual discussion we should be having is what a proper API for that use case would look like and where it could fit. If we don't provide a way to do this, people will keep abusing the remote API.
The metric metadata aspect is arguably a distinct issue. I know you are strongly against it @brian-brazil  but there are multiple people, @beorn7  and me included, that see value in it, so we should discuss it.
It's perfectly okay to be best effort, e.g. in the face of changes, but having something would be valuable.

The metric metadata aspect is arguably a distinct issue. I know you are strongly against it @brian-brazil but there are multiple people, @beorn7 and me included, that see value in it, so we should discuss it.

There's certainly debate there, but even were we to resolve that then the remote API would be the last place to get that information. Doing it in remote API first would be the tail wagging the dog, as Prometheus currently has no use for such information from remote storage and the bandwidth&performance implications would be problematic.

So the actual discussion we should be having is what a proper API for that use case would look like and where it could fit. If we don't provide a way to do this

We already have that in the parsers, which we already provide for exactly this use case - and indeed encourage their use by the various other monitoring systems out there using our format.
The Stackdriver use case here is that they like the format, but not the server. Thus they should use the format directly rather than trying to turn Prometheus into Stackdriver.

The metric metadata aspect cannot be ignored if OpenMetrics or similar efforts were really meant to work across vendors and clouds. Otherwise you end up with mishaps like the Mars Climate Orbiter and similar costs or worse by data and unit misinterpretation. Grafana has very strong Units of Measurement support, it goes far beyond what Prometheus offers today. And a true open metrics standard will likely have to follow that example if it wants to be successful.

This issue is unrelated to OpenMetrics, as this issue is about Prometheus internals rather than that OpenMetrics format which we will ingest.

Even if it's unrelated to OpenMetrics, I would say storing metadata is advisable.

Hi @jkohen, we were going through this issue during our bug scrub. Given you already resolved this with a sidecar, do you think this is still relevant?

@gouthamve oh yeah, thanks for asking. The design we implemented with help from Brian and others is documented at https://github.com/Stackdriver/stackdriver-prometheus-sidecar/blob/master/docs/design.md


[8.x] Include between hours in Cron expressions

Include hours of 'between' range in the Cron expressions--where practical--to aid packages and services such as spatie/laravel-schedule-monitor.
For example this makes it possible to call ->hourlyAt(30)->between('5am', '10pm') and get an expression like 30 5-20 * * *.
This should be a low risk change since the current behavior of a call like ->between('5am', '10pm') already produces a less consistent Cron expression such as * * * * * instead of * 5-20 * * *.

Can it handle 24-hour time?

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Space travelers Hub React Redux kanban

Hello,
Link to project
We are two members in this project
George827 for rocket section.
Tanveerisonline  for mission section.

Hi @george827 @tanveerisonline 👋,
Status: Approved 🟢
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

Setup Kanban board properly ✔
Each student has the required tasks assigned to them ✔

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


[WIP] Add https egress gateway description

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vadimeisenbergibm
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
Assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Closing since there will be no Istio-0.8.1, submitted a PR for Istio 1.0 instead.


Merge changes from KrystianD/modbus_client

Thank you @tombolano for your great work! Your work has triggered me to work more on this project more (especially I god mad when I saw merge address function doesn't work properly.. :) I created unit tests and fixed few more use cases). I haven't yet converted it to support packaging but will definitely do as well, just need to find some time on adjusting my systems which are using this project.

Thanks @KrystianD, this code is really nice since it simplifies a lot the usage of pymodbus, i was needing to read several data from different modbus devices and doing it directly with pymodbus is really cumbersome. I am glad that i could help.
I saw some other things in the code that i think should be changed, I will open an issue on your repository to explain them.


Empty step_stats from context.export_run_metadata() in TF 2.1

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Google Colab

As sessions are no more available in TF 2 API we are using context.enable_run_metadata() and context.export_run_metadata() to accure run_metadata.step_stats which then we feed to timeline.Timeliner to export tracing information about session execution and visualise it usgin chrome://tracing. This approch worked well with TF 2.0 but once we updated to 2.1 run_metadata.step_stats appears to be empty.
Here is code which acquires and prints step stats:
TF 2.0: https://colab.research.google.com/drive/1Jsk7Dn_gTd3xCTTxgQPx3bJvza4oRu1t
TF 2.1: https://colab.research.google.com/drive/1JQ7rqyH5VOAmpHbjMuLGYLwU9dJ7xwk2
I know that according to docs we should use summary.trace_on or profiler_client .start_tracing to acquire tracing information, however, there is seems an issue with GPU tracing https://github.com/tensorflow/tensorflow/issues/34844

probably a duplicate of 34844
can you make sure that running "!ldconfig -p | grep cupti" in your colab?

Here is the output of !ldconfig -p | grep cupti
libcupti.so.10.1 (libc6,x86-64) => /usr/local/cuda-10.1/extras/CUPTI/lib64/libcupti.so.10.1
libcupti.so (libc6,x86-64) => /usr/local/cuda-10.1/extras/CUPTI/lib64/libcupti.so

So seems 34844 has been already fixed in colab
But no step stats
Anyway after using fix from 34844 we are able to get GPU profile using tensorboard, so this issue is not so critical anymore (yet traces converted from step_stats are more informative then those in tensorboard)

unfortunately, profiler team don't support step_stats anymore in favor of new "tf 2.0 profiler".

We have just released a new profiler in TF 2.2 rc0.
https://tensorflow.org/guide/profiler
One of the profiler output is trace.json.gz, that can be directly upload to chrome://tracing to visualize.
Please try if the new profiler fixes your issue.
If it doesn't, we will follow up with you.
thanks

Verifies the fix in tf-nightly works in this colab.
https://colab.research.google.com/gist/gadagashwini/2c9946a562d22127690069c4013da8bc/untitled449.ipynb
Cherrypick request sent out:
https://github.com/tensorflow/tensorflow/pull/37599

@dtim1985  it seems the issue is resolved  with the update.Please feel free to reopen the issue if you still have a concern. Thanks!


Bump jenkins/jnlp-agent docker version

Build failed; the context from the latest run is:
Expand to view
[2019-09-20T12:00:32.145Z] Pull request #39 opened
[2019-09-20T12:00:32.151Z] Connecting to https://api.github.com using jenkinsadmin/****** (GitHub access token for jenkinsadmin)
[2019-09-20T12:00:32.580Z] Connecting to https://api.github.com to check permissions of obtain list of olblak for jenkins-infra/charts
[2019-09-20T12:00:33.071Z] Obtained Jenkinsfile from 3cde656def1eaa763aec10e88a8e02812cf9f208+61a332b2a3c82d8d86b2dbf7429be474401a8072 (2e81e48ff72809d9e1f3504288c4badec7e0fc64)
[2019-09-20T12:00:33.071Z] Running in Durability level: MAX_SURVIVABILITY
[2019-09-20T12:00:33.102Z] Loading library pipeline-library@master
[2019-09-20T12:00:33.102Z] Attempting to resolve master from remote references...
[2019-09-20T12:00:33.218Z] Found match: refs/heads/master revision 478d9a971e23d8ec5ca57019cd3f478f42b6968e
[2019-09-20T12:00:33.225Z] No credentials specified
[2019-09-20T12:00:33.227Z] Cloning the remote Git repository
[2019-09-20T12:00:33.227Z] Cloning with configured refspecs honoured and without tags
[2019-09-20T12:00:33.639Z] remote: Enumerating objects
[2019-09-20T12:00:33.639Z] remote: Counting objects
[2019-09-20T12:00:33.639Z] remote: Compressing objects
[2019-09-20T12:00:33.640Z] Receiving objects
[2019-09-20T12:00:33.748Z] Resolving deltas
[2019-09-20T12:00:34.211Z] Updating references
[2019-09-20T12:00:34.238Z] Fetching without tags
[2019-09-20T12:00:34.275Z] Checking out Revision 478d9a971e23d8ec5ca57019cd3f478f42b6968e (master)
[2019-09-20T12:00:34.342Z] Commit message: "Merge pull request #112 from jenkins-infra/INFRA-2243-fix"
[2019-09-20T12:00:34.344Z] First time build. Skipping changelog.

Powered by the Comment Logger


It should be needed to specify the exact certificate name when Encrypt credentials.

In Step17 Encrypt credentials, it should be needed to specify the exact certificate name.
Because there are two credentials to use encrypt, axdataenciphermentcert and DataEncryption.
I think this is confused to understand.
Thanks for reading.

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

ID: 14409653-d5a8-bf1b-8772-97832acfe6af
Version Independent ID: 331d5d92-1601-ed2e-0dd9-4d68beddebff
Content: Set up and deploy on-premises environments (Platform update 41 and later) - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/deployment/setup-deploy-on-premises-pu41.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @faix
Microsoft Alias: osfaixat

@ans1148, thank you for providing this feedback.
@faix, please consider updating the content based on this feedback.

This content has been updated and will be published later today!


Handle receiver dropped connection during send properly.

Close connection and requeue data safely.
See for thread safe queue swap http://stackoverflow.com/questions/2623086/is-a-variable-swap-guaranteed-to-be-atomic-in-python
Handle here https://github.com/Storj/storjnode/blob/develop/storjnode/network/service.py#L276

outdated


'Undelete' action is enabled for one active blob folder

Storage Explorer Version: 1.8.1_master_20190619.4
Platform/OS: Linux Ubuntu/macOS High Sierra/Windows 10
Architecture: ia32/x64
Commit: 952cf5dc
Regression From: Not a regression
Steps to reproduce:

Expand a non-ADLS Gen2 storage account -> Blob Containers.
Create a new blob container -> Upload a folder which contains at least one file to it .
Right click the uploaded folder and check it's context menu.

Expect Experience:
'Undelete' action is disabled.
Actual Experience:
'Undelete' action is enabled.

This is expected. We always show undelete enabled for a folder because we don't do any checking to see if there are deleted blobs in it. Closing as by design.


Add support for L2 CAT

Implement support for L2 cache allocation. Most of the patches in this PR are about refactoring and renaming existing code. The last patch actually adds support for L2.

typo in commit message of f6b5afab73378ed35e858092b0c525dc49e29d3d: 'an attempty'

I spotted two small typos in commits/comments. Otherwise looks really good to me.

typo in commit message of f6b5afa: 'an attempty'

Thanks for spotting this. Fixed


Add the capability to determine the encoding of a resource by using BOM

/cc @churkin @miherlosev

FPR

\r-

FPR

\r-

FPR

ping @churkin @miherlosev

lgtm

\r-

FPR

Just some minor issues left.
\r-

FPR

\r-

FPR

lgtm
@churkin Seems like your PR with constants will require rebase on top of this and we have a new constants now (e.g. for charset meta)

@churkin FPR

lgtm


AVRO-1878: Add support for field aliases to ResolvingGrammarGenerator.

We introduced automatic code formatting. For more info see the "How to contribute" page. This  probably affected this PR can you please rebase it.


invalid tanka.dev/environment label on windows

When enabling injectLabels on windows tanka generates an invalid label value e.g. environments\default
https://github.com/grafana/tanka/blob/master/pkg/spec/v1alpha1/environment.go#L49

#511 changes the labels to a hash, so in future version this should be resolved.


Close the figures when testing them, to avoid memory leak

Fixes https://github.com/Qiskit/qiskit-terra/issues/4645
~This follows the advice in https://stackoverflow.com/questions/16334588/create-a-figure-that-is-reference-counted/16337909#16337909 to avoid leaving figure references dangling.~

The only thing I need to check here is whether environment style settings are preserved for figures that are created with the object oriented api instead of with pyplot (thinking like a dark theme in jupyter etc). I don't think it's a problem but I normally use pyplot so I just need to check.. Otherwise I think this is fine.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Luciano Bello seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry for the delay, it fell off my radar and I forgot to circle back and check this. I was playing with this a bit, and I think my early concern was justified. Doing something like:
`circuit.draw('mpl').show()` does not work with this PR, it raises an exception:

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-6-3f274e91c9fa> in <module>
      1 with plt.style.context('dark_background'):
----> 2     qc.decompose().draw('mpl').show()

~/git/qiskit/qiskit-terra/.tox/py39/lib/python3.9/site-packages/matplotlib/figure.py in show(self, warn)
    405         """
    406         if self.canvas.manager is None:
--> 407             raise AttributeError(
    408                 "Figure.show works only for figures managed by pyplot, "
    409                 "normally created by pyplot.figure()")

AttributeError: Figure.show works only for figures managed by pyplot, normally created by pyplot.figure()

which is basically my earlier concern, creating figures outside of the pylplot mechanism means the figure isn't connected with the normal user pyplot based workflow.

You are right.
The right way is to close the figures while testing.


python3Packages.flux-led: 0.24.24 -> 0.24.25

Motivation for this change
Update to latest upstream release 0.24.25
Change log: https://github.com/Danielhiversen/flux_led/releases/tag/0.24.25
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 146745 run on x86_64-linux 1

2 packages built:

python38Packages.flux-led
python39Packages.flux-led


fix known account class for braavos

update known account class

Thanks for the PR! I'm not sure we should add a AccountVariantType variant for this though? These variants exist only to deal with account classes with different interfaces so that they need to be treated differently when fetching. If the new Braavos class exposes the same interface (as far as our use of it is concerned, of course), we can just add the hash.
I will have to check which is the case though.

Branch does not compile.

Superseded by https://github.com/xJonathanLEI/starkli/commit/d2c3342266c6a7d21fbe7d7eccc9211514718857.


use virtual potential temperature instead of virtual DSE

Purpose

https://github.com/CliMA/Thermodynamics.jl/commit/cda74a802314b436eb963e7e38445be4e54b27f0 changes the definition of virtual_dry_static_energy, which breaks the surface flux calculation, but is what we want for virtual DSE definition. In surface fluxes we should use density to calculate buoyancy, but as an intermediate step, This PR changes virtual DSE to virtual potential temperature when calculating buoyancy and Richardson number.
To-do

Content

[ ] I have read and checked the items on the review checklist.

You probably also have to flip the compat for Thermodynamics
(and also bump SF version)

You probably also have to flip the compat for Thermodynamics
(and also bump SF version)

Sounds good. I'll do that after we make sure this fix is correct.

We will change Thermodynamics instead and come back to this once we think more carefully about the actual physics.


Move Operator type into own file, and use in environments.jl

This is a bit out of date and H::Operator is incorrect in the function signatures. Do you want to update this? I'm planning a refactor to how Operator and the Hamiltonians work


Execute local operation after remote operations have finished

Hiya,
I'd like to be able to run a local operation after the remote operations, but before the ConDep process exits. Adding a custom local operation appears to execute right before the remote operations begin. I want to execute it as a local operation because I want it to run one time. I can do a workaround where I execute it as a remote operation and restrict its execution based on a server predicate, but it would be better if I could insert a local operation into the overall sequence at the end.
Is it possible to "bookend" the overall execution sequence like this, or is the local -> remote sequence hard-coded?
Thanks!

This is a limitation/simplification in the execution sequence right now
(aka hard coded). Would an option to have it execute at the end instead of
beginning be sufficient? Then it would execute local operations in the
beginning by default, but by passing in an option you can have it execute
it in the end. Would that work for you? If so I'll look into adding this
option today.
Generally I will look into a better way of controlling the execution
sequence in the future.
On Thu, Mar 26, 2015 at 7:32 PM, Nicholas Vander Ende <
<EMAIL_ADDRESS>wrote:

Hiya,
I'd like to be able to run a local operation after the remote
operations, but before the ConDep process exits. Adding a custom local
operation appears to execute right before the remote operations begin.
I want to execute it as a local operation because I want it to run one
time. I can do a workaround where I execute it as a remote operation and
restrict its execution based on a server predicate, but it would be better
if I could insert a local operation into the overall sequence at the end.
Is it possible to "bookend" the overall execution sequence like this, or
is the local -> remote sequence hard-coded?
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/condep/ConDep/issues/28.

--
/Jon A.

Thanks for the quick reply!
I think that option would probably sort it out - I've solved my specific problem in another way (using a separate executable), so no rush. It would be great to be able to insert operations into an arbitrary part of the sequence, though!

Can now confirm this is possible in v 4.0, wich we are getting very close to release. Closing this for now.


Get back to original URL when sent to the login page

When you try to access a specific page directly (let's say https://portus-web/teams/4) and you're not logged-in, you are redirected to the login page. After a successful login, you land on the homepage, and not the page you were trying to access initially.
I think you should be taken back to the page you were intending to go first.
Regards,

Makes sense. Thanks :)

Hmm I'm not redirected at all. I'll got an 'successfully logged in' message and have to remove /users/sign_in manually to go to the dashboard page. Is this a settings or something?

@bertoost this is not happening to me on master (and honestly I've never thing anything like this on previous releases). Which version are you using?

@mssola I am using v2.4.2 as docker image.

Look.. When logged out, I'll end on the sign-in page;
Logging in again will stay on the sign-in page with a flash message.

I manually have to remove the url part to go back to the dashboard.

@bertoost I tested with both master and 2.4.2 and this is not happening.
If you are signed in and try to visit /users/sign_in it redirects you to the index page saying that you are already signed in. So it's pretty weird that you have this behavior. I used the latest versions of Chrome and Firefox.
Did you try in another browser? Try also to clean up your cookies.

Maybe it's because it's behind a reverse proxy? (Traefik)

Today I thought.. let me google this, ended up with finding this issue 😄
It's still the issue. Does someone know it's because it's behind a proxy? (Traefik)


npm tarbal URL is http

So, I'm trying to get to the bottom of this.
In my case 2 specific packages change my npm-shrinkwrap.json link to registry.npmjs.org to http. One of them is compression.
Whoever makes the releases can you check what the value of npm config get registry is on their machine?
Thanks!

$ npm config get registry
https://registry.npmjs.org/

Very weird. We'll see if we can find the root cause.
Thanks for confirming!

No problem! I don't think my registry value really is stored anywhere. Perhaps try completely clearing all the npm cache locally npm cache clean --force and see if that helps? Not sure if the cache remembers it getting downloaded from http at some point on your machine, idk. Just guessing here. The npm folks could probably say exactly why npm is putting http: for the dep in your shrinkwrap, though.

Yup, I have already done all this. This issue isn't new, it happens for some months now. But it only happens for specific packages for me, that's why I thought I'd ask.

All I do is type "npm publish" and then enter my 2FA code at the prompt.

OK - This is a dumb question, but you use a recent-ish version of NPM when you run that command, right?

Yes, 2FA code prompt support was not added until npm 5.5.1. Now, which specific version I used when I published 3 months ago I cannot know for certain, but I keep it as up-to-date as possible, so it would be a reasonable version for the time of the publish date.

Looking here: https://registry.npmjs.com/compression
The 1.7.1 release has https://registry.npmjs.com for the tarball URL and the 1.7.2 release uses http://registry.npmjs.com for the tarball URL. Did you/the same person prepare both releases, and did you/they use the same procedure for each release?
This is weird and it's almost certainly not a problem on your end, but thanks for writing back, as this should help narrow down the issue.

Yea, I've been the only one publishing this particular module and I always do the publishing from the same machine (git development may be on different machines, though). This is because my registry token is only on a single machine for security reasons. That machine is where I ran https://github.com/expressjs/compression/issues/140#issuecomment-392128763 on and it doesn't change too often since I just use it for publishing (it's a virtual machine).

OK, thanks! This has been really helpful.

No problem. There are probably some changes I can publish, so I will publish a new version if there's any dep update pending here and we'll also be able to see if that resolves this issue for some reason. I also have some projects with package-lock.json files and compression 1.7.2 does have a https link, though I see the same behavior with other modules: running npm install changes some of the URLs to http from https even though there are no version changes in any way. I've seen the issue off-and on and sometimes seems to change which modules are getting downgraded ... ?

I've attempted to follow up with the NPM team, I'll let you know if/when I have more information.

Awesome. It would be weird if the actual publisher affects this somehow, but you never know. Definitely would be useful to know whatever the root cause is found to be, though, because it's something else to keep in mind on going!

BTW, the behavior is the same with npm 6.1.0 as it was with npm 5.6.0.
So weird issue :/


Empty sharp image from Buffer

When trying to create a Sharp from empty raw an error is returned. Even if all variables are specified.
var image = Buffer.alloc(0)
// ...
    await sharp(image, {raw: {width: 0, height: 0, channels: 3}})
// Error: Expected width, height and channels for raw pixel input
// at Sharp._createInputDescriptor (...\node_modules\sharp\lib\input.js:57:15)

With size bigger than zero for each variable works fine

Hello, this is by design, you need to start with at least a 1x1 image. What's the use case where you might need a 0x0 image?

Sorry, I don't understand, please can you provide more details and perhaps a worked example of what you'd expect the rest of the sharp pipeline to look like?

My buffer contains an RGB image. Initially, the buffer size is 0 * 0 (* 3 channels) pixels. But after some period of time, it expands to a large X * Y value (* 3 channels) of pixels.
Of course, I now understand that the library is not intended for empty images, but I would like to see the possibility of creating empty images

Sorry, I'm still not sure I understand this scenario. What operations would you expect to work on a 0x0 image? What output formats support a 0x0 image? Are you aware of other image processing libraries that support 0x0 images?

Closing due to inactivity but please re-open with more details of the scenario(s) where support for 0x0 images would be useful.

@lovell I think there's probably a better way to approach this, but our use case would be for conditional compositing, to keep our code reusable. We have a shared function that processes a lot of images, but for a few we use composite  to add rounded edges.
I strongly suspect there's a better alternative for this than a 0x0 image? Any advice?


Perform End-to-End Testing of Anatomizer.py

After completing Issue #13 and Issue #15, we should perform an end-to-end install and run of inquisition w/ just anatomizer.py running.

On test Debian device:
root@nyc3inquisitiontesting01:~/Inquisition/install# /opt/inquisition/inquisition.py -c /opt/inquisition/conf/main.cfg -k
[INFO] configuration check is SUCCESSFUL, exiting...
root@nyc3inquisitiontesting01:~/Inquisition/install#
root@nyc3inquisitiontesting01:~/Inquisition/install#
root@nyc3inquisitiontesting01:~/Inquisition/install# /opt/inquisition/inquisition.py -c /opt/inquisition/conf/main.cfg -t
root@nyc3inquisitiontesting01:~/Inquisition/install#

Only issue encountered was Issue #32 .

root@nyc3inquisitiontesting01:~/Inquisition/install# cat /var/log/inquisition/app.log
2017-05-03 23:42:25,412 [ INFO ] [ lib.anatomize.Anatomize ] starting Anatomize engine...
2017-05-03 23:42:25,418 [ INFO ] [ lib.anatomize.Anatomize ] all database connections established [ SUCCESSFULLY ]
2017-05-03 23:42:25,421 [ INFO ] [ lib.anatomize.Anatomize ] configuration check is SUCCESSFUL, exiting...
2017-05-03 23:42:29,633 [ INFO ] [ lib.anatomize.Anatomize ] starting Anatomize engine...
2017-05-03 23:42:29,637 [ INFO ] [ lib.anatomize.Anatomize ] all database connections established [ SUCCESSFULLY ]
2017-05-03 23:42:29,638 [ INFO ] [ lib.anatomize.Anatomize ] all templates loaded and parsers started [ SUCCESSFULLY ]
root@nyc3inquisitiontesting01:~/Inquisition/install#

root@nyc3inquisitiontesting01:~/Inquisition# redis-cli
<IP_ADDRESS>:6379> keys *
1) "log_id"
<IP_ADDRESS>:6379> quit
root@nyc3inquisitiontesting01:~/Inquisition#

CentOS7 looks good too:
[root@tor1inquisitiontesting02 install]# python3.6 /opt/inquisition/inquisition.py -c /opt/inquisition/conf/main.cfg -k
[INFO] configuration check is SUCCESSFUL, exiting...
[root@tor1inquisitiontesting02 install]#
[root@tor1inquisitiontesting02 install]#
[root@tor1inquisitiontesting02 install]#
[root@tor1inquisitiontesting02 install]#
[root@tor1inquisitiontesting02 install]# python3.6 /opt/inquisition/inquisition.py -c /opt/inquisition/conf/main.cfg -t
[root@tor1inquisitiontesting02 install]# cat /var/log/inquisition/app.log
2017-05-04 00:05:25,712 [ INFO ] [ lib.anatomize.Anatomize ] starting Anatomize engine...
2017-05-04 00:05:25,719 [ INFO ] [ lib.anatomize.Anatomize ] all database connections established [ SUCCESSFULLY ]
2017-05-04 00:05:25,722 [ INFO ] [ lib.anatomize.Anatomize ] configuration check is SUCCESSFUL, exiting...
2017-05-04 00:05:29,127 [ INFO ] [ lib.anatomize.Anatomize ] starting Anatomize engine...
2017-05-04 00:05:29,132 [ INFO ] [ lib.anatomize.Anatomize ] all database connections established [ SUCCESSFULLY ]
2017-05-04 00:05:29,134 [ INFO ] [ lib.anatomize.Anatomize ] all templates loaded and parsers started [ SUCCESSFULLY ]
[root@tor1inquisitiontesting02 install]#

Last one left is Ubuntu.

Ubuntu 16.04 is all set now as well, completing end-to-end testing.
root@fo1inquisitiontesting03:~/Inquisition/install# cat /var/log/inquisition/app.log
2017-05-04 00:32:24,038 [ INFO ] [ lib.anatomize.Anatomize ] starting Anatomize engine...
2017-05-04 00:32:24,063 [ CRITICAL ] [ lib.anatomize.Anatomize ] could not create database connection :: [ (1045, "Access denied for user 'inquisition'@'localhost' (using password: NO)") ]
2017-05-04 00:45:02,348 [ INFO ] [ lib.anatomize.Anatomize ] starting Anatomize engine...
2017-05-04 00:45:02,360 [ INFO ] [ lib.anatomize.Anatomize ] all database connections established [ SUCCESSFULLY ]
2017-05-04 00:45:02,366 [ INFO ] [ lib.anatomize.Anatomize ] configuration check is SUCCESSFUL, exiting...
2017-05-04 00:51:49,165 [ INFO ] [ lib.anatomize.Anatomize ] starting Anatomize engine...
2017-05-04 00:51:49,177 [ INFO ] [ lib.anatomize.Anatomize ] all database connections established [ SUCCESSFULLY ]
2017-05-04 00:51:49,182 [ INFO ] [ lib.anatomize.Anatomize ] all templates loaded and parsers started [ SUCCESSFULLY ]
root@fo1inquisitiontesting03:~/Inquisition/install#

The db error see in the logs are due to Issue #33.


Update the website

I've noticed an error in the documentation at the website. I spent over 8 hours pinning this down so it would be a shame if others ends up doing it as well.
On the page for the WebP-plugin it says you need msvcr110.dll from the Visual C++ Redistributable Package with a link to the VS2012 redist package. But in 1d92a36cecacae8e694ec0376154d6542f0bebc3 libwebp was updated to a newer version that requires msvcr120.dll from the VS2013 redist package instead  The new required package is available from https://www.microsoft.com/en-us/download/details.aspx?id=40784 and it would be great if the website was updated with this.

Sorry about that. I documented it on the Nuget package page but forgot to update the docs page. The docs are actually open source, stored in the gh_pages branch so if you are feeling adventurous they are there to update.

Sorry I missed the gh-pages branch, never thought you were using that since the pages are so customized. I've created a pull request #356 that clarifies the situation a bit more even for users of older versions.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1963

Questions ?
Please refer to the Backport tool documentation


Inserting a new record with related objects in one request

Hello!!
I was trying to insert a new object related with another one already created, but I only know the External ID for the related one, is there any way I could call insert without making two calls? (Asking for ID for the related object and then inserting the new object).
I have found this comment (But it is using upsert): https://github.com/jsforce/jsforce/issues/673#issuecomment-373824396
Thank you!! :)

Insert/update/upsert should all work the same. This is a Salesforce feature, not a JSForce feature - so you can refer to the SFDC docs for examples.
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_upsert.htm
In addition, if for some reason you can't get the insert working, you should be able to specify an "upsert" and use "Id" of the record as the upsert id (External id) so that it will insert records every time.

Hi @paustint! Thank you for your reply. I found that article, but the ID I am trying to use is for the related object.
I have tried something like this, but I am getting a JSON_PARSER_ERROR: Cannot deserialize instance of <unknown> from FIELD_NAME value type or request may be missing a required field
conn.sobject('leads__c').create({
    "Name":"John",
    "source__c":"test",
    "campaign__r":{
        "type":"campaign__c",
        "reference__c":"campn-summer-20-details"
    }
})

I just tried this on the JSforce console and it worked without problems.
conn.sobject('Contact').create({
    "FirstName":"John",
    "LastName":"Smith",
    "Account":{
        "My_Ext_Id__c":"test-123"
    }
})

Hello @paustint! Thank you again for your answer. :)
I have tried again and does not work, maybe it is only compatible with native Salesforce objects?
Request 1:
conn.sobject('Request__c').create({
    "Development__c":{
        "External_Property_ID__c":"TAAD44"
    },
    "User__c":"0030X00002g2LCAQA2"
})

I get: JSON_PARSER_ERROR: Cannot deserialize instance of reference from START_OBJECT value { or request may be missing a required field at [line:1, column:2].
Request 2:
conn.sobject('Request__c').create({
    "Development__c":"a0O0X00000YKSxPUAX",
    "User__c":"0030X00002g2LCAQA2"
})

Request works: { id: 'a0Q0X00000HLTgfUAH', success: true, errors: [] }
The field External_Property_ID__c is marked as an External ID for my Development__c object:

Thank you!

Okay... I found it, I was using the field (Development__c) instead of the relationship (Development_r), now it works as expected.
Many thanks @paustint =)


Support of other architectures (!= x86_64)

Right now, we have focused on x86_64 architecture and we're usually presetting this option with randconfig
In fact there is an option called --seed that allows one to set specific pre-set options' values.
On large scale experiments, we're doing something like this:
python3 kernel_generator.py --dev 200 --linux_version 5.8 --local --seed x86_64.config
see https://github.com/TuxML/tuxml/blob/master/compilation/compiler.py#L213
https://github.com/TuxML/tuxml/blob/master/compilation/x64.config
https://github.com/TuxML/tuxml/blob/master/compilation/settings.py#L15
(for tiny/randconfig)
what's a bit intuitive is that by default there is https://github.com/TuxML/tuxml/blob/master/compilation/tuxml.config that is systematically used (default seed). It was partlly used for 4.13.3 and 4.15 for preventing some bugs. It's a legacy we should remove.
We need to:

[x] change the tuxml.config as the default seed
[x] I dislike the "seed" terminology, one needs another term like "preset"
[x] experiment different architectures (thus preset) such as arm. However it would certainly require cross-compilation support and so new Docker images (eg https://github.com/kernelci/kernelci-core/blob/main/jenkins/dockerfiles/gcc-8_arm/Dockerfile). I suggest to try experimenting with x86_32 (which is another closed architecture) and then others like arm

requires some experiments, but arch support is basically here now.


TypeError, undefined is not iterable

Hey
For some reason this code went wrong:
 const searchres = await YouTube.getVideo(args[0]);
            const Title = searchres.title;
            console.log(Title)

And I got this error:

So what is the problem? :D

odd, may I see your args[0]?

Yeah, it's something like this:
js const args = message.content.slice(Config.prefix.length).trim().split(/ +/);

I mean, what was your args[0]? is it a valid youtube video link?

aah, yeah it's youtube link.

can you please share that link.

aah damn, it was age restricted video :D I didn't noticed that, because with search function it works :D

ok

I've fixed this error on the latest version


Compatibility with Gurobi as alternative to CPLEX

Hi @mskilab,
I've been pretty excited to get this tool in place for some while. After some issues with trying to get ahold of IBM to register for an academic license, I went with Gurobi as suggested. The process was fairly simple with a little adjustment to some misdirected dynamic library paths to get JaBbA to load the Gurobi library properly.
However, after a few test runs, I've narrowed in on some roadblocks in completing the run with Gurobi.
It seems the error stems from expectations of using CPLEX at a few key points.
Below is a snippet of the error, I attached the log file with the complete output for reference:
JaBbA 2023-02-03 16:45:57: Number of gaps with nonzero width: 17908
JaBbA 2023-02-03 16:45:57: Number of segments before gap filtering: 25766
JaBbA 2023-02-03 16:45:58: 11200 segments produced after gap filtering
JaBbA 2023-02-03 16:45:58: creating karyograph
JaBbA 2023-02-03 16:46:27: loaded hets
JaBbA 2023-02-03 16:47:11: Definining coverage good quality nodes as >=50% bases covered by non-NA and non-Inf values in +/-100KB region
JaBbA 2023-02-03 16:47:11: Hard setting 0 Mb of the genome to NA that didn't pass our quality threshold
JaBbA 2023-02-03 16:47:11: Using loess to fit mean to variance relationship in segments with greater than 1 bins
JaBbA 2023-02-03 16:47:12: Using Sequenza to estimate purity ploidy
JaBbA 2023-02-03 16:47:17: Starting BAF model fit
JaBbA 2023-02-03 17:04:50: Built gGraph with 22712 nodes, 16136 edges, purity 0.97, and ploidy 4.4
JaBbA 2023-02-03 17:05:18: Brand new function for reciprocal junctions calling.
.
JaBbA 2023-02-03 17:05:18: Excluding 0 aberrant junctions whose both breakpoints are in NA coverage regions
JaBbA 2023-02-03 17:05:18: Cancel nudge for 4 aberrant junctions where one of the 2 breakpoint is in NA coverage regions
JaBbA 2023-02-03 17:05:18: In sum, we are forcing 0 junctions, excluding 0 junctions, and nudging 5 junctions
JaBbA 2023-02-03 17:05:18: number of specified max.threads: 12
JaBbA 2023-02-03 17:05:18: number of specified max.threads after processing: 12
sh: /Applications/CPLEX_Studio_Community2211//cplex/bin/arm64_osx/cplex: Bad CPU type in executable
Error in if (vnums[1] <= 12 && vnums[2] <= 6) { :
  missing value where TRUE/FALSE needed
Calls: suppressPackageStartupMessages ... JaBbA -> jabba_stub -> ramip_stub -> .cplex_customparams
In addition: There were 24 warnings (use warnings() to see them)
Execution halted

As you can see, JaBbA makes a call/reference to my installation of CPLEX despite my selection of using Gurobi. Looking into this a bit deeper, I can see it's related to the function .cplex_customparams(). Within in this function, there is a parameter --customparams which evokes the following conditional:
    if (customparams)
    {
        if (verbose) jmessage("number of specified max.threads: ", max.threads)
        MAX.THREADS = Sys.getenv("LSB_DJOB_NUMPROC")
        if (nchar(MAX.THREADS) == 0)
            MAX.THREADS = Inf
        else
            MAX.THREADS = as.numeric(MAX.THREADS)
        max.threads = min(max.threads, MAX.THREADS)
        if (is.infinite(max.threads))
            max.threads = 0
        if (verbose) jmessage("number of specified max.threads after processing: ", max.threads)

        param.file = paste(out.file, '.prm', sep = '')
        .cplex_customparams(param.file, max.threads, treememlim = mem * 1024,
                            workingmemlim = floor((mem * 0.6) * 1024))
        if (verbose) {
            jmessage("param.file contents: ")
            system2('cat', normalizePath(param.file))
        }

        Sys.setenv(ILOG_CPLEX_PARAMETER_FILE = normalizePath(param.file))
        if (verbose)
        {
            jmessage('Creating ILOG CPLEX PARAMETER FILE in ', Sys.getenv('ILOG_CPLEX_PARAMETER_FILE'))
        }
    }

Now, there is no issue with that conditional. The problem is this parameter customparams is always set to TRUE when propagated from the parent function ramip_stub() at lines 1261-1288:
ramip_stub(kag.file,
                   jabba.raw.rds.file,
                   mc.cores = mc.cores,
                   max.threads = max.threads,
                   mem = max.mem,
                   tilim = tilim,
                   edge.nudge = edgenudge,
                   use.gurobi = use.gurobi,
                   ab.force = ab.force,
                   ab.exclude = ab.exclude, ## we now exclude things during karyograph_stub
                   ## ab.exclude = integer(0),
                   init = init,
                   verbose = verbose,
                   purity.min = purity,
                   mipstart = mipstart,
                   epgap = epgap,
                   purity.max = purity,
                   ploidy.min = ploidy,
                   ploidy.max = ploidy,
                   slack.prior = 1/slack.penalty,
                   loose.penalty.mode = loose.penalty.mode,
                   dyn.tuning = dyn.tuning,
                   lp = lp,
                   ism = ism,
                   tfield = tfield,
                   fix.thres = fix.thres,
                   min.bins = min.bins,
                   customparams = T)

I think this could be easily adjusted given that it seems the function of the customparams parameter is directly related to CPLEX users. Therefore, you could perhaps set customparams = !use.gurobi.
Also, maybe it is feasible to create an alternative process for similar resource settings with Gurobi.
Let me know if I can provide more info to help troubleshoot. I may cut a branch and test this in the meantime.
Best,
Patrick
jabba.log

Hi again!
It looks like you're right - if you haven't tried this modification already, could you please try reinstalling from the following branch to see if it fixes the issue? https://github.com/mskilab/JaBbA/tree/zc_dev
There are some other minor bug fixes in this branch but hopefully they won't affect your analysis. Please let me know how it goes!

Hello Zi-Ning,
After pulling the updated dev branch, I can confirm JaBbA executed without an issue.
Based on the log, the Gurobi Optimizer was invoked correctly.
.....
Starting optimization with gurobi!
Gurobi Optimizer version 10.0.0 build v10.0.0rc2 (mac64[x86])

CPU model: Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
Thread count: 4 physical cores, 8 logical processors, using up to 8 threads

I will notify you if I have any further issues but otherwise this issue has been resolved.
Thanks again,
Patrick


Allow geekdocSearchShowParent

Titles in search results have not context. For example, if I have multiple "Getting Started" pages, all the results are going to be the same. This PR is to be able to give more context to search results:
If you activate this behaviour in your config file:
# config.yml
...
params:
  ...
  geekdocSearch: true
  geekdocSearchShowParent: true

Then, first parent is shown as prefix in search results:

geekdocSearchShowParent: false (default and current approach):

geekdocSearchShowParent: true:

Fixed


Trade aggregation: add offset parameter

Currently, trade aggregation buckets are aligned with epoch. This presents a challenge with aligning daily and weekly aggregations to a specific timezone.

+1

Implemented in #697

Implemented in #697


delete section does not always remove the desired section

I hit the "x" next to "L124 - 5mm plate - 100ST" and it deleted the sample above it ("L124 -3mm plate").  This has happened multiple times.  An undo button could be helpful for these types of bugs/mistakes because it's really painful to redo stuff that was correct and accidentally deleted.

It looks like unless you are trying to delete the topmost selection, it deletes the section above the one you are trying to remove.  n-1 problem?


Atone Form: Missing requested time out message when can not connect to server

Summary (Required)
Missing requested time out message when can not connect to server
Description (Required)

Perform a transaction with internet connection weak or low respond from server
Wait for a long time

Actual result: Missing requested time out message when can not connect to server
Acceptance Criteria (Optional)
Requested time out message must be displayed when can not connect to server (Maximum should be 60s)

@at-aoiyamamura
Waiting for client's check

Cái này Hoài đã fix, a Kiên đã check Ok rồi. Giờ chờ client check OK sẽ close.

@at-aoiyamamura

@at-duyentran @at-thinhung @at-hanhpham
We do not have any feedback from client about this issue.
iOS side already resolved, so I will close this issue. Sorry for late.


Create PerfectNumber.cpp

Description
Added code for the perfect numbers less than n.
Fixes #53
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation Update

@codermind-divya Please first ask for assignment to this issue in preferred language.

Sorry! I am new to open-source.
Can I work on this issue in c++.

@codermind-divya Please first ask for assignment to this issue in preferred language.
Sorry! I am new to open-source!
Can I work on this issue in C++?

@codermind-divya Sure, just put a comment in the issue for assignment😄


Define optional arguments for Patch.fromBlobs()

According to the libgit2 documentation (https://libgit2.org/libgit2/#HEAD/group/patch/git_patch_from_blobs) all arguments are allowed to be NULL.

Would you kindly add a test case for calling NodeGit.Patch.fromBlobs with all optionals null?

Sure. Don't really know what the expected behavior is but seems to generate an "empty" patch object with size 0.


testifylint: enable require-error

Which problem is this PR solving?

Apply require-error rule of testifylint

Description of the changes

use require instead of assert on errors testing

How was this change tested?

CI

Checklist

[x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[x] I have signed all commits
[ ] I have added unit tests for the new functionality
[ ] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: yarn lint and yarn test

this one is impossible to review manually, can you describe how the PR was made? Are there any manual changes, or is everything just s/assert/require/?


No suggestions in menu

It does check misspelled word however it's not showing those words in context menu. See -

@wearhere Can you look into it?

@wearhere ping 🎅 .

There is some additional setup needed for that. Did you see https://github.com/mixmaxhq/electron-spell-check-provider#but-how-do-i-show-spelling-suggestions-in-the-context-menu ?


images.dwell.com

This URL is necessary for images to load on Dwell.com

@steakscience can you provide me with more info? Which blocklists are you using? And where it's blocked

It is from Steven Black / Pi Hole default blocklist

Thanks for the info @steakscience . I have opened an issue in StevenBlack. Let's wait for his feedback


Restricted rounds?

Hi:) first of all, Thank you for the nice work!
Reviewing the code, I found a curious point which is not explained in the paper.
in coco.py, it looks like round is restricted to five, but coco has 17 keypoints(rounds).
is there any reason using 5 rounds, not full rounds?
 for idx in range(5):
      if idx >= len(kpt_des): break
      if self.conv_format == 'keypoint':
          q1 = "Where is the {} of this person in this image? Please provide its coordinates.".format(kpt_name[idx])

If there is anything that i misunderstood, please tell me! thanks😄

I think, it results from VRAM issue. 5 keypoints' description is the maximum length of prompt in RTX 3090(24GB). because, if setting the description to much longer than COCO, the training script outputs "cuda-out-of-memory error".


build(connector-besu): fix CVE-2022-21190 CVE-2023-36665 CVE-2022-2421

Commit to be reviewed

build(connector-besu): fix CVE-2022-21190 CVE-2023-36665 CVE-2022-2421
Primary Changes
----------------
1. Updated the version of the base image that is used in the Dockerfile
2. Updated the Dockerfile to use the yarn version 3
3. Updated the README to the new command to run the container

Fixes #2745
Pull Request Requirements

[x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

Hello @jagpreetsinghsasan already fixed it, thank you

LGTM

@petermetz  No worries, Already updated it and re requested for review. Thank you

@jagpreetsinghsasan Were your change requests addressed to your satisfaction?

@jagpreetsinghsasan Were your change requests addressed to your satisfaction?

Yes @petermetz , I have resolved those review comments. Its good to merge

@jagpreetsinghsasan Were your change requests addressed to your satisfaction?

Yes @petermetz , I have resolved those review comments. Its good to merge

@jagpreetsinghsasan Got it, thank you for confirming! I'll dismiss the review then.


How did you use this library.

Hello.
I´d like to know how did you use this library.
I am studying a way to generate a B2MML from Business Process Model.
Thanks in advanced!

I created this library primarily to allow b2mml payloads to be serialized to/from XML, You can, however, use add a reference to the library and use it to build a model programmatically.

Hi
Do you know some BPMS that is possible to connect this library to create a XML based a process model. I know the Enterprise Architect as BPMS, but the database is based in MS-Access.

Unfortunately this library is simply an implementation of the B2MML domain model; it doesn't contain any code.  The primary use cases would be usage as the target or source of a deserialization or serialization, respectively.
More specifically, if assuming you have an XML file containing B2MML, you'd use an XML library to deserialize your XML to an object of a type contained within this library before working with it programmatically.  This allows you to avoid manually parsing the file or deserializing to a generic XML document and traversing the nodes.


[5.1] Add PHP 8.4 to CI

Part of issue #123

add PHP 8.4 to CI
chore: run cs-fixer regardless of PHP version (forcing it to run on PHP 8.4 in CI - it passes)
explicitly mark nullable parameters like ?callback ?string. This was supported since PHP 7.1, so that is very convenient because the 5.1.x release series still supports all the way back to PHP 7.1

@cedric-anne IMO this will support PHP 8.4 for the 5.1.x series. Please review and comment.
Then I can check these things in master (which might already be OK), and try similar in other sabre-io repos.


FF4j disableGroup method enables instead of disable

See: getFeatureStore().enableGroup(groupName) in the following method. Issue in ff4j-core-1.3.1
/**
* Disable group.
*
* @param groupName
*            target groupeName
* @return current instance
*/
public FF4j disableGroup(String groupName) {
getFeatureStore().enableGroup(groupName);
getEventPublisher().publish(groupName, EventType.DISABLE_GROUP);
return this;
}

Thank you for the notice. It's now fixed, I will release soon !


API token

where do i get an API token, i dont have one nad can't seem to find how to get one for modlunky, it won't allow me to use mod codes without one

It's on your settings page of spelunky.fyi (https://spelunky.fyi/accounts/settings/) There's a link in modlunky that takes you to that page.


Feat/check contract with contract ID

Description
Right now, checking a contract foo.clar that contract-call?'s into contract bar.clar will fail because the underlying clarity-cli binary does not use foo.car's fully-qualified contract identifier when analyzing it.  The work-around today is to require all contract-call?'s to use the fully-qualified contract identifiers, which is somewhat painful for developers.
This PR updates the Clarity provider interface to take an optional contractId?: string argument to checkContract().  With proper support from clarity-cli (added in this PR here: https://github.com/blockstack/stacks-blockchain/pull/2486), this will enable checkContract() to succeed on contracts that invoke other contracts through contract-call? via the short-hand notation that elides the address component of the contract identifier.
Additional context here: https://github.com/blockstack/stacks-blockchain/issues/2478.
NOTE: This PR is blocked on https://github.com/blockstack/stacks-blockchain/pull/2486, and by extension, blocked on a new release of clarity-native-bin that includes it.
Type of Change

[ ] New feature
[X] Bug fix
[ ] API reference/documentation update
[ ] Other

Does this introduce a breaking change?
No -- the PR should be backwards-compatible, provided it uses a compatible clarity-native-bin.
Are documentation updates required?
Nope -- the new argument is optional, and the Client object automatically passes the contract ID for the contract under consideration to the underlying provider's checkContract().
Testing information
I have so far manually verified that this PR fixes the aforementioned bug in the Stacks blockchain repo.  However, I don't see any existing test coverage for checkContract in the clarity package.  Please advise on how to proceed.
Checklist

[X] Code is commented where needed
[ ] Unit test coverage for new or modified code paths
[X] npm run test passes
[X] Changelog is updated
[X] @lgalabru @zone117x

@lgalabru to help with a review

@jcnelson could you please resolve the conflicts and merge this PR?

@jcnelson pinging you again to get this PR over the finish line soon :)


Fixed NameError: name 'json' is not defined

@denisneuf
Hi again!
merge pls and release =)

@drewxa thank you bro, done


Remove the Trezor button

It is pretty clear we won't have Trezor anytime soon and definitely not before launch. That button should be removed then. Otherwise we are just fake news :-) and will confuse a lot of users as they try to connect a Trezor and nothing happens.

Fixed.

Fixed.


doc(decision): document use of "story" issues

What this PR changes/adds
Adds a decision-record about the use of "story" issues, a.k.a. umbrella issues.
Why it does that
A decision was made to use task lists in issues, which greatly improves the structure of work, keeps PRs clean and succinct and makes code reviews easier and more easily digestible.
Further notes
n/a
Linked Issue(s)
n/a
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[x] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[ ] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #883 (07872fc) into main (3428dbf) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 07872fc differs from pull request most recent head d86d429. Consider uploading reports for the commit d86d429 to get more accurate results

@@            Coverage Diff            @@
##               main     #883   +/-   ##
=========================================
  Coverage     60.07%   60.07%
+ Complexity     2263     2261    -2
=========================================
  Files           607      607
  Lines         13071    13071
  Branches        912      912
=========================================
  Hits           7853     7853
  Misses         4792     4792
  Partials        426      426

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 3428dbf...d86d429. Read the comment docs.

@MoritzKeppler is this OK for you?

@paullatzelsperger Should those story issues be maked with a dedicated label (for e.g. filtering) or is this too much and somehow implied?

@paullatzelsperger Should those story issues be maked with a dedicated label (for e.g. filtering) or is this too much and somehow implied? Just asking, I think this should not be part of a decision record, right?

+1 on having a "story" label for readability and filtering.

@paullatzelsperger Should those story issues be maked with a dedicated label (for e.g. filtering) or is this too much and somehow implied? Just asking, I think this should not be part of a decision record, right?

+1 on having a "story" label for readability and filtering. @juliapampus could you create one?

@paullatzelsperger Done

4 approves, I guess this one is ready to merge, right? @paullatzelsperger

4 approves, I guess this one is ready to merge, right? @paullatzelsperger

Damn sure is :)


[Macros] Narrow the carve-out for DebugDescription’s use of symbol linkage markers.

This change only allows symbol linkage markers in the peer expansion of _DebugDescriptionProperty.

@swift-ci please smoke test


add more verbose documentation

changes:

add documentation
fix bug with partisipationUrl
change procurementMethodType to landlease

Pull Request Test Coverage Report for Build 23

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.093%

Totals

Change from base Build 23:
0.0%

Covered Lines:
959

Relevant Lines:
1127

💛  - Coveralls

Pull Request Test Coverage Report for Build 23

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.093%

Totals

Change from base Build 23:
0.0%

Covered Lines:
959

Relevant Lines:
1127

💛  - Coveralls

Pull Request Test Coverage Report for Build 24

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.093%

Totals

Change from base Build 23:
0.0%

Covered Lines:
959

Relevant Lines:
1127

💛  - Coveralls


raft: fix typo in raftlog

fix typo in String() method of raftlog which will misorder
the "committed" and "unstable.offset" output.

LGTM. Thanks for fixing this!


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Major Changes

#822 b799677 Thanks @threepointone! - PartySocket v1
PartySocket's been pretty stable, so it's time to cut a v1. We have plans for future features, but it's pretty good right now, so let's ship it.

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


downgrade to v2.9

          downgrade to v2.9

Originally posted by @UndiedGamer in https://github.com/TheRealJoelmatic/RemoveAdblockThing/issues/270#issuecomment-1888643306
y dowgrade the version and obtain the same result.

Why you opened a new issue?

i didnt work bozo


MQTT event on detector not detecting face [FEAT]

Is your feature request related to a problem? Please describe.
Currently if Frigate detects a person Double Take with pass the image to the configured detector/s and if a face is identified it will return ever the person's name if known or unknown. In turn double take will display the image in its GUI and send an MQTT message with the details of what was detected. However, if the detector/s do not detect a face, nothing happens.
Describe the solution you'd like
Double take to send an MQTT message if no face is detected in an equivalent way as it does when an unknown person is detected.
Additional context
I have security automation setup in HA and node-red which is listening to the double take 'camera' topics, when a message is sent it among other things sends a TTS message to my speakers saying either 'Bob had been detected in the drive' or 'Unknown person had been detected in the drive'. Issue is there are occasions Frigate detects a person, my detectors (using both deepstack and compreface) do not identify a face resulting in no camera topic being sent. Resulting in no warning that someone is in my drive :)
Worth noting it's rare for both deepstack and comreface not picking up a face, but it's most common at night when the image is dark, the exact time I want my security automation to be working.
As a result of the missing warnings, I've needed to change my automation so its listening to the frigate topic, this however doesn't allow me to work out if I know the person or not.

I definitely want to prioritize this feature and will try to include it in the next release. I also wanted to include the image on the UI as well.
If no matches or unknowns are found, I was going to take the image from the mid point of the event. Meaning if there are 10 images analyzed and no results are found, then the 5th image would be the one saved to the UI. I'll probably just use the label that Frigate gives, so then it can expand for other labels as well in the future.
Do you think it should go to a new MQTT topic? Or to the existing camera one? Or maybe a both?

For my use case having the message go to the existing camera topic would be ideal, I already have automation listening to each of the camera topics.

maybe consider to send also "misses" if the bounding-box was smaller than configured.
sometims still a match... but marked red because of the box-sizes.
good to get that information over mqtt as well -> https://github.com/jakowenko/double-take/issues/139

@jakowenko have you made any progress towards this? I'd love this feature as I'm trying to use double-take to reduce my alerts to only indicate unknown people, if a face isn't detected as it currently stands there's no alert from double-take so this would go unnoticed.

Sorry for going MIA. Going to start working on this feature this week.

Appreciate your very busy but wondering if you have had any more movement with this one?

Sorry for bringing this one back, I know I requested it sometime ago. Just wondering if there has been any progress.


About the training data.

Thanks for your great work!
I am curious about the Human Attribute Pre-training stage, if you pre-trained the model with the full-body image in SHHQ or just use the cropped upper-body image (e.g. the showed tiktok video results)?

I have the same question.

Hi @Fanghaipeng @linziqu , sorry for the late responses due to my current limited bandwidth. We just use the original images in the pretraining data, but we include data augmentation in the dataloader with image cropping. So it may result in some half-body images (but not only upper-body images)


Manage service learning faculty

I created a page for faculty instructors to view, search previous courses tutored. Created a dictionary in the backend with instructors as keys and previous classes taught as values. Passed my dictionary to a data table. position the search box of the data table with CSS styling. link the instructors to the course management page.
Link to the Manage Service learning page: /manageservicelearning

Test
Navigate through the page click on the instructors and check the next page
search classes and instructors in the search box
check the database to see if all instructors are in the table

These changes have still not been made. Also, there are conflicts to resolve with development


Discussion: Scaling Agile

What we're after:

Our community has expressed interest in this, particularly expression curiosity about agencies using SAFe. Partner may have mentioned SAFe, may have needs to scale agile
Exposure for guild
Could give us content, something to memorialize (not seeing much recently, older cloud.gov, maybe FEC)
We want to steer away from discussing specifically SAFe, rather agility at scale

Some smaller chunks we could look at:

Agile program management
Multiple vendors, multiple teams (what are the good things that seem to work, SAFe, LeSS, DAD)
Step 0 in scaling
-- Learning how to avoid it
-- Steve Denning (Andrew to follow up)
DA Decision framework

Possible formats:

Training
Coaching
Unconference / open space : virtually
Failures – when does agile at scale go bad?

Possible people who can represent:

Bret, Alan A., Cata, Hopson indicated interest
Prisby or someone else from Login.gov
Porta's experience with scaled projects

People we can speak to about ideas:

Uchenna (Porta to check)

Maybe/later:

Federalist (Eddie)

Notes/other considerations

Marketing
yeah that SAFe one i think would make a good “marquee” agile guild event
Good to have other members contribute
Solicit questions beforehand
Memorialize somehow

More context here:
https://docs.google.com/document/d/11w5VA-PY-KuBx7sLBJyjDdAnuTQPGR9otx9eRjTyYtQ/edit#heading=h.wpfgksukm3w4

Notes from 8/24 guild meeting.

Want to steer away from discussing specifically SAFe, rather agility at scale

But even agility at scale is too large a topic so let's look at some smaller chunks:

Agile program management
Multiple vendors, multiple teams. (what are the good things that seem to work
SAFe, LeSS, DAD)
Step 0 in scaling
-- learning how to avoid it
-- Steve Denning
DA Decision framework

2 formats for this kind of thing (long term)
-- training format
-- coaching format
-- unconference / open space : virtually

But how do you market something like ^^?  That's the event the guild would target to have.

Failures
-- When does agile at scale go bad

How much useful experience does the guild have to put on something like this?
-- Uchena Moka

From our leads sync – Porta to follow up with Uchenna on possible folks she may know who can speak to this, and I'll look up the Steve Denning angle.

@porta-antiporta FYI, I cleaned up the issue as discussed.

Closing as stale, on the assumption that the need will resurface if it still exists.


Handle API failures when not connected to the internet

Should probably throw an exception when no internet is available or the API cannot be reached. If the call below fails there is not catch to handle it: https://github.com/speckleworks/SpeckleCore/blob/a8c054ab499578bd3f014a5298c5e99db460f382/SpeckleCore/SpeckleApiClientApiCalls.cs#L337

I would see the easiest way to fix this via an InternetAccess flag which can be checked in the PrepareRequest and execeptions thrown. https://github.com/speckleworks/SpeckleCore/blob/master/SpeckleCore/SpeckleApiClientHead.cs#L58
I'm hesitant to change the autogenerated code, as it will make subsequent future generations more painful. But if nswag can be coerced into adding that catch, i'm fine :)


 Sometime I click m1+m2 it perform the 5 hit attack, but other time it perform 3 hit attack with a broken animation. I did edit the character scale, but even with the normal scale with both gender, the animation is still broken.

Modlist version
1.07

what twohanded skill level and what twohanded perks please?

fixed for next update


Restrict the writeLogsPolicy

Split permissions related to 'Bucket Operations' and 'Object Operations'
Specify the Bucket in Resource.
Remove the wildcard from the Action.

@h1f1x Could you please verify those changes and if so, merge it? The reason is to make it compliance with cfn-nag.
@teo-scout24 If you have any other objection, please let us know.

I don't have any objection...


Add support for iCloud Sandbox testers

🔑
Fixes https://github.com/fastlane/fastlane/issues/2043
This adds support for creating and listing iCloud Sandbox users, which are useful for testing In-App Purchase or Apple Pay (see creating user accounts for more info).

This is great, thanks for your contribution @jflinter, this will be in the next release

My pleasure, thanks for the quick review @KrauseFx !


React 0.14 release

Wait for quick release. Current version with React 0.13 produce a lot of warnings because of cloneWithProps and context.
@kenwheeler

On it. Refactoring a ton of my repos for 0.14 over the next few days.

Just cut 1.0.0, enjoy

Great work. Thanks for quick fix.


Support Ollama custom models

Details
It would be great if we could use the Ollama models in the typescript version similar to how we can in the python library

Checklist

[X] Create packages/core/src/llm/OllamaModel.ts ✓ https://github.com/run-llama/LlamaIndexTS/commit/fd07772e21e2996f143bd82966b4930e9cad37ae
[X] Check packages/core/src/llm/OllamaModel.ts ✗
[X] Modify packages/core/src/llm/OllamaModel.ts ✓ https://github.com/run-llama/LlamaIndexTS/commit/91705359b70bb79c186c7d9d56fb38bdad31d47e
[X] Check packages/core/src/llm/OllamaModel.ts ✗
[X] Check packages/core/src/llm/OllamaModel.ts ✗
[X] Modify packages/core/src/llm/LLM.ts ✓ https://github.com/run-llama/LlamaIndexTS/commit/cfe834fbf4557b5d3e95e9a2a0b5ef9b01397536
[X] Check packages/core/src/llm/LLM.ts ✗
[X] Modify package.json ✓ https://github.com/run-llama/LlamaIndexTS/commit/4c3d15388b6fbc27f719f4f7f76125b73665bed9
[X] Check package.json ✗
[X] Modify package.json ✓ https://github.com/run-llama/LlamaIndexTS/commit/ac648b13be8c63326dab5b744cb0724b825d664c
[X] Check package.json ✗
[X] Check package.json ✗
[X] Check packages/core/src/llm/LLM.ts ✗
[X] Create packages/core/src/llm/index.ts ✓ https://github.com/run-llama/LlamaIndexTS/commit/500cda8d7f32f0529969deabe1cc5251656382f9
[X] Check packages/core/src/llm/index.ts ✗

Closing due to inactivity
Feel free to open again if necessary
As well we can revisit it later


chore: backports for leanprover/lean4#4814 (part 20)

see https://github.com/leanprover-community/mathlib4/pull/15245

bors merge