@calcom/web:build: ERROR: command finished with error: command (/calcom/apps/web) yarn run build exited (129)

I'm following the (Advanced users) Build and Run Cal.com instructions and it is failing with the following error:
@calcom/prisma:build: Datasource "db": PostgreSQL database "cal", schema "public" at "database:5432"
@calcom/prisma:build:
@calcom/prisma:build: 280 migrations found in prisma/migrations
@calcom/prisma:build:
@calcom/prisma:build:
@calcom/prisma:build: No pending migrations to apply.
@calcom/prisma:build:
@calcom/prisma:build:
@calcom/embed-snippet:build: vite v4.5.2 building for production...
@calcom/embed-snippet:build: transforming...
@calcom/embed-snippet:build: ✓ 1 modules transformed.
@calcom/embed-snippet:build: rendering chunks...
@calcom/embed-snippet:build: computing gzip size...
@calcom/embed-snippet:build: dist/snippet.es.js  1.01 kB │ gzip: 0.58 kB
@calcom/embed-snippet:build: Entry module "src/index.ts" is using named and default exports together. Consumers of your bundle will have to use `snippet.default` to access the default export, which may not be what you want. Use `output.exports: "named"` to disable this warning.
@calcom/embed-snippet:build: dist/snippet.umd.js  0.89 kB │ gzip: 0.57 kB
@calcom/embed-snippet:build: ✓ built in 475ms
@calcom/embed-react:build: cache miss, executing 837577fb135532b8
@calcom/embed-react:build: vite v4.5.2 building for production...
@calcom/embed-react:build: transforming...
@calcom/embed-react:build: src/index.ts (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
@calcom/embed-react:build: src/index.ts (1:0) Module level directives cause errors when bundled, "use client" in "src/index.ts" was ignored.
@calcom/embed-react:build: src/Cal.tsx (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
@calcom/embed-react:build: src/Cal.tsx (1:0) Module level directives cause errors when bundled, "use client" in "src/Cal.tsx" was ignored.
@calcom/embed-react:build: src/useEmbed.ts (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
@calcom/embed-react:build: src/useEmbed.ts (1:0) Module level directives cause errors when bundled, "use client" in "src/useEmbed.ts" was ignored.
@calcom/embed-react:build: ✓ 13 modules transformed.
@calcom/embed-react:build: rendering chunks...
@calcom/embed-react:build: computing gzip size...
@calcom/embed-react:build: dist/Cal.es.js  23.13 kB │ gzip: 7.11 kB
@calcom/embed-react:build: dist/Cal.umd.js  15.13 kB │ gzip: 6.07 kB
@calcom/embed-react:build: ✓ built in 1.31s
@calcom/web:build: cache miss, executing 63907efcef44d90f
@calcom/web:build: warn  EMAIL_FROM environment variable is not set, this may indicate mailing is currently disabled. Please refer to the .env.example file.
@calcom/web:build: Duplicate value found in common.json keys:   seats_available_other and seats_available_one
@calcom/web:build: Duplicate value found in common.json keys:   location_variable and location
@calcom/web:build: Duplicate value found in common.json keys:   additional_notes_variable and additional_notes
@calcom/web:build: Duplicate value found in common.json keys:   already_have_account and already_have_an_account
@calcom/web:build: Duplicate value found in common.json keys:   timezone_variable and timezone
@calcom/web:build: Duplicate value found in common.json keys:   scheduling_for_your_team and workflow_automation
@calcom/web:build: Duplicate value found in common.json keys:   saml_sso and saml_config
@calcom/web:build: Duplicate value found in common.json keys:   advanced_managed_events_description and unified_billing_description
@calcom/web:build: Duplicate value found in common.json keys:   email_team_invite|subject|invited_to_subteam and user_invited_you_to_subteam
@calcom/web:build: Duplicate value found in common.json keys:   email_team_invite|heading|invited_to_regular_team and email_no_user_invite_heading_team
@calcom/web:build: Duplicate value found in common.json keys:   email_team_invite|content|invited_to_regular_team and email_user_invite_subheading_team
@calcom/web:build: Duplicate value found in common.json keys:   create_an_out_of_office and ooo_create_entry_modal
@calcom/web:build: Attention: Next.js now collects completely anonymous telemetry regarding usage.
@calcom/web:build: This information is used to shape Next.js' roadmap and prioritize features.
@calcom/web:build: You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
@calcom/web:build: https://nextjs.org/telemetry
@calcom/web:build:
@calcom/web:build:    Creating an optimized production build ...
@calcom/web:build: <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (836kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
@calcom/web:build: Browserslist: caniuse-lite is outdated. Please run:
@calcom/web:build:   npx update-browserslist-db@latest
@calcom/web:build:   Why you should do it regularly: https://github.com/browserslist/update-db#readme
@calcom/web:build: Browserslist: caniuse-lite is outdated.  Does anyone have any suggestions regarding how I could further debug or fix this?

same error

I have tried again with version 4.0.0 and I still have this error.
Also I outputted the results to a TXT file and then grepped for error, omitting YN0013 and these results were returned, I don't know if this is relevant?
grep -i error ~/tmp/update.txt | grep -v YN0013
➤ YN0002: │ @calcom/ee@workspace:packages/features/ee doesn't provide react (p8fe64), requested by @hookform/error-message
➤ YN0002: │ @calcom/ee@workspace:packages/features/ee doesn't provide react-dom (p0eda1), requested by @hookform/error-message
➤ YN0002: │ @calcom/ee@workspace:packages/features/ee doesn't provide react-hook-form (pb317e), requested by @hookform/error-message
Error adding google credentials to DB: Unexpected end of JSON input
@calcom/embed-react:build: src/index.ts (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
@calcom/embed-react:build: src/index.ts (1:0) Module level directives cause errors when bundled, "use client" in "src/index.ts" was ignored.
@calcom/embed-react:build: src/Cal.tsx (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
@calcom/embed-react:build: src/Cal.tsx (1:0) Module level directives cause errors when bundled, "use client" in "src/Cal.tsx" was ignored.
@calcom/embed-react:build: src/useEmbed.ts (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
@calcom/embed-react:build: src/useEmbed.ts (1:0) Module level directives cause errors when bundled, "use client" in "src/useEmbed.ts" was ignored.
@calcom/web:build: ERROR: command finished with error: command (/calcom/apps/web) yarn run build exited (129)
 ERROR  run failed: command  exited (129)

I just tried again with version 4.0.1 and it failed in the same manner:
@calcom/web:build:    Creating an optimized production build ...
@calcom/web:build: <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (836kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
@calcom/web:build: Browserslist: caniuse-lite is outdated. Please run:
@calcom/web:build:   npx update-browserslist-db@latest
@calcom/web:build:   Why you should do it regularly: https://github.com/browserslist/update-db#readme
@calcom/web:build: Browserslist: caniuse-lite is outdated. Please run:
@calcom/web:build:   npx browserslist@latest --update-db
@calcom/web:build:   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
@calcom/web:build: ERROR: command finished with error: command (/calcom/apps/web) yarn run build exited (129)
command (/calcom/apps/web) yarn run build exited (129)

 Tasks:    6 successful, 7 total
Cached:    0 cached, 7 total
  Time:    13m35.743s
Failed:    @calcom/web#build

 ERROR  run failed: command  exited (129)
The command '/bin/sh -c yarn turbo run build --filter=@calcom/web' returned a non-zero code: 129

Is there anything I can do to help debug this issue?

I have tried again with version 4.0.2 and there is still the same error:
@calcom/web:build: warn  EMAIL_FROM environment variable is not set, this may indicate mailing is currently disabled. Please refer to the .env.example file.
@calcom/web:build: Duplicate value found in common.json keys:   seats_available_other and seats_available_one
@calcom/web:build: Duplicate value found in common.json keys:   location_variable and location
@calcom/web:build: Duplicate value found in common.json keys:   additional_notes_variable and additional_notes
@calcom/web:build: Duplicate value found in common.json keys:   already_have_account and already_have_an_account
@calcom/web:build: Duplicate value found in common.json keys:   timezone_variable and timezone
@calcom/web:build: Duplicate value found in common.json keys:   scheduling_for_your_team and workflow_automation
@calcom/web:build: Duplicate value found in common.json keys:   saml_sso and saml_config
@calcom/web:build: Duplicate value found in common.json keys:   advanced_managed_events_description and unified_billing_description
@calcom/web:build: Duplicate value found in common.json keys:   email_team_invite|subject|invited_to_subteam and user_invited_you_to_subteam
@calcom/web:build: Duplicate value found in common.json keys:   email_team_invite|heading|invited_to_regular_team and email_no_user_invite_heading_team
@calcom/web:build: Duplicate value found in common.json keys:   email_team_invite|content|invited_to_regular_team and email_user_invite_subheading_team
@calcom/web:build: Duplicate value found in common.json keys:   create_an_out_of_office and ooo_create_entry_modal
@calcom/web:build: Attention: Next.js now collects completely anonymous telemetry regarding usage.
@calcom/web:build: This information is used to shape Next.js' roadmap and prioritize features.
@calcom/web:build: You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
@calcom/web:build: https://nextjs.org/telemetry
@calcom/web:build:
@calcom/web:build:    Creating an optimized production build ...
@calcom/web:build: <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (836kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
@calcom/web:build: Browserslist: caniuse-lite is outdated. Please run:
@calcom/web:build:   npx update-browserslist-db@latest
@calcom/web:build:   Why you should do it regularly: https://github.com/browserslist/update-db#readme
@calcom/web:build: Browserslist: caniuse-lite is outdated. Please run:
@calcom/web:build:   npx browserslist@latest --update-db
@calcom/web:build:   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
@calcom/web:build: ERROR: command finished with error: command (/calcom/apps/web) yarn run build exited (129)
command (/calcom/apps/web) yarn run build exited (129)

 Tasks:    6 successful, 7 total
Cached:    0 cached, 7 total
  Time:    13m25.699s
Failed:    @calcom/web#build

 ERROR  run failed: command  exited (129)
The command '/bin/sh -c yarn turbo run build --filter=@calcom/web' returned a non-zero code: 129

Does anyone know if this is fixable or if there is anything I can do to help debug this issue?

Thanks to the suggestion here I have it working, closing -- the server did have 3GiB of RAM, I shut it down, allocated 32GiB and the build worked.


Add option to switch tab close button to the left side

Like Safari.

We were thinking about it: https://github.com/atom/one-dark-ui/pull/95
It got closed with: ...wait for 2.0 where "breaking" changes are more ok.
But that was a while ago and we might can reconsider since there aren't any plans for 2.0 yet.

I was just reviewing the comments from #95—including mine. Since that time, I think I land squarely on the "native experience" side of the argument for this particular issue.
Considering the idea "muscle memory," I develop solely on a Mac, so I expect the close icon to be on the left side—that's where it is for everything else, and that's where my muscle memory takes me (when I use the mouse). Any app that doesn't do that (i.e., Chrome) calls attention to itself.
For "consistency across platforms," I think there's a certain amount of context to consider. No app exists entirely on its own. It lives in an environment created by the operating system it runs on. That operating system defines rules and sets expectations for its users. Apps that don't follow those rules or meet those expectations feel out-of-place.
Because of this, I think it's possible to draw a line between what should be consistent across platforms and what should be consistent to a platform. To that end, I humbly endorse an option to place the close button on the left side, please. :pray: :smile:
But, if it doesn't make it in, I've lived with it this long because the beauty and aesthetic of the rest of the theme are more valuable to me than the location of the close tab button.

I humbly endorse an option to place the close button on the left side, please. 🙏 😄

Ok, one can't say no to being asked that politely. :smile: There is now a PR #253 that should be available in Atom 1.27.


TLPBot Test

This is a test and should be ignored.

Can't... ignore... must... comment. (Can I close this or do you need it still?)

testing

testing

fun fun

do soemthing robot.

Getting there....

this is making me a tad aggro

more testing.

blah

Ok, test more.

lol testing.

asdf

asdf

wtf?

que?

closer?

not really.

right meow.

grrr

what what?!


FIX: for event_type: "posting" cased problems

#3 Agent event type is posting leads to NonType bug.

Hey, I've found that event is of type posting that causes problems. Fell free to contact me when you encounter new problems : ).


[CWS] Introduce CWS K8S User Session tracking context

What does this PR do?

This PR introduces a User Sesison resolver for CWS (see below for an exaplaination about what it is, and why we introduced it). This new resolver is made of 3 different parts:

An admission mutating webhook that instruments both the pod creation and pod execution events:

During the pod creation, the mutation webhook will introduce a new volume (called datadog-cws-instrumentation) and a mount points to this volume in all the containers of the pod. It will also introduce a new init container with a mount point to the same volume. On init, this container will copy cws-injector (see below) to the volume.
During the pod execution, the mutating webhook will override the command to first call cws-injector with the K8S context as argument, and then the user command.

cws-injector is a new command in /cmd which is called (thanks to the previous step) before any command is run in an instrumented pod. This binary will forward the k8s context it received as argument to the CWS agent using an eRPC call.
the User Session resolver, which contains all the required logic in CWS to receive the k8s context from an eRPC call, integrate it in the process context recorded by CWS, and add business logic to it (i.e. the ability to write rules for it).

sequenceDiagram
    autonumber
    participant D as Dev1
    participant API as API server
    participant AC as CWS Admission Controller
    participant C as Container1
    participant CWS as CWS agent
    API->>+AC: A new deployment is scheduled
    Note left of AC: A new volume is mounted in
all containers
    Note left of AC: An init container is added to inject
`cws-injector` in the volume
    AC-->>-API: OK
    D->>+API: kubectl exec bash
    API->>+AC: "Dev1" wants to run "bash"
in "Container1"
    Note left of AC: "bash" is replaced with
"/cws/cws-injector {credentials} bash"
    AC-->>-API: OK
    API->>+C: "/cws/cws-injector {credentials} bash"
    activate C
    C->>+CWS: eRPC: store {credentials}
for current session
    CWS-->>C: OK
    C->>C: exec "bash"
    C-->>D: Interractive session opened
    Note over D,C: User session
    D->>C: exit
    Note left of CWS: session {credentials}
cleared
    C-->>D: OK
    deactivate C
    deactivate CWS
    deactivate API

Motivation

Currently, when CWS events are emitted, only the host user is reported (i.e. root or local Unix users). Although this is an interesting piece of context for services or applications that might run as privileged users, it doesn't really help understand what's happening when a developer or sysadmin run commands in production remotely. These commands are usually flagged by our default rules, and the lack of context make them harder to investigate. For Kubernetes environment, this PR introduces an additional piece of context for these events: the content of the v1.UserInfo structure. When Kubernetes is properly configured, CWS events will now contain the K8s username, UID and groups of the user that ran the commands remotely.
Additional Notes

For now, the cws-injector image is stored in Dockerhub, but if this feature gets more traction, we will publish the image to more image registry.
We currently do not support "existing" containers, the CWS instrumentation will only work for workloads that are scheduled after the Datadog agent is deployed.
This feature should be considered experimental and exploratory for now. It doesn't deserve a changelog.

Describe how to test/QA your changes

To QA this feature:

add the following CWS rule to an agent deployed in a K8S cluster:

 - id: user_session_test
   expression: exec.user_session.k8s_username != ""

Deploy a pod in the cluster
Run kubectl exec your_pod -- bash

You should have generated a CWS event with your K8S user context.
Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[x] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[x] If applicable, the need-change/operator and need-change/helm labels have been applied.
[x] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[x] If applicable, the config template has been updated.

What's preventing a user from using the cws-injector to inject fabricated userinfo data?

What's preventing a user from using the cws-injector to inject fabricated userinfo data?

Good question ! This: https://github.com/DataDog/datadog-agent/blob/3b12c10fad7a6505d1b7f897cc8c460c374ac1a4/pkg/security/ebpf/c/include/helpers/user_sessions.h#L21-L28


Added symlinks for Busybox utils

This adds symlinks to the busybox image for Windows. It makes the use of busybox in Dockerfile contexts work on Windows.

LGTM.


LISTEN/NOTIFY support

I’m wondering if this library supports listen/notify or if it needs to be adapted slightly to. Any suggestions on the best approach on getting it working? I’ve used pg-notify in node and may need to port it for deno use if nothing exists yet.

Hey @ddibiase, there is not LISTEN/NOTIFY support yet, but it's on my roadmap. I expect it should land during next month or two. Feel free to contribute!

I'd be happy to contribute as I need to solve this for my side project. Would you mind giving some direction on how you'd like it implemented? I was considering porting andywer/pg-listen for Node. It's TS and very well written with a lot of nice features.
It has an dependencies on EventEmitter, TypedEventEmitter, pg and pg-format that could be replaced with simple alternatives. pg-format could actually be ported relatively easily.
Any thoughts?

@ddibiase yes please!

I made one pass reading pg-listen - I'll keep you posted today, this is something we definitely want to support. Functionality itself is pretty straight-forward, but we need to improve testing for this project, so it'd be good if there was a thorough test suite.

Sorry for the delay, I had to sit on this thing for a while. I hope to post a PR this week with prototype for this functionality.

I tried to give this a go, but it seems a bit hard given the architecture of deno-postgres: it only does readMessage() when expecting something, and from a bunch of different places.
This is in contrast to e.g. ts-postgres which has a single central message reader that's always open to accept messages.
Not sure how to adapt it to the notifications. Tips welcome.

@jakajancar to be honest I haven't really put much thought about this issue since it was opened. It is very likely that supporting listen/notify will require to rewrite significant parts of this lib.
That said, I'm open to such changes if we could discuss them first.


Flux version not shown

Describe the bug
Whenever I access the Dashboard with a user that only has access to a single Namespace, this is what the footer shows:

The Flux version isn't shown, instead it reads -.
Environment

Weave-Gitops Version: 0.22.0
Flux Version: 2.0.0-rc.1
Kubernetes version: 1.27.1

To Reproduce
Steps to reproduce the behavior:
Access the Dashboard with a user that only has access to a single Namespace.
Expected behavior
The Flux version is shown. Alternatively show a message that tells me why I can't see the Flux version.
Actual Behavior
It just shows -.

We don't support v2.0.0-rc.1 of Flux yet so that's the reason it's falling back to -.
Maybe we should have used "Unsupported version" or whatever instead.

Updated the description accordingly.

Another data point to note is that the Flux Runtime page is very able to show the Flux version (when the user has the necessary permission) whereas the footer is not so it looks like it is generally possible:

I have the same problem. This is my setup.
$ flux version
flux: v2.0.1
helm-controller: v0.35.0
image-automation-controller: v0.35.0
image-reflector-controller: v0.29.1
kustomize-controller: v1.0.1
notification-controller: v1.0.0
source-controller: v1.0.1

$ gitops version
Current Version: 0.28.0
GitCommit: 3ad24e719c66f01efa755072476e3aa5efb3e1c9
BuildTime: 2023-07-19T18:04:30Z
Branch: releases/v0.28.0


⚠ Bofrost.be has degraded performance

In fafcb67, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 985 ms

Resolved: Bofrost.be performance has improved in cbc68a2 after 18 minutes.


Updated MAINTAINERS.md format.

Coming from https://github.com/opensearch-project/.github/issues/121, updated MAINTAINERS.md to match opensearch-project recommended format.

@lezzago Can we get a second PR here and merge this pls?


Bug: Claiming future auctions allowed

Bug
It's possible to call the claim function on future auctions before they have been started.
Because of the default values of the Auction struct, namely the status (Active), endTime (0), and tokenCount(0), it's possible for a malicious user to brick future auctions with the claim function.
This bug means that it's possible to permanently prevent certain tokenIds from being auctioned in the future if they have been used to set up an auction that has already been claimed.
File: src/EnsAuctions.sol
257:     function claim(uint256 auctionId) external {
258:         Auction storage auction = auctions[auctionId];
259:
260:         if (auction.status != Status.Active) revert InvalidStatus();
261:         if (block.timestamp < auction.endTime) revert AuctionNotEnded();
262:
263:         auction.status = Status.Claimed;
264:
265:         balances[auction.seller] += auction.highestBid;
266:         ++sellers[auction.seller].totalSold;
267:
268:         emit Claimed(auctionId, auction.highestBidder);
269:
270:         _transferTokens(auction);
271:     }

Proof of Concept
Consult the added test in this pull request that demonstrates the bug.
Mitigation
Consider checking whether there are any outstanding bids in in the claim() function, and reverting if not.
Alternatively, consider adding an additional status PreAuction, and setting the relevant auction status to Active in startAuction() function.

Nice


iosdk -h not recognized

ᐅ  iosdk -h
iosdk: error: unknown short flag '-h', try --help

Default for "GNU style" command is not using -h, will add this

done


[bug]: AlertDialog does not come up on trigger click when in full screen mode of browser

Describe the bug
In a scenario where the browser is in full screen mode, triggering the alert dialog box does not do anything and causes unresponsiveness. but when in normal mode, the dialog works all fine.
Apparently the dialog is getting rendered in DOM but is not showing up on the screen. Attaching a screenshot for reference

Affected component/components
AlertDialog
How to reproduce
Go to full screen mode of browser
Try to trigger the AlertDialog box
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Browser Brave Version 1.65.114 Chromium: 124.0.6367.60 (Official Build) (arm64)
Mac Sonoma 14.4.1

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

should've mentioned this before but i tried change z-index to a higher value but no luck

looks like an issue with some other package, closing for now


Implement proper MIPS microAptiv CPU initialization

Read the document listed below and try to merge following functionality with kernel startup routine:

init_caches.S
init_cp0.S
init_gpr.S
init_tlb.S

Boot-MIPS: Example Boot Code for MIPS® Cores
Look at the files in M14Kc directory for reference. Note that microAptiv is superset of M14Kc architecture.

Please DO NOT copy the code from Boot-MIPS examples as their licensing is very restrictive:

This code is confidential and proprietary to MIPS Technologies, Inc. ("MIPS Technologies") and
may be disclosed only as permitted in writing by MIPS Technologies or an authorized third party.
Any copying, reproducing, modifying, use or disclosure of this code (in whole or in part) that is
not expressly permitted in writing by MIPS Technologies or an authorized third party is strictly
prohibited. At a minimum, this code is protected under trade secret, unfair competition, and
copyright laws. Violations thereof may result in criminal penalties and fines.


Compile error if you use dotenv in gatsby-config file

Overview
After I install this plugin, and import the addToMailchimp function into a component, the site will fail to compile.
Reproduction Steps

Install this plugin
Import import addToMailchimp from 'gatsby-plugin-mailchimp'; into a component

IF your gatsby-config.js file imports dotenv because you are using environment variables, the command yarn develop will fail with the following error:
 ERROR  Failed to compile with 2 errors                                                                                08:39:41

This dependency was not found:

* fs in ./gatsby-config.js, ./~/dotenv/lib/main.js

To install it, you can run: npm install --save fs
 WAIT  Compiling...                                                                                08:39:41

 ERROR  Failed to compile with 2 errors                                                                                08:39:42

This dependency was not found:

* fs in ./gatsby-config.js, ./~/dotenv/lib/main.js

To install it, you can run: npm install --save fs

Here is the line in my gatsby-config, where if I comment it out then build will then work.
const dotenv = require('dotenv').config({ path: '.env.gatsby' });

I believe this may be related to #9  (and fixed) once PR #10 is merged.

looking into this.

Add this to your gatsby-node.js file
exports.onCreateWebpackConfig = ({ actions }) => {
  actions.setWebpackConfig({
    node : {
      fs : "empty"
    }
  })
};

That fixes the error. What is the underlying issue I wonder?

Seeing this issue as well. Tried the snippet that @ytwguru shared above, but that didn't do the trick for me. Will update if I find another fix.

https://github.com/benjaminhoffman/gatsby-plugin-mailchimp/pull/10 is merged, which I am hoping takes care of this issue.  i'm going to deploy a new version of this plugin so please upgrade to ensure this fix works!  thank you.  🙏
closing issue for now.  please re-open if it's still not working.  thx


Update branding to 5.0.0-alpha1

This is blocked until we branch for preview8

We'll still target netcoreap3.0 in the mean time even though we're updating our branding right?

We'll still target netcoreap3.0 in the mean time even though we're updating our branding right?

Initially yes.

Separately the validation builds got further but lots of references changed and it appears some tests are looking for our "3.0" packages still.

Two classes of problems:

Tests assuming package version equals the TFM version
Removed baseline package references

I'm still looking at 1. For 2., I'm adding the overrides for now but the proper way to do this is to update the baseline.

Seems like for 1. the work will be a little more involved than I anticipated. I'm disabling the tests right now to unblock but it will need followup to re-enable again.

I think all the issues have been fixed. The test failure looks to be a flaky SignalR test.

Hmm this is the second build in a row that's hanging, in a separate job though. I'm wondering if it's coincidence or there's an actual problem at this point.


Tests/examples for non-threaded Charm++ programs using Isomalloc

Original issue: https://charm.cs.illinois.edu/redmine/issues/1972

~~https://charm.cs.illinois.edu/gerrit/4472~~ https://github.com/UIUC-PPL/charm/commit/730f7c25a216c1d4cb69693dc9153cc9bda7db72 adds support for arbitrary Isomalloc contexts. We should have tests and examples for this feature.

Original date: 2018-09-07 18:41:21

We also need to document the interface in the manual somewhere too, once we have tests and examples.

The patch in question was merged because it included cleanup that seemed to resolve an issue, but the API was not fully sanitized for real use in practice. My refactoring will remove the entirely arbitrary contexts that the lack of testing applies to.


Database Schema

Database Schema
Description
As a developer, it would be useful to discuss and decide what our database is going to need to store, and then create it.
Acceptance Criteria

Discussion about database
Approach (EF Code First?  Database first?)
Implement

A brief note about the Approach -- basically, I'm suggesting we need to discuss whether we're going to:

Use C# code with EntityFramework to set up our database.
Set up our Postgres database, then open it with EntityFramework.

I lean towards 1, I think it would be easier.

We decided to take the code first approach.
This is now being blocked by #10.  We need to host a database.
Although, we could just each have a locally hosted postgres server and progress on this.
We also decided that we want businesses to be able to customize the attributes their inventory tracks.


Uno: Cannot play two Wild +4 cards in a row

If you play Wild +4 card draw, pick color you don't have, and then Wild +4 card draw again, the game will reject it, even if you don't have any other card options. This is because top card color is Wild which means game sees "alternative" ways to play other than than Wild +4 card.
I mostly put this bug as a reminder for myself.

my bad, oversight from my commit


Added property DoAllowEmptyTables to interface IExcelDataReader

Added property DoAllowEmptyTables to interfaces IExcelDataReader in all
projects. Tests have been added. If the property is set also empty sheets will be returned.
The new behaviour is only activated when the property is set to true.
Therefore there should be no side-effects if not activated.
The feature is added to fix issues related to
https://github.com/ExcelDataReader/ExcelDataReader/issues/131
Note:
The new tests are "green". However, some tests are not working, but since one fails due to missing test file and these tests are not connected to my change at all, I strongly assume they had failed before my change already.

I don't think this is needed now that everything is included by default.

Yes, the current behavior always returns empty tables, so this PR can be closed. Although the idea itself is good; the ConfigureDataTable callback passed to AsDataSet() should specify an option to skip empty DataTables. PR welcome =)


Support a stop-word list when slugifying

It would be nice to be able to specify a list of common English words which add little to a slug, e.g.
>>> slugify('The quick brown fox jumps over the lazy dog', stopwords=['the'])
'quick-brown-fox-jumps-over-lazy-dog'

Sounds great. You can send a pull request for it, or wait till the next minor update.


Set up project with dependency management

Ant build and project layout in current form does not fit for usability. Need to migrate.
Proposal :

maven
gradle
grape (need to recognize)
buildr (need to recognize)
sbt (need to recognize)

Almost done in gradle, however it was hard to recreate project structure in other buildsystem. It could be impossible in maven.

Closed accidentally


PressableButtonExample needs polish or removal

Open PressableButtonExample scene and play in editor.
Look at Click Indicator cube and click mouse button or press gamepad button.
Observe no color cycling.
The buttons to the left look a bit wonky too and the scene lacks a description panel. We need to freshen this scene up or remove it from examples.

Ported from internal database.

It looked really bad before, but it's better than it was when this bug was filed.

We can delete this scene since everything here is already in HandInteractionExamples scene.

Closed via removal in #4523

Hm...actually bernadette and I found that scene useful for testing different configurations. Without that scene there's not great way to test different button sizes, etc. I would argue for bringing it back as a PressableButtonTest scene.

Thinking on it a bit more, while it's useful to have pressable button examples as separate scene, maybe the current form of the scene is not appropriate. Closing for now, we will open a separate issue if we feel need to have second pressable button scene to show different configurations.

Fixed in #4527


remove lingering reference to SSL certificates in README

Dang it, I knew I'd miss something :joy:

I also added my twitter link and adjusted @Mzack9999's to be consistent with everyone while I was editing the README. ❤


Changed Guava dependency from 18.0 to 14.0.1 to make it compatible with Apache Spark

Apache Spark provides already a previous version of the Google Guava library. This makes the two tools difficult to integrate (cfr. this StackOverflow question).
In this version of the repo I changed the Guava dependency and adjusted the rest of the code accordingly.
I know that switching to a previous version of a library is normally not a good idea, so I understand if you don't accept my pull request.
Hope this helps.

Hrm. We use this library in other places where newer (latest) Guava is used.
Guava 14 is from 2013. Imo Spark is the problem, it should be updated.
It's difficult with Guava because they do remove deprecated functionality quite quickly.
So either way, 14 or 19 or whatever, will cause problems for someone.
I believe that it's best for a library like this one to go with the latest dependency version. And if someone has specific requirements, like you, they must find a solution. Sometimes an exclude in Maven can do the trick, so that your version of Guava is used. Otherwise your custom version/branch works.
At this point I don't see how to get rid of Guava. Internal functionality could be copy/pasted into the code. But the Optional class is in the interfaces. If we required Java 8 we could switch to the JDK Optional, but for me that's too early.

No worries, I totally understand and I was surprises to see that Spark is using (and providing) such an old version of Guava.
Anyway, if you or any of your users needs to use it with spark here is the code ;)
Cheers!


Create a performance profiling script to be run before and after performance improvements

Rough outline of the performance profiling script:

The script will submit POSTs to the WMG API of a deployed environment, requiring the user to specify the backend API URL as an argument.
The script will iterate through a number of different queries (e.g. gene sets of increasing sizes, compare on/off, etc)
The script will parse the response header for the server timings and output the results.
The script will have the capacity to execute requests serially or in parallel (controlled by an optional input flag)

Here are the following test cases:
For "Group By" in [None, Disease, Publication]:

1 gene
5 genes
10 genes
25 genes
50 genes
100 genes
200 genes

The genes should be sliced from a hardcoded list of 200 random genes to ensure reproducibility.
The parallel input flag accepts an integer N, default 1. If N>1, each test case is triggered N times concurrently.

@atarashansky - A couple of clarifications here:

I read the description as the script will run through all test cases (7 x 2 = 14). If we notice something odd about a particular test case and want to isolate that (ex: 25 genes with group-by disease), we won't be able to do that. Maybe that is ok but just want to call that out.
Clarification on parallelism here. Do you mean that if N = 5,

2A) it will run 5 concurrent requests of "1 gene" and after that is complete, it will trigger 5 concurrent requests of "5 genes" and after that is complete, it will trigger 5 concurrent requests of "10 genes", etc? OR
2B) it will trigger all 14 tests concurrently and run 5 trials of 14 concurrent requests?
I think you mean 2A but want to clarify here.


Narrow browser window bug

When you have a narrow window, you can scroll through the table to look at all the data but the header remains static. See attached image

Needs scrollX: true, adding to each of the table DataTable calls


Cursive_Table_View doesn't build with cursive

This setup in Cargo.toml doesn't work, I'm getting error saying that probably two versions of cursive_core are used:
[dependencies]
cursive = {git="https://github.com/gyscos/cursive.git",branch="main"}
cursive_table_view = "*"
Best Regards

Yeah it's not easy to combine git dependencies with dependencies from crates.io, since cargo isn't sure that they are compatible.
I think if you give a version to cursive in addition to the git value, it might help, but there's a chance you'll need to use the cursive from crates.io as well.
You might be able to patch the dependencies (see the documentation):
[dependencies]
cursive = "0.16"
cursive_table_view = "0.13"

[patch.crates-io]
cursive = {git="https://github.com/gyscos/cursive.git",branch="main"}

Haven't tested it though.

Yeah it's not easy to combine git dependencies with dependencies from crates.io, since cargo isn't sure that they are compatible.
I think if you give a version to cursive in addition to the git value, it might help, but there's a chance you'll need to use the cursive from crates.io as well.
You might be able to patch the dependencies (see the documentation):
[dependencies]
cursive = "0.16"
cursive_table_view = "0.13"

[patch.crates-io]
cursive = {git="https://github.com/gyscos/cursive.git",branch="main"}

Haven't tested it though.

Would the issue reported by me be sorted by this: https://github.com/gyscos/cursive/issues/536

Would the issue reported by me be sorted by this: https://github.com/gyscos/cursive/issues/536

I suppose indeed, publishing a new version of cursive_table_view compatible with cursive 0.16 may have fixed the issue.

I suppose indeed, publishing a new version of cursive_table_view compatible with cursive 0.16 may have fixed the issue.


fix(hotfix): preload modern resource in spa modern mode

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

@pi0 The audit error comes from v3.13.0 which has been fix in v3.13.0


Bug with time causes all tokens to be incorrect

I noticed a few days/weeks ago that all tokens generated by the Google Authenticator app were deemed invalid. None of the accounts/websites accepted the generated keys. Nothing obviously happened on my phone. I didn't reset it, didn't replace it with a new handheld or anything else.
After some fiddling around and changing the date/time settings and setting the checkbox on "Use 24-hour notation" in the Android settings the issue was resolved.
Apparantly the Authenticator app does not work properly anymore when the 24-hour vs am/pm notation is changed.
It is unclear to me why the 24-hour notation was changed into am/pm in the first place, as I prefer 24-hour notation. However, this could have been my kid fiddling around on my phone or I could have done it by accident.  But nevertheless, the Authenticator app shouldn't stop working after changing time display settings.
I believe this is a bug.

Having a similar issue with LG G3 Android 5.0
All tokens generated by the authenticator app for three different accounts are invalid.
When trying to use the time correction feature - the app crashes.

Having a similar issue on DASH JR K, Android 4.4.2  Switching the time to 24 hour notation didn't help.  Ended up using FreeOTP, which "just worked".

@oalders if it doesn't work at all, no matter what time notation you use, then your issue is most likely #4, unless you built Authenticator yourself from this repo.

@ThomasHabets thanks for this.  I'm using version 2.49 which I downloaded from the Play Store yesterday.  Do you know if the fix for #4 was shipped with that version?

@oalders I think it's not. But it will be in the next release.

Fix from #4 is in the app store version now. Reopen if you can reproduce this with the open source version.


internal/ui: Do not use the native fullscreen on macOS when the window is transparent

On transparent mode, the expectation is a kind of desktop applications on an existing space rather than an application in an independent space.

On transparent mode, the expectation is a kind of desktop applications on an existing space rather than an application in an independent space.

Now I'm not sure this is really true... Let's revisit if we find this is really needed...


gaps between app shared memory partitions can waste a lot of space

Describe the bug
On systems which require power-of-two size/alignment, we are not ordering the app shared memory partitions in an optimal way, which results in a lot of memory being wasted.
A good example is running the app memory size script from #14120 on the kernel produced by tests/subsys/jwt on mps2_an385, notice the huge gap in between z_libc_partition and k_mbedtls_partition:
$ python3 ~/projects/zephyr4/scripts/appmem_report.py zephyr/zephyr.elf
Userspace memory partition report:
Partition                     Total       Used        Wasted      Efficiency
----------------------------------------------------------------------------
ztest_mem_partition           0x40        0x34        0xc         81.25%
  gap 0x0
z_libc_partition              0x20        0x4         0x1c        12.50%
  gap 0x7fa0
k_mbedtls_partition           0x8000      0x7fe0      0x20        99.90%

total                         0x10000     0x8018      0x7fe8      50.04%

Ordering the app shared memory partitions in reverse order of total size should greatly reduce these gaps.
We don't know the full sizes of these partitions when gen_app_partitions.py runs since the zephyr_prebuilt.elf has not been linked yet, but since we are examining the individual object files we might be able to assemble a total anyway. Or we could somehow figure out a way to get the linker to reorganize these partitions for us, but that might require them being placed in individual sections.

If we try to solve this in gen_app_partitions.py, any solution for this will need to consider the memory used not only in .o files scanned, but libraries added via the --library option to gen_app_partitions.py

The linker has SORT_BY_ALIGNMENT which might allow us to sort the partitions at link time.  Just requires that each partition ends up in its own section.  Not sure what the implications or requirements in the linker script are related to that.
I know we need to keep the partitions together, that should be easy enough.  @ioannisg had some additional constraints we needed to ensure.
Maybe first step is just to get each partition in its own linker section and ensuring the proper constraints.

SORT_BY_ALIGNMENT can only be applied to input sections. With app shared memory, the sorting needs to be done to across different output sections. The issue is due to ARM's MPU alignment requirements, where a 64KB region must be aligned on 64KB. So k_mbedtls_partition in the description has to be aligned at 32KB since its partition is 32KB. Hence there is a big gap between z_libc_partition and k_mbedtls_partition because of all the padding.


feat: Add Web Extension Support

Description
This work-in-progress PR adds the ability for NaNofuzz to run in a VS code Web Extension host. The goal is for NaNofuzz to run inside GitHub CodeSpaces. Key point: web extension run in a browser web worker -- Node functionality is unavailable.
Implementation strategy and design decisions

Utilize typescript.transpileModule() to transpile Typescript user modules to Javascript on-demand while the IDE is running.  This makes for a simple transpiler that avoids calling tsc with the trade-off that transpilation is on a module-by-module basis, which is similar to tools like Babel.
Utilize vscode.workspace.fsfor all filesystem access rather than node's fs
Use web workers for running tests, which provide the ability to terminate runaway tasks.  Utilize a shim to abstract away important differences between browser WebWorkers and Node worker_threads
Similar to a browser, VS Code web extensions lack a module loader.  This is a problem as we need to load, transpile, and execute module code in the web extension at runtime: it's not possible to bundle the user's code in advance.  VS Code provides require as a global, but is simply a shim used to load the vscode api.  We will need to provide our own module loader that uses vscode.workspace.fs to access the filesystem and preserves VS Code's shim.

Open items

Add module loader for browser that uses vscode.workspace.fs to load user file inside the IDE workspace.
Add browser entrypoint and start testing inside the web extension host.
Improve performance.  Switching from vm to workers cost us speed due to message passing overhead.  Can likely address this by chunking work or managing a worker thread pool.
We should probably be nice and get ts options from the user's tsconfig, but this isn't necessary for the current research need.
The code needs comments and is messy in many places.

The CodeSpaces extension host runs in a Node container, so we no longer need this PR.


broken links - Inbound endpoint

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


Only play viewer join sounds when they send an initial message

To avoid putting people on the spot for joining the stream quietly update the bot to only play their join sound when they send their first message for that stream session

This could be an option in the JSON, so someone can have a sound effect, but only play the first time they say something in the channel.
e.g.
"joinSoundEffects": [
{ "themichaeljolley": "whocares" },
{ "roberttables": "hecc" },
{ "electrichavoc": "shock" },
{ "rhonin52": "swipe" },
{ "surlydev": "ohnoheishere", "style": "lurker" }
],

Optional configurable setting.
{ "lurkdetection" : "true" } - defaults to false


testNonRegression: Generate actual files on error

testNonRegression is insanely useful to write characterization tests and then maintain those tests as changes are made subsequently to the Jenkinsfile.
The point of this pull request is to add a feature that replaces the need to add this code to my test suites:
// uncomment the line below when you want to update the reference callstacks
//System.setProperty(RegressionTestHelper.PIPELINE_STACK_WRITE, "true");

...such that if the output of a run changes, I don't have to:

Temporarily un-comment the line
Re-run the test
Re-comment the line

I instead can fire up my diff tool and copy the changes from the newly-generated .actual file into the corresponding suite file (if I want to).
As a bonus, the "expected" file will now be written if one didn't exist before, instead of the corresponding test failing with a FileNotFoundException.
Please let me know if there are additional tests you would like me to write/run.
Thanks!

Thanks for this pr. We realized that issue after the release, but it was too late.
I’ll take a look as soon as I can.

Another simpler approach would be to add the following to your build.gradle file:
test {
    systemProperty "pipeline.stack.write", System.properties["pipeline.stack.write"]
}

Now if you run gradle -Dpipeline.stack.write=true cleanTest test it will rewrite the output since the property is getting passed from the gradle java process to the forked test process.  If you only want to refresh a subset of the tests add the --tests * flag limiting which tests you are going to run.

I would say, pipeline.stack.write is supposed to indicate whether the reference files must be written.
When you run the test and the reference file is different, we suggest to load the file.
I would rather suggest to check the file existence just before comparing it:
        assertThat(referenceFile.exists())
                .as('To initiate the callstack reference file, user JVM parameter -D%s=true', PIPELINE_STACK_WRITE)
                .isTrue()


Azure Container Apps are missing from this list in addition to other services.

[Enter feedback here]

Azure Container Apps are missing from this list.
Other services should also be listed here or at least there should be a link to these other services support to be able to be deployed into a vnet.

Perhaps you can explain the difference between depooying to vnet and only limiting traffic from the vnet using technologies like private link

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

ID: 2422f8ec-802e-7f92-c499-9181f3fe8d8b
Version Independent ID: eb2b0e2c-8fb5-573c-ef0d-50073d053c3d
Content: Virtual network for Azure services
Content Source: articles/virtual-network/virtual-network-for-azure-services.md
Service: virtual-network
GitHub Login: @mohnader
Microsoft Alias: mbender

Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.


New version: Mozilla.Firefox.DeveloperEdition.tl version 132.0 (132.0b4)

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

Verify by proxy: https://github.com/microsoft/winget-pkgs/pull/179431#issuecomment-2400690391


Apply URL Search params to releases page

Filters are now conjoined with the URL for deep linking (and also helps with load testing).

One thing I noticed, which I don't know is new with this PR or happened before too, but it "bounces up" to the top of the page and then scrolls back down for each filter change. Is there a way to avoid that?

@jakerainis while you're in here, would you mind updating the numeric spacers in use-pack-filter?
priceHigh: 50_000

☝🏼 this is misleading since this includes cents

@afraser That's 50,000 in whatever unit is the current one, which might be USD, SEK, or whatever the user configured. In addition, Dinero will handle the formatting of this, which in turn includes a currency definition and how many decimals should be used (i.e. what the exponent value is). I think it's fine to leave this as is.

Removed the scroll behavior as well.


vagrant: bump bpf-next vagrant box version

Pull in latest BPF kernel tree from bpf-next which contains extended
bpf_{get,set}sockopt() helper support for sock_addr programs [0].
[0] https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=bcd6f4a8bedabac6949d05e418e73a0a1b309e84
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=3218231dbb16cd85d94831759b6c78e6feb54b58
Signed-off-by: Daniel Borkmann<EMAIL_ADDRESS>

test-me-please

test-me-please

retest-net-next

retest-net-next


JOSS Review: Software Paper References

There is only a single reference. It does not fully support the claim (from the software paper) for the need of the library under review. Only big-math https://github.com/eobermuhlner/big-math is referenced currently.
"References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?"
Please include papers and/or repositories providing further evidence for claims.
Refers to JOSS Review: https://github.com/openjournals/joss-reviews/issues/4283

Would it be best to withdraw the submission, develop the Use Case (some Use Case Scenarios), and then resubmit to JOSS?


Ensure edmf consistency passes

This PR builds ontop of #1043 and removes the soft-fail so that we don't lose this test.

bors r+


Add sponsor link for VS IDE extensions

VS Code shows sponsor links for any extension that has been specified in its manifest file.

Please add one for VS extensions as well, but I suggest you do it on the publisher level, instead of the individual extension. Here's my idea.
Step 1
On the publisher profile, add a field where you can specify you sponsor URL, just like you can specify twitter account, GitHub profile etc. When a sponsor link is added, show the sponsor link next to every extension just like you do for VS Code. Also show the sponsor link on the publisher profile page.
Step 2
Add support for each individual extension to specify a sponsor link in its manifest file. If a publisher profile contains a sponsor link, the individual extension will override it with its own link. Step 2 is optional.

Yes add sponsors

We did not go with Step 1 for VS Code for several reasons; the step 2 is the reasonable solution to support sponsorship.
This need help from Tina's team, I will talk to her and put it on our todo list


Barratry update

About the PR

adds one chem dispenser board to chemistry
adds mindshield crate to armory
adds ninja bombing spots in engi, botany, bridge, armory, sec, hop, med, cargo and evac
Why / Balance

chemists are in pain
pretty sure ss13 has that and #20795
it wasnt there before

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl: JoeHammad

add: chem dispensers to barratry, you can stop crying now

Please fix your IDE so the diff isn't massive.

uhhhh i dont know hwo to do that or what that means

I am fine with the changes I just do not like the entire map diff, I need to find out why it did that

crlf

detroit gets something!? WOOO


../bosh-lite/bin/provision_cf fails

bosh target <IP_ADDRESS> lite
cd ..; git clone https://github.com/cloudfoundry/cf-release ; cd cf-release
../bosh-lite/bin/provision_cf

...
Submodule path 'src/loggregator/src/github.com/ugorji/go': checked out 'f1f1a805ed361a0e078bb537e4ea78cd37dcf065'
Submodule path 'src/smoke-tests': checked out 'eab961481c905718fe3624d05fd62ae803fbc3c0'
Submodule path 'src/statsd-injector': checked out 'e7152f1b153d9f7a0acc0720378b862278af821b'
Submodule path 'src/uaa-release': checked out '9be621523814a0fe03abb9118f6a6036e4f6345e'
Submodule path 'src/uaa-release/src/uaa': checked out '9b5c13d793ebfe358e26559cedc6b528a557b43f'
+ git clean -ffd
Removing latest-bosh-lite-stemcell-warden.tgz
+ set +x
CF Release has been updated
/Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/optionally_run_with_bundler.rb:22:in `write': Permission denied - /Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/run_bosh_with_bundler.Gemfile (Errno::EACCES)
	from /Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/optionally_run_with_bundler.rb:22:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/bosh:3:in `<top (required)>'
	from /usr/bin/bosh:23:in `load'
	from /usr/bin/bosh:23:in `<main>'
/Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/optionally_run_with_bundler.rb:22:in `write': Permission denied - /Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/run_bosh_with_bundler.Gemfile (Errno::EACCES)
	from /Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/optionally_run_with_bundler.rb:22:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/bosh_cli-1.3202.0/bin/bosh:3:in `<top (required)>'
	from /usr/bin/bosh:23:in `load'
	from /usr/bin/bosh:23:in `<main>'
Can only target Bosh Lite Director. Please use 'bosh target' before running this script.

I did run bosh target!

Those Permission denied errors look suspicious and sounds like https://github.com/cloudfoundry/bosh-lite/issues/316#issuecomment-161881325 where it was suggested to try locally removing BOSH_USE_BUNDLER from scripts/generate-bosh-lite-dev-manifest. Maybe give that a try?

Yes, I believe the gem install failed due to not enough permissions and I had to sudo it.

I tried that. It failed again:
Aborted. Please install spiff by following https://github.com/cloudfoundry-incubator/spiff#installation
Incorrect YAML structure in `/Users/mqm/git/cf-release/bosh-lite/deployments/cf.yml': expected Hash at the root

I just installed it, will try yet one more time.

You have to install the spiff binary and it has to be available in your path
https://github.com/cloudfoundry-incubator/spiff

...
  Started updating job loggregator_trafficcontroller_z1 > loggregator_trafficcontroller_z1/0 (57441685-c2cf-43e3-a897-6fbb581c9969). Done (00:00:15)
  Started updating job router_z1 > router_z1/0 (d14e672c-0d2d-4c91-821a-57eed059c123). Done (00:00:37)

Task 3 done

Started		2016-03-10 01:09:17 UTC
Finished	2016-03-10 01:56:43 UTC
Duration	00:47:26

Deployed `cf-warden' to `Bosh Lite Director'

(env) Marcio-Marchinis-MacBook-Pro-Silver:bosh-lite mqm$ !3743
cf api --skip-ssl-validation https://api.<IP_ADDRESS>.xip.io
Setting api endpoint to https://api.<IP_ADDRESS>.xip.io...
FAILED
Server error, status code: 404, error code: 0, message:

Is this the expected behaviour?

Is the domain property of your deployment manifest configured to be <IP_ADDRESS>.xip.io?

You might also want to try cf api --skip-ssl-validation https://api.bosh-lite.com instead - it looks like the domain defaults to bosh-lite.com in the sample manifest.

Closing due to inactivity.


[request]: Allow specifying the role session length for AssumeRoleProvider

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Tell us about your request
The ability to set the DurationSeconds field of the sts:AssumeRole request that AssumeRoleProvider makes behind the scenes.
Tell us about the problem you're trying to solve.
We're using an assumed role to presign s3:GetObject URLs, and we want to be able to control the length of time the URLs are valid for. Presigned URLs produced using temporary credentials are valid for the lesser of the signature validity period and the credential validity period, so using AssumeRoleProvider we can't produce any URLs that are valid for longer than 3600 seconds (the default validity period for sts:AssumeRole).
Are you currently working around this issue?
We can manually call sts:AssumeRole using aws-sdk-sts and then produce the signed URLs using aws-sig-auth, but it's not nearly as ergonomic.
Additional context
No response

This would be a useful feature 👍🏻
In the short term, you can workaround this while maintaining ergonomics by using sts::AssumeRole to implement ProvideCredentials. You can pass that in as a credentials provider, enabling you to use the normal flow with longer-lived creds. It is also probably a fairly small change here: https://github.com/awslabs/smithy-rs/blob/main/aws/rust-runtime/aws-config/src/sts/assume_role.rs and we'd be happy to mentor / accept a PR.

released in 0.10.1


python2 plugin cannot find pip2

python2 plugin cannot find pip2 during the parts phase building on xenial.
/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip2 does not exist,
but these
/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip
/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip3
/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip3.5
Note that my host does have pip 8.1.2 installed and it is pip2 as  the plugin assumes.
This failure happens after attempting to use the python3 plugin, which failed for a different reason.
Note I am surprised to see "Using /home/curtis/Work/DOTS/.local/lib/python2.7/site-packages".
Thinking this my download cache could be interfering with the snap, I unset the env var
unset PIP_DOWNLOAD_CACHE
but it continues to show up.
From snapcraft.yaml
parts:
find-text:
plugin: python2
source: src
$ snapcraft clean
$ snapcraft snap
...
Searching for pip
Best match: pip 8.1.2
Adding pip 8.1.2 to easy-install.pth file
Installing pip script to /home/curtis/Work/find-text/parts/find-text/install/usr/bin
Installing pip3.5 script to /home/curtis/Work/find-text/parts/find-text/install/usr/bin
Installing pip3 script to /home/curtis/Work/find-text/parts/find-text/install/usr/bin
Using /home/curtis/Work/DOTS/.local/lib/python2.7/site-packages
Processing dependencies for pip
Finished processing dependencies for pip
python2 /home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip2 install --global-option=build_ext --global-option=-I/home/curtis/Work/find-text/parts/find-text/install/usr/include/python2.7 --target /home/curtis/Work/find-text/parts/find-text/install/usr/lib/python2.7/site-packages .
python2: can't open file '/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip2': [Errno 2] No such file or directory
Command '['/bin/sh', '/tmp/tmp9bezb1oa', 'python2', '/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip2', 'install', '--global-option=build_ext', '--global-option=-I/home/curtis/Work/find-text/parts/find-text/install/usr/include/python2.7', '--target', '/home/curtis/Work/find-text/parts/find-text/install/usr/lib/python2.7/site-packages', '.']' returned non-zero exit status 2

Moving my ~/.pip dir out of the way does not fix the issue:
python2: can't open file '/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip2': [Errno 2] No such file or directory
$ ls /home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip*
/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip
/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip3
/home/curtis/Work/find-text/parts/find-text/install/usr/bin/pip3.5

Does this work for you now?

Yes this works thank you.


[CI] Try to fix sporadic docker-compose issues

Rationale for this change
The docker-compose utility is progressively being removed from GHA-provided runners:
https://github.com/actions/runner-images/issues/9557
What changes are included in this PR?
Use docker client CLI directly instead of docker-compose where possible.
Are these changes tested?
Yes, this should fix the sporadic CI failures because of the above migration.
Are there any user-facing changes?
No, except additional optional env var ARCHERY_DEBUG.

@github-actions crossbow submit -g nightly

@github-actions crossbow submit -g nightly

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g linux

@github-actions crossbow cuda

@github-actions crossbow submit cuda

@github-actions crossbow submit wheel312*

@raulcd @assignUser @kou Any further comments here? Otherwise it would be nice to merge this quickly.


Can we figure out what's wrong with ratings?

So my current progress on this is that noping 80054c50 I get 354116, @spotlightishere What does this error mean?
Anyway, by noping that address, I effectively removed the if statement on line 23 which says:
if (iVar == 0){
    SetNodeMissing(param3,somethingsomethingsomething);
}

Which makes me think that we have a missing node. Can anyone take a look at this?

I may look at this later this week with you and Spotlight, also, I made us a new PHP engine (Galvatron) SRC is private atm, read it's README for why.

Actually, it appears to be intentionally missing somehow, odd.

@zurgeg Well, I'll be darned, this is a weird thing Nintendo put in. It's not a missing node, Nintendo is literally setting a missing node ON purpose. Peculiar.

I don't know why they would. @larsenv Does Nintendo do this often? 🤔

@6100m Interesting, also ratings are working now :)

I'm gonna close this up as it's fixed. Wii had some invalid images.

Excellent :) I always wondered if those shapes were for ratings, now I know :)
I watched Nintendann's Wii No Ma video repedeatly a month before I joined the Rii No Ma team 😄


IDE flag overview and DISKINIT.EXE behavior

IDE flag overview
0000:0457h DA / UA 80h and 81h connection information
0000:055Dh DA / UA 80h to 83h information (upper 4bit is 640 kb I / F FDD DA / UA F0h to F3h)
0000:05BAh IDE connection information (CD-ROM is also counted) Setting with 3 IDE3 or more models that can be recognized?
F8E8:0005h Perhaps the model that can be recognized by more than three IDEs is Bit4 = 1b.
F8E8:0010h IDE connection information (CD-ROM is also counted) There is also software and drivers that also refer to this. Set with models that can be recognized more than 3 IDEs?
PC-98エミュを語ろう21
https://egg.5ch.net/test/read.cgi/software/1632474041/

Diskinit.exe does not work properly if the appropriate value is not set for 0000:0457H.
In the NP21 / W implementation, WINNTFIX=TRUE only sets the value to 0000:0457H when the IDE slave is not connected. Also, 0000:0457H is not written.
This action seems to avoid problems that occur with Windows 3.1 32-bit Disk Access, but the actuation with the actual machine is different.


Displaying the Flavor text with the mission

Displaying the Flavor text with the mission could give you a better idea of what mission you're going to play. As long as you didn't also give the full text for the rules alongside it, I should think that wouldn't be so bad.

https://www.reddit.com/r/shadowsofbrimstone/comments/7mptca/brimstone_random_mission_picker/drwijtw/


Use java 8 Optional instead of Guava for sharding-ui

Pull Request Test Coverage Report for Build 2048

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

Totals

Change from base Build 1033:
0.09%

Covered Lines:
12133

Relevant Lines:
20521

💛  - Coveralls


Fix the FFTW part of the Github Actions build

This requires that the latest Firedrake docker image be built with FFTW,
and then to fix the mpi4py_fft install in the asQ Actions build.

The FFT takes up a very small proportion of the runtime with scipy.fft. Updating to FFTW is not a priority at the moment. See runtime profile for scalar advection below.


How to get in touch regarding a security concern?

Hello 👋
I found a potential security issue in paly-with-docker, how can I get in touch with you in a private way and submit my security report?
Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.

:wave: thx for reporting. You can contact me at marcosnils (at) gmail.com for disclosure.
I'll add the security policies later this week, thx for mentioning it out!.

closed since this is addressed already. I'll publish the security advisory in a bit

@marcosnils Hi, is it still in progress ?

Hi! No, the security advisory has been published already https://github.com/play-with-docker/play-with-docker/security/advisories/GHSA-vq59-5x26-h639

@marcosnils Hi, the page is 404 for me. Did you add me as collaborator ?

Just added you.

@marcosnils  Could you assign a CVE id in that page? Only maintainers can do this.


Allow everyone to read or write a wiki by a repo unit setting

Replace #6312
Help #5833
Wiki solution for #639
Ready for review

There is some small UI nits but I don't whether it's affected by this PR.

Looks like I can view the code unit even if I have only wiki unit read/write permission.

Hmm .... it seems that the "access mode" package has something that I still misunderstood, will figure out.

Looks like I can view the code unit even if I have only wiki unit read/write permission.

Hmm .... it seems that the "access mode" package has something that I still misunderstood, will figure out.

I think it is a design problem in old code and the comment seems not right:
// HasAccess returns true if the current user has at least read access to any unit of this repository
func (p *Permission) HasAccess() bool {

Now I can somewhat understand that HasAccess is used for "code view" for many cases, these cases don't check "CanRead(Code)"
Correct me if I am wrong ..... (I am going to propose some more fixes)


Update FairStaking.toml

Previous PR :
https://github.com/anoma/namada-testnets/pull/342
https://github.com/anoma/namada-testnets/pull/464
https://github.com/anoma/namada-testnets/pull/1255 https://github.com/anoma/namada-testnets/pull/2032
Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[x] Only one toml is added in this PR
[x] The file being added is indeed a .toml file
[x] The toml being added is to the correct folder, and only to the correct folder
[x] The eth_hot_key and eth_cold_key are present
[x] The email, discord, elements telegram, and twitter fields are present and valid

Whitespace found in filename. Found filename namada-public-testnet-15/Update FairStaking.toml


Error: error during handshake: error on replay: validator set is nil in genesis and still empty after InitChain

Hello, I tried to run full node locally myself. Could you help me out?

It looks like it may have not downloaded the correct genesis file for some reason.   Are you using this docker-compose.yml?

Closing as this is definitely working now. @btfdip please try with the latest examples in the repo.


Check that archive node deb package works as expected

The only change that should be required here is that the archive node deb should list postgresql as a dependency.

@lk86 I wonder if @kaozenn can take this from you?

relates to #11976 specific for nix deb package

@mzajda0mina Why is this issue marked "Archived in project"? Is it done?

@robinbb is a duplicate of #11976

@robinbb hm, yes, I was not correct re the duplicate ticket number. I did it during standup, where a duplicate was pointed to me, but now I don't see it... I will re-check. I see also that I added the [nix-dep] prefix in the title. It means that it depends on NIX work. If we get NIX working the issue doesn't exist. The title is misleading, too. It's about PostgreSQL dependency and not  Archive node working state.
Re the archiving non-closed issue: it was my way to remove it from this dashboard and don't lose it forever. When I have better grip on the project I intend to move or delete non issues.

So, unless there is a duplicate issue identified, we should not archive this one because we might then lose track of it. If a duplicate issue is identified, we can close this one and mark it "Done".


type ArgMax cannot be converted

Hi , I meet a problem that my network has  an ArgMax operation what code is
x = keras.layers.Lambda(lambda x : tf.argmax(x, axis = 3,output_type=tf.float32))(x)

and
meet this problem:
node lambda_1/ArgMax of type ArgMax cannot be converted, fall back to tf2onnx
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/zhu/keras-onnx-1.6.5/keras2onnx/main.py", line 60, in convert_keras
    parse_graph(topology, tf_graph, target_opset, output_names, output_dict)
  File "/home/zhu/keras-onnx-1.6.5/keras2onnx/parser.py", line 794, in parse_graph
    graph, keras_node_dict, topo, top_level, output_names)
  File "/home/zhu/keras-onnx-1.6.5/keras2onnx/parser.py", line 595, in _parse_graph_core
    _on_parsing_tf_subgraph(graph, nodes, varset)
  File "/home/zhu/keras-onnx-1.6.5/keras2onnx/parser.py", line 335, in _on_parsing_tf_subgraph
    raise RuntimeError("Some tensorflow operation doesn't support, stop converting.")
RuntimeError: Some tensorflow operation doesn't support, stop converting.

How to solve this problem.
My keras is 2.1.5 keras-onnx-1.6.5 onnxruntime-1.7.0 tensorflow-1.14.0

Just checked in the fix, which should work for your case. Please pull keras2onnx master (not install from pypi) and try. Also please pull onnxconverter-common from master.
In your code you mentioned output_type=tf.float32), seems argmax only supports int32 or int64?
you mention onnxruntime-1.7.0? should be onnx-1.7 right? please use onnx 1.6 before onnxruntime 1.3 gets released.

Just checked in the fix, which should work for your case. Please pull keras2onnx master (not install from pypi) and try. Also please pull onnxconverter-common from master.
In your code you mentioned output_type=tf.float32), seems argmax only supports int32 or int64?
you mention onnxruntime-1.7.0? should be onnx-1.7 right? please use onnx 1.6 before onnxruntime 1.3 gets released.

