[Bug]: Java BundleProcessorCache evicts all processors for a bundle descriptor id after 1 minute of idleness

What happened?
A timeout of 1 minute is specified here:
https://github.com/apache/beam/blob/master/sdks/java/harness/src/main/java/org/apache/beam/fn/harness/control/ProcessBundleHandler.java#L923
The key of this cache is the bundle descriptor id (fused stage) and the value is a list of BundleProcessors cached.  This means that if we don't process a stage for a minute all of the bundle processors are destroyed. For long-lived streaming pipelines this is wasteful as stages are processed in parallel and if were previously processed, will likely process again.  Creating a BundleProcessor involves constructing user DoFn and running Setup method so it is non-trivial.
Some improvements:

increase the timeout for streaming pipelines by default or make it runner configurable
don't throw away the entire list of cached BundleProcessors on expiration but perhaps just remove the last processor.

Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[ ] Component: Python SDK
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

could introduce a way to track the frequency of use for each Bundle processor and only remove those that haven't been utilized for a longer period, rather than a strict one-minute rule.

What's the comparable lifetime in other contexts, e.g. Dataflow legacy worker streaming? Is there any eviction at all?

Dataflow streaming runner never times these out so that is certainly a valid option in my opinion.
Queue is here:
https://github.com/apache/beam/blob/add34385719e53e4cc728267bfd2d8e8730c7267/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/streaming/ComputationState.java#L46
Stored in map here:
https://github.com/apache/beam/blob/add34385719e53e4cc728267bfd2d8e8730c7267/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/StreamingDataflowWorker.java#L209
Neither of which have a timeout.
We add all successfully processed dofns back to the queue:
https://github.com/apache/beam/blob/add34385719e53e4cc728267bfd2d8e8730c7267/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/StreamingDataflowWorker.java#L1161

Yea, I mean for today we do know that there's a finite number of them since the graph cannot change dynamically. I don't have historical context, nor have I looked at the commit history, so I don't know if there is a specific motivation here. Lacking that, I also would favor copying something that is known good. Aka let us just not time them out. Or we could at least set it to, say, an hour. I suppose you can close up and free bounded sources that have completed, if that is not done some other way.


authenticate the remaining storage interactions

In #323 not all interactions were covered with authentication support because of ongoing refactoring of walproposer/walacceptor networking. So authentication was added to the following interactions:

zenith cli <-> pageserver
compute postgres <-> pageserver

The remaining parts are:

compute postgres <-> safekeeper
safekeeper <-> pageserver

Now safekeerer <-> pageserver part uses "hardcoded" token in passed to safekeeper via environment variable. Safekeeper should validate the token against distributed public key and pass it to pageserver in connections.
Should be done after #117

closing this as dup of https://github.com/neondatabase/neon/issues/1854
please reopen if you think something else is missing


Parse query expects int

Fix of phpstan/phpstan error: Parameter #2 $urlEncoding of function GuzzleHttp\Psr7\parse_query expects bool|string, int given.

Please fix the phpdoc description alignment. :)

@GrahamCampbell done :)

Thanks!

@sagikazarmark Could I kindly ask you to release a patch version so we can update our project and remove phpstan ignore? What is the schedule for next release?

@northys there are a few other PRs in the pipe. No ETA at the moment, but I also would like to see a release in the near future.


