Doesn't download albums hidden from profile

If I hide an album from my Bandcamp profile, bandcamp-downloader does not find it.

Try adding the option --include-hidden when running bandcamp-downloader.py.

Oops! Yep that works great, thanks!


IntelliJ Silent update is not working

Hi there, and thanks for AppGet.
I'm giving it a try and so far I'm very pleased. Good job!
Nevertheless I'm trying to update IntelliJ Community Edition (from 182.4892.20 to 183.5912.21).
I have an error during installation (Silent Mode)

In the logs :
2019-03-27 01:40:27.2670 8816:8 [Fatal]  UpdateService: An error occurred while updating intellijAppGet.Installers.InstallerException: Installer for IntelliJ IDEA Community 183.5912.21 returned with a non-zero exit code: 2. Installation aborted by script
   at AppGet.Installers.InstallService.RunInstaller(InstallInteractivityLevel interactivity, PackageManifest packageManifest, IInstaller whisperer) in c:\src\src\AppGet\Installers\InstallService.cs:line 163
   at AppGet.Installers.InstallService.<Install>d__12.MoveNext() in c:\src\src\AppGet\Installers\InstallService.cs:line 96
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at AppGet.Update.UpdateService.<UpdatePackage>d__8.MoveNext() in c:\src\src\AppGet\Update\UpdateService.cs:line 50
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at AppGet.Update.UpdateService.<UpdateAllPackages>d__9.MoveNext() in c:\src\src\AppGet\Update\UpdateService.cs:line 78

I'm glad you find appget useful, this is a known issue #31 I'll see if I can do a beta release of it sometime this week.
I'm gonna close this issue in favour of #31


Fix Vera++ rule for switch statements.

Don't warn on continue statements without comment in a switch-case.
JerryScript-DCO-1.0-Signed-off-by: László Langó<EMAIL_ADDRESS>

LGTM! Those fallthrus are so annoying.


Session storage send buffer

Task #69 - Improve transmission reliability

Add session storage buffer (disabled by default).

Some tweaks and :shipit:

:shipit:


Wrong duration for some mp3 streaming

When I try this podcast, all recent episode is not properly works in SwiftAudioPlayer.
https://rss.art19.com/business-wars-daily
It looks like the duration of mp3 is wrong and it will stuck at the actual ended position.
Tested on SwiftAudioPlayer Example project.

it looks like the duration is changing due to a random advertising clip appended at the end.
I'm still researching it.

Thanks for researching this! I'll look into it as well but in general duration comes from either the metadata from the audio at the beginning of the audio if provided or calculated from the expected file size given by the server.

I tried "metadata" and "calculated size" but couldn't get the correct duration.
These episode are using some sort of DAI to dynamically insert a small part audio into the episode.
So I decide to use  "durationLoadedByNetwork" to make sure the audio to play though.
Please check pr #155 (just a theory, not fully check or test) to see if this theory works.


Add custom scrollbar

Changing the custom scrollbar will make the appearance of the website more beautiful

you can assign that task to me under gssoc-ext and hacktoberfest label..


