Video: Combine "title" and "assistive text" fields

Summary
1.drop the alt text input UI.
2.use one text field to set both alt and title.
Relevant Technical Choices
Remove the text input for alt.
Keep alt in amp-video tag.
Use the title update logic to update both title and alt.
To-do
N/A
User-facing changes
There is only 1 text field for the video description / assistive text field
Testing Instructions
After creating the video and updating the video's assistive text, the alt attribute should show up under the <amp-video> tag, with the same value as title.

Fixes #4708

There are some unrelated/unnecessary changes to package-lock.json here. Please undo those and CI should run smoothly again.

There are some unrelated/unnecessary changes to package-lock.json here. Please undo those and CI should run smoothly again.

There are some unrelated/unnecessary changes to package-lock.json here. Please undo those and CI should run smoothly again.

Done, and sorry for the force push; I have done some research on the follow up commit. Since I accidentally messed up the first commit (by using force push) the following commit might be affected and might need to use force push as well. I will keep in mind and keep making multiple commits in my coming PR.

Related: #5353

Here is the updated screenshot:

Just a heads up🤣, really not meant to do the force push. Because previously messed up the git, just did it for the fix. I will for sure do the normal commit in any of my other coming PRs.

@zidianlyu Two suggestions after QA feedback in https://github.com/google/web-stories-wp/issues/4708#issuecomment-736657668

use alt for the combined field, not title
Update wording in media edit dialog (assets/src/edit-story/components/library/panes/media/local/mediaEditDialog.js) to say "Video description" (or "Image description", respectively) instead of "Alt text"

Note: to see mediaEditDialog.js in action, click on "edit" here:

There is a merge conflict.

@zidianlyu FYI, took the liberty to expand on the PR to cater for the pre-publish checklist and the media edit dialog. Updated the description accordingly.


Load flow comparison on PEGASE case

using: case9241pegase

The .m and .mat file are both available here: https://github.com/G-PST/power-flow-exercise/tree/main/reference-matpower

[ ] PowerSystems.jl
[ ] PowerModels.jl
[ ] PowSybl
[ ] pandapower


Fix agent not reconnecting to master

This PR fixes race condition in agent websocket client that is triggered by client trying to send message via ws client that does not exist (or is in some weird state).
Fixes #840

@miskun ping


audio / video .canPlayType(MIMEtype)

The HTMLMediaElement.canPlayType() method determines whether the specified media type can be played back.
Can be used like this: [audio | video].canPlayType('video/mp4')
Some MIME types would be:
audio/mpeg
audio/mp4
audio/ogg
audio/ogg
audio/webm
audio/wav
link to MDN here

Pretty sure this is supported by all audio & video supporting browsers.