[WORKAROUND][MI100][MI200] Disable MIOpenGEMM convolutions for OCL BE (W/A for #1315). Disable iGemm ASM GTC XDLOPS convolutions for NCHW (W/A for #1317, SWDEV-312112, SWDEV-313696)

:warning: Alternative for #1318 (either this PR or #1318 can be merged)

W/A for #1315
W/A for #1317
W/A for https://ontrack-internal.amd.com/browse/SWDEV-312112
W/A for https://ontrack-internal.amd.com/browse/SWDEV-313696

Details

Disable MIOpenGEMM convolutions for xDLOPs GPUs (MI100/MI200) && OpenCL BE
Disable iGemm ASM GTC XDLOPS convolutions for NCHW configs (keep them enabled for NCHW)
[Jenkins] Add Fp32 Full tests stages for Opencl BE && MI100/MI200
[NFC] Fix comments related to WORKAROUND_MIOPENGEMM_SINCE_ROCM41

Needs to double-check if this really resolves #1315 and #1317. I will do that tomorrow.

https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1324 -> found a fix for SWDEV-312112

This unblocking PR is ready to go, please review!

Manually tested on MI200 node with OCL BE, all tests pass.

WORKAROUND_ISSUE_1317 must also disable test_regression_opencl_float_mi100 which is intended to test some NCHW configs on OCL BE with ConvAsmImplicitGemmGTCDynamicWrwXdlops (see #1012). The reason is that PR totally disables ConvAsmImplicitGemmGTCDynamic*Xdlops for NCHW && OCL.


:robot: Triggering CI on branch 'release-next' after synching to upstream/main

Needs https://github.com/openshift/release/pull/36408

/retest

/retest

/retest

OCF Webhook is merging this PR


[INTERNAL] node 19 on windows: use 19.5.0

With node version 19.6.0 issues came up which might be fixed with a future node version.
Therefore downgrading to 19.5.0.

Coverage: 94.623%. Remained the same when pulling 7e0eb9dccc2ff887b6c575bfa59a6ffad8e91e87 on workaround-node-19-windows into 14c5e5cbacf898fb10df4f51d3dd7926e6af5592 on main.


File Manager Reload

I'M currently using Brackets 1.0 version on Windows 8.1, having an issue with the File Manager
Issue Explain:
If i am working on any Project name(XYZ), later on if i switch to any other project name (ABC) using file explorer, then Editor windows is changed but their is no changed in the File Manager as their is no files tree open for project ABC, instead still showing the files tree for previously opened project XYZ.
Until i restart/reopen Brackets its not working/showing the currently selected project folder.
Please look into the matter.
Thanks
Kunal Sindhi
www.jankiphulkari.com
www.whatkhabar.com
www.facebook.com/k.sindhi89

Closing since there's been no response from the filer


Pixel-based color sampling for the Eyedropper tool

Since there's no way to obtain the color of a pixel from a rendered web page, the Eyedropper tool currently just grabs the fill color of the shape that's clicked on. It doesn't know if you are clicking on the stroke of a shape instead. Or if you are clicking on somewhere along a gradient where you'd expect to pick the interpolated color. (For gradients, we're just using the color on one end of the gradient.) Picking the exact color of the pixel under the mouse cursor would be a more useful behavior. Given the above-mentioned issue, there are two approaches with pros and cons:

Use the EyeDropper API which is supported on Chromium-based browsers.
Pro: works even outside the viewport or web browser entirely
Con: limited browser support (no Firefox and Safari)
Rasterize the document and render it to an off-screen canvas then sample the corresponding pixel colors from that, using the same code for exporting artwork as PNG/JPG (see #629). It'd have to re-render every time the canvas changes, in case the user pans/scrolls/zooms while picking colors. Be careful of possible DPI scaling-related gotchas.
Pro: works in all browsers
Con: possibly worse performance

The second option is probably a better long-term solution.

@Keavon Hey I'm interested in working on this!

Great! I recommend the more robust approach of rasterizing the artwork, as described in the second bullet point. Although admittedly that'll be a little more difficult, but it's the better solution. Feel free to ask how to get started on this and we can talk through it on Discord.

@jackiechen73 just checking if this is still in progress. No worries if not, I can always move it back to the Up For Grabs list so someone else can take it on.

@Keavon Still working on it! Got caught up with school and midterms for a bit but looking to finish this up soon

@Keavon just came across this it seems promising. https://github.com/canvg/canvg. Was going to start working on this but it seems like @jackiechen73 has it covered.

@Keavon just came across this it seems promising. https://github.com/canvg/canvg. Was going to start working on this but it seems like @jackiechen73 has it covered.

No need for a dependency, we can use the canvas API to render the SVG string from a blob URL as an image drawn to the canvas. It supports SVG as one of the file types. That's how we already save JPG and PNG from the export dialog.

@Keavon I think I'm going to drop this ticket -- tried implementing the second solution without much success :(


Adding all the script files/codes for the cs page, on a separate js file

Added on the same js file


docker-compose fr0tt/benotes:2.7.0-beta could not run with sqlite

I followed the guide on docker-compose BETA and it worked. But when switching to sqlite, the site is not working
Found no usable log during the investigation. Only this
laravel.log
[2023-05-20 10:34:36] production.ERROR: Database migration failed.

supervisord.log
2023-05-20 17:34:18 Migrate database...
2023-05-20 17:34:23 Database migration failed. Try again...
2023-05-20 17:34:29 Database migration failed. Try again...
2023-05-20 17:34:36 Database migration failed. Try again...
2023-05-20 17:34:36 Database migration failed.
2023-05-20 17:34:36 2023-05-20 10:34:36,494 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-05-20 17:34:36 2023-05-20 10:34:36,497 INFO supervisord started with pid 19
2023-05-20 17:34:37 2023-05-20 10:34:37,499 INFO spawned: 'nginx' with pid 20
2023-05-20 17:34:37 2023-05-20 10:34:37,502 INFO spawned: 'php-fpm' with pid 21
2023-05-20 17:34:38 2023-05-20 10:34:38,582 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-20 17:34:38 2023-05-20 10:34:38,582 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-20 17:35:04 <IP_ADDRESS> - - [20/May/2023:10:35:04 +0000] "GET / HTTP/1.1" 200 812 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "-"
2023-05-20 17:35:04 <IP_ADDRESS> - - [20/May/2023:10:35:04 +0000] "GET /api/auth/me HTTP/1.1" 401 5 "http://localhost:8000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "-"
2023-05-20 17:35:04 <IP_ADDRESS> - - [20/May/2023:10:35:04 +0000] "POST /api/auth/refresh HTTP/1.1" 500 6634 "http://localhost:8000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "-"

Scenarios that i tried with the same error described

Using the fresh compose, .env with only change DB_CONNECTION=sqlite & DB_DATABASE=storage/database.sqlite. Already ran "php artisan install" without any error in  terminal.
Same as above, but tried to "touch storage/database.sqlite && chown $user:$user storage/database.sqlite" before install.
Using the working pgsql, switch to sqlite as above, "php artisan install" again.

You're right.
It should work if you change in your .env file DB_DATABASE to /var/www/storage/database.sqlite

Thanks, its working now


add system set & icon

Probably added system set and plug-in icon

Probably because of prettier formatting, git said that it seems to have changed, but in fact only the icon and two snippets were added.

Sorry, you didn't reply for a long time ago, so tried to create a plugin by myself. But I don't think it's very good, it was deleted a long time ago. Please forgive me for doing this~

Forget it, I don't know what I'm thinking


[PROPOSAL] Internationalization

Would be cool also to be able to use the trans() helper to load translated content within a static site also...

I know this is old but I think this hasn't been addressed yet and it is preventing me from using Jigsaw in a lot of projects :(
Any idea to work something out with current implementation of Jigsaw? Any idea if this is ever gonna be solved?
Thank you!

Yes, it's the most-requested feature at the moment! Can you give a little more detail about what your needs are? We'd need to sort out how to define the current locale, presumably by specifying a language code as part of the URI; and then perhaps indicating which languages to use for a particular template by specifying the language codes in the YAML front matter of the template.

Oh, this is really great to hear!
I guess my needs are quite simple, nothing fancy:

Enable several languages
Defining the translated version of each page/content (Gettext with Poedit, maybe?)
Serving the translated content depending on the URI the user requested.

FYI I've been using LaravelLocalization since before Laravel introduced its custom translation system and it's been great. Actually way better than the built-in system.
Thank you :) and thanks for your quick response.

We're gonna be working on this feature soon, and would love to get input on what people think would be the most useful and user-friendly way to handle internationalization. Keeping close to Laravel's implementation of things like trans() is definitely a goal, and I personally don't have any experience w/ Poedit to know if that's applicable here or not. To those who are interested...how would you like to see internationalization implemented in Jigsaw?

Hi,
let me preface this by saying that I believe that Jigsaw as a static generator solves a real world need of people wanting to use Blade templating without the additional weight of unnecessary Laravel components, etc.
I personally like to use example.com/lang/ in my URLs to specify a language. It is a feature I'm missing in a lot of the static generators that avoid using nested collections or its equivalent. Here if I use language as a top-level collection, my URL structure immediately becomes very hard to structure as something as simple as baseURL/en/blog/post-title is no longer possible.
I really like the way Laravel let's users choose their own directory structure inside resources/views & their own way of creating URL slugs, making them as (non-)complicated (or even business specific) as they want. It's an opinionated feature I'd like to see implemented in some way.
For the folks that use trans(), I think the implementation closest to "the Laravel way" is the best, as this is how most people discover Blade & subsequently Jigsaw.

You can somewhat do this already, and in fact I wonder if having language as a collection isn't really the best solution for an internationalized site—considering that the number of languages is likely small, not subject to frequent change, and doesn't require many of the features that collections is designed to provide (you don't generally need to do things like change the sort order of languages, see a paginated subset of languages, count them, etc.). I'm not opposed to considering the concept of nested collections, but it would be worth considering other scenarios where that would be useful, before we go down that road.
To do what you outlined above, you could do something like this. In config.php:
<?php

return [
    'baseUrl' => 'https://example.com',
    'path' => '{language}/{type}/{-title}',
    'collections' => [
        'posts-sl' => [
            'type' => 'blog',
            'language' => 'sl',
        ],

        'posts-en' => [
            'type' => 'blog',
            'language' => 'en',
        ],
    ],
];

...and then store your translated blog posts in _posts-sl and _posts-en, extending a common template like _layouts.post or, if the post template had language-specific components, _layouts.sl.post and _layouts.en.post. So your directory structure would look something like this:

which would build to this:

Note that I'm using path at the top-level in config.php and allowing it to cascade to the collections; you could also just define the path within each collection. Also note that I used the token {type} instead of what I wanted to use, {section}, since section is a reserved word by Jigsaw...something we should probably change.
I threw in non-collection translated pages as well, about.md and o.md.
So you'd end up with:
example.com/en/about
example.com/en/blog/my-first-post
example.com/sl/o
example.com/sl/blog/moj-prvi-post

The issues I'd like to sort out are:

Would a collection of languages offer any benefits over a solution like this
Are there other potential use cases for "nested" collections
As far as internationalization is concerned, what would be a good structure for storing the translated content; is it generally preferable to keep translated content in separate files, or in the same file but somehow designated by language, or in an array of strings, or (probably) all three?

@damiani Your proposition perfectly describes my use case! Also, actually including Slovene text in them, made me laugh. You've made my day again :)

Hi again,
I'm giving it a try and outlining my concerns once tested. But I think that, using this approach, there's no way I could provide a user (ang Google) the alternative lang link (i.e. en/blog/my-first-post --> sl/blog/moj-prvi-post). This is quite a caveat imho.
But just as I said, i'll give it a go and come back with some ideas or feedback.
Thanks!

@morpheus7CS Blame Google for any translation errors :)
@afontcu Yes, please report back with your thoughts. You could have alternative links for users/Google pretty easily if you weren't customizing the blog post title by language (i.e. en/blog/my-first-post and sl/blog/my-first-post, but like I said, I'm not well-versed enough in the requirements of a fully-internationalized site to know the nuances. So I'm very interested in your input here.

Hi there! Been testing the approach outlined above and while it covers 80% of the requirements of a translated site, there are some important flaws:

As we discussed, the inability to provide alternatives (translated) links if permalink is different is a major issue. Internationalization makes really no sense if every permalink has to be the same, or if we cannot provide alternative links.
I'm guessing this would need some logic which cannot be solved by setting Collections or some kind of settings, am I right?

You are right when you say that "the number of languages is likely small, not subject to frequent change, and doesn't require many of the features that collections is designed to provide". But languages should offer some kind of static information, such as locale code ('es_ES', 'en_GB', 'de_DE') or native name ('Español', 'English, 'Deutsch`). I may be able to get this by populating the Settings file, but doesn't feel right.

I feel bad when I have to duplicate (or more) my pages schema just to add translations, where an array would be enough if implement. I'm thinkin of some function such as _t($title), where $title gets its value from a lang array, with as many positions as active languages.

Thank you very much!

I'm also building a multi-locale site, and realized that you can include Illuminate\Translation component, and then define a translation helper in config.php, as in:
use Illuminate\Filesystem\Filesystem;
use Illuminate\Translation\FileLoader;
use Illuminate\Translation\Translator;

return [
    '__' => function ($page, $key, $locale = 'en') {
        // Prepare the FileLoader
        $loader = new FileLoader(new Filesystem(), './lang');

        // Register the Translator
        $translator = new Translator($loader, $locale);
        return $translator->get($key);
    },
];

Then you can define a 'master' layout for each page (e.g. about-us, services, home), an extend the layout specifying only page metadata. For example, you can have a master 'about-us' layout in source/_about-us.blade.php, with something like:
@extends('_layouts.master')

@section('body')

{{ $page->__('some.key', $page->locale) }}

@endsection

And locale-specific pages in source/en/about-us.blade.php
---
extends: '_about-us'
locale: de
---

and source/de/ueber-uns.blade.php:
---
extends: '_about-us'
locale: de
---

With this setup, translation strings can be organized in the same way as in a regular Laravel project.
This is something that I only quickly tested, and it works. I'm not sure how slow the build will get with more translation strings - it can probaly be optimized by loading FileLoader and FileSystem once.

I like @amadeann 's approach, but what if you want to translate a whole post with HTML inside (e.g. for formatting)? Do you keep all that in the translation strings?

I like both approaches, but in @amadeann's approach: what if you want to translate a whole post with HTML inside (e.g. for formatting)? Do you keep all that in the translation strings?

If the formatting is very different between languages, and the layout changes as well, then just create separate pages. If you need minor formatting (like wrapping some text in ), then get the unescaped translation string (see Laravel docs): Hello, {{ $name }}..

I followed @damiani 's suggestions, but how do you access the blog posts then?
If the blog is just called blog you can access it with $blog. But when it's blog-en, $blogEn won't work for me.


Pure Cool Link unavailable after HA reboot

Hi,
we have 3 Pure Cool Link in our house. After a reboot two of them show up but cannot be controlled e.g. fan speed or osszilation. The third one does not even show up.
Also relinking with a new/additional integration does lead nowhere.
I then tried to update to the latest version of HACS and your integration. Same story. Any hint?
Cheers Frank.

Also when I try to setup Dyson Cloud the authenification fails, no matter wether I'm logged in in the app or not.

Works again. For the 3rd one a power cycle did the trick. For the other two there must have been gone something terribly wrong (during an update?). I had to manually work on entity names to get it right again.


Xinmo Dual Arcade left/down vs right/up issue

anybody knows a proper txt for that controller ?
the 1P stick mixes up left/right and up/down as the same inputs, ignoring the directions, resulting in only left/bottom working
03000000c0160000e105000001010000,Xin-Mo Xin-Mo Dual Arcade,platform:Linux,b:b4,a:b3,x:b0,leftshoulder:b2,dpup:a1,dpdown:a1,start:b7,dpright:a0,rightshoulder:b5,guide:b9,y:b1,back:b6,dpleft:a0,

Try this
03000000c0160000e105000001010000,Xin-Mo Xin-Mo Dual Arcade,platform:Linux,b:b4,a:b3,x:b0,leftshoulder:b2,dpup:a0,dpdown:a0,start:b7,dpright:a1,rightshoulder:b5,guide:b9,y:b1,back:b6,dpleft:a1,

sorry, not sure to find the answer in those posts
that controller works fine anywhere with its mapping in retroarch or emulationstation,
the issue comes with the new gamecontrollerdb.txt (PPSSPPSDL 1.3 specifically) : the above mapping does not work as it does not seem capable to manage negative values (1 positive value per axis is not enough)
a correct file should probably be something like the below which is not possible now :
03000000c0160000e105000001010000,Xin-Mo Xin-Mo Dual Arcade,platform:Linux,b:b4,a:b3,x:b0,leftshoulder:b2,dpup:a1,dpdown:a(-1),start:b7,dpright:a0,rightshoulder:b5,guide:b9,y:b1,back:b6,dpleft:a(-0),

Please open a PR with adequate mappings using the latest SDL version which supports the adequate modifiers.


Administratively set global models should not have settable org/is_global fields

In GitLab by @jasonpagetas on Jul 15, 2024, 22:53
When creating a new Device type, or device model you must select an organization before you can submit. Regardless of that choice the option is reverted back to global once submitted and there is no way to unselect this option.
Suggest this changes to include a check box for "is global" which then removes the organisation dropdown
Tasks

Remove form fields organization and is_global from:

[x] manufacturer

[x] device type

[x] device model

[x] software categories

added 1m of time spent

In GitLab by @jasonpagetas on Jul 15, 2024, 22:53
marked this issue as related to #74

marked the checklist item device model as completed

marked the checklist item device type as completed

mentioned in commit 7b26fac73d38d9644e20db0b3a85b4def73c9bf1

marked the checklist item software categories as completed

marked the checklist item manufacturer as completed

added 1m of time spent


$state.go with {reload: true} messes with $ionicHistory.goBack()

Short description of the problem:
I'm trying to navigate from the state app.profile.id with parameter {id: x} to the state app.profile.id with parameter {id: y}. I do it by $state.go('app.profile.id', {id: y}, {reload: true}) When I console.log the history stack, everything seems right (current view is state with y and back view is the state with x). The back button appears however the transition to the back view doesn't happen. When I hit the back button and manually refresh the data (I have pull down to refresh implemented), the data seems to be changed to x. Also, when I hit the back button one more time, this time nothing happens at all, the goBack() completely breaks. I have cache enabled.
What behavior are you expecting?
It should navigate back from page with id y to page with id x, then the back button should keep working as it should.
Steps to reproduce:

Create states, one with an id. (app.home, app.profile.id)
Enable caching
Enable back button
Have a link from home to profile page with id x, and from there a link to profile page with id y
Once clicked, execute $state.go with reload: true
Try clicking on the back button page with id y. The transition to x will not happen (even if the data changed to x)
Click back one more time, nothing happens.

Which Ionic Version? 1.2.4
Run ionic info from terminal/cmd prompt: (paste output below)
Your system information:

Cordova CLI: 5.4.1
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.0
Ionic Version: 1.2.4
Ionic CLI Version: 1.7.12
Ionic App Lib Version: 0.6.5
ios-deploy version: 1.8.2
ios-sim version: 5.0.3
OS: Mac OS X El Capitan
Node Version: v4.1.1
Xcode version: Xcode 7.2 Build version 7C68

Hi @oguzgelal 😄 ,
Why are you using the reload parameter?  Does your app work without it?
Thanks,
Dan

Hello @danbucholtz, thanks for your reply 😊  I'm using the reload parameter because the transition doesn't happen without it.

@oguzgelal, can you make a super simple codepen or plunkr for me?  I am having a hard time visualizing this.
Thanks,
Dan

@danbucholtz Sorry for the late reply.
Well, this case might be a little hard to reproduce with plunker because of the database connections. However I created a simple screencast to make the issue easier to visualise. Here they are:
This is the build with reload: true

This is the build without reload: true

This issue was moved to driftyco/ionic-v1#149


qt/locale: Change the name prefix from bitcoin_ to dogecoin_

Hi, Can we change the name in src/qt/locale/bitcoin_ta.ts to src/qt/locale/dogecoin_ta.ts. Are we using the same as in bitcoin so that it stays the same?

Many of the translations originate from bitcoin. I'd like to keep it as-is for 1.14, but we can consider this for 1.21. We can discuss the pros and cons of this in #2273 perhaps?


ReadAssignmentFromRoutes and AddDisjunction

When I add disjunction to model, ReadAssignmentFromRoutes always return null
model.AddDisjunction(new int[] {3, 5, 7}, 100000000);
var assignment = model.ReadAssignmentFromRoutes(routesArray, false);

Are you sure your routes are valid with respect to the disjunction added ?
If two or more of 3, 5, 7 are in routes then it's not valid (at most one of
them can be in a route).
On Mon, Jul 11, 2016 at 6:36 AM, KarolK<EMAIL_ADDRESS>wrote:

When I add disjunction to model, ReadAssignmentFromRoutes always return
null
model.AddDisjunction(new int[] {3, 5, 7}, 100000000);
var assignment = model.ReadAssignmentFromRoutes(routesArray, false);
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/208, or mute the thread
https://github.com/notifications/unsubscribe/AKjyUgZSC-4vESSDYceLbVjcCA_UBt57ks5qUchfgaJpZM4JJBnT
.

{3, 5, 7} are not in initial routes.

It's my mistake. Everything works well.


Abstract away Request objs in the ConfigureIndex method

Problem
Currently, when users call the ConfigureIndex method (in Pinecone.java), they have to pass a ConfigureIndexRequest object. This object in turn, needs to be created with a ConfigureIndexRequestSpec object, which itself needs to be created with a ConfigureIndexRequestSpec, WHICH THEN needs to be created with a ConfigureIndexRequestSpecPod object.
This is hella cumbersome.
Solution
This PR abstracts away these Request objects, so the user doesn't have to deal with them at all. Instead, the user can simply call the ConfigureIndex method 1 of 2 ways:

ConfigureIndex("indexName", someNumberOfReplicas)
ConfigureIndex("indexName", "somePodType")

Relevant Asana ticket: https://app.asana.com/0/1203260648987893/1206994598304485/f
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Infrastructure change (CI configs, etc)
[ ] Non-code change (docs, etc)
[ ] None of the above: (explain here)

Test Plan
Unit tests and updated integration tests included in PR.

@austin-denoble re: this question, I just used the one in IntelliJ. The one you get to by doing Code > Reformat file


Update MapManager.java

And why you did two separate pull requests instead of one with your all changes? This is not good practise.

First time using this function


fix: windows incompatibilities

Hi guys! Thanks for the project.
Today i managed to work with unoserver in windows, and i have a fell breakpoints.

In server.py when executing in windows the command f"-env:UserInstallation={self.tmp_uri}" displays a strange error see example, seems not necessary for soffice.exe that command. So, i added a Linux verification to append it.

In server.py when executing in windows, the process crashes because not exists a signal SIGHUP in Windows envrionment, so i added a verification as well.

By change that, works like a charm! Please consider the pull request for Windows users. Thanks again!
Edit 1: The issue with Windows is because the temporary uri generation gives an invalid path to process creation, causing the error, commit fixed.

Fixed. Please review the changes!

Thanks, looks pretty good now!
Have you tested the changes? In particular, I wasn't very sure if the pathlib bit would actually work on Windows.

@mara004 Yes, i'm currently using in Windows, it's working fine!! ;)

@ankology Great, thanks for your work!

Thanks to everyone for this!


Karate-Gatling struggles to post xml at high rate compared to other requests

Issue first noticed on the develop branch, however as I know that the rewrite branch is the priority I have been able to replicate this here (commit 6ce22ce1).
Attached is a directory which should be copied to examples/gatling/src/test/java/example.
example.zip
I can provide a full working example project if required.
Please note that to run my example I had to delete examples/gatling/src/test/java/mock (this no longer works due to prior changes on this branch), and I also found that I had to add the javax.xml.bind jaxb-api dependency to karate-core to be able to build (which is also unrelated to the code I've added).
I am trying to simulate very high traffic e.g. 1000 requests per second (ramp 10,000 users in 10 seconds), and noticed that karate-gatling struggles when posting xml, even when using a mock server.
Making a simple get request, a post with an empty string, and a post with simple json ({ foo: bar }) always seems to take ~10-11 seconds as expected e.g. (run the following from example/gatling)
$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=get.feature

Simulation example.ExampleSimulation completed in 10 seconds
Parsing log file(s)...
Parsing log file(s) done
Generating reports...

================================================================================
---- Global Information --------------------------------------------------------
> request count                                      10000 (OK=10000  KO=0     )
> min response time                                      1 (OK=1      KO=-     )
> max response time                                    379 (OK=379    KO=-     )
> mean response time                                     7 (OK=7      KO=-     )
> std deviation                                         15 (OK=15     KO=-     )
> response time 50th percentile                          4 (OK=4      KO=-     )
> response time 75th percentile                          6 (OK=6      KO=-     )
> response time 95th percentile                         21 (OK=21     KO=-     )
> response time 99th percentile                         37 (OK=37     KO=-     )
> mean requests/sec                                909.091 (OK=909.091 KO=-     )

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postString.feature

Simulation example.ExampleSimulation completed in 11 seconds

---- Global Information --------------------------------------------------------
> request count                                      10000 (OK=10000  KO=0     )
> min response time                                      2 (OK=2      KO=-     )
> max response time                                    344 (OK=344    KO=-     )
> mean response time                                     7 (OK=7      KO=-     )
> std deviation                                         16 (OK=16     KO=-     )
> response time 50th percentile                          5 (OK=5      KO=-     )
> response time 75th percentile                          6 (OK=6      KO=-     )
> response time 95th percentile                         20 (OK=20     KO=-     )
> response time 99th percentile                         36 (OK=36     KO=-     )
> mean requests/sec                                833.333 (OK=833.333 KO=-     )

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postJson.feature

Simulation example.ExampleSimulation completed in 11 seconds

---- Global Information --------------------------------------------------------
> request count                                      10000 (OK=10000  KO=0     )
> min response time                                      1 (OK=1      KO=-     )
> max response time                                    678 (OK=678    KO=-     )
> mean response time                                     8 (OK=8      KO=-     )
> std deviation                                         28 (OK=28     KO=-     )
> response time 50th percentile                          4 (OK=4      KO=-     )
> response time 75th percentile                          6 (OK=6      KO=-     )
> response time 95th percentile                         20 (OK=20     KO=-     )
> response time 99th percentile                         49 (OK=49     KO=-     )
> mean requests/sec                                833.333 (OK=833.333 KO=-     )

Posting simple xml (<foo></foo>) however takes about a minute
$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postXml.feature

Simulation example.ExampleSimulation completed in 56 seconds

---- Global Information --------------------------------------------------------
> request count                                      10000 (OK=10000  KO=0     )
> min response time                                      1 (OK=1      KO=-     )
> max response time                                    400 (OK=400    KO=-     )
> mean response time                                     5 (OK=5      KO=-     )
> std deviation                                         16 (OK=16     KO=-     )
> response time 50th percentile                          3 (OK=3      KO=-     )
> response time 75th percentile                          5 (OK=5      KO=-     )
> response time 95th percentile                         13 (OK=13     KO=-     )
> response time 99th percentile                         38 (OK=38     KO=-     )
> mean requests/sec                                175.439 (OK=175.439 KO=-     )

The response times in each case appear to be approximately the same, therefore it looks like the difference must be due to constructing/making the request.
Note that I haven't tried this for other HTTP method types e.g. delete.

@theathlete3141 the rate I'm going likely to look at this next year :P - one suggestion is try to form the payload as a string (use text if needed) to avoid XML parsing - as always any investigation or better still code contribution from you or anyone else is welcome. all the best !

@theathlete3141 If you put the payload in a variable instead of the request ligne :
Background:
    * url karate.properties['mock.server.url']
    * def xmlPayload = "<foo></foo>"

  Scenario:
    Given path 'test'
    And request xmlPayload
    When method post
    Then status 200
    And match response.success == true

The speed is better, but not yet fast.
================================================================================
---- Global Information --------------------------------------------------------
> request count                                      10000 (OK=10000  KO=0     )
> min response time                                      0 (OK=0      KO=-     )
> max response time                                     80 (OK=80     KO=-     )
> mean response time                                     2 (OK=2      KO=-     )
> std deviation                                          4 (OK=4      KO=-     )
> response time 50th percentile                          1 (OK=1      KO=-     )
> response time 75th percentile                          2 (OK=2      KO=-     )
> response time 95th percentile                          8 (OK=8      KO=-     )
> response time 99th percentile                         19 (OK=19     KO=-     )
> mean requests/sec                                357.143 (OK=357.143 KO=-     )
---- Response Time Distribution ------------------------------------------------
> t < 800 ms                                         10000 (100%)
> 800 ms < t < 1200 ms                                   0 (  0%)
> t > 1200 ms                                            0 (  0%)
> failed                                                 0 (  0%)
================================================================================

But, as a lot of work is done on XML payload to parse it, a lot of time is wasted in your case.

Thank you both for your suggestions. I've found that the way in which the request is formed makes a big difference to how fast they can be executed
postXml.feature
From the original example
Feature:

  Background:
    * url karate.properties['mock.server.url']

  Scenario:
    Given path 'test'
    And request
    """
    <foo>
    </foo>
    """
    When method post
    Then status 200
    And match response.success == true

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postXml.feature

Simulation example.ExampleSimulation completed in 56 seconds

postXml2.feature
Modifying postXml.feature so that the payload is on one line
Feature:

  Background:
    * url karate.properties['mock.server.url']

  Scenario:
    Given path 'test'
    And request '<foo></foo>'
    When method post
    Then status 200
    And match response.success == true

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postXml2.feature

Simulation example.ExampleSimulation completed in 33 seconds

postXml3.feature
Modifying postXml.feature to define the payload separately to setting the request
Feature:

  Background:
    * url karate.properties['mock.server.url']

  Scenario:
    Given path 'test'
    And def payload =
    """
    <foo>
    </foo>
    """
    And request payload
    When method post
    Then status 200
    And match response.success == true

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postXml3.feature

Simulation example.ExampleSimulation completed in 57 seconds

postXml4.feature
Modifying postXml3.feature so that the payload is on one line
Feature:

  Background:
    * url karate.properties['mock.server.url']

  Scenario:
    Given path 'test'
    And def payload = '<foo></foo>'
    And request payload
    When method post
    Then status 200
    And match response.success == true

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postXml4.feature

Simulation example.ExampleSimulation completed in 36 seconds

postXml5.feature
Modifying postXml3.feature to use text rather than def
Feature:

  Background:
    * url karate.properties['mock.server.url']

  Scenario:
    Given path 'test'
    And text payload =
    """
    <foo>
    </foo>
    """
    And request payload
    When method post
    Then status 200
    And match response.success == true

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postXml5.feature

Simulation example.ExampleSimulation completed in 35 seconds

postXml6.feature
Modifying postXml5.feature so that the payload is on one line
Feature:

  Background:
    * url karate.properties['mock.server.url']

  Scenario:
    Given path 'test'
    And text payload = '<foo></foo>'
    And request payload
    When method post
    Then status 200
    And match response.success == true

$ mvn test -D gatling.simulationClass=example.ExampleSimulation -D scenario=postXml6.feature

The logs contain the error
ERROR com.intuit.karate - classpath:example/postXml6.feature:8
And text payload = '<foo></foo>'
no step-definition method match found for: text payload = '<foo></foo>'

Still a long way off the ~10 seconds as seen for other payload types, but at least it's possible to improve upon the orignal ~1 minute.

if the response is xml - karate will attempt to always parse it by default which will explain that
there is an experimental way to have more control over the request (approximate code below) which may be interesting to explore
* def myUrl = karate.properties['mock.server.url']
* karate.http(myUrl).body('<some>xml</some>').invoke('post')

.. but may not be sending the stats to gatling ;) I'm not too worried about this use-case a) in real-life most systems would spend time waiting for responses b) in the worst case, just write a bit of Java code that makes the raw HTTP request and you publish the stats to the PerfContext manually.

In deed, this way it works:
  Background:
    * def myUrl = karate.properties['mock.server.url']
    * def fun = function(){ return karate.http(myUrl).body('<some>xml</some>').invoke('post') }

  Scenario:
    * call fun

---- manuallyPostXml.feature ---------------------------------------------------
[##########################################################################]100%
          waiting: 0      / active: 0      / done: 10000
================================================================================

Simulation example.ExampleSimulation completed in 29 seconds

But no results sent back to Gatling. I suppose it is normal, since it is not Gatling that actually send the request, but the current JRE.
By the way, is it possible to use Gatling Load Injectors through Karate?

@sixdouglas great, thanks for testing that out ! actually you can do this if you measure the time manually
* karate.capturePerfEvent('my xml request', startTimeMillis, endTimeMillis)

I'm not sure what you mean by load injectors, do you mean feeders ?

In deed, it works
Feature:

  Background:
    * def myUrl = karate.properties['mock.server.url']
    * def fun = function(){ let startTimeMillis = new Date().getTime(); karate.http(myUrl).body('<some>xml</some>').invoke('post'); karate.capturePerfEvent('my xml request', startTimeMillis, new Date().getTime()) }

  Scenario:
    * call fun

Simulation example.ExampleSimulation completed in 29 seconds
Parsing log file(s)...
Parsing log file(s) done
Generating reports...

================================================================================
---- Global Information --------------------------------------------------------
> request count                                      10000 (OK=10000  KO=0     )
> min response time                                     17 (OK=17     KO=-     )
> max response time                                    573 (OK=573    KO=-     )
> mean response time                                    31 (OK=31     KO=-     )
> std deviation                                         28 (OK=28     KO=-     )
> response time 50th percentile                         26 (OK=26     KO=-     )
> response time 75th percentile                         35 (OK=35     KO=-     )
> response time 95th percentile                         48 (OK=48     KO=-     )
> response time 99th percentile                         71 (OK=71     KO=-     )
> mean requests/sec                                333.333 (OK=333.333 KO=-     )
---- Response Time Distribution ------------------------------------------------
> t < 800 ms                                         10000 (100%)
> 800 ms < t < 1200 ms                                   0 (  0%)
> t > 1200 ms                                            0 (  0%)
> failed                                                 0 (  0%)
================================================================================

The results are collected, but the timing is still longer than with json payload.
When you want to apply a heavy load on a system, one Gatling Instance may not be enough. In this case, you can have multiple Gatling injectors (runners) and one Gatling master to give the tasks and collect statistics (more details here). Is it possible to achieve this using plain Karate?

@sixdouglas ah yes - this also is broken after the re-factoring, but you may find this interesting, last section covers gatling: https://github.com/intuit/karate/wiki/Distributed-Testing

closing as wontfix


Function 'ConvertAnimationToSchema' in the Runtime Converter doesn't iterate child nodes

It looks like this was fixed at some point.


Use `dump-emacs' in emacsWithPackages wrapper

Inspired by this comment on Reddit, https://www.reddit.com/r/emacs/comments/8ew9pu/looking_for_really_unorthodox_emacsd/dxyq1ot/, I think it might be useful to run dump-emacs inside the Emacs wrapper. We already byte compile everything in site-packages, but dump-emacs means that we can compile everything entirely into the $out/bin/emacs binary. Need to research how much performance benefit this actually gives but according to some random posts it could be huge.

Closing - gccemacs does this for us.


treewide: remove unused clang from build closure

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360711

x86_64-linux

:white_check_mark: 4 packages built:

helvum
niri
stardust-xr-kiara
xen-guest-agent

(The packages are all unavailable on darwin)


Open Beauty Facts preparation

I just suffixed every string that needs to be changed with _obf. Everything is still commented out.
I added the Open Beauty Facts logo

Is it possible to add commented out lines or will it create issues ?

why not create a fork for obf instead of only one repo for two apps ?

Maintenance efforts.

@teolemon and using another branch ?

Well this is a branch (obf-start) :-)
My point is that constantly rebasing the branch might be a pain.


Trinus Headtracking

heay guys,
I am working on setting up an Trinus VR, PS Move and Smartphone based VR setup.
I got the Move Controlers working and the HMD is working in the config tool as well.
My problem is that trinus is not getting any information from freePIE.
Wirh Riftcat everything works fine, but Trinus is not detecting anything.

hi,
first of all don't use trinus! use riftcat it works way better. and you wont have the freepie issue.


Error during installation

If I run the setup (pip install PCA9685-driver) the following error occures:
pi@raspberrypi:~/tmp $ pip install PCA9685-driver
Collecting PCA9685-driver
Downloading PCA9685-driver-1.1.0.tar.gz
Collecting smbus-cffi==0.5.1 (from PCA9685-driver)
Downloading smbus-cffi-0.5.1.tar.gz
    Complete output from command python setup.py egg_info:
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    Package libffi was not found in the pkg-config search path.
    Perhaps you should add the directory containing `libffi.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'libffi' found
    c/_cffi_backend.c:2:20: fatal error: Python.h: No such file or directory
    #include <Python.h>
                        ^
    compilation terminated.
    Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-build-59NF29/smbus-cffi/setup.py", line 48, in <module>
        'Topic :: System :: Hardware',
    File "/usr/lib/python2.7/distutils/core.py", line 111, in setup
        _setup_distribution = dist = klass(attrs)
    File "/usr/local/lib/python2.7/dist-packages/setuptools/dist.py", line 320, in __init__
        self.fetch_build_eggs(attrs['setup_requires'])
    File "/usr/local/lib/python2.7/dist-packages/setuptools/dist.py", line 377, in fetch_build_eggs
        replace_conflicting=True,
    File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 852, in resolve
        dist = best[req.key] = env.best_match(req, ws, installer)
    File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1124, in best_match
        return self.obtain(req, installer)
    File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1136, in obtain
        return installer(requirement)
    File "/usr/local/lib/python2.7/dist-packages/setuptools/dist.py", line 445, in fetch_build_egg
        return cmd.easy_install(req)
    File "/usr/local/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 673, in easy_install
        return self.install_item(spec, dist.location, tmpdir, deps)
    File "/usr/local/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 699, in install_item
        dists = self.install_eggs(spec, download, tmpdir)
    File "/usr/local/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 880, in install_eggs
        return self.build_and_install(setup_script, setup_base)
    File "/usr/local/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 1119, in build_and_install
        self.run_setup(setup_script, setup_base, args)
    File "/usr/local/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 1107, in run_setup
        raise DistutilsError("Setup script exited with %s" % (v.args[0],))
    distutils.errors.DistutilsError: Setup script exited with error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-59NF29/smbus-cffi/

How do I fix the problem?
It only occures on my Raspberry. On my main PC pip works fine.
Running pip as root doesn't change anything.

You must install libffi-dev
apt-get install libffi-dev

This didn't solve the problem 😞

Python developer packages are installed?
If not: sudo apt-get install python-dev (in case of python2)

It works.
The tool is awesome!


Assertion error when running the uatg from-config command

Chromite Bug Bounty

we have installed all the tools and their dependency.
we cloned the uatg repo and ran the uatg setup command.
we made the path corrections in config.ini file and also enabled few test cases in index.yaml
we tried to run the command "uatg from-config -c config.ini -v debug", but there is an assertion error. here is the error we got

Note:-  This error is only occurring only when we try generating a cache test case, Its able to generate test case for other module, like branch_predictor
We are using
uatg version - 1.3.0
python version - 3.8.10
This is the index.yaml file

This is the config.ini file

This is the core_config.yaml

Hi @Pruthvi-Raj-S
The version of UATG you are using is old. Please try the same with UATG 1.5.0 (current release), preferably in a new virtual environment.
Moreover, make sure you are using the dev branch of chromite_uatg_tests as well as the latest release of Chromite (using csr-box branch.
Let me know if it works.
Alenkruth

For UATG Version 1.5.0 you will also have to update your config.ini file. I am attaching a link to my config.ini. Since the documentation is pretty outdated, the docs does not have the latest template. Sorry about that.
config.ini
--Alenkruth

If you still face the issue even after trying all the above steps, Please send a complete log of UATG's execution.
uatg from-config -c config.ini -v debug &> log.txt should help you get the log file.
-- Alenkruth

Hi @Alenkruth
I did update the uatg and also replaced config.ini file, but for the path to the yaml files containing DUT Configuration. I had to rebuild the chromite core.
After cloning the chromite repo and changing the git status to using-csrbox.
I ran the python command present in the run.sh of the chromite repo
when i try to run "make generate_verilog" i do get this log  glog.txt
here is the log file when i do "make link_verilator"
vlog.txt

Hi,
While rebuilding chromite core, did you reinstall/update the requirements? That should be done using pip install -r requirements.txt in the chromite's root directory.
Moreover, you should also try to clean and rebuild chromite. Since, building using the command in run.sh without performing a --clean would result in using outdated dependencies. Append --clean to the command you used to rebuild to clean the cloned dependencies. Then rebuild again.
Let me know if it works.
Alenkruth

Hi,
Yes, I did do pip3 install -r requirements.txt before rebuilding the chromite core.
I did clean the cloned dependencies, by using --clean and rebuild the core again.
But I'm still getting an error, when I do make generate_verilog, this is the log file newglog.txt
--Pruthvi

I have tried rebuilding the core and i also tried the make command. But, I am unable to reproduce the error in my machine.
Can you check if the issue persists in any other machine of yours?
On a side note, you will have to use make link_verilator_elf once generate_verilog is done.
--Alenkruth

Hi,
I tried cloning and building the core on a different path and did not encounter any errors while doing these commands
make generate_verilog
make link_verilator_elf
make generate_boot_files
So i tried to run make hello on the benchmarks, and also created a link of code.mem in the bin directory.
But when i try to run the ./chromite_core +rtldump , i get this error

Hello @Alenkruth Al,
To follow up with the same issue #26

I have build the chromite core, my Make Hello and dhrystonemake dhrystone march=rv64im mabi=lp64 ITERATIONS=5000 works
I have installed the latest UATG version(1.5.0) , also have made the appropriate changes in config.ini file
I was able to generate the ASM files
I have cloned the chromite-core-verif repo , compiled and tried running the ASM files during which i encountered an error which i have enclosed below in the compile report and run report
Compile Test Report.pdf
Run Test Report.pdf

Hi,
I tried cloning and building the core on a different path and did not encounter any errors while doing these commands make generate_verilog make link_verilator_elf make generate_boot_files
So i tried to run make hello on the benchmarks, and also created a link of code.mem in the bin directory.
But when i try to run the ./chromite_core +rtldump , i get this error

you should add a +elf=<name_of_elf> along with the +rtldump flag.
Alenkruth

hi,
you can use a +elf=<name_of_elf> in addition to the +rtldump parameter. it
should work.
-- Alenkruth
On Fri, May 20, 2022, 7:58 PM Pruthvi Raj S @.***>
wrote:

Hi,
I tried cloning and building the core on a different path and did not
encounter any errors while doing these commands
make generate_verilog
make link_verilator_elf
make generate_boot_files
So i tried to run make hello on the benchmarks, and also created a link
of code.mem in the bin directory.
But when i try to run the ./chromite_core +rtldump , i get this error
[image: image]
https://user-images.githubusercontent.com/87191910/169549245-e82697a4-9b07-403e-b809-38c9c081d0d4.png
—
Reply to this email directly, view it on GitHub
https://github.com/incoresemi/uatg/issues/26#issuecomment-1132963208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFULDS4GUWNV3PHF2NX4NVTVK6ORHANCNFSM5WMNYNEA
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Container Registry] test failing in nightly runs

Container Registry nightly test runs are failing with:

Error Message
Azure.RequestFailedException : Service request failed.
Status: 405 (Method Not Allowed)
Content:
{"errors":[{"code":"REGISTRY_DISALLOWED_OPERATION","message":"The operation is disallowed on this registry, repository or image. View troubleshooting steps at https://aka.ms/acr/faq/#why-does-my-pull-or-push-request-fail-with-disallowed-operation","detail":{}}]}
Headers:
Server: openresty
Date: Thu, 01 Jul 2021 18:47:13 GMT
Connection: keep-alive
Access-Control-Expose-Headers: REDACTED
Docker-Distribution-Api-Version: REDACTED
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
X-Ms-Correlation-Request-Id: REDACTED
Content-Type: application/json; charset=utf-8
Content-Length: 263
Stack Trace
at Azure.Containers.ContainerRegistry.ContainerRegistryRestClient.UpdateTagAttributes(String name, String reference, TagWriteableProperties value, CancellationToken cancellationToken) in //sdk/containerregistry/Azure.Containers.ContainerRegistry/src/Generated/ContainerRegistryRestClient.cs:line 870
at Azure.Containers.ContainerRegistry.RegistryArtifact.UpdateTagProperties(String tag, ArtifactTagProperties value, CancellationToken cancellationToken) in //sdk/containerregistry/Azure.Containers.ContainerRegistry/src/Artifact/RegistryArtifact.cs:line 411
at Azure.Containers.ContainerRegistry.Tests.Samples.SetPropertiesSample.SetImageProperties() in /Users/runner/work/1/s/sdk/containerregistry/Azure.Containers.ContainerRegistry/tests/Samples/Sample03_SetImageProperties.cs:line 34

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=977895&view=results

This is tracked by #21236


Minor styling tweaks to details panel and landing pages #423

Description
see #423
Testing instructions
Add a set up instructions describing how the reviewer should test the code

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage
[ ] {more steps here}

Agile board tracking
closes #423

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.64%. Comparing base (200caf8) to head (7d538eb).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #424      +/-   ##
===========================================
- Coverage    93.65%   93.64%   -0.01%
===========================================
  Files           60       60
  Lines        15938    15938
  Branches      2065     2062       -3
===========================================
- Hits         14926    14925       -1
- Misses        1007     1008       +1
  Partials         5        5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Google Drive Data link Invalid

Hey, I have watched your video and read the code. I was trying to rerun the code in colab and It seems to appear that the data link that is pokemon.npy is not downloadable, I mean it shows 404 error on the drive page. Can you please update the link for the pokemon dataset.

Hi! Thank you for uploading your video. I'm having the same problem when downloading the pokemon file. Could you please upload the link again? Thanks in advance :)


Inference Hyperparameter Tuning

Is there any interest in tuning the inference hyperparameters such as model, prompt, max_tokens, n, temperature, and top_p? I've been studying how to get the best value of the inference by tuning these hyperparameters under a budget constraint. I'll be happy to contribute here if there is a common interest.
Link to a notebook example: https://github.com/microsoft/FLAML/blob/main/notebook/integrate_openai.ipynb
Related research paper: https://arxiv.org/abs/2303.04673

Interesting!
I've been thinking of adding to a section on the main readme page that links to other tools & examples around the web. I think FLAML could be a good candidate. Would adding a link there (but not a notebook to the repo) make sense to you?

Interesting!
I've been thinking of adding to a section on the main readme page that links to other tools & examples around the web. I think FLAML could be a good candidate. Would it make sense to you if I added a link there (but not a notebook to the repo)?

Sure, that'll be great. We also have an example of tuning ChatGPT (both GPT-3.5 and GPT-4): https://github.com/microsoft/FLAML/blob/main/notebook/integrate_chatgpt.ipynb
Other suggestions are appreciated as well.

@ted-at-openai
The notebook links are updated:
https://github.com/microsoft/FLAML/blob/main/notebook/autogen_openai.ipynb
https://github.com/microsoft/FLAML/blob/main/notebook/autogen_chatgpt.ipynb
And a documentation webpage is added:
https://microsoft.github.io/FLAML/docs/Use-Cases/Auto-Generation

Thanks! Added link to the README in this PR: https://github.com/openai/openai-cookbook/pull/442

Thanks! Added link to the README in this PR: #442

Thank you! Please let me know if there is anything I can help with in future.


Unable to locate element: {"method":"css selector","selector":"._3Tw1q"}

hello, i having a problem running it on Win

C:\Windows\system32>python C:\Users\Kanna\WhatSoup\whatsoup.py
[9512:4340:0227/163848.421:ERROR:upgrade_util_win.cc(73)] IProcessLauncher::LaunchCmdElevated failed; hr = 80004002
[9512:2152:0227/163848.451:ERROR:login_database.cc(654)] Password store database is too new, kCurrentVersionNumber=28, GetCompatibleVersionNumber=29
[9512:2152:0227/163848.451:ERROR:password_store_default.cc(39)] Could not create/open login database.
DevTools listening on ws://<IP_ADDRESS>:55297/devtools/browser/6e5e80ed-295c-4c29-85e4-45131568fd88
Success! WhatsApp finished loading and is ready.
Traceback (most recent call last):
File "C:\Users\Kanna\WhatSoup\whatsoup.py", line 1008, in
main()
File "C:\Users\Kanna\WhatSoup\whatsoup.py", line 29, in main
chats = get_chats(driver)
File "C:\Users\Kanna\WhatSoup\whatsoup.py", line 183, in get_chats
name_of_chat = selected_chat.find_element_by_class_name(
File "C:\Users\Kanna\AppData\Local\Programs\Python\Python39\lib\site-packages\selenium\webdriver\remote\webelement.py", line 398, in find_element_by_class_name
return self.find_element(by=By.CLASS_NAME, value=name)
File "C:\Users\Kanna\AppData\Local\Programs\Python\Python39\lib\site-packages\selenium\webdriver\remote\webelement.py", line 658, in find_element
return self._execute(Command.FIND_CHILD_ELEMENT,
File "C:\Users\Kanna\AppData\Local\Programs\Python\Python39\lib\site-packages\selenium\webdriver\remote\webelement.py", line 633, in _execute
return self._parent.execute(command, params)
File "C:\Users\Kanna\AppData\Local\Programs\Python\Python39\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute
self.error_handler.check_response(response)
File "C:\Users\Kanna\AppData\Local\Programs\Python\Python39\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 242, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"._3Tw1q"}
(Session info: chrome=87.0.4280.66)

It opens chrome and opens WhatsApp web, but it does nothing to the page itself

@kannadivinorum thanks for letting me know! I just pushed a change that should fix this. Can you do a git pull, try again, and let me know if you have any other issues? I've tested it on Win/Linux/Mac so you should be good to go.
To expand on the issue itself...before the most recent update, WhatSoup had a lot of hardcoded HTML attributes in place and in the case of your error it was a DIV element with class "_3Tw1q" which no longer exists, hence the message of 'no such element: Unable to locate element...' WhatsApp cycles and randomizes most of its HTML attributes which means an error like this will happen often if we keep using hardcoded values.
The fix replaced all hardcoded HTML attribute names with Xpath values and other means of identifying the right elements without depending on randomly generated and frequently changing values.

I run it, and it seems to be working, it no longer get that error, that fixed the issue!
However, when i try to export the chat, i get an "Error! 'Erika' produced no search results in WhatsApp." and i don't know if it has something to do with the same issue.
Full event:
(env) PS C:\Windows\system32> python C:\Users\Kanna\WhatSoup\whatsoup.py_util_win.cc(73)] IProcessLauncher::LaunchCmdEle[11424:9604:0227/175057.160:ERROR:upgrade_util_win.cc(73)] IProcessLauncher::LaunchCmdElevated failed; hr = 80004002
[11424:10360:0227/175057.192:ERROR:login_database.cc(654)] Password store database is too new, kCurrentVersionNumber=28, GetCompatibleVersionNumber=29
[11424:10360:0227/175057.193:ERROR:password_store_default.cc(39)] Could not create/open login database.
DevTools listening on ws://<IP_ADDRESS>:56790/devtools/browser/7318812c-3898-4aee-aac1-f576ce33f505
Success! WhatsApp finished loading and is ready.
Success! Your chats have been loaded.
+-----------------------------------------------------------------------------------+
|                         Your 5 Most Recent WhatsApp Chats                         |
+---+--------------------+---------------+------------------------------------------+
| # | Chat Name          | Last Msg Time | Last Msg                                 |
+---+--------------------+---------------+------------------------------------------+
| 1 | Erika              | 5:17 p. m.    | Con tu familia? O andas sola? 😮         |
| 2 | Jonkis de mierda   | 5:01 p. m.    | Samuel: Sticker                          |
| 3 | Gey sin impak      | ayer          | Hotaru: https://youtu.be/B_yz6rw4Fe4     |
| 4 | Ivan               | martes        | Deja les digo                            |
| 5 | +52 1 33 3973 4853 | lunes         | https://1fichier.com/?3mkh068v5za3jd9mnh |
|   |                    |               | k0 esa es la ISO de 64 bits              |
+---+--------------------+---------------+------------------------------------------+
Would you like to see a complete summary of the scraped chats (y/n)? n
Select a chat export option.
Options:
chat number           Select chat for export
-listchats            List your chats
-quit                 Quit the application
What chat would you like to scrape and export? 1
Error! 'Erika' produced no search results in WhatsApp.
Select a chat export option.
Options:
chat number           Select chat for export
-listchats            List your chats
-quit                 Quit the application
What chat would you like to scrape and export?

Thank you for your fast respond by the way!

it seems to have something to do with the language, i changed my phone language to English and it's working like a charm!
Again, thanks for the fast response!

@kannadivinorum Glad you found a workaround. At the moment there are a few key elements in the HTML that I haven't found a great way to identify besides things like titles/labels which as you discovered are in English for me. For example, the code in question that produced your 2nd issue is:
# Look for the unique class that holds 'Search results.'
WebDriverWait(driver, 5).until(expected_conditions.presence_of_element_located(
       (By.XPATH, "//*[@id='pane-side']/div[1]/div/div[contains(@aria-label,'Search results.')]")))

Thanks for letting me know you ran into this new issue. I'll create a new issue to track it and look into a better solution for the few elements that rely on English language settings. I'm closing this issue (hardcoded classes) for now.


Crash in ApptentivePayloadSender deleteCompletedOrFailedRequest:

We are seeing a crash in our app that appears to be originating from the ApptentivePayloadSender deleteCompletedOrFailedRequest: method.  It is not in the stack trace for the crash itself, but in going through 20 instances of this crash (out of 275+), the only non-system code that is executing is this method.  See attached images for the stack traces.  Unfortunately Firebase doesn't give me a good way to paste the whole thing as text in any kind of easily readable format :-/
Not sure if this is helpful or not, but we have not seen this crash in versions of our app running version 3.x versions of the SDK, only the version that is running 4.0.2.

I'm sorry that you're running into all of the teething problems with our new architecture (we've rearchitected the networking code, which is why this is present in 4.0.x but not 3.x). And thanks again for being forthcoming with your crash reports.
I've been looking at the code and don't yet see a smoking gun, but I'll continue to investigate and keep you updated with what I find.

As far as we can tell, the issue is due to a block sometimes being released while it's being executed, because the object that owns the block (in this case, a managed object context) is getting released.
Any time the app exits, it would set up the preconditions for this to occur. I've push a fix to a branch (https://github.com/apptentive/apptentive-ios/tree/v4.0.4-pre) that you can try out.
The fix makes the block capture the managed object context so that it can finish running before the managed object context (and hence the block) gets released.
I've modified the code to have the block (indirectly) retain a reference to itself.

No problem, and we really appreciate how responsive you have been when we report an issue!  I just tried the updated SDK and did not have any issues.  I was not able to reproduce the crash before the fix, so I don't know if it has resolved the issue or not, but it seems stable in the small amount of testing I have done.

I wanted to follow up and see when this fix might be released.  We are continuing to see a large number of these crashes.  Thanks!

Also, I would like to clarify something you mentioned above...

Any time the app exits, it would set up the preconditions for this to occur.

By that do you mean the app going into the background?  We have received a number of reports of the app shutting down when backgrounded and I wanted to see if this was the cause.

Yes, that is what I mean.

We just released version 4.0.4 that should address this crash.

That's great news, thank you!

Unfortunately 4.0.4 didn't eliminate the issue.  We are still seeing this crash, although it has a slightly different stack trace now:

I think this could be related to https://github.com/apptentive/apptentive-ios/issues/198. There is a significant bug in the way that we handle app exit in this part of the code.
It would be manifested as the managed object context being released before it should and the background task completion handler not getting called, causing the system to kill the app.
We will be releasing a patch in the near future and will update you when we do.

Version 4.0.5 (just released) fixes a problem with the background task that is used to save the Core Data stack on app exit. It is likely that a non-clean exit of the Core Data stack is to blame for this crash, so please update and let us know if it fixes the issue.

The latest version of our app was released on Friday and we did not see any of these crashes come in over the weekend.  This was our most frequently occurring crash so I would have expected to see it at least once if it were still an issue.  I think this can be closed, and I will write back in if it happens again.

@frankus we have recently migrated from 3.x to 4.0.7, and unfortunately we are still seeing this issue, primarily on iOS 11 (11.0.2 and 11.0.3)
Here is the Stacktrace
Crashed: NSManagedObjectContext 0x1c01c9600 0  libobjc.A.dylib                0x1841f8430 objc_msgSend + 16 1  Apptentive                     0x10314a744 __58-[ApptentivePayloadSender deleteCompletedOrFailedRequest:]_block_invoke + 32 2  CoreData                       0x18750eea4 developerSubmittedBlockToNSManagedObjectContextPerform + 156 3  libdispatch.dylib              0x184655048 _dispatch_client_callout + 16 4  libdispatch.dylib              0x184663580 _dispatch_sync_invoke_and_complete_recurse + 64 5  libdispatch.dylib              0x18466307c _dispatch_sync_wait + 516 6  CoreData                       0x18750eda8 -[NSManagedObjectContext performBlockAndWait:] + 304 7  Apptentive                     0x10314a6f4 -[ApptentivePayloadSender deleteCompletedOrFailedRequest:] + 144 8  Apptentive                     0x103149d8c -[ApptentivePayloadSender requestOperationDidFinish:] + 240 9  Apptentive                     0x10314e5a4 -[ApptentiveRequestOperationCallback requestOperationDidFinish:] + 108 10 Apptentive                     0x10314d3e8 -[ApptentiveRequestOperation processResponse:withObject:] + 496 11 Apptentive                     0x10314cee8 __39-[ApptentiveRequestOperation startTask]_block_invoke + 416 12 CFNetwork                      0x18525ad50 __75-[__NSURLSessionLocal taskForClass:request:uploadFile:bodyData:completion:]_block_invoke + 32 13 CFNetwork                      0x1852720ec __49-[__NSCFLocalSessionTask _task_onqueue_didFinish]_block_invoke + 152 14 Foundation                     0x18569a310 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 16 15 Foundation                     0x1855da9e4 -[NSBlockOperation main] + 72 16 Foundation                     0x1855ca620 -[__NSOperationInternal _start:] + 848 17 libdispatch.dylib              0x184655048 _dispatch_client_callout + 16 18 libdispatch.dylib              0x18465c6c8 _dispatch_block_invoke_direct$VARIANT$mp + 288 19 libdispatch.dylib              0x184655048 _dispatch_client_callout + 16 20 libdispatch.dylib              0x18465c6c8 _dispatch_block_invoke_direct$VARIANT$mp + 288 21 libdispatch.dylib              0x18465c574 dispatch_block_perform$VARIANT$mp + 104 22 Foundation                     0x18569bfe8 __NSOQSchedule_f + 376 23 libdispatch.dylib              0x184655048 _dispatch_client_callout + 16 24 libdispatch.dylib              0x18465d3d4 _dispatch_continuation_pop$VARIANT$mp + 428 25 libdispatch.dylib              0x18465bcd4 _dispatch_async_redirect_invoke$VARIANT$mp + 604 26 libdispatch.dylib              0x1846621c8 _dispatch_root_queue_drain + 596 27 libdispatch.dylib              0x184661f10 _dispatch_worker_thread3 + 120 28 libsystem_pthread.dylib        0x1848fb130 _pthread_wqthread + 1268 29 libsystem_pthread.dylib        0x1848fac30 start_wqthread + 4

@loevborg Thanks for the update. I will reopen the issue and we'll continue to try and track down a repro and fix.

@frankus exact same issue in our app. Let me know if you need more info.

We finally tracked this down and have a fix included in the 4.1.1 release.

@frankus The earlier version I had was 4.0.7 to get this issue fixed I updated my pod and got an updated version 4.1.0
How will I get 4.1.1?

I wonder if this might be a problem with CocoaPods. Their website is showing 4.1.1 as the current version: https://cocoapods.org/pods/apptentive-ios.


Linkml range does not always propagate to shacl

Many property shapes in gen-shacl output do not have any of these attributes:sh:datatype, sh:nodeKind, or sh:class. This makes it impossible to select the correct property-editor during the automatic form generation process, instead having to rely on a default text-field-editor.
Some digging shows that this is a known issue in LinkML: https://github.com/linkml/linkml/issues/1299
And there's an open PR: https://github.com/linkml/linkml/pull/1300

For example, we have the slot:
email:
    slot_uri: dlco:email
    description: Email address associated with an entity.
    exact_mappings:
      - schema:email
      - obo:IAO_0000429
    range: EmailAddress

where EmailAddress is a type:
types:
  EmailAddress:
    uri: dlco:EmailAddress
    base: str
    description: RFC 5322 compliant email address
    pattern: '(?:[a-z0-9!#$%&''*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&''*+/=?^_`{|}~-]+)*|"(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])*")@(?:(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?|\[(?:(?:(2(5[0-5]|[0-4][0-9])|1[0-9][0-9]|[1-9]?[0-9]))\.){3}(?:(2(5[0-5]|[0-4][0-9])|1[0-9][0-9]|[1-9]?[0-9])|[a-z0-9-]*[a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])+)\])'
    notes:
      - The validation regex is taken from https://stackoverflow.com/a/201378
      - The regex is single-quoted for YAML encoding, hence all inner "'" have been doubled

