Calories sensor value showing incorrectly

          one other thing I will mention... whilst playing with some of the new stuff.

I've noticed that the calories on my last activity...so sensor.strava_0_7 and showing wrong on the integration only...they are showing as 166kcal on the integration, but My watch and strava both show it as 599 .....so no idea what is wrong there,all other stats appear correctly.  Not the end of the world, but thought you might like to know/see
Having had a quick look back, it seems to be a similar story on all the other captured stats for Calories only...but no idea where it is pulling that stat from as all of my runs are 10K so the count would never be that low...and even on my recent 60K ride they show as only 224... assuming it's the conversion from calories to kcals...at a multiplication factor of 4.2... it's still out by 20%

Originally posted by @jouster1974 in https://github.com/craibo/ha_strava/issues/79#issuecomment-1451937541

Apologies this is not solved as I had expected.
I am using the kilojoules stats field and converting that to Calories. I do not get the calories field in the activity summary stats. I also noticed this field is only available for activity types ride.
I will re-open this to look into further

I have made a change to get the Calories for all activitiy type using the Get Activity (getActivityById) method. I will post a PR

Thanks @iainbullock
If we are going to pull each activity individually then it would make more sense to pull all the stats from the activity rather than the activity summary.
I'm working on an enhancement that will change this to do that and keep all the stats for an activity against the type so that the data is not mixed between the different activity types.
I'll try get this temp solution merged and released this week

Tim,
Yes I agree. I was thinking of doing something similar as a solution for
getting Stats for the week for example. I’ll await your future enhancement
and see if it does that
Thanks for your response and developing this in the first place
Iain
On Wed, 19 Apr 2023 at 04:32, Tim @.***> wrote:

Thanks @iainbullock https://github.com/iainbullock
If we are going to pull each activity individually then it would make more
sense to pull all the stats from the activity rather than the activity
summary.
I'm working on an enhancement that will change this to do that and keep
all the stats for an activity against the type so that the data is not
mixed between the different activity types.
I'll try get this temp solution merged and released this week
—
Reply to this email directly, view it on GitHub
https://github.com/craibo/ha_strava/issues/80#issuecomment-1514082870,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AODIAOJTSKFJLRQ3GOZCSKTXB5MEFANCNFSM6AAAAAAVNPG6P4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @iainbullock
I've added this to the current version as I have not had the time to spend on the refactor into seperate entities per sport type.
It's available in version 3.2.27

Thanks Tim for letting me know. I’ll check it out when I next update
Iain
On Sun, 15 Oct 2023 at 12:15, Tim @.***> wrote:

Closed #80 https://github.com/craibo/ha_strava/issues/80 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/craibo/ha_strava/issues/80#event-10657449841, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AODIAOIMC4WRMQBSCR5JGHDX7PAV3ANCNFSM6AAAAAAVNPG6P4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Ensure pty_buf is always freed on exit

Appears to fix an AddressSanitizer-detected memory leak where pty_buf is not always freed when a child process exits.

Never mind, it's possible to cause a use-after-free condition with this.

It should be freed on every read_cb, I've made a fix on main branch, closing.


refactor(ngResource): Use core encode methods in ngResource

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Refactor
What is the current behavior? (You can also link to an open issue here)
Core package and ngResource both define methods for encodeUriQuery and encodeUriSegment.
ngResource's methods are out of date, as changes were made to core encodeUriQuery over a year ago.
What is the new behavior (if this is a feature change)?
Refactor the usage of these methods in ngResource by removing the duplicate methods, and using the core methods instead.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Looks like a single saucelabs job timed out :P

As mentioned by @Narretz, we try to avoid exposing internal helpers/utility functions as public.
On the other hand, it has been bugging me for sometime, that we are using two identical(?) implementation of the same functions. Apart for being WET (isn't that the opposite of DRY), there is the danger of those getting out of sync. E.g. 3625803 has fixed the core version only. Does it mean it should not be included in ngResource version or was it just an oversight ? Who knows...
To expose or not to expose ? :confused:
BTW, if we decided to expose them, I would suggest $$ prefixing the keys to declare them as Angular-private.

Yeah, it was bugging me too. Mainly because I want to propose some changes around some of the encodings, and it seemed wrong to make the identical methods diverge further.
@gkalpak Can you point me to an example in the repo of the $$ private prefix on methods? If it is accepted that we go this route, i'll follow your suggestion and fix those.
Thanks!

Also wondering why this saucelabs test keeps timing out on me :-/

I have restarted the build 4 times and the tests keep failing (on Safaris). I wonder if it's a real issue (something to do with the difference introduced in 3625803.
WRT $$, I mean instead of angular.encodeUriSegment = encodeUriSegment do angular.$$encodeUriSegment = encodeUriSegment. $$-prefixed properties/methods/services are considered "Angular-private" and users are not supposed to touch them (or suffer the consequences when we break them without notice :grin:).

Usually when I see saucelabs errors like this, it's a fluke. Odd that it's consistent. Can I run those selenium tests locally? grunt test:unit passes, but I don't think that runs integration tests. I'll try to see if I can get it running locally.
I'll update the PR with those pseudo private prefixes too.

grunt test:unit passes, but I don't think that runs integration tests

It's the unit tests that fail on Travis. Other tests pass.
The failing browsers are Safari 8.0.8 (Mac OS X 10.10.5) and Safari 9.0.0 (Mac OS X 10.11.0).

Looks like master is actually failing.

Pseudo private methods are now using $$. I'll wait until master is green and rebase this.

And now we're passing :)

@gkalpak Any new thoughts on this? Appreciate the input, thanks!

I do not like the idea of exposing these function... why not just move these functions to a different file and include this file when building angular core and ngResources ?
I know that sharing files between modules is something we currently not do, I just do not like the idea of exposing more helper functions.

I know that sharing files between modules is something we currently not do

We do it with the loader IIRC, but yeah, we are not doing it with a bunch of other stuff.
If we start going down that path, I'm afraid we are going to complicate our build process for little gain.

I just do not like the idea of exposing more helper functions

I'm not thrilled about it either, but nor do I like the current situation that we duplicate code.
On the other hand these won't be "public" helpers, so we won't have to keep them backwards compatible. Do you have other concerns, besides that ?
--
Just to be clear, these helper functions, won't be public. They won't be documented and will be $$-prefixed, so breaking them shouldn't be an issue. If someone relies on undocumented, private $$ features, they have it coming :)
BTW, it won't be the first time we expose undocumented $$ stuff to modules. Off the top of my head, we have a couple of those exposed for ngAnimate (not as properties on window.angular, but as services).
--
So, considering the options:

Have duplicate implementations of the same functions (this is what happens now)
Expose the functions as private, undocumented helpers on window.angular (this is what this PR does)
Move functions to a separate file and include that file to all modules that need it

I don't feel too strongly about either, but slightly favor the first two over the 3rd one.
--
In fact, if we decide to go with the 2nd option (private helpers), we could introduce window.angular.$$privateHelpers and attach private helpers there (as a means to be even more explicit that those are private), but I'm definitely not too happy with that option either.
--
Another approach would be making those injectable (again behind a $$-prefix), which is a little more involved, but doable.

My thoughts are the same as above ^
Seems like adding build complexity is overkill because these are pseudo private methods.

Ok, lets go with the current approach. We can always change it later :)

Awesome :) Excited to get some more patches in related to this issue.

@lgalfaso, with "current approach" did you mean the one currently in effect or the one proposed in the PR ? (I assume the former, right ?)

/ping @lgalfaso

Hello everyone. Hoping for a decision on this, as I have some more patches planned around the encode methods. Thanks :)

@gkalpak by current approach I meant the one in the PR

I was about to merge this, when I realized that this is a potential (minor) breaking change.
Although it shouldn't matter in practice (since both the encoded and the unencode ; would be interpreted identically from the server), it could break some tests (where for example $httpBackend was set up to expecte an encode ;, but the request is made to the URL with unencoded ;).
BC or fix?

If there is a possibility of a BC then let's just put this in 1.6 and document the BC.
We don't want to have to muck about with potential G3 breakages because of this small improvement.

I thought of this as a fix. This is an example of why the duplicate methods were an issue. A PR was merged with a patch for replacing semicolons in the encodeUriQuery method, but the patch only made the change in one of the methods, in this case the core encodeUriQuery method. It probably should have been done in both instances.
My (this) patch keeps the correct core version of the encodeUriQuery method.

@nicholasserra, the problem is that since v1.3.0-beta.18 $resource has been behaving in a specific way. With this fix, this way will change and could result in broken tests. It is something to be avoided with patch release. Updating from 1.5.x to 1.5.{x+1} should be a drop-in replacement.

Understood. 1.6 sounds good.

I forgot to add a breaking change notice in 2456ab6 :confused:


ci: fix gh action to upload coverage report

Description
Related Issue
Fixes #44
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

https://github.com/ahasunos/nse_data/actions/runs/11515765331 is green


Install "timedout" of HDP singleton (static) with 658 retries left.

Hi,
with blueprint "example-hdp3-singlenode", no problem, installation and run of HDP is successful
with blueprint "example-hdp3-singlenode-with-ranger-atlas ", installation failed.
output error :
FAILED - RETRYING: Wait for the cluster to be built (659 retries left).
FAILED - RETRYING: Wait for the cluster to be built (658 retries left).
ok: [master01]
TASK [ambari-blueprint : Fail if the cluster create task is in an error state] *******************************************************************************
fatal: [master01]: FAILED! => {"changed": false, "msg": "Failed to build the mytestcluster cluster. Task Status is TIMEDOUT."}
NO MORE HOSTS LEFT *******************************************************************************************************************************************
to retry, use: --limit @/home/drascek/scripts/ansible/ansible-hortonworks-master/playbooks/install_cluster.retry
PLAY RECAP ***************************************************************************************************************************************************
localhost                  : ok=17   changed=5    unreachable=0    failed=0
master01                   : ok=192  changed=58   unreachable=0    failed=1

