how to use Snoop to perform automation tests with WPF UI

Hello guys!
I am really sorry for introducing an issue for asking this kind of information.
I read a post on Stackoverflow where one of the members had successfully used Snoop to perform "unit automated tests" with his UI.
The post did not give any details on how to do so, so I thought it would be a good place to start asking you guys for some blueprints in this direction.
Would it be possible to obtain a sample code showing how to instantiate a test with Snoop and controlling the interface? It could be any interface, as long as we can see how to code a click and how to inspect an answer coming from a processing that has been triggered by a button-click, it would be great.
Thank you all and sorry again for this post that is clearly not an issue, although I would really appreciate an answer.
Have a nice day!

I never tried to do something like that with snoop and don't think it's capable of doing that.
Could you add a link to the stackoverflow question?


Investment table is broken on Beta

Caused by the following failing gqueries.

Closed with https://github.com/quintel/etmodel/pull/2234.


Changes headers to sentence case

Summary of the changes / Why this is an improvement
Changes headers from title case to sentence case.
Checklist

[x] CLA is signed

@kevinkq travis tests are passing now on master, please rebase and let the tests run again. sorry for the inconvenience ;)


bump framework version

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6558188988


fix: copying a GameObject also copies ComponentBreakable (Issue #443)

I am looking to it, closing the engine with a copy of a breakable crash


make #derive before #attr when expand to avoid warning legacy_derive_helpers

when use cxx with derive macros with helper container attribute will meet the warning
https://github.com/rust-lang/rust/issues/79202
a minimal case:
#[cxx::bridge]
mod ffi {
    #[derive(Debug, Default, Deserialize)]
    #[serde(rename(deserialize = "de_name"))]
    struct Data {
        size: usize,
    }
}

Published in 1.0.71.


Fptest64

Fptest64 was branched off of fptest. It is identical except that it modifies the 64-bit floating point routines from Berkeley softfloat 2 to use pointers instead of values, allowing these to be compiled by cc65. All functions that previously took a float64 as an argument now take a *float64 as an argument. All functions that returned a struct (either a float64 or a commonNaNT) now accept an additional argument, dst, which is a pointer to memory for returning the value.
There's also one small change in roundAndPackFloat32 that fixes a problem I encountered in small test programs on the Commodore 64.
Note that this differs from the approach for returning commonNaNTs in the 32-bit floating point routines. Those return a pointer to static memory containing the commonNaNT, which means each invocation of the function clobbers the return value of the previous invocation. The approach used here trades inconvenience for safety by avoiding this clobbering.
Note also that, to reduce memory copying, some functions modify the pointed-to return memory during the function and will produce incorrect results if a memory location is used both as an input argument and a return location. To avoid problems, don't do this:
float64 a, b;
float64_add(&a, &a, &b);

Instead, do this:
float64 a, b, c;
float64_add(&c, &a, &b);
a = c;

The functions included here should work, though they require more testing. Fully integrating them into the compiler will require further work:

adding assembly language hooks to use the functions
handling 64-bit floating point values in the AST
adding generator code to use the functions in compiled programs
figuring out how to pass pointers instead of 8-byte values in generated code

For this last problem, I can think of 2 solutions:

Use a separate stack just to hold 8-byte values and pass pointers between functions
Update the calling convention to allow passing 8-byte values. This should be relatively easy with the cdecl calling convention, but with fastcall, we will probably have to add a new pseudo-register on the zero page, tentatively labeled sreg2, which would be 4 bytes in size.

I am not that familiar with the compiler, but I'll keep working on these problems for a future pull request.
-Jim

looks like some style issues need to be fixed :)

Yep, I found a dangling space in specialize.h. It's fixed now and all tests pass!

OK, so i looked a bit closer... Unfortunately i see one or two problems with this. I really appreciate the effort - however, i'd rather keep the unmodified code in my branch as long as the modifications are not exactly like we need them.

Changing the ABI for 64 bit floats to pass pointers to the 64bit values, instead of passing 64bit values (which implies adding support for this to the compiler first), sure looks like the obvious thing to do - however, there might be some subtle detail in how C is supposed to work that makes this a bad thing to do. I honestely can't tell, @acqn @oliverschmidt @spiro-trikaliotis @kugelfur et al please comment

: another thing to consider is, that at some point in the future, the float support should be extended so it can make use of  eg a library with 16bit floats. This would be a lot easier to handle, if floats and doubles share the same ABI (ie no passing of doubles via pointers), because then the existing 32bit float library code can be used for the doubles in that case.

besides the parameter passing, the 64bit functions must match the described API for 32bit functions exactly. ie your described behaviour for a = a X b is not acceptable, it must be possible to do this, the code generator will become a mess if it cant handle the two cases exactly alike.

Unfortunately this topic as well beyond my skill level. I won't be able to provide any helpful assessment :disappointed:

Hi Bob! I agree with everything you're saying and can see why you wouldn't want to accept the pull request in its current state. I'm happy to change the float64 functions to exactly match the float32 functions (i.e., making the a = a X b case work correctly). I think the trickier thing is the problem you brought up first -- for 64-bit floats to be used in functions, there needs to be a way to pass 8-byte values between functions. If the compiler secretly passes pointers instead of the full 8 bytes of the float64, a user could do something like this:
#include <stdio.h>

double modify_incoming(double x) { // here, a pointer to x is passed instead of a copy of x.
	x += 5.0;
	return x;
}

int main() {
	double x = 8.0;
	double y = modify_incoming(x);

	printf("%f, %f\n", x, y);
	// this should print "8.0, 13.0", but it will actually print "13.0, 13.0".

	return 0;
}

To solve this problem, we would either need to extend the calling convention of cc65 to allow passing 8-byte values as arguments and return values (see my previous post for ways to do that), or we would need to do the code generation such that, when doubles are passed, a temporary variable is put on the stack to use in place of the incoming argument.
For example, the user code above could generate code with the necessary stack-allocated temporary variables internally, like so:
#include <stdio.h>

void modify_incoming(double *dst, double *x) {
	double _temp = *x; // a temporary variable is inserted here to hold x's value.
	_temp += 5.0;
	*dst = _temp;
}

int main() {
	double y;
	double x = 8.0;
	modify_incoming(&y, &x); // this is changed to pass by pointer.

	printf("%f, %f\n", x, y);
	// this should print "8.0, 13.0", and now it actually will.

	return 0;
}

Overall, I think this would make code generation for 8-byte values complicated. I think updating the calling convention to allow for 8-byte argument passing would be the cleanest solution, but I don't think I can do that by myself. I'd be happy to help with that as much as I can, but that seems like a big increase in the scope of the project compared to implementing 32-bit floats. For now, I can get the float64 functions to work safely with the a = a X b case, and then the issue of fully implementing doubles in the compiler could be addressed later. What do you think?

For now, I can get the float64 functions to work safely with the a = a X b case, and then the issue of fully implementing doubles in the compiler could be addressed later. What do you think?

For the reasons already mentioned, i think it only makes sense without that magic converting to pointers (That will create more problems than it solves).


Keys presses twice on Windows

What crate(s) in this repo are involved in the problem?
tokio-console
What is the issue?
Whenever pressing a key in the tokio-console ui, it presses twice. Pressing j goes down two elements. Pressing space pauses then unpauses. Both keys press instantly. It doesn't matter when I release the key.
How can the bug be reproduced?
Run tokio-console on Windows 10 (or Windows 11, apparently) on Powershell or Git Bash. The bug happened on the Tabby terminal emulator and on the VSCode terminal emulator.
Logs, error output, etc
No response
Versions
console-subscriber v0.2.0
console-api v0.6.0
tokio-console 0.1.10
Possible solution
I remember seeing somewhere that Windows key events fire on both key pressed and key released, while Unix key events only fire on key pressed. It may be the other way around.
Additional context
No response
Would you like to work on fixing this bug?
maybe

Interesting, thanks for the report! I wonder if there's something we can enable in crossterm/ratatui to make its key event behavior on Windows consistent with other platforms?
If not, we could certainly implement some windows-specific logic to work around this in the console. But, it seems like there ought to be something in the terminal UI libraries for it...

I'm also having this issue.
Windows 11
New terminal app
nushell

For me, #515 fixes this problem.

Interesting, thanks for the report! I wonder if there's something we can enable in crossterm/ratatui to make its key event behavior on Windows consistent with other platforms?

Ratatui doesn't have anything that handles the actual key events, the code for this is all in Crossterm.
In Crossterm, there's an open issue to put the KeyPress events behind a feature flag, as it caught a number of people off guard (and makes upgrading apps from 0.26 to 0.27 kinda annoying). Until then it's pretty easy to check for event.kind == KeyEventKind::Press instead.


Update log4j

Looks good to me. However, the dev-mode lo4j2 configurations differ to the former ones w/ respect to max file size for roll-over. Was this change intentionally?

Hawkeye! No, this is a remnant from when I tested the roll-over stuff and got committed by mistake. Fixed. Thx!


A higher-level interface to model checkpointing

