[x/gamm][StableSwap - Post V8] Add stableswap scaling factor governor

There is a desire to use stableswaps with yield accumulating assets. There are a few designs for how you could do this, but the simplest one seems to be to utilize the 'scaling factors' present in the Stableswap algorithm. If someone wanted to adjust the scaling factors according to yield, then this would achieve altering the price that its being stable around.
We should add a new field in the stableswap proto message, called scaling_factor_governor, which can be either blank, or an osmo address.
We should also add a new message called "MsgStableSwapAdjustScalingFactors", that can only be sent from the scaling_factor_governor address for the respective poolID. (if the address is blank, noone can send this message for the given poolID). This message adjusts the scaling factors to the provided ones.
It is intentioned that cosmwasm contracts could be used to set these in the future. There should also be a query for this, as it will be important for front-ends / users to know about a governor risk prior to LP'ing.
This is a post v8 feature

Could i try doing that ?


not authorized camera access  crashes

if the user does not authorize the camera access and then reopens it, the app crashes

Fixed. Thanks!

thank you!

thank you man!


[QUERY]Blob StorageでCreateIfNotExistsを使用するとHTTPStatus409が発生する

Question
ファイル有無が分からない Blob Storage に対して、storage client library Ver7.1.2で
「CreateIfNotExists();」を行うと正常に完了するが、storage client library Ver9.3.3では
Application Insightsの失敗にHTTPStatus409が記録される。
実行するコードは同じなのですが、仕様が変わったのでしょうか。回避策があれば教えてください。
Environment:
storage client library Ver9.3.3
AppService
StorageV2 (general purpose v2)
.NetFramework 4.7.2
IDE and version : Visual Studio 16.8.5
Sample Code.
// Blobクライアントの取得
_client = _clients.GetOrAdd(connectionString, (cs) =>
{
var account = StorageManager.CreateStorageAccount(cs);
var client = account.CreateCloudBlobClient();
client.DefaultRequestOptions.RetryPolicy = retryPolicy;
return client;
});
// コンテナの取得
_container = _client.GetContainerReference(containerName);
// パブリックアクセスを設定
if (publicAccess.HasValue == true)
{
var p = _container.GetPermissions();
p.PublicAccess = publicAccess.Value;
_container.SetPermissions(p);
}
_container.CreateIfNotExists();

Hi @fj6731bn.  Thank you for your feedback and we regret that you're experiencing difficulties.  Unfortunately, this repository is English-based and we're not able to understand your scenario well enough to help.   Would you be able to translate into English so that we can assist?   If you're unable to translate, your best path forward would be to open an Azure support request, where they'll have folks with the language skills needed to help.

Hi,
I apologize in advance if I got the Japanese Translation wrong.
Looks like you're using version 9.3.3 of the Blobs package. That package is currently deprecated, I suggest you update to version 12.
However for a short explanation, that's the expectation if you did a CreateIfNotExists on a Blob that already exists. The SDK recevies the 409 BlobAlreadyExists error that you see in Application Insights, and omits it from your view since that's the functionality of CreateIfNotExists. This is expected behavior of the API.

thank you.
This case complies with the specifications.
I understand that it cannot be suppressed.


Use windows native look and feel

Maybe add an option later to change themes

I will add here what not to forget
https://gist.github.com/skyrpex/5547015


failure installation on Mac OS 11.0.1 (Big Sur)

I have a mac OS 11.0.1 Big Sur, python 3.9.
I am trying to install aplpy package, firstly I need to install pyregion requirement package. But the error is typical
pyregion/_region_filter.c:12082:52: error: no member named 'tp_print' in 'struct _typeobject'
__pyx_type_8pyregion_14_region_filter_AngleRange.tp_print = 0;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
14 errors generated.
error: command '/usr/bin/gcc' failed with exit code 1
----------------------------------------
ERROR: Command errored out with exit status 1
Is this because of new Mac OS version?
Thanks for your help.

This because of python 3.9. I also had this problem with the released version of pyregion from pypi (2.0), but I think the problem is already fixed in the master branch, so you might want to try to install from github instead.

I believe this should be fixed with the v2.1.1 release. Please reopen if you still see the problem.


fix typo in storm-client pom file: kyro -> kryo

@revans2 : typo I found while poking around and trying to understand the shaded kryo jar, as per our discussion in STORM-2191.

+1


macOS ImageIO corrupts .ico, .cur when using IMG_Load()

Steps to reproduce:

Build on macOS with the ImageIO backend
Load test/sample.ico, test/sample.cur on macOS using IMG_Load()

Expected result: they load successfully and draw as a copy of the reference
Actual result: https://github.com/libsdl-org/SDL_image/issues/248#issuecomment-1133183528, https://github.com/libsdl-org/SDL_image/issues/248#issuecomment-1133188304
Workaround: Use IMG_Load_RW() or IMG_LoadTyped_RW() instead.

As with #256, I'm only opening this so I have something to refer to in a commit: I don't think it's a release blocker.
I suspect that what is happening here is that the version of IMG_Load() in IMG_ImageIO.m thinks it can load these files, but its interpretation of them is not the same as ours.


Use proper scope names in ScenarioHook

The scopes names were using feature.before and feature.after in ScenarioHook, while it should be scenario.before and scenario.after.
Can't see which tests I should update, I'll take a look (it should be within hooks.feature I guess ?)

It's kinda worrying that this change hasn't caused any difference in the test suite

pretty much agree...

Can you add a test that will fail if your change is reverted?

I am using scenario scope hooks without this fix and it seems to be working. I'll try to add a test that fails without this fix, but I'm not quite sure how. I'll need some time to check it up.

@Taluu can you add a test so I can merge it?

Will do. Any hint on how shuold I test that (and make sure a failure is triggered without this fix, otherwise it could be quite pointless) ? Because there seems to be a bunch of scenarios with before / after scenario hooks and it didn't fail before...

TLDR;
There are already tests that cover this case. The reason why those weren't failing is because of defensive/type-guiard programming on my side.
Longer version
Those constants are used during creation of hooks and scopes. They are then used by the HookRepository to fetch callbacks appropriate for a just fired hook. Now technically, there is a bug and in case of ScenarioHook this guard will be ignored for firing both Feature and Scenario hooks. So why doesn't it fail? Keep reading.
If hook and scope name check out (even wrongly), we pass forward to filtering guard. Filtering guard checks if the kind of hook (all hooks in case of Behat) is the filterable hook and then asks hook to filter itself based on given Scope. If you drill down to RuntimeScenarioHook, you'll see that the first thing this guy does is type-checks the scope you pass.
Basically it means that hooks have two guards in play - name-based and type-based ones. This is redundancy and an obvious design flaw. I shouldn't have checked type inside RuntimeScenarioHook and should've followed tell-don't-ask querying pattern. This way already existing tests would've highlighted the name-guard bug.
This PR and implications
With two guards in place and commitment to BC, there's not much we can do. I'll still merge this PR as it should potentially provide very minor performance optimisation by avoiding unnecessary type checks.

Thanks for the explanation !

@Taluu thanks for spotting!


Header hero img

Unfortunately, I did a bit more on this branch than I wanted, the start for the mobile site is now given, ready to merge.

All done and ready to merge


Crash upon Nether Generation

Describe the Bug
Another Generation crash bug, here's the crash log. https://pastebin.com/ctB4w1vG
Reproduction Steps
Just entered the Nether at a Portal I made in a new world.
Expected Result
Enter the Nether
Operating System
Windows 10
Mod Version
2.5.1
Minecraft Version
1.19
Forge Version
41.0.63
Other Mods
Appleskin, Bookshelf, Clumps, Comforts (forge edition), Cosmetic Armor Reworked, Enchantment Descriptions, Fast Leaf Decay, Goblin Traders, Gravestone Mod, Iron Chests, Mining Master, Moonlight Lib, More Villagers, Mouse Tweaks, Sophisticated Backpacks, Sophisticated Core, Supplementaries
Additional Context
Found a cool generated portal frame, started building a base, entered the nether for some resource havesting and this happened.

I can even provide the seed and the portal frame location which I used which caused the crash if need be.

Sorry this issue came back up! I wasn't able to replicate it before, but found what seemed to be causing the issue anyway. I'm looking into it again to see if I can find another instance of the error that I missed previously. I'll keep you updated!

Could you do me a huge favor and replicate the issue with this mod installed? That should give more information if the crash still occurs. If it doesn't occur, it's possible that the crash is caused by this which I believe Cyanide should fix as of version 2.1.1. Thanks in advance!

Install Cyanide fixed the problem for me

Well I did and found out something interesting. https://pastebin.com/7YrX4SPF
I think this will best explain it.

Interesting! Well, I’ll have to figure that out, but it might actually be a Mining Master issue. I’ll have to figure it out, so I’ll leave this issue open here for now until I determine which mod is actually causing the issue. Thanks for reporting this!

I've done some personal bug testing and I've found that both terrablender and moonlight cause crashes with nether generation