and the resulting shacl property shape is a mere:
[ sh:description "Email address associated with an entity." ;
      sh:maxCount 1 ;
      sh:order 1 ;
      sh:path dlco:email ],

Note also that apart from the missing datatype or nodekind attributes, the pattern is also missing, as are the exact_mappings from email slot.

This is fixed by https://github.com/linkml/linkml/pull/2102


ap_requires was removed in apache 2.4

I install openidc on apache2.4 and see this error:
Syntax error on line 1 of /etc/apache2/mods-enabled/auth_openidc.load: Cannot load /usr/lib/apache2/modules/mod_auth_openidc.so into server: /usr/lib/apache2/modules/mod_auth_openidc.so: undefined symbol: ap_requires
Action 'configtest' failed.
As noted at http://httpd.apache.org/docs/current/developer/new_api_2_4.html, ap_requires was removed in apache2.4.
Can you add support for apache2.4?
Thanks.

Hi, I am trying to migrate a different module (that uses ap_requires) from apache 2.2 to apache 2.4. Can you point me to the changes that you did so that I can understand what should be changed ? Thanks.

+1, psankar did u reselved this problem?

I could not. Thankfully that module was scheduled for rewrite and it saved me. But I have heard that with some compiler and linker options magic, it could be changed, but I have never tried that.

