Unexpected ignore coloring of nested file listed as a top level ignore only

Just noticed this - I have "gradle.properties" in my .gitignore, which is a root level file and not controlled by Git in this case. However I also have a template version of the file in a nested directory that is in Git. The plugin marks the nested version as ignored, yet Git reports it as changed (which is what I expect - in this case I have a pending change in it). I would think the nested gradle.properties at this point should be highlighted in blue, which it becomes if I take out the entry in the .gitignore.
Example:

Incidentally the .gitignore inside the templates directory naturally is itself a template and doesn't have a gradle.properties entry in it.
I'm not entirely sure how to get gradle.properties at any location gitignored just to see what happens, but then I don't need that either so that's ok :-)

@Cervator I think, it's strongly connected to the issue #105  - it will reset the ignore scope if nested repository appears - so it will not ignore
templates/gradle.properties

file as well.
If I'll prepare some RC build - could you test it and confirm taht it works well ?

Sure, just let me know how :-)

Great. It's available here: https://github.com/hsz/idea-gitignore/releases/tag/v1.1.2-RC

Good news / bad news. With that RC #105 appears fixed, but the gradle.properties in a subdir is still being ignored. Just to clarify this is not a nested Git root, just a plain ole boring subdir :-)

In that screenshot Core and CoreSampleGameplay are in the root repo and Sample is its own nested root. So that looks right.
For reference the parent repo with the gradle.properties is https://github.com/MovingBlocks/Terasology (the copy at the root was manually duplicated from the template, no magic involved)
For completeness here's the content of the template .gitignore (which shouldn't be in play at all since it is not in a Git root, and it doesn't have any related entries)
# Modules get a copy of build.gradle as they are not allowed to have their own (for build security / sandboxing)
build.gradle

# IntelliJ
*.iml

# Eclipse
.checkstyle
.classpath
.project
.settings
bin/
build/

With following command:
find . | git check-ignore --verbose --no-index --stdin

you can check what files are mathed by the .gitignore rules in your repository.
As I can see, the templates/gradle.properties file was added to the repository before ignoring gradle.properties rule or added with --force switch.
Currently, VCS files index is not respected by the plugin. It's using only the rules from ignore files.

Ooohh. So you mean that file would normally have been ignored, but since it already exists in the repo what git returns on the command line clashes with how it ideally should work?
Yeah it is entirely possible if not probable that entry was added to the ignore later. My apologies for the inconvenience in that case :-)

Fix has ben released just right now with v1.1.2

Thanks @hsz ! It works.


[Bug] Resizing in tmux pane errors

Resizing in a tmux pane gives an error message:
[Neo-tree ERROR] Error in event handler for event vim_resized[table: 0x7fcde9dc7048]: ...q/.local/share/nvim/lazy/nui.nvim/lua/nui/utils/init.lua:23: Invalid window id: 1027

Could you elaborate more (perhaps what you did to produce the error or your configs)?

@YodaEmbedding
I can open Neo-tree with :Neotree and then resize the tmux pane it is in and I do not receive any vim errors. I performed a resize both horizontally and vertically, with mouse and keyboard. Please provide a minimal configuration to recreate this error.

Not OP, but I can reliably reproduce it too with neo-tree float lazy loaded.

Minimal config
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)

require("lazy").setup({
  {
    "nvim-neo-tree/neo-tree.nvim",
    branch = "v2.x",
    dependencies = {
      "nvim-lua/plenary.nvim",
      "nvim-tree/nvim-web-devicons",
      "MunifTanjim/nui.nvim",
    },
    keys = {
      { "<leader>e", "<cmd>Neotree float<cr>", desc = "NeoTree" },
    }
  }
})

Steps to reproduce

Open Neovim
Open a split (either :split or :vsplit)
Open neo-tree float (<leader>e in my mapping)
Close neo-tree float
Close one of the split
Resize the terminal

Thanks a lot! I have been able to reproduce the error. This seems to be a bug with Neotree float, when the nvim window is resized (does not need to be inside a tmux session). I will have a look into this.


Provider SSM seems limited to 10 parameters per map

With teller 2.0.5, when i create a provider SSM with one map like this:
  ssm:
    kind: ssm
    maps:
    - id: nonprod
      path: /project

And i put more than 10 parameters prefixed by /project in SSM parameter store
teller show and teller sh return only 10 parameters.
It should return all parameters, shouldn't it ?

yes, looks like a limit in pagination, we will resolve it in next version

should be resolved with 2.0.6


Add default celery metrics and logging using celery signals

Adds default celery metrics for tasks that succeed, fail, are revoked (expired before started), and new pending tasks
Utilizes celery results backend if available to temporarily store results of celery tasks. Returning log_data from celery tasks wherever possible to make use of this mechanism
Ran black on this python file to reformat

Coverage decreased (-0.2%) to 58.51% when pulling 11b15e7e234e0d5b7b494e35697d2ced5fbb5972 on celery_metrics into 37f4b4c2a60dbc76442449273346b096464497e8 on master.


Update mockito-core to 3.6.28

Updates org.mockito:mockito-core from 3.3.3 to 3.6.28.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito", artifactId = "mockito-core" } ]

labels: test-library-update, semver-minor

Superseded by #88.


Add NBodySimulator benchmarks

[x] Low level benchmarks

[x] Gravitational potential
[x] Coulomb potential
[x] Magnetic dipole
[x] Lenard Jones potential
[x] Harmonic bond potential
[x] Valence angle potential

[ ] High level benchmarks

[x] Liquid argon simulation
[ ] Water simulation

The low level part, statistical benchmarks should test the acceleration functions in order to help catch possible performance regressions and provide a baseline for future optimizations.
For the high level simulation I think work-precision-like diagrams would be of interest, focusing on

time vs energy error
number of steps vs energy error
for various integrators.

I marked this as ready by mistake.
It is almost ready, but I was wondering what integrators are most relevant for the list. Currently the first benchmarks runs without problems, but takes a few hours. The second hangs for some yet unknown reason at τ=3.1622776601683796e-14.

I'd try a smattering of symplectic methods, DPRKNs, and then throw Tsit5, Vern7, and Vern9 in there for good measure

I addressed the previously mentioned problems and calibrated the timestep by computing a cost factor that should take into account the cost per timestep between between different integrators.
What I noticed now is that there are some (significant I'd say) differences between the weaved files, namely the energy error doesn't look the same between the runs. In the html file we have

and

while in the markdown file

and

and in the pdf

and

I'm not sure how to explain these differences. The weaving process happens on the same machine in all cases and with the same code.

The initial conditions are not exactly the same, since velocities are random
https://github.com/SciML/NBodySimulator.jl/blob/172b046d8f3cfd0737df294fb54481b0bc95e754/src/bodies.jl#L35

The variation is due to the computation of the cost (which depends on runtime) at each run. The best way to solve this is to compute the cost once and then hardcode them.

With fixed time-step cost, here are some new results

McAte2 seems to consistently perform better than other solvers. I also noticed that it is the single solver with a lower cost than VelocityVerlet and I was wondering if this is relative to it's performance relative to VelocityVerlet.
In the energy error history I noticed that high order solvers then to have a higher energy error (and slightly lower runtimes) and I'm not sure if this indicates problems with the cost tuning.

With the adaptive solvers I also tried to apply the same line of reasoning in regards to cost tuning, but I still get the same behavior of constant runtime.

Comparing to the symplectic solvers it seems that DPRKN6 and DPRKN8 are quite competitive.

the errors on the fixed time step ones still look fairly random. I'm surprised

I think we can leave the water simulation for later. This should hopefully produce better results. I'll also start a local run to check again if everything is ok. There are also some long time benchmarks included, but commented out (with t=100). From what I understand form the literature, we'd need something with ~10^8 Verlet timesteps for talking about long term, so maybe a longer runtime is needed. I did not test that due to how long it would take. If you want, I can enable them, but the runtimes could well be over a week or more (since everything is run 3 times).

It would be fine to get that setup as a separate file that we don't run often.


FUSETOOLS2-827 - Fix convert to list of properties for path using / not

as path options separator

just wondering what happens to the aws2-s3 prefix because that is gone regarding the animated gif?

just wondering what happens to the aws2-s3 prefix because that is gone regarding the animated gif?

the aws2-s3 prefix is redundant for Camel kafka Connector, the connector to use is determined by the connector.class property


Add sklearn installer

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

Project coverage is 100.00%. Comparing base (5539dbc) to head (2afffbc).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #174   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          110       113    +3
  Branches         9         9
=========================================
+ Hits           110       113    +3

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


Debian Image

Most of Docker Official Images are based on Debian or Alpine while this Kong image is based on CentOS.
Is there any specific reason not to use Debian?

We have an Alpine image (kong:0.11-alpine at the time of this writing), which is a preview but seems to be working well in our tests. So please use it with caution and report any bugs.


feat: Added full-width prop for buttons

Description
Added fullWidth property for normal, primary and link buttons.
AWSUI-19884
How has this been tested?
New unit tests and permutations

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Will there be updated "Usage" guidelines for this property, i.e. when it should be used from a design point of view?

Will there be updated "Usage" guidelines for this property, i.e. when it should be used from a design point of view?

Yes, there will be a new guideline added. It is under preparation.

Will there be updated "Usage" guidelines for this property, i.e. when it should be used from a design point of view?

Yes, there will be a new guideline added. It is under preparation.

Will there be updated "Usage" guidelines for this property, i.e. when it should be used from a design point of view?

Yes, there will be a new guideline added. It is under preparation.

Will there be updated "Usage" guidelines for this property, i.e. when it should be used from a design point of view?

Yes, there will be a new guideline added. It is under preparation.


cannot hide bottom navigation

I use this code when load this PDF viewer plugin,
PDFViewer(document: document, showNavigation: false,))
But the result is the screen not loading the PDF, and only the floating center button appear (which should not appear) at the top below appBar.

