[tool_crash] FileSystemException: Failed to decode data using encoding 'utf-8', null

Command
flutter --no-color pub upgrade

Steps to Reproduce

...
...
...

Logs
FileSystemException: Failed to decode data using encoding 'utf-8', null
#0      _File._tryDecode (dart:io/file_impl.dart:615:7)
#1      _File.readAsStringSync (dart:io/file_impl.dart:624:7)
#2      ForwardingFile.readAsStringSync (package:file/src/forwarding/forwarding_file.dart:99:16)
#3      ErrorHandlingFile.readAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:218:22)
#4      _runSync (package:flutter_tools/src/base/error_handling_io.dart:590:14)
#5      ErrorHandlingFile.readAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:217:12)
#6      getGradleVersionForAndroidPlugin (package:flutter_tools/src/android/gradle_utils.dart:200:45)
#7      GradleUtils.injectGradleWrapperIfNeeded (package:flutter_tools/src/android/gradle_utils.dart:176:9)
#8      AndroidProject._regenerateLibrary (package:flutter_tools/src/project.dart:705:26)
<asynchronous suspension>
#9      AndroidProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:668:7)
<asynchronous suspension>
#10     FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:361:7)
<asynchronous suspension>
#11     PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:365:7)
<asynchronous suspension>
#12     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1350:27)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#15     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:348:9)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)

[✓] Flutter (Channel stable, 3.16.0, on Microsoft Windows [版本 10.0.19045.3031], locale zh-CN)
    • Flutter version 3.16.0 on channel stable at D:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db7ef5bf9f (3 weeks ago), 2023-11-15 11:25:44 -0800
    • Engine revision 74d16627b9
    • Dart version 3.2.0
    • DevTools version 2.28.2

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at D:\AndroidSdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = D:\AndroidSdk
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Users\A23544\AppData\Local\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop Windows apps (Visual Studio Professional 2019 16.11.26)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional
    • Visual Studio Professional 2019 version 16.11.33529.622
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 2022.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • 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-9505619)

[✓] VS Code, 64-bit edition (version 1.63.0)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • Pixel 3 (mobile)  • 8BHX1AWTN • android-arm64  • Android 12 (API 31)
    • Windows (desktop) • windows   • windows-x64    • Microsoft Windows [版本 10.0.19045.3031]
    • Chrome (web)      • chrome    • web-javascript • Google Chrome 104.0.5112.48
    • Edge (web)        • edge      • web-javascript • Microsoft Edge 119.0.2151.97

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

• No issues found!

Flutter Application Metadata
Type: module
Version: 1.0.0+1
Material: true
Android X: true
Module: true
Plugin: false
Android package: com.autel.voiceaiflutter
iOS bundle identifier: com.autel.voiceaiflutter
Creation channel: stable
Creation framework version: d211f42860350d914a5ad8102f9ec32764dc6d06
Plugins
path_provider_linux-2.2.1
path_provider_windows-2.2.1
shared_preferences-2.2.2
shared_preferences_android-2.2.1
shared_preferences_foundation-2.3.4
shared_preferences_linux-2.3.2
shared_preferences_web-2.2.2
shared_preferences_windows-2.3.2

Closing this as a duplicate of https://github.com/flutter/flutter/issues/65021


Aachen dataset running issue "Invalid HDF5 object reference"

hello:
Could you help me to check if I missed something? I'm trying to reproduce the Aachen dataset result. I tried both 1.1 and original one. They both failed at the same step. (all step above runs fine).
I'm running from windows 10 x64 bit. cuda 11 on 3090 card.
here is the log.
thank you so much
KeyError                                  Traceback (most recent call last)
 in
----> 1 sfm_match_path = match_features.main(matcher_conf, sfm_pairs, feature_conf['output'], outputs)
c:\users\cinetec\appdata\local\programs\python\python37\lib\site-packages\torch\autograd\grad_mode.py in decorate_context(*args, **kwargs)
24         def decorate_context(*args, **kwargs):
25             with self.class():
---> 26                 return func(*args, **kwargs)
27         return cast(F, decorate_context)
28
F:\temp\slam\superglue\Hierarchical-Localization\hloc\match_features.py in main(conf, pairs, features, export_dir, exhaustive)
89         print(name0)
90         print(name1)
---> 91         feats0, feats1 = feature_file[name0], feature_file[name1]
92         for k in feats1.keys():
93             data[k+'0'] = feats0[k].array()
h5py_objects.pyx in h5py._objects.with_phil.wrapper()
h5py_objects.pyx in h5py._objects.with_phil.wrapper()
c:\users\cinetec\appdata\local\programs\python\python37\lib\site-packages\h5py_hl\group.py in getitem(self, name)
262                 raise ValueError("Invalid HDF5 object reference")
263         else:
--> 264             oid = h5o.open(self.id, self._e(name), lapl=self._lapl)
265
266         otype = h5i.get_type(oid)
h5py_objects.pyx in h5py._objects.with_phil.wrapper()
h5py_objects.pyx in h5py._objects.with_phil.wrapper()
h5py\h5o.pyx in h5py.h5o.open()
KeyError: 'Unable to open object (component not found)'

I have never ran hloc on Windows so a crash is not unsurprising. The pair lists that I provide use UNIX-style paths with a '/' separator. For Windows you should edit these files to use the '' separator. Exporting the results in localize_sfm.py will also break. It might also crash elsewhere.

I have never ran hloc on Windows so a crash is not unsurprising. The pair lists that I provide use UNIX-style paths with a '/' separator. For Windows you should edit these files to use the '' separator. Exporting the results in localize_sfm.py will also break. It might also crash elsewhere.

Hi Skydes:
Thank you for your answer. I just tried run this script on ubuntu for the aachen v1.1 dataset. still exact same error at the same location. any idea?
thank you

Does it crash elsewhere? Or is updating the pair file sufficient? Did you need to apply the changes of PR https://github.com/cvg/Hierarchical-Localization/pull/29?

Does it crash elsewhere? Or is updating the pair file sufficient? Did you need to apply the changes of PR #29?
Hi Skydes. it seams aachen 1.1 dataset still crash. I guess the generated data and the path still conflict on windows.
trying the original 1.0 dataset now. will keep you update.

Closing this issue due to inactivity. Feel free to reopen it.

I also encountered a similar problem, but I was running in docker and the system was ubuntu 16

Loaded SuperGlue model ("outdoor" weights)
0%|          | 0/133066 [00:00<?, ?it/s]
Traceback (most recent call last):
File "/persist/Hierarchical-Localization/venv/lib/python3.6/site-packages/torch/autograd/grad_mode.py", line 28, in decorate_context
return func(*args, **kwargs)
File "/persist/Hierarchical-Localization/hloc/match_features.py", line 138, in match_from_paths
grp = fd[name0]
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "/persist/Hierarchical-Localization/venv/lib/python3.6/site-packages/h5py/_hl/group.py", line 288, in getitem
oid = h5o.open(self.id, self._e(name), lapl=self._lapl)

Could you please copy the entire traceback with the exception?
Did you make sure that the feature extraction ran smoothly beforehand?
Could you please catch the exception and print the requested key vs the keys contained in the hdf5 feature file? hloc.utils.io.list_h5_names might be helpful.

Could you please copy the entire traceback with the exception?
Did you make sure that the feature extraction ran smoothly beforehand?
Could you please catch the exception and print the requested key vs the keys contained in the hdf5 feature file? hloc.utils.io.list_h5_names might be helpful.

Thank you for your answer.I have just solved this problem. This problem has nothing to do with the code，thank you.

Could you please copy the entire traceback with the exception?
Did you make sure that the feature extraction ran smoothly beforehand?
Could you please catch the exception and print the requested key vs the keys contained in the hdf5 feature file? hloc.utils.io.list_h5_names might be helpful.

Thank you for your answer.I have just solved this problem. This problem has nothing to do with the code，thank you.

Hi, Can you provide the solution to this problem? I have the same issue but I don't know which part is wrong. Thank you!

Could you please copy the entire traceback with the exception?
Did you make sure that the feature extraction ran smoothly beforehand?
Could you please catch the exception and print the requested key vs the keys contained in the hdf5 feature file? hloc.utils.io.list_h5_names might be helpful.

Thank you for your answer.I have just solved this problem. This problem has nothing to do with the code，thank you.

Hi, Can you provide the solution to this problem? I have the same issue but I don't know which part is wrong. Thank you!

Have you solved this problem? I met the same issue...I guess the data format maybe wrong, but I can't solve it! Could you help me?

i sloved this problem by changing aachen data with aachen_v1_1 dataset...


6.1.0 webapp add context-path for proxy fail

hello , I want to add context-path for webapp, then i can use nginx to proxy it. Unfortunately, it fail.
I modify the webapp/webapp.yml as follow.
server:
port: 8080
context-path: /skywalking

Js codes can't access your new context. Change codes id you want.

Js codes can't access your new context. Change codes id you want.

Is there no some solutions now?

We don't have plan to provide such feature. Not relate to project goals.

won't it create issues if I want to push my frontend application being served at port 80 but skywalking is running at 8080. The browser will start throwing CORS issue. I think it is a general use case.
Currently all the UI loads directly from root context, an additional context configuration should be there. meanwhile this could be done by doing changes  in the code.

应该有个对策给这个场景。绝大多数公司都有安全限制。对外端口80这种都是严格控制不是任意服务可以独享的。常规情况下，多服务都是经80匹配location转发到后端服务。这是很基础的需求。


Is this integration working at all these days for anyone.

Is this integration working at all these days for anyone, for me I getting nothing on usage even though when I go in the bright app it is showing

