Is finch dead?

No value judgement, I currently rely on it for a few projects and I'm wondering if I should just move on? I'd be happy to merge scala-steward pulls etc to keep it ticking over.

Yea I get the sentiment, and I'd get it if you wanted to move on. We definitely haven't been very active over the last year or so. Sergey and I had talked earlier this year about the next release. The only real thing remaining is to update the docs which was half done in #1231. I think we'll be in a much better spot for getting back to a more regular-ish releases once we've released that. For my part, I haven't had a ton of time in awhile, although I'm hoping to get freed up in the next couple months to work on it.
@sergeykolbasov Maybe it makes sense to post your doc redesign idea for 0.33.0 in an issue (happy to port it over if you don't have time) and see if any other folks can help. We might also consider bring on some more people. Happy to chat about that here or in the maintainers chat.
Not sure if other folks have thoughts here, but would be happy for more input.

Finch is definitly very handfull and pleasant to use, we're glad to have migrated on it.
The only drawback we have meet is with the dependencies updates, on which we would be glad to help maintain as well.

As it stands I'm not dying for features. I think it works well as a library, I think it's more just keeping up with deps shakes fist at jackson.I think a docs refresh would be grand. I have a PR for last year targetting one tiny part of the docs #1274 and it's that kind of thing (references to removed code) I think that makes the project look unmaintained. I think the overall quality of the project is great.

Well, it's gotten to the point where I can't update key dependencies (shapless / circe), adios amigos. Thanks for the ride :)

Can we just onboard new maintainers? I would be happy to help, even if it's just updating dependencies and cutting new releases.

@rpless yes, still interested!

Any update?

@joroKr21 It sounds like you are interested.

Yes, I'd be interested. I hope we can release by just publishing a tag - if not automating releases would be the single most important thing for me.

Sorry for the delay, I have invited both @joroKr21 and @tpetillot to the repo.

I hope we can release by just publishing a tag

So we do have an automated release process, however its not tag based. What we do to trigger the release process is push a commit like this, that removes the -SNAPSHOT part of the version and then CI kicks and handles the release.

So we do have an automated release process, however its not tag based. What we do to trigger the release process is push a commit like this, that removes the -SNAPSHOT part of the version and then CI kicks and handles the release.

Does it mean right after the release you need another commit to add -SNAPSHOT again?

@joroKr21 seems like CI add it back  https://github.com/finagle/finch/commit/78b2f15f62dbaaa89529f4132d315d3f4f4b85c2

@joroKr21 if you're up to, we may discuss the takeover of the updates on https://gitter.im/finagle/finch

Correct, CI will also cut a new snapshot version for you.

Started with https://github.com/finagle/finch/pull/1446 to allow IntelliJ proper indexing.
Next updates will be: finagle, shapeless and circe on which I've not detected any breaking change.
CE3 is not a priority for us ATM, so I guess I'll update as much as possible dependencies under 0.32.2, then bring CE3 under 0.33.0 if you're ok with it?
Let me know if you wish keep an eye from distance, or if I should merge PR on my own (which I'll not until it has been stated).

Next updates will be: finagle, shapeless and circe on which I've not detected any breaking change.

There are a bunch of scala-steward PRs we can merge

@rpless 756cea1a61ae82418ba7c3413f05448d71dde402 release doesn't seems to be triggered, as it's not a Github Action I don't think I have any visibility neither other control on it... Any hint?

Uh I did not realize we were on github actions. Last I checked the we released via Travis CI. It looks like the github action does not invoke ./build/build.sh which is whats needed to release. That also requires some secrets that I don't think I have, I can't move those over to github actions. We might need to delete the github actions setup and go back to Travis CI.
It looks like @sergeykolbasov set github actions up. He probably has more insight.

I'm not sure of which github actions setup you're talking about (currently, on this repository, GA only handle tests).
Indeed, it definitly look like everything is configure for Travis CI.
Hope we'll be able to release soon🙏

I think we may just need to revert this commit for now. I know most people tend to prefer Github Actions these days, but I'm not really sure whats involved in porting the release process to it.

@rpless not sure to understand what you mean.
Is Travis CI still setup? Does it ignore finch repository because of the github actions folder? If removed, would the tests be triggered elsewhere?

Sorry if I was not clear. My guess is that the travis build is not happening due to the github actions folder being there. My guess is that removing it will allow the travis build process to happen. As far as I can tell travis is still configured and has access to the repo.

thank you for your clarifications, just tried and nothing seems to happend. I'm not familiar with travis, but while checking under https://app.travis-ci.com/github/finagle/finch I've a a danger alert at top indicating:

We are unable to start your build at this time. You exceeded the number of users allowed for your plan. Please review your plan details and follow the steps to resolution.

Last build was https://app.travis-ci.com/github/finagle/finch/builds/249090088 on https://github.com/finagle/finch/commit/117129bb2c7089250cb227842e5c05cf579e3ec7 (which seems to be way before github action test was added)

I'm also familiar with github actions, so would be perfect for me.
Hope secret is still in hand! 🙏

Ok so the good news is that Vladimir had the password. I've confirmed that it works and have uploaded it as a Github Actions Secret. Its name is ENCRYPTION_PASSWORD to keep inline with what the script calls it.
I'm not terribly familiar with Github actions, but it does seem like the best way forward. I think if we could get a Github Action that calls the current ./build/build.sh file that would probably be the fastest way forward.

Also, does the release process include sonatype release? or does it require user releasing closed repository?
As I understand it, this is handled by CI. I don't have access to Sonatype but have released things to the Maven Central before with our CI setup.

@rpless thank you so much for digging into this!
I'm also not super familiar with Github Actions but, from what I can tell, if they can run our script, the magic should happen on its own. Anything I can help with at the moment?

i updated the build script to help with this effort #1461
thank you for recovering the password  @vkostyukov !


[bug] V 1.0.2 - Issue with Association  when including custom name

Is there an existing issue for this?

[X] I have searched the existing issues

Is this a regression?

[X] Yes, this used to work before

Current Behavior
We have Rails 7.0 and Blueprinter 1.0.1, and we used to use association with custom name, it was working as expected. However, bump to Rails 7.1 and update all other gems, including Blueprinter, which is V 1.0.2, had an issue with associations and custom names to raise an exception as
ActiveRecord::AssociationNotFoundError:
       Association named 'custom_name' was not found on Classxx; perhaps you misspelled it?

The issue that when we call blueprint.reflections[view].associations inside override pre_render method, the hash came with key for display_name instead of actual association name, which through the exception.
Expected Behavior
If we reverse to old version of Blueprinter, all work as expected
Steps To Reproduce

Upgrade to V 1.0.2
Create a serializer with association

association :class_1, name: :class_2, blueprint: Class1Serializer do |object|
    ....
  end

Environment
- OS: Mac
- Browser Name and version: Chrome Or we can replicated from console terminal
- Ruby Version: <IP_ADDRESS>

Anything else?
No response

Hey @Z-GH! Thanks for reporting!

The issue that when we call blueprint.reflections[view].associations inside override pre_render method, the hash came with key for display_name instead of actual association name, which through the exception.

Could you add a simple version of your custom pre_render code that throws the exception when you get a moment?

Thanks @lessthanjacob , we can do, I was hoping if we can change the gem itself for versioning consistency. However, that works as well.
Thank you.


During the cleanup token process, add support for an event when token is expired.

Hello
I have a third party system that uses the concept of sessions to maintain user state. I need the ability to automatically clean up the sessions in the third party system when the tokens are expired. I would love to have an event that is fired by the token cleanup process so I can implement my logic to clean up the sessions.
I would be willing to help with the work for this feature request if needed.
Thanks,
G

Not a bad idea.

@LindaLawton this might be a nice project given that you mentioned your Friday plans :)

Sounds like fun considering i have not played in the event system yet.    Assign me to it.   I know where to find you if i have any questions free to point me in the correct direction.   The last bug took me four hours to find and five minutes to fix :)

Awesome!! thanks. Let me know if can help.

@LindaLawton Thanks for the support. I am curious to see how things are going. Any updates?
Thanks,
G

I didn't have long to look at it but was unavailable to figure out what even calls it.     its like the setting isn't used anywhere.
I should have some more time to look at it Friday.

@LindaLawton checking in.. how are things going?

unfortunately we had some issues at work that have priority, and now we are into vacation season. I won't have to look at this until the end of August.

How would this event look like?  Just a delegate? Or something from DI? DI is tricky since this token thing runs outside of http requests.

A delegate is fine. Understand the DI complexity.

Ok so turns out i was already resolving stuff from DI in the token cleanup, so we can do a service in DI

ok, done -- and with an interface in DI.

Thank you!! Do you have a unit test to show how it works?

no, but the sample EF host does. if you'd like to add tests, we'd love them

Hi, please can you show some piece of code?
I need to do some stuff when a token is expired, but I cant figure it out
thanks in advance

@gsvitak @brockallen, can you please help me find the piece of code that do this feature? thanks in advance

for future references you should implement IOperationalStoreNotification


Last version not complete.

The latest version din't update __about__.py.

Sorry, that's my bad. I prepared a new release for the first time and forgot about this file. I'll try to fix it.

Should be fixed now!


Bash Update hangs - post build 14342

The Linux sub-system does not get updated
The update for the linux subsystem that starts as a backgroud process hangs after downloading packages

I disabled the linux subsystem, rebooted. Enabled and rebooted
Ran lxrun /uninstall /full /y and then lxrun install - The install appears to complete but the prompt does not return
C:\WINDOWS\system32>bash
-- Beta feature --
This will install Ubuntu on Windows, distributed by Canonical
and licensed under its terms available here:
https://aka.ms/uowterms

Type "y" to continue: y
Downloading from the Windows Store... 100%
Extracting filesystem, this will take a few minutes...
Installation successful!

This is where it hangs
However after this at some time the background update starts but again hangs

I understand this is a beta feature. My reason for posting is to see if I can help debug and or provide some help to improve
regards

What is that you are wanting to update? The WSL subsystem itself is closely tied to Windows and gets updated by Windows update with the new Windows build. The background update task that you are referring to is for reporting updates for user mode Ubuntu binaries that are available, it doesn't update them automatically. Once you are inside of bash, you can update the user mode Ubuntu binaries by doing "sudo apt upgrade" or "sudo apt-get update/upgrade". Does that help?

