Am I doing it wrong?  - [FATAL] exit status 2 - xcaddy build v2.4.6 --with github.com/caddy-dns/cloudflare

I am sorry for pasting just a log here, but I cannot catch for anything meaningful (to not bother you).

I installed go 17.3 and latest xcaddy.

xcaddy version - v0.2.0 h1:PLtoEQ5LjjYQNyHEnFM+rWP9HYfxQejlYkBKE0M9vso=
ubuntu 20.0.4 aarch64 - up to date.
go 1.17.3
The moment I try to build it with
xcaddy build v2.4.6 --with github.com/caddy-dns/cloudflare@latest

I get fatal.
ubuntu@ip-172-31-17-201:~/go/bin$ sudo tar -C /usr/local -xzf go1.17.3.linux-arm64.tar.gz
ubuntu@ip-172-31-17-201:~/go/bin$ xcaddy build v2.4.6 --with github.com/caddy-dns/cloudflare@latest
2021/12/03 10:50:12 [INFO] Temporary folder: /tmp/buildenv_2021-12-03-1050.1397751167
2021/12/03 10:50:12 [INFO] Writing main module: /tmp/buildenv_2021-12-03-1050.1397751167/main.go
2021/12/03 10:50:12 [INFO] Initializing Go module
2021/12/03 10:50:12 [INFO] exec (timeout=10s): /usr/local/go/bin/go mod init caddy
go: creating new go.mod: module caddy
go: to add module requirements and sums:
	go mod tidy
2021/12/03 10:50:12 [INFO] Pinning versions
2021/12/03 10:50:12 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -d -v<EMAIL_ADDRESS>go get: added github.com/beorn7/perks v1.0.1
go get: added github.com/caddyserver/caddy/v2 v2.4.6
go get: added github.com/caddyserver/certmagic v0.15.2
go get: added github.com/cespare/xxhash/v2 v2.1.1
go get: added github.com/golang/protobuf v1.5.2
go get: added github.com/google/uuid v1.3.0
go get: added github.com/klauspost/cpuid/v2 v2.0.9
go get: added github.com/libdns/libdns v0.2.1
go get: added github.com/matttproud/golang_protobuf_extensions v1.0.1
go get: added github.com/mholt/acmez v1.0.1
go get: added github.com/miekg/dns v1.1.43
go get: added github.com/prometheus/client_golang v1.11.0
go get: added github.com/prometheus/client_model v0.2.0
go get: added github.com/prometheus/common v0.26.0
go get: added github.com/prometheus/procfs v0.6.0
go get: added go.uber.org/atomic v1.7.0
go get: added go.uber.org/multierr v1.6.0
go get: added go.uber.org/zap v1.19.0
go get: added golang.org/x/crypto v0.0.0-20210915214749-c084706c2272
go get: added golang.org/x/net v0.0.0-20210913180222-943fd674d43e
go get: added golang.org/x/sys v0.0.0-20210915083310-ed5796bab164
go get: added golang.org/x/term v0.0.0-20210503060354-a79de5458b56
go get: added golang.org/x/text v0.3.7
go get: added google.golang.org/protobuf v1.27.1
2021/12/03 10:50:14 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -d -v github.com/caddy-dns/cloudflare@latest
go get: added github.com/caddy-dns/cloudflare v0.0.0-20210607183747-91cf700356a1
go get: added github.com/libdns/cloudflare v0.1.0
2021/12/03 10:50:14 [INFO] Build environment ready
2021/12/03 10:50:14 [INFO] Building Caddy
2021/12/03 10:50:14 [INFO] exec (timeout=0s): /usr/local/go/bin/go mod tidy
2021/12/03 10:50:15 [INFO] exec (timeout=0s): /usr/local/go/bin/go build -o /home/ubuntu/go/bin/caddy -ldflags -w -s -trimpath
# runtime/internal/sys
/usr/local/go/src/runtime/internal/sys/stubs.go:9:7: PtrSize redeclared in this block
	/usr/local/go/src/runtime/internal/sys/arch.go:24:38: previous declaration
/usr/local/go/src/runtime/internal/sys/stubs.go:10:24: undefined: Uintreg
/usr/local/go/src/runtime/internal/sys/stubs.go:16:7: StackGuardMultiplier redeclared in this block
	/usr/local/go/src/runtime/internal/sys/arch.go:27:74: previous declaration
2021/12/03 10:50:15 [INFO] Cleaning up temporary folder: /tmp/buildenv_2021-12-03-1050.1397751167
2021/12/03 10:50:15 [FATAL] exit status 2

Caddy v2.2.3 h1:xxMaF/Nb3B5VhXkQREvjGUdfDgseMmc5IyhUktYO7gM= is already installed on the same machine. Could that be an issue?

Ok this has to do with how go lang is being upgraded.
More info here: https://github.com/golang/go/issues/48134
The important step I was missing is just below. I had to cleanup my go folder.
sudo rm -rf /usr/local/go

install a fresh go copy
sudo wget -c https://golang.org/dl/go1.17.3.linux-arm64.tar.gz
sudo tar -C /usr/local -xzf go1.17.3.linux-arm64.tar.gz

Then execute
xcaddy build v2.4.6 --with github.com/caddy-dns/cloudflare@latest

Everything has worked like a charm.

Ah, yep. When installing Go you need to remove old versions because file extractions don't necessarily remove old files that aren't supposed to be there anymore. Thanks for following up!


visualpriors source code

Hi,
Thanks for providing this tool. I want to use the visualpriors in my project. And I am considering maybe I can extend the visualpriors by including new features. However, I can't find the  source code for this package. The only repository I found is: https://github.com/alexsax/visual-prior. But only checkpoint files are included. Is it redirected to somewhere else?
Thanks

Hi,
https://github.com/alexsax/visual-prior is indeed the correct repository. Right now there are two branches: master (with source code) and networks with checkpoints. I just switched the default branch back to master so hopefully the source code should now be easier to find.
Let me know if this link isn't what you want: https://github.com/alexsax/visual-prior/tree/master
Thanks for reaching out!


Add extend-access-ws web service sample for OIG/WebLogic

WebService which is complementary to #361.

@mgere-oracle Please see olaf Feedback.

@mgere-oracle Please see olaf Feedback.

I have addressed all the points raised by @oheimburger. Please let me know if there's anything left pending from my side.


VirtualBox appliance does not boot to KDE login

Issue description
Using the official VirtualBox .ova from here, no KDE login appears, contrary to the description following it ("... When the KDE login screen appears ...").
Steps to reproduce
Download, install and start .ova as described on http://nixos.org/nixos/download.html.
Technical details

VirtualBox 5.0.28

journalctl log http://pastebin.com/eG3EFVxX.

I believe this is from #16641 being broken again.


[feat][jdbc-#1300]add parameter pollingFromMax

… pollingMode starts with the maximum value of the incrementColumn

Purpose of this pull request

Set the parameter 'pollingFromMax=true' so that the pollingMode starts with the maximum value of the incrementColumn
Which issue you fix
Fixes # (issue).
#1300
Checklist:

[ ] I have executed the 'mvn spotless:apply' command to format my code.
[ ] I have a meaningful commit message (including the issue id, the template of commit message is '[label-type-#issue-id][fixed-module] a meaningful commit message.')
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have checked my code and corrected any misspellings.
[ ] My commit is only one. (If there are multiple commits, you can use 'git squash' to compress multiple commits into one.)

@baisui1981 @FlechazoW


Release 24.3

coverage: 90.557%. first build
when pulling 6ed71ba984335613dc1e149cd3e761aa28dd70b6 on release/24-3
into 805b78a75ba54564f3898cf9fc2447736c9746a2 on main.


pick not working under tmux

I'm running on OSX.
$ ls | pick
Traceback (most recent call last):
File "/usr/local/Cellar/pick/0.0.2/libexec/src/pick.py", line 76, in <modul
exit(main())
File "/usr/local/Cellar/pick/0.0.2/libexec/src/pick.py", line 67, in main
output = curses.wrapper(view.run)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.
urses/wrapper.py", line 43, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/local/Cellar/pick/0.0.2/libexec/src/view.py", line 58, in run
self._setup_curses(screen)
File "/usr/local/Cellar/pick/0.0.2/libexec/src/view.py", line 43, in _setup
rses
curses.init_pair(1, 251, curses.COLOR_BLACK)
_curses.error: init_pair() returned ERR
$

I'm confused, this seems related to bernardorufino/pick and not
thoughtbot/pick. Looks like someone reported the same problem:
bernardorufino/pick#15.

Sorry, I think you're right.


Validation message in JSON Schema

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ x] support request

Current behavior

We use JSON Schema for our app and you have provided some example.
We saw your example to pass validation message in the FormlyFieldConfig schema here.
Similarly, we would like to supply validation message as part of JSON Schema.
The validation message could be static or dynamic based on the content in current control or any other control in the form.
There are many such validation used in FormlyFieldConfig.
May I know where can I find all possible validation in your documentation.
How to apply the same in JSON schema
For instance
{
      key: 'maxWordCount',
      type: 'textarea',
      templateOptions: {
        label: 'maxWordCount',
        maxWordCount: 4,
        rows: 5,
      },
      validation: { show: true }
    },

The above example uses maxWordCount and rows.
How do I give this in JSON Schema.
Please advise.
Expected behavior

Validation Message could not be provided in the JSON schema.
You have given example to add generic validation function at the module level.
but we want to define at the JSON Schema level.
Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

We prefer to use JSON Schema.
Please tell us about your environment:

Windows 10

Angular version: 2.0.X

Angular 8

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

Node (for AoT issues): node --version =

similar to https://github.com/ngx-formly/ngx-formly/issues/1772#issuecomment-530618830, in json-schema you can pass a custom formly config through widget property.

