fix: External footer links

External footer links were not working correctly because they were <nuxt-links>.

#15 related, closing and linking here.

@SYNTAG there was something still here in adding rel="noopener noreferrer" and impacts your lighthouse audit score https://developers.google.com/web/tools/lighthouse/audits/noopener

@audiolion I appreciate the warning. But this isn't a big concern for us since these are our own internal social media profile links on our footer.


feat(launcher): add use-effect-router

[x] core code implement
[x] test coverage
[x] perf useRouter

Codecov Report

Merging #74 (4011128) into master (5a5c857) will increase coverage by 0.42%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
+ Coverage   96.26%   96.69%   +0.42%
==========================================
  Files          17       19       +2
  Lines         241      272      +31
  Branches       42       47       +5
==========================================
+ Hits          232      263      +31
  Misses          9        9

Impacted Files
Coverage Δ

packages/launcher/src/hooks/index.ts
100.00% <100.00%> (ø)

packages/launcher/src/hooks/use-effect-router.ts
100.00% <100.00%> (ø)

packages/launcher/src/hooks/use-query.ts
100.00% <100.00%> (ø)

packages/launcher/src/hooks/use-router.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Possibly missing data in pre-generated files bi-sf1000-composite-projected-fk.tar.zst.*

Not sure whether some csv files are actually missing in pre-generated data files bi-sf1000-composite-projected-fk.tar.zst.* or this was intentional, but I can see non-continuous numbering of parts in several directories, for example:
in the bi-sf1000-composite-projected-fk/graphs/csv/bi/composite-projected-fk/initial_snapshot/dynamic/Person_likes_Comment/ directory there are parts numbered from 00000 to 00355, but parts 00343-00345, 00347, 00350 and 00351 are missing.
in the bi-sf1000-composite-projected-fk/graphs/csv/bi/composite-projected-fk/initial_snapshot/dynamic/Forum_containerOf_Post/ directory the part 00007 and from 00352 to 00357, and so on...
As there is no other source to compare and the archives do not contain any checksum files, there is no way to confirm data completeness and integrity.

@krisiasty thanks for pointing out this issue. This is quite unfortunate – the missing files should be there. What likely happened is the following: I generated that data sets in EMR, then I used the aws s3 cp command instead of doing repeated runs of aws s3 sync (which performs an rsync-style synchronization).
I regenerate the files and upload the correct version.

@szarnyasg thanks for confirmation. When you regenerate new files, could you please also include some checksums for the content?
Also, since the data on cloudflare r2 storage for sf1000 in the composite-projected-fk format are incomplete, doesn't that mean all the official benchmark results which used that data, including LDBC Social Network Benchmark on Tigergraph, are invalid?
How did it pass the audit? Shouldn't they all need to be re-run and re-audited again?

Well, not so fast. Let me share my initial thoughts:

The R2 repository is LDBC's official repository for BI data sets. So we may decide to elevate this (broken) data set to become a definitive version for the BI benchmark. I'll discuss this possibility with the task force.

Unlike SNB Interactive queries, most BI queries do not target an individual Person node, instead, they use data ranges, countries, tags, etc. Therefore, if a few likes and containership edges are missing, the queries will finish successfully – but they will touch on slightly less data.

The amount of data missing seems to be small, so its effect on the runtimes is also small, maybe even negligible. I will double-check this

How did it pass the audit?

At the moment, TigerGraph is the only system (that we have access to) that can run the benchmark at scale factor 1000 – so we cannot cross-validate the results on this scale factor against a system that uses a different serialization layout (composite-merged-fk). Instead, the cross-validation happens at smaller scale factors such as SF10 (as prescribed by the auditing guidelines), which TigerGraph passed successfully.

I looked into this further and it seems that having missing files is a normal phenomenon - just a symptom of Spark crashing and retrying the job during generation.
I checked it using the Person_likes_Comment file in both formats and the number of entities align perfectly:
$ for FILE in *.csv.gz; do echo "${DIR} $(zcat ${FILE} | tail -n +2 | wc -l)" >> num-entries.csv; done
$ bi-sf1000-composite-merged-fk/graphs/csv/bi/composite-merged-fk/initial_snapshot/dynamic/Person_likes_Comment $ awk '{ sum += $1 } END { print sum }'  num-entries.csv
2249224980

$ for FILE in *.csv.gz; do echo "${DIR} $(zcat ${FILE} | tail -n +2 | wc -l)" >> num-entries.csv; done
$ bi-sf1000-composite-projected-fk/graphs/csv/bi/composite-projected-fk/initial_snapshot/dynamic/Person_likes_Comment $ awk '{ sum += $1 } END { print sum }'  num-entries.csv
2249224980

So, does it mean we can assume the data is complete, just file part numbers are not sequential because of spark crashes?

Yes. For the larger scale factors, I remember doing repeated ‘aws s3 sync’
runs to make sure everything is synced.
That said, if you stumble upon any other suspicious cases, let me know and
I’ll look into it.
On Wed 15 Feb 2023 at 18:20, Krzysztof Cieplucha @.***>
wrote:

So, does it mean we can assume the data is complete, just file part
numbers are not sequential because of spark crashes?
—
Reply to this email directly, view it on GitHub
https://github.com/ldbc/ldbc_snb_bi/issues/158#issuecomment-1431728095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKWPMK2BOOHV66MXNWXQ4TWXUF4HANCNFSM6AAAAAAU4GCLOY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Update native-svg.md

Adding a line on how to make sure any newly uploaded svgs become visible in the Make it Native app - this was quite a hassle to figure out. Hope this helps.
Best regards,
Wouter Penris

SVGs and images in general are going to receive a wide documentation update in the near future. I will try to include these amendments to that update.

Our SVG and images documentation update is still on the horizon. I will add this info as a warning message directly to the docs. If we optimize the product and have no need for the warning in the future, I'll remove it in future SVG updates.

Info added in this commit: https://github.com/mendix/docs/commit/6621833f25470750ffcba7e323366e9cd00e0b84
I will close this PR.


Liveshare Api Join not working as expected

When trying to use the Liveshare api within another vscode extension, the join function doesn't join a session, instead it shows an empty input box to enter the url of the session.
I am using https://www.npmjs.com/package/vsls for the api and using the function join which takes a url.
I have tested this using the latest version of liveshare (1.0.4419) where it doesnt work, i have also tested it with 1.0.3014 and it is working, so i would assume something has changed between releases.
Given that both repos are maintained by liveshare team, is it possible to update the npm? as i think it could be just a matter of this.
Version: 1.57.1
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:28:32.912Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.5.0
Steps to Reproduce / Scenario:
Create an extension, use the npm dependancy https://www.npmjs.com/package/vsls
Then:
const url = "x";
const client = await getApi(this.context.extension.id);
await client.join(Uri.parse(url), { newWindow: true });

Where x is a valid liveshare url
This connects successfully to a session when using liveshare 1.0.3014 but not when using the latest 1.0.4419
Screenshots

Just incase anybody else has the same issue, the temporary fix i used was this:
await client.join(Uri.parse(url), { newWindow: true, inviteLinkJoining: false } as any);

The "options" needs to have the property inviteLinkJoining set to false, so to get around this, i cast it as an any.

Thanks @Reedyuk.

Closing this as resolved per the previous comments.


Make mclwrap use its own package names and not Math's

