populate contacts field for other formats

Description
in #808 a new database field contacts has been introduced, the field is currently only populated from iso records, this item aims to extend the load functionality so other formats such as DC, WMS, ... also are enabled to populate the contact field

Thanks @pvgenuchten.  Suggest that the internal model of this object be modelled after https://github.com/opengeospatial/ogcapi-records/blob/master/core/openapi/schemas/party.yaml as a rule.  This would mean:

all contacts populated to pycsw:Contacts would be OARec compliant
any "returnable" using pycsw:Contacts would be able to parse and serialize based off OARec

I'm happy to implement this if folks agree.  Thoughts?  cc @kalxas

+1

I’m neutral on the model used, would be helpful if all tools use similar model (pygeometa, owslib, pycsw), I can prepare the pr


zpool: Make handles extern for better C interop

I found myself wanting to return handles from exported functions for FFI use. I think it makes sense to make handles extern to make this easier, since handles are just a wrapped integer anyways.
(There shouldn't be any performance penalty doing this, right?)

Yes, this is a very good idea. There won't be any additional performance cost. Thanks!


Install on aws beanstalk

I'm trying to deploy on aws beanstalk with https://github.com/npcode/mattermost-docker/blob/next/Dockerrun.aws.json but failed with this error:
Update environment operation is complete, but with errors. For more information, see troubleshooting documentation.

I tried it again but it still not work. The database seems not to start.
Here is the log of the db container:
-------------------------------------
/var/log/containers/db-9b074b96866c-stdouterr.log
-------------------------------------
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
creating template1 database in /var/lib/postgresql/data/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating collations ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
loading PL/pgSQL server-side language ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
syncing data to disk ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    postgres -D /var/lib/postgresql/data
or
    pg_ctl -D /var/lib/postgresql/data -l logfile start

****************************************************
WARNING: No password has been set for the database.
         This will allow anyone with access to the
         Postgres port to access your database. In
         Docker's default configuration, this is
         effectively any other container on the same
         system.

         Use "-e POSTGRES_PASSWORD=password" to set
         it in "docker run".
****************************************************
waiting for server to start....LOG:  database system was shut down at 2016-04-12 19:22:01 UTC
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
 done
server started
ALTER ROLE

/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/make_db.sh
CREATE DATABASE
CREATE ROLE
GRANT

LOG:  received fast shutdown request
LOG:  aborting any active transactions
LOG:  autovacuum launcher shutting down
LOG:  shutting down
waiting for server to shut down....LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

LOG:  database system was shut down at 2016-04-12 19:22:05 UTC
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  incomplete startup packet
LOG:  received smart shutdown request
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down

Well, this might not be a problem of db. eb local run displays errors of app and I think this is the culprit.
app_1 | Starting platform
app_1 | [10:51:48 UTC 2016/04/24] [INFO] (github.com/mattermost/platform/utils.GetTranslationsBySystemLocale:52) Loaded system translations for 'en' from '/mattermost/i18n/en.json'
app_1 | [2016/04/24 10:51:48 UTC] [INFO] Current version is 2.1.0 (2.1.0/Mon Mar 14 20:45:23 UTC 2016/f189bc2073cf800c5f4506a69bdb51d7065269bf)
app_1 | [2016/04/24 10:51:48 UTC] [INFO] Enterprise Enabled: false
app_1 | [2016/04/24 10:51:48 UTC] [INFO] Current working directory is /mattermost/bin
app_1 | [2016/04/24 10:51:48 UTC] [INFO] Loaded config file from /mattermost/config/config.json
app_1 | [2016/04/24 10:51:48 UTC] [INFO] Server is initializing...
app_1 | [2016/04/24 10:51:48 UTC] [INFO] Pinging sql master database
app_1 | [2016/04/24 10:51:48 UTC] [CRIT] Failed to ping db err:dial tcp: lookup dockerhost on <IP_ADDRESS>:53: no such host
app_1 | panic: Failed to open sql connection dial tcp: lookup dockerhost on <IP_ADDRESS>:53: no such host
app_1 |
app_1 | goroutine 1 [running]:
app_1 | panic(0xb2e0c0, 0xc82041c450)
app_1 |  /usr/local/go/src/runtime/panic.go:464 +0x3e6
app_1 | github.com/mattermost/platform/store.setupConnection(0xd40f40, 0x6, 0xc820432348, 0x5, 0xc82047b9a0, 0x48, 0xa, 0xa, 0xc8203be000, 0x0)
app_1 |  /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:169 +0x894
app_1 | github.com/mattermost/platform/store.NewSqlStore(0x0, 0x0)
app_1 |  /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:61 +0x122
app_1 | github.com/mattermost/platform/api.NewServer()
app_1 |  /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/api/server.go:35 +0xe8
app_1 | main.main()
app_1 |  /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:67 +0x756

Now I can reproduce this with docker-compose.yml in my local machine. This problem occurs when I remove 'volumes' option in docker-compose.yml

Fixed by 1b1dc3c79b6bd559298cd2da2100c4bfb49eeb2c.


Add optional tool param "properties" to adhere to OpenAI spec

Prior, I was unable to have a tool param with type "array" because OpenAI spec requires items={"type": "str"} property to be set. This solution adds the option to specify any optional parameters to pass to the actual API. May also be useful for flexibility in working with different providers.
Very open for feedback on how this should be tackled.
This PR contains:

[x] New features
[ ] Changes to dev-tools e.g. CI config / github tooling
[ ] Docs
[ ] Bug fixes
[ ] Code refactor

What is the current behavior? (You can also link to an open issue here)
Cannot have a list as the type of my toolparam since it doesn't adhere to OpenAI API spec.
What is the new behavior?
By setting optional properties you can override this behaviour
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information:
This solution may not be optimal. Probably it could be nicer to have a specific property for this

Thanks! Would like get this in but need to think about how it might affect other providers that also consume the same JSON schema. Will do some additional research/experimentation then revert back.

Took a closer look at this and what I think I'd like to do is generally extend our tool use / docstring handling to support arrays (then you wouldn't need a special field here, we would just do the right thing when seeing a Python list). Will likely work on this soon and post an update here once we have one.

Sounds good, thanks for looking at this!

@aisi-inspect Is there any update on this? Should I open up an issue to be able to track this better?

This issue should cover it: https://github.com/UKGovernmentBEIS/inspect_ai/issues/97
We will introduce richer typing (arrays, objects, etc.) fairly soon.

FYI there is work in progress on this here: https://github.com/UKGovernmentBEIS/inspect_ai/tree/feature/tool-json-schema
Should be merged within the next few days.

Resolved with https://github.com/UKGovernmentBEIS/inspect_ai/pull/158


fix meta-features extraction without dataset cache

Made dataset data unnecessary for PymfeExtractor
Improved corresponding test to avoid this behavior

Hello @MorrisNein! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file meta_automl/data_preparation/datasets_loaders/custom_datasets_loader.py:

Line 5:1: F401 'meta_automl.data_preparation.dataset.DatasetBase' imported but unused

In the file meta_automl/data_preparation/meta_features_extractors/pymfe_extractor.py:

Line 15:1: F401 'json' imported but unused


[Hexagon] Deprecate SDK 3.x, rewrite HexagonSDK.cmake

Avoid setting global state, instead implement get_hexagon_sdk_property, which will set a user-provided variable to the value of the requested property.

cc: @masahi


NameError: name 'load_lua' is not defined

Thanks for your wonderful work. I ran train.py but I meet an error. NameError: name 'load_lua' is not defined. The version of torch is 1.7.1.

There was another error when I  repalced load_lua with torchfile.load.
struct.error: unpack requires a buffer of 4 bytes.

Sorry for that. We have modified the code (i.e., model.py and network.py). Please update them, and it should be working now.

Thank you for your reply  quickly. Yes , it works now.

感谢您的出色工作。我跑 train.py 但遇到了错误。名称错误： 未定义名称“load_lua”。火炬的版本是 1.7.1。

Hello, I currently encountered the same problem while running this code. How did you resolve it at that time? Torch version 1.4.0


Use the base directory of the scripts

example
other/dir $ gl
./gl: line 1: git-log: command not found

Use $PATH


Provides more configurable per environment config.php

Hi!
i would be great to have option to configure ADLDAP per environment. This is code, that i use now in multiple instances.
Thanks!

Thanks @profak!

@stevebauman, hooray! Thanks!


Installing not yet used packages

go version go1.8 linux/amd64
I was starting a new project and decided to give dep a whirl, so this experience is from my first moments with the tool
I started with a noop main.go, ran dep init which produced an empty lock/manifest which seemed about right, then attempted dep ensure github.com/gorilla/mux which gave an error of sorts, with no packages being added to vendor/
dep: No constraint or alternate source specified for "github.com/gorilla/mux", omitting from manifest

So I attempted to manually specify a constraint: dep ensure<EMAIL_ADDRESS>which gave no output but did add the dependency to the manifest. However no packages were added to vendor or the lock file.
With a bit of trial and error I found that I have to use the package in my project before it exists to have dep install it.
The main reason I want to install a package first as it allows editors to provide code completion, but it's also just habit from other tools/languages (npm, cargo, glide etc)

Thanks for trying dep, and for providing the feedback!
Yeah, we've been back and forth over this quite a lot. I honestly can't even remember where we've landed right now.
There's an existing mechanism by which we could accomplish the outcome you want pretty easily - see #36. The question has mostly about whether we can do it in a way that won't have weird gotchas for folks, and that won't make the command set awkward, or have the same literal command have drastically different behavior depending on disk state.
It should be easier to do this under the new approach to the command set we're taking. That's being discussed in #277.

#489 brought us dep ensure -add, so this is now addressed!


feat: recognize amazon linux 2 and 2023

It seems serialized-size byte tests are failing both here and in main.
I am not sure if it depends on my arch building protobuf or some other changes. If anyone else can replicate the green test or the failing it would be extremely helpful

Tests are failing because a new tag adds size to the metric!


Feature/wb50

Updated DELETE /collection/{id} route to not delete attack objects which are in another collection
Added DELETE /collection/{id}/modified/{modified} to delete a collection by id and version

It looks good overall. I have one edge case that needs to be addressed. Plus a couple stylistic things that aren't crucial, but are probably worth doing to keep the code base consistent.
The edge case is when deleting a particular version of a collection with the deleteAllContents=true parameter set. In this situation, the code deletes the objects in the contents of the collection, even if they're still referenced by another version of the same collection. That leaves the remaining version of the collection with dangling references.
Stylistically, there are two things I noticed. The first is the 2 space vs 4 space indentation. I don't have a preference on that, except that I think the code is generally a little easier to read if the indentation is consistent, especially within a file. The second is the way of iterating over a collection. Instead of using for (let i = 0; i < coll.length; i++) the rest of the code uses for (const attackObject of objectList). It's a little more succinct and I think it conveys the intent better.

