Investigate better Result

I made a simple Result type in the master branch of this repository. It's a very simple implementation that I would like to improve and ensure it's robust enough to handle what we want.
The purpose of this specific type is to carry along the general information found during the subdomain enumeration process, encapsulating the necessary logic into a concise protocol/interface which other pieces of the internal system and work with.
At least that's what I was thinking when making it. 😹
Current Implementation
It currently looks like this (note: this is not used in SubFinder, just this repository):
type Result struct {
	Type    string
	Success string
	Failure error
}

The Type is a string which is meant to have some sort of meaning based on whatever Result this is. Perhaps something like "baidu", "yahoo", "shodan", "google", or whatever other Sources are implemented now and in the future.
The Success is also a string which is mean to carry the meaningful value like "example.google.com" as a found subdomain.
The Failure is meant to encapsulate the errors from the Source as a typical golang error.

I'm fairly certain this can be improved to provide better... results 😉
Forgive my terrible puns, please.
Improving the Implementation
Note these are not in order or need to be done together in any way, just thinking:

The Result type could perhaps be turned into an interface instead of a struct that contains these current values.
The Success for a Result could be an empty interface and based on the Type, type assertion could happen where needed.

Success with interface{} (empty interface)
Instead of a string to encapsulate all successes, an empty interface (interface{}) could be used. This would allow different types of results to provide practically any value; and it would be up to whoever is using that type to do the correct type assertion for what they want.
To be clear: I'm not saying this is the best way to go, or the worst.
package main

import "fmt"
import "encoding/json"

type Result struct {
	Type    string
	Success interface{}
	Failure error
}

func main() {
	r := &Result{}
	b := []byte(`{"Type":"example","Success":0,"Failure": null}`)
	err := json.Unmarshal(b, r)
	if err != nil {
		panic(err)
	}
	r.Success = r.Success.(float64) + 1
	fmt.Println(r.Success == float64(1))
}

Output
true

Note: this also provides the least amount of friction for what is current implemented. Though I do not think that is the primary "selling point" for this approach. Just one aspect to consider. 👍

Implementing success as interface is really cool. It would also allow us to return an array of subdomains or individual subdomains.

@Ice3man543 Yeah, I agree. 👍
Example of dealing with results with different underly success types (string and slice of strings):
package main

import "fmt"

type Result struct {
	Type    string
	Success interface{}
	Failure error
}

var Example1 = &Result{Type: "example1", Success: "red.google.com"}
var Example2 = &Result{Type: "example2", Success: []string{"gree.google.com", "blue.google.com"}}

func main() {
	examples := []*Result{Example1, Example2}

	for _, example := range examples {
		switch v := example.Success.(type) {
		case string:
			fmt.Printf("%v is a string\n", v)
		case []string:
			fmt.Printf("%v is a slice of strings\n", v)
		default:
			fmt.Printf("The type of v is unknown\n")
		}
	}
}

Output
red.google.com is a string
[gree.google.com blue.google.com] is a slice of strings

Timestamp (UTC)?
Just another thought, maybe not the best one. 🤷♀  What if there was a timestamp associated with the result? Something like Coordinated Universal Time (UTC).
In certain situations, this may be useful to have such as:

Comparing results over time ( past results ).
Keeping track of the results per second from sources.
Storing results in a database for better queries.

Over in the investigate better result branch, I've implemented the following:
type Result struct {
	sync.RWMutex
	Timestamp time.Time
	Type      string
	Success   interface{}
	Failure   error
}


Add updateAt and createdAt in the index class

When manipulating indexes (get/create/update), the SDKs return an instance of Index which already contains the primaryKey attribute.
ex:
index = client.index('movies')
index.primary_key

But we cannot do:
index.updated_at
index.created_at

We should be able to do this so that every information are available from the index instance.
TODO

[x] meilisearch-dart
[x] meilisearch-dotnet
[ ] meilisearch-go
[x] meilisearch-java
[ ] meilisearch-js
[x] meilisearch-php
[x] meilisearch-python
[x] meilisearch-ruby
[ ] meilisearch-rust
[x] meilisearch-swift

Addition to the Python SDK, it's already implemented in:

Dart SDK
Java SDK
Swift SDK

And partially implemented in

JS SDK (for example, the attributes are not updated in getRawInfo)

Addition to the Python SDK, it's already implemented in:

Dart SDK
Java SDK
Swift SDK

And partially implemented in

JS SDK (for example, the attributes are not updated in getRawInfo)

The issues have been open in the different repositories.

Yes, would be awesome to get an official perspective from the core team!
I've read about other implementations, about who is using the converted data object (not searched in every implementation):

https://github.com/meilisearch/meilisearch-dotnet/pull/170
https://github.com/meilisearch/meilisearch-python/pull/261
https://github.com/meilisearch/meilisearch-dart/blob/15287f6e08b1f35faaf2b5ff221222b02d5ac306/lib/src/index.dart#L13
https://github.com/meilisearch/meilisearch-swift/blob/518cc19652e6a921bc829ed3319841100e8f3ab8/Sources/MeiliSearch/Model/Index.swift#L28

Hello @bb and @brunoocasali! Thanks a lot for your intervention here, this is really pleasant to work with contributors who care about all the SDKs 😄
Even if we like the conformity over the SDKs (ex: provide the same kind method so that there are all convenient to use) we always want to prioritize one thing: to be idiomatic with the language. If you, as Ruby developers, think this is better to have Time object instead of String, we trust you :)
Your feedback to other languages you like/master is also more than welcome :)

Update: the meilisearch-ruby PR was changed to use the Time class and merged.
I also stumbled over https://github.com/meilisearch/meilisearch-js/pull/1056#discussion_r728772207

Since only one SDK is missing, and it has its issue, there is no need to keep this open!
I'll close it, thanks, team! ❤


unclear how to deploy to rackspace

Hi,
I got my local vagrant running, just by retrying the same sequence after few days.
Now I want to test with rackspace machines.
I got ssh ping working: ansible all -i inventory/1-datacenter -m ping
I use /etc/hosts to spoof and map host-01 through host-05 to same ip in the cloud.
And I run security setup both locally and remote (where do I need to run?).
I run it with --consul false.
Now trying to execute:
nicu@nmarasoiu:~/tools/microservices-infrastructure$ ansible-playbook -i inventory/1-datacenter site.yml -e @./security.yml
PLAY [localhost] **************************************************************
TASK: [check for security] ****************************************************
skipping: [localhost]
PLAY [localhost] **************************************************************
TASK: [verify openstack environment] ******************************************
skipping: [localhost] => (item=OS_USERNAME)
failed: [localhost] => (item=OS_PASSWORD) => {"failed": true, "item": "OS_PASSWORD"}
msg: openstack environment variable OS_PASSWORD is not set
FATAL: all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
verify openstack environment -------------------------------------------- 0.01s
check for security ------------------------------------------------------ 0.01s
to retry, use: --limit @/home/nicu/site.retry
localhost                  : ok=0    changed=0    unreachable=0    failed=1

I do not necessarily want openstack, not do I understand its role at the moment.
My machines will be already defined (I provide them with docker-machine for now).

also want to mention that i prefer other authentication methods such as the key pair, not the password. maybe would be better to clarify context on the os_password above and alternatives if any

Setting a password, retry, now gives:
nicu@nmarasoiu:~/tools/microservices-infrastructure$ ansible-playbook -i inventory/1-datacenter site.yml -e @./security.yml
PLAY [localhost] **************************************************************
TASK: [check for security] ****************************************************
skipping: [localhost]
PLAY [localhost] **************************************************************
TASK: [verify openstack environment] ******************************************
skipping: [localhost] => (item=OS_USERNAME)
skipping: [localhost] => (item=OS_PASSWORD)
PLAY [all] ********************************************************************
TASK: [add ssh key to openstack tenant] ***************************************
failed: [host-01 -> <IP_ADDRESS>] => {"failed": true}
msg: Unable to authorize user: Authentication requires 'auth_url', which should be specified in 'HTTPClient'
failed: [host-04 -> <IP_ADDRESS>] => {"failed": true}
msg: Unable to authorize user: Authentication requires 'auth_url', which should be specified in 'HTTPClient'
failed: [host-03 -> <IP_ADDRESS>] => {"failed": true}
msg: Unable to authorize user: Authentication requires 'auth_url', which should be specified in 'HTTPClient'
failed: [host-02 -> <IP_ADDRESS>] => {"failed": true}
msg: Unable to authorize user: Authentication requires 'auth_url', which should be specified in 'HTTPClient'
failed: [host-05 -> <IP_ADDRESS>] => {"failed": true}
msg: Unable to authorize user: Authentication requires 'auth_url', which should be specified in 'HTTPClient'
FATAL: all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
add ssh key to openstack tenant ----------------------------------------- 0.52s
verify openstack environment -------------------------------------------- 0.01s
check for security ------------------------------------------------------ 0.01s
to retry, use: --limit @/home/nicu/site.retry
host-01                    : ok=0    changed=0    unreachable=0    failed=1
host-02                    : ok=0    changed=0    unreachable=0    failed=1
host-03                    : ok=0    changed=0    unreachable=0    failed=1
host-04                    : ok=0    changed=0    unreachable=0    failed=1
host-05                    : ok=0    changed=0    unreachable=0    failed=1
localhost                  : ok=1    changed=0    unreachable=0    failed=0
Would you be kind to explain what is being attempted? Is openstack the only flow to deploy multiple nodes? How is localhost affected (it is my dev computer)?

Are you running off of master? We've just implemented terraform (terraform.io) provisioning to clusters, which allows us to deploy to Google Cloud, OpenStack, and AWS (coming this week).
We've found a huge amount of incompatibilities between Ansible 1.9.X and the python-novaclient modules, which is causing many users to fail with errors. This is why we are shifting to terraform.
For the error you are getting, can you confirm that your inventory/group_vars/dc1 file is populated with the correct values for your openstack environment?

Hi,
I am not sure if I have an openstack env. I just have a rackspace account, and have 1 running machine, which I wanted to provision with all roles (for now; after this works i will go 4 nodes).
I am in the process of studying how to use rackspace public cloud as an openstack provider, I am now anticipating it would offer a public api endpoint and a way to authenticate to it, and likely i will kill my machine to be automatically created from the specs i give ansible through site.yml and/or other configs (i need to determine those as well).

Is there a clear way to deploy to a number of existing IPs with ssh keys installed?
Can I find a documentation on this?
We must evaluate rackspace, but they offer openstack only in private cloud with $25K monthly fee.
Apparently they also offer some way to automate creating vms because docker-machine has a working rackspace driver (not the openstack driver) which worked for me. But that needs to be hooked to ciscocloud, which is not my target at the moment.


fix tsserver picking hidden files created by emacs

