Implanter Fabricator

About the PR
Adds a new Lathe that allows for the production of various implants. This automaton can be Emagged to gain access to some not-so-strong implants.
Removed the ability to buy fun implants via cargo.
added 2 new implants:

Smoke Cloud Implant (the only way to get it is by emagging a new lathe)
Protokinetic implant - allow to rarely shoot ptk projectiles from hand

Why / Balance
Implants are a rather interesting mechanic that is very underutilized
I think we also need useful implants for the crews. Adding this to the medical machine would increase the variety of gameplay of the medical department.
Technical details
no c#
Media

https://github.com/space-wizards/space-station-14/assets/96445749/e8bb0d08-4097-4a25-88ff-bacee42b45e3

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

add: Added new ImpLathe. Lathe to fabricating implanters.
add: New Protokinetic and smoke cloud implanters added.

I wanted to make biochem cooler, but you nuke it

I think inventory is interesting and nuking it for powergaming implants doesn't seem good and just creeps them even harder. The only reason nukies / sec have implants is important to bypass inventory but there's no reason a random clown needs to be able to teleport at will.

there's no reason a random clown needs to be able to teleport at will.

thats emag only

there's no reason a random clown needs to be able to teleport at will.

thats emag only

It's still forcing implant removal as a mechanic and bypassing the entire reason it even exists for nukies.

why emag card need to gain more value again?

I don't think PKA implant being random is a good idea, it should probably just have a long cooldown (15 seconds maybe)

o7


Task/dry the deploy workflow

DRYed the CD workflow

Waiting for https://github.com/nationalarchives/ds-caselaw-data-enrichment-service/pull/166 to be merged in first so that the postgres upgrade issue that is causing terraform apply to fail on main is fixed.


Investigate having the generator impl traits manually instead of emitting #[derive]

time-passes for an --all-features build shows most of the non-LLVM time breaks down like this:
  time: 82.388; rss: 951MB	expansion
  time: 57.681; rss: 2107MB	item-bodies checking
  time: 57.331; rss: 3152MB	borrow checking

Manual impls at codegen time would reduce the time spent in expansion for all users of the crate, at the cost of duplicating the functionality of the derives into the code generator.
Investigate if the complexity is worth it, especially since serde's derives are the most complicated to reimplement.

Replacing #[derive(Deserialize, Serialize)] with manual impls gives:
debug
master 5m08s 5m08s 5m22s
issue-4 3m08s 3m03s 3m02s

release
master 3m30s 3m30s 3m24s
issue-4 2m53s 3m01s 2m52s

The difference between debug-master and release-master is because proc macros like serde_derive are themselves compiled in debug mode for debug builds.
Replacing #[derive(Debug, Default)] with manual impls produces no discernible difference, probably because they're emitted by the compiler itself.
The only remaining dependency on serde_derive is for the impls for ::IntOrString. Replacing these with manual impls allows proc_macro2, quote, serde_derive and syn to be dropped entirely, bringing compile time down to 3m for debug and 2m30s for release.


Support file descriptors

Though the documentation states that FDs are in the type system the following code fails with a hang:
import asyncio
import dbus_next
from dbus_next.aio import MessageBus

async def main():
    bus = await MessageBus(bus_type=dbus_next.constants.BusType.SYSTEM).connect()
    introspection = await bus.introspect('org.freedesktop.login1', '/org/freedesktop/login1')
    obj = bus.get_proxy_object('org.freedesktop.login1', '/org/freedesktop/login1', introspection)
    manager = obj.get_interface('org.freedesktop.login1.Manager')
    infd = await manager.call_inhibit("sleep", "My Program", "Wait while I save...", "delay")
    print("My inhibit fd is:", infd)

asyncio.run(main())

To anyone reading this! Don't suffer like I did. This library supports FDs if you change the code to this:
bus = await MessageBus(bus_type=dbus_next.constants.BusType.SYSTEM, negotiate_unix_fd=True).connect()

@mike-matera Firstly, thank you for posting this. I was wondering why my code was hanging and had traced it to the client not supporting file descriptors which, in turn, led me here.
I'm looking to implement exactly the same think (i.e. a sleep inhibitor) but, for some reason, python isn't closing the file descriptor that's returned by the call to Inhibit. I can call os.close on it without error but the inhibitor isn't removed.
Do you have some fuller code that shows how you did it? Appreciate that this is almost 6 months after you posted this but thought I'd ask!


prevent name change save of one char

closes #490
Note that the user is able to delete all characters from the firstName and lastName fields but the store is only altered if the field has one or more characters.  Meaning that a user can remove all characters, see an error message, but the name that is saved is a single character if they navigate away from the page.
I played with a few options like forcing a single character to remain in the input fields but this seemed like a bad UX if the user for some reason wants to delete all characters and start over, it prevents them from doing so and is a little jerky.

Merged #493 into dev.


System.NullReferenceException when try removing url attribute

Bug Report
Prerequisites

[x] Can you reproduce the problem in a MWE?
[x] Are you running the latest version of AngleSharp?
[x] Did you check the FAQs to see if that helps you?
[x] Are you reporting to the correct repository? (there are multiple AngleSharp libraries, e.g., AngleSharp.Css for CSS support)
[x] Did you perform a search in the issues?

For more information, see the CONTRIBUTING guide.
Description
removing url attribute (src in this case) with local path would cause an NRE.
using AngleSharp.Html.Parser;

namespace AngleSharpNre
{
    class Program
    {
        static void Main(string[] args)
        {
            const string html = "<video src=\"D:\\videos\\learning\\tail.wmv\"></video>";
            var parser = new HtmlParser();
            var dom = parser.ParseDocument(html);
            dom.GetElementsByTagName("video")[0].RemoveAttribute("src");  // NRE
        }
    }
}

Steps to Reproduce

Create a Console Application
Paste the code above
Run

Expected behavior: The attribute been removed successfully
Actual behavior: An NRE
Environment details: Windows 10, .Net 5.0 rc2, AngleSharp 1.0.0-alpha-827

Thanks for reporting this - will be fixed asap.

@FlorianRappl
Thanks for the quick fix, removing src attribute in video tag is working now!
Unfortunately after a little digging in my log file, I find out that embed tag has exactly the same issue😞 and can be reproduced with version alpha-842.

Fixed and available in devel / the preview.


Mentioning other ways of generating tables

Hi folks,
I noticed an important omission in the documentation that I thought I'd remove. Namely, tables can also be created using Markdown and HTML. I'm not sure, but I'd guess that tables generated using CSV probably do not have support for KaTeX. But tables generated using Markdown do (I just tested that too), so this information may benefit some users.
Thanks for your time.

Thanks!


[ios] fix race conditions (close #652)

I was experiencing a bunch of crashes in production with 1.2.3
There was already a solution proposed here: https://github.com/react-native-kit/react-native-track-player/issues/652
I was able to reproduce the issue locally and used Thread Ripper to test the solution proposed in the above issue.

I have verified that this PR solved the crashes I was experiencing in production.

Released in 1.2.4


Reset uploader component

Describe the bug
Currently MESOP Uploader component cannot be reloaded / refreshed / reset
https://google.github.io/mesop/components/uploader/
To Reproduce
Upload a file with the uploader component and you fill get the "file name" beside the upload button.
But if one is implementing a "clear" button (e.g. in a chat) it is not possible to remove the "file name" text after the uploader button.
Expected behavior
Add a clear / refresh feature for the component
Screenshots
Before:

After pressing clear (this removes UploadedFile from state) but the uploader component (file name) cannot be "reset" and still shows the demo-image1.png

Thanks for bringing this up. I've noticed this too. I'll take a look this week. Seems like it should be fixable, but if not I think this could work: https://google.github.io/mesop/components/?h=reset#resetting-a-component as a temporary workaround.

Here are few options (not particular order) API-wise:

Add a clear parameter. Then when cleared, send an on_clear event back to the server so that the clear parameter can be disabled. Needing to include on_clear hook to reset seems a bit tedious though

Add a filename parameter. If set to empty string, then the value will be cleared. If set, then the given filename will be displayed.

Just use the reset component use the key update workaround above.

I think I'm going to go with option 2. This way, a user can upload a file and no filename will show at all (if that's what they want). This works for now since the upload is immediate. No need to select a file and press an upload button. The main drawback with number 2 is if a user sets a filename even though nothing has been uploaded. But I think that is OK.

Sorry for the delay on this. Thought I could get to it before I went OOO for a week. Unfortunately did not get to it.
My solution for this ended up being to remove the labels altogether. I realized they were a bit redundant and could be added manually in Mesop anyway which would give more flexibility.


Exhaustive switch code action for selection

Imagine selecting a range of something:
// Select the full expression below
event->JsxEvent.Keyboard.ctrlKey

...and then get a code action Exhaustive switch on selection, that would produce this:
switch event->JsxEvent.Keyboard.ctrlKey {
  | true => failwith("todo")
  | false => failwith("todo")
}

Could have a sibling action for try/catching a block of code.


Image sprite loading

Allow loading of images from the project folder.
Requirements:

[ ] Loads from local folder.

Question: do we need to load sprites separately with a sprite sheet? Or is that an old school optimization?

https://wiki.libsdl.org/SDL_LoadBMP

Should this include some clipping and ensuring image is place correctly?


[AutoPR containerinstance/resource-manager] Adding April Swagger For GA

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2778

(message created by the CI based on PR content)

Codecov Report

Merging #2309 into restapi_auto_containerinstance/resource-manager will increase coverage by 0.05%.
The diff coverage is 76.82%.

@@                                 Coverage Diff                                 @@
##           restapi_auto_containerinstance/resource-manager    #2309      +/-   ##
===================================================================================
+ Coverage                                            52.77%   52.82%   +0.05%
===================================================================================
  Files                                                 5630     5659      +29
  Lines                                               133962   134250     +288
===================================================================================
+ Hits                                                 70697    70923     +226
- Misses                                               63265    63327      +62

Impacted Files
Coverage Δ

...nce/models/container_exec_request_terminal_size.py
100% <100%> (ø)
:arrow_up:

...inerinstance/models/container_exec_response_py3.py
100% <100%> (ø)

...zure/mgmt/containerinstance/models/volume_mount.py
100% <100%> (ø)
:arrow_up:

...ce/azure/mgmt/containerinstance/models/resource.py
100% <100%> (ø)
:arrow_up:

...ls/container_group_properties_instance_view_py3.py
100% <100%> (ø)

.../containerinstance/models/resource_requests_py3.py
100% <100%> (ø)

...e/mgmt/containerinstance/models/container_state.py
100% <100%> (ø)
:arrow_up:

...tance/models/container_properties_instance_view.py
100% <100%> (ø)
:arrow_up:

...tance/azure/mgmt/containerinstance/models/event.py
100% <100%> (ø)
:arrow_up:

...models/container_exec_request_terminal_size_py3.py
100% <100%> (ø)

... and 80 more

Continue to review full report at Codecov.

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

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2320


Fix up error handling

Quoted from the discord:

our error handling solutions are still premature. there are certain errors which i would want to catch and send to the void, certain ones i would want to propagate up the error call stack, etc.
ideally, i only want fatal errors to result from human error, such as passing a weird argument, etc. anything machine related should not be fatal, and should be delt with by the program in an organized fashion.
for example, if we implement websockets, we would want to keep our current API based solution, and have an error handling to catch API request issues with the websocket, and to fallback to the API instead.
i want to add more redundancy to certain aspects of ketchupbot. i've said for a while now that i believe for ketchupbot to be mission critical to the Galaxypedia, we NEED it, basically. there should never be a situation where a non-human error results in a crash.

Quoted from the roadmap:

my entire kinda reason for this rewrite was that i wanted to make ketchupbot a lot more robust, and i mean a LOT more. ive gone as far as to enable strict linting options, enforce a naming convention, etc. to ensure that things can NEVER go wrong, and if something does go wrong, it is reported but will not bring everything down with it. im going to develop this rewrite assuming everything can go wrong, and expecting everything to go wrong. so yeah, do note that my first priority in this rewrite is making sure things are robust, everything else is secondary.

going into why i want it to be this robust--even though docker's auto restart is pretty sufficient--i believe that ketchupbot is very mission critical. a while back i was in denial. i didnt want to think that us staff had to rely on a bot to keep our site up to date, it felt embarassing. but as ive grown, ive realized that our shame doesnt matter. our job is to keep this wiki afloat, and up to date. if a bot is our crutch, so be it, but we might as well make sure that our crutch doesn't break on us. ketchupbot is critical to us and the community. we cannot afford for it to break. not now, not ever.

ok tbh i dont see where we can go from here. i've already set up sentry, so i think that's the best way to go moving forwards


Production recommendation

Hey!
Really love what you're doing here. I'm contemplating using this as a basis for our MD components in an app that is launching in 2-3 months. This far, things have been a breeze and I really enjoy the small details, such as colourized error handling of TextFields. There is still a lot to do, and I don't mind helping out when stuff is a bit more ironed out, but what is looks very solid.
So the big question remains: Would you consider this safe to use in prod in about 2-3 months? What is your rough internal timeframe (I won't hold you to it) for a 1.0?

I don't have a specific timeframe for 1.0, I just work on things as I can tie them into other things I am working on.


Polish translation

Simple Polish translation
BTW. 2 GB repo (--depth=1) ?!

BTW. 2 GB repo (--depth=1) ?!

I'm not efficient when it comes to Unity.. lol.. Sorry about that. I think it's because I have the AssetDB installed.

I'm not efficient when it comes to Unity

LOL :-D
Ok, GryfuPl and me have finished translation. There are only small differences (between this PR and issue one).
Now is your move.


Use nodeCache to take place of treeCache

cherry pick from #7466

Codecov Report

Merging #7953 (49d6780) into 3.0 (ee4d909) will decrease coverage by 0.31%.
The diff coverage is 82.35%.

@@             Coverage Diff              @@
##                3.0    #7953      +/-   ##
============================================
- Coverage     59.83%   59.51%   -0.32%
+ Complexity      327      326       -1
============================================
  Files          1086     1086
  Lines         44369    44294      -75
  Branches       6631     6590      -41
============================================
- Hits          26546    26360     -186
- Misses        14904    15019     +115
+ Partials       2919     2915       -4

Impacted Files
Coverage Δ

.../configcenter/support/zookeeper/CacheListener.java
72.72% <75.00%> (+3.16%)
:arrow_up:

...pport/zookeeper/ZookeeperDynamicConfiguration.java
80.55% <75.00%> (+4.23%)
:arrow_up:

...ting/zookeeper/curator/CuratorZookeeperClient.java
67.78% <87.09%> (+1.86%)
:arrow_up:

...a/org/apache/dubbo/rpc/filter/AccessLogFilter.java
25.00% <0.00%> (-44.74%)
:arrow_down:

...va/org/apache/dubbo/rpc/support/AccessLogData.java
53.16% <0.00%> (-37.98%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-13.80%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

... and 39 more

Continue to review full report at Codecov.

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


Cannot get symbol inside class decorator (Cannot read property 'members' of un...)

TypeScript Version:
1.8.10
Code
@Component({
  selector: SELECTOR
})
class SampleComponent {}
const SELECTOR = 'ng-demo';

Expected behavior:
With sample SyntaxWalker based on tslint, once I visit the PropertyAssignment - selector: SELECTOR and invoke typeChecker.getSymbolAtLocation(prop.initializer); I should get the SELECTOR symbol.
Actual behavior:
     TypeError: Cannot read property 'members' of undefined
      at resolveName (node_modules/typescript/lib/typescript.js:15307:73)
      at resolveEntityName (node_modules/typescript/lib/typescript.js:15725:26)
      at getSymbolOfEntityNameOrPropertyAccessExpression (node_modules/typescript/lib/typescript.js:28708:28)
      at Object.getSymbolAtLocation (node_modules/typescript/lib/typescript.js:28770:28)

why are you calling it on the initializer? this is the 'ng-demo' part. you probably want PropertyAssignment.name
it shoudl not crash either ways, so that is a bug.

PRs are welcomed

Found a root cause. See ☝ linked issues!


update gateway api, gateway can enable ravenl3/ravenl7 and can select…

… multiple endpoints for ravenl7

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind enhancement
/kind feature
/sig network

What this PR does / why we need it:

support to enable/unenable raven l7 proxy
support to enable/unenable raven l3 tunnel
support for electing multiple replicas
support watch lb service for update the public ip for exposed gateway

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@River-sh The gateway CRD has been modified some fields and type. And does it support older version not a new cluster?

@luckymrwang  The new gateway crd can support the old version, which only adds the Spec attribute


Rebuild for GCC7

Needed to unblock gperf, which is needed to unblock qt.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

CI passed. @conda-forge/core this feedstock has been quite inactive so some intervention will probably be required.


[webview_flutter] Unable to focus on text input in webview

Is there an existing issue for this?

[X] I have searched the existing package issues
[X] I have read the guide to filing a bug

What package does this bug report belong to?
webview_flutter
What target platforms are you seeing this bug on?
Android
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
No provided. Please see the screenshot.

Steps to reproduce
Steps to reproduce issue:

Upgrade webview_flutter_android to 3.9.2

Important: I can only reproduce the issue on Android device in Release mode. I tested debug mode, the issue does not show. I think the showing of keyboard somehow caused the flutter app to re-render the webview.
Steps I used to fix the bug:

Downgrade webview_flutter_android to 3.8.2

I believe the bug was introduced two weeks ago in this PR: https://github.com/flutter/packages/pull/4533

Please revert that PR until some one come up with a better solution.
Expected results
Expected Behavior: When I tap to focus on a <input> element in webview, the soft keyboard shows and I can type normally.
https://github.com/flutter/flutter/assets/22270677/4efac599-71fd-4cbb-98b3-76d5a9c7c6d0
Actual results
Wrong behavior: When I tap to focus on a <input> element in webview, the page flashes with white screen, and automatically loose focus. The soft keyboard cannot open and I cannot type.
https://github.com/flutter/flutter/assets/22270677/3e151fdc-0e89-4215-a992-35a7792ddc51
Code sample
Code sample
No provided. Please see the videos I uploaded.

Screenshots or Videos

Screenshots / Video demonstration
Expected Behavior: When I tap to focus on a <input> element in webview, the soft keyboard shows and I can type normally.
https://github.com/flutter/flutter/assets/22270677/4efac599-71fd-4cbb-98b3-76d5a9c7c6d0
Wrong behavior: When I tap to focus on a <input> element in webview, the page flashes with white screen, and automatically loose focus. The soft keyboard cannot open and I cannot type.
https://github.com/flutter/flutter/assets/22270677/45441ca2-958b-49a2-bb32-ffa7bcc4c47e

Logs
Logs
No related logs.

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.10.6, on macOS 13.4.1 22F770820d darwin-x64, locale en-CN)
    • Flutter version 3.10.6 on channel stable at /Users/fondoger/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (4 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/fondoger/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.0

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.80.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.70.0

[✓] Connected device (3 available)
    • V2055A (mobile) • <IP_ADDRESS>:42651 • android-arm64  • Android 12 (API 31)
    • macOS (desktop) • macos               • darwin-x64     • macOS 13.4.1 22F770820d darwin-x64
    • Chrome (web)    • chrome              • web-javascript • Google Chrome 115.0.5790.170

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Thanks for the report @fondoger
I tried the plugin example and ran in release mode but was able to input and type in properly and it also showed up the keyboard properly as below:

I used latest plugin versions.  If above doesn't represent your case, can you provide us a minimal code sample so that we can make the issue actionable ?

Help, the same issue was found in version  webview_flutter: ^4.2.2

webview_flutter_android: 3.8.2 is work for me.
It seems to have occurred during the first installation.

1、install and open
https://github.com/flutter/flutter/assets/4929805/6e7a4749-a44d-4795-8edf-87cd3670ef67
2、kill app and then open app
https://github.com/flutter/flutter/assets/4929805/51988a7c-fe98-445e-b6c2-267ea8808980

I tried by using <input type="text"> in plugin example, ran in release mode in which the keyboard opened properly:


issue fixings

Coverage remained the same at 93.074% when pulling 869ae1fb67f50a3dfc55f5f0a5d465f006d426ba on dev into 3ed9a1db3f514c5fe787d46c5efa1f0428464269 on master.


Support for postgres index creation?

Is there a way, using dbt, to create an index in postgres as part of a run? Given that everything is a select, it's not clear where this functionality would live, and I couldn't find anything in the docs or issues about it.
Or, is the answer to just get out of postgres and move to BigQuery etc :) ?

Hey @ryantuck - you can accomplish this with a post-hook. You'll probably want to do something like
{{
  config({
    "materialized" : "table",
    "post-hook": 'create index if not exists {{ this.name }}__index_on_FIELD on {{ this }} ("FIELD")'
    })
}}

select ...

^ assuming the index you want to add is on a column called FIELD. If you find yourself doing this a lot, you can create a macro to add an index to an parameterized column. We also have a nascent postgres package that does exactly this :)
I think in general, dbt works best with Redshift/Snowflake/BigQuery, but sounds like there are at least a few folks using it on postgres with some success! Hope this helps :)

An issue I've found with the suggested hook is it seems to only add an index every second run. But if I remove the if not exists, then it fails on it already existing (after the first run).
Is this something to do with how dbt handles the cleverness of the table creation and renames? Is there a fix that will solve the immediate problem?

Discussion for that at https://github.com/fishtown-analytics/dbt/issues/804

Let's add first-class support for an index config to models running on Postgres. We support the analogues for Redshift/Snowflake/BigQuery -- we might as well support these natively on Postgres too.
We don't intend to prioritize this directly (we always recommend using a proper data warehouse with dbt like Redshift, Snowflake, or BigQuery), but I would be very happy to work with a community contributor to implement this functionality in dbt!