FWIW: I don't think it can be done without source code changes. But since it is not specific to mod_auth_openidc I suggest you try and find answers elsewhere, sorry.


java 11 and zgc

Whether cratedb supports Java 11 and ZGC to improve the efficiency of GC or not, at present, the amount of cluster data is large and the GC time is long. I wonder if it is feasible to improve the performance through zgc.

We are keeping an eye on GC developments, but so far haven't done any testing with ZGC and we're not supporting it officially.
Note that ZGC is still experimental in Java 11 and it usually takes a while to iron out all bugs. For example for G1GC there have been bugs up to Java9 that could lead to index corruption with Lucene.
In case you decide to evaluate it on a test environment or something - we'd be curious to hear back on your experiences.

Closing this for now as we don't have any plans to look into zgc as long as it is marked as experimental.
Note though that 3.2 supports java 11 and that you might already see improvements using G1GC instead of ConcMarkSweepGC


Feature Request : Light/Dark Mode toggle button

A button that switches between light and dark mode on the website. Here is a link preview to a sample website. Below are some screenshots of something like what I had in mind, the toggle button is on the top right.

Will be possible to implement using const {savedTheme, setStorageTheme} useTheme()hook from #307 and see whatever new design will be decided in #285.

An MVP could be:
Add a button that links people to download a Chrome extension like this one.