Thank you very much and I retry one more time and can create a .onnx using the tf.argmax.


Why it does that
Briefly state why the change was necessary.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes # <-- insert Issue number if one exists

Codecov Report
Patch and project coverage have no change.

Comparison is base (722b523) 69.04% compared to head (d82ae27) 69.04%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #48   +/-   ##
=======================================
  Coverage   69.04%   69.04%
=======================================
  Files          26       26
  Lines         646      646
  Branches       22       22
=======================================
  Hits          446      446
  Misses        197      197
  Partials        3        3

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


Changed eventhandler action type to interface in order to permit exte…

…nsibility
This modification brings the ability to extend the current action types to custom ones.
Details: Implementing the newly created interface in an Enum.

@AlexVinogradov Please resolve build failures.

@apanicker-nflx Trying to find a solution for interface serialization with protobuf (so far not so lucky). Seems the newly introduced interface for the actions cannot be mapped by protobuf


Update Laravel integration

This pull request updates the Laravel integration and can be merged once issue #8 is resolved.

Added type declarations
Simplified the service provider
Suggested packages for Laravel
Ran tests against Laravel 11
Dropped support for Laravel 9 and 10
Updated the config file location

Normalizing the composer.json file using the ergebnis/composer-normalize package is another idea for the future.

Great! I'm all for keeping the dependencies lean and easy to handle, but its very narrow in this case – will need a minute to think about it.
PHP 8.3 however should definitely be included in the test matrix though and I'm thinking Laravel 10 also as it's technically not EOL?