What is that you are wanting to update? The WSL subsystem itself is closely tied to Windows and gets updated by Windows update with the new Windows build. The background update task that you are referring to is for reporting updates for user mode Ubuntu binaries that are available, it doesn't update them automatically. Once you are inside of bash, you can update the user mode Ubuntu binaries by doing "sudo apt upgrade" or "sudo apt-get update/upgrade". Does that help? Also, 14342 is the latest release Windows build that is publicly available as of now.

Sunil
Let me clarify.
I am not trying to update anything
What I am saying is that the WSL does not get updated and hangs
And then as a result so does  the bas/WSL - and in the end I cant get into the WSL at all
I tried disabling/enabling but it all ends up with WSL update running as part of windows update by itself. Which never completes
Hope this clarifies my issue

@rajendrapande Can you help clarify a few things for me?
When you're talking about WSL update, are you talking about our weekly Scheduled Task that updates the apt package index?  That should only run once a week and when the machine is idle so I doubt that's what you're running into.

I picked up the WSL update as a reference from Sunil.
Sequence is this
Linux subsystem works fine
I do the update for 14342
Post 14342 update the update runs in the background to update the linux subsystem
It hangs - I did not realize it was hanging. Shutdown the machine normally
Upon restart attempted to run bash - it just hung
To resolve I first disable linux subsystem rebooted, enabled and rebooted - no difference. Bash still hangs
Ran lxrun uninstall. Lxrun install
The install completes (_Though the command prompt does not return control - it just stays at install completed)
Then the background update runs again and hangs after downloading packages
And no matter what I do I cant seem to get out of this cycle
Hope this helps

@rajendrapande It would be helpful to us if you could follow these instructions to collect logs so we can investigate further.

Going through old issues.  This one has not moved in 2 months.
Closing out as old.  Please feel free to re-open with more comments if still an issue.

I am still seeing this.  Running Win10 build 14965.rs_prerelease.161104-1700.   Occasionally after I am running WSL Bash, this other window pops up (on its own, not from anything I did) trying to update packages.  It hangs and I cannot get rid of it without close all bash windows.

This is still an issue.  AptPackageIndexUpdate opens in windows cmd, updates package index, then stays open.  It isn't closable by any method I know of.

There is a fix inbound for this issue.


Az upgrade lists different version than it actually installs

Describe the bug
Command Name
az upgrade
Errors:
Your current Azure CLI version is 2.25.0. Latest version available is 2.29.0

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Have installed az version 2.25 (I have not tested it with other versions)
az upgrade

Expected Behavior
Your current Azure CLI version is 2.25.0. Latest version available is 2.45.0

Environment Summary (This was collected after running az upgrade, note that the version was correctly upgraded to 2.45 but the command said 2.29 would be installed)
Windows-10-10.0.22621-SP0
Python 3.10.8
Installer: MSI

azure-cli 2.45.0

Extensions:
communication 1.3.0

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context

@bebound for awareness

Could you please provide the output of az upgrade --debug when you get Your current Azure CLI version is 2.25.0. Latest version available is 2.29.0

I cannot, as I've already upgraded to version 2.45. I only have the history output from the commands that I ran before/after running az upgrade, I've pasted them below if that's of any help.
❯ az --version
azure-cli                         2.25.0 *

core                              2.25.0 *
telemetry                          1.0.6

Extensions:
communication                      1.3.0

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\Andrei\.azure\cliextensions'

Python (Windows) 3.8.9 (tags/v3.8.9:a743f81, Apr  6 2021, 13:22:56) [MSC v.1928 32 bit (Intel)]

Legal docs and information: aka.ms/AzureCliLegal

You have 2 updates available. Consider updating your CLI installation with 'az upgrade'

Please let us know how we are doing: https://aka.ms/azureclihats
and let us know if you're interested in trying out our newest features: https://aka.ms/CLIUXstudy

❯ az upgrade
This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Your current Azure CLI version is 2.25.0. Latest version available is 2.29.0.
Please check the release notes first: https://docs.microsoft.com/cli/azure/release-notes-azure-cli
Do you want to continue? (Y/n): Y

❯ az --version
azure-cli                         2.45.0

core                              2.45.0
telemetry                          1.0.8

Extensions:
communication                      1.3.0

Dependencies:
msal                              1.20.0
azure-mgmt-resource             21.1.0b1

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\Andrei\.azure\cliextensions'

Python (Windows) 3.10.8 (tags/v3.10.8:aaaf517, Oct 11 2022, 16:37:59) [MSC v.1933 32 bit (Intel)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

I figure it out.
In 2.25, CLI use this file to determine the latest version:
https://github.com/Azure/azure-cli/blob/3d14ca21e648f4fc0124132a43156a85a50251cd/src/azure-cli-core/azure/cli/core/util.py#L274
But the master branch has rename to main after 2.29.


Fix hiding of useless comments under Linux

Closes #1536.
The fix is surprisingly simple.
The textContent of the comment is empty (under Linux) if only one or more g-emojis were used. So we can simply check for an empty string.

Perhaps it can be coupled with if select.exists(‘img’, comment) return

@bfred-it, comments containing usefull images are no longer hidden.

Done. :smiley:

Uhm no, just one selector is enough. Just replace 'a' with 'img' on the previous implementation

Mhh, I tried it, but then no useless comments with emojis will be removed if I select  img, like this
if (select.exists('img', commentText)) {
	continue;
}

Oh is it because emojis are images on Linux?
Then the selector should be a img

Yes, now it works. :smile:


Add public equal_metadata_block function

Closes #257

:books: Documentation preview :books:: https://equistore--258.org.readthedocs.build/en/258/

Thanks for the review @Luthaf ! I've made the requested changes, using NotEqualErrors in the _check* functions. Let me know if they're ok!

Do you want to squash the first two commits, or should I squash-merge the whole PR?


PropertyAttribute_legacy tests fails

Hi,
both on Linux/i686 (clang 13) and FreeBSD/amd64 (clang 10) I get two test failures:
         71 - PropertyAttributeTest_legacy (Subprocess aborted)
         72 - PropertyAttributeTest_legacy_optimised (Subprocess aborted)

Please can you show the output of running this test?

I just tried on Linux/i686 and I get other failures now, no longer this one. I'll open a separate one.
I did not remember which FreeBSD system I tested. On my laptop with FreeBSD all tests pass. I will test on my other two FreeBSD systems next week. They are all amd64, I have no 32bit FreeBSD system. If all pass, I'll close this one.


fix: unit test on Windows

Fix:

skip some unit test cases because Windows handles file permissions differently from Unix-based systems, and therefore, using file permissions like 0000, 0600, 0644, or 0700 in tests may not work as expected on Windows.

Test:

unit test on Windows
unit test on Linux

Signed-off-by: Junjie Gao<EMAIL_ADDRESS>

Codecov Report

Merging #651 (4077014) into main (2e56dd4) will decrease coverage by 0.15%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #651      +/-   ##
==========================================
- Coverage   33.16%   33.01%   -0.15%
==========================================
  Files          32       32
  Lines        2014     2014
==========================================
- Hits          668      665       -3
- Misses       1324     1326       +2
- Partials       22       23       +1

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


train_weibo/reddit.pkl?

How to get the train_weibo/reddit.pkl?

You may download via Baidu Disk or Google Storage links in the Intro page.

There is only train/test_persona_dim in Baidu Disk.

I checked the links and update the right one. Thx :)

Thx.

And dev_train/reddit.pkl also be needed.


Error handling

Just wanted to bring this discussion up: should this library handle errors that come from the API?
The thing is that API claims to always return 200 so I think there are different errors that need to be handled

Timeout (when HTTP just does not respond)
HTTP errors (when API fails to respond, like 500, etc)
API errors (error returned in JSON response, codes here). Ideally I'd split these up into 2 categories:

Auth error
Everything else

I think it would be great if this library could handle all of that and provide a common way to deal with it. Currently I'm considering implementing JSON error handling inside of my integration

@krasnoukhov Thanks.
This can be added to roadmap.
Just in case, there is a method in Common model which can return error mappings:
getMessageCodeText

I tried to make client as agnostic as possible (e.g. what you send is what you get).
Currently error handling could be done by wrapping each request with check for errors list:
{'success': False, 'data': [], 'errors': ['API key incorrect'], 'warnings': [], 'info': [], 'messageCodes': [], 'errorCodes': [], 'warningCodes': [], 'infoCodes': []}

Let's keep this thread open so we can discuss how and why we would need to add error handler.
I suggest to make something like raise_for_errors flag optional.

I created a PR that implements these things. I use this approach in this commit in my integration. Let me know if this works

I created a PR that implements these things. I use this approach in this commit in my integration. Let me know if this works

Great! Thanks!


Dead?

No more activity here. Is the project dead?

Pretty much, at least for the time being.
I no longer work in Hack or PHP, so my interest in this project has kind of waned.

OK, thanks.


chore: auto-deploy

[ ] https://docs.travis-ci.com/user/deployment/npm/
[ ] secret key into deploy.api_key.secure

can you please fix lint error and resolve conflict?


Update phpunit, phpbench, easy coding standard

...and some other dependencies

Hello @marmichalski, we will continue?


Update the PyPI package of the ingest-graph-validator to the latest version in the repo (as of 2020-05-28)

Description:
Update the PyPI package, so everybody who wants to install it gets the latest version regardless of the installation route (github repo or pip).
Acceptance criteria:

[x] They PyPI package has been updated to the latest version of the tool in the repo.
[x]  The PyPI package has been tested that it provides the same functionality as the latest version in the git repo. For example, it creates the same set of relationships between nodes for test datasets.

This is fixed in https://github.com/ebi-ait/ingest-graph-validator/pull/26 .

This is fixed in https://github.com/ebi-ait/ingest-graph-validator/pull/26 .


Please add also an ultra-offensive debugger that shitstorms you on every error

Thanks for creating this issue. We think this issue is unactionable or unrelated to the goals of this project. Please follow our issue reporting guidelines.
Happy Coding!


Alpha of color behaving strange when MSAA is on