It looks like there's still a problem with deleting the contents when deleting a single version of a collection. I think the issue is that MongoDB uses an implicit AND between query terms. So when modified is set, it's looking for collections that has a different value for stix.id AND a different value for stix.modified. Which will exclude other versions of the same collection.
I pushed a couple of additional test cases that might make it easier to check if things are working the way you want them to.

Thanks for finding that @ElJocko .  npm run test ran with no errors


[Dependencies] Bump go and cosmos-sdk

Summary
Bumps golang and cosmos sdk to the latest versions.
Issue

Discovered that the latest cosmovisor needs a newer go version in #796

Type of change
Select one or more from the following:

[ ] New feature, functionality or library
[ ] Consensus breaking; add the consensus-breaking label if so. See #791 for details
[ ] Bug fix
[x] Code health or cleanup
[ ] Documentation
[ ] Other (specify)

Testing

[ ] Documentation: make docusaurus_start; only needed if you make doc changes
[ ] Unit Tests: make go_develop_and_test
[x] LocalNet E2E Tests: make test_e2e
[x] DevNet E2E Tests: Add the devnet-test-e2e label to the PR.

Sanity Checklist

[ ] I have tested my changes using the available tooling
[ ] I have commented my code
[ ] I have performed a self-review of my own code; both comments & source code
[ ] I create and reference any new tickets, if applicable
[ ] I have left TODOs throughout the codebase, if applicable

The code changes were done as requested by the linters here. I had to bump the golangci-lint to the newer version, which brought us more linters/checks.


Support [term] configuration in Cargo config.toml for color and logging

Describe your use case
According to the config linked by obi1kenobi here, the base cargo tool supports configuring color and logging in the [term] section of Cargo.toml config.toml.  As an extension to cargo, it makes sense to allow these values to configure cargo-semver-checks as well, if set.
Describe the solution you'd like
cargo-semver-checks reads the configuration from the [term] section of config.toml to configure color and logging level if they are set.  We would have to set precedence rules between this, env vars like CARGO_TERM_COLOR and CARGO_TERM_QUIET, and config flags like --color and --verbose, and it would make sense to follow the same rules that cargo does.
Alternatives, if applicable
No response
Additional Context
I can work on implementing this if it seems like something we want.

I think these are settings in config.toml not Cargo.toml.
Right now they are a nice to have, similar to the anstyle migration. If this feature is added, most people won't notice, a few will be happy, and nobody will object. That's great, and if you're excited to work on it — I'm happy to support you in that.
We have many other work items with higher impact: writing new lints, resolving some false-positives, improving the use of cargo-semver-checks in large workspaces (along the lines of #600), and of course all the GSoC project ideas.
If you are optimizing for positive community-wide impact per time spent, I'd be happy to suggest a few concrete things you could take a look at. If you are excited about this feature specifically, I'm all in favor and happy to support you here.

I think these are settings in config.toml not Cargo.toml.
oops, fixed.

If you are optimizing for positive community-wide impact per time spent, I'd be happy to suggest a few concrete things you could take a look at. If you are excited about this feature specifically, I'm all in favor and happy to support you here.
I just saw this and wanted to note it as something we could work on.  I can definitely do this, but I can definitely work on more of the higher-priority items that you had in mind.  What were you thinking of?

If you're interested in chasing down and fixing some false positives, #727 is great. False-positives in general are very high-priority items because they erode users' trust in cargo-semver-checks.
Improving user-facing error messages are also generally important, since they help onboard new users more effectively while also decreasing maintainers' support burden: the more users can figure out how to do themselves, the fewer questions they'll need to ask about it. #723 is great low-hanging fruit here, and there are likely more in the issue tracker.
Decreasing maintainer burden and improving efficiency is also always great. #665 is a good example.
The work on #600 itself will be a long arc (probably a month or two), but you could help make a big dent in that timeline by augmenting our test suite to include test cases for each of the edge cases mentioned in #600. Roughly, half the work there is design & implementation, and the other half is making sure we have in fact actually solved the problem and won't accidentally break it again in the future. PRs reproducing each problem in test cases would be very helpful for that!
All of these have natural stopping points along the way, which is nice in case you have classwork or other responsibilities that come up. You'll be able to make impactful contributions steadily and without a large up-front time commitment.


pyinstaller打包pytorch

one.py 只有三行代码，如下：
import torch
a = torch.zeros(2, 3)
print(a)
当我用pyinstaller把 one.py 打包成exe文件后， 运行exe后，出现如下问题：
failed to execute script one
我怀疑这是pytorch框架的问题，因为我打包其它py文件时并未发生类似问题。
我百度和谷歌了，并没有能解决我问题的相应办法。应该怎样解决这个问题呢？

closed due to outdated, feel free to reopen it if you have any problems. Sorry that I was busy in the past half year and did not respond in time.


Creating a Blog Post dumps you to a not-very-helpful page

Description
After writing a blog post, the page you go to is not very useful. I am not sure what the intended page/content to see is (e.g. I cannot create another blog post from this page, I cannot see my other posts).
Screenshots

Files
A list of relevant files for this issue. This will help people navigate the project and offer some clues of where to start.
To Reproduce
Go Home > Blog > New Post
Publish a new post.
Tasks
Include specific tasks in the order they need to be done in. Include links to specific lines of code where the task should happen at.

[ ] Task 1
[ ] Task 2
[ ] Task 3

Remember to use helpful labels and milestones. If you use the "help wanted" label, Code for America will promote it widely.

The page you are seeing is the blog post you just created.
I think it is only confusing for these fake skeleton posts. But it would also make since to go to the index blog page, or new form, with a link in the flash message to the full post page you created. Wither way we should probably make it consistent with projects and events.


[Proposal] PrometheusMetricProvider should be decoupled from specific metric names

Such that an alternative implementation can re-use existing functionality and plug in alternative metric names then.

Closed by https://github.com/bakdata/streams-explorer/pull/137


Adding partial keyword to Interfaces generated in ComponentEntityInterfaceGenerator

Hi,
I'm currently using my own version of ComponentEntityInterfaceGenerator class in which the only difference is that it generates a partial interface (so that I'm able to other custom generators).
Since I have to keep up with the possible changes (like the ones made with #591), could you maybe add the partial keyword to the official generator to increase the extensibility for everyone?
Thanks for this awesome ECS framework!
Cheers

Just curious, what is your exact use case. With what do you extend the partial interface?

For now I'm using something like your code gen example in #451.
And I think that in general if your generated interfaces are partial, then we can have more "freedom" in creating custom code generators.
Besides what harm can it make? 😁

OK :)


gdk::content_register_deserializer usage is unclear, and possibly broken

Bug description
I'm not really certain that this is buggy or just completely undocumented and confusing to the point of unusability, but I just cannot get gdk::content_register_deserializer to work.
I've tried all kinds of variations on this code. Calling return_success() or not, setting user_data to Some(mine), even using unsafe to call gdk_content_deserializer_return_success directly (that one made more progress). I've explicitly closed the input stream and not.
    MyType::ensure_type();

    gdk::content_register_deserializer(
        SPECIAL,
        MyType::static_type(),
        |deserializer, user_data: &mut Option<MyType>| {
            let mine = MyType::default();

            deserializer.set_value(mine.into());
            deserializer.return_success();
        },
    );

If I understand it right, this simple code should just unconditionally "deserialize" the default value, but it just throws warnings and the corresponding display.clipboard().read_value_async never calls its callback.
Looking at nautilus code, since i couldn't find any rust usages of register_deserializer, I see it ends with the same two calls and I cannot figure out what I'm doing differently, and throughout the day I've tried code almost identical to Nautilus' code just to try to figure out what is going on.  From nautilus-clipboard.c which I was using as a reference.
    g_value_set_boxed (gdk_content_deserializer_get_value (deserializer), clip);
    gdk_content_deserializer_return_success (deserializer);

Backtrace
Really it mostly just throws warnings and does nothing, or it segfaults (even without unsafe in my code) depending on how I try to get it to work. I just don't get how deserializer.return_success() can end up with a confused type.
(aw-fm:2614375): Gdk-CRITICAL **: 23:22:51.795: gdk_content_deserialize_finish: assertion 'GDK_IS_CONTENT_DESERIALIZER (result)' failed

(aw-fm:2614375): GLib-GIO-CRITICAL **: 23:22:51.795: g_task_return_error: assertion 'error != NULL' failed

