Bad status code

Failed to introspect data source: 'xxx' because Bad status code
Failed to introspect data source: 'xxx' because Bad status code
Initial introspection complete. Got 2 data sources, 0 queryable
Can not get queryable datasources. why?

What is the status code reported?
Can you run with --verbose mode and attach offending query?

@vogievetsky
vvvvvvvvvvvvvvvvvvvvvvvvvv
Sending query 1:
{
"queryType": "segmentMetadata",
"dataSource": "xxx",
"merge": true,
"analysisTypes": [
"aggregators"
],
"lenientAggregatorMerge": true
}
^^^^^^^^^^^^^^^^^^^^^^^^^^
Will refresh data sources every 10000ms
Listening on 9090
vvvvvvvvvvvvvvvvvvvvvvvvvv
Got error in query 1: Bad status code (in 110ms)
^^^^^^^^^^^^^^^^^^^^^^^^^^
Failed to introspect data source: 'xxx' because Bad status code
vvvvvvvvvvvvvvvvvvvvvvvvvv
Sending query 2:
{
"queryType": "sourceList"
}
^^^^^^^^^^^^^^^^^^^^^^^^^^
vvvvvvvvvvvvvvvvvvvvvvvvvv
Got result from query 2: (in 39ms)
[
"xxx",
"xxx"
]
^^^^^^^^^^^^^^^^^^^^^^^^^^
Adding Druid data source: 'xxx'
vvvvvvvvvvvvvvvvvvvvvvvvvv
Sending query 3:
{
"queryType": "segmentMetadata",
"dataSource": "xxx",
"merge": true,
"analysisTypes": [
"aggregators"
],
"lenientAggregatorMerge": true
}
^^^^^^^^^^^^^^^^^^^^^^^^^^
vvvvvvvvvvvvvvvvvvvvvvvvvv
Sending query 4:
{
"queryType": "segmentMetadata",
"dataSource": "xxx",
"merge": true,
"analysisTypes": [
"aggregators"
],
"lenientAggregatorMerge": true
}
^^^^^^^^^^^^^^^^^^^^^^^^^^
vvvvvvvvvvvvvvvvvvvvvvvvvv
Got error in query 4: Bad status code (in 42ms)
^^^^^^^^^^^^^^^^^^^^^^^^^^
Failed to introspect data source: 'xxx' because Bad status code
vvvvvvvvvvvvvvvvvvvvvvvvvv
Got error in query 3: Bad status code (in 44ms)
^^^^^^^^^^^^^^^^^^^^^^^^^^
Failed to introspect data source: 'xxx' because Bad status code
Initial introspection complete. Got 2 data sources, 0 queryable


Custom LLDB formatters not loading from the ~/.lldbinit file

OS: MacOS Catalina 10.15.6
VSCode version:   1.49.1
Extension version: v1.5.3
Toolchain version:
Build target:
Python version:
In our project, we're using custom LLDB formatters. They are configured through ~/.lldbinit. When I run lldb in zsh, the formatters are properly registered. When I run VS Code with vscode-lldb, the formatters aren't registered, which is strange because https://github.com/vadimcn/vscode-lldb/issues/91 specifically has a note saying custom formatters can be registered using ~/.lldbinit.
I also tried creating a symlink <workspaceroot>/.lldbinit to ~/.lldbinit and it doesn't work, either (though when running lldb itself in zsh, it does see it, and warns me that it's ignored unless I configure some variable to allow this risky configuration). I would have expected this to work after seeing the response in https://github.com/vadimcn/vscode-lldb/issues/42.
Do I need to configure anything in my launch configuration to make vscode-lldb load the ~/.lldbinit file? Is there anything I can do to troubleshoot this issue, besides adding "lldb.verboseLogging":true in my workspace settings? I did that, and I see no reference to .lldbinit in the Output/LLDB console.

I have this problem too.
I have a command hello that just print "hello world". it works in zsh, but not in vscode.
this is the debug console output:
Executing script: initCommands
Executing commands in '/home/hunauta/.lldbinit'.
(lldb) command script import /home/hunauta/lldb/MyModule.py
Launching: /dev/shm/eigen3/build/Debug/MyProject
Launched process 33882
hello

this is my configuration:
{
            "type": "lldb",
            "request": "launch",
            "name": "lldb-launch",
            "program": "${command:cmake.launchTargetPath}",
            "args": [],
            "cwd": "${workspaceFolder}",
            "initCommands": [
                "command source /home/hunauta/.lldbinit"
            ]
}

@mbargiel: Yes, codelldb will not import ~/.lldbinit by default.   If you'd like, you can achieve that, by adding to VSCode configuration:  "lldb.launch.initCommands": ["command source ${env:HOME}/.lldbinit"]

@Rupemgera: That should work, and it does for me.   Print output should appear in VSCode's Debug Console window.

@vadimcn Thanks for the response!
Could this be made into a feature request, then? I would find it a fairly reasonable application of the Principle of Least Surprise to expect codelldb to behave the same as other mainstream lldb integrations (Apple's Xcode, JetBrains's CLion), not to mention running lldb itself. As it is, it just feels like a feature of lldb itself is disabled/broken by this extension.
As for https://github.com/vadimcn/vscode-lldb/issues/42, can you confirm that what you said in that post,

In 0.5.2 the debugger will be started in ${workspaceRoot} directory. Just having .lldbinit should work now.

is no longer true? As I mentioned in my original post, I created a ${workspaceRoot}/.lldbinit symlink pointing to my real ${HOME}/.lldbinit, and it wasn't picked up either. If so, that's too bad, because I could have made it a Git hook/zsh alias to create that symlink. I would rather not alter the project's launch.json config because I share it with a couple hundred other people. (Sure, I can also programmatically alter the file and do git update-index --assume-unchanged .vscode/launch.json but that feels a lot more trouble, especially because we have a bunch of lldb launch configs...)

My current thinking is this: dotfiles are fine for CLI tools, but since Codelldb is a VSCode extension, it it appropriate for it use the standard VSCode configuration storage mechanisms.
And you can always get the behavior you want - by adding a single line into VSCode's user-level configuration file (not in launch.json - that's for individual launch configurations).

That makes sense. And I certainly didn’t think to register this config as a user config rather than a project/launch config. Thanks! I’ll try that.

@vadimcn I added the config to my user settings and it works! Thanks for the suggestion!

I also found this rather surprising - could it be added to the Troubleshooting/User Manual wiki?


How do I correctly publish the dist folder to npm?

Type of Issue
[X] Bug Report
[ ] Feature Request

