Enhancement request: Laravelish paginate

Hey, once again.
I would suggest to create adapter/transformer so we could pass some property and tell that this is definitely Laravel pagination, and it would parse laravel's paginate response.
Best wishes!

Thanks, I will work on it :+1:


v

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Submission validity

[X] This is not a personal support request, that should be posted on discussions community.
[X] I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.

Self troubleshooting

[X] I've read the documentation and made sure to follow it.
[X] I've read the troubleshooting first steps and frequent issues guides.

Version
1.7.2
Description
I get suddently the following message when trying to accesshttp://ccbe.link/admin while everything was working for months without any changes.
Warning: main(./includes/load-yourls.php) [function.main]: failed to open stream: No such file or directory in /home/filigran/ccbe.link/admin/index.php on line 3
Fatal error: main() [function.require]: Failed opening required './includes/load-yourls.php' (include_path='.:/usr/local/lib/php') in /home/filigran/ccbe.link/admin/index.php on line 3
Expectation
Normal dashboard
Reproduction steps
http://ccbe.link/admin
Context
No response

Duplicate of #3510


Kong1.4.1 Admin API /metrics 405 Not Allowed

Summary
I Updated Kong to 1.4.1 in my computer and tried to get metrics data from http://localhost:5001/metrics by GET method, but Kong return 405 Not Allowed. It works right in 1.4.0.
Steps To Reproduce

Update to Kong 1.4.1
Get Request to http://localhost:5001/metrics

Additional Details & Logs

Kong version 1.4.1

I've verified this problem with Kong's Docker image:
http :8001/metrics
HTTP/1.1 405 Not Allowed
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 32
Content-Type: application/json; charset=utf-8
Date: Wed, 04 Dec 2019 16:35:35 GMT
Server: kong/1.4.1
X-Kong-Admin-Latency: 1

{
    "message": "Method not allowed"
}

from v1.4.1, add new STATUS_LISTEN configuration, you need config STATUS_LISTEN(or KONG_STATUS_LISTEN on docker) to use /metrics.
see: https://docs.konghq.com/1.4.x/configuration/#status_listen

this broken change not described in CHANGELOG.md. Suggest to add description in CHANGELOG.md.

@JiyongShi The change was unintended (i.e. it is a bug). The linked PR has a fix for it.

@JiyongShi Curious to know what value did you set for the STATUS_LISTEN?


Plot corr function

Update Conduct and Contributing md files.
Add a plot_corr function with docstrings only.

Looks good to me


[🐞] singleJsxRoot eslint-rule: false positive for conditon ?  :  render body

Which component is affected?
Qwik Runtime
Describe the bug
export const K = component$((props: {x: boolean}) => {
  return props.x ?
123
 :
foo

})

will trigger the qwik/single-jsx-root warning
Reproduction
playground link
Steps to reproduce
No response
System Info
n/a

Additional Information
No response

Someone can correct me if I'm wrong, but I'm pretty sure what your writing is equivalent to...
export const K = component$((props: { x: boolean }) => {
  if (props.x) {
    return
123
;
  } else {
    return
foo
;
  }
});

which causes deoptimization in Qwik.
Try this instead
export const K = component$((props: { x: boolean }) => {
  return <>{props.x ?
123
 :
foo
}</>;
});

Does this mean that the documentation on this page is incorrect for having a conditional return?
https://qwik.builder.io/qwikcity/advanced/routing/#dynamic-404-page