Release Type: Official Release
Version: <IP_ADDRESS> (latest)
Platform(s): Windows
Describe the bug
The alpha of colors behaves rather weired if MSAA is turned on. In my example I have a pure emissive material where the alpha channel of its white color gets increased over time. One would expect a blending with the background in a linear fashion, but when turning on MSAA one gets a kind of step function based on the amount of MSAA levels.
To Reproduce
See attached project.
MyGame5.zip
Expected behavior
MSAA should not affect alpha blending.
Does the blend state of the MSAAResolver need to be different? Or is it the shader itself - maybe it shouldn't take the alpha values into account at all - at least the referenced original shader doesn't, only loading rgb (https://github.com/TheRealMJP/MSAAFilter/blob/master/MSAAFilter/Resolve.hlsl#L378) and returning alpha = 1 for the final color value.

Close this now, since #836 is merged?

Fixed by #836


Location Tracking not working since 2023.38.x

Hello.
I saw an open ticket for this, but it seems to have gone.  Location tracking still not working since tesla changed API.  Teslamate has this fixed, so it, I assume is possible?

Apologies, I found the original.
https://github.com/alandtse/tesla/issues/756
However, this is marked as fixed, yet I do not see tracking still?

Duplicate of https://github.com/alandtse/tesla/issues/756

@NickWhitNTES if you get latest version (v3.19.3) it should work (I've just upgraded my instance in Home Assistant and can see it working now)

@NickWhitNTES if you get latest version (v3.19.3) it should work (I've just upgraded my instance in Home Assistant and can see it working now)

I think its not offered up in HACS yet?

By default, HACS will poll GitHub every so often to see if there are updates, it might be that this release happened after that poll. You can either wait til HACS does it, or force it to check by clicking the triple dot -> _Update information

I have this version installed, and none of the Teslas added are showing location info on the "Location Tracker".

In which case, if you have the v3.19.3 installed, have rebooted HA and forced synced the data from the car after reboot then it would be worthwhile updating the issue with the bug information requested (version, logs, etc) so that people can investigate. Without that information it is an almost impossible task (esp if it is working for others)

Well, Have you Tried turning it off and on again? :)
Working now, thank you all!


[Documentation] Letter functions using Lob API

Files are here
Pre- work:

Ensure server files of database are open: "Which data models does this function consume"
highlight code snippet for /createLetter (line 159) and type into chat "Explain this function to me"

Tasks for completion:

[ ] addition to inline comments: _/createLetter (line 159) _ and copilot prompt "refactor to be more readable with inline comments"
[ ] addition to wiki: highlight all of the file and ask for a wiki summary for all test codes and add it here https://github.com/ProgramEquity/amplify/wiki/Validating-a-mailing-address

Hi I was wondering if I can work on this. Still very new in my software learning / career but would like to tackle this if possible!

Hi @cadakris are you working on this issue? If you are, would you like to work on this together?

Hey @XicaFelix I actually haven't started working on it. I'd like to work on it together but I won't have time to look at this tomorrow so you can totally take it on.

@cadakris, ok sounds good!

Branch: issue-608

Adding my updates to the task
File to work onhere
Pre- work:

Ensure server api file is open
highlight code snippet for /createLetter function (line 159) and ask Copilot Chat: "Explain this function to me", or use the /explain slash command
try prompting Copilot: "Which data models does this function consume?"

Tasks for completion:

[ ] add inline comments for /createLetter functions (line 159) - highlight the createLetter function and select copilot -> start inline chat
try prompting Copilot: "refactor to be more readable with inline comments"
[ ] addition to wiki: highlight the whole file, ask Copilot for a wiki summary and add it here https://github.com/ProgramEquity/amplify/wiki/Validating-a-mailing-address


GitHub actions and danger

Task
TR #XXX
Why?
CCC Days experiment
What Changed
What changed in this PR?

[ ] Github actions
[ ] Danger

Screenshots
If any UI changes need to be shown off, please add screenshots here.

Can we make parallel_tests a default? It's required to run our tests in parallel on GHA
https://github.com/RoleModel/gimme-credit/blob/main/.github/workflows/ci.yml#L96-L121
https://github.com/RoleModel/gimme-credit/blob/main/Gemfile#L72
https://github.com/RoleModel/gimme-credit/blob/main/.rspec_parallel


Remove proxy checkboxes from options

Never used these checkboxes. No response on IRC or SE so I am assuming its not useful: https://bitcoin.stackexchange.com/questions/109636/understanding-network-options-in-bitcoin-core-gui
Will get some extra space and need to add checkboxes for onlynet next: https://github.com/bitcoin-core/gui/issues/413

The use cases for these check boxes is specifying where to use a proxy and then setting a different proxy for usage with tor.

Can you share docs or steps how is this options being used or helpful?

https://bitcoin.stackexchange.com/a/109651/113152

@hebasto Thanks for answering. Will close this PR as I think removal isn't required although I think some changes or discussion is required because:

I2P is added which uses <IP_ADDRESS>:7656 as proxy
Few PRs are open in bitcoin/bitcoin which change behaviour of proxy and onlynet. It was discussed that proxy is just a proxy and should remain same for all networks if it can be used.


Overlay subscriptions are incompatible with sensor_data publishers

The generic subscription in an overlay plugin is initialized with QoS reliability: reliable.
This makes it incompatible with sensor_data publishers.
There has been a similar discussion in rqt_image_view#41, which led the maintainers to set the default QoS to sensor_data.
Alternatively, a GUI control to set QoS could be added.
Both would solve the issue, I'm not sure about the best option though.
PS: great rqt plugin, thanks!

@Kettenhoax thanks for reporting the issue! I thought I had fixed that a while back in #3, but i had only changed it for the image topic and not for the overlay topics.
This should be resolved by #34, thanks for your contribution.


Issue with LlamaParse chokes if I try to specifically access page 0 (the cover) of a pdf

Page Specification | Target Pages

to fix your trouble check this solution click
maybe this will solve your problem.

Hi @kpkpkp,
This is now fixed. Thanks for reporting it.


#9: Implements mergeSome on a sequence of futures

See #9
This seems like a simpler implementation than what you had done for batchGetSome in Carlos and it seems to work (passes tests similar to merge tests).
The implementation I went with is essentially reduce except with an extra recover to make sure nothing will fail.
We could even refactor this into reduceSome (with some handler for the error case) and then mergeSome is a specialization of that -- however, I can't think of a use for such a method so I just inlined what would be reduceSome inside of mergeSome.
I like what you said re: mergeAll and mergeSome -- I didn't change merge to mergeAll since I'm sure you'll want to deprecate that, but called this method mergeSome.

Sorry for the long wait -- I became unexpectedly very busy last week. As soon as this change (or something similar) is merged and Carlos is upgraded to a new PiedPiper, I can implement batchGetSome.

hi @bkase, I couldn't have done better! Very elegant solution for the mergeSome issue that I didn't manage to solve in batchGetSome!
I'll put the reduceSome idea in the issues, so that I can think whether there could be a use case for it.
I'll also deprecate merge and rename it to mergeAll.
Regarding the new release of PiedPiper to be used from Carlos, I'll do it as soon as I have some spare time, probably in the weekend.
Thanks a lot for your contributions!


Tooltip on Button in btn-group show/hide infinite loop and locking events

Bug description:
The issue is, when a button element inside a btn-group has a uib-tooltip and position is set to top (top-left also seems to cause the issue), when mousing over from the top edge of the button, the tooltip is triggered and hidden infinitely, locking the button and causing a bad visual experience. This only started to occur post migration to the uib prefix. It seems to be caused by a combination of the size of text in the button and the size of the text in the tooltip. Usage in this way to achieve a tooltip on a dropdown button.
It's most noticeable in Firefox. IE and Chrome seem to exit of the infinite loop, though the tooltip will either disappear or mouse move will trigger the show/hide loop.
Link to minimally-working plunker that reproduces the issue:
http://embed.plnkr.co/HbDMwCpv1Ijf6lgLQbIQ/
Version of Angular, UIBS, and Bootstrap
Angular: 1.5.3
UIBS: 1.3.2
Bootstrap: 3.3.6

Add the uib-tooltip directive to the btn-group element instead.  The btn-group-vertical class adds css that doesn't allow the tooltip to grow horizontally, so the text wraps and throws off the vertical positioning.

I can do that for this scenario, but what about if we have a btn-group of different buttons and all require a unique tooltip?

Ah, this looks like a well trodden path. It came down to the classic bootstrap tooltip in btn-group issues which uibTooltipProvider allows you to fix with:
$uibTooltipProvider.options({ appendToBody: true });

I'm not entirely sure what knock-on effects doing this on my entire angular module will have.

Closing as a support issue.

@icfantv perhaps it worthwhile updating the documentation for all controls using button groups and mentioning this as a fix (as bootstrap mention their specific fix to the same issue in their documentation).

@Arkiliknam, happy to consider that.  Can you please link in that documentation reference?  Thanks.

@icfantv, sure. It's found here: http://getbootstrap.com/components/#btn-groups

Tooltips & popovers in button groups require special setting
When using tooltips or popovers on elements within a .btn-group, you'll have to specify the option container: 'body' to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the tooltip or popover is triggered).


Revert "file: 5.35 -> 5.36"

Reverts NixOS/nixpkgs#56126
This worked previously, borg liked it, but having problems fetching now.  Reverting until sorted, sorry!

It may be best to fetch from github: https://github.com/file/file but the tarball hash is different :(.


fix(pgPool): only create one postgres pool to avoid creating too many connections for heroku

Looks to me like pool construction got left behind there after an early refactor, and no app has ever had enough users (thus sessions) to surface connection issues. Beauty! 🙌


add supporto for Sanguino boards (atmega1284p)

Please add support for Sanguino boards (used in 3d printers)
Pins definitions seems wrong with platformio.
Arduino board definition is here:
https://github.com/MarlinFirmware/Marlin/tree/Development/ArduinoAddons/Arduino_1.5.x/hardware/marlin/avr
I successfully compiled and uploaded to this board with platformio using command "platformio init --board=1284p16m" and adding upload_speed = 57600 to platformio.ini, but looks like that pins definitions are wrong.
I can't get proper values (like those returned when compiling and uploading with arduino) for this program:
void setup() {
Serial.begin(9600);
pinMode(17, INPUT);
}
void loop()
{
myread = analogRead(17);
Serial.println(myread);
}
It should return pin 17 analog read (buttons attached to it), instead I get a fixed value coming from nowhere.
Thank you

but looks like that pins definitions are wrong.

This is obvious behaviour, because the "PINs MAP" of 1284p16m isn't equal to Sanguino board. We will add support for this board.


Screen black-out

There are moments where the screen will suddenly, and randomly at that too, go completely black before coming back with everything visible.

Is this still an issue? We'll need more info to assist.


HDInsights 2018-06-01-preview SDK is available but API isn't

👋🏻
I've spent a few hours this morning upgrading to v18 of the SDK - and at the same time looked into moving over to 2018-06-01-preview of the HDInsights SDK. Unfortunately whilst the SDK is available the API isn't (I've checked the Resource Provider and it's not exposed there) - is there a timeframe for this going live?
Thanks :)

@wawon-msft can you please comment?

Ping @wawon-msft, CC @joshgav

The squishy answer I got was "1-2 deployment cycles" which is pretty vague (Tom I think you're on that thread).  In the meantime the recommendation is to use the old API version.  Sorry I don't have a better answer.


Issue with Ubuntu 20.4/gcc 9.3

I just set up a new VM. with Ubuntu 20.4.  When building I get a message related to inlining.  I'm going to switch to Ubuntu 18, like I was using before which worked fine, but I thought you might want to know about it.
[ 88%] Building CXX object quantum/plugins/qsim/CMakeFiles/xacc-qsim.dir/accelerator/QsimAccelerator.cpp.o
In file included from /usr/lib/gcc/x86_64-linux-gnu/9/include/immintrin.h:107,
                 from /home/hellmersjl/github/xacc/tpls/qsim/lib/simulator_avx.h:18,
                 from /home/hellmersjl/github/xacc/tpls/qsim/lib/simmux.h:19,
                 from /home/hellmersjl/github/xacc/quantum/plugins/qsim/accelerator/QsimAccelerator.hpp:22,
                 from /home/hellmersjl/github/xacc/quantum/plugins/qsim/accelerator/QsimAccelerator.cpp:13:
/usr/lib/gcc/x86_64-linux-gnu/9/include/fmaintrin.h: In lambda function:
/usr/lib/gcc/x86_64-linux-gnu/9/include/fmaintrin.h:63:1: error: inlining failed in call to always_inline ‘__m256 _mm256_fmadd_ps(__m256, __m256, __m256)’: target specific option mismatch
   63 | _mm256_fmadd_ps (__m256 __A, __m256 __B, __m256 __C)
      | ^~~~~~~~~~~~~~~

@joehellmers Do you have more information about the system configurations, e.g. full Dockerfile?
I'm using Ubuntu 20.04.1 with gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) and cannot reproduce that error.

@tnguyen-ornl , this is a VirtualBox VM with the latest version of 20.04.1 including doing an "sudo apt-get dist-upgrade".  There isn't anything special about the system.  I created it from scratch and was installing XACC based on the installation instructions in the ReadTheDocs website.
Now I'm getting the same issue on 18.04.1 as well.

@joehellmers Looks like you hit this VirtualBox bug, same compile error reported elsewhere.
Could you please run gcc -march=native -Q --help=target on your VirtualBox instance and let us know the result?

The following options are target specific:
  -m128bit-long-double        		[enabled]
  -m16                        		[disabled]
  -m32                        		[disabled]
  -m3dnow                     		[disabled]
  -m3dnowa                    		[disabled]
  -m64                        		[enabled]
  -m80387                     		[enabled]
  -m8bit-idiv                 		[disabled]
  -m96bit-long-double         		[disabled]
  -mabi=                      		sysv
  -mabm                       		[enabled]
  -maccumulate-outgoing-args  		[disabled]
  -maddress-mode=             		long
  -madx                       		[disabled]
  -maes                       		[enabled]
  -malign-data=               		compat
  -malign-double              		[disabled]
  -malign-functions=          		0
  -malign-jumps=              		0
  -malign-loops=              		0
  -malign-stringops           		[enabled]
  -mandroid                   		[disabled]
  -march=                     		haswell
  -masm=                      		att
  -mavx                       		[enabled]
  -mavx2                      		[enabled]
  -mavx256-split-unaligned-load 	[disabled]
  -mavx256-split-unaligned-store 	[disabled]
  -mavx5124fmaps              		[disabled]
  -mavx5124vnniw              		[disabled]
  -mavx512bitalg              		[disabled]
  -mavx512bw                  		[disabled]
  -mavx512cd                  		[disabled]
  -mavx512dq                  		[disabled]
  -mavx512er                  		[disabled]
  -mavx512f                   		[disabled]
  -mavx512ifma                		[disabled]
  -mavx512pf                  		[disabled]
  -mavx512vbmi                		[disabled]
  -mavx512vbmi2               		[disabled]
  -mavx512vl                  		[disabled]
  -mavx512vnni                		[disabled]
  -mavx512vpopcntdq           		[disabled]
  -mbionic                    		[disabled]
  -mbmi                       		[disabled]
  -mbmi2                      		[disabled]
  -mbranch-cost=<0,5>         		3
  -mcall-ms2sysv-xlogues      		[disabled]
  -mcet-switch                		[disabled]
  -mcld                       		[disabled]
  -mcldemote                  		[disabled]
  -mclflushopt                		[disabled]
  -mclwb                      		[disabled]
  -mclzero                    		[disabled]
  -mcmodel=                   		[default]
  -mcpu=
  -mcrc32                     		[disabled]
  -mcx16                      		[enabled]
  -mdispatch-scheduler        		[disabled]
  -mdump-tune-features        		[disabled]
  -mf16c                      		[disabled]
  -mfancy-math-387            		[enabled]
  -mfentry                    		[disabled]
  -mfentry-name=
  -mfentry-section=
  -mfma                       		[disabled]
  -mfma4                      		[disabled]
  -mforce-drap                		[disabled]
  -mforce-indirect-call       		[disabled]
  -mfp-ret-in-387             		[enabled]
  -mfpmath=                   		sse
  -mfsgsbase                  		[enabled]
  -mfunction-return=          		keep
  -mfused-madd
  -mfxsr                      		[enabled]
  -mgeneral-regs-only         		[disabled]
  -mgfni                      		[disabled]
  -mglibc                     		[enabled]
  -mhard-float                		[enabled]
  -mhle                       		[enabled]
  -miamcu                     		[disabled]
  -mieee-fp                   		[enabled]
  -mincoming-stack-boundary=  		0
  -mindirect-branch-register  		[disabled]
  -mindirect-branch=          		keep
  -minline-all-stringops      		[disabled]
  -minline-stringops-dynamically 	[disabled]
  -minstrument-return=        		none
  -mintel-syntax
  -mlarge-data-threshold=<number> 	65536
  -mlong-double-128           		[disabled]
  -mlong-double-64            		[disabled]
  -mlong-double-80            		[enabled]
  -mlwp                       		[disabled]
  -mlzcnt                     		[enabled]
  -mmanual-endbr              		[disabled]
  -mmemcpy-strategy=
  -mmemset-strategy=
  -mmitigate-rop              		[disabled]
  -mmmx                       		[enabled]
  -mmovbe                     		[enabled]
  -mmovdir64b                 		[disabled]
  -mmovdiri                   		[disabled]
  -mmpx                       		[disabled]
  -mms-bitfields              		[disabled]
  -mmusl                      		[disabled]
  -mmwaitx                    		[disabled]
  -mno-align-stringops        		[disabled]
  -mno-default                		[disabled]
  -mno-fancy-math-387         		[disabled]
  -mno-push-args              		[disabled]
  -mno-red-zone               		[disabled]
  -mno-sse4                   		[disabled]
  -mnop-mcount                		[disabled]
  -momit-leaf-frame-pointer   		[disabled]
  -mpc32                      		[disabled]
  -mpc64                      		[disabled]
  -mpc80                      		[disabled]
  -mpclmul                    		[enabled]
  -mpcommit                   		[disabled]
  -mpconfig                   		[disabled]
  -mpku                       		[disabled]
  -mpopcnt                    		[enabled]
  -mprefer-avx128
  -mprefer-vector-width=      		none
  -mpreferred-stack-boundary= 		0
  -mprefetchwt1               		[disabled]
  -mprfchw                    		[disabled]
  -mptwrite                   		[disabled]
  -mpush-args                 		[enabled]
  -mrdpid                     		[disabled]
  -mrdrnd                     		[enabled]
  -mrdseed                    		[disabled]
  -mrecip                     		[disabled]
  -mrecip=
  -mrecord-mcount             		[disabled]
  -mrecord-return             		[disabled]
  -mred-zone                  		[enabled]
  -mregparm=                  		6
  -mrtd                       		[disabled]
  -mrtm                       		[disabled]
  -msahf                      		[enabled]
  -msgx                       		[disabled]
  -msha                       		[disabled]
  -mshstk                     		[disabled]
  -mskip-rax-setup            		[disabled]
  -msoft-float                		[disabled]
  -msse                       		[enabled]
  -msse2                      		[enabled]
  -msse2avx                   		[disabled]
  -msse3                      		[enabled]
  -msse4                      		[enabled]
  -msse4.1                    		[enabled]
  -msse4.2                    		[enabled]
  -msse4a                     		[disabled]
  -msse5
  -msseregparm                		[disabled]
  -mssse3                     		[enabled]
  -mstack-arg-probe           		[disabled]
  -mstack-protector-guard-offset=
  -mstack-protector-guard-reg=
  -mstack-protector-guard-symbol=
  -mstack-protector-guard=    		tls
  -mstackrealign              		[disabled]
  -mstringop-strategy=        		[default]
  -mstv                       		[enabled]
  -mtbm                       		[disabled]
  -mtls-dialect=              		gnu
  -mtls-direct-seg-refs       		[enabled]
  -mtune-ctrl=
  -mtune=                     		haswell
  -muclibc                    		[disabled]
  -mvaes                      		[disabled]
  -mveclibabi=                		[default]
  -mvect8-ret-in-mem          		[disabled]
  -mvpclmulqdq                		[disabled]
  -mvzeroupper                		[enabled]
  -mwaitpkg                   		[disabled]
  -mwbnoinvd                  		[disabled]
  -mx32                       		[disabled]
  -mxop                       		[disabled]
  -mxsave                     		[enabled]
  -mxsavec                    		[disabled]
  -mxsaveopt                  		[disabled]
  -mxsaves                    		[disabled]

  Known assembler dialects (for use with the -masm= option):
    att intel

  Known ABIs (for use with the -mabi= option):
    ms sysv

  Known code models (for use with the -mcmodel= option):
    32 kernel large medium small

  Valid arguments to -mfpmath=:
    387 387+sse 387,sse both sse sse+387 sse,387

  Known indirect branch choices (for use with the -mindirect-branch=/-mfunction-return= options):
    keep thunk thunk-extern thunk-inline

  Known choices for return instrumentation with -minstrument-return=:
    call none nop5

  Known data alignment choices (for use with the -malign-data= option):
    abi cacheline compat

  Known vectorization library ABIs (for use with the -mveclibabi= option):
    acml svml

  Known address mode (for use with the -maddress-mode= option):
    long short

  Known preferred register vector length (to use with the -mprefer-vector-width= option):
    128 256 512 none

  Known stack protector guard (for use with the -mstack-protector-guard= option):
    global tls

  Valid arguments to -mstringop-strategy=:
    byte_loop libcall loop rep_4byte rep_8byte rep_byte unrolled_loop vector_loop

  Known TLS dialects (for use with the -mtls-dialect= option):
    gnu gnu2

  Known valid arguments for -march= option:
    i386 i486 i586 pentium lakemont pentium-mmx winchip-c6 winchip2 c3 samuel-2 c3-2 nehemiah c7 esther i686 pentiumpro pentium2 pentium3 pentium3m pentium-m pentium4 pentium4m prescott nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client icelake-server cascadelake bonnell atom silvermont slm goldmont goldmont-plus tremont knl knm intel geode k6 k6-2 k6-3 athlon athlon-tbird athlon-4 athlon-xp athlon-mp x86-64 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 btver1 btver2 generic native

  Known valid arguments for -mtune= option:
    generic i386 i486 pentium lakemont pentiumpro pentium4 nocona core2 nehalem sandybridge haswell bonnell silvermont goldmont goldmont-plus tremont knl knm skylake skylake-avx512 cannonlake icelake-client icelake-server cascadelake intel geode k6 athlon k8 amdfam10 bdver1 bdver2 bdver3 bdver4 btver1 btver2 znver1 znver2

I built and test the tnguyen/fix-virtual-box-qsim-build branch and it seems to have worked fine, including all tests passing.
Will you be merging this with master at eclipse/xacc, or is it something I would just need to do whenever I'm doing work on VirtualBox?

Thanks @joehellmers for checking the fix. Yea, I've submitted a PR to get it merged.

Thanks @joehellmers for checking the fix. Yea, I've submitted a PR to get it merged.


Fix: Lack of Garbage Collection

Fixes a bug that instantiates a new tooltip on each call to _on_mouse_entered() without destroying it when _on_mouse_exited() is called.
Creates and stores the tooltip on _ready() and just reuses it, improving memory and performance.
Also added some error handling to prevent crashes if a panel isn't assigned.

Forgot to pull the latest changes before this merge request.


Three column conflict resolution view

A three column git merge conflict resolution view could be really useful. Currently, a single column is used, showing both incoming changes and changes from HEAD, as well as the eventual merged state.
An alternative to this would be to use three columns for the three different states, ie. incoming changes on the left, the state of HEAD on the right, and the output of the merge once changes are picked in the centre column.
Sublime Merge has a similar implementation.

Closing as this is a duplicate of #37350


[#226] Use lexical variable for saved buffer hash

Should help with https://github.com/radian-software/apheleia/issues/226 although there is a second problem related to performance also reported in that thread, which would not be helped with this.
Mostly indentation changes.

This uses the lexical variable approach suggested by @DinoChiesa, which I think is the best solution. There is a second thing mentioned in https://github.com/radian-software/apheleia/issues/226#issuecomment-1769166750, which is that we should perhaps only allow the results of the last (most recent) formatting operation to be applied, rather than whichever one happens to finish first. I think this implementation should actually achieve that as a side effect.
In the following cases the "earlier formatter" and "second formatter" are two instances of the same formatter. Chained formatters are configured to run in series, and that is not what is happening in #226.
Case 1: no changes to buffer between when the two format operations start. The formatter makes no changes to the buffer. In this case it doesn't matter which order the formatters finish in because neither will make any changes.
Case 2: no changes to buffer between when the two format operations start. The formatter wants to make some changes to the buffer. If the earlier formatter finishes first then its changes will invalidate the saved buffer hash from the second formatter so the second formatter's changes will not be applied. The same happens if the later formatter finishes first. Either way only one formatter runs, and since there were no changes to the buffer between when the two format operations start, the output should be the same in both cases.
Case 3: the buffer was modified between when the two format operations start. If the earlier formatter finishes first, it will abort because the buffer hash changed. The second formatter will be able to apply its changes (or it won't have any to apply) because the buffer hash has not changed since it started. If the later formatter finishes first, the same thing will happen. The earlier formatter will still abort as before... unless the buffer modification is actually reverted by the later formatter which finished first. In that case the earlier formatter will indeed get to run as well. However that should be fine because it will have the same effect as running the same formatter twice, no data will be lost.


[RFC] Use DataFrame.query() in df_filter_tasks()

Allow using the query language of pandas for filtering dataframes. Since it can be slower for small input and lead to MemoryError or ValueError for very large queries, abstract over it to allow both regular indexing and query building.
TODO: If that is deemed to be an interesting feature, the query building blocks might be turned into classes with overloaded operators, so that it's possible to write code once and then choose the method of evaluation separately.

Closing as DataFrame.query() is unreliable due to some limitations in numexpr parser.


Fix onHover not always populating for library references

Cases like let foobar = Table.AddColumn| failed to provide onHover details. This is because I returned EmptyHover in localDocumentSymbolProvider instead of the expected null value. It got by the existing tests as I was only testing providers in isolation.

Merging with #114 to prevent needing an additional version bump.


Imported events in remote calendars should appear in the proper spot for the user's local time

I have an event in my Office 365 Calendar that was created by a colleague in America.  The event is scheduled for 8.30am their time but 12:30 my time.  Outlook shows the event in my diary correctly at 12:30 but when I import this via the ics import it shows up in Full Calendar at 8:30 in the morning.
Is there something I can do to fix this or is it an issue with the ics import ?

Timezones are notoriously tricky and right now, I'm assuming that the time given in the ics import is the time that an event should be displayed. I'll need to dig deeper into the ICS spec to pull out timezone information, and allow users to set their local timezone. I'll put this in the queue of bugs to work on!

Adding a "help wanted" label to this ticket because timezones are notoriously difficult, but if anyone is interested in working on this problem, it would be greatly appreciated!

+1 for a google calendar on macos. timezones def tricky af.

Thanks very much
On Tue, 15 Mar 2022, 21:38 Davis Haupt, @.***> wrote:

Timezones are notoriously tricky and right now, I'm assuming that the time
given in the ics import is the time that an event should be displayed. I'll
need to dig deeper into the ICS spec to pull out timezone information, and
allow users to set their local timezone. I'll put this in the queue of bugs
to work on!
—
Reply to this email directly, view it on GitHub
https://github.com/davish/obsidian-full-calendar/issues/66#issuecomment-1068497058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEV5W55AWJNPP4ZJIHWSPTDVAD7LPANCNFSM5QYA5MIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

In the meanwhile, this manual change at obsidian-full-calendar/main.js is doing the job for my .ics files:
function expandICalEvents2(iCalExpander, range) {
  let rangeStart = addDays(range.start, -1);
  let rangeEnd = addDays(range.end, 1);
  let iCalRes = iCalExpander.between(rangeStart, rangeEnd);
  let expanded = [];
  for (let iCalEvent of iCalRes.events) {
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
//    start: iCalEvent.startDate.toString(),
//      end: specifiesEnd2(iCalEvent) && iCalEvent.endDate ? iCalEvent.endDate.toString() : null
start: moment(new Date(new Date(iCalEvent.startDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.startDate.timezone) > -1 ? iCalEvent.startDate.timezone : Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 ))).format("YYYY-MM-DDTHH:mm:ss"),
end: specifiesEnd2(iCalEvent) && iCalEvent.endDate ? moment(new Date(new Date(iCalEvent.endDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.endDate.timezone) > -1 ? iCalEvent.endDate.timezone : Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 )).toString()).format("YYYY-MM-DDTHH:mm:ss") : null
    }));
  }
  for (let iCalOccurence of iCalRes.occurrences) {
    let iCalEvent = iCalOccurence.item;
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
//      start: iCalOccurence.startDate.toString(),
//      end: specifiesEnd2(iCalEvent) && iCalOccurence.endDate ? iCalOccurence.endDate.toString() : null
start: moment(new Date(new Date(iCalOccurence.startDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.startDate.timezone) > -1 ? iCalEvent.startDate.timezone : Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 ))).format("YYYY-MM-DDTHH:mm:ss"),
end: specifiesEnd2(iCalEvent) && iCalOccurence.endDate ? moment(new Date(new Date(iCalOccurence.endDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.endDate.timezone) > -1 ? iCalEvent.endDate.timezone : Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 )).toString()).format("YYYY-MM-DDTHH:mm:ss") : null
    }));
  }
  return expanded;
}

