since some days the adapter crashed

Hello,
since some days the adapter crashes permanently.
Error in the log:
Unhandled  promise rejection.
This error originated either by throwing inside of  an async function without a catch block, or by
rejecting a promise which  was not handled with .catch().
statusText: undefined
statusCode: 500
(19695) unhandled promise rejection: null
I have tryed to downgrade from 1.5.3 -> 1.5.1 but same result.
Maybe it base on a other adapter ?
What can I do ?

Did you get an update for the software or did you change anything on the setup of ioBroker or the network?

no, I have updated some adapter like javascript, but noting for the iobroker in general

so any help? what can I do ?
2020-11-28 17:24:36.906  - error: stiebel-isg.0 (9435) statusCode: 500
2020-11-28 17:24:36.906  - error: stiebel-isg.0 (9435) statusText: undefined
2020-11-28 17:24:36.907  - error:  Unhandled promise rejection. This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch().
2020-11-28 17:24:36.907  - error: stiebel-isg.0 (9435) unhandled promise rejection: null
2020-11-28 17:24:36.908  - error: stiebel-isg.0 (9435) statusCode: 500
2020-11-28 17:24:36.909  - error: stiebel-isg.0 (9435) statusText: undefined
2020-11-28 17:24:36.909  - error:  Unhandled promise rejection. This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch().
2020-11-28 17:24:36.910  - error: stiebel-isg.0 (9435) unhandled promise rejection: null
2020-11-28 17:24:36.911  - error: stiebel-isg.0 (9435) statusCode: 500
2020-11-28 17:24:36.911  - error: stiebel-isg.0 (9435) statusText: undefined
2020-11-28 17:24:36.912  - error:  Unhandled promise rejection. This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch().
2020-11-28 17:24:36.912  - error: stiebel-isg.0 (9435) unhandled promise rejection: null
2020-11-28 17:24:36.913  - error: stiebel-isg.0 (9435) statusCode: 500
2020-11-28 17:24:36.914  - error: stiebel-isg.0 (9435) statusText: undefined
2020-11-28 17:24:36.914  - error:  Unhandled promise rejection. This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch().
2020-11-28 17:24:36.915  - error: stiebel-isg.0 (9435) unhandled promise rejection: null
2020-11-28 17:24:36.916  - error: stiebel-isg.0 (9435) statusCode: 500
2020-11-28 17:24:36.916  - error: stiebel-isg.0 (9435) statusText: undefined
2020-11-28 17:24:36.917  - error:  Unhandled promise rejection. This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch().
2020-11-28 17:24:36.917  - error: stiebel-isg.0 (9435) unhandled promise rejection: null
2020-11-28 17:24:36.918  - error: stiebel-isg.0 (9435) statusCode: 500
2020-11-28 17:24:36.919  - error: stiebel-isg.0 (9435) statusText: undefined
2020-11-28 17:24:36.920  - error:  Unhandled promise rejection. This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch().
2020-11-28 17:24:36.920  - error: stiebel-isg.0 (9435) unhandled promise rejection: null

I have checkt the software version in isg and attached an screenshot.

I have no access to the service portal, so no update in the last month.
I have tryed to update the cat version, but nothing change in the adapter 1.5.3 ist the version.
It would be great to finde a solution. It looks like the issue he try to connect to often and then isg is overloadet with requests.

Okay. A old version, 8.5.6. So that's not the problem.
If the ISG is under to havy load, you can set a higher interval in the adapter.

How i can update?
I set the interval ti 90 seconds, I think it is high enough
unltdnetworx<EMAIL_ADDRESS>schrieb am Sa. 28. Nov. 2020 um
22:26:

Okay. A old version, 8.5.6. So that's not the problem.
If the ISG is under to havy load, you can set a higher interval in the
adapter.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/unltdnetworx/ioBroker.stiebel-isg/issues/32#issuecomment-735292456,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF7HFJIFUX4CCCB3DPEDKBDSSFTHRANCNFSM4UERIQOA
.

You can update your ISG with the updater tool for windows or linux. I think it's only updating to 10.x or you get the stiebel-eltron test account and it will be updated by them.
Link to the updater (no more available on the german site):
https://www.stiebel-eltron.com/en/home/products-solutions/renewables/controller_energymanagement/internet_servicegateway/isg_web.html#downloads
I would recommend to clone the sd-card to back it up.

so I have updated my isg to v8.6.4 (the newest) and now it looks fine, no errors in the log for the moment.
Thx. for support me.
Thomas

Seems that this has to do with something according to the adapter or the environment, not the adapter itself.
With Version 10 the the modbus ability was in introduced. Maybe you should really try to take the demo license to update the ISG to the newest version. On the one hand you'll get the ability to use modbus, in the other hand the ISG software seems to react quicker.

In wich Intervall the Adapter will push data?
In the setting I can only see pull.
I had a test account there some years ago, so no longer possible and I would like the not invest to them.
Maybe a update of the JavaScript adapter?
Any other suggestions or only set the interval longer?

The adapter pushes values only if you change something. It waits about 10 seconds for other values to change and then pushes them as bundle to reduce the load onto the ISG.
The adapter is a standalone version and doesn't need other adapters to work. So I am a little confused about this phenomenon without any manual changes.
The adapter is like a little DDOS-attack to ISG, pulling values that often. So the only way to reduce the load on the server is to set the interval higher.
You could also try to clone the full sd-card inside the ISG to a new one and try this new one. Maybe the card comes to its end?

so I have requested a portal connection to stiebel, received a code and now I still waiting for an update of my isg.
Maybe it is possible for you to implement also to read the version number from isg and showing in the objects ?

so I updated to isg version 12.1 but no change.
Same errors in log and the the adapter crash and flag red. So it is not a problem of the isg

If you speak german, I've written a tutorial how to connect yout isg via modbus instead of the adapter. At the moment only for Lüftungsintegralgeräte. Maybe this helps you.
https://blog.unltd-networx.de/iobroker-stiebel-eltron-tecalor-waermepumpe-per-modbus-anbinden

i will try to use modbus


Mutations for poses other than default

Humans exported by massproduce for poses other than the default tend to have horrible mutations.
To see what I'm talking about:
Open MakeHuman 1.2.0
Switch the pose to fight03  (shows it particularly well)
Go back to the 'Modelling' tab, and drag the 'height' slider up and down without releasing it.
The human should develop hideous mutant hands!
But when you release the slider - PING! The human magically heals.
The problem is, the humans exported by massproduce don't magically heal before export - they're saved as mutants. I'm guessing there's some sort of expensive renormalising step which is only done when the slider is released, and that's not being triggered when massproduce alters the value manually?
Thanks for this great plugin! Other than this one problem, it's been great.

Thanks. I honestly never even considered what problems posing would cause.
But you're probably right that there is some magic redraw or update call we're missing here.

I've never done any coding on MakeHuman - should I be opening it up and looking for this? And if so, any clues as to where I should make a start?

Have you been able to fix this error somehow @TomGroves ?


[WIP] Initial implementation of asset serving in DashR

This PR proposes to provide support for locally serving assets from a specified assets folder. As in Dash for Python, the following features would be implemented upon merging these commits (/assets below refers to whichever folder is specified in assets_folder):

Assets folder auto resolution (/assets) at the root of the project by default.
Assets folder may be passed as parameter, customizing the path as desired
JS/CSS files in /assets are served in the index
An assets_ignore filter permits excluding assets matching specified regex
Assets are cached by the browser, and uncached when modified
All files in /assets are served statically
The generated assets URL respects routes/requests pathname prefix
Easy retrieval of assets URLs is possible: get_asset_url(asset) returns a ready-to-insert URL string
A favicon.ico is served as the title icon of the page, if in the root directory of /assets

There ~are~ is at least ~two~ one item~s~ that ~have~ has not yet been implemented, but which ~are~ is desirable:

~A favicon.ico is not currently served as the title icon of the page~
Automatic compression of served assets is not currently supported, but should be feasible

While the above features have been tested, formal tests asserting that these elements are provided should be be written. An example of the Python code which performs this task is available here:
https://github.com/plotly/dash/blob/master/tests/test_resources.py
Closes #46.

@alexcjohnson Let me know if this is looking a bit better; I've also added support for a favicon.ico in 74392b1.


Use SecretStr for kafka_ssl_password in KafkaConfig

There isn't currently a 3.0.0 release, so this stays with that version.
Switches the field type for KafkaConfig.kafka_ssl_password from str to SecretStr, and updates the generate_ssl_context() to get the secret value accordingly.
The impact is that depending services will need to run scripts/update_config_docs.py and scripts/update_readme.py

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 91.446%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
1657

Relevant Lines:
1812

💛  - Coveralls


Convert some scripts to use TS and use dev-rome

I recently added scripts/generated-files/lint-rule-docs.ts. It would be nice to move a lot of the scripts that aren't in the init-path for dev-rome into TypeScript that we can run with dev-rome and use our internal modules.

Resolved by #832.


TypeError: Cannot read property 'unmask' of undefined (Socket.io)

