Defender CREATE2  inconsistent address

I am deploying 3 contracts using 3 different defender functions to 3 test networks. But somehow, the addresses in Ethereum Sepolia are different from Base Sepolia and Polygon Mumbai when using deployImplementation and deployProxy. deployContract produces consistent address.
Here's the hardhat task to deploy the contracts.
import { task, vars } from "hardhat/config";

task("deployWithDefender", "Deploy all contracts with OpenZeppelin Defender")
  .addParam("salt", "Salt for CREATE2 to determine address of contract")
  .setAction(async (taskArgs, hre) => {
    const { salt } = taskArgs;
    const { ethers, defender } = hre;

    const owner = new ethers.Wallet(vars.get('PRIVATE_KEY'), ethers.provider);

    const coordinatorFactory = await ethers.getContractFactory("Coordinator", owner);
    const coordinatorParams = [owner.address, owner.address, owner.address];
    const coordinator = await defender.deployContract(
      coordinatorFactory,
      coordinatorParams,
      {
        salt
      }
    );
    await coordinator.waitForDeployment();
    const coordinatorAddress = await coordinator.getAddress();

    console.log(`Deployed Coordinator at ${coordinatorAddress}`);

    const collateralFactory = await ethers.getContractFactory("Collateral", owner);
    const collateralAddress = await defender.deployImplementation(
      collateralFactory,
      {
        salt
      }
    );

    console.log(`Deployed Collateral at ${collateralAddress}`);

    const factoryFactory = await ethers.getContractFactory("Factory", owner);
    const factory = await defender.deployProxy(
      factoryFactory,
      [coordinatorAddress, collateralAddress, owner.address, []],
      {
        initializer: "initialize",
        salt,
      },
    );
    factory.waitForDeployment();
    const factoryAddress = await factory.getAddress();

    console.log(`Deployed Factory at ${factoryAddress}`);
});

And here are the addresses from the code above.
ethereum sepolia
deployContract        0x3b3D50f73623a8A56F26879849C94D6491E85563
deployImplementation  0x710D1de8E335842642F619c6032BfD81232748F4
deployProxy           0x12354D65D4FB82739cEc19957B09826b53deAC66
base sepolia
deployContract        0x3b3D50f73623a8A56F26879849C94D6491E85563
deployImplementation  0xF14b88C28343f3Bb0a27430F4f287D13564158e9
deployProxy           0xCa8EB5A75D868d1f0dEC0B577877F909cD2f3Ee3
mumbai
deployContract        0x3b3D50f73623a8A56F26879849C94D6491E85563
deployImplementation  0xF14b88C28343f3Bb0a27430F4f287D13564158e9
deployProxy           0xCa8EB5A75D868d1f0dEC0B577877F909cD2f3Ee3
I am using "@openzeppelin/hardhat-upgrades": "^3.0.5"

I tried again. And this time, it was consistent. Was there anything happened with the pipeline when it produced a different addresses?
ethereum sepolia
deployContract 0x7f3e8b44f75b3C640E843434AF972A913e6926b1
deployImplementation 0x80f7230a3674a97A6E1636261221093A5e5b8225
deployProxy 0x0aCB6f41aD3c42F004b21C3F5C8d041424A2b690
base sepolia
deployContract 0x7f3e8b44f75b3C640E843434AF972A913e6926b1
deployImplementation 0x80f7230a3674a97A6E1636261221093A5e5b8225
deployProxy 0x0aCB6f41aD3c42F004b21C3F5C8d041424A2b690
mumbai
deployContract 0x7f3e8b44f75b3C640E843434AF972A913e6926b1
deployImplementation 0x80f7230a3674a97A6E1636261221093A5e5b8225
deployProxy 0x0aCB6f41aD3c42F004b21C3F5C8d041424A2b690

My bad. Thanks for checking.


Virtual Sky

When I click on the virtual sky icon  I do not see the virtual sky show up on the image.
Any idea what may be causing this?
Mike
n3bsq.com/allsky

If you are referring to the constellation overlay it worked for me on your site under both Safari and Firefox.


Support for OIDC Auth

Twitch Supports OIDC Authorization with custom claims
https://dev.twitch.tv/docs/authentication/getting-tokens-oidc/
It would be nice to support the OIDC auth method.
I suggest to implement https://github.com/coreos/go-oidc, to instead do :

The code exchanging
ID_TOKEN verification
Supports the ability to extract the custom OIDC claims!

MISC:

Add ability to get a Auth OIDC url, from helix.GetAuthorizationURL

https://github.com/nicklaw5/helix/pull/118


_pickle.UnpicklingError: invalid load key, '\x08' when load ICVL dataset you provided in BaiduDisk

The dataset you provided is arranged as follow

but when run your script to retrain will raise this kind of error.
File "/htrainer. Trainng/Desktop/Project/HSIR/hsirun/train.py", line 78, in main     if trainer.epoch < 30: trainer.train(train_loader1)   File "/home/tanxiaodong/Desktop/Project/HSIR/hsir/trainer.py", line 175, in train     for batch_idx, data in enumerate(train_loader):   File "/home/tanxiaodong/miniconda3/envs/hsir/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 633, in __next__     data = self._next_data()   File "/home/tanxiaodong/miniconda3/envs/hsir/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1345, in _next_data     return self._process_data(data)   File "/home/tanxiaodong/miniconda3/envs/hsir/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1371, in _process_data     data.reraise()   File "/home/tanxiaodong/miniconda3/envs/hsir/lib/python3.10/site-packages/torch/_utils.py", line 644, in reraise     raise exception _pickle.UnpicklingError: Caught UnpicklingError in DataLoader worker process 0. Original Traceback (most recent call last):   File "/home/tanxiaodong/miniconda3/envs/hsir/lib/python3.10/site-packages/torch/utils/data/_utils/worker.py", line 308, in _worker_loop     data = fetcher.fetch(index)   File "/home/tanxiaodong/miniconda3/envs/hsir/lib/python3.10/site-packages/torch/utils/data/_utils/fetch.py", line 51, in fetch     data = [self.dataset[idx] for idx in possibly_batched_index]   File "/home/tanxiaodong/miniconda3/envs/hsir/lib/python3.10/site-packages/torch/utils/data/_utils/fetch.py", line 51, in <listcomp>     data = [self.dataset[idx] for idx in possibly_batched_index]   File "/home/tanxiaodong/Desktop/Project/HSIR/hsir/data/dataset.py", line 74, in __getitem__     img = self.dataset[index]   File "/home/tanxiaodong/Desktop/Project/HSIR/hsir/data/dataset.py", line 162, in __getitem__     x = pickle.loads(raw_datum) _pickle.UnpicklingError: invalid load key, '\x08'.

you could try to change backend to caffe
https://github.com/bit-isp/HSIR/blob/bea25d05efa8f8ac1195cb874190fce0d0e1333e/hsir/data/dataset.py#L137
I might upload the caffe version. I will check it and upload the pickle version as well later.


Provide tensorboard logs

