vector-algorithms-<IP_ADDRESS> test suite crashes GHC 7.10.3

While building LTS 4.0, I ran into the following issue at http://hydra.cryp.to/build/1523996/nixlog/1/raw:
properties: internal error: evacuate: strange closure type -326929864
    (GHC version 7.10.3 for x86_64_unknown_linux)
    Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
Test suite properties: FAIL

One thing I don't quite understand is why that package is part of LTS 4.0 in the first place considering that https://github.com/fpco/stackage/blob/master/build-constraints.yaml doesn't list it? Am I missing something terribly obvious?

It's a dependency of packages that are in stackage, e.g. snap.

OK, I see. I was just wondering how to find out which maintainer to ping as a part if this issue and by looking at build-constraints.yaml I could not, which surprised me.

If you add a vector-algorithms < 0 constraint:
V~/r/s/stackage master> stackage-curator check
Loading default build constraints
Creating build plan
Determining target package versions
Parsing package descriptions
Writing build plan to check-plan.yaml
Checking plan
stackage-curator:
vector-algorithms (not present) depended on by:
- [ ] Rasterific-0.6.1 (>=0.3). Vincent Berthoux<EMAIL_ADDRESS>@Twinside
- [ ] criterion-<IP_ADDRESS> (>=0.4). FP Complete<EMAIL_ADDRESS>@snoyberg. @bos
- [ ] hoogle-4.2.43 (>=0.6). Neil Mitchell. @ndmitchell
- [ ] metrics-<IP_ADDRESS> (-any). Ian Duncan<EMAIL_ADDRESS>@iand675. @iand675
- [ ] mono-traversable-<IP_ADDRESS> (>=0.6). No maintainer. @snoyberg
- [ ] snap-<IP_ADDRESS> (>=0.4 && < 0.8). No maintainer. @mightybyte
- [ ] statistics-<IP_ADDRESS> (>=0.4). No maintainer. @bos

You can also look in the LTS YAML file itself for the users, e.g.:
  vector-algorithms:
    users:
    - Rasterific
    - criterion
    - hoogle
    - metrics
    - mono-traversable
    - snap
    - statistics
    - vector-algorithms

For what it's worth: the build succeeds fine if the test suite is disabled, any I haven't noticed any issues in dependent packages either.

I'm unable to reproduce the test suite failure. Is there any action we can take to address this issue?

We're no longer using GHC 7.10.3, closing.


can't read pdb ends with .pdb1.gz

