[bug] Events from Rust are lost to JS

Describe the bug
When an event is emitted from Rust, it's lost to JS, as it loads before JS is ready to start listening for any event. The following code highlights the issue
Backend
tauri::Builder::default() .on_page_load(move |window, _| {
    let bootstrap = Bootstrap {};
    window.emit("bootstrap", bootstrap.clone()).unwrap();
})

Frontend
import { listen } from '@tauri-apps/api/event';

listen('bootstrap', () => {
  console.log('Hello World');
})

Reproduction

Clone repository that reproduces the issue
Follow instructions to start the App
Note that JS never starts, as it waits for an event to happen.

Expected behavior
JS should load Application. Edit the main.rs file and uncomment the commented code to show how it works by adding a timeout.
Platform and versions
Operating System - Windows, version 10.0.22000 X64
Webview2 - 98.0.1108.50
Visual Studio Build Tools:
   - Visual Studio Community 2019
   - Visual Studio Build Tools 2017

Node.js environment
  Node.js - 16.13.0
  @tauri-apps/cli - 1.0.0-rc.4
  @tauri-apps/api - 1.0.0-rc.1

Global packages
  npm - 8.5.0
  pnpm - Not installed
  yarn - Not installed

Rust environment
  rustup - 1.24.3
  rustc - 1.58.1
  cargo - 1.58.0
  toolchain - stable-x86_64-pc-windows-msvc

App directory structure
/.git
/node_modules
/public
/src
/src-tauri

App
  tauri - 1.0.0-rc.2
  tauri-build - 1.0.0-rc.2
  tao - 0.6.2
  wry - 0.13.1
  build-type - bundle
  CSP - unset
  distDir - ../build
  devPath - http://localhost:3000/
  framework - React

Stack trace
No response
Additional context
No response

Previously we had an event cache to mitigate this, but it causes issues, see #2323
So the event system isn't ideal for your use case, I'd probably write a function in your case:
Backend
tauri::Builder::default() .on_page_load(move |window, _| {
    window.eval("window.__BOOTSTRAP__ ()").unwrap();
})

Frontend
window.__BOOTSTRAP__ = () => {
  console.log('Hello World');
  delete window.__BOOTSTRAP__;
})

on_page_load is executed when DOMContentLoaded is fired, so you might need to check if the function exists and delay if it doesn't.
You can also emit an event or send a command from the frontend to notify when your listener is ready.

I ended up calling the backend with the frontend as soon as JS is ready, however I still need to apply the delay at 50ms or so. Not ideal still, but I guess will be ok. I may end up making a Tauri plugin 🤷♂ thank you for looking at the issue though


NOISSUE - Update aedes version and fix Dockerfile

What does this do?
Fixes Dockerfile, updates Aedes version, adds instance ID and message TTL env var.
Which issue(s) does this PR fix/relate to?
Put here Resolves #XXX to auto-close the issue that your PR fixes (if such)
List any changes that modify/break current functionality
There are no such changes.
Have you included tests for your changes?
No. I've tested it manually.
Did you document any new/modified functionality?
I've updated README.md file for aedes MQTT adapter.
Notes
Instance ID was already there, I've just wired it to aedes opts.

Codecov Report

Merging #863 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #863   +/-   ##
=======================================
  Coverage   85.43%   85.43%
=======================================
  Files          72       72
  Lines        4737     4737
=======================================
  Hits         4047     4047
  Misses        451      451
  Partials      239      239

Continue to review full report at Codecov.

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


No way to break open geodes

Geodes can be obtained by mining, however there is no way to break them open (nor is there a list of what items and their chance are). Maybe implement a new NPC job that you can give a diamond and geode to in a trading window and receive a random item. The trade window output would need to not display the item as its a random chance.
I don't believe there is an event to capture the trade, so this might be a chance to use a custom gui inventory window!

itemsadder.dsc custom gui handler support has been implemented into 1.3


Is there any way to colorize -ls command through the  :!ls in vim file?

Describe the solution you'd like
Would be great to colorize all directory/file names after writing :!ls directly from changing document!
Additional context

does it work if you use :ls --color?

does it work if you use :ls --color?

U r right, thank you!


Click while on animation

I have Link components inside a Motion component, but the component doesn't work while it is animated, after the animation stops, then the navigation works.
I'm using React Router Link component for the navigation.

I have this same issue, did you ever figure out a solution?

same here. I'm using a staggered motion to fade in elements, but the click event on each of the elements seems to get swallowed while they are animating. after the animation is finished everything works as expected.


Unable to install

