OmniGUI for Unity3d

I would like to make a renderer for Unity3d.  There are various things I would need to do to make sure it's possible such as ensuring it can run in the unity environment.
However, I'd like to know where I could start if I wanted to implement the rendering/hosting portion?

Hi! I think it's perfectly doable. As long as you can add references to .NET Standard, you can create a drawing backend to make it work with Unity3D. Did you take a look to the IDrawingContext  interface? If you make an implementation of those methods, then you've got it :)
I can try to offer you help as long as you set up a OmniGUI.Unity3D in, for example, your own fork of OmniGUI :)
Thanks for your interest!

BTW, the rendering unit in OmniGUI is the mentioned IDrawingContext. It's also necessary to provide a custom implementation of ITextEngine that provides text measuring (for now :)).
Feel free to ask me anything.

So, I'm trying to get started on this, I've made a fork and loaded up the project in Visual Studio but most of the projects don't load.
I'm not sure what this is supposed to look like, but even OmniXAML doesn't load.
What version of .net standard does it require?

Unity hasn't setup any support for .NET standard yet, but they are aiming to in the 2018.1 beta, which is the next major release.
Still, I'd like to get the kinks worked out in loading and working on the project.
To clarify my last comment, I'm using Visual Studio 2017 15.5.1 currently and have .NET 4.6 4.6.1 and 4.6.2 installed.
I installed the .NET Core 2.0 SDK
but most of the projects fail to load

Oops, it seems that the submodules aren't downloaded. Can you verify that the \OmniXAML and \Zafiro subdirs are empty? If so, execute this command inside the root folder:
git submodule update --init
Tell me if it works!
(You can check this question in StackOverflow for more information regarding this problem https://stackoverflow.com/questions/11358082/empty-git-submodule-folder-when-repo-cloned)

it's not a preview as far as I know?  its the community edition.

I got Team viewer loaded up, what needs to happen

Okay, I think I got this, executing the git submodule upate init, didn't quite do the trick.
I followed the SO answer and used a recursive clone which had much better results.
I need to install some libs for some of the projects to load so I'm doing that now and we'll see how that goes.

should I be able to have all projects loaded and be able to compile?  I'm having some issues with getting the project to compile without making any modifications

Hey! No, you can unload all the projects inside the Platforms and Tests Apps solution folders. Unload them and they should compile :) If it doesn't, tell me the error that it shows.
Good luck!

I checked and the OmniGui.dll is definitely not there.

OK, I have experienced the same issue before.

First, unload the projects under Platforms and Test Apps

Now, try to compile individually.

First: Zafiro.Core inside the OmniXAML folder.
Next: the rest of projects in the OmniXAML folder.
Next. The projects in the Zafiro folder.
Last: The rest of the projects.

It seems that VS sometimes has problems with using submodules.
If it still doesn't work check that the lightweight solution loading is disabled. I also had problems with that :)

Severity	Code	Description	Project	File	Line	Suppression State
Error		Cannot find project info for 'E:\Projects\Progamming\UnityLibraries\OmniGUI\OmniXAML\Zafiro\Zafiro.Core\Zafiro.Core.csproj'. This can indicate a missing project reference.	OmniGui	C:\Program Files\dotnet\sdk\2.1.2\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Sdk.targets	114
now I only have this error.

I can't seem to find lightweight solution loading from all my search/google, I can only assume its not set, but I don't see the options where they should be.,

Strange! have you tried to restart Visual Studio?

https://dotnetvibes.com/2017/02/13/lightweight-solution-load-in-visual-studio-2017/

Lightweight solution load was removed in 15.5
"Visual Studio team had decided to discontinue Lightweight Solution Load (LSL) support in the 15.5 release. "

I restarted, but I still have the same problem

OK, do you have the project in GitHub? Just point me to the code and I will see what's going on!

I do, but I haven't pushed or made any changes, so its no different than what you have.

OK! I will check it later 😅
Enviado desde mi teléfono con Windows 10

De: James LaPenn<EMAIL_ADDRESS>Enviado: Tuesday, December 12, 2017 7:06:49 PM
Para: OmniGUI/OmniGUI
Cc: José Manuel Nieto; Comment
Asunto: Re: [OmniGUI/OmniGUI] OmniGUI for Unity3d (#7)
I do, but I haven't pushed or made any changes, so its no different than what you have.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/OmniGUI/OmniGUI/issues/7#issuecomment-351135293, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AC9z20TcXVA_g6jbmeOsDcJt8qPSdoFEks5s_sC5gaJpZM4Q7cbJ.

executing dotnet restore seemed to help, but now I can't reproduce it.
What framework should I be targetting, it looks like you're targeting net standard 1.2 right now

Wow, but do you have it building now? Yes, it’s 1.2 because it doesn’t require a bigger API, so it’s quite compatible 😀
Enviado desde mi teléfono con Windows 10

De: James LaPenn<EMAIL_ADDRESS>Enviado: Tuesday, December 12, 2017 7:14:35 PM
Para: OmniGUI/OmniGUI
Cc: José Manuel Nieto; Comment
Asunto: Re: [OmniGUI/OmniGUI] OmniGUI for Unity3d (#7)
executing dotnet restore seemed to help, but now I can't reproduce it.
What framework should I be targetting, it looks like you're targeting net standard 1.2 right now
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/OmniGUI/OmniGUI/issues/7#issuecomment-351138042, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AC9z25RYNQvvlhz65wWoNJdw32CTVmdCks5s_sKKgaJpZM4Q7cbJ.

Windows 10 Pro x64, Fall Creators Update.

how about IDE?

This => :)

You have any other ideas on this?  I do have to wait for the next beta of Unity to develop this extension, but I'd really like to be able to pick it up and go once I have all the parts.


vscode-extensions.charliermarsh.ruff: 2023.60.0 -> 2024.4.0

Description of changes
I updated the version to latest (2024.4.0) and added arch parameters

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Can we rename the commit to
vscode-extensions.charliermarsh.ruff: 2023.60.0 -> 2024.4.0

Done!

Hi! To fit CONTRIBUTING.md, could you please rename the commit to vscode-extensions.charliermarsh.ruff: 2023.60.0 -> 2024.4.0? Thanks! :)
pkgs commit-conventions

Hi! To fit CONTRIBUTING.md, could you please rename the commit to vscode-extensions.charliermarsh.ruff: 2023.60.0 -> 2024.4.0? Thanks! :)
pkgs commit-conventions

@Azd325 Oh my bad, sorry for the wasted time, I'll keep an eye on that for the next PR! Should be OK now. I also added explanation in commit description :+1:

@DataHearth But nice catch. I have only darwin so I never saw that issue. :)

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

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


Poor intellisense experience w/o internet connection

No indication as to what the problem is and even says it "successfully" acquired typings
Repro steps:
0. disable wifi

File > New Project (any type)
typings fail to be acquired, and no indication as to why.

Closing as this is now part of the JS/TS language service.


this entry needs a link to "the rest of the story" about Scripting.Dictionary

See https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/windows-scripting/x4k5wbx4(v%3Dvs.84) for the complete reference information on Scripting.Dictionary.

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

ID: 1cc9bdf2-54b9-e787-dc1f-f58f83136d2b
Version Independent ID: 73078319-88b6-e1c0-4c15-a6761fc492ae
Content: Dictionary Object
Content Source: Language/Reference/User-Interface-Help/dictionary-object.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

@dickwatson
Thanks for the feedback. I added this link to the page. Changes will be live in a day or so...


Add a core "disengage gcds" analyser

Pull request type

[x] This is new functionality or an addition to existing functionality
[ ] This is a bugfix to existing functionality
[ ] This is a patch bump

Pull request details

[ ] This is in response to a GitHub issue: [Link to issue]
[x] This is in response to a discussion or thread on Discord: [Link to thread or start of discussion]
[ ] The goal of this PR is detailed below:

All tanks and several melee jobs have a low value ranged attack that they can use when disengaging from an enemy.
Gunbreaker had a module tracking this, since the only job specific input is the action ID, we could move it to core so that other jobs can easily implement it as well by passing their disengage action in.

Testing / Validation

[] The changes being implemented with this bugfix include comments that contain example log(s) to test with

[ ] I have submitted the example log(s) to the xivanalysis static on FFLogs for record keeping

[x] I used the log(s) listed below to develop and test this bugfix:

https://www.fflogs.com/reports/a:GxgMcjNHyVmqFb89#fight=last&type=damage-done
Job Maintenance

[x] I am active on the xivanalysis Discord and part of the job maintainers group for the job(s) in this PR
[ ] I have collaborated with one or more job maintainers for the job(s) in this PR while developing it
[ ] I prefer to receive any communications through GitHub only

Since there were no potency or action changes in 7.05 for warrior I have also bumped the supported patches value in the changelog.

@AzariahAeroborn I've updated this per review comments, please take a look when you have the opportunity and let me know if there's any more to do here.


Compartment definition parsing

Summary
This PR creates a new script to parse the Patient compartment definition so that we can more accurately identify all the ways that a FHIR resource can reference a Patient resource. Updates are made in measure.service.js to reflect the use of the compartment definition over the modelInfo.
New behavior
Previously, we parsed the modelInfo to tell us how all the different resourceTypes reference the patient, but it isn’t accurate so it makes more sense to parse through the Patient compartment definition for the search params and then use that to get the relevant xpaths. The script npm run parse-references has been updated to parse the Patient compartment definition for the search parameter keywords that are used for a given resource type. The parameters are then used to lookup the corresponding path value in asymmetrik’s parameter jsons, which we have exported.
Note that this script assumes that you want to use base version 4_0_0. We will need to update it for 4_0_1 when that is available.
(Also I did not delete the modelInfo directory from the repo in case we do need it at some point for something. If it does make more sense to delete it, I can do that before merging these changes.)
Code changes
The “parse-references” script was updated in package.json to call parseCompartmentDefinition.js instead of parseModelInfo.js.
The parseCompartmentDefinition.js script was added to parse the patient compartment definition. It goes through each resource, and if it has a param attribute, it uses getSearchParameters to obtain the xpaths that are used to reference the patient.
Testing guidance
Run the unit tests and make sure they work and that they make sense.
To test this on your own, follow the testing procedure outlined in this PR that used the modelInfo. The only difference will be that you want to change the subject.reference to performer.actor.reference instead of actor.reference (the modelInfo got this wrong). The code within the bundle should look like this:
"performer": {
	"actor": {
		"reference": "Patient/numer-EXM130"
	}
  }

Check that the code works with performer.actor.reference. If you add the console.log statements that are suggested in the referenced PR, they should show up, although you may run into a separate error regarding data.map in the test server. This is an issue with parsing in fqm-execution since we are using a nested structure. This is something to take note of for the future.

In what way is the modelinfo not accurate?

