Question about multivariate prediction of input data

Hi，my input data is image data compressed by a stack self-encoder, compressed as a vector of length 324, which is equivalent to 324 variables to be predicted, is such compressed data suitable to be used with the PatchTST model, and if I want to predict the future year's data (4380 in total), is it possible to run the predict function individually after completing the training and write each prediction at the end of the data file, and then run the predict function again individually?

Hi, as long as the input data is a multivariate time series (or sequential data), and you want to use a L look-back window to forecast the future T steps (which means the input shape is [M, L] and output shape is [M, T]), you can use PatchTST to do it.

Hi, as long as the input data is a multivariate time series (or sequential data), and you want to use a L look-back window to forecast the future T steps (which means the input shape is [M, L] and output shape is [M, T]), you can use PatchTST to do it.

Thank you very much for your answer, I still have questions. If tuning is required, which parameters will have a large impact on the model and what should their corresponding ranges be, and if the separation of patches is to be achieved, do I need to set both the INDIVIDUAL and DECROSION parameters to TRUE?

Hi,
Thanks for the question. We do ablation on hyperparameters in the appendix. INDIVIDUAL is the idea from DLinear paper and you can set it as False in default. Sorry I haven't found DECROSION.

It's the parameters DECOMPOSITION, sorry for wrong typing

This is also the same as DLinear repo: https://github.com/cure-lab/LTSF-Linear

Thank you very much, I have another question, most of my data ranges from magnitude tens to positive tens in feature Thank you very much, I have two more questions, my data in the feature dimension of most of the range for the amplitude of tens to positive tens, is it necessarily need to regularize the data, the second question for the data is now the number of features of 324, if I reduce the number of features, will it help to improve the prediction accuracy?


(QENG-3489) Add Ubuntu 16.04 to beaker host generator data.

This PR also

fixes some test fixture borkage that resulted from the Cisco platform renames
adds new test fixtures (it's not clear why these weren't in place previously)

@melissa @tvpartytonight this is ready for review.

:+1: looks good to me!

Is there anything blocking this being merged? And once it's in, does that mean we need a new release of this project?

@melissa ideally we would have two reviews, but please feel free to merge when you are ready.
And yes, we will need a new release for it to be usable--we have a jenkins job that does this.

Seems legit to me - although I dislike having the cisco stuff combined with ubuntu.  Can @LuvCurves give a thumbs up on the cisco bits?

@shermdog the cisco stuff is a fix for test fixtures that would have otherwise caused PR tests to be red...I'm not sure why/how we missed that when we renamed the cisco platform aliases a few weeks back.

This looks good to me; I second @waynr's comments about the cisco bits. 👍


Very large dataset

I ran xgboost on a large regression dataset.
feature number: 124
instance number: 31M
train file size: 33G
And I got the error:
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
Is this because of the large size of training data?
Any solution?
Thanks

@tqchen Link provided by you above doesn't work anymore. Would you please refresh the link or else provide some verbal directive on what to search for?

these are already merged to main brach

see https://xgboost.readthedocs.org/en/latest/tutorial/aws_yarn.html


Dynamic ref convolution op

Info

Make the reference implementation of Convolution work with dynamic shapes

dynamic input tensor and weights

Depends on #1199 and #1249 and #1295
Disables some reference compiler passes when shape is dynamic
Runs compute_shape() during eval() when the instruction has a dynamic output shape
Runs compute_shape() in the ref_convolution compute() function if the instruction shape is dynamic
Dynamic auto_pad calculation implemented

Issues/TODO

ONNX parser handle unknown shape to dynamic shape (implemented)
auto_pad ONNX option will need to be recomputed at evaluation time
Memoize the compute_shape() for multiple different sets of arguments? (not doing for now)
Allow setting padding/strides/dilation at evaluation? (Attributes will be set at compile-time)
Need to error out when kernel shape is incompatible, ex. kernel is larger than image (Not handled in original code)

Made some significant changes to support dynamic shape auto_pad. Should be ready for re-review now.


PyMySQL Package missing for MariaDB Database Connection

Home Assistant release with the issue:

0.100.2
Operating environment (HassOS/Generic):

Hass.io 64-bit on a RaspberryPi 3
Supervisor logs:

19-10-13 09:57:46 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-10-13 10:24:41 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.100.2
19-10-13 10:24:41 INFO (SyncWorker_5) [hassio.docker.interface] Update image homeassistant/raspberrypi3-64-homeassistant:0.100.1 to homeassistant/raspberrypi3-64-homeassistant:0.100.2
19-10-13 10:24:41 INFO (SyncWorker_5) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-64-homeassistant tag 0.100.2.
19-10-13 10:27:48 INFO (SyncWorker_5) [hassio.docker.interface] Stop homeassistant application
19-10-13 10:28:49 INFO (SyncWorker_5) [hassio.docker.interface] Clean homeassistant application
19-10-13 10:28:50 INFO (SyncWorker_8) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-64-homeassistant with version 0.100.2
19-10-13 10:29:51 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-10-13 10:32:41 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-10-13 10:32:51 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-10-13 10:34:27 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-10-13 10:34:32 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-10-13 10:35:32 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-10-13 10:35:42 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-10-13 10:35:42 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.100.2
19-10-13 10:35:42 INFO (SyncWorker_6) [hassio.docker.interface] Cleanup images: ['homeassistant/raspberrypi3-64-homeassistant:0.100.1']
19-10-13 10:37:46 INFO (MainThread) [hassio.host.info] Update local host information
19-10-13 10:37:46 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-10-13 10:37:46 INFO (MainThread) [hassio.host.services] Update service information
19-10-13 10:37:46 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-10-13 10:37:47 INFO (MainThread) [hassio.host.network] Update local network DNS information
19-10-13 10:37:47 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
19-10-13 10:37:56 INFO (SyncWorker_5) [hassio.docker.interface] Restart homeassistant/raspberrypi3-64-homeassistant
19-10-13 10:39:15 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance

Description of problem:
When setting up the recorder to use an external MariaDB database as per documentation with the below connection url:
mysql+pymysql://user:password@SERVER_IP:PORT/DB_NAME?charset=utf8
Home Assistant fails to connect to the database because it cannot initiate pymysql.
When checking for the package with the below command, it’s noted that the package is already installed:
pip3 install pymysql
However, if you install the package PyMySQL, the integration works correctly:
pip3 install PyMySQL
Problem is that because the package is not included in the image, I need to install it each time HomeAssistant has an update.

We use the C implementation. Look into documentation of the add-on

I was following the HomeAssistant documentation.
So if the documentation is incorrect, then fine, but then that should be fixed.

Similar issue. Not sure where to turn. Documentation doesn't say anything about setting up the Recorder component to use MariaDB on an external server with hassio. Assumes you have access to the same python env as homeassistant.


Github tag style

Feature Description
Recently, the tag style for Yosys changed from yosys-0.44 to 0.45. Is this the new style going forward, or is this a typo? In either case, please strive for a consistent tag style between yosys, sby, mcy, and eqy.

#4578

For the record, I would have personally preferred vX.Y rather than X.Y because the former allows listing all tags with git tag v* and the latter requires you to do the far more error prone git tag '*.*'. (There is no way to write a glob pattern matching a variable digit amount number.)

ReadtheDocs supposedly follows PEP440, which does allow for the preceding v character, although I'm not sure how exactly that fits with the existing docs versioning.  I was actually under the impression that the plan was to tag releases with both the yosys-0.xx style and the 0.xx for docs.

although I'm not sure how exactly that fits with the existing docs versioning.

It strips the v prefix.

Perfect.  I'm pro v prefix then

This should now be the case as of v0.48.  Note also the v prefix.

Yep, I realized already yesterday with a failing build. :-) At least now Yosys and EQY/etc. are harmonized 👍


+[UIImage circleBrushTexture]: unrecognized selector sent to class 0x106d7aa50 using Swift?

Sorry for buggin'!
I'm having trouble, perhaps it's on my part, but i get the unrecognized selector error. I'm using Swift to implement JotUI and the following function is the culprit:

(JotSharedBrushTexture*)brushTexture {
JotGLContext* currContext = (JotGLContext*)[JotGLContext currentContext];
(... yada yada yada ....)
JotSharedBrushTexture* texture = [currContext.contextProperties objectForKey:@"brushTexture"];
if (!texture) {
// ######## PROBLEM ########
NSLog(@"Creating a texture");
texture = [[JotSharedBrushTexture alloc] initWithImage:[UIImage circleBrushTexture]];
NSLog(@"After creating texture"); // doesn't log from here.
// ########################
[currContext.contextProperties setObject:texture forKey:@"brushTexture"];
}
return texture;
}

Could this be because I'm just using Swift and this on my part?

[UIImage circleBrushTexture] is defined in UIImage+BrushTextures.h/m. I suspect you just need to translate those files to Swift as well, and then it'll work fine :)
Very interested to hear how the Swift port goes! Keep me updated for sure, that'll be awesome when it's done

Oh ha! I probably misread your comment that you were translating into swift, not umpiring into your swift project! My only excuse is that it's very late at night and shouldn't be replying to things... :)
Another thought- look at the other linker flags in build settings and make sure they have the -ObjC -all_load. Check the included sample project- I may need to update the readme about that.

Ok - I double checked and i'd missed adding that to the readme, so just pushed an update for that - thanks for posting about the issue :). It also seems that only -ObjC is needed, not the -all_load, at least for the included sample project, so give that a try first.


Forms Node on NodeRed Dashboard 2.0