Hi,
I found an interesting naming convention in pdb, which causes bugs in graphin. When I download files from PDB, e.g.,  6mhu.pdb1.gz, which ends with pdb1.gz, graphin can not read it because it accepts pdb.gz.
https://github.com/a-r-j/graphein/blob/77a4d9ab90dd525876766e6d5b88f0bb7ac10274/graphein/protein/graphs.py#L103
However, these two formats are the same thing.
Just curious about why PDB has such a name format. I also suggest U to support this format. I am happy to submit a PR for that.
Below is the code to download the pdb files.
    def _download_pdb(self,savedir = ".data/all_biounits"):
        os.makedirs(savedir, exist_ok=True)

        LOGFILE = "pdb_logs"
        SERVER = "rsync.ebi.ac.uk::pub/databases/rcsb/pdb-remediated"
        PORT = "873"
        FTPPATH = "/data/biounit/PDB/divided/"

        # Construct the rsync command
        rsync_cmd = [
            "rsync",
            "-rlpt",
            '-v',
            '-z',
            "--delete",
            f"--port={PORT}",
            f"{SERVER}{FTPPATH}",
            savedir
        ]
        print(' '.join(rsync_cmd))
        subprocess.run(
            rsync_cmd,
            stdout=subprocess.PIPE,
            stderr=subprocess.PIPE,
            text=True,
            check=True
        )

        return savedir```

I found pandas pdb also does not support the pdb1.gz format...

HI @pengzhangzhi thanks for raising this issue. It's a good spot and it should be supported. I'd suggest opening another issue with biopandas as we will also need to add support there first.
Re: why this format exists, this is to distinguish biological assemblies.


Lynt v1

A Lynt v1 milestone exists so you can see which issues need to be resolved before releasing v1.
The main priority right now:

Use ESLint instead of TSLint for TypeScript files
Auto-detect necessary features instead of needing to pass in --react or --flow or --typescript flags
Vue support
Create editor plugins (VSCode to start off with)

Yes from me for supporting frameworks outside react ecosystem


Issues with the new technology editor

I have merged the new technology editor and gas network into master (not deployed to staging), but there are some minor "niggles" still occurring. I'll note them here, but I can split this into separate issues if preferred.

I can't add certain technologies to an existing LES. I can delete and edit technologies successfully. Strangely, some technologies can be added:
Can be added:

Battery
Power-to-gas

Cannot be added:

Buffer space-heating
Buffer hot water
Household
Building
Electric vehicle
Other
Residential PV panel

It seems that I can import a new LES with these technologies, but I cannot add them manually to an existing LES.

Adding a household technology shows two profile select boxes:

Using the default topology, if I add a battery or power-to-gas to the "Households 2" endpoint, the technology is instead added to "Households 1". This only seems to affect existing testing grounds; technologies are assigned to Households 2 and 3 and successfully saved when importing a new LES.

Adding a household technology shows two profile select boxes:

You should change the units field for some duplication fun:

:sweat_smile:
I'll look into the issues though.

I can't add certain technologies to an existing LES.

"but I cannot add them manually to an existing LES."
Do you have an exmample LES?
Or what do you mean by 'added'. Does that mean, that the template does pop-up but it doesn't add it to the technology_profile in the database?

Adding a household technology shows two profile select boxes: -> fixed

Using the default topology, if I add a battery or power-to-gas to the "Households 2" endpoint, the technology is instead added to "Households 1"

I still need to look into this one.

You should change the units field for some duplication fun:

:laughing:

Does that mean, that the template does pop-up but it doesn't add it to the technology_profile in the database?

Yes exactly. The UI works fine, the data is sent to the Rails app correctly, but the TestingGround doesn't get saved.
I have found the reason: it appears the load profile key is being duplicated before it is sent from the browser to the Rails app. The TestingGround validation fails with a message such as:
"has an unknown load profile: ev_availability_profile_1_3.7_kwev_availability_profile_1_3.7_kw"

Eh, maybe you could give an example LES here aswell? I'm trying really hard to break it though.

Grab a copy of the staging database, import it locally, and run the migrations.
Visit http://MOSES_URL/testing_grounds/372/edit
Add a Battery to "Households 2" and press "Save".
Refresh the page. The battery has appeared on "Households 1".

Thanks!

"has an unknown load profile: ev_availability_profile_1_3.7_kwev_availability_profile_1_3.7_kw"

I found it. Wrong jQuery selector,, again.


Adding functional tests to MetaPackages

This is following up to #24  For the new static WebHost APIs

Adding test for #24 which is in preview1. This should also go into the 2.0.0-preview1 branch cc @muratg @Eilon


WiFiS3 add gettime issue 206

This requires a change in bridge as well.(pull request has been sent)
In commands.h it MUST have :
#define _GETTIME                 "+GETTIME"
regards,
Paul

Wifi.h and WiFi.cpp are NOT copied before compile. They are included in the pull requirest. What do I need to do ?


⚠ Bofrost.lu has degraded performance

In 43d2c7e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1097 ms

Resolved: Bofrost.lu performance has improved in 2ec7cb4.


Market Page should error if it cannot load the market ID

We should check the value of the market id in the market-view
https://github.com/AugurProject/augur/blob/master/packages/augur-ui/src/modules/market/containers/market-view.ts#L46
Make sure to checksum format it (use getAddress from ethers.js/utils) and error if its not a valid address or our utils formatAddress
Also, should error if the market is not found (e.g. if the hotloading can't load any market data).
Currently UI blows up in SDK

There are two situations

marketId is not a valid ethereum address
marketId doesn't exists as a market

not a marketid but valid ethereum address

I saw the error once but unable to bring it up again

@matt-bullock  I think the above only happens if user goes to a market trading page then changes the marketId to make an invalid market address.
if the user clicks on a link with bad marketId address the market loads correctly with market not found modal.

@bthaile ok these links show the message correctly so I'll close


Fix Common class ignoring other branches of multiple inheritance tree

Common was not calling super().__init__() method, which means mixin classes might have been excluded from the chain of __init__() calls. Fixing that, and adding a "root" class to handle calls to object.__init__().

Added to 1.22 right away, it should be a no-op fix needed for the future development of Common-derived classes.

@happz is this some more info on this topic? https://www.thedigitalcatonline.com/blog/2020/03/27/mixin-classes-in-python/ ?

@happz is this some more info on this topic? https://www.thedigitalcatonline.com/blog/2020/03/27/mixin-classes-in-python/ ?

It's definitely related. Mostly the part of developers being responsible for creating sane inheritance trees once they turn to multiple inheritances. Thanks to our use of keyword-only arguments, our classes tried to propagate arguments to object.__init__(), which would not work.

Perhaps one thing: Shall we update the class overview accordingly?

Perhaps one thing: Shall we update the class overview accordingly?

Done in c2b6dfbca1433a3cf9f3e31a76e9e4f02a5d9fa1

Perhaps one thing: Shall we update the class overview accordingly?

Done in c2b6dfb

thx. clicked the checkbox item :)

Tests were failing because of mismatch of github/packit merge. Rebased and squashed.


[Help or suggestion] How to disable short if-else statements on a single line?

Test case
// Input to the formatter, preferably a reduced test case.
always_ff @(posedge clk, posedge rst) begin
    if (rst) dout <= 2'b0;
    else if (en1) dout <= 2'b01;
    else if (en2) dout <= 2'b10;
end

Actual output
// This doesn't look right.
always_ff @(posedge clk, posedge rst) begin
    if (rst) dout <= 2'b0;
    else if (en1) dout <= 2'b01;
    else if (en2) dout <= 2'b10;
end

Expected or suggested output
// This result would look better from the formatter.
always_ff @(posedge clk, posedge rst) begin
    if (rst)
        dout <= 2'b0;
    else if (en1)
        dout <= 2'b01;
    else if (en2)
        dout <= 2'b10;
end

So is there a way to make the if-else statement and assignment statement on the different lines for current release? If not, I strongly strongly suggest to give an option to enable this feature, just like AllowShortIfStatementsOnASingleLine: Never option in clang-format. I really don't like they are on the same line even if no begin-end block!
Thank you!

Hello,
Did you manage to solve it? I am looking for that also.

Haha, I am not alone. No, I give up that. BTW, verible updates so slow :(

Hopefully the authors can solve this problem quickly！Thanks！


EventGrid: Update 2020-04-01-preview swagger to include new properties per customer's feedback

EventGrid: Update 2020-04-01-preview swagger to include new properties per customer's feedback
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[X] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

Hello @akning-ms ... The breaking changes failure is false positive. All the removed properties and newly added ones are by design and based on the external customer feedback/requirements. Please note that all these properties were added as part of the 2020-04-01-preview which is still in preview and was not GA'ed yet.

@banisadr  Can you please review the changes .. thanks

/azp run automation - sdk

@chiragg4u  Per your request, we got the PR reviewed by the PM and approved. kindly provide the sign off from ARM team to complete this PR.
@akning-ms  The tests/gates seems to be stuck since yesterday with no progress. Seems to be an infra issue?

/azp run automation - sdk


Assigned Animation Libraries can't be removed from Animation Players

Godot version
4.10 alpha
System information
Windows 10, amd 6900xt, vulkan clustered
Issue description
Animation libraries that have been added to an animation player can't be removed.
Steps to reproduce

Add an animation library to an animation player using the Animation > Manage Animations... windows.
Try to delete the animation library by clicking on the trash can symbol.

Minimal reproduction project
Try to remove the "rotate" animation from the animation player in the Example Scene:
AnimationBugReports.zip

Duplicate of #61422
Fixed by #62151


Validate cursor position in UIA UTR ctor

Summary of the Pull Request
This adds some validation in the UiaTextRange ctor for the cursor position.
#8730 was caused by creating a UiaTextRange at the cursor position when it was in a delayed state (meaning it's purposefully hanging off of the right edge of the buffer). Normally, Cursor maintains a flag to keep track of when that occurs, but Windows Terminal isn't maintaining that properly in Terminal::WriteBuffer.
The correct approach would be to fix WriteBuffer then leverage that flag for validation in UiaTextRange. However, messing with WriteBuffer is a little too risky for our comfort right now. So we'll do the second half of that by checking if the cursor position is valid. Since the cursor is really only expected to be out of bounds when it's in that delayed state, we get the same result (just maybe a tad slower than simply checking a flag).
Closes #8730
Filed #12440 to track changes in Terminal::_WriteBuffer for delayed EOL wrap.
Validation Steps Performed
While using magnifier, input/delete wrapped text in input buffer.

Are there plans to remove the FailFast logic in this PR as well?

Are there plans to remove the FailFast logic in this PR as well?

Nope. That's a huge undertaking. @miniksa and I were talking about the possibility of switching them over to asserts, but we'll have to do some research before committing to that.

I FOUND IT
OpenConsole!1794053.

Since we don't really do chk and have a ton of different types of asserts, we're going to reduce this all down to one pattern.
Either it's important enough to check and fast fail on to generate a bucket all the time, or it should be recovered and keep going.
Many of the asserts we have are indicative of programming failures on our part, so they should crash when we are building/testing them. Others are indicative of stuff that should "never happen". So either they never happen and we won't crash, or they do happen, will crash, and we can identify what sorts of reliability enhancements to make in these areas by their hit level.
I've removed assert(), ASSERT(), NT_ASSERT(), Assert(), and ASSERT_FRE() from the code and replaced things with either a FAIL_FAST_* wil macro or removed it, especially if it's a thing we've never really utilized.

I FOUND IT
OpenConsole!1794053.

Since we don't really do chk and have a ton of different types of asserts, we're going to reduce this all down to one pattern.
Either it's important enough to check and fast fail on to generate a bucket all the time, or it should be recovered and keep going.
Many of the asserts we have are indicative of programming failures on our part, so they should crash when we are building/testing them. Others are indicative of stuff that should "never happen". So either they never happen and we won't crash, or they do happen, will crash, and we can identify what sorts of reliability enhancements to make in these areas by their hit level.
I've removed assert(), ASSERT(), NT_ASSERT(), Assert(), and ASSERT_FRE() from the code and replaced things with either a FAIL_FAST_* wil macro or removed it, especially if it's a thing we've never really utilized.

When I talked about this verbally to @carlos-zamora, I had suggested using a telemetry-based assert so we could collect the stack of the failure but not crash the application. Like whatever that engineering system thing is we have that lets you effectively make a "crash report" but keep running. I thought it was telemetry asserts. I did not mean those classic ones that I converted from in that old OpenConsole PR.

you do still need to fix the SA build!

you do still need to fix the SA build!

oh yeah. Idk why that's happening. _pData is checked for nullness in the RuntimeClassInitialize() call -.-.
I'll just check it again, I guess.

the static analyzer is not capable of telling that RuntimeClassInitialize does a null check INSIDE itself and propagating that out to callers

the static analyzer is not capable of telling that RuntimeClassInitialize does a null check INSIDE itself and propagating that out to callers

That's fair. But out of curiosity, why is it complaining now? I didn't touch the method signature.

you are using pData on the body now where you were not before


Pod install error "env: node: No such file or directory" and "Invalid Podfile file: A JSON text must at least contain two octets!."

When trying to create a new react-native project using react-native init I get the following error when running pod install:
env: node: No such file or directory

[!] Invalid `Podfile` file: A JSON text must at least contain two octets!.

 #  from /Users/kristoffer/rnt/ios/Podfile:42
 #  -------------------------------------------
 #
 >    use_native_modules!
 #  end
 #  -------------------------------------------`

