Support POSIX glob syntax / pluggable pattern syntaxes

POSIX-style globbing is an extremely common syntax for most tools, so it would be nice to provide support for glob patterns where FilePatterns are currently used.
I think it would even be possible to add without breaking backwards-compatibility:
If you used the Glob library, you could replace current uses of FilePattern with a class:
class AsPattern p where
  (?==) :: p -> FilePath -> Bool

instance AsPattern FilePattern where
  (?==) = ... current definition ...

instance AsPattern Pattern where
  (?==) = System.FilePath.Glob.match

In any case, even if you didn't want to pull in the dependency on the Glob library, making it a class would be convenient because it would allow people to plug in their own pattern syntaxes.

Also, if you supported this, you could add a newtype Literal = Literal FilePath to only match against the precise same file, which would go nicely with #144 to not inflict the overhead of pattern matching when the exact filename is known.

In the cases where FilePattern is a literal, I already do very cheap matching on it (I even hash them in advance and store them in sets to make bulk matching very cheap). For the pluggable syntax, an alternative is just to define something on top of ?> (which I already use to implement %> anyway):
(%%>) :: String -> (FilePath -> Action ()) -> Action ()
(%%>) a b = match (compile a) ?> b
Now you can do globbing syntax with %%>. Is that enough, or can you think of cases where you want more?

My use-cases are more for the functions in the Action monad that use FilePattern.
removeFiles, trackAllow, and getDirectoryFiles are where I'd really love to have POSIX globbing (especially getDirectoryFiles!), and I don't think ?> really does anything on that front.

For removeFiles, you can just use the glob stuff directly with liftIO - there's no real "Action" stuff happening there.
For trackAllow, it's rare to use anything more than a directory, and rare to do anything at all yet (support for tracking on Linux is coming in the next version of Shake, but at the moment, trackAllow is mostly pointless).
For getDirectoryFiles there are lots of optimisations about scanning that are quite dependent on FilePattern. My guess is that it would be much better if you could just l lift globDir into a tracked Shake rule. At the moment you can write a Shake rule (just copy the existing getDirectoryFiles one), but it's not super-simple. I'm currently looking at how to make writing a new rule super-simple, and then that's probably the way to go.

OK, I'll give that a look. Thanks for the advice!


[suggestion] keybind to open ModSettings screen

hello, thank you for making this mod, it has quickly become a must-have :D
may i suggest adding a keybind to open modsettings ? many mods offer a keybind to open their respective configuration screens, but i find that incovenient because it requires way too many keybinds. Instead with modsettings, they could all be under one keybind x)

Good idea! I'll see what I can do. :)


fix: fix caddy v2.7.x runtime error: ResponseWriter doesn't implement…

… http.Flusher

1. What does this change do, exactly?
fix caddy v2.7.x runtime error: ResponseWriter doesn't implement http.Flusher by using ResponseController introduced in golang v1.20
2. Please link to the relevant issues.
https://github.com/klzgrad/naiveproxy/issues/575
https://github.com/caddyserver/forwardproxy/issues/107
3. Which documentation changes (if any) need to be made because of this PR?
None
4. Checklist

[x] I have written tests and verified that they fail without my change
[x] I made pull request as minimal and simple as possible. If change is not small or additional dependencies are required, I opened an issue to propose and discuss the design first
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code

5. PS
This PR does not fix an issue that caused the forwardproxy to not work when turning on the LOG directive in Caddyfile https://github.com/klzgrad/naiveproxy/issues/550#issuecomment-1683945230

@Chilledheart Can you test if this works?

@Chilledheart Can you test if this works?

No, it is not working.
I tested github.com, google.com and etc in some vm at seatle.
Below configuration is added.
  log {
    output file /var/log/caddy.log {
      roll_disabled
    }
    format console
    level  INFO
  }

"5. PS This PR does not" this PR is not for fix that log issue

Okay, then. I tested it without log option. It seems working now (both of google.com and github.com,  with naiveproxy in linux and shadowrocket in ios)

Built with go version go1.21.3 linux/amd64


Template Literals are Escaped

<template>
  <button
    :id="`my-dynamic-id-${id}`"
  >
    Text
  </button>
</template>

