CommonJS support

Elysia 0.5 add support for CommonJS by default, this should allow us to drop the additional step of using CLI to convert Elysia modules to CommonJS.
It would be nice if would you updated the package to support CommonJS as well.

Sounds good, I will give it a try.
But I think since you introduced code analysis, it won't work without a build step (before each run) because of bun transpile step, for example:
isFnUse
// Bun
let is = isFnUse(
  'set',
  `(context) => {
    if (handleOrigin(context.set, context.request), handleMethod(context.set), exposedHeaders.length)
      context.set.headers["Access-Control-Allow-Headers"] = typeof allowedHeaders === "string" ? allowedHeaders : allowedHeaders.join(", ");
    if (maxAge)
      context.set.headers["Access-Control-Max-Age"] = maxAge.toString();
    return new Response("", {
      status: 204
    });
  }`
);

console.log(is); // true

// Node
is = isFnUse(
  'set',
  `context => {
        handleOrigin(context.set, context.request);
        handleMethod(context.set);
        if (exposedHeaders.length) context.set.headers['Access-Control-Allow-Headers'] = typeof allowedHeaders === 'string' ? allowedHeaders : allowedHeaders.join(', ');
        if (maxAge) context.set.headers['Access-Control-Max-Age'] = maxAge.toString();
        return new Response('', {
          status: 204
        });
      }`
);

console.log(is); // false

bugs in Bun.build / bun build kinda blocks progress atm

I got it working without using Bun.build. I adjusted the following parts of isFnUse, in case you encounter the same problem in the future with bun.
https://github.com/bogeychan/elysia-polyfills/blob/302cceaea8feb06aa701b166fb362678f828af3a/scripts/runtime.js#L38-L46
https://github.com/bogeychan/elysia-polyfills/blob/302cceaea8feb06aa701b166fb362678f828af3a/scripts/runtime.js#L51-L57
I'll look into CommonJS support tomorrow

CommonJS support should be added without build-step in<EMAIL_ADDRESS>and<EMAIL_ADDRESS>yarn create elysia my-elysia-app --template node

If you want to support ESM hybrid with CJS in Elysia you can follow this blog post. I implemented the same approach.
Furthermore you have to use "moduleResolution": "nodenext", (i.e. specify all imports and exports with .js extension)


PaginationV2 arrow icon misalignment

Detailed description

The arrow icon after the page number in PaginationV2 doesn't align correctly. I believe this is a regression introduced recently. I didn't see it in the previous versions. See here:
http://react.carbondesignsystem.com/?selectedKind=Pagination&selectedStory=v2&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Fstories%2Fstories-panel

Is this a feature request (new component, new icon), a bug, or a general issue?
This is a bug

Is this issue related to a specific component?
Yes, PaginationV2 in carbon-components-react

What did you expect to happen? What happened instead? What would you like to see changed?
I expected the icons align to the vertical center of the component.

What browser are you working in?
Firefox, Chrome and Safari. The problem happens on all of them and doesn't seem to be related to a specific version of the browsers.

What version of the Carbon Design System are you using?
carbon-components-react:  6.114.0

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
I am working on an IBM product that has a quarterly release cycle, and we're moving to React with extensive use of carbon components.

Steps to reproduce the issue
The problem can be reproduced in the carbon-components online storybook:
http://react.carbondesignsystem.com/?selectedKind=Pagination&selectedStory=v2&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Fstories%2Fstories-panel
Additional information
See the screenshot above in the description section

I'm particularly interested in this fix as it's blocking me updating to the latest version of v6. I had a brief look into this and have a feeling the regression was introduced in #2093 as it's the only major styling update I can see since this component worked.

Looking at your codepen I'm not seeing this misalignment. Maybe this was fixed @tozhangkai ?

Hi, I believe this issue refers to v6 and as such the link in the issue is not accurate. You can clearly see the arrow issue at: http://v6-react.carbondesignsystem.com/?selectedKind=Pagination&selectedStory=v2&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Fstories%2Fstories-panel
I am eagerly awaiting a fix for this issue also. Had a brief look into the cause but didn't really get anywhere. Anything I can do to help please let me know.

@asmith-IBM Yeah contributions will be great - The style is hosted in v9 branch of carbon-components repo.

@asmith-IBM thanks for pointing out this is for carbon react v6 (or carbon v9). The link I provided used to point to the v6 code and now it appears to have been moved to the latest code base. @asudoh is there an estimation on when it'll be fixed? It becomes a show stopper for our product as we have pagination in many of the pages, and the problem is pretty obvious. The new v7 (or carbon v10) doesn't have the problem, but it's a totally new design and we can't afford to move to it recently. Thanks.

@tozhangkai This issue is not marked as high priority as application can do (small) style override to address this. As I noted earlier, contributions will be nice - Thanks!

@asudoh could you post the style override is to fix this? Thanks.

@wilhaddenIBM I don't have one I can rattle off quickly - You can use DOM inspector in Chrome DevTools to fiddle with the styles to see what change yields the style you desire. Once you figure it out, be sure to consider contributing back. Thanks!


Copy the whole git repo only if necessary

