[ERROR] Error: ER_PARSE_ERROR

Hello together,
using db-migrate gte 0.9 I get the following error:
[ERROR] Error: ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CREATE TABLE token (
token VARCHAR(200) NOT NULL,
license_id CHAR(36) NOT NU' at line 9
Its working on the development system but not on the server. I have no clue, what the reason could be. The mysql version is the same (5.6). Here the migration script:
CREATE TABLE license (
license_id CHAR(36) PRIMARY KEY,
customer_id CHAR(36),
xml TEXT NOT NULL,
is_blocked BOOL NOT NULL DEFAULT FALSE,
blocking_reason VARCHAR(1000)
);
CREATE TABLE token (
token VARCHAR(200) NOT NULL,
license_id CHAR(36) NOT NULL,
created_on DATETIME NOT NULL,
usages INT NOT NULL DEFAULT 0,
PRIMARY KEY (token, license_id),
CONSTRAINT fk_token_license FOREIGN KEY (license_id) REFERENCES license(license_id)
);
CREATE TABLE token_log (
token_log_id INT PRIMARY KEY AUTO_INCREMENT,
token CHAR(36) NOT NULL,
ip VARCHAR(200) NOT NULL,
used_on DATETIME NOT NULL,
CONSTRAINT fk_tokenlog_token FOREIGN KEY (token) REFERENCES token(token)
);
Best Regards
mscho

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29607647-error-error-er_parse_error?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github).

Please always provide all necessary details you should in any case always add:
used:

node version
npm version
db-migrate version
db-migrate driver version
db-migrate driver(s)

Also attach a verbose run and in this case also post the versions of both mysql servers. In the verbose run you get an output of the generated queries which you can also test by hand.
Without this information I'm currently not able to help you.
Please get this informations especially important now the verbose run output

Hey there @mschop. Be sure to add "multipleStatements": true to each environment in your database.json configuration file, otherwise sql file based MySQL migrations (using the node-mysql driver) will fail after the first statement due to a syntax error.

@mschop +1