Could you please share your tensorboard logs of some trained representative models like: voice-en-us_lessac.tar.gz, voice-en-us_libritts.tar.gz (Ex. via https://tensorboard.dev) so that we can align our training progress with yours to know how much training time we may needed?

Thank you :hugs:

Hi @synesthesiam, I've run training script for about a day (162 epoch now), why do tensorboard just show last log is epoch 2?

For those who encountered above tensorboard misbehavior, it may be due to installation problem of tensorboard. Using another installation, I was able to view it correctly


Fix of Duplicate Job Creation in Databricks During Airflow DAG Runs

Airflow DAG executions may create duplicate workflows in the Databricks workspace even when the job already exists. This PR resolves this issue by leveraging the built-in job name filtering feature of the Databricks REST API within the jobs_api.list_jobs() method in workflow.py/_get_job_by_name.
closes: https://github.com/astronomer/astro-provider-databricks/issues/75

Hi @pankajkoti, thanks for your review. I've thoroughly tested this change in our development environment, testing 5 different jobs both before and after implementing the updates. This included testing 2 existing jobs that previously couldn't return a job id via the original REST API call. I can confirm that the changes successfully resolve the issue. We're ready to proceed with the merge. Thanks again for your support.

Thanks @Hang1225 for the contribution. The PR has been merged and will be included in the next release.
I modified the PR title and description a bit to elaborate it further 🙌🏽

Thank you again @pankajkoti! Would you be able to share the timeline for the next release? I'd like to update our teams on when to expect the fix.

Hi @Hang1225 thanks, I will work on the release soon. Expected ETA before EOD tomorrow 17th April, 2024 IST

Hi @Hang1225 , we just released https://pypi.org/project/astro-provider-databricks/0.2.2/ which includes this PR. Please try it out and let us know how it works. Thanks again for contributing this fix!


Mod Menu not opening

Mod menu looks great and I'm excited for it, but on 2.203, Tab won't open it, and I've pressed every other key. What keybind opens the menu?
Thanks in advance! :D

I think you might have installed it incorrectly, because everything should work fine on any game version.
Could you provide a screenshot of your game directory?

Thanks, I'm pretty sure I installed the Release Zip, but it's working now. No idea what happened, but thanks! :D


Unhandled Exception in ProxyServer, Couldn't authenticate host 'play.google.com' with certificate '*.google.com'

Hi Team,
whenever I debug, I'm getting this error. Could you please guide me to fix this issue?
Unhandled Exception in ProxyServer, Exception = Titanium.Web.Proxy.Exceptions.ProxyConnectException: Couldn't authenticate host 'play.google.com' with certificate '*.google.com'. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Net.Security.SslStream.EndAuthenticateAsServer(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Titanium.Web.Proxy.ProxyServer.d__0.MoveNext()
--- End of inner exception stack trace ---
at Titanium.Web.Proxy.ProxyServer.d__0.MoveNext()

@honfika , Do we have any updates on this?


Edit ETH address: withdraw using the native Axelar integration

Context
When withdrawing using the native Axelar integration, the transfer modal currently supports switching wallet extensions.

Instead/in addition we can support edit to any address as we do for Withdraw IBC asset.

Possible solution
Withdraw supports edit to any ethereum address. Deposit still allows switching between ethereum wallets

Tradeoffs, drawbacks, and suggested alternative
However, there is a UX drawback to this solution. Novice users likely only want to withdraw to wallet addresses they have access to through wallet extensions. Supporting an edit feature exposes them to accidentally entering incorrect addresses, possibly losing their funds.

If an advanced user's only goal is to connect and withdraw to a non-MM wallet extension, it's possible this issue will be resolved by the addition of web3modal.
If advanced users seek to withdraw assets to specific addresses, it may be optimal to protect novice users and have those advanced users send to specific addresses from their respective wallets post-withdraw from Osmosis (trade-off: gas costs, UX for advanced users).
If Osmosis were to add more wallet-like capabilities, as @jonator mentioned, this could be sectioned off into a send/receive feature.

Note: we already support users switching multiple accounts within MetaMask

Note: this requires regeneration of Axelar deposit address. We may want to user a less dynamic UI because of this.

It's not a big deal to generate new deposit addresses, it just takes time. According to Axelar.


Hypercore 8 Upgrade

This PR updates the replicate API to support Hypercore v8. It also includes the top-level alwaysUpdate, which will perform an update({ ifAvailable: true }, ...) before every head operation.

4.0.0


Show on App Launch: Disable text entry when Specific Url not selected

Task/Issue URL: https://app.asana.com/0/1207908166761516/1208685892092430/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5236  👈
#4944 : 5 other dependent PRs (#4946 , #5050 , #5127  and 2 others)
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mikescamell and the rest of your teammates on  Graphite


api: add comments when admins performs manual actions on task or resolution

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature

What is the new behavior (if this is a feature change)?
When a human operator modifies a task or a resolution, through a manual action, comment is added to indicate that the task/resolution have been manually modified (audit log like)

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:

LGTM. Proposed comments alternatives.

Comments addressed.


decorator: Remove unused Union.

The other variant of possible return type was removed in
7c9e8a50718f7a4c79a1f3c92d97c45cbf5af070, but the return type is not
accurately reflecting that.

Fixes:

Screenshots and screen captures:
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @PIG208!


Organize the Examples Folder

Outline & Motivation
Our examples folder is messy, it currently looks like this: https://github.com/Lightning-AI/lightning/tree/master/examples
It does not matter if you are an expert or a beginner, if you arrive here in this repository, the examples folder sticks out as an obvious place to start exploring. But it's a mess. Where to start? What is important? What is new, what is old? The Readme is outdated.
Pitch
Organize the top level folders into:
examples/
    app
    fabric
    pytorch

Organize the readme, either at the top level or in each subfolder, with sections for
Beginner
Intermediate
Expert
(or a similar structure organized by concepts).
Delete examples that are too outdated or irrelevant. Make everything as concise as possible.
Additional context
No response
cc @borda @justusschock @awaelchli

that sounds good to me, just would split the app into app and component
or we can still utilize the prefix to keep it rather flat?
examples/
    app_...
    component_...
    fabric_...
    pytorch_...

I think we should get rid of the distinction, every component should be runnable in isolation (as a simple app), so I'd just keep app

Just like @awaelchli suggested
examples/
    app
    fabric
    pytorch

inside app, just have the current app examples (no need to further split between app and component, that was my suggestion)

Would be happy to take this one.

@andrewaf1 the stage is yours :)

@andrewaf1, how is it going, can I help somehow? :)

So, I've been going through everything, making sure everything makes sense, is relevant, runs according to the readme instructions, etc.
I wanted to clarify what is going to go into the "pytorch" folder. Is that supposed to be the examples with a "pl_" prefix (in which case the folder should be called something else, right?) Or is that intended to contain the plain pytorch examples that are bundled with the fabric examples?

And another thing that has me a little confused. One of the examples throws the error:
Traceback (most recent call last):
  File "/home/andrew/lightning/examples/pl_basics/autoencoder.py", line 26, in <module>
    from pytorch_lightning import callbacks, cli_lightning_logo, LightningDataModule, LightningModule, Trainer
ImportError: cannot import name 'callbacks' from 'pytorch_lightning' (unknown location)

I can do from lightning.pytorch import callback successfully. I feel like I'm not up to speed on something here.

@andrewaf1 Good questions. Yes you are right, with the pytorch folder we mean anything that was previously prefixed with pl_. The PyTorch Lightning examples. The Lightning package, as it currently is on master, will have these three modules:
lightning.app: The app framework
lightning.pytorch: What was previously pytorch_lightning
lightning.fabric: The new Fabric code base
This is what motivates the new example structure I proposed. The examples/fabric folder already follows that pattern, so this, and the pure torch files inside of it, can be left as they are.

I can do from lightning.pytorch import callback successfully. I feel like I'm not up to speed on something here.

This is simply because the imports in the examples haven't been updated yet. from pytorch_lightning import should become from lightning.pytorch import x. This will get done in #16615.

@andrewaf1, how is it going here? :)

hey @Borda, please assign this issue to me. Would love to work on this!


Unable to add multiple entries for Alert configurations at the same time in Publisher and Dev Portal with API Manager 3.2.0

Description:
When we try to add multiple entries at the same time for Alert Configurations in Publisher and Dev Portal, the '+' mark will be disabled.
Steps to reproduce:

Go to Publisher Portal -> Settings. Then click the Settings button of 'Abnormal Response Time' and then click '+ New Configuration'.
After adding API Name, Version and 'Abnormal Response Time', click + mark to add. The entry should be successfully added and displayed in the list.
Then again click '+ New Configuration' and try to add another entry but the '+' mark is disabled.

This is common for 'Abnormal Backend Time' in publisher and 'Abnormal Requests per Minute' in Dev Portal as well.

Affected Product Version:
API Manager 3.2.0

We can close this issue since this is not reproducing in master.


fix(amplify-category-auth): fixed the comparison process between appC…

Description of changes

This is a PR to solve the following problem.
https://github.com/aws-amplify/amplify-cli/issues/7821
Removed the process of checking whether the callback URL and logout URL of appClientWeb and appClientNative match.
Issue #, if available

https://github.com/aws-amplify/amplify-cli/issues/7821
Description of how you validated changes
Sorry, I wanted to test it, but I couldn't figure out how to build the changes and test them manually.
Checklist

[x] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #7822 (8ff13e5) into master (f3eae13) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7822      +/-   ##
==========================================
+ Coverage   53.27%   53.28%   +0.01%
==========================================
  Files         555      555
  Lines       28023    28017       -6
  Branches     5429     5427       -2
==========================================
  Hits        14929    14929
+ Misses      12110    12106       -4
+ Partials      984      982       -2

Impacted Files
Coverage Δ

...c/provider-utils/awscloudformation/import/index.ts
5.07% <ø> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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

Have you checked out our contributing guide? We also have a discord community where you can ask questions in more real-time. It would be nice to have a test to prevent regressions.

Specifically, you can run yarn setup-dev which will allow you to manually test via amplify-dev [cmd]
Automated jest tests can be added in packages/amplify-category-auth/src/__tests__/provider-utils/awscloudformation/utils/
What I don't want is the next time someone changes the validation, it breaks your use case. So make sure your use case that is broken now is specifically handled in the test.

I'm closing this pull request since it hasn't seen any movement for a few months. The tests do not pass as written and the approach of removing those checks won't work on its own since they're useful generally. @EringiV3 if you're still interested in contributing please reach out in our discord and we can discuss an approach!


New sound footsteps synced with foot position [WIP]

This is still work in progress.
Footsteps are now synced with ankle local position.
With this new PR old one https://github.com/webaverse/app/pull/1996 is not needed.

This was bugged and has long been superseded by an animations-based footstep detection system.


ios 8.1 xcode 6.1 compatible.

Interesting! Is a y-max constraint part of the original flappy bird? That said, I'm not sure we need to add it - it seems like an edge case we don't necessarily need to handle in this demo app.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3513

Questions ?
Please refer to the Backport tool documentation


MSDF Generator leaves holes in Tilt Fonts

Godot version
4.1.1.stable
System information
Windows 11 - 4.1.1.stable
Issue description
Certain fonts generate with holes in the faces of some of the types.
This bug is possibly specific to Tilt Fonts, https://github.com/googlefonts/Tilt-Fonts
I have only tested the TrueType format.
A reproduction project is attached.
An example Font is is TiltNeon, the font rendered in the picture and sample project, it is available under the SIL Open Font License here for testing and reproduction: https://fonts.google.com/specimen/Tilt+Neon

Steps to reproduce

Import the Attached Reproduction Project and open reproduction.tscn

OR:

Import the TiltNeon-Regular.ttf font, available here:  https://fonts.google.com/specimen/Tilt+Neon

Write a word like "Metis" in large type.

Observe holes int he letters M and e.

Minimal reproduction project
godot-tilt-font-reproduction.zip (52kb)

This is usually caused by self-intersections in the font, which is a font bug.