I have tried a couple of times, on 2 versions of python, to install following instructions but it fails at installing neuropod
(venv) G:_ludwig\venv\Scripts>pip install ludwig[full]
Collecting ludwig[full]
Using cached ludwig-0.3.tar.gz (212 kB)
Collecting Cython>=0.25
Using cached Cython-0.29.21-cp37-cp37m-win_amd64.whl (1.6 MB)
Collecting h5py>=2.6
Using cached h5py-2.10.0-cp37-cp37m-win_amd64.whl (2.5 MB)
Collecting numpy>=1.15
Using cached numpy-1.19.2-cp37-cp37m-win_amd64.whl (12.9 MB)
Collecting pandas>=0.19
Using cached pandas-1.1.3-cp37-cp37m-win_amd64.whl (8.7 MB)
Collecting scipy>=0.18
Using cached scipy-1.5.3-cp37-cp37m-win_amd64.whl (31.2 MB)
Collecting tabulate>=0.7
Using cached tabulate-0.8.7-py3-none-any.whl (24 kB)
Collecting scikit-learn
Using cached scikit_learn-0.23.2-cp37-cp37m-win_amd64.whl (6.8 MB)
Collecting tqdm
Using cached tqdm-4.50.2-py2.py3-none-any.whl (70 kB)
Collecting tensorflow>=2.2
Using cached tensorflow-2.3.1-cp37-cp37m-win_amd64.whl (342.5 MB)
Collecting tfa-nightly==0.12.0.dev20200820045606
Using cached tfa_nightly-0.12.0.dev20200820045606-cp37-cp37m-win_amd64.whl (920 kB)
Collecting PyYAML>=3.12
Using cached PyYAML-5.3.1-cp37-cp37m-win_amd64.whl (216 kB)
Collecting absl-py
Using cached absl_py-0.10.0-py3-none-any.whl (127 kB)
Collecting xlwt
Using cached xlwt-1.3.0-py2.py3-none-any.whl (99 kB)
Collecting xlrd
Using cached xlrd-1.2.0-py2.py3-none-any.whl (103 kB)
Collecting openpyxl
Using cached openpyxl-3.0.5-py2.py3-none-any.whl (242 kB)
Collecting pyarrow
Using cached pyarrow-2.0.0-cp37-cp37m-win_amd64.whl (10.7 MB)
Collecting lxml
Using cached lxml-4.6.1-cp37-cp37m-win_amd64.whl (3.5 MB)
Collecting soundfile
Using cached SoundFile-0.10.3.post1-py2.py3.cp26.cp27.cp32.cp33.cp34.cp35.cp36.pp27.pp32.pp33-none-win_amd64.whl (689 kB)
Collecting scikit-image==0.14.2
Using cached scikit_image-0.14.2-cp37-none-win_amd64.whl (24.6 MB)
Collecting uvicorn
Using cached uvicorn-0.12.2-py3-none-any.whl (45 kB)
Collecting fastapi
Using cached fastapi-0.61.1-py3-none-any.whl (48 kB)
Collecting pydantic
Using cached pydantic-1.6.1-cp37-cp37m-win_amd64.whl (1.6 MB)
Collecting python-multipart
Using cached python-multipart-0.0.5.tar.gz (32 kB)
ERROR: Could not find a version that satisfies the requirement neuropod (from ludwig[full]) (from versions: none)
ERROR: No matching distribution found for neuropod (from ludwig[full])
Expected behavior
Successfully installed
Environment (please complete the following information):

OS: Win10
Python 3.8.3, 3.7.4
Ludwig assume latest

@Bandit253 thanks for noticing us about it, we'll look into it. My best guess is that the issue lies with neuropod and Win10, but I have to verify it.
As a temporary workaround, if you don't need neuropod specifically, i would suggest you install just ludwig and optionally all the subpackages that are useful for you usecase. neuropod is inclused in the serve subpackage at the moment, so if you don't install it you shouldn't be finding issues.
Let us know if this helped.

Thanks I will do that for now.


Check case of non-MS axes are all caps

Observed behaviour
https://github.com/agyeiarcher/Krspy-VF/issues/32
Expected behaviour
FB should ensure all axes tags are capitalized correctly; MS' axes are lowercase and others are caps.
Resources and exact process needed to replicate
https://docs.microsoft.com/en-us/typography/opentype/spec/dvaraxisreg#registered-axis-tags

From a GF perspective, we implement this by checking that the tags are valid according to the axisregistry. @davelab6, please reopen if you still want a check for non-GF uses.


Wrong Dialog focus when opened from a ListItem

Hello,
I have a List in which each ListItem contains a Dialog
When I click on a ListItem to open its Dialog, the focus stays on the ListItem, so I'm unable to close the Dialog by clicking on the background.
The only option I pass to the Dialog is autoScrollBodyContent={true}
Here is an example of the issue :

@jgoux : were you able to close the issue by any chance? Do let me know


feat: add weighted MerkleRoot/MessageId ISM factories

Description

Backward compatibility

Testing

Looks good but please add a changeset


mpfr: 4.1.1 -> 4.2.0

Changes: https://www.mpfr.org/mpfr-current/#changes While at it dropped upstreamed patch.
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Tested on my system and all direct reverse dependencies: arb basiliskii cgal cgal_4 cgal_5 cloudcompare csxcad ecl ecl_16_1_2 flint fplll fplll_20160331 gappa gcl gcl_2_6_13_pre gdb gecode gecode_6 giac giac-with-xcas glsurf gplates gretl jasmin-compiler kalker kcalc lean2 ledger libbytesize libmpc libqalculate meshlab mpfi openscad pltScheme polymake prusa-slicer racket racket-minimal racket_7_9 scryer-prolog sollya suitesparse suitesparse_5_3 super-slicer super-slicer-latest symengine wcalc wcpg.
Found no issues.