I am running below migration but I am also getting syntax error
SET SESSION sql_mode="NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION";
/*
set global log_bin_trust_function_creators=1;
SET FOREIGN_KEY_CHECKS=0;
ALTER DATABASE invite_manager CHARACTER SET utf8 COLLATE utf8_unicode_ci;
ALTER TABLE [[table]] CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;
*/
CREATE FUNCTION fun_enc(_password VARCHAR(255))
RETURNS TEXT
DETERMINISTIC
BEGIN
RETURN	PASSWORD(PASSWORD(PASSWORD(_password)));
END;
/* ====================================================== */
CREATE TABLE IF NOT EXISTS  status (
status_id BIGINT UNSIGNED NOT NULL PRIMARY KEY  AUTO_INCREMENT,
name VARCHAR(30) NOT NULL,
type VARCHAR(30) NOT NULL DEFAULT 'OTHER',
rcd timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
rcu varchar(255) NOT NULL ,
rmd timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
rmu varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (1,'ACTIVE','AI','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (2,'INACTIVE','AI','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (3,'DELETED','AI','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (4,'UP','PH','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (5,'DOWN','PH','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (6,'READY','QUEUE','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (7,'IN PROGRESS','QUEUE','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (8,'ERROR','QUEUE','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (9,'COMPLETE','QUEUE','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (10,'DAY','DATETIME','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (11,'MONTH','DATETIME','migration','migration');
INSERT IGNORE INTO status (status_id,name,type,rcu,rmu) VALUES (12,'YEAR','DATETIME','migration','migration');
....................
.........................
[ERROR] Error: ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CREATE FUNCTION fun_enc(_password VARCHAR(255))
RETURNS TEXT
DETERMINISTIC

@samiksha-singla Please use code blocks...
And also please provide all information necessary to help you. From right now, it looks like you are using not db-migrates migrations but raw sql. Therefor all SQL Syntax errors are your own fault, please refer to the official documentation of your used database to lookup how the Syntax should be.

As a hint, you're probably missing delimiters...

For future issues: https://help.github.com/articles/creating-and-highlighting-code-blocks/

What details should I share with you for better debugging ? I am indeed using migration files instead of raw sql. One thing more these migrations works perfectly on mysql server on linux  but on windows same migrations are problematic .. ? any hints for this .

@samiksha-singla Just scroll up: https://github.com/db-migrate/node-db-migrate/issues/333#issuecomment-169114012

One thing more these migrations works perfectly on mysql server on linux but on windows same migrations are problematic .. ? any hints for this .
Don't know, I am not a windows user, try to ask this on stack overflow.

I am indeed using migration files instead of raw sql.
No you don't. There is no support for CREATE FUNCTION yet, though you must use raw sql otherwise you wouldn't be able to actually.

Well, sorry for this issue. It seems, that this is caused by some strange mysql system/version depending syntax difference. It's now working.

Hey there @mschop. Be sure to add "multipleStatements": true to each environment in your database.json configuration file, otherwise sql file based MySQL migrations (using the node-mysql driver) will fail after the first statement due to a syntax error.

This worked like a charm!!!


Compile failure with swiftUI

Type conflicts are found. Color in SwiftUI is an existing class, and BFKit contains the following code
public typealias Color = UIColor
This caused me to compile failure and had to remove the relevant code

Thanks, I will look at it!
Maybe I will need to rename the Color typealias...

Thanks, I will look at it!
Maybe I will need to rename the Color typealias...


How to set a new token?

Hey, how should I set a token so that every new browser requests has it in its Authorization header?
Thanks

Setting a new token is not part of the package, however - you can use the PyJWT package I use for this package.
Please take a look at https://github.com/jpadilla/pyjwt and see how to generate new token.
Have a great week,
Amit.


Stronger fading when you start typing

When the compose box is open, we fade messages from streams/topics the user is not replying to to reduce the chance they send a message to a stream/topic they didn't intend, and to reduce the visual/cognitive processing required to figure out where their message is going to go.
I think there is room to continue in this direction even further, by e.g. darkening (or highlighting, or boxing) the messages / nav bars / etc of the stream/topic the user is replying to. One idea would be to add this darkening only after they've started typing, rather than when the compose box opens. This is both for performance reasons (it already takes a lot of work to make fading performant), and in order to not be too distracting in the common case when the user is not intending to send a message.

Hi!
I'd like to start on this as my first contribution for outreachy. This would be my first ever contribution so could you please help me and tell me how to proceed? I know C/C++, Python and basic HTML,CSS and Java.

Hi! I'm guessing this is actually no longer a good thing to work on, since Zulip is currently going through a visual redesign which will likely change the experience around this. Thanks for reading through our issues, and hope you find another project of interest! I've removed the "help wanted" tag.


Linter issues

When checking whether a linter exists, we're always treating linters as modules in the current python installation. I.e. if user has provided fully qualified path to linter, we still check if linter is installed using pythong -c 'import <linter>'
The telemetry captured to determine whether a user has provided a fully qualified path to a linter no longer works (logic is incorrect)
Assume user enters the path to a linter in settings.json, and the path is invalid.
We'll display the message Linter xxx is not installed [Install] [Disable xxx] [Disable linting]
If user opts to install, they'll keep getting the above error as the path provided in settings.json is invalid.

Sample messages that will be displayed for Test Frameworks, Linters and Formatters (when the paths are invalid):

The prompt is not triggered if you specify "doesnotexist"; it seems to be specific to lacking a path separator.

@brettcannon
Do you not get any prompt when you use doesnotexist?
There are two types of prompts, one that will mention the invalid path and the other thats a generic message.

I get the generic message to install Black.


Changed linter to standardjs

New Pullrequest for ticket #19
Changes:

Replaced semistandard with standardjs
Fixed lint errors
Removed unused file

Thank you @sAleksovski!
closes #19


fix #309 validity checks for query and target files

@ohadmo any idea why CI is not executing?

@vellamike, seems like there is a long queue caused by cudf

@rached-ab for the style check failures, take a look at the code formatting (and auto formatting) option we have for the repo - https://github.com/clara-genomics/ClaraGenomicsAnalysis#code-formatting


Openapi

Sync my openapi branch with the new openapi branch on this repo.
@vloschiavo when happy with the pull request, please click "Squash and merge" during the merging :)
First draft of the openapi documentation based on the readme information added by the community.  Lots more still to do but hopefully this is a good starter for 10 and we can get an idea of whether this format works for contributors of whether they prefer the readme format.
Once the content is on the openapi branch we can enable GitHub Pages to deploy the branch content as a website.  Second PR incoming for the new paragraphs in the readme mentioning the openapi spec alternative documentation as the readme changes will need to go to master before this new branch is finished with.

Hi @vloschiavo,
Apologies, seems I don't have the permission to switch on GitHub pages on this repo.  Please can you enable GitHub pages and select the openapi branch as the one to deploy?

Settings --> Pages --> Source: Deploy from a branch --> Branch: openapi.
Thank you :)

No problem! Done!
-Vince Loschiavo
On Fri, Apr 7, 2023, 12:13 vls29 @.***> wrote:

Hi @vloschiavo https://github.com/vloschiavo,
Apologies, seems I don't have the permission to switch on GitHub pages on
this repo. Please can you enable GitHub pages and select the openapi branch
as the one to deploy?
[image: image]
https://user-images.githubusercontent.com/11139924/230664244-8709dc13-2de2-4b65-8c27-b0f69ca047fb.png
Settings --> Pages --> Source: Deploy from a branch --> Branch: openapi.
Thank you :)
—
Reply to this email directly, view it on GitHub
https://github.com/vloschiavo/powerwall2/pull/92#issuecomment-1500562280,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCYSW6QEYIYG5PBCUTSFJDXABRMTANCNFSM6AAAAAAWWRWMXE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Filesystem performance on macOS 10.15

Firstly, I think this looks like a great project and it's good to see an alternative in this space!
I finally got around to testing vctl on Fusion 11.5.6 (macOS 10.15.6, MBP 2018 32GB i7-8850H) in comparison to Docker For Mac. These are some typical build times from clean for a nodejs (bucklescript, actually) project, 2 CPUs and 8GB RAM assigned to the container VM.
Native: 2s
Docker for Mac (osxfs): 10s
Fusion/vctl: 30s
I'm not sure if there are any tuning or filesystem-related knobs we can play with?

Not presently, but maybe @jeffwubj would have more insight.
I know that we're doing a lot of performance-related work in the upcoming Fusion 12 release, but I'm not sure how many 'knobs' we expose...

I'm also seeing terrible fs performance on macOS Big Sur with the latest VMware Fusion.
This seems to impact both volumes and the containers themselves, for example javascript-obfuscator, a node.js project with many dependencies takes about 8 seconds to even show the help on CLI compared to 0.2s on macOS native.
in vctl container:
root@php:/app# time /usr/local/bin/javascript-obfuscator
Usage: javascript-obfuscator <inputPath> [options]

[output omitted]

real	0m8.319s
user	0m1.328s
sys	0m0.294s

on macOS:
❯ time /usr/local/bin/javascript-obfuscator
Usage: javascript-obfuscator <inputPath> [options]

[output omitted]

/usr/local/bin/javascript-obfuscator  0.26s user 0.05s system 104% cpu 0.293 total

I'm also seeing terrible fs performance on macOS Big Sur with the latest VMware Fusion.
This seems to impact both volumes and the containers themselves, for example javascript-obfuscator, a node.js project with many dependencies takes about 8 seconds to even show the help on CLI compared to 0.2s on macOS native.
in vctl container:
root@php:/app# time /usr/local/bin/javascript-obfuscator
Usage: javascript-obfuscator <inputPath> [options]

[output omitted]

real	0m8.319s
user	0m1.328s
sys	0m0.294s

on macOS:
❯ time /usr/local/bin/javascript-obfuscator
Usage: javascript-obfuscator <inputPath> [options]

[output omitted]

/usr/local/bin/javascript-obfuscator  0.26s user 0.05s system 104% cpu 0.293 total


Lazy invalid defaults get silently converted to nil

I discovered that setting a default to a lazy value of the wrong type silently converts it to nil instead of raising an error. For example:
class Example < ActiveInteraction::Base
  boolean :a_boolean,
    default: -> { Object.new }

  def execute
    inputs
  end
end

Example.run!
# => {:a_boolean=>nil}

That should be raising an InvalidDefaultError, as it would when default: Object.new.

:(

I probably introduced this regression in #271.

In particular, I think #271 and #265 conspired to create this regression.


simple wgpu example

this is a simple example using wgpu of a rainbow triangle that is centered at the mouse position.
it's probably not the cleanest way to do things on the wgpu side but it's a good starter example for people looking to use wgpu in baseview
some things to note:

the wgpu version used is 0.18, this is because we needed a version that accepted a window that implements HasRawWindowHandle and HasRawDisplayHandle from rwh
the surface size on wgpu should be twice the window size in baseview for the sizes to match up. not sure why this is, but good to note

@prokopyl not sure what the weird clippy error is for the windows test, looks like its coming from the baseview source. everything else should be fixed though!

fyi @andrew-r-thomas, i was able to get the latest version of wgpu working with your example, basically i remove the lifetime requirements, made Surface 'static, and converted directly between the raw window and display handle types between 05 and 0.6

fyi @andrew-r-thomas, i was able to get the latest version of wgpu working with your example, basically i remove the lifetime requirements, made Surface 'static, and converted directly between the raw window and display handle types between 05 and 0.6

sweet! I think there are a bunch of refactoring changes for baseview that are in progress that will allow for 0.6 to be more fully supported, but good to know that theres a fix in the meantime!


Optional putting post content in RSS feed

Optionally (disabled by default) it could be also possible to put also the whole content of the post in the RSS feed - <content:encoded> (probably also with <media:content>).
Sample feed with content.

I added all of them
params.toml
...
updatePeriod = "" # Possible values: 'hourly', 'daily', 'weekly', 'monthly', or 'yearly'.
updateFrequency = ""
fullContents = false

Thanks, it works in general. However there is some problem with the images - they are not displayed.
For the following markdown:
> Get know about my migration from WordPress to Hugo and the reasons behind it.

{{}}

{{< notice info >}}
This is a modified version of the blog post I also placed as the last one on my old WordPress-based blog.
{{< /notice >}}

## Welcome to my new blog!

I have:

Get know about my migration from WordPress to Hugo and the reasons behind it.

<img data-src="https://preview--solidsoft-blog-hugo.netlify.com/images/posts/wordpress-to-hugo.png" data-caption=""
             src="data:image/svg+xml,%0A%3Csvg xmlns='http://www.w3.org/2000/svg' width='24' height='24' viewBox='0 0 24 24'%3E%3Cpath fill='none' d='M0 0h24v24H0V0z'/%3E%3Cpath fill='%23aaa' d='M19 3H5c-1.1 0-2 .9-2 2v14c0 1.1.9 2 2 2h14c1.1 0 2-.9 2-2V5c0-1.1-.9-2-2-2zm-1 16H6c-.55 0-1-.45-1-1V6c0-.55.45-1 1-1h12c.55 0 1 .45 1 1v12c0 .55-.45 1-1 1zm-4.44-6.19l-2.35 3.02-1.56-1.88c-.2-.25-.58-.24-.78.01l-1.74 2.23c-.26.33-.<IP_ADDRESS>h8.98c.41 0 .65-.47.4-.8l-2.55-3.39c-.19-.26-.59-.26-.79 0z'/%3E%3C/svg%3E"
             class="lazyload" width="400px" height=""/>

 This is a modified version of the blog post I also placed as the last one on my old WordPress-based blog.

Welcome to my new blog!

Looking at some SO answers (I'm also not familiar with Atom), I wonder if data-src shouldn't be replaced with just src?

There were some mistakes in the rss.xml. Now it's fixed
Since I can't detect images in the post when making the xml file, I use the image specified in the front-matter.
---
image: "images/..."
---

My feeder doesn't display them. However, I see they are in the feed, so it may be it just cannot used it. Let's leave it as it - the content itself is displayed. Thanks.


I try to install with cabal install graphql-api, but I have an issue

Building library for graphql-api-0.1.2..
[ 1 of 18] Compiling GraphQL.Internal.Arbitrary ( src/GraphQL/Internal/Arbitrary.hs, dist/build/GraphQL/Internal/Arbitrary.o )
[ 2 of 18] Compiling GraphQL.Internal.OrderedMap ( src/GraphQL/Internal/OrderedMap.hs, dist/build/GraphQL/Internal/OrderedMap.o )
[ 3 of 18] Compiling GraphQL.Internal.Syntax.Tokens ( src/GraphQL/Internal/Syntax/Tokens.hs, dist/build/GraphQL/Internal/Syntax/Tokens.o )
[ 4 of 18] Compiling GraphQL.Internal.Syntax.AST ( src/GraphQL/Internal/Syntax/AST.hs, dist/build/GraphQL/Internal/Syntax/AST.o )
src/GraphQL/Internal/Syntax/AST.hs:55:1: warning: [-Wdodgy-imports]
Module ‘Protolude’ does not export ‘Type’
|
55 | import Protolude hiding (Type)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 5 of 18] Compiling GraphQL.Internal.Syntax.Parser ( src/GraphQL/Internal/Syntax/Parser.hs, dist/build/GraphQL/Internal/Syntax/Parser.o )
src/GraphQL/Internal/Syntax/Parser.hs:86:23: error:
Ambiguous occurrence ‘option’
It could refer to either ‘Protolude.option’,
imported from ‘Protolude’ at src/GraphQL/Internal/Syntax/Parser.hs:8:1-41
(and originally defined in ‘Data.Semigroup’)
or ‘Data.Attoparsec.Text.option’,
imported from ‘Data.Attoparsec.Text’ at src/GraphQL/Internal/Syntax/Parser.hs:23:5-10
(and originally defined in ‘Data.Attoparsec.Combinator’)
|
86 | field = AST.Field <$> option empty (pure <$> alias)
|                       ^^^^^^
src/GraphQL/Internal/Syntax/Parser.hs:333:12: error:
Ambiguous occurrence ‘option’
It could refer to either ‘Protolude.option’,
imported from ‘Protolude’ at src/GraphQL/Internal/Syntax/Parser.hs:8:1-41
(and originally defined in ‘Data.Semigroup’)
or ‘Data.Attoparsec.Text.option’,
imported from ‘Data.Attoparsec.Text’ at src/GraphQL/Internal/Syntax/Parser.hs:23:5-10
(and originally defined in ‘Data.Attoparsec.Combinator’)
|
333 | optempty = option mempty
|            ^^^^^^
cabal: Leaving directory '/var/folders/zb/jqp3vqj170nc5vkyw8k2p_tw0000gn/T/cabal-tmp-13818/graphql-api-0.1.2'
cabal: Error: some packages failed to install:
graphql-api-0.1.2-HmKbgdf15yT6zJHN4EkHkp failed during the building phase. The
exception was:
ExitFailure 1

I think probably we need to put an upper bound on the protolude version (or update the code to use the latest protolude and then put a lower bound on it).
I personally won't have time to address this over the next few weeks, but would be happy to review a PR.

What version of Protolude is working for you ?

Whichever is included in the Stackage nightly-2017-01-25 resolver, c.f.
https://github.com/jml/graphql-api/blob/master/stack.yaml#L1
On Mon, 4 Sep 2017 at 13:15 Thibaut Assus<EMAIL_ADDRESS>wrote:

What version of Protolude is working for you ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jml/graphql-api/issues/121#issuecomment-326948328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHq6hPT5JJi_mH24CpsJRKEv4kAoXZCks5se-nigaJpZM4PL1Z_
.

    protolude-0.1.10
``` is working for me, so it's probably protolude 0.2 that breaks

@tibastral does the latest master (which includes https://github.com/jml/graphql-api/pull/123) work for you?

@tibastral I'm closing this for now, but please re-open if you're still having issues.


Updated kubelet server references about 4h hardcoded timeout

Updated kubelet server related page regarding the hard-coded 4h timeout in case of non idle logging.
Partially fix : https://github.com/kubernetes/kubernetes/issues/104595

/ok-to-test

this documentation is generated from kubelet help text. update the help text at https://github.com/kubernetes/kubernetes/blob/master/cmd/kubelet/app/options/options.go#L478 to modify the source this is pulled from

This is being fixed with https://github.com/kubernetes/kubernetes/pull/104735 in the k/kubernetes repo.
Can you close this PR @Debanitrkl ? Thanks!


Added options passed to validate_unique/3 to changeset.validations

This makes it so that:

you can look at the changeset and know if there's a scope or if the downcase option is set to true
validate_unique's metadata looks more like validate_length and other validators
if you wanted a test that a field is unique in a case insensitive way you don't have to roll the entire test, you can just look in changeset.validations

Not sure about this one. It at least feels wrong to add the repo to the metadata, that's not interesting to display to users. I can't really imagine a case where showing downcase is interesting either, scope may be interesting though but I can't imagine a case where I would display it to users.

@crismali Thank you! can you provide more information on where/when you need this metadata?

I'm not particularly interested in displaying the metadata to users as that seems more like the role of changeset.errors. I'm much more interested in having the metadata available for testing.
For example, if you're simply validating the uniqueness of a field with no options, you can write:
changeset = User.changeset(%User{})
assert {:email, :unique} in changeset.validations

instead of:
email =<EMAIL_ADDRESS>Repo.insert(%User{email: email})
changeset = User.changeset(%User{}, %{email: email})
assert changeset.errors == [email: "must be unique"]
refute changeset.valid?

I prefer the above test since validate_unique already essentially has the same test in Ecto itself.
But since the metadata for downcase or scope doesn't exist in changeset.validations, you can't write tests that look like the first one when passing those options. You have to write:
Repo.insert(%User{email<EMAIL_ADDRESS>changeset = User.changeset(%User{}, %{email<EMAIL_ADDRESS>assert changeset.errors == [email: "must be unique"]
refute changeset.valid?

instead of:
changeset = User.changeset(%User{})
assert {:email, {:unique, [on: Repo, downcase: true]}} in changeset.validations

The longer tests aren't a huge burden, they just seem to be testing the library in places it's already well tested =)

@crismali so I am not a fun of this style of tests. Then you are not testing anything really, you are simply testing the implementation.
However, I agree the metadata may be useful for other things and that we should include it if we can. Thank you!

No problem! =)


Object scope authorization with nested associations

The Object Scope Authorization currently does not support nested associations, because when the middleware is executed, the fields are still Ecto.Association.NotLoaded

Closed with #9


Any example of ComputedColumn? Handling relations, few beginner questions

How should I handle relationships with NPoco. Let's say I have
public class Player
{
    public int PlayerID { get; set; }
}

public class Item
{
    public int ItemID { get; set; }
    public int PlayerID { get; set; } // foreign key
}

How can I get all items of specified player.
I can do
var playerItems = db.Query<Item>().Where(item => item.PlayerID == playerId);

Can you explain how to query it in some other way?
I saw there are things like [ComputedColumn], [ResultColumn], [Ignore] but I don't know where to use them as they're not well documented.
What is the difference between [Ignore] and [ResultColumn]? If in both cases they're not mapped?
I use NPoco with the existing database. Is it possible to also use it in code-first databases? Will it generate tables for me?
Can NPoco auto generate Joins?

Have you looked here.
https://github.com/schotime/NPoco/wiki/Mapping

Yeah but I don't quite understand how does it handle relations


functionary-7b-v1 model upgrade

Suggested model functionary-7b-v1 is quite dumb, v1.4 uses Mistral, and v2.X is using new OpenAI API. Please support those new https://github.com/MeetKai/functionary models.
When I've try to use llama-cpp-python as an OpenAI api substitution with v1.4 I've got error:
Something went wrong: function ' execute_services' does not exist - like extra space within function name, when I use yaml as function configuration then sometimes it is ': function_name'
This is related to llama-cpp-python or functionary maybe ?

This is related log
llama-cpp-python    | root ::= object
llama-cpp-python    | object ::= [{] ws object_11 [}] ws
llama-cpp-python    | value ::= object | array | string | number | value_6 ws
llama-cpp-python    | array ::= [[] ws array_15 []] ws
llama-cpp-python    | string ::= ["] string_18 ["] ws
llama-cpp-python    | number ::= number_19 number_25 number_29 ws
llama-cpp-python    | value_6 ::= [t] [r] [u] [e] | [f] [a] [l] [s] [e] | [n] [u] [l] [l]
llama-cpp-python    | ws ::= ws_31
llama-cpp-python    | object_8 ::= string [:] ws value object_10
llama-cpp-python    | object_9 ::= [,] ws string [:] ws value
llama-cpp-python    | object_10 ::= object_9 object_10 |
llama-cpp-python    | object_11 ::= object_8 |
llama-cpp-python    | array_12 ::= value array_14
llama-cpp-python    | array_13 ::= [,] ws value
llama-cpp-python    | array_14 ::= array_13 array_14 |
llama-cpp-python    | array_15 ::= array_12 |
llama-cpp-python    | string_16 ::= [^"\] | [\] string_17
llama-cpp-python    | string_17 ::= ["\/bfnrt] | [u] [0-9a-fA-F] [0-9a-fA-F] [0-9a-fA-F] [0-9a-fA-F]
llama-cpp-python    | string_18 ::= string_16 string_18 |
llama-cpp-python    | number_19 ::= number_20 number_21
llama-cpp-python    | number_20 ::= [-] |
llama-cpp-python    | number_21 ::= [0-9] | [1-9] number_22
llama-cpp-python    | number_22 ::= [0-9] number_22 |
llama-cpp-python    | number_23 ::= [.] number_24
llama-cpp-python    | number_24 ::= [0-9] number_24 | [0-9]
llama-cpp-python    | number_25 ::= number_23 |
llama-cpp-python    | number_26 ::= [eE] number_27 number_28
llama-cpp-python    | number_27 ::= [-+] |
llama-cpp-python    | number_28 ::= [0-9] number_28 | [0-9]
llama-cpp-python    | number_29 ::= number_26 |
llama-cpp-python    | ws_30 ::= [ <U+0009><U+000A>] ws
llama-cpp-python    | ws_31 ::= ws_30 |
llama-cpp-python    | system:
llama-cpp-python    | // Supported function definitions that should be called when necessary.
llama-cpp-python    | namespace functions {
llama-cpp-python    |
llama-cpp-python    |   // Use this function to execute service of devices in Home Assistant.
llama-cpp-python    |   type execute_services = (_: {
llama-cpp-python    |     //
llama-cpp-python    |     list?: Array<{
llama-cpp-python    |         domain: string,
llama-cpp-python    |         service: string,
llama-cpp-python    |         service_data: {
llama-cpp-python    |           entity_id: string,
llama-cpp-python    |         },
llama-cpp-python    |       }>,
llama-cpp-python    |   }) => any;
llama-cpp-python    |
llama-cpp-python    | } // namespace functions
llama-cpp-python    |
llama-cpp-python    | system:
llama-cpp-python    | A chat between a curious user and an artificial intelligence assistant. The assistant gives helpful, detailed, and polite answers to the user's questions. The assistant calls functions with appropriate input when necessary
[...]
llama-cpp-python    | user:
llama-cpp-python    | </s>turn on kanapa light</s>
llama-cpp-python    | assistant: execute_services:
llama-cpp-python    |
llama-cpp-python    | {
llama-cpp-python    |   "list": [
llama-cpp-python    |     {
llama-cpp-python    |       "domain": "light",
llama-cpp-python    |       "service": "turn_on",
llama-cpp-python    |       "service_data": {
llama-cpp-python    |         "entity_id": "light.kanapa"
llama-cpp-python    |       }
llama-cpp-python    |     }
llama-cpp-python    |   ]
llama-cpp-python    | }
llama-cpp-python    |
llama-cpp-python    |

Thank you, I wasn't aware they update the model, will do!

All v1 models becomes obsolete https://github.com/MeetKai/functionary/issues/83

Hi @abetlen , I'm from the team at functionary. Thank you for integrating our models into llama-cpp-python!
As mentioned by @luzik , it seems like you would like to add support for all our newer models (which are much more powerful and intelligent than v1). There have been quite some changes in our models since v1, including the prompt format and templates, which you may not know of.
Thus, to prevent wrong prompt templates, I will work to add support for all of our newer models in llama-cpp-python. I'll keep you updated on when the PR is raised!

Hey @jeffrey-fong great work on the models and I appreciate the help, I'll take a look at the PR over the weekend and see about getting this merged in soon.

Hi, I also run into issue with functionary v1. I have tested the PR and it works pretty well. Is it possible to merge it soon? @abetlen ?

There is also web server documentation to be fixed
https://github.com/abetlen/llama-cpp-python/blob/main/docs/server.md#function-calling


NHM data processing and addition to intake catalog

The original NHM data is on ScienceBase, but it probably needs to be reformatted. Parker has a version on Caldera and on S3. @pnorton-usgs and Jacob will work with Rich to reformat this data.

@pnorton-usgs - I know you've been working on updating CONUS404. Has the NHM data rechunking had any progress, or will it be worked on anytime in the near future?

@amsnyder I have this on my list of things to do but currently I don't expect to get to it before mid-October at the earliest.

@amsnyder @rsignell-usgs @pnorton-usgs
The National Water Census has an S3 bucket that they will serve NHM-PRMS v1.0 and v1.1 on in native format and aggregated to HUC12s. Maybe we can tap into that, I chatted Shirley and she will get back to me with the s3 URLs.

@sfoks any update on the NHM results from NWC? Would this version be the same as what your benchmark results are based upon? Is this version what should be used in HyTEST evaluation notebooks?
This is an interesting case, in that WMA potentially has a lot of projects storing redundant copies of the same (or darn similar) data, with no real tracking of this. Don't know if the type of tracking we're doing around CONUS404 (which is largely internal to our own project) would scale to a WMA-wide effort.

@rviger-usgs No updates on this (need to follow-up with Shirley). Last correspondence was that the NWC was thinking of modeling application delivery via globus endpoint. I think there was a meeting today @alamotte-usgs and NHGF with NWC about data and storage. Any mention of modeling application locations and storage on s3 or BlackPearl?

@sfoks Still digesting today's meeting, I don't think we got that deep into the weeds, but I could be wrong. I will follow up Monday before the Monday NWC call.

fwiw, if we all want to use the same version of the data, I'd love to have a particular project kind of "own" the dataset, serving it, and making this known to the community (e.g., through NHGF catalog). I'd been assuming that would be HyTEST but am flexible (MDMF? NHGF? NWCensus?).

@rviger-usgs I'd say STAC through NHGF catalog! ~wasn't that the original thinking?

@sfoks I attended the meeting too, and we did not determine a storage location, but I think Shirley & co. are going to follow up with me because I told them I wanted to discuss the datasets they were serving, storage location, and format to make sure we weren't duplicating efforts. I agree @alamotte-usgs - I think it should be exposed through the NHGF Catalog and STAC if we can. I was hoping to check if @rviger-usgs  would be ok with storing it on the OSN pod if they want to - seems like a really good use case for it.

I'm okay with it being on the OSN pod--think it'd want to be a published dataset to do it that way (don't think this is really a new requirement; NWCensus would probably need this, too). Might need to work with Jacob as the product owner for the PRMS and WRF-Hydro modeling applications. Thinking he'd get it pub'd via Sciencebase and we could replicate in a more usable form (if Sciencebase doesn't have the interfaces or performance that we/Shirley need).

I have finished kerchunking both NHM v1.0 and v1.1 model output variables for each calibration on caldera. I'm thinking the on-prem kerchunked datasets should be copied to hytest_scratch; @amsnyder what do you think? I've posted a similar question in issue #124. I can also push these to S3, I just need to know where they should go.

I talked to @pnorton-usgs this morning and suggested he place a copy of these NHM datasets hytest_scratch area for now. If someone needs to work with these in the cloud, we can discuss making an additional copy, but I think we should avoid making extra copies of data that we need to maintain and paying cloud storage fees without a use case. @pnorton-usgs will let us know when he has shared the data and added it to our intake catalog.

  Can they fit in our OSN 100TB allocation?

Parker gave me some very rough estimates of # of files and size and I think it's somewhere between 50-200 GB of data (big range of uncertainty, I know). We could put them on the OSN pod, but we will just have to move them once we get our actual pod, so I'd rather not put them there unless someone needs them in the cloud.
I am also worried about creating multiple copies of datasets without better dependency tracking to make sure that any dataset updates are propagated to all copies of the data.

We can close this again but I wanted to provide an update on the total space for the NHM model output. @amsnyder @rsignell-usgs The total size is about 800G.


Allow to set environment variables from build script

system-deps provides many environment variables to configure its options. This is great for end users, but it doesn't allow libraries to provide defaults or configure them programmatically.
An improvement could be to have a add_env method in the build script configuration that will add certain values to its environment (it doesn't set the real env variable). Since system-deps already had a Mock variable type tests, we can reuse it, providing a fallback to the environment in the case of build scripts and not doing so in tests.
Use cases

Configuring system-deps options using crate features. For example, a crate could have a feature that determines if it is statically or dynamically linked, and using add_env we can set the relevant variable from the build script.
Allow dependencies to provide defaults, for example, set linking line deduplication if the crate requires it.
Better interface with other env variables specific to the crate. If a package already reads the option SOME_CONFIG, it can now also set needed system-deps variables.

Considered alternatives

Use .cargo/config.toml to set [env] variables per target. However, rust doesn't allow to use features to configure these values, and dependencies can't share this with users.
Build scripts can emit environment variables and metadata using cargo directives. However, the first is only passed to it's corresponding library, and the second only sends the metadata to its dependent crates, not its dependencies (like system-deps).
Users can set the variables directly or with a Makefile/similar script. However, this requires extra configuration when using a dependency and it can cause unexpected issues.

TODO:

[ ] Should the environment or the set variables have priority? I'm leaning towards the current implementation (set variables shadow environment) since then the decision lays on the crate using system-deps. They can read the environment and decide whether to use it or not.
[ ] Add tests.
[ ] Link related PRs.

Note: This was originally part of the PR for supporting prebuilt binaries (ADD LINK). However, in an effort to make reviewing easy, I separated this feature since it works independently.

That seems very reasonable. During development I used this in a few places. However, after all of the refactoring, the only reason I still used this was to enforce the clean linking variable without requiring the user to specify it. But if we actually do the deduplication correctly we don't need the variable in the first place.
It is true that I could see other some potential uses for this (that's why I kept it in), like setting the environment based on features (since cargo doesn't allow this yet). However, if this was an intentional design decision, the best thing would be to do as you say and see if there are real use cases that can't be solved otherwise.


Document COSI API, resources, and add a simple getting started section

@jeffvance @rrati @brahmaroutu @tparikh

LGTM

LGTM

/lgtm

/lgtm


Error 502 Bad Gateway after migrating from NPM to NPMplus

Hey, i swaped out my NPM container for NPMplus in Unraid, afterwards i only get 502 errors for all my websites.
I have my domain on cloudflare and i am using cloudflare tunnel to directly connect to the cloudflared container running on my unraid server aswell.
This worked no problem for NPM, but something is buggy with NPMplus here. Not sure were to pinpoint this, so i am opening an issue here now.

Please send the docker logs

Nvm, i found the issue. My cloudflare tunnel was configured wrong and had the old hostname of NPM still as the configured proxy instead of npmplus.

Btw, as there is none, i am creating a template for npmplus for unraid, so others can use your container aswell there easily

Sounds good


Extend assistant-tool output handling

This add support for tool_use messages from the assistant tool.
What I addressed:

The tool sometimes returns message as a string, sometimes as an array of messages. I extended the MessageAssistant so we can handle both cases.
For arrays of messages, I added handle for two cases:

We render the markdown if the type is text
We render an action button in all other cases.

Changed the chat history state to use Jotai.

I'm sure we need to extend this further going forward when we have a better picture what the API returns.

This LGTM @oliverroick


[fix] #2923: Return FindError when AssetDefinition does not exist

Signed-off-by: Shanin Roman<EMAIL_ADDRESS>

Description of the Change
Skip validation if AssetDefinitionId doesn't exist.

Issue
Closes #2923.

Benefits
Proper error message.

Possible Drawbacks
No.

Seems fine to me code-wıse, but I don't think Skipping on error is a good idea, since we will be losing information about the error. Now we are returning Deny with error inside, see e.g. this macro, so for consistency we would should return Deny here as well.
I understand that we will most likely catch the error later anyway, but that would be too much relying on behavior of too distant part of the system for my taste.


Enable KTLS on connections using BIO_connect

The first commit introduces a potential behavior change that it would be good to check with on the Linux side in that ktls_start() might now be called on listen sockets and since BIO_socket can be used to create listen sockets (for example by bss_acpt.c).  Presumably Linux just ignores the socket option in ktls_start on such a socket, but it would be good to confirm that this is ok.
The second commit is in a response to a core dump on FreeBSD when 'openssl s_time' switches to reusing sessions since free() of a stack pointer triggers a crash inside of jemalloc (the libc malloc in FreeBSD).

Checklist

The commit message for the first change (and my initial comment above) both need to say "ktls_enable()" rather than "ktls_start()"

Automated Ping: This issue is in a state where it requires action by @openssl/committers but the last update was 35 days ago

@mattcaswell  Does your approval still hold?

This pull request is ready to merge

Merged to master, thank you.


Variable rename passes cause z3 crash

We currently skip the flattening passes of the P4 compiler. The reason is that both the Header and the Struct flattening pass generate a whole new set of z3 constants. We do not create a mapping of these variables and the z3 solver crashes because it does not seem to be able to handle the complexity of the comparison.
In the future, we need to find a way how to accurately translate variable renaming.

This also extends to UniqueName and Inline passes


Installation failed due to missing mods

The modpack currently fails to install because the following archives are hidden on the Nexus.

Dynamic Mountain Fogs - Cathedral Weathers
Improved Atmosphere Mesh - Cathedral Edition
Improved Cloud Mesh for Improved Atmosphere Mesh

They all appear to have been hidden on Feb 15th.

Elysium has updated, so redownload the list.

Thanks. Thought I had the most recent version of the modlist.

Another version should be up soon.


fix the hardcoding of api version for classicadmin in powershell

This is a fix for this hardcoding
https://github.com/Azure/azure-powershell/blob/preview/src/ResourceManager/Resources/Commands.Resources/Models.Authorization/AuthorizationClient.cs#L297
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

@mcardosos can you take a look into this,had to make a minor fix since the api version was moved to parameters section,we werent able to hardcode the api version like before[which isnt recommeded also]

@darshanhs90
To clarify (I am not familiar with Azure Powershell) How is it that moving files fixes the issue?
Is it because now files are in the wrong api version folder, and with this change they will be in the right api version folder, so it does not need to be overriden?

@mcardosos no earlier,since we had a apiversion as follows
"/subscriptions/{subscriptionId}/providers/Microsoft.Authorization/classicAdministrators": {
"get": {
"tags": [
"ClassicAdministrators"
],
"operationId": "ClassicAdministrators_List",
"description": "Gets service administrator, account administrator, and co-administrators for the subscription.",
"parameters": [
{
"name": "api-version",
"in": "query",
"required": true,
"type": "string",
"description": "The API version to use for this operation."
}
which allowed us to modify the api version in sdk and powershell for all the classicadmin requests[since we had a single swagger file with 2015-07-01 version]
The reason for hardcoding it in the requests was that classicadmin api supported only 2015-06-01 and not the other API version[2015-07-01]
Hence i made this PR to fix that issue.
As we moved the api-version to Parameters section ,it doesn't allow us to pass in the api version as part of the request like earlier causing the classicadmin calls to hit the api version 2015-07-01 resulting in bad request

Oh, okok :) Moving the files is the right thing to do in this case, yes.
If in the future, you happen to have a global param you want to pass in the method, take a look here
https://github.com/Azure/autorest/tree/master/docs/extensions#x-ms-parameter-location
(However, I wound not recommend this for API version parameter).
Change LGTM. @fearthecowboy is this change good for you too? For context, the operation ClassicAdministrators_List that is being removed in authorization.json, already exists in authorization-ClasicAdminCalls.json

@mcardosos anything blocking this pr to be merged?

I don't see a problem. @lmazuel -- you have any problem with this?

LGTM thanks @fearthecowboy :)


GPU-enabled Mac build of TensorFlow version 0.11.0rc2-py2 was compiled against cuDNN v5.1

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
This is a regression of issue #3826.
Environment info
Operating System: macOS Sierra Version 10.12.1 (16B2555)
Installed version of CUDA and cuDNN: cuda_8.0.47_mac, cudnn-8.0-osx-x64-v5.1 (I explain why I am using cuDNN v5.1 rather than cuDNN v5 below.)
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
lrwxr-xr-x  1 root  admin     13 Nov 11 17:13 /usr/local/cuda/lib/libcuda.1.dylib -> libcuda.dylib
-rwxr-xr-x@ 1 root  wheel  13504 Sep 26 17:59 /usr/local/cuda/lib/libcuda.dylib
lrwxr-xr-x@ 1 root  wheel     45 Sep 26 18:00 /usr/local/cuda/lib/libcudadevrt.a -> /Developer/NVIDIA/CUDA-8.0/lib/libcudadevrt.a
lrwxr-xr-x@ 1 root  wheel     50 Sep 26 18:00 /usr/local/cuda/lib/libcudart.8.0.dylib -> /Developer/NVIDIA/CUDA-8.0/lib/libcudart.8.0.dylib
lrwxr-xr-x@ 1 root  wheel     46 Sep 26 18:00 /usr/local/cuda/lib/libcudart.dylib -> /Developer/NVIDIA/CUDA-8.0/lib/libcudart.dylib
lrwxr-xr-x@ 1 root  wheel     49 Sep 26 18:00 /usr/local/cuda/lib/libcudart_static.a -> /Developer/NVIDIA/CUDA-8.0/lib/libcudart_static.a
lrwxr-xr-x  1 root  admin     47 Nov 11 17:29 /usr/local/cuda/lib/libcudnn.5.dylib -> /Developer/NVIDIA/CUDA-8.0/lib/libcudnn.5.dylib
lrwxr-xr-x  1 root  admin     45 Nov 11 17:29 /usr/local/cuda/lib/libcudnn.dylib -> /Developer/NVIDIA/CUDA-8.0/lib/libcudnn.dylib
lrwxr-xr-x  1 root  admin     48 Nov 11 17:29 /usr/local/cuda/lib/libcudnn_static.a -> /Developer/NVIDIA/CUDA-8.0/lib/libcudnn_static.a

If installed from binary pip package, provide:

A link to the pip package you installed: export TF_BINARY_URL=https://storage.googleapis.com/tensorflow/mac/gpu/tensorflow-0.11.0rc2-py2-none-any.whl
The output from python -c "import tensorflow; print(tensorflow.__version__)".

I tensorflow/stream_executor/dso_loader.cc:111] successfully opened CUDA library libcublas.dylib locally
I tensorflow/stream_executor/dso_loader.cc:111] successfully opened CUDA library libcudnn.dylib locally
I tensorflow/stream_executor/dso_loader.cc:111] successfully opened CUDA library libcufft.dylib locally
I tensorflow/stream_executor/dso_loader.cc:111] successfully opened CUDA library libcuda.1.dylib locally
I tensorflow/stream_executor/dso_loader.cc:111] successfully opened CUDA library libcurand.dylib locally
0.11.0rc2

If installed from source: Not Applicable
If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)

Set up TensorFlow according to the instructions at
https://www.tensorflow.org/versions/r0.11/get_started/os_setup.html#prepare_environment_for_mac_os_x
In particular, the page says to install cuDNN v5 from the cuDNN Download page.

Test the installation by running:
 cuda-memcheck python -m tensorflow.models.image.mnist.convolutional

You should see:

E tensorflow/stream_executor/cuda/cuda_dnn.cc:368] Loaded runtime CuDNN library: 5005 (compatibility version 5000) but source was compiled with 5105 (compatibility version 5100).  If using a binary install, upgrade your CuDNN library to match.  If building from sources, make sure the library loaded at runtime matches a compatible version specified during compile configuration.

What other attempted solutions have you tried?
Uninstalling cuDNN v5 and installing cuDNN v5.1 (labeled "cuDNN v5.1 (August 10, 2016), for CUDA 8.0" on the cuDNN Download page) fixes the issue.
As before in issue #3826, the installation instructions should be corrected to specify that cuDNN v5.1 needs to be installed.

cc @yifeif
Will update the docs,
Which documentation have you been using specificly?

I was following:
https://www.tensorflow.org/versions/r0.11/get_started/os_setup.html#prepare_environment_for_mac_os_x
The master version of these docs appear to be the same:
https://www.tensorflow.org/versions/master/get_started/os_setup.html#prepare_environment_for_mac_os_x

@yifeif, did we update the documentation about this one?

Updated the instruction at #6407. Should be up on the website tomorrow.


CLOUD-684 change slack notifications

Test name
Status

demand-backup
passed

init-deploy
passed

scaling
passed

recreate
passed

affinity
passed

monitoring
passed

self-healing
passed

scheduled-backup
passed

operator-self-healing
passed

clone-cluster
passed

tls-check
passed

users
passed

ns-mode
passed

commit: https://github.com/percona/percona-postgresql-operator/pull/211/commits/bbc6834b62235f16bb4f2d51a2c86dde7c4cb50b
image: perconalab/percona-postgresql-operator:PR-211-bbc6834b-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-211-bbc6834b-pgo-event
image: perconalab/percona-postgresql-operator:PR-211-bbc6834b-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-211-bbc6834b-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-211-bbc6834b-postgres-operator
image: perconalab/percona-postgresql-operator:PR-211-bbc6834b-pgo-deployer


Examples are not working

I have been trying to run the examples, specifically this one: https://github.com/FluxML/GeometricFlux.jl/blob/master/examples/graphconv.jl.
I am getting the following error:
[ Info: Training on GPU
ERROR: LoadError: MethodError: no method matching getindex(::Cora, ::Int64)
Stacktrace:
 [1] load_data(dataset::Cora, batch_size::Int64, train_repeats::Int64, test_repeats::Int64) (repeats 2 times)
   @ Main /workspace/Julia/graphconv.jl:16
 [2] train(; kws::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
   @ Main /workspace/Julia/graphconv.jl:73
 [3] train()
   @ Main /workspace/Julia/graphconv.jl:57
 [4] top-level scope
   @ /workspace/Julia/graphconv.jl:116
in expression starting at /workspace/Julia/graphconv.jl:116

I am using Julia v 1.8.1. I have installed the latest versions of the listed dependencies.

It seems error occurs at loading data.
Could you please check if you have MLDatasets installed?

Yes, MLDatasets is installed.

Is it using MLDatasets successfully? It's kind of weird and should don't raise error. I tested it on my computer and it got passed.

Could you reproduce this?
julia> using MLDatasets

julia> cora = Cora()
dataset Cora:
  metadata    =>    Dict{String, Any} with 3 entries
  graphs      =>    1-element Vector{MLDatasets.Graph}

julia> cora[1]
Graph:
  num_nodes   =>    2708
  num_edges   =>    10556
  edge_index  =>    ("10556-element Vector{Int64}", "10556-element Vector{Int64}")
  node_data   =>    (features = "1433×2708 Matrix{Float32}", targets = "2708-element Vector{Int64}", train_mask = "140-trues BitVector", val_mask = "500-trues BitVector", test_mask = "1000-trues BitVector")
  edge_data   =>    nothing

julia> @which cora[1]
getindex(d::Cora, i) in MLDatasets at /home/yuehhua/.julia/packages/MLDatasets/eZ0Va/src/datasets/graphs/cora.jl:64

I am using MLDatasets v0.5.15. Here is the trace:
julia> using MLDatasets

julia> cora = Cora()
ERROR: MethodError: objects of type Module are not callable
Stacktrace:
 [1] top-level scope
   @ REPL[2]:1

The latest version is MLDatasets v0.7.4. Could you update to this version?

I have updated the packages, still getting the same error.
My packages:
  [052768ef] CUDA v3.12.0
  [587475ba] Flux v0.13.6
⌃ [7e08b658] GeometricFlux v0.13.4
  [3ebe565e] GraphSignals v0.7.3
⌃ [86223c79] Graphs v1.7.3
  [eb30cadb] MLDatasets v0.7.4
  [d96e819e] Parameters v0.12.3
  [92933f4c] ProgressMeter v1.7.2
  [10745b16] Statistics

Trace:
ERROR: LoadError: MethodError: no method matching getindex(::Cora, ::Int64)
Stacktrace:
 [1] load_data(dataset::Cora, batch_size::Int64, train_repeats::Int64, test_repeats::Int64) (repeats 2 times)
   @ Main /GCN.jl:16
 [2] train(; kws::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
   @ Main /GCN.jl:73
 [3] train()
   @ Main /GCN.jl:57
 [4] top-level scope
   @  /GCN.jl:116
in expression starting at /GCN.jl:116

Hi @kaansancak  Updating GeometricFlux to the latest version 0.13.7 solves the issue. The 0.13.4 version is not using MLDatasets.jl. Reproduce:
(tmp.V2PSqe1wQb) pkg> add<EMAIL_ADDRESS>.
.
.
julia> @which Cora()
Cora() in GraphMLDatasets at /home/deebyo/.julia/packages/GraphMLDatasets/nsi8O/src/dataset.jl:41

You can update all the packages using using Pkg; Pkg.update(). If you cannot use the current version of GeometricFlux.jl use a temporary environment . Hope it solves the issue.

Hi @kaansancak Updating GeometricFlux to the latest version 0.13.7 solves the issue. The 0.13.4 version is not using MLDatasets.jl. Reproduce:
(tmp.V2PSqe1wQb) pkg> add<EMAIL_ADDRESS>.
.
.
julia> @which Cora()
Cora() in GraphMLDatasets at /home/deebyo/.julia/packages/GraphMLDatasets/nsi8O/src/dataset.jl:41

You can update all the packages using using Pkg; Pkg.update(). If you cannot use the current version of GeometricFlux.jl use a temporary environment . Hope it solves the issue.

This solved the issue, thank you!


setProgressButtonEnabled on AppIntro class doesnt work

I am trying to hide Next button on First Slide and show it on the Second Slide. I set setProgressButtonEnabled(false) on the AppIntro class as well as First Slide. On the Second Slide, I set setProgressButtonEnabled(true). However, I observe that the next button is hidden on second slide. I even tried to use ((AppIntro) getActivity()).findViewById(R.id.next).setVisibility(View.GONE). Even this doesn't work.
However, ((AppIntro) getActivity()).findViewById(R.id.vuew_pager).setCurrentItem(1) moves to the next slide.
Please help me on this issue.

Can you try building and looking at DisableSwipeIntro1.java for an example?
To try your example, I changed the following in it:
@Override
public void onSlideChanged() {
    if(pager.getCurrentItem() == 1){
        Toast.makeText(getApplicationContext(), "currently item 1", Toast.LENGTH_SHORT).show();
        setProgressButtonEnabled(true);
    }
}

and
public void toggleProgressButton(View v) {
    setProgressButtonEnabled(false);
}

Otherwise if it's still not working, can you post your code/configuration somewhere so I can look at it? It's working for Android 4.4 through 6.0 for me.

@srihari1988 did @danluong's suggestion work for you?

Trying to achieve a similar functionality. Though
((AppIntro2) getActivity()).setProgressButtonEnabled(false); works but the button is disabled (or hidden) for all the slides. And with @danluong 's suggested code, I am getting NullPointerException.
Moreover, what I am trying to achieve is ability to have the next button disabled for 2nd (out of 3) slide and enable that button once user confirms a particular action.

Again, if you guys are having issues with this, please post a sample project so I can investigate why this is occurring. I'd be happy to look into it, but need more info.

The issue with my implementation was that the Viewpager was loading multiple pages at once and the code from last fragment gets executed last, thereby affecting my requirement. I overrided the setUserVisibleHint method on the fragment to ensure that the code is running (hiding next button) only when the fragment is visible (active).
@Override
public void setUserVisibleHint(boolean isVisibleToUser) {
super.setUserVisibleHint(isVisibleToUser);
    if (isVisibleToUser) {
        getActivity().findViewById(R.id.next).setVisibility(View.INVISIBLE);
}

}

Looks like this no longer applies after the recent changes on the library, please reopen this issue if still affected by this issue.


id: motion to modify intro - need to fill in info for defendant who is in the wrong place

What do we want to tell defendants who cannot use this interview at the beginning of the order?
See

What if the person who abused me files a protective order or criminal case against me?
Massachusetts law about defending against a c.209A Order?
Restraining Orders - Mental Health Legal Advisors Committee?
Talk to a lawyer?

Can we just refer them to this form on Mass.gov: https://www.mass.gov/doc/defendants-motion-to-modify-or-terminate-abuse-prevention-order-gl-c-209a/download

☝ Would that link alone work, @CaroRob ?

Conclusion: Defendants in these situations really need a lawyer. Advise defendant to talk to a lawyer and provide a link to https://masslrf.org/en/home.


model change and load park details

Description
This PR includes the following proposed change(s):

BC-337 Load park details and par model changes

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Does the change impact or break the Docker build?

[ ] Yes
[ ] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes

Hi Siva,
I'm adding this change now, just to get the model changes in place. The actual park details json data will be re-updated once Rob provides the new data.
Thanks,


Fix displaying of new PEPs in python-news

Currently we only send new PEP updates to #mailing-lists if they were "created" on the same day that the bot is checking for them.
https://github.com/python-discord/bot/blob/ea0b227801f19d14338e7e582d745ea250773370/bot/exts/info/python_news.py#L116-L120
This does not work in most cases, as when PEPs are created is not the same as when they are published.
https://peps.python.org/pep-0001/#pep-header-preamble

The Created header records the date that the PEP was assigned a number

The number is usually assigned quickly after the PR to https://github.com/python/peps is created, but then the PR is reviewed which means it can be a while before it's actually merged and becomes visible. The difference can be fairly big (e.g. https://github.com/python/peps/pull/2620).
We can fix this by extending the check if it's in the last month (maybe last 2 months). The only issue I see with this is that in development people might get a few peps sent in a row when they first start up, but this seems pretty minor.

I'm somewhat struggling with the overall logic of that function. If we're keeping track of what PEPs are already shown in the channel, why do we need any date validation?

I'm somewhat struggling with the overall logic of that function. If we're keeping track of what PEPs are already shown in the channel, why do we need any date validation?

It shouldn't make a big difference in production, although in dev it prevents you being sent loads of posts when you first start up the bot. The feed only contains the past 10 PEPs so it would be fine without the validation, although a generous time check would also be fine imo.

It also doesn't seem like there's an exit condition in the loop. Are we just going over the entire feed every time?

Yeah


Framework improvements

Removes the now unneeded module map. This means for swift projects an objective-c bridging header is no longer required.

Switched all imports to the new module import style, @import ModuleName for improved efficiency.

@E-B-Smith free to take a look at this?

Thanks -- I am going to merge this soon but I wanted to reach out to some partners first to see what impact this may have on them.  Many people use this code and expect it to just work!
Thanks for adding this!

no problem! Once it's in the developer doc should be updated to remove the bits about needed an objective-c bridging header.

I know, right?  That will be nice.

Result of Integration 1
Duration: 1 minute and 28 seconds
Result: 23 errors, failing state: build-errors

would fix but can't see integration results

No worries.  The new integration server wasn't configured right when it tested this PR.
Your PR is in the pipeline.  How would it affect you if I made the project a dynamic framework too?
I know that it would disrupt people on iOS 7 (yes, there are a surprising number of people still using iOS 7).  Are there any other issues?

Sorry @E-B-Smith what do you mean making the project a dynamic framework too? It's set to build them which also gives carthage support (forgot to mention that)!

@ekimia Yes - The carthage version builds as a dynamic framework, but the CocoaPod / straight integration still builds as a static library.

Ah, it wouldnt affect what i did at all :)

Result of Integration 2
Duration: 2 minutes and 35 seconds
Result: 25 errors, failing state: build-errors

Result of Integration 1
Duration: 1 minute and 16 seconds
Result: -1 error, failing state: build-failed

Result of Integration 1
Duration: 1 minute and 49 seconds
Result: 28 errors, failing state: build-errors

Result of Integration 1
Duration: 1 minute and 28 seconds
Result: -1 error, failing state: build-failed

Result of Integration 2
Duration: 18 seconds
Result: -1 error, failing state: build-failed

Result of Integration 4
Duration: 0 second
Result: -1 error, failing state: checkout-error

Result of Integration 5
Duration: 3 minutes and 12 seconds
Result: -1 error, failing state: checkout-error

Result of Integration 1
Duration: 1 minute and 7 seconds
Result: -1 error, failing state: build-failed

Result of Integration 2
Duration: 19 seconds
Result: -1 error, failing state: build-failed

Result of Integration 1
Duration: 1 minute and 5 seconds
Result: -1 error, failing state: build-failed

Result of Integration 1
Duration: 0 second
Build was manually canceled.

bump @E-B-Smith

Thanks for the bump.  See PR #705 .

closing in favor of https://github.com/BranchMetrics/ios-branch-deep-linking/pull/705


Feature repo create file

Hi, just added a new missing api method. Creating files in a repository.

Oh sorry, missing tests. Will add them.

@icyleaf don't know about the nightly crystal build, but I think it's ok. Please check.
cheers.

@icyleaf don't know about the nightly crystal build, but I think it's ok. Please check.
cheers.

Nightly build uses master branch of crystal-lang repo which was some broking changes since v1.0.0, i will fix it.


Move bulk video downloads to a celery task

Requesting to download multiple attachments starts a celery task that generates a zip file, uploads it to google cloud storage, creates a signed url, and emails it to the requesting user.

If a zip file with the same videos already exists on google cloud storage it just generates the link and emails it.

Hey @pattisdr I think I'm done with this. If you want to functionally test it you'll need credentials for AWS and Google Cloud Storage in your environment variables. You'll also need to set the env var for the GCS private bucket. If you want to do this lmk and I'll send you creds in a super secret way.
The only thing I'd be worried about is if the matching/consent stuff worked. I tested it pretty well but it couldn't hurt to check it again.

Looks good to me, nice work on this!!

:+1: :tada:


Opt-in Regions list is out of date

The list of AWS Opt-in regions in sessions.go does not include the latest AWS Regions. This limits users ability to use the latest AWS regions.
Please see the available region list here.
We will need to consume the new SDK version release in the plugin list below:

[ ] Athena
[ ] Redshift
[ ] Timestream
[ ] CloudWatch
[ ] X-ray
[ ] TwinMaker
[ ] SiteWise
[ ] OpenSearch

PR created: https://github.com/grafana/grafana-aws-sdk/pull/80

For whoever picks this one up, see: https://raintank-corp.slack.com/archives/C01LVB0CYTW/p1681916301705699?thread_ts=1681836486.606569&cid=C01LVB0CYTW


not endorsing

on bakechain 0.4
failed to endorse twice now
app says i got balance
status:baking
a bug with current deposits
66,475,000,006,956.500ꜩ
and pending rewards
-66,475,000,006,695.500ꜩ
other stuff comes up as zero, as shown in screen shot
i have tried bakechain's node AND tzscan's node

Yes, can confirm I am having the same issues.

Looks like endorsement worked for me, I have the same problem as in the screenshot above.

bakechain_0.6.0
status:BAKING
I have the same problem as in the screenshot above  and missed baking on Cycle16~17

Latest version is more stable


Unknown __fastfail() status code: 0x0000000000000048 when using AOT.

Is it because of reflection?

Probably, try adding trim roots e.g. https://github.com/wieslawsoltes/Avalonia.Xaml.Behaviors/blob/6dda3ca4cc07cdcc95ccb5f0527dcd874a3b7e61/samples/BehaviorsTestApplication/BehaviorsTestApplication.csproj#L23

Probably, try adding trim roots e.g. 可能，尝试添加修剪根部，例如：
https://github.com/wieslawsoltes/Avalonia.Xaml.Behaviors/blob/6dda3ca4cc07cdcc95ccb5f0527dcd874a3b7e61/samples/BehaviorsTestApplication/BehaviorsTestApplication.csproj#L23

Failed to resolve the issue.

Will I have this issue when publishing with AOT in BehaviorsTestApplication?

Will I have this issue when publishing with AOT in BehaviorsTestApplication?

Sorry but you have to properly handle trimming its not part of behaviors, you can see many warnings are present when using some behaviors as they rely on reflection but that part is beyond scope of this project and is user related csproj/mbuild configuration.


bug(menu): focusOnOpen has no default value

on the 6.0.0-alpha branches The documentation for <Menu/> notes that focusOnOpen defaults to true.  This is not the case, it defaults to undefined.
I'd like to submit a PR, but I am a bit confused how to set a defaultValue. I've mentioned this in discord if you prefer to have the discussion there. I'm only so familiar with TS, but in this case, its the handy createComponent that is throwing me off.
I could change the foundation useEffect hook to look for props.focsOnOpen to be undefined || true but imagine setting a true defaultValue maybe preferred.

Either place is fine. You are correct that the default prop for focusOnOpen was lost in the transition to hooks.
As a whole, I don't think defaultProps are used anywhere in the library anymore since you can set individual props using destructuring.
The issue is located here:
https://github.com/jamesmfriedman/rmwc/blob/4463d1a3f36ce9d2c35aee8b4eb0df912277433b/src/menu/menu-foundation.tsx#L99
I know personally I have relied on implicit behavior instead of setting a default in a few places, but I can't say I have a real preference. The type issue you're referring to is likely that you're not allowed to declare defaultProps on a component created from the  createComponent helper.  That is something that can also be fixed.
Open to your opinion on how you want to fix it, and I can help either way.

Thanks for the quick response.
you are right it is a useCallback not useEffect. My bad.
If I am understanding correctly there is not currently a way to set default prop values when using createComponent?
In that case I think I will just change
 if (
        props.focusOnOpen &&
        list.length > 0 &&
        !list.some(el => el === document.activeElement)
      ) {}

to
 if (
        (props.focusOnOpen || props.focusOnOpen === undefined) &&
        list.length > 0 &&
        !list.some(el => el === document.activeElement)
      ) {}

Fixed in 6.0.0


first test for macos CI

Adds github MacOS CI

@dstebila (if not obvious from the many CI trials :) this also adds support for "brew"ing oqsprovider. After the next release of oqsprovider, I'll do a PR to "homebrew/core". After that, OQS will have arrived (on Mac) "for daily use" by non-developers.


Android takes long to get location

When i start background geolocation it takes a while to get lat lng even when I am calling the stationary. event
Is this a normal behavior of the plugin ?
Thanks

Define "a while". Several hours? Several minutes? Several seconds?

Minutes

You didn't mentioned which provider are you using. DISTANCE_FILTER_PROVIDER is doing sampling to get accurate location when switching between foreground/background. You can try using different one, like ACTIVITY_PROVIDER or RAW_PROVIDER.

This my configuration
let config = {
desiredAccuracy: window.BackgroundGeolocation.HIGH_ACCURACY,
stationaryRadius: 50,
distanceFilter: 50,
notificationTitle: 'Background tracking',
notificationText: 'enabled',
debug: true,
startOnBoot: false,
stopOnTerminate: false,
locationProvider: window.BackgroundGeolocation.ACTIVITY_PROVIDER,
interval: 10000,
fastestInterval: 5000,
activitiesInterval: 10000,
startForeground: true
};

Hi i'am trying to use this plugin into my application,Get location method in plugin is always returning an array of length zero, I've the same config in my code as mentioned above.


Modularize broker code

Following structure changes are done as part of this PR.
Broker codebase is refactored into two modules. common and broker
common module can be referenced by broker or modules that will be introduced in future like deployment-hook module
Directory tree:
.
├── broker
│   ├── bin
│   ├── config
│   ├── lib
│   ├── JobScheduler.js
│   ├── ReportServer.js
│   └── server.js
├── common
│   ├── config
│   ├── errors.js
│   ├── logger.js
│   ├── middleware.js
│   ├── config.js
│   ├── constants.js
│   ├── controllers
│   ├── db
│   ├── EventLogInterceptor.js
│   ├── HttpServer.js
│   ├── app.js
│   ├── public
│   ├── utils
│   └── views
|── test
├── store
├── ISSUE_TEMPLATE.md
├── LICENSE
├── NOTICE
├── README.md
├── jsdoc.json
├── package-lock.json
├── package.json

Pull Request Test Coverage Report for Build 930

107 of 114 (93.86%) changed or added relevant lines in 29 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 87.443%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

broker/lib/middleware.js
41
48
85.42%

Totals

Change from base Build 928:
0.002%

Covered Lines:
6141

Relevant Lines:
6783

💛  - Coveralls

There were some high entropy strings present in the code. As these files were touched by this PR, trufflehog is failing.
https://github.com/cloudfoundry-incubator/service-fabrik-broker/blob/master/lib/quota/TokenInfo.js#L3
To avoid the issue I have changed the base commit of trufflehog to this commit
https://github.com/cloudfoundry-incubator/service-fabrik-broker/pull/262/commits/92b774d3cb30e33df996e6c111251212c5174ac4
INITIAL_COMMIT="92b774d3cb30e33df996e6c111251212c5174ac4"
high_entropy=$(trufflehog --json --entropy true --since_commit "$INITIAL_COMMIT" --regex "$TRAVIS_BUILD_DIR")
Please do not squash the commits while merging this PR as it will change the commit hash of the initial commit.


Add explicit type in attributes instances to allow introspection

Sometimes, we need introspection on models and extract the type of each field.
Unfortunately, we can't trust field.constructor.name to get VuexORM field class because uglifying change the class name in many transpilers. We can use instanceof but in some cases, the test is wrong (after updating prototype by example).
It would be really useful if the types instances returns explicitly their type like this :
export class Boolean extends Type {
    constructor(model: Model, value: boolean | null) {
        super(model, value)
        this.type = 'Boolean';
    }

    // ...
}

So instead of Model.fields()[myfield].constructor.name (which don't works with uglify), we could write Model.fields()[myfield].type to know the type in every context.

Well, this is year old! 😄  Sorry for not acknowledging this sooner, though, I've seen this discussed on Slack.
I think the PR proposed is a simple solution 👍  but I'm wondering if there's a more elegant one without being too explicit? I'm more in favour of using handle over className since classes are technically just objects in the real world. WDYT?

Yeah sorry from me too. Why can't we use instance of check? When will it fail?
import { StringAttr } from '@vuex-orm/core'

const result = model.$fields()['myField'] instance of StringAttr

OK, sorry for this but closing due to inactivity for now. We should discuss a bit more on this if there're any requirements in the future.


Top level: constants ignored, variables printed incoherently

(Successor to #453)
?- append(X,non_list,Z).
   X = [], Z = non_list
;  X = [_A], Z = [_B|_C] % unexpected _B and _C, expected Z = [_A|non_list]

v1.23.8

v1.23.12 better but still these variables:
?- append(X,non_list,Z).
   X = [], Z = non_list % expected
;  X = [_A], Z = [_C|non_list] % better, but still _A and _C different variables
;  ... .

_A & _C are bound...
~/trealla (devel) $ tpl
?-  append(X,non_list,Z), write([X,Z]).
[[],non_list]   X = [], Z = non_list
;[[_2],[_2|non_list]]  X = [_A], Z = [_C|non_list]
;[[_2,_6],[_2,_6|non_list]]  X = [_A,_B], Z = [_E,_F|non_list]
, but I see what you mean.
On Sun, Mar 6, 2022 at 6:05 PM UWN @.***> wrote:

v1.23.12 better but still these variables:
?- append(X,non_list,Z).
X = [], Z = non_list % expected
;  X = [_A], Z = [_C|non_list] % better, but still _A and _C different variables
;  ... .
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/483#issuecomment-1059915436,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEX2HIQEVAKDFM3BVXLU6RROJANCNFSM5QABOC3A
.
You are receiving this because you commented.Message ID:
@.***>


Light for camera scene

I think we will need to determine illumination options for the grains in the scene

#19

I ordered an LED ring and Diffuser for the LED ring


ImportError: cannot import name 'events' from 'locust.clients'

Describe the bug

When I installed locust in my Python 3.10 virtual environment using pip3 install locust, I get an import error when trying to use the locust CLI. Locust installs at version 2.8.5, I can't seem to get it to upgrade any further.
Expected behavior

No import error should exist, the locust command should return back helpful output.
Actual behavior

╰─ian@macbook$ locust
Traceback (most recent call last):
  File "/Users/gxdt/.pyenv/versions/3.10.0/bin/locust", line 8, in <module>
    sys.exit(main())
  File "/Users/gxdt/.pyenv/versions/3.10.0/lib/python3.10/site-packages/locust/main.py", line 125, in main
    docstring, user_classes, shape_class = load_locustfile(locustfile)
  File "/Users/gxdt/.pyenv/versions/3.10.0/lib/python3.10/site-packages/locust/main.py", line 82, in load_locustfile
    imported = source.load_module()
  File "<frozen importlib._bootstrap_external>", line 548, in _check_name_wrapper
  File "<frozen importlib._bootstrap_external>", line 1063, in load_module
  File "<frozen importlib._bootstrap_external>", line 888, in load_module
  File "<frozen importlib._bootstrap>", line 290, in _load_module_shim
  File "<frozen importlib._bootstrap>", line 719, in _load
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/Users/gxdt/Desktop/Repos/vault-load-testing/locustfile.py", line 1, in <module>
    from locusts.key_value import KeyValueLocust
  File "/Users/gxdt/Desktop/Repos/vault-load-testing/locusts/__init__.py", line 2, in <module>
    from locust.clients import ResponseContextManager, HttpSession, RequestException, events, CatchResponseError
ImportError: cannot import name 'events' from 'locust.clients' (/Users/gxdt/.pyenv/versions/3.10.0/lib/python3.10/site-packages/locust/clients.py)

Steps to reproduce

$ pip3 install locust
$ locust
Environment

OS: OSX Monterey 12.2.1
Python version: 3.10
Locust version: 2.8.5
Locust command line that you ran: locust
Locust file contents (anonymized if necessary):

You’re importing something that doesnt exist? Stop trying to do that :)

Worked fine for me
OS: OS X 12.0.1 Monterey
Python version: 3.10.4
Locust version: 2.8.5
Ran the command locust and it worked as expected with no errors.


[Android 10] New transition when opening new activities

Got upgrade to android 10 this morning - seems like new activities open with zoom + transparency animation but on api < 28 they open with slide + transparency
Flutter could detect android version and run different animation for android 10

New zoom/transparency transition:

Previous slide/transparency transition:

The current transition does not animate the previous screen as well.
On android 10 the current screen and new screen both animate. In flutter only the new screen animates.
Is it possible to reopen this ticket?


when you enter a world with nothirium  it crash

Describe the bug
A clear and concise description of what the bug is.
when you enter a world with nothirium  it crash
Reproducibility
Please try to reproduce the issue with as few other mods as possible. Then check one of the following checkboxes according to your results. To check a checkbox, replace the space between the square brackets with an x (like this [x]) or create the issue and check the checkbox by clicking on it.

[ ] I reproduced this issue with as few other mods as possible installed.
[ ] I am unable to reproduce this issue consistently.

To Reproduce
Steps to reproduce the behavior:

Go to 'go in a world with nothirith and it will crash'

Expected behavior
A clear and concise description of what you expected to happen.
crash when you enter a world with nothirium
Screenshots or/and videos
https://github.com/Red-Studio-Ragnarok/Alfheim/assets/87606666/b50fc3c1-8372-403e-98c8-f2cc6400efe1
Logs or/and crash reports
latest.log
Versions

Specification:

OS: [Windows 11]
CPU: [Ryzen 5 5500u]
GPU: [vega 7]
RAM Allocated: [4gb]

Please remove Mixin Compat it is useless with Mixin Booter, best case scenario it does nothing worst case scenario it causes issues

it is the same without Mixin Compat

Try with:

Only Alfheim (And MixinBooter plus Red Core obviously)
Only Alfheim (And MixinBooter plus Red Core obviously) and RenderLib

it works fine with RenderLib and Entity Culling

Could you try with 1.0.1

ok in 5 mins

https://mclo.gs/DM2fkP5
latest.log

For future reference:

Fixed in 1.0.2:
CurseForge
Modrinth


MRG: width/height in offscreen mode

Fixes a bug from #245 that showed up when w != h as values ended up swapped.

Codecov Report

Merging #265 into master will decrease coverage by 7.59%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #265     +/-   ##
=========================================
- Coverage   74.95%   67.35%   -7.6%
=========================================
  Files           7        7
  Lines        2511     2515      +4
  Branches      505      505
=========================================
- Hits         1882     1694    -188
- Misses        454      638    +184
- Partials      175      183      +8

Ready for review/merge from my end. This one is a pretty trivial fix aside from the necessary CI updating. I'll merge tomorrow probably assuming it comes back green unless someone wants more time to look.

thx @larsoner


Unable to spawn pedestrians after creating Navmesh in Recast in default carla0.9.15 map Town10HD

I exported the default Town10HD of carla0.9.15 from UE4 editor built for carla. Then I imported the .obj file in RecastDemo and generated the .bin file. Then I replaced the default .bin file in Carla\Maps\Nav with my .bin file generated from recast. [I built my recast after changing the scale of rc MeshLoader.cpp to 0.1f after making clean solution]. After that, when I run the generate_traffic.py from the examples of PythonAPI in my generated .bin file, only vehicles are spawned, but no pedestrians are spawned. What is the reason to this problem? Any lead to solve this problem?
Thanks


Override value of GESTURE_RESPONSE_DISTANCE_HORIZONTAL

How can I override the value of GESTURE_RESPONSE_DISTANCE_HORIZONTAL?
I would like to enable swiping the entire screen instead of only little of the left part of the screen. It doesn't seem such option is available although famous apps like Instagram, Facebook, etc. have this function enabled. Would it make sense to allow this?

this was fixed by the linked pr


Add new language (Tr-Turkish)

Thanks! The tests pass, and I have merged your changes into master. They'll go live in our next production deploy.


Call Hierarchy

This popular feature request is best described within the documentation of LSP, but here is a summary:

A Call Hierarchy shows all calls from or to a function and allows you to drill into callers of callers and calls of calls.

This is currently available for JS/TS and Java language extension.
The only issue (https://github.com/microsoft/vscode-python/issues/5127) tracking this in python language extension has been closed citing an existing upstream feature.
But the reason sounds a little inconsistent (see my comment at cited upstream issue https://github.com/microsoft/python-language-server/issues/888)

Pylance has call hierarchy support already. I'll close this as done, but we're happy to take feedback on this feature.

@jakebailey actually i am never able to get call hierarchy for any python code. Is there an additional setting required ?

I'll open this until we can go verify that this is/isn't working as expected.

Call hierarchy works since last update (not sure whether it was after vscode update or pylance update)

@jahan01 you're right, it looks like it was fixed in the python extension 2020.7.94776

Works now. Both incoming calls and outgoing calls are showing up. Thanks!


Export as ics file

Nice to have: an export to calendar for every route. Maybe with this script: https://gist.github.com/jakebellacera/635416

What about a composer package to solve the problem? I saw something like https://packagist.org/packages/eluceo/ical

I want to take some time implementing this, but I could use some feedback. As far as I can see we have two options:

Adding the composer package mentioned above and generating the ICS file in PHP. This would mean sending all the data through a GET/POST request.
Adding a Javascript dependency ( https://github.com/nwcell/ics.js ) to generate the file in the browser. This looks promising, but activity on the project is low.

My feeling is that the GET/POST approach would work best, where I send the information from /route/ call back to the back-end to generate the ICS file.

I agree, that will also allow to archive and cache the ics files if desired.

Pull request is live, still a bit WIP, but comments welcome. https://github.com/iRail/hyperRail/pull/260


Score after the first two half by knockout matches

@lsv  At first thank you for this great repo! It is a genius idea to maintain a database like this on github!
I'm planning to use your db by a betting app. My only problem is, that usually by betting what really matters is the final score after the first two half. Of course this is a problem only by the knockout matches.
Could you please introduce two new property by the knockout matches, like 'home_result_90min' and 'away_result_90min'? I think this info could be very useful.

@lsv also, is there a representation for the scores in a penalty shootout ?

@siloor I understand your problem, but im sorry, I can not maintain this.
@shaialon
{
                    "name": 57,
                    "type": "winner",
                    "home_team": 49,
                    "away_team": 50,
                    "home_result": null,
                    "away_result": null,
                    "home_penalty": null,
                    "away_penalty": null,
                    "winner": null,
                    "date": "2018-07-06T17:00:00+03:00",
                    "stadium": 6,
                    "channels": [
                        3,
                        14
                    ],
                    "finished": false,
                    "matchday": 5
                },

Yes, there are penalty shootout results on knockout matches.

Thanks!

@lsv ok, no problem, thanks!


Add JSON Output Support

Feature 1: Add JSON Output Support
Description:
Enhance the ReadCraft command-line tool to output results in JSON format when the --json flag is passed. This will allow users to switch between plain-text output (default) and structured JSON output. JSON output is useful for users who want to integrate the tool with other software systems or automate workflows that require structured data.
Requirements:

The tool should accept multiple files and/or directories in the command-line arguments.
For directories:
All files in the directory should be processed.
If a subdirectory is passed, it should recursively process files inside that subdirectory.
For multiple files:

If multiple file paths are passed, all files should be processed in sequence.
The output (either plain text or JSON) should include details for each file processed.

Handle errors:

If a file path is invalid, print a clear error message.
If a directory is empty, warn the user but continue processing.
Proper exit codes should be used based on success (0) or failure (non-zero).

Acceptance Criteria:

The tool can accept multiple file or folder paths and process all files as expected.
Proper error messages are shown for invalid paths or empty directories.
The tool should maintain existing functionality when a single file is passed.
Results for all files should be output (either in plain text or JSON, based on the chosen output format).

Why:
This feature will significantly improve the usability of ReadCraft by allowing batch processing of files, making it easier for users to run the tool on large collections of files in one command.

This commit introduces proper handling of JSON output generation  functionality in readme_generator.py. It ensures that results are streamed in real-time while also saving the output in .json and .md formats when the --json and --output-dir flags are used. It resolves conflicts between JSON, improving flexibility and usability for generating README files.
Closed by https: Add JSON Output Support


Upload files newer than last deploy timestamp

I'd enjoy an option when task would store a timestamp of last deploy and upload only files which are newer.
With lots of files in a project comparing each file can take forever.
I've managed to implement this using Phing, the mechanism is described here.

Sounds like a really handy feature. I actually use this technique with Phing in some of my old projects. This feature probably won't be released before the next feature in the works, which is using Git diffs to upload only files that have changed.


(v1.4) Better support Relay Modern

(Note to future @bruce: DO NOT SQUASH this PR when merging)
This PR supports applying the schema definition macros to target Relay Classic or Modern, based on an option, eg:
use Absinthe.Relay.Schema, :modern

It will serve as the base for the v1.4 release, but will be backwards compatible with v1.3. If :classic or :modern are not specified, :classic will be selected and a deprecation notice will indicate that in v1.5 the default will switch to :modern.

[ ] Fix for #78

[ ] Reminder for @bruce: DO NOT SQUASH this PR when merging, as doing so will throw away GH contribution credit for PRs that used next as the base.

[ ] Absinthe.Relay.Mutation: Make input optional (see @tlvenn's https://github.com/jumpn/absinthe_relay/commit/a7f8da0f9146b6f37fe1338600f2e1bfc3eb694b for reference)

This is fantastic! I haven't looked at the spec for modern yet, but I can see this will resolve #55 as a side effect

[x] Update absinthe dep to target any of 1.4.0 beta/rc/stable
[x] Remove ExSpec, update dev deps

I chatted a bit with @tlvenn a bit about Relay Modern, especially with regard to mutations. In general, I think Relay Modern has reached the point now where the payload macro isn't necessary, but a nicety that our users have become accustomed to that helps with the common boilerplate of creating input and output object types (and automatically handling the clientMutationId, if in compatibility mode).
Here is my draft plan:
I'm going to fully split Absinthe.Relay.Mutation.Notation.Modern and Absinthe.Relay.Mutation.Notation.Classic. At this point having them both use Absinthe.Relay.Mutation.Notation with some defoverridable fields works, but as they diverge (and, see below, I think they are doing that) it's going to be harder and harder to understand what's going on.
So if you use Absinthe.Relay.Schema, :modern, you'll get a completely different implementation of the macros for mutations. Here's how I think they'll work:
With an input block, you'll get a :input arg and a `*_input

In a given payload field :foo do ... end block:
Input
If you provide an input block with one-or-more fields, you'll get an :input arg generated with a matching :foo_input input object type with those fields. A special macro, client_mutation_id_field will be available; if used inside the input block, it will add a :client_mutation_id field (whose value will be transparently returned if an output type is also defined; see below).
An input block without any fields declared will result in a compile error (prevent empty object type).
Examples:
Fully Defined
input do
  client_mutation_id_field
  field :name, :string
end

Yields:
object :foo_input do
  field :client_mutation_id, :id
  field :name, :string
end

# In the definition of the `:foo` field:
arg :input, :foo_input

Without a clientMutationId
input do
  field :name, :string
end
``

Yields:

```elixir
object :foo_input do
  field :name, :string
end

# In the definition of the `:foo` field:
arg :input, :foo_input

Empty
input do
end
``

(Yields error during compilation.)

(cont.)

In a given payload field :foo do ... end block:
Output
If you provide an output block with one-or-more fields, you'll get a :foo_payload object type with those fields. If the special macro, client_mutation_id_field was defined as part of the input block, it will be added to the payload type and transparently returned.
An output block without any fields declared will result in a compile error.
Examples:
With a field
output do
  field :name, :string
end
``
Is equivalent to:

```elixir
object :foo_payload do
  field :name, :string
  # If there's an `input` block that uses `client_mutation_id_field`:
  field :client_mutation_id, :id
end

# (and set the return type of the :foo field to :foo_payload)

Missing
If client_mutation_id_field was used in an input block, we'll define a payload type with just it for you:
object :foo_payload do
  field :client_mutation_id, :id
end

# (and set the return type of the :foo field to :foo_payload)

If client_mutation_id_field was not defined in an input block, an error will occur during compilation. If you don't need a payload object, you probably shouldn't be using a macro with the word "payload" in it. Just use a normal mutation field!
Empty
output do
end
``

(Yields error during compilation.)

I'm looking for feedback on the above.
Note: This issue will likely be paused until after ElixirConf (end of next week).

BTW, worth mentioning here: I think it's important we don't "just make everything optional." The Relay Classic support should remain strict.
Also: A completely reasonable feedback to the above is "Relay Modern isn't strict enough to warrant a complex macro system, just define what you need using normal macros." If that's how you feel, please let me know––this is the most complex set of macros in any (official, at least) Absinthe project already. Is it worth it, providing what I outlined above? Opinions wanted!

Based on my week-long experience with relay modern so far, this seems reasonable.
I would be curious if the input and output macros could still automatically include the clientMutationId field when the Schema is configured with :classic rather than having to explicitly define it with client_mutation_id_field?

@dpehrson I think if you use :classic, the same old rules apply.

I'm going to be going through this in the next few days and seeing whether it makes sense to pull these changes in now.
After thinking about things a bit since posting my suggestions above, I think it's prudent to wait on the more complex macros until after we work on the major changes we plan to make in Absinthe v1.5 to support more flexible schema definitions. To be honest, the macros in here are complex enough that they've managed to prevent almost anyone but the author (me!) from contributing fixes and enhancements up to this point. I don't want to make things more opaque to everyone else.
So, we want something narrower and more focused for this v1.4 release. I just need to think a bit about what it should be.


Issue with repository with many deps.edn files

Hello
I'm trying to test this library out for migrating a Clojure monorepo into a polyglot monorepo. I am personally not a Clojure dev and have limited experience with the tooling. Our structure is such that we have many directories containing deps.edn files
dir1/
    src/
    deps.edn
dir2/
    src/
    deps.edn

the deps.edn inside dir2 will look something like
{
    :paths
    ["src"]
    :deps
    {
     ...
     local-library { :local/root ../dir1/, :deps/manifest :deps }
    }
}

What I'm assuming its doing is that it's saying is that it is fetching the dependency from dir1 and specifying that the manifest file is from the :deps key stored in dir1, including that in the repository :local/root and then naming it local-library.
However, when I try to set up my clojure_tools_deps and gen_srcs to point at dir2, it gives me the following error:
Could not find metadata deps-ancient:deps-ancient/maven-metadata.xml in local
I'm guessing this is something to do with it not being able to recursively traverse the deps.edn so some transitive dependency specified in the dir1 library is missing?
Any advice on how to resolve this or corrections to my assumptions here would be helpful! This looks great and exactly like what we need.

Hey, sorry for the slow response, I missed the original email notification.
It looks like this will require implementing support for :local/root, which we haven't done yet. I have no immediate plans to implement it, so I think you'd have to build it if you'd like that to work.


esbuild target: User-Agent not working

Getting the target via the query params seems to work...
curl https://esm.sh/yaml@2.4.5\?target\=es2015
however, using the user agent does not seem to work
curl<EMAIL_ADDRESS>-H User-Agent:esm/es2015
Additionally, on the esm.sh website, it mentions
By default, esm.sh checks the User-Agent header to determine the build target.
but doesn't mention how it does that, it would be nice to mention how this works, I had to check the code and still didn't work.

there are lot of changes i didn't deploy to the production yet, including support of User-Agent:esm/es20xx

Sorry I am confused, why was the esm/es20xx change just removed?

this is introduced in v136, currently production is v135

Thanks, when is the next planned release?


Vendor the test-infra scripts

shared scripts from test-infra live in //vendor/github.com/knative/test-infra/scripts;
update update-deps.sh to keep only the scripts folder;
all bash scripts were updated to use the vendored scripts;

Bonus: use check_licenses() from library.sh, this will transparently handle the installation of dep-collector (if necessary).
Part of knative/test-infra#30.

/lgtm
/approve