PSM-393 Upgrade org.pitest:pitest-maven 1.4.9 -> 1.5.2

This PR contains the following updates:

Package
Update
Change

org.pitest:pitest-maven
minor
1.4.9 -> 1.5.2

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

Suggested commit message:
PSM-393 Upgrade pitest-maven-plugin 1.4.9 -> 1.5.2

See:
- https://github.com/hcoles/pitest/releases/tag/pitest-parent-1.4.10
- https://github.com/hcoles/pitest/releases/tag/pitest-parent-1.4.11
- https://github.com/hcoles/pitest/releases/tag/pitest-parent-1.5.0
- https://github.com/hcoles/pitest/releases/tag/pitest-parent-1.5.1
- https://github.com/hcoles/pitest/releases/tag/pitest-parent-1.5.2
- https://github.com/hcoles/pitest/compare/pitest-parent-1.4.9...pitest-parent-1.5.2


CASSANDRA-16052 CEP-7 Storage Attached Indexes (Phase 1)

This is now rebased to trunk as of 6cea0cd448d11dc633237ceb1f73f36c2eafb368

Current test baseline should roughly correspond to: https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=cep-7-sai-5-30-rebase

CI from the last rebase: https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=cep-7-sai-25-july-rebase


[FacebookBridge] Facebook integration tests

Pulled this out of the #1817 PR as it needs some further strategy discussion.

Ooh, interesting, I see @teromene was actually building something similar, as a separate application, a few years ago:
https://github.com/teromene/rss-bridge-validator/blob/master/test_datas.php
Though that's a separate application, displaying a frontend rather than integrating with the CI pipeline

Can't be doing network calls in unit tests. Maybe add a new folder integration_tests later. Could also just logic on local static html. We also have progress on automatic testing so this is less relevant. Also this would certainly trigger antibot reponse.


Different between .bag file size recorded by D435 and D435i model

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 18.04)

Kernel Version (Linux Only)
<IP_ADDRESS>

Platform
PC

SDK Version
2.24 }

Language
Cpp

Segment
{others }

Issue Description
I use the rs-record-playback Sample to record realsense stream into file.
For a 5 seconds length data, D435 save about 156MB.
But D435i save about 600MB.
My question is:

What is the different between stream channels of D435 and D435i.

How can i program the D435i so it will save the .bag file as same size as D435.
Using realsense-viewer, i can see that there's addition stream called motion-stream on D435i. I want D435 and D435i take the same amount of data. Is there any way i can turn this motion stream off programmingly on D435i.

I tried to turn off other channels except DEPTH and COLOR.
// Disable motion channel of D435i
		if ("Intel RealSense D435I" == std::string(it.second.get_info(RS2_CAMERA_INFO_NAME))) {
			std::cout << "Disable motion channel of D435i" << std::endl;
			cfg.disable_stream(RS2_STREAM_INFRARED);
			cfg.disable_stream(RS2_STREAM_FISHEYE);
			cfg.disable_stream(RS2_STREAM_GYRO);
			cfg.disable_stream(RS2_STREAM_ACCEL);
			cfg.disable_stream(RS2_STREAM_GPIO);
			cfg.disable_stream(RS2_STREAM_POSE);
			cfg.disable_stream(RS2_STREAM_CONFIDENCE);
		}

But no -luck, the D435i still have a very large .bag size comparing to D435.

If you are using the Viewer, you can enable compression under playback and record preferences in settings window.
ROS-bag compression saves up on size a bit, but introduces some amount of frame drops. For IMU streams at high frequency this could cause degradation of tracking, so we disabled compression by default for the 35i.

Hello @dorodnic
Thank you for your information.
So it mean that D435 turn the compression on by default and D435i turn the compression off by default.
That make sense.
I have to save of lot of depth, color () into disk so i need this feature.
Sorry i don't find any oftion inside realsense-viewer that could help me turn the compression on....
Is there any way that i can turn the compression on for D435i by programming or using preset ?
I look through preset files at :
D400 Series Visual Presets but couldn't find any related parameters.

#3089 shows the relevant UI.
Programmatically, it is possible, but a bit clunky. There is no easy way to control it via the pipeline. Let me know if you still need it, I'll try to guide you through this.

Hello  @dorodnic .
Thank you for your information. i found the button. And i'm able to turn the compression on using the realsense-viewer.
I still need to turn on/off the compression programmingly, please help.

The process would be:

Find the device you are using by creating a context and calling query_devices
Create recorder using this ctor by passing the output filename, device to be recorded, and compression flag.
Iterate through the sensors of the record device via query_sensors.
For each sensor, find the stream profiles you are interested in (say, Z16 640x480 @60 FPS)
Call sensor.open with profile / profiles you selected.
Create syncer object.
Call sensor.start on all sensors and pass syncer object as parameter to start.
Stream will be recorded. You can use syncer.wait_for_frames somewhat similar to pipeline.wait_for_frames, but please note that pipeline will always return frames from all streams, while the syncer can also provide "partial" framesets when full match could not be accomplished.

You can take a look at sensor control example to understand this process better.

hello @dorodnic
Thank you for your information.
Actually, it's totally different with the approach i'm using right now.
Is there any example that i can follow/
Currently, i'm following the approach used in record-playback .
Mainly using rs2::pipeline and rs2::config.
pipe_1->stop(); // Stop the pipeline with the default configuration

// Re Init the pipe: clear and release everything
pipe_1 = std::make_shared<rs2::pipeline>();

rs2::config cfg;
// re create the conf
cfg.enable_device(dev.get_info(RS2_CAMERA_INFO_SERIAL_NUMBER));
auto advanced_mode_dev = dev.as<rs400::advanced_mode>();
// Check if advanced-mode is enabled to pass the custom config
if (!advanced_mode_dev.is_enabled()) {
	// If not, enable advanced-mode
	advanced_mode_dev.toggle_advanced_mode(true);
	std::cout << "Advanced mode enabled. " << std::endl;
} else {
	std::cout << "Advanced mode is already enabled. " << std::endl;
}

// Select the custom configuration file
std::cout << "Sensor will load configuration from" << preset << std::endl;
std::ifstream input(preset);
std::string preset_json((std::istreambuf_iterator<char>(input)), std::istreambuf_iterator<char>());
advanced_mode_dev.load_json(preset_json);
input.close();

// Reduce size of stream
std::cout << "Reduce the resolution of sensor using conf at : " << conf << std::endl;
boost::property_tree::ptree pt;
boost::property_tree::ini_parser::read_ini(conf, pt);
cfg.enable_stream(RS2_STREAM_COLOR, std::atoi(pt.get<std::string>("Color.width").c_str()),
				std::atoi(pt.get<std::string>("Color.height").c_str()), RS2_FORMAT_BGR8,
				std::atoi(pt.get<std::string>("Color.fps").c_str()));
cfg.enable_stream(RS2_STREAM_DEPTH, std::atoi(pt.get<std::string>("Depth.width").c_str()),
				std::atoi(pt.get<std::string>("Depth.height").c_str()), RS2_FORMAT_Z16,
				std::atoi(pt.get<std::string>("Depth.fps").c_str()));

// Alow recording into file
cfg.enable_record_to_file(files[cnt]);
// Start pipeline with new configuration
pipe_1->start(conf);

Is there any option that i can put in these line to turn compression on ?
cfg.enable_record_to_file(files[cnt]);

Sorry for the long post.

I understand, this is what I meant by clunky. Unfortunately, there is no overload of cfg.enable_record_to_file(files[cnt]); that controls the compression.
Alternatively, there is always an option to go into the code and hard-code desired value, but it has its own drawbacks.

Hello @dorodnic .
Thank you for your information.
i feel that Hard-coding the code or following your guide may lead to a technique risk.
I decide to purchase a new D435 to replace the D435i.
Thank you for your time and effort.
That actually help me a lot.


Azure Monitor OpenTelemetry Commitments (July - December 2021)

This tracks the work for OpenTelemetry

can we use epic in the Java repo that I created before? https://github.com/Azure/azure-sdk-for-java/issues/23128

Yes.


New players cannot join the lobby

Bug Report
Hi! Not sure this is a bug or a config, but whenever we play a match (e.g. with 5~6 people) and someone else tries to join the lobby, he receive the message ", Guild member (undefined isn't in the lobby."
Also, we noticed that this issue may also happen if some minutes (didn't checked how many) have passed after the start of the lobby (I think it was around 10m)
Steps to Reproduce
1- Play a game with fewer people
2- once the match is over, ask to someone else join the lobby
Expected behavior
Let anyone join the lobby if the status is "intermission"

From your description, I think you've encountered a bug I found the other day.
When someone joins the voice channel during a lobby, they should be automatically added as a spectator. (And listed at the bottom of the info post.) But that doesn't always happen for some reason.
I'm going to fix that as soon as I can, but there's a workaround: if someone doesn't show up as a spectator, have them switch to a different voice channel for a couple seconds and then switch back. That gives the bot a chance to see them again.

Oh, thanks for the tip. Gonna try that next time we play.

I have the same problem, if the game is running, new ppl can join the vocal but the bot don't but them in spectator ... So to fix that I stop and restart a lobby.

This issue is resolved in version 2.3.0


Feature Request: Show system time.

Title… I think it’d be pretty handy to show the time, especially when you want to have a quick game session, but have places to be at a certain time.

like this format? DD/MM/YY : HH/SS/MM ? if not then what type of time are you refering to

Something like that would be cool. Not sure how much work this it, but maybe 24 and 12 hour could be configured in the yaml, or maybe use the format already set in PS3 settings? When the idea came to mind, I was thinking “HH:MM (am/pm)” maybe above or to one side of the FPS display. Either way, the time being there regardless of position or format would certainly be useful :)

Thank you 😎


