squash doc history in separate task

Squashes document history in a separate scheduled task rather than on write. This will significantly improve performance for document writes in the case where the time since last update exceeds the document TTL.
Open concerns

Is there any good way of stubbing out asyncio.sleep() in the unit tests? Testing this is tricky because it's not as simple as doing unittest.mock.patch("asyncio.sleep"), since that causes the document history to be squashed on every write. What I'm looking for is a utility that lets me imperatively advance the event loop clock, e.g. loop.advance(123). I found asynctest, but it doesn't seem to work and is abandoned.

I like that we don't need to query the last timestamp anymore.This should now make it easy to implement document TTL for FileYStore. Do you want to do it?
One thing I'm concerned about is what happens if there is a write at the same time as we're squashing updates? Could you add a test for that?

@davidbrochart

I like that we don't need to query the last timestamp anymore.This should now make it easy to implement document TTL for FileYStore. Do you want to do it?

Oh yeah, totally forgot about that. Let me do so.

One thing I'm concerned about is what happens if there is a write at the same time as we're squashing updates? Could you add a test for that?

Should be the exact same behavior as a write occurring after a squash, since aiosqlite essentially just stores SQL statements in a queue and polls from it whenever it's finished executing the current one. But yes, I can add a test for this.

@davidbrochart Wait, we still need a timestamp if we want to handle the case where the server is not kept alive during a document's TTL. Take this scenario:

add a bunch of updates
shut down the server
repeat

In this scenario, the document history grows without bound. I think we need to handle this case as it's fairly common for users running Jupyter locally on a laptop (in which case disk space is also tight), but I'd like @ellisonbg's opinion on this matter as well.

To handle the above case, we'd need to squash on __init__() and do the same query we were doing before.

I agree we do need the timestamp in cases where the server restarts, but why wouldn't we need it otherwise? I am trying to understand the logic here. My idea of how this would work is this:

Every so often (configurable) the background task check to see how long ago the last update for a document was made.
If that time interval is longer than the TTL (also configurable) delete the history.

This logic is needed to ensure that this cleanup doesn't happen while users are editing it.

In the current state of the code, is the idea that you simply count the number of updates to the doc and if it hasn't changed in the TTL then you collapse?

@ellisonbg The implementation in this PR basically just creates a task that sleeps for the duration of the document TTL and then squashes the document history . Any updates cancel the existing task and create a new task. Therefore having a process repeatedly querying the database isn't needed, and thus the timestamp isn't needed for this case. This is how cron is typically implemented.

I think the key question here is this: when is it safe to squash the history?
Here is my understanding (@davidbrochart please add more details or correct any inaccuracies here). When the first user opens a document, the full state of the document is loaded into the memory of the server. As that user makes changes, updates are 1) forwarded to other users, 2) stored in the db, 3) applied to the in memory document on the server. The server is unable to distinguish between users closing the document or network disruptions (both of these appear as network disconnections). The database is used when a client disconnects and reconnects to get them any missing updates. When all clients have been disconnected for a certain amount of time (I think 1m be default) the state of the document is flushed from memory. The db is also used the next time a user opens the document after it is flushed from memory.
The failure mode of squashing history is that we would squash updates that are needed by a user. Let's imagine the following scenario:

N users have the document open and are editing it.
User 1 closes their laptop and goes to lunch at 12 noon local time. This is registered as a client disconnect.
While user 1 is at lunch, other users edit the document and generate new updates.
At 12:59, updates are squashed.
At 1:00, user 1 returns and opens their laptop. At this time, the updates needed by that user no longer exist and have been squashed.

A few questions:

What will actually happen in this case. Is everything smart enough to detect this and still reassemble the current state of the document?
To cover situations like this safely, do we need to run the history squashing during periods of long inactivity. We could determine this by waiting some (long) period of time after all clients disconnect.
Another way we could mitigate this risk is to do more granular history squashing. For example, rather than squashing all the history, we could squash the history into days, and only for days older than 1 week. That way, users would always have the full history for a week, and then daily beyond that.

As that user makes changes, updates are 1) forwarded to other users, 2) stored in the db, 3) applied to the in memory document on the server.

That's correct, just mentioning that 3) is the cause of 1) and 2). We apply changes from the clients to the "server peer", and listen to changes made on this peer to broadcast them to clients and store them.

The database is used when a client disconnects and reconnects to get them any missing updates.

Yes, but only if no client is accessing the document for some time. It there is at least one client accessing the document, the missing updates will be sent to new clients from memory, as the in-memory document would still be present.

At 1:00, user 1 returns and opens their laptop. At this time, the updates needed by that user no longer exist and have been squashed.

Unless the document is still in memory, in which case user 1 will get the full history of changes. Otherwise, yes they will get a document with no history, but I think this is the desired behavior.
The document is kept in memory if at least one user is accessing it, and for some time after all clients disconnect from this document.
If we agree on this, I think your questions don't apply anymore, right?

At 1:00, user 1 returns and opens their laptop. At this time, the updates needed by that user no longer exist and have been squashed.

Oh I see your point. Let's assume that updates have been flushed from memory to disk, and squashed.

What will actually happen in this case. Is everything smart enough to detect this and still reassemble the current state of the document?

No, I don't think it will give user 1 its missing updates. I will give them a big update consisting of the whole document, leading to content duplication.

To cover situations like this safely, do we need to run the history squashing during periods of long inactivity. We could determine this by waiting some (long) period of time after all clients disconnect.

Yes, the point being making sure that all clients closed their document in the front-end, i.e. willingly disconnected.

Another way we could mitigate this risk is to do more granular history squashing. For example, rather than squashing all the history, we could squash the history into days, and only for days older than 1 week. That way, users would always have the full history for a week, and then daily beyond that.

True, although this will never eliminate the risk.
Actually the real solution would be to do what Kevin once suggested: introduce the notion of document session. If the user disconnects for too long, invalidate the session and force the deletion of the document in the front-end, and recreate it from the back-end.

@davidbrochart Revision summary:

Fixed test flakiness by awaiting the squash task directly in tests rather than doing await asyncio.sleep(ystore.document_ttl + 0.1)
Added test for behavior with a simultaneous write occurring at document TTL

Not sure how useful this is, given that this tests the execution order of tasks scheduled to run at the same tick of the event loop, which is likely undefined behavior in Python. Right now, it appears that an update written at the document TTL is included in the squash.

Squash updates on init by doing the same timestamp query we were doing before

Thanks for tagging this issue in #14031 @davidbrochart - I am not familiar with all the details, but it seems indeed that some very robust logic for invalidation and full document refresh in the frontend is necessary. Google Docs evidently does that on occasion - I've had it tell me that my document was stale and forced a reload, after refusing any more edits into a doc.
I'm spitballing here, not knowing the implementation details, but it seems to me that any squashing should be done "behind a barrier" - a point in the history that defines a fixed state that updates can't traverse with any granularity. Anyone needing to sync state across that barrier simply needs to re-sync to the state at the barrier, and then get the updates after that.
I'll come to the team meeting tomorrow and hopefully we can discuss this a bit. I was willing to dogfood RTC in production for a bit, but at this point I may need to pull the plug unless we find a viable solution path quickly, as I can't really tolerate any data loss/damage in that environment. It would be a shame to lose the opportunity of this environment for real-world feedback on various aspects of UX and performance, so 🤞 that we can figure this out :)


Fix/Remove delete league from settings tab

The delete league link under the settings tab in the league dashboard needs to be removed.

@makkoli   I'm fairly new contributing so let me know if I can work on this.

@vikramnr Feel free to work on this and don't be afraid to ask for help if you need it.

@makkoli  👍

@makkoli   Should I also remove the form for delete league?

Yeah, we won't be needing that anymore.

@makkoli May I ask why the ability to remove a league was taken away?

FCC decided they didn't want to have that option available. They didn't want admins to delete leagues and lose all the data associated with them.

@makkoli: That makes sense.  Is there still a need for admins to send a housekeeping request?
FCC could keep the data but create a new record cloning the same data with the changes.
ie "Click here to request League Rename"
"Click here to request Remove League Listing"


Win10 launchClient build failure

What went wrong:
A problem occurred evaluating root project 'Minecraft'.

