Getting Godaddy Windows Machine with Parallels Plesk to Work

Hi, do you think you could offer any insight into how to get a Windows web.config correct to get this working on a Windows machine?  I am using the web.config below and it just redirects me to the cgi-node.js and shows that text in my browser.  I am assuming I am missing something in order to get the
cgi-node.js to "run" instead so I can see the results of .  Any help would be appreciated.  Thank you.
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="cgi-node">
                    <match url=".jscript" />
                    <action type="Rewrite" url="\cgi-bin\cgi-node.js" appendQueryString="false" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>

I would love to help. IIS (Internet Information Services) hosting and configuration is completely different than Apache. You'll need to tell IIS to execute *.jss scripts as CGI using node.exe. Since we are using an intermediate script, cgi-node.js, to execute the page it might be a bit tricky.
If IIS allows parameter passing to the CGI application this it will be easy, otherwise I might have to create an exe that wraps node.exe with cgi-node.js to then execute the web script file *.jss.
These are some clue on the direction to take with ISS. I'll try it out and keep you posted.

Awesome, that would be great.  Thanks a lot!  I'll keep researching myself as well.

I setup IIS to execute cgi-node for *.jss files. It worked but I got the following error:
node.js:558 throw new Error('Implement me. Unknown stdin file type!');
Error: Implement me. Unknown stdin file type! at process.stdin (node.js:558:17) at startup (node.js:155:16) at node.js:814:3
I'll need to look into it further...

Okay.
I'm learning/playing with IIS web.config-urations (not making much progress, but understanding more).  Is this being run as a classic/legacy CGI application or as a FastCGI application?


Datagrid showing horizontal scroll if the last column is hidden

Describe the bug
Datagrid showing horizontal scroll if the last column is hidden
How to reproduce

https://clarity-datagrid-horizontalscroll.stackblitz.io
Steps to reproduce the behavior:
https://stackblitz.com/edit/clarity-datagrid-horizontalscroll
Expected behavior
It should not show horizontal scroll if the width is enough in the window.
Versions
App

Angular: 8.x
Clarity: 2.3.1

Device:

Type: [e.g. MacBook]
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional notes
Add any other notes about the problem here.

This is a known issue.Please subscribe to #1248 for updates. fwiw - the PR for drag and drop columns should fix that issue. Can you confirm @Shijir ?
I'm closing this in favor of the existing issue.


Improve exception reporting in build plugins

It seems that when the AOT generation phase fails (because a dependency is not supported or other reasons), the build plugins don't always properly report the exception cause and developers need to use a -X (maven) or --stacktrace (gradle) CLI flag to see the root exception.

After checking this, it seems we're already good citizens here.
Maven shows the following:
Build failed during Spring AOT test code generation: Could not generate spring.factories source code: Devtools is not supported yet, please remove the related dependency for now. -> [Help 1]

Gradle shares less details by default, but this seems in line with other plugins:
 * What went wrong:
Execution failed for task ':generateAot'.
> Could not generate spring.factories source code

Closing this issue as declined as a result.

Using Gradle, this is actually what the problem is. Gradle does not show Devtools is not supported yet, please remove the related dependency for now part so lots of time spent on debugging...

Thanks for the feedback @UkonnRa
We would like to improve this situation. What was your process for finding the root issue here? In your opinion, what would be the typical way of handling this for a Gradle plugin?

@UkonnRa Could you please provide us a feedback ?

I think it's not an important problem so I have not spent more time on this. The current situation is good enough. Thanks


[Question] is there any way to link recordes after CUD operations automatically  ?

Hi
When i use the create link command to link related data according to  create link documentation  everything is OK . but i need a feature to link or unlink records after CUD operations . it must be like an observer with a link pattern that i defined in create link command .
Is there any way to save my link pattern in ODB and after CUD operations ODB apply the link pattern only on current record (just like a CUD trigger) ?
If the answer is NO :
We would have the following syntax in create link command:
CREATE LINK <link> TYPE [<link-type>] FROM <source-class>.<source-property> TO <destination-class>.<destination-property> [INVERSE] [ON CREATE|UPDATE|DELETE|ALL]
Thanks
Saeed Tabrizi

Hi @saeedtabrizi
You can write a custom hook: http://orientdb.com/docs/2.2.x/Hook.html
It's not trivial, but it's powerful enough for what you need
Thanks
Luigi

Hi @luigidellaquila
Thanks for the best answer from you .
We can close this issue now .
Saeed


Pressing enter key doesn't make new line.

I'm new to draft-js. I found a problem while testing and using it.
Because this rich text editor doesn't make new line in Korean.
I have to press enter twice as aforementioned. It's really inconvenience.
This situation is also being happened in Facebook Note and Messenger.
If this was intended to prevent mistake during type, It should be fixed or changed.
When user press enter, line should be changed.
My test environments was OSX latest, Chrome latest.

I tested more:

Chrome needs enter twice
Safari works well. best.
FireFox similar to Chrome.
Opera similar to Chrome.

Are you using OSX El Capitan?

@hellendag Yes, it is latest version

Thanks. There are some known issues with Korean composition that appear to have been introduced by El Capitan. I'll follow up here with details.

@hellendag I saw it is working well at Windows. It can't be fixed in OSX El Cap?

Here's the crux of the issue. See the screenshot below, the result (in Chrome 49) of testing on https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html with the following steps:

Switch to 2-set Korean keyboard
Type d (ㅇ)
Press backspace to delete the character.

The events occur from the bottom (oldest) to the top (newest).
Note the compositionEnd and textInput events. The data field here should be the empty string -- the character is being removed after pressing the backspace key, so the events should not carry the ㅇ character in the data field.
The Draft composition handler expects that deletions do not preserve the deleted character in the textInput event data field for this reason. While OSX versions prior to El Capitan behaved correctly, it's broken now. Note that this bug occurs on Firefox and Safari as well -- it appears to be an OS-level issue. Windows does not have this problem.
We may be able to devise a workaround, but the problem here would be that we won't know the difference between a committed composition and a deleted one. When textInput fires, the backspace key has not yet been handled, so there would be no detectable difference between a deletion and a confirmation. We could defer handling the textInput until after some key event, in order to detect whether it's a deletion or a commit. But that's kind of a hack.
The most appropriate thing here is probably for us to file an issue with Apple.

@hellendag I see. Even if I pressed delete, data still consist composited word in OSX El Cap.
Can I suggest about it?
I saw Draft works well on OSX El Cap Safari. I checked the event occurs.

There's no composition type events. I think Draft doesn't need composition types....
Only textInput, input, keydown and keyup events are not enough to implement Draft composition handler? Is it for other language?

Hmm. Something is very wrong with Korean input on El Capitan.
I just tried this in Safari and ran into a bunch of different weird event sequences when switching language to Korean or reloading the page, including both yours and mine.

Initially, I saw something that looked like your screenshot: no composition events, no textInput event. (This is unequivocally wrong.)
I switched to Katakana and typed a test string. Composition events appeared properly.
I then cleared the input and switched back to Korean. Characters didn't even get inserted into the input, though key events fired. No composition or textInput events fired.
I reloaded the page and typed Korean characters. Everything then worked the same as in my screenshot, with composition events and the incorrect data field.

@hellendag IMHO, biggest problem usint draft.js with Korean is 'enter key event problem' which already mentioned by @Beingbook.
So, how about change to insert hardcoded newline when last event was ''compositionupdate'' and not 'compositioned"?
Then (I think ) it will be good enough.

Hi - following up on this, it sounds like the original bug reported was an issue with Korean IME in all browsers in El Capitan. The only action item is:

The most appropriate thing here is probably for us to file an issue with Apple."