Previous code:
function expandICalEvents2(iCalExpander, range) {
  let rangeStart = addDays(range.start, -1);
  let rangeEnd = addDays(range.end, 1);
  let iCalRes = iCalExpander.between(rangeStart, rangeEnd);
  let expanded = [];
  for (let iCalEvent of iCalRes.events) {
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
    start: iCalEvent.startDate.toString(),
      end: specifiesEnd2(iCalEvent) && iCalEvent.endDate ? iCalEvent.endDate.toString() : null
    }));
  }
  for (let iCalOccurence of iCalRes.occurrences) {
    let iCalEvent = iCalOccurence.item;
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
      start: iCalOccurence.startDate.toString(),
      end: specifiesEnd2(iCalEvent) && iCalOccurence.endDate ? iCalOccurence.endDate.toString() : null
    }));
  }
  return expanded;
}

I know it isn't DRY, but it's easier this way to update the file using a bash+sed command.

@FabianoLothor didn't work out for me. Do you happen to have any tips on troubleshooting this thing? It's a real deal breaker for me, cause I have team members in 5 different timezones (from -11 to +3 hours from me) and calendar records are all in the wrong places.

thnaks for this.  It messes up all day events.  Shows the event as during the day and busy and not in the all day header only.

Hey guys, sorry to hear about that, just revert the code and your ics events will be in the right place again.
@vlitvin it's hard to say my friend.
Basically what the code is doing is passing the right startDate and endDate based on the object provided by the ics file.
Everything will depend on how the ics file is returning the things.
If you want to dig, add a breakpoint or a console.log after the lines below:
here:
  for (let iCalEvent of iCalRes.events) {
    console.log(iCalEvent.startDate.toString(), iCalEvent.startDate.timezone, iCalEvent.endDate.toString(), iCalEvent.endDate.timezone)

and here:
  for (let iCalOccurence of iCalRes.occurrences) {
    let iCalEvent = iCalOccurence.item;
    console.log(iCalOccurence.startDate.toString(), iCalEvent.startDate.timezone, iCalOccurence.endDate.toString(), iCalEvent.endDate.timezone)

Those are the data that I'm using to convert the toString to my timezone.
It's tricky, indeed, because sometimes the ics doesn't provide the right unix-timestamp,
I'll update the code in the end of this week to something more clear and DRY to make it more understandable.

In the meanwhile, this manual change at obsidian-full-calendar/main.js is doing the job for my .ics files:
function expandICalEvents2(iCalExpander, range) {
  let rangeStart = addDays(range.start, -1);
  let rangeEnd = addDays(range.end, 1);
  let iCalRes = iCalExpander.between(rangeStart, rangeEnd);
  let expanded = [];
  for (let iCalEvent of iCalRes.events) {
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
//    start: iCalEvent.startDate.toString(),
//      end: specifiesEnd2(iCalEvent) && iCalEvent.endDate ? iCalEvent.endDate.toString() : null
start: iCalEvent.startDate.timezone ? moment(new Date(new Date(iCalEvent.startDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.startDate.timezone) > -1 ? iCalEvent.startDate.timezone: Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 ))).format("YYYY-MM-DDTHH:mm:ss") : iCalEvent.startDate.toString(),
end: specifiesEnd2(iCalEvent) && iCalEvent.endDate ? ( iCalEvent.endDate.timezone ? moment(new Date(new Date(iCalEvent.endDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.endDate.timezone) > -1 ? iCalEvent.endDate.timezone : Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 )).toString()).format("YYYY-MM-DDTHH:mm:ss") : iCalEvent.endDate.toString()) : null
    }));
  }
  for (let iCalOccurence of iCalRes.occurrences) {
    let iCalEvent = iCalOccurence.item;
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
//      start: iCalOccurence.startDate.toString(),
//      end: specifiesEnd2(iCalEvent) && iCalOccurence.endDate ? iCalOccurence.endDate.toString() : null
start: iCalEvent.startDate.timezone ? moment(new Date(new Date(iCalOccurence.startDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.startDate.timezone) > -1 ? iCalEvent.startDate.timezone : Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 ))).format("YYYY-MM-DDTHH:mm:ss") : iCalOccurence.startDate.toString(),
end: specifiesEnd2(iCalEvent) && iCalOccurence.endDate ? ( iCalEvent.endDate.timezone ? moment(new Date(new Date(iCalOccurence.endDate.toString()).getTime() + (((new Date().setMilliseconds(0) - Date.UTC.apply(null, new Date().toLocaleString("ja", { timeZone: Intl.supportedValuesOf('timeZone').indexOf(iCalEvent.endDate.timezone) > -1 ? iCalEvent.endDate.timezone : Intl.DateTimeFormat().resolvedOptions().timeZone }).split(/[/\s:]/).map((p, i) => i === 1 ? 0 : p))) / 60 / 1000 - new Date().getTimezoneOffset()) * 60 * 1000 )).toString()).format("YYYY-MM-DDTHH:mm:ss") : iCalOccurence.endDate.toString()) : null
    }));
  }
  return expanded;
}