Description
This probably isn't the best place to ask for support, but I can't figure out how to correctly publish the dist folder to the package repository.
I have a newly converted library (https://github.com/code-orange/telemachy).
yarn build works fine, I get the binaries in the dist folder, and they seem to work just fine.
However, when I run yarn publish dist or npm publish dist, the source files are uploaded to the package repository instead of the contents of the dist folder (although that has a correct package format).
How To Reproduce

yarn build/npm build
yarn publish dist/npm publish dist
Download tarball for package (wget `npm view telemachy dist.tarball` )

Expected Behaviour
The tarball contains the contents of the dist folder that was just built.
Instead, the tarball contains the source code (without generated files).
Version Information
$ node_modules/.bin/ng-packagr --version
ng-packagr:            2.0.0-rc.12
@angular/compiler:     5.2.4
@angular/compiler-cli: 5.2.4
rollup:                0.53.4
tsickle:               0.26.0
typescript:            2.6.2
node: v6.10.3
yarn: 1.3.2

I may have jumped the gun on this issue...
While the contents of npm view telemachy dist.tarball are most definitely not the contents of the dist folder, actually installing the library seems to correctly pull in the dist files.
It seems that the tarball is different from the files that are actually being installed.

Yep, everything is actually working fine. Feel free to close this issue.


Nvidia GeForce Experience v<IP_ADDRESS>

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install -m <manifest>?

Can't test Nvidia GeForce Experience in a VM 🙃
Microsoft Reviewers: Open in CodeFlow

Found Nvidia GeForce Experience [Nvidia.GeForceExperience]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://us.download.nvidia.com/GFE/GFEClient/<IP_ADDRESS>/GeForce_Experience_v<IP_ADDRESS>.exe
██████████████████████████████   119 MB /  119 MB
Successfully verified installer hash
Installing ...
Installer failed with exit code:<PHONE_NUMBER>

@OfficialEsco I couldn't find anything on that exit code. It may just be that I don't have nvidia hardware on this machine.

@denelon Yes it is, which is why i said you can't test it in a VM


ValueError

Hi,
I'm trying to run Self Canonicalization with the provided code in a cloud computing platform (4 x A100),
but getting this error continuously.
Loading checkpoint shards:   0% 0/2 [00:00<?, ?it/s]
Traceback (most recent call last):
File "/content/drive/MyDrive/edc/run.py", line 106, in
edc = EDC(**args)
File "/content/drive/MyDrive/edc/edc/edc_framework.py", line 94, in init
schema_canonicalization_embedding_model = MistralForSequenceEmbedding.from_pretrained(
File "/usr/local/lib/python3.9/dist-packages/transformers/modeling_utils.py", line 3531, in from_pretrained
) = cls._load_pretrained_model(
File "/usr/local/lib/python3.9/dist-packages/transformers/modeling_utils.py", line 3958, in _load_pretrained_model
new_error_msgs, offload_index, state_dict_index = _load_state_dict_into_meta_model(
File "/usr/local/lib/python3.9/dist-packages/transformers/modeling_utils.py", line 794, in _load_state_dict_into_meta_model
raise ValueError(f"{param_name} doesn't have any device set.")
ValueError: embed_tokens.weight doesn't have any device set.
Do you have any idea why this is happening?

try setting all device_map="auto" to device_map="cpu" in edc_framework.py.

It solved the issue, thank you!


sdio: add sdh peripherals and modify sdh_demo

Also fix some code issues.
Tested on M1s Dock, is works fine.

I have completed the adjustment in latest commit. @luojia65


Finish up most of the Sockets PAL and fix a few bugs.

The only remaining feature work that I am aware of for the PAL is the implementation of receive-after-accept and send-after-connect semantics on *nix.

@cipop @stephentoub PTAL

LGTM

:+1:


Use model alias for the CTE identifier generated during ephemeral materialization

Resolves #5273. Reimplementation of https://github.com/dbt-labs/dbt-core/pull/5488 to match the new split between adapter and core repos.
See https://github.com/dbt-labs/dbt-adapters/pull/236 for the corresponding adapter PR.
Problem
Ephemeral model materializations do not currently support using special characters like dots in file names, even if these special characters are sanitized using model aliases.
Solution
Prioritize using the model alias, if specified, when creating a node identifier for ephemeral models, and sanitize the identifier to make sure no illegal characters are used when creating CTEs that would cause a runtime error.
This change requires a corresponding change to dbt-adapters to fully fix the bug, which is implemented in this PR: https://github.com/dbt-labs/dbt-adapters/pull/236
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
[x] This PR includes type annotations for new and modified functions

A note on the CLA
cla-bot seems to think I haven't signed the CLA, even though I just did so. Perhaps I didn't format my GitHub username correctly? In any case, let me know if I need to sign it again.

@MichelleArk @QMalcolm @gshank Sorry for the wide tag radius, I'm not sure who is best equipped to help here! This should be ready for review, but cla-bot seems convinced that I haven't signed the CLA even though I have. (I may have done so incorrectly, but I'm not sure how to confirm 😅 ) Any idea how I can move forward here?

Howdy @jeancochrane!
Sorry for the noise from the CLA bot 🙃 I've looked at our CLA database and the issue that we filter out any submitted usernames that begin with @. Unfortunately, I don't have edit access to the underlying database, just view access. Could you submit your CLA again but without the @ prefix on your username?

Done, thanks for the tip @QMalcolm!

Thank you for summoning the bot @QMalcolm! If you could also summon it on https://github.com/dbt-labs/dbt-adapters/pull/236 I would be very grateful 🙏🏻

@jeancochrane with the latest version of https://github.com/dbt-labs/dbt-adapters/pull/236, do we need this PR in dbt-core anymore?

@jeancochrane with the latest version of https://github.com/dbt-labs/dbt-adapters/pull/236, do we need this PR in dbt-core anymore?

Unfortunately I believe it's still needed in order to fix unit testing in our case @dbeatty10! While https://github.com/dbt-labs/dbt-adapters/pull/236 successfully gets ephemeral materializations working for projects that use aliases to strip out special characters, unit tests appear to use Compiler._recursively_prepend_ctes() to construct the CTE identifiers that represent input data, and _recursively_prepend_ctes() uses model.name when constructing these CTE identifiers:
https://github.com/dbt-labs/dbt-core/blob/4c7d922a6da0d4c63980115f0fc46296b80e191d/core/dbt/compilation.py#L374
In practice, this means that with the current main branch of dbt-core installed alongside https://github.com/dbt-labs/dbt-adapters/pull/236, a unit test query can end up looking something like this (adapted from an example in our project that uses dots to namespace model filenames) -- note how the definition of the CTE at the top does not use the alias final_model_raw, while the reference at the bottom does:
with __dbt__cte__model.final_model_raw as (
    -- Fixture for model.final_model_raw
    select try_cast(null as varchar) as year, ...
)
select
    ...
from __dbt__cte__final_model_raw AS fmr

So I think that the current PR title "Use model alias for the CTE identifier generated during ephemeral materialization" is actually misleading; this particular PR is in fact fixing the CTE identifier generated during unit testing, not during ephemeral materialization. I'll go ahead and change that!
Taking a step back, however, it strikes me as a potential code smell that the CTE identifier is generated one way during definition (with {identifier} as (...)) and another way during reference (... from {identifier} as fmr). Perhaps that's an intentional design decision, or perhaps it's a sign that a better fix than this one would be to consolidate the code that generates CTE identifiers into one place. I leave that decision up to you, however, since I don't have as much insight into this code as you do! Just let me know what direction you think is appropriate to go and I'd be happy to take a stab at it.

Actually @dbeatty10, my previous comment was incorrect -- the discrepancy between the CTE identifier used during definition vs. reference that I described above does in fact affect ephemeral materialization as well, not just unit tests. I should have tested more thoroughly prior to commenting! I've reverted the title of this PR and will edit my previous comment to reflect this mistake.

Closing and re-opening to try to restart CI tests.

the discrepancy between the CTE identifier used during definition vs. reference that I described above does in fact affect ephemeral materialization as well

Okay, makes sense @jeancochrane !
Could you do a couple things?

Update from alias to identifier as-needed to pass CI
Instead of modifying an existing test in tests/functional/schema/fixtures/sql.py and tests/functional/schema/test_custom_schema.py, could you add a new one?

Sounds great, thanks so much @ChenyuLInx! Let me know if you'd like a hand with any of that, otherwise I'll hang tight.

@dbeatty10 @ChenyuLInx Seems like these changes didn't get added to the changelog for v1.8.6, any idea why not? I'm assuming I just didn't format the changelog metadata correctly, I'll try to do that right next time!

Makes sense, thanks for all your help getting this over the line @dbeatty10!


Locating site package dir fails on Windows 11

Config script mistakenly assumes user site package directory instead of global one!
In this case:

packageDir = C:\Users\JKN010
sitePackageDirGlobal = C:\Python312\Lib\site-packages
sitePackageDirUser = C:\Users\JKN010\AppData\Roaming\Python\Python312\site-packages

Which is used here:
        if packageDir.lower() in sitePackageDirGlobal.lower():
            sitePackageDir = sitePackageDirGlobal
        elif packageDir.lower() in sitePackageDirUser.lower():
            sitePackageDir = sitePackageDirUser

The first test fails, and the second one succeeds, so the config script assumes the user dir is the correct one. BUT in reality this directory does not exist, whereas Iromlab got installed in the global dir! (Iromlab was installed by running pip in command prompt windows that was launched as local admin).
Results are same if config script is run as local admin.

This happened because I accidentally cloned the source repo to the exact same location the script used to write its config!


Feature flag Coproduct impl

Currently Freestyle can support both cats Coproduct and iota CopK. We should default to the most performant impl which is currently iota but let users choose which one they use via feature flag.

It's also possible to generate both at the same time-- this would be useful for libraries containing free algebras.

I've opened an issue in Iota to support converting to cats coproducts.


Publish docker image for arm architectures

I'm trying to run your image on my Raspberry Pi 5 which uses a 64-bit arm architecture. When I attempt to pull the image it fails with no matching manifest for linux/arm64/v8 in the manifest list entries.
Is this something I can work around or does it require an arm image to be published?
will@raspberrypi:~/actual-budget $ docker pull jhonderson/actual-http-api:v0.9.2
v0.9.2: Pulling from jhonderson/actual-http-api
no matching manifest for linux/arm64/v8 in the manifest list entries

When I inspect the manifest this is what I get:
will@raspberrypi:~/actual-budget $ docker manifest inspect jhonderson/actual-http-api:v0.9.2
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.index.v1+json",
   "manifests": [
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 2003,
         "digest": "sha256:a0cff9639aaff0dc20bdf912f144754b187606bac42011b0fb3196c1393d2c65",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 566,
         "digest": "sha256:2920048d9119f638c7b7a0c8f0c8c95777befbaf465af03766955ddf7eaa3214",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         }
      }
   ]
}

Hello @willem-h , thanks for reporting this. I just added support for arm64, you should be able to install it in raspberry pi using the tags v0.10.0 or latest.
Feel free to close if it works.
Cheers

Yep, that worked. Thanks for such a quick turn-around.


Add Manifest.toml and CompatHelper

Currently, only the Project.toml files are checked in, it seems. This helps to avoid conflicts between dependencies of different tutorials but it does not ensure reproducibility. It would be easier to rerun and debug the examples if the Manifest.toml would be checked in as well.
Additionally, one could then use CompatHelper to be informed about updated packages (it would be cool if the tutorials would be rebuilt automatically but it is even helpful if this has to be done manually, I think).

it would be cool if the tutorials would be rebuilt automatically but it is even helpful if this has to be done manually, I think

@cpfiffer Is there a particular reason that the docs are not built with CI? It frightens me a bit when I look at a tutorial and see "Julia Version 1.5.3", which means it's likely built months ago.

It would be easier to rerun and debug the examples if the Manifest.toml would be checked in as well.

In my experience with my blog (https://github.com/rikhuijzer/huijzer.xyz) and TuringModels.jl (https://github.com/StatisticalRethinkingJulia/TuringModels.jl), just the Project.toml with compat entries should be enough if you rerun everything about every week. I've never gotten into major issues because package maintainers stick to semantic versioning quite well.

It's a bit wasteful to rerun everything every week, and it's also not guaranteed that package updates (even according to Semver) don't break tutorials (e.g. additional exports in some package might cause ambiguity errors). IMO both Manifest and Project files should be added to make it reproducible, and we should use the same CI setup as SciMLTutorials and SciMLBenchmarks (https://github.com/TuringLang/TuringTutorials/pull/118#issuecomment-839730947).

It's a bit wasteful to rerun everything every week, and it's also not guaranteed that package updates (even according to Semver) don't break tutorials.

With that logic, we could also stop using CI. I would argue that the time wasted by people on manually running tutorials and messing around with broken tutorials is more wasteful. But, do these tutorials take hours to run? Maybe that's what I'm missing here.
With "every week" I meant "reasonably regularly".  My point is that, in my experience, package updates do not often break runs. And if they do, it might actually be good to detect it soon and fix it instead of trying to find the culprit months later. For example, my blog has been running with Query, AlgebraOfGraphics (used to be Gadfly), MLJ, MLDataUtils, Turing and more for quite a while. I've never encountered much issues with it. And arguably, if a tutorial is expected to be so fragile, shouldn't it be a good idea to make them more robust?

Let me put it differently: let me know if a PR on CI for the TuringTutorials would be appreciated. That's why I was asking in the first place.

There's no reason for rerunning tutorials if the package versions are fixed with a Manifest file which IMO we should do since otherwise the setup is not reproducible. CompatHelper will bump package versions and rerun the tutorials if new breaking versions are available. Additionally, one could also update Manifest files at irregular times automatically if desired but it seems less important.

Let me put it differently: let me know if a PR on CI for the TuringTutorials would be appreciated. That's why I was asking in the first place.

I would appreciate it. Is there a way to attach it to an update in the Manifest?

I would appreciate it. Is there a way to attach it to an update in the Manifest?

Okay. I'll start to work on it and add a Manifest.toml.

@rikhuijzer Check out what we did in KernelFunctions.jl to parallelize the creation of the examples (it's with Literate.jl but I suppose it's easily adaptable to Weave.jl) : https://github.com/JuliaGaussianProcesses/KernelFunctions.jl/blob/master/docs/make.jl


🎨 Prefixing Device Functions

It might be useful to allow for custom prefixes in the device implementation. First, this enables the device provider to prefix the function with their prefix of desire, e.g., ABC_QDMI_query... for the company ABC. Secondly, this also facilitates more flexible implementations of the driver. With different prefixes, the device libraries can also be linked statically and do not have to be loaded dynamically by the driver.
Overall, most changes should involve the driver. However, also the device implementations need to include the header in a way that supports those prefixes.

Would the device vendor need an ABC_QDMI_query... because it will have a different function signature than QDMI_query...? If so, it would be better to change the signature of QDMI_query... or introduce a new QDMI_query_xyz....

Would the device vendor need an ABC_QDMI_query... because it will have a different function signature than QDMI_query...? If so, it would be better to change the signature of QDMI_query... or introduce a new QDMI_query_xyz....

See https://github.com/Munich-Quantum-Software-Stack/QDMI/pull/86 for a proof-of-concept realization (still in flux/draft) ;-)

In the following, I add some lessons learned while experimenting with different options in #86.
Lessons Learned
Include header "shifted"
It is possible to substitute symbols in a header by previously defining substitution rules, such as
#define <old symbol> <new symbol>

In that way, a generic "substitution" header can be defined, see device_shifted.h.in that contains a placeholder for the prefix that can be replaced by CMake's configure_file(...). When this header is included in a device, the symbols are all name-shifted by the specified prefix.
Problem
The problem with that solution is, that the device_shifted.h.in header transitively includes qdmi/device.h with the substitutions applied. When all devices are linked statically together into one driver, the issue arises that the substitution rules for the first device that is compiled are applied since the header qdmi/device.h will only be included once due to the preprocessor directive #pragma once.
Use of objcopy
Another solution to rename the symbols in the compiled device libraries to rename the symbols after compilation in the object files using objcopy on Linux, and ld with the option -alias_list in Mac OS, see
https://github.com/Munich-Quantum-Software-Stack/QDMI/blob/9b475de8fc5fe3dc13c57091cf10fcee22191a40/examples/device/unprefixed_c/CMakeLists.txt#L19
https://github.com/Munich-Quantum-Software-Stack/QDMI/blob/9b475de8fc5fe3dc13c57091cf10fcee22191a40/examples/device/unprefixed_c/CMakeLists.txt#L28
With this approach, no source code, neither in the header nor in the source code, must be touched for the device implementations. To this end, when statically linking all devices together into one library, the header that must be included is always the same and it suffices that this is included only once aligning with #pragma once.
Problem
While the function symbols can be renamed with objcopy or ld, respectively, that is not possible for types defined by the devices. Since every device must define their type for the Job, Site, and Operation this leads to multiple definitions for QDMI_Job, QDMI_Site. and QDMI_Operation. This issue cannot be resolved using objcopyor ld. The only way would be to define the previously mentioned types as void*. However, this could lead to type unsafe implementations.
Use Wrapper around device types
One way to avoid having the void* mentioned in the previous section could be to define a struct in the driver behind the QDMI_Job that contains a void pointer to the QDMI_Job of the respective device together with a pointer to the actual device. It would be the job of the driver then to cast the object behind the void pointer to the correct data-type for the respective device. This way, the driver would need to deal with more complexity but the client and driver could still safely use types for jobs, sites, and operations.
Problem
As pointed out in #83 , this approach causes problems in information returned from the device. For example, when querying the coupling map, the device needs to refer to the sites. The device has only access to its representation of a site and will return those to refer to certain sites. The client receiving this information (unfiltered—as the driver does (and should) not know what information is passed there) sees the objects of the site's type defined by the device. However, the client only knows the site's representation returned from the driver, which is the wrapper around the device's sites.
Potential Solution
As pointed out in the previous section, it is unavoidable for devices to have their own implementation of the jobs, sites, and operations, to define them under different names–and this must happen already on the source code level and cannot be achieved by applying objcopy afterward. To facilitate the different naming of the types (and function symbols), the qdmi header must be modified (prepending the prefix) before they are included in a device's implementation. To circumvent the problem described in the first section, the header files must be copied to follow the constraint that one header is only included once. Having this copy also allows the modification of this copy in place, which makes the substitution rules, as described in the first section, superfluous.
The devices can include their modified header that defines all types and symbols implemented in the device prepended with a custom prefix. The device must then use the prefix for every function and type. By this, also the (static) driver knows the signature (including the types of parameters) from the device's functions and can cast the arguments accordingly.
For an implementation of that check out #86 .


[Test] Add missing flow-based test for bip39 passphrase entry

Description
Adds a missing flow-based test for the process of entering an optional bip39 passphrase, reviewing the resulting fingerprint, editing the passphrase, once again reviewing the results, and then finalizing the seed.
This pull request is categorized as a:

[x] Test case

Checklist

[x] I’ve run pytest and made sure all unit tests pass before sumbitting the PR

If you modified or added functionality/workflow, did you add new unit tests?

[x] N/A

I have tested this PR on the following platforms/os:

[x] Other

LGTM


Request aborted on image upload over 1MB

Node version: v15.11.0
Sails version (sails): 1.4.0
ORM hook version (sails-hook-orm): 3.0.1
Sockets hook version (sails-hook-sockets): 2.0.0
Organics hook version (sails-hook-organics): none
Grunt hook version (sails-hook-grunt): 4.0.1
Uploads hook version (sails-hook-uploads): none
DB adapter & version (e.g. sails-mysql@5.55.5): 1.0.1
Skipper adapter & version (e.g. skipper-s3@5.55.5<EMAIL_ADDRESS><EMAIL_ADDRESS>
I have this form on my frontend:

		<form class="form" action="/newsCreate" enctype="multipart/form-data" method="POST">

Create News

		  <button type="button" class="close" data-dismiss="modal">
			×
		  </button>

					Title
				  	<input type="text" name="newsTitle" id="newsTitle" class="form-control" placeholder="Insert news title" aria-describedby="News title" />

				<input type="hidden" name="_csrf" value="<%= _csrf %>" />

					<textarea id="editor1" name="newsBody" rows="10" cols="80">
						This is my textarea to be replaced with CKEditor.
					</textarea>

					News External URL (optional)

						<input type="url" class="form-control" pattern="https://.*" name="newsExternalUrl" />

					News Image

						<input type="file" class="form-control" name="newsImage" multiple="multiple" />

		  <button type="button" class="btn btn-secondary" data-dismiss="modal">Close</button>
		  <button type="submit" class="btn btn-primary float-right">Create News</button>

		</form>

And I have this on my backend:
        let newsTitle = req.param('newsTitle'), newsBody = req.param('newsBody'), newsExternalLink = null;

        if (req.param('newsExternalUrl') && req.param('newsExternalUrl') !== '') newsExternalLink = req.param('newsExternalUrl')
        if (newsTitle.length < 3 || newsBody.length < 3) return res.send('Fields are empty [NEWS]');

        d.run(() => {
            req.file('newsImage').upload({

                maxBytes: 150000000,
                dirname: require('path').resolve(sails.config.appPath, 'assets/newsImages')
            }, async function whenDone(err, uploadedFiles) {
                if (err) { return console.log(err) }

                let index = uploadedFiles[0].fd.lastIndexOf('/');
                let imageName = uploadedFiles[0].fd.substring(index+1 , uploadedFiles[0].fd.length);

                try {
                    let createdNews = await Ucpnews.create({
                        newsTitle: newsTitle,
                        newsBody: newsBody,
                        authorId: req.user.id,
                        newsExternalLink: newsExternalLink
                    }).fetch();

                    await Ucpnews.update({id: createdNews.id}).set({
                        newsImg: imageName
                    });

                } catch(e) {
                    console.log(e);
                }
            });
        });
        return res.redirect('/');
    },

My problem is that whenever I upload a file bigger than 1MB, I get the error request aborted.
/**
 * HTTP Server Settings
 * (sails.config.http)
 *
 * Configuration for the underlying HTTP server in Sails.
 * (for additional recommended settings, see `config/env/production.js`)
 *
 * For more information on configuration, check out:
 * https://sailsjs.com/config/http
 */

module.exports.http = {

  /****************************************************************************
  *                                                                           *
  * Sails/Express middleware to run for every HTTP request.                   *
  * (Only applies to HTTP requests -- not virtual WebSocket requests.)        *
  *                                                                           *
  * https://sailsjs.com/documentation/concepts/middleware                     *
  *                                                                           *
  ****************************************************************************/

  middleware: {

    /***************************************************************************
    *                                                                          *
    * The order in which middleware should be run for HTTP requests.           *
    * (This Sails app's routes are handled by the "router" middleware below.)  *
    *                                                                          *
    ***************************************************************************/
  passportInit: require('passport').initialize(),
  passportSession: require('passport').session(),

  order: [
    'cookieParser',
    'session',
    'passportInit',
    'passportSession',
    'compress',
    'bodyParser',
    'poweredBy',
    'router',
    'www',
    'favicon',
  ],

  //bodyParser: require('skipper'),

    /***************************************************************************
    *                                                                          *
    * The body parser that will handle incoming multipart HTTP requests.       *
    *                                                                          *
    * https://sailsjs.com/config/http#?customizing-the-body-parser             *
    *                                                                          *
    ***************************************************************************/

    bodyParser: (function _configureBodyParser(){
      var skipper = require('skipper');
      var middlewareFn = skipper({
        strict: true,
        maxWaitTimeBeforePassingControlToApp: 5000,
        maxTimeToBuffer: 10000
      });
      return middlewareFn;
    })(),

  },

};

This is my http config file.

I've been struggling for days, I've searched a lot on internet and I've read a lot of posts, nothing helps with my issue and I have no idea why it is happening.

@andreiwow2 I'll try to reproduce this issue

@andreiwow2 I'll try to reproduce this issue

I am sorry, I forgot about this issue.
the problem was because I had the return outside the upload function which refreshed the browser page before the file uploaded which ended with an abort.


Compute pitch compensated acceleration

part of PR stack.
But I don't know how to submit a PR to commaai/openpilot that's comparing two branches in the opgm repo, so the layers of the PR stack will include the commits from the previous.

route: c11fcb510a549332|2022-08-17--18-58-31

Verification: from posted route


obs-packaging: Skip packaging qemu-lite for non-amd64 arch

qemu-lite is required to be packaged only
for amd64 arch. Skip it for all other
architectures.
Fixes: #152
Signed-off-by: Nitesh Konkar<EMAIL_ADDRESS>

lgtm
snap failed restarting ...

lgtm


Create xz debs

using tar instead of zst fixing compatibility issue.
Sample  https://www.reddit.com/r/jailbreak/comments/vqnazh/free_release_permasigner_generate_a_permasigned/iesbm00/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

Thanks for the pr! Didn’t think this would be an issue


perf(cargo-package): match certain path prefix with pathspec

What does this PR try to resolve?
Improve #14955
check_repo_state checks the entire git repo status.
This is usually fine if you have only a few packages in a workspace.
For huge monorepos, it may hit performance issues.
For example, on awslabs/aws-sdk-rust@2cbd34db53389aed1cafe4c56d23186ef5ff304a the workspace has roughly 434 members to publish. git ls-files reported us 204379 files in this Git repository. That means git may need to check status of all files 434 times.
That would be 204379 * 434 = 88,700,486 checks!
Moreover, the current algorithm is finding the intersection of PathSource::list_files and git status. It is an O(n^2) check. Let's assume files are evenly distributed into each package, so roughly 470 files per package. If we're unlucky to have some dirty files, say 100 files. We will have to do 470 * 100 = 47,000 times of path comparisons.
Even worse, because we git status everything in the repo, we'll have to it for all members,
even when those dirty files are not part of the current package in question.
So it becomes 470 * 100 * 434 = 20,398,000!
Solution
Instead of comparing with the status of the entire repository,
this patch use the magic pathspec1 to tell git only reports
paths that match a certain path prefix.
This wouldn't help the O(n^2) algorithm,
but at least it won't check dirty files outside the current package.
How should we test and review this PR?
Run this command against awslabs/aws-sdk-rust@2cbd34db53389aed1cafe4c56d23186ef5ff304a,
and see if it is getting better.
CARGO_LOG_PROFILE=1 cargor package --no-verify --offline --allow-dirty -p aws-sdk-accessanalyzer -p aws-sdk-apigateway

Additional information
There are some other alternatives, like making PathSource::list_files additionally reports dirty files. I don't want to touch that part right now because it is already overly complicated.
Some other approaches like

switching to gitoxide
a flag --no-vcs to skip vcs at all
improve the O(n^2) algorithm.

This approach should be the most straighforward one.

From https://github.com/rust-lang/cargo/issues/14955#issuecomment-2555139730

Here are profiling data: trace.tar.gz
On 59b2ddd4484 (trace-offline.json)

#14962 (trace-offline-pathspec.json)


switch CGPM tests to use real satellite data set

The nonsense data generator I wrote was expedient but silly.

I disagree with this issue. The real satellite data set is a beast suitable for "battle conditions" or some large integration test for missing data, werid strings/unicode characters, large categoricals and so on.
The stubbed data generator you wrote was perfect for me as a test case and I think it should stay because it is easy to debug.

OK.


Allow setting crossRegionAccessEnabled

Copying objects from between multiple buckets that are in different regions currently fail with this error:
Caused by: software.amazon.awssdk.services.s3.model.S3Exception: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. (Service: S3, Status Code: 301, Request ID: Y72AK58DSRMM1HN9, Extended Request ID: MISChGBdhF5aNEP+wyhG4FWtUzgnxt4bKvj3uWqLS7pG+t931kUWZWqNVgW3iYFWTiHwWnp18QTFcZXDUdfpLA==)
	at software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:156)
	at software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleResponse(AwsXmlPredicatedResponseHandler.java:108)
	at software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handle(AwsXmlPredicatedResponseHandler.java:85)
	at software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handle(AwsXmlPredicatedResponseHandler.java:43)
	at software.amazon.awssdk.core.internal.handler.BaseClientHandler.lambda$successTransformationResponseHandler$7(BaseClientHandler.java:270)
	at software.amazon.awssdk.core.internal.http.async.AsyncResponseHandler.lambda$prepare$0(AsyncResponseHandler.java:89)
	at java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:966)
	at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:940)
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
	at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
	at software.amazon.awssdk.core.internal.http.async.AsyncResponseHandler$BaosSubscriber.onComplete(AsyncResponseHandler.java:132)
	at software.amazon.awssdk.utils.async.SimplePublisher.doProcessQueue(SimplePublisher.java:275)
	at software.amazon.awssdk.utils.async.SimplePublisher.processEventQueue(SimplePublisher.java:224)
	at software.amazon.awssdk.utils.async.SimplePublisher.complete(SimplePublisher.java:157)
	at java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:719)
	at java.util.concurrent.CompletableFuture.uniRunStage(CompletableFuture.java:731)
	at java.util.concurrent.CompletableFuture.thenRun(CompletableFuture.java:2023)
	at software.amazon.awssdk.services.s3.internal.crt.S3CrtResponseHandlerAdapter.onErrorResponseComplete(S3CrtResponseHandlerAdapter.java:143)
	at software.amazon.awssdk.services.s3.internal.crt.S3CrtResponseHandlerAdapter.handleError(S3CrtResponseHandlerAdapter.java:132)
	at software.amazon.awssdk.services.s3.internal.crt.S3CrtResponseHandlerAdapter.onFinished(S3CrtResponseHandlerAdapter.java:101)
	at software.amazon.awssdk.crt.s3.S3MetaRequestResponseHandlerNativeAdapter.onFinished(S3MetaRequestResponseHandlerNativeAdapter.java:24)