line 143 in lib/src/viewer.dart:
bottomNavigationBar: (widget.showNavigation || widget.document.count > 1)
should be
bottomNavigationBar: (widget.showNavigation && widget.document.count > 1)


refactor Tailwind class as delegate and not root of component hierarchy

The current inheritance tree for the components in the htmlcomponents module  has "Tailwind" at it's root:

IMHO it would be better to use a delegation pattern to allow other css styles then Tailwind to be adopted. The name of the class should be more oriented to the CSS/Class behavior that is the purpose of the class. The current tw_dict could be loaded from an external configuration file instead of being part of the source code.

see #685


mandatory: The map must be closed/surrounded by walls, if not the program must return an error.

◦ The map must be closed/surrounded by walls, if not the program must return
an error.

Solucionado em:
https://github.com/tonnytg/42_cub3d/blob/main/src/map/map_check.c


Runtime config can't be removed.

When I was still learning bosh, I was messing with things, and accidently loaded a runtime-config (meaning to update my cloud-config instead). I realized my mistake and went to fix it, but there is no option to remove a runtime-config, and you can't submit an empty one. So I had to add something to it, so I put in a harmless release. No real damage done, but there should be an option to completely clear runtime-config, or runtime-config should be able to be empty.

Agreed. We can relax validation constraints to allow empty file.

This can now be achieved by running bosh delete-config.


Add whatsapp icon

Hi,
thanks a lot, great package.
Is it possible to add a new icon, whatsapp?
https://www.whatsappbrand.com/
Thanks,
Amir.

I opened a pr: https://github.com/jaketrent/react-social-icons/pull/17

It's there now.  Thanks all.  Closing.


Public proxy interface improvements.

I want the public interface to be organized and self-documented.

Totally the least practically built interface, ever, but I think it is at least semi-cool to use. Still undecided on it.


Call to contract state fails on generated function binding

Which packages are impacted by your issue?
@graphprotocol/graph-ts
Describe the issue
Hi guys! I just recently ran into the following error:
/Users/vargaelod/taraxa/taraxa-platform/packages/dpos-subgraph/abis/Dpos.json
The ABI of the contract is attached and used in the codegen. Latest version for the dependency.
However, whenever I try to call a view method like:
function getValidatorInfoFromContract(
  validator: Address,
  event: ethereum.Event
): ValidatorBasicInfo {
  let basicInfo = ValidatorBasicInfo.load(validator.toHexString());
  if (!basicInfo) {
    basicInfo = new ValidatorBasicInfo(validator.toHexString());
  }

  const validatorAddress = validator.toHexString();
  const dpos = Dpos.bind(event.address);

  if (validatorAddress) {
    const chainData = dpos.getValidator(validator);

    basicInfo.commission = chainData.commission;
    basicInfo.commissionReward = chainData.commission_reward;
    basicInfo.description = chainData.description;
    basicInfo.totalStake = chainData.total_stake;
    basicInfo.lastCommissionChange = chainData.last_commission_change;
    basicInfo.owner = chainData.owner.toHexString();
    basicInfo.endpoint = chainData.endpoint;
    basicInfo.save();
  }
  return basicInfo;
}

The calls fail with:  RPC error: Error { code: InvalidParams, message: “INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised”, data: None }
Reproduction
https://github.com/Taraxa-project/taraxa-platform/tree/feature/add-subgraph-for-dpos/packages/dpos-subgraph
Steps to Reproduce the Bug or Issue

Build
Start your local node connected to mainnet:https://rpc.devnet.taraxa.io
create-local
deploy-local

Expected behavior
As a user, I expect the handler to be able to call the view function, return the data and fill in the entity for the indexing database.
Screenshots or Videos
No response
Platform

OS: [macOS]
NodeJS: [v16.10.0]
"@graphprotocol/graph-cli": "0.42.4"
"@graphprotocol/graph-ts": "0.29.3"

Subgraph Manifest
specVersion: 0.0.1
description: Dpos Contract indexing for Taraxa
schema:
file: ./schema.graphql
dataSources:

kind: ethereum
name: Dpos
network: mainnet
source:
address: "0x00000000000000000000000000000000000000fe"
abi: Dpos
mapping:
kind: ethereum/events
apiVersion: 0.0.6
language: wasm/assemblyscript
entities:
- ValidatorBasicInfo
- ValidatorData
- UndelegateRequest
- DelegatorInfo
- DelegationData
- UndelegationData
- CommissionRewardsClaimedEvent
- CommissionSetEvent
- DelegatedEvent
- RedelegatedEvent
- RewardsClaimedEvent
- UndelegateCanceledEvent
- UndelegateConfirmedEvent
- UndelegatedEvent
- ValidatorInfoSetEvent
- ValidatorRegisteredEvent
abis:
- name: Dpos
file: ./abis/Dpos.json
eventHandlers:
- event: CommissionRewardsClaimed(indexed address,indexed address)
handler: handleCommissionRewardsClaimed
- event: CommissionSet(indexed address,uint16)
handler: handleCommissionSet
- event: Delegated(indexed address,indexed address,uint256)
handler: handleDelegated
- event: Redelegated(indexed address,indexed address,indexed address,uint256)
handler: handleRedelegated
- event: RewardsClaimed(indexed address,indexed address)
handler: handleRewardsClaimed
- event: UndelegateCanceled(indexed address,indexed address,uint256)
handler: handleUndelegateCanceled
- event: UndelegateConfirmed(indexed address,indexed address,uint256)
handler: handleUndelegateConfirmed
- event: Undelegated(indexed address,indexed address,uint256)
handler: handleUndelegated
- event: ValidatorInfoSet(indexed address)
handler: handleValidatorInfoSet
- event: ValidatorRegistered(indexed address)
handler: handleValidatorRegistered
file: ./src/mapping.ts

Subgraph GraphQL Schema
type ValidatorBasicInfo @entity(immutable: false) {
id: ID!
totalStake: BigInt!
commissionReward: BigInt!
commission: Int!
lastCommissionChange: BigInt!
owner: String!
description: String!
endpoint: String!
}
type ValidatorData @entity(immutable: false) {
id: ID!
account: String!
info: ValidatorBasicInfo!
delegations: [DelegationData!]!
undelegations: [UndelegationData!]!
}
type DelegationData @entity(immutable: false) {
id: ID!
account: String!
delegator: DelegatorInfo!
validator: ValidatorData!
}
type UndelegationData @entity(immutable: false) {
id: ID!
stake: BigInt!
block: BigInt!
validator: ValidatorData!
}
type UndelegateRequest @entity(immutable: false) {
id: ID!
eligibleBlockNum: BigInt!
amount: BigInt!
}
type DelegatorInfo @entity(immutable: false) {
id: ID!
stake: BigInt!
rewards: BigInt!
}
type DelegatedEvent @entity(immutable: true) {
id: ID!
delegator: String!
validator: String!
amount: BigInt!
}
type UndelegatedEvent @entity(immutable: true) {
id: ID!
delegator: String!
validator: String!
amount: BigInt!
}
type UndelegateConfirmedEvent @entity(immutable: true) {
id: ID!
delegator: String!
validator: String!
amount: BigInt!
}
type UndelegateCanceledEvent @entity(immutable: true) {
id: ID!
delegator: String!
validator: String!
amount: BigInt!
}
type RedelegatedEvent @entity(immutable: true) {
id: ID!
delegator: String!
from: String!
to: String!
amount: BigInt!
}
type RewardsClaimedEvent @entity(immutable: true) {
id: ID!
account: String!
validator: String!
}
type CommissionRewardsClaimedEvent @entity(immutable: true) {
id: ID!
account: String!
validator: String!
}
type CommissionSetEvent @entity(immutable: true) {
id: ID!
validator: String!
commission: Int!
}
type ValidatorRegisteredEvent @entity(immutable: true) {
id: ID!
validator: String!
}
type ValidatorInfoSetEvent @entity(immutable: true) {
id: ID!
validator: String!
}
Additional context
No response

Additional info - using this example via ethers everything works as intended:
const contract = new ethers.Contract(dposAddress, Dpos, ethers.provider.getSigner(0));
  const encoded = contract.interface.encodeFunctionData("getValidator", ["0x780fe8b2226cf212c55635de399ee4c2a860810c"]);
  console.log(encoded);
  const call = ethers.provider.call({
    to: dposAddress,
    data: encoded,
  });
  const result = await call;
  const decoded = contract.interface.decodeFunctionResult("getValidator", result);

  console.log(decoded);

hey @VargaElod23 - I don't know if your null check if (validatorAddress) will prevent calling when the validator is null, and it looks like the RPC error is complaining that validator isn't a valid name / type. Closing for now, you can find more active support in the Graph discord, please re-open if you believe this is a bug in Graph Node

Hi @azf20 . I quadruple-checked and the constraints are fine, in fact, there's no handler where the validator isn't a valid Ethereum address. I also added the relevant ABI and you can see that the naming is exactly that + interface can be accessed here. I strongly believe this is an error either in the codegen or in the Node itself.

Yes, it does, at least for the specified RPC endpoint