Hi Abdellatif Ait boudad,
Thank you very much for the response.
I tried as per your suggestion to set textarea rows and maxWordCount but it is not working.
Similarly tried validation message for IP that also not works.
Please find the same here and advise.
        "properties": {
          "firstname": {
            "type": "textarea",
            "title": "First name",
            "widget": {
              "formlyConfig": {
                "maxWordCount": 25,
                "rows": 5
              }
            },
          },
          "ip": {
            "$id": "#/properties/ip",
            "type": "string",
            "title": "The Ip Schema",
            "default": "",
            "examples": [
            "111.123.789.654"
            ],
           "pattern": "^(\\d{1,3}\\.){3}\\d{1,3}$",
           "widget": {
            "validation": {
               "messages": {
                 "pattern": (error, field: FormlyFieldConfig) => `${field.formControl.value} is not a valid IP Address`
                }
              }
            }
          }
        },

Thanks
Raj

your json is not valid, here is a working example https://stackblitz.com/edit/angular-multi-step-json-schema-u3mgpf
for textarea pass those options through templateOptions:
"widget": {
  "formlyConfig": {
    "templateOptions": {
      "maxWordCount": 1,
      "rows": 5
    }
  }
},

for ip field:
"widget": {
  "formlyConfig": {
    "validation": {
      "messages": {
      "pattern": (error, field: FormlyFieldConfig) => `${field.formControl.value} is not a valid IP Address`
      }
    }
  }
}

Hi  Abdellatif Ait boudad,
Thanks for timely response.
Raj

Hi,
I face one challenge, when I store the JSON into the file and parse using newtonsoft.
It is not accepting the arrow function without quotes. if I add quotes for arrow function, it is not working.
Please let me know any work around.
Thanks
Raj

Hello, having the same question about validation message.
The example given by @aitboudad is not JSON, it's Javascript. Is it possible to achieve the same by pure JSON?

For those who are willing to use pure JSON for ip field example above https://github.com/ngx-formly/ngx-formly/issues/1775#issuecomment-531279301, you may try with expressionProperties:
"widget": {
  "formlyConfig": {
    "expressionProperties": {
      "validation.messages.pattern": "field.formControl.value + 'is not a valid IP Address'"
    }
  }
}


[FEAT] Updated readme

Closes #1284

Hey @himanshu1221  You have Created PR on wrong Branch,  change the branch from master to dev branch.

Hey @himanshu1221 You have Created PR on wrong Branch, change the branch from master to dev branch.

i have changed the branch @kanishkcs

hey @llaske I have made the changes i have deleted the file from the PR you can review the file and suggest to me the changes if any

Nope. You must remove the main.yml from your PR not from the repo.
If I merge your PR, the file will be removed.

i'l make a seperate PR for the same i am closing this pr


Add missing depth buffer formats to the OpenGL backend

Those formats were supported by all other backends, but still missing for the OpenGL backend.

I've actually found an existing problem, which is a bit tricky to fix. It affects this scenario. Apparently, if we want to modify the depth and stencil sizes, we need to do so before a window is created. Unfortunately, it looks like SDL2 is just giving us default depth/stencil values no matter what we specify here, even though the return values indicate success. The SDL documentation actually does say that you need to call these functions before window creation: https://wiki.libsdl.org/SDL_GL_SetAttribute.
It is a bit tricky because VeldridStartup lets you create a Window separately from the GraphicsDevice. Other backends don't care about this at all. We should be able to fix this in CreateWindowAndGraphicsDevice, but not the standalone CreateGraphicsDevice function.

That's an existing problem and not made any worse by your change. I'll merge this and look into a real fix for the problem.

I merged a fix for the above. Note that 32-bit depth formats don't seem to actually bit supported by SDL2 as far as I can tell (there's not much indication as to what you're actually allowed to pass in). I've improved the error detection when context creation fails as well, because sometimes a non-zero context handle is returned even if context creation failed (I have no idea why).
It seems that all of the other depth formats should be supported, though, including the combined depth-stencil formats.
Additionally, specifying no depth buffer (SwapchainDepthFormat == null) now correctly skips creating the depth buffer.


O.Writable doesn't work well with generics after update to 4.0.10

class M {
  fn(): void {}
  x = 5
}

function f<T extends M>(m: T) {
    const w = m as O.Writable<T>
    w.fn() // complains fn is not there
    w.x = 10 // complains x is not there
}

works ok with the latest version of 3

not sure if related to the old https://github.com/pirix-gh/ts-toolbelt/issues/41

Ping @xaviergonz. I've just fixed it, it was not related to #41, but related to the refactor of 4.0.
This happened when I brought out true type distribution. Not sure why, though, but it seems like type distribution (X extends unknown) can break a deferred generic evaluation, and evaluate it immediately instead.
Please do not hesitate to open a bug, or a question if you see anything else!
Cheers

Build is not passing, let me fix this

It's out

Thanks! Will check it out later

Hmm, I don't see a new version

Sorry, about this. Got a false positive with the CI. It's out (for real)


support $ref

I would love to see support added for the $ref keyword. I have several error messages that are used throughout my schemas, and it would be helpful to only have to define them once.
// error schema
{
  "$id": "errors",
  "string": "must be a string",
  "basicObject": {
    "type": { "$ref": "#/string" }
  }
}

// schema
{
  "type": "string",
  "errorMessage": { "$ref": "errors#/basicObject" }
}

I am trying to validate specific property as below
const valid = ajv.validate({ $ref: `${schemaName}#/properties/${fieldName}` }, value);

and I have property specific error-message defined in schema it does not work.
It only works when I pass full schema object instead of $ref.
Is it in pipeline to support $ref keyword.


set an empty string when string was not provided

preventing TypeError: Cannot read property 'trim' of undefined or TypeError: Cannot read property 'trim' of null

👍


A fix for the issue #892

https://github.com/archtechx/tenancy/issues/892
Described the isuse there in detail, please approve PR if you feel it's a suitable fix. I've tested it my side and everything works as intended.

Hey!
So as I wrote in the email, this feature isn't really intended to work with request data. It may still work (and if it's needed for Passport to work, definitely use it), but it's not intended so we don't want it enabled by default.
As for the change in this PR — you can achieve the same without modifying the package code. Add this to the register() method of AppServiceProvider/TenancyServiceProvider:
UniversalRoutes::$identificationMiddleware = [
    InitializeTenancyByDomain::class,
    InitializeTenancyBySubdomain::class,
    InitializeTenancyByRequestData::class
];

(And import all of those classes)

This wasn't Possible.
	<title>Access to undeclared static property Stancl\Tenancy\Features\UniversalRoutes::$identificationMiddleware (500 		Internal Server Error)</title>

This worked, but you missed the "s" pural out on identificationMiddleware. it's actually identificationMiddlewares.


consider adding suffix "d" to the debug targets

I failed to link release version of tbb to my debug project, the symbols didn't match
And since the debug and release build of tbb output the same file names, I just can't copy them to the same lib folder
Had to rename all tbb targets and do another debug build
So why not adding set(CMAKE_DEBUG_POSTFIX "d") to your root CMakeLists.txt and make the job much easier

Or using set_target_properties (${LIB_NAME} PROPERTIES DEBUG_POSTFIX "d") for each tbb targets to avoid global effect


Navbar issue on home

Description
The navbar does not stick on the top of the page instead scroll with the page.
Screenshots
No response
Additional information
No response
Do you want to work on this issue?

[X] I want to work on this issue.

i would like to work on this issue under GSSOC'23 . please assign this to me


libreswan: 3.18 -> 3.29, addressing CVE-2019-12312 & CVE-2019-10155

Motivation for this change
https://nvd.nist.gov/vuln/detail/CVE-2019-10155
https://nvd.nist.gov/vuln/detail/CVE-2019-12312
This is targeted at staging because of the huge rebuild - however, that rebuild is all due to the small change made to unbound required to persuade it to install its libevent-support headers. I haven't tried a full rebuild of these as the addition of this header to the output shouldn't really affect other packages not looking for it. Famous last words. libreswan itself has no reverse dependencies.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @afranchuk I am not a user of this package so would appreciate some help in testing.

Superficially this looks fine to me, though I can't test anything because I no longer use the package myself...

What should we do regarding 19.09? I don't feel comfortable backporting the patch to 3.18 - a lot of code around this area has changed between the two versions.. but it's also quite a big bump. It's "only" a null pointer dereference, but debian seem to have classed it "grave".


"Open in full editor" button in sandbox mode, fixes #426

If in sandboxOn mode (sandbox=1)

launch full editor without sandbox
If in sandboxPub mode (sandbox:PUBID)
ensure published project is the latest, if not, publish the project, then go to full editor with new published project id (pub:PUBID in the path)
If in sandboxProject mode (sandbox:FILECONTENTS)
export project to get the latest file contents, then go to full editor with project:FILECONTENTS in the path

Note: opening in a new tab, although we might want to consider opening in current tab to avoid ad block.


Build node-gyp without XCode

From the docs I'm told that I must have XCode installed in order to get gcc and make tools.
I have MacOSX with gcc and make installed separately via homebrew.
I'd much rather not install XCode as it messes with a bunch of other stuff and starts taking liberties that I don't like.
Will there ever be an option to install without needing XCode?

Not an officially supported one.  Certainly not in the near future, quite possibly never.


Implement Comprehensive Chaos Testing in Staging Environment

Why:
Before deploying to production, it is crucial to perform comprehensive chaos testing in a staging environment that closely resembles the production setup. This ensures that the system is resilient to failures and behaves as expected under stress conditions.

Raft is not going to be implemented soon.
We should review all Raft tasks if it is coming back.


Elaborate on safe usage of setErrors and setFieldError

📖 Documentation
Elaborate on when it is safe to use setFieldError and setErrors (ie. only in onSubmit or as some kind of side effect, but not as a replacement for actual validation). This is because validation is not aware of the manual usage of these methods, and, in fact, validation will overwrite errors on the next change, blur, or submit attempt.
Related #1278 #706 #1111

bump, i'm interested in this, is it in progress?

oh man... I did 5AM for this reason while implementing a usePersistFState hook

Any workarounds? Still stuck with this.