"It's a feature" - the font is actually not self-intersecting, the glyph is 3 dimensional.
(though indeed, its 2D projection is likely self-intersecting)
The source is originally https://github.com/googlefonts/Tilt-Fonts
I can totally understand that this is probably so specific this can get closed as "won't fix", but maybe there is some interest in this by the community. It is probably outside the scope of the engine to make the fonts render as intended (3D), but their desired 2D behaviour could be achieved.

I assume groud meant 2d profile when he said the font is self-intersecting - AFAIK the 3d mesh/msdf generator works based on 2d profiles.

There's a fix, but it requires a lot of code to fix a rare issue with non-compliant fonts (self intersections are not allowed by OpenType standard), so it's unlikely it will be ever merged - https://github.com/godotengine/godot/pull/61555

I actually shipped the repro project with the 2D version of this font, not the YROT/XROT version, so - yes, that font file apparently self-intersects. (but the 3D version displays the same issue)
Since OpenType covers this as in violation of the standards, I'll just close this, as that's the killer argument.


T1

pending:T1
account1:4fHiFr1YDL8hAHkoaN1AkmneXTRorMmdjqEshkPNnhzPJndhow
account2:42x3nb1xnVPEqbQv7p6rwrBnxkFQ3FhuCCm4YwRmGRr46y5sUD
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots with all transactions.
@foreva73

pending:T1
account1:4fHiFr1YDL8hAHkoaN1AkmneXTRorMmdjqEshkPNnhzPJndhow
account2:42x3nb1xnVPEqbQv7p6rwrBnxkFQ3FhuCCm4YwRmGRr46y5sUD
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots with all transactions.
@foreva73

screenshots were not required in the task!
On Tue, Jan 12, 2021 at 2:55 PM Suhas Hegde<EMAIL_ADDRESS>wrote:

pending:T1
account1:4fHiFr1YDL8hAHkoaN1AkmneXTRorMmdjqEshkPNnhzPJndhow
account2:42x3nb1xnVPEqbQv7p6rwrBnxkFQ3FhuCCm4YwRmGRr46y5sUD
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots
with all transactions.
@foreva73 https://github.com/foreva73
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Concordium/Testnet3-Challenges/pull/1405#issuecomment-758608182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMXEJWD7LRPGM7JOORWARKTSZQ2EHANCNFSM4TKV6E5A
.

screenshots were not required in the task!
On Tue, Jan 12, 2021 at 2:55 PM Suhas Hegde<EMAIL_ADDRESS>wrote:

pending:T1
account1:4fHiFr1YDL8hAHkoaN1AkmneXTRorMmdjqEshkPNnhzPJndhow
account2:42x3nb1xnVPEqbQv7p6rwrBnxkFQ3FhuCCm4YwRmGRr46y5sUD
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots
with all transactions.
@foreva73 https://github.com/foreva73
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Concordium/Testnet3-Challenges/pull/1405#issuecomment-758608182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMXEJWD7LRPGM7JOORWARKTSZQ2EHANCNFSM4TKV6E5A
.

confirmed:T1
account1:4fHiFr1YDL8hAHkoaN1AkmneXTRorMmdjqEshkPNnhzPJndhow
account2:42x3nb1xnVPEqbQv7p6rwrBnxkFQ3FhuCCm4YwRmGRr46y5sUD
DeviceDetails:verified

confirmed:T1
account1:4fHiFr1YDL8hAHkoaN1AkmneXTRorMmdjqEshkPNnhzPJndhow
account2:42x3nb1xnVPEqbQv7p6rwrBnxkFQ3FhuCCm4YwRmGRr46y5sUD
DeviceDetails:verified


disable and grey out days that do not belong to specific month

As the title described....i don't know if this is a bug or a feature, but at the npm page of the package, screenshot demonstrates such a thing... in reality it doesn't

just edited the css...the "outside month" class was there


CI=true is not working, composer install failing without .git folder

My company recently started using CaptainHook and have a shared testing server that we deploy to via Envoyer. This environment needs to have development packages installed for testing purposes which causes the composer install command to fail with the following error.
[RuntimeException]
Shiver me timbers! CaptainHook could not install yer git hooks! (git directory not found)

This makes sense due to the deployment not including the .git folder. When searching I found #13 and the corresponding PR which should allow us to set CI=true in our .env file, however this is having no effect.
Is there any other way to disable CaptainHook on a per-environment basis?
On a related note, I'm also worried what other effects setting CI=true would have since this environment isn't strictly for CI. Would you accept a PR that adds a specific environment variable for disabling CaptainHook only (i.e. DISABLE_CAPTAINHOOK)?

I'm assuming you are using either the plugin-composer or captainhook-phar package.
The issue for you is that those Composer plugins will always at least try to install the hooks.
You can execute Composer like this
composer install --no-plugins

As long as you are not using any other plugins that you need to execute this will disable all plugins and the Cap'n will not install the hooks.

Yes, we're using plugin-composer. The --no-plugins option is a good idea however it looks like we don't have control over this from Envoyer. :slightly_frowning_face: It would still be nice to have an environment variable specifically for Captainhook.

I just pushed plugin-composer version 5.3.3 with the option to use the environment variable CAPTAINHOOK_DISABLE set to true to disable the plugin completely.
So you should be good to go if you run a composer update and setup the environment variable.
Hope that helps ;)

Awesome, thank you!


not possible to make description window to shrink

cannot get the description window to shrink. I can make it bigger, but not
smaller. I'm using three 27 inch monitors in extended mode. See linked
image.
http://screencast.com/t/z12ctWvu7q
156815

Will be resolved with edit view redesign


NM 1.22-git copr repo GPG key is not working

It would be nice to track NM 1.22-git as an optional Travis job but CI is failing due a GPG key error. The error is the following one in the centos8-nmstate-dev container image:
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
Public key for NetworkManager-1.22.5-24625.1bb3ee4c55.el8.x86_64.rpm
is not installed. Failing package is:
NetworkManager-1:1.22.5-24625.1bb3ee4c55.el8.x86_64
 GPG Keys are configured as:
https://copr-be.cloud.fedoraproject.org/results/networkmanager/NetworkManager-1.22-git/pubkey.gpg
Public key for NetworkManager-config-server-1.22.5-24625.1bb3ee4c55.el8.noarch.rpm
is not installed. Failing package is:
NetworkManager-config-server-1:1.22.5-24625.1bb3ee4c55.el8.noarch
 GPG Keys are configured as:
https://copr-be.cloud.fedoraproject.org/results/networkmanager/NetworkManager-1.22-git/pubkey.gpg
Public key for NetworkManager-libnm-1.22.5-24625.1bb3ee4c55.el8.x86_64.rpm
is not installed. Failing package is:
NetworkManager-libnm-1:1.22.5-24625.1bb3ee4c55.el8.x86_64
 GPG Keys are configured as:
https://copr-be.cloud.fedoraproject.org/results/networkmanager/NetworkManager-1.22-git/pubkey.gpg
Public key for NetworkManager-ovs-1.22.5-24625.1bb3ee4c55.el8.x86_64.rpm
is not installed. Failing package is:
NetworkManager-ovs-1:1.22.5-24625.1bb3ee4c55.el8.x86_64
 GPG Keys are configured as:
https://copr-be.cloud.fedoraproject.org/results/networkmanager/NetworkManager-1.22-git/pubkey.gpg
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

On docker.io/nmstate/centos8-nmstate-dev  with ID b1daa66b0acb the RPM db is broken for an unknown reason which makes RPM not find the GPG key:
[vagrant@nmstate-dev nmstate]$ docker run -it docker.io/nmstate/centos8-nmstate-dev /bin/bash
[root@4a1b3e9d7433 /]# rpm --verifydb
error: rpmdb: BDB0533 Page 2358: overflow refcount 1, referenced 0 times
error: rpmdb: Packages: BDB0090 DB_VERIFY_BAD: Database verification failed
error: db5 error(-30970) from db->verify: BDB0090 DB_VERIFY_BAD: Database verification failed

After building the container locally, the RPM db is not broken. Build steps:
cd packaging
docker build -f Dockerfile.centos8-nmstate-dev .

The RPM corruption is happening on the Docker hub build infrastructure:
https://hub.docker.com/repository/registry-1.docker.io/tyll/nmstate/builds/0fa134f5-52f6-4276-8cd1-9917a88b2c6e
We have two options: Try to use quay.io or to build the images manually on our systems AFAICS.

It also fails on quay:

RUNrpm --verifydb
4.2.2020, 12:37:21
4.2.2020, 12:37:21---> Running in 5ae0aded3b51
4.2.2020, 12:37:21error: rpmdb: BDB0533 Page 2358: overflow refcount 1, referenced 0 times
4.2.2020, 12:37:21error: rpmdb: Packages: BDB0090 DB_VERIFY_BAD: Database verification failed error: db5 error(-30970) from db->verify: BDB0090 DB_VERIFY_BAD: Database verification failed
4.2.2020, 12:37:22Removing intermediate container 5ae0aded3b51
 Dockerfile build failed

Another possible workaround:
Rebuild the container image on Travis for jobs to test against a different NM version.