@p9g for this specific use case, we are trying to parse the ModelInfo to identify all the ways in which a given FHIR resource can reference a Patient, making use of the <contextRelationship context="Patient" ... tags. An example of an inconsistency that we found is shown in the following example for FHIR Procedures:
   <typeInfo baseType="FHIR.DomainResource" namespace="FHIR" name="Procedure" identifier="http://hl7.org/fhir/StructureDefinition/Procedure" label="Procedure" retrievable="true" primaryCodePath="code" xsi:type="ClassInfo">
      ...
      <contextRelationship context="Patient" relatedKeyElement="patient"/>
      <contextRelationship context="Patient" relatedKeyElement="actor"/>
   </typeInfo>

The relatedKeyElement attributes are saying patient and actor. Initially we thought these would be referring to the specific attributes on the FHIR resource itself, but that seems to not be the case (FHIR Procedures have subject, not patient). Then we thought that these relatedKeyElements were referring to search parameters, not attribute names (FHIR Procedures do have a patient search parameter, but not an actor one: https://www.hl7.org/fhir/procedure.html#search
--
We found more examples like this in the ModelInfo, so we decided it wasn't a reliable enough way to identify the attributes on FHIR resources that reference a patient.


Update pivot sidebar layout mechanism

This PR updates the sidebar layout mechanism to display as many pills as possible while still maintaining the visibility of all three sections.

@djbarnwal Alright, unfortunately, only Safari seems to support setting a flex-basis in conjunction with max-height: fit-content, so I just moved this conditional clamping to a JS implementation. Works as intended across all browsers now.


npm does not save authToken when authenticating to Verdaccio

My reason:
Hi,
I want to get an auth token to my private registry running Verdaccio, for CI purposes.
When I authenticate with npm login --registry https//npm.example.com npm stores my password in clear text instead of saving an auth token.
This worked 2 months ago. Since then I update to the latest version of npm (5.6.0) and Verdaccio (2.7.3) and I no longer get an auth token.
Steps to reproduce:
$ npm login --registry https://npm.example.com
Username: demurgos
Password:
Email: (this IS public<EMAIL_ADDRESS>Logged in as demurgos on https://npm.example.com/.
$ cat ~/.npmrc
//registry.npmjs.org/:_authToken=ffffffff-ffff-ffff-ffff-ffffffffffff
//npm.example.com/:_password="xxxxxxxxxx"
//npm.example.com/:username=demurgos
<EMAIL_ADDRESS>//npm.example.com/:always-auth=false

$ npm --version
5.6.0
$ verdaccio --version
2.7.3

App Version:
I believe that it worked (saved the token instead of password) with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Config file:
# path to a directory with all packages
storage: /var/www/example.com/verdaccio/storage/

web:
  enable: true
  title: Example - npm by Verdaccio

auth:
  htpasswd:
    file: /var/www/example.com/example.htpasswd
    # Disable registration
    max_users: -1

# a list of other known repositories we can talk to
uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '**':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

# Public root
url_prefix: https://npm.example.com/

listen:
  - localhost:xxxx

# log settings
logs:
  - {type: stdout, format: pretty, level: http}

Additional information:
$ npm --verbose prints:
$ npm login --verbose --registry https://npm.example.com
npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node',
npm verb cli   '/usr/bin/npm',
npm verb cli   'login',
npm verb cli   '--verbose',
npm verb cli   '--registry',
npm verb cli   'https://npm.example.com' ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb npm-session 2e8442c56aaa32fb
Username: (demurgos) demurgos
Password: (<default hidden>)
Email: (this IS public<EMAIL_ADDRESS><EMAIL_ADDRESS>npm verb login before first PUT { _id: 'org.couchdb.user:demurgos',
npm verb login   name: 'demurgos',
npm verb login   password: 'XXXXX',
npm verb login   type: 'user',
npm verb login   roles: [],
npm verb login   date: '2018-01-20T18:34:09.575Z' }
npm http request → PUT https://npm.example.com/-/user/org.couchdb.user:demurgos
npm http 409 ← Conflict (https://npm.example.com/-/user/org.couchdb.user:demurgos)
npm info adduser Authorized user demurgos
Logged in as demurgos on https://npm.example.com/.
npm verb exit [ 0, true ]
npm info ok

Container: N/A (I use my local environment)

To be honest, is very disappointing how npm changes things on minor versions that totally breaks functionalities.
I have been suffering hughe problems on my CI environments because this silently changing features

@demurgos does this issue persist with latest npm?

I gave up on the npm CLI (in favor of yarn) so I haven't tried since then. After updating all my dependencies, it seems to work with npm 6.0.1 and verdaccio 2.7.4. (I get a token instead of credentials, as expected).
I'm closing this issue for now.


sim/minmea: Fix defconfig warning

Summary
Warning/Error:
$ ./tools/configure.sh -l sim:minmea
$ make defconfig
$ make savedefconfig
$ diff defconfig boards/sim/sim/sim/configs/minmea/defconfig
38d37
< CONFIG_GNSSUTILS_MINMEA_LIB=y
39a39
> CONFIG_GNSSUTILS_MINMEA_LIB=y

Impact
sim:minmea
Testing
./tools/configure.sh -l sim:minmea

[Experimental Bot, please feedback here]
This PR does not meet the NuttX requirements. Here's why:

Missing Information in Summary: The summary only provides an error message. It needs to explain:

Why the change is necessary (What problem does the error indicate? Why is the config option duplicated?)
What the change does to fix the problem.
How the change works.

Insufficient Impact Assessment:

The impact section only lists "sim:minmea".  It needs to clarify what impact the change has on the user, build process, hardware, documentation, security, and compatibility. For example, does this fix a bug? Does it add a new feature?

Incomplete Testing Information:

Build Host:  Provide details about the OS, CPU architecture, and compiler used for testing.
Target: Specify the simulator version and configuration used.
Logs:  The testing logs are empty. Include relevant logs from before and after the change to demonstrate the issue and the fix.

To improve this PR:

Expand the Summary: Explain the problem, solution, and how it works.
Complete the Impact Assessment:  Address all the impact points with specific details.
Provide Detailed Testing Information: Include the Build Host, Target details, and relevant testing logs demonstrating the problem and the fix.


Module '"@prisma/client"' has no exported member 'Prisma' on Docker image build

Bug description
When compiling from Typescript down to JS, I get the following error: error TS2305: Module '"@prisma/client"' has no exported member 'Prisma'.
This only happens when building a Docker image. When building locally on my host I have no issues.
Older versions of the Docker engine are not giving issues.

How to reproduce
Dockerize your app on Docker engine 20.10.13. After installing dependencies and trying to build the project, TS should complain about the above error.
Expected behavior
The app should compile from TS to JS successfully.
Prisma information

Environment & setup

OS: Mac OS (M1)
Docke engine version: 20.10.13
Node base image: node:14.17.5-alpine
TypeScript version: 4.3.5

Prisma Version
prisma: 2.29.1 and 3.11.0
@prisma/client: 2.29.1 and 3.11.0

I am having this same issue. Same environment too.

@janpio not OP but I tried it and I get this error instead:
 => ERROR [builder 5/6] RUN yarn run prisma generate                                                                                1.0s
------
 > [builder 5/6] RUN yarn run prisma generate:
#15 0.328 yarn run v1.22.18
#15 0.348 $ /app/node_modules/.bin/prisma generate
#15 0.938 Error: Unknown binaryTarget linux-arm64-openssl-undefined and no custom binaries were provided
#15 0.974 error Command failed with exit code 1.
#15 0.975 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
------

@fcoury what does your schema.prisma look like? I recall having the same openssl issue in my docker
Adding this fixed it:
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "rhel-openssl-1.0.x"]
}

@khuezy thank you so much for the suggestion. I just tried it with those changes and unfortunately I still got the same error:
 => ERROR [builder 5/6] RUN yarn run prisma generate                                                                                0.5s
------
 > [builder 5/6] RUN yarn run prisma generate:
#15 0.224 yarn run v1.22.18
#15 0.243 $ /app/node_modules/.bin/prisma generate
#15 0.515 Error: Unknown binaryTarget linux-arm64-openssl-undefined and no custom binaries were provided
#15 0.530 error Command failed with exit code 1.
#15 0.530 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
------
executor failed running [/bin/sh -c yarn run prisma generate]: exit code: 1

For reference, here's my schema.prisma file:
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Report {
  id           Int    @id @default(autoincrement())
  ticker       String
  balanceSheet Bytes
  income       Bytes
  cashFlow     Bytes
}

Hmm what does your Dockerfile look like? If you're using -slim, you'll need to install the openssl
eg:
RUN apt-get install -y openssl

Just managed to make it work using docker-buildx:
docker buildx build --platform linux/amd64 -t partnerx .

Should it be possible to build using Docker Desktop without buildx on a M1 Mac?

It might be related to https://github.com/prisma/prisma/issues/8478 if you are using M1 Mac. Prisma do require openssl to be installed so your images should have it.

Can you share a minimal reproduction here with contents of your Docker image?

Same issue. Also for me it is happening kinda randomly. One time it works and another - no. That is the worst kind of problems...

The error appeared suddenly in our CI, but our docker image and our node/yarn/prisma version did not change since the last successful build. Unfortunately, we were unable to reproduce the bug locally.

Hey y'all,
I had the same issue a few days ago, and I've fixed it by simply using npx prisma generate before yarn build and after npm install .
I hope this can help you ;)

Can confirm that @rafaell-lycan 's solution works! Great explanation @aloknecessary

Thanks @stefantul, Just for the records, my explanation is no different. :)

@stefantul yes, it works. =)

Managed to speed up medium-sized project building significantly via Apple Silicon for X86 linux server without the need to use --platform=amd64 on all build layers.
What I did is separate the prisma generate from other stages. My existing Dockerfile is already multi-staged, so separating prisma or any other binary generating process does makes sense, if you're not doing multi-stages build, I recommend you to do so.
Below is a simplified example Dockerfile (this project is building Nextjs+Prisma).  Pay attention to the FROM line, only the binary-deps and runner (the end target) have --platform=amd64 in it.
Only those build lines inside that 2 stages will make your Apple Silicon machine runs emulation, other will run natively, this means npx prisma generate will detect x86 machine and download those Rust-compiled binary. The usual long-running command (npm/yarn install and npm/yarn build) will run natively. Why this works is because the compiled code (except the one generating binaries externally) doesn't really depends on the architecture during build, only during runtime (that's why the end stage does have --platform=amd64.
##########
## DEPS ##
##########
FROM node:16-alpine AS deps
RUN apk add --no-cache libc6-compat

WORKDIR /app

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
RUN \
    if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
    elif [ -f package-lock.json ]; then npm ci; \
    elif [ -f pnpm-lock.yaml ]; then yarn global add pnpm && pnpm i; \
    else echo "Lockfile not found." && exit 1; \
    fi

