Markdown Tab Component

The official ReasonML docs started using Docusaurus' tabable component to make the code examples more compact:

We need an equivalent to represent the same code snippet in different languages and make them tabbable.

Thought about the design of this:
Docusaurus is using html comment strings to do the component injection. We don't need to do that, we can use MDX to do the dirty bits, leading to a much cleaner solution. This is how I'd imagine the markdown to look like:
<CodeTabs>

```re
let a = 1 + 1;
```

```js
const a = 1 + 1;
```

</CodeTabs>

Here, CodeTabs is injected as a shortcode. It's globally available to our editors.
The Tab component has the same look and feel as a normal code example box, but displays available languages in the top right corner. Clicking on a language will toggle to the appropriate content.
Implementation wise, the component would need to look at its children, checking the mdxType to be code and then reuse some of the Markdown.Code logic to build the TabComponent (also mostly copy paste of the CodeExample component).

In the Screenshot the tabs are titled "Reason" and "Output".
Where would the CodeTabs component get this information from?
How would it handle several codeblocks of the same language?

@woeps I find Output to be a very weird description... would have been much more understandable if it'd be called JS or... ML .. depending on what the output actually is!
How would it handle several codeblocks of the same language? - That would be a "real tab component" with actual tabs (maybe CodeTabs should actually be called something like CodeToggle to disambiguate), but it would be another compoent then I guess. I am mostly referring on toggling between different representations of e.g. one Reason snippet to JS or ML.

I thought this might be some preparation for larger examples, where each "tab" would represent a file/module. Now, I see this was a misconception of mine.
Then I guess the build will just fail with multiple code blocks if the same lang, which seems fine in this case.


Websocket Streaming API in antelope_memento_api

The new API will allow the user to connect to the websocket endpoint and subscribe to events for multiple blockchain accounts.
The wsebsocket service needs to listen on a separate TCP port, so a new environment option is required.  socket.io  protocol is used for communication.
The connection serves only one request at a time. A subsequent call on startStreaming will cancel the previous streaming request in this socket.
startStreaming arguments:

accounts: array of blockchain account names
start_block: optional starting block number. If omitted, the streaming starts from the current head block.
irreversible: optional boolean. If set to true, only updates from irreversible blocks are streamed.

The server sends events of the following structure:

type: string event type, valid values: fork, trace
block_num:  block number
data: transaction trace or null

If the starting block is lower than last irreversible block, the API needs to retrieve the historical data from RECEIPTS and TRANSACTIONS tables in chunks of 1000 (configurable) blocks and feed them tot he client:
select block_num, trace from TRANSACTIONS join (select distinct seq from RECEIPTS where receiver in ('atomicassets', 'eosio') and block_num >= 246026319 and block_num < 246027319) R on TRANSACTIONS.seq=R.seq order by TRANSACTIONS.seq;

Once it reaches the last irreversible block, it should switch to querying EVENT_LOG. First it determines the starting ID, using the last processed block number:
select max(id) from EVENT_LOG where block_num=246373737;

Then it starts retrieving the records from EVENT_LOG in chunks of 100 (configurable) traces:
select id, block_num, data from EVENT_LOG where id>37130 and id <= 37230;

Once it reaches the position where common dispatcher is retrieving the data, the stream switches to the common dispatcher.
The common dispatcher remembers the last processed ID and retrieves a new chunk of data every 500ms in chunks of 100 (configurable) events with the same query as above. It then analyzes every trace and determins which clients should receive it.
While walking the EVENT_LOG, the server should look at the fields and determine if the trace needs to the sent to the client, as follows

in trace object, loop through action_traces. Within each action trace:
match  receipt.receiver against the list of target accounts;

As soon as one of the matching criteria is true, abort looping through the action traces and push the trace to the client.
If there are no connected clients, the API does not need to scan the EVENT_LOG.
If a client is too slow in consuming the stream, the server should switch from head block back to scanning EVENT_LOG specifically for this client. If the scanning delays behind the last irreversible block, the server should switch to scanning RECEIPTS and TRANSACTIONS.

If the stream was requested with irreversible=true, the sever walks along RECEIPTS and TRANSACTIONS only. Before querying the traces, it needs to check if the last irreversible block has advanced:
select MAX(irreversible) from SYNC

If the value is higher than the one previously known, it fetches the traces as described above.

While walking through the irreversible history, the socket produces only trace events.
Once it crosses the Last Irreversible Block (LIR, the irreversible field in SYNC table), it starts reading events from EVENT_LOG table, and keeps sending trace events to the websocket client, checking the transaction contents and deciding if the transaction is related to the subscriber or not.
If EVENT_LOG contains a fork event, the websocket client should receive the event of type fork with the forked block number.
Once the reader reaches the head block, it should read new transactions from EVENT_LOG only once, and see which websocket clients need to receive the message: the trace events are filtered by the accounts subscription, and fork events need to be sent to all clients.


Fixes #773 Camera Scan button making it difficult to view the nutrition facts for some products

Description
The camera scan button was anchored to the pager view which was not necessary and was coming in the way. Also changed the height of the pager to be able to scroll to the bottom.
Screen-shots, if any

Superseded by #796


v-if breaks extensions

When creating and recreating medium-editor instance first time it loads extensions and runs them just fine.
Second time medium-editor is created the extension button shows up but dissapears after click.
Not sure what's the issue here. No errors in console, create and destroy events are fired properly.
I'm importing extension with
import AttachmentButton from './AttachmentButton'

and then in options:
extensions: {
'attachmentbutton' : new AttachmentButton(),
}

What am i missing?

Well not very smart but working solution is change:
this.api = new MediumEditor(this.$refs.element, this.options)
to
this.api = new MediumEditor(this.$refs.element, _.cloneDeep(this.options))

this way i get new instance every time. But i'm pretty sure it's a bad idea.

Can you create a minimal working example please? You have v-if in your headline but not in the description.
Regards

I've edited original question,
You can use:
https://github.com/yabwe/medium-editor/blob/master/src/js/extensions/anchor.js

as extension to recreate.

Please just share your repo :joy: Otherwise I won't be able to carve out the time necessary to solve this.

Closing due to inactivity


Readthedocs Installation Out of Date

The installation instructions on the readthedocs are out of date compared to the Github readme. We should probably remove the instructions from Github and only provide a single set of updated instructions on the readthedocs.

Resolved in https://github.com/kammerje/spaceKLIP/pull/211


Add ARM testing

Addresses #283. Thank you to those who worked on #319 , pulled a lot of the code to make this testing work from there.
Successful testing run: https://github.com/bmsiegel/aws-privateca-issuer/actions/runs/9651463359
Let's merge the testing, then we'll get the ARM support PR merged. Will leave some comments on #319

/approve


Fixes #31 On branch edburns-31-vmsizeselect fix #31 less faulty logic to determ…

…ine location of vmSizeSelect
modified:   arm-ttk/testcases/CreateUIDefinition/VMSizes-Must-Match-Template.test.ps1

Use
$isInSteps = $selector.JSONPath.Contains('steps[')
to determine where the vmSizeSelect is within the createUiDefinition.

looks good - waiting for test case...

@bmoore-msft When you say "waiting for test case" I hope you don't mean from me, because my PowerShell skills are not up to doing that quickly.  Please confirm who owns the task of delivering the test case.

looking for a simple way to validate the fix... files in #31 will do...


Make Configuration.TestFilter Codable

This modifies the structure of Configuration.TestFilter so that it's a pure data type and can conform to Codable.
Motivation:
For easier integration with tools we'd like to make Configuration conform to Codable, so that it only contains data specifying how tests should run and does not include non-serializable things such as closures.
Configuration's nested TestFilter type currently includes a closure for filtering tests and is therefore cannot conform to Codable in its current form. This type doesn't really need to store a closure, however; it only needs to store information about how to perform filtering (e.g. data about criteria to match against), and later that can be interpreted when applying filtering.
Modifications:

Rename Configuration.TestFilter.Kind to Configuration.TestFilter.Predicate to better describe its new purpose, and add conformance to Codable.
Make two trivial supporting, pure-data types also conform to Codable.
Move the actual filtering logic derived from the pure data predicate type above to a new Configuration.TestFilter.Operation enum. This type need not (and cannot) conform to Codable.

Result:
With this change, one significant stored property of Configuration will now be Codable, which is progress towards the overall goal.
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

Resolves rdar://126627664

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test


Update EmailEntity_CloudAppEvents.yaml

Fix User_Id column name (casing) to match configured entity mapping.
Required items, please complete
Change(s):

Updated query for: EmailEntity_CloudAppEvents.yaml

Reason for Change(s):

Adjust casing of User_Id to match configured entity mapping
Resolves ISSUE #11278

Version Updated:

Yes

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Hi @nicolonsky,
Kindly repackage this solution to accommodate this change. Refer to the following guidelines for your reference. Thanks
https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.md

Hello @nicolonsky, We have pushed the content of this PR to an existing PR for Threat Intelligence
Hence closing on this PR
#11257


Error converting Lantern.gltf to .glb

Error:
SyntaxError: Lantern.gltf: Unexpected token ] in JSON at position 4609
    at JSON.parse (<anonymous>)
    at _readFile (/usr/local/lib/node_modules/gltf-pipeline/node_modules/jsonfile/index.js:25:16)

I'm tracking down an issue unrelated issue with multiple primitives so I tried to convert the Lantern.gltf (has multiple primitives in 1 mesh) to a .glb and I got the crash above. If I manually remove the extra primitive, so that there is just one primitive per mesh, the conversion succeeds. Weird.
repro
gltf-pipeline -i  ~/repros/glTF-Sample-Models-master/2.0/Lantern/glTF/Lantern.gltf -b

re-synced the file, all good.


No docs for --artifacts-path