Enabling crossRegionAccessEnabled fixes this. It would be great to set this i.e. through env when creating the filesystem.

One way to get around this is to set the default client builder:
fs.clientProvider()
  .asyncClientBuilder(
    S3AsyncClient.crtBuilder.crossRegionAccessEnabled(true)
  )

I would prefer not to do this by default because of this warning in the SDK.

Enabling this mode has several drawbacks, as it can increase latency if the bucket's location is physically far from the location of the request.Therefore, it is strongly advised, whenever possible, to know the location of your buckets and create a region-specific client to access them

Cross region data transfer can also incur additional costs which is something that a user should probably opt in for.
However, we should certainly allow this and being able to set this through the env seems like a great way to do this.
Would you be open to adding a PR for this?

I just remembered about these issues that I filed. I'll take a stab at this one.

Thinking on this some more, perhaps cross region access should be enabled by default. It is for the aws s3 commands from the CLI and it can be difficult to know that a bucket is in a different region so for maximum ease of use I think we should do this.

Fixed by #318


Fixes compilation with libphonenumber 8.5.0

This adds two new atoms to represent output from ValidationResult.
I'm using Archlinux, during the latest update to libphonenumber 8.5.0 compilation of elibphonenumber broke.

sorry. i didn't mean to open it yet, as tests are failing!