Hi @samijaber , @tuurbo and @tjclifton 👋
Just saw this issue and wanted to let you know, that Manu removed the mentioned eslint rule and made the rendering of multiple root elements w/o performance drops possible. (PR: https://github.com/BuilderIO/qwik/pull/3034) 🎉
Hope it's okay for all, if i close this issue now since the rule is gone with the next release 👼


Blocks job or job definition creation when a parameter has no key and no value

Fixes #208. Validates new parameter when it is created. Fails validation when a parameter has no key and no value.
"A key and not a value" is valid because Jupyter sets the named parameter's value to the empty string; it should not cause execution to fail. "No key and a value" was, and remains, invalid (see 00:17 in the video below).
https://user-images.githubusercontent.com/93281816/198420287-bfea0462-9e76-4219-99aa-c0ef2f0d73f4.mov

Per @ellisonbg , rejects "key and no value" as invalid.
https://user-images.githubusercontent.com/93281816/198684546-4e4829da-0a03-41a2-9f0b-b5d0d8485f30.mov


make menu bar responsive on small screen sizes

Issue ticket number and link
Closes #30
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I have added tests

Closed for #363


2.x test cleanup

Removing EurekaClientTest (as the client now just delegates to the Handlers) and adding the interest tests to the InterestHandlerTest class

NetflixOSS » eureka » eureka-pull-requests #77 SUCCESS
This pull request looks good


Warning banner if 'Always On' is disabled

I'm not sure if it's possible, but can we have some kind of warning banner pop up if we see that the function isn't running in 'Always On' mode? It could explain that triggers may not fire if the site is stopped.
Somewhat related to #557.

Yes, @davidebbo and I were discussing this as well recently. I thought he mentioned that they were doing something similar for regular WebJobs UI.

Yes, I think @panchagnula is doing something along those lines for continuous WebJobs. Though we'll likely need a separate check from the Function Portal.

In WebJobs UI we turn ON Always ON if Continuous WebJobs is chosen in the UI drop down - based on the SKU type.

we need a fwlink with explanation why it's bad. @christopheranderson, @lindydonna can you provide the link?

@alrod Here you go: https://go.microsoft.com/fwlink/?linkid=830855


"File Not Found" Error when try to process dataset to train new voice

When I made a new voice dataset and copy-paste the path name to RVC v2 and hit "process," I always get this error message:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\Med/preprocess.log'
Putting no spaces in the voice dataset file name and experiment name did not fix this problem.
What do?

Give the path of the folder where the trainingdata (audio) exists.  preprocess.log is a file where the ouput (text/logs) of preprocess step will be saved. You could maybe create this file if not exists.

Add a similar issue but in my case it was actually because ffmpeg was not installed, the error was confusing
winget install ffmpeg
reload venv


yandex hybrid layer didn't work

Hello, When I chose hybrid layer in the example, map size got smaller and it didn't work properly.

I am unable to reproduce this issue with examples/yandex.html.
Please specify your browser version, and show your code (preferable using https://jsfiddle.net/ or similar sandbox)

Hello,
When I checked again the example, i didn't see the issue. Before I restart my computer, I had a lot of opened tab in chrome. Maybe the reason of issue is this. Currently everything works excellent . Thank you for your quick response.


NSTimer.new -> NSTimer.init

Non-scheduling initializers are currently defined as static methods because there was a bug in Foundation causing a crash.
I believe it was fixed, but I don't remember when exactly — it's possible it was only iOS 9/El Capitan, and it still won't work on iOS 8 etc.
If someone could verify this, we could add initializers that are appropriately marked as @available.
PR-s appreciated.

Hm, #22 made this hard :( I can't use initializer syntax if using CFRunLoopTimerCreateWithHandler. So either we'll have to wait for factory initializers (there is a Swift Evolution proposal out there), or… back to NSTimerActor? :(

Nope, still doesn't work. Not sure why — I'd swear I've seen this work... If someone wants to help, check out this branch: https://github.com/radex/SwiftyTimer/tree/init


Timestamp is not completely localizable

The timestamp below a message always displays username followed by time, see History.tsx. The string resource file only allows customization of the time portion, see Strings.tsx.
Expected: locale may specify time to precede username.

Should we include moment? Or are you aware of any better libraries for localization?

We should try out HTML Intl API.

Timestamp in v4 can now localizable.


Best way to log users activity

Witch the best way to log users activity?
I need log to database:

User logged in
User goes online
User goes offline
User make RPC call
User logged out

My decision:
1 and 5: in message broker AuthenticationHandler isValidUser()
2 and 3: in microservice(node client) with using Presence API
4: in every RPC procedure or in message broker PermissionHandler canPerformAction()
Is it right way?

Take a look at the monitoring plugin, by filtering the message types you can log any message
https://deepstream.io/tutorials/custom-plugins/monitoring/


Add config to override http subcription settings on a per cluster basis

Fixes #886

[x] Rebased/mergable
[x] Tests pass
[ ] CHANGELOG.md updated

/cc @joelegasse


Introduce "Extended" attributes

Extended properties allow for better names in different categories, while ensuring values are consistent.

[x] Update models
[x] Update serializers
[x] Remove data validation from cue and lean on our DB+test suite instead
[ ] Split base and extended properties in data files

Replaced by #139


Improve Git workflow

Git workflow needs improvement.
Builds fail when pushing to master because commits on the master branch trigger CI pushes to PyPi which fail because the setup.py version isn't bumped.

Repos default branch should be devel.
master is used for tagged commits only

Hey @nnarain!
You probably already evaluated this option, but just in case you haven't: Instead of having two branches, Travis can also push to PyPI only on tagged commits. You can achieve this by adding the following to your build stage in .travis-ci.yml:
  on:
    tags: true

Doing this you wouldn't need to add another branch.

I've been thinking about different git workflows and that option totally slipped my mind. I use in gameboycore.
Thanks!


[Feature Request] Color scheme support for barbar and galaxyline

Galaxyline: https://github.com/glepnir/galaxyline.nvim
Barbar: https://github.com/romgrk/barbar.nvim
Both are very popular plugins. Thank you for such an amazing color scheme

I'll take a look at this sometime during this week!

@luong-komorebi Thanks to @ful1e5 there is now barbar support. I can take a look at galaxyline when I have some time. You can also try setting color overrides until I get a chance to do it myself!

Thank you so much. Yes I did notice the commits and I think it s good to close this issue. Looking forward to see barbar and galaxyline being reference in the readme. Great work!


Consider switching from Enzyme to React-Testing-Library

See https://github.com/kentcdodds/react-testing-library for info

@fterdal and I are both big on blessing react-testing-library.
I do think this should not precede moving away from enzyme across all curriculum :(

Mayhaps a good first step would be creating a React checkpoint using it react-testing-library and seeing how it flies? I've got my eyes on refactoring the checkpoints anyway.


User is not created using LDAP and Automatic user creation when User naming attribute is set to UserPrincipalName (eMail-Address)

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
I have created an LDAP access server configuration with the option "Automatic user creation" and "UserPrincipalName" which is the eMail address of the user as the "User naming attribute. The user is not being created / importe in the local user database. If I use "SAMAccountName" in the "User naming attribute", the user is created as expected.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:

Go to 'System\Access\Servers'
Click on 'Plus symbol to add a new server'
Fill out 'type (LDAP), hostname, port value, transport, protocol (3), bind credentials, search scope, base DN, Authentication containers, Extended Query, User naming attribute (UserPrincipalName), Read properties (true), Synchronize gourps (true), Automatic user creation'
Login to the web GUI. User will be logged in but no user object is being imported in the user database.

Expected behavior
A user object should be created after the first login.
Describe alternatives you considered
Alternatively, the user object is being created, when the "User naming attribute" is SAMAccountname instead of UserPrincipalName .
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 23.10_2 (amd64, OpenSSL).

email addresses aren't supported as local usernames

is it a real local user or just a proxy object referring to ldap? We do not have real local user, all users are in active directory.
From: Ad Schellevis @.>
Sent: Thursday, 02. November 2023 18:33
To: opnsense/core @.>
Cc: haebi5 @.>; Author @.>
Subject: Re: [opnsense/core] User is not created using LDAP and Automatic user creation when User naming attribute is set to UserPrincipalName (eMail-Address) (Issue #6980)
email addresses aren't supported as local usernames
—
Reply to this email directly, view it on GitHub https://github.com/opnsense/core/issues/6980#issuecomment-1791224249 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZBFKDXNY44Z3A4B6D24A3YCPKLRAVCNFSM6AAAAAA63BLMAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGIZDIMRUHE .
You are receiving this because you authored the thread.Message ID: @.***>

email addresses aren't supported as local usernames

so, why did it fell off the fork? in pfsense it is working.

it didn't, we never supported email addresses for local usernames, nor does FreeBSD for that matter.

It is not a local user. It is an LDAP user from active directory. And the exact same config is working on pfsense
From: Ad Schellevis @.>
Sent: Sunday, 05. November 2023 14:58
To: opnsense/core @.>
Cc: haebi5 @.>; Author @.>
Subject: Re: [opnsense/core] User is not created using LDAP and Automatic user creation when User naming attribute is set to UserPrincipalName (eMail-Address) (Issue #6980)
it didn't, we never supported email addresses for local usernames, nor does FreeBSD for that matter.
—
Reply to this email directly, view it on GitHub https://github.com/opnsense/core/issues/6980#issuecomment-1793745542 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZBFKFTGWO3AIVRQZ5C6HDYC6LOFAVCNFSM6AAAAAA63BLMAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTG42DKNJUGI .
You are receiving this because you authored the thread.Message ID: @.***>

If in doubt just ask for a feature with the necessary technical background attached.

it didn't, we never supported email addresses for local usernames, nor does FreeBSD for that matter.

It's not a local user. The user is from the LDAP backend.

So, no updates on this?

User cannot login, when the user naming attribut in the access server is set to userprincipalname:


ParallelReportDownload example should catch exceptions on each API call

Describe the problem you are trying to solve
Running ParallelReportDownload, with an invalid customer ID, all async requests fail because of one invalid ID.
Describe the solution you would like
Only the invalid ID call should fail, not all requests.
Describe alternatives you've considered
Additional context
Inner Exception:
Google Ads API Inner Exception for 123321124: Status(StatusCode="InvalidArgument", Detail="Request contains an invalid argument.", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1603373622.780000000","description":"Error received from peer ipv4:<IP_ADDRESS>:443","file":"T:\src\github\grpc\workspace_csharp_ext_windows_x86\src\core\lib\surface\call.cc","file_line":1062,"grpc_message":"Request contains an invalid argument.","grpc_status":3}")

Fixed in 6.0.0


feat: Made several visual updates to the import github modal and populated the resource datatable

Description
Update the github import modal with the suggest visual enhancements
Populated resource manager datatable
Resolves #(issue)
https://github.com/DARPA-ASKEM/Terarium/issues/1164
https://github.com/DARPA-ASKEM/Terarium/issues/1168
which are related to https://github.com/DARPA-ASKEM/Terarium/issues/1144
Sorry merged main and get things back to create the video :P

Food for thoughts:
I am a bit skeptical about all the z-index changes, because the numbers are relative to the context where they are set and they are not compared against each other in a absolute sense.
It may be better if we have a layout schematic and we can use that as a reference rather than tweaking z-indices all over the place. @jamiewaese-uncharted

Food for thoughts:
I am a bit skeptical about all the z-index changes, because the numbers are relative to the context where they are set and they are not compared against each other in a absolute sense.
It may be better if we have a layout schematic and we can use that as a reference rather than tweaking z-indices all over the place. @jamiewaese-uncharted

absolutely.  I knew out of all changes there might a comment about this.  So, maybe I did it wrong, but it was the only way I was able to get the DropDown list to work within the modal.  I just scaled the indexes so the order should be in theory preserved, at least for the elements who's z-index was predefined.

updates.webm


links not working on getting started page

https://sbi-dev.github.io/sbi/tutorial/00_getting_started/
broken link: https://www.mackelab.org/sbi/tutorial/02_flexible_interface/
possible solution: links not updated to new website?

Good catch. I did try to update all links in the docs, so I am hopeful that this is an outlier.


为什么中文文档移除了脚手架

在中文模式下,官方文档并没有脚手架的连接,只能通过路由去找

Are you referring to the next/previous links, e.g.

If so, those were recently added in #1024 but ONLY to the English docs.  If you want to add them to the Chinese docs, you are welcome to open a PR.  In general, we maintain the English docs, and rely on the community to update the translated versions.


Support building docker images locally and without SBT

Fixes #744
Overhauls our docker release process to run releases of docker outside of SBT.  This was tested through the signing process deploying SNAPSHOT images to docker hub.
All images do a git clone to pull vinyldns, and perform the build of the container based on that git clone.

A new build directory contains the things to be built, for this PR only the docker images are here.  Anticipate possibly pulling in other artifacts in the future.
build/docker contains all of the docker setup
build/docker/test contains a func test docker image that can be used to test any VinylDNS API instance
build/docker/test-bind9 contains our bind9 setup
build/docker/api is a MySQL only API distribution
build/docker/portal is a MySQL only Portal distribution

In addition, a few files are added to make the build easier:

build/start.sh starts a given vinyldns version
build/stop.sh stops the current running vinyldns setup
build/release.sh this is the MAIN guy that performs the build.  Lots of arguments that are useful for testing.  Can provide a repository (for publishing to a docker register that is not docker hub), for building clean vs. assuming docker images.  Besides building everything, also runs func tests (smoke tests) against the docker image before completing.

Added a README.md for others to follow along with
To test..

Make sure you increase your docker machine settings to 4GB (the default of 2GB failed)
Go to the build directory
From there, run ./release.sh -c -t 111 to only build the docker images, this should build 0.9.4-b111
Start it up, run ./start.sh -v 0.9.4-b111
Login to the portal at http://localhost:9001
When finished, run ./stop.sh from the build directory
If you see an error code 137 error, you need to increase your memory

Going to dig a bit into this; ran into an issue building the portal due to tag issue. Possibly may need to specify a separate tag for portal:
ERROR: for portal  (<Service: portal>, "The command '/bin/sh -c apt-get update     && apt-get install -y     curl     gnupg     && curl -sL https://deb.nodesource.com/setup_6.x | bash -     && apt-get install -y nodejs     && npm install -g grunt-cli' returned a non-zero code: 100")
ERROR: Service 'portal' failed to build: The command '/bin/sh -c apt-get update     && apt-get install -y     curl     gnupg     && curl -sL https://deb.nodesource.com/setup_6.x | bash -     && apt-get install -y nodejs     && npm install -g grunt-cli' returned a non-zero code: 100
Error response from daemon: No such image: vinyldns/portal:0.9.4-b111


Batch query aggregated data in message

I am making a logging alerting system. I have logs in the influxdb database and I want to trigger alerts based on them. I have tried doing it with stream and it worked fine, but sending an alert for each log was too much for me.
Because of that I tried to make a batch alert every 10 minutes with a window of 10 minutes to check for all the logs in the database and alert on them. This is why I need all the "values" from the "series" field.
I am doing a batch query like so:
batch
    |query('''SELECT * FROM "foo"."bar".foobar''')
            .period(10m)
            .every(10m)
            .groupBy('spam')
   |alert()
           .crit(lambda: 2 > 1)
           .log('alerts.log')

And this is the (simplified) output when I log into a file.
{
   "id":"foobar",
   "message":"...",
   "details":"{....  {log:"message1", ...}},
   "time":"2016-10-25T08:20:13Z",
   "duration":0,
   "level":"CRITICAL",
   "data":{
      "series":[
         {
            "name":"docker",
            "columns":[
               "time",
               "log"
            ],
            "values":[
               [
                  "2016-10-25T08:20:13Z",
                  "message1",
               ],
               [
                  "2016-10-25T08:20:23Z",
                  "message2",
               ]
            ]
         }
      ]
   }
}

This is a fairly reduced example, but as you can see, only the first element of the "values" list is present in the "details" field.
Ideally I would like to get all these "values" and join them somehow into a single message. I want to be able to access them when I am constructing my message for example: {{ index .values }}
Thank you.

Same question. Anyone knows how to fix it without touch the source code?


Update tink to 1.9.0

Description
Updates tink dependency to 1.9.0 and update gradle build to use implementation instead of api to add tink to not leak tink dependency into other modules and only available to at runtime.

Consider splitting the version bump from gradle changes.


Form onSubmit always has undefined as argument

I'm not sure what I'm doing wrong, but I've got this:
      <Form
        style={styles.form}
        noValidate
        onSubmit={(adminOrg) => console.info(adminOrg)}
      >

And the console always dumps out undefined when I submit the form. How exactly does Form's onSubmit work? Where does it get its expected value from?

Ahh. There's a mistake in the documentation:
https://davidkpiano.gitbooks.io/react-redux-form/content/step_by_step.html
<Form> requires a model prop passed to it.

Thanks @ffxsam ! Fixed the documentation.


Add capability to specify portallocator port range

According to this: https://github.com/dotcloud/docker/blob/v0.9.0/networkdriver/portallocator/portallocator.go port range used to expose container ports to outside world is hardcoded. This doesn't seem to be good. It would be great to be able specify this port range as a configuration option in a file or as command argument.

we have https://github.com/docker/docker/pull/8412 does that solve the problem

@jfrazelle let's then close this issue.


Duplicate statement in FragmentSuperActivityToast.java

kilida,
Thanks for spotting this issue, I have fixed this in version 2.0.

John


meson: add patch to find boost via pkg-config

Fixes https://github.com/NixOS/nixpkgs/issues/86131
https://github.com/mesonbuild/meson/pull/13272
TODO remove all the meson(cmake uses the vars too) BOOST_{INCLUDE,LIBRARY}DIR
Tested with
diff --git a/pkgs/tools/package-management/lix/common.nix b/pkgs/tools/package-management/lix/common.nix
index fe77830d56f1..f25b16af3309 100644
--- a/pkgs/tools/package-management/lix/common.nix
+++ b/pkgs/tools/package-management/lix/common.nix
@@ -21,6 +21,7 @@ assert (hash == null) -> (src != null);
   bash,
   bison,
   boehmgc,
+  fetchpatch,
   boost,
   brotli,
   busybox-sandbox-shell,
@@ -110,7 +111,16 @@ let
         bison
         flex
         jq
-        meson
+        (meson.overrideAttrs (previousAttrs: {
+          patches = previousAttrs.patches ++ [
+            # upstream PR: https://github.com/mesonbuild/meson/pull/13272
+            (fetchpatch {
+              name = "find-boost-pkg-config.patch";
+              url = "https://github.com/mesonbuild/meson/commit/f0eda0346b2b936e4ef795f3a82733d6711b18fb.patch";
+              sha256 = "sha256-uSilNuSx9yd1cxs0XVLcLw4MOXEd2uIe2g+wk+SBqeU=";
+            })
+          ];
+        }))
         ninja
         cmake
         python3
@@ -201,13 +211,6 @@ let
         (lib.mesonOption "sandbox-shell" "${busybox-sandbox-shell}/bin/busybox")
       ];

-    # Needed for Meson to find Boost.
-    # https://github.com/NixOS/nixpkgs/issues/86131.
-    env = {
-      BOOST_INCLUDEDIR = "${lib.getDev boost}/include";
-      BOOST_LIBRARYDIR = "${lib.getLib boost}/lib";
-    };
-
     postInstall =
       ''
         mkdir -p $doc/nix-support

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

The upstream PR was merged.

Rebased

Thanks for getting this fixed upstream!


Increment version for storage releases

Increment package version after release of azure-storage-blob

@deyaaeldeen  Change log entries are sorted based on the version when it's auto updated and this is getting confused when preview version string is present. I will work with @chidozieononiwu to figure out a solution. This script is common across al language repo. Script was probably changed recently since this was working earlier for storage packages.

Closing this PR as we won't be taking version increment PRs on hot fix branches


ESOCKETTIMEDOUT or 502 bad gateway

[x] I have checked that the [SDK documentation][sdk-docs] doesn't solve my issue.
[x] I have checked that the [API documentation][api-docs] doesn't solve my issue.
[x] I have searched the [Box Developer Forums][dev-forums] and my issue isn't already reported (or if it has been reported, I have attached a link to it, for reference).
[x] I have searched [Issues in this repo][github-repo] and my issue isn't already reported.

Description of the Issue
I am trying to upload a files that contains 100 bytes but get either a
ESOCKETTIMEDOUT timeout error, or a 502 - Bad Gateway Error.
at first i was getting an ESOCKETTIMEDOUT error, and after looking though github issues #343
I tried following the timeout configuration setting instructions on https://github.com/box/boxcli/blob/main/docs/configuration.md#configure-how-client-retries-calls-and-handles-timeouts
and then I started to get 502 - Bad Gateway errors
the error docs for the box api say to use an
exponetail back off strategy, but the cli docs all ready claim to do that.
what should I Do next
Steps to Reproduce
run box files:upload -v --parent-id 0 ./project_id_list.txt
Expected Behavior
i expected to upload a file
Versions Used
@box/cli/3.4.0 linux-x64 node-v16.16.0
Error Message, Including Stack Trace
$ box files:upload -v --parent-id 0 ./project_id_list.txt                                                                                -- INSERT --
ESOCKETTIMEDOUT Error logs
  box:@box/cli:hooks:init done +0ms
  box init version<EMAIL_ADDRESS>argv: [ 'files:upload', '-v', '--parent-id', '0', './project_id_list.txt' ] +0ms
  box-cli:init Initializing Box CLI +0ms
  box-cli:init Loaded settings {
  box-cli:init   boxReportsFolderPath: '<path on my comupter>',
  box-cli:init   boxReportsFileFormat: 'txt',
  box-cli:init   boxDownloadsFolderPath: '<path on my computer>',
  box-cli:init   outputJson: false,
  box-cli:init   enableProxy: false,
  box-cli:init   proxy: { url: null, username: null, password: null },
  box-cli:init   enableAnalyticsClient: false,
  box-cli:init   analyticsClient: { name: null }
  box-cli:init } +1ms
  box-cli:init Using environment oauth {
  box-cli:init   clientId: '<my oauth id>',
  box-cli:init   clientSecret: '<my oauth secret>',
  box-cli:init   name: 'oauth',
  box-cli:init   cacheTokens: true,
  box-cli:init   authMethod: 'oauth20'
  box-cli:init } +0ms
  box-cli:init SDK client settings { iterators: true, analyticsClient: [Object], request: [Object] } +1ms
  box-cli:execute Starting execution command: files:upload argv: [ '-v', '--parent-id', '0', './project_id_list.txt' ] +0ms
  box-cli:execute Running framework error handler +1m
  box-cli:execute Handling re-thrown error in base command handler +6ms
Error: ESOCKETTIMEDOUT
    at ClientRequest.<anonymous> (/usr/lib/node_modules/@box/cli/node_modules/request/request.js:816:19)
    at Object.onceWrapper (node:events:641:28)
    at ClientRequest.emit (node:events:527:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:771:9)
    at Object.onceWrapper (node:events:641:28)
    at TLSSocket.emit (node:events:539:35)
    at TLSSocket.Socket._onTimeout (node:net:516:8)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)

502 error logs
box:@box/cli:hooks:init done +0ms
box init version<EMAIL_ADDRESS>argv: [ 'files:upload', '-v', '--parent-id', '177977690803', './project_id_list.txt' ] +0ms
box-cli:init Initializing Box CLI +0ms
box-cli:init Loaded settings {
box-cli:init   boxReportsFolderPath: '<path on my comupter>',
box-cli:init   boxReportsFileFormat: 'txt',
box-cli:init   boxDownloadsFolderPath: '<path on my computer>',
box-cli:init   outputJson: false,
box-cli:init   enableProxy: false,
box-cli:init   proxy: { url: null, username: null, password: null },
box-cli:init   enableAnalyticsClient: false,
box-cli:init   analyticsClient: { name: null },
box-cli:init   numMaxRetries: 3,
box-cli:init   retryIntervalMS: 3000,
box-cli:init   uploadRequestTimeoutMS: 3600000
box-cli:init } +1ms
box-cli:init Using environment oauth {
box-cli:init   clientId: '<my id here>',
box-cli:init   clientSecret: '<my secret here',
box-cli:init   name: 'oauth',
box-cli:init   cacheTokens: true,
box-cli:init   authMethod: 'oauth20'
box-cli:init } +0ms
box-cli:init SDK client settings {
iterators: true,
analyticsClient: [Object],
request: [Object],
numMaxRetries: 3,
retryIntervalMS: 3000,
uploadRequestTimeoutMS: 600000
} +1ms
box-cli:execute Starting execution command: files:upload argv: [ '-v', '--parent-id', '177977690803', './project_id_list.txt' ] +0ms
box-cli:execute Running framework error handler +1m
box-cli:execute Handling re-thrown error in base command handler +9ms
Error: 502 - Bad Gateway
  at createErrorForResponse (/usr/lib/node_modules/@box/cli/node_modules/box-node-sdk/lib/api-request.js:70:12)
  at APIRequest._handleResponse (/usr/lib/node_modules/@box/cli/node_modules/box-node-sdk/lib/api-request.js:180:19)
  at Request.self.callback (/usr/lib/node_modules/@box/cli/node_modules/request/request.js:185:22)
  at Request.emit (node:events:527:28)
  at Request.<anonymous> (/usr/lib/node_modules/@box/cli/node_modules/request/request.js:1154:10)
  at Request.emit (node:events:527:28)
  at IncomingMessage.<anonymous> (/usr/lib/node_modules/@box/cli/node_modules/request/request.js:1076:12)
  at Object.onceWrapper (node:events:641:28)
  at IncomingMessage.emit (node:events:539:35)
  at endReadableNT (node:internal/streams/readable:1345:12)
  at processTicksAndRejections (node:internal/process/task_queues:83:21)

also thought it might by good to share that I am able to successfully use the cli to run other commands like folders:get and folders:create

Hi @slugbyte
This is a known issue - https://github.com/box/boxcli/issues/298 The CLI officially supports node up to v14 - https://github.com/box/boxcli#version-schedule. Try downgrading your node version to v14 and see if that helps.

thanks for the quick reply!!!
downgrading to 14 worked perfectly :)


Unable to run after upgrading OS

I upgraded from Ubuntu 15.1 to <IP_ADDRESS>. Everything went smoothly during the upgrade, except now when I run  sudo bundle exec rake production:check --trace I get the following:
rake aborted!
LoadError: libmysqlclient.so.18: cannot open shared object file: No such file or directory - /home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/mysql2-0.3.20/lib/mysql2/mysql2.so
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `require'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `block in require'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:240:in `load_dependency'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `require'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/mysql2-0.3.20/lib/mysql2.rb:31:in `<top (required)>'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.11.2/lib/bundler/runtime.rb:77:in `require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.11.2/lib/bundler/runtime.rb:77:in `block (2 levels) in require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.11.2/lib/bundler/runtime.rb:72:in `each'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.11.2/lib/bundler/runtime.rb:72:in `block in require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.11.2/lib/bundler/runtime.rb:61:in `each'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.11.2/lib/bundler/runtime.rb:61:in `require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.11.2/lib/bundler.rb:99:in `require'
/home/huginn/huginn/config/application.rb:7:in `<top (required)>'
/home/huginn/huginn/Rakefile:5:in `require'
/home/huginn/huginn/Rakefile:5:in `<top (required)>'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/rake_module.rb:28:in `load'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/rake_module.rb:28:in `load_rakefile'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:686:in `raw_load_rakefile'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:96:in `block in load_rakefile'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:178:in `standard_exception_handling'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:95:in `load_rakefile'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:79:in `block in run'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:178:in `standard_exception_handling'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:77:in `run'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/exe/rake:27:in `<top (required)>'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/bin/rake:23:in `load'
/home/huginn/huginn/vendor/bundle/ruby/2.3.0/bin/rake:23:in `<main>'

Navigating to /home/huginn/huginn/vendor/bundle/ruby/2.3.0/gems/mysql2-0.3.20/lib/mysql2/ shows the file being there.
Any ideas on what could be wrong and how to fix it?

I suspect the mysql client libraries where updated and the gems c extension is still linked to the old version try forcing a reinstallation of the gems:
sudo -u huginn -H bundle install --force --deployment --without development test

That did the trick! Thanks Dominik!
Along the way, I had to update bundler
sudo gem install bundler
Install json 1.8.3 separately
sudo gem install json -v1.8.3
sudo bundle package
and then re-run the command


Fix timestamp

Signed-off-by: Aadhitya A<EMAIL_ADDRESS>Description
This PR fixes timestamp issue
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

meshery/meshery#4819

meshery/meshery#4820


Voctocore sometimes segfaults on startup

On some of my gentoo-machines voctocore crashes about 30% of the time.
Log from inside gdb:
Using host libthread_db library "/lib64/libthread_db.so.1".
2017-02-22 03:59:54     INFO root: Python Version: sys.version_info(major=3, minor=4, micro=5, releaselevel='final', serial=0)
2017-02-22 03:59:54     INFO root: GStreamer Version: (major=1, minor=10, micro=3, nano=0)
2017-02-22 03:59:54     INFO Clock: Using System-Clock for all Pipelines: <Gst.SystemClock object at 0x7ffff422b1f8 (GstSystemClock at 0x9c00e0)>
2017-02-22 03:59:54     INFO Clock: Starting NetTimeProvider on Port 9998
[New Thread 0x7ffff3b6c700 (LWP 18961)]
[New Thread 0x7ffff2ea0700 (LWP 18962)]
2017-02-22 03:59:54     INFO Pipeline: Video-Caps configured to: video/x-raw,format=I420,width=1280,height=720,framerate=50/1,pixel-aspect-ratio=1/1
2017-02-22 03:59:54     INFO Pipeline: Audio-Caps configured to: audio/x-raw,format=S16LE,channels=2,layout=interleaved,rate=48000
2017-02-22 03:59:54     INFO Pipeline: Creating 3 Creating AVSources: ['cam1', 'cam2', 'cam3']
2017-02-22 03:59:54     INFO Pipeline: Creating AVSource cam1 at tcp-port 10000
2017-02-22 03:59:54     INFO Pipeline: Creating Mirror-Output for AVSource cam1 at tcp-port 13000
[New Thread 0x7ffff0b06700 (LWP 18963)]
[New Thread 0x7fffe3fff700 (LWP 18964)]
[New Thread 0x7fffe37fe700 (LWP 18965)]
[New Thread 0x7fffe2ffd700 (LWP 18966)]
[New Thread 0x7fffe27fc700 (LWP 18967)]
2017-02-22 03:59:54     INFO Pipeline: Creating AVSource cam2 at tcp-port 10001
2017-02-22 03:59:54     INFO Pipeline: Creating Mirror-Output for AVSource cam2 at tcp-port 13001
[New Thread 0x7fffe1c76700 (LWP 18968)]
[New Thread 0x7fffe1475700 (LWP 18969)]
[New Thread 0x7fffe0c74700 (LWP 18970)]
[New Thread 0x7fffc3fff700 (LWP 18971)]
[New Thread 0x7fffc37fe700 (LWP 18972)]
2017-02-22 03:59:54     INFO Pipeline: Creating AVSource cam3 at tcp-port 10002
2017-02-22 03:59:54     INFO Pipeline: Creating Mirror-Output for AVSource cam3 at tcp-port 13002
[New Thread 0x7fffc2ffd700 (LWP 18973)]
[New Thread 0x7fffc27fc700 (LWP 18974)]
[New Thread 0x7fffc1ffb700 (LWP 18975)]
[New Thread 0x7fffc17fa700 (LWP 18976)]
[New Thread 0x7fffc0ff9700 (LWP 18977)]
[New Thread 0x7fffb3fff700 (LWP 18978)]
2017-02-22 03:59:54     INFO Pipeline: Creating Videmixer
2017-02-22 03:59:54     INFO VideoMix: Configuring Mixer for 3 Sources
2017-02-22 03:59:54     INFO VideoMix: Updating Mixer-State for Fullscreen-Composition
[New Thread 0x7fffb37fe700 (LWP 18979)]
[New Thread 0x7fffb2ffd700 (LWP 18980)]
[New Thread 0x7fffb27fc700 (LWP 18981)]
[New Thread 0x7fffb1ffb700 (LWP 18982)]
[New Thread 0x7fffb17fa700 (LWP 18983)]
[New Thread 0x7fffb0ff9700 (LWP 18984)]
[New Thread 0x7fff93fff700 (LWP 18985)]
2017-02-22 03:59:54     INFO Pipeline: Creating Audiomixer
2017-02-22 03:59:54     INFO AudioMix: Configuring Mixer for 3 Sources
2017-02-22 03:59:54     INFO AudioMix: Updating Mixer-State
[New Thread 0x7fff937fe700 (LWP 18986)]
[New Thread 0x7fff92ffd700 (LWP 18987)]
[New Thread 0x7fff927fc700 (LWP 18988)]
[New Thread 0x7fff91ffb700 (LWP 18989)]
[New Thread 0x7fff917fa700 (LWP 18990)]
[New Thread 0x7fff90ff9700 (LWP 18991)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffb27fc700 (LWP 18981)]
0x00007fffe1df4ce5 in ?? () from /usr/lib64/gstreamer-1.0/libgstcompositor.so

Config:
[mix]
videocaps=video/x-raw,format=I420,width=1280,height=720,framerate=50/1,pixel-aspect-ratio=1/1
audiocaps=audio/x-raw,format=S16LE,channels=2,layout=interleaved,rate=48000

; tcp-ports will be 10000,10001,10002
sources=cam1,cam2,cam3

; set the initial audio source
audiosource=cam1

[previews]
; disable if ui & server run on the same computer and can exchange uncompressed video frames
enabled=false
deinterlace=false

[stream-blanker]
enabled=false
sources=pause,nostream

I will try to build gstreamer with debugging symbols and get a more detailed stacktrace.

We've been seeing them on VOC-Systems, too, and I've also had reports from other Groups.
It might be related to https://bugzilla.gnome.org/show_bug.cgi?id=755782
I think I've once already digged after it and found it to be an open Issue originating from the order in which things are initialized in gstcompositor.
It would be good if you could try to reproduce it with an uninstalled git-master of gstreamer (see https://arunraghavan.net/2014/07/quick-start-guide-to-gst-uninstalled-1-x/)

It would be good if you could try to reproduce it with an uninstalled git-master of gstreamer (see https://arunraghavan.net/2014/07/quick-start-guide-to-gst-uninstalled-1-x/)

That fixed the problem for me
I am using Debian testing (stretch)

I'm closing this as an upstream issue that is already fixed. Please reopen if it is still reproducible with an gst-uninstalled head.


(348) show team lead

1. Show team lead on the project information tab
The user who creates the project is assigned as the team lead. We want to display this in the project information tab.
2. Update CHANGELOG

 Show team lead on the project information tab


🧑💻: Addition of All Contributors in Readme.md file

Title
Addition of All Contributors in Readme.md file
Enhancement Aim
The aim of this enhancement is to acknowledge the contributions of all individuals who have contributed to the project by adding a "Contributors" section in the README.md file. This will serve as a token of appreciation for their efforts.
Changes

Add a Contributors section to the README.md file.
Include contributor names, roles, and profile links using the All Contributors specification or manual listing.
Ensure the design and layout of the section are consistent with the current README.md style.

Like this..
Screenshots 📷

Guidelines

[X] I have read the guidelines
[X] I have the link to my latest merged PR

Full Name
Rahul-AkaVector
Participant Role
GSSOC, HACKTOBERFEST,

@Rahul-AkaVector this issue has already been taken care in one of the open assigned issues.


bug: Change the copy of the JetBrains Cody Pro user limit copy

Installation Information
NA
Goal
To prevent Cody Pro users from abusing Cody Pro by spamming a bunch of chat/command and autocomplete requests.
Describe the bug
Current copy:

Everything under the right hand column (aka Pro messages) in this comment: https://github.com/sourcegraph/jetbrains/pull/166#issuecomment-1843517258

Expected behavior
Requested copy:

Thank you for using Cody so heavily today!
To ensure that Cody can stay operational for all Cody users, please come back tomorrow for more chats, commands, and autocompletes. Learn more

Additional context (logs, images, etc)
No response

@iskyOS can you give a quick look at the proposed copy and LMK what you think?

Issue addressed. It is impossible to test it right now b/c of the issue with the agent (PLG Rate limiting error messages are currently broken).


SQLSTATE[42S02]: Base table or view not found

After initial installation:
modman clone https://github.com/madalinoprea/magneto-debug
and
n98-magerun.phar cache:flush
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento1.sheep_debug_request_info' doesn't exist, query was: DESCRIBE `sheep_debug_request_info`

#0  lib/Varien/Db/Statement/Pdo/Mysql.php(110): Zend_Db_Statement_Pdo->_execute(Array)
#1  app/code/core/Zend/Db/Statement.php(291): Varien_Db_Statement_Pdo_Mysql->_execute(Array)
#2  lib/Zend/Db/Adapter/Abstract.php(480): Zend_Db_Statement->execute(Array)
#3  lib/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract->query('DESCRIBE `sheep...', Array)
#4  lib/Varien/Db/Adapter/Pdo/Mysql.php(504): Zend_Db_Adapter_Pdo_Abstract->query('DESCRIBE `sheep...',
After module is installed and configuration cache is flushed, module's configuration is parsed and observers are registered (from your stacktrace this already happened) and then SQL setup scripts responsible to create database scripts are run (which seems was not happened in your case).

What version of Magento do you use?
What do you get if you execute these SQL queries?

select * from core_cache_option;
select * from core_resource where code = 'sheep_debug_setup';

My proposal is to retry installation and see if consistently you get into same state.

First you will have to clean up and force setup scripts to be re-executed:

-- Uninstall
DROP TABLE IF EXISTS sheep_debug_request_info;
DELETE FROM core_resource WHERE code = 'sheep_debug_setup';

Cache Flush
Load a page (to regenerate cache and run setup scripts)
Check if setup scripts run:

SELECT * FROM core_resource WHERE code = 'sheep_debug_setup';
DESCRIBE sheep_debug_request_info;

You should get something similar to:

Hi @coresh,
Do you still get this error?
Cheers,
Mario

Hi, Mario,
First of all: Thanks for your quick and complete reply.
Issue still not solved (output: the same)
Version: EE <IP_ADDRESS>

select * from core_resource where code = 'sheep_debug_setup';
`

code, version, data_version
sheep_debug_setup, 1.6.0, 1.6.0
`

select * from core_cache_option;

# code, value
block_html, 1
collections, 1
config, 1
config_api, 1
config_api2, 1
eav, 1
full_page, 1
layout, 1
translate, 1

i can't find CREATE table sheep_debug_request_info syntax:
$ grep -RHni sheep_debug_request_info /m/
/m/.modman/magneto-debug/code/Debug/Block/Abstract.php:89:            $this->requestInfo = Mage::registry('sheep_debug_request_info') ?: Mage::getSingleton('sheep_debug/observer')->getRequestInfo();
/m/.modman/magneto-debug/code/Debug/Block/View.php:22:            $this->requestInfo = Mage::registry('sheep_debug_request_info');
/m/.modman/magneto-debug/code/Debug/Test/Block/View.php:19:        $this->replaceRegistry('sheep_debug_request_info', 'registry data');
/m/.modman/magneto-debug/code/Debug/Test/Model/RequestInfo.php:42:        $this->assertEquals('sheep_debug_request_info', $resourceModel->getMainTable());
/m/.modman/magneto-debug/code/Debug/controllers/IndexController.php:84:        Mage::register('sheep_debug_request_info', $requestInfo);
/m/.modman/magneto-debug/code/Debug/etc/config.xml:20:
sheep_debug_request_info

/m/.modman/magneto-debug/docs/uninstall.md:13:DROP TABLE IF EXISTS `sheep_debug_request_info`;

In the same time magneto-debug version 1.5 worked like a charm

Regarding magneto-debug version 1.6
issue: solved after commenting line 163 of:
.modman/magneto-debug/code/Debug/Model/Observer.php

    /**
     * Saves request info model.
     *
     * @throws Exception
     */
    public function saveProfiling()
    {
        if (!$this->canCollect() || !Mage::helper('sheep_debug')->canPersist()) {
            return;
        }

        if (!$this->getRequestInfo()->getIsStarted()) {
            return;
        }

        // $this->getRequestInfo()->save();
    }

Did you try to run to remove core_resource entry and flush the cache and you had the same error?
Table is created by https://github.com/madalinoprea/magneto-debug/blob/master/code/Debug/sql/sheep_debug_setup/install-1.3.0.php#L11
I've reinstalled everything on Magento EE <IP_ADDRESS> and everything worked as expected:
# remove tables and resources
❯❯❯ n98-magerun db:console
mysql> drop table sheep_debug_request_info;
Query OK, 0 rows affected (0.01 sec)
mysql> DELETE FROM core_resource WHERE code = 'sheep_debug_setup';
Query OK, 1 row affected (0.01 sec)
# get update
❯❯❯ modman update magneto-debug

# manually trigger setup install
❯❯❯ n98-magerun  sys:setup:run
❯❯❯ n98-magerun db:console
mysql> describe sheep_debug_request_info;
+----------------+---------------+------+-----+---------+----------------+
| Field          | Type          | Null | Key | Default | Extra          |
+----------------+---------------+------+-----+---------+----------------+
| id             | int(11)       | NO   | PRI | NULL    | auto_increment |
| token          | varchar(255)  | NO   | MUL | NULL    |                |
| http_method    | varchar(32)   | NO   |     | NULL    |                |
| store_id       | smallint(6)   | NO   |     | NULL    |                |
| request_path   | varchar(255)  | NO   | MUL | NULL    |                |
| response_code  | smallint(6)   | NO   |     | NULL    |                |
| ip             | varchar(255)  | YES  |     | NULL    |                |
| session_id     | varchar(255)  | YES  | MUL | NULL    |                |
| date           | datetime      | NO   |     | NULL    |                |
| rendering_time | decimal(15,2) | YES  |     | NULL    |                |
| query_time     | decimal(15,2) | YES  |     | NULL    |                |
| query_count    | int(11)       | NO   |     | NULL    |                |
| time           | decimal(15,2) | YES  |     | NULL    |                |
| peak_memory    | int(11)       | NO   |     | NULL    |                |
| info           | mediumblob    | NO   |     | NULL    |                |
+----------------+---------------+------+-----+---------+----------------+
15 rows in set (0.00 sec)

@coresh, yes that line will try to persist some info to the missing table. I wouldn't remove that. It will make the module useless :D
I can provide you raw SQL to create table by hand, but I would like to understand what is happening and why setup script is not running on your installation.

MariaDB [m0ent11422]> drop table sheep_debug_request_info;
ERROR 1051 (42S02): Unknown table 'm0ent11422.sheep_debug_request_info'

In your case that's expected, you don't have that table.

Dear Mario,
According to the setup:
magneto-debug/code/Debug/sql/sheep_debug_setup/install-1.3.0.php

I can't find the syntax with: CREATE TABLE sheep_debug_request_info...

Table is added via Magento DDL object, see newTable call.
I notice that you use MariaDB. Maybe you use a different connection class that doesn't implement newTable?!
Query that used is to create the table is this:
CREATE TABLE `sheep_debug_request_info` (
  `id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'Id',
  `token` varchar(255) NOT NULL COMMENT 'Request Token',
  `http_method` varchar(32) NOT NULL COMMENT 'Http Method',
  `store_id` smallint(6) NOT NULL COMMENT 'Store Id',
  `request_path` varchar(255) NOT NULL COMMENT 'Request Path',
  `response_code` smallint(6) NOT NULL COMMENT 'Http Response Status Code',
  `ip` varchar(255) DEFAULT NULL COMMENT 'Customer IP',
  `session_id` varchar(255) DEFAULT NULL COMMENT 'Session Id',
  `date` datetime NOT NULL COMMENT 'Date',
  `rendering_time` decimal(15,2) DEFAULT NULL COMMENT 'Total Rendering Time',
  `query_time` decimal(15,2) DEFAULT NULL COMMENT 'Total Query Time',
  `query_count` int(11) NOT NULL COMMENT 'Total number of queries',
  `time` decimal(15,2) DEFAULT NULL COMMENT 'Total Time',
  `peak_memory` int(11) NOT NULL COMMENT 'Peak Memory used in bytes',
  `info` mediumblob NOT NULL COMMENT 'Serialized Info',
  PRIMARY KEY (`id`),
  KEY `IDX_SHEEP_DEBUG_REQUEST_INFO_TOKEN` (`token`),
  KEY `IDX_SHEEP_DEBUG_REQUEST_INFO_SESSION_ID` (`session_id`),
  KEY `IDX_SHEEP_DEBUG_REQUEST_INFO_REQUEST_PATH` (`request_path`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COMMENT='sheep_debug_request_info';

After creating the table
sheep_debug_request_info

magneto-debug v 1.6 worked like a charm
without commenting the 163 line: $this->getRequestInfo()->save();
Thanks for your perfect project and real-time support :+1:

No problem.  Still I think we didn't resolve the root cause but at least you can use it.
Cheers,
Mario

Magic instance:

modman remove magneto-debug
drop table sheep_debug_request_info;
modman clone https://github.com/madalinoprea/magneto-debug
redis-cli FLUSHALL (n98-magerun.phar cache:flush)
refreshing browser
So issue with:

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento1.sheep_debug_request_info' doesn't exist, query was: DESCRIBE `sheep_debug_request_info`

step:

DELETE FROM core_resource WHERE code = 'sheep_debug_setup';

refreshing browser
table 'sheep_debug_request_info': created

Result of the 8 step: NO issue
So: issue may be around initial setup install-1.3.0.php.
Quick analyze of:
magneto-debug/code/Debug/sql/sheep_debug_setup/install-1.3.0.php

No problem detected
Strange behave...

Is not me is you :)
I've also tried to replicate this issue using redis as cache backend, flushing cache using redis-cli and everything worked as expected at step 5.
Setup script is executed fist.

Profiling started

Profiling save (table should be there)

Any success?


SCSS imports from "node_modules/payload/dist" don't work for monorepos

Problem
In monorepos the path would probably be something like ../../node_modules/...
That's only a problem with npm monorepos (and possibly yarn?) but not pnpm (since it links all dependencies to the local node_modules)
(Possible) Solutions

? Some tricks in SASS to resolve to multiple paths (maybe they can handle monorepos somehow) - Never used SASS before
Add payload as a dependency (instead of peerDependency) & compile the SCSS at build time

Workarounds I found so far:

pnpm
yarn with no-hoist for payload
npm with install-strategy = shallow => Doesn't hoist anything
npm with install-strategy = linked => Experimental, like pnpm


[varLib] Encode postscriptname for fvar as single-byte encoding

For example, MacRoman.  Apparently OS X implementation requires that they be encoded using single-byte encoding (and be unique).

cc @rsheeter

We already write the fvar postscript font name as both single-byte MacRoman (1, 0, 0) and Windows Unicode (3, 1, 0x409) name records:
https://github.com/fonttools/fonttools/blob/master/Lib/fontTools/varLib/__init__.py#L77
We added a addName method to the name table to do just that:
https://github.com/fonttools/fonttools/blob/master/Lib/fontTools/ttLib/tables/_n_a_m_e.py#L148
When you say "unique", you mean OSX doesn't like that that we also write a windows-unicode one?

See related issue https://github.com/fonttools/fonttools/issues/683 (closed)

Right.  Ok.  Thanks.

Let's close then.

It is a problem though that subsetter by default removes the macroman names.

It is a problem though that subsetter by default removes the macroman names.

I guess we should open a separate issue for this.

It is a problem though that subsetter by default removes the macroman names.

I guess we should open a separate issue for this.

Seems related to https://github.com/fonttools/fonttools/issues/146 so I’ve added it there.


cognito trigger postConfirmation template causes Invalid lambda function output : Invalid JSON for async handler, works after removing the generated code in index.js

CLI version:
4.20.0
I use Amplify CLI to generate a postConfirmation cognito trigger,
exports.handler = async (event) => {
  try {
    // doing some async stuff
  } catch (e) {
    console.log('error', JSON.stringify(e))
    throw e
  }
  console.log('event2', JSON.stringify(event))

  return event
}

Every time I confirmSignUp, I received a 400 code on the clientside Invalid lambda function output: Invalid JSON
Spent a whole night, then this morning I decide to remove all the code in the index.js generated by amplify-cli:
exports.handler = (event, context, callback) => {
  const modules = process.env.MODULES.split(',');
  for (let i = 0; i < modules.length; i += 1) {
    const { handler } = require(`./${modules[i]}`);
    handler(event, context, callback);
  }
};

As the line here worries me: handler(event, context, callback), as you can see it doesn't have the await tag when calling lambda, and I don't know why we need this code in the 1st place, it might be better to explain the why part at the top rather than the logic, the logic is straightforward to understand.
I completely removed this part, and moved my handler here, everything works like a charm now.
As a rough guess, I think the current for loop doesn't compatible with async handler.
Maybe we should just remove it, and replace it with whatever blahblah.js which is the main js the user needs to edit.
So:

to prevent things like this to happen
remove logic that is not user's concern unless it solves some problems (but i definitely don't need this when using serverless framework)
the user does not need to figure out which .js file to edit.

Thanks :)

@Albert-Gao thanks for reporting we'll look into it.

The Amplify CLI generated Lambda function for auth triggers uses "Non-async" handler instead of the async handler, for details, see AWS Lambda doc.
It follow the module package folder structure

In which index.js is the entry point, and it has the exported handler

And custom.js file is the place your enter your code to handle the trigger, which will be invoked by the logic in the index.js
This is the template generated by the CLI
exports.handler = (event, context, callback) => {
  // insert code to be executed by your lambda trigger
  callback(null, event);
};

Since this is a Non-async handler, you shouldn't replace the whole file contents with an "Async" style handler, because the index.js file can not correctly invoke it. The error you see is Cognito complaining it did not receive the correct response, which should be sent by "callback(null, event)" in the Non-async handler.
When you moved the whole logic directly into the index.js and it worked because you change the entry point handler to Async handler.

But how amplify decide if I need an async Cognito trigger or not?
In my case, I certainly need to do some async stuff to get things done.
Were you saying I should strictly follow the generated code to avoid any async stuff in Amplify Cognito trigger? 😄
The problem here is that when the generated code can not determine the future, it’d better if we just remove it. Otherwise it is just a burden.
And no, to update the generated code to fit user land logic is still unacceptable.

Thanks for the feedbacks.
The Amplify CLI provides a mechanism for you to insert your own logic into the handler, and in this case, it uses the Non-Async style handler.
Both Async and Non-Async handler works, as you've found out, it just needs to be consistent.

The async handler pattern ended up being used in a template generated by Amplify CLI itself, so basically, if you deploy an Amplify backend with the "add user to groups" functionality configured, the PostConfirmation script will fail during user sign-up flow. Was quite the nightmare to work backwards from, seems to have been an active issue since 2019 or so.

Any fix with this?
I'm getting the same problem with the Email verification with redirection link feature.

@SalahAdDin:
I'm working on a fix in #7180. To get this working for now, you will need to manually overwrite the template Lambda generated by the Amplify CLI. Go to amplify/backend/function/CustomMessage/src/index.js, and make sure it returns the event variable:
// amplify/backend/function/CustomMessage/src/index.js
const moduleNames = process.env.MODULES.split(',');
const modules = moduleNames.map(name => require(`./${name}`));

exports.handler = (event, context, callback) => {
  for (let i = 0; i < modules.length; i += 1) {
    const { handler } = modules[i];
    handler(event, context, callback);
  }
};

Then push your changes with amplify push. Does that work around this issue for now?

@SalahAdDin:
I'm working on a fix in #7180. To get this working for now, you will need to manually overwrite the template Lambda generated by the Amplify CLI. Go to amplify/backend/function/CustomMessage/src/index.js, and make sure it returns the event variable:
// amplify/backend/function/CustomMessage/src/index.js
const moduleNames = process.env.MODULES.split(',');
const modules = moduleNames.map(name => require(`./${name}`));

exports.handler = (event, context, callback) => {
  for (let i = 0; i < modules.length; i += 1) {
    const { handler } = modules[i];
    handler(event, context, callback);
  }

  // ADD THIS LINE:
  return event;
};

Then push your changes with amplify push. Does that work around this issue for now?
cc @medelman17

My template code was different, but i added return event and it didn't work.

Can you post the code you modified so I can see where you're at?
Just know this is definitely a bug and not something you did.

The original:
exports.handler = (event, context, callback) => {
  // Define the URL that you want the user to be directed to after verification is complete
  if (event.triggerSource === 'CustomMessage_SignUp') {
    const { codeParameter } = event.request;
    const { region, userName } = event;
    const { clientId } = event.callerContext;
    const redirectUrl = `${process.env.REDIRECTURL}/?username=${userName}`;
    const resourcePrefix = process.env.RESOURCENAME.split('CustomMessage')[0];

    const hyphenRegions = [
      'us-east-1',
      'us-west-1',
      'us-west-2',
      'ap-southeast-1',
      'ap-southeast-2',
      'ap-northeast-1',
      'eu-west-1',
      'sa-east-1',
    ];

    const seperator = hyphenRegions.includes(region) ? '-' : '.';

    const payload = Buffer.from(
      JSON.stringify({
        userName,
        redirectUrl,
        region,
        clientId,
      })
    ).toString('base64');
    const bucketUrl = `http://${resourcePrefix}verificationbucket-${process.env.ENV}.s3-website${seperator}${region}.amazonaws.com`;
    const url = `${bucketUrl}/?data=${payload}&code=${codeParameter}`;
    const message = `${process.env.EMAILMESSAGE}. \n ${url}`;
    event.response.smsMessage = message;
    event.response.emailSubject = process.env.EMAILSUBJECT;
    event.response.emailMessage = message;
    console.log('event.response', event.response);
    callback(null, event);
  } else {
    callback(null, event);
  }
};

And i just modify both callback(null,event);.
@ctjlewis

@SalahAdDin Ah yeah, that is the wrong file, but you're very close. Look for a file called index.js in that same directory, right next to it. It will look like the snippet I posted above. Add the return event statement and let me know if it works.

const moduleNames = process.env.MODULES.split(',');
const modules = moduleNames.map(name => require(`./${name}`));

exports.handler = (event, context, callback) => {
  for (let i = 0; i < modules.length; i += 1) {
    const { handler } = modules[i];
    handler(event, context, callback);
  }

  return event;
};

This one?

Yes, perfect. amplify push and let me know how it goes.

I would like but i find the same problem with another places: https://github.com/aws-amplify/amplify-cli/issues/7196
Actually, the CLI is not so much helpful with those errors.

Can you try overwriting the index.js in the various amplify/functions dirs? There should be several, but making sure they all return the events they're supposed to should get this working in the meantime while we work on a fix.

I think the another one is this:
/* eslint-disable */
/*
 * Copyright 2019-2019 Amazon.com, Inc. or its affiliates. All Rights Reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with
 * the License. A copy of the License is located at
 *
 *     http://aws.amazon.com/apache2.0/
 *
 * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
 * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions
 * and limitations under the License.
 */
const awsServerlessExpress = require('aws-serverless-express');
const app = require('./app');

const server = awsServerlessExpress.createServer(app);

exports.handler = (event, context) => {
  console.log(`EVENT: ${JSON.stringify(event)}`);
  awsServerlessExpress.proxy(server, event, context);
};

Very weird. You could add a return event statement to that one also to be safe.
I did not run into these issues in my own configuration and will try to reproduce later today.

CREATE_FAILED               MFALambdaInputs                                                        Custom::LambdaCallout      Wed Apr 28 2021 07:42:30 GMT+0300 (GMT+03:00) Response is not valid JSON
UPDATE_ROLLBACK_IN_PROGRESS amplify-thesiscancer-dev-104158-auththesiscancer7a6cf6e7-14VWV365GEC8A AWS::CloudFormation::Stack Wed Apr 28 2021 07:42:31 GMT+0300 (GMT+03:00) The following resource(s) failed to create: [MFALambdaInputs].
⠙ Updating resources in the cloud. This may take a few minutes...

UPDATE_FAILED               auththesiscancer7a6cf6e7        AWS::CloudFormation::Stack Wed Apr 28 2021 07:42:39 GMT+0300 (GMT+03:00) Embedded stack arn:aws:cloudformation:us-east-2:295982313172:stack/amplify-thesiscancer-dev-104158-auththesiscancer7a6cf6e7-14VWV365GEC8A/fa1fce70-8174-11eb-8a21-063ea9f5776c was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to create: [MFALambdaInputs].
UPDATE_ROLLBACK_IN_PROGRESS amplify-thesiscancer-dev-104158 AWS::CloudFormation::Stack Wed Apr 28 2021 07:42:40 GMT+0300 (GMT+03:00) The following resource(s) failed to update: [auththesiscancer7a6cf6e7].

Nothing yet.

Ah, very sorry Salah - I will try to dig into this, and get some other eyes on it. I have been working on (and successfully patched) the same error in a different context so we're close, but not there yet. Rest assured this is not something wrong with your config.

@ctjlewis So, it is related to the generated code, right?

As I understand it, there are triggers generated by the CLI that do not return events when they are expected to, so these stacks fail when they depend on the results of a previous trigger getting passed to the next, which shows up as "Invalid JSON" (because it got undefined). I had this with the Add User to Groups functionality.

/*
this file will loop through all js modules which are uploaded to the lambda resource,
provided that the file names (without extension) are included in the "MODULES" env variable.
"MODULES" is a comma-delimmited string.
*/
const moduleNames = process.env.MODULES.split(',');
const modules = moduleNames.map(name => require(./${name}));
exports.handler = async (event, context, callback) => {
for (let i = 0; i < modules.length; i += 1) {
const { handler } = modules[i];
// tmp fix seem to work
await handler(event, context, callback);
context.done(null, event);
}
};

Good work around @Dahriel, return event inside the async top-level handler should also work.
Fix is ready with #7219, just waiting on review. cc @edwardfoyle @jhockett

Sorry for the late chime in, but for a lambda trigger case, why not just remove that generated code as the current fix... I mean, user land fix rather than from the Amplify codebase. :D

The generated code is emitted based on templates in the CLI source code. Deleting the files in the amplify/ directory would remove the corresponding functionality completely.
We have a fix ready and are just working on the final touches. cc @medelman17

Just hit this problem, at the tail-end of working out why my post confirmation (add to group) trigger is not being added to the pool, and does not have correct policies. Any connection to this problem or co-incidence?

@BruceWheaton It's totally possible it's related to this issue. The team should be merging #7219 shortly, which should resolve this for everyone, including @SalahAdDin.
cc @renebrandel


Missing workflow_examples

02_Model_Code\river-dl\river_dl\workflow_examples is empty - looks like it is intended to have code in it.

Addressed in #5


Full precision must be dispayed with Decimal Datatype

Context
We would like to see the full precision of decimal/float datapoints within visualize – either within the charts directly or when hovering over a datapoint.
Current Behavior
Currently, the behaviour of the application is such that the full precision of the data coming from LINDAS is not displayed. Small values, in particular, are problematic, as they can be truncated to 0.
Expected Behavior
The application should provide a means for the user to see the full precision of a datapoint – either in the chart display or, at least, in the tooltip for the datapoint.
Full precision must be dispayed for decimal numbers. It concerns table chart, mouse over, axis labels, other places? For export, already ok.
Datasets
The dataset "Greenhouse gas emissions by sector and by gas (hierarchie Gas)" can be used as an example/ for testing. Select the Gas "Synthetic gas" and the sector "Sectors CO2 Ordinance". . - -

https://int.visualize.admin.ch/en/v/mDYTVQkRhvvU
https://int.visualize.admin.ch/en/v/_vkg3ZVUnAZU

References

See also https://gitlab.ldbar.ch/bafu/umweltdatenkiosk-planning/-/issues/361#note_8490
Corresponding GitLab Isssue: https://gitlab.ldbar.ch/bafu/umweltdatenkiosk-planning/-/issues/408

Decision: Show full percision expressed as scientific notation.
Example: https://www.covid19.admin.ch/en/epidemiologic/waste-water/d/development?wasteWaterFacility=427100&rel=abs
Also see comment in Gitlab. https://gitlab.ldbar.ch/bafu/umweltdatenkiosk-planning/-/issues/408#note_8894


added IDC collections statistics query, named  query_stats_agg_idc.txt in the root folder.

@fedorov

Just to motivate you to improve your git skills:

Rebase the commits into a single commit
While rebasing, update the commit message to follow https://slicer.readthedocs.io/en/latest/developer_guide/contributing.html
Force-push the local content to your branch

@vkt1414 can answer questions! ;-)