Looks like this is now covered by MDN data:
https://caniuse.com/mdn-api_htmlmediaelement_canplaytype
(via mdn/browser-compat-data#1166)

Closing per last comment.


It should be like this

It should be | Music | Movies | because is it just that or was it like that?

Video !?

@divyam234

@divyam234  can you help me with it or fix it

FIX GOOD


feat: add speech to text sdk methods

passing all but serialization fuzzing tests
@mhamilton723

 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.:x: zhang-lucy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

/azp run

/azp run

/azp run


update generate_inventory for fans

In some water-cooled systems, the attributes for fans may not include "Functional".  Update bin/generate_inventory for fans in those systems.

see related issue https://github.com/openbmc/openbmc-test-automation/issues/1456

https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/13815/


Add pull request template file

Will help us remember to do routine tasks for each PR and have a standardized format.

note that we can also add an ISSUE_TEMPLATE.md file later if we feel it's necessary.

Looks good!


How to add visitor map to my personal website

How to add visitor map that shows the number of visitors worldwide who visit my github.io website?

Like the world map on the upper right of this website:
http://www.shichuan.org/ShiChuan_ch.html

This function is interesting. Why not add to the plan? @rjzupkoii

@CaucherWang It is an interesting feature, but I'm not sure a lot of people would actually make much use of it, which makes it outside the scope of the template itself. However, if you start a thread over in the disucssions you might find some people that are also interested in implementing one.


add "buildin" system.js and inject as dependency instead of evaluating to raw object

What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
Not yet, need to check if this is the way to go
If relevant, link to documentation update:
N/A
Summary
Instead of evaluating System to {} this injects a System "polyfill"
Does this PR introduce a breaking change?
No
Other information
PTAL @sokra @ljharb
i copy & pasted the buildExpression might need to want to extract that to parserHelpers if this approach is deemed to be "ok"
fixes #4329

[ ] move buildExpression to ParserHelper?
[ ] add test

@ljharb you can do a separate PR renaming it.

¯\_(ツ)_/¯ it's not my codebase and it's not exposed to users, so if the maintainers prefer a non-word that's fine by me

this will actually not  work yet due to typeof System === "undefined" being evaluated to false again therefore always returning non-existing "System".
Will make a new PR tonight

Doesn't webpack polyfill System which is why it changes typeof System === 'undefined' to false?

Doesn't webpack polyfill System which is why it changes typeof System === 'undefined' to false?

yep, typeof System === "object" in webpack.

yes it does, but that leads the "polyfill" to be evaluated to
module.exports = false ? {} : System;
see -> #4373 for suggested fix


Temp tables trigger a schema rebuild

The schema maintaining trigger includes temp tables when watching ddl statements. If users leverage temp tabes extensively it will cause unnecessary schema cache reloads
TODO: steal update from https://postgrest.org/en/latest/schema_cache.html#finer-grained-event-trigger

https://github.com/PostgREST/postgrest-docs/issues/445
https://github.com/PostgREST/postgrest-docs/pull/489

https://github.com/supabase/pg_graphql/blob/1ea20d11932bcdbf0bfe3992b5364e6985c3cf1a/pg_graphql--0.1.0.sql#L3321


Finish AlphaMinusJacobian function

Creates a general-use function for calculating [ alpha * I - jacobian ]. Moves the call to the LU factorization out of the this function for easier testing.
closes #107

Codecov Report
Patch coverage: 97.43% and project coverage change: +0.01 :tada:

Comparison is base (37947c6) 93.72% compared to head (57d2aa7) 93.73%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #117      +/-   ##
==========================================
+ Coverage   93.72%   93.73%   +0.01%
==========================================
  Files          23       23
  Lines        1704     1612      -92
==========================================
- Hits         1597     1511      -86
+ Misses        107      101       -6

Impacted Files
Coverage Δ

include/micm/solver/rosenbrock.hpp
82.83% <97.29%> (-5.33%)
:arrow_down:

include/micm/util/sparse_matrix.hpp
99.09% <100.00%> (+0.01%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


(SERVER-2401) Handle new exceptions when checking CA status

From 03da206 which implements most of this functionality:
Previously, we were catching ECONNREFUSED to determine if the server was
up. When we moved to custom error classes we no longer raise an
ECONNREFUSED, instead raising ConnectionFailed in it (and many other
potential exceptions) place.

So we should now be rescuing ConnectionFailed, but we only want to
swallow exceptions that originated from ECONNREFUSED, re-raising
ConnectionFaileds that originate from other exceptions.

To do so we add the ability to wrap an exception in our custom Error
class and update appropriate places where we were raising.

I snuck in f7fbc63 which changes the help output for generate from:
        --ca-client                  Whether this cert will be used to request CA actions.\
                    Causes the cert to be generated offline.

to
        --ca-client                  Whether this cert will be used to request CA actions.
                                     Causes the cert to be generated offline.


add tus swap to avax via pangolin

Hi @coccoinomane not sure if you like to include this, but just adding the functionality to swap TUS -> AVAX via the bot. Was writing for my own use so decided might as well just write it in this repo
edit: no tests written because I tested with real money

Wow @EugeneTeu , this is an impressive PR!
I love how you extended the Web3Client to use with Pangolin and TraderJoe: great job 💪
However, I am hesitant to add this to crabada.py.
Swap functionalities are indeed useful, but they go outside the scope of the bot.
It is a lot of code to add tocrabada.py, and we might end up with all sort of issues and support requests: slippage problems, failed swaps, request for other tokens, etc.
I fear this would lead the project astray.
This material is better suited for a separate project, say, dextools.py.
A suite of CLI tools to interact with DEXes written in Python, which in principle could support any Uniswap V2 clone.
(I confess that lately I've been working on something similar, but on Javascript.)
If you decide to go ahead with the idea of the separate project, I am happy to make Web3Client an independent pip project, so that you can use it as a dependency.
Cheers,
Cocco

sure. After thinking about it, i agree with you on the scope of the bot. For now I will leave this in my fork then!
on making the Web3Client a pip project, that would be great!

sure. After thinking about it, i agree with you on the scope of the bot. For now I will leave this in my fork then!
on making the Web3Client a pip project, that would be great!

Thank you @EugeneTeu for your understanding :-)
I will read some material on pip and then go ahead with the Web3Client project.
Cheers,
Cocco


[WIP] support cold memory collection and report

Ⅰ. Describe what this PR does
add proposal about cold memory collection and report

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

@BUPT-wxq Glad to see your proposal. Please check the failed CI pipelines below.

e.g. DCO requires you to sign-off the git commits.


Tabs don't work in 0.8.0

\t characters, or tabs, are broken.
I'm not sure if this is desired or not, but I use tabs in my pdfs rather frequently and it works fine in version 0.6.4. With the newest version they are no longer tabs.
Here is a picture rendered using pdfkit 0.8.0

Here is a picture of how it should look, using 0.6.4

Thank you for this awesome software, I must say you really did an excellent job and I am super grateful!

This is still an issue, if there is a workaround for this I would greatly appreciate it.

Still an issue.

I just wanted to say that this is still an issue with version 0.12.1.
Luckily, we actually don't even need a tab, but we noticed that user-provided strings containing \t lead to interesting problems which look like encoding issues (but are actually caused by the tab character). It's also reproducible in the playground linked in the readme.

Still an issue.


open locks: operation not permitted

Output of restic version
restic 0.7.0
compiled with go1.8.3 on linux/amd64
How did you start restic exactly? (Include the complete command line)
restic -r /mnt/media/restic-backups/box/ --quiet --exclude-file /home/user/etc/restic.excludes backup /home/user
What backend/server/service did you use?
local mount
Expected behavior
backup. it worked in 0.6.1
Actual behavior
open /mnt/media/restic-backups/box/locks/2c1b721129e9edb0e69cc813a404aa2de1e4abbd6f858e5e6fb3c34c8ccfc9f1: operation not permitted
OpenFile
restic/backend/local.(*Local).Save
	src/restic/backend/local/local.go:113
restic/repository.(*Repository).SaveUnpacked
	src/restic/repository/repository.go:230
restic/repository.(*Repository).SaveJSONUnpacked
	src/restic/repository/repository.go:215
restic.(*Lock).createLock
	src/restic/lock.go:173
restic.newLock
	src/restic/lock.go:102
restic.NewLock
	src/restic/lock.go:63
main.lockRepository
	src/cmds/restic/lock.go:36
main.lockRepo
	src/cmds/restic/lock.go:23
main.runBackup
	src/cmds/restic/cmd_backup.go:370
main.glob..func2
	src/cmds/restic/cmd_backup.go:39
github.com/spf13/cobra.(*Command).execute
	src/github.com/spf13/cobra/command.go:631
github.com/spf13/cobra.(*Command).ExecuteC
	src/github.com/spf13/cobra/command.go:710
github.com/spf13/cobra.(*Command).Execute
	src/github.com/spf13/cobra/command.go:669
main.main
	src/cmds/restic/main.go:63
runtime.main
	/usr/local/go/src/runtime/proc.go:185
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:2197

That disk is mounted and I can write there. It isn't full.
Steps to reproduce the behavior
Do you have any idea what may have caused this?
No but it started after I upgraded to 0.7.0

Trying with 0.6.1 gives the same error now.

The backup to b2 still works.

DEBUG_LOG does not work, I guess the official binary is not built with support for that.

Hi, thanks for raising this issue. I have a rough idea what may have happened here, but I'd like you to create a debug log for it. You need to recompile restic, instructions are here: https://github.com/restic/restic/blob/master/CONTRIBUTING.md#reporting-bugs

Which file system do you use?

ext4

I think I know what is happening. I am hitting another issue, I cannot chown any files on this nfs share. Not your bug.

I fixed the problem with the nfs share and now restic is working again. Sorry for the not-a-bug.

Thanks for leaving feedback, it's always good to know what's the underlying issue is.
In this case I think it's not chmod since that's done later in the code. I suspect it's the open call with O_EXCL. That wasn't present in earlier versions of restic.


Langgraph streaming error

Hello, I'm trying to hook up assistant UI to langraph but recently started getting an error that affected the behavior of the frontend application. I never got this error in the past. I just started up my FE and BE servers one day and noticed this.
Here's a screenshot of the error in my browser console:

Thanks for reporting this, fixed in v0.0.21

Thanks for the feedback...all good now.


display statement in el2_ifu.sv

Hi,
I saw these lines in el2_ifu.sv file
https://github.com/chipsalliance/Cores-SweRV-EL2/blob/7045b803cab825bc3bb3dbca0cb019e55098acc4/design/ifu/el2_ifu.sv#L340-L362
If we see line num 340, it says:
https://github.com/chipsalliance/Cores-SweRV-EL2/blob/7045b803cab825bc3bb3dbca0cb019e55098acc4/design/ifu/el2_ifu.sv#L340-L341
That on every falling edge of clock, if mcyclel value = 32'h00000010 then we will see all the $display statements.
However, when I write the csr mcyclel with 32`h00000010 it does nothing.
Can anybody help me out about how can I generate all the display statements? As I am currently understanding branch prediction of SweRV EL2, visualizing the results with the help of display statement would speedup my progress.
Thankyou,

I am writing 32'h00000010 on 0xB80 (address of mycylel). Am I following the correct direction?

it's designer's leftover to debug his stuff, I'm not sure about mcycle reference there , but you need to provide DUMP_BTB_ON define to compile this code...

Yes, I had noticed that later. Can you let me know about how I can set this define DUMP_BTB_ON . I can't find this define other than el2_ifu.sv.

need to `define ... in the el2_ifu.sv file .  BTW, you don't need to write to mcycle in your test.

I have tried both ways but it didn't worked


i18n(es): Update i18n.mdx

What kind of changes does this PR include?

Minor content fixes (broken links, typos, etc.)
Changes or translations of Starlight docs site content

Description

What does this PR change?
Update i18n.mdx #809

Hacktoberfest

I am participating in the Hacktoberfest!

Hi @K1ri86 thanks for your PR! We actually don’t want to translate the values of this object. As it says just before the code snippet:

Estos son los valores predeterminados en inglés de las cadenas existentes que se incluyen en Starlight:

“en inglés”, so we should keep them in English!
I think that means the only change needed is to add the 404.text line (in English)?

I saw it translated into other languages and thought it was necessary, so I reverted the commit and added the necessary changes.

Perfect — thank you @K1ri86! And sorry for the extra work you had to do for those translations that weren’t needed 😁

@delucis You can accept hacktoberfest ? 😁

Done! Sorry I missed that.


Near query results are incorrectly sorted

Link to reproduction

To Reproduce

Create a Collection with a point data field
Add some test data
Run near queries on the rest api and graphql and see the sorting and pagination values

Describe the Bug
I think i found a bug with the geo-search functionality.
In the payload docs it says that near queries are automatically ranked based on distance. But the results on the rest api and graphql api are not sorted by distance and different to the sorting when executing the same query on native mongodb.
Even the pagination infos returned from payload are wrong. Pagination shows always infos calculated on the entire data and does not align with the amount of returned results.
This is my collection:
const BusinessListing: CollectionConfig = {
  slug: "business-profiles",
  admin: {
    useAsTitle: "name",
    group: "Business",
  },
  access: {
    create: adminsAndBizUser,
    read: (): boolean => true,
    update: adminsAndBizUser,
    delete: adminsAndBizUser,
  },
  labels: {
    singular: "Profile",
    plural: "Profiles",
  },
  fields: [
    {
      name: "name",
      type: "text",
      required: true,
      label: "Name",
    },
    {
      name: "street",
      type: "text",
      label: "Street",
    },
    {
      name: "streetNumber",
      type: "text",
      label: "Street Number",
    },
    {
      name: "postalCode",
      type: "text",
      label: "Postal Code",
    },
    {
      name: "city",
      type: "text",
      label: "City",
    },
    {
      name: "country",
      type: "select",
      label: "Country",
      options: [
        { label: "Germany", value: "Germany" },
        { label: "Austria", value: "Austria" },
        { label: "Switzerland", value: "Switzerland" },
      ],
    },
    {
      name: "phone",
      type: "text",
      label: "Phone",
    },
    {
      name: "email",
      type: "text",
      label: "Email",
    },
    {
      name: "website",
      type: "text",
      label: "Website",
    },
    {
      name: "location",
      type: "point",
      label: "Location",
    },
    {
      name: "description",
      type: "richText",
      required: false,
      label: "Description",
    },
    {
      name: "slug",
      type: "text",
      required: true,
      unique: true,
      label: "Slug",
      admin: {
        position: "sidebar",
      },
      hooks: {
        beforeValidate: [formatSlug("name")],
      },
    },
    {
      name: "gallery",
      type: "array",
      label: "Gallery",
      fields: [
        {
          name: "image",
          type: "upload",
          relationTo: "media",
          required: true,
          label: "Image",
        },
      ],
    },

    {
      name: "category",
      type: "relationship",
      relationTo: "business-categories",
      required: true,
      label: "Category",
      hasMany: true,
    },
    {
      name: "featured",
      type: "checkbox",
      required: true,
      label: "Featured",
      admin: {
        position: "sidebar",
      },
    },
    {
      name: "published",
      type: "checkbox",
      required: true,
      label: "Published",
      admin: {
        position: "sidebar",
      },
    },
  ],
  timestamps: true,
};`

This query in native mongodb gives results with correct sortings by distance:
`{
  location: {
    $near: {
      $geometry: {
        type: 'Point',
            coordinates: [ 7.6724351, 52.01594009999999 ]
      },
      $maxDistance: 20000,
          $minDistance: 0
    }
  }
}`

This query with the payload graphql api returns wrong sorted results:
`query getBusinessProfiles {
	BusinessProfiles(
    where: {
      location: {
        near: [ 7.6724351, 52.01594009999999, 20000,0 ]
      }
    }
  )
  {
    docs{
     name
      city
    }
  }
}

This query with the payload Rest-api returns even wrong sorted results and the pagination data is totally wrong and not matching the count of results:
const query = qs.stringify(       {         where: {           location: {             near: ${location.lng},${location.lat},${range},0,           },         },       },       { addQueryPrefix: true }     );
Payload Version
1.9.5

I fixed the issues with the commit. Sorting and pagination is both working with that.


"worng!" mesage

Hi! Could you explain when the error is triggered and how I can avoid it?
https://github.com/GhiXu/ACMMP/blob/f4c78f04b8a78f8565242950190df14a53fba7ab/ACMMP.cpp#L975
The method still produces good results, but always with this error, I'm confused.

Hi Kaktusava! Have you figured it out? I'm also confused with this message.

I also encountered this problem, and I'm wondering how could this happen.  When will this sentence be 'true' jbu.depth_h[center] != jbu.depth_h[center].

Has anyone solved this problem? I aslo encountered this problem.  Is the array out of bounds? Or is the value invalid？

Hi @zjhthu this line is used to check if the value is NaN
This message comes relatively late in the process so it's hard to figure out what happens but it may find its origin in a wrong data preparation.


How to initiate a desktop stream from VLC?

I'm trying to stream a desktop from an Ubuntu Box using VLC and this command:
cvlc screen:// :screen-fps=15 :live-caching=450 :sout='#transcode{vcodec=h264,venc=x264{qp=21},acodec=none,scodec=none}:rtp{sdp=rtsp://:8554/ch0.h264}' :no-sout-all :sout-keep
This stream fine to the Picture-Entity card.
But when using Webrtc-camera card, I'm getting this error:
ERROR: Camera send statusRTSP/1.0.461 Client error
Can anyone tell what I should change to make this work with WebRTC?

Hi, wondering if anyone could help out with this.  I'm trying to get a VLC stream working, let me know if there is anything from the commandline perspective that I can change to make this work.

VLC seems to have incorrect support for the RTSP specification

Thanks, Do you have specifics on which part is not correct?  I can connect with VLC to see if I can get something resolved.
The odd thing is that the regular camera card in HA support the VLC RTSP stream but not this.

Check my new project. Maybe it handle this situation
https://github.com/AlexxIT/go2rtc

Closed because no response


Change the 'Version' link in the Info panel

Steps to Reproduce

Launch Ketcher.
Click the  'About' icon.
Click the 'Version 2.4.2' link.

Expected behavior
The user is redirected to the following page https://lifescience.opensource.epam.com/ketcher/index.html
Actual behavior
The user is redirected to the obsolete Help page - https://lifescience.opensource.epam.com/ketcher/help.html
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 101.0.4951.67

Ketcher version
Ketcher v2.4.2-325-g75abd1d4

Additional scope:
update help link: should open the 'help' page according to latest tag (not according to the current branch)


feat(stdlib): encode and decode base16

Motivation
provide a human-friendly representation of binary-coded values.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
move test passed in language/move-stdlib/nursery/sources directory.

I am personally in favor of having more of these utility encoding/decoding libraries inside the Move stdlib, but we need to think carefully about how we want to organize them--one module per format (as this suggests?). All in one big bytes module? Something else?

I support one module per format

Another approach we could consider here (that would make the testing burden a bit less onerous) is to implement this via native functions that wrap the Rust hex library.

Another approach we could consider here (that would make the testing burden a bit less onerous) is to implement this via native functions that wrap the Rust hex library.

I also think it is possible to let the User Module implement a native function with a WASM runtime in the future. This approach lets adding new native functions more gracefully and does not need a hard fork upgrade.


Filters bis

Filter interface without use of templates.
Mono and stereo are instanciated within a single object. (cf. setChannels)
Add the filter demo program as Jack-Qt client.
It's to check everything to be OK after changes.
Also, the demo program supports the FilterEq.

Cf #44, we may only need to use stereo filters in the end.

I'll merge now to put in place new API.
It needs to remove the template parameters in the benchmarks, use setChannels instead.
I'll update it.


Add missing migration

This includes the help text introduced in 325aab3.

Should we perhaps add the following as a travis prerun script?
./manage.py makemigrations --check --dry-run

--check isn't available in this version of Django:
$ ./manage.py makemigrations --check --dry-run
usage: manage.py makemigrations [-h] [--version] [-v {0,1,2,3}]
                                [--settings SETTINGS]
                                [--pythonpath PYTHONPATH] [--traceback]
                                [--no-color] [--dry-run] [--merge] [--empty]
                                [--noinput] [-n NAME] [-e]
                                [app_label [app_label ...]]
manage.py makemigrations: error: unrecognized arguments: --check

Maybe worth doing something like this then?
https://gist.github.com/nealtodd/a8f87b0d95e73eb482c5


golangci: fix golangci-lint reported linting issues

This commit fixes go code style according to golangci-lint best practices and makes
golangci-lint Makefile target to pass. Fixes: https://github.com/containers/nri-plugins/issues/24

cc @mythi

In any case, let's hold this back until #20 is merged. That one is fairly intrusive in terms of which files it needs to touch.

@fmuyassarov shall we mark this PR as non-draft, get it reviewed and merged?

I even forgot about this patch, lol. Yes, let's do it. I will try to fix other issues as well. I think it will be ready latest by tomorrow.


Convert box2d body position from meters to pixels

This solves know problems with attachToBody() method in this class. Box2d always handles meters, instead pixels:
According to Box2D manual:
Caution

Box2D is tuned for MKS units. Keep the size of moving objects roughly between 0.1 and 10 meters.
You'll need to use some scaling system when you render your environment and actors.
The Box2D testbed does this by using an OpenGL viewport transform. DO NOT USE PIXELS.

Why on earth 2 pull requests? This PR clearly depends on #75, so they should be just 1.

Sorry for that! I new to github system.

Sorry, but currently I don't understand why you need converting the start position to pixels. And what are the "known" problems with attach to body method?
I don't reject the thing that I missed something, but the box2dlights is completely working in the box2d world coordinates, and scaling the start vector to pixels, seems to me, will break the other dependent methods, like contains() and etc. which uses the start.x/y values.

The 'know' problems are:

Some users (specially beginners) uses the pixel_to_meters constant, by multiplying / dividing these pixels. A common practice is dividing pixels with meters scale:
  final float PIXELS_TO_METERS = 100f;
  float b2PositionX = 800 / PIXEL_TO_METERS;
  float b2PositionY = 128 / PIXEL_TO_METERS;

Then these divided box2d coordinates pass to box2dlights...

...and then use attachToBody method, but does not follows the light to the body.

For example: http://badlogicgames.com/forum/viewtopic.php?f=11&t=5610#p26860
I've seen the solution: scale the camera, but I my case, I need to handle pixels only (because I do several calculations with pixels).
Ok, I've seen on some code examples using a constant for convert pixels to box2d coordinates and vice-versa (like this: http://www.gamefromscratch.com/post/2014/09/10/LibGDX-Tutorial-13-Physics-with-Box2D-Part-2-Force-Impulses-and-Torque.aspx).
Some users try to scale just the body position, instead deal with the camera.
An optional field variable can be used, so, these divided values will scale to meters:
	// Where BOX2D_WORLD_SCALE is actually PIXEL_TO_METERS
	start.x = vec.x * RayHandler.BOX2D_WORLD_SCALE + dX;
	start.y = vec.y * RayHandler.BOX2D_WORLD_SCALE + dY;

Or you could use a camera with proper scale, like you probably should. We can't guard against all possible mistakes. It should be documented of course.

Ok, I got it, I created a new matrix for store the camera.combined, then scale to box2d and finally apply this matrix to box2dlights:
float PIXELS_TO_METERS_MUL = 100;
float PIXELS_TO_METERS_DIV = .01f;
	box2dLightsMt
		.set(camera.combined)
		.scale(PIXELS_TO_METERS_MUL, PIXELS_TO_METERS_MUL, 0)
	;

	rayHandler.setCombinedMatrix(
		box2dLightsMt,
		camera.position.x * PIXELS_TO_METERS_DIV,
		camera.position.y * PIXELS_TO_METERS_DIV,
		1280 * PIXELS_TO_METERS_DIV,
		800 * PIXELS_TO_METERS_DIV

	);

Yeah, sorry for my mistake, please cancel my PR.


Fix encoding set and maps for unions in thrift-server

Currently the encode method for thrift unions uses the wrong type when mapping values for lists, sets, and maps (it should be using the loose variant for the type).  This results in invalid typescript when in strict mode.
This only changes the codegen for thrift-typescript.

There is also a pretty bad mistake I made in the test refactor.  When reformatting the code, I added braces around a filter arrow function, which resulted in it always returning false.  This resulted in a large chunk of unit tests being no-ops.

v3.2.0-1

@hayes I was a little quick with that. Publish fails because one of the unit tests fails.

Weird. They were passing for me, I'll push a fix when I get back to a computer


Logs returned by ContainerState.getLogs are missing line separators if TTY is set to true

Problem
When using testcontainers 1.15.2, a call to ContainerState.getLogs() for a container with TTY set to true returns a string that has no line separators at all between log rows. Reverting to testcontainers 1.15.1 makes it work again.
$ docker -v
Docker version 20.10.6, build 370c289

Analysis
I'm not that familiar with testcontainer internals (yet) and not the Docker API at all (yet), so bear with me :grin: I have been debugging this for the past hours, and just need to start writing down my findings.
First of all, this change of behaviour seems to come from #3752 (which fixed #1763 and #1854). So the immediate cause of this change is quite clear. But I doubt that just reverting #3752 is the right path forward.
So, I have a custom Tomcat container. Stepping through a call to ContainerState.getLogs() on that container, I end up in org.testcontainers.shaded.com.github.dockerjava.core.FramedInputStreamConsumer with StreamType set to RAW (probably because it was started with TTY?).

This in turn means I end up in org.testcontainers.containers.output.FrameConsumerResultCallback.processRawFrame(OutputFrame outputFrame, Consumer<OutputFrame> consumer) and .normalizeLogLines(String utf8String, Consumer<OutputFrame> consumer). The normalizeLogLines method splits the frame on any newline separators, and passes it on to the Consumer<OuputFrame> WITHOUT any newline on the end of a line (even if the raw frame had one).

As long as ToStringConsumer made sure that newlines were added, this worked fine. However, it probably also meant that with testcontainer versions before 1.15.2 and non-TTY containers (with streams of type STDOUT or STDERR), log rows ended up with two \n between them.
Might be worth adding some context on why we're using TTY as well. We previously had some spurious test failures with the Tomcat container. We never really found a way of reliably reproducing it outside CI (maybe even not at all?), but we believe that it was caused by a WaitStrategy that looked for a certain row logged by Tomcat when it had successfully started, and that that log row was sometimes split up on two different lines in the log output. After adding..
withCreateContainerCmdModifier( cmd -> cmd.withTty( true ) );

..we have not seen a single failure of the same kind.
Solution
As I said, I don't think reverting #3752 is necessarily the right thing to do, because it solved a real issue. Should FrameConsumerResultCallback.normalizeLogLines be fixed to retain newlines? OTOH, Slf4jLogConsumer already seems to take care of any trailing newlines internally, which may be a hint that the fix in ToStringConsumer should instead have been to check if a trailing newline exists, and just add one if not. Or something completely different?

A simple reproducer: https://github.com/slovdahl/testcontainers-issue-4110-reproducer

but we believe that it was caused by a WaitStrategy that looked for a certain row logged by Tomcat when it had successfully started, and that that log row was sometimes split up on two different lines in the log output

This problem is very likely caused by #5843

Imho the FrameConsumerResultCallback should guarantee that it passes a single and complete line to the consumer in all cases independent of stream type and fragmentation. Then, there is no need for the lines to contain any newline characters, and every consumer can add them if required.

I've been able to reproduce this issue. If you set PostgreSQLContainer TTY to true, then it fails to start as it relies on logs for it's startup strategy:
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
	at app//org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:543)
	at app//org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:345)
	at app//org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
	... 72 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*database system is ready to accept connections.*\s'
	at app//org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
	at app//org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
	at app//org.testcontainers.containers.PostgreSQLContainer.waitUntilContainerStarted(PostgreSQLContainer.java:139)
	at app//org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:486)
	... 74 more

Though, idk much about TTYs. What's the usecase for them?


Add support for more common beatmap mirror APIs

Nerina API is a lot better then other beatmap API in my experience

[x] Support Newest, Top+Rated, Most+Played

[ ] Tested Chimu

[x] Tested Cheesegull

[x] Tested Nerina

thanks for the work though! this looks good :)

Can you change nerina mirror server name to nerinyan? it is official name

Can you change nerina mirror server name to nerinyan? it is official name

I know but the mirror name call Nerina right?
I follow the mirror name, I guess I will just ask the Nerinyan staff about it

Please change Neriyan's api address api.nerina.pw to api.nerinyan.moe

Please change Neriyan's api address api.nerina.pw to api.nerinyan.moe

Ya I know, will change later


Running test says "trigger_mode is not defined" when it is

Possibly related to #66 (default settings not working)
Screenshot:

octoprint.log:
2022-12-30 06:01:46,382 - octoprint.server.api - ERROR - Error while executing SimpleApiPlugin filamentsensorsimplified
Traceback (most recent call last):
  File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/server/api/__init__.py", line 158, in pluginCommand
    response = api_plugin.on_api_command(command, data)
  File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/__init__.py", line 1688, in wrapper
    return f(*args, **kwargs)
  File "/home/pi/oprint/lib/python3.7/site-packages/octoprint_filamentsensorsimplified/__init__.py", line 107, in on_api_command
    self._logger.info(f"Perfoming test (mode: {mode}, pin: {selected_pin}, triggered_mode: {trigger_mode}")
NameError: name 'trigger_mode' is not defined

It says "trigger_mode is not defined" but you can see from the screenshot that it is

Wait - nvm. This one is my fault (messing around with init.py)


Fix "Disable VSync" settings description

I fixed the description of the Disable V-sync setting because it was seemingly copy-pasted to the wrong Fix Minimap Flicker setting. I modified that settings description too but am not quite sure what to write in there because I never actually experienced the issue myself.

Flicker fix is meant to be used with some mods modifying minimap which otherwise caused flickering, unsure which one it was now nor if it is relevant still tbh. :suspect:


Fix documentation example for maven.AddPlugin

What's changed?
Fix documentation example for maven.AddPlugin
What's your motivation?
The  element has to be included by the user, as is made clear in AddPluginTest: https://github.com/openrewrite/rewrite/blob/main/rewrite-maven/src/test/java/org/openrewrite/maven/AddPluginTest.java#L125-L139
Any additional context
One could possibly argue that the documentation is correct, but the implementation is wrong; but the implementation follows the same convention used by the other parameters (configuration and dependencies).

Appreciate the immediate fix! Should prevent others from stumbling over this issue with our docs.


Normalize dtype handling and CSV options

Remove names option in from_csv to remove ambiguity
(users can call rename afterwards)

Normalizea and validate dtypes in from_csv

Remove Inf which is not a common Elixir value

Support returning a list from Series.transform to
unify dtypes handling

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


UpdateActivityHandler definition is different for C#/JS

Versions
What package version of the SDK are you using. Daily (9/18/19)
What nodejs version are you using: n/a
What browser version are you using: n/a
What os are you using: n/a
Describe the bug
The signature and implementation of the update activity handler is different between .NET and JavaScript, and the .NET one more closely matches the Bot Framework protocol.
In the .NET SDK, the handler returns a ResourceResponse object.
public delegate Task<ResourceResponse> UpdateActivityHandler(ITurnContext turnContext, Activity activity, Func<Task<ResourceResponse>> next);

https://github.com/microsoft/botbuilder-dotnet/blob/ea31885753e15065f694c588309fccdc493eb61a/libraries/Microsoft.Bot.Builder/ITurnContext.cs#L54
In the JavaaScript SDK, the handler returns void.
export type UpdateActivityHandler = (context: TurnContext, activity: Partial<Activity>, next: () => Promise<void>) => Promise<void>;

https://github.com/microsoft/botbuilder-dotnet/blob/ea31885753e15065f694c588309fccdc493eb61a/libraries/Microsoft.Bot.Builder/ITurnContext.cs#L54
The Bot Framework protocol [on success] returns a resource response object that contains "the ID for the resource."
To Reproduce
Steps to reproduce the behavior:

Look at the code cited above.
Compare to what the Swagger file defines the underlying behavior to be.
Error: C# and JS implementations diverge, and the JS seems to be the one in error.

Expected behavior
C# and JS implementations have the same semantics and align with the underlying protocol.
Additional context
Any such divergence between the 2 (and soon to be more) SDKs has an exponential impact on the effort needed to support the documentation.
[bug]

This discrepancy extends to the TurnContext's update activity method, too.

Related to this: https://github.com/microsoft/botbuilder-js/issues/1037

Creating a new method to return a ResourceResponse for an UpdateActivity-type operation doesn't add utility to the SDK. After testing, the ResourceResponse returned for UpdateActivity contains the Id of the activity that was just updated. You cannot update an activity without its Id, so the return value doesn't add any value.
As such, we've decided to not increase our surface area nor will we implement any breaking changes.
Closing issue.

Link to comment


[SPARK-33861][SQL][FOLLOWUP] Simplify conditional in predicate should consider deterministic

What changes were proposed in this pull request?
This pr address https://github.com/apache/spark/pull/30865#pullrequestreview-562344089 to fix simplify conditional in predicate should consider deterministic.
Why are the changes needed?
Fix bug.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.

Test build #133740 has started for PR 31067 at commit 3ceffeb.

Test build #133740 has started for PR 31067 at commit 3ceffeb.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38328/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38328/

Test build #133749 has started for PR 31067 at commit fbd837d.

Test build #133749 has started for PR 31067 at commit fbd837d.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38328/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38328/

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

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38337/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38337/

Test build #133749 has finished for PR 31067 at commit fbd837d.

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

Test build #133749 has finished for PR 31067 at commit fbd837d.

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

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38337/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38337/

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

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

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

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

Test build #133740 has finished for PR 31067 at commit 3ceffeb.

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

Test build #133740 has finished for PR 31067 at commit 3ceffeb.

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

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

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

Merged to master.

Merged to master.


tfhub yamnet model can't perform batch prediction

I'm trying to use a pretrained model to extract embeddings.
Single observation
X = np.random.uniform(-1,1,(10, 1000)) # 10 samples of length 1000
yamnet_model_handle = 'https://tfhub.dev/google/yamnet/1'
yamnet_model = hub.load(yamnet_model_handle)

yamnet_model(X[0]) # Works, outputs (scores, embeddings, spectrogram)

Multiple observations does not work
yamnet_model(X) # Doesn't work
hub.KerasLayer(yamnet_model_handle,
               trainable=False,)(X) #Doesn't work either

How can I get the output for all observations in X at once? Is this intended?

Hi @AlejandroBaron,
It looks like the model only take a one dimensional waveform. (num_samples,), then batch inference might not be available off the bat.
On the other hands your waveform will be split in "patches", and you will get as many predictions and embeddings. (1 of each for each patch).
With this in mind, an idea would be to flatten your 10 waveforms in one so they result in 10 patches. You will get your 10 embeddings and 10 classes, 1 for each patch i.e time frame.
Your input is padded first before going through the network by the pad_waveform function. Your first time frame will be of size 15600, then afterwards each hop is about 7680.
Pad manually your 10 waveforms, the first to a size of 15600, and the 9 following to a size of 7680. Concatenate everything and run the inference.
:warning:  I'm not sure about this one as this is a bit hacky, let me know if this helps.

Note: This is a little bit different for the spectrograms as you will get more than 10 of them. Spectograms frames have their own calculation.

@AlejandroBaron,
If this issue is related to yament from tfhub, Can you post this issue on tfhub repo? Thanks!


Improve CI readability

We can improve CI readability by using https://github.com/marketplace/actions/surefire-report.
This would save the time spent searching for the errors in the logs.

Nice @andre15silva , that could be very useful


Contour lines

Any good trail map should show relief somehow. We should find a good open contour line dataset we can host and display on the map. Among other benefits, this will help people map incline tags.

@jake-low You had some good ideas on how to do this. Would you mind elaborating here?

Sure.
Years ago Mapzen released a global elevation dataset on AWS. It's still available there as part of the AWS open data program even though Mapzen is no more. The dataset combines a bunch of different DEMs (digital elevation models) to create a single dataset that covers most of the planet, using the best available (at the time) data for each region. They created this dataset using a tool they built internally called joerd.
It's pretty easy to generate hillshade and contour tiles from this data using GDAL tools. Here's an example of a hillshade tile I generated just now:

And here's a contour set (the actual contours are vectors, this image of them is a screenshot from mapshaper).

There's a few details I'm glossing over, briefly:

the source tiles are 256x256 but you generally want to generate hillshades and contours using more resolution than that, so I used a VRT file to combine the tiles together into a virtual dataset and then read a one-tile region of that at the desired resolution/zoom level.
contours are GeoJSON but need to be simplified and converted to MVT for use in MapLibre
the hillshade above has a 1px border artifact, to fix that you'd read a slightly larger region and then trim afterwards

But long story short, with a bit of scripting you could generate two tilesets from this data source: a hillshade raster set and a contour lines vector set. Then you could bundle them up as PMTiles archives, stick them in S3, and serve them with Lambda + CloudFront (which I think is how the vector tiles for this project are already being served). Then you could use them in the map stylesheet.
This would probably only have to be done once (mountains don't changing shape very often, and even when they do, this dataset is no longer being updated). I think it'd be about a day or two of work to write the scripts to generate these tilesets. Generating the tiles would take a few days on a modest server. I don't have a guess ready for what it would cost, but we could do a smallish test region initially to get an estimate for that.


Revert "chore(build): re-create typings after install"

Reverts Stabzs/Angular2-Toaster#65
Reverting pull request until build dependency for spec file is sorted out.

Coverage remained the same at 100.0% when pulling f500f0f5cb63be1f437fdde8de6e6c98215e02a3 on revert-65-chore/cleanup-typings into 8ca638b3cd84ded364dc3e97c55cfd6fcb00de2a on master.


IE8: Using dynamic input types fails silently

This will work:
<module-input>
  <input type="text" />
</module-input>

This doesn't (it will just ignore rendering the tag without an errors):
<module-input>
  <input type={ opts.type } />

  <script>
    opts.type = 'text'
  </script>
</module-input>

Looks like this is a problem with IE and inputs.
http://stackoverflow.com/questions/3793598/input-setattributetype-checkbox-ie-bug
Guess there's nothing that can be done about that.


Fix Makefile to get git version tag properly in one more command.

I noticed PR #163 was insufficient to fix our Makefile.
In this PR, I added --tags option to one more git describe command.

Sorry I missed that in the other PR!


Add MSI property to Remote Rendering Account

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[X] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[X] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

/azp run automation - sdk

@leni-msft Hi, Lei.
FYI, Dapeng(@ArcturusZhang) had help investigated the "identity Missing" issue and the solution is to explicitly add the "Identity" property to certain resource type definition.

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

Dotnet generation failed because the breaking changes in SDK block test project from being built. It is expected.

@ravbhatnagar Could you please help have a look at this PR? Thank you very much.


Error on retrieve usersettingscollection entity

Hi Florian!
When I retrieve usersettingscollection entity, I have error:
var userSettings = WebApiClient.Retrieve({
            entityName: "usersettingscollection",
            entityId: currentUser.replace("{", "").replace("}", ""),
            queryParams: '?$select=decimalsymbol,numberseparator',
            async: false
        });

"code":"","message":"Resource not found for the segment 'usersettingscollections'."

I think that entity plural name usersettingscollections is wrong. Should be usersettingscollection
Regards
OldCat

Hi @fvakiliev,
Yes, you're right, the name of the entity set is usersettingscollection, without the pending s.
The library uses the default rules for building collection names from entity names, unfortunately CRM chose to use different collection names for some special entities.
For those exceptions, don't pass the entityName, and use overriddenSetName instead, as described here:
var userSettings = WebApiClient.Retrieve({
            overriddenSetName: "usersettingscollection",
            entityId: currentUser.replace("{", "").replace("}", ""),
            queryParams: '?$select=decimalsymbol,numberseparator',
            async: false
        });

In addition to that: Please remember that using async: false is discouraged if you don't really need to, so if possible in any way, please use the promise style.

Thanks!


NTR: positive regulation of androgen receptor signaling pathway

Please provide as much information as you can:

Suggested term label:
positive regulation of androgen receptor signaling pathway

Definition (free text)
Any process that activates or increases the frequency, rate or extent of the activity of any androgen receptor signaling pathway.

Reference, in format PMID:#######
PMID:29057879

Gene product name and ID to be annotated to this term
Foxp1 = MGI:1914004
Shq1 = MGI:1919421

Parent term(s)
regulation of androgen receptor signaling pathway - GO:0060765

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

+[Term]
+id: GO:0160207
+name: positive regulation of androgen receptor signaling pathway
+namespace: biological_process
+def: "Any process that activates or increases the frequency, rate or extent of androgen receptor signaling." [PMID:29057879]
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: positively_regulates GO:0030521 ! androgen receptor signaling pathway
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/28728" xsd:anyURI
+created_by: rynl
+creation_date: 2024-08-21T22:03:38Z


ARROW-16567: [Doc][Python] Sphinx Copybutton should ignore IPython prompt text

The CI error is not connected
/opt/conda/envs/arrow/lib/python3.9/site-packages/pyarrow/compute.py:201: RuntimeWarning: Python binding for RankOptions not exposed
  warnings.warn("Python binding for {} not exposed"

and will be removed when https://github.com/apache/arrow/pull/13327 is merged.

Note the actual CI error is:
PR01: Parameters {'thrift_string_size_limit', 'thrift_container_size_limit'} not documented

and should be fixed if you rebase from master (it's my fault, sorry).

Oh, thanks for the info! Now I get why it is happening elsewhere also =)
Yes, tested it - have it recorded! :D


Error when logging on the second time

I followed the setup instructions and added my user_id and url and the first login works (almost) great

Most of the rooms are encrypted, after a bit of a hassle I managed to get iamb verified and yet all rooms were still indicating that the messages were encrypted...
Even more problematic, when calling iamb a second time, I get the following error:
Matrix client error: the server returned an error: expected value at line 1 column 1

This looks similar to the issue in #53, where the sync endpoint wasn't returning JSON. Could you try running curl to see what it's returning?
curl --http1.1 --get -i https://homeserver.tld/_matrix/client/v3/sync

You want to replace homeserver.tld with the domain of your homeserver.

I had the same issue, fixed it by replacing the "url" field to matrix.homeserver.tld instead of homeserver.tld

I was having the OP issue on my own dendrite server. I was able to connect to it by specifying the url as "https://matrix.homeserver.tld" in the ~/.config/iamb/config.json file.

I figured the issue:
Our server is hosted by Element but the link that was given to me contained an indirection. So changing server from:
chat.our.server to ourserver.ems.host solved the issue.


(Re-)introduces testing capabilities via 'make test' and CircleCI

Introduces ability to run tests in an appropriate Docker container built from Dockerfile.test.
Tests can be startet via make test, which has also been set as test command for CircleCI.

There seems to be an issue with Docker 1.8.2 (which is provided in the currently used, Ubuntu 12.04-based, CircleCI image, see here) and the specification of a certain Dockerfile to use for build, like in this case Dockerfile.test.
See e.g. here: https://github.com/docker/docker/issues/16339

Due to the limitation of Docker 1.8 in the CircleCI build environment it seem impossible at the moment to implement a reasonable testing approach. Will keep this branch and hope for an Update to Ubuntu 14.04 with Docker 1.9 in the CircleCI build environment.

@rene-mt Take a look at this https://discuss.circleci.com/t/docker-1-10-0-is-available-beta/2100

Yeah, well... this kind of worked. Thx @mattaitchison for the hint.
However: There are lots of error messages about Docker not being able to remove intermediate containers and the like, as also mentioned in the thread you put me on. And the evaluation of the build argument does not to work properly, so test are also executed during build.
As I read at https://discuss.circleci.com/t/request-docker-1-12/5120/12, support for Docker 1.12 seems to be on the way. May make sense to wait for it to give this another shot.

@mattaitchison Thing ist that due to the Docker version in CircleCI it is not possible to specify a certain Dockerfile to use, which also includes the Dockerfile.dev. Means: if I change this to the dev image the tests won't run in CircleCI.
After all the Docker support in CircleCI is quite brittle in CircleCI at the moment. Therefore I think it makes sense to wait until they upgrade to Docker 1.12 to bring this merge in.

You can upgrade the circleci environment to docker 1.10 which I believe supports named dockerfiles. Check this link for details: https://discuss.circleci.com/t/docker-1-10-0-is-available-beta/2100
$ ./docker-1.10.0-circleci build --help | grep file
  -f, --file                      Name of the Dockerfile (Default is 'PATH/Dockerfile')

@michaelshobbs I did, but as you see in my comment above this unfortunately leads to other problems.

Gah! Apologies as I missed that one and (ha! @mattaitchison linked the same article.) That's what I get for reading GH issues before my morning coffee. 😄

Before coffee!? Man, that's hard :)


Could both build and release definition use the same agent or each must use different agent?

This is my first time working with CI/CD using VSTS so please bare with me.
I'm currently creating a release definition for our project and I'm stuck with this problem, could both build and release definition use the same agent if yes, then how? If no, what are other options to do this?

Agents are in pools, and queues map to pools. https://www.visualstudio.com/en-us/docs/build/concepts/agents/pools-queues

...sorry, i mean to say "yes" both build and release definitions can use the same agent. As long as you have permission, you can choose the same queue either a build definition or a release definition.

@ericsciple Thanks for the response. I've already got it working :)


Skill fails when no Dockerfile is present

configuration is "all repos" and everything else default
name: docker-build-skill
version: 1.1.3-38
upgrade_policy: latest_compatible_release
namespace: atomist
configurations:
- name: Docker Build
  enabled: true
  parameters:
  - name: repos
    value: {}
  resourceProviders:
  - name: docker_push_registry
    selectedResourceProviders:
    - id: AEIB5886C_c534d873-3053-4e66-85d0-4d3697ad60cc

On repos, that do not contain a Dockerfile, the skill fails and the mapped channel gets a message:

Example repo is:  https://github.com/slimslender/nextjs-blog
I expect the skill to run for this but I think it should not fail.

Recently manually upgraded this skill to 1.1.3-38

There's currently no way for us to do this because we can't use the kaniko debug image to test if a file exists before running the build. We are hitting https://github.com/containerd/containerd/issues/4182. Once this is resolved and available in our GKE cluster, we can revisit this issue.
Ideally, the skill wouldn't even start when the file doesn't exist in the repository. Much like what we previously had with push tests.
For now the work-around is to disable the repo with the repo filter.

For now, I've changed the skill to not send a chat message and don't set a GitHub check if the Dockerfile specified doesn't exist. The skill itself will be still be marked as failed in the skill logs.

I'll also create a corresponding requirement on Dockerfile "push rules" because I think this is pretty good justification for prioritizing that work.

have upgraded to 1.1.3-45 and can confirm that slack messages are no longer being sent.


[nrf noup] boards: thingy53_nrf5340: Add common partition map

Change introduces common static Partition Manager configuration.
Jira: NCSDK-18033

[nrf noup] exception granted for the following reasons:

it's adding NCS specific files which doesn't exists upstream, hence no risk of merge conflicts
it's extending board functionality which cannot be done oot, for example in sdk-nrf repo.


doc: document best practices for main.c suite declaration

With the introduction of --list-tests to sanitycheck, a few rules have
been added to how to declare test suites.
Related to #7289
Signed-off-by: Inaky Perez-Gonzalez<EMAIL_ADDRESS>

Codecov Report

Merging #7332 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7332   +/-   ##
=======================================
  Coverage   55.09%   55.09%
=======================================
  Files         474      474
  Lines       51786    51786
  Branches     9937     9937
=======================================
  Hits        28530    28530
  Misses      19304    19304
  Partials     3952     3952

Continue to review full report at Codecov.

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

@dbkinder implemented all the suggestions and pushed the changes; please review?


Bug: 'Tagging Vocabularies' are not used at all

If you initialize Annotorious with the TAG widget and you add 'Tagging Vocabularies' like described here: https://annotorious.github.io/guides/configuring-the-editor , you expect them to see them back somewhere. This does not seem to happen.
See Codepen: https://codepen.io/r-w-c/pen/abPRBbW
Reproduce:
Initialize Annotorious like this:
var anno = Annotorious.init({
  image: 'hallstatt',
  widgets: [{
    widget: 'TAG',
    vocabulary: [
      { label: 'Place', uri: 'http://www.example.com/ontology/place' },
      { label: 'Person', uri: 'http://www.example.com/ontology/person' },
      { label: 'Event', uri: 'http://www.example.com/ontology/event' }
    ]
  }]
});

Excepted result: The defined uri are used somewhere.
Actual result: The defined uri are used nowhere.

The URIs are getting properly serialized to the annotations. E.g.:
"body": [
    {
      "type": "SpecificResource",
      "purpose": "tagging",
      "source": {
        "id": "https://www.example.com/ontology/FP",
        "label": "FP"
      }
    }
  ]

You can see this if you add an annotation handler (anno.on('createAnnotation')).

Aha, expected something else. Thanks


docs(format): clarify some parts of header file

@zeroshade opinions here?

Definitely worthwhile to be explicit about expecting a zero-initialized struct

Thanks Will!


Create dynamic defaults for service creation - fix #101

Fixes #101
Tried to keep it simple.
When the function needs to raise an error, I followed the existing error patterns as a reference.
Added simple unit tests.

Hello, and thanks for your contribution!
I believe we should call your new function after parsePorts and parseRoutes. If you call it before, ports and routes are not yet validated.
With your current proposal, setting the invalid route :abcdef raises an error because the port is invalid.
koyeb service create test --docker nginx --app test --routes :abcdef
ports: abcdef
❌ Error while configuring the service: unable to parse the port "abcdef"

🔎 Additional details
Ports must be specified as PORT[:PROTOCOL]
PORT must be a valid port number (e.g. 80)
PROTOCOL must be either "http" or "http2". It can be omitted, in which case it defaults to "http"
To remove a port from the service, prefix it with '!', e.g. '!80'

🏥 How to solve the issue?
Fix the port and try again

Instead, I think we should:
1/ remove setting the default port in parsePorts
	// For new "web" services, if no port is specified, add the default port
	if len(newPorts) == 0 && type_ == koyeb.DEPLOYMENTDEFINITIONTYPE_WEB {
		port := koyeb.NewDeploymentPortWithDefaults()
		port.SetPort(80)
		port.SetProtocol("http")
		return []koyeb.DeploymentPort{*port}, nil
	}

2/ remove setting the default route in parseRoutes
	// For new "web" services, if no route is specified, add the default route
	if len(newRoutes) == 0 && type_ == koyeb.DEPLOYMENTDEFINITIONTYPE_WEB {
		route := koyeb.NewDeploymentRouteWithDefaults()
		route.SetPath("/")
		route.SetPort(80)
		return []koyeb.DeploymentRoute{*route}, nil
	}

3/ In a new function setDefaultPortsAndRoutes, called after setPorts and setRoutes, set the defaults.
What do you think?

Lack of proper testing / understanding of the code from my side.
Your approach sounds good to me. I'm on it !

Just updated my PR.
I tend to comment a lot my code, feel free to delete what you think is unecessary.
If there is any mistakes / improvments to be made, I'm happy to hear about it.
The unit tests as I wrote them are only testing the func setDefaultPortsAndRoutes. I believe that it has its limits (as we've seen it with my first PR) and I was thinking about testing the parent function parseServiceDefinitionFlags but I didn't want to overstep.
To do so, I think that it could be interesting to have standerdized error variables or functions within the codebase: This could not only improve the readability of error handling but also make it easier to compare expected errors in unit tests.
Instead of returning the full error in the code, like in this example:
// Two or more ports are set
if len(currentPorts) > 1 {
	return &errors.CLIError{
		What: "Error while configuring the service",
		Why:  `your service has two or more ports set but no matching routes`,
		Additional: []string{
			`Routes must be specified as PATH[:PORT]`,
			`PATH is the route to expose (e.g. / or /foo)`,
			`PORT must be a valid port number configured with the --ports flag. It can be omitted, in which case it defaults to "80"`,
		},
		Orig:     nil,
		Solution: "Set the routes and try again",
	}
}

It would look something like that:
// Two or more ports are set
if len(currentPorts) > 1 {
	return ErrTwoPortsNoRoutes
}

Which would be useful in the unit tests when an error is supposed to be raised with something like:
expectedError := ErrTwoPortsNoRoutes

if assert.Error(t, err) {
     assert.Equal(t, expectedError, err)
}

I don't know if this approach makes sense. Do you think that it's a good idea or did you have something else in mind ?

Regarding the errors, you are right, it would be better. If you are willing to, you can make another pull request to address the issue.
Regarding the PR, it looks good to me.
I just added two changes:

rename setDefaultPort and setDefaultRoute:

-               definition.SetPorts(setDefaultPort(80))
-               definition.SetRoutes(setDefaultRoute(80))
+               definition.SetPorts(getDeploymentPort(80))
+               definition.SetRoutes(getDeploymentRoute(80))

rewrite the error messages

-                                       `Routes must be specified as PATH[:PORT]`,
-                                       `PATH is the route to expose (e.g. / or /foo)`,
-                                       `PORT must be a valid port number configured with the --ports flag. It can be omitted, in which case it defaults to "80"`,
+                                       "For each port, you must specify a matching route with the --routes flag",

-                                       `Ports must be specified as PORT[:PROTOCOL]`,
-                                       `PORT must be a valid port number (e.g. 80)`,
-                                       `PROTOCOL must be either "http" or "http2". It can be omitted, in which case it defaults to "http"`,
-                                       `To remove a port from the service, prefix it with '!', e.g. '!80'`,
+                                       "For each route, you must specify a matching port with the --ports flag",

thanks a lot!


CovariantEqualsChecker still triggers for scala.Any

The following code triggers CovariantEqualsChecker:
override def equals(o: scala.Any) = ???

While the following does not:
override def equals(o: Any) = ???

It's a weird corner case, since most sane people don't write scala.Any, but apparently I'm not sane.

Fixed by #282


set the polling mode based on path type to resolve wsl2 file system issue.

Description

This PR resolves #159.
In watcher.js:415, changed the code like following to save and open collection on wsl2 fs.
usePolling: watchPath.startsWith("\\\\") ? true : false,

after changing the code above, the bruno works fine. (see the following picture)

Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

FYI even with 1.5.1 I still face the same issue:
Opening Bruno from windows and loading queries stored on WSL shows only the folders.
Is there any option to activate in 1.5.1 to have the fix properly working or activated ?

OK I got it, I have 2 ways to access to my WSL files:
\\wsl.localhost\Ubuntu-20.04
W:\

1.5.1 works fine if I pint to content in "\wsl.localhost\Ubuntu-20.04"
It fails if path is in "W:"
It's possible that the second path (W:) is a customization I made in the past, I don't remember. If it's the case, you can ignore my comment.
If it's a default WSL setup, that kind of path might be necessary to be supported


[GPU Logic Bug] SELECT DISTINCT  FROM  Brings Errors

Describe:
 SELECT DISTINCT <column> FROM <table> brings different results, when using CPU-only configurations and GPU-used configurations.
SQL with CPU-only Config:
CREATE TABLE t1(c0 integer , SHARD KEY(c0)) WITH (shard_count=28);
INSERT INTO t1(c0) VALUES(1);
INSERT INTO t1(c0) VALUES(2);
ALTER SESSION SET EXECUTOR_DEVICE='CPU';
SELECT DISTINCT - (t1.c0) FROM t1;

Result:
EXPR$0
-2
-1

SQL with GPU-used Config:
ALTER SESSION SET EXECUTOR_DEVICE='GPU';
SELECT DISTINCT - (t1.c0) FROM t1;

Result:
EXPR$0
-1
-2

Environment:
Docker Deployment
https://hub.docker.com/layers/heavyai/heavyai-ee-cuda/latest/images/sha256-5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f?context=explore
Docker DIGEST: sha256:5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f
HeavyDB Version: 7.1.0-20230821-eae9ec17da
HeavyDB license: Free Edition

Hi @qwebug,
HeavyDB v8.0.1 has fixed this issue.
Thanks for your report.


Godot 4.1.3: The variable type is being inferred from a Variant value

Godot version
v4.1.3.stable
Issue description
Recieved a parse error in the console upon importing the plugin into Godot 4.1.3 that reads, "The variable type is being inferred from a Variant value, so it will be typed as Variant". This happens on line 252 in wiggle_bone.gd. Basically Godot doesn't know how to type cast it. To fix, simply apply the type.
var h := max(0.0, k - abs(a - b))
to
var h: float = max(0.0, k - abs(a - b))
Steps to reproduce
Import the plugin into 4.1.3.

Strangely, I couldn't reproduce this error in any Godot version. Though, I once got it too on another occasion. I'll push a new version which should prevent this in any case. Thanks!


Hardware Notification:Depth stream start failure,1.70161e+12,Error,Hardware Error

Do you still experiene the depth stream start failure error if you add initial_reset:=true to your ROS wrapper launch instruction in order to reset the camer at launch, please?

Thanks for you useful and professional guidance !This problem has solved by following you method.


{resource-mover} HTML tag isn't allowed in example syntax

Describe the bug
HTML tags in source code are causing build warnings in MicrosoftDocs/azure-docs-cli.
This is the same issue as these GitHub issues.
Related command
az resource-mover
Errors
2017-03-09-profile/docs-ref-autogen/resource-mover/move-collection.yml
Line 53, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 105, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 147, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 206, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 255, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 307, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 343, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 372, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 404, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 463, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 505, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 535, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 593, Column 93: [Warning: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 596, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 599, Column 116: [Warning: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 661, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
2017-03-09-profile/docs-ref-autogen/resource-mover/move-resource.yml
Line 63, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 109, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 143, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 184, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 238, Column 111: [Warning: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Issue script & Debug output
2017-03-09-profile/docs-ref-autogen/resource-mover/move-collection.yml
2017-03-09-profile/docs-ref-autogen/resource-mover/move-resource.yml
Expected behavior
N/A
Environment Summary
Azure CLI 2.53.0
Additional context
No response

Thank you for opening this issue, we will look into it.


cmd: fix raft engine ctl

Signed-off-by: tabokie<EMAIL_ADDRESS>What is changed and how it works?
Issue Number: Ref #11119
What's Changed:
None

Related changes
Check List

No code

Release note
None

Ping @Connor1996 @5kbpers

/merge


Chromedp stops responding over remote desktop connection

I have an odd issue and I'm not sure if you would know anything about it. I am using chromedp to automate some tasks, which works well, except when I run my program on my server. It seems that when I am NOT connected to a remote desktop session, the program essentially halts. However, if I reconnect and observe the chromedp instances, everything seems to respond again. Is this something you've had experience with? Any suggestions on how to fix it?

Got it resolved. Turns out unactivated copies of windows stops running programs when the session ends.


Reload controller after installing an app

When installing an app in the app center, all files get copied.
However if the app comes with a python controller that can't be loaded after Flasks initialization so we can't get it to work.
We could simply restart the service with systemctl restart tooloop-settings-server but when do we do it?
The install process is invoked by a REST call from the browser. That expects an HTTP response (200 OK or so).
The route handler in tooloop-settings-server.py is therefor waiting for a response from appcenter_controller.py.
So if we would relaunche the service in the install method we would stop the reply-chain. The last member in that chain is the browser but I certainly don't want the UI layer to be responsible for a step in the install process.
Is there a way to simply re-init flask? Or is there a way to send a response and then restart the service anyway?

we can probably do this using the postinst script in the Debian package

done in new Tooloop/Tooloop-Control


Fix over agressive async delegation

When return() is called on a generator that is in the process of yield* delegation, it should not only call return() on the delegated iterable, but should also exit the current generator. The __asyncDelegator processes each call in two steps: first it indicates to the outer generator that it should await the result of a call to next, throw, or return, then it returns the result of that await operation in a tick/tock fashion.
When the delegator "ticks", it returns an IteratorResult that looks like: { value: ["await", result], done: false }. The outer async generator will handle the await and call back into the delegator ("tock"). When the delegator "tocks", it processes the iterator result and either exits with a done: true or yields with a { value: ["yield", value], done: false }.
The problem lies in the fact that when the delegator "ticks" as part of a call to return(), it returns done: false. This informs the underlying generator runtime that the delegator did not actually close, so it continues processing. This change now unconditionally causes the delegator to return by always returning done: true when calling return() on an async delegator.
This change also awaits the result of an async delegator (the x in x = yield* y) to more closely align with the async iteration proposal.
Fixes #15471

I don't feel like I'm qualified to review this given my current knowledge of async implementation. Can you walk me through the PR in person and explain how everything works along the way?

@rbuckton can you port this change to release-2.3

@mhegazy this is now in release-2.3


bug: crash on init

$ fleek init
 INFO  initializing fleek
Git Config - enter your email address: MYEMAILWASHERE
Git Config - enter your full name: MYNAMEWASHERE
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x9a8718]

goroutine 1 [running]:
github.com/ublue-os/fleek/nix.(*Flake).Init(0x0, 0x0?)
	/app/nix/flake.go:50 +0x38
github.com/ublue-os/fleek/cmd.initialize(0xc00028ac00?, {0xaca486?, 0x0?, 0x0?})
	/app/cmd/init.go:143 +0xb77
github.com/spf13/cobra.(*Command).execute(0xc00028ac00, {0x1037200, 0x0, 0x0})
	/root/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920 +0x847
github.com/spf13/cobra.(*Command).ExecuteC(0xc00028a000)
	/root/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
	/root/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
github.com/vanilla-os/orchid/cmdr.(*App).Run(0xc00028a000?)
	/root/go/pkg/mod/github.com/vanilla-os/orchid@v0.4.0/cmdr/app.go:97 +0x78
main.main()
	/app/main.go:56 +0xfc5

This was on newest uBlue Kinoite (custom) as of March 22, 9pm EDT.
$ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-unverified-registry:ghcr.io/bsherman/kinoite-custom:37
                   Digest: sha256:84bbd3540bf28c5c1909dfe4d524507f51610e9cd6aee5fd9a4b1d6e381d627c
                  Version: main (2023-03-23T01:11:06Z)
          LayeredPackages: langpacks-en

I didn't think it would matter, but I also tested on a different machine that's Silverblue, not Kinoite. Same err.

fixed by #54


Enable ITREX v1.4.2 for specific torch version

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


SPNEGO: Support mutual authentication

If an output token is generated, it should be base64 encoded and added
to the HTTP response as a WWW-Authenticate header. This allows the
client to authenticate the server in the case where it has requested
mutual authentication.
From RFC4559 (SPNEGO-based Kerberos and NTLM HTTP Authentication in
Microsoft Windows) section 4.1:
A status code 200 status response can also carry a
"WWW-Authenticate" response header containing the final leg of an
authentication.  In this case, the gssapi-data will be present.
Before using the contents of the response, the gssapi-data should be
processed by gss_init_security_context to determine the state of the
security context.  If this function indicates success, the response
can be used by the application.  Otherwise, an appropriate action,
based on the authentication status, should be taken.

For example, the authentication could have failed on the final leg
if mutual authentication was requested and the server was not able
to prove its identity.  In this case, the returned results are
suspect. It is not always possible to mutually authenticate the
server before the HTTP operation.  POST methods are in this
category.

I'll note, this is one of my first golang contributions, so I hope this is acceptable.

Coverage remained the same at 30.151% when pulling 328cacf891e877533b8b5bcf8eeba3b8e785c45b on mkomitee:features/spnego-mutual-authentication into 5fb4217df13b8e6878046fe1e5c10e560e1b86dc on apcera:master.

The fact that a fix is needed is correct.  Although this isn't part of the code I wrote, it looks like the fix should just be:
if outputToken.Length() > 0 {
  AddSPNEGONegotiate(outHeader, challengeHeader, outputToken)
}

with no need for added header inclusion.  As it stands, this patch will break proxy authentication.
Does this change handle all GSS_S_CONTINUED_NEEDED scenarios?  If so, then a FIXME can be removed too.


[Feature Request] Chaining/Reuse of Flows

Is your feature request related to a problem? Please describe.
The problem that we're running up against is flow complexity and reuse. We have situations where we want to be able to build a flow to perform a specific task, but want to reuse this functionality in several other flows as well. Additionally we're quickly running into the issue where we have a complicated flow that is difficult to comprehend, and encapsulating this complexity into a separate flow component would simplify our higher level flows
Describe the solution you'd like
I would like a capability to call one flow from another flow, treating the called flow as if it is a tool or functionality similar to other node types in the flow.
This would be a new node type in the flow.diag.yaml specification similar to the "python", "llm", and "prompt" node types. This node type would reference a separate flow similar to how a python script is called, treating it as a function call.
Describe alternatives you've considered

In a similar vein I've considered whether an API call to a deployed endpoint would be sufficient, however this has the drawback of requiring a pre-deployed endpoint in order to be functional. This seems like a separate functionality as well with different maintenance costs and patterns.

Building a python tool wrapper to call the flow. There's an existing (preview) functionality to call a flow as a python function, however this appears more suited for python contexts where we want to load a flow. This seems like it could be an alternative where we could build a promptflow "tool" in python which just calls the functionality to load the promptflow definition and call it, however this would suffer from additional runtime overhead costs (having to run and parse the flow each time the "parent" flow is called rather than just integrating the flow contents directly), and a less seamless integration.

Additional context
I'm unclear if there is already a supported solution for code/flow reuse. There seems to be something for "load a flow as a python function" but this isn't exactly what I'm looking to do.
Here's an example of the type of thing I would want to do (purely for example - not trying to do this specifically):
Let's say we want to be able to assist with writing jokes and comedy.
There are several things that we want to be able to do, including (1) checking any jokes that we come up with against known material so that we're hopefully not duplicating another comedian's jokes on accident (2) have an LLM propose a new joke (3) check for the "cleanliness" of a joke (don't want to be writing R-rated jokes for a "PG" crowd) (4) help compose a comedy set.
In almost all cases we're going to want to include check (1) and probably (3). These could be standalone capabilities, but they're also likely to be sub-components if we're asking the LLM to write a new joke or come up with an entire themed set or series of jokes.

When performing a more complex task like writing an entire set we should be able to call the individual flows rather than needing to duplicate the functionality over and over:

I also have a use case when I run a standard flow first and then a feed the outputs (including some intermediate outputs) to the chat flow.


Cannot execute "dotnet publish" command on MySqlEfCore project

I get an error when I execute this command. I have tested on .netcoreapp 2.0 as well as 1.1. Is this a kind of VS error? I cannot even build the project using VS 2017. I have pulled out the dev branch for this development.

Without building the project I have tried out to push to the cloud foundry by using "cf push" and still get the common error as BuildpackCompileFailed.

@Isuama
This is a dotnet tooling "issue" ..  you can no longer publish to a directory that is a directly in the projects root... (i.e. -o publish).  Once that directory exists (i.e. publish) .. the next time you build it will screw up the build...  So 'rmdir /s /q publish'   and then publish again...
Your best to just 'dotnet publish -f xxx -r yyy' ... and use the default publish output directory the tooling selects (i.e. bin\Debug\netcoreapp2.0\ubuntu.14.04-x64\publish) ...  then cf push -f manifest.yml  -p bin..... "
Hope that helps
Dave

Yes that's correct. But in my case I have gone through Steeltoe doc to run those commands and pulled new version from dev branch which made conflict on netcoreapp1.1 and 2.0. I just removed all files and pulled from the master branch and it is working perfectly. Thanks mate


Admin 5.x

https://github.com/instalator/ioBroker.kodi/pull/66

I am using 2.0.5 of the adapter and that annoying message is filling up my logs every 2 seconds. Maybe it is time to fix this bug once and for all.

https://github.com/instalator/ioBroker.kodi/blob/dce1c0688ecdded0b0926595a371763bb474a380/kodi.js#L458


RenameKey funcionality

Added renameKey feature to rename a key value found in a map path to a new key value. This gratly increases the usability of the library. Unit tests were also extended to cover the new feature.

Hi,
Is this pull request going to be included? Added a lot of features, and also fixed a pretty bad bug while removing array items using the library.

Yes I will include it.
Sent from my iPhone

On 19 jun 2015, at 12:14, Tamas Adam<EMAIL_ADDRESS>wrote:
Hi,
Is this pull request going to be included? Added a lot of features, and also fixed a pretty bad bug while removing array items using the library.
—
Reply to this email directly or view it on GitHub.

Hi. Could you merge this pull request? It will save me (and probably others) a lot of work.

@kallestenflo Can You please merge this pull request? Apparently people would like to use the added features and fixes. Also we are closing our project soon, it would be nice to use the official master branch instead of a private forked version.

I can't promise a release date. This project is developed on my spare time and I don't have a lot of that at the moment.
I need to look into your change in AbstractJsonProvider. Is this the bug you mention in previous comment? This will alter the behavior of all Map based JsonProviders.

+1 for this functionality. I had to use this in one of our latest projects and had to write custom code for this to rename a key.

Sure, I know. Just it is on hold for quite a long time ago.
Yes, the AbstractJsonProvider modification is related to commit "Fix for list element removal if multiple path elements match" (48544d1), which was missing a tes file (json-path/src/test/resources/json_array_multiple_delete.json), that's why another commit was made (0042ae9).

@atomcat1978 I made some modifications to your commit. One thing I did was reverting your change in AbstractJsonProvider.removeProperty(...). You say there is bug in this method, could you provide a test that triggers this?

Thanks. When do you plan to release the next version which contains the rename feature?

Hi @kallestenflo ,
I've checked the AbstractJsonProvider.removeProperty affair again. The way how the delete operation in case of arrays is handled has beed updated. Now the operations are sorted based on the array index of the delete operation. This way the functionality works totally ok, there is no need to update the AbstractJsonProvider.removeProperty method any more. Thanks for merging in. Do You have an estimated date for the next release?

Perfect!
I'm trying to fix all issues tagged with BUG. #141 is in progress but it requires a rewrite that is big. I hope to complete it this week and release the week after. This is not a promise.

Thanks for the great work in advance!

I think I will rename convert(ValueConverter vc) to map(Mapper m). Any thoughts on this? This is the last thing I will do before release.
Appreciate your contributions and input.

You are welcome.
Thanks for the update. I think, Map is and MapFunction are ok, and easy to understand.
I'll try to move over our project to the official latest release:) Thanks for the new release!


roll statefulsets on configmap updates

This adds annotations for pod spec in statefulset for automatic rollout on config map updates per helm tip.

This change is

 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.

@t3mi I tested this PR and found that the solution does not work, likely because the mount paths and file names are incorrect, i.e. /alpha/configs.yaml and /zero/configs.yaml.
If you would like to update this, the following items are needed:

the mount path is /dgraph/config
the file name can be json or yaml, depending what the user has for the key of alpha.configFile[0] and zero.configFile[0].
there needs to be a boolean, e.g. alpha.configChecksum: true that enables or disables this feature.


Will this library work in a plain old Java server application?

In the lack of suitable BlueSky SDKs, I ended up checking yours out. I added it as a Maven dependency to Quarkus app I am working on, but it looks like I am not able to use it, even though Maven would fetch it without any issues.

@preslavrachev
Probably the same problem as https://github.com/uakihir0/kbsky/issues/109 . Try using core-jvm stream-jvm.

Looks like this worked, thanks!
Just a heads up: I added a PR with a few small additions to the documentation: https://github.com/uakihir0/kbsky/pull/112


linux: fix epoll_pwait() regression with < 2.6.19 (v0.10)

Linux before kernel 2.6.19 does not support epoll_pwait().  Due to a
logic error in commit 2daf944 ("unix: add flag for blocking SIGPROF
during poll"), the fallback path for ENOSYS was not taken.
This commit also adds epoll_pwait() emulation using pthread_sigmask().
The block/unblock operations are not atomic but that is fine for our
particular use case, to wit, sleep through SIGPROF signals.
This is a back-port of commit 67bb2b5 from the v1.x branch.

Wups, R=@saghul.

LGTM :+1:


fix encoding to avoid duplicated references

fix encoding to avoid duplicated references in file

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Added an Azure DevOps Pipeline example using this toolkit

I created this first version using Azure DevOps Pipelines end to end.
1 - Added a reference to AzDOExample.md on main readme.md
2 - Reference on how to extract API's using APIM DevOps Toolkit
3 - How to create a Build Pipeline to add the ARM json files to the AzDO artifacts
4 - How to create a 2 environments Release Pipeline with the correct dependencies between ARM json files

Architecture.png has transparency and doesn't display correctly on GitHub with dark theme. Needs white background.

Already looks like it is done, so closing.


Add datadog-agentless-scanner package

What does this PR do?
This change adds the datadog-agentless-scanner package.
This package depends on the datadog-agent package
and only contains the agentless-scanner software and init scripts.
This package installs files into the /opt/datadog/agentless-scanner directory.
This package targets the following platforms:

Debian / Ubuntu amd64
Debian / Ubuntu arm64
RHEL / Fedora amd64
RHEL / Fedora arm64
SLES / openSUSE amd64

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge

/merge -c

/merge


Minor: fixed transformed state in UDF Simplify

Which issue does this PR close?
Follow on to https://github.com/apache/arrow-datafusion/pull/9304
Rationale for this change
@Omega359  pointed out this issue on https://github.com/apache/arrow-datafusion/pull/9304#discussion_r1513764598
What changes are included in this PR?
Fix logic inversion bug.
Are these changes tested?
No test changes due to rationale explained on https://github.com/apache/arrow-datafusion/pull/9304#discussion_r1515004035
Are there any user-facing changes?
No

Thanks.

Thank you for the review @jayzhan211


ServiceDispatchHandler: inline #addPeerIndex

Now that we have the helper functions addIndexEntry and deleteIndexEntry,
it's not that much code anymore.
Further, inlining it leads to simpler code in #116, since otherwise the
temptation is to add yet another argument (4th) to #addPeerIndex to control
whether or not we should add/delete to/from the new secondary indices.
r @raynos @rf

#fierce merging this since it's an isomorphic change, to unblock review of #116