Why are you running with specVersion 0.0.1, could you try running with 0.0.5?

Sure, give me a sec

graph-graph-node-1  | Mar 14 14:52:39.725 DEBG eth_call, data: 1904bb2e000000000000000000000000780fe8b2226cf212c55635de399ee4c2a860810c, address:<PHONE_NUMBER>0000000000000000000000000000fe, sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:39.878 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #1) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:40.023 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #2) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:40.164 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #3) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:40.305 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #4) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:40.456 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #5) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:40.619 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #6) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:40.768 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #7) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:40.956 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #8) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:41.119 DEBG Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #9) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:41.311 WARN Trying again after eth_call RPC call for block #1689 (60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4) failed (attempt #10) with result Err(Web3Error(Rpc(Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }))), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:41.334 INFO Done processing trigger, gas_used: 0, data_source: Dpos, handler: handleRewardsClaimed, total_ms: 1694, transaction: 0xcd7b…1d6c, address: 0x0000…00fe, signature: RewardsClaimed(indexed address,indexed address), sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:41.337 INFO Possible reorg detected, retrying, error: failed to process trigger: block #1689 (0x60ef…21e4), transaction cd7bbd9cfd89c46a0c3b07b8d7de8bb41789216bda18e8e8053fc6558ed71d6c: Ethereum node returned an error when calling function "getValidator" of contract "Dpos": RPC error: Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised", data: None }
graph-graph-node-1  | wasm backtrace:
graph-graph-node-1  |     0: 0x3594 - <unknown>!src/mapping/getValidatorInfoFromContract

graph-graph-node-1  |     1: 0x39f3 - <unknown>!src/mapping/enforceValidatorDataExists

graph-graph-node-1  |     2: 0x5be0 - <unknown>!src/mapping/handleRewardsClaimed

graph-graph-node-1  | , block_hash: 0x60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4, block_number: 1689, sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:41.346 DEBG Starting or restarting subgraph, sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:41.346 DEBG subscribing to chain head updates, sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: BlockStream

graph-graph-node-1  | Mar 14 14:52:41.485 DEBG Starting block stream, sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

graph-graph-node-1  | Mar 14 14:52:41.500 DEBG Processing 30 triggers, sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: BlockStream

graph-graph-node-1  | Mar 14 14:52:41.500 DEBG 30 candidate triggers in this block, block_hash: 0x60ef0cb669d0f7145066f0d232822f58f5c4d4ca62d00c4858d33e4c878521e4, block_number: 1689, sgd: 1, subgraph_id: QmWiP3Sfr6Pxe6hm2XZDxQRioCgeWCxQax7efzckx6kUoJ, component: SubgraphInstanceManager

Strange thing is that curl -X POST --data '{"jsonrpc":"2.0","method":"eth_call","params":[{"to":"0x00000000000000000000000000000000000000FE", "data":"1904bb2e000000000000000000000000780fe8b2226cf212c55635de399ee4c2a860810c"},"latest"],"id":1}' https://rpc.devnet.taraxa.io works like a charm

Yup it seems everything works well from our RPC side @azf20 , the only place the problem can be coming from is the data pinning on the RPC call, it seems.

Found the source of the errors in our RPC interface. Thanks @azf20 !


XIgnite quote service has expired

account and token for use of XIgnote service has expired.
We shouldn't really be using services that we need to register for, or that there are expiration dates or low threshold limits of use.
Need to add to the docs on how to create account and change token for now, but look at using different service - specially now that we have yahoo quotes as well.

Is anyone coming up against this issue?

yup.   I've tried signing up for a trial but it's not letting me even get quotes for the trial.

Instead of XIgnite can we use something like this http://www.google.com/finance/info?q=NASDAQ%3aGOOG

yes we do need to get rid of xignite service. we have marketitondemand and yahoo. is there documentation on the google one?


Add verification_value to example usage

I couldn't purchase if verification_value was blank.
I think the example is better if we'll add verigication_value.

Thanks!

Thanks!

@girasquid Thank you for merging :smile:


test: move to JUnit 5

Description
Migrate tests to JUnit 5

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 4.1.0-move-to-junit5-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 4.1.0-alpha.2 :tada:
The release is available on:

4.1.0-alpha.2
GitHub release

Your semantic-release bot :package::rocket:


Drastic not saving in-game or save states

Hello.  I'm running ArkOS 1.6 on my RG351M. I've noticed that Drastic is saving my configuration options ie; frameskip: none, but not saving my progress in games ; Kingdom Hearts Re-Coded or Super Mario 64 DS. I've tried creating save states and those also disappear upon returning to the emulator.
I'm using a fresh 256GB Samsung Evo Memory Card and scanned to fix the exact partition. I've also noticed that randomly the scraped art and information seems to vanish from the main interface. Currently my dream cast images refuse to show up but the videos will still play.
Any assistance would be appreciated. Thank you for the incredible firmware.

It sounds like you may have deleted some important folders from the NDS folder in the easyroms partition.  Restore them by extracting them from this archive
For the disappearing content, it sounds like you may be suffering some corruption of the exfat roms partition.  This will happen if you frequently just reboot the unit using the reset button instead of doing a safe shutdown or restart.  Try scanning the easyroms partition from a Windows 10 or newer computer to see if it can fix it.

Thank you very much for the prompt response.  I'm used to devices like Raspberry Pis so I take great care when safely shutting down these kinds of devices.  I can't seem to download the archive from the link.  I expanded the exfat partition from a 128gb back-up image. Perhaps that may have caused the issue?  I'll likely start over, backing up my roms, images and videos and see if the issue persists.

Sorry about that.  Try this link. https://github.com/christianhaitian/arkos/raw/main/defaultromsfolderstructure-rg351p.7z

I realized the issue was due to expanding the roms partition after flashing a 128gb backup.  i started fresh from a clean install and the issue is completely resolved.  hope this wasn't a big inconvenience.  thank you so much for your help. <3


add arg to specify the documentation's folder, in case is not docs

Is this an issue that has been encountered?  I would have thought that the relative paths were sufficient, especially since I only ever go through doc.meta.build...

not anymore, things work for now... but, I need to provide explicitly the config.mts file, otherwise fails.
https://github.com/lazarusA/julia/tree/la/docs

Aha!  Yeah the Julia docs would be great to test out the formatting :D

@lazarusA Everything seems to be joinpath(doc.user.build, settings.md_output_path, ...), no explicit references to a docs folder.  What exactly needs to be done here?
The package.json file does hardcode .documenter as the md_output_path or so, but that seems unrelated to this issue?

just by changing the template reading the docs and looking for information is so much better. We should try to push this whole thing a little bit more :D

yeah. You are right.
The original issue was that, if you don't provide any .json file, then it tries to copy do docs/, which it might not exist. But, things work know, maybe I should try to remove again the .vitepress folder from src and test again.

Huh, it should never do that in theory.  Maybe Documenter was run in the wrong folder?  That's the only thing I can think of...

Ok, now I had removed the .vitepress folder, the build works, but it looks like it cannot install the proper node dependencies:
> docs:dev
> vitepress dev _build/html/en/.documenter