Add documentation for Service Fabric configuration source

in below Github issue Feature Request: Service Fabric configuration source #9,
Microsoft.ServiceFabric.AspNetCore.Configuration package is added and have provided support for asp.net core IConfigurationProvider, we also need to provide the document once the new Microsoft.ServiceFabric.AspNetCore.Configuration released.
I could contribute to this, or help the writer to author the document for this.

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

ID: 2639218d-5e54-aba0-ca0a-e53025b06d15
Version Independent ID: fec67d60-26a4-ba4c-45cf-f53c74281659
Content: Service communication with the ASP.NET Core
Content Source: articles/service-fabric/service-fabric-reliable-services-communication-aspnetcore.md
Service: service-fabric
GitHub Login: @vturecek
Microsoft Alias: vturecek

@chuanboz thanks for reaching out.
I will assign to the author for awareness. Also, since you are an FTE I suggest pinging @vturecek directly regarding this :)

the document is updated in:
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-communication-aspnetcore#service-fabric-configuration-provider


[Qt5] Update Qt latest to 5.14.1

follow up PR to #9860. Made latest default feature to test CI run.
Needs testing against ParaView PR #9960 to make sure that everything is linked in correctly. But if ParaView builds with it, it should generally work with everything
closes #10344
closes #10338

-- Downloading http://download.qt.io/official_releases/qt/5.14/5.14.1/submodules/qtcanvas3d-everywhere-src-5.14.1.tar.xz... Failed. Status: 22;"HTTP response code said error" CMake Error

no file qtcanvas3d-everywhere-src-5.14.1
http://download.qt.io/official_releases/qt/5.14/5.14.1/submodules/
latest
qtcanvas3d-everywhere-src-5.12.5

qtcanvas3d has been deprecated and removed since 5.13. It will be removed when vcpkg moves to 5.15 LTS

I found that there are some static libraries (such as Qt5UiTools) in qt. If these static libraries are referenced in debug mode, it will also add other qt release libraries that it depends on. Although it can be solved by setting Qt5_EXCLUDE_STATIC_DEPENDENCIES, I don't know if there is a better way.

@longhuan2018: Triplet ?; Linked Qt5 CMake target? Are you using [latest] feature or are you building 5.12.7? I am currently testing building paraview with this PR on windows.

@longhuan2018: Triplet ?; Linked Qt5 CMake target? Are you using [latest] feature or are you building 5.12.7? I am currently testing building paraview with this PR on windows.

I am using latest, and I also upgraded it to 5.14.1, just by modifying the hash value

@longhuan2018: Ok if you are not using this PR please don't mention linkage errors. This PR has additional patches to the Qt5XXXConfig.cmake.in to [latest] to fix the linkage. The reason you see those linkage problems is that _populate_UiTools_target_properties(DEBUG "Qt5UiToolsd.lib" "" FALSE) is called with the last argument being set to FALSE. This eliminates the required generator expression in the INTERFACE_LINK_PROPERTIES.

@longhuan2018: Ok if you are not using this PR please don't mention linkage errors. This PR has additional patches to the Qt5XXXConfig.cmake.in to [latest] to fix the linkage. The reason you see those linkage problems is that is called with the last argument being set to FALSE. This eliminates the required generator expression in the INTERFACE_LINK_PROPERTIES._populate_UiTools_target_properties(DEBUG "Qt5UiToolsd.lib" "" FALSE)

_populate_UiTools_target_properties

OK, then I will also use this PR to test my program

@longhuan2018 : Just remove the FATAL_ERROR and additional CI code add the end of the qt5-base portfile.cmake or you won't get far currently ;) (I require some files from ci check them for each platform once)

That's really hard work, thanks!

/azp run

/azp run

/azp run

Oh, this PR exists so long...

/azp run

/azp run

outdated 5.14.2 released


[Typescript] refactor save() for omitted fields

[Typescript] refactor save() for omitted fields
What
Improved the modularity of the field exclusion logic when saving config to disk.
Why
The current saving mechanism is too rigid

Stack created with Sapling. Best reviewed with ReviewStack.

#116
#113
#112
#111
-> #115

Testplan:

Loaded a config.
Verified Config has attribute filePath
Save() config. Showcase saved config does not have attribute filePath

https://github.com/lastmile-ai/aiconfig/assets/141073967/d00dca5c-ad9f-4a45-b452-f82b4f0d2917

Also side note, we should have a test for save that mocks fs and ensures writeFileSync is called with the correct contents (especially wrt removing outputs); that will also make it easier to ensure the default behaviour correctly removes any new fields that are added to the class that shouldn't be serialized


SelectField option_widget argument not used

The option_widget parameter to SelectField is not used by the built-in Select widget to render the choices as option elements. It appears to use its render_option class method regardless.

If nothing uses it, I think the option_widget parameter should be removed as unless I'm mistaken there's nothing else you can use other than <option> which is the default.

It's definitely used elsewhere. See RadioField for an example:
class RadioField(SelectField):
    widget = widgets.ListWidget(prefix_label=False)
    option_widget = widgets.RadioInput()

SelectField could use some cleanup, it's a bit circuitous right now.