####################
## Native Binaries Deps ##
####################
FROM --platform=amd64 node:16-alpine AS binaries-deps
RUN apk add --no-cache libc6-compat

WORKDIR /app

# Prisma client
COPY --from=deps /app/node_modules ./node_modules
COPY prisma ./prisma
RUN npx prisma generate

# Put any other binary build process here if needed

#############
## BUILDER ##
#############
FROM node:16-alpine AS builder

WORKDIR /app

COPY --from=binaries-deps /app/node_modules ./node_modules

ENV NODE_ENV=production

COPY . .

RUN yarn build

############
## RUNNER ##
############
FROM --platform=amd64 node:16-alpine AS runner

WORKDIR /app

ENV NODE_ENV=production

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/next.config.js ./
COPY --from=builder /app/public ./public
COPY --from=builder /app/package.json ./package.json

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static

USER nextjs

# Entrypoint to run before the final CMD,
# place any additional commands that can only be run during runtime,
# such as DB migration.
COPY --chown=nextjs:nodejs deployment/docker-entrypoint.sh .

EXPOSE 3000

ENV PORT 3000

ENTRYPOINT ["docker-entrypoint.sh"]

CMD ["node", "server.js"]

If you're still new to Dockerfile, ignore all those lines above, just focus on the FROM, RUN npx prisma migrate and COPY --from=binaries-deps.
Hope this helps, sorry for the long explanation.

@stefantul yeah, it works.

Just managed to make it work using docker-buildx:
docker buildx build --platform linux/amd64 -t partnerx .

Should it be possible to build using Docker Desktop without buildx on a M1 Mac?

This results in a very long build time. Any updates?

Just managed to make it work using docker-buildx:
docker buildx build --platform linux/amd64 -t partnerx .

Should it be possible to build using Docker Desktop without buildx on a M1 Mac?

can you explain this please? I do not know what I am looking at.

I got this to work use FROM node:16.18-slim

I ran into this issue when using a PNPM monorepo with Turborepo in a Docker image. After a lot of bashing my head against the problem I fixed it by adding a .npmrc file to the root of the monorepo and then COPYing that file to the Docker container.
The .npmrc file contained
node-linker=hoisted
public-hoist-pattern[]=*prisma*
prefer-symlinked-executables=false

As far as I can see, the comments in this issue in which it is clear what happened fall into one of two categories:

The client wasn't generated with prisma generate during the build or the generated client wasn't copied to the Docker image if generated outside the Docker container (so, not a Prisma issue), or
The client failed to generate on ARM64 Alpine Linux.

The second problem was fixed in Prisma 4.10.0, so I am going to go ahead and close this issue to clean up the backlog a bit. Please let me know if I missed something, or open a new issue if you still run into a similar problem so that we can take a look!

I removed node_modules from .dockerignore, and worked perfectly fine for me!

Hmm what does your Dockerfile look like? If you're using -slim, you'll need to install the openssl
eg:
RUN apt-get install -y openssl

I run docker on centos and this is solution for me.
yum install -y openssl
thank you


Italic PIXI.Text is cut off

The right edge of italic PIXI.Text is cut off.
https://www.pixiplayground.com/#/edit/5c0kJBUwHzWl29oH_aIZh
Any simple workaround to fix it, please?

Environment

pixi.js version: 4.8.8
Browser & Version: Chrome 75.0.3770.100
OS & Version:  Mac Mojave 10.14.5

According to https://github.com/pixijs/pixi.js/blob/dev/packages/text/src/Text.js#L128 , there's padding but its added to all sides, not just right.

Padding is the only solution. We make a guess at how big the canvas has to be before drawing text to it, and 99% of the time it's right. But occasionally.... not so. Add padding to fix, and turn on trim if you find you're getting 'excessive' padding

Thanks. It works. I don't suppose it will be solved so I close the issue.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.10 to before v5.16.11",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f611e8cf98ec908b9c2c0da6064a660fc6022487",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c20f90fe009ffdccba826d2ee839e5d55118a2bf"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "f611e8cf98ec908b9c2c0da6064a660fc6022487",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "c20f90fe009ffdccba826d2ee839e5d55118a2bf",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "lockdep: Correct lock_classes index mapping\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.11 by commit c20f90fe009ffdccba826d2ee839e5d55118a2bf, it was introduced in version v5.10 by commit f611e8cf98ec908b9c2c0da6064a660fc6022487. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000565


Remove the Rickroll

To quote a random poem I found online:

I don't hate you,
Because I still love you.
I can't look at you,
Because it hurts to.
We don't talk,
Because there is nothing left to say.

The Rick Roll has had its golden age. It's time to let it go.

:-1: Long live Rick Roll, it's golden age is all eternity.

Rickroll has been removed by some other pull request.


update makeFiltered to coerce data to character

Closes #104

@samussiah can you take a look at the conflicts? not sure where those are coming from actually ...


nextcloud-client: miscellaneous fixes

Motivation for this change
I've been maintaining a version of this outside of nixpkgs for a while and since this is a thing now I would like to contribute the difference to this expression.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)

Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"

[x] Tested execution of all binary files (usually in ./result/bin/)

[x] Fits CONTRIBUTING.md.

enabled parallel building

use existing cmake* attrs rather than manipulating cmake flags in preConfigure

use inotify for more efficient monitoring of file changes

provide gnome-keyring integration when built with withGnomeKeying = true;

I'm not sure if adding gnome_keyring to LD_LIBRARY_PATH is the correct way to go about this, but it's what worked for me.
@caugner thanks for your work on this package.

My bad, I'll make it so that it checks stdenv.isLinux - what I intended to express is that nextcloud-client tries to find inotify at build time and uses it if it's available.
Happily I'm at my workplace right now where I have access to a Mac to build on, and the build fails with
make[2]: Entering directory '/private/var/folders/jt/qgrx8lp10ylbdlnb93t54r6c0000gn/T/nix-build-alsa-lib-<IP_ADDRESS>.drv-0/alsa-lib-<IP_ADDRESS>/src/control'
  CC       cards.lo
In file included from cards.c:35:
In file included from ./control_local.h:22:
../../include/local.h:47:2: error: Header defining endianness not defined
#error Header defining endianness not defined
 ^
1 error generated.
make[2]: *** [Makefile:334: cards.lo] Error 1
make[2]: Leaving directory '/private/var/folders/jt/qgrx8lp10ylbdlnb93t54r6c0000gn/T/nix-build-alsa-lib-<IP_ADDRESS>.drv-0/alsa-lib-<IP_ADDRESS>/src/control'
make[1]: *** [Makefile:478: all-recursive] Error 1
make[1]: Leaving directory '/private/var/folders/jt/qgrx8lp10ylbdlnb93t54r6c0000gn/T/nix-build-alsa-lib-<IP_ADDRESS>.drv-0/alsa-lib-<IP_ADDRESS>/src'
make: *** [Makefile:338: all-recursive] Error 1
builder for ‘/nix/store/9djjg7idiqp7awyx6v3568fkykacrs3l-alsa-lib-<IP_ADDRESS>.drv’ failed with exit code 2
fetching path ‘/nix/store/3ip043cbchgj6m4hjfiwn0qw87jdcaz0-qtbase-5.6.2-dev’...
cannot build derivation ‘/nix/store/2chdyipixw3ncqisy3316w98vrwaj9m5-qtmultimedia-5.6.2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/z6yl0n1s54ny3zfqz660kfx14w8sn3l0-qtlocation-5.6.2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/24axc64rwn91h8yk8hv8b6vlg2r7jgqz-qtwebkit-5.6.2.drv’: 1 dependencies couldn't be built
killing process 7940
cannot build derivation ‘/nix/store/hn2r0a5186ygw93bxzwh7w74y5v0ik9i-nextcloud-client-2.3.2.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/hn2r0a5186ygw93bxzwh7w74y5v0ik9i-nextcloud-client-2.3.2.drv’ failed
nix-build -A nextcloud-client -I nixpkgs=.  5.87s user 4.06s system 54% cpu 18.223 total

Which is a dependency of qtmultimedia and was not introduced by this commit.
I'm certain this can build on Darwin, but I think that's out of scope for this PR.

Rebased!

Tested locally. Pushed to master (e828dcb5cd4ae321dde053d2eb3a24992b42f167 and parents) and release-17.09 (e61f1a24c4f654de69286626bcb236d8ca117734 and parents). Thanks!

Thank you @eqy and @bjornfor!
In general, it would make sense to merge owncloud-client and nextcloud-client in the sense that the nextcloud-client config could inherit from the owncloud-client. Unfortunately, I don't have the Nix experience to accomplish this.


iOSPushNotification, libRCTPushNotification-tvOS.a not found

Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 85.26 MB / 8.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 8.9.0 - /usr/local/bin/node
Yarn: 1.6.0 - /usr/local/bin/yarn
npm: 5.5.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.1, macOS 10.13, tvOS 11.1, watchOS 4.1
Android SDK:
Build Tools: 23.0.1, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 27.0.1, 27.0.3
API Levels: 23, 25, 26, 27
IDEs:
Android Studio: 2.3 AI-162.4069837
Xcode: 9.1/9B55 - /usr/bin/xcodebuild
npmPackages:
react: 16.3.1 => 16.3.1
react-native: 0.57.0 => 0.57.0
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
Description
I have followed all steps in these articles:
https://facebook.github.io/react-native/docs/pushnotificationios
https://facebook.github.io/react-native/docs/linking-libraries-ios#manual-linking
And iOS build of my app throws this error:
clang: error: no such file or directory: '/Users/DanielKurfirst/Desktop/0917/2020-react-native/ios/build/Build/Products/Debug-iphonesimulator/libRCTPushNotification-tvOS.a'
Has anyone else experienced this?

You should be linking with libRCTPushNotification.a, not libRCTPushNotification-tvOS.a.  The second library is only for Apple TV apps.

@dlowder-salesforce Thank you! That was the culprit.

This issue has been moved to react-native-community/react-native-push-notification-ios#6.

this issue still happen whe you try to do a release..any idea?..thanks


Reproduce issue with nested liquidity and WETH

This PR has 2 things:

It adds a new failing test: trying to add nested liquidity with single token WETH throws with BAL#001 error
Little refactor to extract token addresses and cleanup nested tests (it could be done in other tests too)

@agualis - thanks for opening this issue. The problem is that when creating the relayer actions, I have to prune/skip the ones that have all amounts in equal zero.
In the test case you created, the join action at the 3POOL should be removed from the chain because only WETH was being provided as input directly to WETH_3POOL.
I also refactored a bit the addresses/constants file with something a bit more similar to what we had in the previous SDK, which is a bit more structured to support testing on multiple chains.
Let me know what you think and I'll replicate that to other tests through the code.

@brunoguerios Looks good 👍


Migrations generated in Rails 5.1 inherit from ActiveRecord::Migration[5.1]