Previous code:
function expandICalEvents2(iCalExpander, range) {
  let rangeStart = addDays(range.start, -1);
  let rangeEnd = addDays(range.end, 1);
  let iCalRes = iCalExpander.between(rangeStart, rangeEnd);
  let expanded = [];
  for (let iCalEvent of iCalRes.events) {
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
    start: iCalEvent.startDate.toString(),
      end: specifiesEnd2(iCalEvent) && iCalEvent.endDate ? iCalEvent.endDate.toString() : null
    }));
  }
  for (let iCalOccurence of iCalRes.occurrences) {
    let iCalEvent = iCalOccurence.item;
    expanded.push(__spreadProps(__spreadValues({}, buildNonDateProps2(iCalEvent)), {
      start: iCalOccurence.startDate.toString(),
      end: specifiesEnd2(iCalEvent) && iCalOccurence.endDate ? iCalOccurence.endDate.toString() : null
    }));
  }
  return expanded;
}

I know it isn't DRY, but it's easier this way to update the file using a bash+sed command.
The code won't work for all use cases, invalid ISO Timezones will be ignored and the default timezone will take its place.
Also, the code assumes that moment will be available, I tried to avoid it, but I didn't find a way to get new Date().toJSON() using its timezone, it always returns using UTC.

How did you apply this change? Did you fork the repo and load this script locally?