Just to motivate you to improve your git skills:

Rebase the commits into a single commit
While rebasing, update the commit message to follow https://slicer.readthedocs.io/en/latest/developer_guide/contributing.html
Force-push the local content to your branch

@vkt1414 can answer questions! ;-)

git rebase -i HEAD~3

Rebase the commits into a single commit

@ccosmin97 please read this: https://docs.github.com/en/get-started/using-git/using-git-rebase-on-the-command-line


How to use equal Option?

I think this is noobish question, I try to use equal but it always gave me an error.
router.post('/reset', jsonParser, datalize([field('newPassword', 'New Password').length(6,12).required(), field('confirmPassword', 'Confirm Password').length(6,12).equal(field("newPassword")).required() ]), routes.users.resetPassword);
I think my code is right but it did not work as expected. Thank you.

Hi @igumigu ,
.equal() takes value that should be compared, e.g. .equal('string').
To make 2 fields equal you will have to use custom filter:
.custom(async (value, result) => {
  if (await result.getValue('confirm') !== value) {
    throw new Error('Values must be equal.');
  }
})


Bioclinica - clicking on "Bioclinica Careers"  does not open  "Bioclinica Careers" website

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:
1.Open the URL in the browser
2.Search for "Bioclinica" Company
3. Click on "Bioclinica"
4. Hover over "Bioclinica" Logo
5. Click on "Bioclinica Careers"
EXPECTED RESULTS:
By clicking on "Bioclinica Careers" should open  "Bioclinica Careers" website
ACTUAL RESULTS:
"Bioclinica Careers" does not open  "Bioclinica Careers" website