failed to start server. error:
Error: You need to install `markdown-it-mathjax3` to use math support.
    at createMarkdownRenderer (file:///Users/lalonso/node_modules/vitepress/dist/node/serve-BTRXZ1g2.js:37405:13)
    at async localSearchPlugin (file:///Users/lalonso/node_modules/vitepress/dist/node/serve-BTRXZ1g2.js:41795:14)
    at async createVitePressPlugin (file:///Users/lalonso/node_modules/vitepress/dist/node/serve-BTRXZ1g2.js:42426:5)
    at async createServer (file:///Users/lalonso/node_modules/vitepress/dist/node/serve-BTRXZ1g2.js:63811:14)

commenting out those lines for now 😄 .

Does https://github.com/LuxDL/DocumenterVitepress.jl/pull/91 fix it?

no, it does not.
Summary:

For some reason extra Node dependencies are not being install.
the following syntax in the config.mts menu names is not valid:  'Julia's example':  (the extra ') there was a way, don't remember now.
A lot broken id @ast things.

if you want to see what it works a the moment even this issue comment out some lines
import { defineConfig } from 'vitepress'
import { tabsMarkdownPlugin } from 'vitepress-plugin-tabs'
// import mathjax3 from "markdown-it-mathjax3";
// import footnote from "markdown-it-footnote";

// https://vitepress.dev/reference/site-config
export default defineConfig({
  base: '/docs.julialang.org.git/',// TODO: replace this in makedocs!
  title: 'The Julia Language',
  description: "A VitePress Site",
  lastUpdated: true,
  cleanUrls: true,
  outDir: '../final_site', // This is required for MarkdownVitepress to work correctly...

  ignoreDeadLinks: true,

  markdown: {
    math: false,
    config(md) {
      md.use(tabsMarkdownPlugin)
      // md.use(mathjax3),
      // md.use(footnote)
    },
.
.
.

overall, I'm pretty happy with the outcome.

after cloning the repo simply doing first in the root directory:
make docs # this will build the docs.

then
cd doc

and the usual
npm run docs:dev

ERROR: LoadError: expected package Documenter [e30172f5] to be registered

Ah the error here was that the path in package.json was incorrect.

The language 'llvm' is not loaded, falling back to 'txt' for syntax highlighting. (x5)

The language 'fortran' is not loaded, falling back to 'txt' for syntax highlighting.

are probably dealbreakers for using the actual Julia docs for this, unless we manage to hack Vitepress to change its syntax highlighter to something which supports Fortran and LLVM :(

Ok. I kinda finish the Julia docs 👎🏻 .  Solving https://github.com/LuxDL/DocumenterVitepress.jl/issues/101 might fix the last issue, only LibGit2 is failing and it looks related to a missing tag.
Also, I still had problems with the Node dependencies. I solved by

Copying the package-lock.json into doc folder and then manually doing npm i.  @asinghvi17 how did you solved this?
For now, nav and sidebar are done manually.

You should see this:

ps://github.com/LuxDL/DocumenterVitepress.jl/assets/19525261/5829a1bd-eafd-4d83-9e67-22d9c23340ce">

Ah the error here was that the path in package.json was incorrect.

but, you did changed something? if I understood this correctly.

Ah yeah I forgot :sweat_smile: I just changed the paths in the package.json to point to the cover.  We should actually use npm run vitepress directly instead.


matchmaking servers wrapper

@Noxime Hi, can you review this when you have time?

Taking all this into account I'm not sure if it's worth at all to return Request from function itself. It will make request non-reusable (since you won't be able to refresh query from outside), etc. but on other hand we'll get rid of that ugly ServerListRequest's inside Mutex'es and as far as i think make possible releasing request automatically or while query is refreshing if user wants this. Do you have any thoughts about that?

Just done rewriting it to see if its gonna work. You can check it in the history-rewite branch https://github.com/ymo-4/steamworks-rs/commits/history-rewrite/. Looks cleaner and simpler, isn't it? However "autoreleasing" looks a bit weird and hacky (you can see it in add autorelease commit). Also tested it a little bit and it seems that request.refresh_server() sets is_refreshing state as true and set it back to false after a few RunCallbacks calls but do not call any callbacks, which prevents automatically releasing, especially when calling inside a refresh_complete. Since RunCallbacks waiting for our callback function to be done while we are waiting for refresh_server() results we're getting endless waiting. So we need to either remove refresh_server() method or make a our own custom callback if it's possible.
What do you think of this rewritten version?

To summarize what I have for now. There are two slightly different wrappers for the history requests. Both works well and are ready to merge. Each one has it's pros and cons:
mms (this)
Pros:

User has (almost) all features and possibilities of the request which steamworks gives
User can keep the request alive as long as they want and use it from any threads and places they want

Cons:

User must release request by himself
Has that ugly Arc<Mutex<ServerListRequest>> everywhere
User can't release request while query is refreshing

history-rewite
Pros:

User does not have to worry about releasing the request. It will be released automatically after the refresh_complete callback is called and the query is not refreshing anymore
User can release the request by himself even while query is refreshing
Code looks cleaner and more "rusty"

Cons:

Request is non-reusable in some sense
More limitations, less features
No ServerListRequest.refresh_server method

Feel free to review both of them, decide which is better and if all is well - merge it! Or maybe both are good and we can merge them like crate features or something, who knows.


Have you  change the network ? I can't load the the model which is downloaded from torchvision repository

I can't acess the links you guys providid ( drive link is forbiden in Lab ), so I download the model from torchvision repository. It can't load this model.
Is there any idea about training the mdoel without pretrained model ? Maybe I can init the weights by random value ?
Thks

@graycrown, have you identified the issue? I'd like to use the torchvision vgg weights as well.


Add Body Class and Ignore Class

Hey, here is a new Pull Request. Now you can see it better I hope :)
Sorry for the late response!

No problem, thanks! There are a few linter errors, could you take a look?
https://travis-ci.org/feimosi/baguetteBox.js/jobs/195095908#L188

@feimosi: just fix them yourself and push to @davidhellmann fork and then just squash + merge.

I can't push to other's forks without some extra permission, can I?

Yep you can. This is the default option for PRs opened like in the last
year. See the command line instructions in a PR in a project of yours :)
On Sep 15, 2017 20:23, "Marek Grzybek"<EMAIL_ADDRESS>wrote:

I can't push to other's forks without some extra permission, can I?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/feimosi/baguetteBox.js/pull/143#issuecomment-329845495,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtUw-Cnf1fTWwrMgIJ5yoveMHuDQdks5sirKZgaJpZM4LtNkG
.

@XhmikosR Interesting, thanks! :)

@feimosi: I replied via email but you probably missed it.

Now regarding this PR... are you sure all supported browsers have classList support?
We should add ESLint plugin compat to automate this.

@XhmikosR I didn't get that message.
Anyway, I've added an extra check for classList support here:
https://github.com/feimosi/baguetteBox.js/pull/143/files#diff-4634650f8cf2cdceb34291a9bcf4c23fR472
I'll test test thoroughly before the next release too.

@feimosi: I wouldn't personally go with that. If you still want to support < IE 9 you should do this https://plainjs.com/javascript/attributes/adding-removing-and-testing-for-classes-9/

Sure, it works only in newer IE, but using this option won't break anything, so I don't see any hazard here. Treat it as progressive enhancement, I just need to mention that in the docs.


'bar chart: borderSkipped not working.

borderSkipped not working. Set it to top but top border still visible.
Please see JSBin: https://jsbin.com/xihovibego/edit?html,js,output

@romanovma looks like this can only be set on all elements at the moment. Work around: https://jsbin.com/muxoxodoro/1/edit?html,js,output

@etimberg, actually I want to show only the left border of the bar so setting borderSkipped: 'top' to rectangle won't work for me as doesn't allow to use array.
What do you mean by set on all elements? May this can be a workaround in my case..
Many thanks.

I meant apply to all datasets rather than per dataset. I don't think there is a good way to only draw the left border. You might have to override Chart.elements.Rectangle.prototype.draw

OK, got you, thanks.

Could be a new feature: borderWidth: [0, 0, 0, 1] // trbl

Is there a way one could possibly remove the border width completly?

I want to be able to control the four sides of the border width.  I wonder if this issue will be fixed.  @simonbrunel , @etimberg  Any update?  Thanks.

4 sided control of border width was added in #6077 and released in Chart.js v2.8.0


hyperparameter tuning

Hi! Thanks for your great work.
I am also trying to use my own dataset to carry out the experiment, but I find that semi-supervised has only improved 0.5% IoU than full-supervised for my dataset, could you give me some suggestions for hyperparameter tuning in order to improve the result of semi-supervised?
Thanks.

Hi @lqycrystal
Thank you for your interest.
I would suggest starting with a simple case, using only a single perturbations / aux. decoder with say only K=2, this will reduce the training time and gives you the ability to find the best hyperparameters (LR / weighting and ramp-up period), then add additional aux. decoders. You can also try using annealed CE that helps with small labeled sets.
I'd also like to note that the performance gain depends on the amount of labeled / unlabeled data, if the difference if big, then SSL helps. But the biggest the labeled set, the smaller the gains are.

Hi @lqycrystal
Thank you for your interest.
I would suggest starting with a simple case, using only a single perturbation / aux. decoder with say only K=2, this will reduce the training time and gives you the ability to find the best hyperparameters (LR, loss weightings and ramp-up period, etc...), then add additional aux. decoders. You can also try using annealed CE that helps with small labeled sets.
I'd also like to note that the performance gain depends on the amount of labeled / unlabeled data, if the difference if big, then SSL helps. But the biggest the labeled set, the smaller the gains are.

Thanks for your reply!


Adding Hover Effect in Navigation Bar

Adding Hover Effect in Navigation Bar. Also when a page is active there is no hover effect. I also want to add that.

@QAZIMAAZARSHAD pls assign me this issue.

@ishitakapoor26 navigation bar already has hover effect also another issue to improve it is also open #33


Bugfix to mbedtls_ssl_parse_new_session_ticket

Closed because it was replaced by #69, which was already merged

Not sure if the issue is fixed. Here is my attempt to connect to enabled.tls13.com:
% ./ssl_client2 server_name=enabled.tls13.com server_port=443 ca_file=/etc/ssl/cert.pem auth_mode=optional
. Seeding the random number generator... ok
. Loading the CA root certificate ... ok (114 skipped)
. Loading the client cert. and key... ok (key type: EC)
. Connecting to tcp/enabled.tls13.com/443... ok
. Setting up the SSL/TLS structure... ok
. Performing the SSL/TLS handshake... ok
[ Protocol is TLSv1.3 ]
[ Ciphersuite is TLS_CHACHA20_POLY1305_SHA256 ]
[ Key Exchange Mode is ECDHE-ECDSA ]
[ Record expansion is 5 ]
. Verifying peer X.509 certificate... failed
! The certificate is not correctly signed by the trusted CA
. Peer certificate information    ...
cert. version     : 3
serial number     : 02:A7:C1:95:57:7F:F0:E9:0C:35:99:61:D2:04:B0:ED
issuer name       : C=US, O=Cloudflare, Inc., CN=Cloudflare Inc ECC CA-3
subject name      : C=US, ST=CA, L=San Francisco, O=Cloudflare, Inc., CN=sni.cloudflaressl.com
issued  on        : 2020-08-17 00:00:00
expires on        : 2021-08-17 12:00:00
signed using      : ECDSA with SHA256
EC key size       : 256 bits
basic constraints : CA=false
subject alt name  :
dNSName : tls13.com
dNSName : *.tls13.com
dNSName : sni.cloudflaressl.com
key usage         : Digital Signature
ext key usage     : TLS Web Server Authentication, TLS Web Client Authentication
certificate policies : ???, ???

Write to server: 34 bytes written in 1 fragments

GET / HTTP/1.0
Extra-header:
< Read from server: mbedtls_ssl_read returned -0x6e00
Last error was: -0x6E00 - SSL - Processing of the NewSessionTicket handshake message failed

Thanks @zhihan , there turned out to be another bug not in the way the ticket is parsed, but the way it's fetched from the current messaging layer. Fixed in https://github.com/hannestschofenig/mbedtls/pull/74 and fix confirmed by running the command you pasted.


Add support for strongly-typed columns in Filters utility

The new strongly-typed columns bring clarity to the filtering in the query service and they are supported well in the new client API, but unfortunately, the standard query API is not supported.
The current usage forces us to have smth like:
String orderIdColumn = ImageItem.Column
        .orderId()
        .name()
        .toString();
Query query = factory(userId)
        .query()
        .select(ImageItem.class)
        .where(Filters.eq(orderIdColumn, orderId))
        .build();

It'd be great if we have overloads in the Filters utility class that accept EntityColumn, e.g.:
    public static Filter eq(EntityColumn column, Object value) {
        checkNotNull(column);
        checkNotNull(value);
        return createFilter(column.name().asPath(), value, EQUAL);
    }

Closed with #1246.


Support correlation between variables

Currently,
using Measurements
x = 5.2 ± 0.4
x-x != zero(x)
x*x != x^2
tan(x) != sin(x)/cos(x)

because the package doesn't support correlation between variables.
I don't really know how the covariance matrix should be calculated in this case, where there are two single measurements, not two elements of a population.  Any hint on this is appreciated.
After looking at the user guide of the Python package uncertainties, I think that the Measurement type should be extended to have two extra fields: a unique tag to identify each measurement (so that two measurement with the same value and uncertainty are equal), and the list of derivatives of variables constituting the object.  For example:
# Definition.  The Measurement type is composed by the following fields:
#   * val: the nominal value of the measurement
#   * err: the uncertainty, assumed to be standard deviation
#   * tag: a (hopefully) unique identifier, it is used to identify a specific
#     measurement in the list of derivatives.
#   * der: the list of derivates.  It is a dictionary, whose keys are the tags
#     of the quantities with which the measurement has been derived, and the
#     corresponding value is the derivative of the new measurement with respect
#     to that measurement.  This dictionary is useful to trace the contribution
#     of each measurement.
immutable Measurement{T<:Real} <: Real
    val::T
    err::T
    tag::Float64
    der::Dict{Float64, T}
end

# Constructor
function Measurement(val::Real, err::Real)
    val, err, der = promote(val, err, one(val))
    tag = rand()
    return Measurement(val, err, tag, Dict(tag=>der))
end

This change, necessary to make the package fully work, will definitely degrade performance, so it needs to be thought carefully.  Input is very welcome.

This has been implemented in commits 6f8fb48...590d423 (from 6f8fb48 Move @uncertain to math.jl file to 590d423 10x improvement for "result" function for more than one argument; see https://github.com/giordano/Measurements.jl/compare/6f8fb48...590d423)


build error

Hi Robsondepaula,
when I tried to build your demo project, it showed build error which is  regarding of Dex problem.
Any idea to fix build error?
I have test with latest unity
Thanks
Regrads,
com.android.build.api.transform.TransformException: java.lang.RuntimeException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: /Users/derrick/temp/unity-android-native-camera/UnityAndroidCamera/Temp/gradleOut/build/intermediates/transforms/dexBuilder/release/12, /Users/derrick/temp/unity-android-native-camera/UnityAndroidCamera/Temp/gradleOut/build/intermediates/transforms/externalLibsDexMerger/release/0 See the Console for details.

Hello @superbderrick,
Please open "Build Settings" and make sure:

"Android" is selected in the Platform panel;
the Build System dropbox is showing "Internal".

Please try again and let me know.

Thanks, build is working well but camera preview was not showing.
Anyway thanks the project is very helpful
Thanks
Regards


Texture filter is changing itself when resizing window

Godot version
v4.1.1.stable.official [bd6af8e0e]
System information
Windows 11, NVIDIA GeForce RTX 3060 Laptop GPU
Issue description
The 2d or 3d sprites changing it's texture filter to nearest when window resize occurs. The problem seen when using "compatability" renderer.
Steps to reproduce

Create a scene
Create a Sprite2d or Sprite2d
Attach an texture to it (godot logo for example)
Start the scene
Resize or fullscreen the window

Minimal reproduction project
The repro is pretty easy. But can do if needed.

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/81676, as this is fixed in 4.2.dev4.


dev console should not pop up in release build

By this I'm referring to the exe file created by "npm run dist". Or if there is already an alternative command to achieve this, it should be documented in the readme.

How did you build the files before creating the exe? If you've previously just run npm run dev:react and npm run dev:electron then the app will be built for development not release. As mentioned in #66 the npm run dist command just packages the built files.

This is also not fixed by my attempt with "npm run build".

Did this get fixed by adding in cross-env to the commands for building a release?

Yes.


Typo errors in project documentation

Welcome to NodeCloud with Hacktoberfest 2020!
Stay in the know: Get notified of updates by clicking the 👁🗨 watch button and save the repository for later reference by clicking the ⭐ star button at the top right corner of this repo!
Some typo errors need to be fixed:
The readme file of the nodecloud-next branch contains some typo errors. To note some (typo error > correction),

NodeCloud ☁ is standard library >  NodeCloud ☁ is  a standard library
providers with less code changes > providers with fewer code changes
open source >  open-source
community driven plugin > community-driven plugin,
third party > third-party
background knowlege on these > background knowledge on these
This is where magic happens✨ > This is where the magic happens✨
automactically  > automatically
immediatly > immediately

These need to be corrected and if you identify more typo errors while reading, fix them as well. Feel free to add a comment for further clarifications!
Additional information

The project currently contains two main branches: master and nodecloud-next. This feature is required to the nodecloud-next branch. so make sure that you create the feature branch from nodecloud-next.

nodecloud-next: https://github.com/leopardslab/nodecloud/tree/nodecloud-next.

Be sure to sign up at https://hacktoberfest.digitalocean.com so you can qualify to pick a limited edition t-shirt 👚 or plant a tree 🌳!

See https://hacktoberfest.digitalocean.com for more details.

Add a comment below if you are interested, will assign the task.

Impact

Read me file

Knowledge required

Version control systems (git)

I would give it a shot. could u assign this to me?

I would like to contribute to solving the issue, can you assign this to me?

Hi @PRAy-d welcome to NodeCloud, this issue has been already taken. You can check for more good first issues once new issues are added to the Node Cloud project.

can i help youwith more typo error if so ?

Can I contribute for any other issue ?

Solved with #72


set regular logging level to ERROR

The issue
Fix noisy output in pipenv check as described in issue #5939. Prior to release v2023.8.19 in pipenv/utils/__init__.py logging basic config was set to ERROR, then to INFO. I am not sure whether that was on purpose, was changed in a large commit #5793, maybe it was just used for debugging and then not changed back. @matteius
The fix
Change back to logging.ERROR.
The checklist

[x] Associated issue
[ ] A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

The change to INFO was intentional -- queit/bare should be fixed similar to how it was addressed here:
https://github.com/pypa/pipenv/pull/5897
Otherwise we will not be able to debug resolution internal to pip -- there were plenty of other issue reports related, which is why I made the change you referenced initially.    My stance is yes we want to better support quiet/bare, but its better to have too much information than not enough, and so I would rather leave the default as INFO and override specific to the quiet/bare flags.

@matteius I adjusted the code fitting to your recent pull request, setting to warn if not verbose.
I would like to have some thought based on how to pass the verbosity arg to  the check function in pipenv/cli/command.py: There is the possibility passing it via 'direct' argument, inserting verbose=False into the args, and the possibility of getting it via the State object. Both worked in my tests. I decided to go for the latter choice, however I am not 100% sure on that, as for example the quiet argument could, afaik, also be passed via the State, yet this is not the case. I would be grateful for further feedback.

I think the click args would all get passed via the state, the way you are doing it -- this change looks reasonable to me.


cmd-spawn-timeout when commiting due to 'credential-osxkeychain'

I was able to commit just fine using brackets and bitbucket for a couple of days, it however just - at random - returned the following error this morning;
Error: cmd-spawn-timeout: /usr/local/git/bin/git push --porcelain --progress --set-upstream bitbucket2 master
The commit starts with
git: 'credential-osxkeychain' is not a git command. See 'git --help'.
I tried re-installing, removing the bitbucket from the keychain, without any luck. Any ideas?

Compressing objects:  99% (793/801)
Compressing objects: 100% (801/801)
Compressing objects: 100% (801/801), done.
Writing objects:   0% (1/919)
Writing objects:   1% (10/919)
Writing objects:   2% (19/919)
Writing objects:   3% (28/919)   <-- fails here


[BUG] ValueError: Tokenizer class QWenTokenizer does not exist or is not currently imported.

是否已有关于该错误的issue或讨论？ | Is there an existing issue / discussion for this?

[X] 我已经搜索过已有的issues和讨论 | I have searched the existing issues / discussions

该问题是否在FAQ中有解答？ | Is there an existing answer for this in FAQ?

[X] 我已经搜索过FAQ | I have searched FAQ

当前行为 | Current Behavior
执行cli_demo或者web_demo遇到ValueError: Tokenizer class QWenTokenizer does not exist or is not currently imported.
求助。
期望行为 | Expected Behavior
希望能得到解决办法。
复现方法 | Steps To Reproduce
run cli_demo or web_demo
ValueError: Tokenizer class QWenTokenizer does not exist or is not currently imported.
运行环境 | Environment
- OS:windows
- Python:3.9
- Transformers:4.31.0
- PyTorch:2.0.1
- CUDA (`python -c 'import torch; print(torch.version.cuda)'`):11.8

备注 | Anything else?
i need help!!!

Please first check if the download files are complete (there should be related logs if errors were encountered, but the provided log is incomplete). In mainland China, accessing huggingface may be unstable. The solution to this problem is provided in README (search for "snapshot_download").
In addition, if you have changed the arguments or the Python scripts, please provide us with more information so we can better help you.

同遇到这个问题，
transformers:4.32.0
kaggle notebook: https://www.kaggle.com/code/jackiewu/qwen-int4-finetune

same issue when finetune lora

same issue when finetune lora

i think the peft's version caused this, after change the version to this : transformers==4.32.0 torch==2.1.2+cu121 torchvision==0.16.2+cu121 peft==0.7.1 lora worked

The peft version conflict, as detailed in the README file, was anticipated to arise no earlier than January 30th, 2024.

However, this issue has surfaced significantly sooner than that, suggesting a different cause, most probably due to the similar use of from_pretrained without trust_remote_code=True.
Since the release of Qwen1.5, trust_remote_code=True is no longer a must because it is intergrated into the transformers codebase. For more information about this integration, discussions on how to leverage Qwen1.5 within the transformers environment, and for updates on community feedback and enhancements, please visit the official Qwen1.5 GitHub repository at https://github.com/QwenLM/Qwen1.5.

Encounted the same problem. I just upgraded the transformer to 4.38.0, 4.38.2, or 4.39.0. But all these endeavors fell to succeed. I wonder how to upgrade the accelerate (to 0.27.2)? Many thanks!

Just encounted the same problem. I just upgraded the transformer (to 4.38.2) and accelerate (to 0.27.2), then the model loads up successfully.


Add Annotator for Clinical Data (ACD) connect route

This PR addresses issue #73
There are two primary routes included:

direct:fhir-r4-to-acd
direct:acd-analyze
Per our slack conversation, I omitted the Kafka consumer route that fed route 1 above.
I cleaned up the code since our review last week and added unit tests.
I look forward to your feedback.
Thanks in advance

Addressed the two required updates for PR merging.
I'll look into simplifying the predicate checks for the analyze route.


in your lastdemo have some bug

in SKetchPicker
chose black or white zhe Hue cant click just can move

Ah, great catch! I am looking into it.

This has been fixed in the latest version.


fix: fix "Go to definition" for @value

https://github.com/user-attachments/assets/b4dc6798-9cba-4d14-9cb6-19771b31024f
https://github.com/user-attachments/assets/bc167658-af95-4763-abee-2b3f0d6012fb

Happy New Year 🎍


Questions about distill_loss

sorry to bother, I see the distill_loss in distill.py as :
distill_loss = F.kl_div(
F.log_softmax(distill_logits / T, dim=-1),
F.softmax(teacher_logits / T, dim=-1).detach(),
reduction='batchmean')
I wonder why the teacher part uses the softmax function rather than log_softmax one, thanks.

@haoren55555 yeah, you could do log softmax for teacher too by setting log_target = True https://pytorch.org/docs/stable/generated/torch.nn.KLDivLoss.html . i'm just rolling with what pytorch offers

That was insightful. However, in your implementation of class DistillMixin, you are passing the cls token from the MLP lead.
The MLP head of the distillation token is implemented using LayerNorm, whereas the cls token MLP head is implemented in vit.py without LayerNorm. Why is it so? What am I missing? Please correct me if I am wrong.

https://github.com/lucidrains/vit-pytorch/blob/90be7233a3f55c29692a72da6ee4dcb5aab267d4/vit_pytorch/vit.py#L111C14-L111C22

@lucidrains
I have also noticed that in the paper, the authors mentioned that at test time, they fused the two heads, i.e., MLP heads for cls token and distilled token.

for which we add the softmax output by the two classifiers to make the prediction. (p.8, paragraph 3)

This fusion of two heads is not implemented in the forward method of the DistillMixin class. Please let me know if it is implemented elsewhere or if I am missing something. Thanks for the excellent codebase.


"Building scene..." loading spinner doesn't appear navigating between files

Blocking closing #3385. I've fixed the first part of that test by fixing navigation between files with #3498. However, in order to test there is a re-execution we want to see a loading spinner between file navigations, and that is no longer occurring for some reason.
We definitely want it back to hide the model being built up since it can be pretty jump and jittery.

I actually hate that building scene thing so this is a feature imo On Aug 16, 2024, at 17:28, Frank Noirot @.***> wrote:
Blocking closing #3385. I've fixed the first part of that test by fixing navigation between files with #3498. However, in order to test there is a re-execution we want to see a loading spinner between file navigations, and that is no longer occurring for some reason.
We definitely want it back to hide the model being built up since it can be pretty jump and jittery.
 loading step, read above). I think I just need to sort out how to confirm re-execution has occurred and then #3385 will be good to close. It's definitely re-executing but our test doesn't capture that.

or at least like make it semi-transparent so you can see shit thru it

The building scene is only there to sell the system is fast.
Without this, modeling-app is clearly building up the object. killing any semblance of speed.
Business Lee says we should really keep it.
Technical Lee says yeah I would WAY prefer we just fix the speed issue but I'm not sure we can right now!
Casual Lee says yeah let's rip 'er out I'm not a fan of the hack either.
The internal struggle is real yo

Have now talked to people w complex kcl and all want this gone every where so yeah let’s def remove , people would rather see it executing than a loader

Users hate it

If kcl is slow let’s make it fast, no loaders

If the tradeoff is users see the model executing before we make it faster I’m fine w that

Because in some cases you are instead watching a loader with zero progress for 45 seconds and have no idea if it failed or not which is just hiding the pain and making it worse

And then people blame and think it’s the stream, anyways tldr, kill it

also @adamchalmers and ive now recruited @alteous to help on perf things so we gots people trying to make it better dont worry, just eff the loaders, its too opaque what is happening on large files

Let's do itttt :rocket:

Hey I think this is a great idea, but could it wait until after the electron port is done? I would consider ripping that out a sidequest-on-sidequest situation.

up to you all as long as its right after :)

Oh didn't realise this was a post electron thing. I'll make a status for that.

this is done i just gotta push it

https://github.com/KittyCAD/modeling-app/pull/3691


Add a meaningful CONTRIBUTING.md file

To comply fully with Github's community standards a well documented CONTRBUTING.md file is required to help first time contributors to contribute to this repository. You can use this guide here to write a good one

Hi can i take this ?

Pls assign this task to me

Sure @OverthinkersArea

#32 merged


[SPARK-27834][SQL][R][PYTHON] Make separate PySpark/SparkR vectorization configurations

What changes were proposed in this pull request?
spark.sql.execution.arrow.enabled was added when we add PySpark arrow optimization.
Later, in the current master, SparkR arrow optimization was added and it's controlled by the same configuration spark.sql.execution.arrow.enabled.
There look two issues about this:

spark.sql.execution.arrow.enabled in PySpark was added from 2.3.0 whereas SparkR optimization was added 3.0.0. The stability is different so it's problematic when we change the default value for one of both optimization first.

Suppose users want to share some JVM by PySpark and SparkR. They are currently forced to use the optimization for all or none.

This PR proposes:

Deprecate spark.sql.execution.arrow.enabled
spark.sql.pyspark.execution.arrow.enabled -> fallback to spark.sql.execution.arrow.enabled
spark.sql.sparkr.execution.arrow.enabled
Deprecate spark.sql.execution.arrow.fallback.enabled
spark.sql.pyspark.execution.arrow.fallback.enabled   -> fallback to spark.sql.execution.arrow.fallback.enabled

Note that spark.sql.execution.arrow.maxRecordsPerBatch is used within JVM side for both.
Note that spark.sql.execution.arrow.fallback.enabled was added due to behaviour change. We don't need it in SparkR - SparkR side has the automatic fallback.
How was this patch tested?
Manually tested and some unittests were added.

Test build #105763 has started for PR 24700 at commit beec132.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11019/
Test PASSed.

I think it's fair, but just to call out, spark.sql.sparkr.* doesn't seem to be consistent with existing name scheme, I believe

Test build #105763 has finished for PR 24700 at commit beec132.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105763/
Test PASSed.

Yes.. I am not sure what we should name tho. If we name it spark.pyspark then it's usually spark conf at SpsrkContext. I was thinking it makes sense to spark.sql.pyspark too in a way because it works closely with SQL.

Adding @BryanCutler, @viirya too. Let me go ahead with it. The naming is a bit odd but I think we should use spark.sql.sparkr.* to keep it in SQLConf like before. Otherwise, we can't use it within session level like before ..

If there are no more concerns than that, let me go ahead.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11107/
Test PASSed.

Test build #105851 has started for PR 24700 at commit 9fbc9e1.

Test build #105851 has finished for PR 24700 at commit 9fbc9e1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105851/
Test PASSed.

Not a big deal but would it make a little more sense to be called spark.sql.execution.arrow.pyspark.enabled and spark.sql.execution.arrow.sparkr.enabled? That roughly follows the Scala package and is a little more consistent with the other arrow confs. The current way is fine with me also though.

hmmmmmm .. yea, I can just grep and replace .. I don't have a preference. One argument I can think is that pyspark or sparkr looks wider. but I don't mind. WDYT @gatorsmile, @felixcheung, @viirya, @rxin?
spark.sql.execution.arrow.pyspark.enabled vs spark.sql.pyspark.execution.arrow.enabled
Just pick one (don't have to list up reasons).

spark.sql.execution.arrow.pyspark.enabled looks slightly better.

Let me replace it to spark.sql.execution.arrow.pyspark.enabled way soon.

Test build #105987 has started for PR 24700 at commit 6ad1cd8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11238/
Test PASSed.

Test build #105988 has started for PR 24700 at commit f6a2d99.

ok

Test build #105987 has finished for PR 24700 at commit 6ad1cd8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105987/
Test PASSed.

Test build #105988 has finished for PR 24700 at commit f6a2d99.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105988/
Test PASSed.

Is everybody happy with it :-) ?

I am merging this - looks like we're positive on this in general and no notable comments.

LGTM


Hello, may I ask when it will be open source？

Sorry, I was busy with work a while ago and I didn't organize it well. Please forgive me for delaying your work ~
The code is now open source.
Due to the rush of sorting out, there may be some configuration issues, please feel free to communicate on github or email ~

I get it, Thanks for your interesting work!


[0.23] jazzer junit switched to a runtime api dependency

I am a little confused as to why this would be intentional or if I am misusing your library. The 0.22.1 pom has jazzer-api as a compile time dependency, whereas the 0.23 pom moves all of its dependencies as runtime. Therefore, when upgrading I receive the following error.
> Task :caffeine:compileTestJava
/Users/ben/projects/caffeine/caffeine/src/test/java/com/github/benmanes/caffeine/fuzz/CaffeineSpecFuzzer.java:18: error: package com.code_intelligence.jazzer.api does not exist
import com.code_intelligence.jazzer.api.FuzzedDataProvider;
                                       ^
/Users/ben/projects/caffeine/caffeine/src/test/java/com/github/benmanes/caffeine/fuzz/CaffeineSpecFuzzer.java:31: error: cannot find symbol
  public void parse(FuzzedDataProvider data) {
                    ^
  symbol:   class FuzzedDataProvider
  location: class CaffeineSpecFuzzer

A runtime dependency typically means that users should not use those classes themselves as an implementation detail. For example using the JDBC api with a runtime Postgres driver, or SLF4J with a runtime Logback provider. If an API should be used by consumers then that would be a compile time dependency. This does not seem to be the case unless my tests are an incorrect usage,
package com.github.benmanes.caffeine.fuzz;

import com.code_intelligence.jazzer.api.FuzzedDataProvider;
import com.code_intelligence.jazzer.junit.FuzzTest;
import com.github.benmanes.caffeine.cache.CaffeineSpec;

/**
 * @author<EMAIL_ADDRESS>(Ben Manes)
 */
public final class CaffeineSpecFuzzer {

  // These tests require the environment variable JAZZER_FUZZ=1 to try new input arguments

  @FuzzTest(maxDuration = "5m")
  @SuppressWarnings("CheckReturnValue")
  public void parse(FuzzedDataProvider data) {
    try {
      CaffeineSpec.parse(data.consumeRemainingAsString());
    } catch (IllegalArgumentException expected) { /* ignored */ }
  }
}

The easy workaround is to simply add the API dependency explicitly and that is fine. However the release notes do not state anything about this change if intentional, the junit example uses an outdated version, and it just looks like an accidental goof than an expected change.

It looks as though 0.23 enhanced the integration to support, or at least now document (old, new), that basic types like String can be provided instead. That is a nice change, but certainly requires better communication for your releases.


Missing AnimateTests.swift file

Thanks for making this public. Really love it.
The AnimateTests.swift (and associated AnimateTests.plist) file is referenced in the Xcode project, but is missing in the repo. Which means that the testing scheme cannot be ran.
If they do indeed contain unit tests, it would be useful to have, especially when adding additional functionality.

@drhaynes Happy to hear that you like it. At first I thought about making this a project that I'll maintain and keep adding to, but I don't think that'll happen (at least not at the moment, I simply don't have time for it 😅). Instead, I'd recommend to use it as a reference point (it's mostly an accessory to my 2-part blog posts: https://www.swiftbysundell.com/posts/building-a-declarative-animation-framework-in-swift-part-1) to build your own animation system using the techniques it presents.
I should update the README and Xcode project to reflect this, will do that at some point.

Sure thing, thanks for clarifying.


Building from latest sources LINK error for 2 out of 3 build targets

Describe the bug
Attempting to build from sources recent pull from repo, i get a LINK error showing cannot open input file mrwebrtc.lib for x86 and ARM build targets.  I get no errors for x64 build target.
To Reproduce
Cloned latest source from master.  Ran Powershell scripts for each of the 3 build targets. Open visual studio solution and try to build for each of the 3 build target architectures.  X64 fully succeeds, x86 and ARM have 1 failure (cannot open input file mrwebrtc.lib)
Expected behavior
Clean build for all three build target architectures.
Environment

MR-WebRTC version - Latest master

Hello, is there any news on this issue ? I've got the same problem with master branch but not with release/2.0.

I tried from a fresh clone and everything works as intended.
git clone --recursive https://github.com/microsoft/MixedReality-WebRTC.git -b master mr-webrtc-temp
powershell
cd tools\build
.\build.ps1 -BuildConfig Debug -BuildArch x64 -BuildPlatform Win32
.\build.ps1 -BuildConfig Debug -BuildArch x86 -BuildPlatform UWP
.\build.ps1 -BuildConfig Debug -BuildArch ARM -BuildPlatform UWP

then switch to Visual Studio and build:

mrwebrtc-win32 in x64/Debug
mrwebrtc-uwp in x86/Debug and ARM/Debug

cannot open input file mrwebrtc.lib

I assume you mean webrtc.lib and not mrwebrtc.lib.

x86 and ARM have 1 failure

If Visual Studio complains it cannot find webrtc.lib it's because it's not built. Use the build.ps1 script to build the variant you're missing, or provide more details about exactly what you are trying to do and what you are building in Visual Studio (exact project and solution configuration and platform). ARM is only supported with UWP (and so only for mrwebrtc-uwp, not mrwebrtc-win32), but x86 is for both Desktop and UWP, though you need to build both with ./build.ps1 if you intend to use both. Though in general there is little reason to build Desktop x86.

@djee-ms the LINk error in Visual Studio definitely shows cannot open input file mrwebrtc.lib when building solution for x86 and ARM Release targets.  I ran the powershell script for all three architectures before opening the solution in Visual Studio

What project is failing?

mrwebrtc-unityplugin-win32.vcxproj fails

Alright! So,

This obviously won't work on ARM
There's a bug indeed that I can repro. I thought I had fixed it with #677 and it went away and now came back, I have no idea why this keeps failing.

Do you need the Unity native renderer plugin though? Because if you don't then you can ignore the error.

Actually, there's no bug. I tried in x86 Debug :

mrwebrtc.lib is not found because it's not built. It's missing webrtc.lib.
webrtc.lib is not found because it's not built either. I hadn't run .\build.ps1 for that variant.

After building all items in order everything works as expected.

.\build.ps1 -BuildConfig Debug -BuildArch x86 -BuildPlatform Win32
Build mrwebrtc-win32 in Debug/x86
Build mrwebrtc-unityplugin-win32 in Debug/x86

I don't know about the ARM issue because mrwebrtc-unityplugin-win32.vcxproj doesn't support ARM.

I am building to Release configs, not Debug configs.  I just reverified by running the build script again and trying to build solution for x86 Release and the same project fails.

1>------ Build started: Project: mrwebrtc-unityplugin-win32, Configuration: Release Win32 ------
1>   Creating library xxxxxx\mr-webrtc-temp\tools\build\mrwebrtc\..\..\..\bin\Win32\x86\Release\mrwebrtc-unityplugin.lib and object xxxxxx\mr-webrtc-temp\tools\build\mrwebrtc\..\..\..\bin\Win32\x86\Release\mrwebrtc-unityplugin.exp
1>Generating code
1>Previous IPDB not found, fall back to full compilation.
1>All 889 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
1>Finished generating code
1>mrwebrtc-unityplugin-win32.vcxproj -> xxxxxx\mr-webrtc-temp\bin\Win32\x86\Release\mrwebrtc-unityplugin.dll
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Source I pulled was from March 12th. It looks like this commit was from the 18th?

3d15d1624604a99cdcf40ce11603279177fb4f9c is from March 19th.


Issue #6: Fetch pool data from camelot

closes #6
Description

I made this template for fetching the liquidity data (not price data yet) of OD and WETH in a pool. There still need to be some smart contract changes before this can be tested.

Any problems in the logic?

Add camelotPoolAddress to the OD token object 0x2A09411c7208c6dDcEC0fe8e3E58841f5F0F2030

Add chainlinkRelayer to WETH token object 0x42d8a0Eb0dFE1b5b4A2631adBb3310aEa3d70a92

Fetch balances of WETH and OD

Use market price of OD

Use ChainlinkRelayer getResultWithValidity for price of WETH

calculate the USD price of each

Add both to get total amount USD

rename return variable to totalLiquidityUSD

made the changes, but blocked because fetching the market price of OD fails consistently (tried both geb.contracts.oracleRelayer.marketPrice() and geb.contracts.oracleRelayer.connect(geb.provider).marketPrice). I suppose I could call fetchAnalyticsData within fetchPoolData but that would be a lot of calls to our contracts when all we need is the OD price

@pi0neerpat I've verified that I can get the balance of OD and WETH from our sample pool, it formats these correctly into big numbers and returns the liquidity in USD as well
here's the response from the sdk function, used in the app (see console logs):


[release-4.15] CNF-12400: Enhance seedgen system check with additional requirement checking

Manual cherry-pick of https://github.com/openshift-kni/lifecycle-agent/pull/636
/cc @leo8a

/lgtm

/approve


Documentation. Can Kamelet pull dependencies from private artifactory?

Documentation provides an example of dependencies declaration
# ...
spec:
  # ...
  dependencies:
  - camel:telegram
  - mvn:org.apache.commons:commons-vfs2:2.7.0
  - github:apache/camel-kamelets
  template:
    # ...

Couple of questions though,

can private artifactory be targeted? Any documentation/example please?
can such dependency include bean or processor, so that Kamelet can use it?

private artifactory is not supported as of today.
Depedencies could include beans and processors

Thank you @oscerd
Could you provide an example of dependency defined through the Kamelet, so that beans and processors are automatically bound to the registry?

I have an example of an application

        final KameletMain main = new KameletMain();
        main.configure().setBasePackageScan("com.apache.kamelet.poc");

and a application.properties
camel.component.kamelet.location = classpath:/kamelets,github:apache:camel-kamelets/kamelets
camel.main.routes-include-pattern = classpath:camel/*
camel.main.routes-reload-enabled = true
camel.main.routes-reload-directory = src/main/resources
camel.main.routes-reload-pattern = camel/*.yaml
camel.main.shutdown-timeout = 5
camel.main.lightweight = false

camel.main.autoConfigurationEnabled=true
camel.main.autoConfigurationEnvironmentVariablesEnabled=true
camel.main.autowiredEnabled=true
camel.main.basePackageScanEnabled=true

The application defines the route- camel/application-route.yaml
- route:
    id: "example"
    from:
      uri: "kamelet:example-source?topic=kafka_topic"
      steps:
        - log: "${body}"

The kamelet:example-source is defined in separate dependency (classpath-based lookup above allows application to see it)

apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
metadata:
  name: example-source
  annotations:
    camel.apache.org/kamelet.support.level: "Stable"
    ...
spec:
  definition:
     ...
  types:
    out:
      mediaType: text/plain
  dependencies:
    - "camel:kamelet"
    - "camel:core"
    - "camel:kafka"
    - "mvn:com.apache.kamelet.poc:kamelet-poc-processors:1.0.0-SNAPSHOT"
  template:
    from:
      uri: "kafka:{{topic}}"
      parameters:
        brokers: "{{?bootstrapServers}}"
        groupId: "{{?consumerGroup}}"
        autoCommitEnable: "{{autoCommitEnable}}"
      steps:
        - bean: "customProcessor"
        - to: "kamelet:sink"

kamelet-poc-processors module defines bean & configuration

@Configuration
public class CustomConfiguration implements CamelConfiguration {

    @BindToRegistry
    public CustomProcessor customProcessor() {
        return new CustomProcessor();
    }
...
public class CustomProcessor {
    public void handle(Exchange exchange) throws Exception {
    ...

KameletMain pulls dependencies indeed, but then fails with
Caused by: org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: customProcessor
	at org.apache.camel.component.bean.RegistryBean.doGetBean(RegistryBean.java:134)
	at org.apache.camel.component.bean.RegistryBean.getBean(RegistryBean.java:102)
	at org.apache.camel.component.bean.RegistryBean.createCacheHolder(RegistryBean.java:95)

However, once we add com.apache.kamelet.poc:kamelet-poc-processors:1.0.0-SNAPSHOT dependency to application's classpath, the error goes away.
How can such a problem be fixed, so that dependency is defined through the Kamelet? I will be glad to create a pull request in case such an issue can be resolved

I think you should add the dependency as modeling. Cc @davsclaus

And in 3.20, then camel download standard maven approach via your .m2/settings.xml file (and what else maven has). You can also set explicit repo
https://camel.apache.org/manual/camel-jbang.html#_configuring_exporting
On kamelet main you can call the setRepos method. Its a URL for custom maven repo.

Thank you @davsclaus
I run on plain JRE (no camel-jbang or camel-k)
public class Application {

    public static void main(String[] args) throws Exception {
        final KameletMain main = new KameletMain();
        main.configure().setBasePackageScan("com.apache.kamelet.poc");

        main.setDownloadListener(new DownloadListener() {
            @Override
            public void onDownloadDependency(String groupId, String artifactId, String version) {
                System.out.println("Downloading " + groupId + ":" + artifactId + ":" + version);
            }

Just to clarify, there is no issue for KameletMain to download the dependency in such a case
09:13:16.453 [main] INFO  o.apache.camel.main.BaseMainSupport -     [application.properties]       camel.main.basePackageScan=com.apache.kamelet.poc
09:13:16.453 [main] INFO  o.apache.camel.main.BaseMainSupport -     [application.properties]       camel.component.kamelet.location=classpath:/kamelets,github:apache:camel-kamelets/kamelets,github:mkhudyakov:aggregate-services-result-poc
Downloading org.apache.camel:camel-core-languages:3.20.0-SNAPSHOT
Downloading org.apache.camel.kamelets:camel-kamelets-utils:0.9.2
Downloading org.apache.camel:camel-kafka:3.20.0-SNAPSHOT
**Downloading com.apache.kamelet.poc:kamelet-poc-processors:1.0.0-SNAPSHOT**
Downloading org.apache.camel:camel-yaml-dsl:3.20.0-SNAPSHOT
Downloading org.apache.camel:camel-kafka:3.20.0-SNAPSHOT

The problem is for KameletMain to detect @Configuration / CamelConfiguration in downloaded dependency and bing beans to the registry.
As a result I get
Caused by: org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: customProcessor
	at org.apache.camel.component.bean.RegistryBean.doGetBean(RegistryBean.java:134)

The above issue goes away though in case dependency is explicitly added to the classpath (so no download happens for it)
I've tried the version 3.20.0-SNAPSHOT, but the result is the same.

Okay so scanning kamelet-main downloaded JARs via basePackageScanEnabled is not supported.
Its potentially a little bit difficult as downloads can happen later than the first scanning, and maybe its a bit "too magic".
As what should Camel do if there are similar annotations for spring boot / quarkus in the JAR with their style of annotations.

I can imagine the mechanism like
    public static void main(String[] args) throws Exception {
        final KameletMain main = new KameletMain();
        main.configure().setBasePackageScan("com.apache.kamelet.poc");

        Map<String, Class> configurations = new HashMap<>();
        main.setDownloadListener(new DownloadListener() {

            @Override
            public void onDownloadDependency(String groupId, String artifactId, String version) {
                System.out.println("Downloaded, " + groupId + ":" + artifactId + ":" + version);

                Reflections reflections = new Reflections("com.apache.kamelet.poc");
                Set<Class<?>> classes = reflections.getTypesAnnotatedWith(Configuration.class);

                for (Class clazz: classes) {
                    addConfiguration(configurations, clazz, main);
                }
            }

            @Override
            public void onAlreadyDownloadedDependency(String groupId, String artifactId, String version) {
                System.out.println("Already downloaded, " + groupId + ":" + artifactId + ":" + version);

                Reflections reflections = new Reflections("com.apache.kamelet.poc");
                Set<Class<?>> classes = reflections.getTypesAnnotatedWith(Configuration.class);

                for (Class clazz: classes) {
                    addConfiguration(configurations, clazz, main);
                }
            }
        });

        main.run(args);
    }

    private static void addConfiguration(Map<String, Class> configurations, Class clazz, KameletMain main) {
        if (configurations.get(clazz.getCanonicalName()) != null) {
            System.out.println(clazz.getCanonicalName() + " already registered");
            return;
        } else {
            configurations.put(clazz.getCanonicalName(), clazz);
        }

        try {
            main.configure().addConfiguration((CamelConfiguration) clazz.newInstance());
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

as the downloading happens before the Kametet runs, but the question is how to force KameletMain start accounting for configurations?
The line
            main.configure().addConfiguration((CamelConfiguration) clazz.newInstance());

doesn't have an effect

you need to create the clazz instance via camel and not plain java - see injector on camel context

I created a ticket about scanning downloaded JARs
https://issues.apache.org/jira/browse/CAMEL-18815

Thank you a lot, @davsclaus, the injector helped
            CamelContext camelContext = main.getCamelContext();
            if (camelContext != null) {
                Object clazzInstance = main.getCamelContext().getRegistry().findSingleByType(clazz);
                if (clazzInstance != null) {
                    System.out.println(clazz.getCanonicalName() + " already registered");
                    return;
                }

                Injector injector = camelContext.getInjector();
                main.configure().addConfiguration((CamelConfiguration) injector.newInstance(clazz));
            } else {
                System.err.println("CamelContext is not defined");
            }

Could you also clarify, is such approach, when dependency is defined through the Kamelet, actually the way how it has to work once deployed to K8S / Camel K ?

My goal with KameletMain is a transition from Spring Boot with Camel and camel route resource being deployed to K8S.
Is there any 'executive summary' documentation, which explain the benefits of Camel K as opposed to Spring Boot + Camel?

Camel K is not able to do all of this that camel-kamelet-main can do.
You can use camel-jbang and its 'export' command to export to camel-quarkus (what camel-k runs on top of) as a regular maven based project and deploy to k8s as a standard quarkus project.
For Camel K "benefits" then there is its website: https://camel.apache.org/camel-k/1.11.x/. And its better to ask on camel-k zulip chat room or user mailing list instead of issue tracker.
Closing this ticket