add new device: Samsung Galaxy S9 (starqltechn)

@ValerieOSS If you're not sure it's available, don't try it.

have you verified on your device that it can boot?


⚠ Bofrost.de has degraded performance

In 36b91c9, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1486 ms

Resolved: Bofrost.de performance has improved in bb17174.


failing test for css/js source maps

@rickharrison, I took a few minutes yesterday to take a peek at a fix for the css sourcemap issue when the sourcemap name contains the css name.  (application.css => application.css.map)
I am thinking that the best place to fix it is in this project, and here are some broken tests.  When I get some time, I will dig into the rewrite strategy for this case.

Current coverage is 100% (diff: 100%)

Merging #49 into master will not change coverage

@@           master   #49   diff @@
===================================
  Files           1     1
  Lines          85    85
  Methods        12    12
  Messages        0     0
  Branches       20    20
===================================
  Hits           85    85
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 0aa76dc...2dc7b3e

HI @rickharrison, I have fixed the css/js source map issue by preventing a replacement of a filename in itself.  For example, we will not replace styles.css in styles.css or styles-fp1.css.  This will prevent the map file from being replaced twice.  My PR on broccoli-asset-rev should pass after this is merged.  I think we should update the broccoli-asset-rewrite dependency and merge the tests in the failing tests PR I created a couple days ago.  Thanks and I hope you have/had a happy Thanksgiving.

Thanks for writing this fix. I believe this should be sound as I don't know why you would ever need to reference the file inside of itself. I'd like to get a second opinion from the ember cli team if you don't mind.

Sounds good.  Thanks for the response.

Hi @rickharrison, have you had any discussion on this PR with the ember cli team?  I am open to applying different strategies.  I just thought this was the simplest.


[UI] Connection Wizard: Change adapter logos

Current Behavior
In Meshery Adapters step, currently, we use the same icon for all adapters.
Desired Behavior
We should be using the respective logos for each service mesh adapter.
Implementation
Follow the same strategy used in Dashboard component to render service mesh icons based on the name of adapter. If an adapter is unknown, use Meshery logo instead.
Acceptance Tests

[ ] Respective service mesh icons are displayed for each adapter
[ ] If an adapter is unknown, Meshery logo should be rendered instead

Contributor Guides and Resources

🎨 Wireframes and designs for Meshery UI in Figma
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

@sudo-NithishKarthik taking on this issue😃

Its all yours 🚀


Fix PeriodicClockAligned typo in MonitorEnumType

Hi!
There is a typo in the MonitorEnumType which caused some deserialization errors for me.

+1. issue persists for me as well

Sorry, there is not much activity on the repository, I will try to be active on it


Update hdinsight-plan-virtual-network-deployment.md

Added load balancer guidance

@sreekzz

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Fix hooks error in default column cell renderer

React Hooks "useState" && "useEffect" are called in function "cell" that is neither a React function component nor a custom React Hook function. React component names must start with an uppercase letter. So I simply capitalized the C to fix this error.

cell is just a function that can return JSX, not a component itself. There should be no error here.
And this would be a huge breaking change throughout all of TanStack Table, as it is referenced as cell everywhere else in the api and codebase.
You should still be able to run react hooks in other components defined in cell?
I do like the idea of cell, header, etc. being capitalized to indicate they can have component markup, but we can't just make this breaking change here.

You can still see this error in your example -line 32/40- sandbox
After I did the fix my code worked without any problems so I wanted to share my experience here incase anyone faces this issue in the future.
thanks

@MertHaddad Thanks Mert.
You can not see the error because have no lint check? I think that should be fixed, bad code.