CheckpointReader and CheckpointWriter provide the building blocks for reading and writing model tensors to TensorFlow v2 checkpoint files, but to use them you have had to write model-specific code for extracting Tensors and their names, as well as placing parameters back into the model. This introduces a higher-level API that makes it easy to checkpoint and restore simpler models, and provides customization options for more complex models or for matching the naming schemes of external frameworks.
Writing a checkpoint becomes as easy as
extension LeNet: Checkpointable {}

let model = LeNet()

try model.writeCheckpoint(to: directory, name: "LeNet")

and reading
var newModel = LeNet()

try newModel.readCheckpoint(from: directory, name: "LeNet")

This is handled via the new Checkpointable protocol, which builds on KeyPathIterable. If you extend a model to be Checkpointable you will gain the writeCheckpoint(to:...) and readCheckpoint(from:...) methods for writing and reading checkpoints. By default, this will generate path names for each Tensor<Float> within your model using a naming scheme where each level in the model is named by its property name and separated by "/". For example: conv1/filter.
This can be overridden in a number of ways. The internal separator string can be changed by providing a different checkpointSeparator in the protocol conformance. Specific tensors within the model can be ignored for checkpointing by providing them in ignoredTensorPaths in the protocol conformance.
For the greatest flexibility, customized String -> String mapping between internal tensor path names and those in the on-disk checkpoint can be provided as a default for the model via tensorNameMap in the protocol conformance, or as a parameter when reading or writing a specific checkpoint. This allows for interoperability between a wide variety of frameworks and model naming conventions.
Documentation and tests have been provided for checkpointing overall, and this new functionality in particular. This is now ready for review.

I'm merging this in for now, to allow for the documentation to be accessible and to unblock work on improvements that depend on this.

I'm merging this in for now, to allow for the documentation to be accessible and to unblock work on improvements that depend on this.


[SPARK-45270][K8S][INFRA][DOCS] Upgrade Volcano to 1.8.0

What changes were proposed in this pull request?
This PR aims to upgrade Volcano to 1.8.0 in K8s integration test document and GitHub Action job.
Why are the changes needed?
To bring the latest feature and bug fixes in addition to the test coverage for Volcano scheduler 1.8.0.

https://github.com/volcano-sh/volcano/releases/tag/v1.8.0

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

Thank you, @HyukjinKwon !

K8s integration tests passed. Merged to master for Apache Spark 4.0.0.


Improve ownship detection for EFBs that care

Description
Foreflight was recently updated to improve ownship detection for users with ADS-B out equipped aircraft by comparing gps/baro information against the reported traffic, allowing it to determine the N-Number of the aircraft for track log recording and automatic draft logbook entries.  This update affected Stratux users with aircraft not equipped with ADS-B out, as Foreflight would report 'Ownship Not Detected' even if an ICAO address was set in Stratux configuration.  A recent update to Stratux fixed this issue, however, it negatively affected Stratux users with ADS-B equipped aircraft as it would require them to update the ICAO address in Stratux for proper N-Number detection, or be subjected to draft logbook entries reporting aircraft as 'Stratux'.  This update attempts to deliver the best of both worlds by setting the appropriate traffic type flag based on ICAO Mode-S code defined in Stratux.  A dummy or blank ICAO Mode-S will result in Foreflight's ownship detection logic being used.  A configured ICAO Mode-S setting will result in Stratux passing the ownship information and Foreflight consuming it as is.  Users of other EFB apps such as Aerovie, FlyQ, etc are not affected by this or previous change.
What Is Changing
Update Ownship target identity to report 0x00 which represents 'No Traffic Alert' and 'ADS-B with ICAO' only when a valid ICAO code is configured in Stratux Settings.  Otherwise, send 0x01 for 'No Traffic Alert' and 'ADS-B with Self-Assigned Code'.
Pre-Testing - Non-Assigned Code

Assign ICAO code of F00000 or 000000 in Mode S Code configuration input box
Open Foreflight EFB
Go to Devices -> Stratux
Verify Ownship detection reports 'Stratux' for Aircraft N-Number.

Pre-Testing - Assigned Code

Assign valid ICAO code in Stratux Mode S Code configuration input box
Open Foreflight EFB
Go to Devices -> Stratux
Verify Ownship detection reports 'Detected' and correct N-Number of ICAO entry

Post-Testing - Unassigned Code

Assign ICAO code of F00000 or 000000 in Mode S Code configuration input box
Open Foreflight EFB
Go to Devices -> Stratux
Verify Ownship detection reports 'Not Detected'

Post-Testing - Assigned Code

Assign valid ICAO code in Stratux Mode S Code configuration input box
Open Foreflight EFB
Go to Devices -> Stratux
Verify Ownship detection reports 'Detected' and correct N-Number of ICAO entry

Well-written PR, thanks for submitting.


filename does not contain clustername

it looks like the clustername is missing in the config filenames?
➜  talos talhelper genconfig
generated config for master1 in ./clusterconfig/-master1.yaml
generated config for master2 in ./clusterconfig/-master2.yaml
generated config for master3 in ./clusterconfig/-master3.yaml
generated config for worker1 in ./clusterconfig/-worker1.yaml
generated client config in ./clusterconfig/talosconfig
generated .gitignore file in ./clusterconfig/.gitignore
➜  talos cat talconfig.yaml
  clustername: mycluster
  talosVersion: v1.5.2
  endpoint: https://<IP_ADDRESS>:6443
  nodes:
    - hostname: master1
      ipAddress: <IP_ADDRESS>
      installDisk: /dev/sda
      controlPlane: true
    - hostname: master2
      ipAddress: <IP_ADDRESS>
      installDisk: /dev/sda
      controlPlane: true
    - hostname: master3
      ipAddress: <IP_ADDRESS>
      installDisk: /dev/sda
      controlPlane: true
    - hostname: worker1
      ipAddress: <IP_ADDRESS>
      installDisk: /dev/nvme1
      controlPlane: false
➜  talos  talhelper --version
talhelper version 1.12.0

Hello @runningman84. It's clusterName and not clustername :)

Also thanks for the issue because I just realized that the program should detect it and refuse to proceed. Looks like the library that unmarshal the yaml file doesn't work with wrong capital spelling. Will fix this soon.

Okay I have that from some docs…

Closing this, the new behavior should not allow a mistyped clusterName to continue. Thanks!

Okay I have found the source for the wrong config:
Workflow:
  Create talconfig.yaml file defining your nodes information like so:
  ----------------------------------------
  clustername: mycluster
  talosVersion: v1.0
  endpoint: https://<IP_ADDRESS>:6443
  nodes:
    - hostname: master1
      ipAddress: <IP_ADDRESS>
      installDisk: /dev/sdb
      controlPlane: true
    - hostname: worker1
      ipAddress: <IP_ADDRESS>
      installDisk: /dev/nvme1
      controlPlane: false
  ----------------------------------------

as you see the output of talhelper itself suggests a wrong config

Ah sorry about that, will be fixed in the next version. Thanks!


DateRangePicker. Unable to override Day Component

There is no ability to override Day Component in DateRangePicker via renderDay props
In source code seems like find the location of the problem
Default renderDay always override our passed prop renderDay
<Calendar
        {...other}
        date={date}
        onChange={onChange}
        renderDay={(day, _, DayProps) => (
          <DateRangeDay
            isPreviewing={false}
            isStartOfPreviewing={false}
            isEndOfPreviewing={false}
            isHighlighting={isWithinRange(utils, day, date)}
            isStartOfHighlighting={isStartOfRange(utils, day, date)}
            isEndOfHighlighting={isEndOfRange(utils, day, date)}
            {...DayProps}
          />
        )}
      />

Really. Thanks its a pitfall XD

Really. Thanks its a pitfall XD

Will be fixed in next release? :)

@dmtrKovalenko Is it enough to move {...other} to the end, or do you think that will cause other problems? I could whip up a PR for that otherwise.

We need to pass DateRangeProps. All of these isHighlighting props

Duplicate of #1856

@oliviertassinari why is this closed?


Download range doesn't work anymore

After 73169a7 the download_range function seems to be broken.

or have other people fix it

@billhanyu Why don't you fix it then?

Fix it then.

@billhanyu rude


Fix Windows CI caching and reenable Windows CI

If you could fix the caching for the Windows CI I would be eternally grateful. Otherwise I might have to disable since the network connection to the stackage infrastructure (casa.fpcomplete.com) has become very unreliable and stack builds fail all the time
Originally posted by @pepeiborra in https://github.com/haskell/ghcide/pull/794#discussion_r488124365

The last succesful build with windows was https://dev.azure.com/digitalasset/ghcide/_build/results?buildId=55020&view=results
There are failed ones after it with timeouts, so, to be sure, what do you mean with fix the caching for the windows CI? was it always missing?

Ok, let's take the first build of #808:

two linux jobs (84 and bench) throwed a build time out (reported as canceled)
and windows one throwed a time out downloading packages from stack