Epic
No response
Description
I've been testing the new Dashboard 2.0 with the aim to replace the old dashboard version I have, as this has new features and more options.
The forms node allows you different kind of forms options, and by clicking submit the written data should be sent by the node. The problem comes once you have sent data, as I have tried to write new data and submit it but the node won't send any message by its output. The only way I have found to write the forms again, is reloading the dashboard window, but I don't think that's practical. I have tried this on a simple flow, by just adding the forms node and a debugger. I tested it with different types of forms and the result remains the same.
The flow JSON code I have used is the folllowing:
[
{
"id": "bbad80407c6d0bf2",
"type": "ui-form",
"z": "2f82b4f977637196",
"name": "",
"group": "7ee511c7f05c05ce",
"label": "Form",
"order": 0,
"width": 0,
"height": 0,
"options": [
{
"label": "Label 1",
"key": "User1",
"type": "checkbox",
"required": true,
"rows": null
},
{
"label": "Label 2",
"key": "User2",
"type": "multiline",
"required": true,
"rows": 3
}
],
"formValue": {
"User1": false,
"User2": ""
},
"payload": "",
"submit": "Send",
"cancel": "Clear",
"resetOnSubmit": true,
"topic": "topic",
"topicType": "msg",
"splitLayout": "",
"className": "",
"x": 310,
"y": 160,
"wires": [
[
"8e4abff523e4208d"
]
]
},
{
"id": "7ee511c7f05c05ce",
"type": "ui-group",
"name": "Test Group",
"page": "49ec4fbe10fdeda9",
"width": "6",
"height": "1",
"order": -1,
"disp": true
},
{
"id": "49ec4fbe10fdeda9",
"type": "ui-page",
"name": "Test Page",
"ui": "295ddb930f648f43",
"path": "/",
"layout": "grid",
"theme": "fec3f9ad375dc4f2",
"order": -1
},
{
"id": "295ddb930f648f43",
"type": "ui-base",
"name": "UI Test",
"path": "/dashboard"
},
{
"id": "fec3f9ad375dc4f2",
"type": "ui-theme",
"name": "Test Theme",
"colors": {
"surface": "#ffffff",
"primary": "#0094ce",
"bgPage": "#eeeeee",
"groupBg": "#ffffff",
"groupOutline": "#cccccc"
}
}
]
Which customers would this be availble to
All Users, (CE)
Acceptance Criteria

[ ] criteria 1
[ ] criteria 2
[ ] criteria 3
...

Have you provided an initial effort estimate for this issue?
I can not provide an initial effort estimate

Thanks @PaserVesPro just to clarify here

Add form to Flow
Deploy
Form doesn't transmit data when submitted, only after a browser refresh?

With #213 and #170 closed out, and re-checking this myself, this issue has been resolved.


Using ASP.Net MVC layout landing fails protractor

Hi Guys,
I am working on MVC with AngularJS project where my landing page is usual mvc layout.cshtml page where I am loading angular and other js and css file using mvc bundle. When I am running my test I keep getting error angular is not defined.
This is my config file
exports.config = {
    seleniumAddress: 'http://localhost:4444/wd/hub',
    specs: ['./clientRecord/maintainclient.spec.js'],
    framework: 'jasmine2',
    onPrepare: function () {
        browser.driver.manage().window().setPosition(0, 0);
        browser.driver.manage().window().setSize(1280, 720);
    }
}

With very basic test
describe('Event List Details: ', function () {
    describe('When clicking on an event', function () {
        var name;
        beforeEach(function () {

        });
        it('Should navigate to the details page', function () {
            browser.ignoreSynchronization = true;
            browser.get('http://localhost:14529/');
            browser.waitForAngular();
            browser.sleep(5000);
            var header = element(by.binding('vm.Title'));// browser.driver.findElement(By.id('vmTitle'));
            expect(header.getText()).toMatch("Maintain Client nnnn");
        });
    });
});

Ignore my question the issue was that I was running it in IIS Express. When I moved my website to actual IIS I got it working


video_stream_opencv: 1.1.2-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository video_stream_opencv to 1.1.2-1:

upstream repository: https://github.com/ros-drivers/video_stream_opencv.git
release repository: https://github.com/ros-drivers/video_stream_opencv-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.4
previous version for package: null

video_stream_opencv
* Fix empty frame id in camera info header when providing a calibration file.
* Contributors: tim-fan

Holding for melodic sync...

@clalancette sure, thank you for informing!


dex: upgrade to v2.36.0

The version of dex in pachyderm/dex is v2.36.0 with only one of our changes; the localhost issuer -supporting stuff.  The rest of the stuff in there was only for hub and was becoming a bit of a burden, so it's removed.  For that reason, I think this will be a 2.7-targeting change, so there is plenty of burn time.
We also had to upgrade a lot of modules; we will see what that breaks.

Nice upgrade! Does this live on a branch in pachyderm/dex?

Also, I haven't been able to totally confirm this, but I'm pretty sure we can eliminate insecureSkipIssuerCallbackDomainCheck with the move to proxy everywhere.
Minor nit: We should eliminate references to login_hint in the helm chart example configs if that's gone.

@chainlink I think we have to keep the insecureIssuerCallbackDomainCheck stuff... we pretty much always set the Issuer to http://pachd:30658/ because console reads that and uses it to make requests to pachd; if it's proxy.host then that depends on a networking setup where the domain is accessible from inside the cluster, which is not always guaranteed (for example, if the proxy is behind a LoadBalancer that uses the PROXY protocol; and also when the issuer is "localhost"; console's view of "localhost" is different than the user's workstation's view of "localhost", so it won't be able to talk to the identity server in that case).  For that reason, I think we have to keep it; though we can get rid of it if we make console manually configure OIDC instead of having it auto-configure itself.  I sent them a change to do that a while back, but they and customer-eng preferred the "localhostIssuer" hacks.


fix(learn): Made Changes to Instructions in BFS/DFS exercise

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #38070

Added and moved around details in the instructions of BFS and DFS exercise. Add description of the visual representation (animation) in the instructions for both exercises.

Were you two teaming up on this @anastasiasoenjoto @kylayujiri?

@moT01 Yes we were, is there something we can help you with?

Looks like one of the tests stalled out or something. Closing and opening to try and restart it.

@moT01 Yes we were, is there something we can help you with?

No, I was just curious.


Fix sort order on ProfileBarChart date tooltips

Who is this PR for?
educators, came up working on https://github.com/studentinsights/studentinsights/issues/1657
What problem does this PR fix?
On hover, dates for absences are in reverse order, recent to oldest.  This sort of makes sense in a "what happened most recently sense" but not in what you'd expect just reading a chart.
What does this PR do?
Sorts oldest - recent.
Screenshot (if adding a client-side feature)
before

after

selfie


How to throw errors that won't get transformed to ServerError?

Motivation
Is there anyway I can throw errors without being converted to an ServerError in Vapor project? What's the easiest way to do it for every APIProtocol function?
I want to use this library to generate code, but it limits how I throw errors, it's frustrating
Proposed solution
Maybe put the conversion to ServerError and ClientError to a middleware and give users the choice whether to use it?
Alternatives considered
No response
Additional information
No response

Hi @cantbetrue,
throwing a ServerError is part of the API contract, providing context that's important for debugging.
If you want to get access to the original underlying error, for example thrown in your handler, use the underlyingError property.
Does that address your issue?

So in a scenario like this, how can I  throw ValidationsError directly?
struct API: APIProtocol {
    func register(_ input: Operations.register.Input) async throws -> Operations.register.Output {
        try Components.Schemas.RegisterInput.validate(content: request)
        ...
     }
 }

ValidationsError is defined in Vapor.
Anyway, I added your ErrorMappingMiddleware() code, called it like this:
    let myMiddlewares = [ErrorMappingMiddleware()]
    let transport = VaporTransport(routesBuilder: app)

    try API().registerHandlers(on: transport, serverURL: Servers.server1(), middlewares: myMiddlewares)

But still errors in that function was thrown as ServerError, I get status code 500 and this as the response:
{
    "error": true,
    "reason": "Server error - cause description: 'Middleware of type 'ErrorMappingMiddleware' threw an error.', underlying error: The operation couldn’t be completed. (Vapor.ValidationsError error 1.), operationID: ..."
}

Even if the APIProtocol's function is changed to:
func register(_ input: Operations.register.Input) async throws -> Operations.register.Output {
        throw Abort(.badRequest, reason: "arbitrary test")
 }

Still get back 500 status code and all the "Additional info" in error description.
I tried to extend ServerError and define description myself to make it to my liking but it didn't work, the one defined in the swift-openapi-runtime always take precedence.
Before, in vanilla Vapor, I can easily throw an error as a failed response, with the customized status code and purely cusomizable description, now adding openapi generator makes all that harder.

Can you provide the implementation of the middleware? How are you transforming the errors? That's what affects the responses you're seeing.

I pasted in the above ErrorMappingMiddleware without changing anything, then in entrypoint.swift file
import Vapor
import Logging
import OpenAPIVapor

@main
enum Entrypoint {
    static func main() async throws {
        var env = try Environment.detect()

        try configLogger(env: &env)

        let app = Application(env)
        let transport = VaporTransport(routesBuilder: app)

        try API().registerHandlers(on: transport, serverURL: Servers.server1(), middlewares: [ErrorMappingMiddleware()])
        defer { app.shutdown() }

        do {
            try await configure(app)
        } catch {
            app.logger.report(error: error)
            throw error
        }
        try await app.execute()
    }
}

Then in the API() struct, the function does nothing but throw an AbortError defined by Vapor https://docs.vapor.codes/basics/errors/?h=abort#abort-error.
func register(_ input: Operations.register.Input) async throws -> Operations.register.Output {
        throw Abort(.badRequest, reason: "test")
}

And the response:

In the snippet I provided, see the lines // here turn the error into... - those are the lines where you need to transform your errors into whatever you want them to be 🙂 It was meant to be a snippet that you modify.

@cantbetrue Actually, I just played with this a bit more and realized that while the middleware unwraps the handler's ServerError, the rethrown error gets wrapped again as "middleware threw an error" (because only ServerErrors are passed up without being wrapped).
What this means is that to achieve what you want, you'll need to turn the ErrorMappingMiddleware from being an OpenAPIRuntime.ServerMiddleware into a Vapor middleware. That will be called after both the handler and all ServerMiddlewares have been run, and Vapor shouldn't wrap it again - so that's where you can do the final customization before being turned into an HTTP response.

Ok, confirmed that this does what you want:
import OpenAPIRuntime
import OpenAPIVapor
import Vapor

struct Handler: APIProtocol {
    func getGreeting(_ input: Operations.getGreeting.Input) async throws -> Operations.getGreeting.Output {
        throw Abort(.badRequest, reason: "arbitrary test")
    }
}