Since we don't have a solution for fixing this within Draft I'm closing this issue. Please reopen if you would like to propose a work-around.


CocoaPods integration

I added Log4swift in my project using cocoapods and throw me this errors when is building the project:
MyProject/Pods/Log4swift/Log4swift/log4swift.h:32:9: error: include of non-modular header inside framework module 'Log4swift.log4swift'
#import <Log4swift/NSLogger.h>
MyProject/Pods/Log4swift/Log4swift/log4swift.h:33:9: error: include of non-modular header inside framework module 'Log4swift.log4swift'
#import <Log4swift/LoggerClient.h>
MyProject/Pods/Log4swift/Log4swift/log4swift.h:34:9: error: include of non-modular header inside framework module 'Log4swift.log4swift'
#import <Log4swift/LoggerCommon.h>
MYProject/Pods/Log4swift/Log4swift/log4swift.h:36:9: error: include of non-modular header inside framework module 'Log4swift.log4swift'
#import <Log4swift/ASLWrapper.h>
:0: error: could not build Objective-C module 'Log4swift'

Hi josete89,
I'm trying to reproduce the problem using a swift project, Xcode 7.0, cocoapods v0.39.0 this podfile :
platform :osx, '10.10'
pod 'Log4swift', '1.0.0b3'
use_frameworks!

It is working without an error.
Can you post the podfile you have ?

platform :ios, '8.0'
use_frameworks!
target 'MyTarget' do
pod 'CWStatusBarNotification'
pod 'Socket.IO-Client-Swift' , '~> 3.0.1'
pod 'SwiftLoader', :git => 'https://github.com/leoru/SwiftLoader'
pod 'EasyAnimation' , '~> 1.0.1'
#pod 'RxSwift', '~> 2.0.0-alpha'
#pod 'RxCocoa', '~> 2.0.0-alpha'
#pod 'RxBlocking', '~> 2.0.0-alpha'
pod 'RealmSwift', '~> 0.95'
pod 'Log4swift', '1.0.0b3'
pod 'ReachabilitySwift', '~> 2.0'
pod 'Fabric', '~> 1.5'
pod 'Crashlytics'

end

What Xcode are you using? It seems Xcode bug!

I did the sample project on Xcode v7.0 (7A218)

I'm using Version 7.1 (7B91b) ,it seem this bug fixed in 7.0 but comes back in 7.1 ... I added the code in PodFile and didn't work I'm still finding a solution

CocoaPods issue -> https://github.com/CocoaPods/CocoaPods/issues/3767

Ok.
Maybe I should close this issue then, if you agree with it.
Thanks for the link !

Yes you can close the issue!


[API. Feedback & Complaint] Missing validation on existing user in 'userId' field and existing club in 'clubId' field

Environment: Windows 10 x64, Postman v9.0.7.
Reproducible: always.
Build found: last commit.
Preconditions:

Run Postman
Create new request > Choose 'POST' in 'Method' drop-down
Navigate to 'Authorization' tab, choose 'Bearer Token' in 'Type' drop-down
Set 'accessToken' of any user (e. g. 'email'<EMAIL_ADDRESS>'password': "admin") in 'Token' field

Steps to reproduce

Choose Body > raw > JSON
Enter request URL: https://speak-ukrainian.org.ua/dev/api/feedback
Enter a request to create feedback with non-existing 'userId' (e. g. '234341111111111') and 'clubId' (e. g. '434222222222223') values:
{  "text": "Some text",  "rate": 2,  "userId": "234341111111111",  "userName": "Some User",  "clubId": "434222222222223" }
Enter request URL: https://speak-ukrainian.org.ua/dev/api/complaint
Enter a request to create complaint with non-existing 'userId' (e. g. '234341111111111') and 'clubId' (e. g. '434222222222223') values:
{  "text": "Some text Some text Some text Some text",  "userId": "234341111111111",  "date": "2021-11-03",  "clubId": "434222222222223" }

Actual result
In all cases server is responding with 500 status - 'Internal Server Error' and no any error messages appear.
Expected result
In all cases server should respond with status 400, system should check if entered user or club is exist and if it is not - propper error messages should be displayed.
User story and test case links
Validation of the fields should be performed according user stories below:

#115
#287

Screenshots:
Actual result - feedback

Actual result - complaint

Bug is fixed


A way to re-initialise the renderer to apply changed settings without restart

A way to re-initialise the renderer to apply changed settings without restart.
Currently, to change the shadow quality one must restart the game. Other options are probably setup like this as well.
It would be good to be able to reboot systems to apply changes without having to restart the game.

I have also noticed this and was going to post an issue about it. The need to restart to update the directional shadow quality setting only seems to happen under Linux for me. Works fine in Win10, without having to do restart/reload.

You can do all this from the Viewport API, what you see in Project Settings are just the default values.
As this is already supported (just use get_viewport().set_shadow_blabla), closing this issue


Check for closure compiler before downloading

in "make dist", the wget isn't necessary if closure exists on the machine

Rewritten as #99 including more cases of error in the build.sh

fixed in issue #99


Add {string} parameter type and fail on undefined parameter types

Summary
Add a {string} default parameter type
Expected Behavior
A {string} should match anything, .+. This is consistent with current behaviour for {undefined} parameter types, which currently default to passing a string through unmodified.
An {undefined} parameter type should throw an error.
Current Behavior
If you just want a string, it's common to just name an expression parameter similarly to the stepdef body parameter name, for example {name}, without defining a corresponding type parameter.
Possible Solution
define {string}, change code that handles undefined parameter to throw an error rather than letting it through.
Context & Motivation
It is not uncommon to make mistakes when writing Cucumber expressions. A mistyped parameter name can cause unexpected results, such as parameters that don't get transformed.
Further, enforcing the use of explicit parameter types encourages more attention to building a consistent, ubiquitous language in Cucumber expressions and Cucumber scenarios.
This issue is related to #190

This was implemented as {word}, with regexp \w+


Crashes on Notification received

Fix background crashes when receiving push notifications
Base branch: develop
Purpose
Fix the crashes that happen when receiving push notification while the app is in background
Success condition
Prove crashes when receiving push are no longer reported by users nor showing in crash reports
Context

Users are reporting their app crashing while in background when receiving push notifications
Some users reported that when turning off "Do not disturb mode" and all the push notifications are received, they get one crash per push notification

Steps

Review NotificationService logic where the notification content is changed to show tribe/conversation information and fix issues that could cause crashes
Review didReceiveRemoteNotification logic on AppDelegate where new messages are fetched when a new push notification is received and fix issues that could cause crashes

@Khaalid-oh I'm not sure if we still have crashes when notifications are received. I didn't get user reports recently and I didn't see reports in bugsnag about this neither. So I don't think it makes sense that you take this ticket right now. I will let you know if the issues comes up again

Alright, thanks. I'll be hanging on for an update from you


Somehow have the ability to save previous configuration

Hi !
I've successfully installed lxd-webui on our system thanks to your clearer instructions than the initial ones. I wanted lxd-webui to be abble to view in a graphical way the state of the containers hosted on our hosts. The problem is, right now, that each time we want to see what's on a peculiar host, we have to change the settings page, re-chose the desired certificate and so on before we can get the informations we want. Do you plan to add an option somewhere so that we could save the configuration and recall it whenever we want ?
Thanks.

If i understand correctly: You have multiple LXD server, and you use LXD-WEBGUI to access "all" of them. But then you have to change the configuration each time?
I can add support for multiple LXD server, each with their own settings, and make it possible to quickly switch between them.
In the mean-time as a quick fix, you can just start multiple LXD-WEBGUI's (e.g. start one python http server on port :8080, one on :8081, one on :8082, ...). The configuration should be unique for each port/instance, so if you access :8080, you it is configured for LXD server 1, on :8081 it is configured for LXD server 2 etc.