@kanishk30 currently setErrors and setFieldError are only usable "informationally" outside of validation functions. You can communicate to a user that a given field has a special error state, but validation must also confirm that fact if the user is able to submit the form. A workaround would be to track this exceptional state your own custom state, and disable the submit function (and any custom handlers) if that state is not falsy.
The Formik API will always run field-level and form-level validations before submitting, which will completely override setErrors.
@jaredpalmer I think if we think of the validation process as a series of validators, we could expand the API so devs can add a PersistentValidator (or any kind of custom validator) to the validators list which can always return its internal state instead of being a result of f(formik.values). (And we could detach Yup internals from Formik's internals)


Bundle RBAC related acceptance tests to improve runtime

Pull Request Checklist

Description

Put all RBAC related acceptance tests together.
Related Issue

Relates to #901
Motivation and Context

Some acceptance tests are timing out and appears to be large number of executions of puppet apply.  This change bundles all RBAC acceptance tests into same test blocks to hopefully resolve acceptance test timeouts in travis-ci.
How Has This Been Tested?

time BEAKER_set=debian-8 bundle exec rake beaker which completed in 29 minutes.
General

[ ] Tests pass - bundle exec rake validate lint spec

@ghoneycutt Added comments to previously removed spec files and comment to new rbac spec file. Let me know if they are good enough or need a bit more information.

looks good!

@ghoneycutt This should not be merged.  I'll open a new PR that rules the type/provider tests only on EL7 and run agent/backend tests on all platforms.

Closing in favor of #935


Fix login redirect by replacing useNavigate with window.location.href

This PR fixes an issue where the login redirect was not functioning correctly (etc pre-authorized code) after a successful login. Previously, we used useNavigate to handle the redirect, but due to recent changes (possibly on browser or useNavigate behavior), the navigation was not working as expected.
To resolve this issue, we replaced navigate(from, { replace: true }) with window.location.href = from.pathname + from.search, which ensures the correct redirection to the intended page after login.

Close because the #330 had better approach


Fix the last website link

Although www.contentbox.info appears to not be there any more.

yes sure, [deprecated info-site]


Problem in WindowManager.ShowWindow when trying to show a view located in another assembly

Hello, I want my main assembly to show one view from another assembly. I register the viewModel in the IoC properly and I the instance of the viewModel is created but when I call "this.windowManager.ShowWindow(viewModelInstance)" I get the following error:
"No registrations found for service SaleDocumentsView".
I've been looking at the code for some hours but I can't figure out what's happening. Could anybody help me please?
Thanks

Is your SaleDocumentsView class in the same assembly as your Bootstrapper?

Hello, sorry for the late answer. I fixed it the following day but I'm don't remember exactly how I did it. I think it was that I added the "foreign" assembly in the IStyletIoCBuilder instance in the "ConfigureIoC" method of the Bootstrapper.


Have a unique id per technology

This repo's readme describes it well
https://github.com/Woorank/wappalyzer-wrapper
Convenience wrapper around wappalyzer library.

Cannonicalizes technologies by adding an id that remains constant between versions.

Example:
const wappalyzerWrapper = require('wappalyzer-wrapper');

await wappalyzerWrapper.analyze({ html, scripts, headers, js });

// [
//   { app: 'Google Analytics',
//     version: 'UA',
//     id: 'google-analytics',
//     categories: [ 'analytics' ] },
//   { app: 'jQuery',
//     version: '',
//     id: 'jquery',
//     categories: [ 'javascript-frameworks' ] }
// ]

Uniquely identifying technologies would be requirement for any production app using this as part of it's stack. Should be pretty easy to add and it would be backward compatible.

The technology name is a unique identifier but it would be good to have a numeric ID or UUID in case the name is updated. The downside is that anyone who adds a technology through a PR will need to generate a unique ID.

Hmmm, now that I think of it, will there ever be a technology name that is not unique? I'm not sure that it would be so we can keep using technology name as a unique identifier.
I think we can bench this for now, see if it comes up, best to keep PR process quick and easy.

Ok, so I just realized that technology names keep changing with releases. We really need a unique identifier.
I have to update my database every time I update wappalyzer, otherwise everything goes out of whack.
If technology names are not constant, they cannot be treated as primary keys.
For example, "Locomotive" became "LocomotiveCMS" and dozens others have changed since 6.0.x. Any ideas how to fix this?

It's rare but names do change sometimes. When that happens I treat it as a brand new technology. You may be able to use the cpe field as the identifier if it's present.


Everitt Cheng - 2/9 Review Ticket

Tangibles

Developed second table for database - contains recipes with columns for (id, name, ingredients, and description)

Slight error with get method

Developed frontend for the database

Github Commit

Frontend Commit

0.2/0.3 - Demonstrated front end and demonstrated backend with databases. Didn't show Java tester method/object creation for website.


Vial Placement Error

There is a vial placed within a desk organizer, which causes clipping. This is in the Kreet Research Lab, which I don't know the formID of.

Will update with new information as it becomes available. This is of the utmost importance.

The pen sitting on the whiteboard right next to the placement of the vial is unobtainable. Just putting this here too because it'll probably be pretty easy to patch once the CK releases.

Looking for anyone else to reproduce.   Any @Starfield-Community-Patch/qa willing to take a look?
(This style issue doesn't always need to be double checked, but just flexing the systems a bit)

Looking for anyone else to reproduce. Any https://github.com/orgs/Starfield-Community-Patch/teams/qa willing to take a look?

I can confirm there is a vial with the RefID 0011304a that's clipping inside a PaperTray02 with RefID 00113018

ESM attached that moves the vial from inside the paper tray to in front of it. Attached:
SFCP_Issue_007.zip


Scope of the client is not Atomic compatible

Hi,
I have a problem using AtomicBoolean or AtomicReference inside a client rx query, it looks like updates the Atomic value inside the query scope but you lose it outside this scope.
Is there any way to store some value inside the rxclient query and use it outside? Something like the next:
AtomicBoolean success = new AtomicBoolean(true);
Single<PgRowSet> pgRowSetSingle = cbaClient.rxPreparedQuery(query, tuple);
pgRowSetSingle.subscribe(result -> {
    }, err -> {
         success.set(false); // Is passing through this code
         log.error("Failure: {}", err.getMessage());
    });

log.info("Success value {}", success.get()); // Here the value is 'true' when should be 'false'

Hi, the code in your subscribtion block is called only when the asynchronous result is completed but the method is quickly returned so your logging does not make sense here.

Understood. Thanks for the info.


ImportError: cannot import name 'update_wrapper'

my project env:
python 3.4.3

Django (1.7.4)
mongoadmin (0.2)
mongodbforms (0.3)
mongoengine (0.10.0)
pymongo (3.1)

when i add mongoadmin  into  settings.py,
INSTALLED_APPS = (
    'mongoadmin',
    'django.contrib.admin',
)

and run: python3 manage.py runserver <IP_ADDRESS>:8000
it happens an error:
Traceback (most recent call last):
  File "manage.py", line 20, in <module>
    execute_from_command_line(sys.argv)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/django/core/management/__init__.py", line 354, in execute
    django.setup()
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/django/__init__.py", line 21, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/django/apps/registry.py", line 85, in populate
    app_config = AppConfig.create(entry)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/django/apps/config.py", line 87, in create
    module = import_module(entry)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/importlib/__init__.py", line 109, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1471, in exec_module
  File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/mongoadmin/__init__.py", line 1, in <module>
    from .options import *
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/mongoadmin/options.py", line 26, in <module>
    from django.utils.functional import update_wrapper
ImportError: cannot import name 'update_wrapper'

just add the module, not use it.
if I delete the module, run OK.
so, i think it is a bug.

i find a similar issue.
https://github.com/kezabelle/django-haystackbrowser/issues/5

here says django 1.6+, not support.
I switch to django 1.5.12, the django-mongoadmin is work now.
but, i think this issue still need to be fix.


GraalVM native image support

Check SDK compiles using GraalVM native image.

[ ] Figure out the required tasks required to enable the SDK to compile using GraalVM native image.
[ ] Add CI test checking GraalVM native image compilation.
[ ] Document how to build sdk-java with GraalVM native image (perhaps related to #22?)

For the time being this is not high priority. Lambda users can use Lambda ColdStart for JVM to get good startup time.


[ZEPPELIN-5753] Improve Docker build

What is this PR for?
This pull requests use profile spark-3.2, limits the memory usage of Maven and and reduces the Maven output.
This pull request also improves the dependency resolution for angular-viewport-watch.
What type of PR is it?
Improvement
What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5753

How should this be tested?

manual

Questions:

Does the licenses files need to update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

LGTM


Error:     0: Generic error: Request error

Hi,
Whenever I run this
subwasm meta wss://rpc.polkadot.io:433

or similar, I get the message
subwasm get --url http://<IP_ADDRESS>:9933
Error:
   0: Generic error: Request error

Location:
   cli/src/main.rs:55

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

I've tried this with local node running:
b56afcaab32c   substrate-contracts-node:v0.29   "/bin/sh -c 'exec /b…"   5 days ago   Up About an hour   <IP_ADDRESS>:9615->9615/tcp, :::9615->9615/tcp, <IP_ADDRESS>:9933->9933/tcp, :::9933->9933/tcp, <IP_ADDRESS>:9944->9944/tcp, :::9944->9944/tcp, <IP_ADDRESS>:30333->30333/tcp, :::30333->30333/tcp   docker-substrate-1

Hello, thanks for the report. It looks like a bug related to some rework with the args.
Here are a few workarounds for now:

Do not pass the url: subwasm meta --chain polkadot is actually simpler :)
Get the runtime locally first: subwasm get wss://polkadot-rpc.dwellir.com -o /tmp/runtime.wasm; subwasm meta /tmp/runtime.wasm

I just tested with wss://rpc.polkadot.io:433 and it would not respond, that could also be an issue with that one RPC.
if you search for RPC urls, you may also checkout [subrpc]*(https://github.com/chevdor/subrpc) to abstract away this URL and run:
TMP=/tmp/runtime.was
URL=$(subrpc ep get polkadot | head -n 1)
subwasm get $URL -o $TMP
subwasm meta $TMP


Integrate extras tests into core

We added the extras module of filters to handle tstat and data population for models late in the build. These are implemented as a switch block for now in changepointmodel.bema.extras since this code was ported from the server.
We should move these into the core package and integrate better with the scoring module we developed. This way if we want extras we can filter on them the same way and get a value reported (at least for tstat).
This is not trivial since each of these tests in model dependent based on the shape of the lines we are fitting.

@equalaction relevant to some of what we were discussing and related to #73

See #73 ... we should look to extend pmodels and then add methods that call into the underlying parameter model

Ideally we want these calculations to land both in the pmodel so that the calculation itself is available via the parent Estimator via  property accessor and ideally hook into the scoring API somehow... to allow us to filtering via threshold... this is a useful idiom.
This will allow us to expose these scores in a cleaner way alongside r2 and cvrmse in our result data. The schema would be extended by adding more score objects and thus not break backwards compatibility.
Then the filter_ module would essentially just iterate over the extras. So we are not really getting rid of filter_ in app module, but just condensing it. However there will probably need to be additional config at runtime in order to tie all the pieces together.
Basic outline:
core

Build new calc modules for the model dependent calculations. Similar pattern to models and bounds
Extend / refactor components of pmodels to add proxy calls for each test calculation ... this should include r2 and cvrme ... These should only report the scores by calling some accessor method for the underlying ParameterModelFunction... ex. est.r2 ----> 0.999 est.tstat ----> 42
Extend the scoring module with different ScoreEvals that return a Score object complete with threshold comparison

Here we would probably need some refactoring...

unittests should not break for pmodels or any other tests currently in 3.0.x.

app

After above... remove extras.
Place any additional boiler in config that is needed to adopt core changes.
Refactor filter_ module extras iterator to simply look through scores and check ok=True (similar to how it is working with current scoring)
Add the scores to the response... as long as the schemas are the same it should drop in since we are conforming to the same interface


Size of windows on vectors/patterns need to be consistent

See the size of window when it comes to patterns:

When it comes to function, composition, or vectors, it shrinked. See here:

the window size should be consistents

the window is fixed, but it leads to different issue.

the textboxes should be consistent and closer to others.
Also when its uneditable, it look smaller than expected.

Basically, it should have the similar look like patterns' size of textbox

confirmed the fix

re-open as it revert the first issue
https://github.com/feagi/brain-visualizer/assets/65916520/848825a8-65dc-4da5-8d13-548fb19dba57

unedited and edited has different size. See below:

fixed the window size


Fix changed attribute computation

true, arguably there's a argument to be made that the diff should have the old values, but I'm not sure.


Editing a map is not centering it in the "initial map"

If you have a table with geometries and you move the world a couple of times to any side, clicking on "add feature" should move the map to the center (according to @javisantana).
This is not happening, so when you add a feature:

It's appearing in the table as a new record, with coordinates out of bounds (+-180)
It's not appearing in the map because the_geom_webmercator is generated as null

SB/5249751

We should probably both:

Wrap the view's coordinates/zoom to an inbounds value (what @iriberri says).
Also wrap the coordinates sent when the geometry is finished.


[Hypersonic]... Doesn't seem to work with new Tasks and Projects rework.

Extension
https://raycast.com/reboot/hypersonic
Description
Error:
TypeError: Cannot read properties of undefined (reading '0')
    at D2 (/Users/ben/.config/raycast/extensions/baa4a90b-4452-4213-b1c0-315edd746652/index.js:62:89956)
    at /Users/ben/.config/raycast/extensions/baa4a90b-4452-4213-b1c0-315edd746652/index.js:62:90671
    at Array.map (<anonymous>)
    at KC (/Users/ben/.config/raycast/extensions/baa4a90b-4452-4213-b1c0-315edd746652/index.js:62:90664)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ZC.initialData (/Users/ben/.config/raycast/extensions/baa4a90b-4452-4213-b1c0-315edd746652/index.js:62:90770)

Steps To Reproduce
Try to load Hypersonic, get greeted with the error.
Current Behaviour
No response
Expected Behaviour
No response

I have the same error, please could you double check this error?

Same for me

I found one workaround but will require access to automation features:

add a new status propriety for your tasks, mirroring the original one (i.e. all the status you have, see on my example below)
link the database using this new custom status
build automations like on the last screenshot: when new status set to Done, set old status to Done

you will have to make one automation per status, you will need to do it twice if you want it to be synced bi-directionally


Feat:Enable the search option for the users

Describe the feature
I can implement the search feature for the users so that users can search for a particular song using the search bar in the homescreen. There are few changes I have to do with the backend url and how the query is handled in the if else statement then i am good to go. Please add the label of gssoc so the contribution can be counted.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

How exactly is it different from the one we are currently using.


Pasting a copied block does not work.

Is there an existing issue for this?

[X] I have searched the existing issues

Version of Corteza
2023.3.x
Current Behavior
Block Pasting is not working.
Expected Behavior
When you paste a block it is not being pasted.
Steps To Reproduce
In Compose, copy a block and try to paste it in page builder.
Environment and versions
No response
Anything else?
No response

Found an issue:
Steps to reproduce:

Create a record list page block
Copy and paste the created page block
Change the title, description, translations of the copied page block
Save the change
Click on view page
Click on page builder
Click on view page
See that the title, description, translations of the copied page block have applied to the original page block

If you do the same thing the other way around - change the title, description, translations of the original page block, the changes will be applied to the copied page block

After the latest changes title and description don't duplicate anymore. There's a new issue with translations. After adding a translation to the original page block -> saving -> view page -> page builder -> the title and description translations of the copied page block + the rest of the page blocks are removed

Translations are no longer duplicated but the issue of title and description being removed after adding a translation in a language different from English is still present. Notice how after adding a translation to Hebrew, for example, this removes the title and description of all other page blocks.

An improvement/suggestion: after clicking on the copy page block button, unfocus the button and focus the whole page so you can directly paste the copied page block. Currently, I have to click somewhere else to unfocus the copy button which isn't that good, for me at least. If you are in the page builder and don't have any empty space between the page blocks it can be a bit awkward to "find" where to click in order to unfocus the copy button.

Tested this and can confirm that it's working as expected

Changelog Documentation
Fixed
What was Fixed?
Issues with the copy paste feature
Issues with focusing for pasting a block
Issues with translations concerning duplicated blocks
How was it fixed?
Resolved an issue where pasting was not working at all. Copied blocks can now be pasted.
Improved pasting and copying so that users don't have to click around to focus onto where they should paste a copied block
Duplicated blocks no longer have their translations affected by one another

Added CL.


A&R -> Designs for Null/Missing Values

Description:
Design for #351
Idea: pair dev/designer to figure out what this should look like
Acceptance Criteria:

[ ] wireframe is updated in figma
[ ] wireframe has been reviewed by team/PO
[ ] wireframe link is added to the implementation ticket #351

Dependencies

Blocked by
Blocking

Relevant documentation as reference
Definition of Ready

[ ] Acceptance criteria are included
[ ] Wireframes are included (if applicable)
[ ] Design / Solution is accepted by Product Owner (if applicable)
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] UI meets accessibility requirements
[ ] Unit tests are written
[ ] Work is traceable in GitHub
[ ] PR linked to ticket number
[ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

[ ] Code is peer reviewed and has passed CI/CD tests

QA:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Code is potentially shippable to the production environment
[ ] Functional features have been tested and passed by QA
[ ] UI components tested by designer
[ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

PO Review:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Reviewed and approved by Product Owner

Notes:

@pavelcreates or @meredithom (whoever wants to provide their stamp of approval for this 😅 )
Looks like we're going to print out a somewhat simple report for these missing values, similar to the Standard and Variance report, but with a Date Select as well as Park select - so not much in the way of design needs here. This is what I was using for local testing, but I'm open if there are any tweaks you'd want to add to this page design.
Thanks!

Designs look good - moving to done. FYI @davidclaveau thanks for your patience!

@meyerdarcie thanks for the approval!
I made a slight audible and changed it again at the last minute 😅
This is to match what we'll be adding in #254 and the Figma designs. Made some sense to add a little toggle for "Export all"
A&R:

Figma:

@davidclaveau - changes look good!


Localization support?

Hi, hope to support localization for other language. Translations can be done by community.

Don't think we will support localization any time in the near future. If you want to help the project, you can join our discord. https://discord.gg/CXUbQXyfUs


Demo: Fix text-to-3d

Text-to-3D seems to have been broken. We should fix it. Perhaps gradio client version needs to be upgraded.

Fixed.
Hugging face space seems to be deactivate if its idle time is too long. We may need to fire it by accessing first. Retrying the request may resolve the issue? It is another issue from this issue tho.


Fails to parse exponents with a decimal component.

I was debugging some issues I was having and traced the issue back to using 1.2e3 in an SVG number component. The SVG Number data type indicates that it should support numbers of this kind.
For example, this file should parse correctly, however it fails to parse the translate transformation, and it also fails to parse the path definition beyond the first invalid exponent:
<svg>
  <g transform="translate(11,2.5e-4)">
    <path
       d="m 1,2.2e-4 10,10 -10,10"
    />
  </g>
</svg>

Ideally this should be equivalent to
<svg>
  <g transform="translate(11,0.00025)">
    <path
       d="m 1,0.00022 10,10 -10,10"
    />
  </g>
</svg>

Yes. Looks like I broke it few commits ago.


tuple issue

Hi rt_Utils authors
Thanks for a great tool !
I had it working fine but made some updates and now I get som format issues ( tuples). I am adding the error message here - hope you can help :)
Skipping empty mask layer
Skipping empty mask layer
Skipping empty mask layer
Skipping empty mask layer
Skipping empty mask layer
Skipping empty mask layer
Traceback (most recent call last):
File "", line 1, in
rtstruct.add_roi(mask=mask_3d_bool, color=json.loads(strct_color1[strnum-1]), name=strct_names1[strnum-1])
File "C:\Users\jeskal\Anaconda3\lib\site-packages\rt_utils\rtstruct.py", line 59, in add_roi
self.ds.ROIContourSequence.append(ds_helper.create_roi_contour(roi_data, self.series_data))
File "C:\Users\jeskal\Anaconda3\lib\site-packages\rt_utils\ds_helper.py", line 144, in create_roi_contour
roi_contour.ContourSequence = create_contour_sequence(roi_data, series_data)
File "C:\Users\jeskal\Anaconda3\lib\site-packages\rt_utils\ds_helper.py", line 157, in create_contour_sequence
contours_coords = get_contours_coords(roi_data, series_data)
File "C:\Users\jeskal\Anaconda3\lib\site-packages\rt_utils\image_helper.py", line 64, in get_contours_coords
contours, _ = find_mask_contours(mask_slice, roi_data.approximate_contours)
File "C:\Users\jeskal\Anaconda3\lib\site-packages\rt_utils\image_helper.py", line 87, in find_mask_contours
contours[i] = [[pos[0][0], pos[0][1]] for pos in contour]
TypeError: 'tuple' object does not support item assignment

What updates did you make exactly? If you can submit the changes in a pull request I'd be happy to look it over and hopefully get it into the library :)

So I encountered the same issue and it seems to stem from the opencv-python version
In opencv-python==<IP_ADDRESS> there is no issue, however in v <IP_ADDRESS> you encounter this "tuple issue".
I haven't dug into it beyond this since I can freely change versions without drawback, but figured this might help narrow down the issue.

Thanks @Renal-Of-Loon, perhaps opencv changed datatypes in a more recent version. #35 has the same fix you mentioned @Jkallehauge, we will get that in by Friday this week. Thanks for bring it up!


Surface option for divisor for Std calcs

We use PROC MEANS/SUMMARY to calculate standard deviation.  PROC MEANS/SUMMARY has an option VARDEF= to control the divisor.
http://support.sas.com/documentation/cdl/en/proc/68954/HTML/default/viewer.htm#n1qnc9bddfvhzqn105kqitnf29cp.htm
To all macros that calculate standard deviation, or call macros that do, add VARDEF= as a parameter.  Valid values are {N,DF}.  DF should be set to the default.
Add VARDEF=&VARDEF to PROC MEANS/SUMMARY calls.

Done by #75


no module named app alembic migraiton issue

File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/Users/gsubramanian/dev/workbook-api/app/alembic/env.py", line 9, in
from app.config import settings
ModuleNotFoundError: No module named 'app'

Not sure exactly what you did to get to this point but in response to your issue I've made some corrections to make it easier to get this repo up and running. Like I say in the README, this repo is designed to be a simplified example, rather than a working prototype but fair enough to raise this.
Once you pull the latest commit, you should be able to start the project by simply invoking docker compose up -d. If you want to make a change to a model then create a migration file, I recommend doing so using the existing command i.e. backend/scripts/autogenerate_migrations.sh "your migration message". You should be able to run this migration using backend/scripts/run_migrations.sh. Let me know if this resolves your issue.

i mean without docker compose when i run alembic revison command it is not able to resolve the module,later i found and added sys.path to make it work. thanks anyway for the work, it is useful.


Array is misinterpreted as Array

If one reverts the order of execution of test_getitem_i8 --> test_getitem_bool  to test_getitem_bool --> test_getitem_int8, then i8 arrays starts to be interpreted as boolean arrays and any value different than 0 is interpreted as 1, resulting in a test failure.
diff to reproduce:
https://gist.github.com/guilhermeleobas/0747df260e2e65ba951efc92e6debf8d
It seems that this failure was introduced in https://github.com/xnd-project/rbc/pull/119

It is the same as #140, so closing as duplicate.


Make leaflet a peer dependency / webpack external

This PR is to address #98.
Example:

Conflicts before fix
Conflicts resolved after refactor (using a webpack build @a2a6acd)

I had started refactoring to a stricter typescript and unit testing over the weekend, and just committed it.  However, just before doing so, I implemented your recommendations, TY!  I'll close this PR, but awesome recommendation that I tried my best to accredit to you.

No worries, thanks for folding this in @robertleeplummerjr  👍
Just a heads up tho - in current master the leaflet dependency is in both dependencies and peerDependencies

Fixed and pushed.

Great - looking forward to npm release of v3.2.0


Include properties in array API docs

I went looking for the blocks docs this morning and realized that there were some missing items in the array API docs. I think mostly the missing bits were the properties.

It'd be nice to improve these docstrings while I'm at it.

Let's say follow up. This is an improvement as is.


Using local images

Hi.
Your usage example and the implementation of the NavigationDrawerLayout file are using an implementation of the ImageBackground component with images from network (not local).
I need to load the images locally for testing purposes, How can I do it?
The implementation of the NavigationDrawerLayout.js is as follow:
 <ImageBackground
     source={{
          uri: imageBackground,
     }}
     ...>
...
 </ImageBackground>

Can you change the implementation of this in order to use local images? Or
May I do a Pull Request to improve this code?

Hi @yulioaj290 ,
I have uploaded version 0.0.7 as requested.
In order to use local images, you have to do this:
<NavigationDrawerLayout
        ...
        imageBackground={require('../assets/imageBackground.png')}
        ...

Let me know if there are any problems or if it doesn't work properly.

Hi @yulioaj290 ,
I have uploaded version 0.0.7 as requested.
In order to use local images, you have to do this:
<NavigationDrawerLayout
        ...
        imageBackground={require('../assets/imageBackground.png')}
        ...

Let me know if there are any problems or if it doesn't work properly.
I would like to ask you to respect the documentation I wrote with commitment to the issues.
You can do all the pr you want.

Hi @gaetanozappi
Thank you for the quick response and for uploading the new version. It works great!
I apologize to not respect the issues documentation. :(
PS: I write another issue related to this on react-native-avatar-social#1


impl IntoStream for SpannedIterStream

allows SpannedIterStreams to be used with Parser::parse()

I'm doing a pretty massive refactor of the whole crate in #5 that would invalidate the need for this PR. Thanks for opening it though!

no worries, thanks for the great library!

I've just published 0.5.0-alpha which completely overhauls the crate, adding support for LL(k) parsers, more combinator options, a more powerful error type, much better error recovery, etc. I recommend giving it a go!

Whoa, didn't expect this to be released this quickly -- Parser::recover_with is a really nice idea and it radically simplifies my parser (will upload to github when it becomes a bit more substantial). Thanks again!

Awesome! I look forward to seeing it when you do!


Update get Nearset pq entries

Update the pq entries so the margin and nodeOffset are accessable, and not only comparable.
Additionally added searchK funcitonality to getNearestPqEntries.

👍


Reporters warning

From @waldekmastykarz

An idea for the proxy toolkit: show a warning when it sees that a reporter isn't at the end of the plugins array (basically no other plugins should come after reporters)

The toolkit should highlight any plugin that comes after an active reporter plugin with warning.


Update time to 0.2.x

Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Updates the time crate to 0.2, making Rust 1.40.0 the minimum supported version

From the failing tests it looks like CI isn't running on Rust 1.40.0

I've restarted the build a few times since it should run on stable which is 1.40 right now, but it returns the same errors. 🤔 Can't reproduce it locally, works as expected.
I may introduce some changes to our Pipelines config to output the version of Rust being used for further diagnostics.

https://github.com/rusoto/rusoto/pull/1648 shows curl https://sh.rustup.rs -sSf | sh -s -- -y --default-toolchain stable installs Rust 1.39.0 .
Not sure if that's a bug in rustup or if Rust 1.39.0 is preinstalled on some images and is being used instead of what rustup installed.

I think the older version of Rust is preinstalled on the Linux images we use, I've updated https://github.com/rusoto/rusoto/pull/1648 to install Rust stable on the Linux stable jobs, looks to work. 👍
Once that PR is merged this one can be rebased and should pick up the changes. 😄


Implement Bonjour discovery.

Unable to find a feature-complete bonjour implementation that doesn't suffer race conditions or other fatal issues, I had started work on building https://github.com/dogmatiq/dissolve as a prerequisite for this issue. This is still very low on the priority list.


Updated peerDependencies to support React 18

Updated peerDependencies to support React 18

@dgreene1 @mellis481 @yhy-1 could you please review my PR and run the workflows (UIEN-2779)? Thanks!

@Ke1sy Why aren't you updating the react dependency version in this effort?

@Ke1sy Please check the tests

@Ke1sy Please check the tests

fixed it


Extract more references (from other generators)

This makes it possible to extract all references from the document listed at https://www.w3.org/standards/techs/js#w3c_all with the exception of serviceworkers (but works with editors draft) and selection-api (but that's because it wrongly classifies its references as purely informative).

I guess this addresses #6

I made some tweaks to improve readability a bit (from some definition readability, that is ;)). I'll merge now and create a "util" module.

Are there specs that both contain an informative list and flag individual references as "non-normative"?

how would I know? that's what defensive programming is for >:)

OK, well, your defensive code would have failed too ;) (you forced that type to "normative" for informative references extraction as well). I'll add something back.

nah, I think you can simply ignore it, I'm just being annoying :)

Too late :)


Templating changes...

#1094 #1091 #1057
@olefredrik @colin-marshall I realized when I went through the above issues that you needed to do them all at once. Also, they affected a lot of little things across many files. Hopefully, this PR will be helpful to get the ball rolling on changing some of the templating discussed (with some review and discussion.)

The wrapper should be the same across the theme with the main element.
The innards should mainly be controlled by content and content-page .

Tested ok 👍


Remove grafana watcher from Grafana Helm chart

Since Grafana v5 is able to watch local directories for new dashboards and datasources, grafana-watcher has been made redundant.
Following the cleanup example in #1390, this PR removes the grafana-watcher sidecar from the Grafana Helm chart.
Tested with:

K8s v1.11.2
Helm v2.11.0

Sorry for the inconvenience, but the prometheus-operator and kube-prometheus helm charts are currently being migrated to the upstream stable helm charts. Because of this we are currently not accepting any pull requests. We apologize for the inconvenience, but this is necessary for the migration to actually happen. We announced this here: https://github.com/coreos/prometheus-operator/tree/master/helm#warning
You can view the progress and help here and here.
Thank you for your understanding! :slightly_smiling_face:


Don't run all demos when building docs

When building docs we need to run demos only to save the figures in them, right? If so, we could significantly cut down the time to build docs by not running demos without figures in them.

Agreed!


Zilliz integration and Milvus bugfixes

Included the Zilliz vector database, Milvus bugfixes, and more notebooks.
Also this merge aims to clear the notebook outputs of the shared notebook. Every pull is deleting other peoples outputs and including their own. I believe the best route is to just not have outputs in the notebook instead of everyone overwriting each others work.

It might be worth having a standard output near the end that shows exactly what should be returned. The different sections just show how to get that input using each vector store.

Is there anything that needs to be changed to get this merged? @ted-at-openai

Merged! Thanks for your patience. I think I'm going to split up the single notebook into one for each vector DB, to help keep things manageable. Hopefully can get that done tomorrow.


Add action to push screenshots to conda store

Fixes https://github.com/conda-incubator/conda-store/issues/570

Description

This workflow collects screenshots which have stored as artifacts in test.yml and opens a PR on conda-store to update the docs.
This pull request:

adds gh action to push screenshots to conda-store

Pull request checklist

[x] Did you test this change locally?
[ ] Did you update the documentation (if required)?
[ ] Did you add/update relevant tests for this change (if required)?

Additional information

We originally discussed triggering this from a comment on a PR. I discovered that the only Action trigger, issue_comment, would trigger this to run for every comment on every issue. I feel like that is a lot of wasted compute even if the first thing it did was check to see if its a PR and shut it down. For this reason, I've decided to trigger on label instead.
# There are two ways to trigger this workflow:
# 1. Trigger by adding the `update_screenshots` label.
#    The workflow will run immediately after you add the label. It is
#    also expecting artifacts which have been generated in test.yml.
#    Therefore, this cannot be triggered until test.yml is complete.
# 2. Trigger by workflow dispatch.
#    Specify the PR number with the artifacts you'd like to use.
#    Again, the test.yml workflow must be complete.
#
# If a PR has already been opened on the conda-store repo from this
# action, a rerun of this action will attempt to update the PR, not
# create a new one.

I looked at triggering on the completion of test.yml, but that would trigger the workflow off of main and we'd be forced to use the "latest" generated artifacts, rather than PR-specific.
This will require a PAT to open up the PR on the conda-store side. It is currently looking for secrets.PAT.

I've tested this approach on dummy repos but this will still take me some tuning to get everything right in place.
TODO:

get secrets sorted out
add more screenshots to playwright to cover what's already in conda-store

make sure the words of the doc aren't specific to the old screenshot (i.e. has the doc been updated to the new UI)

sort out where these need to land (in the new docs folder or overwrite the old screenshots?)

@pavithraes it looks like a lot of the images in /docusaurus-docs/conda-store-ui/images have red boxes are the area of interest. We will lose those if we let playwright generate the images. Is that ok, or should we avoid updating those images with playwright?

please update screenshots

Both the workflow dispatch trigger and the issue comment trigger will only work once the workflow is committed to main. I'm leaving the label trigger in for now so that I have a way to call it.

@kcpevey Thanks for working on this!

it looks like a lot of the images in /docusaurus-docs/conda-store-ui/images have red boxes around the area of interest. We will lose those if we let playwright generate the images. Is that ok, or should we avoid updating those images with playwright?

Yes, it's OK to override the images with red highlights. I think keeping the screenshots up-to-date has a greater impact, and we can always make things clearer in the text if needed. :)

Adding the mouse indicator and hover is not available straight out the box with playwright. So this image, for example:

Will not be possible. This may be possible with an extra extension such as mouse-helper (mentioned here) but we'd need to work out if that's possible in python playwright.
Another option would be to run playwright in the Trace Viewer which has snapshots, one of which would include a red circle where the mouse click happened. This would take snapshots before, during, and after each interaction with the page. So it would give us some helpful functionality, but it feels like overkill.
For this work, I'm going to leave off any mouse visualization or click indicators.

There is a duplicate image in the current docs. I'm going to continue on with version-select.png and recommend that versions-view.png be removed.

The pip section of the yaml editor now populates by default. So the two images yaml-editor.png and pip-section.png are now going to be the same image unless I explicitly remove the pip section for yaml-editor.png. I'm not sure what the best choice would be here. Maybe depends on what the docs using these files look like (I haven't looked them up yet)?