Node is installed, running node --version yields v10.16.3.
cocoapods is version 1.8.1.
ruby is version ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin18]
React Native version:
System:
OS: macOS Mojave 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 3.21 GB / 16.00 GB
Shell: Unknown - /usr/local/bin/fish
Binaries:
Node: 10.16.3 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
IDEs:
Xcode: 11.0/11A420a - /usr/bin/xcodebuild
npmGlobalPackages:
react-native: 0.61.1
Steps To Reproduce

react-native init rnt
cd rnt
cd ios
pod install

Describe what you expected to happen:
Pods should be installed without error.
Snack, code example, screenshot, or link to a repository:

Any solutions. i have the same issue.

Issue was that I had two different versions of Cocoa Pods installed, make sure you have the latest version only.
Skickat från min iPhone

7 okt. 2019 kl. 17:58 skrev Ronald<EMAIL_ADDRESS>
Any solutions. i have the same issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Use /api/v1/alerts instead of /api/v1/alerts/groups

I have been talking with @fabxc and @brancz about our current Alertmanager API consumption. We decided to keep AlertGroups and AlertBlocks a server-side implementation detail that the UI doesn't need to know of. This would flatten the UI representation of alerts and keep things simple. The UI would just consume /api/v1/alerts and would only know of the entity Alerts not AlertGroups or Blocks.
Steps needed:

Implement filter logic for endpoint /alerts like it already exists on /alerts/groups
Refactor UI to use /alerts instead of /alerts/groups
(Future) Implement groupBy logic for endpoint /alerts

@stuartnelson3 What do you think? As you implemented the filter logic for the /alerts/groups endpoint, is there any show stopper that I overlooked?

Can't think of any off the top of my head -- the logic just does a match on individual alert objects, so you should be able to re-use it just fine.

I find it useful to see the alert groups - I think it'd be a shame to lose that view in the UI.

Does this mean that the /api/v1/alerts/groups API endpoint would be removed?

@mattbostock The current group representation is not accurate either as we flatten the routing tree they are in to reduce the complexity of the representation – giving you a false sense of security as may happen. What we end up with is something structured, yet not representing the actual structure underneath and not giving you the querying flexibility you want either.
Our reasoning is as follow: Prometheus also has labels and follows a very free form approach to exposing them, i.e. you don't retrieve them as you collected them per your scrape configs but just access them via label selectors.
This gives you a lot of power and while it doesn't give you hard relationships, you can trivially query the same thing manually.
So we wanted to follow something similar – you can freely select from all alerts by labels and freely define how you would like to group them. If you get paged from service=X, zone=eu-west, going to the UI and selecting by exactly those labels will give you what you want 99% of the time. So will querying everything and grouping by (service, zone), or querying team=my_team and grouping by  (service, severity).
You just get a lot of freedom in what you can query and results being slightly fuzzy, e.g. seeing the occasional alert you didn't really care about, doesn't inhibit your use experience as you can just quickly add another selector.

@mattbostock In regards to your second comment: So far there are no plans to remove the /api/v1/alerts/groups endpoint.

@stuartnelson3 @w0rm To prevent duplicate work: Starting on this now.

Closed by #754


bug when proxying itself