Type of issue
Missing information
Description
There is no information about the --artifacts-path flag
Page URL
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-build?source=recommendations
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/tools/dotnet-build.md
Document Version Independent Id
5e495ddd-140e-de5c-a793-d4a9f88be51e
Article author
@tdykstra
Metadata

ID: 910cd365-d63a-00dc-417c-db017f83bf6f
Service: dotnet-fundamentals

@timdeschryver Do you want this one?

FYI dotnet publish is affected too

@tdykstra sounds good to me.


DM-33326: Fix round-tripping of spectractor spectra

Not yet for the round-tripping question (hence it all being so broken in the first place!). I think we need a CI package for atmospec+Spectractor tbh, but I think that's out of scope for now. Maybe we can discuss on Monday.


Firefox doesn't load script in template

See http://jsbin.com/huhis/1/edit. This logs the string "loaded" to the console in Chrome, Canary, and Safari — but not Firefox. (Separate bug: This displays "loaded" twice in Safari.
Background: I came across this case in trying to use a defer attribute on a script required by a analytics beacon element that would only be instantiated once per page. I wanted:

The beacon element to load its own script (rather than requiring the outer page to load the script separately)
The analytics script to be deferred to avoid delaying rendering of the page
Some work to be done after the deferred script eventually loaded.

I couldn't work out how to sink an event handler on the script element's load event if the script tag were outside the template. I tried putting the script tag within the template, and that at least let me sink load with on-load="{{loadedHandler}}". This worked everywhere in Firefox, which I isolated to the jsbin above.

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.

Still


Support "git" as a type to gyro add -s

It's apparently allowed in the gyro.zzz file, so it should be valid from the command line as well.

added this last night


Adds skeletal mesh extractors as configurable settings

Changelog Description
Adds options in the extractor settings to turn on or off the skeletal mesh abc and fbx extractors.

Additional info
At Halon we don't typically use the Abc export for skeletal meshes and needed a way to disable to extractor. One thing to note about the ABC extractor is that either we're using it wrong or it has some issues with it.

Testing notes:

Open a rig working file
In Create add a new Unreal - Skeletal Mesh publish instance.
Make sure to add your mesh and you joints to the  geometry_SET and the joints_set
Depending on your server settings you should see the following on the publish instance.

Click publish.

You should see that it only exports what ever options you have selected.

Thank you for your contribution. Speaking of the rig workflow. there is already an existing fbx rig/animation workflow for publishing the rig to unreal. You need to put your character geometry into the skeletonMesh_SET and it would export the rig in fbx for you.
You can find this community post helpful for you: https://community.ynput.io/t/loading-looks-in-rigging-scenes/1892/11

ah perfect thanks for pointing that out. Just did a quick run through of that and it's doing the trick. I'll go ahead and close this out.


Add support for annotation stereotypes

Duplication of swagger annotations might be enormous if you use them on all REST endpoints, e.g. access token query parameter
@ApiImplicitParams(
            @ApiImplicitParam(
                    name = NAME,
                    dataType = DATA_TYPE,
                    paramType = PARAM_TYPE,
                    value = DESCRIPTION,
                    required = REQUIRED
            )
 )

but what about to create a stereotype similarly like in Java EE?
@ApiImplicitParams(
            @ApiImplicitParam(
                    name = NAME,
                    dataType = DATA_TYPE,
                    paramType = PARAM_TYPE,
                    value = DESCRIPTION,
                    required = REQUIRED
            )
 )
@Stereotype
@Target(TYPE)
@Retention(RUNTIME)
public @interface MyApiParam{
}

Usage:
@GET
@MyApiParam
Response getAll();

See: http://docs.oracle.com/javaee/7/api/javax/enterprise/inject/Stereotype.html

This would be a god-send. Our api has 11 implicit params that are on every single API call.

Not familiar with @Stereotype but how is that different than what #1867 provides?


staff payment update for trimming

Issue #: /bcgov/entity#10342
Description of changes:

update to trimming fields

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the business-filings-ui license (Apache 2.0).

Successfully published:

<EMAIL_ADDRESS>
⭐