Yes, it doesn't appear to be anything terribly wrong from Ambari Server's point of view (like blueprint issues and so on).
It seems to have installed the components but couldn't start them:
2019-01-29 17:20:23,161  INFO [pool-33-thread-1] HostComponentResourceProvider:693 - Handling update to host component, clusterName=mytestcluster, serviceName=AMBARI_METRICS, componentName=METRICS_MONITOR, hostname=master.jp.com, currentState=INIT, newDesiredState=INSTALLED

2019-01-29 18:25:18,101  INFO [ambari-action-scheduler] ActionScheduler:876 - Host: master.jp.com, role: METRICS_MONITOR, actionId: 4-0 timed out and will be rescheduled

2019-01-29 18:40:29,123 ERROR [ambari-action-scheduler] ServiceComponentHostImpl:1033 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=METRICS_MONITOR, hostName=master.jp.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_START, event=EventType: HOST_SVCCOMP_START

Not much we can see here, you'd have to investigate why on the host itself.
Could be anything like memory issues or disk space and so on...
Also, check the status in Ambari GUI like I mentioned, as it might provide additional information.
The Ambari Server log provides general information about Ambari Server state so not very useful if you want to dig deep into a specific issue with a service or a host.

right anything terrible :)
the problem came from slow network access
as soon as I fix that, it works fine

Good to know @jp006 thanks for the update!
But yes, sounds like a different kind of terrible :)


WError blows up when cause is passed down