09:44:32 I uihandler.go:449> GET /fortio/?url=http%3A%2F%2Flocalhost%3A8080%2Ffortio%2Ffetch%2Flocalhost%3A8080%2Fecho&qps=100&t=3s&c=1&p=50%2C+75%2C+99%2C+99.9&r=0.0001&H=User-Agent%3A+istio%2Ffortio-0.3.4&H=&load=Start HTTP/1.1 [::1]:65293
09:44:32 I uihandler.go:82> Starting load request from [::1]:65293 for http://localhost:8080/fortio/fetch/localhost:8080/echo
09:44:32 I http.go:101> Setting regular extra header User-Agent: istio/fortio-0.3.4
09:44:32 I httprunner.go:83> Starting http test for http://localhost:8080/fortio/fetch/localhost:8080/echo with 1 threads at 100.0 qps
09:44:32 I uihandler.go:449> GET /fortio/fetch/localhost:8080/echo HTTP/1.1 [::1]:65296
09:44:32 I http.go:634> Server wants to close connection, no keep-alive!
09:44:32 E http.go:644> More data is available but stopping after 135, increase -httpbufferkb

reproducible with
fortio load -curl -httpccch -loglevel=debug http://<IP_ADDRESS>:8081/fortio/fetch/localhost:8081/debug