Failed to apply plugin [id 'net.minecraftforge.gradle.forge']
Unable to obtain url ([https://launchermeta.mojang.com/mc/game/version_manifest.json]) with etag!

I cannot visit the site launchermeta.mojang.com even on Edge browser. It seems that I cannot access this page.

@RockmanZheng I solved this problem by referring to this site: https://plugins.gradle.org/plugin/net.minecraftforge.gradle.forge  （Build script snippet for plugins DSL for Gradle 2.1 and later）

@hexiaobing5880 Thanks for your response. I will close this thread once I figure it out with your advice. Thank you again for your clue.

@hexiaobing5880 I copied the code in the website you gave me into build.gradle. Things can be downloaded with this change. But another error occurred.
There are no mappings for MC 1.11.2
In build.gradle, minecraft{...}, version = "1.11.2-<IP_ADDRESS>8" and mappings = "snapshot_20161220" seems to be mismatched.

No. But I work around this issue by install Malmo on Ubuntu 16.04 (Linux system). @fixbut

Tracking under #714. Some people are still having problems getting the mappings.


Allow grouping of Findings (and push to JIRA)

This PR introduces the concept of groups of findings (Finding Group). The main reason to introduce this concept is to be able to group findings together before pushing them to JIRA as one JIRA ticket. For example when you have multiple vulnerabilities in a dependency. You still want to see all separate dependencies in Defect Dojo with their CVE, CWE, severity, etc. And also be able to use deduplication and reimport as usual.
At first I tried using the merge functionality in Defect Dojo, but it doesn't always work well with deduplication nor with Reimport. So I chose to introduce this concept. It can be used for other stuff as well in the future, for now the main reason is to group vulnerabilities together into 1 JIRA ticket.
Some automatic grouping could be implemented in the future:

automatically group findings by component_name
additionally push these groups to JIRA automatically (or manually)
group findings that are in the same advisory

To use the finding groups you need to enable a feature flag: FEATURE_FINDING_GROUPS or DD_FEATURE_FINDING_GROUPS
To make it work with the webhook, notes, jira pushing, findings list, etc. I touched quite a bit of code. The good thing is that all our unit tests and integration tests still work. The bad thing is that it will require quite a chunk of time to add tests for the finding groups feature. So that's why I have hidden it behind a feature flag, and propose to do some dogfooding in dev before we release it. So I suggest target release 1.15.0 end of April.
I also like to get some feedback from others before investing more time. I need to know this is something we want to keep and expand.
This PR also introduces a second django template, which is used to generate the description of the JIRA issue for the finding group: issue-trackers/jira_full/jira-finding-group-description.tpl. I have moved the 'full' and 'limited' templates in their own subfolders so we still have only one selection to make in the JIRA Project config of a Product/Engagement. This is a breaking change for people who have configured non-default JIRA templates in their instance. I expect this affects not many people.
I added some API methods / fields to be able to retrieve the finding_group for findings and filter on them.
Bugfixes along the way:

#4118

Locally tested push and also the webhook coming back, seems to work fine. Remains a couple of minor things to finalize that first iteration, but looks good so far :+1:  Thanks!

Also, I would not show column "Group" is all findings are to the N value.


Can't perform a React state update on an unmounted component.

When unmounting ImageViewer quickly, i.e before image appears, I get
Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.

same！
memory leak make my image list show blank
it‘s a emergency question！

sorry I GOT something wrong，I use tab navigation，and use it to navigate to gallary page ，and when i came back i got this  probrem ，SO the keypoint is，don‘t use navigation ，use modal and open this component in onepage if you use tab navigation（because the tabpage will never get destroy when app running）！ how to resolve it????  @ascoders

how to resolve it at last? @blackjack0v0 @io-pan

Same Here!
    "react": "16.9.0",
    "react-native": "0.61.4",
    "react-native-scrollable-tab-view": "1.0.0",

index.bundle?platfor…&minify=false:29307 Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
in ImageViewer (at CustomSlider.js:38)
in RCTView (at AppContainer.js:101)
in RCTView (at AppContainer.js:119)
in AppContainer (at Modal.js:250)
in RCTView (at Modal.js:271)
in RCTModalHostView (at Modal.js:258)

It's late but for anyone who has the same issue, putting the width and height of images will fix it, also optimize performance.

Putting width and height with url doesn't solve the issue for me, P.S I can't see loading indicator after putting width and height. this library has many state updating issues, I get Warning: Cannot update during an existing state transition (such as within 'render'). Render methods should be a pure function of props and state. also when scrolling quickly through the images.

same here


Multiple issues cause by Vispy versioning

🐛 Bug
Lately we had several people report problems that were tricky to debug due to weird vispy stack traces.
Ultimately, several of them were caused by the fact that we (me being a major culprit...) have been pushing many updates in vispy that changed the internals of visuals. These changes were to a point that the patches we do here in napari (a recurring problem being our specialized Labels isosurface rendering) need to be updated accordingly.
This, combined with the fact that so far we're been pinning only a minimum version for vispy, results in a lot of people installing non-dev versions of napari with a vispy version that's incompatible.
What do people think about pinning an exact version of vispy to solve this problem?

#4570
#4415
#4548

Another thing that we should do is:

#3771

To clarify, this means that no matter what we do on the napari side now, if a new version of vispy comes out that's incompatible with an existing napari version, users will get these cryptic errors, with the nly solution being releasing a new napari version that fixes it.

If I good understand these problems comes from vispy 0.10.0. So maybe it will be enough to pin vispy <= 0.11.0?

But we also regularly depend on newer versions of vispy to implement new functionality. so in practice most of the times we have a minimum vispy version that's very recent (0.10.0 in current main, but it's 0.9 on the current latest release) and at the same time we have to preemptively lock upper version in case new stuff breaks (which as I mentioned, has been happing somewhat regularly lately). So you'd end up with vispy=>0.10.0,<=0.11.0, which is the same as pinning :P

So you'd end up with vispy=>0.10.0,<=0.11.0, which is the same as pinning :P

no, because 0.10.1 may introduce bugfix or new features without breaking API. It is different to vispy==0.10.0.
Strict pinning requires politics for release new versions of napari when bugfix of strictly pinned library is released.
For example, some time ago all release of hsluv was removed from pypi (it looks like some try of account higjack).
They restore it but cannot recovery old versions because of single upload policy on pypi. So if any project has strict pinning of hslav then its installation is broken until new project release: pypi.org/project/hsluv/#history

But we can pin with ~=0.10, and it should, right?

@brisvag @Czaki your constraints are equivalent. I find >=0.10.0,<0.11 to be the most readable. But, annoyingly, neither version will fix #4589! Can someone weigh in on whether that means we should do a hard pin, or update something on our end to make things compatible with vispy 0.10.x?

(Also note <0.11, not <=0.11.)

@jni What do you mean neither version will fix it? Tghat bug should not happen with 0.10.0, but only if you use dev. To fix #4589 NOW we have to replace $sample with $get_data in the gatecorical isosurface shader. However, that would require the next vispy version to be out, so that's the problem :P


escape usage in markdown

Usage doesn't render properly on Github unless we escape the <>

Thanks for noticing this. I fixed it in 052cb33cdc02235197e3c791a4be63a6c13f0a2b, and I made sure to give you credit.


Convert several tests to use netutil.CommonTrafficQueues

Pull Request Functional Test Report for #1777 / c23b1b5f2f939c63eedce61f664ea7f4d068cc62
Virtual Devices

Device
Test
Test Documentation
Job

Arista cEOS

DP-1.7: One strict priority queue traffic testDP-1.14: QoS basic testDP-1.4: QoS Interface Output Queue CountersDP-1.11: Bursty traffic test

Cisco 8000E

DP-1.7: One strict priority queue traffic testDP-1.14: QoS basic testDP-1.4: QoS Interface Output Queue CountersDP-1.11: Bursty traffic test

Cisco XRd

DP-1.7: One strict priority queue traffic testDP-1.14: QoS basic testDP-1.4: QoS Interface Output Queue CountersDP-1.11: Bursty traffic test

Juniper cPTX

DP-1.7: One strict priority queue traffic testDP-1.14: QoS basic testDP-1.4: QoS Interface Output Queue CountersDP-1.11: Bursty traffic test

Nokia SR Linux

DP-1.7: One strict priority queue traffic testDP-1.14: QoS basic testDP-1.4: QoS Interface Output Queue CountersDP-1.11: Bursty traffic test

Openconfig Lemming

DP-1.7: One strict priority queue traffic testDP-1.14: QoS basic testDP-1.4: QoS Interface Output Queue CountersDP-1.11: Bursty traffic test

Help


Linter proposal: disallow visibility: visible

And encourage to use visibility: inherit instead, because using visibility: visible may unintentionally override an inherited visibility: hidden. And in the rare cases where it is actually intentional, I think it's good have an explicit comment that disables this rule.

I like this. I think it could be a generic DisallowedValues linter or something:
DisallowedValues:
    enabled: true
    blacklist:
      - property: visibility
        value: visible
        reason: Use "visibility: inherit" instead, to avoid accidentally overriding "visibility: hidden."
      - property: font-family
        value: serif
        reason: We don't use serif.

The YAML is getting a little deep... but I think that list-of-dictionaries syntax works...

Ah yes, that sounds like a sensible abstraction!

What do you think about calling it disallowed_value: serif instead of value: serif? I don't have strong feelings about it, but I think that disallowed_value might be a little clearer.
Alternatively, what about combining property and value like:
DisallowedValues:
    enabled: true
    blacklist:
      - style: visibility: visible
        reason: Use "visibility: inherit" instead, to avoid accidentally overriding "visibility: hidden."


Frontend Project "responsive navbar" Hamburger Visibility Correction

Title and Issue number
Frontend Project "responsive navbar" Hamburger Visibility Correction
Close #3627
Output
Before

After

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md

@MohitGupta121 Kindly review this pull request.

Hi @MohitGupta121
Kindly review this pull request so that I can work on other issues.


[Release] Bumped snowflake version to 4.4.4

What does this PR do?
[Release] Bumped snowflake version to 4.4.4
Motivation
The changelog/Fixed label was missing in this PR https://github.com/DataDog/integrations-core/pull/12896 so this integration was not released. I will include it in RC2
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Unfrozen

I have to release two other integrations, opening another PR with all of them. Sorry @maycmlee


Validation for Task Message Volunteers (#1411)

I noticed some very weird behavior when returning the original BadRequest(ModelState) to an AJAX for submission. Sometimes it would return 1 of the validation errors, but most times it only returns "Bad Request" as the responseTest. The Modelstate errors do not appear to be in any part of the response object the AJAX error callback receives.  This was causing JSON parsing issues. I also noticed that this problem exists anywhere we have
 return BadRequest(ModelState);
which occurs in the EventAdminController when sending a message to all the volunteers within an event, and in the IntineraryController, when creating a new Itinerary. All three areas have this validation bug, but I have only fixed this one because I am unsure if we want to proceed with this solution.
I resolved this by returning a JsonResult with a success flag and the model state errors. In the AJAX success method, I am either returning a success message if the flag is true, or iterating through the errors and displaying them within the validation message box if false. If the error event is hit within the AJAX, it returns a generic error message, as this means it was something server related and not a validation error. With this solution there is no JSON parsing to worry about.

This fix obviously breaks the unit test which confirms a badrequest is returned if a modelstate error exists.

So should we remove the unit test then? Cc @mgmccarthy

@tonysurma @mgmccarthy  I could also modify the unit test to check the JSON response to make sure the success flag is set to false if an error exists in the modelstate

@tonysurma cc @adam3039, anything "javascript" is a bit outside my wheelhouse. I can take a peek at the code, but I'm not too sure if I should be the one making decisions on it or reviewing it.

@dpaquette or @canadianjames, thoughts?

@adam3039, @tonysurma - I realize you didn't ask me to weigh in, but I figured I'd share my thoughts anyway if that's okay.
A couple opinions:

I am not a huge fan of returning automated errors from code behind. The errors that a user sees should be a view specific concern for usability, ease of localization in the future (may not be an issue for this project), etc. Therefore, I do not like pushing the model state's validation errors directly out to the user...they are a bit too "programmer-y" in my opinion.
It is a bit alarming that the modelstate data isn't being populated when it shows up in the browser. I wonder if this is a bug with ASP.Net 5, if Microsoft decided to break with how the previous versions of ASP.Net Web API worked (intended and different than the old behavior), or something else is going odd in the allReady solution to override/break the default behavior.

As far as an overall solution, I think your solution style is okay if we feel that these are "application level" errors and not "HTTP level" errors. Personally, I like trying to leverage HTTP as much as possible and BadRequest feels okay because the request was bad...it didn't contain the appropriate inputs and therefore the request is a bad one.
This makes me think that we should actually do client side validation before the ajax call. We would still need to update the code to handle BadRequest and Unauthorized responses. However, this isn't likely going to be sufficient in all cases because we would likely duplicate a lot of logic on the client side that the server is trying to do automatically through attributes on the models.
However we decide to solve this particular issue (and the other places you found in the code), we should definitely update the unit tests to behave however we want these to.

Thanks for weighing in @tonylambert . I entirely agree that I think it may be a priority to investigate BadRequest(ModelState) further, as I do think it is the cleanest solution (at least for server side validation). I do think something is happening within the solution that is overriding/breaking the default behavior, as you said.
I provided this as a solution because I've seen model validation handled within the success callback of an AJAX response before, while the error callback is reserved for more server-centric errors.
I agree that the cleanest solution is likely investigating what is causing the BadRequest(ModelState) to just return a "Bad Request" string, as well as providing client side validation for the required fields. Since the ViewModel already has the necessary validation attributes, I believe it would just be a matter of adding unobstrusive validation to the project, but someone could certainly correct me on this.

@adam3039 - I haven't tried this, but maybe creating a brand new toy ASP.Net API project and see if you can get
return BadRequest(ModelState)
to return the way we expect. It at least tells us if the framework has changed (or has a bug which is probably unlikely) or if we have broken something.

I think that  return BadRequest(ModelState) would be the preferred approach. It looks like others have had problems with this and I'm not sure what the resolution was. I did not have time to read through the entire issue.
https://github.com/aspnet/Mvc/issues/4607

@tonylambert  The return Badrequest(ModelState);  is working fine, this is not a bug in ASP.NET.
The problem is in the web.config because the web server is cutting out the response body and replacing it with the text "Bad Response", because of the existingResponse="Replace" setting:
https://github.com/HTBox/allReady/blob/master/AllReadyApp/Web-App/AllReady/web.config#L7-L10:
    <httpErrors errorMode="Custom" existingResponse="Replace">
      <remove statusCode="404" />
      <error statusCode="404" prefixLanguageFilePath="" path="/Error/Error404" responseMode="Redirect" />
    </httpErrors>

So I think the solution should be that we change this setting to existingresponse=PassThrough this would preserve the properly serialized ModelState in the response.

@adam3039, @nemesv - That sounds like it would solve the problem, but is that opening up any information disclosure issues that we would want to avoid? I honestly don't know enough about other scenarios that could provide other details. If there are unhandled exceptions, then those would come back as 500 errors. It would seem that this wouldn't be a problem, but I haven't put a lot of thought into it.

@adam3039 based on the comments here from @dpaquette and others is there anything more you need?  Thanks again


cannot find type definition: multipart.FileHeader

Describe the bug
When I include the *multipart.FileHeader typed field in the custom struct and annotate the swag as the following screenshots, swag init will return the error msg
To Reproduce
Steps to reproduce the behavior:

run go get  github.com/swaggo/swag/cmd/swag@80b6894b047bd06e970efa3e6dee1c3818811f4d in order to support the object for formdata  ref: #300
define custom struct as below screenshot
define the swag annotations as below screenshot
run swag init
saw the error

Expected behavior
swag init should executed successfully
Screenshots

Your swag version
v1.6.8-0.20200921161410-33e4ac3219fa

Your go version
1.15.2
Desktop (please complete the following information):

OS: WIN 10

Although it may be a bit late, but I will share my workaround(may not the best practice)

add swaggerignore tag for *multipart.FileHeader
add swag comment to request struct and *multipart.FileHeader  separately

This is work for me  (swag v1.8.1)
swag init --parseDependency --parseInternal --parseDepth 1

https://github.com/swaggo/swag/issues/817

thx,is't worked


[lc_ctrl] Remove RD access to isolated partition in DEV

This addresses a security concern in #7197.
Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

We can also remove the write access, but I don't think that is needed.

Sure - just thought I'd put the change already out such that we can get it reviewed.


Timestamps

In one of the last commits there's a problem.
https://github.com/mybb/mybb2/commit/a33e0fbc2c002dc7069c978e6fd049ab4b7dd68d?diff=unified#diff-e6a42cbe15e7b8610cb2e34cf5f38577
$timestamps should be public or we get this error:
Access level to MyBB\Core\Database\Models\User::$timestamps must be public (as in class Illuminate\Foundation\Auth\User)

Yep, @JoshHarmon can you revert that change or shall I create a patch?

Yeah... The code sniffer led me astray there. I'll patch it up.

Fixed in #226


Self service ui

create dashboard-header.js, refactor file structure of views, form clear function, make exploreDimension and filter optional on the submit, test refactored error msg and hideSuccessError functionality, adding metric_function to anomaly-function/create params, modal for anomaly-function/delete

LGTM


mixin support like dart language

Hi , is it possible to support mixing with fields support, It will help us to implement behaviors (features) in separate clean mixin
then we compose our class using those mixin, fields are important to implement behaviors,
Just imagine this example , if I want to make game player class that can play sound , produce light, and fall by physics
it is very clean to make these features as seperate mixin : Sound, Light, Rigidbody
then I can compose them like  class  MyPlayer : with Sound, Light, Rigidbody
basically  it will copy mixin code into MyPlayer
It will be awesome also if mixin will have constuctor and destructor called when MyPlayer class created or destroyed.
of course also must be able to cast MyPlayer to any mixin, for example I want to Add MyPlayer to Physics System, I must cast to Rigidbody.
last thing mixin can use and force MyPlayer to have specific feilds or functions. ( for example all mixins code require MyPlayer position).
Regards.
[Enter feedback here]

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

ID: 83c8d9be-958f-d92a-77f5-c105fa307c93
Version Independent ID: 0974453c-bf3d-37ed-a965-c4178f3be945
Content: Create mixin types using default interface methods
Content Source: docs/csharp/whats-new/tutorials/mixins-with-default-interface-methods.md
Product: dotnet-csharp
Technology: csharp-advanced-concepts
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Hi @aliessmael
I'm going to close this because it's not a docs issue, but a product request. You can suggest news features in the dotnet/csharplang repository.
The LDM (Language design meeting) team discussed possible designs to enable this feature. After deliberating, the decision was that the likelihood of introducing the "diamond inheritance problem" was too great. That's a reason for the restriction that default interface members can't include instance fields.
This is still an attractive feature, but it would require a better solution before it can be added.


Command $ pip install pyscf[all] will downgrade pyscf

Hi,
I just found an issue here, after installing pyscf 2.0 using command:
> $ pip install pyscf

then use the following command to install all extension modules:
> $ pip install pyscf[all]

the command above will downgrade pyscf from 2.0 to 1.7.6 which can be seen as follows:

Requirement already satisfied: pyscf[all] in ./.conda/envs/PYSCF/lib/python3.8/site-packages (2.0.1)
Requirement already satisfied: numpy!=1.16,!=1.17,>=1.13 in ./.conda/envs/PYSCF/lib/python3.8/site-packages (from pyscf[all]) (1.22.3)
Requirement already satisfied: scipy!=1.5.0,!=1.5.1 in ./.conda/envs/PYSCF/lib/python3.8/site-packages (from pyscf[all]) (1.6.2)
Requirement already satisfied: h5py>=2.7 in ./.conda/envs/PYSCF/lib/python3.8/site-packages (from pyscf[all]) (3.6.0)
Collecting pyberny>=0.6.2
Downloading pyberny-0.6.3-py3-none-any.whl (27 kB)
Collecting pyscf-doci
Downloading pyscf-doci-0.1.0.tar.gz (9.0 kB)
Preparing metadata (setup.py) ... done
Collecting pyscf[all]
Downloading pyscf-2.0.0-cp38-cp38-manylinux1_x86_64.whl (40.9 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 40.9/40.9 MB 6.9 MB/s eta 0:00:00
Downloading pyscf-1.7.6.post1-cp38-cp38-manylinux1_x86_64.whl (29.7 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 29.7/29.7 MB 7.2 MB/s eta 0:00:00
WARNING: pyscf 1.7.6.post1 does not provide the extra 'all'
Installing collected packages: pyscf
Attempting uninstall: pyscf
Found existing installation: pyscf 2.0.1
Uninstalling pyscf-2.0.1:
Successfully uninstalled pyscf-2.0.1
Successfully installed pyscf-1.7.6.post1

This has been mentioned in #1243 . Hope this can be fixed soon.


Field level descriptions

Figure out how to get the descriptions added to the field level info? I think it'll be a matter of doing YAML at the end of the docstring, but if there's a better way, then that would be great. As a proof of concept, see if there's a way to add a description to the User's family_name: "Family name of the user. For bibliographic citations."

Saman says to 'add to to the "help_text" parameter when declaring the field in the serializer model'

Here's an example, if that wasn't clear:
class UserSerializer(JSONAPISerializer):
        family_name = ser.CharField(help_text="Family name of the user. For bibliographic citations")


modify rsync command slightly

https://stackoverflow.com/a/35452860
remove the * at the end of the source

done


Wuffs style notes

Just a few drive-by comments on Wuffs style, in no particular order:

wuffmain.c looks like it's based from example/gifplayer/gifplayer.c in the Wuffs repo. That example first reads all of stdin into memory, since playing an animated GIF requires re-winding the input back to the start. For a zstd decoder, you might want to rebase off of example/zcat/zcat.c instead. That latter example is very recent. You might not have seen it when you first looked.

Speaking of wuffmain.c, it should probably be wuffsmain.c.

Wuffs names are snake_case, not camelCase. Yeah, Wuffs differs from Go here.

BTW, thanks for trying Wuffs!
Be warned, though, that the language is very unstable, and I'll undoubtedly be making breaking changes for the forseeable future. Also, I don't know what your timeline is, and having Wuffs generate Go code is certainly a goal of mine, but it's not a short term goal of mine. As I said, the Wuffs language is unstable, and it'd be harder to change the Wuffs language the more target languages we're code-generating for.
Having said all that, I'll repeat that it's great that you're trying Wuffs. I just wanted to make sure you knew what you're building on.

That latter example is very recent. You might not have seen it when you first looked.

Yes, I knew that my existing main file wasn't ideal - just wanted something that would work ok enough with the simple test cases that I had so far. I imagined I'd have more issues with the Wuffs language and tools before I'd have issues with fixed length buffers :) Thanks for the pointer though, will definitely replace it.

it should probably be wuffsmain.c

Can't remember why I named it that, probably just a typo. Thanks.

Wuffs names are snake_case, not camelCase. Yeah, Wuffs differs from Go here.

Ah - I still prefer camel case, but I'll accept that consistency is preferrable :)

I just wanted to make sure you knew what you're building on.

Yes, of course. Note that there is already a zstd package that wraps the original software with cgo, and Klaus is working on a pure Go implementation that will be ready as a decoder much, much earlier than mine. So I'm not concerned with stability or how fast I get to 1.0, at least not for now. I treat this as a fun experiment above all.
That answers your concerns about Wuffs the language and tools being unstable, and Go not coming soon - it's fine if neither is in the roadmap for the next year. I just hope it's in the roadmap at some point :) However, I'll do my best to report issues and make suggestions where I see fit. And, if you'd like me to help coding any part of it (or even just reviewing), please do let me know.
Unless you say there are parts that you'd like help with, I'll stay away from contributions, unless there are simple fixes that I come up with. You seem to have a vision for the project, and I don't understand quite a lot of the code, so me trying to advance it by throwing code at you is likely not going to be very useful.


Make get_data / get_rva_from_offset public

I want to access File.data but it's private

Yes, I will make them public, they should be. I will make a PR tonight.

Thank you LordNoteworthy :)

v1.1.1 should have this fixed, you can upgrade the pkg and check. Thanks :+1:


Cacti changes

Coming along!  Things to attend to:
*  Integrate documentation with API reference
* Write a tutorial
* In code:
*
* Split methods so that there are blah and blah_ versions
* Split build_cacti into with_forced_ctls and not
* Try to move to just one Fibheap (or justify why we need two)
* Move max matching algs together


Shell Navigation with custom routing does not work

I'm trying to get navigation to work using Shell and when I navigate using Shell.GoToAsync(string) it does nothing...how do I report this issue or get help with this?

You can click the Feedback > This product button at the bottom of the Shell doc or go directly to the Xamarin.Forms open source repo to raise an issue. Note that Shell is still in preview, so it may be a bug or known issue.


Remove "next rates" APIs

In https://github.com/penumbra-zone/penumbra/issues/2630 we added and began using the current epoch's staking rates in the node and client, however the APIs for fetching the next epoch rates remained in place. This is an issue because they can no longer be predicted accurately; the API should be removed entirely.

WIP exists in #2909. We're deprioritizing from Testnet 62, but we'll need this work to be rebased and then land for distributions work.


OSM with HTTPS Ingress and mtls between services

Fixed with commit https://github.com/briandenicola/kubernetes-cluster-setup/commit/efc5987178e313d4ebd273767aa81073830710bb


Allow user to change the activity_type on Updating the Activity

We need to allow users to choose the actitivty on the Creation and Update forms.
The create actitivty form:

The update actitivty form:

@luanfonceca i'll take this one.

@luanfonceca where can i add the activity? is it in the user side or admin side?

Hi @ryanermita, we dont use the Admin. Follow this workflow:

Create an Event
Click on Create Schedule button
Click on Add Activity button

thanks @luanfonceca , im looking into it.


[Event Modify] codeunit 22 "Item Jnl.-Post Line" - OnBeforeCheckItemTracking

In codeunit 22 "Item Jnl.-Post Line" please change event signature from
    [IntegrationEvent(false, false)]
    local procedure OnBeforeCheckItemTracking(ItemJournalLine: Record "Item Journal Line"; ItemTrackingSetup: Record "Item Tracking Setup"; var IsHandled: Boolean; var TempTrackingSpecification: Record "Tracking Specification" temporary)
    begin
    end;

to
    [IntegrationEvent(false, false)]
    local procedure OnBeforeCheckItemTracking(var ItemJournalLine: Record "Item Journal Line"; ItemTrackingSetup: Record "Item Tracking Setup"; var IsHandled: Boolean; var TempTrackingSpecification: Record "Tracking Specification" temporary)
    begin
    end;

Thank you

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Fixed Debian Interface Selection

remove : which makes responder fail to assign int

Example of failed chuckle.log:
[!] Error: eth1:: Interface not found
Breakdown:
responder -I $(netstat -ie | grep -B1 $<IP_ADDRESS>  | head -n1 | awk '{print $1}') -wrfF
__
.----.-----.-----.-----.-----.-----.--|  |.-----.----.
|   _|  -| --|  _  |  _  |     |  _  ||  -|   _|
|| |||   ||||||||
|_|
       NBT-NS, LLMNR & MDNS Responder 2.2

Original work by Laurent Gaffie<EMAIL_ADDRESS>To kill this script hit CRTL-C
[!] Error: eth0:: Interface not found
responder -I $(netstat -ie | grep -B1 $<IP_ADDRESS>  | head -n1 | awk '{print $1}' | sed 's/://') -wrfF
__
.----.-----.-----.-----.-----.-----.--|  |.-----.----.
|   _|  -| --|  _  |  _  |     |  _  ||  -|   _|
|| |||   ||||||||
|_|
       NBT-NS, LLMNR & MDNS Responder 2.2

Original work by Laurent Gaffie<EMAIL_ADDRESS>To kill this script hit CRTL-C
[+] Poisoners:
LLMNR                      [ON]
NBT-NS                     [ON]
DNS/MDNS                   [ON]
[+] Servers:
HTTP server                [ON]
HTTPS server               [ON]
WPAD proxy                 [ON]
SMB server                 [ON]
Kerberos server            [ON]
SQL server                 [ON]
FTP server                 [ON]
IMAP server                [ON]
POP3 server                [ON]
SMTP server                [ON]
DNS server                 [ON]
LDAP server                [ON]
[+] HTTP Options:
Always serving EXE         [OFF]
Serving EXE                [ON]
Serving HTML               [OFF]
Upstream Proxy             [OFF]
[+] Poisoning Options:
Analyze Mode               [OFF]
Force WPAD auth            [ON]
Force Basic Auth           [OFF]
Force LM downgrade         [OFF]
Fingerprint hosts          [ON]
[+] Generic Options:
Responder NIC              [eth0]
Responder IP               [<IP_ADDRESS>]
Challenge set              [1122334455667788]
[+] Listening for events...


Would like to be able to use Duo passcodes

Currently my "default" Duo auth mechanism is Push to my phone.
But sometimes I want to use a Duo passcode (e.g. when I have Yubikey available).
I'd like a --passcode flag to be able to pass a passcode to token.

Please assign this to me and I'll contribute the fix.

Close this issue since kubetoken is no longer maintained.


yaml to json preview using js-yaml

yaml to json preview using js-yaml

Thank you for contributing!

Published to v0.16.5


Dataset

Where can i get the data?

我下载了IJCAI2019_data的那个数据集。但是运行结果和论文中的结果差很多。最后得到的只有：
AVERAGE ACC = 0.6889789303079417
AVERAGE MAC-F1= 0.6618514109412116
应该怎么复现论文中提到的：ACC  73.87  MAC 73.03的结果？

I think you need to change the code in FITE.py: PRE_TRAINED_MODEL_NAME = "bert-base-uncased" to PRE_TRAINED_MODEL_NAME = "vinai/bertweet-large" , and adjust the learning rate.

Where can I get the dataset? There is no instruction on how to obtain the dataset.

You can download the twitter-2017 dataset here:https://github.com/jefferyYu/TomBERT/tree/master/absa_data/twitter,
twitter-2015 dataset here:https://github.com/jefferyYu/TomBERT/tree/master/absa_data/twitter2015, and you can find the images in the TomBERT repo: https://github.com/jefferyYu/TomBERT#download-tweet-images-and-set-up-image-path.


test: Cypress | SetWidget property validations + CI Stabilize

Description

This PR includes Set widget property Scenarios script
entityExplorer.RenameEntityFromExplorer() improved
jsEditor.CreateJSObject() improved

Flaky fixes below spces:

ClientSide/JSObject/JSObjectMutation_spec.ts
Widgets/Form/FormWidget_Select_TreeSelect_spec.js
ClientSide/BugTests/Bug27817_Spec.ts
ServerSide/JsFunctionExecution/JSFunctionExecution_spec.ts
ClientSide/SettingsPane/EmbedSettings_spec.ts
/Widgets/Sliders/CategorySlider_spec.ts
Widgets/Select/RTL_support.ts
Widgets/TableV2/Edge_case_spec.js
Git/GitSync/SwitchBranches_spec.js
Widgets/Modal/Modal_spec.ts
MySQL_Datatypes/Basic_Spec.ts
Binding/TableTextPagination_spec.js
/GitSync/DeleteBranch_spec.js

Type of change

Script fix (non-breaking change which fixes an issue)

Testing
How Has This Been Tested?

[X] Cypress CI runs

Checklist:
QA activity:

[X] Added Test Plan Approved label after Cypress tests were reviewed

/ci-test-limit runId=6748716787

/ci-test-limit runId=6748716787

/ci-test-limit runId=6752320963

/ci-test-limit runId=6752320963

/ci-test-limit runId=6752320963

/ci-test-limit runId=6767278745


Delete old notebooks

PR Overview
Remove defunct notebooks that we do not intend to maintain. Future example-seekers should go to catalyst-cooperative/pudl-examples.
PR Checklist

[x] Merge the most recent version of the branch you are merging into (probably dev).
[ ] All CI checks are passing. Run tests locally to debug failures
[ ] Make sure you've included good docstrings.
[ ] For major data coverage & analysis changes, run data validation tests
[ ] Include unit tests for new functions and classes.
[ ] Defensive data quality/sanity checks in analyses & data processing functions.
[ ] Update the release notes and reference reference the PR and related issues. @zaneselvans do I need to do this?
[ ] Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.

Did you check whether there was any documentation or code referring to these notebooks? Though I suspect that there wasn't since none of them could be getting deployed (they weren't included in the package_data that's included with the Python package)

@jdangerx I think these have been deprecated for a long time and we haven't had any public reference to them for ages, in which case release notes aren't necessary.

@zaneselvans none of these notebooks appear to be referred to, except for in this old closed ticket about modernizing them.


[IOTDB-2196] Support double star ** in group by level

Only support this before:

Implement this now:

LGTM


[BUG] F# Option and ValueOption types are treated as complex types

Describe the bug
FieldBuilder treats F# Option and ValueOption types as complex types
Expected behavior
FieldBuilder gets underlying generic type
Actual behavior (include Exception or Stack Trace)
FieldBuilder gets Option or ValueOption type
To Reproduce

Create model with F# Option and ValueOption fields
Add FSharp.Text.Json to serializer settings
Use FieldBuilder on the model

Environment:

<PackageReference Include="Azure.Search.Documents" Version="11.1.1" />

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

This is interesting to consider alongside changes to support Microsoft.Spatial.

Adding @brjohnstmsft. Did this occur in Microsoft.Azure.Search 10.0 as well, or is this a change in behavior from the older package?

I have never used version 10.
But it is used in https://github.com/ssiltanen/Fasaani
@ssiltanen could you join the discussion?

For now, my workaround is:
let private optonTypeFields = Set.ofSeq <| seq {
    "tag"
    "isValueNone"
    "isValueSome"
    "item"
    "value"
    "isNone"
    "isSome"
}

let rec replaceOption (fields : IList<SearchField>) =
    let unwrapOption (field : SearchField) =
        let fields = field.Fields |> Seq.map (fun f -> f.Name) |> Set.ofSeq
        if (Set.intersect optonTypeFields fields).Count = optonTypeFields.Count
        then
            let wrappedField = field.Fields |> Seq.find (fun f -> f.Name = "value")
            let field' =
                SearchField
                    (field.Name, wrappedField.Type,
                     AnalyzerName = field.AnalyzerName,
                     IndexAnalyzerName = field.IndexAnalyzerName,
                     SearchAnalyzerName = field.SearchAnalyzerName,
                     IsFacetable = field.IsFacetable,
                     IsFilterable = field.IsFilterable,
                     IsSearchable = field.IsSearchable,
                     IsSortable = field.IsSortable,
                     IsHidden = field.IsHidden,
                     IsKey = field.IsKey)
            wrappedField.Fields |> Seq.iter field'.Fields.Add
            wrappedField.SynonymMapNames |> Seq.iter field'.SynonymMapNames.Add
            Some field'
        else
            None

    fields
    |> Seq.choose (fun f -> f |> unwrapOption |> Option.map (fun f' -> f, f'))
    |> Seq.toList
    |> Seq.iter (fun (f, f') ->
                    fields.Remove f |> ignore
                    fields.Add f')
    fields
    |> Seq.iter (fun f -> replaceOption f.Fields)

Which is pretty verbose as I have no clue of which type the field was created.
So that it would be extremely helpful to have this extra property in SearchField class.

The current v11 implementation is mostly copied from the v10 implementation, with a few changes to accommodate design and type differences. @brjohnstmsft would this have worked as desired in v10 (since you're also an F# dev)?

Looking into this more, these are separate types and would require specific handling, but could not be a type reference (would require taking a dependency on F# binaries). This is something we can consider, and any PRs are appreciated.

Well, Newtonsoft.JSON does that without the dependency. We can try that way too

The dependency can be avoided by supporting the type via string name, yes, but that is something that would have to be implemented specifically in the FieldBuilder as well as anywhere else we deserialize. We do have a preview version of Newtonsoft.Json de/serialization support for Azure.* packages you can try here: https://www.nuget.org/packages/Microsoft.Azure.Core.NewtonsoftJson/1.0.0-preview.1

Deserialization is not a big deal. I use FSharp.Text.Json which covers F# types

@heaths We never tested this scenario with the previous library. I speculate that perhaps our F# customers at the time weren't using FieldBuilder.
It would be great to better support F# scenarios out of the box across the Azure .NET SDK. If this problem exists for Search, it likely exists for other services too. Is there an opportunity to address this more broadly (e.g. -- in the codegen for serialization/deserialization logic)?

It would help to know exactly what the expected behavior is. As they are now, to .NET these are just complex types. E.g. should we treat it as a reference- or value-based Nullable<T>? Why isn't Nullable<T> sufficient? The generated code is still based on .NET types in the BCL, e.g. Nullable<T>. While FieldBuilder could perhaps provide late-bound checks for Option or ValueOption, what does that even mean in general? I don't think we couldn't use them in generated code directly since that introduces new dependencies.
/cc @pakrym

Ideal behaviour would be (@xperiandri please correct me if I'm wrong): If you have a model type in F# with Option fields, they're treated exactly the same as nullable fields in a C# model class.
For example, this record type:
type Hotel = { HotelName : string option }

Would be treated exactly the same as this C# class:
class Hotel
{
    public string HotelName { get; set; }
}

FieldBuilder would map the type to Edm.String, and JSON serialization would serialize None to JSON null and vice-versa.
Perhaps a more interesting question is what the behaviour should be for F# fields/properties that aren't optional, since null is disallowed by default in F#. Technically all types in Azure Cognitive Search are nullable (except for collections, which can only be empty, not null).

In the past in these situations, I've simply accepted this and not used Option<'T> on any types used by e.g. Azure Search etc.. It would be nice if the SDK did support Options (as I imagine it does for Nullable<'T>), but I would ask where will it end?
In my (somewhat limited) experience, you normally go from some rich F# type to a flattened, simpler class that's compatible with the Search (or other) SDK.
The general behaviour I've seen for F# and C# class library interop is to not implicitly convert between None and null (although it would be lovely if that were the case).

@isaacabraham I don't do that. I use F# domain model types as is.
Adding FSharp.Text.Json and Dahomey.Json is sufficient to handle major cases to put something like this straight into Azure Cosmos DB and get it back
[<Struct>]
type DomainID<'t> = private DomainID of Guid

[<Struct>]
type ValidString<'t> = private ValidString of string

/// User
and Uzanto =
    { [<JsonPropertyName("id")>]
      ID : UzantoID
      [<JsonPropertyName("facebookId")>]
      FacebookID : UzantoFacebookID
      PhoneHash : PhoneHash voption
      AvatarURL : UzantoImageUrl voption
      Gender : Gender voption
      Birthday : Birthday voption
      Grupoj : GrupoID HashSet
      Bibliotekoj : Biblioteko list
      [<JsonPropertyName("preferredTags")>]
      PreferredTagIDs : RegistriTagID HashSet
      [<JsonPropertyName("profiledRegistrij")>]
      ProfiledRegistriIDs: RegistriID HashSet
      CreatedAt : DateTime }
and UzantoID = DomainID<Uzanto>
and UzantoImageUrl = Url<Uzanto ImageUrl>
and FacebookID = interface end // fsharplint:disable-line InterfaceNames
//[<Struct>]
and UzantoFacebookID = ValidString<FacebookID> //private FacebookID of string

But for Azure Search because of usage of FieldBuilder which does not allow to specify destination type via attribute I had to do that workaround and also implement
        let rec applyOverrides (fields : IList<SearchField>) =
            let fieldsMap = fields.ToImmutableDictionary (fun f -> f.Name)
            fieldOverrides
            |> Map.toSeq
            |> Seq.iter (fun (name, field) ->
                match fieldsMap.TryGetValue name with
                | false, _ -> ()
                | true, value -> if fields.Remove(value) then fields.Add field)
            fields
            |> Seq.iter (fun f -> applyOverrides f.Fields)

that replaces GeoJSON type with GeographyPoint
let private fieldsOverrides : Map<string, SearchField> =
    seq {
        "location", SearchField("location",
                                SearchFieldDataType.GeographyPoint,
                                IsSortable   = Nullable true,
                                IsFilterable = Nullable true)
    }
    |> Map.ofSeq

So that for me serialization is not an issue at all
let serializerOptions =
    let options = JsonSerializerOptions(PropertyNamingPolicy = JsonNamingPolicy.CamelCase)
    let converters = options.Converters
    converters.Add (JsonStringEnumConverter ())
    // HACK: Used to overriede incorrect behavior of Dahomey
    // https://github.com/dahomey-technologies/Dahomey.Json/issues/51
    converters.Add (UriConverter ())
    converters.Add (CultureInfoConverter ())
    converters.Add (RegistriCodeConverter ())
    converters.Add (MemberDataCollectionConverter ())
    converters.Add (MesagoConverter ())
    converters.Add (
        JsonFSharpConverter(
            JsonUnionEncoding.InternalTag ||| JsonUnionEncoding.NamedFields
            ||| JsonUnionEncoding.UnwrapSingleCaseUnions
            ||| JsonUnionEncoding.UnwrapRecordCases
            ||| JsonUnionEncoding.UnwrapOption, UnionTag))
    options.SetupExtensions() |> ignore // Use Dahomey.Json
    let registry = options.GetObjectMappingRegistry()
    registry.Register<RegistriTag>(
        fun objectMapping ->
            objectMapping.AutoMap() |> ignore
            let idMapping = (objectMapping.MemberMappings |> Seq.find (fun m -> m.MemberName = "id")) :?> MemberMapping<RegistriTag>
            idMapping.SetConverter(RegistriTagIDConverter()) |> ignore)
    options

I just pass SearchClientOptions with JsonSerializerOptions and it works perfect.
But the issue is the Search schema generation from a model.

@brjohnstmsft, yes. As F# avoids nulls, then FSharp.Text.Json treats null as incorrect value for the type not wrapped into Option<T> or ValueOption<T>

So if we were to use lazy binding (as a string) for Option and ValueOption types in FieldBuilder, that should be sufficient at a minimum?

No, you need to just extract an  underlying type the same as with  Nullable. Option must be transparent to FieldBuilder

Also as you can see from my example, it is common practice in F# to use single case discriminated unions like ValidString which is just a wrapper of a single value. It would be nice if FieldBuilder could unpack that as well.

I will have a look into it the next week


React.js with Nodejs - TypeError:Path must be a string. Received true

When i run the below command in nodejs, i got "TypeError:Path must be a string. Received true"
D:\projects\infiswift\infi.admin\public>babel --presets react D:\projects\infisw
ift\infi.admin\public\assets\js\hello-world.js --watch --out-dir
TypeError: Path must be a string. Received true
at assertPath (path.js:8:11)
at Object.win32.join (path.js:221:5)
at write (C:\Users\Aximsoft\AppData\Roaming\npm\node_modules\babel-cli\lib\b
abel\dir.js:17:21)
at handle (C:\Users\Aximsoft\AppData\Roaming\npm\node_modules\babel-cli\lib
babel\dir.js:65:7)
at arrayEach (C:\Users\Aximsoft\AppData\Roaming\npm\node_modules\babel-cli\n
ode_modules\lodash\index.js:1289:13)
at Function. (C:\Users\Aximsoft\AppData\Roaming\npm\node_modules
babel-cli\node_modules\lodash\index.js:3345:13)
at module.exports (C:\Users\Aximsoft\AppData\Roaming\npm\node_modules\babel-
cli\lib\babel\dir.js:69:5)
at Object. (C:\Users\Aximsoft\AppData\Roaming\npm\node_modules\ba
bel-cli\lib\babel\index.js:124:1)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10)

@ayyappan8582 I don't see TSD used? It looks like you're using Babel?

Closing as probably wrong repo.
Feel free to continue discussion if we were wrong :rose:


feat: ✨ Styles Package

Pull Request
This PR adds our new styles package as originally defined in #365. It adds the following functionality:
📖 Description
1. @synergy-design-system/styles
A new package named @synergy-design-system/styles was added. It currently holds a typography module only. Please have a look at the provided README.md to see how it is supposed to work.
2. Package Updates
Demos:

Adjusted demos so that they make use of the styles package.
Added some samples on the main page of each of them.

Wrappers:

Adjusted each README to take into account the new styles package

Components:

Adjusted each README to take into account the new styles package
Added @synergy-design-system/tokens as a peerDependency
Added ability to vendor css files, too (this means all files vendored where updated!)
Added new namespace styles/* to exports map in package.json to make sure styles can be loaded.
Added _utility.css from shoelace to vendored files (will get moved to src/styles/utility.css)
Added fouc.css that adds scoped fouc support.
Added generation of new style utilities to the build process to make creation of styles dynamic.

Storybook:

Adjusted storybook configuration that makes use of the styles package
Added README and CHANGELOG of the new styles package
Adjusted configuration to add the styles to the parsed manifest file to make sure knobs work as intended.
A new story namespace Styles was created, holding two demo stories.
Added a demo that shows usage of .syn-body helper classes.

🎫 Issues

Closes #455
Closes #436
Closes #269

👩💻 Reviewer Notes
The following changes where suggested and are not yet part of the package:

[x] Build does not run as my custom markdown is not formatted correctly for P R e T t I e R :(
[x] Allow the usage of automatic boolean attributes for classes
[x] Use BEM-Syntax for classes
[x] Currently, the Manifest does not reload when one of the files in the styles package is updated.

📑 Test Plan

Check out this branch and run pnpm i -r && pnpm build.
Play around with the new package and create a new module by following the supplied README.md
Run the build process and see if the README.md gets updated.
Launch Storybook and have a look at the new namespace Styles
Change a value in one of the style modules and reload storybook. Notice how the stories "className" property will get updated to include the new className (or have one item removed if you chose to remove one)

✅ DoD

[x] I have tested my changes manually.
[x] I have added automatic tests for my changes (unit- and visual regression tests).
[x] I have updated the project documentation to reflect my changes (e.g. CHANGELOG, Storybook, ...).
[ ] I have added documentation to the DaVinci migration guide (if need be)
[x] I have made sure to follow the projects coding and contribution guides.
[x] I have made sure that the bundle size has changed appropriately.
[x] I have validated that there are no accessibility errors.
[x] I have used design tokens instead of fix css values

I think I need a more cleaned up version of this to get a better feeling for it. 😢

Except of the two comments, it looks nice for me :)


Ignore specific properties

Is it possible to have some ignored properties when a document is saved ?
For instance lokijs doesn't save the meta and I would like to add more ignored properties.
It's more a feature request than an issue, it would allow people to extend document easier without having to decorate them with a new level of object.

Lokijs does save the meta do I can't really compare this with that.
You could apply a map function to transform any given set of results to objects which look like what you expect?

@obeliskos is right, this can be handled by my own implementation.


I would like to know how to use spark to run hive without introducing spark hive package in linkis ujes spark. Unable to instantiate sparksession with hive support because hive classes are not found

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-commons
What happened + What you expected to happen
I would like to know how to use spark to run hive without introducing spark hive package in linkis ujes spark. Unable to instantiate sparksession with hive support because hive classes are not found
Relevent platform
.
Reproduction script
.
Anything else
This question comes from the QA documentation of the Linkis community
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

A: linkis-ujes-spark-engine引入pom

org.apache.spark
spark-hive_2.11
${spark.version}

In addition:
It can also be added to linkis 0 Restart the Lib directory of linkis ujes spark enginemanager of X


feat(api): remove z safety margin from pipette movement check

Closes RESC-216
Overview
See the escalations ticket for more info.
Now that we use actual nozzle positions in movement conflict check, we shouldn't need to add such a big safety margin (10mm). We will prefer allowing the movement if it's in the realm of 'slight chance of collision'.
Review requests
Added an integration test. Feel free to throw some tests at it that check for collisions when moving to places where a pipette goes very close to a surrounding labware but falls just short of actually touching it.
Question: There is another way we can handle this and it's keeping the safety margin but making it low, like 2mm. Should we do that instead? See risk assessment for reason.
Risk assessment
Medium- low: there is a slight chance- due to equipment manufacturing tolerance that the pipette might touch/collide a deck item.

Makes sense, thanks.
I agree with removing the safety margin entirely until we can report these close shaves as nonblocking warnings.

That's a god point about warnings!


Some exceptions

I have no idea how this happend nor what it could mean, it seemingly threw these at random after having being in use for a few hours (113 cached music files) and stopped playing.
I could close it with !shutdown though after waiting for some time for if it would add more or restart itself, which didn't happen.
https://pastebin.com/0dEDHg2z
It's really a nice gadget to have around and maybe this log can give you some pointers for stability or sth in development. If not, feel free to ignore it ofc~
Whatever it will be, please keep up the good work, it's appreciated a lot :)

Same

Yeah I have gotten same error on a Linux server. What I do now is enabling a crontab that runs a script to restart the screen with contains the bot every 4 hours.

Newer versions of the bot should handle these better.


Fix bug with the DSL editor/viewer

This fixes 2 bugs:

When adding a DSL for an entity spec, The DSL editor "Done" button was not redirecting to the spec editor. This was due to the previous param object being modified later on by the ui-router. Creating a deep copy of the object avoid this
The DSL viewer was throwing an error while getting the name of the entity for DSL like $brooklyn:self() or $brooklyn:parent(). This is fixed by looking up directly for the relationships if the DSL are of that form

good fixes.  minor comment, good to merge with or without it.


Add support for custom JWS algorithms

This PR introduces a feature custom_alg to identity_jose (disabled by default) that allows it to process JWS with custom alg values.
Switching on custom_alg makes quite a few changes to JwsAlgorithm:

The type is no longer Copy
name() takes only a reference and returns a String rather than &'static str
The constant ALL is removed as it is no longer possible to enumerate all variants

Fixes issue #1406.
Type of change
Add an x to the boxes that are relevant to your changes.

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] Enhancement (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Fix

How the change has been tested
Added a new integration test to identity_jose that exercises the functionality.
Note requires CI changes to be run with cargo test --test custom_alg --features="custom_alg"
Change checklist
Add an x to the boxes that are relevant to your changes.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@itsyaasir, @eike-hass: The change using a feature flag seems to be quite reasonable. What do you think?


Add Time & Time Zone to WRF

To make it easier processing online workshops we would like to add a Timezone question to the Inquiry Form and the Request a Workshop Form.
Questions could be:
Please indicate the Time Zone your workshop will take place.
Please provide the desired start and end time of your workshop.

Do you want to extend just the forms, or do you want to save the new information inside event as well?

Do you want to extend just the forms, or do you want to save the new information inside event as well?

I would love to save the new information inside the event as well :)

I would love to save the new information inside the event as well :)

Thanks for your feedback @sheraaronhurt
@pbanaszkiewicz  Please let us know if you have any other questions about this issue.

Thanks for your feedback @sheraaronhurt
@pbanaszkiewicz  Please let us know if you have any other questions about this issue.

@maneesha @sheraaronhurt I don't have any questions, but I have one assumption you can confirm.
Assumption: Since the workshops can take more than one day, the start and end time are though of as start and end time for each day the workshop lasts.
A different approach is to understand start time on the first day of the workshop, and end time of the last day of the workshop.

@maneesha @sheraaronhurt I don't have any questions, but I have one assumption you can confirm.
Assumption: Since the workshops can take more than one day, the start and end time are though of as start and end time for each day the workshop lasts.
A different approach is to understand start time on the first day of the workshop, and end time of the last day of the workshop.

Thanks @pbanaszkiewicz ... I use it to mean the start/end time for each day the workshop lasts. Thanks for clarifying

Thanks @pbanaszkiewicz ... I use it to mean the start/end time for each day the workshop lasts. Thanks for clarifying

@sheraaronhurt  I think we should talk about this more as we consider moving online workshops from the temporary pilot phase to being official offerings.  For example, what happens when we have a workshop that lasts multiple days, and the start end/time is different each day?  We should also consider this in the context of the instructor selection project.  There, we were talking about not prioritizing time zones.  Saving this for more discussion.

I will bring this up with the Workshop Admin team at our next meeting.

connected to #2255

For online events, we do want to ask what start/end time and what time zone the event will be in.  Not necessary for inperson events.


allow hspec 2.6 to support Stackage LTS 13.1

https://www.stackage.org/lts-13.1/package/hspec-2.6.0
https://www.stackage.org/lts-13.1/package/hspec-discover-2.6.0

<= is wrong, it's always < (except in very rare cases)
just add github to skipped-tests section on Stackage. I won't make releases (neither revisions) to only bump bounds in test-suites: there's nothing "new".

Sent from my iPhone

On 2 Jan 2019, at 0.42, Ryan Mulligan<EMAIL_ADDRESS>wrote:
https://www.stackage.org/lts-13.1/package/hspec-2.6.0
https://www.stackage.org/lts-13.1/package/hspec-discover-2.6.0
You can view, comment on, or merge this pull request online at:
https://github.com/phadej/github/pull/341
Commit Summary
allow hspec 2.6 to support Stackage LTS 13.1
File Changes
M github.cabal (4)
Patch Links:
https://github.com/phadej/github/pull/341.patch
https://github.com/phadej/github/pull/341.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

can be closed


Validate the cloudflareTimeout option and add timing test

@codemanki, I'd like to begin work on this as well.


Build issue

I had the following error
Execution failed for task ':react-native-directed-scrollview:verifyReleaseResources'.
> java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
  Output:  /Users/obsidianart/HDD/GIT/imagzle/node_modules/react-native-directed-scrollview/android/build/intermediates/res/merged/release/values-v28/values-v28.xml:7: error: resource android:attr/dialogCornerRadius not found.
  /Users/obsidianart/HDD/GIT/imagzle/node_modules/react-native-directed-scrollview/android/build/intermediates/res/merged/release/values-v28/values-v28.xml:11: error: resource android:attr/dialogCornerRadius not found.
  /Users/obsidianart/HDD/GIT/imagzle/node_modules/react-native-directed-scrollview/android/build/intermediates/res/merged/release/values/values.xml:957: error: resource android:attr/fontVariationSettings not found.
  /Users/obsidianart/HDD/GIT/imagzle/node_modules/react-native-directed-scrollview/android/build/intermediates/res/merged/release/values/values.xml:958: error: resource android:attr/ttcIndex not found.
  error: failed linking references.

  Command: /Users/obsidianart/.gradle/caches/transforms-1/files-1.1/aapt2-3.2.1-4818971-osx.jar/24fc49a54beeb394af9f7efc15d0a12c/aapt2-3.2.1-4818971-osx/aapt2 link -I\
          /Users/obsidianart/Library/Android/sdk/platforms/android-26/android.jar\
          --manifest\
          /Users/obsidianart/HDD/GIT/imagzle/node_modules/react-native-directed-scrollview/android/build/intermediates/aapt_friendly_merged_manifests/release/processReleaseManifest/aapt/AndroidManifest.xml\
          -o\
          /var/folders/zv/9q28yy151370p5m_h1nmzx5r0000gn/T/aapt-2196059786566862826-out\

and I was using build 27.0.3 (now I'm on 28).
I don't know what causes the error but I'm writing what fixed it for the next person:

open build.gradle inside the node_modules folder in this package
replace with the following at the top

android {
    compileSdkVersion 28
    buildToolsVersion "28.0.3"

Since currently I'm not in a CI with this project I can change directly the package but if someone with more knowledge than me can explain how else it can be fixed I would really appreciate

debug build success but
fail in release
"react": "16.8.3",
"react-native": "0.59.9",
"react-native-directed-scrollview": "git+https://github.com/chrisfisher/react-native-directed-scrollview.git"


nrf52_nffs_example

…com>
new file:   samples/subsys/fs/nffs/CMakeLists.txt
new file:   samples/subsys/fs/nffs/README.rst
new file:   samples/subsys/fs/nffs/prj.conf
new file:   samples/subsys/fs/nffs/sample.yaml
new file:   samples/subsys/fs/nffs/src/main.c

Hi Vikrant, thanks for contributing. You need to edit your commit message so it looks like:
samples: nffs: New NFFS sample

<description>

Signed-of-by: First Last <email>

If you need help configuring git to achieve this please join #zephyrproject on IRC (freenode.net) and I'm sure we'll be able to help you.

Yes, I did it.
Hope now it will get accepted.

This is still somehow incorrect. Look at the "Commits" tab and you will see there are 2 commits, one of which has incorrect formatting. You need to use:
git rebase -i upstream/master

to merge both commits into a single one
Then you can use
git commit --amend

to modify the commit message

Codecov Report

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

@@           Coverage Diff           @@
##           master    #6154   +/-   ##
=======================================
  Coverage   52.88%   52.88%
=======================================
  Files         412      412
  Lines       40274    40274
  Branches     7801     7801
=======================================
  Hits        21297    21297
  Misses      15761    15761
  Partials     3216     3216

Continue to review full report at Codecov.

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

@vikrant8051 you don't need to close the PR, you can change your commits and then git push -f


What is the relationship between segment and timetoken？

Hi, thanks for you great work! I want to ask what is the relationship between original segment(contained in seg_prompt) and time_token_？

Is asr data used when constructing instruction data?

Hi, thanks for your interest.
The time token is used in Vid2seq, which uses relative timestampes. Specifically, it quantizes any video of duration $T_i$ into 100 equally-spaced timestamps.
In contrast, we use absolute timestamps, i.e., original segments contained in seg_prompts. The first number in seg_prompts denotes the duration (seconds) of current video. After that, each two numbers represent the start and end time of a fragment.
The training on TimeIT-104k uses asr data, while the fine-tuning or evaluation on Youcook2, Charades, and qvhighlight do not use asr data.

oh, thanks for your clear reply!


Using chip-tool to commission a device with DAC created using mfg_tool (CON-625)

Hi,
I have created a DAC and other certificates using mfg_tool. Following was the command that I used.
./mfg_tool.py -cn "My bulb" -v 0xFFF2 -p 0x8001 --pai \    -k ~/esp/esp-matter/connectedhomeip/connectedhomeip/credentials/test/attestation/Chip-Test-PAI-FFF2-8001-Key.pem \    -c ~/esp/esp-matter/connectedhomeip/connectedhomeip/credentials/test/attestation/Chip-Test-PAI-FFF2-8001-Cert.pem \    -cd ~/esp/esp-matter/connectedhomeip/connectedhomeip/credentials/test/certification-declaration/Chip-Test-CD-FFF2-8001.der
Afterwards I flashed the firmware. Then flahsed the binary image to the device using esptool.py using the correct address of the partition table.
esptool.py -p /dev/ttyUSB0 write_flash 0x10000 /home/thisal/esp/esp-matter/tools/mfg_tool/out/fff2_8001/35c350b3-febc-4dcd-9532-63746675447c/35c350b3-febc-4dcd-9532-63746675447c-partition.bin 0x17000 build/ota_data_initial.bin 0x29d000 build/storage.bin
After rebooting, the credentials were updated properly, the device was not using the Example DAC, but was responding to the custom DAC that was created.
Next, I tried to commission the device using chip-tool.
./chip-tool pairing ble-wifi <node> <wifi ssid> <password> <passphrase> <discriminator> --paa-trust-store-path ~/esp/esp-matter/connectedhomeip/connectedhomeip/credentials/test/attestation/.
However, the ship-tool fails. Here is the console on the chip-tool. The full log is attached.
...................................................................................................................
[1689258282.243186][126581:126583] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0001
[1689258282.243193][126581:126583] CHIP:CTL: Received Attestation Information from the device
[1689258282.243199][126581:126583] CHIP:CTL: Successfully finished commissioning step 'SendAttestationRequest'
[1689258282.243203][126581:126583] CHIP:CTL: AutoCommissioner setting attestationElements buffer size 278/278
[1689258282.243213][126581:126583] CHIP:CTL: Commissioning stage next step: 'SendAttestationRequest' -> 'AttestationVerification'
[1689258282.243216][126581:126583] CHIP:CTL: Performing next commissioning step 'AttestationVerification'
[1689258282.243218][126581:126583] CHIP:CTL: Verifying attestation
[1689258282.250586][126581:126583] CHIP:CTL: Failed in verifying 'Attestation Information' command received from the device: err 604. Look at AttestationVerificationResult enum to understand the errors
[1689258282.250604][126581:126583] CHIP:CTL: Error on commissioning step 'AttestationVerification': 'src/controller/CHIPDeviceController.cpp:1111: CHIP Error 0x000000AC: Internal error'
[1689258282.250606][126581:126583] CHIP:CTL: Failed to perform commissioning step 8
[1689258282.250608][126581:126583] CHIP:CTL: Going from commissioning step 'AttestationVerification' with lastErr = 'src/controller/CHIPDeviceController.cpp:1111: CHIP Error 0x000000AC: Internal error' -> 'Cleanup'
............................................................................................................................................
The error 604  is AttestationVerificationResult enum;
kCertificationDeclarationInvalidVendorId    = 604,
I was following which is similar.
https://github.com/project-chip/connectedhomeip/issues/26142
Any input regarding how to use certificates generated with mfg_tool along with chip-tool would be highly appreciated.
Thanks and regards,
Thisal
chip-tool_log.txt
device_console_log.txt

Your vendor ID is menuconfig is likely set to 0xFFF1 and you used the 0xFFF2 certificates. Change it to 0xFFF2 in menuconfig.

@jonsmirl Thank you very much.
I had to change both vendor_id and product_id to match with the arguments of the certificates. And it worked perferctly!
CONFIG_DEVICE_VENDOR_ID=0xFFF2
CONFIG_DEVICE_PRODUCT_ID=0x8001


shared-steps unable to find page instance

feature:
Feature: Upload Feature
    # @test
    Scenario:   I can try common steps
        Given   I am on the landing page ----> this is my common step used in multiple feature files

step_definitions:
import { BrowserTypes } from '../../src/browserTypes';
import * as playwright from 'playwright';

import { loadFeature, defineFeature } from 'jest-cucumber';

import { landing_page } from './shared-steps';

let browser: any;
let page: any;

const feature = loadFeature('./src/features/example.feature');

// Loop over all the supported browsers
for (const browserType of BrowserTypes) {
    defineFeature(feature, (test) => {
        beforeAll(async () => {
            browser = await playwright[browserType].launch({ headless: false }).catch((log: any) => console.log(log));
            page = await browser.newPage().catch((log: any) => console.log(log));
        });
        afterAll(() => {
            // browser.close().catch((log: any) => console.log(log))
        });
        afterEach(async () => {
            // await page.waitFor(3000)
        });
        beforeEach(async () => {
            await page.goto('xxxx.com/', {
                waitUntil: 'networkidle0',
            });
        });

        test('I can try common steps', async ({ given }) => {
            landing_page(given, page);
        });
    });
}

shared-steps.ts

export const landing_page = (given, page) => {
    given(/^I am on the landing page$/, async () => {
        console.log(await page.title());
        expect(await page.title()).toEqual('Sign In');
    });
}

Error:
TypeError: Cannot read property 'title' of undefined

      3 | export const landing_page = (given, page) => {
      4 |     given(/^I am on the landing page$/, async () => {
    > 5 |         console.log(await page.title());
        |                                ^
      6 |         expect(await page.title()).toEqual('Sign In');
      7 |     });
      8 | }

unable to call the step definition, for shared step definition from shared file

unable to identify the step_definition from shared file, calling the function in steps file

@bencompton , tried the above example, didn't work. Any update or insight on this please ?

@lakshmanp21 you should check out cucumber-jest. it's a transformer for jest that allows you to use the cucumber api with jest. Because it's using the cucumber js api, it supports declaring step definitions once and they can be used in any feature file.

@lakshmanp21 you should check out cucumber-jest. it's a transformer for jest that allows you to use the cucumber api with jest. Because it's using the cucumber js api, it supports declaring step definitions once and they can be used in any feature file.

I am using cucumber-jest as suggested, though the issue (above) exists
  "dependencies": {     "allure-jasmine": "^2.0.0-beta.8",     "allure-js-commons": "^2.0.0-beta.8",     "codeceptjs": "^2.6.10",     "jest": "^26.6.1",     "jest-cucumber": "^3.0.0",     "playwright": "1.4.0",     "ts-jest": "^26.4.3",     "typescript": "^3.9.7"   },   "devDependencies": {     "@fast-csv/parse": "^4.3.3",     "@testing-library/jasmine-dom": "^1.1.0",     "@types/faker": "^4.1.12",     "@types/jest": "^26.0.15",     "@types/node": "^14.14.6",     "csv-writer": "^1.6.0",     "faker": "^4.1.0",     "jest-allure": "^0.1.3",     "jest-allure2": "^1.2.3",     "moment": "^2.28.0"   }


configure apiserver to verify bearer token?

Next, configure apiserver to verify bearer token using this authenticator. There are two configuration options you need to set:
--authentication-token-webhook-config-file a kubeconfig file describing how to access the remote webhook service.
--authentication-token-webhook-cache-ttl how long to cache authentication decisions. Defaults to two minutes.

ok. how do I do that?
I used kubeadm to install the cluster. I copied the admin.conf to .kube/config
I have that json (not sure what I should change there).
I'm logged into the master.
Now what?

These are parameters to the API server. When installing the cluster, you have to make kubeadm to pass these params to the API server at startup.
I don't have the exact solution but these are some pointers: https://github.com/kubernetes/kubeadm/issues/132 and https://stackoverflow.com/questions/41566408/restart-kubernetes-api-server-with-different-options also the Kubernetes Slack channel's kubeadm room.

Hmm I've added the option to /etc/kubernetes/manifests/kube-apiserver.yaml
and rebooted the master node
now nothing works anymore.
I give up. Thanks anyhow.


BUG add sysroot symlinks

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin rerender

@isuruf this is ready for review!

OK. ready for another look @isuruf!

OK. Shall we merge?


Added missing handle to the s3.Stat log message output

I enabled logging to better understand the s3 interaction flow and noticed that the handle was missing in Stat().

Oh, that's a nice catch. Thanks for your contribution!


Test building via netlify (preview-build)

There appears to be something preventing the front page from updating calendar, I can't see the build logs at Netlify but here we can see the script hasn't run successfully to update the "next upcoming meeting" since before the 18th:

I am investigating. I was able to run the make preview-build locally and I see no issues. It's not helpful looking at the github actions workflow logs for the periodic netlify job, because it doesn't return any status - it's just a trigger that runs a POST and doesn't wait around for the outcome. I may already have access by association to the Netlify production account to review the logs if I can figure out how (or I may need to request access)
I'm just going to see if a preview build works when we run it this way. No reason to expect it shouldn't...

I guess the every 6 hours job does not actually advance the calendar forward, this may have been reported somewhere else
I was able to access the deploy logs, it looks like everything is working, it just doesn't see any new files after the deploy and so no update is triggered. Not sure, looking into how those changes are detected to see if we can resolve it. The other way to make sure the calendar is advanced is to keep merging pull requests. 🤞


Chao/fix partuuid

After lots of testing,the error waiting for partuuid can not be resolved
when install image to emmc may show the primary gpt table corrupt,the backup gpt table appears ok
in this situation, using sfdisk --part-uuid can not get the changed partuuid instead of get the previous original emmc
partuuid not the new one(same as boot media part-uuid)
so in the script regen-rootfs-uuid sed -i 's/'${OLD_UUID}'/'${NEW_UUID}'/i' /etc/default/u-boot-script
replacement fails
finally, it would result in waiting for partuuid.....

This doesn't address why partprobe is not resolving the race.
But I still believe we should drop this altogther an go for a proper installer image.

This doesn't address why partprobe is not resolving the race.
But I still believe we should drop this altogther an go for a proper installer image.

partprobe update the partition table but would not recovery partition table.
so if the partition table corrupt, it would  get unexpected behavior.
yes, I agree with you.  currently install-on-emmc would take long time to flash the emmc and
not easy to operate.
But I think we should provide a workaround at least for this issue before we finish the new proper installer image.

OK, but then make this here much simpler by matching and replacing any currently set PARTUUID. There is not need to pass in the old one if you make the sed pattern more flexible.

alternate similar solution has merged into the master. close it


vue-template-compiler lacks a stringify API

What problem does this feature solve?
when i use vue-template-compiler parseComponent a vue file, and use  @babel/parser @babel/traverse @babel/generator modify some code at vueTemplateComplier AST.script content
But can not find a api to auto generate file from  vueTemplateComplier AST it to origin file.
What does the proposed API look like?
const fileContent = compiler.generateComponent(, {
pad: 'space'
});
// fileContent is same as *.vue file content

As I understand it's actually a feature request instead of a question so I modified your title.

Or we may consider adding it to @vue/component-compiler-utils.

Any updates here? I also wonder wether the code for stringification exists somewhere in the Vue Universe already…


A method PrimitiveType.isSwaggerPrimitive()

A method PrimitiveType.isSwaggerPrimitive().
I am calling the new method isSwaggerPrimitive() to distinguish the fact that PrimitiveType includes OBJECT as an enum which is NOT a Swagger Primitive Data Type per the 2.0 spec.
This is a smaller footprint than https://github.com/swagger-api/swagger-core/pull/2204, which I might revisit.

I understand the change, but what is the motivation for doing so?

Similar logic is in the 3.0 support branch here:
https://github.com/swagger-api/swagger-core/tree/feature/3.0.0-rc1


Empty sf::String crash in destructor

This code crashing with SIGTRAP signal on second line:
sf::String *string = new sf::String();
delete string; <-- crash

If string not empty, destructor work correctly.
System:
Windows 8 x64
MinGW 4.8.3 x64
SFML builded from source, latest Git version of master branch.
On the Linux this trouble don't repeated.

You should try a different compiler as I can run this perfectly using TDM-GCC 5.1.0 x64.

This compiler works correctly, thank you.


Variable Comment context is not accurate

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.92.1
OS Version: Windows 11 Home Single Language (Version: 23H2, OS build: 22631.3880)

Steps to Reproduce:

In C file, declare variables one after other and add comments using '//'.
If you hover on the variables, the comment appear as contexts about the variables.
But if you hover above the subsequent variables, the comments of previous variables also appear in the context.
Does not happen if the comments are of the form '/* */'.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.92.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Updated to the latest version and the issue still exists.


Looking for  suggestions on the right database

HI,
I am using superset for the dashboard, My data resides in Mysql, There are about 15 Million records for 2 years and growing at a rate of 70,000 (approx.) records per day,  I have a 5 tabbed dashboard with 41 Charts, I have aggregated the data which I  could aggregate but for other charts, The data is in its normal form and we have to give the users the ability to change time grail. Can anyone give me suggestions on the right database to use?
The time taken to display the hourly average for a single day is fine (5-6 seconds per chart after Indexing and partitioning in Mysql) (which is the default), But the time taken  for the
"Last Week" is 52 seconds
"Last Month" is 1 minute and 14 Seconds
"Last Quater" filter is about 3 minutes and 40 seconds
Will databases like Druid work for this case or should I try to aggregate the data more.
Note:- I am not sure if this is the right place to ask this question.
Thank you.

@srinify 🙏

@abhishekkumaresan Yes switching databases should speed things up. MySQL is an excellent choice for a metadata db, but being an OLTP db it's inherently at a disadvantage to something like Druid. Druid should help speed things up. You can also find a comparison of various OLAP databases here https://en.wikipedia.org/wiki/Comparison_of_OLAP_servers

Hi Abhishek, there's a few approaches you can take.

I would read more about optimizing MySQL first. I'm definitely not the expert here, but making sure you have appropriate indexes (https://www.tutorialspoint.com/mysql/mysql-indexes.htm), shards (https://medium.com/pinterest-engineering/sharding-pinterest-how-we-scaled-our-mysql-fleet-3f341e96ca6f), and dedicated compute resources for your MySQL server is the first thing I'd try. Using EXPLAIN will help you figure out where the bottlenecks are (https://dev.mysql.com/doc/refman/5.6/en/using-explain.html). There's people running MySQL at scale with petabytes of data!

Try introducing an ETL layer so Superset is only querying intermediate data / aggregates. You can stick with MySQL and use a tool like DBT to introduce some intermediate tables (https://www.getdbt.com/).

Druid is definitely a good choice if your data has lots of aggregations and you need it to be real-time: https://netflixtechblog.com/how-netflix-uses-druid-for-real-time-insights-to-ensure-a-high-quality-experience-19e1e8568d06 If real-time isn't important, then Druid could be a little overkill (remember, each database makes their own set of tradeoffs).

@srinify @nytai @junlincc  Thank you for the suggestions,
@srinify  As you said I have done indexing and I am also experimenting partitioning, I will also look into sharding and DBT, Thank you.

The database market is so large, fast evolving and diverse. People's need are also diverse and evolving. There are much better resources out there to figure out which database engine and setup you may want/need.


Skip pip packages for now (see #100).

It's fine to skip them if there's some problem, but I thought we had agreed that we should now be able to have pyviz on pip.  I tried following the chain of issues and comments, but I can't see any fundamental remaining reason why we can't have pyviz on pip?

I don't know about fundamental, but practically speaking...
Current pyviz depends on unreleased packages not on pypi (e.g. bokeh 1.0 dev something).
Previous pyviz packages won't match the pyviz.org tutorial and will have broken pyviz --install-examples command.
(what I wrote in https://github.com/pyviz/pyviz/issues/100#issuecomment-426395781)


Add Note: Existing Private DNS Zone can not use with new PostgreSQL Flex Server

Add Note: Exiting Private DNS Zone Cannot use for the Flex Server.
Customer wanted to create Flex Server on the Exiting Private DNS Zone using Portal, but drop-down does now show  DNS Zone.
Test in the lab

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

ID: 9dfacd9d-6903-1cd0-2db7-110b70e14d3b
Version Independent ID: 4c3e1d9f-ba8e-5dfd-8dd9-f1695456775f
Content: Networking overview - Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/concepts-networking.md
Service: postgresql
Sub-service: flexible-server
GitHub Login: @niklarin
Microsoft Alias: nlarin

Hi @HitenBhavsarMSFT Thanks for reaching out, We will Investigate and update you shortly.

Hi @HitenBhavsarMSFT private DNS zone was created using preview API?

You should be able to see this as long as you're in same subscription. I would recommend opening a support ticket with Microsoft so that an engineer can look into this.

#please-close


Usage in readme not clear enough

I find the readme confusing as it doesn't give any real word example and does not explain what swagger client is.
Right now i'm not sure if swagger client is the library swagger-client?
As for var validation = swagger.validateModel("modelName", jsonObject, _allowBlankTarget_, _disallowExtraProperties_); what is swagger? is it the generated json from yaml file or the swagger client?
Also:
var validation = validator.validate(object, swaggerModel, swaggerModels, allowBlankTarget, disallowExtraProperties);
What is really swaggerModel ? is it let say the defined schema response in my generated swagger.json? is models just all components?

Swagger-Model-Validator was originally designed to work against swagger-node-express.
Ir was designed to be injected into the swagger client created by swagger-node-express so that it could get access to the swagger models it requires to validate.  If the client is not available then the second use (using the validator directly) can be tried.
The swagger model referred to in that call is the model that you are trying to validate against and the swagger models is a set of all of the models contained in the swagger definition.
If you look at the tests you should be able to see some examples of the validator used that way.

This cleared things up a bit for me thanks

I agree with @brodyd . The readme is extremely lacking. You shouldn't expect people to look at the tests to figure out how to do basic things with the library.