(creating as draft for now until I see that it doesn't break anything else)
Previously, the git repo was always copied during discover -h fmf, however
we only need the .git present only if some operations with git are
performed (e.g. checkout to a ref). Otherwise, the fmf root is
sufficient to enable tests to run. This preserves space/bandwith if
fmf root is different from git root.
Fixes: #1016

I'd prefer explicit flag / option. One might want to copy git even if they are not using ref/modified-....

Agreed. Having an explicit option to always sync the whole git could possibly be useful. By default I'd suggest to save space.

/packit test

Added one more missing option which requires git (fmf-id) + added the option to force the repo sync. Hopefully, tests should be green.

One hundred green tests! :champagne:


Show warning message in Sunstone when scheduled action fails

Description
Currently if some driver action fails a warning message is shown in Sunstone. The same behavior could apply to scheduled actions.
Use case
User can easily know if the action has failed.
Interface Changes
Sunstone.
Additional Context
The error when the action fails is stored under SCHEDULED_ACTION/MESSAGE.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

@tinova PRs to be approved:

Code
Docs


enforce recompute flag on fsdpa quantization

Currently fp8fsdpa quantization supported only when flash_attention_recompute is True

https://github.com/huggingface/optimum-habana/pull/972

upstream URL
https://github.com/huggingface/optimum-habana/pull/976


Add Option to Create Element w/Tags

One issue is when creating a tag, you need to specify the unit. Might try a "copy" element approach instead.


fix: delete stale config files

connected to: https://github.com/scalameta/metals/issues/6253

You can't really clean up the .bloop dir this way.
The plugin is run per project/subproject so if you are importing a Gradle build that has multiple projects (e.g. Foo and Bar) then bloopInstall will import Foo and then when it tries to import Bar it will now delete the .bloop/Foo.json file - hence the CI failures.
It might be better to do this in Metals as off the top of my head I suspect the best way is to alter the init-script.gradle script.
You could add something like
// I haven't tested this but...
tasks.register('bloopClean', Delete) {
    delete '.bloop'
}

and then change the bloopInstall exec to be something like...
./gradlew --init-script /tmp/metals5311744264606695985/init-script.gradle bloopClean bloopInstall
Another option would be to change Metals to always remove .bloop before importing regardless of whether the import is Gradle, SBT, Maven as I suspect this might apply to other build tool imports.
If you want this to be a Gradle only thing then I can look at this next week.

The plugin is run per project/subproject
Oh, I see. I'm closing this then.

Gradle, SBT, Maven as I suspect this might apply to other build tool imports
Don't know about Maven but SBT plugin deletes old config files.

It might be better to do this in Metals as off the top of my head I suspect the best way is to alter the init-script.gradle script.

Deleting the whole .bloop will delete some bloop caches, not sure if that's an issue (e.g. stale semanticdbs might still be useful), @tgodzik?

Fixing this in Metals: https://github.com/scalameta/metals/pull/6305.


build target wrong folder

PHP Version

Shopware Version

Actual behaviour
storefront is built into folder ResourcesResources
Expected behaviour
storefront is built into folder Resources
Steps to Reproduce?
Build a plugin with storefront-stuff.

Broken since v0.1.38


S3 bucket deletion using as_completed

Issue #927

@kapilt - There is one question for you in the diff (search for your name)


Update dependency org.apache.portals.pluto:pluto-taglib to v3

This PR contains the following updates:

Package
Update
Change

org.apache.portals.pluto:pluto-taglib
major
2.1.0-M3 -> 3.1.0

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 3.x releases. However, if you upgrade to 3.x manually then Renovate will then reenable updates for minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


#282 Restructure examples/ directory

Description
This PR restructures the examples directory to provide a more organized and user-friendly entry point for users seeking specific functionality.
Issue reference
Fixes #282
Review
Before you mark your PR as ready for review, please ensure that you've considered the following:

Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

[ ] New Feature: A non-breaking change that adds new functionality.
[ ] Optimization: A code change that improves performance.
[x] Examples: A change to existing or additional examples.
[ ] Bug Fix: A non-breaking change that addresses an issue.
[ ] Documentation: Updates to documentation or new documentation for new features.
[ ] Refactoring: Non-functional changes that improve the codebase.
[ ] Style: Non-functional changes related to code style (formatting, naming, etc).
[ ] Testing: Additional tests to improve coverage or confirm functionality.
[ ] Other: (Insert description of change)

Key checklist:

[ ] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All unit tests pass: $ nox -s tests
[ ] The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.
Further checks:

[ ] Code is well-commented, especially in complex or unclear areas.
[ ] Added tests that prove my fix is effective or that my feature works.
[ ] Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

I think this is ready for an initial review, I've covered most of the notebooks and scripts in #282-comment, example tests might be failing right now which i'll work on to fix.
However there's one notebook that's repeating in Getting Started/ & Design Optimisation/ i.e. spm_electrode_design

Tests are also passing now.
cc: @NicolaCourtier @BradyPlanden

Hi @arjxn-py, thanks for sharing your progress on this issue! A few comments:

please consider whether to put scripts and notebooks together in the new folder structure or keep separate (currently the new folders are all stored within examples/notebooks which will make the scripts difficult to find)
let's merge and rename LG_M50_ECM/data into just LGM50_data
the new plotting_a_dataset.ipynb is more like what I was imagining for importing_a_pybamm_model (importing, running and plotting the result of a PyBaMM model)
just "plotting a dataset" would be like the start of LGM_50_identification

Thanks again, please let me know if any questions and request a review when you are ready.

This branch has become outdated - issue #282 on the restructuring of the examples directory has been resolved by #559.
Please open a new issue if you would like to improve the examples!


Suggestion: Add Pictures to the Mod Pages and Git Page

I would really like to see some pictures as I would not like to make a whole server just to test it out.

Pretty sure you don't need one, just install it on your client and use it in singleplayer


[Feature/Improvement] Improve the submit button appearance.

Purpose: N/A
More details:
Update the appearance of the submit button so it looks less clunky. Keep it as a BottomSheet so that it hovers above the keyboard. Adding space or padding between the submit button and the keyboard may also improve the appearance.
Something like this:

Acceptance Criteria:

Submit button appearance improved, similar to the one shown in the screenshot.

I would like to contribute, please assign me this issue.

Hi @Krunal-375, I have assigned the issue to you. Thank you for supporting the project!

Closed in #130


Dockerfile for php laravel and .dockerignore file created.

Is there a way we can have it include hte laravel stuff using composer instead of committing it all to hte repo? (if not, that' sfine)


cc: Convert base file name to screaming snake case

This patch converts the base file name into screaming_snake_case instead
of upper for cc macro generation.
This is motivated by:
INFO: From Compiling external/com_github_openzipkin_zipkinapi/zipkin-jsonv2.pb.validate.cc:
In file included from bazel-out/k8-opt/bin/external/com_github_openzipkin_zipkinapi/zipkin-jsonv2.pb.validate.cc:5:
bazel-out/k8-opt/bin/external/com_github_openzipkin_zipkinapi/zipkin-jsonv2.pb.validate.h:37:31: warning: ISO C99 requires whitespace after the macro name [-Wc99-extensions]
                              ^
1 warning generated.

As reported in
https://github.com/envoyproxy/envoy/pull/6985#issuecomment-526658473.
Signed-off-by: Dhi Aurrahman<EMAIL_ADDRESS>

Thanks, this is definitely the right way forward. Looks like the pgv_python_proto_library rule declares output file names that don't match what is actually being produced. Let me know if you need help debugging.

Looks good, will merge once CI passes

Thank you, @akonradi!


Tell user to sign codef's name when signing for them. Close #165

Tell user to sign codef's name when signing for them. Close #165
Test on mobile, ideally a small one

[ ] Test 1 (on mobile):

[ ] 1 codef
[ ] User will sign for codef
[ ] User gets to signatures
[ ] When signing for codef, user sees correct instructions as laid out in #165

As per comments, MVP will be changing the text on the page that lets the user choose how their codefendant will sign. This PR and strategy will be closed for now.


Cannot save Workspace when using "Save Workspace As..." to save on top of currently opened .CODE-WORKSPACE files

Issue Type: Bug
Steps to reproduce:

Open VS Code.
Open new document.
Save file to any directory. This will be the current working directory.
File > Save Workspace As...
Save Workspace to the current working directory.
Close VS Code.
Open VS Code.
Open the .CODE-WORKSPACE file in the current working directory.
File > Save Workspace As...
Save the workspace on top of the opened .CODE-WORKSPACE file.
It will fail to save/overwrite .CODE-WORKSPACE.

Expected:
The currently opened .CODE-WORKSPACE should be overwritten by the VS Code, because it is the current .CODE-WORKSPACE being overwritten by the current Workspace. In other words, the behavior should act like "Save Workspace". (Yo dawg...)
Actual:
You cannot save to a currently opened .CODE-WORKSPACE, even if the Workspace currently opened is the .CODE-WORKSPACE.
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-1603 v3 @ 2.80GHz (4 x 2794)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_offsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.92GB (5.36GB free)

Process Argv

Screen Reader
no

VM
0%

@tommai78101 what is the usecase of saving the same workspace that is opened on the same file?

Huh.....
It is not mentioned that Workspaces can auto-save changes here:
https://code.visualstudio.com/docs/getstarted/settings

@bpasero
Huh.....
It is not mentioned that Workspaces can auto-save changes here:
https://code.visualstudio.com/docs/getstarted/settings

@tommai78101 yeah it is, closing then.

Wow, GH does have issues...

@tommai78101 but making changes to the workspace does not require you to save the workspace at all, these changes are automatically saved. There is never a need to save the workspace if it already exists on disk.


Question: BitBucket 2FA and App Password Experience

Atlassian announced that they will ending support for basic authentication via password for Bitbucket API and Git over HTTPS and I have tried to analyze what this might mean for our setup with abapGit and the company repos in Bitbucket.
My firts attempt was to activate to 2FA in Bitbucket and use the app passwords for login, similar to the token setup used with gitHub, but this does not seem to be working (I receive a 401).
Since I'm not an authentication wizard, I have no clue on how to best analyze this and find out how we can contonue to use abapGit with Bitbucket, so any help or pointers that any of you can provide would be appreciated.
Does anyone have any experience how to use abapGit with Bitbucket without using Basic Authentication?

https://bitbucket.org/blog/deprecating-atlassian-account-password-for-bitbucket-api-and-git-activity

can you git clone via command line and the approach mentioned in https://stackoverflow.com/questions/39886995/how-to-access-bitbucket-using-app-password ?

Wow. That was fast :-)
And very helpful, because the command line approach described in the stackoverflow article helped me to figure out that the issue was actually the user name.
The Atlassian documentation states to use "your normal Bitbucket username", but does not mention that if one previously logged in with the e-Mail address as the username, that isn't actually working.
It has to be the user name itself, not the e-mail address.
Thanks for the help. And if someone has the same problem and finds this issue:
Use the Username, not the e-Mail address and create an app password in Bitbucket.


if create more than one course

version: v4.8.0
here is the courese folder

there is no proloem on the courses home page

if you click any courses, you will find, the toc is wrong

i will close it,
menu:
example:
name: Overview
weight: 1
i use the same menu name, if i change the menu name, everything work fine


Adds openslide backend

This is adding the openslide backend for reading WSIs. It is using a modified version of the OpenSlideStore class from  manzt/napari-lazy-openslide/napari_lazy_openslide/store.py to do so.
The issue related to stergioc/sopa#3 has been solved. At the moment, the feature extraction excecution time is x3 faster with the openslide backend (related to stergioc/sopa#2).
I let you @quentinblampey do the final checks :)

Looks good to me @stergioc, merging!


Allows re-loading a workflow version with --force if it has new steps.

This PR makes it possible to add steps to the leaves of a workflow by re-loading it with the --force option.

Previously, any difference in steps between the old and new versions would result in an error.
This PR still prevents removing steps from the old version, or inserting steps before other steps, as that could break existing projects.
The logic for why this change is safe is as follows:

Since adding a new step doesn't change the created_depends_on or submission_depends_on properties of any other step, existing projects can't be prevented from proceeding.
Since new steps can't be inserted into the topology as antecedents of another step, existing projects can't be prevented from completing.
For existing projects, calling create_subsequent_tasks() after adding Steps to the workflow might result in new tasks being created, but they won't be created by default upon loading the new steps.

Coverage increased (+0.01%) to 93.759% when pulling 1378a97905648c0c12fca2c109a764dcc7716664 on feature-permissive-workflow-loading into 708e1c64b9d496b25751355c242c44388c597799 on master.


Don't hide breadcrumb root page for users with limited tree visibility

Fixes #11451
Remove the special case for when the first item in the breadcrumb is something other than the site root. This special-casing had two effects, neither of which was actually desirable:

It replaced the displayed page title with 'Root' (which is undesirable because the page in question is often one that the user can edit, and therefore they ought to be able to see what it is
It took precedence over the styling for the last item in the breadcrumb, which should be always visible rather than on-hover

Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?

Please describe additional details for testing this change.
To test on Bakerydemo: create a Breaditors group with: Access to Wagtail admin, Add and Edit permission over the Breads page, and no other permissions. Create a user account in the Breaditors group and log in as that user. Go to Pages -> Breads.
[^1]: Development Testing

Closing in favour of #11541


Authentication problem with certificate for one of ingresses

/kind bug
What happened:
I am migrating from kube-lego to cert-manager and I'm trying to set up certificates for existing ingresses. One - pointing to k8s dashboard - worked out of the box. Second - pointing to docker registry - blows up with this in logs:
I0503 11:35:33.789997       1 helpers.go:162] Found status change for Certificate "registry-tls" condition "Ready": "False" -> "False"; setting lastTransitionTime to 2018-05-03 11:35:33.789965679 +0000 UTC m=+5604.837250986
I0503 11:35:33.790050       1 sync.go:241] Error preparing issuer for certificate registry/registry-tls: acme: urn:ietf:params:acme:error:unauthorized: User account ID doesn't match account ID in authorization
E0503 11:35:33.800680       1 sync.go:168] [registry/registry-tls] Error getting certificate 'registry-tls': secret "registry-tls" not found
E0503 11:35:33.800719       1 controller.go:186] certificates controller: Re-queuing item "registry/registry-tls" due to error processing: acme: urn:ietf:params:acme:error:unauthorized: User account ID doesn't match account ID in authorization

What you expected to happen:
Certificate would change Ready status to true.
How to reproduce it (as minimally and precisely as possible):
My Ingress resource:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: registry
  namespace: registry
  annotations:
    kubernetes.io/tls-acme: "true"
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/proxy-body-size: 1024m
spec:
  tls:
  - hosts:
    - registry.example.com
    secretName: registry-tls
  rules:
  - host: registry.example.com
    http:
      paths:
      - path: /
        backend:
          serviceName: registry
          servicePort: http

Domain replaced with example.com obviously.
Anything else we need to know?:
I used this guide: https://cert-manager.readthedocs.io/en/latest/tutorials/acme/migrating-from-kube-lego.html
I don't use helm, so I used non-rbac static manifests.
Environment:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