HttpExceptionRequest Request {
  host                 = "casa.fpcomplete.com"
  port                 = 443
  secure               = True
  requestHeaders       = []
  path                 = "/v1/pull"
  queryString          = ""
  method               = "POST"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 ConnectionTimeout

Maybe we could retry the build of dependencies, to try to recover for thos ones

Windows build take so long because the Azure cache is not being used by stack. This also makes them more flaky, as stack has a non-zero chance of failing to connect to casa.fpcomplete.com.


Data manager: Some sessions are not listed

This started to happen when there are 281 sessions, around today.

Did some investigation with @seanholmes77 and confirmed that there is no skipped sessions. So this is WAI.


Replace temporary solution for CSS for new entry point

In #6458 we added the bundle generated by deep-insights to the vendor/stylesheets dir, AFAIK we should really use the https://github.com/CartoDB/CartoAssets once it's ready, so as part of integrating that this temporary CSS should be :fire:

Reopening because we still need to :fire: the temporary files as parto f adding cartoassets https://github.com/CartoDB/cartodb/commit/76d3f19072f3d50f5ca6dc4b4d848e4c676e471b
cc @xavijam

:ok_hand:

It should be covered in branch: issue-6455.


Bug: set temperature has value 6553.5 on fan only

Weird bug for you, if you set the mode to Fan Only, the set temperature goes to 6553.5C

I wonder if the integration should just not update the set temperature if the value= 6553.5? (i.e. leave it as the previous value)
Alternatively, it could be set as unavailable but that will be less useful for running automations off the currently set temperature.

+1 this bug is making it tricky to setup some automations.
Appreciate anything you can do to resolve.

Sorry for being AWOL. I will try to fix the bug tomorrow!

Fixed in 0a3da779ee324a395411157117aca85132a8f633

Sorry to say I think this bug still exists.
If my unit is set to 22, and then I turn on fan mode when exiting fan mode, it sets the temp to 6553.5 again.
It looks like this chap had the same issue and fixed it, if that's useful.
https://github.com/bigmoby/fglair_for_homeassistant/issues/45

Hi @danielkaldheim if it could help you or give you some hints, I've tried to solve as follows:
    async def async_set_display_temperature_degree(self) -> float | None:
         data = None
         if self._adjust_temperature is not None:
             adjust_temperature_value = self._adjust_temperature["value"]
             if adjust_temperature_value == 65535:
                 datapoints = await self._async_get_device_property_history(
                     self._adjust_temperature["key"]
                 )
                 # Get the latest setting other than invalid value
                 for datapoint in reversed(datapoints):
                     if datapoint["datapoint"]["value"] != 65535:
                         adjust_temperature_value = int(datapoint["datapoint"]["value"])
                         break
             data = round((adjust_temperature_value / 10), 1)
         return data

In other words, I seek in history the last valid value.

Thank guys for reporting issues!
I did some changes in https://github.com/danielkaldheim/ha_airstage/releases/tag/v1.1.6 and hopefully this resolve the issue. Thanks @bigmoby!
I'll keep the issue open a few days just incase.

Thanks for the update, sorry to say... I have come across an interest bug which I assume is connected...
If the unit is set to fan mode and then I attempt to turn it off, I get the following error pop up.
Failed to call service climate/set_hvac_mode. int() argument must be a string, a bytes-like object or a real number, not 'NoneType'
If I set it to heat or cold I am then able to turn it off.
This is running v.1.1.6

@changeableface thanks for reporting! I think I know why this is failing. I'll investigate.

Hopefully fixed in

Yeah, that appears to have done the trick.
Nice one bruva! 😎


GridModel supports treeGridStyleMode property - Fixes #1250

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

We need a toolbox toggle for this in the 'options' sidebar.  Saw that the
associated branch has this manipulable in the portfolio, example -- that
really just makes sense for dev purposes, we won't want this for merging.
I am going to go back on what I said earlier -- for symmetry lets make this
visual property behave just like the myriad of other visual properties on
GridModel, that is , not observable, but settable -- e.g.:
get rowBorders() { return this.agGridModel.rowBorders }
setRowBorders(rowBorders) { this.agGridModel.setRowBorders(rowBorders) }
On Wed, Oct 14, 2020 at 9:20 AM Don<EMAIL_ADDRESS>wrote:

@febbraiod commented on this pull request.
In cmp/grid/GridModel.js
https://github.com/xh/hoist-react/pull/2101#discussion_r504670656:

@@ -253,7 +258,8 @@ export class GridModel {
showHover = false,
rowBorders = false,
cellBorders = false,

   stripeRows = true,

   treeGridStyleMode = 'none',

   stripeRows = treeGridStyleMode == 'none' ? true : false,

Got it. Didn't mean to imply insistence, just wanted to put all the info
on the table
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/xh/hoist-react/pull/2101#discussion_r504670656, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARTL2I5EAXMMXFYEHSPS5LSKWQSHANCNFSM4R6I5EYQ
.


Enh motor bundle

closes #435

Did someone at NSLS-II break the Debian packages? https://travis-ci.org/NSLS-II/ophyd/jobs/271019267#L665
@klauer -- Any idea what would cause that?

Looks like someone changed it just today, breaking a bunch of CI:
main has been removed: http://epics.nsls2.bnl.gov/debian/dists/
wheezy, staging directories have been updated: http://epics.nsls2.bnl.gov/debian/dists/wheezy/
Probably would have been wise to use the distribution name URL to start with, but perhaps as a short-term fix you could ask around and see if someone can symlink them?

Leon:

I don't see Debian version (code name) in error messages. Release file is inside of directory structure - one in jessie, another in wheez etc. Similar is valid for Ubuntu - if you look at other lines that Stu referred - is has trusty in there, but nothing similar in Debian lines. bnl.gov is a simple mirror from our local repository accessible from controls network. Both look good to me. My take - somebody dropped Debian version from the code that is not happy any more.

I think my finger-pointing was premature. Note the double spaces here, highlighted with underlines: deb http://epics.nsls2.bnl.gov/debian/__main contrib. EPICS_DEB_DIST isn't set here.
main, of course, is just a subdirectory in the distro one.

Pseudo-positioner should probably just have it's own version of hints.

@tacaswell Would you move 0fdcc5a to a separate PR? We may want to handle this the new way we are handling caproto (source installs).

I think I need the other docker for the tests to work.

try rebasing to make the tests happy


📜 Add v8.0.0 predicates documentation version

📜 Documentation update
🎉 A new version of axone-protocol/axoned is available.
This PR add this new v8.0.0 version into the documentation.

Summary by CodeRabbit

New Features

Introduced various predicates for handling blockchain-related data, including:

bank_locked_balances/2 for retrieving locked balances.
bank_spendable_balances/2 for retrieving spendable balances.
bech32_address/2 for converting bech32 encoded strings.
block_height/1 for current block height.
block_time/1 for current block time.
chain_id/1 for current chain ID.
crypto_data_hash/3 for computing data hash.
did_components/2 for dissecting DIDs.
ecdsa_verify/4 and eddsa_verify/4 for signature verification.
hex_bytes/2 for hexadecimal conversion.
json_prolog/2 for JSON-Prolog conversion.
open/3 and open/4 for stream handling.
read_string/3 for reading strings from streams.
string_bytes/3 for string-byte conversion.
uri_encoded/3 for URI encoding/decoding.

Added consult/1 and current_output/1 predicates for Prolog file and stream handling.
Updated documentation to include these new features in version "v8.0.0".

@coderabbitai ignore


⚠ Processors has degraded performance

In 0f96f89, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 83 ms

Resolved: Processors performance has improved in 2510cdf.


Feature: Add partial support of traffic control qdisc

Missing parts:
* Parse TCA_OPTIONS for each kind of qdisc
* Parse TCA_STATS_APP for each kind of qdisc
* Parse TCA_XSTATS for each kind of qdisc
* Parse TCA_STATS_PKT64
* Parse TCA_STATS_RATE_EST

Closing as I receive no reply from TC team and I don't want to speed time on this enormous project.


youtube-dl cannot login to lynda.com

Does anybody know why I cannot log into Lynda.com?
C:\youtube-dl http://www.lynda.com/Access-tutorials/Access-2013-Essenti
al-Training/115857-2.html --username<EMAIL_ADDRESS>--password secret --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'http://www.lynda.com/Access-tutorials/Access-2013-
Essential-Training/115857-2.html', u'--username', u'PRIVATE', u'--password', u'P
RIVATE', u'--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2015.11.02
[debug] Python version 2.7.10 - Windows-8-6.2.9200
[debug] exe versions: none
[debug] Proxy map: {}
[lynda:course] Logging in as<EMAIL_ADDRESS>[lynda:course] 115857: Downloading course JSON
[download] Downloading playlist: Access 2013 Essential Training
[lynda:course] playlist Access 2013 Essential Training: Collected 84 video ids (
downloading 84 of them)
[download] Downloading video 1 of 84
[lynda] Logging in as<EMAIL_ADDRESS>ERROR: Unable to log in; please report this issue on https://yt-dl.org/bug . Mak
e sure you are using the latest version; type  youtube-dl -U  to update. Be sure
to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "youtube_dl\YoutubeDL.pyo", line 661, in extract_info
File "youtube_dl\extractor\common.pyo", line 289, in extract
File "youtube_dl\extractor\common.pyo", line 283, in initialize
File "youtube_dl\extractor\lynda.pyo", line 25, in _real_initialize
File "youtube_dl\extractor\lynda.pyo", line 83, in _login
ExtractorError: Unable to log in; please report this issue on https://yt-dl.org/
bug . Make sure you are using the latest version; type  youtube-dl -U  to update
. Be sure to call youtube-dl with the --verbose flag and include its complete ou
tput.

Duplicate of #7361.


Unhandled Exception: NoSuchMethodError: The getter 'defaultBinaryMessenger' was called on null.

E/flutter (27819): [ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: NoSuchMethodError: The getter 'defaultBinaryMessenger' was called on null.
E/flutter (27819): Receiver: null
E/flutter (27819): Tried calling: defaultBinaryMessenger
E/flutter (27819): #0      MethodChannel.get:binaryMessenger (package:flutter/src/services/platform_channel.dart:138)
E/flutter (27819): #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:312)
E/flutter (27819):
E/flutter (27819): #2      MethodChannel.invokeMapMethod (package:flutter/src/services/platform_channel.dart:347)
E/flutter (27819):
E/flutter (27819): #3      SharedPreferences._getSharedPreferencesMap (package:shared_preferences/shared_preferences.dart:152)
E/flutter (27819):
E/flutter (27819): #4      SharedPreferences.getInstance (package:shared_preferences/shared_preferences.dart:25)
E/flutter (27819):
E/flutter (27819): #5      SPUtils.init (package:island/utils/sp_utils.dart:15)
E/flutter (27819):
E/flutter (27819): #6      main (package:island/main.dart:22)
E/flutter (27819):
E/flutter (27819): #7      _runMainZoned.. (dart:ui/hooks.dart:218)
E/flutter (27819): #8      _rootRun (dart:async/zone.dart:1124)
E/flutter (27819): #9      _CustomZone.run (dart:async/zone.dart:1021)
E/flutter (27819): #10     _runZoned (dart:async/zone.dart:1516)
E/flutter (27819): #11     runZoned (dart:async/zone.dart:1500)
E/flutter (27819): #12     _runMainZoned. (dart:ui/hooks.dart:210)
E/flutter (27819): #13     _startIsolate. (dart:isolate-patch/isolate_patch.dart:305)
E/flutter (27819): #14     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172)
[√] Flutter (Channel master, v1.8.5-pre.101, on Microsoft Windows [Version 10.0.17763.107], locale zh-CN)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Android Studio (version 3.4)
[√] Connected device (1 available)
• No issues found!

When i switch to the stable. There is no error.
[√] Flutter (Channel stable, v1.7.8+hotfix.4, on Microsoft Windows [Version 10.0.17763.107], locale zh-CN)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Android Studio (version 3.4)
[√] Connected device (1 available)
• No issues found!

The change responsible for this has been reverted. Can you check that everything is wokring again as expected? Feel free to reopen this, if not.

@goderbauer
I'm still seeing this error on today's master
2019-08-31 16:02:29.895644+0900 Runner[16318:16525335] [VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: NoSuchMethodError: The getter 'defaultBinaryMessenger' was called on null.
Receiver: null
Tried calling: defaultBinaryMessenger
#0      PlatformAssetBundle.load (package:flutter/src/services/asset_bundle.dart:98)
<asynchronous suspension>
#1      AssetBundle.loadString (package:flutter/src/services/asset_bundle.dart:67)
<asynchronous suspension>
#2      CachingAssetBundle.loadString.<anonymous closure> (package:flutter/src/services/asset_bundle.dart:162)
#3      _LinkedHashMapMixin.putIfAbsent (dart:collection-patch/compact_hash.dart:291)
#4      CachingAssetBundle.loadString (package:flutter/src/services/asset_bundle.dart:162)

[✓] Flutter (Channel master, v1.9.8-pre.32, on Mac OS X 10.13.6 17G8030, locale en-JP)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.1)
[!] Android Studio (not installed)
[✓] VS Code (version 1.37.1)
[✓] Connected device (1 available)

I m also getting this error.
[VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: NoSuchMethodError: The getter 'defaultBinaryMessenger' was called on null.
Receiver: null
Tried calling: defaultBinaryMessenger
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:51)
#1      get:defaultBinaryMessenger (package:flutter/src/services/binary_messenger.dart:87)
#2      MethodChannel.get:binaryMessenger (package:flutter/src/services/platform_channel.dart:140)
#3      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:314)

#4      OptionalMethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:429)

#5      SystemChrome.setPreferredOrientations (package:flutter/src/services/system_chrome.dart:228)

#6      main (package:tempah_app/main.dart:34)

#7      _runMainZoned.. (dart:ui/hooks.dart:229)
#8      _rootRun (dart:async/zone.dart:1124)
#9      _CustomZone.run (dart:async/zone.dart:1021)
#10     _runZoned (dart:async/zone.dart:1516)
#11     runZoned (dart:async/zone.dart:1500)
#12     _runMainZoned. (dart:ui/hooks.dart:221)
#13     _startIsolate. (dart:isolate-patch/isolate_patch.dart:305)
#14     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172)
[VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: NoSuchMethodError: The getter 'defaultBinaryMessenger' was called on null.
Receiver: null
Tried calling: defaultBinaryMessenger
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:51)
#1      get:defaultBinaryMessenger (package:flutter/src/services/binary_messenger.dart:87)
#2      MethodChannel.get:binaryMessenger (package:flutter/src/services/platform_channel.dart:140)
#3      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:314)

#4      SharedPreferences.getInstance (package:shared_preferences/shared_preferences.dart:25)

#5      main (package:tempah_app/main.dart:42)
#6      _AsyncAwaitCompleter.start (dart:async-patch/async_patch.dart:43)
#7      main (package:tempah_app/main.dart:26)
#8      _runMainZoned.. (dart:ui/hooks.dart:229)
#9      _rootRun (dart:async/zone.dart:1124)
#10     _CustomZone.run (dart:async/zone.dart:1021)
#11     _runZoned (dart:async/zone.dart:1516)
#12     runZoned (dart:async/zone.dart:1500)
#13     _runMainZoned. (dart:ui/hooks.dart:221)
#14     _startIsolate. (dart:isolate-patch/isolate_patch.dart:305)
#15     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172)
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.9.8-pre.35, on Mac OS X 10.14.5 18F132, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2)
[✓] Android Studio (version 3.4)
[✓] VS Code (version 1.37.1)
[✓] Connected device (1 available)
• No issues found!

The issue should be reopen @goderbauer.

same issue

We would need additional information to re-open this. How does the error reproduce? Can somebody post a minimal code example that shows the error?
Also, did you update your app as explained in https://groups.google.com/forum/#!topic/flutter-announce/sHAL2fBtJ1Y: If you use message channels before calling runApp you need to initialize the  bindings manually by calling WidgetsFlutterBinding.ensureInitialized().

@goderbauer thank you, with WidgetsFlutterBinding.ensureInitialized() works fine

With this line before runApp WidgetsFlutterBinding.ensureInitialized(); it works but we should not have to do this. It's add complexity.

I think @mickyliu945 is right,
After switching the channel to stable in the terminal, everything works just fine.
Go to terminal and type: flutter channel stable
When running the app in debug / release mode it will work again.

It's worked with WidgetsFlutterBinding.ensureInitialized();.  My flutter version is 1.17.4


Improve textureSize usage in process material

Godot version
4.2beta3
System information
Fedora, RX 590
Issue description
Follow up to https://github.com/godotengine/godot/pull/83831
The particle system currently uses textureSize() an unnecessary amount of times and it needs to be optimized.
Steps to reproduce
/
Minimal reproduction project
/

Basically we just need to read textureSize once and store it in a variable that we use later. We can read it at the same time that we initialize all the randomness params.


Support merging classes and modules across files

I currently have a setup something like this:
A.ts
module mod {
  export class A {
  }
}

B.ts
/// <reference path="A.ts" />
module mod.A {
  export class B extends A {
  }
}

But I'm getting the error in B.ts:
A module declaration cannot be in a different file from a class or function with which it is merged.
It works fine, however, if the declarations are in the same file: Playground
In my compiler options, I'm concatenating all the files together in the output, so shouldn't it not matter that they're in different source files? Even if the output wasn't concatenated, I don't understand how the declarations being in separate files changes anything.
Basically, the structure I'm going for is that A is going to have a lot of subclasses, and I wanted to have them all be in a module also called A. It just makes sense organizationally to me.
Why is this not allowed? Is there a way around it?

It isn't allowed because we can't be sure about the ordering of the files. A.ts must execute first; this is different from other module merging scenarios because those can generally take place in any order.

But if I'm compiling with concatenated output, can't you guarantee the order of execution?

There are simple cases the compiler could know it's safe (but doesn't today), and more complex cases that would be harder (if not impossible) to analyze correctly. We generally haven't yet seriously invested in features that require analyzing ordering (whether code within a file, or file ordering itself), especially if that investment would still only cover some of the relevant scenarios (ex only allow classes and modules to merge in specific ordering and with --out). And of course there's another alternative where we don't give an error at all and leave it up to the user to make sure the ordering is working correctly/as intended. I'll edit the title a bit to reflect the suggestion.

Okay, I understand, and I see the potential difficulty of the general problem. I can adjust my model to work around this, but if in the future support is built for module/class/function dependency ordering that would be great.

I need this, too.

:+1:

+1

We would need this feature as well.

On "module":"es2015" and "target":"es3"
We should only require to delete the export { MyClass }; an the files would be ready to concat following the order of the imports and if something have been already imported, dont concat them

Accepting PRs for this - just re-use the existing logic we have for detecting if two constructs will be in the right order in an outFile

@RyanCavanaugh Should I writte a proposal of how this should work before send the PR?

There shouldn't be anything to propose other than "correctly don't issue the error when the code would work". The emit should be the same; if you think it should be something different then we should get on the same page about what the scenario is

I kinda need this feature too. Any recent updates?
Also, what would the import statements look like for importing these "distributed" class/namespace declarations?

Non-module compilation is basically extinct at this point, and no one has bothered implementing this since the seven years since it was approved, so let's just not bother at this point.


JAV-44 Removed vendor packages and introduced Gom to handle dependencies

Removed the vendor code except "didip/tollbooth" and "grpc-ecosystem", these two packages has been modified and none of the opensource version matches the current code.

Coverage decreased (-0.4%) to 71.237% when pulling 51dad05b902a7264be09748ece8aa945b6b9202f on asifhuawei:vendor into 0dede59abfd194136a52989b241c4d4447bcf82c on ServiceComb:master.

Codecov Report

Merging #13 into master will decrease coverage by 0.33%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #13      +/-   ##
=========================================
- Coverage   67.54%   67.2%   -0.34%
=========================================
  Files          12      13       +1
  Lines        3260    3376     +116
=========================================
+ Hits         2202    2269      +67
- Misses        828     877      +49
  Partials      230     230

Impacted Files
Coverage Δ

server/service/services_dependency.go
67.29% <0%> (-0.31%)
:arrow_down:

common/query_filter.go
0% <0%> (ø)
:arrow_up:

common/HSAError.go

server/service/microservice/versionrule.go
100% <0%> (ø)

server/service/microservice/microservice.go
5.66% <0%> (ø)

server/service/query_rule_service.go
78.12% <0%> (+0.34%)
:arrow_up:

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 0dede59...51dad05. Read the comment docs.

@asifhuawei
why are the following two vendor repos not removed?

didip/tollbooth
grpc-ecosystem

@seanyinx
These two vendor packages has been changed by the sc team and we don't have any open source version of these two packages which matches the current code. So basically we don't have any open source repo's or commits which matches these vendor's.


python310Packages.ansible-lint: 6.12.2 -> 6.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.ansible-lint is: Best practices checker for Ansible
meta.homepage for python310Packages.ansible-lint is: https://github.com/ansible/ansible-lint
meta.changelog for python310Packages.ansible-lint is: https://github.com/ansible/ansible-lint/releases/tag/v6.13.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.13.0 with grep in /nix/store/022y2panwq210266i77q7b1dwwvqw87v-python3.10-ansible-lint-6.13.0
found 6.13.0 in filename of file in /nix/store/022y2panwq210266i77q7b1dwwvqw87v-python3.10-ansible-lint-6.13.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
ansible-lint
python310Packages.ansible-lint
python311Packages.ansible-lint

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/022y2panwq210266i77q7b1dwwvqw87v-python3.10-ansible-lint-6.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.ansible-lint https://github.com/r-ryantm/nixpkgs/archive/c54e18dc013199b1c87d4dc730a95384ec8b6491.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/022y2panwq210266i77q7b1dwwvqw87v-python3.10-ansible-lint-6.13.0
ls -la /nix/store/022y2panwq210266i77q7b1dwwvqw87v-python3.10-ansible-lint-6.13.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

python311Packages.ansible-lint

1 package built:

ansible-lint (python310Packages.ansible-lint)

Maintainer pings
cc @sengaya for testing.

Result of nixpkgs-review pr 216599 run on aarch64-darwin 1

1 package failed to build:

python311Packages.ansible-lint

1 package built:

ansible-lint (python310Packages.ansible-lint)


Add Dependabot for GHA updates and template install-nix-action version in README.md

Related to discussion in #21 (but something I was planning to look into at some point anyway), I've added a quick implementation to enable dependabot and made it so the cachix/install-nix-action version used in the workflow is copied to README.md when generated. I'm open to better ideas of how to handle this, though, because this is clearly not quite ideal
I also fixed a (apparently harmless) typo in the get_eval invocation in update.rb that I happened to notice
Successful Run: https://github.com/lilyinstarlight/nix-unstable-installer/actions/runs/1495536686
Corresponding Release: https://github.com/lilyinstarlight/nix-unstable-installer/releases/tag/nix-2.5pre20211026_5667822
Release README.md: https://github.com/lilyinstarlight/nix-unstable-installer/blob/nix-2.5pre20211026_5667822/README.md
Dependabot PR Examples: https://github.com/lilyinstarlight/nix-unstable-installer/pulls?q=is%3Apr+author%3Aapp%2Fdependabot+
Quick question: Should we update the README.md file manually for now to update the cachix/install-nix-action version in the example, since it seems that older cachix/install-nix-action version now errors in GitHub Actions? (And also since I'm not sure when the Nix x86_64-darwin and aarch64-darwin flakey test failures will be fixed at https://hydra.nixos.org/jobset/nix/master/evals)

I'm going to trigger a release workflow manually and that should fix everything.

looks like there was no new version available

Yep, the Darwin builds have been failing after the new non-blocking GC was merged to unstable last month -- ref NixOS/nix#5502


Migrate compose.db to enable aggregate on queries

Heroku still uses an old MongoDB version (2.6) and 3.x is needed for aggregate queries...

Compose is never planning to update heroku version to more than 2.6:

We should probably think about either choosing another mongodb add-on, or move to Compose.io externally from Heroku. Both these solutions require migrating the database.


Add support for other social media handles in page and project author metadata

It's possible to add social media links to the metadata for each author in a page or book. For example the page-level config like the following:
authors:
- name: Jo the Jovyan
  affiliation: Planet Jupyter
  twitter: projectjupyter

Results in:

Option 1: Add other social media networks
In addition to Twitter, we could add support for other major social media links like:

BlueSky
Mastodon
Threads

Option 2: Generalize this so others can add arbitrary data
Another option would be to generalize this pattern into something that anybody could attach a URL + icon to. For example:
authors:
- name: Jo the Jovyan
   icons:
   - url: https://x.com/projectjupyter
      icon: fa-twitter

Related issues

This issue is the same idea but applied at the book level: https://github.com/jupyter-book/myst-theme/issues/362

Definitely something we want to support - here's the tracking issue for this in the html theme repository:

https://github.com/jupyter-book/myst-theme/issues/362

Great!

I thought about it more and do think this is distinct from https://github.com/jupyter-book/myst-theme/issues/362 so I've updated the body of this issue and focused it on author metadata!

I like the more general solution!

Thanks Chris.


Adding another related project to README.md

DeepLogic AI is a commercial service that can extract data from digital invoices (PDFs), scanned invoices, and handwritten forms.
Related to #300

Thanks @duskybomb! Is it your startup? 😄


Type: FREE is missing in the HITS DB

Hello
In the version 1.2.1 the Type: FREE is missing in the HITS DB
Pleas repair this problem

Well you got a custom one too which replaced FREE:

Yes but some config have both, and when i click costume it don't give the info of free.

You Can Free in LiteDB tell that Zalando have free info, but when i click custom don't give nothing

First of all that version you have is not the master branch, and it's not supported by me, so you shouldn't post here. So basically your issue is that user-defined custom keychains do not display the related hits correctly in the hits DB. I will look into it.

By the way @ForlaxPy could you add like (Forlax Mod) on the title of your releases? Because people are starting to contact me with issues related to that build thinking I made that update. Thank you so much.

Oh yes sure, sorry for the inconvenient

@flyal could you please to try to add this  [CUSTOMKC] Name=FREE Color=OrangeRed
To the Environment.ini in Settings. I think that's why it's missing

Ok i will try it now. Thnx

Yeah most definitely @ForlaxPy solution will work, let us know

Now it display the free but remove the custom. Or to add both?

@flyal totally up to you, you can keep the custom one or remove it but Id suggest you to keep it as it's built in the main OB and most of config makers are using it.

Ok thnx

Perfect, I'll close this then ^_^

I try, the solution is to have both
it work display free and custom
[CUSTOMKC]
Name=CUSTOM
Color=OrangeRed
[CUSTOMKC]
Name=FREE
Color=OrangeRed
Environment.zip


Bonfire: Confirm the Ending - A test case requests true for what should be false.

Challenge Bonfire: Confirm the Ending has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36</code

.
Please describe how to reproduce this issue, and include links to screenshots if possible.

The test case shown in the screenshot asserts true, where it should be false. If we are matching the last character or word in a string with the target, then you can clearly see it in the case
end("He has to give me a new name", "me") should return true.

that the last word "name" is not same as the target "me".
My code:
function end(str, target) {
  // "Never give up and good luck will find you."
  // -- Falcor
  var n = str.split(" ");

  if (str.slice(-1) === target || n[n.length - 1] === target) {
    return true;
  } else {
    return false;
  }

}

end("Bastian", "n");

I don't see anywhere in the instructions that states that it has to be a word or single character. They simply state Check if a string (first argument) ends with the given target string (second argument).
Closing as not a problem with the tests but feel free to reply if you need further clarification or see conflicting instructions that I missed.
Thanks and happy coding!

Yes, your comment has made the fact a lot clearer that the questions asks to check if a string (first argument) ends with a given target string (second argument).
But in the test case which I pointed out, the given string "He has to give me a new name" does not end with target string "me", and so it should return false. But the test case asks to return true.
Please correct me if I am wrong. Thank you for your prompt reply.

@av-7 A string can be any length, it does not have to be a word. So that test should return true because me are the last two characters in the string He has to give me a new name

@ltegman Yes, I get it now. Thank you for the clarification.

function end(str, target) {
// "Never give up and good luck will find you."
// -- Falcor
var len=target.length;
if(target==str.substr(-len,len)){
return true;
}else{
return false;
}
}
end("Bastian", "n");
The right answer for the question using the hint given.


Corrected Ars Magica, Added Tinker's Steelworks

Ars Magica is spelled without a K.  One of those things I could have avoided just by looking at the mod's page. :-/
Aside from that, I've added limestone generation for Tinker's Steelworks.

I think you might have forgotten to add the include directives to CustomOreGen_Config_Default.xml. Also, the files need to be exported from the jar by adding them to the list in CustomOreGenBase.java.

I see.  Well, shows what I know about Java.  Fixing it now.  Also adding GeoStrata stone configuration.

re


Gotcha using workspace-dotted without specifying a version

Setup
My hakari.toml has:
workspace-hack-line-style = "workspace-dotted"

My root Cargo.toml has:
[workspace.dependencies]
my-workspace-hack = { path = "/path/to/my-workspace-hack" }

After initial setup (generate then manage-deps) all workspace packages have the following added as expected:
[dependencies]
my-workspace-hack.workspace = true

Issue
Later, when re-running cargo hakari manage-deps (or running cargo hakari --dry-run --quiet in CI), hakari reports that many packages are missing the my-workspace-hack dependency and attempts to add them again (or fail in the case of the CI job).
I debugged this and discovered the error, namely that the workspace dependency must specify a version as well as a path, i.e.:
[workspace.dependencies]
my-workspace-hack = { version = "0.1.0", path = "/path/to/my-workspace-hack" }

I traced this to the following code, which in my case always hits the first else clause (link.version_req() == &VersionReq::STAR) when the hakari package has no version:
https://github.com/guppy-rs/guppy/blob/07c17f96f37ebd75d11e30428a1a3bfa4e23cdfa/tools/hakari/src/cli_ops/manage_deps.rs#L153-L164
So whilst this is not a bug, it is a gotcha and the cause is non-obvious (I had to step through in the debugger).  Perhaps something could be added to surface this (likely not what the user intended) behaviour more directly?  Perhaps running without an given version should be an explicit opt-in?
Documentation
The documentation does talk about this to an extent, though in a different context (I skipped reading the section initially as it did not apply to my circumstances).
It say (emphasis mine):

This option lets you specify the path to the workspace-hack crate, once, in the root Cargo.toml

And then shows an example where only the version is given:
[workspace.dependencies]
my-workspace-hack = "0.1.0"  # or another version number if you've changed it

So perhaps the need to specify the version could be made more prominent in the documentation?

Thanks, good catch! I think we can update the check to not require that the version be specified -- I don't think there's a reason to require it.

This is now out in cargo-hakari 0.9.30.


[dep] Add yamllint.

Arch  https://aur.archlinux.org/packages/yamllint/  (not sure if there's any difference among distros)
Gentoo https://gpo.zugaina.org/dev-util/yamllint     (not even sure if this the official website but this is the only one I found)
Debian https://packages.debian.org/source/buster/yamllint
Fedora https://admin.fedoraproject.org/pkgdb/package/rpms/yamllint/  (not sure if there's any difference among distros)
Ubuntu https://packages.ubuntu.com/source/xenial/yamllint  (only available Xenial onward)

Thanks, all comments addressed.

Thanks for iterating. There seems to still be an alphabetical order issue as yamllint should go before yasm and after yaml-cpp


New Release

Hi maintainers,
What are the requirement for making a new official release?
I would like to benefit from the changes already made to the $env expansion in this PR, however this is not yet included in the latest release (2023.8.0).
Could you consider making a new release including these enhancements?
Thanks in advance.

The fix should be in pre-release version  2023.9.10681010. We typically make releases after couple of weeks of feedback on fixes and stability of the pre-release versions.


gfn-electron: init at 1.13.0

Description of changes
Adding electron based Geforce Now client
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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

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

1 package built:

gfn-electron

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2729

Closing since I have not been using gfn-electron it for a while


v2.0.0 - Email field missing

The new version 2.0.0 doesn't have the email field anymore. I removed the integration to get rid of the old (not used) tunnels.
After I want setup the integration this email filed was gone.
Cleared cache, restart safari didn't help as well

There has been an improvement in security; now, neither the email nor the Global API is used. Instead, the Account ID and an API token that you have to create in Cloudflare are used.
You need to create a custom token.

Done and working!


Added AWKUM KP Pakistan

@abdulsamadbukhari Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Feature: Support for DSN flag - sendStringParametersAsUnicode

This is a feature addition for a new DSN flag - sendStringParametersAsUnicode which basically allows us to specify if the Go default string types should be sent as UNICODE(if true) or not(if false).
Official Support for sendStringParametersAsUnicode in JDBC

@microsoft-github-policy-service agree

@stuartpa @apoorvdeshmukh can you please check this PR?

please add some functional tests showing what problem this is solving

@shueybubbles problem this PR solves is mentioned here - https://github.com/microsoft/go-mssqldb/issues/40

@shueybubbles I agree to your point that it will change for all input parameters that are of the string type, but it will only happen for the clients opting for it specifically. It's a backward compatible change as by default this flag is false itself.

@shueybubbles have added test cases for the above please check, also this feature is in accordance with the Official JDBC driver as well.

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

Project coverage is 74.54%. Comparing base (fe7c3d4) to head (28f3fbf).
Report is 2 commits behind head on main.

Files
Patch %
Lines

mssql.go
85.71%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #180      +/-   ##
==========================================
- Coverage   74.72%   74.54%   -0.18%
==========================================
  Files          32       32
  Lines        6298     6341      +43
==========================================
+ Hits         4706     4727      +21
- Misses       1316     1331      +15
- Partials      276      283       +7

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


Add lambda function "invoke" helper.

I tend to use this a lot in my infrastructure tests.

We just merged in the tf12 update, so if you can rebase this branch on master, I can go ahead and kick off the tests. Thanks for waiting!

@yorinasub17 I just rebased. No problem in waiting.

Thanks! Just kicked off our build.

The build failed, but it was for a known flaky test, so I am going to go ahead and merge + release this. Thanks for the contribution!

Thanks @yorinasub17!


feat: Integrate tools to optimize circuits

Related: https://github.com/google/heir/issues/110
We can take a high-level arithmetic program and create optimization passes that can invoke tools like Yosys and ABC to optimize and output a combinational circuit.
The combinational circuit can then be lowered to boolean FHE schemes.

See this other tool here: https://github.com/lsils/mockturtle
And some discussion about this here: https://discourse.llvm.org/t/integration-with-abc-optimizer/65264/2

I think it would be nice to go
Arith / other high-level -> Combinational logic block -> [ABC Transform] -> Optimized combinational logic block
Combinational logic can then be lowered to  schemes that support boolean gates / luts.

I also noticed this ArithToCombPass from CIRCT:
https://github.com/llvm/circt/blob/main/include/circt/Transforms/Passes.td#L56C5-L71

I think we can mark this one as fixed now.

Reopening so we can migrate the TODOs to new issues


Scripts not uploading to jamfcloud instance

We have a relatively new JamfCloud instance and we are trying to use jamf-migrator to migrate scripts from an on-prem Jamf Pro instance to our cloud instance. Only 7 of the scripts upload. The 100+ others don't and throw 409 errors. git2jss has the same issue, so I'm guessing it's some kind of error handling or API related thing with jamfcloud.

Looks like I get 409s for two primary reasons:

Category the script is in doesn't exist in the target JSS
EAs that have ? (or potentially other special characters) in the name

Would it be possible to include some error handling for these situations? Maybe if a category isn't available put the script in None?

Good idea.  I'll fix it so if the category is not there it sets it to none.  This should apply to anything missing a category like policies.  I'll try to do the same for buildings and departments.  Tackle the special chars in the name next.

Category, building, and department will be dropped if they do not exist on the destination server.  Couldn't replicate the issue with a ? in the name of an extension attribute.  I get the following in the log, and verified the EA was created on the destination server.
20181109_17:16:57 [CreateEndpoints] [computerextensionattributes] succeeded: test - !@#$%^&*
20181109_17:16:57 [CreateEndpoints] [computerextensionattributes] succeeded: test - ?
Wonder if I could get the XML from one of the EAs that failed.


Hover makes all elements Black

Description
when you hover on the post you cannot see the like, comment section ...etc. as shown below
Steps to reproduce
hover on post
Screenshots

Desktop (please complete the following information)
os - windows
browser - edge
Smartphone (please complete the following information)
No response
Additional information
No response

please assign it to me, I want to work on this issue

hey @narayansoni, should i start working on it ?

sure go ahead!


Add SENTRY_RELEASE to the Docker image environment when built

Problem

@krysal pointed out that Sentry consumes some things automatically from the environment. SENTRY_ENVIRONMENT for example, which we set in the ECS task definition. SENTRY_RELEASE is another one and one we could easily set in the Docker image so that we get better problem timelines.
Description

Add the SENTRY_RELEASE environment variable to the image. You may need to add a build arg with which to populate the ENV call.
Implementation

[ ] 🙋 I would be interested in implementing this feature.

More info from Sentry Documentation:

When you give Sentry information about your releases, you can:

Determine issues and regressions introduced in a new release
Predict which commit caused an issue and who is likely responsible
Resolve issues by including the issue number in your commit message
Receive email notifications when your code gets deployed

Additionally, releases are used for applying source maps to minified JavaScript to view original, untransformed source code.

The first part of the second point is particularly attractive. Would be great if is paired with the reactivation of the Sentry Release GitHub Action.  I guess it will require updating the <environment>-frontend-deploy/action.yml files (generated by terraform).


Improve support for local messages (fixes draft sync issue)

With drafts not being uploaded we now kind of have to support local messages. This doesn't add proper support for local messages, but should make local drafts work.
This PR introduces the following changes:

Don't remove local messages during folder sync. Prior to a sync we process all pending actions, including uploads. Previously that should have eliminated all local messages. Whatever local message was left over at that point was safe to be removed. With the introduction of local drafts this is no longer the case.
Remove local message after upload. The only way I can think of to have "left over" local messages is if we upload a message but don't get the server UID of the uploaded message. That way we can't update the local version of the uploaded message and it remains a "local only" message. We now check for this case and remove the local message. The uploaded message will then be downloaded during the next folder sync.
Add support for deleting local messages. We now simply skip all the remote operations when the user deletes a local message.

Fixes #2164

Good if drafts are not lost anymore, but I hope this is just a temporary fix, as I consider syncing drafts an important benefit of IMAP.


[master] Fix regression in evptests.txt

(a port to master of #3222 )
When compiling without EC support the test fails abruptly parsing some keys.
Some keys pulled in #3187  start with
------BEGIN EC PRIVATE KEY-----
this format is not supported without EC support.
This commit reformat those keys with the generic format. After this change the
test simply skips the unsupported EC keys when EC is disabled, without parsing
errors.

Checklist

[x] tests are added or updated

@levitte the port of #3222

Is it actually so that it's impossible to cherry-pick it to 1.1.0?

@dot-asm that's what #3222 is for: cherry-pick wasn't able to automatically merge the changes because of different edits to evptests.txt in the two branches!

Check this comment: https://github.com/openssl/openssl/pull/3222#issuecomment-294134456

thanks!

As a follow up to latest comment, #3226 is the pull request fixing the issue mentioned in https://github.com/openssl/openssl/pull/3222#issuecomment-294134456


PrimeVueResolver does not work well with Toast

The component <Toast /> works as intended if I imported it manually, but it does not appear after I added the PrimeVueResolver to the resolver. My other components work fine tho. I tried to solve the problem by removing import Toast from 'primevue/toast' and  .component('Toast', Toast) from my main.js but it does not help. It's probably an issue that needs to be looked into. Thank you.
Edit:
It seems to be only an issue during development because when I use npm run build and npm run serve, the toast component is working.

In my case, primevue's resolver is completely unavailable. PrimeVue version is 3.7.0.
By checking the source code, it is found that there is a problem with primevue's resolver.
Lowercase is used as the folder name in the primevue, while uppercase is used in the resolver, which needs to be corrected here.
Just try to write others resolver.
The Original resolver:
import { ComponentResolver, SideEffectsInfo } from '../../types'

const components = [
  'AutoComplete',
  'Calendar',
  'CascadeSelect',
  'Checkbox',
  'Chips',
  'ColorPicker',
  'Dropdown',
  'Editor',
  'InputMask',
  'InputNumber',
  'InputSwitch',
  'InputText',
  'Knob',
  'Listbox',
  'MultiSelect',
  'Password',
  'RadioButton',
  'Rating',
  'SelectButton',
  'Slider',
  'Textarea',
  'ToggleButton',
  'TreeSelect',
  'TriStateCheckbox',
  'Button',
  'SpeedDial',
  'SplitButton',
  'DataTable',
  'Column',
  'ColumnGroup',
  'DataView',
  'VirtualScroller',
  'FullCalendar',
  'OrderList',
  'OrganizationChart',
  'Paginator',
  'PickList',
  'Timelist',
  'Tree',
  'TreeTable',
  'Accordion',
  'AccordionTab',
  'Card',
  'DeferredContent',
  'Divider',
  'Fieldset',
  'Panel',
  'Splitter',
  'SplitterPanel',
  'ScrollPanel',
  'TabView',
  'TabPanel',
  'Toolbar',
  'ConfirmDialog',
  'ConfirmPopup',
  'Dialog',
  'OverlayPanel',
  'Sidebar',
  'Tooltip',
  'FileUpload',
  'Breadcrumb',
  'ContextMenu',
  'MegaMenu',
  'Menu',
  'Menubar',
  'PanelMenu',
  'Steps',
  'TabMenu',
  'TieredMenu',
  'Dock',
  'Chart',
  'Message',
  'Toast',
  'Carousel',
  'Galleria',
  'Image',
  'Avatar',
  'AvatarGroup',
  'Badge',
  'Chip',
  'BlockUI',
  'Inplace',
  'ScrollTop',
  'Skeleton',
  'ProgressBar',
  'ProgressSpiner',
  'Tag',
  'Terminal',
  'TerminalService',
]

export interface PrimeVueResolverOptions {
  /**
   * import style along with components
   *
   * @default true
   */
  importStyle?: boolean
  /**
   * import `primeicons' icons
   *
   * requires package `primeicons`
   *
   * @default true
   */
  importIcons?: boolean
  /**
   * imports a free theme - set theme name here (e.g. saga-blue)
   *
   * @default ''
   */
  importTheme?: string
}

/**
 * Resolver for PrimeVue - If you're using a component with the same tag as an native HTML element (e.g. button) the component must be in uppercase
 *
 * @link https://github.com/primefaces/primevue
 */
export function PrimeVueResolver(options: PrimeVueResolverOptions = {}): ComponentResolver {
  return (name: string) => {
    const sideEffects: SideEffectsInfo = []

    if (options.importStyle)
      sideEffects.push('primevue/resources/primevue.min.css')

    if (options.importIcons)
      sideEffects.push('primeicons/primeicons.css')

    if (options.importTheme) {
      sideEffects.push(
        `primevue/resources/themes/${options.importTheme}/theme.css`,
      )
    }

    if (components.includes(name)) {
      return {
        path: `primevue/${name}/${name}.vue`,
        sideEffects,
      }
    }
  }
}

Should be:
// ...
    if (components.includes(name)) {
      return {
        path: `primevue/${name.toLowerCase()}/${name}.vue`,
        sideEffects,
      }
   }

// ...

Just modify the 'path' line:
path: `primevue/${name}/${name}.vue`,

to:
path: `primevue/${name.toLowerCase()}/${name}.vue`,

It should fix it.
When I'm free, I'll PR.
You can submit it if it is convenient for you.

Before the patch, my primevue components are already working. After updating the package, The toast component is still having the same issue which doesn't not appear in npm run dev, but functional in npm run build then npm run serve. Since import ToastService from 'primevue/toastservice' and createApp(APP).use(ToastService)are necessary to make the toast component work, maybe exclude the toast component from the list, so manually import toast componentimport Toast from 'primevue/toast'andcreateApp(APP).component('Toast', Toast)` would work.


Admin Lite UI: Links to filtered lists of Organizations not working

Affects: All links of the format "X organizations" in the Admin Lite UI
Issue
As an administrator, when I examine lists of Programs or Countries, there is a link next to each object name with the format "X organizations". When I click on that link, I should be taken to a filtered list of organizations associated with that object, but I'm actually just taken to a list of all organizations.

Acceptance criteria

[ ] 1. When clicking on an "X organizations" link from the Programs page, I am taken to a filtered list of those organizations for which at least one associated user can view that program.

[ ] 2. When clicking on an "X organizations" link from the Countries page, I am taken to a filtered list of those organizations for which at least one associated user works on at least one program in that country.

Housekeeping

[ ]  Unit test/s written wherever applicable
[ ]  i18n tags included wherever applicable
[ ]  Functionality is accessible to people using screen readers

@hannalcamp Can you paste the browser URL of the Organizations view when this happens?

Yeah, the second screenshot is what happens when I click a "2 organizations" link.

QA Passed:

Both links to orgs from countries and programs page, appear to link properly to relevant organizations


PHP 5.5+ version

Can you make a version for 5.5+? Seems like only offering compatibility with 7.0 is a little aggressive.

@kjdion84 https://github.com/spatie/7to5 :nerd_face: :nerd_face:

That is cool.


Merge Filepath stdlib module with File module

$subject.

Completed with https://github.com/ballerina-platform/module-ballerina-file/pull/22


New Task: Build data dashboard

@MicPie, it seems I cannot add tasks to projects (perhaps they are scoped for the org and not the repo)
Adding a task for developing a GitHub page/dashboard that takes the meta might be nice.yaml files to make a simple dashboard/static page to get an overview of the datasets we have implemented.
Not a high priority, but a nice to have

(BTW, we might also assign "priority"  and "urgency" to the tasks in Eisenhower matrix style ;))


Issue-1493 Updated hibernate validator to 6.0.17.Final.

Pull Request Description
This pull request closes #1493
Acceptance Test

[x] Building the code with mvn clean install -Dintegration.tests still works.
[x] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[x] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[x] The tests in the strongbox-web-integration-tests still run properly.
[x] Snyk security check passes

Questions

Does this pull request break backward compatibility?

[ ] Yes
[x] No

Does this pull request require other pull requests to be merged first?

[x] Yes, strongbox/strongbox-parent#42 (PR-1503 does not need to be merged)
[ ] No

Does this require an update of the documentation?

[ ] Yes
[x] No

Files changed 0 @PrzemyslawCieslik  ? :)

Most-likely it's because of the version change in the strongbox-parent.

Files changed 0 @PrzemyslawCieslik ? :)