Once this is fixed, we need to update the Travis jbos for NM-1.22-git if it is still there (see #778)

Could we close this then?

Could we close this then?

No, this is only an intermediate solution. We need something automatic in the future.


[DSheet] Missing feature for setting vertical balance parameters

There is no method for setting the maximum point resistance and xi factor that are needed for calculation the vertical balance.
The current work-around is setting the vertical balance properties directly as a string via model.datastructure.input_data.vertical_balance.
I've created functionality for setting these parameters but I think I need to be assigned as a contributer in order to create a new branch. Could you add me as a contributer?
Regards,
Daniël Kentrop

Hi Daniël,
Good to hear that your want to make your first contribution. There is no need to add you as a contributor. By creating a pull request, you can create a branch yourself. When your commits are done, we will review the code and we merge the pull request upon approval.
Please let me know, if you have any questions.
Regards,
Walter

Hi Walter,
Thanks for your explanation! I made a pull request #182 which fixes this issue. It is ready for review. Let me know if I should change or add anything.
Regards,
Daniël


Missing function

Missing function:
Physique Rating
Visceral Fat
Metabolic Age
Caloric Intake
Please, add them.
Best Regards,
Robert

Thank you for your attention, @Jufo84,
why do you want these changes to be made?
These values are not shown in Garmin Connect as far as I know.
Best Regards,
David

They are visible and partly synchronized by Weight Logger (https://github.com/kochka/WeightLogger):
http://icebox.pl/garmin.png

Ah ok, thanks for your explanation, I've never really noticed these values in the web frontend, because I mainly use the Android app.
Your idea of connecting things sounds just great and seems to be very interesting. Is this project somewhere available on Github?
I assume you do not have knowledge of Golang, do you?
I'll work on this feature soon, it should not be that time-consuming.
Regards,
David

I don't know yet how to do it, probably based partly on https://github.com/rando-calrissian/esp32_xiaomi_mi_2_hass/blob/master/appdaemon/apps/xiaomi_scale.py wants this data to be sent by your program . I will probably create a project in github (I haven't done it yet), but only when I have your part complete, is there a chance to add these parameters ?
Best Regards,
Robert

I'm currently working on this feature, but the caloric intake doesn't get recognized, same as in your screenshot.
I also found out that those fields do not show up, when there are no values behind them, like it always was in my case
Regards,
David

The Weight Logger has the same problem, it cannot send the Caloric Intake parameter, maybe it is not possible yet :(


74 merkle tree and proofs

Description

Support public key and IP address whitelisting for event rate limits

Related Issue

https://github.com/Cameri/nostr-ts-relay/issues/74
Motivation and Context

Allow relay operator to mirror without hitting event rate limits

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Non-functional change (docs, style, minor refactor)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my code changes.
[ ] All new and existing tests passed.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

7 of 7 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 88.027%

Totals

Change from base Build<PHONE_NUMBER>:
0.5%

Covered Lines:
832

Relevant Lines:
937

💛  - Coveralls


Website links don't have Salt focus ring styles

Latest version

[X] I have tested the latest version

Description
Raised in #4312, doc links are using Salt focus style
Steps to reproduce
Tab through heading / links
https://www.saltdesignsystem.com/salt/components/button/examples
Expected behavior
No response
Browser

[X] Chrome
[ ] Safari
[ ] Firefox
[ ] Microsoft Edge

Operating system

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

Are you a JPMorgan Chase & Co. employee?

[X] I am an employee of JPMorgan Chase & Co.

This is fixed on main due to #3448

Closing this as should be fixed now


Official Savage Worlds: Bug fixes - encumbrance penalty, token displa…

…y, specialization

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Bug Fixes

Fixed encumbrance issues. The encumbrance penalty is no longer applied to all attributes and it now automatically subracts 2 from Pace and running rolls.
Fixed an issue where dice rolls for skill specialization were not appearing.
Fixed a bug that showed the token on damage rolls when "Show Token with Roll Template" was unchecked.

@rpgnerdz is approved to make edits to the Official Savage Worlds character sheet.


Which value should I use to measure CPU load and network bandwidth ?

I'm writing a simple load balancer. I have some nodes (servers), and each node will report cpu load and network bandwidth (my code using module systeminformation) to load balancer.
Which value should I use to measure CPU load and network bandwidth in each node?

CPU
avgload or currentload or os.loadavg()

Network bandwith
rx_sec + tx_sec or only tx_sec

@kietheros I am not sure, what your approach is here and if it would make sense to use these values in a load balancer ...
I would consider two approaches:

In a load balancer you can determine on parameters that happened right now (so basically in that millisecond or so). avgloador currentload are not that accurate. So when you get a result, a few milliseconds the situation can be completely different.

Or you would like to make decisions in your load balancer based on more general - average - parameters ... then you can of course use avgload or currentload. avgload is based on what nodejs gives back for the cpu. I created the currentload() function because this is the more accurate and you can control it much better. Be sure, that this gives back the real load between two calls of currentload. So if you call this every second, it will give you back the load in this past second.
Concerning network bandwidth. I would - depending on your use case - use both values separately. You probably would like to be in control of received AND send bytes. Depending on the network both could be a bottleneck. But this is for sure much more complex because this would also mean, that you know about the overall bandwidth (read AND write) of the network where your services are hosted. If you e.g. make a load balancing between two machines in one network and the external connection is the bottleneck, your load balancing would be kind of independent of what is going on in one of the two machines. If the bandwidth of machine 1 hits the limits of the external network, then you would also get no gains when you switch to the other machine (behind the same external network). So the network topology would play a rule here also.

So in both cases I am not really sure if your approach really is the best ...
Hope my explanation make some sense for you. Perhaps you can describe your idea here more detailed.

@sebhildebrandt Thank for your reply !
I have just updated my questions. I think using average load is suitable. After reading your reply, I have a bit of a misunderstanding about load average and cpu utilization. Please correct me if I'm wrong

currentload: the current cpu utilization, unit: percent

os.loadavg() or value in htop: load average in last 1, 5 and 15 minutes. I will use load average / number of cores to convert to percent.

avgload: I don't sure about this value. Perhaps like value in htop (load average), measure between 2 calls of this function

About network bandwidth, I will use rx_sec + tx_sec because my node both sends and receives data.

@kietheros so this is nearly correct ...

currentload: the current cpu utilization, unit: percent ... dependent on calls to this function (as described above)
avgload : this is actually the average of 1, 5 and 15 min load average / number of cores ... independent of calls of this function

@sebhildebrandt
Thank for your reply. I try using two below values:
currentload
I save currentload in each second.
value1 = calculate average currentload in last 60s. (%)
avg
value2 = avg * 100. (%)
I find that value2 is much larger than value1 (value1 ~ 20 -> 25,  value2 ~ 70). Which value should I use to represent cpu load? Which value does services as HAProxy use ? I'm a newcomer, could you tell me your selection ?

@kietheros and what is compared to that the first value of os.loadavg() / number of cores?

Result:  systemiformation avgload ~  os.loadavg() / number of cores

@kietheros how many cores you have and how many threads?

{
use_average_of_currentload: 23.722149410222805,
use_avg: 78,
use_os_loadavg: 78.070068359375
}
os.cpus().length = 8
(I have checked in htop, 8 cores / 8 threads)

const listCpuLoads = []; si.currentLoad(async (data) => {             if (listCpuLoads.length >= 60) {                 listCpuLoads.shift();             }             listCpuLoads.push(data.currentload);             results.average_of_currentload = getAverage(listCpuLoads);             results.avg = data.avgload * 100;             results.os_loadavg = os.loadavg()[0] / os.cpus().length * 100;         });
{   average_of_currentload: 24.586460869366967,   avg: 60,   os_loadavg: 60.009765625  }

@kietheros so this is absolutely fine!
Pleas consider, that os loading is NOT a percentage value!! It is more about running and waiting threads:

Linux load averages are "system load averages" that show the running thread (task) demand
on the system as an average number of running plus waiting threads. This measures demand,
which can be greater than what the system is currently processing

my currentload-function on the other hand IS a percentage value!
So is makes no sense to compare the two values directly.

@sebhildebrandt
OK. I only consider which value is better for represent the system load. In your opinion, which one is better ?

@kietheros

if you want to make decisions on the true percentage values - go for currentload
if you just want to compare and take the lowest, take os.loadavg()[0] as this is probably faster

@sebhildebrandt Thank you very much ! I will use currentload.

avgload : this is actually the average of 1, 5 and 15 min load average / number of cores ... independent of calls of this function

@sebhildebrandt would it be possible to expose the raw min1 min5 and min15 load numbers too? As far as I can see they are currently not exposed.

@fabiospampinato that would make sense ... will extend si.currentLoad() to provide those values too.

@fabiospampinato the question here is: would it really make sense

to just provide the 1, 5 and 15 min numbers (as given from the OS) which needs extra calculation to give meaningful results
or should I provide my post-calculated results (which means already divided by CPU cores) ...
What do you think?

Potentially providing both kind of values could be the optimal option, but for my use case specifically I want to recreate the load sections that tools like top or glances have, for that I think I need the value provided by the OS, I personally don't care too much about the per-core loads (although that could come in handy to me in the future).

@fabiospampinato

the first one (average of 1, 5 and 15 min load average - given by the OS) can be determined directly in nodes with os.loadavg() - so for your purposes actually no need to extend systeminformation
but I will introduce a avgload (levied by cores) because this is - at least to me - more meaningful.

Explanation: If the avgload given by the OS is high but you have plenty of cores, this might be not a big problem. In relation to just 1 or two cores, this really shows that your system is under pressure.

os.loadavg()

I wasn't aware that existed, thanks for pointing that out!
That's certainly good enough for me, but I think it would be cleaner if this library provided all that sort of data directly, using multiple libraries to get information about the system like that is kind of ugly.


Add "Composer Preload" plugin

Hi Jens,
Please consider adding "Composer Preload" plugin to the list.
This is a shameless self plug, but I genuinely believe this plugin serves a useful purpose. It adds a new "composer preload" command that, when run, creates a vendor/preload.php file that can cache a configurable list PHP files to opcache, speeding up execution of the app.
This can come really handy when phone 7.4 comes with Preload RFC implemented.
Thanks,
Ayesh.

Hey Ayesh,
so, the generated file contains a list of opcache_compile_file() entries.
And in the end you would set opcache.preload=vendor/preload.php or trigger this from the app itself, right? Ok, why not... it's an alternative to https://github.com/jderusse/composer-warmup
Referencing the Preload RFC: https://wiki.php.net/rfc/preload
Thanks for contributing. 👍
Regards Jens

Thanks, the other plugin looks pretty interesting too, although it has a different approach to warm up.
Thanks for accepting the PR!
Cheers
Ayesh.


Add ID localization of force delete stateful pod

Add ID localization of task force delete statefulset pod. Issue #22296

Awesome, thanks for the contribution 😎
/approve


[1.17] gateway deployment controller: handle backwards compatibility

This introduces a mechanism to tell older versions to stop managing a Gateway.
How this works:
1.17 controls all Gateways. Users will upgrade to a patched version (basically this PR backported) which annotates all Gateways with version=1. It also has logic to not control Gateways with version>1
User installs 1.18 as canary revision. Any Gateways in canary revision will get version=2 set; at this point, the 1.17 controller will stop trying to manage it. Warning: if a user needs to remove 1.18 at this point, they would need to manual set the version label back to 1. This is not ideal, but it is the best we can do I think.
User makes 1.18 the "default revision". At this point it does the same as above, but to a wider set of gateways.
Eventually, if we somehow run into the same circumstance, we can change the logic again to version=3 in some future version and completely change how we do gateway ownership. That is, this solution is future proof.
This introduces forward compatibility with 1.18+.
This pr is nearly a cherrypick of https://github.com/istio/istio/pull/44174, but there are a few differences (due to code drift, this one has version=1 set).

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.17
62550dc8ca226c2e3cb79d4343bdf33fe5304630
link
true
/test unit-tests-arm64

unit-tests_istio_release-1.17
62550dc8ca226c2e3cb79d4343bdf33fe5304630
link
true
/test unit-tests

lint_istio_release-1.17
2366bbb198f260961452ff15d519cd5bdd5368bc
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I believe we may want to hold this out until we can get the new annotation added in istio/api, else we will see Unknown Annotation errors in istioctl analyze.

/cherrypick release-1.16

@howardjohn: #44171 failed to apply on top of branch "release-1.16":
Applying: Future proof Gateway deployment controller
Using index info to reconstruct a base tree...
M	pilot/pkg/config/kube/gateway/deploymentcontroller.go
M	pilot/pkg/config/kube/gateway/deploymentcontroller_test.go
M	pilot/pkg/config/kube/gateway/testdata/deployment/cluster-ip.yaml
M	pilot/pkg/config/kube/gateway/testdata/deployment/manual-ip.yaml
A	pilot/pkg/config/kube/gateway/testdata/deployment/manual-sa.yaml
M	pilot/pkg/config/kube/gateway/testdata/deployment/multinetwork.yaml
M	pilot/pkg/config/kube/gateway/testdata/deployment/simple.yaml
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/config/kube/gateway/testdata/deployment/simple.yaml
Auto-merging pilot/pkg/config/kube/gateway/testdata/deployment/multinetwork.yaml
CONFLICT (modify/delete): pilot/pkg/config/kube/gateway/testdata/deployment/manual-sa.yaml deleted in HEAD and modified in Future proof Gateway deployment controller. Version Future proof Gateway deployment controller of pilot/pkg/config/kube/gateway/testdata/deployment/manual-sa.yaml left in tree.
Auto-merging pilot/pkg/config/kube/gateway/testdata/deployment/manual-ip.yaml
Auto-merging pilot/pkg/config/kube/gateway/testdata/deployment/cluster-ip.yaml
Auto-merging pilot/pkg/config/kube/gateway/deploymentcontroller_test.go
Auto-merging pilot/pkg/config/kube/gateway/deploymentcontroller.go
CONFLICT (content): Merge conflict in pilot/pkg/config/kube/gateway/deploymentcontroller.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Future proof Gateway deployment controller
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-1.16

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn: new issue created for failed cherrypick: #44215

In response to this:

/cherrypick release-1.16

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Bug: Signup page errors when signing up new pod

Bug Title: [Bug] Signup page errors when signing up new account

Bug Description:
At the moment, there seems to be an issue when attempting to sign up a new pod. Was not able to reproduce what was shown in PR #378 before it was merged into Development.

Reproduction Steps:
See clip below.

Expected Behavior:
Allows people to sign-up for new account

Actual Behavior:
What actually happened, and how it differed from the expected behavior.

Screenshots (If applicable):
https://github.com/codeforpdx/PASS/assets/14917816/0d0bd183-74a1-40ed-91e9-49482f02d231

@bingeboy

I'm getting a similar error after successfully signing up with the form.
Seems to be an issue with useContactList.js
Steps to create the error:
Browser FF Node v16.2

Start dev pod and dev server on localhost
From homepage http://localhost:5173 click LOGIN button sign into the pod
Once the user landing page loads click the link Your Signup Link
Create a sign in
When the page loads with You have successfully registered for a pod the error should be seen in the console.
XHR requests that are throwing a error 409

Hey Hi!!
I just cloned your repo and tried solving this bug, however I guess another new bug has developed, I am actually now not being able to open the Login Screen after pressing the Login button on the navbar
Could you suggest what should I do?

Hey @Aspireve. With regards to that error, I think it's due to the local environment not set up correctly. Please check your .env file. If you manage to get the environment set up, you should get the following (assuming you've entered into a valid Solid server).
https://github.com/codeforpdx/PASS/assets/14917816/8007afe4-d992-487e-b7cd-768975de92e3

Ohh cool!! I was now able to login with a Solid Id.
Could you tell me how to sign up for a new account on the website so I could find the page where the bug resides?

Ohh I just found it lol.

Heyy @leekahung
I did a bit more research, I don't think it is possible to register two accounts on the same Solid Pod
At the point when I am trying, its giving a 409 (conflict) error, which reveals that there can be only one profile for one pod at a time
And for registering a new account you need to get a new pod via the Solid System (the way we created our first account)

Heyy @leekahung
I did a bit more research, I don't think it is possible to register two accounts on the same Solid Pod
At the point when I am trying, its giving a 409 (conflict) error, which reveals that there can be only one profile for one pod at a time
And for registering a new account you need to get a new pod via the Solid System (the way we created our first account)

I believe there's a bit of a misunderstanding here. What was attempted here was simply registering a new account for someone. It'll be assigned their own webId and their own Pod on Solid, and their webId would be added to your contact list. What was shown here was simply the bug that appears when attempting to do that.

Ohh so I'm guessing this issue is solved then?

Ohh so I'm guessing this issue is solved then?

I believe so since I haven't encountered that error as of late. Think I'll close down this issue as resolved? Might have been fixed in one of the earlier PRs related to the sign up flow.

Closing issue.


undefined method 'version' for nil:NilClass

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 4.7.0
Ruby: jruby 1.7.26 (1.9.3p551)
Distribution: RHEL 6
Module version: commit d29770fc960b106c5834b33d9121c656f0cc44c7

How to reproduce (e.g Puppet code you use)
install the module and set reports correctly
What are you seeing
I'm getting the following error, which seems to stem from https://github.com/voxpupuli/puppet-report_hipchat/blob/master/lib/puppet/reports/hipchat.rb#L37:
Error: Could not send report: Error 500 on SERVER: Server Error: Could not autoload puppet/reports/hipchat: undefined method 'version' for nil:NilClass
What behaviour did you expect instead
No Error when executing the report
Any additional information you'd like to impart
If I execute the file directly using puppetserver's Ruby, I see the gem:
~]# GEM_HOME=/opt/puppetlabs/server/data/puppetserver/jruby-gems /opt/puppetlabs/server/bin/puppetserver ruby /opt/puppetlabs/puppet/cache/lib/puppet/reports/hipchat.rb
Gem::Specification.new do |s|
  s.name = "hipchat"
  s.version = Gem::Version.new("1.5.4")