[LI-HOTFIX] Move info-level consumer logs on seeking to an offset to debug-level. (#89)

TICKET =
LI_DESCRIPTION =
Info-level logs cause a line to be logged for each partition seek. This leads to an excessive number of logs in Kafka consumer users with frequent seek operations.
Pre-2.3 versions of Kafka use debug-level logs for seek operations. This patch brings this behavior back.
EXIT_CRITERIA = TICKET [KAFKA-8883]

Hi @PrachiKhobragade , when squash/merging, can you remove the period in the title (.... debug-level.).  This is the convention of git commit message.


/xmlui/shibboleth-login does not work with http proxy but works with ajp proxy

Works
132   # add path your repository path that will be protected by shibboleth
133   location /repository/xmlui/shibboleth-login {
134     shib_request /shibauthorizer;
135     ajp_keep_conn on;
136     ajp_pass tomcat8;

Does not work
132   # add path your repository path that will be protected by shibboleth
133   location /repository/xmlui/shibboleth-login {
134     shib_request /shibauthorizer;
135     include proxy_params;
136     proxy_pass http://<IP_ADDRESS>:8089/repository/xmlui/shibboleth-login;

i'm guessing all the parameters/headers get prefixed with HTTP_ in the
later case
2015-10-01 16:42 GMT+02:00 Jozef Misutka<EMAIL_ADDRESS>
Works
132   # add path your repository path that will be protected by shibboleth
133   location /repository/xmlui/shibboleth-login {
134     shib_request /shibauthorizer;
135     ajp_keep_conn on;
136     ajp_pass tomcat8;
Does not work
132   # add path your repository path that will be protected by shibboleth
133   location /repository/xmlui/shibboleth-login {
134     shib_request /shibauthorizer;
135     include proxy_params;
136     proxy_pass http://<IP_ADDRESS>:8089/repository/xmlui/shibboleth-login;
—
Reply to this email directly or view it on GitHub
https://github.com/ufal/lindat-dspace/issues/391.


Wrong or missing consumption data? 🤔

Not sure if I'm missing something here, but the info about my meter provided by the S-Miles Enduser app doesn't match the output of hoymiles-wifi:
App vs ha-hoymiles-wifi:

hoymiles-wifi output:
$ hoymiles-wifi --host <IP_ADDRESS> get-real-data-new --as-json
{
  "deviceSerialNumber": "******",
  "timestamp":<PHONE_NUMBER>,
  "activePower": 4,
  "firmwareVersion": 1,
  "meterData": [
    {
      "deviceType": 1,
      "serialNumber": "******",
      "phaseTotalPower": 261,
      "phaseAPower": 261,
      "powerFactorTotal": 983,
      "energyTotalPower": 1959,
      "energyPhaseA": 1959,
      "energyTotalConsumed": 1972,
      "energyPhaseAConsumed": 1972,
      "faultCode": 1,
      "voltagePhaseA": 23170,
      "currentPhaseA": 1149,
      "powerFactorPhaseA": 983
    }
  ],
...

Can you update to main branch? There are some conversion erros in the 0.3.2 release, since I don't have a meter and had to guess the units. main branch (or next release) should adresses it.

If I had to guess, I'd say things got worse:

  "meterData": [
    {
      "deviceType": 1,
      "serialNumber": "*****",
      "phaseTotalPower": 72,
      "phaseAPower": 72,
      "powerFactorTotal": 846,
      "energyTotalPower": 2200,
      "energyPhaseA": 2200,
      "energyTotalConsumed": 1972,
      "energyPhaseAConsumed": 1972,
      "faultCode": 1,
      "voltagePhaseA": 22980,
      "currentPhaseA": 385,
      "powerFactorPhaseA": 846
    }
  ],

Huh. That's weird. Is there anything in the logs? Seems like the data cannot be read any more from the meter.

I thinks the consumption is calculated via inverter power and meter power. No direct value from meter.

I'm back 😅 Now everything looks good, so maybe it was an exceptional issue, but I think using the main branch was key for this.
I think I understand now how to get the consumption via the total generated power (by my 3 inverters) - the meter power (divided by the meter power factor?) so I created a small dashboard with all my panels and the rest of the info provided by the S-Miles app (probably need to fix a few issues though):

Generated power, consumed, injected to the grid, bought from the grid, then the solar panels, and then some graphs (with some crazy numbers as you can see, still don't know why).
Looking forward to the next version of ha-hoymiles-wifi! Thank you again 🙇♂


Support channel image

RSS and Atom both support setting a channel image, with the three nodes url, title and link. See https://cyber.harvard.edu/rss/rss.html#ltimagegtSubelementOfLtchannelgt for the RSS side, and https://tools.ietf.org/html/rfc4287#section-4.2.8 for the Atom side (I think that's the best fit, but it seems to support just an URL). Maybe feedparser could be extended to carry the channel image around?

One idea is to easily support access to the full underlying structure with all its additions (in a uniform "parsed" way e.g. xml or json converted to a nested ruby hash, for example.

feedjira has a class for rss channel images in https://github.com/feedjira/feedjira/blob/master/lib/feedjira/parser/rss_image.rb/. I think it has no equivalents for atom and jsonfeed.
Having full access to the origin structure sounds very useful. Something like https://stackoverflow.com/a/10144623/2508518 could work, though I assume nokogiri is not an ideal requirement for this gem.

Thanks. Good points. Soon or later the "old" standard rss library has to get replaced with something better. Why not nokogiri?  I'm all for it. The only downside as far as I can tell is the "hard-to-install" part because it requires a c-extension.  The idea of the nested hash is that it is uniform, that is, the same for xml and json - thus, I'm not sure if the nokogiri format is a 100% fit here.


Not working behind enterprise proxy

Didn't had this problem with versions 1.4.X but starting with version 1.5.0-beta.X (and now the current beta version 2.0 too) the problem appeared.
At work, like many people, I have to use a proxy to connect to the Internet. When I run the app it just hangs on the white window with the blue loader, going nowhere.
This is the console log when I run it from there:
`
ERROR [2016-08-30 13:30:49.933]   messengerfordesktop:browser/managers/auto-update-manager: Error: connect ECONNREFUSED <IP_ADDRESS>:443
at Object.exports._errnoException (util.js:1008:11)
at exports._exceptionWithHostPort (util.js:1031:20)
at TCPConnectWrap.afterConnect as oncomplete
[1570:0830/143105:FATAL:url_request_context.cc(104)] Check failed: false. Leaked 1 URLRequest(s). First URL: http://pcprt4prxscr.telecom.pt/proxyPTP.pac.
#0 0x000001e095ae
#1 0x000001e1f1bb
#2 0x0000009646bb
#3 0x0000009644f6
#4 0x0000009646e9
#5 0x0000034da2ad brightray::URLRequestContextGetter::~URLRequestContextGetter()
#6 0x0000034da409 brightray::URLRequestContextGetter::~URLRequestContextGetter()
#7 0x0000009650d7
#8 0x000003409a11 _ZN4base8internal9BindStateINS0_15RunnableAdapterIPFv13scoped_refptrIN9brightray23URLRequestContextGetterEEEEES7_JRS6_EE7DestroyEPNS0_13BindStateBaseE
#9 0x000001e34e5d
#10 0x000001e25c71
#11 0x000001dfe9d9
#12 0x000001e3e03e
#13 0x000001e24c7a
#14 0x00000266c4d6
#15 0x00000266c6de
#16 0x000001e5d708
#17 0x000001e59c93
#18 0x7f86234516fa start_thread
#19 0x7f861cedfb5d clone
`
And this is the log when I use the option to restart in debug mode and then open the log:
http://pastebin.com/v4ThQD77
I think it's not using the PAC file I have defined as system-wide proxy configuration. As an example, Ghetto Skype (which uses Electron) sets the proxy when it starts (don't know what they're doing behind the scenes, it's just a message that appears when I run it) and it's working flawlessly.

We will take a look at that. Thanks!
@Aluxian

Is there any way to ignore system-wide proxy configuration? I need to use a PAC file to access my enterprise proxy and I still can't connect using version 2 due to the same error but with other apps I can use proxychains to bypass the proxy (p.e., I use it with Corebird). When I try Messenger-for-Desktop with proxychains it hangs and when I kill the process this is the message (PAC URL edited):
ERROR [2017-01-19 15:11:19.917]   messengerfordesktop:browser/managers/auto-update-manager: Error: connect ECONNREFUSED <IP_ADDRESS>:443
    at Object.exports._errnoException (util.js:1026:11)
    at exports._exceptionWithHostPort (util.js:1049:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)
^C[7721:0119/151125:FATAL:url_request_context.cc(108)] Check failed: false. Leaked 1 URLRequest(s). First URL: http://[URL]/proxy.pac.
#0 0x000001e5801e <unknown>
#1 0x000001e6dd1b <unknown>
#2 0x0000009814eb <unknown>
#3 0x000000981526 <unknown>
#4 0x0000035c364d brightray::URLRequestContextGetter::~URLRequestContextGetter()
#5 0x0000035c37a9 brightray::URLRequestContextGetter::~URLRequestContextGetter()
#6 0x000000981fb7 <unknown>
#7 0x0000034e0391 _ZN4base8internal9BindStateINS0_15RunnableAdapterIPFv13scoped_refptrIN9brightray23URLRequestContextGetterEEEEEJRS6_EE7DestroyEPNS0_13BindStateBaseE
#8 0x000001e83bfd <unknown>
#9 0x000001e74a01 <unknown>
#10 0x000001e4e129 <unknown>
#11 0x000001e8cede <unknown>
#12 0x000001eabeca <unknown>
#13 0x0000027078f6 <unknown>
#14 0x000002707afe <unknown>
#15 0x000001eabf8e <unknown>
#16 0x000001ea8513 <unknown>
#17 0x7f82fd7a56ba start_thread
#18 0x7f82f723382d clone

[1]    7721 abort      messengerfordesktop

If I could disable Messenger-for-Desktop from going to check system-wide proxy settings, maybe I could get it through.
Until then, I'll have to keep using 1.4 version

Hey,
MFD works like Chromium. So how would you make Chrome/Chromium bypass the proxy?

On 19 Jan 2017, at 15:18, Valter Vicente<EMAIL_ADDRESS>wrote:
Is there any way to ignore system-wide proxy configuration? I need to use a PAC file to access my enterprise proxy and I still can't connect using version 2 due to the same error but with other apps I can use proxychains to bypass the proxy (p.e., I use it with Corebird). When I try Messenger-for-Desktop with proxychains it hangs and when I kill the process this is the message (PAC URL edited):
ERROR [2017-01-19 15:11:19.917]   messengerfordesktop:browser/managers/auto-update-manager: Error: connect ECONNREFUSED <IP_ADDRESS>:443
at Object.exports._errnoException (util.js:1026:11)
at exports._exceptionWithHostPort (util.js:1049:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)
^C[7721:0119/151125:FATAL:url_request_context.cc(108)] Check failed: false. Leaked 1 URLRequest(s). First URL: http://[URL]/proxy.pac.
#0 0x000001e5801e
#1 0x000001e6dd1b
#2 0x0000009814eb
#3 0x000000981526
#4 0x0000035c364d brightray::URLRequestContextGetter::~URLRequestContextGetter()
#5 0x0000035c37a9 brightray::URLRequestContextGetter::~URLRequestContextGetter()
#6 0x000000981fb7
#7 0x0000034e0391 _ZN4base8internal9BindStateINS0_15RunnableAdapterIPFv13scoped_refptrIN9brightray23URLRequestContextGetterEEEEEJRS6_EE7DestroyEPNS0_13BindStateBaseE
#8 0x000001e83bfd
#9 0x000001e74a01
#10 0x000001e4e129
#11 0x000001e8cede
#12 0x000001eabeca
#13 0x0000027078f6
#14 0x000002707afe
#15 0x000001eabf8e
#16 0x000001ea8513
#17 0x7f82fd7a56ba start_thread
#18 0x7f82f723382d clone
[1]    7721 abort      messengerfordesktop
If I could disable Messenger-for-Desktop from going to check system-wide proxy settings, maybe I could get it through.
Until then, I'll have to keep using 1.4 version
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Aluxian/Messenger-for-Desktop/issues/536#issuecomment-273803223, or mute the thread https://github.com/notifications/unsubscribe-auth/ABWmduUcTn4yKZaReKP6oVwYli7HrzDqks5rT37JgaJpZM4Jwij8.

Well, maybe not using proxychains since I can't use it with Chromium too, but installing a proxy extension in Chromium (like FoxyProxy) I can easily define my SOCKS proxy and navigate using it. Just an example.
But as I said in the first post, I use Ghetto Skype (which is developed with Electron) and it reads the PAC file from the system-wide settings too and run it flawlessly, so they must be doing something else. Note that I can open messenger.com and web.skype.com within the browser without any trouble (without using my SOCKS proxy).

Just checked out and I wasn't remembering it, but I'm using MFD v1.5.0-beta.1 using proxychains.
Some shared images/videos in the chat were blocked due to coming from Facebook (which is blocked, messenger.com isn't) so I started using MFD with proxychains and it works. So, maybe something with Electron?

Sorry, I'm confused now as to what works and what doesn't. MFD v2+ is built on Electron.

MFD v1.5.0-beta.1: I think it is build using NWJS and I can use it behind the enterprise proxy for normal chatting (I just use it with proxychains, without any problem, because that way I can see everything in the chat - videos/images from FB, videos from Youtube,...)
MFD v2+: I can't use it, even for normal chatting, because it hangs due to the PAC file I have applied system-wide. Ghetto Skype, which is built using Electron too, just works flawlessly and reads the system-wide proxy settings (therefore, handles the PAC file correctly).

Alright! I'll see what I can do.


Sema: Fix type mixup with unbound method references [4.0]

Description: Fixes a crash that's possible with a construct that's mostly useless, but beginners might mistakenly write it expecting it to work.

Scope of the issue: This was reported by a customer while testing a development toolchain trying to reproduce an unrelated issue.

Risk: Low.

Reviewed by: @rudkx

Radar: rdar://problem/34048597

@rudkx Can you review for 4.0?

@swift-ci Please test


TestStore.send not asserting properly

Description
I'm running TCA 0.42.0. I'm trying to write tests for my reducer. To make sure things are functioning properly I'm trying to intentionally write a failing test. I followed the examples in the documentation and here is my minimum reproducing example
import ComposableArchitecture
import Foundation
import XCTest

@testable import AppSource

@MainActor
class Test: XCTestCase {
    func test() async {
        let store = ComposableArchitecture.TestStore(
            initialState: PostViewReducer.State(),
            reducer: PostViewReducer()
        )

        print(store.state)
        await store.send(.loadCommentsPage) {
            $0.shouldLoadCommentsPage = false
        }
        print(store.state)
    }
}

And here are the logs from running the test
Test Suite 'Selected tests' started at 2022-10-17 02:20:46.431
Test Suite 'test_unit.xctest' started at 2022-10-17 02:20:46.432
Test Suite 'Test' started at 2022-10-17 02:20:46.432
Test Case '-[AppTests.Test test]' started.
State(shouldLoadCommentsPage: false)
State(shouldLoadCommentsPage: true)
Test Case '-[AppTests.Test test]' passed (0.016 seconds).
Test Suite 'Test' passed at 2022-10-17 02:20:46.449.
	 Executed 1 test, with 0 failures (0 unexpected) in 0.016 (0.017) seconds
Test Suite 'test_unit.xctest' passed at 2022-10-17 02:20:46.450.
	 Executed 1 test, with 0 failures (0 unexpected) in 0.016 (0.017) seconds
Test Suite 'Selected tests' passed at 2022-10-17 02:20:46.450.
	 Executed 1 test, with 0 failures (0 unexpected) in 0.016 (0.019) seconds
Program ended with exit code: 0

Checklist

[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
I inserted the two log statements to confirm the state is updated correctly. Initially shouldLoadCommentsPage is false. I sent the loadCommentsPage action and afterwards it's true. However I'm passing $0.shouldLoadCommentsPage = false into with the closure that's passed to send. I expect this to make the test fail since shouldLoadCommentsPage is updated to true. However the test seems to finish without any problems.
Actual behavior
The test finishes without any errors.
Steps to reproduce
No response
The Composable Architecture version information
0.42.0
Destination operating system
ios 15
Xcode version information
XCode 14
Swift Compiler version information
swift-driver version: 1.62.8 Apple Swift version 5.7 (swiftlang-<IP_ADDRESS>.4 clang-14<IP_ADDRESS>)
Target: x86_64-apple-macosx12.0

It's hard to know what is going on without seeing some code. Can you share something that we can run locally to reproduce?
The only guess I have without seeing more code is that perhaps you are using a reference type for your state? Reference types have instance/identity equality and are not equal based on just the data they hold.

Hi @mattdornfeld, I'm going to move this to a discussion because I do not believe it is a bug in the library considering we have a ton of test coverage on this area of the library and have never witnessed this before. If you are still having trouble please feel free to share some code so that we can help diagnose the problem.


Remove avatar button

Can you provide some description?

https://github.com/aeternity/superhero-ui/pull/316


Editing class name does not work

Editing the name of properties works properly, but saving name updates for classes has no effect. The old name remains unchanged. Please fix, thanks.

Also, some old versions still remain in the vocabulary.


Complete thunderbird-newsreader-configuration.md

can we bundle the images referenced?

Not 100% sure how to do that. I'll google it and bundle them later today

you can include the files in the doc directory with your pull request

i.e. https://github.com/majestrate/nntpchan/blob/3983506fe3018023959fe9c4a80b6252c9c6b73e/doc/moderation.md

Should be bundled now


Suggestion - WZDX Selected Units of Measurement - allow both English and Metric for interoperability

Summary
WZDX currently appears to be built upon metric units - kph, km, etc.  However, in order for WZDX to be an international, interoperable standard, wouldn't it make more sense to simply allow data providers to specify their own units?  This would allow either English or metric units to be used, based on the location and application in question.
Motivation
Restricting WZDX to metric units seems limiting.  In the U.S., where WZDX is first being standardized, English units of measurement such as mph are standard, and so many agencies that may wish to use the data from the feed will be operating in English units.  For example, I imagine most DOTs would like to receive and share their data in miles and mph, not in kilometers per hour, which are not units they use.  That is only a minor conversion if it is a single value, but smart work zone systems and connected devices and vehicles may end up processing millions of lines of data just for a single device.  So, it seems cumbersome and strange that a provider would need to convert millions upon millions of lines of data from mph to kph, only to have the receiving agency need to convert it back once again.  And this also creates rounding errors switching back and forth.  This is just one example, but I can imagine many applications where the main producers and receivers of this data are both operating in English units, so it seems sensible to remain with them.
It seems that it would give the feed much greater flexibility and international interoperability, simply to have a field where units are specified.
Proposed Changes
Recommend that the specification allows either English or metric units of measurement.  And recommend adding a field in the feed where this is specified.  This will allow users to use the appropriate measurements for the area and application they are operating in.

No objection. this will allow each countries to work in their native format and will allow data exchanges across the 2 units.
For us as a data producer our road side equipment such as radar are defacto in KPH and we are used for conversion but I can understand some are not and do not want to manage such process.

FYI, this discussion has already happened, see #169 and #174.
The team following presentation to and input from subgroup members decided that WZDx choosing a single unit is the cleanest approach. Converting a between speed units for presentation purposes is not an issue. Machines do not care what unit they work with.
We will bring this issue up in one of the next two subgroup meetings for another round of discussion, but it is unlikely this will be changed. It is simpler to have the specification define the standard for unit. This is done by the TMDD specification and by data producers such as Ver-Mac and GM. They use KPH internally then convert to the desired unit of the end user.

@j-d-b Thanks for the reply.  Yes, I saw issue #169.  However, that discussion was with regard to the value of a  variable speed limit, which is a single value, not for the units of the entire feed, which I would consider a very different scope, as it affects all future data streams related to the feed, which will be numerous.
Respectfully, I can't agree that choosing a single unit, which is not the unit of the country WZDX is initiating from, is cleanest nor simplest.  The only thing it would eliminate is a simple one-line entry on the feed, where a user would specify their units, based on the local standard.  But what it creates is massive amounts of unnecessary data conversion and storage on the other end.  For example, on the smart work zone data feed, a DOT within the US will require data from smart work zone providers, the data for which, they will want in English units, since KPH is not applicable for their operations.  So the smart work zone provider will need to convert all data into metric, and feed it to the DOT, which will then have to convert it back again.  And when there are questions about any data provided in the feed, it will have to be analyzed in the kph it was transmitted in, while communicated in mph, since that is what everyone is actually using.  This seems inherently messy and complex to me, not clean.
Again, this is not significant when one is thinking on the scale of a single measurement.  But we are talking about big data here, where one set of devices will generate millions and millions of lines of data.
Understood that Ver-Mac and GM may use kph internally and convert to other units.  However, the idea is for this to be an international standard that can be used by all different agencies and data providers.  So it seems to me that more flexibility will provide more utility here.  My company provides many data feeds to DOTs within the US and they always require the data in English units, since that is what they operate on.  Why not allow for this?

@devorah-ql there are several downsides and non-trivial added complexity that come from adding the ability to specify units:

It is not straightforward where to specify the units;
We may have to add and maintain a variety of enumerated types to enumerate the options for units for all options that anyone wants;
Processing software has to check the units property and have conditional logic for handling each type of unit.

For a few examples of each, using the reduced_speed_limit concept as an example:
1. Where and how to specify units
One way is to add a property for specifying the unit next to each property that needs a unit. For example, with reduced_speed_limit we could have added reduced_speed_limit_units which is restricted to a new "SpeedUnits" enumerated type with some set of options including KPH and MPH (and more?). However, then we'd need a new property for every property that used speed units.
Another option, as you suggest, is to have the unit for speed specified at the feed-level, let's call it speed_unit for this example.
A first negative is that it isn't clear what properties the speed unit applies to. The specification documentation would have to specify that, which is hard to maintain and requires processing code to have these "rules" coded in it somehow so it can know to check the feed info for the unit when parsing certain properties elsewhere on objects in the feed. I think that is unclear coupling and poor design.
Also, if we're talking about humans parsing a feed, which is the only case I see your argument relevant because machines don't care what unit they are working in, you would see the value in the reduced_speed_limit property and then have to check a different object that isn't nearby (visually) to know what unit it is. It is also easier to forget the unit than if the property name says the unit, like it does with reduced_speed_limit_kph in WZDx v4.0.
There are variations on these options, but it's hard to get around the negatives.
2. Many enumerated types with boundless options
I'll use the "SpeedUnits" enumerated type as an example again: it would have to contain many options depending on what consumers/producers use (in addition to KPH and MPH) to avoid anyone having to convert the unit.
3. Processing software has to check the units property and have conditional logic for handling each type of unit.
Parsing reduced_speed_limit_kph from a WZDx feed is trivial because you know the unit from the property name/description and thus do not need any more information to know what to do with it. If the unit was specified anywhere else and there were multiple options, processing software would have to check multiple properties and have conditional logic that parses it differently depending on the unit. Again, this is more added complexity.

@j-d-b. Thank you for explaining the complexity and the trade-offs here.  That is helpful to understand.

@j-d-b.  Thanks for explaining the potential issues.  It is helpful to understand the details and understand the concerns about complexity.
I discussed this along with a few of my developers, and here are some thoughts:

It is not straightforward where to specify the units;

The developers think this should be pretty straightforward.  It would be standard that this type of information would get specified in the root node, and based on that would apply to all the children.  For example, it could be specified in the basic info of the WZDXfeed or the RoadRestrictionFeed, or the SWZDeviceFeed.  Basic info already has to be provided there, so units could be included as well.  And then based on this, those units would apply to all children.  The developers said this type of setup is common with JSON feeds, and not complicated to process.
And agreed, the specification document would have to detail what those units are.  But it will have to do that anyways when the system is running on metric.  This would just involve adding English units as well, which should not be too onerous.  As far as parsing, the system will have to do the same things whether metric, English etc.  It will still have to know that speed values are kph, while distance values are kilometers, etc.  So either way, the units of the field have to be documented, and then taken in by the processor.

Many enumerated types with boundless options
I'll use the "SpeedUnits" enumerated type as an example again: it would have to contain many options depending on what consumers/producers use (in addition to KPH and MPH) to avoid anyone having to convert the unit.

I can understand the hesitance to open up to boundless unit variation, and agree that there doesn't seem to be a compelling reason to do so.  It seems it would be quite reasonable to restrict the feed to Metric and English units, which covers much of the world.  I don't think that all minor edge cases need to be covered.  But that doesn't stop us from covering the major units of the U.S., which is where the feed is being developed, alongside metric, which also covers much of the world.

Processing software has to check the units property and have conditional logic for handling each type of unit.

In many places, the end-users will be using English units.  So this means that the processing software is already going to have to understand units and do conversions.  So, I can't say that seems any simpler than checking units and processing based on the ones specified.  I double-checked this with my developers and they confirmed that checking units and processing based on them is simple programmatically speaking.  Those who have the skill to process a JSON feed would presumably be able to process units as well.
In terms of the desire to specify units in general, agreed that machines don't care what unit they are working in.  But the data will be used by humans, who do indeed care what units they are functioning in.  English unit users want to be told their data in English and metric users want it in metric.  Also, ultimately, the data from the feed needs to be analyzed by humans, because of the Garbage In/Garbage Out issue.  If everyone is feeding data into the system, questions will have to come up - is this good data?  What is the meaning of the data?  Etc.  So, humans will always end up coming into the analysis at some point to ensure accuracy.
In the end data can be converted.  But IMO, it just seems more straightforward for English users to be able to send their data back and forth in the same format, instead of having to convert it back and forth and back again.  Then conversion can just be done by those who need it.

Why has speed units been standardized on KPH, but roadway distance markers are in miles (WorkZoneRoadEvent, beginning_milepost and ending_milepost)?
I don't see any issue with either fixing speed units to KPH or providing a root-level localization property, in terms of computational complexity - neither are meaningfully complex and both are not nothing (convert a million KPH values to MPH, or look up a million localization properties - it's six of one, half a dozen of the other). But having a specification that mixes localization classifications is confusing.
To complicate matters further, some countries (just one?) appear to use a mixture of measurement units. I believe the UK is mostly metric, but roadway distance and speed are still in miles. I don't know if that is exclusively colloquial or if it is official (which units do UK traffic engineers work in?).
Aside, the non-metric classification is typically called "Imperial", not "English".

@dxpack yes, the milepost property naming is an issue we have discussed though it looks like it never made it into an Issue. Are you able to make an issue for making milepost naming either not specific to a unit, such as "highway location marker", or consistent with the rest of the chosen WZDx units?
As for the argument for allowing a producer to specify a unit, I am personally against it for the reasons above, primarily because I don't see any benefit in it and it adds complexity (at least another property and enumerated type). We can discuss it in the next WZDx Spec Update Subgroup meeting with all the members to come to a conclusion.

Issue: #243 beginning_milepost / ending_milepost (WorkZoneRoadEvent / DetourRoadEvent): not internationally descriptive

Closing due to low priority and the proposed ability to specify a unit is a significant breaking change (we'd have to rename  properties) with no functional value.


fix: fix backtrafficpolic is applied to routes with the same prefix

What type of PR is this?

Using backendTrafficPolicies to patch route resources may lead to unexpected results.
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #2366

/retest


Add new feature getSelectionRange / hasSelectionRange

The problem
There is no method to check the selection range of text for an input text field.
The Details
Whould be cool to integrade a method SelenideElement.getSelectionRange and/or Condition.selectionRange(String selection) to selenide.
Tell us about your environment

Selenide Version: 4.12.2
Selenium Version: 3.13.0
OS Version: Windows 10

Code To Reproduce Issue [ Good To Have ]
Right now we check it like this:
private String getSelectionRange(SelenideElement element) {
	return executeJavaScript("return arguments[0].value.substring(arguments[0].selectionStart, arguments[0].selectionEnd);", element); //$NON-NLS-1$
}

Hi @mseele can you provide a little more info? is this for the length of entered text ('value') or the maximum length value on a given field?  I will create a PR when you clarify, thanks.

What is selectionRange exactly? Characters selected with a mouse (to copy to clipboard?) inside of any element?

It's the start and end positions of the current text selection in an  element.
Please see https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/setSelectionRange for more details.
It is, for example, usefull if you have an input field that selects the whole input on focus (by code) and you want to test this.

@mseele

If I understand correctly, your method getSelectionRange actually returns selected text (not start/end positions). Thus it should be named getSelectedText(). Am I right?
In Selenide style, we should add condition instead of just getter. Like this:

$("textarea#bio").shouldHave(selectedText("London"));
$("textarea#bio").shouldHave(text("birth place: London"));

given the following image, it would be returning the value for 'selected' (basically what has been selected / highlighted?

if so, do we think this is a worthwhile feature to implement?

@symonk you example is exactly what i meant.

@symonk yes, why not. But I remind that I still prefer adding condition instead of just getter:
$("textarea#bio").shouldHave(selectedText("London"));

@symonk Hi! How is your PR going?

pretty slow sorry @asolntsev I am experimenting with the idea here https://github.com/symonk/selenide/commit/addca46b59af1d2967ed8eba78f29c08aa7977dd, however I am changing jobs right now so I have a lot of stuff to work out and no time just yet to continue.

@symonk no problems! I can do this PR by myself. I just wanted to be sure that we don't do the same job twice.

@asolntsev Hello, I am settled into work now so im going to work on this, ok?

@symonk Sure, go on :)


Not Working on OSX Vim 7.3

I'm really excited to eventually get this plugin to work... However, I have put it into my ~/.vim/bundle directory and it does not seem to be activating when I read a file. In an attempt to fix this, I have appended a line to my .vimrc (autocmd BufRead * :IndentLinesEnable). However, obviously this is crashing as the plugin does not seem to be installed...
Error detected while processing BufRead Auto commands for "*":
E492: Not an editor command: :IndentLinesEnable

Ok, I just updated to MacVim and am using the included Vim binary (as opposed to the Apple provided one)... Now there are no errors, and the plugin appears to exist. However, it still is not working.


GitHub actions and apps that need to be implemented.

[ ]  Integrate markdownfmt
[ ] Exported functions shouldn't be merged without a proper example function - need bot for this.
[x] Remind bot that pings people that need to be reminded.
[ ]  Stale issue warning bot.
[ ]  Repo page and clone traffic logging.

/remind me to test this bot by pinging @allyourbasepair in 10 minutes.

/remind me about the thing in 2 minutes


VSL-131: Added view for assets on settings page

Description

Added view on settings page of the treasury with:

Buttons for adding vaults and treasuries
Tables for presenting vaults and treasuries - from the state
Changed vessel-assets to vessel-collections (which stores NFTs in the state)
Added vessel-vaults which store vaults in the state
Remove button opens the modal for removing the vault/collection
View on Flowscan will redirect to the contract address
Updated modals for adding vaults and collections

Demo / Test Result

No vaults, no collections added:

Modal for adding vault:

Modal for adding collection:

Three vaults, one collection added:

Remove vault modal:

Remove collection modal:

Just a heads up, all the work around button UI probably need to be refactored into using the new UI system once VSL-182 is merged, I'll work with you to make the update.

Just a heads up, all the work around button UI probably need to be refactored into using the new UI system once VSL-182 is merged, I'll work with you to make the update.

Related to this comment, I added one comment to VSL-182 to style the buttons that are already merged, just in case this PR gets stalled, in order not to block the tickets that are in prod review so they can be tested independently.
Buttons from this PR will be updated once VSL-182 is merged

Front-end feedback:

Remove shadow from token vaults and nft collection table.
Make sure dropdown and text field has the same height.
Add 1px border above buttons similar to the border under the modal header.


Fix shader type detection

Fixes https://github.com/godotengine/godot/issues/78482

The problem was that get_shader_type() was called too early, before the preprocessing step. This PR moves the check after the preprocessing and uses the preprocessed shader code to figure out the shader_type. This makes sure the shader compiler only sees valid shader code that has all preprocessor statements removed, so that get_shader_type() can correctly parse the code and figure out the type. Previously, any preprocessor statements before the shader_type xyz; would cause a silent parsing failure and the shader type would default to spatial.

Thanks!

Cherry-picked for 4.1.2.


apt-get update: retries and error handling

Sometimes, for whatever reasons, apt-get update fails. This might be caused by mirrors that are updated right in the moment when apt-get update was executed or due to network issues. Usually this later causes various obscure problems like "WARNING: The following packages cannot be authenticated!" and crash the chef run.
I suggest to implement some shell logic to retry apt-get update if it fails (retries: attribute, maybe 3?) in all resources that have the command 'apt-get update'`.
I'm also not sure if the ignorance of errors (ignore_failure true) is a good idea, but at least a retry would probably reduce errors a lot.
The Debian/Ubuntu autopkgtest maintainers had the same issue and implemented a very simple static solution: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/diff/?id=7f667754

I am sometimes living behind a (really not small) proxy service and I am getting quite often such sequences of failure as you can see below. When manually invoked for me it can take some 1 to >10 attempts to get all querys succeeding.
 Care should be taken to allow similar behaviour either by default or by special expressed desire. An option for changing (=increasing) the retry count value on the command line that applies to the any individual open for a location should be made availabel.
See here an expample what currently happens to me:
# apt update [...] Get:6 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [391 kB] Err:6 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages   Hash Sum mismatch [...] Get:10 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [114 kB] Fetched 562 kB in 3s (182 kB/s)           Reading package lists... Done E: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/by-hash/SHA256/6a4dfa61229a6e9d1e82f5fb3434c9b650bc856aca68add08343380e3fb48afe  Hash Sum mismatch E: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-i386/by-hash/SHA256/17dc81048807986276d6314abbacc968efe9da255679863b06667b5ffa60ffd8   E: Some index files failed to download. They have been ignored, or old ones used instead.

We've removed the apt_update and apt_repository resources from this cookbook as they were merged into core chef. I'm going to close this issue out now. If you think it's still valid against a new chef-client release please open it up against the chef/chef repo so we can work on it where the code now resides.

the resource change is not related, but the original bug seems to be "fixed" by setting "ignore_failure" to true in https://github.com/chef-cookbooks/apt/commit/24a68c0dbf96df3be4348e8b22693abde56cbd88 anyhow


Add pixi support and pixi-pack instruction

To easily export conda dependencies to Upkie, this PR introduce pixi-pack.

Add a pyproject.toml to turn ppo_balancer into a standard python package
Add pixi specific clause in pyproject.toml to manage conda dependencies with pixi
Add pack-to-upkie tasks to create an archive with all conda dependencies
Add instruction in the README.md

Just tested this on Michel Strogoff:

Previously conda_env.tar.gz: 3.3 GB :package: :package: :package: :package: :package: :package: :package: :package: :package: :package: :package:  :package:  :package:  :package:
Now environment.tar: 230 MB :package:

Thank you for this @jorisv! :+1:


[WIP] LAI VC Revamp

This PR separates the immutable and mutable components of the LAI interface. Now one view controller is responsible for fetching data, while the other is only responsible for displaying already-fetched data.
Incidentally, I upgraded CocoaPods to match the lock file.
Fixes https://github.com/artsy/auctions/issues/330

          2 Warnings

:warning:
PR is classed as Work in Progress

:warning:
Needs testing on a Phone if change is non-trivial

  Generated by :no_entry_sign: danger

This is superseded a bit by https://github.com/artsy/eigen/pull/2162 but I'm going to keep it open, at least for now.

Okay, feeling pretty good about this. Ready for review @orta, but as mentioned above please don't merge until after 3.2.0 is out (to give us enough time to beta this thoroughly before deploying). (Also no rush, you're still on vacay.)

Merged locally. See: https://github.com/artsy/eigen/pull/2244#issuecomment-290731330


Retain Campaign History for Joining to CRM Data

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
In some of the models such as the campaign_report, the CTEs are filtered for is_most_recent_record = True. This means that each campaign name reflects the most up-to-date name, which may not match the name on a lead, contact, etc from a CRM like Salesforce. This makes it more difficult to calculate metrics like Cost per X, where X is some event that takes place in the Sales funnel.
Is it possible to update models to not filter for the most recent record, so we can get a full history of campaign performance?
Describe alternatives you've considered
I've tried copy/pasting the code from this package into custom models to build reports that can relate spend to conversion events, but that seems duplicative. If we can do it all in this package, that would be much better =)
Are you interested in contributing this feature?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.

Anything else?
N/A

Hey @SamtheDeveloper91, thank you for your engagement with our Ads Reporting packages and recommending this feature expansion. Including the ability to view historical campaign metrics is an improvement that we've considered in the past and would definitely be open to exploring. That being said, we would like to be thoughtful about the implementation to ensure we can avoid issues that can arise such as extended run times, duplicity, customer confusion, etc. I don't believe the solution would be as simple as removing the filter since then our grouping for the campaign in our campaign_report output model would be sorted by every variety of our dimensions instead of just the most recent campaign.
In order to dive into this a little deeper, I was curious if you'd be open to joining our office hours to talk to our team more about your use case(s) and what changes you have already implemented? This would give us some more insight into how your thinking about implementing this feature and allow us to brainstorm a potential solution that would work for most of our customers.


Indexer-agent: remove fallback to hardcode default file

Remove ensureGlobalCostModel and reconcileCostModel from indexer agent as they clutter the agent without any real changes towards the cost models.
Simply use CLI for creating or updating global cost models
graph indexer cost set model global [path]/basic.agora

Nice, I like the goal of this PR, but the code changes should be much simpler.
Looking at the code changes though it seems there is other work mixed in with it? It seems to be based off the https://github.com/graphprotocol/indexer/pull/483 branch?

Nice, I like the goal of this PR, but the code changes should be much simpler.
Looking at the code changes though it seems there is other work mixed in with it? It seems to be based off the https://github.com/graphprotocol/indexer/pull/483 branch?

 I rebased this branch to main, shouldn't depend on the other PR anymore


Write out entity/attribute info

Depends on #3

For depth columns, note: https://github.com/padilla410/lake-temp-lstm-static-data-release/pull/15#discussion_r1082902908

I made pretty significant progress on this today. I thought I would need more input at this time, but I believe I just need one small thing:
@AndyMcAliley can you write out a brief description of the ealstm_group column and post it in a comment here? I renamed that from your metadata column, lstm_group. Just something short that says what the possible values are and what it means/how someone could use it. Here are two little examples:

driver_gcm_cell_no: Cell number mapping to a grid cell id for each NetCDF file stored in "meteorological_inputs_GCM.zip", which contains the appropriate GCM meteorological data used for modeling each lake.
model_preds_ealstm_nldas: TRUE or FALSE values saying whether or not the lake was modeled by the EA-LSTM model. All 62,966 lakes included in this study were modeled by EA-LSTM and this column only contains values of TRUE.

ealstm_group: Which partition the lake belongs to. Options are Training, Validation, Testing, or None. Lakes in the Training partition were used to optimize neural network parameters. Validation lakes were used to choose hyperparameters. Testing lakes were used to evaluate final model performance. Lakes in the None partition were not used for any of these purposes, likely because they lack sufficient temperature observations.

Mostly complete with #24


Reproducible builds: Automatically remap $CARGO_HOME and $PWD

As a followup of https://github.com/rust-lang/rust/issues/41555, I think $CARGO_HOME and $PWD (the location of the project) should be remapped to fixed values automatically.
I found both of those paths inside binaries and I have to add boilerplate to all of my reprotest scripts to normalize them.
The motivation behind this is that alice and bob can both download the same release of a rust project, cargo build --release it and end up with a 100% identical binary, given a sufficiently similar build environment (rustc version and system libraries).

Maybe we can do this only on release builds?

If we can solve the debug problem, yes we may be able to do it by default on release builds as well.

@alexcrichton debugging in rust depends on debug symbols, correct?
[profile.dev]
debug = true       # include debug information (debug symbols). Equivalent to
                   # `-C debuginfo=2` compiler flag.

couldn't we remap those paths if debug is set to false?

Perhaps, but I believe they still show up in panic paths

@alexcrichton Any additional colour on what could/would break wrt debuggers? I am somewhat surprised $PWD makes it into the binaries at all.

@mfarrugi debuggers use the paths in debuginfo (which don't show up in strings output) for setting breakpoints and showing code whiel you're stepping through code. Anything which references a registry crate has an absolute path and can be debugged by setting breakpoints on the file and such. Crates in the cwd, if referenced via an absolute path, are also loaded by the debugger and would break as $PWD/foo.rs doesn't actually exist

The question is what to map the paths to. In Debian we install source code into /usr/share/cargo/registry but other systems might be different. Ideally we'd map it to a virtual path like $CARGO_REGISTRY and put the logic of "where is $CARGO_REGISTRY" into the system debugger itself.

these also look blocking
https://github.com/rust-lang/rust/issues/40374
https://github.com/rust-lang/rust/issues/40552
https://github.com/rust-lang/rust/issues/75263

https://github.com/rust-lang/rust/issues/102299

@alexcrichton How can I make rust builds are reproducible? can you let me the procedure that you know or can u guide me?. The reproducible issue I faced is reported here https://github.com/rust-lang/rust/issues/102299

We also have rust-lang/rust#111540 which might help


Query Real Service Test data in daily report

This month we at Msft are beginning to collect logs from our CI pipeline, so we can do release-readiness analysis based on that synthetic traffic.  We have a daily report we are using to track some core metrics and we should be including this data set as a source for that report.

I have 2 PRs in ADO that updated the daily report query: one is to include all errors in 3 databases, not just the error table; the other is a time chart query for the real service test databases


Revert "Update classifiers.py"

Reverts matuszewski/python-classifiers#14

REVERIFY

REVERIFY

Jenkins job python-classifiers-project/nightly-job ended with SUCCESS. Build: http://sullust.ddns.net:33404/job/python-classifiers-project/job/nightly-job/2/

REVERIFY


lookup.index_table_from_tensor() emits an error in eager mode when invoked more than once.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): +
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): MacOS
TensorFlow installed from (source or binary): tf-nightly
TensorFlow version (use command below): 1.5.0-dev20171206
Python version: 3
Bazel version (if compiling from source): -
GCC/Compiler version (if compiling from source): -
CUDA/cuDNN version: -
GPU model and memory: -
Exact command to reproduce:

from tensorflow.python.ops import lookup_ops
import tensorflow.contrib.eager as tfe
tfe.enable_eager_execution()

inpt = ['1611', '1612', '1613', '1615', '1616', '1617', '1618', '1619', '1621']

a = lookup_ops.index_table_from_tensor(inpt, name='a')
b = lookup_ops.index_table_from_tensor(inpt, name='b')

Problem
When the eager execution is enabled, the following error occurs:
FailedPreconditionError: Table already initialized. [Op:InitializeTableV2] name: string_to_index/hash_table/string_to_index/hash_table//string_to_index/hash_table/table_init//

Source code / logs
Full trace:
https://pastebin.com/GsKBjyV6
Question
Is there a way to specify more than one lookup table (a shared_name or a special scope)?

Actually, exposing a shared_name var, here, and assigning explicitly a unique string solves the problem for the eager execution mode.
Solution:
from tensorflow.python.ops import lookup_ops
import tensorflow.contrib.eager as tfe
tfe.enable_eager_execution()

inpt = ['1611', '1612', '1613', '1615', '1616', '1617', '1618', '1619', '1621']

a = lookup_ops.index_table_from_tensor(inpt, shared_name='a')
b = lookup_ops.index_table_from_tensor(inpt, shared_name='b')

I do not know if a shared_name was intentionally abandoned, but I can submit a PR, assuming that adding a shared_name argument to lookup_ops is an acceptable workaround.

@josh11b any idea what that could be?

As it is now these functions are not really eager-compatible. When you set a shared_name they work by accident.
We should add a class-based version of them like we have been doing for other packages (like feature_column).

@alextp I couldn't find the feature_column with eager support code you referred to. Can you send a link?
Is a shared_name hack +/- stable?
It's just such a pure joy to debug big NLP models with eager, so I'd like to make at least a  somewhat proper support.
btw, are there any available public roadmap for eager compatibility?

The shared name hack will continue to work.
On Dec 11, 2017 01:16, "MtDersvan"<EMAIL_ADDRESS>wrote:

@alextp https://github.com/alextp I couldn't find the feature_column
with eager support code you referred to. Can you send a link?
Is a shared_name hack +/- stable?
It's just such a pure joy to debug big NLP models with eager, so I'd like
to make at least a somewhat proper support.
btw, are there any available public roadmap for eager compatibility?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/15212#issuecomment-350599205,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAATxZwPhfbZ5O54ixEPP6JiLrkVXarRks5s_IJYgaJpZM4Q7FAz
.


fix a bug that the local history will always be record into bob.

Solving a bug where the local history of different participants is incorrectly recorded on one party.

1010


Implement SSE _mm_load* instructions

This implements SSE instructions:

_mm_loadh_pi
_mm_loadl_pi
_mm_load_ss
_mm_load1_ps
_mm_load_ps1
_mm_load_ps
_mm_loadu_ps
_mm_loadr_ps

I also added some experimental doctests, but I can't get them to run. (That is, I can't get them to fail by adding assert!(false). They are being compiled, though)

Awesome, thanks!

Looks like the tests may be failing on i686?

Looks like it picks different instructions in 32-bit mode:
disassembly for stdsimd::x86::sse::_mm_loadh_pi:
	 0: push %ebp
	 1: mov %esp,%ebp
	 2: mov 0x8(%ebp),%eax
	 3: movsd (%eax),%xmm1        // 3&4 could be combined into
	 4: unpcklpd %xmm1,%xmm0  // movhps (%eax),%xmm0
	 5: pop %ebp
	 6: ret

disassembly for stdsimd::x86::sse::_mm_loadl_pi:
	 0: push %ebp
	 1: mov %esp,%ebp
	 2: mov 0x8(%ebp),%eax
	 3: movsd (%eax),%xmm1   // 3&4 could be written as
	 4: movsd %xmm1,%xmm0 // movlps (%eax),%xmm0
	 5: pop %ebp
	 6: ret

Not sure what to do about this. The implementation is based on the one from xmmintrin.h
We have some other problems with assert_instr being too strict / fragile. We can make it less strict, or we could have a test based on the result matching the C intrinsic. But that would require invoking a C compiler somewhere. Perhaps, we can have a separate C file reference_sse.c and then have a macro matches_c_body(<function_name>).

Hm maybe we could just relax it here for now? I'm not sure how to deal with this as I'm not sure why there's different codegen...

Thanks again!


LAMOST

Train on highest-SNR LAMOST spectra with APOGEE labels (the usual 3 + alpha enh.)
Test on the full 12,000 LAMOST set and compare to APOGEE labels
Take-one-out tests

first point - I would start with just first 3 labels and get that working with no bias at low SNR then move to 4 labels
second point: apply test step to the stars = (full set of 11000 stars) - (stars in training set).


ReDet code using latest version of MMDetection

I just want to ask, have you tried to implement ReDet in the latest version of MMDetection?

No plan yet.  Another repo: https://github.com/jbwang1997/OBBDetection/blob/master/configs/obb/roi_transformer implemented most operators for oriented bounding box, you may refer to it.


[BUG] WAM Account Picker works just once

Library name and version
Azure.Identity.BrokeredAuthentication 1.0.0-beta.3
Describe the bug
WAM Account picker fails to open up more than once.
When WAM was incorporated into our module, we expect to be able to sign in using WAM any number of times without fail. What we have come to realize is that WAM allows just one sign in per session meaning once the module has been loaded, the WAM account picker works just once and stops working after that
Expected behavior

Sign-In through WAM
Sign out
Sign-In through WAM
Sign out

Actual behavior

Sign-In through WAM
Sign out
Sign-In through WAM (doesn't work)

Reproduction Steps
https://github.com/microsoftgraph/msgraph-sdk-powershell/pull/1344

Connect-MgGraph -SignInUI Native (Sign in using WAM now works as expected).
Disconnect-MgGraph (Sign out of account)
Connect-MgGraph -SignInUI Native (Sign in again using WAM fails to open WAM account picker).

Environment
No response

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Identity:0.121299416,Service Bus:0.11613217,Event Hubs:0.06354465'

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Here is a link to the implementation line
https://github.com/microsoftgraph/msgraph-sdk-powershell/blob/eb0f42e4f01aecece5abe75b5129936c094c7e24/src/Authentication/Authentication.Core/Utilities/AuthenticationHelpers.cs#L109


[Fix] Returning the measurements to Qadence

Moving computation of expectation value from samples from qadence-protocols to qadence
Computing expectation values from samples and refactoring tomography functions

@gvelikova what is this MR about?

@dominikandreasseitz Qadence-protocols should contain only error mitigation protocols, while measurement protocols should stay in Qadence, so this is why the moving happens. This is related to @rajaiitp on readout mitigation methods.

Computing expectation values of observable from state vector/samples has nothing to do with measurements honestly.
The measurements have already been made and the circuit is no longer of interest to us, just need to do some proper parity based addition, but most of the required functions are present in the tomography.py which I am moving to utils.py soon

I think what @dominikandreasseitz suggested is that you open an issue and add a description. I makes reviewing easier and contribution more tractable.

Computing expectation values of observable from state vector/samples has nothing to do with measurements honestly. The measurements have already been made and the circuit is no longer of interest to us, just need to do some proper parity based addition, but most of the required functions are present in the tomography.py which I am moving to utils.py soon

@rajaiitp @gvelikova If I understand correctly, you provide a sample and estimate an expectation value using common functionality present in tomography (now utils). I have just a simple question about it: would it make sense to only retain the tomography protocol and pass the sample through options ? This would simplify the whole handling of the protocol I think. Ie. check if samples is present in the options dict and execute the appropriate expectation estimation.

Computing expectation values of observable from state vector/samples has nothing to do with measurements honestly. The measurements have already been made and the circuit is no longer of interest to us, just need to do some proper parity based addition, but most of the required functions are present in the tomography.py which I am moving to utils.py soon

@rajaiitp @gvelikova If I understand correctly, you provide a sample and estimate an expectation value using common functionality present in tomography (now utils). I have just a simple question about it: would it make sense to only retain the tomography protocol and pass the sample through options ? This would simplify the whole handling of the protocol I think. Ie. check if samples is present in the options dict and execute the appropriate expectation estimation.

Tomography has to do with circuits/models, backend used for simulation, read out noise. If we force this function call thru tomography options we would be required to create dummy circuits that dont have anything to do with its evaluation. I would prefer we keeping it like this, as an independent function call, but I'm not sure if you want to keep it here or move it elsewhere in the package.

@rajaiitp lets wait what roland says on monday


Date with time picker

Feature request: (ie: not an Issue)
Any thoughts of merging Date and Time picker line, similar to: http://jquense.github.io/react-widgets/docs/#/datetime-picker
Currently, it requires math to merge both input fields to produce a single timestamp.

I am missing this component too...

Maybe not exactly what you seek, but we have a datetime picker that is based on the date and time picker in toolbox
https://github.com/beanloop/react-toolbox-components/blob/master/docs/datetime-picker.md
https://github.com/beanloop/react-toolbox-components/blob/master/src/datetime-picker.tsx
Hopefully it's helpfull

I think this is out of the spec. Note that the implementation is flexible and it's done in multiple separated files. You can create your own by importing small components from react-toolbox :)


2.0.0 enum converts to string

Controller
[Route("test")]
[ApiController]
[Authorize]
public class TestController : ControllerBase
{
    [HttpGet]
    [ProducesResponseType(typeof(ProductListResponse), (int)HttpStatusCode.OK)]
    public async Task<ProductListResponse> Products([FromQuery(Name = "sort_type")] ProductSortType? sortType)
    {
        return new ProductListResponse();
    }
}

Result where ProductSortType enum becomes string
 public partial interface ITestApi
 {
     [Get("/test")]
     Task<ProductListResponse> Products([AliasAs("sort_type")] string sorttype = null);
 }

It should be something related to .net8

Ok. Error happened only when it comes from model. I tried debug to see where error is but after 1h left. How do you do?
Would be great to have test. Maybe one day will come back
Enum val is always serialized as string
public enum SomeEnum
{
    Value1,
    Value2,
    Value3
}

public class SomeQueryModel
{
    public SomeEnum EnumVal { get; set; }
    public string Param1 { get; set; }
    public Guid? Param2 { get; set; }
    public int Param3 { get; set; }
}

@valentasm1
I have published an updated version:
https://www.nuget.org/packages/GenerateAspNetCoreClient.Refit/2.1.0
Hopefully everything works fine now!

It works. Thank you.


docs: (IAC-1208) Additional Data Transfer Doc Changes

Changes
Additional changes to the experimental Data Transfer doc after some feedback

Also removed a left over section that was recommended to be removed in the feedback notes.


NoMethodError: undefined method `read_timeout=' for #TCPSocket:(closed)

Every time I try to close the connection (after an error state) I get this error.
Here is example code that reproduces the above error:
        ftps = DoubleBagFTPS.new
        begin
          ftps.debug_mode = true
          ftps.passive = true
          ftps.open_timeout = 1.0
          ftps.ftps_mode = DoubleBagFTPS::EXPLICIT
          ftps.connect 'ftp.secureftp-test.com'
          ftps.login 'test', 'test'
        rescue Net::FTPPermError => e
          puts e.class
          puts e.message
        rescue StandardError => e
          puts e.class
          puts e.message
        ensure
          ftps.close unless ftps.closed?
        end

This seems to be happening in the close method of Net::FTP:
NoMethodError: undefined method `read_timeout=' for #<TCPSocket:(closed)>
	from ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/net/ftp.rb:111:in `read_timeout='
	from ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/net/ftp.rb:960:in `ensure in close'
	from ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/net/ftp.rb:960:in `close'

I can't determine what DoubleBagFTPS is doing to cause this, but it doesn't happen if I switch to Net::FTP.

Ok, here's some more information. I get this when an error occurs during login. In this case a "certificate verify failed" error:
connect: ftp.secureftp-test.com, 21
get: 220 Microsoft FTP Service
put: AUTH TLS
get: 234 AUTH command ok. Expecting TLS Negotiation.
OpenSSL::SSL::SSLError
SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

If I add the following before the call to close then it works.
          ftps.send :decorate_socket, ftps.instance_variable_get(:@sock)

The issue is that the failure happens when the socket attempts to connect. But decorate isn't called until after the socket is connected. For some reason, #closed? returns false for a connection that has never opened.

I'm getting the same thing.

I started to look at this a few months ago.  Unfortunately, the public ftp
site upon which this gem depends for it's tests is no more.  If I get a
chance I'll see if my ftpd or some other ruby ftp lib. can be used to
create a new test suite.  Ftpd uses this gem in its own tests, but not at
runtime, so it ought to be ok, mostly, even if it is a little bit "close"
of a relationship between the two. Either that, or we get lucky and find
another public ftp server that has ssl support.
On Sep 26, 2015 18:05, "Jamon Holmgren"<EMAIL_ADDRESS>wrote:

I'm getting the same thing.
—
Reply to this email directly or view it on GitHub
https://github.com/bnix/double-bag-ftps/issues/9#issuecomment-143508824.

Thanks @wconrad! No rush.


Minimize number of HTTP requests made by Less

I started towards hacking on less.js tonight to see if I could get it to not load duplicates.
In the process I stumbled upon these few lines: https://github.com/less/less.js/blob/master/dist/less.js#L460-L468
Which lead me to this documentation: http://lesscss.org/usage/#using-less-in-the-browser-usefilecache
I set the useFileCache option to true here (actually, the equivalent in my version of Steal): https://github.com/stealjs/steal-less/blob/master/less.js#L24
Doing so reduced the number of HTTP request made by the less.js library from 171 to 10.
The app seemed to continue to work just fine.
From what I understand, setting this option by default will address https://github.com/stealjs/steal-less/issues/1.

So it prevents re-fetching files that have already loaded? That makes sense. In reality the browser cache should handle duplicates anyways, but devs often turn the browser cache off. Sounds like a good fix to me!

If you could make a PR for this it would be a great enhancement to get in.

I can do that.
I've been using a branched version of my app with useFileCache set to true and I haven't noticed any issues.

This is now being done: https://github.com/stealjs/steal-less/blob/master/less.js#L26


Widget support for android

A widget support would be great addition for this almost perfect app.

#8


Improve Treament Summary Report

Proposed Changes

Fixes #8060

tested..however the IP number in patient dashboard is mentioned as OP number in the treatment summary

@samholics fixed the above issue, can you please check again
cc: @nihal467

tested, working fine.  issue resolved. @nihal467 @khavinshankar

LGTM


Added a new section "Project Setup" in the readme file based on issue #262

Added a new section "Project Setup" in the readme file based on issue #262. It will help the people to set up their preferred projects without any confusion.

Hello @phyleria I have made some necessary changes. Would you please check?

Hello @phyleria what should be the name of that section? Project Setup?

Yes, project setup

Hello @phyleria Please have a look now.

Hello @phyleria I have made some more changes. Please check them.

Hello @phyleria done. Would you please label it as "hacktoberfest" and then merge it?


v0.0.4

Coverage remained the same when pulling 89f2659170dab9e7b3c0cb68b8ba40333cef697d on develop into 45f2f53ce0cb326bc79938a228121aa1710308e6 on master.


Add ability to opt out of added documenter CSS

Fixes #93
@rikhuijzer The added test only hits one of the two places where _wrap_documenter_output is called, but I'm not certain how to hit the other place.

Thanks! Great implementation :+1:


update index files

index.php and admin/index.php will be copied during installation process. If those file changes, they need to be changed for the setup process too.

done.


[Feature]: Document how to upgrade to this CLI from the ruby CLI

What area(s) will this request affect?
Extension
What type of change do you want to see?
New feature
Overview
Please document the steps necessary to switch to this version of the CLI from the Ruby version.
Motivation
I see that the ruby CLI is deprecated and it points to this tool, but there are no clear steps for how to upgrade to this tool. The command set is different and it seems like configuration is handled differently. It would be nice to have some documentation about how to make the switch.

Hi! Sorry for the late response.
You can find a migration guide here: https://shopify.dev/docs/apps/build/cli-for-apps/migrate-to-latest-cli
Hope it helps.


Disable PIE for go and balena

This resolves the high memory usage issue on 32bit resinOS on pi3.
This PR will need to be backported to 2.15.y
Impacts https://github.com/resin-os/meta-resin/issues/1168

Contributor checklist

[x] Changes have been tested
[x] Change-type present on at least one commit
[x] Signed-off-by is present
[x] The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

When submitting a review, please pick:

'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

@resin-jenkins retest this please

@resin-ci retest

The build actually succeeded in https://jenkins.dev.resin.io/job/meta-resin/2432/ . There is an issue with jenkins picking the right branch.


Batch workflow. Add RF and VQSR

Refactor the Joint Calling Hail-Batch workflow. The main script is sitting in workflows/batch_workflow.py .

Script is designed to work with the CPG bucket structure and the following main bucket structure:

# main (or test):
gvcf
  batch0
    sample1.g.vcf.gz
    sample2.g.vcf.gz
    metadata.csv
  batch1
    sample3.g.vcf.gz
    sample4.g.vcf.gz
    metadata.csv
joint_vcf
  v0.mt
  raw
    v0.mt (before variant filters - keeping it until the variant QC workflow is stable)

# analysis (or temporary)
joint_vcf
  v0
    sample_qc
    variant_qc
      vqsr
      rf

So the command line arguments to the script look as follows: --dataset tob-wgs --version v0 --batch 0 --batch 1 --to temporary.

Add a helper script to run with the analysis runner: joint-calling/workflows/drive_joint_calling.py

Add new steps to the workflow: reblock_gvcf to populate fields required for VQSR; GVCF combiner; sample QC; random forest steps (annotation and model creation). VQSR and RF can be enabled with --run-vqsr and --run-rf respectively.

Run example on a test data (19 samples): https://batch.hail.populationgenomics.org.au/batches/1465,
on 96 samples: https://batch.hail.populationgenomics.org.au/batches/1448 (output in gs://cpg-tob-wgs-temporary/joint_vcf/v1/)

Good point! Updated it write the matrix table to main if --access-level full, and other files (plots and tables) to analysis. With standard or test access level, it will write everything to temporary.

Before looking at the code in detail, a high-level response to the bucket structure: shouldn't the MatrixTables end up in the main bucket?
We also discussed only having one version to avoid duplication (not a raw and qc version, with soft filters). Can we already move to that model? What does work refer to?

I'm a bit confused why we have a joint_vcf folder both in main and analysis:
# main (or test):
joint_vcf
  v0.mt
  raw
    v0.mt (before variant filters - keeping it until the variant QC workflow is stable)

# analysis (or temporary)
joint_vcf
  v0
    sample_qc
    variant_qc
      vqsr
      rf

Why not keep a single MT in main, with soft filters and a metadata annotation whether VQSR or RF was used for variant filtering? That would be much more space efficient.

@tiboloic, I consolidated the filtering threshold in one file: https://github.com/populationgenomics/joint-calling/blob/add-rf-and-vqsr/joint_calling/filter_cutoffs.yaml, which can be overridden using a --filter-cutoffs-file option.
Also, updated the docs to actualise the SNP number thresholds, to clarify on the filter-cutoffs file, and to clarify on hard filtering and frequencies calculation.


v4 Sass compile error on flex

Hello,
When compiling v4 bootstrap flex I get the following syntax error:
Sass::SyntaxError:         Sass::SyntaxError: ".col-xs-1" failed to @extend "%grid-column-float-xs".
        The selector "%grid-column-float-xs" was not found.
        Use "@extend %grid-column-float-xs !optional" if the extend should be able to fail.

Regards,

Is this using the Ruby compiler? I recalling hitting something similar last week

Yes,
Basically the following thing happens in the spec (it asserts that the file could be compiled):
It successfully passes on bootstrap.scss but fails on bootstrap-flex.scss
%w(_bootstrap _bootstrap-flex _bootstrap-grid _bootstrap-reboot).each do |file|
      FileUtils.rm_rf('.sass-cache', secure: true)
      engine = Sass::Engine.for_file("#{path}/#{file}.scss", syntax: :scss, load_paths: [path])
      FileUtils.mkdir_p("tmp/#{File.dirname(file)}")
      File.open("tmp/#{file}.css", 'w') { |f|
        f.write engine.render
      }
      assert true # nothing was raised
    end

You can git clone and run the specs: https://github.com/JanStevens/bootstrap-sass
Using Sass gem 3.4.16, havent tried with other versions

Samsies. Also using 3.4.16. Same error with Compass 1.0.3.

Change line 34 in _grid-frameworks.scss to:
@if $enable-flex {
  // Do nothing
} @else {
  @extend %grid-column-float-#{$breakpoint};
}

and it will compile.

What about the optional flag?
In _grid-framework.scss line 31
@for $i from 1 through $columns {
  .col-#{$breakpoint}-#{$i} {
    @extend %grid-column-float-#{$breakpoint} !optional;
    @include make-col-span($i, $columns);
  }
}

Fixed by f88cbe7ee4e2b765b1c4c53efa9a5077e6a22529.


Resolved kirang89/song-bot#1 . Implemented automatic album-directory cre...

Following is algo, I tried to implement. pls give sugggestions.

Ask user 'Do you want create album? (y) '
If answer NOT  in ('y', 'Y', 'yes', 'YES'),   download song/ songs in current directory.
If answer in ('y', 'Y', 'yes', 'YES') then, chck if directory already exits.
If exists then download songs in it
else create it and download songs in it.

This sounds good! Thank you for taking your time to do this. Happy 2015 :)

This sounds good! Thank you for taking your time to do this. Happy 2015 :)

@kirang89  Thanks for merging. Happy New Year

@kirang89  Thanks for merging. Happy New Year


powershell: 6.2.3 -> 6.2.4

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/powershell/versions.
meta.description for powershell is: '"Cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework"'.
meta.homepage for powershell is: '"https://github.com/PowerShell/PowerShell"
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.2.4 with grep in /nix/store/afwb91v2adxm69rjsxb1yvsy8qhhig94-powershell-6.2.4

directory tree listing: https://gist.github.com/6f939e9fa8ca55964cfaa3ec86f1b49e

du listing: https://gist.github.com/1f2da615f8a3c05c5280cf470960e17f

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

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
powershell

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/afwb91v2adxm69rjsxb1yvsy8qhhig94-powershell-6.2.4 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's 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 powershell https://github.com/r-ryantm/nixpkgs/archive/f7f2d0db9b202096391316827dd20cdb8d53b574.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/afwb91v2adxm69rjsxb1yvsy8qhhig94-powershell-6.2.4
ls -la /nix/store/afwb91v2adxm69rjsxb1yvsy8qhhig94-powershell-6.2.4/bin

cc @yrashk for testing.

closing in favor of #84454


Feature/new encoding

This is related to eleveldb PR: https://github.com/basho/eleveldb/pull/157
Per group discussion last Friday it was decided to change the riak_object content encoding format for TS, from:
<< EncBin/binary >>
to
<<?ENC_MAGIC/integer, EncBin/binary>>
The change to riak_object.erl are to implement this new encoding format.  Changes are:

Add MSGPACK_MAGIC macro (it was decided this should be 2)

Modified from_binary() to remove the now obsolete encoding specification (since it is contained in the encoded contents as the magic number)

However I left a stub with the encoding argument around just in case someone still tries to call the old from_binary/4

Removed the obsolete encoding argument from the call chain initiated by from_binary/3

changed encode_msgpack to use the new format,ie:

encode_msgpack(Bin) ->

msgpack:pack(Bin, [{format, jsx}]).

<<?MSGPACK_MAGIC:8/integer, (msgpack:pack(Bin, [{format, jsx}]))/binary>>.

Added a pattern match to decode_maybe_binary to match on the new magic number:

decode_maybe_binary(<<?MSGPACK_MAGIC:8/integer, Bin/binary>>) ->
decode_msgpack(Bin);

And one questionable change that warrants some thought:  I added a default for no valid starting byte (either 0, 1 or ?MSGPACK_MAGIC), the idea being that if anyone tries to read back data written with the previous msgpack encoding format, the code would quietly read it and not try to decode it -- ie treat it like a user-supplied binary of unknown content, same as if the initial byte were a 1:

decode_maybe_binary(<<Bin/binary>>) ->
Bin.

Running a few r_t's that are meant to read/write data, as well as some poking manually on the shell seems to indicate no issues. However, I would like to see an automated test added for this. "test/riak_object_eqc.erl" seems a good candidate for this.

Thanks for the comments!  I changed the macro to MSGPACK_ENCODING_FLAG, and added an automated unit test to riak_object.erl (packObj_test/0), to test encoding/decoding in both msgpack and normal term_to_binary() encoding.   (This was previously tested in my sandbox, but not committed as a unit test)

+1 23535f7
Cover indicates the test covers the code, and is easier than doing it on my own.


Make actions with template arguments usable and add documentation

Actions may have template arguments. However it's not obvious how to write them. We need to find a nice and simple way to define them and we need to add some documentation describing the new API.

I think this can be closed now. The example template_function_accumulator demonstrates how to use templated actions.


[SPARK-36673][SQL][FOLLOWUP] Remove duplicate test in DataFrameSetOperationsSuite

What changes were proposed in this pull request?

As a followup of #34025 to remove duplicate test.
Why are the changes needed?

To remove duplicate test.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing test.

cc @xkrogen

LGTM, thanks!

Thank you @xkrogen !

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47926/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47926/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47926/

Merging to master/3.2.

Test build #143419 has finished for PR 34032 at commit e90d207.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143419/


Use global code coverage flag in swift package generate-xcodeproj

There's a conflict between '--enable-code-coverage' in the top-level options and the same flag in the Xcode-project generation command. This uses the top-level flag (which is required for the build parameters, even though it's only ever used by swift test) for both purposes.

This should unblock moving to ArgumentParser version 0.3.1.

@swift-ci please test

Right, the only user-facing change is that it adds the --disable-code-coverage flag (which will be a no-op).

Right, the only user-facing change is that it adds the --disable-code-coverage flag (which will be a no-op).

That seems fine to me, since enable- and disable- prefixes are a standard and expected idiom, even when just repeating the default.
Thanks!

@swift-ci please smoke test

Sure! We'll just need to coordinate landing with the other Swift project clients. I'll add a comment about that in the manifest.

@swift-ci Please smoke test

@swift-ci Please test self hosted

@swift-ci Please smoke test self hosted

@swift-ci Please smoke test


Feature Request: Installation via Homebrew

I'd love to be able to install the quba-viewer via brew! Are there any plans to add the quba-viewer formula in the near future?

I just opened a pull request to add it as a cask: https://github.com/Homebrew/homebrew-cask/pull/187408

very cool thank you, just watch out for #23 this will most likely change the format of the name of the dmg as of 1.4.1


Support EOF Contracts

This requires a reasonable change from the current situation.  Its not clear to me best how to manage it.

In an ideal world, we would have a (roughly speaking) consistent interface that allowed us to iterate "sections".  For example, one section is a function, etc.  So for legacy contracts we have to work harder, but for non-legacy contracts life is easier.
Perhaps even the simplest option is actually to simply to convert the contract into EOF form?  But, perhaps we do lose something there.


Replace janky merge_on_date_year with built-in merge_asof()

Tracked down the source of the frequency mismatch between some MCOE output dataframes
and the frequency of their output objects. It was due to some bad merges in both the EIA
923 outputs and the mcoe analysis outputs. Several problems arose from the fact that
our merge_on_date_year() function would silently choose just the left dataframe's
version of any column which appeared in both dataframes, leading to unexpected outcomes
when we didn't realize that the column existed in both the left and right dataframes.
I got rid of merge_on_date_year() entirely, as well as the is_annual() function which
was only called by it, and replaced them with a much shorter, simpler function in
helpers called clean_merge_asof() that uses the pandas.merge_asof() method to bring
together dataframes with different time frequencies. It also ensures that the columns
which are being merged on are sorted, as required by merge_asof(), and that they have
the same datatypes (e.g. if plant_id_eia is an int64 in one dataframe, and
pandas.Int64Dtype() in the other, it'll cast them both to a uniform type, which must be
explicitly specified as an input). It also ensures that report_date is a Datetime and
not just a column of iso date strings like "2021-07-27"
In addition to the frequency mismatch issue, replacing merge_on_date_year() surfaced a
bad bug in the fuel_receipts_costs_eia923() output function, which was merging in the
coalmines_eia923 table, including a column named just "state" -- i.e. the state that the
coalmine is in... not the state that the plant is in. Then when the plant's state was
merged in, it was ignored, since a state column already existed in the (at that point)
left dataframe. This probably had two effects:

Many fewer records in the frc_eia923 table had states associated with them than would
be expected, since not all fuel deliveries come from mines.
The records that did end up having states had the states of the mine not the
plant. This bad state field was then used to merge in the monthly average fuel prices
from the EIA API in cases where no fuel price was reported.
As a result, we were unable to fill in as many missing fuel prices as with might
otherwise have been able to.

In addition, I discovered that the pudl_out.bga() and pudl_out.bga_eia860() methods,
which were linked up to the pudl.outputs.mcoe.boiler_generator_assn() and
pudl.outputs.glue.boiler_generator_assn_eia860() functions respectively, were identical,
except that the bga() version dropped the autoincrementing pseudo key field "id". I
think this situation is leftover from when we hadn't yet integrated our more complete
bga() process into the database, and it was being run on the fly by the output object.
So far as I know, this arrangement wasn't causing any actual errors, but it was
confusing and duplicative, and so I removed the bga() functionality, since bga_eia860()
follows the naming convention of other database tables more closely.
I moved the integration of the unit_id_pudl field into the boiler_fuel_eia923() and
generation_eia923() output functions, since those fields end up getting used later on,
and the were being added in several different places. This led to column conflicts and
duplicated code.
Added a Sphinx extension that will allow us to add re-directs in the documentation
if/when we move a page, and used it to redirect anyone visiting the new removed
data_dictionary.html page to the new page under data_dictionaries/pudl_db.html
Closes #1088
Closes #1102

@cmgosnell see the commit messages for the last two commits that went into this PR for additional details on what happened and why: dbbc7e4 and 3c90593
I still need to make unit tests to exercise pudl.helpers.clean_merge_asof()


fix: add update-name script

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


Recursive type checking

Adds a getValues function in JimpleNode that recursively finds all Values in the node.
Changes the generalizedValuesAreEqual function to use getValues rather than getTopLevelValues.
Adds tests for both functions.

Codecov Report

Merging #125 into master will increase coverage by 0.3%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master     #125     +/-   ##
===========================================
+ Coverage     85.94%   86.25%   +0.3%
- Complexity      255      277     +22
===========================================
  Files            27       28      +1
  Lines           548      582     +34
  Branches        114      119      +5
===========================================
+ Hits            471      502     +31
  Misses           23       23
- Partials         54       57      +3

Impacted Files
Coverage Δ
Complexity Δ

...aapi/models/libraryusagegraph/jimple/JimpleNode.kt
94.44% <100%> (+12.09%)
21 <3> (+4)
:arrow_up:

...raryusagegraph/jimple/GeneralizedNodeComparator.kt
83.87% <100%> (ø)
21 <0> (ø)
:arrow_down:

...haapi/models/project/javamaven/JavaMavenProject.kt
76.47% <0%> (ø)
13% <0%> (?)

...raphgenerator/jimple/LibraryUsageGraphGenerator.kt
88.46% <0%> (+2.74%)
9% <0%> (ø)
:arrow_down:

...eline/projectcompiler/javamaven/ProjectCompiler.kt
83.78% <0%> (+3.01%)
11% <0%> (+5%)
: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 0b1a83f...c132588. Read the comment docs.

@gandreadis Done!