Because I change back to original snapshot version @fuss86

Thank you for your fixes! I'm closing this via the parent.


HDDS-2239. Fix TestOzoneFsHAUrls

What changes were proposed in this pull request?
Make sure context classloader is restored to avoid NPE during shutdown.
https://issues.apache.org/jira/browse/HDDS-2239
How was this patch tested?
Ran TestOzoneFsHAUrls in IDE.

/label ozone

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
40
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
37
hadoop-hdds in trunk failed.

-1
mvninstall
38
hadoop-ozone in trunk failed.

-1
compile
21
hadoop-hdds in trunk failed.

-1
compile
14
hadoop-ozone in trunk failed.

+1
checkstyle
61
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
1066
branch has no errors when building and testing our client artifacts.

-1
javadoc
21
hadoop-hdds in trunk failed.

-1
javadoc
18
hadoop-ozone in trunk failed.

0
spotbugs
1167
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
37
hadoop-hdds in trunk failed.

-1
findbugs
20
hadoop-ozone in trunk failed.

_ Patch Compile Tests _

-1
mvninstall
34
hadoop-hdds in the patch failed.

-1
mvninstall
43
hadoop-ozone in the patch failed.

-1
compile
25
hadoop-hdds in the patch failed.

-1
compile
18
hadoop-ozone in the patch failed.