I recommend leaving the label trigger for pushing the images in place and removing in a subsequent PR so that we can be sure that the other triggers work once they are in main.

Finally, this is ready for review!
If you check the PR on the docs side, you can see the comparison of the new images. Because we no longer have the "red boxes" to direct your attention to a portion of the screen, I decided to crop the images to only include the region of interest. If you check the netlify docs, the image sizes are now inappropriate. I recommend that this can be merged and that the auto generated PR on the other side be worked on to resize the images in the docs.

If you check the https://github.com/conda-incubator/conda-store/pull/731, you can see the comparison of the new images. Because we no longer have the "red boxes" to direct your attention to a portion of the screen, I decided to crop the images to only include the region of interest.

I actually prefer this approach -> only show the relevant UI sections vs the whole UI so this is a +1 from me

This is ready to merge (failing CI is outside of this PR)

Ok, this thing is back to passing CI 🎉 Now I need to double check the images.

I suspect this is failing due to a bad token. We were originally using @jaimergp 's PAT. Can you please regenerate and add it as a secret named CONDA_STORE_SYNC in this repo? It needs to be able to open a PR on https://github.com/conda-incubator/conda-store

I suspect this is failing due to a bad token. We were originally using @jaimergp 's PAT.

Quick question about this. Is this going to create any maintenance issues in the future? Is this the most future-proof approach we can take?