(aw-fm:2614375): GLib-GIO-CRITICAL **: 23:22:51.795: GTask source_tag (source object: 0x55f96b3bc330, source tag: 0x7f2637292cc0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.

(aw-fm:2614375): GLib-GObject-CRITICAL **: 23:22:51.795: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Please provide an easy to run example.

Honestly I think that's part of the problem, there aren't any examples or documentation at all in gtk4-rs and I think I'm probably the first person, period, to ever try using this function. I wasn't able to get any code at all to successfully run to completion. I'll try and make a more minimal example of something that should probably work later, but the example given is already pretty minimal: calling set_value and return_success with some dummy value should be enough.

Here's some code that, to the best of my understanding from reading the GTK docs and Nautilus/Caja code, should work. Assumes you have some text in your clipboard, I've only tested this on X myself. This example segfaults.
It is wrong in that it doesn't close deserializer's input stream, but that shouldn't break anything, not immediately. Reading that requires some additional async mess and doesn't change the eventual crash or failure.
use gtk4::gio::Cancellable;
use gtk4::glib::BoxedAnyObject;
use gtk4::prelude::{ApplicationExt, ApplicationExtManual, DisplayExt, StaticType};
use gtk4::traits::WidgetExt;
use gtk4::{gdk, glib, Application, ApplicationWindow};

fn main() -> glib::ExitCode {
    let app = Application::builder().application_id("org.example.HelloWorld").build();

    app.connect_activate(|app| {
        // We create the main window.
        let window = ApplicationWindow::builder()
            .application(app)
            .default_width(320)
            .default_height(200)
            .title("Hello, World!")
            .build();

        window.set_visible(true);

        gdk::content_register_deserializer(
            "text/plain;charset=utf-8",
            BoxedAnyObject::static_type(),
            |deserializer, user_data: &mut Option<BoxedAnyObject>| {
                println!("Deserializing");
                let boxed = BoxedAnyObject::new("Dummy value");

                deserializer.set_value(boxed.into());
                deserializer.return_success();
            },
        );

        window.display().clipboard().read_value_async(
            BoxedAnyObject::static_type(),
            glib::Priority::DEFAULT,
            Cancellable::NONE,
            move |text| {
                let text = text.unwrap();
                let text = text.get::<BoxedAnyObject>().unwrap();
                let text = text.borrow::<String>();

                println!("Got clipboard contents {text}");
            },
        );
        println!("timeout-done");
    });

    app.run()
}

I do believe the content_register_deserializer is probably wrong. Needs someone to look into it at some point but what is exactly you are trying to achieve? because the code itself doesn't seem to be correct, you are registering a deserializer and then reading the value from clipboard except nothing is set on the clipboard?

Well my ultimate goal is to actually read the contents of the clipboard and deserialize it into my custom type, so that I get cross-platform (at least X and Wayland) clipboard support. The example is very, very obviously just a dummy example that neither reads the contents of the clipboard nor actually deserializes them, it's just a minimal example of API usage that should work in that the deserializer is completed and should produce some value.
See https://gitlab.gnome.org/GNOME/nautilus/-/blob/ffc39891d4692e74b26df26f8ac697bd30882c4c/src/nautilus-clipboard.c#L215 and the referenced functions for something similar to what I was trying to do. I've wasted enough hours trying to get this to work in gtk-rs.


fix: remove-zero-categories observe (fixes #2919)

GitHub Issue (if applicable): #2919
Trello Link (if applicable):
Explanation of Bugfix/Feature/Modification:
For some reason, this specific modal isn't getting hooked into. Doing some observation instead.

How are you handling the guard option from addToolkitEmberHook in this PR? I think it should still be involved somewhere, right?

How are you handling the guard option from addToolkitEmberHook in this PR? I think it should still be involved somewhere, right?

You're totally right, forgot this dropdown was used elsewhere. Will figure out a solution.

How are you handling the guard option from addToolkitEmberHook in this PR? I think it should still be involved somewhere, right?

You're totally right, forgot this dropdown was used elsewhere. Will figure out a solution.

Never mind, this already works as implemented as https://github.com/williammck/toolkit-for-ynab/blob/90398b3fe91e8f3c94d9cd2274806a75a46c6c4d/src/extension/features/budget/remove-zero-categories/index.js#L18 has .modal-budget-overspending in the selector.

Gotcha! Thanks for checking!


Unable to compile under VS

I'm trying to replace std::string with utf8string. But some problem occurs:

at line 4336 in tinyutf8.h,  gives error C4146 unary minus operator applied to unsigned type, result still unsigned
afteri tried fixing the previous problem another occurs: C4703 potentially uninitialized local pointer variable 'app_lut_base_ptr' used	tinyutf8.h	3134
also there are about 70 warnings. Could you fix them all?
some operators are not overloaded as in std::string:

operator+=(char )
operator+(const char*, string)

I am using VS2019, and c++ standard is 17, warning level is 4

Hi There!,
Concerning the error, I will try to fix that one as soon as I have the time to, I guess within the next few days 😃 Same goes for operator+= overloads.
Could you paste your compilation output into this issue? THis way, I can understand the issues better and make sure I fix all errors in the first place, so you can start working.
All the Best,
Jakob

Did you get my message?


Add a pruning mechanism for events

Parent Issue
#718

We need to wait until we define precisely the scope of the events that we want to store before we decide of a pruning mechanism and rules.
Currently, we are planning for 3000x365/5=~220K events per year, which is very low: the pruning is not even mandatory now.


AUC util funcs div by zero errors

pdstools version checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pdstools.

Issue description
For real-life datamart data we sometimes encounter div by zero errors in the AUC calculation methods.
/Users/perdo/Library/Python/3.12/lib/python/site-packages/pdstools/utils/cdh_utils.py:362: RuntimeWarning: invalid value encountered in divide
probs = pos / (pos + neg)
/Users/perdo/Library/Python/3.12/lib/python/site-packages/pdstools/utils/cdh_utils.py:365: RuntimeWarning: invalid value encountered in divide
FPR = np.cumsum(neg[binorder]) / np.sum(neg)
/Users/perdo/Library/Python/3.12/lib/python/site-packages/pdstools/utils/cdh_utils.py:366: RuntimeWarning: invalid value encountered in divide
TPR = np.cumsum(pos[binorder]) / np.sum(pos)
Reproducible example
pos = np.asarray(pos)
    neg = np.asarray(neg)
    if probs is None:
        probs = pos / (pos + neg)

    binorder = np.argsort(probs)[::-1]
    FPR = np.cumsum(neg[binorder]) / np.sum(neg)
    TPR = np.cumsum(pos[binorder]) / np.sum(pos)

    Area = (np.diff(FPR, prepend=0)) * (TPR + np.insert(np.roll(TPR, 1)[1:], 0, 0)) / 2
    return safe_range_auc(np.sum(Area))

Expected behavior
No errors. Method should be protecting against zero divide. Not by adding a 1 or 0.5 but we can probably detect and skip - need to double check the algorithm. It's probably both the auc_from_bincounts and aucpr_from_bincounts, which are very similar.
Installed versions

Replace this line with the output of---Version info---
pdstools: 3.4.4
Platform: macOS-14.6.1-arm64-arm-64bit
Python: 3.12.3 (v3.12.3:f6650f9ad7, Apr  9 2024, 08:18:47) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]

---Dependencies---
plotly: 5.22.0
requests: 2.32.3
pydot: 2.0.0
polars: 0.20.31
pyarrow: 16.1.0
tqdm: 4.66.4
pyyaml: <not installed>
aioboto3: 13.0.1

---Streamlit app dependencies---
streamlit: 1.38.0
quarto: <not installed>
papermill: 2.6.0
itables: <not installed>
pandas: 2.2.2
jinja2: 3.1.4
xlsxwriter: 3.2.0), leave the backticks in place

Think you could squeeze this in for #260 @operdeck ?


Reduce the size of the cosine table

I picked the most naive way of implementing the cosine table to get something working and compare with the soft float impl. It takes an absurd amount of space so it'd be good to get it down to 1/4 of its size or less. There could also be a build parameter (env var or otherwise) to set the precision (or size) which is why I generated it from build.rs in the first place.

Got the cosine table down from 128KB to 32KB. I should add a build-time option for generating lower-precision 4/8/16KB tables that interpolate the missing values.

Cosine table is now down to 16KB with an option for a higher-precision 32KB version with cargo psx run --cargo-args "features psx/hi_prec_trig". The 16KB table is a u8 array so to go any smaller I'll need to make a smaller table.

I removed the trig functions in the latest crate rewrite so I'm closing this for now.


Async validators and Observable?

I'm submitting a ...
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[x] support request

Can I use async validators with service which returns observable (regular angular service based on Observable)? How to correctly handle the http response?

@aitboudad
I remember reading about useFactory and how to use one example
    { provide: FORMLY_CONFIG, multi: true, useFactory: uniqueUsernameValidationConfig, deps: [RegistrationService] },
Never would of crossed my mind this is how you would pass service.... you are amazing. How do you remember all those kind of things?

Never would of crossed my mind this is how you would pass service.... you are amazing. How do you remember all those kind of things?

I'm just trying to find a solution :smile:,
IMO it's not about remembering but how much you've played with the knowledge you've learned.


Fix compilation of arm protected build

Correct typos in include/nuttx/arch.h and suppress
"'noreturn' function does return" warning coming from arm_pthread_exit.c
Signed-off-by: Jukka Laitinen<EMAIL_ADDRESS>Summary
Arm protected build didn't compile for me any more.
Impact
This fixes the issue
Testing
Tested of STM32F765 (Pixhawk 4)

Fixed the same warning also on risc-v with this same PR


CRITICAL: [Actionable Whisper] [$250] After selection an option for a tracked expense, the LHN still shows 'What would you like to do with this expense?'

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.67-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Action Performed:

Track an expense
Select any of the actionable whisper options
One done, the actionable whisper and the tracked expense should no longer be in the self-DM

Expected Result:
Describe what you think should've happened
The LHN should no longer show 'What would you like to do with this expense?', and instead whatever occurred last in the self-DM
Actual Result:
Describe what actually happened
The LHN still shows 'What would you like to do with this expense?'
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Start a chat with the user first, before performing the steps
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/30609178/c59cec39-3230-45af-8c65-d97bb9ae87d4

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b488eb6e01215bbc
Upwork Job ID:<PHONE_NUMBER>358557184
Last Price Increase: 2024-04-30

This is likely an internal / external issue.
When we dismiss the actionable whisper, the BE should send an updated lastMessageText to the client. Additionally, there should be an optimistic update on the FE when this happens as well. When the "Dismiss for now" option is selected, it seems to work properly

@thienlnam if this is an internal / external, should I mark it as such so we get proposals for the external piece?

pending further discussion

Let me double check to confirm my theory first, but yeah we can after that

Yup, looks like this is correct - we'll need to do something optimistically and on the BE as well

Awaiting proposals

Bumped in slack for proposals

Proposal
Please re-state the problem that we are trying to solve in this issue.
After selection an option for a tracked expense, the LHN still shows 'What would you like to do with this expense?
What is the root cause of that problem?
Here last reportLastMessageText will be What would you like to do with this expense?
https://github.com/Expensify/App/blob/f851f575ef433c0a87cac2c6cf20951483887566/src/libs/actions/IOU.ts#L1478-L1479
What changes do you think we should make in order to solve the problem?

Here we are hiding these actions we should also add !isActionableTrackExpense(reportAction)
https://github.com/Expensify/App/blob/f851f575ef433c0a87cac2c6cf20951483887566/src/libs/ReportActionsUtils.ts#L556-L572
What alternative solutions did you explore? (Optional)

What's the next step here, and who is doing it?  When?

We have the whisper in the sortedVisibleReportActions even after resolution but it is not displayed as a report action in the report screen because of this here
https://github.com/Expensify/App/blob/ee8f9c661f269f405a5ae8ba47ea07f42a306c6c/src/pages/home/report/ReportActionItem.tsx#L903-L905
so we should use the same logic for displaying in LHN as well.
So the alternative solution here by @Nodebrute looks good to me.
🎀 👀 🎀 C+ Reviewed

Great!  @Nodebrute what is your ETA?

@quinthar I'll raise a PR today.

I am working on the PR currently testing all cases.

PR in review

@Nodebrute I see there are several bumps for you on the PR. Can you address those asap?

PR still in review