-1
javac
25
hadoop-hdds in the patch failed.

-1
javac
18
hadoop-ozone in the patch failed.

-0
checkstyle
33
hadoop-ozone: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
871
patch has no errors when building and testing our client artifacts.

-1
javadoc
23
hadoop-hdds in the patch failed.

-1
javadoc
20
hadoop-ozone in the patch failed.

-1
findbugs
34
hadoop-hdds in the patch failed.

-1
findbugs
19
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
29
hadoop-hdds in the patch failed.

-1
unit
28
hadoop-ozone in the patch failed.

+1
asflicense
36
The patch does not generate ASF License warnings.

2747

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1600

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 40e4cb25f01b 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 10bdc59

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-compile-hadoop-ozone.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/diff-checkstyle-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/testReport/

Max. process+thread count
410 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozonefs U: hadoop-ozone/ozonefs

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/1/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
119
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
57
hadoop-hdds in trunk failed.

-1
mvninstall
46
hadoop-ozone in trunk failed.

-1
compile
19
hadoop-hdds in trunk failed.

-1
compile
13
hadoop-ozone in trunk failed.

+1
checkstyle
65
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
952
branch has no errors when building and testing our client artifacts.

-1
javadoc
20
hadoop-hdds in trunk failed.

-1
javadoc
17
hadoop-ozone in trunk failed.

