mount resource is not idempotent with label

Description
mount resource infinitely tries to enable the resource with device_type :label.
After run, /etc/fstab file is unchanged.
I dumped out the current_resource and new_resource with some attributes:
enabled: true false
device: LABEL=/mnt/foo /mnt/foo
device_type: device label
mount_point: /mnt/foo /mnt/foo
fstype: ext4 ext4
options: ["defaults", "nofail"] ["defaults", "nofail"]
dump: 0 0
pass: 2 2

Chef-client tries to continue enabling this resource because,  Chef::Provider::Mount#action_enabled judges whether to enable the resource when current_resource.enabled && mount_options_unchanged? && device_unchanged? is falsey (https://github.com/chef/chef/blob/master/lib/chef/provider/mount.rb#L123-L129)
And device_unchaged? implementation is @current_resource.device == @new_resource.device, so device of current_resource and new_resource differs, as current_resource's one is from the first column of /etc/fstab and new_resource's one is from mount resource definition.
To make this resource idempotent, I think the device_unchaged? implementation need to be fixed.
(I noticed this issue yesterday, just after upgrading chef-client from v13 to v14. With v13 this resource had been idempotent.)
Chef Version
14.10.9
Platform Version
AmazonLinux 1
Replication Case
On EC2, mount the EBS volume like the following
dir = "/mnt/foo
mount dir do
  device_type :label
  device '/mnt/foo'
  fstype 'ext4'
  options 'defaults,nofail'
  action [:mount, :enable]
end

Client Output
This log is whyrun log with -l trace option
[2019-03-02T00:26:42+09:00] INFO: Processing mount[/mnt/foo] action mount (foo_base::nfs-common line 23)
[2019-03-02T00:26:42+09:00] TRACE: Providers for generic mount resource enabled on node include: [Chef::Provider::Mount::Mount]
[2019-03-02T00:26:42+09:00] TRACE: Provider for action mount on resource mount[/mnt/foo] is Chef::Provider::Mount::Mount
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=2013548k,nr_inodes=503387,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
/dev/xvda1 on / type ext4 (rw,noatime,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
none on /sys/kernel/debug type debugfs (rw,relatime)
/dev/xvdf on /mnt/foo type ext4 (rw,relatime,data=ordered)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
sunrpc on /proc/fs/nfsd type nfsd (rw,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/xvdf
[2019-03-02T00:26:42+09:00] TRACE: Special device /dev/xvdf with label /mnt/foo mounted as /mnt/foo
[2019-03-02T00:26:42+09:00] TRACE: Found mount LABEL=/mnt/foo to /mnt/foo in /etc/fstab
[2019-03-02T00:26:42+09:00] TRACE: mount[/mnt/foo] is already mounted
.[2019-03-02T00:26:42+09:00] INFO: Processing mount[/mnt/foo] action enable (foo_base::nfs-common line 23)
[2019-03-02T00:26:42+09:00] TRACE: Providers for generic mount resource enabled on node include: [Chef::Provider::Mount::Mount]
[2019-03-02T00:26:42+09:00] TRACE: Provider for action enable on resource mount[/mnt/foo] is Chef::Provider::Mount::Mount
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=2013548k,nr_inodes=503387,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
/dev/xvda1 on / type ext4 (rw,noatime,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
none on /sys/kernel/debug type debugfs (rw,relatime)
/dev/xvdf on /mnt/foo type ext4 (rw,relatime,data=ordered)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
sunrpc on /proc/fs/nfsd type nfsd (rw,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/xvdf
[2019-03-02T00:26:42+09:00] TRACE: Special device /dev/xvdf with label /mnt/foo mounted as /mnt/foo
[2019-03-02T00:26:42+09:00] TRACE: Found mount LABEL=/mnt/foo to /mnt/foo in /etc/fstab

Stacktrace
N/A

I have this issue too.
Chef client version 14.11.21


upload doesn't work

I'm getting the error:
sorry, the request failed. Please try again. {line: 381, column: 882, sourceURL: file: //index.android.bundle.

Not really sure what the error is all about but it seems I do not get this error when I enable chrome debugging. I tried creating a deploy version of the app in hopes that it would work but it didn't.
I'll come back later to update and provide more info.

seems to be related to this: https://github.com/wkh237/react-native-fetch-blob/issues/6
I'll close this off when it solves the issue for me.

Hi @anchetaWern , I already got the situation, thanks for the report.
You may try upgrade to v0.4.0, or would you provide the usage code about how the error happens?

@wkh237 thanks it's working now. It looks like it's the same problem as the issue I linked to.
I was supplying the base64 of the image picked with this module: https://github.com/marcshilling/react-native-image-picker to your library and it didn't work before when chrome debugging is disabled.


Files "Not" added to chat

Someone may have noted this but when I ran /ls to get the files added to the chat it said:
Repo files not in the chat:
Basically, it listed all of the files that I DID ADD TO CHAT... doh!

Thanks for trying aider and filing this issue.
I'm not sure I understand the problem you are trying to describe. Maybe can you share a screenshot that shows the issue?

Looks alright for me?
readme.md> /ls

Files in chat:

  readme.md

Repo files not in the chat:

  .gitattributes
  .gitignore

Well, I manually add some files (eg:"/add src/filename.cs"), then when I run the "ls" command it shows everything I added to chat as "not in the chat". In fact nothing shows as "added".
When I take a look at some of the files in the "aider" git directories, I can see it says "added to chat" in fact when I add them it says this in the console right afterwards... says commit, too... I also tried globbing "/add src/**/*.cs and it rolls through a dozen files as adding them. I think I have about 3 dozen source files altogether.
I do get a throttle message not long after I add too many files within say, 10 mins or so. Some of the files are long but I'm trying to build context so I don't have to explain so much and want it to review things as well.  Does the .DB file keep key value pairs for files and content or am I to add files every single time? I may be doing it wrong as I thought it kept a history/db to eliminate asking for file access every time.
Maybe I'll just try starting from scratch but a lot of heavy lifting all over again it seems. My code may be terrible, but I spent a lot of hours on it to get the old pile working (my precious), lol.
I'll keep playing with it.

Can you share a screenshot?

I can..

Hopefully this helps!
I'm running aider 0.17.0

It looks like maybe you have added some very large files to the chat? What does /tokens show you? You may have overwhelmed and confused GPT with too much context.

Let me know if you can share more info to help debug and reproduce.
I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.

wondering if there is a way to show only files in the chat.
not so useful to have a list of files not in the chat when there are hundreds of files!


how to destroy GBA use memory

HI @FASTSHIFT,
I want integrated into NXP guider  framework, I need to have a function that can delete the memory used by GBA.
Do you have any suggest ?

@kay54068
Supported in this commit
Call the lv_gba_emu_del function to free the memory of the entire gba emulator.

Hi @FASTSHIFT
Got it. thanks.
your new code arch very nice , worthy of further study.


Handle bundles that have data items with empty payloads

This PR adds support for data items with empty payloads on the process stream method. There is increased testing coverage added. I have validated that I am able to unpack bundles from this change:

~/ar-io/bundle-exporter main !2                        31s node 18.16.0 11:46:01 AM
> node index.js abELEpiWpOZZNFYEwkBKCXWH9JSSs8MxjK8QaY4aknY
Bundle with txId abELEpiWpOZZNFYEwkBKCXWH9JSSs8MxjK8QaY4aknY already exists in ./bundles
Working on bundle with txId abELEpiWpOZZNFYEwkBKCXWH9JSSs8MxjK8QaY4aknY...
Data item count: 2
(1/2) Unpacking data item with txId ECC4MAuSwc0Q4RxA0T9ehviQlWYdfU-kLf_QRYClXcc...
... unpacking item data with size 47 at offset 1236...
(2/2) Unpacking data item with txId UjKLwBe1cdv5iWyj-9h58vEvhIpAxdnB0Y9QLeYq3Qg...
... unpacking item data with size 0 at offset 2327...
Bundles unpacked to ./output folder

~/ar-io/bundle-exporter main !2 ?1                                                             node 18.16.0 11:46:26 AM
> node index.js dJl5lR6vYM-VwnHvWYv_iRP7lJNeGSL3UDTco9tByko
Bundle with txId dJl5lR6vYM-VwnHvWYv_iRP7lJNeGSL3UDTco9tByko already exists in ./bundles
Working on bundle with txId dJl5lR6vYM-VwnHvWYv_iRP7lJNeGSL3UDTco9tByko...
Data item count: 1
(1/1) Unpacking data item with txId RunqhAitvmUyfrJwKxj0t5i7Nl39OU0kGVM0whQHPKM...
... unpacking item data with size 0 at offset 1166...
Bundles unpacked to ./output folder

These bundles are available to inspect: dJl5lR6vYM-VwnHvWYv_iRP7lJNeGSL3UDTco9tByko abELEpiWpOZZNFYEwkBKCXWH9JSSs8MxjK8QaY4aknY

Putting this back into draft for now. Getting some unexpected results I need to understand

Putting this back into draft for now. Getting some unexpected results I need to understand

All good there, ready for review!


Login error on safari browsers

I am getting a login error, on safari browser (Version 13.1 (156<IP_ADDRESS>.8)).
Error : "You has to have the permission to view the workflows!"
I've also tried local demo, but the error is same.

Mehmet;

It worked on my Safari, interesting 🤔 But the thing is, I have bumped into this on my mobile device and though maybe it is flakiness with my phone. Thank you for reporting this @m3hm3taydin , I will look into this as soon as possible.


Support skip_page missing OffsetIndex Fallback in SerializedPageReader

Which issue does this PR close?
Closes #2459
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

I'm going to get this in as the fix for master is in #2494


Add ReasonCode to SendExtendedAuthenticationExchangeDataAsync

Fixes #1881

@chkr1011 is there a way to validate this fix from the MyGet feed?

@rido-min The libraries cannot be signed because the branch is not created in this repo so that access to certain keys does not work and will thus the build will fail. I can create a separate branch or we merge this PR and create another one if further changes are required (I would create the branch then so that the Actions work properly).


update stage_ops_test to medium and add 2 shards

Fix timeout of stage_op_test.  Increase timeout and add 2 shards.

Can one of the admins verify this patch?

Btw. do we know what why the tests started to time out? Performance regression? CI overload?

Jenkins test this please.

This is the reason: https://github.com/tensorflow/tensorflow/pull/9686


How does server wait for async dispatches?

I might've missed this somewhere, but not sure I understand. If I run withReduxSaga in sync mode, and have a bunch of dispatch calls in getInitialProps, how does next-redux-saga know when they are all done on the server side so it can render the app and respond with it?
My sample code is working as expected for now, but I want to be sure it's not just timing luck (so that production requests don't randomly fail sometimes because some dispatch actions didn't finish on time).

Hi @ivanakimov -
When next-redux-saga runs on the server it dispatches END, which allows all your dispatch calls to complete before sending a response to the client. (source)
Does that help?  Let me know if you have any other questions.

Thanks for the explanation @bmealhouse. I might be a little bit confused then about how dispatches work. If I dispatch lots of my custom actions in my getInitialProps (and some of them make API requests), and then your last dispatch(END) happens -- does it work because dispatch actions are queued up and your END is guaranteed to be last? Are there any scenarios where some dispatches might not finish in time (for example my one dispatch triggers another dispatch etc, or multiple API calls being made)?

@ivanakimov - When END is dispatched, it triggers the root saga to shutdown, however, the root saga cannot shutdown, until all of its dependencies (async requests) have resolved. As long as you dispatch all your async actions before END is dispatched (which you are, by using getInitialProps from Next.js), then those async actions are guaranteed to finish processing on the server before a response is sent to the client.
You can dispatch as many times as you'd like as long as you are inside a single saga. END will wait until all the calls to dispatch have resolved before shutting down.
When you are dispatching async actions between multiple sagas, this is where things start to break down. You would have to handle this situation using channels, however, I'd rather duplicate code vs. introduce the complexity of channels.


fixed three dots menu on comments shown to all users

PR Fixes:

1 Three dots menu on comments shown to all users and not just the owner of the comment

Resolves #1259
Checklist before requesting a review

[ yes ] I have performed a self-review of my code
[ yes ] I assure there is no similar/duplicate pull request regarding same issue

lol, 17 files
are you kidding me?

@MeerUzairWasHere It is happening due to Code Linting and Formatting I have experienced the same ,I had changed only three lines and after running running npm run lint:check/fix and same for the format These many files have changed

Even without running the npm run lint:fix/format:fix, when commiting the changes it happens by default

and the linting is so irregular ,
is this an issue or it is made like that

You can see in the above file the imports go to the same line same line and on different line for some imports

@MeerUzairWasHere it also fixes linting and makes the code more in-line with the rest of the code base. without this, it will fail the linting check.

Closign in favour of #1260


V-Slice Mod Support

What feature do you want to get added on the P-Slice engine?
V-Slice Mod Support (yes fr)

No.


Textures rotated in atlas don't work

This needs to be fixed.

Fixed in https://github.com/indiesoftby/defold-dissolve-fx/commit/29c4fc2dfd3a018a85f304776595917ee8e8563b


How to support a new resolution?

If there are enough GPU cards and data volume, can the SFT-based method add a new resolution generation, such as a width of 480 and a height of 720?

Theoretically speaking, this is certainly feasible, but we have not attempted it


Converting spaces to underscores

Currently, spaces in screenshot filenames are left as-is, which makes working with those files in git cumbersome.
Would you accept a PR for converting spaces to underscores/dashes?

This implies a BC Break.

I'll accept a PR for an optional parameter.  But you could use the fileNameGetter method override to change output file names.

Do you think that changing the default to using underscores/dashes would break current workflows?
Or are there other reasons not to make that the default?

People use PhantomCSS in all kinds of ways in the wild.  I'm reluctant to change default behaviors, as this would almost certainly affect someone's workflow.


Debating about an official build tool ...

Hi,
I can see that their are 3 ways for building :

make
neph
docker

I personnaly using make (cause it's easy and I'm lazy).
@tbrand I can see that are building using neph
Shouldn't we build using the same thing ?
Behind that, there is the idea of a cross-platform solution -> building objectif c, dot net, and else using the same toolchain / isolation level.
For me docker is a good idea, but for linux enable tools (no asp no swift ...).
I suggest we use Vagrant (cause there is OS X, Windows ...).
@tbrand @OvermindDL1 what do you think about that ?
Regards,

I'd probably just use make or shell scripts myself in general...?

@OvermindDL1 its what I do but ... I do not run asp or swift benchmarks ;-)
there is not many solution that could be used to create various (OS) targets

@OvermindDL1 its what I do but ... I do not run asp or swift benchmarks ;-)

Ditto.  ^.^;
Probably docker that is front-managed by a make file or shell script would probably be best.

@OvermindDL1 the problem will be the same ...
docker is linux specific

docker is linux specific

Uh... no?  I'm pretty sure it runs on mac, and it definitely runs on windows (we are using it on windows at work)...  o.O?

@OvermindDL1 ;-)
sure
docker work on Windows
but you can not create Windows targets, can you ?

but you can not create Windows targets, can you ?

In a VM setup, but then again, screw windows?  ^.^

@OvermindDL1 Not a windows* fan either, but as a performance comparison, I think its a mistake too not show asp performance ..

@OvermindDL1 Not a windows* fan either, but as a performance comparison, I think its a mistake too not show asp performance ..

But asp works just fine on linux (we are running an ASP site with the official Microsoft .NET Core on RedHat7 at work)?

@OvermindDL1 I do not know that such language is officially supported by RedHat 👍
However, the idea here is not to debate about language ... but how to build which_is_the_fastest
my point is that building, in my point of view, SHOULD be cross-platform (for the moment cross-os), not just to say that we COULD by to be closest as real usage ;-).
it could be accurate in the feature to benchmarks python and ruby on FreeBSD for example

@OvermindDL1 I do not know that such language is officially supported by RedHat +1

Recently added (about a year ago or so).  We converted the front-end website (marketing department uses an ASP horror that we'd prefer not, but eh...) to redhat with it with no issues.
https://developers.redhat.com/topics/dotnet/

:trollface: sorry, I feel your pain ...

to be serious, docker COULD be a solution ...
if @tbrand and you are OK ;-)

Just for me, I continue to use neph. It's very good tool for me. :smile: I can put a patch by myself when new repository has been added.
So if main build tools will be moved to docker, that's ok. But we cannot remove neph completely.
make is very common tools - so the same reason as neph - it is difficult to remove from the project I think.

sure, I don't want to remove something ... taste and flavour, is for each developer
@tbrand I think about one tool use to display official results. not a problem for me if you use neph  and some others make, just for me docker could help maintaining because portable ... and what about your time ;-)