Yes and No .
Elec is working ( i have solar and batteries ) so usage and costs are correct for me but nothing on gas (which is what i really wanted this for.

I installed it a couple of weeks ago just to monitor my electricity but it seems to have a figure stuck in it for usage of 0.43kWh costing £0.46p.
I uninstalled and re-installed (with reboots in between) but it's the same.
Th Bright app on my phone seems fine

Same issue for me, no gas data and electric stuck on 0.36kWh and £0.66

See issue #330

Hey, I've had a look at this myself and can see that I'm experiencing the same issue with electricity consumption. My Home Assistant log shows some data below but doesn't seem to make sense to me.

I decided to have a look at the API calls themselves to see if there are any things I can see there is an entry every 30 minutes with around 0.24kwh which makes sense for my usage.

I therefore think this may be related to the integration itself to HA rather than the Glowmarkt API. I do know there have been some issues with the DCC though, especially around the British Gas / Trilliant onboarding which have reduced updates from every x minutes to hours (temporarily).
I'm not overly familiar with the HA entity database but if there is a way of retrospectively creating or updating states via the API then we could work around that each run?

I too suspect that it's an issue with the integration. For a long time I was stuck on an older version of Home Assistant from last year (I think it was something like version 2022.10) and so consequently I had to use version 0.6.0 of this integration. On easter weekend I was able to update to HA 2023.1 and so I updated the integration to the latest version 1.0.3 which is when I then started seeing similar problems to what everyone else is reporting i.e. little or no gas or electricity usage being logged in HA. After a few days I rolled the integration back to version 0.6.0 and since then it seems to be working, not perfectly, but it is show almost-correct gas and electricity usage for each say since I've been back on that version, so definitely a lot better than 1.0.3!

0.6.0 used the previous version of pyglowmarkt - see commit 1de64c749cf878b1eebe4a7faa86eb1b0c8cc429 and #295, so it was not affected by the issue.

Hi I also have the same issue. Several weeks now. I have Electric but no gas data in both the phone app and Home assistant. It was working and I have changed nothing. I contacted Hildebrand & GlowMarket and they say they can see my Gas data at their end. I am using British Gas SMETS2 but the display unit has no built in WiFi. Are there any other methods available? Al

There is a fix that has been merged
https://github.com/HandyHat/ha-hildebrandglow-dcc/pull/331
This works for me and data is available again

This integration simply does not work.  The readings are sporadic at best and the #331 fix does not fix the issue.  Is this integration dead now or is there any development on going to fix it?  Like others I have also tried the API myself and get expected numbers back so I also suspect its an integration rather than API issue.  I haven't had any accurate readings for nearly 3 months now.

I think the DCC is always a day behind, never gives me a live reading.
I do have the Glow CAD and it updates live, updating every few seconds, using a custom component via MQTT

I think the DCC is always a day behind, never gives me a live reading.
I do have the Glow CAD and it updates live, updating every few seconds, using a custom component via MQTT

The data in the DCC itself is up to date, the glow app always shows my usage up to the previous hour. In the integration, I'm seeing readings for today for both electricity and gas, they seem very sporadic. Admittedly I'm not using much gas anyway at this time of year but electricity consumption should show non zero values for every hour and in the glow app it does show this, but not in HA. I'm still using version 0.6.0 of the integration because while it's by no means accurate, it seems to work better than the more recent versions.

Maybe it would be better if this plugin returns data in the same way as the phone app ( 1/2 hour periods ) so that it can be used in other ways.

I think the DCC is always a day behind, never gives me a live reading.
I do have the Glow CAD and it updates live, updating every few seconds, using a custom component via MQTT

Did you create this IHD component, can you publish/share it?!

No I didn't create it, it's here
https://github.com/megakid/ha_hildebrand_glow_ihd_mqtt


Automatically create first initial snapshot

Author Name: EOLE Team (EOLE Team)
Original Redmine Issue: 4437, https://dev.opennebula.org/issues/4437
Original Date: 2016-04-29

Hello,
Making some tests on a VM in ONE 4.14.2, I took disk snapshots to be able to redo my testing, but then I realise I forgot to create manually a first snapshot for the “untouched” image disk.
Normally, I do a @DELETE-RECREATE@ to revert to initial disk state, but this loose my snapshots.
Is it possible to create a first snapshot before starting a VM, if none are present?
Regards.

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2016-05-01T21:42:02Z

This make sense, we are working on the delete action for 5.0 to expose it under the admin interface. So this option will come in handy ...
Cheers

Original Redmine Comment
Author Name: Anton Todorov (Anton Todorov)
Original Date: 2016-07-04T20:33:44Z

Hi,
I would like to share my thoughts regarding this interesting feature request.
What do you think about a global configuration attribute/variable/ for this feature (enabled/disabled) then per Template and per Image attributes to override the global flag? In such way every admin will have the freedom to tune the OpenNebula behavior regarding the needs.
Kind Regards,
Anton Todorov

Original Redmine Comment
Author Name: EOLE Team (EOLE Team)
Original Date: 2016-08-23T08:59:22Z

Anton Todorov wrote:

Hi,
I would like to share my thoughts regarding this interesting feature request.
What do you think about a global configuration attribute/variable/ for this feature (enabled/disabled) then per Template and per Image attributes to override the global flag? In such way every admin will have the freedom to tune the OpenNebula behavior regarding the needs.

I personally think such configurability at different levels with the possibility to bloc or not the option to sublevels should be the de facto standard behavior ;-)
Regards.

Original Redmine Comment
Author Name: EOLE Team (EOLE Team)
Original Date: 2016-08-23T15:39:24Z

Hello,
I work around this issue by creating a @VM_HOOK@ to make the initial snapshot for each @OS@ disk if no snapshot exists:

The hook configuration

VM_HOOK = [
  name      = "initial_snapshot",
  on        = "RUNNING",
  command   = "initial_snapshot",
  arguments = "$ID" ]

The hook script

<code class="ruby">
#!/usr/bin/env ruby
1. coding: utf-8

1. -------------------------------------------------------------------------- #
1. Copyright 2016, Équipe EOLE<EMAIL_ADDRESS>                           #
1. Author: Daniel Dehennin<EMAIL_ADDRESS>                    #
1.                                                                            #
1. Licensed under the Apache License, Version 2.0 (the "License"); you may    #
1. not use this file except in compliance with the License. You may obtain    #
1. a copy of the License at                                                   #
1.                                                                            #
1. http://www.apache.org/licenses/LICENSE-2.0                                 #
1.                                                                            #
1. Unless required by applicable law or agreed to in writing, software        #
1. distributed under the License is distributed on an "AS IS" BASIS,          #
1. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.   #
1. See the License for the specific language governing permissions and        #
1. limitations under the License.                                             #
#--------------------------------------------------------------------------- #

##############################################################################
1. Script to implement initial snapshot for DISKs
##############################################################################

##############################################################################
ONE_LOCATION=ENV["ONE_LOCATION"]

if !ONE_LOCATION
    RUBY_LIB_LOCATION="/usr/lib/one/ruby"
    VMDIR="/var/lib/one"
    CONFIG_FILE="/var/lib/one/config"
else
    RUBY_LIB_LOCATION=ONE_LOCATION+"/lib/ruby"
    VMDIR=ONE_LOCATION+"/var"
    CONFIG_FILE=ONE_LOCATION+"/var/config"
end

$: << RUBY_LIB_LOCATION

require 'opennebula'
include OpenNebula

if !(vm_id = ARGV[0])
    puts "Missing VM ID"
    exit(-1)
end

RUNNING_STATE = OpenNebula::VirtualMachine::LCM_STATE.index('RUNNING')

1. Check if an image is of type OS
1. Params:
1. +image+:: an OpenNebula::Image object
def is_snapshotable?(image)
    image.info
    return !image.has_elements?("TYPE") \
           || image.retrieve_elements("TYPE") == ["0"]
end

1. Check if a disk of a VM already has a snapshot
1. Params:
1. +disk_id+:: ID of the disk
1. +vm+:: an OpenNebula::VirtualMachine
def has_snapshots?(disk_id, vm)
    return vm.element_xml("/VM/SNAPSHOTS[child::DISK_ID='#{disk_id}']") != ''
end

begin
    client = Client.new()
rescue Exception => error
    puts "Error: #{error}"
    exit(-1)
end

begin
    vm = OpenNebula::VirtualMachine.new_with_id(vm_id, client)
    vm.info
rescue Exception => error
    puts "Error: #{error}"
    exit(-1)
end

vm.each '/VM/TEMPLATE/DISK' do |disk|
    disk_id = disk.retrieve_elements("DISK_ID")[0].to_i
    image_id = disk.retrieve_elements("IMAGE_ID")[0].to_i
    image = OpenNebula::Image.new_with_id(image_id, client)

    if !is_snapshotable?(image) || has_snapshots?(disk_id, vm)
        puts "Nothing to do for disk #{disk_id}"
        next
    end

    puts "Create initial snapshot for disk #{disk_id}"
    vm.disk_snapshot_create(disk_id, "initial snapshot")
    begin
        sleep(1)
        vm.info
    end until vm.lcm_state() == RUNNING_STATE
end
</code>

Original Redmine Comment
Author Name: EOLE Team (EOLE Team)
Original Date: 2016-08-25T09:14:31Z

I upload new version of my hook (attachment:initial_snapshot) to skip persistent disk, include datablocks and provide more informations in logs.


Add mark as dangerous functionality

closes #1350
Adds the mark as dangerous functionality.

All of this can be squashed and merged.

I have no way of testing it myself, i use Linux (silly!)


Inventory-Setups-1.6