If a scenic model or database view is generated in a rails 5.1 application, the migration inherits from ActiveRecord::Migration[5.0] instead of ActiveRecord::Migration[5.1].

Ahhh looks like this is fixed in 5e698a231130097a5935fff08e50fe8d8497a905 and just waiting on a release. Apologies.


{Core} Directly call acquire_token_for_client to acquire access token for service principal

Related command
az login
Description
MSAL 1.23.0 (https://github.com/AzureAD/microsoft-authentication-library-for-python/pull/581) changed the behavior of acquire_token_for_client so that it will automatically look up access tokens from cache, so there is no need to call acquire_token_silent and check the result manually then call acquire_token_for_client.
The MSAL example also reflects the same:
https://github.com/AzureAD/microsoft-authentication-library-for-python/blob/95df6086ec186e395186e097f8c9103c4ee74d83/sample/confidential_client_secret_sample.py#L53-L55
# Since MSAL 1.23, acquire_token_for_client(...) will automatically look up
# a token from cache, and fall back to acquire a fresh token when needed.
result = app.acquire_token_for_client(scopes=config["scope"])

Core

/azp run


[KARAF-5826] Upgrade to narayana 5.9.0.Final

retest this please

Feature verification fail. I'm fixing.


Make dataclasses frozen

HA is moving to a model where dataclasses need to be frozen (to aid caching), and will start logging depreciation warnings in 2024.x. Let's get ahead of the game.
See https://github.com/home-assistant/core/pull/105211

Hmph, looks like we can only pass frozen=True if the base class is frozen. This probably depends on #480 then.


Remove Legacy Datasets

Overview
Deleted old, unused datasets. Also regenerated sampleData to ensure everything was new. Closes #1642.
Test Notes/Sample Code

Notes:
I also turned off the qualification-tests-dev workflow. I mentioned in #1533 that the workflow should be turned back on once the tests are ready, but let me know if you'd like to do something more complicated to decide when those ones run.

@jwildfire Should sampleSummary be removed as part of this, per #1637? Right now it looks like sampleSummary and sampleResults are identical, and I'm not sure if they're supposed to be different.

@jwildfire Should sampleSummary be removed as part of this, per #1637? Right now it looks like sampleSummary and sampleResults are identical, and I'm not sure if they're supposed to be different.

See #1651


WebApp:'az webapp config access-restriction add' fails when webapp has a pre-existing ServiceTag rule

This is autogenerated. Please review and update as needed.
Describe the bug
When using az webapp config access-restriction add to add additional rules to a webapp that already have a rule with a ServiceTag, the command fails
Command Name
az webapp config access-restriction add
Errors:
'ServiceTag' is not valid value for enum <enum 'IpFilterTag'>
Traceback (most recent call last):
Temp\pip-unpacked-wheel-tv8yhkg2\msrest\serialization.py, ln 987, in serialize_enum
enum.py, ln 293, in __call__
enum.py, ln 535, in __new__
enum.py, ln 548, in _missing_
ValueError: 'ServiceTag' is not a valid IpFilterTag

...

Temp\pip-unpacked-wheel-tv8yhkg2\msrest\serialization.py, ln 771, in serialize_data
Temp\pip-unpacked-wheel-tv8yhkg2\msrest\serialization.py, ln 994, in serialize_enum
msrest.exceptions.SerializationError: 'ServiceTag' is not valid value for enum <enum 'IpFilterTag'>

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Create a WebApp and add an access restriction rule with a Service Tag. Im my case, we have an "allow frontdoor" rule using the service tag of AzureFrontDoor.Backend
Then try and create any additional rules with az webapp config access-restriction add -g {} -n {} --rule-name {} --priority {} --action {} --ip-address {} --subscription {}

Expected Behavior
Add the additional rule
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.18.0

Extensions:
azure-devops 0.18.0
front-door 1.0.11

Additional Context

webapp

Looking in to this issue.

Hi, we're having the same error but with another command.
az webapp traffic-routing set --distribution StageName=100 --name WebApp --resource-group ResourceGroup
The issue is related?

@andre-r-magalhaes - Issue is logged for ServiceTag rule. you too using this rule?

@rodney-almeida - could you please share the --debug log for further investigation.

@madsd might probably be fixed when we have the new SDK in CLI?

@panchagnula yes, this cannot be fixed before we have the new SDK. Until then - if you use service tag rules, you will have to manage from ARM/REST, portal or PowerShell...

I am also having this same issue.

@Pangamma Official release of the next CLI version containing the fix is 6. May (2.23)


Upcoming events section added

Description
Created an  Upcoming event section
Closes #58
Type of change
Please delete options that are not relevant.

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] Any dependent changes have been merged and published in downstream modules

Screenshots

@codewithvk Please take a review at this, will the colour seems good to you?
I was unable to make it similar to that mentioned in the issue, any suggestions will be helpful for me. And apologies for the delay.

Can u please check this again?


datapath: Switch from BPF_{FUNC,FUNC_REMAP,STUB} to libbpf approach

Instead of defining helpers ourselves, import bpf_helper{,_defs}.h from the libbpf and generate vmlinux.h from the net-next. The libbpf approach seems to become canonical, and with it it's easier to add new helpers and structs (copying vs defining ourselves each individually).

@dylandreimerink Are you still on it? If not, maybe it makes sense to make it good-first-issue?

I completely forgot about this issue to be honest. At the time this was hard to do due to the old testing framework we had, which is one of the reasons for replacing the mocking framework with the new unit test framework. So this have no big obstacle left, seems like a good first issue to me. Inspiration can also be drawn from my first attempt linked in the timeline

Is this issue still make sense? I want to try it.


Replace Ansible with SQLAlchemy/PyMySQL for database creation and management.

This commit removes the dependency on Ansible for the creation and management of databases for OpenStack Services. It adds a small python script that utilizes PyMySQL via SQLAlchemy, two libraries that are present in every OpenStack Service Container regardless of origin.
It builds on the commits in the following PRs, which should be reviewed prior to this:

https://github.com/att-comdev/openstack-helm/pull/130
https://github.com/att-comdev/openstack-helm/pull/131
https://github.com/att-comdev/openstack-helm/pull/132

The new commit introduced in this review is: https://github.com/att-comdev/openstack-helm/pull/133/commits/3929b12c5ab57c5a4a98be6998723b55dada3b64

This change is

Superceeded by: https://github.com/att-comdev/openstack-helm/pull/140


Support template into_toml members (Issue #255)

Add a has_template_into_toml_member trait to support constructing or assigning to toml::basic_value with template into_toml method, as in the doc and Issue #255.

The code looks perfect!
Although CI does not run here (maybe because the last commit is auto-update of single-include with [skip ci] keyword), it seems to pass the CI tests in your repo (https://github.com/CDK6182CHR/toml11/actions/runs/10017135670). We can run CI here by pushing an empty commit to your repo, but I think we don't need it because ci scripts have no change.


[SOK] Update ReadMe and re-test DLRM performance.

 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.Weida Yang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


The typeString function doesn't work for special characters selected with the SHIFT key under Windows

The typeString() function can't handle special characters that were selected via the SHIFT keys.
It works OK for alphabetical characters both upper and lower case.
Example:
var robot = require('robotjs');

setTimeout(
	function () {
		robot.typeString(":::::::::::::::::");
	},
	5000
);

Output
;;;;;;;;;;;;;;;;;

The timeout gives you 5 seconds in which to select a text box. This will then insert semicolons into the focused text box.
After investigating this further it appears that any special character that is selected with the SHIFT key is passed through as if SHIFT was not pressed.
Another example:
robot.typeString("!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!");

Output:
1111111111111111111111111111111

I'm going to attempt to fix this, but if anyone can give me any idea why this might happen please let me know.

I've traced this problem to the function MMKeyCode keyCodeForChar(const char c). It calls VkKeyScan which converts a character to a key code. The returned key code contains the modifiers (eg SHIFT in my case) but the modifiers are ignored because they are not processed into the (presumably cross-platform) format that Robotjs expects.

I've submitted a pull request #110 to fix this issue.

This has finally been merged! Thanks again @ashleydavis!!

This made it into v0.3.4, and it seems to be working great!


proxy authentication still not configurable

Can't have proxy authentication working with next configuration:
[httpd]
authentication_handlers = {couch_httpd_auth, cookie_authentication_handler}, {couch_httpd_auth, proxy_authentication_handler}, {couch_httpd_auth, default_authentication_handler}

Expected Behavior

I have "testdb" with next "_security" document:
{
    "admins": {
        "names": [
            "testuser"
        ]
    },
    "members": {
        "names": [
            "testuser"
        ]
    }
}

I need to send any requests to "testdb" with header: "X-Auth-CouchDB-UserName: testuser" and get success responses:)
Current Behavior

but all I have is:
{
    "error": "unauthorized",
    "reason": "You are not authorized to access this db."
}

also sending GET request to "/_session" it responses with:
{
    "ok": true,
    "userCtx": {
        "name": null,
        "roles": []
    },
    "info": {
        "authentication_db": "_users",
        "authentication_handlers": [
            "cookie",
            "default"
        ]
    }
}

so no "proxy" in authentication_handlers
Also I should mention that I've tried both with require_valid_user=true and false
I was waiting so long for 2.1.0 expecting proxy_authentication to be fixed... I need it for my app...
I can't believe I have to get back to 1.6.1 again:(
Does anyone have the same issue?
I'm using express app as a middleware between client and couchdb.
As possible solution of this problem I'm thinking about generating couchdb cookie on the fly... but it seems overwhelmed to me. Proxy authentication should just work as it is in 1.6.1
Your Environment

Version used: CouchDB 2.1.0
Browser Name and version: Chrome 60
For sending requests I use: Postman 5.1.3
Operating System and version: Mac OS 10.12.5

Our test passes, so this looks like you're missing the correct information (and our documentation is probably out of date).
Use the following stanzas:
[httpd]
authentication_handlers = {chttpd_auth, proxy_authentification_handler}, {chttpd_auth, default_authentication_handler}

[chttpd_auth]
authentication_db = _users
x_auth_username = X-Auth-CouchDB-Username
x_auth_roles = X-Auth-CouchDB-Roles
x_auth_token = X-Auth-CouchDB-Token
proxy_use_secret = false
secret = secret

See https://github.com/apache/couchdb/blob/master/test/javascript/tests/proxyauth.js#L108-L131

Thanks a lot for your answer.
I've tried this configuration, but nothing's changed.
here is my configuration:

list of dbs

GET /test/_security with basic authentication (by the way I also get this bug with error and reason)

I've noticed that this error and reason appears only if I add "testuser" twice via fauxton (it doesn't  show already added admins and members)
GET /_session with proxy header

GET /test with proxy header

There is currently a bug with setting a database's _security object using Fauxton - see https://github.com/apache/couchdb/issues/741 for details. Try setting it correctly using something like curl and try again?