too
(with the version of fortio main which doesn't hard code keepalive to false)


Fix tensorflow version, remove unnecessary 2020-resolver option.

Change-Id: I8fc660196462d7b18d946a23ce9b77c1c6887722
Signed-off-by: Luca Foschiani<EMAIL_ADDRESS>Issue-Id: SCM-1697

Depends on #26 for CI to pass.

Depends on #26 for CI to pass.

Depends on #26 for CI to pass.

Thanks for the heads up.

Depends on #26 for CI to pass.

Thanks for the heads up.


404.html issue on mobile view

The hamburger menu overlaps the content of the 404.html page, as shown in this screenshot (iPhone 6/7/8 view) :

It seems that the following rule on _main.scss :
@media screen and (max-width: $medium - 1) {
  padding-top: calc(3rem + #{$burgerContainerHeight});
}

is overriden by this one on about.scss :
main {
  padding-top: 0;
  ...
}


Feat/migrator

Hey
This PR introduce de protocol key on the FileMigrationProvider
This allows window users to add a protocol if they need to
https://github.com/kysely-org/kysely/pull/430
Thanks again for this amazing library

https://github.com/kysely-org/kysely/pull/430#issuecomment-1691251528

Thanks !


Can not get Credentials from AWS ECS

When deploy to ecs, I found it can not get credentials from ecs task role.
Maybe need add ContainerCredentialsProvider in CustomCredentialsProviderChain.java

Hi @crazygit thanks for reporting. I think it could make sense to add that provider to the chain but in the meantime you can create a new Kinesis Appender with the credentials provider you need and add it in.
Here's an example (using a Logstash layout but you could use any sort):
import ch.qos.logback.classic.Logger;
import ch.qos.logback.classic.spi.ILoggingEvent;
import com.gu.logback.appender.kinesis.KinesisAppender;
import net.logstash.logback.layout.LogstashLayout;
import org.slf4j.LoggerFactory;
import com.amazonaws..auth.ContainerCredentialsProvider;

public class LoggerSwap {
    public static void swapLogger() {
        Logger rootLogger = (Logger) LoggerFactory.getLogger(org.slf4j.Logger.ROOT_LOGGER_NAME);

        LogstashLayout layout = new LogstashLayout();
        layout.setContext(rootLogger.getLoggerContext());
        layout.start();

        KinesisAppender<ILoggingEvent> appender = new KinesisAppender<>();
        appender.setBufferSize(1000);
        appender.setRegion("eu-west-1");
        appender.setStreamName("KINESIS_STREAM_NAME");
        appender.setContext(rootLogger.getLoggerContext());
        appender.setLayout(layout);
        appender.setCredentialsProvider(new ContainerCredentialsProvider());
        appender.start();

        // Stop the existing one if you have configured it
        rootLogger.getAppender("console").stop();
        rootLogger.addAppender(appender);
    }
}

@mbarton
Thanks!

Unfortunately changes from #27 have been reverted by #29


allow Angular 1.5.x

Thanks! I'm sorry, I should have specified - we'll need to update the bower.json in this repo as well so the tests get run on our CI server with the new version of angular.
https://github.com/jtrussell/angular-snap.js/blob/master/bower.json#L10-L13

I'm sorry, my fault.

Justin, perhaps I make something wrong?

Nope - perfect. I just hadn't had a chance to merge yet :). Will publish shortly.

Thx a lot, Justin! :)


[WFLY-8275][JBEAP- 8993] jca inflow transactions integration with new wfly txn client

These are fixes for integration of wildfly transaciton client with JTA and JCA layers.
After discussion with David and Flavia I created a new wrapper JBoss XATerminator class which is configured to be used in JCA. The new terminator then delegates calls to wildfly client ContextXATerminator and inner Narayana calls are mimicked or passed to Naryana's JBossXATerminator implementations.
https://issues.jboss.org/browse/JBEAP-8993
https://issues.jboss.org/browse/WFLY-8275

hi @fl4via,
if you have some time I would like ask you for taking a look at this prepared PR (this is Narayana's forked WildFly repository for testing purposes). It contains some more changes than I put to my email from last week (the one about inflow jca transaction integration with wildfly transaction client).
I plan to create PR to WildFly upstream/master when new release of Narayana and WFTC will be ready.
Thank you


GUIBlock naming is suboptimal

impicit block class GUIBlock should be called differently than object around it - can cause import problems (e.g. in scripting environments such as tut)

Solved by #44


auto-save

generated model did not get auto saved when toolkit crashed

Investigation confirmed that autosave was no implemented in model generation code. New code has been added to enable models to autosave after they have been successfully generated.

fix tested on windows


Create Prototype from existing mockup

Figma. This is still rough, but will suffice for first prototype https://www.figma.com/file/G8essVjeMul3J5mKoxCMQF/spotlightpa-(INTERNAL)?node-id=0%3A1
Notes

The mockup is for the about page. The hero and top-nav will eventually be global.
We will be creating individual pages for

Impact & Awards
Partners
Staff
Supporters
Mission

However, the links on the page below the about copy will lead to that place on the page.
The mockup has only two sections (Impact..., Partners), but we will have sections on the page for each of the other items.
I have Work Sans font in there. Ignore that and use Raleway that is already there. (I just don't think the client's font choice is good, but we should stick with it though)
When user clicks on "More Topics" a drawer should reveal below the hero and show several columns. See mockup for a very rough first draft. - topics should come from: https://www.spotlightpa.org/topics/

@regisphilibert Believe I am going to need some assistance hiding the existing nav/footer from the new about page. Also I'm having trouble getting rid of the banner ad for the newsletter. When you get a chance, can we review? The branch is up to-date, and the page renders at /about/about-tnd

@AdamChlan @budparr we have a working preview on cloudflare: https://spotlightpa-org.pages.dev/about/about-tnd/


Communicate responsible disclosure policy for security issues

Due to Netty's position as the network layer for applications, premature disclosure of security issues could leave applications vulnerable without providing an opportunity for maintainers to address. The Netty project should formulate and clearly communicate a responsible disclosure policy for security issues. This should include a policy for how to handle issues that were not disclosed following the responsible disclosure policy. This would permit the Netty project maintainers the opportunity to investigate, and release fixes (if necessary) for security issues before their disclosure.

+1
from @normanmaurer https://github.com/netty/netty/issues/6312#issuecomment-277777880:

we have<EMAIL_ADDRESS>for reporting security stuff

We should document this clearly. Also we should make sure the appropriate devs have access so we have good coverage.

We may want to update the GitHub issue template or contributor hint to include this info too.
[1] https://github.com/netty/netty/tree/4.1/.github


When I create model, I faced to NO SUCH COLUMN ID error

No description provided.

You should delete migrations and sqlite db and then you should do makemigration and migrate


[Feature] Add option to disable trailing 0

Usually the trailing 0 in CSS/SCSS is deprecated, it would be nice if users can turn it off with a workspace setting such as "sassFormat.trailingZero": false, for example with the current stylelint set I have the trailing 0 is an error and the sass formatter will keep adding it

Hi, @Nikodermus I'll consider this feature for one of the future updates. Thanks.

Please. This has been bugging me so much.


Custom Error JSON Format

Is it possible to customise error JSON format?
All I want to do is to change Error to lowercase error. So when in my code I do:
rest.Error(w, "Decode JSON error", http.StatusBadRequest)

I'd like to get this JSON:
{
  "error": "Decode JSON error"
}

+1

I made a mistake by not having “Error” in lower case. But I also have a strict rule of not breaking compatibility between major versions (see semver.org).
One solution could be to have a global variable with a default value for the error payload field. This default will be “Error” for compat reason, but you’ll be able to change it for your project.
This whole thing will then be cleaned up for version 4.
Sounds reasonable ?

done https://github.com/ant0ine/go-json-rest/commit/c3c57b2a42c1c77a2d8cb5d66393d8796f42cfc0

:+1:


Upgrade webpack to 2.2

This PR is pretty much the result of me banging my head against the wall while trying to get the tests running. All tests are supposed to show up green now!
Seeing how this plugin seems to be pretty much set in terms of what it does, I figured a major release would be the way to go., unless someone can figure out a pretty way to support both versions of webpack next to each other.
Should fix #22

This saved my build - gets my vote!

NOTE: I just discovered a strange problem in our own testsuite on Webpack2.2. It seems that second/third runs don't properly rewire resources. I have no clue what is going on, and we decided to actually move away from rewire, so I won't be able to update this PR. I hope that somebody else will be able to figure out what's going on!

@RSO thanks for your work, I'm curious what are you using instead of rewire?

Not using anything anymore, we've decided that unit-tests like this add less value to our codebase in comparison to the pain they add. In some cases we found other ways around rewire, for instance in cases where we had to mock window.location =, we decide to create a redirectHelper that actually returns a sinon.spy() when called in the test environment.
In other cases we decided that mocking was just simply not the way to go.


stun message pointer nil error

github.com/pion/turn/internal/client.(*UDPConn).bind(0xc080582000, 0xc05ecd7f80, 0x434fd6, 0x8f2a98)
/go/pkg/mod/github.com/pion/turn@v1.3.5/internal/client/conn.go:521 +0x45f
github.com/pion/turn/internal/client.(*UDPConn).WriteTo.func2.1(0xc080582000, 0xc05ecd7f80)
/go/pkg/mod/github.com/pion/turn@v1.3.5/internal/client/conn.go:217 +0x39
created by github.com/pion/turn/internal/client.(*UDPConn).WriteTo.func2
/go/pkg/mod/github.com/pion/turn@v1.3.5/internal/client/conn.go:216 +0xad
Description
Reference issue
Fixes #...

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x73fe6f]
goroutine 5133193 [running]:
github.com/pion/turn/internal/client.(*UDPConn).bind(0xc080582000, 0xc05ecd7f80, 0x434fd6, 0x8f2a98)
/go/pkg/mod/github.com/pion/turn@v1.3.5/internal/client/conn.go:521 +0x45f
github.com/pion/turn/internal/client.(*UDPConn).WriteTo.func2.1(0xc080582000, 0xc05ecd7f80)
/go/pkg/mod/github.com/pion/turn@v1.3.5/internal/client/conn.go:217 +0x39
created by github.com/pion/turn/internal/client.(*UDPConn).WriteTo.func2
/go/pkg/mod/github.com/pion/turn@v1.3.5/internal/client/conn.go:216 +0xad

@hcm007 Thanks for your PR.
There was a similar PR earlier we addressed it.
Your issue might have already been fix at 0e40b1c.
You could use replace in go.mod to confirm, but we should tag the current master then incorporated it into pion/webrtc soon.

once #97 is merged, I will tag, then we can bump pion/turn version for pion/webrtc.

Hi @hcm007, the fix pion/turn@0e40b1c has been landed in pion/webrtc@cabbd8b.

Fixed with https://github.com/pion/webrtc/commit/cabbd8b


Added option to view the changelog

Fixes #535
OK, so it doesnt add any notifications yet, but thats still planned
Signed-off-by: Simon Bennetts<EMAIL_ADDRESS>

@dscrobonia screenshots above - the changelog data is read from the add-on and therefore from https://github.com/zaproxy/zap-hud/blob/develop/CHANGELOG.md so its up to us to put a suitable level of detail in that (re https://github.com/zaproxy/zap-hud/issues/535#issuecomment-507936000)

You might be asking too much of me there :P
In this case I think it would just be a nice to have - I cant see many people wanting to keep going back to the HUD options...


Add zap toggle develop

Describe your changes
Describe the purpose + content of these changes
Link the related issue
Closes #0000
Checklist before requesting a review

[ ] Is this PR ready for merge? (Please convert to a draft PR otherwise)
[ ] I have performed a self-review of my code.
[ ] Did I request feedback from a team member prior to the merge?
[ ] Does my code following the style guide at docs/CODING-STYLE.md?

Instructions for Reviewers
Functionalities or workflows that should specifically be tested.

Environmental conditions that may result in expected but differential behavior.

If relevant, list additional work to complete pre-merge (delete logging, code abstraction, etc)

replaces https://github.com/CrocSwap/ambient-ts-app/pull/4318

just waiting on new SDK functions for Zap Off mode

replaces: https://github.com/CrocSwap/ambient-ts-app/pull/4318


Fixed TC's tanks taking all the fluid of one type even if they can't contain all of it

Fixed TC's tanks taking all the fluid of one type even if they can't contain all of it, resulting in a huge waste of resources in some cases

Do I need to change something, maybe try with the latest successful build from 2 months ago?

I need to change the git branch. The current 1.20.1 branch is based off of upstream 1.19.2 right now which doesn't compile yet


Prebuilt vcpkg-tool+cmake binaries for ARM64 Linux

It would be pretty cool if arm64 linux was a fully supported platform for downloading prebuilt binaries. I'm willing to help make this happen, and have a machine for testing.
CMake already has prebuilt arm64 linux binaries, so that part should be easy at least. I assume steps are something like:

Get arm64 Linux CI/releases working for vcpkg-tool
Fix bootstrap and vcpkgTools.xml

Anything else? Is this interesting?

https://github.com/microsoft/vcpkg/issues/27905#issuecomment-1381039192

@BillyONeal could you clarify if in that comment you meant you need hardware AND cross compilation workflow or hardware OR cross compilation instructions?
I can absolutely set up cross compilation for you, and probably even running tests in a docker container. Would that be acceptable?
Can't help you with hardware :)

@BillyONeal could you clarify if in that comment you meant you need hardware AND cross compilation workflow or hardware OR cross compilation instructions?

I don't know. Is cross compilation how folks who do this normally do it? If so I don't think we need hardware, but we do need someone with the hardware to check and make sure it actually works.

There are pretty much 3 primary ways of doing this to my knowledge:

Have real hardware
Cross-compile using a cross-toolchain and a sysroot
Emulate real hardware (via docker or full VM, docker being much simpler)

Nice thing about 3) is you can run a testsuite as well as you already have a full emulated environment, but compilation is slower as you're also emulating the compiler itself. A blend can work well too (use a cross-toolchain then run tests in an emulated environment).