On a side note: You had troubles/problems with setting up lxd-webgui? Can you elaborate? Is it certificate related? I'd like to make installation as easy and straight forward as possible.

I'll try to explain the context in which we use both lxd and lxd-webui, so that you can understand the use-case and the problems I faced concerning the install of lxd-webui.
We have three network zones, each one has it's own purpose. Our setup include 7 hosts to serve different things.
There are 2 machines per zone, which work in balanced mode.
If I take the example of one of these machines, it hosts an apache2 webserver running as a reverse proxy for each lxc container.
And each container has it's own production environment to serve what it has to serve (own version of apache/php/tomcat/whatever is required).
The 7th machine is on top of all the 6 previous ones and is here for administration/setup.
Exemple taken for lxd-webui :
I set up a lxc container on the administration machine, to make a full install. Your documentation was much appreciated, even though I finaly fall down to have lxd-webui served by apache rather than the simple http-server you present in the readme.
So, on the host, I have the main apache that serves just as a reverse proxy for the lxc container serving lxd-webui.
Since lxd-webui is here to have an overview of all that is running on all machines, it will stay as it is on this "admin" machine.
Now, when I setup a production application, I do the same, and when everything is fine, I use lxc copy to deploy the container on the two machines of the concerned zone, copy the apache2 config files of the host-admin to the apaches that serves as reverse proxy on the two production hosts and the load balancing is configured accordingly to access these two hosts and finaly the two lxd containers.
So, we have 7 lxd hosts machines to manage. lxd-webui is handy and very promising for this purpose.
The only problem I faced, is that on each lxd host I had to create a certificate and add it to the trusted certificate of the lxd process.
I hope my explanations are clear enough :-s

Wow that's quite a setup you have there, but i'm not sure i understand 100%. But maybe this is already a use-case for enterprise-grade software, like Kubernetes, or other container orchestration software.
Concerning the client certificate: You can create one client certificate (the self-signed cert you have to import in the browser), and add this cert to all LXD hosts as trusted cert. There should be one client certificate per administrator (it is the equivalent to username+password).
Anyway, what you would need is the ability to specify different LXD hosts, and lxd-webgui should use them all at the same time. This way, you can see the state of all containers of the different LXD hosts. E.g. in the container overview: "webserver-1-container @ lxd-zone-1", "webserver-1-container @ lxd-zone2", where lxd-zone1 and lxd-zone2 are two different LXD servers. Is this correct?

You have fully understood our setup. And indeed, either have each container displayed as you suggest or have the ability to chose the host in a select box would be great !

I'm also running into this requirement (managing of different LXD hosts) right now. I think i will implement this feature, but it requires quite a bit of work. May take me a few weeks until its done.

sounds nice feature to have. If i have multiple LXD hosts, it would be nice to use one control panel to show an aggregate of all containers and its associated host with basic filter option to i can limit output to specific host.


Question / Request: make APK available outside Google Play

Hi,
I am trying to keep my Android device running without a google account - something more and more people appear to do. OS Monitor used to be available in the F-Droid store but it is no longer there. Is there any way to get the APK without a google account? I found an old version here but would love to get the most recent version of course...
https://code.google.com/p/android-os-monitor/downloads/list
Thanks!

Hm, weird, I get a Not Found error when trying to install from the F-Droid app but can download the APK from the browser...

I can install it from F-Droid today. It looks local repository database of F-Droid is not up-to-date, or temporary broken.

Works here now, so fixed, thanks.

Hi guys,
Please update apk-file in F-Droid repo.
It's very nice when you can install fresh OS Monitor from F-Droid, not from Google Play.
Thanks!


Round 7 - Daily Intake Report - Camera

When the camera button is pressed, the blue box that has "Snap a Photo" and Scan Barcode" has a little triangle in the top right corner that points to the pencil tool.  It should be pointing to the camera button. Similarly with the pen/search button, when that is tapped, the little triangle should point to that icon (and not the water icon).

Fixed.


Display Error Message When Deleting Report Approval Step and a Report is Still Pending

When saving an advisor organization, a cryptic error message is sometimes displayed.  The current message states: "Not Acceptable: You do not have permissions to perform this action."  The error message comes from an approval step that has been removed that still has a pending report assigned to the approval step.
Improve the error message to let the super user know exactly what's wrong.
Or even better, when the super user removes the approval step (with a pending report), display an error message and don't let the approval step be removed.  Display the error message when the report approval step is deleted instead of when the advisor organization is saved.
Reference item 104

The issue seems to be a bit larger than simply displaying the error message.
Approval steps are not correctly loaded from the database:
When editing an organization: After adding a new approval step, the step does not show up in the list. At random when editing the approval steps, one or multiple steps do no show up.
@gjvoosten will look into the db specifics to figure out what is going wrong

The erratic behaviour appears to have been caused by corrupt approval chains in the database (multiple approval steps with the same next step).The database has been manually corrected, and the code has been updated to wrap approval chain manipulation inside a database transaction to avoid future inconsistencies.


Added derivations for Type, ParseFromJSON and ToJSON for sqlx::types:…

Added derivations for Type, ParseFromJSON and ToJSON for sqlx::types::Json<T>.
Purely ergonomical, and passes all implementations to the child T.

thanks

Perfectly timed 👏


Example - "Sensorica 3D Printer"

See: http://requirebin.com/?gist=01d39d31f218a6a4f429cccbe7b91e80
And: https://github.com/serapath/economy/blob/master/example/sensorica3Dprinter.md

Improvements:

[ ] How to book "debt-like", "equity-like", etc... sensorica member contracts
[ ] Maybe switch "claim" to "accounts receivable"

Inspiration:

"Recipe + Plan + Reality"


fix(security-vulnerability): fix security vulnerability

:tada: This PR is included in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix yargs typing with zod in all clis

all yargs usages except dataset generation has any typing and no zod checking

Low priority


Rename improperly named functions in MSFT_xExchClientAccessServer, MSFT_xExchDatabaseAvailabilityGroupNetwork, MSFT_xExchEcpVirtualDirectory, and MSFT_xExchExchangeCertificate.

Pull Request (PR) description
Rename improperly named functions, and add comment based help in MSFT_xExchClientAccessServer, MSFT_xExchDatabaseAvailabilityGroupNetwork, MSFT_xExchEcpVirtualDirectory, and MSFT_xExchExchangeCertificate.
This Pull Request (PR) fixes the following issues