With a fresh npm install I am suddenly seeing an error to do with Karma's socket.io code. This is across different browsers (Chrome / PhantomJS) and systems (macOS / Ubuntu).
Expected behaviour
Karma starts, loads browser, connects to browser and then runs tests.
Actual behaviour
Karma starts, loads browser, and fails to connect to browser, instead receiving a syntax error:
START:
06 03 2017 16:39:59.624:INFO [karma]: Karma v1.5.0 server started at http://<IP_ADDRESS>:9876/
06 03 2017 16:39:59.626:INFO [launcher]: Launching browser Chrome with unlimited concurrency
06 03 2017 16:39:59.652:INFO [launcher]: Starting browser Chrome
06 03 2017 16:40:00.582:ERROR [karma]: TypeError: Cannot read property 'unmask' of undefined
    at Receiver.unmask (/Users/petemill/Development/Makook/dmktplc/admin-web/node_modules/engine.io/node_modules/ws/lib/Receiver.js:306:46)
    at Receiver.finish (/Users/petemill/Development/Makook/dmktplc/admin-web/node_modules/engine.io/node_modules/ws/lib/Receiver.js:505:25)
    at Receiver.expectHandler (/Users/petemill/Development/Makook/dmktplc/admin-web/node_modules/engine.io/node_modules/ws/lib/Receiver.js:493:33)
    at Receiver.add (/Users/petemill/Development/Makook/dmktplc/admin-web/node_modules/engine.io/node_modules/ws/lib/Receiver.js:103:24)
    at Socket.realHandler (/Users/petemill/Development/Makook/dmktplc/admin-web/node_modules/engine.io/node_modules/ws/lib/WebSocket.js:825:20)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at TCP.onread (net.js:548:20)
npm ERR! Test failed.  See above for more details.

Environment Details

Tested on 1.4.x and 1.5.x

Steps to reproduce the behaviour

Latest version of karma, karma-coverage, karma-mocha and karma-chrome-launcher
Run karma

Can ignore this - weird coding in ws package can cause conflict if more modern version of bufferutil and utf-8-validate packages are installed

I have the same issue. So what is the suitable version of bufferutil and utf-8-validate ?
I'm using 3.0.0 for buffuerutil and 3.0.1 for utf-8-validate

I also have the same issue after upgrading to a newer angular-cli (and updating karma). What's the solution? :)

@creat-or I downgraded the dependencies version for bufferutil and utf-8-validate and it worked.

Related: https://github.com/socketio/engine.io/pull/495
From what I can tell this should be fixed by getting rid of ws 1.1.2 and using ws 1.1.4 instead.
As soon as the new version of engine.io is released, can you guys update the dependency?

I'm having the same issue as @MiraLak . Using same dependencies 3.0.0 for bufferutil and 3.0.1 for utf-8-validate (socket.io 1.7.3).
What did you do to fix it? Downgraded what to what?
Should I need to downgrade it in socket.io node_modules or in my app package.json?

A workaround that works for me:

remove old node_modules/
run npm install --no-optional

This will prevent the "offenders" bufferutil and utf-8-validate from being installed. Everything should still work.

Hi, have the same issue and still nobody answered to previous question "Downgraded what to what?" and workaround doesn't work for me )

I have ws 1.1.4 and am still getting this error

#2880 ought to fix this issue.

Is there a plan when are you going to release this fix? This is a pretty serious issue for us because all of our unittests are failing.
Or is there any documentation about your release cycle or release plans?
Sorry if I'm missing something but I couldn't find anything about this.
Thanks


Ignore .exe files

Hi all :wave:
this PR adds an ignore case for .exe files. This because it's a bad idea to upload executables files, especially if they're only for one platform (Windows in this case).
Also removed all files .exe already uploaded

I'm sorry, I did not want to delete this PR :sweat_smile: @suryapratapsinghsuryavanshi

I'm sorry, I did not want to delete this PR 😅 @suryapratapsinghsuryavanshi

Okey!


Update expensify-common version

Details

Fixed Issues
$ https://github.com/Expensify/App/issues/44032
PROPOSAL: $ https://github.com/Expensify/App/issues/44032#issuecomment-2191745067
Tests

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Click on the text input
type _ ahead of a asterisk e.g. _*bold*
Press send
Verify in the chat the _ ahead of bolded bold

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/6c0ed66b-b9b7-42cc-aaf2-3839307f9e78

MacOS: Desktop

@parasharrajat  I think my fix is included in https://github.com/Expensify/App/pull/45556 already.

@parasharrajat is this issue still count to me?

@parasharrajat Sry for making you condused. I am asking if the payment still goes to me?

Close because the fix has been merged by another PR.


Nicola devel

@paolofrance  @ManuelBeschi  the merge is urgent!!!!!!!! I asked @paolofrance to start the merge just after Robothon!


Error synchronizeing OMIE prices

When synchronizing with www.omie.es, we are getting this error:
javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Full stacktrace here:
cert-error.log

It seems like this is a common issue when a client (in this case, conluz) is unable to authenticate the SSL certificate presented by the server.
This error message, PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, means that the Java client is unable to find the server's certificate or any of the certificates in the certificate chain in the local Java keystore. To solve this, we might need to add the SSL certificate into your Java application's truststore file.

How to generate a keystore
To generate a keystore for your Spring Boot app with a self-signed certificate, you can use the keytool command-line utility provided with the JDK. Here's an example:
keytool -genkeypair -alias spring -keyalg RSA -keysize 2048 -storetype PKCS12 -keystore keystore.p12 -validity 3650
This command explained:
-genkeypair: Generates a key pair (a public key and private key).
-alias spring: Specifies the alias name for the keystore entry.
-keyalg RSA: Specifies the algorithm to generate the key pair.
-keysize 2048: Specifies the size of the key to be generated.
-storetype PKCS12: Specifies the type of the keystore.
-keystore keystore.p12: Specifies the name of the keystore.
-validity 3650: Specifies the validity (in days) of the key pair (In this case 10 years).
You will be prompted for general information about this certificate, such as company, contact details etc. More importantly, the first question is about entering the keystore password.
The result will be a keystore file keystore.p12 in the directory you ran the command.
Now that you've created your keystore, you can tell Spring to use it for SSL encryption. In your application.properties file, add the following properties:
server.ssl.key-store=keystore.p12
server.ssl.key-store-password=<your-keystore-password>
server.ssl.key-store-type=PKCS12
server.ssl.key-alias=spring

Replace  with the password you entered when creating the keystore.
Please note that the self-signed certificate is not trusted by clients, it can prompt warnings to your users since it's not signed by a well known Certificate Authority that browsers normally trust. It's OK for local development, but for a production application, obtain a certificate from a trusted Certificate Authority.

Add OMIE cert to keystore
To do this, you will need to export the SSL certificate from www.omie.es. You can do this with your preferred browser, or you can use openssl command from your terminal:
echo | openssl s_client -servername www.omie.es -connect www.omie.es:443 2>/dev/null | openssl x509 > omie.pem
This command will retrieve the certificate and save it in a file named omie.pem.
Next, import this certificate into your keystore using the keytool:
keytool -import -alias omie -keystore conluz.p12 -file omie.pem
Replace path-to-keystore with the path to your Spring Boot application's keystore file.
Once this is done, the keystore used by your Spring Boot application will include the necessary certificate to establish an SSL connection with www.omie.es.
When your Spring Boot application makes a connection to www.omie.es, it will now have the certificate in its keystore and validation will be successful.
If asked to trust the certificate, type yes.


Is Bip.io community still alive?

It seems like Bip.io is the best alternative to Zapier at the moment considering that it's open source. Is it still alive?

Just following up on the previous reply. So what is happening with the project? Is anyone still working on it? I'd love to join and help.

It seems like no one is maintaining this anymore =(

That is pretty unfortunate.. I was hoping this project would take off! Of course one of us could always fork and keep it going ;) I just don't have time to work on it right now.

Yes
Sent from my iPhone

On Nov 15, 2016, at 5:20 AM, Jason Shin<EMAIL_ADDRESS>wrote:
It seems like Bip.io is the best alternative to Zapier at the moment considering that it's open source. Is it still alive?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi guys, I am building an open source reboot of Bipio. Our slack team is based in https://bipioteam.slack.com. Please request invitation to myself or @serri588 .
Core server - https://github.com/JasonShin/BipHub
Frontend - https://github.com/JasonShin/Biphub-frontend

Hi, I am building a open source clone of Bipio but with much newer tech stacks and coding standards. Development is currently going on and please come and join us.

@JasonShin are you still active in that slack channel? I see that things have been moved to https://gitlab.com/bipio and https://gitlab.com/biphub


febio: 4.7 -> 4.8; febio-studio: 2.7 -> 2.8.1

Things done
Follow up to https://github.com/NixOS/nixpkgs/pull/352943 which needs to be merged first.

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357044

x86_64-linux

:white_check_mark: 2 packages built:

febio
febio-studio

aarch64-linux

x86_64-darwin

:white_check_mark: 2 packages built:

febio
febio-studio

aarch64-darwin


IPDatabase: Support cloning of git:// remotes

This allows to clone repositories in environments that support neither
HTTPS nor SSH.  It is not secure but sometimes the only option.

Ciao @FrancescoConti, this has been successfully tested by me and an external collaborator, who asked for it due to the restricted environment described in the commit message.

that seems ok 👍


Plamen dev

set up locally poetry

I had some troubles mainly due to the poetry installation on my Linux machine. After some trial and error, I managed to pass it. However, I'd need help from someone to test on Windows and MacOS. Thanks,

I will test it on windows and update it here shortly. Thanks

I had some troubles mainly due to the poetry installation on my Linux machine. After some trial and error, I managed to pass it. However, I'd need help from someone to test on Windows and MacOS. Thanks,