Do you mean in conjunction with Infernal Expansion or on their own? There is an existing Vanilla bug that could cause these exact crashes. I haven't yet had a chance to look at Mining Master to see what could be causing this, but the crash does seem to be a strange issue that shouldn't be occurring (especially since the Cyanide log seems to say that the feature should be before itself if I'm reading it correctly). It would be interesting to know if TerraBlender is having similar issues as well.

The issue has been identified and there will hopefully be a fix soon. There's a possibility Forge themselves may rework something that would fix this issue, but, if they decide not to, we will fix this on our end. Thank you for your patience!

I'm not 100% sure, but I'd assume there is a way, yes. I've never attempted it, but I think there should be some way to do it

I might have run into this as well, the pastebins are expired so I can't tell. I had a feature cycle crash on attempting to enter the nether the first time.
Cycle:
At step 6
Feature '[Unknown minecraft:worldgen/placed_feature]'
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:crystalline_chasm' at index 18, 19 and 5 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'minecraft:nether_wastes' at index 3, 4 and 3 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 2, 3 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 3, 4 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 4, 5 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 5, 6 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 6, 7 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 7, 8 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 8, 9 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 9, 10 and 8 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 10, 11 and 8 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 11, 12 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 12, 13 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 13, 14 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 14, 15 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 15, 16 and 10 others)
  must be before '[Unknown minecraft:worldgen/placed_feature]' (defined in 'biomesoplenty:undergrowth' at index 16, 17 and 1 others)

Fixed by #2395c299a77c86ddcd7c33ea7f4bb437a7038115. Sorry didn't realize this was still open!


🚧 wip: worker.scheduled() for unstable_dev

Initial implementation of worker.scheduled() for unstable_dev. (https://github.com/cloudflare/wrangler2/issues/1804)
const worker = await unstable_dev("index.js");

const resp1 = await worker.fetch("/path");

// We now export a way of testing scheduled events
const resp2 = await worker.scheduled();
// or with a custom cron
const resp3 = await worker.scheduled("* * * * *");

There are a few things to think about here:

This relies on the middleware for testing scheduled events (https://github.com/cloudflare/wrangler2/pull/1815) - and hence actually requires us to start unstable_dev with testScheduled: true
We have a couple of options here as it isn't ideal to make people pass through testScheduled:

Option 1: Only enable worker.scheduled() if testScheduled is set to true.
Option 2: Enable testScheduled by default. This will always wrap the worker with middleware unless disabled. This would override the route /__scheduled which is very unlikely to have been used by people as default behaviour, but we would still expose the option for people to disable it, (and when disabled we would not allow worker.scheduled() to work.
Option 3: We bundle the worker twice, once with the scheduled middleware disabled, and once with it enabled and then start two dev servers and direct traffic to each of the two depending on if people call worker.fetch() or `worker.scheduled().
Option 4: Similar to option 3, just we only start up the second server on the first worker.scheduled() request. We could additionally only start up the non-scheduled event middleware (regular) server on the first worker.fetch(). Meaning if only one of .scheduled() or .fetch() is called we only start up one server and shouldn't(?) lead to any increased loading times overall. This would only be true in testing environments and outside of that would behave as it does now.

For Option 4:
// Initial `unstable_dev` call doesn't start up any servers
const worker = await unstable_dev("index.js");

// First call to `worker.fetch()` bundles and starts up a server
const resp1 = await worker.fetch("/path");

// Subsequent calls to `worker.fetch()` use the existing server
const resp2 = await worker.fetch("/path");

// First call to `worker.scheduled()` starts up a second server with the scheduled testing middleware bundled
const resp3 = await worker.scheduled();

// Subsequent calls to `worker.scheduled()` use the existing server with middleware bundled
const resp4 = await worker.scheduled("* * * * *");

// shuts down all servers
await worker.stop();

It is very hard to capture any response out of the scheduled events as scheduled events can't return a response. It is probably worth having a dig into how people are using scheduled events to figure out how might be best to capture something testable out of them.

I didn't realise scheduled events don't return anything - is there a value in calling them from a test runner then? What should we assert/expect on?

I think it would be nice to have some way of capturing logging from the started dev process, that would give something to assert / expect on.
Currently we can assert/expect on errors

Here is an example test that you could do:
it("should be false then true", async () => {
  const scriptContent = `
  let test = false;

  export default {
    fetch(request, env, ctx) {
      return new Response(test);
    },
    scheduled(event, env, ctx) {
      test = true;
    },
  };
`;
  fs.writeFileSync("index.js", scriptContent);

  worker = await unstable_dev(
    "index.js",
    { testScheduled: true },
    { disableExperimentalWarning: true }
  );
  const resp1 = await worker.fetch("/test");
  const resp2 = await worker.scheduled();
  const resp3 = await worker.fetch("/test");

  if (resp1) expect(await resp1.json()).toBe(false);
  if (resp2) expect(await resp2.text()).toBe("Ran scheduled event");
  if (resp3) expect(await resp3.json()).toBe(true);

  await worker.stop();
});

If people are updating KV or something like that we could check for that pre and post operation.

I started using Cloudflare workers as infrastructure for a personal project, and I wanted to know exactly how to test a locally scheduled cron job (with the scheduled module syntax). I'm again on the bleeding edge (matter of attraction, lol).
How is the community testing this exactly? I couldn't find many examples or references in the documentation to understand what unstable_dev's experimental.testScheduled option does. I know this is just a draft, but could you point me in the right direction?

Hey @fmquaglia, check out the docs for --test-scheduled under https://developers.cloudflare.com/workers/wrangler/commands/#dev

Closing this for now. The current approach is to provide { experimental: { testScheduled: true } } in the unstable_dev() options, and then to hit the /__scheduled URL.
Also going forward the native vitest unit test running support that is being worked on will provide a way to run the scheduled() handler directly in tests if needed.


Testing CI/CD

:tada: This PR is included in version 1.0.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Lifecycle websocket / CollabSession

Currently CollabSession takes a fresh a websocket object and binds to the onopen event to immediately send an ['open'] message. That's too opinionated behavior.
In our multi-document notepad app we want the websocket connection to be owned by the app and be created only once. So I think we should leave the websocket initialization to the app and require a connected/authenticated websocket connection. Then each time a user 'opens' or 'creates' a document we initialize a new CollabSession. We also need to make sure to dispose (or disconnect) the previous collab session and the new collabsession takes over the message handling. We should use ws.addEventListener('message', handler) instead of onmessage = handler so the app can bind a custom message handler too.
this.session = new CollabSession(doc, ws, {
  docId: 'note-1',
  docVersion: 0
});

// sends the open message to the server
this.session.start();
this.session.on('document:opened', this._renderEditor, this);

// to switch to a different session
this.session.stop(); // like dispose deregisters the handlers
this.session = new new CollabSession(otherdoc, ws, {
  docId: 'note-27',
  docVersion: 0
});
this.session.start();

Does that sound reasonable?

Yes, we defenetely should manage sockets on app side and pop them out in
case of disconnection.
On Sat, Feb 13, 2016, 19:46 Michael Aufreiter<EMAIL_ADDRESS>wrote:

Currently CollabSession takes a fresh a websocket object and binds to the
onopen event to immediately send an ['open'] message. That's too
opinionated behavior.
In our multi-document notepad app we want the websocket connection to be
owned by the app and be created only once. So I think we should leave the
websocket initialization to the app and require a connected/authenticated
websocket connection. Then each time a user 'opens' or 'creates' a document
we initialize a new CollabSession. We also need to make sure to dispose (or
disconnect) the previous collab session and the new collabsession takes
over the message handling. We should use ws.addEventListener('message',
handler) instead of onmessage = handler so the app can bind a custom
message handler too.
this.session = new CollabSession(doc, ws, {
docId: 'note-1',
docVersion: 0
});
// sends the open message to the serverthis.session.start();this.session.on('document:opened', this._renderEditor, this);
// to switch to a different sessionthis.session.stop(); // like dispose deregisters the handlersthis.session = new new CollabSession(otherdoc, ws, {
docId: 'note-27',
docVersion: 0
});this.session.start();
Does that sound reasonable?
—
Reply to this email directly or view it on GitHub
https://github.com/substance/substance/issues/455.

We could also not pass the ws immediatly, but explicitly with a connect call. That way we could start with a non-collab offline session but then later connect it to the hub.
this.session.connect(ws);

@oliver---- not quite there but if you look at that code... does that seem to go into the right direction?
https://github.com/substance/notepad/blob/7899624dca51286bfca787a996615cbf29466680/notepad/app.js

Looking good.
However I would need try it out to say more.

thx. i will try to get it working in a branch.
On Sun, Feb 14, 2016 at 4:03 PM Oliver Buchtala<EMAIL_ADDRESS>wrote:

Looking good.
However I would need try it out to say more.
—
Reply to this email directly or view it on GitHub
https://github.com/substance/substance/issues/455#issuecomment-183903426
.

That's working now. We should just get this into master by adapting examples and testsuite.


UP-4828 wrapping entity consume in finally

https://issues.jasig.org/browse/UP-4828
Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines
[ ] tests are included
[ ] documentation is changed or added

Description of change

wrapping EntityUtils.consumeQuietly in finally block of SoffitConnectorController

Thanks @davidmsibley! -- very glad to have this contribution.

Travis CI test failure is coming from the flaky random string test.
The AppVeyor test failure the same one appearing on master right now.

Coverage increased (+0.002%) to 22.866% when pulling 6709c2e7daf44aac3c841acfa67f86d12bc97326 on davidmsibley:UP-4828 into 63cf26066eb0ce9411631ec614d8ffd41e559f92 on Jasig:master.


Inherit cargo deps with workspace=true

Ref https://mainmatter.com/blog/2024/03/18/cargo-autoinherit/


tsl throwing error

how to solve this ? must be tsl configuration.
ERROR in D:\Workspace\saleor-storefront-0.4.0\src\views\Search\index.tsx
./src/views/Search/index.tsx
[tsl] ERROR in D:\Workspace\saleor-storefront-0.4.0\src\views\Search\index.tsx(58,5)
      TS2322: Type 'string | string[]' is not assignable to type 'number'.
  Type 'string' is not assignable to type 'number'.

there are list of errors like this and it start occurring after i install  @babel/preset-env and @babel/preset-react
still showing error even uninstall these.
delete node_modules and lock file too
problem is same

It was my mistake i did something wrong, instead of fixing i create app again.


Checkbox component support Icons

Feature request
In view of the storage stuffs I'm wondering if we could have it such that passing an Icon as a prop to a Checkbox component will show the Icon in place of the checkbox, until the user hovers over the checkbox
If the checkbox is selected, icon should remain hidden

I'm not sure about this.
I think it might be better to keep them separate, and just hide/show a checkbox on top of the Icon 'in app' rather than bloating the Checkbox component. Might also force


[Error] Downloading stash for Standard

Hi there,
Procurement 1.9.2 Initialized.

Authenticating ****                                                         [OK]
Loading characters...                                                                     [OK]
Loading Standard Stash Tab 1...                                                           [OK]
Loading Standard Stash Tab 3...                                                           [OK]
Loading Standard Stash Tab 4...                                                           [OK]
Loading Standard Stash Tab 5...                                                           [OK]
Loading Standard Stash Tab 6...                                                           [OK]
Loading Standard Stash Tab 7...                                                           [OK]
Loading Standard Stash Tab 8...                                                           [OK]
Loading Standard Stash Tab 9...                                                           [OK]
Loading Standard Stash Tab 10...                                                          [OK]
Loading Standard Stash Tab 11...                                                          [OK]
Loading Standard Stash Tab 12...                                                          [OK]
Loading Standard Stash Tab 13...                                                          [OK]
Loading Standard Stash Tab 14...                                                          [OK]
Loading Standard Stash Tab 15...                                                          [OK]
Loading Standard Stash Tab 16...                                                          [OK]
Loading Standard Stash Tab 17...                                                          [OK]
Loading Standard Stash Tab 18...                                                          [OK]
Loading Standard Stash Tab 19...
[Error] Downloading stash for Standard, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues

Hi, you need to send me the details logged to the DebugInfo.log file, however a new version of Procurement has just been released.
Please test with the new version and let me know if this is still a problem.


feat: reject outdated dlc offers

resolves https://github.com/get10101/10101/issues/1670

@luckysori / @holzeis : Any idea why this test would reproducibly fail funding the app?
Even locally it fails even though other tests work...

I don't think this is related to your changes. I've seen this test failing randomly on the ci.
However, could this log in the coordinator be related to this test failing?
Error in transaction funding: Misuse error: Funding transaction absolute timelock is non-final
2023-12-08 20:18:56 DEBUG ln_dlc_node::ln::event_handler: Received event event=ChannelClosed { channel_id: ChannelId([202, 125, 47, 22, 194, 166, 160, 15, 130, 129, 191, 65, 58, 190, 222, 235, 120, 110, 207, 212, 73, 223, 159, 140, 89, 197, 94, 195, 137, 165, 70, 160]), user_channel_id:<PHONE_NUMBER>39165280308927710438938030910, reason: ProcessingError { err: "Error in transaction funding: Misuse error: Funding transaction absolute timelock is non-final" }, counterparty_node_id: Some(PublicKey(f9cbfe38e9475b90e1c4a126e05fbe5ba7bbfc69f7b062f2a7d0749a730c8de437a0f3336b7618d086149fd5d29f9dce91c5481d41592ae5960a4e2d6651aa79)), channel_capacity_sats: Some(1550000) }

@luckysori / @holzeis : Any idea why this test would reproducibly fail funding the app? Even locally it fails even though other tests work...

I think we need to enable TRACE logs in LND, because it's hard to know why it failed. All I see in the LND logs is this:
2023-12-08T20:18:58.7610907Z 2023-12-08 20:18:56.642 [DBG] CRTR: Payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d in state terminate=false, active_shards=0, rem_value=50000000 mSAT, fee_limit=2500000 mSAT
2023-12-08T20:18:58.7611643Z 2023-12-08 20:18:56.643 [DBG] CRTR: PaymentSession(d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d): pathfinding for amt=50000000 mSAT
2023-12-08T20:18:58.7612116Z 2023-12-08 20:18:56.643 [DBG] CRTR: Pathfinding absolute attempt cost: 150 sats
2023-12-08T20:18:58.7612601Z 2023-12-08 20:18:56.644 [DBG] CRTR: Found route: probability=0.7362499999999998, hops=2, fee=2500 mSAT
2023-12-08T20:18:58.7613010Z 2023-12-08 20:18:56.644 [DBG] CRTR: Pathfinding perf metrics: nodes=2, edges=2, time=1.20418ms
2023-12-08T20:18:58.7614141Z 2023-12-08 20:18:56.655 [DBG] CRTR: Payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d (pid=2) successfully sent to switch, route:<PHONE_NUMBER>81985 (50002500 mSAT) -><PHONE_NUMBER>976 (50000000 mSAT), cltv 233
2023-12-08T20:18:58.7615103Z 2023-12-08 20:18:56.655 [DBG] HSWC: ChannelLink(0b3bf1acc50d1d82df5dfd902f58c389cc458435cfd7bf24b29141ffe56e04e6:1): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=2)->(Chan ID=123:1:1, HTLC ID=1)
2023-12-08T20:18:58.7616993Z 2023-12-08 20:18:56.656 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Sending UpdateAddHTLC(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, id=1, amt=50002500 mSAT, expiry=233, hash=d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d) to 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7617328Z 2023-12-08 20:18:56.656 [DBG] HSWC: Subscribing to result for paymentID=2
2023-12-08T20:18:58.7618312Z 2023-12-08 20:18:56.656 [DBG] CRTR: Payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d in state terminate=false, active_shards=1, rem_value=0 mSAT, fee_limit=2497500 mSAT
2023-12-08T20:18:58.7619113Z 2023-12-08 20:18:56.708 [DBG] HSWC: ChannelLink(0b3bf1acc50d1d82df5dfd902f58c389cc458435cfd7bf24b29141ffe56e04e6:1): removing Add packet (Chan ID=0:0:0, HTLC ID=2) from mailbox
2023-12-08T20:18:58.7620526Z 2023-12-08 20:18:56.709 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Sending CommitSig(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, num_htlcs=1) to 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7622896Z 2023-12-08 20:18:56.724 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Received RevokeAndAck(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, rev=fed137dca1f5e4fab4c7063d505cd3190e9d8967ff53d7f10b6e72795e17bb2a, next_point=033c9a99728e704d880f142faf8058d9777ac50aa0e64df6c1235fdd62b196e9f2) from 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7624534Z 2023-12-08 20:18:56.724 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Received CommitSig(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, num_htlcs=1) from 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7626591Z 2023-12-08 20:18:56.740 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Sending RevokeAndAck(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, rev=7809262f1663e3829d246ab568b3cd8e5e9db332c423ab547ab09de90628feaa, next_point=03995dc1b6e83402cbbde1bf6e7b5f210ff47bd3211c8527cd305730b80189d1b3) to 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7632522Z 2023-12-08 20:18:57.004 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Received UpdateFailHTLC(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, id=1, reason=15bae06d0a1b079db54d6e0795bef70a84733437cc0c6209b21fdd119a7922c68766fe25fa240d9b940ddf4607405624913c45339fd7f2c82091f42c1755d8a98d62adfb5231ed5a4e6ddf03e72e9ebbad499af82e8d281d2fe4ecadbe0ca0515d075fcc1f93705285d579039ff8680e1174d5f9c3a684ee3503acbbca8793b3d87f9d1bbb41020c90ba38996a775d894e4fbba7187d9b512a7e0ae6fdcf1b56c91794579fe391e355d93b15c6b2556059c09ea448f0a66a331d94ca95387d065f42354eb3d92c8574ebb9389d9eeb7bbd5bfb15579950ba55dce368e80d27ef1313a4348945ba5ce8fb22ebb60d3bd60a24258085c6bd4266a7ea0f1cb7751cbb28e6222df8cc4ca67fbf8e449d26feccc213a60a19b55b8c47a378beeb80f4dfbb12af) from 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7634164Z 2023-12-08 20:18:57.046 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Received CommitSig(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, num_htlcs=0) from 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7636202Z 2023-12-08 20:18:57.047 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Sending RevokeAndAck(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, rev=29aabf20f76ebe4244f12f608ee1f251a631c1980317106166340ce16aa63f88, next_point=02138304fc1f3f8de8906289cf0588e8ba23a42716f86505f978e50cd6ba0a8b9d) to 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7637659Z 2023-12-08 20:18:57.049 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Sending CommitSig(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, num_htlcs=0) to 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7639989Z 2023-12-08 20:18:57.067 [DBG] PEER: Peer(02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9): Received RevokeAndAck(chan_id=e6046ee5ff4191b224bfd7cf358445cc89c3582f90fd5ddf821d0dc5acf13b0a, rev=04e1a81defb5b6eeac12a20b9f5f1a213ec4c575a719fd3232e2006ef536ce20, next_point=023930a4e621640c06efb487cffd93f78608863e8c31d2e43c49014209caed05f4) from 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9@<IP_ADDRESS>:9045
2023-12-08T20:18:58.7640764Z 2023-12-08 20:18:57.068 [DBG] HSWC: ChannelLink(0b3bf1acc50d1d82df5dfd902f58c389cc458435cfd7bf24b29141ffe56e04e6:1): settle-fail-filter &{1 [0]}
2023-12-08T20:18:58.7641484Z 2023-12-08 20:18:57.068 [DBG] HSWC: ChannelLink(0b3bf1acc50d1d82df5dfd902f58c389cc458435cfd7bf24b29141ffe56e04e6:1): Failed to send 50002500 mSAT
2023-12-08T20:18:58.7642249Z 2023-12-08 20:18:57.068 [DBG] HSWC: Closed completed FAIL circuit for d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d: (0:0:0, 2) <-> (123:1:1, 1)
2023-12-08T20:18:58.7642596Z 2023-12-08 20:18:57.068 [DBG] HSWC: Storing result for paymentID=2
2023-12-08T20:18:58.7643042Z 2023-12-08 20:18:57.069 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=2
2023-12-08T20:18:58.7643824Z 2023-12-08 20:18:57.069 [DBG] HSWC: Tearing down open circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=2) with keystone=(Chan ID=123:1:1, HTLC ID=1)
2023-12-08T20:18:58.7644608Z 2023-12-08 20:18:57.069 [DBG] HSWC: Closed completed FAIL circuit for d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d: (0:0:0, 2) <-> (123:1:1, 1)
2023-12-08T20:18:58.7645306Z 2023-12-08 20:18:57.069 [WRN] CRTR: Attempt 2 for payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d failed: UnknownNextPeer@1
2023-12-08T20:18:58.7646598Z 2023-12-08 20:18:57.080 [DBG] CRTR: Reporting pair failure to Mission Control: pair=02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9 -> 03e48d0c739a74d0a7f262b0f769fcbba75bbe5fe026a1c4e1905b47e938fecbf9, amt=0 mSAT
2023-12-08T20:18:58.7647550Z 2023-12-08 20:18:57.080 [DBG] CRTR: Setting 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9->03e48d0c739a74d0a7f262b0f769fcbba75bbe5fe026a1c4e1905b47e938fecbf9 range to [0 mSAT-0 mSAT]
2023-12-08T20:18:58.7648742Z 2023-12-08 20:18:57.080 [DBG] CRTR: Reporting pair failure to Mission Control: pair=03e48d0c739a74d0a7f262b0f769fcbba75bbe5fe026a1c4e1905b47e938fecbf9 -> 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9, amt=0 mSAT
2023-12-08T20:18:58.7649692Z 2023-12-08 20:18:57.080 [DBG] CRTR: Setting 03e48d0c739a74d0a7f262b0f769fcbba75bbe5fe026a1c4e1905b47e938fecbf9->02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9 range to [0 mSAT-0 mSAT]
2023-12-08T20:18:58.7650834Z 2023-12-08 20:18:57.080 [DBG] CRTR: Payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d in state terminate=false, active_shards=0, rem_value=50000000 mSAT, fee_limit=2500000 mSAT
2023-12-08T20:18:58.7651531Z 2023-12-08 20:18:57.080 [DBG] CRTR: PaymentSession(d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d): pathfinding for amt=50000000 mSAT
2023-12-08T20:18:58.7651985Z 2023-12-08 20:18:57.080 [DBG] CRTR: Pathfinding absolute attempt cost: 150 sats
2023-12-08T20:18:58.7652414Z 2023-12-08 20:18:57.081 [DBG] CRTR: Pathfinding perf metrics: nodes=1, edges=1, time=342.597µs
2023-12-08T20:18:58.7653273Z 2023-12-08 20:18:57.081 [DBG] CRTR: PaymentSession(d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d): not splitting because destination doesn't declare MPP or AMP
2023-12-08T20:18:58.7654098Z 2023-12-08 20:18:57.081 [WRN] CRTR: Failed to find route for payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d: unable to find a path to destination
2023-12-08T20:18:58.7654933Z 2023-12-08 20:18:57.081 [DBG] CRTR: Marking payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d permanently failed with no route: no_route
2023-12-08T20:18:58.7655828Z 2023-12-08 20:18:57.091 [DBG] CRTR: Payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d in state terminate=true, active_shards=0, rem_value=50000000 mSAT, fee_limit=2500000 mSAT
2023-12-08T20:18:58.7656165Z 2023-12-08 20:18:57.091 [WRN] RPCS: Unable to send payment: no_route

The failed payment is d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d. The most interesting line seems to be:
2023-12-08T20:18:58.7645306Z 2023-12-08 20:18:57.069 [WRN] CRTR: Attempt 2 for payment d830db20d8af3eb5a8fb800f061f2fba3ea9d899190ba6c48a2854288f00635d failed: UnknownNextPeer@1

This comment suggests that one of the nodes in the path was offline.

Error in transaction funding: Misuse error: Funding transaction absolute timelock is non-final

Might be an issue on the coordinator, failing to open the jit channel? 🤔

I can confirm that the channel that was closed due to the Funding transaction absolute timelock is non-final error was indeed the jit channel that should have been created for the test. That explains the no route found.

// Transactions are evaluated as final by network mempools if their locktime is strictly
// lower than the next block height. However, the modules constituting our Lightning
// node might not have perfect sync about their blockchain views. Thus, if the wallet
// module is ahead of LDK, only allow one more block of headroom.

It might be an issue with our on-chain wallet sync.

Error in transaction funding: Misuse error: Funding transaction absolute timelock is non-final

Might be an issue on the coordinator, failing to open the jit channel? 🤔

You're right and I think I know why.
When building the funding transaction BDK sets a locktime to prevent fee sniping:
        let lock_time = match params.locktime {
            // When no nLockTime is specified, we try to prevent fee sniping, if possible
            None => {
                // Fee sniping can be partially prevented by setting the timelock
                // to current_height. If we don't know the current_height,
                // we default to 0.
                let fee_sniping_height = current_height.unwrap_or(LockTime::ZERO);

                // We choose the biggest between the required nlocktime and the fee sniping
                // height
                match requirements.timelock {
                    // No requirement, just use the fee_sniping_height
                    None => fee_sniping_height,
                    // There's a block-based requirement, but the value is lower than the fee_sniping_height
                    Some(value @ LockTime::Blocks(_)) if value < fee_sniping_height => fee_sniping_height,
                    // There's a time-based requirement or a block-based requirement greater
                    // than the fee_sniping_height use that value
                    Some(value) => value,
                }
            }

I strongly suspect BDK's current_height can be slightly in the future and we end up with a non-final funding transaction. This can happen because we don't set the current_height when building the transaction, so BDK just takes its latest sync height. We can't guarantee that LDK has been synced as far as BDK, so we run into
Funding transaction absolute timelock is non-final

Error in transaction funding: Misuse error: Funding transaction absolute timelock is non-final

Might be an issue on the coordinator, failing to open the jit channel? 🤔

You're right and I think I know why.
When building the funding transaction BDK sets a locktime to prevent fee sniping:
        let lock_time = match params.locktime {
            // When no nLockTime is specified, we try to prevent fee sniping, if possible
            None => {
                // Fee sniping can be partially prevented by setting the timelock
                // to current_height. If we don't know the current_height,
                // we default to 0.
                let fee_sniping_height = current_height.unwrap_or(LockTime::ZERO);

                // We choose the biggest between the required nlocktime and the fee sniping
                // height
                match requirements.timelock {
                    // No requirement, just use the fee_sniping_height
                    None => fee_sniping_height,
                    // There's a block-based requirement, but the value is lower than the fee_sniping_height
                    Some(value @ LockTime::Blocks(_)) if value < fee_sniping_height => fee_sniping_height,
                    // There's a time-based requirement or a block-based requirement greater
                    // than the fee_sniping_height use that value
                    Some(value) => value,
                }
            }

I strongly suspect BDK's current_height can be slightly in the future and we end up with a non-final funding transaction. This can happen because we don't set the current_height when building the transaction, so BDK just takes its latest sync height. We can't guarantee that LDK has been synced as far as BDK, so we run into
Funding transaction absolute timelock is non-final

Hopefully fixed with https://github.com/get10101/10101/pull/1709.

found a bug...

yay, all tests run (locally) :)

@holzeis

I think the reject flow would also be useful for the CloseOffer message.

The CloseOffer message only contains the amount which was proposed but it does not have a expiry/maturity time like the OpenOffer messages. I think this is out of scope of this ticket which only handles outdated offers.


improve overloads and par validation

Codecov Report

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

@@           Coverage Diff           @@
##           master     #216   +/-   ##
=======================================
  Coverage   88.99%   88.99%
=======================================
  Files          60       60
  Lines        2108     2108
  Branches      262      262
=======================================
  Hits         1876     1876
  Misses        231      231
  Partials        1        1

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 6bbef56...26651c3. Read the comment docs.


Data type of HISTORY_PREVIOUS_VALUE

In the FileChecker,  HISTORY_PREVIOUS_VALUE is type float in all of the file types except Bio-profile.  In Bio-profile, either float or double is accepted.  I don't remember the history of this.
My question: What should we enforce for traj-v3.2?
(I am currently only allowing float but Jean-Philippe uses double in some or all of his v3.2 files.)

Hi @MarkIggy.  I believe "double" is needed in bgc files because some bgc parameters need 64bit storage. e.g. radiometry counts.  The data type of each parameter is noted in the parameters xlsx, which @catsch maintains.  The GDAC file checker should be synched with the parameters xlsx.
Since traj-v3.2 is designed to hold both core and bgc parameters, HISTORY_PREVIOUS_VAUE in traj-v3.2 should accommodate both float and double values.  Most floats will only require "float", but some bgc floats will require "double".

This issue was implemented in v2.8.00.
HISTORY_PREVIOUS_VALUE may be either float or double in traj-v3.2


ARROW-8044: [CI][NIGHTLY:gandiva-jar-osx] Pin libgit2 at 1.0

@ursabot crossbow -g gandiva-jar-osx

Doing pip3 install pygit2==1.0.3 (the earlier version) here https://github.com/apache/arrow/blob/aec37d768abbee3ea3ce4c32002462ff0e1c3674/dev/tasks/gandiva-jars/travis.osx.yml#L60 should solve the issue. The brew libgit2 package is not yet updated to 1.0.x

@projjal thanks, I'll try that

@ursabot crossbow --help

Manual crossbow https://travis-ci.org/bkietz/crossbow/builds/660702789


Implicit boolean conversion of Objective-C object literal always evaluates to true

Description
I upgraded my react-native version to 0.43.0. And ran my app in xcode 9.2 but i get this error: "Implicit boolean conversion of Objective-C object literal always evaluates to true" on line 685: -> statement: "return @NO;"
How to repeat issue and example
Run Xcode 9.2 and received this warning "Implicit boolean conversion of Objective-C object literal always evaluates to true" in File ImagePickerManager.m
Additional Information

React Native version: [0.43.0]
Platform: [iOS]
Development Operating System: [MacOS]
Dev tools: [Xcode]

Were you running the example app or did you install this as a dependency in an existing application?


Monitor and/or Reduce OpenShift Resource Usage for FormsFlowAI via SysDig

Title of ticket: Monitor and/or Reduce OpenShift Resource Usage for FormsFlowAI via SysDig
Description
In task #1238, we need to increase CPU/mem availability so we can host a new Redash.
This task is about using SysDig in combination with load-testing of the application.  The goal is to either:

Identify there is under-utilized resources and properly tune formsflow deployment to use less.
Identify all resources are fully utilized, and make a request to platform team for more space.

Dependencies
Load-testing using JMeter is working
DOD

[x] SysDig dashboards are working and displaying resource utilization
[ ] SysDig reports/dashboards created during load testing
[ ] Solution is identified (either tuned down resource limits or requesting more resources)

@acoard-aot Is the goal to complete this task in its entirety during this sprint or do we need to revisit scope?

Potentially need to revisit.  There is still more work for me to do here,
but a large chunk of the work can only begin after Richard is done his load
testing work.  I don't know exactly how long that will take, but could
potentially push into next sprint.  Good to raise it and happy to discuss
more, maybe at next standup? I can split up tasks if that's what we decide.
On Mon, Jan 17, 2022 at 10:36 AM molly pilchar @.***>
wrote:

@acoard-aot https://github.com/acoard-aot Is the goal to complete this
task in its entirety during this sprint or do we need to revisit scope?
—
Reply to this email directly, view it on GitHub
https://github.com/bcgov/foi-flow/issues/1240#issuecomment-1014805264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOTSLJRVGVRVICLRJEAL5ILUWRORBANCNFSM5LKPLBRA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Splitting ticket and marking the remaining ticket as completed.


Version Control Git

Any plans to implement version control on schema's

Hi @sbansal6 - Not sure I understand. Are you talking about the database schema of the connection or of sqlpad's object model schemas?

I think having VCS on the query could be nice and the ability to roll back to a previous version of your saved query.

@rickbergfalk :- I mean source controlling database schema and objects. Their no open source tool that does it, only few proprietary ones.

http://www.red-gate.com/products/sql-development/sql-source-control/

@sbansal6 - I've used red-gate's tooling in the past and their sql source control is really cool. Unfortunately though I think it might be a bit out of scope for this project...
@jameswinegar query history would be a nice add, although I think we'd need a way to limit it in some way. The embedded database used by sqlpad stores a copy of everything in memory. While I'm sure it could hold a lot, if such a feature was worked on there would need to be a way to limit the save history... maybe to the previous n versions (maybe even configurable in the settings?).
If that seems desirable we can repurpose this issue - otherwise I can close it.

I'm going to close this issue for now - open to any pr that adds query history/previous query versions.


support references for examples

Like other items that support the $ref syntax, would like to have $ref support for example values.

@fehguy There is a problem with it.
example is user supplied data so it can natively have $ref.
For example, API that returns JSON Schemas, or any other JSON data since JSON Pointer is widely used.
And I have real-life example, Google Discovery is API that returned data format based on top of JSON Schema.

So I guess this can only work easily if we wrap the actual examples in some other format. Is this sensible?

#636 did some changes related to this, but I'm not sure if this finished this issue.

@fehguy - see https://github.com/OAI/OpenAPI-Specification/issues/666#issuecomment-213364604.

PR #636 added Example Objects, and they can be referenced in 3.0.  #666 definitively decided that referencing example values (which can look identical to references in some cases) will not be done.
Closing this as resolved with referenceable Example Objects in 3.0.


Make ReplicationRules::get_info crate-private for safety

Problem
ReplicationRules::get_info() is unsafe if you use an unknown replication id, which may come from an invalid serialization (since the replication id itself is crate-private).
Solution
Mark it with pub(super).

I remember it and working on API rework for rules right now. Want to solve it a bit differently.

Codecov Report
Patch coverage: 99.09% and project coverage change: -0.93% :warning:

Comparison is base (0fc7044) 95.61% compared to head (dbdb5bb) 94.69%.
Report is 7 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
- Coverage   95.61%   94.69%   -0.93%
==========================================
  Files          10       10
  Lines         662      735      +73
==========================================
+ Hits          633      696      +63
- Misses         29       39      +10

Files Changed
Coverage Δ

src/lib.rs
100.00% <ø> (ø)

src/client.rs
89.42% <96.00%> (+4.17%)
:arrow_up:

src/replicon_core.rs
94.04% <100.00%> (-2.93%)
:arrow_down:

src/server.rs
97.17% <100.00%> (+0.70%)
:arrow_up:

... and 1 file with indirect coverage changes

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

Opened #49.

Superseded by #49.


Obsidian Sync issue with icon-folder

I would like to ask, what the right way is to store zip files or any other possible large files so that Obsidian sync successfully syncs the files. We are currently experiencing some issues with Sync and the icon folder plugin.
You've already created one issue here. But that didn't really solve the issue for some users. So I've tried to add a new syncing mechanism that just adds the zip files which includes the icons. But that didn't really work either (see this issue).
So, I would like to ask, what's the right approach I need to follow for users not complaining anymore about syncing failures of this plugin?

If you're using a single file then you can put it in your plugin folder to have it synced with your plugin - other folders inside .obsidian is simply ignored which is why .obsidian/icons/ is never synced.
The support reply seems to link to the previous discussions we've had:

We've tried reaching out to them to make the .obsidian/icons/ the default behavior, but to no avail. https://github.com/FlorianWoelki/obsidian-iconize/issues/52

It seems like the plugin still defaults to unpacked icons in the plugin folder, which interferes with Sync functionality. I highly suggest defaulting the icon locations to NOT your plugin folder as it will get synced when the user chooses to sync their plugins, unless you pack them into a single file.

If you're using a single file then you can put it in your plugin folder to have it synced with your plugin - other folders inside .obsidian is simply ignored which is why .obsidian/icons/ is never synced.
The support reply seems to link to the previous discussions we've had:

We've tried reaching out to them to make the .obsidian/icons/ the default behavior, but to no avail. FlorianWoelki/obsidian-iconize#52

It seems like the plugin still defaults to unpacked icons in the plugin folder, which interferes with Sync functionality. I highly suggest defaulting the icon locations to NOT your plugin folder as it will get synced when the user chooses to sync their plugins, unless you pack them into a single file.

Alright, thank you for the suggestion! I'll update the plugin so that the path defaults to .obsidian/icons/.
Thank you!

Because this plugin creates thousands of icon files which clogs up the syncing process. Moving it there precisely prevents these icons from being synced.


Import for ADE20K dataset

Summary
Resolved #399.
How to test

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG
[ ] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] I have linked related issues

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

@zhiltsov-max Fixed all comments from you.

Could you check if the imported dataset can be converted into some other format? Pascal VOC or other.

I checked converting with VOC, COCO and KITTI formats. Conversion to COCO failed, but I think it's no related with this PR, the problem occurs here:
https://github.com/openvinotoolkit/datumaro/blob/935fb0ede3c70a68582c7d13b5f5450e51f81235/datumaro/plugins/coco_format/converter.py#L232-L234
masks has type generator, but then we use += between generator and itertools.chain Python doesn't support such concatenation. Or I'm wrong?

masks has type generator, but then we use += between generator and itertools.chain Python doesn't support such concatenation. Or I'm wrong?

Yes, looks like a bug in COCO. Will you fix it?

masks has type generator, but then we use += between generator and itertools.chain Python doesn't support such concatenation. Or I'm wrong?

Yes, looks like a bug in COCO. Can you fix it?

Yes, I'll fix it in new PR.


refactor: Rename DataGridView Extensions

This brings it in line with other extension methods, following #158

:tada: This PR is included in version 1.8.1 :tada:
The release is available on:

v1.8.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.8.1 :tada:
The release is available on:

v1.8.1
GitHub release

Your semantic-release bot :package::rocket:


add failing test to demonstrate #399

Problem
add failing test to demonstrate issue in #399
Solution
added test_get_status_display
Commandments

[ ] Write PEP8 compliant code.
[ ] Cover it with tests.
[ ] Update CHANGES.rst file to describe the changes, and quote according issue with GH-<issue_number>.
[ ] Pay attention to backward compatibility, or if it breaks it, explain why.
[ ] Update documentation (if relevant).

I guess this PR isn't any relevant anymore. Cherrypicked test_get_status_display and the test is no longer failing. So I'm closing this.


virsh define ... looks for qemu in /usr/bin

Describe the bug
sudo virsh define template.xml
error: Failed to define domain from template.xml
error: Cannot check QEMU binary /usr/bin/qemu-system-x86_64: No such file or directory

To Reproduce
Activate the libvirt module and install virt-manager (might not be necessary).

Oh, the template.xml references the qemu path and it's just being generated incorrectly by $TOOL. This isn't a nixpkgs issue.


InvalidContentLink

The dependency on the ARM template has changed to bicep.
This causes the error: Unable to download deployment content from '
https://raw.githubusercontent.com/Azure-Samples/cognitive-services-speech-sdk/master/samples/ingestion/ingestion-client/Setup/ArmTemplateBatch.json'.
I

URL in Customer-Service-Conversational-Insights-with-Azure-OpenAI-Services/blob/infrastructure/ARM/deployment-template.json  is probably: https://raw.githubusercontent.com/Azure-Samples/cognitive-services-speech-sdk/master/samples/ingestion/ingestion-client/infra/main.json

I got a version error and the deployment worked when substituting the Version 0301 to 1106

Thank you for your feedback @JuFranze. Our team will review and respond to your logged issue. Your patience is appreciated.

Hi @JuFranze - Issue has been addressed as part of #116 . Please try re-deploying and let us know if any further issues. Thanks.

Closing issue per @Roopan-Microsoft's update above.

@JuFranze - Use ckm-v1 branch to deploy the Version 1.


Cpp17CopyAssignable requirements を追加

https://eel.is/c++draft/utility.arg.requirements#tab:cpp17.copyassignable

完了


Feature/nest 4 devon4j

Issue Number
No issue
Implementation description
Changed the nestjs types to be compatible with the new angular version.
@devonfw

 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.

Please @dario-rodriguez sign the CLA in order to merge this PR. Thanks!

Changed the nestjs types to be compatible with the new angular version.

Are simlar changes needed to https://github.com/devonfw/devon4node/tree/develop/template ?

Changed the nestjs types to be compatible with the new angular version.

Are simlar changes needed to https://github.com/devonfw/devon4node/tree/develop/template ?

I think no. Those changes are related to the new response structure introduced by devon4j. In this case we need all backends send the same response in order to work with the same frontend.


Docs: Add introduction documentation for cairo vm - Issue #328

This PR is for the issue Intro Documentation #328. Added intro documentation to understand in a general way all the sections as a small summary of what we'll see in the specific parts.

Did you use AI for the part about builtins? We should avoid things like:
" These include managing resource usage effectively to prevent performance degradation or vulnerabilities, ensuring robust security measures to mitigate risks such as integer overflow, reentrancy attacks, and access control issues, and maintaining compatibility with existing standards and protocols within the blockchain ecosystem. "

Thank you for the feedback, I will apply the changes as soon as possible and I will modify that sentence to avoid that kind of explanation

Hi @TAdev0 can you review these changes please, I considered all your comments for this improvement but if something is needed to improve I will do it, thanks.

hi @coxmars  any update on this?

hi @coxmars any update on this?

I'm finishing applying the changes, I'll let you know as soon as I have it.

Hey @coxmars if you need any help please let us know

Hey @coxmars if you need any help please let us know

Hi Rodrigo, I would like you to give me some context/guidance on the resources section, what do you mean by that? I did not find related information or maybe I did not understand the specific approach to address the explanation. Thank you.

@TAdev0 improvements applied if you need other changes just let me know, thanks


Release 2.19.2

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Can't insert data when using source option for schema field

I'm using the source field option to map a field to a differently named table column. This works when selecting data, but not when inserting data:
Test:
  describe "issue" do
    setup do
      query!("""
      create table if not exists field_source (
        id String,
        field_name String
      ) engine MergeTree
      ORDER BY (id)
      """)

      query!("""
      INSERT INTO field_source VALUES ('insert', 'value');
      """)
      :ok
    end

    defmodule Stuff do
      use Ecto.Schema

      @primary_key false
      schema "field_source" do
        field(:id, Ch, type: "String")
        field(:name, Ch, type: "String", source: :"field_name")
      end
    end

    test "foobar" do
      all(Stuff)
      |> dbg()

      insert_all(Stuff, [
        %{id: "foo", name: "bar"},
        %{id: "foobar", name: "bax"},
      ])
      |> dbg()
    end
  end

Output
[test/ch/type_test.exs:767: Ch.TypeTest."test issue foobar"/1]
all(Stuff) #=> [
  %Ch.TypeTest.Stuff{
    __meta__: #Ecto.Schema.Metadata<:loaded, "field_source">,
    id: "insert",
    name: "value"
  }
]

  1) test issue foobar (Ch.TypeTest)
     test/ch/type_test.exs:765
     ** (RuntimeError) missing type for field :field_name
     code: insert_all(Stuff, [
     stacktrace:
       (ecto_ch 0.3.0) lib/ecto/adapters/clickhouse/schema.ex:229: anonymous fn/2 in Ecto.Adapters.ClickHouse.Schema.extract_types/2
       (elixir 1.15.7) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
       (elixir 1.15.7) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
       (ecto_ch 0.3.0) lib/ecto/adapters/clickhouse/schema.ex:44: Ecto.Adapters.ClickHouse.Schema.insert_rows/5
       (ecto_ch 0.3.0) lib/ecto/adapters/clickhouse/schema.ex:33: Ecto.Adapters.ClickHouse.Schema.insert_all/8
       (ecto 3.10.3) lib/ecto/repo/schema.ex:59: Ecto.Repo.Schema.do_insert_all/7
       test/ch/type_test.exs:769: (test)

👋 @hkrutzer
The error comes from https://github.com/plausible/ecto_ch/blob/36348a1a838f74efadd8346d0982c39e3079955a/lib/ecto/adapters/clickhouse/schema.ex#L229
Seems like we'd need to check for __schema__(:field_source, field) as well.

Not sure, I don't know how other adapters do this, but I couldn't easily find it. I guess they don't have to look up the type like ecto_ch has to?

Yes, other adapters don't need to do this kind of reflection.

https://github.com/plausible/ecto_ch/pull/137 should fix it. It's included in v0.3.1 release.

It's fixed, thanks very much!


setfacl - Operation not permitted

Hello, I am getting an error with Symfony 4 projects when using setfacl. It was working fine with my Symfony 3.4 projects. The error is this:
  The command "cd /var/www/html/my_website/releases/48 && (setfacl -L -R -
  m u:"www-data":rwX -m u:`whoami`:rwX var)" failed.

  Exit Code: 1 (General error)

  Host Name: mywebsite.com

  ================
  setfacl: var/log/prod-2019-12-18.log: Operation not permitted

Every day I have to login into the server and launch this script before launching Deployer:
sudo chmod -R 777 var/
Do you know why it's giving this error?
Thanks!

Add this sudo chmod -R 777 var/ as task for deploy)) Some owners issues.

The problem is that the deployer user has no right to perform sudo commands. Why was it working with Symfony 3.4? What was changed in the recipe? Thanks

I had the same issue with setfacl and could fix it by adding the user that i deploy with to the group of my web-server user.

same issue. In my case it was the rights of the log file. Don't know why deployer needs to touch that.
command that failed cd /srv/www/myproject/releases/14 && (setfacl -L -R -m u:"www-data":rwX -m u:whoami:rwX var)
../shared/var/log/prod.log
Solution was to put the file to rwxrwxr--, while rw-rw-r-- was not enough.
My deployer user belongs to the www-data group

Maybe that's what https://serverfault.com/a/936550/119666 is suggesting.

It is better for you to create a new user for the deployment. Do not use 777 in production mode. You may read my write up regarding server configuration with deployer in here

Unfortunately the bug is still here but I managed to resolve it by editing the writable_dirs. Instead of using add I use set and I manually configure the folders:
<?php

namespace Deployer;

require 'recipe/symfony4.php';

//
// Config
// ======

// project name
set('application', 'mywebsite');

// project repository
set('repository', 'git@bitbucket.org:myhost/mywebsite.git');

// allows you to enter a passphrase for keys or add host to known_hosts
set('git_tty', true);

// shared files/dirs between deploys
add('shared_files', []);
add('shared_dirs', ['public/upload/media']);

// writable dirs by web server
set('writable_dirs', ['public/upload/media', 'var/cache', 'var/log', 'var/sessions']); // <=== please note this setting

I'm not 100% sure though why this is working.
In my opinion the default recipe should not mark as writable the whole var folder.

FYI : there is a better solution without using sudo by overriding the writable_dirs variable. See : https://github.com/deployphp/deployer/issues/2932#issuecomment-1026341540


battery: Add AC icon and low_threshold config

When fully charged on AC, show plug character (U+1F50C).
Add config option to show percentage even if fully charged on AC.
Add config option to set low battery threshold.

@jceaser Do you have Mac support?

yes

:+1: looks good to me

pmset -g batt | egrep "([0-9]+%)" -o


[Bug] "Alert Threshold Reached" is visible on the "Map Legend" in "No-Trigger"

Who notified us about the bug?
@Piotrk39
Describe the bug
When spend IBF-System in No-Trigger mode and user reads the legend "Alert Threshold Reached" is visible.
Steps to reproduce

Mock IBF with Floods no-trigger
Log-in
View "Map Legend"

Expected behavior
"Alert Threshold Reached" should not be visible in "Map Legend"
Dependencies
TO BE FILLED IN

@Piotrk39 can you add screenshot or video?

@arsforza can you confirm if this is actually a bug, or if it's intended? And if it's a bug, is it maybe a one line fix?

@jannisvisser I can't confirm if it is a bug or an intended behavior
from a first quick check it seems like alert_threshold is passed as active (one of the conditions needed to show layers in the legend) even when there is no trigger

@Piotrk39 I've looked at this and concluded this is a feature, not a bug. Maybe a questionable feature, but so be it. Closing this.

@BlaiseSelvan  Ping.


Service containers have their working directory changed when launched

Component
server
Describe the bug
From 2.7.0 if I add a service container that had WORKDIR set in Dockerfile the service won't be able to find files via relative paths (or it expects to find files in it's current folder).
Workaround:  Set directory manually on the service
Steps to reproduce

Create a container that has WORKDIR set to something you know the contents of and set CMD and ENTRYPOINT to ls
Add said container to a pipeline as a service (with no commands ofc)
Observe the output, it should be different from WORKDIR's contents.

Expected behavior
Working directory inside the container should be left alone and be the same set in the container.
System Info
{"source":"https://github.com/woodpecker-ci/woodpecker","version":"2.7.0"}

docker-compose config:
version: '3'

services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:v2.7.0
    ports:
      - 5000:8000
      - 10000:9000
    volumes:
      - ./data:/var/lib/woodpecker/
      - /etc/ssl/certs:/etc/ssl/certs:ro
      - /etc/timezone:/etc/timezone
      - /etc/docker/certs.d:/etc/docker/certs.d:ro
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=REDACTED
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=REDACTED
      - WOODPECKER_GITEA_CLIENT=a3439c88-9061-4ce7-b3dc-64500fd5257f
      - WOODPECKER_GITEA_SECRET=REDACTED
      - WOODPECKER_GITEA_SKIP_VERIFY=true
      - WOODPECKER_AGENT_SECRET=REDACTED
      - WOODPECKER_ADMIN=Gr3qi
      # - WOODPECKER_LOG_LEVEL=debug
      - WOODPECKER_AUTHENTICATE_PUBLIC_REPOS=true
      #- WOODPECKER_MIGRATIONS_ALLOW_LONG=true
      - WOODPECKER_BACKEND_DOCKER_VOLUMES=/etc/ssl/certs:/etc/ssl/certs:ro,/etc/timezone:/etc/timezone,/etc/docker/certs.d:/etc/docker/certs.d:ro
  # woodpecker-agent:
    # image: woodpeckerci/woodpecker-agent:v2.6.0
    # command: agent
    # restart: always
    # depends_on:
      # - woodpecker-server
    # volumes:
      # - /var/run/docker.sock:/var/run/docker.sock
      # - /etc/ssl/certs:/etc/ssl/certs:ro
      # - /etc/timezone:/etc/timezone
      # - /etc/docker/certs.d:/etc/docker/certs.d:ro
    # environment:
      # - WOODPECKER_SERVER=woodpecker-server:9000
      # - WOODPECKER_AGENT_SECRET=REDACTED
      # - WOODPECKER_BACKEND_DOCKER_VOLUMES=/etc/ssl/certs:/etc/ssl/certs:ro,/etc/timezone:/etc/timezone,/etc/docker/certs.d:/etc/docker/certs.d:ro

Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

this migth happen if the service has no commands (as usual) and no environment set, it will count as plugin. and plugins get set there working directory.
using the directory is no workaround but the solution!
this is done because of security considerations.
I think we should add an hint to use directory into the docs :)
In any case normally you should not have to set a workdir as it will be set to the root of where the workflow workspace is mounted at.
@Gr3q does this answer/solve your issue and could you propose a good place where to put that hint into the docs?

If you want to put it somewhere it should be above https://woodpecker-ci.org/docs/usage/services#configuration where you note that any container setting WORKDIR in it's Dockerfile might not work as expected and you need to redefine it with the directory field.

this migth happen if the service has no commands (as usual) and no environment set, it will count as plugin. and plugins get set there working directory.

I have environment set.
services:
  - name: database
    image: linuxserver/mariadb
    pull: true
    environment:
      - TZ=Europe/London
      - MYSQL_USER=dockeruser
      - MYSQL_ROOT_PASSWORD=root
      - MYSQL_PASSWORD=testpw
      - MYSQL_DATABASE=api

  - name: signing-server
    image: REDACTED
    pull: true
    # Unfortunately this is needed now...
    directory: /api
    environment:
      - TEST_MODE=True
      - TEST_SIGN_CLIENT_ID=test
      - TEST_SIGN_CLIENT_SECRET=test

In any case normally you should not have to set a workdir as it will be set to the root of where the workflow workspace is mounted at.

This is only good in the use case where a service you want to run might depend on (uses files from) the repo the pipeline runs on.
For the use case when you just want to run something like redis/db as a service it doesn't make sense. To use the workaround you also need to have knowledge about the internals of the image used, which is not always the case.
The question is how the affected images are treated. Either:

The fault is with the image in question, meaning they should work with their WORKDIR changed. An upstream bug report would need to be opened.
Or docker images can reasonably assume that the WORKDIR is not changed when their own RUN or ENTRYPOINT commands are used. In this case the fault is whoever runs the image incorrectly.

Some addition info that the linter says I shouldn't use directory on services
[linter]unit-tests-with-cache: servicesMust validate one and only one schema (oneOf)
[linter]unit-tests-with-cache: services.1Additional property directory is not allowed

-> #4127

Did this get fixed by #4127?

I would say https://github.com/woodpecker-ci/woodpecker/issues/3993#issuecomment-2353089981 + mentioned issue should fix it ...


Problem with Google Service Json

File google-services.json is missing. The Google Services Plugin cannot function without it. i am trying to run this application in my visual studio code but missing one file

Fixed by https://github.com/nt4f04uNd/sweyer/pull/21 - google-services.json is now checked in


Update the example to use node8.10 by 30/04/2019 - Node 6 is being deprecated on AWS Lambda

AWS sent me this email:

Invokes for functions configured to run on node.js 6.10 will continue to work normally, however the ability to create new Lambda functions configured to use the node.js 6.10 runtime will be disabled on April 30 2019. Code updates to existing functions using node.js 6.10 will be disabled 30 days later on May 30 2019

7 days to go until Amazon drop support and the example and the quick start on this repo stop working.
This won't work after 30/4:
serverless create -u https://github.com/adieuadieu/serverless-chrome/tree/master/examples/serverless-framework/aws

Ok well time to close this one because you missed out entirely on node 8 which is now also being deprecated.


Problems with large svg image

Hi,
I've tried to use vzl with a file that generates a large svg image but the image gets too small. See the image below:

I've tried to add keyboard shortcuts to change the scale of the divs but that didn't work very well. The div that contains the svg doesn't scale correctly.
globalShortcut.register('CommandOrControl+=', () => {
  webFrame.setZoomFactor(webFrame.getZoomFactor() + 0.1);
})

globalShortcut.register('CommandOrControl+-', () => {
  webFrame.setZoomFactor(webFrame.getZoomFactor() - 0.1);
})

globalShortcut.register('CommandOrControl+0', () => {
  webFrame.setZoomFactor(1);
})

I don't know much about electron but if you point me the direction I can send a PR fixing this issue.
Regards

You can try using svg-pan-zoom


mariadb-connector-c: add mysqlclient.pc pkgconfig symlink

Motivation for this change
Some projects, like the mysqlclient-sys rust crate, use pkg-config to locate the mysqlclient library.
The mariadb-connector-c package only provides compatibility links for the mysql libs and includes. Adding the mysqlclient.pc link increases the compatibility with the build expecting the alternative name.
This fixes the currently failing build of bitwarden_rs-mysql in master and release-20.03.
ZHF: #80379
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @globin

сс @aanderse @Mic92

Please also cherry-pick this into staging-20.03 as a PR.


Functionality with Landis o Gyr E360

Has anyone successfully used this with a Landis o Gyr E360?
I only receive data sporadically, CRC seems to always be correct though.
The problem seems to be that i’m missing some of the data.
From log.txt:
--- Start 374880 ---
0x29, 0x0d, 0x0a, 0x31, 0x2d, 0x30, 0x3a, 0x35, 0x31, 0x2e, 0x37, 0x2e, 0x30, 0x28, 0x30, 0x30,
0x30, 0x2e, 0x30, 0x2a, 0x41, 0x29, 0x0d, 0x0a, 0x31, 0x2d, 0x30, 0x3a, 0x37, 0x31, 0x2e, 0x37,
0x2e, 0x30, 0x28, 0x30, 0x30, 0x30, 0x2e, 0x30, 0x2a, 0x41, 0x29, 0x0d, 0x0a, 0x21, 0x38, 0x42,
0x37, 0x32, 0x0d, 0x0a,
---  End  ---

Landis&Gyr has some bugs, see this thread: https://www.byggahus.se/forum/threads/elmaetare-h1-port-p1-port-han-port-manga-namn-verkar-florera.384608/page-4
It might be that Landis&Gyr send data in chunks with some delay and my implementation is configured to start process the data X ms after data was received,
You may want to try this implementation: https://github.com/psvanstrom/esphome-p1reader/ Let us know if this implementation works.


Deploy on Ultron Testnet

RPC URL: https://ultron-dev.io/
Chain ID - 1230
Currency Symbol - ULX
Block Explorer URL - https://explorer.ultron-dev.io/
Faucet - https://faucet-frontend.ultron-dev.io/

Deployed contracts:

Witnet Solidity Bridge:

WitnetDecoderLib: 0x0985FDe9f424fe4f5AC516F66bAf5591e18aCBEb
WitnetParserLib: 0x7D8A488BACB56dA2De17628e26a21fFd97792b81
WitnetProxy: 0x58D8ECe142c60f5707594a7C1D90e46eAE5AF431
WitnetRequestBoardTrustableDefault: 0x02Cd4089679EAA9431a88170fd784e7dE78A2425

Witnet use cases:

WitnetPriceRouter: 0xB4B2E2e00e9d6E5490d55623E4F403EC84c6D33f
WitnetRandomness: 0xeD074DA2A76FD2Ca90C1508930b4FB4420e413B0

Witnet price feeds:

Price-ULX/USDT-6: 0x4092CC222B1bD1176D8a8cBE4070ccea66E9d1D6

Contract verification funcionality is not yet available at https://explorer.ultron-dev.io/

Bridge and poller use different evm addresses, as usual.

Ultron testnet stack running on bootstrap machine.

Related PRs:

https://github.com/witnet/witnet-solidity-bridge/pull/301
https://github.com/witnet/witnet-price-feeds/pull/161
https://github.com/witnet/data-feeds-explorer/pull/280

ULX/USDT got published in DFE:

https://feeds.witnet.io/ultron/ultron-testnet_ulx-usdt_6

Added change request to https://docs.witnet.io

Deploying two additional price feeds:
* Price-WBTC/WULX-6: 0x502792a6dc858925e9Fb0c3E730411AEb5bB2c4A
* Price-WETH/WULX-6: 0xa0a6c0Ef4Fa60E380Ce28A5e3Ce74508E884a537


Cursor positioning with swipe gesture

Here is a cursor positioning via swipe gesture on the virtual keyboard, so it acts like the pythonista VK.  Basically, the VK now holds a ScrollView, which allows capturing of swipes without switching back to the editor( unlike a custom ui.View).  Except, rather than scrolling the ScrollView, it keeps track of incremental changes, applying a scale factor from pixels to characters.  When the integrated offset is more than 1 character, the ShTerm.io cursor position is updated.
In retrospect, probably only one ShVk is needed, but I created one for each key group, since originally things were not working.  also, I suspect that you will want to add higher level cursor positioning functions to ShTerm, rather than the low level TextField manipulation that I resort to here.  Not sure if this would work with ssh for example.  But this works nicely, and I think is easier than an actual arrow button.  Vertical scroll would also work (would need to oversize the content_size height, and track vertical motion, perhaps calling the VK tapped functions for up and down buttons to scroll through history..

wow thanks @jsbain !
I only had the new branch pushed couple hours back. Here you already sent a pull request and it looks to be a really useful feature.
I am still looking at your changes and learning how it is done. I do notice that the swipe is only recognised when swiping on an area that is not covered by those virtual buttons. This makes it difficult to use on my iPhone 4s unless I put on the landscape mode. So it would be great if swipe can also be tracked when on top of those buttons (Pythonista's own VK does have this function). Is it possible?
I totally agree that higher level interfaces are needed for cursor position manipulation. There are many things needs to be done to rationalise interfaces, especially around ShTerm. I'll keep working on them.
PS: I am going to manually merge this request as Travis CI test failed. But that is only because the dummyui module does not yet have a ScrollView class. It will be an easy fix. Thanks!

If you start swiping in a non button area, it should recognize the swipe.  Actually, on my ipad, I thought that even if I started on a button, if I immediately swipe, it recognized it as a swipe.  I'll play around with it later.

Sorry jsbain. You are right. It does recognise the swipe even on the button
area!! That's awesome! Thanks!
On Saturday, 24 January 2015, jsbain<EMAIL_ADDRESS>wrote:

If you start swiping in a non button area, it should recognize the swipe.
Actually, on my ipad, I thought that even if I started on a button, if I
immediately swipe, it recognized it as a swipe. I'll play around with it
later.
—
Reply to this email directly or view it on GitHub
https://github.com/ywangd/stash/pull/74#issuecomment-71298818.

--
                  Life is elsewhere

@jsbain The popup button looks awesome. Is it possible to have popup buttons and still retain the swipe gesture for cursor positioning? Or will the popup button intercept the swipe gesture and block the scrollview from working?
It would be great if we can have both popup buttons and swipe gesture support. But even if they cannot co-exist, it will still be useful to have at least one popup button in stash. I am thinking of the rightmost one that by default switch key groups. A long-tap can bring up a mini-menu and many interesting stuff can be put in there, e.g. configuration management, possible future multi-tab switch, buttons for possible future editor mode.

We're somewhat limited in what we can do for ui's presented as panel, because it means i don't get to use touch_moved.
With minor changes to the PopupButton concept, it should be possible to implement a simply long-tap popup group of buttons.
I'll have to verify that the scroll gesture doesn't interfere with the touch events for custom buttons.
The pop up will work differently than my example, because in that example you drag your finger to select the button:  this will actually be much simpler, long tap will pop up a list of other characters in an extra row (or maybe could fly out as a vertical column, or depending on orientation), which you then would use a second tap to either select a key, or tap outside of the VK to cancel entry.  I'll mock something up this weekend.

@jsbain Yes It is indeed annoying that drag gesture cannot be used in panel mode. I hope this is a bug and will be fixed eventually. In my opinion, panel mode is still the best choice for stash even with its limitation simply because it persists.
You are right that what I described really is just a long tap action. I didn't realise the difference. I guess drag and select will not work in panel UI. So long tap is an Ok alternative. I'd prefer to keep the cursor positioning function. So if custom view does interfere with it, we can just have one custom view button at the rightmost position.


Update to pull_request_target

Restricted github_token permissions in integ_test workflow.

Addressed in https://github.com/aws/amazon-vpc-resource-controller-k8s/pull/47


Fix docker compose setup

Description

Fix docker compose setup making the proxy accessible from local environment.
How Has This Been Tested?

Running docker compose -f docker-compose.yaml up:
❯ docker compose -f docker-compose.yaml up
[+] Running 2/2
 ✔ Container mlmd-server     Created                                                                                0.0s
 ✔ Container model-registry  Recreated                                                                                0.1s
Attaching to mlmd-server, model-registry
mlmd-server     | WARNING: Logging before InitGoogleLogging() is written to STDERR
mlmd-server     | I1113 15:40:34.877207     7 metadata_store_server_main.cc:577] Server listening on <IP_ADDRESS>:8080
model-registry  | I1113 15:40:35.008906       1 proxy.go:31] proxy server started at localhost:8080
model-registry  | I1113 15:40:35.008978       1 proxy.go:34] MLMD server localhost:9090
model-registry  | 2023/11/13 15:40:44 "GET http://localhost:8080/api/model_registry/v1alpha1/model_versions?pageSize=100&orderBy=ID&sortOrder=DESC&nextPageToken=IkhlbGxvLCB3b3JsZC4i HTTP/1.1" from <IP_ADDRESS>:40616 - 200 56B in 3.046919ms

Merge criteria:

[x] The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

fyi @rkubis this should fix the issue you found.

fyi @rkubis this should fix the issue you found.

@lampajr Thanks!


The peek plugin window show nothing for previewing..

Describe the bug
I just follow the guidelines to install this plugin,
and I go the deno-official-website to download deno for that
I use packer to install this plugin, and I get 'installed successfully'
then I open the .md file for preview, and nothing happens
To Reproduce
just add this in packer.funcion
	use({
		"toppair/peek.nvim",
		run = "deno task --quiet build:fast",
		config = function()
            require('peek').setup()
		end,
	})

then I open a file named 'a.md', nothing happend
I use :lua require('peek').open(), then get a window, just a black for that
Expected behavior
just preview md file
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]: Ubuntu 22,04
nvim --version: 0.8.0

deno --version: latest

plugin setup: as i Described

Additional context
Add any other context about the problem here.
none

sorry about that I dont't know why I can upload the bug.png file.....
I get this

Something went really wrong, and we can't process  that file....

bug.zip

I'm running into the same issue on:
* macOS 13.0.1

* nvim 0.8.1 (homebrew)

* deno 1.28.2

The peek.log contents:
INFO      72942    28/11/2022, 11:26:36.206  DENO_ENV: undefined --logfile=/Users/steve.loveless/.local/state/nvim/peek.log --theme=dark --syntax
INFO      72942    28/11/2022, 11:26:36.217  listening on <IP_ADDRESS>:57658
INFO      72942    28/11/2022, 11:27:23.459  SIGNAL:  SIGTERM

FWIW, I was curious so I tried doing this in app/src/main.ts, but this doesn't seem to change the behavior:
// const DENO_ENV = Deno.env.get('DENO_ENV');
const DENO_ENV = 'development';

Same here with similar setup

@JuanZoran @turboladen @brancobruyneel
Can you guys check whether it is fixed now, after #23?

I just install deno and then add this to my config file

plugins:add {
'toppair/peek.nvim',
build = 'deno task --quiet build:fast',
}

but it builds failed, here is debug message:
error: Error reading config file file:///home/zoran/.local/share/nvim/lazy/peek.nvim/deno.json: Permission denied (os error 13)
I am freshman about deno, I don't how can I solve this problem

I've switched to native browser mode before to workaround the issue. Just switched back and can confirm that it works now. Thanks @toppair @jakehl!

Can also confirm it works, thanks!


UI for the Client credentials

[x] Development of UI
[x] API's integrations

Acceptance Criteria:
Creating ClientID and ClientSecret:

As an organization Owner, I should be able to create clientId and clientSecret
The client ID and client secret should be visible to the organization's owner and admin

Deleting ClientSecret:

As an organization Owner or Admin, when I navigate to the client details page, there should be an option to delete the associated
Client Secret

Copy ClientSecret:

As an organization Owner, I should be able to copy clientSecret when create clientSecret but after refresh not able to view copy button
The copy functionality should be available immediately after the creation of the clientSecret
After refreshing or reloading the page, the "Copy" button should no longer be visible, ensuring that the Client Secret cannot be copied again

Masking ClientSecret after Reload:

As an organization Owner or Admin, after creating a new Client Secret and refreshing the page, the Client Secret should be masked

Tested on the QA environment and changes look fine as per the acceptance criteria.


Add support for frozenset's to Variable Explorer and allow to graphically modify sets

Problem Description
The tuple and the list are immutable and mutable counterparts. When opened in the Variable Explorer, the tuple is greyed out and from a user perspective this is because it is immutable and cannot be modified and the list is colored meaning it can be modified:

Another pair is the frozenset and set... Unfortunately the frozenset is not supported by the variable explorer (it should look identical to the way the set is currently displayed) and the set, as it is visually appears to be immutable...
This is probably because the set methods aren't supported in the GUI. However from a user perspective, just getting started with Python, it makes the set in general look immutable:

The set has the mutable methods:
update
difference_update
intersection_update
symmetric_difference_update
__isub__
__iand__
__ior__
__ixor__

So for example using:
s.symmetric_difference_update({'world'})

s.update({'world2'})

can be used to modify the set.
These mutable methods could be used under the hood for example for:

an update button (shows a dialog box to update the set with a new value)
a subtract button (subtracts highlighted entries)
allow editing of a value in the set (in a similar manner to what can be done for a value in a list)

The dict is also a builtins collection that is mutable. The variable explorer shows the insertion order in the contracted view:

But not in the expanded view:

Perhaps an option for this should be available (and enabled by default):

Versions

Spyder version: 6.0.0a4  (conda)
Python version: 3.11.8 64-bit
Qt version: 5.15.8
PyQt5 version: 5.15.9
Operating System: Windows-10-10.0.22631-SP0

Hey @PhilipYip1988, thanks for reporting. If understand things correctly, there are several enhancement requests in your comment above:

Add support for frozenset to the Variable Explorer (we don't provide support for it yet). That's reasonable and not too hard to do.
Allow to modify sets, which should require more work but it seems doable too.
Sort dicts by insertion order, which has already been requested.

Let me know if that's correct.

Hey @ccordoba12  yes that's a good summary of the enhancement requests.


Create a double category bar chart

Is it possible to create a double category bar chart using the chartist library?

Hi @tawani 👋
In case it's still relevant here's an example.


[Microsoft Graph v1.0]: teams conversationmember list

The resourceProvisioningOptions filter is not supported in the v1.0 endpoint, but the displayName filter is, therefore we should implement the v1.0 endpoint in the request, keeping the displayName filter but removing the resourceProvisioningOptions filter, then filter the request response using JavaScript to remove any groups that are not Teams.
https://github.com/pnp/cli-microsoft365/blob/1bae1ad9a62301470fee8ae38410df4c289205eb/src/m365/teams/commands/conversationmember/conversationmember-list.ts#L128-L134

Hi @garrytrinder, Can I work on this?

Absolutely, thank you @SmitaNachan its all yours 👍🏻


#732 reward TIPPED_ARROW

Tipped Arrow
Crafting a tipped arrow will be rewarded.
Technically, there's no recipe provided for a tipped arrow by Spigot API , so I had to make it work this way. There will be made no difference by different effects of the tipped arrow.
Lingering Potion
Brewing a lingering potion cannot be rewarded, because Jobs can only reward the ingredients.
Dragon's Breath already works fine, so you get rewarded when brewing lingering potions.

You would have to work on this to make it work properly. The following should be done:

We should create a new enum in which we put all the Arrow, Potion and Lingering effects so we can work with different effects, not all of them.
We should revisit the CRAFT action, in which we would put the effects as well as accept materials. but we do not do this, instead you can create a new Action in which we will include all the effects we want.
There is no need to deal with recipes, because we do not make unique materials.

That would be a lot of work to do. We used to start with Potion effects, but there was a problem with it and it was removed, it will be added later.
Unfortunately, hard and time consuming work is required to work properly. You can use the Minecraft Official Website to find the appropriate effects ID as well as names. https://minecraft.gamepedia.com/Arrow
If you can’t do it, then this PR will stay open until someone (or we) add it.

Okay right if we want to respect potion types, there will be a lot more to do.

I could create a new enum for all effects (Arrow, Potion and Lingering use the same effects).
For that rework of the CRAFT action: We could delegate the PotionType of that item to a new constructor for ItemActionInfo.
Then, I think there have to be changes made in the action method in Jobs,java, where the ActionInfo is passed to.
But could you give me a hint where in this huge method body the actual Material of the ActionInfo is evaluated? It might be the same place where we have to add a check for that potion.
Or more general: Where does the plugin match a Material to the specified action?

You don't have to do any changes to the Jobs#action method and with ItemActionInfo. Just you have to use this method:
Jobs.action(jPlayer, new ItemActionInfo(resultStack, ActionType.CRAFT));

resultStack is always be the crafted item when the player do that.
If you see job#getJobInfo(info, level) method you will see that the material/entity... stuffs are been translated by the TranslatableWords file.

Job#getJobInfo compares just names of material, but no ItemMeta. If we want to check e.g. a tipped_arrow + slowness, the item cannot simply be identified by it internal ID, because there are no sub-IDs for potion stuff, just NBT Tags (ItemMeta).
So you mean I have to make these changes in getJobInfo(action, level) by expanding it with a ItemMeta check? But then, an ActionInfo has to have a field for itemMeta or potion effect in order to compare it with the actual JobInfo, or shall it be represented as a subType?

So you mean I have to make these changes in getJobInfo(action, level) by expanding it with a ItemMeta check? But then, an ActionInfo has to have a field for itemMeta or potion effect in order to compare it with the actual JobInfo, or shall it be represented as a subType?

No, you have to put the ItemMeta checks in another static method (like Util) or making a new class, extending with BaseActionInfo in actions package to check the ItemMeta for effects.

Is there any progress on this?

Hey, I just continued working on it and saw that you already merged it. However, I've not been finished in that moment.
I just corrected most of Potion names.
And I've got an open question:
I didn't get to implement that correct translation for material with potions.
Example in jobConfig: TIPPED_ARROW-SLOWNESS
Works fine but in /jobs info the correct name doesn't show up - its just "None".
I think it shouldn't be much work. So because you already know how this works, could you do that translating thing?

I'm sorry I accepted soon. I just didn't think ahead. Open another PR.
I think /jobs info only displays the items that are in the CMIMaterial enum.


CLI does not close when pressing X to exit the dev CLI

Description:
When you're in the dev CLI, you're prompted to press X to close the dev server.
That does kill the containers, but it doesn't fully detach from the process.
Image (credit: @thesujai)

Steps to reproduce:

Ensure dev server is running via ./dev.sh
Wait for everything to start fully.
Once ready, press x.

Expected behavior:
All containers are killed ✅
Process detaches cleanly from the terminal ❌
Actual behavior:
As shared in the screenshot above, process does not detach cleanly from the terminal.

Whoever is picking this, the bug is because:
The useEffect(Which is suppose to close the process) is never triggered because the appState is not updating here. I checked with log statements, the appState before and after this dispatch() is same. So our exit() in the useEffect is never called

Hey @thesujai are you still working on this issue ?

No I am not.

Sure, @shamun-khatri. Feel free to give it a shot.

Hey @shamun-khatri, how's it going? Are you still working on this?
I'd be okay with reassigning this in case you're occupied with other things. :)

Should i give it a shot ?

Whoever is picking this, the bug is because:
The useEffect(Which is suppose to close the process) is never triggered because the appState is not updating here. I checked with log statements, the appState before and after this dispatch() is same. So our exit() in the useEffect is never called

@jayantbh Sorry for the delay I was not feeling well for a couple of days and also I got stuck on another work.
The comment by @thesujai that I am replying to is not the problem. I have tried debugging and find that Appstate is changing well. and it becomes terminated and also that useEffect hook is calling which leads to exit().
But then also it is not detached to the terminal.
I am looking for the solution but this comment might be useful if someone is looking at the wrong place.

Thanks for looking into that, @shamun-khatri. :)
Feel free to continue looking into this.
Same goes for @aadarsh-nagrath or anyone coming to this later.

I'm un-assigning this issue so anyone coming to this later may attempt a fix till we have one.

@jayantbh I have raised a pull request. please have a look at that.

I hope too, currently, that is working but in the future, if any problem persists. Will look on more depth into this.