Is converted to
template: "<button\n      :id=\"`my-dynamic-id-".concat(id, "`\"\n    >\n      Text\n    </button>"

I'm pretty sure that .concat is coming from gulp-babel, but ` is coming from this

Could you not replace it with the following instead of using a template literal?:
  <button
    :id="'my-dynamic-id' + id"
  >
    Text
  </button>
</template>```

I'm open for suggestions if you have a better solution.

@nfplee That's what I'm doing as a workaround, but my company's style guide forbids that, also it gets a little bit more ugly as things get complicated :style="{'flex': '1 1 ' + sliderWidth + '%'}". Another workaround is to put it in a computed, but this is liable to cause issues when somebody else in our company adds to this repo not understanding that template literals are a problem
Is there a reason why template literals have to be escaped?

This should now be fixed. Please reopen and let me know any problems if it's still causing an issue. Thanks


Ono to one relations

Hi! Thanks for your script!
Can you please add one to one relations?
I changed your code a bit
$bindingKeys = $newValue;
if(!is_array($bindingKeys))
{
$bindingKeys = ['0' => $bindingKeys];
}
After I can use one to one relations, but always when you update your script and I do composer update I losing it. Maybe you can just add it into your code, please?

Of course!
But I need a real life example to understand the situation and what kind of data you are working.
I ask you to make a pull request, and send it for review.

Thanks for your quick answer!
                <?=$form->field($user, "hobbies")->widget(Select2::classname(),[
                    'hideSearch' => true,
                    'value' => '', // initial value
                    'data'=>ArrayHelper::map(Hobbies::find()->all(), 'id', 'name_ru'),
                    'showToggleAll' => false,
                    'options' => [
                                    'placeholder' => 'Select...',
                                    'multiple' => true,
                                    //'class' => 'form-group',
                                ],
                    'pluginOptions' => [
                        'allowClear' => true,
                    ],
                ])->label('Hobby'); ?>

If I change 'multiple' => true, to 'multiple' => false I need to select only one value from the list your script shows me error Invalid argument supplied for foreach()
foreach ($bindingKeys as $relatedPk) {
That is why I added this code
$bindingKeys = $newValue;
if(!is_array($bindingKeys))
{
$bindingKeys = ['0' => $bindingKeys];
And after I can use it without any error messages

The behavior is expecting either an array of ids or no attribute value at all. All other kinds of input need to be transformed into this internal representation using custom getters and setters.
There is no need to update the behavior itself, implement your logic in getters/setters.


[BUG] Cannot do a Helm upgrade after PR 2763

Describe the bug
It looks like the original plan for https://github.com/longhorn/longhorn/issues/7571 included modifying the Helm pre-upgrade check. Later, https://github.com/longhorn/longhorn-manager/pull/2763 moved the check to the node controller, but accidentally (I think) retained the environment check in app/pre_upgrade.go. This check doesn't work without the closed https://github.com/longhorn/longhorn/pull/8463, so Helm upgrades currently fail with the following message:
time="2024-07-10T20:24:53Z" level=info msg="Checking if the engine upgrade path from map[ei-b907910b:{Version: GitCommit: BuildDate: CLIAPIVersion:10 CLIAPIMinVersion:0 ControllerAPIVersion:5 ControllerAPIMinVersion:0 DataFormatVersion:0 DataFormatMinVersion:0}] is supported" func=util.checkEngineUpgradePath file="util.go:318" newEngineClientAPIMinVersion=8 newEngineClientAPIVersion=10 newEngineControllerAPIMinVersion=4 newEngineControllerAPIVersion=5
time="2024-07-10T20:24:53Z" level=fatal msg="Failed to run pre-upgrade" func=main.main.PreUpgradeCmd.func5 file="pre_upgrade.go:36" error="failed to check environment, please make sure you have iscsiadm/open-iscsi installed on the host: open /host/proc: no such file or directory"

To Reproduce
Try to run helm upgrade -n longhorn-system longhorn ./chart.
Expected behavior
The upgrade succeeds.
Additional context
cc @mantissahz

https://github.com/longhorn/longhorn-manager/pull/2763 does

check environment while starting daemon
check environment while pre-upgrade
periodically check environment and update to conditions

We should merge https://github.com/longhorn/longhorn/pull/8463 for the second check. Isn't it? @mantissahz

We should merge https://github.com/longhorn/longhorn/pull/8463 for the second check. Isn't it? Accidentally closed? @mantissahz

Yes, I forgot that checking the iscsi iscsiadm/open-iscsi installed will use the shell command.
We

Update:
Tested the PR https://github.com/longhorn/longhorn/pull/8463, and it works to update Longhorn from 1.6.2 to 1.7.0-dev

Verified on master-head 20240711

longhorn master-head https://github.com/longhorn/longhorn/commit/40b4207c14fe95a6fc084c8600e90e7a9d947620

The test steps
https://github.com/longhorn/longhorn/issues/8974#issuecomment-2221421404
Result Passed

[x] Successfully installed Longhorn.
[x] Successfully created workloads, volumes, snapshots, backups, and system backup.
[x] Successfully upgraded Longhorn from version 1.6.2 to master-head.


Copyright dates need to be updated in src/parsley.js

https://github.com/guillaumepotier/Parsley.js/blob/master/src/parsley.js#L3
20012-2014 -> 2012-2015

Thanks, but there's actually no really compelling reason to change a copyright date. See http://stackoverflow.com/questions/2390230/do-copyright-dates-need-to-be-updated

First date incorect (20012).

Oh, that's good to fix :smile:
Done. Thanks :+1:

Forgot to add a src/parsley.js (line 3).

Indeed, and that's the one that matter. Fixed for good now. Thanks!


Typo in 1.16 Release Blog Post

This PR fixes a missing no to correct "are longer serving the deprecated APIs."

/assign @onlydole

/lgtm

/assign @castrojo

/assign @kbarnard10

Definitely /lgtm

/approve

/approve
No idea why this didn't merge yet, let's see if this retriggers it.


Update docs for v 1.0.0 and Scala 3

Hi,
Just tried to get started, using Scala 3 JS, and found this page: https://japgolly.github.io/scalacss/book/quickstart/index.html
This didn't work with some cryptic errors about conflicting cross-version suffixes.
I figure it's because the quick start uses 0.8.0-RC1, and 0.8.0-RC1 does not support Scala 3. I tried with version 1.0.0 and it seems OK.
Page needs updating?

On the topic, the quickstart is not working for me (the 12 px syntax). Should this be working?


Keyboard backlights can't be turned off

Hi and thanks for the tool!
I have one minor nitpick, and that is that the line
https://github.com/RPigott/blight/blob/154ae0baeadeb24605e0e6d43bb00c7c9fee8e52/blight.py#L65
seems to also affect the keyboard backlighting, so blight can't be used to turn off the keyboard backlights.
On a side note, where do these values come from? On my W530 I do have a brightness level way over 100, but 0 is still a valid level (and does not turn off my screen either).

Hey @Gigadoc2, glad you like it.
And yeah that could probably be changed. I guess it should probably only care about a minimum value for backlight devices, not leds.

where do these values come from?

I stole them from GNOME: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/master/plugins/power/gsd-backlight.c#L237. It's kinda hard to come up with good defaults on your own since there doesn't appear to be any common convention between devices on the meaning of the raw brightness values.

I see, yes the situation is somewhat problematic :D
While I don't know about other hardware, on mine 0 and 1 make no real visual difference, so I am fine either way :)
BTW, I just realized that my keyboard backlight has a max_brightness of 2, so it seems that it is not of type raw then?

Yeah the type only matters for backlight devices, not leds.


menu button not working on Alert

when the Alert.alert() show then the menu button is not working.
i want if user wants to dismiss the alert with menu button so what is the workaround ?

it is working when you add a prop style:cancel
for example :
Alert.alert(
alertTitle,
alertText,
[{
text: button,
onPress: () => handle(),
style: 'cancel'
}],
);


Is there a way to center specific columns

Vue.js version: 1.0.28
consumed using: browserify

Is there a way to center specific columns, I can't see anything obvious that would allow me to do it. Using templates maybe?

How about
tr td:nth-child(x) {
 text-align:center
}


docs: distributions: Fedora

Improve documentation on the Fedora caveat with FirewallD. Add a link from README.md.
Addresses a part of https://github.com/coreos/rkt/issues/2202
@joshix PTAL

@alban Suggestions inline

"needs/review" is just the weirdest tag. Is that upstream at k8s as well?

@joshix Thanks for the review! I updated the PR based on your suggestions. PTAL

lgtm


Fix #5 and #7: Update cmdparser.hpp to fix a few issues

Update cmdparser.hpp to fix:

Properly parsing std::vectorstd::string (crashed due to default initializing a std::string to 0)
Ensuring the default argument consumes leftover variadic arguments at the beginning, middle, and end of the line
Ensuring that dominant arguments (like help) will appear even if required arguments are missing

Looks great, thanks for the PR!


feat(CI): check external types

This adds CI job that runs cargo-check-external-types against a whitelist of exported types.
Whitelist in https://github.com/hyperium/hyper/issues/2925#issuecomment-1362473727 didn't change.
For now the nightly for this needs to be pinned to nightly-2022-11-16, because cargo-check-external-types doesn't work with the latest nightly json doc format.
Resolves #2925
Superseeds #2957

I'm unsure why it cannot find the nightly version. I created an upstream issue: https://github.com/dtolnay/rust-toolchain/issues/76


GitOps for shared installations/organizations

As a user on a shared installation (only having access to one organization) I'd like to use a GitOps workflow. Access the management API via OIDC, Hook up my git repository, create my clusters, configure OIDC, create users and roles and install applications on top of the clusters.
As a user in a big organization I'd like to create an organization for another platform team. The platform team wants to use GitOps for their own clusters and organizations.
Questions:

[x] Is access to the management API already possible on shared environments?
[x] Can a user on a shared environment create additional roles and bindings with less permissions?
[x] Can a user add a git repository for flux and manage the organization via GitOps?

Any docs would be nice.

cc @MarcelMue @giantswarm/team-rainbow

Notes from Honeybadger brainstorming session
Topic of GitOps for shared installations/organizations
  - Should be possible
  - RBAC is sorted for customers using orgs only
  - We create clusters right now by using the default namespace which is “admin” permission
    - Uncertain if there is any requirement for this or if a full cluster could be created in the org namespace

Essentially the customer would need to be a manegement cluster user (not admin) and would therefor have RBAC limited access to an organization. Flux is already set up for customers in a way that escaping from the org namespace should be impossible. So they can just create a kustomization in the org namespace which references the automation service account in the org namespace.
The major questions would be if cluster creation in only the org namespace is completely possible (should be, but we did not do it that way so far - e.g. account info shared between orgs is in the default namespace).
Confidence is relatively high but trying this out would be a "test" of our RBAC setup.

Showed off first implementation of the concept. Now setting up more PoC environment with collaborative access.

This issue is fully implemented from my current knowledge. I am still trying this out with a customer and will close it, once I have more certainty that it's completely done. There is no work being done here other than direct customer work currently.

@MarcelMue regarding this, is there any documentation ? do you see any knowledge handover to honeybadger about possible future product adaptations you envision? is there something you want to bring up in WG GitOps UX today given that this is now done (as per your comment above)?

@MarcelMue can we close this?

Please leave it open for now, I can keep it on my personal board only if you want.

@MarcelMue do you see this impacting the team at some point or not?

There will be some docs to review.

closing this, as there are no open tasks


Repair the price tolerance feature

I don't think the price tolerance field is wired up to the form. When I change it and blur the input, I expect the "Min received" to change. That's what it does in the OUSD dapp.

Fixed and deployed


make log error more explicit about actions to take

@zdhickman @jhaber @markhazlewood
Until we're automatically re-trying tasks that are getting lost in singularity we should have a better message here so users know what to do. So far I've only see this error come up when a slave has a hung docker daemon.

:sake:


Checkpoint actions don't need to be tracked in the log replay hashmap

Currently, we don't distinguish between actions that came from deltas vs. checkpoint, which bloats the hash table used to track and deduplicate versions in file_stream.rs.
We need the hash table to track actions from deltas, that we've already seen and which may have older versions in older deltas and/or checkpoint... but checkpoint actions are already "oldest" and so we don't need to track them.

This appears to have been solved some time ago by the introduction of the is_log_batch parameter in the input stream.

yup - thanks for the cleanup!


Handle scope validation tests

Fixes #121

Add unit tests for handle scope validations, using a mocked runtime so that the tests can run without libnode. [1]

Test rules for nesting different types of value scopes.
Test attempts to access values from disposed scope or from different thread.
Test attempts to access references from a different thread.
The checks should also cover attempts to access values/references from a disposed environment because they rely on the thread-local current scope that will be null (or different) after the environment root scope is closed. There are no explicit tests for this though.

Refactor and fix handle checks in JSValue, JSValueScope, and JSReference to pass the tests.
When making API calls related to a JSValue instance, always use the value's Scope member rather than the thread-local "current" scope. This allows for validation that the current and target environments (threads) are the same.
Add new exception types JSValueScopeClosedException (subclass of ObjectDisposedException) and JSInvalidScopeException (subclass of InvalidOperationException) to provide detailed error info when a handle scope problem is detected.
Pass a GC handle to the JSRuntimeContext via the hint parameter of all finalizers (which required some minor refactoring where the hint was used for other things). Previously the finalizers were getting the context via the thread-local scope, which caused errors when finalizers ran after the root scope was closed. Also the finalizers were calling napi_get_instance_data (many times) which should be avoided. Finalizers now do not make any JS calls and do not rely on any thread-statics.
Fix a similar issue with JSReference.Dispose(), to handle disposing references after the root scope was closed.
Fix a bug in generator tool response file parsing of an empty quoted value (""). This broke builds targeting .NET 4 where the --packs argument value is empty. (I don't know how this passed testing before.)

I compared benchmark results before and after the changes - there was no measurable impact from the additional validations.
[1] Currently I get a crash when trying to create more than one "environment" using the new embedding APIs. I will check whether that is fixed in a newer revision of that PR; I'm using a build of libnode from a much older PR revision.

I am concerned that PR removes all safety checks from JSValue.
After this change the Handle is never checked which will cause a lot of security risks of accessing released memory.
Am I reading this change wrong?

I am concerned that PR removes all safety checks from JSValue. After this change the Handle is never checked which will cause a lot of security risks of accessing released memory. Am I reading this change wrong?

The checks are not removed, but moved to the JSValueScope to napi_env conversion. We could have them in both places but I thought that was redundant since you have to get a napi_env to do anything with a handle. I can explain in more detail when I have time later.

I am concerned that PR removes all safety checks from JSValue. After this change the Handle is never checked which will cause a lot of security risks of accessing released memory. Am I reading this change wrong?

The checks are not removed, but moved to the JSValueScope to napi_env conversion. We could have them in both places but I thought that was redundant since you have to get a napi_env to do anything with a handle. I can explain in more detail when I have time later.

The main goal of JSValue is to safely wrap napi_value. Replacing it for the napi_env check from JSValueContext is not equivalent. For the functions that use a single napi_value, I agree, there is no difference. But if a function uses two or more napi_value, then we effectively check only one of them, while others are used unchecked. It is dangerous if these values are from different scopes.
If we want to get rid of redundant napi_value/napi_env checks, then we should rather avoid checking for napi_env because it will be covered by napi_value check, but not the other way around.

if a function uses two or more napi_value

Yes, that is a good point about additional napi_value args.

If we want to get rid of redundant napi_value/napi_env checks, then we should rather avoid checking for napi_env because it will be covered by napi_value check, but not the other way around.

For static functions that take only a napi_env and no value handles we still have to validate the thread access to the env via the current scope.
So we'll check in both places, and it will a little redundant sometimes, but it is only a boolean plus an nint comparison so it's not a big cost. From benchmarks of scenarios that have heavy interaction with handles, it looks like maybe 1-2% performance difference, though the benchmarks don't quite have that level of precision. Regardless I think is worth it for the added safety.
I suppose we could add a JSValueScope.UncheckedEnv handle property that could be used when we know the scope is already being checked via the value, but it's probably not worth the code complexity / risk of bugs.

In the update I also added consistent public Handle and EnvironmentHandle properties; the (napi_value), (napi_env), and (napi_ref) operators now just call those. That follows framework API design guidelines that any operators should have non-operator equivalent properties or methods. And I added an internal UncheckedEnvironmentHandle property that can be used to bypass redundant checks when the scope / env handle will already be checked via value handle access in the same call.

        throw new InvalidOperationException("Parent scope must not be null.");

Should we use the JSInvalidScopeException in this function?

Refers to: src/NodeApi/JSValueScope.cs:390 in c4cc578. [](commit_id = c4cc57839df8677a81095bb955b04a7cf391e04a, deletion_comment = False)

        throw new InvalidOperationException("Parent scope must not be null.");

Should we use the JSInvalidScopeException in this function?

JSInvalidScopeException was renamed to JSThreadAccessException at your suggestion. So then it didn't make sense to use for the parent scope checks here because they are not about threading. (JSInvalidScopeException.cs was mistakenly still included in the dif.)


Have GF back on the Title Screen if an easter egg is activated

Basically this allows people to have gf back on the title screen instead of it being stuck as pessy or shadow mario or whoever by just typing "gf" however in case some people do want to see someone like pessy every time they open the game they are still able to do that.

You can go back to gf by typing the same name again. So if you typed "pessy" you can type it again to put gf back on the title screen.

You can go back to gf by typing the same name again. So if you typed "pessy" you can type it again to put gf back on the title screen.


Automatically get new published datasets

It would be nice if the downloading tool (fzo store download) could automatically detect new datasets (either datasets published after a given date, or datasets that are not already present in the local store) and offer to download them all at once.
Something like fzo store download --all-new or fzo-store download --since=YYYY-MM-DD.

Full list of experiments is available as a JSON table here: https://wwwdev.ebi.ac.uk/gxa/sc/json/experiments


CORGI-65 - Task and collector for pyxis manifests

For https://issues.redhat.com/browse/CORGI-65

very cool - we will review (and fix reason why CI did not run for your PR!).

Thanks Ralph! Looks like all the pieces are there well done. We will review it more detail in the coming days.

Thanks guys. Maybe CI failed because this was submitted from my fork? (Untrusted!)

Thanks guys. Maybe CI failed because this was submitted from my fork? (Untrusted!)

yes that will be it ;)

I have a mypy error that I'm struggling to understand:
corgi/collectors/pyxis.py:127: error: Argument "cert" to "post" of "Session" has incompatible type "Tuple[Optional[str], Optional[str]]"; expected "Optional[Union[str, Tuple[str, str]]]"  [arg-type]

Squashed, rebased on main, and signed my commit.

@ralphbean Can you please resolve the merge conflict with corgi/monitor/consumer.py so I can merge?

@jasinner rebased and resolved!


Long post titles may overlap with nav bar

Can I take this issue ?

Can I take this issue ?

Please choose only one issue at a time. Just leave a comment to let us know
which one, and let us know if you stop working on it later.
On Mon, Jan 25, 2021, 7:22 PM Abhay Singh Yadav<EMAIL_ADDRESS>wrote:

Can I take this issue ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WikiEducationFoundation/WikiEduWebsite2015/issues/15#issuecomment-767262913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGPEY5WHAHFVVMHA2R5CNTS3YYO3ANCNFSM4BKBEPDA
.

Please choose only one issue at a time. Just leave a comment to let us know
which one, and let us know if you stop working on it later.
On Mon, Jan 25, 2021, 7:22 PM Abhay Singh Yadav<EMAIL_ADDRESS>wrote:

Can I take this issue ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WikiEducationFoundation/WikiEduWebsite2015/issues/15#issuecomment-767262913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGPEY5WHAHFVVMHA2R5CNTS3YYO3ANCNFSM4BKBEPDA
.

Okay, I want to work on this issue.

Okay, I want to work on this issue.

By following README file can I run it on my local machine?

By following README file can I run it on my local machine?

Yes, you should be able to. This is a wordpress theme, so you'll need to install wordpress, then install and activate this theme, in order to replicate the issue. The readme should be correct in broad strokes, but may be out of date in terms of the JS build tools.

Yes, you should be able to. This is a wordpress theme, so you'll need to install wordpress, then install and activate this theme, in order to replicate the issue. The readme should be correct in broad strokes, but may be out of date in terms of the JS build tools.


ControlNet support

The ControlNet extension improves the control over the composition by a lot. I would imagine it being a worthwhile addition.
Additional context
Currently the extension even throws errors when working in Krita:
Error running process: stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py
Traceback (most recent call last):
  File "stable-diffusion-webui/modules/scripts.py", line 386, in process
    script.process(p, *script_args)
  File "stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 390, in process
    enabled, module, model, weight, image, scribble_mode, \
ValueError: not enough values to unpack (expected 13, got 0)

It would be very useful! :)
Here is the link to it:
https://github.com/Mikubill/sd-webui-controlnet

Maybe useful, "added an API layer":
https://github.com/Mikubill/sd-webui-controlnet/pull/194

The ControlNet extension improves the control over the composition by a lot. I would imagine it being a worthwhile addition.
Additional context Currently the extension even throws errors when working in Krita:
Error running process: stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py
Traceback (most recent call last):
  File "stable-diffusion-webui/modules/scripts.py", line 386, in process
    script.process(p, *script_args)
  File "stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 390, in process
    enabled, module, model, weight, image, scribble_mode, \
ValueError: not enough values to unpack (expected 13, got 0)

This is more an issue of controlnet than the plugin, seems the controlnet is interfering even when disabled.
Regarding it's support, yeah it would be amazing. I'm back to 2 A111 because of it. I've bind every folder with models so it's just the setting and the extensions, it's not a big deal. Controlnet is the best improvement since local fine tuning.

Seems complex enough that I can't just guess what is going wrong, I may take a look at it if I have time.

This excellent free and open source photoshop plugin just had a new update with controlnet, maybe the code of this plugin can help the one here for krita :
https://www.reddit.com/r/StableDiffusion/comments/11iuqhv/major_update_automatic1111_photoshop_stable/
https://github.com/AbdullahAlfaraj/Auto-Photoshop-StableDiffusion-Plugin

I see, maybe I will look at it when my internship is over.

i tried to implement controlnet to auto-sd and use it in krita but apparently i'm too stupid for that. if you could describe how you did it i would be eternally grateful.

i tried to implement controlnet to auto-sd and use it in krita but apparently i'm too stupid for that. if you could describe how you did it i would be eternally grateful.

I haven't done it yet, I'm still working on the UI but I've got some approaches in mind. If it turns great then I'll share it.

the deforum plugin has good controlnet support plus a lot of other features (especially powerful for image-to-image animation). if getting controlnet support added is going to require onboarding another plugin, might get more bang for your buck integrating deforum. no idea if there's a difference in LOE between adding support for just controlnet vs. deforum. maybe if we reach out to the gradio team, they could come up with some more generic support between gradio applications and krita?

the gradio team would probably not do that...


remove "record variable"

and remove duplicate section

This PR is replacing https://github.com/mulesoft/docs-mule-runtime/pull/721, which was approved by Ana.


Typechecker has missed a type error

I have accidentally introduced a type error in the variable declaration:
// it should be:
// var erc20State: Erc20State
var erc20State: erc20State

https://github.com/informalsystems/quint/blob/56abbcd46437c8b515b7c7b50e4dc1b899da61ab/examples/solidity/ERC20/erc20.qnt#L244-L257
The type checker did not detect a problem in the variable declaration. Moreover, I had a type error in the following action:
https://github.com/informalsystems/quint/blob/56abbcd46437c8b515b7c7b50e4dc1b899da61ab/examples/solidity/ERC20/erc20.qnt#L253-L257
We should figure out, what is going on with the type checker.

I understand the problem! Our language manual specifyies:

Uninterpreted type or type name: IDENTIFIER_IN_CAPS.
Type variable (parameter): a, ..., z.

So erc20State here is parsed as a (quantified) type variable.
This is actually a language design problem 😅 Should we prevent state variables to have quantified type variables at all? @konnov

Ok! I'll change the issue name to reflect the specifics of what the type checker misses.

I'll also add this check to constants as we discussed at some point during the quint meeting.

As a special case of this we should not allow declaration of these to include free row variables. This is currently accepted:
    var rec1: { f1: int, f2: str | r1 }
    var rec2: { f2: str, f3: bool | r2 }

This is related to #456 and can probably be fixed at the same time. It is another case where we are allowing type annotations for things that cannot be values (nothing can have type 'a since we don't have a bottom or non-termination).


Hw2

Hi, Jenn and Kelvn week 2 homework is ready for review. Thank you!

Excellent job! This is approved for merge! You can see your feedback on the doc.

Really nice work setting up this repository, your feedback is ready in the document!


[SPARK-49080][SQL][TEST] Upgrade mssql-jdbc to 12.8.0.jre11

What changes were proposed in this pull request?

This PR aims to upgrade mssql-jdbc to 12.8.0.jre11.
Why are the changes needed?

This is the latest stable version of mssql-jdbc,  related release notes:
https://github.com/microsoft/mssql-jdbc/releases/tag/v12.7.0
https://github.com/microsoft/mssql-jdbc/releases/tag/v12.7.1
https://github.com/microsoft/mssql-jdbc/releases/tag/v12.8.0
Some fixed issues:

Fix to ensure metadata returned follows JDBC data type specs https://github.com/microsoft/mssql-jdbc/pull/2326
Added token cache map to fix use of unintended auth token for subsequent connections https://github.com/microsoft/mssql-jdbc/pull/2341
Clear prepared statement handle before reconnect https://github.com/microsoft/mssql-jdbc/pull/2364
Reset socketTimeout to original value after a successful connection open https://github.com/microsoft/mssql-jdbc/pull/2355
Clear prepared statement cache when resetting statement pool connection https://github.com/microsoft/mssql-jdbc/pull/2361
Fixed ClassLoader leak of ActivityCorrelator ThreadLocal https://github.com/microsoft/mssql-jdbc/pull/2366

Does this PR introduce any user-facing change?

No.
How was this patch tested?

Pass GA.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @LuciferYang

Can we also update MsSQLServer to 2022-CU14-ubuntu-22.04？

Can we also update MsSQLServer to 2022-CU14-ubuntu-22.04？

No problem, let me work on this.

If you don't mind, we can also switch the docker registry from mcr to https://hub.docker.com/r/microsoft/mssql-server directly

If you don't mind, we can also switch the docker registry from mcr to https://hub.docker.com/r/microsoft/mssql-server directly

Is this the part? mcr.microsoft.com/mssql/server
But it seems that this is already the link you gave https://hub.docker.com/r/microsoft/mssql-server? Or am I not getting what you mean?
https://github.com/apache/spark/blob/080e7eb0de06d49959f2f2b05a1f446adf12fadb/connector/docker-integration-tests/src/test/scala/org/apache/spark/sql/jdbc/v2/MsSqlServerNamespaceSuite.scala#L32

You are right, I made a mistake


Profile Picture

Profile Picture is not showing after registration.

harsh i did not understand what it is actually about i just started learning Django

I saw this issue. the thing is there is 2 users data db 1 one which is created by own django admin panel. 2. You have created profile model. after registering data is going to by default admin panel not in profile. so first we have to enter data in profile model and after that we have to show it on screen. and in front end after registering user have to upload image in profile section which will shown on profile section of user later and if user is not have uploaded any profile image so we have to show bydefault blank profile image. hope you got it or assign this one it to me I can do that. @harsh-9in

yes @nooras  you can work on this issue.


[icu] fix mingw builds

Describe the pull request

What does your PR fix?
Fixes  #16663

Which triplets are supported/not supported? Have you updated the CI baseline?
All, no

Does your PR follow the maintainer guide?

Yes

Can you remove the first commit from this PR? I believe you might have mistakenly added it here.
Also, please update the version file.

It was taken from https://github.com/unicode-org/icu/pull/1733

It was taken from unicode-org/icu#1733

So lets wait for unicode-org/icu#1733 merge.

Closing in favor of https://github.com/microsoft/vcpkg/pull/20253.


[qt5-base] Remove excess dependency icu[tools]

Fix #29463

There is no conflict. I would prefer if this isn't merged with a misleading message.

Title has changed.

Thanks for your contribution 🌷
There is a deprecated function, would you like to change it?
vcpkg_copy_tool_dependencies -> vcpkg_copy_tools

Thanks for your contribution 🌷
There is a deprecated function, would you like to change it? vcpkg_copy_tool_dependencies -> vcpkg_copy_tools

No. Sorry for that. Qt contains many tools, and all tool names must be listed accurately.
It's a dirty job and you have to be very careful to make sure you don't make mistakes

No. Sorry for that. Qt contains many tools, and all tool names must be listed accurately.
It's a dirty job and you have to be very careful to make sure you don't make mistakes

Understood, thanks for your reply.

@MonicaLiu0311 Did you forget to add reviewed tag?


General mechanism explanation documentation

The Liquidity module has common/different characteristics with the Uniswap model.
For version 1, belows are common/different characteristics
Common
Liquidity pool with two reserve tokens
Permissionless liquidity pool creation
Constant product equation utilization
Difference
Expandable types of liquidity pools in future (such as curve.finance style with 2+ reserve tokens)
Batch swap execution (possibly one batch execution for multiple blocks)
Universal swap execution price in one batch
Self swap and pool swap matching types
The detail explanation of the mechanism of liquidity module will be written down in readable format
so that anyone in the community including Tendermint team can understand and verify the suggested mechanism.
I expect writing will be done by 2020.10.16
Writing will be updated here : https://github.com/tendermint/liquidity/blob/develop/doc/Liquidity-Module-Mechanism-Explained.MD

Working draft documentation here : https://docs.google.com/document/d/1vy0k_X7bE8HHJZU0kx8etpA_axRCBJvpe8gmOFsRrSs/edit?usp=sharing

Replace to lightpaper

Replace to lightpaper


[Hybrid] Add <Link /> component to SDK - SDK approach

GUS: https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00000t0GJqYAM/view
Related PRs:

https://github.com/SalesforceCommerceCloud/pwa-kit/pull/478
https://github.com/SalesforceCommerceCloud/pwa-kit/pull/468

Description

Problem
We want to reduce the number of manual steps to implementing Hybrid in the PWA.
Solution SDK approach
This PR adds a minimal <Link /> component to the SDK that will help hybrid projects to automate routable links pointing to the PWA and non-routable links pointing to the external origin.
The <Link /> component matches the to prop URL with the paths defined in routes.jsx file.

If the URL doesn't match returns an anchor element. The link will be resolved by eCDN, and thus it's possible to point it to the external origin.
If it matches returns a react-router Link component with a relative URL. The PWA react-router will resolve the link.

The <Link /> component props:

to: path for the link. The value can be an absolute URL or a relative URL.

Result
Reduced manual work

Users will need to use the SDK Link component in their PWA.
Users will need to remove the routes that they don't want to be resolved by PWA from routes.jsx file.
(Optional) All URLs not matching the PWA routes will point to eCDN. Update eCDN rules to point the URL to the appropriate external original URL.

For example, imagine we want to use the Cart page from SFRA, and in the PWA, we have multiple links pointing to the PWA Cart page /cart.

We assume we’re using the SDK <Link /> component in the PWA.
We remove the path /cart from routes.jsx file.
Now all the links example-domain.com/cart point outside the PWA to eCDN by using an anchor link in the PWA.
(Optional) Update eCDN rule, point example-domain.com/cart to example-domain.com/s/RefArch/cart?lang=en_US

TODO

[ ] Extend Link to use {Link as RouterLink} OR {NavLink as RouterNavLink} from react-router
[ ] Use a RegExp to match the wildcard path.
[ ] Cover all the absolute/relative URLs potential combinations.

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

Extracted matchPath to a SDK util called matchRoute.
Added Link component to the SDK.
Use SDK Link component in the PWA Link component.

How to Test-Drive This PR

Checkout this branch hybrid-sdk-link-component
Run npm ci
Run npm run start --prefix packages/pwa

Verify:

Internal links work as expected by navigating through the App.

Links that have a path that doesn't match a PWA route, point to the external origin.
Navigate to the PDP and click the "Show full details" link below the photo gallery.

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

Closing since it was a POC for a PWA Hybrid spike.


minor: Make Leviathan work with different balenaCloud environments

To improve short-term reliablity, Leviathan will be working with a seperate balenaMachine. Changes include:

Client improvements to use balena API URL from the config.js

Signed-off-by: Vipul Gupta (@vipulgupta2048) <EMAIL_ADDRESS>

lgtm


Update language IDs as per Golang loc framework

Localization pipeline and PR creation by loc pipeline has been setup so closing this experimental PR.


Build df9d82e1-2846-4694-8a4d-03442bb4fd42: FAILURE

[avocano] df9d82e1-2846-4694-8a4d-03442bb4fd42 status: FAILURE
View Logs
I'm an automation. Googlers: go/avocano-admin-notifiers

Nightly build, same error as #45


Add Terminal Reset Helper

This came out of the issue filed over at dialoguer: https://github.com/console-rs/dialoguer/issues/294
The TLDR is that when the application terminates in unexpected ways (or really just ctrl+c) it's pretty easy for the terminal to be left in an unfortunate state. While there might be ways in which APIs can be restructured to cause this less, this is generally quite unfortunate and too easy to cause.
It also will in most cases require either using raw inputs to ensure that ctrl+c is manually handled on all inputs to reset the terminal state locally or (more correctly) to handle cltr+c globally. The latter however requires the user to be involved here as there can really only be one handler via the ctrlc crate or similar.
As a strawman proposal I'm considering adding a helper that people can put into their own ctrlc handlers which resets the terminal back to the state it was in when the application was started.
fn main() {
    let state = console::capture_terminal_state();
    ctrlc::set_handler(move || {
        state.restore();
        // ...
    });
    // stuff happens here
}

What's kind of ironic here is that the actual terminal settings are usually already properly reset, what's not reset is the cursor which is not in the terminal state that is manipulated via normal operations. Instead the cursor is hidden and shown via ANSI codes and there is no reasonable way to query the state of that.
So in a way what would need to be done is to carefully manage the cursor state within console/dialoguer independently. I'm really not sure what the most reasonable approach is here.


Why is there no validation in the release method of RedissonSemaphore, and instead it directly performs an incr action?

public RFuture<Void> releaseAsync(int permits) {
    if (permits < 0) {
        throw new IllegalArgumentException("Permits amount can't be negative");
    }
    if (permits == 0) {
        return new CompletableFutureWrapper<>((Void) null);
    }

    RFuture<Void> future = commandExecutor.syncedEval(getRawName(), StringCodec.INSTANCE, RedisCommands.EVAL_VOID,
            "local value = redis.call('incrby', KEYS[1], ARGV[1]); " +
                    "redis.call('publish', KEYS[2], value); ",
            Arrays.asList(getRawName(), getChannelName()), permits);
    if (log.isDebugEnabled()) {
        future.thenAccept(o -> {
            log.debug("released, permits: {}, name: {}", permits, getName());
        });
    }
    return future;
}

Here is the code for the release() method in version 3.21.0. There is no check to see if the key exists, and there is no check to see how many permits the semaphore can release. It simply performs an incr action. If another client performs a duplicate release() operation, it will release many permits that should not have been released.

This is how JDK implementation works. It's expected behaviour.


Typescript / Angularfire2 / Angular 2

How implement this with Typescript / Angularfire2 / Angular 2 ??

firebase-search is a Node.js module. It won't do any good on the browser with Angular. But you can definitely use it with TypeScript in Node. It's a vanilla module.


Resize Observer API docs tasks for Fx68

See https://trello.com/c/ez5jtSt5/134-resize-observer-api-fx-68 for the original trello card.
Acceptance criteria

[ ] Landing page created for Resize observer API

[ ] Basic "Using..." tutorial published

[ ] ResizeObserver ref docs cleaned up as needed, examples added, etc.

[ ] Update ResizeObserver API to match the up-to-date spec — documented appropriately

[ ] Implement Resize Observer API — documented appropriately

[ ] Hacks post written about Resize Observer

This is behind a pref in Firefox 68, not enabled till 69.
However, it is supported in Chrome since 64, so worth documenting.

Worth noting that Joe Medley has already written a lot of this material. It should be given a quick once-over while putting htis together but should help speed things up.

I'll start working on this today.

I'm adding it to Experimental features for now; we'll add it to the 69 release doc plan.

I've also created a quick outline at the main overview page location for the API, just to serve as a jumping-to point.

Resize observer docs finished — see https://github.com/mdn/sprints/issues/1905#issuecomment-526296951


Optimize mesh generation by preventing unneeded shape recalculations

Currently whenever a value of a PrimitiveMesh is set in GDScript it will completely regenerate the entire mesh. This is fine in most cases, but in the case that the set variable is the same as the current variable (p_radius == radius), there's no need to regenerate the mesh. In some cases we could get a big performance boost by just returning the function if the set variable is the same as the current one.
This PR fixes #99414

This should be ready to merge!

Thanks! Congratulations on your first merged contribution! 🎉

Fantastic work, @carsonetb
I was surprised to read on your profile that you're a middle schooler.  Your communication on the original issue and here, use of git, PR naming, is all excellent.  Keep it up; you're going to go far!

Congrats @carsonetb! :)


Add Chinese version of Chapter 1-7

Please also refer to the updates here https://github.com/intel-analytics/bigdl-llm-tutorial/pull/35 :)

could you please resolve the conflict and then I'll merge it quickly.


Create dataset loader for SEA Wikipedia

Dataloader name: sea_wiki/sea_wiki.py
DataCatalogue: https://seacrowd.github.io/seacrowd-catalogue/card.html?SEA Wikipedia

Dataset
sea_wiki

Description
SEA Lang & Local Langs Wikipedia Archives, dumped from WIkipedia HF and processed by boilerplate removal. This dataset consists of URL of referred Wikipedia Article, its Title, and its Text Data (Article Contents).

Subsets
ace, ban, bcl, bjn, bug, cbk_zam, gor, id, ilo, jv, km, lo, mad, map_bms, min, mnw, ms, nia, pag, pam, shn, su, tet, th, tl, vi, war

Languages
ace, ban, bcl, bjn, bug, cbk, gor, ilo, ind, jav, khm, lao, mad, min, mnw, mya, nia, pag, pam, shn, sun, tet, tgl, tha, vie, war

License
Creative Commons Attribution Share Alike 4.0 (cc-by-sa-4.0)

Homepage
https://huggingface.co/datasets/sabilmakbar/sea_wiki

HF URL
https://huggingface.co/datasets/sabilmakbar/sea_wiki

Paper URL
No publication

Working on this issue, ETA tomorrow evening

#self-assign


Right-clicking on Discord messages brings up no context menu

Describe the bug
Right-clicking to bring up a context menu on a Discord message does nothing
To Reproduce
Steps to reproduce the behavior:

Go to any text channel in discord
Right-click on any message
See nothing happen

Expected behavior
A context menu should appear.
Desktop:

OS: Win 10
Ferdi Version 5.4.4-beta.3

Additional info:
No errors in the console.

@diceroll123 Is this happening on other services too? (Gmail, Slack, for example).

I don't know if Slack has custom context menus like Discord, but:
Gmail - context menu works when right-clicking an email in inbox
Slack - right clicking a message opens the windows context menu with Copy/Inspect Element
To clarify on Discord, it ONLY doesn't work for messages. It works for users in the sidebar and in chat, servers in the left sidebar, channels in the left sidebar.
Peculiar.

Sorry for the false alarm, folks. Turns out it's this way on the web client in my browser as well. (which I only used to look into this some more myself)
Googling this, it looks like it was an issue + was resolved 4 months ago.
In any case, doesn't seem to be Ferdi's bug. Closing!


bookstack: 23.08.3 -> 23.10.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bookstackapp/bookstack/releases.
meta.description for bookstack is: A platform to create documentation/wiki content built with PHP & Laravel
meta.homepage for bookstack is: https://www.bookstackapp.com/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 23.10.1 with grep in /nix/store/8bvx332qkikqbyalfbv1nva518i01bf8-bookstack

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
bookstack

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/838154f34e4e04b58a4ac8688f7e2ce0e4f39533#bookstack

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

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

1 package built:

bookstack

Maintainer pings
cc @ymarkus for testing.

old version, see #268909


Set Readme File

Explain project features & services. Also add some example usage with code blocks.

Actually GIF and images can add.


feat: allow more specific labels to search in the same cluster

the cluster could have multiple set of sentry nodes and proxy from different networks, proxy should be able to only gather sentry prival svc based on label like chain_id or other customized labels

@agouin any chance to review?


New feature

i have added 4 new "psychobabble's" that can react to certain patterns.

File changes look good I don´t see any major problems with the additions. Syntax seems fine as well.

The code looks fine but there are some conflicts with the branch that need to be resolved. In the code itself I don´t see any syntax problems and it should run properly.


[BUG] 1.20.1 JEI checking multiblocks crashes game with "Index 0 out of bounds for length 0"

Forge version:  47.2.32
Masterful Machinery version: 0.1.11
ADD ON'S
N/A
Botania version:  444
Mekanism version: <IP_ADDRESS>
Pneumaticcraft version: 6.0.15
Link to Log: https://gist.github.com/Joshernoob/dcf3c252ffd026f0a8bc7d8fed23c913

Load game with mods and multiblock
load world
try to use u on the controller to find it use
crash to desktop

What I expected to happen:
should show a JEI multiblock
What happened instead:
crash to desktop with a crash report naming this mod, JEI and Fancy Menu as the problems (if that helps)

this is not a bug, pls create a ticket in the discord server. i can help you resolve it there


Document frame rate with your 128x96 panel.

Great detail in your readme but would be nice to know what frame rates you achieve with your panels.

Hello
For my 128x96 I have 48 16x16 panels. Each panel has it's own virtual pin.
So the fps is the fps of 256 ws2812.=> 127 fps. The max theorical gps for 256 less is 130fps. I achieve 127 fps due to overhead in my driver.
Hence the 12288 are refreshed at 127fps.

Thanks!

Are you looking at using this driver for one of your builds?

Yes for a 3mx3m. 90x90 pixel panel art project.  But it wil have to wait since this will be a hobby project.


EventType subClassOf skos:Concept?

What is the use case for this?
https://github.com/tibonto/aeon/blob/77a0ce7d192d663a0c0bc83ca149a231af558565/aeon.ttl#L1467
It looks strange to me, but without knowing the intended use case I can't tell whether it's good or bad.

@clange: The idea behing making the EventType a skos:Concept is rooted in the fact, that there are no clear discriminators with which we can make a distinction that will hold in a global context as the definitions for the various event types vary depending on the sociocultural context.

@StroemPhi looking at this once more, I think what you meant is aeon:EventType rdf:type skos:Concept, i.e., instance instead of subclass.

@clange the instances of aeon:EventType are Conference, Workshop, etc. and yes they are suppose to be instances of skos:Concept so for example aeon:Conference rdf:type skos:Concept.
But how can I then group them in AEON if I can't make aeon:EventType a subclass of skos:Concept?
Or does that mean that we'd just have many individuals for skos:Concept and the range of aeon:has_event_type would be skos:Concept?

@clange the same pattern holds true for AEON_0000027 ('academic field') & AEON_0000028 ('topic'). If this can be modeled better wrt the fact that they we need some way to bundle these named individuals of skos:Concept that are event types, academic fields or topics, I'm happy to change this.

Acoording to the SKOS specs, I should have been using skos:Collection alongside with the skos:memeber relation instead of skos:Concept in order to be able to group the skos:Concepts of academic field, event type and topic.
Will be fixed in:

a3f4a29 is the result of rebaseing this branch on https://github.com/tibonto/aeon/tree/issue6-definitions-and-descriptions, as this contains more up to date definitions.

So the idea is that event type becomes an iao:plan specification, as the type of an academic event is made up by the sociocultural format the organizers chose. The good thing about it being a plan spec is that this entails action and objective specifications. When we now also add to have condition specifications as part of the academic event type specification, we have everything needed to describe the plans of the organizers.
The only thing I didn't think tzhrough before pushing is that the subclasses of academic event should not be logically defined using the named individuals for the event type specs defined in AEON via the rdfs:equivalentTo but rather the rdfs:subclassOF axiom. Will fix this now.


Improve README.md

Improved readme.md file

@shubhsharma19 Thank you for your contribution! Share our project with others to help it grow. Your PR has been merged successfully. Keep up the great work!


Make daemon.json settings configurable

This allows it to configure all daemon.json options via vars.

Hello, @mhutter
Thanks for this PR. I like the improvement to the Docker daemon configuration. It's a clever idea.
Could you please update further the README file so that users know how to actually configure the Docker daemon through the docker_config variable?
Cheers!

Updated README to mention docker_config

Looking good! Let's get this merged.


Authentication support

Added a single user account with statically set username and password in /webapp/auth.py env vars. Planning on creating a secure user database and browser based user management.


White bar on top of pastebin when viewing on mobile

There's a white bar on mobile (< 480px) when viewing pastes.

Gonna close this one. If this still happens, please open a new issue at the new repo.


Reduce the frequency of retrying to kill tasks.

With the current setting marathon will retry to kill tasks after 5seconds if it hasn't received a confirmation in that timeframe (https://github.com/mesosphere/marathon/blob/a35f1c9f4f0dec7501de55efa72742510afe6d1c/src/main/scala/mesosphere/marathon/upgrade/StoppingBehavior.scala#L76),
When killing a lot of tasks it is very unlikely that after 5 seconds all tasks are killed, and hence marathon will create a lot of additional load for the Mesos Master by retrying to kill the large number of outstanding tasks over and over again. Potentially we should try to make the retry adaptive to the number of outstanding tasks to be killed or even partition the tasks to be killed.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2384. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


nixpkgs: add module

Looks good and works as it's intended, one thing to note that i just found out by testing this is that having a lib overlay does not influence the lib argument passed to modules, you need to use pkgs.lib for the stuff in your overlays. I'm not sure why that's not possible, maybe it can be changed upstream.

Yeah, the lib module argument seems kind of hard coded in NixOS so it will not be affected by overlays. I'm not sure whether this is intentional or not.
In any case, this branch is merged to master now. Thanks for the comments and testing!


Eventlog: Staking request data to BALN token SCORE

Add an event log to setStake transactions indicating the change in stake.
For example, if Bob currently has 1,000 BALN staked and changes it to 800 BALN staked, the event should return "-800" labeled changeInStake

@dbrehmer @BennyOptions Is this the problem we need to solve?


Empty port field expects all ports being allowed

This patch fixes the empty Ports field case, it expects all ports being
allowed. Reconciler should convert nil or empty Services to nil when
converting to Openflow PolicyRule. nil represents "not restricted by port"
in Openflow PolicyRule.
Related to #52

@jianjuns I just realized that the current implementation is correct, the function will return nil when services is nil or empty. The issue I was investigating was not because of it, abandon this PR.


Error in Multi-Job Submission

I was using a Python script to generate and run multiple jobs. The script would create multiple deferred job submissions before running one qf check at the end to fill queues. After the first job was successfully submitted, I received the following error:
Traceback (most recent call last):
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/bin/qf", line 8, in <module>
    sys.exit(main())
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/cli.py", line 174, in main
    program.check()
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/program.py", line 124, in check
    self.check_impl(conn)
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/program.py", line 217, in check_impl
    while self.try_dequeue_one(conn):
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/program.py", line 246, in try_dequeue_one
    if limit is None or self.queue_has_open_slots(queue, limit):
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/program.py", line 257, in queue_has_open_slots
    for job in self.enumerate_own_backend_jobs_in_queue(queue):
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/program.py", line 269, in enumerate_own_backend_jobs_in_queue
    for job in self.backend.get_own_pending_jobs()
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/real_backend.py", line 61, in get_own_pending_jobs
    return [dict_to_job(job) for job in pending_jobs]
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/real_backend.py", line 61, in <listcomp>
    return [dict_to_job(job) for job in pending_jobs]
  File "/afs/crc.nd.edu/user/s/sbothwel/.local/lib/python3.8/site-packages/qfunnel/real_backend.py", line 108, in dict_to_job
    queue=d['queue_name'] or d['hard_req_queue'],
KeyError: 'hard_req_queue'

The error did not stop jobs from being properly submitted nor cause any known issues. However, it happened upon the submission of every second job for every use of qf check.

Was the queue full at the time, i.e. was the job in the qw state? Or was the job able to go into the r state right away?

The queue was not full at the time. There was space, and the jobs could have gone into the r state right away. I don't remember ever seeing a qw state when I was handling the issue.

The XML API from qstat changed when the CRC updated its software over the break. I've updated qfunnel accordingly.


Sending single message for multiple devices

SimplePushNotification class accept only one tokens and for each token we are generating the simple push notification class instance instead is there any simple approach to send same message for multiple devices

is there any simple approach to send same message for multiple devices

Well, I think you mean "is there a method in Pushy to do this," to which the answer is "no." To literally answer your question, though, there is indeed a simple way to send the same message to multiple devices: just use a for loop.
We have declined to implement a "multi-send" feature in the past for two main reasons:

There's no protocol-level notion of sending the same notification to multiple devices, and so our internal implementation of such a method would just be a for loop anyhow.
It's unclear what a "multi-send" method should return. Should it be a single Future? If so, what happens if some notifications are accepted and some are rejected? There are a range of reasonable answers to these questions, but none will be right for everybody.

Because the need is easily met outside of Pushy and because an attempt to build a multi-send feature into Pushy would have a complexity cost way out of proportion to the benefits, we will not implement this feature in the foreseeable future.


Feat: Add a workflow to close old issues

Describe the feature
An automated implementation titled the Close Old Issue Bot is intended to quickly locate inactive or resolved issues and close them.
By removing clutter and ensuring active focus on important tasks, it increases the effectiveness of issue management.
The Github actions workflow will be created in the ./github/workflows directory in order to automate the task of closing the old/inactive issues.
The workflow tracks the status of open issues and flags those that haven't been updated in a while.
Promotes a tidy and organized issue tracker by closing out-of-date or resolved issues in accordance with specified criteria.
Add ScreenShots
NA
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

Hey @abhinav-m22 | We do not need this now


Error loading page

Describe the bug
Can't watch anything get "Error loading"
To Reproduce
Click on any anime (or even dubbed)
Click any episode
Shows error screen
Expected behavior
Play anime...
Screenshots

Smartphone (please complete the following information):

Device: Android
Version 12

Additional context
Did the source url break?

@Myst400 I will get working on fixing this bug please give me a few days to fix it.

@Myst400 I fixed the issue, It should work now. Thank you for reporting the issue.


Add try/(catch) to downloading function

Downloading data from GBIF could be wrapped in try() to catch timeout errors; also write to logs when maximum number of attempts is reached (and failed). Logs can then be checked for things to re-attempt downloading.

See the query_gbif() function in the West Virginia White project.

Added this and went ahead re-running the rest of the data pipeline (download, filter, presence/absence). Will take a look later at delta of records. @ezylstra

@jcoliver. Something weird happened with the shapefiles zip so we didn't have 5 files for each species. Often the .prj file was missing.  I re-ran gbif-3-presence-absence.R after clearing out anything in my local gbif/shapefiles and gbif/presence-absence folders and now the shapefiles.zip seems to be complete.  Not sure what happened, but make sure to pull the latest version with new zips before you work on anything.  Eventually, we may need to add something to gbif-3-presence-absence.R that would clear out any existing files (assuming we want to replace them), but this isn't urgent if we're both working with the latest version and we're not running src/data scripts.


WebDriverRunner.getBrowserDownloadsFolder() returns null when 'selenide.remote` enabled

The problem
When running tests via Selenoid, it's required to download files from a container.
For Selenide 5.15.1 download was happening to the folder we could get via WebDriverRunner.getBrowserDownloadsFolder().
For the Selenide version specified below, WebDriverRunner.getBrowserDownloadsFolder() returns null when a method tries to determine a folder to download the file.
Tell us about your environment

5.18.0:
Chrome 88.0:

Yes, it's reasonable because "BrowserDownloadsFolder" only applies to local browser. In case of remote browser, we don't know what folders exist on the remote machine.
Why do you need this value? How can you use it, if the folder is located on another machine anyway?
P.S. If you run browser in Selenoid, we have specific support in selenide-selenoid module.

Yes, it's reasonable because "BrowserDownloadsFolder" only applies to local browser. In case of remote browser, we don't know what folders exist on the remote machine.
Why do you need this value? How can you use it, if the folder is located on another machine anyway?
P.S. If you run browser in Selenoid, we have specific support in selenide-selenoid module.

My scenario is the following:

Obtain the unique for the current session folder
Download file from Selenoid to that folder (FileUtils.copyURLToFile)

For Selenide 5.15.1 the folder wasn't null for such kinds of scenarios.

My scenario is the following:

Obtain the unique for the current session folder
Download file from Selenoid to that folder (FileUtils.copyURLToFile)

For Selenide 5.15.1 the folder wasn't null for such kinds of scenarios.

@imaksymiv Clear, thanks.
I suggest just to use selenide-selenoid dependency. It does exactly what you need. You can use the old good Selenide method $.download(), and selenide-selenoid will fetch the file from Selenoid container and save to a unique folder on your machine.

@imaksymiv Clear, thanks.
I suggest just to use selenide-selenoid dependency. It does exactly what you need. You can use the old good Selenide method $.download(), and selenide-selenoid will fetch the file from Selenoid container and save to a unique folder on your machine.


fix: fix missing word in chat message

raycast/extensions#11141

Hi @almoce, thanks for your help, I have also fixed the bug when using tags.


Initial release?

Would it be possible to cut an initial version of when?

What do you mean by that?

Basically tagging a version in Git so that a release of when can be made available. As of right now there are no releases present for when: https://github.com/mitsuhiko/when/releases
I'd like to package when to add it to MacPorts, but there are no releases or versions of when available to do so.

Ah okay. I will tag something off on the weekend probably. I want to make it so it actually builds from source without having to download something from geonames first.

This is now published to crates.io under the name when-cli.

Thank you @mitsuhiko. when is now available via MacPorts: https://ports.macports.org/port/when/


Permanent grouping of widgets

To actually better manage large VIS Views it would be great if VIS would get a functionality to permanently group widgets into one permanent unit so that all operations will be performed on the group and its members. In addition there would of course be the need to also be able to ungroup them again to access individual member information/functionality.

Good idea

Should work now


Error while training on custom_coco dataset

Question
Hi @xiuqhou ,I wanted to train Relation_detr on my custom coco_dataset but getting error.

how can i resolve this?
Additional
Also please suggest me some fine tunning strategy that should i follow for more accuracy
No response

Hi there,
Thank you for helping us find a bug. This error occurred in some versions of pytorch, which we did not encounter in the initial code test. Now that we have fixed it in our latest code, please use our updated repository and try again!
To get better accuracy, we have some suggestions:

Make sure learning rate follows the linear scaling rule with total batch_size. If total_batch_size increases k times, learning rate should be increased k times. We set learning_rate=1e-4 for  batch_size=5 and 2 GPUs (total_batch_size=5 * 2=10). If you use batch_size=2 and 1 GPU (total_batch_size=2), for example, you should change learning rate to 2e-5.
If you just want better performance, instead of making a fair comparison with other methods in a paper. You can use a stronger data_augmentation. Set transform  in configs/train_config.py to presets.strong_album will increase accuracy.
And remember to use larger backbones and load pretrained weight. We will update more pretrained weight in the next few weeks.


To have a 100% test coverage on ipycytoscape

From @ianhi comment's:
Still needed:

[ ] json graph creation
[ ] df graph creation
[ ] tests for CytoscapeWidget methods
[ ] Tests of adding interaction callbacks

will require using the mocked comms to fake a message.

[ ] typescript tests (need to expand on this and be more specific, please feel free to contribute to this issue with test ideas!)

maybe use karma-typescript (I think it came with the js cookie cutter)

If you're adding one of these tests please reference this issue.

will require using the mocked comms to fake a message.

This was just to note that these mocks already exist from the cookiecutter.

maybe use karma-typescript (I think it came with the js cookie cutter)

These have been updated a bit since ipycytoscape was created in order to get them pass. Should be based on the content here:
https://github.com/jupyter-widgets/widget-ts-cookiecutter/tree/master/{{cookiecutter.github_project_name}}/tests

pre 100% I think we should focus on having tests for the methods to create the graph as these have definitely been the source of pretty much all new bugs. Networkx had the most bugs so made those tests first. With first set of tests the coverage looks like this: https://codecov.io/gh/quantstack/ipycytoscape/src/0079bf2768036df4435c7d10e3927d9e7de19b34/ipycytoscape/cytoscape.py
So we should also add:

[ ] test add_node. add_edge, remove_node, remove_edge, remove_edge_by_id

I think we covered these:
json graph creation
df graph creation
tests for CytoscapeWidget methods

Right @ianhi ?
Also, do you know any example we can copy for

Tests of adding interaction callbacks

I think we covered these:

I don't thnk we have. We've just added more complete tests of the possibilities with networkx https://github.com/QuantStack/ipycytoscape/blob/master/ipycytoscape/tests/test_graph_creation.py
json is probably the easiest thing for someone to get started on.

Also, do you know any example we can copy for
Tests of adding interaction callbacks

Not off the top of my head. I think we would need to make Mock events and feed them in. But if anything this would make more sense on the typescript side. Maybe this is one to leave until there is a better testing framework for jupyter.

So we should also add:
* [ ]  test `add_node`. `add_edge`, `remove_node`, `remove_edge`, `remove_edge_by_id`

I'm not very familiar with automated testing. Is it necessary to test remove_edge and remove_edge_by_id? Basically remove_edge_by_id calls remove_edge. So if remove_edge_by_id  works like intended this should also be valid for remove_edge, or miss I something?
(I try to write some tests for this at the moment.)

what do you mean by "df graph creation"?

Dataframe graph creation - Create a graph from a pandas dataframe

Ok, I am on that one right now.
I actually would have some questions.
Should I open an issue on questions about this implementation?
How is it possible to share code to be commented/discussed over before pulling?

Is it necessary to test remove_edge and remove_edge_by_id? Basically remove_edge_by_id calls remove_edge. So if remove_edge_by_id works like intended this should also be valid for remove_edge, or miss I something?

I think everything you said here is correct, but it can still be nice to test both as that makes easier to figure out what went wrong. So perfect world do both, but don't let the perfect be the enemy of the good and either would be an improvement over the current situation.

I actually would have some questions.
Should I open an issue on questions about this implementation?
How is it possible to share code to be commented/discussed over before pulling?
Actually it is perfectly possible

Feel free to open PRs to get early feedback if you'd like. Otherwise for tests posting quesitons in this issue is probably a good move.

pre 100% I think we should focus on having tests for the methods to create the graph as these have definitely been the source of pretty much all new bugs. Networkx had the most bugs so made those tests first. With first set of tests the coverage looks like this: https://codecov.io/gh/quantstack/ipycytoscape/src/0079bf2768036df4435c7d10e3927d9e7de19b34/ipycytoscape/cytoscape.py
So we should also add:
* [ ]  test `add_node`. `add_edge`, `remove_node`, `remove_edge`, `remove_edge_by_id`

#225

pre 100% I think we should focus on having tests for the methods to create the graph as these have definitely been the source of pretty much all new bugs. Networkx had the most bugs so made those tests first. With first set of tests the coverage looks like this: https://codecov.io/gh/quantstack/ipycytoscape/src/0079bf2768036df4435c7d10e3927d9e7de19b34/ipycytoscape/cytoscape.py
So we should also add:
* [ ]  test `add_node`. `add_edge`, `remove_node`, `remove_edge`, `remove_edge_by_id`

#225

pre 100% I think we should focus on having tests for the methods to create the graph as these have definitely been the source of pretty much all new bugs. Networkx had the most bugs so made those tests first. With first set of tests the coverage looks like this: https://codecov.io/gh/quantstack/ipycytoscape/src/0079bf2768036df4435c7d10e3927d9e7de19b34/ipycytoscape/cytoscape.py
So we should also add:
* [ ]  test `add_node`. `add_edge`, `remove_node`, `remove_edge`, `remove_edge_by_id`

#225

:cherry_blossom:


ReadMail operator does not handle HTML mime type

We only handle text mime type.
In some cases, emails are only sent with HTML mime, and we are not able to extract content from the email.

Fixed, added handling of HTML MIME Type.


[DOC-1388] REST API Client doesnt reset response when changing active item

Expected Behavior
the response should be empty or chosen from response history of the active request
Actual Behavior
last request regardless of active
Reproduction steps
send request
change active item
response is for other request

Link to site / OpenAPI Spec
No response
Version
latest
What browsers are you seeing the problem on?
No response
DOC-1388

Good news, this was fixed in #573 already: https://github.com/scalar/scalar/blob/main/packages/api-reference/src/helpers/showItemInClient.ts#L21


(FOR REVIEW) (SERVER-325) flush jrubies after max requests

NOTE: not ready for merge; need to clean up some of the last few commits and add a few more tests.

This PR does the following:

Change our JRuby queuing strategy from FIFO to LIFO.  (This improves memory usage by a great deal when the system is not under high load, and also makes it possible for us to flush individual JRuby instances after a maximum number of requests in a sane way; in a FIFO model, all JRuby instances would hit the max number of requests at roughly the same time.)
Refactors a lot of the JRuby code to make it possible to flush instances with more granularity than the entire pool
Introduce a setting 'max-requests-per-instance'; after any JRuby instance handles more requests than this, it will be flushed and replaced in the pool by a fresh one

Needs rebase?

This seems like a good thing.  At a high level, the implementation details (LIFO vs. FIFO, tracking request counts, etc.) all sounds sane me.

@KevinCorcoran thx; this'll get put on hold for a bit as it's targeted at 1.1 and not 1.0.4, but as soon as I rebase it and address @camlow325 's comments I was planning on pinging you for a more in-depth review.

sure, sounds good

Closing this until after our 1.0.x release; also need to rebase and try Jeremy's suggestion of switching to flush-on-return instead of flush-on-borrow.  Will re-open when that's ready.


REGISTRY: Error: Unsupported extrinsic payload version 5

Hi there.
I tried to construct&sign with the latest version of txwapper-polkadot 0.5.1 on Westend node. But, signing always fails with the following error message.
...
Payload to Sign: 0x900403...
2021-04-28 18:01:16        REGISTRY: Error: Unsupported extrinsic payload version 5
    at new GenericExtrinsicPayloadUnknown (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/extrinsic/ExtrinsicPayloadUnknown.cjs:23:11)
    at new Type (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/registry.cjs:349:16)
    at initType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:44:19)
    at createTypeUnsafe (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:63:12)
    at createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:78:10)
    at TypeRegistry.createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/registry.cjs:306:39)
    at Function.decodeExtrinsicPayload (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/extrinsic/ExtrinsicPayload.cjs:39:21)
    at new GenericExtrinsicPayload (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/extrinsic/ExtrinsicPayload.cjs:29:45)
    at new Type (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/registry.cjs:349:16)
    at initType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:44:19)
