Question about scenario

so if I opt for manual clicks for logon/logoff, I can get this working no problem with my implicit provider. I'd like to basically say spa as a whole is blocked without authentication.
I've basically put something in place that loads the discovery doc, then tries to login. After that oauthservice .hasIdToken(), I initiate the implicitflow().
No combination of router guards and those checks will end up breaking before we present any user interface, and was wondering how people are achieving this effect. There is no user interface for unauthenticated users. I could just enforce the index.html doesnt get served it not authenticated... but seems like I should be able to achieve this here as well.
My router guard experiments resulted in weird looping between my oidc server and the opening component.

can you provide a minimal sample that shows this issue?

not really no... I  mean I think if you just took the out of the box example and said I dont want to display the main route, but rather would prefer to redirect to login page
(eg, this app and all the diff routes etc require authentication vs the login via buttons.)

I'm using yeoman generator aspnetcore-spa with angular 2, universal and Vs 2015. So to make it work, I created an Authentication service witch in the constructor is implementing the discovery file flow and I wrapped It in an isBrowser (for any angular-universal user only). Then, I provided it to my app.module provider and created a super route guard (authGuard) that check for hasValidAccessToken.
Everything was fine, untill the day I decided to regenerate the same project for Vs 2017. I got the same issue as you did, with the looping between my oidc and my angular app. After 2 days of digging, I finally have a solution for you. XD
The probleme is that the hashed part of the url is cleaned before it achieved to loadDiscoveryDocument and than call the trylogin. So as a patch, you can call the trylogin before loadDiscoveryDocument.
If like me you are calling loadUserProfile in the trylogin.onTokenReceived then you'll have to set userinfoEndpoint manually with (probably) : http..../connect/userinfo

In the upcoming version you will be able to do sth like this:
this.oauthService.tryLogin()
.then(_ => {
    if (!this.oauthService.hasValidIdToken()) {
        // No error but also no token
        this.oauthService.initImplicitFlow();
    }
    this.router.navigate(['/']);
})
.catch(_ => {
    // Error
    this.oauthService.initImplicitFlow();
})


Show/hide, no animation

This doesn't work:
{
animIn: { opacity: 'show' },
animOut: { opacity: 'hide' }
}

Wrong repo.


Regression test and OpenFAST updates

Regression Test

New failure criteria

if channelRange < 1 {
	norm = InfinityNorm
} else {
	norm = InfinityNorm / channelRange
}

Optional error plotting and results summary provided with matplotlib generated files embedded into html
Improved results output when running the regression test manually
Improved control when running the regression test manually - single case execution, generate plots without running the case (great for debugging)
Added abstraction and improved the API's to the custom python infrastructure

OpenFAST

Export unpacked binary output file
Git commit is embedded in the binary when built with CMake; VS integration is on the way
-- Including the git info in the module specific outputs is more involved since each module handles its own I/O and the I/O code is tucked into larger subroutines - saving for future work
Fix BeamDyn, BeamDyn driver, and OrcaFlex driver precision-type bugs
Replace unicode with ascii characters in output
Additional meta data is printed in the OpenFAST log:

**************************************************************************************************
 OpenFAST

 Copyright (C) 2017 National Renewable Energy Laboratory

 This program comes with ABSOLUTELY NO WARRANTY. See the "license.txt" file distributed with this
 software for details.
 **************************************************************************************************

 OpenFAST v8.17.01c-dev-dc586c7*
 Compile Info:
  - Architecture: 64 bit
  - Precision: double
 Execution Info:
  - Date: 08/28/2017
  - Time: 19:55:51-0600

 OpenFAST input file heading:
     FAST Certification Test #06: AOC 15/50 with many DOFs with gen start, loss of grid, and
     tip-brake shutdown. Many parameters are pure fiction.

 Running ElastoDyn.
 Running AeroDyn14.
 Running InflowWind.
 Running ServoDyn.
  Timestep: 0 of 35 seconds.

TO DO BEFORE MERGE

Verify on peregrine & windows
Update r-test baseline solutions for all machine/compiler combinations
Include OpenFAST 0.1.0 - OpenFAST 1.0.0 comparison
Update the versions for glue codes and modules

@michaelasprague that will be a document listing the test cases that failed the regression test, documenting some of the major differences in solutions, and listing the procedure used for the regression test. This is very similar to the document I've prepared (though not yet fully shared) on the FAST v8 - OpenFAST 0.1.0 comparison.


Reworking the web UI

Building out a real list of local packages, fixes #93

TODO:

[x] Search
[ ] Group multiple versions together
[ ] Clickable packages

Gif of search in action:

Slow progress but I now have the beginning of an individual package view, this needs to at least show a list of versions and some links out to github, registry etc
In future it could show the readme as well.

Individual package page is coming along nicely

More functions to add to the UI:

[ ] download a version
[ ] update a package

And some ideas for later:

[ ] add a package
[ ] export
[ ] view config
[ ] edit config
[ ] manage keys
[ ] view peers


README: Use only SVG badges

This PR changes the build badges to SVG for sharper readability ✨
Goal
For a uniform look
Approach

Edit in-place. Preview rendered result.

Coverage decreased (-27.2%) to 72.84% when pulling e3459dabadf0a9ef1b86f3758a298e42c8d355f8 on olleolleolle:patch-2 into e7ad59d432ebd76087707fc2bf7e439095e4a6f6 on ivanoblomov:master.


Add readAll and internal data access to memory session

Title says it all. Requested in https://t.me/grammyjs_ru/101

It looks cool.
In the same discussion, we had the idea of adding a method to get all the sessions. Can we add this in the same PR?

Yes, we can add that.
I'm also thinking about allowing
for await (const data of ctx.session) {
  // handle session data of user
}

which would effectively allow you to enumerate all sessions.
This would be optional to implement for storage adapters. Hence, it is a non-breaking change. Storage adapters that do not support this will simply throw an error when this is attempted.

@Satont please review.

Looking good, thank you. 👍

Taking that as an accepted review, merging.


chore(deps): update dependency jest to v27.4.7

This PR contains the following updates:

Package
Type
Update
Change

jest (source)
devDependencies
minor
27.0.6 -> 27.4.7

@types/jest
devDependencies
minor
27.0.1 -> 27.4.0

Release Notes

facebook/jest
v27.4.7
Compare Source
Fixes

