ASCOM.DarkSkyGeek.FocuserApp.exe unhandled exception

The ASCOM.DarkSkyGeek.FocuserApp.exe application generates the following unhandled exception when attempting to "Set Zero position!" when clicking the either of the left-arrow buttons when the Focuser is moving.

This does not occur when attempting to click the right-arrow buttons when the Focuser is moving because the right-arrow buttons are disabled while the Focuser is moving. To be consistent, the left-arrow buttons should also be disabled when the Focuser is moving.

Correction, I incorrectly described the operations in the reverse order - in actuality, attempting to "Set Zero position!" when the Focuser is moving generates the unhandled exception. When moving the Focuser with the right-arrow buttons, the "Set Zero position!" button is disabled preventing the issue, but when moving the Focuser with the left-arrow buttons, the "Set Zero position!" is NOT disabled. So, the "Set Zero position!" should be disabled when moving with any of the arrow buttons.

Yes, I was able to reproduce. Fix incoming!


Native Federation: Nx workspace default setup errors

I have a Nx workspace as monorepo, all basic setup.
When I have the @nx/angular dependency, as it is from the default setup, i get a ton of errors on building or serving the app.
When I move this dependency to the dev-dependencies, everything is fine.
I read this in the native-federation read.me:

Perhaps your shared packages contain some code esbuild cannot transfer to EcmaScript modules. This should not be the case for packages, built with the Angular CLI or Nx and the underlying package ng-packagr. If this happens, please let us know about the package causing troubles.

I'm new to NX so I'm not sure if I need some of the @nx/angular functionality in my applications, but I think this should work, or at least been mentioned somewhere.
And an other issue I have after the basic setup, my host can not load the remote at all.
I get the following error:
ERROR Error: unknown remote check-out -> check-out is the name of my remote.
I can see in the dev-tools, that both of the remoteEntry.json, host and "unknown" remote are loaded. So I'm not sure if this is a bug?

Hi,
I know this one. @nx/angular seems to be a nodejs packages, hence we cannot compile it for the browser. To resolve this, please move it to devDependencies or add it to the skip list in your federation.config.js.

Thanks for the answer.
In addition I found my other problem.
It seems, like the schematics from native-federation translate the name of a kebab-case remote to a camelCase in the assets/federation.manifest.json. Then it was, in my case, registered as checkOut.


Pass unauthenticated user Display Name using URL. ex.: letsmeet.no/test?name=myself

I thought about integrating letsmeet.no rooms to our website for communicating with our users that needs some kind of support.
The room name will be the user id (so that the room is private), but today the user will have to type his/hers name during room entry.
As the user is already authenticated in our website, I could send the person name to the URL directly. Something like "http://letsmeet.no/user-anthony?name=Anthony Evans"
What do you think?

 Now I testes with displayName and it works! Thanks!

Where can I find any documentation on those query parameters?


Visit https://pkg.go.dev/github.com/golang/perf/cmd/benchstat
What did you see happen?
Documentation is for v0.0.0-20190306144031-151b6387e3f2, from 2019. Documented flags include -html, which does not exist in the latest version.
What did you expect to see?
Documentation matches the binary installed via go install golang.org/x/perf/cmd/benchstat@latest.
The flag was removed in perf rev 02c5517, from January 2023.

Related Issues and Documentation

x/perf/benchstat: README.md is out of date #20727 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

CC @aclements maybe?

https://pkg.go.dev/github.com/golang/perf/cmd/benchstat is the documentation for github.com/golang/perf, not golang.org/x/perf. Only the latter is the correct module path.
The psuedoversion v0.0.0-20190306144031-151b6387e3f2 is at https://go.googlesource.com/perf/+/151b6387e3f2aa5908e4a6074f06be9ecc34f004, before there was a go.mod file, so I suppose this package was importable via github.com/golang/perf.
cc @golang/pkgsite is there anything we can do here to avoid confusion? Perhaps just remove github.com/golang/perf entirely?

This is probably similar to #68357 (though I didn’t double check the details, so sorry if not).

When I submitted, it hadn't occurred to me that there were two different URLs for benchstat docs.
https://pkg.go.dev/golang.org/x/perf/cmd/benchstat
https://pkg.go.dev/github.com/golang/perf/cmd/benchstat
For pkg.go.dev/golang.org/x/perf/..., is the package crawler actually using the golang.org url or does it still go to github.com/golang/perf/... like the other?
My thinking is, if the package crawler detects all of the following:

$url and $url2 are both for code in the same git repo, and
only one of the two has a module, and
the one with the module is newer
... then manipulate the page in some way that results in users going to the better version.

This manipulation could take the form of a banner newer version at new import path [link] and/or, as mentioned in https://github.com/golang/go/issues/68357#issuecomment-2219463378, via meta tags telling search engines to go away. (IMO adding both would be best, so that if I get to the old version in spite of a search engine, I can still get to the newest/best version).
I think this approach would work on both #68357 and on this issue.

For pkg.go.dev/golang.org/x/perf/..., is the package crawler actually using the golang.org url or does it still go to github.com/golang/perf/... like the other?

golang.org/x/... uses the <meta name="go-import"> mechanism to redirect to the actual git repository. However, the official git repo for golang.org/x/perf is https://go.googlesource.com/perf, not https://github.com/golang/go.
So while I think your proposed approach would work for most vanity import paths, it wouldn't work here.

Let's remove github.com/golang/perf from pkgsite.


Can't delete Cluster resource

When destroying the Cluster resource, it times out.
I've found that the k0sctl process prompts the user to confirm, making it impossible to delete the resource.
Solution: Set the parameter "Force: true" in this part:
https://github.com/ydkn/pulumi-k0s/blob/main/provider/k0sctl.go#L139

Adding this does not seem to fix it. Anything anywhere else that'd need changing?

#12


Make rebar3-nix-bootstrap depend on erlang.

This fixes patchShebangs ability to properly fix up path to escript binary.
@peti @ericbmerritt

I've pushed the patch to http://hydra.cryp.to/jobset/nixpkgs/erlang-updates ...

Looks like the base problem is fixed. There are few builds like [1] which I have been expecting to fail.
1: http://hydra.cryp.to/build/1554398


Write mode is not being used.

Hi,
I have a rustfmt.toml with:
reorder_imports = true
write_mode = "Overwrite"

When I run fmt either with cargo fmt or rustfmt directly the backup files are still created. I already tried to change to write_mode = "overwrite" and the same thing happens. The config file is being read though since reorder_imports = true works.
Is this a known bug or am I doing something wrong?
Thanks.
P.S.: I'm using rustfmt v0.2.1.

I tested this with master and could not reproduce. I think this has been fixed by @kamalmarhubi  in one of his recent PRs, though I'm not sure which one.
Closing, but feel free to re-open if this is still happening for you.

I don't recall doing anything that would have fixed it, but I do have feelings about write_mode-in-rustfmt.toml (spoiler: I don't like it!).

:-)


Update L5R Sheet to Portuguese

###Updating character sheet to the Official Portuguese version of L5R
Changes / Comments
Line 23 issue is solved
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Hello! Your Pull Request includes changes to translation files. We will not deny your Pull Request, but we would prefer sheet contributors use Crowdin for translations. Please email Cassie at<EMAIL_ADDRESS>and she will get you an invite to our Crowdin within 48 hours. Please use that for future translation updates! Thanks for all you do!


B-21460-INT Mobile Home and Boat shipments now have 2nd/3rd Address

Agility ticket
Summary
Fixed issue with Prime Sim created shipments not having 2nd/3rd addresses
How to test

Access the office app
Login as a Prime Sim
Open a move
Create a new Boat/MH shipment with 2nd/3rd addresses
login as TOO/TIO/SC and open that move
Verify shipment has 2nd/3rd addresses and H&AL shows 2nd/3rd addresses for that shipment

I ran through the test steps, and everything is populating as expected 👏


refactor(connector): [Worldline] Currency Unit Conversion

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description
This pull request implements the get_currency_unit from the ConnectorCommon trait for the Worldline connector. This function allows connectors to declare their accepted currency unit as either Base or Minor. For Worldline  it accepts currency as Minor units.
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Links to the files with corresponding changes.

crates/router/src/connector/worldline.rs
crates/router/src/connector/worldline/transformers.rs

Motivation and Context
Closes #2249
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

@SanchithHegde @srujanchikke can you review the commits?

Let me know if any changes to be made in this.

Looks good to me!
Thanks for the PR, @Suraj3240!

Thank you 😊

Hey @Suraj3240  👋,
Thanks a bunch for all your contributions! We've got a little something for you to show our appreciation.
Just take a moment to fill out this form, and get ready for some awesome swag coming your way.
Thanks!


add EtherWalletKit on the Blockchain section

Project URL
https://github.com/SteadyAction/EtherWalletKit
Category
Blockchain
Description
You can implement Ethereum wallet without a server and blockchain knowledge.
Why it should be included to awesome-ios (optional)
Checklist

[ x] Only one project/change is in this pull request
[ x] Has unit tests, integration tests or UI tests
[ x] Addition in chronological order (bottom of category)
[ x] Supports iOS 9 / tvOS 10 or later
[ x] Supports Swift 4 or later
[ x] Has a commit from less than 2 years ago
[ x] Has a clear README in English

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

849
301
https://github.com/alexdrone/FlexboxLayout redirects tohttps://github.com/alexdrone/flexboxswfit_deprecated

3144
302
http://ios-goodies.com redirects tohttps://ios-goodies.com/#_=_

  Generated by :no_entry_sign: Danger


Made compatible with kitnic.it

This commit adds Gerbers plotted with the OSHPark CAM job, a 1-click-bom.tsv which tries to specify all the retailer SKUs and a kitnic.yaml description file to make your repository compatible with kitnic.it.
If you are happy with adding your project it would look something like this (just a preview). We are running a promotion at the moment so you get $25 voucher for Dangerous Prototypes' store if you add your project. If you are not happy to add it of course, I'll let it be and remove the preview from the web.
Some notes about the BOM