Fix up operator API generation rules

Product Version(s): N/A (PR is for docs repo tooling itself)
Issue: N/A
Link to docs preview: N/A
SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:
Operator API documentation regeneration has not been happening. This change updates
the Makefile so that it's possible to update individual docs trees, but also update
all trees at once to ensure everything is correct and up-to-date.
Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

This is a great help -- thanks! CI passing now. LGTM!


add tense to relative-time

This adds tense to relative-time, which enables it to be used like time-ago or time-until. This makes the logic within relative-time slightly more complicated but with subsequent PRs we'll be able to drastically reduce complexity within time-ago and time-until, and we can remove them entirely in a major version bump.

:wave: Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

:art: If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
:fast_forward: If this is a PR that includes changes to an interaction, please include a video recording in the description.
:warning: If this is urgent, please visit us in #primer on Slack and tag the first responders listed in the channel topic.


50 subscriptions per account

The limitations mention that

There's a limit of 50 subscriptions per account. After that, subscriptions can only be created by using Account Center.

But, when trying to create a new subscription using the Service Principal, I get the following error:
There must be an existing subscription with the offer up to a max number of subscriptions.  Further details: Account must have between 1 and 49 existing subscriptions. 50 subscriptions were found.
This SP has only been used to create about 5 subscriptions so far, so is the limit speaking to the number of subscriptions globally or is it saying that each account can create up to 50 subscriptions?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 371189c2-154f-2716-bbc0-8496a76c5ac9
Version Independent ID: bb5cd103-ff51-1753-f269-e2c1aa49a8c8
Content: Programmatically create Azure Enterprise subscriptions
Content Source: articles/azure-resource-manager/programmatically-create-subscription.md
Service: azure-resource-manager
GitHub Login: @adpick
Microsoft Alias: adpick

@Unalloyedcube Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

The limit is on a per account basis, however it includes all subscriptions ever created on that account (by API or otherwise). The system treats a deleted subscription the same as an active subscription for auditing purposes. Hope that clarifies, and we are working to remove this limitation before we GA the API.

Does this limit include unsuccessful creation attempts as well? I asked because during testing not all subscriptions were created. Only 5 were created successfully, so I should be able to create more subscriptions under that SP.

I wouldn't expect it to include unsuccessful creation attempts, but it isn't the creation history of the SP that is relevant, it's the Account that the SP has access to. For example, the account owner may have created other subscriptions under that account without your knowledge if all you have is create permissions via the SP.

I get it now. Thanks for the clarification.

@Unalloyedcube Happy to help!
@femsulu #please-close

I couldn't find any official doc about the limits of subscriptions per account. Do they still valid? Does it exist an official doc about it?

@adpick can NelsonMarcos Question be answered?
We are currently working on a new subscription design as well, and a limit of 50 would have an design impact. So Official Docs and/or knowing it is still valid would help.


electrum-personal-server: init at 0.2.0

