Bot Teams Authentication sample not working as expected

Sample Used : samples/bot-teams-authentication/python
I have run this sample and this doesn't seem to work properly.
Issue :

After Sign In prompt is shown, and I complete the login process on the popup, I get this message.

After this, all further messages (except for logout) do not send back any response, nor do i get the expected "Do you want to see your token?" screen.

After login error of (1) occurs, only Logout functionality works. But once logout completes, attempts to log in creates leads to issue described (1).

These are the settings used on Azure Bot Service OAuth connection I am using:

Thank you for reporting this, we will check this and get back to you.

We are able to repro this issue, we have informed sample team regarding the same. We will keep you posted on the updates.

Hi @Meghana-MSFT , any updates on this issue? We are currently blocked for a lot of features dependent on Authentication.

We raised a bug for the same, we will keep you posted on the updates. Thank you.

July 22 2024, is there any update on this? It work on web version but desktop  app not working at all

Apologies for the delay, we tested the sample (https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-teams-authentication/python) in Teams web & Desktop. It is working fine.

Hi @Meghana-MSFT, I am facing the same issue.
It is not working as expected. I tried the same manifest and bot service settings for python and nodejs samples. nodejs works perfectly fine, while python sample is not working. Either it is just stay silent or have an Something went wrong or Unable to reach app error on the Sign In. Although python sample works fine in the Bot Framework Emulator.


FPS drops in scroll example

See here:
https://user-images.githubusercontent.com/27787342/202433627-bf1ace81-6270-49df-9b36-8f013b5c2dfb.mov
Running on M1 Mac in release mode.
What's the performance bottleneck here? How can this be fixed?

The current state isn't necessarily representative; this uses an old version of druid-shell, for example. That is done to create a minimum compiling state.
We can revisit this once #1 lands.

What @DJMcNab said. You want to be putting a lot more attention into #1, though it doesn't do anything interesting yet.
There are, however, a couple more things to say about the scroll example in the repo. One, it is slow on purpose (the list element computes an expensive hash), to compare against an equivalent SwiftUI program. Second, if you're running it on mac, it is running into a performance problem (expensive font creation) which has been fixed in later piet but not yet released. When I develop, it's locally patched. This is why we need to get the Druid 0.8 release done, and also why https://github.com/raphlinus/raphlinus.github.io/issues/74 hasn't been published yet after many months.

Does that mean that Piet's release cycle is tied to Druid's?

This may be the same thing I ran in to, caused by UI and computation sharing the same thread pool. I did modify the example to use a separate thread pool and cancellation.

Does that mean that Piet's release cycle is tied to Druid's?

Technically doing a Piet release alone (without also releasing Druid) would improve the performance of the scrolling example. But I think the releases are highly related, as any applications built on Druid would suffer from the performance issue until the release is done. This is all somewhat irrelevant to Xilem though.
Regarding cancellation, this is a complex question. I'm pretty sure there's a discussion of it in Zulip, and it's part of my plans for the blog post to explain it reasonably well.

The scroll example no longer exists. Additionally, we now use vello as the backend instead of piet.
Thanks for the report!


support of machine learning library

because it is much more efficient to use other language(ie. python) to write some machine learning code on top of some library(ie. tensorflow), but the official AIIDE tournament machine seems do not support such python library.
so I has several questions:

do you have plan to do such things in future?
is the submitted AI folder has space limitation? for example, can i put a pre-config python version in the AI folder which may occupy about 30m.
other recommended alternative?

@davechurchill @richard-kelly
Thanks

Nothing stops you from running machine learning software on any of the client machines. In fact, we supported it for the tournament this year - we just don't include those libraries with the tournament software since it would be too difficult to keep track of all the different libraries. Once you install the libraries on the machine, just modify the bot launch batch file to run whatever python you need on the client machine and it should work just fine.

ok，do you mean I should submit the bot with a  pre-configured python version which can install on the tournament machine only once?
By the way, which bot this year used this pre-install function?

You write the code - we will provide the libraries. So you would say "this program requires python 3.6.x and tensorflow installed" and we will install those libraries

oh，that's great!
Thanks

If you look at the 'compete' page on the website: http://www.cs.mun.ca/~dchurchill/starcraftaicomp/compete.shtml
It says your submission must include:
"A readme file containing compilation instructions, including any environment variables or external libraries (boost, etc) used in your bot, with links to the official download pages for those libraries (we will have the latest version of boost and all versions of BWAPI installed)"
So as long as you tell us with your submission which libraries or software packages you need, and you give us an official release version to run, it's fine.


Ignored websocket calls to the rest API

Hi,
I tried to make some calls to a rest API via websocket (using a proxy) and the calls are not triggered.
Here you can find the application (rest + websocket classes): reproducer.zip.
Thanks,
Mihai

Put your example in a gist or in github or inline.

This is a common feature and it works. We want to put this in git or gist so we can help. Closing for now.

I fixed this.


Implementing Finding Factorial in O(logN)

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I will write a c++ code to show implementation of factorial program in O(logN) time.
Use Case
For all positive integers.
Benefits
Students will learn about time optimisation for factorial algorithm.
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[ ] I'm a GSSOC'24 contributor
[X] I have starred the repository

please assign me issue under gssoc 24 .


actually i am not able to proceed the next step once i upload the dataset for the regression model.

Expected behavior
A clear and concise description of what you expected to happen.
I am not able to proceed further once i upload the dataset then after that i am not able to select the target column for regression ML model and also. i am not able to move to the next step .
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

Add any other context about the problem here.

I've seen a few duplicated issues like this. While we will further investigate the root cause, one workaround is save and re-open.


Module not found: Error: Can't resolve 'react-diff-viewer'

I tried to create a material demo using preact-cli, and I want to use react-diff-viewer, so I installed it via npm i react-diff-viewer react-list-drag-and-drop -S.
D:\code\material-demo>npm i react-diff-viewer react-list-drag-and-drop -S
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>
When I run npm run dev, I got the error belows.
Build failed!

✖ ERROR ./node_modules/babel-loader/lib??ref--0!./src/routes/home/index.js
Module not found: Error: Can't resolve 'react-diff-viewer' in 'D:\code\material-demo\src\routes\home'
 @ ./node_modules/babel-loader/lib??ref--0!./src/routes/home/index.js 14:0-48
 @ ./src/routes/home/index.js
 @ ./src/components/app.js
 @ ./src/index.js
 @ ./node_modules/preact-cli/lib/lib/entry.js
 @ multi ./node_modules/preact-cli/lib/lib/entry webpack-dev-server/client webpack/hot/dev-server

I found the problem, it was the package itself issue, see https://github.com/praneshr/react-diff-viewer/issues/6.


Setting large cookie fails silently

This cookie library (as my own cookies.js so far) appears to be failing silently when trying to set a cookie too large:

var superlongtext = "";
for (var i = 0; i < 10; i++) {
    superlongtext += "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.";
}

Cookies.set('test', superlongtext);
var final = Cookies.get('test');

alert("Bug? " + (final !== superlongtext));
// Says "Bug? true"

JSFiddle with the error | | JSFiddle without the error (small cookie)
A possible solution would be to make this check manually when setting a cookie; set it, read it and compare it with the value that you were supposed to set. If they are different throw an error. Would love to know your thoughts on this. I am also considering allowing for an error/fallback function.
Edit: found Browser Cookie Limits, but still it's probably better to check if it was set properly.

Hey Francisco,
This seems like a reasonable strategy to take, given that each browser vendor can choose to implement their own arbitrary limits. It's worth noting that RFC6265 provides a little bit of guidance in terms of what expectations should be met, at a minimum:

6.1.  Limits
Practical user agent implementations have limits on the number and
size of cookies that they can store.  General-use user agents SHOULD
provide each of the following minimum capabilities:
o  At least 4096 bytes per cookie (as measured by the sum of the
length of the cookie's name, value, and attributes).
o  At least 50 cookies per domain.
o  At least 3000 cookies total.

The real bummer is that there's multiple scenarios that could prevent a cookie from being set properly, and it's not always trivial to determine what the exact cause is, given the loosey-goosey limits. Cookies could be disabled in the browser, an individual cookie could be too large, there could be too many cookies for a single domain, or there could be too many cookies in total.
It occurs to me that it's also theoretically possible that the Cookies.js enabled property ends up being false due to one of these limits having been hit, but while browser cookies are still enabled. Perhaps the end result is equivalent to if cookies were truly disabled, but it seems semantically incorrect.
In any case, it could be good to check if a cookie actually got set, and if not, throw an error. However, I don't think we can easily include why the cookie failed to be set in the error message (beyond giving possible suggestions/ideas as to what the cause might have been).
Related issue: https://github.com/ScottHamper/Cookies/issues/49
As a side note, the idea of having a cookie with 4+ KB of data in it kind of gives me the heebie-jeebies. This isn't to say we shouldn't loudly throw errors when a cookie fails to be set, but it seems a gross abuse of cookies to attempt to cram that much data into one. But I also honestly don't understand why anyone would use cookies for anything more than authentication/identification/anti-CSRF tokens (which should be HttpOnly anyways) and simple UI preference settings (grid sorts, applied filters, etc).

In addition to browser's failing silently, HAproxy, Apache2 and others may reject all requests or response which exceed the maximum HTTP header size configured in the server. While browsers may reject server responses (or the servers themselves).
It could result in the inability of the server to remove the offending cookies via a Set-Cookie header, by being prevented from even receiving requests from such a browser.
I have encountered this when I had to move PHP sessions into cookie storage to enable scalability and fix some problems with too many sessions stored on one server, for a legacy application at the company I work for.
As a side note, Brotli helped a lot :)
Estimating the header size was the way to go, and then destroying data inside cookies or entire cookies if size got out of control (memory leaks in these storage cookies sometimes).
What I mean is: the size of a single cookie is not that important, but the size all all HTTP headers which may contain multiple cookies.