@nirev looking forward to this PR when it comes through!


Some issues with attributes on custom models

System Info

Who can help?
No response
Information

[ ] The official example scripts
[ ] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder
[ ] My own task or dataset (give details below)

Reproduction
As reported by @kashif , it should be possible to use methods like LoRA on custom models that, for instance, wrap the actual model. Here is a reproducer:
import torch
from transformers import AutoModelForCausalLM
from torch import nn
from peft import LoraConfig, get_peft_model

model_id = "facebook/opt-125m"

class MyModel(nn.Module):
    def __init__(self):
        super().__init__()
        self.llm = AutoModelForCausalLM.from_pretrained(model_id)
        # solution 1: explicitly expose missing attributes
        # self.prepare_inputs_for_generation = self.llm.prepare_inputs_for_generation
        # self.config = self.llm.config

    # solution 2: pass through all missing attributes
    # def __getattr__(self, name: str):
    #     """Forward missing attributes to the wrapped module."""
    #     try:
    #         return super().__getattr__(name)  # defer to nn.Module's logic
    #     except AttributeError:
    #         return getattr(self.llm, name)

    def forward(self, *args, **kwargs):
        return self.llm(*args, **kwargs)

config = LoraConfig(task_type="CAUSAL_LM", target_modules=["q_proj", "v_proj"])
model = MyModel()
model = get_peft_model(model, config)
inputs = torch.tensor([[1, 2, 3, 4, 5]])
output = model(inputs)