Ammo assignments added into "Assign"-tab

As an easier way to assign ammo to pawns, I added two "Ammo"-columns to the "Assign"-tab, similar to how it already has an option for medicine.
Two, just in case someone has a "primary" and "secondary" ammo they want to carry. It should be easy to add more columns, if desired - it could be handled in a dynamic way, though that would require a rework.
If ammo is disabled, the columns will be hidden and the assigned ammo should be reset to 0 (upon opening the "Assign"-tab).

Notes:

Pawns will not drop the ammo they were already carrying when assigning different ammo or completely disabling ammo, but the same is true when changing the assigned medicine (which is part of the base game) and with ammo assigned through the drug policies. While I consider this to be a (minor) bug, it is a problem of base game, not of this mod.
Also, I decided not to remove ammo from the drug policy settings, as medicine can be assigned through both the "Assign"-tab and the drug policy in base game as well.

I ran into strange issues with some completely unrelated errors:
System.FieldAccessException: Field Verse.VerbProperties:forcedMissRadius' is inaccessible from method yayoCombat.yyShotReport/yayoTryCastShot:Prefix (bool&,Verse.Verb_LaunchProjectile,Verse.LocalTargetInfo,bool)'
So I went and recompiled the project and reloaded the RimWorld files through NuGet - now there are errors showing up in the code, mainly "forcedMissRadius" and "preventFriendlyFire" being inaccesible due to protection level.
Will try to figure out what's going on.
Am doing something wrong?
I thought I downloaded the latest version of the project.
The only change I figure I did was that I compiled it as Release instead of Debug, going by what ILSpy tells me about the original DLL.