This is a weird error 🤔 it looks like your ACME account isn't porting across properly.
Can you try deleting your ACME account private key (after first backing it up, just in case!) and seeing if the issue still occurs? It could be that something about your ACME account is messed up.

also running into this
/remove-lifecycle stale

Closing this as it's getting stale - if you're still running into issues, you can try the #cert-manager channel on slack.k8s.io, or open a new issue describing your problems 😄


Print spec of components that form a cycle

Talked offline and agreed to take a more elaborate approach, as this will print out all the nodes that depend on something that is part of the cycle.


Improve code examples readability in readme

I think this version of the readme would be more readable, fell free to disapprove however.
Nice job!

It's definitely more readable, thanks for the PR :)


Create binaries for use in CI?

The recently release of 1.1.1e broke Ruby's OpenSSL, due to the change in eof handling.
Might binaries of both the most recent release and master be saved as release assets so external repos could make use of them in CI?
In Ruby world, we've got assets where the current CI replaces the previous CI only if all testing passes, so the master release asset is always a passing build.
Actions could support Ubuntu, macOS, and both msvc & MSYS2/MinGW builds on Windows.
It would be more that a few lines of code, but it would certainly broaden the scope of applications testing against master.
Or, maybe just 'engage' the master releases when master hits an alpha or beta release...

Creating binaries is not something we've ever attempted before, and we've always been a "source only" distribution. I'm not really sure I understand why us creating binaries helps? Or how testing against master helps prevent issues in the stable 1.1.1 release?

It seems that you can just build the latest openssl in ruby's CI system


Fix tests for where registers are mapped to SRAM

currently there are 3 tests which do not work on the "feature/8-map-registers-to-sram" branch.
(this branch might soon after writing this be merged so make sure t take that into account)
these need to be changed in order to not reach memory locations outside of the size of the memory.
Some tests also attempt to use registers which are not labelled between 0-31 (since some currently attempt to access registers with higher indexes (i.e. R35) which do not exist and thus return an error).

Issue closed, since #31 is also closed


Reuse Application data fetching code between steps

Notes:

Each step now triggers requests to fetch any un-loaded data which is required for any step, not just the current step. This will prevent further loading states when a user reaches a later step.
Each piece (or set) of data has a hook which determines whether it is present in the redux store, and triggers a fetch if it is not. There is a single hook which combines all of these, which is used in each step.
The redux selectors have also been extracted to their own hooks for simplicity.

Nice work! This is pretty much what I had pictured for the application, but this covers everything. My only suggestion would be to move the hooks to the hooks folder we already have.

Thanks! I'll move applicationHooks to the hooks folder. And now that the Fit step is merged into dev, I'll refactor that step as well.


Keeping the screen on

Great app.
I think it just needs an option where we can force the screen to be on.
Thanks for sharing the code btw!

I used to have this feature but removed it because it seemed like a security concern. I will consider adding it again, thanks for the feedback.


Errors "template system-library-rancher-logging incompatible with rancher version or cluster's [local] kubernetes version" seen in rancher server

Rancher Server Setup

Rancher version: 2.6.3-rc1
Installation option (Docker install/Helm Chart): docker install

Information about the Cluster
Describe the bug
Errors "template system-library-rancher-logging incompatible with rancher version or cluster's [local] kubernetes version" seen in rancher server
To Reproduce
No cluster was deployed. And logging was not enabled. But found these errors in rancher logs
Result
Rancher server has logs
2021/11/19 23:26:14 [ERROR] error syncing 'local/p-9bjkx': handler system-image-upgrade-controller: upgrade cluster local system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [local] kubernetes version, requeuing
2021/11/19 23:26:21 [ERROR] error syncing 'local/p-m9vzl': handler system-image-upgrade-controller: upgrade cluster local system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [local] kubernetes version, requeuing

This looks to be related to the generated catalog image list.

The error messages as reported in the original issue description is not seen anymore.

Reopening this issue since this error is seen on a 2.5.11 to 2.6.3-rc4 rancher upgrade
2021/12/05 17:44:22 [ERROR] error syncing 'system-library': handler system-image-upgrade-catalog-controller: upgrade cluster c-78qvp system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-78qvp] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-srmq4 system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-srmq4] kubernetes version, requeuing
2021/12/05 17:45:23 [ERROR] error syncing 'c-srmq4/p-69t9k': handler system-image-upgrade-controller: upgrade cluster c-srmq4 system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-srmq4] kubernetes version, requeuing
2021/12/05 17:45:27 [ERROR] error syncing 'c-78qvp/p-5lb89': handler system-image-upgrade-controller: upgrade cluster c-78qvp system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-78qvp] kubernetes version, requeuing
2021/12/05 17:46:12 [INFO] checking cluster [c-78qvp] upstream state for changes
2021/12/05 17:46:12 [INFO] updating cluster [c-78qvp], upstream change detected
2021/12/05 17:46:12 [INFO] cluster [c-78qvp] matches upstream, skipping spec sync
2021/12/05 17:46:22 [ERROR] error syncing 'system-library': handler system-image-upgrade-catalog-controller: upgrade cluster c-78qvp system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-78qvp] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-srmq4 system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-srmq4] kubernetes version, requeuing
2021/12/05 17:47:23 [ERROR] error syncing 'c-srmq4/p-69t9k': handler system-image-upgrade-controller: upgrade cluster c-srmq4 system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-srmq4] kubernetes version, requeuing
2021/12/05 17:47:27 [ERROR] error syncing 'c-78qvp/p-5lb89': handler system-image-upgrade-controller: upgrade cluster c-78qvp system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-78qvp] kubernetes version, requeuing
2021/12/05 17:48:22 [ERROR] error syncing 'system-library': handler system-image-upgrade-catalog-controller: upgrade cluster c-78qvp system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-78qvp] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-srmq4 system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-srmq4] kubernetes version, requeuing
2021/12/05 17:49:23 [ERROR] error syncing 'c-srmq4/p-69t9k': handler system-image-upgrade-controller: upgrade cluster c-srmq4 system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-srmq4] kubernetes version, requeuing
2021/12/05 17:49:27 [ERROR] error syncing 'c-78qvp/p-5lb89': handler system-image-upgrade-controller: upgrade cluster c-78qvp system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-78qvp] kubernetes version, requeuing
2021/12/05 17:50:22 [ERROR] error syncing 'system-library': handler system-image-upgrade-catalog-controller: upgrade cluster c-78qvp system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-78qvp] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-srmq4 system service logging failed: template system-library-rancher-logging incompatible with rancher version or cluster's [c-srmq4] kubernetes version, requeuing

On a 2.5.11 to 2.6.3-rc4 upgrade on docker install, these are. not seen anymore.
But right after the upgrade the following error messages are seen, and they. are not available after sometime (mostly during the downstream cluster agent pgrades)
2021/12/07 23:24:33 [ERROR] error syncing 'system-library': handler system-image-upgrade-catalog-controller: upgrade cluster c-s2ggs system service logging failed: cluster c-s2ggs not ready, handler system-image-upgrade-catalog-controller: upgrade cluster c-xdn8p system service logging failed: cluster c-xdn8p not ready, handler system-image-upgrade-catalog-controller: upgrade cluster c-vsjbd system service logging failed: cluster c-vsjbd not ready, requeuing


Osm land fixes

Updates to the osm_land and natural_earth importer scripts to handle use cases as follows:

Case where osm_land and natural_earth databases are stored on different servers, with different sets of credentials.
Case where we do not have permissions to drop existing natural_earth database

@gsoyka this looks good, thanks for the PR. Can you please update the README under the Natural Earth and OSM Land sections with the new command flags?

@ARolek Good call, I've updated the readme with the various configuration scenarios

Nice! Thank you.


how to precess 3d data

thank you for yout amazing work！
I want to know whether the net can process 3d data

Thank you for your interests in our work. The current version of UTNet doesn't support the processing of 3D data. But the idea of UTNet can definitely be applied to 3D tasks. We are currently working on it. Hopefully, the 3D version of UTNet will be released in a few weeks.


Continuation tokens not supported in Node when using ORDER BY clause

2 notes.

The Node SDK doesn't seem to support continuation tokens if you use an ORDER BY clause. I tried a query with and without the ORDER BY clause, and in both cases hasMoreResults = true, but when ORDER BY is included then continuationToken = undefined.
This claims that continuation tokens are only supported in Node when you specify a partition key in the options object. This does not appear to be a restriction any longer. My queries have been getting continuation tokens even without specifying a partition key.

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

ID: 0313c2d6-c1fe-9340-f1c8-76d660c4b1fb
Version Independent ID: 5121eaa8-d954-2f18-3f22-bd5c1d74281b
Content: Pagination in Azure Cosmos DB
Content Source: articles/cosmos-db/sql/sql-query-pagination.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

Hi @icanfathom Thank you for reaching out. We will look into it and update you as appropriate.

#reassign:gahl-levy
@gahl-levy, can you assist with this question?

@icanfathom, thanks for this feedback.
I have two things:

This seems to be a bug in the Node SDK. You may need to file an issue in the Azure SDK for JS repo to get support with this.
I have an update for the docs that removes the mention of Node.js not supporting this. This issue should auto-close once that change is queued for publishing.

Thanks again!

Hello,
I can't see how node.js sdk support order by for continous token.
When I add order by to the query I get an undefined token.
Is there a solution ?
Thanks you

Bump, same problem here, running a cross partition query with ORDER BY, no continuation token returned


Using HyprPanel with hyprsplit does not work well

Describe the bug
I use https://github.com/shezdy/hyprsplit to have separate workspaces per monitor similarly to awesome.
Using waybar they have an implementation that shows things correctly on each bar but in hyprpanel this very clearly does not work.
Screenshots

You can use the Workspace Icon Mappings to solve that. Like this:
{"1":"1","2":"2","3":"3","4":"4","5":"5","6":"6","7":"7","8":"8","9":"9","10":"10","11":"1","12":"2","13":"3","14":"4","15":"5","16":"6","17":"7","18":"8","19":"9","20":"10"}