The error is:
Traceback (most recent call last):
  File "/home/foo/anaconda3/envs/peft/lib/python3.10/pdb.py", line 1723, in main
    pdb._runscript(mainpyfile)
  File "/home/foo/anaconda3/envs/peft/lib/python3.10/pdb.py", line 1583, in _runscript
    self.run(statement)
  File "/home/foo/anaconda3/envs/peft/lib/python3.10/bdb.py", line 598, in run
    exec(cmd, globals, locals)
  File "<string>", line 1, in <module>
  File "/home/foo/work/forks/peft/foo.py", line 31, in <module>
    model = get_peft_model(model, config)
  File "/home/foo/work/forks/peft/src/peft/mapping.py", line 170, in get_peft_model
    return MODEL_TYPE_TO_PEFT_MODEL_MAPPING[peft_config.task_type](
  File "/home/foo/work/forks/peft/src/peft/peft_model.py", line 1442, in __init__
    self.base_model_prepare_inputs_for_generation = self.base_model.prepare_inputs_for_generation
  File "/home/foo/work/forks/peft/src/peft/tuners/lora/model.py", line 332, in __getattr__
    return getattr(self.model, name)
  File "/home/foo/anaconda3/envs/peft/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1709, in __getattr__
    raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
AttributeError: 'MyModel' object has no attribute 'prepare_inputs_for_generation'

Expected behavior
This code should work even without one of the two solutions sketched out above.

I investigated this a bit and I think there is no good solution on the PEFT side here.
The issue is that if we want to accommodate a specific task type, like causal LM in this instance, we need to have specific attributes on the model for it to work. Therefore, we cannot support arbitrary custom models.
For users who come across this, there are 3 potential solutions:

Expose the specific needed arguments ("solution 1" in the snippet above). This has the least amount of side effects, but future PEFT versions may require additional parameters, so this solution is not quite as robust as the next.
Implement __getattr__ ("solution 2" in the snippet above). This is more robust to future changes, but can make some errors messages more confusing.
Don't pass the task_type. When using config = LoraConfig(target_modules=["q_proj", "v_proj"]), the code above passes, but some task specific methods may not work correctly, like model.generate.

I investigated this a bit and I think there is no good solution on the PEFT side here.
The issue is that if we want to accommodate a specific task type, like causal LM in this instance, we need to have specific attributes on the model for it to work. Therefore, we cannot support arbitrary custom models.
For users who come across this, there are 3 potential solutions:
1. Expose the specific needed arguments ("solution 1" in the snippet above). This has the least amount of side effects, but future PEFT versions may require additional parameters, so this solution is not quite as robust as the next.

2. Implement `__getattr__` ("solution 2" in the snippet above). This is more robust to future changes, but can make some errors messages more confusing.

3. Don't pass the `task_type`. When using `config = LoraConfig(target_modules=["q_proj", "v_proj"])`, the code above passes, but some task specific methods may not work correctly, like `model.generate`.

which snippets are you talking about?

In the code I posted above, I have solution 1 and 2 as comments. I'll reproduce it here for you:
class MyModel(nn.Module):
    def __init__(self):
        super().__init__()
        self.llm = AutoModelForCausalLM.from_pretrained(model_id)
        # solution 1: explicitly expose missing attributes
        # self.prepare_inputs_for_generation = self.llm.prepare_inputs_for_generation
        # self.config = self.llm.config

    # solution 2: pass through all missing attributes
    # def __getattr__(self, name: str):
    #     """Forward missing attributes to the wrapped module."""
    #     try:
    #         return super().__getattr__(name)  # defer to nn.Module's logic
    #     except AttributeError:
    #         return getattr(self.llm, name)

    def forward(self, *args, **kwargs):
        return self.llm(*args, **kwargs)

You could either uncomment the code beneath "solution 1" or the code beneath "solution 2". The pros and cons are described above. Of course, depending on what your code looks like, the solution may need a bit of tweaking.

Thanks for the great explanation. Just to  confirm, this will only behave as expected if the llm is the first thing that is passed in the forward call right? Are there any caveats to using this approach to fine-tune models?

this will only behave as expected if the llm is the first thing that is passed in the forward call right?

Sorry, could you explain further? The llm is not passed to the forward call in this example.

Are there any caveats to using this approach to fine-tune models?

It depends on your use case. Just to give an example, when you wrap your model like this, checks such as isinstance(model, transformers.PretrainedModel) will return Falseb and checks of the signature of forward will not find certain arguments if you use *args, **kwargs. Furthermore, some methods like save_pretrained may not work or at least not fully.
These things can be issues if, for instance, you use some training framework (say, Trainer from transformers) which relies on these types of checks. If your training and inference is fully custom and is aware of what the model looks like, you should be able to avoid these issues though.

@BenjaminBossan

Sorry, could you explain further? The llm is not passed to the forward call in this example.
I mean to say that self.llm is the first thing that the input is passed into in the forward call. Like the first layer of the model, only then it'll work as expected. Is that right?

Well, for the original issue why I opened the PR, this is not relevant. If your use case requires the model to be called later, that should not be a problem.


Controller stays in SmartStart inclusion mode even if there aren't any planned provisioning entries

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

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

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

Describe the bug
Not sure how it happened, but the controller is reporting that it's in SmartStart inclusion mode, even though all my provisioned entries are included. I'd expect it to be Idle.
Not sure how to reproduce, possibly:

Add a QR code for SmartStart inclusion
Power on the node, and it gets included
SmartStart inclusion mode is not disabled?

Device information
N/A
How are you using node-zwave-js?

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

Which branches or versions?
version:
node-zwave-js branch: 8.11.6
zwavejs2mqtt branch: 6.5.2
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
In debugging an HA issue, I noticed that the controller was in SmartStart inclusion mode due to an unprovisioned node. I removed the entry and the state went to idle.
Some days later I had to re-include a node, so I performed the exclusion, then re-imported the QR code and added it via SmartStart. Today, I noticed that the inclusion state is back to SmartStart, but all nodes are provisioned.
Attach Driver Logfile
Sent privately.

I'm unable to reproduce this. The only thing I could imagine is that there is a provisioning entry with a DSK that's not known to belong to any included nodes.


Add missing parenthesis when MBEDTLS_ECP_NORMALIZE_MXZ_ALT is declared

As reported in, and fixes #4217
Status
READY
Requires Backporting
Yes
Migrations
NO
Todos

[x] Backported

Steps to test or reproduce
Part of the _ALT interface, and therefore not tested.

Note: I checked and 2.16 is affected, so this needs to be backported there. No need to backport to 2.7 as it's reaching end-of-life with the next release, for which the code is already freezed.

Added #4241 for backporting to 2.16


color blind people issue

Some colors are too close to each other  and this make color recognition harder for color blinded people
Screenshots

It's great theme and I'm waiting for it to get better
Thanks for considering color blinded night owls!

Second this. The one thing I have a problem with (pretty major), is the background-highlighted color. I can barely see it. 😭

I was able to adjust the theme in my VSCode settings by adding the below to the settings.json file:
"workbench.colorCustomizations": {
    "[Night Owl]": {
      "list.focusBackground": "#2E3250"
    }
  }

I just tried to find the color that was used elsewhere in the theme so it didn't feel out of place. It was honestly still hard for me though since I don't see some of these colors well. 🙈

Cutting a release today that should help with the focus background issue.


fixed reconciliation on storage size change

fixes https://github.com/VictoriaMetrics/operator/issues/1144

Thanks for contribution!


pip install bug

There appears to be some pip installation bugs, though it works with pip2:
) pip install academictorrents
Collecting academictorrents
  Using cached https://files.pythonhosted.org/packages/85/b8/276d72e19330981d48df6b6480fa975e10d9a80f0f3490d8dcab65454005/academictorrents-2.0.21.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/9f/jr_p974d3j318tmvrfkjl55w0000gp/T/pip-install-fd55gdv7/academictorrents/setup.py", line 7, in <module>
        with open('LICENSE') as f:
    FileNotFoundError: [Errno 2] No such file or directory: 'LICENSE'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/9f/jr_p974d3j318tmvrfkjl55w0000gp/T/pip-install-fd55gdv7/academictorrents/
-> [1]
) pip3 install academictorrents
Collecting academictorrents
  Using cached https://files.pythonhosted.org/packages/85/b8/276d72e19330981d48df6b6480fa975e10d9a80f0f3490d8dcab65454005/academictorrents-2.0.21.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/9f/jr_p974d3j318tmvrfkjl55w0000gp/T/pip-install-l4oioj01/academictorrents/setup.py", line 7, in <module>
        with open('LICENSE') as f:
    FileNotFoundError: [Errno 2] No such file or directory: 'LICENSE'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/9f/jr_p974d3j318tmvrfkjl55w0000gp/T/pip-install-l4oioj01/academictorrents/
-> [1]
) pip2 install academictorrents
Collecting academictorrents
  Downloading https://files.pythonhosted.org/packages/64/44/74e4de0b1ee76d252b829d5d651c724f2a3f72de6dab512f347b4994b696/academictorrents-2.0.21-py2-none-any.whl
Collecting PyPubSub==3.3.0 (from academictorrents)
  Downloading https://files.pythonhosted.org/packages/95/5a/1801be1a63af9250e79b8941a37b88e3ca0d660b880b9862fe9016ae6a3a/PyPubSub-3.3.0.zip (87kB)
    100% |████████████████████████████████| 92kB 3.0MB/s
Collecting future==0.16.0 (from academictorrents)
  Downloading https://files.pythonhosted.org/packages/00/2b/8d082ddfed935f3608cc61140df6dcbf0edea1bc3ab52fb6c29ae3e81e85/future-0.16.0.tar.gz (824kB)
    100% |████████████████████████████████| 829kB 9.8MB/s
Collecting bencode.py==2.0.0 (from academictorrents)
  Downloading https://files.pythonhosted.org/packages/1f/09/cda159542fe188706de49734e26522c360affe79f8dcf01e807f72cdfc7f/bencode.py-2.0.0-py2.py3-none-any.whl
Collecting bitstring==3.1.5 (from academictorrents)
  Downloading https://files.pythonhosted.org/packages/f3/e5/dfe4c49c93d174a5fd807ed307d3a3f38c6b3e140972945f81a5f5578ca7/bitstring-3.1.5.zip (624kB)
    100% |████████████████████████████████| 624kB 10.7MB/s
Collecting requests==2.7.0 (from academictorrents)
  Downloading https://files.pythonhosted.org/packages/26/ff/c71b3943bebdd9f7ceb9e137296370587eb0b33fe2eb3732ae168bc45204/requests-2.7.0-py2.py3-none-any.whl (470kB)
    100% |████████████████████████████████| 471kB 12.1MB/s
Building wheels for collected packages: PyPubSub, future, bitstring
  Running setup.py bdist_wheel for PyPubSub ... done
  Stored in directory: /Users/athundt/Library/Caches/pip/wheels/94/da/6e/2127e2253ef98b9b98b625e78f5158dd66966a5cc9f1d1478b
  Running setup.py bdist_wheel for future ... done
  Stored in directory: /Users/athundt/Library/Caches/pip/wheels/bf/c9/a3/c538d90ef17cf7823fa51fc701a7a7a910a80f6a405bf15b1a
  Running setup.py bdist_wheel for bitstring ... done
  Stored in directory: /Users/athundt/Library/Caches/pip/wheels/2d/29/47/179175c4ddff694032837432ae45c04c6bf93e4b01c23fb5b3
Successfully built PyPubSub future bitstring
internetarchive 1.8.2.dev1 has requirement requests<3.0.0,>=2.9.1, but you'll have requests 2.7.0 which is incompatible.
Installing collected packages: PyPubSub, future, bencode.py, bitstring, requests, academictorrents
  Found existing installation: requests 2.20.0
    Uninstalling requests-2.20.0:
      Successfully uninstalled requests-2.20.0
Successfully installed PyPubSub-3.3.0 academictorrents-2.0.21 bencode.py-2.0.0 bitstring-3.1.5 future-0.16.0 requests-2.18.4

Thanks @ahundt for the heads up! I'll take a look at this shortly and get back to you.

@ahundt
This issue has been resolved in the newest version of the AcademicTorrents package out on PyPi and Github, version 2.0.27.
Thanks for letting me know about it!


The toggle button for dark button needs a label.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The toggle button on the docs page( https://docs.circuitverse.org/#/ ) did not specify its purpose. Separate it from the edit on GitHub link. It is confusing at first sight.
Additional context
Add any other context or screenshots about the feature request here.

Hi,
How does this look?

I am actually very new (this is my first issue :) ) to this repository and I am not yet aware of the structure of the codebase. It would be helpful if you could point me to the HTML/CSS files.
Thank you.

Hi, @CodeSarthak!!! This is cool but I can't help you with further stuff since I am just a contributor to this project and I don't have push permissions. So, wait for the reviewers to look at your solution. The HTML/CSS files you will find them here:
https://github.com/CircuitVerse/CircuitVerse/tree/master/public

Sure, I'll wait for the approval and then start working on it.
Thanks a lot @PragatiVerma18. Just a small thing - I was able to locate the CSS files but I am still unable to find the HTML source files :(

Here you go :
https://github.com/CircuitVerse/CircuitVerseDocs/blob/master/docs/index.html
I guess we were looking at the wrong place. There is a separate repository for the CircuitVerse docs:
https://github.com/CircuitVerse/CircuitVerseDocs

Right. Thank you once again.

@satu0king

Hi,
How does this look?

I am actually very new (this is my first issue :) ) to this repository and I am not yet aware of the structure of the codebase. It would be helpful if you could point me to the HTML/CSS files.
Thank you.

That looks good, you can just write toggle theme instead of go dark and try and avoid space between edit on github and the toggle button.
Thank You

Thank you for the feedback @satu0king . I have made the improvements :

Please do recommend any other changes if required.