Angle brackets in type statement cause confusing error message

Repro is with Zed commit 0c2f62f.
As an insider, I know the angle brackets don't belong in the type statement. But playing the role of a hacky user, I happened to do the following:
$ zq -version
Version: v1.8.1-49-g0c2f62fa

$ echo null | zq -z 'type foo=<string> yield "hi"' -
zq: JSON field "decls" in Go struct type "ast.Scope": JSON field "expr" in Go struct type "ast.ConstDecl": JSON field "value" in Go struct type "zed.TypeValue": JSON field "type" in Go struct type "zed.TypeDef": value of type "*zed.TypeValue" not assignable to type "zed.Type"

I'd instead have expected something like a syntax error.

Verified in Zed commit b58a6d7.
I've confirmed via binary search that this was fixed by the changes in #4996. Repeating the original repro, we now get a proper error message.
$ zq -version
Version: v1.12.0-36-gb58a6d7a

$ echo null | zq -z 'type foo=<string> yield "hi"' -
zq: error parsing Zed at column 10:
type foo=<string> yield "hi"
     === ^ ===

Thanks @mattnibs!


Add support for Tron

What changed? Why?
Issue: Tron chain intergration
Get block data; Transaction Receipts;
For now, I’ve ignored trace data due to the lack of a corresponding API. Later, I’ll try to supplement similar trace-like data using the TransactionInfo endpoint.
To support Tron(TRX), did following things:

Update parser.go and client.go to use Ethereum client and parser for Tron based on the reference from this Tron RPC API Document

Update the common.proto to add Blockchain: 57 and Network enums: 137

Add Tron configuration templates (copy from ethereum)

Add Tron configuration files

Add the client/ethereum/tron.go with EthereumNodeType_ALCHEMY_TRON skip Trace data.

Add the tron_native with EthereumNodeType_ALCHEMY_TRON skip Trace data.

Update ethereum_native.go to parse "0x0000000000000000" to 0

How did you test the change?

[ ] unit test
integration test
[ ] functional test
[ ] adhoc test (described below)

I get the real trace data of Tron after redeploied Tron Node ewith nabled vm.vmTrace config.
the trace data are json files existed inside the trace dir of Node, and each contract transaction got a file name with Tx address.
here is one of them with internal transactions https://github.com/PikaZ76/block-data/blob/main/tron_trace_blocks/85a65c910a9df8cb7738f3df5380e1f4459a8c5078872b3f222a2f473d8c1eae.json
I notice some issues for those trace files.

there very detail of call stacks in this trace data,
it's very disk consuming for those trace data when enable the vm.trace for Tron node.
(take 337G for only about 4,500 blocks)
Trace data is only generated after enabling vmTrace on the TronNode. Before that, it is impossible to get any historical trace data, even from official sources...

so It seems that the transactionInfo is actually more suitable, it's provide internalTransactions.
Since transactionInfo is a separate HTTP endpoint and not on the same port as the JSON-RPC interface, and it can't be directly configured in chainstorage.
So I deployed a proxy that aggregates the JSON-RPC and transactionInfo interfaces into one endpoint.
This way, chainstorage can access transactionInfo data seamlessly.
here is the schema of InternalTx:

hash: the hash value of the internal transaction
caller_address: caller address
transferTo_address: the calling contract address or the account address receiving TRX/TRC10 tokens
callValueInfo.callValue: the amount of TRX/TRC10 tokens transferred
callValueInfo.tokenId: TRC10 name or id of the transfer; when transferring TRX, this field is empty.
note: instruction type, such as call, create, suicide, freezeBalanceV2ForEnergy, freezeBalanceV2ForBandwidth, unfreezeBalanceV2ForBandwidth, etc.
rejected: Whether the internal transaction is executed failed, true means the execution failed.
extra: At present, it is mainly used to save voting information and record the voting SR and its number of votes in JSON format

should we store the internalTx by mapping it into EthereumTransactionFlattenedTrace like this:
{
	"hash": "3e2b8ca208f6c899afdc74b772a4504cdd6704bbeff6d34045351c9ad83f478d",
	"caller_address": "4158baea0b354f7b333b3b1563c849e979ae4e2002",
	"transferTo_address": "41f5a6eae2fb24b0bda6288e346982fc14e094c19a",
	"callValueInfo": [
		{
			"callValue": 405000000
		}
	],
	"note": "63616c6c"
}
->
{
	"type": "CALL",
	"from": "4158baea0b354f7b333b3b1563c849e979ae4e2002",
	"to": "41f5a6eae2fb24b0bda6288e346982fc14e094c19a",
	"value": "405000000"
}

or just keep it in origional schema?

should we store the internalTx by mapping it into EthereumTransactionFlattenedTrace like this:
...
or just keep it in origional schema?

map it to standard schema is preferred


feat: reset device add config flow

PR Description

cache login data
add remove cached login data step
add a simple skip login option
add async def check_cloud_login and check_cloud_key
reset add device step
disable v3 device add with v2/v1 protocol
force check device_id/device_protocol in finally step
all the error should be log in debug mode
to be done, code can be review via comments

Reason & Detail
Related issue
fix #X

Sorry to request changes, but I'm not a fan of a single PR with so many changes.