I just updated Create UI (locally) to 2.0.3 -- works great! (I'm assuming we never accept spaces between digits, right?)

Right. phew!


CSV normalization doesn't support in-cell linebreaks

A CSV row may be split in multiple lines when quoted fields contain lines breaks. This is correctly supported by ogr2ogr (and, I assume, by Ruby's CSV module).
Handling such rows is checked by the specs ('imports records with cell line breaks') but the test is perfomed with a CSV file that doesn't require normalization, so this problem hasn't been detected so far.
CSV files are normalized when either:

The encoding is different from UTF-8, ISO-8859-1/2
The delimiter is not the comma
It contains a single column (single-column rows are omitted during normalization)

In these cases Ruby CSV normalization is performed changing the  encoding to UTF-8 and the separator to ',' (and likely slowing noticeably the process along the way).
This Ruby normalization process reads each line and parses it with CSV.parse_line, silently ignoring anything that causes errors, which causes multiline rows to be dropped (an possibly other evil things).

I've added a test in branch csv_normalization_6116 to detect this: dd1e0834

Make a PR and after a code review you will be able to merge it to master :). Good catch!

Currently normalization causes any line with invalid CSV syntax to be dropped from the result.
What should we do with them? let MalformedCSVError exceptions be handled by the calling code (`CartoDB::Importer2::Loader´) and fail the import process? drop the lines but make the user aware some data was ignored?

The existing code has this particularity:
Reverse feed characters (0x8D) are removed, but only for files in Windows-1252 encoding.
Is this some legacy hack for some very specific case? Do we need to preserve this behaviour?

@rafatower

Now the behaviour with the current PR is this regarding empty lines:

Lines without content (just a line-break) and malformed lines are ignore and omitted from the output
Whitespace-only lines are kept with null values in all fields

Should we omit blank (only whitespace) lines? and all-null rows? (the latter could contain column separators in addition to whitespace)

Both cases are "malformed lines" from the point of view of CSV's, right? I'd prefer to treat them alike.
Is it hard to change that?

Don't think so. Just drop the row if row.all?(&:nil?)
Counting malformed lines which are not "empty" may be harder (depends of whether the exception raised carries the information about the source text, which I'll check).
Anyway, we'll be releasing these features (ignore all-null rows, report ignored nonblank rows) separately.


Bitbucket Cloud Personal/Team add-on

Hello,
i tried to install the add-on on a team account but i got this error :

Maybe add Team account support or something like this ?

Hey @ridaamirini, thanks for reporting this.
I'll definitely investigate on this. I don't know the differences between those kind of accounts but this extension is pretty simple. Maybe there is some stuff with permissions that I should check.
Let you know soon.

Hi! Sorry for delay
It should be fixed in the last release


webspeechapi type isn't defined

Hey, I'm running Angular 8.
When starting the dev server with the SpeechRecognitionService, I get these errors :
ERROR in node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/adapter/adapter.d.ts(1,23): error TS2688: Cannot find type definition file for 'webspeechapi'.     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/adapter/adapter.d.ts(2,39): error TS2304: Cannot find name 'SpeechRecognitionStatic'.     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/adapter/adapter.d.ts(4,39): error TS2304: Cannot find name 'SpeechGrammarListStatic'.     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/adapter/event.d.ts(1,23): error TS2688: Cannot find type definition file for 'webspeechapi'.     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/service/rx-speech-recognition.service.d.ts(1,23): error TS2688: Cannot find type definition file for 'webspeec hapi'.     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/service/speech-recognition.common.d.ts(1,23): error TS2688: Cannot find type definition file for 'webspeechapi '.     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/service/speech-recognition.service.d.ts(1,23): error TS2688: Cannot find type definition file for 'webspeechap i'.     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/service/speech-recognition.token.d.ts(1,23): error TS2688: Cannot find type definition file for 'webspeechapi' .     node_modules/@kamiazya/ngx-speech-recognition/lib/speech-recognition/speech-recognition.config.d.ts(1,23): error TS2688: Cannot find type definition file for 'webspeechapi'.

This library can only support Angular 7 and below.
Try it with Angular 7 as your project.
Thanks.

NOTE
There is work that supports Angular 8, but the release date is undecided.
https://github.com/kamiazya/ngx-speech-recognition/pull/334
If you can help, Pull Request is welcome.
Thanks.


Update howto-vm-sign-in-azure-ad-windows.md

It seems to me that the Windows Hello for Business key trust model is currently available for RDP and satisfies the MFA requirement.

@junhasems : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MicrosoftGuyJFlo, Can you review the proposed changes?  Possibly simplify the wording?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.
#label:"aq-pr-triaged"


Backward compatibility issue

We had developed our application using siemens/ix-angular: 1.6.3 but after updating it to the latest version(2.0.4) some features of the old version are not working and existing component's UI is also distorted like Navigation, Workflow etc.

Our Current Situation:
We recently updated our application from Siemens/ix-angular version 1.6.3 to their latest version 2.0.4.
Issues After Releasing the Latest Version:
Certain features that were functional in the previous version are not working as expected in version 2.0.4.
The UI of existing components, particularly navigation and workflow elements, appears distorted and dysfunctional after the update.
Suggestion Needed:
We require guidance or suggestions from Siemens/ix-angular on resolving these issues caused by the update to version 2.0.4.
Confirmation for Future Stability:
We seek assurance from Siemens/ix-angular that future updates will not lead to similar issues impacting the functionality and user interface of our application.
Reconsidering the Use of iX:
Due to these blockers and the impact on our application's functionality and UI, we may need to reconsider our continued use of Siemens/ix-angular.

Any update on this?

@jaya-prakashsharma can you please provide a list of features that are not working for you and that are NOT addressed in the migration guide already? Thank you


feat(swc/plugin_runner): free allocated memory when errors

Description:
This is small bikeshedding for the host side runner. There are multiple paths can short-curcuit if error occurs, and by having simple Drop host try to free memory as much as it can. A struct was introduced to keep reference to allocated ptr to track.
Related issue (if exists):

https://github.com/swc-project/swc/issues/3167

cargo-crev installation fails: https://github.com/RustCrypto/utils/issues/714


Considerations for Keeping Your Code Closed Source

You should consider not releasing your code as open source if your business model relies on maintaining a competitive edge and generating revenue from software sales. Following OpenAI's example, keeping your code closed source allows you to control distribution and directly monetize your innovations. It also protects your intellectual property and ensures that you can provide high-quality support and services to your customers, which often serves as an additional revenue stream. This decision is not solely about security and ethics; it's also about establishing a strong financial foundation for sustainable growth.

@putuoka 🤫
Releasing code as open source can be hugely beneficial to humanity.
It encourages global collaboration, accelerates innovation, and allows for diverse and inclusive solutions.
Open source projects can educate and inspire new developers, fostering a community that can lead to unforeseen opportunities and advancements.
While it might not directly generate revenue like closed source, its impact on technological progress and community building is invaluable.
LET'S OPEN THE DOORS TO INNOVATION AND PROGRESS FOR ALL MANKIND! #releasethecode

@impactcolor yes anyone can code it if they are literally albert einstein 2
us charlatans and measly javascript peasants still need the code #RELEASETHECODE

@petercunha hahaha!

@putuoka 🤫
Releasing code as open source can be hugely beneficial to humanity.
It encourages global collaboration, accelerates innovation, and allows for diverse and inclusive solutions.
Open source projects can educate and inspire new developers, fostering a community that can lead to unforeseen opportunities and advancements.
While it might not directly generate revenue like closed source, its impact on technological progress and community building is invaluable.
LET'S OPEN THE DOORS TO INNOVATION AND PROGRESS FOR ALL MANKIND! #releasethecode

While altruistic as that sounds, it pains me to say that in a capitalist world it should be without backlash that developers of this project can choose whether to publish their code, or start a company and create revenue from their AI breakthrough subsequently using that profit to advance their AI development idea forward, which also is progress for mankind.
TL;DR:

Don't pressure the developers one way or the other. I myself hope they publish it, but I understand if they choose to keep it closed source.

If you want glory and international recognition and Github stars forever, I would recommend you release the code and let people vask in the amazing work you researchers have done. You will be remembered for this break through in animation, or someone can beat you to the punch and release something better in a few weeks and you would have missed your shot at fame. Just saying =) but you do you =D

It’s important to note that no one pushed before or now for the developers to do anything. The paper says “code” and it links to this repo that contains no code.  That’s why people are asking.

@putuoka 🤫
Releasing code as open source can be hugely beneficial to humanity.
It encourages global collaboration, accelerates innovation, and allows for diverse and inclusive solutions.
Open source projects can educate and inspire new developers, fostering a community that can lead to unforeseen opportunities and advancements.
While it might not directly generate revenue like closed source, its impact on technological progress and community building is invaluable.
LET'S OPEN THE DOORS TO INNOVATION AND PROGRESS FOR ALL MANKIND! #releasethecode

While altruistic as that sounds, it pains me to say that in a capitalist world it should be without backlash that developers of this project can choose whether to publish their code, or start a company and create revenue from their AI breakthrough subsequently using that profit to advance their AI development ideas forward, which also is progress for mankind. A lot of good can come of closed source projects just as it is for open source. Chances are they will likely publish it soon based on the fact they built this github page for the project with a citation block in the read me.
TL;DR: Don't pressure the developers one way or the other. Personally, I hope they publish it. However, I understand if they choose to keep it closed source to make a profit. The world doesn't run on moral duty. They likely will provide the code soon.

Bros the only mature adult in this entire thread of children arguing lmfao

You should consider not releasing your code as open source if your business model relies on maintaining a competitive edge and generating revenue from software sales. Following OpenAI's example, keeping your code closed source allows you to control distribution and directly monetize your innovations. It also protects your intellectual property and ensures that you can provide high-quality support and services to your customers, which often serves as an additional revenue stream. This decision is not solely about security and ethics; it's also about establishing a strong financial foundation for sustainable growth.

Not that I am a fan of software patents, but they could patent the method and still release the code. With that said, considering the number of people working towards this goal and beyond and the rate of advancement, I suspect that this will not be the best method for long.

I feel like we’re already a community bonded together just because of this thread 😂

I feel like we’re already a community bonded together just because of this thread 😂

I turned on notifications for when it releases, but I keep getting notified about everyone talking to each other. It's kind of hilarious.
I assume everyone came here after seeing it in our subscription feed on youtube?

Thank you all for your incredible support and interest in our project. We've received lots of  inquiries regarding  a demo or the source code. We want to assure you that we are actively working on preparing the demo and code for public release.  Although we cannot commit to a specific release date at this very moment, please be certain that the intention to provide access to both the demo and our source code is firm.
Our goal is to not only share the code but also ensure that it is robust and user-friendly, transitioning it from an academic prototype to a more polished version that provides a seamless experience. We appreciate your patience as we take the necessary steps to clean, document, and test the code to meet these standards.
Thank you for your understanding and continuous support.

Well, there you go folks. I think all of these issues can be close as resolved. The code is coming; they are just polishing it up.

They have just dubbled down on releasing the code. They are firm on releasing it.

Let's stay civil. Lots of researchers from meta, openai, basically any big company, have a huge team of researchers filled with lots of chinese people. Something about the chinese math system makes it a lot easier to do maths.


API docs file sync

Partial resolves https://github.com/nebari-dev/nebari-docs/issues/157
Changes introduced in this PR:

adds automated file sync of the api docs

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

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[x] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[ ] Yes
[x] No

Documentation
Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?

[ ] Yes, docstrings
[ ] Yes, main documentation
[ ] Yes, deprecation notices

Further comments (optional)
This must be merged after #1511

I'll wait until after the release and rebase on main.


search: Report found_newest/found_oldest

This was really only tested with automated tests, but they're fairly extensive.

Gave this a careful read.  This is great, merged, thanks @showell!

@borisyankov FYI, these new found_newest and found_oldest properties may be helpful for mobile once we're willing to depend on Zulip 1.8, since they mean the app doesn't need to do math to figure out if you've reached the top of bottom of a feed.
@amanagr you can probably depend on this, since I doubt zulip-terminal will be popular before 1.8 is what everyone has.


Multidimensional Data

Due to the linearity of the FFT, a multidimensional transform can be accomplished by transforming all 1D vectors along some dimension, followed by transforming all vectors in a different direction. But it's helpful not to have to do that looping ourselves, so numpy and scipy provide an axis kwarg to their fft, dct, and dst functions, and there is also a multidimensional FFT via fftn, and scipy.fftpack has followed suit with dctn and dstn.
When taking derivatives along different dimensions, we then have to be careful to select (via numpy.slice) the correct directions/vectors to multiply (1j*k)**nu along.
Figure out how to do this such that Laplacians ($\frac{d^2}{dx^2} + \frac{d^2}{dy^2}$), multidimensional derivatives ($\frac{d^2}{dx dy}$), and other useful constructions can be evaluated, with intuitive input from the user, e.g. nu and axes variables.

Based on my mathematical probings, doing a "true" multidimensional transform, multiplying by appropriate $(jk_d)^{\nu_d}$, and combining terms to get a single inverse transform expression isn't really possible for the Chebyshev case, which makes it not very convenient or tractable.
Unlike the truly periodic case, you have to make a last change of variables, and that results in a lot of chain rules that splinter the equations into many terms. You have to do and keep in memory inverse transforms of multiple orders of derivative in the Fourier domain in order to solve for the $\nu^{th}$ derivative the Chebyshev domain.
In another many-terms-related unfortunate turn, the DCT-I, which is most simply equivalent to the FFT and to the interpolation Johnson argues is optimal, which I traced extensively and upon which my inverse transforms rely, has first and last terms outside the middle sum, so that when more dimensions are added, you get an exponential explosion ($3^n$) of terms.
To complicate matters further, there are many possible linear derivative operators $\mathcal{L}$ in multiple dimensions, and each results in its own combination of terms that can or can't be inverse transformed together. I don't see a super easy way to programmatically arrive at the correct terms for arbitrary $\mathcal{L}$, although in theory it's possible, and the few I've done have suggestive echoes of each other.
But worst of all, solving for domain endpoints is still a major issue, way more challenging than in 1D, actually, because you have to consider combinatorial subsets of dimensions approaching the limit simultaneously.
Given this reality, and given the fact that a "multidimensional transform" is still just looping over a bunch of 1D vectors under the hood (albeit with some clever use of the hardware, allegedly), I've opted to do derivatives only along one dimension at a time.
Is this really any better or worse computationally? Well, for $\frac{d^2}{dxdy}$, you (1) transform all vectors along x, (2) transform all vectors along y, collect stuff, then (3) inverse transform along x, (4) inverse transform along y, do your variable transformation. If we do the dimensions one at a time, we just change the order: 1, 3, 2, 4, and we get to use simpler variable transformations and not have to deal with as many edge cases, so no we haven't saved anything by using dctn and friends. For $\Nabla^2$? (1) transform all vectors along x, (2) transform all original vectors along y, (3) inverse transform the 1st derivative along x, (4) inverse transform the 2nd derivative along x, (5) inverse transform the 1st derivative along y, (6) inverse transform the 2nd derivative along y, add, variable transformations. It's 6 sets of O(N log N)s no matter how you slice it. $\frac{d^3}{dx^2 dy}$? I've got to work this one out on paper, but I wonder whether it's no savings too, in which case really why bother with this, beyond vectorizing in numpy over single dimensions for speed and convenience? (I'd much rather use a single call than have to write a python tool for each vector along a dimension.)
However, in the periodic case, where it really may be convenient to use fftn and friends, best practice would be to do so! I'll look in to this for #7.

I've worked out the $\frac{\partial^3}{\partial x^2 \partial y}$ case, and it's actually worse to do it with "true" multidimensional transforms!
We already know $\frac{\partial^2}{\partial x^2} \hat{y}(\theta_1, \theta_2)$ from doing the $\nabla^2$ case, so we get!
$$ \frac{\partial}{\partial y} ( \frac{\partial}{\partial \theta_1} \hat{y} \cdot \frac{d^2 \theta_1}{d x^2} + \frac{\partial^2}{\partial \theta_1^2} \hat{y} \cdot \left( \frac{d \theta_1}{d x} \right)^2 $$
If we do a little calculus, applying the multidimensional chain rule, then we end up with:
$$ \frac{\partial^2}{\partial \theta_1 \partial \theta_2} \hat{y} \cdot \frac{d \theta_2}{d y} \cdot \frac{d^2 \theta_1}{d x^2} + \frac{\partial^3}{\partial \theta_1^2 \partial \theta_2} \hat{y} \cdot \frac{d \theta_2}{d y} \cdot \left( \frac{d \theta_1}{d x} \right)^2 $$
Here all the $\frac{d}{d \theta}$ terms can be readily evaluated from $\frac{1}{-\sqrt{1-x^2}}$ and end up not really affecting which inverse transforms we have to do, so let's ignore them.
Notice what's left: A multidimensional derivative of $\hat{y}$ and another, distinct multidimensional derivative of $\hat{y}$. This is because the second derivative in $x$ splintered, so now we've got multiple terms. At some stage of the algorithm, we don't actually have $\hat{y}$ yet, only $Y_{k_1 k_2}$. Taking different derivatives, we end up with different $Y_{k_1 k_2}'$ and have to inverse transform both sets.
This means we have to do two 2-dimensional inverse transforms to get back out of the frequency domain, and remember we had to do a transform along each dimension to get in to the frequency domain, for a grand total of 2 + 2*2 = 6 O(N log N)*O(N) routines (extra O(N) from iterating $\forall$ the vectors in a dimension). Compare this to doing the dimensions separately: We transform along $x$, then inverse transform twice (once for each of the splintered terms), then we take that result and transform along $y$, then inverse transform once (because only one term for the first derivative). That's a total of 1 + 2 + 1 + 1 = 5! So we actually save work doing the dimensions separately!
You can imagine how the situation would be all the worse for higher derivatives, e.g. for $\frac{\partial^4}{\partial x^2 \partial y^2}$ you'd get four different multidimensional derivative terms and have to do two sets of transforms for each of them to get back out of the frequency domain. Add the 2 to get in to frequency domain, and that's 10. Compare to 2*(1 + 2) = 6 if doing them separately.
So not only is it much simpler in terms of mathematical expressions to split up the dimensions, it's actually computationally the smart thing to do. Hence I'll consider this task done for the Chebyshev case. Of course in the Fourier case there is no such splintering of terms, doing true multidimensional derivatives would still be a good idea.


Update and rename SafeSingeltonFactory.sol to SafeSingletonFactory.sol

Hey! Thanks for the PR. Unfortunately we can't merge this, for more info please see https://github.com/safe-global/safe-singleton-factory/pull/228


Create new tag

@artemeff would you mind tagging master?

yep, sorry, tagged

Thanks for the tag and maintenance of the repo!

you're welcome! :)


Need guidance for JLC assembly: missing BOM & CPL files

First, thanks for your work on this awesome project!
I'm planning to order the board from JLC and also get assembled by them, because I may not be able to solder all the tiny parts together.
In the step to upload BOM & CPL .csv files, I don't have them.
From your ibom.html, I can extract the list of parts, but I don't find the positions of each part.
Can you show me how to get the desired files?
Here is an example of .csv files that I have successfully uploaded to JLC to get assembly in the past:
https://github.com/JeremyBois/Ogen/blob/main/PCB/data/production/V1.2/bom.csv
https://github.com/JeremyBois/Ogen/blob/main/PCB/data/production/V1.2/positions.csv

You probably won't be able to build this automatically. Placeholder tolerances are broken.


Flutter for web support

Hello
I'm using flutter_masked_text in my app and now I need to create a web version of some views and would be very nice if this package support Flutter Web :)
Are you thinking in add support for Flutter Web soon? This is in your plans?
Thanks!

Hi @emersonsiega !
Thanks for the request.
Once I have time, yes, but I need to check how flutter web works (I didn't check it yet).

Works great in web. I'm using it.


Add isServer prop to getInitialProps

It would be nice to have a slightly more clear argument to tell you whether you're rendering from the client-side or server-side.
export default class extends React.Component {
  static getInitialProps ({ isServer }) {
    return isServer ? {...} : {...};
  }
  render () {...}
}

Opening this up to see how you feel about it.

Coverage increased (+2.5%) to 59.936% when pulling 0cfa81ad17bc353737599dbae5f20a822ce23d51 on thejameskyle:isServer into 955f6817c41fc8bd518309390080be8250c3ec13 on zeit:master.

We didn't add isServer by design for now.

it should be a value per environment (not per method call).
easy to define it if you need.

Additionally, I think generally feature detection would be better than detecting runtime environment.

Yeah, isServer is more of an environment setting. We could have import isServer from 'next/env' or sth along those lines in the future. Thanks @thejameskyle


fix a typo in readme

closing after discussion with @kexinhuang12345 . this is handled in another PR.


No build step

Removes the build step from .jsx to .react.js by making webpack understand .jsx and allowing node to transpile on demand with sourcemap support.
Lint .jsx files
Add test coverage for generated config.js

If you get an error of XMLHttpRequest is not defined then make sure to do a clean npm install. There is a new version of source-map-support which Lab depends on that was released a few hours ago. Lab does not use shrinkwrap dependencies so we get the fix without a new Lab release.

Thanks! I can't wait to check this out after work. :tada:

These changes are great. Great work getting this done.
I made some changes you can pull into your fork's branch and then we can merge this.

Nice job fixing the issues. Interesting how you solved them!
I know config.js is generated and that might be why you don't want to add a test, but my OCD can't take that Coverage: 99.99% (1/12464) line! :)

Oh how interesting. I have at test for this locally that was identical to the test in your PR. I thought it was a mistake that you added a "duplicate" test... now I see it's being ignored via .gitignore.

Also, instead of -c, you could include -t 100 in the Lab command line. It will fail the travis builds if you are under 100% test coverage.

Ah, ok. Now I see that although the threshold defaults to 100 using the -t 100 changes the exit status. Thanks :+1:, let's get that in here too then.


Is it possible to show a full year in month view?

Is it possible to show a full year in month view?  I want to make a page that shows all 12 months of the year.  I want the user to be able to see the current month and as they scroll down they see all the following months.  I don't need lazy load or anything just want to be able to tell month view to show 365 days, not just a month's worth.
Is it possible to show a full year in month view?

@wootwoot1234 I think this is possible if you're okay with rendering all the months of the calendar (it would get very long). I was able to do this with a previous iteration of the calendar but we also forked the calendar as well in order to do this so it was probably all custom code. We wanted to render two months at a time instead of just one and I was able to do this. I think it required rendering two separate views, one with the current month, and the other with the next month. In your case you would do this 11 times instead of the 1 extra time that I did.

Closing due to inactivity.


Helm Uninstall Deletion Protection with Pre-Delete Hooks

I'm working with a client interested in adding a "deletion protection" feature in their Helm chart. On helm uninstall, the workflow would be:
if <some condition>:
  Do not uninstall. Reset Helm release status to 'deployed'
else:
  Uninstall the release

We tried implementing this with a pre-delete hook, where the hook would exit 1 in attempt to fail the deletion if necessary, but this instead keeps the release stuck in the uninstalling state and cannot be upgraded. I thought about helm rollback if the release is stuck, but this won't work if there's only 1 revision (the one stuck uninstalling).
Is there a way to cancel a Helm uninstall, whether it be through a hook or some other means? If not, can the Helm release status be reverted to deployed if a pre-delete hook fails?

This will be beneficial where pre-delete hook can verify if the delete conditions are met then attempt delete, else reject delete.

This will be beneficial where pre-delete hook can verify if the delete conditions are met then attempt delete, else reject delete.

+1. I think it would really be beneficial if there would be an annotation for something like /hook-stop-on-fail so if the hook is pre-... and it fails, it would stop whatever command user has typed.

Any progress on this issue ?  I will encounter the same problem because I want to delete external resources at un-install.  The problem comes if they cannot be deleted because dependencies have to be removed from the external resources.

No progress has been made as far as I'm aware, however I will drop this link here if someone wants to follow up and propose ideas:
https://github.com/helm/helm/blob/main/CONTRIBUTING.md#proposing-an-idea


How to change/remove default messages shown when starting project as a console app?

How can I change/remove default messages shown when starting project as a console app?
For example I am seeing messages:

Starting up as a console service host
The {{SERVICE NAME}} is now running, press Control+C to exit.

I want second one not to be displayed on console app.

No way to customize that, should be a pretty easy job, feel free to contribute with a PR.


Fix docstring

I think this docstring was incorrect. I updated to reflect the truth.

Processing this pull request

Merged into branches master, iso6 in 72a8033b83e03602f8425e51511a33bc2909c519

Processing #5473.

Processing #5473.


Failing execution_summary

Hi all,
I am currently facing an issue with the execution_summary where the attributes is of below format.
attributes = set([datetime.datetime(2017, 8, 4, 0, 0), datetime.datetime(2017, 8, 3, 0, 0)])
Error :
  File "<console>", line 1, in <module>
  File "/luigi/luigi_shell.py", line 315, in run
    scheduler_port=options.luigi_port)
  File "/luigi/luigi/interface.py", line 270, in build
    return _schedule_and_run(tasks, worker_scheduler_factory, override_defaults=env_params)['success']
  File "/luigi/luigi/interface.py", line 204, in _schedule_and_run
    logger.info(execution_summary.summary(worker))
  File "/luigi/luigi/execution_summary.py", line 428, in summary
    return _summary_wrap(_summary_format(_summary_dict(worker), worker))
  File "/luigi/luigi/execution_summary.py", line 362, in _summary_format
    str_output += '{0}\n'.format(_get_str(group_tasks[status], status in _PENDING_SUB_STATUSES))
  File "/luigi/luigi/execution_summary.py", line 154, in _get_str
    first, last = _ranging_attributes(attributes, param_class)
  File "/luigi/luigi/execution_summary.py", line 209, in _ranging_attributes
    next_attributes = {param_class.next_in_enumeration(attribute) for attribute in attributes}
  File "/luigi/luigi/execution_summary.py", line 209, in <setcomp>
    next_attributes = {param_class.next_in_enumeration(attribute) for attribute in attributes}
AttributeError: 'str' object has no attribute 'next_in_enumeration'```

a follow up question; what should be the param_class value ?


Unify logging in xrdp/*

Follow-on pull request to #1633 which migrates all logging in the xrdp directory to use the LOG() and LOG_DEVEL() macros.
Changes:

Migrate logging to the LOG() and LOG_DEVEL() macros (using text transform script)
error logs use the LOG macro
add XRDP_BOOT_LOG_LEVEL environment variable to enable run time debugging of xrdp before the logging sub-system is initialized.
update code formatting with astyle for all files in xrdp/*

This pull request is ready for review.

@aquesnel
Hi, thanks again for your big contribution to the log system.  I'd appreciate it if you write up documents about the new log system on the wiki.
This is written by myself years ago. Feel free to edit and replace it.
https://github.com/neutrinolabs/xrdp/wiki/Reworking-logs

@aquesnel
Hi, thanks again for your big contribution to the log system.  I'd appreciate it if you write up documents about the new log system on the wiki.
This is written by myself years ago. Feel free to edit and replace it.
https://github.com/neutrinolabs/xrdp/wiki/Reworking-logs

@metalefty that's a good idea, I will update the wiki with documentation about the logging system.
Since the unification of the logs is not yet complete I plan to add a new section describing the unified log system and it's capabilities. Once the log unification work is complete them I'll remove the outdated sections from the wiki.
The documentation that I'll write will be a high level overview of the logging and then link to the existing documentation in the code and the man pages

https://github.com/neutrinolabs/xrdp/blob/c76c58044119e6fc2bbe7fa6e9819448e07582ea/common/log.h#L97
https://github.com/neutrinolabs/xrdp/blob/c76c58044119e6fc2bbe7fa6e9819448e07582ea/docs/man/xrdp.ini.5.in#L216

Do you know if there is a way to have the doxygen and man pages rendered and available online so that they can be referenced online?
I looked into GitHub pages and netlify but I didn't find a clear solution for making the doxygen and man pages available online.

@metalefty that's a good idea, I will update the wiki with documentation about the logging system.
Since the unification of the logs is not yet complete I plan to add a new section describing the unified log system and it's capabilities. Once the log unification work is complete them I'll remove the outdated sections from the wiki.
The documentation that I'll write will be a high level overview of the logging and then link to the existing documentation in the code and the man pages

https://github.com/neutrinolabs/xrdp/blob/c76c58044119e6fc2bbe7fa6e9819448e07582ea/common/log.h#L97
https://github.com/neutrinolabs/xrdp/blob/c76c58044119e6fc2bbe7fa6e9819448e07582ea/docs/man/xrdp.ini.5.in#L216

Do you know if there is a way to have the doxygen and man pages rendered and available online so that they can be referenced online?
I looked into GitHub pages and netlify but I didn't find a clear solution for making the doxygen and man pages available online.

I agree it's not immediately obvious how to link in doxygen and manpages. There are a few people using gh-pages to do this, but committing the output of doxygen to the same repo seems crazy to me.

I agree it's not immediately obvious how to link in doxygen and manpages. There are a few people using gh-pages to do this, but committing the output of doxygen to the same repo seems crazy to me.

@metalefty I've written the Logging wiki page and updated the Reworking logs page to reference the new page. Can you please review it and let me now if you have any feedback.
@matt335672 I agree that committing the output of doxygen to the repo seems crazy.

@metalefty I've written the Logging wiki page and updated the Reworking logs page to reference the new page. Can you please review it and let me now if you have any feedback.
@matt335672 I agree that committing the output of doxygen to the repo seems crazy.

Good work.
Minor comments/suggestions
Logging

use xrdp rather than XRDP to refer to the project (see here). @metalefty made this comment in relation to one of my PRs relatively recently, which is why I wrote the Wiki page.
Chansrv log is per-user rather than per-system. So it appears in $XDG_DATA_HOME/xrdp or $HOME/.local/share/xrdp. Alternatively you could just say that for any system, log locations are documented in the man pages.
sesman forks too to run the session leader, so the  comment under 'log files' can be expanded to incluse sesman.

Reworking logs
Might be worth saying explicitly in the g_write/g_writeln section that when xrdp and xrdp-sesman are daemonised they redirect stdout to /dev/null anyway, so some of the existing code which appears to be logging errors actually isn't. I've been caught by this a few times, lastly in #1776.

Good work.
Minor comments/suggestions
Logging

use xrdp rather than XRDP to refer to the project (see here). @metalefty made this comment in relation to one of my PRs relatively recently, which is why I wrote the Wiki page.
Chansrv log is per-user rather than per-system. So it appears in $XDG_DATA_HOME/xrdp or $HOME/.local/share/xrdp. Alternatively you could just say that for any system, log locations are documented in the man pages.
sesman forks too to run the session leader, so the  comment under 'log files' can be expanded to incluse sesman.

Reworking logs
Might be worth saying explicitly in the g_write/g_writeln section that when xrdp and xrdp-sesman are daemonised they redirect stdout to /dev/null anyway, so some of the existing code which appears to be logging errors actually isn't. I've been caught by this a few times, lastly in #1776.

@matt335672 I've updated the logging wiki page based on your feedback. I didn't update the reworking logs page since I didn't change any connect on that page.
Please let me know if you have more feedback.

@matt335672 I've updated the logging wiki page based on your feedback. I didn't update the reworking logs page since I didn't change any connect on that page.
Please let me know if you have more feedback.

@metalefty I've removed the bootstrap logging that you said was hacky. Let me know if you have more feedback.

Give me a couple of days to look at this - I've not managed it yet.

@matt335672 , Thanks for reviewing and catching the signal handler issue. I've implemented the feedback that you suggested. Please let me know if you have more feedback before this can be merged.


TS is incompatible with geometric multigrid

See https://lists.mcs.anl.gov/pipermail/petsc-dev/2015-February/016907.html

Oh boy, this is disappointing. I wonder if something could be done after all the work the firedrake team put into making the firedrake geometric interface.


Change kubearchive go module name to match standard naming convention

Go modules uploaded to github should be named like this: github.com/<namespace>/<repo name>
See Organizing a Go module
kubearchive's root module name should be github.com/kubearchive/kubearchive
Will also need to refactor go code that imports other kubearchive go code

I need to keep track of other PRs that get accepted before this one so that import lines will be fix


feature: disable twilight for certain filetypes

Did you check the docs?

[X] I have read all the twilight.nvim docs

Is your feature request related to a problem? Please describe.
twilight starts in Telescope, dashboard which is not intended
Describe the solution you'd like
an excluded_filetypes in twilight config
Describe alternatives you've considered
none
Additional context

dashboard ⬆

exclude = {}, -- exclude these filetypes


PyPI page shows raw ReST source

https://pypi.python.org/pypi/pep257 looks like this:

Typically this happens when PyPI encounters a ReStructuredText syntax error or a feature that is explicitly disabled for PyPI (like non-absolute URLs in links).
Usually I use restview's --pypi-strict mode to discover the source of the error, but here restview doesn't complain, so I"m baffled.

I checked the current master branch against testpypi and it looks okay, so I guess it was fixed somewhere along the way. I will close the issue after it is confirmed against the real pypi server.

There have been several updates on PyPI recently to fix formatting issues found by users. The changes have been deployed to both testpypi and pypi itself. You should be able to close this now if it works on testpypi.

Solved as of version 0.4.1


Can we add a list of IRL meetups to the Hangouts page?

Issue originally created by @ProkhorZ
This issue was created on gitlab and then migrated here. Only the original post was migrated, not the comments. Please take a look at the discussions on the original Gitlab issue before commenting here: https://repo.getmonero.org/monero-project/monero-site/-/issues/945

It would be nice if people discovering Monero could see whether there are regular meetups for Monero fans in their area.
There are active Monero meetups in Toronto, Vienna, Johannesburg, Utrecht, Berlin, Munich, Los Angeles and Zürich. And maybe I missed some?
Downside: all these meetups use one centralized commercial website. But linking to all relevant meetups from our own website is a first step towards relying less on meetup.com. What do you think?

This issue has been open for more than an year, if there is no interest in implementing this, i will just go ahead and close it. Consider that such feature would require a considerable amount of time in maintainance.
Ping people who partecipated to the discussion on gitlab: @el00ruobuob @lh1008 @ProkhorZ


Add a simple abstract frame navigation interface

Closes #118
This PR adds a simple abstract frame navigation interface for later use by the GUI (#107) and implementation in lib2 (#125).

As nothing is implemented, you can use the interface keyword instead of abstract class.
Also, I would propose forward: Boolean instead of direction: Boolean as it would be more meaningful.


Error with libjcef.so linux-kylin-v10-arm64

Please follow the format strictly and do not modify the template. Please always test with the official sample app here (you will need to download the version using the maven artifact you want to test). You can add your own text under Additional information. In case the build was not working, please consider adding the console output, screenshots and steps to reproduce.
Tag
v108.4.13+jcef-natives-linux-arm64-jcef-c1f0745+cef-108.4.13+ga98cd4c+chromium-108.0.5359.125.jar
OS (linux/windows/macosx)
linux
Version/Flavor (e.g. Ubuntu 20.04, Windows 10, Big Sur)
kylin v10 (4.4.131-20200618.kylin.desktop.android-generic)
Arch (amd64/i386/arm64/arm)
arm64
Report as working? (Y/N)
N
Did you test with the official sample app? (Y/N)
Y
Additional information

It appears you have a different set of base libraries on your system than jcef expects. You can either install glibc 2.27 on your system or compile jcef on your system using the wrappers from jcefbuild or the manual build instructions from the jcef repo. Sadly I can not help here.


Fix issue where clear button was not clearing the selected color anymore

Thanks for the fix! Will merge now.
Happy new year :)


The performance and limitation of Distrinet after docker replacement

Use the same servers to deploy the original Distrinet and the Distrinet replaced by docker respectively, and compare their performance.

We tested the performances of these examples: a linear topology with 6 hosts and 6 switches; a binary tree whose depth is 3; customized topology.
We care about these metrics: the connection of the topology and the bandwidth of iperf.

Linear topology with 6 hosts and 6 switches:
lxd:pingall

lxd:iperf

docker:pingall

docker:iperf

Customized topology: the topology is the same as early test for Distrinet.
lxd:pingall

lxd:iperf

docker:pingall

docker:iperf

Otherwise, we added a new module to test the time to establish and stop the topology.And we noticed that after the docker replacement, time performance is better.
lxd:

type
start time(ms)
stop time(ms)

linear_10
43283.724
17412.770

linear_20
85042.979
29419.694

linear_30
145570.518
51053.180

linear_40
189553.188
73760.429

tree_depth=2_fanout=2
21257.863
9104.821

tree_depth=2_fanout=3
30518.782
13705.951

tree_depth=3_fanout=2
33082.372
14239.144

tree_depth=3_fanout=3
81417.790
28824.049

custom
46788.506
22290.356

docker:

type
start time(ms)
stop time(ms)

linear_10
39618.796
14586.549

linear_20
74643.517
29851.002

linear_30
116308.483
49878.966

linear_40
150765.474
71019.690

tree_depth=2_fanout=2
17055.762
6914.141

tree_depth=2_fanout=3
29184.385
13014.671

tree_depth=3_fanout=2
31833.954
11628.452

tree_depth=3_fanout=3
75521.407
29416.155

custom
45623.731
18247.342

Upper bound for linear topology:
lxd container: 90 hosts and 90 switches can be established.

lxd container: when establish 99 hosts and 99 switches, this error occured.

docker container:300 hosts and 300 switches can be established.

docker container:400 hosts and 400 switches can be established.However, some packages are lost.


Update extensions_vk.cpp to work with latest Vulkan headers.

Some video structures were renamed and hence nvpro-code doesn't build with the latest Vulkan headers anymore.
Also, this adds EXT_mesh_shader and other extensions from the 226 release.

Looks good to me - thanks, Timur! We've got some additional changes to the extensions_vk.py generation script I'll add in after this to make configuring this easier in the future.
Thanks again!


Expose an Admin API

Spin keeps its logs and manifest on the filesystem, which makes them opaque to anything outside system its hosted on. Could we expose an API for administration of Spin apps? I think it would be an aliasable route, and flagged off by default. Maybe on a path like http://localhost:3000/_spin/?
I don't know what the shape of this API would be, but for my purposes something like

/logs/:id?stdout&stderr - Exposes the logs of any component as a service, something like HTTPAppender
/ -  Exposes the manifest as JSON

... would do the job!

I like this @ecumene ! I wonder how we handle AuthN/AuthZ on these privileged endpoints. Perhaps to expose something like this we should start a discussion for API security for Spin? What do you think?

Perhaps to expose something like this we should start a discussion for API security for Spin?

Hasura exposes an admin console for their service, but it's a flag. Maybe that's something we could do?

I wouldn't be opposed to that! Would you be interested in putting together a SIP so we can gather broader feedback? Or do you feel more comfortable chatting this out in this issue for a bit?

I'll take a crack at a SIP 😁

This sounds great!
I think a flag to expose that initially sounds great — at some point we will have to integrate authz for the components / paths..
Looking forward to the SIP!


Provide Support for Gap Assessment

In order to support the ongoing GAP assessment, I will provide/upload artifacts and other documentation as necessary.
Acceptance Criteria

[ ] Upload Gap Assessment Artifacts to Smartsheet

Security considerations
3PAO Gap Assessment

Closed ticket as it has been done last week.


Treat HTTP/2 stream errors as spurious network errors.

Closes https://github.com/rust-lang/cargo/issues/6788.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+
Thanks again for this!

:pushpin: Commit cc29c2b60969dbf00ad230c42c70b0584c52bd55 has been approved by alexcrichton

:hourglass: Testing commit cc29c2b60969dbf00ad230c42c70b0584c52bd55 with merge f2ea95a37a1921f16ddcb29209bbe2caa36dd600...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: alexcrichton
Pushing f2ea95a37a1921f16ddcb29209bbe2caa36dd600 to master...


Add WETH9 contract for Wrapped tSSC

Add WETH9 contract for Wrapped tSSC
deployed at 0xF9019F905f5828930094300D8949bDAc63B054EB on 3h

After having read the LayerZero docs so far, it is almost certain that we would have to make our wTSSC token contract compatible with xERC20 standard (with LZ's _lzSend, _lzReceive like functions). I will provide more lead on this as I dive into Omnichain Fungible Tokens (OFT).


Add "Github" bugtracker adapter

As the native "Rational Team Concert" adapter which allow to make relations between "problems" in ARA and "Defect" in the bugtracker, it will be wonderful to make the same relation with "Github".

Hi Julien !
This feature is already done in the version 3.1.0 :) https://github.com/Decathlon/ara/releases/tag/v3.1.0
You can use it in your Project's setting page, the Defect Adapter dropdown menu will contains RTC and GitHub :)


Terms meanings in trajectory json files

I really appreciate your amazing work and the codes that you provided.
I have encountered some terms that are not mentioned in the paper so I want to clarify them.

negative_prompt
surface_normal_threshold
single color for text_prompt: I thought the same text prompt execept for the floor and the ceiling would be used for each came pose.

Thank you for your help!

Problem solved for negative_prompt and surface_normal threshold!
In addition, I want to ask what is bbox in the codes!
Thank you so much!

We found it is helpful to use "single color" as prompt for completion. If only a few pixels need to be inpainted, we do not want to create another object.
Bbox is the bounding box of the generated mesh.

Thank you so much for your quick reponse.
Why would you need a bounding box for the generated mesh?

We use it during completion to constrain where the additional camera poses can be placed.

Thank you so much for your kind answers!


ImportError

I am using VSCode to run python script. Recently I wrote a data process script, but when run the script in VSCode, ImportError was arised. I also run using RUN AND DEBUG in VSCode, everything is OK. What happened?

I am using Macbook VSCode:)


basic structure for empty pie chart

Hi,
Thanks for the pull request - please adhere to the PR template when submitting pull requests.
Also, please remove any commented out code/dead code and all debugger statements also.
I'm going to close this PR so you can open a new one explaining in greater detail the reason for the PR.
Thanks.

I have something to handle empty pie chart data, I'll take the opportunity to deal with update and removal of data since I'm in there and update the repo soon.

Sounds good!  The PR is only for reference in case it is needed.  I left
the debuggers in areas where I made the changes,  so that it is easy to
see.  No need to merge,  just for reference.
Thanks and have a great weekend!
Xiaofan
On Jul 29, 2016 5:34 PM, "FrenchBen"<EMAIL_ADDRESS>wrote:

I have something to handle empty pie chart data, I'll take the opportunity
to deal with update and removal of data since I'm in there and update the
repo soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PredixDev/px-vis-pie-chart/pull/3#issuecomment-236325901,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANlUgpDE3ovumPuWo4hflWWKhMbjfcPVks5qapwJgaJpZM4JYqiR
.

@xiaofanwu Pie should now support empty data as well as update to data in the latest version. Let me know if that works for you.


vEOS fails to build with certain release names

Hi
Arista uses some slightly weird release number scheme, that the makefile fails on:
htj@pyrite:~/src/vrnetlab/veos$ make
Makefile:7: warning: overriding recipe for target 'docker-pre-build'
../makefile.include:24: warning: ignoring old recipe for target 'docker-pre-build'
for IMAGE in vEOS-lab-<IP_ADDRESS>F.vmdk; do
echo "Making $IMAGE";
make IMAGE=$IMAGE docker-build;
done
Making vEOS-lab-<IP_ADDRESS>F.vmdk
make[1]: Entering directory '/home/htj/src/vrnetlab/veos'
Makefile:7: warning: overriding recipe for target 'docker-pre-build'
../makefile.include:24: warning: ignoring old recipe for target 'docker-pre-build'
cp *.iso docker/
ERROR: Incorrect version string
../makefile.include:27: recipe for target 'docker-build' failed
make[1]: *** [docker-build] Error 1
make[1]: Leaving directory '/home/htj/src/vrnetlab/veos'
../makefile.include:18: recipe for target 'docker-image' failed
make: *** [docker-image] Error 2
Here are the file names:
vEOS-lab-<IP_ADDRESS>F.vmdk
vEOS-lab-4.17.1F.vmdk
The image builds fine with the latter one, but not with the first one.

Thx for reporting! :D

Btw, please let me know if it works or not ;) and overall just feedback on the vEOS image would be nice since I'm not using it myself..

vEOS-lab-4.17.1F.vmdk booted fine as seemed to work. Haven't tried interface mapping.
Haven't tried vEOS-lab-<IP_ADDRESS>F.vmdk yet.
I got VMX running and realized I need something beefier than my laptop to run a this (3:36 boot time, and 150% idle, wtf :-))

Ok.
The boot time of the vMX sucks right now because it restarts the control plane once. This is just part of how vMX works. The control plane can be used in vRR mode or vMX and so it requires a reboot to change the mode. We could move this part to the build time instead, which would then lengthen build time to like 2 minutes but would cut that off the boot time.
XRv is also slow in booting and I'm not aware of anything that I can do to speed that up :/
I guess 150% CPU is the forwarding plane of the vMX, right?

Just to confirm, the vEOS-lab-<IP_ADDRESS>F.vmdk images build and boots fine after the fix.


python import error

I ran into an issue installing the server. There seems to be a python problem.
Command run:
python3 medallion/scripts/run.py --conf-file sample-config-with-memory-backend.json.
Error I saw after I ran the command:
Traceback (most recent call last):
File "medallion/scripts/run.py", line 10, in
from medallion.common import (
ImportError: cannot import name 'APPLICATION_INSTANCE'
Any idea on what is causing this error and how to fix it?
Thanks

How to reproduce this?  I tried with a git clone of the master branch, using the config file in the test directory, and it worked:
>python .\medallion\scripts\run.py -c .\medallion\test\data\config.json
 * Serving Flask app 'medallion' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

I used python 3.9.13 on a win10 laptop.

Hah, just realized that config file was a sample that was in the repo!  (I always use my own, and am aware of the unit tests and that data directory, and forgot those others were there.)
Ok, so it worked on master branch with sample-config-with-memory-backend.json as well:
>python .\medallion\scripts\run.py -c .\sample-config-with-memory-backend.json
 * Serving Flask app 'medallion' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

This may be an environmental issue, because I see you use a windows operating system.
For context, the exact steps I executed:

Installed Centos7 on a ESXI vm
Ran yum install git
Ran git clone https://github.com/oasis-open/cti-taxii-server.git
Ran cd cti-taxii-server
Ran yum install python3 (which installed python 3.6.8)
Ran python3 -m pip install --upgrade pip
Ran python3 -m pip install medallion
Ran python3 medallion/scripts/run.py --conf-file sample-config-with-memory-backend.json

I don't have access to a centos7 VM to accurately replicate your environment, but just from looking at the steps, I see some confusion.  In step 7, you are installing medallion from pypi.  In step 8, you are running medallion from your local git clone, which is a different codebase.  You're mixing two different codebases: the git clone codebase and the pypi version.  You need to decide which version you want to run.
If you want to use the version from your git clone directory, from within that directory run pip install . (or python3 -m pip ..., as you have done).  That will cause pip to create an installable package from the sources and install it into your python environment (I don't see creation of a virtual environment in your list of steps, so I assume you can manage your environment).
If you want to use the version from pypi, all you need is to run pip install medallion.  There is no need to git clone a repo; the installable package will be downloaded and installed automatically (though you will still need to get a config file from somewhere).
In either case, a medallion executable is created as part of the installation, so you can start medallion as medallion -c <config file>.  If you have the python environment script directory in your $PATH, you should be able to run it.  You don't need to use the run.py script directly.


6502 CPU Implementation

Closing in favor of CPU tagged instruction implementation tickets.

Closing in favor of CPU tagged instruction implementation tickets.


Verification of Correctness

The Static vs Dynamic trick that this library seems sound based on my informal reasoning. It would be nice to verify that it is actually sound. I am not capable of a rigorous proof, but maybe someone else could.

With https://github.com/andrewthad/linear-containers/pull/6, I've added a rough explanation of how static and dynamic references work. This should hopefully help anyone who is trying to understand what's going on.


fd -i returns negative IUsed

Windows Version
Microsoft Windows [Version 10.0.22621.1555]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
run df -
Expected Behavior
Should not see negative numbers under IUsed
Actual Behavior
observe negative numbers
Diagnostic Logs
No response

I am not seeing this locally, can you share the exact commands you are running and the output you are seeing please?

Cool thanks for the info - will investigate.


[SPARK-30532] DataFrameStatFunctions to work with TABLE.COLUMN syntax

What changes were proposed in this pull request?
DataFrameStatFunctions now works correctly with fully qualified column name (Table.Column syntax) by properly resolving the name instead of relying on field names from schema, notably:

approxQuantile
freqItems
cov
corr

(other functions from DataFrameStatFunctions already work correctly).
See code examples below.
Why are the changes needed?
With current implementation some stat functions are impossible to use when joining datasets with similar column names.
Does this PR introduce any user-facing change?
Yes. Before the change, the following code would fail with AnalysisException.
scala> val df1 = sc.parallelize(0 to 10).toDF("num").as("table1")
df1: org.apache.spark.sql.Dataset[org.apache.spark.sql.Row] = [num: int]

scala> val df2 = sc.parallelize(0 to 10).toDF("num").as("table2")
df2: org.apache.spark.sql.Dataset[org.apache.spark.sql.Row] = [num: int]

scala> val dfx = df2.crossJoin(df1)
dfx: org.apache.spark.sql.DataFrame = [num: int, num: int]

scala> dfx.stat.approxQuantile("table1.num", Array(0.1), 0.0)
res0: Array[Double] = Array(1.0)

scala> dfx.stat.corr("table1.num", "table2.num")
res1: Double = 1.0

scala> dfx.stat.cov("table1.num", "table2.num")
res2: Double = 11.0

scala> dfx.stat.freqItems(Array("table1.num", "table2.num"))
res3: org.apache.spark.sql.DataFrame = [table1.num_freqItems: array<int>, table2.num_freqItems: array<int>]

How was this patch tested?
Corresponding unit tests are added to DataFrameStatSuite.scala (marked as "SPARK-30532").

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Test build #119807 has started for PR 27916 at commit 45c1d8b.

Merged build finished. Test PASSed.

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

Test build #119807 has finished for PR 27916 at commit 45c1d8b.

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

Merged build finished. Test FAILed.

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

Fixed tests.

Test build #119830 has started for PR 27916 at commit 2f24ae0.

Merged build finished. Test PASSed.

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

Test build #119830 has finished for PR 27916 at commit 2f24ae0.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Tests failed because of something that seems completely irrelevant (in hive). Digging deeper to understand why.

retest this please

Merged build finished. Test PASSed.

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

Test build #120044 has started for PR 27916 at commit 2f24ae0.

Test build #120044 has finished for PR 27916 at commit 2f24ae0.

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

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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

Test build #120149 has started for PR 27916 at commit 37f441e.

Test build #120149 has finished for PR 27916 at commit 37f441e.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Looks like tests failed for the same reason as previously. Could not replicate this locally (local build & tests are just fine).

retest this please

Test build #120176 has started for PR 27916 at commit 37f441e.

Merged build finished. Test PASSed.

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

Test build #120176 has finished for PR 27916 at commit 37f441e.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest  this please

Test build #120185 has started for PR 27916 at commit 37f441e.

Merged build finished. Test PASSed.

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

Test build #120185 has finished for PR 27916 at commit 37f441e.

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

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

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

Test build #120207 has started for PR 27916 at commit 37f441e.

Test build #120207 has finished for PR 27916 at commit 37f441e.

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

Merged build finished. Test FAILed.

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

Test build #120561 has started for PR 27916 at commit dd9f258.

Merged build finished. Test PASSed.

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

Test build #120561 has finished for PR 27916 at commit dd9f258.

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

Merged build finished. Test PASSed.

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

@cloud-fan Merged with latest master. Now tests work (previously they failed with unrelated issues).

thanks, merging to master/3.0!


Create release Asset of fork

With the change to WowUp, you can now have it install addons directly from a URL (Like GitHub!). https://wowup.io/guide/get-addons/overview
The only issue is that it is looking for a release asset in the branch (Im guessing it doesnt just like Tags).
I saw on the parent repo you were possibly trying to publish so this could be an easy way to add your fork for now.

Yep I was mostly waiting on permission from the original author before formalizing any release. I would also need to do some rebranding. I'll give it a few more days to hear from him before I move forward.

Any chance you've got an update on this? I check this fork a few times a month to make sure i've got the most up-to-date version, but if WoWUp could check it would be much simpler.

Sorry, not yet. It's less of a technical holdup and more of a legal one. The upstream project is All Rights Reserved, which technically means without express written permission I can not legally host a fork on Curseforge or WoWUp. I've emailed the author, and he hasn't responded thus far.

So I'm making good headway on this!
I had only meant to start rebranding to a the new name of "DevTool" which I've been toying with, but I ended up going on a performance and stability sprint. The original version of this addon used a bespoke linked list data model for storing the active data in the main window, and unfortunately it was pretty fragile and did not scale well into the tens of thousands of nodes, such as when you are viewing _G. I tried fixing the linked list model, but it ended up being much cleaner and more direct to just store the data in a table structure. Likewise, doing this changeover + some well needed optimizations yielded something like a 98% decrease in CPU load with _G loaded into the window and actively scrolling through the window. Also, we now free up memory immediately when we clear the workview, which keeps the addon from ballooning out of control. The most I can hit now is about 25MB when loading _G, wheras before I could easily get into the hundreds of MB if I had repeat opening and closings.
So good new all around. It will be easier to maintain going forward, as we have way less custom code now. And we have massive CPU and memory improvements.

So I'm making good headway on this!
I had only meant to start rebranding to a the new name of "DevTool" which I've been toying with, but I ended up going on a performance and stability sprint. The original version of this addon used a bespoke linked list data model for storing the active data in the main window, and unfortunately it was pretty fragile and did not scale well into the tens of thousands of nodes, such as when you are viewing _G. I tried fixing the linked list model, but it ended up being much cleaner and more direct to just store the data in a table structure. Likewise, doing this changeover + some well needed optimizations yielded something like a 98% decrease in CPU load with _G loaded while actively scrolling up and down the window. Also, we now free up memory immediately when we clear the workview, which keeps the addon from ballooning out of control. The most I can hit now is about 25MB when loading _G, wheras before I could easily get into the hundreds of MB if I had repeat opening and closings.
So good new all around. It will be easier to maintain going forward, as we have way less custom code now. And we have massive CPU and memory improvements.

Is the new table approach going to lead to key collisions? I feel one of the best ways I've used VDT was to dump a table, do something, then redump the same table to observe the changes. I haven't necessarily reviewed the changes much but figured I'd see if that was considered since it'd be cool to have both a more opimized tool but still retain the previous exellent debugging functionality.

If I coded it correctly, it shouldn't. DevTool interacts with and identifies the table based on the unique table hash id, so as long as no two tables have the same hash id it shouldn't be a problem. And I cannot think of a reason it should ever be the case that two tables end up with the same identifier.

Releases are minted and should be on their way to Curseforge and Wago. It might take a minute for Curseforge to approve it, assuming everything goes smoothly.


Bug: Svelte template reactivity issue

Bug report
Packages affected

[ ] sandpack-client
[x] sandpack-react

Description of the problem
I'm using sandpack-react. Using the svelte template with default settings, reactive variables update correctly, but they render to the DOM as undefined.
What were you doing when the problem occurred?
Using this basic component:
<script>
  let count = 0;
  const add = () => {
    count += 1
    console.log('Added:', count)
  }
</script>

<button on:click={add}>
  Count: {count}
</button>

What steps can we take to reproduce the problem?
Paste the code into /App.svelte into Sandpack in my sandbox. The button reads undefined after clicking, but count displays correctly in the console.

Link to sandbox: link
Your Environment

Software
Name/Version

Sandpack-react version
^0.9.13

Browser
Chrome, Firefox

Operating System
Windows

The same happens with a customSetup passed to SandpackProvider. Switching the dependency from svelte: '^3.0.0' to svelte: '^3.44.2' fixes the issue, even though Svelte v3.44.2 is loaded by the bundler in both instances. A bundler issue?
Sandbox demo

Hey @CTNicholas, thanks for raising this issue!
We've been working on a fix to address this issue in the main bundle repository.
Meanwhile, I hope this is not blocking you.

Hey @CTNicholas, thanks for raising this issue! We've been working on a fix to address this issue in the main bundle repository. Meanwhile, I hope this is not blocking you.

Awesome! All good, I love the package, keep it up guys!


ARUHA-1080: dummy commit to test approvals;

[ARUHA-XXX: Name of ticket](link to ticket)
Description
A few sentences describing the overall goals of the pull request's
commits.
Review

[ ] Tests
[ ] Documentation
[ ] CHANGELOG

Deployment Notes
These should highlight any db migrations, feature toggles, etc.

👍

👍


init new project-page | Support new api features

closes #93
Had to update the project page to support the new API changes for filtering projects.
Also tried out some animation with layout-hints before loading.

Deployed to https://web-vsm-dev.radix.equinor.com/


Feature Request: allow arbitrary commands when starting up

first of all: thanks for the tool, it's already very useful.
as an improvement, I suggest to allow executing arbitrary command when wabash starts the initial bash session. in my case, I need a sudo mount -a to mount some shares defined in /etc/fstab

Hm. I'd prefer not to add extra complexity for any features that are already covered on the Linux side -- is there any reason you couldn't add this as a service configuration in /etc/init (similar to /etc/init/binfmt-support.conf, say), and then start it using the existing service support in wabash? Since wabashd is acting as fake-init to start these services, this seems to be the most Linuxy way of getting what you want.

I understand your reasoning, but I hoped to not having to specify artificial services just to run simple one-off commands :)
the mount --all command for example would have to become /etc/init.d/mount-fstab to be usable in wabashd:
#! /bin/sh
### BEGIN INIT INFO
# Provides:          mount-fstab
# Required-Start:    $local_fs $remote_fs
# Required-Stop:     $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:
# Short-Description: Mount fstab mounts
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
NAME=mount-fstab
DESC="mount fstab mounts"

if [ "$(uname)" != Linux ]; then
  exit 0
fi

. /lib/lsb/init-functions
[ -r /etc/default/rcS ] && . /etc/default/rcS

set -e
CODE=0

case "$1" in
  start|restart|reload)
    if init_is_upstart; then
      exit 1
    fi
    log_daemon_msg "Enabling $DESC" "$NAME"
    mount --all || CODE=$?
    log_end_msg $CODE
    exit $CODE
    ;;

  *)
    N=/etc/init.d/$NAME
    echo "Usage: $N {start|restart|reload}" >&2
    exit 1
    ;;
esac

exit 0

would you consider to instead adding an option to have wabash execute /etc/rc.local at the end of faking init, so that simple commands could be run?


Differentiate "allow-all" and "allow-none" in ssl_context:verify_subject_alt_name

"allow-all": No secure naming is checked.
"all-none": Secure naming is checked against an empty list of service accounts. So it always fails.
We need to verify whether Envoy supports the two cases through config. Ideally, an undefined verify_subject_alt_name field should mean "allow-all" and a defined but empty verify_subject_alt_name field should mean "allow-none".

This should be addressed by lyft/envoy#615

lyft/envoy#648 fixes this issue in Envoy upstream

Please note that https://github.com/lyft/envoy/issues/648 was reverted in Envoy (see: https://github.com/lyft/envoy/issues/615, https://github.com/lyft/envoy/pull/668).

@lookuptable , is this issue solved? I think currently we enforce client cert now.


Display annotation for iOS

Thanks Phil, I've addressed your comments. Ready for another review.

Hi @saratchandrakarumuri please review!


chore: updated deprecated use of antd Progress

Most of the details in the PR template didn't seem relevant for such a simple change, so I omitted them. Let me know if I should add something.
I also did not run the tests. The last time I tried that when attempting to make a PR for another issue, I got loads of TypeScript errors despite not having changed a single file, so this time I felt discouraged to try and felt I might never get around to submitting the PR otherwise.
Closing issues
Closes #5205
Self Check before Merge
Please check all items below before review.

[x] Corresponding issues are created/updated or not needed
[x] Docs are updated/provided or not needed
[x] Examples are updated/provided or not needed
[x] TypeScript definitions are updated/provided or not needed
[x] Tests are updated/provided or not needed
[x] Changesets are provided or not needed

Ah, I was hoping the tweak commit will be squashed into the original and won't need a properly formatted commit message.
Should I also use "chore:" as the prefix for that and force push to replace the commit?

Ah, I was hoping the tweak commit will be squashed into the original and won't need a properly formatted commit message.
Should I also use "chore:" as the prefix for that and force push to replace the commit?

Yes, you can use 'chore' and 'force push' ⚡

Done

I only changed the attribute. All other changes were applied by some automatic formatter, which I assumed you have configured on this project.
I used Github Codespaces for this PR.

I tried to manually revert the changes and commit that, but got this error:
> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -

><EMAIL_ADDRESS>lint:staged
> lint-staged

[STARTED] Preparing...
[SUCCESS] Preparing...
[STARTED] Running tasks...
[STARTED] Running tasks for *.{js,jsx,ts,tsx}
[STARTED] eslint -c ./.eslintrc --quiet --fix --cache
[SUCCESS] eslint -c ./.eslintrc --quiet --fix --cache
[SUCCESS] Running tasks for *.{js,jsx,ts,tsx}
[SUCCESS] Running tasks...
[STARTED] Applying modifications...
[FAILED] Prevented an empty git commit!
[STARTED] Reverting to original state because of errors...
[SUCCESS] Reverting to original state because of errors...
[STARTED] Cleaning up...
[SUCCESS] Cleaning up...

  ⚠ lint-staged prevented an empty git commit.
  Use the --allow-empty option to continue, or check your task configuration

husky - pre-commit hook exited with code 1 (error)

Seems like husky runs eslint fix during commit, which applies the formatting changes back, resulting in an empty changeset.


Applicants should not be able to see what staff member is lead on their application

Currently when a user submits an application, they can see who the staff lead is. In other cases we obscure the staff members name and it probably also makes sense to do so here as it's PII.

to me the only people who really need this info would likely be staff

We already hide staff names in comments for applicants so apparently it is important for OTF staff to stay anonymous. This is a logical extension of that.
When we implement this I think we should add a setting HIDE_STAFF_IDENTITY or similar. I suggest it is false be default but OTF would set it to true. This would then hide staff identity in comments, lead and any other place we find.

We should also add a function so we do not need to do user.is_apply_staff or user.is_finance or user.is_contracting. Maybe def is_employed(self):?

We could at the same time add a def is_external(self):.
All groups should belong to one of these criteria.

yeah I totally agree, sounds like a nice solution! I can toss something up quick.

basically have everything figured out for the new config option and having the lead/comment names hidden based on that, but one thing I'm logically struggling with is the activity tab, as activities like this are shown:

with how we currently handle visibility it seems like filtering this activity based on the HIDE_STAFF_IDENTITY may add another level of activity visibility complexity. For now should we just make this activity team visibility only and when visibility refactoring happens in #3915 consider how to reincorporate it? Open to any alternative ideas too

I see no problem with making this staff only.


Add support for NOK in conversion

Is it possible to add support for conversion to NOK (Norwegian kroner) in a future release?

@searedvandal added NOK
Get the latest version using Go to get the update
go get -u github.com/miguelmota/cointop

Thanks!