struct ErrorMappingMiddleware: AsyncMiddleware {
    func respond(to request: Request, chainingTo next: any AsyncResponder) async throws -> Response {
        do {
            return try await next.respond(to: request)
        } catch {
            if let error = error as? ServerError {
                let transformedError = error.underlyingError // here turn the error you threw in your handler into another error
                throw transformedError
            } else {
                let transformedError = error // here turn other errors into your transformed errors
                throw transformedError
            }
        }
    }
}

@main struct HelloWorldVaporServer {
    static func main() async throws {
        let app = Vapor.Application()
        app.middleware.use(ErrorMappingMiddleware())
        let transport = VaporTransport(routesBuilder: app)
        let handler = Handler()
        try handler.registerHandlers(on: transport, serverURL: URL(string: "/api")!)
        try await app.execute()
    }
}

Closing as we seem to have found a way to address the ask. Please reopen if you believe this should be handled by Swift OpenAPI Generator.


Avoid invoking 'runNow' multiple times.

Codecov Report

Merging #125 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
+ Coverage   92.22%   92.23%   +0.01%
==========================================
  Files          11       11
  Lines        1286     1288       +2
  Branches      259      259
==========================================
+ Hits         1186     1188       +2
  Misses        100      100

Impacted Files
Coverage Δ

lib/bundling.js
95.3% <100%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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


Project Proposal: Super Smash Bros

This project would revolve around the game Super Smash Bros. I'm a big fan and I've been playing this game since it was on the Nintendo 64. I'm sure there are other fans as well. This project would analyze the different versions of the game and how it has evolved over the years. Most of all I want to analyze all of the characters on Super Smash. Each version gets new characters and I want to see how they are all different/similar to each other. We could even look into the tiers of characters. I'm very open to suggestions. I think there is a lot we can do and I would be very eager to make a project about Super Smash Bros.

Hey Barbie! I'm a super big Smash fan too, I'd be super down to work on this since I know a lot about the series and I'm interested in it too!

I really like this idea as well Barbie! I am a huge fan of the Super Smash games as well and I have grown up playing them too since the Nintendo 64. I think it would be cool to make some sort of a timeline of when the games released and you can even go as far as to add the consoles to that line up as well. Then for new characters, some were added to thee games over time (more with Smash Ultimate now with the fighter passes), but it would be cool to make an interactive timeline that has the characters released as well. A graph can be made of the characters that appear across all of the titles so you can check for consistency there as well. Overall I would love to be apart of this project if my project isn't as widely liked and accepted!

I think including a section that reviews character buffs/nerfs throughout the games would be interesting too, as there were balancing changes even between games for a lot of characters. Also, showing notable competitive players for each character could add do the project.

This sounds like such a fun project idea Barbie! I love Super Smash Bros, and there are so many intricacies to the game and all of the different versions that have come out over the years that there's a plethora of opportunity for cool data research and visualizations to be done to highlight the awesomeness of the game. I think it would be cool to develop a timeline of the different platforms SSB has been released on over the years, the elements of the game that have been improved as time has progressed, and the characters that have been added. This is a project I could see myself working on for sure.

This sounds like a really interesting Project Proposal Barbie. I think adding a section about special moves would be an interesting addition. I am very interested in the possibility of joining this project.

Nothing wrong with smash that's for sure, I could see myself doing this project, I enjoy the variety in information we could categorize, especially with the expansive ultimate roster.

@BarbieCessar or others here: An issue: How do you deal with the game franchise and its own resources? What would your project do differently than what is already available on the Nintendo site: https://www.smashbros.com/en_AU/fighter/index.html  ?

if your are doing smash bros I would recommend talking about the different mini games and trophies you can get in the different game. for example in the 3ds version you could customize your characters with different upgrades, and even make a mii a fighter.

Its a good idea, I also really enjoy smash brothers. I've been playing that ever since it first came out. I know that you would want to analyze all of the characters of the game but how would you handle the characters like the miis where the player can completely change the way they are played and look. And also there are characters that are physically different selections but have the exact same move set. Would they both get a entre or would they be combined somehow.

Think this would be quite a fascinating project idea, especially for the game fanatics! There is a lot of different ways you could go with this project in terms of comparisons. I think you have the right idea in wanting to compare and contrast the different characters from game to game. Since there happens to be a number of recreations of this game you will have a good opportunity to collect your data. You could maybe even compare and contrast the design of the characters/maps in each of the games


refactor(postgres-cdc): refactor postgres_row_to_owned_row

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Try refactoring to resolve https://github.com/risingwavelabs/risingwave/pull/16416#discussion_r1597542366
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[x] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[x] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

An undecided issue: for codes like this:
let mut builder = dtype.create_array_builder(0);
if let Some(v) = val {
    v.into_iter().for_each(|val| {
        builder.append(
            val.map(|v| ScalarImpl::from(v.into_boxed_slice())),
        )
    });
}
Some(ScalarImpl::from(ListValue::new(builder.finish())))

This means when there's error parsing the pg rows, we will return {} instead of NULL. But in Debezium's json parser, we directly fallback it toNULL by returnint the err. Should we update this part to following codes?
if let Some(v) = val {
    let mut builder = dtype.create_array_builder(0);
    v.into_iter().for_each(|val| {
        builder.append(
            val.map(|v| ScalarImpl::from(v.into_boxed_slice())),
        )
    });
    Some(ScalarImpl::from(ListValue::new(builder.finish())))
} else {
    None
}

Before this PR, NULL::TYPE[] is not well handled, it will be parsed as {} instead of NULL. The bug is due to the following style of codes.
let mut builder = dtype.create_array_builder(0);
// do something
if let Some(v) = val {
    v.into_iter().for_each(|val| {
        builder.append(
            val.map(|v| ScalarImpl::from(v.into_boxed_slice())),
        )
    });
}
// do something
Some(ScalarImpl::from(ListValue::new(builder.finish())))

The correct way to handle NULL::TYPE[] is to check if the value is None before creating the array builder.
if let Some(v) = val {
    let mut builder = dtype.create_array_builder(0);
    v.into_iter().for_each(|val| {
        builder.append(
            val.map(|v| ScalarImpl::from(v.into_boxed_slice())),
        )
    });
    Some(ScalarImpl::from(ListValue::new(builder.finish())))
} else {
    None
}

An open question: Do you think we should also add UuidList(Vec<Option<uuid::Uuid>>) and EnumList(Vec<Option<EnumString>>)?

After refactoring, multi-dismension list should trivial to support. Will add it in next PR.
During refactoring, I find an interesting thing: while testing, I setup a postgres as data source and I run the test multiple times. The second round of test for the postgres will usually fail but the first and following tests will succeed🤣. Will continue to investigate.

After refactoring, multi-dismension list should trivial to support. Will add it in next PR.

https://docs.rs/postgres-types/latest/postgres_types/trait.FromSql.html#arrays
https://docs.rs/postgres-types/latest/postgres_types/trait.ToSql.html#arrays

FromSql is implemented for Vec<T>, Box<[T]> and [T; N] where T implements FromSql, and corresponds to one-dimensional Postgres arrays.
ToSql is implemented for [u8; N], Vec<T>, &[T], Box<[T]> and [T; N] where T implements ToSql and N is const usize, and corresponds to one-dimensional Postgres arrays with an index offset of 1.

Related: https://github.com/risingwavelabs/risingwave/issues/3811#issuecomment-1556656529 #15614

During this refactoring, I also found three another bugs of Debezium CDC.
https://github.com/risingwavelabs/risingwave/issues/16895
Early timestamp is not handled correctly, so I have to use a timestamp close to now to avoid this error.
https://github.com/risingwavelabs/risingwave/issues/16880
When enum in PG is recreated (delete and create with the same name), the type registry won't keep up with upstream so that Debezium cannot handle the enum correctly, so that lead to a NULL for this enum in debezium message. I have no solution to resolve, so temporarily didn't add test for this.
https://github.com/risingwavelabs/risingwave/issues/16882
INTERVAL_ARRAY is not supported. Resolved by not allowing INTERVAL_ARRAY's into_scalar
BTW, besides these three, I suspect Debezium may not support "inf/-inf/nan" for some types. Will check later.

Spend more time on fixing debezium.

Agree. I've noted down the bugs found as issues. But they may not be urgent, will fix when requested.

IIRC there is dark magic in java class loader to replace a certain library class without forking the project

Should be ClassLoader.


Add in google analytics

Ensure we have code implemented across all pages.

Thanks Rich. It seems Bev has done this. I'm still not able to access any data, so just looking through my settings to figure out why.

FreeCen2 currently uses the analytics id 'UA-71283391-1'  If there is a new analytics id since that was set up, just let one of the developers know what the new id is and a developer can update it in application.html.erb  Or, could it be that the site has not yet been verified (see the other story regarding google site verification key)?

UA-89287207-1 is the code for freecen2.freecen.org.uk - to be implemented if it is not already, on all pages
(UA-71283391-1 is the code for www.freecen.org.uk)

@PatReynolds , could someone test this  code ?

It doesn't seem to be working (is it live on test2?)

@PatReynolds , @dougkdev  could you deploy it in test2?

Has this been deployed in test2? If so, the code doesn't appear to be working. Added Mike (our analytics volunteer) to contribute

Just in case you need the universal google analytics tracking code. Google specifies that in order to get the full benefit of that we need to implement it on every page of the site:

Is it not working or it was not deployed?!

@dougkdev can you confirm if deployed?

It is not deployed.  @Vino-S will you merge/test/deploy Israel's pull request?  @israelriibeiro , Vino is a full-time developer, whereas I have been mostly phased out of the projects. Going forward it is better to ask her instead of me in order to get a more a timely response, thanks.