Fixes #
Saw this good for first timers. I followed what @sheetalkamat suggested.
#31916

[x] There is an associated issue in the Backlog milestone (required) #31916

[x] Code is up-to-date with the master branch
[x] You've successfully run gulp runtests locally
[x] There are new or updated unit tests validating the change

Please add a unit test

 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.:x: suhasdeshpande sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@sheetalkamat someone will merge this PR at some point? Do I need to follow up?


Exception thrown on application bootstrap

Getting below exception,
\node_modules\swiper\dist\js\swiper.js:3627
var ua = navigator.userAgent.toLowerCase();
^
ReferenceError: navigator is not defined

#1541

#1541

nolimits4web/Swiper#1541

There is a similar issue here nolimits4web/Swiper#1541
#14

+1

💯


Loads Frame but fails load content of DASHBOARD, @superset-ui/embedded-sdk

I have a superset application up and running in Ubuntu server.
I have made required configuration in Superset_config.py file for DASHBOARD to embed in My application[Angular page],
I have created a user with role :  GAMMA, PUBLIC and
Able to get create CRSI and guest token for embedded function,
I'm using CDN [https://unpkg.com/@superset-ui/embedded-sdk] to embed my dashboard.
with
`
`
The script loads the IFRAME to my angular page, and a superset loading screen will be seen for few seconds but it just calls /role API and stops after that..!!

Please can anyone explain what I'm missing.?

Are you a 100% certain you don't have a trailing slash in the supersetDomain?

It's hard to infer what is actually going on without seeing the error logs.
But I wrote a guide on it, hopefully, it helps someone 😄 Choose your preferred media 😝
https://huamichaelchen.substack.com/p/end-to-end-example-of-setting-up
https://medium.com/@huamichaelchen/end-to-end-example-of-setting-up-superset-embedded-dashboard-f72fc985559

Hopefully, the answers above is sufficient to close this thread. I'll do so anyway since it's been so long since there was a comment here. If this needs revisiting/reopening, just say the word.


access denied to S3 bucket

curl https://gregburek-buildpack-postgresql.s3.amazonaws.com/cedar/postgresql-9.3.5.tgz yields the following result:
<?xml version="1.0" encoding="UTF-8"?>
<Error>AccessDenied<Message>Access Denied</Message><RequestId>B8C2735410219510</RequestId><HostId>IEWj5EzCblZgoo803crRYJNiVjkaU1GEu8RGvV5Sm59BxFR6fJcHdTTLVMT//G8V</HostId></Error>

Is there a problem with the S3 bucket?  Or is this buildpack not intended to be used directly?

Checking on this, that file doesn't exist, and in fact the cedar folder is empty. We are on cedar-14 stack internally and the last time I tried to get cedar binaries working, it was a huge rat's nest. I suggest using https://s3.amazonaws.com/gregburek-buildpack-postgresql/postgresql-9.3.4.tgz which should work on cedar.
Alternately, I recommend going to cedar-14, it is way better and has an official docker image: heroku/cedar:14

Ok, thanks -- I'll see about getting us migrated to cedar-14.


PersistMarshalError while resyncing faucet wallet

[Error] A database error occured: PersistMarshalError "field keyRing: int64 Expected Integer, received: PersistNull" @(haskoin-wallet-0.2.0:Network.Haskoin.Wallet.Server.Handler ./Network/Haskoin/Wallet/Server/Handler.hs:92:15)

The error is referring to the keyRing field in the KeyRingAccount table. It is a foreign pointer to the ID of the KeyRing table. Can you describe how to reproduce the issue?

I rescanned the blockchain for a particular keyring used in the faucet. The scan was done from scratch. There was no previous database in that system. I will send the mnemonic to you by encrypted email.

It seems the problem happens with SQLite but not MySQL. Will look further into it.

Solved in newest code.


Update FlowStats_all.R

Changing length + grep to grepl

Changes Unknown when pulling 007900d6a682dcd837002b980c776a309df2af86 on doug-friedman:patch-3 into ** on USGS-R:master**.

Hi Doug,
Thanks for the PR. I will review it soon. However, you should know I am in the middle of a package overhaul of EflowStats to improve it's performance, make the code more concise and maintainable, and improve the user experience.
I think it will be substantially more user friendly and definitely MUCH faster.


⚠ GreatPosterWall has degraded performance

In ebded48, GreatPosterWall ($GPW) experienced degraded performance:

HTTP code: 200
Response time: 2417 ms

Resolved: GreatPosterWall performance has improved in 9fd2ab9.


Add a cookie consent/information dialog/notice

Is your feature request related to a problem? Please describe.
We should indicate to users that we use cookies on the site.
Describe the solution you'd like
Can use spatie/laravel-cookie-consent to add the feature, but will likely need designs to match the site look and feel.
Describe alternatives you've considered
Implement our own solution, similar to the mechanism used by #1604 to show the language confirmation.
Additional context
Will need to assess the accessibility of spatie/laravel-cookie-consent.

Design: https://www.figma.com/file/AXufBnFAVHvGdsxnQMVhNF/The-Accessibility-Exchange-Wireframes?node-id=7473%3A118646&t=Vg6IkRBfkXDN2uQY-1


About collect images for calibration.

Hello,
I followed the instructions in https://github.com/OpenDriveLab/ThinkTwice/blob/main/camera_calibration/README.md and spent several days installing UE4 and Carla. However, when I run collect_data_for_calibration.py, I found that there is no calibration checkerboard in the scene, and the camera perspective does not change. Each frame collected is the same, which cannot be used to calculate distortion parameters with calculate_distortion_parameters.py.
Could you please provide any suggestions about this situation?