Yes, when I use cURL or postman to set up _security document there is no bugs...
Anyway, problem with _security  not worries me as much as problem with proxy authentication.

}

proxy not working...
Today I've also tried the same operations on Windows 10 with postman and got exactly the same results.

Our test passes, so this looks like you're missing the correct information (and our documentation is probably out of date).

But according to this, it doesn't look like Proxy authentication is implemented yet.
Is that the case or am I doing something wrong?
My config:
[httpd]
authentication_handlers = {chttpd_auth, proxy_authentication_handler}, {chttpd_auth, default_authentication_handler}

[chttpd_auth]
x_auth_username = X-Auth-CouchDB-UserName
x_auth_roles = X-Auth-CouchDB-Roles
x_auth_token = X-Auth-CouchDB-Token
authentication_db = _users
proxy_use_secret = false
secret = secret

I had the same issue and then  I moved  authentication_handlers from [httpd] instead of  [chttpd] and now proxy auth works for me.  Perhaps the doco is wrong ( or it's a bug and it's looking in the wrong section

@gbiellem, thanks! I've tried your approach and it changed nothing. Proxy authentication still is not working for me.
Now I actually rolled back to 1.6.1 and it works fine:)
Since title of this issue is changed, I'm going to wait until docs will be updated and then try it out.
@wohali, should I close this issue?

No, please - clearly we need to update our docs.

@gbiellem Are you running in cluster mode or in single mode?

@domachine single mode

Documentation bug fixed via apache/couchdb-documentation#167.
@S-Aggarwal your problem is that you need to change this:
[httpd]
authentication_handlers = {chttpd_auth, proxy_authentication_handler}, {chttpd_auth, default_authentication_handler}

to this:
[chttpd]
authentication_handlers = {couch_httpd_auth, cookie_authentication_handler}, {couch_httpd_auth, proxy_authentication_handler}, {couch_httpd_auth, default_authentication_handler}

I came here via the current docker official couchdb installation (2.3.1) - still in its default configuration, couchdb has
[httpd]
{couch_httpd_auth, cookie_authentication_handler}, {couch_httpd_auth, default_authentication_handler}

and if I delete this entry in favour of the [chttpd] one - couchdb instantly terminates

https://docs.couchdb.org/en/stable/api/server/authn.html#proxy-authentication has the correct information, note the configuration is slightly different than what you tried.

I also ended up because of confusion with the default configuration of the Docker image for Couch which only has authentication_handlers defined in the httpd section, while the Couch docs only mention that config parameter under chttpd.
Does anybody know if authentication_handlers can/should still be defined on both sides of it if only exists/is relevant in the chttpd section?
I'd like to set a good security baseline for our production instance.


Add another button "About" in NavBar with the Functionality to access the About the portfolio

Currently, the navbar is missing an "About" button to direct users to the portfolio's "About" section. This task involves adding a new "About" button to the navbar and ensuring it navigates users to the About section of the portfolio, providing details about the portfolio owner.
Name : Manan Malik
Participant Role : Hacktoberfest
Please provide issue to me under the Hacktoberfest

@alainQtec can't find the js fils for the repo please help

can you add the tag of hacktoberfest before assigning

@alainQtec can't find the js fils for the repo please help

bruh.. what repo ?!

If you mean my portfolio, I will make be making it Public very soon.
hours actually :)


Top layer thickness & flux distribution

As discussed in Gwyther 2021, layer thickness has a big impact on melt rates; the method for mixing melt fluxes downwards is also important for melt rates. We compared ROMS, COCO and MPAS-O, but ISOMIP+ has more implementations. We should at least include some discussion of how the other models implement model z_top thickness/model boundary layer parameterisation, and the implications for melting.

Another relevant paper for this discussion is Scott et al. 2023.  They show convergence with high vertical resolution (and without tuning heat and salt transfer coefficients) to a lower melt rate, consistent with ROMS.  They assert that this is consistent with the constant background diffusivity prescribed by the experimental design (i.e. lack of enhanced turbulent mixing as one would presumably have in a resolved boundary layer).
Would be fun to discuss this further both in the Hackathon and in the paper.


setTypeface to buttons

Hi,is it possible to add setTypeface methode for buttons in java code? just for setting typeface to buttons i have copied your library file into my project to customize the typeface. I want to add your library in gradle  of my project.
thank you

I have the same issue


Make fipsinstall -out flag optional

If -out is not specified, send output to stdout.
Fix documentation errors.
Remove "-out -" from an invocation.
This also fixes #14612.

Starting a build/test on NonStop x86 for this PR

This change works on NonStop x86 with FIPS. Thank you.

@DDvO is this Appveyor issue possiblly related to one of your changes.. (Could have been a while ago - considering how long Appveyor is being queued lately). A windows backslash issue maybe?

Wish Appveyor didn't queue for so long..

@DDvO is this Appveyor issue possiblly related to one of your changes.. (Could have been a while ago - considering how long Appveyor is being queued lately). A windows backslash issue maybe?

Sorry for that - this is meanwhile fixed by #14636.

Wish Appveyor didn't queue for so long..

Indeed, though it's not Appveyor but the current use of nmake - for that, see also #10752 .

Unfortunately the currently queued AppVeyor run will fail due to the unrelated issue #14622 that is meanwhile fixed.
So I suggest cancelling the current CI run by rebasing this PR on that fix and force-pushing.

Seems to have the necessary approvals above so adding "approval done"

Rebased and pushed to pick up the windows fix.  No code changes.

Rebased and pushed to pick up the windows fix. No code changes.

This time your PR suffers from the same AppVeyor error as other current PRs:
Unable to resolve package source 'https://www.powershellgallery.com/api/v2'.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Rebased and pushed to pick up the windows fix. No code changes.

This time your PR suffers from the same AppVeyor error as other current PRs:
Unable to resolve package source 'https://www.powershellgallery.com/api/v2'.

Is it possible that #14660 is contributing to this?

Is it possible that #14660 is contributing to this?

I think Appveyor's current problems are independent of #14660

Is it possible that #14660 is contributing to this?

I think Appveyor's current problems are independent of #14660

Silly question: Should there not be a -Name argument before VSSetup?

@rsbecker, -Name is optional according to docs

Merged
eb78f9552307248ca5ccfc28d61faa823dae7c7e Make fipsinstall -out flag optional

@rsbecker, -Name is optional according to docs

Another ironic possibility. There was a recent SSL cert change on the powershell site (05 Mar 2021). Is it possible github does not have an up to date certificate? ;)

Is it possible github does not have an up to date certificate? ;)

You mean appveyor.  Yes, that's perfectly possible.  Either way, it's obvious that something isn't right, but that it's also outside of our control.  We can only wait...  and possibly notify appveyor of the problem


Powerstate

Codecov Report

Merging #72 (ee8217e) into master (3efa759) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #72   +/-   ##
======================================
  Coverage    4.45%   4.45%
======================================
  Files          14      14
  Lines        1213    1213
======================================
  Hits           54      54
  Misses       1152    1152
  Partials        7       7

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3efa759...ee8217e. Read the comment docs.


GPyOpt BayesianOptimization Fails to complete execution after initial_design_numdata iterations.

I am trying to use the parallel GPyOpt using the instructions on the following notebook:
http://nbviewer.jupyter.org/github/SheffieldML/GPyOpt/blob/master/manual/GPyOpt_parallel_optimization.ipynb
The notebook itself runs without any issues. In my case, I only change the objective function to a Neural Network using Keras library (with TensorFlow backend). And consequently, I change the hyper-parameters' domain into something like this:
domain =[{'name': 'num_hidden_layers', 'type': 'discrete', 'domain': (1,2,3)},
{'name': 'num_neurons', 'type': 'discrete',
'domain': tuple(range(1,21)),'dimensionality': 3},
{'name': 'learning_rate', 'type': 'discrete',
'domain': tuple(np.logspace(np.log10(0.001), np.log10(1), num=10))},
{'name': 'l2_reg', 'type': 'discrete',
'domain': tuple(np.logspace(np.log10(0.001), np.log10(1), num=10))},
{'name': 'batch_size', 'type': 'discrete', 'domain': tuple(range(1,51))},
{'name': 'dropout', 'type': 'continuous',
'domain': (0.01,0.99), 'dimensionality': 3}]
This has mixed_type variables.
But for some reason, After I call the BayesianOptimization method as follows:
num_cores, batch_size = 1, 1
GPyOpt.methods.BayesianOptimization(f=fcnet_regression_loss,  (this outputs neural network validation accuracy)
domain = domain,
acquisition_type = 'EI',
normalize_Y = True,
initial_design_numdata = 10,
evaluator_type = 'local_penalization',
batch_size = batch_size,
num_cores = num_cores,
acquisition_jitter = 0)
After 10 iterations, the notebook crashes and shuts down the Jupyter kernel.
I couldn't still figure out what causes this problem.

If I change the domain into 'continuous' type variables only, i.e.,
mixed_domain =[{'name': 'num_hidden_layers', 'type': 'continuous', 'domain': (0.9,3.1)},
{'name': 'num_neurons', 'type': 'continuous',
'domain': (1,21),'dimensionality': 3},
{'name': 'learning_rate', 'type': 'continuous',
'domain': (0.1,0.9)},
{'name': 'l2_reg', 'type': 'continuous',
'domain': (0.1,0.9)},
{'name': 'batch_size', 'type': 'continuous', 'domain': (5,51)},
{'name': 'dropout', 'type': 'continuous',
'domain': (0.01,0.99), 'dimensionality': 3}]
Then the optimization converges.
Also, for mixed type domains, with both discrete and continuous type variables, if I choose the discrete sets very small (in order of two or three elements each) then algorithm converges, but it is very slow.

Hi,there @amohar2
Thank you for your work,I'm interested in your work that you changed the objective function to a Neural Network using Keras library,could you tell me how did you define the fcnet_regression_loss? Because I wrote a func,which is used for optimize the Neural Network,but it did not work.
Looking forward to your apply
thank you very much


[libjulia_jll] Fix libjulia_jll for Julia v1.7

At the moment, with Julia v1.7 we get:
(jl_h4pidc) pkg> add libjulia_jll
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package libjulia_jll [5ad3ddd2]:
 libjulia_jll [5ad3ddd2] log:
 ├─possible versions are: 1.3.1-1.7.0 or uninstalled
 ├─restricted to versions * by an explicit requirement, leaving only versions 1.3.1-1.7.0
 ├─restricted by compatibility requirements with GMP_jll [781609d7] to versions: [1.3.1, 1.5.1-1.7.0] or uninstalled, leaving only versions: [1.3.1, 1.5.1-1.7.0]
 │ └─GMP_jll [781609d7] log:
 │   └─possible versions are: 6.2.1 or uninstalled
 ├─restricted by compatibility requirements with PCRE2_jll [efcefdf7] to versions: 1.5.4-1.7.0 or uninstalled, leaving only versions: 1.5.4-1.7.0
 │ └─PCRE2_jll [efcefdf7] log:
 │   └─possible versions are: 10.36.0 or uninstalled
 └─restricted by compatibility requirements with libLLVM_jll [8f36deef] to versions: 1.3.1 or uninstalled — no versions left
   └─libLLVM_jll [8f36deef] log:
     └─possible versions are: 12.0.1 or uninstalled