@MertHaddad @KevinVandy
i have a columns like this : export const columns: ColumnDef<Post>[] = [{
{
     id: 'actions',
    cell: ({ row }) => {
         const { push } = useRouter();   <=======
         const editPost = (id: string) => {
             push(`/dashboard/posts/edit/${id}`);
         };
         return (....

i get this error : React Hook "useRouter" is called in function "cell" that is neither a React function component nor a custom React Hook function.
how can i fix this? can i pass the id value to the main component?
thank you!

If there is anyone having this problem in 2024, check this out:
https://github.com/TanStack/table/discussions/4205


Redisson doesn't clean idle connections

I use the next configuration:
        config.useSingleServer().setAddress(endpoint)
        .setIdleConnectionTimeout(2000)
        .setConnectionPoolSize(10)
        .setConnectionMinimumIdleSize(3)
        .setPingConnectionInterval(0);

Why idle connections does not clearing by redisson ?

Unable to reproduce. Can you set debug logging level for org.redisson.connection.IdleConnectionWatcher and share output?

I can see that validateAmount method is always return false result. And don't go down to check idleTimeout.

minimumAmount is 3 as well as connections amount. IdleConnectionWatcher won't close connections until idle connections amount became greater than 3.


Researcher ID (still) doesn't display

On my CV and on compiling the template in the current repo, academic icons properly display except for the Researcher ID symbol.
I can load the academicons package on my system and compile with XeLaTeX to display it using the corrected call (pull request #28 - also verified the old call was wrong).
Can anyone reproduce this?

fixed, see my current pull request.

fixed, see my current pull request.


Help: How to integrate temperature sensor

I'm the guy on twitter who asked for the netamo integration :)
I'm trying to integrate a temperature sensor. I can access the temperature via simple http requests. Can I adapt the thermometer class for this?
https://github.com/brutella/hc/blob/master/model/accessory/thermometer.go
I tried adding the temperature sensor to my devices like follows:
thermometer_info := model.Info{
	Name:         "Netatmo",
	SerialNumber: "001",
	Manufacturer: "Netatmo",
	Model:        "Thermostaty",
	}

	model_thermometer := accessory.NewTemperatureSensor(thermometer_info, 10, 0, 100, 1)

But this will obviously give me 10°C as the temperature. Is there a func called when I access the sensor device via homekit? I would put the http call there. Thanks!

As you can see from the NewTemperatureSensor method, the second argument is the temperature.
You can update the temperature using the SetTemperature(...) method.
I would recommend repeatedly update the temperature every x seconds.


adding unittest for MKLDNN Softmax operator

Description
Adding Unittest for softmax operator with MKLDNN support. The test compares the output of MKLDNN integrated operator to the one without MKLDNN support.
Checklist
Essentials

[x] The PR title starts with [MXNET-1098], where 1098 refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Add tests for MKLDNN softmax operator

Comments

backward Softmax does not have MKLDNN support
OpReqType supported: WriteTo, WriteInplace
@azai91 please review

@mxnet-label-bot [pr-awaiting-response]

@pengzhao-intel  Thanks for the review. Can you please clarify what you mean by 'unit test' and 'enhancement'? And how separating into two PR would be better? Thanks :)

@mseth10 sorry, I misunderstand the PR. Please ignore previous comments :)

@mseth10 Thanks for the contribution!
Could you please look into the CI failures.

@ankkhedia Jenkins CI check passed. Travis CI failed due to time limit, which is not an issue.
Also, can you please change the tag from 'pr work in progress' to 'pr waiting for review'?

@sandeep-krishnamurthy @anirudh2290 Could you please change the label to pr-awaiting-review
@azai91 ping for review.

Can you please add a test case to cover #13141

Thanks for your contribution @mseth10
@mxnet-label-bot update [pr-awaiting-review]

@azai91  will add a test case to cover #13141 in a separate PR.    @nswamy

@mxnet-label-bot remove ['pr-work-in-progress']

@mxnet-label-bot add [pr-awaiting-review]

@nswamy @anirudh2290 pulling this to your attention. Thanks!

@mxnet-label-bot remove [pr-work-in-progress]


Client Allocation Request for: Yoshihito Kagami Photography

Client Allocation Questions
Core Information

Name: Yoshihito Kagami Photography
Website / Social Media: https://kagamiphoto.com
Region: Asia excl. Greater China
DataCap Requested: 10TiB
Addresses to be Notarized: f1pmvlr2vmc3f5mpketckupq6rmw674qdd2pnruny
Notary Requested: MasaakiNawatani

@kagamiphoto2 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hello @kagamiphoto2
Please respond to the questions below in paragraph form, replacing the text saying 'Please answer here'. Include as much detail as you can in your answer!
Please describe the nature of your organization, project, or use case. For organizations, please include your relationship with the organization the size of the organization, and time since inception. For projects and other use cases, please link to relevant web pages or Github. Please include as much relevant detail to provide contextual information (with external links). If you have any presentation document about your business, please provide it to me.
Please answer here.

Have you been approved for a DataCap previously? If so, can you share the details of the last allocation decision (who approved your DataCap, what your plan was for spending it, how you executed on that plan)?
Please answer here.

**Allocation Strategy
Do you intend to store your data in a single geography or many?
Please answer here.

Are you aware of and do you intend to use the features you may specify (e.g. Fast Retrieval) with your storage deals?
Please answer here.

How do you plan on securing the DataCap to ensure your organization (and its delegated members) are the ones allocating the DataCap?
Please answer here.

Do you plan on allocating a substantial portion of your DataCap to a single miner, or will you spread it across many miners?
Please answer here.

For application developers, will you be acting as the client on behalf of your users or you applying as a Notary on behalf of your users? If so, how much DataCap per user are you seeking to have approved?
Please answer here.

Do you agree to use the DataCap to only store data that abides by local regulations and in compliance with the recipient miner’s terms of service?
Please answer here.

**Track Record
Have you previously received DataCap to allocate before? If so, please link to any previous decisions that have been made.
Please answer here.

Are there any disputes open against you from your previous DataCap allocations?
Please answer here.

Been found to be in violation of the Principles of Filecoin Plus?

Please answer here.

Hi @MasaakiNawatani
Thanks. Please check our previous request with you back in 2021 December.
(https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/1224)


Includes libmbt in Go module source

Closes: #145
Description
Following cgo docs, libmbt should be part of go module source.
go get github.com/informalsystems/modelator/go/pkg/core is successful now.

For contributor use:

[ ] ~If applicable, unit tests are written and added to CI.~ Current CI takes care of it.
[x] Ran go fmt, cargo fmt and etc. (or had formatting run automatically on all files edited)
[ ] Updated relevant documentation (docs/) and code comments.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] ~Added a changelog entry, using unclog.~ Not needed.

Right now, the PR includes mbt library for x86_64 only. It should also include,

[ ] i686
[ ] darwin
[ ] windows


Update license

MIT license needs both of year and copyright holder.
Please complete MIT license. We want to use this without legal risk.

Coverage remained the same at 97.143% when pulling 00c176e2c3cf4f204321261b7e2b7fa5a8d5b1a6 on r-browser-app-team:r-browser-app-team-patch-1 into 6b998300e8cc2f732d80f99b7ecea37c97ab6ded on jamestalmage:master.

Coverage remained the same at 97.143% when pulling 00c176e2c3cf4f204321261b7e2b7fa5a8d5b1a6 on r-browser-app-team:r-browser-app-team-patch-1 into 6b998300e8cc2f732d80f99b7ecea37c97ab6ded on jamestalmage:master.


Support the new Canada West Region - ca-west-1

Is your feature request related to a problem? Please describe.
Yes. We are dealing with backups (and other things) and we want to be able to use ca-west-1.
Describe the feature you'd like
We would like for the ca-west-1 region to be supported.
Additional context
As of now, we get this error.

Hello @saedx1
Thank you for reaching out to the Landing Zone Accelerator team! We are working on adding support for Canada West Region - ca-west-1. This may be addressed in future releases.

@padebnat  Any updates on this?
Control Tower now supports it: https://aws.amazon.com/about-aws/whats-new/2024/05/aws-control-tower-canada-west-calgary-region/

Hi @saedx1 , this has been included in our v1.7.0 release so I will be closing this issue. Thanks for supporting the Landing Zone Accelerator!


easy_install problem

From<EMAIL_ADDRESS>on 2011-03-08T18:56:19Z
Hi,
with the lasted source code I have the following problem:
easy_install .
Processing .
Running setup.py -q bdist_egg --dist-dir D:\spyderlib_2.x\egg-dist-tmp-24xdmr
Traceback (most recent call last):
File "C:\Python26\Scripts\easy_install-script.py", line 8, in <module>
load_entry_point('setuptools==0.6c12dev- r88124 ', 'console_scripts', 'easy_install')()
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 1712, in main
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 1700, in with_ei_usage
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 1716, in <lambda>
File "C:\Python26\lib\distutils\core.py", line 152, in setup
dist.run_commands()
File "C:\Python26\lib\distutils\dist.py", line 975, in run_commands
self.run_command(cmd)
File "C:\Python26\lib\distutils\dist.py", line 995, in run_command
cmd_obj.run()
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 211, in run
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 427, in easy_install
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 476, in install_item
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 655, in install_eggs
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 930, in build_and_install
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\command\easy_install.py", line 919, in run_setup
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\sandbox.py", line 62, in run_setup
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\sandbox.py", line 105, in run
File "C:\Python26\lib\site-packages\setuptools-0.6c12dev_r88124-py2.6.egg\setuptools\sandbox.py", line 64, in <lambda>
File "setup.py", line 63, in <module>
from spyderlib import version
File "D:\spyderlib_2.x\spyderlib_init_.py", line 33, in <module>
from spyderlib import qt
File "D:\spyderlib_2.x\spyderlib\qt_init_.py", line 17, in <module>
sip.setapi('QString', 1)
AttributeError: 'module' object has no attribute 'setapi'
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=573

From pierre.raybaut on 2011-03-09T09:25:49Z
This issue was closed by revision 8e46d7c6cc .
Status: Fixed

From pierre.raybaut on 2011-04-24T07:38:28Z
This issue was closed by revision 8e46d7c6cc76 .


Removed Mock API from SUI codebase

PV https://www.pivotaltracker.com/story/show/140667939

@miq-bot add_label fine/no
@miq-bot add_label enhancement

@AllenBW made that change.  Let me know if we can approve this one.

@chalettu
the whole url isn't necessary, referencing the user repo and branch or version is all ya need here
prefer the follow: ManageIQ/manageiq-api-mock#master

@AllenBW can you review again and approve?


Add support for FB Instant articles

Code it's already in place, but fixes are needed, apparently, to let FB digest the feed

I'll call this complete, bar any outstanding bug


cygncursesw-10.dll missing

When I try to start pspsh.exe or usbhostfs_pc.exe I have an error saying "cygncursesw-10.dll" is missing, someone knows why?

Install cygwin

That's odd, which release did you download? I'm looking at the pspsh-windows.zip from the 3.1.1 release and it seems the dll you mention is included.

That's odd, which release did you download? I'm looking at the pspsh-windows.zip from the 3.1.1 release and it seems the dll you mention is included.

I downloaded the Development build of last week
https://github.com/pspdev/psplinkusb/releases/download/latest/pspsh-windows.zip

This is caused by #33, but I still need to investigate why this issue is happening.

It turns out libreadline depends on ncurses, so we need it to be added back. I'll reverse the changes from #33

This should be fixed now. Sorry it took a while, this issue was quite confusing.


vatlayer doesnt reflect in VAT

What I'm trying to achieve
Using the VatLayer plugin
Steps to reproduce the problem
In dashboard:

Activate the plugin with appropriate API key
Go to http://localhost:9000/dashboard/taxes/

What I expected to happen
Having the right VAT applied to each country with reduced rate
Screenshots and logs

System information
Saleor version:

[X] dev (current main)

How can I be sure of that ? I made a checkout main for every submodules I am not used to submodules.
https://github.com/saleor/saleor-platform
Output of git submodules
+308413ed9c19e7938e690fe3cf339b526fd34df2 saleor (3.0.0-a.0-1684-g308413ed9)
+f3d628c2d8142c46338f6b6531097bfe195d2417 saleor-dashboard (3.1.0-a.16)
+619024c9d4b3a8e43f6edf8d4958b85bf1b8ac57 saleor-storefront (3.0.0-b.2-4-g619024c9)

Operating system:

[ ] Windows
[x] Linux
[ ] MacOS
[ ] Other

For exemple,
Standard VAT is 20% in France when it showed 40% ?

Ok... I got it wrong I miss understand the column name... It is the number of VAT in the country. But where is the standard VAT rate ?

Also I am confused about:
https://docs.saleor.io/docs/2.9.0/guides/taxes#all-product-prices-are-entered-with-tax-included
From the enterprise perspective everything is seen without taxes then we collect taxes for the state. So I would enter intuitively net price in the dashboard.
I can open a discussion for this if needed :)

Vatlayer was replaced with build-in flat rate taxes which should be used instead.


Pull request docs missing section "multiple-merge-bases-issue" or wrong link

A pull request inside Azure DevOps showed the following warning about multiple merge bases:
Warning: Multiple merge bases detected. The list of commits displayed might be incomplete.
Alongside is a button labeled Learn more and the URL https://docs.microsoft.com/en-us/azure/devops/repos/git/pull-requests?view=azure-devops#multiple-merge-bases-issue
The problem now is that the section that this should lead to is missing in the docs.
Now either that section has never been there, is not live yet or has been moved elsewhere.
Nonetheless it should be fixed.

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

ID: bb8692f5-ffc0-ffdc-9b40-b5a69199d544
Version Independent ID: a9afd5a2-53b7-f2fe-4088-37d97b041563
Content: Create a pull request to review and merge code - Azure Repos
Content Source: docs/repos/git/pull-requests.md
Product: devops
Technology: devops-code-git
GitHub Login: @vijayma
Microsoft Alias: vijayma

https://developercommunity.visualstudio.com/t/learn-more-link-points-to-non-existent-section-of/1560780


stuck at length of mel chunks 0% every time for too long.

Using cuda for inference.
Reading video frames...
Number of frames available for inference: 200
(80, 402)
Length of mel chunks: 122
0%|                                                                                | 0/1 [00:00<?, ?it/s]
0%|                                                                                | 0/8 [00:00<?, ?it/s]

input video is 720* 1280，8 seconds，input audio file : wav file is 5 seconds.
i do not know why it is so long to be stuck at mel chunks?   1800 seconds passed without any response.
how can we speedup the proc?  it is crazy slow!
i use laptop with GPU nividia 4070  8GB vRam.

Try changing the resize factor to a larger number. If that doesn't help try changing to a different Stable Diffusion checkpoint.

Hi,
Yes, you can try resize factor but your gpu seems good enough for processing 720x1280
Try  to usé -medvram when launching stable-diffusion-webui
Let me know
Regards

how can i use " -medvram" ?  modified the code of "webui-user.bat"?

Yes,
In command arg

i try to use “set COMMANDLINE_ARGS= --medvram”   ，but  it does not work, and still stuck for long!

Just for check, try yo use resize factor x2 and Let me know the result please

yes,  last time i had set resize factor x2 and its speed can be acceptable! but the resolution of the output video file has also been halved.  So is there a way to  restore the resolution of the output video?

You can upscale with this method : https://www.youtube.com/watch?v=3z4MKUqFEUk
But after doing It in resize factor x2 try x1 in same session

sorry , I don't understand what you meant("But after doing It in resize factor x2 try x1 in same session").
i saw the youtube video ( https://www.youtube.com/watch?v=3z4MKUqFEUk) and i found it could be used to upscale the img not video that i output.
how can i do with it?  Excuse me that  i am not familiar to operate with sd-ui.

Sorry, i just want you make test with resize factor x2 and just after resize factor x1 to see if it still stuck.
True, but you can extract img from the final video, or you can active debug and found images in debug folder those with dst_xxxxx.png and use it in batch mode

The same issue. and on the webUI, each time there is an error in the video processing area.


Enhancement of reduction procedure

Description of the problem
Let's talk for a moment about the reduction mechanics implemented in neuronika. Currently, during a backward pass, we "shrink" the gradient entering each node by calling the two functions reduce and sum_axis_inplace.
Functions Code
fn sum_axis_inplace(arr: &mut DynTensor, axis: Axis) {
    let (first, rest) = arr.view_mut().split_at(axis, 1);
    Zip::from(first.remove_axis(axis))
        .and(rest.lanes(axis))
        .for_each(|dst, src| *dst += src.sum());
    arr.index_axis_inplace(axis, 0);
}

pub fn reduce<D: Dimension, E: Dimension>(dest: &Tensor<D>, src: &Tensor<E>) -> DynTensor {
    let mut dyn_rhs = src.clone().into_dyn(); // <- Very costly operation!

    unsafe {
        while (*(&dyn_rhs as *const DynTensor)).ndim() > dest.ndim() {
            sum_axis_inplace(&mut dyn_rhs, Axis(0));
        }
    }

    for (axis, size) in dest.shape().iter().enumerate() {
        if *size == 1 {
            sum_axis_inplace(&mut dyn_rhs, ndarray::Axis(axis));
            dyn_rhs.insert_axis_inplace(ndarray::Axis(axis));
        }
    }

    dyn_rhs
}

As you can see in the first line of reduce, every time it is executed it does a .clone(), but since the type on which it's executed is an Array that uniquely owns its content, we are actually allocating and copying it. Also, in a scenario where src and dest shapes are equal, this operation is completely useless as we can simply add them together.
Possible solution
One way to avoid all of these penalties is to introduce a new Reducer structure that contains a buffer with the same capacity as the largest gradient on which the reduction has to be performed. If and when this operation has to be performed, the contents of the input tensor are copied into the buffer, which is then used to generate a new ArrayViewMut on which the actual accumulation will take place.

Solution Code
pub struct Reducer {
    buffer: Vec<f32>,
}

impl Reducer {
    fn sum_axis_inplace(arr: &mut ArrayViewMut<f32, IxDyn>, axis: Axis) {
        let (first, rest) = arr.view_mut().split_at(axis, 1);
        Zip::from(first.remove_axis(axis))
            .and(rest.lanes(axis))
            .for_each(|dst, src| *dst += src.sum());
        arr.index_axis_inplace(axis, 0);
    }

    fn load(&mut self, src: &ArrayView<f32, IxDyn>) {
        let src_len = src.len();

        assert!(src_len <= self.buffer.capacity());

        unsafe {
            ptr::copy_nonoverlapping(src.as_ptr(), self.buffer.as_mut_ptr(), src_len);
            self.buffer.set_len(src_len);
        }
    }

    pub fn new(cap: usize) -> Self {
        assert_ne!(cap, 0);

        Self {
            buffer: Vec::with_capacity(cap),
        }
    }

    pub fn reduce<D: Dimension>(&mut self, dst: &mut Array<f32, D>, src: ArrayView<f32, IxDyn>) {
        let excess = src.ndim() - dst.ndim();
        let to_shrink = src.shape()[excess..src.ndim()]
            .iter()
            .enumerate()
            .filter(|(_, len)| **len == 1)
            .map(|(id, _)| id)
            .collect::<Vec<_>>();

        if excess == 0 && to_shrink.is_empty() {
            // dst.assign(&src);
            return;
        }

        self.load(&src);
        let mut src =
            unsafe { ArrayViewMut::from_shape_ptr(src.raw_dim(), self.buffer.as_mut_ptr()) };

        for _ in 0..excess {
            Reducer::sum_axis_inplace(&mut src, Axis(0));
        }

        for axis in to_shrink {
            Reducer::sum_axis_inplace(&mut src, Axis(axis));
            src.insert_axis_inplace(Axis(axis));
        }

        // dst.assign(&src);
    }
}

Test Configuration
Both these versions have been tested on the following code with the --release flag twice, one with valgrind to assess the memory usage, and one without for the completion time.

New Code Test
const TRIES: usize = 16;

let mut reducer = Reducer::new(1_024 * 1_024 * 4);
let src = Array::from_elem((1_024, 1_024, 4), 1.);
let mut dst = Array::from_elem((1_024, 4), 0.);
let res = (0..TRIES)
    .map(|_| {
        let start = Instant::now();
        for _ in 0..1_024 {
            reducer.reduce(&mut dst, src.view().into_dyn());
        }
        start.elapsed().as_millis()
    })
    .sum::<u128>();
println!(
    "Mean elapsed time: {} milliseconds",
    res as f64 / TRIES as f64
);

Old Code Test
const TRIES: usize = 16;

let src = Array::from_elem((1_024, 1_024, 4), 1.);
let dst = Array::from_elem((1_024, 4), 0.);
let res = (0..TRIES)
    .map(|_| {
        let start = Instant::now();
        for _ in 0..1_024 {
            neuronika::variable::node::reduce(&dst, &src);
        }
        start.elapsed().as_millis()
    })
    .sum::<u128>();
println!(
    "Mean elapsed time: {} milliseconds",
    res as f64 / TRIES as f64
);

Results
VersionIterationsSourceDestinationTime (ms)AllocationsBytes UsedCurrent1'024(1'024, 1'024, 4)(1'024, 4)10'931.811,03717,196,664,945Proposed9'561.561433,572,977
Looking at the numbers, we can see that this new version, even on only 1'024 iterations, is almost 1.5 seconds faster, and uses 512 times less memory.

Interesting! I have a couple of questions: when does Reducer gets freed? And who owns it?

This procedure works in-place and does not allocate. I briefly tested it and it seems to work. I would extensively test it before adopting it anyways.
fn accumulate<D, E>(target: &mut Array<f32, D>, source: &Array<f32, E>)
where
    D: Dimension,
    E: Dimension,
{
    // context: source is a tensor whose shape is the result of broadcasting between target
    // and some other.
    let target_dim = target.raw_dim();

    // base case: when target is the broader
    if let Some(smaller) = source.broadcast(target.raw_dim()) {
        *target += &smaller;
    } else {
        let source_dim = source.raw_dim();

        let target_dims = target_dim.ndim();
        // computes the difference between the number of dimensions
        let k = source_dim.ndim() - target_dims;
        let axis_zero_size = source_dim.slice().iter().take(k).product::<usize>();

        let mut reshape = D::Larger::zeros(target_dims + 1);
        reshape[0] = axis_zero_size;

        for (r, s) in std::iter::zip(
            reshape.slice_mut().iter_mut().skip(1),
            source_dim.slice().iter().skip(k),
        ) {
            *r = *s;
        }
        // reshapes such that the sub-views match the dimensionality of target
        let views = source.view().into_shape(reshape).unwrap();

        for view in views.axis_iter(Axis(0)) {
            let view_dim = view.raw_dim();
            // accumulates using the outermost axis
            for (i, (t_dim, v_dim)) in
                std::iter::zip(target_dim.slice(), view_dim.slice()).enumerate()
            {
                // dimensions can either be equal or 1
                if t_dim != v_dim {
                    let axis = ndarray::Axis(i);
                    let mut lanes_v = view.lanes(axis).into_iter();

                    while lanes_v.len() > 0 {
                        let mut lanes_t = target.lanes_mut(axis).into_iter();
                        while let Some(mut lane_t) = lanes_t.next() {
                            if let Some(lane_v) = lanes_v.next() {
                                if lane_t.len() == 1 {
                                    lane_t[0] += lane_v.sum();
                                } else {
                                    lane_t += &lane_v;
                                }
                            }
                        }
                    }
                    break;
                }
            }
        }
    }
}

We ran some tests on different machines and we can conclude that the in-place variant is 1.3 ~ 4.6 times more efficient than the buffered one, so we will implement [this] version in the library.
Well done @frjnn!