thanks, it's a fullly of the old feature, not one feature, all the old process has been droped, and  most of the feature bounds in this new process.
and every step has add with all the detail comments and why we do it now, old process without any comments and info why it to do that...
if there is any error, just refer to the comments, please fullly drop old mode and old codes.
we don't have any testcase in integration side, most of the current process only can be test by manual action, and I have manual tested/verified with 90% of current code changes, confirmed it works as expected flow.
if we want to split it with more PRs, we should  consider how to deploy it step by step..... each feature should combind one by one, also conside how to replace the old code step by step.
wish you have any good solution to deloy it step by step with old proces replace, and I don't want to waste time with old process.... so I just select a fresh new one.
could you help me to finish it with more PRs?  I can drop my current PR, sorry....
waitting for your feedback with the solution when we got a agreement.
there is too many auth failed github issue, we should release a new version to check and confirm it.


[Feature Request] SSH Support

In my opinion it would be fantastic if the app had the ability to change the code via SSH and then run it on a remote device/server via a dedicated terminal.

Please refer to #29


Add support for function call (response back) (message.role=tool)

Add support for function call (response back)

Currently there's no support for sending back the function call result to the model using the role=tool messages.
Using the native API (not openai), function tool calls don't have an identifier associated tool_call_id, this is present in the openai API, and is important to be available on both APIs.

[!IMPORTANT]
This ID is very when providing the result back to the model (in a chat history where the same function was invoked multiple times in a chat history with different results) for the model to reason about.

Broken image link.
Function call results can use role=tool if the template supports it, eg {{- else if eq .Role "tool" }} in the llama3.2 template.
The tool id would be nice to have, in practice I haven't found it an issue, probably because in my use cases, the completion contains only one or two tool calls.

Hi, any update on this?
I have probably the same issue, using default models (templates) provided with models by ollama.
Using the native API, role=tool response message are present in history, but multiple tried models (lama3.1, qwen2.5), are responding that they don't see tool response, when asked. Unless provided with comment as role=user, which should not be the correct way.
(Tested models are able to make valid tool calls)
Thanks in advance.


is this malware

bruh

@W1lcro to be quite frank. No. This is not malware. How can I tell, well the code is open to public view. If you are really that concerned that this is malware you can build the project yourself instead of downloading the pre-compiled binary in the releases.

Its not tho, lol. I Think you misunderstand something about what open source means


fix(shared-data): reduce 96chan pickup distance

Keeps the lifetime nice and long.
Numbers from hardware.

We don't need to update the drop tip value as well?

Nope, different stresses I guess


lesspipe: 2.06 -> 2.07

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/wofr06/lesspipe/releases.
meta.description for lesspipe is: A preprocessor for less
meta.homepage for lesspipe is: https://github.com/wofr06/lesspipe
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.07 with grep in /nix/store/gp441dswkghky14y9p3m8i37imcwpzrn-lesspipe-2.07
found 2.07 in filename of file in /nix/store/gp441dswkghky14y9p3m8i37imcwpzrn-lesspipe-2.07

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
lesspipe
tests.nixos-functions.nixos-test
tests.testers.nixosTest-example

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

lesspipe

Maintainer pings
cc @martijnvermaat for testing.

@NickCao I asked this on Matrix but I guess you skimmed past it, so I'll ask here:

how did you test [this]? do you have strings in your environment? a user is saying that lesspipe doesn't work bc they don't have strings in their environment

Fetch lesspipe from cachix
Open a clean bash shell
Follow the instructions in readme to set LESSOPEN
Use less to read /proc/config.gz
The output is plain text

I don't have strings in PATH, maybe my test just did not go through that code path.

Regarding our packaging of lesspipe, we are actually missing a HUGE number of program in the wrapper, whether intended or not, see https://github.com/wofr06/lesspipe#42-list-of-preprocessed-file-types. However supporting all of them would bloat the closure size beyond acceptance.


[DOCS] Fix Markdown in README.md

Issue Description
In README.md, the following 'Getting Started' link is not rendered correctly as there is a typo in the markdown.
Screenshots or Examples (if applicable)

Proposed Solution (optional)
We should fix the markdown so that the link is rendered correctly.
Code of Conduct

[X] I have checked the existing issues.
[X] I am willing to work on this issue (optional)

This is right; thank you for your feedback! Do you want to be assigned to this issue?

This is right; thank you for your feedback! Do you want to be assigned to this issue?

i would like to have it!!

I would love this opportunity to contribute to this issue and provide valuable output.

I would like to redesign the readme.md file and also fix the Getting Started link so that the users can get an updated look of readme.md file

Yeah sure, @FlorianJacta!

Thanks for assigning, @FlorianJacta!