is preferred when possible, but often isn't (especially for 32-bit targets which can't build some larger projects these days anyways....)

Since vcpkg-tool has few dependencies, I don't think creating a sysroot would be very difficult--may even be able to get away with just installing the cross-stdlib that ubuntu ships if you don't need any other host packages.

@russelltg The other bit is the RHEL 'devtoolset' games we play in order to make sure our bits work on older boxes: https://github.com/microsoft/vcpkg-tool/blob/7b53f45badf690bc18a33446a202cde841234d60/azure-pipelines/signing.yml#L227

Yeah, that makes sense and is good practice when shipping linux binaries. Of course the other option is to statically link libc but that isn't without caveats too. (but nice thing about that is it will run on Alpine, as only dep is the kernel).
Fwiw, it seems like devtoolset is to bring in a newer compiler to and old RHEL verison (which has an old glibc, which is needed for it to be compatible with old systems).
One thing I learned about recently is zig c++, which lets you just specify a glibc version right on the commandline. Unfortuantely, it doesn't seem to support precompiled headers, but I was able to trivally cross compile it against an old glibc (2.17, same as RHEL 7):
$ /bin/cat zig-toolchain-aarch64.cmake
set(CMAKE_SYSTEM_NAME "Linux")
set(CMAKE_SYSTEM_PROCESSOR "aarch64")
set(CMAKE_C_COMPILER "zig" cc -target aarch64-linux-gnu.2.17)
set(CMAKE_CXX_COMPILER "zig" c++ -target aarch64-linux-gnu.2.17)
$ cmake -Bbuild -GNinja -DCMAKE_TOOLCHAIN_FILE=zig-toolchain-aarch64.cmake -DCMAKE_DISABLE_PRECOMPILE_HEADERS=ON
$ ninja -C build
$ file build/vcpkg
build/vcpkg: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 2.0.0, with debug_info, not stripped
$ docker run --rm -v `pwd`:/vcpkg-tool arm64v8/ubuntu:jammy ldd -r -v /vcpkg-tool/build/vcpkg
WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v4) and no specific platform was requested
	libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000400000810000)
	libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000400000830000)
	libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x00004000009f0000)
	/lib/ld-linux-aarch64.so.1 (0x00007fbd9d1c1000)

	Version information:
	/vcpkg-tool/build/vcpkg:
		libpthread.so.0 (GLIBC_2.17) => /lib/aarch64-linux-gnu/libpthread.so.0
		libc.so.6 (GLIBC_2.17) => /lib/aarch64-linux-gnu/libc.so.6
		libdl.so.2 (GLIBC_2.17) => /lib/aarch64-linux-gnu/libdl.so.2
		ld-linux-aarch64.so.1 (GLIBC_2.17) => /lib/ld-linux-aarch64.so.1
	/lib/aarch64-linux-gnu/libpthread.so.0:
		libc.so.6 (GLIBC_2.17) => /lib/aarch64-linux-gnu/libc.so.6
	/lib/aarch64-linux-gnu/libc.so.6:
		ld-linux-aarch64.so.1 (GLIBC_PRIVATE) => /lib/ld-linux-aarch64.so.1
		ld-linux-aarch64.so.1 (GLIBC_2.17) => /lib/ld-linux-aarch64.so.1
	/lib/aarch64-linux-gnu/libdl.so.2:
		libc.so.6 (GLIBC_2.17) => /lib/aarch64-linux-gnu/libc.so.6
$ VCPKG_FORCE_SYSTEM_BINARIES=1 QEMU_LD_PREFIX=/usr/aarch64-linux-gnu ./build/vcpkg --version
vcpkg package management program version 2999-12-31-unknownhash-debug

This statically links in libc++, so similar to what your existing glibc builds do (except I assume those statically link in libstdc++). Since vcpkg works on macOS I assume libc++ is an acceptable standard library for vcpkg.
Since I had to disable precompiled headers, I had to patch vcpkg to add a bunch of missing includes, which would be a slight  maintenance burden (although I consider having proper includes good practice, but ymmv).

Also, I'm realizing that not requiring VCPKG_FORCE_SYSTEM_BINARIES would be the most important part for me and also the easiest, considering CMake ships arm64 binaries....

I want this to stay open

Are there any updates on this issue?

Is there a way for the community to contribute this support or is the build system outside of the repository?
Using GitHub actions, Arm linux builds can be compiled using cross-compilation docker containers such as used in  https://github.com/prebuild/prebuildify-cross or https://github.com/dockcross/dockcross

Is there a way for the community to contribute this support or is the build system outside of the repository?

Ah, I see there's another repo. I've taken a stab at this here: https://github.com/microsoft/vcpkg-tool/pull/1478


Bug fix 3.7/overfetch in filter