I chose a random 0603 yellow LED but didn't double check if the current limit is OK for it
I picked a 16Mhz resonator but am not sure if the footprint is right, in fact it's very likely that it's the wrong part
I don't know which RFM12B part is the right one and where to source it

Sorry for the delayed response to this. It looks nice for those able/willing to do some soldering. The resonator I used is called CSTCE8M00G52-R0, Ceramic Resonator, 8MHz Fundamental 10pF, 3-Pin Cap Chip, 3.2 x 1.3 x 0.7mm and has item# 721-4824 at RS. Yours seem to be a through hole so please revisit the PR :D The RFM69C is sourced off eBay.

I am glad you approve! I have amended the BOM with your info. I also added a link to the upcoming Kitnic page to the README. Can remove that commit if it's not wanted of course.

This is now up as: https://kitnic.it/boards/github.com/kanflo/aaduino/


Add blog post about OCI security profiles

PTAL @jhrozek @JAORMX @pjbgf @ccojocar
Targeted for May 24.

Targeted for April 12, right before KubeCon.

Sorry, we have the Kubernetes post-release communication series of blog announcements coming up. You'll need to liaise with SIG Release's comms team to get that date. The Kubernetes v1.27 release is likely to happen on the 11th of April.
/hold
pending allocation of publication date.

@kubernetes/sig-docs-blog-owners would a release date this week work for us?

Thanks @sftim, fixed everything as suggested.

I'm afraid this'll need a new publication date. How does late May sound? If you want publication earlier, you can; please liaise with release comms.

@sftim may sounds good to me! Do you have a specific date in mind?

@sftim friendly ping, which date do we want to choose?

@sftim I moved that one to 2023-05-24 for now if that would be a good fit.

Hi @saschagrunert, May 24th looks good to me, it doesn't look like it's conflicting with anything else on our blog calendar.

This still needs an lgtm -- @pjbgf, @jhrozek, @tuxerrante, since you reviewed earlier, could you take another look to make sure your comments were addressed adequately and provide an lgtm if so?

Totally fine for me 🙂
/lgtm

/unhold
@nate-double-u may I ask you to approve?

Thanks
/approve


Support Contains Words in WIQL

Summary of the Pull Request
What is this about?
Fixes The specified operator cannot be used with long-text fields. error we've been seeing lately when attempting to create ADO work items.
Info on Pull Request
The = operator is not support on long-text fields. The ADO API tells us which operators are supported for a particular field. The particular field in which we saw this error does support the  Contains Words operator. Fall back to Contains Words if = is not supported.
What does this include?
Validation Steps Performed

Reproduced the error we were observing in local dev API call to ADO
The error doesn't happen anymore after this PR

Codecov Report

Merging #2686 (d5d707a) into main (f48546f) will decrease coverage by 4.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2686      +/-   ##
==========================================
- Coverage   29.38%   25.36%   -4.03%
==========================================
  Files         291      123     -168
  Lines       36048    12855   -23193
==========================================
- Hits        10594     3261    -7333
+ Misses      25454     9594   -15860

Impacted Files
Coverage Δ

src/ApiService/ApiService/Log.cs
7.72% <0.00%> (-0.10%)
:arrow_down:

src/ApiService/ApiService/OneFuzzTypes/Enums.cs
32.39% <ø> (ø)

...Service/ApiService/onefuzzlib/notifications/Ado.cs
0.00% <0.00%> (ø)

src/agent/win-util/src/jobs.rs

...gent/input-tester/src/test_result/vcpp_debugger.rs

src/agent/onefuzz/src/uploader.rs

src/agent/onefuzz-task/src/local/test_input.rs

src/agent/onefuzz-task/src/main.rs

src/agent/debugger/src/module.rs

...nt/onefuzz-task/src/tasks/report/dotnet/generic.rs

... and 161 more

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


Speculative fix for code-completion nullptr dereference

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

I haven't managed to find a test case, but we see crash reports about
this call. It may be that the correct fix is for some other part of the
compiler not to produce a null protocol self, but it's harmless for the
ASTPrinter to dodge a null pointer here.
rdar://problem/27053440

@swift-ci Please test and merge

That doesn't seem related.

@swift-ci Please test and merge

Not related.  Merging...


[QA] Instantiated avatars are not reflecting self avatar locomotion

Explorer Alpha build version:
0.3.160-main-251ca6c
Issue Description:

When instantiating an amount of avatars, in some ocations the locomotion breaks and there is no movement other thant sliding and jumping
Steps to reproduce:

Instantiate avatars (more than 30 if possible)
Move around

Expected behaviour:
The avatars instantiated replicate self movement
Current behaviour:
There is no movement of the avatars instantiated and self avatar
Reproduction rate:

[ ] < 10%
[ ]  < = 25%
[X]  50%
[ ]  < = 75%
[ ]  100%

Severity:

[ ] Cosmetic
[ ] Minor
[X] Medium
[ ] High
[ ] Critical
[ ] Blocker

Priority:

[ ] High
[X] Medium
[ ] Low

Platforms / OS:

[ ] Windows 11
[X] Windows 10
[ ] Mac Sonoma
[ ] Mac (specify the version on Additional Notes)

Evidence:
Additional Notes:

https://github.com/decentraland/unity-explorer/assets/139157886/87d74ed5-551c-4f4a-886d-1384d2b4c813

Not a bug :)


[CROSSDATA-647] Fix microstrategy problem with create table as select

Description
Microstrategy doesn't support create table using as select, so if a query select table as query comes, It will have the same behaviour as a view.
It follows https://github.com/Stratio/Crossdata/pull/763.
Testing

[ ] Unit, integration tests

Documentation

[ ] Changelog update
[ ] Documentation link

Changes Unknown when pulling 581093e2db1a847c5b958cdda451274503f33200 on fix/microstrategy_create_table into ** on master**.

Coverage remained the same at 35.829% when pulling d31936fe8f97156804fe65aea4dc6b41928f01e1 on fix/microstrategy_create_table into f0a5294db1a51edf321230816dbd0b8270d4b93e on master.

Coverage remained the same at 35.829% when pulling d31936fe8f97156804fe65aea4dc6b41928f01e1 on fix/microstrategy_create_table into f0a5294db1a51edf321230816dbd0b8270d4b93e on master.


ABI: Automation should complete only when workers and master got attached and co operators are running as true.

Implement wait-for complete install for ABI

This issue has been resolved in above mentioned PR.


SIC Logo

Hi.
What's wrong with the old logo?

Hello!
I'd like to see it updated a bit more 😉... I love this IPTV list, by the way!
Thanks.

Ok, thanks.
I still don't know what's the recommended size for logos in most IPTV players. However, smaller file size means faster zapping, so I'll aprove your PR.


episode mark seen

Describe the bug
I don't know if this feature has already been implemented cause if it has been, then i am reporting a bug.
if episode is marked as seen and you press back and return to home, the anime you watched should now be in the next episode in the continue watching section instead of where you left off from the finished episode
To Reproduce
Steps to reproduce the behavior:

finish the episode and mark anime as seen
press back to return home
anime should be in the next episode in the continue watching section instead of where you left off in the finishes episode

Screenshots
If applicable, add screenshots to help explain your problem.
Please complete the following information:

Android 7.0
1.2.3
OPPO F3

Additional context
Add any other context about the problem here.

Should be fixed in latest update :+1:


Mind the Gap - OSS Badges

This will add a badge to this project to signify it's an open source software project. Clicking the badge links to the new Hudl OSS page.
NOT READY FOR MERGE UNTIL PAGE IS DEPLOYED

:100:


Change fixed shortcuts for configurable shortcuts (remove fixed_shortcuts)

The idea of this PR is to remove fixed_shortcuts and leave only config_shortcuts as suggested by @ccordoba12
I have encounter several issues:

Some fixed_shortcuts use QKeySequence (copy, zoom in, and zoom out), I replaced by the corresponding shortcuts (Ctrl+c Ctrl++, Ctrl+-), because It is not possible to import QKeySequence in spyder/config/main.py

RUN_CELL_SHORTCUT and RUN_CELL_AND_ADVANCE_SHORTCUT variables in spyder/config/gui.py are platform dependent (I moved that code to spyder/config/main.py but I change Qt imports to strings)

Some actions have two shortcuts, I created two different configurations keys (example: editor/close file 1 'editor/close file 2) There is another workaround? should shortcuts have several options?

It's ok to remove fixed_shortcut() function? how plugins should register shortcuts? (there is already an issue about this #3254 )

Fixes: #3395

@rlaverde, thanks a lot for this!
To fix the errors in Travis and AppVeyor, please merge with 3.x. I just fixed those errors in #3499 ;-)
Note: Please avoid rebases to update your branches and use merges instead. Rebases are messy and most of the time make history very difficult to follow.

@rlaverde, this looks good to me, thanks a lot for it :-)
I left a couple of very simple comments, after you solve them I can merge it :-)

@ccordoba12 I just added two commits with the changes that you suggested
I experience a bug, zoom out (Ctrl+-) is not working, It was working using QKeySequence.ZoomIn; I'm not sure if this is related with this bug in QT https://bugreports.qt.io/browse/QTBUG-38137

@ccordoba12 I already solved the zoomIn error, It wasn't related to the Qt bug, It was a double lambda word :/
I think this is ready

Looks good :-) @rlaverde could you rebase?

@goanpeca I just rebase it, and reorder and squash some commits to make the history cleaner.

Just a warning / reminder (prompted by #3584) that this breaks shortcuts in external plugins since in the discussion of #3254 it was decided that external plugins should use fixed shortcuts for now.

@jitseniesen, you're right. Let's discuss this in #3254 to not pollute this PR :-)

@rlaverde this is ready? any comments @ccordoba12

@goanpeca I think this is ready, but #3254 have to be resolved first

Yep, this is ready but please don't merge it until I release 3.0.2. After that, we'll start the work for 3.1 :-)
#3254 is for 4.0, so it doesn't need to be resolved first :-)


See 'docker --help'
  CHECK   vetting all packages...

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

The build has been terminated

I don't know whether docker: 'buildx' is not a docker command. is the cause of the error or a symptom.
Cc @dylandreimerink just in case, although given how little info we have, I have no idea how to reproduce.