0
spotbugs
1044
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
33
hadoop-hdds in trunk failed.

-1
findbugs
17
hadoop-ozone in trunk failed.

_ Patch Compile Tests _

-1
mvninstall
37
hadoop-hdds in the patch failed.

-1
mvninstall
37
hadoop-ozone in the patch failed.

-1
compile
23
hadoop-hdds in the patch failed.

-1
compile
16
hadoop-ozone in the patch failed.

-1
javac
23
hadoop-hdds in the patch failed.

-1
javac
16
hadoop-ozone in the patch failed.

+1
checkstyle
59
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
824
patch has no errors when building and testing our client artifacts.

-1
javadoc
21
hadoop-hdds in the patch failed.

-1
javadoc
17
hadoop-ozone in the patch failed.

-1
findbugs
31
hadoop-hdds in the patch failed.

-1
findbugs
18
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
28
hadoop-hdds in the patch failed.

-1
unit
23
hadoop-ozone in the patch failed.

+1
asflicense
37
The patch does not generate ASF License warnings.

2647

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1600

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux a09fa9b23a80 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 8de4374

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/testReport/

Max. process+thread count
305 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozonefs U: hadoop-ozone/ozonefs

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/2/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 80.155 s - in org.apache.hadoop.fs.ozone.TestOzoneFSInputStream
[INFO] Running org.apache.hadoop.fs.ozone.TestOzoneFsHAURLs