#432 Provide a Live Demo

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs Update
What is the current behavior? (You can also link to an open issue here)
Created a Demo on stackblitz  and provided link in ReadMe
What is the new behavior (if this is a feature change)?
no new feature added
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] This PR is against the develop branch. (Please do not submit PR's to the master branch)
[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Other information:

Thanks for the PR - I was hoping for the code to be included in the readme, or someplace in the repo so that I can update it as this evolves. What do you think?

@dalelotts , sorry I had been out on short trip.

I was hoping for the code to be included in the readme, or someplace in the repo so that I can update it as this evolves. What do you think?

sure since I used stackblitz one can simply fork the project and update the link.
https://stackblitz.com/edit/angularjs-bootstrap-datetimepicker

@vir-c Thanks! I forked it and created a demo. I like SlackBlitz so I also created a new repo for a more complete demo app! =)


RHINENG-8149: setuptools vulnerability mitigation

Resolve RHINENG-8149

The generated image insights-puptoo:pr-321-eb7f3ca (via PR-check#305 ) has python packagesetuptools | 65.5.1 .
Hi @r14chandra , could you kindly help review the fix?


multiple devices

Can this support multiple Android TV Devices at the same time? i have total 3 and it struggles with inconsistent behaviour now, was ok with 1 device

15/09/2024, 15:45:55] [homebridge-adb] Fire TV - 🤖 Awake [15/09/2024, 15:45:56] [homebridge-adb] Mama Room TV - 🤖 Awake [15/09/2024, 15:45:56] [homebridge-adb] Mama Room TV - 🐞 App change to com.tcl.tv  [15/09/2024, 15:45:56] [homebridge-adb] Mama Room TV - 🤖 Input - Current app id - com.tcl.tv [15/09/2024, 15:45:56] [homebridge-adb] Mama Room TV - 🐞 🎚 Updating switches from app change event com.tcl.tv  [15/09/2024, 15:45:58] [homebridge-adb] Mama Room TV - 🐞 Alive: Sun Sep 15 2024 15:45:58 GMT+1000 (Australian Eastern Standard Time)  [15/09/2024, 15:45:58] [homebridge-adb] Mama Room TV - 🐞 Connected  [15/09/2024, 15:46:11] [homebridge-adb] Mama Room TV - 🐞 Trying to turn OFF accessory  [15/09/2024, 15:46:11] [homebridge-adb] Mama Room TV - 🐞 Turning power off  [15/09/2024, 15:46:14] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 10  [15/09/2024, 15:46:16] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 9  [15/09/2024, 15:46:18] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 8  [15/09/2024, 15:46:19] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 7  [15/09/2024, 15:46:21] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 6  [15/09/2024, 15:46:22] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 5  [15/09/2024, 15:46:23] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 4  [15/09/2024, 15:46:25] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 3  [15/09/2024, 15:46:27] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 2  [15/09/2024, 15:46:28] [homebridge-adb] Mama Room TV - 🐞 Turning power off: true, 1  [15/09/2024, 15:46:28] [homebridge-adb] Mama Room TV - 🐞 Turning power off: Failed  [15/09/2024, 15:46:29] [homebridge-adb] Mama Room TV - 🤖 Power Off - Failed [15/09/2024, 15:46:29] [homebridge-adb] Mama Room TV - 🐞 Power off error message: Failed
it turns off and turn on fine and sometimes It does not

It should support multiple devices, but yes it's a bit inconsistent right now. Especially for turning on/off devices, even in a single device configuration sometimes.


Improve article 1910.06709

Exact location of issue
The footnotes of 1910.06709 (link is to the first footnote).
Problem details
Visual problem:
When viewing the article in Firefox on a laptop screen with full screen width, the footnotes appear in the right margin alongside the text (which seems fine) and they are slightly cut-off on the right (which is the problem). It looks as if the last character or so of each line is "under" the scrollbar on the right edge.
Possible fix:
Changing the css property padding-right the ltx_note_outer class (set on this line) from 2rem to 3rem produces something acceptable, at least in my browser. I have no idea if this would be a robust fix.
(Optional) Expected behavior
I would expect the footnote text to appear in the right margin (as it does now), without overflowing to the right of the visible area.
Desktop (please complete the following information)

OS: Debian (12/bookworm/testing)
Browser: Mozilla Firefox 91.7.0esr

(Optional) Screenshots

Thanks for letting me know! The really valuable information for me here @mguaypaq is to know your monitor width and screen resolution. You have one of the few form factors that my @media queries waffle through, sorry about that.

My screen is 14 inches along the diagonal, 12 inches wide, and my resolution is 1920 x 1200.

I did not have any better ideas (or time to do a complete redesign of the side note UI), so I went with your suggestion @mguaypaq . Thanks for the report, and apologies the resolution took so long.


Request Body Validation

Hey, I just tested around with the mocking mode of prism and it turned out that JSON request bodies are not validated, e.g.  Do I overlook something obvious here to let the validation happen or is this just not implemented?
I used the petstore examples from swagger.

Hi @GalaxyGorilla! Could you share more details of the requests you are making? There's a couple where it doesn't validate, but it should be validating for most.

I just used the petstore minimal example and then tried a POST:
 % curl -vvv localhost:4010/pets -X POST -d "some bullshit"
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 4010 (#0)
> POST /pets HTTP/1.1
> Host: localhost:4010
> User-Agent: curl/7.54.0
> Accept: */*
> Content-Length: 13
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 13 out of 13 bytes
< HTTP/1.1 200 OK
< Content-Length: 69
< Content-Type: application/json
< Sl-Response-Valid: true
<
* Connection #0 to host localhost left intact
{"id":30459975,"name":"pariatur amet aliqua deserunt","tag":"mollit"}

My expectation was that the request body is validated against the parameter description in the spec.

We would also like to see this feature implemented.
When a parameter required by the contract is missing, the expected behavior would be 400 Bad Request preferably with an explanation of the missing parameters.

One thing to watch out for is what is additionalProperties set to and what is the combination of required properties. I expanded on it here some: https://community.stoplight.io/t/contract-testing-not-working/295/7

Same problem here. Here's my simple spec:
swagger: "2.0"
info:
  title: Sample API
  description: API description in Markdown.
  version: 1.0.0
host: webhook.site
basePath: /v1
schemes:
  - https
paths:
  /users:
    post:
      summary: Creates a new user.
      consumes:
        - application/json
      parameters:
        - in: body
          name: user
          description: The user to create.
          schema:
            type: object
            required:
              - userName
            properties:
              userName:
                type: string
              firstName:
                type: string
              lastName:
                type: string
      responses:
        201:
          description: Created

And my test request to a local prism instance running the validate command:
-> prism validate -d -s ./simple.oas2.yml
-> curl -vX POST http://localhost:4010/users

And here's the response:
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 4010 (#0)
> POST /users HTTP/1.1
> Host: localhost:4010
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Transfer-Encoding: chunked
< Cache-Control: no-cache, private
< Content-Type: text/html; charset=UTF-8
< Date: Mon, 18 Feb 2019 22:40:36 GMT
< Server: nginx/1.10.3
< Sl-Request-Valid: true
< Sl-Response-Valid: true
< Vary: Accept-Encoding

I am expecting the 404 not found because of the host I am using but the Sl-Request-Valid header says my request is valid when I obviously did not post in a JSON object in the body. What am I missing?

Same here. Seems not resolved for this issue. Any idea for this issue.

Hey everyone! We just released a new patch version, 2.0.18. I'd recommend trying it with that.
And for @micahknox can you try updating but add content-type header with application/json to see if that gets the contract testing working.


Support parse ipv6

Purpose of the pull request
The ipv6 may have multiple commas.
Brief change log

Change the parse address logic in Host.

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #14584 (7d29be0) into dev (20cf4ad) will decrease coverage by 0.01%.
The diff coverage is 57.14%.

:exclamation: Current head 7d29be0 differs from pull request most recent head a5d5439. Consider uploading reports for the commit a5d5439 to get more accurate results

@@             Coverage Diff              @@
##                dev   #14584      +/-   ##
============================================
- Coverage     38.48%   38.48%   -0.01%
+ Complexity     4549     4543       -6
============================================
  Files          1254     1254
  Lines         43709    43679      -30
  Branches       4822     4819       -3
============================================
- Hits          16822    16810      -12
+ Misses        25013    24998      -15
+ Partials       1874     1871       -3

Impacted Files
Coverage Δ

...org/apache/dolphinscheduler/remote/utils/Host.java
76.47% <57.14%> (+31.78%)
:arrow_up:

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Change memory order in Task Status

compare_exchange_weak is actually undefined behavior is success has a stronger ordering than failure.
Failure is either relaxed or acquire. However, it makes sense to make success release anyway regardless, because it is done that way in the function prior.

@al45tair Can you test this please?

@swift-ci Please test

FWIW, I don't think you changed the success memory order to release, even though you mention that in your comment above. (Also, this is a change to a compatibility library, which is only used when building code for older versions of Apple systems where Concurrency doesn't form part of the OS; updating the compatibility libraries isn't entirely straightforward, so it might take a long time for this change to appear in an Xcode release.)


Icons are way too big

Icons are way too big consider using the same size of icons that the rest of the editor uses

I am using a 4k display and for that the size is about right. Could you make a screenshot on how this looks on your machine?

I don't know exactly what he means, but I do have this issue on my end.

And to a lesser extent:

@rubybrowncoat - this is a known editor bug and will be fixed in a future version of Godot (https://github.com/godotengine/godot/issues/57286)

I resized all icons to be 16x16 like the built-in icons, this seems to work better. I also found  a way for them to not be blurry at this size.


[release-1.12] fix CVE-2023-45288, bump base images, bump go

Pull Request Motivation
Similar to #6929, #6932 and #6931
Kind
/kind bug
Release Note
Fix CVE-2023-45288 by updating golang.org/x/net
Bump to latest golang patch version - 1.21.9

/retest

/approve
/lgtm


error   ERROR: Failed building wheel for dlib

nentations->insightface->-r c: ai\comfyuI-aki-v1.3\ComfyuI-aki-v1.3\custom nodesicomfyuI FaceAnalysis\requirements.txt (line 3))(4.8.0)3uilding wheels for collected packages: dlib
Building wheel for dlib(pyproject.toml)error:subprocess-exited-with-error:Building wheel for dlib(pyproject.toml)did not run successfully.exit code: 1>See above for outputa subprocess, and is likely not a problem with pipnote:This error originates from

Could not build wheels for dlib, which is required to install pyproject.toml-based projects

try to install the pre-compiled wheel, it's linked in the readme

and for Fedora ? as i'm facing the same problem cmake already installed in .venv `Collecting dlib
Using cached dlib-19.24.4.tar.gz (3.3 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: dlib
Building wheel for dlib (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for dlib (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [26 lines of output]
:210: SyntaxWarning: invalid escape sequence '('
:211: SyntaxWarning: invalid escape sequence '('
:212: SyntaxWarning: invalid escape sequence '('
:192: SetuptoolsDeprecationWarning: The test command is disabled and references to it are deprecated.
!!
          ********************************************************************************
          Please remove any references to `setuptools.command.test` in all supported versions of the affected package.

          By 2024-Nov-15, you need to update your project and remove deprecated calls
          or your builds will no longer be supported.
          ********************************************************************************

  !!
  /tmp/pip-build-env-a2inih7h/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'tests_require'
    warnings.warn(msg)
  running bdist_wheel
  running build
  running build_ext
  Traceback (most recent call last):
    File "/home/luc/ComfyUI/.venv/bin/cmake", line 5, in <module>
      from cmake import cmake
  ModuleNotFoundError: No module named 'cmake'

  ERROR: CMake must be installed to build dlib

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for dlib
Failed to build dlib
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (dlib)
(.venv) luc@fedora39:~$
`

uninstall cmake and try again

tried that 20 times , it did work on one of my previous installation but not this time.uninstalling cmake then reinstalling it doesn't change anaything it's like it couldn't find it as it is present in pip list

do NOT reinstall it. just uninstall cmake and then install dlib


fix: string to entity conversion inconsistencies

Signed-off-by: Andrei Kuzmiankov<EMAIL_ADDRESS>closes #397

Can you update the constructors to support ScheduleId | string as well.


Updating some storage mocks after google-resumable-media==0.3.1 release.

Fixes #4243.
Also increasing the lower-bound on google-resumable-media to 0.3.1.

Can I get a review @jonparrott @tseaver @lukesneeringer? Our tests are broken right meow (e.g. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/3882)

I'm OK with merging now to unblock others, but I'm worried that we are papering over the real bug (either here or in google-resumable-media).  So we should either not close #4243 (but maybe edit its title / description), or else reopen https://github.com/GoogleCloudPlatform/google-resumable-media-python/issues/41.

@tseaver There is no bug. This is working as "intended", but the intent can be discussed (see my comment https://github.com/GoogleCloudPlatform/google-cloud-python/pull/4244#discussion_r146901312)


Fleet 🚫🍌in 🖥 hostname

What version of fleet are you using (fleet version --full)?
"version": "2.1.1",
"branch": "master",
"revision": "918b9facd140a2bb80cdf589b6d87e58c8cf90ff",
"go_version": "go1.11.5",
"build_date": "2019-05-04T01:00:59Z"
What operating system are you using?
RHEL 7.something
What did you do?
One of my 🐴coworkers named his computer 🍌. It's actually bound to ActiveDirectory with that name and it's windows computer name matches. It's legit.
What did you expect to see?
🍌
What did you see instead?
??

Relates to https://github.com/kolide/launcher/pull/481

Some discussion from slack with the OP and their coworker:

Mysql is using utf8mb4
livequery SELECT hostname AS hostname FROM system_info; returns ??.ad.rit.edu
livequery select '🤕'; gets a lot of emoji from a lot of hosts
osquery -i returns ?? too

osquery> SELECT hostname AS hostname FROM system_info;
+---------------+
| hostname      |
+---------------+
| ??.ad.rit.edu |
+---------------+

This is looking more like how windows returns that data

I am closing this as an osquery issue. Fleet does support emoji hostnames if they are returned from osquery.


does not work with payload V3

This plugin does not work in Payload V3
any plan to update ?
its a great plugin if it will work

@yonnic I can make an update sometime this upcoming week - thanks for letting me know!


doc update description of field sql_digest

emphasize sql_digest will be empty is query is not slow query.

run buildall


Increase project quality

Guys add please support for on_failure_callback in this way:
from airflow.providers.slack.notifications.slack import send_slack_notification
'on_failure_callback': [
        send_slack_notification(
            slack_conn_id='slack',
            text="""
                :red_circle: Task Failed.
                *Task*: {{ ti.task_id }}
                *Dag*: {{ ti.dag_id }}
                *Execution Time*: {{ ti.execution_date }}
                *Log Url*: {{ ti.log_url }}
                """,
            channel="analytics-alerts",
            username="Airflow",
        )
    ],

Now its only possible without params and only through absolute path for .py file.

Thank you, @matveykortsev, indeed, this feature would be valuable. I've created a high-level task to compare the missing issues like this.


Treaty and Dependency Injection

Hi!
In order to use some feature of elysia like dependency injection (https://elysiajs.com/patterns/dependency-injection.html), I split the code into multiple file:
First, a state for the database
// setup.ts
export const setup = new Elysia({ name: 'setup' })
    .state('redis', redis)

// routes/auth.ts
import { Elysia } from 'elysia';

import { setup } from '../setup';

export const authRouter = new Elysia({prefix: "/auth"})
    .use(setup)
    .post('/login', async (context) => { ... })
    .post('/logout', async (context) => { ... }));

// routes/foo.ts
import { Elysia } from 'elysia';

import { setup } from '../setup';

export const fooRouter = new Elysia({prefix: "/foo"})
    .use(setup)
    .get('/', async (context) => { ... })
    .post('/manage', async (context) => { ... }));

and finally the main entry point for my app
// server.ts
import { Elysia } from 'elysia';

import { authRouter } from './routes/auth';
import { fooRouter } from './routes/foo';

const app = new Elysia()
    .use(authRouter)
    .use(fooRouter)
    .listen(6001);

export type App = typeof app;

console.log(`🦊 Elysia is running at ${app.server?.hostname}:${app.server?.port}`);

Working as expected, manually querying various endpoints.
When using Treaty, I get an empty elysia app on the client side

Any idea where my code fails?
Thanks in advance!

any workaround? was wondering why my eden type not working at all

Can’t replicate, seems to have been fixed in a newer releaase since the issue was posted?

This still does not work for me.

This is still happening to me too on "elysia": "~1.1.17" and "@elysiajs/eden": "~1.1.3", with the same structure as @artecoop, which basically means I either create an humoungous index or I can't use types


debug_info throws error on Mac OS with Silicon M1, M2

The method throws an error because these macs have the M1 or M2 silicon, but not the NVML Shared Library. Need to find an alternative that is compatible.

This library seems like it might be an option.
https://github.com/helloall1900/pynvx

Closing the issue.
It is possible to run this in debug mode with pycharm on the sd-gpu resource, so there's no reason to bother with mac m1, m2 compatibility. Those gpu would never be used in production, so there is no point at least for now.


Add more details to the description of SOAP APIs

Is your suggestion related to a missing or misleading document? Please describe.
We have encountered that in the Managing Users and Roles SOAP APIs[1], the username parameter description does not say how we need to provide the username to the SOAP request.
Ex : For isExistingUser SOAP API we need to send the userstore domain qualified username to search the user in the particular userstore. If we did not add the doamin qualified username it will only serch the user in the PRIMARY userstore. But in [2], there are no description about these details.
[1] https://is.docs.wso2.com/en/5.11.0/develop/managing-users-and-roles-with-apis/#managing-users-and-roles-with-apis
[2] https://is.docs.wso2.com/en/5.11.0/develop/managing-users-and-roles-with-apis/#isexistinguser
Describe the improvement
We need to update the description of the SOAP APIs with the proper details about how we need to send the params and what is the behavior of the corresponding SOAP API with those params.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Custom data with authcode / token

I have had an OAUTH server running using oath2orize for some time and use it with many different services.
I now have a need for a user to select a particular option when they perform the Allow through the Dialog.  For example, when the perform allow they will select a particular option, 1, 2, 3 or 4.
I want to store this with the authcode in a seperate field as well as store it when the authcode exchange occurs.
Problem is that when I do the authsave in oauth2orize.grant.code() I do not have access to the req.query values passed in.
Any suggestions would be most appreciated.

Figured it out...
In the decision code, you can pass in a value.  Below you will see instanceID which I pass in when retrieved from req.body.instanceID.
exports.decision = [
login.ensureLoggedIn(),
server.decision( function(req, done) {
console.log("OAUTH: User's decision processing");
return done(null, { scope: req.body.scope, state: req.body.state, instanceID: req.body.instanceID})
})]
Then when I do the authsave, I have access to the value in ares value.  I then pass this into my authsave function that writes it to the database.
server.grant(oauth2orize.grant.code(function(client, redirectURI, user, ares, done) {
console.log("OUATH: Going to perform grant");
var code = utils.uid(48);
db.authsave(code, client.id, redirectURI, user.id, ares.instanceID, function(err) {
	if (err) {
		return done(err);
	}

	done(null, code);
});

}));


@rnmapbox/maps installation error in react-native-expo project

Environment

Dev OS: [Win11]

Steps to reproduce
I've installed @rnmapbox/maps in my react-native-expo project by using this guide: https://github.com/rnmapbox/maps/blob/main/plugin/install.md, but getting error: "Cannot read property 'EventTypes' of null.
Note: I've added screenshots below

Anyone solved this? Same error happening to me


add OME-TIFF validation to ingest process

https://docs.openmicroscopy.org/bio-formats/6.5.1/users/comlinetools/xml-validation.html
@ilan-gold: is there anything else that you are checking for?
Current status: validation process checks that OME-TIFF is valid XML.
Next update will check OME-TIFF against the schema.

@ngehlenborg @ilan-gold xmlvalid only validates the structure of the OME.TIFF header against a schema.
This is the bare minimum. For example, the images missing the channel names passed the xmlvalid test. There should be a discussion about fields per assay type and how we can use that information at run time to trigger computations within a DAG.

I agree with @icaoberg that we should really be doing more.

Informing the submitters of what their channel names will look like (as a check, like Ivan said, especially if there are none)
Informing them if they leave out physical scale units (since we can display that)
Checking for blank images and warning the submitter of this (Nico has some images with blank channels)
If this tifffile issue with multiple tags continues to be a problem (and it's not a bug), we should overwrite the incoming file (or reject it).
If we really wanted to get fancy, we could find (or try to compile) a list of names for fluorescent stains and check the incoming channel names against a reference list.  This will make future cross-dataset work much easier.
We can check to make sure the Z * C * T number of channels actually lines up with what is in the image.
Provide a warning about large 32 bit images that would need to be pyramidal (due to the visual artifacts we have been seeing).

This is what I can come up with as far as the metadata is concerned.

Another thing we could add is a way to indicate to people that their data is spatially the same, like with seqFish which has a bunch of repeat positions and hybridization cycles.

See also issue #70

Just a thought @jswelling @ngehlenborg @icaoberg  but one option for this beyond running tiffcomment or the like could be to tell people to run the bioformats2raw + raw2ometiff pipeline and check that they can "drag and drop" the output onto Avivator.  I find myself doing this a lot anyway and I have started telling people to do it. We could even automate it further to do the following:

Install bioformats2raw + raw2ometiff via conda as mentioned here:

conda create --name bioformats python=3.8
conda activate bioformats
conda install -c ome bioformats2raw raw2ometiff

Run bioformats2raw + raw2ometiff on one of the input files (doesn't matter which, I think this is just a sanity check since people tend to uniformly process their files so one file broken usually indicates them all being broken)
Start a simple http server on their computer that serves the OME-TIFF output of the pipeline that was run locally
Open a web browser with Avivator pointing at that http server
This should all be doable within the python ecosystem from what I can tell.  Thoughts?


Group prefix repeating

Hey, I just updated to "@elysiajs/eden": "0.6.0" and "elysia": "0.6.3"... Now my group path names are repeating in both in Eden Treaty and Eden Fetch... Any idea how to fix?

I'm having the same problem.
There is an issue in which the group name is repeated when the files of each router are imported and grouped.
Therefore, when executing the request, an error occurs (because there is a problem with the mapping being doubled).
The issue hasn't been resolved, so why is it closed?
Did you also solve the problem?

@gtrabanco oh thanks!

@Micnubinub, can you provide a your minimal reproducible code for me to test

@Micnubinub, can you provide a your minimal reproducible code for me to test

"@elysiajs/eden": "0.6.0",
"elysia": "0.6.10",
Server:
const test = (app: Elysia) => app
  .group('/app', group => group
    .get('/test', async () => {
        return "Test"
    }))

const app = new Elysia()
  .use(test)

Client:
export const fetcher = edenFetch<App>(import.meta.env.VITE_BASE_URL, {
})

@SaltyAom are you able to reproduce?

Fixed in "@elysiajs/eden": "0.6.1" and "elysia": "0.6.11"


Add ShouldBeTrue and ShouldBeFalse validation rules

Hi!
Regarding Issue #3 this PR adds ShouldBeTrue and ShouldBeFalse validation rules and it's tests.
Let  me know if something must to be changed.
Thanks!

Thanks @alibori! The only change I would like to make (for now) is to remove null as a falsy value. If @brendt is of the mind that should change we can introduce a second PR to adjust that.

Done @aidan-casey 👍
Thanks!

Thanks, @alibori!


Clarification of git users

Git user during import is not git bot user...

Thx @eickler, it helped me to understand why I was having trouble running the QuickStart repos.

Thx @eickler, it helped me to understand why I was having trouble running the QuickStart repos.


Make block explanations more compact in Blockly

See feedback:
Blockly contains a lot of self-explanatory text, which is great. But this is in tension with the desire for blocks not to be too large, so that I can see a reasonable  chunk of program at one time. Even small Blockly programs occupy a huge amount of screen. Some attention to making the blocks more compact would help.

Do you want me to give it a try in https://github.com/input-output-hk/marlowe/pull/23 ?
My day job is Frontend developer btw. Happy to give some free hours to improve meadow. Every little helps!

That would be great, but probably in a separate pull-request would be better.
The file to edit is: marlowe/meadow/blocks/blocks.xml
I use this tool to edit it:
https://blockly-demo.appspot.com/static/demos/blockfactory/index.html

Sounds good to me. I'll give it a try this week.

OK detailed suggestions here:
Convention: using … for something to fill in and \n for a (line) break.
Contracts

Pay: some extra line breaks in here: remove if possible; turn currency/name into a new block, with Ada as "smart" option; the amount of; from the account.
If … \n then … \n else …
When … \n at timeout … \n continue …

Values

Available money; will use new block for currency/name; account number;
Choice id … by participant … default …

Case

Action … \n Contract … (i.e. no "and").

Actions

Deposit \n amount … \n New token block \n into account …
Choice: Name … \n Owner … \n Bounds …

We have updated block explanations in Blockly in new Marlowe Playground


EPG XML has overlapping times for shows

I have several schedules where there is only one item in the list. It is configured to play a random episode from a show for a duration of 1 hour, with tail and fallback fillers at the ending (the shows are roughly 42 minutes long). When viewing the playout from the website, it's fine (there's one episode listed per hour, starting at the top of every hour). However, the XMLTV listing is messed up. Specifically, it lists overlapping start and end times for the shows. This results in Tivimate (for example) not showing every other episode.

I'm guessing something in the XMLTV generation is getting confused with the previous episode's filler start times and the new episode's start times. Can this be fixed?

Thanks for the report - I recently fixed a couple bugs that caused overlapping playout items when filler was configured to pad, but I didn't look at the duration playout mode which is similar in effect. I'll take a closer look.
Please confirm your version of ETV (found below the left menu).

Forgot to mention the version, it's v0.7.4-beta-linux-x64.

I have a similar issue that I posted about on the Discord channel.  I figured I would post it here as well.  In my scenario I have channels that each have a single schedule set for duration of multiple hours with a tail mode of offline. Every night around 11:30pm these channels guide data overlaps all the other shows/movies until the next schedule start period.

The playout shows the correct shows...

BUT the xmltv shows that the overriding show (2nd one below) has a stop date of 033000 instead of 000437...
</programme><programme start="20230308231817 -0500" stop="20230308234028 -0500"

 </programme><programme start="20230308234028 -0500" stop="20230309033000 -0500"

 </programme><programme start="20230309000437 -0500" stop="20230309002655 -0500"

 </programme><programme start="20230309002655 -0500" stop="20230309004738 -0500"

 </programme><programme start="20230309004738 -0500" stop="20230309011054 -0500"

 </programme><programme start="20230309011054 -0500" stop="20230309013340 -0500"

 </programme><programme start="20230309013340 -0500" stop="20230309015510 -0500"

 </programme><programme start="20230309015510 -0500" stop="20230309021733 -0500"

 </programme><programme start="20230309021733 -0500" stop="20230309023925 -0500"

 </programme><programme start="20230309023925 -0500" stop="20230309030141 -0500"

 </programme><programme start="20230309030141 -0500" stop="20230309032352 -0500"

 </programme><programme start="20230309090000 -0500" stop="20230309092341 -0500"

 </programme><programme start="20230309092341 -0500" stop="20230309094641 -0500"

Updated to 0.7.5-f7d19e37-docker-vaapi and tested. The epg is now correct. I did have to reset the playout as you stated for the offline tail mode.

I can confirm this is fixed, closing this.


realm: Schedule realm deletion time while deactivating realm.

This PR adds a new option which allows to schedule realm data deletion time while deactivating a realm and also adds a server level setting to configure maximum and minimum allowed deletion days.
Fixes: #24677.

Screenshots and screen captures:
Confirm deactivate realm model

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Before anyone starts reviewing my PR, a few changes need an explanation as to why that change was done.

The moving out of get_expiration_time_in_minutes, set_expires_on_text and set_custom_time_inputs_visibility from invite.js was suggested by Alex in this comment.

@alya, can you review this?

Please add a screenshot of the deletion time dropdown.
Why are custom times limited to 14 days or more?

Please add a screenshot of the deletion time dropdown.
Why are custom times limited to 14 days or more?

Added the screenshot of the deletion time dropdown in the PR description.
Minimum allowed duration set to 14 was suggested by @timabbott in this comment.
CZO thread

@opmkumar - Thanks for working on this!
From your comments above and from looking at your changes here, it seems like this is an updated version of the changes in #26109. If you're changes incorporate someone else's work, then you should make sure that you mention them in your commit message as a co-author: https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html#mentioning-other-contributors.
It's also usually good practice to mention in your initial PR comment that the changes are an updated version of a past PR so that it's clear that the work here is an updated version of an older PR.
Glancing at the commit messages here, I think you should review the formatting section of our commit discipline guide while you're updating for the co-author attribution: https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html#formatting-guidelines.
Finally, I've taken some of the prep work from #26109 and incorporated it into #30510. It probably makes the most sense for that PR to get reviewed and merged first, as then the remaining work here (and in #26109) would be updating the final commit for those changes.

Hm, my bad, I didn't know about the co-author part earlier. Will update my commit message and PR accordingly.
So, once #30510 gets reviewed and merged, I will continue my work.
Thanks, @laurynmm.

#30510 is now merged, so you should be able to rebase this.

Where did the 2 years option come from? Was it discussed somewhere?

Rather than having a whole line about the minimum time, let's just put "(14+ days)" after "Custom time" (on the same line).

I pushed some string changes to this PR. You can review, fix tests, and squash them into your commit.

Where did the 2 years option come from? Was it discussed somewhere?

Yes, it was added by @timabbott in the previous PR. (see this comment)

I pushed some string changes to this PR. You can review, fix tests, and squash them into your commit.

@alya, I have squashed the commits.
Current behavior:

Great, @laurynmm will review once conflicts are resolved.

Great, @laurynmm will review once conflicts are resolved.

Resolved the conflicts.
@laurynmm, this PR is now ready for your review.

Thanks for such a detailed review, @laurynmm.

On the backend, I think the None value for the minimum days is not being handled and documented correctly.

I probably made a mistake while defining MIN_DEACTIVATED_REALM_DELETION_DAYS in default_settings.py.
In my opinion, MIN_DEACTIVATED_REALM_DELETION_DAYS can be a non-null value since we know that its value won't be less than 0 any way.
So, in default_settings.py:
# Minimum and maximum permitted number of days before full data
# deletion when deactivating an organization. A nonzero minimum helps
# protect against a compromised administrator account being used to
# delete an active organization.
MIN_DEACTIVATED_REALM_DELETION_DAYS: int = 14
MAX_DEACTIVATED_REALM_DELETION_DAYS: int | None = None

What are your thoughts on this?

I probably made a mistake while defining MIN_DEACTIVATED_REALM_DELETION_DAYS in default_settings.py. In my opinion, MIN_DEACTIVATED_REALM_DELETION_DAYS can be a non-null value since we know that its value won't be less than 0 any way.
So, in default_settings.py:
# Minimum and maximum permitted number of days before full data
# deletion when deactivating an organization. A nonzero minimum helps
# protect against a compromised administrator account being used to
# delete an active organization.
MIN_DEACTIVATED_REALM_DELETION_DAYS: int = 14
MAX_DEACTIVATED_REALM_DELETION_DAYS: int | None = None

What are your thoughts on this?

In the previous pull request, how was the value set? Did it get any comment in the review process? If not, then it might be worth an #api design disccusion on CZO to clarify this detail.
Either way for the endpoint that's used for realm deactivation, we have to handle that new parameter delay_deletion_days (I think) as potentially being None for all cases of these server values.

Did it get any comment in the review process?

I was able to find this comment from the previous PR: https://github.com/zulip/zulip/pull/26109/files#r1308103946

Hmmm... yeah, that was specifically about the web app UI. And the server implementation there did have the min constant on the server typed as Optional[int], so I think it'd be good to just check on an #api design conversation in CZO about this detail to get feedback from other folks. I did a quick look for the previous pull request number in CZO and didn't see any conversations in that channel, so you can probably just start a new topic.

I have updated the PR @laurynmm.
Thanks :)

@opmkumar - Thanks for doing those updates! I went ahead and pushed a few updates to the frontend implementation for these changes, as well as some revisions to the API documentation changes. It'd be great for you to review my changes  and let me know if you have any questions.
@alya - During the review process there were some updates to some of the user-facing strings, so mentioning you in case you want to do a pass again. Specifically:

If a custom time input is invalid due to the server's min/max settings, we display "Invalid custom time" to the user.
For a valid deletion time, we only show the date and not the time; see updated screenshot below.

Notes/Questions:

Currently, the backend changes do not include adding a management command for processing the deactivated realms with scheduled_deletion_date set. I haven't looked back at all the comments on #26109, which this pull request builds on, to see if that was brought up at any point in time. Do we want to do that as a follow-up or as part of these changes?
Per this CZO api design conversation, I wasn't sure if we wanted to implement the settings any differently here. Currently, these changes just set a default min at 14 days and max as None for the server.

Updated screenshots:

Org deactivation modal - invalid custom time below server min

Org deactivation modal - valid time

API changelog entry

Register response - server min and max constants

I decided it's be most efficient to merge this with the above tweaks after a thorough review. Action items:

@opmkumar to do a round of careful testing and report any issues noted in the design thread.
Opened #32763 and tagged as a release goal to track making sure the deferred deletions actually happen. @opmkumar I'm assuming you'll put up a PR for that within the next week or two; the release goal tagging is just the backup plan in case you get busy.
@timabbott to make sure we set the right values for Zulip Cloud.

Also, @laurynmm , could you please adjust the documentation at https://zulip.com/help/deactivate-your-organization ?


WebAuthn

Following on from:
https://github.com/w3c/webauthn/issues/1362#issuecomment-746624274
https://github.com/greenpau/caddy-auth-portal/blob/cb90d8656989a35ede780bdedcb21e555aea08ad/assets/templates/basic/settings.template#L607-L635
I don't have the time to debug the code at the moment, but have a look at how I implemented the getPublicKey() polyfill.
In particular, the bit where I use the result.response.attestationObject:
https://github.com/craigfrancis/webauthn-tidy/blob/main/new/js/polyfill.js?ts=4#L552
I, like you, use CBOR.decode() to get to authData.
Then I use my authenticator_buffer_parse function to get the flags, and the der_content.
Now that's DER format, I don't know enough about Go to know if it can support that... but if not, and it's like PHP which uses PEM (via openssl), then it's fairly easy to convert ($user_key_value is the DER value base64 encoded):
https://github.com/craigfrancis/webauthn-tidy/blob/main/new/check.php?ts=4#L126

@craigfrancis , once again, thank you for much! I will review and follow up with questions.

@craigfrancis , Happy New Year! 🎉
I am getting back to it! I use CBOR from github.com/paroga/cbor-js.
https://github.com/craigfrancis/webauthn-tidy/blob/85b8f53648a628e0a8f1866d450960008b18a75c/new/js/polyfill.js#L472-L474
It looks like you are using slightly different CBOR implementation. In the implementation I use, there is no length to publicKeyObject. My guess is that you needed an offset and you included it in your CBOR implementation. Is that right?

@craigfrancis , Happy New Year! 🎉
I am getting back to it! I use CBOR from github.com/paroga/cbor-js.
https://github.com/craigfrancis/webauthn-tidy/blob/85b8f53648a628e0a8f1866d450960008b18a75c/new/js/polyfill.js#L472-L474
It looks like you are using slightly different CBOR implementation. In the implementation I use, there is no length to publicKeyObject. My guess is that you needed an offset and you included it in your CBOR implementation. Is that right?

@craigfrancis, the CBOR code I am referring to starts here and returns length over here.

@craigfrancis, the CBOR code I am referring to starts here and returns length over here.

I’ll check it over again when I get back to my computer, but if memory serves, I had to modify the CBOR decoder a bit to return the length, and stop itself when it’s at the end.
Again, I’m relying on my memory here, but I think WebAuthN uses a feature of CBOR, where it encodes the length in itself (as in, this field is X bits long, next, this field is Y bits long, etc, now we get to the end, and we have processed Z bits)... I’m sure it made someone think they were very clever, to save a bit of data, but personally I think it just adds complexity.

I’ll check it over again when I get back to my computer, but if memory serves, I had to modify the CBOR decoder a bit to return the length, and stop itself when it’s at the end.
Again, I’m relying on my memory here, but I think WebAuthN uses a feature of CBOR, where it encodes the length in itself (as in, this field is X bits long, next, this field is Y bits long, etc, now we get to the end, and we have processed Z bits)... I’m sure it made someone think they were very clever, to save a bit of data, but personally I think it just adds complexity.

Added this image for my notes.

Added this image for my notes.

Yep, that's the image I was using, from the Attestation section of the WebAuthN spec.
As to what I did, well, you've already identified the key points...
I'm also using github.com/paroga/cbor-js, which I hope I've credited them correctly on line 41.
First, and not really relevant to this issue, on line 46, I tweaked how the library is included (I'm putting it into a local CBOR variable, so I can do CBOR.decode(), without using a module, or the global scope).
And the key part, which you have already highlighted on lines 416-419, is where I've replaced the original code (commented out, just above), which complained about "Remaining bytes", and instead I'm returning the decoded data, and the offset it got to (and intentionally ignoring the remaining data).
Just to confirm the changes, I just did:
diff -w cbor.js polyfill.js
[...]
>
>         var CBOR = (function(undefined) {
>
389a412,533
>                     // var ret = decodeItem();
>                     // if (offset !== data.byteLength)
>                     //     throw "Remaining bytes";
>                     // return ret;
>                     return {
>                             'data': decodeItem(),
>                             'length': offset,
>                         };
>                 }
>
>                 return {'encode': encode, 'decode': decode};
>
>             })();
[...]

(this does ignore some of the wrapper code, but it's not important here).

Yep, that's the image I was using, from the Attestation section of the WebAuthN spec.
As to what I did, well, you've already identified the key points...
I'm also using github.com/paroga/cbor-js, which I hope I've credited them correctly on line 41.
First, and not really relevant to this issue, on line 46, I tweaked how the library is included (I'm putting it into a local CBOR variable, so I can do CBOR.decode(), without using a module, or the global scope).
And the key part, which you have already highlighted on lines 416-419, is where I've replaced the original code (commented out, just above), which complained about "Remaining bytes", and instead I'm returning the decoded data, and the offset it got to (and intentionally ignoring the remaining data).
Just to confirm the changes, I just did:
diff -w cbor.js polyfill.js
[...]
>
>         var CBOR = (function(undefined) {
>
389a412,533
>                     // var ret = decodeItem();
>                     // if (offset !== data.byteLength)
>                     //     throw "Remaining bytes";
>                     // return ret;
>                     return {
>                             'data': decodeItem(),
>                             'length': offset,
>                         };
>                 }
>
>                 return {'encode': encode, 'decode': decode};
>
>             })();
[...]

(this does ignore some of the wrapper code, but it's not important here).

And the key part, which you have already highlighted on lines 416-419, is where I've replaced the original code (commented out, just above), which complained about "Remaining bytes", and instead I'm returning the decoded data, and the offset it got to (and intentionally ignoring the remaining data).

@craigfrancis , thank you looking at it 👍
Interesting observation ... not on topic, but still relevant.
      if ('x5c' in attStmt) {
        // Handle non-ECDAA attestation type
        var certChain = [];
        // The elements of this array contain attestnCert and its
        // certificate chain, each encoded in X.509 format. The attestation
        // certificate attestnCert MUST be the first element in the array.
        response["x5c"] = []
        attStmt.x5c.forEach(item => response.x5c.push(uint8array_to_base64(item)));
      } else {
        if ('ecdaaKeyId' in attStmt) {
          // Handle ECDAA attestation type
        } else {
          throw "ecdaaKeyId not found in attestation statement";
        }
      }

Apparently, if I take the first element of x5c array, base64 decode it and run the following SSL command, I get a valid cert.
echo -n "x5c 1st element value" | base64 -d > key.crt
openssl x509 -in key.crt -inform der -text

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 902058766 (0x35c4530e)
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN = Yubico U2F Root CA Serial 457200631
        Validity
            Not Before: Aug  1 00:00:00 2014 GMT
            Not After : Sep  4 00:00:00 2050 GMT
        Subject: C = SE, O = Yubico AB, OU = Authenticator Attestation, CN = Yubico U2F EE Serial 902058766
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:66:ae:cd:ae:25:18:8e:4a:23:97:00:58:41:84:
                    7f:65:ad:f1:f0:8b:04:23:fa:85:63:4a:bb:a9:86:
                    2e:14:2d:f7:b9:f4:09:df:2e:4e:5e:9e:06:af:7a:
                    17:39:e1:51:d5:77:90:30:b5:8a:d7:71:b5:5f:6c:
                    75:62:7e:2b:07
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            <IP_ADDRESS>.4.1.41482.2:
                <IP_ADDRESS>.4.1.41482.1.7
            <IP_ADDRESS>.4.1.457<IP_ADDRESS>:
                ...
            <IP_ADDRESS>.4.1.457<IP_ADDRESS>:
                ....(yr.I..u=....*
            X509v3 Basic Constraints: critical
                CA:FALSE

And the key part, which you have already highlighted on lines 416-419, is where I've replaced the original code (commented out, just above), which complained about "Remaining bytes", and instead I'm returning the decoded data, and the offset it got to (and intentionally ignoring the remaining data).

@craigfrancis , thank you looking at it 👍
Interesting observation ... not on topic, but still relevant.
      if ('x5c' in attStmt) {
        // Handle non-ECDAA attestation type
        var certChain = [];
        // The elements of this array contain attestnCert and its
        // certificate chain, each encoded in X.509 format. The attestation
        // certificate attestnCert MUST be the first element in the array.
        response["x5c"] = []
        attStmt.x5c.forEach(item => response.x5c.push(uint8array_to_base64(item)));
      } else {
        if ('ecdaaKeyId' in attStmt) {
          // Handle ECDAA attestation type
        } else {
          throw "ecdaaKeyId not found in attestation statement";
        }
      }

Apparently, if I take the first element of x5c array, base64 decode it and run the following SSL command, I get a valid cert.
echo -n "x5c 1st element value" | base64 -d > key.crt
openssl x509 -in key.crt -inform der -text

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 902058766 (0x35c4530e)
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN = Yubico U2F Root CA Serial 457200631
        Validity
            Not Before: Aug  1 00:00:00 2014 GMT
            Not After : Sep  4 00:00:00 2050 GMT
        Subject: C = SE, O = Yubico AB, OU = Authenticator Attestation, CN = Yubico U2F EE Serial 902058766
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:66:ae:cd:ae:25:18:8e:4a:23:97:00:58:41:84:
                    7f:65:ad:f1:f0:8b:04:23:fa:85:63:4a:bb:a9:86:
                    2e:14:2d:f7:b9:f4:09:df:2e:4e:5e:9e:06:af:7a:
                    17:39:e1:51:d5:77:90:30:b5:8a:d7:71:b5:5f:6c:
                    75:62:7e:2b:07
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            <IP_ADDRESS>.4.1.41482.2:
                <IP_ADDRESS>.4.1.41482.1.7
            <IP_ADDRESS>.4.1.457<IP_ADDRESS>:
                ...
            <IP_ADDRESS>.4.1.457<IP_ADDRESS>:
                ....(yr.I..u=....*
            X509v3 Basic Constraints: critical
                CA:FALSE

I think that's the certificate for the authentication device, when doing a full attestation check.
When calling navigator.credentials.create(options), the options['publicKey']['attestation'] will normally be set to 'none', to avoid the "Allow this site to see the make and model of your security key" permission check.
I doubt many sites will use this, unless you're going to be checking the full certificate chain, and checking that against your own list of hardware providers you trust (a bank might do this, but I doubt a typical website will care).

I think that's the certificate for the authentication device, when doing a full attestation check.
When calling navigator.credentials.create(options), the options['publicKey']['attestation'] will normally be set to 'none', to avoid the "Allow this site to see the make and model of your security key" permission check.
I doubt many sites will use this, unless you're going to be checking the full certificate chain, and checking that against your own list of hardware providers you trust (a bank might do this, but I doubt a typical website will care).

When calling navigator.credentials.create(options), the options['publicKey']['attestation'] will normally be set to 'none', to avoid the "Allow this site to see the make and model of your security key" permission check.

@craigfrancis , good to know! 👍

I doubt many sites will use this, unless you're going to be checking the full certificate chain, and checking that against your own list of hardware providers you trust (a bank might do this, but I doubt a typical website will care).

I think this could be handy.

When calling navigator.credentials.create(options), the options['publicKey']['attestation'] will normally be set to 'none', to avoid the "Allow this site to see the make and model of your security key" permission check.

@craigfrancis , good to know! 👍

I doubt many sites will use this, unless you're going to be checking the full certificate chain, and checking that against your own list of hardware providers you trust (a bank might do this, but I doubt a typical website will care).

I think this could be handy.

If you're a bank, and you're providing the devices to customers; or a company providing them to employees; you know the manufacturer, and that might be a useful feature.
But for most websites, who cares where the device came from?
This check also adds an extra step during the enrolment process (where some people, typically the ones who know more about this stuff, might wonder why you want to know).
It's also a step that might go wrong (in the future, more hardware manufacturers will hopefully exist, and it's possible that some might not get the attestation process quite right, as it's not used that often).
I also like how Apple suddenly started supporting this in Safari 14 via FaceID or TouchID, and I didn't have to add them to the list of my "approved" manufacturers (it just started working).

If you're a bank, and you're providing the devices to customers; or a company providing them to employees; you know the manufacturer, and that might be a useful feature.
But for most websites, who cares where the device came from?
This check also adds an extra step during the enrolment process (where some people, typically the ones who know more about this stuff, might wonder why you want to know).
It's also a step that might go wrong (in the future, more hardware manufacturers will hopefully exist, and it's possible that some might not get the attestation process quite right, as it's not used that often).
I also like how Apple suddenly started supporting this in Safari 14 via FaceID or TouchID, and I didn't have to add them to the list of my "approved" manufacturers (it just started working).

just in case someone find it ...
The sig field in the attestation object:
  "attestationObject": {
    "attStmt": {
      "alg": -7,
      "sig": "MEQCIBRQMm1GlRgK+7UQXYcuc0IWEsM9nWejSi0cyaQQUvDyAiBHw9BgPdt9tC7w5Itr29xFpodZgm8DvXFJnLOoys6GZw==",
...

gets decoded as follows. Big thanks to @francislavoie for the pointer to ASN.1 JavaScript decoder.

echo "MEQCIBRQMm1GlRgK+7UQXYcuc0IWEsM9nWejSi0cyaQQUvDyAiBHw9BgPdt9tC7w5Itr29xFpodZgm8DvXFJnLOoys6GZw==" | base64 -d > sig.bin
od -A x -t x1z -v sig.bin

The result follows.. The first 2 bytes (30 44) indicates it is a sequence (30 is sequence, see also SEQUENCE encoding
) of 68 bytes in length (44 hex is 68 decimal).
Then, there are 2 objects, each is 34 bytes in length. The first 2 bytes (02 20) indicates it is an integer (02) of 32 bytes length (20 in hex, or 32 in decimal).
000000 30 44 02 20 14 50 32 6d 46 95 18 0a fb b5 10 5d  >0D. .P2mF......]<
000010 87 2e 73 42 16 12 c3 3d 9d 67 a3 4a 2d 1c c9 a4  >..sB...=.g.J-...<
000020 10 52 f0 f2 02 20 47 c3 d0 60 3d db 7d b4 2e f0  >.R... G..`=.}...<
000030 e4 8b 6b db dc 45 a6 87 59 82 6f 03 bd 71 49 9c  >..k..E..Y.o..qI.<
000040 b3 a8 ca ce 86 67                                >.....g<
000046

just in case someone find it ...
The sig field in the attestation object:
  "attestationObject": {
    "attStmt": {
      "alg": -7,
      "sig": "MEQCIBRQMm1GlRgK+7UQXYcuc0IWEsM9nWejSi0cyaQQUvDyAiBHw9BgPdt9tC7w5Itr29xFpodZgm8DvXFJnLOoys6GZw==",
...

gets decoded as follows. Big thanks to @francislavoie for the pointer to ASN.1 JavaScript decoder.

echo "MEQCIBRQMm1GlRgK+7UQXYcuc0IWEsM9nWejSi0cyaQQUvDyAiBHw9BgPdt9tC7w5Itr29xFpodZgm8DvXFJnLOoys6GZw==" | base64 -d > sig.bin
od -A x -t x1z -v sig.bin

The result follows.. The first 2 bytes (30 44) indicates it is a sequence (30 is sequence, see also SEQUENCE encoding
) of 68 bytes in length (44 hex is 68 decimal).
Then, there are 2 objects, each is 34 bytes in length. The first 2 bytes (02 20) indicates it is an integer (02) of 32 bytes length (20 in hex, or 32 in decimal).
000000 30 44 02 20 14 50 32 6d 46 95 18 0a fb b5 10 5d  >0D. .P2mF......]<
000010 87 2e 73 42 16 12 c3 3d 9d 67 a3 4a 2d 1c c9 a4  >..sB...=.g.J-...<
000020 10 52 f0 f2 02 20 47 c3 d0 60 3d db 7d b4 2e f0  >.R... G..`=.}...<
000030 e4 8b 6b db dc 45 a6 87 59 82 6f 03 bd 71 49 9c  >..k..E..Y.o..qI.<
000040 b3 a8 ca ce 86 67                                >.....g<
000046

Oh, that's interesting... that's similar to the (erm, cheats way) I created the DER encoding of the public key:
https://github.com/craigfrancis/webauthn-tidy/blob/85b8f53648a628e0a8f1866d450960008b18a75c/new/js/polyfill.js?ts=4#L483
Where my prefix is used to say it's DER encoded, ecPublicKey, using prime256v1, followed by the key value, marked ECC uncompressed.
With your signature, with its two 32 byte integers, what are they? values r and s?
https://tools.ietf.org/html/rfc3279#page-21
https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm#Signature_generation_algorithm
It's as this point I struggle to follow the calculations, assume it's all correct, and store the base64 encoded value :-)

Oh, that's interesting... that's similar to the (erm, cheats way) I created the DER encoding of the public key:
https://github.com/craigfrancis/webauthn-tidy/blob/85b8f53648a628e0a8f1866d450960008b18a75c/new/js/polyfill.js?ts=4#L483
Where my prefix is used to say it's DER encoded, ecPublicKey, using prime256v1, followed by the key value, marked ECC uncompressed.
With your signature, with its two 32 byte integers, what are they? values r and s?
https://tools.ietf.org/html/rfc3279#page-21
https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm#Signature_generation_algorithm
It's as this point I struggle to follow the calculations, assume it's all correct, and store the base64 encoded value :-)

With your signature, with its two 32 byte integers, what are they? values r and s?

@craigfrancis , that's the question I am asking myself right this moment 😃 That's why it is fun to explore :-)

With your signature, with its two 32 byte integers, what are they? values r and s?

@craigfrancis , that's the question I am asking myself right this moment 😃 That's why it is fun to explore :-)

Closing. Need to find time to get back to webauthn.


Release 1.3.0.Beta25

Summary
Releases 1.3.0.Beta25. Release contains:

https://github.com/quarkus-qe/quarkus-test-framework/pull/856
https://github.com/quarkus-qe/quarkus-test-framework/pull/857
https://github.com/quarkus-qe/quarkus-test-framework/pull/859
https://github.com/quarkus-qe/quarkus-test-framework/pull/860
https://github.com/quarkus-qe/quarkus-test-framework/pull/861
https://github.com/quarkus-qe/quarkus-test-framework/pull/863
https://github.com/quarkus-qe/quarkus-test-framework/pull/864

Please check the relevant options

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[ ] Refactoring
[x] Release
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[ ] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[ ] Example scenarios has been updated / added
[ ] Methods and classes used in PR scenarios are meaningful
[ ] Commits are well encapsulated and follow the best practices

I'm not going to run OC because I just waited to finish OC run for https://github.com/quarkus-qe/quarkus-test-framework/pull/864 and it's absolutely same code. No point.


Open sans font

Implements Open Sans per new design spec.
closes #581

[Current coverage][cc-pull] is 69.01%

Merging [#590][cc-pull] into [develop][cc-base-branch] will not change coverage

@@            develop       #590   diff @@
==========================================
  Files            37         37
  Lines          1336       1336
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            922        922
  Misses          414        414
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [f02e3c2...590af54][cc-compare]
[cc-base-branch]: https://codecov.io/gh/Solinea/goldstone-server/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/Solinea/goldstone-server/compare/f02e3c299ded2b66c2999ae1b4bc13990ef6a720...590af5496f8ef74dbc9d1d0e821d64a2c6f9a412
[cc-pull]: https://codecov.io/gh/Solinea/goldstone-server/pull/590?src=pr

👍


gh-pages branch - viewport minimal-ui breaks page on Safari 9.0.1

The page http://www.chartjs.org/docs/ breaks with error Viewport argument key "minimal-ui" not recognized and ignored. on the following line of HTML (docs.html:6:104)
<meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0, minimal-ui">

The broken page screenshot on Safari 9.0.1 running on El Capitan 10.11.1:

minimal-ui has been deprecated by Apple since iOS 8.0 SDK - source under "WebKit".
Tested this on different user accounts and clean installations of Safari (iOS and OS X). It is worth noting that the error is clearly coming from Safari itself (exception on deprecated WebKit option). This issue is non-existent in any version of Chrome.

I've cloned the charts repository and I'm currently testing locally on the gh-pages branch on several Safari versions.
A pull request will be opened some time next week (if someone else doesn't get to it before I do).

Replacing that meta tag to
<meta name="viewport" content="width=device-width, initial-scale=1.0">

Didn't fix it for me

According to #1678 this is related to the CSS. I can fix the gh-pages branch but only @nnnick can fix the deployed site until #1658 is dealt with.

I've fixed the CSS on the gh-pages branch.

@etimberg this is still unfixed

@thebearjew my understanding is that this has been fixed on the github pages site, https://nnnick.github.io/Chart.js/ but only @nnnick can change chartjs.org

Ah, that is much more clear.
Thank you, I'll use the gh-pages branch instead.


Refs 2675: rename kafka-consumer deployment

Summary
Rename the kafka-consumer deployment prior to adding alerting around the pods
Testing steps
tests pass?
Checklist

[x] Tested with snapshotting feature disabled and pulp server URL not configured if appropriate

https://issues.redhat.com/browse/HMS-2675

/retest

Going ahead and merging as the failed iqe test is unrelated.


New version: SASLib v1.1.0

Registering package: SASLib
Repository: https://github.com/tk3369/SASLib.jl
Created by: @tk3369
Version: v1.1.0
Commit: 853eb78bda40259b2ee471d4c1a1796bed96d55c
Reviewed by: @tk3369
Reference: https://github.com/tk3369/SASLib.jl/commit/853eb78bda40259b2ee471d4c1a1796bed96d55c#commitcomment-36645539

@tk3369 Can you please add the compat entries? You may find CompatHelper helpful.
[noblock]

Yes, added now 👌


Ensure that updating query limits are handled correctly

clarification?

I just got the impression that we weren't 100% confident about #415, so this serves as a reminder to make sure it captures the logic correctly.  Feel free to close if you think we're good.

I'll write a few tests here


Remove version: SmartSoft.SmartFTP version 10.0.3190.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://static.smartftp.com/static/Products/Client/10.0.3190.0/x64/SmartFTP.msi
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 912)


Revert "MAINT: Add a --debug pdb to allow easier line-by-line debugging"

Reverts nipreps/fmriprep#2871
Testing whether this resolves the ds054 error.

There's definitely something in the PR. Commenting on #2876


feat: finalize onchain color voting

[x] issue #14
[x] follows contribution guide
[x] code change includes tests
[x] breaking change

This PR finalize onchain voting.
At end of each day, most voted colors will be added to color palette.

Thank you for making those changes!


Version 2023-08-15 Section 12.8.2 (RJMCMC example) typos

Either substitute \alpha with \beta in equation (12.139)  at p531 (latex page 563/1354) (quickest fix)

Or, at p532 (latex page 564/1354):

above equation (12.141): we require $|| \mu_1 - \mu_2|| < 2 \alpha $ instead of 2 \beta
(12.142) \beta should be \alpha
below (12.142): should be "| \det J_{split} |= 2\alpha" instead of 2 \beta
below (12.143):  should be "where |det J_{merge} | = 1/(2\alpha)" instead of \beta

thanks


Add support for protocol-rooted URL as "next_page" argument for _logout_url constructor

This request adds support for passing a protocol-rooted url (http://example.com) to the _logout_url function, instead of assuming that all redirect targets are rooted to the same host as the service from which you are logging out.

This is, admittedly, a "hacky" solution. Ideally, I'd like to implement something that actually validates the URL.

Thanks!


so many error when compiling on windows with visual studio

hello, I have compiled the source code on windows/visual studio after configured with cmake, there are so many errors, such as(there are more than 500 errors):
Severity	Code	Description	Project	File	Line	Suppression State
Error		the global scope has no "posix_memalign"	mkldnn
Severity	Code	Description	Project	File	Line	Suppression State
Error		identifier "jit_conv_call_s" is undefined	mkldnn
void operator()(jit_bnrm_call_s *arg) { jit_ker(arg); }
Severity	Code	Description	Project	File	Line	Suppression State
Error		more than one conversion function from "lambda ->mkldnn::c_api::mkldnn_primitive_desc_t" to "" applies:	simple-net-cpp	C:\myproject\intel\caffe\external\mkldnn\include\mkldnn.hpp	594
............................................................
anyone compiled the source code successfully on windows? thanks.
I have installed the intel xe 2017(with c++ compiler) evaluation, and tried to compile it with intel c++, but still failed.

Windows is not yet supported. See issue #10 for additional discussion.


Server crashes on connect with missing cert error

We just updated to the latest version of Valheim and now the server crashes every time we try to connect with the following error (in the logs):

valheim | src/steamnetworkingsockets/clientlib/steamnetworkingsockets_p2p.cpp (338) : Assertion Failed: GetState() == k_ESteamNetworkingConnectionState_ProblemDetectedLocally
valheim | src/steamnetworkingsockets/clientlib/steamnetworkingsockets_connections.cpp (2473) : Assertion Failed: [#4142063336 P2P steamid:76561197984411869] problem (5002) We don't have cert, and self-signed certs not allowed, but connection already dead (0 5002 We don't have cert, and self-signed certs not allowed)

We're running the docker image within an Azure VM.

I just tried to reproduce but can't. Started a fresh container, it starts up and downloads with
...
 Update state (0x61) downloading, progress: 99.20<PHONE_NUMBER> /<PHONE_NUMBER>)
Success! App '896660' fully installed.

server starts with
...
02/26/2021 09:24:36:  Done generating locations, duration:28941.649 ms
02/26/2021 09:24:36: DungeonDB Start 506

and when I connect I get
02/26/2021 11:17:02: Connecting to Steamworks.SteamNetworkingIdentity
02/26/2021 11:17:02: Got status changed msg k_ESteamNetworkingConnectionState_FindingRoute
...
02/26/2021 11:17:04: Got handshake from client<PHONE_NUMBER>7220805
...
02/26/2021 11:17:08: VERSION check their:0.146.11  mine:0.146.11
02/26/2021 11:17:08: Server: New peer connected,sending global keys
...
02/26/2021 11:17:21: Got character ZDOID from Luu : 724918021:1

and the client loads into the world.
Maybe some intermittent issue?
The error is produced in CSteamNetworkConnectionBase::BRecvCryptoHandshake  specifically
https://github.com/ValveSoftware/GameNetworkingSockets/blob/8b678e4f6721d5ac3105e5b53fc9aa9c4089856e/src/steamnetworkingsockets/clientlib/steamnetworkingsockets_connections.cpp#L1559-L1577
If the issue persists and you're inclined to debug it further that's where I'd start tracing back the cause.

A new version of Valheim was released today and the changelog lists
* Fixes instant disconnection issue that some players have experienced.

@trevorloflin can you check if the update fixes your connection issue?

It looks initially like I'm still getting the same error. I'm going to dig deeper and see if I can get you more info.

seems i posted a possible linked issue?

src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1276) : Assertion Failed: SDR service thread gave up on lock after waiting 55ms.  This directly adds to delay of processing of network packets!
stdout

even with a fresh install on the server same issue.

Here are the logs of the server starting up:
2021-02-26 09:41:16,422 INFO spawned: 'valheim-server' with pid 490
Running Valheim Server
ERROR: ld.so: object 'libdoorstop_x64.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Found path: /opt/valheim/plus/valheim_server.x86_64
Mono path[0] = '/opt/valheim/plus/valheim_server_Data/Managed'
Mono config path = '/opt/valheim/plus/valheim_server_Data/MonoBleedingEdge/etc'
Preloaded 'libsteam_api.so'
Initialize engine version: 2019.4.20f1 (6dd1c08eedfa)
[Subsystems] Discovering subsystems at path /opt/valheim/plus/valheim_server_Data/UnitySubsystems
Forcing GfxDevice: Null
GfxDevice: creating device client; threaded=0
NullGfxDevice:
    Version:  NULL 1.0 [1.0]
    Renderer: Null Device
    Vendor:   Unity Technologies
Begin MonoManager ReloadAssembly
- Completed reload, in  0.057 seconds
2021-02-26 09:41:17,526 INFO success: valheim-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
valheim-server: started
UnloadTime: 0.925900 ms
02/26/2021 09:41:18: Starting to load scene:start
HDR Render Texture not supported, disabling HDR on reflection probe.
HDR Render Texture not supported, disabling HDR on reflection probe.
Unloading 6 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 4.615800 ms
Only custom filters can be played. Please add a custom filter or an audioclip to the audiosource (Amb_MainMenu).
HDR Render Texture not supported, disabling HDR on reflection probe.
02/26/2021 09:41:39: Initializing world generator seed: ( 0 )   menu:True  worldgen version:1
02/26/2021 09:41:39: Using mountain distance: 1000
02/26/2021 09:41:39: Render threading mode:SingleThreaded
02/26/2021 09:41:39: Get create world [excised]
02/26/2021 09:41:39: Using environment steamid 892970
02/26/2021 09:41:39: Using steam APPID:892970
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 1 milliseconds to initialize
CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
RecordSteamInterfaceCreation (PID 494): SteamGameServer013 /
RecordSteamInterfaceCreation (PID 494): SteamUtils009 /
Setting breakpad minidump AppID = 892970
RecordSteamInterfaceCreation (PID 494): SteamGameServer013 / GameServer
RecordSteamInterfaceCreation (PID 494): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 494): SteamNetworking006 / Networking
RecordSteamInterfaceCreation (PID 494): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 494): STEAMHTTP_INTERFACE_VERSION003 / HTTP
RecordSteamInterfaceCreation (PID 494): STEAMINVENTORY_INTERFACE_V003 / Inventory
RecordSteamInterfaceCreation (PID 494): STEAMUGC_INTERFACE_VERSION014 / UGC
RecordSteamInterfaceCreation (PID 494): STEAMAPPS_INTERFACE_VERSION008 / Apps
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded.
RecordSteamInterfaceCreation (PID 494): SteamNetworkingUtils003 /
RecordSteamInterfaceCreation (PID 494): SteamNetworkingSockets008 /
Warning: failed to set thread priority: set failed for 8: -1: setpriority() failed
Warning: failed to set thread priority: set failed for priority 8
Warning: support for elevated priorities is most likely unavailable, suppressing future warnings
02/26/2021 09:41:39: Server ID [excised]
02/26/2021 09:41:39: Authentication:k_ESteamNetworkingAvailability_Waiting
02/26/2021 09:41:39: Steam game server initialized
02/26/2021 09:41:39: Missing audio clip in music respawn
02/26/2021 09:41:39: Builder started
02/26/2021 09:41:40: Loaded localization English
02/26/2021 09:41:40: Game server connected
Unloading 16 unused Assets to reduce memory usage. Loaded Objects now: 85969.
Total: 64.870700 ms (FindLiveObjects: 4.164900 ms CreateObjectMapping: 11.090200 ms MarkObjects: 49.317700 ms  DeleteObjects: 0.292800 ms)
Unloading 6 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 13.151600 ms
HDR Render Texture not supported, disabling HDR on reflection probe.
HDR Render Texture not supported, disabling HDR on reflection probe.
02/26/2021 09:41:41: Zonesystem Awake 299
02/26/2021 09:41:41: DungeonDB Awake 299
02/26/2021 09:41:41: Registering lobby
02/26/2021 09:41:41: Initializing world generator seed:XmPw65WVCl ( -1570306369 )   menu:False  worldgen version:1
02/26/2021 09:41:41: Using mountain distance: 1000
02/26/2021 09:41:41: Found 565 mountain points
02/26/2021 09:41:41: Remaining mountains:80
02/26/2021 09:41:41: Calc time 29.413 ms
02/26/2021 09:41:41: Found 8075 lake points
02/26/2021 09:41:43: Remaining lakes:117
02/26/2021 09:41:43: Calc time 2623.892 ms
02/26/2021 09:41:43: Rivers:152
02/26/2021 09:41:44: River buckets 14713
02/26/2021 09:41:44: River render time 353.707 ms
02/26/2021 09:41:44: River Calc time 370.493 ms
02/26/2021 09:41:45: River buckets 23797
02/26/2021 09:41:45: River render time 609.341 ms
02/26/2021 09:41:45: Placed 1919 streams
02/26/2021 09:41:45: Stream Calc time 1369.488 ms
02/26/2021 09:41:45: Load world [excised]
02/26/2021 09:41:45: Loading 81 zdos , my id 497102565 data version:26
02/26/2021 09:41:45: Loaded 0 dead zdos
02/26/2021 09:41:45: Removed 0 OLD generated ZDOS
02/26/2021 09:41:45: Loaded 7141 locations
02/26/2021 09:41:45: Audioman already exist, destroying self
Unloading 490 unused Assets to reduce memory usage. Loaded Objects now: 86302.
Total: 85.562000 ms (FindLiveObjects: 4.541000 ms CreateObjectMapping: 10.351200 ms MarkObjects: 66.980300 ms  DeleteObjects: 3.684000 ms)
02/26/2021 09:41:49: Zonesystem Start 299
02/26/2021 09:41:50: DungeonDB Start 299

After more testing and thinking, I think this issue doesn't have anything to do with the docker image. It has to be some weird interaction between my OS and the Valheim server software. I'm gonna close this so it doesn't clutter your list up.


⚠ Bofrost.de has degraded performance

In 8ef0b84, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1222 ms

Resolved: Bofrost.de performance has improved in 2d59cc1 after 1 hour, 6 minutes.


Support for java 10

Expected behavior
Should be able to run the specification without any errors/warnings.
Actual behavior
Get the fallowing warnings
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/Users/apoorvag/.gauge/plugins/java/0.6.8/libs/protobuf-java-3.3.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Steps to reproduce

Install Java 10
init gauge java template using gauge init java
run gauge run secs

Gauge version
Gauge version: 1.0.1
Commit Hash: 8281d03

Plugins
-------
java (0.6.8)
screenshot (0.0.1)
html-report (4.0.5)

Duplicate of https://github.com/getgauge/gauge-java/issues/149


ARXML: extract bus information

This internalizes the information about the CAN buses which can be provided by ARXML files. most of the infrastructure was already present, the exception is the FD baudrate which was not around, supposedly because the base DBC file format (probably) does not support CAN-FD.
Besides this, I added the file format version of the input file to the autosar specifics of the database and cleaned up the message loading code slightly (to avoid using nested functions).
Andreas Lauser<EMAIL_ADDRESS>on behalf of MBition GmbH.
Provider Information

@juleq: as usual; merge at will

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

122 of 131 (93.13%)  changed or added relevant lines in 5 files are covered.
213 unchanged lines in 19 files lost coverage.
Overall coverage decreased (-2.6%) to 92.648%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cantools/database/can/message.py
2
3
66.67%

cantools/database/can/signal.py
2
3
66.67%

cantools/subparsers/list.py
30
31
96.77%

cantools/database/can/bus.py
14
17
82.35%

cantools/database/can/formats/arxml.py
74
77
96.1%

Files with Coverage Reduction
New Missed Lines
%

cantools/database/can/formats/arxml.py
1
93.5%

cantools/database/diagnostics/database.py
1
93.62%

cantools/subparsers/plot.py
2
97.58%

cantools/tester.py
2
93.37%

cantools/database/can/bus.py
3
80.65%

cantools/database/can/attribute.py
4
77.78%

cantools/database/can/formats/dbc.py
5
98.38%

cantools/database/can/node.py
6
76.0%

cantools/database/can/signal_group.py
6
72.0%

cantools/logreader.py
6
92.45%

Totals

Change from base Build<PHONE_NUMBER>:
-2.6%

Covered Lines:
5595

Relevant Lines:
6039

💛  - Coveralls


Update role_playing_with_function.py

Description
In role playing with function call, give the user agent the information about function can allow user to instruct the assistant agent to use which function, and the confuse phenomenon also  has disapeared.
Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
You can use the syntax close #15213 if this solves the issue #15213

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[x] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

Hi @zhiyu-01. Thanks for the PR. But why we can the user agent has access to the tools here?

To let the user know what ability the assistant have, and it was found in practice that it can eliminate the confuse of the user, which  I have met in #298 .


[wip] onnx running top 100 huggingface models

Downloading many GBs over a slow internet, over a vpn, is no fun 🫠 .
extra/datasets/onnx_model_download.py this is the file. Can use MODEL=google-bert/bert-base-uncased for running individual models
I also have a few other PRs included in this (including #8109 lol I forked it) that I will see to get merged first.
This currently passes with PYTHONPATH=. python extra/datasets/onnx_model_download.py
We currently test the POTENTIAL_MODEL_PATHS. So we aren't testing quantized or encoder stuff or other things I don't understand :D  (gonna try running them to try to understand them)
We do skip some models for ORT verification (ort failure) and 2 other models that have missing OP implementation.
There are a few problems I ran into while working on this:

some models have a whole pipeline of different models like https://huggingface.co/stabilityai/stable-diffusion-xl-base-1.0. The implementation of the pipeline cannot be generic/shared unfortunately
get_input is not robust at all. It was the naive randn with value 1 as variable shape before (where we get gather oob error and all nan output), so I have made it a bit better. But lets say when new month starts and new models start appearing, this get_input is likely to fail.

Yeah....
Not sure how this would be tested in CI....

i think it's fine to keep a file of a fixed 100 models, and make it very easy to update with a script, and we can monitor if anything failed when we try to update the model list.
fixed dlownloaded models go into cache so ci should be good

How many GB is it? What's the distribution of sizes?

How many GB is it? What's the distribution of sizes?

10-100 MB: 5 files
100 MB - 1 GB: 59 files
1 GB - 2 GB: 18 files
2 GB - 5 GB: 11 files
5 GB: 1 files
80G    /Users/zibo/Library/Caches/tinygrad/downloads


Define docker image endpoint

Followup on #8 : will fix docker building, and also add an endpoint script that flexibly deploys this on provided input data.

Closed in favor of #10