Mclwrap's bilinear group classes are currently found under org.cryptimeleon.math.structures.groups.elliptic.type3.mcl.
I would like to make Mclwrap not fake being part of Math like that anymore, for example using a directory structure such as org.cryptimeleon.mclwrap.bn254.
I just added standalone representation tests to mclwrap (didn't have those before) and they seem to collect all of Math's classes as well, due to passing org.cryptimeleon.math to StandaloneReprTest. Obviously Mclwrap is not going to include standalone repr tests for all those classes. That problem can be solved by giving Mclwrap its own packaging structure.
What do you think @JanBobolz ?

Hard agree. The Java package names should be consistent with the gradle project names, i.e. org.cryptimeleon.mclwrap.stuff
Good catch!

Fixed as part of #20


[Storage] Download stream refactor

Refactored the StorageStreamDownloader objects to:

[Breaking] Moved iterable behaviour to separate chunks() function (#7731).
Added readall() and readinto(stream) functions to start implementing stream interface (#7504).
Deprecated content_as_bytes(), content_as_text(), download_to_stream().
[Breaking] Made most of the public attributes private, and documented those remaining public ones.
Reduced some duplicate code (still lots of work to be done here).
Added async module level upload/download functions.

Can one of the admins verify this patch?

Would be great if you can update History.md :)
Thanks.

@rakshith91 - Done.

/azp run python - storage - ci

It looks great 😀

/azp run python - storage - ci


Import COM/IDL helpstrings

Most COM properties/methods have a short helpstring attached to them. Importing those will be useful when using the module on IDEs.

Since f983a33, only enumerations are missing docstrings. I don't know the best way to document single attributes so that IDEs pick their description. May revisit in the future.


Terraform AWS 4.0 Provider Upgrade

Good afternoon.
I am in the process of upgrading to the 4.4.0 terraform provider for AWS, however when I do so, I get these errors in the tf-module.  It looks like the S3 configuration has changed significantly.
Error: Value for unconfigurable attribute
│
│   with module.backoffice_tf_next.module.proxy_config.aws_s3_bucket.proxy_config_store,
│   on .terraform/modules/backoffice_tf_next/modules/cloudfront-proxy-config/main.tf line 13, in resource "aws_s3_bucket" "proxy_config_store":
│   13:   acl           = "private"
│
│ Can't configure a value for "acl": its value will be decided automatically
│ based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.backoffice_tf_next.module.statics_deploy.aws_s3_bucket.static_upload,
│   on .terraform/modules/backoffice_tf_next/modules/statics-deploy/main.tf line 10, in resource "aws_s3_bucket" "static_upload":
│   10: resource "aws_s3_bucket" "static_upload" {
│
│ Can't configure a value for "versioning": its value will be decided
│ automatically based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.backoffice_tf_next.module.statics_deploy.aws_s3_bucket.static_upload,
│   on .terraform/modules/backoffice_tf_next/modules/statics-deploy/main.tf line 12, in resource "aws_s3_bucket" "static_upload":
│   12:   acl           = "private"
│
│ Can't configure a value for "acl": its value will be decided automatically
│ based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.backoffice_tf_next.module.statics_deploy.aws_s3_bucket.static_deploy,
│   on .terraform/modules/backoffice_tf_next/modules/statics-deploy/main.tf line 36, in resource "aws_s3_bucket" "static_deploy":
│   36: resource "aws_s3_bucket" "static_deploy" {
│
│ Can't configure a value for "lifecycle_rule": its value will be decided
│ automatically based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.backoffice_tf_next.module.statics_deploy.aws_s3_bucket.static_deploy,
│   on .terraform/modules/backoffice_tf_next/modules/statics-deploy/main.tf line 38, in resource "aws_s3_bucket" "static_deploy":
│   38:   acl           = "private"
│
│ Can't configure a value for "acl": its value will be decided automatically
│ based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.marketplace_tf_next.module.proxy_config.aws_s3_bucket.proxy_config_store,
│   on .terraform/modules/marketplace_tf_next/modules/cloudfront-proxy-config/main.tf line 13, in resource "aws_s3_bucket" "proxy_config_store":
│   13:   acl           = "private"
│
│ Can't configure a value for "acl": its value will be decided automatically
│ based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.marketplace_tf_next.module.statics_deploy.aws_s3_bucket.static_upload,
│   on .terraform/modules/marketplace_tf_next/modules/statics-deploy/main.tf line 10, in resource "aws_s3_bucket" "static_upload":
│   10: resource "aws_s3_bucket" "static_upload" {
│
│ Can't configure a value for "versioning": its value will be decided
│ automatically based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.marketplace_tf_next.module.statics_deploy.aws_s3_bucket.static_upload,
│   on .terraform/modules/marketplace_tf_next/modules/statics-deploy/main.tf line 12, in resource "aws_s3_bucket" "static_upload":
│   12:   acl           = "private"
│
│ Can't configure a value for "acl": its value will be decided automatically
│ based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.marketplace_tf_next.module.statics_deploy.aws_s3_bucket.static_deploy,
│   on .terraform/modules/marketplace_tf_next/modules/statics-deploy/main.tf line 36, in resource "aws_s3_bucket" "static_deploy":
│   36: resource "aws_s3_bucket" "static_deploy" {
│
│ Can't configure a value for "lifecycle_rule": its value will be decided
│ automatically based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.marketplace_tf_next.module.statics_deploy.aws_s3_bucket.static_deploy,
│   on .terraform/modules/marketplace_tf_next/modules/statics-deploy/main.tf line 38, in resource "aws_s3_bucket" "static_deploy":
│   38:   acl           = "private"
│
│ Can't configure a value for "acl": its value will be decided automatically
│ based on the result of applying this configuration.

What are your thoughts on upgrading to the new version? Should I fork this in the meantime?
Thanks so much!

Yes, 4.0 changed some S3 configuration options.
Need to take a look at our own dependencies (terraform-aws-modules/lambda/aws & terraform-aws-apigateway-v2) if they are already compatible with the 4.x version.
In general I see nothing that speaks against to increase the minimum required aws provider to 4.x 👍


EXCEPTION CAUGHT BY SERVICES LIBRARY

I'm using Ubuntu 20. Just upgrade with the later version of Flutter. Created a new project and run flutter run -d linux.
Then I got the exception message below. This might help on the improvement on the next release.
EXCEPTION CAUGHT BY SERVICES LIBRARY
╞══════════════════════════════════════════════════════════
The following assertion was thrown during a platform message callback:
A KeyUpEvent is dispatched, but the state shows that the physical key is not
pressed. If this occurs
in real application, please report this bug to Flutter. If this occurs in unit
tests, please ensure
that simulated events follow Flutter's event model as documented in
`HardwareKeyboard`. This was the
event: KeyUpEvent#aae2b(physicalKey: PhysicalKeyboardKey#7001b(usbHidUsage:
"0x0007001b", debugName:
"Key X"), logicalKey: LogicalKeyboardKey#00078(keyId: "0x00000078", keyLabel:
"X", debugName: "Key
X"), character: null, timeStamp: 6:00:01.183000)
'package:flutter/src/services/hardware_keyboard.dart':
Failed assertion: line 432 pos 16: '_pressedKeys.containsKey(event.physicalKey)'

When the exception was thrown, this was the stack:
#2      HardwareKeyboard._assertEventIsRegular.<anonymous closure>
(package:flutter/src/services/hardware_keyboard.dart:432:16)
#3      HardwareKeyboard._assertEventIsRegular
(package:flutter/src/services/hardware_keyboard.dart:443:6)
#4      HardwareKeyboard.handleKeyEvent
(package:flutter/src/services/hardware_keyboard.dart:535:5)
#5      KeyEventManager.handleRawKeyMessage
(package:flutter/src/services/hardware_keyboard.dart:881:37)
#6      BasicMessageChannel.setMessageHandler.<anonymous closure>
(package:flutter/src/services/platform_channel.dart:197:49)
#7      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure>
(package:flutter/src/services/binding.dart:387:35)
#8      _invoke2 (dart:ui/hooks.dart:186:13)
#9      _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5)
#10     _Channel._drainStep (dart:ui/channel_buffers.dart:224:31)
(elided 4 frames from class _AssertionError and dart:async)

Hi @ljfreelancer88, Thanks for filing the issue. There have been several reports of this issue in the past and most of which have been fixed in the latest release of flutter. Could you please share the output of flutter doctor -v  and the steps to reproduce the issue? Also, ensure that you are on the latest stable release of flutter 3.0.5.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.6 to before v5.10.88",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cf7da0d66cc1a2a19fc5930bb746ffbb2d4cd1be",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=451f1eded7f56e93aaf52eb547ba97742d9c0e97"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "cf7da0d66cc1a2a19fc5930bb746ffbb2d4cd1be",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "451f1eded7f56e93aaf52eb547ba97742d9c0e97",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "mptcp: clear 'kern' flag from fallback sockets\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.88 by commit 451f1eded7f56e93aaf52eb547ba97742d9c0e97, it was introduced in version v5.6 by commit cf7da0d66cc1a2a19fc5930bb746ffbb2d4cd1be. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002701


Listing and dumping trace labels should not be a privileged operation

A user should be able to see her/his own labels.

@kaccardi: Do you think we could store trace data per tenant ?

yes.


Home page looks blank

Describe your use-case which is not covered by existing documentation.
The home page for the documentation looks empty. I would suggest adding at least some description.

@krisstern @Cr1t-GYM
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
No response

Yeah, we could definitely add a brief description there stating our purposes, for example.


Node library throws unhelpful error if your codes are too big

If you submit an Account or Transfer with a code that's bigger than a 16-bit integer, the library will throw an unhelpful error:
tigerbeetle-schema-gen/node_modules/tigerbeetle-node/dist/index.js:59
                binding.submit(context, operation, batch, (error, result) => {
                        ^

Error: code
    at tigerbeetle-schema-gen/node_modules/tigerbeetle-node/dist/index.js:59:25
    at new Promise (<anonymous>)
    at request (tigerbeetle-schema-gen/node_modules/tigerbeetle-node/dist/index.js:57:16)
    at Object.createAccounts (tigerbeetle-schema-gen/node_modules/tigerbeetle-node/dist/index.js:77:40)
    at file:///tigerbeetle-schema-gen/dist/index.js:23:34
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

Node.js v18.17.1

It would be useful for the library to check the sizes of integer fields and return specific errors if you exceed the allowable size.

We already have a test for it in place (and it's correctly failing).
For some reason, it's not running during CI.
cc @matklad
https://github.com/tigerbeetle/tigerbeetle/blob/9871760c8567760271d34afde9e67039bb30569b/src/clients/node/src/test.ts#L58-L67

Yeah, I don't think we've ever run those tests on CI?
There's placeholder place for them over here, it's high time we sort this out:
https://github.com/tigerbeetle/tigerbeetle/blob/9871760c8567760271d34afde9e67039bb30569b/src/clients/node/ci.zig#L14


Use snake case for payload to follow all other endpoints

All other endpoints use snake case, just that one was not following the pattern.

Coverage remained the same at 90.227% when pulling 83c8010f3130a594c4a3b2c7fa8c849ffdbb4408 on rafaelcaricio:use-snake-case-api-status into b2e93f805d2e95193e0b809fa0b67013ef5f4b48 on zalando:release2.0.

:+1:


move stuff over from google code before shutdown

Hello,
Earlier today, Google announced we will be turning down Google Code Project Hosting. The service started in 2006 with the goal of providing a scalable and reliable way of hosting open source projects. Since that time, millions of people have contributed to open source projects hosted on the site.
But a lot has changed since 2006. In the past nine years, many other options for hosting open source projects have popped up, along with vibrant communities of developers. It’s time to recognize that Google Code’s mission to provide open source projects a home has been accomplished by others, such as GitHub and Bitbucket.
We will be shutting down Google Code over the coming months. Starting today, the site will no longer accept new projects, but will remain functionally unchanged until August 2015. After that, project data will be read-only. Early next year, the site will shut down, but project data will be available for download in an archive format.
As the owner of the following projects, you have several options for migrating your data.
ilanguagelab
The simplest option would be to use the Google Code Exporter, a new tool that will allow you to export your projects directly to GitHub. Alternatively, we have documentation on how to migrate to other services — GitHub, Bitbucket, and SourceForge — manually.
For more information, please see the Google Open Source blog or contact<EMAIL_ADDRESS>-The Google Code team
Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
You have received this mandatory email service announcement to update you about important changes to Google Code Project Hosting.

done https://github.com/iLanguage/ilanguagelab


Remove 0.5 prerelease from allowed julia versions

A trivial change.  may as well stick it through CI

As suggested at https://github.com/JuliaLang/METADATA.jl/pull/7651

Coverage remained the same at 89.319% when pulling 56ac0f9d2cabbc40a9a9e8e31a219b4448075d1f on remove-0.5-prerelease-dep into 5ee49051762d4b3aaa717660a6d6a06bd7dbfab3 on master.


Allow build args to be overridden from the command line

In addition to the static set of args within the dobi file, it would be helpful to allow build args to be overridden from the command line.
One of the scenarios this would support is where a build arg is used within a Dockerfile  but is known only at runtime. For example, an arg might form part of the base image name/tag from which the image extends.

Setting anything on the command line is difficult. dobi was designed so that any parameters are encoded in the config. make works in a similar way. The only way to specify parameters is through environment variables. #91 seems related, I don't have a good solution for that.
There are a couple ways to set dynamic values from the config. By setting an env variable on the command like you can read it using {env.VARIABLENAME} (http://dnephin.github.io/dobi/variables.html).
If the value is only available as output from some command than you can use job:capture (http://dnephin.github.io/dobi/tasks.html#job-tasks) to run the command and capture stdout to a variable, which you can then use with the same {env.VARNAME} syntax.

Thanks @dnephin; I'd missed the capture task. That might do the job, cheers!


CPU spikes

I can observe CPU spikes (it's the container that uses the most CPU over 70 services/containers). I'll experiment with CPU limits and report :_p

Would be interesting to know what happens there.

It was not addressed but it is still an issue IMHO.

@pascalandy Can you exec into the container when this happens? Or get some docker top output?

I can but what are you looking for?
user@vps2:~/workdir# docker top tool-shepherd.1.1f5tigggh7zw9rjqhnp8ut52p
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
root                18647               25831               0                   22:02               ?                   00:00:00            sleep 1m
root                25831               25797               0                   21:53               ?                   00:00:00            /bin/bash /usr/local/bin/shepherd

Well, if it is the shepherd container which is using the CPU, it would be interesting to see if it is the shepherd script itself or the docker client. I can't really make a picture of this currently.

I saw this using prometheus and Graphana. Other containers were running normally.
I now use --cpu-limit to mitigate this.
So let's close this if you prefer.

Yes, let's close this for now. Feel free to reopen if you get to the cause.


Add probes to the rotor model

We should add an object called Probe to ROSS.
The user would instantiate this object with arguments (node, probe_orientation) and pass it to the rotor constructor.
The object would be used in the plot_rotor() method and we should also be able to use it as an argument in methods such as plot frequency response.

We could, also, modify some methods that requires a dof input to a (node, probe_orientation) input like you said.

@raphaeltimbo, I'm adding this feature to the rotordynamic report.
Is it important to add probes as object to the Rotor, like the elements? I was leaning to add this option to .plot() methods. I see this way more flexible to the user.
For example:

probes argument: inputting multiple tuples (probe_node, probe_orientation)

>>> import ross as rs
>>> rotor = rs.rotor_example()
>>> speed = np.linspace(0, 1000, 101)
>>> response = rotor.run_freq_response(speed_range=speed)
>>> response.plot(probes=[(node1, orientation1), (node2, orientation2), ... ])

OR

probe_node and probe_orientation arguments

>>> import ross as rs
>>> rotor = rs.rotor_example()
>>> speed = np.linspace(0, 1000, 101)
>>> response = rotor.run_freq_response(speed_range=speed)
>>> response.plot(probe_node =[node1, node2, ...], probe_orientation =[orientation1, orientation2, ...])

In both cases we could use pint.Quantity.
What's your opinion?

I agree with you that it is more flexible this way.
I prefer the first option: probes=[(node1, orientation1), ...]

I had to do some changes on the code to make it work.

_calculate_major_axis() method
First, to calculate the displacements for different orientions than 0º (x dir.) and 90º (y dir.), I built a slightly different method to calculate the semi axes. This method calculates the semi axes for all speed values in the speed_range argument, given a single node.
The other one, which is already used to calculate the deflected shape, calculates the semi axes for all the nodes, given single speed value.

Alternative:
Change the current _calculate_major_axis() method to receive a single speed value and a single node value. The plot methods would iterate over it (through speed values or node values) and fill the arrays that would be created in the plot methos instead of being created in _calculate_major_axis().
In this case, .plot() method iterates over speed values (with node fixed) and plot_deflected_shape() iterates over nodes values (with speed fixed).

plot() method
.plot() method now gets a probe argument. It must be a list of tuples, where each tuple contains the node and orientation for the probe.
.plot(probe = [(node1, orient1), (node2, orient2), ...])
This change, allows the user to plot several results on the same chart, as you can see below:

It was not necessary to add a new method. The displacement measured by the probe argument is calculated by and operator applied to the probe_resp (X, Y) coordinates, which rotates the vector according to the probe orientation angle. Then, the absolute value is obtained by the equation in polar coordinates for the elipse.
        for i, p in enumerate(probe):
            dofx = p[0] * number_dof
            dofy = p[0] * number_dof + 1
            angle = Q_(p[1], probe_units).to("rad").m

            operator = np.array(
                [[np.cos(angle), - np.sin(angle)],
                 [np.cos(angle), + np.sin(angle)]]
            )

            probe_resp = operator @ np.vstack((magnitude[dofx], magnitude[dofy]))
            probe_disp = np.sqrt((probe_resp[0] * np.cos(angle)) ** 2 +
                                 (probe_resp[1] * np.sin(angle)) ** 2)


unable to launch Godot 4 alpha9

Godot version
version 4 - alpha 9
System information
Ryzen 5600H, Windows 11, RTX-3060 (Latest Driver) Laptop
Issue description
Cannot launch Godot 4 alpha 9. Following Error during launching:
Assertion Failed
Program:...
File: thirdparty/vulkan/vk_mem_alloch
Line: 14054

Steps to reproduce
Just launch the Godot_v4.0-alpha9_win64.exe
Minimal reproduction project
No response

Related to https://github.com/godotengine/godot/issues/57708. Check the solutions outlined in that issue.


Server\ Add onSubscibe() callback for characteristics.

Adds a new method to NimBLECharacteristicCallbacks that gets called when a client changes it's subscription status.

As an addition to this I’m considering removing the descriptor callback for 2902 descriptors.
Any feedback on do so would be appreciated.
@mitchjs I know you make use of the 2902 callback, is this PR a suitable replacement for your purposes?

@mitchjs sorry I thought I remembered you using the 2902 callbacks to detect when a client subscribed to your characteristic. Please disregard if I’m mistaken. Thanks for replying.

It seems this ha opened up a bigger hole. After removing the callbacks for the 0x2902 I came to realize the whole class is useless at that point... bigger changes to this PR incoming.

@h2zero I'll test later on, thanks. As an aside, there is still a typo in the PR title (subscibe not subscribe).

Lol I do that one often, thanks!

@h2zero I've had chance to test the code to date on this PR.
I was manually creating 2902 descriptors in my code eg. characteristic->createDescriptor("2902", properties);. This compiled fine, but then "crashed" my code with an assertion that "0x2902 descriptors cannot be manually created" as expected. I removed my manual creation (I was only doing that so I could use the onSubscribe callback that has now been moved to the characteristic).
The removal of the ability to manually create the 2902 descriptor will need to be documented accordingly, as it's a breaking change (and one that might not be obvious from a successful compilation).
I'm very happy with the onSubscribe on the characteristic, thanks very much for thinking about my underlying requirement!

Thanks for testing! I don’t see any issue removing the 2902 class. Any functionality it had could be easily incorporated into the characteristic if anyone needs it.
The documentation has already been changed in this PR :)


Cannot create configs

I have installed the bsp jar (I used a local mason repo using the same yaml file instead of your fork because of some parsing errors) and Mason loads/installs it fine. This plugin also loads correctly, but I am unable to create the config for gradle-bsp. The command does nothing, with no output.
I am aware that this plugin is early in development and I would love to help you out. I am trying to get some meaningful data from  buildTarget/dependencyModules and buildTarget/dependencySources so that I can pipe them to plugins like neotree.

Hi,

I have installed the bsp jar (I used a local mason repo using the same yaml file instead of your fork because of some parsing errors) and Mason loads/installs it fine.

I will change the Readme to avoid that confusion, you are actually right it does not work with "github:616b2f/mason-repository", I got the same error after I tried it for myself, as used the same method you described when I developed and just thought changing from "file" to "github" reference would work the same, but it does not. Thank you for pointing that out!

This plugin also loads correctly, but I am unable to create the config for gradle-bsp. The command does nothing, with no output.

You have to run :BspCreateConfig gradle-bsp, did you run it without specifying the server name?

I added a hint if BspCreateConfig command is called without a parameter, just in case :)

Yeah, I am using the correct syntax BspCreateConfig gradle-bsp. There is no change after running the command. No new files created or error messages.

I am currently have no clue why it's not working on your site, I added some more error handling and notifications. Maybe you can try again and report back.
Also I only tested it on Linux, it may have issues on Windows or MacOS.

The logging helped! The problem was autocomplete. The command I was trying to run was :BspCreateConfig gradle-bsp  (with the trailing space) and thus it failed.

On an unrelated note, does this plugin rely on jdtls/lspconfig by any chance ? I get this error when trying to load bsp,

Spawning language server with cmd: java failed with error message: attempt to call a nil value
E116: Invalid arguments for function execute

It could be trying to run gradle command which is not installed on my system. Java/Gradle uses project specific gradle binaries through a gradlew script present in the root of workspace. It would be nice if the plugin could accommodate that.

The logging helped! The problem was autocomplete. The command I was trying to run was :BspCreateConfig gradle-bsp  (with the trailing space) and thus it failed. The command should probably be trimmed to eliminate spaces and this issue can be marked as fixed :)

sounds as a good idea, would you like to create an PR for that?

On an unrelated note, does this plugin rely on jdtls/lspconfig by any chance ? I get this error when trying to load bsp,

Spawning language server with cmd: java failed with error message: attempt to call a nil value

~It could be trying to run gradle command which is not installed on my system. Java/Gradle uses project specific gradle binaries through a gradlew script present in the root of workspace. It would be nice if the plugin could accommodate that.~ Apparently, it tries to run java directly. I am not sure why that fails as java works fine on my system

no it does not rely on any of those, you see "language server" in your error message only because I copied the RPC part from Neovim, from the LSP implementation.
What you can try to narrow down the issue, try copy the argv part from your .bsp/gradle.json, this is the command that actually should be run and try to run it in your terminal, from the root of your repository.

Yes. I realized that after I read through the json file. I will experiment and figure out what exactly is the problem on my end. Just a general suggestion, it would be nicer if the entry was called "command" instead of "argv"

Yes. I realized that after I read through the json file. I will experiment and figure out what exactly is the problem on my end. Just a general suggestion, it would be nicer if the entry was called "command" instead of "argv"

OK feel free to open a new issue if you find something that can be improved.
Regarding "argv" the file schema is part of the BSP specification.


Fix convention issue

CE 2020 and 'with Convention => C' in stead of 'pragma Convention' expose circularity. Fix by introduce of nested package 'Internals'

Tested with FSF GCC 9.2.0, works here.
This is a better solution to using pragma, as I'm trying to reduce the use of pragma's preferring the use of aspects instead.

I prefer pragmas. This will make SDLAda compatible with older Ada versions. Im not ashamed to say that i like Ada 83 too.

This is an Ada 2012 binding, I even mention that  in the readme.
Pretty sure that the 2012 spec is deprecating pragma's in favour of aspects.


0-db backends deployment is broken as grid v2 is deprecated

0-stor supports 0-db backends deployment in case of unreachable/ full 0-db's but only for grid v2, which is deprecated.

Currently there is no real rust client to facilitate deployments. I think we should create a full library first so it can be used here. The library that we should mimic: https://github.com/threefoldtech/grid3_client_ts

ok, but this also means that  qsfs handled by zos  for a vm deployed on the grid is broken if a metadata 0-db is gone  and data can be lost if data backends are lost. There is currently no way to handle these use cases I think (the user will not even know what is going on).

Hot reloading was implemented a while ago, linked issue was never updated it seems.
Config reload can be triggered by sending a SIGUSR1 to the daemon.
The repair process monitors saved files and will repair them if any shard is unreachable on the chunk on the shard is missing/corrupt. Repairs are done with the new config


csharp-teams-sample-graph is not nice

Can somebody have a look at this code?
GraphService uses ServiceHelper.SendRequest and HttpHelpers.HttpXXX why two of them?
GraphService.GetMyId HttpResponseMessage is a IDisposable
Why do you use a setting an const?
private static string GraphRootUri = ConfigurationManager.AppSettings["ida:GraphRootUri"];
public string graphBetaEndpoint = "https://graph.microsoft.com/beta";
HttpHelpers.httpClient - HttpClient is a IDisposable
Statics.Deserialize exists 2 times with different implementations
GraphService.AddTeamToGroup(string accessToken) accessToken is never used
instead the HttpPut uses the accessToken

Closing this as we are closing this repository and will no longer maintain it. The Teams code snippets in this sample are replicated in the ASP.NET Core Graph Snippets sample. We apologize for any inconvenience.


docs / K8s troubleshooting

Some troubleshooting notes on kubernetes

LGTM. Can be merged :-)

LGTM. Can be merged :-)


Not getting stacktrace from exceptions

I always get a full stacktrace when I get an exception which helps figure out where the error is coming from. But lately for some reason I stopped getting them.
I'm currently getting this screen:

With only this in the console output:

Which is not helpful at all. What's worse, if I search for 'isNotEmpty' on my code base, i can't find any, which is leading me to believe it's happening inside the flutter framework. Because of some mistake on my part I'm sure, but without the stacktrace I don't know where to look.
Any idea why this might be happening?

Logs

[✓] Flutter (Channel dev, 1.24.0-7.0.pre, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-US)
    • Flutter version 1.24.0-7.0.pre at /Users/jan/flutter
    • Framework revision a0860f6e87 (4 weeks ago), 2020-10-29 20:07:34 -0700
    • Engine revision 073263e39d
    • Dart version 2.11.0 (build 2.11.0-260.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/jan/Library/Android/sdk
    • Platform android-R, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    • CocoaPods version 1.10.0.rc.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • AOSP on IA Emulator (mobile) • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
    • macOS (desktop)              • macos         • darwin-x64     • Mac OS X 10.15.7 19H2 darwin-x64
    • Web Server (web)             • web-server    • web-javascript • Flutter Tools
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 86.0.4240.198
    ! Error: iPhone de Jan Lubeck is not connected. Xcode will continue when iPhone de Jan Lubeck is connected. (code -13)

• No issues found!

Try enabling "pause on exception" feature in the debugger of your IDE

@nt4f04uNd  Do you know where that is on Android Studio? Can't seem to find it...

@jlubeck https://stackoverflow.com/questions/24718958/android-studio-ide-break-on-exception

Looks like I already had everything checked:

Switch to "Break on all exceptions"

Aha!! Thanks!

Though it's still unclear, why the stacktrace didn't print

Well, thanks to the break on all exceptions, it stopped here in one of my external dependencies:
    try {
      _doc = await widget.build(pageFormat);
    } catch (e) {
      error = e;
      return;
    }

So it was a caught exception. Should it be printing the stacktrace there? If it should, I'll reopen the issue

From the code you shown it's not obvious to me why the flutter would show an exception. AFAIK stack traces should be always printed, but I'm not sure, so better to reopen it for someone else to look at.

Hello @jlubeck
can you please try without a try-catch bloc to see the stack trace?
One variable is null by the way that's why this error is occur.
Thanks

The problem is that part is not part of my code, it’s on an external dependency

On Nov 25, 2020, at 12:24 AM, Abhishek Ghaskata<EMAIL_ADDRESS>wrote:

Hello @jlubeck
can you please try without a try-catch bloc to see the stack trace?
One variable is null by the way that's why this error is occur.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi @jlubeck
Following the indication of jetbrains' Flutter plugin, the correct way to address the problem is to open an issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Remove redundant usage of object URNs in database commands

The ADS half of this STS change: https://github.com/microsoft/sqltoolsservice/pull/2245
Leaving this as a draft until the new STS build is published.

Changes included in STS version bump:


Broken links

Hi,
There are quit a few broken links on:
https://github.com/pshihn/rough/wiki/Examples
The dist folder (mentioned on https://github.com/pshihn/rough) is also missing

All of the images won't preview in the wiki https://github.com/pshihn/rough/wiki/Examples

Links are fixed. There's a new "Gallery" page coming on the website which will have links to more. examples

Image links seem broken again throughout the wiki.


[python] support building bindings for multiple python version

Right now we support building only against one python version. It is standard in distributions to provide both python2 and python3 bindings. We already support building against python2 and python3, but only one at a time. It would be nice to support building against multiple python versions out of the box.
We my want to use setup.py to build the python bindings, but that require some work. However, it seems to to be the de facto way of building extensions.

Agreed! On another project I call out to setup.py from the build system, it should be possible. I have never built for multiple pythons though. I think swig needs to be run with different flags for python2 and python3 so I guess it might need a bit of work to put the outputs in different directories.

Ok I didn't get your point, but we are on the same page. It is low priority I'd say, but migrating to using setup.py for that seems to be the way to go.

Indeed, seems that setup.py can handle building 'extensions' and passing options to swig.  Not sure if that's better or worse than running it from cmake, but if it can automatically handle multiple Pythons then maybe it's the bets way forward.  I would have to try it on a test project to see how it could work.

Le 5 janv. 2017 à 15:16, Stephen Sinclair<EMAIL_ADDRESS>a écrit :
Yep, I'm aware of -py3, but my point was more that the output from swig is distinct in the two cases, so swig needs to be run once for each Python and the output stored in different places. We can't just compile the same cpp from swig for each Python.

Yes, I think you’re right.
A simple(ugly) solution is to configure (cmake) first with python2 detection build and install
and then cmake/build/install again but with python3
which leads to siconos-python packages installed in both the python2 and python3 site-packages directories.
I’m not sure but I think that cmake just checks which python version is in the PATH and then do the proper config.
So I guess that a user with multiple versions of python will be able to switch between them (using pyenv for example) and build two
different versions of siconos-python interface.
By the way for the notebooks on https://notebook-ljk.imag.fr https://notebook-ljk.imag.fr/ I used python3 without any change in siconos config (no -py3, just python default being python3 ) and it worked well.

For example, currently the build directory features folders like build/numerics/swig, it will have to be changed to output build/numerics/swig-py2 and build/numerics/swig-py3. On the other hand maybe we can get setup.py to handle this for us. Right now we use cmake to run swig but perhaps setup.py could be responsible for it. I'll look into how that works.

I looked at this before …As far as I remember that was possible but quite painful ...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/siconos/siconos/issues/96#issuecomment-270653475, or mute the thread https://github.com/notifications/unsubscribe-auth/AHbsU6RVeVAgsp4vc0bNsybHtDhpPvlbks5rPPtHgaJpZM4LbkI5.

Just reading up on this, it seems even a CMake developer recommends just calling CMake twice for each Python version.  Supporting both may be next to impossible without official CMake support.  Although this is from 4 years ago, maybe things have changed, but I can't find anything more recent.
https://public.kitware.com/Bug/bug_relationship_graph.php?bug_id=13857
On the other hand I had a look at the VERBOSE=1 output for CMake running swig when set to a Python3 executable, and it does not provide the -py3 flag as far as I can tell.
If we do want to make the effort to build both, probably the only reasonable way is to switch for calling setup.py from each supported Python and using a fake 'timestamp' target: https://bloerg.net/2012/11/10/cmake-and-distutils.html

If we do want to make the effort to build both, probably the only reasonable way is to switch for calling setup.py from each supported Python and using a fake 'timestamp' target: https://bloerg.net/2012/11/10/cmake-and-distutils.html

On Gentoo, there is a support to build against multiple python install. I think the trick is to call setup.py from different interpreter. In cmake, we could loop over the python implementation requested by the user on the command line and use a buildir like build_${PYTHON_EXECUTABLE} (if PYTHON_EXECUTABLE is python2.7). The difficult part is to migrate the cmake code (swig calls + doxy2swig + ...)


#3138 #3488 refactor ClansView

I'm just started to getting to know CoffeScript and your code base, digging around like this would be the best approach for me. I will edit my code and make a new commit soon

Sounds good!
There are many inconsistencies in the codebase, as we move generally toward using 3rd party tools the way they were intended, particularly in how we use Express on the server and Backbone on the client, and adding tests. When in doubt, check the cookbook, which has up to date guidelines, or ask on feel free to ask on #general. The latter will help us figure out what to add to the Cookbook.
Thanks again!

👍
Squashed and merged in: 2ded5ff4f063a2dda4717b0cde6d65f1bbf1a432


winit panicks failing to find x11 monitor

copied from https://github.com/tomaka/glutin/issues/1018:
When I iterate over available monitors with events loop, nothing is returned, and attempting to call get_primary_monitor() will crash:
extern crate glium;
use glium::glutin;

fn main () {
  {
    let events_loop = glutin::EventsLoop::new();
    let mut available_monitors_count = 0;
    for i in events_loop.get_available_monitors() {
      available_monitors_count += 1;
    }
    println!("avilable monitors count: {}", available_monitors_count);  // prints '0'
    let primary_monitor = events_loop.get_primary_monitor(); // crash 1
  }
  let events_loop = glutin::EventsLoop::new();  // crash 2
}

crash 1 with:
thread 'main' panicked at '[winit] Failed to find any x11 monitor', libcore/option.rs:916:5

If crash 1 is commented out, then code will reach crash 2 with:
thread 'main' panicked at 'Failed to call XInternAtom: XError { description: "BadRequest (invalid request code or no such operation)", error_code: 1, request_code: 140, minor_code: 42 }', libcore/result.rs:945:5

Previously the iter loop would show some available monitors, and the primary monitor would be returned, but I'm not sure exactly what has changed since the last time it worked. This is on end of life LTS Ubuntu (14.04) so it may be something out of date.

Can you tell me the output of xrandr --version?

Versions of XRandR earlier than 1.5 use a different code path, but should still work. It's just, as you might guess, it tends not to get tested.
...wait, actually, what version of winit are you running? I just noticed the "BadRequest (invalid request code or no such operation)" error, which would seem to suggest a protocol issue, and distinction between XRandR 1.5 and earlier versions wasn't implemented until relatively recently.

Ah, I was getting the dependency from glium which has a lagging dependency on glutin which in turn has a lagging dependncy on winit 12.0.
Updating both to use winit 14.0 does fix the 2nd panic (creating another event loop after the first has been dropped), but the 1st panic remains.

Just another data point:
$ xrandr --version
xrandr program version       1.4.2
Server reports RandR version 1.4

With the glium code, the following winit code and with one or two connected monitors I could not observe any crashes.
extern crate winit;

fn main () {
  {
    let events_loop = winit::EventsLoop::new();
    let mut available_monitors_count = 0;
    for i in events_loop.get_available_monitors() {
      available_monitors_count += 1;
    }
    println!("avilable monitors count: {}", available_monitors_count);  // prints '0'
    let primary_monitor = events_loop.get_primary_monitor(); // crash 1
  }
  let events_loop = winit::EventsLoop::new();  // crash 2
}

xrandr --listmonitors --verbose might contain some interesting information.

$ xrandr --listmonitors --verbose
xrandr: unrecognized option '--listmonitors'
Try 'xrandr --help' for more information.

this seems to show some kind of display information, not sure how it's different from 'monitors':
$ xrandr -q
Screen 0: minimum 8 x 8, current 1600 x 900, maximum 16384 x 16384
VGA-0 disconnected primary (normal left inverted right x axis y axis)
LVDS-0 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
   1600x900       60.0*+   40.0
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

$ xrandr -q
Screen 0: minimum 8 x 8, current 3286 x 1080, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 260mm x 140mm
   1366x768      59.97*+
   1360x768      59.96
   1280x720      60.00
   1024x768      60.00
   1024x576      60.00
   960x540       60.00
   800x600       60.32    56.25
   864x486       60.00
   640x480       59.94
   720x405       60.00
   680x384       60.00
   640x360       60.00
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1920x1080+1366+0 (normal left inverted right x axis y axis) 530mm x 300mm
   1920x1080     60.00*+
   1680x1050     59.88
   1600x900      59.98
   1280x1024     75.02    60.02
   1280x800      59.91
   1152x864      75.00
   1280x720      59.97
   1024x768      75.08    60.00
   832x624       74.55
   800x600       75.00    60.32
   640x480       75.00    60.00
   720x400       70.08
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Ah, sorry, I guess --listmonitors must be a 1.5 thing.
@b-r-u unless you have a burning desire to trawl through the RandR spec, I'll take a crack at fixing this.

@francesca64 Please do, I have very little experience with the RandR protocol!

@spearman this branch adds some debug messages: https://github.com/francesca64/winit/tree/x11-randr
@b-r-u XRRGetScreenResources is apparently really slow, so I'm going to look into caching the monitor list and using XRRSelectInput to receive events when the state changes. That's totally unrelated to this problem; I just enjoy caching things.

Compiling against the x11-randr branch actually detects 1 monitor and doesn't crash at all:
     Running `target/debug/examples/crash`
PRIMARY 636
CRTC_COUNT 2
> CRTC #0
·> ID 634
·> WIDTH 1600
·> HEIGHT 900
·> OUTPUT_COUNT 1
·> IS_VALID true
> CRTC #1
·> ID 635
·> WIDTH 0
·> HEIGHT 0
·> OUTPUT_COUNT 0
·> IS_VALID false
avilable monitors count: 1
PRIMARY 636
CRTC_COUNT 2
> CRTC #0
·> ID 634
·> WIDTH 1600
·> HEIGHT 900
·> OUTPUT_COUNT 1
·> IS_VALID true
> CRTC #1
·> ID 635
·> WIDTH 0
·> HEIGHT 0
·> OUTPUT_COUNT 0
·> IS_VALID false
PRIMARY 636
CRTC_COUNT 2
> CRTC #0
·> ID 634
·> WIDTH 1600
·> HEIGHT 900
·> OUTPUT_COUNT 1
·> IS_VALID true
> CRTC #1
·> ID 635
·> WIDTH 0
·> HEIGHT 0
·> OUTPUT_COUNT 0
·> IS_VALID false

Wait, really? All I did was refactor the monitor module. Well, I updated the branch to be ready for merging (besides the fact that I still need to impl Debug for MonitorId on all the other platforms) so if things still work after you pull that, I guess this is fixed.
I plan on putting out a 0.14.1 release soon, which will include this.
(Since this was so quick, I'll save the caching for future work.)

Hmm, yeah now it finds 0 monitors again and crashes on the call to get_primary_monitor

The only way it could've changed is if it's somehow a timing issue that the println! calls accidentally fixed, and since all the XRandR calls we make are synchronous, that shouldn't be possible.

...though, I guess that's specifically what git bisect is for, but I've never used it.

I've pushed another commit which will print any X11 errors that occur, so if it's a protocol issue we'll find out quite easily.

Well I don't see any X11 errors printing out, but this time it detects 1 monitor, but it's not the primary monitor, and crashes when trying to get primary (I added a debug print of the 1 available monitor):
     Running `target/debug/examples/crash`
available monitor: MonitorId { inner: X(MonitorId { id: 634, name: "LVDS-0", dimensions: (1600, 900), position: (0, 0), primary: false, hidpi_factor: 1.3333334 }) }
avilable monitors count: 1
thread 'main' panicked at '[winit] Failed to find any x11 monitor', libcore/option.rs:914:5

Ha, there's definitely something funky happening here. The thing is, if there's no primary monitor detected, get_primary_monitor just returns the first monitor in the list, and get_primary_monitor calls get_available_monitors internally. This means you're getting inconsistent results between calls.

Is it consistently the second call that fails? Note that on master, the monitor list is now cached, so you'd want to disable that: https://github.com/tomaka/winit/blob/cebd15bfd1c5f9915fa5a97cfe0025bc462089e9/src/platform/linux/x11/monitor.rs#L19
Can you try capturing some logs for me using xtrace (it's probably called x11trace, depending on the package manager)?

Running with the current master for some reason it takes the xrandr 1.5 path, although the version is 1.4:
000:<:0034: 12: RANDR-Request(140,0): QueryVersion major-version=1 minor-version=5
000:<:0035:  8: RANDR-Request(140,8): GetScreenResources window=0x0000028a
000:>:0034:32: Reply to QueryVersion: major-version=1 minor-version=4
000:>:0035:152: Reply to GetScreenResources: timestamp=0x00006fee config-timestamp=0x00006fee crtcs=0x0000027a,0x0000027b; outputs=0x0000027c,0x0000027d,0x00000280,0x00000281,0x00000282,0x00000283,0x00000284,0x00000285; modeinfos={id=0x0000027e width[pixels]=1600 height[pixels]=900 dot_clock=110000000 h_sync_start=1664 h_sync_end=1706 h_total=2010 h_skew=0 v_sync_start=903 v_sync_end=906 v_total=912 name_length=8 mode_flags=HSyncNegative,VSyncNegative},{id=0x0000027f width[pixels]=1600 height[pixels]=900 dot_clock=73330000 h_sync_start=1664 h_sync_end=1706 h_total=2010 h_skew=0 v_sync_start=903 v_sync_end=906 v_total=912 name_length=8 mode_flags=HSyncNegative,VSyncNegative}; mode names='1600x9001600x900'
000:<:0036: 12: RANDR-Request(140,42): UNKNOWN opcode=0x8c opcode2=0x2a unparsed-data=0x8a,0x02,0x00,0x00,0x01,0x00,0x00,0x00;
000:>:0036:Error 1=Request: major=140, minor=42, bad=650
[winit X11 error] XError {
    description: "BadRequest (invalid request code or no such operation)",
    error_code: 1,
    request_code: 140,
    minor_code: 42
}
monitor count: -1
thread 'main' panicked at 'capacity overflow', liballoc/raw_vec.rs:741:5

If I set FORCE_RANDR_COMPAT to true here's the output of xtrace:
https://gist.github.com/spearman/f5d443ae9186fa584cdb6f6a972d7081

Running with the current master for some reason it takes the xrandr 1.5 path, although the version is 1.4

That's really weird. The condition should work the same as it did before: https://github.com/tomaka/winit/blob/v0.13.0/src/platform/linux/x11/monitor.rs#L28
I could just query the extension version instead of basing it on library availability, which is probably more correct anyway.
(and at bare minimum, an assert that monitor_count isn't negative...)
Anyway, I found the problem, and it's amusing. I pretty much never use iterators, so when I refactored, I didn't realize that calling next after calling find like that would always result in None. This is much better than the conclusion that this is caused by some esoteric race condition.
New branch: https://github.com/francesca64/winit/tree/x11-unregress-monitors

New branch: https://github.com/francesca64/winit/tree/x11-unregress-monitors

Ok, now that one works, finds the primary monitor and no crashes =)


SubMenu arrows get distorted

Hi
I am using the SubMenu as follow:

for some reason, is random times, the submenu arrow is being distorted

Any idea why it gets distorted?

Hi @tssobe , it's hard to tell what problem might be from the screenshots. Can you post a minimal example showing the issue?

Hi @szhsin , the issues that the arrows of the submenu become distorted as you can see in the screenshot.
Without the distortion is should look:

It looks like a styling issue. If you are using the arrow which comes with the default style, it's an ::after pseudo-element that might be overridden by your global style sheets under some conditions.
Try to create the arrow with a div in the label prop to see if the problem resolves.


Have a project with common concepts between spectre.console and spectre.cli

I have a project using spectre.cli and now I want to add spectre.console to it, in order to improve the user experience.
I noticed that a concept like "ValidationResult" exists in both projects, so, it will exist in both namespaces.
I see the potential of using both projects together, so I have been thinking if it wouldn't be a good idea to have a "core" project with base concepts common to both (like the ValidationResult).
Sorry if this is not the best place to give this kind of feedback since it impacts both projects.

@gsferreira Thanks for the suggestion!
I however want to keep the two projects separate and don't want them to rely on shared definitions since this will make it more difficult to change things in the future and I don't want the cognitive overhead it would impose. One solution to this could be to rename the ValidationResult class in one library to something else. I will think about it.


Auto-generated code for main

As titled

:broken_heart: Build Failed

Buildkite Build
Commit: 0baf9ab75204331fb0714483419a7125f26c91df

Failed CI Steps

:junit: Test results

Going to wait til I get those integration tests working before merging.

:broken_heart: Build Failed

Buildkite Build
Commit: 8f33d4530dc3bd0d4a438d79ef1618cfc1d4a677

Failed CI Steps

:junit: Test results

History

:broken_heart: Build #869 failed 0baf9ab75204331fb0714483419a7125f26c91df

:broken_heart: Build Failed

Buildkite Build
Commit: 2d591ceed3e0c1339adc7aa83a8db4a215e45257

Failed CI Steps

:junit: Test results

History

:broken_heart: Build #872 failed 8f33d4530dc3bd0d4a438d79ef1618cfc1d4a677
:broken_heart: Build #869 failed 0baf9ab75204331fb0714483419a7125f26c91df

:broken_heart: Build Failed

Buildkite Build
Commit: e4e110e6a3da22f57be8461785e407d3b971429a

Failed CI Steps

:junit: Test results

History

:broken_heart: Build #877 failed 2d591ceed3e0c1339adc7aa83a8db4a215e45257
:broken_heart: Build #872 failed 8f33d4530dc3bd0d4a438d79ef1618cfc1d4a677
:broken_heart: Build #869 failed 0baf9ab75204331fb0714483419a7125f26c91df

:broken_heart: Build Failed

Buildkite Build
Commit: e4e110e6a3da22f57be8461785e407d3b971429a

Failed CI Steps

:junit: Test results

History

:broken_heart: Build #894 failed e4e110e6a3da22f57be8461785e407d3b971429a
:broken_heart: Build #877 failed 2d591ceed3e0c1339adc7aa83a8db4a215e45257
:broken_heart: Build #872 failed 8f33d4530dc3bd0d4a438d79ef1618cfc1d4a677
:broken_heart: Build #869 failed 0baf9ab75204331fb0714483419a7125f26c91df

:broken_heart: Build Failed

Buildkite Build
Commit: 7ddd08ff85ca8336fa1bead7b4fb928db03888ea

Failed CI Steps

:junit: Test results

History

:broken_heart: Build #895 failed e4e110e6a3da22f57be8461785e407d3b971429a
:broken_heart: Build #894 failed e4e110e6a3da22f57be8461785e407d3b971429a
:broken_heart: Build #877 failed 2d591ceed3e0c1339adc7aa83a8db4a215e45257
:broken_heart: Build #872 failed 8f33d4530dc3bd0d4a438d79ef1618cfc1d4a677
:broken_heart: Build #869 failed 0baf9ab75204331fb0714483419a7125f26c91df

:green_heart: Build Succeeded

Buildkite Build
Commit: be66bdf1847a855b689b5c8bba61732777ff65bf

History

:broken_heart: Build #897 failed 7ddd08ff85ca8336fa1bead7b4fb928db03888ea
:broken_heart: Build #895 failed e4e110e6a3da22f57be8461785e407d3b971429a
:broken_heart: Build #894 failed e4e110e6a3da22f57be8461785e407d3b971429a
:broken_heart: Build #877 failed 2d591ceed3e0c1339adc7aa83a8db4a215e45257
:broken_heart: Build #872 failed 8f33d4530dc3bd0d4a438d79ef1618cfc1d4a677
:broken_heart: Build #869 failed 0baf9ab75204331fb0714483419a7125f26c91df


undeploy didn't nuke my apigw custom domain

Context
I did a 'zappa undeploy production' for a project with a 'domain' set under 'production'.
Expected Behavior
I expected that to correctly remove the apigw entries that it created.
Actual Behavior
It removed the API-GW API, but not the 'Custom Domain Name' that it was using.  The custom domain was 'emptied', however, in that it no longer listed any API Mappings, but I can't tell if that was Zappa doing its job or AWS nuking a reference to a no-longer-existing API entry.
Possible Fix
Your Environment

zappa --version => 0.37.1
linux (ubuntu 16.04)
python -V => 2.7.12

There is a TODO in the code about this - the question is should Zappa do this or not.
I guess it should remove the Domain Name from API Gateway, but not remove the Route53 entry. Make sense?

Agreed.

Wait, why not remove the Route53 entry?  It's an alias that points to the API-GW custom domain ('8ukj2r8fajf8jq24f.cloudfront.net') right?  And that domain is going to be completely invalid if you nuke the API-GW.  So why not update the Route53 entry?  Or at least have an option to do so?

We could remove just the one CNAME record I suppose

Yeah, I'd consider doing that under the heading of 'maintain referential integrity'.  It's not a database, but the concept still kind of applies.

I suggest providing a flag to enable the feature, but have it remove the route53 as well as the custom domain name.
In the past I would have said to not remove the custom domain name, but since AWS can handle the certificates through ACM, its not a big deal anymore.

I can't believe this still is open. MUSTFIX for next release!


Load tests CLI

It would be nice to be able to run the load tests via CLI, passing params as command line args

we have quite a lot a params, I think from a file might be better.

we have quite a lot a params, I think from a file might be better.

Yeah, I'm thinking a config file that holds the majority of vars such as urls, faucet key, etc. but that can be overridden with command line args such as number of txs, users, delays...


Add //> using jvm "…" directive

Is your feature request related to a problem? Please describe.
Users can ask for a custom JVM on the command line, like scala-cli --jvm 11 foo.sc. Yet there's no corresponding using directive.
Describe the solution you'd like
Directives such as these should be accepted by Scala CLI:
//> using jvm "11"
//> using jvm "graalvm-java17:22.2.0"

Should be a matter of setting jvmIdOpt in the BuildOptions provided by the directive.

Fixed by #1539.


Externalize docker and postgres configs

Move docker-compose and postgresql.sql to quarkuscoffeeshop-support

quarkuscoffeeshop-support


Rework include controller view handling to allow the called controller to specify the view (edit: this was a mistaken assumption)

The current functionality for includes only allows specifying the include view in the calling controller. If you specify a view in the include controller, it's ignored, which means the calling controller must specify the view if it's anything other than the default.
This is unintuitive (determined through my own mistakes in recalling how it works while trying to use it). Ideally, the include controller should be able to specify a custom view using the view directive within the called action like any other controller action.
The only question is which should take precedence: the view specified in the include controller action itself, or the view specified for the include in the calling controller. On one hand, it makes sense to look at the calling controller's include view as an overwrite that takes priority over the include controller's view. However, using the include's view as the higher priority seems a bit more modular, in that the include controller is ultimately in charge of how it renders by enforcing its own rules.
Either way, initial attempts to make this work broke controller caching because the include controller's view can't be known until after the controller action is called, yet the cache check happens before that (line 1142 in server.js).

The issue with include controller view directives not working was fixed in 296b32b. The longstanding issue with caching include controllers that specify an alternate view is the real problem here.
See #78. No resolution expected.


Is there a way to filter out mature listings from the API?

I'm trying to find groups for families with similar interests with the following API:
https://api.meetup.com/find/groups?text=oceans+OR+craft+OR+flowers+OR+dinosaurs+OR+planets&zip=94063&country=US&radius=25&offset=0&page=20&key=API_KEY
There seem to be mature listings returned in the response that I would like to filter out.
"Bay Area Naked Club Nature Outings and Events"
Is there a way for me to achieve this?

+1 for this

(I am not affiliated with meetup. But have made an Oauth2 meetup app 😉)
Seems like text delimited by spaces performs an "AND".
A hack that I would suggest,
Batch requests using Oauth2
https://www.meetup.com/meetup_api/docs/batch/
(I have not tackled batch requests yet. But it is on the to do list.)
api.meetup.com/find/groups?text=oceans&zip=94063&country=US&radius=25&offset=0&page=20&key=API_KEY
api.meetup.com/find/groups?text=craft&zip=94063&country=US&radius=25&offset=0&page=20&key=API_KEY
api.meetup.com/find/groups?text=flowers&zip=94063&country=US&radius=25&offset=0&page=20&key=API_KEY
api.meetup.com/find/groups?
text=dinosaurs&zip=94063&country=US&radius=25&offset=0&page=20&key=API_KEY
api.meetup.com/find/groups?
text=planets&zip=94063&country=US&radius=25&offset=0&page=20&key=API_KEY


Listen NetInfo connectionChange event (change deprecated)

Fixes #75

@kytwb Great, thanks!
Just a quick question, would that cause a problem for users with lower versions of RN? (I think it's polite to support at least 1-2 previous versions)

@kfiroo I'll check and make it backward compatible if possible.
If not possible, what should I do? Follow semver and major/minor the version?

@kytwb Thanks!
If you can't make it backward compatible we should merge it after the 1.4 version, which already forces users to upgrade

Will this work?
https://github.com/facebook/react-native/issues/12503
just check if RN >= 0.48.0 then use connectionChange event name


Ability to see the generated code before deciding on whether to copy

Description
I really appreciate the idea behind this project. Would it be a good idea to preview the CSS code generated on the webpage below or near the output?
Screenshots
No response
Additional information
This may require some CSS library for syntax highlighting.
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

Hi thanks for this issue, how do you plan on doing this?

I think the easiest solution would be to depend on a syntax highlighting library for CSS and just add the specific html

doesn't sound as useful

If the user gets to see the code generated before they copy, chances are they might come up with some rather interesting stuff. Say, for example, it'll be easier for the user to understand what kind of CSS is being generated, useful for both people trying to learn or how to come up with say a combination of shadows and other effects (as in when certain properties might be more useful). This would also help beginners in particular I feel, so that they could easily approach other styling ideas.

not the feature itself, more like the method to do it

I think a better way would be to change the Get code button on the results page to Preview.  When clicked, the new preview button displays a modal where the user sees generated code snippet, and a Get Code  button to copy to clipboard.
It could look something like this 👇 👇:

how about it being like a sidebar? that opens on closes so basically like the result section that opens by the side but smalller?

Absolutely that would work too. But I think with regards to user experience and intuitiveness, the modal display would be a much better approach.

Absolutely that would work too. But I think with regards to user experience and intuitiveness, the modal display would be a much better approach.

I disagree, it's much easier to open and close it than the modal, when it's open they compare things. But once again I tried to make it more accessible, so we won't need that feature, like the number of degree changes when you slide or the colour showing too.
Maybe we should figure out how to make that better rather than the modal or extra review


Ban one element tuples harder

After the Sema change I added an assert to IRGen to ensure we don't emit one-element tuple metadata. After fixing some other causes of this assert, I uncovered a new bug in lazy metadata emission! Makes this change all the more worth it.
Fixes rdar://problem/30384023, rdar://problem/41474370,
and https://bugs.swift.org/browse/SR-8109.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please test

@swift-ci Please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 0c8337c9642043b12058a63eada26b804463a651

Build failed
Swift Test Linux Platform
Git Sha - 0c8337c9642043b12058a63eada26b804463a651

Does the new error happen in Swift 4.2 mode? If it does, this change will almost certainly break something; it might be better to warn the user and correct the AST if they're not in Swift 5 mode.


Add progress messages to CTS for long running CTS

Description
When working with MegaBoom, CTS can take a long time(stopped after 30000s or 10 hours or so...).
To reproduce, unzip https://drive.google.com/file/d/1rgNaEOD-IP0Ae16ZSTZKyV3ZC2t-QLHd/view?usp=sharing
$ ./run-me-BoomTile-asap7-base.sh
OpenROAD v2.0-11160-g042cdcfa4
This program is licensed under the BSD-3 license. See the LICENSE file for details.
Components of this program may be licensed under more restrictive licenses which must be honored.
clock_tree_synthesis -root_buf BUFx4_ASAP7_75t_R -buf_list BUFx4_ASAP7_75t_R -sink_clustering_enable -sink_clustering_size 30 -sink_clustering_max_diameter 100 -balance_levels -distance_between_buffers 60
[INFO CTS-0049] Characterization buffer is: BUFx4_ASAP7_75t_R.
[deleted]

[INFO CTS-0102]  Path depth 78 - 79
[WARNING STA-0357] virtual clock clock_vir can not be propagated.
Warning: There are 380 unconstrained endpoints.

==========================================================================
cts pre-repair report_check_types -max_slew -max_cap -max_fanout -violators
--------------------------------------------------------------------------
-148.0156
-1.0903

==========================================================================
cts pre-repair report_design_area
--------------------------------------------------------------------------
Design area 4644608 u^2 20% utilization.
[INFO RSZ-0058] Using max wire length 162um.
[INFO RSZ-0047] Found 79 long wires.
[INFO RSZ-0048] Inserted 295 buffers in 79 nets.
Warning: There are 380 unconstrained endpoints.
[never completes]

Suggested Solution
Some sort of progress message to give an idea of how long it will run, or if it is hopeless and the problem needs to be fixed earlier in the flow.
Additional Context
No response

Try repair_timing -verbose and see if that's what you want

Try repair_timing -verbose and see if that's what you want

No effect, it churns here with no further output:
[INFO CTS-0099]  Sinks 352871
[INFO CTS-0100]  Leaf buffers 11846
[INFO CTS-0101]  Average sink wire length 8833.40 um
[INFO CTS-0102]  Path depth 78 - 79
[WARNING STA-0357] virtual clock clock_vir can not be propagated.
Warning: There are 380 unconstrained endpoints.
[no further output]

I think is sta computing timing and CTS itself is done.
@tspyrou do you want to discuss such messages with Cherry?


price too precise

I was placing a buy order at buyprice 816.95 with buy method . But it shows {u'message': u'price too precise<PHONE_NUMBER>999999)'} sometimes . how to avoid this problem?

All values are sent over the wire as strings - if you do nothing, your float is implicitly converted to string along with its imperfect precision. Here are some example solutions.

just do auth_client.buy(price= round(price,2), size=size, product_id='LTC-USD')
notice: round(price,2)


Lint XSD files

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When I use the VALIDATE_XML, I always get a successful build even with multiple errors in the file.
Expected Behavior
I expect error outputs when malformed xsd files are linted.
Super-Linter version
v6.0.0

Relevant log output
none

Steps To Reproduce

Include the following in the xsd file:

<?xml version = "1.0" encoding = "UTF-8"?>
<!-- $Header: /cvsroot/ebxmlrr/ebxmlrr-spec/misc/3.0/schema/rim.xsd,v 1.20 2005/02/03 19:28:15 farrukh_najmi Exp $ -->
<schema targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
  xmlns="http://www.w3.org/2001/XMLSchema"
  xmlns:tns="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
  xmlns:xml="http://www.w3.org/XML/1998/names=
      <maxLength value="4"/>

Push to github and run the action.
Below is my output with the above xml in my xsd file.

Anything else?
No response

Hi @Dosanyintolu1 !
Include the following in the xsd file: what extension does the file have?
In the current implementation, super-linter lints files with a .xml extension using xmllint. We can probably check .xsd files as well. xmllint seems to support this, at least for syntax.

#5250 should take care of this

@ferrarimarco Sorry for the late response. But yes, its an xsd extension. Now you've created the PR to fix this, do I have to wait for it to be merged before I can test again ?

No worries! You're correct :)


Enable CoreOS rolling upgrades

We've always disabled automatic updates on CoreOS, because we used to see incompatibilities between versions of etcd and fleet. Now that we're using the CoreOS stable channel and upgrades should be backwards-compatible, we should consider enabling updates as CoreOS does by default.

dupe of #1043


Error: invalid format

When I ran:
jeff@MacBook-Pro wasm % cargo fund
Error: Github API token must be provided through the CARGO_FUND_GITHUB_API_TOKEN environment variable or the --github-api-token flag.
jeff@MacBook-Pro wasm % cargo fund --github-api-token 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
Error: Insufficient Github API token scopes. Modify your token to include the `public_repo` and `user` scopes at https://github.com/settings/tokens.
jeff@MacBook-Pro wasm % cargo fund --github-api-token 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
Error: invalid format
jeff@MacBook-Pro wasm % cargo fund --github-api-token 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
Error: invalid format
jeff@MacBook-Pro wasm %

I've deleted both tokens so it's safe to post them here.

We have this issue as well, running with RUST_LOG=debug environment variable shows that we depend on https://docs.rs/simple-mutex, which points to https://github.com/stjepang/simple-mutex, which is a deleted repo.
cargo-fund should probably report this error and continue

@VictorKoenders I created a test project just now with simple-mutex as a dependency and am unable to reproduce the issue:
[dependencies]
simple-mutex = "^1.1.5"

❯ cargo fund
    Updating crates.io index
  Downloaded simple-mutex v1.1.5
  Downloaded 1 crate (11.5 KB) in 0.28s
/tmp/cargo-fund-test (found funding links for 0 out of 2 dependencies)

I do see the log output about the inability to resolve, but it does not lead to an error:
Apr 25 15:48:56.672  INFO cargo_fund::github: Could not resolve to a Repository with the name 'stjepang/simple-mutex'.

@surferjeff apologies for not catching this issue when it was first opened, but do you have any other detail that might help reproduce?

I'm seeing the same error even when I try to run cargo fund on the cargo-fund repo itself

@emschwartz thank you! That was the hint I needed. Fixed in #9 and the subsequent 0.2.1 release.

Excellent! Glad to hear it -- and thanks for fixing that


fix deprecation float -> Decimal

Decimal.new to convert a float is deprecated. Using Decimal.from_float removes deprecation warning

some refactoring is done, so I will just close this. Thanks!


Cannot connect to any (Azure) database

Issue Type: Bug

Go to "New connection"
Type or copy-paste server information and credentials
Click "Connect"
Loading indicator spins infinitely and doesn't throw any errors. However the software is responsive and I can click "Cancel" to close the connection panel.

I tried to set server info in few ways:

xxxxxx.database.windows.net

Without specified port
Set the port 1433 in "Advanced" section

xxxxxx.database.windows.net,1433
xxxxxx.database.windows.net:1433

SQL Operations Studio version: sqlops 0.30.6 (df7e3ec7d52a82febee5b597a1019cabf021b883, 2018-06-19T21:50:31.119Z)
OS version: Linux x64 4.15.0-24-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 2504)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: unavailable_softwarevideo_encode: enabledvpx_decode: unavailable_softwarewebgl: enabledwebgl2: enabled

Load (avg)
2, 1, 0

Memory (System)
15.43GB (10.01GB free)

Process Argv
/usr/share/sqlops/sqlops --unity-launch

Screen Reader
no

VM
0%

Extensions: none

I am unable to repro this on my end. I'll let someone else confirm.

@MattIrv Unfortunately we do not have any on-prem servers. I've tried to restart the Studio and also my laptop, but it didn't help. Just now I tried to reinstall the Studio and it's still occurring.
Here's some additional information related to my case:

I installed via .deb package
I haven't been able to connect at all after installing the software, otherwise it seems to work nicely
I've checked and installed all the mentioned dependencies at https://docs.microsoft.com/en-us/sql/sql-operations-studio/download?view=sql-server-2017

I just noticed the docs stating you are officially only supporting Ubuntu 16.04, but not the latest LTS version. I'm using Linux Mint 19, which is based on Ubuntu 18.04 :(

I tested a fresh install of Ubuntu 18.04 and it worked just fine with a db server on azure.

@niklas-e Thanks for the additional info. This happens on Mint 19 because our logic for determining whether you're using a supported version of Mint hasn't been updated yet for version 19.
I'll make a fix but it probably won't be released for a while since I think it just missed our July release. In the meantime I've attached a patched file that you can download and copy over the corresponding file in your installation (on mine it's at /usr/share/sqlops/resources/app/extensions/mssql/node_modules/service-downloader/out/platform.js (rename the attached file from platform.txt to platform.js) and restart SQL Ops Studio and then it should work.
platform.txt

I can confirm what @MattIrv said, but for Gentoo. just added case for gentoo without any version.

@MattIrv cool, it's working now! Thank you!

The newest insiders build contains this fix and it will be included in the August public preview release, so I'll close this issue now. All unsupported Linux distros will now try to use our regular Linux service anyway


Script do not appear in the services Tab

Hello friends,
Was wondering what am I doing wrong:
I have a docker HA instance running with the HACS Integration on it.
I Installed pyscript using the HACS store and after creating a basic script under /pyscript/scripts/hello.py
I can see in the logs that HA has loaded the script:
[custom_components.pyscript.global_ctx] Loaded /config/pyscript/scripts/hello.py
However, after reloading the pyscript integration, I can not find the service anywhere
My HA configuration.yaml looks like:
...
pyscript: !include pyscript/config.yaml
...

and my pyscript config.yaml:
allow_all_imports: true
hass_is_global: true

has someone a hint ? Thanks in advance

Allright, I found the issue and I will post the fix in case someone has it too:
The python scripts should be in the form:
@service
def hello():
    """hello_world example using pyscript."""
    log.info("Hello")

@juanitoddd if this issue is resolved, please close it.


Bug: duplicate git source that cannot be deleted

📜 Description
I'm not sure how to recreate this but it has happened to me more than once. In short, it happens when trying to create a new application, and adding a git source. Sometimes that process fails with this message:

If I reload the page there are no git sources configured. So naturally I try to add the git source again. It works the second time around, but by the time I reach the pipeline configuration, I see that I have two souces. Looking back at the git source configuration page, I will now have the same git source configured twice.
When I try to delete one of them, it doesn't work. My only recourse is to completely delete the app and start all over again.
👟 Reproduction steps
Not sure, it's doesn't always happen, so I can't consistently make it happen, but as mentioned I've encountered this more than once
👍 Expected behavior
I should always be able to delete a git source. The fact that the same git source was created twice is an issue too, but the real problem is that I then couldn't delete it.
👎 Actual Behavior
I can't delete the duplicated source.
☸ Kubernetes version
EKS 1.30
Cloud provider
AWS
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Thank you for raising the issue @yuvii. I attempted to replicate the bug you reported but was unable to achieve the same outcome. Nonetheless, I will escalate this issue to the team to investigate further and identify the potential cause.


[Automation] Generate Fluent Lite from Swagger redisenterprise#package-preview-2024-09

[Automation] Generate Fluent Lite from Swagger redisenterprise#package-preview-2024-09

/azp run java - redisenterprise - mgmt - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-redisenterprise

close as service is not deployed yet.


"map loading" doesn't go away after downloadImg() runs

Duplicate of this https://github.com/datadesk/web-map-maker/issues/148


enable gofmt,golint and fix lint errors

Signed-off-by: silenceper<EMAIL_ADDRESS>
enable gofmt,golint for golangci, and fix lint errors.
gofmt  file pkg/scalers/azure/azure_monitor_test.go
gofmt -w -s pkg/scalers/azure/azure_monitor_test.go

Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)
[ ] Tests have been added
[ ] A PR is opened to update the documentation on https://github.com/kedacore/keda-docs
[ ] Changelog has been updated

Fixes #

How does this works with this:
https://github.com/kedacore/keda/blob/v2/Makefile#L199-L215

@zroubalik

make revive can change to make golangci
To be consistent, use gofmt instead of  go fmt , because gofmt tool is used in golangci.

@silenceper ok, would you mind changing the Makefile accordingly, please?

@zroubalik
PTAL

Yes, I add -s for gofmt.


Code will be out of bounds if long in tutorial

Describe the bug
Code will be out of bounds if long in tutorial
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Click any JS/Python tutorial (eg. Chase the Pizza)
Actual behavior
Code will be out of bounds if long in tutorial

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.7.2
3.Microsoft MakeCode version: 7.3.2

This is fixed now.


x/tools/gopls: autocompletion is appended to typed word

What did you do?
In VSCode, typed part of a word to autocomplete it, e.g. cancel, then selected cancelCtx.
What did you expect to see?
I expected the current word to be cancelCtx.
What did you see instead?
Current word became canccancelCtx.

Build info
Also getting this behaviour with v0.4.0.
golang.org/x/tools/gopls v0.3.4
    golang.org/x/tools/gopls@(devel)
<EMAIL_ADDRESS>h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
<EMAIL_ADDRESS>h1:Kpca3qRNrduNnOQeazBd0ysaKrUJiIuISHxogkT9RPQ=
<EMAIL_ADDRESS>h1:WG0RUwxtNT4qqaXX3DPA8zHFNm/D9xaBpxzHt1WcA/E=
<EMAIL_ADDRESS>h1:8gQV6CLnAEikrhgkHFbMAEhagSSnXWGV915qUMm9mrU=
<EMAIL_ADDRESS>=> ../
<EMAIL_ADDRESS>h1:/atklqdjdhuosWIl6AIbOeHJjicWYPqR9bpxqxYG2pA=
<EMAIL_ADDRESS>h1:sXmLre5bzIR6ypkjXCDI3jHPssRhc8KD/Ome589sc3U=
<EMAIL_ADDRESS>h1:KaMb5GLhlcSX+e+qhbRJODnUUBvlw01jt4yrjFIHAuA=

Go info
go version go1.14 darwin/amd64

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/alex/Library/Caches/go-build"
GOENV="/Users/alex/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY="github.com/t11e/*,github.com/sanity-io/gradient"
GONOSUMDB="github.com/t11e/*,github.com/sanity-io/gradient"
GOOS="darwin"
GOPATH="/Users/alex/.go"
GOPRIVATE="github.com/t11e/*,github.com/sanity-io/gradient"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/opt/go/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/opt/go/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/alex/Code/golang-tools/gopls/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/qs/wpmg19r12_9_nz7pvvs2_82r0000gn/T/go-build188118376=/tmp/go-build -gno-record-gcc-switches -fno-common"

VSCode
Version: 1.44.2
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T17:07:18.473Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

VSCode-Go 0.14.1.
Log
gopls.log.gz

Thanks for the report! /cc @muirdm

I think this is because incrementalAnalyzer{} is a syntax error without extra parents around it. The composite literal curlies are parsed as the if block curlies, so the AST is all messed up.
I'm not sure it would be easy to work around this type of syntax error. Maybe a code action to add in the missing parens?

@muirdm: No, that's not a syntax error.

Ah, I see what you're saying. It's not valid syntax in an if statement without parens.

Looks like it generally happens in the presence of syntax errors. For example:
expectErr := proto.QueryParseError{Description: "No query"})  // <-- extra parenthesis

If you try to autocomplete expectErr after this code snippet, the same thing happens.

Yup, syntax errors wreak all sorts of havoc. We try to work around "expected" syntax errors you get as you type code (e.g. as you type if fooBa), but unexpected syntax errors will still prevent completion from working properly due to various reasons.

FWIW, GoLand does not have this issue.

There are two steps to improving this in gopls:

Manually extract the completion prefix when there are syntax errors instead of depending on AST. This will fix all simple cases of "fooBa" completing to "fooBafooBar". We haven't done this because you will still get a degraded completion experience (e.g. gopls won't be able to determine the expected type), so we wanted to address common cases with special AST fixup logic so completion works optimally.
Manually parse and type check the surrounding expression. For example:

b := bytes.Buffer{}) // syntax error
b.Wr

To offer b.Write() properly, we need to manually extract the selector expression b and type check it (since it is not in the AST). It is easy in this case, but the left side of the selector can be an arbitrarily complex expression, so it is non-trivial to pick out out dependably. Out of curiosity, does GoLand handle selector expressions like this as well?

@muirdm  An example from GoLand. Is the GIF relevant to your question?

I'm not sure if I'm understanding it correctly, but in GoLang, it does seem like
b := bytes.Buffer{}) // syntax error
is valid in a sense
b := bytes.Buffer{}

From what I can tell, GoLand's parser is more lenient, and will recover from such parsing errors. I'm not able to make it break on unexpected tokens. For example, if you do:
b := bytes.Buffer{}:=
b2 := bytes.Buffer{}

then doesn't understand the type of b anymore, but it will happily continue to parse the rest of the file, and b2 will be autocompletable. Gopls just stops working.
Looking at how parser errors are phrased, it seems GoLand has its own parser, and doesn't reuse Go's.

Thanks. It makes sense that GoLand has its own parser since the standard library parser wasn't designed to work in the face of syntax errors.

It makes for any language server to have to its own parser. 😉 Editors aren't compilers, after all.
As an aside, this extends beyond just accidental syntax. Losing autocompletion occurs, of course, while just typing code. Here's an example where temporarily missing parantheses cause breakage:

That's unrelated to this bug, but it shows how the current parser is a problem.

Similar bug (the file has a syntax error some lines below the cursor):

Another example.
The first one (res.var) was ok, and then the second one (res.err) was messed up. This inconsistency makes the completion feature more confusing.

I'm experiencing the same issue when typing a comment for documenting a method/function. Typing the first few characters of the method/function name and pressing tab/enter afterwards used to autocomplete properly, but now it just appends the name to the already typed characters.

@kostaskoukouvis: That is https://github.com/golang/go/issues/39262.

@kostaskoukouvis: That is #39262.

Oops! My bad! :(

I'm experiencing the same issue here. The syntax error in my case was this statement:
if a, b _ = objobject.dosomething
When I removed the underscore, the autocorrect goes back to working as intended.


Review the Laboratory Report page and menu

Review the Laboratory Result Report (semantic-notes.html page)
possibly split in more pages
reorganize the menu entry (the current name is quite generic)

@kruzikh : check if you are OK with the applied changes

@gcangioli it look good. I just noticed that you renamed value sets by adding Vs to the name - I agree. I would also propose to change names of logical model by adding Lm into their names.


Support for non-64 bit and big-endian platforms

Current implementation works only on 64 bit little endian machines. There are slow-value feature but this feature currently does not help since Value is not fully implemented there.

New Value allows nan-boxing on 32 bit and big endian platforms.


About code wrt to the latest version of your paper

I am studying lifelong learning and I have read your great paper Lifelong Generative Model.  You have updated your paper to v6. This tf code is inconsistent with your latest version of the paper, neither the torch code. Could you release source code corresponding to the latest version please? Thank you.

Hi there,
Thanks for the interest! Yes the tf code is depreciated.
I am working on cleaning up the code to the final version in the following
branch:
https://github.com/jramapuram/LifelongVAE_pytorch/tree/feature/distributed_impl?files=1
however I will not be able to push the most recent changes for a few weeks.
Please bear with me!
On Wed, Dec 4, 2019 at 10:59 AM huanli2012<EMAIL_ADDRESS>wrote:

I am studying lifelong learning and I have read your great paper Lifelong
Generative Model. You have updated your paper to v6
https://arxiv.org/abs/1705.09847v6. This tf code is inconsistent with
your latest version of the paper, neither the torch code
https://github.com/jramapuram/LifelongVAE_pytorch. Could you release
source code corresponding to the latest version please? Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jramapuram/LifelongVAE/issues/2?email_source=notifications&email_token=AB6TEB2P2JXWL33YL7FC4A3QW6EP3A5CNFSM4JVGZAKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H56672A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6TEBZS6KKJ4AFS5W7M4C3QW6EP3ANCNFSM4JVGZAKA
.

Thank you for opening source code. I will follow with interest and looking forward to your early release.


RT3572

Hey
Can you please add rt3572 chipset in support list?

So the Supported Chipsets list isn't updated yet, but as of v2.0.2, all ralink firmware files are added.
If it still doesn't work, then it's very likely the kernel doesn't support this driver.

Closing due to inactivity.