2021-04-28 18:01:16        REGISTRY: Error: createType(ExtrinsicPayloadUnknown):: Unsupported extrinsic payload version 5
    at createTypeUnsafe (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:66:11)
    at createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:78:10)
    at TypeRegistry.createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/registry.cjs:306:39)
    at Function.decodeExtrinsicPayload (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/extrinsic/ExtrinsicPayload.cjs:39:21)
    at new GenericExtrinsicPayload (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/extrinsic/ExtrinsicPayload.cjs:29:45)
    at new Type (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/registry.cjs:349:16)
    at initType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:44:19)
    at createTypeUnsafe (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:63:12)
    at createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:78:10)
    at TypeRegistry.createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/registry.cjs:306:39)
(node:7750) UnhandledPromiseRejectionWarning: Error: createType(ExtrinsicPayload):: createType(ExtrinsicPayloadUnknown):: Unsupported extrinsic payload version 5
    at createTypeUnsafe (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:66:11)
    at createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/createType.cjs:78:10)
    at TypeRegistry.createType (/home/alice/team/alice_repo/test/node_modules/@polkadot/types/create/registry.cjs:306:39)
    at /home/alice/team/alice_repo/test/dist/test.js:207:10
    at Generator.next (<anonymous>)
    at fulfilled (/home/alice/team/alice_repo/test/dist/test.js:5:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

My source code is:
...
//  chain info fetched from Westend node
const genesisHash: string = await _client.getGenesisHash();
const { hash, height } = await _client.getFinalizedBlockInfo();
const runtimeVersion: RuntimeVersion = await _client.getRuntimeVersion(hash);
const metadataRpc: string = await _client.getMetadataRpc(hash);

const registry = getRegistry({
    chainName: 'Westend',
    specName: 'westend',
    specVersion: runtimeVersion.specVersion,
    metadataRpc: metadataRpc
});

//  sender info
const keyring = new Keyring({type: 'sr25519', ss58Format: 42});
const account = 'alice';
const index = 0;
const keypair = keyring.createFromUri(`${config.Mnemonic}//${account}//${index}///${config.Password}`);
const from = encodeAddress(keypair.publicKey, 42);
const nonce = await _client.getNextAccountNonce(from);

//  destination
const dest = '5HSvA742A9gkxtBMDQB4VzH2vCbE2CQ9MNdJrMmaap4dWpFK';

const unsigned = methods.balances.transferKeepAlive(
    {
        value: '1',
        dest: dest,
    },
    {
        address: from,
        blockHash: hash,
        blockNumber: registry
            .createType('BlockNumber', height)
            .toNumber(),
        eraPeriod: 64,
        genesisHash,
        metadataRpc: metadataRpc,
        nonce: nonce,
        specVersion: runtimeVersion.specVersion,
        tip: 0,
        transactionVersion: runtimeVersion.transactionVersion,
    },
    {
        metadataRpc: metadataRpc,
        registry: registry,
    }
);

// Decode an unsigned transaction.
const decodedUnsigned = decode(unsigned, {
    metadataRpc: metadataRpc,
    registry: registry,
});
console.log(
    `\nDecoded Transaction\n  To: ${
        (decodedUnsigned.method.args.dest as { id: string })?.id
    }\n` + `  Amount: ${decodedUnsigned.method.args.value}`
);

// Construct the signing payload from an unsigned transaction.
const signingPayload = construct.signingPayload(unsigned, { registry: registry });
console.log(`\nPayload to Sign: ${signingPayload}`);

registry.setMetadata(createMetadata(registry, metadataRpc));
const { signature } = registry
    .createType('ExtrinsicPayload', signingPayload, {
        version: runtimeVersion.transactionVersion,
    })
    .sign(keypair);

const txPayload = construct.signedTx(unsigned, signature, {
    metadataRpc: metadataRpc,
    registry: registry,
});

const { success, result } = await _client.submitExtrinsic(txPayload);
console.log(success);
console.log(result);

It seems transaction version 5 is fetched from the node, but the current library(or registry) doesn't support it.
Can you guide me to solve this issue?

Hey @steegol. Sorry for the delayed response. You may want to try and pull down master and see if that can work as we have updated the @polkadot/* dependencies, and there is a potential chance that could be the issue. I will also look into this and see if I can get a more accurate diagnosis for you.

So i looked into it and you are correct about the transactionVersion lacking support regarding the error Unsupported extrinsic payload version 5,  in @polkadot/api here.
As you mentioned version 5 is not supported. That can be seen here under the GenericExtrinsicPayload class where the type is generated. (Linking these to have references to the issue at hand).
That leads me to a few questions.

I tried to run and get your code working, but cant seem to get _client working. Is this an internal custom ApiPromise wrapper you have built? If so could you share how you are getting the runtimeVersion so that I can test it out on my westend-local chain?

is that encodeAddress you have from @polkadot/util-crypto as well? (Just making sure).

Are you connected to a live chain, or offline? If offline, which runtimeVersion of westend are you currently running on? This is so that I can try and reproduce your error with the correct node.

Ahh. Okay, so the actual issue is the version you are placing inside of here.
const { signature } = registry
    .createType('ExtrinsicPayload', signingPayload, {
        version: runtimeVersion.transactionVersion,
    })
    .sign(keypair);

it should rather be
import { EXTRINSIC_VERSION } from '@polkadot/types/extrinsic/v4/Extrinsic';

const { signature } = registry
    .createType('ExtrinsicPayload', signingPayload, {
        version: EXTRINSIC_VERSION,
    })
    .sign(keypair);

The extrinsicVersion should always point to 4.
I rewrote a working version of your example to give a little more context on how I got it working locally.
import { Keyring } from '@polkadot/api';
import { cryptoWaitReady } from '@polkadot/util-crypto';
import { rpcToLocalNode } from './util';
import { EXTRINSIC_VERSION } from '@polkadot/types/extrinsic/v4/Extrinsic';
import {
    construct,
    decode,
    getRegistry,
    methods,
    createMetadata,
    deriveAddress
} from '@substrate/txwrapper-polkadot';

const main = async () => {

    // Wait for the promise to resolve async WASM
    await cryptoWaitReady();
    // Create a new keyring, and add an "Alice" account
    const keyring = new Keyring();
    const alice = keyring.addFromUri('//Alice', { name: 'Alice' }, 'sr25519');
    console.log(
        "Alice's SS58-Encoded Address:",
        deriveAddress(alice.publicKey, 42)
    );

    const { block } = await rpcToLocalNode('chain_getBlock');
    const blockHash = await rpcToLocalNode('chain_getBlockHash');
    const genesisHash = await rpcToLocalNode('chain_getBlockHash', [0]);
    const metadataRpc = await rpcToLocalNode('state_getMetadata');
    const { specVersion, transactionVersion } = await rpcToLocalNode(
        'state_getRuntimeVersion'
    );

    const registry = getRegistry({
        chainName: 'Westend',
        specName: 'westend',
        specVersion: specVersion,
        metadataRpc: metadataRpc
    });

    //  destination
    const dest = '5HSvA742A9gkxtBMDQB4VzH2vCbE2CQ9MNdJrMmaap4dWpFK';

    const unsigned = methods.balances.transferKeepAlive(
        {
            value: '1',
            dest: dest,
        },
        {
            address: deriveAddress(alice.publicKey, 42),
            blockHash,
            blockNumber: registry
                .createType('BlockNumber', block.header.number)
                .toNumber(),
            eraPeriod: 64,
            genesisHash,
            metadataRpc: metadataRpc,
            nonce: 0,
            specVersion: specVersion,
            tip: 0,
            transactionVersion: transactionVersion,
        },
        {
            metadataRpc: metadataRpc,
            registry: registry,
        }
    );

    // Decode an unsigned transaction.
    const decodedUnsigned = decode(unsigned, {
        metadataRpc: metadataRpc,
        registry: registry,
    });
    console.log(
        `\nDecoded Transaction\n  To: ${(decodedUnsigned.method.args.dest as { id: string })?.id
        }\n` + `  Amount: ${decodedUnsigned.method.args.value}`
    );

    // Construct the signing payload from an unsigned transaction.
    const signingPayload = construct.signingPayload(unsigned, { registry: registry });
    console.log(`\nPayload to Sign: ${signingPayload}`);

    registry.setMetadata(createMetadata(registry, metadataRpc));

    const { signature } = registry
        .createType('ExtrinsicPayload', signingPayload, {
            version: EXTRINSIC_VERSION,
        })
        .sign(alice);

    const txPayload = construct.signedTx(unsigned, signature, {
        metadataRpc: metadataRpc,
        registry: registry,
    });

    console.log(`\nTxPayload: ${txPayload}`);

}

main().catch((error) => {
    console.error(error);
    process.exit(1);
});

@steegol Hope that helps :)

Thank you for your comments and gentle guide. It worked now!
Just for recap, my misunderstanding was that transactionVersion is synonym to extrinisicVersion. Am I correct?

@steegol Yup Exactly.

Closing this issue due to being resolved.


Add animation on drag and drop and a ghost style for the item being dragged

Drag works great, but it looks incomplete from a UX point of view.
It would be great if:

There was a ghost style applied to the item being dragged (i.e. so that the user can see it is being dragged). This should be configurable.
Would be nice if there was an animation to that showed items re-sequence on drop.

Yes, having animation for the drag and drop would be very nice.

An easy solution would be using react-dnd as shown in the example https://react-dnd.github.io/react-dnd/examples/sortable/cancel-on-drop-outside
In this example, the tag order is already changed while dragging (and changed back if dragged outside), which keeps the "drop ghost" at the actual drop position.


Fix redundant badge notification.

Fix badge notifications being displayed twice if :AwardBadge is called in quick succession.

This pull request looks good to me. I think we should merge it.


getting undefined: X_GoV8 on install

here is the final output of attempting to run ./go/build.sh install:
cd /Users/paetling/gc/gc/servertooth_go/src/github.com/sony/v8eval/go/v8eval
/usr/local/go/pkg/tool/darwin_amd64/compile -o $WORK/github.com/sony/v8eval/go/v8eval.a -trimpath $WORK -p github.com/sony/v8eval/go/v8eval -complete -buildid e5c9b41c69fd04b9e1a776f6ec77f19245d2ba69 -D _/Users/paetling/gc/gc/servertooth_go/src/github.com/sony/v8eval/go/v8eval -I $WORK -pack ./v8.go
# github.com/sony/v8eval/go/v8eval
./v8.go:36: undefined: X_GoV8
# github.com/sony/v8eval/go/v8eval
./v8.go:36: undefined: X_GoV8
FAIL	github.com/sony/v8eval/go/v8eval [build failed]

I am running on a mac with version 10.11.3 and have go version go1.5.1. I am not sure what is actually going wrong and am trying to investigate. But thought I would submit an issue to see if you had any suggestions or if there is anything obvious I am missing?

Update installation on Ubuntu 14.04 with go version: go1.5.1 also fails with the same error.

v8eval requires SWIG, which generates X_GoV8. What version of SWIG do you use?

I see. I did not have swig installed on my mac. Once I installed that I was able to install. Am trying the linux installation now.
Thanks for the help


Fix generic type validation to support datetimes and non-ASCII strings.

SC-24612
The C# API's rules around type validation in its generic methods have some defects that prevent datetime types and non-ASCII strings from being used. This PR improves the type validation to fix these cases.
Summary of changes

When performing type validation, instead of converting the .NET Type to a TileDB DataType and compare them, we do the opposite. This happens because (with few exceptions), the mapping between .NET types and TileDB data types is one-to-many, and so by "narrowing down" we can validate that datetime data types match with long, while long maps to DataType.Int64.

The validation logic was centralized in the ErrorHandling.CheckDataType. It accepts a generic type parameter and a DataType regular parameter, and fails if they are incompatible.

There are two special cases for validation: DataType.Boolean and StringUtf16. Besides byte and ushort, they can also match with bool and char (in .NET it's 2 bytes long) respectively.

We could do the same with StringUtf32 and System.Text.Rune, but the Core must validate that UTF-32 strings contain valid Unicode codepoints (if it already does, please let me know).

Behavior breaking change: The EnumUtil.DataTypeToType method mapped all string DataTypes to sbyte, which is an obviously wrong behavior, and inconsistent with what the C++ API does. This PR changes it to map ASCII and UTF-8 strings to byte, UTF-16 strings to ushort, and UTF-32 strings to uint.

In case of DataTypes with multiple valid types (like StringUtf16 and Boolean), DataTypeToType returns the matching numeric type.

Minor behavior breaking change: Some generic methods throw ArgumentException which is more appropriate than InvalidOperationException. Not commonly expected to hit, but worth mentioning.

The failing examples in #258 succeed after this.

Behavior breaking change: The EnumUtil.DataTypeToType method

Is there any way that external users could be relying on this behavior?

Besides the validation we do, one other use case I could find for this method is to dynamically construct an array of that type using reflection, as part of processing TileDB arrays of unknown schemata, but there are better ways of doing this.
Another thing we could do is make an internal edition of this method with the updated behavior and deprecate the public TypeToDataType and DataTypeToType methods, keeping the existing behavior in the meantime.

Thanks


[AutoRelease] t2-security-2022-07-20-42742(Do not merge)

https://github.com/Azure/sdk-release-request/issues/3001
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1028

issue link:https://github.com/Azure/sdk-release-request/issues/3001


Version 2.5, incorporating OSCAR data

This PR uses the updated exquisite-corpus that gets its Web data from OSCAR, providing a large amount of natural text in a number of languages.
Given our criteria that a "small" wordlist needs 3 sources of data and a "large" wordlist needs 5, this adds new support for the following languages:

Filipino (Tagalog)
Icelandic
Lithuanian
Malayalam
Slovak
Slovenian
Tamil
Urdu
Vietnamese

These languages now have "large" wordlists:

Bengali
Catalan
Hebrew
Norwegian Bokmål
Swedish
Ukrainian

Vietnamese is included at the syllable level, because syllables are separated by spaces. At one point I believed that Vietnamese would have to be handled more like Chinese, with a heuristic-based tokenizer that grouped multiple syllables together into words, but when I scan the Vietnamese Wiktionary data I find that the multi-syllable entries seem to be phrases that decompose into defined words. Tokenizing Vietnamese by splitting on spaces seems to also put us in line with how other NLP systems handle it.

Not sure how Galician got in there, because it only has 2 sources. I'm guessing it was a file left behind from a different build attempt where it had 3, before I filtered some data.