Fixed

Can you retest?

Re-teste, Careers button opens Bioclinica Career page.


Ttkbootstrap and Ttkcreator crash with no error message when launched from command line

Desktop (please complete the following information):
ttkbootstrap 1.10.1
OS: Windows 10
Describe the bug
When py -m ttkbootstrap or py -m ttkcreator is run at the command line, it does something for a couple of seconds and then crashes silently (no error message). Weirdly, ttkbootstrap still works when imported as a module.
To Reproduce

Open command prompt
Enter py -m ttkcreator or py -m ttkbootstrap
Press Enter
Crash without an error message

Expected behavior
Ttkcreator and ttkbootstrap should run
Screenshots

Additional context
No response

Already tried fix from #497, didn't help

Ttkcreator appears to crash somewhere around here

It actually seems like it crashes even earlier now

Nevermind, still seems to crash somewhere inside DemoWidgets

This appears to be caused by https://github.com/israel-dryer/ttkbootstrap/issues/568


Suggestion: Pre moving indicator

Hello, thanks for providing this tool!
Have you considered adding some sort of indicator / overlay / sound option to trigger few secs before the window moves? This is really frustrating when it switches ms before clicking on an action, for example when clicking on a Chrome tab and it shifts to the tab closing button at that exact moment.
To be honest, sadly I find it unusable in those conditions.

