How can I apply jquery validation plugin to the Trumbowyg?

How can I apply jquery validation plugin to the Trumbowyg, for simple validation such as empty, maxlength, etc.

Run validation on the textarea like there is no Trumbowyg. It will work.

I will give it a try.

@Alex-D no it doesn't work when you leave editor it throws this error:
Uncaught TypeError: Cannot read property 'replace' of undefined

I am having the same issue on my application. I've checked here and it is like Trumbowyg has the input from the user when access via get $('#temp').trumbowyg('html') but when I access the value on the textarea itself it is empty.

Same happens to me, when i start typing on the trumbowyg textarea i start getting Cannot read property of undefined. Trying to fix it but i think it might be a validate problem.

With each new textarea, insert a new line assigning an id to the generated div:
$("div.trumbowyg-editor.trumbowyg-reset-css").eq(0).attr('id', 'S1');
$("div.trumbowyg-editor.trumbowyg-reset-css").eq(0).attr('id', 'S2);
...

$('#submitbutton').click(function() {
    if ($('textarea[name="mytextarea"]').val() == '') {
        $('.showmessage').css("display", "block");
        return false;
    } else {
        $('.showmessage').css("display", "none");
    }
});

@Dhiarllon let me to the following solution that has helped me, as I was getting the following error whenever jQuery validation tries to work a Trumbowyg element:
Uncaught TypeError: Cannot read properties of undefined (reading 'replace')

Try adding a random value to an id attribute in the trumbowyg-editor div. Something like this will work although I'm sure there are more elegant solutions:
$(".trumbowyg").find(".trumbowyg-editor").attr("id", Math.random());


chore(monitoring): promote from incubator to production

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

v2.4.2
v2.4.2
GitHub release

Your semantic-release bot :package::rocket:


Coinview: move to interface

This is 1st part of my work on coinview. In this PR abstract class CoinView was replaced with an interface.
Some methods were renamed, implemented GetTipHash in a correct way (instead of calling Fetch with an empty array)
Next steps:

ensure rewind data is not aggregated. (save in batches)
rewind based on blocks
remove some fields from rewind data that we can get from disconnected block.
Change signaling to ChainedHeaderBlock
signal on block disconnected

There is not much in this PR, which is good, so just couple of comments I made, so please address those, otherwise it looks good.

Looks good now

running networks now

Not sp1?

It's not a part of the sprint but a part of core way of syncing.
However I can create issues for everything we are doing for core way of syncing and proven headers so we can include those to sprints


introduced generators/shuffle : tool to shuffle selected text

you see, the build if failing if I don't lintfix in TravisCI. I lintfixed in my local

build is passing. YAAAY!

So is it good to be merged?


[Bug]: The page order doesn't work as expected in page setting page

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The page order doesn't work as expected in page setting page

https://release.app.appsmith.com/applications/61b6f62066fa8b31464b0a33/pages/61b71d095440164c77e9f7f6/edit/pages
Steps To Reproduce

go to page setting page
Try to reorder the page name from page setting page
The order doesn't work as expected

Environment
Release
Version
Cloud

@RakshaKShetty why is this issue marked low? Isn't this core functionality that is broken?

@Nikhil-Nandagopal This issue i am facing in one of my app so i have kept the  priority as low

Issue is resolved with new UX


Security implications of exec-host

What happened (or feature request):
During security discussions of ddev-ui's privilege escalation, it was discussed that only allowing ddev prefixed commands to be sudo'd via the UI. This led to the conclusion that ddev exec-host could be similarly as disastrous (i.e. ddev exec-host rm -rf /*). While commands that ddev-ui uses can be very tightly controlled, the security/safety implications of exec-host needs to be addressed on a CLI level.
What you expected to happen:
ddev exec-host should provide a level of safety in which an accidental command does not cause system-wide damage.
How to reproduce this:
Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.
all
Anything else do we need to know:
N/A
Related source links or issues:
DDEV-UI Issue 14
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)
Unknown

I never heard of ddev exec-host.  ?
I definitely think we should only exec ddev with advanced privs, and only with a full path to known executable, and only one command that we need.


Missing commit? What's going on

I just had a problem using the Document invite, because apparently one of the Commits is missing.
Error opening https://atomicdata.dev/invites/1?public-key=dlOABAaykKn7F5KTOYK3gOuxSiMOLzeljtNLmcnUWNs%3D
Unable to get commits for https://atomicdata.dev/document/pnf5jlv3r2f. Resource not found. Failed to retrieve locally: 'https://atomicdata.dev/commits/Ony7Xa5pm3pdQHJrXIhSu+HUrVeGuBQ7FzzbzRBJTmZclPHUah1h35lRGwqn4dAlgML+KGyGSYM8WgV1AeKQBw=='. Resource not found. Resource https://atomicdata.dev/commits/Ony7Xa5pm3pdQHJrXIhSu+HUrVeGuBQ7FzzbzRBJTmZclPHUah1h35lRGwqn4dAlgML+KGyGSYM8WgV1AeKQBw== not found

For now I've simply created a new Resource and pointed the existing invite to there, but I don't know what has caused this.

Commits cannot be deleted by users, it is not permitted
Commits are only indexed after they are stored (or.. are they?)

A possible culprit is the get_commits_for_resource function, which uses a tpf query to find all Commits. For now I can skip over missing commits, but it still begs the question how this can happen.


Add Raspberry Pi 5 Support in meta-mender-community/meta-mender-raspberrypi

Hi,
This GitHub pull request contains patches to enable Mender on Raspberry Pi 5 using meta-raspberrypi and meta-lts-mixins (for U-Boot 2024.04). It has been tested on Raspberry Pi 4 and Raspberry Pi 5 with the following configurations:

machine raspberrypi5 with U-Boot 2024.04 with meta-lts-mixins
machine raspberrypi4-64 with U-Boot 2024.04 with meta-lts-mixins
machine raspberrypi4-64 with U-Boot 2024.01

This GitHub pull request depends on:

Support Scarthgap in meta-mender https://github.com/mendersoftware/meta-mender/pull/2103
Consolidated preparation and bump to scarthgap #379

Once GitHub pull request #379 gets merged, I will rebase this GitHub PR on top of it. I am opening it right now to get early feedback about the Raspberry Pi 5 work.
Best regards, Leon

Hi @leon-anavi, I have created the scarthgap branch. Can you rebase to it? Plus two additional remarks:

at least for now, the layer directory should be called meta-mender-raspberrypi-community
can you also add a kas file? This makes the `meta-lts-mixins´ dependency clear and easily reproducible.

Hi @TheYoctoJester,

Hi @leon-anavi, I have created the scarthgap branch. Can you rebase to it? Plus two additional remarks:

Yes, done

at least for now, the layer directory should be called meta-mender-raspberrypi-community

OK, as part  of the rebase I created sub-layer meta-mender-raspberrypi-community.

can you also add a kas file? This makes the `meta-lts-mixins´ dependency clear and easily reproducible.

Here I have a problem with the mender integration when I try to use branch scarthgap of your https://github.com/TheYoctoJester/meta-mender, aka https://github.com/mendersoftware/meta-mender/pull/2099:
root@raspberrypi5:~# mender
-sh: mender: command not found

In my local.conf I have:
# mender-full
INHERIT += "mender-full"

Is there anything special from https://github.com/TheYoctoJester/meta-mender branch scarthgap  that I am missing?
It works fine if I switch meta-mender to my GitHub pull request for scarthgap in meta-mender: https://github.com/mendersoftware/meta-mender/pull/2103
Here are more details about the layers in my setup:

OK with https://github.com/mendersoftware/meta-mender/pull/2103:

meta
meta-poky
meta-yocto-bsp       = "scarthgap:fb91a49387cfb0c8d48303bb3354325ba2a05587"
meta-oe              = "scarthgap:6819f825caf750b4deac5d8dda1b81f3380615be"
meta-raspberrypi     = "master:1879cb831f4ea3e532cb5ce9fa0f32be917e8fa3"
meta-mender-core
meta-mender-raspberrypi = "scarthgap-rpi5-support:541a14e304bad1066541303caf95fc71d6236cd3"
meta-mender-raspberrypi-community = "rpi5-master:dbd528b3b5b9124df551d237f49b40e06256ca45"
meta-lts-mixins      = "scarthgap/u-boot:66ceeebd047d7fdfc8668b300319a76da8ae257d"

FAIL with https://github.com/mendersoftware/meta-mender/pull/2099:

meta
meta-poky
meta-yocto-bsp       = "scarthgap:fb91a49387cfb0c8d48303bb3354325ba2a05587"
meta-oe              = "scarthgap:6819f825caf750b4deac5d8dda1b81f3380615be"
meta-raspberrypi     = "master:1879cb831f4ea3e532cb5ce9fa0f32be917e8fa3"
meta-mender-core
meta-mender-raspberrypi = "scarthgap:1e727c2a72bc6713a013855166eab9625b4817a7"
meta-mender-raspberrypi-community = "rpi5-master:dbd528b3b5b9124df551d237f49b40e06256ca45"
meta-lts-mixins      = "scarthgap/u-boot:66ceeebd047d7fdfc8668b300319a76da8ae257d"

Best regards, Leon

Hi @leon-anavi, that's probably because of the migration to Mender Client 4.0. The mender binary has been split into mender-auth and mender-update, so you have to check using the latter one. I have assembled the necessary information here: https://hub.mender.io/t/using-mender-client-4-0-on-yocto/6767

Hi @leon-anavi, tried to build this branch now for testing, and u-boot is being skipped:
ERROR: Nothing PROVIDES 'u-boot' u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the raspberrypi5 machine configuration. u-boot was skipped: incompatible with machine raspberrypi5 (not in COMPATIBLE_MACHINE) ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'u-boot']
As far as I can tell the layer revisions match, anything else you have in your setup?

As far as I can tell the layer revisions match, anything else you have in your setup?

This GitHub pull request contains u-boot_2024.04.bbappend that marks Raspberry Pi 5 as a compatible machine for U-Boot: https://github.com/mendersoftware/meta-mender-community/pull/380/commits/dbd528b3b5b9124df551d237f49b40e06256ca45#diff-550da7d60d61f8bf246c3ace54ca982ab13f37a9df8435f0c46f637d92ea9a02R1 Do you have this in your setup?
Best regards,
Leon

@TheYoctoJester I see recipes and patches coming with meta-mender-raspberrypi have been removed from the GitHub PR for meta-mender: https://github.com/TheYoctoJester/meta-mender/commit/9428935c278f88e3bede57fd1edcf9a8f5f991f6 What is the plan regarding these bits? Should I add them to meta-mender-raspberrypi-community as part of this GitHub pull request?
Thanks,
Leon

@leon-anavi yeah, sorry for the bad timing. The move of meta-mender-raspberrypi into meta-mender-community was discussed and decided after we had already started on the 'meta-mender-raspberrypi-communityeffort. So in summary, we will combine it :-) Its just a bit too many moving parts right now asscarthgaponmeta-mender` also needs sorting out.
I'll keep you updated!

@leon-anavi yeah, sorry for the bad timing. The move of meta-mender-raspberrypi into meta-mender-community was discussed and decided after we had already started on the 'meta-mender-raspberrypi-communityeffort. So in summary, we will combine it :-) Its just a bit too many moving parts right now asscarthgaponmeta-mender` also needs sorting out. I'll keep you updated!

OK, I rebased the patches. Now this GitHub pull request adds all required configurations in sub-layer meta-mender-raspberrypi-community, including kas configuration files for Raspberry Pi 5 which can be built with:
kas build meta-mender-community/kas/raspberrypi5.yml

I successfully tested a mender update manually by installing it with the following sequence:

Download and install the update:

mender-update install http://<IP_ADDRESS>:8000/core-image-minimal-raspberrypi5.mender

Reboot Raspberry Pi 5:

reboot

Verify the update is successful and commit it:

mender-update commit

Temporary the kas configurations use repositories containing GitHub pull requests for adding support for Yocto release scarthgap in Mender, aka the one for this GitHub PR and https://github.com/mendersoftware/meta-mender/pull/2099
@TheYoctoJester could you please review the modified version of the GitHub pull request and the kas configurations?
Best regards, Leon

Hi @leon-anavi, looks nice, also passed my test build pipeline. The only remaining concern I have at the moment is the scope of meta-lts-mixins, see also https://hub.mender.io/t/raspberry-pi-latest-u-boot-or-yocto-lts-one/6793. I'm not sure what the best and most robust way forwards for users is.
Oh, and as the meta-mender-raspberrypi layer has now been folded into it, we can remove the -community tail in this name. Want me to do it?

Hi @leon-anavi, I've pushed the last things I had in my pipeline to your branch. Can you give it a short review? If you're fine with it, I'll merge. 🎉

Hi @TheYoctoJester,

Hi @leon-anavi, I've pushed the last things I had in my pipeline to your branch. Can you give it a short review? If you're fine with it, I'll merge. 🎉

Thank you for your improvements. I had a look at the changes and they all look good to me.
Thanks, Leon


Support filtering on translation values in editTexts

This is  a feature request.

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
[x] Did you check the documentation?
[x] Did you perform a cursory search?

Description

It would be really useful if the editTexts search feature allowed searching on value alongside key
Use Case
Noticing a bad translation; requiring to look up in the code where it's generated to (in most cases it's the more secluded items that have bad translations, so just toggling language isn't a solution in those cases + they're often reported in the field (and they just have a globally set language + can't be asked for that info)
Remarks
I noticed key-based filtering is embedded quite deeply (likely due to the missing-key logic; which is a great feature too!) if you have an implementation method idea that wouldn't cause a big hit on performance I'm definitely willing to PR this.

If you switch the language to English don't should see the key instead of the translation? Because if you do then you can filter by that key.

Not if we receive a screenshot from a user of a dialog that only appears in certain cases (for example)

you can easily search by the translation in the JSON file and get the key.

Those responsible for translations don't have direct access (nor proper knowledge to handle) such files though.
I'll see how cleanly I can implement it and PR if so.
Given the current structure the best implementation method would likely be to filter by value only if no results are returned (to reduce regular load)


Can't play chess

When I want to play, it always says:

File "src/chess_zero/play_game/game_model.py", line 37, in move_by_ai
self.last_evaluation = self.last_history.values[self.last_history.action]
AttributeError: 'NoneType' object has no attribute 'values'

What should I do?

@wonderkid27
It happens because the last commit has uncommented this line for the purpose of training. Does it resolve your problem?


Multiple same scene instances in different viewport causing duplicated objects

Godot version:
3.2.3
Issue description:
In the example project there is multiple viewports so I can have multiple instances of the same scene.
The scenes _ready function will create scene instance which has kinematic body with collider, adds it to scene and starts moving it. I used randf to create the velocity vector, I am not sure exactly why it makes them appear apart but if I remove that line, the box will start moving left really fast for some reason (I assume its something to do with collisions since it didn't happen when I moved object by changing its transform.origin)
When I have both of the viewports it looks like the box is duplicated in each scene instead of one box per scene.

Here is what I see when I removed the second viewport which is as expected.

Am I doing something wrong or is this a bug?
Minimal reproduction project:
ViewportBug.zip

You are using a shared 3D World Resource. You may have different Views on this World but all your TestScene Instances are placed in the same space. What you can do is to use different "World" Resources on the Viewport's and toggle on "own_world" or you can use different visuallayers for your objects and cull_masks for the cameras so one viewport doesn't capture the content from the other viewport.

@smix8 Thanks! That indeed solved the issue. I guess this isn't a bug after all then.


Suggest predicate-based formatter in [FilteringTextInputFormatter] docs for whole string matching

Fixes #78100

Explains when not to use a FilteringTextInputFormatter.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@goderbauer rephrased some of the new docs could you take a look again?


Add the ability to pass generic mongo options

Hey all,
We run Mongo with SSL enabled, but the mongo plugin does not have the ability to pass the --ssl flag to the mongo commands. Rather than add a flag specific to ssl we followed the example from the mysql plugin and added the options parameter that allows passing any flags.
#ultimatesoftware

Thanks!


[macOS, 3.4] Fix OpenGL flickering.

Backport of #56059 for 3.4.
Remove kCGLCEMPEngine, which is causing flicker.
Disable window redraw during resize, when rendering in the separate thread.

Thanks!


[FIX] don't remove other orders if sync the current order

@GabbasovDinar Orders from other tables do not disappear, but the synchronization error appears

@Railia  this PR does not resolve the synchronization error. Thr PR solves the error of deleting orders only


CI Workflow for the End-to-End test

I'm being atypically unorthodox in the way I'm conducting this pull request, but there is a didactic reason for that.
The core of this PR is implementing the end-to-end test CI workflow (.github/workflows/e2e.yaml), that runs self-hosted on cloud VMs customized to our interest of running WSL 2 from the latest store app. That implementation itself is not straightforward, but we discussed the details already, such as why we need to control the VM through azure-cli or why we need to remotely connect to it during the execution of the tests.
Doing so revealed a challenging bug related to snapd version 2.57.4, not easily discoverable through other testing, as discussed in #309 . After fixing the snapd question, another issue was raised by the test workflow: missing language-selector-common package in the subiquity snap. That issue was partially addressed in PR #310 , while we gain time to work on a better approach. Discussing the details of that is outside of the scope of this PR.
Those pull requests intentionally brought the fixes to this branch, so you guys can appreciate all the fixes demanded by the end-to-end testing step by step and, mainly, the effects of those fixes in a timeline of CI runs, revealing broken tests being fixed one after another, proving that the test workflow works.
Here we have the interesting timeline:

Run job<PHONE_NUMBER> was broken due the snap problem. Although the logs don't clarify the cause, one can see that we don't have a server log and the client log shows a long list of attempts to connect to the server. The server never started because we couldn't find the snaps.

Run job<PHONE_NUMBER> was broken due language-selector-common package, addressed in #310

Run job<PHONE_NUMBER> is a good run after both fixes mentioned above. Line 780 of e2e/Run Tests show:

ok  	github.com/***/wsl/e2e/test-runner	212.086s

This is just a first implementation and I'm sure we can improve it further soon. For instance, right now I'm only allowing the most stable test scenario. Soon we'll mature the other already existing scenario and implement more as we get more mature with the new OOBE as a Windows application. Also, for now, only Ubuntu-Preview is being considered. Soon we'll have to make this a testing matrix to test also 22.04 LTS.
For now, I think we are good to go.

As a side note, some flakyness needs further troubleshooting related to the prefill file not being generated by the launcher. Logs from the last run show:
=== Prefill file  ====
    wsl_tester.go:50: Failed to retrieve the prefill file:
        exit status 1: cat: /var/log/prefill-system-setup.yaml: No such file or directory
    wsl_tester.go:52:

        === Server Debug Log ====
    wsl_tester.go:55: 2022-10-25 02:32:07,781 INFO systemsetup-server:[89](https://github.com/ubuntu/WSL/actions/runs/3314374925/jobs/5473825375#step:8:90) Starting System Setup server revision unknown
        2022-10-25 02:32:07,781 INFO systemsetup-server:90 Arguments passed: ['/snap/subiquity/current/lib/python3.8/site-packages/system_setup/cmd/server.py', '--tcp-port=59339', '--prefill', '/var/log/prefill-system-setup.yaml', '--autoinstall=']
        2022-10-25 02:32:07,781 ERROR systemsetup-server:95 "File /var/log/prefill-system-setup.yaml" is invalid. Option will be ignored.

Let's deal with that in another PR. This is getting too big.


Clojurescript support

Do you have a sense of how much work this is?

I doubt it's that much work, as Specter is a small library.

This is now supported in 0.6.0


chore: update dev-running docs

Codecov Report
Patch and project coverage have no change.

Comparison is base (c5cb7dc) 62.62% compared to head (7b9a919) 62.62%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2008   +/-   ##
=======================================
  Coverage   62.62%   62.62%
=======================================
  Files         141      141
  Lines       28256    28256
=======================================
  Hits        17695    17695
  Misses      10561    10561

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


grammy command can create an unbounded number of parallel network requests

If i point grammy to a set of remote VFS filepaths, it will fetch them all in parallel. We should probably bound the concurrency.
Also, I think we can increase performance a bit by using fslice rather than fstat. Since all we need is the data.

It might also at some point be nice to have grammy product a live table, so that we don't need to wait for grammy to fetch all of the data before we can see a histogram for some of the data.


feat: column support for array_append, array_prepend, array_position and array_positions

Which issue does this PR close?

Closes https://github.com/apache/arrow-datafusion/issues/6804
Rationale for this change
This is the first PR for solving the column issue.

What changes are included in this PR?
Four array functions now start to support column data:
array_append,
array_prepend,
array_position,
array_positions

Are these changes tested?
Yes

Are there any user-facing changes?
Yes

This is on my list to review, but I might not have time for it until later in the week (Wednesday) -- I am somewhat occupied with #6800  at the moment

Thanks @izveigor


Remove Rico from OpenLayers.js

A minor point, but I assume these are still in there by mistake. The other deprecated classes seem to have already been removed.

If we remove the Rico files we should also remove AnchoredBubble.js (refs #99). We should probably list in the release notes the deprecated scripts that are no longer auto-loaded by OpenLayers.js.

sorry, i was thinking that Rico and friends had been moved to deprecated.js. Perhaps we should keep them in OpenLayers.js until they are moved. Though it probably doesn't matter too much, as I can't imagine anyone uses this for anything other than testing and looking at examples.
Re the release notes, it might be a good idea to separate out the classes from the list of deprecated things, and say something like: "The following classes have been moved to deprecated.js and removed from OpenLayers.js."

@probins after a bit more thinking i think it's better to keep them in OpenLayers.js for 2.12. This is more in line with the original plan, as described in http://osdir.com/ml/openlayers-development-gis/2011-12/msg00003.html.
Can we close this issue?


Phantom tracks?

There are two tracks here that I cannot appear to open. Can you help me figure out why?

To be clear, one (probably both?) of these tracks is one that I uploaded. So I'm confused as to why it seems unavailable.

I have the same problem. Are those tracks still marked as being in "Processing" mode in your user profile? I suspect this might be the cause. The request to the server to retrieve nearby images is successful, the server just isn't returning any images, as if you had clicked miles away from any coverage.


Refactor out normalization to where it belongs

The TTS system does too much normalization. The whole SSML parsing and all related code should actually be part of the normalization process. Now parts of normalization are done here, other parts in the frontend pipeline and a load of hard coded new stuff is here that should be done in a saner way inside the normalizer project.
I'd propose to move the SSML parsing into the normalizer, there is already e.g. html processing and cleaning done.

We discussed this a bit offline.
Normalization is part of a TTS system, and future voice models might use non-normalized text as input rather than a string of phonemes.
The normalizer GrammatekNormalizer performs no* local normalization, and only synchronizes the response from the normalization service with original tokens and the byte offset in the input. It does however perform SSML parsing before passing the text over to the service, since the service has (had?) no knowledge of SSML.
I'd be happy to move the SSML parsing to somewhere else, saner or not, if we can maintain the current functionality by doing so.
This discussion will continue offline :)
* Except for the simple say-as expansions.
cc: @SmariF89


[WIP, really] Allow VM code to create tasks

In the category of "cool things we can do with the tactic monad", we can now define a tactic combinator in Lean that replaces the current goal with a lemma and proves it asynchronously in a different thread:
  def fill_shr (x : bitvec n) (i : ℕ) (fill : bool) : bitvec n :=
  bitvec.cong (by async { begin [smt] by_cases (i ≤ n), eblast end }) $
    repeat fill (min n i) ++ₜ taken (n-i) x

However I stumbled into a major issue: rb_map is not thread-safe, even with ts_vm_obj.  I think the reason is that we do not clone the comparison function, any ideas on how to solve that @leodemoura?

However I stumbled into a major issue: rb_map is not thread-safe, even with ts_vm_obj. I think the reason is that we do not clone the comparison function, any ideas on how to solve that @leodemoura?

I will try to fix this. I incorrectly assumed all vm_external objects did not contain nested vm_objs. I forgot rb_map :(

It seems to work pretty well.  Even the info manager and show-goal work transparently!


Update index.html

fix typo and add newline (newline was done by git, not me)

A newline at the end of files is standard convention and good practice anyway. Thanks for spotting the typo! Merging.


nuxt/bridge - minimal codesandbox does not start

Environment
Codesandbox
Reproduction
As per the minimal reproduction, the v2-bridge-codesandbox does not load.
Describe the bug
Codesandbox does not start and gives 502: Bad Gateway
Additional context
No response
Logs
If you fork and try to force it to load again you get logs like this
> Sandbox Container: Sandbox 7pwk9l started
yarn run v1.22.19
$ nuxt dev
/bin/sh: 1: nuxt: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.19
$ nuxt dev
/bin/sh: 1: nuxt: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.19
$ nuxt dev
/bin/sh: 1: nuxt: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.19

rm -rf node_modules
rm yarn.lock
rm -rf .nuxt
yarn cache clean -f
yarn install

@neversaynever88 - I'm not sure I understand. This is a fresh codesandbox and it fails to start. I'm guessing an explicit nuxt dependency is needed to be added as a dependency to it, but I just wanted to check. Either way the fixed codesandbox should be linked to the minimal reproduction docs.

Fixed at https://github.com/nuxt/starter/pull/524
Until https://github.com/nuxt/bridge/issues/918 resolves the issue, you can change nuxi: latest to nuxi: 3.8.4 to start.


General: Remove gender

Allow any gender to select torso options

This pull request was fulfilled with the latest few commits in the ToonCreatorExpansion branch.
As a result, I will be closing this pull request.


Delete icon can hardly be seen due to low contrast

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.901
Where did you get the app from?
Other
Android version
10
Device model
Honor View 20
Steps to reproduce
Open received mail
Expected behavior
the icons at top should be see clearly
Actual behavior
very often, the delete icon (trashbin) can hardly be seen due to low contrast.
This does not happen always, but very often. I could not find the conditions when it occurs,
To come back to normal behaviour set the dive to dark mode and view the message again.
The reset the device dark mode. It seem to continue as expected.

Logs
No response

Another way to return to "Normal":
terminate k9mail and clear it from memory (Swipe)
restart k9mail

I have seen a red trash in today. Otherwise the same behavior as above.
I am quite sure I did not see this bug in versions up to 6.803

This is probably caused by the MessageListSwipeCallback setting a tint on the drawables provided by SwipeResourceProvider without calling mutate() first.


Fix/issue 35 + linter fixes

Fixes #35
Description of the change

It turns out unauthenticated URLs starting with git:// is no longer supported by GitHub, so I had to update the requirements file accordingly to a supported format. I hit this when I started to work on a environment from scratch.
I also took the opportunity to apply fix some linter errors that were failing on tox, so now tox in the CI is supposed to be passing again.

Release notes

N/A (only development changes)

Hi @viniarck can you please clarify which specific change was the fix for issue #35? Since there was a lot of changes, I must admit I got lost.


Remove upper bound on dlt dependency in Kafka source

Tell us what you do here

improving, documenting, or customizing an existing source (please link an issue or describe below)

Short description
Unpin the dlt dependency for the Kafka source.
Related Issues

Fixes #414

Additional Context

@rudolfix, most likely I took it from another source, as an example. I guess there will be no problems if we drop the bound.


MTLCommandBufferErrorDeviceRemoved not available on macCatalyst

MoltenVK/MoltenVK/MoltenVK/GPUObjects/MVKQueue.mm:312:10: error:
'MTLCommandBufferErrorDeviceRemoved' is unavailable: not available on macCatalyst
case MTLCommandBufferErrorDeviceRemoved:
when doing a make all build.
System: Apple M1 on macOS 11.0.1, with Xcode 12.2

Fixed in PR #1177.


Update rebar3 hack to use shell:start_interactive arities from Erlang 26

After pushing the hack detailed in the following ticket:

#79

@rvirding providing some lovely insight from his recent dive into the new shell features offered by Erlang 26. In particular, the various arities and their supported args for shell:start_interactive.
If this works as expected, I will create a rebar3 ticket to improve the interactive handling for custom shells in rebar3. Additionally, this work will serve as a spike to inform the following LFE ticket:

https://github.com/lfe/lfe/issues/480

This worked great. Will push out a new release shortly.

After successfully testing this, I opened a ticket to use this approach to fix the source of the issue in rebar3:

https://github.com/erlang/rebar3/issues/2817


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112106

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118036

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118903

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118936

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119697


Chained stack modifiers don't actually operate on the stack

Vyxal, 12 bytes
3 4₌≬+:_≬+:_

Try it Online!
for example
This could be quite hard to fix, I don't really understand the internal structure of Vyxal's modifiers.

Speaking of which, pretty sure modifier grouping isn't documented.

here's the thing:
3 4₌λ2|+:_;λ2|+:_;

does what I think you intend.
but so should
3 4₌‡≬+:_d‡≬+:_d

but it doesn't

@chunkybanana about my above remark - what do you think?

I agree that that should just push the function, not try and call it.
Also, would setting the arity to len(stack) dynamically work?

You don't need to set it to len(stack)) - setting it to -1 should automatically use stack if that was actually implemented.

Also, would setting the arity to len(stack) dynamically work?

On second thought, no, it wouldn't work. Because what happens if you try something like ₌+- on an empty stack with two inputs? len(stack) will set the arity to 0 and not pop any inputs despite the fact that there needs to be stuff popped.


Android problem: DexException: Multiple dex files...

Hello,
Thank you for this module.
I have successfully setup on the iOS, but I keep on getting this error while compiling for android.
Unknown source file : com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/iid/MessengerCompat$1;

See https://github.com/bamlab/react-native-image-resizer/issues/15. This project had a similar issue and a fix was suggested. @beeant please confirm if it works for you.

I'm having the same issue using this lib with https://github.com/zo0r/react-native-push-notification
I think both libs depends on google play services is the reason to cause this problem

I'm having the same issue with RN29. I have no idea how to fix this

have you tried cleaning the build?

as react-native-push-notification and maybe other packages depends on google play services we need match the google play services in this packages
you can run
./gradlew -q app:dependencies

to discover which packages depends on google play services, and which version they r using
them u can force them to use a specific version
dependencies {
   compile ('com.google.android.gms:play-services-gcm:9.2.0') {
        force = true;
   }
}

@sibelius can you specify which file needs that change?
also react-native-push-notification relies on gms 8.+, could that be an issue?

u should change android/app/build.gradle
and react-native-push-notification relies on gms 8.+ but u can force another version as above

cool @beeant @rturk  does this solve your issue?

@evollu after much work I've managed to make my app work. Thanks.
Looks like latest rnpm link still a little bugged and is not correctly importing packages.

cool.

@evollu Hello, I have a similar conflict with "react-native-intercom" but I am not sure what needs to be done there. Should I do something there? Or here?

<EMAIL_ADDRESS>


Enhanced Orthogonal Persistence (64-Bit with Pointer Compression)

Note: This requires adjustments of the IC runtime and execution layers - the PR is thus not yet ready to be merged.
Enhanced Orthogonal Persistence (64-Bit with Pointer Compression)
This implements the vision of enhanced orthogonal persistence in Motoko that combines:

Stable heap: Persisting the program main memory across canister upgrades.
64-bit heap with pointer compression: Supporting 32GB of main memory without doubling pointers sizes.

As a result, the use of secondary storage (explicit stable memory, dedicated stable data structures, DB-like storage abstractions) will no longer be necessary: Motoko developers can directly work on their normal object-oriented program structures that are automatically persisted and retained across program version changes.
Advantages
Compared to the existing orthogonal persistence in Motoko, this design offers:

Instantenous upgrades: New program versions simply resume on the existing main memory and have access to the memory-compatible data.
Scalable upgrades: The upgrade mechanism scales with larger heaps and in contrast to serialization, does not hit IC instruction limits.

Compared to the explicit use of stable memory, this design improves:

Simplicity: Developers do not need to deal with explicit stable memory.
Performance: No copying to and from the separate stable memory is necessary.

Design
The stable heap is based on the following main properties:

Extension of the IC to retain main memory on upgrades.
A long-term memory layout that is invariant to new compiled program versions.
A fast memory compatibility check performed on each canister upgrade.

IC Extension
The necessary IC extensions are implemented in a separate PR: https://github.com/dfinity/ic/pull/143
This PR is based on these extensions.
Memory Layout
In a co-design between the compiler and the runtime system, the main memory is arranged in the following structure, invariant of the compiled program version:

Lower 4MB: Rust call stack.
Space between 4MB and 4.5MB: Limited reserved space Wasm data segments, only used for the Motoko runtime system.
Between 4.5MB and 5MB: Persistent metadata.
Thereafter: Dynamic heap space. Fix start address at 5MB.

Compact Pointers
By aligning objects to 16 bytes, object addresses have the lowest 4 bits zero. One bit is spent for pointer tagging (skewing), such that 3 free bits can be used to extend the addressable space by factor of 2**3 = 8, resulting in 32GB.
A 64-bit address a in the range of 32GB is encoded as a compact pointer a >> 3 - 1 of 32-bit width.
The compact pointer p is again decoded to a 64-bit address (p + 1) << 3.
The alignment to 16 bytes increases internal fragmentation (potential padding inside the object). However, the internal fragmentation overhead is expected to  less than generally extending the word size to 64-bit. Without alignment, the minimum object size is 12 bytes (except for the Null singleton that fits into 8 bytes).
Persistent Metadata
The persistent metadata describes all anchor information for the program to resume after an upgrade.
More specifically, it comprises:

A stable heap version that allows evolving the persistent memory layout in the future.
The stable subset of the main actor, containing all stable variables declared in the main actor.
A descriptor of the stable static types to check memory compatibility on upgrades.
The reference to the null singleton object.
The runtime state of the garbage collector, including the dynamic heap metadata and memory statistics.
A reserve for future metadata extensions.

Compatibility Check
Upgrades are only permitted if the new program version is compatible to the old version, such that the runtime system guarantees a compatible memory structure.
Compatible changes for immutable types are equivalent to the allowed Motoko subtype relation, e.g.

Adding or removing actor fields.
Removing object fields.
Adding variant fields.
Nat to Int.
Shared function parameter contravariance and return type covariance.

The existing IDL-subtype functionality is reused with some adjustments to check memory compatibility: The compiler generates the type descriptor, a type table, that is recorded in the persistent metadata. Upon an upgrade, the new type descriptor is compared against the existing type descriptor, and the upgrade only succeeds for compatible changes.
This compatibility check serves as an additional safety measure on top of the DFX Candid subtype check that can be bypassed by users (when ignoring a warning). Moreoever, the memory compatibility rules is in some aspects different to the Candid sub-type check:

Types cannot be made optional.
Mutable types (aliases) are supported with type invariance.

Garbage Collection
The implementation focuses on the incremental GC and abandons the other GCs because the GCs use different memory layouts. For example, the incremental GC uses a partitioned heap with objects carrying a forwarding pointer.
The incremental GC is chosen because it is designed to scale on large heaps and the stable heap design also aims to increase scalability.
The garbage collection state needs to be persisted and retained across upgrades. This is because the GC may not yet be completed at the time of an upgrade, such that object forwarding is still in use. The partition table is stored as part of the GC state.
This is because the GC may not yet be completed at the time of an upgrade, such that object forwarding is still in use. The partition table is stored as part of the GC state.
The garbage collector uses two kinds of roots:

Persistent roots: These refer to root objects that need to survive canister upgrades.
Transient roots: These cover additional roots that are only valid in a specific version of a program and are discarded on an upgrade.

The persistent roots are registered in the persistent metadata and comprise:

All stable variables of the main actor, only stored during an upgrade.
The null singleton object.
The stable type table.

The transient roots are referenced by the Wasm data segments and comprise:

All canister variables of the current version, including flexible variables.

Main Actor
On an upgrade, the main actor is recreated and existing stable variables are recovered from the persistent root.
The remaining actor variables, the flexible fields as well as new stable variables, are (re)initialized.
As a result, the GC can collect unreachable flexible objects of previous canister versions.
Unused stable variables of former versions can also be reclaimed by the GC.
No Static Heap
The static heap is abandoned and former static objects need to be allocated in the dynamic heap.
This is because these objects may also need to survive upgrades and must not be not overwritten by new data segments.
The incremental GC also operates on these objects, meaning that forwarding pointer resolution is also necessary for these objects.
The runtime systems avoids any global Wasm variables for state that needs to be preserved on upgrades.
Instead, such global runtime state is stored in the persistent metadata.
Sharing optimization (pooling) is possible for compile-time-known objects, see below.
Wasm Data Segments
Only passive Wasm data segments are used by the compiler and runtime system. In contrast to ordinary active data segments, passive segments can be explicitly loaded to a dynamic address.
This simplifies two aspects:

The generated Motoko code can contain arbitrarily large data segments which can loaded to dynamic heap when needed.
The IC can simply retain the main memory on an upgrade without needing to patch the active data segments of the new program version to the persistent memory.

However, more specific handling is required for the Rust-implemented runtime system:
The Rust-generated active data segments of the runtime system is changed to passive and loaded to the expected static address at the program start (canister initialization and upgrade).
The location and size of the RTS data segments is therefore limited to a defined reserve, see above.
This is acceptable because the RTS only uses small size for data segments (e.g. 54KB) that is independent of the compiled Motoko program.
Null Singleton
As an optimization, the top-level `null`` singleton is allocated once in the dynamic heap and remembered in the persistent metadata across upgrades.
This is necessary to implement null checks by pointer comparison (however, by first resolving pointer forwarding before the comparison).
The null singleton needs to be part of the persistent root set.
Migration Path
When migrating from the old serialization-based stabilization to the new stable heap, the old data is deserialized one last time from stable memory and then placed in the new stable heap layout.
Once operating on the stable heap, the system prevents downgrade attempts to the old serialization-based persistence.
Old Stable Memory
The old stable memory remains equally accessible as secondary memory with the new support.
Current Limitations

Optimization of statically known objects: Currently, compile-time-known objects are always dynamically allocated. For an improved performance and size, they could be shared in the dynamic heap by remembering them in an additional pool table. The pool table needs to be registered as a transient GC root and recreated on canister upgrades.
The compact pointer representation only allows 32 GB. Moreover, the GC is also limited to 32 GB because it uses a static partition table.
The floating point display format differs in Wasm64 for special values, e.g. nan becomes NaN. There is currently no support for hexadecimal floating point text formatting.
Workaround for Rust needed to build PIC (position-independent code) libraries. Explicit use of emscripten via LLVM IR.
ic-wasm would need to be extended to support memory64 and passive data segments. The Wasm optimizations in test/bench are thus currently deactivated.
The Wasm profiler is no longer applicable because the underlying parity-wasm crate seems deprecated. A re-implementation of the profiler would be needed.

Related PRs

IC support for enhanced orthogonal persistence: https://github.com/dfinity/ic/pull/143
IC deterministic working set limit for 64-bit main memory: https://github.com/luc-blaeser/ic/pull/1
Motoko base library 64-bit support: https://github.com/dfinity/motoko-base/pull/589
Full-fledged 64-bit enhanced orthogonal persistence: https://github.com/dfinity/motoko/pull/4225

Underlying partial implementations:

32-bit enhanced orthogonal persistence: https://github.com/dfinity/motoko/pull/4193
64-bit support for Motoko (transient heap): https://github.com/dfinity/motoko/pull/4136

This was an experiment. It is only a compromise solution. Probably, for ease of maintenance, we should go for only two modes, the classical support and new full-fledged 64-bit enhanced orthogonal persistence.


Viro & NativeBase

Environment
Please provide the following information about your environment:

Development OS: Mac & Windows
Device OS & Version: Android 8.0.0 & iOS 11.4.1
Version: ViroReact 2.10.0 and React Native 0.55.1
Device(s): iOS & Android

Description
I am trying to use NativeBase along side ViroReact.
I have created a ReactViro app using the instruction outlined in the documentation.
I then install Native Base using the following commands:
npm install native-base --save and react-native link
I then run: npm start
Sample code
import React, { Component } from 'react';

import { CheckBox } from 'native-base';

export default class ViroSample extends Component {
  render() {
    return <CheckBox />;
  }
}

module.exports = ViroSample

Output
Once I load the App in the Viro Media's Testbed, I get the following errors:
iOS: Unrecognized font family 'Ionicons'
Android: App renders a Chinese character instead of the icon.

Hi @stu236,
Native base is a custom native module so it won't work from the Testbed app. You'll need to create a iOS or Android Studio project and install native base into that project. This is the only way to use native modules like Native base with Viro React.
Here's how you do that with iOS XCode: https://docs.viromedia.com/docs/starting-a-new-viro-project-1
Here's how you do that with Android Studio: https://docs.viromedia.com/docs/installing-viro-android
Let us know if this makes sense or if you have any more questions. Thanks!

Hey, meant to comment earlier.
These instructions worked great and all works well.
Thanks!


Updated the README.md by changing the yarn commands

I have changed all the yarn commands that are written as heading into a code snippet

They're written as emphasized code snippets so it can be clearly read and understood. Is there any benefit in converting them into smaller code-snippets?

Actually there was an issue regarding this that's why I changed it, and the possible reason could be like it was looking very odd in capital.  So changing it would give it a more clean and professional look.

It looking odd is a subjective opinion. As of now, it is clean and clear and has no issues with legibility. Unless you can find any guidelines/rules regarding or actual problematic issues, we'd like to keep it as is.

sure...I would look for such issues


Add new tables, new data and queries using JOIN

Request Review for Pull Request
In this milestone I have:
- Created new tables for visits, vets, and specialization
- Add correct data to each of the new tables.
Queries
- Who was the last animal seen by William Tatcher?

- How many different animals did Stephanie Mendez see?

- List all vets and their specialties, including vets with no specialties.

- List all animals that visited Stephanie Mendez between April 1st and August 30th, 2020.

- What animal has the most visits to vets?

- Who was Maisy Smith's first visit?

- Details for most recent visit: animal information, vet information, and date of visit.

- How many visits were with a vet that did not specialize in that animal's species?

- What specialty should Maisy Smith consider getting? Look for the species she gets the
most.

Please, let me know if there's anything else I should add to my project.
Thank you.
Kind regards,
Santiago.

Thank you for your time and attention. Have a great weekend.


OCPCLOUD-2565: Featuregate implementation

This change:

Updates the MAO, to bring in new changes to the Machine Reconciler.
Reads in feature gates from flags, passing them to the reconciler.

Running the binary without passing the --feature-gates flag will result in the feature gates initialising as follows:
I0812 17:36:32.555187    1120 main.go:154] Initializing feature gates: AllAlpha=true|false (ALPHA - default=false), AllBeta=true|false (BETA - default=false), MachineAPIMigration=true|false (ALPHA - default=false)
I0812 17:36:32.555275    1120 main.go:159] FeatureGateMachineAPIMigration initialised: false

Note that any feature gates that are GA will not be printed in the help text, but can still be set by flags.

/retest

/retest

/retest

/retest
CI infra issues

/retest

The /e2e-openstack-nfv-intel job is failing due to sriov-network-operator not installing. This has been permafailing for a while, so we can ignore the failure.

/approve
/lgtm


[Bug] Update DeleteAccounts

Use RemoveAccount to be consistent with other libraries
Update paramaters to get rid of envAliases[]. User should not have to pass this in. Might also consider using an Account object instead of homeAccountId.
RemoveAccounts should remove the account and any associated accessTokens, refreshTokens, and IdTokens. In it's current implementation, I think it's only removing accounts.
Expose RemoveAccount on clientApplication.

Resolved in #215


Inconsistent operations on paths containing characters outside of range

Holla,
Using hadoop-manta through Kafka Connect HDFS discloses a strange behavior.
Paths that contain characters that are outside of the ones allowed by Manta are created without warning. The out-of-range characters get escaped.
Ex.: ~~/stor/project/topics/+tmp/topic_name/partition=0 -> ~~/stor/project/topics/%2Btmp/topic_name/partition%3D0 (which is okay, I guess)
The problem arises when kafka-connect-hdfs tries to read back from there: Manta returns a 404.
[1:statusLine=HTTP/1.1 404 Not Found]
[2:serverCode=DirectoryDoesNotExist]
[3:server_message=/<account>/stor/project/topics/+tmp/topic_name/partition=0 does not exist]

Looks like the conversion happens silently on the Manta side, on creation. (I might be wrong I did not dig yet.)
Should:

hadoop-manta escape the path somewhere like here before even involving Manta
Manta be responsible and either: prevent creation of such items OR convert consistently

Please let me know if this is a real issue or/and if I am getting something wrong.
Regards,
Marc

My gut instinct is that this issue is due to this problem with the Manta SDK: https://github.com/joyent/java-manta/pull/234
It should be fixed in the upcoming release of the Manta SDK.

Fixed in 54b5cdfd21de1fc4ad7d51431621123d97622f5b


Return from TryMetabolize early if there are no reagents to process

About the PR
TryMetabolize copied and shuffled the reagents list before processing them, even when there were no reagents in that list. Now it does an early return instead.
Screenshots

Changelog

didnt think this would still have an impact with an empty list tbh

I'm not totally sure it does. It showed up on the trace as a huge chunk of TryMetabolize though, and I can't think of an explanation for that other than the reagent list almost always being empty (given how much stuff happens when it's not).


Update to web-config - Current Version

This change will point the GP2040 web-config towards the new GP2040-CE repo and pull the current version information from there.

LGTM, just nix the blank lines at the end.


Prevent invalid access to ParameterView. Fixes #12622

ParameterView provides a view over a RenderTreeFrame array. It's what we pass into components' SetParametersAsync lifecycle method so they can update themselves.
However, the underlying storage comes from a shared pool, so it's vital that people don't hold onto references of it and then start reading from it at an arbitrary time in the future. To enforce this rule, this PR makes it throw if you try to read from it after the end of its safe lifetime.
This would have been really trivial if ParameterView was a class, as we could have just mutated it to say "you're disposed now". But it's not - it's a readonly struct - so the only way it can know about its own expiry is by holding a reference to a reference-typed thing that can mutate when expiry should happen.
So, the implementation here is putting a "version"-type field on RenderBatchBuilder that changes after every synchronous render-and-diff operation. This means as soon as you yield the thread from a lifecycle method, the ParameterView becomes electrified. You can't read from it either asynchronously later in the same method, or arbitrarily in the future if you store the reference on your component class.

Random build failures

This change discovered that one of our Mvc.ViewFeatures tests was holding ParameterView references in an unsafe way: https://github.com/aspnet/AspNetCore/pull/14541/commits/c1153f7706d1fdca5d8f3dfb38716b4799a3a902


Fix #778: label overlapping problem for parallel edges (self-loop edges included)

I came into the same problem that mentioned in #778. This overlapping issue is fixed by adding count information to the plugin sigma.canvas.edges.labels.curve.js. The comparison is shown below.
Also, I modified the example file examples/parallel-edges.html to show the result.
Edges between two nodes:
Before:

After:

Edges between self-loop nodes:
Before:

After:

This seems good to me. I’ll check this at the beginning of the week. Ping me if I forget.

Any progress with the code review ;)

./idea is the folder created by the IDE Webstorm. I'll modify my pull request.

Updated!

Yes. In sigma.js/plugins/sigma.renderers.parallelEdges/utils.js, the functions are overwritten with the last argument.

Fair enough. Merging now.


VAC was unable to verify game session

Got patched

works for me,  also this error can happen normally without using any cheat..
First do you still get the error without using the bypass loader,
Second what cheat are you using with the bypass loader,
Third what dll injector with that cheat,
Fourth make sure you look at this (https://support.steampowered.com/kb_article.php?ref=2117-ILZV-2837) as it could have absolutely nothing to do with the bypass loader and/or cheat,
And last try rebooting, opening steam as administrator, verifying game files, making sure that the programs listed in the link are not installed on your computer, that your using windows, that your not running csgo through a virtual desktop, and that you reboot again as rebooting windows is one of the best fix for anything.
Hopefully this helped...


Create a GitHub issue template

There should be a simple way to create an issue ticket template that prefills issue tickets upon creation

Not doing this


Build error

npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.0.0
npm ERR! npm  v2.14.2
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the pty.js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls pty.js
npm ERR! There is likely additional logging output above.

https://yadi.sk/i/TdoRvlQ-j6Hxw

tried sudo?

@Voyga : I've tried

It looks like you are using Node v4.0, it could cause unexpected issues with node-gyp. Try to downgrade to v0.12.7

Actually it is supposed to work with node v4. Try rm -rf node_modules && npm install

You can also try to remove the ~/.node-gyp directory.

After I removed gyp and modules directories, the problem disappeared.
rm -rf ~/.node.gyp && rm -rf node_modules && npm install

Thanks all,
I deleted ~/.node-gyp,  node_modules and reinstalled successfully. Must have Xcode (make) to build applications

Please close this Issue


Item internationalization

Coverage decreased (-0.08%) to 94.84% when pulling a852e88954070c6dd6c4fe920263f6f06d7b8f54 on item-internationalization into 4134ae0851df0c3499b3fd153ed662cfadb63267 on master.

Coverage remained the same at 94.92% when pulling f94da8e084c3a2c152ad7579bcf3a6aabb11d89d on item-internationalization into 4134ae0851df0c3499b3fd153ed662cfadb63267 on master.


implement notification lifecycle management in the protocol

Is your feature request related to a problem? Please describe.
Right now managing the life cycle of notification is partly done in the protocol and partly in the apps. Idea is to take care of the complete life cycle in the.
Describe the solution you'd like
Manage the life cycle in the protocol
Describe alternatives you've considered
Alternative would be to manage the lifecycle in the app
Additional context

@VJag please add the details for this enhancement request

Is this a duplicate of #546 ?

@VJag @murali-shris can we close this due to duplication?

Duplicate of https://github.com/atsign-foundation/at_server/issues/546

Re-opening as now that I look more closely I see this was created as one of the tasks in #546, and it hasn't been done yet.


TableGet operation

Focus of changes
This change adds the TableGet method, which is defined in the REST API docs here: https://docs.microsoft.com/en-us/rest/api/storageservices/addressing-table-service-resources#resource-uri-syntax
To return a single table, name that table within the Tables collection, as follows:
https://myaccount.table.core.windows.net/Tables('MyTable')

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Can you please fix the CI? Just a handful to clean up https://github.com/Azure/azure-rest-api-specs/pull/15852/checks?check_run_id=3464738929

None of the existing example conform to the checks that got flagged, from what I can tell. Is there an example that you are aware of that I could refer to to fix this?

https://github.com/Azure/azure-rest-api-specs/blob/7fa8283a875ba7823fd1e27b545b4cd2201ba1f5/specification/cosmos-db/data-plane/Microsoft.Tables/preview/2019-02-02/examples/TableDelete.json
So probably something like this.
{
  "parameters": {
    "x-ms-version": "2019-02-02",
    "DataServiceVersion": "3.0",
    "table": "mytable",
    "url": "myaccount.table.core.windows.net"
  },
  "responses": {
    "200": {},
    "404": {}
  }
}

Can you please fix the CI? Just a handful to clean up https://github.com/Azure/azure-rest-api-specs/pull/15852/checks?check_run_id=3464738929

I think they are all addressed now - the remaining one (https://github.com/Azure/azure-rest-api-specs/pull/15852/checks?check_run_id=3797201250) is due to the previous mis-naming of the Table-Get example.


Add unit tests for the new syntax infrastructure

Hi!
Can you please add description? So I can implement this.

Closing as no customers complained about this.


How to write entity to parcel with all its children (one-to-many list) ?

I'm looking for ability to keep in parcel entity with its children. I have a case when I don't need to insert record in the database, but I have to keep it in RAM until user decides to save all in persistent storage.

~You don't need a Parcelable for in-memory storage. Just put it in any variable in any class you have access to and pick it up later.~
Put it in the database along with the rest and flag it as draft with a custom column. Something like Gmail drafts. The message is stored in DB but can be dismissed or sent later.
Saved state is limited by 1MB for an Activity. That saved state includes fragments. Don't abuse it to store big data.

Thank you for your answer. I'd like to transmit entities between activities inside of Bundle objects for better performance. Also I don't want to mix buiseness logic with service in the same entity. And finally I have a simple data that don't need to be drafted or something, it simply have to be saved or not.

Hi you can do this by saving the entity and the list of one-to-many children separately, and rebuilding the hierarchy on deserializing. Parcelable is not designed to store objects that contains cycles or complex hierarchies, hence why the built in support is just the flat columns of the entity.


vscode.executeDocumentSymbolProvider missing children. Returns SymbolInformation[] rather than DocumentSymbol[]

Currently the vscode.executeDocumentSymbolProvider returns instances of SymbolInformation rather than the newer DocumentSymbol. The problem with that is the missing children property.
This is a deliberate duplicate of https://github.com/microsoft/vscode/issues/57984. Sorry about that but that issue is closed for comments and I'm still facing the same issue two years later.
My goal is to get the full symbol tree exactly as shown on the left panel outline.
Steps to Reproduce:

Boot the template Typescript extension with yo and slightly modify extension.ts:

import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) {
  console.log('Congratulations, your extension "sandbox" is now active!');

  let disposable = vscode.commands.registerCommand('sandbox.helloWorld', () => {
    vscode.window.showInformationMessage('Hello World from sandbox!');
  });
  context.subscriptions.push(disposable);

  //added code
  const getSymbols = async () => {
    const docSymbols = await vscode.commands.executeCommand(
      'vscode.executeDocumentSymbolProvider',
      vscode.window.activeTextEditor?.document.uri
    );
    console.log('Document Symbols:', docSymbols);
  };
  getSymbols()
}

export function deactivate() {}

Run the extension.
On the Extension Development Host window, open that same extension.ts file.
Activate the extension: ctrl+shift+p > > Hello World
Inspect the console / debug console. Would expect to get full object tree just like in the outline:

Instead it logs only the top-level symbols with no children.

Document Symbols:
extension.js:25
Array[2]
 0:Object
  name:"activate"
  kind:"Function"
  location:Object
  containerName:""
 1:Object
  name:"deactivate"
  kind:"Function"
  location:Object
  containerName:""

VSCode Version: 1.48
OS Version: Win10

OK, I just found https://github.com/microsoft/vscode/issues/58793 and it seems if I cast the object to DocumentSymbol I can actually access the children prop, even though it remains hidden.
  const getSymbols = async () => {
    const docSymbols = await vscode.commands.executeCommand(
      'vscode.executeDocumentSymbolProvider',
      vscode.window.activeTextEditor?.document.uri
    ) as vscode.DocumentSymbol[];
    console.log('Document Symbols:', docSymbols); // children prop won't show
    console.log(docSymbols[0].children); // but they exist!
  };
  getSymbols()


fix: wip try to fix broken CircleCI

#8012  👈
master

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

Join @fcarreiro and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

proof_construction_time_sha256_100_ms (16): 6,599 (+21%)
proof_construction_time_sha256_30_ms (16): 1,808 (+28%)
avm_simulation_time_ms (Token:mint_public): 42.5 (-40%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 69.5 (+72%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,769
1,552 (-1%)
704 (-1%)
743 (+1%)
762 (-1%)

proof_construction_time_sha256_30_ms
11,960 (+1%)
3,250 (+2%)
:warning: 1,808 (+28%)
1,626 (+11%)
1,552 (+5%)

proof_construction_time_sha256_100_ms
45,377
12,090 (+2%)
:warning: 6,599 (+21%)
5,968 (+10%)
5,659 (+5%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0 (-2%)
90.0 (+3%)

proof_construction_time_poseidon_hash_30_ms
1,529
420
202
221 (-3%)
266 (-1%)

proof_construction_time_poseidon_hash_100_ms
5,648
1,514
674
727 (-1%)
747 (+1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,324
7,844
14,852

l1_rollup_calldata_gas
49,708
92,450
177,692

l1_rollup_execution_gas
1,294,371
2,042,081
3,869,362

l2_block_processing_time_in_ms
255 (-3%)
437 (-1%)
802 (-2%)

l2_block_building_time_in_ms
9,282 (-1%)
18,243 (+1%)
35,997 (-1%)

l2_block_rollup_simulation_time_in_ms
9,282 (-1%)
18,243 (+1%)
35,997 (-1%)

l2_block_public_tx_process_time_in_ms
7,822
16,674 (+1%)
34,430 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
2,858 (-3%)
3,808

node_database_size_in_bytes
12,660,816
16,707,664

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
53.2 (-2%)
8,139

FeeJuice:set_portal
10.1 (+4%)
2,362

Token:constructor
82.4 (-1%)
31,107

FPC:constructor
53.8 (-2%)
22,380

FeeJuice:mint_public
37.8 (-19%)
6,150

Token:mint_public
:warning: 42.5 (-40%)
11,720

Token:assert_minter_and_mint
:warning: 69.5 (+72%)
8,028

AuthRegistry:set_authorized
35.7 (-22%)
4,537

FPC:prepare_fee
229 (-4%)
8,812

Token:transfer_public
34.3 (-15%)
47,374

FPC:pay_refund
55.0 (-18%)
12,114

Benchmarking:increment_balance
973
7,450

Token:_increase_public_balance
39.2 (-1%)
8,960

FPC:pay_refund_with_shielded_rebate
66.6 (+2%)
12,663

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.165

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.15 (-1%)
3.79 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.111 (-1%)
0.107 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.4 (-2%)
17.7 (-5%)
30.6 (-3%)
58.6
112 (-3%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.110 (-1%)
0.103 (-5%)
0.0995 (-3%)
0.101
0.100 (-3%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.2 (-2%)
25.5 (-1%)
43.2 (-3%)
81.6
159 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.108 (-2%)
0.103 (-2%)
0.104 (-3%)
0.101 (-1%)
0.100 (-1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.2 (-2%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
132
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.104 (-1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
64,779
668,997

Transaction size based on fee payment method
| Metric |  |
| - |  |


Added delete and filelist examples

Added delete and list file methods to the example section of the readme

Cheers :)


Vaultwarden update

Please verify that you have read and understood the guidelines.
yes
A clear and concise description of the issue.
| Updating VaultWarden to 1.32.5 (Patience)
[ERROR] in line 87: exit code 0: while executing command cargo build --features "sqlite,mysql,postgresql" --release &> /dev/null
What settings are you currently utilizing?
Default Settings
Which Linux distribution are you employing?
Debian 12
If relevant, including screenshots or a code block can be helpful in clarifying the issue.
No response
Please provide detailed steps to reproduce the issue.
Launch .sh script to update version.
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/vaultwarden.sh)"

Any update on this one?

I am not able to recreate this issue, update worked fine here. Could this be related to https://github.com/community-scripts/ProxmoxVE/issues/236 ? Do you have enough resources allocated to the LXC? 4 CPU cores and 6GB RAM minimum. Do you have enough storage?

6 vCPU
7GB RAM
11.06 GiB used of 11.71 GiB
Disk could be the problem... but cannot understand how can vaultwarden use 11GiB...

6 vCPU
7GB RAM
11.06 GiB used of 11.71 GiB
Disk could be the problem... but cannot understand how can vaultwarden use 11GiB...

Thats an Problem.
Vaultwarden on GNU Systems use many storage, the most of this are from the Cargo Builds.

Feel free to investigate the disk usage and report back if something is wrong

root@vaultwarden:~# du -h | sort -hr | head -n 30
7.7G    .
4.9G    ./.rustup/toolchains
4.9G    ./.rustup
1.9G    ./.cargo/registry
1.9G    ./.cargo
1.1G    ./.cargo/registry/src
936M    ./vaultwarden
922M    ./vaultwarden/target/release
922M    ./vaultwarden/target
854M    ./vaultwarden/target/release/deps
759M    ./.cargo/registry/src/index.crates.io-6f17d22bba15001f
617M    ./.cargo/registry/index
594M    ./.cargo/registry/index/github.com-1ecc6299db9ec823
576M    ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git/objects/pack
576M    ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git/objects
576M    ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git
570M    ./.rustup/toolchains/1.72.0-x86_64-unknown-linux-gnu
525M    ./.rustup/toolchains/1.82.0-x86_64-unknown-linux-gnu
512M    ./.rustup/toolchains/1.67.0-x86_64-unknown-linux-gnu
506M    ./.rustup/toolchains/1.69.0-x86_64-unknown-linux-gnu
505M    ./.rustup/toolchains/1.75.0-x86_64-unknown-linux-gnu
487M    ./.rustup/toolchains/1.80.1-x86_64-unknown-linux-gnu
480M    ./.rustup/toolchains/1.79.0-x86_64-unknown-linux-gnu
479M    ./.rustup/toolchains/1.72.0-x86_64-unknown-linux-gnu/lib
471M    ./.rustup/toolchains/stable-x86_64-unknown-linux-gnu
471M    ./.rustup/toolchains/1.65.0-x86_64-unknown-linux-gnu
470M    ./.rustup/toolchains/1.77.0-x86_64-unknown-linux-gnu
458M    ./.rustup/toolchains/1.67.0-x86_64-unknown-linux-gnu/lib
452M    ./.rustup/toolchains/1.69.0-x86_64-unknown-linux-gnu/lib
449M    ./.rustup/toolchains/1.82.0-x86_64-unknown-linux-gnu/lib

root@vaultwarden:~# rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /root/.rustup
installed toolchains
stable-x86_64-unknown-linux-gnu (default)
1.65.0-x86_64-unknown-linux-gnu
1.67.0-x86_64-unknown-linux-gnu
1.69.0-x86_64-unknown-linux-gnu
1.72.0-x86_64-unknown-linux-gnu
1.75.0-x86_64-unknown-linux-gnu
1.77.0-x86_64-unknown-linux-gnu
1.79.0-x86_64-unknown-linux-gnu
1.80.1-x86_64-unknown-linux-gnu
1.82.0-x86_64-unknown-linux-gnu
active toolchain
stable-x86_64-unknown-linux-gnu (default)
rustc 1.65.0 (897e37553 2022-11-02)
Could be a good idea to add a rust cleanup task...

Really prefer the LXC concept... but this problems do not affect docker...

Fixed, cleaning up rust toolchains.
rustup toolchain uninstall XXXXXXXXXXXXXXXXXXXXX
root@vaultwarden:/# rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /root/.rustup

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu (default)
1.82.0-x86_64-unknown-linux-gnu

active toolchain
----------------

stable-x86_64-unknown-linux-gnu (default)
rustc 1.82.0 (f6e511eec 2024-10-15)


How to use Api Ai with botkit any documention ?

Apparently, the botkit-middleware-apiai repo got deleted recently and has been moved to botkit-middleware-dialogflow. There you can find some basic introduction.

botkit-middleware-dialogflow is not working i opened issue there .

look cools answer.


fix armstrong numbers function name to match tests

tests expect this function to be called armstrong-number? (singular), this rename fixes that.

I rebased locally and ran the CI tests.  Maybe this patch's branch predates the CI for this track.  Anyway, it passed all the tests (it would have been weird if it failed).  I'll go ahead and merge this.  Thanks again for your contribution, @joaofnds !


Instructor List

Create a list of all of our instructors and if they are available for private instructors and their contact information

Created staff page, profile information can be added.


When disabling ranges - sidebar still exists with no options

I'm using disableRanges() and disableCustomRange() combined in my DateRangeFilter, but sidebar to pick custom range exists.
Now:

Expected behavior:

Thank you for raising the issue.
Fixed with version 2.5.7.
Use disableRanges() method only to hide the range column.


the wiki should Be more simple and practical

for example,the icon on wiki page

there is no need to change the icon for Chinese.
And the wiki's quick start is Not following the common sense.You can provide a maven or gradle start guidence step by step.

Issues have been created in the dubbo-website project


Ollama API integration

I am trying to figure out how to integrate Ollama for full local integration. Running into an issue of using the API streaming endpoint vs the API key that you require.
Any idea on how to fix or are there plans to integrate Ollama?

This project uses https://github.com/knowsuchagency/promptic which sits on top of litellm and should support ollama https://docs.litellm.ai/docs/providers/ollama


Import-BetaSpConfig does not take in import file properly

I am having an issue using Import-BetaSpConfig from the powershell PSSailpoint library, getting this error : "{ “messages”: [ { “localeOrigin”: “DEFAULT”, “text”: “No files were supplied for import.”, “locale”: “en-US” } ], “trackingId”:
** | “3112a5a5c8164fb694d4fd67b0be39c3”, “detailCode”: “400.1.3 Illegal value” }"**
when executing the following code.
$Preview = $true
$filename = "export_config_ef867c38-a454-42a3-a3d5-f9671b1ad00d.json"
$Result = Import-BetaSpConfig -Data $filename -Preview $Preview

This is resolved in https://github.com/sailpoint-oss/powershell-sdk/commit/2cb1e5fd03daae487e8b252356fb4468df09afa6.


bump build-number, styling recipe, add python to run dependencies

great, by looking into successful build-logs, I see that now artifacts for each python variant is built


Remove warning "deprecated" in url.py

What's this Pull Request do?
Remove warning in urls.py.
"The old syntax using pattern is deprecated in Django 1.8, and will be removed in Django 1.10."
What has been changed?

[x] Remove patterns from urls.py

Any background context you want to provide?
version django=1.9.6
RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and will be removed in Django 1.10. Update your urlpatterns to be a list of django.conf.urls.url() instances instead.
Screenshots
GitHub issues

Thanks!


cypress docker image root user misconfiguration

We tried to run cypress docker image under Jenkins which runs all docker images with non-root account. Unfortunately, this is not possible without hack and modifications in the image itself.
I've investigated this a bit and it seems that the source of this issue is that cypress is installed under /root folder by default. This is misconfiguration because /root folder is not designed to host global libraries or software. It translated then to all sorts of problems, like libraries not resolving, difficulties to run images under SaaS CI providers, etc.
My proposal is to have cypress installed into /usr/local or whatever is provided by default npm configuration under used OS.

@ViliusS
There are Jenkins examples listed in the table:
cypress-io/cypress-example-kitchensink > CI Workflow Examples
The examples use cypress/base Docker images.
Which type of Docker images were you having problems with (base/browsers/included)?
If you were not using cypress/base perhaps you would like to try that out.

Closing due to inactivity.

@MikeMcC399 sorry, I've totally missed your previous question. We were actually using cypress/factory image. We could in theory probably use base but we really don't want to take care of installing cypress ourselves. IMHO cypress (or any software for that matter) should not be installed into /root by default, be it custom or official image.

Thanks for your feedback and I have re-opened your issue.

The Cypress binary installs in /root
https://github.com/cypress-io/cypress-docker-images/blob/55c80b6bd6a64213f5544da91fc50dd966834075/factory/factory.Dockerfile#L24
The Cypress npm module installs in /usr/local/lib/node_modules which is standard for npm global installation.
https://github.com/cypress-io/cypress-docker-images/blob/55c80b6bd6a64213f5544da91fc50dd966834075/factory/factory.Dockerfile#L111-L113


Component Plugins Docs

Feature Description
Component plugin docs are quite new, and need some work for both plugin authors, and users.
@archiewood - would be good to get your input here.

So far:

[ ] Example plugin library at labs.evidence.dev
[ ] Updated docs to unpacked format
[ ] Referenced labs.evidence.dev as template


Backend - Actual API for Recruiters' Posts

[x] Create table for Job and dependencies
[x] Integrate with SQLBoiler
[x] Generate models
[ ] Create service
[ ] create endpoint for the APIs

closing as this is done #65


How do I use the generated images vector sequences for portraying real images?

Thank you for creating this code!
I managed to successfully train the PixelVAE model and CanvasVAE model, and I have questions regarding how to plot a reconstructed layout as a real banner image.
As far as I know, the PixelVAE model encodes pillow images into vectors (512 dim) and the CanvasVAE model interprets the image sequences as a collection of those vectors.
The output of the CanvasVAE, are all in numbers (whether they are discretized values or float numbers), and while it is possible to portray the generated outputs as bounding boxes using the top, left, width, and height values, I am not sure how to convert image vector sequences to real rgba images.
I could use the PixelVAE decoder, but the outputs are too blurry and hard to distinguish (hardly usable as real images)
In your paper, I read that you have randomly generated crello documents with real images portrayed in the banners. Is there a specific method you used to generate real crisp images based on the generated image vector?

@hunkim98 The images are retrieved from the training dataset in the paper. See Section 5.4

Oh, I see! the images and shape seem to have been filled using a "nearest neighbor retrieval". Thanks for your clarification!


Put CosmicEmu in new emulators framework

A nice emulator framework for power spectra was implemented here #1094. We should put the existing cosmicEmu implementation in the same framework.

Done in #1103


Add some options for the prometheus secret so you can use an existing secret

Specifically, it allows you to override the secret name, the keys for the username, password, and/or bearer token inside that secret. Just like before, the secret is created values for username, password, or bearer_token are set, and the secret will not be created if those values are not set.
This also updates the deployment to reference the secret with named keys, even if the secret has not been created.

##Chart rendered with default values
rendered chart:
<no secret created>
---
# Source: opencost/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
...
spec:
  template:
    spec:
      containers:
      - image: "quay.io/kubecost1/kubecost-cost-model:prod-1.103.1"
        ...
          env:
          - name: PROMETHEUS_SERVER_ENDPOINT
            value: "http://my-prometheus.opencost.svc:9090"
          - name: CLUSTER_ID
            value: "default-cluster"
          # If username, password or bearer_token are defined, pull from secrets
          # Add any additional provided variables
          imagePullPolicy: Always

Chart rendered with username and password
values:
opencost:
  prometheus:
    username: "my-username"
    password: "my-password"

rendered:
---
# Source: opencost/templates/secret.yaml
apiVersion: v1
kind: Secret
...
data:
  DB_BASIC_AUTH_USERNAME: "bXktdXNlcm5hbWU="
  DB_BASIC_AUTH_PW: "bXktcGFzc3dvcmQ="
...
---
# Source: opencost/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
...
spec:
  template:
    spec:
      containers:
      - image: "quay.io/kubecost1/kubecost-cost-model:prod-1.103.1"
        ...
          env:
          - name: PROMETHEUS_SERVER_ENDPOINT
            value: "http://my-prometheus.opencost.svc:9090"
          - name: CLUSTER_ID
            value: "default-cluster"
          # If username, password or bearer_token are defined, pull from secrets
          - name: DB_BASIC_AUTH_USERNAME
            valueFrom:
              secretKeyRef:
                name: oc-opencost
                key: DB_BASIC_AUTH_USERNAME
          - name: DB_BASIC_AUTH_PW
            valueFrom:
              secretKeyRef:
                name: oc-opencost
                key: DB_BASIC_AUTH_PW
          # Add any additional provided variables
          imagePullPolicy: Always

Chart rendered with secret_name, username_key, and password_key
values:
opencost:
  prometheus:
    secret_name: "my-secret"
    username_key: username
    password_key: password

rendered:
<no secret created>
---
# Source: opencost/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
...
spec:
  template:
    spec:
      containers:
      - image: "quay.io/kubecost1/kubecost-cost-model:prod-1.103.1"
        ...
          env:
          - name: PROMETHEUS_SERVER_ENDPOINT
            value: "http://my-prometheus.opencost.svc:9090"
          - name: CLUSTER_ID
            value: "default-cluster"
          # If username, password or bearer_token are defined, pull from secrets
          - name: DB_BASIC_AUTH_USERNAME
            valueFrom:
              secretKeyRef:
                name: my-secret
                key: username
          - name: DB_BASIC_AUTH_PW
            valueFrom:
              secretKeyRef:
                name: my-secret
                key: password
          # Add any additional provided variables
          imagePullPolicy: Always


bug: Mock data export csv file error

There is a problem with data simulation exporting csv files in AI tools

Thanks for the feedback, I think I know what the problem is and I'll fix it as soon as I can.

This issue has been resolved.
#23
https://github.com/Caojiahao-Coder/gpt_next/releases/tag/v1.3.7-2

Thanks again for your use and feedback.


Corrected typo

Changed a typo from Start_VMs_job to Stop_VMs_job on line 159.

I signed it!

Thanks for the fix!


Error while running sample test

Are you requesting a feature or reporting a bug?
I report a bug
What is the current behavior?
I try to launch the sample test given in https://github.com/DevExpress/testcafe.
I run with chrome and firefox but the html opened is displayed as text, not read.
Here is what chrome displayed when opened.

I have nothing in logs
What is the expected behavior?
The HTML should be interpreted
How would you reproduce the current behavior (if this is a bug)?
I just followed getting started https://github.com/DevExpress/testcafe
Specify your

operating system: Ubuntu 16.04
testcafe version: 0.17.2
node.js version: 6.11.3
chrome version : 61.0.3163.100 (official release) (64bits)

Hello @ggrimbert, could you please try the latest TestCafe alpha? You can install it with npm i testcafe@alpha.

Same thing,
I tried to launch tests with following commands :
testcafe 'chrome --user-data-dir=/tmp/temp-chrome-profile --auto-open-devtools-for-tabs --allow-javascript' test1.ts --proxy <IP_ADDRESS>:80

testcafe chrome test1.ts

In these examples it's .ts, but I tried with .js and got the same results.

Do you have some proxy? If so, could you disable it and try to run tests without it? If you need your proxy to access the Internet, you can install http-server (npm i -g http-server), run it from an another terminal window (just http-server), disable proxy and use the following test:
fixture `Simple`. page `localhost:8080`;

test('Test', t => t.wait(3000));

I do have a proxy...
While using the following command
testcafe 'chrome --user-data-dir=/tmp/temp-chrome-profile --no-proxy-server' test1.ts --proxy <IP_ADDRESS>:80

it works ! Thanks for your help


Flatlist performance and loading mechanism

Description
I'm testing initial performance of Flatlist (without any optimization code) and found something interesting:

it used 7.37 seconds to finish loading of 300 simple numbers
after initial batch of load (<100 numbers) is finished, system loaded 10 numbers per batch, but repeat start from 1-100, 1-110,1-120...until 1-300 (so in total around 3000 times)

I don't understand this mechanism as well as long duration to load just 300 numbers.
Maybe somewhere is wrong? Thanks in advance for help and clarifications.
Since this is testing only for initial performance, pls forget any optimization solution temporarily.
Version
0.68.2
Output of npx react-native info
{
"name": "myunittest",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web",
"eject": "expo eject"
},
"dependencies": {
"@react-native-async-storage/async-storage": "^1.17.7",
"@react-native-community/netinfo": "8.2.0",
"@react-navigation/native": "^6.0.10",
"@react-navigation/native-stack": "^6.6.2",
"axios": "^0.27.2",
"cos-js-sdk-v5": "^1.3.9",
"expo": "~45.0.0",
"expo-av": "~11.2.3",
"expo-camera": "^12.2.0",
"expo-media-library": "~14.1.0",
"expo-web-browser": "^10.2.1",
"react": "17.0.2",
"react-native": "0.68.2",
"react-native-countdown-component": "^2.7.1",
"react-native-radio-buttons-group": "^2.2.11",
"expo-file-system": "~14.0.0"
},
"devDependencies": {
"@babel/core": "^7.12.9"
},
"private": true
}
Steps to reproduce
import React from "react";
import { StyleSheet, Text, View, FlatList } from "react-native";
export default function App() {
const list = [
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41,
42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80,
81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115,
116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146,
147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177,
178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208,
209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239,
240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270,
271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300,
];
console.log(Date.now());
function renItem({ item, index }) {
if (index === 299) console.log(Date.now());
return <Text style={{ width: 100 }}>{item};
}
return (

);
}
const styles = StyleSheet.create({
container: {
backgroundColor: "fff",
justifyContent: "center",
alignItems: "center",
marginVertical: 36,
paddingVertical: 16,
},
});
Snack, code example, screenshot, or link to a repository

Don't know why codes on Return are not shown, post again
return (

);

I recommend taking a look at this resource to help understand the performance characteristics of FlatList and what you can do to tweak/optimize for your use case.

yes，I have read it. Yet I just want to understand initial performance of RN on Flatlist, seems not good enough...
thanks anyway for your advice, cheers.

@alickcai did you test this on an Android device running Android 13 by any chance? I have encountered an issue where flatlist performance is massively degraded on Android 13.

flatlist performance is massively degraded on Android 13.

@mmmoussa is your flatlist inverted by chance? We experienced a huge in performance as well on Android 13 and found it to be the inverted prop on flatlists and used this solution

Thanks @GenoD! We did end up finding the cause to be the inverted prop as well and we ended up fixing it by reversing our data before feeding it to the list and then also inverting all logic that made use of item index.

This is still a problem I don't know why this is closed. The performance is not good. We have tried the optimization mentioned in the doc.


Disconnecting example

For people unfamiliar with the dbus event loop. How are we supposed to cleanly shutdown after having written a value?
I added these in disconnect_succeeded:
device.disconnect()
manager.stop()

Should that suffice?

disconnect_succeded is received when the device is disconnected successfully (one of the cases is when device.disconnect() is called during execution) so you have to call these two methods (device.disconnect(), manager.stop()) in your code before disconnect_succeeded is received, not inside its handler. Otherwise, you are going to execute a disconnect() method on an already disconnected device.

So let's say I want to write to all characteristics and exit cleanly, I would use something like this, correct?
import gatt

manager = gatt.DeviceManager(adapter_name='hci0')

class AnyDevice(gatt.Device):
    def connect_succeeded(self):
        super().connect_succeeded()
        print("[%s] Connected" % (self.mac_address))

    def connect_failed(self, error):
        super().connect_failed(error)
        print("[%s] Connection failed: %s" % (self.mac_address, str(error)))

    def disconnect_succeeded(self):
        super().disconnect_succeeded()
        print("[%s] Disconnected" % (self.mac_address))

    def services_resolved(self):
        super().services_resolved()

        print("[%s] Resolved services" % (self.mac_address))
        for service in self.services:
            print("[%s]  Service [%s]" % (self.mac_address, service.uuid))
            for characteristic in service.characteristics:
                print("[%s]    Characteristic [%s]: Sending Testing string!" % (self.mac_address, characteristic.uuid))
                characteristic.write_value(bytearray("Testing", encoding="ascii"))

        self.disconnect()
        self.manager.stop()

device = AnyDevice(mac_address='XX:XX:XX:XX:XX:XX', manager=manager)
device.connect()

manager.run()

Yes, this is a correct way to do it

Does this work on you? When I try this, the program does not exit


Update mus56.toml

I changed the net_address:
old: <IP_ADDRESS>
new: <IP_ADDRESS>
Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

https://github.com/anoma/namada-testnets/pull/1218
https://github.com/anoma/namada-testnets/pull/1772

Whitespace found in filename. Found filename namada-public-testnet-15/Update mus56.toml