Reverts an unintended behavior change in Filter Executor in comparison to 3.6
It will now again fetch full batches of documents instead of taking into account the requested limit.
Backport of:
https://github.com/arangodb/arangodb/pull/12214
"Fixes"
https://arangodb.atlassian.net/browse/BTS-139
Jenkins:
http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11065/

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11067/

Tests blue.


FreeBSD support

This adds FreeBSD support by e.g. making bzip2's build-script use cc instead of gcc. This means that the result may be different for Linux systems that have cc linked to clang instead of gcc.
Not all packages build on FreeBSD yet, but I hope to work on this at NixCon.

It's good to know! I also want to port NixOS to NetBSD, so I will watch your efforts.

I don't think I can do anything about these CI failures, looks like it is just timing out cause the build takes too long?

@AndersonTorres Maybe we could merge the NetBSD and FreeBSD porting efforts, I guess it is mostly just replacing "isFreeBSD" with "isFreeBSD || isNetBSD". You could take the FreeBSD patch for nix and use it with this nixpkgs, and it might work. Then we could merge it together.

cc @tomster

@ysangkok there is some support for NetBSD or FreeBSD on Nix itself?

Currently there is incomplete support for FreeBSD in Nix, but I am expecting mjacob's patch to get merged.
Build farm sounds like a good idea, but what exactly needs to be designed? I can sponsor a jail if needed.

This depends on https://github.com/NixOS/nix/pull/657 so maybe we should wait until that is merged...

A thing: are you testing it using clang and llvm stack? They are the preferred ones on FreeBSD nowadays.

@AndersonTorres yes, I am using clang/llvm. But, I will push some commits switching to coreutils, since nixpkgs depend on them for patching binary files with patch(1). The manual also mentions coreutils. But on NixCon it seemed that there was consensus for making a pure stdenv for FreeBSD, which would be cross-compiled with a Linux-type compiler (which would also run on FreeBSD if binary emulation was working). That stdenv would then probably use gcc since this is what other pure stdenv's use.

Just for the record, the new darwin (almost pure) stdenv uses clang.

Ok, I stand corrected. But currently I am not focusing on the pure stdenv anyway, and most issues seem related to the use of clang. For example, this is the issue I am currenly trying to work around: https://mariadb.atlassian.net/browse/MDEV-5944

@nbp How would you like me to document this?

@domenkozar should we add a release note section to the Nixpkgs manual?

@ysangkok I was thinking of having a section of supported platforms in the Nixpkgs manual, where Linux, Darwin and Cygwin would already be listed, but I do not see any.  If you want to add such documentation in a separate issue I would be fine too, as there is no existing documentation in place.

That depends what's meant by "supported". On Hydra.nixos.org we have CI only for three platforms currently (two Linux and one Darwin). For the rest the state might tend to rot (or we might not know), I'm afraid, and even the Darwin support level doesn't seem to be first-class yet.

@vcunat Bitcoin is building and runs now, I am satisfied with this and would like to get it reviewed for merging.

OK, queued in my TODO ;-)

I tested building some stuff on FreeBSD 11.0-CURRENT and can attest that the workaround for m4 is also required for it (clang 3.7.0).
In 11.0-CURRENT and m4, make check only fails for test 189 (but not for 084 as with FreeBSD 10).
I tested this with the package from the ports tree too and got the same result, so clearly this is not specific to the Nix package.

@vcunat I rebased onto current master.

The stdenvNative changes (in pkgs/stdenv/native/default.nix) seem useless now that stdenvFreeBSD is used instead. It's used by cygwin, for example, and it isn't clear to me if it would be broken by those changes (the alias targets might not be provided).

@vcunat I undid those changes now, you are right, they were unnecessary.

@vcunat I undid those changes now, you are right, they were unnecessary.

While testing this, cyrus_sasl wouldn't build on x86_64-linux; for now I've made the fetched patch and autoreconfHook conditional.

Staged.

Thanks!

@vcunat I'm also happy to help build-farm wise, whenever it's time.

@FlorianHeigl: You mean providing binaries for freebsd in some way?


Integration and UI Testing

What happened (or feature request):
Given the amount of user interaction on the UI, we probably need a more robust approach for integration testing with sample data.
This epic includes:

[ ] Direct integration testing between ddev-ui and ddev, with real projects. So for example, a test to create a site would actually create a site and verify that it came up correctly.
[ ] Testing of any ddev-ui actions that change anything on the filesystem. So for example, if we take any action (like untarring an archive), test to make sure that happened on the filesystem.
[ ] Actual UI testing.

adding @mafriend - this is an epic that contains (some) of the current priorities around testing


java.lang.ArrayStoreException: org.json.JSONObject$1 cannot be stored in an array of type java.lang.String[]

Expected Behaviour
Actual Behaviour
Force close of the app
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Android 6.0.1
Android) What device vendor
Xiaomi Redmi Note 3
Cordova CLI version and cordova platform version
cordova --version                                    6.5.0
cordova platform version android                     6.5.0

Plugin version
cordova plugin version | grep phonegap-plugin-push   1.10.5

Sample Push Data Payload
Sample Code that illustrates the problem
Logs taken while reproducing problem
java.lang.ArrayStoreException: org.json.JSONObject$1 cannot be stored in an array of type java.lang.String[]
at com.google.android.gms.gcm.zza.zzf(Unknown Source)
at com.google.android.gms.gcm.zza.zzs(Unknown Source)
at com.google.android.gms.gcm.GcmListenerService.handleIntent(Unknown Source)
at com.google.android.gms.iid.zzc.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)

Looks like a problem in GCM library, make sure you are using latest version.
Anyway, we are not updating 1.x.x version anymore, you should move to 2.x.x and FCM as Google is deprecating GCM and will stop working next year.


Update faq.md

Updated the AKS Faq use of custom extension information to include the Log Analytics agent.

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

Hi @miwithro -- This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

In re: grammar, from an internal style guide:

#sign-off

@zr-msft: I'm sorry - only the author of this article, @mlearned, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Update README.md

Closes #37

Added approaches to solve micro-challenges given in the micro-byte
Didn't give solutions right away. Instead mentioned the concept used or gave hints
Added multiple approaches to solve the problems wherever possible
Added new concepts on the topic.

@all-contributors kindly add @Nitesh-thapliyal for:

[x] doc

@all-contributors kindly add @Sreejan-22  for:

[x] doc


Generic conversion from map to object

to_value could use an internal overload that converts a map-like object (key/value pairs) to a json::object.

There are a few separate concerns here IMHO:

represent an object as JSON (without necessarily converting it)
parse an object from JSON representation (without necessarily going through a value object)
actual conversion to/from json

"object" here refers specifically to json::object while "map" refers specifically to any ForwardRange whose value type is convertible to json::key_value_pair.