fix(chat): increase max headers size (Issue #2852)

Description:
increase max headers size
Issues:

Issue #2852

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review


Catalog - Add quotes csv fields when exporting

Add quotes around csv fields when exporting so that the fields will read properly in programs such as excel.
For instance,<PHONE_NUMBER>4B5100 gets quoted so that it doesn't show up in excel as 1.04E+15.

Nothing was wrong with the original output and was working as designed making this an enhancement.


Fixing logo symlinks

Another github.dev snafu meant that I accidentally committed to main. This fixes that and makes a proper pull request. Sorry about that folks

merging since the test is happy now


Changes to the default protection alerts do not appear in Get-ProtectionAlert

When performing a change to one of the default protection alerts, for instance; "User restricted from sending email", these changes do not appear to be reflected by performing the Get-ProtectionAlert.
You can replicate this behaviour by modifying, for instance, the notification users by adding a new user. When running Get-ProtectionAlert on a default alert, it will always say "TenantAdmins" even though you've added another Notification User.

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

ID: d51d54fa-4505-9f5a-c737-23927c3fa5f3
Version Independent ID: 937d76b1-48ab-dd34-a432-27db5b6284dd
Content: Get-ProtectionAlert (exchange)
Content Source: exchange/exchange-ps/exchange/policy-and-compliance/Get-ProtectionAlert.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Hi @cammurray, thank you for your feedback.
Please check Set-ProtectionAlert cmdlet help. You cannot edit default alerts:
https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance/set-protectionalert

@dariomws306  Thank you very much for the contribution and sharing this explanation. @cammurray
Hope this comment is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@officedocsbot close


\left...\right don't get INNER spacing

The texClass of INNER is being lost on \left...\right constructs, even though the class is properly displayed in the MathML output.  For example, a\left(b\right) does not have the extra space between the a and (.

This is due to
https://github.com/mathjax/MathJax-src/blob/aa41c0b9362de07c29dcef6de474941385386293/ts/core/MmlTree/MmlNodes/mrow.ts#L157
which incorrectly uses prev to determine if the open is the first element in the list (prev may be the element just before the mrow).  This test should either be removed or modified to test for the actual previous element).


Android 8.0: Configuration File Error, Read Error with Config File

I'm trying to set up a profile on the Android app eduroam CAT.
I'm using Android 8.0 and I'm trying to install the corresponding Android 8.0 Oreo profile downloaded from this page.
When in the application, I'm using the drop-down menu and clicking "Select Config File". Then I select the downloaded profile.
When I do this I get a "Configuration File Error" and "Read Error with Config File".
I don't know what to do here.
eduroamCAT version is 1.1.44

Hello,
I have tried to repeat this error on my emulator of Android 8.0, without success.

I have tried manually selecting the downloaded profile and discovering the profile.
What device type/model are you using?
Thanks,
Gareth

No response from user, so closing issue.
Gareth


Typo in command (missing white space in command construction)

identity provider creation failed due a missing white space in command construction

Thank you for your contribution!
This GitHub repository is just a mirror of https://opendev.org/openstack/kolla-ansible, where development really happens. Pull requests proposed on GitHub are automatically closed.
If you are interested in pushing this code upstream, please note that OpenStack development uses Gerrit for change proposal and code review.
If you have never contributed to OpenStack before, please see:
https://docs.openstack.org/contributors/code-and-documentation/quick-start.html
Feel free to reach out to the First Contact SIG by sending an email to the openstack-discuss list with the tag '[First Contact]' in the subject line. To email the mailing list, you must first subscribe which can be done here:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss


feat: Pricing calculator

Summary

Added pricing calculator markdoc tag and new docs page.
Notes:

I have added Pricing Calculator page directly in Operations category. In Figma Pricing calculator is under Cost Management. Let me know if you would like to change its placement.
Page content needs to be reviewed and updated. I have added only few quick mocks.
Do we want to start using expandable callouts in docs or keep them always expanded like now? If we would like to use expandable variant then this functionality needs to be added.

Feel free to edit it.
Test Plan
Tested locally.
Checklist

[ ] If required, I have updated the Plural documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have added a meaningful title and summary to convey the impact of this PR to a user.
[ ] I have added relevant labels to this PR to help with categorization for release notes.

Everything is fixed besides integrating https://github.com/pluralsh/design-system/pull/439 with it.

Looks great!


Add types to package.json

Description
Types were not being exported even though they were generated.
I added the types field to the package.json and linked it to the build/index.d.ts file. (As advised here: https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html)
Contributing Agreement

[x] I have read and understood the Optimism Contributing Guide and Code of Conduct and am following those guidelines in this pull request.

Do you mind removing changes to the yarn.lock?

Do you mind removing changes to the yarn.lock?


Remove unnecessary execute permissions

Markdown and image files are not executable file, so I removed the execute permission from them. release.sh may be executable file, so I maintained the execute permission for this.

Thanks for the PR, @sorairolake. I'm happy to accept this change and will merge it in now.


Sqlsmith: Generate table function

[ ] generate_series
[ ] unnest
[ ] regexp_match
[ ] range

See: https://github.com/risingwavelabs/risingwave/blob/main/src/expr/src/table_function/mod.rs

There's no other table functions besides hop and tumble, which are already generated :sweat_smile:

Actually there is, such as generate_series. But since they are less used in the real world, without them will be fine.

Actually there is, such as generate_series, unnest. But since they are less used in the real world, without them will be fine.

I see. I will track these under refinements, thanks.

Reopen to track for regexp_match, as well as other table functions.


Add explicit support for JRuby

Dear maintainers, I would like to explicitly add support for JRuby to this gem. I was able to make the necessary changes, as follows:

Some stubs where causing some issues that are resolved by either explicitly un-stubbing or stubbing a particular instance, as opposed to any_instance
Nokogiri has it's own java extension different from the one in MRI. The 1.5 series has some bugs that have
been resolved in 1.6 series, so I use that version when in JRuby
Nokogiri has different behavior when validating XML schemas in MRI and JRuby. I already raised the issue there (https://github.com/sparklemotion/nokogiri/issues/1282). To get around it, I removed the memoization that was earlier added as a performance improvement. Is this acceptable?
The Nokogiri::XML::Node#canonicalize method in Nokogiri also behaves differently in JRuby vs MRI. However, that is easily solved by passing in nil (which is the default parameter) instead of [] for the inclusive_namespaces.

I believe 3 is the only real change in behavior for the gem. I'd appreciate your feedback.
Travis build: https://travis-ci.org/ylansegal/ruby-saml/builds/61692511
Thanks

I'm glad with with the fact of supporting JRuby, and I'm ok with the code. @luisvm, @Lordnibbler what do you think?

I have updated this PR, because of conflicts with the recent changes in master. What are the chances of this being merged?
Also, besides the Nokogiri mentioned above. JRuby 1.7.20 also has some change in behavior (in jruby-openssl) that breaks the tests. I have created an issue for them: https://github.com/jruby/jruby-openssl/issues/42
Thanks,

JRuby 9000 is out, and jruby-openssl 0.9.8 fixes some X509 cert parsing issues. I updated the pull request. I am aware that there are merge conflicts: I will gladly resolve them again if there is interest from the committers in merging this PR.

@ylansegal
Apologies for not merging your PR on time, I think that supporting JRuby makes sense since it not requires much changes and can help some of the java-customers.
Please fix conflicts, we will review the changes, test and include it on the master branch.

@pitbulk I've fixed the merge conflicts and added support for JRuby-1.7.21 and JRuby-<IP_ADDRESS>.
Thank you,

We will review it and get it merged this week. Thanks for contributing!.

@ylansegal does the issue you have with schema validate relate to not being able to validate on hard validation?
I do get an invalid_ticket error in JRuby but not on MRI.
response = RubySaml::Response.new(request.params['SAMLResponse'], options)

unless response.is_valid?
    raise ValidationError.new(response.errors.join('\n'))
end

@keaplogik Are you seeing issues after this PR was merged? All the ones I was having where solved.
The issue with the schema validation that I mentioned in the original post was solved by not memoizing the Nokogiri::XML::Schema object, which triggers a difference in behavior between Nokogiri in MRI vs JRuby.
I am not sure what is causing your invalid_ticket

OK thanks. Looks to be a separate issue I may need to do some more verification on my test. Looks like a digest mismatch error.

Changes Unknown when pulling 7d86fe2cdd0f70f5ad849d64f34a5e723aaa3b89 on ylansegal:feature/jruby_support_0.9 into ** on onelogin:master**.


create violin plots for cell type distribution

making violinplots (fig S2b). like S2, but different way of analyzing the data

@pascoesean Lastly I would remove the uploading of the factors file

@pascoesean merged!


Support in multi-line string

When trying to convert a notebook with a multi-line string (''') soorgeon fails.

do you have the error message?

Can't recreate, closing for now.


FrameToScreen/BoundsToScreen work, but are not correct

In #3158 I found the logic I put in these apis is not actually correct. It works with current Frame functionality but only by accident.
This issue is to help me remember this needs to be fixed.
The solve will be to make FrameToScreen recursive vs using a while loop.
More unit tests are required in CoordinateTests.

Just a thought:
Remember that the csharp compiler cannot perform tail call optimization, so use of recursion usually results in slower code than the equivalent iterative approach, which is able to be aggressively optimized.
Recursion for things like this can be clearer, but just something to be aware of.

Yes it's passed by reference and normally this kind of calculation use recursion which is the preferable.

Yep, I'm aware of that. I'm pointing out that, specifically, the C# compiler doesn't emit good code for recursion, even though the relevant opcodes are available in IL.
It's an unfortunate implementation detail of the compiler and has been a long-standing issue, with many proposals around it, for many years.
One way to make it better is to implement your recursion using local functions, though it still will never emit the .tail opcode.
It's important for a library to be conservative with the stack, as we don't know how deep we may already be when invoking an operation.
Again, though, just something to be aware of.
Personally, I prefer recursion when it makes sense, too, but there IS a cost, specifically when using C#.

This recursive method is accurate to get conditions where must have an end, otherwise is a StackOverflowException

Yes.
It's not a question of accuracy.
It's a notice of performance considerations due to implementation details of the C# compiler and debugging difficulty, if an exception (of any kind - not just a stack overflow) happens in a recursive method, in C#, specifically. Your stack trace will have every recursive call on it, and you have to unwind it yourself, since the compiler and JITer won't emit the .tail opcode.

Cool, I've never used that Resharper feature. Didn't know it existed.
I'll give it at try when I tackle this issue.

Normally when the stack overflow exception throw it's in situations where the values passed into parameters and the return values are always the same for about 1000 times, more or less. So that would an coincidence or must probably for sure a bug 😃

Cool, I've never used that Resharper feature. Didn't know it existed.
I'll give it at try when I tackle this issue.

Yeah it's pretty nifty.
Though it won't offer it if it is complex enough that it can't figure out how to do it, so it's not available in 100% of situations.

Normally when the stack overflow exception throw it's in situations where the values passed into parameters and the return values are always the same for about 1000 times, more or less. So that would an coincidence or must probably for sure a bug 😃

Right. Infinite recursion bugs will of course throw it.
You can encounter it outside of those scenarios if you enter a non-trivial recursive method from a point in the application where the stack is already deep, as well, which is why it's just polite for libraries to try to avoid it when possible.
Now, if MS ever makes the compiler emit .tail opcodes, the whole problem will go away and it will cease to matter.
In this application, it's unlikely for this particular method to ever have to traverse a tree with a depth more than single digits (amusingly, except maybe for TreeView), so it's probably not a bit deal. It's just the first time someone mentioned recursion explicitly since I've had eyes on things, so it was mostly an FYI.

I believe this is all fixed in

https://github.com/gui-cs/Terminal.Gui/pull/3278

Probably? 🤔
I guess if I notice anything still weird when I get back to stuff dependent on that, I'll file charges or whatever. 😛

Probably? 🤔
I guess if I notice anything still weird when I get back to stuff dependent on that, I'll file charges or whatever. 😛

https://github.com/gui-cs/Terminal.Gui/pull/3295 adds a bunch of unit tests that prove this stuff now finally, actually, does work as advertised.

THANK YOU!


Use a singularity container with casa to replace casatasks

The use of casatasks is hurting more than helping, locking us into a older version of python in order to keep some level of compatibility to python-casatasks.
Moving forward it would probably be a good idea to mock up a branch that uses a singularity container with casa6 to replace the current use of casatasks

This was completed in #169
Along the way the python version was also bumped up from 3.8 to 3.12.


⚠ Bofrost.at has degraded performance

In d8d7c54, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2739 ms

Resolved: Bofrost.at performance has improved in d20df03.


4.x: Use a single version of Java

All modules of Helidon should use the same source version.

This will make builders, and common unusable on older versions of Java.
If you are interested in these features on older versions, please let us know through an issue, and we will check what options we could have for that!


🐞 [Bug] TFRobot: Node count in the node group isn't working correctly

What happened?
I selected the node count to be only one and deployed a VM group with 100 VMs for that node group, but after deploying was done successfully, I found that there was more than one node used on the VMs.

which network/s did you face the problem on?
Dev
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant log output
"node_groups": [
    {
      "name": "test1",
      "nodes_count": 1,
      "free_cpu": 1,
      "free_mru": 1,
      "free_ssd": 1,
      "free_hdd": 1,
      "dedicated": false,
      "public_ip4": false,
      "public_ip6": false,
      "certified": false
    }
  ],
  "vms": [
    {
      "name": "examplevm1",
      "vms_count": 100,
      "node_group": "test1",
      "cpu": 1,
      "mem": 1,
      "flist": "https://hub.grid.tf/tf-official-apps/base:latest.flist",
      "entry_point": "/sbin/zinit init",
      "root_size": 0,
      "public_ip4": false,
      "public_ip6": false,
      "ssh_key": "harby",
      "env_vars": {
        "user": "user1",
        "pwd": "1234",
        "user": "user2",
        "test": "pass"
      }
    }
  ]

I tried it twice, and the same thing happened. On both times the deployment failed on the first try with this error.
2:20PM DBG Deploying 100 virtual machines, this may to take a while
2:20PM DBG failed to read message error="read tcp <IP_ADDRESS>:35670-><IP_ADDRESS>:443: use of closed network connection"
2:25PM DBG failed to deploy error="45 errors occurred:\n\t* error waiting deployment: waiting for deployment 83956 timed out\n\t* error waiting deployment: waiting for deployment 83949 timed out\n\t* error waiting deployment: waiting for deployment 83921 timed out\n\t* error waiting deployment: waiting for deployment 83933 timed out\n\t* error waiting deployment: waiting for deployment 83909 timed out\n\t* error waiting deployment: waiting for deployment 83967 timed out\n\t* error waiting deployment: waiting for deployment 83942 timed out\n\t* error waiting deployment: waiting for deployment 83953 timed out\n\t* error waiting deployment: waiting for deployment 83913 timed out\n\t* error waiting deployment: waiting for deployment 83912 timed out\n\t* error waiting deployment: waiting for deployment 83965 timed out\n\t* error waiting deployment: waiting for deployment 83906 timed out\n\t* error waiting deployment: waiting for deployment 83910 timed out\n\t* error waiting deployment: waiting for deployment 83958 timed out\n\t* error waiting deployment: waiting for deployment 83966 timed out\n\t* error waiting deployment: waiting for deployment 83941 timed out\n\t* error waiting deployment: waiting for deployment 83951 timed out\n\t* error waiting deployment: waiting for deployment 83948 timed out\n\t* error waiting deployment: waiting for deployment 83908 timed out\n\t* error waiting deployment: waiting for deployment 83964 timed out\n\t* error waiting deployment: waiting for deployment 83968 timed out\n\t* error waiting deployment: waiting for deployment 83960 timed out\n\t* error waiting deployment: waiting for deployment 83943 timed out\n\t* error waiting deployment: waiting for deployment 83879 timed out\n\t* error waiting deployment: waiting for deployment 83963 timed out\n\t* error waiting deployment: waiting for deployment 83946 timed out\n\t* error waiting deployment: waiting for deployment 83904 timed out\n\t* error waiting deployment: waiting for deployment 83947 timed out\n\t* error waiting deployment: waiting for deployment 83952 timed out\n\t* error waiting deployment: waiting for deployment 83945 timed out\n\t* error waiting deployment: waiting for deployment 83880 timed out\n\t* error waiting deployment: waiting for deployment 83959 timed out\n\t* error waiting deployment: waiting for deployment 83905 timed out\n\t* error waiting deployment: waiting for deployment 83878 timed out\n\t* error waiting deployment: waiting for deployment 83876 timed out\n\t* error waiting deployment: waiting for deployment 83914 timed out\n\t* error waiting deployment: waiting for deployment 83877 timed out\n\t* error waiting deployment: waiting for deployment 83915 timed out\n\t* error waiting deployment: waiting for deployment 83907 timed out\n\t* error waiting deployment: waiting for deployment 83957 timed out\n\t* error waiting deployment: waiting for deployment 83962 timed out\n\t* error waiting deployment: waiting for deployment 83911 timed out\n\t* error waiting deployment: waiting for deployment 83961 timed out\n\t* error waiting deployment: waiting for deployment 83944 timed out\n\t* error waiting deployment: waiting for deployment 83950 timed out\n\n" Node group=test1
2:25PM INF Retrying to deploy Deployment trial=2 Node group=test1
2:25PM INF Filter nodes Node group=test1
2:25PM DBG reached nodes page=5 total pages=6
2:25PM DBG nodes IDs=[100]
2:25PM DBG Updating vms group Node group=test1
2:25PM DBG failed to get node pools error="context canceled" node ID=28
2:25PM DBG failed to get node pools error="context canceled" node ID=11
2:25PM DBG failed to get node pools error="context canceled" node ID=14
2:25PM DBG failed to get node pools error="context canceled" node ID=31
^C

we need to add validation to make sure the requested number of nodes can serve the required resources of the needed vms

We can mention the behavior in the docs. Retry approach will still be the same

Work Completed

mentioned the behavior in the docs as a note


Navigator user Agent undefined

I don't know if I should open issue here or in the original repo, and if it was not yet fixed?
Sometimes we want to get navigator.userAgent (i.e. I need to pass the same user agent that playwright is using to aiohttp or other fetch lib)
Having navigator.userAgent undefined breaks scripts (like Google Search's captcha) and can also be used for fingerprint (i.e.: FingerprintJS)
May I ask, how is the status of fingerprintjs detection? last time I checked in the original one, fingerprint.com could still get stealth plugin

Having navigator.userAgent undefined breaks scripts

This should never be the case with this library, unless you explicitly specify an undefined UA to use. If userAgent is undefined, that's a bug.

May I ask, how is the status of fingerprintjs detection?

This is not something that is tested against at the moment.


Not working with VueJS / NuxtJS

Great modal system. I'm trying to integrate it within my VueJS / NuxtJS project, so I installed through npm and tried to simply include it.
import tingle from 'tingle.js'
But it crashes completely
document is not defined

internal/modules/cjs/loader.js:721:30
Module._compile
internal/modules/cjs/loader.js:732:10
Module._extensions..js
internal/modules/cjs/loader.js:620:32
Module.load
internal/modules/cjs/loader.js:560:12
tryModuleLoad
internal/modules/cjs/loader.js:552:3
Module._load
internal/modules/cjs/loader.js:657:17
Module.require
internal/modules/cjs/helpers.js:20:18
require
webpack:/external "tingle.js":1:
Object.tingle.js
webpack/bootstrap:25:
__webpack_require__

Any idea where that could be coming from ? I really want to use this modal in the project ... Thanks

Hi,
I'm not familiar with Nuxt but maybe it's related to this: https://nuxtjs.org/faq/window-document-undefine

Thanks for the quick reply, I believe you're right and it's not a tingle issue, I'll try to use this. Thanks for your input!


[Electron 8.0.0] electron-v76 support

Summary of Problem
Hi. I'm trying to build an electron app but during the install prebuilt binary process I'm getting messages like (for each OS)
prebuild-install http 404 https://github.com/serialport/node-serialport/releases/download/<EMAIL_ADDRESS>
prebuild-install WARN install No prebuilt binaries found (target=8.0.0 runtime=electron arch=x64 libc= platform=linux)

which causes an error
../node_modules/app-builder-lib/node_modules/app-builder-bin/mac/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE

Quick check shows that there's just no release for Electron 8.0.0 as the highest is v75 but new Electron requires v76: https://github.com/serialport/node-serialport/releases
When will you add a support for Electron 8.0.0? It's a stable version now.
Versions, Operating System and Hardware

SerialPort 8.0.7
electron 8.0.0
electron-builder 22.3.2
electron-builder-http 19.27.5
Node.js v12.9.1
All platforms

@reconbot how we can help you resolve this issue?

I set it back from version 8 to 7.
I am using it now.

@ghost602 please, try electron-rebuild package. I'm using electron 8.2.0 and It`is working.
There is hook in package.json.
 "scripts": {
    "install": "electron-rebuild -f -w serialport",
  },

@ghost602 try electron-rebuild package. I'm using electron 8.2.0 and It`is working.
There is hook in package.json.
 "scripts": {
    "install": "electron-rebuild -f -w serialport",
  },

I checked and I still don't believe - it really works 🎉 Rebuilding with node-gyp, electron-rebuild any many other solutions just didn't worked till now. Thanks @qdimka for response! 😄

Meh... it works only for mac. Linux and windows are having the same issue as mentioned in first post.

Yeah, I also get this issue (trying to build for Windows on Docker).

This fixed the issue for me 👍

Yay, thanks! It works well 🚀

Sorry to bump this up, not sure it is allowed or if I should create a new issue but the same problem appears with Electron ABI v80.

Same issue:
prebuild-install WARN install prebuilt binaries enforced with --force!     prebuild-install WARN install prebuilt binaries may be out of date!     prebuild-install info looking for cached prebuild @ /Users/jarrod/.npm/_prebuilds/950adb-bindings-v9.0.0-electron-v80-darwin-x64.tar.gz     prebuild-install http request GET https://github.com/serialport/node-serialport/releases/download/<EMAIL_ADDRESS>   prebuild-install http 404 https://github.com/serialport/node-serialport/releases/download/<EMAIL_ADDRESS>   prebuild-install WARN install No prebuilt binaries found (target=9.0.1 runtime=electron arch=x64 libc= platform=darwin)

rebuilding native dependencies  dependencies=<EMAIL_ADDRESS>platform=win32 arch=ia32
• install prebuilt binary  name=@serialport/bindings version=9.0.0 platform=win32 arch=ia32
• build native dependency from sources  name=@serialport/bindings
version=9.0.0
platform=win32
arch=ia32
reason=prebuild-install failed with error (run with env DEBUG=electron-builder to get more information)
error=prebuild-install info begin Prebuild-install version 5.3.4
prebuild-install WARN install prebuilt binaries enforced with --force!
prebuild-install WARN install prebuilt binaries may be out of date!
prebuild-install info looking for cached prebuild @ C:\Users\wxb\AppData\Roaming\npm-cache_prebuilds\209cc5-bindings-v9.0.0-electron-v76-win32-ia32.tar.gz
prebuild-install http request GET https://github.com/serialport/node-serialport/releases/download/<EMAIL_ADDRESS>prebuild-install WARN install connect ETIMEDOUT <IP_ADDRESS>:443

Same issue:
rebuilding native dependencies  dependencies=<EMAIL_ADDRESS>platform=win32 arch=ia32
  • install prebuilt binary  name=@serialport/bindings version=9.0.0 platform=win32 arch=ia32
  • build native dependency from sources  name=@serialport/bindings
                                          version=9.0.0
                                          platform=win32
                                          arch=ia32
                                          reason=prebuild-install failed with error (run with env DEBUG=electron-builder to get more information)
                                          error=prebuild-install info begin Prebuild-install version 5.3.4
    prebuild-install WARN install prebuilt binaries enforced with --force!
    prebuild-install WARN install prebuilt binaries may be out of date!
    prebuild-install info looking for cached prebuild @ C:\Users\wxb\AppData\Roaming\npm-cache\_prebuilds\209cc5-bindings-v9.0.0-electron-v76-win32-ia32.tar.gz
    prebuild-install http request GET https://github.com/serialport/node-serialport/releases/download/<EMAIL_ADDRESS>    prebuild-install WARN install connect ETIMEDOUT <IP_ADDRESS>:443

I think you should double check your internet connexion/proxies because the bindings for v9.0 ABI v76 is available and the link mentionned in the output you provided is working (https://github.com/serialport/node-serialport/releases/download/@serialport/bindings@9.0.0/bindings-v9.0.0-electron-v76-win32-ia32.tar.gz). You had a timeout error (connect ETIMEDOUT <IP_ADDRESS>:443), so I assume it's rather some kind of connectivity issue on your side.


Hook

Hi, I never finished this game when I was a young boy.
Now I have a modded GBC with IPS screen and an EZ Flash jnr I will be very happy if this game has working save states.
Thanks 👍

Hi there,
I've now created a patch for this. Give it a try and let me know if any issues :)

Hi there,
I've now created a patch for this. Give it a try and let me know if any issues :)

You are my hero, many thanks it works perfectly 👍

That's great, thanks for letting me know :)


cannot build project with Angular6

Hello, I have the following issue:
I followed the provided instructions to integrate ng2-heremaps into my Angular6-project, but unfortunately, when start ng serve, I get the following error:
ERROR in ./node_modules/ng2-heremaps/index.ts Module build failed: Error: {local-path-to-angular}\ClientApp\node_modules\ng2-heremaps\index.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property. The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an issue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).     at AngularCompilerPlugin.getCompiledFile ({local-path-to-angular}\ClientApp\node_modules\@ngtools\webpack\src\angular_compiler_plugin.js:749:23)     at plugin.done.then ({local-path-to-angular}\ClientApp\node_modules\@ngtools\webpack\src\loader.js:41:31)     at process._tickCallback (internal/process/next_tick.js:68:7) i ｢wdm｣: Failed to compile.
Can you please help me? Am I doing something wrong or does the library needs to be updated?
If you need more information, please let me know.
Best regards,
elvirus

I never tested this with Angular 6, but apparently it requires a bit of polishing according to this document
I'm not able to fix this quickly at the moment, but if this is urgent to you feel free to make pull request

Thank you for your reply. After taking a brief look into the documentation of the Angular Package Format I realized that I do not understand which work should be done here. I am fairly new to the Angular world and never made npm packages before.
I would really like to support you here, I think I just don't have the required knowledge.
There is something mentioned in the error message of including the file in tsconfig.json... Could that be a workaround for me in order to use your lib? Unfortunately, I was not able to get it working. Do you have an idea how to make it work with tsconfig? Can this be done?
Best regards,
elvirus

I tried to build a new version of the library using the angular-library-starter you linked here. I got several errors during the build and addressed one after the other. There where changes in some imports (f. i. rxjs), some types have changed also.
After I got rid of all errors in the build console, the build failed again but without any error output. :-(
So, unfortunately, I must give up here. I was really exited when I found your library but since I have to implement a map feature in the current sprint, I have to fallback to using OSM which is really a bummer for me. :-(
Maybe, if you find the time to update the lib (which seems to be the only one available in the web), I might change my code to use it then.
Cheers,
elvirus

@elvirusHDS Let me take a look at this today. I have it working locally, so it should be workable. Though admittedly I am just using it as a module in my application.

@elvirusHDS I created a pull request where I switched the code over to using angular-library-starter. #3
I tested by building and then copying the contents of the dist folder into the node_modules/ng2-heremaps folder of a new app where I had installed ng2-heremaps. It seems to work fine now.
@mjaric If my changes look good could you merge the pull request and deploy to NPM. Thanks!

checking. Will get back to you as soon as I try it in simple app

ok, version 0.2 is in npm now. @jedsmith13 good job on wrapping all build, packing and publishing stuff!!!
I have to download angular-cli since I didn't build any apps recently in angular. So give me few more minutes to check this build.

works! so you can use it from npmjs.org by adding
"ng2-heremaps": "~0.2.0", into dependencies in package.json

I'm not sure if peer dependency is required since it would be good to allow other people that uses older angular to use this lib too.
@elvirusHDS please confirm that it works for you now.
Thanks!

WOW! Guys, you are awesome!
I updated the dependency and the project builds now. That's great for the start!
You deserve a cake for that!
I obtained an appID and an apiCode at heremaps and when I start the application I get the following error:
Error: Uncaught (in promise): TypeError: Cannot read property 'UI' of undefined TypeError: Cannot read property 'UI' of undefined at https://localhost:5001/vendor.js:143920:44 at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke (https://localhost:5001/polyfills.js:2741:26) at Object.onInvoke (https://localhost:5001/vendor.js:58219:33) at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke (https://localhost:5001/polyfills.js:2740:32) at Zone.push../node_modules/zone.js/dist/zone.js.Zone.run (https://localhost:5001/polyfills.js:2491:43) at https://localhost:5001/polyfills.js:3225:34 at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (https://localhost:5001/polyfills.js:2774:31) at Object.onInvokeTask (https://localhost:5001/vendor.js:58210:33) at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (https://localhost:5001/polyfills.js:2773:36) at Zone.push../node_modules/zone.js/dist/zone.js.Zone.runTask (https://localhost:5001/polyfills.js:2541:47)
Can it be that I am doing something wrong here or is it in the library?
my here config:
export const hereConfig = {
appId: '{appId from heremaps}',
apiKey: '{appCode from heremaps}',
apiVersion: '3.0',
libraries: ['core', 'service']
}
When I remove 'geometry from the libraries array in the config, I get basically the same error but with UI instead of geometry...
excerpt from my app.module.ts:
[...]
import { HereMapsModule } from 'ng2-heremaps';
import { hereConfig } from './config/here-maps'
[...]
imports: [
[...]
HereMapsModule.forRoot(hereConfig),
],
my mapComponent:
<heremap [center]="{latitude: 52.2688736, longitude: 10.5267696}">
Any ideas? Did you guys see any map data?
Thank you so far,
best regards,
elvirus

I think you need to change config and include library 'ui' too. libraries
export const hereConfig = {
  appId: '{appId from heremaps}',
  apiKey: '{appCode from heremaps}',
  apiVersion: '3.0',
  libraries: ['core', 'service', 'ui']
}

Here is what dependency matrix looks like. So just add module name (not file name it will be generated for you under the hud). So to summarize libs:

core - always required
service - This module supports map tile retrieval, routing, geocoding, etc.
mapevents - This module provides functionality to enable user-interaction with the map, including map panning and pinch-to-zoom
ui - This module provides a set of pre-built cross-browser UI components (such as base map settings, zoom control, map scale) that can be added to the map. It also provides functionality to display location-specific info bubbles with arbitrary HTML content on the map.
clustering - This module provides functionality for marker clustering.
data - This module provides set of classes for display of KML and GeoJSON data.
places - This module simplifies the use of REST places API. (requires service)
pano - This module provides access to HERE StreetLevel imagery on WebGL-enabled devices. It supports switching the map to the StreetLevel rendering mode and navigation through StreetLevel panoramas. (requires service)

Ok,
awesome! It seems to be working. I have no errors and the map ui is shown. There are no map tiles displayed though but I think this is a problem of my container hierarchy. I should be able to figure this out on my own.
thank you so much!
Awesome lib! Awesome work!
Cheers,
elvirus


Literature | Maintenance

Add the below to our documentation.
https://www.linkedin.com/company/pyquant-news/posts/

https://github.com/PacktPublishing/Python-for-Algorithmic-Trading-Cookbook

This book looks very informative and useful to us sir

add them to our literature notes. Maintain literature.md document to track good things.
Also, point out at something that are bad.

a good linkedIn posts for some simple tips or ways to get stock data in easy manner
https://www.linkedin.com/company/quant-science/posts/

https://www.interactivebrokers.com/campus/ibkr-quant-news/implementing-technical-indicators-in-python-for-trading/

https://www.navyfederal.org/makingcents/investing/dollar-cost-averaging.html#:~:text=With a dollar-cost averaging,per-share cost over time.

https://www.tradingview.com/pricing/#compare


[Theming] theme.spacing doesn't accept multiple string arguments

Using a custom function for theme.spacing with multiple arguments (theme.spacing("xs", "sm")) used to work in v4.8, now it doesn't.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Given a custom spacing function like:
const customSpacing = key => {
  const mySpacings = { xs: 10, sm: 30, lg: 50 };
  return mySpacings[key] || key;
};

And applying it like so: padding: theme.spacing("sm", "xs")
The output is: padding: sm xs

Expected Behavior 🤔
Expected the output to be  padding: 30px 10px

Steps to Reproduce 🕹
CodeSandbox of the example above:
https://codesandbox.io/s/material-demo-sv3h3?file=/demo.js:430-455
If you change to "@material-ui/core": "~4.8.0" it works fine
Steps:

Notice how the div padding isn't properly applied (inspect the red div element)

Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.10.0

React

Browser

TypeScript

etc.

We had this effort that conflict with your use case: #20408. However, it seems that we didn't approach is correctly. What do you think of this fix?
diff --git a/packages/material-ui-system/src/spacing.js b/packages/material-ui-system/src/spacing.js
index 41d191eb8..27b20fc1e 100644
--- a/packages/material-ui-system/src/spacing.js
+++ b/packages/material-ui-system/src/spacing.js
@@ -79,6 +79,10 @@ export function createUnarySpacing(theme) {

   if (typeof themeSpacing === 'number') {
     return (abs) => {
+      if (typeof abs === 'string') {
+        return abs;
+      }
+
       if (process.env.NODE_ENV !== 'production') {
         if (typeof abs !== 'number') {
           console.error(`Material-UI: Expected spacing argument to be a number, got ${abs}.`);
diff --git a/packages/material-ui/src/styles/createSpacing.js b/packages/material-ui/src/styles/createSpacing.js
index 779a8d2ae..66a344b75 100644
--- a/packages/material-ui/src/styles/createSpacing.js
+++ b/packages/material-ui/src/styles/createSpacing.js
@@ -34,9 +34,6 @@ export default function createSpacing(spacingInput = 8) {

     return args
       .map((argument) => {
-        if (typeof argument === 'string') {
-          return argument;
-        }
         const output = transform(argument);
         return typeof output === 'number' ? `${output}px` : output;
       })
diff --git a/packages/material-ui/src/styles/createSpacing.test.js b/packages/material-ui/src/styles/createSpacing.test.js
index dc29b6289..9eabc0403 100644
--- a/packages/material-ui/src/styles/createSpacing.test.js
+++ b/packages/material-ui/src/styles/createSpacing.test.js
@@ -42,7 +42,12 @@ describe('createSpacing', () => {
     let spacing;
     spacing = createSpacing();
     expect(spacing(1, 'auto')).to.equal('8px auto');
-    spacing = createSpacing((factor) => `${0.25 * factor}rem`);
+    spacing = createSpacing((factor) => {
+      if (typeof factor === 'string') {
+        return factor;
+      }
+      return `${0.25 * factor}rem`
+    });
     expect(spacing(1, 'auto', 2, 3)).to.equal('0.25rem auto 0.5rem 0.75rem');
   });

Do you want to work on it? (and add a new test case to avoid regressions? :)

Hey @oliviertassinari  If it's cool with you, could I give this issue a shot? I'd really like to get my hands dirty with open source and this would be a good first step :)

@oliviertassinari Your test implies a breaking change.

@eps1lon The elements that could support it's a bug fix for a regression rather than a breaking change:

The test case we break in question comes from #20408. It's not directly linked to the issue we were trying to solve.

    spacing = createSpacing((factor) => `${0.25 * factor}rem`);
    expect(spacing(1, 'auto', 2, 3)).to.equal('0.25rem auto 0.5rem 0.75rem');

The only required test for #20408, that match the linked issue, was:

const spacing = createSpacing();
expect(spacing(1, 'auto')).to.equal('8px auto');

We should have had a test case for @zettca's use case before making #20408, to not introduce this regression

createSpacing((factor) => ${0.25 * factor}rem);

Why did we have a test if this was never supported? Please don't include internals in test or explicitly mark them as private to enable the whole team to work on the code.

@eps1lon Yeah, agree, this might not have been the wisest decision, it was meant to create a stronger constraint, to better explore the cope of the customization options available. Should we wait for v5 to change it back?

As I user, I expected that by using a custom function, its result wouldn't be "hijacked" in some special cases.
Our actual spacing function is something like this:
const spacing => key => {
  const mySpacings = { xs: 10, sm: 30, lg: 50 };
  switch (typeof key) {
    case "string":
      return mySpacings[key] || key;
    case "number":
      return 10 * key || 0;
    default:
      return 0;
  }
};

With something like this you can support factor spacing, "xs"/"sm"/"lg" spacing, as well as any other string (auto, unset), etc. Can't we support every use case like this?
Anyways, just my two cents on the matter.

As I user, I expected that by using a custom function, its result wouldn't be "hijacked" in some special cases

@zettca Yes, I think that we all agree that it's the desired direction to go into. The question is: how? Thanks for sharing more details on how you use the spacing function.

I can implement @oliviertassinari's proposed solution, if that's okay with you guys 😃


Fix fdPread: shouldn't move file offset

Fixes #958.
This is breaking a zig test, I still haven't been able to figure out why.

It seems, at the root of it, we have that embed.openfile does not implement io.ReaderAt. 😔

I could Seek, Read and then Seek back. But if any operation fails, I'm breaking the invariant of pread: “The file offset is not changed.”

@ncruces is it required for embed to implement this, or is it just due to our tests using embed?

No, not required. It's just due to tests using embed.
But it also means anyone using embed will start seeing pread failures. And it seems zig uses pread for most (all?) reads.
I came up with an alternative implementation that tries io.ReaderAt and falls back to io.Seeker doing multiple seeks. All tests pass. https://github.com/ncruces/wazero/commit/e12b34e2e3e8ab9e3d09d5c59afd63c28198712f
There's some prior to doing this. For instance, see Go's implementation of pread under Windows:
https://github.com/golang/go/blob/e870de9936a7efa42ac1915ff4ffb16017dbc819/src/internal/poll/fd_windows.go#L538-L546

thanks for the notes and the research leading to them!

If you want to go with an alternative fix, works for me, @achille-roussel will be starting some more abstraction work soon, and the important part is to have tests in to make sure this doesn't re-break later.

I'll go with this since at least it means no regression for zig folks.
The big issue is this leaving the file offset in an inconsistent state if the initial seeks succeed but the final one fails. It's still an improvement over the current situation (final offset is always wrong).
Other considerations don't really apply (pread is supposed to be thread-safe, but there's no concurrency in WASM). I can add some comments pointing this out.
I'll work on tests now.

@ncruces sounds good. we're going to cut the release in a couple days, and this is great to go in. You can add notes in RATIONALE.md and then code comment to there on the tradeoffs. you'll notice there are others.

I drifted you. for names, use export (capitalize first letter) and dot import like so 	. "github.com/tetratelabs/wazero/internal/wasi_snapshot_preview1"

thanks for hanging in there @ncruces!

No problem.
Thank you for wazero!


Controller won't close

I am able to call the controller and have it open up in a sheet, but it currently is not closeable and doesn't seem to respond to any gestures.
import UIKit

class SettingsViewController: UIViewController {

  override func viewDidAppear(_ animated: Bool) {
    super.viewDidAppear(animated)
    let controller = UIViewController()
    let transitionDelegate = SPStorkTransitioningDelegate()
    transitionDelegate.swipeToDismissEnabled = true
    transitionDelegate.customHeight = 350
    controller.transitioningDelegate = transitionDelegate
    controller.modalPresentationStyle = .custom
    self.present(controller, animated: true, completion: nil)
  }

  override func viewDidLoad() {
    super.viewDidLoad()
  }

}

I added the customHeight declaration for testing and that doesn't seem to work either as the controller takes up the height of the screen.
I am using the storyboard and I have added the SPStorkSegue class to my segue and it's set as a push segue, but have also tried setting it to open modally.

@anthonycollini hi!
You can create simple project and send me archive for testing?


allow fractional sizes in minimap

Hi,
I have a "retina" screen mac and wanted to make use of the smaller real pixels; currently I have 1 real pixel interline, 3 real pixels char height, and 2 real pixels char width. I also experimented with smaller sizes, but my poor eyesight disagreed.
Anyway, to do that, I needed the character sizes to be fractional – with a devicePixelRatio of 2, I want to use increments of .5. Hence my patch, and hence this pull request.

:+1: Thanks for that, I wasn't sure at first if a float would gives good results but I should have thought of HiDPI displays.
Out of curiosity, have you tried with values < 0.5?
I wonder if the minimum value should be set on a lower value.

Hi,
I haven't tried smaller values; I see that devicePixelRatio is set to
maximum of three, so to allow working with "real" pixels, the minimum
should be at most 0.3333. Again, haven't tried it.
Thanks for the prompt merge, that's awesome! 8-)
Jack
On 16 February 2015 at 22:49, Cédric Néhémie<EMAIL_ADDRESS>wrote:

Merged #271 https://github.com/fundon/atom-minimap/pull/271.
—
Reply to this email directly or view it on GitHub
https://github.com/fundon/atom-minimap/pull/271#event-236606122.


Add preprocessValue callback, just to allow users to change value a…

…s they type

This is useful to do normalizations, like transforming japanese numbers (e.g., １, ２, etc.) to the right alpha numbers (e.g., 1, 2, etc.).
I wasn't able to change anything as the component seems to completely manage its own state and it doesn't take defaultValue property.. directly changing value makes the cursor jump like crazy.
I tried adding a test for this, but Simulate.change and Simulate.keyDown

Coverage decreased (-40.4%) to 51.473% when pulling 3e3ba6467f3ce8fe11772be281f5c6f0942a4c30 on brunops:preprocess-value into 0d18e7465af5ee5f3108883c6a65974aa2b553ff on patw0929:master.

directly changing value makes the cursor jump like crazy

I think this is the real issue. IMO normalization should be done by saving fixed value and passing it as value prop.

@janmarek I meant passing value directly makes the cursor jump very weirdly, not only to the end, but very odd behavior, probably because the component is managing its own state internally. Not sure if it's related to the fact that utilsScript already does formatting (cursor already jumps even on demo page, but a "normal jump").
For the use case I mentioned, the preprocessValue part makes the component work as is.

@patw0929 any thoughts on this?

Hi @brunops
Sorry, I'm busy at my work recently. :astonished: :astonished: :astonished:
Have a not carefully thought here, maybe the "normalization" can be a build-in feature, and handling in TelInput's keydown event?

Oh, no problem man.
I wouldn't add normalization as part of the plugin itself, I think providing a callback where people can process the input any way they want to is more flexible (most people will probably never use this).

Sorry for being busy so long... :sob:
I'm curious about the need of normalizations. Because we already restrict the input keys in 0 ~ 9 & + in handleKeyPress function, so users should not have any chance to key in full width numbers like １, ２, right?

@patw0929 no worries man!
You are correct, the problem appears when full width numbers need to be allowed, in a way that instead of when typing １, instead of showing nothing, would actually show 1. Let me know if that's clear

Going to close this due to age, not opposed to revisiting the underlying changes / ideas though!


Revise guidance on creating pull requests

Updated to:

make it clearer that pull requests are publicly visible on GitHub, and so can be seen by other people
remove 'changing the information here will not change the original description, but will send it in addition' as it's not clear to the user what the difference between those two things is; why they should care or what they should do about it.
try and remove some overlap with step 6 (the Design System team being notified of the PR)

You can preview this change here:
Built with commit f1fcf0efd2f30453a9e0349fa07ff41ab5f6ecd9
https://deploy-preview-972--govuk-design-system-preview.netlify.com


Categorize action types as prepost and inflow

Describe the improvement
Categorize action types as prepost and inflow to differentiate action types that can be configured from 'Actions' UI (e.g: pre issue access token action) and action types that can be incorporated along with the other similar constructs that can be used within a flow (e.g: authentication)
This is because the overall experience of these categories are different. Refer the definitions and examples below.
Pre-Post Actions:
This category represents actions that occur at the boundaries of a flow, either before or after it (pre-post actions).
e.g: pre issue access token, pre profile update
InlineFlow Actions:
This category includes actions that are executed within the flow, as part of the flow execution itself, typically for performing custom functions.
Here there are already available system defined similar components. So it is important to define these custom functions providing the similar experience. Therefore, these functions should be supported over the same set of APIs and the UX
e.g: authentication
With this Pre-Post Actions will be able to be configured and managed from the 'Actions' UI.
And InFlow actions will be managed and configured with the same experience, the respective available system defined components that does the same functionality are configured. For example, there are other system defined authenticators like google, email/password, TOTP, etc in authentication flow. So adding a custom authentication should give a similar experience for the user.
Additional context
Related to https://github.com/wso2/product-is/issues/20809

[x] Introduce pre-post and in-flow action type categories
[x] Update REST API to not to support for in-flow action types
[ ] Update the API documentation and actions documentation

All PRs are merged


Memory Leak from Training Step

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes, although my code is somewhat based on the MNIST deep learning tutorial.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 14.04 VERSION="14.04.5 LTS, Trusty Tahr"
TensorFlow installed from (source or binary):
Installed via the VirtualEnv method
TensorFlow version (use command below):
1.1 and 1.2
Bazel version (if compiling from source):
CUDA/cuDNN version:
CUDA Version 8.0.44
GPU model and memory:
GeForce GTX 780M 4GB
Exact command to reproduce:
self.sess.run(self.train_step, feed_dict={self.x: trainingdata, self.y_true: traininglabels, self.keepratio: self.training_keep_rate})

Describe the problem
This is very similar to the bug report I submitted here, but is a bit of a slower leak and is present in both TF 1.1 and 1.2.  I have finalized my graph.  Using the architecture described by Zeiler et al., 2013 (ZF Net), batch sizes of 64, and 224x224 grayscale (1 channel) input, it leaks approximately 4GB after approximately 3000 batches.  This makes it unworkable, for say, 80 epochs of ImageNet training.  I have confirmed that the leak either does not occur or is much less severe (hard to tell which) if I comment out the training line (i.e. still do all of my preprocessing and loading).
As directed in that last linked issue, I tried to call sess.run with
options=tf.RunOptions(trace_level=tf.RunOptions.FULL_TRACE), run_metadata=run_metadata
and start the program with
env TF_CPP_MIN_VLOG_LEVEL=1 python deep_learning_main.py
but the amount of spew was enormous, and it won't respond to keyboard interrupts (I have to kill the job).  If that info would be helpful, how do I go about recording/saving this information properly to upload and help you all debug?
1_08.zip

Write the log (with TF_CPP_MIN_VLOG_LEVEL=1) to a file and upload it somewhere so that we can download it.
Also, see if you can reproduce the problem with a simpler program. The current program is over 1000 lines, making it hard to debug a memory leak. Additionally, I cannot run the program because you have some hardcoded paths, and the matplotlib dependency makes it hard to run internally. See if synthetic data can be used to remove the dependency on the imagenet data.

I apologize for not getting back to this and being able to help; I've run out of time and had to move on to a new project.  However, I have had a similar issue with PyTorch; apparently it is an issue with CUDA and maybe my GPU.  Perhaps the TF leak is caused by same issue?  See
https://discuss.pytorch.org/t/tracking-down-a-suspected-memory-leak/1130/44
https://discuss.pytorch.org/t/memory-usage-leak/5645

@reedwm btw, regarding using TF_CPP_MIN_VLOG_LEVEL to debug memory leaks, it became less useful between 1.0.1 and 1.1
Some of the deallocation messages started missing allocation ids, so you can't tell how much memory got reclaimed.
ie for some of my scripts I see messages like this
'2017-05-09 15:31:16.865982: I tensorflow/core/framework/log_memory.cc:35] LOG_MEMORY MemoryLogTensorDeallocation { allocator_name: "cpu" }'
instead of
I tensorflow/core/framework/log_memory.cc:35] LOG_MEMORY MemoryLogTensorDeallocation { allocation_id: 235 allocator_name: "cpu" }

@JamesKostas That's ok. Respond to this post if you ever get time to upload the logs or reproduce the problem with a simpler program.
@yaroslavvb Can you file a separate bug? allocation_id might be only printed if its not 0, but I'm not sure.

@reedwm -- filed under https://github.com/tensorflow/tensorflow/issues/13087

Without a reproducible test case, it seems unlikely we are going to make much headway, especially if you are working on a new project. So I am closing for now.

@zheng-xq, FYI.


Debug

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues

https://github.com/yiisoft/yii-debug/pull/223

Overall, the change makes sense 👍


Streaming SSR

React has support for streaming SSR which is being reworked for React 18. We should support it. Some potential issues:

It seems to be tied to Node's stream APIs, it may not work on worker environments (like Cloudflare's). (solved in later releases)
Some integrations (like Apollo client) may not support it, so it should be opt in.

Any update on this?

I started work on my personal fork. It's still in exploratory phase but I can safely say that a) it works, b) it brings breaking changes in data fetching API, c) but the new API will be a lot nicer (you can fetch from any component, not just pages). Please check back soon, I'm hoping to release in a few weeks.

This is working in 0.6.

This "React 18 (server components etc.)" is mentioned as planned on: https://rakkasjs.org/guide/feature-comparison
Should that be updated if it's now released?

Version 0.6 is currently rakkasjs@next and hasn't been officially released. It's still in rough alpha stage but streaming SSR with Suspense for data fetching is functional. I'm aiming for a release right after Vite 3 stable is out (should be in about a month).
Development is on the next branch and there are a few quite exciting features you might like to check.
I closed the issue so that people don't work on a PR about it. I updated the closing comment accordingly.

There's some really cool progress on the next branch. What I'm missing from the above linked example however is the ability to imperatively call the server code to get the data from outside the render cycle of the component.
With the next branch, if I want to fetch something again I have to set a new state in the component and then call refetch. This can lead to a lot of state juggling for complex queries. There's also no way to call these endpoints from outside components (eg. when you need more control over when and what resources are loaded forcing you to default to fetch and API routes again).
For comparison: Blitz.js has had a similar concept to the hook useServerSideQuery that is proposed here. Blitz does require you to specify these functions in specially named files but you can simply import them on the client and they will be magically transformed into http requests just like here. And since they are also available as simple functions they can be called from anywhere which makes them insanely ergonomic - and they can easily be wrapped into a special hook if that's needed.

@IgnusG thanks for your interest!
The linked example is just a rough demonstration of the concept. This week's focus will be implementing the following plan:
There will be two imperative functions called runServerSideQuery and runServerSideMutation. useServerSideQuery and useServerSideMutation will be convenience wrappers around useQuery+runServerSideQuery  and useMutation+runServerSideMutation respectively.
useQuery is a minimal, Suspense-only subset of the similarly named react-query API and it's been already implemented. And useMutation will be a subset of react-query's useMutation. I'm planning to drop my own implementations in favor of the original react-query ones when/if they release a streaming-compatible version.
The difference between runServerSideQuery and runServerSideMutation is that the former can be called either during SSR or on the client so it can appear on the render path and throw Suspense promises. The latter will only be available on the client and can only be called from event handlers, useEffect callbacks etc. Because runServerSideQuery can be called on the server, it requires a context parameter (which will be passed to the callback). It will also issue a GET request by default and it will be possible to prerender the responses for static sites.
In short, you will be able to do things imperatively, like runServerSideMutation(() => doSomethingOnTheSever()) but I expect the useServerSide* hooks to be adequate for most scenarios.
I'm also hoping to provide integration examples with telefunc and tRPC for more complex RPC scenarios. And finally, API routes and fetch will of course continue to be available for building REST or GraphQL endpoints.

@IgnusG thanks for your interest!
The linked example is just a rough demonstration of the concept. This week's focus will be implementing the following plan:
There will be two imperative functions called runServerSideQuery and runServerSideMutation. useServerSideQuery and useServerSideMutation will be convenience wrappers around useQuery+runServerSideQuery and useMutation+runServerSideMutation respectively.
useQuery is a minimal, Suspense-only subset of the similarly named react-query API and it's been already implemented. And useMutation will be a subset of react-query's useMutation. I'm planning to drop my own implementations in favor of the original react-query ones when/if they release a streaming-compatible version.
The difference between runServerSideQuery and runServerSideMutation is that the former can be called either during SSR or on the client so it can appear on the render path and throw Suspense promises. The latter will only be available on the client and can only be called from event handlers, useEffect callbacks etc. Because runServerSideQuery can be called on the server, it requires a context parameter (which will be passed to the callback). It will also issue a GET request by default and it will be possible to prerender the responses for static sites.
In short, you will be able to do things imperatively, like runServerSideMutation(() => doSomethingOnTheSever()) but I expect the useServerSide* hooks to be adequate for most scenarios.
I'm also hoping to provide integration examples with telefunc and tRPC for more complex RPC scenarios. And finally, API routes and fetch will of course continue to be available for building REST or GraphQL endpoints.

Ah perfect! I'm not a big fan of react-query which is why I was mentioning the imperative approach. runServerSideQuery and runServerSideMutation are pretty much the exact thing I was hoping for (similar to what Blitz offers with its query and mutation handlers - but of course they are built on top of NextJS - whereas I prefer Vite).
I'm curious about the tRPC integration too! I was quite happy with it last time I used it.

I'm curious about the tRPC integration too! I was quite happy with it last time I used it.

It should be usable even today. I know someone was working on it at some point but I've never tried it myself.

I'm not a big fan of react-query

I believe a framework like Rakkas has to come with something that works out of the box. To my knowledge Relay is the only library that has semi-official streaming SSR with Suspense support. So I had to come up with something, react-query is popular and easy to use so I based my interim solution on that. As more and more libraries start to support streaming with Suspense, hopefully we can make more and more data fetching methods available.
Of course you can use pretty much anything today if you don't need SSR though.

I'm not a big fan of react-query

I believe a framework like Rakkas has to come with something that works out of the box. To my knowledge Relay is the only library that has semi-official streaming SSR with Suspense support. So I had to come up with something, react-query is popular and easy to use so I based my interim solution on that. As more and more libraries start to support streaming with Suspense, hopefully we can make more and more data fetching methods available.
Of course you can use pretty much anything today if you don't need SSR though.

Yes that's understandable. One of the goals of rakkas is after all to provide an out-of-the-box opinionated experience.
Can't wait for future updates on rakkasjs@next!

@IgnusG version 0.6.0-next.6 supports import * as rakkas from "rakkasjs". Also implemented runServerSideMutation and useMutation. runServerSideMutation is can be used for client-only data fetching.


OnlyIfModified should be true by default

Can you please elaborate? Do you have a specific use case? I'm hesitant to change the default behaviour of such a central configuration item.

The default behaviour caused my tasks to download a 80 MB ZIP-File everytime I ran the task.
I believe this is highly unintuitive and contrary to Gradles default Up-To-Date machanic.
It took me over an hour to figure out why this happened, because I was so accustomed to the default Up-To-Date check in Gradle. This may as well be my fault though for looking in the wrong places.

Ah OK. I see what you mean. However, as I said, the configuration item is very central and changing its default behaviour might break existing builds. I'm afraid we cannot do this for the time being (unless someone else has a good idea for a workaround).

I can absolutely understand that. For now you could add a paragraph to Usage or Examples in the README to showcase the default behavior vs. what people might expect the default behaviour to be.
Being down there in a long list of properties shouldn't be the only place to find such the "default behaviour of such a central configuration item". ;)

That's a good idea! Thanks. I amended the README accordingly.


Avoid including 'index' (or equivalent) as part of module name during error reporting

When we resolve an external module to a folder index file like index.d.ts (or through the typing field of package.json), we should not consider that index part to be part of the filename for the purposes of error reporting.
For example, we currently display

Module '"c:/github/DefinitelyTyped/react-router/index"' has no exported member 'LinkProps'.

Instead it should be:

Module '"c:/github/DefinitelyTyped/react-router"' has no exported member 'LinkProps'.

I think this is already solved:
// @filename: ./nested/index.d.ts
export type A = 'A'

// @filename: ./foo.ts
import { B } from './nested' // Module '"./nested"' has no exported member 'B'.ts(2305)

cc @jakebailey


Add required packages for pylibmc

/cc @tmatsuo @bshaffer

"Really high demand", "required for the product to work", or "we have a
specific use case in the documentation that needs this". In this case, its
all three. We need this for the Memcache documentation and sample, which is
a critical feature.
On Thu, Oct 20, 2016, 6:12 PM Douglas Greiman<EMAIL_ADDRESS>wrote:

@duggelz commented on this pull request.
In resources/apt-packages.txt
https://github.com/GoogleCloudPlatform/python-runtime/pull/32#pullrequestreview-5182395
:

@@ -30,3 +30,11 @@ libblas-dev
libfreetype6-dev
liblapack-dev
libquadmath0
+# Needed by pylibmc

What the general policy for what goes in here and what doesn't? "Yes is
forever" :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/python-runtime/pull/32#pullrequestreview-5182395,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPUcxsI_yqQA_yZVWZ4UPpZhM-E-lkRks5q2BFkgaJpZM4Kcqyx
.


Ruleset and Skill Resource

This PR
Will remove the filter of rulesets based on skill set existence.
Instead it will filter the skills being referenced i they are not existent.
The rulesets will still be present.

I'm not entirely convinced the issue is completely resolved by removing this code. The code that Will had added here is checking for and comparing the skills ids that return in this resource to existing genesyscloud_routing_skill resource types and removing/filtering any non-matching skills.
I think the full fix to this is to use a CustomAttributeResolver hook in the exporter definition to do the comparisons between the skill references found in the outbound ruleset, and the actual skills found in the genesyscloud_routing_skill resource type and filter out / log any references that cannot be resolved

I'm not entirely convinced the issue is completely resolved by removing this code. I mean, it will fix the hanging issue, but the code that Will had added here for DEVTOOLING-319 is checking for and comparing the skills ids that return in this resource to existing genesyscloud_routing_skill resource types and removing/filtering any non-matching skills. We'll just get another report of DEVTOOLING-319 without handling this issue properly.
I think the full fix to this is to use a CustomAttributeResolver hook in the exporter definition to do the comparisons between the skill references found in the outbound ruleset, and the actual skills found in the genesyscloud_routing_skill resource type and filter out / log any references that cannot be resolved

Hi Brian..
The problem is CustomAttributeResolver does only have references for the attributes and  to filter them or modify them.
if we want to change the instances of exporter based on some condition , we need to overridde the GetResourceFunc of Exporter
In other words modify the GetResourceFunc method to give us the values we want after filter


Issue in compilation of lighting-app

Reproduction steps
With SHA 49654486db9ae006f5c9e2fc89b59c622ad614dd

While compiling lighting-app, I am running into the following issue;

Error Log;

FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/mcuboot/zephyr/zephyr_pre0.map
: && ccache /Users/priyankahonnakasturi/chip-nordic-tools/gnuarmemb/bin/arm-none-eabi-gcc   zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj -o zephyr/zephyr_pre0.elf  zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj  -fuse-ld=bfd  -Wl,-T  zephyr/linker_zephyr_pre0.cmd  -Wl,-Map=/Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/mcuboot/zephyr/zephyr_pre0.map  -Wl,--whole-archive  app/libapp.a  zephyr/libzephyr.a  zephyr/arch/common/libarch__common.a  zephyr/arch/arch/arm/core/aarch32/libarch__arm__core__aarch32.a  zephyr/arch/arch/arm/core/aarch32/cortex_m/libarch__arm__core__aarch32__cortex_m.a  zephyr/arch/arch/arm/core/aarch32/mpu/libarch__arm__core__aarch32__mpu.a  zephyr/lib/libc/minimal/liblib__libc__minimal.a  zephyr/lib/posix/liblib__posix.a  zephyr/soc/arm/common/cortex_m/libsoc__arm__common__cortex_m.a  zephyr/soc/arm/nordic_nrf/nrf52/libsoc__arm__nordic_nrf__nrf52.a  zephyr/drivers/clock_control/libdrivers__clock_control.a  zephyr/drivers/gpio/libdrivers__gpio.a  zephyr/drivers/flash/libdrivers__flash.a  zephyr/drivers/timer/libdrivers__timer.a  zephyr/drivers/pinctrl/libdrivers__pinctrl.a  modules/nrf/lib/fprotect/lib..__nrf__lib__fprotect.a  modules/nrf/drivers/hw_cc310/lib..__nrf__drivers__hw_cc310.a  modules/mcuboot/boot/bootutil/zephyr/libmcuboot_util.a  modules/hal_nordic/nrfx/libmodules__hal_nordic__nrfx.a  -Wl,--no-whole-archive  zephyr/kernel/libkernel.a  -L"/Users/priyankahonnakasturi/chip-nordic-tools/gnuarmemb/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m+fp/hard"  -L/Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/mcuboot/zephyr  -lgcc  zephyr/arch/common/libisr_tables.a  -no-pie  -mcpu=cortex-m4  -mthumb  -mabi=aapcs  -mfpu=fpv4-sp-d16  -mfp16-format=ieee  -Wl,--gc-sections  -Wl,--build-id=none  -Wl,--sort-common=descending  -Wl,--sort-section=alignment  -Wl,-u,_OffsetAbsSyms  -Wl,-u,_ConfigAbsSyms  -nostdlib  -static  -Wl,-X  -Wl,-N  -Wl,--orphan-handling=warn  /Users/priyankahonnakasturi/chip-nordic-tools/nrfconnect/sdk-nrf/nrfxlib/crypto/nrf_cc310_platform/lib/cortex-m4/hard-float/no-interrupts/libnrf_cc310_platform_0.9.15.a  /Users/priyankahonnakasturi/chip-nordic-tools/nrfconnect/sdk-nrf/nrfxlib/crypto/nrf_cc310_bl/lib/cortex-m4/hard-float/no-interrupts/libnrf_cc310_bl_0.9.12.a && cd /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/mcuboot/zephyr && /Users/priyankahonnakasturi/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages/cmake/data/bin/cmake -E echo
/Users/priyankahonnakasturi/chip-nordic-tools/gnuarmemb/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.bfd: zephyr/zephyr_pre0.elf section `datas' will not fit in region `FLASH'
/Users/priyankahonnakasturi/chip-nordic-tools/gnuarmemb/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.bfd: region `FLASH' overflowed by 64 bytes
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
[90/537] Generating gen/app-codegen/cpp-app/app/PluginApplicationCallbacks.h, gen/app-codegen/cpp-app/app/callback-stub.cpp
2022-11-29 16:14:02 INFO    Parsing idl from /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/../lighting-common/lighting-app.matter
2022-11-29 16:14:02 INFO    Running code generator cpp-app
2022-11-29 16:14:02 INFO    File to be generated: app/PluginApplicationCallbacks.h
2022-11-29 16:14:02 INFO    Writing new data to: /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/gen/app-codegen/cpp-app/app/PluginApplicationCallbacks.h
2022-11-29 16:14:02 INFO    File to be generated: app/callback-stub.cpp
2022-11-29 16:14:02 INFO    Writing new data to: /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/gen/app-codegen/cpp-app/app/callback-stub.cpp
2022-11-29 16:14:02 INFO    Done
[326/537] Building C object modules/openthread/platform/CMakeFiles/openthread_platform.dir/alarm.c.obj
FAILED: modules/mcuboot/mcuboot_subimage-prefix/src/mcuboot_subimage-stamp/mcuboot_subimage-build mcuboot/zephyr/zephyr.hex mcuboot/zephyr/zephyr.elf /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/modules/mcuboot/mcuboot_subimage-prefix/src/mcuboot_subimage-stamp/mcuboot_subimage-build /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/mcuboot/zephyr/zephyr.hex /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/mcuboot/zephyr/zephyr.elf
cd /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build/mcuboot && /Users/priyankahonnakasturi/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages/cmake/data/bin/cmake --build . --
[338/537] Linking C static library modules/nrf/drivers/hw_cc310/lib..__nrf__drivers__hw_cc310.a
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /Users/priyankahonnakasturi/connectedhomeip/.environment/pigweed-venv/bin/cmake --build /Users/priyankahonnakasturi/connectedhomeip/examples/lighting-app/nrfconnect/build
priyankahonnakasturi@priyankas-mbp nrfconnect %

Steps to reproduce:

1. cd ~/connectedhomeip
2. git reset --hard 49654486db9ae006f5c9e2fc89b59c622ad614dd
3. export PKG_CONFIG_PATH="/opt/homebrew/opt/openssl@3/lib/pkgconfig"
4. source scripts/activate.sh
5. source ~/032321_install_nordic_tools.sh
6. python3 scripts/setup/nrfconnect/update_ncs.py --update
7. cd examples/lighting-app/nrfconnect
8. west build -b nrf52840dk_nrf52840 --pristine always

Bug prevalence
Today
GitHub hash of the SDK that was being used
49654486db9ae006f5c9e2fc89b59c622ad614dd
Platform
nrf, python
Platform Version(s)
Darwin
Anything else?
No response

@phonnakasturi-apple does this run into the same issue for you?
scripts/examples/nrfconnect_example.sh lighting-app nrf52840dk_nrf52840

It looks like your linked binary ended up too big to fit on the chip you are building for, which is a little surprising given that we do build pretty much this configuration (but with RPC additionally enabled) in CI.

I'm able to build this target locally on Linux (I don't have mac to verify it for darwin). Generally the region that was overflown should be occupied in almost 100% (99,33% in my case). I assume something may be configured wrong in the local environment, so e.g. different toolchain version than recommended is used and target is linked in slightly different way. @phonnakasturi-apple could you attach the full log from the build and not only the failure part? I will try to compare some details with my own configuration.

@bzbarsky-apple With scripts/examples/nrfconnect_example.sh lighting-app nrf52840dk_nrf52840 ; I ran into the same issue.
Attaching the complete log ;
nordic_issue.txt

@kkasperczyk-no Here is the complete log;
nordic_issue1.txt

@bzbarsky-apple @kkasperczyk-no I see the same issue with lighting app while all-cluster-app builds fine with the same SHA using the above script.

@cjandhyala that's understandable, because by default all-clusters-app is built with OTA Software Update disabled and lighting-app with OTA support enabled. The problem you see is related to the fact of overflowing the region reserved for bootloader that is used for the software update purpose, so that's why it won't be reproduced for all-clusters-app.

Hi, looks like the flash overflow issue occurs on gcc 9.2.1 (and perhaps other 9 minor revisions). We'll try to optimize the flash usage in the future so that the build success doesn't depend so much on the used toolchain, but, anyway, newer versions of Zephyr (and hence nRF Connect SDK) will require using Zephyr-SDK toolchain rather than arm-none-eabi-gcc I recommend that you update your scripts to use that toolchain as described in: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_installing.html#install-a-toolchain.
Btw, CI uses Pigweed-supplied GCC 10.3.1 and currently, it seems to be also sufficient.

we are running 'python3 scripts/setup/nrfconnect/update_ncs.py --update ' and we have the latest zephyr SDK
=== updating zephyr (zephyr):
HEAD is now at<PHONE_NUMBER> [nrf fromtree] drivers: spi: fix sample syntax
BTW updating the arm GNU compiler to latest , we are able to build the lighting app. Is there any issue in using the latest compiler or do you recommend some version of it ?


Failing CuPy tests

Since the introduction of https://github.com/dask/dask/pull/6738, a few CuPy tests have broken.

1 bincount test fails after #7183 ;
16 tri* tests fail after #6997 .

We're discussing and trying to allocate GPUs for Dask PRs in the near future, so I'll probably wait for that to work on fixing the tests above.

Thanks for tracking this @pentschev!

For reference - I've documented some affected behavior under https://github.com/dask/dask-ml/issues/803 as well.

cc @thomasjpfan, in case you have a chance to look at the bincount issue from https://github.com/dask/dask/pull/7183.

@pentschev can you try this and see if it fixes the cupy tests for bincount? https://github.com/dask/dask/pull/7391

@GenevieveBuckley thanks for pinging me, but unfortunately I still see the same failure with #7391 :
======================================================= FAILURES =======================================================
____________________________________________________ test_bincount _____________________________________________________

    @pytest.mark.skipif(
        not IS_NEP18_ACTIVE or cupy.__version__ < LooseVersion("6.4.0"),
        reason="NEP-18 support is not available in NumPy or CuPy older than "
        "6.4.0 (requires https://github.com/cupy/cupy/pull/2418)",
    )
    def test_bincount():
        x = cupy.array([2, 1, 5, 2, 1])
        d = da.from_array(x, chunks=2, asarray=False)
        e = da.bincount(d, minlength=6)
>       assert_eq(e, np.bincount(x, minlength=6))

dask/array/tests/test_cupy.py:934:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

a = array([0, 2, 2, 0, 0, 1]), b = array([0, 2, 2, 0, 0, 1]), check_shape = True, check_graph = True, check_meta = True
check_chunks = True, kwargs = {}
a_original = dask.array<_bincount_agg-aggregate, shape=(6,), dtype=int64, chunksize=(6,), chunktype=numpy.ndarray>
b_original = array([0, 2, 2, 0, 0, 1]), adt = dtype('int64'), a_meta = array([], dtype=int64)
a_computed = array([0, 2, 2, 0, 0, 1]), bdt = dtype('int64'), b_meta = None

    def assert_eq(
        a,
        b,
        check_shape=True,
        check_graph=True,
        check_meta=True,
        check_chunks=True,
        **kwargs,
    ):
        a_original = a
        b_original = b

        a, adt, a_meta, a_computed = _get_dt_meta_computed(
            a, check_shape=check_shape, check_graph=check_graph, check_chunks=check_chunks
        )
        b, bdt, b_meta, b_computed = _get_dt_meta_computed(
            b, check_shape=check_shape, check_graph=check_graph, check_chunks=check_chunks
        )

        if str(adt) != str(bdt):
            # Ignore check for matching length of flexible dtypes, since Array._meta
            # can't encode that information
            if adt.type == bdt.type and not (adt.type == np.bytes_ or adt.type == np.str_):
                diff = difflib.ndiff(str(adt).splitlines(), str(bdt).splitlines())
                raise AssertionError(
                    "string repr are different" + os.linesep + os.linesep.join(diff)
                )

        try:
            assert (
                a.shape == b.shape
            ), f"a and b have different shapes (a: {a.shape}, b: {b.shape})"
            if check_meta:
                if hasattr(a, "_meta") and hasattr(b, "_meta"):
                    assert_eq(a._meta, b._meta)
                if hasattr(a_original, "_meta"):
                    msg = (
                        f"compute()-ing 'a' changes its number of dimensions "
                        f"(before: {a_original._meta.ndim}, after: {a.ndim})"
                    )
                    assert a_original._meta.ndim == a.ndim, msg
                    if a_meta is not None:
                        msg = (
                            f"compute()-ing 'a' changes its type "
                            f"(before: {type(a_original._meta)}, after: {type(a_meta)})"
                        )
                        assert type(a_original._meta) == type(a_meta), msg
                        if not (np.isscalar(a_meta) or np.isscalar(a_computed)):
                            msg = (
                                f"compute()-ing 'a' results in a different type than implied by its metadata "
                                f"(meta: {type(a_meta)}, computed: {type(a_computed)})"
                            )
>                           assert type(a_meta) == type(a_computed), msg
E                           AssertionError: compute()-ing 'a' results in a different type than implied by its metadata (meta: <class 'numpy.ndarray'>, computed: <class 'cupy.core.core.ndarray'>)
E                           assert <class 'numpy.ndarray'> == <class 'cupy....core.ndarray'>
E                             +<class 'numpy.ndarray'>
E                             -<class 'cupy.core.core.ndarray'>

dask/array/utils.py:320: AssertionError

Thanks Peter, I might take more of a look at it today

It seems .meta is always being made a numpy array (rather than updating to whatever the array type actually is). Let me see if I can change that

Thanks Peter! Fixed in this commit: https://github.com/dask/dask/pull/7391/commits/6bf5340e7434ac40de7812d90902fc9074bfad6b
I have cupy version 9.0.0b3 installed on my machine locally, and the cupy test_bincount passes with this change.
pytest dask/array/tests/test_cupy.py::test_bincount

As you say, the other tests related to https://github.com/dask/dask/pull/6997 are still failing. PR https://github.com/dask/dask/pull/7391 doesn't address those.

Hmm, it seems that the like kwarg for numpy array creation was only introduced in numpy version 1.20
This means my fix works if you have a recent version of numpy, but is now breaking the dask CI tests because the minimum numpy dependency allowed is version 1.15.1 See https://github.com/dask/community/issues/136
Not sure what's the best way to handle it.

I added https://github.com/dask/dask/pull/7391#discussion_r594983434 on the PR, using array_safe should resolve issues with older NumPy versions. 😄
Thanks @GenevieveBuckley for working on that!


About extractive labels

Hi，I've got extractive labels problem that are pressing on me.
I follow the steps：

"generate_ext_labels_arxiv_data" from raw arxiv dataset(arxiv_train/val.pk.bin)，ps: It has been set  start_id/end_id :train(from to 203037) and val(from 0 to 6436) separately.
and then combined with arxiv_train/val.pk.bin

but after combined the arxiv_train/val.pk.bin data size are 291/437 kb separately，the val is bigger than train
（I use above data to train the hier model：model is not improved）
Can you answer this question or point out my mistake ？ thank u！ @potsawee

On my disk, arxiv_{train/val/test}.pk.bin are 7.1GB, 219MB, 219MB, respectively. Are you sure you did the initial data pre-processing correctly?

291/437 kB sounds like your data consists of ~10 examples rather than 200k,6k examples. You could do a simple check to see how many examples are there by e.g. len(data) or len(data_xtras) or whatever you call your data variable. You should see this show 203,037 for training set and 6,436 for validation set (arxiv dataset).

After I deleted this line, it became correct：
“data = data[:10] # just to show an example”


count_if functors should not require const call operators

The following snippet (created from the example in the docs) does not compile.
#include <thrust/count.h>
#include <thrust/device_vector.h>
#include <iostream>

struct is_odd
{
  __host__ __device__
  bool operator()(int &x)
  {
    return x & 1;
  }
};

int main() {
    thrust::device_vector<int> vec(5);
    vec[0] = 0;
    vec[1] = 1;
    vec[2] = 2;
    vec[3] = 3;
    vec[4] = 4;

    int result = thrust::count_if(vec.begin(), vec.end(), is_odd());
    std::cout << result << "\n";

}

It seems is_odd is lacking the const attribute in operator(), since it works when I add it.
nvcc version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2017 NVIDIA Corporation
Built on Fri_Nov__3_21:07:56_CDT_2017
Cuda compilation tools, release 9.1, V9.1.85

Updated title to reflect fix. Discussion in #1088 is relevant.

@allisonvacanti  thank you for the fast response! Should the docs be fixed while #1088 is discussed? I am using thrust in a course and multiple students have reported this problem. Unfortunately, none were able to figure out the solution (put const in the argument) as the resulting error is not really helpful (for c++ beginners, at least).

Agreed, those issues give exceptionally poor diagnostics and the docs should be updated. I'll look into what's involved in updating those doxygen pages.


crypto 3.0.1 dependency update

need an update of aws_s3_client

highly appreciate if able to merge agent3bood:null-safety branch


Sometimes redundant services are printed/converted in kompose convert

Note that there's a redundant file "web-svc.json" created message.
➜ examples(master)$ ../kompose convert
file "web-rc.json" created
file "web-svc.json" created
file "redis-rc.json" created
file "web-svc.json" created
file "redis-svc.json" created

➜ examples(master)$ ../kompose convert
file "redis-rc.json" created
file "web-rc.json" created
file "redis-svc.json" created
file "web-svc.json" created

Yup. Also I have to re-structure convert function. It's too long and difficult to follow somehow.

Done. Convert function is now more easier to keep track. Issue is also fixed by https://github.com/skippbox/kompose2/commit/2e986b61e7d80617fb29265d70cf167ee1fa4990


[Hotfix] Send request to import account iff user does not cancel.

[#OSF-5756]

I don't understand why this is necessary; don't we prevent the request if the user cancels here: https://github.com/CenterForOpenScience/osf.io/pull/5055/files#diff-780e22e6e487060eaba79b328e4c746cR156 ?

That's a different case -- it's hit when the user has only one ExternalAccount connected for the addon

This is the troublesome case. connectExistingAccount is being .bind-ed as the callback function. The dropdown's value (an external_account_id) is passed in if the user clicks Import, null if Cancel. The case where they have only one account assumes that their only account is the one that they choose, and is checking that they confirmed the import, but is doing so before connectExistingAccount is called.

Thanks for the clarification.


Accounts Minting Whitelist

Add whitelisting for accounts (in addition to existing contracts whitelist).
(Or a combined/universal whitelist)

current whitelist is for contracts.  Would like to do the same thing for accounts, which is currently not supported.

FYI, the whitelist can't be combined for several reasons, mostly keeping Accounts the main NFTHolder mode and being retro compatible on upgrade from previous version.

can we do this via multisig? Need to discuss.  Multi sig is global - for the entire account; not specific to cep-78.   May need to resolve with a proxy account, which would serve as a whitelist.

@RitaMAllenCA The open  PR is working though and is tested. But Ryo submitted the idea of switching to dictionaries both lists, Zoltan likes the idea and I was wondering if Karan would let it be into dictionaries as per comment on the PR https://github.com/casper-ecosystem/cep-78-enhanced-nft/pull/162#issuecomment-1473783748 for next version.
For the multisig part, I am not sure what is meant like that but if Karan wants to explain a proxy we can have a look.


Zoom 6 v1.1 relief is a bit chunky compared to v1.0

http://tangrams.github.io/walkabout-style/#6/40.622/-123.871
v1.0

v1.1

http://tangrams.github.io/walkabout-style/#6/45.406/8.097
v1.0

v1.1


Publish to GitHub Marketplace

There are several other installer actions in addition to Pulumi's own -uses: docker://pulumi/actions.  Is there any intention to publish this action?

Yes, this is tracked in https://github.com/pulumi/pulumi/issues/4660


Print stdout in real time ?

I wanted to know if there's any way to display the output in real time while a command is running ?
This is possible when using subprocess,  was wondering if I can do the same here
Thanks

Closed due to inactivity.


Modules V2 - Research - poetry plugins

Investigate what extensions capabilities poetry offers
starting point: https://github.com/python-poetry/poetry/issues/693
timesbox: 1day

Conclusions:

poetry has support for plugins but currently only on master, not yet on any released version
2 plugin types: Plugin gets activated when poetry starts, ApplicationPlugin can register additional commands and options. The latter would be most suitable for our use cases.
fairly little documentation. The basics of how to register a plugin are there, but there is no documented core poetry interface. If we'd want to hook into the core poetry code, we'd need to look at the source. poetry.masonry.builders might be a place of interest.


Use separate routes instead of anchors

first part of https://github.com/woodpecker-ci/woodpecker/issues/3827

I just changed it now to use router-link instead of button to solve all the issues you had

That's smart as we don't have to extract the route matching logic and in addition get open to new tab with proper links


chore: adding pre-commit to run flake8 before pushing to remote

I created this PR to run flake8 before we commit changes in the repo. It frequently happened to me that I made changes in the repo and pushed to the remote, and it doesn't pass our CI pipeline and I have to spend some time to fix the issues and commit again.
To make this work we need to run pip install pre-commit and every time someone commits something flake8 run and checks the files.
I think we can include isort and bandit too

Why not just run tox? That will run flake8, unit tests, bandit, or anything else we enable.

Thanks @thraxil Sounds good, I check if we can use tox and if yes let's replace flake8 with tox


Problem With Database

I have a problem with database

Looks like it couldn't read the database file, are you sure that it's present on the disk and that the webserver user has read permissions to the file?

yes

yes disk isn't full and i have disable hashrate to see but it's the same problem apear after few miniutes , i have clear the database and reinstall a new one but the same problem apear

i have install the 1.7.1 panel right now , i have to wait the miner to connect and we will see if problem persist or not

Stack trace:
#0 /home/........../www/wp-content/master/internalPages/statisticsAjax.php(38): PDO->query('SELECT ms_statu...')
#1 /home/........../www/wp-content/master/page-loader.php(5): include('/home/..........')
#2 {main}
thrown in /home/................./www/wp-content/master/internalPages/statisticsAjax.php on line 38
[06-Jun-2023 21:51:27 Europe/Paris] PHP Fatal error:  Uncaught PDOException: SQLSTATE[HY000]: General error: 11 database disk image is malformed in /home/...................../www/wp-content/master/internalPages/statisticsAjax.php:38
This is error i have in error log

Could be a WordPress problem, I have seen it before because of that. Or there's some general problem with your disk or permission.