Here you go :
https://github.com/CircuitVerse/CircuitVerseDocs/blob/master/docs/index.html
I guess we were looking at the wrong place. There is a separate repository for the CircuitVerse docs:
https://github.com/CircuitVerse/CircuitVerseDocs

Thank you for your help @PragatiVerma18 but this HTML file is not the correct one :(


Compatibility with modded storage

Describe the Suggestion
Make contraptions work with modded storages like Expanded storage.
Screenshots and Videos

Expanded Storage on Curseforge
Additional Context
It uses it's own container library
https://www.curseforge.com/minecraft/mc-mods/ninjaphenixs-container-library

This is more of a issue with the forge version supporting modded storages you can make a issue about it their or make a addon


[Feature Request]: Add option to disable gradual dimming for some lights

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Current Behavior
When I adjust the brightness on my lifx bulbs they receive too many commands at once and there is a fews seconds of lag when adjusting them.
Expected Behavior
A option in yaml that would allow you to disable the gradual dimming on individual cards, then the light would just snap to the desired brightness, but would not affect all cards, just the ones specified.
Steps To Reproduce
No response
Context
YAML state

Environment
- Browser:
- HA Version:
- Mushroom:

Anything else?
No response

If this can be fixed then I will be able to use this repo.

Similar for me as well. Sometimes too many commands get stuck in the pipe. Unfortunately at least for my installation it is super irregular and seems to be an issue with HA itself.
Your expected behavior:
A option in yaml that would allow you to disable the gradual dimming on individual cards, then the light would just snap to the desired brightness, but would not affect all cards, just the ones specified.
makes sense to me.
@ironcrafter54 Do you know how to add an option like that?

I do not know how this would be done, the only way I could think of is adding a secondary light card called no-gradual-change that would still slide like the others cards but would only update when you release your finger/mouse.

How about an "update interval" parameter that sends the update every x ms?

Yeah that would probably allow you to fix the problem

I know I'm resurrecting an old thread, but @ironcrafter54 you do realize the bars act instantly if you just click somewhere on the bar, right?
I almost uninstalled this repo, since my 7" tablet was too narrow to reach max brightness if I started dragging from a low brightness, there wasn't enough physical space for the gradual dimming to reach 100%. Only then did I realize that I don't have to drag from a low point, I can just tap on 70%-80% on the bar and then drag from there.

Yep I am aware of that, thanks


temporarily disable format apps dropdown e2e test case

Signed-off-by: Chunxi Luo<EMAIL_ADDRESS>

@JustinKuli @gparvin
This newly added header test case behavior wired between local/grc travis and canary, I temporarily disable it and I will continuously investigate this and another header case in the same file https://github.com/open-cluster-management/grc-ui/blob/main/tests/cypress/tests/welcomePage_and_Header.spec.js#L46, will reenable once fixed them
FYI @willkutler

/ltgm


Fix license

Fix #39

Fixes the license to use the default github apache2.0 template
move copyright info to readme
Adds license badge to readme

@LourensVeen could you have a look at this?

Ah, I figured there'd be a little viper beneath the grass somewhere... :smiley:.


ENT leave empty lines

After toggling inline preview, calling org-toggle-inline-images works as intended, but ENT on the image will:

if it is the first line of the image, toggle it text, and leave otehr slices as is(still image)
if it is not the first line of the image, toggle the first line to text, and leave empty lines. for every other line.

ENT on the remaining slices resulting from the first condition will also leave empty lines.
demo: (used arrow keys and ENT throughout)

Thank you for this report. There is a modification hook on each overlay that should entirely delete the corresponding sliced image and dummy lines. Could you please install the most recent version of the package and confirm you still have this problem in your emacs -Q?


Fasttouch on Android doesn't work well

Hi,
Fasttouch doesn't work well on Android, sometime you just scroll and you accidently click link, and it happen often and it' anoying.
But fasttouch work great on iPhone.
Any idea to make fasttouch work on iPhone but not on Android?
I just wanted to find a way to put useFastTouch: false,
Only when it's not a iPhone.
something like, if it's not iPhone useFastTouch: false,
i know how to check user agent, but don't really know how tu make it work in the:
var jQT = new $.jQTouch({
Dynamically changing true to false or something like that.
something like that should work, but really don't know how
var ua = navigator.userAgent.toLowerCase();
var isAndroid = ua.indexOf("android") > -1; //&& ua.indexOf("mobile");
if(isAndroid) {
// Do something!
var fastouch = 'false,' ;
//alert('is android');
}

any idea to make it work?


Nice project but.

How can I use this on windows to force my python script to bytecode (while in windows) the files to bytecode the pyc using the linux pyc file magic as it seems they are diferent than the windows 3.5.2. (Yes I need to generate a zip archive with pyc files inside that works on linux as for some unbenowned reason the magic is different.)

I think this is out of scope for pew.
You might want to take a wheel, and compile its files to .pyc
Or maybe use Pex
Or maybe pyinstaller
Afaik Python bytecode should work the same for the same Python version (even if on Linux vs Windows), if you found otherwise can created a reduced test case I'm sure that would be interesting for others (maybe the Python core developers themselves)... but I don't see how pew could help you solve that problem


nixos-container: Run containers using unified cgroup hierarchy

Describe the bug
Containers spawned by nixos-container fall back to old cgroup hierarchy, which does not support proper delegation of resource limits to processes running in that container.
Steps To Reproduce
Steps to reproduce the behavior:

nixos-container create test --auto-start
nixos-container root-login test
3. systemctl status will show Tainted: cgroupsv1
4. mount | grep cgroup will show a mount type cgroup
5. systemd-run --scope -G -p MemoryMax=4G -p MemorySwapMax=10M nix shell nixpkgs#ruby_3_1 -c ruby -e '(1 << 100).times.to_a' This will be allowed to consume all memory of the machine until it runs out, the 4G cap is not enforced

Expected behavior
I expected the container to use a unified cgroup hierarchy, same as on the host, with full delegation and control over its subtree.
Metadata
# nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.19.14, NixOS, 22.11 (Raccoon), 22.11.20221014.4428e23`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.0`
 - channels(root): `"home-manager, nixos"`
 - channels(kuba): `"home-manager, nixpkgs"`
 - nixpkgs: `/nix/store/r2s8wcc8n4c72p9zg5gsacg8nmdhjvka-source`

This is the log from<EMAIL_ADDRESS>using declarative containers:
Oct 17 13:54:45 eridanis systemd[1]: Starting Container 'test'...
Oct 17 13:54:46 eridanis container test[88707]: Spawning container test on /var/lib/nixos-containers/test.
Oct 17 13:54:46 eridanis container test[88707]: Press ^] three times within 1s to kill container.
Oct 17 13:54:46 eridanis container test[88707]:
Oct 17 13:54:46 eridanis container test[88707]: <<< NixOS Stage 2 >>>
Oct 17 13:54:46 eridanis container test[88707]:
Oct 17 13:54:46 eridanis container test[88707]: running activation script...
Oct 17 13:54:46 eridanis container test[88707]: setting up /etc...
Oct 17 13:54:46 eridanis container test[88707]: starting systemd...
Oct 17 13:54:46 eridanis container test[88707]: systemd 251.4 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +SMACK +SE>
Oct 17 13:54:46 eridanis container test[88707]: Detected virtualization systemd-nspawn.
Oct 17 13:54:46 eridanis container test[88707]: Detected architecture x86-64.
Oct 17 13:54:46 eridanis container test[88707]: Failed to create symlink /sys/fs/cgroup/cpu: Read-only file system
Oct 17 13:54:46 eridanis container test[88707]: Failed to create symlink /sys/fs/cgroup/cpuacct: Read-only file system
Oct 17 13:54:46 eridanis container test[88707]: Failed to create symlink /sys/fs/cgroup/net_cls: Read-only file system
Oct 17 13:54:46 eridanis container test[88707]: Failed to create symlink /sys/fs/cgroup/net_prio: Read-only file system

I thought it could be relevant, but after googling around, these seem like errors that happen after systemd decided to use cgroupv1. I'm not sure how to debug its decision to use legacy cgroups inthe first place.

Thanks, that was it. I also noticed this in the code https://github.com/systemd/systemd/blob/7e6821ed4e09d68c45858ba463a013eb7593c2c6/src/nspawn/nspawn.c#L475-L499
But the following is not enough to enable it:
containers.${name}.extraFlags = [ "--setenv=SYSTEMD_NSPAWN_UNIFIED_HIERARCHY=1" ];

Running $ SYSTEMD_NSPAWN_UNIFIED_HIERARCHY=1 systemd-nspawn ... didn't help either, so I'm not sure how you're supposed to use it.
Should we add a symlink as a workaround? I think it'd make sense to fix it for all users of nixos-containers by defining it somewhere around here: https://github.com/NixOS/nixpkgs/blob/0c60d6c5d5ab9e5676726199ac6f4ec2a5134b75/nixos/modules/virtualisation/nixos-containers.nix#L485-L489

That worked! I can see with systemctl status that the container is no longer tainted. Working on a PR now


[feature request] Save ER Diagram layout

After re-arranging the ER diagram with tens of tables, i found out that closing the diagram or refreshing it changes the arrangment of tables, instead of just adding/removing/updating.
Which means, every time i make a small change to a table, i have to re-arrange the full ER diagram again, from scratch.
That is really time comsuming, and makes the "ER Diagram" tool pretty "unuseful" to me.

Already implemented in 7.0.5

Refreshing does indeed cause the ERD to reset in layout. So this is either not actually implemented, or a bug.
Version <IP_ADDRESS>407071610


Super Resolution notebook: Error(s) in loading state_dict for ControlNet

The notebook fails for me when trying to load the state_dict due to missing and unexpected keys. Upon further inspection, it seems that the correct controlnet_bottleneck_mode should be "effnet" instead of "large". However, even in that case, the number of channels in the SR checkpoint (3) is not the same as what the model expects (16). Changing "controlnet_filter" allows me to load the model, but just leads to another error further down the line. Could it be that you simply uploaded the wrong checkpoint?

 "
}

To me it looks like the checkpoint on HuggingFace does not match the "large" mode.

Works now (someone updated the checkpoint an hour ago). Thanks!


Add a PromptDialog testing component

Adds a component that's useful for testing the PromptDialog components. Selecting a link on the page will trigger a dialog to open.
See gecko-dev/toolkit/components/windowwatcher/nsIPromptService.idl for the dialog parameters.
After installation the following file can be edited directly to test different prompts and parameters:
/usr/share/harbour-webview/components/component.js
This PR is intended only for testing purposes of the following PRs which must be applied for this to work:
https://github.com/sailfishos/embedlite-components/pull/5
https://github.com/sailfishos/sailfish-components-webview/pull/117

Marked as work in progress since there's no plan to integrate this, it's just for testing.


Waveshare Red-Black-White Screen

Hello, I already have the Waveshare red/black/white e-ink screen. Any idea on how to modify the code to account for the different screen? I can't seem to figure out how to get it to even turn on. Can I add the appropriate screen in myself on the screen configuration? EPD2in13bc I think is the one I need.

Hi @holmesha , to add support for the EPD2in13bc screen, you can take a look at https://github.com/dr-mod/zero-btc-screen/blob/main/presentation/screens/epd2in13bv3.py they should be very similar, it might just boil down to substituting the driver class.

I have the same red/black/white e-paper screen from Waveshare as @holmesha. I'm no fluent Python programmer but was able to get the screen properly working in black/white currently.
Basic steps taken:
Copy epd2in13bv3.py to epd2in13bc.py
Edit file configuration.cfg:
diff --git a/configuration.cfg b/configuration.cfg
index 4e67afe..6d734e6 100644
--- a/configuration.cfg
+++ b/configuration.cfg
@@ -2,13 +2,14 @@
 console_logs             : false
 #logs_file                : /tmp/zero-btc-screen.log
 dummy_data               : false
-refresh_interval_minutes : 15
+refresh_interval_minutes : 5
 currency                : BTC

 # Enabled screens or devices
 screens : [
-    epd2in13v2
+#    epd2in13v2
 #    epd2in13bv3
+    epd2in13bc
 #    picture
 #    inkyWhatRBW
   ]
@@ -20,6 +21,9 @@ screens : [
 mode : candle

 [epd2in13bv3]
+mode  : candle
+
+[epd2in13bc]
 mode  : line

 [picture]

Add black/white/red screen driver:
diff --git a/presentation/screens/__init__.py b/presentation/screens/__init__.py
index 53b7a12..58e4497 100644
--- a/presentation/screens/__init__.py
+++ b/presentation/screens/__init__.py
@@ -1 +1 @@
-from . import epd2in13v2, epd2in13bv3, picture, inkywhatrbw
+from . import epd2in13v2, epd2in13bv3, epd2in13bc, picture, inkywhatrbw

More changes are required to display e.g. "loosing" candles in red color. I haven't implemented this, yet. On Reddit one guy did this, but he hadn't replied to me after I asked for some code snippets. Apparently he didn't provide a push request here, too.

Thanks so much for digging into my question! I'm new to all of this and the code has been a bit of a struggle so far.

At the moment I can't assist further to add the red color where appropriate. I need to get more used to Python first.

epd2in13bv3.py works fine for me out of the box with the 2.9" Red/White/Black E-Ink Waveshare display hat, but it only displays in black and white.
+1 for red color support.


PermissionError: [Errno 13] Permission denied

Hi, I used the recording button on http://localhost:5000/ to record my voice.
After ending recording, I got these error messages:
An error occurred. Please try again. {"readyState":4,"responseText":"<!doctype html>\n<html lang=en>\n  <head>\n    <title>PermissionError: [Errno 13] Permission denied: 'C:\\\\Users\\\\xxxx\\\\AppData\\\\Local\\\\Temp\\\\tmpw6fhik2p.m4a'
Traceback (most recent call last):
  File "VoiceNoteTaker\venv\lib\site-packages\flask\app.py", line 2551, in __call__
    return self.wsgi_app(environ, start_response)
  File "VoiceNoteTaker\venv\lib\site-packages\flask\app.py", line 2531, in wsgi_app
    response = self.handle_exception(e)
  File "VoiceNoteTaker\venv\lib\site-packages\flask\app.py", line 2528, in wsgi_app
    response = self.full_dispatch_request()
  File "VoiceNoteTaker\venv\lib\site-packages\flask\app.py", line 1825, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "VoiceNoteTaker\venv\lib\site-packages\flask\app.py", line 1823, in full_dispatch_request
    rv = self.dispatch_request()
  File "VoiceNoteTaker\venv\lib\site-packages\flask\app.py", line 1799, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "VoiceNoteTaker\main.py", line 30, in transcribe
    audio_file.save(temp_audio_file.name)
  File "VoiceNoteTaker\venv\lib\site-packages\werkzeug\datastructures.py", line 3002, in save
    dst = open(dst, "wb")

tested on Windows 11, venv python version 3.10.10. Does not work using admin Anaconda prompt either.

Looks a Windows privilege issue. I haven't tested it on Windows yet and will get my hands on it this week.

Meanwhile, a quick get around may be, you can try the WSL(2) to run the application.


[$1000] Web - On Task Details, the title Section shows hovered effect even though the cursor is on the description.

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

Action Performed:

Open App > Press FAB > Assign Task > Create Task
Press the check icon on Title to complete the Task
Uncheck the checkbox icon to reopen the task
Observe the hover state of the Title section

Expected Result:
The Title section should not show the hover effect if the cursor is on the Description section.
Actual Result:
Clicking on uncheck will shift the hover to Description, but still, Title Section shows the hover effect(green background)
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.55-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/55816fd5-4be8-4e74-89f7-f53fc6a305bb

https://github.com/Expensify/App/assets/115492554/060320be-86a5-498c-8961-bfc90f00ddb3
Expensify/Expensify Issue URL:
Issue reported by: @jayeshmangwani
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691523409931269
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01efa6edb4c1b8dea5
Upwork Job ID:<PHONE_NUMBER>389550592
Last Price Increase: 2023-08-18

Looks like dupe https://github.com/Expensify/App/issues/16923
cc @parasharrajat

Agree that It dupe

@parasharrajat Yes it's reproducing on my side
https://github.com/Expensify/App/assets/35371050/ede23d7f-20d6-4872-b7b0-5341de6bd5b1


Large js gets redownloaded on reopening the page

Currently on almost every load of the page, 700kb+ of JS gets redownloaded.
On not very fast internet Wallet can take up to 15s to load (google.com loads in 4s), reloading another ~5-10s

From China it's even worse:

Steps to reproduce

Open incognito window
Open Inspect > "Network" tab
Open wallet.near.org
Observe loading >1Mb of data
Refresh wallet.near.org
Observer re-loading >1Mb of the same data

700k of JS is not a lot these days, e.g. Twitter loads more than 1 MB of JS.

Currently on almost every load of the page

this isn't the case for me in either Safari or Chrome. It has etag so any browser properly supporting HTTP shouldn't be re-downloading whole file unless it is updated
maybe it is somehow messed with by firewall though? (not clear how without removing HTTPS)
are you sure it happens outside of incognito (which has to reload everything as otherwise you are identifiable)?

I will embed this one in #1101 , even if not strictly connected I believe that having a smaller payload is better than just pumping everything through CDNs
cc @MaximusHaximus

The JS files are not re-downloaded in my test.
The 800+ KB JS file is fast to load in my environment, but still takes 20~40 seconds for some users.


Vite-Plugins Incompatible

When using vite plugins like vite-plugin-pages or vite-plugin-components I get ERR_UNSUPPORTED_DIR_IMPORT or is not a Function. Any ideas how to get that working? Without vite plugins the DX for me is not there sadly.

Just saw that in need to add the default key after the plug-in Import to get it working:
Pages.default()


Issue recovering LND wallet

Context
I've deposited funds in an old version of Raspiblitz and when I tried restoring my wallet after updating the node I never managed to access my funds anymore.
Back then there was no channel backup, but the funds were on chain (not committed to any channel) anyway.
Recently I've update to 1.6.2 and entered my mnemonic from the old node and this is what I see while trying to recover:

I imagine the chances of recovering my funds are low by now, but if there is still a chance I'd like to try, if someone could point to a path that depends less on raspiblitz software and more on the underlying software so I can try faster.

try exiting this screen and use the lnd cli:
lncli create
will offer you to enter the seed and will restore your onchain funds.
Can also use the LND Lighning Desktop App as in the FAQ.

I've managed to recover my funds last evening, I wasn't entering the password D since the message suggests most people don't set that password, but apparently I did.
I recovered it using the Zap wallet though.

try exiting this screen and use the lnd cli:
lncli create
will offer you to enter the seed and will restore your onchain funds. Can also use the LND Lighning Desktop App as in the FAQ.

The LND Lightning Desktop App was archived in 2021. Do you still recommend it or is there a better option now @openoms ?
The LND Lightning Desktop App says "loading network" since quite a while after accepting the seed phrase:

try exiting this screen and use the lnd cli:
lncli create
will offer you to enter the seed and will restore your onchain funds. Can also use the LND Lighning Desktop App as in the FAQ.

The LND Lightning Desktop App was archived in 2021. Do you still recommend it or is there a better desktop option now @openoms ?
The LND Lightning Desktop App says "loading network" since quite a while after accepting the seed phrase:

No, do not use that outdated app.
Can recover an LND seed (and SCB) in Blixt wallet on mobile.

I didn't have any SCB and the funds weren't found in Blixt, so I used sparrow wallet to recover what was accessible on-chain.
It looks like some funds might still be locked in private lightning channels. Is it possible to break these channels and free the funds by deliberately publishing an outdated state?


CI Tests failing with both python 2 and python 3

Hey @icarito. I've tried make CI tests passing. But build fails with this error:

ERROR in ./node_modules/py-loader?compiler=pj!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./test/fixture/pages/index.vue
Module parse failed: Unexpected token (1:16)

https://circleci.com/gh/nuxt-community/python-module/4
Would you please take a look at it? (Since you are a python geek 🤓 )

Javascripthon is expected to only work for Python 3.5 -

I think I fixed circleci now. Thanks for the class on testing with Nuxtjs! :-D

Thanks for your amazing idea :) Science after public announcement many users will try this module, what's your idea to add instructions installing exactly python 3.5 and also adding fork of metapensiero to their local requirements.txt?

Before making an announcement :-) I'd like to work out the proper syntax with @azazel75 because we are still stabilizing the syntax for ES6 exports https://github.com/metapensiero/metapensiero.pj/issues/39 - hopefully we won't have to use a fork.

OK. So we will wait for a while before the announcement. Please ping me or @Atinux for that and good luck ;)