Hi there,
I totally understand your frustration. I’ve found myself almost starting Discord calls and waiting for the windows to move before clicking on something important.
I’ve been thinking of adding a small red dot to the taskbar icon right before the windows are about to move. This might be too subtle, especially since many OLED users might want to hide the taskbar.
I'm hesitant to add a more obtrusive overlay, but I'm open to ideas. Do you think the dot would be sufficient, or do you have other suggestions on how to best handle this?

Hey, thanks for your reactivity and enthusiasm!
I was thinking about setting a blinking border few seconds around the focused window. I'm totally stranger to Windows API, but apparently this can be done through WS_BORDER in the Win32 API (see: https://falloutsoftware.com/tutorials/win/win5.htm)
This could be a border such as the native textarea outline:

Also, I think you would need to add an alternative/second option as a sound effect. Some free licensed notify/alert sound effects you might find interesting: https://pixabay.com/sound-effects/search/alert
I like this one, it's not too weird, too long or too dimmed:


Incorrect unused varible warning in let-expr

Description:
$subject
Steps to reproduce:
var _ = let null n = null in function(int? i = n) returns boolean { // unsed variable 'n'
        return i == ();
    };

Affected Versions:
Ballerina 2201.0.0 (Swan Lake)

Since this is only with parameter defaults, https://github.com/ballerina-platform/ballerina-lang/pull/31589 may fix this.
@chiranSachintha, can you please check?