@c3024 please handle BZ so we can issue payment this week

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@c3024] The PR that introduced the bug has been identified. Link to the PR: No particular PR can be held responsible for this. This bug appears due to introduction of the new feature Track Expense. And these whispers as report actions work differently.
[x]  [@c3024] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: NA
[x]  [@c3024] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No discussion was started because this bug cannot be identified in prior.
[x]  [@c3024] Determine if we should create a regression test for this bug. Yes
[x]  [@c3024] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

Track an expense
Select any of the actionable whisper options on the whisper received
Confirm that the LHN of self DM displays the last visible message of the report instead of What would you like to do with this expense? (This might change back to What would you like to do with this expense? after refreshing. That is a separate internal issue and is being fixed here #42727)

@joekaufmanexpensify This is marked as a CRITICAL issue. Is $500 pay applicable for this issue similar to this?

Checking

Confirmed payment is $250 here, since the high priority was not added by the project leader here. There has been some confusion on this, but it was clarified in Slack several days ago that the intent of the price doubling is to be specifically when  a project leader adds this label to the issue, not based on the status of the issue in the linked GH project.

All set to issue payment. We need to pay:

@Nodebrute $250 for PR via Upwork
@c3024 $250 for C+ via Upwork

@Nodebrute $250 sent and contract ended!

@c3024 $250 sent and contract ended!

All set. Thanks everyone!


FCParts.GenerateParts() is missing

The changelog for v0.62 says there's a new method FCParts.GenerateParts(), however I don't see that in the class browser.
I'm using the most recent version of the class browser (pulled today).

It's there on mine. It's a class method. Are you using the jwtagfile.xml for 0.62?

Figured it out. Yes, I am using that version of jwtagfile.xml, but your message reminded me that I needed update RGP Lua itself.
It's neat that the class browser will only show methods the running version of RGP Lua supports.
To prevent further confusion, would it be possible to add a quick piece of text to the dialog to show the current version of the class browser and RGP Lua?
Closing in the meantime since my original issue is solved. Feel free to reopen.


Set up multi jobs for spec testing.

No spec changes detected: https://github.com/firebase/firebase-ios-sdk/runs/4670424646?check_suite_focus=true
Test all specs with skip-tests: https://github.com/firebase/firebase-ios-sdk/runs/4665958677?check_suite_focus=true


Don't use js for css. Part 1

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[x] Refactoring

Context

[x] Closes #8496
[ ] Requires deployment <snek/rubick/worker>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality

Optional

[x] I've tested it at </ksm/collection>
[x] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Ecosystem Telegram?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

Copilot Summary

🤖[deprecated] Generated by Copilot at b255410
This pull request introduces a new ThemedImage component that adapts to the light and dark theme modes using CSS variables, and replaces the existing image elements with this component in various UI components. It also refactors some components to use CSS media queries instead of JavaScript logic for responsiveness and theme mode, and fixes some minor bugs and formatting issues in the SCSS and Vue files.

🤖[deprecated] Generated by Copilot at b255410

This pull request has a theme
To make the UI look supreme
With ThemedImage and CSS
We can reduce the code mess
And make the icons and logos gleam

I'll close this one since there is multiple conflicts, not really convinced by this solution.


[FEAT]: Source T-shirts for the team members

Description
In preparation to the 2022-02-17 OpenCV Weekly Webinar and other future public showcases of the ARNEIS project, I believe it would be great if all the team members wear some unique piece of garment (i.e. a T-shirt or a hoodie), featuring either the ARNEIS logo or the B-AROL-O Team logo.
Additional Information
No response

Here are some sites of companies printing customized t-shirts where we may ask for a quote:

https://www.stickermule.com/it/products/magliette-personalizzate (produzione entro 4 giorni e spedizione gratuita)
https://camaloon.it/magliette-personalizzate(forse piu' indicato per volumi)
...

Just for fun I submitted a quote to https://www.stickermule.com/. Here is the result:

By the way, which is your T-Shirt size? Personally, I wear a 2XL.

Not urgent, we already have a lot on the plate for this week. Postponing after the 2022-02-17 webinar

On saturday 2022-03-05 checked in a local store the possibility to print t-shirts for our goal.

Unlikely in this laboratory they can only print on white shirts and not over colored shirts. Their technology is thermal transfer: they print on white paper the Logo and when transferred to the t-shirt also the white background is transferred.
The cost is 15.5€ per shirt (1 t-shirt).
Next Step : check for online laboratories.

Last night I had an idea for improvement: Why on the T-Shirts couldn't we print a QRCode linking to https://arneis.readthedocs.io close to ARNEIS logo - or maybe, on the back of the T-Shirt if this does not add too many extra costs?
For the tool to be used I would recommend https://devpost.com/software/axolotl

Order of t-shirt from https://camaloon.it/.
More information about prices and order in private project
Image of the ordered t-shirt


SSL domain and media library translation

If I have a bucket mybucket.domain.com and set the custom domain to mybucket.domain.com all the images urls are translated to http://mybucket.domain.com/... which is correct.
When I set the domain to https://mybucket.domain.com only the new images I upload have the correct address, all the old images stay with https://storage.googleapis.com/ domain.

The GCS url is saved as attachment meta data in database.
You have to do a manual sync from Media >> Stateless Settings >> Sync tab.


Comment or deprecate "place-tbl-lbl" named template

Expected Behavior
The "place-tbl-lbl" named template (in org.dita.html5/xsl/tables.xsl) should be either commented or deprecated if it is not currently used.
When I tried to override figure and table titles, I saw that "place-fig-lbl" affected figure titles but "place-tbl-lbl" did not affect table titles. A closer inspection revealed that the figure label template is defined and used:
$ fgrep 'place-fig-lbl' -r .
./xsl/topic.xsl:      <xsl:call-template name="place-fig-lbl"/>
./xsl/topic.xsl:  <xsl:template name="place-fig-lbl">

but the table label template is defined but never used:
$ fgrep 'place-tbl-lbl' -r .
./xsl/tables.xsl:  <xsl:template name="place-tbl-lbl">

I spent a couple hours trying to figure out why the override was failing before realizing the template was never used.
Actual Behavior
If you search for "table--title-label" in tables.xsl, you'll see some piecemeal templates further down the file that implement table output. This is fine; the user just needs some guidance (in comments, etc.) to know where they should be working.
Environment

Ubuntu 19.10
DITA-OT 3.4
html5 transformation

Linked issue above marks this template deprecated. Waiting to remove from develop branch until after the hotfix change is merged into develop


Support per-page scrolling

When set to "Page Fit" and any scroll action is triggered (down-scrollbar arrow, mid-click, scrollwheel, etc.), PDF.js should scroll a whole page and not just a few pixels. This is the behavior Adobe Reader has, and it feels appropriate.

Oh yes, full page zomming and scrolling is a long-awaited feature. If you look at presentation slides, every mouse wheel tick should scroll one page. The new fullscreen mode does this correctly, but I would also like to have this feature in non-fullscreen mode.
BTW: That is the main cause why I open the PDFs in Acrobat and not natively in Firefox with pdf.js.


How to crawl current webpage only?

Whenever I crawl a webpage, this tool not only scrapes the content of the webpage but also automatically visits the URLs on the page. This process is very time-consuming. How can I make the tool scrape only the content of the given webpage?

@OpEnD17 I'd like to see your code because our library doesn't work that way. When you pass a URL, it only crawls that URL and extracts links, but doesn't crawl the external links. Please share your code so I can help.


Admin can change user's donor level

[x] Added dropdown with donor levels next to every user in the 'registered user' list on the admin dashboard
[x] Default dropdown value is filled with current user donor level (from database)
[ ] TO DO: Update db with selected donor level
[ ] TO DO: Get donor level choices from the db, instead of hard-coding
[ ] TO DO: Make default value dark text, not greyed out

@anoshaminai: it's hard to tell what was changed because the indentation was changed for a lot of the html. Take a look at https://github.com/hack4impact/women-veterans-rock/pull/27/files to see what I'm talking about. It'll be a lot easier to see the differences when things are properly indented again.

@aharelick Is that the correct indentation?

@aharelick @Mebsworth Please take a look !

@anoshaminai, I don't think you ever pushed your most recent code, looks like the most recent commit is from awhile ago

@aharelick Sorry about that, should all be there now!


Error in Validation split percentage - Image Classification tutorial

Thank you for submitting a TensorFlow documentation issue. Per our GitHub
policy, we only address code/doc bugs, performance issues, feature requests, and
build/installation issues on GitHub.
The TensorFlow docs are open source! To get involved, read the documentation
contributor guide: https://www.tensorflow.org/community/contribute/docs
URL(s) with the issue:
https://github.com/tensorflow/docs/blob/master/site/en/tutorials/images/classification.ipynb
Please provide a link to the documentation entry, for example:
https://www.tensorflow.org/versions/r2.0/api_docs/python/tf/MyMethod
Description of issue (what needs changing):
Under Load using Keras.preprocessing > Create Dataset, the percentage under training_ds for validation_split is set to 0.2. I believe is supposed to be 0.8.
Clear description
When you used 0.8 on the number of images in the directory, it will result to 2936, but 0.2 is way smaller.

@roca77
Could you please give in more details or an example of the issue faced.

@Saduf2019 @jvishnuvardhan The error is in the documentation itself; In both tutorials (on github and on tensorflow's website), there is an error on the percentage when the program splits the data into training dataset and validation dataset. I believe the correct percentage is 0.8 for training and 0.2 for validation.

@roca77 Thanks for raising the issue.
The percentage 0.2 is correct. The split is percentage of data reserved for validation which is 0.2. You can check the documentation here
The documentation says that

validation_split
Optional float between 0 and 1, fraction of data to reserve for validation.

Please verify once and close the issue. Thanks!

Closing; Thanks for checking


pythonPackages.hypothesis: 3.79.3 -> 3.81.0

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build python2Packages.hypothesis python3Packages.hypothesis python2Packages.pytest python3Packages.pytest

Failure on x86_64-darwin (full log)
Attempted: python2Packages.hypothesis, python3Packages.hypothesis, python2Packages.pytest, python3Packages.pytest
Partial log (click to expand)
cannot build derivation '/nix/store/8m38j2x563fpkhv22m4vgarq7h0acnn8-python3.7-mock-2.0.0.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/yv4rkgkf5178wm0pzy18zrn3vfd909f6-python2.7-hypothesis-3.81.0.drv': 15 dependencies couldn't be built
cannot build derivation '/nix/store/pkrn5kdhbwsh4ci8zjc55zfdg115nlrc-python3.7-pytest-3.9.2.drv': 17 dependencies couldn't be built
cannot build derivation '/nix/store/nrz8wwcqsbcmxphc4iq9s3ldcjh9b73z-python3.7-apipkg-1.5.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/7x2pnznr2piznj4800pm8zfminvbsqfb-python3.7-flaky-3.1.0.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/nx8lqnf6fx23km92cwyg1jdq0djx3y0i-python3.7-pytest-forked-0.2.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/v1v6d7lawd3l1jjhcy2cgwz4jy0n9ghb-python3.7-execnet-1.4.1.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/pim97ks8mgqhqrgprznqwcmhl2c1h04n-python3.7-pytest-xdist-1.23.2.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/xy5m993xc8w8a8ifam4np27nykjxi11l-python3.7-hypothesis-3.81.0.drv': 14 dependencies couldn't be built
error: build of '/nix/store/jfj3793apw3kh2bm0xi7jfz4wfafpfd5-python2.7-pytest-3.9.2.drv', '/nix/store/pkrn5kdhbwsh4ci8zjc55zfdg115nlrc-python3.7-pytest-3.9.2.drv', '/nix/store/xy5m993xc8w8a8ifam4np27nykjxi11l-python3.7-hypothesis-3.81.0.drv', '/nix/store/yv4rkgkf5178wm0pzy18zrn3vfd909f6-python2.7-hypothesis-3.81.0.drv' failed

Success on aarch64-linux (full log)
Attempted: python2Packages.hypothesis, python3Packages.hypothesis, python2Packages.pytest, python3Packages.pytest
Partial log (click to expand)
2.71s call     hypothesis-python/tests/cover/test_simple_collections.py::test_dictionaries_of_fixed_length[7]
2.22s call     hypothesis-python/tests/cover/test_simple_collections.py::test_dictionaries_of_fixed_length[6]
2.17s call     hypothesis-python/tests/cover/test_simple_collections.py::test_sets_of_fixed_length[9]
2.14s call     hypothesis-python/tests/cover/test_composite.py::test_can_shrink_matrices_with_length_param
=================== 1751 passed, 6 skipped in 408.98 seconds ===================
pytestcachePhase
/nix/store/f30ny42s7xgpk7yiwnq9kydgk3xh31vw-python2.7-hypothesis-3.81.0
/nix/store/2fvk7r5s8gxwh2gbzvzbwbxbi9flavr0-python3.7-hypothesis-3.81.0
/nix/store/45gqzww20xm8qrcygh1nrglx6frcj5wv-python2.7-pytest-3.9.2
/nix/store/s79nshkadldnk3x18cj566lz6b484r40-python3.7-pytest-3.9.2

Success on x86_64-linux (full log)
Attempted: python2Packages.hypothesis, python3Packages.hypothesis, python2Packages.pytest, python3Packages.pytest
Partial log (click to expand)
1.32s call     hypothesis-python/tests/cover/test_charmap.py::test_reload_charmap
1.31s call     hypothesis-python/tests/cover/test_charmap.py::test_recreate_charmap
1.28s call     hypothesis-python/tests/cover/test_reproduce_failure.py::test_encoding_loop
1.18s call     hypothesis-python/tests/cover/test_charmap.py::test_regenerate_broken_charmap_file
=================== 1752 passed, 2 skipped in 171.59 seconds ===================
pytestcachePhase
/nix/store/b59yczpl33ww4i9knba4223mrmngxqci-python2.7-hypothesis-3.81.0
/nix/store/yv721fw6qg86h7h0ag6azz6gihpv4vda-python3.7-hypothesis-3.81.0
/nix/store/7h6n6avj9bhij8b278z13fgc4wsrr5w4-python2.7-pytest-3.9.2
/nix/store/sr5gf70s0ghw01wa5s5vsd056sm36lg6-python3.7-pytest-3.9.2

FWIW hypothesis 3.82.1 is now out, although by the time I hit send it'll
probably be 3.83 or something ;).

Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/49393#issuecomment-434010656Non-text part: text/html

Never versions are out, FWIW...


Delete bucket fails after deleting all objects in the bucket

If I create a bucket "test" and add the following object keys:
index.html
styles/main.css
Then if I delete all the objects and try to delete the bucket I get the following error:
Unable to delete bucket test:  {
"message": "The bucket your tried to delete is not empty",
"code": "BucketNotEmpty",
"region": null,
"time": "2016-04-18T19:27:26.649Z",
"requestId": null,
"extendedRequestId": null,
"statusCode": 409,
"retryable": false,
"retryDelay": 0.46673882752656937
}
However, the bucket is empty if I view it through the browser.
The problem appears to be that the "styles" directory is still present in the data dir even though all keys have been deleted.
If I manually delete the styles directory, then I am able to delete the bucket.  So there appears to be an issue cleaning up empty directories once all keys have been deleted.

Hello @joshwils82 - Thank you for reporting this. Do you think you could make a pull request? If not, I should have some time this week to get around to this and the various other outstanding issues.
Thank you!

Hi @jamhall,
I might be able to find some time to put together a pull request. I will try to pull something together over the next couple of days.  Otherwise, if you get to it first just let me know.
Thanks!


Pirate Weather API unreachable since 5/26

Hi there...I noticed several days ago that my app's weather data was not up to date. After looking through logs, I see that all calls to api.pirateweather.net have been failing since May 26. By failing, I mean I get no response at all and the call times out.
At first I chalked it up to a transient internet issue, but my ISP (Mediacom) couldn't see an issue on their end and said it must be a problem with the website. Then I noticed that the last entry on the API Changelog is dated May 26...same day calls started failing. Could be coincidence, but smells a little fishy :)
Also, looking through the Issues I saw #64. I wonder if my problem accessing the site could be the same or similar issue?
EDIT: I can access pirateweather.net and merrysky.net without issue. This is strictly an issue with api.pirateweather.net.

Apologies, my problem above turns out to NOT be a Pirate Weather issue. Rather, after many days troubleshooting I finally tracked it down to a recent OPNsense update that inexplicably started sending traffic to Pirate Weather API out over a VPN gateway by default. The other end of the VPN was just dropping these packets, so no responses were ever received. I've not yet tracked down what is causing this bizarre behavior in OPNsense, but at least I've found the problem and implemented a workaround.
Very sorry to bother...

Awesome! Happy that you got it working- I've run into my share of random network VPN issues, so no worries at all. Thanks for the kind words, and let me know if anything else crops up


Visual Studio code is not responding. it shows window is not responding

when i am writing/running a code in visual studio code, it shows window is not responding. i have uninstall the Visual studio code & reinstall it, but the problem has not been solved yet.

Can you check if the freeze happens with exploration build thats on a newer runtime https://az764295.vo.msecnd.net/exploration/f0e1fbf4cb8c4c27d6290f0310f5a4d63597cd21/VSCodeUserSetup-x64-1.48.0-exploration.exe
If the freeze continues, can you also check with --disable-extenions

Can you check if the freeze happens with exploration build thats on a newer runtime https://az764295.vo.msecnd.net/exploration/f0e1fbf4cb8c4c27d6290f0310f5a4d63597cd21/VSCodeUserSetup-x64-1.48.0-exploration.exe
If the freeze continues, can you also check with --disable-extenions

I have tried, but the same problem exists again. i have attached the Screenshot also.

kindly solve my issues.
my vs code is not responding.

I have started see this too.

Started seeing this here as well on macOS. For me it seems to be related to the scroll back buffer of the integratedTerminal; scrolling back as well as running commands with large amounts of output cause the window to freeze. Disabling extensions did not solve the issue.
Version: 1.49.2

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

</details


GoPool's performance in comparison to other goroutine pool implementations

Question
GoPool seems to perform poorly from the benchmarks I ran
name                   time/op
UnlimitedGoroutines-8   301ms ± 4%
ErrGroup-8              515ms ± 9%
AntsPool-8              582ms ± 9%
GammaZeroPool-8         740ms ±13%
BytedanceGoPool-8       572ms ±18%
ItogamiPool-8           331ms ± 7%

name                   alloc/op
UnlimitedGoroutines-8  96.3MB ± 0%
ErrGroup-8              120MB ± 0%
AntsPool-8             22.4MB ± 6%
GammaZeroPool-8        18.8MB ± 1%
BytedanceGoPool-8      82.2MB ± 2%
ItogamiPool-8          25.6MB ± 2%

name                   allocs/op
UnlimitedGoroutines-8   2.00M ± 0%
ErrGroup-8              3.00M ± 0%
AntsPool-8              1.10M ± 2%
GammaZeroPool-8         1.05M ± 0%
BytedanceGoPool-8       2.59M ± 1%
ItogamiPool-8           1.05M ± 0%

Reference -> https://github.com/alphadose/itogami
Benchmarking code -> https://github.com/alphadose/go-threadpool-benchmarks

Could you please try the same test as https://github.com/bytedance/gopkg/blob/develop/util/gopool/pool_test.go？

Got these results
2022/07/05 16:20:06.801184 logger.go:190: [Error] GOPOOL: panic in pool: test: test: goroutine 2025 [running]:
runtime/debug.Stack()
	/opt/homebrew/Cellar/go/1.18/libexec/src/runtime/debug/stack.go:24 +0x68
github.com/bytedance/gopkg/util/gopool.(*worker).run.func1.1.1()
	/Users/alphadose/assignment/go-threadpool-benchmarks/vendor/github.com/bytedance/gopkg/util/gopool/worker.go:64 +0x80
panic({0x100601700, 0x100623510})
	/opt/homebrew/Cellar/go/1.18/libexec/src/runtime/panic.go:838 +0x204
command-line-arguments.testPanicFunc()
	/Users/alphadose/assignment/go-threadpool-benchmarks/gopool_test.go:27 +0x30
github.com/bytedance/gopkg/util/gopool.(*worker).run.func1.1(0x1400010c2b0?, 0x10060c8a0?)
	/Users/alphadose/assignment/go-threadpool-benchmarks/vendor/github.com/bytedance/gopkg/util/gopool/worker.go:69 +0x5c
github.com/bytedance/gopkg/util/gopool.(*worker).run.func1()
	/Users/alphadose/assignment/go-threadpool-benchmarks/vendor/github.com/bytedance/gopkg/util/gopool/worker.go:70 +0x1a8
created by github.com/bytedance/gopkg/util/gopool.(*worker).run
	/Users/alphadose/assignment/go-threadpool-benchmarks/vendor/github.com/bytedance/gopkg/util/gopool/worker.go:41 +0x64
%!(EXTRA []interface {}=[])
goos: darwin
goarch: arm64
BenchmarkPool-8      	     367	   3841601 ns/op	  179468 B/op	   10227 allocs/op
BenchmarkGo-8        	     100	  11113182 ns/op	  167427 B/op	   10016 allocs/op
BenchmarkItogami-8   	     369	   3109478 ns/op	  174749 B/op	   10073 allocs/op
PASS
ok  	command-line-arguments	4.771s

https://github.com/alphadose/go-threadpool-benchmarks/blob/master/gopool_test.go

I think it's not enough to test cpu cost handler only, in most of the real scenarios, blocking is the usual operation, eg: http handler, rpc handler, and there is a write syscall at least.
I tried with a short sleep and get a much worse performance from gopool than std:
func testFunc() {
	// DoCopyStack(0, 0)
	time.Sleep(time.Microsecond * 10)
}

result:
BenchmarkPool-8          	       2	 810477898 ns/op	76536652 B/op	 2361916 allocs/op
BenchmarkGo-8            	       4	 296506521 ns/op	97106736 B/op	 2011528 allocs/op

it also saves a lot of memory

I think the memory cost can be ignored since it runs 10000 times in each b.N loop, it's a much smaller memory cost for each Go operation:
https://github.com/bytedance/gopkg/blob/develop/util/gopool/pool_test.go#L24

I took a quick glance at the code, and found that it makes good use of the runtime's internal funcs, that's great!

@alphadose Cool!

@alphadose
I took a look at your test and found that it's unfair because itogami's pool size is 5e4 but gopool size is much smaller. For itogami's pool it's similar to using std goroutine but your implementation performs a little better.
https://github.com/alphadose/go-threadpool-benchmarks/blob/master/gopool_test.go#L89
And the same point with gopool's default cpu cost handler, if I change the pool size and change to a testFunc with a short sleep, itogami doesn't perform better than std in my env:
# pool size: 1000
BenchmarkPool-8      	      10	 110218422 ns/op	  461439 B/op	   12138 allocs/op
BenchmarkGo-8        	      84	  13746197 ns/op	  969096 B/op	   20052 allocs/op
BenchmarkItogami-8   	      10	 104207091 ns/op	  200136 B/op	   10413 allocs/op

It's only faster than std when the PoolSize >= benchmarkTimes, else it's much worse than std.

if we remove the limit on itogami then it essentially becomes an infinite goroutine pool but it also saves a lot of memory (due to recycling via the stack) as compared to using native goroutines, hence I think its beneficial to use itogami in this case too with some modifications

It would be no means if we don't limit the pool size and I think users prefer to use std goroutine rather than

@alphadose
I met a SIGSEGV from Itogami when running the benchmark:
goos: linux
goarch: amd64
pkg: github.com/alphadose/go-threadpool-benchmarks
cpu: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
BenchmarkGo-8         	     328	   3554240 ns/op	  972669 B/op	   20124 allocs/op
BenchmarkPool-8       	     206	   6353972 ns/op	  590759 B/op	   19165 allocs/op
BenchmarkItogami-8    	fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x4372a7]