I have a question about this. Is this going to create any maintenance issues in the future? Is this the most future-proof approach we can take?

Because we are opening a PR on another repo, we need credentials. In other projects, we have github service accounts where we share credentials (so basically internal "bot" users). Since this would have to be a user in the conda-incubator org, we didn't feel that was appropriate and decided to go with personal credentials in the future. Happy to explore any other ideas though!

I looked through the built docs on the other PR. I need to make a few minor tweaks to some of the image clipping.

Unfortunately I had the images looking great on my local setup (which is running the same conda-store version as CI) but the images I generated locally differ from CI. The images that require clipping are "off" by an unacceptable amount.

Sorry to possibly rock the boat here, but I am starting to wonder if we should abandon this PR.
Similar to CI, I also had iffy results running this locally. For example, the following screenshot is not ready to be published straight to the docs:

It's to be expected that there will be differences between the screenshots taken on CI and those taken locally. This came up when I started working on JupyterLab, which has a number of snapshot tests, which compares saved screenshots taken on a previous run and committed to the repo with screenshots taken on the current run. If you did anything that changed the UI, you couldn't update the saved and committed screenshots from your local computer; you had to upload your changes in a PR and then ask a GitHub robot to attach updated screenshots to your PR.
I don't want us to fall into a sunk cost fallacy here. We have spent a lot of time to get this PR close to the finish line, but considering the work left to do and the work it may demand in the future, have we already tipped past the value this PR potentially provides?

