PostgreSQL to MySQL change reflects these errors

After changing the database driver from postgresql_psycopg2 to mysqlclient driver and ran some migrations and saw this error messages:
WARNINGS:
?: (mysql.W002) MariaDB Strict Mode is not set for database connection 'default'
HINT: MariaDB's Strict Mode fixes many data integrity problems in MariaDB, such as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/4.0/ref/databases/#mysql-sql-mode
Operations to perform:
Apply all migrations: accounts, admin, app, auth, contenttypes, course, payments, quiz, result, sessions
Running migrations:
Applying payments.0002_testclass_array...Traceback (most recent call last):
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\mysql\base.py", line 75, in execute
return self.cursor.execute(query, args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\MySQLdb\cursors.py", line 179, in execute
res = self._query(mogrified_query)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\MySQLdb\cursors.py", line 330, in _query
db.query(q)
File "C:\Users\USER\Envs\sms\Lib\site-packages\MySQLdb\connections.py", line 255, in query
_mysql.connection.query(self, query)
MySQLdb.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near
'[200] DEFAULT () NULL' at line 1")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\USER\Desktop\Projects\sms\manage.py", line 23, in
main()
File "C:\Users\USER\Desktop\Projects\sms\manage.py", line 17, in main
execute_from_command_line(sys.argv)
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\core\management_init_.py", line 446, in execute_from_command_line
utility.execute()
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\core\management_init_.py", line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\core\management\base.py", line 414, in run_from_argv
self.execute(*args, **cmd_options)
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\core\management\base.py", line 460, in execute
output = self.handle(*args, **options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\core\management\base.py", line 98, in wrapped
res = handle_func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\core\management\commands\migrate.py", line 290, in handle
post_migrate_state = executor.migrate(
^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\migrations\executor.py", line 131, in migrate
state = self._migrate_all_forwards(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\migrations\executor.py", line 163, in _migrate_all_forwards
state = self.apply_migration(
^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\migrations\executor.py", line 248, in apply_migration
state = migration.apply(state, schema_editor)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\migrations\migration.py",
line 131, in apply
operation.database_forwards(
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\migrations\operations\fields.py", line 108, in database_forwards
schema_editor.add_field(
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\mysql\schema.py", line 105, in add_field
super().add_field(model, field)
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\base\schema.py",
line 641, in add_field
self.execute(sql, params)
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\base\schema.py",
line 192, in execute
cursor.execute(sql, params)
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\utils.py", line 103, in execute
return super().execute(sql, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\utils.py", line 67, in execute
return self._execute_with_wrappers(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\utils.py", line 80, in _execute_with_wrappers
return executor(sql, params, many, context)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\utils.py", line 84, in _execute
with self.db.wrap_database_errors:
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\utils.py", line 91, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\django\db\backends\mysql\base.py", line 75, in execute
return self.cursor.execute(query, args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\MySQLdb\cursors.py", line 179, in execute
res = self._query(mogrified_query)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\Envs\sms\Lib\site-packages\MySQLdb\cursors.py", line 330, in _query
db.query(q)
File "C:\Users\USER\Envs\sms\Lib\site-packages\MySQLdb\connections.py", line 255, in query
_mysql.connection.query(self, query)
django.db.utils.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '[200] DEFAULT () NULL' at line 1")
Please is it a must to use postgreSQL?

This issue has been successfully resolved in PR#22 . The changes made address the bug related to database compatibility in the payments app, allowing for the use of databases other than PostgreSQL without encountering migration errors.
Feel free to review the details


Uncaught promise error

Version of Komada
v0.20.10
Are core files modified?
No.
Describe the problem
Uncaught promise error when trying to send a message in a channel that the bot can see but cannot talk in. This happens with System Commands and custom commands.
Expected Behaviour
The error should be caught or handled in some way.
Actual Behaviour
This Error is given:
Uncaught Promise Error: DiscordAPIError: Missing Permissions     at item.request.gen.end (/root/node_modules/komada/node_modules/discord.js/src/rest/handlers/RequestHandler.js:52:65)     at then (/root/node_modules/komada/node_modules/snekfetch/src/index.js:263:21)     at <anonymous>     at process._tickDomainCallback (internal/process/next_tick.js:228:7)
Steps to Reproduce.

Make a text channel that the bot can read messages, but not send messages.
Use a command in that channel and receive an error in the console.

Another uncaught promise error (dont know how to reproduce this one)
Uncaught Promise Error:   TypeError: Cannot read property 'missing' of null   at Object.exports.run (/komada/src/inhibitors/missingBotPermissions.js:22:88)

First uncaught error can be reproduced.
Have yet to find a way  to reproduce the second error.
@UnseenFaith @kyranet @bdistin
Thoughts?


e2e: serial: avoid cooldown on test skip

regardless of the cooldown time, it doesn't make sense to cooldown if the test skipped for unmet prererquisites, which is actually the only reason why we should skip at all in this suite.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/hold
still testing, looks good so far but not completed yet

/hold cancel


chore: submit coverage to codecov

Enable GH Actions on push
Submit coverage report to codecov
Add Windows to OS tests matrix

Previous build was failing due to a issue with Yarl 1.6.0 as stated at https://github.com/aio-libs/yarl/issues/509.
Newer versions does fix the issue but should take into account any future breaking issue from upstream libraries, maybe use dependabot to handle automatically those checks as well?


Possibility to exclude flaky tests from report

We have a separate workflow for handling flaky tests.
Is it possible to exclude them from failure report?

I needed it as well, so I started working on it : https://github.com/ScaCap/action-surefire-report/pull/238


fix build on metal by returning Device

Fixed the function return type to be a Device on get_device().

Background
With cargo build --release --features metal I was seeing this build error:
error[E0107]: enum takes 2 generic arguments but 1 generic argument was supplied
   --> mistralrs-pyo3/src/lib.rs:50:20
    |
50  | fn get_device() -> Result<Device> {
    |                    ^^^^^^ ------ supplied 1 generic argument
    |                    |
    |                    expected 2 generic arguments
    |
note: enum defined here, with 2 generic parameters: `T`, `E`
   --> /Users/kylekelley/.rustup/toolchains/nightly-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/result.rs:527:10
    |
527 | pub enum Result<T, E> {
    |          ^^^^^^ -  -
help: add missing generic argument
    |
50  | fn get_device() -> Result<Device, E> {
    |                                 +++

I started changing it to a proper Result<Device, E> until I noticed that this function was returning a Device. Builds on MacOS again. 💪

Thanks!


[release-1.11] go dependencies: bump protobuf library

Manual cherrypick required.
#37784 failed to apply on top of branch "release-1.11":
Applying: go dependencies: bump protobuf library
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 go dependencies: bump protobuf library
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

This was merged in https://github.com/istio/istio/pull/37796


Kubernetes service created when statefulset scale from Rancher UI

Rancher Server Setup

Rancher version: 2.5.7

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream): Local

User Information

What is the role of the user logged in? Admin/Cluster

Describe the bug
A kubernetes service is created (with selector label : workload.user.cattle.io/workloadselector=apps.statefulset-*) when i scale up/down my statefulset from the UI "Cluster explorer". The service created have the same name that my statefulset. So, if i have already a service with this name, a pop-pop error displays.
It seems that the service created is related to UI mode, but not en CLI mode with kubectl command.
Is the creation of this service normal? What is the  purpose?

Hi,
Ave you information regarding this use-case? Have you need more information ?
Thanks
Loïc

Hi,
Have you need more information regarding my issue? Is there a link on the rancher doc that mentions this point? Currently,  i didn't find.
Thanks
Loïc


Adding camera bounds cause incorrect bounding box estimation

https://github.com/bwasty/gltf-viewer/blob/847bf5f05af17a4937fff10195fc9c00e58299f5/src/render/node.rs#L109-L113
I stumbled onto this TODO after trying to take a screenshot of a model with a camera, but using bounding box estimation. It seems that the camera bounds are being taken into account when trying to set a nice camera position, causing the bounding box to be incorrectly estimated.
Here is the screenshot produced by gltf-viewer:

And here is the scene view in Houdini, notice the small camera dot in the bottom left:

I'm attempting to get the camera node's bounds to not count in the scene bounds, but my Rust knowledge is very limited. I hacked together this diff that seems to resolve the problem:
diff --git a/src/render/node.rs b/src/render/node.rs
index a1dc13c..80a487f 100644
--- a/src/render/node.rs
+++ b/src/render/node.rs
@@ -106,6 +106,10 @@ impl Node {
             self.bounds = mesh.bounds
                 .transform(&self.final_transform);
         }
+        else if let Some(ref _camera) = self.camera {
+            // Skip updating bounds for Cameras, since they don't have bounds.
+        }
         else if self.children.is_empty() {
             // Cameras (others?) have neither mesh nor children. Their position is the origin
             // TODO!: are there other cases? Do bounds matter for cameras?

Is this the correct solution? Do you have any other ideas about how to fix this?

Looks good - a slight simplification would be else if self.camera.is_some().

awesome. should I make a PR or...?

Yes, that would be great :)

when could I expect this change to make it onto crates.io? I'd love to be able to just cargo install with a version rather than with a git url and sha.

Here it is: https://crates.io/crates/gltf-viewer

wow, thank you for the quick reply and publish! I really appreciate it!


Incorrect Cost shown on Energy Dashboard

Since the latest version of the Octopus Energy integration, the cost is showing as double that actual cost on the Energy Dashboard. The KW/H for electricity and cubic meters for gas is showing as correct but the cost is double
Octopus Energy Integration:

Energy Dashboard:

This is odd and I'm not sure if it's an issue with the energy dashboard or the entity as the entity is showing the correct price. Did you do any home assistant restarts on the day which might have caused home assistant to count the price twice?
Also how is the price calculated on the energy dashboard? I've not seen this and I have the sensor.octopus_energy_electricity_xxx_xxx_previous_accumulative_cost sensor added under the option Use an entity tracking the total costs which I think Home Assistant just reads but does nothing special with.

Yes I did restart home assistant after upgrading the Octopus integration, it is odd that the KW/h valve was correct but the cost has doubled. Since I reported the issue the energy dashboard has been reporting the correct usage and cost so maybe it was some weird glitch, I am using the sensor.octopus_energy_electricity_xxx_xxx_previous_accumulative_cost on the energy dashboard to calculate cost.
From: David Kendall @.>
Sent: 27 January 2023 20:33
To: BottlecapDave/HomeAssistant-OctopusEnergy @.>
Cc: carlchurchman @.>; Author @.>
Subject: Re: [BottlecapDave/HomeAssistant-OctopusEnergy] Incorrect Cost shown on Energy Dashboard (Issue #133)
This is odd and I'm not sure if it's an issue with the energy dashboard or the entity as the entity is showing the correct price. Did you do any home assistant restarts on the day which might have caused home assistant to count the price twice?
Also how is the price calculated on the energy dashboard? I've not seen this and I have the sensor.octopus_energy_electricity_xxx_xxx_previous_accumulative_cost sensor added under the option Use an entity tracking the total costs which I think Home Assistant just reads but does nothing special with.

Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBottlecapDave%2FHomeAssistant-OctopusEnergy%2Fissues%2F133%23issuecomment-1407045398&data=05|01||832faea4042e4bc1f36508db00a5a336|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638104483621762259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=aWG6nPkCpZBdQqjjl8joHDSgD5Fl%2B4pR7wK4RdNzfc0%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASJBXN5WMS47FSV7VZDWZ7TWUQWGRANCNFSM6AAAAAAUGTAHJI&data=05|01||832faea4042e4bc1f36508db00a5a336|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638104483621762259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=YTn6gg%2FEBYhl1CRbqXUBsAYKWY8Iqj30cnaBl7TX9w0%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

This might be a qwerk with the way the energy dashboard works. Upon restarts, I restore the last known state of the sensor.
The calculated price depends on which sensor you add. If you use the current price sensor then it multiplies the energy value by that value, which is not ideal as the data is accumulative and a day old. With the way you've set it up, it was my understanding that it just took that value as is as. But the sensor must be added under the option Use an entity tracking the total costs which is the third one down (from memory).
I'll close this issue, but if you see it again feel free to reopen it


Add support for lualine?

lualine.nvim is a popular neovim status line plugin which has support for various themes, but doesn't really work with oxocarbon. After having used oxocarbon for a few weeks now I can't go back to any other theme so I would love to have oxocarbon as a theme for lualine.
I opened this issue in the original repo too but didn't get a reply, this fork seems like it has more features too! Great work
Looks kind of plain right now

Hey. I can sure do something about it. Can you please post some screenshots of other themes and how they look with lualine? I personally don't use lualine so I want to use what balance of colors looks and works the best. Thanks.

Hi! Thanks for the quick response! Here's how it looked in the my old theme (solarazied dark). It's a bit hard to see you'll have to zoom in

There are some more screenshots on the lualine repo as well.

Thanks. I'll probably do a few different versions, just not now. If I will not respond again in 2 days, please ping me.

Sure thing

Its been 2 days :)

Its been 2 days, just reminding you @B4mbus

@nexxeln Hey. Can you install oxocarbon from the lualine branch, set the theme and tell me how it looks? I don't have lualine set up so I wasn't able see if it even works. Thanks.

With packer that would be
use {
  'B4mbus/oxocarbon-lua.nvim',
  branch = 'lualine'
}

I believe.

Hey! I installed it and used the instructions from the readme to set the global options. However it is expecting a boolean I think instead of a number. Here's the error.

 I pushed new changes, try again, please.

Works now, but its kind of unreadable?

Also doesn't match the theme a whole lot

Sorry if I'm being too demanding 😄

@nexxeln oh I see. You're not too demanding at all, you are the user, you have all the rights to demand :p
I'll install lualine and fiddle around to make something sensible, It will probably all come down to a single theme tho.

That sounds good to me!


Scaling archives: more pages?

Current Behavior
As the gazelle keeps growing and more issues are created, the archives page will have to list a lot more past issues. Right now, the ArchivesController just gets a set number of issues that seems to be a large enough number to not be a problem for a couple more years if the Gazelle continues to publish once a week, but it'd be good to come up with a better long-term solution.

Possible Solution
We could start by fetching in reverse chronological order so that we don't run into the problem we did this semester where recent articles were visibly missing, and then maybe fetching and displaying more dynamically as the user scrolls down? Or perhaps having multiple numbered pages? This would require some front-end changes, and is a design choice.

https://www.thegazelle.org/archives

Related to #131 : reverse chronological order should be prioritized, but pagination for archives, authors, and categories can be done all at once

Thanks for bringing this up!
We definitely need to start fetching in reverse order, regardless of design choices on the archives page. Additionally, I think building a better archives page might be a nice idea as well. For now, I will approve the hacky PR to fix it, but moving further we best redesign the archives page. 50 or so "issues" per page, and an additional section for categories/specials etc would be ideal.
It would be a bit of work but an excellent exercise: could be tackled by a group of people instead of just one developer.


PDFSection - allow PDFSectionColumns to have equal heights

I have a PDFSection with 3 columns. Each PDFSectionColumn contains a PDFTable where the height is dynamic.
Problem: columns have different heights (based on their respective content)
Solution: ability to set config to force each column to have equal height:
e.g.: pdfSection.equalColumnHeights = true
Maybe there is a simpler alternative that I'm missing.
Hard to know what to do since a lot of the docs are missing description, majority of classes just says TODO
overall, amazing library though. Thanks!

Hi @grantespo, thanks for opening up the issue.
About the docs: Yes, you are right, they definitely lack on completeness, due to me working mostly alone on it (except for the amazing contributors)
Is the usage documentation any help?
I like your solution with the equalColumnHeights but it isn't this easy (is it ever? 😄)
How would the content of each section be affected?
When using tables we can increase the padding around cell content and cell borders, but how about all the other data types? Should an image be stretched, etc.?
From a quick look at the problem space, I believe this won't be trivial to implement.


Multiple paginationType

Hi,
I was trying to use multiple pagination types in the same gallery.
In the .js file it says "or":
paginationType: 'bullets', // 'bullets' or 'progress' or 'fraction' or 'custom'
In my project I would like to use 'progress' and 'fraction' together. Is that possible?
Thanks.

Multiple paginations are not supported


chore: Format repo

Format outstanding files & proto definitions.

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

You'll need to make mockery after make format.


update: on ssl-exporter serviceMonitor add default relabelings action.

if relabelings action: replace is ignored, it will be OutOfSync sync status on Argo-CD.
if you have argo-cd alert by application  sync status, it will be firing alerts.

LGTM. Please change the helmchart version to 1.2.1 so the pipeline works.


tests: check for tls events to trigger once per flow

Test for issue https://redmine.openinfosecfoundation.org/issues/1983

Appears to pass now: https://github.com/jasonish/suricata-verify/actions/runs/4963447610

Reabsed here to show that this now passes.

Which certificate is supposed to have an invalid length in this big pcap with many flows ?

I would close this PR as it does not get any anomalies (instead of twice as much as wanted)

Closing this PR, work to be continued in the redmine ticket...


Replace unwrap calls with expect in bevy_sprite crate

Objective

Addresses https://github.com/bevyengine/bevy/issues/3899 for bevy_sprite crate.

Solution

Replaced all unwrap calls with expect calls and added comprehensive error messages when these statements panic.

Feel free to review the error messages and provide suggestions on how they could be made clearer.

Should I use the following pattern (suggested by clippy) on places where I call a format! macro as the argument for the expect call?
foobar.unwrap_or_else(|_| panic!(/* ... */))

Also, I was trying to display HandleIds as part of some errors but noticed it's an enum with tuple variants and it doesn't implement Debug, so any suggestion on how to clarify messages on loops or places where a hint on the entity/handle/etc. could be useful is very welcome.

Should I use the following pattern (suggested by clippy) on places where I call a format! macro as the argument for the expect call?
foobar.unwrap_or_else(|_| panic!(/* ... */))

Please do, otherwise there will be a String allocated even when there isn't an error.

Closing per discussion in #3899 <3


[initial-code] First version

First version of the library. Some things can be improved like:

Get rid of the marker interface
Provide an annotation-based configuration
Using a friendlier interface in MethodChecker

This are not relevant right now and can be addressed in a future version.

I'll add a Tavis file to this PR


Compiling with --no-default-features broken since 1.37.0

Hi,
Prior to 1.37.0 it was possible to compile with --no-default-features to work around #12. However since 1.37.0 compilation with --no-default-features fails with error:
error[E0061]: this function takes 5 arguments but 4 arguments were supplied
  --> /home/ximon/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-deb-1.37.0/src/compress.rs:66:5
   |
66 |     zopfli::compress(&Options::default(), &Format::Gzip, data, &mut compressed)?;
   |     ^^^^^^^^^^^^^^^^ -------------------  -------------  ----  --------------- supplied 4 arguments
   |     |
   |     expected 5 arguments
   |
note: function defined here
  --> /home/ximon/.cargo/registry/src/github.com-1ecc6299db9ec823/zopfli-0.6.0/src/lib.rs:85:8
   |
85 | pub fn compress<R, W>(
   |        ^^^^^^^^

For more information about this error, try `rustc --explain E0061`.
error: could not compile `cargo-deb` due to previous error
error: failed to compile `cargo-deb v1.37.0`, intermediate artifacts can be found at `/tmp/cargo-installFsF2oo`

Fixed


Hiding / Showing Elements

I've found the need to steal the following elements/strategy from bootstrap-sass to mixin to a neat project:
// Visibility utilities
// Note: Deprecated .visible-sm, .visible-md, and .visible-lg as of v3.2.0
@include responsive-invisibility('.visible-sm');
@include responsive-invisibility('.visible-md');
@include responsive-invisibility('.visible-lg');

.visible-sm-block,
.visible-sm-inline,
.visible-sm-inline-block,
.visible-md-block,
.visible-md-inline,
.visible-md-inline-block,
.visible-lg-block,
.visible-lg-inline,
.visible-lg-inline-block {
  display: none !important;
}

@media (max-width: $screen-sm-max) {
  @include responsive-visibility('.visible-sm');
}
.visible-sm-block {
  @media (max-width: $screen-sm-max) {
    display: block !important;
  }
}
.visible-sm-inline {
  @media (max-width: $screen-sm-max) {
    display: inline !important;
  }
}
.visible-sm-inline-block {
  @media (max-width: $screen-sm-max) {
    display: inline-block !important;
  }
}

@media (min-width: $screen-md-min) and (max-width: $screen-md-max) {
  @include responsive-visibility('.visible-md');
}
.visible-md-block {
  @media (min-width: $screen-md-min) and (max-width: $screen-md-max) {
    display: block !important;
  }
}
.visible-md-inline {
  @media (min-width: $screen-md-min) and (max-width: $screen-md-max) {
    display: inline !important;
  }
}
.visible-md-inline-block {
  @media (min-width: $screen-md-min) and (max-width: $screen-md-max) {
    display: inline-block !important;
  }
}

@media (min-width: $screen-lg-min) {
  @include responsive-visibility('.visible-lg');
}
.visible-lg-block {
  @media (min-width: $screen-lg-min) {
    display: block !important;
  }
}
.visible-lg-inline {
  @media (min-width: $screen-lg-min) {
    display: inline !important;
  }
}
.visible-lg-inline-block {
  @media (min-width: $screen-lg-min) {
    display: inline-block !important;
  }
}

@media (max-width: $screen-sm-max) {
  @include responsive-invisibility('.hidden-sm');
}

@media (min-width: $screen-md-min) and (max-width: $screen-md-max) {
  @include responsive-invisibility('.hidden-md');
}

@media (min-width: $screen-lg-min) {
  @include responsive-invisibility('.hidden-lg');
}

Note that I've removed the XS and shifted things to a 3 device strategy for simplicity.
// Small screen / phone
// Should not be used
$screen-sm-min:              480px !default;

// Medium screen / tablet - small desktop
$screen-md-min:              768px !default;

// Large screen / desktop
$screen-lg-min:              1200px !default;

// So media queries don't overlap when required, provide a maximum
$screen-sm-max:              ($screen-md-min - 1) !default;
$screen-md-max:              ($screen-lg-min - 1) !default;

Would something like this be advantageous to including in bourbon?
I'd be happy to submit a PR to tackle this challenge, just would like to discuss various strategies before I start down a single path and make sure that it would be a welcome addition to bourbon.

We typically discourage showing and hiding based simply on viewport size when we can, but it’s a per-project thing.
Bourbon is also a library of pure Sass mixins and functions, so since these are classes, it really doesn’t fit within the scope and purpose of Bourbon. Bootstrap handles things very differently than Bourbon.

Sure, I wasn't talking about using the Bootstrap code as-is, I was more talking about the idea of hiding/showing elements.
What do you encourage use of instead of hiding/showing per viewport size?

You can always build some mixins and use them alongside Bourbon.
It’s best to try to have all elements show across viewports when possible. Since we use Neat as our grid framework, we just use its media queries mixins it hide/show things when needed.

good one, I'd go further and just replace Bourbon with Bootstrap or Foundation


Initial stab at a parser for source code

basic parser for jsx that produces an abstract syntax tree in JSTree format
a single rule that checks the syntax of the defaultMessage fields

uses jsonpath to search the AST for a particular pattern (messages defined within defineMessages())
uses formatjs/intl-messageformat to do the validation

This one depends on i18nlint-common and ilib-lint to go first before the ci/cd will succeed.


First Persian translation for MediaElement

Hey,
I noticed that this great player didn't have a Persian translation yet. So in this pull request, I translated MediaElement to Persian.
Best regards,
WmaTeam

Coverage remained the same at 73.832% when pulling cf4aba4f0023b6640f7d712de9b3b5537c605d4d on wmateam:i18n_fa into 0ed6a821fd6d149265b418700ab93917dbf7dcfc on mediaelement:master.

Thanks for this work. Please remove any changes on the build folder to avoid issues when creating bundles. Also, given that this is translation work, can you take a look at https://github.com/mediaelement/mediaelement-plugins and check the files that are suffixed -i18n.js, please? It will be very helpful to get translation there as well.


Same API called multiple times on easycla corporates landing page & few of them are failed

Summary
Same API called multiple times on easycla corporates landing page & few of them are failed
Background
Steps :

Open corporate cla page link
Login with user : veerendrat
Search & open project : SUN
Open console network tab
Now click on easycla link
Visits each & every graphql request & check there responses

Actual behavior
Same API called multiple times on easycla corporates landing page & few of them are failed

429 error appears for approvedContributorsList api
422 error appears for companyClaManagers api
404 error for claActivityLogs api

Expected behavior
API should call one time on each load without any error
Details

Project Link : https://lfx.dev.platform.linuxfoundation.org/foundation/a09P000000DsCE5IAN/cla
Project Name: SUN
Organization : Microsoft corporation
User : veerendrat

Screenshots

Environment

Environment:

[ ] ALL
[ ] DEV
[ ] STAGING
[ ] PROD

@thakurveerendras I have checked all server side easycla API's, I can't find any server side error.
Thank you.

@umeshlumbhani247 , Issue is still reproducible at my end
Project link : https://lfx.dev.platform.linuxfoundation.org/foundation/a09P000000DsCE5IAN/cla

@nickmango is this still reproducible?


more variations called after two rounds of ont reads polishing

Hello,
Thank you very much for developing such a great polishing tool.
I have used Racon to polish my raw contigs (assembled using raw ont reads) twice with ont reads. Then I called variations for both raw contigs and ont-polished contigs using Illumina reads. I found there are more variations in the polished contigs, although the total variation length is a little smaller. Is this normal?
As follows:
ont-polised: racon two rounds with ont reads;
illumina-polished: pillon three rounds with illumina reads

Thank you very much for your kind help.
Best regards,
Chengcheng

Hi Chengchen,
what is the coverage of your dataset? You used a reference for variation calling or the Illumina reads?
Best regards,
Robert

Hi, Robert,
The coverage of my ont reads is ~66X. I mapped illumina reads to the assembled contigs to call variations with GATK. No reference for variation calling. The coverage of illumina reads is ~80X, which was also used in pilon polishing.
Best regards,
Chengcheng

Can you please check what is the average quality of the ont reads?

We generated these ont reads from 3 flowcells. The mean.q are 9.4, 8.9 and 8.8. I merged these reads together to use.
Best regards,
Chengcheng

There is a tiny chance that this is the issue as Racon employs a quality threshold on windows at 10. Try running one iteration with parameter -q 8 and try calling variants.

Thank you for the suggestion. I will try it.
Best regards,
Chengcheng

Hi, Robert,
I suddenly realize that I used fasta files (both for the sequences and target sequences) for Racon polishing. And the overlaps file is in paf format and was generated by mapping ont reads (also fasta file) to my contigs with minimap2. Will this be a problem? How does Racon obtain quality information in this case?
Best regards,
Chengcheng

The fasta file will not be a problem as Racon does not use qualities in this case. I am not sure why there is a minimal difference in variations. The initial assembly was obtained with which assembler?

I used smartdenovo to assemble raw ont reads. It produced very continuous contigs with contig N50 of 9.2Mb and total contig size of 550Mb. I was very satisfied with these assembly statistics. The contig size was very reasonable. And also complete BUSCO of initial assembly was 86.4%. Racon improved it to 90.6% (round1) and 90.4% (round2).
Best regards,
Chengcheng

Does smartdenovo employ any accuracy boosting during assembly or is the final error equal to the error in raw reads?

I'm not sure about the details of how this assembler works. But from what I read on their github page, https://github.com/ruanjue/smartdenovo/blob/master/README-tools.md the final consensus sequence is more accurate than raw reads, reaching to  99.7%. But they still suggest to use other tools to improve the accuracy.
Best regards,
Chengcheng

Well then I think it is not that surprising that the accuracy changed a little. Maybe you can change different alignment parameters, like 2/-5/-2 or 3/-5/-4. You can also try Racon with Illumina.


Power BI Publisher for excel is no longer available

Why and when was Power BI Publisher for Excel removed?
So, now we have to go to Power BI, pick our report or dataset and then click menu item to Analyse in excel before we can connect excel to a  Power BI Dataset.  Not Great!!!
We are currently using Excel 2016 and this change has a negative impact to our business.
This was much better when we were able to install Power BI Publisher for Excel and then in Excel we had the Power BI Ribbon and were able to easily connect to Power BI Datasets.
Will this feature come back??????

Thanks for your comment @GMAU01,
This looks like product feedback or a product question, rather than documentation feedback. You can submit product feedback or feature ideas by going to Power BI Ideas.


Add multiple roof forecast

I am running a solar installation with opposite orientations, i.e. SE and NW.
Getting proper forecast values is only possible, by fetching the forecasts separately.
I would suggest to add support for multiple (or at least a second) forecast location.
Visualization could stay as is, by simply adding up the forecasted energy values for both locations.

Duplicate of #64, see there for a workaround


swift backend storage error

Using swift backend as storage for registry is failing with following error (registry.log).
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: time="2016-09-12T12:32:49.064356273Z" level=info msg="debug server
listening localhost:5001"
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: panic: Swift authentication failed: Response didn't have storage url and auth token
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]:
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: goroutine 1 [running]:
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: panic(0xd88060, 0xc820011c40)
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: #011/usr/local/go/src/runtime/panic.go:481 +0x3e6
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: github.com/docker/distribution/registry/handlers.NewApp(0x7f1e5ae5
3680, 0xc8203d2300, 0xc820384580, 0x7f1e5ae53680)
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: #011/go/src/github.com/docker/distribution/registry/handlers/app.g
o:121 +0x619
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: github.com/docker/distribution/registry.NewRegistry(0x7f1e5ae536c0
, 0xc8203d2300, 0xc820384580, 0xe, 0x0, 0x0)
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: #011/go/src/github.com/docker/distribution/registry/registry.go:86
+0x2b0
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: github.com/docker/distribution/registry.glob.func1(0x14ccdc0, 0xc8
203bc520, 0x1, 0x1)
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: #011/go/src/github.com/docker/distribution/registry/registry.go:55
+0x2a9
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).execute(0x14ccdc0, 0xc8203bc4d0, 0x1, 0x1, 0x0, 0x0)
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: #011/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:495 +0x6d4
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).Execute(0x14ccf60, 0x0, 0x0)
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: #011/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:560 +0x180
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: main.main()
Sep 12 08:32:49 <IP_ADDRESS> registry[1433]: #011/go/src/github.com/docker/distribution/cmd/registry/main.go:23 +0x23
We looked in the swift logs and there are no authentication errors.

Please see the swift backend configuration.
version: 0.1
log:
level: debug
fields:
service: registry
storage:
cache:
layerinfo: inmemory
swift:
username: admin
password: ********
authurl: http://xxxx.xxxx.xxx:5000/v3
tenant: admin
domain: default
insecureskipverify: true
region: regionOne
container: docker_images
maintenance:
uploadpurging:
enabled: false
delete:
enabled: true
admin account and tenant are available in Openstack keystone.

@biolounge  I use keystone v2, it woks. I am not sure if v3 can wok. This is my config:
version: 0.1
log:
  fields:
    service: registry
storage:
  swift:
    tenant: admin
    username: admin
    password: 5c8d15f732104053
    authurl: http://<IP_ADDRESS>:5000/v2.0
    container: docker_registry
http:
  addr: :5000
  headers:
    X-Content-Type-Options: [nosniff]
health:
  storagedriver:
    enabled: true
    interval: 10s
    threshold: 3

Be sure that the container docker_registry is created before you start registry.

@biolounge for swift v3, the auth URL may look like: https://storage.myprovider.com/v3/auth
For more info, refer to https://docs.docker.com/registry/configuration/

Yes, that solved the issue!


Use new panic-strategy field in custom target?

PR rust-lang/rust#36794 introduced a new panic-strategy field for target JSON files, that allows to set the default panic strategy for the target. We could use it to get rid of the profile options in the Cargo.toml. This would also remove the need for eh_personality and _Unwind_Resume (since the sysroot is then compiled without unwinding support too).
However, we couldn't introduce it before the Returning from Exceptions post, since we're using the default x86_64-unknown-linux-gnu target in the earlier posts.

Fixed in #310


Upgrade to Android plugin 3.x

The Android Gradle plugin needs to be upgraded to last version.
Currently project doesn't build with latest Gradle plugin (see also: https://github.com/libgdx/gdx-pay/issues/180#issuecomment-425677463)
Due to lack of time, I cannot do the upgrade currently. If anyone is willing to take up this task, I will be happy to accept PR.
I started the work here: https://github.com/libgdx/gdx-pay/tree/android-build-tools-3-upgrade, but ./gradlew check fails with lint errors. Not yet dived into details.
Maybe @ProZhar or @MrStahlfelge have some time left ;-)?

libGDX is not compatible with Gradle plugin >= 3
https://github.com/libgdx/libgdx/issues/4698
https://github.com/libgdx/libgdx/issues/5177
We have to stay on 2.x

@keesvandieren I would love to help, but I don’t know well gradle and its plugin :(

4.6 is now supported by 1.9.9 and 1.9.8

PR is made, but it has lint problems: #185

I was able to manage the lint problem, it was caused by the gdx-pay-android project not being an actual Android project. Next problem was with the unmock library, changed to the latest version fixed it.
Now the build fails on signing the test project. I tried a lot of different Travis commands but no success.

It is building :)

@keesvandieren Because we update from 1.9.6 to 1.9.8, I would suggest to release 11.4 before merging this to the master branch.


x/tools/gopls: codeaction taking ~6 seconds for no apparent reason

What version of Go are you using (go version)?

$ go version
go version devel +73d213708e Sat Jan 25 16:34:18 2020 +0000 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20200124220429-8fe064f891f2
$ go list -m golang.org/x/tools/gopls
golang.org/x/tools/gopls v0.1.8-0.20200124220429-8fe064f891f2

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/myitcv/.cache/go-build"
GOENV="/home/myitcv/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myitcv/gostuff"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/myitcv/gos"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/myitcv/.vim/plugged/govim/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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build563121321=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Per the following gopls log file: gopls_20200126_1322_54_956033106.log, a CodeAction call took ~6.3 secs when there was no apparent reason for the delay.
[Trace - 13:26:53.641 PM] Sending request 'textDocument/codeAction - (2)'.
Params: {"textDocument":{"uri":"file:///home/myitcv/gostuff/src/myitcv.io/cmd/gitbranchgraph/main.go"},"range":{"start":{"line":0,"character":0},"end":{"line":0,"character":0}},"context":{"diagnostics":null}}

[Trace - 13:27:00.029 PM] Received response 'textDocument/codeAction - (2)' in 6388ms.
Result: {}

As you can see the preceding change was not very interesting:
[Trace - 13:26:52.001 PM] Sending notification 'textDocument/didChange'.
Params: {"textDocument":{"version":48,"uri":"file:///home/myitcv/gostuff/src/myitcv.io/cmd/gitbranchgraph/main.go"},"contentChanges":[{"range":{"start":{"line":45,"character":0},"end":{"line":46,"character":0}},"text":"\toriginsToLocals := make(map[string]bool)\n"}]}

What did you expect to see?
Near instant response.
What did you see instead?
~6.3 sec delay.
Tentatively marking as v0.3.0

cc @stamblerre @heschik
FYI @leitzler

I'm going to close this issue since it doesn't seem to be reproducible. Please open a new issue with a repro case if this comes up again.


Migrated to null safety and made another branch

My suggestions in graphx_widget.dart - > SceneBuilderWidget
 final SceneController Function() builder;
...
required this.builder,
...
late SceneController _controller;
...
_controller = widget.builder();
'

Excuse me. I still don't know how to pull.

My suggestions in render.dart - > graphics
final points = List.filled(sides, null);   = >     final points = List.filled(sides, Offset(0, 0));
NOTICE: This constructor cannot be used in null-safe code.
/// Use [List.filled] to create a non-empty list.

@MarceloRab I fixed what you suggested.

FIx - core > scene_controller
f ((_config.useKeyboard ?? false) || (_config.usePointer ?? false)) {
I don't know why it is generating an error. Would it be something on nullsafety?

FIx - core > scene_controller
f ((_config.useKeyboard ?? false) || (_config.usePointer ?? false)) {
I don't know why it is generating an error. Would it be something on nullsafety?
Can you say what error you are getting?


Enhancement Request: Improved Crop Experience of Resizing Crop Region of Zoomed-In Image

Some image editing apps have a particular UX when it comes to resizing the crop region of a zoomed-in image.
Crop resizing UX typically involves adjusting the crop frame from one side along an axis or a corner point that will potentially expand/contract along two axes. If expanding, the expansion of the crop frame will continue until it meets the edge of the image. This is how Mantis currently functions for an image that is fully visible on screen along the axis being expanded (assuming the mask is turned off).
But if the image is zoomed-in and a portion of the image is off-screen in the direction of the crop frame expansion, then some adjustments will need to be made to the zoomScale and contentOffset of the scrollView to animate the image back in to view until an edge of the image along the expansion axis is met. In Freeform (unlocked) aspect ratio mode, this also causes the opposite axis of the crop frame to shrink in the simple case that expansion occurs along a single axis (this is to give the appearance that the crop frame is elongating along the expanding axis). This is an important UX enhancement that would greatly improve Mantis.
To complicate this experience, Catalyst UX should be different than iOS. Catalyst should hide the toolbar and use the entire View to resize the crop frame in the direction of the expansion. Typically on an iOS device, there are controls displayed on screen along with the grid control. In this case, the grid control should have a maximum size that is inset from any controls or tool bar that remain visible on screen during a resize operation. Currently, Mantis allows expansion below the toolbar which is an awkward experience.

Here is a video showing enlarging along x axis to the left of zoomed in image:
https://github.com/guoyingtao/Mantis/assets/5288729/7b2e070e-a51c-486c-97e9-679408e0fa64


Creating new user with special character in his name gives invalid error message

When you create user with special character in its name. for eg schrödinger
the error message is invalid
actual behavior

it gives error message

preferred_name 'schrödinger' must be at least the local part of an email

❯ curl -s -k -X POST https://localhost:9200/ocs/v1.php/cloud/users -H "OCS-APIREQUEST:true" -d username=schrödinger -d userid=schrödinger -d<EMAIL_ADDRESS>-u admin:admin | xmllint --format -
<?xml version="1.0" encoding="UTF-8"?>
<ocs>
  <meta>
    <status>error</status>
    <statuscode>400</statuscode>
    <message>preferred_name 'schrödinger' must be at least the local part of an email</message>
  </meta>
</ocs>

expected behavior
The user creation should be successful or it should give proper error message
eg.
preferred_name 'schrödinger' contains invalid characters

In graph API
curl -k -XPOST -uadmin:admin -H "Content-Type: application/json"  -d '{"displayName": "SpecialUser","mail": "usrmail@oc.com.np","onPremisesSamAccountName": "@-_.","passwordProfile": {"password": "%regular%"}}' https://localhost:9200/graph/v1.0/users -v | jq

* upload completely sent off: 138 out of 138 bytes
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [130 bytes data]
* Mark bundle as not supporting multiuse
< HTTP/1.1 400 Bad Request
< Content-Length: 204
< Content-Type: application/json; charset=utf-8
< Date: Thu, 04 Aug 2022 07:38:54 GMT
< X-Graph-Version: 2.0.0-beta.5+8d97b7e1a
<
{ [204 bytes data]
100   342  100   204  100   138   3238   2190 --:--:-- --:--:-- --:--:--  5428
* Connection #0 to host localhost left intact
{
  "error": {
    "code": "invalidRequest",
    "innererror": {
      "date": "2022-08-04T07:38:54Z",
      "request-id": "anu-OptiPlex-3050/Ts01Gjj6uE-012724"
    },
    "message": "username<EMAIL_ADDRESS>must be at least the local part of an email"
  }
}

@dpakach this is an old issue that was transferred from the archived ocis-ocs repo a few weeks ago.
Please close if no longer relevant.
I don't see any entry in expected-failures for this. Is it still an issue?

Actual: we use graph api. message if onPremisesSamAccountName: "schrödinger" is 400 with "message": "Invalid username"


Morphology causing spurious distinctions between items?

The commodity ID module finds pairs of commodities like {gisz}RU and {gisz}RU-ur-ka. Are these the same thing with different morphology? If so, is there reliable morphological parsing for Sumerian to help identify these as the same object?

This may be useful: https://github.com/cdli-gh/morphology-pre-annotation-tool


Fix model loading issue and improve inference feedback to user

Pull request fixes #3 and implements the improvement suggestion therein.

Thanks for the adjustments. I will merge this PR.


Add iterable table support in a slightly different way

This is an alternative to #1. Relative to #1 this PR here is at the same time more and less intrusive: here I slightly modify the Result type by adding a type parameter and then I'm implementing the standard julia iterator interface directly on the Result type. In that sense it is more intrusive than #1 because it modifies the type you defined a little bit. It is less intrusive because with that you don't need to take any dependency on IteratorInterfaceExtensions.jl and TableTraits.jl, and yet you still are fully integrated into the iterable tables ecosystem.
This one also enables the following nice syntax:
for row in execute(conn, "SELECT typname FROM pg_type WHERE oid = 16")
    println(row.typname)
end

and all the other great things you can do with iterators (think generators, list comprehensions etc.).
If you wanted to merge this one here, we should probably squash it first.

Thanks for the help! I think I'd like to do this with the new Data.rows from DataStreams. Do you think that would be feasible? That way we wouldn't have to edit Result or add in IterableTables interface packages.

I don't know. The whole DataStreams/Missings/DataFrames world is such a moving target right now that it is a bit tricky to say.
Just relying on Data.rows won't work for missing data, though. The iterable tables world uses DataValue, so an iterator that produces named tuples that have Union{T,Missing} values won't interop. I assume that is what Data.rows would do, right?
Note though that you don't have to take a dependency on IterableTables.jl in either of the two ways to implement this. The version in #1 takes a dependency on IteratorInterfaceExtensions.jl and TableTraits.jl, which are both very, very minimalistic packages. I also don't expect any changes for either of them, so they should be very stable at this point (they are new packages, but the overall design has been stable for more than a year without any change).

Just relying on Data.rows won't work for missing data, though. The iterable tables world uses DataValue, so an iterator that produces named tuples that have Union{T,Missing} values won't interop. I assume that is what Data.rows would do, right?

Ah okay. I think you might be able to convert the types with the transforms kwarg but I'll have to look into it. In the meantime I'll close this PR as the first one is closer to what I'd like and I'm going to put this off until after the first release (coming soon).

Note though that you don't have to take a dependency on IterableTables.jl in either of the two ways to implement this. The version in #1 takes a dependency on IteratorInterfaceExtensions.jl and TableTraits.jl, which are both very, very minimalistic packages. I also don't expect any changes for either of them, so they should be very stable at this point (they are new packages, but the overall design has been stable for more than a year without any change).

I'm not worried about the dependencies, more about implementing schema (column typing, etc.) stuff in a couple different places, which is why I'd like to find a way to implement IterableTables support wrapping the DataStreams constructs if possible.


[SPARK-13471] [SQL] Update hive groovy dependency to 2.4.4; bump artifact to <IP_ADDRESS>-spark

This updates the org.spark-project.hive artifact to <IP_ADDRESS>-spark and increases the groovy version to 2.4.4, so ensuring that CVE-2015-3253 doesn't get passed downstream.

closing as I'm proposing fix it in the POMs;


Scrolling text support / DrawText length > 14

Continuation of https://github.com/alexeden/rpi-led-matrix/issues/24
Re-implement DrawText using hzeller DrawGlyph method instead of DrawText.  Should help to fix garbled/Unicode text being written to screen.
Need to extend alexeden's library to add DrawGlyph method from hzeller.  Consider creating a PR into alexeden/rpi-led-matrix when changes are done if it's helpful.

I don't think the issue is with Unicode perse. The same issue happens if you use regular characters of length greater than 16. The reason you're seeing it with shorter strings that include Unicode is that those characters are more than a single byte. What I think happens is the underlying library statically allocates a buffer based on some maximum number of regular characters for the screen. When your string exceeds that, you get a buffer overflow, which corrupts the data.

I don't think the issue is with Unicode perse. The same issue happens if you use regular characters of length greater than 16. The reason you're seeing it with shorter strings that include Unicode is that those characters are more than a single byte. What I think happens is the underlying library statically allocates a buffer based on some maximum number of regular characters for the screen. When your string exceeds that, you get a buffer overflow, which corrupts the data.

I see what you mean, @konstk1.  I think changing that in hzeller's code might be a bit beyond me.  It would probably be the correct fix.
@samturner3, I tweaked my library without touching the alexeden's repo or my fork of it.  Now it iterates through the characters in the string and writes them separately.  It seems to be working!  I double checked the spacing of characters and I that should be the same as before as well.
Try cloning the latest version from wesleytabaka/rpi-led-matrix-painter-example and let me know what you think.  That's commit  683f4b91057d9de412e917a0aaab807c75d59e6e
Thanks!

@wesleytabaka I'm now getting this error when installing
pi@rpiWallClock:~/rpi-led-matrix-painter-example $ npm i

><EMAIL_ADDRESS>postinstall /home/pi/rpi-led-matrix-painter-example
> npm run build

><EMAIL_ADDRESS>build /home/pi/rpi-led-matrix-painter-example
> cd ./src/ && tsc

index.ts:1:24 - error TS2307: Cannot find module 'rpi-led-matrix-painter' or its corresponding type declarations.

1 import * as Board from "rpi-led-matrix-painter";
                         ~~~~~~~~~~~~~~~~~~~~~~~~

index.ts:2:37 - error TS2307: Cannot find module 'rpi-led-matrix-painter' or its corresponding type declarations.

2 import { PaintingInstruction } from "rpi-led-matrix-painter";
                                      ~~~~~~~~~~~~~~~~~~~~~~~~

Found 2 errors.

Package.json:
  "dependencies": {
    "rpi-led-matrix-painter": "^1.1.4"
  },

PS want to communicate on this over some kind of chat app?

@samturner3 It look like you might need to run npm install and then npm run build.
Sure we can chat if you'd like.  What are you on?  I can send a send a Zoom link and we can chat there.

@samturner3 It look like you might need to run npm install and then npm run build.
Sure we can chat if you'd like. What are you on? I can send a send a Zoom link and we can chat there.

Yep ran npm i and build. Sure send over the link

Here's my Zoom link: https://wesleytabaka.com/zoom

@samturner3 , based on our discussion and the results yesterday I'm going to close this issue.
I'll also create a new one for the unhandledPromiseRejection warning and the error itself when trying to create a canvas outside the bounds of the LED board.
Thanks!


Is it possible to read environment variables from outside the yml file?

Hi and thanks for this library. I'm very interested but I have a need which I didn't see in the documentation.
I prefer not to commit my environment variables to the git repo and read them from a .env on the production machine. Would it be possible to read the environment from a file?

Hi @n4cr !
Procsd ENV variables (inside procsd.yml file) should store only production-mode specific variables required for your application, like for example HOST, PORT, etc.
All other sensitive data you should go inside .env file and it could be read by your application itself. For example for Ruby there is https://github.com/bkeepers/dotenv , for Python https://github.com/theskumar/python-dotenv and so on.
Once again, inside procsd.yml you should store variables which are only production mode specific. Everything else put inside .env file and read it from your application.

But, if you still want it, you can :)
Your .env file should be located in the same folder with procsd.yml. To use env variables from .env file inside procsd.yml use following syntax:
# .env

SOME_API_KEY="234rsfsdfw423rfes"

# procsd.yml

app: sample_app
environment:
  API_KEY: <%= ENV['SOME_API_KEY'] %>

Thanks @vifreefly for the response. The reason I asked for this was because foreman exports the .env into the Service file so then it is accessible through reading them from the environment variables. But I guess your point to read them directly from .env file stands. As well as your solution.
Great work. I'm investigating procsd and probably start using it.


Editor GPU: Support inline decorations that change only text color (eg. bracket pair colorization)

This change adds support for rendering some inline decorations on the GPU, specifically those that only change the color style. This is done for each inline decoration by walking the stylesheet tree to find relevant styles, parsing them and applying the result to the glyph metadata.
See no yellow bar on the left, meaning they're all GPU lines:

Supporting all of CSS is obviously out of scope, but I think we could support the vast majority of decorations by supporting a small selection of styles like color, background-color, background, font-style, text-decoration-*, etc. most of which are easy to actually render once we get the data to the rasterizer.
Part of #227095
Fixes #233989
TODO follow ups deferred:

https://github.com/microsoft/vscode/issues/234432
https://github.com/microsoft/vscode/issues/234433

Fix it .


Potential Contribution for Issue #496

Issue #496
Hello everyone!
Full Disclosure: I'm a second-year CS undergrad who is extremely new to open-source software development, but I've really been wanting to get involved with it for some time, so being a fan of MS, I hoped I might be found to be of even a little use here.
Looking in the issues list, I noticed one (#496) mentioning a problem with the project template not generating a proper, unique default project name for each subsequent project creation of the type "From Existing Code".
My experience with this software's code is extremely limited, but looking through MSDN's documentation for *.vstemplate files, as well as comparing the template code for the aforementioned type with that of other types - such as NodeJS WebApp - I've noticed that the  tag used in the bugged project type differs from the name of the target file checked within the  tags, unlike with other project types. In an effort to possibly fix this, I've changed the  tag to "FromExistingCode" to match the name of the target file ("FromExistingCode.njsproj").
While I'm aware that I should be testing this on my end, I'm afraid that even after pulling an all-nighter trying to get the cloned builds working on my system, I still seem to be getting about 9 build errors out of 27 total builds, mostly because of some "TestUtilities.UI.dll" files it appears. If anyone could try to splice the content of this commit into their own working build to possibly test at their convenience, I would be extremely appreciative to hear of their results and feedback. Again, I do apologize if I'm coming off as rude, burdensome, or hindering with regards to this project's workflow - I'm just trying to dip my toes into open-source contributing in any way I can, and your time and feedback is greatly appreciated in helping me become a better software developer for the future!
Best Regards,
Austin Hull, Drexel University, Philadelphia

Hi @AustinHull, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, MSBOT;

Thanks for the contribution!
However it looks like you forked the lightweight-install branch and built on that. That's why it says this PR shows 62 changed files. The lightweight installer work is still ongoing and being actively worked on with #1139, and we do not want to take it in just yet.
Instead, create a new branch off master for your pull request, apply your fix, and submit that instead. The commands to do this would look something like:
# Create new branch from master
git checkout -b fix-for-496   master

# Apply your change to the new branch
git cherry-pick 3f03b1d

Regarding getting a build for testing, were you following our build instructions. Was anything unclear in these instructions or could they be improved? What are the errors you are currently seeing?
If you need to, you can always grab a build from AppVeyor as well under the artifacts tab. Here's the example build from your contribution: https://ci.appveyor.com/project/mousetraps/nodejstools/build/1.0.748/job/yvdk5yie2awfu33s/artifacts
Being able to test locally would be much faster however, so let's see if we can get you started with that.

Hello mjbvz, thank you for all the helpful advice and feedback, I really appreciate it!
I'm working on porting my commit to a new branch now, just as you've said, but I do seem to still be rather confused on how the testing of this project works, considering it's a VS extension. I downloaded the AppVeyor build, but I'm not too sure where I'm supposed to put it in order to test my results. I've managed to startup the Experimental Instance of VS via the dev console, but that's about as far as I could get from the documentation provided.
As for getting the build to run locally, I have tried my best to follow the build instructions posted, but I'm wondering if my issues may be stemming from Part 2 of that process. No matter what I do to try and elevate cmd.exe to admin access, I can never seem to execute the *.ps1 file for environment setup (the prompt keeps telling me - despite my admin privileges.  that I do not have permission to access the file), so I attempted to follow the manual alternative, running the registry file to enable the verification skip, and placing the .target file in the specified VS folders (I seem to have three different version folders within my VisualStudio directory).
Thank you again!

Using the appveyor build, you should just be able to run the installer msi. Again, this is an unsigned build and installing this way is not recommended, but it should work.
Can you also copy paste the error you are seeing to provide some more context so we can diagnose the problem. Thanks.

Oh, of course, thank you! The errors I seem to be getting while building NodejsTools.sln are:
3>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
3>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
5>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
11>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
11>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
8>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
9>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
9>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
14>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
14>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
I haven't deleted any files from the project, so I'm not sure why these files aren't being found, but I don't have as much experience with DLLs as I would prefer to have, so maybe I made a simple setup mistake? Thank you again for all your help!

On installing the AppVeyor build, I've noticed that my change hasn't solved the problem, BUT I have noticed that properly functioning project templates seem to each create a folder dedicated to each project within VS's Projects folder, whereas the FromExistingCode project template does not. Perhaps I can look into this as a possible cause.

@AustinHull For the build, are you running the commands from a vs developer command prompt? Can you share the output from running these commands:
msbuild /version

and
where msbuild

Do any of the referenced files from the error exist? It may be helpful if you could share the entire output from running msbuild, starting with the msbuild command itself.

As for the fix, I'm actually not sure of what the root cause of the problem is, so identifying what is different between this template and the other templates sounds like a great starting point. Keep in mind that Vs does cache templates, which can cause problems while testing, so make sure you run devenv /setup or devenv /InstallVSTemplates after installing anew build.
It'd be best if you can get building NTVS in VS directly since that allows testing changes much more quickly. What errors were you seeing that prevented that from working?

@mjbvz Alright, heres the output from the command prompt:
C:\Program Files (x86)\Microsoft Visual Studio 14.0>msbuild /version
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.
14.0.25420.1
C:\Program Files (x86)\Microsoft Visual Studio 14.0>where msbuild
C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
Additionally, the entire Build Log is comprised of the following:
Error occurred while restoring NuGet packages: An error occurred while reading file 'C:\Users\austi_000\Documents\nodejstools\Nodejs\Tests\NpmTests\packages.config': There are duplicate packages: Newtonsoft.Json
1>------ Build started: Project: Nodejs, Configuration: Debug x86 ------
2>------ Build started: Project: TestUtilities.UI, Configuration: Debug x86 ------
2>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudioTools.VSTestHost.14.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
2>C:\Users\austi_000\Documents\nodejstools\Common\Tests\Utilities.UI\UI\AutomationWrapper.cs(21,35,21,45): error CS0234: The type or namespace name 'VSTestHost' does not exist in the namespace 'Microsoft.VisualStudioTools' (are you missing an assembly reference?)
2>C:\Users\austi_000\Documents\nodejstools\Common\Tests\Utilities.UI\UI\EditorWindow.cs(32,35,32,45): error CS0234: The type or namespace name 'VSTestHost' does not exist in the namespace 'Microsoft.VisualStudioTools' (are you missing an assembly reference?)
2>C:\Users\austi_000\Documents\nodejstools\Common\Tests\Utilities.UI\UI\TestExtensions.cs(24,35,24,45): error CS0234: The type or namespace name 'VSTestHost' does not exist in the namespace 'Microsoft.VisualStudioTools' (are you missing an assembly reference?)
2>C:\Users\austi_000\Documents\nodejstools\Common\Tests\Utilities.UI\UI\VisualStudioApp.cs(29,35,29,45): error CS0234: The type or namespace name 'VSTestHost' does not exist in the namespace 'Microsoft.VisualStudioTools' (are you missing an assembly reference?)
2>C:\Users\austi_000\Documents\nodejstools\Common\Tests\Utilities.UI\UI\VisualStudioInstance.cs(25,35,25,45): error CS0234: The type or namespace name 'VSTestHost' does not exist in the namespace 'Microsoft.VisualStudioTools' (are you missing an assembly reference?)
3>------ Build started: Project: TestUtilities.UI.Nodejs, Configuration: Debug x86 ------
4>------ Build started: Project: SharedProjectTests, Configuration: Debug Any CPU ------
3>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudioTools.VSTestHost.14.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
3>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
4>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudioTools.VSTestHost.14.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
4>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
4>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
1>  Restoring NuGet packages...
1>  To prevent NuGet from downloading packages during build, open the Visual Studio Options dialog, click on the Package Manager node and uncheck 'Allow NuGet to download missing packages'.
1>  All packages listed in packages.config are already installed.
1>  Nodejs -> C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\CloudService.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\TypeScriptAzureExpressWebRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\TypeScriptAzureNodejsWorkerRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\TypeScriptAzureWebRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\Express4App.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AzureExpress4App.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AddWebSiteExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AddWebSiteAzureExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\NodejsWebApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AddWebSiteAzureNodejsApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AddWebSiteNodejsWebApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AzureNodejsApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\NodejsConsoleApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\FromExistingCode.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AddWebSiteAzureStarterExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AddWebSiteStarterExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AzureStarterExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\StarterExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\JavaScript\Node.js\1033\AzureNodejsWorker.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptConsoleApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptWebApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptStarterExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptAzureStarterExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptAzureWebApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptAzureExpressApp.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptFromExistingCode.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ProjectTemplates\TypeScript\Node.js\1033\TypeScriptAzureNodejsWorker.zip
1>  Nodejs -> C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\JavaScript\TapeUnitTest.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\JavaScript\TypeScriptTapeUnitTest.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\JavaScript\MochaUnitTest.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\JavaScript\TypeScriptMochaUnitTest.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\JavaScript\UnitTest.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\JavaScript\TypeScriptUnitTest.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\JavaScript\DockerfileTemplate.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\CloudService\NETFramework4\Web Role\Node.js\CloudServiceWebRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\CloudService\NETFramework4\Web Role\Node.js\CloudServiceTypeScriptWebRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\CloudService\NETFramework4\Web Role\Node.js\CloudServiceExpressWebRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\CloudService\NETFramework4\Web Role\Node.js\CloudServiceTypeScriptExpressWebRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\CloudService\NETFramework4\Worker Role\Node.js\CloudServiceTypeScriptWorkerRole.zip;C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\ItemTemplates\CloudService\NETFramework4\Worker Role\Node.js\CloudServiceWorkerRole.zip
1>  Nodejs -> C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Nodejs\Microsoft.NodejsTools.dll
1>          1 file(s) copied.
5>------ Build started: Project: Profiling, Configuration: Debug x86 ------
6>------ Build started: Project: NodejsTests, Configuration: Debug x86 ------
7>------ Build started: Project: Nodejs.Tests.UI, Configuration: Debug x86 ------
8>------ Build started: Project: AzurePublishing.Tests.UI, Configuration: Debug x86 ------
7>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudioTools.VSTestHost.14.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
7>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
7>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
8>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudioTools.VSTestHost.14.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
8>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
8>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
6>  Restoring NuGet packages...
6>  To prevent NuGet from downloading packages during build, open the Visual Studio Options dialog, click on the Package Manager node and uncheck 'Allow NuGet to download missing packages'.
6>  All packages listed in packages.config are already installed.
6>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
5>  Profiling ->
5>  Profiling ->
5>  Profiling -> C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Binaries\Profiling\Microsoft.NodejsTools.Profiling.dll
5>  Creating intermediate PkgDef file.
9>------ Build started: Project: ProfilerTests, Configuration: Debug x86 ------
10>------ Build started: Project: ProfilerUITests, Configuration: Debug x86 ------
10>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudioTools.VSTestHost.14.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
10>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.dll' could not be found
10>CSC : error CS0006: Metadata file 'C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\TestUtilities.UI.Nodejs.dll' could not be found
9>  ProfilerTests -> C:\Users\austi_000\Documents\nodejstools\BuildOutput\Debug14.0\Tests\ProfilerTests.dll
========== Build: 3 succeeded, 7 failed, 17 up-to-date, 0 skipped ==========
When checking for the files being referenced in the errors, I seem to find almost-matching files, except for some reason they seem to be  missing the .UI. portion of their file names. I'll instead find a file named "TestUtilities.Nodejs.dll", for example.
Thanks!

The initial error seems to be:
2>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudioTools.VSTestHost.14.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

Did you run the EnvironmentSetup.ps1 -vstarget "15.0 script? This should install the vstest host assemblies. You can also manually run the msi found in: nodejstools / Common / Tests / Prerequisites / VSTestHost.msi.

Those errors are in the test projects thought and shouldn't prevent you from building and running NTVS itself through visual studio. Is anything blocking you from doing that currently?

Ah, looks like executing the VSTestHost.msi installer did the trick! My builds are now yielding 27 successes with 0 failures. Thank you again for taking the time to walk me through that, I greatly appreciated it! Now I'm presuming I can run this build by switching the solution to Release mode, building that, and then running a sort of installer just like I did through the build yielded by AppVeyor?

Good to hear that worked.
You should be able to build, launch, and debug NTVS all from within Visual Studio itself. In the nodejstools solution, make sure to set NodeJs as your startup project in VS ( https://msdn.microsoft.com/en-us/library/a1awth7y.aspx?f=255&MSPPError=-2147217396 ) by right clocking on the NodeJs project node and selecting "set as startup project". Then simply hit debug and VS will build NTVS and install in in an experimental Visual Studio Instance that you can debug.
Let me know if that works.

Yes, it seems to be working for me now, thank you!
I've also managed to determine, by manually creating a "FromExistingCode1" folder in the Projects directory, the wizard will then appropriately set the default name for the subsequent project as "FromExistingCode2". Unfortunately, even setting the  tag of the FromExistingCode.vstemplate file doesn't seem to automatically create the project folder as I was hoping, so I'm going to have to look into that further.
Thank you again for all the help! I suppose you could close this PR if you'd like, since I'm still in the process of looking for a solution.

Ok, I'm going to close this issue since, as I mentioned, you should start working off of the master branch instead of the lightweight install branch.
I recommend started with at NewProjectFromExistingWizard and ImportWizardCommand to debug new project creation. Let me know if you are blocked by anything or could use any additional pointers.


SubscriptionPrice is missing fields

Describe the bug
Fields in the API: https://developer.paddle.com/api-reference/subscriptions/list-subscriptions (see in the example under the items[0].price)
Fields in the SDK: https://github.com/PaddleHQ/paddle-python-sdk/blob/v0.1.3/paddle_billing/Entities/Subscriptions/SubscriptionPrice.py
Missing fields:

type
name
unit_price_overrides
custom_data
status
quantity {minimum, maximum}

In my case I need minimum and maximum quantity that are returned by the API but not by the SDK
Steps to reproduce
If you call paddle.subscriptions.list() using the paddle-python-sdk it returns half of the price fields comparing to performing the API request directly
Expected behavior
I expect minimum and maximum quantity for the price to be returned
Code snippets
No response
Python version
3.11
SDK version
1.0.3
API version
1
Additional context
No response

Also, there are two classes: paddle_billing.Entities.Price and paddle_billing.Entities.Subscriptions.SubscriptionPrice and the first one has all the fields but the second one is truncated, I do not understand why, the API returns all price fields for the items when you get or list subscriptions

Hi @marinaglancy ... this issue was closed slightly prematurely as the fix was merged into main. We've now released this in v0.2.0 👍


Store GW: Stream chunk fetching; Reduce memory used per query.

Following @pracucci idea from last Thanos Community Sync in order to reduce and predict better memory usage of Thanos Store Gateway per query.
The idea is to move Block index lookup to a separate, first stage and do it concurrently for all blocks that potentially can match the query. We pack all in some kind of merge sort series set.
Then we can have a defined number of workers that get series IDs and fetches chunks for them send to stream (in the right order).
This way we can highly control the overall resources per requests used. This is even more important because we overfetch chunk bytes from object storage to avoid API rate limits. Holding those bytes as short as possible and only for few series / blocks, make a lot of sense. (:
Help wanted, whoever have time first. It's big refactor.

Some comments we made on code while 1:1 to @yeya24

@bwplotka @yeya24 I think we're missing the content of the comments? Could you please check the link again?

Just click the link and scroll down you see comments in the code added

@yeya24 is on it :hugs:

Still very viable

There is a huge optimization possibility here (https://github.com/thanos-io/thanos/pull/4271).

The problem here is that we do sorting before sending so it's much harder than it seems :/

@fpetkovski isn't this something similar to what you have implemented with block series client?

Yes, we already do something like this. Chunks are fetched in batches and sent via gRPC. What we could improve on is to add some pooling so that bytes for sent chunks get recycled. I am not sure how this would work with the async nature of gRPC though, maybe we should move to planetscale/vtproto first?

That wouldn't help as it is a problem with grpc-go itself. Maybe that could be a point in favor of switching to something like https://github.com/storj/drpc. But that's a totally separate thing so maybe we can close this?

From what I understand, Mimir does some pooling in store gateway, but I don't know the exact details: https://grafana.com/blog/2023/07/06/breaking-the-memory-barrier-how-grafana-mimirs-store-gateway-overcame-out-of-memory-errors.
I agree it can be treated as a separate issue though.


Global CustomConverters no longer working

I'm using the converter mentioned in https://github.com/simple-odata-client/Simple.OData.Client/issues/158#issuecomment-242160215. After updating to 5.6.2 (from 5.5.0) I replaced CustomConverters.RegisterTypeConverter by CustomConverters.Global.RegisterTypeConverter but I keep getting a ConstructorNotFoundException. As far as I can see the global TypeCache is not used anywhere and the Session TypeCache does not contain my custom converter.
Is there anything I may have missed or some kind of workaround besides registering the converter in each setting?

@phatcher Do you have some input on this one?

@zivillian You don't need to register it for every setting, just at start up as the values stored against the ITypeCache per-url.
Something like this in your application startup
var settings = new ODataClientSettings
               {
                  BaseUri = "https//foo.com/odata"
               };

settings.TypeCache.Converter.RegisterTypeConverter(typeof(ClassType), ClassTypeConverter.Convert);

There are some TypeConverter tests in my last commit which I'd thought I'd pushed a while go, but they are now on my v5 branch.
The open question is whether we should retain a global custom converters collection and then copy onto each endpoints copy and if so when in the lifecycle should this happen and how do we then override it on a per-settings basis.

@zivillian Do you have any input on this one

I'm currently registering the TypeConverter in each setting and haven't looked into this again. If there is no need for a global TypeConverter I'd favor removing the property.


retry v5 install

not the most sophisticated retry logic, but should solve simple dns problems

@dickeyxxx lgtm


Install pre-release of pytest 3.0

Don't merge this please 😄
Let's see if pytest 3.0 behaves as expected 😂

Current coverage is 100% (diff: 100%)

Merging #796 into master will not change coverage

@@           master   #796   diff @@
====================================
  Files          15     15
  Lines         601    601
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          601    601
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update ad872a0...0d53b45

https://pypi.python.org/pypi/pytest/3.0.0


feat: add Pairing precompile

Before closing issue ensure we have a constraint count + a matching test with the exact interface.

Have test using test engine. Not integrated yet.