Added in #103


Error in worker thread. Returning empty response......

Checklist

[x] I have read the FAQ
[x] I have checked if this issue already exists (both open and closed issues)
[x] I am using the most recent version of pogom from the master branch
[x] If this is an installation issue, I am posting my OS, OS version, python version, pip version
[x] I'm posting the complete log
[x] I'm using a descriptive title for this issue

My Issue
I keep getting this error:
016-08-10 23:26:11,422 [   auth_ptc] [  ERROR] PTC Login failed.
2016-08-10 23:26:11,422 [     pgoapi] [  ERROR] Error in worker thread. Returning empty response. Error: local variable 'r' referenced before assignment
2016-08-10 23:26:11,422 [       scan] [   INFO] Map Download failed. Trying again.
...
I have had this error for over 2 days now, and it works for my friend all the time. I try to run it from MAC, and he uses Windows.
Hope someone has any answers:)

how many workers are you using and are they ALL getting this?

Tried everything from 1 to 10 workers, and yes all is getting this error.

Banjorune, where you changed workers number?

pedrosodre, it depends on how many ptc/google accs you add, if im not wrong :=)

@Banjorune Are you sure your accounts are verified and accepted ToS?
My scans used to get the same error untill I put the time into creating, accepting ToS and verifiying email for all of my 200 accounts.
https://github.com/FrostTheFox/ptc-acc-gen
https://github.com/TachyonRSA/PoGoTos
https://gist.github.com/sebastienvercammen/e7e0e9e57db246d7f941b789d8508186

Crisicus, I only accepted ToS on the first account. It doesent work on that either, but i will try to verify all the other accounts and see if it helps. (Don't think it will make any difference tho, my friend tried to use one of my PTC acc's on he's pogom map and it worked for him)...

I got a new error now when i tried to dobble click on the runserver.py file, (i usualy start it from the terminal).
IDEL´s Subprocess didn´t make connection. Either IDLE can´t start a subprocess or personal Firewall software is blocking the connection.
I looked at the firewall on the my MAC computer and is turned off....


DST-381: CYA page updates

Changes made to CYA page:

[x] Include visually hidden text for screen readers
[x] Add Other Addresses in Supply Chain
[x] Update supplier/end user details

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.70%. Comparing base (d6a029d) to head (b0a42a9).
Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #91   +/-   ##
=======================================
  Coverage   71.70%   71.70%
=======================================
  Files          50       50
  Lines        1336     1336
=======================================
  Hits          958      958
  Misses        378      378

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


Add Colégio Vitória Régia from file

@marcosvieirajr First stage of verification passed, official domain for Colégio Vitória Régia is vitoriaregia.net as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

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


Feature/multi pull secrets

adds the feature to use multiple pull-secrets from the k8s pods
additionally there is a possibility to specify a particular pull secret that is used in case all pull secrets from the pods are failing (the global custom pull secret must be in the same namespace as the sbom-operator itself)

@derkoe can you also please take a look at my implementation
it at least works in our OCP Clusters


add support for fetch timeout control for node_helpers, fix timeouts on armv6l

user reporting slow/no connection/timeout errors on armv6l for calendar, and newsfeed
we can increase the timeout by adding calls to the undici lib, but it requires node 20.18.1 or above.
this adds the support for timeout
(also environment variable to override if needed,, mmFetchTimeout (default 30 seconds)
and updates the base node version

Warn: package-lock
integrity/resolve missing

for changing the built-in node fetch timeout we have to add the whole undici http client as dependency?
I would prefer a simpler solutions e.g. adding env var --network-family-autoselection-attempt-timeout (untestet)

no idea what this drags in
const { setGlobalDispatcher, Agent } = require("undici");

/!\ resolve and integrity are removed from package-lock.json
For information it's allows to download each libraries from an compressed file
Without it, MagicMiror deps will take many many Time for installing

@bugsounet  I don't know what you are telling me..  git says there are two lines changed in package.json
systeminfo(changed version)  and undici (added)
after I changed, I erased package-lock.json , and did a new npm install  to get the latest

@sdetweil how did you test this? With an arm v6 machine or can I simulate this some other way?

i tested on the armv6l that had the timeout error on both news and calendar and also on my amd64 machine.

what url did you use for testing/simulating?

the default config urls. on armv6l
and my google cal and default on my amd
i had hard coded it in calendar to
prove, news failed
thats why the question about fixing for any/all via app/whatever
then put this on the armv6, and both worked
and of course all the testcases e2e and electron

only way to simulate would be to create sone cpu sucker threads to cause delays . armv6 problem is small memory and slow processor handling swapping on sd card

i wonder if the guys 11 calendars failure would be fixed here

@sdetweil my question was only how I can test it, used this not working url now.
Your solution works, my tests with --network-family-autoselection-attempt-timeout does not work. The undici package is small, so I'm fine with merging this beside the package-lock.json problem.
If you look at the diffs of package-lock.json you removed many many lines like
			"resolved"<EMAIL_ADDRESS>			"integrity": "sha512-5vbUs2A98CC3g1AlOBdkBE0BMukkLjLIsMHAtuxg6Pt9dQXxYWdLKOf66v6c/vIqtNcgTMv0oGtddLdMuH9X6w==",

Don't know how you did it but this must be reverted before merge ...

@khassel  oh, how to test timeout
use this
https://httpbin.org/delay/10
the number is seconds of delay

If you look at the diffs of package-lock.json you removed many many lines like

I did  NOT "remove" anything
I see the resolved is missing on some, and the integrity value is different.. I just ran npm install with no package-lock, and no node_modules folder to generate a new one , this IS a different node version..
npm install (not install-mm) on my amd64 is blazing fast,  <30 seconds total

I did NOT "remove" anything

look at the diff

@khassel I saw the diff.. but I didn't DO it on purpose.. just npm install

seems to be a npm issue, maybe this helps: https://github.com/npm/cli/issues/4263#issuecomment-1173093952

I can npm install again without removing the files and it looks better..
pushed

Remove node_helper and do npm install again
Diff package-lock.json and see result.
Must be fine

package-lock.json did not change

I can't verify from my computer, sorry

I can't verify from my computer, sorry
I don't know what you are telling me

@sdetweil : verified it's ok for me :)


fix ActiveField input to merge options from child classes #16329

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
tba

Fixed issues
#16329

This probably breaks BC. And using array_merge_recursive() for merging configs is incorrect - it will give incorrect result if you try to override some settings. array_replace_recursive() or ArrayHelper::merge() should be used in this case.

Can't be applied as is as @rob006 mentioned. Closing.