https://github.com/elek/ozone-ci-q4/blob/07087a6f1beec835a848cf7ee587509107334626/pr/pr-hdds-2239-t668n/integration/output.log#L2892

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
83
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
45
hadoop-hdds in trunk failed.

-1
mvninstall
40
hadoop-ozone in trunk failed.

-1
compile
18
hadoop-hdds in trunk failed.

-1
compile
13
hadoop-ozone in trunk failed.

+1
checkstyle
59
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
944
branch has no errors when building and testing our client artifacts.

-1
javadoc
20
hadoop-hdds in trunk failed.

-1
javadoc
16
hadoop-ozone in trunk failed.

0
spotbugs
1035
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
34
hadoop-hdds in trunk failed.

-1
findbugs
17
hadoop-ozone in trunk failed.

_ Patch Compile Tests _

-1
mvninstall
31
hadoop-hdds in the patch failed.

-1
mvninstall
34
hadoop-ozone in the patch failed.

-1
compile
21
hadoop-hdds in the patch failed.

-1
compile
16
hadoop-ozone in the patch failed.

-1
javac
21
hadoop-hdds in the patch failed.

-1
javac
16
hadoop-ozone in the patch failed.

+1
checkstyle
52
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
790
patch has no errors when building and testing our client artifacts.

-1
javadoc
19
hadoop-hdds in the patch failed.