Additionally, I originally planned to change the camera resolution to 900x256, FOV to 100, front_camera position to x=1.3,y=0,z=2.5 and set undistort to False, so I don't need to calculate distortion parameters. But there are still some parameters in the transformation matrices that I don't know how to set.
Regarding LIDAR2IMG:
LIDAR2IMG = {
    "rgb_front":np.array([[800.0,<PHONE_NUMBER>4, 0.0, -1200.0], [450.0, 0.0, -214.35935394, -139.10161515000004], [1.0, 0.0, 0.0, -1.5], [0.0, 0.0, 0.0, 1.0]]),

I can see that 800 and 450 are half of the original width 1600 and height 900, and 214.359 corresponds to parameters that can be directly calculated from the image resolution and FOV. After changing the camera settings, this should be changed to 377.594.
The value of 1200 seems to be related to the camera position, so I still can make a guess about what value should be set for this parameter after changing the camera settings, But I don't know what 139.1016 represents. Therefore, I plan to follow the instructions in https://github.com/OpenDriveLab/ThinkTwice/blob/main/camera_calibration/README.md to see if it can be calculated by calculate_distortion_parameters.py. However, it seems that there are some problems with the process of collecting images for calibration, which is a bit confusing.
Before possible reply, I will continue to try to solve this problem by myself. If I can solve it successfully, I will close this issue on my own.

Current progress: I directly extracted the compressed files downloaded from IBISCape into the map folder, instead of creating a separate folder within the map folder to store them. Now I can see the calibration board.

Now I have collected some images for calibration and obtained some parameters by running calculate_distortion_parameters.py, but these parameters seem to have nothing to do with 139.1016?
Camera matrix :

[[214.28235796   0.         799.5       ]
 [  0.<PHONE_NUMBER>4 449.5       ]
 [  0.           0.           1.        ]]
Distortion Matrix :

[[ 2.98099705e-03 -4.35741787e-03 -5.61294835e-05  1.27164886e-05
   1.80059518e-03]]
rvecs :

(array([[0.22166708],
       [0.23211306],
       [1.58715942]]), array([[0.20972128],
       [0.20671492],
       [1.57471855]]), array([[0.10820797],
       [0.10391412],
       [1.57302881]]), array([[0.50355373],
       [0.48164285],
       [1.50607193]]), array([[0.45873178],
       [0.45762182],
       [1.52581263]]), array([[0.45941141],
       [0.4598727 ],
       [1.52925688]]), array([[0.23872499],
       [0.2616931 ],
       [1.55377912]]), array([[0.45415101],
       [0.44368763],
       [1.53894023]]), array([[0.42452736],
       [0.40566571],
       [1.55872336]]), array([[0.2716295 ],
       [0.28624505],
       [1.58581533]]), array([[0.46011214],
       [0.45866348],
       [1.52386996]]), array([[0.08822307],
       [0.08204556],
       [1.57440487]]), array([[0.00347659],
       [0.03479309],
       [0.00905184]]), array([[0.56930725],
       [0.55490375],
       [1.49517161]]), array([[0.46209434],
       [0.46135466],
       [1.53002564]]), array([[0.19148223],
       [0.18293333],
       [1.57392301]]), array([[0.45955071],
       [0.45793221],
       [1.52471733]]), array([[0.45750716],
       [0.4553597 ],
       [1.52393647]]), array([[0.39585859],
       [0.38174277],
       [1.55457805]]), array([[0.33984159],
       [0.33644849],
       [1.55513569]]), array([[0.10041518],
       [0.09533827],
       [1.57324022]]), array([[0.00378244],
       [0.0888063 ],
       [0.00631415]]), array([[0.23874479],
       [0.2573771 ],
       [1.59453126]]), array([[0.44493193],
       [0.42638195],
       [1.55320535]]), array([[0.36492549],
       [0.358147  ],
       [1.5518794 ]]), array([[0.45911729],
       [0.45845451],
       [1.52741744]]), array([[-0.0466223 ],
       [ 0.05257099],
       [-1.56246822]]), array([[-0.04492518],
       [ 0.33337589],
       [-0.00070372]]), array([[0.00424974],
       [0.00491133],
       [0.01047056]]))
tvecs :

(array([[ 6.59723144],
       [-4.77955409],
       [ 9.6155787 ]]), array([[ 6.23746009],
       [-4.95289208],
       [ 9.62410831]]), array([[ 4.72545169],
       [-5.01703479],
       [ 9.46942248]]), array([[ 9.7733353 ],
       [-5.18042499],
       [10.18032002]]), array([[ 9.51692199],
       [-4.98669711],
       [ 8.62480518]]), array([[ 9.53951498],
       [-4.9755155 ],
       [ 8.85589948]]), array([[ 5.98607525],
       [-5.0324915 ],
       [13.68420973]]), array([[ 9.42421348],
       [-4.95611648],
       [ 8.21378837]]), array([[ 9.07502163],
       [-4.95155019],
       [ 8.31267258]]), array([[ 7.35116272],
       [-4.70289733],
       [ 9.36909196]]), array([[ 9.50337616],
       [-4.98920092],
       [ 8.37361719]]), array([[ 4.44395759],
       [-5.00953886],
       [ 9.36904114]]), array([[-2.34885378],
       [-5.05964229],
       [ 9.56202647]]), array([[10.86401171],
       [-5.07950019],
       [ 8.08573514]]), array([[ 9.58901652],
       [-4.96930508],
       [ 8.93467486]]), array([[ 5.90826339],
       [-4.99996169],
       [ 9.67476568]]), array([[ 9.50968227],
       [-4.98894112],
       [ 8.49963576]]), array([[ 9.46067274],
       [-4.98651146],
       [ 8.28380494]]), array([[ 8.7098112],
       [-4.9658785],
       [ 8.5301649]]), array([[ 7.99445368],
       [-4.95371473],
       [ 8.92081057]]), array([[ 4.61540717],
       [-5.01409643],
       [ 9.40557943]]), array([[-1.75666834],
       [-5.04612606],
       [ 9.8806514 ]]), array([[ 6.95741384],
       [-4.66148217],
       [ 9.56343023]]), array([[ 9.30779252],
       [-4.94145645],
       [ 8.20729119]]), array([[ 8.31617567],
       [-4.96286955],
       [ 8.76270472]]), array([[ 9.52611465],
       [-4.98191613],
       [ 8.74144602]]), array([[-2.08250646],
       [ 0.94791493],
       [ 9.75200973]]), array([[ 0.32376455],
       [-4.93061337],
       [16.35661429]]), array([[-2.66707133],
       [-5.07063039],
       [ 9.3831467 ]]))

Process finished with exit code 0

So, could you please tell me what is the parameter 139.1016 here?
LIDAR2IMG = {
    "rgb_front":np.array([[800.0,<PHONE_NUMBER>4, 0.0, -1200.0], [450.0, 0.0, -214.35935394, -139.10161515000004], [1.0, 0.0, 0.0, -1.5], [0.0, 0.0, 0.0, 1.0]]),

What does it mean? If modify the RGB camera configuration as mentioned above and set undistort to False, do I need to change this parameter? If I don't change it, will it have a significant impact? Because in this case, I really don't know how to modify this parameter.

@xanhug   Hi,  LIDAR2IMG is a mapping from ego coordinate system to image cooridnate system:  it seems that you has not considered the extrinsics (the position of the camera)?
If you set undistort as False, as in the data loading part, it will use the conversion matrix without considering Distortion matrx.  As a result, you do not need to conduct calibration at all (much more simple).  All you need is to get the intrinsics and extrinsics matrix (you could use CARLA api in https://carla.readthedocs.io/en/latest/tuto_G_pedestrian_bones/#camera-geometry) and obtain the LiDAR2Img.
I think the calibration would not influence a lot especially with small fov.

@xanhug Hi, LIDAR2IMG is a mapping from ego coordinate system to image cooridnate system: it seems that you has not considered the extrinsics (the position of the camera)?
If you set undistort as False, as in the data loading part, it will use the conversion matrix without considering Distortion matrx. As a result, you do not need to conduct calibration at all (much more simple). All you need is to get the intrinsics and extrinsics matrix (you could use CARLA api in https://carla.readthedocs.io/en/latest/tuto_G_pedestrian_bones/#camera-geometry) and obtain the LiDAR2Img.
I think the calibration would not influence a lot especially with small fov.

Thanks a lot.


feat(typography): Body font selector scoping

Description
This PR updates the body selector in packages/sage-assets/lib/stylesheets/core/_typography.scss to only apply if the sage-excluded class is not set on body. Then when styles are desired in a scoped context the .sage-scoped class can be used on the closer container.
This will prevent the Inter font from applying to the body which is helpful when using Sage on the member side or other environments. It also ensures any global tag selectors are moved and reconciled in the global reboot file so that core files can be included in a project independently as needed.
We are not documenting this on the docs site as this is not a fully robust solution that we want to publicize yet. Build team is using it in a limited context for the Quizzes redesign effort underway.
Screenshots

Class Applied
Class Not Applied

Testing in sage-lib

Open http://<IP_ADDRESS>:4000/
Ensure that the body font is still Inter or Inter var.

Testing in kajabi-products

In Admin, open the developer tools
Inspect the body element
Add the sage-excluded class to the body element and ensure that Inter var and/or Inter does not get applied. Add sage-scoped at a lower level container to see Sage type apply therein.

Notes
(LOW) Adds some MVP scoping options for Sage to be used in scoped member-facing contexts.
NOTE: Sage Engineering has reviewed this work in a number of kp contexts with the Bridge on and found no regressions.
Related
https://kajabi.atlassian.net/browse/SAGE-156

@JulaB Have you tried adding the sage-scoped class to or around the modal to see if that helps prevent the heading font from overriding Sage?

Have you tried adding the sage-scoped class to or around the modal to see if that helps prevent the heading font from overriding Sage?

Yes, I added it here https://github.com/Kajabi/kajabi-products/pull/22306/files#diff-0e158ff96225a99f22477edde3c3ff8329e3126236182794195c72c22b71fcd0R20 and in other places.


Fix space launch file path

Fix an issue when the path to the launch file contained a space.

Many thanks for your feedback and pull request! We appreciate your contribution. We will add it to the master branch for the next release.

Thanks for your input. We merged this manually into the develop branch.


gnome: moved gnome-shell overlay outside its gnome packages umbrella

Once with this PR https://github.com/NixOS/nixpkgs/pull/338583 got merged the gnome-shell overlay did not have any effect, moreover stylix flake stopped building on the unstable.
This PR removed the outer gnome overlay and let the gnome-shell be modified as a standalone package.
Note: this is the first time I look at stylix codebase and I might have overlooked things. If you think of something missing please ping me.
Edit: The error I got when using the latest nixpkgs master branch:
error:
       … while calling the 'head' builtin

         at /nix/store/gi5jqh2i4djgqz45vljnpz0bhnxdafgv-source/lib/attrsets.nix:1575:11:

         1574|         || pred here (elemAt values 1) (head values) then
         1575|           head values
             |           ^
         1576|         else

       … while evaluating the attribute 'value'

         at /nix/store/gi5jqh2i4djgqz45vljnpz0bhnxdafgv-source/lib/modules.nix:821:9:

          820|     in warnDeprecation opt //
          821|       { value = addErrorContext "while evaluating the option `${showOption loc}':" value;
             |         ^
          822|         inherit (res.defsFinal') highestPrio;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: attribute 'gnome-shell' missing

       at /nix/store/nbcyd1kbx2w64g4qniz4jmss6x19q2f1-modules/gnome/nixos.nix:26:23:

           25|       gnome = super.gnome.overrideScope (gnomeSelf: gnomeSuper: {
           26|         gnome-shell = gnomeSuper.gnome-shell.overrideAttrs (oldAttrs: {
             |                       ^
           27|           # Themes are usually applied via an extension, but extensions are

Once with this PR NixOS/nixpkgs#338583 got merged the gnome-shell overlay did not have any effect, moreover stylix flake stopped building on the unstable.

Consider updating the Nixpkgs input in Stylix to that particular commit to ensure Stylix stays in sync.

@trueNAHO I changed the following in my stylix fork:
- nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
+ nixpkgs.url = "github:NixOS/nixpkgs/ca9576c81da013b7ab7a302990f7928d33e85198";

Then did a nixos-rebuild switch --flake . As expected it builds on this branch but it does not on master.

I changed the following in my stylix fork:
- nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
+ nixpkgs.url = "github:NixOS/nixpkgs/ca9576c81da013b7ab7a302990f7928d33e85198";

Then did a nixos-rebuild switch --flake . As expected it builds on this branch but it does not on master.

Sorry for being unclear: Could you update your patch (this PR) to include the Nixpkgs update in the flake.lock file?

I'm not sure what to commit here. when the next update of nixpkgs-unstable is going to happen this issue is going to affect stylix users.

I am not very familiar with the current GNOME setup. @danth, might be more helpful here.

@trueNAHO I was trying to say that the issue https://github.com/NixOS/nixpkgs/pull/338583 was introduced today and https://github.com/NixOS/nixpkgs/tree/nixpkgs-unstable the changes in abovementioned PR did not reach nixpkgs-unstable yet. The latest commit in nixpkgs-unstable is from yesterday.
However when the changes land in the nixpkgs-unstable branch we will not be able to use stylix with gnome-shell.
So even if I bump the flake version of nixpkgs now it will not have any effect because the master branch of nixpkgs was not merged into nixpkgs-unstable yet.
I'll happily bump the nixpkgs in flake.lock after the mentioned changes lands in nixpkgs-unstable.

Just updated flake.lock as the gnome-shell changes landed in nixpkgs-unstable branch

Edit: I'm going to need some help with the failing tests

I think we need to wait for https://github.com/NixOS/nixpkgs/pull/338836 to land.
Related: https://github.com/danth/stylix/issues/542

I think we need to wait for https://github.com/NixOS/nixpkgs/pull/338836 to land.

Since #544 is merged, rebasing this branch on master should fix the tests since none of them have Hyprland enabled.


vectorstores: add mongovector

resolves https://github.com/tmc/langchaingo/issues/771
The goal of this PR is to provide a way for users to read and write to an Atlas cluster as a vector database using the MongoDB Go Driver.
A Store should be a wrapper for mongo.Collection, since adding and searching vectors is collection-specific. In this case AddDocuments() and SimilaritySearch() become analogues for Collection.InsertMany() and Collection.Aggregate(). This also keeps our implementation inline with the Python driver implementation.
Because a single collection can have multiple vector search indexes, we must provide an option to use a specific embedding when adding a document. However, to ensure there is at least a default behavior [where a user does not have to include an optional embedder] we should require that a default embedder be included at construction. We've chosen to use vectorstores.Options.NameSpace for this purpose.
PR Checklist

[x] Read the Contributing documentation.
[x] Read the Code of conduct documentation.
[x] Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
[x] Describes the source of new concepts.
[x] References existing implementations as appropriate.
[x] Contains test coverage for new functions.
[x] Passes all golangci-lint checks.

@jtazin @matthewdale @qingyang-hu @blink1073

Sorry about the delay here, I'll very likely be able to review this today and have been meaning to cut a new release so this should make it in soon!

Fantastic change! I'm curious what the plan around the go.mongodb.org/mongo-driver/v2 beta tag is -- I don't love depending on a not-declared-stable package version.

we should also get 'go test' to just work via a testcontainer container

we should also get 'go test' to just work via a testcontainer container

Oh I didn't realize this was leveraging a feature not in the F/OSS version of mongo -- is there a reasonable way to fake this so we don't take on a network dependency in CI?


Uncaught error from Chrome <IP_ADDRESS> on Windows 10 Error

Logger: frontend.js.latest.202312082
Source: components/system_log/init.py:300
First occurred: 16:17:57 (1 occurrences)
Last logged: 16:17:57
Uncaught error from Chrome <IP_ADDRESS> on Windows 10 Error /hacsfiles/floor3d-card/floor3d-card.js:2288:34538 Object.s [as onError] (/hacsfiles/floor3d-card/floor3d-card.js:2231:539918) XMLHttpRequest. (/hacsfiles/floor3d-card/floor3d-card.js:2231:436056)

Hello @Trzinka, I must say that since I put the card template I received a lot of tickets in GitHub. When you create a card from the template and then you change the model (removing the reference to the template model), you need to remove all references to the template objects in the entity and the object groups.

Closing as stale for 2 months


Feature Request: DatePart in InfluxQL

Can we have InfluxQL support DatePart which is supported in almost all SQL engines? The use case is to analyze long term trend over a wide time scale, but only part of the range.
Example use cases.

Server utilization during business hours, we will have a data point at every 10 seconds, but we want to trend business hour vs non business hour utilization
Data/requests/hit volume on first of the month over time, we can always have a grafana plot the entire timescale, but that kind of overloads the analysis, I rather have a graph where I can compare 1st of every month data over last 10 years.

Proposal:
Have support for DatePart with only one argument (as we have the timescale as fixed argument), which will apply the filter on the timescale.
e.g. Select * from Host_Metrics where DatePart(hour)>8 and DatePart(hour)<17

+1 for such functionality. Any progress on that topic?

+1

+1

+1

+1

+1

+1

I think this is still relevant.

Influx data seems to have found a nice way to decrease open issue counts drastically.. Just close all of them for which team hasn't committed to fix or provided an alternative solution in years..

Still relevant.

+1

This feature would be very helpful.

+1

+1

I would also like this feature very much. +1

DatePart-like functionality is available in Flux using the hourSelection() function.
It likely won't be added InfluxQL.

@sanderson - an hour selector addresses the first example use case, but not the second, nor the ability to analyze long term trend over a wide time scale, but only part of the range..
In Flux, is it possible to use date in a filter function, to more dynamically filter time slices?

@cruscio Sure, here's a quick example:
import "experimental"
import "date"

from(bucket:"example")
  // Query data from the last 12 months
  |> range(start: -12mo)
  // Filter by measurement and field
  |> filter(fn: (r) => r._measurement == "m_example" and r._field == "f_example")
  // Use the date.monthDay() function to return only data from the first of each month
  |> filter(fn: (r) => date.monthDay(t: r._time) == 1)
  // Add the month as a tag on each month
  |> map(fn: (r) => ({ r with month: date.month(t: r._time)}))
  // Add the month column to the group key so each month's first day is a separate table/series
  |> experimental.group(columns: ["month"], mode: "extend")
  // Align all the data to a starting time so you can directly compare hours of each 1st day.
  |> experimental.alignTime()

This will return data that, when visualized, looks something like this:

I worked 30 years with db2 and oracle and also 10 years with mysql. I'm very surprised what problems the influxdb users have.

It is really an essential feature for many applications to select records based on a time of the day, not only an absolute time stamp.
So many people having that issue and no progress...  :(

It is really an essential feature for many applications to select records based on a time of the day, not only an absolute time stamp.
So many people having that issue and no progress...  :(

@teichhei What you're looking for is accomplished with hourSelection() function. This filters results to only points within hours of each day:
from(bucket:"example-bucket")
  |> range(start:-90d)
  |> filter(fn: (r) => r._measurement == "example-measurement" )
  |> hourSelection(start: 9, stop: 17)

@teichhei What you're looking for is accomplished with hourSelection() function. This filters results to only points within hours of each day:
from(bucket:"example-bucket")
  |> range(start:-90d)
  |> filter(fn: (r) => r._measurement == "example-measurement" )
  |> hourSelection(start: 9, stop: 17)

Yeah can’t get my head around flux.
I might have to if that’s where it is heading but I find it horrible.
From: Scott Anderson<EMAIL_ADDRESS>Sent: Thursday, 7 January 2021 23:54
To: influxdata/influxdb<EMAIL_ADDRESS>Cc: Heinz Teichmann<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [influxdata/influxdb] Feature Request: DatePart in InfluxQL (#6723)
@teichheihttps://github.com/teichhei What you're looking for is accomplished with hourSelection() functionhttps://docs.influxdata.com/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/hourselection/. This filters results to only points within hours of each day:
from(bucket:"example-bucket")
|> range(start:-90d)
|> filter(fn: (r) => r._measurement == "example-measurement" )
|> hourSelection(start: 9, stop: 17)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/influxdb/issues/6723#issuecomment-756202744, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP6G3B5NYL65O4DT6H2PFODSYXKLHANCNFSM4CEZUB6A.

It would be great to be able to group the results by date part (hour for example). Is this possible?

@cruscio Sure, here's a quick example:
import "experimental"
import "date"

from(bucket:"example")
  // Query data from the last 12 months
  |> range(start: -12mo)
  // Filter by measurement and field
  |> filter(fn: (r) => r._measurement == "m_example" and r._field == "f_example")
  // Use the date.monthDay() function to return only data from the first of each month
  |> filter(fn: (r) => date.monthDay(t: r._time) == 1)
  // Add the month as a tag on each month
  |> map(fn: (r) => ({ r with month: date.month(t: r._time)}))
  // Add the month column to the group key so each month's first day is a separate table/series
  |> experimental.group(columns: ["month"], mode: "extend")
  // Align all the data to a starting time so you can directly compare hours of each 1st day.
  |> experimental.alignTime()

This will return data that, when visualized, looks something like this:

When I do that on my data, Chronograf can't display the result as a graph. Also, the different tables of the result can't be clicked in table-mode. Can you help me?

DatePart-like functionality is available in Flux using the hourSelection() function. It likely won't be added InfluxQL.

Fast forward to year 2023 and at the docs page we see:

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

So for InfluxDB 2.0 we should use Flux for this date-time functionality but starting with InfluxDB 3.0 this will be ported to InfluxQL?

It still isn't likely that date-part functionality is going to to be added to InfluxQL, however, 3.0 natively supports SQL and the SQL implementation does support a date_part function.

Thank you for the quick reply. I didn't realize that SQL and InfluxQL are two different supported query languages. The page The Plan for InfluxDB 3.0 Open Source explains this and a lot more.


CLI should support http proxy

The CLI connects directly to the API HOST on default port 443
But if the user needs to use an http proxy (very typical inside corporations) the CLI needs to provide a way for the user to use the WSK CLI.
We should take same approach as CF CLI, using an environment variable
https_proxy
If you have an HTTP proxy server on your network between a host running the cf CLI and your Cloud Foundry API endpoint, you must set https_proxy with the hostname or IP address of the proxy server.

The https_proxy environment variable holds the hostname or IP address of your proxy server.

https_proxy is a standard environment variable. Like any environment variable, the specific steps you use to set it depends on your operating system.

Format of https_proxy
https_proxy is set with hostname or IP address of the proxy server in URL format: https_proxy=http://proxy.example.com

If the proxy server requires a user name and password, include the credentials<EMAIL_ADDRESS>
If the proxy server uses a port other than 80, include the port number: https_proxy=http://username:password@proxy.example.com:8080

Some more notes
It looks like http_proxy is something that the golang http library handles, user can use both HTTP_PROXY or http_proxy
If we use the golang net http library to connect to openwhisk API it should be easy to implement, but as always we will need to write some test cases to have confident in the integration.
cc @dubeejw @mdeuser

Closed by #612.

The Go CLI may not have this feature, and #612 did not add a test when this feature was added to the Python CLI.
@mdeuser @dubeejw FYI.

Added for Python CLI with tests as part of #925 as I ran into the need for this. There is a tangentially related issue for the Go CLI in #924.

It looks like setting an environment variable for HTTP_PROXY, or HTTPS_PROXY will cause the Go CLI to use a proxy. Would need a proxy to verify this though.

Starting test Wsk CLI usage should show api build using http apihost at 2016-07-30 11:07:53.774
expected exit code = 0
exit code = 3
stdout: whisk API host
whisk API build		 Unknown

stderr: error: Unable to obtain API build information: Request failure: Get https:///api/v1: http: no Host in request URL

@dubeejw @mdeuser supporting http proxy very important to users behind corporate firewall.

@csantanapr, I believe @rabbah comment above is not related to proxy support. As I stated above we need a proxy to test with.

@dubeejw OK, I think I miss interpreted @rabbah comments then.
I think using a container that runs the proxy for our tests will be ideal.

@csantanapr, I believe the HTTP transport package we are using supports HTTP, and HTTPS proxies by default. I do not believe SOCKS5 is supported. Here's an excerpt from the package's documentation (https://golang.org/pkg/net/http/).
DefaultTransport is the default implementation of Transport and is used by DefaultClient. It establishes network connections as needed and caches them for reuse by subsequent calls. It uses HTTP proxies as directed by the $HTTP_PROXY and $NO_PROXY (or $http_proxy and $no_proxy) environment variables.

@csantanapr, looks like CF utilizes the same technique for proxy support. Here's a link to their doc: https://docs.cloudfoundry.org/cf-cli/http-proxy.html.

Yes I was aware of CF CLI and BluemIx CLI supporting some soft of http proxy.
OK So it looks like all we are todo is document the support similar to bluemix

Note: If your network contains an HTTPS proxy server between the host that runs the CLI and the Bluemix, you must specify the host name or IP address of the proxy server by setting the HTTPS_PROXY environment variable.

HTTPS proxy support definitely works currently with the Go CLI, I just tried it out.

@dubeejw want to close this one?


[QUESTION] Using named routes in the config file

config/adminlte.php:
return [
    // ...
    'menu' => [
        // ...
        [
            'text' => 'Categories',
            'url'  => 'category.index', // this doesn't work, '/category.index' page is not found
            'icon' => 'fas fa-list'
        ],
        // ...
    ],
    // ...
];

And here is the named route itself:
Route::group(['prefix' => 'categories'], function () {
    Route::get(
        '/', \App\Http\Controllers\Category\IndexController::class
    )->name('category.index');
    // ...
});

How can I use a named route when configuring AdminLTE? Thanks in advance!

@loglinn05 Use route key instead of url. Check docs here.

Ahh, thank you so much! It works. Good luck! Bye!


zlib: Add comments regarding static/shared linking

The main explanation was taken from commit:
e999def1 zlib: clean up static/shared distincion

The SHARED_MODE=1 bit was originally introduced in commit:
0bfc84b0 Cross-compile zlib for Windows

Motivation
Spending hours to figure out why the zlib build behaves different from other builds, and how.
I don't claim the current approach is good, but at least now it's explained.
Things done

[x] Comments-only change
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

@nh2 thank you!


Redirect after play?

Hey people. It's actually a question that I have. I need to redirect the page after the entire video is played.
Tried to compare getCurrentTime() and getDuration(), but didn't get too far.
Any ideas?

You probably want to listen to the ended event


Function: fix missing metadata load

This version is a bit lighter by not requiring a full override of the cattr structure method to handle other formats (bonus is this doesn't suppress some of the automatic checks cattr does.

This looks much cleaner to me. Nice!

Ok, great, thanks. We do need to finalise the list of acceptable forms in functions/parameters though and record them some where, ideally in the example


Handle Multiple Entities While Filtering By VideoId and Validity Range

We are getting some crashes due to multiple instances being selected:
var storedObj = dlContext.Videos.SingleOrDefault(v => v.VideoId == newObj.VideoId && v.ValidityStart <= now && now < v.ValidityEnd);

In the example above, that filtering returns multiple instances, so SingleOrDefault raises an exception, and the fetcher crashes.
We change it to LastOfDefault.

@josiasal This is not right.
Note that we filter by validity, meaning there can only be 1 or 0. .SingleOrDefault is performing an implicity a validity check. Switching to .LastOrDefault hides the inconsistency.
What you need to do is fix in the database, by invalidating the older row. I.e. the validity end of the older row should be equal to the validity start of the newer row.
The question remains regarding why/how such inconsistency came to be.

@filipelbc-ba, see the updated code.


Change env var prefix

Describe the problem
Vite will now let you change VITE env var prefix to be something else like PUBLIC or CLIENT
Describe the proposed solution
https://github.com/vitejs/vite/pull/4676
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

Do we have to do something? I mean, if it is on the vite config we just need to bump the version of vite right?

yeah. and I think we should change our default and document it

Maybe KIT? Would it make sense to expose it in the config, because it would be a breaking change?

I sent a PR to accept both VITE_ and PUBLIC_ so that it won't break existing applications

Isn't this just an extra thing people have to learn? If someone knows Vite (and to become expert in SvelteKit, they will eventually need to know their way around Vite, at least a bit) then they will know about VITE_, and if they see it without context then they'll likely understand that it's a Vite feature (and therefore that they can learn about it on https://vitejs.dev/).
By contrast I don't think I would immediately know what PUBLIC_ was unless I happened to have read the relevant part of the docs (or rather the FAQs, per #2355). It feels like this could be left to user config, rather than increasing the surface area of SvelteKit-specific idioms that people need to learn.

It is an extra thing to learn to some extent, but if you don't know about PUBLIC_ I don't think there's much harm that would come from it. You'd simply create all your environment variables with a VITE_ prefix instead and you could carry on your marry way in bliss. Or if you read code in a project you weren't familiar with and you saw PUBLIC_ you might not know that was needed to access it on the client, but by the same respect you also wouldn't know that VITE_ was needed either unless you read the docs or had some prior Vite familiarity. The worst thing that would happen in that case is you might create one with a VITE_ prefix when the project was using a PUBLIC_ prefix and it'd be an extra comment in code review

Is there a specific reason why you suggest PUBLIC_? It's a pretty well-established pattern generally to use the framework name as a prefix is it not?. VITE_, REACT_APP_, etc. My first thought would probably be to use KIT_, though I don't have any strong opinions on that.
I agree that, though the reasons make sense, it has always been a little weird to put VITE_ everywhere when the immediate framework is SvelteKit.

I didn't know that was becoming a pattern. I hadn't seen REACT_APP_ before. It looks like there's also SNOWPACK_PUBLIC_. I'm not sure it's a pattern I particularly like, but I guess it is what it is. In my mind it seems odd to name your variables after the framework you're using. PUBLIC_ is more informative and denotes what it does. But it is harder to discover if you need to search for it since it's less unique

I'm going to go ahead and close this. Everyone's got a bit different opinion about it and it would make the behavior diverge from VITE which might add as much confusion as it would solve. If you'd like to configure this, you can do so in your svelte.config.js

This may have already shipped (?), but I'd opine that something like GLOBAL_ or KIT_ is easier to make sense of than PUBLIC_ from a first comers perspective. public...what? Public has very different connotations in different scenarios.

this was left as VITE_. you can configure it on a per-project basis using the Vite configuration options


USB connection

USB connection
"A drawback of the Apple Virtualization framework is that there is no implementation for USB forwarding as of when I'm writing this. Therefore, these scripts set up the Xilinx Virtual Cable protocol. Intended to let a computer connect to an FPGA plugged into a remote computer, it allows for the host system to run an XVC server (in this case a software called xvcd by Felix Domke), to which the docker container can connect.

xvcd is contained in this repository, but with slight changes to make it compile on modern day macOS (compilation requires libusb and libftdi installed via homebrew, though there is a compiled version included). It runs continuously while the docker container is running.
This version of xvcd only supports the FT2232C chip. There are forks of this software supporting other boards such as xvcserver by Xilinx."
Will we ever see USB connection work on mac? i have a usb adapter on my mac and was wondering if it would work
Thank you!

It is theoretically possible to have support to directly forward the USB connection to the Docker container but as of now there is no implementation of that. In the mean time, we're stuck with xvcd.


Remove isValidDimensions

bug
Since a second monitor could have a negative displacement compared to the first monitor, the original logic leads to false negatives.
See #15109
Keyword for detection: Fixes https://github.com/atom/atom/issues/15019
Edit: See comment directly below https://github.com/atom/atom/pull/22973#issuecomment-924168285
Explain change
Since isValidDimensions has a bug, and it's not needed anymore (see comment below) it can be removed
Possible Drawbacks
none?
Verification Process
None. I haven't made tests for this yet, so this is a draft.
Release notes
Fix false negatives when checking if window dimensions can be stored.

@icecream17  I don't think we need the isValidDimensions check anymore. Even when a window is minimized,  browserWindow.getPosition() is still able to give correct window dimensions.
  storeWindowDimensions() {
    this.windowDimensions = this.getWindowDimensions();
    localStorage.setItem(
      'defaultWindowDimensions',
      JSON.stringify(this.windowDimensions)
    );
  }

I would also encourage you to think about what happens when you quit Atom, disconnect the second monitor and reopen Atom from your laptop alone.
Do you mind updating this PR?

I think I understand, the code shouldn't reopen the window in an impossible-to-see location. (Which originally corresponded to a disconnected screen.)
Also my last commit is invalid, since getDefaultWindowDimensions calls isValidDimensions. So isValidDimensions should be reimplemented to check whether the dimensions are visible or not.
(Note: It might take a while for me to code that)

@icecream17 The dimensions will always be valid. The invalid dimensions were a result of a bug in electron where if the window was minimized it returned invalid dimensions. Now, this is not the case since that bug has been fixed on electron. We don't need to reimplement isValidDimensions.

I'm not sure how to turn screens on/off. Maybe I should just manually check


Question about paid apps

Hi,
Just curious to know what happens if I install paid app that I haven't purchased yet ? is there some kind of warning that says I will be charged ?. Compare to apps that you have paid for already ?
thanks

Hi @lanox! Currently mas is able to install applications only from your "Purchased" list. See #46 for details.


Provide more stats on each platform message

When optimizing for latency, it is helpful to identify interesting platform messages. These can be, but is not limited to:

Platform messages that send a large amount of data
Platform messages that take a long time in the method codecs during encoding and decoding
Platform messages that wait a long time when jumping from the Dart UI thread to the host task queue (for that platform channel)
Platform messages that wait a long time when jumping from the host task queue to the Dart UI thread
Platform messages handlers (e.g. onMethodCall) that take a long time to run

This can guide performance work by developers. For example, if a platform message takes a long time to jump from the Dart UI thread to the host task queue, such as in instances where the platform thread servicing the default host task queue is blocked, one option would be to use a background task queue for that channel.
Related is https://github.com/flutter/flutter/pull/104531 which provides aggregated stats on the platform messages, but we would like similar data for each platform message.
go/flutter-e2e-pm-hack is an internal document that explains a hack for this in more detail, by passing down an identifier from Dart to the engine and host to track the platform message invocation, and then using a perfetto query to parse the timeline events. There are probably better ways to do this though, and it would be nice if this can be eventually integrated into devtools in some sort of table.
cc @gaaclarke @kenzieschmoll

I think the way you have the data laid out per platform channel message is clear and nice.  I'm not convinced yet that it is worth the runtime cost and engineering cost.

Platform messages that send a large amount of data

The aggregate data we already have can give you this information per channel.  I'm not sure it is helpful to the developer to be able to pinpoint specifics via an enumeration that they didn't specify.

Platform messages that take a long time in the method codecs during encoding and decoding

This is mostly just a function of the payload size.  CPU profilers can give us this information but not tie it back directly to a channel.

Platform messages that wait a long time when jumping from the Dart UI thread to the host task queue (for that platform channel)
Platform messages that wait a long time when jumping from the host task queue to the Dart UI thread

We have timeline events for that now.

Platform messages handlers (e.g. onMethodCall) that take a long time to run

CPU profilers can tell us that.  Maybe you are making the case that we shouldn't have to rely on CPU profilers to get this information?

I agree as well that it may not be worth the cost of building this, let's look at the data first in the prototype and see what action items we can find before we invest more into building a full-fledged solution.


Message provider verification error: "Caught panic with error: failed printing to stdout"

Software versions

OS: Mac OSX 14.4.1
Consumer Pact library: Pact JS 12.3.0
Provider Pact library: Pact JS 12.3.0
Node Version: v16.20.2

Issue Checklist
Please confirm the following:

[x] I have upgraded to the latest
[x] I have the read the FAQs in the Readme
[x] I have triple checked, that there are no unhandled promises in my code and have read the section on intermittent test failures
[x] I have set my log level to debug and attached a log file showing the complete request/response cycle
[x] For bonus points and virtual high fives, I have created a reproduceable git repository (see below) to illustrate the problem

Expected behaviour
Pact verification is successful.
Actual behaviour
Pact verification is unsuccessful with error:
thread '<unnamed>' panicked at library/std/src/io/stdio.rs:1021:9:
failed printing to stdout: Resource temporarily unavailable (os error 35)
stack backtrace:
   0:        0x11643b088 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hb478ebbfb46e27ce
   1:        0x11645d588 - core::fmt::write::he4d5fa2daff1f531
   2:        0x116437ccc - std::io::Write::write_fmt::hc5a47a68eba63d9f
   3:        0x11643aebc - std::sys_common::backtrace::print::h79bd952cc5812e7a
   4:        0x11643c5e0 - std::panicking::default_hook::{{closure}}::h82301f6222887737
   5:        0x11643c328 - std::panicking::default_hook::h1e49abbb3f1d7dbf
   6:        0x11643ca28 - std::panicking::rust_panic_with_hook::h1e70c5d905e30e9d
   7:        0x11643c91c - std::panicking::begin_panic_handler::{{closure}}::h399e32952efd26a4
   8:        0x11643b50c - std::sys_common::backtrace::__rust_end_short_backtrace::h2ab87f841a2323e7
   9:        0x11643c6a4 - _rust_begin_unwind
  10:        0x1164bc61c - core::panicking::panic_fmt::h33e40d2a93cab78f
  11:        0x116436ce0 - std::io::stdio::_print::h2c869062e4130656
  12:        0x1157da3cc - pact_verifier::verify_provider_async::{{closure}}::{{closure}}::hc20d3590fb2780e7
  13:        0x115812b4c - <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll::h6192e06b5541dff5
  14:        0x1158852f8 - <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll::h15b2b04a4836487e
  15:        0x11588c490 - pact_verifier::verify_provider_async::{{closure}}::hdfb4a205a57c5fce
  16:        0x1158b0df8 - tokio::runtime::park::CachedParkThread::block_on::hbe826fd4bc423331
  17:        0x11595eea4 - tokio::runtime::context::runtime::enter_runtime::hcc547b869e4394a4
  18:        0x1159dc5e8 - tokio::runtime::runtime::Runtime::block_on::h125b509c5d36c1d2
  19:        0x115967a48 - pact_ffi::verifier::handle::VerifierHandle::execute::hf5436875cfce2f47
  20:        0x115a01978 - pact_ffi::error::panic::catch_panic::h1a10465fee822ae2
  21:        0x11598758c - _pactffi_verifier_execute
  22:        0x104faa964 - __ZN18VerificationWorker7ExecuteEv
  23:        0x104faa6a4 - __ZN4Napi11AsyncWorker9OnExecuteENS_3EnvE
  24:        0x100d39ed8 - _worker
  25:        0x197bc6f94 - __pthread_joiner_wake
Caught panic with error: failed printing to stdout: Resource temporarily unavailable (os error 35)
[15:31:20.709] ERROR (40657<EMAIL_ADDRESS>Verification unsuccessful

Steps to reproduce
Minimal example below, instructions in README:
https://github.com/qmg-rbass/pact-bug-2
Looks to me like it is caused by having a large number of messages to verify. This minimal example uses 128 dummy messages in the same pact file. But we see the same error in a real project with ~45 different messages, spread across several files on a pact broker.
The minimal example fails every time. In the case of the real project it is based on, we interestingly see the error ~80% of the time, with verification eventually successful after multiple retries.
Relevant log files
[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailablethread '<unnamed>' panicked at library/std/src/io/stdio.rs:1021:9 (os error 35)
:
failed printing to stdout: Resource temporarily unavailable (os error 35)
[tracing-subscriber] Unable to write an event to the Writer for this Subscriber! Error: Resource temporarily unavailable (os error 35)
stack backtrace:
   0:        0x112253088 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hb478ebbfb46e27ce
   1:        0x112275588 - core::fmt::write::he4d5fa2daff1f531
   2:        0x11224fccc - std::io::Write::write_fmt::hc5a47a68eba63d9f
   3:        0x112252ebc - std::sys_common::backtrace::print::h79bd952cc5812e7a
   4:        0x1122545e0 - std::panicking::default_hook::{{closure}}::h82301f6222887737
   5:        0x112254328 - std::panicking::default_hook::h1e49abbb3f1d7dbf
   6:        0x112254a28 - std::panicking::rust_panic_with_hook::h1e70c5d905e30e9d
   7:        0x11225491c - std::panicking::begin_panic_handler::{{closure}}::h399e32952efd26a4
   8:        0x11225350c - std::sys_common::backtrace::__rust_end_short_backtrace::h2ab87f841a2323e7
   9:        0x1122546a4 - _rust_begin_unwind
  10:        0x1122d461c - core::panicking::panic_fmt::h33e40d2a93cab78f
  11:        0x11224ece0 - std::io::stdio::_print::h2c869062e4130656
  12:        0x1115f23cc - pact_verifier::verify_provider_async::{{closure}}::{{closure}}::hc20d3590fb2780e7
  13:        0x11162ab4c - <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll::h6192e06b5541dff5
  14:        0x11169d2f8 - <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll::h15b2b04a4836487e
  15:        0x1116a4490 - pact_verifier::verify_provider_async::{{closure}}::hdfb4a205a57c5fce
  16:        0x1116c8df8 - tokio::runtime::park::CachedParkThread::block_on::hbe826fd4bc423331
  17:        0x111776ea4 - tokio::runtime::context::runtime::enter_runtime::hcc547b869e4394a4
  18:        0x1117f45e8 - tokio::runtime::runtime::Runtime::block_on::h125b509c5d36c1d2
  19:        0x11177fa48 - pact_ffi::verifier::handle::VerifierHandle::execute::hf5436875cfce2f47
  20:        0x111819978 - pact_ffi::error::panic::catch_panic::h1a10465fee822ae2
  21:        0x11179f58c - _pactffi_verifier_execute
  22:        0x1079fe964 - __ZN18VerificationWorker7ExecuteEv
  23:        0x1079fe6a4 - __ZN4Napi11AsyncWorker9OnExecuteENS_3EnvE
  24:        0x103791ed8 - _worker
  25:        0x197bc6f94 - __pthread_joiner_wake
Caught panic with error: failed printing to stdout: Resource temporarily unavailable (os error 35)
[15:34:07.729] DEBUG (40817<EMAIL_ADDRESS>shutting down verifier with handle 0
  foo message (0s loading, 86ms verification)
2024-05-08T14:34:07.704745Z DEBUG tokio-runtime-worker Connection{peer=Client}: h2::codec::framed_write: send frame=GoAway { error_code: NO_ERROR, last_stream_id: StreamId(0) }
2024-05-08T14:34:07.705403Z DEBUG tokio-runtime-worker Connection{peer=Client}: h2::proto::connection: Connection::poll; connection error error=GoAway(b"", NO_ERROR, Library)
2024-05-08T14:34:07.729598Z DEBUG ThreadId(01) pact_ffi::verifier: pact_ffi::verifier::pactffi_verifier_shutdown FFI function invoked
[15:34:07.729] DEBUG (40817<EMAIL_ADDRESS>response from verifier: null, 1
[15:34:07.729] ERROR (40817<EMAIL_ADDRESS>Verification unsuccessful

Moving this back to pact-js, it is a Node issue.
Looks like process.stdout._handle.setBlocking(true) before calling the FFI methods resolves the issue.


Add order by on list

Similar than this (image):
http://crud-admin-generator.com/images/list.png

First should be updated to the latest version: https://github.com/patcito/angularjs_scaffold/issues/24


updated membership bot for orders

Another big update. Updates will get smaller from here on out.
Basic details:

All orders are pulled from Jan 1st, spreadsheet is recreated everytime it's run
Recreating the spreadsheet was easier than reconciling orders for things like mooring services that happened after the initial transaction
There are two different spreadsheets created, one for orders and one for the dock
The spreadsheet for the dock has two tabs, one for memberships and one for moorings
TODO items are to add sailing lesson schedules into the spreadsheet

This needs just one slight change. A Lambda handler (main in this case) requires the event and context.


Fix typo in README.md

Fixed a typo in docker built -t sweagent/swe-agent-run:latest . corrected to build

Thanks!


Have problems with the huge-apps example.

When I use webpack-dev-server to automatic refresh the page, it doesn't work when I change codes of the component. However,  it works when I change codes of the router config files.

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router, and per the issue template, we are not handling support requests here.
If you have a question or otherwise need help, please post on Stack Overflow with the #react-router tag at https://stackoverflow.com/questions/ask?tags=react-router, or drop in on the #react-router room on Reactiflux at https://discord.gg/0ZcbPKXt5bYaNQ46.


Allow multiple classes on level up like the nice one in KM

Got a collaborator who is willing to help with this (thanks YukiHamster).  Built a prototype UI and data parts.

Would love to see this


chore: move all env to one package

Summary
Create a new package env and move all env defined and used in all packages to it.
How was it tested?

I'll create a following PR to add a new file utils.go in package env to provide utility functions for these envs.

has some conflicts. Could you rebase and update, please?

has some conflicts. Could you rebase and update, please?

Done. PTAL


Jenkinsfile template for integration tests

Motivation
https://issues.jboss.org/browse/AEROGEAR-2207
Description

Jenkinsfile should contain configuration and commands for running only integration tests
Integration test will be triggered only when PR contains label "test/integration"
Implementation of integration test itself is currently blocked by https://issues.jboss.org/browse/AGIOS-675

Progress

[x] Jenkinsfile template for testing Mac OSX slave
[x] Integration test

@psturc Great stuff. Could we also disable reporting status back for non integration tests? I do not see label "integration test" - did you meant comment?

Ignore my previous comment. My only recomendation is to use "test/integration" label. I created that label for you

@psturc Good to go!

@wtrocki I think this PR is ready to be merged.
However, there's maybe one thing worth considering.
I was struggling with adding more tests, because they would have to be separated from regular unit tests (they would fail in 🔵 CI). And I did not find a nice way how to do the separation.
The only thing that worked, was renaming the tests to not start with name "test" so they are not triggered via xcodebuild or fastlane if you do not specify them, like here. But that's not nice solution IMO.
Wdyt? Is there another way how we could achieve the separation of tests?

@psturc Let's not hack things around. You need to create separate target for your tests and put tests into target. For example: http://rshankar.com/create-new-test-target-in-xcode/
As for current PR it's ok to merge and work on follow up PR's.

@psturc Follow up tasks:

[ ] Create separate target for functional tests
[ ] Move tests to new target (or create new ones)
[ ] Add info to contribution guide for integration tests (this should be technically adde to every bigger PR before merge.


Add a tiny service worker for teh offlinez

Moved sw.js to root because scope
Cached core.css for now (can be removed later obv)
Did not cache the webfont but added sensible fallbacks instead

Don’t merge yet. Didn’t test permalinks and they don’t work.

@paullewis All done :)

LGTM!

:tada:


Fix typo in README

Fix typo in README

Thank you for this pull request! For some reason, I couldn't merge it directly. But I made the fix in README directly.


From my experience, I tend to believe this is a known network problem from Origins (Forge). When origins is reset, some changes may actually not be sent to the client correctly. It could cause this issue and https://github.com/EdwinMindcraft/origins-architectury/issues/231.
In most cases the problem should get solved when re-entering the world (no matter single player or multiplayer).

I see, Thank you


fix(runtime/ffi_api): wrong paths for C examples

The C example file is refered as // add.c, but the commands compilations examples use add_numbers.c instead.
Additionally, the .ts use libadd as lib path so it doesn't work out of the box when you try it
Also -Wl may be a typo because it throws the following:
cc: error: unrecognized command line option ‘-Wl’; did you mean ‘-W’?

Just using -W is fine though

This is related https://github.com/denoland/dotland/issues/1825


Basic integration with Northstar API

What's this PR do?

Basic integration with Northstar API using @dosomething/northstar-js

Tests
  ․․․․․․․

  7 passing (3s)

What are the relevant tickets?
Closes #37.

👍


Allow users to withdraw expired requests

Rationale
In the unhappy case that a user creates a request that is not filled (for whatever reason) within the timeout period, we need to have a way in the UI to allow the user to withdraw the tokens that are locked with his request. The functionality is already implemented in the smart contracts, but not in the frontend.
Implementation
I believe it would be ideal to offer this functionality as part of the "transaction history" overview, so that the user can see if a request wasn't successful and has the options to press a button "withdraw funds" to get back his funds.
I need input from @olympe-silve regarding this and it would be great if it could be included in the design of the transaction history. I am also open to other suggestions, but this currently the best place for this functionality in my opinion.

#279 needs to be taken into account here. In order to withdraw tokens from a request the request must be expired and does not have any active claims on it. If that is the case then we need to wait until all active claims are resolved. This takes at least 8 days.
Each claim has a termination set, which can be prolonged if the challenge continues. But at least at each point in time we could give the user a feedback that he has to wait at least X time.
This should be reflected in the UI. Unless a request is filled, the user might ahve the opportunity to withdraw the tokens in the future. There will be a timestamp when the user can withdraw the tokens. We should give the user this timestamp as feedback withdrawable in XXX (until it is filled).
Im happy to discuss details

indexed keyword on ClaimMade events is included in #569


Fix bug which append email addresses to infinity

This pr fixes the bug which appended email addresses to infinity to contact. It happened because the deletion did not work.

Vielen Dank, den Bug hab ich auch, neue Version kommt in Kürze 👍😊


Server-Side validation fails.

There seems to be an issue when editing an address within the profile.
given the route: "frontend.account.address.edit(.save)".
If you remove the required attribute of a mandatory field (to be able to submit the form), i'd expect the validator to validate the data and output the errors in the frontend.
instead I get the following error:
Uncaught PHP Exception Symfony\Component\Routing\Exception\MissingMandatoryParametersException: "Some mandatory parameters are missing ("addressId") to generate a URL for route "frontend.account.address.edit.page"." at /Users/blockj/Sites/shopware/mybacknumber_sw6/vendor/symfony/routing/Generator/UrlGenerator.php line 165.
Edit://
EA1.1 GIT Version

hey @Gainto
thanks for reporting this issue. could you please check, if this still exists in EA2 and/or current master?

hey
sure, tested in in EA2 and Master.
I can confirm that this still exists in both versions.

255.mov.zip
Please see the attached video. (Captured in EA1.2)

Hello,
thank you for creating this issue.
I have opened a ticket on our Issue Tracker for you. See the ticket link: https://issues.shopware.com/issues/NEXT-5243
Please use this ticket to track the state of your issue.


Only Chrome TokenMismatchException

Hi, im getting some problems using CSRF. Every form submited on Google Chrome fails with TokenMismatchException. In some cases if I try to refresh and force to resubmit some times so this works, but always fail on firsts.
Doing same with FF works like a charm.
I'd test with simple forms and default routes to Auth. (http://laravel.com/docs/5.1/authentication#authentication-quickstart)
The forms has "{!! csrf_field() !!}".
Disabling csrf verification in Kernel config works well.
My sytem info:
Laravel 5.1.10
Chrome 44.0.2403.157 (64-bit) (LINUX)

Please ask on the forums.

Thanks.


wal2json

Project description
wal2json is a PostgreSQL extension. The extension is a JSON output plugin for changeset extraction.
Metadata

homepage URL:

https://github.com/eulerto/wal2json

source URL:

https://github.com/eulerto/wal2json

license:

BSD

platforms:

unix, linux, darwin

I packaged this up over in https://github.com/NixOS/nixpkgs/pull/173434
It worked for my minimal testing, but I haven't done anything more involved with it yet.


element in curly brackets is too high udc.tex

Maybe it is correct. It is just the P sticking out and there is room for a g or p.


handle new logback based logging in Sesame Console

(Migrated from https://openrdf.atlassian.net/browse/SES-568)
The aduna application base switched from log4j to logback for logging. The Console needs to be modified accordingly, most notably the "set log" command.

Is this still an issue? I thought that we had switched to SLF4J-API for libraries and Logback for applications (console/workbench) already but I haven't verified that.

The set log command suggested by PrintHelp doesn't work ("unknown parameter: log") since SES-750.


Connect User Management to MongoDB

The User management requires connection to the SP MongoDB in order to perform management and authorization operations:

Keycloak can't store developer's public keys. While storing the developer public key and certificate, Keycloak throws an exception (Value too long for column "VALUE NVARCHAR (255)).
User Management needs to know which micro-service resources are exposed to the users
User Management needs to store roles and permissions mappings dynamically

User management is connected to a dedicated collection user_management in MongoDB. This enables next features:

storing per user public_key and certificate
store micro-services exposed resources, e.g. nsds
store roles and permissions mappings


Fail to build LibSVM on Windows (VS2008)

6>------ Build started: Project: LIBSVM, Configuration: Release x64 ------
6>1>------ Build started: Project: svm-predict, Configuration: Release x64 ------
6>2>------ Build started: Project: svm, Configuration: Release x64 ------
6>3>------ Build started: Project: svm-scale, Configuration: Release x64 ------
6>4>------ Build started: Project: svm-train, Configuration: Release x64 ------
6>3>Compiling...
6>2>Compiling...
6>4>Compiling...
6>1>Compiling...
...
6>1>LINK : fatal error LNK1181: cannot open input file 'm.lib'
6>1>Build log was saved at "file://e:\work\TubeTK\TubeTK-R64\LIBSVM-build\svm-predict.dir\Release\BuildLog.htm"
6>1>svm-predict - 1 error(s), 29 warning(s)

As of eb540d387150, code conditionally building on VisualStudio has been removed.
If this is still an issue, re-open.


Add make target to update bundle generation golden files

This PR adds a make target to update the bundle generation testdata files without manual copy-paste.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cc @ewollesen

/approve


Adding darkmode in the homepage

adding darkmode in homepage will enhance user experience
Priority- High

@vishanurag assign me this issue


Clickd moi

Presently allows for getting current users and dumping their job stats in a user readable way. Also includes an explicit check on import that redis is available and works.

Code looks fine. What about adding a call to the script in .travis so we know that it runs (in case of modifications)?

@antgonza, merge or one more review?


Array size question

Hello,
I'm just reading code out of curiosity. Shouldn't this be 64 bytes? https://github.com/Sc00bz/bscrypt/blob/main/blake2b.cpp#L73

Yes and fixed. Funny thing I've been meaning to replace the BLAKE2b code with a standard library (like https://github.com/BLAKE2/libb2), but then it's no longer cross platform and no longer self contained.

For what it's worth, I feel self contained and portable is good for the reference implementation. It would also be nice to have docs & test vectors, but I guess it's already tracked here https://github.com/Sc00bz/bscrypt/issues/2 ;)


Unable to type into comment boxes when using GitHub PR extension

When attempting to leave a pull request comment using the GitHub PR extension, the cursor jumps to the top of the file and prevents typing in the comment box.
Steps to reproduce:

Open a file from the GitHub PR extension.
Click on one of the changed lines
Click inside the comment box
Start typing

Expected Behavior

Text is typed into the comment box

Actual Behavior

Cursor jumps to line 1 of the file

Affected Versions
VSCode version 1.49.1
NeoVim extension version 0.0.63 (although this has been in the last several releases)

I'm using github PR extension too and don't have such problem. Try with empty init.vim first

I'm not sure if this is the same issue, but I have seen something similar using the Atlassian Bitbucket extension. I have been able to work around it by clicking in the file somewhere near the comment box, then the cursor jump is no longer an issue. I haven't done a ton of narrowing down to find the cause, but I will try and see if I can reproduce with empty init.vim etc.

@KidVizious @ian-h-chamberlain  are you using side by side or inline diff editor?

I use the side by side diff editor.

works for me with side-by-side too

I was previously not using a custom init.vim so I created an empty one and pointed the plugin to that file.  Same issue.

Could you also try to remove all plugins?

@Shatur95 Vim plugins? I'm not using any...just a vanilla neovim install.

Yes. Strange, we need to find the cause of the problem, because none of us can reproduce it...
Okay, maybe some VSCode settings causes the issue?

I seem to see the issue when running in either side-by-side or unified diff mode, although unified exacerbates the problem since the cursor generally travels farther from the comment box.
I tried with empty init.vim and all extensions disabled except these:
redhat.vscode-yaml  asvetliakov.vscode-neovim atlassian.atlascode

(YAML extension is required by Atlassian extension)
The only seemingly related VSCode user or workspace settings I can find in my settings are:
{
    "diffEditor.ignoreTrimWhitespace": false,
    "diffEditor.renderSideBySide": true,
}

Although as I mentioned both values of renderSideBySide seem to have the same issue.
Some other environment info in case it is helpful:
Extension details:
Name: Neo Vim
Id: asvetliakov.vscode-neovim
Description: Real VIM in your Visual Studio Code
Version: 0.0.63
Publisher: Alexey Svetliakov
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim

neovim details:
$ nvim --version
NVIM v0.5.0-nightly-81-gaa4557920
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/tmp/neovim-20200908-21341-1cp1gl/build/config -I/tmp/neovim-20200908-21341-1cp1gl/src -I/usr/local/include -I/tmp/neovim-20200908-21341-1cp1gl/deps-build/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include -I/usr/local/opt/gettext/include -I/tmp/neovim-20200908-21341-1cp1gl/build/src/nvim/auto -I/tmp/neovim-20200908-21341-1cp1gl/build/include
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-aa45579/share/nvim"

Run :checkhealth for more info

VSCode details:
Version: 1.49.2
Commit: e5e9e69aed6e1984f7499b7af85b3d05f9a6883a
Date: 2020-09-24T16:23:52.277Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0

Let me know if there's anything else I can provide to help!

I believe #461 fixes that


Do not include rake release at all

Hi there,
My Rakefile looks like this:
# This is literally all I have
require 'geminabox-release'
GeminaboxRelease.patch(:use_config => true)

When I list all the available rake actions, I get the geminabox ones, as well as the rubygems one:
rake build
rake inabox:forcepush
rake inabox:push
rake inabox:release
rake release # This one releases to Rubygems

Is there a way to not create that one? It's easy to forget including inabox: before that if you are in a hurry.

Update -  I found a way doing this:
require 'geminabox-release'
GeminaboxRelease.patch(:use_config => true)

Rake::Task['release'].clear

I think you should do this by default in your gem. If not possible, please add it as an option. Otherwise please consider at adding a note on the README.

i'll consider adding a option to remove the default bundler tasks

added an option :remove_release which actually removes the rake release task, not just disables the actions.


(Unbound dns over tls) not showing in https://<IP_ADDRESS>/help

I've come across a few things that occur when following this guide they are
1. When unbound is installed you are then unable to get the root.hint file or any of the DoH files. However stopping the unbound service after installing it ,and restarting the service after step 4 as per the guide is a work around. (sudo service unbound stop)

2. Downloading the cloudflared 32bit gives a 404 error. But is fixed by downloading from the officical github -> wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-arm .

3. After cloudflared-linux-arm is downloaded it needs to be renamed to cloudflared before the copy step is carried out. (mv cloudflared-linux-arm cloudflared)

4. After all of this I end with DoH working but not DoT (this is with or without alternative dns on pc) ->
   ![Capture](https://user-images.githubusercontent.com/15659183/144603760-7745702c-8d3c-416e-8491-3201c876c80f.PNG)
   I tried just having DoT configured and all I get is ->
   ![Capture2](https://user-images.githubusercontent.com/15659183/144604035-ea48c50a-415a-4a96-bcdc-13bd0c9f91c1.PNG)
   At this point I have no idea what to do.
   ps. I have followed this guide 6 or so months ago and it was working.
   pps. I have tried the fix in the previous issue.

same issue for me with https://<IP_ADDRESS>/help and i even tried older version unbound 1.13.1 and no luck.. But its confirmed unbound is working from https://dnssec.vs.uni-due.de/ and terminal commands test validation  :
dig sigfail.verteiltesysteme.net @<IP_ADDRESS> -p 53
dig sigok.verteiltesysteme.net @<IP_ADDRESS> -p 53

The first command should give a status report of SERVFAIL and no IP address. The second should give NOERROR plus an IP address. (From https://docs.pi-hole.net/guides/dns/unbound/#test-validation)
So i dont know if it could be the website https://<IP_ADDRESS>/help or browsers not showing TLS cause recently with firefox and chrome  i see from https://www.cloudflare.com/ssl/encrypted-sni/ TLS 1.3 is on by default so i really can't tell..I'll try a whole different method for DOT and see but for now i guess unbound still works but ill find another way for DNS OVER TLS
Originally posted by @trinib in https://github.com/trinib/AdGuard-WireGuard-Unbound-Cloudflare/issues/5#issuecomment-1001643176

@26adriano @Issladde  i see dns over tls on https://<IP_ADDRESS>/help  started showing again

i'll close issue when i update readme


This is available in other languages?

Thank you for your great work!
Can this extract MIDI from singing voices in other languages?
Thanks!

It might be possible, but the model is only trained on Chinese, so it might not work well in other languages.

And could you tell me where you found out about this program?

I just simply look up everything related to DiffSinger everywhere. I'm currently trying to train DiffSinger in other language

You may have to try the language you need yourself, there is user feedback that Japanese quality is acceptable.English is not.

Oh, I'm trying on Vietnamese. Thank you so much


Replace LambDynamicLights with Shimmer

Shimmer is a great project with a flexible configuration possibilities for users and devs, including colored dynamic lighting. And it already can work with Sodium 0.5 :)
Maybe give it a chance?
By the way, LambDynamicLights has been seen causing a huge performance drops on some devices, including mine. Here's an example:
https://discord.com/channels/977987490742935652/1125634282128408626/1125696662313111592
Demo from discord:
https://pomf2.lain.la/f/ca5t9oyd.mp4

Shimmer doesn't work on Quilt because the mod is returning null from a method that is supposed to be not-null, which somehow works on Fabric, but doesn't on Quilt (as it shouldn't).

And the shimmer dev has some... weird... opinions on when they should add quilt support. According to them, quilt will be supported when quilt removes the WIP banner from their front page

The weird thing is that the only place I found where it doesn't work is that they're returning null from a method that should never have null returned from it. It's sloppy code and it's breaking on Quilt because Quilt expects that code to be written properly.

Well, if they don't want to fix it then reporting it to the quilt devs will probably work

Yeah, Quilt could probably handle that a bit better (like mimicking Fabric), but honestly it's just luck at this point that that doesn't crash on Fabric.

Shimmer also has a lot more stuff than LDL, that doesn't fit under OF compat. I wonder how laggy it is on low-end PCs.

I wonder how laggy it is on low-end PCs.

Still better than LDL, which is broken on 1.20 (see attached video)

At least LDL loads

Still better than LDL, which is broken on 1.20 (see attached video)

But that's a bug, surely. I meant that generally it seems to be doing a lot more, and it might not fit for Additive especially with coloured lights and stuff.


Achievement comments refactor to support avenger flow

This PR is meant to be integrated with backend PR #917
The main goal is to polish the user experience for avengers using the achievements page.

Previously, the achievement view feedback panel only allowed users to view feedback for their own assessments. Hence admins who are able to toggle to different students will still see their own feedback, and not the feedback specific to the student they were viewing.

This is achieved mainly by creating new backend routes for admins that the AchievementView and AchievementOverview will fetch from.

This PR also addresses

Total xp bar at the top of the achievements page will now correctly reflect the xp of whichever user you are currently viewing.
Selecting a new user to view will reset the achievement card view on the right.
Changes the tsconfig to only warn users of unused variables, instead of completely failing the compilation.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

15 of 61 (24.59%)  changed or added relevant lines in 8 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.08%) to 32.875%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/application/actions/SessionActions.ts
4
5
80.0%

src/commons/achievement/AchievementCommentCard.tsx
1
3
33.33%

src/pages/achievement/subcomponents/AchievementDashboard.tsx
0
3
0.0%

src/commons/sagas/RequestsSaga.ts
2
9
22.22%

src/commons/achievement/AchievementOverview.tsx
0
9
0.0%

src/commons/sagas/BackendSaga.ts
5
15
33.33%

src/commons/achievement/AchievementView.tsx
0
14
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/commons/achievement/AchievementView.tsx
1
0%

src/pages/achievement/subcomponents/AchievementDashboard.tsx
1
2.22%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
4331

Relevant Lines:
12250

💛  - Coveralls


Portugal ACWC

I assume that this is an error, right?

This should be safe to close as it looks like a mistake and/or spam.


Can't remove TaskbarX

Even after uninstalling TaskbarX from the application, the apps on the taskbar do not move towards the left. When tried to remove the TaskbarX application, there was an error and displayed the message that it can't remove the application cause it's running.

I stopped TaskbarX and then uninstalled it and it worked.


missing default value?

(lens/over (lens/in [:path] ["default"])
           #(conj % "hi")
           {})

returns {:path ("hi")} but I expect {:path ["default" "hi"]}
I would expect the default value to get passed into the update function. Is the above how it's supposed to work?

This is the expected behavior, the in lens is defined as:
(lens (fn [s] (get-in s path default))
      (fn [s f] (update-in s path f)))))

This means, getter and setter are individual options, and update-in does not define the default.
If you want, the default value used also for updates, you probably need something like this:
(lens (fn [s] (get-in s path default))
      (fn [s f] (update-in s path (fnil f default))))))

Thanks. What's the rationale? Does it break any lens laws? I'm a total novice and there's plenty of information available regarding this but I didn't want to leave you hanging. I appreciate your response and I've had great success using the library so far.

No, it does not breaks any law I think, but in any case; maybe this is an expected behavior from one perspectvie, can be unexpected from other. If you define a getter with default value, the setter is not expected to execute the getter, they are separated operations. In any case. The builtin in lense is just an implementation; it is not mandatory to you use it. You should create your own lenses for your purposes.

Ok, thank you. I was trying too hard to get by with just the provided lenses.


Run Travis on PRs

Now that travis is set up to run flake8, it would be good to configure this repo to run travis and show the build pass/fail status on the pull request. I am the only admin for this repo, so please find the relevant docs so I can set this up :)
(Originally posted as a comment in https://github.com/googlefonts/fontbakery/pull/799#issuecomment-223403089)

This has been working for a while now.


2 muc-room-destroyed events generated by event_sync when used in combination with token_owner_party

I have observed the following:
When using the event_sync plugin together with the token_owner_party plugin POST ${api_prefix}/events/room/destroyed is called twice:

Immediately after  the last owner has left the room.
Again party_check_timeout seconds after the last owner left the room.

Is there a way to change this behaviour so that only the 2nd event occurs, as this is what I would logically expect? Right now my workaround is to ignore the 1st event but that's a kludge IMO. Thanks! :)

I cannot reproduce this issue. room_destroyed is only triggered once in Prosody in my tests.
I tested by adding this line:
module:log("info", "DESTROYED ZZZZZZZZZZZZZ")
into room_destroyed function in the module.

I have tested on 3 different machines and am seeing 2 room_destroyed events on all of them. Maybe it's something to do with my setup? Below are excerpts from my Prosody config if that helps:
VirtualHost "6cba52c9-5268-4bad-a094-7e41317e774a.konnect-me.info"
    authentication = "token"
    app_id="xxx"
    app_secret="xxx"
    allow_empty_tokens = false

    modules_enabled = {
        "bosh";
        "ping"; -- Enable mod_ping
        "speakerstats";
        "external_services";
        "conference_duration";
        "end_conference";
        "muc_lobby_rooms";
        "muc_breakout_rooms";
        "av_moderation";
        "room_metadata";
    }

Component "conference.6cba52c9-5268-4bad-a094-7e41317e774a.konnect-me.info" "muc"
    restrict_room_creation = true
    storage = "memory"
    modules_enabled = {
        "muc_hide_all";
        "muc_meeting_id";
        "muc_domain_mapper";
        "polls";
        "token_verification";
        "token_affiliation";
        "token_lobby_bypass";
        "token_owner_party";
        "muc_rate_limit";
        "muc_password_whitelist";
    }
    admins = {<EMAIL_ADDRESS>}
    muc_password_whitelist = {
<EMAIL_ADDRESS>    }
    muc_room_locking = false
    muc_room_default_public_jids = true
    party_check_timeout = 20

Component "esync.6cba52c9-5268-4bad-a094-7e41317e774a.konnect-me.info" "event_sync_component"
    muc_component = "conference.6cba52c9-5268-4bad-a094-7e41317e774a.konnect-me.info"
    api_prefix = "http://<IP_ADDRESS>:9000"

Now I am unable to reproduce this and only receive one room_destroyed event directly after the meeting ends. I am not sure if I was testing with an older version previously? Feel like I'm going mad. Anyway, I'll close this issue & modify mod_token_owner_paty.lua locally to ensure this works the way I need it to (I am only interested in receiving a room_destroyed event party_check_timeout seconds after the end of the meeting).