......

@lesismal I made itogami as a proof of concept for a better golang scheduler, and as it uses golang runtime internals it is unsafe because of some edge cases here and there. Hence, its also unsafe to use for real use cases.
If you are interested here is the corresponding issue in golang core https://github.com/golang/go/issues/53398

If you are interested here is the corresponding issue in golang core golang/go#53398 ^ the benchmarking in the above case is based on a no-limit version of itogami which can be viewed in this branch https://github.com/alphadose/itogami/tree/golang-scheduler

I took a quick look at 53398, It's good trying to use lock-free to optimize performance.
But as I know, lock-free is only suitable for a few scenarios such as a queue's push and pop operations. It can't be used to optimize a process with multiple steps which have beyond the atomic operations' ability.

@lesismal I made itogami as a proof of concept for a better golang scheduler, and as it uses golang runtime internals it is unsafe because of some edge cases here and there. Hence, its also unsafe to use for real use cases.

Since it's unsafe, the benchmark result should not be used to compare with std other goroutine pools, it doesn't make sense and would make misleading.
About http performance, I agree with you that fasthttp is really fast, but gnet's http benchmark is not a fully implementation of http protocol, details here, that also makes misleading. I used to opend an issue to advise not to use that benchmark result to claim gnet's performance but wasn't accepted and it seems my issue was deleted... But I would still be glad to see if someday the author deletes the http benchmark result, or if he fully supports the protocol.
I have another lib that does these tls/http/websocket things with goroutine num and memory usage under controlled: https://github.com/lesismal/nbio
There's also a sub-package that implements goroutine pools with limited size,  it can't perform better than std but can limit pool size, and it seems the benchmark with short sleep performs a little better than I attached in the previous comments, if interested, welcome to try.