This is awesome! I have no knowledge about Python, but when it's ready I would love to announce it publicly :)

@Atinux - I'm honored to contribute, a fan of Nuxt and Vue :-)
At this point the anonymous default exports have landed in the transpiler so things are working well.
Please review this and feel free to release it - hopefully it will be useful and improved upon.
Thanks in advance,
Sebastian

@icarito I need to release it  ;-)

Initial version just released!

wow !


Object Oriented Refactor

Description
This PR creates an object-oriented structure to the codebase. Code is organized into 2 primary folders: drivers and managers. The drivers interact with the low-level hardware, such are the Ethernet interface and UART. The drivers are instantiated in Context.hpp. The managers use the drivers to get useful work done. They are instantiated in main.cpp and access the drivers through the context object.
This PR does the following:

Splits existing EthernetDriver code into driver and manager paradigm
Adds Roboclaw support for speed control

Self Checklist

[x] I have tested that the new behavior works
[x] I have formatted the code with make format

Everything looks good to merge!


feat: add view-ui-plus resolver

I would wait until view-ui-plus get more adoption

I would wait until view-ui-plus get more adoption

Which project is not built from scratch. The great thing about GitHub is that it doesn't restrict unpopular projects.

@see IMHO, view-ui-plus can provide this resolver by itself. There are too many issues in this repo about resolvers instead of the plugin self.
TBH, maybe Element Plus will built-in itself's resolver in the future, then we can upgrade or maintain it better.