...

Code was initially implemented here: https://github.com/jamtur01/puppet-hipchat/pull/36

@walkamongus can you please run the following: puppetserver gem list hipchat

Hi @james-powis -- the output above was from the same puppetserver where the issue is occurring and shows the hipchat gem version as 1.5.4.
Do you need the literal output of the puppetserver gem command? Let me know and I can grab it.

@walkamongus I would prefer so, every time I have seen the error you are describing was due to the gem not actually being available to puppetserver. In short if the output spits out a version then we have something new and fun to identify, if it does not then puppetserver gem install hipchat should fix your issue.

@james-powis  -- sure thing...here it is:
~]# /opt/puppetlabs/server/bin/puppetserver gem list hipchat
*** LOCAL GEMS ***

hipchat (1.5.4)

@walkamongus If you check the puppetserver log I am willing to bet you are going to see this on the first report observed after a reload of puppetserver: You need the hipchat gem to use the Hipchat report
I am betting the GEM_HOME and/or PATH are being overriden. Perhaps RVM is in use given you are running CENT 6 and this module... In that scenario you have to use the RVM provided gem to install the hipchat gem.

Hi @james-powis,
Thanks for your help. I actually think I just found the issue and it seems to be specific to Puppet Enterprise. It appears that permissions were not correct on directories of the gem itself (down in /opt/puppetlabs/server/data/puppetserver/jruby-gems/gems) when installed via puppetserver gem. Permissions were set to 0750 and this prevents the puppetserver user (pe-puppet) from being able to access the directories. Perms of 0755 fixed the issue and the error is now gone.