-1
javadoc
17
hadoop-ozone in the patch failed.

-1
findbugs
29
hadoop-hdds in the patch failed.

-1
findbugs
17
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
24
hadoop-hdds in the patch failed.

-1
unit
23
hadoop-ozone in the patch failed.

+1
asflicense
29
The patch does not generate ASF License warnings.

2503

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1600

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux eac00ef72a7d 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 022fe5f

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/testReport/

Max. process+thread count
305 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozonefs U: hadoop-ozone/ozonefs

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1600/3/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thanks @bharatviswa504 for reporting the problem, and for reviewing and committing the fix.


Add minimum bounding methods

#1281
Property decorator was fitting here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 84.221%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
2087

Relevant Lines:
2478

💛  - Coveralls


Improve the warning to suggest network connection

Warn about the most probable when update failed
I got to look around 10 minutes having ca-certificate and a current time, but no internet...

Thanks.


Req: Export Missing option

This suggestion came from reddit and was described as a diff export.
Story: As a user, I want to send my friends a pak file containing only the files that fail to download.
Idea
Stan has the entire mod cached already. Stan wants to play a mod with his friends, and from Stan's perspective, everything works great. But Stan's friends complain that some models and other resources aren't loading and they get errors.
Stan uses TTS-Manager to export "only missing". TTS-Manager attempts to download all resources in the mod.json file, and compares them to Stan's local cache. Any files that completely fail to download or differ from Stan's cache are added to the export from Stan's cache. Any files that successfully download and match Stan's cache are ignored.
Instead of sending his friends a 150MB *.pak file, Stan instead sends a 15MB *.diffpak file, which is small enough to directly attach to an email. Stan's friends use TTS-Manager to unpack it.

So, I started on this last night. Fairly easy to code up (I've got it working in the CLI). but it seems that it is going to be functionally limited until I've done #33 from my testing so far.


Fix overriding theme with props

At the initial render styled-components was taking the theme from ThemeProvider even the component had an own theme prop.

Amazing, thanks so much!