Hey @FlorianJacta, I just found out that this issue has already been fixed via another PR (#1983).

It's okay, @FlorianJacta. 🙂


Remove duplicate code.

Result:
Fixes #170.

Codecov Report

Merging #172 into 5.3 will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                5.3     #172      +/-   ##
============================================
+ Coverage     63.51%   63.56%   +0.05%
- Complexity      582      583       +1
============================================
  Files           263      263
  Lines         11251    11250       -1
  Branches       1876     1876
============================================
+ Hits           7146     7151       +5
+ Misses         3136     3127       -9
- Partials        969      972       +3

Impacted Files
Coverage Δ
Complexity Δ

...rpc/message/bolt/BoltSendableResponseCallback.java
44.73% <ø> (+1.14%)
5 <0> (ø)
:arrow_down:

...pay/sofa/rpc/transport/ClientTransportFactory.java
59.09% <0%> (-4.55%)
0% <0%> (ø)

.../com/alipay/sofa/rpc/common/utils/CommonUtils.java
83.92% <0%> (ø)
0% <0%> (ø)
:arrow_down:

.../alipay/sofa/rpc/registry/local/LocalRegistry.java
57.83% <0%> (+0.6%)
26% <0%> (+1%)
:arrow_up:

...ava/com/alipay/sofa/rpc/config/RegistryConfig.java
36% <0%> (+1%)
0% <0%> (ø)
:arrow_down:

...ay/sofa/rpc/client/AllConnectConnectionHolder.java
52.51% <0%> (+1.67%)
0% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Sentry Profiling Integration doesn't work

This is the suggested configuration from the docs:
import * as Sentry from "@sentry/node";
// NOTE: @sentry/tracing should be imported before @sentry/profiling-node
import "@sentry/tracing";
import {ProfilingIntegration} from "@sentry/profiling-node";

Sentry.init({
  // ... SDK config
  integrations: [
    // add profiling integration
    new ProfilingIntegration()
  ]
  profilesSampleRate: 1.0,
});

This is my module configuration:
   SentryModule.forRoot({
      enabled: true,
      dsn: process.env.SENTRY_DSN,
      logLevels: ['debug'],
      debug: true,
      integrations: [new ProfilingIntegration()],
      // @ts-ignore
      profilesSampleRate: 1.0,
    }),

Profiling doesn't work and profilesSampleRate produces a type error.

This seems to be a problem with all integrations. I get type error since @nestjs version 9.2.1 and @sentry version 7.26.0.
Versions 9.1.6 and 7.17.2 work fine.
The problem is probably somewhere between NestJS -> ntegral -> Sentry.

Any news about that? I can confirm that the problem exists in 7.36.0 also.

@sentry/tracing not working either? Or it's the same package?

@sentry/tracing not working either? Or it's the same package?

According to the Sentry docs for NodeJS, tracing is already enabled: https://docs.sentry.io/platforms/node/performance/#enable-tracing

Has anyone managed to solve this issue?

Has anyone managed to solve this issue?

I end up using the plain @sentry package.
I forked a repository with a generic node implementation and develop this to support tracing.

It appears that SentryService gets initiated twice. And because of that Sentry.init gets called twice also.

A workaround:

Add fromFactory guard in sentry.service.ts constructor to initiate Sentry.

constructor(
    @Inject(SENTRY_MODULE_OPTIONS)
    readonly opts?: SentryModuleOptions,
    readonly fromFactory?: boolean
  ) {
    super();
   ...
   if (fromFactory) {  // <-- here
      Sentry.init(opts);
    }
  ...
}

Add it to the Service instantiation in forRootAsync/ forRoot in sentry-core.module.ts

public static forRootAsync(options: SentryModuleAsyncOptions): DynamicModule {
    const provider: Provider = {
      inject: [SENTRY_MODULE_OPTIONS],
      provide: SENTRY_TOKEN,
      useFactory: (options: SentryModuleOptions) =>
        new SentryService(options, true), // <-- here
    };
   ...
}

Has anyone managed to solve this issue?

@AdamGerthel @StPaulis  check my workaround above.


Create Ian's Final Project Post

Nice work!  A truly strange game :)  Thanks for a great semester; more comments to follow via email.


[Dropdown Menu] 'enter' keyboard press does not follow link

How can we reproduce this bug?

http://foundation.zurb.com/sites/docs/dropdown-menu.html
Use keyboard to 'tab' to first example dropdown menu (or any example dropdown menu).
Press 'enter' on a menu item

What did you expect to happen?
Considering the example menus use empty links (href="#"), if the link was activated, the page would jump to the top and "#" would be appended to the url. This can be confirmed by using the mouse instead of the keyboard. Issue is with keyboard only, mouse clicks are working as expected.
What happened instead?
Nothing. Links are not activated.
Test case
The topbar for the Zurb Foundation site shares this same issue. Any of the dropdown menus, Learn, Develop, Support, Docs, will reproduce this same issue. Tab to the dropdown menu, and attempt to open any of the submenu items by pressing "enter".

I already changed the links for the Drilldown Menu here #8477. I think we should do this for all links to ensure that this works well.

Hi, this is not resolved, but has been closed for over 2 years. I am unable to open the link of any dropdown menu item which contains a submenu, only trigger the submenu. As mentioned above, this affects even the Zurb website and all the dropdown menu examples in the documentation.
Requesting this be re-opened.  Thanks.

Hi @totallyspun,
please open a new issue, fill out the issue template and also reference this issue here.

Just did a quick test, it's working fine for me. if you're still having issues, please follow Daniel's advice above and open a new issue so we can get this fixed.