Fixes #286
Fixes #288
Fixes #289
Fixes #290

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md.
[x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #344 into dev will decrease coverage by 0.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##              dev     #344      +/-   ##
==========================================
- Coverage   32.22%   32.21%   -0.02%
==========================================
  Files          39       39
  Lines        4642     4641       -1
==========================================
- Hits         1496     1495       -1
  Misses       3146     3146

Impacted Files
Coverage Δ

...rk/MSFT_xExchDatabaseAvailabilityGroupNetwork.psm1
21.05% <25%> (ø)
:arrow_up:

...angeCertificate/MSFT_xExchExchangeCertificate.psm1
13.04% <25%> (-1.25%)
:arrow_down:

...irtualDirectory/MSFT_xExchEcpVirtualDirectory.psm1
31.03% <50%> (ø)
:arrow_up:

...ientAccessServer/MSFT_xExchClientAccessServer.psm1
23.07% <50%> (ø)
: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 59a6ced...71a5bd7. Read the comment docs.


fix comments lost in generated DDL.

no comments generated on DDL in database, this problem should be fixed, or there's no way to get descriptions for the tables and their columns unless checking the schema golang code, which may  lead to  impossibility of reverse engineerings and incomprehension for DBA.

Hey @chaosue! Any update on this PR?

After a discussion with Cheng on Discord, we think the configuration can be simplified by providing a single annotation in the entsql package to indicate that columns' comments should also be stored on the database schema. For example:
func (T) Annotations() []schema.Annotation {
    return []schema.Annotation{
        // WithComments indicates that all entity comments
        // should be stored in the database schema as well.
        entsql.WithComments(true),
    }
}

Table comments can be implemented once https://github.com/ent/ent/pull/3164 is merged, and an entsql.Comment(string) annotation can be added in case there are requests for mixed comments (one for code generation, and one for the database).

entsql.Comment(string)  When will this feature be implemented?

table comment ? entsql.WithComments(true), schema.Comment(string) SQL DDL not work。Will this feature be supported? @a8m

if you want to generate table comment and column comment, you can upgrade your entgo to master version. And then use like this:
type T struct {
	ent.Schema
}

func (T) Annotations() []schema.Annotation {
	return []schema.Annotation{
		entsql.Annotation{Table: "t"},
		entsql.WithComments(true),
		schema.Comment("t is like business unit table"),
	}
}

func (T) Fields() []ent.Field {
	return []ent.Field{
		field.String("name").Comment("unique name"),
		field.String("description").Default("").Comment("xxx"),
	}
}

table comment ? entsql.WithComments(true), schema.Comment(string) SQL DDL not work。Will this feature be supported? @a8m

if you want to generate table comment and column comment, you can upgrade your entgo to master version. And then use like this:
type T struct {
	ent.Schema
}

func (T) Annotations() []schema.Annotation {
	return []schema.Annotation{
		entsql.Annotation{Table: "t"},
		entsql.WithComments(true),
		schema.Comment("t is like business unit table"),
	}
}

func (T) Fields() []ent.Field {
	return []ent.Field{
		field.String("name").Comment("unique name"),
		field.String("description").Default("").Comment("xxx"),
	}
}


Add source map support

Errors are difficult to debug when given a stack trace because there's no source map support.
Here's an example stack trace where source map support would have made it much easier to debug an issue:

+1, this will also help for Sentry errors. I am hoping to add this to our cue on Q1

Yep, indeed. I have a PR that never got merged https://github.com/hirosystems/stacks-wallet-web/pull/1876
Sourcemaps are a little trickier for extensions, as Sentry can't just go and fetch them. We need to upload them on release.

This issue has come up again. QA is running into errors that are potentially blocking/delaying another API release because the there's no (useful) error logging or source maps:

index.js:150788 TypeError: Network request failed
    at XMLHttpRequest.xhr.onerror (index.js:83310:16)
onError @ index.js:150788

Thanks Matt for bringing it up. This one is in the radar for @He1DAr as he improves our Sentry implementation


redux-form should not write errors to the console explicitly.

Formerly https://github.com/erikras/redux-form/pull/3723 was merged to address https://github.com/erikras/redux-form/issues/3636
The original issue (https://github.com/erikras/redux-form/issues/3636) was that exceptions thrown in an onSubmitSucceeded handler were being swallowed. The fix in https://github.com/erikras/redux-form/pull/3723 handled this by explicitly logging an error to the console (i.e. with console.error)
I'd like to suggest that this isn't the correct fix for the problem.
When an error is thrown within a promise, the normal and expected behavior is for the promise to reject. This was occurring, but due to a separate issue (https://github.com/erikras/redux-form/issues/3303), the promise was later being marked as resolved.
The correct fix to the original problem is to let the error in an onSubmitSucceeded handler bubble up as an unhandled rejection. This has already been solved in https://github.com/erikras/redux-form/pull/3744, although it wasn't solved at the time that https://github.com/erikras/redux-form/issues/3636 was opened.
In other words, the fix in https://github.com/erikras/redux-form/pull/3744 makes the fix in https://github.com/erikras/redux-form/pull/3723 unnecessary, and also the fix (explicit use of console.error) in https://github.com/erikras/redux-form/pull/3744 is undesirable. We should not consider exceptions raised in a promise to be errors that should be written to the console -- instead, just let them bubble up as rejected promises.
I'm opening this issue to request that you consider reverting https://github.com/erikras/redux-form/pull/3723
Thanks!

cc/ @h1b9b  @ClementParis016

Note: The current code will console.error not just for errors thrown in onSubmitSucceeded, but for errors thrown in onSubmit also. So supposing you return a promise from onSubmit that rejects with an error that is not a SubmissionError, then the error will be written to the console. My opinion is that it is undesirable for the library to do this by default because a rejected promise returned from onSubmit is not necessarily something we want our application to consider as an error and write to the console.

I totally agree with you @naw, logging the error makes it visible but it doesn't provide any solution to handle it. I would rather like to be able to handle the error myself and report it to an external logging system.

@ClementParis016 To be clear, you can handle the error yourself now by watching for unhandled promise rejections. This was fixed in #3744 and follows normal promise behavior (except for the extra console stuff, of course).  Not sure if this solves your particular problem or not.

Published fix in v7.3.0.


Comment Spelling Cleanup

for the sake of looking nice, although it obviously does not really matter.

Thanks for PR!


Problems during reimplementation

First of all, thank you very much for your excellent work. I've been trying to replicate your results, but I've encountered some issues, and I hope you can help me with them. Firstly, the results I obtained during replication did not match the results mentioned in the paper (AP 33.02, AP50 57.87, AP75 33.09), and there is a significant difference. Below are the training and testing commands I used:
Training:
python train_net.py --num-gpus 1 --config-file configs/RCNN-FPN-CROP.yaml OUTPUT_DIR outputs_FPN_CROP_VisDrone

Testing:
python train_net.py --eval-only --num-gpus 1 --config-file configs/RCNN-FPN-CROP.yaml MODEL.WEIGHTS <your weight>.pth

I hope you can point out any mistakes I may have made. Thanks again.

Check the issue #16.

Can you share your R-50.pkl with me, thank you

It is not mine in any regard. I downloaded it from the source mentioned in Detectron2's official code.

I downloaded R-50.pkl here, is it the correct pkl file?

Yes

Okay, then the difference in experimental results should be a configuration problem, thank you.


Fix triangle clipping in drawByPath3()

Currently drawByPath3() is generating some weird glitches, when mesh is partially outside of view frustum.
This is probably issue which should be in PS2SDK, but I will leave it there.
Line in PS2SDK which propably cause the glitching
Using in:
https://github.com/h4570/tyra/blob/d58163d75be2d6c848f4456f73cebd8a6c1a63bd/src/engine/modules/gif_sender.cpp#L217

Visual example of the glitch:

DrawByPath3() will be depreceated in next releases


Add guidance on which release to use

On jupyterlab start-up. I guess this goes in all of Hello World, GettingStarted.md, and the README, in that we should say repeatedly, we develop against the most recent release unless there is good reason not to (like, a particular new function is needed). It'd be good to only say in one place what that most recent release is - perhaps on the main README.
This is separate from noting which release each notebook was last verified on - in principle they should all say the most recent release, but they may not (for one reason or another).

There are releases and releases. I think you want to be developing against the most recent major release (modulo any bugfixes), which is currently 16.0. I think it would be best to avoid the daily and weekly releases in general.

The LSST Science Platform Notebook Aspect tutorial that new users are likely to use while getting setup on the platform suggests using the latest daily release. I think it would be good for the main README to say that its suggested release takes precedence over the notebook tutorial so that new users can follow unambiguous directions.

@jtmyles those LSP docs say that developers of the LSP shoudl use the most recent daily, but users like us should use a supported release or the most recent weekly. Our CIT script uses the supported release via --kernel lsst, so for this reason and Paul's above, we should go with that. I'll check our docs now and then close this out.


initial implementation

do you have any suggestions how i can improve the repo?
@BinaryLust can we has travis enabled for the github organisation?

generated verilog netlist doesn't work on simulation


visualization

❓ Questions & Help
Hi, does PyG have a visualization tool to help us see the states of node classification during the training process?

Hi, I'm sorry. We do not provide any visualization tools. You need to consult other libraries for that, e.g. networkx. We provide convert methods to the networkx format in the torch_geometric.utils subpackage.

Btw @rusty1s , which tools (e.g., meshlab) or library (e.g., menpo3d, MPI-IS/mesh) are generally used to visualize meshes or 3d shape?

Never used any library for this, so I do not have any recommendations. For visualizing, I usually export models in .off format and render them.

@rusty1s  Can you elaborate it a bit? Which software do you use to render them? Thanks.

.off is a really simple format which I write manually. Alternatively, you can use .ply (with plyfile package). I render them with Blender.

Thank you @rusty1s

I've been extracting the embeddings from the forward pass and using plotly to plot at each epoch. May not be useful for large n


Citing this library

I am using this library in my bachelor thesis and it plays an integral part and I was wondering if you have any preferred citation method?
Right now I would include author, title, url, version, date.
I couldn't find any paper about this specific library... (other libraries, such as dicom_wsi or Dicomizer have separate papers)

Hi @wand555
Great to hear that you are using the library for your thesis!
Unfortunately there is not yet any (public) publications for this library, so your suggested citation is appropriate.


Cant get many-to-any data when querying the items

I'm trying to retrieve page data according to Directus docs: https://docs.directus.io/guides/headless-cms/reusable-components.html
However, the returned data doesn't include related items fields at all... just id fields from the relation table.
My code:
const fetchArticle = async () => {
  try {
    const filters = { slug: route.params.slug || 'home-page' }
    const page = await getItems({
      collection: 'pages',
      params: {
        filter: filters,
        fields: [
          '*',
          {
            content: [
              '*',
              {
                item: [
                  {
                    basic_section: ['*'],
                    home_gallery: ['*'],
                    call_to_action: ['*'],
                  },
                ],
              },
            ],
          },
        ],
        limit: 1,
      },
    })
    return page[0]
  } catch (e) {}

And the result:
{
  "id": "449107f9-ef17-4e74-9d55-cef747887a41",
  "status": "draft",
  "sort": null,
  "user_created": "cd49aecf-e351-4ec9-ab4f-4ff710e2ced2",
  "date_created": "2023-10-02T10:07:00.528Z",
  "user_updated": "cd49aecf-e351-4ec9-ab4f-4ff710e2ced2",
  "date_updated": "2023-10-04T11:27:23.732Z",
  "title": "Home Page",
  "slug": "home-page",
  "content": [
    1,
    3,
    4
  ]

All fields from related collections are missing.
All the collections have public read permissions without limitations at this point.
I'm wondering if this is an issue with an error in Directus Docs or this module bug.
Version
nuxt-directus
nuxt:

is there a workaround for that for now?

Hello,
Fields need to be specified as an array of strings.
example:
fields: [ '*', "content.*","item.*" ],


chore: update plugin-tailwindcss test filename

Summary

🤖 Generated by Copilot at 7b929b3
Renamed a test file to match the name of the macro it tests. Updated the import statements and references to the tailwind macro in the test cases.
Details

🤖 Generated by Copilot at 7b929b3

Rename utils.test.ts to macro.test.ts to reflect the usage of the tailwind.macro function (link)

Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

Please update the snapshot 😄


EXSWHTEC-284 - Implement tests for square/cube root device math functions

Depends-on: #260

Accuracy tests for single-precision and double-precision sqrt/rsqrt/cbrt/rcbrt/hypot/rhypot/norm3d/rnorm3d/norm4d/rnorm4d
Sanity tests for single-precision and double-precision norm/rnorm
Negative tests for single-precision and double precision square/cube root math functions

Related to my first comment, I would like to request that these reviews be reorganized into smaller pieces starting with core test infrastructure changes and followed by reviews for each new added test or highly related family of test.  Ideally the core changes would have been approved before new test development, but now any core changes needed will have to be propagated to all the tests. Ideally an individual review would touch no more than 3-4 files and fit on no more than 2-3 screens.

@b-sumner Thank you for your review. We tried to do exactly that by creating #233 , all the PRs (including this one) contain these common core files, but as the core PR is not yet merged it is hard to go through each of them to find specific files that are not core files. In this PR those are root_funcs.cc with main implementation for root and cubic math functions and math_root_negative* which are used to simply check if compilation fails when functions arguments are of invalid type (that same approach has been used in atomic PRs).

#233 has 17 files which by itself is a concern.  And including them in every subsequent review is a bigger concern.  This review process would have gone more smoothly if you could restrict to a handful of files and wait for merge to submit the next handful.  What we have now with several reviews each with 15+ files, some of which may or may not be identical is a problem so I would like to back up and try again with the smooth approach.

@nives-vukovic : Could you please look into splitting this PR into smaller ones so that it can be reviewed easily?

@mangupta This PR depends on PR #260, which is also chained with another PRs. When all PRs in the dependency chain are approved and merged, this PR will not be very big and will be simple to review. All math PRs have a common base which is large, therefore this was the only viable approach.

PR has been merged into develop branch via commit 46ada257307db5e604948478b6325092121e29c1.


Obsolete command?

Typing this command: dotnet new webapp -o aspnetcoreapp
Results in: No templates matched the input template name: webapp.
I think webapp should be replaced with 'web'? or 'mvc' or 'razor'

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

ID: ca6139d4-022c-395a-0abf-539660550df1
Version Independent ID: 3dd23f8a-300e-3f78-1dc5-8b759aabdccc
Content: Get started with ASP.NET Core
Content Source: aspnetcore/getting-started/index.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Nevermind... I am on 2.1.201... apparently I need 2.1.300


[BEAM-6286] Add SamzaRunner profile to mvn archetype

Seems this was lost during the conversion to gradle a while back. Add this back.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


Model Integration

Hello everybody!
I wish to add a vehicle model that I built on my own into the compiled version of Carla.
Is there a way to do it, since differently from the source there is no human-like interface?
Thanks in advance.

Thx! Waiting for your integration of pedestrians in Carla source!


Segmentation fault in Eigen::internal::InnerMostDimReducer<...>::reduce when passing large tensor to sparse_softmax_cross_entropy_with_logits

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): I have written custom code. A simple reproduction script is included below.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04 (also occurring on Linux Ubuntu 14.04)
TensorFlow installed from (source or binary): TensorFlow installed from binary (also occurring after building from source)
TensorFlow version (use command below): TensorFlow v1.6 (also occurring on v1.4, v1.5, v1.7rc0)
Python version: Python 2.7 (Ubuntu base and also occurring on Anaconda Python 2.7)
Bazel version (if compiling from source): Bazel version: 0.11.1
GCC/Compiler version (if compiling from source): GCC 4.9.4
CUDA/cuDNN version: CUDA not used, CPU only
GPU model and memory: GPU not used, CPU only (Intel(R) Xeon(R) CPU E5-2650 and Intel(R) Xeon(R) Platinum 8175M)
Exact command to reproduce: Command to reproduce using script given below: "python sfi.py 300000"

Describe the problem
A segmentation fault is occurring with the following gdb backtrace when a "logits" tensor of sufficient size is passed to sparse_softmax_cross_entropy_with_logits. The single argument to the demonstration code below adjusts the size. I have found that there is a point below which the SegFault does not seem to ever occur and above which the SegFault always seems to occur, but around that point (e.g. within +/- 2) the SegFault behaviour is intermittent. Right on the change point I can run the same code with the same argument and it will sometimes generate a SegFault and sometimes not (though the random data generated in the demo code may be causing this randomness).
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffcdffb700 (LWP 2440)]
0x00007fffef12a590 in Eigen::internal::InnerMostDimReducer<Eigen::TensorEvaluator<Eigen::TensorReductionOp<Eigen::internal::MaxReducer<float>, Eigen::IndexList<Eigen::type2index<1l>> const, Eigen::TensorMap<Eigen::Tensor<float const, 2, 1, int>, 16, Eigen::MakePointer> const, Eigen::MakePointer> const, Eigen::ThreadPoolDevice>, Eigen::internal::MaxReducer<float>, true>::reduce(Eigen::TensorEvaluator<Eigen::TensorReductionOp<Eigen::internal::MaxReducer<float>, Eigen::IndexList<Eigen::type2index<1l>> const, Eigen::TensorMap<Eigen::Tensor<float const, 2, 1, int>, 16, Eigen::MakePointer> const, Eigen::MakePointer> const, Eigen::ThreadPoolDevice> const&, int, int, Eigen::internal::MaxReducer<float>&) ()
   from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
(gdb) bt
#0  0x00007fffef12a590 in Eigen::internal::InnerMostDimReducer<Eigen::TensorEvaluator<Eigen::TensorReductionOp<Eigen::internal::MaxReducer<float>, Eigen::IndexList<Eigen::type2index<1l>> const, Eigen::TensorMap<Eigen::Tensor<float const, 2, 1, int>, 16, Eigen::MakePointer> const, Eigen::MakePointer> const, Eigen::ThreadPoolDevice>, Eigen::internal::MaxReducer<float>, true>::reduce(Eigen::TensorEvaluator<Eigen::TensorReductionOp<Eigen::internal::MaxReducer<float>, Eigen::IndexList<Eigen::type2index<1l>> const, Eigen::TensorMap<Eigen::Tensor<float const, 2, 1, int>, 16, Eigen::MakePointer> const, Eigen::MakePointer> const, Eigen::ThreadPoolDevice> const&, int, int, Eigen::internal::MaxReducer<float>&) ()
   from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#1  0x00007fffef12a90f in Eigen::internal::EvalRange<Eigen::TensorEvaluator<Eigen::TensorAssignOp<Eigen::TensorMap<Eigen::Tensor<float, 1, 1, int>, 16, Eigen::MakePointer>, Eigen::TensorReductionOp<Eigen::internal::MaxReducer<float>, Eigen::IndexList<Eigen::type2index<1l>> const, Eigen::TensorMap<Eigen::Tensor<float const, 2, 1, int>, 16, Eigen::MakePointer> const, Eigen::MakePointer> const> const, Eigen::ThreadPoolDevice>, int, true>::run(Eigen::TensorEvaluator<Eigen::TensorAssignOp<Eigen::TensorMap<Eigen::Tensor<float, 1, 1, int>, 16, Eigen::MakePointer>, Eigen::TensorReductionOp<Eigen::internal::MaxReducer<float>, Eigen::IndexList<Eigen::type2index<1l>> const, Eigen::TensorMap<Eigen::Tensor<float const, 2, 1, int>, 16, Eigen::MakePointer> const, Eigen::MakePointer> const> const, Eigen::ThreadPoolDevice>*, int, int) () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#2  0x00007fffedcd5541 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#3  0x00007fffedcd5511 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#4  0x00007fffedcd5511 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#5  0x00007fffedcd5511 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#6  0x00007fffedcd5511 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#7  0x00007fffedcd5511 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#8  0x00007fffedcd5511 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#9  0x00007fffedcd5511 in Eigen::ThreadPoolDevice::parallelFor(long, Eigen::TensorOpCost const&, std::function<long (long)>, std::function<void (long, long)>) const::{lambda(long, long)#1}::operator()(long, long) const () from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#10 0x00007fffebcecb70 in Eigen::NonBlockingThreadPoolTempl<tensorflow::thread::EigenEnvironment>::WorkerLoop(int) ()
   from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/../libtensorflow_framework.so
#11 0x00007fffebceb8e2 in std::_Function_handler<void (), tensorflow::thread::EigenEnvironment::CreateThread(std::function<void ()>)::{lambda()#1}>::_M_invoke(std::_Any_data const&) ()
   from <home_dir>/.conda/envs/research/lib/python2.7/site-packages/tensorflow/python/../libtensorflow_framework.so
#12 0x00007fffe20355b0 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#13 0x00007ffff77e7184 in start_thread (arg=0x7fffcdffb700) at pthread_create.c:312
#14 0x00007ffff6e0703d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

The problem occurs in all of these configurations:

Binary CPU-only install of TF: v1.4, v1.5, v1.6, and v1.7
Build from source code: v1.6, v1.7
Building with MKL and without MKL
Ubuntu Python and Anaconda Python (but only Python 2.7 in both cases)
In clean virtual/conda envs with only the minimum TF dependencies installed

Source code / logs
I've been able to distil the problem down to the following code which reliably reproduces the problem for me on my local hardware and also on a m5.2xlarge EC2 instance running Ubuntu 16.04 Server or Amazon Linux. The following code has no external data or code dependencies other than tensorflow.
The script has a single argument which sets the "vocabulary size" (this was originally an RNN LM); if this value is large enough a SegFault occurs. The only operation of note is the sparse_softmax_cross_entropy_with_logits.
#!/usr/bin/env python
from __future__ import absolute_import, division, print_function, unicode_literals
import sys
import tensorflow as tf

def main():
    vocabulary_size = int(sys.argv[1])
    batch_size = 256
    step_size = 32

    print("Vocabulary size:", vocabulary_size)

    labels = tf.get_variable("labels", shape=[batch_size, step_size], dtype=tf.int32)
    logits = tf.get_variable("logits", shape=[batch_size, step_size, vocabulary_size])
    costs = tf.nn.sparse_softmax_cross_entropy_with_logits(labels=labels, logits=logits)

    with tf.Session() as session:
        session.run(tf.global_variables_initializer())

        print("Executing...")
        session.run(costs)
        print("SUCCESS!")

if __name__ == "__main__":
    main()

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

I have updated the issue to use the template headings. Hopefully this is now correctly viewed as complete.

I've updated the issue after discovering that the only operation needed to generate the SegFault is sparse_softmax_cross_entropy_with_logits.

I've tried compiling with the latest version of Eigen but the SegFault still occurs.

I've been unable to fix this problem directly so I'm now using a workaround. I believe these two functions are equivalent as long as logits is of rank 3. Thankfully, the alt function does not appear to be any slower.
def base_sparse_softmax_cross_entropy_with_logits(logits, labels):
    return tf.nn.sparse_softmax_cross_entropy_with_logits(labels=labels, logits=logits)

def alt_sparse_softmax_cross_entropy_with_logits(logits, labels):
    log_softmax = tf.nn.log_softmax(logits)
    logits_shape = tf.shape(logits)
    y, x = tf.meshgrid(tf.range(logits_shape[1]), tf.range(logits_shape[0]))
    indexes = tf.stack([x, y, labels], axis=-1)
    return -tf.gather_nd(log_softmax, tf.cast(indexes, tf.int64))

While developing that alternative code I found I needed to cast the indexes to int64 since the total number of elements exceeded 2**31 and this caused gather_nd problems. I wonder whether this is actually the cause of the problem in tf.nn.sparse_softmax_cross_entropy_with_logits; is it assuming the total number of elements is less than 2**31?

@ebrevdo, can you take a look?

I tried changing the dtype of the labels passed to tf.nn.sparse_softmax_cross_entropy_with_logits to be tf.int64 instead of tf.int32 but the problem remains.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

I think we optimize using int32 indexing. We could change this to int64 on
the CPU path maybe.
On Sat, Apr 21, 2018, 11:27 AM Alfred Sorten Wolf<EMAIL_ADDRESS>wrote:

Nagging Assignee @ebrevdo https://github.com/ebrevdo: It has been 14
days with no activity and this issue has an assignee. Please update the
label and/or status accordingly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/17783#issuecomment-383318472,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim-ou72GLufRcPF-kC26N1Y4TwH-kks5tq3n_gaJpZM4SuZnL
.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 34 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 49 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 64 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 79 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 94 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 109 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 124 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 139 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 154 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 169 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 184 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 199 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 214 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@qtdaniel
You are using an older version of tensorflow which is not actively supported now, please try to upgrade to the latest TF versions.
I tried to replicate the issue on colab using TF v2.8.0 and faced the following error:
ValueError                                Traceback (most recent call last)
[<ipython-input-1-68f3af6bcb7f>](https://localhost:8080/#) in <module>()
     24
     25 if __name__ == "__main__":
---> 26     main()

[<ipython-input-1-68f3af6bcb7f>](https://localhost:8080/#) in main()
      5
      6 def main():
----> 7     vocabulary_size = int(sys.argv[1])
      8     batch_size = 256
      9     step_size = 32

ValueError: invalid literal for int() with base 10: '-f'

Please refer to this gist. Thank you!

https://instagram.com/w0ssh?igshid=YmMyMTA2M2Y=

@sushreebarsa Thanks. I think you are right, this does appear to be fixed in TensorFlow 2.7. But note that the error you reported from Colab is not related to the original issue, it is related to passing the wrong arguments to the script. You need to pass 300000, not -f. The reproduction command is python sfi.py 300000 but the original code will not work with TF 2+. If the code is upgraded to work with the v1 compatibility API in v2 then the original error is not reproduced. I get an out-of-memory error but that's because the tensor it is trying to create is just too big for my machine; I am not currently able to test it on a machine with more memory.


stop spamming me with "servers stopping" messages

it's highly unusual for IRC servers to send a PRIVMSG to every user connected when it shuts down... at most there will be a WALLOP warning people of the reason behind the operation, and that's less intrusive: it's usually bound to a specific window and won't bring as much attention as a direct message.
i don't quite care if the server stops. i will notice through usual means, which is a warning in my status window. since i'm connected to the IRC bridge, I'm seeing this message about once a day, and it's pretty annoying.
i don't know if this will resolve it, I haven't tested this. but i hope it will.

i don't know if this will resolve it, I haven't tested this. but i hope it will.

not really doing to merge something without any form of testing...

Merging #65 would also change the annoying PRIVMSGs to a much more rational ERROR message.

ah that seems sufficient then, let's go with #65...
i was just scratching an itch here.


 This was written for 2.7

But you have used "import asyncio" which throws exceptions on python (2.7).

Looks like the kademlia package I used has since been updated to python 3 and now uses asyncio. You'll have to either hunt down the older version of the kademlia package, or update the code for use with python 3. I haven't worked on this project in a few years, and have no reason to update it, but feel free to make changes and submit a pull request if you'd like. From a quick glance, it looks like this is the last version of kademlia before the switch to asyncio.

You just need to mention the following requirements in the readme:
Python == 2.7
kademlia == 0.4
rpcudp == 2.1
Everything else works fine. One more thing, Did you ran all the VM's server.tac on <IP_ADDRESS>:8468? I'm currently able to ping every machine from every other machine but I don't know if they are connected after running their scripts because no sign of other machine's ip is visible in one machine's log that is being created in command window.

Feel free to add a requirements.txt for an easy pip install. Again, this was a school project from a few years ago so I don't really have an incentive to work on it anymore. The code is available for you to do with as you please.
As for the server.tac, it only needs to be run on 1 of the 3 or more vms. It's acting as a kademlia network for the others to connect to until they've contacted the dht. I haven't run this in a while but I think I ran the server.tac on localhost (<IP_ADDRESS>:8468) which i believe is hardcoded into the file. Then when connecting to the network on the commander and clients, you'll need to specify the ip of the vm that they see on their network. Might have to adapt firewall rules to make sure the port is open.


MB-5838 - Remove local ecs-service-logs with upstream version

Description
Explain a little about the changes at a high level.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
echo "Code goes here"

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Messages

:book:
:link: MB-5838

  Generated by :no_entry_sign: dangerJS against 39c055129b2a26711d4e6799fb791f0a1870d898

Messages

:book:
:link: MB-5838

  Generated by :no_entry_sign: dangerJS against 39c055129b2a26711d4e6799fb791f0a1870d898


update Chinese translation

I fixed some problems in the Chinese translation files. Also improved readability in Chinese.

可恶啊，被你抢先了🤣

可恶啊，被你抢先了🤣

快你一步😆


Implement filter pushdown for SQLite

What should be done?
We should support the same filter pushdowns as we currently support for PostgreSQL.
We should integrate it with explain.
We also should investigate how we should change our tests to make it easier for new backends: currently, they expect all backends to support the same pushdowns.
Where?
SQLite backend and handler.
Definition of Done

handler updated;
unit tests added/updated;
integration/compatibility tests added/updated;
spot refactorings done;
user documentation updated.

We probably should do refactorings from #3337 plus pushdown of string for _id field only (because it can't be array).

On hold for now


Clicking on links in the issue description does not navigate to the page.

Issue
If one clicks on the provided link in the issue description it should take you to the required page but this feature is not there right now. I can work on this issue and make the required changes.

/assign


Allow skipping protostar upgrades

Closing. Protostar doesn't prompt the user like oh-my-zsh, but displays a notification.


Unclear number of control points for computing shape along centerline

Description
In sct_process_segmentation.compute_shape(), the shape is computed along the centerline by fitting NURBS with a given number of control points, which is 5x the number of slices in the image, as shown here: https://github.com/neuropoly/spinalcordtoolbox/blob/master/scripts/msct_shape.py#L249
I am wondering why shape isn't computed per slice, as it would be 5x faster, and also users are interested in the per-slice information (not the interpolated shape between slices).
@benjamindeleener could you please comment?

OK, my understanding is that we need to compute properties in the plane orthogonal to the cord centerline, and the decision to use 5x more points along the curve is to have a safe representation of the cord shape between two consecutive slices. Hence, the approach is to over sample, compute shape, and then average for each slice.

The number which is 5x times the number of slices in the images on this function is not the number of control points but the number of points in the NURBS. As demonstrated on the figure attached which is issued from the test data of the SCT Paris 2018 course :

The number of points provided by the centerline image is around 230 (red) and the fitting is done using the control points (green), the result (blue) has 5 times the number of slices of the original image (320 -> 1600).
As for the reason for why there is 5 times more points even though the shape is computed per slice, I think you were right when you said :

we need to compute properties in the plane orthogonal to the cord  centerline and the decision to use 5x more points along the curve is to have a safe representation of the cord shape between two consecutive slices. Hence, the approach is to over sample, compute shape, and then average for each slice.

Since in the code some properties are calculated based on the plane orthogonal to the spinal cord.
I would suggest de-linking this issue to #2038 because the later deals with the number of control points and not the sampling of the NURBS curve.

I would suggest de-linking this issue to #2038 because the later deals with the number of control points and not the sampling of the NURBS curve.

agreed

Whoops, I deleted my comment by mistake, as there is no way of retrieving deleted comments to my knowledge, for the sake of clarity I will re-write  it :
The number which is 5x times the number of slices in the images on this function is not the number of control points but the number of points in the NURBS. As demonstrated on the figure attached which is issued from the test data of the SCT Paris 2018 course :

The number of points provided by the centerline image is around 230 (red) and the fitting is done using the control points (green), the result (blue) has 5 times the number of slices of the original image (320 -> 1600).
As for the reason for why there is 5 times more points even though the shape is computed per slice, I think you were right when you said :

we need to compute properties in the plane orthogonal to the cord centerline and the decision to use 5x more points along the curve is to have a safe representation of the cord shape between two consecutive slices. Hence, the approach is to over sample, compute shape, and then average for each slice.

Since in the code some properties are calculated based on the plane orthogonal to the spinal cord.
I would suggest de-linking this issue to #2038 because the later deals with the number of control points and not the sampling of the NURBS curve.


js: Remove Container.replicate()

This has been removed from all of the blueprints we maintain,
so is now ready to be removed from Quilt. We're removing this
because the semantics of it are confusing, and it's easy for
users to loop to create many containers.

Also, food for thought for the CI/CD deployment for our docs -- this change should also trigger the docs to redeploy.

Oh, and when you're at it, can you also update the website example to quilt run ./meanExample.js instead of quilt run ./mean.js (https://github.com/quilt/mean/pull/10)?

I updated this and also the website: https://github.com/quilt-corp/quilt-website/pull/3

Fixed


RequiredKeysNotSet should tell me what was not set

It's a little annoying having to go back through code to figure out which of the required parameters was not set. It would be much more convenient if the error message would just tell me.

right? FFS what a hassle #38


Thinking in classes instead of vtbls?

What would a class-based approach look like?
Do we need to need to specify the size of a vtable at all? When I was calculating things, the only xref in a vtable is vf0. The next xref is generally the start of a new vtable. Is this the rule or just common? Do vtables continue past what look like xrefs to data (dwords, bytes, etc)?
@vtbl(0x14169AE50, size=3)  # Cycle through __dict__, basically treating this like an enum
class Component__GUI__AtkResNode(Component__GUI__AtkEventTarget):
    dtor = 1  # also lose the nice layout orientation of all the addresses in a line, unless we turn off formatting, aligning the = signs.
    ctor = 0x1404CC6B0"

@vtbl(0x14169AEC8)  # More verbose, harder to maintain?
class Component__Gui__AtkCollisionNode(Component__GUI__AtkResNode):
    @vfunc(1)
    def dtor(): ...
    @func(0x14053F820)
    def ctor(): ...

It looks like a class, but its still basically working the vtables. However the automatic sizing would open up some opportunities I think. Especially if we can identify the first vtbl object regularly. Then they could all be labled something dumb like vtbl_Unknown001.

vtbls should only be pointers to functions, and only index 0 should ever have xrefs, so yeah its possible to find the end of them automatically, unless the compiler is doing weird stuff. The xrefs are usually the ctor(s), the dtor(s), and any inlined ctors/dtors.
Btw I didn't mean Python classes. I meant we shouldnt be defining vtables, we should be defining (C++) classes/structs. This is because some classes have multiple vtbl trees due to multiple inheritance, and classes with no vfuncs have no vtbls, but still have functions that we would want to group with them logically.
class Client::Game::Character::BattleChara     class Client::Game::Character::Character         class Client::Game::Object::GameObject (vtbl 1) 0x1416C8150 (89 entries)         class Client::Graphics::Vfx::VfxDataListenner (vtbl 2) 0x1416C8418 (2 entries)
both those vtbls belong to the BattleChara class, one is the vtbl for the BattleChara->Character->GameObject chain and will have all the vfuncs for those classes, the other is just the VfxDataListenner vtbl. (Unrelated but 5.4 actually added a third class that ::Character derives from, so they have 3 vtbls now).
Anyway:

base class is responsible for defining function names for all vfuncs in their vtbl
derived class is responsible for defining function names for vfuncs added by that derived class
overrides can maybe be handled automatically if IDA has a script function to determine if something was already renamed by the user, otherwise we list them explicitly in derived classes (just need a number listing of functions overridden)

    vtbl 0x1416B0EC0
        count 78 // might not need counts
        function_names
            17 EnableDraw

class Client::Graphics::Vfx::VfxDataListenner
    vtbl 0x141698960
        count 2
        function_names
            1 Something

class Client::Game::Character::Character
    vtbl 0x1416B1B48
        base Client::Game::Object::GameObject
        count 89 // this means ::Character adds 11 new functions, since GameObject already had 78
        function_overrides // vfunc overrides, 'override' keyword in C++
            17 // function names for the first 78 can be pulled from base class GameObject automatically
        function_names // names for added functions
            80 Something
    vtbl 0x1416B1E10
        base Client::Graphics::Vfx::VfxDataListenner
        count 2
        function_overrides
            1, 2
    non_virtual_functions
        ctor 0x1406EA340 ```

this is all the data basically


Failures on [dtd] Use secure random number generator to generate URI auth code (path) and secret

There are new test failures on [dtd] Use secure random number generator to generate URI auth code (path) and secret.
The tests
pkg/dds/test/sse_smoke_test RuntimeError (expected Pass)

are failing on configurations
unittest-asserts-release-mac-arm64

This test went from Pass -> flaky on September 18, and the logs from September 18 (https://dart-ci.appspot.com/log/pkg-mac-release-arm64/unittest-asserts-release-mac-arm64/14520/pkg/dds/test/sse_smoke_test) show the exact same failure, so @jyameo's change did not cause any new failures.
https://dart-ci.web.app/#showLatestFailures=false&test=pkg/dds/test/sse_smoke_test&configurations=unittest-asserts-release-mac-arm64


signMessage and verifyMessageSignature now supports a binary message

Purpose
Support messages as Buffers (/Uint8Arrays) in signHelper's signMessage and verifyMessageSignature.
Changes
Expand the supported message type in signMessage and verifyMessageSignature to include Uint8Arrays.
Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[x] (If necessary) I have updated the CHANGELOG.

I like the sneaky fix as well :)

Yeah, I ran into it myself this time. :upside_down_face:

If I understand correctly the wallet API will handle the schema and display of the parameter, right? This is just the core SDK function.

Yes, exactly, I just wanted to fix it here, instead of doing a weird workaround in the wallet.


ENH: set color for bad channel with spatial_colors=True

Closes #12137
@hoechenberger can you try it with your data to see if it helps?
This will affect at least evoked.plot and spectrum.plot as spatial_colors=True by default.

[ ] See if it actually helps with reports
[ ] Add test
[ ] Add changelog entry

@larsoner i don't know when I'll will have time to test this, don't wait for me 🥹

On main:
import mne
raw = mne.io.read_raw_fif(mne.datasets.sample.data_path() / "MEG" / "sample" / "sample_audvis_filt-0-40_raw.fif")
raw.pick("eeg", exclude=()).load_data()
raw.plot_psd(exclude=())

gives:

On this PR it's:

There is a bug on main where bad_ch_idx=[] so the dashed-ness was never applied. But I like that in this PR that is applied and it's gray -- I think it works well.
With the gray we could consider getting rid of the dashing which makes the bad one easier to resolve:

I like the last figure you posted!

Ready for review/merge from my end.
When I modified the Report tutorial with dashing turned off it looked like this. So I decided in the end to keep it to make it slightly more differentiable.