Motivation for this change
This change adds a package and NixOS module for ([Electrum Personal Server]https://github.com/chris-belcher/electrum-personal-server). The module sets up the service as a systemd user service, and thus each user would configure the service. The only configuration provided by the module is the location of the user's configuration file.
Things done

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

[*] NixOS
[ ] macOS
[ ] other Linux distributions

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

I've migrated the module and package to my NUR. See https://nix-community.github.io/nur-search/repos/emmanuelrosa/


Proper runtime "enter" instead of spawn + local blocking

Remove the necessity to spawn threads by using an explicit enter method in the Runtime trait which blocks on the passed future.
Description, Motivation and Context
Currently all runtimes need to run in background threads / worker pools.
With this PR this is changed: there is an explicit enter which is supposed to block on the passed future, so a current_thread runtime doesn't need to spawn new threads (which makes strace way easier to read, and is simply cleaner imho).
This also removes various (lazy_statics) globals: if a runtime is entered again, it will simply have to recreate the runtime environment, and it should shutdown cleanly on leaving enter. (One might argue whether it should only block on the passed future or on a more generic "runtime shutdown".)
The second commit avoids double-boxing with a more generic JoinHandle and its type-erased CompletionHandle part.
This also makes it more explicit that enter can't work on wasm; I went for a simple panic though instead of going #[cfg(...)]-crazy over the API (especially as the existing wasm cfg handling is broken and looks wrong).
Types of changes

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

(Although the breaking change should only be visible for runtime_raw users.)

@stbuehler Hey there! Overall I like this idea a lot! It'd be nice if it the method could be named block_on to match the futures lib. Would you mind changing it to that? Thanks heaps!
Also cc/ @stjepang, there's a bunch of atomic operations going on that I don't feel confident in reviewing. Would you mind taking a look? Thanks!

I'm certainly open to renaming it - my initial choice was indeed block_on :) But may I suggest having an additional word in it to make it clear it is more than just block_on - maybe start_and_block_on (my favorite choice right now) or enter_and_block_on (to link it to runtime_raw::enter)?
If we go with start_and_block_on one might add a fn start(&self) method later for platforms like wasm which run forever, can't block and where you can only have (and start) one runtime (for example like this: https://github.com/stbuehler/runtime/commit/611231ab57dcdbd6e0929b5dafa4e8819924659e).
I'll have a look at the atomics again too; the synchronization of data with completed should be fine (Acquire/Release are basically made for this exact use case) - but I'm not sure AtomicWaker synchronizes properly (it might need a full barrier), although I think that should count as bug in AtomicWaker...

I took a look at the source of futures_util::future::abortable and they only use Relaxed to set and check the flag (as AtomicWaker uses AcqRel operations internally providing a full barrier), so the atomic ordering should be fine.

Renamed enter to start_and_block_on, and remembered how to spawn on "currently running executor (per thread)" in tokio, removing some complexity.

@stbuehler dang yeah, the fact that the WASM spawn function doesn't block is a bit inconvenient. I do really like short names, so I'd prefer runtime::enter over any longer variants (and in turn the blocking behavior can vary per program).
Still, I kind of wish we could have a WASM futures executor function with the same semantics as the other block_on functions. Perhaps we should open an issue about this.

So you want me to rename it back to enter (I don't mind doing it, just want to make sure :) )?
(In case you didn't notice: I'm also trying to get a RemoteCompletionHandle into futures-rs, so RemoteHandle from futures-rs would be able to replace JoinHandle, solving the atomic ordering issue here.)

After reading the PR again, I noticed that the wasm32 implementation simply panics. This seems like it's indeed the right model. That also means that calling it block_on is in fact an accurate name, and would be preferable over any other.
I still don't feel qualified to review any of the atomics code, pinging @stjepang again for a review pass.

I'd kind of prefer holding off merging this change as it increases complexity quite a bit for comparatively little benefit, which is essentially starting one thread less. I don't feel comfortable saying this is the right step forward as there are many unknowns here. Maybe we can revisit this PR later at some point?

I'd kind of prefer holding off merging this change as it increases complexity quite a bit for comparatively little benefit, which is essentially starting one thread less. I don't feel comfortable saying this is the right step forward as there are many unknowns here. Maybe we can revisit this PR later at some point?

I think the first commit decreases complexity and improves the API significantly, and have no interest in waiting for it.
The second commit increases the complexity of the JoinHandle, yes; I don't mind removing that part (it only costs some boxes for the initial future to be entered), and hope that https://github.com/rust-lang-nursery/futures-rs/pull/1766 goes through - then a later change could use RemoteCompletionHandle from futures.  Also if we drop the second commit I think the current JoinHandle could already be removed in favor of RemoteHandle.

How about this?
/// Runtime trait for runtimes supporting blocking.
pub trait BlockingRuntime<F, T>
where
    F: Future<Output = T>,
{
    /// Runs a future inside the runtime and blocks on the result.
    ///
    /// Needs to call `enter_runtime` or `set_runtime` (only on background threads) in threads
    /// running futures.
    fn block_on(&self, fut: F) -> T;
}

This would remove the need for boxing, support !Send if the runtime supports it, and no atomic memory ordering to review.
See https://github.com/rustasync/runtime/compare/master...stbuehler:runtime-enter2 for the full idea.

Just updated the branch:

no atomic changes anymore, doesn't touch JoinHandle
split block_on method into a separate trait BlockingRuntime

reduces duplication in the tokio imlementation (as only the block_on implementation differs between Tokio and TokioCurrentThread)
the type implementing Runtime can be private now, only the type implementing BlockingRuntime needs to be public - this prevents people abusing entry points in Runtime when it wasn't "entered" before.
wasm32 doesn't need a stub implementation for it, it can use a separate trait

In the context of https://github.com/rustasync/runtime/pull/83#issuecomment-520150680 I'm going to go ahead and close this PR. The way our interactions have been going recently has not been great, and I think it's in everyone's best interest if we part ways here. Thanks for your contributions, and good luck!


Invalid hook call in monorepo example

Describe the bug
The setup as shown in monorepo example apparently includes React twice in the final bundles, making it impossible to use hooks due to hook violation
Expected behavior
I'd expect hooks to be working correctly - like they do in basic example.
I'd expect React to be included once - as I suspect this is the cause of hooks failure
To Reproduce

clone the monorepo example
add const [x] = useState(1) to index.tsx or any other hook usage

const IndexPage: NextPage<IndexProps> = props => {
    const [x] = useState(1)

    return (

                Hello hook {x}.{' '}
                <Link href="/about">
                    About us
                </Link>

    )
};

see the error probably caused by multiple instances of React included in the bundles:

Server Error
Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.

This error happened while generating the page. Any console logs will be displayed in the terminal window.
Call Stack
resolveDispatcher
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/ui/node_modules/react/cjs/react.development.js (1465:13)
useState
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/ui/node_modules/react/cjs/react.development.js (1496:20)
IndexPage
webpack-internal:///./pages/index.tsx (14:61)
processChild
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/react-dom/cjs/react-dom-server.node.development.js (3043:14)
resolve
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/react-dom/cjs/react-dom-server.node.development.js (2960:5)
ReactDOMServerRenderer.render
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/react-dom/cjs/react-dom-server.node.development.js (3435:22)
ReactDOMServerRenderer.read
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/react-dom/cjs/react-dom-server.node.development.js (3373:29)
renderElementToString
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/react-dom/cjs/react-dom-server.node.development.js (3988:27)
render
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/next/next-server/server/render.tsx (130:12)
Object.renderPage
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/next/next-server/server/render.tsx (721:12)
Function.getInitialProps
webpack-internal:///../server/node_modules/next/dist/pages/_document.js (133:19)
loadGetInitialProps
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/next/next-server/lib/utils.ts (306:27)
renderToHTML
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/next/next-server/server/render.tsx (730:48)
<unknown>
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/next/next-server/server/next-server.ts (1054:24)
<unknown>
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/next/next-server/server/next-server.ts (1023:25)
DevServer.renderToHTMLWithComponents
file:///Users/adambar/Projects/tests/nest-next/examples/monorepo/server/node_modules/next/next-server/server/next-server.ts (1131:9)

Version

next.js: 9.4.4
nest: 6.11.11
nest-next: 9.2.0

Additional context
Hooks work fine in basic example.

Digging deeper, it seems it's directly caused by https://github.com/vercel/next.js/issues/9022, so not the issue of this repo itself.

I'm actually going to reopen this because it looks like it may be an issue with both the ui and server having react and react-dom as dependencies. It looks like the there are two suggestions to fix the problem.

Move the react and react-dom dependencies up a directory into the main monorepo folder. This comment provided an example of that.
Use lerna. I don't see any comments confirming that it actually fixes the problem.

I'm open to suggestions and PRs!

Yes, actually I solved it by moving the dependencies one level up, too. Worked for me. I closed it as it's basically the Next's issue, but in fact you're right, the issue with the example being broken exists here. I'd prepare the PR when I have a moment.


fix few sendable warning

motivation: less warning, stable CI
changes: add few sendable annotations to address warning / errors

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test


Investigate failing sample tests

The sample tests are currently failing on master:
https://circleci.com/gh/googleapis/nodejs-monitoring/3742

Fixed in #126


Migrate util/shape to mljs

Those method allow to generate a special matrix that can contain a shape. This is kind of special matrix with a circle or a square, ...
@targos don't you think this could also move to mljs
It is a kind of package that allow to generate matrix based either on a shape or a function (gaussian or other)
I would suggest to create a generate package
matrix-generator or matrix-creator

👍 for a new package but I think it makes more sense to be in the image-js org


add total (combined) balance display field to QT overview

Someone mentioned this at one point, I don't remember who.
I implemented it in the QT but haven't added it to the getinfo field in the RPC calls at this time.
I wanted some feedback regarding the wording for the label as well as just to know if people really want this feature and if they want it in the daemon as well.

(1 hour)

Nice! I think it was confusing for people new to Proof of Stake. I think more info is always better than less. As for the daemon I don't really care about it. How much work is it? Who uses the daemon and can't add? :)

Fixes #309
Work wise it's almost no effort one way or the other @dbroyhill I was just trying to get an idea if people wanted said feature or not.

So should the first "Balance" be "Available Balance"?

Makes sense!

@jpass022 possibly, that's sort of why I was asking for feedback on those labels ;)

Closing in favor of #464


red error sorry i'm a noob :(

intalled everything but i still get this error :(

can you copy/paste the terminal output after you just started comfyui?

looks like it solved automatically and magically after a bunch of restart. ty


Class selector is not working

Guys, could any help me on this?
$('#datetimepicker1').datetimepicker(); -> this is working
$('.datetimepicker1').datetimepicker(); -> not working.
also change

to

Could anyone help me?

basic setup instructions are in the docs: http://eonasdan.github.io/bootstrap-datetimepicker/
if that doesn't help please post a jsfiddle of your issue


Add geom_series.rst

Still many notes to dongchen remain

@AnjuJoon maybe you could add some illustrations for sequences in this notebook? There currently isn't any code in here. Tom has suggested some possible plots in comments in the rst.
@jstac

From @jstac : This branch is stale since work is ongoing on the geom_series lecture in the sandpit.  Closing.


chore(api): move protobuf definitions into console-api dir

Currently, the protobuf definitions for the console API are symlinked
into the console-api directory. This is intended to support vendoring
the console-api crate (see #128).
However, some users have reported that the symlink isn't the ideal
solution. Windows users have had issues following the Unix symlink, so
#128 broke the build for people trying to develop the console on Windows
(I suspect it may still work in WSL?).
There's no real reason that the proto/ directory needs to be in the
repo root, rather than the console-api crate; the symlink was only
added to avoid moving it around. Therefore, it's fine to just move it
instead. This branch moves the proto/ dir into console-api/proto,
hopefully fixing the build issues for Windows users.

cc @Milo123459, please let me know if this fixes the issues you were having building the console?

Fixed my issue, thank you!

Fixed my issue, thank you!

awesome, sorry for any inconvenience!


ExchangeOABVirtualDirectoryAttributeContainingPotentialWebshell description points to reference URL that is 404

Describe the bug
The solution for "Exchange OAB Virtual Directory Attribute Containing Potential Webshell" refers to the Microsoft-controlled URL "https://aka.ms/ExchangeVulns" which redirects to "https://msrc.microsoft.com/blog/2022/09/29/customer-guidance-for-reported-zero-day-vulnerabilities-in-microsoft-exchange-server/blog.microsoft.com/2021/03/02/multiple-security-updates-released-for-exchange-server/" however that page is listed as 404 page Not Found as of 9/12/23.
To Reproduce
Steps to reproduce the behavior:
Open the links, see for yourself, :)
Expected behavior
Need a proper reference URL if it is available, or Microsoft needs to re-store the missing page. or if this detection is no longer relevant perhaps it should be pruned.

Hi @ktb-jcm, thanks for flagging this issue, we will soon get back to you on this. Thanks!

Hi @ktb-jcm, we are working on this issue, and we will provide an update by 21 Sep 2023. Thanks

Hello @ktb-jcm, the MSRC removed the post to which the link is redirect.
We raised the PR with the changes, and changes will be reflected in an upcoming version of the solution.
Thanks!


[Chrore] refactor size conversions

This PR refactors all size conversions to provide consistency throughout Speedtest Tracker.
To-do

[x] Dashboard metrics
[x] Results resource
[x] Results export
[ ] InfluxDB integration
[ ] Listeners and threshold notifications
[x] API endpoints
[ ] Update documentation to define how data is stored and displayed
[ ] tbd...

Changelog
Added

required chrisullyott/php-filesize to help with size conversions

Changed

precision floats will be used instead of rounded floats for all metrics, as a result there will be small changes to metrics reported

Issues

closes #418
closes #467

@alexdelprete when it comes to InfluxDB, I need a reliable data state to pass when something is missing. Does InfluxDB prefer null or 0?
Leaning on 0's

@alexdelprete when it comes to InfluxDB, I need a reliable data state to pass when something is missing. Does InfluxDB prefer null or 0? Leaning towards 0's

I think null is better: https://docs.influxdata.com/flux/v0.x/data-types/basic/null/

null it is


SOQL Error: Expected "'", "(", ":", "FALSE", "NULL", "TRUE", [+-], [0-9], or [1-9] but "=" found.

Describe the bug
When using SOQL source type, if the query contains an equality operator like <, <=, >, >= then get a parse error.
To Reproduce
Steps to reproduce the behavior:

Select SOQL source type
Enter query SELECT Id FROM Account WHERE CreatedDate > YESTERDAY
Error

Expected behavior
I expect to be able to enter normal SOQL queries with equality operators and date/datetime filters.
Source Type
SOQL
Action Type
All
Named Credentials
N/A

Hi doug,
Im still getting this error using this clause: RRC_ArrivalDate__c <= NEXT_N_DAYS: 21.
This is the returning error
Invalid SOQL Query
Expected [0-9] but " " found.

Hi @orlandotv,
The workaround in this case is to remove the whitespace in your relative date filter. For example, NEXT_N_DAYS: 21.
I'll look at softening the validation; it was never intended to "block" people from saving their configurations, just to help people test their queries.

Hi @orlandotv, I'm tracking the whitespace support for date literals in SOQL on a new issue ==> https://github.com/douglascayers-org/sfdx-mass-action-scheduler/issues/100. Please watch it to stay notified of updates. Thanks!


Networking: BUG: TestCNContainer_Base

The test case fails randomly with the following error. The same test when run again will work on the same system.
Detected with Docker version 1.10.3, build 20f81dd
--- FAIL: TestCNContainer_Base (2.45s)
Error Trace:    cn_container_test.go:323
Error:          Expected nil, but got: &errors.errorString{s:"docker container MAC not setup ca:fe:00:02:02:03"}
The failure needs to be root caused. It may be a due to docker timing issue, in which case the mac addresses should be queried again.

Error does not show up in Travis CI. Closing it for now.


Report button on extension

We need a way for users to notify us if a detection is missed, or incorrectly identified.
This might appear as a small icon next to removed/replaced/blurred posts for users to click and report the false identification.
Or, it might appear next to all posts so users can report any post they choose if it was a missed detection.
Not great at UI design thonks, so if someone else has a better idea for how the reporting of false/missed detections should work, input is greatly appreciated.

lgtm!


Validate RHEL 9.3

K3s Versions to be Validated

v1.26.11+k3s2
v1.27.8+k3s2
v1.28.4+k3s2
Testing Considerations

Install and run sonobuoy conformance tests on a hardened cluster
Validate SUC upgrade
Install Rancher Manager
Validate snapshot restore via cluster-reset-restore-path

Additional Information

config.yaml inclusions:
selinux: true

RHEL 9.3 results (with selinux: true)
Verified tests:

Install and run sonobuoy conformance tests on a hardened cluster - v0..57.1 used - PASS

Validate SUC upgrade - PASS

Install Rancher Manager - v2.8.0 used for testing. PASS

Validate snapshot restore via cluster-reset-restore-path. PASS

Versions tested on:
v1.26.11+k3s2
v1.27.8+k3s2
v1.28.4+k3s2


Release/v0.8.x

@WPringle, the changes in this branch seems to be mostly in examples, and a few lines of modifications in the main code. I don't think it's going to cause any conflicts in merging. Is there any reason for not merging them to main other than failed lint tests? If so, we can spend some time on fixing the lint errors and then merge to main.
So the karhunenloeve_polynomialchaos scripts fully replace the functionality of kl_surrogate scripts?

@SorooshMani-NOAA No reason for not merging in, only Zach didn't have time to review and fix any conflicts.
Yes, the karhunenloeve_polynomialchaos scripts replace the old kl_surrogate ones, and would be nice to have that in main as they were used in the paper.


uploading on save to multiple servers at once

Is this a similar or duplicate feature request?

[ x ] I don't know. I will go check it.
[ ] No.

Is your feature request related to a problem? Please describe.
When I save I would like to upload to multiple servers at once. Currently, I tried profiles and contexts and I can only ever get 1 server to update, unfortunately.
Describe the solution you'd like
Given passwords servers usernames etc I'd lave ALL servers to update on when I do save locally.
Describe alternatives you've considered
Changing what is dev and prod using profiles seems to be the only solution that works for me right now.
Does this project help you?

[x] Yes. SFTP IS AWESOME!
[x] Yes. I want to support you.

So far SFTP seems awesome and would be more than happy to donate even more if this feature is added!  (btw seems there something wrong with donating to you via paypal right now...)

Related issue: https://stackoverflow.com/questions/47058663/visual-studio-code-sftp-to-multiple-servers

related issue: https://github.com/liximomo/vscode-sftp/issues/469#issuecomment-604741469


Uploading a Group Chat custom avatar that is too large shows badly formatted error message

Coming from https://github.com/Expensify/App/pull/39757#issuecomment-2052653886
Reproduction:

Create a Group Chat
Navigate to report details page
Upload a custom avatar that is too large

Expected:
The error message displayed is taking up the normal width of the screen.
Actual:

@Expensify/design I found this inconsistency in the avatar error message, which one is the correct one?

Hmm I think I lean towards the right version being more correct. Thoughts @Expensify/design?

Yeah I think so too. I think it makes more sense with the rest of our app for it to span the full width.

Working on a similar issue on https://github.com/Expensify/App/pull/42088#issuecomment-2109806472. Checking if we can fix that issue there too

Just raised a PR

@marcaaron Can you please assign me this issue as C+ as I reviewed the PR?

@s77rt @c3024 pls apply in upwork thanks - https://www.upwork.com/jobs/~013621cec02e1951b1

@laurenreidexpensify Accepted! Thanks!

@laurenreidexpensify applied, thank you.

Summary:

C+ @s77rt paid $250 via Upwork
Contributor @c3024 paid $250 via Upwork

@s77rt regression step recommendations for this?

@laurenreidexpensify The bug was found during PR review and not entirely a regression. I don't think this is worth adding a test for


How to set customized model path?

I am using a node graph like this:
(
		# MediaPipe graph that performs face mesh with TensorFlow Lite on CPU.
		# Input image. (ImageFrame)
		input_stream: "input_video"
		# Output image with rendered results. (ImageFrame)
		output_stream: "output_video"
		# Collection of detected/processed faces, each represented as a list of
		# landmarks. (std::vector<NormalizedLandmarkList>)
		output_stream: "multi_face_landmarks"
		# Throttles the images flowing downstream for flow control. It passes through
		# the very first incoming image unaltered, and waits for downstream nodes
		# (calculators and subgraphs) in the graph to finish their tasks before it
		# passes through another image. All images that come in while waiting are
		# dropped, limiting the number of in-flight images in most part of the graph to
		# 1. This prevents the downstream nodes from queuing up incoming images and data
		# excessively, which leads to increased latency and memory usage, unwanted in
		# real-time mobile applications. It also eliminates unnecessarily computation,
		# e.g., the output produced by a node may get dropped downstream if the
		# subsequent nodes are still busy processing previous inputs.
		node {
			calculator: "FlowLimiterCalculator"
			input_stream: "input_video"
			input_stream: "FINISHED:output_video"
			input_stream_info: {
				tag_index: "FINISHED"
				back_edge: true
			}
			output_stream: "throttled_input_video"
		}
		# Defines side packets for further use in the graph.
		node {
			calculator: "ConstantSidePacketCalculator"
			output_side_packet: "PACKET:0:num_faces"
			output_side_packet: "PACKET:1:use_prev_landmarks"
			output_side_packet: "PACKET:2:with_attention"
			node_options: {
				[type.googleapis.com/mediapipe.ConstantSidePacketCalculatorOptions]: {
					packet { int_value: 1 }
					packet { bool_value: true }
					packet { bool_value: true }
				}
			}
		}
		# Subgraph that detects faces and corresponding landmarks.
		node {
			calculator: "FaceLandmarkFrontCpu"
			input_stream: "IMAGE:throttled_input_video"
			input_side_packet: "NUM_FACES:num_faces"
			input_side_packet: "USE_PREV_LANDMARKS:use_prev_landmarks"
			input_side_packet: "WITH_ATTENTION:with_attention"
			output_stream: "LANDMARKS:multi_face_landmarks"
			output_stream: "ROIS_FROM_LANDMARKS:face_rects_from_landmarks"
			output_stream: "DETECTIONS:face_detections"
			output_stream: "ROIS_FROM_DETECTIONS:face_rects_from_detections"
		}
		# Subgraph that renders face-landmark annotation onto the input image.
		node {
			calculator: "FaceRendererCpu"
			input_stream: "IMAGE:throttled_input_video"
			input_stream: "LANDMARKS:multi_face_landmarks"
			input_stream: "NORM_RECTS:face_rects_from_landmarks"
			input_stream: "DETECTIONS:face_detections"
			output_stream: "IMAGE:output_video"
		}
	)

This will using a default path of tflite,
Is there a way to set a cusomtized tflite path? In somwhwat reason my project must using a customized path.

one way to specify resource root directory is to use resource_root_dir command line flag
https://github.com/google/mediapipe/blob/ee2f940e1fcc0e07c16afd773250b42ad41b36af/mediapipe/util/resource_util_default.cc#L52
like...
https://github.com/andrechen/mediapipe/blob/6507d32a91618c36df0203ae55b31be16f793276/visualstudio/demo_run_graph_main.cc#L208

@andrechen  Hello, I didn't use absl neither glog.
Also, I think this is not a universal way.
Does there any way to set specific Node model path customized in proto?

Unfortunately, this graph currently doesn't allow custom locations for file names. What environment are you running the graph under? You should be able to set the flag --resource_root_dir to point to any directory or relative path on your system (as you invoke your binary).

@schmidt-sebastian  hello, if graph can not specific, which code/entrance I can set to support? Or how to modify graph node name to set model path (I think it should be supported)
Since you said there is a flag can specific, where does this flag takes effect?
I need manually set model path since my program runs on a relative bin, which should using my path otherwise I don't know where to put these assets.

Unfortunately, this part of the code does not let you specify the path as part of the graph. This is a design decision that we hope to mitigate soon in newer versions of this API (but this could take a while).
I am not sure how you launch your binary. The command line flag above can be passed to the MediaPipe binary as you would pass any other environment variables. Can you let us know how you launch your process? We might be able to help then.

Unfortunately, this part of the code does not let you specify the path as part of the graph. This is a design decision that we hope to mitigate soon in newer versions of this API (but this could take a while).
I am not sure how you launch your binary. The command line flag above can be passed to the MediaPipe binary as you would pass any other environment variables. Can you let us know how you launch your process? We might be able to help then.

like this: .\holistic_tracking_cpu.exe --resource_root_dir asserts
but it do not work, get the error,such as:
Calculator::Open() for node "holisticlandmarkcpu__poselandmarkcpu__poselandmarkbyroicpu__poselandmarkmodelloader__LocalFileContentsCalculator" failed: ; Can't find file: mediapipe/modules/pose_landmark/pose_landmark_full.tflite


Help with using autograd in training with wrapped NN modules

Let's say I have a whole wrapped network made with nn called 'model' and I used the
modelFunction, params = autograd.functionalize(model)
neuralNet = function(params, input, target) ...  return myCustomLoss end
df = autograd(neuralNet)

Now I want to train my model. Since I have my training typical procedure (with the mini-batch closure) already written and ready, I would like to keep most of it, only exploiting the very easy way to get the gradients with autograd.
So let's confront the 2 methods, so that you can tell if that is actually possible.
The usual:
local feval = function(x)
  if x ~= parameters then
     parameters:copy(x)
  end
  -- reset gradients
  gradParameters:zero()

  -- f is the average of all criterions
  local f = 0

  -- evaluate function for complete mini batch
  for i = 1,#inputs do
     -- estimate f
     local output = model:forward(inputs[i])
     local err = criterion:forward(output, targets[i])
     f = f + err

     -- estimate df/dW
     local df_do = criterion:backward(output, targets[i])
     model:backward(inputs[i], df_do)
  end
  -- normalize gradients and f(X)
  gradParameters:div(#inputs)
  f = f/#inputs

  -- return f and df/dX
  return f,gradParameters
  end

So, using autograd while making the smallest changes possible it would be:
-- create closure to evaluate f(X) and df/dX
local feval = function(x)
   -- get new parameters
   if x ~= parameters then
      parameters:copy(x)
   end
   -- reset gradients
   gradParameters:zero()

   -- f is the average of all criterions
   local f = 0

   -- evaluate function for complete mini batch
   for i = 1,#inputs do
      -- estimate f
      local df_do, err, output = df(params,inputs[i],targets[i])
      f = f + err
      model:backward(inputs[i], df_do)
   end

   -- normalize gradients and f(X)
   gradParameters:div(#inputs)
   f = f/#inputs
   -- return f and df/dX
   return f,gradParameters
end

And then going on with using the optim module in the classical way.
Is this not possible/not suggested?

@synchro--  were you successful in doing this? I am mixing optim with wrapped nn modules and getting the following errors:
/Graph.lua:40: bad argument #2 to 'fn' (expecting number or torch.DoubleTensor or torch.DoubleStorage at /tmp/luarocks_torch-scm-1-9261/torch7/generic/Tensor.c:1125)

I have actually never tried in the end. I dropped the project because I was
working on something else, but it's something I could try in the next weeks
let's say.
Keep me up to date if you manage to use optim that way.
On Thu, Mar 23, 2017, 11:06 sebastiangonsal<EMAIL_ADDRESS>wrote:

@synchro-- https://github.com/synchro-- were you successful in doing
this? I am mixing optim with wrapped nn modules and getting the following
errors:
/Graph.lua:40: bad argument #2 to 'fn' (expecting number or torch.DoubleTensor or torch.DoubleStorage at /tmp/luarocks_torch-scm-1-9261/torch7/generic/Tensor.c:1125)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twitter/torch-autograd/issues/169#issuecomment-288672004,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFmzun9DRyVOLkOXVLWNrPtXGd4Llmw6ks5rokQmgaJpZM4LaS2X
.

I can confirm that it is possible to mix optim with wrapped nn modules. Errors that you hit might be features that autograd does not support.

@biggerlambda Thanks. Do you have any example of that?


Source file for the icons

Is the source file (e.g. Photoshop) for the button images available somewhere? I need to design some icons for an Openseadragon plugin my collegae created, but it would be nice to keep them exactly in the same style of the original buttons.

Sadly those images are something like 8 years old...if the original Photoshop file exists, it's probably on a disused machine somewhere on the Microsoft campus.
If you do come up with an icon-free version while you're making your new buttons, it would be great if you could share it here! Also note the alternative icon pack here:
http://openseadragon.github.io/#plugins

The notification I got when you closed this issue acted as a reminder for me that I do have a psd and and some icon-free png's available. Shall I add them to to images folder and create a pull request?

It would be great if you could share your icon set!
I'd actually prefer for you to publish them from your account as an icon pack, like this one:
https://github.com/peterthomet/openseadragon-flat-toolbar-icons
...and then update here:
https://github.com/openseadragon/site-build/blob/master/www/index.html#L174
...to add it in.
Sound good? Hopefully we can get some good variety of icons.

Ok, but what I'm talking about is not really an icon pack. It's just an empty version of the buttons already used in the Openseadragon viewer plus a psd file. Something to be used in case anyone might create a custom plugin and needs to add a button in the same style of the default viewer buttons.

Ah, I see; wonderful! Well, it might still be good to link to them from the "Plugins" section of the homepage, but I agree that it also makes sense to have them here in this repository. The blank icon png files could be useful in the "images" folder, so people can use them directly by adding their own icon on top directly in the HTML/CSS.
The PSD would be useful for people who want to really integrate their icons for the best results. It shouldn't go in the "images" folder, though, because that folder becomes part of the distribution. I suppose it could just go in the root level of the repository here, or it can go in a new folder on the root level or something.
Or maybe the PNGs could go in the "images" folder of this repository and the PSD could go in the "site-build" repository so it's just linked from the webpage. I'm not sure what's best, so I'm open to whatever you think...
Anyway, thank you for putting these together!

@hendriklammers Sorry if my indecision put you off... how about the PNGs go in the images folder and the PSD goes in the root and we call it good?

Ah sorry not at all, just a bit busy at the moment.. I did manage to make the pull request though 😉

Is there a way to unsubscribe from all these emails?  When I click on “mute the thread” I am asked for a github account but I don’t recall ever having one.  However, I am being inundated by these emails and I would like to avoid that.  Also, I don’t recall ever registering or accepting to receive such notifications.
Regards,
Joe Roberts
Sr Staff Product Security Leader
GE Energy Connections
T:<PHONE_NUMBER>
E: joe.roberts<EMAIL_ADDRESS>2018 Powers Ferry Rd
Atlanta GA 30339
USA
GE Imagination at work
Ah sorry not at all, just a bit busy at the moment.. I did manage to make the pull request though 😉
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openseadragon_openseadragon_issues_747-23issuecomment-2D281168439&d=DQMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=csaVkpSIPOBqr_tnavLo2oLgFhoBSnSLA6J_PP-fAbw&m=6wOcTDIlAE1IRClpLGT-u9qm9WNYZd8XaAKyvGoRm1M&s=qP7GGmQxWVohw6MuSD4r2XZBIHaI3j93weuT5WR8QBQ&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AF4L-2DTXim5FkwjJKLTydjlWLZttQOeDAks5ree-2DWgaJpZM4GUbzx&d=DQMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=csaVkpSIPOBqr_tnavLo2oLgFhoBSnSLA6J_PP-fAbw&m=6wOcTDIlAE1IRClpLGT-u9qm9WNYZd8XaAKyvGoRm1M&s=qKNGZXHZqYJc4Seb8o9BEVVLZK4cnFNhjdw4kV9OcCg&e=.

@hendriklammers Thank you!
@tirendel (Joe) I'll e-mail you separately about unsubscribing...

Fixed by #1135


Cannot get gem to work with Rails 5

So I've been trying to get this gem to work with Rails 5 however I'm having no luck.
I have installed the gem and ran bundle
gem 'acts-as-taggable-on', :git => 'https://github.com/mbleigh/acts-as-taggable-on'

Next, I ran the migrations by running
rails acts_as_taggable_on_engine:install:migrations

I added acts_as_taggable to the model
class Work < ApplicationRecord
  has_one_attached :header_image
  has_many_attached :uploads

  acts_as_taggable
end

Next, I added :tag_list to the controller
def work_params
  params.require(:work).permit(:header_image, :title, :description, :website, :tag_list, uploads: [])
end

I added the following to the form

    <%= form.label :tag_list, value: "Tags", class: "block uppercase tracking-wide text-grey-darkest text-xs font-bold mb-2" %>
    <%= form.text_field :tag_list, class: "appearance-none block w-full bg-champagne-dark text-grey-darkest border rounded py-3 px-4 mb-3", placeholder: "Tags", required: true %>

and to render I have
<%= work.tag_list %>

However, on work edit I get the following error:

Any help is appreciated.

Hello, Ben.
This is a known issue currently with ActAsTaggableOn and Rails 5.2. There are two ways to fix it for now with a PR branch in development using git => branch => in your gemfile or using source code from that branch and using a path => in your gem file to the source code in your vendor directory (got this working in production). Here are the links, be sure you're on the Rails 5.2 branch, and let me know if you need any other assistance:
Branch: https://github.com/Fodoj/acts-as-taggable-on/tree/rails-5.2?files=1
Issue: https://github.com/mbleigh/acts-as-taggable-on/issues/874

Please go to here : Pull Request #887 to see all the ready to merge and to use solutions to work with Rails 5.2! It is fully tested and ready to go! It is just missing to merge the changes into the main project!


Added the architecture overview for camundas

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


New Textures for jMAVSim

jMAVSim is a useful simulator, it just looks a bit outdated. This PR updates the rendering & textures:

I added a second texture that looks nice too:

Performance
I tested on my laptop with integrated GPU. The CPU load is the same, and the FPS count it the same as well.
The RAM usage increased from 460MB to 660MB - due to the increased texture resolution. I found a Garbage Collector flag that reduces RAM usage by 100MB down to 560MB. Still quite a lot, but, well, it's java...
Texture source: https://www.hdri-hub.com/free-hdri-environments-for-download
@MaEtUgR @Stifael would be good to test this on different machines.

Nice! Tested it on macOS 10.12 with Oracle Java 8.


Add new regions

Is it possible to add Europe regions to codedeploy plugin following the availability of Codedeploy in Europe Today ?

+1 for eu-west-1 support.

Hi,
The 1.6 version of the plugin released this week should include support for all current CodeDeploy regions. Please re-open and let us know if you have any problems using it!


Anormal CPU usage

Issue description
I have a map with a few markers (~5), when I click on marker the cpu is always working even when the map is longer displayed.
<agm-map *ngIf="isReady"
   [latitude]="filters.city.lat"
   [longitude]="filters.city.lng"
   [zoom]="mapZoom">
   <agm-marker *ngFor="let place of places"
        [latitude]="place.lat"
        [longitude]="place.lng"
        (markerClick)="onSelectPlace(place)">
   </agm-marker>
</agm-map>

    /**
     * On select a place event handler.
     * Emits the selection.
     * @param place
     */
    public onSelectPlace(place: Place): void {
        // this.selectPlace.emit(place);
    }

Current behavior
I've checked with chrome performance tab the activity of my application:

The map is loaded, I do nothing and I can't see no activity. I click on a marker at 6000ms and after I do nothing but I can see an activity even after angular lifecycle OnDestroy.
Expected/desired behavior
No activity after I clicked on a marker after a few second.
angular2 & angular-google-maps version
@angular/cli: 1.4.7
node: 8.6.0
os: linux x64
@angular/animations: 4.4.5
@angular/common: 4.4.5
@angular/compiler: 4.4.5
@angular/core: 4.4.5
@angular/forms: 4.4.5
@angular/http: 4.4.5
@angular/platform-browser: 4.4.5
@angular/platform-browser-dynamic: 4.4.5
@angular/platform-server: 4.4.5
@angular/router: 4.4.5
@angular/cli: 1.4.7
@angular/compiler-cli: 4.4.5
@angular/language-service: 4.4.5
typescript: 2.3.4
@agm/core: ^1.0.0-beta.1

Thanks

possibly related to #796?

I have the same problem. I use @agm/core: 1.0.0-beta.2.
Thanks


Chain has just started, api eth_sendTransaction failed; wait a minute or two, it succeed.

Describe the bug
Chain has just started, api eth_sendTransaction failed; wait a minute or two, it succeed.
To Reproduce
When go run main.go, api eth_sendTransaction ensued, api  eth_getTransactionReceipt returns null.
But wait a minute or two, api eth_sendTransaction succeed, api  eth_getTransactionReceipt returns normal.
Expected behavior
When go run main.go, api eth_sendTransaction ensued and succeed, api  eth_getTransactionReceipt returns normal.
Additional context
It is speculated that it is involved in aspects of sleep time.

has fixed


Create build script to deploy on GitHub Pages

I need to look into this a bit more, but I believe all the utilities needed to run md_to_html.sh can be used with GitHub Actions to publish onto GitHub Pages. It would be super cool and would require zero hosting costs.

This first change will allow a future build script to go through all the markdown files and run md_to_html.sh on all of them. From there, it would then be possible to generate all artifacts easily, and upload them wherever they need to go.

The basics are now here. GitHub Actions will convert all the markdown files to HTML and push the results to the gh-pages branch, which GitHub Pages then picks up and deploys them.
See an example page: https://wiki-knights.github.io/CS-Materials/intro-to-c/printing/printing.html
This is now going to need some styling and navigation, but the raw content is now publicly accessible.


Fix hostvars certs

Add additional fields validation for hostvars dict_object

Fixed missing fields in hostvars dict after second deployment

Mrged into https://github.com/seecloud/automation/pull/25 due to critical dependencies


use separate enums for uniform and sampler binding points

reviewers, I updated the PR with changes to backends.


Api url has changed

I've been using this lib for a couple months, with everything ok.
Now I'm getting this error:
FetchError: request to https://prod-auth.nubank.com.br/api/token failed, reason: write EPROTO<PHONE_NUMBER>93792:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate:../deps/openssl/openssl/ssl/s3_ pkt.c:1498:SSL alert number 42<PHONE_NUMBER>93792:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:../deps/openssl/openssl/ssl/s3_pkt.c:659
I think the api URL has changed to this new url:
https://prod-s0-webapp-proxy.nubank.com.br/api/proxy/AJxL5LBUC2Tx4PB-W6VD1SEIOd2xp14EDQ.aHR0cHM6Ly9wcm9kLWdsb2JhbC1hdXRoLm51YmFuay5jb20uYnIvYXBpL3Rva2Vu

Thanks @pedrolauro. How do I get the new API URL for the /register endpoint?

nice! thanks for pointing it out @pedrolauro, I'm going to take a look soon

Just try to login at Nubank's website and watch for XHR requests into the dev tools Network tab. I found that new URL doing that.
Later I just updated the new url on apis_uri.js file and it worked.

when I first started doing the API wrapper there was an endpoint that enlisted all the other possible ones, if this one still exists maybe we could use it to always be up to date

After you successfully authenticated with that new url (and also the old one), the response includes a range of api's urls, for all kinds of functions for Nubank. But none for Nuconta, though..
Did you guys have seen any way to integrate with NuConta's API?
Btw, why the hell are we discussing this in english? lol =D

Btw, why the hell are we discussing this in english? lol =D
I'm always talking in english at work so I'm on default mode haha, also makes sense if any "gringo" will see this in the future.

About the NuConta I don't think they made it public yet, gonna try to dig on that but probably is not allowed (if anyone from NuBank is reading this, please, let us know!)

summoning @rafaelcorreiapoli

Thanks @grsabreu. One of the urls mentioned by pedrolauro is called "savings". But I don't know how to use that, sorry. There is no documentation :(

Quem consegue me ajudar no básico? Quero testar essa API, mas como faço pra executar o script?

@RNT17 Tente usar
const createNuBank = require("nubank").default;

There's 2 discovery URI's that can be used to get all API endpoints:
https://prod-s0-webapp-proxy.nubank.com.br/api/discovery and https://prod-s0-webapp-proxy.nubank.com.br/api/app/discovery

@danilobarion1986 	cool man. Can you create a PR for us with this change?

@danilobarion1986 cool man. Can you create a PR for us with this change?

I'm developing an automated workflow to get my bills with Ruby because I'm not so familiar with Javascript... When I finish the part of use dynamic URL's I could try to translate it to Javascript and then open a PR here :)

@danilobarion1986 are you considering the qrcode step required to get the "events link"?
I'm also trying to use nubank's api to get my purchase list but from what I'm seeing I will have to use: i) discovery links; ii) login link; iii) lift link; iv) and finally events link.
Do you have a different approach on mind?

@danilobarion1986 are you considering the qrcode step required to get the "events link"?
I'm also trying to use nubank's api to get my purchase list but from what I'm seeing I will have to use: i) discovery links; ii) login link; iii) lift link (which involves reading a qrcode); iv) and finally events link.
Do you have a different approach on mind?

Yes, this is the exact workflow to authenticate. As I said before, I won't be able to make a PR with the javascript code, but I finish my ruby automation (it can be viewed here). Before I made it I tried to use a python automation, but I encounter some errors with it and then decided to roll out my own.

@danilobarion1986 are you considering the qrcode step required to get the "events link"?
I'm also trying to use nubank's api to get my purchase list but from what I'm seeing I will have to use: i) discovery links; ii) login link; iii) lift link (which involves reading a qrcode); iv) and finally events link.
Do you have a different approach on mind?

Yes, this is the exact workflow to authenticate. As I said before, I won't be able to make a PR with the javascript code, but I finish my ruby automation (it can be viewed here). Before I made it I tried to use a python automation, but I encounter some errors with it and then decided to roll out my own.

Thanks!
I'm already finishing an implementation using Javascript following the workflow described above, however, I'm not sure if it fits this api considering it would be a huge breaking change this new qrcode requirement.

Cool @dygufa !
I think that fix the dynamic URI issue and add other login flow, considering QR Code validation, are two different things (If someone is already using login without QR Code, what I don't know if it is possible...).
But if everybody needs a QR Code to log in them I agree with you that is better to launch a new breaking version and deprecate this one

Hi, just passing by to say that I decided to create a project to build a library for Nubank's API with all the QR Code authentication and stuff. Thanks for your ruby project @danilobarion1986, it was a great help. I already made an npm package for it, you can check it here.

Hi, just passing by to say that I decided to create a project to create a JS library for Nubank's API with all the QR Code authentication and stuff. Thanks for your ruby project @danilobarion1986, it was a great help. I already made an npm package for it, you can check it here.

Just saw your comment on the npm lib you wrote, really appreciate man!


Enables pushed app before starting

Fixes #707.
Travis will likely have issues with unrelated tests until #754 is merged.

@johnnyman727 How can I smoke test this update? Should I follow the steps here?
Do you know why some of the controller.js tests are failing?

@HipsterBrown that would be a good smoke test if you have a windows machine. Otherwise, I would just make sure t2 run and t2 push work as expected with t2 init-generated assets.
The controller.js tests are failing because of the t2 update --list tests. Somehow our SSL certs on the build server became invalidated (maybe out of date?) so the http.gets are failing. I made mocks for the requestBuildList function in #292 to get that build working on Travis but it might have been better form to break the fix out into a separate PR. :/ Anyway, once that PR lands, this PR should be green too.

Ok thanks. I'll give that a shot when I get home tonight.
It looks like #292 is nearly ready to be merged but if it still needs some time, it might be worth breaking out those mocks into a separate PR still so we can get this fix merged as well. That's up to you though.

@HipsterBrown Okay, you'e sufficiently persuaded me to stop being lazy. I broke the unit test fix out into #754.

As a matter of principle, this shouldn't land until the tests are green—we're all agreed on that, right?

I've just given appveyor a kick to re-run those tests.

@rwaldron how do you force AppVeyer to re-run the tests?

All green tests means LGTM! 👍

There's a "re-build" button :)


interface to esmlab-data

See
https://github.com/pydata/xarray/blob/aabda43c54c6336dc62cc9ec3c2050c9c656cff6/xarray/tutorial.py

Yep, this is what I thought we would eventually do in esmlab.


self.hoi_data_label_batch[env_ids] = F.one_hot(torch.tensor(skill_label, device=self.device), num_classes=self.condition_size).float() RuntimeError: Index put requires the source and destination dtypes match, got Long for the destination and Float for the source.

Hi,
Thanks for your greast work.

I run the command python skillmimic/run.py --test --task SkillMimicBallPlay --num_envs 16 --cfg_env skillmimic/data/cfg/skillmimic.yaml --cfg_train skillmimic/data/cfg/train/rlg/skillmimic.yaml --motion_file skillmimic/data/motions/BallPlay-M/layup --checkpoint skillmimic/data/models/mixedskills/nn/skillmimic_llc.pth and want to control by Q or W from my keyboard. However, a problem occurred.

  self._reset_random_ref_state_init(env_ids) #V1 Random Ref State Init (RRSI)   File "/home//SkillMimic/skillmimic/env/tasks/skillmimic.py", line 229, in _reset_random_ref_state_init     self.hoi_data_label_batch[env_ids] = F.one_hot(torch.tensor(skill_label, device=self.device), num_classes=self.condition_size).float() RuntimeError: Index put requires the source and destination dtypes match, got Long for the destination and Float for the source.
2. When I run the python skillmimic/run.py --task HRLCircling --cfg_env skillmimic/data/cfg/skillmimic_hlc.yaml --cfg_train skillmimic/data/cfg/train/rlg/hrl_humanoid_discrete_circling.yaml --motion_file skillmimic/data/motions/BallPlay-M/run --llc_checkpoint skillmimic/data/models/mixedskills/nn/skillmimic_llc.pth --headless, it tells me Exception: Unrecognized task! Task should be one of: [BallBalance, Cartpole, CartpoleYUp, Ant, Humanoid, Anymal, FrankaCabinet, Quadcopter, ShadowHand, ShadowHandLSTM, ShadowHandFFOpenAI, ShadowHandFFOpenAITest, ShadowHandOpenAI, ShadowHandOpenAITest, Ingenuity]

Hi Zhongan,
Thank you for bringing these issues to my attention.
I'm pleased to let you know that both problems have been resolved and the code has been updated:
(1) The first issue was due to an improper assignment to self.hoi_data_label_batch in _update_condition. I've corrected this part.
(2) The second issue was caused by the missing import of os in HRLCircling. This has now been fixed.
Please pull the latest version of the code. Let me know if you have any further questions or run into any more issues.


[Feat]: Add health endpoint

Is your feature request related to a problem? Please describe.
I do not want to allow anonymous access to my Zot instance, and I also do not want to set the authorization header (using htpasswd) for my Kubernetes liveness probes, since that will expose a valid authentication header to anyone that has read access to deployments on my Kubernetes clusters.
Describe the solution you'd like
Add a /health or /healthz endpoint to Zot, which just returns HTTP 200. This shows that the server is up and running
Describe alternatives you've considered
Remove the liveness probes, or set a TCP liveness probe up instead, to test if the application listens on the configured port.
Additional context
Multiple issues and other references have been created for this, but they have either been closed with no explanation or explain that it is not needed (which I think it is. It is pretty standard practice for applications running in the cloud).
Some references to existing issues/PRs include: https://github.com/project-zot/zot/issues/1767, https://github.com/project-zot/zot/issues/196, https://github.com/project-zot/zot/issues/2087, and https://github.com/project-zot/zot/pull/197

@AndersBennedsgaard thanks for trying out zot!
Do you want to consider a liveness command instead?
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-liveness-command
^ this would give you more flexibility with curl for example.

That would definitely be a possibility, yes. That would allow for you to mount the credentials as an environment variable from a Secret, instead of having it as plain-text in the Deployment.
However, there is no curl, wget, or anything similar packaged into the Zot container at the moment since it is based on a distroless image, so if I wanted to use exec probes I would have to create a custom build with it.
But I would still prefer a health-check endpoint, to remove the requirement for managing extra credentials just for checking if the service is up. I could also just configure the ingress controller to expose the healthcheck path, if I didn't want users to access it


broken support for AsyncioExecutor

The #13 PR introduced executors into request processing for batched queries. It also broken support for use of AsyncioExecutor from within asyncio context.
When using AsyncioExecutor this line blocks forever:
https://github.com/graphql-python/graphql-server-core/blob/427cccb00ae41fb88e8fcaf89aa64f5edb855394/graphql_server/__init__.py#L137
The get() method is called on Promise that must be awaited in async context, here it will stay pending forever.
Call to wait_until_finished() on executor does not help because get_response is not a coroutine and returns a Promise. Async Promises are not handled by wait_until_finished() method of AsyncioExecutor (code). Even if it was, AsyncioExecutor.wait_until_finished() cannot run from within asyncio context and would fail for any asyncio-based application like aiohttp server.
related issue: https://github.com/graphql-python/graphql-core/issues/67
Fix to the above issue introduces a flag return_promise which is just what we need to handle response in async context.
implementatio details:
https://github.com/graphql-python/graphql-core/commit/b4758b1
https://github.com/graphql-python/graphql-core/commit/895b324
https://github.com/graphql-python/graphql-core/commit/cea224a
This fragment of graphql-core test show hows its intended to be used in asyncio context:
https://github.com/graphql-python/graphql-core/blob/a600f7c662e7a6db7d6b56e7c67bf43925b6b23d/tests_py35/core_execution/test_asyncio_executor.py#L65-L75
The return_promise lets the main application handle waiting for executors to finish its task, so graphql-server-core should respect that.
I found this issue in my aiohttp application (using graphql-python/aiohttp-graphql), all queries would block forever. I had to restrict this package version to <=1.1.1

It seems that the version 1.1.1 of this package isn't available anymore, so this issue is now critical for my project and many others.


New release: Version 0.6.1

Release Checklist
These scripts must pass:

[x] npm run ci:jest-coverage (to fix: add / improve tests!)
[x] npm run ci:npm-outdated (to fix: npx ncu -u, npm install, npm update)
[x] npm run ci:npm-audit (to fix: npx resolve-audit)
[x] npm run frontend:build (to fix: address issues)
[x] npm run docs:build (to fix: address issues)

Manual browser testing:

[x] Chrome
[x] Firefox

Manual browser testing - feature list:

[x] fix "User" filter and top-level chip deselection (see #423 )

Before deployment:

[x] CHANGELOG.md is updated to include details of new release
[x] version bumped to 0.6.1 in package.json using npm version patch
[x] above changes reviewed and merged to master

Deployment:

[x] push to CodeCommit succeeds
[x] deployment to AWS succeeds
[x] #prj_move notified: MOVE back up after new version deployment

Marking closed - this went out last week.


feat: make ServerFormInfo's submittedFormData more type-safe

As suggested by @kentcdodds in https://github.com/brophdawg11/remix-validity-state/issues/7#issuecomment-1245857252 & https://github.com/brophdawg11/remix-validity-state/issues/7#issuecomment-1245875487

Would also be nice to have the type be string (as opposed to string | undefined) when required: true is set.
Example:
type FormValidations = {
	email: Validations
	password: Validations
}

const formValidations: FormValidations = {
	email: {
		type: 'email',
		required: true
	},
	password: {
		required: true
	}
}

export const action = async ({ request }: ActionArgs): Promise<TypedResponse<ActionData | never>> => {
	const { submittedFormData, valid } = await validateServerFormData(await request.formData(), formValidations)
	if (!valid) {
		return badRequest({ formError: `Form not submitted correctly` })
	}

	const { email, password } = submittedFormData
	// const email: string | undefined
}

@MichaelDeBoey Apologies for the delay!  The end of 2022 got super busy but finally getting back to some side projects now.  I've got a PR open for my restructure now so I copied these changes into there - #26.  With the new structure, I can start looking at handling multiple values and supporting string | string[] typings on submittedFormData as well


can not use the funtion: "cv.applyColorMap(img, cv.COLORMAP_JET)"

Hi!
Thanks for your contribution of the code!
I am a little sad when I run "img_out = cv.applyColorMap(img, cv.COLORMAP_JET)", I got an error say that: “attempt to call field 'applyColorMap' (a nil value)”
Does it means that this Torch_Opencv do not support the funtion “applyColorMap" ??
Thanks!

Hi, it works, but you have to require 'cv.imgproc' first. Please study this code and the demos, especially filtering.lua.

Hi!
I am very happy to receive your reply!
Your answer really help me a lot,Thank you very much!
Well, How can i know the usage of such function? Does there have some doc or manual to access, about this torch_opencv?
Hope to receive your answer to this basic question.

Currently, there is no documentation on torch-opencv (sadly). However, the function signatures are mostly compatible with their C++ counterparts, so you can check the OpenCV 3.1.0 C++ reference directly.
For example, there you can find
void cv::rectangle (Mat &img, Rect rec, const Scalar &color, int thickness=1, int lineType=LINE_8, int shift=0)

This means that in torch-opencv you can call rectangle() using the very same names for the function and its parameters. You can also omit some of the parameters (their default values are same as in the docs):
cv.rectangle{img, {100,200,300,400}, {0,255,255}, lineType=cv.LINE_AA}

If there is an output parameter like dst,
void cv::integral (InputArray src, OutputArray sum, int sdepth=-1)

then there are several options to fill it:

Leave it nil, then torch-opencv will create and return a new Tensor:

local img = torch.FloatTensor(100, 200)
local sum = cv.integral{img}
-- or:
local sum = cv.integral{img, nil}
-- or:
local sum = cv.integral{img, sum=nil}

Pass a Tensor of appropriate size:

local img = torch.FloatTensor(100, 200)
local sum = torch.FloatTensor(101, 201)
cv.integral{img, sum}
-- or:
cv.integral{img, sum=sum}

These are the rules for most functions. In rare cases, if something doesn't work as expected or raises an error, then the safest way is to check the code directly at cv/<package-name>/init.lua (for example, here is the cv.rectangle code). It should be clear enough to understand.
Feel free to get in touch with me anyway.


electron-firebase

Link to project (GitHub): https://github.com/david-asher/electron-firebase
Describe the project in 2-3 sentences: Electron-Firebase is a quickstart framework for building cross-platform cloud-connected desktop applications using Electron and Firebase. With a few configuration settings you can include a complete authentication workflow into your app that can use email/password, phone number, google, facebook, or many other identity providers.
Why would Firebase developers be interested in this project?: Electron-Firebase is unusual in being both an NPM module and an example application, and it spans both worlds of the Browser JavaScript environment and the host node.js environment. As such, it will install several folders and files into the root of the NPM application that form the example application, which you are encouraged to modify for your own purposes.
Have you added a .opensource/project.json file to your site: Yes

https://github.com/david-asher/electron-firebase/blob/master/.opensource/project.json

@david-asher looks really cool!  Let me add it to the site now.  I hope those .js.md files don't trip up the script!

Your page should be live on the site within 24h

@david-asher we're making a new site similar to firebaseopensource.com but for all of Google. So it would be one place with projects like yours plus projects from Flutter, Angular, Android, etc.
Would it be ok if I included this project on that site? We're hoping to launch in around 2 months so if you're ok with it I'll add your project and send you a link when it's live.

@david-asher we're making a new site similar to firebaseopensource.com but for all of Google. So it would be one place with projects like yours plus projects from Flutter, Angular, Android, etc.
Would it be ok if I included this project on that site? We're hoping to launch in around 2 months so if you're ok with it I'll add your project and send you a link when it's live.

Hi Sam, absolutely - I'd be delighted to participate!

Hi Sam, absolutely - I'd be delighted to participate!


[BUG] Mantine UI is not working

Describe the bug
Tried to do quickstart with Remix and Mantine, but UI is unstyled
Steps To Reproduce
yarn create refine-app
choose options, Remix and Mantine
start with yarn dev
open the page
Expected behavior
Expected Mantine UI
Screenshot

Desktop
Windows 10
 "@refinedev/cli": "^2.0.0",
    "@refinedev/core": "^4.0.0",

Mobile
No response
Additional Context
No response

Hey @tombohub ,
Thank you for reporting the issue. I created a new Remix and Mantine UI application, but I couldn't reproduce the problem. Is there something I might have missed?
✔ Choose a project template · refine-remix
✔ What would you like to name your project?: · loathsome-trusty
✔ Choose your backend service to connect: · data-provider-custom-json-rest
✔ Do you want to use a UI Framework?: · mantine
✔ Do you want to add example pages?: · inferencer
✔ Do you need any Authentication logic?: · auth-provider-custom
✔ Choose a package manager: · npm
✔ Would you mind sending us your choices so that we can improve superplate? · no

Hello @tombohub, we are closing the issue since we couldn't reproduce it. Feel free to re-open it if your problem persists.

@omeraplak Hi, I've tried again and problem is not there when opening in incognito mode. Thank you


Avoid two  elements for blog section

Change our customizations to Docsy, so that pages in the blog section don't have two <h1> elements.
This snag showed up when we were testing PageFind for search.
/area web-development

@dipesh-rawat thoughts on the best way to fix the spacing and other discrepancies?

https://github.com/kubernetes/website/pull/44665#pullrequestreview-1807925118 is nice observation! An <h2> with a specific target for blog headers can do the job imo

This PR does already select <h2> elements specifically on blog pages (in the CSS selector sense of “select”).

Thanks
/lgtm

/approve


Clearer error report in callwatchers

add catch_backtrace() to display the backtrace in error log to help debugging

Sounds like a sound proposal, thank you very much!
We'll do some testing this week and merge if successful.

Just checked and the error report is really helpful.
Thanks a lot.


Errors in CMakeLists when using c++20 modules

Xmake Version
v2.8.1+master.beafb2d5c
Operating System Version and Architecture
Ubuntu 22.04.3 LTS
Describe Bug
When generating CMakeLists while using c++ 20 modules with gcc-13
The part in cmake responsible for compiling modules will not set appropriate flags, and will not propagate target flags like -g.
Expected Behavior
Correctly set flags
Project Configuration
add_rules("mode.debug", "mode.release")

target("modules_test")
    set_kind("binary")
    set_languages("c++23")
    add_cxxflags("gcc::-fmodules-ts")
    add_files("src/*.cpp", "src/*.ixx")
    add_files("engine/*.ixx")

I use gcc-13
Additional Information and Error Logs
Example of an error
note: C++20 ‘module’ only available with ‘-fmodules-ts’
warning: keyword ‘export’ is deprecated, and is ignored
I fixed it in my local copy of xmake with very dirty hack like so
This from cmakelists.lua 96x lines
`
for _, cmd in ipairs(cmds) do
        local command = _get_command_string(cmd, outputdir)

        if command then

            if string.find(command, "g++") then

                cmakelists:print("    COMMAND %s -fmodules-ts", command)

            else

                cmakelists:print("    COMMAND %s ", command)

            end
        end
    end

`

duplicate. see https://github.com/xmake-io/xmake/issues/3642

try it again. xmake update -s dev https://github.com/xmake-io/xmake/pull/4746
and please update cmake to >= 3.28.0


Swiftmailer 6.0 compatibility

Will there be support for Swiftmailer >=6.0?
I ran into this issue https://github.com/yiisoft/yii2/issues/7848 and had to use 5.4.0 to make it work.

Great!
I just want to remind you that this will break backward compatibility for users still using 5.4. Maybe additional check for newInstance() method existence will help but that's up to you.
Thanks a lot for the quick response!

@nforced I actually tested with both 5.4 and 6.0, the difference between the two versions is the method newInstance being removed, but the classes can still be instantiated as usual.
In v5.4 the following code is equally valid
$transport = \Swift_MailTransport::newInstance();
$transport = new \Swift_SendmailTransport();

phpunit tests are passing with both versions, it should be ok ;)
Thank you for pointing that out!


travis tag deploy

Codecov Report

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

@@           Coverage Diff           @@
##             master    #45   +/-   ##
=======================================
  Coverage       100%   100%
  Complexity        4      4
=======================================
  Files             2      2
  Lines             5      5
=======================================
  Hits              5      5

Continue to review full report at Codecov.

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


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=498307916
https://github.com/Azure/azure-cli-extensions/commit/ae39e8ec6f95a11a511de7f95c398d04f73e4588

OPS Build status updates of commit eda5df0:
:clock10: Preparing: average preparing time is 57 sec(s)

OPS Build status updates of commit eda5df0:
:clock10: Incremental building: average incremental building time is 13 min(s) 49 sec(s)

OPS Build status updates of commit eda5df0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


add "requiredfiles_per_task" in benchmark.xml (especially for VCloud)

Instead of distributing all "requiredfiles" onto all workers (this runs in O(#files * #workers)!), it would be sufficient to send "requiredfiles_per_task" only to the worker for this task (this should need only O(#files)). This is beneficial for witness-checking, precision-re-usage, and everything related to re-using task-based information from a previous benchmark as input for new benchmark-tasks.
The substitution of the substring "${sourcefile_name}" in the "requiredfiles_per_task"-element has to be evaluated once per task.
This issue has to be implemented in benchexec first, then it can be used by other scripts based on benchexec. This issue also requires to modify the script vcloud.py at CPAchecker to simply write the "requiredfiles_per_task" at the end of the task-lines (just like an additional sourcefile, tab-separated). The VCloud itself does not need to be changed.
Example:
By replacing (1) by (2) the files would only be used for the task itself, because only there the name is matching (instead of the wildcard "*" that matches all files.
(1) <requiredfiles>../../test/results/benchmark.2015-05-27_1105.logfiles/test.*.files/output.txt</requiredfiles>
(2) <requiredfiles_per_task>../../test/results/benchmark.2015-05-27_1105.logfiles/test.${sourcefile_name}.files/output.txt</requiredfiles_per_task>

Perhaps the new xml-tag "requiredfiles_per_task" is too much, because "requiredfiles" is already available on "rundefinition"-level. It does not allow substitution. Maybe implementing the task-based substitution of "${sourcefile_name}" might be enough?
Also vcloud.py has code for something like this. Documentation?

The latter suggestion of allowing to use ${inputfile_name} etc. is now implemented for tags contained inside <rundefinition> and <tasks>.
If <requiredfiles> is used directly on the top level this is not done, to allow for a list of globally required files to be handled more efficiently instead of duplicating it per task.