At least with custom inherited classes this was causing it to blow up (i.e., it couldn't find "cause" on the prototype").

Is this still an issue? This PR is 2.5 years old now.

I don't think this is still an issue.


Unexpected error "invalid shift operator"

Description:
Code below should compile
any a = 1;
boolean lt = 3 < <int>a;

instead you get the compile time error invalid shift operator, but of course this is not a shift operator at all.
Affected Versions:
0.990.1-SNAPSHOT (Dec 20, 2018)
OS, DB, other environment details and versions:
Windows 10
Suggested Labels (optional):
Component/Compiler, Type/Bug

Already fixed with new parser enhancements

@dulvinw Shall we add a test case, if not?

This we can close this. Parser tests includes a few test-cases relates to this:
https://github.com/ballerina-platform/ballerina-lang/blob/aeb25da680ce72ba3f6cb4af05425f81067f5a20/compiler/ballerina-parser/src/test/java/io/ballerinalang/compiler/parser/test/syntax/expressions/BinaryExpressionsTest.java#L41-L46

Closing as per the above comment.


HHH-15833 Sybase doesn't support named parameters

https://hibernate.atlassian.net/browse/HHH-15833

We tried to test hibernate-core version 6.2.0.CR2 with the following dialect, but unfortunately we get the same error


New version: rhysd.actionlint version 1.6.25

Pull request has been created with Komac v1.6.0 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109924&drop=dogfoodAlpha

False positive? How can this be resolved?
Ping @rhysd

Not sure, but the Validation-Defender-Error label means the binary got flagged by Windows Defender. Maybe you can try to submit it as a false positive here: https://www.microsoft.com/en-us/wdsi/filesubmission

Hi @rhysd,
Here's some more information on our validation process: https://learn.microsoft.com/en-us/windows/package-manager/package/repository#validation-process
Here is my manual validation log from the last run: rhysd.actionlint.x<IP_ADDRESS>.log

11:18:20 AM: 2023-06-16 11:18:20.471 [FAIL] Installer failed security check. Url: https://github.com/rhysd/actionlint/releases/download/v1.6.25/actionlint_1.6.25_windows_386.zip Result: 0x80004005

The installer ZIP failed a Defender scan on download and couldn't be installed by WinGet. Please scan the zipping system for viruses and resubmit, along with updating the hash, as removing the virus should change the hash too.

A manual scan from Windows Defender doesn't seem to trigger anything.

@sitiom Thank you for the information and manual scan result.
@stephengillie The binary is built on GitHub-hosted runner of GitHub Actions using GoReleaser action.
Workflow which built the v1.6.25 binary: https://github.com/rhysd/actionlint/actions/runs/5280674972/jobs/9553137042
I never build release binaries on my local. The job automatically runs when new version tag is added so it is hard to rebuild binaries.

Hi @rhysd,
Apparently it was a false positive, as both the Automated and Manual validation pipelines have passed a Defender scan. Sorry for any concern caused.

@wingetbot waivers Add Validation-Executable-Error


gh-pages should be just examples page

We will replace gh-pages or rawgit with jsdelivr CDN for hosting the library (#42).
A use of gh-pages should be just examples and description about L.esri.WebMap after finishing it.

Done.


Fixed feature flag behavior

Description
The feature flag behavior was inverter, now is working as expected.
Fixes # (issue)
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

src/constants/features.js
100.00% <100.00%> (ø)

src/Routes/Devices/Inventory.js
0.00% <0.00%> (ø)

src/Routes/Devices/DeviceTable.js
31.61% <33.33%> (ø)

:loudspeaker: Thoughts on this report? Let us know!.


fixed minor typo in readme

Hello, this PR just fixes a very minor typo in the README.md

Thank you!


Can not download images from Google

$ python3 image_downloader.py "stroller on street" -e Google
Scraping From Google Image Search ...
Keywords:  stroller on street
Number:  100
Face Only:  False
Safe Mode:  False
Query URL:  https://www.google.com/search?tbm=isch&hl=en&q=stroller on street&safe=off
== 0 out of 0 crawled images urls will be used.
Finished.
it works with Bing and Baidu, but the search results with this two engines are not satisfied, how can I fix this? Thanks!

@Qjizhi Not sure why it didn't work.
Have you tried the windows packed exe version? Did it work?

If you can't get the urls，you can uncomment the time.sleep(10) in crawler.py (line 56).

@Qjizhi It could be the situation that your internet connection is relative slow, so that the page may not load completely when code checking the urls.
@zfxxfeng Thanks for pointing that out.


Looks like Directory ID was renamed Tenant ID

@smsaladi : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Add TypeScript support

https://github.blog/changelog/2020-12-16-npm-displays-packages-with-bundled-typescript-declarations/

https://github.com/vuejs/vue-cli/issues/5552

Had another go today, this time trying to move things to Vue 3. Got most of the code updated to TS, also added the entries I think we needed to have the .d.ts included.
Alas, the demo application wouldn't start right, always failing with the same error
[Vue warn]: HMR API usage is out of date.
Please upgrade vue-loader/vite/rollup-plugin-vue or other relevant depdendency that handles Vue SFC compilation.

I think it will have to wait until I start upgrading the app I'm working on at $work to Vue 3. That app uses the code from this library, so I will have more time to learn how to update and package the library. Sorry if anyone is waiting for this to use the library with TypeScript or Vue3 :disappointed:

Finished moving it to Vue 3 and Vite. Hopefully this task will be easier now to implement (later, as I ran out of bandwidth for this project for now).


Icons also being loaded from view string literal values

Hi,
Having a strange issue where the string literal value of a UITextField is being interpreted as icon codes and rendered as the icons themselves.
Example Code:
    func updateSpecificLocationField() {
        let carIcon = String.fontAwesomeIcon(name: .car)
        let placeholder = "Getting Location..."
        specificLocTxt.font = UIFont.fontAwesome(ofSize: 15, style: .solid)
        specificLocTxt.text = "\(carIcon) \(placeholder)"
    }

And the car icon works fine, but for the word "Location", I am literally getting a cat icon as well due to the "cat" lol:

Edit: Apologies, forgot to add system specifics:
Xcode: 10.2.1
Swift 5
github "thii/FontAwesome.swift" "1.7.0" (via Carthage)
Also seeing the same issue w/ UILabel

Also seeing the same issue w/ UILabel

I am seeing this same behavior as well. It seems that interpolation is having some unintended side effect.

Could you attach a reproducible example project?

@thii Yes, of course:
TestFA.zip

Was this ever resolved? I provided the examples as requested.

Bump

This is just my 5 cents, not thii's opinion: But isn't this a side-effect because you are displaying regular text using fontAwesome, it is supposed to display icons, not regular text.


Ignore generic types when handling paths

Professor,
This is a simple PR to ignore expressions of generic types when handling paths.
Please take a look. Thank you.

Thank you for pointing out. I have updated the codes.


fix(deps): update terraform ibm to latest for the da solution

This PR contains the following updates:

Package
Type
Update
Change

ibm (source)
required_provider
minor
1.64.2 -> 1.65.0

Release Notes

IBM-Cloud/terraform-provider-ibm (ibm)
v1.65.0
Compare Source
Features

Support for VMware as a Service API

Datasources

ibm_vmaas_vdc

Resources

ibm_vmaas_vdc

Support for PowerVS

Datasources

ibm_pi_networks

Enhancements

align Projects terraform provider to latest API spec (5252)
Add power edge details to workspace data source (5205)
feat(tekton): add locked properties (5274)
Added support for IBM Cloud Logs atracker targets (5270)
Deprecate vtl attributes in data source/resource (5265)
Update PI Image import/export and capture cos region doc (5273)
CBR typeset change for cbr rule/zone and adding CBR retries (5246)
Fix data assignment APIs (5306)
feat: wrap provider to create new error structure (5278)
ODF workerpool support (5283)
fix(Cloud Databases):Incorporate new client-error-toolchain in datasources (5320)
Added IAM fields in enterprise create child account response (5313)
ODF 4.15 Templates for add-on and satellite (5316)
Added support for snapshot service tags (5326)

BugFixes

Fix deleting instances with replicant attribute set (5176)
fix access group resource: recreate ag when it is deleted outside terraform (5304)
fix(docs): fixed documents for network acl and rules (5302)
add fix for timeouts for observe logging resource (5300)
Produce error when selecting invalid region in toolchain service (5297)
Fix instance policy drift (5308)
fix access group members resource: recreate ag members when it is deleted outside terraform (5317)
updated host_flavor id docs (5323)
fix(docs): Fix bm initialization doc titile (5330)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

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

GitHub release
v1.1.5

Your semantic-release bot :package::rocket:


Progress spinner is now shown during the whole logout process

Updated "logout" command to make sure that the app doesn't always waits for 10 seconds before exiting

The goal with the 10 second timeout is that sometimes it takes a very long time to delete a token. Rather than make the user wait forever to log out before actually being logged in, the current code means that the users don't wait more than 10 seconds before the process goes on. I would not remove this logic.


tests: threads_ext: set NEWLIB_LIBC_MIN_REQUIRED_HEAP_SIZE

One of the tests is failing since it was split out in 1a633609a0d triggering an assertion:
ASSERTION FAIL [((((size_t)(16)) << 10) - (((uintptr_t) (&_end)) - 0x20000000)) >= 8192] @
WEST_TOPDIR/zephyr/lib/libc/newlib/libc-hooks.c:139
Setting a smaller CONFIG_NEWLIB_LIBC_MIN_REQUIRED_HEAP_SIZE seems to make it pass.
Tested with:
$ west build -t run -p -b qemu_cortex_m0/nrf51822 -T tests/posix/threads_ext/portability.posix.threads_ext.newlib

thanks @cfriedt, I changed this to your diff and co-signed with your name since it's your fix at this point :-)


[WIP] Flutter Plugin Tool supports multi-platform plugin config

WIP
Description
This addresses https://github.com/flutter/flutter/issues/10288 partially.
I'm currently re-using a Plugin pojo. There will be some follow up work
here:

[DONE] Migrate the current pojo to have a Map<String, PlatformPlugin> and have
impls for: AndroidPlatformPlugin, IOSPlatformPlugin,
MacOSPlatformPlugin. They can each contain their own fields.

Add more meaningful error messages to the tool when we encounter any
invalid configurations. Currently there is not much error handling done.

[DONE] Address https://github.com/flutter/flutter/issues/38628

Related Issues

https://github.com/flutter/flutter/issues/10288
https://github.com/flutter/flutter/issues/38628

Tests
I added the following tests: plugin_parsing_test.dart.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

@amirh i'm staging this PR to get any initial feedback you had about the vision.
I do not intend to land it in its current state. I will have follow-up work to address the things listed in the PR description.

I'm also changing the current parameters and namespacing them as they relate to the new format:

androidPackage becomes android -> package
iosPrefix becomes ios -> classPrefix

@stuartmorgan , I have removed all references to macOS in legacy format, i did not realize that none of them were published. I also included macOS plugin in the test that I wrote.
@jonahwilliams , I have added the documentation about the required fields for the plugins. I have also filed https://github.com/flutter/flutter/issues/38853 to address support for unknown/unsupported plugins. I will add support for them in a follow-up PR.
I have also resolved the other comments you have given me. PTAL and thanks!


Not Saving Changes

I feel like I'm doing this wrong, but for some reason I can't seem to SaveChanges properly.
using (var dbContextScope = _dbContextScopeFactory.Create())
{
    var context = dbContextScope.DbContexts.Get<ApplicationContext>();

    var file = context.Set<Models.File>().Find(id);

    file.Name = "This should be updated, but it's not :)";

    var result = dbContextScope.SaveChanges();
}

The only way I'm able to actually get the result to be > 0 is to create one of these _dbContextScopeFactory.CreateWithTransaction(IsolationLevel.Serializable)
My creates work perfectly, but for some reason the updates don't seem to update :confused:
Am I going about this the wrong way?

Hi, @mglodack
Actually assigning field and calling SaveChanges() shouldn't change anything.
You can write somethink like this:
    context.Entry(file).State = EntityState.Modified;

Be careful because in other cases entity can be detached from context and you should call:
   context.Set<Models.File>.Attach(file);

So, I use the general function with Generic Repository pattern aka:
    public void Update(TEntity entity)
    {
        Entities.Attach(entity); // Entities => DbContext.Set<TEntity>
        DbContext.Entry(entity).State = EntityState.Modified;
    }

Also take a look at this answer at SO
http://stackoverflow.com/questions/30987806/dbset-attachentity-vs-dbcontext-entryentity-state-entitystate-modified

@jonny-novikov Awesome!
Thank you for the explanation and SO reference. :smile:

@jonny-novikov
I'm still not seeing any changes being saved when I call the DbContextScope SaveChanges method.
However, if I call the actual context SaveChanges method then the records get updated.
I was under the impression that I no longer need to call DbContext SaveChanges.
Is this still true or am I misunderstanding the library?
using (var dbContextScope = _dbContextScopeFactory.Create())
{
   // Make changes
  dbContextScope.SaveChanges(); // Should call all the DbContext instances SaveChanges methods
}

I've got the same issue in case of updating multiple records. I've got more than one row to update, I loop through, attach each entity and then call savechanges on dbcontextscope at the end. as soon as it tries to add another row, attaching entity throws primary key error. But this works fine if I call the dbcontext.savechanges()


feat: add events create command

Adds a new events create command to create iCal events that can be easily imported to any calendar.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


password protecting the conference room

I am trying to password protect the multi party conference room joining , however session ceases to exist if url is redirected or any additional parameters such as memeber name or meeting id is added to the existsing url of created conference .

HI , Ca I use this code  for RTCMulticonnection v3?


deflake tests

Motivation
Closes #3331
Changes
Changes that fixes flaky tests in p2p module
Test Plan
unit tests
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors try

bors try


Upgrade bsp4s to use jsonrpc4s and jsoniter-scala directly

This is a continuation of the work that @jvican did in #125.

Removes dependency on circe, we now only depend on jsoniter-scala itself
for JSON purposes, which is a library with no third-party dependencies.

I rebased on the current main branch and brought this up to date with the aim
to unlock #153.
Note that that also includes the work in #174, so you may want to merge that in first.

Alrighty, after updating to the newly released jsonrpc4s we are all 🟢.

@jastice Can you take a look at this whenever you have some time?


Unexpected keys errors obfuscating schema errors in nested hashes

Describe the bug
In nested structures errors generated by enabling config.validate_keys = true obfuscate schema errors. For not nested hashes all kinds of errors are visible.
To Reproduce
NestedSchema = Dry::Schema.JSON do
  config.validate_keys = true

  required(:top_field).filled(:hash) do
    required(:existing_field).filled(:integer)
  end
end

NestedSchema.call({top_field: {existing_field: 'String', unexpected_field: 1}}).errors.to_h
# {:top_field=>{:unexpected_field=>["is not allowed"]}}

Expected behavior
I would expect to see this list of errors instead: {:top_field=>{:unexpected_field=>["is not allowed"], :existing_field=>["must be an integer"]}}
With simple structure it works as expected:
SimpleSchema = Dry::Schema.JSON do
  config.validate_keys = true

  required(:existing_field).filled(:integer)
end

SimpleSchema.call({existing_field: 'String', unexpected_field: 1}).errors.to_h
# {:unexpected_field=>["is not allowed"], :existing_field=>["must be an integer"]}

Your environment

Affects my production application: YES
Ruby version: 2.6.5
OS: macOS 10.14.6

Seems to be fixed by https://github.com/dry-rb/dry-schema/pull/284


When clicking on a specific trip (from current trips list in dashboard), it opens the trip dashboard / overview with all its details.

Implemented the navigation with commit: 70857dc


Creating a Certificate Chain

Hi I am trying to setup a full certificate chain for our Service Provider.
Our client (IdP) needs the full chain to establish thrust. I see in their metadata multiple certificates, is it possible for me to do the same?
Or is there an other way like only putting the public certificates in the metadata and sending the CA certificates by mail? (to be honest I am new to the subject and don't really know what I'm doing :)
thanx

Service Provider only publish 1 certificate , not the CA, the CA is used to validate the certificate itself, but
no many implementations do that, only check that the signature match the certificate, no if the certificate is valid itself.

Thankyou


Delete _config.yml

看起来它好像没用了？

Pull Request Test Coverage Report for Build 104

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 103:
0.0%

Covered Lines:
244

Relevant Lines:
244

💛  - Coveralls

Pull Request Test Coverage Report for Build 104

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 103:
0.0%

Covered Lines:
244

Relevant Lines:
244

💛  - Coveralls

@run-ze 谢谢关注。这个文件有用的。 项目主页有用到：https://xujiajun.cn/gorouter/  我没放出来而已


rootBundle is giving exxeption

The following code is giving me exception
return await rootBundle.loadString('assets/images/null.png');
the exception is:
Exception: FormatException: Unexpected extension byte (at offset 0)

@aifrosals
Please check this document on how to use rootBundle and see if you are properly added the assets in pubspec.yaml.
If problem persists, provide flutter doctor -v and minimal reproducible code sample that shows the issue.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

I'm not the owner, but I have the same symptoms.
code sample
Future<String> loadAsset() async {
  return await rootBundle.loadString('assets/Image/Icon.png');
}

assets:
    - assets/Image/Icon.png

[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.19042.746], locale ja-JP)
    • Flutter version 1.22.5 at C:\flutter
    • Framework revision<PHONE_NUMBER> (5 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\ntete\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[!] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.52.1)
    • VS Code at C:\Users\ntete\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.18.1

[√] Connected device (1 available)
    • SCV36 (mobile) • 988ad0374259505444 • android-arm64 • Android 8.0.0 (API 26)

! Doctor found issues in 1 category.

Image.assets('assets/Image/Icon.png') ← This is displayed without any problem, so I don't think the path is wrong. What do you think

I'm not the owner, but I have the same symptoms.
code sample
Future<String> loadAsset() async {
  return await rootBundle.loadString('assets/Image/Icon.png');
}

assets:
    - assets/Image/Icon.png

[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.19042.746], locale ja-JP)
    • Flutter version 1.22.5 at C:\flutter
    • Framework revision<PHONE_NUMBER> (5 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\ntete\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[!] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.52.1)
    • VS Code at C:\Users\ntete\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.18.1