To add into every page (currently it's only on search page). To also check/test real time analytics as unsure if this is working or not.

Just a heads up. Google Analytics is not installed yet.

I have made few changes in code and deployed it in test2.  Could someone test it and let me know whether it is working?

@dougkdev to deploy/roll-out (which should fix it).

Working fine.


Not able to import RestBuilder

Hello,
We are using Grails 2.4.5 and are trying to use the RestBuilder class to implement some functional tests for our REST API's.
I have included compile "org.grails.plugins:rest-client-builder:2.1.1" in the BuildConfig.groovy file.
I can see that the plugin is downloaded but do not see the RestBuilder class in any src directory. I also do not see any references to other dependencies that might include RestBuilder.

Could this be an issue when the plugin was upgraded/moved for Grails 3.x?
Thanks,
Kathy

For questions please try Slack (http://slack-signup.grails.org)  or StackOverflow (http://stackoverflow.com/tags/grails)


@each - invalid selector after

I just passed from an old version of grunt-sass to gulp-sass, and I immediatly get an error when trying to compile
$colors : (teal:#00A0B1, blue:#2E8DEF, sky-blue:#0A5BC4, dark-purple:#643EBF, purple:#A700AE, red:#bf1e34, orange:#DC572E, yellow:#E0BC2D, green:#00A600, grey:#A8A8A8)
@each $name, $color in $colors
    .#{$name}
        background-color: $color

Error:
      throw er; // Unhandled 'error' event
            ^
Error: public/styles/tools.sass
  11:202  invalid selector after
    at options.error (.../node_modules/gulp-sass/node_modules/node-sass/lib/index.js:276:32)

I tried removing the . in .#{$name}  and replaced it in the variable like #{'.' + $name} or other things but nothing worked.
Am I missing something or is it a bug ?

Ruby Sass says:
Error: Invalid CSS after "..., grey:#A8A8A8)": expected selector or at-rule, was "@each $name, $c..."
        on line 2 of 1069.test.scss
  Use --trace for backtrace.

It works if you give the file name .sass extension or tell node-sass to use indented syntax:
~/node_modules/node-sass/bin/node-sass 1069.test.sass
.teal {
  background-color: #00A0B1; }

.blue {
  background-color: #2E8DEF; }

.sky-blue {
  background-color: #0A5BC4; }

.dark-purple {
  background-color: #643EBF; }

.purple {
  background-color: #A700AE; }

.red {
  background-color: #bf1e34; }

.orange {
  background-color: #DC572E; }

.yellow {
  background-color: #E0BC2D; }

.green {
  background-color: #00A600; }

.grey {
  background-color: #A8A8A8; }

Ruby gives some warnings at the top:
WARNING on line 4, column 6 of 1069.test.sass:
You probably don't mean to use the color value `teal' in interpolation here.
It may end up represented as #008080, which will likely produce invalid CSS.
Always quote color names when using them as strings (for example, "teal").
If you really want to use the color value here, use `"" + $name'.

Well, I was using .pipe(sass({outputStyle: 'compressed'})) in gulp and it 's that that broke all the thing. After trying directly with node-sass, I got the same problem. With any other output-style I have no problem compiling this code.
So using --output-style compressed seems to broke with @each using the SASS syntax

Here's what I got with the current libsass master (wrapped a bit)
$  ~/node_modules/node-sass/bin/node-sass -i 1069.test.sass --output-style=compressed
.teal{background-color:#00A0B1}.blue{background-color:#2E8DEF}
.sky-blue{background-color:#0A5BC4}
.dark-purple{background-color:#643EBF}.purple{background-color:#A700AE}
.red{background-color:#bf1e34}.orange{background-color:#DC572E}
.green{background-color:#00A600}.grey{background-color:#A8A8A8}

Within tools.sass I have:
$colors : (teal:#00A0B1, blue:#2E8DEF, sky-blue:#0A5BC4, dark-purple:#643EBF, purple:#A700AE, red:#bf1e34, orange:#DC572E, yellow:#E0BC2D, green:#00A600, grey:#A8A8A8)
@each $name, $color in $colors
    .#{$name}
        background-color: $color

node-sass -i tools.sass --output-style=compressed
{
  "message": "invalid selector after ",
  "column": 33,
  "line": 2,
  "file": "/home/mborges/git/processus/src/public/styles/tools.sass",
  "status": 1
}

node-sass --version
node-sass	3.2.0	(Wrapper)	[JavaScript]
libsass  	3.2.5	(Sass Compiler)	[C/C++]

node-sass --version
node-sass	3.2.0	(Wrapper)	[JavaScript]
libsass  	3.2.5	(Sass Compiler)	[C/C++]

Mine:
$ ~/node_modules/node-sass/bin/node-sass --version
node-sass   3.2.0   (Wrapper)   [JavaScript]
libsass     3.2.5-172-g1ebed-dirty  (Sass Compiler) [C/C++]

So it seems it got fixed in the yet-unreleased libsass code.

I can confirm this issue is present in LibSass 3.2.5 is compressed output mode. It appears to be resolved on master. We'll get this fix when the next version of LibSass is released.

Fixed in https://github.com/sass/node-sass/pull/1214. Will be in v3.4.0.


Difficulty Accessing Private GitHub Repo with IDF Component Manager in CI Pipeline (RDT-637)

Hello,
I'm encountering an issue with espressif/esp-idf-ci-action@v1 while trying to build a project in my CI pipeline. The project uses the IDF Component Manager to fetch a component from a private GitHub repository.
Despite several attempts, I'm unable to grant access to the private repository for the IDF Component Manager running on GitHub. I've tried methods similar to those discussed in this forum post, including using ssh-agent and configuring known_hosts, but to no avail.
Could you please clarify:

Is espressif/esp-idf-ci-action designed to support accessing private repositories through the IDF Component Manager using idf_component.yml?## IDF Component Manager Manifest File
dependencies:
  espressif/button: "^2.5.0"
  ## Required IDF version
  idf:
    version: ">=4.1.0"

  # For components in git repository:
  esp_arithmetic:
    path: "./component_add"
    version: "*"
    git: "git@github.com:kaspernyhus/multi_component_test.git"

If supported, could you provide guidance or examples on how to configure this correctly?

Hello @hayschan and thank you for raising the topic.
Access to private repositories wasn't in our scope yet. At the same time, we can make it work.
The flow is different for SSH based repository access and over HTTPS. Is it crucial for you to use SSH access, or can you switch to HTTPS?
In this case, we can support passing of arbitrary environment variables, that can be used for authentication.

As long as the IDF component manager can access private GitHub Repo, I am fine with any solution.
Another workaround might be having private component on the ESP registry. These component can be grabbed from the ESP registry, but not available to public unless the user have a special authentication. The authentication can be password, or a pair of private and public key.

@hayschan I apologize, didn't notice your response.
To access a private repo through HTTPs you can use environment variables in the manifest for credentials https://docs.espressif.com/projects/idf-component-manager/en/latest/reference/manifest_file.html#environment-variables-in-manifest
And #43 adds a way to pass custom arguments, including environment variables.

@hayschan Now (in v1.2.0 of this action) it's possible to pass an env variable with credentials and use environment variables in the manifest.
I would like to close this issue, if you have any ideas, or it doesn't work in your case, feel free to reopen it.


Fix Deprecation warnings on test PyPi workflow

https://github.com/pymc-labs/pymc-marketing/actions/runs/4628916188
Seems like some _ underscores have to be replaced by - dashes

I'll take it


Fully immutable spancontexts

Makes all span contexts fully immutable, and converts to a builder pattern for creating them during parsing.

@dotnet/razor-compiler for review please.


Add libsodium dependency installation to readme

There are libsodium installation instructions on this page.
Have you looked at those?

I've seen the instructions too. The libsodium dependency being used is the fork of a fork of the original, and it's behind in releases. If this crypto lib is truly required to run the cardano nodes, consider sponsoring the author(s) on Github and using the official lib version since it's apparently actively maintained. It leaves me in the dust, and I'm a big fan of ADA. Please clarify how the library is used in cardano and what can be done to switch to the original.

Usage in cardano-node:
# strings bin/cardano-node | grep ^sodium_ | sort -u
sodium_compare
sodium_fe25519_frombytes
sodium_fe25519_invert
sodium_fe25519_tobytes
sodium_free
sodium_ge25519_add
sodium_ge25519_double_scalarmult_vartime
sodium_ge25519_from_hash
sodium_ge25519_from_uniform
sodium_ge25519_frombytes
sodium_ge25519_frombytes_negate_vartime
sodium_ge25519_has_small_order
sodium_ge25519_is_canonical
sodium_ge25519_is_on_curve
sodium_ge25519_is_on_main_subgroup
sodium_ge25519_p1p1_to_p2
sodium_ge25519_p1p1_to_p3
sodium_ge25519_p3_to_cached
sodium_ge25519_p3_tobytes
sodium_ge25519_scalarmult
sodium_ge25519_scalarmult_base
sodium_ge25519_sub
sodium_ge25519_tobytes
sodium_init
sodium_is_zero
sodium_malloc
sodium_memzero
sodium_ristretto255_from_hash
sodium_ristretto255_frombytes
sodium_ristretto255_p3_tobytes
sodium_sc25519_invert
sodium_sc25519_is_canonical
sodium_sc25519_mul
sodium_sc25519_muladd
sodium_sc25519_reduce

Forum discussions on the same topic: "Why is not the origin libsodium library used when running a cardano-node?"
This algorand's fork of libsodium apparently provides VRF implementation but they are not used anywhere in cardano-node, are they? lddoutput does not find any use of these VRF functions. Finally, the CI workflows use a vanilla libsodium version:
$ grep sodium .github/workflows/haskell.yml
    - name: Install libsodium (Windows)
          https://download.libsodium.org/libsodium/releases/libsodium-1.0.18-mingw.tar.gz -o libsodium-1.0.18-mingw.tar.gz
        tar zxvf libsodium-1.0.18-mingw.tar.gz
        sed -i "s|/d/a/1/s/|D:/a/cardano-node/cardano-node/|g" libsodium-win64/lib/pkgconfig/libsodium.pc
        export PKG_CONFIG_PATH="$(readlink -f libsodium-win64/lib/pkgconfig)"
        export LIBSODIUM_PATH="$(readlink -f libsodium-win64/bin | sed 's|^/d|D:|g' | tr / '\\')"
    - name: Install libsodium (MacOS)
      run: brew install libsodium
    - name: Configure to use libsodium
          flags: -external-libsodium-vrf
        sudo apt-get -y install libsodium23 libsodium-dev

Can we conclude that users can simply install the original libsodium library and then we can update the documentation to include installation instructions below? If we do, I'm happy to submit a pull-request.
Install libsodium (Windows)

curl -Ls https://download.libsodium.org/libsodium/releases/libsodium-1.0.18-mingw.tar.gz -o libsodium-1.0.18-mingw.tar.gz
tar zxvf libsodium-1.0.18-mingw.tar.gz

Install libsodium (MacOS)

brew install libsodium

Install libsodium (Linux)

sudo apt-get -y install libsodium23 libsodium-dev

then we can update the documentation to include installation instructions below

Whet you use the VRF additions or not is your choice (IOG's strict recommendation is to not depend on system library), and controlled via addition of flag you see in CI, i.e. flags: -external-libsodium-vrf
Personally , I'd always trust testing from official Package Manager's libsodium instead of a fork, but the trace from documentation to use system libsodium for advanced users (only for testing) was removed. I doubt they'd like to put it back in 🙂

Can we conclude that users can simply install the original libsodium library

No , you cant use ldd / strings / grep for library name and conclude a submodule will not be used , but in this case, adding the above mentioned flag will cause node to not depend on fork

Closing this. If this is still relevant please reopen.


Always on Top does not play sound

Microsoft PowerToys version
v0.56.1
Running as admin

[X] Yes

Area(s) with issue?
Always on Top
Steps to reproduce

Enable Always On Top.
Enable "Play a sound when pinning a window" option.
Activate Always On Top on any window such as Windows Explorer or Microsoft Edge.

✔ Expected Behavior
A sound played after pinning window.
❌ Actual Behavior
Pinning occurs, but sound never played.
Other Software
No response

Same version works fine on a Dell Optiplex desktop computer. Bug occurs on a Dell Latitude 5400 laptop.

Hi Tim, sorry to hear something isn't working as expected. Just to be sure: There can be a number of places for sound settings, for example the Volume Mixer (sndvol.exe) - have you checked all of them?

I just did and you helped me solve the problem. Somehow, PowerToys.AlwaysOnTop.exe was muted. I unmuted and the sound plays now. Thank you Jay-o-Way!


Bugfix 3.4: Defensive code for recent lambda function in Communicator

handleResults() recently changed.  It now creates a lambda function for Scheduler to execute instead of performing the work in-line.  This code defends against the possibility (though not proven to exist) that the lambda function executes after the Communicator object is destroyed.

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/1831/


feat: icons support

https://user-images.githubusercontent.com/6196971/215571496-d678b9ef-d2ad-4b72-99a3-8675adaa55ec.mov

Awesome! What about adding this support via env LLAMA_ICONS=true instead on --icons?

I was thinking of adding a couple more flags in the future like:

--group-directories-first
--colo[u]r=WHEN    when to use terminal colours (always, auto, never)

These flags come from exa and are really useful for me.
If you like these additional flags, having an env variable will not scale IMHO.
wdyt?

I use the ll alias, so I can just pass there all the flags.
Other people can also add such flags under an alias.
If you prefer env variables I can do that but flags seems cleaner to me.

I use the ll alias so cd works, so I can just pass there all the flags.

Make sense.
Flags are okay :)

BTW, will you be able to generate gif the same way as in https://github.com/antonmedv/llama/tree/master/.github/images ? Using vhs.

Yeah vhs is awesome

Cool, so if you're good with the PR feel free to merge :)

Can you also generate the gif?

@antonmedv done!

Awesome thanks! Let’s also add this gif in examples in README with instructions on how to install icons.

Done :) Let me know if that's ok


Update stable version in repo from 3.0.7 to 3.1.0

Think about update stable version to 3.1.0
Version: stable=3.0.7 (118 days old) => latest=3.1.0 (15 days old)
Installs: stable=257 (50.2%), latest=52 (10.16%), total=512
Click to edit

done


github pr template directory restructure

Github introduced a new feature for work-in-progress PR, moving the existing PR template to it's own directory to enable that feature

@weshaggard merging this. The only way to find out if this will enable the feature is to actually merge this and find out.
Let me know if you see any issues.


Add zmqpp as third party dependency

The header only cpp wrapper for zeromq is not easily installed other than getting it from git. This PR provides a script to add it as subtree into third party dependencies.

Changes Unknown when pulling 46da17953ae431f49427ef917417951597fd0fe3 on build/dependency-script into ** on master**.

Changes Unknown when pulling 46da17953ae431f49427ef917417951597fd0fe3 on build/dependency-script into ** on master**.


[BUG] Flaky test: testProcessSpansWithoutDiagnosticId

https://dev.azure.com/azure-sdk/public/_build/results?buildId=1328428&view=ms.vss-test-web.build-test-results-tab&runId=28048024&resultId=105959&paneView=debug
tracer.end("success", isNull(), <any>);
Wanted 3 times:
-> at com.azure.messaging.eventhubs@5.11.0-beta.1/com.azure.messaging.eventhubs.EventProcessorClientTest.testProcessSpansWithoutDiagnosticId(EventProcessorClientTest.java:324)
But was 2 times:
-> at com.azure.core.amqp@2.4.0-beta.1/com.azure.core.amqp.implementation.TracerProvider.end(TracerProvider.java:134)
-> at com.azure.core.amqp@2.4.0-beta.1/com.azure.core.amqp.implementation.TracerProvider.end(TracerProvider.java:134)

@ZejiaJiang can you please take a look? I think it's one of the tests recently added in #26180

@ZejiaJiang can you please take a look? I think it's one of the tests recently added in #26180

OK, I'll take a look

@lmolkova I triggered java-eventhub-ci and java-core-ci of the main branch manually. And java-eventhub-ci of main branch is successful, java-core-ci is failed as well. I need sometime to review your code.

@ZejiaJiang sorry for not being clear - I didn't touch anything related to the test - it's something that reproduces on main - i.e. no need to review my code.

@lmolkova
Here is some updates. I'm not sure whether this case is a flaky test or not.
The test of eventhub-ci didn't fail.
The test of eventhub that triggered by core-ci fails all the time.
I'm trying to figure out what the difference betweent the test of eventhub-ci and the eventhub test that triggered by core-ci.

BTW, in the test log, it shows that the context start with EventHubs.process for 3 times and end with the status message success for 2 times. I'd like to ask what will cause the context don't end with the status message success. I'm not famliar with telemetry and have no idea what will cause the context end failed.


Adding Granularity Feature to Cleaner.py

As a user it is very common to want the granularity of a given data set. We need to implement this feature to find all possible primary keys.


FEAT Add positivity constraint for L1 and L21 penalties

It could be done either by using a PositiveL1 penalty (duplicates code but keeps L1 untouched) or adding a positive argument to L1 (that may confuse users that just care about a vanilla L1 penalty)

I'd opt for the positive option (principles of least surprise, close to sklearn + less code to maintain).


weird xml extraction

Example url:
https://www.dummies.com/article/home-auto-hobbies/home-improvement-appliances/electrical/how-to-replace-a-light-switch-185346/
Command:
trafilatura.extract(page_source, output_format='xml', include_comments=False)
Problem:
Output is not reading like a regular XML.

Yes, there is something wrong with the extraction here.

The main extractor is not impacted, readability_lxml extracts the wrong content, I will implement a quick fix.


Removing add_category function

Reasons for it's removal:

It is not used anywhere in the code base
It has a bug, it is not modifying the study_columns table.
It is repetitive. The same functionality can be accomplished with the extend function.

Changes Unknown when pulling 9c800921c3b936d9b64c61ca625d95c75f343a11 on josenavas:remove-add-category into ** on biocore:master**.

:+

1:

Coverage decreased (-0.01%) to 79.03% when pulling 9c800921c3b936d9b64c61ca625d95c75f343a11 on josenavas:remove-add-category into 3ad2264831d9e905fe9534e8082ef12682823379 on biocore:master.


avoid socat TTY handling

This change makes it so that everything works properly even if the user ran with docker -ti.
socat detects whether stdout is a TTY and "helpfully" stores and restores TTY settings with tcgetattr() and tcsetattr().  Upon the call to tcsetattr(), socat receives signal 22, SIGTTOU.  Docker (or some other parent process) seems to set the signal disposition for SIGTTOU to "terminate", and thus socat exits with status 150 (128 + 22).  This causes SENT_NODES not to be updated.  All that because the user thought they might want to run with docker -ti to watch the output while the cluster booted up.
Of course, the answer could be "don't run with --tty", but we don't actually need socat's stdout and this change prevents the user from shooting their foot.

Thanks for the patch and thorough explanation!


[Vlmo]  error with Step 3: Vision-Language Pre-Training (VLMo-Base)

my  command:
python run.py with data_root=./data_model_pth/data_arrows_root/ num_gpus=1 num_nodes=1 task_mlm_itm_itc_base whole_word_masking=True step200k per_gpu_batchsize=8 load_path=$INIT_CKPT log_dir=./data_model_pth/Output/
WARNING - VLMo - No observers have been added to this run
INFO - VLMo - Running command 'main'
INFO - VLMo - Started
Global seed set to 1
ERROR - VLMo - Failed after 0:01:20!
Traceback (most recent call last):
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/experiment.py", line 312, in run_commandline
return self.run(
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/experiment.py", line 276, in run
run()
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/run.py", line 238, in call
self.result = self.main_function(args)
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/config/captured_function.py", line 42, in captured_function
result = wrapped(args, **kwargs)
File "run.py", line 73, in main
dm = MTDataModule(_config, dist=True)
File "/home//Share_data//unilm/vlmo/vlmo/datamodules/multitask_datamodule.py", line 19, in init
self.dm_dicts = {key: _datamoduleskey for key in datamodule_keys}
File "/home//Share_data//unilm/vlmo/vlmo/datamodules/multitask_datamodule.py", line 19, in
self.dm_dicts = {key: _datamoduleskey for key in datamodule_keys}
File "/home//Share_data//unilm/vlmo/vlmo/datamodules/coco_caption_karpathy_datamodule.py", line 7, in init
super().init(args, **kwargs)
File "/home//Share_data//unilm/vlmo/vlmo/datamodules/datamodule_base.py", line 54, in init
self.tokenizer = get_pretrained_tokenizer(tokenizer)
File "/home//Share_data//unilm/vlmo/vlmo/datamodules/datamodule_base.py", line 19, in get_pretrained_tokenizer
return BertTokenizer.from_pretrained(
File "/home//anaconda3/envs//lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 1672, in from_pretrained
resolved_vocab_files[file_id] = cached_path(
File "/home//anaconda3/envs//lib/python3.8/site-packages/transformers/file_utils.py", line 1329, in cached_path
output_path = get_from_cache(
File "/home//anaconda3/envs/***/lib/python3.8/site-packages/transformers/file_utils.py", line 1552, in get_from_cache
raise ValueError(
ValueError: Connection error, and we cannot find the requested files in the cached path. Please try again or make sure your Internet connection is on.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "run.py", line 69, in
def main(_config):
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/experiment.py", line 190, in automain
self.run_commandline()
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/experiment.py", line 347, in run_commandline
print_filtered_stacktrace()
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/utils.py", line 493, in print_filtered_stacktrace
print(format_filtered_stacktrace(filter_traceback), file=sys.stderr)
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/utils.py", line 528, in format_filtered_stacktrace
return "".join(filtered_traceback_format(tb_exception))
File "/home//anaconda3/envs//lib/python3.8/site-packages/sacred/utils.py", line 568, in filtered_traceback_format
current_tb = tb_exception.exc_traceback
AttributeError: 'TracebackException' object has no attribute 'exc_traceback'

Hi @CHB-learner, the error may be because of the download failure of the tokenizer file ("ValueError: Connection error, and we cannot find the requested files in the cached path. Please try again or make sure your Internet connection is on.").

Hi @CHB-learner, the error may be because of the download failure of the tokenizer file ("ValueError: Connection error, and we cannot find the requested files in the cached path. Please try again or make sure your Internet connection is on.").

Is it my Internet problem? If so, can I download it manually? Because my remote server may not be able to access the Internet.

Do you have any suggestions regarding this issue?

You can refer to the transformers library, the tokenizer file is downloaded from the internet via transformers repo.

Thanks~!!
solved command
TRANSFORMERS_OFFLINE=1  python run.py ..............................


feat(hmr): add public js/css file hmr

Description
support hmr for public js/css file.

Additional context
this PR will load public js/css file in serve, and make the public file id map the file.

pass public js/css in static file server(sirv)
load the file in the new plugin.

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

We discussed with @bluwy IIRC that it would be confusing if HMR only works for js/css files in the public folder. I think that if the complexity is low, we should provide HMR for every file, and if not at least the current way things works is consistent.
Maybe we should review how many users are asking for this feature?

oh, you are right. May be we don't need to support it.


Removed extra backticks in Linux PMs

Fixes #53

https://github.com/cppalliance/site-docs/issues/53#issuecomment-1539082579

Yes. Peter's solution already includes this: https://github.com/cppalliance/site-docs/pull/49/files#diff-9550f07414fb7c6eb9212ef68722bb2e699b70f4f43f224fdc2386740aaae7b3
I don't know why the diff still shows it here though. I'm missing something.

Yep. Peter's PR fixed it.


Possible space leak in Gall on mapping ducts to bones

In %gall, instead of giving unprivileged user code raw access to ducts, we add a layer of indirection by mapping each incoming duct to an opaque integer called a bone. This mapping is never cleaned up. This implies we space leak on each message.
I'm unsure when we could clean up this mapping even in theory. We'd have to have a way of understanding that a duct is never used again.

Probably we'd want some sort of ++enumerate-all-known-bones an app can optionally implement, upon getting enough support tickets. The main short-term action here is adding the mapping as a separate clause to %gall |wegh, if it's not already, so we can keep an eye on the problem. How much analytics does urbit currently collect on each running ship, just the implicit "ping time / connectedness status"?
(If an app indirects bones by putting them in wires it doesn't store, or in turn providing an evaluation environment where they're abstracted further, ++enumerate-all-bones may similarly not be straightforward to implement)

The set of ducts should correspond to fixed entities within the system that don’t tend to expand without limit.  So long as this is true, the leakage should be manageable.
Sent from my iPhone

On Dec 19, 2018, at 5:11 PM, Elliot Glaysher<EMAIL_ADDRESS>wrote:
In %gall, instead of giving unprivileged user code raw access to ducts, we add a layer of indirection by mapping each incoming duct to an opaque integer called a bone. This mapping is never cleaned up. This implies we space leak on each message.
I'm unsure when we could clean up this mapping even in theory. We'd have to have a way of understanding that a duct is never used again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Right now, we reset the "root" ducts more-or-less every time we restart, because (almost?) all the I/O drivers all use the "instance number" (u3A->sen) in their ducts. That makes some sense, the abstract resource (listener, socket, etc.) represented by that duct has changed. But that change is not the most convenient thing ...

Even if the originating duct from Unix doesn't change, lots of internal
Arvo wires are unique. Each Ford request to Clay, for example, has a wire
containing filepath and date. I don't see how we can have a system that
both reuses ducts consistently and also provides enough information for
vanes to disambiguate responses.
I could see us building something akin to a capability system for apps. In
this scheme, Gall still holds a bone-duct mapping for each app. By default,
sending a move on a bone cancels the bone, deleting it from the mapping. If
an app wants to hold a bone open so it can send more moves on it, the app
has to ask Gall to hold it open for it.
If Gall wants to shut down an app or reclaim memory from it, Gall could
always delete the open bones, which should represent unfulfilled requests
from the app or unfinished async state machines. If it's feeling courteous,
Gall could then fire an arm on the app to let it know which bones had been
reclaimed. If a vane responds to Gall on a reclaimed duct, Gall would just
ignore the response as unknown.
At least this way the default case would be not to leak, and if it does
leak, Gall can blame the app developer.
On Thu, Dec 20, 2018 at 12:57 PM Anton Dyudin<EMAIL_ADDRESS>wrote:

Probably we'd want some sort of ++enumerate-all-known-bones an app can
optionally implement, upon getting enough support tickets. The main
short-term action here is adding the mapping as a separate clause to %gall
|wegh, if it's not already, so we can keep an eye on the problem. How
much analytics does urbit currently collect on each running ship, just the
implicit "ping time / connectedness status"?
(If an app indirects bones by putting them in wires it doesn't store, or
in turn providing an evaluation environment where they're abstracted
further, ++enumerate-all-bones may similarly not be straightforward to
implement)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449133087, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1Y9SkXadNd-GZy3JdoBlUIByGzUqC3ks5u6_nEgaJpZM4ZbT9m
.

--
—
~rovnys-ricfer
https://urbit.org

You’d probably want a duct to stay open by default, and thus require an explicit close instead...
Sent from my iPhone

On Dec 20, 2018, at 4:43 PM, Ted Blackman<EMAIL_ADDRESS>wrote:
Even if the originating duct from Unix doesn't change, lots of internal
Arvo wires are unique. Each Ford request to Clay, for example, has a wire
containing filepath and date. I don't see how we can have a system that
both reuses ducts consistently and also provides enough information for
vanes to disambiguate responses.
I could see us building something akin to a capability system for apps. In
this scheme, Gall still holds a bone-duct mapping for each app. By default,
sending a move on a bone cancels the bone, deleting it from the mapping. If
an app wants to hold a bone open so it can send more moves on it, the app
has to ask Gall to hold it open for it.
If Gall wants to shut down an app or reclaim memory from it, Gall could
always delete the open bones, which should represent unfulfilled requests
from the app or unfinished async state machines. If it's feeling courteous,
Gall could then fire an arm on the app to let it know which bones had been
reclaimed. If a vane responds to Gall on a reclaimed duct, Gall would just
ignore the response as unknown.
At least this way the default case would be not to leak, and if it does
leak, Gall can blame the app developer.
On Thu, Dec 20, 2018 at 12:57 PM Anton Dyudin<EMAIL_ADDRESS>wrote:

Probably we'd want some sort of ++enumerate-all-known-bones an app can
optionally implement, upon getting enough support tickets. The main
short-term action here is adding the mapping as a separate clause to %gall
|wegh, if it's not already, so we can keep an eye on the problem. How
much analytics does urbit currently collect on each running ship, just the
implicit "ping time / connectedness status"?
(If an app indirects bones by putting them in wires it doesn't store, or
in turn providing an evaluation environment where they're abstracted
further, ++enumerate-all-bones may similarly not be straightforward to
implement)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449133087, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1Y9SkXadNd-GZy3JdoBlUIByGzUqC3ks5u6_nEgaJpZM4ZbT9m
.

--
—
~rovnys-ricfer
https://urbit.org
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

A wire is for routing.  It should be the persistent identity of a cause — a module of the system, not an instance or event.  If you need data in the card, put it in the card!
Eg: bones go between user agents.  They are sockets.  One pair of agents, communicating for one purpose, one bone.  The sequence number is for numbering!
Sent from my iPhone

On Dec 20, 2018, at 6:28 PM, Anton Dyudin<EMAIL_ADDRESS>wrote:
I think there's some case to be made for e.g. %poke to be "ack by default",
as opposed to current "ack if not immediately crashing" or the prior "ack
only manually"; and in the case where the poke is the only card that has
used the bone, have acks reclaim them by default, with "I'm still using
this" being an explicit effect.
Or perhaps a more general principle of "this bone has had as many actions
finished on it as have been started", where subscription data is not
"finished" but a connection close is; and the escape hatch then being a
gall endpoint for "hold onto this duct" / "hold less onto this duct" manual
refcounting in cases that doesn't cover.
On Thursday, 20 December 2018, cgyarvin<EMAIL_ADDRESS>wrote:

You’d probably want a duct to stay open by default, and thus require an
explicit close instead...
Sent from my iPhone

On Dec 20, 2018, at 4:43 PM, Ted Blackman<EMAIL_ADDRESS>wrote:
Even if the originating duct from Unix doesn't change, lots of internal
Arvo wires are unique. Each Ford request to Clay, for example, has a wire
containing filepath and date. I don't see how we can have a system that
both reuses ducts consistently and also provides enough information for
vanes to disambiguate responses.
I could see us building something akin to a capability system for apps.
In
this scheme, Gall still holds a bone-duct mapping for each app. By
default,
sending a move on a bone cancels the bone, deleting it from the mapping.
If
an app wants to hold a bone open so it can send more moves on it, the app
has to ask Gall to hold it open for it.
If Gall wants to shut down an app or reclaim memory from it, Gall could
always delete the open bones, which should represent unfulfilled requests
from the app or unfinished async state machines. If it's feeling
courteous,
Gall could then fire an arm on the app to let it know which bones had
been
reclaimed. If a vane responds to Gall on a reclaimed duct, Gall would
just
ignore the response as unknown.
At least this way the default case would be not to leak, and if it does
leak, Gall can blame the app developer.
On Thu, Dec 20, 2018 at 12:57 PM Anton Dyudin<EMAIL_ADDRESS>wrote:

Probably we'd want some sort of ++enumerate-all-known-bones an app can
optionally implement, upon getting enough support tickets. The main
short-term action here is adding the mapping as a separate clause to
%gall
|wegh, if it's not already, so we can keep an eye on the problem. How
much analytics does urbit currently collect on each running ship, just
the
implicit "ping time / connectedness status"?
(If an app indirects bones by putting them in wires it doesn't store,
or
in turn providing an evaluation environment where they're abstracted
further, ++enumerate-all-bones may similarly not be straightforward to
implement)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449133087, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA1Y9SkXadNd-
GZy3JdoBlUIByGzUqC3ks5u6_nEgaJpZM4ZbT9m>
.

--
—
~rovnys-ricfer
https://urbit.org
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449210190, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhvejexzmAk8spLDzqVeMfnM8VRGnks5u7D3pgaJpZM4ZbT9m
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I certainly see how that is a possible design. Is the relevant "add a
non-wire causality mechanism" restructuring planned for the %poke / %nice /
%mean types then?

A wire is for routing. It should be the persistent identity of a cause — a
module of the system, not an instance or event. If you need data in the
card, put it in the card!
Eg: bones go between user agents. They are sockets. One pair of agents,
communicating for one purpose, one bone. The sequence number is for
numbering!
Sent from my iPhone

On Dec 20, 2018, at 6:28 PM, Anton Dyudin<EMAIL_ADDRESS>wrote:
I think there's some case to be made for e.g. %poke to be "ack by
default",
as opposed to current "ack if not immediately crashing" or the prior "ack
only manually"; and in the case where the poke is the only card that has
used the bone, have acks reclaim them by default, with "I'm still using
this" being an explicit effect.
Or perhaps a more general principle of "this bone has had as many actions
finished on it as have been started", where subscription data is not
"finished" but a connection close is; and the escape hatch then being a
gall endpoint for "hold onto this duct" / "hold less onto this duct"
manual
refcounting in cases that doesn't cover.
On Thursday, 20 December 2018, cgyarvin<EMAIL_ADDRESS>wrote:

You’d probably want a duct to stay open by default, and thus require an
explicit close instead...
Sent from my iPhone

On Dec 20, 2018, at 4:43 PM, Ted Blackman<EMAIL_ADDRESS>wrote:
Even if the originating duct from Unix doesn't change, lots of
internal
Arvo wires are unique. Each Ford request to Clay, for example, has a
wire
containing filepath and date. I don't see how we can have a system
that
both reuses ducts consistently and also provides enough information
for
vanes to disambiguate responses.
I could see us building something akin to a capability system for
apps.
In
this scheme, Gall still holds a bone-duct mapping for each app. By
default,
sending a move on a bone cancels the bone, deleting it from the
mapping.
If
an app wants to hold a bone open so it can send more moves on it,
the app
has to ask Gall to hold it open for it.
If Gall wants to shut down an app or reclaim memory from it, Gall
could
always delete the open bones, which should represent unfulfilled
requests
from the app or unfinished async state machines. If it's feeling
courteous,
Gall could then fire an arm on the app to let it know which bones had
been
reclaimed. If a vane responds to Gall on a reclaimed duct, Gall would
just
ignore the response as unknown.
At least this way the default case would be not to leak, and if it
does
leak, Gall can blame the app developer.
On Thu, Dec 20, 2018 at 12:57 PM Anton Dyudin <
<EMAIL_ADDRESS>wrote:

Probably we'd want some sort of ++enumerate-all-known-bones an app
can
optionally implement, upon getting enough support tickets. The main
short-term action here is adding the mapping as a separate clause
to
%gall
|wegh, if it's not already, so we can keep an eye on the problem.
How
much analytics does urbit currently collect on each running ship,
just
the
implicit "ping time / connectedness status"?
(If an app indirects bones by putting them in wires it doesn't
store,
or
in turn providing an evaluation environment where they're
abstracted
further, ++enumerate-all-bones may similarly not be
straightforward to
implement)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449133087,
or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA1Y9SkXadNd-
GZy3JdoBlUIByGzUqC3ks5u6_nEgaJpZM4ZbT9m>
.

--
—
~rovnys-ricfer
https://urbit.org
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449210190, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
ABxXhvejexzmAk8spLDzqVeMfnM8VRGnks5u7D3pgaJpZM4ZbT9m>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449220833, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhvLa8uKK7RYVSAyxWKWLDINl1jV-ks5u7EkVgaJpZM4ZbT9m
.

I'm confused about why we'd want to reuse ducts, and concerned that it's a
fairly different vision from how the system currently works. Multiple vanes
use ducts as unique identifiers for requests. This works when each wire
uniquely identifies its proximate cause. It doesn't work if wires only
indicate the category of cause, instead of the instance. In fact, I think
there's currently a bug in Eyre because it expects unique ducts from other
vanes but some of them get reused. I'm pretty sure all versions of Ford
also assume unique ducts.
Why would we want ducts to be reused this way, other than for making space
leaks less likely? Isn't it a lot more informative to see a stack of
specific, unique causes than to see a stack of notional reasons? For that
matter, if a wire is just supposed to represent a module, does it even make
sense to have non-unique wires, rather than just a stack of routing nodes:
~[%c %a %$]? In that case we should be able to remove wires entirely and
just have Arvo push the vane's label onto the duct.
If we stop putting identifying information in wires, that also implies that
every gift also needs to contain the card of the request to which it's
responding, or an equivalent representation of the request. Otherwise if
the requesting vane makes multiple requests in the same category, when it
gets a response it has no way of knowing which request is being responded
to. I suppose we could do that, but I don't see the benefit of making that
the responder's responsibility.
One difference between the duct stack and a synchronous call stack is that
we have multiple call stacks that interleave with each other
chronologically. At any given time each vane might have several unfinished
"function calls" in the form of notes passed to other vanes that haven't
yet responded. Another difference is that our "function calls" can "return"
multiple times, like a coroutine -- maybe Clay has responded once on a
subscription duct, but will respond again on the same duct in the future. I
see wires as the asynchronous duals of unique identifiers for the arguments
to function calls, so that when the requesting vane receives a sign in
response to its request, it knows which coroutine it's dealing with.
—
~rovnys-ricfer
https://urbit.org
On Fri, Dec 21, 2018 at 12:21 AM Anton Dyudin<EMAIL_ADDRESS>wrote:

I certainly see how that is a possible design. Is the relevant "add a
non-wire causality mechanism" restructuring planned for the %poke / %nice /
%mean types then?

A wire is for routing. It should be the persistent identity of a cause —
a
module of the system, not an instance or event. If you need data in the
card, put it in the card!
Eg: bones go between user agents. They are sockets. One pair of agents,
communicating for one purpose, one bone. The sequence number is for
numbering!
Sent from my iPhone

On Dec 20, 2018, at 6:28 PM, Anton Dyudin<EMAIL_ADDRESS>wrote:
I think there's some case to be made for e.g. %poke to be "ack by
default",
as opposed to current "ack if not immediately crashing" or the prior
"ack
only manually"; and in the case where the poke is the only card that
has
used the bone, have acks reclaim them by default, with "I'm still using
this" being an explicit effect.
Or perhaps a more general principle of "this bone has had as many
actions
finished on it as have been started", where subscription data is not
"finished" but a connection close is; and the escape hatch then being a
gall endpoint for "hold onto this duct" / "hold less onto this duct"
manual
refcounting in cases that doesn't cover.
On Thursday, 20 December 2018, cgyarvin<EMAIL_ADDRESS>wrote:

You’d probably want a duct to stay open by default, and thus require
an
explicit close instead...
Sent from my iPhone

On Dec 20, 2018, at 4:43 PM, Ted Blackman <
<EMAIL_ADDRESS>wrote:
Even if the originating duct from Unix doesn't change, lots of
internal
Arvo wires are unique. Each Ford request to Clay, for example, has
a
wire
containing filepath and date. I don't see how we can have a system
that
both reuses ducts consistently and also provides enough information
for
vanes to disambiguate responses.
I could see us building something akin to a capability system for
apps.
In
this scheme, Gall still holds a bone-duct mapping for each app. By
default,
sending a move on a bone cancels the bone, deleting it from the
mapping.
If
an app wants to hold a bone open so it can send more moves on it,
the app
has to ask Gall to hold it open for it.
If Gall wants to shut down an app or reclaim memory from it, Gall
could
always delete the open bones, which should represent unfulfilled
requests
from the app or unfinished async state machines. If it's feeling
courteous,
Gall could then fire an arm on the app to let it know which bones
had
been
reclaimed. If a vane responds to Gall on a reclaimed duct, Gall
would
just
ignore the response as unknown.
At least this way the default case would be not to leak, and if it
does
leak, Gall can blame the app developer.
On Thu, Dec 20, 2018 at 12:57 PM Anton Dyudin <
<EMAIL_ADDRESS>wrote:

Probably we'd want some sort of ++enumerate-all-known-bones an
app
can
optionally implement, upon getting enough support tickets. The
main
short-term action here is adding the mapping as a separate clause
to
%gall
|wegh, if it's not already, so we can keep an eye on the problem.
How
much analytics does urbit currently collect on each running ship,
just
the
implicit "ping time / connectedness status"?
(If an app indirects bones by putting them in wires it doesn't
store,
or
in turn providing an evaluation environment where they're
abstracted
further, ++enumerate-all-bones may similarly not be
straightforward to
implement)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/urbit/arvo/issues/954#issuecomment-449133087
,
or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA1Y9SkXadNd-
GZy3JdoBlUIByGzUqC3ks5u6_nEgaJpZM4ZbT9m>
.

--
—
~rovnys-ricfer
https://urbit.org
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the
thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449210190,
or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
ABxXhvejexzmAk8spLDzqVeMfnM8VRGnks5u7D3pgaJpZM4ZbT9m>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449220833, or
mute
the thread
<
https://github.com/notifications/unsubscribe-auth/ABxXhvLa8uKK7RYVSAyxWKWLDINl1jV-ks5u7EkVgaJpZM4ZbT9m
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449306579, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1Y9cCd4JEcNH1PWGWZ0QC8SxiYya-Gks5u7JodgaJpZM4ZbT9m
.

I guess instead of encoding the whole request in the response, we could treat them more like file descriptors. The request could contain a sequence number that the response would also include -- that's not how vanes work right now, but we could build that. If we do, though, I don't really see the utility of having wires at all. If a complex multi-vane operation failed, for example, you wouldn't see any of the actual data that failed, only the general category of operation in each vane, which isn't really much more information than the vane labels themselves.

nothing else in the system works that way

https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon#L41
https://github.com/urbit/arvo/blob/release-candidate/sys/vane/ford.hoon#L211
https://github.com/urbit/arvo/blob/release-candidate/sys/vane/eyre.hoon#L103
https://github.com/urbit/arvo/blob/release-candidate/sys/vane/dill.hoon#L14
https://github.com/urbit/arvo/blob/release-candidate/sys/vane/gall.hoon#L65

The "file descriptor" comparison is definitely apt: imagine programming in
a UNIX environment where creating temporary files was virtually forbidden
by convention, because if you did, the file would immediately be persisted
immutably to Amazon Glacier.

wut

I feel like I have miscommunicated somewhere: sole requires separate
unrelated events to come in on the same duct, everything else uses ducts as
unique ids for events(as you have just linked), I am generally in agreement
with your perspective here.
On Friday, 21 December 2018, Ted Blackman<EMAIL_ADDRESS>wrote:

nothing else in the system works that way
https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon#L41
https://github.com/urbit/arvo/blob/release-candidate/sys/
vane/ford.hoon#L211
https://github.com/urbit/arvo/blob/release-candidate/sys/
vane/eyre.hoon#L103
https://github.com/urbit/arvo/blob/release-candidate/sys/
vane/dill.hoon#L14
https://github.com/urbit/arvo/blob/release-candidate/sys/
vane/gall.hoon#L65
The "file descriptor" comparison is definitely apt: imagine programming in
a UNIX environment where creating temporary files was virtually forbidden
by convention, because if you did, the file would immediately be persisted
immutably to Amazon Glacier.
wut
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/954#issuecomment-449539672, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhmmEKyzbdJ68QKfPs-Gw5MTiSY7Xks5u7ZzKgaJpZM4ZbT9m
.

Oh, great. Can you explain your hypothetical a bit more?


MyDSLDSLDocView

A typo.
Correct it, please.

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

ID: 7cb4f2a5-261b-15ef-fe63-e5c9e4df69c7
Version Independent ID: 04a65c32-f983-ec19-c440-db7a2b7df16b
Content: Embedding a Diagram in a Windows Form - Visual Studio
Content Source: docs/modeling/embedding-a-diagram-in-a-windows-form.md
Service: unspecified
GitHub Login: @gewarren
Microsoft Alias: gewarren

@ArturGudiev thanks for the feedback, I will fix this. Unless you would like to? If you are inclined, you can click the Edit button near the top right of the page, and then commit the change.

@gewarren ok. I have created a pull request

@ArturGudiev thanks again for noticing and fixing this typo.


Usage with React

Hi!
Is there a way of using this library with React?
I try to integrate this library in my React project, and I have some issues with that,
I've included all scripts in my index.html, and I try to initialize quiet-js like this:
useEffect(() => {
  // some code...

  window.Quiet.init({
    profilesPrefix: "/",
    memoryInitializerPrefix: "/",
    libfecPrefix: "/",
  });

  function onTransmitFinish() {
    textbox.focus();
    btn.addEventListener('click', onClick, false);
    btn.disabled = false;
    var originalText = btn.innerText;
    btn.innerText = btn.getAttribute('data-quiet-sending-text');
    btn.setAttribute('data-quiet-sending-text', originalText);
  }

  function onQuietReady() {
    var profilename = document.querySelector('[data-quiet-profile-name]').getAttribute('data-quiet-profile-name');

    transmit = window.Quiet.transmitter({ profile: profilename, onFinish: onTransmitFinish });

    btn.addEventListener('click', onClick, false);
  }

  window.Quiet.addReadyCallback(onQuietReady, onQuietFail);
}, []);

And I get the next error:

I tried to debug this and it seems that the error occurs on this line:

Does anyone have any ideas on how to fix this issue or provide some minimal example of integration with React?

Update: Initially I downloaded the library from the example page and I think there was an old version, then I downloaded the files directly from Github and now there are no errors.


feature: upgrade Astro to v5 beta

Changes

Upgrade Astro to the version 5 beta

Associated issue
Resolves #188
How to test

Open preview link
See if it works
Check code mainly

Checklist

[x] I have performed a self-review of my own code
[x] I have made sure that my PR is easy to review (not too big, includes comments)
I have made updated relevant documentation files (in project README, docs/, etc)
I have added a decision log entry if the change affects the architecture or changes a significant technology
[x] I have notified a reviewer

Very happy with all the test coverage we have so far. Gives me a much better feeling with these upgrades 🙌


No work 2FA

@matuhinal Please indicate which document you are referring to. Thanks

@matuhinal Thank you for your feedback. Are you referring to this page - https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-userstates?
If yes, could you please tell us what happens when you enable 2fa?
Thanks
Sri

Yes, there is a security issue. The request is open in M 365, but has not been resolved yet

2FA problem with work account Can't change phone number to another

@matuhinal Thank you for the quick response. Since you have a support ticket open with the M365 support team, I'd let you continue working with them. This channel is specifically created for updates in documentation(Microsoft docs).
Hope this helps!
Thanks
Sri

Здравствуйте Не помогает)

@matuhinal Thank you for the response. The issue needs to be addressed by the support team and we do not troubleshoot technical issues in the forum. The best way to get your issue resolved is to contact Microsoft Support. If you’re a Microsoft 365 or Office 365 admin, use the information that’s provided at Get support.
@yogkumgit There are no changes in this document. Please close the issue.
Thanks
Sri

@msbemba  Thank you very much for the contribution and sharing this explanation. @matuhinal Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed here to close it as here, we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Swift 3

fix Swift 3 syntax error

@csbzhixing FeedParser has been deprecated in favour of FeedKit
It's the same framework, under a different name.

Sorry for this situation.


Fix live updating groups UI on changing group managing permissions.

First commit is to fix live updating stream subscribers list.
Second commit is to fix live update of groups UI.

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

🔍 Existing Issues For Review
Your pull request is modifying functions with the following pre-existing issues:
📄 File: web/src/user_group_edit.js
Function	Unhandled Issue
update_general_settings_elements Error: the: expected exactly one item the(src/util)
Event Count: 1 Affected Users: 1
Did you find this useful? React with a 👍 or 👎

This was fixed in 688def19ab48.

Merged, thanks @sahil839!


Print Format Error (Clinton06)

Please investigate why some print formats on Clinton06 (Staging) faced the error below, even though the Print format code is exactly the same as on Clinton02 (Production). but on Production site there is no error.
example affected doctype:
Sales Order
Sales Invoice
Quotation

Fixed.


No one uses batch files anymore

Windows Powershell was introduced in 2006 and has been built into the OS since Windows 7. It's been the de facto default shell for Windows development ever since.
A lot of cross-platform projects that are not primarily targeted at Windows haven't kept up with this transition, but it's really time to switch off a scripting language that's been all but deprecated in the Windows development world for years.
Incidentally, Powershell is also a full-scripting language with a feature set comparable to Bash, not a clunky command runner. Using it would mean we didn't need to lean on install-time replacement of the path the python executable, making robot play much nicer with virtualenv.

We've been actually thinking about starting to use .exes instead of .bats in RF 3.1 (#2415). Would Powershell scripts have some benefits compared to them? Do they work with Win7 and newer out-of-the-box or do you need to install something? The only good thing about batch files is that they are ubiquitous.

There's nothing you could do with a ps script you couldn't do with an exe. The main benefit is transparent readability (like a shell script). But exes might be a nice alternative!

These exes would be automatically created by setuptools. The problem is that I'm not sure do all the supported Python interpreters (incl. Jython and IronPython) support creating them.
Could ps scripts somehow avoid the current problem with batch file?

Throwing my two cents into the ring, in my personal experience batch files are still widely used. I also feel moving to PS is not as clear-cut; I have witnessed some exotic installations of Windows 7 without Powershell ie. some large companies deliberately remove it from their employees' laptops during installation. Batch, due to nature of Windows' backwards compatibility, will probably work forever instead.
Granted, if PS is chosen, it is trivial to write a batch wrapper for it. However I would personally much prefer exe's.

No Powershell please. It is restricted to use in many companies due to security issues.

robot.exe is the way to go. Closing in favor of #2415.


Don't redraw screen when returning from temporary EmptyFormAction

Fixes https://github.com/newsboat/newsboat/issues/1463 by skipping a redraw when returning from an EmptyFormAction.
Before https://github.com/newsboat/newsboat/pull/1259, those lines weren't hit when opening a browser because the local f variable would be a nullptr.

Coverage increased (+0.004%) to 58.993% when pulling 68b987201f9dcf8dd8dfaafff41a10a781600cf5 on dennisschagt:bugfix/issue-1463 into 729edb6f4bb4e6c488b1ab45baab07a964edd372 on newsboat:master.

Looks like I based my changes on an old version of the master branch. I just rebased.


nil message received causing NPE

The case messages <- message
here at https://github.com/wvanbergen/kafka/blob/master/consumergroup/consumer_group.go#L413
appears to succeed, but there are situations I see where message == nil.  This cause a problem when message.Offset is accessed in the case arm.  I have not tried to further characterize what makes message == nil.
I'm using go 1.5.1 on ubuntu 14.  For my present set of tests, I'm also compiling and runing -race, although I have not run anything to rule in/rule out these situations

I suppose message can be nil when the messages channel gets closes by the consumer, after which the channel will return nil continuously.

It's unlikely that I will get to this any time soon, but I'll gladly review and apply patches.

I'm no longer in a good position to try your patch... the project I was working on that needed these improved semantics was cancelled back in January, and I'm not sure I can put the pieces back together to fairly exercise this infrequently occurring situation.

Closing this ad a duplicate of #95