Since this is only with parameter defaults, #31589 may fix this.
@chiranSachintha, can you please check?

This issue is still not fixed with that changes. I will check on that.


Rename the facets as per open lineage standard facets

Description
What is the current behavior?

Facet names should be as per https://github.com/OpenLineage/OpenLineage/blob/main/spec/OpenLineage.md#standard-facets.
To avoid naming conflicts, make sure that custom facets have a common prefix in their name related to the project that defines them: https://github.com/OpenLineage/OpenLineage/blob/main/spec/OpenLineage.md#custom-facet-naming

closes: #1101
What is the new behavior?

Return empty TaskMetadata as part of extract() method.
Rename facet names as per https://github.com/OpenLineage/OpenLineage/blob/main/spec/OpenLineage.md#custom-facet-naming
Test and run on Marquez UI

Does this introduce a breaking change?
No
Checklist

[x] Attached the screenshot of marquez UI
[x] Created tests which fail without the change (if possible)
[x] Extended the README / documentation, if necessary

Rebase from main please

Done

A general comment - is there a way for us to prevent a regression.
Don't want to block this PR -- but want us to take care of it in the next sprint

@kaxil This was something which was share after yesterdays discussion with open lineage team.
But will take of this going forward.


Hello how to use direction top?

Hello,
Thanks for this package.
I wanted it to use top direction like in chat.
I already set position but its not working, its still default to bottom direction.
Please help, thanks.