Problem should be fixed now. At least it's working fine again for me.
I set AllowUnsafeBlocks to true for Release, this fixed the accessibility issues, and GeneratePathProperty to true for Krafs.Rimworld.Ref, this fixed the compile-time errors. The flag was removed when I updated it...

I use a publicized version of rims assembly, making all the fields public, means less need for reflection, etc
im not a very proferssional developer at all im afraid, i never remember to set it to release, all mine are debug mode still haha - i only started learning to code a few years back to make mods

Requiring less reflection is really neat, read up on it a bit at work, and while I was sure they are slow, they are apparently even slower than I feared. Might have to look up where I used it and see if there isn't better alternatives.
I often forget to set it to Release as well. it just surprised me that suddenly there were very unexpected errors.
Still not entirely sure whether what I wrote actually was the fix for the problem or not, now that I think about it. I might want to look into it again, just to be sure why it works this way and why it didn't work before.
Anyway, I'm just glad it was easy to implement and it seems to work without issues now.

it needs to be set to allowunsafe code to work, im not entirely sure why, Wiri helped me set it all up awhile back, hes a Much smarter cookie than me!, real friendly and helpful too - though i believe Krafs has a publicizer package now too on nuget, i havent tried it yet, but i Think it does the same thing, was asking him about doing something like that awhile back