I installed all the packages using poetry on windows. It successfully installed all packages.

I will in the future set up GitHub actions. We did this for pytimetk and we've identified a lot of issues with polars and pandas along with testing on various platforms.


IS : Custom claims lost when updating user profile

Moved from: https://wso2.org/jira/browse/IDENTITY-7335
Hi WSO2 team,
WSO2 Identity Server offers some extension points for instance ability to add custom claims.
This is normally donc by writing a custom claim handler as described in one wso2 post :
http://pushpalankajaya.blogspot.com/2014/07/adding-custom-claims-to-saml-response.html
When using WSO2 OAuth2.0 Playground sample and OAuth2.0 Authorization code grant type, custom claim handler is invoked normally when resource owner is authenticated.
Then at the end of process you get an access token enabling to retrieve, for instance, user info with customs claim ("computed before when custom claim handler is invoked).
If you update some information of user profile and request again user info from user info endpoint with access_token, all the +custom + claims are lost in provided response.
Actually, when you update user profile, information that were previously cached are emptied so when user info endpoint is called with access_token, user claims (and their corresponding values) are computed from userstore perspective only so that why custom claims are lost.
Would it be possible in that scenario of retrieving claims from userstore that custom claim handler would be also called to ensure that customs claims are available in answer?
Regards,
Franck

From @mefarazath

We store claims against token. When user claims update we clear the claims stored against the token.
Thereafter if u do userinfo calls then claims are retrieved from the user store..
So custom claims will be lost.
Best possible solution is to revoke the token if user claims are updated.
Anyways that too has practical issues. Consistency vs accuracy. If we don't clear the stored claims we might end up with stale values.
Improve the claim handling is also an option. So that even when we retrieve from the userstore custom claims can be injected.
Basically we ask for user claims from an API in any flow (framework or not) it returns the same claims.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


[Segment Replication] Add background checkpoint sync making SegRep more resilient to network failure

Is your feature request related to a problem? Please describe.
Today SegRep relies on a transport layer call from primary shards to replicas alerting them there are new segments to sync.  When a replica finishes a sync it will report back to the primary shard of its completion.  This ensures that primaries track the state of all of their replicas and use this to enforce SR backpressure if they fall too far behind.
These transport layer calls are made using a RetryableTransportClient, but if they were to outright fail it would require a future write and a primary refresh for the replica to fully sync.  This would mean replicas may never catch up or know to sync.
SR pressure was implemented to help mitigate lagging replicas by blocking writes giving replicas time to catch up.  However, in this scenario the replicas would never catch up and writes on the particular shard could be indefinitely blocked until a flush is triggered.
Describe the solution you'd like
As a safety mechanism add a background sync, similar to RetentionLease sync, from each primary that sends its latest checkpoint to its known stale replicas with the latest replication checkpoint and return the replica's current checkpoint to update tracking state.
Describe alternatives you've considered
Switch to a pull model from replicas. - https://github.com/opensearch-project/OpenSearch/issues/4577

closing this as search only replicas perform the pull based sync on a schedule.


[Feature Request] Add --disable-noqa option

This option would enable the disable_skip_errors flag in ConventionChecker.check() added in #485.
I don't have a need for this feature, but I mention it because pydocstyle doesn't have feature parity with flake8's --disable-noqa feature. This issue exists primarily for tracking purposes, feel free to close as "won't fix".

As I said in #485, I really find it unrealistic to expect every tool to implement every flag that Flake8 has even if they strive to support a sub-set of Flake8's features (e..g, #noqa) I'm not a maintainer here though, so I express this opinion to further support the maintainers if they choose to close this without implementing this


feat: Support @documentation (for Java initially)

Issue #, if available:
Resolves #427. Progresses on #359.
Description of changes:
Adds a validator that any use of @documentation on local services does not use any CommonMark markup, and augments the Java code generation to recognize @documentation anywhere it currently recognized @javadoc.
Also adds a test model for validation and Java for now.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

We need at least one instance of the actual trait,
instead of the /// short cut that I find... questionable...

The /// ... syntax is pure sugar for @documentation("..."), and by the time Smithy parses the model and gives it to us there's no difference. I can add at least one explicit @documentation trait just for completeness and help explain, but there's literally no difference in the model.
We can debate separately whether we want to use that syntax in our models. Personally I'd prefer it because it improves readability.
I'll also add background to the README.md (which I just realized I left out).


Follow up for connection status event

https://github.com/jxcore/jxcore-cordova/issues/96

Will be released in <IP_ADDRESS>

Already implemented into 0.1.0


MONGODB hangs in "Pending" state after latest "upgrade"

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes:
Which chart: stable/mongodb
What happened: install hangs in "Pending" status
What you expected to happen: it should pull the image and run
How to reproduce it (as minimally and precisely as possible):
run helm install --name test stable/mongodb
Anything else we need to know: This worked fine before mongodb upgraded to 4.0 yesterday. I have tried to use versions 3.6.5, 3.6, 3.7 and 4.0.
base $ kubectl describe deployment test-mongodb
Name:                   test-mongodb
Namespace:              default
CreationTimestamp:      Thu, 28 Jun 2018 14:00:44 -0500
Labels:                 app=mongodb
                        chart=mongodb-3.0.1
                        heritage=Tiller
                        release=test
Annotations:            deployment.kubernetes.io/revision=1
Selector:               app=mongodb,release=test
Replicas:               1 desired | 1 updated | 1 total | 0 available | 1 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  1 max unavailable, 1 max surge
Pod Template:
  Labels:  app=mongodb
           release=test
  Containers:
   test-mongodb:
    Image:      docker.io/bitnami/mongodb:3.6.5
    Port:       27017/TCP
    Host Port:  0/TCP
    Liveness:   exec [mongo --eval db.adminCommand('ping')] delay=30s timeout=5s period=10s #success=1 #failure=6
    Readiness:  exec [mongo --eval db.adminCommand('ping')] delay=5s timeout=5s period=10s #success=1 #failure=6
    Environment:
      MONGODB_ROOT_PASSWORD:  <set to the key 'mongodb-root-password' in secret 'test-mongodb'>  Optional: false
      MONGODB_USERNAME:
      MONGODB_DATABASE:
      MONGODB_EXTRA_FLAGS:
    Mounts:
      /bitnami/mongodb from data (rw)
  Volumes:
   data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  test-mongodb
    ReadOnly:   false
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
OldReplicaSets:  <none>
NewReplicaSet:   test-mongodb-79d67b4fcd (1/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  4m    deployment-controller  Scaled up replica set test-mongodb-79d67b4fcd to 1

Do any pods get created? What's the output of kubectl describe pod $PODNAME?

@prydonius - you just helped me figure out part of the issue. I created the storage class (had been removed without my knowlegde) I am now getting InvalidImageName
base $ kubectl describe pod test-mongodb-mongodb-5d857c74-f8bg6 -n=mongodb
Name:           test-mongodb-mongodb-5d857c74-f8bg6
Namespace:      mongodb
Node:           ip-172-20-60-8.us-east-2.compute.internal/<IP_ADDRESS>
Start Time:     Thu, 28 Jun 2018 15:33:54 -0500
Labels:         app=mongodb
                pod-template-hash=18413730
                release=test-mongodb
Annotations:    <none>
Status:         Pending
IP:             <IP_ADDRESS>
Controlled By:  ReplicaSet/test-mongodb-mongodb-5d857c74
Containers:
  test-mongodb-mongodb:
    Container ID:
    Image:          docker.io/bitnami/mongodb:%!s(float64=3.6)
    Image ID:
    Port:           27017/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       InvalidImageName
    Ready:          False
    Restart Count:  0
    Requests:
      cpu:      100m
      memory:   256Mi
    Liveness:   exec [mongo --eval db.adminCommand('ping')] delay=30s timeout=5s period=10s #success=1 #failure=6
    Readiness:  exec [mongo --eval db.adminCommand('ping')] delay=5s timeout=5s period=10s #success=1 #failure=6
    Environment:
      MONGODB_USERNAME:
      MONGODB_DATABASE:
      MONGODB_EXTRA_FLAGS:
    Mounts:
      /bitnami/mongodb from data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-gtjfp (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          False
  PodScheduled   True
Volumes:
  data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  test-mongodb-mongodb
    ReadOnly:   false
  default-token-gtjfp:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-gtjfp
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                 Age              From                                                Message
  ----     ------                 ----             ----                                                -------
  Warning  FailedScheduling       1m (x2 over 1m)  default-scheduler                                   PersistentVolumeClaim is not bound: "test-mongodb-mongodb" (repeated 4 times)
  Normal   Scheduled              1m               default-scheduler                                   Successfully assigned test-mongodb-mongodb-5d857c74-f8bg6 to ip-172-20-60-8.us-east-2.compute.internal
  Normal   SuccessfulMountVolume  1m               kubelet, ip-172-20-60-8.us-east-2.compute.internal  MountVolume.SetUp succeeded for volume "default-token-gtjfp"
  Warning  FailedMount            1m (x3 over 1m)  attachdetach-controller                             AttachVolume.Attach failed for volume "pvc-92946898-7b12-11e8-b2c6-021cbde021d2" : "Error attaching EBS volume \"vol-0d9f7fc28e8403a2e\"" to instance "i-08e34d79ce49b69c2" since volume is in "creating" state
  Normal   SuccessfulMountVolume  1m               kubelet, ip-172-20-60-8.us-east-2.compute.internal  MountVolume.SetUp succeeded for volume "pvc-92946898-7b12-11e8-b2c6-021cbde021d2"
  Warning  InspectFailed          7s (x7 over 1m)  kubelet, ip-172-20-60-8.us-east-2.compute.internal  Failed to apply default image tag "docker.io/bitnami/mongodb:%!s(float64=3.6)": couldn't parse image reference "docker.io/bitnami/mongodb:%!s(float64=3.6)": invalid reference format
  Warning  Failed                 7s (x7 over 1m)  kubelet, ip-172-20-60-8.us-east-2.compute.internal  Error: InvalidImageName

@pkelleratwork nice, glad you got the StorageClass issue resolved. Did you provide any values to change the image tag when deploying MongoDB?

@pkelleratwork no problem, and glad you got that working for you. I am curious how you got that InvalidImageName though, can you share what values you were providing?

We have seen that issue with the docker image tag before.
In theory, the issue was fixed in this PR https://github.com/kubernetes/charts/pull/5893.
@pkelleratwork could you check if your _helpers.tpl include the following snippet for the image name?
{{/*
Return the proper image name
*/}}
{{- define "mongodb.image" -}}
{{- $registryName :=  .Values.image.registry -}}
{{- $repositoryName := .Values.image.repository -}}
{{- $tag := .Values.image.tag | toString -}}
{{- printf "%s/%s:%s" $registryName $repositoryName $tag -}}
{{- end -}}

The key thing is the toString function in the tag line.


Deploy snowpack frontend

Create a pipeline to deploy what is currently built to display the snowpack data

simple CICD pipeline now implemented in PR#10

open pr - creates ephemeral deployment in dev, updates the comment for the pr with the ephemeral route.
close pr - tears down the ephemeral env created for the PR and deploys to prod.

PROD Url: https://snowpackdata-prod-frontend.apps.silver.devops.gov.bc.ca/


SOLR-16196: Fixes for 9.0 release

Merge after https://github.com/docker-library/official-images/pull/12406 is merged, adding any more changes here as needed.
After this is merged, immediately delete the auto-created PR that will be made in https://github.com/docker-library/official-images, as this is just mirroring the changes already made in the PR above.

Edited for the guidelines given in: https://github.com/docker-library/official-images/pull/12406#issuecomment-1124393213

All the gpg invocations ought to have --batch on them (the way it's been explained to me in the past by GnuPG developers is that it switches GnuPG from "UI / UX mode" into "API mode"), but otherwise this looks OK to me. :+1:

Thanks for the review @tianon !


Update .Net Docker version 3.1 to 5.0

Summary
change dotnet version to the latest version

 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: edsulaiman sign nowYou 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 sign our Contributor License Agreement before we can accept your contribution.:x: edsulaiman sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


V1.2.0 packaging is broken

The packaging of V1.2.0 fails due to addition of an additional require node.js module. In addition it add the demo sources and compiled libraries in the package.
More over the version number is not updated

Fixed in Tag V1.2.1


Code completion over packages

Would be nice if you could auto complete also the functions in the packages like R Studio does.

It should do so at least in library and require calls, doesn't it?
On Sat, Nov 4, 2017, 20:33 Peter Rijnbeek<EMAIL_ADDRESS>wrote:

Would be nice if you could auto complete also the functions in the
packages like R Studio does.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/holgerbrandl/r4intellij/issues/132, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAMQ-N1JP5U5bJxyJ6BrEu3RbNUWtI77ks5szLwLgaJpZM4QSIUx
.

No if I for example install devtools this does not autocomplete:
Install_github
From: Holger Brandl<EMAIL_ADDRESS>Reply-To: holgerbrandl/r4intellij<EMAIL_ADDRESS>Date: Sunday, 5 November 2017 at 15:29
To: holgerbrandl/r4intellij<EMAIL_ADDRESS>Cc: Peter Rijnbeek<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [holgerbrandl/r4intellij] Code completion over packages (#132)
It should do so at least in library and require calls, doesn't it?
On Sat, Nov 4, 2017, 20:33 Peter Rijnbeek<EMAIL_ADDRESS>wrote:

Would be nice if you could auto complete also the functions in the
packages like R Studio does.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/holgerbrandl/r4intellij/issues/132, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAMQ-N1JP5U5bJxyJ6BrEu3RbNUWtI77ks5szLwLgaJpZM4QSIUx
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/holgerbrandl/r4intellij/issues/132#issuecomment-341977177, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG6oiXKQ29nEIIyW17FSU4GipajLaaroks5szcYrgaJpZM4QSIUx.

This certainly works:

No for me:
<EMAIL_ADDRESS>Same if I use require.
What is the difference with your version?
From: Holger Brandl<EMAIL_ADDRESS>Reply-To: holgerbrandl/r4intellij<EMAIL_ADDRESS>Date: Wednesday, 8 November 2017 at 16:43
To: holgerbrandl/r4intellij<EMAIL_ADDRESS>Cc: Peter Rijnbeek<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [holgerbrandl/r4intellij] Code completion over packages (#132)
This certainly works:
[image]https://user-images.githubusercontent.com/200952/32557960-f0089e9e-c4a3-11e7-89eb-609d674cacc3.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/holgerbrandl/r4intellij/issues/132#issuecomment-342857311, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG6oiaC4b4KMW0X4K0nrB-nRKqzWSWpKks5s0cwigaJpZM4QSIUx.

Do you see a R Skeletons tree in the project's "External Libraries", like


Button to copy selected id stops working

In the list of selected ids for a segmentation layer, the clipboard button to copy an id frequently stops working (under both Chrome and Edge on OS X). I haven't figured out an event to trigger this, but typically after using a state for some time doing the usual mix of navigation and edits, the button will no longer turn green when pressed and will not copy the segment id. Refreshing the page always restores function, so I imagine some button state is not being reset under some condition.

In case others find this, just a note that clicking in the Segment Selection text entry box normally fixes this without a reload.

In case others find this, just a note that clicking in the Segment Selection text entry box normally fixes this without a reload.


[5.7] Added test helper to assert that a Job has been queued with a Chain

This PR adds a new test helper when testing Jobs and allows to check if a Job was pushed with a specific Chain. The expectedChain can be an Array of Classes or Array of Objects.
This PR is a continuation of #23381 and addresses @taylorotwell concerns on checking only for the first Job. This PR tries to fix that situation.
Hopefully it is ready now.
Cheers.

Any big reason you sent this to master branch instead of 5.6?

Please send to 5.6 branch.

Sure @taylorotwell. Will add this to 5.6 branch.


React upgrade and cleanup - step I: Upgrade to latest version

Encode versions:
react: 0.12.2
react-bootstrap: 0.15.1
babel-preset-es2015: 6.6.0
babel-preset-react: 6.5.0
update the following: /develop/snovault/npm-shrinkwrap.json
/develop/snovault/package.json
/node_modules/react/

Steps so far: updated package.json (ncu -u) and deleted npm-shrinkwrap.json. In package.json, added the following:
"react": "^15.3.1",
"react-dom": "^15.3.1",
"react-bootstrap": "^0.30.3"
And deleted react-forms.
Completely rebuilt dependencies, made a new shrinkwrap, and now am purging js files. All of this is being done on a new branch, react_upgrade. After getting a minimal working homepage (at least), I will start to put js files back in.

Here, I will keep a list of major react changes that must be done for the upgrade.
Changes
implement react-dom
get rid of CloneWithProps

hey this is cool, I'm guessing the encode guys would be interested in the bullet points of what all was needed once your done, so we can send it on to them after you got it all sorted.

With newer versions of React, we know have the choice of using React.createClass (the traditional way) or ... extends React.Component (the new, ES6 way). A nice summary is here: https://toddmotto.com/react-create-class-versus-component/
For the time being, since we're on a tight schedule and already are using mixins (which are NOT supported with extends React.Component), I will stick with React.createClass. Maybe we should revisit this later.

Running into the setProps problem repeatedly, so I'm gonna jump to phase II - implement Redux, even though all the JS isn't yet put back in.


Fix WARNING box format in filters.md

Fix format for the WARNING box with the following sentence::

Only configure IFilterFactory.IsReusable to return true if the source of the filters...

Hopefully this will fix the broken rendering on the live site:

Thanks @guardrex I see there's no rest for the weary (it's 2am here and I am still up trying to assimilate the sum of all ASP.NET knowledge :grin:)

Thanks @guardrex I see there's no rest for the weary (it's 2am here and I am still up trying to assimilate the sum of all ASP.NET knowledge :grin:)


Issue/pagination fix iso6

Description

Short description here *

closes Add ticket reference here
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Processing this pull request

Pull request rejected by merge tool. This pull requests's target branch is master but it is not in the change entry's destination branches 'iso6'

Processing this pull request

Merged into branches iso6 in b73f2cb473c3e0c675fbb1c22d42625a2fbcd5f8


Recycling multiple files, and switching to another tab results in an app crash

Describe the bug
Moving multiple files to the recycle bin, and switching to another tab results in an app crash
To Reproduce
Steps to reproduce the behavior:

Moving multiple files to the recycle bin
switch to another tab
Observe crash

Expected behavior
Obviously no crash here. We need to find a better way to associate the current app instance with the AppService connections
Screenshots

Additional context
Files.IShellPage.FilesystemViewModel.get returned null.
Maybe @gave92 has a solution for this one? I'd propose passing the current app instance to the AppService connection for each request.

@duke7553 hi! could you confirm if something like the following is sufficient to solve the issue? (sorry I'm pasting code below, I'll make a proper PR when I can)
In App.xaml.cs -> Connection_RequestReceived
// If we are currently displaying the reycle bin lets refresh the items
if (App.CurrentInstance.FilesystemViewModel?.CurrentFolder?.ItemPath == path)
{
    await Windows.ApplicationModel.Core.CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(CoreDispatcherPriority.Normal,
    () =>
    {
        // Let's check again in case current folder has changed
        if (App.CurrentInstance.FilesystemViewModel?.CurrentFolder?.ItemPath == path)
        {
            App.CurrentInstance.FilesystemViewModel.RefreshItems();
        }
    });
}


chore(main): release 0.15.8

:robot: I have created a release beep boop
0.15.8 (2023-04-10)
Bug Fixes

intro: add sub-figure titles (25e3e7f)
intro: 程序 -> 应用 (f7b8b1f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/CCXXXI/thesis/releases/tag/v0.15.8 :sunflower:


Does the device need to be jailbroken?

Hi
I am unable to use this framework as it needs to connect via ssh. As far as i know, you need to jailbreak the device to do it, isnt it?
Does this tool work by loading the .ipa directly from the computer, or connecting to a non-jailbroken device?

The majority of features work by connecting via SSH, so you'll need a jailbroken device for those.  A few things might work without a jailbroken device, but not much.

Note that you still need to have an SSH server running on the device (get it using Cydia) even if you are connecting via USB.
http://www.idbtool.com/documentation/setup.html

You can also run it against XCode's iOS simulator, but again functionality may be somewhat limited.


fix: drops max count

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #10706
[x] adjust flaky tests

Hmm, I think the limited specs of the current runner cause flaky tests from e2e. Since running e2e tests is quite heavy, we need to increase the specs: https://docs.github.com/en/actions/using-github-hosted-runners/about-larger-runners/about-larger-runners

Please can you do the test fixes and and max count in two separated prs?

Please can you do the test fixes and and max count in two separated prs?

sure, let me revert first

sure, let me revert first

waiting for

the test fixes

Updates: I refactored some stuff on composable for drops. and, I just found out that this composable prevents the user from closing the modal composables/useModalIsOpenTracker.ts

Updates: I refactored some stuff on composable for drops. and, I just found out that this composable prevents the user from closing the modal composables/useModalIsOpenTracker.ts

I also find this error when I'm working on another issue. Here is how I solved it. WDYT https://github.com/kodadot/nft-gallery/pull/10772/commits/643eb8e5f8e6deeb9771ea4c3ac6a4b233885095

I also find this error when I'm working on another issue. Here is how I solved it. WDYT 643eb8e

oh, I like yours

added #10804 see context
@preschian you've got some conflicts
@vikiival  can we merge,

@vikiival can we merge,
Y

merging this~


Automated cherry pick of #2447: scheduler: sku not unmarshal to ServerConfigs

Cherry pick of #2447 on release/2.10.0.
#2447: scheduler: sku not unmarshal to ServerConfigs

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@03384ed). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #2450   +/-   ##
================================================
  Coverage                  ?   7.53%
================================================
  Files                     ?     410
  Lines                     ?   63884
  Branches                  ?       0
================================================
  Hits                      ?    4814
  Misses                    ?   58659
  Partials                  ?     411

Flag
Coverage Δ

#aFlag
7.53% <0%> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/cmdline/helper.go
46.57% <0%> (ø)

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 03384ed...4337e80. Read the comment docs.

/lgtm

/approve


frdm_k64f：the test case tests/subsys/logging/log_switch_format/logger.syst.v2.immediate/ blocks

Describe the bug
When running the twister command , the test case blocks at "SYST Sample Execution Completed". And the test case add in this commit: 1c1748d5795ced54cbf2b8242b0d4010cbf1781e. Before the DEVICE log, there is a DEBUG log "DEBUG   - Could not find a matching testcase for logger.syst.v2.immediate" ,this may provide a clue.
To Reproduce
Steps to reproduce the behavior:

source zhephyr-env.sh
twister -p frdm_k64f --device-testing --hardware-map map.yml -T tests/subsys/logging/log_switch_format/ -vv
See error

Expected behavior
The test log goes pass as expected.
Impact
The test blocks at "SYST Sample Execution Completed".
Logs and console output
*** Booting Zephyr OS build zephyr-v3.1.0-165-g90537fe447d6  ***
Running TESTSUITE test_log_switch_format
===================================================================
START - test_log_switch_format_success_case
SYS-T RAW DATA: 220A000B1700C0000000000000004572726F72206D657373616765206578616D706C652E00
hello sys-t on board frdm_k64f
[00:00:00.029,000] ^[[1;31m<err> log_switch_format: Error message example.^[[0m
hello sys-t on board frdm_k64f
SYS-T RAW DATA: 220A000B17008B010000000000004572726F72206D657373616765206578616D706C652E00
hello sys-t on board frdm_k64f
SYST Sample Execution Completed

Environment:
OS: Linux,
Toolchain Zephyr SDK 0.14.1
Commit SHA or Version: 0a758c36c864cc138941848f42c8ea4aa7dc95b3

@aasthagr could you look into this?

Sure, I will take a look.

The testcase tests/subsys/logging/log_switch_format/logger.syst.v2.immediate does pass. It doesn't fail or is not blocked as it executes till the "PROJECT EXECUTION SUCCESSFUL" and twister does indicate it as a passing testcase. See below:

I do see the line below in logs which you have indicated, but its just a DEBUG log. I am not sure what that means though, because the testcase is identified and executed by twister:
DEBUG   - Could not find a matching testcase for logger.syst.v2.immediate

Sorry maybe the description is not very accurate, this should really be the problem of twister. This problem is only seen when using the twister command.


Provide an example and dockerfile to build a nodejs app using extension and UBI

TODO
In order to extend the upstream testing coverage, can you please take care about the following todos please :

[ ] Provide a github nodejs example project (as discussed here: https://github.com/redhat-buildpacks/builders-spike/issues/1)
[ ] Design a Dockerfile able to install during the build phase the needed nodejs RPMs
[ ] Have a README documenting how to use & test the project using the UBI builder image and Dockerfile

Questions:

Should we also test the run image supporting too a Dockerfile ?

@mhdawson

@cmoulliard can you add some context to this?  There are already instructions on how to build/use what we have so far in the upstream work here - https://github.com/paketo-community/ubi-nodejs-extension
That will change as the PRs related to the ubi stack land but it will likely remain the best place for instructions on how to use what we have in place so far.
I'm not quite sure what this is for: Design a Dockerfile able to install during the build phase the needed nodejs RPMs. The extension generates a docker file which is applied by the builder so no separate docker file should be needed.
This existing example can be built and run although it would be missing the back end database - https://github.com/nodeshift-starters/nodejs-rest-http
@cmoulliard maybe it makes sense for the two of us to get together so that I can share what all is in flight and better understrand what you need from our team.

can you add some context to this? There are already instructions on how to build/use what we have so far in the upstream work here - https://github.com/paketo-community/ubi-nodejs-extension

For sure. The reason why I developed this project and recently added github actions is to b able to validate upstream our runtimes using: pack, tekton, quarkus client, shipwright and to be sure that our builders + some test cases will work. This is the purpose of this ticket

I'm not quite sure what this is for: Design a Dockerfile able to install during the build phase the needed nodejs RPMs. The extension generates a docker file which is applied by the builder so no separate docker file should be needed.

Ok. So I will remove this request from the ticket description as N/A ;-)

See project documenting how to use nodejs with UBI image: https://github.com/paketo-community/ubi-nodejs-extension

Error reported by the job https://github.com/redhat-buildpacks/testing/actions/runs/5378308526/jobs/9757934836?pr=21
===> EXTENDING
Running the 'extender' on OS 'linux' with:
Container Settings:
  Args: '/cnb/lifecycle/extender -app /workspace -log-level debug'
  System Envs: 'CNB_EXPERIMENTAL_MODE=warn CNB_PLATFORM_API=0.12'
  Image: 'pack.local/builder/636a636e7274686c7574:latest'
  User: 'root'
  Labels: 'map[author:pack]'
Host Settings:
  Binds: 'pack-cache-library_test-app_latest-c58426545694.build:/kaniko pack-layers-xgwsrwffem:/layers pack-app-hbkwqaymys:/workspace'
  Network Mode: 'host'
[extender] Extending base image for build: container-registry.local:5000/quarkus-pack-hello@sha256:277dbc51909926d92573d50f6f49401dee21901afb709413c834fbffda70aad4
[extender] Starting build
[extender] Running build for buildpack<EMAIL_ADDRESS>[extender] Looking up buildpack
[extender] Finding plan
[extender] Creating plan directory
[extender] Preparing paths
[extender] Running build command
[extender]
[extender] Paketo Buildpack for CA Certificates 3.6.0
[extender]   https://github.com/paketo-buildpacks/ca-certificates
[extender]   Launch Helper: Contributing to layer
[extender]     Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
[extender] Processing layers
[extender] Updating environment
[extender] Reading output files
[extender] Updating buildpack processes
[extender] Updating process list
[extender] Finished running build for buildpack<EMAIL_ADDRESS>[extender] Running build for buildpack<EMAIL_ADDRESS>[extender] Looking up buildpack
[extender] Finding plan
[extender] Creating plan directory
[extender] Preparing paths
[extender] Running build command
[extender] Paketo Buildpack for Node Engine 1.3.0
[extender]   Resolving Node Engine version
[extender]     Candidate version sources (in priority order):
[extender]       package.json -> "18 || 16"
[extender]       <unknown>    -> ""
[extender]
[extender] failed to satisfy "node" dependency version constraint "18 || 16": no compatible versions on "ubi8-paketo" stack. Supported versions are: []
[extender] ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 51

Can you help me ? @mhdawson

@cmoulliard it looks like you don't have the extension as part of the builder. We have seen that error when the builder has not been build correctly to include the extension.
Looking at the output in what you posted I see:
Creating builder with the following buildpacks:
-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
I don't see the extension there, but it is possible that it does not report extensions.
What does your builder.toml look like?

What does your builder.toml look like?

See: https://github.com/redhat-buildpacks/testing/blob/5650a2c010b7ed44d2459989b738e55a1976ddf0/.github/nodejs_ubi_builder.toml

I would try the extra step in https://github.com/paketo-community/ubi-nodejs-extension/pull/6/files

I would try the extra step in https://github.com/paketo-community/ubi-nodejs-extension/pull/6/files

You mean -> building the extension by executing the bash script build.sh ? @mhdawson

You mean -> building the extension by executing the bash script build.sh ? @mhdawson

I updated the github action to include the build step

Job is failing during export step: https://github.com/redhat-buildpacks/testing/actions/runs/5379904652/jobs/9761804922?pr=21#step:5:880
In order to verify if the procss is working end to end, I also executed it locally and got also an error locally which is a bit different
===> EXPORTING
Running the exporter on OS linux with:
Container Settings:
  Args: /cnb/lifecycle/exporter -daemon -launch-cache /launch-cache -log-level debug -app /workspace -cache-dir /cache -stack /layers/stack.toml test-app
  System Envs: CNB_USER_ID=1000 CNB_GROUP_ID=1000 CNB_PLATFORM_API=0.10
  Image: buildpacksio/lifecycle:0.17.0-pre.2
  User: root
  Labels: map[author:pack]
Host Settings:
  Binds: pack-cache-library_test-app_latest-c58426545694.build:/cache /var/run/docker.sock:/var/run/docker.sock pack-cache-library_test-app_latest-c58426545694.launch:/launch-cache pack-layers-acfprmxfpx:/layers pack-app-dwbnxjsgty:/workspace
  Network Mode: host
[exporter] ERROR: failed to export: get run image top layer SHA: image "test-app" has no layers
ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 62
[5:38](https://redhat-internal.slack.com/archives/C04T5P4FVN2/p1687793921704069)

IMPORTANT: The local value of CNB_PLATFORM_API is 0.10 vs 0.12 when the job is executed by github !

See gist: https://gist.github.com/cmoulliard/c5cafc8d52934c6a42f84532e7dbc981#file-gistfile1-txt-L1

Created PR to fix that - https://github.com/paketo-community/ubi-nodejs-extension/pull/7


Openssl 3.0.0+quic

Rebase onto 3.0. Very clean! Only CHANGES.md and VERSION.dat had conflects.

Checklist

[X] documentation is added or updated
[X] tests are added or updated

Checks are failing in "check_docs", specifically make md-nits; in at least one file that isn't modified by QUIC.
Another issue is in "external_test_pyca" test=TestRSA.test_generate_rsa_keys[3-2048]. It appears related to RSA key generation, which is not touched by QUIC.
I made a tweak to CHANGES.md, and I'm not seeing the same issue locally with ./config && make md-nits. So...?

I made a tweak to CHANGES.md, and I'm not seeing the same issue locally with ./config && make md-nits. So...?

I think it's "known" that md-nits will pick up different things depending on the version of the markdown libraries/tools you have installed

Waiting on queued checks to complete before merging.

In case it takes too long for GitHub to run them...
The original run: https://github.com/quictls/openssl/actions/runs/1209540222

Added fixes for the nits and the "make update" issue.

CIFuzz / Fuzzing (pull_request) seems to be failing due to something unrelated to QUIC:
: error: unsupported option '--with-fuzzer-lib=/usr/lib/libFuzzingEngine'

Everything but the CIFuzz passed. @nibanks @kaduk


Restrict the set of files which is excluded by filename

This change removes the automatic exclusion for all filenames where no specific example of this requirement could be found. The code generators for the files that are not eligible for analysis use <auto-generated> (or <autogenerated>) in the generated code, which causes the exclusion to occur by content instead.
Fixes #848
Fixes #849
Fixes #850
Fixes #851
Fixes #854

:+1:


Unable to load handler matching mongoose: Cannot find module 'mongoose'

Hi, when trying to add a mongodb data-source and create an API to use it, I get the following error in the gateway container logs, I know this is a gateway issue, but I felt it would be best here as I used the docker composer to build my stack.
any assistance would be greatly appreciated, thanks :)
2021-09-11T13:58:19.540Z pid: 20 [router] error: Error: Unable to load handler matching mongoose: Cannot find module 'mongoose'
Require stack:
/usr/local/share/.config/yarn/global/node_modules/graphql-compose-mongoose/lib/types/MongoID.js
/usr/local/share/.config/yarn/global/node_modules/graphql-compose-mongoose/lib/index.js
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    at getPackage (/usr/local/share/.config/yarn/global/node_modules/@graphql-mesh/config/index.cjs.js:67:23)
    at async getHandler (/usr/local/share/.config/yarn/global/node_modules/@graphql-mesh/config/index.cjs.js:74:23)
    at async Promise.all (index 0)
    at async /usr/local/share/.config/yarn/global/node_modules/@graphql-mesh/config/index.cjs.js:245:50
    at async Promise.all (index 0)
    at async Promise.all (index 0)
    at async Object.processConfig (/usr/local/share/.config/yarn/global/node_modules/@graphql-mesh/config/index.cjs.js:240:84)
    at async getMeshForApiDef (/usr/local/share/.config/yarn/global/node_modules/@graphql-portal/gateway/dist/src/server/router.js:126:28)
    at async buildApi (/usr/local/share/.config/yarn/global/node_modules/@graphql-portal/gateway/dist/src/server/router.js:79:12)
    at async Promise.all (index 2)
2021-09-11T13:58:19.540Z pid: 20 [router] error: Could not get schema for API, endpoint /test won't be added to the router

I also want to add, that I ran through the guided tour to add the pets API, and that works perfectly

resolved, added && yarn global add mongoose before && graphql-portal in the container command.
"/bin/sh" "-c" "echo 'Waiting for 10 seconds for Dashboard to come online...' && /bin/sleep 10 && cd /opt/graphql-portal && yarn global add mongoose && graphql-portal"


Update README.md

Thanks for sharing Inferno! Very intrigued by your work, particularly the focus on performance, to address usability on low-powered devices. Made a few tweaks to your README to correct a few typos and such, that I encountered.

@aarontam thank you very much for the PR :)
If you're interested in joining in on the discussion and helping more, send me your email and I can invite you to our Slack. My email is<EMAIL_ADDRESS>


[DOC-8203] Document limitation on modifying Kubernetes labels when using the Operator

[DOC-8203] Document limitation on modifying Kubernetes labels when using the Operator
Previews
src/current/v22.1/orchestrate-a-local-cluster-with-kubernetes.md
src/current/v22.1/orchestrate-cockroachdb-with-kubernetes-multi-cluster.md
src/current/v22.1/deploy-cockroachdb-with-kubernetes.md
src/current/v22.1/deploy-cockroachdb-with-kubernetes-insecure.md
src/current/v22.2/orchestrate-a-local-cluster-with-kubernetes.md
src/current/v22.2/orchestrate-cockroachdb-with-kubernetes-multi-cluster.md
src/current/v22.2/deploy-cockroachdb-with-kubernetes.md
src/current/v22.2/deploy-cockroachdb-with-kubernetes-insecure.md
src/current/v23.1/orchestrate-a-local-cluster-with-kubernetes.md
src/current/v23.1/orchestrate-cockroachdb-with-kubernetes-multi-cluster.md
src/current/v23.1/deploy-cockroachdb-with-kubernetes.md
src/current/v23.1/deploy-cockroachdb-with-kubernetes-insecure.md

@mdlinville can we merge this?

@mdlinville can we merge this?

I asked for @nickvigilante's help because this is prevented from merging due to the Netlify issue.


Add future_if_past

If a time gives a date < now, and future_if_past is true, we bump the date to the next day
Wrapped the flag into a Cfg object if ever we expand the parameters in the future

Thanks for your contribution.
Feature
This feature makes sense, implementation and test looks good.
Cfg and API
I have mixed feeling regarding the Cfg struct: I doubt the parameters will need to be extended and it looks cumbersome.
I would rather keep now as a standalone parameter for now instead of burying it under a struct:
I prefer:
pub fn evaluate<Tz: chrono::TimeZone>(
    time_clue: TimeClue,
    now: DateTime<Tz>,
    /// assume next day if only time is supplied and time < now
    assume_next_day: bool,
) -> Result<DateTime<Tz>, EvaluationError> {...}

over
pub fn evaluate<Tz: chrono::TimeZone>(
    time_clue: TimeClue,
    cfg: &Cfg<Tz>,
) -> Result<DateTime<Tz>, EvaluationError> {...}

Note: evaluate is a pub fn so modifying its signature is a breaking API change, for this reason I would rather rename it to keep backward compatibility:
/// same as evaluate_time_clue(time_clue, now, false)
/// ie assume times are relative to current day, even if time is past
pub fn evaluate<Tz: chrono::TimeZone>(
    time_clue: TimeClue,
    now: DateTime<Tz>,
) -> Result<DateTime<Tz>, EvaluationError> {evaluate_time_clue(time_clue, now, false)}

pub fn evaluate_time_clue<Tz: chrono::TimeZone>(
    time_clue: TimeClue,
    now: DateTime<Tz>,
    /// assume next day if only time is supplied and time < now
    assume_next_day: bool,
) -> Result<DateTime<Tz>, EvaluationError> {...}

I will be happy to merge your PR with these changes if you are okay with them.
Thanks again.

It is done! :)


uplift to java 21 and spring boot 3, pom sorting and flattening

Updated to Spring Boot 3 and Java 21, added a .editorconfig (adjust and reformat as needed), introduced pom sorting and flattening for consistency

Hi @ulisesbocchio  any idea when this PR can be merged ?


✨[feature Request]: FAQ enhancing

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
In the FAQ section, the question and the answer are not on separate lines, which makes it visually unappealing. I want to separate the question and the answer to improve readability.
Use Case
as reader the visibility
Benefits
This change in the FAQ enhances the readability of the website.
Add ScreenShots

Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@biswajit-sarkar-007 update ur branch and please check correctly


Bug: eqMac has disappeared from the Menu Bar, with no way to open the app at all

Disclaimer:

[x] I have checked for a similar issue and sure it hasn't been reported before.

Describe the bug
I am finding since the latest Mac OS release, the eqMac item no longer appears in the menu bar at the top.
I have always had it in the mode that eqMac only appears in the Menu Bar.
Because of this, I can no longer access eqMac.
Things I have tried:

Quitting eqMac with Activity Monitor and then restarting
Restarting my Mac.
Reinstalling latest eqMac.
Removing other items from my menu bar (in case the issue was I had too many items)
I have gone into my Control Center settings and nothing appears to fix. eqMac is not an option in there.

I would happily run the app as an item in my dock at the bottom of the screen, but I cannot even open the app to change this setting.

I'm having the same issue. I tried similar steps to resolve the issue.

Can you open eqMac if you Cmd + Space and search for eqMac.app
Or open it from the Applications directory and then go to Settings and tell me which Icon Placement is set:

It should be either Both or Status Item for the icon to appear on the top bar

@nodeful it won't open at all. It was set to "Status Bar" previously.

Do you have any crash reports related to eqMac or CoreAudio in Console.app? (under Crash Reports tab)

Also what if you use Exposé (like the 4 finger up motion on the trackpad or the Function button (for me it's F3)) do you see the window appear?

Using 4 finger thing:

I can see that eqMac is running through activity monitor

How do I find these crash reports? Sorry not sure where you mean.
Thanks for helping!

Just found the crash reports...
Nothing I'm afraid.
I closed eqMac via Activity Monitor and restarted too.

I think the app is running fine. I just have no way to actually interact with it

And the Audio Output device is set to the driver or not?

Do you mean this?

I think that used to have eqMac as an option, but can't say 100%.

So something is blocking eqMac from accessing internet I think, even though it should not be a requirement to have internet, but just to check:
Visit this page in the browser: https://ui.eqmac.app/v5/success.html
Also try to run this command in Terminal.app: ping ui.eqmac.app

By any chance you guys have some Firewall settings or VPNs running?

I do sometimes have to a run a VPN for work stuff, but it has never been an issue before.
Just hit that URL and works fine (VPN is off right now, and has been all day)

Pinging fine too

Also can you Sample eqMac process and send me the report as a file:

Here you go mate:
Sample of eqMac.txt

Ok for now I have no ideas what is going on, as if it just ignores the code I wrote. Gotta love computers

All good mate, appreciate your time looking into it and providing this open source!
I also just ran sudo killall coreaudiod to see if that did anything, but it did not.

I'm able to workaround by killing the task and re-opening via terminal;

/Applications/eqMac.app/Contents/MacOS/eqMac

@HudsonGraeme could you let me know exactly how I start it via terminal?

@HudsonGraeme could you let me know exactly how I start it via terminal?

Yes, in terminal the command should just be /Applications/eqMac.app/Contents/MacOS/eqMac

I think I know what is happening, but not sure why.
Basically the app is trying to  show you an update prompt but fails to show the prompt window.
Please just download the update here and install:
https://github.com/bitgapp/eqMac/releases/tag/v1.8.4
This should resolve your issue

Ok, so I quit eqMac via Activity Monitor, then ran:
open /Applications/eqMac.app/Contents/MacOS/eqMac via terminal.
The application has started running, but same issue. Shows in AM but not in the menu bar.

@nodeful it worked!!!
You legend!
Thanks so much :)

Worked for me too! Thanks @nodeful


Missing additional button prompts across all Controller Types

Right now; I'll need to add additional button images for each Controller Prompts. It'll be dealt with for a future update.
But in the meantime:
Steam Controller:

[x] Guide button
[x] Swipe versions of Trackpad button

Steam Deck:

[x] Guide Button
[x] Quick Menu button
[x] Joystick Touch
[x] Swipe versions of Trackpad button

DualShock 4:

[x] Guide button
[x] Left Touchpad Click
[x] Right Touchpad Click
[x] Left Touchpad Touch
[x] Right Touchpad Touch
[x] Swipe versions of Touchpad button

DualSense:

[x] Guide button
[x] Left Touchpad Click
[x] Right Touchpad Click
[x] Left Touchpad Touch
[x] Right Touchpad Touch
[x] Swipe versions of Touchpad button
[x] (DualSense Edge) Paddle Buttons

Xbox Wireless Controller

[x] Guide button
[x] (Xbox Elite) Paddle buttons

Added all Guide Buttons to the list. We should be half-way there.
https://github.com/AL2009man/Gamepad-Prompt-Asset-Pack/commit/589d171331a2308df68fc5a9c8e77bd47ff0ef5b

All missing button prompts (alongside new additions) has been added to the collection.


"File Not Found"

@EdwardCaulfield commented on Sun Dec 02 2018
Attempting to install on Mac OS Mojave and even though I can set the path as documented in this guide, it still shows a "Not Found" error for the SDK location.  I am not at all successful in the NDK location and even though I am able to navigate to the Java SDK (JDK) Location and it gets a green "Found" - once I click on "OK" and return to the dialog, all fields are empty again.
I am using the version 7.7 (build 1868) of Visual Studio for Mac (Community edition).
Much appreciate your help clarifying this situation.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 97e1cd96-e7a2-ec22-8d79-ac949e890ccb
Version Independent ID: 922a3fdf-7bab-7d9d-5518-904db9e75ee3
Content: Microsoft Mobile OpenJDK-Verteilung (Vorschauversion) - Xamarin
Content Source: docs/android/get-started/installation/openjdk.md
Product: xamarin
GitHub Login: @vyedin
Microsoft Alias: vyedin

@vyedin commented on Mon Dec 03 2018
@EdwardCaulfield would you mind filing this in VS Mac Report an Issue so we track it in our bug system? Please also attach your VS for Mac logs.

@EdwardCaulfield commented on Mon Dec 03 2018
Will do.

@CeciAc commented on Mon Dec 03 2018
Hi @vyedin @EdwardCaulfield
Should I move this issue to the en-us repository?
Please advise,
Kind regards

@EdwardCaulfield commented on Tue Dec 04 2018
Yes, please.
Kind Regards,
Edward

As indicated in the thread above, this should be reported via Visual Studio for Mac report a problem page.

Hello Prashant,
Thank you for the reminder.  I’ve not yet had an opportunity to work on the project again since issuing my initial report. If the problem persists (I think there was an upgrade in the meantime), I will use the appropriate tools to report it.
Thank you, however, for your persistence.  After close to 30 years dealing with big companies, it is a rare experience and shows how much the Microsoft culture has improved under the current leadership.  Really a nice thing to see!  Google could learn a lot from you!
Best Regards,
Edward Caulfield
http://360grad.studio/
+41 76 281 1960
If you're not progressing, you're regressing;
This email and any files transmitted with it may contain confidential and/or legally protected information. They are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender and delete it immediately, considering its dissemination, distribution or copying being strictly prohibited.

On 10 Dec 2018, at 22:02, Craig Dunn<EMAIL_ADDRESS>wrote:
As indicated in the thread above, this should be reported via Visual Studio for Mac report a problem https://docs.microsoft.com/en-us/visualstudio/mac/report-a-problem page.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/xamarin-docs/issues/1213#issuecomment-445971614, or mute the thread https://github.com/notifications/unsubscribe-auth/ACfhXlXrDYfZkBSq6eex5rjwyFMN65B0ks5u3svpgaJpZM4ZJKGj.


:sparkles: implement ListIssues and GetCreatedAt for Azure DevOps

What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)

[x] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
ListIssues and GetCreatedAt throw an unsupported error
What is the new behavior (if this is a feature change)?**
ListIssues and GetCreatedAt have implementations

[x] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
Next step of https://github.com/ossf/scorecard/issues/4177
Special notes for your reviewer
Azure DevOps doesn't have an official API to retrieve user permissions for a project or a repository. As a stopgap solution, I've defaulted all issue and comment authors to RepoAssociationMember. This is probably a good minimum bar.
The audit log is the best way to retrieve the repository creation date, but this may not be enabled. So I am using the first repository commit as a fallback value.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

implement `ListIssues` and `GetCreatedAt` for Azure DevOps

With these changes the Maintained check now completes

Details
$ env SCORECARD_EXPERIMENTAL=1 go run . --repo dev.azure.com/jamiemagee/jamiemagee/_git/jamiemagee --checks Maintained
Starting [Maintained]
Finished [Maintained]

RESULTS
-------
Aggregate score: 5.0 / 10

Check scores:
|--------|------------|--------------------------------|-----------------------------------------------------------------------|
| SCORE  |    NAME    |             REASON             |                       DOCUMENTATION/REMEDIATION                       |
|--------|------------|--------------------------------|-----------------------------------------------------------------------|
| 5 / 10 | Maintained | 5 commit(s) and 1 issue        | https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained |
|        |            | activity found in the last 90  |                                                                       |
|        |            | days -- score normalized to 5  |                                                                       |
|--------|------------|--------------------------------|-----------------------------------------------------------------------|


Ambient Temp Calibration

Searched and couldn't find anything about this. I have a DR-HTF004S (Pilot Max S) and it has a feature where you can calibrate the temperature. It was originally reporting 83°F degrees (in the app and HA), but I've used the app feature to calibrate it down to -4°F degrees less.
The Dreo app says 79°F (adjusted value), but HA sensor is still reporting 83°F after lengthy time and restart. It's seemingly not picking up the calibrated value. Is there any way to get it to use the adjusted temp?

config_entry-dreo-01J4SESQHVM1DM0J5VF830S8QV.json

I don't see anything like that in the diagnostics (which have the full payload back from Dreo). It's possible it's just an app feature. If you delete the app and reinstall is it still there?

Yes, just deleted and re-installed and it's still showing my adjusted / calibrated temp on the main home screen and controls screen. So I assume it's being stored server-side and not just in the app.
I do see this in the diagnostics, which seems to be the setting in question, but I don't see the calibrated temp value in the payload either.
            "preference": [
              {
                "id": "250",
                "type": "Temperature Calibration",
                "title": "device_control_temp_calibration",
                "image": "ic_temp_cal"
              }
            ],

@zyonse any chance you have any idea?

Could be this? Hard to say because my fan doesn't have that option in the app.

Funnily enough we actually have a config option in the homebridge plugin that does the exact same thing, setting an offset for the temp sensor.

@zyonse does it not come back in the regular GetDeviceState call?

Ok, just so I have it saved somewhere....this should be enough to sort this out and implement it.
One thing we need to figure out is if we should allow setting it from here, or just factor it into the calculation of the actual temperature.
I see a GET to:
https://app-api-us.dreo-cloud.com/api/user-device/setting?timestamp=1725762806531&dataKey=kHafFanTempOffsetKey&deviceSn=REDACTED
Which returns this:
{"code":0,"msg":"OK","data":{"id":"1832608117463527425","deviceSn":"REDACTED","dataKey":"kHafFanTempOffsetKey","dataValue":"0"}}
I see a PUT to:
https://app-api-us.dreo-cloud.com/api/user-device/setting?timestamp=1725762798003
With this body to reduce the temperature 1 degree:
{"dataKey":"kHafFanTempOffsetKey","dataValue":-1,"deviceSn":"REDACTED"}

Alright, @SeanPM5 can you try out the attached branch and see if it works for you?

Tested the branch on a secondary HA instance:

It picked up my -4 calibrated temp (74F) rather than 78F. Good!
Then changed calibrated temp to -10 (from 78F to 68F) for testing purposes. Reloaded integration and it picked up that value too. Good!
Lastly, I changed calibration to -1 in the Dreo app. This time, instead of reloading the HA integration I waited for the temperature state to update in HA by itself. It went from 68 to 69, so it was still using the -10 from above (last time I reloaded) rather than my more recent -1 app adjustment (that I didn't reload integration for).

So that is the only minor issue I found, if you adjust in the app the integration doesn't pick it up until reloaded. I consider that more of a minor edge case but just wanted to share my complete findings. Besides that one tiny thing, it's working great for me.

Thanks. I'm aware of that.
I need to check to see if it pushes the update down. If not I'll have to poll or something.

Just double checked and can confirm my calibration is set to +0


Https pattern changed/broken ?

Until very recently, automation to close repo using the format https://dev.azure.com/{your organization}/{your project} to clone a repo from Azure DevOps worked well. Both for PATs ad alternate credentials.This seems to be broken now as the format changed to<EMAIL_ADDRESS>essentially breaking the pattern of using<EMAIL_ADDRESS>organization}/{your project} . What is the pattern to authenticate using the new pattern ? Basic Git commands seems to work using SSO but explicit authentication from a test machine is not working

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

ID: 3f8b4989-21f0-53c5-dfce-6d5f1a66b8b2
Version Independent ID: 2f4419a7-408b-40cd-9190-985a9976d556
Content: Authenticate with your Git repos - Azure Repos
Content Source: docs/repos/git/auth-overview.md
Product: devops
GitHub Login: @steved0x
Microsoft Alias: sdanie

@vmaruhpe There were url behavior changes last year but nothing recent. It's possible that your builds were running into an issue with alternate credentials where your builds could have started getting failed auths all of a sudden. The issue was fixed yesterday (2/4/2019).
If your builds were not using alternate credentials, then it might be that you weren't affected by the url changes until now and to get past it you can just make sure to upgrade to Git 2.19 or later and use the<EMAIL_ADDRESS>format for your remote.

Thank you @alepauly. My situation is case 1 as you described above. Is the fix in production already?
Need one more clarification though. For the URL format<EMAIL_ADDRESS>, can alternate credential still be used ? That is  something like https://username:password<EMAIL_ADDRESS>?

Thank you for the clarification. May I suggest  changing the default URL to the earlier format on the Azure DevOps repo page or adding it as an additional option ?

Definitely, I'll make sure the appropriate team is aware of your
suggestion. Thanks!
On Tue, Feb 5, 2019 at 12:06 PM vmaruhpe<EMAIL_ADDRESS>wrote:

Thank you for the clarification. May I suggest changing the default URL to
the earlier format on the Azure DevOps repo page or adding it as an
additional option ?
[image: image]
https://user-images.githubusercontent.com/35544818/52290541-1ab35580-2925-11e9-8940-6d3bddc9628d.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/vsts-docs/issues/3212#issuecomment-460719720,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGjjX25r-A4VU1IlVYrNCFDRi52IzR-Vks5vKboXgaJpZM4afCKe
.

--
"Time flies like an arrow. Fruit flies like a banana.." - Groucho Marx


Physical datasource inited twice while initiating OrchestrationDataSource

Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
3.1.0
Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-JDBC
Expected behavior
init physical datasource only one time
Actual behavior
config one datasource, but inited two.
2019-03-12 17:39:18.111  INFO 55623 --- [           main] com.alibaba.druid.pool.DruidDataSource   : {dataSource-1,DataSource-1655894346} inited
2019-03-12 17:39:19.587  INFO 55623 --- [           main] com.alibaba.druid.pool.DruidDataSource   : {dataSource-2,DataSource-391884147} inited

Reason analyze (If you can)
AbstractOrchestrationDataSource is parent class of OrchestrationShardingDataSource, and they both invoke DataSourceConverter.getDataSourceMap respectively in their constructors, in which physical datasources are created.
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).

already fixed at #1791


Applications force-killed by the manufacturer's Android

The current message distribution system relies on Android's BroadcastReceiver and registering only the application package name. The causes problems if the target app (the one that should receive a notification from the UP implementor) has not been started, has been manually killed or has been reclaimed by the system. Then, there's no way, using  BroadcastReceivers and Context.sendBroadcast(), to bring an application back to life, which defeats a bit the pupose of UP.
The protocol should rely on a system that is able to start an app, whether is exists in memory or not. The only system I can think of, is creating a dedicating an empty activity for that, registering that activity (instead of the application package name) and start it whenever a UP implementor should distribute a notification, using Context.startActivity(). This is how Android's sharing system works.

You should check that website : https://dontkillmyapp.com/
Do you see solutions for your device ? Do you see improvement if you do what's recommended ?

I run Lineage. There shouldn't be any optimization beyond what's on AOSP. I guess there's not good solution. Maybe future Android API level come with a solution to ensure an app correctly receives notifications.

Lineage uses some vendor blobs, I don't know if some on your device can be related to battery optimization :thinking: .
I wonder if the issue doesn't occur after the message is received by the application: have you disabled battery optimization for element for instance ? If the app is in background for a while, the sync with the server can takes time (it will be shorten with matrix sync v3) and the app may be killed during this process.

I just disabled battery optimizations. I'll see if it solves the problem. But honestly, I just wished users wouldn't have to do such configurations. Using a phone should be simple…


Use slimmer protobuf structures for remaining k8s structures

Follow up of https://github.com/cilium/cilium/pull/11326 for remaining structures

test-me-please

test-me-please

Coverage decreased (-4.7%) to 37.814% when pulling 133046e03a9b35ad3d4fe9c9fcac63a46afc815a on pr/use-slimmer-protobuf-definitions-others into a7f8fc8f68ba16aff545eabef33d0d3f8914079c on master.

Unable to debug k8s flakes due https://github.com/cilium/cilium/issues/11386