Hi all. Just wanted to update this issue with the workaround (Proposed by drewbanin in https://github.com/fishtown-analytics/dbt/issues/1945#issuecomment-576826021) we are going to use @ DoSomething.org. For context: our former data lead created this related issue https://github.com/fishtown-analytics/dbt/issues/1945#issue-526684234.
Macro
{% macro get_index_name(model, idx_name) %}
    {{ model.schema ~ '_' ~ model.table ~ '_' ~ idx_name ~ '_' ~ run_started_at.strftime('%Y%m%d_%H%M%S') ~ ' ON ' ~ model }}
{% endmacro %}

Usage
Creates indexes consistently on every run for the given table in the pattern <schema>_<table_name>_<idx_name>_<yyyymmdd_hhmmss>, e.g. "public_post_actions_unique_20200804_235704"
models:
    ds_dbt:
        ...
        model_name:
            table_mame:
                alias: post_actions
                materialized: table
                 post-hook:
                    - "CREATE UNIQUE INDEX {{ get_index_name(this, 'unique') }} (created_at, id)"

@drewbanin I've gone through a few iterations of my own macro to create an index in Postgres. I'd love to contribute it. It handles the timestamp naming above as well as supports indexes on multiple columns (and chooses the best index name such that the index name is a unique function of the columns the index is on).
Should I contribute it to the main repo or to the Postgres package? I'm a first time contributor and am happy to follow the process here.

nice one @arzavj ! @jtcohen6 what do you reckon the right home for a macro like this would be?

@drewbanin I agree with your statement last year about adding first-class support for index creation to dbt-postgres. It's such a common need and request.
I definitely don't think the Fishtown-maintained Postgres package is the right place for it—we haven't updated it in years, and we've never added it to hub.getdbt.com. At the same time, there is a hub package maintained by @sgoley, postgres_utils, which for now includes index and uindex macros but with eventual plans of much more.
I believe that package was spurred to creation by the proposal of custom Postgres types (https://github.com/fishtown-analytics/dbt/issues/2619)—for which, since it could be accomplished via a simple DDL statement wrapped in a Jinja macro, I didn't want the dbt contribution/release/etc process to be an obstacle. In retrospect, I don't know if that was the right call; I'm going to own that and clean the slate.
We know that indexing is used by so many dbt-postgres users. I'm be in favor of adding:

index as an adapter config
A create_index macro here that prepares the appropriate DDL, including the finer points that @arzavj mentions above. (And maybe handles unique naming or drop index if exists, too? See discourse.)
An update to the table materialization that executes create_index after create_table_as, before closing the transaction. Given that postgres uses the default table materialization, we'll need to think about how to do this in a way that doesn't affect other databases. A dispatched macro, whereby default__create_index noops? Appending it to the set of inside-transaction post_hooks?

@arzavj Is that code you'd be interested in contributing?

@jtcohen6 yes that sounds good! I'll get my dev env set up and start working on this

@jtcohen6 would love to get your thoughts on the first draft above

We know that indexing is used by so many dbt-postgres users. I'm be in favor of adding:

@jtcohen6 such a synchronicity to find this issue / thread today as I've been trying to revive my package, find some time to work
on it, and make some initial overtures towards work in this area exactly.
To make sure I understand the path forward correctly, you are putting forward these options:

make indexes a first class citizen of the python adapter to postgres from dbt
add indexes to the dbt postgres adapter default macros
fold indexes into the table materialization script itself

From my perspective, I was thinking path 2 was the best route forward here but I was starting to plan for the package to "override" the default adapters.sql for a database from a package. (That is possible correct?)
And then some of the things that I've run into in the testing of my package are the necessity of:

create or replace if not exists (otherwise indexes will be full re-built during every run including incremental runs)
index types (since postgres supports multiple and even further extends that with index extensions like trigram

Just some thoughts!

Glad to have you here, @sgoley!
The three things I listed weren't mutually exclusive options, but rather (in my view) the three necessary ingredients of a solid implementation:

Adding index as an adapter config enables users to set this config from dbt_project.yml as well as in-file config() files.
Wrapping the necessary PostgreSQL in a Jinja macro, for modularity/accessibility/cleanliness.
If the index config is specified on a model, the Postgres materializations should take notice. Good callout of incremental models—we'll want to create the index for new and full-refresh runs, but not incremental models. We could accomplish that via if not exists, or should_full_refresh(), or (ideally) both.

@arzavj Thanks for taking the plunge here! I'll check out #3106 momentarily, and would invite others to do the same. The more eyes on that code, the merrier.


Fix up some tests for woql.js

@kevinchekovfeeney mind merging this PR? It's getting super long now... I believe all test here is up to date.


Call out code style enforcement as experimental part 2

Summary
Calls out that enforcing code style on build is experimental

CC: @mavasani @mikadumont


251/patroni

follow up from https://github.com/bcgov/digital_marketplace/issues/251

@bdolor  - Do you need someone to review this?

no review necessary. Since there was/is no buildConfig saved in the codebase, a new build had to be triggered via OpenShift GUI. This change to the deploymentConfig merely captures what was done in the GUI.

Closing ticket.


spkl.fakes

Hi Scott
Great job (once again)!
With spkl.fakes is it currently possible to mock LINQ queries?
Cheers

Perfect, thanks Scott!

Hi Scott,
I am also trying to use Linq with last binding (OrganizationServiceContext().CreateQuery). Using  pluginPipeline.FakeService.ExpectRetrieveMultiple throws the error:
Fake Organization Service expected 'RetrieveMultiple' but 'Execute' was called
I tried using ExpectExecute with retrieveMultipleRequest as delegate is fine but with this we can't return any results. It returns OrganisationResponse (casted to RetrieveMultipleResponse) which doesn't allow setting EntityCollection property, and therefore being unable to get the result entities!
Is there a way to include these results on response of ExpectExecute delegate?

Please ignore previous question, I have managed to get the response with desired EntityCollection entities. Thanks

Could you post the code you used for reference? Thanks

Yes sure, this is returning the returnEntities collection. Thanks
            pluginPipeline.FakeService.ExpectExecute((retrieveMultipleRequest) =>
            {

                if (((QueryExpression)((RetrieveMultipleRequest) retrieveMultipleRequest).Query).EntityName != target.LogicalName)
                    throw new InvalidPluginExecutionException("Wrong entity!");

                var linqResponse = new RetrieveMultipleResponse
                {
                    Results = new ParameterCollection
                    {
                        {"EntityCollection", new EntityCollection(returnEntities)}
                    }
                };
                linqResponse.EntityCollection.EntityName = target.LogicalName;
                return linqResponse;
            });


Create Harshal Dhande

@HRD2002FFCOCPOOLREALMENARZO20 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


x/tools/gopls: consider adding opt-in support for symlinks

We currently have partial support for symlinks and no test coverage. We believe that some of the timeouts on the openbsd builder may be caused by the latency of evaluating symlinks.
Some options:

Remove support for symlinks completely and document this
Add opt-in OR opt-out support for symlinks via a configuration
Support symlinks by default, but disable support for symlinks in tests

/cc @heschik @findleyr

Remove support for symlinks completely and document this

This would painfully impact productivity if your editor has no support for opening multiple modules in single workspace.
I spent a lot of time recently to make it work and it still doesn't work well.
First of all, experimentalWorkspaceModule requires modules to be present inside single workspace root.
That means you must put all linked projects to be there.
So, let's say you have multiple projects (projectA and projectB) that use library1 and you want to use on-disk version of this library in both.
Your only option is to make a copy in both projectA and projectB. And it is bad. But that could be easily solved with symlinking library1 into both projects.
Yes, you can make gopls.mod and maintain that by hand. But that's not really a comparable option.
This also can be solved by allowing LSP client to provide workspace information (e.g. vscode has multi-root workspaces where every root not required to be in same subdirectory). But I am not aware if that's a thing right now.


[FLINK-2696] [test-stability] Hardens ZookeeperOffsetHandlerTest.runOffsetManipulationinZooKeeperTest

The test case ZookeeperOffsetHandlerTest.runOffsetManipulationinZooKeeperTest failed, because the ZooKeeper client could not connect to the ZooKeeper server. I suspect that this might be caused by contention of multiple test cases for the same port to bind to. Internally, Curator's TestingServer is started with a port which has been determined using NetUtils.getAvailablePort. Since the port is not directly bound, it is possible that another process uses the determined port and, thus, preventing the TestingServer from starting.

+1 to merge

+1 to merge

Failing test case is org.apache.flink.yarn.YARNSessionFIFOITCase.testJavaAPI and, thus, unrelated.

Merging it.


UI Improvements – Status Bar, Icons, and Cancellable Tasks

This PR enhances the VSCode extension's UI, with improvements made to the layout, typography, and the connect/disconnect commands for a cleaner interface.
Changes
UI Enhancements

Improved layout, typography, and interaction feedback
Colored icons for warnings, errors, and server URL (when connected)

Status Bar

Addresses and fixes issue #8 .
Consolidated status bar items into a single item and removed icon colors (as recommended by vscode docs)
Dynamically displays active stack name or 'loading...' message
Replaced server icon with a shrine icon for better differentiation

Task Cancellability

'Connect' and 'Disconnect' operations now support cancellation

Environment View

Consistent loading indicators and state representations during LSP server restart
Enhanced refresh and state change logic for accurate updates

Console and Notifications

Cleaned up console output
Reduced notification frequency

Loading Indicators

Added to stacks and pipeline views for visual feedback during data retrieval or refresh

Authentication Error

Addresses #19 for authentication errors related to long-lived connections ("Authentication error: error decoding access token. You may need to rerun zenml connect")
Relevant views will now show the error for direct feedback:

Lint/format

Added ruff to the requirement.in file and updated the scripts/lint.sh to use ruff instead of nox --session lint, followed by eslint for typescript. Addresses #11.

Summary by CodeRabbit

Documentation

Updated the Slack Community link in the contributing guidelines.

New Features

Added new Python-related functions for better extension integration.
Introduced a new constant for ZenML client state change notifications.
Enhanced error, loading, and pagination tree items in the activity bar with additional parameters and functionality.
Improved server and stack views in the activity bar with new logic for displaying statuses and handling authentication errors.
Refined the status bar functionality to display server status and active stack information more efficiently.

Bug Fixes

Corrected typos and simplified error message handling in various components.
Fixed parameter declaration in the ZenKeyError method and improved logic for fetching stacks.
Updated the Python package dependencies and linting script for better code quality.

Refactor

Made formatting adjustments and added comments to improve code readability and maintainability across several files.
Restructured command registration and error handling for clearer logic flow.
Refactored event subscription and handling in the environment data provider for better state management.

Style

Updated string literals for consistency and improved icon path assignment logic based on themes.

So #8, #19 and #11 will be complete when we merge / release this?

Yes, all 3 should be complete after merging this 👍


Change script to allow other services restarted as well

Currently, with every update of anvil I need to modify the script to allow for other services, not explicitly mentioned in the script, to be restarted as well.
Services are (for instance) mattermostd, courier-imap-imapd-ssl, sabnzbd and others.

What? I have users?

Yeah, I wonder how best to do this. Sounds like a hook-type thing.
Here, run 'this script'.
How would you prefer to handle it? A configuration item:
USER_RESTART="mattermostd courier-imap-imapd-ssl sabnzbd"
USER_RELOAD="foo bar"

for service in $USER_RESTART
do
  service $service restart
done

for service in $USER_RELOAD
do
  service $service reload
done

Yeah! And I love it.
Cheers, Peter

On 30 Oct 2019, at 22:37, Dan Langille<EMAIL_ADDRESS>wrote:

What? I have users?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

This is a security risk, but it's all up to the user.

certpuller -s needs to be updated too.

This is a security risk, but it's all up to the user.

Not sure why this is a security risk: the script runs as anvil user, and as such it has no authorizations to restart whatever service, unless explicitly configured in sudoers

I ran this through on one server.  Do you want to give it a go?

Hi Dan,
Apologies for late answer: gonna try tonight

On 5 Nov 2019, at 14:49, Dan Langille<EMAIL_ADDRESS>wrote:

I ran this through on one server. Do you want to give it a go?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

It sounds like it worked.


App crash, on archived version

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
I experienced a crash but I can't replicate it locally only when I build the app and install it.
What did you expect to happen?
The app should not crash in the first place
What happened instead?
ℹ Please replace this with of what happened instead.
Alamofire Environment
Alamofire version: 5.2.2
Xcode version: 11.6
Swift version: 5
Platform(s) running Alamofire:
macOS version running Xcode: 10.15.5
Demo Project
ℹ Please link to or upload a project we can download that reproduces the issue.
This is the stack trace from firebase crashlytics
// This is how I created or initialized sessionManager
internal lazy var sessionManager: Session = {
        let configuration = URLSessionConfiguration.default
        let delegate = Session.default.delegate
        let manager = Session(configuration: configuration, delegate: delegate, startRequestsImmediately: true, cachedResponseHandler: nil, eventMonitors: [AlamofireLogger()])

        return manager
}()

Crashed: org.alamofire.session.rootQueue
0  libsystem_platform.dylib       0x18dfcc3d0 os_unfair_lock_lock$VARIANT$armv81 + 16
1  Alamofire                      0x104c39fbc Request.lastRequest.getter + 127 (__hidden#2399_:127)
2  Alamofire                      0x104c77f58 _hidden#6970_ (__hidden#7540_)
3  Alamofire                      0x104c2d9a0 _hidden#1656_ (__hidden#855_)
4  libdispatch.dylib              0x18df8a9a8 _dispatch_call_block_and_release
5  libdispatch.dylib              0x18df8b524 _dispatch_client_callout
6  libdispatch.dylib              0x18df68b3c _dispatch_lane_serial_drain$VARIANT$armv81
7  libdispatch.dylib              0x18df6954c _dispatch_lane_invoke$VARIANT$armv81
8  libdispatch.dylib              0x18df7284c _dispatch_workloop_worker_thread
9  libsystem_pthread.dylib        0x18dfdcb74 _pthread_wqthread + 272
10 libsystem_pthread.dylib        0x18dfdf740 start_wqthread + 8

If you're able to reproduce it, can you create a test project we can use to test?

I could but as of now I can't, I tried creating a new build the same issue
Crashed: org.alamofire.session.rootQueue.serializationQueue
0  libsystem_platform.dylib       0x1b6bfc3d0 os_unfair_lock_lock$VARIANT$armv81 + 16
1  Alamofire                      0x104a75fbc Request.lastRequest.getter + 127 (__hidden#2399_:127)
2  Alamofire                      0x104ab2f74 _hidden#6964_ +<PHONE_NUMBER> (__hidden#7540_:4367380340)
3  Alamofire                      0x104ab1b20 _hidden#2134_ + 218 (__hidden#7540_:218)
4  Alamofire                      0x104a8d0b4 _hidden#5162_ +<PHONE_NUMBER> (__hidden#855_:4367225012)
5  Alamofire                      0x104a9e39c _hidden#5298_ +<PHONE_NUMBER> (__hidden#855_:4367295388)
6  Alamofire                      0x104a9e378 _hidden#5297_ + 583 (__hidden#5723_:583)
7  Alamofire                      0x104a699a0 _hidden#1656_ +<PHONE_NUMBER> (__hidden#855_:4367079840)
8  libdispatch.dylib              0x1b6bba9a8 _dispatch_call_block_and_release + 24
9  libdispatch.dylib              0x1b6bbb524 _dispatch_client_callout + 16
10 libdispatch.dylib              0x1b6b98b3c _dispatch_lane_serial_drain$VARIANT$armv81 + 564
11 libdispatch.dylib              0x1b6b99580 _dispatch_lane_invoke$VARIANT$armv81 + 448
12 libdispatch.dylib              0x1b6b98a0c _dispatch_lane_serial_drain$VARIANT$armv81 + 260
13 libdispatch.dylib              0x1b6b9954c _dispatch_lane_invoke$VARIANT$armv81 + 396
14 libdispatch.dylib              0x1b6ba284c _dispatch_workloop_worker_thread + 580
15 libsystem_pthread.dylib        0x1b6c0cb74 _pthread_wqthread + 272
16 libsystem_pthread.dylib        0x1b6c0f740 start_wqthread + 8

Can you provide a more full crash report? I'd like to see the type of crash and platform.

The last comment I posted is the latest stack trace. I can't find a way to download the full crash report from crashlytics but I took a screenshot of it.

Here is another crash report screenshot

Hello? Any update? This is the stack trace from Crashlytics.
Crashed: com.apple.main-thread
0  libswiftCore.dylib             0x191416428 bool swift::RefCounts<swift::SideTableRefCountBits>::doDecrement<(swift::PerformDeinit)1>(unsigned int) + 8
1  Alamofire                      0x1029a77d0 Request.deinit + 29 (__hidden#5723_:29)
2  Alamofire                      0x1029ae1a8 _hidden#5050_ +<PHONE_NUMBER>
3  libswiftCore.dylib             0x191415714 _swift_release_dealloc + 28
4  Alamofire                      0x102979c74 _hidden#2574_ +<PHONE_NUMBER> (__hidden#855_:4340505716)
5  libswiftCore.dylib             0x191415714 _swift_release_dealloc + 28
6  libsystem_blocks.dylib         0x1d2f41784 _Block_release + 188
7  libdispatch.dylib              0x18d39e280 _dispatch_client_callout + 16
8  libdispatch.dylib              0x18d3805b8 _dispatch_main_queue_callback_4CF$VARIANT$armv81 + 856
9  CoreFoundation                 0x18d6e4c30 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
10 CoreFoundation                 0x18d6df0e8 __CFRunLoopRun + 2480
11 CoreFoundation                 0x18d6de200 CFRunLoopRunSpecific + 572
12 GraphicsServices               0x1a37d9598 GSEventRunModal + 160
13 UIKitCore                      0x18ffa4004 -[UIApplication _run] + 1052
14 UIKitCore                      0x18ffa95d8 UIApplicationMain + 164
15 Mycare tst                     0x102676f8c main + 15 (__hidden#295_:15)
16 libdyld.dylib                  0x18d3bd598 start + 4

Crashed: com.apple.main-thread
0  libswiftCore.dylib             0x1b8371d04 _swift_release_dealloc + 16
1  Alamofire                      0x100905c74 _hidden#2574_ +<PHONE_NUMBER> (__hidden#855_:4298808436)
2  Alamofire                      0x100905c74 _hidden#2574_ +<PHONE_NUMBER> (__hidden#855_:4298808436)
3  libswiftCore.dylib             0x1b8371d10 _swift_release_dealloc + 28
4  libsystem_blocks.dylib         0x1aa816a4c _Block_release + 148
5  libdispatch.dylib              0x1aa8ee524 _dispatch_client_callout + 16
6  libdispatch.dylib              0x1aa8a05b4 _dispatch_main_queue_callback_4CF$VARIANT$mp + 904
7  CoreFoundation                 0x1aaba67fc __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
8  CoreFoundation                 0x1aaba16d0 __CFRunLoopRun + 1724
9  CoreFoundation                 0x1aaba0ce8 CFRunLoopRunSpecific + 424
10 GraphicsServices               0x1b4ceb38c GSEventRunModal + 160
11 UIKitCore                      0x1aeccf444 UIApplicationMain + 1932
12 Mycare tst                     0x100422f8c main + 15 (__hidden#295_:15)
13 libdyld.dylib                  0x1aaa288f0 start + 4

I may be getting the same crash on my Authenticator.
This is my bt:
* thread #4, queue = 'com.journey.session.request', stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
    frame #0: 0x00007fff20360517 libsystem_platform.dylib`_os_unfair_lock_recursive_abort + 23
    frame #1: 0x00007fff2035b1a5 libsystem_platform.dylib`_os_unfair_lock_lock_slow + 258
    frame #2: 0x00000001087446ed Journey`UnfairLock.lock(self=(unfairLock = 0x00007f9314f05da0)) at Protected.swift:101:9
    frame #3: 0x0000000108744740 Journey`protocol witness for Lock.lock() in conformance UnfairLock at <compiler-generated>:0
    frame #4: 0x00000001087443d6 Journey`Lock.around<Self>(closure=0x0000000108745570 Journey`partial apply forwarder for closure #1 () -> A1 in Alamofire.Protected.write<A>((inout A) -> A1) -> A1 at <compiler-generated>, self=) at Protected.swift:39:9
    frame #5: 0x00000001087454af Journey`Protected.write<T>(closure=0x00000001086ddcf0 Journey`reabstraction thunk helper <A where A: Alamofire.Authenticator> from @callee_guaranteed (@inout Alamofire.AuthenticationInterceptor<A>.(MutableState in _3C9F9DFE4B92DED5A2689265F324D782)) -> () to @escaping @callee_guaranteed (@inout Alamofire.AuthenticationInterceptor<A>.(MutableState in _3C9F9DFE4B92DED5A2689265F324D782)) -> (@out ())partial apply forwarder with unmangled suffix ".13" at <compiler-generated>, self=0x0000600000cedec0) at Protected.swift:153:14
    frame #6: 0x00000001086d9323 Journey`closure #1 in AuthenticationInterceptor.refresh(result=success, self=0x000060000260ba20) at AuthenticationInterceptor.swift:342:32
    frame #7: 0x00000001084a5fb6 Journey`thunk for @escaping @callee_guaranteed (@in_guaranteed Result<BearerCredential, Error>) -> () at <compiler-generated>:0
  * frame #8: 0x00000001084a5982 Journey`ApiAuthenticator.refresh(credential=(accessToken = ""), session=0x00006000014daf00, completion=0x00000001084a6410 Journey`partial apply forwarder for reabstraction thunk helper from @escaping @callee_guaranteed (@in_guaranteed Swift.Result<JourneyKit.BearerCredential, Swift.Error>) -> () to @escaping @callee_guaranteed (@guaranteed Swift.Result<JourneyKit.BearerCredential, Swift.Error>) -> () at <compiler-generated>, self=0x000060000260b2d0) at ApiAuthenticator.swift:27:13
    frame #9: 0x00000001084a5f4e Journey`protocol witness for Authenticator.refresh(_:for:completion:) in conformance ApiAuthenticator at <compiler-generated>:0
    frame #10: 0x00000001086d904d Journey`AuthenticationInterceptor.refresh(credential=, session=0x00006000014daf00, mutableState=Alamofire.AuthenticationInterceptor<JourneyKit.ApiAuthenticator>.MutableState @ 0x0000600000ceded8, self=0x000060000260ba20) at AuthenticationInterceptor.swift:341:23
    frame #11: 0x00000001086d7e7c Journey`closure #1 in AuthenticationInterceptor.adapt(mutableState=Alamofire.AuthenticationInterceptor<JourneyKit.ApiAuthenticator>.MutableState @ 0x0000600000ceded8, urlRequest=Foundation.URLRequest @ 0x00007000003223b0, session=0x00006000014daf00, completion=0x0000000108800c80 Journey`partial apply forwarder for closure #4 (Swift.Result<Foundation.URLRequest, Swift.Error>) -> () in Alamofire.Session.performSetupOperations(for: Alamofire.Request, convertible: Alamofire.URLRequestConvertible) -> () at <compiler-generated>, self=0x000060000260ba20) at AuthenticationInterceptor.swift:270:17
    frame #12: 0x00000001086d808d Journey`partial apply for closure #1 in AuthenticationInterceptor.adapt(_:for:completion:) at <compiler-generated>:0
    frame #13: 0x0000000108745552 Journey`closure #1 in Protected.write<T>(closure=0x00000001086d8070 Journey`partial apply forwarder for closure #1 (inout Alamofire.AuthenticationInterceptor<A>.(MutableState in _3C9F9DFE4B92DED5A2689265F324D782)) -> Alamofire.AuthenticationInterceptor<A>.(AdaptResult in _3C9F9DFE4B92DED5A2689265F324D782) in Alamofire.AuthenticationInterceptor.adapt(_: Foundation.URLRequest, for: Alamofire.Session, completion: (Swift.Result<Foundation.URLRequest, Swift.Error>) -> ()) -> () at <compiler-generated>, self=0x0000600000cedec0) at Protected.swift:153:23
    frame #14: 0x0000000108745591 Journey`partial apply for closure #1 in Protected.write<A>(_:) at <compiler-generated>:0
    frame #15: 0x00000001087443e4 Journey`Lock.around<Self>(closure=0x0000000108745570 Journey`partial apply forwarder for closure #1 () -> A1 in Alamofire.Protected.write<A>((inout A) -> A1) -> A1 at <compiler-generated>, self=) at Protected.swift:40:16
    frame #16: 0x00000001087454af Journey`Protected.write<T>(closure=0x00000001086d8070 Journey`partial apply forwarder for closure #1 (inout Alamofire.AuthenticationInterceptor<A>.(MutableState in _3C9F9DFE4B92DED5A2689265F324D782)) -> Alamofire.AuthenticationInterceptor<A>.(AdaptResult in _3C9F9DFE4B92DED5A2689265F324D782) in Alamofire.AuthenticationInterceptor.adapt(_: Foundation.URLRequest, for: Alamofire.Session, completion: (Swift.Result<Foundation.URLRequest, Swift.Error>) -> ()) -> () at <compiler-generated>, self=0x0000600000cedec0) at Protected.swift:153:14
    frame #17: 0x00000001086d74e3 Journey`AuthenticationInterceptor.adapt(urlRequest=Foundation.URLRequest @ 0x00007000003226b0, session=0x00006000014daf00, completion=0x0000000108800c80 Journey`partial apply forwarder for closure #4 (Swift.Result<Foundation.URLRequest, Swift.Error>) -> () in Alamofire.Session.performSetupOperations(for: Alamofire.Request, convertible: Alamofire.URLRequestConvertible) -> () at <compiler-generated>, self=0x000060000260ba20) at AuthenticationInterceptor.swift:252:54
    frame #18: 0x00000001086daecb Journey`protocol witness for RequestAdapter.adapt(_:for:completion:) in conformance AuthenticationInterceptor<A> at <compiler-generated>:0
    frame #19: 0x00000001087ff711 Journey`Session.performSetupOperations(request=0x00006000011cc7e0, convertible=(payload_data_0 = 0x726573752f697061, payload_data_1 = 0xec000000656d2f73, payload_data_2 = 0x00000001088cdb38 type metadata for Alamofire.UploadRequest, instance_type = JourneyKit.UserMeRequest, witness_table_URLRequestConvertible = 0x00000001088a7f00 Journey`protocol witness table for JourneyKit.UserMeRequest : Alamofire.URLRequestConvertible in JourneyKit), self=0x00006000014daf00) at Session.swift:1050:17
    frame #20: 0x00000001087fdb9b Journey`Session.performDataRequest(request=0x00006000011cc7e0, self=0x00006000014daf00) at Session.swift:995:9
    frame #21: 0x00000001087fd7d6 Journey`closure #1 in closure #1 in Session.perform(request=0x00006000011cc7e0, self=0x00006000014daf00) at Session.swift:983:49
    frame #22: 0x00000001086da460 Journey`thunk for @escaping @callee_guaranteed () -> () at <compiler-generated>:0
    frame #23: 0x0000000109088ef8 libdispatch.dylib`_dispatch_call_block_and_release + 12
    frame #24: 0x000000010908a130 libdispatch.dylib`_dispatch_client_callout + 8
    frame #25: 0x000000010908cfd3 libdispatch.dylib`_dispatch_continuation_pop + 577
    frame #26: 0x000000010908c08b libdispatch.dylib`_dispatch_async_redirect_invoke + 755
    frame #27: 0x000000010909e279 libdispatch.dylib`_dispatch_root_queue_drain + 334
    frame #28: 0x000000010909ed03 libdispatch.dylib`_dispatch_worker_thread2 + 127
    frame #29: 0x0000000109133b28 libsystem_pthread.dylib`_pthread_wqthread + 244
    frame #30: 0x0000000109132b3f libsystem_pthread.dylib`start_wqthread + 15

it may be related to me creating my own queues? I followed the guidelines to use a serial one on root, yet request and serialization are concurrent.

Removed the custom queues from session and that's not it. Maybe this one is easier to read.

I could help my case by dispatching the completion here:
func refresh(_ credential: BearerCredential, for session: Session, completion: @escaping (Result<BearerCredential, Error>) -> Void)

The deadlock is produced by calling the completion immediately.

Sorry I'm not really sure what caused the issue. Can you enlighten me?

I would recommend you strip down your networking till you find something that might make sense. Specially any threading/queueing you may be using (since this is a deadlock).
Good luck.

oh no. It sounds like a lot of work.
From the screenshots you gave I hope this is the one causing it
internal lazy var sessionManager: Session = {
        let configuration = URLSessionConfiguration.af.default

        let delegate = Session.default.delegate
        let manager = Session(configuration: configuration,
                              delegate: delegate,
                              startRequestsImmediately: true,
                              cachedResponseHandler: nil,
                              eventMonitors: [AlamofireLogger()])

        return manager
    }()

    internal lazy var interceptor: Interceptor = {
        let oAuthAdaptor = OAuthAdaptor(baseUrl: self.configuration.baseUrl, persistenceService: self.persistenceService)
        let oAuthRetrier = OAuthRetrier(apiManager: self, baseUrl: self.configuration.baseUrl, persistenceService: self.persistenceService)
        let interceptor = Interceptor(adapter: oAuthAdaptor, retrier: oAuthRetrier)
        return interceptor
    }()

// Then request looks like this
let request = sessionManager.request(
            url,
            method: method,
            parameters: parameters,
            encoding: encoding,
            headers: HTTPHeaders(headers ?? [:]),
            interceptor: interceptor
        ).validate()

@hernangonzalez Your crash seems to be a double lock within the AuthenticationInterceptor. As you've discovered, we (unintentionally) expect the refresh method of your Authenticator to be asynchronous. I'll see if I can get a fix out soon. In the meantime, an asynchronous dispatch of the completion handler should workaround the issue.
@aabanaag You have multiple different crashes. The first, with os_unfair_lock_lock$VARIANT$armv81 at the top of the call stack, appears to be some issue within os_unfair_lock itself. Your other two are different, one in the Swift runtime's deinit machinery, the other in dealloc itself. However, since the Alamofire portions of those crashes are hidden, it's hard to investigate. If you can get those properly resymbolicated that would help a lot.

@jshier I will do that today. Thank you!

@hernangonzalez You may also need to update your version of Alamofire, as your call stack is calling performDataRequest for what looks like an UploadRequest, which was a bug fixed in 5.0.5.

@hernangonzalez The issue should be fixed on the bug/authenticator-recursive-locking branch, please give it a try!

@aabanaag Have you been able to update to Xcode 12 / Swift 5.3? I wonder if that may fix your issues.

I tried publishing a build via testflight and I'm unable to replicate it but what I did was use appstore signing option, but I'll check if it fixed the issue.

Hello, I just got back to working on my app, and I still have the issue but only on ad-hoc builds.

I still have no clue on how to fix this. About the structure of my app, I have an SDK framework contains network calls and any network-related process for our backend which has the Alamofire dependency then I installed that framework onto my app. I think the reason why my crashes are hidden is due to the fact that it is from a framework that I installed onto the app. Any ideas on how to make sure the crashes from a framework gets unsymbolicated?

I'm closing this, we are using bitrise and I just updated the stack to use the newer xcode and this was resolved.

Thanks for keeping us updated!


format not supported on addMonitor ?

Thanks for this great lib :)
I've got several addMonitors running, which work great, but they're showing decimals places for what are integer values. So I tried format: (v: number) => Math.trunc(v) but it appears to just be ignored. The same format works fine on addInput, however, so is this just a limitation of addMonitor ?

Thank you for using Tweakpane. And yes, it should be added. I'll implement it later.

Implemented in #329. Please wait for the next release.

Great, thanks :)


feat: PuppetPadchat supports get QrCode for userSelf(can be scan by others for adding friend)

const user = wechaty.userSelf()
const qrcode = user.qrcode()
console.log(qrcode)

Need to notice that you can only generate a QR code for your self, cannot get other users' .

Had implemented with the branding new ContactSelf class.


Compatibility with stackview 0.9.0?

Hi there,
As of stackview 0.9.0 (which notably includes https://github.com/haesleinhuepf/stackview/pull/68), we start observing some errors when using napari-workflows in https://github.com/fractal-analytics-platform/fractal-tasks-core (see relevant issue: https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/827).
I don't have a minimal working example yet, but the specific error we hit is when calling numpy.unique on an array which is a napari-workflows output (that is, it comes from napari_workflow's Workflow.get(...)).
The output object has the following properties
fractal_tasks_core/tasks/napari_workflows_wrapper.py:550 napari_workflows_wrapper
    mask: (
        StackViewNDArray([[[ 0,  0,  0, ...,  0,  0,  0],
                           [ 0,  0,  0, ...,  0,  0,  0],
                           [ 0,  0,  0, ...,  0,  0,  0],
                           ...,
                           [ 0,  0,  0, ..., 60, 60, 60],
                           [ 0,  0,  0, ..., 60, 60, 60],
                           [ 0,  0,  0, ..., 60, 60, 60]],
                          [[ 0,  0,  0, ...,  0,  0,  0],
                           [ 0,  0,  0, ...,  0,  0,  0],
                           [ 0,  0,  0, ...,  0,  0,  0],
                           ...,
                           [ 0,  0,  0, ..., 60, 60, 60],
                           [ 0,  0,  0, ..., 60, 60, 60],
                           [ 0,  0,  0, ..., 60, 60, 60]]], dtype=int32)
    ) (StackViewNDArray) len=2

fractal_tasks_core/tasks/napari_workflows_wrapper.py:551 napari_workflows_wrapper
    mask.shape: (
        2,
        540,
        640,
    ) (tuple) len=3

where the shape look correct.
When we then pass it to numpy.unique, this leads to an internal error
ValueError: could not broadcast input array from shape (539,640) into shape (345599,)

where it's unclear to me what these shapes represent.

Would you mind clarifying what was the reason behind https://github.com/haesleinhuepf/stackview/pull/68, so that we can review whether this is a bug on our side? Thank you!

Thanks for reporting this @tcompa ! I also don't understand the issue yet, but I suspect that this is the relevant change:
https://github.com/haesleinhuepf/stackview/commit/afe4fd24baa492397fb9a7ab8c5f71cdd2e08672
CC @jo-mueller

but I suspect that this is the relevant change: https://github.com/haesleinhuepf/stackview/commit/afe4fd24baa492397fb9a7ab8c5f71cdd2e08672

Yes, I can confirm this is the case.
I tried using 0.9.0 but reverting that specific change, and the error was not there any more (reported in  https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/827#issuecomment-2320471319).

Ok, this should be fixed in stackview 0.9.1 - even though I'm afraid there may be more follow-up changes necessary.
The new version is available on pypi. Conda-forge may follow in 12-24h. @tcompa if you could test it again next week it would be awesome. Thanks for reporting the bug!

Hi @tcompa ,
thanks again for checking! In order to reproduce the new issue, I might need more details. I tested this minimal-working-example code (with stackvie 0.9.1) and it runs with no error:
import numpy as np
from stackview._static_view import StackViewNDArray

labels = StackViewNDArray(np.asarray([
    [0, 1],
    [2,0 ]
]))

labels[labels > 0] += 1

Can you modify it and cause the error you observe?
Thanks again!

Can you modify it and cause the error you observe?

Sure:
import numpy as np
from stackview._static_view import StackViewNDArray

labels = StackViewNDArray(np.asarray([
    [0, 1],
    [2, 0]
]))

labels = np.expand_dims(labels, axis=0)
print(labels)

I don't know whether calling expand_dims on a StackViewNDArray is meant to be supported, but this is the lowest-level Fractal operation that then triggers the error.

A similar example leading to the same error is
import numpy as np
from stackview._static_view import StackViewNDArray

labels = StackViewNDArray(np.asarray([[0, 1], [2, 0]]))
new_labels = labels.reshape((1, 2, 2))
print(new_labels)

Chiming in: Could the underlying problem be that StackView doesn't know how to handle singleton dimensions? If that's the case, an array.squeeze() in the stackview functionality (for instance here) should possibly do the trick? 🤔

If that's the case, an array.squeeze() in the stackview functionality (for instance here) should possibly do the trick?

Great idea! This could help indeed @jo-mueller , just the point the code is definitely wrong. The StackViewNDArray is no widget and also doesn't use any widget-related code.

Ok, one more attempt. I am now overloading all members of the StackViewNDArray by forwarding calls to the inner numpy array (details).
@tcompa would you mind trying again with stackview 0.9.2 ? It's on pypi already and conda will follow in 12-24h.

Fantastic, big thanks again for reporting the issue and for testing!

Fantastic, big thanks again for reporting the issue and for testing!


lazy load app on reload only

fixes #3431
fixes #3430
If neither --eager-loading or --lazy-loader are passed to flask run, the default is now to eager load on the first run, then lazy load on reloads. This makes the command fail immediately if there is already an error, and the server remains up if errors are introduced later.

Going to experiment with this, but if we get rid of the --lazy-loading option completely and always let the server fail on initial errors, we can match the semantics of app.run() and flask run at this point. flask run can be a call to app.run(), reducing a lot of duplication.
cc @miguelgrinberg

Very nice improvement, and so simple!
On the removing of code duplication between flask run and app.run(), I would be super happy if we can also expose the CLI through app.run(), along the lines of my PR #2781. So I think I would favor the reverse approach, which is to re-implement app.run() to use the flask run and CLI logic.

Well, that's what I get for staying up too late. We can't put this in app.run() because it could never be lazy, since the next reload would have to import app again. It has made me think about some other things though, so I might be able to change something down the line.


GitRepo: Downgrade repo to 2.13.8

For all 2.14 releases of repo until the current stable release 2.14.2
running sync with the --fetch-submodules option fails, for example for
the project used in GitRepoFunTest with these errors:
$ repo sync -c --force-sync --fetch-submodules

Fetching: 100% (2/2), done in 4.304s
Garbage collecting: 100% (2/2), done in 0.004s
Fetching: 100% (2/2), done in 0.010s
Garbage collecting: 100% (2/2), done in 0.004s
error: submodules/commons-text/: Cannot checkout oss-review-toolkit/ort-test-data-git-submodules/commons-text due to missing network sync; Run `repo sync -n oss-review-toolkit/ort-test-data-git-submodules/commons-text` first.
error: Cannot checkout oss-review-toolkit/ort-test-data-git-submodules/commons-text
error: submodules/test-data-npm/: Cannot checkout oss-review-toolkit/ort-test-data-git-submodules/test-data-npm due to missing network sync; Run `repo sync -n oss-review-toolkit/ort-test-data-git-submodules/test-data-npm` first.
error: Cannot checkout oss-review-toolkit/ort-test-data-git-submodules/test-data-npm

error: Unable to fully sync the tree.
error: Checking out local projects failed.
Failing repos:
submodules/commons-text
submodules/test-data-npm
Try re-running with "-j1 --fail-fast" to exit at the first error.

This issue does not occur with version 2.13.8, and also not with the
current master branch. Therefore temporarily downgrade to 2.13.8 with
the hope that the next release works again.

Is there already an upstream issue reported?


New Tradfri Device - Symfonisk

Link to the Device: https://www.ikea.com/de/de/p/symfonisk-fernbedienung-fuer-soundsystem-weiss-60370480/
click
double click
triple Click
and a analog value

tradfri.0
2020-01-04 22:27:41.735
warn
(26787) Unknown accessory type 8. Please send this info to the developer with a short description of the device!

tradfri.0
2020-01-04 22:27:41.729
warn
(26787) object was: {"3":{"0":"IKEA of Sweden","1":"SYMFONISK Sound Controller","2":"","3":"2.1.022","6":3,"9":21},"5750":8,"9001":"Test","9002":1578171261,"9003":65540,"9019":1,"9020":1578171395,"90

tradfri.0
2020-01-04 22:27:41.729
warn
(26787) found unknown property with key 15018

Sadly this doesn't include any information about the pressed buttons - just like the normal remotes.


bug: NGINX Ingress Controller 0.16 Chart Fails to install

Describe the bug
When deploying with the 0.16 chart the following errors are thrown:
Diagnostics:
  pulumi:pulumi:Stack (ingress-controller-maratest02):
    NGINX Ingress Controller will be deployed with the Helm Chart<EMAIL_ADDRESS>    Using Ingress Controller image:<PHONE_NUMBER>25.dkr.ecr.us-west-2.amazonaws.com/ingress-controller-maratest02:2.4.2

  kubernetes:helm.sh/v3:Release (kic):
    error: failed to create chart from template: chart requires kubeVersion: >= 1.21.0-0 which is incompatible with Kubernetes v1.20.0

Resources:
    + 2 created

To Reproduce
Steps to reproduce the behavior:

Deploy to AWS with the 0.16 chart and 3.0 KIC (unsure if this occurs on other clouds; will test separately).
KIC will error out with the above errors.

Expected behavior
KIC should deploy
Your environment
n/a
Additional context
None

At least for AWS, the workaround is to expressly use:

0.15.2 Helm Chart
2.4.2 Ingress Controller

The helm chart version and the Ingress controller version can be set in the configuration yaml (there is no prompt for them currently).

A combination of 0.15.0 and 2.4.0 works as well.


Deploy with Llama2

Hi SolidGPT team,
Are there any ways I can deploy your product with Llama2 or any other open source model?
I saw you have Llama manager but didn't find a way to use it.
BR,

Yes, we are working on using opensource model Llama2 as the LLM core to implement fully local deployment. We will update more about this cool feature in the future. Btw, we will publish our roadmap real soon

@wwwwww1020 Does the SolidGPT fully support Azure integration, any best practice for that?

would be great if was possible to use with LM Studio app

Yes you can easily deploy the project into Azure with Static App , container app and blob storage. We have provide the blob storage client manager let user easily store their data into the blob. We will provide more context about deployment in the further

would be great if was possible to use with LM Studio app

good idea we will do some research on this

So are you going to support Chinese LLM like ERNIE in the future?

So are you going to support Chinese LLM like ERNIE in the future?

Yes we are going to adding more model like ERNIE

Hey, did we have any update on LM Studio or anything similar which gives openAI compatible API?


Fill Lines

can you make it so you can disable the fill below the lines in a graph?

You can, using the fill property. You'll find all the info you need in the readme.


gfr_equation: invalid value warning

Warning that would be nice to be resolved:
microsim/microsim/gfr_equation.py:82: RuntimeWarning: invalid value encountered in double_scalars
return constant * (x.creatinine / crThreshold) ** exponent * 0.993**x.age

And these ones too:
See the caveats in the documentation: https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#returning-a-view-versus-a-copy
peopleDF.loc[:, "ageGroup"] = (peopleDF["age"] // 5) + 1
/Users/deligkaris.1/Library/CloudStorage/OneDrive-TheOhioStateUniversityWexnerMedicalCenter/MICROSIM/CODE/microsim/microsim/population.py:893: SettingWithCopyWarning:
A value is trying to be set on a copy of a slice from a DataFrame.
Try using .loc[row_indexer,col_indexer] = value instead
See the caveats in the documentation: https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#returning-a-view-versus-a-copy
peopleDF.loc[:, "ageGroup"] = peopleDF["ageGroup"].astype(int)
/Users/deligkaris.1/Library/CloudStorage/OneDrive-TheOhioStateUniversityWexnerMedicalCenter/MICROSIM/CODE/microsim/microsim/population.py:893: FutureWarning: In a future version, df.iloc[:, i] = newvals will attempt to set the values inplace instead of always setting a new array. To retain the old behavior, use either df[df.columns[i]] = newvals or, if columns are non-unique, df.isetitem(i, newvals)
peopleDF.loc[:, "ageGroup"] = peopleDF["ageGroup"].astype(int)
/Users/deligkaris.1/Library/CloudStorage/OneDrive-TheOhioStateUniversityWexnerMedicalCenter/MICROSIM/CODE/microsim/microsim/population.py:871: SettingWithCopyWarning:
A value is trying to be set on a copy of a slice from a DataFrame
See the caveats in the documentation: https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#returning-a-view-versus-a-copy
dfForAnnualEventCalc.rename(
/Users/deligkaris.1/Library/CloudStorage/OneDrive-TheOhioStateUniversityWexnerMedicalCenter/MICROSIM/CODE/microsim/microsim/population.py:892: SettingWithCopyWarning:
A value is trying to be set on a copy of a slice from a DataFrame.
Try using .loc[row_indexer,col_indexer] = value instead

The person-based code is not using Pandas as much. These warnings no longer exist.


add MultiStepLR; correct CosineDecay according to the original paper and pytorch

This is for better academic reproducibility and alignment with Pytorch to make it more user-friendly.

Add MultiStepLR which decays lr by milestones, as in Pytorch.
Correct the implementation of CosineDecay. In the original paper(https://arxiv.org/abs/1608.03983), if you check the formulation it is clear that the decay is epoch-wise, as in Pytorch. Making it batch-wise as now can lead to non-reproducible results for developers who switch between Pytorch and TF As most research papers now are in Pytorch, this bug will deter researchers from implementing/reimplementing methods in Tensorflow.
However for compatibility with old code, this argument is optional, so if you don't change anything it will be the old batch-wise decay.

Please remove all the unrelated files from this PR.

Please remove all the unrelated files from this PR.

Could you please identify those? I didn't add files.

Please note that there are a bunch of files in this PR are just format change, which is not related to this PR.
Please remove them.

Anything I need to do at this point?

We're waiting for the internal tests to finish running. (please change the tag to finish running once done, thanks!)

Hi,
Tests are failing with below error message   ```
File "/build/work/98b77b6d908e91741657894b0cf073ac979f/google3/runfiles/google3/third_party/tensorflow/python/util/module_wrapper.py", line 248, in _getattr
attr = getattr(self._tfmw_wrapped_module, name)
AttributeError: module 'tensorflow.compat.v2' has no attribute 'keras'

Hi,
Tests are failing with below error message
File "/build/work/98b77b6d908e91741657894b0cf073ac979f/google3/runfiles/google3/third_party/tensorflow/python/util/module_wrapper.py", line 248, in _getattr
    attr = getattr(self._tfmw_wrapped_module, name)
AttributeError: module 'tensorflow.compat.v2' has no attribute 'keras'

I haven't modified any part of this folder, so the problem should lie in your code?

It's hard to infer where this error occured as this is only a wrapper that doesn't exist in my directory. Could you please provide more information?

@rchao Could you please provide more context? It appears to be a package versioning issue with the test environment.

@sachinprasadhs could you provide some further comments?

Hi @rchao Any update on this PR? Please. Thank you!

Rick may not be able to further assist with this PR. Let's assign it again in our next triage.

Hello, Thank you for submitting a pull request.
We're currently in the process of migrating the new Keras 3 code base from keras-team/keras-core to keras-team/keras.
Consequently, merging this PR is not possible at the moment. After the migration is successfully completed, feel free to reopen this PR at keras-team/keras if you believe it remains relevant to the Keras 3 code base. If instead this PR fixes a bug or security issue in legacy tf.keras, you can instead reopen the PR at keras-team/tf-keras, which hosts the TensorFlow-only, legacy version of Keras.


Configure import/no-extraneous-dependencies for test code

https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-extraneous-dependencies.md
When writing unit tests, you sometimes install and use packages that are not part of the published library, so you install them as devDependencies. eslint doesn't know that, so it will complain that they should be normal dependencies.
Something similar could be the case for scripts and other tools you write.
For "projects" you can get away with moving these to normal dependencies, since everything should be installed anyway.
For libraries you do care about what is placed where, since it determines if it will be installed when your library is used by another project or library.
Currently I've added this to my .eslintrc.
  rules: {
    "import/no-extraneous-dependencies": ["error", {"devDependencies": ["**/*.test.ts", "**/test-utils/**/*.ts"]}]
  },

If we make this more generic, we might be able to include it in the default eslint-config?
Thoughts and suggestions are welcome!

Should we also add an exception to '**/*.stories.ts'?


Failed to get Pottage Soup tooltip in JEI

As I was browsing the JEI pages for this mod, I hovered over the "Pottage Soup" item, which did not have a crafting recipe. It also prompted me to hold shift to see the tootip, so I did, in case that explained how the item was obtained. However, it gave me an error and told me to check the log. Here it is: https://pastebin.com/sNwLrGa2
I am using alpha_c_09.
I also have a couple of questions - what are the Deceiver woods? What are the Nodes items? And how do I use the Respirator?
Thanks for your time! :)

Oh! Sorry to keep bombarding you with questions, but it seems the acid lakes effect you even if you're in a boat. Is there a way to avoid that?

It seems that you used an empty pottage, which can't be obtained even in creative mode. And you're right, the pottage doesn't have craft. It can only be obtained by using a bowl on a campfire pot. On how to build a campfire, read the description of the latest changelog.
Deceiver woods it's just a kind of tree.
 The luck enchanting can increase the chance.
The respirator can be opened by left mouse button click. You can use it by placing it in the slot above the helmet slot.
Acid should not affect you while you are in the boat. However, acid dissolves the boat itself.
You can disable this only through damage events.

Ah, okay. Unfortunately, the empty Pottage is the one that shows up in JEI, which is why I was confused. :) Thank you for the explanation! However, I could not find the camp
Another question about the respirator - I figured out that you need to right click it and put an item inside, so I was just trying random things from the creative tab to see what fit. xD I found that it was a Fiber of Foggy Sponge, but there doesn't seem to be a recipe to craft it, and I can't seem to find any in the world.
I've also got more questions... sorry, haha. If I'm going to put this in my modpack then I have to know how it works so I can incorporate it properly and explain it in the documentation. ^^; I've been trying to just play through it myself and test things, but I keep getting confused.

I could not seem to make a compost heap. I saw on the mod page that "two or more sides of the heap should be full blocks" - but I'm not sure what that means. I tried using multiple different types of soil, all of which were surrounded on all sides but the top. I tried with Compost (and everything else that MW adds, I didn't try vegetables or anything). Nothing seemed to work and I was not given the achievement.

I was testing out the "You Can Live" achievement, and it seems that while I'm next to the Filter Coal blocks (which I couldn't find a recipe for - I used JEI to cheat them in), my health does go down slower - but it continues to go down every few seconds. Is this intentional? I'm not sure if I'm doing something wrong or not.

Oh! And about the boat: You're correct, it does seem to break the boat. However, it also damages the player while inside the boat, before it breaks.
Would it be possible to add a config option to whitelist certain boats (such as for modpacks that have metal boats etc) to be unaffected by the acid? Not a big deal, just suggesting. :) Thank you very much for your time!

Oh and another tiny suggestion that's not really worth making a new thread over: Making Niobium Ore have a slight glow while in the world would be fantastic. I'm using Hardcore Darkness so they'll be extra hard to find, haha! It's totally fine if that's not something you'd be interested in doing, though. :)

Oh... How many questions...
1: Campfire hide under the chagelog spoiler. To create it you need to shift-click LMB with any stones in hand.
2: Only filter items can be put in the respirator. It is filter coal or foggy sponge fiber, but fiber must be washed with water bucket.
3. Compost heap. Try to shift-click LMB on hole in the ground with any biomaterial in hand. The ground hole has four walls around it )
4. Filter coal block doesn't protect you 100 percent, but it reduce the damage a little.
5. I'll think about it.
6. Niobium ore is already slightly glowing.
P.S. You can join to the discord server and ask other questions there. If I cat't help you, somebody will help )
P.S.S Sorry for English. I'm just learning.

Oops, I just realized that I forgot to delete some of that message earlier. I had figured out some of it, so I meant to remove those questions, but I guess I forgot. That's what happens when I try to do too many things at once, lol!
And oh okay! I had misunderstood the compost heap instructions, I'll try that out when I get back to my pc.
And thank you very much for all your responses! I totally missed the part on the mod page that mentioned the discord, I'll definitely join it instead of peppering you with questions here ^^;
Also your English is fine! I'm guessing you're from Russia (because your download link a while back was .ru)? Anyway, your English is way better than my second language is, so there's no need to apologize. Thanks again!


MiniPCI and USB Dongle Issue

Hello, i was recently trying to use a miniPCI module: SIERRA MC7700 and a USB Dongle AWUS036ACS - ALFA
I have the exampleimage 1.3.1
The problem with it is that even with an SIM card and the module connected the IOT detects it as USB :

And i cannot do nothing to use it ... ,

That is what i have right now...
In adittion , i have some weird issue when i try to install the drivers for the USB dongle , i receive a meesage that says that i have an wrong kernel header, but i was trying everything and nothing works :/ .
Im using this to guide me: https://github.com/morrownr/8821au-20210708
I would really appreciate your help with this, thanks in advance!!

Look like our kernel config is missing CONFIG_USB_SERIAL_SIERRAWIRELESS. You could add that to recipes-kernel/linux/files/iot2050_defconfig_extra.cfg and rebuild your own image.

Hello , thanks for the prompt response
That CONFIG_USB_SERIAL_SIERRAWIRELESS is a filé or a code line to write on that address? Sorry i am new on this

You will have to add a line with CONFIG_USB_SERIAL_SIERRAWIRELESS=m to that iot2050_defconfig_extra.cfg.


Do we really need GLEW ?

By making Viewer inherit from QOpenGLFunctions_4_1_Core we bring all the OpenGL 4.1 core functions to the namespace Viewer::
This might be a clean cross platform replacement for GLEW that is only needed on windows and can generate inclusion headache when combining with Qt ...
Actually, Viewer inherit from QOpenGLFunctions that bring OpenGLES 2.0 functions . why ?

Using QOpenGLFunctions instead of QOpenGLFunctions_x_y was an error (I
think I was mislead by the qt code samples), I'll fix this.
For GLEW I do not really know if we really need it or not, but I remember
having problems getting opengl working on windows without it.
I can't remember if the problem was getting the function definitions or
linking against them though. I'll give it a try.
On Sat, Nov 5, 2016 at 10:24 AM, MathiasPaulin<EMAIL_ADDRESS>wrote:

By making Viewer inherit from QOpenGLFunctions_4_1_Core we bring all the
OpenGL 4.1 core functions to the namespace Viewer::
This might be a clean cross platform replacement for GLEW that is only
needed on windows and can generate inclusion headache when combining with
Qt ...
Actually, Viewer inherit from QOpenGLFunctions that bring OpenGLES 2.0
functions . why ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AGGA-IRIT/Radium-Engine/issues/131, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABGWn7HhtZHTZ-JV08XudzWk37snZRcKks5q7EtKgaJpZM4KqNpd
.

Using QOpenGLFunctions instead of QOpenGLFunctions_x_y was an error (I
think I was mislead by the qt code samples), I'll fix this.
For GLEW I do not really know if we really need it or not, but I remember
having problems getting OpenGL working on windows without it.
I can't remember if the problem was getting the function definitions or
linking against them though. I'll give it a try.

Undid merge (pull request) because compilation failed.

Fixed by 62e1712fb1d633f6ab14b953c89e0c6b6b6ecc95. Closing


Refactoring to specialised functional interfaces

Hello,
I am a Graduate Student at Oregon State University, studying the impact of autoboxing. I am testing a tool, which analyses the source code to find opportunities to refactor the code to a specialised implementation for primitives, thus eliminating autoboxing. All the changes, have been done manually, and have been verified by me. I have many more such patches, I will be happy to contribute.

Interesting. We have generated a numer of classes just for the reasons you mention. I will take a look at this!

Please have a look at https://github.com/speedment/speedment/blob/master/CONTRIBUTING.md to see how to contribute to the project.

How does the tool work. Is it a GitHub project?

Sure. I ll create a new pull request against develop-3.0' branch.
I have not github-ized it completely yet. It works as an eclipse plugin for now.
You have to give mappings for classes.
Eg. Function -> IntFunction/IntUnary/etc. according to conditions,
Map -> fastUtil maps, or gs-collection maps or whatever you choose.
So anything can be set in the mappings. Even the classes you have made to avoid autoboxing.
In a nutshell,it analyses the autoboxing instances in the source-code, and refactors against a set of pre-conditions if mapping is available.

We are working towards, inferring the mappings too.

Sounds cool! Nice to be able to detect this automatically. Presumably we have missed a number of them... Make sure to sign the contributor license agreement and you will get a "fame spot" in Speedment main POM file!

Thanks a lot.
If you could guide me to what classes you have made for avoiding autoboxing(probably, being used in the hot-path). I could probably test the too, and use it as an opportunity to continue contribution. I can see some in  com.speedment.common.function and  com.speedment.common.function.collector

Check out the module Speedment - Runtime - Field. There are many specialized implementations for different field types like IntField and LongField.

@ameyaKetkar Did you sign the CLA?

Yes I did sign the CLA.
Thank you, I will look into what you mentioned.

Added to pom:

Ameya Ketkar (GitHub:ameyaKetkar)
America/Los_Angeles

Thanks a lot.


UwU wanguage a-a-added fow funny puwpose

What's n-nyew?!!

UwU wanguage fow funny puwpose (even it's nyot that funny) ÚwÚ
I think i-it w-wouwd be funny t-to have a (nyot t-that) funny wanguage muhahahahahaha

Pwease don't waugh at me meo *cries*
Nyow I d-d-doing with onye commit muhahahahahaha
RIP autocorrect

I tried using this language but apparently it breaks the app 😭.
There's a way to technically "adding alien language" but apparently it's a tedious work on flutter.

I tried using this language but apparently it breaks the app 😭.
Technically, there's a way to add "alien language" but apparently it's a tedious work on flutter.

Basically, you can use uwu in slang but you need to tell Flutter that en is active.
// Convert slang locale to flutter locale
extension on AppLocale {
  Locale get digestedFlutterLocale {
    if (this == AppLocale.uwu) {
      return AppLocale.en.flutterLocale;
    }

    // Return the actual locale
    return flutterLocale;
  }
}

// MaterialApp
locale: TranslationProvider.of(context).locale.digestedFlutterLocale,

Just my two cents if you still want the "uwu" language :joy:

The relevant line should be https://github.com/nullxception/boorusphere/blob/46eaaa6f0a46da8ef7e1aa20d02da7659354a6de/lib/presentation/boorusphere.dart#L71
The slang i18n does not know what locales are real.
Basically, you can use uwu in slang but you need to tell Flutter that en is active.
// Convert slang locale to flutter locale
extension on AppLocale {
  Locale get digestedFlutterLocale {
    if (this == AppLocale.uwu) {
      return AppLocale.en.flutterLocale;
    }

    // Return the actual locale
    return flutterLocale;
  }
}

// MaterialApp
locale: TranslationProvider.of(context).locale.digestedFlutterLocale,

Just my two cents if you still want the "uwu" language :joy:

Would be good, if it wouldn't break others things. Did you tried yet?

I would commit newer version of locales soon.


使用ILLA CLI 搭建 请求的api地址是localhost

Description
服务器搭建 地址应该是服务器的ip
Steps to reproduce
服务器搭建 地址应该是服务器的ip

ILLA Builder Version
1.6.4
Browser
No response
Operating System

[ ] macOS
[ ] Windows
[X] Linux

Additional Information
No response

Thanks for the feedback. We'll take a look.

We have fixed this error in https://github.com/illa-family/illa/pull/28.


Minimum value of Parameter range for HomeSeer Floodlight Sensor HS-FLS100+ is rejected

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
Previous PR#3701 was CLOSED but NOT fixed.  https://github.com/zwave-js/node-zwave-js/issues/3701
What causes the bug?
Unable to input parameter value of zero.  It is still using MIN of 10 and MAX of 900
For HomeSeer HS-FLS100+, Lux_Trigger_Threshold, allowed values are 0, 30-200, 255. Value 0 will NOT activate floodlight. Value 30 represents 10 lux, Value 200 represents 900 lux. Value 255 will activate floodlight regardless of ambient light level
What do you observe?
Zwave JS HomeSeer HS-FLS100+ parameter options:

This does NOT match the Z-Wave JS Database

What did you expect to happen?
Per the HomeSeer HS-FLS100+ Manual (located at - https://products.z-wavealliance.org/ProductManual/File?folder=&filename=MarketCertificationFiles/2947/HS-FLS100-user-manual2b-A501112779R.pdf

What did you see?

Device information
Manufacturer: HomeSeer
Model name: HS-FLS100+
Node ID in your network:
Currently on CORE 2022.2.1; SUPERVISOR 2022.01.1; HOME ASSISTANT OS 7.2
From Z-Wave log from RE-INTERVIEW:
2022-02-05T13:56:24.907Z CNTRLR   [Node 046] Interview stage completed: NodeInfo
2022-02-05T13:56:24.912Z CNTRLR   [Node 046] Interviewing Manufacturer Specific...
2022-02-05T13:56:24.913Z CNTRLR » [Node 046] querying manufacturer information...
2022-02-05T13:56:25.485Z CNTRLR   [Node 046] [+] [Manufacturer Specific] manufacturerId: 12         [Endpoint 0]
2022-02-05T13:56:25.488Z CNTRLR   [Node 046] [+] [Manufacturer Specific] productType: 513           [Endpoint 0]
2022-02-05T13:56:25.491Z CNTRLR   [Node 046] [+] [Manufacturer Specific] productId: 11              [Endpoint 0]
2022-02-05T13:56:25.493Z SERIAL » [ACK]                                                                   (0x06)
2022-02-05T13:56:25.498Z DRIVER « [Node 046] [REQ] [BridgeApplicationCommand]
│ RSSI: -74 dBm
└─[ManufacturerSpecificCCReport]
manufacturer id: 0x0c
product type:    0x0201
product id:      0x0b
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch:
Diagnostics
Driver Version: 8.10.2
Server Version: 1.14.1
Home ID: XXXXX
Server URL: ws://core-zwave-js:3000
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
No, it never worked anywhere
If yes, where did it work?
No response
Attach Driver Logfile
No Log file needed

FYI - I have updated to Currently on CORE 2022.2.1; SUPERVISOR 2022.01.1; HOME ASSISTANT OS 7.2 today, and I re-interviewed the node, and still have this failure.
Do I need to remove this device and re-add it, because I would have to climb up on a ladder to re-add it as it is mounted on the corner of my house (and I have 5 of these)?

PLEASE DO NOT TAKE ANY ACTION ON THIS YET... I might have opened this PT too early.
I was jsut informed that I need to wait for the Z-Wave JS addon to pickup the right zwavejs version, then update it, then reinterview.  See https://github.com/zwave-js/node-zwave-js/issues/3701

Let me know how it goes

Issue resolved, I did open this by mistake.


Update CustomHttpClient.php

My intelephense linter is throwing errors that $this->$_guzz is undefined (using PHP v7.3). This should fix it.

I just ran composer update but I am not sure why the checks fail.. unfortunately, I don't have much time to like into this further.. I have sent you an access request to this repo @stanleynguyen.

I just ran composer update but I am not sure why the checks fail.. unfortunately, I don't have much time to like into this further.. I have sent you an access request to this repo @stanleynguyen.

I just ran composer update but I am not sure why the checks fail.. unfortunately, I don't have much time to like into this further.. I have sent you an access request to this repo @stanleynguyen.

One of the dependency is problematic. It's been taken care of by #115

I just ran composer update but I am not sure why the checks fail.. unfortunately, I don't have much time to like into this further.. I have sent you an access request to this repo @stanleynguyen.

One of the dependency is problematic. It's been taken care of by #115

Thank you so much for the contrib @CorbaDigitpaint

Thank you so much for the contrib @CorbaDigitpaint


Error when trying to do any action on image on dev bot

Main bot is practically down (very slow response time), so I decided to use the dev bot on the support server. But when trying to do any action on an image, this error (or sometimes a different one) pops out:
Message: Error: Error: A number was expected

Stack Trace: Error: Error: A number was expected
    at Socket.<anonymous> (/mnt/CA60D24E60D2413D/Files/esmBot-rewrite/utils/image.js:59:36)
    at Socket.emit (node:events:379:20)
    at addChunk (node:internal/streams/readable:313:12)
    at readableAddChunk (node:internal/streams/readable:288:9)
    at Socket.Readable.push (node:internal/streams/readable:227:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

Please fix

Looks like I forgot to rebuild the image functions on my own rig after #57, should be fixed now

Looks like I forgot to rebuild the image functions on my own rig after #57, should be fixed now


java.lang.ArrayIndexOutOfBoundsException: arraycopy: last source index 32 out of bounds for byte[31]

Hi,
since bcprov_1.68 we see a lot of errors like this in our tests:
Caused by: java.lang.ArrayIndexOutOfBoundsException: arraycopy: last source index 32 out of bounds for byte[31]
at java.lang.System.arraycopy(Native Method) ~[?:?]
at org.bouncycastle.crypto.params.X25519PublicKeyParameters.(Unknown Source) ~[bcprov_1.68.0.jar:1.68.0]
at org.bouncycastle.jcajce.provider.asymmetric.edec.KeyAgreementSpi.engineDoPhase(KeyAgreementSpi.java:163) ~[bcprov_1.68.0.jar:1.68.0]
at javax.crypto.KeyAgreement.doPhase(KeyAgreement.java:579) ~[?:?]
I cloned the repository and did the following change in my repo:
X25519PublicKeyParameters.java line 22:
System.arraycopy(buf, off, data, 0, buf.length);
The arraycopy should only copy as much bytes as the buffer contains.
This helped fixing our errors. I would recommend changing this line.
Thanks
Laurence

See comments for https://github.com/bcgit/bc-java/pull/920 .

I could only estimate, but 1.69 may be around the end of April.