I am leaning towards the same view as @gabalafou, this PR has lagged a lot more than I would have liked both in time and effort, and I am worried that it will add a non-trivial amount of maintenance and upkeep work.

Apologies I couldn't get this across the finish line. I just didn't have enough consistent hours and there was too much breakage every time I returned. I suspect this means that maintenance burden would be significant as well (having the change the crop extents slightly all the time). Closing seems reasonable.


Implement pub-sub for storage in memory

This PR Implements a pub-sub mechanism for in memory storage STORAGE_DSN=memory://localhost:6379. This way while I change the proxy definition via API I instantly see the changes and no need for redeploying the server

👍

Can we add integration tests for this? E.g. run the third instance with memory storage just to test this piece of functionnality.

@vgarvardt yes makes total sense to test this, added on our backlog 👍

👍


[Bug]: call ChatGLM failed

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
d0a1ffe6e21e81f64b1c9199123be6936dbc4a01
Other environment information
No response
Actual behavior
Configure the LLM as ChatGLM and chat, got
ERROR: Completions.create() got an unexpected keyword argument 'presence_penalty'

Expected behavior
No response
Steps to reproduce
Deployed local docker environment.
Create a knowledge base, uploading some docs.
Config ChatGLM as LLM and config the ApiKey.
Then create an assistant with ChatGLM, chat with it, the error will happen.

Additional information
No response

I met this problem when I run ChatGLM . You can solve this by closing the Presence penalty option.

Pull the latest source code and images, try it again.
The website has  already updated.


Fix DateTimeParseException in FHIR import

fixes #18

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Adrian Wilkins seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @awilkins, many thanks for the contribution!
I'm looking at the date format for FHIR (https://build.fhir.org/datatypes.html#date) and wondering if there might be an issue if only the year or year and month are provided?
I think it may be possible to do this with the OffsetDateTime.parse(date, <format>) where  is something like YYYY[-MM[-DD]], which would avoid the string manipulation.

Had a crack with various permutations of DateTimeFormatter

Found it very hard to construct a custom format string that matches ISO8601

The X token is the closest for zone but includes whitespace and a colon
The code that actually builds the ISO formats in DateTimeFormatter uses inner classes of DateTimeFormatterBuilder

.ISO_LOCAL_DATE doesn't work because OffsetDateTime.parse() demands a zone offset
.ISO_OFFSET_DATE doesn't work because OffsetDateTime.parse() needs the InstantSeconds field which this doesn't set
.ISO_OFFSET_DATE_TIME (the default) which does set zone and InstantSeconds requires the time and zone string

Even if we had a parser with optional bits missing, I think that OffsetDateTime is going to want them to not be missing.
Changing the type of dateFinalised in the VersionAware trait would probably be quite disruptive, so I'm content with it in it's current state.

OK, thanks for that, yes I agree changing the format in VersionAware would have a big impact. I'll merge this PR.

Any chance of a 5.2.1 release? Getting this fix into an instance is mildly fiddly without it.

@awilkins We've been building up to our 2023.1 release of all core, ui, and major plugins, and we'll hopefully be doing that in the next week or so


chore(client): replace detect-runtime dep with std-env

closes https://github.com/prisma/team-orm/issues/626

See https://prisma-company.slack.com/archives/C04TW4A2H8C/p1705329136188049
Blocked because it adds 3KB to the runtime, because esbuild does not tree shake it for some reason

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


Ore crafting allows infinite ores.

You can craft ores and then mine them with fortune and duplicate them, then craft more and on and on.