Hi,
Sorry i solved it, i missed the example.
Thanks for this great package.


pid_m calculation in matmul.py

I'm reading matmul.py source code. Should pid_m calculation be pid_m = group_id * GROUP_M + (pid // grid_n) % GROUP_M, instead of pid_m = group_id * GROUP_M + (pid % group_size).

https://github.com/openai/triton/issues/2864
Close as duplicate


Add warning message when transaction_max_spans is exceeded

Simply as it says above. Fixes #849
Checklist

[x] Implement code
[x] Update documentation
[x] Update CHANGELOG.md

Thanks for the PR!
Please see the comment.
Also, in order for us to be able to merge this PR, please sign the CLA.

Eh I've tried twice now. Originally I added @ in my github username and figured since it didn't pick right up I should have maybe not done that and did it a second time without it. Any thoughts or should I just wait longer for the bot to pick it up??

We're good now 👍

Codecov Report

Merging #890 into master will decrease coverage by 0.49%.
The diff coverage is 75%.

@@             Coverage Diff             @@
##             master     #890     +/-   ##
===========================================
- Coverage     64.95%   64.46%   -0.5%
  Complexity       85       85
===========================================
  Files           231      231
  Lines          9610     9446    -164
  Branches       1262     1232     -30
===========================================
- Hits           6242     6089    -153
+ Misses         2979     2969     -10
+ Partials        389      388      -1

Impacted Files
Coverage Δ
Complexity Δ

...tic/apm/agent/configuration/CoreConfiguration.java
96.55% <ø> (-0.74%)
0 <0> (ø)

...va/co/elastic/apm/agent/impl/ElasticApmTracer.java
73.97% <75%> (-4.78%)
0 <0> (ø)

Continue to review full report at Codecov.

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


2155 ux changes for between cycles

Context

Changes proposed in this pull request
The three major UX changes for end of cycle are:

Allow users to continue to view their application choices until they have carried over an application. Not doing so meant that people were unable navigate to offers or view what applications were awaiting provider decision.
Do not allow candidates with inactive applications to carry over. We should treat inactive applications like 'awaiting provider decision'. They are rejected by default on the 24th.
We had multiple carry over experiences -- sometimes people were redirected to the applications page with some inset text. Sometimes they were sent to the Carry over page. Now they will all of the same experience of going to the carry over page, keeping things much simpler

I've also

Added lots of tests for candidates as they move through the end of cycle period with application choices in different states.
Deleted skipped tests that are no longer relevant
Updated skipped tests so they can be run again
Removed hard coded dates from specs

Guidance to review

Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault
[ ] Inform data insights team due to database changes
[ ] Make sure all information from the Trello card is in here
[ ] Rebased main
[ ] Cleaned commit history
[ ] Tested by running locally
[ ] Add PR link to Trello card

 Implement UX for candidate during end of cycle


[RELENG-5833] catch error in EachLimit to throw it cleanely

Hello erwan-b,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Conflict
There is a conflict between your branch feature/RELENG-5833/raise-clean-error-EachLimit and the
destination branch development/3.0.
Please resolve the conflict on the feature branch (feature/RELENG-5833/raise-clean-error-EachLimit).
git fetch && \
git checkout origin/feature/RELENG-5833/raise-clean-error-EachLimit && \
git merge origin/development/3.0

Resolve merge conflicts and commit
git push origin HEAD:feature/RELENG-5833/raise-clean-error-EachLimit

Conflict
A conflict has been raised during the creation of
integration branch w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit with contents from feature/RELENG-5833/raise-clean-error-EachLimit
and development/3.0.
I have not created the integration branch.
Here are the steps to resolve this conflict:
 $ git fetch
 $ git checkout -B w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit origin/development/3.0
 $ git merge origin/feature/RELENG-5833/raise-clean-error-EachLimit
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit

Integration data created
I have created the integration data for the additional destination branches.

