RUM (Real User Monitoring) ?

Does the Jaeger tracing ecosystem provide something like Elastic APM RUM ?

The page you link has practically zero information about what exactly E-APM supports w.r.t. RUM. It sounds more like metrics.

Sorry, these provide better info:
https://www.elastic.co/guide/en/apm/agent/rum-js/master/intro.html
https://www.elastic.co/blog/performing-real-user-monitoring-rum-with-elastic-apm
https://github.com/elastic/apm-agent-rum-js

Thanks for the links. The blog still sounds pretty confusing as to what exactly they are trying to do. You can certainly get traces into Jaeger like the ones they showed, if you instrument your frontend application. Jaeger itself does not provide instrumentation (it's not in the scope of the project), but you can use OpenTelemetry which has good support for JS and is natively integrated with Jaeger. As far as user activity metrics, and dimensions like geo locations - that's not what Jaeger is built for, I would point you to Grafana and Prometheus.


Move to symmetric data encryption from asymmetric encryption

Following configuration properties has to be included in carbon.xml.

true
AES
symmetric.key.value

Need to create a file named "symmetric-key.properties" in CARBON_HOME/repository/resources/security path and write the symmetric key in plain text or the secret alias, if using secure vault for encrypting the symmetric key.
Ex: symmetric.key=secretAlias:symmetric.key.value

Carbon Jira: https://wso2.org/jira/browse/CARBON-15662

Reviewed. Can merge.

Test Case : https://github.com/wso2/product-is/pull/345/commits

Doc Jira : https://wso2.org/jira/browse/DOCUMENTATION-2768

Reviewed. Can merge.

Test Case : https://github.com/wso2/carbon-kernel/pull/707


[KAITO VS Code Experience]

Describe the bug
when running a test query on successfully deployed phi-3-mini-4k-instruct, i get the following output
Error executing curl command: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 curl: (7) Failed to connect to localhost port 64063 after 2224 ms: Could not connect to server curl: (3) unmatched brace in URL position 17: generate_kwargs:{temperature:0.5, ^

Mention the platform you are using
windows 11 vscode
To Reproduce
Steps to reproduce the behavior:

Go to Kaito, install Phi-3-mini-4k
Click on "test"
error appears

Expected behavior
get the response from the model
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

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

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Fixed in PR #1106

❤ Thank you so much for this! under this work: https://github.com/Azure/vscode-aks-tools/pull/1106 this specific issue will be fixed by next release, fyi and cc: @tejhan !! Thanks all, leaving this to open until we release new version sometime next week please.


ref: use guard-collection

tests have been adjusted
checkhealth now only checks for executables since conf_not_found is handled in filetype.lua
updated docs

@glepnir Is this pr ready?


Add Daemonset test logic in TestGetReplicasFromRuntimeObject

And also fix the usage of DefaultUnstructuredConverter.FromUnstructured()
Ref #790
/assign @mm4tt

/lgtm
/approve
Thanks a lot for the fix and tests!

/ok-to-test


$hashAlgorithm must be string, null used

hello
i try shield in my project and i have this error
`CodeIgniter v4.2.1 Command Line Tool - Server Time:
An uncaught Exception was encountered
Type:        TypeError
Message:     Typed property CodeIgniter\Shield\Config\Auth::$hashAlgorithm must be string, null used
Filename:    C:\wamp64\codeigniter4\vendor\codeigniter4\framework\system\Config\Factories.php
Line Number: 126`

Hello, what is the set value of public string $hashAlgorithm
in file app/Config/Auth.php?
Please set
public string $hashAlgorithm = PASSWORD_DEFAULT;

If the problem is not solved, please provide more about the PHP version,Sheild version, how to install and etc?

yes $hashAlgorithm is PASSWORD_DEFAULT
PHP: 7.4.0 — CodeIgniter: 4.2.1
shield 1.0 beta
maybe it is a issue with codeigniter4/settings 2.1


website 2.0

add password strength meter like this
add 2-factor auth - this might be useful

closing since moving future looking stuff to trello


Patch to make Strategy compatible with splatfacto

This is because nerfstudio uses (N,1) for opacity, and gsplat uses (N,).
I don't think this should affect gsplat functionality, but I haven't tested so if someone else could that'd be great!

Right! Sorry that I forgot about this!
I changed the squeeze to flatten to avoid the shape error in the extreme case where there is only a single gaussian.
Also modify a few more places.
This seems to be good but not tested.


Cannot set self-hosting url using command line argument and hosting.json

"dotnet run -serverurl http://xyz:5000" or
"siteapp.exe -serverurl http://xyz:5000" does not work. Neither does ""server.urls": "http://xyz:5000/"" in hosting.json. Only "UseUrls("http://xyz:5000")" in code works.

Share your Program.Main and and your hosting.json file. The command line should be server.urls not serverurl.

@Tratcher  server.urls does not work for me.

Program.Main and hosting.json:
public static void Main(string[] args)
{
var application = new WebHostBuilder()
.UseDefaultHostingConfiguration(args)
.CaptureStartupErrors(true)
.UseKestrel()
//.UseUrls("http://.:5000")
.UseIISIntegration()
.UseStartup()
.Build();
			application.Run();
	}//public static void Main(string[] args)

{
"server": "Microsoft.AspNetCore.Server.Kestrel",
"server.urls": "http://wdwin10:5001/"
}

I think you need two dashes - so it should be --server.urls

@cwe1ss Same result.

I missed that you use dotnet cli.
Try dotnet run -- --server.urls http://...
See docs for more details.

@cwe1ss Not this one either. But I got the command line figured out. Here is:
dotnet run /server.urls http://.:8000
Aslo hosting.json is now working after the app rebuilt.


Consider adding 'learning or memory' - for cases where it's not clear which is affected.

CC @aoifelarkin - could you add some examples?

I reckon this might not happen enough to be worthwhile for an extra CV term, so am happy to close the ticket.


I have added instructions for how to download the nightly artefact from Azure

Can you please rebase (and squash) your patch?

I believe I have have incorporated your feedback and squashed the commits as you requested. Thank you for your patience whilst I have been learning features of git unfamiliar to me.


istio DeleteCollection operation fails can't return error

Bug description
	clusterConfig, err := clientcmd.BuildConfigFromFlags("", Kubeconfig())
	if err != nil {
		fmt.Println(err)
	}
	istio, err := versionedclient.NewForConfig(clusterConfig)
	err = istio.NetworkingV1beta1().Gateways("test").DeleteCollection(context.TODO(), metav1.DeleteOptions{}, metav1.ListOptions{})
	fmt.Println("===>", err)

The DeleteCollection operation will not return an error regardless of whether the resource exists.
[ ] Docs
[ ] Installation
[] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[x] Developer Infrastructure
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
[root@test-10 xxx]# istioctl version --remote
client version: 1.6.0
control plane version: 1.6.0
data plane version: 1.6.0 (3 proxies)

How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)
operator installation.

see

// DeleteCollection deletes a collection of objects.
func (c *gateways) DeleteCollection(ctx context.Context, opts v1.DeleteOptions, listOpts v1.ListOptions) error {
	var timeout time.Duration
	if listOpts.TimeoutSeconds != nil {
		timeout = time.Duration(*listOpts.TimeoutSeconds) * time.Second
	}
	return c.client.Delete().
		Namespace(c.ns).
		Resource("gateways").
		VersionedParams(&listOpts, scheme.ParameterCodec).
		Timeout(timeout).
		Body(&opts).
		Do(ctx).
		Error()
}

@howardjohn
I am trying to delete a resource that does not exist, but no error is reported.

I think this is purely a Kubernetes issue. I am not even sure its unintended behavior, really. Lets track in https://github.com/kubernetes/kubernetes/issues/95537


[xh]Add OracleDB Destination

Tests
Tested with S3 source, destination is oracle DB.
Scenarios tested:

It can create table and export data.
If table already exists, it can export data directly.
If table schema is different, it can alter table
If insert data with unique keys or not and can update records if duplicated unique key records found with SQL/PL command.

Screenshot of the created table, exported records:

Screenshot of the alter table schema:

cc:
@wangxiaoyou1993 @dy46

Could you add the README file?

Updated this PR and tested with Postgres source with Array type and Json type column.
For array type, the varray in oracle is a user defined collection type. Every time user needs to define such an array type CREATE TYPE my_personal_type AS VARRAY(10) OF VARCHAR2(80); with customized name my_personal_type. It shows my_personal_type when we read it. It is tricky to know the exact type. Currently I use a CHAR(255) type to convert array.
For json type, it is supported in this PR with customized convert_column_to_type function to convert to NCLOB type in Oracle.
Screenshots for the test table input and output:
int array input table:

int array output table:

Text array and Json column input table:

Text array and Json column output table:

PTAL @wangxiaoyou1993


prune command failing with --cwd

What version of Turborepo are you using?
1.2.5
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Mac
Describe the Bug
--cwd command not working.
Expected Behavior
--cwd command works
To Reproduce
Run
turbo prune --scope=rs-frontend --docker --cwd=./out/rs-frontend

Getting
ERROR  package.json: open /Users/dev/monorepo/out/rs-frontend/package.json: no such file or directory
I upgraded from 1.1.2 to 1.2.5 and the --cwd command is no longer working for me.

--cwd is intended for setting the root of the monorepo when turbo is being run in a different directory. In this case, it does not set the output of turbo prune. The output directory is currently always going to to be <monorepo root>/out

I rely on this behaviour (setting unique --cwd) to build docker containers concurrently (see https://github.com/ewnd9/node-grpc-micro-services-demo/blob/436e5b59171b2a955aef098d505f9ac14d70f530/packages/shared/tooling/src/turbo-docker.ts#L27<EMAIL_ADDRESS>@gsoltis Is there any workaround?


.net "No such host is known" using DNS Service on standalone cluster

Hi,
using DNS Local SF Service on standalone cluster (6.0.216) from a .net application we get several times (but not constantly) "No such host is known" as shows at the attached screenshot.
The error does not appear when using normal nslookup.

Is this a know issue to you?
can you advise something? is there a workaround ?
kind regards
Yannis

I'ma having the same problem, I'm working behing an enterprise proxy. I tried the same http client code in a standalone asp.net core web api and it worked. When running in the local cluster, I always get "No such host is know". I tried disabling dnsService but it didn't help.

Got the same problem also. We're using the latest Service Fabric Cluster in Azure and this problem is still there. The "No such host is known" errors cluttered the error log when services are starting. Can someone from MS share the plan for this issue?

Still happening - Please resolve

Hi @dario-ms - we're also seeing this in SF clusters in Azure as well. The clusters are upgraded to the latest version. We've raised the issue with support and have been advised to increase DnsService.InstanceCount setting, which has been done, but the problem is still occurring. It does seem like this is the underlying cause, but there does not seem to be any activity on resolving this issue.
Is it possible to get an update?

Hi @dario-ms - we're also seeing this in SF clusters in Azure as well. The clusters are upgraded to the latest version. We've raised the issue with support and have been advised to increase DnsService.InstanceCount setting, which has been done, but the problem is still occurring. It does seem like this is the underlying cause, but there does not seem to be any activity on resolving this issue.
Is it possible to get an update?


Serving of the images not working properly

Hey,
thanks for the great library.
I ve got a problem with serving the right images:

// use it before declaring static routes
app.use(
  responsiveImages({
    debug: true,
    // options
    staticDir: '/upload',
    watchedDirectories: ['/upload/sellerProductImage'],
    directScaling: true,
    directScaleSizes: [200, 400],
  })
);

// sellerProductImages
const sellerProductUploadDirectory = path.join(__dirname, '../upload/sellerProductImage');
app.use('/upload/sellerProductImage', express.static(sellerProductUploadDirectory));

I can see that different sizes are generated, but the normal (not rescaled) images are being served, and i get the following in the log:
node_1      | express-responsive-images: (test.jpg) requested directory is in watchlist: /upload/sellerProductImage
node_1      | express-responsive-images: (test.jpg) requested file: test.jpg
node_1      | express-responsive-images: (test.jpg) filetype is supported: jpg
node_1      | express-responsive-images: (test.jpg) origin image does not exists

When i remove the staticDir in the configuration above, i get the following in the log:
node_1      | express-responsive-images: (test.jpg) requested directory is in watchlist: /upload/sellerProductImage
node_1      | express-responsive-images: (test.jpg) requested file: test.jpg
node_1      | express-responsive-images: (test.jpg) filetype is supported: jpg
node_1      | express-responsive-images: (test.jpg) cookie "screen" is set: density=2, width=320
node_1      | express-responsive-images: (test.jpg) new image width is probably 640
node_1      | express-responsive-images: (test.jpg) origin image is smaller than new image width
node_1      | GET /upload/sellerProductImage/test.jpg 200 34.391 ms - 22759

But when i do that, i dont get any image served at all in the browser - which is really odd.
Any help would be much appreciated!
Thanks.

Please try the following two steps. Perhaps the first one can fix it.

Set watchedDirectories: ['/sellerProductImage'] cause this options is already watching inside staticDir.

Are you sure about this line const sellerProductUploadDirectory = path.join(__dirname, '../upload/sellerProductImage');? Give it a try with this const sellerProductUploadDirectory = path.join(__dirname, 'upload/sellerProductImage');

The default value of staticDir is /public. So you should not delete it in your application.

Thanks for the quick reply!

i changed it, and now i am getting:

node_1      | express-responsive-images: (test.jpg) requested directory is not in watchlist: /upload/sellerProductImage

pretty sure that it's right like that, because i can see images like i described above with the first configuration. This is my folder-structure:

the code i am showing is located in app.ts

Since this is more a misconfiguration and not an issue by the module your question is related to stackoverflow. Please post your question there. I would be pleased to help you on SO.


Dead link in Managing-Threads-and-Custom-Services

Dead link in http://guides.codepath.com/android/Managing-Threads-and-Custom-Services#threading-glossary

Fixed, thanks.


Redirect to home when click on FlavorFusion title

Hi right now I believe the title is not properly redirecting back to the home page. I can fix this if I am assigned the issue, thank you.

I have just finished the code, please tag the issue with hacktoberfest-accepted, assign me, and I will be happy to create the PR! Thank you!


Plugin not showing zoom window when implemented on bootstrap modal

Hi
Following is code for modal

                <button type="button" class="btn btn-default" data-dismiss="modal" style = 'float : right;margin: 10px;' ng-click = 'resetBrightnessContrast()'>Close</button>

Following is the CSS
.large img.testlarge {
height : 2118px;
width : 1050px;
}
.small img.testlatge {
height : 1412px;
width : 700px;
}
Modal is initially not visible. But when I click a button a function is called from where modal is triggered to open using jquery
Just below that code I inserted code to initialize anythingzoomer
$("#zoomTiffFirsts").anythingZoomer({switchEvent: ''});
But when modal is opened, I am not able to see any image
Please help me with this
Regards

HTML Code for above thread

                <button type="button" class="btn btn-default" data-dismiss="modal" style = 'float : right;margin: 10px;' ng-click = 'resetBrightnessContrast()'>Close</button>

Hi @omkark!
I think you need to include a refresh of AnythingZoomer once the Bootstrap modal opens. Try this (demo):
$('#viewAlphaArrays').on('shown.bs.modal', function () {
    $("#zoomTiffFirsts").anythingZoomer();
});

I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue the discussion in this thread.


Could not resolve all files for configuration ':react-native-share:debugCompileClasspath'

Steps to reproduce

npm install --save react-native-share
react-native link react-native-share
follow instructions to do manual install and configuration
react-native run-andorid

Expected behaviour
Be able to compile and run without build errors
Actual behaviour
A long list of errors:
Could not resolve all files for configuration ':react-native-share:debugCompileClasspath'.

Could not resolve com.android.support:appcompat-v7:27.1.1.
Required by:
project :react-native-share
Cannot find a version of 'com.android.support:appcompat-v7' that satisfies the version constraints:
Dependency path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7:27.1.1'
Constraint path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7' strictly '27.1.1' because of the following reason: debugRuntimeClasspath uses version 27.1.1
Dependency path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7:27.1.1'
Constraint path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7' strictly '27.1.1' because of the following reason: debugRuntimeClasspath uses version 27.1.1
Dependency path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7:27.1.1'
Constraint path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7' strictly '27.1.1' because of the following reason: debugRuntimeClasspath uses version 27.1.1
Dependency path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7:27.1.1'
Constraint path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7' strictly '27.1.1' because of the following reason: debugRuntimeClasspath uses version 27.1.1
Dependency path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7:27.1.1'
Constraint path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7' strictly '27.1.1' because of the following reason: debugRuntimeClasspath uses version 27.1.1
Dependency path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7:27.1.1'
Dependency path 'myapp:react-native-share:unspecified' --> 'com.facebook.react:react-native:0.59.6' --> 'com.android.support:appcompat-v7:28.0.0'

Could not resolve com.android.support:support-annotations:27.1.1.
Required by:
project :react-native-share
Cannot find a version of 'com.android.support:support-annotations' that satisfies the version constraints:
Dependency path 'myapp:react-native-share:unspecified' --> 'com.android.support:appcompat-v7:28.0.0' --> 'com.android.support:support-annotations:28.0.0'

Environment
info
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 2.26 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.4.0 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 27.0.3, 28.0.2, 28.0.3
System Images: android-22 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.1 AI-173.4907809
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: ^16.8.6 => 16.8.6
react-native: ^0.59.6 => 0.59.6
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-cn-richtext-editor: 1.0.33
react-native-git-upgrade: 0.2.7
react-native-share version: "^1.1.3", also tried to get from master
package.json:
"dependencies": {
"@babel/polyfill": "^7.4.3",
"@babel/runtime": "^7.4.3",
"@pigzbe/react-native-stellar-sdk": "^1.0.6",
"autobind-decorator": "^2.1.0",
"axios": "0.18.0",
"ethers": "3.0.27",
"identicon.js": "2.3.2",
"mobx": "5.1.0",
"mobx-react": "^5.4.3",
"moment": "2.22.2",
"react": "^16.8.6",
"react-native": "^0.59.6",
"react-native-actionsheet": "^2.4.2",
"react-native-cached-image": "^1.4.3",
"react-native-camera": "^2.6.0",
"react-native-country-picker-modal": "^0.7.1",
"react-native-dropdownalert": "^3.10.0",
"react-native-elements": "^0.19.1",
"react-native-gesture-handler": "^1.1.0",
"react-native-jwt-io": "^1.0.3",
"react-native-keyboard-aware-scroll-view": "^0.8.0",
"react-native-linear-gradient": "^2.5.4",
"react-native-loading-spinner-overlay": "^1.0.1",
"react-native-modal": "6.5.0",
"react-native-permissions": "1.1.1",
"react-native-phone-input": "^0.2.1",
"react-native-picker-select": "^6.1.0",
"react-native-qrcode-svg": "^5.1.2",
"react-native-randombytes": "^3.5.2",
"react-native-reanimated": "^1.0.1",
"react-native-render-html": "^4.1.2",
"react-native-sensitive-info": "5.2.4",
"react-native-share": "^1.1.3",
"react-native-side-menu": "^1.1.3",
"react-native-snackbar": "0.5.0",
"react-native-svg": "^6.5.3",
"react-native-table-component": "^1.2.0",
"react-native-vector-icons": "^4.6.0",
"react-navigation": "^2.18.2",
"rn-fetch-blob": "^0.10.15",
"url": "^0.11.0"
},
"devDependencies": {
"@babel/core": "^7.4.3",
"@babel/plugin-external-helpers": "^7.0.0",
"@babel/plugin-proposal-class-properties": "^7.4.0",
"@babel/plugin-proposal-decorators": "^7.4.0",
"@babel/plugin-proposal-export-default-from": "^7.0.0",
"@babel/plugin-proposal-export-namespace-from": "^7.0.0",
"@babel/plugin-transform-runtime": "^7.4.3",
"babel-core": "^7.0.0-bridge.0",
"babel-eslint": "^9.0.0",
"babel-plugin-module-resolver": "^3.2.0",
"babel-plugin-require-context-polyfill": "^1.0.0",
"enzyme": "3.5.0",
"enzyme-adapter-react-16": "1.3.0",
"eslint-config-rallycoding": "3.2.0",
"jsdom": "12.0.0",
"metro-react-native-babel-preset": "^0.50.0",
"react-native-dotenv": "^0.2.0",
"react-native-mock-render": "0.1.1",
"react-test-renderer": "16.6.1",
"schedule": "^0.4.0"
},
"jest": {
"preset": "react-native"
}
Also tried to retrieve from:
"react-native-share": "git+https://github.com/react-native-community/react-native-share.git",
still got the errors.
Build.gradle file:
buildscript {
ext {
    buildToolsVersion = "28.0.3"
    minSdkVersion = 16
    compileSdkVersion = 28
    targetSdkVersion = 28
    supportLibVersion = "27.1.1" //27.1.1
}
repositories {
     google()
    jcenter()
}
dependencies {
    //classpath 'com.android.tools.build:gradle:3.1.4'
    classpath 'com.android.tools.build:gradle:3.3.0'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
google()
mavenLocal()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
// ADD THIS
maven { url 'https://maven.google.com' }
    // ADD THIS
    maven { url "https://jitpack.io" }
    maven {
      // Local Maven repo containing AARs with JSC library built for Android
      url "$rootDir/../node_modules/jsc-android/dist"
    }

}

}
subprojects {
afterEvaluate {project ->
// force libs to use recent buildtools
if (project.hasProperty("android")) {
android {
compileSdkVersion = 28  // change to match your desired version
buildToolsVersion = "28.0.3" // ....
}
}
}
}
task wrapper(type: Wrapper) {
gradleVersion = '4.4'
distributionUrl = distributionUrl.replace("bin", "all")
}
Link to repo (highly encouraged)
https://github.com/

Interesting - if I recall correctly react-native 0.59.6 was pulled. 0.59.5 is the actual latest react-native stable.
Your support libs are old
etc - please confirm the example works for you

is https://github.com/react-native-community/react-native-share/issues/492 related?

getting same error any solution??

I have this occur with react-native 0.60.0

Here I found a solution that has helped me


Add definition for Enumerable#filter_map

This method was added in Ruby 2.7.
See https://ruby-doc.org/core-2.7.1/Enumerable.html#method-i-filter_map.
Motivation
The filter_map method was added in Ruby 2.7 and was not made available in Sorbet. Using it causes errors.
Test plan
I added something. Does that test anything?

Related: https://github.com/sorbet/sorbet/issues/2390


Touchpadpressed bool keep pressed after release

Is reproducible in the example scene 002. Any advice how to fix it?

I'll look into a fix shortly

I'm sorry is related with the configuration of the enums in the controller Events script(with all of them in trigger works fine). I'll keep looking into it.

Fixed with https://github.com/thestonefox/SteamVR_Unity_Toolkit/commit/9bf7506fa65df13685abd91617c37b0d95a25a33


mobile ad networks, analytics, tracking

I was wondering if some of these domains might make the list.  I cannot find them on any of the typical blocklists out there but I see them constantly on my phone via NetGuard logs.
These just came from DNS requests from Lastpass, Netflix, Runtastic, Avast! antivirus, YouTube and a few other apps on my phone
med.heyzap.com
www.googleadservices.com
www.googletagmanager.com
secure.insightexpressai.com
<IP_ADDRESS> *.36a9.ip4.static.sl-reverse.com    (mixpanel.com analytics)
a.fiksu.com
api.segment.io
cdn.segment.com
dc.services.visualstudio.com    (Visual Studio analytics)
e.crashlytics.com    (found in many apps)
settings.crashlytics.com
mobile-service.segment.com
analytics-prod-ingress.bricknet.com
tags.otherlevels.com
admin.brightcove.com
app.adjust.com
fonts.googleapis.com
brahe.apptimize.com
md-a-c.apptimize.com
appload.ingest.crittercism.com
s.amazon-adsystem.com
device-metrics-us-2.amazon.com
14716.engine.mobileapptracking.com
stats.appsflyer.com
t.appsflyer.com
t.singular.net
control.kochava.com

Those Softlayer static.sl-reverse.com connections could come from Avast or others and are definitely tracking the user.

So... the way this repo works is, we aggregate actively curated lists of hosts that are involved, one way or another, in bad activity.
Maybe you could suggest these hosts to an organization that actively curates these lists?
If you would like to actively start curating a lists of hosts, then I'd be happy to include what you've got.
Closing.


PointingRelativeToScroll

where is this feature in the newest version? Its work like hold a button active mouse-scroll by pointing Y axis.

I think there's been a little more active discussion about this feature request in https://github.com/tekezo/Karabiner-Elements/issues/1074, although it hasn't led to a solution as yet.


Bitwarden: Unlocking the vault using the extension locks the vault for the script-commands

Extension – Bitwarden

Authors: @pomdtr, @jomifepe, @daniel-stoneuk

Description
When unlocking the vault with the "search vault" functionality of this extension, the vault is being locked for all bitwarden script commands.
Steps To Reproduce

Unlock your vault using the unlock script-command.
Use the bitwarden extension. E.g. the "Search Vault" command.
Try to run any bitwarden script-command. --> This will not work, as the vault is now locked for the scripts.

The expected behavior
The extension and the script-commands should work independent of each other.
Using the extension should not "block" the usage of the script-commands.
Raycast version
Version: 1.30.3

This is probably linked with the extension persisting the SESSION_ID from bitwarden. As soon as it generates a new one, it invalidate the one from the script commands, and vice-versa.
I'm not sure there is any solution to this except adding the script commands as extension commands.

Yea @pomdtr you're exactly right. Both the script commands and the extension use the same Bitwarden CLI tools to manage user sessions.
@MarcelBochtler The script command package and the extension were never intended to be used together; the extension was released after the script commands existed, when Raycast exposed the public extensions API. For the best user experience, the extension is the recommended source of truth these days (although the script commands should still work just fine on their own). If there are script command features that are missing from the extension, I'd recommend opening an issue and/or PR to have them added.

Thanks for the explanation.
The issue is not only that the extension does not work well with the script command package, it also does not work well with the bw CLI itself.
Whenever the extension was used, the CLI will be locked, which breaks any usage of it in scripts outside of Raycast.

The script command package and the extension were never intended to be used together

That is fine, I'd be happy to unlock the extension and the bw CLI separately.
Unfortunately, as of now, the extension basically blocks / interferes with the usage bw.

Bitwarden's CLI will look for a BITWARDENCLI_APPDATA_DIR environment variable to decide where to store it's own database. We could specify this in the extension code as the support path so that the data.json file used by the Raycast extension is different to the default. Unfortunately this would log everybody out of the extension, requiring re-entry of the master password.
@MarcelBochtler would you be happy with a workaround? One I've come up with (and tested) is as follows

Create an executable with the following contents

#!/bin/bash
export BITWARDENCLI_APPDATA_DIR="/Users/[username]/Library/Application Support/Bitwarden CLI Raycast/"
/usr/local/bin/bw $@

Create the directory above (Replace /usr... with /opt/homebrew/bin/bw if on M1)
Set the Bitwarden extension to use this executable in Raycast preferences

I can't confirm how secure this is, in particular if the bash script introduces any security issues. If you know a better way to run an executable with an environment variable please let me know!
If there's demand we could add a preference to the Bitwarden extension to set BITWARDENCLI_APPDATA_DIR - it would be a couple lines of changes, what do you think @pomdtr?

@daniel-stoneuk This is a smart idea, but it is not documented in the bitwarden API docs. So it could potentially break after updating the cli.
I have another idea. We could allow the user to set it's own BW_SESSION variable in the raycast pref. The user would then be able to share both in the script commands, the extension and the bitwarden cli.

I feel strongly that changes should not be made to encourage simultaneous use of both the script commands and the extension, especially if it would require confusing users with additional extension preferences that would rarely apply. I would rather see the extension updated to add any features enabled by the script commands that are currently missing.

I feel like using the extension should not stop you from using the cli.
Using a custom BITWARDENCLI_APPDATA_DIR location would isolate the extension, allowing you to use both. It sounds like the right solution to me.

Yes, I agree that that change should be made; the extension should be isolated so as not to interfere with CLI commands. My comment was in reference to:

I have another idea: we could allow the user to set it's own BW_SESSION variable in the raycast pref. The user would then be able to share it both in the script commands, the extension and the bitwarden cli.

I believe this change can and should be transparent to users.

This is a smart idea! It is not documented in the bitwarden API docs, so it could potentially break after updating the cli, but this is unlikely.

I've found a mention elsewhere in the bitwarden docs, so we should be good to use it! https://bitwarden.com/help/data-storage/#cli

Perfect !


Added Directory Fetching Logic through Github API

Description
Directory Fetching: Added logic to fetch directories from GitHub using Node.js and the GitHub API.
UI Enhancement: Implemented a card-style layout to display directories, with each card featuring a "View Repository" button.
Note:
This PR addresses the fetching part only,further improvement in the script and UI can be done as per requirements
Images -

Additional Context:
N/A

@MastanSayyad instead of obfuscating the github token i made a env file since we were allowed to use nodejs.
Obfuscated code can be decrypted so it was of no use to do that, i have made a simple express server which takes the github token from the env file and fetches the directories through github api
@sanjay-kv can you review the pr please

done @shreyash3087
can you publish the link to public.

@sanjay-kv i havent deployed it anywhere for now, we can do that after we are done with the whole website, also if anyone want to look at the website they can run it on localhost for now, there is a sample env file which i have provided where anyone can put there github token and remove the ".example" from "env.example" and run the express server on localhost to test the website. I havent provided my github token as we discussed about it with @MastanSayyad in #1135
@MastanSayyad should we make a readme file for other contributors so that they can setup the project easily in there local devices

sure

Hey @sanjay-kv Will this basic template be enough? As you said, we can add the necessary info and style it later (also I have on purpose added some bugs to see who identifies it tho it is easy to locate)


Tesseract couldn't load any languages!

Hi all,
I install qt box and do not know how to config to tessdata
Please help me
Log:
Failed loading language 'eng'
Tesseract couldn't load any languages!

Thanks

If you see "English" in language field (or any other language), than your configuration is correct.

@zdenop But it have problem:
Failed loading language 'eng'
Tesseract couldn't load any languages!
why does it fail ???
Thanks

where/when you have this error?
Dňa ut 14. 8. 2018, 3:27 kimchicanh<EMAIL_ADDRESS>napísal(a):

@zdenop https://github.com/zdenop But it have problem:
Failed loading language 'eng'
Tesseract couldn't load any languages!
why does it fail ???
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zdenop/qt-box-editor/issues/72#issuecomment-412722099,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjCzDaSsY9Qja6ZAWXxL84ylZpMuOSiks5uQieRgaJpZM4V6Og3
.


correct savepath

https://github.com/deepinv/deepinv/blob/43475b6d538ede8492c81e00a94dd7d8c14663fc/deepinv/training/trainer.py#L298
I just tried running a few examples on my local Windows machine (for testing) and get the error:
OSError: [WinError 123] The filename, directory name, or volume label syntax is incorrect: 'ckpts\\denoising/24-10-11-13:49:37'

I think this is due to the line above where the should be:
 str(self.save_path / f"{get_timestamp()}") if self.save_path else None

otherwise "/" is used as a path separator on Windows.

Hi @gschramm, thanks for raising this error. Looking at the filepath in the error you showed, it looks like there are colons in the directory name which are forbidden on Windows. However, deepinv.utils.logger.get_timestamp should use underscore instead of colons on Windows:
https://github.com/deepinv/deepinv/blob/43475b6d538ede8492c81e00a94dd7d8c14663fc/deepinv/utils/logger.py#L71
I think you are using an old version of the package, as this code was added in #183 and released in v0.2.1. Please can you pip install git+https://github.com/deepinv/deepinv.git#egg=deepinv and try again?

indeed. I didn't use 0.2.1 (installed from conda-forge) where 0.2.1 isn't available yet.


LTO for Android

Currently LTO for Android fails during the linking stage due to some incompatible DWARF versions between Rust and C++. We need to investigate how to fix this.

See:
[1]: https://stackoverflow.com/questions/58633287/force-lld-to-link-relocatables-that-use-debug-info-in-different-dwarf-versions
[2]: https://www.github.com/rust-lang/rust/issues/103057

We just ignore the warnings since they are immaterial to the correctness of the library.


Feature Request: be able to scan actions defined within a composite actions

Since composite actions are a alternative method to make the workflows more reusable, i think it would be good to add a way to check if the actions defined within have a new version.
Today, a composite action can be defined in two ways:

In a public repository
Then, can be used in a workflow like another Github Action in the marketplace (ex: uses: actions/checkout@v3). For this case, the version updater will work without problems.

In a private repository
For this case, you need to checkout the repo that contains the composite action using a PAT token. Then in the step, the action need be specified specified without the version (@x.x.x). The version of the composite action is determined by the ref input of the checkouted step of the composite action repo.

The problem is, in both cases, there is no way to check the versions of the actions used in the composite actions. Our projects uses a lot of these composite actions in the workflows. We used this approach because Github Actions does not support using reusable workflows from private repositores, only composite actions. There is a way to add this feature? Maybe scan the composite action file, instead of the workflow itself...
Thanks in advance.

I have an example:
# .github/actions/setup-poetry/action.yml (lines 1-25)
name: 'Setup Poetry'
description: 'Install and cache Poetry using pipx'
runs:
  using: "composite"
  steps:
    - name: Set pipx environment variables
      run: |
        echo "PIPX_HOME=${HOME}/.cache/pipx" >> $GITHUB_ENV
        echo "PIPX_BIN_DIR=${HOME}/.local/bin" >> $GITHUB_ENV
      shell: bash

    - name: Cache pipx poetry installation and binaries
      uses: actions/cache@v3
      with:
        path: |
          ${{ env.PIPX_HOME }}
          ${{ env.PIPX_BIN_DIR }}
        key: 1-${{ runner.os }}-pipx-poetry-${{ env.POETRY_VERSION }}

    - name: Install poetry
      run: |
        if ! pipx list | grep -q "package poetry ${{ env.POETRY_VERSION }}"; then
          pipx install poetry==${{ env.POETRY_VERSION }}
        fi
      shell: bash

This is then used like so:
# .github/workflows/lint.yml (lines 25-26)
- name: Setup Poetry
  uses: ./.github/actions/setup-poetry
  env:
     POETRY_VERSION: '1.6.1'


Release 1.1.0

[x] Create a branch for the release Branch "v1.1.0"
[x] Update the dependencies. The dependabot PR backlog is not comprehensive and doesn't include transitive dependencies, and merging them one at a time tends to break things, so the best way to do this is manually with npm. Done in PR #95
[x] Bump the intermineVersion in data-sources/intermine/api/index.ts if appropriate. Done in PR #67
[x] Update the base image version in the Dockerfile if necessary (this should be the most recent node LTS version) and do a test build and run of the Docker image on you local machine so you know if something is going to go off the rails before the automated build action on GitHub. Done in PR #98
[x] Update the GHCR image tag in compose.prod.yml to the imminent release version Done in commit 2a9f6812de0d86c97c9dbcfb74534383a49eac44
[x] Bump the "version" number in package.json. Done in  commit 881df8a8d5ce76d8b636b4058bc16908ba0d14bd
[x] Open a PR that merges the release branch into main. PR #99
[x] Merge the release PR after it passes testing and review.
[x] Tag a corresponding release on GitHub. This will trigger an automated Docker image build on GitHub. If the build succeeds it will be automatically published to GHCR.

Release v1.1.0 has been tagged and the Docker image was automatically built and uploaded to GHCR. Closing.


Color / Starred / Dormant / Archive mode

Description: Implement the following options in the study details view

[x] Ability to select a colour for the study
[x] Starr the study, so they are easily retrievable
[ ] Option to archive study in the study settings page
[ ] If in dormant stage, its ready to be deleted (send email at least a week before the study is permanently deleted)
[ ] If in archive mode, remove the study from the index and hide from the active views

@CS76, The ability to color and star study work fine but we don't have the option to delete/archive Study as of now.

It is also not clear what is the point of coloring as the color doesn't show up anywhere

Closing this in favour of #510 #509


Add aivoicegenerator.org

Hi, I'd love to add my free AI voice generator service to your awesome collection 🙂
AI Voice Generator's twitter username: @aivoicemaker

Thanks! adding 👍


Perf improvements

Hey,
Recently popped into this issue thread to discuss a fairly significant perf improvement idea, but found out @fabian-hiller had already done almost exactly the same thing!
However, I just finished a 4 hour plane ride and I spent the whole flight looking for more perf improvements and found a few!
Sizeable optimizations
Both of these generally just involved doing less whenever possible:

Evaluate full issue paths lazily instead of eagerly
Avoid creating PipeInfo objects when pipe.length === 0

I'd say these contributed 90% to the total performance improvement in this PR.
Micro-optimizations

Make cachedEntries for the object schema a flat array instead of an array of 2-tuples -- mainly just less indirection which is more friendly to the CPU.
Simpler "is object" check using input?.constructor === Object

Here are the results on my machine using typescript-runtime-type-benchmarks:
*** valibot @ current head of main, i.e. e6c53c8 ***
Running "parseSafe" suite...
Progress: 100%

  valibot:
    1 784 335 ops/s, ±1.51%   | fastest

Finished 1 case!
Running "parseStrict" suite...
Progress: 100%

  valibot:
    1 715 007 ops/s, ±0.15%   | fastest

-------------------------------------------

*** THIS PR ***
Running "parseSafe" suite...
Progress: 100%

  valibot:
    2 616 009 ops/s, ±0.21%   | fastest

Finished 1 case!
Running "parseStrict" suite...
Progress: 100%

  valibot:
    2 317 246 ops/s, ±0.25%   | fastest

This run amounts to +47% on parseSafe, +35% on parseStrict.

Thank you very much for your contribution! At the moment I have to focus on the text of my bachelor thesis. As soon as I have more time, I will check and merge your changes.

Just a quick notice about path if we're really trying to optimize the performance. Usually path is only needed in case of failures so that the path can be added to the issues. If this is the case, it can be allocated lazily only if the validation (or sub-validation) returns any issues instead of the current implementation where the path is allocated eagerly. This should yield some small performance improvements due to decreased number of allocations and gc overhead.
If the failure types are something like
type Issues = {
  pathItem: PathItem
  issues: (IssueErrorMessageAndMeta | Issues[])[]
}

Then the _parse function validation logic in failure cases becomes extremely simple:
// object validation pseudo
let issues: Issues[] | undefined
for each key in objectSchema {
  const result = parseKeySchema(object[key])
  if (result.issues) {
   (issues = issues ?? []).push(result.issues)
  }
}
return issues ? { valid: false, issues } : { valid: true, value }

Of course the issues structure (and paths along with it) must be flattened at the top level parse before returning the issues to the library user, but that should be very straightforward task to do (similar to the current getPath).
That said, I'm not familiar with this library or its features so take this with grain of salt... 😄

Yes, that is correct. Thank you very much for pointing it out. I will take it into account for the final implementation.

Yep that's a very good point, interested to see how much this speeds things up further

Thank you for your contribution! Due to my bachelor thesis I have a lot to do at the moment. I'll try to check the changes next week at the latest.

Thank you for your contribution! Due to my bachelor thesis I have a lot to do at the moment. I'll try to check the changes next week at the latest.

Sure, no pressure nor hurry, it's your library dude :) I just rebased and fixed the conflicts, nothing else.
If I have extra time I can try to find time to implement @milankinen 's suggested refactor as well, but it's kind of 50/50 whether I can find the time

Found an hour of idle time and started shoveling, looking pretty promising... :D
Removing previous results
Executing "valibot"
Loading "valibot"
Running "parseSafe" suite...
Progress: 100%

  valibot:
    3 657 558 ops/s, ±0.11%   | fastest

Finished 1 case!
Running "parseStrict" suite...
Progress: 100%

  valibot:
    3 213 696 ops/s, ±0.10%   | fastest

@milankinen you absolute GOAT! 🐐
I'm not quite finished with the refactor yet - must make sure all the tests pass and none of the public API is broken.

Can you explain why it is necessary to make a distinction between LeafIssue, NestedIssue and UnionIssue for the issues?

Can you explain why it is necessary to make a distinction between LeafIssue, NestedIssue and UnionIssue for the issues?

Sure! We can obviously iterate on the data model, but the idea in a nutshell is to accurately model the different kinds of objects according to the information that is actually relevant to each:
LeafIssue is an issue with a "primitive": the input was supposed to be a string, but was a number instead, or was supposed to be an object, but was a string instead (important to distinguish this from other issues with objects -- here the specific problem is that the input is not an object at all). So for these types of issues it makes sense to include input , message etc, but it does not include other issues, so they shouldn't be in its datatype. The primitive also doesn't really have to be aware of path -- a string is a string, the path is its containing parent's concern.

NestedIssue is an issue with a "composite": an input may be a valid object (i.e. it is not a string), but it can have e.g. the following problem: it should have contained key a of string, but a was a number instead. It's still a valid object, but something within its composition is wrong. More precisely, one or more sub-paths within this composite contained issues. Hence, it makes sense to include path and a list of issues from each subpath. Likewise, for maps and records, origin belongs here, but nowhere else, since origin is nearly always value.

Looking at the current implementation of NestedIssue, it should probably still have the validation property which I neglected to add. But does it need to have reason? The reason in the above example is that one of its child properties was not a string. So I'm thinking the reason belongs to the child, not the container.

UnionIssue was something that I identified as a special case: It's basically a "pathless" NestedIssue. Not 100% sure what to do with it. The current data model for it may well not be the right one.

Wow nicely done @jussisaurio 😮 👌!

Can you explain why it is necessary to make a distinction between LeafIssue, NestedIssue and UnionIssue for the issues?

Sorry my fault, separation was just my initial thought because of separation of concerns. 😅  It's not absolutely necessary to have different types of issues if the issues are flattened "in-place" in schemas. E.g. something like:
const createIssue = (msg: string) => ({msg, path: []})
const appendIssues = (issues: Issue[], childIssues: Issue[], pathItem: PathItem) => {
  issues.push(...childIssues.map(issue => issue.path.unshift(pathItem) && issue))
  return issues
}

// string.ts
if (typeof value !== 'string') {
  return createIssue('not a string')
}

// object.ts
if (result.issues) {
  issues = appendIssues(issues, result.issues, key)
}

I don't have time to think about it in detail at the moment. However, I want to keep the library as simple as possible, as this also reduces the bundle size, and splitting it into different issues seems a bit complicated. It is already possible to extract all important information with the current implementation, isn't it?
A path is still needed for a LeafIssue if it is in an object. Or can a LeafIssue not concern nested data? If so, the name is not optimal.
The only thing that would make sense to me would be:

RootIssue: Issue without path
NestedIssue: Issue with path
UnionIssue (special case): With sub-issues (stems from RootIssue or NestedIssue)

With the current implementation, the path is only constructed once an issue occurs, which is great. Does this lead to bugs with deeply nested issues? We may construct the path retroactively e.g. with path.unshift(…)? Then LazyPath would not be necessary, and the code would be simpler constructed or?

Tomorrow or Sunday, I will try to release a new version with all performance improvements. For time reasons (because of my bachelor thesis), I will then weigh whether I build on this issue or implement the ideas independently for the time being. I appreciate your contribution and will mention you in the release notes. 🤝

@fabian-hiller you are free to do what you like ofc :) the important point is the lazy construction of paths.
as you can see in the most recent commit i removed the LazyPath class entirely because its not needed at all. ParseInfo no longer contains path because it's only constructed when an issue actually arises. that is the key detail.
wish you the best with your thesis, those are a lot of work!

I don't have time to think about it in detail at the moment. However, I want to keep the library as simple as possible, as this also reduces the bundle size, and splitting it into different issues seems a bit complicated. It is already possible to extract all important information with the current implementation, isn't it?
A path is still needed for a LeafIssue if it is in an object. Or can a LeafIssue not concern nested data? If so, the name is not optimal.
The only thing that would make sense to me would be:

RootIssue: Issue without path
NestedIssue: Issue with path
UnionIssue (special case): With sub-issues (stems from RootIssue or NestedIssue)

With the current implementation, the path is only constructed once an issue occurs, which is great. Does this lead to bugs with deeply nested issues? We may construct the path retroactively e.g. with path.unshift(…)? Then LazyPath would not be necessary, and the code would be simpler constructed or?

And yes in the most recent commit the path is constructed retroactively in the flatten() function. In non flattened issues the path is only the key or the index, because nested issues have an issues array, which may have their own issues array, etc. So you can always build the full path string from those as necessary. Again, this was just my shot at the implementation, but it does avoid doing any extra work on the paths before an issue actually happens.
If you want you can play around with it in a branch to see how it works. But anyway, do whatever you think is best!

Thank you both for the research and ideas. Since I wanted to do a few things differently, I implemented it on my own and added you guys as co-authors. Feel free to check the result. You may see something we can do better.
The paths are now created lazy, and the pipeline is only executed when required. Also, I changed the object check to input.constructor !== Object.
However, I kept the previous implementation of cachedEntries because there was hardly any difference in performance in my test environment, and the code became more confusing with the new implementation.
The changes helped to improve performance by about 30% in my test environment. That's great! Thanks a lot!

Hey @fabian-hiller , nicely done! 🥳
I made a simpler version of the flat cachedEntries here, trying to be a bit more sensitive towards eventual bundle size and readability. It still gets a tad confusing in the objectAsync case.
Perf-wise: I'm still consistently getting a 6% perf boost using this strategy on typescript-runtime-type-benchmarks compared to current main, so feel free to throw it in at your discretion if you consider it a net win.

Thanks for the hint. For objectAsync I would probably leave it as is, but for object I can imagine the change. @naruaway can you check in your benchmark suite how the change affects performance?

I guess many of (similar) changes in this PR are already incorpolated in the latest main.
So I compared Make cachedEntries for the object schema a flat array instead of an array of 2-tuples -- mainly just less indirection which is more friendly to the CPU. part (I extracted out this part on top of the current main: https://github.com/naruaway/valibot/pull/1) against the current main.
And I ran the benchmark suite for the following commits on my MacBook Air (M2 chip):

latest-main: 00d234f4438250349d71d2cf154bef38649bc769 current main branch
use-flat-object-cache: bad8b32ed0d1bcab69cc901e6cbd82d7fb08a5ca I tried using speread operator on top of the main: https://github.com/naruaway/valibot/pull/1

Benchmark results

nodejs, deep, valid
  use-flat-object-cache : 1095916.5 ops/s (fastest, 5.2% faster)
  latest-main           : 1042200.5 ops/s
nodejs, many_features, invalid
use-flat-object-cache : 294343.5 ops/s (fastest, 1.2% faster)
latest-main           : 290939.5 ops/s
nodejs, many_features, valid
use-flat-object-cache : 1183446 ops/s (fastest, 3.8% faster)
latest-main           : 1140184 ops/s
nodejs, optional_nullable, valid
use-flat-object-cache : 798971.5 ops/s (fastest, 5.1% faster)
latest-main           : 760427.5 ops/s
nodejs, wide, invalid
use-flat-object-cache : 175466.5 ops/s (fastest, 2.2% faster)
latest-main           : 171669 ops/s
nodejs, wide, valid
use-flat-object-cache : 369301 ops/s (fastest, 5.6% faster)
latest-main           : 349862 ops/s
bun, deep, valid
use-flat-object-cache : 1814776 ops/s (fastest, 9.8% faster)
latest-main           : 1652201.5 ops/s
bun, many_features, invalid
use-flat-object-cache : 1224463.5 ops/s (fastest, 4.9% faster)
latest-main           : 1167401.5 ops/s
bun, many_features, valid
use-flat-object-cache : 1818182.5 ops/s (fastest, 9.1% faster)
latest-main           : 1666586.5 ops/s
bun, optional_nullable, valid
use-flat-object-cache : 1001718.5 ops/s (fastest, 15.0% faster)
latest-main           : 870855 ops/s
bun, wide, invalid
use-flat-object-cache : 494294 ops/s (fastest, 12.8% faster)
latest-main           : 438072 ops/s
bun, wide, valid
use-flat-object-cache : 685653 ops/s (fastest, 18.9% faster)
latest-main           : 576454.5 ops/s

Interestingly, in the above result, we see that this "flat cache" strategy consistently improves the runtime performance for both Bun and Node.js and the performance improvement is more significant for Bun (up to 18.9% for "wide, valid" case). We might want to consider merging this strategy as long as the maintainer thinks the code is readable & maintainable enough.

Thank you @naruaway. I will think about it.


Remove cyclic dev dependency with the parser crate

Summary
This PR removes the cyclic dev dependency some of the crates had with the parser crate.
Specifically, this PR does the following:

Remove ruff_python_parser as a dev dependency in ruff_python_ast

Move all of the test cases that depends on the parser from ruff_python_ast to ruff_python_parser

Remove ruff_python_parser and ruff_python_index as dev dependency in ruff_python_trivia

Move tests related to comment ranges from ruff_python_trivia to ruff_python_index. If it were to move to ruff_python_parser, then ruff_python_index would become a dev dependency on ruff_python_parser. This is problematic because ruff_python_index already has a direct dependency on ruff_python_parser.
Move other test cases from ruff_python_trivia to ruff_python_parser crate

Motivation
The main motivation for this PR is to help development. Before this PR, rust-analyzer wouldn't provide any intellisense in the ruff_python_parser crate regarding the symbols in ruff_python_ast crate.
[ERROR][2024-05-03 13:47:06] .../vim/lsp/rpc.lua:770	"rpc"	"/Users/dhruv/.cargo/bin/rust-analyzer"	"stderr"	"[ERROR project_model::workspace] cyclic deps: ruff_python_parser(Idx::<CrateData>(50)) -> ruff_python_ast(Idx::<CrateData>(37)), alternative path: ruff_python_ast(Idx::<CrateData>(37)) -> ruff_python_parser(Idx::<CrateData>(50))\n"

Test Plan
Check the logs of rust-analyzer to not see any signs of cyclic dependency.

Hmmm, I struggle with

Move all of the test cases that depends on the parser from ruff_python_ast to ruff_python_parser

The problem is that the tests are now no longer living next to the implementations. This makes them hard to discover or even knowing why a test failed (My intuition for a failing test in the parser crate is that the parser is incorrect).

Removing the cyclic dep is more important to me than co-locating the tests, so I’d still vote in favor of this.

The other alternative is to create a third crate that depends on both, and put the tests in there, but that will also bring some confusion,

Removing the cyclic dep is more important to me than co-locating the tests, so I’d still vote in favor of this.

Because of rust-analyzer? Because it isn't a cyclic dependency according to rust

ruff_python_ast
ruff_python_parser: depends on ruff_python_ast
ruff_python_ast (tests): depends on ruff_python_parser

Yeah, because of rust-analyzer. It’s causing real problems for people!

Yeah. A few alternative options where I don't have a strong preference:

Create a subfolder in the parser crate for the ast tests, e.g. tests/ast to make it clear what this tests are about
Create a sub-crate in the ruff_python_ast/integration_tests named ruff_python_ast_integration_tests and add it to the workspace members in the root Cargo.toml

I'm slightly preferring the second option. I don't know if @BurntSushi has any other recommendation on how we could restructure our project to avoid the rust-analyzer cyclic dependency.

It seems like this is the rust-analyzer issue: https://github.com/rust-lang/rust-analyzer/issues/3390
I guess it's a problem because rust-analyzer just always enables cfg(test). Which makes sense. That's what you want. But when the test library introduces a circular dependency, that turns into a true circular dependency if cfg(test) is always unconditionally enabled.
I don't really know another way to disable it. I ran into this problem too, but didn't diagnose the root cause. I'd definitely vote in favor of fixing this somehow. It'd be nice if RA could figure out how to make this work though, because this is a legitimate pattern in the ecosystem.

Yeah, weak vote for making a separate crate. (Personally fine with it being at crates/ruff_python_ast_integration_tests for simplicity.)

I've updated the PR description to reflect the recent changes. Thank you all for the recommendations.

It seems like this is the rust-analyzer issue: rust-lang/rust-analyzer#3390

Stumbled upon this just now, there is an issue on the rust-analyzer repo with some more info about this than the one you linked here https://github.com/rust-lang/rust-analyzer/issues/14167


bump framework version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7977138139

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7977138139
Status: failure


New launch workaround

As I was scrolling around, I saw a video about how to use VS for Godot 4 and saw the launch workaround that work both in Godot 3 and Godot 4. I don't know but I think there will be a way to implement this
https://youtu.be/OtfxxY4AeVQ

Honestly I think a launch profile like this should be setup by godot itself when creating a new c# project.
Only problem I currently see with this is that it takes the godot executable path as a parameter. It would be nicer if Godot would set an environment variable for this. So you wouldnt need to manually update the path everytime a new godot version releases

Yes

It will be great all these new feedback could be integrated into VStudio Extension for Godot4 to improve the development experience.
NOW, as always like the previous > 2 years, Any new comer need to read everything to figure out how to make all these discussions work
https://gist.github.com/SilentPenguin/bf24eb348c9d00c34605d1cc54318be7


Make the drag gesture recognizers start from the commit point, not the down point

If a drag gesture recognizer has to compete, then it will commit when the pointer is at a different point than when the gesture started. Currently, we give drag deltas based on the delta from the original point. We should add a configuration option that allows the drag gesture deltas to be based on the commit point instead, and then we should default GestureDetector's gesture recognizers to match the platform's behaviour (which, at least on Android, is to use the commit point).

Hixie, I'm looking into this issue. What do you mean by commit point? Is that the point from which we're sure it's a drag and the GestureDetector emits an onDragStart?
Also, can you give me pointers on how the platform-specific configuration can be set up?

Yes, the commit point would be when we send onDragStart.
Platform-specific configuration at the widget layer looks like:
https://github.com/flutter/flutter/blob/9fe53b0d2bb091535c16689cab705c95eac1c53d/packages/flutter/lib/src/material/scrollbar.dart#L81-L99
In this case this would be in GestureDetector. However, it's possible that actually all platforms want the same behaviour, in which case it would just be a matter of setting the default behaviour on the recognizer to be the commit point.

@jslavitz Does your PR https://github.com/flutter/flutter/pull/23424 address this?

Related: https://github.com/flutter/flutter/issues/15144

Does the DragStartBehavior do that now?


Async error in server's console

Hi, when I have started using this plugin, I encountered these error messages in server's console. It always happens every minute while application is running. Could you please look at it? I'm overloading my Sentry dashboard with these weird errors. However, in Strapi administration everything looks correct. Even publishing works as expected.
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
TypeError: Cannot read properties of null (reading 'publishedAt')
    at Object.toggle (/Users/test-user/Sites/rkckk/web.com/node_modules/strapi-plugin-publisher/server/services/publication-service.js:61:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Thanks.

That should only occur if the records don't exist which is not expected to happen. I will add a guard for it but strange that it is occuring.

This should be fixed in v1.3.4 (latest release)


Use serde_json::Deserializer for all deserialization

Fixes #193.
Previously the from_iter / from_reader / from_slice / from_str functions would go through the private DeserializeImpl struct which made it impossible to specialize on the JSON deserializer.
This approach makes it possible but a bit awkward because I would like to keep the Read trait out of the public API. The resulting code on the user's side looks something like this:
struct S<R> {
    json_deserializer: serde_json::Deserializer<R>,
}

impl<R> S<R>
    where for<'a> &'a mut serde_json::Deserializer<R>: Deserializer<Error = serde_json::Error>
{
    fn next<T: Deserialize>(&mut self) -> Result<T, serde_json::Error> {
        Deserialize::deserialize(&mut self.json_deserializer)
    }
}

As you can tell from the tests, I also made StreamDeserializer much nicer to construct and possible to use with the &[u8] / &str optimizations that were previously only for from_slice / from_str.
  let data = "{ ... }";
- let mut stream: StreamDeserializer<Value, _> = StreamDeserializer::new(
-     data.as_bytes().iter().map(|byte| Ok(*byte))
- );
+ let mut stream = Deserializer::from_str(data).into_iter::<Value>();

The nightly build fails because of clippy.

:umbrella: The latest upstream changes (presumably #206) made this pull request unmergeable. Please resolve the merge conflicts.

Thanks, great! This should make it possible to specialise in a non-hacky way

:umbrella: The latest upstream changes (presumably #208) made this pull request unmergeable. Please resolve the merge conflicts.

I fixed the conflict.


Rules - Github - Part Two

to: @ryandeivert (Tuesday morning)
What
Open source rule that alerts whenever a GHE user is promoted to a site administrator.
Testing
Tests added, and passing:
StreamAlertCLI [INFO]: (25/25) Successful Tests
StreamAlertCLI [INFO]: (51/51) Alert Tests Passed
StreamAlertCLI [INFO]: Completed

Coverage remained the same at 94.71% when pulling 50592d9e18de67f684f3e46c2bc901358991931c on mimeframe-streamalert-rules-github-part-deux into 7f005672d5b028a26c7fdd41f9f579e7b1f0a757 on master.


Data engineering failure — Why is it almost impossible to meet deadlines? - Christophe Blefari @ Towards Data Science

URL: https://towardsdatascience.com/data-engineering-failure-why-is-it-almost-impossible-to-meet-deadlines-fc1b5b5aa90
Review (1-2 sentences): Do you meet deadlines? Nice article about expectations and problems to meet deadlines including data engineering specific. You can find some probably obvious but useful solutions through reading this.

Published in Digest #11


Do not support to include related ressources as attributes

A related ressource should not be included as an attribute value:

Although has-one foreign keys (e.g. author_id) are often stored internally
alongside other information to be represented in a resource object, these
keys SHOULD NOT appear as attributes.

Resource objects have a relationships property which should describe it's
relationships. Relationships could be described by link objects or resource
linkage. Resource linkage must be used if it's a compound document.
Of course an attributes value may be a JSON object or an array:

Complex data structures involving JSON objects and arrays are allowed as
attribute values. However, any object that constitutes or is contained in
an attribute MUST NOT contain a relationships or links member, as those
members are reserved by this specification for future use.

Better explained in these these issue:
https://github.com/json-api/json-api/issues/902

The case that is most correct is the last one (i.e. relationships are
always present). The only time when a relationship shouldn't be present
is if it's been filtered out with the ?fields parameter. In this sense,
relationships are just like attributes.
To your point about the possible overhead of including the relationship
ids in to-many relationships: this is exactly why "links" can be used as
a substitute for "data"!

@IanVS do you have another pair of eyes? I'm not a hundred percent sure that I understood it correctly.

Yeah I'll give it some review tonight.

It's been a long time since I've looked at any of this, but I think my goal was to shove the related data into the attributes instead of as a compound document.  You've pointed out this is incorrect, and the section I linked to in the spec was regarding include query parameters from a client to specify the items to return in a compound document section.  So, I think you're doing the right thing here.


Local variable 'nfr_energy_value' referenced before assignment,  No such file or directory: 'kb.owl'

Assign values to variables nfr_energy_value and nfr_safety_value in the if condition block
https://github.com/tud-cor/mc_mros_reasoner/blob/91667fab876b3fcdfb629def208d3ecf60583396/mros1_reasoner/scripts/mros1_reasoner.py#L77-L90
Use default="$(find mros1_reasoner)/scripts/kb.owl" as the file is not searched by  default="kb.owl"
https://github.com/tud-cor/mc_mros_reasoner/blob/91667fab876b3fcdfb629def208d3ecf60583396/mros1_reasoner/launch/run.launch#L3
No test_mros1_reasoner.py available in the master branch
https://github.com/tud-cor/mc_mros_reasoner/blob/91667fab876b3fcdfb629def208d3ecf60583396/mros1_reasoner/launch/test.launch#L5

@shreyashpalande  thanks for reporting this.
These errors are fixed in https://github.com/tud-cor/mc_mros_reasoner/commit/44d3dab479426a1068ccf6da566c9929ed6a49c0
Can you check them, and if everything is OK close this


[FIXED] SetLogger to be able to set debug/trace to 0

In NATS Streaming, we have a test - started early on - that was testing
logging and called SetLogger(l, true, true), then reset by calling
SetLogger(l, false, false) to reset the values. That obviously had not
the expected effect.
During profiling, I noticed that there were tons of allocated
objects due to NATS server debug/trace statements caused by that.

Coverage decreased (-0.5%) to 89.938% when pulling 44d18c3af63c12adf01d026cdfe7b35f3803ce1a on fix_setlogger into 8caed5eefdbb4b5c9455729343c8006cec71da21 on master.

@derekcollison Given the results from coveralls, it looks like even here in gnatsd, all tests following TestSetLogger in server directory were running with server using debug and trace. Should I add back SetLogger(l, true, true) at the end of that test to restore debug/trace == 1?

You mean to get the test coverage back?

Yes, I meant to get the coverage back.
By the way, here is the pprof result for running NATS Streaming server test:
go test -race -c ./server
go test -race -v ./server -memprofile mem.out
go tool pprof --alloc_objects ./server.test ./mem.out

(pprof) top
5270852 of 6189530 total (85.16%)
Dropped 177 nodes (cum <= 30947)
Showing top 10 nodes out of 70 (cum >= 1459995)
      flat  flat%   sum%        cum   cum%
   1708336 27.60% 27.60%    3167849 51.18%  github.com/nats-io/nats-streaming-server/vendor/github.com/nats-io/gnatsd/server.(*client).traceOp
    606229  9.79% 37.39%     606229  9.79%  fmt.(*fmt).padString
    524304  8.47% 45.87%    2013474 32.53%  fmt.Sprintf
    481527  7.78% 53.65%     481527  7.78%  fmt.glob.func1
    458758  7.41% 61.06%    2184653 35.30%  github.com/nats-io/nats-streaming-server/vendor/github.com/nats-io/gnatsd/server.(*client).Tracef
    373914  6.04% 67.10%     809161 13.07%  github.com/nats-io/nats-streaming-server/vendor/github.com/nats-io/go-nats-streaming.(*conn).publishAsyncWithReply
    360452  5.82% 72.92%     786448 12.71%  fmt.(*pp).handleMethods
    320404  5.18% 78.10%    1045544 16.89%  github.com/nats-io/nats-streaming-server/vendor/github.com/nats-io/gnatsd/server.(*client).traceMsg
    292740  4.73% 82.83%     292740  4.73%  github.com/nats-io/nats-streaming-server/vendor/github.com/nats-io/nats.(*Conn).processMsg
    144188  2.33% 85.16%    1459995 23.59%  github.com/nats-io/nats-streaming-server/vendor/github.com/nats-io/gnatsd/server.(*client).deliverMsg

And an svg for the Sprintf method only:
(pprof) svg Sprintf > sprintf.svg

You will see that lot of them belong to the gnatsd server because debug/trace is enabled because one of Streaming test that called SetLogger(l, true, true) and although we then call SetLogger(l, false, false) it has no effect.
sprintf.pdf

So once we can turn it back off should be good to go correct?

Yes, I think we need to be able to set it back off, or we should not test it setting on because otherwise it affects all remaining running tests.

LGTM


Test and implementation refactoring

Some changes in the implementation:

Reduce constructor visibility of some bindings if the constuctor is used in test cases only
Replace the default profile null with Profile.DEFAULT

I guess its allright


feat(performance): update build step to include svgo to optimize svg output (#103)

Alaska Airlines Pull Request
This PR adds the SVGO library to optimize the SVG output of the Icons for file size reduction.
Resolves: #103
Summary:
svgo's optimize() function has been added in generate.js as a last step before the files are written to disk.
Some of the built-in plugins' default settings were changed in order to preserve necessary elements and attributes for this project:

removeDesc: false (removes <desc> when true)
removeTitle: false (removes <title> when true)
removeUnusedNS: false (removes xmlns:xlink= attribue when true)
removeUnknownsAndDefaults: { keepRoleAttr: true } (removes role= when false)

File sizes for all icons are reduced without affecting image quality. Example: payment/cc-alaska.svg is reduced from 61 KB to 23 KB.
Type of change:

[X] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[X] My update follows the CONTRIBUTING guidelines of this project
[X] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please amend the commit to use feat(performance) as this is a new optimization feature. Also, the build keyword will not create a new release and users will not be able to take advantage of the new lighter weight icons.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[feature][graphql] Create a tool to map metadata library to GraphQL schema

Is your feature request related to a problem? Please describe.
Metadata libraries are defined in yaml files, they need to be mapped to .graphqls files for gqlgen to generate GraphQL model and resolvers.
Describe the solution you'd like
A simple go tool to parse library yaml files and generate graphqls files.
Describe alternatives you've considered
None
Additional context
The tool should also run automatically using Makefile rules.

closing as "not planned now" and labelled as requested, per Scrum decision 2023-10-30


fix: omnicompl may no completeItems yet

lspserver may have no completeItems yet, then omnicompl will be 'err'.

if lspserver.omniCompletePending || !lspserver->has_key('completeItems')

The lspserver.completeItems field is set to an empty List in line 488 above, when the omni-completion function
is called with findstart' set to true.  Under what conditions, the completeItemskey will not be present inlspserver`?

somehow if omniCompletePending is false, then lspserver maybe no completeItems yet.
--
shane.xb.qian

if lspserver.omniCompletePending || !lspserver->has_key('completeItems') The lspserver.completeItems field is set to an empty List in line 488 above, when the omni-completion function is called with findstart' set to true. Under what conditions, the completeItemskey will not be present inlspserver`?

somehow if omniCompletePending is false, then lspserver maybe no completeItems yet.

Under what conditions did you see this problem?

if lspserver.omniCompletePending || !lspserver->has_key('completeItems') The lspserver.completeItems field is set to an empty List in line 488 above, when the omni-completion function is called with findstart' set to true. Under what conditions, the completeItemskey will not be present inlspserver`?

somehow if omniCompletePending is false, then lspserver maybe no completeItems yet.

Under what conditions did you see this problem?

Under when if omniCompletePending is false, there is no 'lspserver.completeItems = []'
--
shane.xb.qian

if lspserver.omniCompletePending || !lspserver->has_key('completeItems') The lspserver.completeItems field is set to an empty List in line 488 above, when the omni-completion function is called with findstart' set to true. Under what conditions, the completeItemskey will not be present inlspserver`? > > somehow if omniCompletePending is false, then lspserver maybe no completeItems yet. Under what conditions did you see this problem?

Under when if omniCompletePending is false, there is no 'lspserver.completeItems = []'

In the two places where omniCompletePending is set to false, lspserver.completeItems is initialized.
So I don't see a condition where omniCompletePending is false but completeItems is missing
from lspserver.
Can you use describe the steps to reproduce this problem (e.g. LSP server, plugin configuration
and the keys pressed)?

if lspserver.omniCompletePending || !lspserver->has_key('completeItems') The lspserver.completeItems field is set to an empty List in line 488 above, when the omni-completion function is called with findstart' set to true. Under what conditions, the completeItemskey will not be present inlspserver`? > > somehow if omniCompletePending is false, then lspserver maybe no completeItems yet. Under what conditions did you see this problem?

Under when if omniCompletePending is false, there is no 'lspserver.completeItems = []'

In the two places where omniCompletePending is set to false, lspserver.completeItems is initialized.
So I don't see a condition where omniCompletePending is false but completeItems is missing
from lspserver.

what if 'omniCompletePending' itself was 'false', where did 'lspserver.completeItems = []'?
--
shane.xb.qian

I am seeing this message in Java with
call LspAddServer([#{name: 'jdtls',
								 \	 filetype: 'java',
								 \	 path: 'jdtls',
								 \ }])

on every completion

My cursor is between { }
After this fix, error is gone. No completions though. Should I expect completions ?

Which language server are you using?  Can you include the LSP plugin settings?  It will also be useful to include a sample code that reproduces the problem.

After this fix, error is gone. No completions though. Should I expect completions ?

i donot know,
to me, it should be "searching",
// then later (somehow?) it showed the completions, or "failure",
maybe more make sense.

this PR shoud be helping such flow, but i donot know why it is showing "searching" forever... :shrug:
// vs #462 which just to cancel the compl.

or it was quickly enough to "cancel"?
but later somehow it may get the completions (of/at that) anyway.
// so i donot know, it is up to yegappan, and #462

This is a regression caused by the PR https://github.com/yegappan/lsp/pull/418. I have committed https://github.com/yegappan/lsp/commit/0b9bba0ee4eaa84a75d88a0775b3b34dbf42b12d to address this issue.

I have committed 0b9bba0 to address this issue.

i think it became worse, tho logically maybe you were right if -2, but it would be no message about the status?
'cancel' meant you passed [] then no result, or here this PR let it be showing "searching",
tho not sure why it was showing forever, vs [] made it be failed directly.
so i donot know your first commit at #462 was better or here mine this one was preferred.
// anyway, personally i donot like your second commit for #462, but up to you, i am not going to argue too much.

Which language server are you using? Can you include the LSP plugin settings? It will also be useful to include a sample code that reproduces the problem.

Apologies for the late reply
I am using https://github.com/typescript-language-server/typescript-language-server
My settings

hi Err ctermfg=Red      ctermbg=NONE cterm=bold
hi Wrn ctermfg=Yellow   ctermbg=NONE cterm=bold
hi Hnt ctermfg=Blue     ctermbg=NONE cterm=bold
hi Inf ctermfg=White    ctermbg=NONE cterm=bold

au BufWinEnter * sign define LspDiagError     text=E   texthl=Err numhl=Err linehl=
au BufWinEnter * sign define LspDiagWarning   text=W   texthl=Wrn numhl=Wrn linehl=
au BufWinEnter * sign define LspDiagHint      text=H   texthl=Hnt numhl=Hnt linehl=
au BufWinEnter * sign define LspDiagInfo      text=I   texthl=Inf numhl=Inf linehl=

call LspOptionsSet(
            \ {
            \    'showSignature': v:false,
            \    'autoComplete': v:false,
            \    'showDiagOnStatusLine': v:true,
            \    'noNewlineInCompletion': v:true,
            \    'completionMatcher': 'icase',
            \    'keepFocusInReferences': v:true,
            \    'highlightDiagInline': v:false,
            \ }
            \ )

let lspServers = [
            \ {
            \    'name': 'clangd',
            \    'filetype': ['c', 'cpp'],
            \    'path': '/usr/bin/clangd',
            \    'args': ['--background-index']
            \ },
            \ {
            \    'filetype': ['javascript', 'typescript'],
            \    'path': 'typescript-language-server',
            \    'args': ['--stdio']
            \ },
            \ {
            \    'filetype': 'python',
            \    'path': '/home/santosh/.local/bin/pylsp',
            \    'args': ['--check-parent-process', '-v']
            \ },
            \ {
            \	 'filetype': 'vim',
            \	 'path': 'vim-language-server',
            \	 'args': ['--stdio']
            \ },
            \ ]

call LspAddServer(lspServers)

au FileType c,python,javascript,typescript,vim,sh nnoremap <buffer> <silent> gd :LspGotoDefinition<CR>

au FileType javascriptreact,typescriptreact nnoremap <buffer> <silent> gd :LspGotoDefinition<CR>

au User LspAttached set keywordprg=:LspHover

Which language server are you using? Can you include the LSP plugin settings? It will also be useful to include a sample code that reproduces the problem.

Apologies for the late reply
I am using https://github.com/typescript-language-server/typescript-language-server

Thanks for the details.   This problem should be addressed by https://github.com/yegappan/lsp/commit/0b9bba0ee4eaa84a75d88a0775b3b34dbf42b12d.  Can you try the latest version of the plugin?

No error anymore.


API Key Revocation for shared users

Problem
When the application sharing enabled, the shared user can only generate the API Keys but can not revoke those
Solution
Allow the shared users to revoke the API Keys generated.
Affected Component
APIM
Version
No response
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Public fix: https://github.com/wso2/carbon-apimgt/pull/12191 has already been merged.


Collect ClockDrift metadata block part of the new ${ECS_CONTAINER_METADATA_URI_V4}/task endpoint

Feature request to include the new ClockDrift metadata block which is part of the new v4 ${ECS_CONTAINER_METADATA_URI_V4}/task endpoint
ClockDrift information is useful to determining if there's an time drift which can cause problems with time sensitive token/authorization flows.
Context: https://aws.amazon.com/about-aws/whats-new/2021/09/monitoring-clock-aws-fargate-amazon-ecs/
Priority:  Nice to have. Currently trying to troubleshoot an intermittent issue which may be due to clock drift.

We appreciate you taking the time to bring this to our attention. After reviewing this issue, we are unable to commit on a timeline to resolution. When committing to resolve an issue, we take into account the type of issue, the customer impact, and the development effort required. If the situation changes, we will revisit this decision.
We encourage community contributions and are happy to collaborate on design proposals and pull requests. See our PR guidelines in the README. If you have any further questions or comments about this, please let us know by replying to this issue.


chore: code reorganization

This change moves our source files under src, our build files under build, and uses the base tsconfig-google.json config.  It makes this library more consistent with our other libraries, and makes it easier to work with generated files.

@alexander-fenster Would be great if you could start reviewing these :)

Please note that this change broke link refs for KMS: https://cloud.google.com/kms/docs/reference/libraries#client-libraries-install-nodejs
You may want to check with other products referencing here to make sure they aren't broken.

Yar, thanks for the heads up.  @jmdobry is there an easy way to search the docs for links to this repo?


feat: *_classification files gain column indicating the version or revision of the bridge, if relevant

Some classification systems (e.g. ISIC) have numerous different versions of the classification system.
It would be good to track this in a user-facing in, for example, the individual *_classification datasets, while recognizing that that column would never actually be used in the code.
My proposal would be that:

the *_classification datasets gain a column indicating this information if necessary
the sector_classifications dataset keeps only the crucial columns used by the code (e.g. sector, borderline, code, code_system)

cc @jacobvjk
AB#10174

Update:

[ ] nace_classification
[ ] naics_classification
[ ] sic_classification
[ ] gics_classification
[ ] psic_classification
[ ] isic_classification

library(r2dii.data)

classifications <- list(
  nace_classification = nace_classification,
  naics_classification = naics_classification,
  sic_classification = sic_classification,
  gics_classification = gics_classification,
  psic_classification = psic_classification,
  isic_classification = isic_classification
)

lapply(classifications,names)
#> $nace_classification
#> [1] "original_code" "code"          "code_level"    "sector"
#> [5] "borderline"
#>
#> $naics_classification
#> [1] "code"        "naics_title" "sector"      "borderline"
#>
#> $sic_classification
#> [1] "code"        "description" "sector"      "borderline"
#>
#> $gics_classification
#> [1] "code"        "code_level"  "sector"      "borderline"  "description"
#>
#> $psic_classification
#> [1] "original_code" "code_level"    "code"          "sector"
#> [5] "borderline"
#>
#> $isic_classification
#> [1] "ISIC Rev 5 Code"  "ISIC Rev 5 Title" "code"             "sector"
#> [5] "borderline"       "revision"

Created on 2024-03-12 with reprex v2.1.0

Closed by #357


How to incorporate auxiliary input information in geometric models

❓ Questions & Help
Thanks for awesome work.
I'm trying to use SpiralNet++/SplineConv/GMMConv for CFD analysis (something like this paper but for 3D) and getting good results.
I would like to know what's the best way to incorporate auxiliary input information (other than input coordinates and spiral sequences/edges) in the network.
For example, I would like to introduce input freestream velocity (x,y, z-direction) and angle of attack (scaler value) to the network.
Many Thanks.

Can't you just use these features as input features to your network?

One way is to concatenate extra information with input coordinates.
But I'm confused that what if I have only one single scaler value (e.g. angle of attack = 30) as auxiliary input information, then I would concatenate 30 with all input coordinates (x,y,z, 30) making input coordinates 4 dimensional?

Yeah, that‘s what I meant.


input with tag passes arguments in lowercase

Normally, strings passed to functions are passed as is. But in the markup below the passed string is converted to lower case. Not sure why. The workaround is to call the function outside the markup and then just insert the variable. But it would be ideal if this worked. The parameter below "gEnableEventProcessing" gets passed to my .net class as lower  case.
<input type="checkbox" class="form-check-input" id="gEnableEventProcessing" name="gEnableEventProcessing" {{ get_setting_bool '<input type="checkbox" class="form-check-input" id="gEnableEventProcessing" name="gEnableEventProcessing" {{ get_setting_bool 'gEnableEventProcessing' }} >' }} >

Difficult to say, I don't recall that we are doing something in particular... you example is a bit weird because you have nested {{ get_setting_bool  which would not work, specially the first string after get_setting_bool  is going to eat until the next '

Thanks for commenting, I see that my post was messed up, copy/paste error. I fixed the html in my original post. To get it to work I did:
{{ chk=get_setting_bool 'gEnableEventProcessing' }}
Then use {{ chk  }} in place of the call. This works ok. So very odd. The call is made, but the parameter is converted to lowercase. I checked the HTML that was generated and the parameter is ok, so its converted only when the call is made and the parameter is passed.

if you had a very small reproducible bug here that you can copy paste and I could run directly, that would help, otherwise I can't really tell if it is a bug in scriban or a misusage of it.


[Feature]: Add a Cancel CTA on Toast msg "API will be executed on Page Load" when user consume API response {{API.data}}

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Suggested Solution
We could give users a "CANCEL" CTA in the toast where we inform them "API1 will now run on page Load"?
Why should this be worked on?
Though it makes sense to enable "Run API on Page Load" for users automatically when they consume API's response using {{API1.data}} but for the case when they actually don't need to run API on page load, this adds up to user work to manually disabled it.
Cases where the user would want to disable "Run API on page load" though using API's response

Form submission
File upload
Many scenarios of post API calls related to submission of data and using the response.
DB update query

I would strongly like this feature, or even better, a feature I can set at the install / workspace / app / page level to disable this automatic change.  I prefer to control my query execution by using a JS object pageManager.start() that is run on page load and executes the queries in the order (or simultaneously) that I want.  It gets frustrating to have to remember to go back and disable run on page load for all the queries after I work on a page, and sometimes they get missed (usually isn't terrible, but will cause the query to run twice).


governance: Make sure proposals have valid type

That makes things definitely better 👍 But still, do you have any thoughts to share about

Wouldn't it make sense and be just fine to use the top level type only, drop the one in object data (data/vchData), change this constructor to also accept int nObjectType and drop LoadData() + just verify its valid JSON in IsValidLocally instead of checking fUnparsable

I mean, if you don't see anything concerning / this doesn't break anything it might be the better solution for two reasons:

Don't send/include redundant data (not that we talk about huge data :D but redundant is redundant haha)
Also makes sure there can't be inconsistency in type for trigger objects (should still be possible with this PR i think?).

I would avoid touching vchData/data structure unless there is an actual need for this tbh because this is what we get from 3rd-party software via rpc (and an overhead is tiny imo). Good point re type for triggers, added 27487b0.


[Enhancement] React rendering instead of handlebars

I've tested the demo app on mobile a bit (iPhone 4s) and its pretty slow / sluggish. Have you considered rendering using React? I haven't seen anything regarding this.

That's a great idea. If you submit a pull request for this I'll be happy to evaluate it :)


Multiple calendars

Hiya! I am interested in displaying multiple calendars.
Do you have a nice way of doing this?
Thank you!

Just instantiate as many as you like


Could you tell me how long I need to wait for DatePicker?

What problem does this feature solve?
I will update 0.6 -> 0.7, but I need date picker, Could you tell me the estimation about this component?
thanks.
What does the proposed API look like?

next month I am afraid.

We can use this component in 0.7 or 1.0? If you tell me we can use in the angular6, I will cry......, I have start a new project and use the 0.7, and I have to finish it in the next month.

you can choose other datepicker component instead.

So, After updating the angular6, I can use DatePick in ng-zorro?

@vthinkxie any advices for other datepicker component ?

@oridark you can use https://material.angular.io/components/datepicker/overview as temp solution.


hyperboot.org down

@substack Is it possible to get the source of the site, or is that just the example in the repo?


Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Add Assignment 2
What did you learn from the changes you have made?
preprocessing data, implement and improve model for NLP
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Use GPT3 pretraing for model
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
The generative part was a bit challenging because we didn't cover it in the course. I built the generation function separately, checking the output line by line to ensure I handled errors correctly. I also used Lab 8 and hints from the assignment description.
How were these changes tested?
Code parts and model was tested manually.
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Reviewed and marked as completed


Crosspost to LinkedIn

It would be kind of cool if it was possible to CrossPost to LinkedIn articles as well. Not sure if it would be better implemented as a separate project (or if the API's even support it..)

I would do it separately. Do you know where the API docs are?
On Sat, Dec 9, 2017 at 12:30 AM, 0xdevalias<EMAIL_ADDRESS>wrote:

It would be kind of cool if it was possible to CrossPost to LinkedIn
articles as well. Not sure if it would be better implemented as a separate
project (or if the API's even support it..)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aarongustafson/jekyll-crosspost-to-medium/issues/39,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEn2HkOQLyRtAYxjr7w7TZQDmyq1S0Wks5s-hsPgaJpZM4Q78Aw
.

As best I can tell from a quick google, it seems like it doesn't appear to be something they expose as a public API :(

https://developer.linkedin.com/docs/guide/v2/shares/articles-api

Only has retrieve/delete type endpoints

https://www.quora.com/Can-I-schedule-LinkedIn-pulse-posts-automatically-through-software-like-Hootsuite

Says no

https://stackoverflow.com/questions/30592163/linkedin-api-pulse-share

Has basically hacked around it to do it through the Web UI automagically

Realistically, it's probably not all that hard of a workflow to do manually. Was playing with things yesterday, and it seems that I can write my post, use this (or the import tool) to send it to medium, clean it up there, then copy all of that and paste into LinkedIn basically verbatim, give it a final once over, then publish.

I kept having Ruby/Jekyll issues when upgrading my Mac, so I have moved off of Jekyll and will not be working on this project anymore, going forward. I am going to flag this as won’t fix, but leave it open in case someone else wants to pick up the project from here.


Update Composer dependencies (2020-03-13-00-13)

Visual regression test passed!
View the visual regression test report


Stop IncomingSocketManager epoll tasks on server stop

Description
HTTPServer creates an IncomingSocketManager instance on startup which creates two async epoll tasks and DispatchQueues on linux. These tasks should be terminated when the server stops so the dispatch threads are released. Otherwise for a linux application that does a periodic Kitura.start() and Kitura.stop(), the threads for these tasks are never released.
Also, initialize Log.logger once across all tests to avoid crash (See IBM-Swift/Kitura#996)
Motivation and Context
See IBM-Swift/Kitura#997
How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Codecov Report

Merging #175 into master will increase coverage by 0.06%.

@@            Coverage Diff             @@
##           master     #175      +/-   ##
==========================================
+ Coverage   84.37%   84.43%   +0.06%
==========================================
  Files          27       27
  Lines        2406     2416      +10
==========================================
+ Hits         2030     2040      +10
  Misses        376      376

Impacted Files
Coverage Δ

Sources/KituraNet/HTTP/HTTPServer.swift
75.67% <100%> (+0.9%)
:white_check_mark:

Sources/KituraNet/IncomingSocketManager.swift
90% <100%> (+1.36%)
:white_check_mark:

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 5e7ad7d...6607684. Read the comment docs.


RPC takes too long to respond

Just call /v1/chain/get_info. It takes 114 seconds to return.

I meet the same problem, could you share how to resolve it?


When updating with a qualified updated_at column, the current time is still persisted

Laravel Version: 8.64.0
PHP Version: 7.4
Database Driver & Version: MySQL 8.0.20

Description:
When the updated_at column is manually updated using a qualified column name, the current time is still persisted. If the column name is not qualified, it works as expected.
Steps To Reproduce:
This works:
MyModel::whereIn('my_model.id', $ids)->update(['updated_at' => $date]);

But this results in the updated_at column being set to the current time rather than the provided time:
MyModel::whereIn('my_model.id', $ids)->update(['my_model.updated_at' => $time]);

Gonna see how @rodrigopedra's PR goes. Thanks for reporting.


 (I tried restarting the game but nothing happened)
Auto talk cannot skip cutscene from domain anymore
Console bug

Hope devs fix these soon

God mode also doesn't really make you invincible, i still take damage from some attacks and almost all environmental things