@leismal

But as I know, lock-free is only suitable for a few scenarios such as a queue's push and pop operations. It can't be used to optimize a process with multiple steps which have beyond the atomic operations' ability.

I went through the golang's scheduling code and there is room for improvement by switching to a lock-free stack in some places. I got the idea itself from a gophercon talk delivered by a member of golang core team and I tested it out, got some good results. The major performance improvement by switching to a lock free stack would be scheduling all operations entirely in user-space and avoid lock()/unlock() system call context switches.

Since it's unsafe, the benchmark result should not be used to compare with std other goroutine pools, it doesn't make sense and would make misleading.

Agreed, I will update the readme so that people are aware that its experimental and unsafe.


Env Dashboard Should filter the record as per folder

As we are using folder plugin and restrictive access to the various project.
This should support -> which should enable us to display only those jobs or values which are related to folder\view in jenkins.
I can also contribute.
This Plugin is very useful :)

yeah I'm facing the same issue in that the link to the job cannot be displayed


Doris support in memory olap table

For https://github.com/apache/incubator-doris/issues/2846
The doc and schema change support will do in next PR.

Update the PR for https://github.com/apache/incubator-doris/issues/2866
Currently, I don't persist in_memory property in FE partition metadata, I think which is not very n necessary. If we think we should persist in_memory property  in FE partition metadata, I could do this work in next PR. This PR is big enough.

Add in_memory property to partition level.
2.Handle FE and BE in_memory meta consistency in ReportHandler.

LGTM.
The report process is inefficient, may be we should optimize it later.

Yes. I agree with you. I also considered this point. I think we can handle SetTabletInMemory once an hour even once a day, if which has a performance issue.

Update the PR to Fix conflict only, not change from morningman last review.


add ship signature to ship request

add an example where the shipment request can include a signature option on delivery. This can be commented out to not require the signature option.

+1


Does this framework support "what you serve is what you train" for weight only quantization?

Keeping activations as float while quantizing the weights to int8 or int4. I see that currently how it is done is by using float * float dot product. is there a int * float dot product available?

Yes, in the config, you can select it individually.

Thanks for the speedy reply. Would you mind pointing me to the config field that toggles this?

https://github.com/google/aqt/blob/main/aqt/common/aqt_config.py#L362
As you see lhs and rhs have completly separate quantization configs.

Yes, but from what i see in the underlying dot product code, if activation is not quantized, a float * float dot product is used? https://github.com/google/aqt/blob/main/aqt/jax/aqt_dot_general.py#L91 Is this a fake quantization or is this also the arithmetic in serving time?

Sorry that I missed your comment.
For the dot product to be accelerated, both sides need to have the same type.
You are probably most concerned about weight loading.
We will implement that in AQTv2 within a month.


tikv_util: add handled task counter for LazyWorker

Add a metric to inspect the total number of tasks handled by a LazyWorker.

What is changed and how it works?

Issue Number: Close #16195

What's Changed:
Add a metric to inspect the total number of tasks handled by a LazyWorker.

Check List
Tests

Unit test

Release note

None

/merge

/hold

/unhold

/merge


E3/DC | disable weather regulated charging if car is connected and Soc < targetSoC

Is your feature request related to a problem? Please describe.
If weather-based household battery charging is activated, the system waits to charge the house battery until E3/DC thinks that a favorable time has been reached to bypass the 70% feed-in limit by charging the house battery.
However, this in turn further delays the start of charging of any connected EV.
Describe the solution you'd like
When E3/DC was only readable via Modbus, i solved this using RSCP integration and a home assistant automation and disabled weather-based charging when a car was connected and its TargetSoC had not yet been reached and reactivated it as soon as the car was unplugged or the TargetSoC was reached.
Is this a useful function that could, should and would be transferred to evcc?
Describe alternatives you've considered
If there is no wish to include this functionality into evcc core, i will stick with the HA automation.
Additional context
Add any other context or screenshots about the feature request here.
/cc @docolli @spali

These: gerätespezifische Anforderung -> außerhalb zu lösen.

Never used this function since my 13kWp are distributed on Southeast and Northwest roofs, so only in very rare cases I get over the 70% limit. Do you have >7kWp, then then 70% limit could be disabled now.
Also I set the bufferStartSoc quite low (40%), so that my car starts early to load and my batterie loads later (when the car is disconnected).

Then lets leave this in HA as its very device- and usecase- specific.


tables should preserve integers

https://github.com/twosigma/beakerx/pull/6007
see explanation here.  this is true of groovy tables too.
new TableDisplay( new CsvPlotReader().read("tab.csv"))

where tab.csv has
"a"
"1"

we should get a integer column, not double.

still needs to be fixed in groovy


Don't log ALB healthchecks in CloudWatch

I don’t think they’re a big cost, but they do spam the logs and slow down search:
10:14:09.578 [finagle/netty4-7] INFO c.t.f.h.filters.AccessLoggingFilter - <IP_ADDRESS> - - [14/Jun/2018:10:14:09 +0000] "GET /management/healthcheck HTTP/1.0" 200 16 0 "ELB-HealthChecker/2.0"

I tried adding janino to our dependencies and this to logback.xml, but I couldn't get it working in my brief experiments:
    <filter class="ch.qos.logback.core.filter.EvaluatorFilter">
      <evaluator>
        <expression>
          return (message.contains("ELB-HealthChecker/2.0"));
        </expression>
        <OnMismatch>NEUTRAL</OnMismatch>
        <OnMatch>DENY</OnMatch>
      </evaluator>
    </filter>


Python: interactive window not showing code execution status

July version(1.59) of VS Code came with new interactive window.
In the previous version interactive window shows [*] during the time when line is running. Once line completed, number appear [1]. In the new version user is required to click on the wheel sign to see if the line is still running.
Please return the feature from the previous version back to see if the line of code is still running without any additional clicks.
Thanks for your help.

running indicator now shows


panctl : ImportError: cannot import name 'HTML'

panctl
Traceback (most recent call last):
  File "/home/arthur/.virtualenvs/pantalaimon/bin/panctl", line 5, in <module>
    from pantalaimon.panctl import main
  File "/home/arthur/.virtualenvs/pantalaimon/lib/python3.6/site-packages/pantalaimon/panctl.py", line 27, in <module>
    from prompt_toolkit import HTML, PromptSession, print_formatted_text