I played around more and was able to follow the parent link with screen reader, but not simple keyboard nav without opening in new tab. If it was working for you, what is the method to follow link with simple keyboard command?

Sorry, I misunderstood.
So you want a dropdown menu where the top-level item is also opens as a link?
Unfortunately, that isn't currently supported. But I think we need to make note of that in the docs. For the dropdown menu to be accessible, the top level dropdown menus need to be empty links.
Any chance you want to take a stab at submitting a doc update PR?


add initial marshmallow support

Basic support for marshmallow schemas https://marshmallow.readthedocs.io/en/stable/
It would be nice if we could override the default renderer for these types of classes to show a table instead of the header style renderer?

I would like to show inherited fields as well, however enabling inherited_members also shows all the methods inherited from the base marshmallow.Schema class. I added a blacklist to remove these methods / attributes, but there may be a cleaner way to deal with this that i am not seeing

Hi @stufisher, thanks a lot for your contributions, this is really appreciated :slightly_smiling_face:
I'll review now!

Thanks for reviewing, ill get back to you shortly with updates. Any idea on my second question? I guess ill open an mkdocstrings ticket

Sorry for the delays, think ive addressed the things youve mentioned :)

Hi again, no problem about the delays, I myself am having a hard time finding time/motivation to work on my open source projects in the evenings, after work :slightly_smiling_face:  Thank you for getting back on this :slightly_smiling_face:
I think this is good now, I'll squash and merge!


API versioning

Background
There have been no breaking changes since the first version was released, so this hasn't come up until now. I believe the best solution to #206 will require a breaking change to the API. That being said, when we make breaking changes to the API we'd like to allow for clients to use the older versions of the API so they have time to upgrade their integration to the new version. So we need a way to let the API determine which version is being requested and then return the response with the correct logic for that particular version.
Description
Requests should be able to include an X-Api-Version header specifying the version of the API the request is meant for. The API should then execute the logic for that particular API version and return the specific response.
Acceptance Criteria
The API should accept an X-Api-Version header.
There should be a standardized way to put certain logic behind a newer API version.
The API should respond with an accurate version number for which logic was executed. Right now I think it just responds with 1.0 no matter what.

I'm will to take a stab at this.

@aaron-suarez; to clarify things, the APIs you want to version are all defined in /app/api/route.py correct?

Yeah, but more generally, any response from our API is going to have a version along with it, which currently is sort of hard coded here https://github.com/OperationCode/resources_api/blob/master/app/init.py#L12
We want that instead to be variable, defaulting to the latest version, but if someone requests a specific API version we should support that.

Cool, thanks for that additional information. I'm currently thinking of adding a new decorator that will take in some configuration specifying a mapping of versions to functions that will generate outputs. It would wrap the top level blueprint route and its parameter list will receive the generated output and the route's body can send it out. I'll obviously also have to think about how to handle outputting the version as well.
Does that sound good in theory?
Also, looking at the file you linked, I can't help but notice that you have a base URI for the blueprint that references a version number (/app/v1). Will it be confusing to have a separate version number specified in a header from what is already specified in the path? Also, what value does the path specified version number provide if it is not getting used to indicate new APIs? Are these going to refer to 2 separate versions (like one version for the whole solution and another specific to each endpoint?)

For the first part: I'm fine exploring the idea of a decorator, that could probably work. But I don't think it even needs to be that much overhead. I think that it would be more like if statements, where a version is mapped to some constant that you check against, so it would look like:
def some_route():
     if api_version_1_1:
        do_something_for_1_1()
    else:
        do_the_thing_for_1_0()

and then of course we'd need to return "apiVersion": "1.1" in the JSON response if it goes the api_version_1_1 route.
For the second part: the idea is that if we have to bump a major version (e.g., 2.0) we're probably going to rewrite a bunch of business logic, so we'll just create a new set of folders for that version. I'm less concerned about what will happen when we hit a major version update and more concerned about allowing for minor version updates, like my 1.1 example above. It's not exactly semver, a version is only bumped when there are breaking changes. A major version is only bumped when it's basically a complete rewrite. I'd be willing to talk about other approaches, but it's not like we're distributing software for people to download and run on their machines. If we have a patch level change to make, we just patch it and we patch it for all versions. If we have a breaking change, we increment the minor version to separate it from the versions that came before.
Does that make sense?

Yes, that does make sense. Hopefully the final question, are you wanting to have this implemented on each route, or would you like for me to just implement it on a representative route, as I’m assuming most routes do not require versioning (at least not yet?)

I think the acceptance criteria for this will be creating a centralized place where we can define such constants as api_version_1_1, a way to parse the incoming X-Api-Version header and respond to it, and ensuring we return the correct API version in the json response. Like you said, all of the routes are on 1.0 right now, there is no branching logic for 1.1

@aaron-suarez; I've posted up a PR. The only thing I didn't include was a centralized place to define constants, though I did setup a default version number constant in a new versioned module. If you are also wanting to be able to specify valid version ranges or something, I propose doing that in a separate PR.


contracts: calldata encryption function (Solidity)

Closes: #436
Implements calldata encryption to create encrypted transactions from contracts on Sapphire.
This also updates Cipher TS to accept an optional nonce parameter, this means we can do easier deterministic tests to verify the Solidity implementation matches the Typescript implementation.