[√] Connected device (1 available)
    • SCV36 (mobile) • 988ad0374259505444 • android-arm64 • Android 8.0.0 (API 26)

! Doctor found issues in 1 category.

Image.assets('assets/Image/Icon.png') ← This is displayed without any problem, so I don't think the path is wrong. What do you think


Fixed errors/warnings listed on lgtm.com

Clubhouse Story
List of errors/warnings is at https://lgtm.com/projects/g/AugurProject/augur/alerts/?mode=list.
Submitter checklist

[ ] Test covering functionality added/fixed in
Check the linked story includes the following:

[ ] Steps to reproduce
[ ] Screenshot (If applicable)

Reviewer Checklist

[ ] Test/lint pass

Can you investigate why Travis doesn't like these changes?

Yep, was just looking at that. Apparently react-datetime is required after all.

Ok, when it passes the check we can merge it up.

Hey There,
Glad to see that you've addressed so many alerts in one fell swoop! Just so that you're aware, if you like you can enable Pull Request integration from this page: https://lgtm.com/projects/g/AugurProject/augur/ci/
What it will do is analyse each pull request, and let you know the changes to the alerts that would occur if it was merged. If there are no alert changes, then no comment! Check out the details here: https://lgtm.com/help/lgtm/using-lgtm-analysis-continuous-integration
Let me know if you have any questions!

Thanks for the tip, @samlanning! I'll go ahead and enable it so we can try it out.


Add options param to update() to extend options

This little addition makes it possible to extend the options with the update() function.
This is useful if you need to change the labelInterpolationFnc together with changed data.
Tested in my current project without issues.

Hey man thanks for the PR thats great! You should call removeMediaQueryListeners on the old options provider before you instanciate a new one.

@gionkunz added with 8b500a2

Thanks for this Christian!


The name of the exercise should appear on top when running the routine

Each exercise now has exercise name in the exercise screen


Fix appsettings_SQLite.json syntax

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


Error: ENOTDIR: not a directory with node-fetch

I am encountering an error related to node-fetch when running my Electron application. The error message indicates a directory issue, specifically ENOTDIR: not a directory.
Steps to Reproduce:

Install the @aracna/core:1.1.89 package in an Electron application.
Package the application using electron-builder.
Attempt to run the application.
The error is triggered.

Environment:
node-fetch Version: 3.3.2
Node.js Version: 20.9.0
Electron Version: 24.5.1
Operating System: Windows 10, macOS 14
Package Manager: 10.1.0
Attempted Solutions:

Cleared npm cache and reinstalled dependencies.
Unpacked the asar archive to verify the node-fetch module exists and is structured correctly.
Downgraded/Upgraded node-fetch to different versions to test compatibility.

@manesid I'm facing same issue. How did you resolve it?


A benchmark suite for the getFirstAvailableBlock RPC call

Summary of Changes
$ cargo run -- --identity ~/.config/solana/id.json --rpc-bench first-available-block --iterations 0 --url l --mint 7z5aMSb5zfJThETMRgFFd3XNKKVcZGNtWQDS3qfgbQ2t --space 165
   Compiling solana-accounts-cluster-bench v2.2.0 (/home/sol/src/agave/accounts-cluster-bench)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 17.47s
     Running `/home/sol/src/agave/target/debug/solana-accounts-cluster-bench --identity /home/sol/.config/solana/id.json --rpc-bench first-available-block --iterations 0 --url l --mint 7z5aMSb5zfJThETMRgFFd3XNKKVcZGNtWQDS3qfgbQ2t --space 165`