ImportError: cannot import name 'HTML'

Maybe the dependency to prompt_toolkit needs to be a bit more precise ?
I realised that I had done toggleglobalsitepackages in this env, so I was probably on
python3-prompt-toolkit/bionic,bionic,now 1.0.15-1 all [installed,automatic]

I can't reproduce that on prompt toolkit 2 nor 3. Does that line show prompt toolkit 1.0 as the installed version?

I think this is fixed by #34

Fixed now.


Review for OpenCDSS release

Need to review the documentation for OpenCDSS release.

I updated the documentation to use CC BY 4.0 license.  I updated the content files to use OpenCDSS repository links.  I updated the Markdown to work with MkDocs 1.0.4.  Close the issue.


Support irreducible CFG

Most of TeaVM algoritms rely on reducible CFG. As pure Java programs can't produce irreducible CFG, everyting works fine. But some bytecode ingineering tools can produce irreducible CFGs, for example, tools for transforming to continuation-passing style, like javaflow. For this purpose TeaVM should do preprocessing on the very first stage of compilation (even before converting to SSA) that would transform irreducible graph to reducible by copying parts of graph.

This feature is very important for async code, since TeaVM's async code transformer sometimes produces irreduciblesflowgraphs.


Enable nested json2text within yaml2text (and viceversa)

Currently this does not work:
[yaml2text,filename.yaml,paths]
----
{% for path in paths %}

[json2text,{{ path }},event]
--
include::../event.liquid[]
--

{% endfor %}
----

We want to be able to nest json2text blocks within yaml2text (and viceversa).

@abunashir is this something you can fix? Thanks.

And we should add this type of usage to documentation.

Hey @ronaldtse, I was looking into it lately but it seems to bit tricker than I thought, since we are using two different types as pre-processor extensions (yaml2text , json2text ) in one block, it's creating a bit of an issue with each other.
For example, currently, the json2text extension is registered as pre-processor first then the yaml2text, so when we try to process the example block Ascidoctor invokes json2text first. That preprocess goes through the document, and tries to process it.

At this point, the nested path value is not assigned, so it can’t handle value as expected and just wipes that out from the document, then the yaml2text extension kicks in and it only processes whatever is left in the document. We can reverse the order they are registered, but the example would not work when yaml2text is added as nested to json2text.
So my question is, how important is this feature to have cross types in one block even though the user can potentially rewrite their data as main data types? We might be able to find some hacks, but is it worth adding this complexity in a document?


Total refactoring

This package requires total refactoring before adding new Laravel versions support and new features.

hi @antonkomarev, what will it breaks if you remove the requirement of laravel 5?
Basically they are traits attached to models (I'm not expert in Laravel)
Thanks in advance

In theory L6 and L7 support could be added without removing L5 support.

this in you composer
"illuminate/database": "~5.2|~5.3|~5.4|~5.5|~5.6|~5.7",
"illuminate/support": "~5.2|~5.3|~5.4|~5.5|~5.6|~5.7"
doesn't block laravel to v5?
I'm trying to install your branch add-latest-laravel-versions-support

Yes. I haven't added latest Laravel versions because this package was archived for a long time. You could send a PR for the new Laravel versions support.

@antonkomarev does the laravel7 branch work with laravel 7, or does the package still need to be updated to laravel7

This package is not working with latest laravel versions. I'm not using it on production anymore. It requires some refactoring.

Is this package still needed "Total Refactoring" to be an ongoing concern?
We are currently getting a "package is abandoned" message when installing the latest version.
I am happy to help put with the development that you are wanting to do if we can put together a plan of the development that is needed/wanted.
Thanks

@jny986 I've removed abandoned message. Package was updated at the end of the 2020, but I forgot to remove this notice.
I don't have plans to continue actively maintaining it by myself, but if you have an ideas how it could be improved - it's always opened for PRs.

I don't mind helping with the development as well.> Is this package still needed "Total Refactoring" to be an ongoing concern?

We are currently getting a "package is abandoned" message when installing the latest version.
I am happy to help put with the development that you are wanting to do if we can put together a plan of the development that is needed/wanted.
Thanks

@aaly00 not really, if you are fine with current implementation - we could continue development without changing its architecture. It will be awesome if you will write how are you using this package and what you want to improve.


fatal: ambiguous argument 'master': unknown revision or path not in the working tree.

Hi I am having this error, when trying to trigger other pipelines based on file changes.
From the way i understand the Orb, it should trigger other pipelines in specific directories where there is a change.
But after configuring the orb, i notice it was actually filtering out the directories where the pipeline configs are targeting, but it isnt triggering the pipelines. rather it gives a git error.
Here is my config.yml below.
#/**************************************************************************
#******************    TOP LEVEL CONFIGURATION      ***********************#
#**************************************************************************/

version: 2.1

setup: true

orbs:
  dynamic<EMAIL_ADDRESS>
workflows:
    test-workflow:
      jobs:
        - dynamic/continue:
            context: circleci
            root-config: config
            modules: |
              .
              web.frontend.src.main

this is the default config file located under .circleci dir
I have two other config files with the names test.yml and web.frontend.src.main.yml, they are also located in .circleci dir.
Expected behavior

when there are changes in root dir. test.yml executes
when there are changes in web/frontend/src/main/ dir, web.frontend.src.main.yml executes

Current behaviour
dynamic workflow executes(that is my config.yml)
auto detect detects the modules specified in confg, but pipeline is not executed despite the changes in those directories.
During the Filter step; this is the log of the error.
ERROR
Auto-detected the following modules:

test
web.frontend.src.main

Collecting wildmatch==0.3.1
  Downloading wildmatch-0.3.1-py3-none-any.whl (4.1 kB)
Collecting pathspec==0.9.0
  Downloading pathspec-0.9.0-py2.py3-none-any.whl (31 kB)
Installing collected packages: pathspec, wildmatch
Successfully installed pathspec-0.9.0 wildmatch-0.3.1

[notice] A new release of pip is available: 23.0.1 -> 23.1.2
[notice] To update, run: pip install --upgrade pip
fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
CircleCI received exit code 0

additional information
My default branch is not master it is develop

just to confirm my hypothesis, I set up a separate environment, it seems it works well when the default branch is master branch but fails with the error above when the default is develop branch.

thank you, pipeline is working now.

It would be nice if this was called base-revision instead of default-branch so that it was more guessable. The path-filtering orb uses base-revision.

Agreed @Martin-Narvar good catch! I'll implement this in #106


The "Getting Started" tutorial does not seem to work

Hi,
I follow the introduction but it seems that the websocket.receive method isn't called. The question is now if it is my fault, a error in the introduction or a bug in channels.
Here are the relevant package versions that i use:
asgi-redis==0.13.1
asgiref==0.13.3
autobahn==0.14.1
channels==0.16.0
daphne==0.14.2
Django==1.9.7
redis==2.10.5
Twisted==16.3.0

consumer.py
from channels import Group

# Connected to websocket.connect
def ws_add(message):
    Group("chat").add(message.reply_channel)
    Group("chat").send({
        "text": "New user here!",
    })

# Connected to websocket.disconnect
def ws_disconnect(message):
    Group("chat").discard(message.reply_channel)

# Connected to websocket.receive
def ws_message(message):
    Group("chat").send({
        "text": "[user] %s" % message.content['text'],
    })

routing.py
from channels.routing import route
from tailIt.consumers import ws_add, ws_message, ws_disconnect

channel_routing = [
    route("websocket.connect", ws_add),
    route("websocket.receive", ws_message),
    route("websocket.disconnect", ws_disconnect),
]

A snippet of settings.py:
CHANNEL_LAYERS = {
    "default": {
        "BACKEND": "asgiref.inmemory.ChannelLayer",
        "ROUTING": "tail_log.routing.channel_routing",
    },
}

I used Wireshark to verify the data transmission between the server and Firefox. At the connect to the websocket i get the message "New user here!". But if i send something via socket.send("something") i see the message goes to the server but nothing returns to the browser.
As far as i understand django/channels should return a message like "[user] something".

Unfortunately it looks like you've run into the bug with Twisted 16.3 outlined in #237 - just downgrade Twisted to 16.2. Daphne should have forced this by default when you installed it, so it's strange you got the wrong version - do you still have the installation logs anywhere?

Thanks i read this just at the moment in the changelog of daphne

I upgraded before a few hours via pip freeze --local | grep -v '^\-e' | cut -d = -f 1  | xargs pip install -U. So pip upgraded twisted after channels. So i got incompatible versions. If i just use pip install -U channels twisted get downgraded automatically. It seems that pip doesn't check if it is safe to upgrade a package.

Urgh, that's annoying. A fix is on its way upstream into Autobahn, so hopefully this won't be a problem for too long.


Effect composer - postprocessing

Hi, is there anyone who has tried to use some postprocessing filter?
So instead of using the renderer.render function uses composer.render?
Like this:
renderer.setAnimationLoop(() => { composer.render(); //renderer.render(scene, camera); });
If i try to use effect composer, i get this error in console with a simple shader filter too.
This is the error:
THREE.WebGLProgram: Shader Error 0 - VALIDATE_STATUS false Program Info Log: Fragment shader is not compiled......
Is there a solution?
Thanks

Anyone are using postprocessing library with MindAR?
ref. https://github.com/pmndrs/postprocessing

The issue is stale. feel free to re-open if there is new insight.


Fixing Dockerfile using old apt cache and start command

Fixing Dockerfile using old apt cache and start command.
I had an issue with the apt trying to pull different versions and then the container would not start due to the "()" in the start command.

The () is definitely necessary in this scenario. As for clean, I'm not sure it really matters since I imagine Dockerfiles should pull a clean base image?

Yea I realized that afterwards. I am currently rewriting the whole thing to be more production ready and will create a pull request for that then. My plan is to use uwsgi as the web server and having it run as an unprivileged user within the container. The container will share a volume with the host OS to keep persistent storage.
I may also create a script to setup a systemd-nspawn container down the road, not sure yet though.

Also I was having an issue with just having update and upgrade. It was looking for an older version of something... can't remember exactly what but adding the clean before update and upgrade fixed it.


New structure is good, now we need a README

Please add a detailed README file in the main folder describing the project.

I've added a new README! Chek it out! ;)
Closed in: ee854e7c2d9c648e61e2572a37e77e3774830801.


[sigh] skip cert verification on linux & Windows

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[ ] I've updated the documentation if necessary.

Motivation and Context

Resolved #19114
Description

Skip certificate validation on Linux & Windows
Testing Steps

@googlebot I signed it!

@joshdholtz I think the failing test is unrelated to the changes. Can you please help? 🙂

@googlebot I consent.

@joshdholtz Thanks a lot! This looks great 💪


Add language Portuguese/BR

I will add a translation into Portuguese for Brazil (pt-br). I think it would be interesting for the community.

@acacio90 thanks, you have the instructions about contributing a translation in Readme.md
first create a fork, and do not forget that commits need to be signed...


🏎 Background Thread Skia Rendering

This PR implements support for rendering on a separate background thread. The new rendering pipeline is as the following:

Each Skia View is notified on vsync on the main thread
On each vsync update we check if there are any pending repaint requests for a given view (a Value was changed, a command was sent to repaint, mouse events etc.)
If there is a repaint request waiting, we’ll schedule a call to the Javascript draw method for that specific view on the JS thread.
The JS thread calls repaint, and instead of repainting to the underlying hardware it repaints on a “virtual” canvas using a Skia class called SkPicture - which can record drawing commands and replay them on a another surface / canvas.
A message is then dispatched to the render thread (which is a separate thread only doing Skia rendering) - with the SkPicture created on the JS thread
The render thread will render the SkPicture on the GPU surface / canvas in the background.

In addition this PR also includes a few optimisations found when profiling rendering:

The JsiHostObject class now contains optimisations and explicit declarations to make sure property/function lookups are as fast as possible.

Looks great. I'm pretty excited about this new feature. Pretty straightforward.

Thanks :)

My only question is: could/should the SkPicture be available to be used in makeImageSnapshot if needed?

I don't think it is necessary, since when making snapshots we're able to draw directly onto a raster surface (bitmap data), so there is no need to take the route through SkPicture I think. If we find issues with the DisplacementMap that can be solved by using a more centralised route I'm of course all in :)

Not a big deal but sometimes on start this is the debug state.

Not a big deal but sometimes on start this is the debug state.

Fixed :) :)