@walkamongus I believe the cause of the issue you encountered is logged here: https://tickets.puppetlabs.com/browse/ENTERPRISE-552


__dirname is not defined (in Vite development server)

Vite Plugin Version
0.7.5
Laravel Version
10.10.0
Node Version
18.6.0
NPM Version
9.5.1
Operating System
Windows (WSL)
OS Version
Windows 10 Pro: 22H2
Web browser and version
Google Chrome Version 113.0.5672.92 (Official Build) (64-bit)
Running in Sail?
No
Description
I created a new Laravel application by using Laravel installer v:4.5.0
The development server shows an error message that __dirname is not defined
However, even the error message is displayed, the development server continues to run and serves the application.
could be related to changes in the way Node.js handles the __dirname variable in ES modules.
Apart from this error message everything works fine.
My current approach might not be the most elegant or optimal solution, I would like to offer my temporary workaround for handling the error.
import { dirname } from "path";
import { fileURLToPath } from "URL";

And I have added the expression dirname(fileURLToPath(import.meta.url) in the place of previous __dirname
It would look like this
fs.readFileSync(path.join(dirname(fileURLToPath(import.meta.url)), "dev-server-index.html")).toString().replace(/{{ APP_URL }}/g, appUrl)
return JSON.parse(fs.readFileSync(path.join(dirname(fileURLToPath(import.meta.url)), "../package.json")).toString())?.version;
Steps To Reproduce
laravel new app
npm install
npm run dev

See https://github.com/laravel/vite-plugin/issues/216

Please upgrade to 0.7.6. Sorry for the troubles, folks.


poetry shell fails to set Python path if prompt uses VT100 escape sequences to read terminal information

Poetry version: 1.4.2
Python version: 3.11.2
OS version and name: Ubuntu 23.04

[x] I am on the latest stable Poetry version, installed using a recommended method.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] I have consulted the FAQ and blog for any relevant entries or release notes.
[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue
Related: https://github.com/python-poetry/poetry-plugin-shell/issues/18 https://github.com/python-poetry/poetry/issues/571
This is a result of me diagnosing why poetry shell starts a new shell, but without the virtual env activated.
Looking at how poetry uses the shell, it uses pexpect to run it, writing the command to activate the python environment as its first input. This breaks in all configurations that read anything before that; particularly, any configuration that uses VT100 escape sequences that read anything. These may be more or less common in, for example, prompts.
For example, I have this in my .bashrc, essentially from this  StackOverflow comment:
new_line_ps1() {
    local _ y x _
    local LIGHT_YELLOW="\001\033[1;93m\002"
    local RESET="\001\e[0m\002"

    IFS='[;' read -p $'\e[6n' -d R -rs _ y x _

    if [[ "$x" != 1 ]]; then
        printf "\n${LIGHT_YELLOW}^^ no newline at end of output ^^\n${RESET}"
    fi
}

if [ "$color_prompt" = yes ]; then
    PS1='$(new_line_ps1)${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='$(new_line_ps1)${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

My analysis of what happens:
What this prompt does is it outputs the "\e[6n" VT100 escape code to read cursor position. VT100 compliant terminals respond to this by producing the a string like "\e[10;1R" as if input from a keyboard. This can then be read by the program to determine that the cursor is on line 10, column 1.
The way poetry shell is implemented, it typically claims to be VT100 compliant if run from such a terminal (because it does not change the TERM environment variable), yet it does not respond to VT100 queries the shell outputs before giving it the activation command. In this case, that results in the read command in the prompt reading (part of) the activation command.

I have the same problem. poetry shell doesn't work with certain prompts (e.g. from oh-my-posh).

A workaround is to add this to your shell config (e.g. .zshrc for zsh):
poetry() {
    if [[ "$1" = "shell" ]]; then
        source "$(dirname $(poetry run which python))/activate"
    else
        command poetry "$@"
    fi
}

This function basically remaps poetry shell to "manually" activate the virtual env.
Based on https://github.com/python-poetry/poetry/issues/571#issuecomment-443595960


README should read like a tutorial

Just finished a first pass on the README tutorial documentation. I think running through importing another city's data will inform some additions (My next step). @jmeisel, I'll throw it to you for any edit suggestions

just pulled from master and it looks like the awesome new readme assumes the integration of changes from #7 that haven't been merged yet.
since we're planning on demoing today.  please let me know if it'd be helpful for me to amend the tutorial instructions to explain what's required currently.  as an alternative, i could also probably put together and link to a quick gist (to help clarify temporarily).

We should have the new build system merged in by 3. Thanks for checking on that @jgravois.


Editor adding additional strings

Editor is behaving very strange (adding additional string values) when trying to edit properties in yaml file. Had a property "type:" and after pressing 7 times "t" after "e" letter it became:
"typetttttttddddddypettttttddddddypetttttddddddypettttddddddypetttddddddypettddddddypetddddddype:"

@rbarilani Can you give your 2 cents please?

@fmueller Working on it.

@wilq87 Can you be so kind to give us some more informations to reproduce the bug:

Browser Version
The schema that you are trying to modify.

Thx in advance.

@rbarilani
Browser:
Version 57.0.2987.98 Built on Ubuntu , running on Ubuntu 16.04 (64-bit)
copy pasted API yaml for wholesale-article

@wilq87 I we deployed a new version can you be so gentle to try again with the same schema?

@rbarilani works like a charm! thanks

@wilq87 👍 Great. Thanks for your contribution.


Use correct spacing for header nav elements

Does a discussion already exist on the topic you are interested in, or on a similar topic?

[X] I verified and it doesn't exist

What
The header navigation items have incorrect internal spacing, resulting in visual discrepancies with the corresponding front-end element.
Why
Keep spacing aligned.
Context
No response
More
No response

Resolved in v3.6.0


Add VkImportMemoryHostPointerInfoEXT replaying support

Fixes issue: https://github.com/LunarG/gfxreconstruct/issues/802
Replay which use VkImportMemoryHostPointerInfoEXT fails with error
 [gfxrecon] FATAL - API call vkAllocateMemory returned error value VK_ERROR_INVALID_EXTERNAL_HANDLE that does not match the result from the capture file: VK_SUCCESS. Replay cannot continue.
Vulkan validation layers output:
Objects: 1
        [0] 0x555cba6d96d0, type: 3, name: NULL
        VUID_Undefined(ERROR / SPEC): msgNum:<PHONE_NUMBER> - Validation Error:
        [ VUID_Undefined ] Object 0: handle = 0x555cba6d96d0, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x79de34d4 |
            VkImportMemoryHostPointerInfoEXT: required parameter pHostPointer specified as NULL.
Objects: 1
        [0] 0x555cba6d96d0, type: 3, name: NULL
        VUID-VkMemoryAllocateInfo-pNext-03332(ERROR / SPEC): msgNum: 980427729 - Validation Error:
        [ VUID-VkMemoryAllocateInfo-pNext-03332 ] Object 0: handle = 0x555cba6d96d0,
        type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x3a7023d1 |
        If the pNext chain includes a VkImportMemoryHostPointerInfoEXT structure, opaqueCaptureAddress must be zero.
        The Vulkan spec states: If the pNext chain includes a VkImportMemoryHostPointerInfoEXT structure,
        VkMemoryOpaqueCaptureAddressAllocateInfo::opaqueCaptureAddress must be zero
        (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/linux/1.3-extensions/vkspec.html#VUID-VkMemoryAllocateInfo-pNext-03332)

1 - Implemented allocation for external memory
2 - Resetted opaqueCaptureAddress to 0 if replay uses VkImportMemoryHostPointerInfoEXT

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

Fixed formatting

@bradgrantham-lunarg @panos-lunarg  Any feedback ?

Hi, @effolkronium !  Thanks for your submission!
PageGuardManager is designed for use in capture for detecting changes to mapped pages for writing to the capture file.  I don't think it's the right thing to use in the replay consumer.  Can you do what you're doing to keep track of those allocations another way?  Like store them in the replay consumer class?  (I haven't had as much time to look into this as I'd like, so I'm sorry I can't provide a more specific suggestion.)
The "generated" files are written by framework/generated/generate_vulkan.py.  The next time that's run (typically on a new SDK version but also when the generated code needs to be altered) your changes will be overwritten.  If you still need to change the generated code after addressing the above, can you instead change the generators to add your change, or alternately pull it out of generation and make a custom handler?
Thanks again!

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

The build script will run the style checks. E.g., from the root: CMAKE_BUILD_PARALLEL_LEVEL="16"  python3 ./scripts/build.py -a x64 -c debug

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

Fixed formatting, please, run CI again
@bradgrantham-lunarg

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

Resolved conflicts with the https://github.com/LunarG/gfxreconstruct/commit/9622292187b1a9dd3aeef38f0492f3d8bcda018c commit.
@panos-lunarg can it be merged to dev branch now ?

@panos-lunarg  @effolkronium  I think it's ready to be merged.

Give me a moment and I'll merge it.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

CI gfxreconstruct build queued with queue ID 12867.

It looks like our internal CI never ran (oversight on our part) so I'm running it now.  If that passes, I'll merge.

CI gfxreconstruct build # 2058 running.

CI gfxreconstruct build # 2058 failed.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

replay_allocate_info->allocationSize is VkDeviceSize, which is always uint64_t.  But on 32-bit Windows, at least, size_t is 32 bits, so this produces a warning and we take warnings as errors.  You can test the 32-bit build on your machine with python3 scripts/build.py -c debug -a x86 --build-dir dbuild (set build-dir as you desire).
Having an allocation that would exceed size_t would be invalid under https://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkImportMemoryHostPointerInfoEXT-handleType-01750, so I just added a check (which should compile out in Release) and added a cast to get rid of the warning (which we take as error).

CI gfxreconstruct build queued with queue ID 12935.

I see. Thanks for the check. Will do the x86 builds in case of another PR's from me : )

I see. Thanks for the check. Will do the x86 builds in case of another PR's from me : )

No problem.  Thanks very much for the PR!

CI gfxreconstruct build # 2061 running.

CI gfxreconstruct build # 2061 passed.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

CI gfxreconstruct build queued with queue ID 13009.

CI gfxreconstruct build # 2063 running.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

CI gfxreconstruct build queued with queue ID 13027.

CI gfxreconstruct build # 2064 running.

CI gfxreconstruct build # 2064 failed.

CI gfxreconstruct build # 2064 failed.

I think we may have had a CI machine failure.  I'm running the case that failed again by hand.

CI gfxreconstruct build queued with queue ID 13346.

CI gfxreconstruct build queued with queue ID 13346.

I'm reasonably sure your PR will pass if we can keep the CI machine running, but it will probably be tomorrow because a few other jobs were also backed up on that machine.  If it passes overnight I'll merge it tomorrow.

Author effolkronium not on autobuild list. Waiting for curator authorization before starting CI build.

💓


Ownership of pointers in mraa_board_t

It seems like there is no clear definition on who owns the different pointers (usually char*) inside mraa_board_t.
Frequently, they are assigned a constant value (i.e. b->platform_name = "MonkeyBoard";) and then freed with free(b->platform_name). Not nice, and might cause segfaults or C-library stack dumps on mraa_deinit().
Same applies for other character pointers, like device_path in mraa_uart_dev_t.
As a side note, since I don't know what is the proper place to discuss overall items with this library:
Has anyone run a static code analyzer on this library? Or a runtime memory integrity tester (like valgrind)? Considering how many bugs can be spotted just by attempting to use the library and by glancing at the code, I think using some memory error detection tools might be a useful (and maybe scary) exercise to bring the code closer to production level.

Yes, this is not nice. mraa_deinit() in general is not great and works realtively badly. It's rare that mraa is unloaded like this so it's never been at the forefront of development, but it should be improved.
Originally the names where all constants, this has changed a little over time with newer library additions and sadly some bugs have been introduced :/
Actually we've run a bunch of static analysis tools and generally they don't complain too much, @alext-mkrs is currently setting up a public instance of sonarcube and fixing a bunch of them.
Generally it is the responsibility of the platform files. Generally I think the easiest thing would be to have a deinit() per platform be called as part of an advance function hook so that a platform always deinit() correctly.

Letting the platforms free what they allocate sounds like a much better way to go to me.
Maybe introduce platform destructor functions in x86.c and arm.c, which in turn can mux the destructor call to the actual platform file. In case the platform has no destructor, either a default deinit can be used (like now) or just exit without deinit.

There's actually no need to mux this, we can just use the advance function and add a mraa_deinit_replace. Although having had a deeper look into what you are saying I don't actually believe we even have an issue (although I'm sure there's an edge case somewhere, as stated above mraa_deinit() is not tested that thoroughly and likely has some edge cases in some of our many build/runtime configurations...)

No platforms allocates plat->platform_name, they all use constants. The exception is the json_platform which does allocate it, but this is treated in mraa_deinit as a special case with mraa.c:263
platform_name is freed (not mraa_board_t.platform_name) but this is always allocated see mraa.c:166 or mraa.c:204 as it's a composite name of mraa_board_t.platform_name and a possible subplatform or something from a json file.
The freeing of device_path only occurs when platform_type is MRAA_JSON_PLATFORM.  But this is correct as they are allocated see jsonplatform.c:525

You seem to be right. Did not expect a global variable with exactly the same name as the board_t member variable (your point 2) and mixed them up - being new to the code base and all.
Maybe the deinit part of the code is ok, I've not seen an actual issue. Just found this when filling out the mraa_board_t struct for my board (and tried to figure out who owns the pointers there).
This topic can be closed from my point of view.

yeah I probably should have called it combined_platform_name or something, probably not the smartest bit of naming i've done :)


Re re re re reeeebase hotfix back into dev

This is a rebase of the current branch that's in production (v2.1.27) + a hotfix merge I made yesterday to the dev branch
Because of a conflict in the signup module the diff looks crazy.
CONFLICT (content): Merge conflict in lib/modules/dosomething/dosomething_signup/dosomething_signup.module
But it's not so crazy.

:eyes: checked and looks good. Gonna pull branch down and manually test some signups next!

Ok, signing up as an authenticated user seems to work fine. Record in database created with appropriate run id.

Aight, also checked campaigns Braümhilda had already signed up for and reported back on, and still shows as signed up and can see her reportback when loading that campaign page.

:+1:

There were a few PHP related errors/warnings that cropped up:
https://dosomething.slack.com/files/diego/F0KLMTVSS/pasted_image_at_2016_01_28_11_26_am.png
https://dosomething.slack.com/files/diego/F0KLN1FBQ/pasted_image_at_2016_01_28_11_28_am.png
https://dosomething.slack.com/files/diego/F0KLNP57S/pasted_image_at_2016_01_28_11_29_am.png


Implement fiber powered workers

Fyi, I'm using this to have multiple Mosquito::Runner's in one process (works with Mosquito v1.0.0rc2):
class Swamp
  Log = ::Log.for("swamp")

  @@fibers = [] of Fiber
  def self.start(n=1)
    raise Exception.new("Swamp already started") unless @@fibers.empty?
    n.times do
      @@fibers << spawn { Mosquito::Runner.start }
    end
    Log.info &.emit("Swamp started (#{n} workers)", { ev: "swamp.started", workers: n })
  end

  def self.stop(timeout = 28.seconds)
    Log.info &.emit("Swamp stopping", { ev: "swamp.stopping", workers: @@fibers.size, timeout: timeout.total_seconds })
    t = Time.monotonic
    Mosquito::Runner.stop
    begin
      while !@@fibers.empty?
        fiber = @@fibers.shift
        while !fiber.dead?
          sleep 0.42
          raise IO::TimeoutError.new if Time.monotonic - t > timeout
        end
      end
    rescue ex : IO::TimeoutError
      Log.error &.emit("Swamp failed to stop", { ev: "swamp.stop_failed", reason: "timeout", workers: @@fibers.size })
    else
      Log.info &.emit("Swamp stopped", { ev: "swamp.stopped", workers: @@fibers.size })
    end
  end
end


[documentation] plugin documentation

Description
As a Greenhouse user, I want to know in business language what I get from the various observability plugins to be able to assess whether it solves my problem.
Objectives

define a template for plugin documentation
polish the readme's
add a quick start guides
add example architectures

Acceptance criteria

[ ] Plutono plugin
[ ] OTEL collector plugin
[ ] kube-monitoring plugin
[ ] ...

duplicate to https://github.com/cloudoperators/greenhouse-extensions/issues/356


Kick-off session for 'Ask users for ethnic groups' pattern

What
Organise a kick-off session for the 'Ask users for ethnic groups' pattern contribution.
Why
To discuss the contribution in detail, including timescales and support.
To do

[x] Set a date and time for the session
[x] Prep for the session
[x] Create and share the agenda
[x] Run the session
[x] Share the acceptance criteria agreed in the kick-off session with the contributor to check
[x] Update GitHub issue for tracking the work and share with contributor
[x] Create a Slack channel for contribution conversations between us and the contributor

Contribution criteria


do not use same cli arg for different purposes

https://github.com/integritee-network/worker/blob/8c17f521c19edc58161a2901dcf753b1e7f101e4/service/src/main.rs#L426-L428

trusted worker url is the url to talk to the worker from anywhere
in the case of an attestter build, it should be named marblerun-url

wrong reading of code, sorry


select_layer.cpp has no code.

The size of the file is 0.

This .cpp file is not used and we have removed it. Thank you!


Angular 17 doesn't build with native-federation

While native-federation version 17 does seem to work with ng serve, the build command never finishes.
On a blank Angular 17 project, after running the schematic:
ng g @angular-architects/native-federation:init --project app-test --port 4201 --type remote
The first time ng build is executed, it shows the following output, and hangs:
Application bundle generation complete. [1.645 seconds]
 INFO  Building federation artefacts
 INFO  Preparing shared npm packages
 NOTE  This only needs to be done once, as results are cached
 NOTE  Skip packages you don't want to share in your federation config

After cancelling the execution and running a second time, it will stay hung with the following output:
Application bundle generation complete. [1.458 seconds]
 INFO  Building federation artefacts

This means the project can't successfully build on a CI/CD pipeline

Thanks for pointing this out.
I did not manage to reproduce this issue
Can you please reproduce this issue with a minimal application?
If not, is there a way to have a look at your source code?

Thanks for pointing this out. This issue is resolved now.
Please update to the latest version and try again.

I can confirm that the new version 17.0.2 solves the issue of npm run build not returning.
Thank you!

I see a new DeprecationWarning from node when npm run build is executed a second time.

This was fixed with current version 17.0.3
Thanks!


[Question] Context Recall different scores for the same context (questions and GT)

I am wondering why the RAGAS metric "context recall" is sometimes different for the same question, the same context and the same ground truth.
I reduced my dataset to 1 question. I see the same context for each test, because the retrieval model is the same, but different answers since I test different LLMs for summarization. The ground truth is also the same for all cases.
The values I get are 0.5 for one test case and 1.0 for another. If I change the question I can get 0 and 1, for example.
I expect "context recall" values be the same for both cases.
The same problem with "context precision".

Hey, can you share the data point for which you observed this? @checkcode555 so that we can debug the issue

I have a somewhat similar issue related to how context recall is computed. For an empty list context, the context recall is always 1. The ground truth is not empty, but given that no context was retrieved from the retriever component, shouldn't the context recall be 0?

Hey @roxanamirel feel free to reinstall ragas from source and to resolve your issue.

@shahules786 I reinstalled from source "Successfully installed ragas-0.1.4.dev5+g169c6e5" and I get the same result, context recall 1, where contexts list is empty. Thanks!

Just an update, that it turns to be that LLM is involved in calculating the context recall score. It means that the usage of different LLMs would lead to different scores. What is confusing is that the scores vary a lot and can be even 0 while using gpt4 for exampe and 0.8 while using gpt3.5 for the same input data. The question is then how to interpret these scores and whether it is trustable. I was wondering whether the calculation can be more transparent and intermediate results can be provided (not only the final score as it is at the moment).


CV does not work with bookdown

The package I used for my CV, "vitae", requires the use of "#" for stylistic design. However, bookdown uses #'s to determine new page starts. Thus, so far, they're incompattible

Fixed it by uploading a picture of the PDF of the CV and refering to the source code via a link


GPU array bugs

1: immediate commands containing MAKE-GPU-ARRAY crash on compile
inside an Emacs file (C-C), but work fine in REPL.
(defparameter garray (make-gpu-array '(0.0 1.0 2.0)
					:element-type :float))

Heap exhausted (no more space for allocation).
917504000 bytes available,<PHONE_NUMBER>6 requested.

It seems there is no way to compile immediate-mode GPU allocations.
2: GPU arrays lose sync with underlying C arrays
(defun test1 ()
  (setf garray (make-gpu-array '(0.0 1.0 2.0)
			       :element-type :float)))
(test1)  ;;yea, this will crash too.  Use REPL

>garray

#<GPU-ARRAY :element-type :FLOAT :dimensions (3) :backed-by :BUFFER>

> (pull-g garray)
(0.0 1.0 2.0)

>(with-gpu-array-as-c-array (qqq garray) (setf (aref-c qqq 0) 999))
999

>(pull-g garray)
(0.0 1.0 2.0)

I though pull-g only goes one level and pulls GPU arrays into C arrays?  Here we wind up with a Lisp list...

Hey @stacksmith, sorry for the slow replies I've been putting all time into work recently. The days need extra hours.
Luckily these two are easy to explain. In reverse order

Gpu-arrays are not designed to stay in sync. they are just meant to be an array on the gpu. c-arrays are the local analog and are meant to have a layout that makes it  easy to transfer data (relatively) efficiently between them.

Is a symptom of how slime/slync etc work. When you compile top level forms in slime it runs them on a different thread than the thread the repl is running on. This then causes an error usually we start cepl from the repl and that means that is the thread the GL context is bound to.
I've looked into using multiple contexts on the threads in question but whilst it would help for some GL objects, not all of them are available on all contexts (VAOs are a good example).

The way I usually handle it on small sessions is to (defvar something nil) and then have a 'reset' method that is called on start and then I can call on demand whilst I'm experiementing. For larger projects I'm likely to have some more interesting lifetime requirements anyway and so I'm less likely to just have misc gpu-arrays in top level vars.
 You can start swank using communication-mode nil which means no multi-threading at all. With everything on the same thread i think what you are trying will work but that has it's own disadvantages as you could imagine.

Thanks.  I am still confused about 2.  So I cannot use 'with-gpu-array-as-c-array' to mutate the GPU array?  I thought that's exactly what it's for...

@stacksmith You are totally right. Sorry for misreading. Here is my test I think is equivilent
(defun test1 ()
  (let ((garray (make-gpu-array '(0.0 1.0 2.0) :element-type :float)))
    (print (pull-g garray))
    (with-gpu-array-as-c-array (qqq garray)
      (setf (aref-c qqq 0) 999))
    (print (pull-g garray))))

I get an error saying
The value
  999
is not of type
  SINGLE-FLOAT

when I change it to 999f0 I get
TESTS> (test1)

(0.0 1.0 2.0)
(999.0 1.0 2.0)
(999.0 1.0 2.0)

I then wondered if my test was too different and compiled these:
(defvar garray nil)

(defun test1 ()
  (setf garray (make-gpu-array '(0.0 1.0 2.0)
                               :element-type :float)))

and then ran this


ko publish ./...

ko publish ./cmd/...
2020/12/19 09:39:01 failed to publish images: found 7 local packages, expected 1

ko resolve is  capable of building and deploying multiple images, and ko publish is seemingly capable of identifying multiple import paths to build, but we run afoul of https://github.com/google/ko/blob/722ad3c37b2e01219aa053ba11b6b0d6d065b5d7/pkg/commands/publisher.go#L39 in ko publish.

FWIW ko publish ./cmd/foo ./cmd/bar ./cmd/baz works, it's just ./... that doesn't. Maybe this was an explicit decision, but I don't remember the motivation.
I guess ko publish ./... has slightly different semantics ("publish all supported refs in ./...") compared to ko publish ./a ./b ("publish ./a and ./b, if they are supported").

I don't think it was an explicit decision. Though... this reminds me of how we started requiring ko:// in references because it made things a lot easier to reason about and error report, but I think it's probably fine to support this kind of thing, if the diff is reasonable. We should be able to find and build any main packages pretty cheaply... we might have to change some things from returning a foo to a []foo, but I think that's fine.


inconsistent parameters of NWBIO.write_block

write_block methods are expected to take self, block, **kwargs as parameters, as. defined in https://github.com/NeuralEnsemble/python-neo/blob/ffde1764b206a8e7122e88ff974cfc40325d3333/neo/io/baseio.py#L192
@legouee Is there a particular reason why you require an additional nwbfile argument here instead of using the self.filename to identify the file to write to?

Hi @JuliaSprenger. Following the write_block method, I restructured the code. I added all the NWB annotations and the definition of a pynwb file in the init function. This therefore allows me to have the write_block method consistent with the whole python-neo code.
See PR #1166


[10.1] ISPN-11352 JGroups Subssytem: persist properties in the relay element

https://issues.redhat.com/browse/ISPN-11352

integrated! thanks @tristantarrant !


Add lowering strategy pass

@nirvedhmeshram @yzhang93 @MaheshRavishankar
This PR adds AMDAIEAddLoweringStrategyPass that adds tiling configurations based on a tiling-strategy option. Please let me know whether this is a good approach for enabling different tiling strategies, for example for ukernel vs direct-codegeneration?
@nirvedhmeshram If you want I can use this PR to update the code here to rely on AMDAIEAddLoweringStrategyPass instead, like I think you meant in this TODO: https://github.com/nod-ai/iree-amd-aie/blob/aa32917f1db27ae97ebfaa9b176b534fcb4720f4/compiler/plugins/target/AMD-AIE/iree-amd-aie/Transforms/AMDAIELowerExecutableTarget.cpp#L107 Let me know.

@nirvedhmeshram @yzhang93 @MaheshRavishankar
This PR adds AMDAIEAddLoweringStrategyPass that adds tiling configurations based on a tiling-strategy option. Please let me know whether this is a good approach for enabling different tiling strategies, for example for ukernel vs direct-codegeneration?
@nirvedhmeshram If you want I can use this PR to update the code here to rely on AMDAIEAddLoweringStrategyPass instead, like I think you meant in this TODO:
https://github.com/nod-ai/iree-amd-aie/blob/aa32917f1db27ae97ebfaa9b176b534fcb4720f4/compiler/plugins/target/AMD-AIE/iree-amd-aie/Transforms/AMDAIELowerExecutableTarget.cpp#L107
Let me know.

Yes updating the code there would be great. Thanks!

This looks good to me. I am landing this change. cc @yzhang93 and @Abhishek-Varma

Landed using #115


How to project ParBilinearForm onto ParGridFunction?

Hello everyone,
I am wondering how I can project ParBilinearForm onto ParGridFunction to get ParLinearForm.
Additionally, what is the R required to convert ParGridFunction into HypreParVector what what would be the command to do that?

Thank you,
Sai

Can you clarify what are you trying to achieve?
The diagram above just states that bilinear forms map grid functions (primal vectors) to linear forms (dual vectors).
Given a ParGridFunction there several HypreParVector objects you can derive from it, depending on if you want to assemble it (ParGridFunction::ParallelAssemble), average it (ParGridFunction::ParallelAverage) or just keep the true dof values (ParGridFunction::ParallelProject).
Hope this helps,
Tzanio


Apply TimetableTopArea dark theme design

Idea Description
There is a new image for the dark theme. Please apply it!
Reference images and links
To be

https://www.figma.com/file/MbElhCEnjqnuodmvwabh9K/DroidKaigi-2023-App-UI?type=design&node-id=56145-56684&mode=dev

May I work on this task?

Thanks! Assigned 👍


Please update dependencies

Hi there,
Can you please update all dependencies to latest version?
  http: '>=0.12.0 <0.13.0'. => http: '^0.13.4'
  intl: '^0.16.1' => intl: '^0.17.0'
  meta: '^1.1.8' => meta: '^1.7.0'

I'm having few conflict issues when import mailslurp like this
Because every version of mailslurp depends on http ^0.12.0 and every version of my_app from git depends on http ^0.13.3, mailslurp is incompatible with my_app from git.

same problem here.

any updates?