The problem is that libjulia_jll v1.7 says it's compatible with libLLVM_jll 11:
https://github.com/JuliaRegistries/General/blob/1bef9ca01489022d8065aa3d8fe86bbc835a11bd/L/libjulia_jll/Compat.toml#L45
but this is wrong, because Julia v1.7 eventually had LLVM 12: https://github.com/JuliaRegistries/General/blob/1bef9ca01489022d8065aa3d8fe86bbc835a11bd/L/libLLVM_jll/Compat.toml#L7-L8
I'm not sure what's the best fix: fixing compatibility with libLLVM_jll (but older builds libjulia_jll will likely not work anymore) or yank old builds of libjulia_jll v1.7.0 and just remove dependency on libLLVM_jll, since libjulia_jll v1.7 doesn't actually depend on libLLVM_jll.  CC @fingolfin who I think may have useful ideas

Yank older versions imo, since they only existed during the dev period and the only released version of Julia 1.7 is using LLVM 12. But yeah we often don't declare the dependency on libLLVM since it seems problematic...

Ok, I yanked all older versions and removed some dependencies no longer used in the JLL package.  With this PR in julia v1.7 I can install the package
(tmp) pkg> add libjulia_jll
    Updating registry at `~/.julia/registries/General`
    Updating git-repo `https://github.com/JuliaRegistries/General.git`
┌ Error: Some registries failed to update:
│     — /home/mose/.julia/registries/General — branch origin/mg/libjulia not found
└ @ Pkg.Registry /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.7/Pkg/src/Registry/Registry.jl:450
   Resolving package versions...
    Updating `/tmp/Project.toml`
  [5ad3ddd2] + libjulia_jll v1.7.0+8
    Updating `/tmp/Manifest.toml`
  [692b3bcd] + JLLWrappers v1.4.0
  [21216c6a] + Preferences v1.2.3
  [5ad3ddd2] + libjulia_jll v1.7.0+8
  [0dad84c5] + ArgTools
  [56f22d72] + Artifacts
  [2a0f44e3] + Base64
  [ade2ca70] + Dates
  [f43a241f] + Downloads
  [b77e0a4c] + InteractiveUtils
  [b27032c2] + LibCURL
  [76f85450] + LibGit2
  [8f399da3] + Libdl
  [56ddb016] + Logging
  [d6f4376e] + Markdown
  [ca575930] + NetworkOptions
  [44cfe95a] + Pkg
  [de0858da] + Printf
  [3fa0cd96] + REPL
  [9a3f8284] + Random
  [ea8e919c] + SHA
  [9e88b42a] + Serialization
  [6462fe0b] + Sockets
  [fa267f1f] + TOML
  [a4e569a6] + Tar
  [cf7118a7] + UUIDs
  [4ec0a83e] + Unicode
  [deac9b47] + LibCURL_jll
  [29816b5a] + LibSSH2_jll
  [183b4373] + LibUV_jll
  [745a5e78] + LibUnwind_jll
  [c8ffd9c3] + MbedTLS_jll
  [14a3606d] + MozillaCACerts_jll
  [83775a58] + Zlib_jll
  [8e850ede] + nghttp2_jll
  [3f19e933] + p7zip_jll


Can we provide a callback instead of providing serverURL

Hi Team,
I need to pass a custom body with some headers to the license server.
I am not able to active this using the Videojs-contrib-dash as I am not able to find a way to intercept the license call.
Please help me, Many thanks
Vikas Bansal

This is something you need to ask the dash.js folks as license requests are handled by that library, not videojs-contrib-dash.


[WIP][SPARK-32802][SQL] Avoid using SpecificInternalRow in RunLengthEncoding#Encoder

What changes were proposed in this pull request?

Currently RunLengthEncoding#Encoder uses SpecificInternalRow as a holder for the current value when calculating compression stats and doing the actual compression. It calls ColumnType.copyField and ColumnType.getField on the internal row which incurs extra cost comparing to directly operating on the internal type. This proposes to replace the SpecificInternalRow with T#InternalType to avoid the extra cost.
Why are the changes needed?

Operating on SpecificInternalRow carries certain cost and negatively impact performance when using RunLengthEncoding for compression.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Relies on existing unit tests.

Test build #128322 has started for PR 29654 at commit f3f6fc5.

Merged build finished. Test PASSed.

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

Test build #128322 has finished for PR 29654 at commit f3f6fc5.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #128422 has started for PR 29654 at commit 903992b.

Merged build finished. Test PASSed.

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

Test build #128422 has finished for PR 29654 at commit 903992b.

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

Merged build finished. Test PASSed.

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

Test build #128432 has started for PR 29654 at commit 2e18856.

Merged build finished. Test PASSed.

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

Test build #128432 has finished for PR 29654 at commit 2e18856.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

@maropu could you review this PR? thanks!

Have you checked the performance on jdk8, too? Could you update the golden files?

benchmarks/CompressionSchemeBenchmark-results.txt
benchmarks/CompressionSchemeBenchmark-jdk11-results.txt

I don't know enough to review the logic but it looks plausible.

Looks good. I have one question.

Have you checked the performance on jdk8, too? Could you update the golden files?

benchmarks/CompressionSchemeBenchmark-results.txt
benchmarks/CompressionSchemeBenchmark-jdk11-results.txt

Haven't checked jdk8. Let me do that and update the golden files.

Test build #128582 has started for PR 29654 at commit bcda6c2.

Merged build finished. Test PASSed.

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

cc @cloud-fan

Thanks. I think the CI failure is not related. Probably it is caused by #29640

Wait, where do you see the CI failure?

@srowen I see this in the "Python lint" section, and this happened to two of my PRs which do not touch Python at all.
I think it is just a simple fix. Let me come up with a PR quickly.

OK right I see it locally anyway. I can submit a fix, I have the PR now.

OK right I see it locally anyway. I can submit a fix, I have the PR now.

Oops. I just filed #29733

Test build #128582 has finished for PR 29654 at commit bcda6c2.

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

Merged build finished. Test PASSed.

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


feat: etcd-election support NonVoter

What this PR does / why we need it:
etcd-election support NonVoter
Specified Reivewers:
/assign @sfwn

/approve


Review and document ontology development practices

The goal of this issue is to document development practices to help collaborators understand how to contribute.
Software engineering practices are well established for management of development vs. releases, they just need to be applied to ontology development.  One possibility is to use github (e.g. this repository), as it’s the primary platform for open-source projects.  However, it assumes those who work on ontology development have an understanding of working with git (or any code versioning system) or are willing to learn it or find ways to use the github-UI to get their work done.  The use of github is one option.  Another option is the protege-web platform, which is more specific to ontology development.  There may be other options.  It should be noted that both github and protege-web have privacy management tools available.  In any case, there is an argument for application of well established software engineering practices to the ontology development process.
The concern above is related to the actual implementation and document management details, rather than the broader design and consensus process.  W3C process could be considered/adapted to ontology collaborations, esp. the way they manage proposals vs. recommendation status?  Also wondering how schema.org manage things.
Some relevant OWL documents on versioning:

https://www.w3.org/2007/OWL/wiki/Ontology_Versions
https://www.w3.org/TR/owl2-syntax/#Ontology_IRI_and_Version_IRI
https://www.w3.org/TR/owl2-syntax/#Versioning_of_OWL_2_Ontologies

Relevant slide presentation on change management:

http://www.slideshare.net/badenhughes/change-management-and-versioning-in-ontologies

Interesting survey of systems for ontology development/collaboration:

http://www.mkbergman.com/906/a-brief-survey-of-ontology-development-methodologies/

Also, Tania Tudorache is the lead developer of Protege at Stanford.  She could be invited to comment on the Protege community approach to ontology development, management, versioning etc.  From Stanford Who, her public contact details are:

Email<EMAIL_ADDRESS>Web page: http://web.stanford.edu/~ttania/

Closing: not related to the ontology per se.


Color based on Feature in WebGLPoints Layer style expression not working

Describe the bug
I'm trying to render a simple point using the WebGLPoints layer in a color that is a parameter of the feature. A static color is working fine, if I use a dynamic color, the shape is not visible.
OL: 9.2.3
To Reproduce
This is my style:
style: {
"shape-points" : 4,
"shape-radius" : ['get', 'size', "number"],
"shape-fill-color" : ['get', 'colorValue', "color"],
'shape-rotation' : 0.785,
'shape-opacity': 1,
}
And I set the parameters like this on the feature before adding it to the layer source:
feature.set("size",10)
feature.set("colorValue", "red")
Setting the size works as expected. Using a static color like
"shape-fill-color" : "red"
works without problem.
Setting "shape-fill-color" : ['get', 'colorValue', "string"] results in the correct error message:
Error: The following expression was expected to return color, but returns string instead: ["get","colorValue","string"]
Setting the colorValue like  feature.set("colorValue", "'red'") results in
Uncaught Error Error: Failed to parse "'red'" as color
so something is parsed and used
Expected behavior
I would like to color each point individually if possible. https://openlayers.org/en/latest/apidoc/module-ol_expr_expression.html
does not state any limitations regarding color. Is it possible at all?

I believe you have to supply red/green/blue separately.
{
  "shape-points": 4,
  "shape-radius": ["get", "size", "number"],
  "shape-fill-color": [
    "color",
    ["get", "red"],
    ["get", "green"],
    ["get", "blue"],
  ],
  "shape-rotation": 0.785,
  "shape-opacity": 1,
}

feature.set({
  red: 255,
  green: 0,
  blue: 0,
});

As an alternative you could use the WebGL vector layer renderer https://stackblitz.com/edit/js-zpb8ez?file=package.json,index.html,index.js


Staging Commit to update Technical Documentation

Technical documentation has gone through a major rework. The main branch's README no longer reflects the README in the staging branch.

Great job updating the README. Also you somehow have all of these other features, too. Thanks!


store_pascal_string() crashes when saving an empty string

Godot version:
v3.0.5-stable_x11.64, Xubuntu
Issue description:
store_pascal_string() crashes the game when trying to save an empty string.
Steps to reproduce:
Download the example project.
Run the scene.
The game quits.
Edit the script, write anything in the currently empty string.
Run the game.
The game runs fine.
Example project:
pascal_string_bug.zip

yes, problem here is that in an empty string, doing string[0] crashes.

There's a PR open for this #21708


Define the Homebrew installation