Inventory Setups 1.6:
Adds a way to view setups in game using the "Show worn items" menu.
Adds Spellbook to the setup so you can make sure you are on the correct setup
Adds a help button that links to the read me (https://github.com/dillydill123/inventory-setups#inventory-setups) which now contains pictures and gifs to help new users. This button can be hidden in the config (learning from jagex's mistakes).

FYI assert will cause client hanging if it evaluates to false.

Are asserts enabled in releases? I thought they are only active during debug. This is how I’ve always used them (in C++ for example).
I think the asserts are fine and won’t get triggered. But if you have a strong opinion on removing them I don’t have a problem either.

asserts are only enabled if you run with -ea

I believe they're only enabled for players running dev builds, but that will likely affect some nonzero number of players. See #292 for reference

It sounds like it won’t affect many players if one does trigger and I like having them in there for debug purposes. If you still think they should be removed it’s not a problem though.

I'll merge it as-is, but I worry with things like these that it will cause more traffic to #support if any of the assertions are buggy or overly strict.


ImportError: DLL load failed while importing nvdiffrast_plugin: the specified module cannot be found.

How To Solve this problem ? help

me too


@blueprint.response does not respect error responses

Hi! I'm using your library as a convenience wrapper and I really like it!
However, one thing I've come across is that when I use the @blueprint.response decorator on my view function, all responses are marshaled with the Schema and return a 200 response. The decorator does not respect when I've finished the request with an error code.
There are many times when I abort the request (using flask's abort) instead of returning data. flask-rest-api overrides my aborts and return {errors}, 409 statements, so for any view function that returns an error, I cannot use @blueprint.response. This means I'm using @blueprint.response for some of my view functions and not for others, which makes for some very inconsistent and bug-prone code.
As far as I can think of, there isn't a reason you would ever want to marshal an error response to the schema, right? So would it be possible for flask-rest-api to only marshal the response with marshmallow if the view function returns "normal" data, but respect things with error codes, like flask's abort? Maybe @blueprint.response could include a keyword arg like respect_errors which defaults to True or something like that?
Thanks again, great work!

Hi. Thanks for the positive feedback.
Please abort with flask-rest-api's abort. It is a webargs overload of flask abort that should do the right thing.
I do that a lot in my code and I do it the way you describe. The Schema in response is only used when going through the view func the "normal" way. When aborting, the overloaded abort stores info in the exception and the error handler in flask_rest_api/error_handler.py returns the error messages serialized as json. Maybe this deserves a few words in the docs.
The whole thing is a bit hard to grasp because it involves error messages being added to the exception object and exception handlers registered in the Flask app. This allows mimicking the behaviour of webargs, so that when aborting with a 422 (for instance when POSTing a Pet with a reference to a nonexistent category, which cannot be detected at input validation time but only when trying to write to the DB), the response is similar to a typical webargs validation error response.
Yet, there might be something else, because using flask abort, you wouldn't get the error messages correctly returned, but you would at least exit the function without marshshalling with the response Schema.
Try flask-rest-api's abort and if the problem persists, post a sample code here.
No need for a new parameter, what you want is current behaviour already.

So I tried to switch to flask_rest_api's abort, and no such luck.
But I think I've figured it out, and I think it's related to #7. Whoops.
So I've been using flask_classful's FlaskView in order to organize my API. As flask_rest_api is not compatible with FlaskView, I have been using the blueprint decorators, but not actually in conjunction with a blueprint.
It's fairly hacky, and it actually took me a while to get the two to work together, because I really liked the convenience provided by your decorators, but here's what I did.
In the __init__.py of my flask app, I defined a flask_rest_api Blueprint:
api_bp = Blueprint("api", __name__)

Then, in my flask_classful FlaskViews, I just imported api_bp whenever I needed it, and used the decorators to decorate the view functions in my FlaskView class.
Back in the root of my flask app, in my create_app function, I can then register these FlaskViews to the api_bp:
from .api.users import UserInterface
UserInterface.register(api_bp)

And then finally I register the flask_rest_api Blueprint with my app:
app.register_blueprint(api_bp)

Apparently this hacky method to get the two to work together is actually what is breaking my aborts.
Any thoughts? Thanks again!

Let's discuss this in #7.


Substrate-api-client only offeres balance pallet

To submit extrsinics from the enclave to the node, we somehow need to ensure the enclave has some funds. But currently this is not possible
https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/worker/src/main.rs#L709 does not transfer any balances because Polkadex node does not support balance pallet.
We should either
a) adapt https://github.com/Polkadex-Substrate/substrate-api-client/blob/master/src/extrinsic/balances.rs#L50
b) create an additional function (or even file) and adapt the worker
c) add the balance pallet to the Polkadex node
With asset ids only (option a) and b): Is there any main asset id that the enclave should pay in?

@haerdib clearly (b)
api-client is designed to support any pallet, so we can just call polkadex custom stuff easily by just assembling the call directly without using the helpers. Therefore, the worker needs to be modified to replace the transfer call with a custom one. Check api-client examples for that

@brenzi @haerdib We don't need to do that, Polkadex uses Balances Pallet, as you can see here https://github.com/Polkadex-Substrate/Polkadex/blob/develop/runtime/src/lib.rs#L399