Buttery fingers... Sorry browsed the wrong PR, accidentally closed. Reopened again.

Work continued in #12


issues met when debugging an x86_64 emulation process at the arm64 instruction-level

When we follow https://ffri.github.io/ProjectChampollion/appendix/ to debug at arm64 instruction-level debug, there are many strange issues, such as:

If a watchpoint is set, rosetta runtime will fail with "rosetta error: failed to allocate vm space for aot".  An example session follows:

lisa@jjl bt % lldb -- ./runner ./float
(lldb) target create "./runner"
Current executable set to '/Users/lisa/bt/runner' (arm64).
(lldb) settings set -- target.run-args  "./float"
(lldb) r
Process 9182 launched: '/Users/lisa/bt/runner' (arm64)
Process 9182 stopped
* thread #2, stop reason = exec
    frame #0: 0x00007ffdfffbc3ec runtime`_mh_execute_header + 17388
runtime`_mh_execute_header:
->  0x7ffdfffbc3ec <+17388>: mov    x19, sp
    0x7ffdfffbc3f0 <+17392>: and    sp, x19, #0xfffffffffffffff0
    0x7ffdfffbc3f4 <+17396>: mov    x29, sp
    0x7ffdfffbc3f8 <+17400>: ldr    x20, [x19, #0x20]
Target 0: (runtime) stopped.
(lldb) watchpoint set expression 0x7ffdfffbc3f0    ====> set a watchpoint that won't hit
Watchpoint created: Watchpoint 1: addr = 0x7ffdfffbc3f0 size = 8 state = enabled ...
    new value: -7998388550590730625
(lldb) c
Process 9182 resuming
rosetta error: failed to allocate vm space for aot   =========> will cause such failure
Process 9182 stopped
* thread #2, stop reason = signal SIGTRAP
    frame #0: 0x00007ffdfffd4d38 runtime`_mh_execute_header + 118072