Define the Homebrew installation.
This may go to a different project under the poof-backup umbrella, with installers for Homebrew, Debian/Ubuntu, and RH.

https://docs.brew.sh/Python-for-Formula-Authors

More background:  https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap

https://github.com/poof-backup/homebrew-poof - created.

Clearer instructions.

Homebrew Formula Cookbook


[Feature Request] High Score Cards : enter HEX for Canvas color

While creating card canvas, I need to use a color picker to find the correct color but cant find a way to the HEX for the canvas?
side note: maybe you have a color picker library to build in... not important just a thought.

I've hidden the link to custom colors, because there have been focus issues with the build in color picker dialog.
I just retested this and while the dialog behaves strange, it does what it is intended to do, so I'll re-enable it.

Solved, 2.18.3


Chatbot textfield not working in Firefox

CSS issue, the textfield not positioned correctly in a Firexfox browser, screenshot attached.
Perhaps absolute positioning, 45px from the bottom, with explicit 100% width. This fixes for firefox, haven't tested on other browsers. Chrome works fine out of the box as you probably know.
Problem Highlight

Proposed Changes:

Fixed:

https://github.com/botfront/botfront/commit/882d2b9582be5c2a69021f85426b2eba5cb0bed3


How to properly bind to ViewModel data that is avaialbe after Awake?

This seems like a a great library, and I might be severely missing the point, but I don't see a way out of the box to support binding to ViewModels that have their data populated after Awake (since initializiation for binders seems to happen on Awake).
e.g.

when the ViewModel is created at runtime, and then initialized (since Unity doesn't allow initializing a GameObject before Awake except if it's disabled, and that's an ugly flow for prefabs)
or even, using IViewModelProvider to have POCO VMs, as you suggested in previous issue replies: how can GetViewModel return a valid non-MonoBehaviour instance that's somehow injected into the MonoBehaviour (ony way I see is you'd have to call some static singleton-ish provider class from within the method for it to happen before Awake, and I'd like to be able to stick with a DI flow)

Adding [DefaultExecutionOrder(100)] to AbstractMemeberBinding fixes it for VMs already in the scene at lauch, but it doesn't work for those created at runtime.
Any insights welcome! Thanks!

Ok, modifying AbstractMemberBinding to call Init() in "Start" rather than "Awake" seems to do the trick. Are there any pitfalls to this change in the context of the library?


Voting via a Proxy

No option for Voting via a Proxy

I agree with this request to add voting via a proxy.  If you join our discord I'll get our community to give you tips.  https://discord.gg/UnE6z96


4.26 support

Hi, would it be possible for you to add 4.26 support? It does not seem to work on 4.26.

@SavannahGames
Could you tell me the problems on 4.26?
It would help me to fix the issue.

@SavannahGames
Could you tell me the problems on 4.26?
It would help me to fix the issue.

"ProjectName could not be compiled. Try rebuilding from source manually".  I have tried to regenerate visual studio project files many times, still this issue comes up.
C:/Users/Admin/Desktop/UnrealEngine4/NoiseBlueprint/Plugins/NoiseBlueprintLibrary/Source/NoiseBlueprintLibrary/Private/PerlinNoise/PerlinNoiseBPLibrary.cpp(1): fatal error C1083: Cannot open include file: 'PerlinNoiseBPLibrary.h': No such file or directory -- this also comes up, even when I put the header file there, it says suppressed.lib & refuses to compile, says "critical error"

@SavannahGames
Thanks!
I will check it.

@SavannahGames
Thanks!
I will check it.
Just wanted to let you know that I tested it on 4.22 and it works flawlessly. 4.26 does not want to seem to work at all. so 4.26 definitely needs some repairing or rewriting of code.

This error is now resolved by using master branch's source codes.
Thanks for your report @SavannahGames !


DSD-1444: Updating Storybook documentation for Logo component

Fixes JIRA ticket DSD-1444
This PR does the following:

Updates the Logo component Storybook documentation to version 7.
Compare with prod: https://nypl.github.io/nypl-design-system/reservoir/v1/?path=/docs/components-media-icons-logo--logo-with-controls

A few notes that maybe @bigfishdesign13 you can help with:
1 I'm not sure if it's the vite plugin but each SVG gets an additional width and height attribute and throws off how its rendered:

2 The SimplyE svgs don't render correctly and I can't figure out why.

How has this been tested?
Locally.
Accessibility concerns or updates

N/A

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[ ] All new and existing tests passed.

Front End Review:

[ ] Review the Vercel preview deployment once it is ready.

@EdwinGuzman I am just digging into this now.  As you noted, explicit height and width attributes are being added to the SVGs in the Logo component.  This is also happening to the SVGs in the Icon component, but those are square and there is no visible impact.  I will see what I can find.

@bigfishdesign13 take a look. The logos are rendering better now. All the "simplye" logos are still cut off and I don't think it's related to this PR since the rest of the logos are rendering fine. It seems there's some sort of clip or reference that may not work in the SVG markup.


Add phone input component

Refer to https://linear.app/cardstack/issue/CS-7589/create-phoneinput-component
What is changing

add phone input component in boxel-ui

Examples
Searchable country selector

Valid state

Invalid state

Notes

country list and phone number libraries are lived inside in boxel-ui as discussed in boxel team meeting
we used awesome-phonenumber instead of  libphonenumber-js. Though libphonenumber-js its more popular but the awesome-phonenumber suggest improvement in bundle sizes etc

Looks good thanks


Fixes -error not suppressing startup logs

Fixes #3849
This brings back the 0.13 logic:
  def setGlobalLogLevel(s: State, level: Level.Value): State = {
    s.globalLogging.full match {
      case a: AbstractLogger => a.setLevel(level)
      case _                 => ()
    }
    s.put(BasicKeys.explicitGlobalLogLevels, true).put(Keys.logLevel.key, level)
  }

is this just an idea, or was it manually tested to fixed the issue?

Manually tested and confirmed.


tests: drivers: counter: counter_nrf_rtc: Run test on nrf54h20

Add nrf54h20dk to platform allow list.
Overlay for tht target was already added.

FYI: @nordic-piks , @nordic-krch , @anangl


Sarama won't build when cross compiling

Versions
Sarama version: 8eafb3ab902d1aca96eb14d605fdd64b6d2dccf0
Go Version: 1.7.1
Problem Description
I have a program that depends on Sarama. It includes it vendored in its directory. Then I go to compile it with
GOOS=darwin GOARCH=amd64 go build -v -o
and I get a build error:
musher/vendor/github.com/Shopify/sarama
src/goloaders/src/musher/vendor/github.com/Shopify/sarama/async_producer.go:59: undefined: Broker
src/goloaders/src/musher/vendor/github.com/Shopify/sarama/client.go:33: undefined: Broker
src/goloaders/src/musher/vendor/github.com/Shopify/sarama/client.go:53: undefined: Broker

Actually, turns out it was on an in-house variant which takes cgo dependencies. I'm going to close this.


Make custom containers' default labels configurable by locale config

https://github.com/vuejs/vuepress/issues/659

https://github.com/vuepress/vuepress-plugin-container#defaulttitle


[BUG]: UseDotNet@2 installs a weird mix of build and runtime SDKs for dotnet 6.* - caused DotNetCoreCLI@2 "dotnet restore" failure

Task name
UseDotNet
Task version
2.228.0
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server 2016 Standard & 2012 R2
Task log
Starting: Install dotnet if not already present
==============================================================================
Task         : Use .NET Core
Description  : Acquires a specific version of the .NET Core SDK from the internet or the local cache and adds it to the PATH. Use this task to change the version of .NET Core used in subsequent tasks. Additionally provides proxy support.
Version      : 2.228.0
Author       : Microsoft Corporation
Help         : https://aka.ms/AA4xgy0
==============================================================================
Tool to install: .NET Core sdk version 6.x.
Found version 6.0.416 in channel 6.0 for user specified version spec: 6.x
Version: 6.0.416 was found in cache.
Creating global tool path and pre-pending to PATH.
Finishing: Install dotnet if not already present

Relevant log output
#[section]Starting: dotnet restore
=============================================================================
ask         : .NET Core
escription  : Build, test, package, or publish a dotnet application, or run a custom dotnet command
ersion      : 2.221.0
uthor       : Microsoft Corporation
elp         : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli
=============================================================================
command]C:\Windows\system32\chcp.com 65001
ctive code page: 65001
nfo: .NET Core SDK/runtime 2.2 and 3.0 are now End of Life(EOL) and have been removed from all hosted agents. If you're using these SDK/runtimes on hosted agents, kindly upgrade to newer versions which are not EOL, or else use UseDotNet task to install the required version.
command]AGENT_HOMEDIRECTORY\_work\_tool\dotnet\dotnet.exe restore REDACTED_PROJECT_PATH --configfile AGENT_HOMEDIRECTORY\_work\18\Nuget\tempNuGet_118721.config --verbosity Diagnostic
GENT_HOMEDIRECTORY\_work\_tool\dotnet\sdk\6.0.416\MSBuild.dll -nologo -distributedlogger:Microsoft.DotNet.Tools.MSBuild.MSBuildLogger,AGENT_HOMEDIRECTORY\_work\_tool\dotnet\sdk\6.0.416\dotnet.dll*Microsoft.DotNet.Tools.MSBuild.MSBuildForwardingLogger,AGENT_HOMEDIRECTORY\_work\_tool\dotnet\sdk\6.0.416\dotnet.dll -maxcpucount -property:RestoreConfigFile=AGENT_HOMEDIRECTORY\_work\18\Nuget\tempNuGet_118721.config -target:Restore -verbosity:m -verbosity:diagnostic REDACTED_PROJECT_PATH.csproj
uild started 10/26/2023 6:37:04 PM.
8:37:06.636   1:5>ProcessFrameworkReferences: (TargetId:41)
Output Item(s):
_PackageToDownload=
Microsoft.NETCore.App.Runtime.Mono.browser-wasm
Version=6.0.24 (TaskId:39)