I would suggest at least making it so it needs 4 of that gem/metal to craft it


Can't Disable Temperature/Humidity from Leak Sensors

Describe The Bug:
Despite making sure that the setting is unchecked, my three leak sensors continue to show both humidity and temperature values through Homebridge and the Home app.
To Reproduce:

Set up plugin.
Ensure that "Show water sensor temperature and humidity in HomeKit" is unchecked.
See these values continuing to show in the Home app.

Expected behavior:

Logs:
[23/07/2024, 13:49:54] [Flo-by-Moen] Initializing Flo-by-Moen platform...
[23/07/2024, 13:49:54] [Flo-by-Moen] Starting communication with Flo portal
[23/07/2024, 13:49:54] [Flo-by-Moen] Flo Info: Using local cache Flo token.
[23/07/2024, 13:49:54] [Flo-by-Moen] Flo Info: Token will refresh in 4 hour(s) and 15 min(s).
[23/07/2024, 13:49:54] [Flo-by-Moen] Initializing Flo devices...
[23/07/2024, 13:49:56] [Flo-by-Moen] Flo device updates complete, background polling process started.
Device will be polled each 1 min(s) 30 second(s).
[23/07/2024, 14:00:04] [Flo-by-Moen] Initializing Flo-by-Moen platform...
[23/07/2024, 14:00:04] [Flo-by-Moen] Starting communication with Flo portal
[23/07/2024, 14:00:04] [Flo-by-Moen] Flo Info: Local caching of Flo token is disabled.
[23/07/2024, 14:00:04] [Flo-by-Moen] Flo Status: Refreshing Token...
[23/07/2024, 14:00:05] [Flo-by-Moen] Flo Info: Token will refresh in 12 hour(s) and 0 mins(s).
[23/07/2024, 14:00:05] [Flo-by-Moen] Initializing Flo devices...
[23/07/2024, 14:00:08] [Flo-by-Moen] Flo device updates complete, background polling process started.
Device will be polled each 1 min(s) 30 second(s).
[23/07/2024, 14:01:06] [Flo-by-Moen] Initializing Flo-by-Moen platform...
[23/07/2024, 14:01:06] [Flo-by-Moen] Starting communication with Flo portal
[23/07/2024, 14:01:07] [Flo-by-Moen] Flo Info: Using local cache Flo token.
[23/07/2024, 14:01:07] [Flo-by-Moen] Flo Info: Token will refresh in 4 hour(s) and 3 min(s).
[23/07/2024, 14:01:07] [Flo-by-Moen] Initializing Flo devices...
[23/07/2024, 14:01:09] [Flo-by-Moen] Flo device updates complete, background polling process started.
Device will be polled each 1 min(s) 30 second(s).

Plugin Config:
    "name": "Flo-by-Moen",
    "auth": {
        "username": "XXXX",
        "password": "XXXX"
    },
    "disableCache": false,
    "showTemperatureAndHumidity": false,
    "enableValveControl": false,
    "showHealthTestSwitch": false,
    "showAuxSwitch": false,
    "treatWarningAsCritical": false,
    "surpressWaterNotification": false,
    "deviceRefresh": 90,
    "offlineTimeLimit": 4,
    "sleepRevertMinutes": 120,
    "retryErrorDisplay": 3,
    "showFloTemperature": false,
    "showGPMPSIasLight": false,
    "platform": "Flo-by-Moen"

Screenshots:

Environment:

Plugin Version: 1.0.11
Homebridge Version:  1.8.3
Node.js Version:  18.17.1
NPM Version:  9.6.7
Operating System:  4.56.4

Corrected in repo, will be part of the next release.

Corrected in version 1.0.12

This still seems to be an issue in  v1.0.18. @haywirecoder can you re-open?

Hi unfortunately, I can't reproduce what your are seeing. Just tested a few times, if "showTemperatureAndHumidity": false is set the Temperature/Humidity value are no longer exposed in homebridge.

@haywirecoder maybe I am misunderstanding what this configuration is for? I have a temperature sensor that shows up along with the Flo in Homekit. It is always around 80ish degrees. What is this exactly? Is it the temperature of the water or the garage area? Should showTemperatureAndHumidity toggle this on and off? Mine is set to false and it still shows up.

@litex2x, yes that parameter is only for the leak sensors. The temperature that is displayed is the water temperature in the Flo valve. However,  Flo (moen) deprecated this attributed awhile ago, so it most likely inaccurate, so I will simply removed it in the next version.

@haywirecoder Thanks I will keep an eye out for the new version. Sorry I did not realize this config was only for the leak sensor.


.io

?

I have litterally no idea how this ended up here. Im just as confused as you are.  Sorry for that.

hahahah no problem


Remove 0.17 deprecations

Since #2980 starts a breaking change for 0.19, let's also clean up all 0.17's deprecations.
I've removed Python::acquire_gil in its own commit, as that was a reasonably chunky removal.

I was thinking about keeping acquire_gil around for a while longer, because I think a lot of people still use it, and maybe use it in ways that aren't trivial to rewrite using with_gil. That said I also don't like having both around, so +1 to this.

I think this would be worth it considering how much tricky/unsafe code can be removed or get reduced visibility due to this, especially the drop order checking which could inject unexpected and intermittent panics into downstream code.

@davidhewitt I would like to help here if I can as I would very much like to see this merged for the reduction in complexity it allows. Would you mind if I tried to rebase this and add another commit for the migration guide entry?

Please do, at the moment when I get a scrap of time I'm trying to finish off #3029

I added an entry to the migration guide but admittedly the example is quite artificial. Please have a look and let me know if this is sufficient for our purposes.

bors r=adamreichold,davidhewitt


Fix summary segment overflow

Alaska Airlines Pull Request
Fixes #32
Summary:
Fixes the flightline overflowing when showing a summary segment. This was because the :first-child selector used to shorten the first segment in a flightline did not apply to the summary segment, which was the second child (after the slot).
Also remove references to the Sass demo build, which caused npm run dev to fail.
Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Verified fix

:tada: This PR is included in version 1.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


About the Mean and Std calculation.

Hey, I'm curious in why you use the average number rather than the original variance when u calculate the variance of data in following code.  Is there any experiment you made about it?
Std[0:1] = Std[0:1].mean() / 1.0
Std[1:3] = Std[1:3].mean() / 1.0
Std[3:4] = Std[3:4].mean() / 1.0
Std[4: 4+(joints_num - 1) * 3] = Std[4: 4+(joints_num - 1) * 3].mean() / 1.0
Std[4+(joints_num - 1) * 3: 4+(joints_num - 1) * 9] = Std[4+(joints_num - 1) * 3: 4+(joints_num - 1) * 9].mean() / 1.0
Std[4+(joints_num - 1) * 9: 4+(joints_num - 1) * 9 + joints_num*3] = Std[4+(joints_num - 1) * 9: 4+(joints_num - 1) * 9 + joints_num*3].mean() / 1.0
Std[4 + (joints_num - 1) * 9 + joints_num * 3: ] = Std[4 + (joints_num - 1) * 9 + joints_num * 3: ].mean() / 1.0

Hi, the main motivation is that every group of features indicating the same
type of feature (rotation, position), therefore it makes sense to average
their std and mean. Actually I got this implementation from several
SigGraph papers.
Q137589933 @.***> 于2023年7月8日周六 05:28写道：

Hey, I'm curious in why you use the average number rather than the
original variance when u calculate the variance of data in following code.
Is there any experiment you made about it?
Std[0:1] = Std[0:1].mean() / 1.0
Std[1:3] = Std[1:3].mean() / 1.0
Std[3:4] = Std[3:4].mean() / 1.0
Std[4: 4+(joints_num - 1) * 3] = Std[4: 4+(joints_num - 1) * 3].mean() / 1.0
Std[4+(joints_num - 1) * 3: 4+(joints_num - 1) * 9] = Std[4+(joints_num - 1) * 3: 4+(joints_num - 1) * 9].mean() / 1.0
Std[4+(joints_num - 1) * 9: 4+(joints_num - 1) * 9 + joints_num3] = Std[4+(joints_num - 1) * 9: 4+(joints_num - 1) * 9 + joints_num3].mean() / 1.0
Std[4 + (joints_num - 1) * 9 + joints_num * 3: ] = Std[4 + (joints_num - 1) * 9 + joints_num * 3: ].mean() / 1.0
—
Reply to this email directly, view it on GitHub
https://github.com/EricGuo5513/HumanML3D/issues/73, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKRYNB2BGPPBBQXCMG4W5J3XPE75LANCNFSM6AAAAAA2CZJY3M
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, the main motivation is that every group of features indicating the same type of feature (rotation, position), therefore it makes sense to average their std and mean. Actually I got this implementation from several SigGraph papers. Q137589933 @.> 于2023年7月8日周六 05:28写道：
…
Hey, I'm curious in why you use the average number rather than the original variance when u calculate the variance of data in following code. Is there any experiment you made about it? Std[0:1] = Std[0:1].mean() / 1.0 Std[1:3] = Std[1:3].mean() / 1.0 Std[3:4] = Std[3:4].mean() / 1.0 Std[4: 4+(joints_num - 1) * 3] = Std[4: 4+(joints_num - 1) * 3].mean() / 1.0 Std[4+(joints_num - 1) * 3: 4+(joints_num - 1) * 9] = Std[4+(joints_num - 1) * 3: 4+(joints_num - 1) * 9].mean() / 1.0 Std[4+(joints_num - 1) * 9: 4+(joints_num - 1) * 9 + joints_num3] = Std[4+(joints_num - 1) * 9: 4+(joints_num - 1) * 9 + joints_num3].mean() / 1.0 Std[4 + (joints_num - 1) * 9 + joints_num * 3: ] = Std[4 + (joints_num - 1) * 9 + joints_num * 3: ].mean() / 1.0 — Reply to this email directly, view it on GitHub <#73>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKRYNB2BGPPBBQXCMG4W5J3XPE75LANCNFSM6AAAAAA2CZJY3M . You are receiving this because you are subscribed to this thread.Message ID: @.**>

Thanks for your reply, it repels my doubts!