jest-config Add missing @babel/core dependency (#12216)

v27.4.6
Compare Source
Fixes

[jest-environment-node] Add AbortSignal (#12157)
[jest-environment-node] Add Missing node global performance (#12002)
[jest-runtime] Handle missing mocked property (#12213)
[@jest/transform] Update dependency package pirates to 4.0.4 (#12002)

Performance

jest-config perf: only register ts-node once when loading TS config files (#12160)

v27.4.5
Compare Source
Fixes

[jest-worker] Stop explicitly passing process.env (#12141)

v27.4.4
Compare Source
Fixes

[babel-jest] Add process.version chunk to the cache key (#12122)
[jest-environment] Add mocked to jest object (#12133)
[jest-worker] Stop explicitly passing execArgv (#12128)

Chore & Maintenance

[website] Fix the card front that looks overlapping part of the card back

v27.4.3
Compare Source
Fixes

[jest-environment-jsdom] Remove @types/jsdom dependency (and make its dom property private) (#12107)

v27.4.2
Compare Source
Fixes

[jest-worker] Add additional execArgv to filter (#12103)

v27.4.1
Compare Source
Fixes

[jest-worker] Filter execArgv correctly (#12097)

v27.4.0
Compare Source
Features

[expect] Enhancing the toHaveProperty matcher to support array selection (#12092)
[jest-core] Add support for testResultsProcessor written in ESM (#12006)
[jest-diff, pretty-format] Add compareKeys option for custom sorting of object keys (#11992)
[jest-mock] Add ts-jest mock util functions (#12089)

Fixes

[expect] Allow again expect.Matchers generic with single value (#11986)
[jest-circus, jest-jasmine2] Avoid false concurrent test failures due to unhandled promise rejections (#11987)
[jest-config] Add missing slash dependency to package.json (#12080)
[jest-core] Incorrect detection of open ZLIB handles (#12022)
[jest-diff] Break dependency cycle (#10818)
[jest-environment-jsdom] Add @types/jsdom dependency (#11999)
[jest-environment-jsdom] Do not reset the global.document too early on teardown (#11871)
[jest-transform] Improve error and warning messages (#11998)
[jest-worker] Pass execArgv correctly to worker_threads worker (#12069)

Chore & Maintenance

[docs] CLI options alphabetized (#11586)
[jest-runner] Add info regarding timers to forcedExit message(#12083)
[*] Replaced substr method with substring (#12066)
[*] Add types entry to all export maps (#12073)

v27.3.1
Compare Source
Fixes

[expect] Make expect extension properties configurable (#11978)
[expect] Fix .any() checks on primitive wrapper classes (#11976)

Chore & Maintenance

[expect] BigInt global is always defined, don't check for its existence at runtime (#11979)
[jest-config, jest-util] Use ci-info instead of is-ci to detect CI environment (#11973)

v27.3.0
Compare Source
Features

[jest-config] Add testEnvironmentOptions.html to apply to jsdom input (#11950)
[jest-resolver] Support default export (.) in exports field if main is missing (#11919)

Fixes

[expect] Tweak and improve types (#11949)
[jest-runtime] Ensure absolute paths can be resolved within test modules (#11943)
[jest-runtime] Fix instanceof for ModernFakeTimers and LegacyFakeTimers methods (#11946)

v27.2.5
Compare Source
Features

[jest-config] Warn when multiple Jest configs are located (#11922)

Fixes

[expect] Pass matcher context to asymmetric matchers (#11926 & #11930)
[expect] Improve TypeScript types (#11931)
[expect] Improve typings of toThrow() and toThrowError() matchers (#11929)
[jest-cli] Improve --help printout by removing defunct --browser option (#11914)
[jest-haste-map] Use distinct cache paths for different values of computeDependencies (#11916)
[@jest/reporters] Do not buffer console.logs when using verbose reporter (#11054)

Chore & Maintenance

[expect] Export default matchers (#11932)
[@jest/types] Mark deprecated configuration options as @deprecated (#11913)

v27.2.4
Compare Source
Features

[expect] Add equality checks for Array Buffers in expect.ToStrictEqual() (#11805)

Fixes

[jest-snapshot] Correctly indent inline snapshots (#11560)

v27.2.3
Compare Source
Features

[@jest/fake-timers] Update @sinonjs/fake-timers to v8 (#11879)

Fixes

[jest-config] Parse testEnvironmentOptions if received from CLI (#11902)
[jest-reporters] Call destroy on v8-to-istanbul converters to free memory (#11896)

v27.2.2
Compare Source
Fixes

[jest-runtime] Correct wrapperLength value for ESM modules. (#11893)

v27.2.1
Compare Source
Features

[jest-transform] Improve the unexpected token error message. (#11807)

Fixes

[jest-runtime] Fix regression when using jest.isolateModules and mocks (#11882)
[jest-runtime] Include test name when importing modules after test has completed (#11885)
[jest-runtime] Error when ESM import is used after test is torn down (#11885)

v27.2.0
Compare Source
Features

[jest-resolver, jest-runtime] Pass conditions to custom resolvers to enable them to implement support for package.json exports field (#11859)
[jest-runtime] Allow custom envs to specify exportConditions which is passed together with Jest's own conditions to custom resolvers (#11863)

Fixes

[@jest/reporters] Use async transform if available to transform files with no coverage (#11852)
[jest-util] Return correct value from process.send stub (#11799)

v27.1.1
Compare Source
Features

[jest-runtime] Add experimental, limited (and undocumented) support for mocking ECMAScript Modules (#11818)

Fixes

[jest-resolver] Support node: prefix when importing Node core modules with ESM (#11817)
[jest-types] Export the PrettyFormatOptions interface (#11801)

v27.1.0
Compare Source
Features

[jest-haste-map] Use watchman suffix-set option for faster file indexing. (#11784)
[jest-cli] Adds a new config options snapshotFormat which offers a way to override any of the formatting settings which come with pretty-format. (#11654)
[jest-reporters] Expose the getSummary util (#11695).
[jest-resolver] Support node: prefix when importing Node core modules (#11331)

Fixes

[jest-each] Relaxed the validation to allow multibyte characters in headings (#11575)
[jest-environment-jsdom] Add support for userAgent option (#11773)
[jest-environment-node] Add Event and EventTarget to node global environment. (#11727)
[jest-mock] Fix spyOn to use Object.prototype.hasOwnProperty (#11721)
[jest-resolver] Add dependency on jest-haste-map (#11759)
[jest-types] Compat with @types/node v16 (#11645)

Chore & Maintenance

[docs] Correct expects.assertions documentation by adding async/await for asynchronous function.

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

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

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (27.4.7). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Issue with react-native-0.15.0

Hi, there,
As of 0.15.0, the signature of RCTEventDispatcher sendTextEventWithType has changed. See this commit.
As a workaround, I have modified RNSearchBar.m to pass a key of nil, as you aren't listening for the onKeyPress event, and this has got things working for me. But, if you want to implement this in the future, you might need to send back the text events being sent from UISearchBar.

Would you mind putting up a PR for this?

Sure. Leave it with me.
On Wed, 2 Dec 2015 at 3:57 AM, Alex Rothberg<EMAIL_ADDRESS>wrote:

Would you mind putting up a PR for this?
—
Reply to this email directly or view it on GitHub
https://github.com/umhan35/react-native-search-bar/issues/39#issuecomment-161030666
.

I PRed #45.

Thanks. :-)
On Wed, 2 Dec 2015 at 10:38 AM, Alex Rothberg<EMAIL_ADDRESS>wrote:

I PRed #45 https://github.com/umhan35/react-native-search-bar/pull/45.
—
Reply to this email directly or view it on GitHub
https://github.com/umhan35/react-native-search-bar/issues/39#issuecomment-161132349
.


re-enable full functionality of GB

Summary
Task to be done after https://github.com/umee-network/umee/issues/1402

re-enable remaining messages
re-enable slashing

This will trigger v3.1.0 release

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Missing re-enable slashing


Adding enhancement func File.SetColWidthByInt()

PR Details
Description
Allow setting column width by addressing columns by their index (index starts at 1).
Related Issue
closes #1271
Motivation and Context

Context: I have historical data that changes over time. Due to the displayed data, it makes more sense to display them horizontally.
Current downside of SetColWidth(): requires to enter strings for columns, instead of column numbers

would require a workaround like: creating a list of all columns, slicing them in chunks and iterating over them

No workaround required anymore.
How Has This Been Tested
TBD
Types of changes

[x] Docs change / refactoring / dependency upgrade
[x] New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

how should I add unit tests?
change existing unit tests to switch between both SetColWidth*() funcs?
e.g.
func TestColWidth(t *testing.T) {
	f := NewFile()
	assert.NoError(t, f.SetColWidth("Sheet1", "B", "A", 12))
	assert.NoError(t, f.SetColWidth("Sheet1", "A", "B", 12))
	…
}

becomes
func TestColWidth(t *testing.T) {
	f := NewFile()
	assert.NoError(t, f.SetColWidth("Sheet1", "B", "A", 12))
	assert.NoError(t, f.SetColWidth("Sheet1", 1, 2, 12))
	…
}

?

I applied your suggestions (though the constant is currently called TotalColumns, but I can rename it).
Though now you cannot make an assert.ErrorIs() check anymore in the tests or an errors.Is() in actual app code.

Codecov Report

Merging #1272 (3b0fcca) into master (1dbed64) will decrease coverage by 0.01%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master    #1272      +/-   ##
==========================================
- Coverage   98.45%   98.43%   -0.02%
==========================================
  Files          31       31
  Lines       23311    23331      +20
==========================================
+ Hits        22950    22967      +17
- Misses        241      243       +2
- Partials      120      121       +1

Flag
Coverage Δ

unittests
98.43% <83.33%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

stream.go
88.83% <50.00%> (-0.77%)
:arrow_down:

errors.go
100.00% <100.00%> (ø)

lib.go
98.34% <100.00%> (-0.01%)
:arrow_down:

excelize.go
99.66% <0.00%> (ø)

calc.go
98.95% <0.00%> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


added update, create sheet functionality

Resolves issue #1 and allow for updates.

Thanks again for contributing.


@silevis reactgrid excel table full width

iam using @silevis react grid excel table , i have tried many ways to achieve full width , but i unable to get the table to fit the screen , even if the excel consists two cells , could you please suggest me the approach . how to get the full width table
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
none
Screenshots or Videos (Optional)

Do you intend to try to help solve this bug with your own PR?
None
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

why was this issue opened for TanStack Table?


GEODE-6107: in test start locators one at a time

There exists a known race condition in starting locators such that if
two locators are started simultaneously, not all the MBeans get
federated to both members. This was causing intermittent test failures
in the before() of JMXMBeanReconnectDUnitTest. To fix this, a wait has
been added so that the first member has enough time to start before the
second one.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Does customer-facing documentation mention that locators must not be started or restarted with N seconds of each other, and how many seconds N is?  Is the race condition something that can be fixed (is there an existing GEODE ticket for this you can reference)?  Your change seems like a great improvement to our test stability in general but also potentially sweeping a real issue under the rug.


[Translatable] Strange Issue with Query Hint and APC

I have a strange issue with the Translatable Query Hint when using APC as the metadata cache. I have my entity manager conifgured as follows.
<?php
$cache = new \Doctrine\Common\Cache\ArrayCache;
$DoctrineConfig->setMetadataCacheImpl($cache);

When using the Array Cache (as above) my application works as expected (including auto joining translation tables by using the Query Hint provided)
When I use the APC Cache for Metadata - but I manually clear the APC cache before each run, the application also works as expected
<?php
apc_clear_cache();
apc_clear_cache('opcode');
apc_clear_cache('user');
$cache = new \Doctrine\Common\Cache\ApcCache;
$DoctrineConfig->setMetadataCacheImpl($cache);

THE PROBLEM
The problem comes when I use APC caching, but don't clear it manually every time (i.e Using It would be doing in a live environment)
<?php
$cache = new \Doctrine\Common\Cache\ApcCache;
$DoctrineConfig->setMetadataCacheImpl($cache);

What I'm finding is that while everything is working as expected (including the query hint), there are a whole bunch of weird queries being generated (around translations) that are neither required, nor do they return any useful information. There are tons of these being generated on every request.
SELECT m0_.content AS content0,
m0_.field AS field1 FROM color_translation m0_
WHERE m0_.foreign_key = '12451'
AND m0_.locale = '12451'
AND m0_.object_class = '12451'

As you can see the locale and object_class fields are using the foreign key value instead of something sensible.
I'm going to look into this further next week when I have more time. In the meantime - any ideas?
*n.b I'm using yml mapping for all my entities, and annotation mapping for Gedmo\Translatable\Entity only.

closed because of sf2 cache machanism bug, if that is not the case reopen

I have the same wired behaviour with doctrine APCu cache. @sfblaauw Do you have any updates?
With doctrine array cache or if I useQueryCache(false) it works perfect.

APCu Version 4.0.6
PHP Version 5.5.22
Server Software Apache/2.4.12 (Ubuntu)
Doctrine 2.4
ZF2 2.3.5


Issue with new snpEff annotations in classic mode

Even in -classic and -formatEff the new snpEff (4.1) has changed SPLICE_SITE_REGION to SPLICE_SITE_REGION+INTRON which prevents parsing of the snpeff effects for these sites by GEMINI

Thanks for this. Can you tell if it also still produces SPLICE_SITE_REGION or is it a complete replacement?
We should look at their docs to see what else may have changed as this is an important source of false negatives

I'll look into the changelog. If it just allows multiples now, it looks like an easy fix in func_impact to loop over impact_string.split("+")

Looks like both are present

Good catch @brentp, I hadn't gone into the documentation enough to see that in the changelogs. Just ran a quick test and it seems that is the case.

I don't see this in the changes: http://snpeff.sourceforge.net/features.html
But I think that's because the concentration is on ANN.
@dgaston, any chance that you could share a header and a few lines with this problem?

@arq5x does that seem reasonably to loop over impact_string.split('+') here:
https://github.com/arq5x/gemini/blob/5398efd2de9b57934d2afe63d47c8533ebd1fc30/gemini/func_impact.py#L35-55
?

This challenge is then which annotation to store. Let me give it some thought...

variant_impacts are already many to one, or is there another issue?

Yup, I am not in the office at the moment but will post as soon as I can.

Sample '+' lines (SPLICE_SITE_REGION): http://pastebin.com/raw.php?i=CiTqKpe8
VCF header: http://pastebin.com/raw.php?i=0invvc3W
You'll notice in the VCF header there are a couple of snPEff entries from different rounds of SnpSift RmInfo and reannotating.

Thanks much, Daniel. Given that these new types come from -classic and we already have a goal (https://github.com/arq5x/gemini/issues/383) of supporting version 4.0 and abaove, I think perhaps the best solution here would be to update GEMINI to expect snpEff >=4.0.  Otherwise, I fear that we be left in a state of applying consecutive patches for these new terms.
In the interim, you could run snpEff <= 3.6 to reproduce prior results.
Thoughts?

I agree absolutely that just updating to a newer version of snpEff is the best solution long term. Putting some notice in the current documentation about the issue would probably be a good bet so people know. You can easily pull all of these variants by querying for "impact_sevierity is NULL" as a SQL where clause.

Yep, we should add a warning in the interim. Thanks Daniel.


How to specify canvas size and Image Mode

I can't seem to find how to adjust the canvas size to anything that isn't a square. It appears to default to [501, 501]. Is there a way to specify say an 800x600 pixel canvas size?
Also, is there a way to specify the image mode? I'm a little unclear how the PIL.Image module connects back to the image that turtle_pil creates.

Hello! Sorry, these features are currently not implemented.


Yatin: Watch askshank.com

Yatin requests the watch of the watch_keyword askshank\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

askshank\.com has been seen in 0 true positives, 1 false positive, and 0 NAAs.

Approved by rene in Charcoal HQ


Can't it be installed in the M2 chip of the Mac

In Mac OS, computers installed on the M2 pro chip via homebrew software will display the following error message
My macos version is 13.5, Xcode version is 14.3.1, MacBook Pro 14，Apple M2 Pro
brew install<EMAIL_ADDRESS>==> Downloading https://formulae.brew.sh/api/cask.jws.json
-#O#- #   #
==> Downloading https://formulae.brew.sh/api/formula.jws.json
#=#=-#  #
==> Fetching<EMAIL_ADDRESS>==> Cloning https://github.com/zeroc-ice/icetouch.git
Updating<EMAIL_ADDRESS>==> Checking out tag v3.6.4
HEAD is now at 5f8ab96 Update ice submodule to v3.6.4
HEAD is now at 5f8ab96 Update ice submodule to v3.6.4
Entering 'ice'
<EMAIL_ADDRESS>==> Installing<EMAIL_ADDRESS>from zeroc-ice/tap
==> make install<EMAIL_ADDRESS>OPTIMIZE=yes MCP
Last 15 lines from<EMAIL_ADDRESS>"_mcpp_use_mem_buffers", referenced from:
"_mcpp_use_mem_buffers", referenced from:
Slice::Preprocessor::preprocess(bool, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&) in Preprocessor_Slice_cpp.o
Slice::Preprocessor::printMakefileDependencies(std::__1::basic_ostream<char, std::__1::char_traits>&, Slice::Preprocessor::Language, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>>> const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&) in Preprocessor_Slice_cpp.o
Slice::Preprocessor::preprocess(bool, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&) in Preprocessor_Slice_cpp.o
Slice::Preprocessor::printMakefileDependencies(std::__1::basic_ostream<char, std::__1::char_traits>&, Slice::Preprocessor::Language, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>>> const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&) in Preprocessor_Slice_cpp.o
ld: symbol(s) not found for architecture x86_64
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [../../lib/IceTouch/ObjC/bin/slice2objc] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [../../lib/IceTouch/Cpp/bin/slice2cpp] Error 1
make[1]: *** [install] Error 1
make: *** [install] Error 1
If reporting this issue please do so at (not Homebrew/brew or Homebrew/homebrew-core):
https://github.com/zeroc-ice/homebrew-tap/issues

HI @devzw,
Ice Touch 3.6 does not support Apple Silicon. It's recommend to upgrade to Ice 3.7. The Ice Touch SDKs were merged into Ice in 3.7.

Hi @externl
I have also encountered the same problem. How can I solve it to install it icetouch@36
thanks

Hi @PaulWyw, the only "fix" is to upgrade to Ice 3.7 as I mentioned above.


chore: Merge community master

What do these changes do?

Related issue number

Fixes #xxxx
Check code requirements

[ ] tests added / passed (if needed)
[ ] Ensure all linting tests pass, see here for how to run them

Replaced by #114 .


Problem on Part 3 Step 27.

I don't know what's wrong.

Please give a screenshot or at least something.

It won't show Emu in the System Setting.

This isn't a support forum.

Stop opening issues for pointless or trivial questions and wasting my time.


Ensure min_nodes and max_nodes are up to date with the cloud provider.

During our testing, there's possibility that the min_nodes / max_nodes value can be updated via the AWS console or through API. This will help to ensure the RunOnce loop keep the min_nodes and max_nodes up to date.

Sounds good. Grab me anytime if there's anything needs to work on.

I've tested the changes and all seems to be well. Of note, edge case testing included changing the minimum ASG size to a conflicting value while escalator was scaling up. Escalator behaved correctly by noting the current node count was less than the minimum and resolved to normal once the scale operation was complete.
Approved and merge/release shortly.


Npm i without sudo

Why is sudo needed to run npm i on MacOS and Ubuntu? If I run it without sudo, i get the eaccess permission denied error.
If this would work without sudo, I could do matrix workflows over all 3 platforms, but as Windows doesn't know sudo, I can't do that...

Hello, @hrueger
Could you provide steps to reproduce the issue?
For example, I don't use sudo:
on: push
jobs:
  build:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [macos-latest, ubuntu-latest]
    steps:
     - name: npm i
       run: |
         git clone https://github.com/cnpm/npminstall
         cd npminstall
         npm i

Sure, I did some more tests and found out that it only happens on Ubuntu (MacOS is fine now, I don't know why) and only when a package is installed globally. The project where I ran npm i originally had a dependency which had a posinstallscript which tried to install another package globally.
You can see my test action here: https://github.com/hrueger/npm-i-sudo-tests/runs/528174020. I only try to install nativescript globally.
My workflow file looks as follows:
name: "Test"

on: [push]

jobs:
  osxUbuntuNoSudo:
    strategy:
      matrix:
        os: [ubuntu-latest, macOS-latest]
      fail-fast: false
    name: No sudo on ${{matrix.os}}
    runs-on: ${{matrix.os}}
    steps:
    - uses: actions/checkout@v1
    - name: Install
      run: npm install -g nativescript
  osxUbuntuWithSudo:
    strategy:
      matrix:
        os: [ubuntu-latest, macOS-latest]
      fail-fast: false
    name: Sudo on ${{matrix.os}}
    runs-on: ${{matrix.os}}
    steps:
    - uses: actions/checkout@v1
    - name: Install
      run: sudo npm install -g nativescript

The Ubuntu job without sudo is failing.

@hrueger , The /usr/local/lib/node_modules folder has owner root. A normal user can't write to system folder. In your case, running the installation command with sudo gives you the permissions of the superuser, and allows you to modify files that your normal user doesn't have permission to modify the directory /usr/local/lib/node_modules/. The root user does, and so the installation is successful.
Workaround:

Use NPM_CONFIG_PREFIX - https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally

export NPM_CONFIG_PREFIX=~/.npm-global
npm install -g nativescript

Use sudo
sudo npm install -g nativescript

Change owner
sudo chown -R $USER /usr/local/lib/node_modules

@al-cheb Thanks for the quick response! That makes sense.
Is there any chance that that folder will be changed to a folder which is writable for non-root users by default in the future? Or does that have (security) drawbacks?

@hrueger, You should  follow the recommendation - "In general, all packages should be installed locally(local packages are installed in the directory where you run npm install , and they are put in the node_modules folder under this directory)." (https://nodejs.dev/npm-global-or-local-packages). Updating a global package would make all your projects use the new release, and as you can imagine this might cause nightmares in terms of maintenance, as some packages might break compatibility with further dependencies, and so on.
WebPack: Note that this is not a recommended practice. Installing globally locks you down to a specific version of webpack and could fail in projects that use a different version.(https://webpack.js.org/guides/installation/#global-installation)
It's very serious security drawbacks for production system when non-root user can write to system folders. I think it's possible to change default behavior in future,

Try running actions/setup-node before installing anything globally with npm. I've run into this problem and doing this seems to fix the permissions, even though node and npm are already pre-installed on the runners.
- uses: actions/setup-node@v1
  with:
    node-version: '12.x'
- name: Install
  run: npm install -g nativescript

@hrueger, by default actions/setup-node@v1 task is using /opt/hostedtoolcache as an installation path where all users can able to write.
npm config get prefix : /opt/hostedtoolcache/node/
Free free to open the thread if you have any concerns.


Add Auto-E switch and fix standard mode

Fixes #.

Add Auto-E switch to disable automatic scientific notation while F-E switch is disabled
Fix standard mode - disable automatic scientific notation for non-scientific standard mode

Description of the changes:

Added Auto-E switch in scientific mode to force disable automatic scientific notation while F-E switch is disabled
Changed default value for automatic scientific notation in standard mode to disabled

How changes were validated:

manual

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


Allow unique-callout module to be dis/en-abled using cargo flags

As previously discussed, even though unique callouts perform better in accuracy and performance, there is still doubt about its reliability. So, it's best to allow users to enable or disable this module using cargo feature flags.
To minimize the use of cfg all around the code (it's an anti-pattern to do so), I have added dead code in the unique_callout.rs to have them as placeholders if the module is disabled.
After this PR is merged, I'll create a new PR to merge this branch into main to squash all the commits into one merge commit.

All the CI checks are working fine locally but if someone is still unsure, note that merge PR will run the CI regardless ;)

@unleashed Added a dummy module with the reasoning behind it as well. I think this is the minimum number of cfg attributes that are needed and cannot decrease the count more due to coupling between the unique_callout and other modules.

Rebased and CI is passing locally.

@unleashed LGTM now, please approve and merge if it looks good to you as well :)

Looks good!


Merge 9 -> 10

➡ Forward port
Port sdf9 to sdf10 (second attempt at #741)
Branch comparison: https://github.com/ignitionrobotics/sdformat/compare/sdf10...sdf9
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

Codecov Report

Merging #750 (0262ecd) into sdf10 (424bf9c) will decrease coverage by 0.07%.
The diff coverage is 86.01%.

@@            Coverage Diff             @@
##            sdf10     #750      +/-   ##
==========================================
- Coverage   88.38%   88.31%   -0.08%
==========================================
  Files          65       66       +1
  Lines       10411    10570     +159
==========================================
+ Hits         9202     9335     +133
- Misses       1209     1235      +26

Impacted Files
Coverage Δ

include/sdf/Console.hh
100.00% <ø> (ø)

include/sdf/Element.hh
100.00% <ø> (ø)

src/Console.cc
87.71% <22.22%> (-12.29%)
:arrow_down:

src/Sensor.cc
80.41% <50.00%> (-1.64%)
:arrow_down:

src/ForceTorque.cc
89.38% <89.38%> (ø)

src/Joint.cc
97.61% <93.33%> (-0.43%)
:arrow_down:

src/Element.cc
96.88% <100.00%> (+0.04%)
:arrow_up:

src/Model.cc
86.73% <100.00%> (+0.13%)
:arrow_up:

src/World.cc
93.45% <100.00%> (+0.07%)
:arrow_up:

src/parser.cc
79.31% <100.00%> (+0.09%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


use action/checkout@v4

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

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

Totals

Change from base Build<PHONE_NUMBER>4:
0.0%

Covered Lines:
16879

Relevant Lines:
17097

💛  - Coveralls


Added if statements for custom database name and custom password

here we go. new take at this
@mkostick

One minor suggestion, otherwise G2G.

applied the suggestion. merging


Keep selected tab through rotation at FeedScreen

Issue

close #127

Overview (Required)

Tab selection returns to Home every time when the screen is rotated, so it is now keeped in the ViewModel.

Links

Screenshot

Before
After

When an item is selected from the Drawer, FeedScreen receives the selected tab as InitialSelectedTab, but how do I propagate this as the initial state to the ViewModel?

Currently, I have implemented it only in FeedScreen, but should I implement it in OtherScreen as well?

👀

It's good question💡
@Index197511 Don't worries, It is walcome thing that you'll just implement the FeedScreen to improve keeping selected tab within rotation☎
By the way, we're glad that the number of contributors will increase if you create a new issue for other screens to fix the same problem.

Thank you!
I've finished implementation and make an issue to implement the selected tabs from the Drawer and something similar in OtherScreen.

@mhidaka
Thank you!
I've finished implementation and make an issue to implement the selected tabs from the Drawer and something similar in OtherScreen.

Great! Thank you for your additional work. and The review of this PR is waiting for A reviewer in charge to get freetime. please wait a minite 😉

👀

When an item is selected from the Drawer, FeedScreen receives the selected tab as InitialSelectedTab, but how do I propagate this as the initial state to the ViewModel? @takahirom

How about this way?
    effectFlow.collectInLaunchedEffect { effect ->
        when (effect) {
            is FeedViewModel.Effect.ErrorMessage -> {
                scaffoldState.snackbarHostState.showSnackbar(
                    effect.appError.getReadableMessage(context)
                )
            }
        }
    }
    LaunchedEffect(initialSelectedTab) {
        dispatch(...)
    }

It looks very good.
However, with this way, won't the LanchedEffect be called every time the screen is rotated and the Tab will be reset?

It looks very good.
However, with this way, won't the LanchedEffect be called every time the screen is rotated and the Tab will be reset?
@takahirom

I will check more 👀

It was my mistake. Perhaps the selected tabs are unmanageable in this scope. 👀
I'm very sorry, is it possible to move the tab management process to AppContent and use savedInstanceState()?

It may take a while, but I'll try it.

Would it be better to create another issue and implement it there? @takahirom

I have assigned you to this issue. Therefore, you can add an implementation to this PR or issue another PR. 👍
https://github.com/DroidKaigi/conference-app-2021/issues/198

I'm thinking if I try to save FeedTabs within onSavedInstanceState, Activity must own selected tab in the FeedScreen. I'm not sure how to do this, as having a ViewModel in the Activity seems subtle.
@takahirom

Can you use navigation? (I tried. but this is not fixed format commit)
https://github.com/DroidKaigi/conference-app-2021/commit/7a907ac9602267443265a912744d7c69ef121e48

Thank you for your help!
I moved the SelectedTab that I had in ViewModel to Navigation.
It's working well.

Thank you for your help! @takahirom
I moved the SelectedTab that I had in ViewModel to Navigation.
It's working well.
I've finished implementation for this PR.


Confidence Scoring for Predictions

Story:
As a support team lead, I want to see a confidence score alongside the model’s predicted category, so I can assess when manual review may be necessary.
Acceptance Criteria:
Display a confidence score with each predicted category (e.g., above 90% is high confidence).
Route tickets below a certain confidence threshold for manual review.
Improvements:
Integrate confidence scoring capabilities in the model, possibly by using ensemble methods to validate predictions.
Provide training to agents on how to interpret and use confidence scores effectively.

Out of scope


FoxySDK.Nucleon

A base class providing opt-in internationalization, validation, container-based styling and CRUD capabilities to the custom elements extending it. This is the foundation that (almost) every new component in Foxy Elements will be built upon + being part of our SDK it will allow other devs to seamlessly integrate their own elements with the ones provided by Foxy.
WIP. Demos are in this repo for now, but may be moved to the Elements by the time this PR is ready for review. To see them, run: npm run serve:demos and open http://localhost:1234/nucleon.html.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: pheekus:white_check_mark: ndvo:x: brettflorioYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: pheekus:white_check_mark: ndvo:x: brettflorioYou have signed the CLA already but the status is still pending? Let us recheck it.


Deploy ingress-nginx ServiceMonitor in Rancher v2.5 for scraping by Monitoring v2

What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Steps to reproduce (least amount of steps as possible):
ingress-nginx-controller metrics are not scraped by default with Monitoring v2 in Rancher v2.5. For Rancher provisioned clusters with the ingress-nginx ingress controller, would it be possible to auto-deploy a ServiceMonitor and metrics Service similar to the below, which will enable scraping by Prometheus:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: ingress-nginx-controller
  namespace: ingress-nginx
spec:
  endpoints:
  - interval: 30s
    port: metrics
  namespaceSelector:
    matchNames:
    - ingress-nginx
  selector:
    matchLabels:
      app: ingress-nginx
---
apiVersion: v1
kind: Service
metadata:
  name: ingress-nginx-controller-metrics
  namespace: ingress-nginx
  labels:
    app: ingress-nginx
spec:
  ports:
  - name: metrics
    port: 9913
    protocol: TCP
    targetPort: 10254
  selector:
    app: ingress-nginx
  type: ClusterIP

Environment information

Rancher v2.5.2

gz#11621
gz#13981

@axeal, yes this is possible. Thanks for providing the Service / ServiceMonitor!
This issue will also encompass adding Grafana Dashboards, sourced from https://github.com/kubernetes/ingress-nginx/blob/a268ec493c6a1d81d0932f9aeedd1781df2fe7b1/deploy/grafana/dashboards/nginx.json and https://github.com/kubernetes/ingress-nginx/blob/a268ec493c6a1d81d0932f9aeedd1781df2fe7b1/deploy/grafana/dashboards/request-handling-performance.json.

@aiyengar2 Where to add these json files ?
Can it be finished in Grafana GUI ?

@k8w you can add these JSON files via the Rancher UI, here are the relevant docs: https://rancher.com/docs/rancher/v2.x/en/monitoring-alerting/v2.5/persist-grafana/.
Since you already have the JSON, all you need to do is the last step.

@aiyengar2 @sowmyav27 could you please point me how to install the enhanced chart? IIUC it should be available in rancher/charts.git in dev-v2.5 branch which is present in my cluster (well, it is https://git.rancher.io/charts - is it the same?) but latest monitoring chart version in the v2 dropdown is 9.4.203-rc04 even after the repo refresh. I was trying with rancher:v2.5-head. The new monitoring chart version should be 9.4.204-rc01.
Should I clone the charts.git locally and deploy it manually or is there a way how to do it from webUI?

I just successfully installed the testing monitoring chart from my local git checkout.
git clone https://git.rancher.io/charts --branch dev-v2.5
cd charts/charts/rancher-monitoring/rancher-monitoring-crd/9.4.204-rc01
helm install rancher-monitoring-crd ./
cd ../../rancher-monitoring/9.4.204-rc01/
helm install rancher-monitoring ./

@thehejik weird, I see https://github.com/rancher/charts/tree/dev-v2.5/assets/rancher-monitoring contains 9.4.204-rcXX versions so it should be working. But the approach you did via bash works too.

@thehejik The RC version of the chart is not available on 2.5-head because the rancher charts by default point to release-v2.5. We can manually change it to point to dev-v2.5 now and proceed with testing. I have asked it to be looked at by the dev.

Thanks, I had some problems with DNS but now it works correctly.
The feature is working as described but so far user has to set ingressNginx.enabled=true https://github.com/rancher/dashboard/issues/2485 in the chart value YAML file (Apps -> Monitoring -> General -> Edit as YAML).

The corresponding ServiceMonitor and Service are being created
New monitoring-ingress targets are all UP in Prometheus:  ingress-nginx/rancher-monitoring-ingress-nginx/0 (3/3 up)
There is a new Grafana dashboard named NGINX / Ingress Controller available

I was testing on rancher 2.5.7 with v2.5-head image tag and used http://git.rancher.io/charts dev-v2.5 branch. Monitoring helm chart was in version 9.4.204-rc04.

I just updated our 2.5.7 rancher installation to 2.5.8, and updated also our rancher monitoring, but can't get it running somehow.
I've enabled ingressNginx.enabled: true, and also set a different namespace (we installed the nginx ingress controller into a "default" namespace, but get only following error in the end:

Error:  UPGRADE FAILED: cannot patch "rancher-monitoring-alertmanager.rules"  with kind PrometheusRule: Internal error occurred: failed calling  webhook "prometheusrulemutate.monitoring.coreos.com": Post  "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s":  dial tcp <IP_ADDRESS>:443: connect: connection refused &&  cannot patch "rancher-monitoring-general.rules" with kind  PrometheusRule: Internal error occurred: failed calling webhook  "prometheusrulemutate.monitoring.coreos.com": Post  "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s":  dial tcp <IP_ADDRESS>:443: connect: connection refused &&  cannot patch "rancher-monitoring-k8s.rules" with kind PrometheusRule:  Internal error occurred: failed calling webhook  "prometheusrulemutate.monitoring.coreos.com": Post  "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s":  dial tcp <IP_ADDRESS>:443: connect: connection refused &&  cannot patch "rancher-monitoring-kube-apiserver-availability.rules" with  kind PrometheusRule: Internal error occurred: failed calling webhook  "prometheusrulemutate.monitoring.coreos.com": Post  "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s":  dial tcp <IP_ADDRESS>:443: connect: connection refused &&  cannot patch "rancher-monitoring-kube-apiserver-slos" with kind  PrometheusRule: Internal error occurred: failed calling webhook  "prometheusrulemutate.monitoring.coreos.com": Post  "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s":  dial tcp <IP_ADDRESS>:443: connect: connection refused &&  cannot patch "rancher-monitoring-kube-apiserver.rules" with kind  PrometheusRule: Internal error occurred: failed calling webhook  "prometheusrulemutate.monitoring.coreos.com": Post  "https://rancher-monitoring-operator.
--

You need to define selector for rancher-monitoring-ingress-nginx service
ingressNginx:
  enabled: true
  namespace: ingress-nginx
  service:
    port: 9913
    targetPort: 10254
    selector:
      app.kubernetes.io/component: controller
      app.kubernetes.io/instance: ingress-nginx
      app.kubernetes.io/name: ingress-nginx
  serviceMonitor:
    interval: 1m
    metricRelabelings: []
    relabelings: []

I just updated our 2.5.7 rancher installation to 2.5.8, and updated also our rancher monitoring, but can't get it running somehow.
I've enabled ingressNginx.enabled: true, and also set a different namespace (we installed the nginx ingress controller into a "default" namespace, but get only following error in the end:
Error: UPGRADE FAILED: cannot patch "rancher-monitoring-alertmanager.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-general.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-k8s.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kube-apiserver-availability.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kube-apiserver-slos" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kube-apiserver.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.
cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kube-prometheus-general.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kube-prometheus-node-recording.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kube-state-metrics" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kubelet.rules" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kubernetes-apps" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kubernetes-resources" with kind PrometheusRule: Internal error occurred: failed
calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused
&& cannot patch "rancher-monitoring-kubernetes-storage" with kind PrometheusRule: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://rancher-monitoring-operator.cattle-monitoring-system.svc:443/admission-prometheusrules/validate?timeout=30s": dial tcp <IP_ADDRESS>:443: connect: connection refused

@h0jeZvgoxFepBQ2C see https://github.com/rancher/rancher/issues/32416#issuecomment-828881726. If you re-trigger an install, it should successfully install.

You need to define selector for rancher-monitoring-ingress-nginx service in order to collect metric from ingress nginx controller pod
ingressNginx:
  enabled: true
  namespace: ingress-nginx
  service:
    port: 9913
    targetPort: 10254
    selector:
      app.kubernetes.io/component: controller
      app.kubernetes.io/instance: ingress-nginx
      app.kubernetes.io/name: ingress-nginx
  serviceMonitor:
    interval: 1m
    metricRelabelings: []
    relabelings: []

Do you have a link where this is documented? thx!

Hmm @thehejik when we tested this did we need to update the selector?
@quangthe sorry for the late ask, but could you share your environment information that required you to provide a selector in https://github.com/rancher/rancher/issues/30126#issuecomment-870213309 so we can attempt to reproduce? Specifically:

Rancher version: ``
Kubernetes Version: ``
Type of cluster

[ ] Custom: Running a docker command on a node
[ ] Imported: Running kubectl apply onto an existing k8s cluster
[ ] EKS
[ ] GKE
[ ] AKS
[ ] Infrastructure Provider: Rancher provisioning the nodes using different node drivers (e.g. AWS, Digital Ocean, etc)
[ ] Other: ``

Monitoring Chart Version: ``

Based on the labels shown in https://github.com/kubernetes/ingress-nginx/blob/8b3a6f02526e8bcf8b6fff2bf8d3613e20211b15/deploy/static/provider/cloud/deploy.yaml#L298, it seems like you are right that the default should be to use app.kubernetes.io/name: ingress-nginx instead of app: ingress-nginx, as used in Rancher's chart.
But I wonder if RKE / RKE2 still deploy ingress-nginx with the other label, which is why we left it as app: ingress-nginx.

@aiyengar2 I don't think I was using the proposed selector, on the other hand I'm not sure if metrics from ingress were shown.

Hmm in that case, @sowmyav27 I'm re-opening this issue and putting it to test.
We need to confirm that setting ingressNginx.enabled: true shows the ServiceMonitor on the Prometheus UI for targets and that it has active targets that are emitting metrics.
We should also double check that the Grafana dashboards are eventually populated with metrics if an ingress is added to the cluster.

Retested on 2.5.9 with v2 monitoring 14.5.100 from official release-v2.5 chart repo on RKE1 cluster.
I was using default values for the chart installation where ingressNginx.enabled: true is enabled by default (switched to Edit as YAML to validate). I didn't change any selector value - there is still the original label app: nginx-ingress set on nginx-ingress-controller-* pods.
This is what was used for monitoring installation:
ingressNginx:
  enabled: true
  namespace: ingress-nginx
  service:
    port: 9913
    targetPort: 10254
  serviceMonitor:
    interval: ''
    metricRelabelings: []
    relabelings: []

Grafana
For testing purposes I've deployed an nginx deployement and created L7 Ingress entry for the nginx using default nginx-ingress as loadbalancer, then I was doing curl <nginx_lb> in a endless loop while checking the grafana board NGINX / Ingress Controller and its graphs. The metrics data were being processed there:

Prometheus

ServiceMonitor for rancher-monitoring-ingress-nginx exists:

Ingress related targets are up, healthy and are giving data:

I'd say everything is working as expected with default values.

Perfect! Thanks for checking @thehejik.
@h0jeZvgoxFepBQ2C @quangthe if you are still encountering this issue, please let us know your environment information! Perhaps there’s something we could document that is specific to the environment that you are deploying Monitoring into that requires selectors, but by default updating it should not be required.


ui/datasets: Refactor selectors

Code Changes

Track dataset by fides key instead of object copy and nulls

Previously we've stored a copy of the dataset returned by the get-by-key query,
but only every use its key property. With this change we only store the key and
use the object from the query directly.

As part of this, I also converted a lot of null to undefined. There different
opinions on this, but undefined is generally more useful in a TS codebase because:

It plays nicely with optional function arguments.
It can be represented by a single question mark in interfaces. (See the State
changes in this commit.)
It doesn't have null's typeof null === "object" confusion.

Single state for edit drawer

This resolves some naming inconsistencies and also makes it explicit that only one drawer can ever be open.

Extract collection lookups to selector

Extract field lookups to selector

Extract field types into Cell component

Steps to Confirm

[ ] The dataset editing experience should be unchanged.

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation Updated:

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md

Description Of Changes
These changes set me up for #1075. Layering in classification information means a lot of nested lookups with fallbacks. Well-organized selectors are going to make this possible.

heh @LKCSmith and I had this discussion around null vs undefined a while ago and settled on null over undefined, hence why there's so many nulls around. I don't really have a strong opinion either way and am happy to go back to undefined, but thought I'd surface that old discussion since it might be relevant

heh @LKCSmith and I had this discussion around null vs undefined a while ago and settled on null over undefined, hence why there's so many nulls around. I don't really have a strong opinion either way and am happy to go back to undefined, but thought I'd surface that old discussion since it might be relevant

I'm wondering if this is just a practice I carried over from previous jobs that has since changed or evolved in some way. I think I remember questioning if it was still a best practice or not,  but the tradeoffs here sound like they would simplify the TS a bit. I think I generally don't like how it looks with setting or dispatching undefined over null -- it just seems weird to me in a Redux context.
But, if this makes our codebase easier to read or follow though, I'm amenable to it

had this discussion around null vs undefined a while ago

Classic! it's one of those JS classic things that is unreasonably confusing and gets plenty of back-and-forth in a code base (or in random online threads).

I'm wondering if this is just a practice I carried over from previous jobs that has since changed or evolved in some way.

Yeah, there was a bit of an argument in favor of null when we didn't have TS to make a distinction between "this is a value, but nothing is there at the moment" and "this ain't a value at all". I think that's the logic of some built-in APIs like document.getElementById which returns null when there is no match. But then JS steps on its own feet with array.find returning undefined when there is no match!
In TS the benefit of optional?: working with undefined in function params and interfaces sways me away from null.
Though even in plain JS, question mark chaining falls back to undefined, so something like state.data?.maybe?.value could result in multiple "empty" values if you use null, but only one if you consistently use undefined.


[SQL Standard] FETCH FIRST is broken

Using SQL 2008 standard version of LIMIT, FETCH FIRST causes an error:
select * from atom.audit order by ctime desc fetch first 10 rows only;

Query execution failed
Reason:
SQL Error [42601]: ERROR: syntax error at or near "LIMIT"
Position: 73
This seems like an issue with dbeaver's query parser not realising that a query in fact does have a limiting clause and adding one at the end of the query, effectively preventing user from running standard-compliant queries.
As this form is supported by Postgres, DB2, Oracle and MSSQL (https://modern-sql.com/slides) it might perhaps make some sense to fix it at some point.

Looks odd, I can't reproduce this. We don't use LIMIT for SQL Server.
What DBeaver driver do you use? jTDS, Microsoft? Or is it some custom configured driver?

Using Postgres. The log clearly shows the error where LIMIT is added.

It is a bug in SQL transformer.
As a workaround you can disable "Use SQL to limit fetch size" option. BTW it is disabled by default.


contentType only available on Dropzone?

The contentType parameter is only available on the Dropzone template. If this is intended, please specify so in the readme, could've saved me some hair-pulling :P
If not, then please fix upload_boostrap and upload_semanticUI templates so they accept contentType as well.
Now when contentType is used, it isn't appended to the formData parameter and formData is undefined.

Not sure what do you mean, content type is automatically added to the form data.
As per: https://github.com/tomitrescak/meteor-tomi-upload-jquery/blob/master/templates/upload.js#L23-L28

Sorry, you were right. It was a bug. Will be fixed in the next release 2.1.8. I apologise.

I have the same problem with the version 2.4.0 of upload-jquery. Is it supposed to be fixed ?


fix(doc): Promote Open Beta to GA

Signed-off-by: cbrealey<EMAIL_ADDRESS>PR summary

PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[x] Documentation content changes
[ ] Other (please describe)

What is the current behavior?
N/A: Doc updates only
What is the new behavior?
N/A: Doc updates only
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


HomeAssistant module: daikin not compatible

Describe the bug
With daikin = {}; in configuration.nix , we get:

The 'daikin' option near /var/lib/hass/configuration.yaml:0 has been removed, please remove it from your configuration

Without, we get in Home Assistant logs:

Setup failed for daikin: Unable to import component: No module named 'pydaikin'

In other words: in both (which, unfortunately is all) cases it doesn't work.
Steps To Reproduce

Add daikin = {}; (see Nix Home Assistant wiki entry for if you are not familiar with this syntax)

Expected behavior
A working integration without any error or warning messages in some supported configuration.
Screenshots

Additional information
Unlikely to be an upstream problem.
Similar to #166821
Notify maintainers
@jsimonetti
Metadata
nixpkgs module and package: 710fed5a2483f945 (on an otherwise nixos-21.11 system)

The solution suggested in https://github.com/NixOS/nixpkgs/issues/166824#issuecomment-1086119241 works.


Update Project “fill-murrays”

Automatically generated by Netlify CMS

:construction_worker: Deploy Preview for blissful-lumiere-fdb2f5 processing.
:hammer: Explore the source changes: 36b4568ab0ce1951e63b2ad8a2bd8188ce656467
:mag: Inspect the deploy log: https://app.netlify.com/sites/blissful-lumiere-fdb2f5/deploys/60e6b10471533f0007513f5d


[BUG] Coverage no longer displaying in README badge

I'm not sure when this bug manifested, but we should fix it. There's no point in having the badge if it's not working. This may also mean that it's not calculating changes to coverage for PRs, which is something we want.

I'll look into this. I want to add some more tests for something, but it probably makes sense to fix this issue first.

I made it work by pasting the CODECOV_TOKEN into the GitHub Secrets settings thing again... Not sure why it stopped working.
The badge is now displaying coverage again (it's at a miserable 46% :upside_down_face:)


abao debugging

test with cargo test --package iroh --lib --all-features -- tests::many_files --exact --nocapture

Bug is fixed in #720. Abao was not at fault.


:seedling: cache: small refactor to make wiring into kcp easier

Summary
Related issue(s)
Fixes #

/assign @stevekuznetsov @sttts

https://github.com/kcp-dev/kcp/issues/342


ImportAware links are being called inconsistently

ImportAwareLinksDiscoverer is relying on ResolvableType to figure out whether the bean type implements ImportAware. Unfortunately, some bean definitions doesn't have one so we should fallback to the beanClassName if necessary.

On a second look, this is rather a different problem. We're taking the parent configuration class as the import link whereas framework really means the import semantic. So, for instance, if you have a inner class of a configuration class that's import aware, the AOT engine will honor the callback whereas the JVM would not (as the inner class wasn't @Import'ed).
Unfortunately, there's no API to access that information as the ImportStack is computed at runtime. We will have to change something in our override of ConfigurationClassParser for this.

Fixed by 1d055a169b8917


Release next blueprint version

[x] Upgrade JHipster dependencies
[x] Bump third party dependencies
[x] Migrate EsLint dependency
[ ] Update change log, examples
[ ] Update jhipster svelte library dependencies, eslint, other confs
[ ] Prepare release and polish configurations

@pascalgrimaud , @mraible , Can we add some bounty for next release publish?

@vishal423 What amount do you think is appropriate?

Done!


Support for non-standard compilers

Example cross compilers.

Check in create.sh script that the compiler paths are valid
Forward that variable to cmake
Allow easier tweaking of flags on a per compiler basis.

Can be done via cmake vars, if it comes up I'll reopen this one


[SPARK-20764][ML][PySpark][FOLLOWUP]Fix visibility discrepancy with numInstances and degreesOfFreedom in LR and GLR - Python version

What changes were proposed in this pull request?
Add test cases for PR-18062
How was this patch tested?
The existing UT

Test build #77229 has started for PR 18068 at commit 7bbfe3a.

Test build #77231 has started for PR 18068 at commit 013adc4.

Test build #77229 has finished for PR 18068 at commit 7bbfe3a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  class DecisionTreeClassifierWrapperWriter(instance: DecisionTreeClassifierWrapper)
 class DecisionTreeClassifierWrapperReader extends MLReader[DecisionTreeClassifierWrapper]
  class DecisionTreeRegressorWrapperWriter(instance: DecisionTreeRegressorWrapper)
 class DecisionTreeRegressorWrapperReader extends MLReader[DecisionTreeRegressorWrapper]

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77229/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77231/
Test FAILed.

retest this please

Test build #77234 has started for PR 18068 at commit 013adc4.

Test build #77234 has finished for PR 18068 at commit 013adc4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77234/
Test PASSed.

Merged build finished. Test PASSed.

LGTM, merged into master and branch-2.2. Thanks for all.


Upgrade gRPC to v1.40.0 and Golang version to 1.15+

Update the depending libraries for latest bug/security fixes and bump the minimum Golang version accordingly.

CC @dfawley

@dfawley Good catch. I corrected the commands in README in #11, and tested them via Docker images.


[Question] Getting rid of<EMAIL_ADDRESS>

I believe and I noticed there was some effort around removing lodash-es and I see it has been removed. Does the latest release compatible with angular 9?

lodash released 4.17.21, to address latest security issue. Please have a look at it.

I'm have not tested this, but would guess that there are some issues. The 9.0.3 version of the tree still has lodash-es in version 4.17.15 as a dependency. We can update this to 4.17.20 and release it as a new version. Would a new version help or do you need lodash-es do be gone completely?

Because of a fix for the virtual scroll we also updated older versions of the tree. In that update I added also the lodash-es update. So in the new version 9.0.4 there are two new bugfixes for virtual scroll and also the update for lodash-es to version 4.17.20.

lodash 4.17.20 wont solve the security issue. I request you to upgrade to 4.17.21

@tobiasengelhardt I am sorry I should have commented earlier. But 9.0.4 has security issues as lodash 4.17.20 has to CWE issues. I am afraid you may have cut a new release with lodash-es 4.17.21

There is now version 9.0.5 available with lodash-es 4.17.21. There will also be a 10.0.4 version with the same update. If there are new lodash issues in the future just open a new issue and we will update lodash again.

Hey @tobiasengelhardt Thanks for the upgrades ! Any eta for 10.0.4 ? I saw the commits in the branch already, is there anything we could do to help?


HDDS-6502. Blocks of old key versions are not deleted on key deletion

What changes were proposed in this pull request?
When a key is deleted from OM, only the latest version of blocks are sent to SCM for deletion.
In OmMetadataManagerImpl#getPendingDeletionKeys(), we gey the latest version location information and return only those blocks for deletion to KeyDeletingService. This leads to older versions of blocks being orphaned.
RepeatedOmKeyInfo infoList = kv.getValue();
// Get block keys as a list.
for (OmKeyInfo info : infoList.getOmKeyInfoList()) {
  OmKeyLocationInfoGroup latest = info.getLatestVersionLocations();
  List<BlockID> item = latest.getLocationList().stream()
    .map(b -> new BlockID(b.getContainerID(), b.getLocalID()))
    .collect(Collectors.toList());
  BlockGroup keyBlocks = BlockGroup.newBuilder()
    .setKeyName(kv.getKey())
    .addAllBlockIDs(item)
    .build();
  keyBlocksList.add(keyBlocks);
  currentCount++;
}

This PR proposes to return all blocks from all versions of a key to KeyDeletingService when a key is marked for deletion.
What is the link to the Apache JIRA
Please replace this section with the link to the Apache JIRA)](https://issues.apache.org/jira/browse/HDDS-6502)
How was this patch tested?
Added unit test

Thank you @adoroszlai and @kaijchen for reviewing the PR. I will merge it in shortly.


Run Envoy Gateway like DaemonSet

Description:
For many use-cases need to start Kubernetes API Gateway like DaemonSet on special nodes.
We discuss it in Slack, and I found request of this feature in issue.
To start the discussion, I can suggest API-scheme for EnvoyProxyKubernetesProvider in EnvoyProxy (with Kubernetes Provider).
I propose the following architecture for implementation:
Now it's looks:
type EnvoyProxyKubernetesProvider struct {
	EnvoyDeployment *KubernetesDeploymentSpec `json:"envoyDeployment,omitempty"`

	EnvoyService *KubernetesServiceSpec `json:"envoyService,omitempty"`

	EnvoyHpa *KubernetesHorizontalPodAutoscalerSpec `json:"envoyHpa,omitempty"`
}

I think we can add field type and field for EnvoyDaemonset:
type KubernetesProviderType string

type EnvoyProxyKubernetesProvider struct {
        // By default - Deployment.
        Type KubernetesProviderType `json:"type,omitempty"`

	EnvoyDeployment *KubernetesDeploymentSpec `json:"envoyDeployment,omitempty"`

        EnvoyDaemonset *KubernetesDaemonsetSpec `json:"envoyDaemonset,omitempty"`

         // Need add logic to NOT create service
	EnvoyService *KubernetesServiceSpec `json:"envoyService,omitempty"`

        // Don't work, if type = Daemonset
	EnvoyHpa *KubernetesHorizontalPodAutoscalerSpec `json:"envoyHpa,omitempty"`
}

And:
// KubernetesDaemonsetSpec defines the desired state of the Kubernetes daemonset resource.
type KubernetesDaemonsetSpec struct {
	Patch *KubernetesPatchSpec `json:"patch,omitempty"`

	Pod *KubernetesPodSpec `json:"pod,omitempty"`

	Container *KubernetesContainerSpec `json:"container,omitempty"`

	InitContainers []corev1.Container `json:"initContainers,omitempty"`

         // Running only on special nodes
	NodeSelector map[string]string `json:"nodeSelector,omitempty"`
        Tolerations []corev1.Toleration `json:"tolerations,omitempty"`

        // By default - false
        HostNetwork bool `json:"hostNetwork,omitempty"`
}

(And need add logic for disable metrics Ports (19001) for DaemonSet ports). I think will be better, if we add field DisableMetricsPort to EnvoyProxyKubernetesProvider struct.
Finish
I can implement all the logic after agreeing on the API schema

This feature looks great, and we probably need to discuss the design of the API.

ptal @envoyproxy/gateway-maintainers @envoyproxy/gateway-reviewers

SGTM, but we need to talk about the API. In most cases, you can share the configuration between DS and Deployment, so maybe we can just something like mode?
here's what OpenTelemetry Operator did:
https://github.com/open-telemetry/opentelemetry-operator/blob/eaf998f2ae9ca93ecf319d6864690a2bd7cbe0c7/apis/v1beta1/opentelemetrycollector_types.go#L88

Its looks like we've had multiple users requesting Daemonset + hostNetwork mode
mode may get tricky for 2 cases

we've already called it envoyDeployment
we want to add a field to deployment but it may not exist in daemonset
we may not want to spend extra cycles supporting all cases in daemonset that are supported in deployment since that is not the common case for this project

I'd suggest supporting a new envoyDameonSet knob with a single patch field, so we dont spend our efforts adding more fields into it


Multiple small improvements

This pull request is all over the place, and mostly contains small changes that has annoyed me during development.
(P.s. Ignore the messy commit history. If accepted, merge and squash to keep the main fork tidy. )
Changes in simple_message.py
If you debug test_moto.py in VS Code and use break-points, continuing the execution often results in 0 is not a valid MsgType error.
This error never occured during normal runtime, although it's convenient to not have the debugger crash when using break-points.
With the current implementation, any attempt to parse a message type not included in the specifications retults in an Invalid message.
0 is not a valid MsgType
  File "/home/lab/Documents/moto_lars/moto/simple_message.py", line 168, in __init__
    self.msg_type = MsgType(msg_type)
  File "/home/lab/Documents/moto_lars/moto/simple_message.py", line 174, in from_bytes
    return cls(*cls.struct_.unpack(bytes_))
  File "/home/lab/Documents/moto_lars/moto/simple_message.py", line 992, in from_bytes
    header = Header.from_bytes(bytes_[4:16])
  File "/home/lab/Documents/moto_lars/moto/simple_message_connection.py", line 51, in recv
    return SimpleMessage.from_bytes(self._tcp_client.recv())
  File "/home/lab/Documents/moto_lars/moto/state_connection.py", line 87, in _worker
    msg: SimpleMessage = self.recv()

Changes in motion_connection.py
We currently MotionConnection.check_motion_ready(), but this returns a SimpleMessage with a MotoMotionReply body rather than a bool.
I added a wrapper method for that.
This is then used in send_joint_trajectory_point to confirm that motion is possible.
Changed any except: to except Exception:
Bare excepts defaults to BaseException and therefore also catches KeyboardInterrupt, meaning that it isn't possible to terminate the program using Ctrl+c.
See python docs
Changes in simple_message_connection.py
I added useful error messages when trying to connect to the controller.
Essentially the same as is described in the troubleshooting section.

@tingelst: what is the status of this PR?
I'd based my work on this branch, but if it's not going to get merged I'll switch to main.

Thank you, @SebastianGrans!
This is now merged into main, @gavanderhoorn.


Add documentation about restricting AWS creds to specific regions + how to set up that db

https://iasql.com/docs/aws/


Several error

Thank you for your work.
To test your good work, I tried to follow the instructions given in the README.md.
I have two problems
In environment.yml, it seems to be gaussian-splatting/submodules/diff-gaussian-rasterization-custom and not gaussian-splatting/submodules/diff-gaussian-rasterization.
I git cloned it with --recursive but just diff-gaussian-rasterization is empty.
The second issue is that in ./widgets/video_widge.py, the from scene.cameras import CustomCam is not working.
It looks like vanila gs is not importing well.
What should I do?
I'd like to contribute to your work after I've tested it enough.
And FYI, it doesn't seem to work on CUDA 11.7 or lower.
Thank you.

Hey, thanks for participating!
I have updated the submodules so that they are no longer hardcoded but instead linked to the respective repository. I hope this resolves the first issue. You might have to clone the repository again, to make it work.
The second issue can hopefully be resolved by adding the "gaussian-splatting" folder to the python path. I have added the line  sys.path.append("./gaussian-splatting") to main.py. Let me know if this works.
Do you have an idea, why CUDA 11.7 is not working properly?

Thank you for your quick response.
I cloned it again and the UI is working.
However, I'm facing a new problem
I set the training result of vanilla gaussian splatting to the path --data_path.
I think I missed something in this, could you please tell me?
The error is as below.
~/workspace/src# python main.py --data_path="/root/workspace/src/output/8467a616-9/"

Traceback (most recent call last):
  File "/root/workspace/src/viz/renderer.py", line 47, in render
    self._render_impl(res, **args)
  File "/root/workspace/src/viz/renderer.py", line 102, in _render_impl
    self.gaussian_model.load_ply(ply_file_path)
  File "/root/workspace/src/./gaussian-splatting/scene/gaussian_model.py", line 258, in load_ply
    opacities = np.asarray(plydata.elements[0]["opacity"])[..., np.newaxis]
  File "/opt/conda/envs/gs-view/lib/python3.10/site-packages/plyfile.py", line 715, in __getitem__
    return self.data[key]
  File "/opt/conda/envs/gs-view/lib/python3.10/site-packages/numpy/core/memmap.py", line 334, in __getitem__
    res = super().__getitem__(index)
ValueError: no field of name opacity

Never mind the last issue. The path was invalid.
When I set the path correctly, I see an array for _xyz or _opacity. But all I see is a black window.

The renderer seems to be working fine.
However, the Gaussians that I have are relative to a different coordinate system and have large values, which I think is why they don't show up.

Okay, thats good news that the renderer is working properly. With the mouse wheel, you can zoom out further that with the UI. Maybe, that helps rendering very large scenes. I will look into building a feature that autodetects the center of the scene and also adjusts the zoom to the size of the scene

I have just pushed a new feature that autodetects the center of the scene and adjusts the radius. The new buttons can be found in the camera widget. I hope this helps to properly render the scene.
It uses the mean xyz as center and stddev of xyz as radius
If there are no more questions, I will close this issue


:balance_scale: Suprising performances : gemma2:8b 1.40 times faster than gemma2:2b on ollama :llama:

:grey_question: Context
As mentionned earlier :

https://github.com/aurelio-labs/semantic-router/pull/346

A gave a try to semantic-router and got really impressive results, see 🔀 Semantic Router w. ollama/gemma2 : real life 10ms hotline challenge 🤯 .
... but recently gemma2:2b has been released, then I switched to this model, with the hope that :

It should be faster
Be as good

... but surprinsngly it did as good, but slower.
:point_right: The goal of this issue is to understand why... and what could be done to make semantic router run even faster than 10ms.
:balance_scale: Data
Considering the following runs :

Jupyter on gemma2:2b
Jupyter on gemma2:8b

Below some performances, both with same output quality :

Cell N°
gemma2:2b
gemma2:8b

13
44.2 ms
33 ms

14
16 ms
12.7 ms

15
15.9 ms
12 ms

16
17 ms
12 ms

17
15.9 ms
11.8 ms

18
21.4 ms
11.4 ms

19
16.3 ms
12.6 ms

20
15.6 ms
11.6 ms

:information_source: On each test, the 8b is faster than the 2b... and it's surprising:
:bar_chart: Benchmark conclusion
The average speed-up factor of gemma2:8b compared to gemma2:2b is approximately 1.40. This means that, on average, gemma2:8b is 1.40 times faster than gemma2:2b.
:point_right: Do you get the same performances ?

According to your feedbacks, I'll push an issue to ollama


epic anchors only work at top level

I can only add an anchor with a epic attribute at the top most level in a document. If I attempt to put it under even one layer of a region anchor pair, it goes unrecognized.
The following example in LUA works.
-- SECTION
-- !SECTION
-- FIXME[epic=Test]

This does not
-- SECTION
-- FIXME[epic=Test]
-- !SECTION

This issue will be fixed in the next release

yet fixed...


First pass at banners beta

Initial pass at a new feature i've been working on

This is failing CI for test coverage, but i don't currently intend to add tests for this code because its not mature enough for tests to be meaningful without too much overhead


Add "blocked" webhook event documentation

Not sure where to edit the webhook_description but I believe this is now part of the officially supported webhooks

@maschwenk thanks for the PR! We haven't added build.blocked to webhooks just yet, but you're right - we totally need to add it.
We haven't done it yet since we need to push out a new version of our webhooks out (to add blocked as a state to builds and jobs and as an event) but we haven't gotten around to it yet. We've got a PR internally to finish this off in the new year though!


[$1000] Android - letter "g" is cut off from the bottom in the IOU card when the language is spanish

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login the app with 2 different accounts as user A and user B, user A should be on android.
As user A, Go to settings> preferences> language>  choose spanish.
As user B, send a money request to user A.
From user A, go to user B chat report and notice the  "g" letter in "pagar" is cut off from the bottom in the IOU card.

Expected Result:
"g" letter in "pagar" shouldn't be cut off from the bottom in the IOU card when the language is spanish.
Actual Result:
"g" letter in "pagar" is cut off from the bottom in the IOU card when the language is spanish.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.65-6
Reproducible in staging?: Y
**Reproducible in production?:**Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/91d1147a-c1df-461e-b265-32985fc22c00
https://github.com/Expensify/App/assets/115492554/0b0fa278-4731-43e5-b004-57a59de80b4a
Expensify/Expensify Issue URL:
Issue reported by: @ahmedGaber93
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693773598319289
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0113b4746fa8dbba09
Upwork Job ID:<PHONE_NUMBER>489021440
Last Price Increase: 2023-09-29

Proposal
Please re-state the problem that we are trying to solve in this issue.
Letter g is cut off in the IOU card when the language is Spanish
What is the root cause of that problem?
The button in IOU card is a ButtonWithDropdownMenu component(in SettlementButton)
In ButtonWithDropdownMenu, we set the button height with StyleUtils.getDropDownButtonHeight function
https://github.com/Expensify/App/blob/b119f9ab54e7cc7272702e270693896b352b61e0/src/styles/StyleUtils.ts#L1172-L1181
As you can see, we limit the button height to 40(for normal button). For normal button, font size is 13, and padding is 16 for both top and bottom. So the text height would be 16. This isn't enough for 13px font
This is the root cause
What changes do you think we should make in order to solve the problem?
We have min heights for buttons already here
https://github.com/Expensify/App/blob/b119f9ab54e7cc7272702e270693896b352b61e0/src/styles/styles.js#L490
https://github.com/Expensify/App/blob/b119f9ab54e7cc7272702e270693896b352b61e0/src/styles/styles.js#L499
https://github.com/Expensify/App/blob/b119f9ab54e7cc7272702e270693896b352b61e0/src/styles/styles.js#L509
I suggest not to limit the height of buttons to constants. We can use fit-content instead or simply remove height css.
This works as expected

Result

What alternative solutions did you explore? (Optional)

@Expensify/design thoughts on this? I think it's probably worth fixing if our button height isn't enough for our default font size and padding.
But if we decide to fix it, I'm going to reduce the bounty to $250 since this is a minor design issue rather than a bug that is impeding user action.

Yeah we should fix. Any idea why this only affects Android?

For anyone providing a proposal, please include in your RCA why this issue is only happening on Android (cc @s-alves10).

Ah, I wonder if instead of using so much vertical padding, can we just use some kind of flex display to align the text in the vertical center of the button? Otherwise we should reduce the padding and increase the line height I suppose.

Looks like we're still waiting on a proposal with full RCA. @s-alves10 do you want try to update yours to answer the questions above?

Raising bounty to try to get proposals.

Proposal
Updated

@parasharrajat mind taking a look at the updated proposal?

@parasharrajat have you had a chance to review?
Also, @s-alves10 you said this:

I think the reason that this issue happens only on android is the difference in font rendering between iOS, android, and desktop.

Could you expand on that? How is font rendering different on these devices? I also noticed the "g" getting cuttoff in the compose box of my iPhone SE recently and I'm wondering if it's the same problem.

I think digging into font-rendering details beyond the scope of this issue
But we can see various operating systems renders text differently in this article
Also we have similar issue in react native font rendering
https://github.com/facebook/react-native/issues/32384

What do you think @parasharrajat?

@parasharrajat bump.

Sounds good @parasharrajat. Let us know what you find.

Sounds good

Weird. I'm not sure why upwork offers weren't automatically sent.
@s-alves10 @ahmedGaber93 could you please apply to this job? https://www.upwork.com/jobs/~0140dad38648f3fa4e

Payment summary:

Bug reporter - @ahmedGaber93 - $50 (to be paid via Upwork)
C - @s-alves10 - $1000 (to be paid via Upwork)
C+ - @parasharrajat - $1000 (to be paid via NewDot)

@parasharrajat please go ahead and make the request on NewDot.

@puneetlath
Applied. Thanks

@puneetlath
Accepted the offer. Thanks

Upwork contracts paid. @parasharrajat will request on NewDot.
Thanks y'all!

$1,000 payment approved for @parasharrajat based on this comment.


[#3582] Samples (csharp_dotnetcore/adaptive-dialog) are not validating the age correctly

Fixes # 3582
Description
This PR fixes an issue when the bot asks for the user's age and when provided, it shows Sorry, 'XX' does not work. I'm looking for a value between 1-150..
Detailed Changes

Ask for the age step recognition, was changed from TextInput to NumberInput.

The ActivityTemplate AskUserAege was changed to AskUserAge to be more clear.
In the AskUserAge template, the No age suggested option, was changed to Will not give it, as LUIS was returning a coincidence with the age utterance, causing to return an age of 0 (zero).

06.todo-bot

NoValue intent score was changed from 0.9 to 0.8, due to not recognizing the step when No name was provided by a significant amount of 0.15.

08.todo-bot-luis-qnamaker

GetUserProfileDialog.qna ChitChat path was changed from [ChitChat](./ChitChat.qna) to [ChitChat](../RootDialog/ChitChat.qna). (Fixes # 2758)
Removed profile? from QnA, due to not recognizing Profile suggested action provided by the user.

This PR updates the following samples

05.interruptions-bot
06.todo-bot
08.todo-bot-luis-qnamaker

Testing
The following images show the bot unable to recognize the age, and the bot after the fix recognizing the age properly.

Promoted https://github.com/microsoft/BotBuilder-Samples/pull/3584


dashboard policy validations

@ericpgreen2 In GetCatalogEntry, we actually resolve the template using user attributes and evaluate the resultant expression that's why you will see errors if it fail during either resolution or expression evaluation. Currently we do not do that in PutAndReconcile as I thought user context might not be available always during local development as there might not be any user logged in. How do we solve this ? should we make sure if user is writing a policy, they have to provide user attributes for testing during local development or should we assume some test user attributes to validate the expressions ?
cc @begelundmuller

@pjain1 @ericpgreen2 While we don't have any user context when reconciling/validating a policy, we should be able to use a dummy payload to at least validate that the expressions and templating parses correctly. We could use a payload like this:
email<EMAIL_ADDRESS>domain: example.org
name: Mock User
groups: []
admin: false

@ericpgreen2 added validations with mock user data

@ericpgreen2 added validations with mock user data

So much better!


Update Updates.set to allow Bson value argument

Hi @tyilo thanks for the PR.
I have added a Jira ticket JAVA-5620 to track this improvement request.  It will be triaged in due course.
Cheers,
Ross


[TensorFlow -> ONNX] BiasAdd layer after DepthwiseConv2dNative is ommited

Platform (like ubuntu 16.04/win10): Win10
Python version: Python 3.6.4
Source framework with version (like Tensorflow 1.4.1 with GPU): tensorflow 1.14.0
Destination framework with version (like CNTK 2.3 with GPU): onnx 1.5.0
Pre-trained model path (webpath or webdisk path):
https://github.com/ARM-software/ML-KWS-for-MCU/blob/master/Pretrained_models/DS_CNN/DS_CNN_L.pb
Running scripts:
mmconvert                                        --srcFramework tensorflow                      --inputWeight DS_CNN_L.pb                      --inNodeName Reshape_1                         --inputShape 49,10,1                           --dstNodeName labels_softmax                  --dstFramework onnx                           --outputModel DS_CNN_L_mmdnn.onnx
When converting the above model, where the following groups are encountered (TensorFlow pb):

the BiasAdd layer is ommited and the resulting layer is this (ONNX):

You can see the bias operand of the convolution (B) is missing.
I actually verified the numerical behavior of the resulting ONNX model is NOT correct (using some actual input data and comparing to the original TensorFlow model).
I manually edited the ONNX proto in order to put the missing bias operands, after which the numerical behavior became correct.

@mciprian13 , thank you very much for the feedback. We will look into the issue.

@mciprian13 , it seems that function rename_DepthwiseConv2dNative() forgets to handle the BiasAdd. You may take the following workaround:

Go to the installation directory of MMdnn. E.g.  ~/.local/lib/pythonX.Y/site-packages/mmdnn , or /usr/lib/python3/dist-packages/mmdnn
Open file "conversion/tensorflow/tensorflow_frozenparser.py" .
Locate the rename_DepthwiseConv2dNative() function.
Add "self._get_bias(source_node, IR_node)" to the end.

Please have a try and verify whether the issue is fixed.
Thanks.

Fixed in the pull request https://github.com/microsoft/MMdnn/pull/800.