runtime`_mh_execute_header:
->  0x7ffdfffd4d38 <+118072>: brk    #0x1
    0x7ffdfffd4d3c <+118076>: stp    x20, x19, [sp, #-0x20]!
    0x7ffdfffd4d40 <+118080>: stp    x29, x30, [sp, #0x10]
    0x7ffdfffd4d44 <+118084>: add    x29, sp, #0x10            ; =0x10
Target 0: (runtime) stopped.
(lldb)

command might struck. e.g.

isa@jjl bt % lldb -- ./runner ./lazy  ===> lazy has a dead loop in main()
(lldb) target create "./runner"
Current executable set to '/Users/lisa/bt/runner' (arm64).
(lldb) settings set -- target.run-args  "./lazy"
(lldb) r
Process 9235 launched: '/Users/lisa/bt/runner' (arm64)
Process 9235 stopped
* thread #2, stop reason = exec
    frame #0: 0x00007ffdfffbc3ec runtime`_mh_execute_header + 17388
runtime`_mh_execute_header:
->  0x7ffdfffbc3ec <+17388>: mov    x19, sp
    0x7ffdfffbc3f0 <+17392>: and    sp, x19, #0xfffffffffffffff0
    0x7ffdfffbc3f4 <+17396>: mov    x29, sp
    0x7ffdfffbc3f8 <+17400>: ldr    x20, [x19, #0x20]
Target 0: (runtime) stopped.
(lldb) c
Process 9235 resuming
Process 9235 stopped              ====> type ctrl+c to stop in the main function of lazy
* thread #2, stop reason = signal SIGSTOP
    frame #0: 0x0000000100011018
->  0x100011018: ldur   w0, [x5, #-0x8]
    0x10001101c: cmp    w0, #0x0                  ; =0x0
    0x100011020: b.eq   0x100011028
    0x100011024: b      0x100011018
Target 0: (runtime) stopped.
(lldb) si        ========> stuck here

and so on.

My understanding of this issue is that LLDB creates mappings in the target process when trying to evaluate an expression, which makes Rosetta upset (you'll see similar behavior if you use the expression command). I've had luck using the "lower-level" commands that directly read registers and take addresses.

@saagarjha
Thank you for sharing!

I've had luck using the "lower-level" commands that directly read registers and take addresses.

Could you show me concrete commands for enabling watchpoints?
If you share this information, I'll update the project documentation.

Oh, I was mostly commenting in general terms–basically, recommending you use commands like register read and such that don't evaluate expressions. Unfortunately the watchpoint command does, so I wasn't able to use it directly. There's a Python API, but:
$ lldb arch -- -x86_64 ./a.out
(lldb) target create "arch"
Current executable set to 'arch' (arm64e).
(lldb) settings set -- target.run-args  "-x86_64" "./a.out"
(lldb) r
Process 8085 launched: '/usr/bin/arch' (arm64e)
Process 8085 stopped
* thread #2, stop reason = exec
    frame #0: 0x00007ff7fffbba2c runtime`_mh_execute_header + 14892