The buildx message is unrelated, and also not the last message vetting all packages.... I have seen this failure mode before and it turns out to be the go test ./... stage which can go for >10m without making output which Travis doesn't like.
Should be noted that I have only ever seen it when one of the tests breaks which causes a timeout in one of the tests. So there might be an underlying issue. But we should also fix the fact that those errors are obscured.
The simplest "fix" would be to pass -v to go test so it will output while it is running. But that might break our nice tparse formatting. And spam the Travis CI log.

we are moving away from travis, the first step is to migrate amd64 job to GHA
https://github.com/cilium/cilium/pull/22900

just ran into this again, would it be OK if I added something like -timeout 9m30s to make integration-tests? (Maybe it has to be conditional on running on travis?)


Can not pull v3.9.0 from Jitpack

I tried to pull v3.9.0 from Jitpack but it did not work.
The latest version that worked for me was: v3.8.2

This is a known issue https://github.com/taycaldwell/riot-api-java/issues/61. Please check existing issues before creating a new one.


Bug: contains: "%" always matches every row, but it shouldn't

This code returns all rows, but it shouldn't:
MyModel.find().where({name: {contains: "%"}}).exec(//...

I'm using MySQL.  EDIT: I can also confirm this behavior using blueprints and hitting the following URL:
.../api/user?where={%22name%22:{%22contains%22:%22%25%22}}
Possibly related to #802.
This function calls normalize.likeCriteria.  It seems to have been written in a hurry since the usage message is for startsWith, not contains.  Presumably likeCriteria should be escaping percent signs, but it's not.
https://github.com/balderdashy/waterline/blob/4653f8a18016d2bcde9a70c90dd63a7c69381935/lib/waterline/query/finders/helpers.js#L61-L72
Here's likeCriteria:
https://github.com/balderdashy/waterline/blob/912734b0fbb05d179d7183c0932b83c8010cf4bc/lib/waterline/utils/normalize.js#L267-L286
This function is never called; not sure why: https://github.com/balderdashy/waterline/blob/4653f8a18016d2bcde9a70c90dd63a7c69381935/lib/waterline/utils/normalize.js#L383-L386
EDIT: also that function doesn't make sense to me.  It will not touch percent signs at the beginning or end of the string, it won't touch adjacent percent signs, and it won't prefix percent signs with a backslash.

Hi @cspotcode, I'm not sure this is a waterline core issue, it looks more like a waterline-sequel (which is used by sails-mysql) issue. Check:
https://github.com/balderdashy/waterline-sequel/blob/master/sequel/lib/criteriaProcessor.js#L623-L645
@tjwebb, what do you think?

In that case, what is the purpose of the waterline code I found?  Is it not being used?  I unfortunately don't have time to do more debugging or write a fix.  This bug does affect my work, so I will be grateful for a fix to be implemented.
Thanks in advance.

I honestly can't tell as I am myself getting acquainted with it. But I don't think waterline core would be able to do this escaping as it supports all kind adapters, of which many are not SQL.

I'm not sure I see the error
Model.find().where({name: {contains: "%"}}) this based on looking it it would generate the follow sql statement select * where name like '%'
This is valid SQL and does return all records. It may be not be ideal, but its valid.

Yeah, I know it's valid SQL, but is it the valid & intended behavior for waterline's "contains" query?  Waterline is a multi-DB ORM that claims you can use the same queries with any supported DB, without modification.  If I say 'contains': '100%', what does that mean?  Does it mean I'm looking for an attribute containing the string "100%"?  Will it behave the same way in MySQL, sails-disk, and MongoDB?  What about the meaning of "_"?  Of ".", "^", or "$"?
From the sails documentation (http://sailsjs.org/#!/documentation/concepts/ORM/Querylanguage.html)

The Waterline Query language is an object-based criteria used to retrieve the records from any of the supported database adapters. This means that you can use the same query on MySQL as you do on Redis or MongoDb. This allows you to change your database without changing your code.

...and further down:

'contains'
A shorthand for pattern matching both sides of a string. Will return records where the value contains the string anywhere inside of it.
Model.find({ class: { 'contains': 'history' }})
// The same as
Model.find({ class: { 'like': '%history%' }})

"where the value contains the string anywhere inside of it."  No mention of SQL-specific behavior.
Unless I'm mistaken, the Mongo adapter does things differently, and does not convert all % into .*:
https://github.com/balderdashy/sails-mongo/blob/1e7f2e1d3798fcf0a510455d54cbacd0f7a0125f/lib/query/index.js
Waterline claims to implement a consistent interface across databases, but it doesn't.  It should either update the docs to explain the differences, update the docs to explain the "%" and "_" wildcard matching, or normalize behavior across DB backends.  I'm not sure which is the bug, but either way there's a bug.

i get you, my bad
Model.find().where({name: {contains: "%"}}) should be generating the following SQL then select * where name like '%/%%' where it escapes the percent and encapsulates it. Intead its not escaping the reserved characters and giving us like %%%
That code you found https://github.com/balderdashy/waterline/blob/4653f8a18016d2bcde9a70c90dd63a7c69381935/lib/waterline/utils/normalize.js#L383-L386
would fix it, but in reality it should be escaping all reserved characters, not just %.
That code not withstanding it is a  a waterline-sequel issue. Agreed that it is confusing with the odd code in waterline.

Tiny nitpick, just to clarify: the generated SQL should use a backslash instead of a forward slash, so select * where name like '%\%%'
In MySQL LIKE queries the underscore also has a special meaning, so it should be replaced with \_.

@cspotcode yup, my bad.

@cspotcode, @randallmeeker, this has been raised in balderdashy/waterline-sequel#33, please continue the discussion there.


Check how to do some tasks asynchronously

Some tasks like sending notifications to affected users can be done asynchronously so as to speed returning a response for the triggering controller.

Task execution is well-documented in https://docs.spring.io/spring-framework/docs/current/reference/html/integration.html#scheduling


Settings

shared preferences package?

https://pub.dev/packages/shared_preferences

https://pub.dev/packages/shared_preferences


Sync again

Sync again

We should have clear contribution guidelines, and probably not accept PRs on the main branch. Only on develop


fuzz: add fuzzer for mulmod

Fuzzer for mulmod

Fixed. I guess the old corpus is moot now though, so we could clear that from CI (dunno how much it matters)


libwebp cve

flutter engine uses libwebp 1.3.1
https://github.com/flutter/engine/blob/b0d6bd15e7399bd69c7fef457fc53e405635b76f/DEPS#L604-L605
as CVE-2023-4863 describes libwebp < 1.3.2 have this vulnerability.
is it affect flutter apps?

The fix was backported to the 1.3.1 branch prior to the release of 1.3.2:
https://chromium.googlesource.com/webm/libwebp/+/2af26267cdfcb63a88e5c74a85927a12d6ca1d76
The link DEPS file references this commit.

@Viper-Bit

flutter engine uses libwebp 1.3.1
https://github.com/flutter/engine/blob/b0d6bd15e7399bd69c7fef457fc53e405635b76f/DEPS#L604-L605

It was rolled back to 1.3.1 as part of this cherry pick: https://github.com/flutter/flutter/issues/134496

is it affect flutter apps?

If you face any such issues with vulnerability, file an issue with relevant details so that we can address it properly.
Closing for now.


Bug in Lean checker

The Lean checker fails on the message below. @johnjyang can take a look, please?
msg = '''### Spec: In Lean4, write a factorial function and prove that the factorial is always strictly positive.
### Lean4:
```lean
import Mathlib

def factorial (n: Nat) : Nat :=
  if n = 0 then
    1
  else
    n * (factorial n-1)

theorem factorialPositive (n : Nat) : factorial n > 0 :=
  Nat.zeroLtOne.lt_of_lt_add $ by
    induction n with
    | zero => simp [factorial]
    | succ n h => simp [factorial, h]

#eval factorial 5

In this Lean4 code, we have defined a factorial function that computes the factorial of a given natural number n. The function is defined recursively: the factorial of 0 is 1, and the factorial of a positive integer n is n times the factorial of n-1.
We then prove that the factorial of any natural
'''
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... >>> import lean

lean.calculateScoreHelper(msg)
{ "cmd" : "import Mathlib\n\ndef factorial (n: Nat) : Nat :=\n  if n = 0 then\n    1\n  else\n    n * (factorial n-1)\n\ntheorem factorialPositive (n : Nat) : factorial n > 0 :=\n  Nat.zeroLtOne.lt_of_lt_add $ by\n    induction n with\n    | zero => simp [factorial]\n    | succ n h => simp [factorial, h]\n\n#eval factorial 5" }

Traceback (most recent call last):
File "", line 1, in
File "/home/namin/llm-verified-with-monte-carlo-tree-search/lean.py", line 39, in calculateScoreHelper
r = checkLean(v)
File "/home/namin/llm-verified-with-monte-carlo-tree-search/lean.py", line 79, in checkLean
out = proofsearch.run_code(lean_code_block.strip(), verbose=True)
File "/home/namin/llm-verified-with-monte-carlo-tree-search/pySagredo/proofsearch.py", line 37, in run_code
index = self.proc.expect('env": \d+}', timeout=20)
File "/home/namin/mambaforge/envs/trl/lib/python3.10/site-packages/pexpect/spawnbase.py", line 343, in expect
return self.expect_list(compiled_pattern_list,
File "/home/namin/mambaforge/envs/trl/lib/python3.10/site-packages/pexpect/spawnbase.py", line 372, in expect_list
return exp.expect_loop(timeout)
File "/home/namin/mambaforge/envs/trl/lib/python3.10/site-packages/pexpect/expect.py", line 179, in expect_loop
return self.eof(e)
File "/home/namin/mambaforge/envs/trl/lib/python3.10/site-packages/pexpect/expect.py", line 122, in eof
raise exc
pexpect.exceptions.EOF: End Of File (EOF). Exception style platform.
<pexpect.pty_spawn.spawn object at 0x7fe3878f10f0>
command: /home/namin/.elan/bin/lake
args: [b'/home/namin/.elan/bin/lake', b'env', b'lean', b'--run', b'REPL/Main.lean']
buffer (last 100 chars): ''
before (last 100 chars): 'l\r\n#11866 factorial\r\n#11867 factorial\r\n#11868 _eval._closed_1\r\n#11869 _eval\r\n#11870 _eval._boxed\r\n\r\n'
after: <class 'pexpect.exceptions.EOF'>
match: None
match_index: None
exitstatus: None
flag_eof: True
pid: 1198115
child_fd: 5
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile('env": \d+\}')

The file crashes the Lean server because it has an infinite loop and an eval. What to do?

I think for now, I will skip evaluations.

also see: https://github.com/namin/llm-verified-with-monte-carlo-tree-search/commit/cf36cffad085bbdd64aee1a1fcdffef876d4892e

have you figure it out? I run lean.py it returns:
{ "cmd" : "import Mathlib\n\ndef factorial : Nat → Nat\n| 0 => 1\n| n+1 => (n+1) * factorial n\n\ntheorem factorial_pos : ∀ n : Nat, 0 < factorial n\n| 0 => Nat.zero_lt_one\n| n+1 => Nat.mul_pos (Nat.succ_pos n) (factorial_pos n)\n\n#eval factorial 5" }
(-1.0, '')


chore: fix coam helm deployment.yaml indentation

I noticed that this failed in shipit, also updated dependencies as I got an error testing this with helm template

Added the missing network policies for COAM and Administration ingress with a6d8a8a.


Remove all references to geopm_context

This file was used to add source code locations to
the PYTHONPATH while the test was executing.
Require that user have geopmdpy and geopmpy in
their PYTHONPATH in order to run tests
Move skipped integrations tests into separate
directory and get rid of imports from main.py
Use unittest discover mechanism to find integration
tests for the HPC runtime.
Require that the geopm source code repo is in
the python path to give access to integration
test modules that are not installed
Modify imports in tests accordingly
TODO: Add a skip decorator that honors
GEOPM_RUN_LONG_TESTS, this feature was part of
main.py and has been removed.
Relates to #1675
Fixes #2033

# SUCCESS: test-service.sh Thu Dec 23 08:25:10 PST 2021
The integration tests are passing.  Just need to fix the unit test.

The skipped files primarily do not use the unittest infrastructure, but rather were dropped in the integration/test directory and not added to the main.py imports.  These were never executed as part of our integration test scripting.


ETCD: 2.3.x - netutil: could not resolve host

Greetings,
Environment
OS: RHEL 7.3
ETCD: etcd-3.0.15

Problem
Deploying ETCD using Marathon/Mesos. Used to work fine under 2.0.10, but under 3.0.x it is exhibiting problems with host resolution. This is my JSON file for Marathon:
{
        "id": "/etcdhost",
        "groups": [{

                "id": "/etcdhost/sdncluster1",
                "apps": [{
                        "id": "etcd1",
                        "cpus": 0.5,
                        "mem": 128,
                        "instances": 1,
                        "constraints": [
                                ["hostname", "CLUSTER", "mslave1"]
                        ],
                        "container": {
                                "type": "DOCKER",
                                "volumes": [],
                                "docker": {
                                        "image": "akamalov/docker-etcd:3.0.15",
                                        "network": "HOST",
                                        "portmappings": [{
                                                "containerPort": 2380,
                                                "hostPort": 33380,
                                                "protocol": "tcp"
                                        }, {
                                                "containerPort": 2379,
                                                "hostPort": 33379,
                                                "protocol": "tcp"
                                        }],
                                        "privileged": false,
                                        "parameters": [{
                                                "key": "hostname",
                                                "value": "etcd1.sdncluster1.etcdhost.marathon.mesos"
                                        }],
                                        "forcePullImage": false
                                }
                        },
                        "args": [
                                "--name etcd1.sdncluster1.etcdhost.marathon.mesos",
                                "--initial-cluster etcd1.sdncluster1.etcdhost.marathon.mesos=http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380,etcd2.sdncluster1.etcdhost.marathon.mesos=http://etcd2.sdncluster1.etcdhost.marathon.mesos:2380,etcd3.sdncluster1.etcdhost.marathon.mesos=http://etcd3.sdncluster1.etcdhost.marathon.mesos:2380","-initial-cluster-token mesos-cluster",
                                "--initial-advertise-peer-urls http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380",
                                "--advertise-client-urls http://etcd1.sdncluster1.etcdhost.marathon.mesos:2379",
                                "--initial-cluster-state new",
                                "--heartbeat-interval 500",
                                "--election-timeout 2500"
                        ]
                }, {
                        "id": "etcd2",
                        "cpus": 0.5,
                        "mem": 128,
                        "instances": 1,
                        "constraints": [
                                ["hostname", "CLUSTER", "mslave2"]
                        ],
                        "container": {
                                "type": "DOCKER",
                                "volumes": [],
                                "docker": {
                                        "image": "akamalov/docker-etcd:3.0.15",
                                        "network": "HOST",
                                        "portmappings": [{
                                                "containerPort": 2380,
                                                "hostPort": 33380,
                                                "protocol": "tcp"
                                        }, {
                                                "containerPort": 2379,
                                                "hostPort": 33379,
                                                "protocol": "tcp"
                                        }],
                                        "privileged": false,
                                        "parameters": [{
                                                "key": "hostname",
                                                "value": "etcd2.sdncluster1.etcdhost.marathon.mesos"
                                        }],
                                        "forcePullImage": false
                                }
                        },
                        "args": [
                                "--name etcd2.sdncluster1.etcdhost.marathon.mesos",
                                "--initial-cluster etcd1.sdncluster1.etcdhost.marathon.mesos=http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380,etcd2.sdncluster1.etcdhost.marathon.mesos=http://etcd2.sdncluster1.etcdhost.marathon.mesos:2380,etcd3.sdncluster1.etcdhost.marathon.mesos=http://etcd3.sdncluster1.etcdhost.marathon.mesos:2380","-initial-cluster-token mesos-cluster",
                                "--initial-advertise-peer-urls http://etcd2.sdncluster1.etcdhost.marathon.mesos:2380",
                                "--advertise-client-urls http://etcd2.sdncluster1.etcdhost.marathon.mesos:2379",
                                "--initial-cluster-state new",
                                "--heartbeat-interval 500",
                                "--election-timeout 2500"
                        ]
                }, {
                        "id": "etcd3",
                        "cpus": 0.5,
                        "mem": 128,
                        "instances": 1,
                        "constraints": [
                                ["hostname", "CLUSTER", "mslave3"]
                        ],
                        "container": {
                                "type": "DOCKER",
                                "volumes": [],
                                "docker": {
                                        "image": "akamalov/docker-etcd:3.0.15",
                                        "network": "HOST",
                                        "portmappings": [{
                                                "containerPort": 2380,
                                                "hostPort": 33380,
                                                "protocol": "tcp"
                                        }, {
                                                "containerPort": 2379,
                                                "hostPort": 33379,
                                                "protocol": "tcp"
                                        }],
                                        "privileged": false,
                                        "parameters": [{
                                                "key": "hostname",
                                                "value": "etcd3.sdncluster1.etcdhost.marathon.mesos"
                                        }],
                                        "forcePullImage": false
                                }
                        },
                        "args": [
                                "--name etcd3.sdncluster1.etcdhost.marathon.mesos",
                                "--initial-cluster etcd1.sdncluster1.etcdhost.marathon.mesos=http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380,etcd2.sdncluster1.etcdhost.marathon.mesos=http://etcd2.sdncluster1.etcdhost.marathon.mesos:2380,etcd3.sdncluster1.etcdhost.marathon.mesos=http://etcd3.sdncluster1.etcdhost.marathon.mesos:2380","-initial-cluster-token mesos-cluster",
                                "--initial-advertise-peer-urls http://etcd3.sdncluster1.etcdhost.marathon.mesos:2380",
                                "--advertise-client-urls http://etcd3.sdncluster1.etcdhost.marathon.mesos:2379",
                                "--initial-cluster-state new",
                                "--heartbeat-interval 500",
                                "--election-timeout 2500"
                        ]
                }]
        }]
}

ETCD errors on container complaining about host resolution:
[root@mslave1 executors]# docker logs 8f
Using default CLIENT_URLS (http://<IP_ADDRESS>:4001,http://<IP_ADDRESS>:2379)
Using default PEER_URLS (http://<IP_ADDRESS>:7001,http://<IP_ADDRESS>:2380)
Running '/bin/etcd -data-dir=/data -listen-peer-urls=http://<IP_ADDRESS>:7001,http://<IP_ADDRESS>:2380 -listen-client-urls=http://<IP_ADDRESS>:4001,http://<IP_ADDRESS>:2379 --name etcd1.sdncluster1.etcdhost.marathon.mesos --initial-cluster etcd1.sdncluster1.etcdhost.marathon.mesos=http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380,etcd2.sdncluster1.etcdhost.marathon.mesos=http://etcd2.sdncluster1.etcdhost.marathon.mesos:2380,etcd3.sdncluster1.etcdhost.marathon.mesos=http://etcd3.sdncluster1.etcdhost.marathon.mesos:2380 -initial-cluster-token mesos-cluster --initial-advertise-peer-urls http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380 --advertise-client-urls http://etcd1.sdncluster1.etcdhost.marathon.mesos:2379 --initial-cluster-state new --heartbeat-interval 500 --election-timeout 2500'
BEGIN ETCD OUTPUT

2016-12-06 15:37:33.994580 I | etcdmain: etcd Version: 3.0.15
2016-12-06 15:37:33.994776 I | etcdmain: Git SHA: fc00305
2016-12-06 15:37:33.994793 I | etcdmain: Go Version: go1.6.3
2016-12-06 15:37:33.994806 I | etcdmain: Go OS/Arch: linux/amd64
2016-12-06 15:37:33.994825 I | etcdmain: setting maximum number of CPUs to 8, total number of available CPUs is 8
2016-12-06 15:37:33.995191 I | etcdmain: listening for peers on http://<IP_ADDRESS>:2380
2016-12-06 15:37:33.995268 I | etcdmain: listening for peers on http://<IP_ADDRESS>:7001
2016-12-06 15:37:33.995372 I | etcdmain: listening for client requests on <IP_ADDRESS>:2379
2016-12-06 15:37:33.995426 I | etcdmain: listening for client requests on <IP_ADDRESS>:4001
2016-12-06 15:37:34.225432 E | netutil: could not resolve host etcd1.sdncluster1.etcdhost.marathon.mesos:2380
2016-12-06 15:37:34.239653 I | etcdmain: stopping listening for client requests on <IP_ADDRESS>:4001
2016-12-06 15:37:34.239738 I | etcdmain: stopping listening for client requests on <IP_ADDRESS>:4001
2016-12-06 15:37:34.239771 I | etcdmain: stopping listening for peers on http://<IP_ADDRESS>:7001
2016-12-06 15:37:34.239799 I | etcdmain: stopping listening for peers on http://<IP_ADDRESS>:2380
2016-12-06 15:37:34.239830 I | etcdmain: --initial-cluster must include etcd1.sdncluster1.etcdhost.marathon.mesos=http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380 given --initial-advertise-peer-urls=http://etcd1.sdncluster1.etcdhost.marathon.mesos:2380
[root@mslave1 executors]#

For some reason, ```netutil`` is not being able to resolve the host provided:
2016-12-06 15:37:34.225432 E | netutil: could not resolve host etcd1.sdncluster1.etcdhost.marathon.mesos:2380

DNS is provided by Mesos-DNS and container coming online registers with Mesos-DNS which makes the container resolvable. For example, zookeeper was deployed in the same fashion:
[root@mslave1 default]# ping -c 3 zk2.zk.kafka.marathon.mesos
PING zk2.zk.kafka.marathon.mesos (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=60 time=1.26 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=60 time=0.869 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=60 time=0.434 ms

--- zk2.zk.kafka.marathon.mesos ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.434/0.854/1.260/0.338 ms
[root@mslave1 default]#

Again, 2.0.10 I've deployed, works fine. It's 3.0.x I am having a problem with.
Any pointers ?
Thanks,
Alex

Maybe related to https://github.com/coreos/etcd/pull/6365
/cc @heyitsanthony ?

@gyuho unlikely; that was turned into a warning for 3.0.9.

DNS is provided by Mesos-DNS and container coming online registers with Mesos-DNS which makes the container resolvable.

So the address isn't expected to resolve until after etcd boots? If so, that sounds similar to #6262

Thanks @heyitsanthony . I can see that a user disabled DNS healthcheck. Was it done as a parameter to ETCD ?? Where was it disabled, do you know by chance?

It looks like the symptom is exactly the same as in #6262. So, the container has to be fully up, and  only then Mesos-DNS get it registered. Wondering if there is some type of a delay or retry can be used with ETCD so it can re-try the operation (just like ZooKeeper does) after a period of time? It did work like a champ on 2.x releases, but 3.x  it no longer work with Marathon/Mesos with dynamic IP addresses. Also, we cannot use IP addresses and then to cluster update, because IP addresses are dynamically provided by SDN.
Thanks again,
Alex

I got this problem in v3.0.15, too.

Did it the merge make it to 3.0.16 ?

@akamalov it wasn't backported to 3.0.x since it's a change in behavior which isn't exactly a bug fix.

Thanks @heyitsanthony. I tried to test https://github.com/coreos/etcd/issues/7008 (via Marathon), but deployment is exiting complaining at flags provided
Here is the Marathon JSON file I used to deploy:
{
        "id": "/etcd-host",
        "groups": [{

                "id": "/etcd-host/sdncluster1",
                "apps": [{
                        "id": "etcd1",
                        "cpus": 0.5,
                        "mem": 128,
                        "instances": 1,
                        "constraints": [
                                ["hostname", "CLUSTER", "mslave1"]
                        ],
                        "container": {
                                "type": "DOCKER",
                                "volumes": [],
                                "docker": {
                                        "image": "akamalov/etcd-docker:3.1.7008",
                                        "network": "HOST",
                                        "portmappings": [{
                                                "containerPort": 2380,
                                                "hostPort": 22380,
                                                "protocol": "tcp"
                                        }, {
                                                "containerPort": 2379,
                                                "hostPort": 22379,
                                                "protocol": "tcp"
                                        }],
                                        "privileged": false,
                                        "parameters": [{
                                                "key": "hostname",
                                                "value": "etcd1.sdncluster1.etcd-host.marathon.mesos"
                                       }, {
                                                "key": "userns",
                                                "value": "host"
                                        }],
                                        "forcePullImage": false
                                }
                        },
                        "args": [
                                "--advertise-client-urls http://etcd1.sdncluster1.etcd-host.marathon.mesos:2379",
                                "--initial-cluster-state new",
                                "--initial-cluster-token etcd-cluster1",
                                "--initial-cluster etcd1.sdncluster1.etcd-host.marathon.mesos=http://etcd1.sdncluster1.etcd-host.marathon.mesos:2380,etcd2.sdncluster1.etcd-host.marathon.mesos=http://etcd2.sdncluster1.etcd-host.marathon.mesos:2380,etcd3.sdncluster1.etcd-host.marathon.mesos=http://etcd3.sdncluster1.etcd-host.marathon.mesos:2380",
                                "--initial-advertise-peer-urls http://etcd1.sdncluster1.etcd-host.marathon.mesos:2380"
                        ]
                }, {
                        "id": "etcd2",
                        "cpus": 0.5,
                        "mem": 128,
                        "instances": 1,
                        "constraints": [
                                ["hostname", "CLUSTER", "mslave2"]
                        ],
                        "container": {
                                "type": "DOCKER",
                                "volumes": [],
                                "docker": {
                                        "image": "akamalov/etcd-docker:3.1.7008",
                                        "network": "HOST",
                                        "portmappings": [{
                                                "containerPort": 2380,
                                                "hostPort": 22380,
                                                "protocol": "tcp"
                                        }, {
                                                "containerPort": 2379,
                                                "hostPort": 22379,
                                                "protocol": "tcp"
                                        }],
                                        "privileged": false,
                                        "parameters": [{
                                                "key": "hostname",
                                                "value": "etcd2.sdncluster1.etcd-host.marathon.mesos"
                                       }, {
                                                "key": "userns",
                                                "value": "host"
                                        }],
                                        "forcePullImage": false
                                }
                        },
                        "args": [
                                "--advertise-client-urls http://etcd2.sdncluster1.etcd-host.marathon.mesos:2379",
                                "--initial-cluster-token etcd-cluster1",
                                "--initial-cluster-state new",
                                "--initial-cluster etcd1.sdncluster1.etcd-host.marathon.mesos=http://etcd1.sdncluster1.etcd-host.marathon.mesos:2380,etcd2.sdncluster1.etcd-host.marathon.mesos=http://etcd2.sdncluster1.etcd-host.marathon.mesos:2380,etcd3.sdncluster1.etcd-host.marathon.mesos=http://etcd3.sdncluster1.etcd-host.marathon.mesos:2380",
                                "--initial-advertise-peer-urls http://etcd2.sdncluster1.etcd-host.marathon.mesos:2380"
                        ]
                }, {
                        "id": "etcd3",
                        "cpus": 0.5,
                        "mem": 128,
                        "instances": 1,
                        "constraints": [
                                ["hostname", "CLUSTER", "mslave3"]
                        ],
                        "container": {
                                "type": "DOCKER",
                                "volumes": [],
                                "docker": {
                                        "image": "akamalov/etcd-docker:3.1.7008",
                                        "network": "HOST",
                                        "portmappings": [{
                                                "containerPort": 2380,
                                                "hostPort": 22380,
                                                "protocol": "tcp"
                                        }, {
                                                "containerPort": 2379,
                                                "hostPort": 22379,
                                                "protocol": "tcp"
                                        }],
                                        "privileged": false,
                                        "parameters": [{
                                                "key": "hostname",
                                                "value": "etcd3.sdncluster1.etcd-host.marathon.mesos"
                                       }, {
                                                "key": "userns",
                                                "value": "host"
                                        }],
                                        "forcePullImage": false
                                }
                        },
                        "args": [
                                "--advertise-client-urls http://etcd3.sdncluster1.etcd-host.marathon.mesos:2379",
                                "--initial-cluster-token etcd-cluster1",
                                "--initial-cluster-state new",
                                "--initial-cluster etcd1.sdncluster1.etcd-host.marathon.mesos=http://etcd1.sdncluster1.etcd-host.marathon.mesos:2380,etcd2.sdncluster1.etcd-host.marathon.mesos=http://etcd2.sdncluster1.etcd-host.marathon.mesos:2380,etcd3.sdncluster1.etcd-host.marathon.mesos=http://etcd3.sdncluster1.etcd-host.marathon.mesos:2380",
                                "--initial-advertise-peer-urls http://etcd3.sdncluster1.etcd-host.marathon.mesos:2380"
                        ]
                }]
        }]
}

Here is the error:
[root@mslave1 executors]# docker ps -a
CONTAINER ID        IMAGE                           COMMAND                  CREATED             STATUS                      PORTS               NAMES
760788b1bdc4        akamalov/etcd-docker:3.1.7008   "etcd '--advertise-cl"   5 seconds ago       Exited (2) 3 seconds ago                        mesos-d4a8dbc6-4b76-46d4-9fe9-8c93014e2008-S1.16e1f6ed-b897-40fb-b9c2-fb80883a38fd
fdcc2ce4f69a        akamalov/etcd-docker:3.1.7008   "etcd '--advertise-cl"   10 seconds ago      Exited (2) 7 seconds ago                        mesos-d4a8dbc6-4b76-46d4-9fe9-8c93014e2008-S1.df019344-ef85-479a-b8bd-5a676d443d77

[root@mslave1 executors]# docker logs 76
flag provided but not defined: -advertise-client-urls http://etcd1.sdncluster1.etcd-host.marathon.mesos:2379
usage: etcd [flags]
       start an etcd server

       etcd --version
       show the version of etcd

       etcd -h | --help
       show the help information about etcd

       etcd --config-file
       path to the server configuration file

[root@mslave1 executors]#

@akamalov Will args automatically split into separate arguments on spaces? It seems like:
"args": [
    "--advertise-client-urls http://etcd1.sdncluster1.etcd-host.marathon.mesos:2379",
    ...
]

should be:
"args": [
    "--advertise-client-urls",
    "http://etcd1.sdncluster1.etcd-host.marathon.mesos:2379",
    ...
]

Otherwise the string will be treated as one argv string instead of two.
It's the difference between:
[anthony@etcd]$ ./bin/etcd "-advertise-client-urls http://etcd1.sdncluster1.etcd-host.marathon.mesos:2379"
flag provided but not defined: -advertise-client-urls http://etcd1.sdncluster1.etcd-host.marathon.mesos:2379
usage: etcd [flags]
       start an etcd server

and
[anthony@etcd]$ ./bin/etcd -advertise-client-urls http://etcd1.sdncluster1.etcd-host.marathon.mesos:2379
2017-01-18 14:28:14.201116 I | etcdmain: etcd Version: 3.1.0-rc.1+git
2017-01-18 14:28:14.201216 I | etcdmain: Git SHA: 1613516
2017-01-18 14:28:14.201219 I | etcdmain: Go Version: go1.7.3
...


e2e: allow amzn2 for worker nodes

What this PR does / why we need it:
Terraform configs for AWS use amzn, while machine-controller uses amzn2. We need to make sure both are considered valid by our E2E tests.
Does this PR introduce a user-facing change?:
NONE

/lgtm


tomcat background process is needed to cleanup sessions

With background-processor-delay=0s, tomcat background process is disabled. All org.apache.catalina.session.StandardSession objects are kept in memory, resulting in a small but steady increase in memory usage, ending in OutOfMemory after some time (one month in our case)
NB: it only impacts spring-boot embedded tomcat.

What objects are kept in memory?

The following objects are kept in memory:
org.apache.catalina.session.StandardSessionFacade
org.apache.catalina.session.StandardSession

and some deps (?)
java.beans.PropertyChangeSupport
java.beans.PropertyChangeSupport$PropertyChangeListenerMap
java.util.concurrent.ConcurrentHashMap
java.util.concurrent.ConcurrentHashMap$Node
java.util.ArrayList
java.lang.String

Issue detected by comparing the output of jmap -histo over time.
Currently we have 1_441_274 StandardSession in memory.
The culprit seems to be https://github.com/apereo/cas/commit/22f379c1d32c843ef1fe31e5e7cf59b00f94ff7c#diff-e3b0b12fd1ad90ae3a49bf9815f407dc4a59f555f19b89e1f527899e94c74b59R29

@dima767 can you please review this? I remember a while ago you discovered performance issues with the background thread here, do I have that right?

My memory vaguely tells me it was something about slow start up times, but unfortunately I cannot find anything concrete. Perhaps could have been a "band-aid". I'll search some more

Hi @dima767 did you find anything relevant? Safe to proceed with this PR?

Unfortunately nothing at all has been found. I think it’s safe to proceed. Thanks

Unfortunately it seems that maybe that wasn't documented anywhere but it wasn't safe to proceed as this definitely has a significant performance impact both during the first page load and each time validating authentication for a saml endpoint (like Google).
I was experiencing a consistent 8-10 second delay during my authentication attempts for Google.  Those disappeared completely upon restoring the setting.
Can we have this commit reverted?

I would like to arrive at a situation where this goes beyond just hearsay and anecdotal evidence, but instead the reversal, if necessary, is based on concrete, automated, reproducible tests. We can never be sure if this is an issue with your environment, your setup, etc in the way the report is presented. You're welcome to provide reproducers and evidence in a clean environment (a docker container perhaps with test scripts that measure CAS performance with and without this change) then we can take a look and possibly then decide to reverse with enough data, barring other issues such as OOM problems mentioned originally.

Hmm.  Seems like a double standard.
This was not done when this change in the PR was initiated even though there was a recollection of performance issues that might be caused.  Yet when I raise the fact that performance issues have been encountered (I saw them with a vanilla, minimal setup in both the 6.6.x and master branches), now you want concrete, automated and reproducible tests?
Based on the way you have worded your response I cannot tell if I put the time and effort into providing such proof of this issue whether that would lead to the change would be reverted since I can counter that one person has experienced an OOM issue.
Regardless, it seems like this is not a good fix for this one OOM issue if it also causes a huge performance hit for others.

This was not done when this change in the PR was initiated even though there was a recollection of performance issues that might be caused. Yet when I raise the fact that performance issues have been encountered (I saw them with a vanilla, minimal setup in both the 6.6.x and master branches), now you want concrete, automated and reproducible tests?

We have had several people look into this, and none so far have been able to conclusively determine that this change is the culprit. It may be in the end, but we will not make the change without proof. We have consulted internally with other devs and clients and none so far have reported the same. The "performance issues" that you raise so far seem anecdotal and there is no evidence to assume otherwise. The original reporter was kind enough to provide details, data and a reasonable thread-dump for us to make a reasonable assessment. Even if all of that was the result of careless evaluations and assumptions and a reckless process, it does not mean that we would repeat that same process. Even if any change was originally put in with zero tests and assertions for whatever reason, we will not follow that same approach going forward. "X didn't do it, so why should I" won't help your cause here. "X didn't do it, but I will help make it better" is something we'd like to see.

Based on the way you have worded your response I cannot tell if I put the time and effort into providing such proof of this issue whether that would lead to the change would be reverted since I can counter that one person has experienced an OOM issue.

Maybe. Maybe not. Depends on what you put together, how reasonable that data is, and whether is time, interest and energy to evaluate it. There are zero expectations.

Thanks Misagh.  I see where you are coming from and that is fair.  I can't make this a priority to submit anything at this time since I do have a working "fix" for our systems but I will add it to my to do list and can respond back when I can.
When I do respond back should I add the information to this PR or should I open a new PR to revert the change and then include the proof information with that new PR?

I appreciate your time and the effort here and I am glad this is not a showstopper for you. Whenever you find the chance to look into this more deeply is always welcome so long as the release line continues to remain in maintenance. I know Jérôme and Hal are also looking into this as we speak, so we might be able to find something in the meanwhile.
If and when you get to this, you're most welcome to submit your changes, findings, tests etc here on this very same thread. All maintainers watch and review all comments and activity and we'll get back to you at some point. The only exception there might be if your tests are in fact based on Puppeteer, in which case we would like to see a separate PR.
If we do end up reversing this, I would then also ask for a PR from you so that the change is visibly public in the commit log and credit is given where it's due.

I also have a customer who has encountered a "strong slowness" when upgrading to CAS v6.6.11 and who has fixed the problem by restoring this setting.
Thus, I'm trying to demonstrate the performance issue but yet, I haven't been able to show radical slowness even if I use a "vanilla, minimal setup" CAS server with SAML server support (like my customer does).
@wdouglascampbell When you say: "I was experiencing a consistent 8-10 second delay during my authentication attempts for Google", do you mean authn delegation or SAML server support? What CAS modules do you use?
So far, my tests only show that restoring this setting for CAS v6.6.11 makes it around 30% faster.

@leleuj I have setup CAS as a SAML2 IdP for Google.  I'm using the cas-server-support-saml-idp module.  My setup should match what I posted to the mailing list awhile back at the following link.

Thanks. I have a similar setup using the cas-server-support-saml-idp module and another SP client but I don't see any noticable (humain viewable) performance issue between 6.6.10 and 6.6.11 as you do. Only v6.613 shows slowness because of the embedded Tomcat v9.0.81.
This is really strange! I can only argue for a concrete, automated, reproducible test.

Yes.  This is strange.  I went back and used 6.6.11 to test and I still see noticeable slowing of around 7 seconds each time I attempt to provide authentication for Google using the cas-server-support-saml-idp module.  The only additional thing that might be different between our two setups is that I am using the cas-server-support-ldap module to check credentials against an Active Directory server.  However for another site uses this CAS server for authentication but doesn't rely on the cas-server-support-saml-idp module but checks the credentials against the AD server I don't see this noticeable delay.

I had the same issue. It seems that setting a larger value also works (i'm not sure why):

server.tomcat.background-processor-delay=111s


new hidden bug

I found bug in NyStorage:
Sometime on old phones have an error
 NyStorage.read at line 200 within nylo_support
PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT
	at com.android.org.conscrypt.NativeCrypto.EVP_CipherFinal_ex(Native Method)
	at com.android.org.conscrypt.OpenSSLCipher$EVP_CIPHER.doFinalInternal(OpenSSLCipher.java:596)
	at com.android.org.conscrypt.OpenSSLCipher.engineDoFinal(OpenSSLCipher.java:363)

I think better choice use try-catch in the core:  in String? data = await StorageManager.storage.read(key: key);
Will wait new update

Hi @andim27,
Hope you are well, thanks for reporting this.
I've done a bit of digging online and it appears related to the below issues:
https://github.com/mogol/flutter_secure_storage/issues/210
https://github.com/BitCodersNN/unn-mobile/issues/224
This appears to be the solution: https://github.com/mogol/flutter_secure_storage/issues/43#issuecomment-471642126
<application
    ...
        android:allowBackup="false"
        android:fullBackupContent="false">

I've updated Nylo in this commit to fix it https://github.com/nylo-core/nylo/commit/2be2d5bb3e17ce1a19345999cfe4bacf3a97f620 👍


Code intelligent didn't display as markdown content for param comment.

Code intelligent doesn't display as markdown content for param comment.

VSCode Version: 1.12.2
OS Version: Ubuntu 17.04

dupe of #11877


Qbraid - Implementing Improved Multiple Controlled Toffoli

Team members: Filo#0228, AdamF#3239, theLazyOrion#1469, Minh Pham#1953, Peláez#7443.


explorerResourceIsFolder combine with listDoubleSelection

Currently following when clause explorerResourceIsFolder && listDoubleSelection is true when the user choose a file and then a folder (unlike the vice-versa)
My propose it to add clauses such as allSelectionIsFolder, allSelectionIsFile etc.

This is a fair feature request, however those context keys are designed for internal use and we would not change anything there at the moment.
However leaving this request open as we might tackle it in the future.

Thanks for the reply.
Maybe not to change but to add?


add helper function for line numbers

Summary:
Code like this is repeated everywhere in the generator:
generate_indent(indent, o);
o << "current_statement_begin__ = " <<  vs[i].begin_line_ << ";"
          << EOL;

and should be replaced with:
generate_statement_begin(indent, vs[i], o);

Current Version:
v2.18.0

Superseded by stanc3.


feat: Add different kinds of tag

Description
Zeplin: https://zpl.io/g8KLE9R
Fixes https://github.com/appsmithorg/appsmith/issues/19535
Depends on main repo PR, https://github.com/appsmithorg/design-system/pull/536
Type of change

New feature (non-breaking change which adds functionality)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Manual on storybook
Manual on main repo
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] 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

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/generate-alpha

generated alpha: 0.0.0-alpha-20230801084224

/generate-alpha

/generate-alpha

As informed checked the color of each tag components
Observation:
Special tag: Expected color: #4a2185 Actual color: #401D73
Other than Special tag all the colors mentioned are as expected. Moving to Inprogress @tanvibhakta CC: @rohitagarwal88

@shadabbuchh @Sripriya93 Please check this link for the Tag component's new colours to test. Meanwhile, I will delete all the projects which are not meant for the Engg and QA.
Zeplin: https://zpl.io/g8KLE9R

As informed checked only the color of each tag components. All the colors are as expected. Moving to done.

All tests have passed: https://github.com/appsmithorg/appsmith/pull/25804#issuecomment-1663833223


Various fixes

Fix Config file parsing. With the old behavior, only the positions of the values mattered. Keys were irrelevant.
Added handling, README, base .ini file details about EntityPath for the event hub
Applied PEP8
Moved all string concatenations/formats to Python3 format style
Removed dead code
Various refactors

@EliPinkertonMicrosoft,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


feat: get data from csv iand make it into a sqlite database

can you merge this PR

#30

!bounty 50

!bounty 40


helm upgrade doesn't work when KUBECONFIG env var contains multiple files

Output of helm version: version.BuildInfo{Version:"v3.10.2", GitCommit:"50f003e5ee8704ec937a756c646870227d7c8b58", GitTreeState:"clean", GoVersion:"go1.18.8"}
Output of kubectl version: Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.13", GitCommit:"592eca05be27f7d927d0b25cbb4241d75a9574bf", GitTreeState:"clean", BuildDate:"2022-10-14T00:11:57Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): K8s
When running helm upgrade, with KUBECONFIG env var pointing to the .kubeconfig context file list (':' delemited) the command fails if the KUBECONFIG contains multiple files and not a single file.
fails on auth to the cluster cause it's always taking the wrong file
Error: Kubernetes cluster unreachable: Get "https://wdatp-k8s-stg-eus2-3.eastus2.cloudapp.azure.com/version": failed to refresh token: oauth2: cannot fetch token: 400 Bad Request
Response: {"error":"invalid_grant","error_description":"AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2021-02-08T08:37:03.6859975Z and was inactive for 90.00:00:00.\r\nTrace ID: c11a0692-d210-4436-a5ee-6a533d7ec200\r\nCorrelation ID: cfe30e73-ac35-4093-a2d3-30df46d7c903\r\nTimestamp: 2022-11-29 10:10:36Z","error_codes":[700082],"timestamp":"2022-11-29 10:10:36Z","trace_id":"c11a0692-d210-4436-a5ee-6a533d7ec200","correlation_id":"cfe30e73-ac35-4093-a2d3-30df46d7c903","error_uri":"https://login.microsoftonline.com/error?code=700082"}

@orle Does kubectl work any differently?

@joejulian doesn't seem like it's kubectl related. It's most likely an helm3 related issue.
The issue can be mitigated by:

setting a single path in KUBECONFIG env var
using a single file as in /.kube/.kubeconfig
using --kubeconfig /path/to/kubeconfig/file in the helm upgrade command

helm3 should definitely continue to support multiple helm paths in KUBECONFIG env var in my opinion.

Sure, my question is about whether the behavior between the two matches. They both use k8s.io/client-go so the behavior should be the same.

When running helm upgrade, with KUBECONFIG env var pointing to the .kubeconfig context file list (':' delemited) the command fails if the KUBECONFIG contains multiple files and not a single file.

If you reorder the files in KUBECONFIG (so the one with the expected cluster config is first), does helm still fail? I think this would tell us if indeed this is a helm issue with multiple files in KUBECONFIG.
Also, suspect in your error message is the message: The refresh token has expired due to inactivity.. The indicates helm did use the correct kubeconfig values, but creds had expired.
To @joejulian point(s), helm uses the same client-go library as kubectl to source kubeconfig values. It would be unexpected for there to be a behaviour difference here (there could be, but it would be e.g. helm's use of this library would be different).

@gjenkins8 reordering and even renaming (to be alphabetically first) doesn't help. The reason for the token error by the way is that the other kubeconfig is of a different cluster.

I've tested this. I have a KUBECONFIG with a colon delimited list of kubeconfig files. It defaulted to the first one and worked. I cannot duplicate your issue.
I'll ask again if you have the same issue if you run kubectl with the same KUBECONFIG environment variable. If you do, this is a client-go issue. If you don't, we'll need a way of duplicating the issue or there's no way of tracking it down.

Closing: cannot duplicate.

This is a problem for me too and has been for quite a while now. I'm not sure when the bug was introduced, but it's definitely not working correctly. It doesn't matter the order of the kubeconfigs listed on the env var.  It only works when I override the KUBECONFIG env var and specify a single config.
Looking at a packet capture, it appears to be sending data to the cluster, but I can't tell what happens after that.


effort_controllers/joint_position_controller from ROS1

ros1_controllers has effort_controllers/joint_position_controller that accepts position commands and targets an effort-controlled joint. But in this repo, the effort_controllers only accept group effort commands. Is it moved somewhere else or the feature is still missing?

To be more specific, I am trying to control an arm to a set joint position, but with limited torque, so that when an external force (larger than the torque limit) is present, the arm will deviate from the position (with some kind of compliant behavior). Once the external force is gone or become smaller, the arm will tend to move back to the set joint position. Basically some kind of passive motion. Back in ROS1, I can achieve such behavior with effort_controllers/joint_position_controller. I am wondering if ros2_controller has something similar to this.

This functionality is currently missing but it's fairly straight forward to
port it from ROS1. I'd happily review a PR for this
On Tue, 5 Jul 2022, 20:15 Tianyu Li, @.***> wrote:

To be more specific, I am trying to control an arm to a set joint
position, but with limited torque, so that when an external force (larger
than the torque limit) is present, the arm will deviate from the position
(with some kind of compliant behavior). Once the external force is gone or
become smaller, the arm will tend to move back to the set joint position.
Basically some kind of passive motion. Back in ROS1, I can achieve such
behavior with effort_controllers/joint_position_controller. I am wondering
if ros2_controller has something similar to this.
—
Reply to this email directly, view it on GitHub
https://github.com/ros-controls/ros2_controllers/issues/373#issuecomment-1175410184,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA24PYKEJUYLOV3YZQVUCD3VSSCWXANCNFSM52HIHHKA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@bmagyar Just realize https://github.com/ros-controls/ros2_controllers/pull/198 has the group version for this a year ago, is there a reason why it has not merged yet? Would be happy to contribute to this.

It needs revival :)

@tonylitianyu you wanted to contribute to this. Is this still the case?

@bmagyar i am trying to build the effort_controller: joint_position_controller from here, but I keep getting build errors for Humble, is there any new branch with a fix for this?

There was a sync a few days ago, if you rosdep update && rosdep install --from-path src --ignore-src, it should build fine again.

@bmagyar I tried that, but i still seem to be getting errors while building. To give you an idea of my setup:

Ubuntu 22.04
ROS2 Humble
In my home directory, ros2 workspace (ros2_ws)
I have the binary install of ros2_controls and ros2_controllers (ros-humble-ros2-control and ros-humble-ros2-controllers)
In ~/ros2_ws/src i have cloned the effort_controllers package from here

here is the error message I get while building.

Have you tried with --allow-overriding as per the error message? We
generally do not recommend having the same package you are trying to build
from source installed as binary too as ros2 seems to still have issues with
it.
On Wed, 9 Nov 2022, 20:57 Aadiv Shah, @.***> wrote:

@bmagyar https://github.com/bmagyar I tried that, but i still seem to
be getting errors while building. To give you an idea of my setup:

Ubuntu 22.04
ROS2 Humble
In my home directory, ros2 workspace (ros2_ws)
I have the binary install of ros2_controls and ros2_controllers
(ros-humble-ros2-control and ros-humble-ros2-controllers)
In ~/ros2_ws/src i have cloned the effort_controllers package from
here
https://github.com/ros-controls/ros2_controllers/tree/effort_group_position_controller/effort_controllers

here
https://drive.google.com/file/d/1OT8YuICxlYe7KYcne9Gp1ZbFrBrXBSrg/view?usp=sharing
is the error message I get while building.
—
Reply to this email directly, view it on GitHub
https://github.com/ros-controls/ros2_controllers/issues/373#issuecomment-1309288768,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA24PYKPTOVMIRPMIP34IRDWHP6ZPANCNFSM52HIHHKA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@bmagyar yes I did try, it is still giving me build issues/issues in the code itself as shown in the attached file

@bmagyar @Karsten1987 I was able to build this in my workspace(removed binary installation) but getting errors while running the Effort_Controllers/JointGroupPositionController although Effort_Controllers/JointGroupPositionController runs without error.
My system:

Ubuntu 20.04
ROS2 Foxy

Here is the error :


Grafana doesn't show metrics on GKE

Hi, since 1.6.2 Grafana stops to show metrics. My cluster is hosted on GKE an I deployed grafana + influx db using  these templates.
Version:
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"clean", BuildDate:"2017-05-19T18:44:27Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

The heapster logs show me that seems impossible to heapster reach data
I0619 10:27:39.446305       1 heapster.go:72] /heapster --source=kubernetes.summary_api:''
I0619 10:27:39.446437       1 heapster.go:73] Heapster version v1.3.0
I0619 10:27:39.446795       1 configs.go:61] Using Kubernetes client with master "https://<IP_ADDRESS>:443" and version v1
I0619 10:27:39.446820       1 configs.go:62] Using kubelet port 10255
I0619 10:27:39.449074       1 heapster.go:196] Starting with Metric Sink
I0619 10:27:39.840421       1 heapster.go:106] Starting heapster on port 8082
E0619 10:28:05.003390       1 summary.go:97] error while getting metrics summary from Kubelet gke-camonline-cluste1-default-pool-1d836b61-bmsk(<IP_ADDRESS>:10255): Get http://<IP_ADDRESS>:10255/stats/summary/: dial tcp <IP_ADDRESS>:10255: gets
ockopt: connection refused
I0619 10:28:36.640096       1 handlers.go:264] No metrics for container camonline-resource-services in pod application/dp-resource-2913000848-vmtc0
I0619 10:28:36.640176       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-vmtc0
I0619 10:28:36.640195       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-l5qn3
I0619 10:28:36.640211       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-k4s2n
I0619 10:28:36.640220       1 handlers.go:264] No metrics for container camonline-resource-services in pod application/dp-resource-2913000848-mfb08
I0619 10:28:36.640224       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-mfb08
I0619 10:28:36.640232       1 handlers.go:264] No metrics for container camonline-resource-services in pod application/dp-resource-2913000848-jjhxc
I0619 10:28:36.640346       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-jjhxc
I0619 10:28:36.640357       1 handlers.go:264] No metrics for container camonline-resource-services in pod application/dp-resource-2913000848-xq69z
I0619 10:28:36.640363       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-xq69z
I0619 10:28:36.653568       1 handlers.go:215] No metrics for pod application/dp-thumbnail-1613675317-4xhxh
I0619 10:28:36.653658       1 handlers.go:215] No metrics for pod application/dp-thumbnail-1613675317-t8nzg
I0619 10:28:36.653671       1 handlers.go:215] No metrics for pod application/dp-thumbnail-1613675317-s6m8f
I0619 10:28:37.819157       1 handlers.go:215] No metrics for pod application/dp-ws-apiservice-911263868-p2l8k
I0619 10:28:37.819203       1 handlers.go:215] No metrics for pod application/dp-ws-apiservice-911263868-jchbz
I0619 10:28:38.072872       1 handlers.go:264] No metrics for container camonline-auth-services in pod application/dp-auth-3732135627-tr0vb
I0619 10:28:38.072902       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-tr0vb
I0619 10:28:38.072912       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-0sc1k
I0619 10:28:38.072918       1 handlers.go:264] No metrics for container camonline-auth-services in pod application/dp-auth-3732135627-zz4p1
I0619 10:28:38.072921       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-zz4p1
I0619 10:28:38.072927       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-hzc73
I0619 10:28:38.072938       1 handlers.go:264] No metrics for container camonline-auth-services in pod application/dp-auth-3732135627-dj2gk
I0619 10:28:38.072941       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-dj2gk
I0619 10:28:38.228361       1 handlers.go:215] No metrics for pod application/dp-http-4243179347-x0c3b
I0619 10:28:38.228395       1 handlers.go:215] No metrics for pod application/dp-http-4243179347-k91t4
I0619 10:29:06.505526       1 handlers.go:264] No metrics for container camonline-resource-services in pod application/dp-resource-2913000848-xq69z
I0619 10:29:06.505568       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-xq69z
I0619 10:29:08.085346       1 handlers.go:264] No metrics for container camonline-auth-services in pod application/dp-auth-3732135627-dj2gk
I0619 10:29:08.085387       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-dj2gk
I0619 10:29:36.506430       1 handlers.go:264] No metrics for container camonline-resource-services in pod application/dp-resource-2913000848-xq69z
I0619 10:29:36.506454       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-xq69z
I0619 10:29:38.153225       1 handlers.go:264] No metrics for container camonline-auth-services in pod application/dp-auth-3732135627-dj2gk
I0619 10:29:38.239309       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-dj2gk
I0619 10:30:06.506140       1 handlers.go:264] No metrics for container camonline-resource-services in pod application/dp-resource-2913000848-xq69z
I0619 10:30:06.506158       1 handlers.go:215] No metrics for pod application/dp-resource-2913000848-xq69z
I0619 10:30:07.872495       1 handlers.go:215] No metrics for pod application/dp-ws-apiservice-911263868-p2l8k
I0619 10:30:08.255193       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-0sc1k
I0619 10:30:08.255232       1 handlers.go:264] No metrics for container camonline-auth-services in pod application/dp-auth-3732135627-dj2gk
I0619 10:30:08.255238       1 handlers.go:215] No metrics for pod application/dp-auth-3732135627-dj2gk
 workspace  0  vim  1  kubectl  2  ~/workspace                                                                                 2017-06-22  10:52  r2d2

Last, when I run kubectl cluster-info dump i receive this output
==== END logs for kube-system/fluentd-gcp-v2.0-6g7sh ====
==== START logs for kube-system/fluentd-gcp-v2.0-n0348 ====
==== END logs for kube-system/fluentd-gcp-v2.0-n0348 ====
==== START logs for kube-system/fluentd-gcp-v2.0-r3pk0 ====
==== END logs for kube-system/fluentd-gcp-v2.0-r3pk0 ====
==== START logs for kube-system/heapster-v1.3.0-1768742904-sq53l ====
Error from server (BadRequest): the server rejected our request for an unknown reason (get pods heapster-v1.3.0-1768742904-sq53l)

@piosz


raspihats: unmet dependency fix

Raspihats platform update, upstream fixed enum34 requirements, added smbus dependency
Related issue (if applicable): fixes #9547
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#3483
Checklist:
If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[X] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

huh, it was tricky 🔨  :)

Thanks!


Fix pipeline

:white_check_mark: Build bitcointrade-sdk-dotnet 1.0.180 completed (commit https://github.com/guibranco/bitcointrade-sdk-dotnet/commit/5284a99198 by @guibranco)


Make String#freeze spec-compliant

#217
Today I learned:
'foo'.freeze.equal?('foo'.freeze) # => true

Interesting to note that it only seems to apply to string literals and doesn't work if you set a variable first:
s = 'foo'
s.freeze.equal?('foo'.freeze) # => false

(Good thing too, because I have no idea how we'd do that with the compiler! 😅)

(Good thing too, because I have no idea how we'd do that with the compiler! 😅)

Add a hashmap with the frozen strings, in case you freeze a variable that contains a string, look the actual value up in the vector, add it if it doesn't exist, and assign the address of the StringObject from the map to the variable.
I don't think this would be very good for your performance though.

This was really easy thanks to the work in #2087. 🤗


How to export dataclass?

How to export dataclass?
             pydantic version: 1.5.1
            pydantic compiled: False
                 install path: /usr/local/lib/python3.7/site-packages/pydantic
               python version: 3.7.2 (default, Mar 27 2019, 08:41:08)  [GCC 6.3.0 20170516]
                     platform: Linux-4.19.76-linuxkit-x86_64-with-debian-9.8
     optional deps. installed: []

Is it even possible to export (to json) dataclass based object?
from pydantic.dataclasses import dataclass

@dataclass
class TestClass:
    id: int

>>> TestClass(id=1).json()
AttributeError: 'TestClass' object has no attribute 'json'

>>> TestClass(id=1).__pydantic_model__.dict()
TypeError: dict() missing 1 required positional argument: 'self'

I've read back and forth https://pydantic-docs.helpmanual.io/usage/exporting_models/ and https://pydantic-docs.helpmanual.io/usage/dataclasses/ and could not find anything about it.

dataclasses has an asdict() function which should do the trick: https://docs.python.org/3/library/dataclasses.html#dataclasses.asdict
In [1]: from pydantic.dataclasses import dataclass
   ...:
   ...: @dataclass
   ...: class TestClass:
   ...:     id: int
   ...:

In [2]: from dataclasses import asdict

In [3]: asdict(TestClass(id=1))
Out[3]: {'id': 1}

And to json directly? Why: I assume this more efficient that doing object->dict->json by myself.

the .json() method converts a pydantic model to a dict and then runs json.dumps() on it with some custom encoders (for datetimes and such). You can do the same with a dataclass like:
In [4]: from pydantic.json import pydantic_encoder

In [5]: from json import dumps

In [6]: dumps(asdict(TestClass(id=1)), default=pydantic_encoder)
Out[6]: '{"id": 1}'

@StephenBrown2  I'm looking for something like this as well. It's not the serialization that I'm most interested in, but the automatic jsonschema generation so we can have typed interfaces at the JSON api layer as well. Think of reusing the specs in a pydantic dataclass to leverage a typed API endpoint.
https://pydantic-docs.helpmanual.io/usage/schema/
If you want to do that, you have to do:
from pydantic.schema import schema
schema([TestClass])

@StephenBrown2 is pydantic using standard json library? Why not ultrajson - i thought this one is the fastest.

It is if you don't overwrite it: https://github.com/samuelcolvin/pydantic/blob/52af9162068a06eed5b84176e987a534f6d9126a/pydantic/main.py#L106-L107
as documented here: https://pydantic-docs.helpmanual.io/usage/exporting_models/#custom-json-deserialisation


while Export CSV its showing  Dateformat value

i am exporting CSV format  with  Address Column  Address Value is 02/02,after exporting its shows 02-Feb,but i am passing as a string,pls  help me...
here is the code
res += 'CASE WHEN @c->address1 =undefined THEN "" ELSE replaceHTMLCodes(@c->address1) END as [ADDRESS_LINE_1],';

var Shipping_Address={
"Address1":"8, 28 TINTO ROAD",
"Address2":"02/02"
}
pls export in csv

Are you looking at the csv from excel?


API needs more fixes

api.py classes could be more proper (?), I would also like to do more with the project.

api.py classes could be more proper (?), I would also like to do more with the project.

I can rewrite the whole thing in flask_restful

Yeah definitely

I will assign u