Closing this issue then - the problem seems to lie somewhere else (see main issue #154 )


Bot dying a lot to dragon fireballs

Bug Description
Since the splash effect that dragon fireballs create is an entity, the bot does not avoid them
Same for lingering potions
Steps to Reproduce (as best as you can)

dragon fires fireball
bot tries to walk through fireball area and dies

Expected Behavior
bot avoids dragon breath
Actual Behavior
bot walks straight through dragon breath and dies
Crashlogs and Screenshots (if applicable)

Duplicate of https://github.com/toccatina/altoclef/issues/58


cannot obtain glyphicon glyphicon-menu-hamburger

Operating system and version (Windows10)
Browser and version (Chrome 86.0.4240.75 )

this is the code I'm trying to run
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Document</title>
    <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css">

glyphicons have been dropped from bootstrap https://getbootstrap.com/docs/4.5/migration/#components


Incorporate tosa/ tests into our test infrastructure

In #1466, we ran into some issues when adding the newly introduced tosa/ suite to relevant test targets, so this PR revamps this system to properly integrate tosa/ as well as simplify similar work in the future.
Instead of the state of the art with one check-stablehlo custom target and a bunch of suites becoming its dependencies, we now have three custom targets:

check-stablehlo-ci whose name makes it clear that this is what
runs in CI.
check-stablehlo-slow for slow-running tests like the testdata/
suite that we'd like to separate from the other suites, so that
humans don't have to run them every time.
check-stablehlo-quick for everything else.

Each suite becomes a dependency of either -slow or -quick, making its nature explicit and clearly documented.
Also, it looks like the tosa/ suite got broken by one of the LLVM bumps that happened between when its PR got created and when it got merged. I fixed those breakages too.

Thanks!


Change Class Name

instead of class GithubPlatform extends AbstractPlatform it should be
class Github extends AbstractPlatform

i will take this

i will take this task


fix projected query size calculation for queries with LIMIT

This is a backport of the fix in https://github.com/basho/riak_kv/pull/1609.
There was a bug in 1.5.0 where, for queries with a LIMIT clause, the projected query size was incorrectly computed. The LIMIT value was used as the number of chunks in the calculations and not as the number of rows as it ought to be.
Separately, this PR fixes the logic of the max query data size checks for the case where LIMIT is big but the WHERE range is small. Such queries should not be cancelled.

create jira issue

:+1:

+1

thumbs retry

:+1:


Is resigning possible?

I want to make my bot resign, but I can't find a method of doing that in the documentation.

let time run out

See also https://github.com/SebLague/Chess-Challenge/issues/6

If you return Move.Null it will forfeit the game due to illegal move, which I guess you could think of as resigning. I recommend you let the bot keep playing until mate though.


Added globe icon

Fixes Issue

Closes #701
Changes proposed

Updated the readme list of available icons adding the globe icon

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[X] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

hey @Panquesito7, I think you forgot to unlink the issue. 🙂


🚀 Feature Request: [C3] Automate bumping versions of frameworks

Describe the solution
Today we pin the version of the web frameworks we support in a json file. The process of discovering new versions, testing that they work with c3, and bumping them if possible is manual and time consuming. It would be useful to automate as much of this as possible to help with maintainability.
We should have a CI workflow that runs our existing tests on newer versions of framework and surfaces to the team newer compatible versions that we can move to. It would also alert us to new, incompatible versions of frameworks that need attention.

closing as dupe of https://github.com/cloudflare/workers-sdk/issues/3805


Fixed #33277 -- Blocked database connections in threads for SimpleTestCase.

ticket-33277

@David-Wobrock Do you have time to keep working on this?

Hey @felixxm
I haven't found the time yet to finish the work 😕
I hope to be able to tackle it in the coming weeks, but if you want to pick it up from here, feel free 🙂

Closing due to inactivity.


One ServiceLocator by deployed Verticle

Hello,
HK2VerticleLoader creates a new ServiceLocator for every deployed verticle as states following code:
// Each verticle factory will have it's own service locator instance
// Passing a null name will not cache the locator in the factory
locator = ServiceLocatorFactory.getInstance().create(null, parent);

That means that beans can not be shared if multiple Verticles are deployed programatically:
vertx.deployVerticle("java-hk2:my.awesome.verticle");
vertx.deployVerticle("java-hk2:my.awesome.another_verticle");

HK2VerticleFactory has attribute ServiceLocator locator but it always null.
Isn't it would be better to have a single ServiceLocator in HK2VerticleFactory shared between all verticles ?

Each verticle receives its own ServiceLocator instance for a couple reasons:

When running services with IsolatedClassLoader this is necessary, different jar version can be loaded
When using the vert.x redeploy feature you want to ensure new instances are created (and it could be a new version of a jar)

However, if you do want to share instances across verticles that can be achieved by programmatically setting the ServiceLocator on the factory as you mention.  Each verticle created will still have its own locator, but it will use that as the parent locator.  I was not able to come up with a good way to do it via configuration since it is not running in a vert.x context at that point, configuration is not available.
Does that makes sense?  Any suggestions on alternative approaches?
It would probably be good to add an explanation in the read me.

Thanks for your answer. It answers my current problem. I am starting working closely with Vert.x and HK2. If I have some suggestions or ideas I will not hesitate to propose via issues or pull-requests.


python312Packages.overpy: 0.6 -> 0.7

Description of changes
https://github.com/DinoTools/python-overpy/compare/0.6...0.7

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

Would you like to address the test failure on darwin? Setting __darwinAllowLocalNetworking = true; is likely enough.


[BUG] (re-)enable support for more ARM processors

Describe the bug
Deployment on current generally accessible ARM chips for SOC systems fails due to the Amazon base image used. Please (re-)enable support for more accessible ARM chips. System I have been trying to run Opensearch on with the current images is based upon a Rockchip RK3588 (approx. 2 years old) and that gives the following error (I expect the same on several Raspberry PIs btw):
Fatal glibc error: This version of Amazon Linux requires a newer ARM64 processor
                   compliant with at least ARM architecture 8.2-a with Cryptographic
                   extensions. On EC2 this is Graviton 2 or later.

Related component
Build
To Reproduce
Run the current images on a Rockchip RK3588 or other consumer friendly SOC and check the logs. The Amazon Linux image requires specific ARM architectures using fe:
helm install --namespace=opensearch --create-namespace opensearch opensearch/opensearch --values=values.yaml
kubectl logs -n opensearch statefulsets/opensearch-cluster-master configfile

Expected behavior
I expected Opensearch to run on my k8s environment where the base image would be more open to chipsets commonly used or desired by the community. I don't know if there is any specific reason why Amazon Linux is being used but I personally would have expected something like Alpine as the base image.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Helm Version: v3.13.1
Kubernetes Version: v1.29.2
CPU: Rockchip RK3588
Compute Module: TuringPi RK1
Additional context
I have been able to backtrace the issue till helm chart version 2.14.0 so far but then in the pods instead of in the statefulset. I also created an issue in the helm-charts repository (https://github.com/opensearch-project/helm-charts/issues/534) but that was closed with a pointer to this repository

Hi @mrboogiee,
Which version is the last version that support older arm processor?
Do you know if there a particular EC2 instance still support such processor?
As of now 1.x is using AL2 and 2.x is using AL2023 (with some older versions still on AL2).
Would you be able to describe your use case so we can take a look?
Thanks.

Hi @peterzhuamazon,
When deploying the helm template I can run helm template version 2.13.0 for the opensearch cluster which runs opensearchproject/opensearch:2.8.0 as image for the cluster nodes.
The helm template for dashboard works from version 2.12.0 down, where 2.11.0 runs the same image release (opensearchproject/opensearch-dashboards:2.8.0)
Which base images are being used for those releases I haven't looked into yet.
As to the question of which AWS EC2 instances run on older ARM processors I unfortunately am unable to help.
My use case is to run a logging environment in my home lab for multiple purposes (hardware used there is the TuringPi RK1). One of the simplest is to have long(er) term logging of the pods in my K8s cluster, another is to create some dashboards for my firewall logs.
I hope this provides you with some more information.


Generate JSON-RPC library clients using OpenRPC

Using OpenRPC you can describe your JSON-RPC interface, and generate clients accordingly. You can see how we did it for ethereum here: https://github.com/etclabscore/ethereum-json-rpc-specification
Specifically you may want to look at the openrpc.json file in the root.

This is great, do you know if there are plan to generate Go servers out of a OpenRPC spec?

Thanks for the suggestion @BelfordZ. This is certainly something we'd be interested in looking into.

@gchaincl Thank you for taking a look, and asking.
Yes. We are working on generated go clients at the moment. I'd expect it to be ready before the new year.
If you are interested in helping in the efforts to getting a great go client together, feel free to pop by the open-rpc github, specifically https://github.com/open-rpc/generator-client
ATM we dont have an issue filed for the go client, would greatly appreciate this as a contribution.
@hrharder No problem. If you need any help or have any questions, I'm at your disposal.
Great work on this project BTW. It's always refreshing to see good software development practices in crypto.

@gchaincl My appologies, I read clients! haha.
Server generating is on the cards for sure, but its a little bit more nuanced than client generation, since the implementation of the server would be left open - it presents a very different developer workflow. We are working on patterns for making this nice to use, but haven't quite landed on anything yet.

There are existing libraries that can do client/server generation natively in golang, its currently used for hyperledger burrow, take a look, might fit your needs:
https://github.com/gregdhill/go-openrpc

@BelfordZ appreciate it! Glad you're seeing some good practices -- we certainly try.
Appreciate the issue. Once we clear up some higher-priority tasks we have in the pipeline we'll circle back to this. I've wanted to try out OpenRPC for some time. :)

There are existing libraries that can do client/server generation natively in golang, its currently used for hyperledger burrow, take a look, might fit your needs:
gregdhill/go-openrpc

Thanks for sharing, I'll have a look


How to debug main process after packaging?

Forgive me if this is covered somewhere. I can't seem to find it.
I have an app that runs as expected when I launch from my source code via npm run dev. However the packaged app fails to load the necessary local files. I assume this is due to some ipc calls not working out, but I'm not sure how I should go about troubleshooting this since once packaged I no longer have access to the terminal for console.log. Any advice is much appreciated. Thank you!

What OS is this on?

I'd run the app from the terminal, say
Linux: ./myApp
Windows: myApp.exe
macOS [Installed] (I think): open -a myApp

Thanks Tribex. I am on OSX and tried your open -a myApp in terminal but it just launches the app and then nothing.

@yourfavorite On macOS I launch the app with a command like
myApp.app/Contents/MacOS/myApp
Or something like that, I can't remember the path to the executable off the top of my head

@MarshallOfSound Thanks!
open myApp.app/Contents/MacOS/myApp (without the -a flag) did the trick for me!

@yourfavorite
Running:
open myApp.app/Contents/MacOS/myApp
will run the app but I discovered that if you do need to pass in command line parameters, they will not show up in the renderer process. To get them to show up, you need to use exec instead of open:
exec myApp.app/Contents/MacOS/myApp --arg arg1=blah1 arg2=blah2

@JohannBlake open has --args to pass arguments through to the app.  E.g.
open MyApp.app --args --arg1=1 --arg2=2

On Windows:
Command Prompt
cd path/to/myApp/win-unpacked
myApp.exe
Git Bash
./path/to/myApp/win-unpacked/myApp.exe

Hi,
I have created a package of my ElectronApp and installed it into my local machine.
How can I debug my app's main process when I launch the app from windows->start?

hi,
how do you open in Linux?

See https://github.com/electron/electron-packager/issues/514#issuecomment-256530001

See #514 (comment)

Thanks!


[MOB-2491] refactor

moving test files into category folders
removing (most) author attributions

I am not sure about directory names with spaces in them. Makes it harder to write scripts etc. Consider renaming "Deep Linking Tests" -> "deep-linking-tests". This convention is consistent with out other repositories as well.

I am not sure about directory names with spaces in them. Makes it harder to write scripts etc. Consider renaming "Deep Linking Tests" -> "deep-linking-tests". This convention is consistent with out other repositories as well.

I am not sure about directory names with spaces in them. Makes it harder to write scripts etc. Consider renaming "Deep Linking Tests" -> "deep-linking-tests". This convention is consistent with out other repositories as well.

Fixed

I am not sure about directory names with spaces in them. Makes it harder to write scripts etc. Consider renaming "Deep Linking Tests" -> "deep-linking-tests". This convention is consistent with out other repositories as well.

Fixed


Rough align qc

Rough alignment QC.
Plots being generated are

IOU plot
Distortion plot

you did not want to include the rough slicer in this?

You already have rough slicer in render-modules... We can include that, but that would not be in this PR... Coz that's going to add little more complications in terms of the output files and manually viewing them..

you did not want to include the rough slicer in this?

You already have rough slicer in render-modules... We can include that, but that would not be in this PR... Coz that's going to add little more complications in terms of the output files and manually viewing them..

? oh, ok. I thought we had a whole meeting about this where you said you were including it in QC. I haven't looked at that code on months.

you did not want to include the rough slicer in this?

You already have rough slicer in render-modules... We can include that, but that would not be in this PR... Coz that's going to add little more complications in terms of the output files and manually viewing them..

? oh, ok. I thought we had a whole meeting about this where you said you were including it in QC. I haven't looked at that code on months.

Yes we did, but we discussed the output to be in ndviz as a stack with some markers to identify each row -z mapping. Will do that in the next PR...


Update game.md

Slowly working my way through it.  Today, the docs for game.json (Including a port of Starting Inventory, which is mostly word for word from the discord post)

Thanks for contributing to docs! I know I and the others need to get back to docs from time to time too 😃


README.md should be improved

Development section
npm ci
Would be nice to have a warning about minimal npm version. I had outdated npm version and it fails to run npm ci.
npm run storybook
Check package.json, there's no storybook script. Should be npm run start.
Components
Almost all tables are not well formatted. One example:

Many other tables are not well formatted.
Structure
Sections like Developing, Testing and Upgrading should be near the top. Or at least before the Components sections. As one has to scroll way too down to get the info how to run it.

@zrzka That's very strange formatting on the table, since it works with most other rendering tools. I guess no one has noticed it because until recently, the property tables were only exposed through the live storybook and weren't shown in the README.
I agree that we should be specifying supported node/npm versions (I believe npm >=5.7.0 is required for npm ci.
With regards to the structure, I disagree with you. For most users, the documentation is more important than development and testing information.

It appears that marked has a more relaxed table syntax than GitHub.
In marked the following is a valid table:
| First Header  | Second Header |
| ----------------------------- |
| Content Cell  | Content Cell  |
| Content Cell  | Content Cell  |

Whereas GitHub requires | symbols in the line below the table header, like this:
| First Header  | Second Header |
| ------------- | ------------- |
| Content Cell  | Content Cell  |
| Content Cell  | Content Cell  |

With regards to the structure, I disagree with you. For most users, the documentation is more important than development and testing information.

I agree that most users find docs more important than the development stuff. That's perfectly fine. Maybe we can fix this by just adding TOC at the top? Even manual one?
Something like:
# Table of Contents

* [Installation](#installation)
* [Usage](#usage)
* [Components](#components)
* [Development](#developing)
* [Testing](#testing)

Or move the dev & testing into a separate doc and link it at the top?

@zrzka The table of contents sounds like a good idea, I'd consider moving the dev and testing into a seperate doc if its starts getting weightier.


DockBuilder methods not available

As the title says, none of the DockBuilder* methods are available to use.  The referenced cimgui.h for the generator has them stripped out.  Can these be added back in?  I tried building the files myself with the official cimgui.h (with FILE stuff stripped out) and it's not working.  Were these removed for a reason?

I'm not familiar with the DockBuilder methods but it seems they are part of the internal API, which I'm not wrapping. I'm not planning on supporting since I don't really use it, but I just tried to build cimgui with the internal API and it works (well, I haven't tried actually using any of the internal methods, but everything compiles and the LÖVE test file works).
What errors are you encountering? Is it related to the FILE stuff? I had to add this line to cdef.lua for things to work:
typedef struct FILE FILE;

Could you give me some examples of the things you are trying to do, so I can test them as well?


runtime: array of type [8]interface{} is not comparable or hashable

What version of Go are you using (go version)?
go version go1.7.1 darwin/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/jelle/hack/backend/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.1/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8s/_2n6vtf514ddk4vc8vw3l2nr0000gn/T/go-build445284626=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
What did you do?
I created an array of type [8]interface{}, and filled the array with int(0)s. Since all elements of the array are comparable, I expected the array to be comparable (https://golang.org/ref/spec#Comparison_operators). However, it is not: Unlike an array of type [7]interface{} or an array of type [8]int, the array of type [8]interface{} is not comparable or hashable. See https://play.golang.org/p/aVgVglrGQS.
For context, the array of type [8]interface{} was created as a cache key for calls to sql/db.Query. A small wrapper converts the arguments to sql/db.Query into an interface array to use as key in a map[interface{}]interface{} holding previously fetched results.
What did you expect to see?
I expected the playground program to compile and run, without panicing even when uncommenting the comparison of the [8]interface{} value.
What did you see instead?
Comparing the array of [8]interface{} results in a compile-time error:
# command-line-arguments
main.main: call to external function type..eq.[8]interface {}
main.main: type..eq.[8]interface {}: not defined
main.main: undefined: type..eq.[8]interface {}

Trying to use the array as map key results in a panic:
panic: runtime error: hash of unhashable type [8]interface {}

/cc @randall77 @mdempsky

Dup of #17752

Yes, this should be fixed in 1.8.  @jellevandenhooff , can you try the 1.8 release candidate?

Ah, indeed. I can reproduce that it's fixed in Go 1.8 but broken in Go 1.7.

Thanks, 1.8rc1 works!


fix: Allow empty password in PostgreSQL trust authentication login

This PR reclaims the changes introduced in this PR later which got reverted by this PR
Description

The PR removes the empty password validation check for PostgreSQL while creating a new data source.
The JUnit test case is added for the same. Implemented using a separate PostgreSQL container with Trust Authentication enabled for the Same.
Please note for testing from UI perspective we have to create a user with Trust auth enabled to validate the above changes.

Fixes #14003
Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

JUnit

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=464f655

/ci-merge-check

/ci-merge-check

/build-deploy-preview skip-tests=true

/ok-to-test sha=dd96014


Handling unknown segments

Sometimes there will be segments defined by the source system that need to be rolled up into a LINQ to HL7 query. In such a case we need a way to select unknown segments.
I might want to query all the unknown segments skipping over all others. Here is a possible code fragment on how that query might look,
from unknown in query.Select<HL7Segment>().Where(x => x.SegmentId.HasValue && x.SegmentId.Value != "ORC")

Pretty sure this works given your samples.

Yeah, this looks something like,
from unknown q.Except<HL7Segment, ORC>()
I think we just don't have a test for this specific scenario. I will add one.


Support ADVANCED_OPTIMIZATIONS

All that is needed is modifying FFI to use x['attr'] syntax instead of x.attr.

I should note that this is issue is cleverly avoided when you add all the semantic-ui sources to the cabal file. However, this leads to other annoying issues and is also far less flexible (you can't choose which semantic-ui modules to use, for example).

Thanks for the suggestion.  Check out the latest commit.

Awesome! I was quite literally a couple hours too late in making one more comment:
You also need to construct the option objects using syntax like this:
opts = {};
opts['onChange'] = function() {...};
jQuery($...)['...'](opts);

because some of those fields still get rewritten and GHCJS does not provide any way to preserve quotes on the field names (e.g. { "onChange": ... }).


Add option to disable italics on keywords

currently there is no way to customize a theme within Zed unless you install this as a "dev extension." 😅
is this request just for personal preference or does Italics make it difficult to read within the editor somewhere?

This was possible on vscode extension.
Yes, italic keywords make code less readable for some.

possible on vscode extension

I'll leave this issue open for the possibility of when Zed makes themes more customizable like VS Code 😄

Yes, italic keywords make code less readable for some.

I'm planning to define more of Zed's tree-sitter syntax styling and coloring. The various italics will be adjusted when this is published

@ravshansbox found out that there's an experimental feature that overrides any theme you set to your own preference using the ~/.config/zed/settings.json file.

you can set the syntax sub list to override anything set here https://github.com/catppuccin/zed/blob/f376e3a02606b942566ad56efd3b9b07fefd8375/template.hbr#L167

I think the way it is currently done in Zed is to create a separate theme in the theme family that doesn't use italics. Check out this example of how the Night Owl theme handles it.

@Moshyfawn though I like this idea, we would essentially generate an additional 4 Themes for just italics/non-italics (and x4 for other variants) like the Arctis theme on vscode

I personally don't like this, but curious on whether anyone else in the Org disagrees? this port is modeled after the vscode theme and it doesn't have these variants 😅
cc: @sgoudham

Separate theme for every combination of options doesn't look good. What if someone asks for a "no bold" option?

Our VSCode port has a built-in option to enable italics. JetBrains actually does ship non-italics variants under the same plugin so I think it's more than fine.
Our new whiskers version actually makes generating these variants extremely trivial. I'd check out the matrix option for whiskers v2 in the docs!
cc: @nullishamy as she's currently going through porting repositories to our new version

Separate theme for every combination of options doesn't look good. What if someone asks for a "no bold" option?

I don't mind italic variants since other themes tend to offer these too, however I've never seen non-bold/bold themes shipped as "variants"
I believe I'd that close that type of issue as not planned or, as we've done with this issue, tag it with "currently not possible" or equivalent

i'll start a PR draft to create the non-italic variants. bold and other variants in the future would be GH issue labeled as such 🫡


Return sky diffuse irradiance components in sky diffuse dataframe

irradiance.perez can return isotropic, circumsolar and horizon components of sky diffuse irradiance if return_components = True.  Currently, if return_components then results are returned as a tuple (sky_diffuse, diffuse_components) with the elements being a pandas.Series and pandas.Dataframe, respectively.
I propose that we always return a Dataframe with column sky_diffuse and optionally columns for isotropic, circumsolar, horizon.  This avoids having the output of the perez model of a different type (tuple instead of pandas object) and having to unpack the tuple when diffuse_components are requested.

This is an interesting idea. I'm concerned about maintaining API compatibility across all of the transposition models. I think the default behavior of all of the models should be the same, if possible. So, I'm reluctant to default to returning a one-column DataFrame from perez while the others return Series.
We could make similar changes to all of the models. I don't know if that would be useful or busy work. What would the keys look like for each function? For example
isotropic returns sky_diffuse, isotropic?
haydavies returns sky_diffuse, isotropic, circumsolar?
perez returns sky_diffuse, isotropic, circumsolar, horizon?

Good point about compatibility.  We could return a Series if return_components = False rather than a one column data frame.  The hiccup for me is dealing with the tuple instead of a pandas object.
We could propagate the component capability into the other sky diffuse models, although perez is likely to be the most frequently used for this purpose.

Sure, that sounds like a quick fix then.
For reference, the return_components feature was added in #259. It does not appear that we discussed the idea of returning a single DataFrame with the total and the components.

@cwhanse I suggest that we limit the scope of this particular issue to irradiance.perez and create new issues if want to expand this feature to new transposition models.


Test TestAmbientIndex_WorkloadEntries_DisableK8SServiceSelectWorkloadEntries flake

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/47782/unit-tests_istio/1722063640388964352

I think it's similar issue with https://github.com/istio/istio/issues/47739, I'll check it.


lightburn: 0.9.23 -> 1.0.00

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/LightBurnSoftware/deployment/releases.
meta.description for lightburn is: "Layout, editing, and control software for your laser cutter"
meta.homepage for lightburn is: "https://lightburnsoftware.com/"
meta.changelog for lightburn is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

Warning: no invocation of /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00/bin/LightBurn had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00/bin/.LightBurn-wrapped had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00/bin/..LightBurn-wrapped-wrapped had a zero exit code or showed the expected version

0 of 3 passed binary check by having a zero exit code.

0 of 3 passed binary check by having the new version present in output.

found 1.0.00 with grep in /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00

found 1.0.00 in filename of file in /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00

directory tree listing: https://gist.github.com/ee919b2a93fe4551e96d923512f2be20

du listing: https://gist.github.com/8e2b6940a6ce1f7ee0ae1ac7b1f4623a

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
lightburn

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lightburn https://github.com/r-ryantm/nixpkgs/archive/bde1ee1865d4660a7279fe2391f0215bc771e735.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00
ls -la /nix/store/sd22vkfpixd5vkcmgl6sv88vrbf599jy-lightburn-1.0.00/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

lightburn

Maintainer pings
cc @q3k for testing.

Result of nixpkgs-review pr 134029 run on x86_64-linux 1

1 package built:

lightburn


Document Clarification Suggestion: change user /install?

-Install Microsoft 365 Apps on an RDS server-
this section above doesn't indicate whether or not the admin should change user /install to disable .ini file mapping before installing 365 Apps with ODT. AFAIK Office Click2Run does not rely on .ini file mapping but it would be a nice to have clarification in the Microsoft documentation as a confirmation from an official source.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/change-user
Please let me know your thoughts : )
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6da18a8b-9e96-0155-7b30-9c211070d793
Version Independent ID: 5a7e610a-bfcb-d9cc-03f7-589d970128d9
Content: Deploy Microsoft 365 Apps by using Remote Desktop Services - Deploy Office
Content Source: DeployOffice/deploy-microsoft-365-apps-remote-desktop-services.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

Our documentation focusses on listing what you have to do, rather then covering all the steps you should not do. Simply, because the later approach can never be complete. So in short, if the change user /install is not listed in the article, it is not required to perform on an RDS server. Is not listed > not required. Main reason is because Office does not rely on .ini files, so there is no need to redirect them.
Hope this helps as a clarification.


Updating the contributing doc

Updating the contributing doc with information about a common error I encounter when I don't have the correct environment variables set up.

@dwsupplee I didn't have my GOOGLE_PROJECT_ID defined, so everything got skipped with no message saying why. Maybe saying that here could be better? Idk

We don't require GOOGLE_PROJECT_ID for any tests in this repository. Perhaps this would be better fit against googlecloudplatform/php-docs-samples which does?


Design bug fixes

I think I forgot to sync my fork correctly before creating the branch and starting a new pull request.
Fixes #502
Fixes #649
Fixes #544

This PR should be good to merge now... After talking with Rachel, wide screen mode on the guides pages will be it's own backlog card since we would want to make every page on the site have a wide view. So more of a global approach @BrianMMcClain @bryanfriedman


Pinia's "Getting started" page lacks a basic example.

Reproduction
https://pinia.vuejs.org/getting-started.html
Steps to reproduce the bug

Go to the Getting started page
Read the Installation section. Try to do what is described there. Check that the given information is incomplete.
Read the What is a Store? section. Check terminology contradiction between "A Store (like Pinia) is..." and "Create a pinia (the root store)..." in the Installation section. The same thing appears to have three differnet names: a "store", a "pinia" and a "root store".
Read the When should I use a Store section. Read general information given in this section.
Reach the end of the page. No clear example was provided. Recheck the page again: no success. Look at left bar for a possible salvation: no success.

Expected behavior
The behavior I "expected" (in my opinion, which may be different from what is intended by Pinia's docs writer(s) ) was to read a documentation page that would enable a person with basic knowledge in Vue to carry out an introductory example of Pinia's usage.
Actual behavior
See the explanation given in the Installation section (emphasis added here):

Create a pinia (the root store) and pass it to the app:
import { createPinia } from 'pinia'
app.use(createPinia())

My (subjective) issues with this:

"Create a pinia (the root store) (...) [js code is shown]"  Should I create a new file? Where?
"...and pass it to the app" What "the" app? Where does app come from?

Additional information
No response

Added to https://github.com/vuejs/pinia/issues/829


Some characters and objects not loaded properly

Describe the bug
Some characters and objects are not loaded properly after updating Yaagl launcher. I have tried with all wines available, the game doesn't launch at all or has this problem. Dynamic character resolution is disabled
Screenshots

System Information (please complete the following information):

macOS: [Sonoma 14.5]
Device: [Macbook Air 13 inch 2020]
CPU: [Apple M1]
RAM: [8GB]

Which wine version are you using?

The same thing happens to me, I take care of v9.2-mingw

same happened with me too

i used the same v9.2-mingw which it gives on default

I've got same problem

try and switch your wine to unstable-bh-gptk-1.0 works pretty ok for me, not sure if there is any other fix

GPTK or Crossover wine option is best options for all ARM Macs atm, Consider switching to them right away.


Match data for https://theorangealliance.org/events/1819-CA-FTCSDGM1 is missing a lot of matches

Examples: Quals 2 and Quals 6 are not showing up on "MATCHES" tab. In raw data, Quals 2 only has 1 red participant instead of 2 (missing R2). Quals 6 is missing participant B1.

That is really weird. I will go reupload that event right now

https://theorangealliance.org/events/1819-CA-FTCSDGM1
So, @Techno11 @afera15 I cleared all of the team, rankings, and matches from this event page and then went to re-upload all the data, but it appears that the event page crashed/stopped working. I'll throw this one to you guys. Here is the .db file for the event (had to zip it first though)
sd_12082018_gauss_opening.db.zip

@Nate2019 For some reason not all of the matches were deleted. (not an issue of yours, but something with the api), Please try uploading the data again.

Same issue as before.... @Techno11

https://theorangealliance.org/events/1819-CA-FTCSDTM1 also seems corrupted

No idea what's going on... I can try to purge the data and upload again in a few minutes.

We are working on fixing this John. This isn't an issue we have seen with other league meets. Stay tuned for when its fixed.

Fixed


[Question]: Modded Dimensions & Recipes?

General Info

[X] I would like to propose new content
[ ] I would like to propose changes
[X] I would like to propose another thing

Suggestion Description
Hi, will this mod work for modded dimensions, such as the ones from DivineRPG  Also, what is required to craft them? Thanks!

Currently there's no modded support


feat: experiments API for IPFS Desktop

@cwaring this adds an experiments API for IPFS Desktop redux bundle so we can get the current enabled state, know if an experiment is available and toggle it. The API is:
To know if expId is available:
store.selectDesktopAvailableExperiments().includes('expId')

To know if expId is enabled:
store.selectDesktopExperiments().expId

To toggle expId:
store. doDesktopToggleExperiment('expId')

This should only be used for IPFS Desktop-related experiments such as NPM on IPFS.

@cwaring another option would be to mainly dispatch actions. For example, to toggle something, you'd dispatch an event called TOGGLE_NPM_ON_IPFS. Then, it is enabled by ipfs-desktop bundle.
If it fails, we could dispatch an event TOGGLE_NPM_ON_IPFS_FAILED with the error, otherwise we'd change the value of the option.
The main question, IMO, is to decide how to know wether or not the option is enabled:

One option could be what I said in the main post above, and you just selectDesktopExperiments().expId and it is always up to date.
Another option could be to dispatch an event and the experiments bundle would always contain the state itself. Problem with this? It would be harder to get the initial state in a first instance.

Yes, I believe actions (and effects) are the correct approach to manage this communication which would require the desktop bundle to dispatch an appropriate success or failure action on toggle. I would prefer these to be generic actions with a variable payload so that we don't need to add custom hooks for every new experiment.
Currently the webui experiments bundle persists the state of the feature, which also feels like the correct place for this data.
So my suggestion is:

I amend the webui to dispatch a generic toggle action that includes the key of the experiment the user is attempting to enable/disable
you respond to that action and execute the command to enable the functionality
depending on the result of # 2 you dispatch a success or failure action that webui monitors in order to update the enabled state

How does that sound?

@cwaring that sounds great!
But there's still a point missing: initially, how do you know if something is activated or not? Like, for example, I enable npm on ipfs, then refresh the page. How does Web UI know that it is activated? I know the state is persisted to the local storage, although IPFS Desktop settings might be changed manually, so their state would change.

Agree. That's the last missing step but I could use your suggested API here to get the initial values for any desktop experiments on boot.

@cwaring so to simplify, you can use this to get the values:
store.selectDesktopSettings().experiments.expId

I won't need to add more stuff.
Once you know the action names for success, toggling and failure, please tell me so I can update this,.

I've refactored and wired up the doDesktopToggleExperiment toggle method over in #1048 so now I just need to test in context of the desktop app to see if it all works, also you shouldn't need any additional actions or api surface area 🤞
Let me know your thoughts when you get change.

@cwaring you're assuming doDesktopToggleExperiment fails if there's an error. It doesn't! It won't work like that.
I thought we had agreed on dispatching an event saying "Option X needs to be toggled" and then some bundle would toggle it and dispatch a success or fail event.
If you don't mind, I can make some final updates on #1048 to just use events.

Yes you're right, I considered both while making the updates and this seemed like.a simpler option to start with.
The base success/fail actions are in place so if you'd prefer to switch this to a dispatch now please feel free to make the updates. It wasn't 100% clear what pattern I should use to queue up additional actions from a reducer event so I'm keen to have your input here.


Add benchmarks

I'm opening this issue mainly as a reminder to myself to add a benchmark.l file sometime.

It should benchmark...

Startup time
The compiler
Runtime performance (speed, memory usage)

Possibly create Lumen versions of the benchmarks from The Computer Language Benchmarks Game
make benchmark should cause the benchmarks to run, just like make test causes the tests to run.

It was rude of me to clutter up someone else's repo with something like this.  Sorry.


[AIRFLOW-1820] Remove timestamp from metric name

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1820

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:
Remove the start time of the dag from the metric name

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2792 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #2792   +/-   ##
=======================================
  Coverage   73.41%   73.41%
=======================================
  Files         158      158
  Lines       11957    11957
=======================================
  Hits         8778     8778
  Misses       3179     3179

Impacted Files
Coverage Δ

airflow/models.py
87.3% <100%> (ø)
:arrow_up:

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 d8e8f90...9738f11. Read the comment docs.

I'm in favor of removing the timestamp from the metric, if no-one has any objections, I will merge this in the coming days.


improve concurrency safety of pubgrub prefetch

motivation: prevent potential deadlocks
changes:

dont wait on prefetch sync, notify instead.
use memoize on prefteches to avoid races / redundant prefetches
replace switch with tryMap to improve code readability
rename ContainerProvider::provider to ContainerProvider::underlying to improve code readability
add some code comments

@swift-ci please test

@swift-ci please smoke test

@swift-ci please smoke test

looks like the new integration tests from https://github.com/apple/swift-package-manager/pull/3088 are failing unrelated to this PR change (reproduced the same failure locally on main branch). cc @abertelrud @friedbunny

I think that the test failure is unrelated:
/Users/buildnode/jenkins/workspace/swift-package-manager-with-xcode-self-hosted-PR-osx/branch-main/swiftpm/IntegrationTests/Tests/IntegrationTests/XCBuildTests.swift:146: error: -[IntegrationTests.XCBuildTests testTestProducts] : XCTAssertEqual failed: ("terminated(code: 1)") is not equal to ("terminated(code: 0)")

@swift-ci please smoke test

Build failure looks a bit bogus:

/Users/buildnode/jenkins/workspace/swift-package-manager-PR-osx-smoke-test/branch-main/swift-driver/Sources/SwiftDriverExecution/llbuild.swift:21:29: error: compiled module was created by an older version of the compiler; rebuild 'llbuildSwift' and try again: /Users/buildnode/jenkins/workspace/swift-package-manager-PR-osx-smoke-test/branch-main/buildbot_incremental/llbuild-macosx-x86_64/products/llbuildSwift/llbuildSwift.swiftmodule

I think we should have just built the llbuildSwift module?

@swift-ci please smoke test OS X Platform

Build failure looks a bit bogus:

yea, seems unrelated

@swift-ci please smoke test OS X Platform


Circular reference when trying to learn how to authenticate to create tokens

Hi. I'm trying to learn how to use the token API and I've come across a circular reference in the docs.
At the top of the page, there is this line:
"Initial authentication to this API is the same as for all of the Azure Databricks API endpoints: you must first authenticate as described in Authentication."
It links to this page: https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/authentication#authentication
That page says: "To authenticate and access Databricks REST APIs, you use personal access tokens. " and then links back to the token API page. It is unclear how to generate the first token in order to get authenticated without first going through the portal.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e7b6274b-a306-0069-2bb2-188d73e2d1e7
Version Independent ID: 979b0589-3360-7aad-7007-bbc5f848d4b3
Content: Token API - Azure Databricks
Content Source: databricks/dev-tools/api/latest/tokens.md
Service: azure-databricks
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

@Connell1 Thanks for your comment! We will review and provide an update as appropriate.

@Connell1 Thanks for the feedback and bringing this to our attention. We have assigned the issue to the content author to investigate this and update the document as appropriate.

Hi @Connell1! Before you can use the Token API To generate new tokens, you must first create a personal token using the UI to authenticate to the API. After you've authenticated, you can use the API to generate new tokens without using the UI.

@Connell1
Note: You need to create Azure Databricks personal access token manually by going to the Azure Databricks portal.
Even for creating using APIs, initial authentication to this API is the same as for all of the Azure Databricks API endpoints: you must first authenticate as described in Authentication.
Hope this helps. Do let us know if you any further queries.

@Connell1 We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

Is there a way to generated the first access token automatically as part of devops provisioning?


Fix unused variable/function compilation warnings

This PR fixes a number of unused variable/function compilation warnings
that arise when using a config.h that does not define the macro
MBEDTLS_PEM_PARSE_C.

This PR:

Does not require additional tests.
Needs backporting to mbed TLS 2.1 and 1.3.
Fixes issue https://github.com/ARMmbed/mbedtls/issues/562.

Looks good to me.

Reviewed, tested, merged.


update default CI k8s ctx and tooling

add var for and set default agent k8s ctx
add agent entrypoint for terraform install
add kube config to shared DIR between agent and dind containers
update agent service account roles for terraform use

Test: Buildkite CI
Checklist:

[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

Captured in https://github.com/MinaProtocol/mina/pull/7457 targeting compatible

Captured in https://github.com/MinaProtocol/mina/pull/7457 targeting compatible


WIP: Implements "full color" 16 bit driver for ST7789 and adds ColorBitMap widget & demos

Hi
I was inspired from your work and for project that I am planning there is a need for showing "full color" images. How do you feel the direction that I have taken with ST7789_16bit.py driver and ColorBitMap widget. I copied the image_converter from https://github.com/russhughes/st7789py_mpy/blob/master/utils/image_converter.py including the bitmap() function to decode image to frame buffer.
This branch is not very well tested and I do not suggest you REALLY merge this as it is, but I would like to hear your comments.

I avoided writing a 16-bit diver for ST7789 because of the 115,200 byte buffer: this is excessive on most microcontroller platforms. My display drivers are primarily intended for use with the three GUI variants. These use limited sets of fixed colors, which means that the 4-bit drivers work well with 1/4 of the buffer size. Further, aside from nano-gui, the GUI itself uses significant amounts of RAM. These drivers are quite heavily optimised for RAM use, and to overcome the performance hit from using a 4-bit buffer.
You might be interested in my approach to image display. The approach is to use error diffusion ("dithering") to enable color image display on an 8-bit driver and monochrome image display on a 4-bit driver (16-bit drivers are also supported).
At the moment I think a 16-bit driver for a display of this size is too big, but my view may change as hardware platforms acquire more RAM. Currently I see operation on a Pyboard 1.1 or on Pico V1 as being a benchmark. As platforms with more RAM become the norm, I may move towards widgets that require full color and drivers that support it.
Re the changes to the 4-bit driver, I avoid using symbolic constants like
_ST7789_SWRESET = b"\x01"

because they waste RAM. I agree that there is a cost in readability, but anyone seriously studying a device driver will have the hardware datasheet in front of them, so the cost (IMO) is near zero.
Re your changes to the listbox, I am very keen to implement dynamically changeable content for both listbox and dropdown, and intend to start work on this now. There may be potential issues with list currency and with scrolling, but I will use your code as a starting point and credit you in the code comments.
As a general point, creating a huge PR with multiple unrelated changes makes them hard to review and unlikely to be merged. I would recommend that each PR should be focused on a single clear aim.

Hi, Thank you for you feedback for 16bit driver. I understand now better what boards you are targeting and why 16b driver is not usable for such targets. We are targeting ESP-32-S3-DevKitC-1 which has 512kb/8Mb of ram. and 32Mb.
Reading trough https://github.com/peterhinch/micropython-nano-gui/blob/master/IMAGE_DISPLAY.md and I need to inspect your approach more. I wish I would seen it earlier. I only saw the monochrome bitmap widget and that was not enough. Blit method seems really  much robust that my approach.
You are absolutely right about the _ST7789_ constants, it was way for me to read trough the code and understand what it does while looking trough the ST7789 manual.
And sorry for confusion about ListBox.set_elements. it was not what I wanted to present, just the driver and way to show the image. Sadly I did not create proper PR from that feature alone. I actually saw the .set_elements issue after I had finished my work on this current PR.
Thank you for you feedback, I gained valuable info how to continue with my implementation. I think we can close this PR.

There is no confusion about .set_elements: it's a valid approach to dynamically changing the listbox contents, and I think your code handles list currency and scrolling correctly (though I haven't yet tested it).
As I said above I am starting work on dynamic contents for listbox and dropdown. There are two main issues:

I need to figure out whether the set_elements API is the best approach - I have another possible contender.
If I do adopt set_elements I will seek to use its functionality in the constructor to save bytes.

As a general point on MP development, I recommend you watch this short video by Damien. One point he makes is about the RAM used by variable names.
Thanks for the contribution.

I have pushed an update which provides for variable element lists for Listbox and Dropdown. The API differs from yours in that it allows the passed element list to be edited in place rather than being replaced in its entirety. I have also taken the opportunity to change the code with the aim of reducing allocation.

Looking good :+1:  I’ll be hacking more with micro GUI as our project progresses. I watched Damien George's video, and, well, this isn't Python, so I need to unlearn some Python 'best practices.'"


Limit the Diskann cached nodes number

Signed-off-by: cqy123456<EMAIL_ADDRESS>
The number of caches does not exceed 1/3 of the total data size;
Remove the code for cache resizing in cache_bfs_levels().

\lgtm
\approve

/lgtm
/approve


fix: fix generator issues

Description

Fixes somes issues found with generated code during testing

Testing required outside of automated testing?

Install the package and run the modified code

[ ] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

Closing this as I branched out of the wrong branch :|


cannot find symbol import com.amplitude.reactnative.AmplitudeReactNativePackage [Android]

I'm getting the following error trying to run this on Android with react-native 0.64.0.
BUILD FAILED in 29s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
/Users/mohammed/code/rn-app/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:15: error: cannot find symbol
import com.amplitude.reactnative.AmplitudeReactNativePackage;
                                ^
  symbol:   class AmplitudeReactNativePackage
  location: package com.amplitude.reactnative
/Users/mohammed/code/rn-app/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:71: error: cannot find symbol
      new AmplitudeReactNativePackage(),
          ^
  symbol:   class AmplitudeReactNativePackage
  location: class PackageList
Note: /Users/mohammed/code/rn-app/android/app/src/debug/java/com/myapp/ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Any ideas?

It seems to be working now. Got this error after updating to RN 0.64.0. Solved it by removing .gradle directory.


Warning message "do not use for mining" inconsistent with current recommendations

The message "do not use for mining or merchant applications" in main.cpp and qt/bitcoinstrings.cpp is outdated. It contradicts the instructions in the OpenSSL Consensus thread:

... all mining pools MUST upgrade to Namecoin Core ...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 09/04/2015 03:16 PM, cassiniNMC wrote:

The message "do not use for mining or merchant applications" in
main.cpp and qt/bitcoinstrings.cpp is outdated. It contradicts the
instructions in the OpenSSL Consensus thread
https://forum.namecoin.info/viewtopic.php?f=2&t=2354:
... all mining pools MUST upgrade to Namecoin Core ...

I'm pretty sure that's because it's built from a Git commit rather
than a version tag.  Once we have version tags for official releases,
I believe that message will no longer be visible.

-Jeremy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJV6bavAAoJEAHN/EbZ1y06qUQQAKvQjgijftxhzB1vMx/qalq7
7oR0tClQvU/UhpC5IN+O96QoFVbBd5Vg14155ANe5B0Q0JFgFLLra0dNjSBYuhsk
gzkzeH6QHsyNM27w0Q8XaRrXYgjFUrdsQqkPtIHp+LQ4OeRbFvFIAFGZxo0lA0Fg
kV+XhdXq9NPGA2ztiTBpv+sLg1pJIUC+43lM5U6kik+8kqC2a6m1NQpDO5lFRd0T
mRuFqxHfBuyy5rnHPV6fzhNBTrU9/s5EfluqCPvl7u2CRX0TSi15Rs2VWJRXG1n/
gW2n6ts7Ad0VPXl/Zt7QZEG33mrDC0CpeNz75YuAPn+jMm/AhzK8B1zzZZZ/IhuU
3pvLMFUS22F7rWIkDLWMNakC4XMX4gWxQk7pCHYGj6U7V8TgJ3nOaosWKK8JFco2
Qjy/6F0AsyPzWxLcmUNyL4JeDfCQjicAtNdXl1y/SW09USwW+Tuz3XpNfEdmXHRe
kIoDJub4VnWyOVg/75l2pYnMwPkWw9OGqsbG0ddFUcEna0NN8Vz2V/ACM2HC4xwJ
nAjWyzZV1SQMomRRQ2Uq8iGgRSP71WcmRZAxtQu2NHxY8CShw7zCT7uRjY4ikNWR
MNkRaktMxB0B15BQjuttVQEKqrl4DR91/YVNzlIe+0F2qKDUlA8wji0kkZUbAM42
xTRoxVO1fDqTJjLMns2W
=bGFg
-----END PGP SIGNATURE-----

Yes, that's pretty much what's happening.  I've never dealed with versioning so far, but I believe that there's a flag next to the version number that indicates whether the build is supposed to be stable or experimental.
We should probably branch off a release, at least when we think we are ready to do one.  Apart from that, we could provide builds where just the flag is changed for the current semi-"emergency" situation if the warning confuses miners.

tbh with the Windows release in the hurry I could not find the flag to do it. The one I thought would do it in clientversion.h 'CLIENT_VERSION_IS_RELEASE' does not do the job, at least not on its own. If somebody figures out how to remove the warning let me know.

@phelixbtc
Hi. I figured out how to remove the warning.

Do configure as usual.
Open src\config\bitcoin-config.h
Search #define CLIENT_VERSION_IS_RELEASE
Change value to true

Save file.
6.Do make as usual.

This is partially true.  There are two places where the flag appears.  One is in src/clientversion.h, but I'm not sure under which circumstances this is used.  The one that makes the change for me is the one mentioned, although the file is autogenerated.  The change should be made in configure.ac instead.
Note that the 0.12 branch is already set to "release".

Closing this.  The release branches (0.16 currently) already set this "is release" flag to true, so the warning should not apply on them.  We need a proper and more structured release process, but this issue is not (really) about that.


Trailing Comma error in JS files and CallSignature

Bug Report

TSLint version:5.9.1
TypeScript version:2.8.1
Running TSLint via:  VSCode

TypeScript code being linted
lot of .ts and .tsx files and 3 pure JavaScript files
with `tslint.json` configuration:
{
	"defaultSeverity": "error",
	"extends": ["tslint:recommended", "tslint-react", "tslint-microsoft-contrib"],
	"jsRules": {},
	"linterOptions": {
		"exclude": ["**/*.js"]
	},
	"rules": {
		"linebreak-style": false,
		"missing-jsdoc": false,
		"typedef": false,
		"quotemark": [false, "double"],
		"indent": [true, "tabs"],
		"member-access": false,
		"jsx-curly-spacing": false,
		"completed-docs": false,
		"react-tsx-curly-spacing": false,
		"no-unsafe-any": false,
		"ordered-imports": false,
		"import-name": false,
		"no-default-export": false,
		"trailing-comma": false,
		"variable-name": false,
		"interface-name": false,
		"export-name": false,
		"strict-boolean-expressions": false,
		"no-relative-imports": false,
		"jsx-no-multiline-js": false,
		"member-ordering": false,
		"eofline": false,
		"jsx-no-lambda": false,
		"react-this-binding-issue": [true, { "allow-anonymous-listeners": true }],
		"match-default-export-name": false,
		"semicolon": false,
		"react-a11y-img-has-alt": false,
		"react-a11y-role-has-required-aria-props": false,
		"react-a11y-anchors": false,
		"react-anchor-blank-noopener": false,
		"no-any": false,
		"no-useless-files": false,
		"no-console": false,
		"no-non-null-assertion": false,
		"align": false,
		"prefer-for-of": false,
		"no-increment-decrement": false,
		"prefer-template": false,
		"restrict-plus-operands": false,
		"insecure-random": false,
		"promise-function-async": false,
		"no-floating-promises": false,
		"prefer-type-cast": false,
		"prefer-array-literal": false,
		"no-suspicious-comment": false,
		"no-unused-variable": true,
		"jsx-boolean-value": false,
		"max-func-body-length": false,
		"max-line-length": false,
		"no-use-before-declare": false,
		"no-single-line-block-comment": false,
		"no-void-expression": false,
		"react-a11y-event-has-role": false,
		"no-implicit-dependencies": false,
		"no-submodule-imports": false,
		"no-import-side-effect": false,
		"number-literal-format": false,
		"binary-expression-operand-order": false,
		"no-parameter-reassignment": false,
		"chai-vague-errors": false,
		"no-http-string": false,
		"no-require-imports": false,
		"function-name": false,
		"no-var-requires": false
	},
	"rulesDirectory": []
}

Note: in tsconfig.json I have already added:
....
"exclude": ["node_modules"]
Actual behavior
TypeError: Cannot read property 'end' of undefined
at cb (.....\node_modules\tslint\lib\rules\trailingCommaRule.js:163:133)
at visitNode (....\node_modules\typescript\lib\typescript.js:13990:24)
at Object.forEachChild (....\node_modules\typescript\lib\typescript.js:14109:21)
at cb (.....\node_modules\tslint\lib\rules\trailingCommaRule.js:170:23)
at visitNode (.....\node_modules\typescript\lib\typescript.js:13990:24)
at Object.forEachChild (....\node_modules\typescript\lib\typescript.js:14204:21)
at cb (....\node_modules\tslint\lib\rules\trailingCommaRule.js:170:23)
at visitNode (....\node_modules\typescript\lib\typescript.js:13990:24)
at Object.forEachChild (....\node_modules\typescript\lib\typescript.js:14251:24)
at cb (....\src\node_modules\tslint\lib\rules\trailingCommaRule.js:170:23)
Expected behavior
Running without error.
I have tried (I know it is not nice, was just experiment) to rewrite ...node_modules\tslint\lib\rules\trailingCommaRule.js at line 162. I have added the same if === undefined,  like you guys also did in case of ArrowFunction and it is working like charm.
Can it be that I was looking over something or it is an error in the Force?
Or probably the main problem that the JS files are not excluded.

@SophieLeeroy it sounds like you've found a solution (great!) but it's hard to verify the problem or write tests for it without a code snippet that can reproduce the crash. Any chance you can share the specific .ts/.tsx file it crashes on?
Since you're already playing around with the compiled TSLint js, if you add a console log for sourceFile.fileName on line 163 of trailingCommaRule.js it'll tell you which file(s) it's crashing on:
                case ts.SyntaxKind.CallSignature:
                    console.log("Oh my!", sourceFile.fileName);
                    _this.checkList(node.parameters, tsutils_1.getChildOfKind(node, ts.SyntaxKind.CloseParenToken, _this.sourceFile).end, "functions", isRestParameter);
                    break;

hi @JoshuaKGoldberg thanks for the help!
I did it and funnily (or not) it is my bundle.js...hmm... I still belive that my JS files create the error, since I have the project without them too and there it is working without issues.
I am using ChartJS library with React and TypeScript. I will try to extract ithe corresponding codeparts to an app that you can check it as well.
Oh my! ...front-end/public/js/bundle.js TypeError: Cannot read property 'length' of undefined     at TrailingCommaWalker.checkTypeLiteral (....\node_modules\tslint\lib\rules\trailingCommaRule.js:181:20)     at cb (...\node_modules\tslint\lib\rules\trailingCommaRule.js:171:27)


librewolf: 100.0-3 -> 100.0.1-1

Description of changes
Updates Librewolf to 100.0.1-1.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Basic browsing tests pass on NixOS x86_64.