runtime`_mh_execute_header:
->  0x7ff7fffbba2c <+14892>: mov    x19, sp
    0x7ff7fffbba30 <+14896>: and    sp, x19, #0xfffffffffffffff0
    0x7ff7fffbba34 <+14900>: mov    x29, sp
    0x7ff7fffbba38 <+14904>: ldr    x20, [x19, #0x20]
Target 0: (runtime) stopped.
(lldb) script
Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
>>> import lldb
>>> error = lldb.SBError()
>>> lldb.target.WatchAddress(0x7ff7fffea2f8, 1, True, True, error)
<lldb.SBWatchpoint; proxy of <Swig Object of type 'lldb::SBWatchpoint *' at 0x1038f03c0> >
>>> ^D
now exiting InteractiveConsole...
(lldb) c
Process 8085 resuming
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace.
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0  lldb                     0x00000001008082f0 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56
1  lldb                     0x0000000100807858 llvm::sys::RunSignalHandlers() + 128
2  lldb                     0x0000000100808b8c SignalHandler(int) + 292
3  libsystem_platform.dylib 0x00000001c39b04e4 _sigtramp + 56
4  LLDB                     0x000000010f21e788 lldb_private::ThreadPlanBase::ShouldStop(lldb_private::Event*) + 72
5  LLDB                     0x000000010f213e30 lldb_private::Thread::ShouldStop(lldb_private::Event*) + 1272
6  LLDB                     0x000000010f21b974 lldb_private::ThreadList::ShouldStop(lldb_private::Event*) + 824
7  LLDB                     0x000000010f1cc910 lldb_private::Process::ShouldBroadcastEvent(lldb_private::Event*) + 456
8  LLDB                     0x000000010f1c9248 lldb_private::Process::HandlePrivateEvent(std::__1::shared_ptr<lldb_private::Event>&) + 292
9  LLDB                     0x000000010f1cd5bc lldb_private::Process::RunPrivateStateThread(bool) + 1296
10 LLDB                     0x000000010f1ccccc lldb_private::Process::PrivateStateThread(void*) + 28
11 LLDB                     0x000000010f121e1c lldb_private::HostNativeThreadBase::ThreadCreateTrampoline(void*) + 104
12 libsystem_pthread.dylib  0x00000001c3999240 _pthread_start + 148
13 libsystem_pthread.dylib  0x00000001c3994024 thread_start + 8
********************
Crash reproducer for lldb-1300.0.42
Swift version 5.5.2-dev

Reproducer written to '/var/folders/x3/wncmj8p52t732rrxyz6h424m0000gn/T/reproducer-44d129'

Before attaching the reproducer to a bug report:
 - Look at the directory to ensure you're willing to share its content.
 - Make sure the reproducer works by replaying the reproducer.

Replay the reproducer with the following command:
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/lldb -replay /var/folders/x3/wncmj8p52t732rrxyz6h424m0000gn/T/reproducer-44d129
********************
Segmentation fault: 11

…it seems to broken with the version of LLDB that's in Xcode. One built from source seems to work, but you'll run into issues once Rosetta sets up its exception server I believe, the same as breakpoints.

@saagarjha
Thank you for your detailed explanation.
It seems difficult to use watchpoint in Arm64 instruction level...
If you find any workaround for this, please update this issue thread (I will also look for it.).

recommending you use commands like register read and such that don't evaluate expressions.

If you have other knowledge about Rosetta 2 analysis, please let me know.
Pull-requests are always welcome.

Sorry for my slow response.
I know that such strange behavior exists, but I don't know any workaround for watchpoint issue. Breakpoint sometime works fine when we directly modify the file and embed brk #0x1 instruction.

I have trouble with breakpoint.  I use lldb set an hardware breakpoint on AOT file by 'breakpoint set -a 0x100011000 -H'.  It can issue. However, it stuck when I continue give a 'si' or 'continue' command.
Besides I  modify the AOT file and embed  'brk #0x1' instruction in the AOT file. I try this way, but I get a trap in rosetta runtime, and the brk never issued.
Thanks for your delighting.

I still haven't figured out how to get breakpoints to work, because the exception server messes with them. I'll ask around to see if anyone else has figured it out.


1.0.32 Error - Routing error: A versioning/locking problem occurred during the API call to /transaction/update.

Hello,
since the update to version 1.0.32, we have encountered the following core error log permanently in our JTL Shop 5.3.2 with PHP 8.2.24:
Routing error: A versioning/locking problem occurred during the API call to /transaction/update.

Unfortunately, we have no idea what this means, but some customers are unable to complete their orders, and we suspect it might be related to this issue.
Best Regards
C.Kizilkaya

hi @cuneyt2002 , sorry to hear that you encounter this bug. Do you think you could share the full logs when this error is happening as well as your space_id.
You can send those to<EMAIL_ADDRESS>


Arithmetic operations not working with variables in css

Environment
System:

OS: macOS 10.14.1
CPU: (4) x64 Intel(R) Core(TM) i7
Memory: 24.42 MB / 8.00 GB
Shell: 5.3 - /bin/zsh

Binaries:

Node: 12.3.1 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman

npmPackages:

babel-plugin-styled-components: ^1.10.0 => 1.10.0
styled-components: ^4.3.1 => 4.3.1

npx envinfo --system --binaries --npmPackages styled-components,babel-plugin-styled-components --markdown --clipboard
Reproduction
<div
  css={css`
    max-width: ${maxWidth + 80}px;
  `}
>
{children}
</div>

Steps to reproduce

import { css } from 'styled-components'
Pass random or default maxWidth

Expected Behavior
it should increase max-width by 80. suppose maxWidth is 720 then it should give 800px
Actual Behavior
instead of that if I pass maxWidth 720 the output is 72080px.
if I do something like this it's working
${720 + 80}px;

@imkrunal maxWidth is probably coming in as a string and a string + a number stringifies the number and just appends the strings. Try this:
max-width: ${parseInt(maxWidth, 10) + 80}px;

When you write your JSX if you do <Component maxWidth="720" /> that's what causes this btw. If you want it to be a number, do <Component maxWidth={720} /> instead


/sott API returns JSON

Functions consuming generateSOTT() expect a $response object with a Sott property. In order to return this apiClient needs array('output_format' => 'json')

@Agarwal-Sudhanshu's commit https://github.com/LoginRadius/php-sdk/commit/bb6a821e7815018d1d189389c3305509f39c3136 seems to have resolved this issue.


[desktop_multi_window] Passing data back to parent window

On the windows version, I would like to pass data back to the parent window from a created multi_window instance. Is there a limitation in the engine itself that prevents me from modifying the C++ code, or is it just not implemented yet?

you can use DesktopMultiWindow.invokeMethod. the parent window id always be 0.
https://github.com/MixinNetwork/flutter-plugins/tree/main/packages/desktop_multi_window#invoke-remote-window-method

I tried doing that, but I got Unhandled Exception: MissingPluginException(No implementation found for method <method name> on channel mixin.one/flutter_multi_window_channel) - in this case I used the same logic that I used for sending data to the multi_window.
The notes in https://github.com/MixinNetwork/flutter-plugins/blob/main/packages/desktop_multi_window/lib/desktop_multi_window.dart#L53-L57 seem indicate that it's not possible to do this?

You can try the example.
there is a video which send message between main and child windows.
https://user-images.githubusercontent.com/17426470/160977327-c4eb7dd6-327c-4105-bcd9-ea1cc641512e.mov

I am very confused because I can send messages from id 0 to id 1 but not vice versa. But the demo video indicates sending data from 1 --> 0? I tried running flutter clean and rebuilding from scratch, but that did not fix the issue either.

Is this confirmed to work on windows? It seems the demo is on macos.

Took some trial and error, but I was able to figure out the issue. If anyone else runs into this problem, make sure in your flutter_window.cpp file where you're registering plugins, that you do not register the DesktopMultiWindowPlugin. You should register the lifecycle plugin if you're using it, however.


Turn merge bases into assist bases when disabling them

Have disable merge bases turn all merge
bases into assist bases instead of
completely removing them. This allows
us to continue getting benefits of
kopia assisted incrementals and fixes
the not having the backup models for
details merging

Does this PR need a docs update or release note?

[x] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[ ] :no_entry: No

Type of change

[ ] :sunflower: Feature
[x] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Supportability/Tests
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

fixes #4178
#3943

Test Plan

[ ] :muscle: Manual
[x] :zap: Unit test
[x] :green_heart: E2E

Alternatively, something similar to this could be merged into main to solve #4178 and this could be closed (not sure if this will merge onto main cleanly)


AFNetworking is not ios 6 compatible. the podspec says iOS 6 compatible

NSURLSession is not available on iOS 6 at all
NS_CLASS_AVAILABLE(NSURLSESSION_AVAILABLE, 7_0)
@interface NSURLSession : NSObject

AFNetworking is indeed iOS 6 compatible. AFURLSessionManager & AFHTTPSessionManager are not available without iOS >= 7, but the rest is available.

Our app crashes because of the use of this constant
NSURLSessionTransferSizeUnknown

whose value is equal to -1LL and is defined in NSURLSession.h and is being used in AFURLSessionManager.m like so:
    int64_t totalUnitCount = uploadTask.countOfBytesExpectedToSend;
    if(totalUnitCount == NSURLSessionTransferSizeUnknown) {
        NSString *contentLength = [uploadTask.originalRequest valueForHTTPHeaderField:@"Content-Length"];
        if(contentLength) {
            totalUnitCount = (int64_t)[contentLength longLongValue];
        }
    }

If my base SDK is iOS 8 and I run my app on a device that is on iOS 6, this line will crash.

Like I said, you can't use that class unless you're deploying iOS >= 7.

are you referring to this line of code?
#if (defined(__IPHONE_OS_VERSION_MAX_ALLOWED) && __IPHONE_OS_VERSION_MAX_ALLOWED >= 70000) || (defined(__MAC_OS_X_VERSION_MAX_ALLOWED) && __MAC_OS_X_VERSION_MAX_ALLOWED >= 1090)

@interface AFURLSessionManager : NSObject <NSURLSessionDelegate, NSURLSessionTaskDelegate, NSURLSessionDataDelegate, NSURLSessionDownloadDelegate, NSSecureCoding, NSCopying>

?
Because if my base SDK is 8.0 (the SDK that I build with) and my target OS is 6.0 onwards (which is perfectly acceptable), this class will be available at runtime because you are checking my base SDK, not the iOS version on which the app is running.
Is there some check that you are doing which I am missing on?

No, I'm not referring to any line of code. I'm just restating the explicit requirements of the README.

It's quite unfortunately because the requirements do say that AFNetworking is in fact compatible with iOS 6 but it is not because it is not weakly loading the NSURLSession constants like  NSURLSessionTransferSizeUnknown therefore, upon running the code, dlyb crashes like so:
dyld: Symbol not found: _NSURLSessionTransferSizeUnknown
  Referenced from: /var/mobile/Applications/2A408740-41B8-445E-8EA2-73A7387D63A2/my.app/my
  Expected in: /System/Library/Frameworks/Foundation.framework/Foundation
 in /var/mobile/Applications/2A408740-41B8-445E-8EA2-73A7387D63A2/my.app/my

So that symbol is not present when running the app on iOS 6 since constants are in the section that dyld loads before even the app runs.
But if it makes you feel happier, sure, it is compatible with iOS 6 and it totally works /s

AFNetworking is iOS 6 compatible. You just can't use the NSURLSession subspec—specifically, AFURLSessionManager & AFHTTPSessionManager. If you do, you'll end up with exactly the problem you're describing. This is not unexpected.
I'm not sure how this could be made any more explicit. I'm not interested with arguing with you.
If you have a PR for how this could be made clearer in the README or elsewhere, I'd be more than happy to take a look.

Of course it could be made clearer :-)
it could be said that AFNetworking is not compatible if you build with base SDK 7.0 or higher. Simple as that.

AFNetworking is compatible with iOS 6 whatever you set the base SDK too.....you just can't use AFURLSessionManager & AFHTTPSessionManager if your iOS Deployment Target is set to 6.
Base SDK defines the api's that are available to you during development, so if I have it set to 8.1 then I have all the API's that exists up to 8.1. But in your case you have your deployment target set to 6 but are using API's that are on available from iOS 7 onwards. So when it comes to testing on an iOS 6 device it tries to load symbols that don't exist since it's not available in the iOS 6 sdk.
So if you want to use AFNetworking and target iOS 6 don't use AFURLSessionManager & AFHTTPSessionManager or even the constants defined in NSURLSession.

Thanks @gwynantj
What this means is that if I have an app that used iOS 8 as base SDK and supports iOS 6 onwards, I can not even import the AFURLSessionManager anywhere in my code. That means, I cannot use the "AFURLSessionManager" and the "AFHTTPSessionManager" classes on iOS 7 or 8 either.
The reason is that as soon as you import those classes in your code, the constants and other iOS 7 >= symbols will be loaded into memory and as shown before, dyld will crash because those symbols cannot be found on iOS 7.
So basically, those classes will be useless in iOS 7 and 8 if I want my app to run on iOS 6 since there is on way to conditionally, at runtime, import a class, based on the version of the OS on which your app is running.
It seems like everybody here is really trying to stick with the proposed line of "it is compatible with iOS 6" so I am happy leaving it at that and close this discussion.
Thank you both for your time.


Question: Tried compatability / suitablility when used with TCA?

 Does it play well together?
The navigation discussion thread in TCA seemed to state that the new navigation API does not play well together with TCA :/
I think TCACoordinators is a good alternative, but like the new SwiftUI Navigation API a lot but need back port to iOS 15, so I was glad to find this repo! :)

Thanks @Sajjon ! I haven't done much exploration of how this could fit into TCA. From my understanding, the difficulties described in that thread are due to the fairly limited API surface provided by the new navigation APIs. NavigationBackport replicates those APIs, so it would produce the same difficulties.
Looking at the list of additional APIs that would be desirable for integrating better with TCA, I believe they could all be added in this library. However, at the moment the ethos of this library is to match the SwiftUI API surface without offering any additional APIs, so that users can easily migrate away from this library when they are able to bump their deployment target high enough.
I believe the pointfree team are making progress on new navigation functionality within TCA, so perhaps they have been able to overcome some of those difficulties.


Refactor Milkdrop

The main goal here was to split out preset management (next/previous/loading) into a self contained class that could be tested and understood by me.
Additionally I've introduced a wrapper class around our original Milkdrop component. This wrapper handles the initial loading. This simplifies the Mikdrop components, since it can, internally, assume milkdrop and the presets are always loaded.
Finally, I fixed a few bugs along the way:

Somehow we had lost the code that hooked up this._handleFullscreenChange to screenfull.
Some potential race conditions with previous (previous always assumed the target preset was loaded, which theoretically might not be true if you go back quickly right after requesting the full list.
Unsubscribe from the animation loop when we unmount/close the Milkdrop window.

Finally finally, I probably introduced some new bugs 😛
@jberg

@captbaritone : Awesome, so much cleaner! Everything seems to be working, except one small thing.  The initial preset that is selected in Preset never actually gets loaded into the visualizer on startup.
Looks great!!  🎉 🎉