this pull request will merge feature/RELENG-5833/raise-clean-error-EachLimit into
development/2.0
w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit will be merged into development/3.0 (pull request #104)

The following branches will NOT be impacted:

development/1.0

Follow integration pull requests if you would like to be notified of
build statuses by email.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

one peer

Conflict
A conflict has been raised during the update of
integration branch w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit with contents from feature/RELENG-5833/raise-clean-error-EachLimit
and development/3.0.
Please resolve the conflict on the integration branch (w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit).
Here are the steps to resolve this conflict:
 $ git fetch
 $ git checkout w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit
 $ git pull  # or "git reset --hard origin/w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit"
 $ git merge origin/development/3.0
 $ # <intense conflict resolution>
 $ git commit
 $ git merge origin/feature/RELENG-5833/raise-clean-error-EachLimit
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit

History mismatch
Merge commit #31d1c1be3516b09771814292469e27baf877d1df on the integration branch
w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit is merging a branch which is neither the current
branch feature/RELENG-5833/raise-clean-error-EachLimit nor the development branch
development/3.0.
It is likely due to a rebase of the branch feature/RELENG-5833/raise-clean-error-EachLimit and the
merge is not possible until all related w/* branches are deleted or updated.
Please use the reset command to have me reinitialize these branches.

/force_reset

Reset complete
I have successfully deleted this pull request's integration branches.

Conflict
A conflict has been raised during the creation of
integration branch w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit with contents from feature/RELENG-5833/raise-clean-error-EachLimit
and development/3.0.
I have not created the integration branch.
Here are the steps to resolve this conflict:
 $ git fetch
 $ git checkout -B w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit origin/development/3.0
 $ git merge origin/feature/RELENG-5833/raise-clean-error-EachLimit
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit

Integration data created
I have created the integration data for the additional destination branches.

this pull request will merge feature/RELENG-5833/raise-clean-error-EachLimit into
development/2.0
w/3.0/feature/RELENG-5833/raise-clean-error-EachLimit will be merged into development/3.0 (pull request #105)

The following branches will NOT be impacted:

development/1.0

Follow integration pull requests if you would like to be notified of
build statuses by email.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

one peer

/approve

Queue out of order
The changeset has received all authorizations to enter the merge queue,
however the merge queue is currently in an incoherent state. In order
to protect this pull-request, I have not added the changeset to the
queue.
Please contact a member of release engineering.
The following options are set: approve

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/2.0

:heavy_check_mark: development/3.0

The following branches will NOT be impacted:

development/1.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.
The following options are set: approve

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/2.0

:heavy_check_mark: development/3.0

The following branches have NOT changed:

development/1.0

Please check the status of the associated issue RELENG-5833.
Goodbye erwan-b.


Bug in HyperSQL DB

I have filed https://sourceforge.net/p/hsqldb/bugs/1680/
This issue was discovered using this tool and it causes many of the tests to fail.
There is no other good place to mention this, so I am just opening an issue here too.

Bugs in underlying DBs will be the exception rather than the rule. A bug in HSQLDB (or Calcite) does not automatically become a bug in sql-logic-test (SLT).
SLT should have:

A means to disable tests (files and queries within the files);
A means to filter queries (e.g. convert minus space minus to minus minus or to nothing, if that is the workaround to HSQLDB 1680).

Do you consider this a blocking bug for SLT version 0.1? What do you consider to be a reasonable fix?

There is a way to disable tests using the -b argument, but there are literally tens of thousands of failures caused by this one problem, so that's not a workable approach - unless we automate generating that file.
I don't think this is a bug in SLT, just wanted to point out what SLT can do. We may want a way to keep track of the bugs discovered using SLT in other databases.
This suggests a different issue I will file: a way to automatically cluster bugs so that different queries that trigger the same bug produce a single bug report instead of thousands.


chore: bump lune version

The new lune version includes the latest version of rbx_cookie which is required to fix the latest roblox cookie format.

oh good catch


Update devsign title

The "is how it works" part is meant to be a subtitle on the site, not part of the title (but I can see how the site design doesn't communicate that well enough! I'll tweak my page design over there, too.)
Cheers!

Thanks!


Shortcut for accessing StreamField blocks by block name/type

Rebase of #7266 by @Tijani-Dia.
See #7240
This PR adds three methods/shortcuts to StreamValue class.

blocks_by_type Arguments: None
This method returns a  dict consisting of all blocks organised by type.
It allows writing something like the following in templates:
<h1>{{ page.body.blocks_by_type.heading.0 }}</h1>

blocks_of_type Arguments: block_type
This method returns all blocks of type block_type.

first_block_of_type Arguments: block_type
This method returns the first block of type block_type

Do the tests still pass?
Yes
Does the code comply with the style guide?
Yes
For Python changes: Have you added tests to cover the new/fixed behaviour?
Yes
For new features: Has the documentation been updated accordingly?
Not yet. I will add it if the implementation is approved.

Final tweaks and documentation added - just needs someone to review the last 3 commits. (@lb- ?)

Will look at this now - sorry @gasman must have missed the notification


Release 58

Coverage increased (+0.01%) to 32.013% when pulling 0416deb9427a73162642a1857c22cbf3f6d2baae on current into 7f96b11f711192f71074cad51c55deef6beffcf7 on master.


fixed_speed in StepWalker to be used to pass custom speeds

Changes:

Use fixed_speed in StepWalker to pass custom values from 0.0 to stay put to float("inf") to teleport
use StepWalker regardless of walk_min speed

@mjmadsen closed because StepWalker does not support yet speed = 0 or float("inf")


Edit API Endpoint -  Appendix E Heat Input from Oil Data

Create API endpoint for Edit for Appendix E Heat Input from Oil Data
Testing Reference Only:
Monitoring System ID
Oil Mass
Oil GCV
Oil GCV Units of Measure Code
Oil Heat Input
Oil Volume
Oil Volume Units of Measure Code
Oil Density
Oil Density Units of Measure Code

Test Case: TC984

Test Passed


Update astropy-helpers to v1.3.1

This is an automated update of the astropy-helpers submodule to v1.3.1. This includes both the update of the astropy-helpers sub-module, and the ah_bootstrap.py file, if needed.
This is intended to be helpful, but if you would prefer to manage these updates yourself, or if you notice any issues with this automated update, please let @bsipocz or @astrofrog know!

Bad news, it seems that astroplan yet again has failing test with the new astropy. I haven't had a chance to investigate, but from the cron builds it seems that something got merged upstream between 18&11 days ago caused the regression.

@bsipocz gah!
The root cause seems to be changes made to the SkyCoord object, which I'm guessing is now better at recognising if two coordinates are identical.
When a scheduler inserts two ObservingBlocks of the same target next to each other, we also insert a TransitionBlock. Previously this would have a very small, but non-zero duration. It is now zero.
This then causes havoc here, because the start and end time of the TransitionBlock are identical and so filled is an empty array.
The bug here is inserting a TransitionBlock  between two identical ObservingBlocks.

Failures are related to the issues resolved in #295. Should pass once that is merged, and upstream fix is in place in astropy.


feat: scroll_past_bottom option

Fixes #72
Needs formatting, not sure which formatter options to use.

I just realized this prevents zz from working. So not ready to merge


[PLAT-840] API should return null for empty to-one relationships instead of omitting them

Purpose
From the ticket:
According to the JSON API Spec, empty to-one relationships MUST be represented by null. Instead, (at least for the primary_file relationship on preprints) our API simply omits empty to-one relationships in the response. An example of the appropriate response for an empty to-one relationship can be found here (second example).
Ember apps need this information to remove relationships in the client-side data store.
Changes

One line fix adding null data
new test.

QA Notes
Fields which normally wounldn't appear contextually for certain nodes etc should appear with data as null in the API, some examples would include:

The license field for nodes without a license.
The primary_file field for preprints without primary files i.e. orphan preprints.
The registered from field for unregistered nodes.

There are many more examples, but you get the idea, essentially now all relationship fields should always be present.
Documentation
Hmm, I can't think of anything appropriate , but definitely changes to the API should be documented, even though I can't conceive of a situation this is really relevant other then just assuring we are in compliance with the JSON API Spec.
Side Effects
None that I know of.
Ticket
https://openscience.atlassian.net/projects/PLAT/issues/PLAT-840

This is headed to staging3.


Remove duplicate shuffle array snippets. Simplify implementation

Thanks for contributing! This issue has been brought up before, I think. I only kept the order randomizer as it is biased and produces different results than shuffle. Not certain if we should keep it, though. Any other opinions?

"Shuffle array values" is an incorrect implementation. The sort comparator arguments are the actual values and not indices, so r[a] and r[b]will beundefined` unless the keys existence coincidentally.

Check Will it Shuffle? to see my justification.
The randomize-order-of-array.md snippet is under sort (random comparator) and out shuffle-array-values.md is sort (random order). The first one is biased, the second one isn't. Also, it seems that the shuffle method works perfectly fine. Am I missing something?

shuffle([4,5,6]) will always return [4,5,6].

You're right @darrenscerri. That is really bad. Ok, I'm gonna merge your PR then.

There is still some bias with the merged solution, but is fine for most use cases.


Go-rancher to match v1.6.11 rc

https://github.com/rancher/go-rancher/pull/199 has to be merged first

Very stale. Closing. Thanks! Please open a new PR if there is still a relevant change.


Register Package

@JuliaRegistrator register()

Error while trying to register: "Pre-release version not allowed"


oebs-cloud.sh- Not deleting the resources vpc and dhcp-options.

-Created an OpenEBS cluster in AWS using oebs-cloud.sh script.
-Tried to delete the cluster using the same script.
-It was failing to delete the resources vpc and dhcp-options. It retried to delete these resources for 10 minutes and then failed.
 Not all resources deleted; waiting before reattempting deletion
        dhcp-options:dopt-5b914923
        vpc:vpc-dbbe56a0
vpc:vpc-dbbe56a0        still has dependencies, will retry

Not all resources deleted; waiting before reattempting deletion
        vpc:vpc-dbbe56a0
        dhcp-options:dopt-5b914923

Not making progress deleting resources; giving up

Kops delete cluster failed with errors, please check logs..

An error occurred (BucketNotEmpty) when calling the DeleteBucket operation: The bucket you tried to delete is not empty
Failed to delete s3 bucket, please check logs

Platform : AWS
Cli machine : Ubuntu-16.04
K8s version : 1.7.11

Closing this issue, as this is not seen now.


fix(viewmodel): View model and scope can both use 'getReactively'

What if someone wants to use $scope.helpers and vm.helpers?
It won't work so should we support it?
$scope.helpers({
    foo() { return FooCollection.find({}); }
});

vm.helpers({
    bar() { return BarCollection.find({}); }
});

// check foo
$scope.foo // undefined
vm.foo // defined

// check bar
$scope.bar // undefined
vm.bar // defined

@kamilkisiela we are going to solve this scenario as well, even though it's a horrible pattern :)
but because it's a breaking change we will solve it.

@kamilkisiela @Urigo See https://github.com/Urigo/angular-meteor/pull/1278/commits/c48a1f552d9f1ba7ffc014713a258676aa02b583#diff-a3547eb36ef3a55c1cedddba5195e00fR392