Slider Map Workspaces to Icons on
Monitor Specific on

Ignore Workspaces
-[1-9][0-9]
to get rid of the Scratchpad

More of a workaround than a fix but thanks I will give that a go!

I was able to fix it by updating  the source code.
You need to update the dispatcher use in src/components/Bar/modules/workspaces/helpers/index.ts:
In the function getWorkspaceRules, there is a call to the workspacerules dispatcher that returns (in my case) an object formatted like:
[{
  "workspaceString": "eDP-1"
},
{
  "workspaceString": "HDMI-1"
}]

The WorkspaceRule looks like this:
type WorkspaceRule {
  "workspaceString": string,
  "monitor": string
}

The function expects workspaceString to be an int but, as we saw, the output is the monitor name and not the monitor ID. Maybe hyprctl updates the dispatcher or hyprsplit modifies it.
Here is a patch to fix this:
AGS v2 (if you're on the latest version of HyprPanel, after this commit: 2ffd602910ef31c9c1a772848935955df568b10c on Dec 21 2024
diff --git a/src/components/bar/modules/workspaces/helpers/index.ts b/src/components/bar/modules/workspaces/helpers/index.ts
index 8403117..5616db7 100644
--- a/src/components/bar/modules/workspaces/helpers/index.ts
+++ b/src/components/bar/modules/workspaces/helpers/index.ts
@@ -1,7 +1,7 @@
 import { exec, Variable } from 'astal';
 import AstalHyprland from 'gi://AstalHyprland?version=0.1';
 import { hyprlandService } from 'src/lib/constants/services';
-import { MonitorMap, WorkspaceMap, WorkspaceRule } from 'src/lib/types/workspace';
+import { HyprctlWorkspace, MonitorMap, WorkspaceMap } from 'src/lib/types/workspace';
 import { range } from 'src/lib/utils';
 import options from 'src/options';

@@ -63,19 +63,15 @@ export const getWorkspacesForMonitor = (
  */
 export const getWorkspaceRules = (): WorkspaceMap => {
     try {
-        const rules = exec('hyprctl workspacerules -j');
+        const rules = exec('hyprctl workspaces -j');

         const workspaceRules: WorkspaceMap = {};

-        JSON.parse(rules).forEach((rule: WorkspaceRule) => {
-            const workspaceNum = parseInt(rule.workspaceString, 10);
-            if (isNaN(workspaceNum)) {
-                return;
-            }
+        JSON.parse(rules).forEach((rule: HyprctlWorkspace) => {
             if (Object.hasOwnProperty.call(workspaceRules, rule.monitor)) {
-                workspaceRules[rule.monitor].push(workspaceNum);
+                workspaceRules[rule.monitor].push(rule.id);
             } else {
-                workspaceRules[rule.monitor] = [workspaceNum];
+                workspaceRules[rule.monitor] = [rule.id];
             }
         });

diff --git a/src/lib/types/workspace.d.ts b/src/lib/types/workspace.d.ts
index 5066332..885c09c 100644
--- a/src/lib/types/workspace.d.ts
+++ b/src/lib/types/workspace.d.ts
@@ -1,3 +1,14 @@
+export type HyprctlWorkspace = {
+    id: number,
+    name: string,
+    monitor: string,
+    monitorID: number,
+    windows: number,
+    hasFullscreen: boolean,
+    lastwindows: string,
+    lastwindowtitle: string
+};
+
 export type WorkspaceRule = {
     workspaceString: string;
     monitor: string;

If you're still on previous version, you should pull the last version.
If you don't want to, the two files modified are the same, the helpers.ts is just located elsewhere:

src/components/bar/modules/workspaces/helpers/index.ts -> modules/bar/workspaces/helpers.ts

Once you applied the patch, activate these options:

It should be working.
I hope it helps.

NOTE: I wanted to create a PR but, as I'm not a contributor, I don't think I can. Also I tested this only for my usecase and haven't test without Hyprsplit

Can confirm that the above works!
@edjubert Thank you for the (actually quite nice) patch!

I tested this only for my usecase and haven't test without Hyprsplit

I have also tested it without, all good there too :) The only difference is that the workspaces widget will only display the workspaces that are in that monitor, which I personally believe that is nicer

I wanted to create a PR but, as I'm not a contributor, I don't think I can.

You will need to fork the repository, push your changes there and then create a pull request.
See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork

I'll make a PR linking this thread.
That said, I find the label/description for the option not very clear:
Mask Workspace Numbers On Monitors with For monitor-specific numbering don't make any sense.
I think I'll change the label in the PR.
Thank you @davfsa


error: none is not a valid color string

anychart on over on series i get this error :"none is not a valid color string"

@ChagiLevi can you, please, provide a sample, code, and version you use?


[d3d9] Guild Wars 1 hangs

Guild Wars 1 at a specific scene hangs and have to kill the game. It is 100% reproducible.
Disabling dxvk and using wined3d works fine.
Possible point of interest the validation errors in the log below. Thank you.
Software information
Guild Wars 1
System information

GPU: AMD RX 480
Driver: Mesa git
Wine version: wine-staging-6.0_rc4
DXVK version: Latest from master

Apitrace file(s)
https://drive.google.com/file/d/1XRuh6yCElI-VNbhQWCJ2dhd0sGRgqOwL/view?usp=sharing
Log files
guildwars.log

Can confirm this also happens with an RX 5500XT and Intel HD 5500 (i3 5005U cpu) with Mesa 20.3.2 and dxvk 1.7.3. An ideal spot to reproduce it is by trying to load the "Augury Rock" mission which hangs all the time. Works fine on Nvidia. Weirdly enough it doesn't affect the entire game.
I tried older Mesa builds and all 20.x.x have same issue. Works fine with 19.3.5 though.
@Joshua-Ashton or @doitsujin : This game is an MMO, if you need a test account to work on the issue I'd be happy to lend you one.

Can confirm this also happens with an RX 5500XT and Intel HD 5500 (i3 5005U cpu) with Mesa 20.3.2 and dxvk 1.7.3. An ideal spot to reproduce it is by trying to load the "Augury Rock" mission which hangs all the time. Works fine on Nvidia. Weirdly enough it doesn't affect the entire game.
I tried older Mesa builds and all 20.x.x have same issue. Works fine with 19.3.5 though.
@Joshua-Ashton or @doitsujin : This game is an MMO, if you need a test account to work on the issue I'd be happy to lend you one.

Can you please clarify what "hang" means in this case? GPU hang?

Can you please clarify what "hang" means in this case? GPU hang?

Graphics freeze, music keep playing, can return to desktop.

Graphics freeze, music keep playing, can return to desktop.

I've done a little more research into this. I initially thought Mesa 19.3.5 was the last known version to work with recent dxvk's, I was wrong. The game works fine with Mesa 20.1.xx and dxvk 1.7.3.
If you go as far back as DXVK 1.5.4 though, the game works fine again with newer Mesa versions, in my case I'm running 20.3.2.  Switching to 1.5.5 makes the game unstable again.
@doitsujin: I believe it's the game that hangs, process has to be killed manually. Rest of desktops keeps working fine otherwise.
DXVK 1.5.5: https://user-images.githubusercontent.com/13750621/103485596-be4e5e80-4df7-11eb-907f-513948893c09.mp4
DXVK 1.5.4: https://user-images.githubusercontent.com/13750621/103485617-f655a180-4df7-11eb-96f8-fa064c51f3b1.mp4

I've done a little more research into this. I initially thought Mesa 19.3.5 was the last known version to work with recent dxvk's, I was wrong. The game works fine with Mesa 20.1.xx and dxvk 1.7.3.
If you go as far back as DXVK 1.5.4 though, the game works fine again with newer Mesa versions, in my case I'm running 20.3.2.  Switching to 1.5.5 makes the game unstable again.
@doitsujin: I believe it's the game that hangs, process has to be killed manually. Rest of desktops keeps working fine otherwise.
DXVK 1.5.5: https://user-images.githubusercontent.com/13750621/103485596-be4e5e80-4df7-11eb-907f-513948893c09.mp4
DXVK 1.5.4: https://user-images.githubusercontent.com/13750621/103485617-f655a180-4df7-11eb-96f8-fa064c51f3b1.mp4

Can also confirm here (Ryzen 5 2400G, RX 570, AMDGPU + Mesa 20.3.4-2 on Arch Linux)...anything newer than v1.5.4 hangs the Game.
Besides the spots @jrugia named, it happens also after you created a fresh Factions or Nightfall Character and be thrown at their respective starting locations ("Monastery Overlook" and "Island of Shehkah").

Can also confirm here  AMD Ryzen 5 3400G, AMD fury   AMDGPU Mesa 20.3.4 on debian testing.
it is freezing's direly when I do rotate in the game or start move any where in the game

I found a solvitions to use DXVK 1.5.5 to 1.8.1  by disable state cache it does not frez any more
set env to DXVK_STATE_CACHE=0

Can you try the build here: https://github.com/doitsujin/dxvk/actions/runs/716857969 and tell me whether that fixes it?

@K0bin Just tried your build and...it works :) No Crash when i start moving around in our Guild Hall, no crash in Augury Rock like in @jrugia Videos and no crash with a fresh Factions or Nightfall Character.
Really Awesome...Thank you ^^

Great to hear.


Try VGG16 as base model

@yhenon I am trying to use VGG16 as the base model, since the training is too slow (10 days for 1000 epoch) using the current Resnet50. In the function nn_base(), I changed to a VGG16 model wrote in Keras. I did not change the other layers (rpn, classifier). However, when the training was start, the error came out like this:
Exception: Incompatible shapes: [1,16,22,36] vs. [1,4,5,36]
[[Node: sub_2 = Sub[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/gpu:0"](strided_slice_4, rpn_out_regress/BiasAdd)]]
[[Node: Mean_5/_157 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/cpu:0", send_device="/job:localhost/replica:0/task:0/gpu:0", send_device_incarnation=1, tensor_name="edge_1555_Mean_5", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"]]
Do you know where should I change if I would like to use the VGG model?
Thanks!

I would also like to know @yhenon

Hello @mattdingmeng , did you succeeded to implement the VGG16 ?
I quickly tried to reproduce what you say and I have the following error :

Traceback (most recent call last):
File "train_frcnn.py", line 114, in
rpn = nn.rpn(shared_layers, num_anchors)
File "\keras_frcnn\resnet.py", line 202, in rpn
x = Convolution2D(512, (3, 3), padding='same', activation='relu', kernel_ini
tializer='normal', name='rpn_conv1')(base_layers)
File "\site-packages\keras\engine\topology.py", line 541, in call
self.assert_input_compatibility(inputs)
File "\site-packages\keras\engine\topology.py", line 435, in assert_input_compatibility
if K.ndim(x) != spec.ndim:
File "\site-packages\keras\backend\tensorflow_backend.py", line 479, in ndim
dims = x.get_shape()._dims
AttributeError: 'Model' object has no attribute 'get_shape'

Do you have this kind of error with the new version of the script ?
Regards,

I'm working on this btw - not that much more complex to use vgg, although I dont know how the memory is affected.

Hello,
I am currently working on this issue. I made a first PR in order to all get the same code in #86 .
Please, update the code if you succeed to resolve the issue :)

@mattdingmeng  Hi~ Have you solved the problem ‘Exception: Incompatible shapes: [1,16,22,36] vs. [1,4,5,36]’ ?
I'm trying another base network and meet a similar mistake.
Could you please give a hint what caused your problem?
Thank you.

Not yet. I did not solved it.
On Wed, Aug 9, 2017 at 7:59 AM, USTClj<EMAIL_ADDRESS>wrote:

@mattdingmeng https://github.com/mattdingmeng Hi~ Have you solved the
problem ‘Exception: Incompatible shapes: [1,16,22,36] vs. [1,4,5,36]’ ?
I'm trying another base network and meet a similar mistake.
Could you please give a hint what caused your problem?
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yhenon/keras-frcnn/issues/56#issuecomment-321247774,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY5U5XT11OgUQR3_9dMmYNpsvqHFB5Rjks5sWa0zgaJpZM4N0tN1
.


Similar methods like Express res.write() res.end()

I am using new EventSource(url) in client side.
In express I use something like this to send events -
app.get('/', (req, res) => {
  res.write('one')
  res.write('two')
  res.write('three')
  res.end()
})

Is there any similar approach in elysia?

We will implement Server Sent Event after 0.7 is published #103


Add Main.hs to fix the build failure

My intent was just to fix the build failure because of the missing Main.hs.  It grabs the first command line argument (assuming that it's a filepath), formats it, and prints out the result to STDOUT. Eventually, we might want to add an argument parser or something similar. But I've tried not to change too much for my first PR.
I imagine that you might have already have a Main.hs on your machine, but just forgot to check it in ? In that case, we could totally ignore this one :-)

I imagine that you might have already have a Main.hs on your machine, but just forgot to check it in ? In that case, we could totally ignore this one :-)

Well, it's more that there is a wildly different set of code on my personal machine than there is here. This project is very much in flux. I'll add this in anyway.

Ah, got it. Sorry about this then. And thanks for merging it anyways!


Feature Request: In profile ability to edit / remove bonfire results

If there are multiple solutions posted to a bonfire I'd like the ability to remove older versions (though I'd also like to be able to keep older versions too). Perhaps the ability to edit the solution on my profile.

+1, I'd like to see this too.

+1

+1 That would be a great feature.

+1
I'd like to see this too.

@BerkeleyTrue can we close this issue or something like this will be implemented in future?

We will be implementing deleting solutions.

@BerkeleyTrue - Will this be tied to a particular release?

@SaintPeter Nope. Anyone who wants to take a crack at it?

Definitely something I'd enjoy looking into but I don't know when I'll have the time, so if anyone else has the time or interest before I do they should go for it :smile:

This would be great

@BerkeleyTrue Are will still planning to implement this as something a user can choose to do? I know for a time there was talk about deleting all but the most recent solution from an given camper.

It seems that Now I in Chrome I can save a new submission over the last one. But It doesn't seem to work in Firefox.

Closing this as we no longer save multiple versions of a solution, only the most recent one.


更新文档中的编译与部署章节

Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
增加使用supervisord遇到句柄数问题的解决方法
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Thanks for your contribution❤😀

title follows Commit Format Specification is better: https://doris.apache.org/zh-CN/community/how-to-contribute/commit-format-specification.html


shift not working properly with padding on right side

Hi. I'm using floating-dom on my REACT application. I'm using 4 middlewares, including shift one.
Here's a working sandbox: https://codesandbox.io/s/morning-dream-q0qbic?file=/src/App.tsx
STEP TO REPRODUCE

Click on the green <div>, the tooltip will open and looks good.
Click again, tooltip will close.
Resize the region were the example is shown, so that the shift kicks in.
Click again on the green <div>: notice how on the left side, shift has "padded" correctly, but NOT on the right side (look image).

Of course, the firsts two steps are just to see that Tooltip is working ok.
MANUAL "FIX"
To fix the issue, I just need to set right: 4px on the floating element. But, that should be done ONLY when the shift middleware fails.. So, I guess this could be included in floating-ui itself.
EDIT: I'm pretty sure that, having the very long text influence this behavior.

The issue is the size of the tooltip is not affected by shift. The simplest fix is to specify max-width:  calc(100vh - 8px) on the tooltip (8px is for each 4px padding side)
https://codesandbox.io/s/elated-dream-hpm7wf?file=/src/App.tsx

Your proposal fix the issue, that's great!
If I may, I suggest you to add a small paragraph in the documentation, and add this: I suppose that this "problem" could be faced by some more people.


Use Airplay 2 Emulation To Control Older Sonos Like Modern Airplay 2 Device

AirPlay 2 has been cracked.  Please see news here.
If possible, would you consider using AirPlay 2 emulation to treat older Sonos devices like modern AirPlay 2-capable Sonos speakers?  Thanks for your feedback!

Was just reading this https://9to5mac.com/2019/12/05/airplay-2-cracked/
Would be great if this plugin could utilise it

Short answer: No, it wouldn't.  Consequently, I won't be working on this.
Your best option to get AirPlay2 to your old zone players is to (get Santa to) buy (you) an IKEA SYMFONISK bookshelf zone player for EUR 100, and use homebride-zp to group your existing zone players with the SYMFONISK.
Long answer below.
Please see #92, #82, #33.  Airplay2 has nothing to do with HomeKit.  It's a separate feature of Apple's Home app, not even available to other HomeKit apps.
Please read the news you're referring to: they've created a proof-of-concept to emulate an Airplay 2 device, but are nowhere near providing a stable product.  Once there'll be a stable product, it will show up in the Home app because of the Airplay 2 protocol - no need for any homebridge plugin.
Technically, the only place to implement proper Airplay2 support for Sonos is on the zone player itself, i.e. in the zone player "firmware" (it's actually a full-blown Linux system).  Any external solution will not be able to provide a seamless multi-room experience.
The issue is that a zoneplayer wants to initiate a connection to a music source/stream whereas in Airplay2 the music source initiates a stream to a speaker.  So you need a gateway in between, that acts as an Airplay2 server to Airplay2 clients, and as a music source (server) to the zone player.  The abandoned AirSonos project did exactly that.  It would act as a radio station to the zone player and as a speaker to Airplay1 clients.  It would re-broadcast the stream from the Airplay client to the radio stream client on the Sonos zone player, introducing a new layer of buffering.  This additional buffering will break the multi-room synchronisation.  The same will happen if the Airplay2 server connects to the zone player over the line-in, unless the line-in is configured without compression (which will cause issues when you group the line-in zone with other zones).
I did manage to integrate AirSonos in homebridge-zp, see #21, but abandoned that, since it wasn't worth the trouble.  AirSonos doesn't work for MP3 streams with variable bitrate: the music is played at the right speed.  Also, even on my macMini server, the sound was low quality (imo, too low to enjoy my music).  I don't know the audio streaming protocols well enough to figure out what's going wrong, let alone how to fix that (assuming that would be possible in the first place).
The re-broadcasting of the music stream is resource intensive, too intensive to be handled in Javascript.  While AirSonos runs on NodeJS, it has dependencies on C-modules, that need to be compiled while installing AirSonos.  This will give a lot of overhead and issues, when trying to run homebridge-zp with integrated AirSonos on Docker or other non-mainstream platforms.
Concluding: a productised version of the proof-of-concept mentioned in the new won't be enough to Airplay2 to your Sonos zone players (unless you connect them through the line-in).  You'll need something like AirSonos, which will break the multi-room synchronisation.  I'm not even sure that "something like AirSonos" will provide acceptable music quality.  Yet integrating that in homebridge-zp will cause many new support issues.  It's simply not worth my trouble.


Updating raw_post_data to body

Amazon FPS doesn't work because of
https://code.djangoproject.com/ticket/17323
Can we replace request.raw_post_data to request.body? Not sure how to best handle reverse compatibility.

Does replacing the raw_post_data with body fix the issue?

Closing this for now and continuing discussion in #119


Why not px_flutter instead of mercado_pago_mobile_checkout?

I think it's the perfect name :P

Honestly, I think that 'px_flutter' is shorter but more difficult to discover if you do not know that the native ones are called px-something.
Also maybe in the future, MercadoPago may want to use that name to release their own version and I do not want to argue with them about a name :).
I will add this to the FAQ thanks for the question!


Support for ACR/Container Registries as a Repository

Summary of the new feature / enhancement
As a user I want to be able to utilize ACR as a private repository for my packages with PSResourceGet/PowerShellGet.
Proposed technical implementation details (optional)
No response

Doc updates should be made for this as well


Crealla-Prolog crashes

Error msg:
Run logtalk_tester -p trealla-prolog -f xunit -c xml || EXIT=$?
Error! Unsupported backend Prolog compiler: trealla-prolog

This script automates running unit tests found in the current directory and
recursively in its sub-directories by scanning by default for "tester.lgt"
and "tester.logtalk" source files. In case of failed unit tests or test set
errors, this script returns a non-zero exit code. When a "tester.sh" file
exists in the tests directory, the file is sourced before running the tests.
The "tester.sh" file is sourced with all the parameters passed to the script.
The timeout option requires availability of the GNU coreutils timeout command.

from here,
and
TypeError: Cannot write private member to an object whose class did not declare it
    at O (/usr/local/lib/node_modules/xunit-viewer/node_modules/yargs/build/index.cjs:1:3360)
    at showHelp (/usr/local/lib/node_modules/xunit-viewer/node_modules/yargs/build/index.cjs:1:40491)
    at module.exports (/usr/local/lib/node_modules/xunit-viewer/xunit-viewer.js:19:5)
    at Object.<anonymous> (/usr/local/lib/node_modules/xunit-viewer/bin/xunit-viewer:6:1)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47
Error: Process completed with exit code 1.

from here.

Error! Unsupported backend Prolog compiler: trealla-prolog

Either logtalk_tester -h or man logtalk_tester will tell you the valid Prolog identifiers to use.


Error connecting: Error while fetching server API version: module 'six' has no attribute 'ensure_text'

Issue Type

Bug report

Molecule and Ansible details
Ansible: 2.8.0
Molecule: 3.4.0
Scenario
$ virtualenv venv
$ source venv/bin/activate
$ pip3 install molecule[docker]
$ molecule init role -d docker foobar
$ cd foobar
$ molecule create

Desired Behavior
Create Docker container for Molecule.
Actual Behaviour
$ molecule create
INFO     default scenario test matrix: dependency, create, prepare
INFO     Performing prerun...
INFO     Guessed /home/kotovalexarian/repos/global/kotovalexarian/ansible-role-common as project root directory
WARNING  Computed fully qualified role name of foobar does not follow current galaxy requirements.
Please edit meta/main.yml and assure we can correctly determine full role name:

galaxy_info:
role_name: my_name  # if absent directory name hosting role is used instead
namespace: my_galaxy_namespace  # if absent, author is used instead

Namespace: https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespace-limitations
Role: https://galaxy.ansible.com/docs/contributing/creating_role.html#role-names

As an alternative, you can add 'role-name' to either skip_list or warn_list.

INFO     Using /home/kotovalexarian/.cache/ansible-lint/e4342b/roles/foobar symlink to current repository in order to enable Ansible to find the role using its expected full name.
INFO     Added ANSIBLE_ROLES_PATH=~/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/kotovalexarian/.cache/ansible-lint/e4342b/roles
INFO     Running default > dependency
WARNING  Skipping, missing the requirements file.
WARNING  Skipping, missing the requirements file.
INFO     Running default > create
INFO     Sanity checks: 'docker'

PLAY [Create] ********************************************************************************************************************************************************************************************************************************

TASK [Log into a Docker registry] ************************************************************************************************************************************************************************************************************
skipping: [localhost] => (item={'image': 'docker.io/pycontribs/centos:8', 'name': 'instance', 'pre_build_image': True})

TASK [Check presence of custom Dockerfiles] **************************************************************************************************************************************************************************************************
ok: [localhost] => (item={'image': 'docker.io/pycontribs/centos:8', 'name': 'instance', 'pre_build_image': True})

TASK [Create Dockerfiles from image names] ***************************************************************************************************************************************************************************************************
skipping: [localhost] => (item={'image': 'docker.io/pycontribs/centos:8', 'name': 'instance', 'pre_build_image': True})

TASK [Discover local Docker images] **********************************************************************************************************************************************************************************************************
failed: [localhost] (item={'changed': False, 'skipped': True, 'skip_reason': 'Conditional result was False', 'item': {'image': 'docker.io/pycontribs/centos:8', 'name': 'instance', 'pre_build_image': True}, 'ansible_loop_var': 'item', 'i': 0}) => {"ansible_loop_var": "item", "changed": false, "item": {"ansible_loop_var": "item", "changed": false, "i": 0, "item": {"image": "docker.io/pycontribs/centos:8", "name": "instance", "pre_build_image": true}, "skip_reason": "Conditional result was False", "skipped": true}, "msg": "Error connecting: Error while fetching server API version: module 'six' has no attribute 'ensure_text'"}

PLAY RECAP ***********************************************************************************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=1    skipped=2    rescued=0    ignored=0

CRITICAL Ansible return code was 2, command was: ansible-playbook --inventory /home/kotovalexarian/.cache/molecule/foobar/default/inventory --skip-tags molecule-notest,notest /home/kotovalexarian/repos/global/kotovalexarian/ansible-role-common/venv/lib/python3.8/site-packages/molecule_docker/playbooks/create.yml

Featured lines
TASK [Discover local Docker images] **********************************************************************************************************************************************************************************************************
failed: [localhost] (item={'changed': False, 'skipped': True, 'skip_reason': 'Conditional result was False', 'item': {'image': 'docker.io/pycontribs/centos:8', 'name': 'instance', 'pre_build_image': True}, 'ansible_loop_var': 'item', 'i': 0}) => {"ansible_loop_var": "item", "changed": false, "item": {"ansible_loop_var": "item", "changed": false, "i": 0, "item": {"image": "docker.io/pycontribs/centos:8", "name": "instance", "pre_build_image": true}, "skip_reason": "Conditional result was False", "skipped": true}, "msg": "Error connecting: Error while fetching server API version: module 'six' has no attribute 'ensure_text'"}

The error comes from one of the Docker modules and is not strictly related to Molecule. Since Ansible 2.8.0 is not supported anymore, please update your installation and try again. If the error persists even with a newer version of Ansible, feel free to reopen this bug.

@tadeboro Thanks. Probably we need to add a test for ansible version and fail fast, to avoid reports about unsupported config.

Ansible 2.8.0 is installed as a dependency of Molecule 3.4.0, so it must be supported. If it isn't, change the package dependency.

Ansible 2.8.0 is installed as a dependency of Molecule 3.4.0, so it must be supported. If it isn't, change the package dependency.

This is not true. Molecule does not have Ansible listed as a dependency because there are actually several Ansible PyPI packages that users can use to satisfy Ansible dependency. Packages that you can use are ansible, ansible-base, and ansible-core. If the Ansible package is installed, you either had to install it manually or some other package listed it as a dependency.
The error from your issue does not come from Molecule itself, it is caused by an outdated Ansible module that upstream does not support anymore. And there is very little Molecule can do here. We do make sure Molecule works with supported Ansible versions, but we cannot be responsible for users that use EOL dependencies.
For more information about supported Ansible versions, see https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#ansible-community-package-release-cycle and https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#ansible-community-package-release-cycle


java.lang.Double cannot be cast to abi48__0.com.facebook.react.bridge.ReadableMap

I am using react-native-multi-selectbox for the multiselect dropdown, when navigating to the multiselect dropdown page on my app, an error of java.lang.Double cannot be cast to abi48__0.com.facebook.react.bridge.ReadableMap appears when testing the app on Android. It works fine for iOS but this error appears for Android and causes the app to crash.

Hello @sauzy34
I'm getting the same Issue using this package react-native-multi-selectbox
I hope this message finds you well. I'm writing to report an encounter with an existing issue that I've come across while working on app on Android.
Same Here!
Issue Title
 java.lang.Double cannot be cast to abi48_0.com.facebook.react.bridge.ReadableMap
Issue Number: #102

Hello ! I have the same error, only when I try to open SelectBox on Android devices. In IOS Simulator everything works correctly. I hope someone can give us a solution, thank you!


Bug when running git log commands

After the logging in #136 it's a little clearer that there's an error with the code to gather the history  metadata from git. When running against some repositories, there are errors like this:
[ ERROR ] analysis error: Shell command failed:
command: "git log -n1 --format=format:"%H-%ct" 0.1.0"
path:    "/Users/dave/Development/SwiftPackageIndex/Checkouts/github.com-fabianfett-vapor-lambda-runtime"
message: "ShellOut encountered an error
Status code: 128
Message: "fatal: ambiguous argument '0.1.0': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'"
Output: """

Running git tag on that repository shows the error clearly:
v0.1.0
v0.2.0
v0.3.0

The v is being omitted from the tag, probably as it's being stripped as it's not technically a valid version. We'll need to keep the original tag name around as well as the parsed semantic version.
Running the exact same command with the correct tag name works well:
git log -n1 --format=format:"%H-%ct" v0.1.0

Outputs:
8ecc257775d0567cf404287d2c7a40cee7d033d4-1579047775

Oh, right! I'll have to think about to best fix this, that might be tricky.

I think the only way is to add another field in the database that stores the tag name as a string.
It’s not duplicate data. The version is derived from the tag name, but that can’t be reversed.

Just noticed while working on the fix that this is also an issue for our version links to .../releases/<tagName>, which are broken.


UX Improvement: Simplify Conversation Management

Description:
I would like to propose a change to the current user experience of the rust-chatgpt-cli to make conversation management more user-friendly. The current design requires users to provide a conversation index each time they want to continue an ongoing conversation, which can be cumbersome.
Proposed Changes:

chatgpt new will behave mostly the same, to create a new conversation instance and set it as the currently selected conversation:

chatgpt new "question to ask chatgpt"
cat file | chatgpt new

Add a chatgpt status command to show the currently selected conversation, the number of ongoing conversations, total tokens used this month, and accumulated cost for the month:

chatgpt status

When a user asks a question with chatgpt, assume they want to continue with the currently selected conversation by default. If there's no conversation selected, create a new one:

chatgpt "ask a question"

chatgpt list dose not change, lists all conversations, allowing users to select the desired conversation:

chatgpt list

Add a chatgpt del command to delete a specific conversation:

chatgpt del <conversation index>

I believe these changes will simplify conversation management and make the rust-chatgpt-cli more user-friendly. Please consider implementing these enhancements. Thank you!

This sounds like a great idea.
I would like to try it out and go through the chat process. Hopefully this issue solves the (or any) current issue, or a step forward to getting a better user experience with the CLI.

Adding some links - feel free to refer to it or not

https://www.thefountaininstitute.com/blog/chat-gpt-ux-design
https://github.com/ehrenjn/cli-chat


Ensure we grab Amazon's mod24_ packages.

Grab Amazon's renamed packages when using 2.4 on amazon linux

We should try to abstract this at a higher level so we do not need to change every single recipe. Maybe we need to create a new attribute that we can conditionally set.

Maybe something like node['apache']['mod_prefix'] = 'mod24_'

I was thinking about that, but there's two things we need to track:

module prefix
whether or not to install the package -- as it seems it's not necessary except on Amazon?
the mod prefix would be rhel family only

I dunno, look at recipes/mod_perl.rb and I think you'll see that the prefix idea will be tricky

Okay, I just spent several hours making this work. Take a look at https://github.com/svanzoest-cookbooks/apache2/pull/341 where I've moved much of the module config into attributes, and given you a default recipe idea which will allow you to remove many of the mod_ recipes.
This is fairly major work, but it's both simple and powerful. There's some followup work to reduce many of the mod_ recipes into attributes, but I've done the brunt of the work for you.

Thanks for this! It is much appreciated.

I am going to close this in favor of #341


What's the reason to delete password and password_confirmation fields in update_with_password

I'm trying to build a little form to let users change their password. However, I found that password and password_confirmation keys get deleted if empty, which clearly breaks validation of presence. And update passes successfully without telling user anything.
https://github.com/plataformatec/devise/blob/master/lib/devise/models/database_authenticatable.rb#L74-L77
Any reason to keep this piece of code?

I think the comments there explain the reasons behind the code, in case you need different functionality I'd recommend building your own update method that takes the current password into account as well.
Thanks.


Dangling commits show 'undefined' branch

Dangling commits created like
git commit --allow-empty -m "this is force-pushed over"
git push
git reset --hard HEAD~1
git push -f

show a undefined branch on the UI:
https://try.gitea.io/silverwind/symlink-test/commit/18b49740a6d482078d0d7f8b8eaa2c9b28b32cd2

I think they should not show a branch indicator at all.

I think this has been resolved?

I think this has been resolved?

appears to be. Closing as fixed.

appears to be. Closing as fixed.


IWICBitmapSource.CopyPixels incorrectly generated?

Actual behavior
HRESULT Windows.Win32.Graphics.Imaging.IWICBitmapSource.CopyPixels(WICRect* prc, uint cbStride, uint cbBufferSize, byte[] pbBuffer).
I think the byte array is wrong here, because the user have no information about the size of the array before calling CopyPixels.
Also the extended versions for this call seems to be wrong.
Expected behavior
unsafe HRESULT Windows.Win32.Graphics.Imaging.IWICBitmapSource.CopyPixels(WICRect* prc, uint cbStride, uint cbBufferSize, byte* pbBuffer).
Repro steps

NativeMethods.txt content:

IWICBitmapSource

NativeMethods.json content (if present):

  "$schema": "https://aka.ms/CsWin32.schema.json",
  "emitSingleFile": true,
  "public": true,
  "comInterop": {
    "useIntPtrForComOutPointers": true,
    "preserveSigMethods": [
      "IWICBitmapSource",
    ]
  },
  "useSafeHandles": false

Any of your own code that should be shared?

Context

CsWin32 version: 0.2.219-beta
Win32Metadata version (if explicitly set by project):
Target Framework: [e.g. netstandard2.0]
LangVersion (if explicitly set by project): [e.g. 9]

I think the byte array is wrong here, because the user have no information about the size of the array before calling CopyPixels.
Also the extended versions for this call seems to be wrong.

Are you actually seeing a failure here, or is this just a speculative concern?
I see the generated method is:
void CopyPixels(winmdroot.Graphics.Imaging.WICRect* prc, uint cbStride, uint cbBufferSize, [Out] [MarshalAs(UnmanagedType.LPArray,SizeParamIndex = 2)] byte[] pbBuffer);

This looks correct to me, since the documentation for this method shows the user should allocate the array and then pass its length in as the 3rd parameter so the native side knows the length of the array. The native function can write to the array as documented, then you can read it afterward. So I don't see the problem.
That said, I am actually a bit surprised that the original method uses byte[] instead of byte* since we tend to emit the most performant methods and then add a friendly overload that would take the array or Span<byte> as a convenience.

It is just a speculative concern.
Now I noticed that I have to do some more calculation for the buffer size from user side before I can call CopyPixels. The documentation for this function didn't say how to get the cbStride or how to calculate cbBufferSize, so I am a little bit confused about using this function.

I've never used this function myself and generally this repo can't provide guidance for individual functions. General purpose win32 forums would be better for that. Although you can try using the Discussions tab to ask other community members about how to use CopyPixels if you want.
Can we close the issue for now since it sounds like there is no defect here?

I think you are right, that there is no defect here. But for a performance standpoint I think it will be better to have a byte* for the last parameter. If you want to create a System.Drawing.Bitmap from this function you can do this
uint stride, bufferSize;
IWICBitmap wicBitmap;
uint width, height;
//fill stride, bufferSize from some WIC functions I do not know yet, create the wicBitmap
wicBitmap.GetSize(out width, out height);
Bitmap alpha = new Bitmap((int)width, (int)height, PixelFormat.Format32bppArgb);
BitmapData alphaData = alpha.LockBits(new Rectangle(new Point(), alpha.Size), ImageLockMode.ReadWrite, alpha.PixelFormat);
wicBitmap.CopyPixels(null, stride, bufferSize, (byte*)alphaData.Scan0);
alpha.UnlockBits(alphaData);

If you only have the byte[], you have to do a Marshal.Copy to copy the byte[] to alphaData.Scan0. In this case you have two marshalling functions.

As a workaround for now, for performance intensive applications consider setting allowMarshaling: false in NativeMethods.json, which will get you the pointer-typed parameter you want.

So I did a little more research into this. I wanted to get back to a byte* parameter type with a Span<byte> friendly overload for cases like yours. But with #878 I learned that pointers on COM interfaces are generally not desirable because they block remoting interfaces, and CsWin32 cannot predict which interfaces may be used in a remoting setting.
So I think we'll have to keep the byte[] parameter type here. Of course the workaround I mentioned in my prior message about allowMarshaling: false can avoid that requirement if you're willing to give up interfaces completely.


Photolistview scrollscrubber

Add date based scroll scrubber on photos views.
I need to fix the scroll scrubber not displaying as expected until window is resized on some pages. I know, this is because I have a zero height and top, but I did'nt get yet how to fix this.

Looks very good! Thank you for this :)
I didn't find the root cause, but you could do the following as a workaround:
You could also add an optional prop "onHover" to ScrollScrubber, where you could pass a function which is called in handleMouseEnter. Then you could pass a new function, which is basically the same as the useEffect function, where you call setDataForScrollIndicator.
Looking forward to merging this :)

Seems good so far for being merged

Awesome work!


Update .env.sample

The .env.sample file is outdated.
We need to introduce the following changes:
(rename) ROCKET_LOG -> ROCKET_LOG_LEVEL
(remove)  ROCKET_DATABASES={service_cache={url="redis://<IP_ADDRESS>:6379"}}
(add) REDIS_URL = "redis://<IP_ADDRESS>:6379"
(add) FEATURE_FLAG_NESTED_DECODING = true

Env var declarations should not have spaces around the = ;)


Provider placement with 'essential complexity' in mind

so this is more of a question than an issue, at least at this point.
we use terraform to manage up to hundreds of account...
my AWS provider statement looks something like this...
provider "aws" {
  region     = "us-east-1"
  assume_role {
    role_arn = "arn:aws:iam::0123456789:role/ABCTerraform"
    session_name = "ABCTerraform"
  }
}

I'm running on an EC2 instance that has the ability to assume these roles in a number of sub-accounts.
I'm using terragrunt for the remote lock and state management.  Developer teams can read from the remote_state data source (bucket) and build on top of the base infra that I lay down.  vpc-id, internal-subnets, external-subnets, roles, policies, buckets, etc.
There's a set of modules like the docs describe which are in a separate infra-moudles repo.
Then there's another repo that has all of the account configuration terraform and I'm trying to widdle that down to the bare essentials, things that differentiate those accounts.
I'm using 'find_in_parent_folders' and 'path_relative_to_include' and love it.  makes life really simple.
I want to take it further and use what the documentation calls the notion of 'essential complexity' and have just a single file, terraform.tfvars in each account subdirectory in the repo.
here's the folder structure...
├── lab_accounts
│   ├── awslabs76
│   │   ├── setenv.sh
│   │   ├── terraform.tfvars -> ../../terraform.tfvars
│   │   └── us-east-1
│   │       └── vpc
│   │           └── terraform.tfvars
│   ├── awslabs77
│   │   ├── setenv.sh
│   │   ├── terraform.tfvars -> ../../terraform.tfvars
│   │   └── us-east-1
│   │       └── vpc
│   │           └── terraform.tfvars
├── README.md
└── terraform.tfvars

this is basically what the terraform.tfvars file looks like now...
terragrunt = {
  include {
    path = "${find_in_parent_folders()}"
  }
  terraform {
    source =<EMAIL_ADDRESS>  }
}

environment        = "np"
region             = "us-east-1"
cidr               = "<IP_ADDRESS>/23"
internal_subnets   = ["<IP_ADDRESS>/26" ,"<IP_ADDRESS>/26", "<IP_ADDRESS>/26"]
external_subnets   = ["<IP_ADDRESS>/26" ,"<IP_ADDRESS>/26", "<IP_ADDRESS>/26"]
availability_zones = ["us-east-1a", "us-east-1b", "us-east-1d"]

Here's my question, and I apologize if it should be apparent.  Where is the appropriate place to put the provider block/statement?  I've been banging my head and have moved it into the module (not ideal I believe) and can't seem to make it work in the terraform.tfvars file.  Clearly I'm overlooking something, probably simple so I apologize.
I've had a couple of moments of panic where I think I'm affecting an account when I've actually not assumed the role (it fails quietly) and instead have been affecting resources within the account i'm operating in.
Appreciate any feedback.

Here's my question, and I apologize if it should be apparent. Where is the appropriate place to put the provider block/statement? I've been banging my head and have moved it into the module (not ideal I believe) and can't seem to make it work in the terraform.tfvars file.

 The .tfvars files are solely for setting variables, not for defining resources, providers, or anything else.
That said, while Terraform has explicit support built-in for the assume_role configuration, Terragrunt does not. Terragrunt, as of now, only supports the standard auth options of all AWS SDK apps: AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY env vars, ~/.aws/credentials, the instance profile if you're on an EC2 instance, etc.

Oh, one other thing about providers: you can parameterize them with variables too.
provider "aws" {
  region = "${var.aws_region}"
  assume_role {
    role_arn = "${var.role_arn}"
    session_name = "${var.session_name}"
  }
}

That way, you can set aws_region, role_arn, and session_name to a different value in each .tfvars file.

I'm clear now and your feedback, and some sleep, helped a great deal.  Thank you.


Move models to external or infra layer.

Hello man, model is in domain layer, it can be moved to infra or externals layer.

Hi!
Why couldn't the model stay in the domain layer?

In the domain, it needs to have business logic in the case of entities, but the model does two things, it serves as business logic and it also has conversion methods.

How do you suggest?

I could create an entity Request and create a mapper or model in externals that extends from Request, but I don't know if this falls into DRY.

But Request aren't an entity. Because the business logic is Response. Request like is a DTO.

Okay, I hadn't seen it this way. Thanks for replying.


Nan aware dihedrals

Get ready to ruuumble

@richardjgowers I am disabling C++ level testing for IDX for now so we can go ahead with a release. I will make an issue to re-enable.


Replace cross apply with lateral join

To have the EF core follow the SQL standard more closely, replaced cross apply with lateral join. SqlServer overrides and uses cross apply.

This looks like a good change as CROSS APPLY is specific to t-SQL. Only concern here: can we use cross apply as an alias for lateral join? Are they exact aliases? The best docs I found said they are roughly equivalent.
/cc: @anpete

I think that lateral join is a superset of SqlServer's CROSS APPLY. It seems that at least the way CROSS APPLY is currently being used, it can be safely replaced with lateral join. If, in the future, lateral joins are generated by the core in contexts where CROSS APPLY does not work, a distinction will have to be made...

We discussed in triage and agreed that this would be a good change

:shipit:


Charts License

Hello-
We use the Charts plug-in in our application, is there a way that we can apply the license without having the vaadin.charts.developer.license file present in our home directory?  We would like to be able to pass this in as part of the build or have it specified in our build.gradle file.
Thanks in advance!

You can do that by adding the following to your build.gradle:
vaadinCompile {
    jvmArgs = ["-Dvaadin.charts.developer.license=${System.properties['vaadin.charts.developer.license']}"]
}

Just run  gradle -Dvaadin.charts.developer.license=<you license> ... and it will work. Of course you can also add it directly to the build.gradle as well instead of reading it from a system property, but that will expose the license to everyone using the repository which is not optimal.

Wonderful! Thanks much!


Refactor test report

Tests now upload trx files containing test results, a post build job then generates the test reports from the .trx files.

coverage: 99.242% (+0.06%) from 99.183%
when pulling 81cb9b0b898915753e04e2f3b7bb8330640083fd on users/alexpeck/rep2
into a056f06a3e555352f1e50c15043915f215a7524f on main.


update cloudevents dependency and clean up deps

Changes

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Describe any user facing changes here, or delete this block.

Examples of user facing changes:
- API changes
- Bug fixes
- Any changes in behavior

/ok-to-test

@sbwsg Fixed the failing unit tests.

@sbwsg Can this be merged?

Hi @tariq1890 - thanks for your patch.
The patch looks ok, would you mind adding a bit of context for this change to the PR description?

@afrittoli @vdemeester @sbwsg I have updated the description.

Thanks for the extra context :)
/lgtm

/approve

When can we expect the next release of pipeline?

We're working on the next release but have a couple of PRs outstanding before we're ready to cut it.  The plan right now is to have it released this week.  We'll see how that goes!


Curl CAPATH value

How do I override the CURLOPT_CAPATH, which appears to be hard coded to the host value.
In Changelog.md I see:
Added the ability to specify a `CURLOPT_CAPATH` value to be used when libcurl is used by ACL and
AuthDelegate.  See See Appendix C in the README for details.

However there is no reference to this in the README.
Thanks

Based on the source, it looks like you add something like this to AlexaClientSDKConfig.json.
"libcurlUtils" {
    "CURLOPT_CAPATH":"/path/for/custom/certs"
}

Hello INRIX-joel-winarske,
Yes, that is correct.  Thank you!
BTW, if you encounter issues setting up your custom path you can get curl diagnostic information by building with -DCMAKE_BUILD_TYPE=DEBUG -DACSDK_EMIT_SENSITIVE_LOGS=ON on the cmake command line.
Regards,
-SWH


["Problem"] seeing that the itn link is getting changed

the rmd says something like this: website but the rendered html is showing: https://hutchdatascience.org/Ethical_Data_Handling_for_Cancer_Research/www.itcrtraining.org
for this course: https://github.com/fhdsl/Ethical_Data_Handling_for_Cancer_Research
if you click on the link"website" here you will see how it does goes to this url: https://hutchdatascience.org/Ethical_Data_Handling_for_Cancer_Research/

looks like based on https://github.com/fhdsl/Ethical_Data_Handling_for_Cancer_Research/pull/86 that this fixes it... but we should add to our documentation that people need www in their websites to avoid this issue


misleading docs

Your README.md says that you can use the fields parameter to pass extra fields along with the file. After digging through the code, I found out that you are actually sending the config to $http, which uses the data parameter, not the fields one.

the fields are added to the data as the FromData type to be send as multipart/form-data request.


Add sd_lookup_type config option, to allow TCP or UDP

I'm using Consul's DNS for discovery SRV records. Yesterday while I was trying to figure out why my graphs had lots of gaps in them, I discovered that Consul only returns three records for a SRV request made over UDP, but will return all configured records for a request made over TCP. When I had more than three nodes registered for a service, the UDP query was getting a random three each time.
This change adds an optional sd_lookup_type to the job config, allowing you to specify "tcp" on a per-job basis (mainly because it was easier than figuring out how to pass a global config setting through).
Default is udp, which matches the existing default when we weren't providing a setting.
I'll probably just switch over to using something like consul-template to write a non-SD config for now, but this seemed like an easy and innocuous enough change that I thought I would propose it.

:+1: otherwise, thanks! Note that we'll probably change the configuration around SD soon when refactoring the SD layer to be more flexible/general-purpose.

(and also, that sounds like quite odd behavior from Consul?)

@juliusv I can see how it makes sense … I wonder why this doesn't affect us.

@matthiasr Why would it make sense to only return three records when you request all? We don't hit this problem because we're not serving DNS directly by Consul (I think that was way too slow, or maybe there were other problems as well, such as this one).

Thanks. Camel cased and added a config check.
Since UDP is fire-and-forget with no way to really make sure you're getting the whole response, I think the spec is just a lot more strict on the response size there.

Actually I think we should avoid adding yet another config flag and just adhere to the DNS protocol. Consul, as mentioned, has a hard limit of three results over UDP, for whatever reason. It does also set the Truncated flag though, so Prometheus should just do the right thing as DNS client and requery over TCP as specified in the RFC.
The problem with the UDP/TCP payload sizes is that a server needs to decide when to truncate a message and set the corresponding header flag. Consul takes a very conservative approach and truncates after 3 result records, glimpse uses similarly arbitrary 43. The best would be to come as close as possible to 4096 bytes. Anyway, adhering to the Truncated flag is the right thing to do here.

@grobie That's interesting. We had the problem of broken UDP->TCP fallback upon truncated UDP responses ~2 years ago with the DNS implementation in the Go standard library in Prometheus, which is why we switched to miekg/dns back then, which seemed to fix it. If indeed Consul is setting the Truncated flag (you're 100% sure about that?) and the automatic TCP fallback is no longer working, we should fix that indeed.

I checked the prometheus-consul DNS interaction, the problem here is more consul than prometheus. This is of course a bit unsurprisingly, as it works as expected for us at SoundCloud with our own DNS servers.
The consul authors prefer to not set the flag by default, but the RFC5966 says:

[...]  the normal behaviour of any DNS server needing to send a UDP response
that would exceed the 512-byte limit is for the server to truncate
the response so that it fits within that limit and then set the TC
flag in the response header.

Anyway, consul provides a configuration option to change the behavior as described in the RFC: https://www.consul.io/docs/agent/options.html#enable_truncate
IMHO it shouldn't be in the scope of prometheus to cater for consul's non-default behavior, but I might be wrong of course :)

That's cool with me. I admit to knowing none of this about UDP DNS. :smile:
In the meantime I've switched to just letting consul-template manage the config file, which gets the same result with less lookups:
https://github.com/scpr-cookbooks/scpr-prometheus/blob/c3c5986d576d5087082e69521c75cc0163659295/templates/default/prometheus.conf.tmplt.erb


10 cd 4 add icons and splash screen logo

Those images its just a placeholder images to fill the empty space, purely for layout purposes


Move the pc incrementation after the opcode is executed

Motivation
Make the Program Counter (PC) increment after the opcode is executed. This is done in order to follow the specification more closely. (Section 9.5, page 16 https://ethereum.github.io/yellowpaper/paper.pdf)
Description
Move the increment after opcode execution.
Closes https://github.com/lambdaclass/ethrex/issues/1371

Original PR here: https://github.com/lambdaclass/ethrex/pull/1405


Invalid link to Github Repository

Hey,
I was checking out all the examples when I came across Auth External API (JWT).
This example points to an non-existing Github repository: https://github.com/nuxt/nuxt.js/tree/dev/examples/auth-jwt
Please check the issue.
Thanks

I think your in the wrong place to post this issue: you should post it in the documentation repository
https://github.com/nuxt/nuxtjs.org

@jb-reynaud I believe missing example will be an issue for this repo?

@jb-reynaud is right. please, create issues in the right place, to help to resolve them sooner.
As for that example it is gone for some reason. The best I could find is this one:
https://github.com/nuxt/example-auth0
Probably link needs to be replaced with the one above. Anyone is aware where is the original example and why is it gone?