Just wanted to add a preview screenshot to how this feature looks in the Assign tab:

If desired it could also be extended to allow customizing the number of ammo columns.

Closing this pull request, will turn it into an addon mod.


Catastrophic issue found!

Yup, total click bait @sindrebroch  😆
Where's the 'Buy me a coffee' button???

You got me 😆
Thanks a lot, added a button in the README 😄


Check if app has liquid-fire installed

I'm writing an addon and I'd like to be able to check from a component if the host app has liquid-fire installed. What would be the best way to do this?

You could check to see if the liquid-fire-provided component that you want is available in the container, in your own initializer or service:
!!container.lookupFactory('component:liquid-if')

Trying an initializer:
// addon/initializers/liquid-fire-detection.js
export function initialize( container ) {
  var lfDetection = container.lookup('service:liquid-fire-detection');
  lfDetection.set('hasLiquidIf', !!container.lookupFactory('component:liquid-if'));
}

export default {
  name: 'liquid-fire-detection',
  initialize: initialize
};

Bizarrely, the !!container.lookupFactory('component:liquid-if') call causes all liquid-ifs in my app to not work - they always render their contents, and don't respond to data updates. I don't see any errors or other messages in the console, just a deprecation warning about lookupFactory.
Any ideas? Thanks!

@samselikoff you likely want to use an instance initializer, not an initializer