Support RabbitTemplate.invoke using publisher connection.

I configure the RabbitTemplate use publisher connection.
RabbitTemplate.setUsePublisherConnection(true);

When I using RabbitTemplate.convertAndSend, the publisher connection is used. It works.
But when I using invoke like below, the publisher connection is not use.
rabbitTemplate.invoke(operations -> {
    operations.convertAndSend("exchange", "queue", message);
    return operations.waitForConfirms(1000);
});

rabbitTemplate.invoke always not use the publisher connection, I think rabbitTemplate should provide a overload method invoke(OperationsCallback action, boolean usePublisherConnection) to indicate use the publisher connection.

Thanks for reporting; it's a bug.

Thanks for reporting; it's a bug.

I want to know if this bug fixed. What's the behavior of below code.
rabbitTemplate.invoke(operations -> {
    operations.convertAndSend("exchange", "queue", message);
    return operations.waitForConfirms(1000);
});

Is invoke method always use publisher connection if RabbitTemplate's usePublisherConnection is true? @garyrussell

OK, thanks.

As a workaround; you can set that flag to false and inject the publisher factory directly.
RabbitTempalte template = new RabbitTemplate(cachingConnectionFactory.getPublisherConnectionFactory());


Support admin config flexibility when finding cluster id for observability

Spring Kafka 3.0.0
As seen in the following Spring Cloud Stream issue, when activating the binder observability the KafkaAdmin client doesn't use the spring.cloud.stream properties and requires the configuration of the ones in spring.kafka

Closing this; the functionality is already supported by KafkaAdminsetBootstrapServersSupplier().

See https://github.com/spring-cloud/spring-cloud-stream/issues/2597

Correction - this is about configuring the admin used by the template when observability is enabled.


Failed to resolve module specifier 'controllers/nested_form_controller'

Hi, I am using nested_form but I have a error.
I am using rails7 and importmap (pin)
I have this error on browser console
Error
Failed to autoload controller: nested-form TypeError: Failed to resolve module specifier 'controllers/nested_form_controller'
Form is working but I want to clear this error.
Can you help me?
Importmap.rb
pin "stimulus-rails-nested-form", to<EMAIL_ADDRESS>application.js
import NestedForm from 'stimulus-rails-nested-form'
application.register('nested-form', NestedForm)

I have the same error in my console:
importmap.rb
pin "stimulus-rails-nested-form", to<EMAIL_ADDRESS>
and a controllers/nested_form_controller.js
import { Application } from '@hotwired/stimulus'
import NestedForm from 'stimulus-rails-nested-form'
const application = Application.start()
application.register('nested-form', NestedForm)

it works here also, but I would like to get rid of the error.

Hey, reopen in the main monorepo https://github.com/stimulus-components/stimulus-components if needed! 👍


EntitySwitch render children when entity is not found

Hey, I just made a Pull Request!
This PR closes #19418 by rendering the children in case an entity is not found.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Oh sorry - needs a changeset too


Graphql query for device_types fails after upgrade to 1.2.1

Environment

Python version: 3.8.10
Nautobot version: 1.2.1

Steps to Reproduce

In the graphql query browser insert the following query:

query {
device_types {
id
model
}
}

Run the query
With DEBUG enabled the following result is shown.

{
"errors": [
{
"message": "maximum recursion depth exceeded while calling a Python object"
}
],
"data": {
"device_types": null
}
}

With uwsgi and nxing configured ngnix logs the following:

upstream prematurely closed connection while reading response header from upstream
And in the webui a HTTP 502 error is shown.
Expected Behavior
Receive all configured device types as it did before upgrading to version 1.2.1.
Observed Behavior
See point 3 and 4.

Thanks for the report! Here's the stack trace I see:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/graphql/execution/executor.py", line 481, in complete_value_catching_error
    exe_context, return_type, field_asts, info, path, result
  File "/usr/local/lib/python3.6/site-packages/graphql/execution/executor.py", line 557, in complete_value
    exe_context, return_type, field_asts, info, path, result
  File "/usr/local/lib/python3.6/site-packages/graphql/execution/executor.py", line 599, in complete_list_value
    for item in result:
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 287, in __iter__
    self._fetch_all()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 283, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 71, in __iter__
    obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 513, in from_db
    new = cls(*values)
  File "/usr/local/lib/python3.6/site-packages/nautobot/dcim/models/devices.py", line 152, in __init__
    self._original_u_height = self.u_height
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query_utils.py", line 149, in __get__
    instance.refresh_from_db(fields=[field_name])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 635, in refresh_from_db
    db_instance = db_instance_qs.get()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 353, in get
    return qs._no_monkey.get(qs, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 425, in get
    num = len(clone)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 269, in __len__
    self._fetch_all()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 283, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 71, in __iter__
    obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 513, in from_db
    new = cls(*values)
  File "/usr/local/lib/python3.6/site-packages/nautobot/dcim/models/devices.py", line 155, in __init__
    self._original_front_image = self.front_image
  File "/usr/local/lib/python3.6/site-packages/django/db/models/fields/files.py", line 180, in __get__
    instance.refresh_from_db(fields=[self.field.name])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 635, in refresh_from_db
    db_instance = db_instance_qs.get()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 353, in get
    return qs._no_monkey.get(qs, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 425, in get
    num = len(clone)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 269, in __len__
    self._fetch_all()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 283, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 71, in __iter__
    obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 513, in from_db
    new = cls(*values)
  File "/usr/local/lib/python3.6/site-packages/nautobot/dcim/models/devices.py", line 152, in __init__
    self._original_u_height = self.u_height
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query_utils.py", line 149, in __get__
    instance.refresh_from_db(fields=[field_name])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 635, in refresh_from_db
    db_instance = db_instance_qs.get()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 353, in get
    return qs._no_monkey.get(qs, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 425, in get
    num = len(clone)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 269, in __len__
    self._fetch_all()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 283, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 71, in __iter__
    obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 513, in from_db
    new = cls(*values)
  File "/usr/local/lib/python3.6/site-packages/nautobot/dcim/models/devices.py", line 155, in __init__
    self._original_front_image = self.front_image
...

where the following seems to be the infinite recursive loop:
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 635, in refresh_from_db
    db_instance = db_instance_qs.get()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 353, in get
    return qs._no_monkey.get(qs, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 425, in get
    num = len(clone)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 269, in __len__
    self._fetch_all()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 283, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 71, in __iter__
    obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 513, in from_db
    new = cls(*values)
  File "/usr/local/lib/python3.6/site-packages/nautobot/dcim/models/devices.py", line 152, in __init__
    self._original_u_height = self.u_height
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query_utils.py", line 149, in __get__
    instance.refresh_from_db(fields=[field_name])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 635, in refresh_from_db
    db_instance = db_instance_qs.get()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 353, in get
    return qs._no_monkey.get(qs, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 425, in get
    num = len(clone)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 269, in __len__
    self._fetch_all()
  File "/usr/local/lib/python3.6/site-packages/cacheops/query.py", line 283, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 71, in __iter__
    obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 513, in from_db
    new = cls(*values)
  File "/usr/local/lib/python3.6/site-packages/nautobot/dcim/models/devices.py", line 155, in __init__
    self._original_front_image = self.front_image
  File "/usr/local/lib/python3.6/site-packages/django/db/models/fields/files.py", line 180, in __get__
    instance.refresh_from_db(fields=[self.field.name])
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 635, in refresh_from_db
    db_instance = db_instance_qs.get()

Oddly enough I don't think this is code we've touched recently, so I'm not sure yet why this issue is appearing.

FYI, we upgraded from 1.1.5.


Add support for Teams Adaptive cards in QnA Dialog

Fixes Internal IcM Issue #373550043
Port of changes from https://github.com/microsoft/botbuilder-js/pull/4467
Fixes #6630
Description

This PR allows for choosing Adaptive Cards formatted for use in Microsoft Teams instead of the default Hero Cards. This is done to support markdown formatting in QnA and CQA responses since Teams only supports markdown in Adaptive Cards. Changes are made in QnACardBuilder.cs and QnAMakerDialog.cs.
Using the new cards simple requires adding code in the bot to take in a new environment variable: UseTeamsAdaptiveCard = "true" and pass it to the QnA dialog constructor. If no changes are made, the bot will default to a Hero card.
Specific Changes

Create new methods to generate adaptive and hero cards
Modify the card builder class to take in a new bool field to allow for choosing whether or not to use an adaptive card
Modify the dialog class to accept the aforementioned bool field and pass it to the card builder.

Testing

Tests tun successfully.

Pull Request Test Coverage Report for Build 349483

0 of 0   changed or added relevant lines in 0 files are covered.
105 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 78.951%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder.AI.QnA/Dialogs/QnAMakerDialog.cs
46
69.92%

/libraries/Microsoft.Bot.Builder.AI.QnA/Utils/QnACardBuilder.cs
59
47.93%

Totals

Change from base Build 349053:
-0.1%

Covered Lines:
25828

Relevant Lines:
32714

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll

@ceciliaavila,
Could you please provide feedback on the new tests?

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll


GitHub Actions: Arm based hosted runners (Public Beta)

Summary
The GitHub-hosted runner portfolio is expanding to include Arm-based hosted runners. These runners will be fully managed by GitHub with a base image containing a foundational set of tools. Powered by the Ampere Altra Arm–based processor, these runners offer a power efficient compute layer which can increase price to performance ratios, allowing customers to optimize compute costs.
Intended Outcome
Customers are refactoring their applications to take advantage of the price performance benefits of ARM architecture. Developers can now run their workloads on Arm-based hardware hosted by GitHub to build and deploy their release assets anywhere Arm’s architecture is used. These new runners provide power, performance & sustainability improvements for all your Actions jobs.
How will it work?
To get started using Arm-based GitHub-hosted runners, create a runner in a runner group choosing Arm as the hardware. Then update the runs-on: key in your Actions workflow YAML to have those jobs target the new runner. These runners are available for GitHub Team & Enterprise plans only.

🚢 This has shipped: https://github.blog/changelog/2024-09-03-github-actions-arm64-linux-and-windows-runners-are-now-generally-available