[2024-12-06T18:51:43.103362897Z INFO  solana_accounts_cluster_bench] Targeting http://localhost:8899
[2024-12-06T18:51:43.106797696Z INFO  solana_accounts_cluster_bench] Starting balance(s): [716661743680]
[2024-12-06T18:51:43.107795233Z INFO  solana_accounts_cluster_bench] creating 4 new
[2024-12-06T18:51:43.111919292Z INFO  solana_accounts_cluster_bench] txs: 4
[2024-12-06T18:51:43.155339263Z INFO  solana_accounts_cluster_bench] ids: 4
[2024-12-06T18:51:44.162376566Z INFO  solana_accounts_cluster_bench] creating 4 new
[2024-12-06T18:51:44.163164705Z INFO  solana_accounts_cluster_bench] txs: 4
[2024-12-06T18:51:44.208056503Z INFO  solana_accounts_cluster_bench] ids: 4
[2024-12-06T18:51:44.709153917Z INFO  solana_accounts_cluster_bench] creating 4 new
[2024-12-06T18:51:44.709944660Z INFO  solana_accounts_cluster_bench] txs: 4
[2024-12-06T18:51:44.755458802Z INFO  solana_accounts_cluster_bench] ids: 4
[2024-12-06T18:51:45.270454827Z INFO  solana_accounts_cluster_bench] creating 3 new
[2024-12-06T18:51:45.271077190Z INFO  solana_accounts_cluster_bench] txs: 3
[2024-12-06T18:51:45.304960722Z INFO  solana_accounts_cluster_bench] ids: 3
[2024-12-06T18:51:45.809524866Z INFO  solana_accounts_cluster_bench] creating 4 new
[2024-12-06T18:51:45.810313886Z INFO  solana_accounts_cluster_bench] txs: 4
[2024-12-06T18:51:45.856990698Z INFO  solana_accounts_cluster_bench] ids: 4
[2024-12-06T18:51:46.359918562Z INFO  solana_accounts_cluster_bench] creating 4 new
[2024-12-06T18:51:46.360694647Z INFO  solana_accounts_cluster_bench] txs: 4
[2024-12-06T18:51:46.407656942Z INFO  solana_accounts_cluster_bench] ids: 4
[2024-12-06T18:51:46.407674325Z INFO  solana_accounts_cluster_bench] total_accounts_created: 23 total_accounts_closed: 0 tx_sent_count: 23 loop_count: 7 balance(s): [716614610240]
[2024-12-06T18:51:46.918582539Z INFO  solana_accounts_cluster_bench] creating 3 new
[2024-12-06T18:51:46.919218078Z INFO  solana_accounts_cluster_bench] txs: 3
[2024-12-06T18:51:46.953224733Z INFO  solana_accounts_cluster_bench] ids: 3
[2024-12-06T18:51:47.107893084Z INFO  solana_accounts_cluster_bench] t(0) rpc(FirstAvailableBlock) iters: 628 success: 629 errors: 0
[2024-12-06T18:51:47.107919575Z INFO  solana_accounts_cluster_bench]  t(0) rpc(FirstAvailableBlock average success_time: 6359 us

Related: #3242.

Requires re-review because we don't use stacked PR workflows here so I had to resolve a conflict, and resolving the conflict dismisses all reviews.

Rebased, ergo review required.


Ensure tokens start with --componentName or --uitkComponentName

Currently adds linting rule to Lab package - do we want this?
Part of CSS clean up #377:

Ensure component tokens start with their full name, e.g. —doc-grid -> —docGrid (lint rule added**)
Moves subcomponents to next part of token, e.g. --uitkCheckboxIcon- -> --uitkCheckbox-icon-, --uitkAccordionSummary -> --uitkAccordion-summary which means all tokens are evidently scoped to a specific component in our collection
Tokens renamed if necessary, e.g. --formHelperText- -> --formField-helperText-
Layout component items are treated as standalone components (since Layout items can be placed within different Layout components other than their parent, this makes sense. It is also important to ensure differentiation between e.g. the Grid component --grid, the Grid Layout component --gridLayout, and Grid Layout items --gridItem)
MenuTrigger moved from internal component to MenuButtonTrigger at root
Extra: Remove public token from focused characteristic inset value (there should not be an API on characteristics)

** Rule generates allowed component names based on folder structure: folder must be the component name in kebab case (e.g. button, radio-button, form-field, tokenized-input) and will only be accepted as an allowed name if there is an internal component matching this (e.g. Button, RadioButton, FormField, TokenizedInput) - subcomponents (e.g. RadioButtonGroup, FormFieldHelperText) are not added to the accepted list
Catch:

this means components that didn't have a base CSS file (i.e., currently only MenuButton) have had to have an empty CSS file added;
LinearProgress and CircularProgress have been moved into sub-folders (now follows same structure as Layout components);
there is one exception currently which is --text falling under /typography folder - should we change these to --typography, change the folder name to /text, or leave it as an exception?

Great to see components name being automated from folder structure.
Small thing: is there a reason packages/lab/src/menu-button/MenuButton.css is added but empty and also not imported?

Great to see components name being automated from folder structure.
Small thing: is there a reason packages/lab/src/menu-button/MenuButton.css is added but empty and also not imported?

thanks! yes, see the catch in the pr description: (1. this means components that didn't have a base CSS file (i.e., currently only MenuButton) have had to have an empty CSS file added;)


Fix thor dependency

Rails now requires Thor 1.0 or higher so we need to update the
dependency on thor in licensed.
This will allow 0.19 or anything higher.

@eileencodes :wave: release 2.9.1 is out with this change https://github.com/github/licensed/releases/tag/2.9.1


uWebSockets as HTTP interface

According to https://github.com/uWebSockets/uWebSockets/issues/397#issuecomment-277237968, uws.http is considerably faster than http.

uWebSockets/blob/master/nodejs/http_sillybenchmark.js
uWebSockets/blob/master/nodejs/http.js
Performance is still very good as long as writeHead is not called in a hot path (this function is very slow). If you only res.end('some data here'); you get 230k requests per second.
from https://github.com/uWebSockets/uWebSockets/issues/397#issuecomment-275276648

Currently and only in v.0.13.0a6 (since a1). Near drop-in replacement for Next's use case? May need to be tested and benchmarked in a production environment.

Could you tell me where exactly you suggest to use this?

Anyway, since do support custom servers I hope this is doable in the userspace.

master/server/index.js#L4
from
import http, { STATUS_CODES } from 'http'

to
import http, { STATUS_CODES } from 'uws.http'

It could indeed be a user choice, but if the benchmarks get confirmed, the transition is seamless, and it doesn't cause significant maintenance overhead, why not?

v.0.13.0 was released the other day. @arunoda Could you reopen the issue to allow for a thorough evaluation?


[WIP] Lockfile checksum

Thanks so much for the contribution!
To make reviewing this PR a bit easier, please fill out answers to the following questions.
What was the end-user problem that led to this PR?
The main aim is to reduce Gemfile resolve time if checksum remains same.
What was your diagnosis of the problem?
Add a section CHECKSUMS to lockfile that will store the checksum and will be used to match for future.
I continued the work done by @segiddins.
What is your fix for the problem, implemented in this PR?
The main approach was to store a checksum of current gemfile under CHECKSUMS sections in Gemfile.lock
In continuation of #5584.

@segiddins I am not able to test static gemfile option, do not know how to call it from Gemfile. Can you please help me here? And how shall I proceed with this PR?

_static_gemfile! in the DSL

Hello! I really like this feature.
I went thru code and I have 2 initial questions. Sorry if they were answered already, but I can't find any previous discussion related to those questions.

Why checksum can't be stored in file next to lock files?
I see md5 is used to digest lock. Can't something different (ex. SHA1) be used since md5 is blocked on FIPS enabled systems? There were some issues with md5 and FIPS before. I know there's md5_available? helper used to avoid problems. But do we really need to introduce new features with md5 and disable them for FIPS enabled systems?

MD5 is quicker

This test block is failing
context "with a current version" do
  let(:base_version) { Gem::Version.create(Bundler::VERSION) }

  it "returns an empty array" do
    expect(subject).to eq([])
  end
end

We have added sections in 2.0 version. And when we are testing with BUNDLER_SPEC_SUB_VERSION=1.98 this obviously fails. How do I counter this?

The lockfile parser hash of known sections would need an update

I didn't quite understand how to proceed. Should we not change BUNDLER_SPEC_SUB_VERSION for test?


Automatic eta expansion of block arguments

Currently, block arguments always have to be fully applied:
map([1, 2, 3]) { a => f(a) }

Instead, we could also support
map([1, 2, 3]) { f }

which could desugar to the above version.
Similarly, we could allow partial application:
f: (Int)(Int) -> T
map([1, 2, 3]) { f(1) }

desugaring to
map([1, 2, 3]) { x=> f(1)(x) }

The desugaring is type directed and should always lead to fully applied blocks. This is necessary to eventually adapt capabilities.
There are multiple possible designs to where the desugaring can take place. Since it is type directed, we further need to investigate interaction with overload resolution.

We do not automatically eta-expand, but if the provided function has the correct (sub-)type, this is now possible.


Zapping a register variable by its variable name doesn't free the actual register

Compare examples.
No zapping

Zapping the registers

Zapping the registers by their variable name

Rather than guessing which register to zap or having to calculate which register the register keyword will preserve for the variable, it would be nice to allow us to free a busy register by the variable name that's using it.

While it is possible to know exactly where the register will be zapped in the program you give, its not always possible to know where with control flow that cant be 100% known at compile time. This is why register in C is "best effort" not an actual guarantee like it is in HLZASM. This is mathematically impossible to totally implement.

Current implementation zaps registers immediately after the compiler reads "ZAP (REGISTER)", so adding a compiler error/warning for trying to reference a register variable any line after the "ZAP (VARIABLE)" is made should be acceptable for making users not attempt to use zap in branches


Using  Yaml variable in markdown part of the file

Is it possible to use a Yaml-variable in the markdown part of the index.md file, for example.
Hence can I use a config.xyz variable from the  file ~/config/config.yml ?
Would make life more easy
Thanks for any response
Henk

Yes, you can use %meta.*% placeholders, e.g.
---
greet: World!
---

Hello %meta.greet%

Thank you, this makes live so more  easy.
Regards Henk.


Support pnpify --sdk

Pnpify documentation shows that prettier is supported https://yarnpkg.com/advanced/editor-sdks#vim--cocnvim but we need to add a custom prettierPath to the coc-settings.json so that the pnpified prettier can be used. Can coc-prettier add support for this? The vscode extension already supports it.
https://github.com/yarnpkg/berry/blob/8e77d191926e841faaf7093de24db0409e6094a7/packages/yarnpkg-pnpify/sources/generateSdk.ts#L172

Related to https://github.com/neoclide/coc-tsserver/issues/166; was about to post the same :+1:

Has this been solved or is there a workaround?

I think setting   "prettier.prettierPath": ".yarn/sdks/prettier/index.js", in .vim/coc-settings.json works

The above did not work for me, as the SDK was attempting to import prettier from the zip file which threw an error. Try:
  "prettier.prettierPath": "yarn exec prettier"


FINERACT-1189: fineract client as a separate module

Description
Some pointers for your reviews:

fineract-client uses the official OpenAPI Gradle plugin to generate sources; I've removed the plugin that was previously used from fineract-provider; the CLI based code generation is also removed (including spawning a separate Gradle build); just to say fineract-client is a true module now
the "allprojects" section contains now more plugin configurations that can be applied to all modules; I've moved Spring dependency management, Rat and License check there, because like this we only have to configure them once
there is a new section (after "allprojects") that contain every plugin configuration common to Java modules. Source sets, compiler arguments, JDK compatibility as well as Spotless Java related configurations are done in one place here. We can move more stuff here, e. g. Errorprone, Jacoco, Git properties, Checkstyle, Modernizer, Spotbugs, project report; these plugins are not fineract-provider specific, but can be applied to any Java module (fineract-client included); I just wanted to limit this first set of changes (already 25+ files changed)
please look at line 26 of the build.gradle file in the root folder to see how the selection of Java projects works; this allows us to use one common configuration for Java projects (see line 333)
fineract-client/src/main/templates contains OpenAPI/Swagger code generator template files that fix a couple of style errors or just add licenses; just to have the bare minimum there; these sources are still excluded from Spotless and other checks, because... well, generated code.
in the current upstream develop branch the Swagger generated code is built on Travis with "mvn test"; I would be surprised if we have any tests there... I remember there's a flag to generate test stubs, but how useful are these skeleton tests then? Have to check this again
I still have to decide how to handle the Swagger file ("fineract.yaml"). In my first prototype I've copied it from fineract-provider to fineract-client, because I couldn't convince Gradle to build the modules in a certain order (fineract-provider -> fineract-client); it's not really a good practice to do this anyway in Gradle, but still there are a few mechanics that should help (like declaring a project dependency or something along those lines). If I manage to get this working then we don't need to Git manage fineract.yaml under fineract-client (we can just pick it up in fineract-provider/build). Just FYI

Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[x] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[x] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

@ptuomola @vorburger So... how do you guys want to decide on the Mustache templates in fineract-client? Without? I think that's the last open question here before we can merge...

@ptuomola @vorburger So... how do you guys want to decide on the Mustache templates in fineract-client? Without? I think that's the last open question here before we can merge...

I agree with @vorburger - if the only change to the templates is the license, let's not check them in but include them as dependency instead.

@ptuomola @vorburger Swagger templates are gone.

This is great!

I'm re-reviewing it now.. give me a moment to pull it down and actually try it out as well. This is giving me some ideas.. watch for new JIRA! :sweat_smile:
@vidakovic did you notice it has a conflict again, in fineract-provider/build.gradle - will you resolve? #1408 may have (not checked) caused the new conflict.. as it looks like we are almost there with this one now, I'll hold merging other PRs until we merged this :smiling_imp: sorry about that.

@vorburger Let the new ideas come... looking forward :smile:
Checking now for the conflict... brb.

@vorburger Let the new ideas come... looking forward smile

FINERACT-1209 is the big one, that could be so cool; FINERACT-1210 a more medium/longer later idea; FINERACT-1100 minor.


Update iot-hub-protocol-gateway.md

Hi @rohanag12, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@rohanag12 Hi rohanag12, thanks for that correction.


chore: Upgrade to latest Babel, Jest, enzyme

Issue Number
No issue. Just dependency maintenance.
Overview of PR
Upgrades Jest and enzyme to latest, and as required by Jest 24, also upgrades to Babel 7.

Jest 24 required switching to a setupFilesAfterEnv array from the setupTestFrameworkScriptFile string previously in use.
The Babel upgrade required two changes:

switching to several namespaced packages (e.g. @babel/preset-env)
Explicitly including regenerator-runtime in jest-setup.js

Other Considerations

I did NOT upgrade react-testing-library, despite upgrading everything else related to testing. Upgrade it to latest requires changes to tests and so I think it warrants its own pull request.

@trevdor thank you for this. I will merge it and make sure everything is working and compiling


Unexpected results (comparison between black-box and whitebox attacks)

I encountered some unexpected results, and I believe there might be an issue related to the attack comparisons. Specifically, I tried comparing the results of a blackbox (loss-based) attack with a whitebox (gradnorm-based) attack. I was expecting the whitebox attack to outperform the blackbox attack in terms of precision, but I observed the following results after running the code:
•	Loss-based (blackbox) attack results:
•	ROC AUC: 0.8334
•	PR AUC: 0.8308
•	TPR at low FPR: {0.001: 0.149, 0.01: 0.242}
•	GradNorm-based (whitebox) attack results:
•	ROC AUC: 0.3237
•	PR AUC: 0.3954
•	TPR at low FPR: {0.001: 0.007, 0.01: 0.022}

Given that whitebox attacks typically provide better precision, these results seem counterintuitive.
Here’s the configuration file I used for the experiment:
{
"experiment_name": "neo125_github_experiment_whitebox",
"base_model": "EleutherAI/gpt-neo-125m",
"dataset_member": "the_pile",
"dataset_nonmember": "the_pile",
"min_words": 100,
"max_words": 200,
"max_tokens": 512,
"max_data": 100000,
"output_name": "unified_mia",
"specific_source": "Github_ngram_13_<0.8_truncated",
"n_samples": 1000,
"blackbox_attacks": ["gradnorm", "loss"],
"neighborhood_config": {
"model": "bert",
"n_perturbation_list": [
25
],
"pct_words_masked": 0.3,
"span_length": 2,
"dump_cache": false,
"load_from_cache": true,
"neighbor_strategy": "random"
},
"env_config": {
"results": "results_new_white",
"device": "cuda:0",
"device_aux": "cuda:0"
},
"dump_cache": false,
"load_from_hf": true
}
Any insights into why the whitebox attack (GradNorm) underperforms so significantly compared to the blackbox (loss-based) attack would be appreciated.

I was expecting the whitebox attack to outperform the blackbox attack in terms of precision

While it may seem intuitive, results from the literature all point to black-box attacks usually being better than those that only rely on parameters. See this paper for an overview. One exception  is the LiRA attack adapted to use gradient norms (and recent work suggesting that parameter access is useful in the LOO setting), but the gain is negligible and arises mostly from reference models more than access to parameters.


Proposal: Give api to disable shadow on flyouts in 19h1+

Proposal: Give api to disable shadow on flyouts in 19h1+
Summary
I want a way to disable the shadow effects on flyouts in 19h1+
Rationale
We are using commandbarflyout, and we have custom types that expand off that of type Panel that doesn't have shadow. So want an option to disable the CommandBarflyout one as stop gap.

Functional Requirements

Important Notes

Open Questions

Are you planning to add shadows to your custom types eventually?
In the meantime does setting IsDefaultShadowEnabled=false on the FlyoutPresenter do what you want?
e.g.:
<Flyout>
    <Flyout.FlyoutPresenterStyle>
        <Style TargetType="FlyoutPresenter">
            <Setter Property="IsDefaultShadowEnabled" Value="False" />
        </Style>
    </Flyout.FlyoutPresenterStyle>
</Flyout>

@ahhlun , we recommend turning on the shadow for the sub-menu using the code Jesse provided above.

@jesbis can you provide an example using c++ or c++/winrt code behind and not XAML?
The uwp doc site has a lot of setting styles through XAML but I need to do this in code behind.
I have trouble figuring out how to construct "TargetType" and how to set the Setter for the style.

To set TargetType from code in C++/WinRT you can use the xaml_typename helper.
The style setter would need to take a boxed boolean, which you can make through winrt::box_value(false).

@ahhlun , were you able to get this to work? It is preferred that we show shadow on your example case so hope you were able to handle it.

we plan to do this soon

@ahhlun, great! In that case, may I close this issue?

@ahhlun, you previously indicated you are adding shadow in this UI and I do not believe there is additional API needed here, so I am closing this issue.


documentCollection.save not returning full document

The documentation for save() implies that the callback gets called with the full document (doc.some === 'data' in the documentation's example). However, I only get back the new meta attributes (when using promises, if that makes any difference).
{
  error: false,
  _id: 'whatever/1645465998905',
  _rev: '1645465998905',
  _key: '1645465998905'
}

I think I'm actually OK with this behaviour. Image saving a large document, it would be wasteful to send all that data back and forth. So perhaps this is a just a documentation bug.
What might be nice though, is ArangoDB only replying with the new meta info, and the adapter merging that result with the document I saved, and then calling my callback with that merged object.

Merging the input and server response is probably out of scope considering where the driver is heading at the moment.


feat: Restore VK tree

Restores verification in the VK tree. Adds support for Honk and ClientIVC verification keys in the circuits.
We still have an exception for Tube though, since it's still not a single VK.

🔥

Seconded :D


To Objective-C

Please tell how it would be in Objective-C?
 ctr.pageSelected = {
        (page: Int) in self.slideshow.setScrollViewPage(page, animated: false)
    }

Try this.
[ctr setPageSelected:^(NSInteger page) {
    [self.slideshow setScrollViewPage:page animated:NO];
}];


WIP - link to TOS & privacy policy, serve css & fonts directly

Adds static terms-of-service.html and privacy-policy.html with links from the main footer.

[x] The privacy policy still has a placeholder for the date
[x] The privacy policy text isn't centered correctly; not sure why.
[x] There's still nothing for the copyright policy link - need to remove the link or put something there
[x] The links in the login / signup modal aren't correct yet

@yusefnapora copyright policy is 404?


nest-datagraph_nestdatagraph_1 continual restarts

I setup the ini, built the images, but when i run the app, it fails to start properly and throws "nest-datagraph_nestdatagraph_1 exited with code 2" repeatedly.

I try and "docker exec -it" into the container and it fails as the container is continually restarting. This is posing an issue in debugging it.

We merged some PR about Docker bugs.
Could you please retry ?
Thanks

I am still seeing the same behavior unfortunately.

docker-compose logs --follow nestdatagraph
Attaching to nest-datagraph_nestdatagraph_1
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
: invalid option namentrypoint.sh: line 2: set: pipefail
nestdatagraph_1  | /entrypoint.sh: line 3: $'\r': command not found
: invalid option | /entrypoint.sh: line 4: set: -
nestdatagraph_1  | set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
nestdatagraph_1  | /entrypoint.sh: line 5: $'\r': command not found
nestdatagraph_1  | /entrypoint.sh: line 6: syntax error near unexpected token `$'{\r''
'estdatagraph_1  | /entrypoint.sh: line 6: `check_database_connection() {
nest-datagraph_nestdatagraph_1 exited with code 2

@gchenuet I think I figured it out. entrypoint.sh has CRLF line endings. Needed to be LF


Generate Teams function in teams.py doesn't work with unique flag

hmmm. Still looking into what's causing this, will update soon.

https://github.com/alan-turing-institute/p2lab-pokemon/commit/9b7661e448eb0b34a3df2fe6a1573b2bfd26e24d fixes this


Compiling with MINGW (Windows)

I tested building MFEM with MINGW (msys2 on Windows 10)
Christian@CHRISTIAN-PC MINGW64 ~/mfem/build
$ cmake -G "MinGW Makefiles" ../
$ cmake --build .

There are two errors:
isockstream.cpp:26:13: error: conflicting declaration 'typedef int ssize_t'
socketstream.cpp:31:13: error: conflicting declaration 'typedef int ssize_t'

I think the typedef should be enabled only for VC compiler, so a possible fix could be to use
#ifdef _MSC_VER
typedef int ssize_t;
#endif

in both files. That fixes the error for me and compiling with Visual Studio 2019 still works fine.

Thanks for reporting this @wo80.
Do you mind proposing a PR with the fix?
Tzanio

@tzanio I'll do the PR later this day.

Building the tests I get two additional compilation errors:
/mfem/tests/unit/fem/test_datacollection.cpp:309:4:   required from here
/mfem/tests/unit/catch.hpp:2311:98: error: ISO C++ forbids comparison between pointer and integer [-fpermissive]

/mfem/tests/unit/fem/test_inversetransform.cpp:63:4:   required from here
/mfem/tests/unit/catch.hpp:2322:96: error: ISO C++ forbids comparison between pointer and integer [-fpermissive]

Those can be fixed comparing to nullptr instead of NULL.
@tzanio Should this go into the same PR?

@tzanio Should this go into the same PR?

Yes, please.

I also have one test failing, but I don't think it's relevant here (at least, it's not related to the above changes):
-------------------------------------------------------------------------------
ParaView restart mode
-------------------------------------------------------------------------------
E:\data\Projekte\mfem\mfem\tests\unit\fem\test_datacollection.cpp:247
...............................................................................

E:\data\Projekte\mfem\mfem\tests\unit\fem\test_datacollection.cpp:294: FAILED:
  REQUIRE( xml.ErrorID() == XML_SUCCESS )
with expansion:
  6 == 0

The reason the test fails is because the generated ParaView.pvd has some weird formatting, see picture below. I don't know why this happens, maybe something with my MinGW setup. Compiling with Visual Studio all tests pass fine.

The reason the test fails is because the generated ParaView.pvd has some weird formatting, see picture below. I don't know why this happens, maybe something with my MinGW setup. Compiling with Visual Studio all tests pass fine.

In the first line, 0D 0D 0A is CR CR LF. I know that with Visual Studio, the line
pvd_stream << "<?xml version=\"1.0\"?>\n";

will actually output <?xml version="1.0"?>\r\n because the file is open in text mode, and so \n is translated to \r\n.
It looks like what is happening is that somehow \r\r\n is being written to the file. Maybe the conversion from \n to \r\n is happening twice? I don't know why this would be the case, but I have no familiarity with MinGW.
Something similar is probably causing the truncation seen later in the file.

@pazner
https://github.com/mfem/mfem/blob/12c7976b2ef7ee800efa81370aa3b7f47d32eeda/fem/datacollection.cpp#L830
The Save method will produce weird output for any system that uses \r\n as new line. The code looks rather fragile anyway.
Visual Studio also produces wrong line endings (0D 0D 0A) in ParaView.pvd, but it doesn't mess up the actual XML, that's why the test doesn't fail.
Flushing the buffer before reading the current position on line 976 will make the test pass:
pvd_stream << fname << "\"/>\n";
pvd_stream.flush(); // <-- workaround
std::fstream::pos_type pos = pvd_stream.tellp();
pvd_stream << "</Collection>\n";

It does not fix the problem of weird line endings.
Should a new issue opened?

Discussion continued in #2497


System freezing

Hello, when I turned on Run on system startup and rebooted, the system became unusable for like 5 minutes. Everything was so slow, apps didn't opened and all I could do was to wait and stop the application. After that it stopped.
OS: Win 10 x64
RAM: 16G
GPU: 1050ti
CPU: i5 7th gen 4c/4t

Hello o/
Without any logs, I am unable to diagnose your issue. Does this happen only on system startup, and not when running it normally? Please try adding a --log and -vvv as run options and then post the resulting log.txt file, that should be created next to the executable.
Also, I'll need the exact version of the application you're running. The version is displayed in the application's window title bar.

Since no further information was provided, I'm closing this.


Yahoo league

Greetings,
Sorry if I posted in the wrong place. I've been using nfldb since the beginning of the season.  Still trying to get the hang of it.  Is there a way to import the roster of my Yahoo league?  I see you have a project called nflfan.  Do they share the same database?  I would be interested in adding the roster table to the same db holding all of the nfl data.
Thanks

nfldb is not a fantasy football project. It never was and never will be. That said, you can certainly use it in fantasy football projects.
nflfan is a single user web application. Its Yahoo importer broke this year (it still works for public leagues, but not for private leagues). I don't know when or if I'll fix it. nflfan does not store things in the database. Instead, it stores roster info (among other things) in JSON files on disk.
Questions about nflfan should be on its issue tracker. Please open an issue there if you want to continue this discussion! Thanks.


Optimum-NVIDIA 28x throughput

https://huggingface.co/blog/optimum-nvidia
Hi! It would be awesome if this had latency and throughput implications for this project.

optimum-nvidia is dependent on trtllm. so I guess the runtime of optimum-nvidia is trtllm.

I guess that means that vLLM can not benefit from the transformer-engine FP8 implementation of optimum?


[ATable] Unable to customize column headers

<template>

        <ATable
        :rows="rows"
        :columns="columns"
        >
        </ATable>

</template>

i hope it will be like that:
const columns = [
        { name: 'name' ,title:"နာမည်"},
        { name: "age',title:"အသက်"},
        { name: 'address',title:"လိပ်စာ" },
    ]

ATable uses th for headers. What is your expected result.

ATable uses th for headers. What is your expected result.

Hopefully the reality is custom headers instead of key-value-dependent keys.

ATable uses th for headers. What is your expected result.

Sorry, i didn't get what you are trying to achieve.
Can you please share the screenshot of your expected result.

Sorry, i didn't get what you are trying to achieve.
Can you please share the screenshot of your expected result.

wait a minute

You want chines headers, right?
Didn't explicit column prop with name property worked?

Didn't explicit column prop with name property worked?

yes

Glad to hear that 😇
If your query is resolved then can we close this?

Glad to hear that 😇
If your query is resolved then can we close this?

but it not resolved yet

Oh, what do you want to customize then?

Oh, what do you want to customize then?

the th tag context should be title content, not it be bing with key

So you just want to rename the property being used for rendering th header?
You want to rename column definition's name property to title, right?

So you just want to rename the property being used for rendering th header?
You want to rename column definition's name property to title, right?

That's what I mean

So you just want to rename the property being used for rendering th header?
You want to rename column definition's name property to title, right?

It would be better if it could support components

It would be better if it could support components

Do you mean rendering custom components instead of just text?

It would be better if it could support components

Do you mean rendering custom components instead of just text?

yes

Hey, I have made a new release can you please give it a try and let me know your feedback?
Thanks :)


Stop and remove started container in the event of exception

Description
Thanks for contributing this Pull Request. Make sure that you submit this Pull Request against the develop branch of this repository, add a brief description, and tag the relevant issue(s) and PR(s) below.

Relevant Issues : (compulsory)
Relevant PRs : (optional)
Type of change :

[ ] New feature
[ ] Bug fix for existing feature
[x] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

At the moment when getContainerPort runs to any exception, it just exists leaving the started container running.

This is to clean up started containers on the docker in the event of any exception and log the error.

Same comments as left in here https://github.com/karatelabs/karate/pull/1858
Agree in principle but would be best if there are unit tests that reproduce the outcome of the exec command and are then passed into the get container.
In your changes if there's a number parse format I'd think it's more likely that the regex to gather the port doesn't work maybe because of a different OS (and the fix might be #1858 !). I just think it'd be important to have the unit tests with the result of the command so we safely do these changes.

Same comments as left in here #1858
Agree in principle but would be best if there are unit tests that reproduce the outcome of the exec command and are then passed into the get container.
In your changes if there's a number parse format I'd think it's more likely that the regex to gather the port doesn't work maybe because of a different OS (and the fix might be #1858 !). I just think it'd be important to have the unit tests with the result of the command so we safely do these changes.

@joelpramos thanks for sharing the #1858  I have proposed the same on the slack thread in support. Let me add some tests.
BTW development branch don't have the same implementation of getContainerPort method as in master

closing because of inactivity


[WIP] Refactor current UserManagement methods according to latest API reference

Description
[WIP]
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
[X] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (317278a) 97.08% compared to head (cf75f7c) 97.08%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #234   +/-   ##
=======================================
  Coverage   97.08%   97.08%
=======================================
  Files          52       52
  Lines        1199     1199
=======================================
  Hits         1164     1164
  Misses         35       35

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@amygdalama Going to break this PR into a smaller one, starting to refactor methods related to User only https://github.com/workos/workos-ruby/pull/235


Build not including custom @types

I've created a few custom types in my npm module, which works fine during development mode, however when building up the module with tsc, those custom @types are not being released with the build files, and when installing my npm module typescript is complaining about the missing type.
TS Config
{
  "compilerOptions": {
    "outDir": "build/lib",
    "module": "esnext",
    "target": "es5",
    "lib": ["es5", "es6", "es7", "es2017", "esnext", "dom"],
    "sourceMap": true,
    "allowJs": false,
    "moduleResolution": "node",
    "rootDir": "src",
    "baseUrl": "src",
    "forceConsistentCasingInFileNames": true,
    "noImplicitReturns": true,
    "noImplicitThis": true,
    "noImplicitAny": true,
    "strict": true,
    "suppressImplicitAnyIndexErrors": true,
    "noUnusedLocals": true,
    "declaration": true,
    "esModuleInterop": true,
    "paths": {
      "*": ["../@types/*"]
    }
  },
  "exclude": [
    "node_modules",
    "build",
    "scripts",
    "acceptance-tests",
    "webpack",
    "jest",
    "src/setupTests.ts"
  ]
}

Expected behavior:
Custom @types being included along with node_modules types
Actual behavior:
Just node_modules/@types being included

Closing due to lack of repro


Multiple Global Configs

Hi,
We are trying to create multiple instances of Parallec and execute Bulk jobs in each one of them. We need to config different concurrency and timeout values in each client. Is that possible? While considering there is one Class of GlobalConfig.
Thanks

@tomerbal  thanks for your interests in parallec.  You can use the same parallec instance with different aync http client, which give you different timeout: http://www.parallec.io/docs/configurations/#async-http-client
for the concurrency, you can just set per requests. http://www.parallec.io/docs/submit-task/#generate-submit-task


Latest cryptography release breaks urllib3 test suite

cryptography 2.1.4 was OK with the urllib3 test suite certs, but cryptography 2.2 (released early today) isn't.
I don't know which side the fix should be on, but filing this anyway to track it.
Cryptography version of this bug: https://github.com/pyca/cryptography/issues/4154

@reaperhulk says that the problem is that some of urllib3's testing certs are actually not valid according to the RFCs, due to the empty issuerAltNames. It sounds like they might make cryptography more forgiving here, but it's not clear if/when, so probably if we can fix the certs on urllib3's side that'd be a good idea.
If it was just the main server.crt affected, this would be easy: just switch to using trustme :-). It's a little more complicated though b/c urllib3 has a whole bunch of different certs with different strange configurations, some subset of which are affected, so some more work is needed to figure out which ones exactly are affected and how to re-issue them while keeping the same quirky properties that we're testing for.

Did a little more digging:
~/src/urllib3/dummyserver/certs$ for F in $(find -name '*.pem' -o -name '*.crt'); do if openssl x509 -in $F -text | grep -q EMPTY; then echo "affected: $F"; fi; done
affected: ./ca_path_test/cacert.pem
affected: ./server.ip_san.crt
affected: ./server.combined.pem
affected: ./client.pem
affected: ./cacert.pem
affected: ./server.crt

Regenerating server.crt, server.combined.pem, server.ip_san.crt is pretty easy. And I think the other certs here shouldn't go through urllib3.controb.pyopenssl.get_subj_alt_name, which is the thing that's crashing... so that might be all that's required?

Cryptography 2.2.1 was released today and accepts these certs again, so I guess this can be closed!


Investigate setting Pyodide HTTP headers via a service worker

More context: https://raspberrypifoundation.slack.com/archives/C02JBAA2NFP/p1705670224318489
Currently, we are setting some HTTP headers on CloudFlare. We should investigate whether it's possible to set these using a service worker instead to keep application-specific behaviour outside of CloudFlare and within the editor-ui project. We should also look into the approach for the embedded editor, which will be on a different site where we don't necessary control the CloudFlare HTTP headers.
https://dev.to/stefnotch/enabling-coop-coep-without-touching-the-server-2d3n

check in incognito

depriorised with https://github.com/RaspberryPiFoundation/digital-editor-issues/issues/303 and https://github.com/RaspberryPiFoundation/digital-editor-issues/issues/304


Remaining args / -- argument separator?

I'd like to be able to grab the trailing args:
php foo.php -d val foo bar
php foo.php -d val -- foo bar

Then I want to get an array ["foo", "bar"] back.
(-- is common as an argument separator, like everything, including arguments with a leading -, following is passed literally to somewhere else.)
I've searched for it in the docs, but actually found no way how to grab every trailing arg. I've only found a way to grab a single arg...
Was this an oversight in the implementation or was there just some undocumented feature?

This was an oversight, but I will look into rectifying it. Thanks for bringing it to my attention, I'll keep you updated.

I understand your example above, but in the referenced issue afterwards (https://github.com/amphp/aerys/issues/58) how would you expect something like that to come back? Just so I know we're on the same page.
bin/aerys -c config.php -- --port 80 --host localhost

I'm not too sure about the API. Eventually, we could have the argument named "--" for that, or have an extra method for that.
I prefer a "--" argument as this means it'd be easily includible in the definition array.

@joetannenbaum any update on this?

Hey @bwoebi, I guess my question is, would you like it to work something like this:
bin/aerys -c config.php -- --port 80 --host localhost

$climate->arguments->trailing();
// ['port' => 80, 'host' => 'localhost']
// or
// '--port 80 --host localhost'

An unparsed variant. That's the point of the -- separator in general.

@joetannenbaum bump ...?

Just put it into master, want to check it out before I tag it?
$trailing_args = $climate->arguments->trailing();

Looks nice, but usually trailing args should also work without explicit -- at the end for arguments without starting - ... if that is possible? :-)
Thanks!

@joetannenbaum so, what do you think?

bump

I'm sorry for the delay, I've been swamped at work trying to launch a big project. I'll get this up this week.

bump

I hear you, I apologize. CLImate will get love this week.

This can be implemented manually by splitting the array if there's  a -- in $argv and dispatching / parsing the two parts separately.

This week? bump.

I'm working on re-working the argument parser so that it's more readable and intuitive. The '--' version of the trailing arguments is in the current release (3.2.1), if you need the other part implemented prior to the re-write I'm happy to accept a pull request.

@joetannenbaum any progress on this?

@imbrish Hi Paul, I've taken over development of CLImate, I don't currently have this specific task scheduled, but I'll look at it as soon as I can. As Joe said, Pull Requests are always welcome :smile:

Hi Craig! I think https://github.com/thephpleague/climate/issues/85 is the best bet.
Currently it's not possible to get an array of remaining arguments, even with $climate->arguments->trailing() because spaces within and between arguments are mixed together.


Adding additional features to it

Hey, I can contribute by adding additional features or optimizing the model, could you assign me any task? its for gsscoc'24 ext

Yes sure, where are you planning to start?

The Suggested-Issues.md file contains the issues to be worked upon.

thankyou, I'll look into it

@smog-root are you interested in this issue?

yaa. i can optimize it by adding Asynchronous. (asynio) llibrary.
are you expecting me to do??

sure! my dc- chinkichacha

My discord:- the _p1r4te

please open new issue for continuation , this one cannot be continued for some reasons!

@tanishaness I have send you a request at DC

can you assign this to me also .i will try

@tanishaness okay. I will do something about it!


Reached heap limit allocation failed error. "managementApi" flag identified as the cause

Hi! For the past month, I've been experiencing constant memory leaks. The RSS memory gradually increases, causing our server to crash after 6-12 hours when it exceeds the memory limit. The memory leak occurred on both my local Windows machine and in our DEV & QA Linux environments.
QA metrics without the fix applied:

Failed attempts to resolve the issue.
Initially, I tried disabling all my existing Fastify plugins to identify the cause, but it didn't help. Then, I updated Platformatic from version 1.31 to 1.51.8 and several dependencies to their latest versions, but the issue persisted. I even upgraded my Node.js version from nodejs-20.9.0-1 to nodejs-20.12.2-2, but it didn't resolve the problem.
Final solution.
Finally, after checking Platformatic Discord or so, I discovered that starting with Platformatic version 1.30, the experimental "managementApi" flag is enabled by default (despite the documentation advising against using it in production). This seemed suspicious, so I immediately disabled it in our DEV environment to track the memory usage. Since then, the memory leak has stopped, and the RSS memory remains constant, preventing out-of-memory crashes.
Sorry if I can't provide more information, but I wanted to report this issue in hopes that someone can take a deeper look into the managementApi functionality to prevent memory leaks, specially that it's enabled by default.
Additional info:
platformatic.json  with the flag disabled:
{
  "$schema": "https://platformatic.dev/schemas/v1.51.8/runtime",
  "entrypoint": "pdt",
  "allowCycles": false,
  "hotReload": false,
  "autoload": {
    "path": "services",
    "exclude": [
      "docs"
    ]
  },
  "managementApi": false,
  "server": {
    "hostname": "{PLT_SERVER_HOSTNAME}",
    "port": "{PORT}",
    "pluginTimeout": 60000,
    "logger": {
      "level": "{PLT_SERVER_LOGGER_LEVEL}"
    }
  },
  "services": [
    {
      "id": "pdt",
      "path": "services\\pdt",
      "config": "services\\pdt\\platformatic.json"
    }
  ]
}

Here it's an example crash log that displayed in our QA environment using platformatic 1.31:
<--- Last few GCs --->

[23:0x55ee12f57e40] 16324834 ms: Mark-Compact 851.6 (1042.2) -> 850.8 (1043.5) MB, 109.58 / 0.00 ms  (average mu = 1.000, current mu = 0.964) task; scavenge might not succeed
[23:0x55ee12f57e40] 16327815 ms: Mark-Compact 851.6 (1043.5) -> 850.9 (1042.7) MB, 106.59 / 0.00 ms  (average mu = 0.999, current mu = 0.964) task; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x55ee0f3c3c34 node::Abort() [node]
 2: 0x55ee0f232173 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 3: 0x55ee0f5d35d4 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x55ee0f5d3895 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 5: 0x55ee0f7c9ddb  [node]
 6: 0x55ee0f7e4fef v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 7: 0x55ee0f835b1c v8::internal::MinorGCJob::Task::RunInternal() [node]
 8: 0x55ee0f442638 node::PerIsolatePlatformData::RunForegroundTask(std::unique_ptr<v8::Task, std::default_delete<v8::Task> >) [node]
 9: 0x55ee0f444b18 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [node]
10: 0x55ee0fef5cc7  [node]
11: 0x55ee0ff0a0a4  [node]
12: 0x55ee0fef69a6 uv_run [node]
13: 0x55ee0f2da962 node::SpinEventLoopInternal(node::Environment*) [node]
14: 0x55ee0f419e10 node::NodeMainInstance::Run(node::ExitCode*, node::Environment*) [node]
15: 0x55ee0f41a21e node::NodeMainInstance::Run() [node]
16: 0x55ee0f37b928 node::Start(int, char**) [node]
17: 0x7f9bd673bd85 __libc_start_main [/lib64/libc.so.6]
18: 0x55ee0f2d82ce _start [node]
npm notice
npm notice New minor version of npm available! 10.1.0 -> 10.8.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.2>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! path /opt/app-root/src
npm ERR! command failed
npm ERR! signal SIGABRT
npm ERR! command sh -c cd services/pdt && npm install && cd ../.. && platformatic start

Thank you!

This is solved as v1.52.3


concat uses pandas append instead of concat

The implementation of pyams concat method loops over pandas append instead of using pandas concat method. Especially for large dataframes with subannual data concat is much faster than append.
I already implemented pandas concat in pyams concat and will push it in a minute. I hope the new feature will find its way in the next release.

I'm not sure yet how to contribute, i.e. create a branch and upload code :) I'll have a deeper look at it on monday. For now I just upload the new Code here for not forgetting it... The code replaces/extends the concat-method in core.py
def concat(dfs, ignore_meta_conflict=False, **kwargs):
    """Concatenate a series of IamDataFrame-like objects

    Parameters
    ----------
    dfs : list of IamDataFrames
        a list of :class:`IamDataFrame` instances
    ignore_meta_conflict : bool, default False
        If False and `other` is an IamDataFrame, raise an error if
        any meta columns present in `self` and `other` are not identical.
    kwargs
        Passed to :class:`IamDataFrame(other, **kwargs) <IamDataFrame>`
        if at least one of dfs is not already an IamDataFrame

    Returns
    -------
    IamDataFrame

    Raises
    ------
    ValueError
        If time domain or other timeseries data index dimension don't match
    """
    if isstr(dfs) or not hasattr(dfs, '__iter__'):
        msg = 'Argument must be a non-string iterable (e.g., list or tuple)'
        raise TypeError(msg)

    for i in range(len(dfs)):
        if not isinstance(dfs[i], IamDataFrame):
            dfs[i] = IamDataFrame(dfs[i], **kwargs)
            ignore_meta_conflict = True

        if dfs[0].time_col != dfs[i].time_col:
            raise ValueError('Incompatible time format (`year` vs. `time`)')

        if dfs[0]._data.index.names != dfs[i]._data.index.names:
            raise ValueError('Incompatible timeseries data index dimensions')

    _df = dfs[0].copy()

    # merge `meta` tables
    for df in dfs:
        _df.meta = merge_meta(_df.meta, df.meta, ignore_meta_conflict)

    # concatenate data (verify integrity for no duplicates)
    _dfs_data = [df._data for df in dfs]
    _data = pd.concat(_dfs_data, verify_integrity=True)

    # merge extra columns in `data` and set `self._LONG_IDX`
    for df in dfs:
        _df.extra_cols += [i for i in df.extra_cols
                           if i not in _df.extra_cols]
    _df._LONG_IDX = IAMC_IDX + [_df.time_col] + _df.extra_cols
    _df._data = _data.sort_index()

    return _df```

Thanks for the suggestion - I have a few ideas on how to improve that, but I'll wait until you have mastered the first steps of working with git(hub)... I'm pretty sure that there is some value for you in learning that beyond improving pyam performance. Happy to assist bilaterally if you join our Slack channel, see https://pyam-iamc.readthedocs.io/en/stable/contributing.html

I think I managed to create the pull request :)