Running the test against localnet fails for me
  1) CalldataEncryption
       testEncryptCallData:

      AssertionError: expected '0xa264626f6479a462706b58204a0269de680…' to equal '0xa264626f6479a462706b58204a0269de680…'
      + expected - actual

      -0xa264626f6479a462706b58204a0269de680edc05553943543d70c5df9e23f6af53381eded9641b5d08df7b2d646461746158184bf966b9e87a715c26b2428996c85589e1ba7e2c060487206565706f636800656e6f6e63654fb9cb3f82f8a608902dcb321ae611a766666f726d617401
      +0xa264626f6479a462706b58204a0269de680edc05553943543d70c5df9e23f6af53381eded9641b5d08df7b2d64646174615818cbca0d4444a619c839a845d2b045ccf4437a861047e59b5f6565706f636800656e6f6e63654f0d0922c9861097bab82a5a77b15d8666666f726d617401

       at Context.<anonymous> (test/calldata.spec.ts:50:22)

That could happen if you don't build the clients/js package, the solidity tests require repeatability so I had to modify the client to pass a custom nonce.
If the clients/js package isn't rebuilt, the solidity tests will use the last build you did which will generate a nonce every time and ignore the one passed in.


Use CSS Font loading if It can use.

This can avoid Chromium's bug, and can avoid 'Cannot load GameFont' in poor connection.
I'll make PR and notice here.

see https://github.com/rpgtkoolmv/corescript/pull/23

Finished!!


[BAD-297] - Hadoop file output fails append to file

UI changes  - enable extension field in case of using filename from field

related https://github.com/pentaho/big-data-plugin/pull/571

@brosander @deinspanjer Could you please take a look? It`s according the first point of the http://jira.pentaho.com/browse/BAD-297 :

In tab File, when the "Accept filename from field" is selected, the "Extension" field is greyed out indicating it is not used. However it still gets used.
So It was decided to enable for editing extension field (as it was and still is being used) to not break somebody`s existing ktrs.


fix for retries in #858

This should fix the retry infinite loop when a race condition happens while updating the UUID of a checker pod on the khcheck resource.

This is in testing in our test cluster, but is looking good and expected to merge soon.


[BUG] Params (min-price, max-price, order) added to URL

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When clicking in Top-Navigation and waiting a bit you will get this URL for example:
http://localhost:3000/Cooking-pleasure-Provence/?min-price=3&max-price=350&order=name-asc
Sometimes when you click fast on a product these params are added to the product detail page URL.
We need these params for sorting and filtering but I guess the default params should not be added to the URL.
Expected Behavior
URL should not change when no filter or sort is set.
Expected URL will look and stay like this:
http://localhost:3000/Cooking-pleasure-Provence/The expected
Steps To Reproduce

Click some Link from Top-Navigation
Wait until the params are added to the URL

Environment
- OS:
- Node:
- pnpm:

Anything else?
No response

Looks like these files are the reason for that:
packages/cms-base/components/listing-filters/SwFilterPrice.vue
and
templates/vue-demo-store/components/listing-filters/ListingFiltersPrice.vue
A watch is used two times:
//watch(() => prices.max, debounceMaxPriceUpdate);
and
//watch(() => prices.min, debounceMinPriceUpdate);


Preserving viewBox in rollup

I would like to preserve the viewbox attribute, how should I add this in config in the rollup.

Hey @harshalpatel91, I came here for the same answer and found it in another issue here:
https://github.com/gregberge/svgr/issues/456


[Deploy]Cannot deploy it on github

Describe the bug
I'm using your repo as a template, and adding my stuffs on it.
When deployed to github using github default Jekyll action, the page is really weird. It turns out that I have trouble getting main.css and a lot of other files.
In fact, this behavior is really like what I saw using docker to deploy it on my server. (where it goes something like <IP_ADDRESS> is not valid). So I wonder if there is a deploy script that I've missed?
To Reproduce
Steps to reproduce the behavior:

You can simply fork this repo, and deploy it using default action.

Expected behavior
The result should look like my https://yuanze.me/.
Screenshots
You can check my https://yuanze.me/ or https://yuanze1024.github.io/academicpages/.
Desktop (please complete the following information):

OS: MacOS
Browser safari
Version does not matter

Additional context
Please ask me if more details are needed to fix it.

It looks like your configuration is incorrect - in your _config.yml file you should have a URL that is something like [your GitHub username].github.io. Aliasing to a different domain is possible, but it's best to set that up after everything has been setup correctly.


conda install fail

I tried installing nanopolish using conda:
apt-get install -y libhdf5-dev
conda install -y nanopolish

When starting nanopolish index, it errs out w/:
nanopolish: error while loading shared libraries: libhdf5.so.10: cannot open shared object file: No such file or directory

What might I be doing wrong?
Thank you.

Sorry but I don't maintain the conda package, you'll have to ask the conda devs for help.

I see thank you.


Barong and External Authentication Provider

Hello,
Is there any plan to support External authentication like Google or Github on Barong? or is there any current solution to make it possible sign in user using their Google account?

Hello, @counos . It not in the short time plans currently