PackageConflictPreferredPackages=Microsoft.NETCore.App.Ref;Microsoft.NETCore.App.Runtime.Mono.linux-arm;Microsoft.NETCore.App.Runtime.Mono.linux-arm64;Microsoft.NETCore.App.Runtime.Mono.linux-musl-arm64;Microsoft.NETCore.App.Runtime.Mono.linux-musl-x64;Microsoft.NETCore.App.Runtime.Mono.linux-x64;Microsoft.NETCore.App.Runtime.Mono.osx-x64;Microsoft.NETCore.App.Runtime.Mono.rhel.6-x64;Microsoft.NETCore.App.Runtime.Mono.win-arm;Microsoft.NETCore.App.Runtime.Mono.win-arm64;Microsoft.NETCore.App.Runtime.Mono.win-x64;Microsoft.NETCore.App.Runtime.Mono.win-x86;Microsoft.NETCore.App.Runtime.Mono.linux-musl-arm;Microsoft.NETCore.App.Runtime.Mono.osx-arm64;Microsoft.NETCore.App.Runtime.Mono.maccatalyst-x64;Microsoft.NETCore.App.Runtime.Mono.maccatalyst-arm64;Microsoft.NETCore.App.Runtime.Mono.linux-s390x;Microsoft.NETCore.App.Runtime.Mono.browser-wasm;Microsoft.NETCore.App.Runtime.Mono.ios-arm64;Microsoft.NETCore.App.Runtime.Mono.ios-arm;Microsoft.NETCore.App.Runtime.Mono.iossimulator-arm64;Microsoft.NETCore.App.Runtime.Mono.iossimulator-x64;Microsoft.NETCore.App.Runtime.Mono.iossimulator-x86;Microsoft.NETCore.App.Runtime.Mono.tvos-arm64;Microsoft.NETCore.App.Runtime.Mono.tvossimulator-arm64;Microsoft.NETCore.App.Runtime.Mono.tvossimulator-x64;Microsoft.NETCore.App.Runtime.Mono.android-arm64;Microsoft.NETCore.App.Runtime.Mono.android-arm;Microsoft.NETCore.App.Runtime.Mono.android-x64;Microsoft.NETCore.App.Runtime.Mono.android-x86
PackageDirectory=AGENT_HOMEDIRECTORY\_work\_tool\dotnet\packs\Microsoft.NETCore.App.Ref\6.0.24
Path=AGENT_HOMEDIRECTORY\_work\_tool\dotnet\packs\Microsoft.NETCore.App.Ref\6.0.24
RuntimeFrameworkName=Microsoft.NETCore.App
RuntimePackRuntimeIdentifiers=linux-arm;linux-arm64;linux-musl-arm64;linux-musl-x64;linux-x64;osx-x64;rhel.6-x64;win-arm;win-arm64;win-x64;win-x86;linux-musl-arm;osx-arm64;maccatalyst-x64;maccatalyst-arm64;linux-s390x;browser-wasm;ios-arm64;ios-arm;iossimulator-arm64;iossimulator-x64;iossimulator-x86;tvos-arm64;tvossimulator-arm64;tvossimulator-x64;android-arm64;android-arm;android-x64;android-x86
TargetFramework=net6.0
TargetingPackFormat=
Microsoft.WindowsDesktop.App
NuGetPackageId=Microsoft.WindowsDesktop.App.Ref
NuGetPackageVersion=6.0.24

Output Item(s):
RuntimePack=
Microsoft.NETCore.App.Runtime.Mono.browser-wasm
FrameworkName=Microsoft.NETCore.App
IsTrimmable=
NuGetPackageId=Microsoft.NETCore.App.Runtime.Mono.browser-wasm
NuGetPackageVersion=6.0.24
RuntimeIdentifier=browser-wasm (TaskId:39)

Restoring packages for REDACTED_PROJECT_PATH.csproj... (TaskId:65)
Restoring packages for .NETCoreApp,Version=v6.0... (TaskId:65)
Resolving conflicts for net6.0... (TaskId:65)
GET ***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0 (TaskId:65)
BadRequest ***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0 40ms (TaskId:65)
Retrying 'FindPackagesByIdAsyncCore' for source '***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0'.
Response status code does not indicate success: 400 (Bad Request). (TaskId:65)
Enhanced retry: HttpRetryHandler is in a state that retry would have been abandoned or not waited if it were not enabled. (TaskId:65)
GET https://api.nuget.org/v3-flatcontainer/microsoft.netcore.app.runtime.mono.browser-wasm/index.json (TaskId:65)

OK https://api.nuget.org/v3-flatcontainer/microsoft.netcore.app.runtime.mono.browser-wasm/index.json 138ms (TaskId:65)
Acquiring lock for the installation of Microsoft.NETCore.App.Runtime.Mono.browser-wasm 6.0.24 (TaskId:65)
Acquired lock for the installation of Microsoft.NETCore.App.Runtime.Mono.browser-wasm 6.0.24 (TaskId:65)
GET https://api.nuget.org/v3-flatcontainer/microsoft.netcore.app.runtime.mono.browser-wasm/6.0.24/microsoft.netcore.app.runtime.mono.browser-wasm.6.0.24.nupkg (TaskId:65)
OK https://api.nuget.org/v3-flatcontainer/microsoft.netcore.app.runtime.mono.browser-wasm/6.0.24/microsoft.netcore.app.runtime.mono.browser-wasm.6.0.24.nupkg 7ms (TaskId:65)
GET ***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0 (TaskId:65)
BadRequest ***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0 19ms (TaskId:65)
Retrying 'FindPackagesByIdAsyncCore' for source '***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0'.
Response status code does not indicate success: 400 (Bad Request). (TaskId:65)
Enhanced retry: HttpRetryHandler is in a state that retry would have been abandoned or not waited if it were not enabled. (TaskId:65)
PackageSignatureVerificationLog: PackageIdentity: Microsoft.NETCore.App.Runtime.Mono.browser-wasm.6.0.24 Source: https://api.nuget.org/v3/index.json PackageSignatureValidity: True (TaskId:65)
GET ***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0 (TaskId:65)
BadRequest ***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0 17ms (TaskId:65)
8:37:09.399     1>REDACTED_PROJECT_PATH.csproj : error NU1301: Failed to retrieve information about 'Microsoft.NETCore.App.Runtime.Mono.browser-wasm' from remote source '***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0'.
8:37:09.399     1>REDACTED_PROJECT_PATH.csproj : error NU1301: Failed to retrieve information about 'Microsoft.NETCore.App.Runtime.Mono.browser-wasm' from remote source '***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0'.
Installed Microsoft.NETCore.App.Runtime.Mono.browser-wasm 6.0.24 from https://api.nuget.org/v3/index.json with content hash XC/y2xP3KKfjs36vY95ucWw+0DVB9MJJSU5jpBjo+PqIB8EHOpBrUTMeZQh0Bjox3/5AmBWKEDCov6Er1ETuQg==. (TaskId:65)

Done executing task "RestoreTask" -- FAILED. (TaskId:65)
8:37:11.179     1>Done building target "Restore" in project "REDACTED.csproj" -- FAILED.: (TargetId:75)
8:37:11.179     1>Done Building Project "REDACTED_PROJECT_PATH.csproj" (Restore target(s)) -- FAILED.

uild FAILED.

"REDACTED_PROJECT_PATH.csproj" (Restore target) (1) ->
(Restore target) ->
REDACTED_PROJECT_PATH.csproj : error NU1301: Failed to retrieve information about 'Microsoft.NETCore.App.Runtime.Mono.browser-wasm' from remote source '***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0'.
REDACTED_PROJECT_PATH.csproj : error NU1301: Failed to retrieve information about 'Microsoft.NETCore.App.Runtime.Mono.browser-wasm' from remote source '***FindPackagesById()?id='Microsoft.NETCore.App.Runtime.Mono.browser-wasm'&semVerLevel=2.0.0'.

2 Error(s)

ime Elapsed 00:00:06.79
#[error]Error: The process 'AGENT_HOMEDIRECTORY\_work\_tool\dotnet\dotnet.exe' failed with exit code 1
#[error]Packages failed to restore
nfo: Azure Pipelines hosted agents have been updated and now contain .Net 5.x SDK/Runtime along with the older .Net Core version which are currently lts. Unless you have locked down a SDK version for your project(s), 5.x SDK might be picked up which might have breaking behavior as compared to previous versions. You can learn more about the breaking changes here: https://docs.microsoft.com/en-us/dotnet/core/tools/ and https://docs.microsoft.com/en-us/dotnet/core/compatibility/ . To learn about more such changes and troubleshoot, refer here: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshooting
#[section]Finishing: dotnet restore

Aditional info
The problem appeared on 2 VMs which have been running this pipeline for nearly a year at a frequent pace. UseDotNet@2 has always been 6.x during this time so this is the first time this issue has happened.

Hardcoding version '6.1.415' worked.
Deleting the _tool\dotnet dirs also helped get the latest 6.x to work as well.

Good pairs that work: 6.0.415+6.0.23 and 6.0.416+6.0.24 - as per the dotnet release notes.
Bad pair that did not work: 6.0.415+6.0.24

Bump. Has anyone else encountered in recent times?
It still happens occasionally in my organization, but we have mitigated it.


Remove optional dependencies from requirements.txt

Closes #941
Please update your hooks after this PR is merged
Introduced changes

docs-requirements.txt was added
optional dependencies are no longer present in requirements.txt
unused sphinx-rtd-theme was removed

[ ] This PR contains breaking changes

I started to wonder if there's any point of having requirements defined at all. I think for pypi dependencies are somehow defined in the setup.py or other file - they were just there for docs I believe.

Unfortunately, I don't think there is an easy way to do so.
I've tried to upload the package without requirements.txt to test-pypi
https://test.pypi.org/project/starknet-py/
And I can't install it :/

I started to wonder if there's any point of having requirements defined at all. I think for pypi dependencies are somehow defined in the setup.py or other file - they were just there for docs I believe.

Unfortunately, I don't think there is an easy way to do so. I've tried to upload the package without requirements.txt to test-pypi
https://test.pypi.org/project/starknet-py/
And I can't install it :/

If they are necessary, let's keep them.


More settings functionality

Added add user text field to SettingsView and added the axios put request in the SetingsView.  Also updated the api routing for adding a user to user the username instead of userID

@KazyManazy we want to keep the /src/package-lock.json file but  we do not want to keep  /package-lock.json.


Enables forcing a deployment without a new commit.

This behaviour is 'dangerous' as it overwrites the previous
deployments code. But is useful for development when iterating
where you may not want to commit your changes.
Also relies on the Thor CLI defaults to populate the overrides
to allow us to handle less.
closes https://github.com/fac/serverless-tools/issues/12

@HistoireDeBabar Out of curiosity, why were the checks for already existing images/objects in ECR and S3 removed from ecr_pusher and s3_pusher?

@HistoireDeBabar Out of curiosity, why were the checks for already existing images/objects in ECR and S3 removed from ecr_pusher and s3_pusher?

It felt a little too similar and duplicated. Ultimately the responsibility of a pusher, should be to push. Extracting the 'when to push' outside of the class means that we can essentially do the checking logic once, and this can be co-ordinated by a class whose responsibility it is to do orchestration.
For example, at the pusher level - if I needed to check that there's an object/image already there, and then I also needed to consider a force flag, you'd be required to duplicate that logic in every pusher. It'd be easy to miss the implementation, or have it act differently - where one pusher doesn't force for example. So, pulling it out felt like it'd make the behaviour more consistent and easier to rationalise what the pushers were doing.

Thanks @HistoireDeBabar, that makes sense, I just realised the logic was moved to the function deployer class which is definitely a better implementation as all deployments go through it 👌