ok, I moved the code to an instance initializer, used instance.container.lookup('component:liquid-if') and I'm getting the same behavior - {{#liquid-if}} stops functioning. I'll keep digging.

Ok I confirm behavior exists in a brand new app, in both an initializer and an instance initializer.
Steps to reproduce:

ember new liquid-fire-test

npm install --save-dev ef4/liquid-fire#stable

In application.hbs add
{{input type='checkbox' checked=isShowing}}

{{#liquid-if isShowing}}

Foo

{{/liquid-if}}

and verify the checkbox toggles the liquid-if.

ember g initializer liquid-fire-checker

In the initialize function, add
export function initialize(container) {
  console.log(!!container.lookupFactory('component:liquid-if'));
}

This could also be container.lookup, or you could also use an instance-initializer.

Run the app again, and you'll see the {{#liquid-if}} block is no longer functioning. The panel is open and doesn't respond to the checkbox.

I think it would be easier to detect and add a boolean flag to your addons config.  You can use ember-cli-version-checker to detect if liquid-fire is present (and check its version if you care) in the host app, then set a config value in your addon's config hook (or config/environment.js).
See a super long winded explanation of tailoring an addon's output tree based on available packages: https://github.com/ember-cli/ember-cli/issues/4339#issuecomment-115384427

@rwjblue ok, this is actually for an addon. I'm not sure if it's possible for my addon to rely on another addon yet?

@samselikoff - Yes, many cases of nested addons work today (but some do not).  The technique that I was suggesting was unrelated to nested addons though, ember-cli-version-checker is not an addon (it is a utility function/library).

Got it - works great. thanks!


LLVM 14 support

tracking issue for llvm 14

Basic support got added but not all features work yet, issues:

[] #2222

Issues detected by tests were fixed with the merging #2316, if there aren't any other known issues, this issue can be closed.


kminion: 2.2.7 → 2.2.8, init module

Description of changes

https://github.com/redpanda-data/kminion/releases/tag/v2.2.8

Also adds a module + test case
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[X] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I tried to fix the merge conflict, let's see if CI likes it


test file detection fragile

Testing #17039
The provided test file patterns don't work very well.
For example:
*test.py - will detect utest.py but not unittest.py
test.py - will detect utest.py but not unittest.py

This is expected in python. when you name a file unittest.py it overrides the underlying library unittest. The files in your current working directory take precedence over the standard library.


Firefox for Android related issues

Select your issue type: (check at least one)

[x] Bug
[ ] Question
[ ] Suggestion
[ ] Other (please describe):

Describe your issue:
These do no work on Firefox for Android 55

[ ] Browser Action Popup
[ ] Additional Permissions

Select your issue type: (check at least one)

[x] Bug
[ ] Question
[ ] Suggestion
[ ] Other (please describe):

Describe your issue:
tested on: acer liquid zest 4G, firefox nightly v57.0a1

The button "Download" on the watch page is very tiny and hard to click on mobile.
it takes the browser ~2 seconds to remove and add all the things you checked on in the options.
the downloads don't work on mobile on both F4 and rapidvideo. (it is stuck on ready to download.

Keeping this on hold as debugging on Firefox Android is a huge pain.

Looks like all the issues are fixed in FF Mobile 58. @WEBhicham can you test all the features of 9ac in mobile and let me know how it went?


Warning: Deprecated attribute: authorized_gae_applications

The module explicitly specify the google_sql_database_instance.authorized_gae_applications that outputs a terraform warning when used on every plan and apply:
│ Warning: Deprecated Attribute
│
│   with module.stack.module.mssql.module.mssql.google_sql_database_instance.default,
│   on .terraform/modules/stack.mssql.mssql/modules/mssql/main.tf line 54, in resource "google_sql_database_instance" "default":
│   54:     authorized_gae_applications = var.authorized_gae_applications
│
│ This property is only applicable to First Generation instances, and First Generation instances are now deprecated.
╵

e.g. in https://github.com/terraform-google-modules/terraform-google-sql-db/blob/master/modules/mssql/main.tf#L54
Versions used:
Terraform v0.15.3
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v3.40.0
+ provider registry.terraform.io/hashicorp/azurerm v2.59.0
+ provider registry.terraform.io/hashicorp/external v2.1.0
+ provider registry.terraform.io/hashicorp/google v3.67.0
+ provider registry.terraform.io/hashicorp/google-beta v3.67.0
+ provider registry.terraform.io/hashicorp/kubernetes v1.13.3
+ provider registry.terraform.io/hashicorp/null v2.1.2
+ provider registry.terraform.io/hashicorp/random v2.3.1

Still happening.

+1

Happy to review a PR removing this

As a workaround users should also be able to suppress the warning by setting authorized_gae_applications = null

@bharathkkb just created the PR https://github.com/terraform-google-modules/terraform-google-sql-db/pull/240, please review it


Bug smelt with CHARCOAL 1.13.2

Hello,
Since the passage in 1.13, cooking wood charcoal no longer gives the gains, I tried all possible ID but no change. I would like to know if this is a bug on your side and if it is possible to be fixed.
Cordially.
Smelt:
CHARCOAL:
income: 0.20
experience: 0.20

I don't know why not works for you. I tested it and it's working correctly for me.
Try update to the DEV. version. this


Pr/jrajahalme/docker use buildkit also for non dev builds

Use DOCKER_BUILDKIT=1 also for non-dev builds. This causes CI to use cached builds when running ginkgo repeatedly on existing VMs, and reduces the image build time by several minutes in that case.
Remains to be seen if quay and docker support buildkit builds.

test-me-please

Coverage decreased (-0.02%) to 37.825% when pulling 5b899d07528507692440355d93618a59bf17954c on pr/jrajahalme/docker-use-buildkit-also-for-non-dev-builds into 8e86001bdb3a247aceff9508b60e12f9f4cc59aa on master.

test-me-please

Failed on K8s-1.11-Kernel-netnext:
22:15:37  failed to solve with frontend dockerfile.v0: failed to solve with frontend
gateway.v0: rpc error: code = Unknown desc = failed to build LLB: executor failed
running [/bin/sh -c groupadd -f cilium     && echo ". /etc/profile.d/bash_completion.sh"
>> /etc/bash.bashrc]: runc did not terminate sucessfully

I did see this once locally as well, maybe DOCKER_BUILDKIT is not good for prime time yet?

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

CI had trouble with this, so removed the last commits that made CI use DOCKER_BUILDKIT.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

I tried this out.
Made sure that images were cached, docker layers prepared:
$ git checkout upstream/pr/jrajahalme/docker-use-buildkit-also-for-non-dev-builds
$ make dev-docker-image
...
$ make clean
...

First, try without buildkit:
$ time make dev-docker-image
...
real    2m26.373s

Before trying with buildkit, it would break unless I pulled the experimental dockerfile:
$ docker pull docker.io/docker/dockerfile:experimental
...

Now, with buildkit:
$ DOCKER_BUILDKIT=1 time make dev-docker-image
3.29user 1.18system 1:51.20elapsed 4%CPU (0avgtext+0avgdata 72688maxresident)k
272inputs+2240outputs (0major+134079minor)pagefaults 0swaps

I don't know why time is giving entirely different output this time around, but
it at least went down by about 30s.
Repeat builds without changes are even better:
$ DOCKER_BUILDKIT=1 time make dev-docker-image
2.32user 0.79system 0:02.47elapsed 126%CPU (0avgtext+0avgdata 68276maxresident)k
552inputs+2240outputs (10major+131485minor)pagefaults 0swaps

I also tried making a change to the daemon to time that:
$ git show
commit d299ebd4ae2d7ade1c7e21a99845c607f0836b9d (HEAD -> pr/jrajahalme/docker-use-buildkit-also-for-non-dev-builds)
Author: Joe Stringer<EMAIL_ADDRESS>Date:   Tue May 19 11:48:15 2020 -0700

    noop

diff --git a/daemon/cmd/daemon.go b/daemon/cmd/daemon.go
index 155d691579bf..dda2351039d1 100644
--- a/daemon/cmd/daemon.go
+++ b/daemon/cmd/daemon.go
@@ -186,6 +186,7 @@ func (d *Daemon) init() error {

        if err := os.Chdir(option.Config.StateDir); err != nil {
                log.WithError(err).WithField(logfields.Path, option.Config.StateDir).Fatal("Could not change to runtime directory")
+       } else {
        }

        // Remove any old sockops and re-enable with _new_ programs if flag is set
$ DOCKER_BUILDKIT=1 time make dev-docker-image
2.33user 0.97system 0:29.92elapsed 11%CPU (0avgtext+0avgdata 69688maxresident)k
272inputs+2376outputs (0major+133470minor)pagefaults 0swaps

So, down to about 30s container build time for a trivial change to one component.
:tada:

test-me-please

the few test failures are unrelated.

@tklauser This is ready to merge.