Nice, will test it now


Fixes: Allow initial state to include multiple lines of text

Allow initial state to include multiple lines of text and correctly split into codeLine blocks.
closes https://github.com/GitbookIO/slate-edit-code/issues/32

Fix #33 as well

I spent another 2 hours looking at this, can't for the life of me figure out why the specs are failing - the nodes past the code_line just seem to disappear. Debugging slate schemas is a nightmare.

Ah... sorry you had to hit your head on that... Slate already normalizes any mixed blocks and texts. So the first approach was enough already (even if it's not optimal, since we lose some content)

Ah, well I guess I learnt that Slate quirk the hard way. Thanks for the merge!


Jupyterlab extension script for Studio is incompatible

v0.20 adds support for jupyterlab v2 and drops support for v1. Since studio is still on v1 we should keep the installation script pinned to 0.19

Just tested this, the start.sh script does not work with the default version of juypterlab in sagemaker as a lifecycle configuration:
`2022-01-12T22:19:11.655-08:00	Collecting https://github.com/aws-samples/sagemaker-run-notebook/releases/download/v0.20.0/sagemaker_run_notebook-0.20.0.tar.gz Downloading https://github.com/aws-samples/sagemaker-run-notebook/releases/download/v0.20.0/sagemaker_run_notebook-0.20.0.tar.gz (64 kB) Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done'
2022-01-12T22:19:11.655-08:00	Requirement already satisfied: boto3>=1.10.44 in ./anaconda3/envs/JupyterSystemEnv/lib/python3.7/site-packages (from sagemaker-run-notebook==0.20.0) (1.20.25)
2022-01-12T22:19:11.655-08:00	Requirement already satisfied: botocore<1.24.0,>=1.23.25 in ./anaconda3/envs/JupyterSystemEnv/lib/python3.7/site-packages (from boto3>=1.10.44->sagemaker-run-notebook==0.20.0) (1.23.25)
2022-01-12T22:19:11.655-08:00	Requirement already satisfied: s3transfer<0.6.0,>=0.5.0 in ./anaconda3/envs/JupyterSystemEnv/lib/python3.7/site-packages (from boto3>=1.10.44->sagemaker-run-notebook==0.20.0) (0.5.0)
2022-01-12T22:19:11.655-08:00	Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in ./anaconda3/envs/JupyterSystemEnv/lib/python3.7/site-packages (from boto3>=1.10.44->sagemaker-run-notebook==0.20.0) (0.10.0)
2022-01-12T22:19:11.655-08:00	Requirement already satisfied: urllib3<1.27,>=1.25.4 in ./anaconda3/envs/JupyterSystemEnv/lib/python3.7/site-packages (from botocore<1.24.0,>=1.23.25->boto3>=1.10.44->sagemaker-run-notebook==0.20.0) (1.26.7)
2022-01-12T22:19:11.905-08:00	Requirement already satisfied: python-dateutil<3.0.0,>=2.1 in ./anaconda3/envs/JupyterSystemEnv/lib/python3.7/site-packages (from botocore<1.24.0,>=1.23.25->boto3>=1.10.44->sagemaker-run-notebook==0.20.0) (2.8.2)
2022-01-12T22:19:11.905-08:00	Requirement already satisfied: six>=1.5 in ./anaconda3/envs/JupyterSystemEnv/lib/python3.7/site-packages (from python-dateutil<3.0.0,>=2.1->botocore<1.24.0,>=1.23.25->boto3>=1.10.44->sagemaker-run-notebook==0.20.0) (1.16.0)
2022-01-12T22:19:12.905-08:00	Building wheels for collected packages: sagemaker-run-notebook Building wheel for sagemaker-run-notebook (setup.py): started Building wheel for sagemaker-run-notebook (setup.py): finished with status 'done' Created wheel for sagemaker-run-notebook: filename=sagemaker_run_notebook-0.20.0-py3-none-any.whl size=68779 sha256=ecfdd86929a17f9de4898f470430d0bc48790cdc36c10e2f900597bc67bde654 Stored in directory: /home/ec2-user/.cache/pip/wheels/0e/bb/75/ab97750fcde4102926b1864a0fab7580cd2cf72ca6045ded16
2022-01-12T22:19:17.424-08:00	Successfully built sagemaker-run-notebook
2022-01-12T22:19:17.674-08:00	Installing collected packages: sagemaker-run-notebook
2022-01-12T22:19:20.677-08:00	Successfully installed sagemaker-run-notebook-0.20.0
2022-01-12T22:19:20.677-08:00	[LabBuildApp] WARNING | Config option kernel_spec_manager_class not recognized by LabBuildApp.
2022-01-12T22:19:20.677-08:00	[LabBuildApp] JupyterLab 1.2.21
2022-01-12T22:19:22.178-08:00	[LabBuildApp] Building in /home/ec2-user/anaconda3/envs/JupyterSystemEnv/share/jupyter/lab
2022-01-12T22:19:22.447-08:00	[LabBuildApp] Building jupyterlab assets (build:prod:minimize)
2022-01-12T22:19:22.447-08:00	[LabBuildApp] WARNING |
2022-01-12T22:19:22.447-08:00<EMAIL_ADDRESS>is not compatible with the current JupyterLab`

This will be fixed by rolling forward to JupyterLab 3 in the next release.

v0.22.0 is now released with JupyterLab 3.x support. The new lifecycle script fixes this issue.


kapacitor upgrade

I assume from the sophomoric text in https://docs.influxdata.com/kapacitor/v1.3/administration/upgrading/ and the change log on github
That a yum upgrade will just work and will not screw up any configuration or existing tick files?

@mpechner --- please let us know if you feel that this particular content now meets your needs.


Making update alias work for more distributions

Pacman was already there for Arch.
Apt is intended for newer versions of Ubuntu.
Apt-get is intended for Debian older versions of Ubuntu.
Dnf is intended for newer versions of Fedora.
Yum is intended for RHEL/CentOS and older versions of Fedora.

This is a much more elegant solution than using uname. Planning to merge.


Issue disabling advertised listener

What happened?
We have enabled multiple listeners in the redpanda  and disabled the advertised listener for mtlstest listener. In the generated redpanda configuration the the internall listener is removed from redpanda configuration for disabled advertised listener: mtlstest.
What did you expect to happen?
The listener port is removed from LB port mappingsr, no advertised listener is added for the disabled listener, but an internal listener is added for disabled listener.
But we need multiple options for managing advertised listeners' visibility:

Disable the external port mapping in LB but keep the advertised listener for use cases as custom ingress controllers/application gateways.
Disable the external listener: no port mapping in LB,  no advertised listener

How can we reproduce it (as minimally and precisely as possible)?. Please include values file.

The external listener is disabled for  mildest  listener
external:
      default:
        enabled: true
        # -- The port used for external client connections.
        port: 9094
        # prefixTemplate: ""
        # -- If undefined, `listeners.kafka.external.default.port` is used.
        advertisedPorts:
        - 443
        tls:
          # enabled: true
          cert: external
        # default is "sasl"
        authenticationMethod: "sasl"
      mtlstest:
        enabled: false
        # -- The port used for external client connections.
        port: 9194
        # prefixTemplate: ""
        # -- If undefined, `listeners.kafka.external.default.port` is used.
        advertisedPorts:
        - 443
        tls:
          enabled: true
          cert: external
          requireClientAuth: true
        # default is "sasl"
        authenticationMethod: "mtls_identity"

The redpanda generated configuration:  The internal mtlstest listener is removed from redpanda configuration, but we want only to remove from LB configuration and keep the advertised listeners.
      kafka_api:
      - address: <IP_ADDRESS>
        name: internal
        port: 9093
      - address: <IP_ADDRESS>
        authentication_method: sasl
        name: default
        port: 9094

Anything else we need to know?
5.8.12
Which are the affected charts?
Redpanda
Chart Version(s)
5.8.12
Cloud provider
AKS
JIRA Link: K8S-407

We don't currently expose a way to control which listeners appear within the Service port list.
The easiest way to work around this right now would be to disable the external Service entirely and manage the Service yourself.
external:
  enabled: false
---
# Some other yaml file that you kubectl apply -f
apiVersion: v1
kind: Service
metadata:
  annotations: {}
  labels: {}
  name: my-custom-service
spec:
  ports: [] # Your Ports here
  selector: {} # You can copy the selectors that the chart users or copy labels from commonLabels.
  type: ClusterIP


Bridge Callback Set after upgrade to integration newest ver always is off

Bridge Callback Set after install itegration u[grade is always off. After update always was ON. Integration working and is possible open lock via HA and all seems to worling ok.

Please update to 0.3.4. Should be fixed now

updated to 0.3.4 and problem fixed. big thanks for quick action, have a nice day