@sxzz unplugin-element-plus?

@see No, this plugin is used on importing style only automatically, instead of importing Vue componments.

@sxzz another separate library?

@see I mean maybe Element Plus will do it in the future. Currently haven't.

pending too long as view-ui forgotten

Thanks for your contributions. We are sorry we no longer accept new resolvers:
https://github.com/antfu/unplugin-vue-components/blob/main/src/core/resolvers/_READ_BEFORE_CONTRIBUTE.md


Scrolling to specific row (e.g. the end) after content has been set

How would one go about scrolling to a specific row – in my case, the end – after the content has been set (list view has settled, properties are synchronized etc.)? I see no way of hooking into the logic/rendering mechanics. Any pointers are greatly appreciated. :)

This should be resolved when #185 is merged in


Add Fiery Warpath "hunt details"

Report remaining mouse counts per wave, & if bosses are invincible.
Report morale / support_morale fields, for Warpath Thrasher computations
Report streak count, type, and whether the hunt extended it

Quick Q's:

Do Anniversary traps have an insta-catch chance on Warmonger & Artillery Commander with Wardens up? If so, would that affect the invincibility logic?
What insights are you hoping to gain from recording streak count, type, and extended?

I believe they do, so knowing if the boss should have been invincible helps verify the proc rate (not that many will use that anniv. traps here)
Several things:

Gargantuamouse attraction rate vs. streak
on/off streak attraction. There are at least two ways for the charms to bias the population, one being adding "pseudomice" and another being a flat proportion for on/off. The "streak extended" and type fields offer (I think) a great simplification of the otherwise-needed SQL to find instances where the right charm did or did not work

I don't quite follow what you mean by the charms adding "pseudomice".
Also, couldn't the flat proportion be the same no matter whether you're on or off a streak? For instance, suppose Super Warrior charms give a 50% attraction boost to Warrior-group mice. Wouldn't that 50% likely be the same whether or not you're on a streak of Warriors?

By pseudo mice I mean that the population proportion is biased by some amount. Say if you were 3/3/9, arming an Archer charm might double the amount of archers, making it seem like 3/3/18. Arming a Super Archer might quadruple it, so it seems like 3/3/36.
Probably this is not the mechanism (charms anecdotally feel more effective than this scheme would suggest for wave starts and type eradications) but it would be nice to be definitive.
You are correct that a flat proportion is streak independent. I'm taking a shortcut and using HG's computation of whether the caught mouse is of the correct type to extend the streak. Changing the field to be streak independent, e.g. "targeted_was_attracted", means we have to do our own charm vs mouse comparison upon catch in order to set the flag correctly.
I envision the current SQL query to be something like, "select count() from hunts where locationid = # and details.streak.type = 'archer' group by cheeseid, charmid, details.num_archer, details.streak.increased_on_hunt".
This could certainly be doable with the other pattern: "select count() from hunts where locationid =# and details.target_type = 'archer' group by ..., details.num_archer, details.targeted_was_attracted".
To summarize I think there are definitely multiple ways to get at this same information. I went for streak extension because it meant simpler code :)


Add calendar and even pydantic data model

Add calendar and even pydantic data model, and address mypy coverage.
The CalendarList and Event objects are chosen using initial set of fields known to be used by Home Assistant.

Codecov Report

Merging #9 (8403391) into main (b5a5c93) will decrease coverage by 2.08%.
The diff coverage is 97.56%.

@@             Coverage Diff             @@
##              main       #9      +/-   ##
===========================================
- Coverage   100.00%   97.91%   -2.09%
===========================================
  Files            1        2       +1
  Lines           12       48      +36
===========================================
+ Hits            12       47      +35
- Misses           0        1       +1

Impacted Files
Coverage Δ

google_calendar_sync/model.py
97.14% <97.14%> (ø)

google_calendar_sync/store.py
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Replace usage of gpr_cmdline with gflags, and remove gpr_cmdline from…

Replace usage of gpr_cmdline with gflags, and remove gpr_cmdline from grpc

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Is the plan to eventually revive this PR or just restart from scratch by, for example, moving increasingly to gtest?

I think the PR was in a state where it could be revived. The reason it's not been revived yet is mainly because some people (me included) use run_tests.py with the option -lc to run core tests. Doing this would change that.

Is this PR still alive?

Removing reviewers until it's ready to use


BI-1909 - Unable to open observation dataset.

Description
Story: https://breedinginsight.atlassian.net/browse/BI-1909

Updated a unit test to check to prevent an NPE
Updated unit tests so that the database and redis containers live between test suites
Added some logging messages for fetching datasets

Dependencies
brapi-java-testserver/bug/BI-1909
Testing
Regression testing:

experiment upload
experiment view
germplasm upload
germplasm view

Checklist:

[x] I have performed a self-review of my own code
[x] I have tested my code and ensured it meets the acceptance criteria of the story
[x] I have tested that my code works with both the brapi-java-server and BreedBase
[x] I have create/modified unit tests to cover this change
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to documentation
[ ] I have run TAF: <please include a link to TAF run>

Created card to investigate issue: https://breedinginsight.atlassian.net/browse/BI-1928?atlOrigin=eyJpIjoiYWQwMjNhM2ViYWMzNGQyMzk2MjJjNTRlYzg3MzU1MjIiLCJwIjoiaiJ9


Add Saga Pattern

Messaging is something we deal with often.
Saw Cameron's tweet and realized we don't have Saga pattern here yet.

See also: Azure Design Patterns - Saga pattern

Would be good to have this one so Kyle's NServiceBus series can reference it.

Talking with @KyleMcMaster - he'll tackle this next week in adding this page and cross-linking to the article.

I'll take this one (I can't assign myself)

Make sure to link to your Supercharged Sagas series as well!
- [Supercharged Sagas - Introduction](https://blog.nimblepros.com/blogs/supercharged-sagas-introduction/)
- [Supercharged Sagas - Creating Your First NServiceBus Saga](https://blog.nimblepros.com/blogs/supercharged-sagas-creating-your-first-nservicebus-saga/)
- [Supercharged Sagas - Timeout Tips](https://blog.nimblepros.com/blogs/supercharged-sagas-timeout-tips/)
- [Supercharged Sagas - Unit Testing Strategies](https://blog.nimblepros.com/blogs/supercharged-sagas-unit-testing-strategies/)


Added bbox_intersection filter for Jinja.

Added bbox_intersection filter for Jinja, which allows clipping to the query bounding box. Although doing an intersection operation in the database rather than on the client can take some time, it seems it's worthwhile in this case to avoid sending too much over the network.
Connects to mapzen/vector-datasource#302.
@rmarianski could you review, please?

:+1:


improve CSV description and readme with template

Signed-off-by: dongdwdw<EMAIL_ADDRESS>

@dongwangdw
REVIEW OF README FILE:
Line 1 typo - ibm-ponitoring-prometheus-extension-operator - replace "p" with "m"
Line 7 - Replace "The IBM Monitoring Prometheus Extension Operator is used for installing Prometheus and Alertmanager by extending community prometheus operator."
with this:
You can use the ibm-monitoring-prometheus-extension-operator to install Prometheus and Alertmanager by extending the community prometheus operator.
Line 9 - Replace this paragraph:
The operator is part of IBM Monitoring Operator stack. It provides easier way to install Prometheus and Alertmanager with RBAC and TLS enabled. IBM Monitoring Operator stack is integrated in IBM Cloud Paks and installed as a part of Common Services, but they can also be deployed separately with Operator Lifecycle Manager. Please check the documentation below for any prerequisites required to run the standalone Operator.
with this:
This operator is part of the IBM Monitoring Operator stack. It provides a way to install Prometheus and Alertmanager with RBAC and TLS enabled. The IBM Monitoring Operator stack is integrated in IBM Cloud Paks and installed as part of IBM Cloud Platform Common Services. You can also use the Operand Deployment Lifecycle Manager Operator to install IBM Cloud Platform Common Services in your cluster. See the following documentation for prerequisites required to run the stand-alone Operator.
Line 39 - In section , ## SecurityContextConstraints Requirements, Replace this:

privileged SCC for operands
restricted SCC for operator

with this: and include WHICH operands run under privileged?
The ibm-monitoring-prometheus-extension-operator supports running under the OpenShift Container Platform default restricted security context constraints. The <??WHICH??operands> run under privileged security constraints.
For more information about the OpenShift Container Platform Security Context Constraints, see Managing Security Context Constraints.
Line 50: Delete the "### Quick start guide" heading if you do not have any content for this section
Line 52: Delete the ### Debugging guide heading if you do not have any content for this section
REVIEW OF .CSV FILE:
Line 197: In description: add the following statement in bold:
Important: Do not install this operator directly. Only install this operator using the IBM Common Services Operator.
For more information about installing this operator and other Common Services operators, see Installer documentation. Additionally, you can exit this panel and navigate to the IBM Common Services tile in OperatorHub to learn more about the operator.

/approve

/lgtm


Fix Qunit tests for latest Google Chrome (47.0.2526.73)

I'm working on this

Fix done, we're waiting for chrome 47 version on sauce labs


Compress Nobel prize example GIFs

I had a go at reducing the size of the GIFs down using Optimage's visually-lossless compression, and got the images down to ~1.5 MB each — around a 74% reduction:

marie-heavy.gif from 5.21 MB to 1.24 MB
radium-heavy.gif from 6.71 to 1.61 MB

As far as I can tell, Optimage has kept its promise and there's no perceptual difference between old and new images. I'm not sure if this is enough of a reduction to get the repo into a codesandbox, but it should at least help fix meilisearch/meilisearch-vue#34.

Hello @flother! thanks for your PR!
@bidoubiwa will review your PR once she comes back from vacation. She's the maintainer of this repo :)

Thanks a lot for this optimization ! 🔥

bors merge