Update concept-workspace.md

We've had a couple of support cases that resulted from customers using storage account of type "BlobStorage".
This can be very impactful if the issue is only uncovered after some time, as the customer will have to recreate the ML workspace with the correct storage account type.
Discussions with these customers are tough and unpleasant due to the lack of clear statement that directly addresses this requirement.
Propose to add a sentence that makes it as clear as possible that this storage account type cannot be used with Azure ML workspace.

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

assign: @nibaccam

@hugogeraldes thank you for your contribution, can you please elaborate on the scenario here? What are customers trying to do with BlobStorage?

@nibaccam when creating an Azure ML workspace, customers are given the option to use an existing Storage Account.
That Storage Account needs to meet certain requirements.
One of those requirements is that it cannot be of type "BlobStorage".
If you read the current version of the document you can only get to this conclusion indirectly by interpreting what is being said in the same "Important" box where I've written my proposed change.
To avoid unpleasant misunderstandings that can lead to support calls, I propose to add a sentence that clearly and directly addresses this requirement, so that no interpretation is necessary.
Hope to have clarified the situation.

@hugogeraldes  Are you saying that customers can't use an existing BlobStorage as their default storage account with the workspace?
Or are you saying that existing BlobStorage can't be upgraded to general purpose v2? The "Important" box where you placed your edit, talks about general purpose v2, so I want to make sure I'm understanding the scenario.

@nibaccam when you create a storage account in Azure it can be one of three types:
General Purpose V1
General Purpose V2
BlobStorage.
What I'm saying is that the storage account that will be used by the Azure Machine Learning workspace cannot be of type "BlobStorage".

@hugogeraldes thank you for clarifying. The storage account type that is created by default with an Azure ML workspace is a General Purpose v1 and within that storage account type, a blob container/data object is created/attached to the workspace. I was confusing these two items: BlobStorage account type vs the blob data object.
I've proposed a suggestion on the Files changed tab. Let me know what you think?

#sign-off

@nibaccam: I'm sorry - only the author of this article, @sdgilley, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


week 7 achievement visible

Describe your bug here.

i don't know if this was intended, but in 0.5.3b, you can see the week 7 achievement.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Nothing.

you shouldn't upgrade to 0.5.3b since this is a fake release.

I just downloaded it, but reported this bug just in case because I think it was unintended

it's also visible in 0.5.2h, so i don't think that 0.5.3b is the issue

so it was intended?

considering week 8 is releasing on the 30th, this is probably early preparation.

considering week 8 is releasing on the 30th, this is probably early preparation.

this aged bad

Actually, it's a bug in the code that shows hidden achievements. To fix it, find line 47 of AchievementsMenuState.hx:
if(!Achievements.achievementsStuff[i][4] || Achievements.achievementsMap.exists(Achievements.achievementsStuff[i][2])) {
and swap the 4 with a 3.

considering week 8 is releasing on the 30th, this is probably early preparation.

this aged bad

like spoilt milk


tangram package: The Grammar of Tables

Just discovered the tangram package, which  claims to be the grammar of tables.  Here for a reference.

tangram on github: https://github.com/spgarbet/tangram


message function

change message on real time, without hide then show again
waitingDialog.message('Initialize you Environment for the first use')
get the current message :
waitingDialog.message()

Hey, abdennour! Thanks for the contribution! There is only one thing: you should change /src/ files instead of /build/, I've fixed that for you. :smile:


port RPC credentials script from Bitcoin

Current script is broken (parsing conflicts?), it's useful for k8/docker/etc env to get it fixed.

What do you mean by "broken"? What's the issue exactly?

@UdjinM6 can't get it working in homebrew. im writing new formulae since i've lost some data i had along #2464, plus need to add new dependencies for evo. would it make a difference if i post logs from 0.12.3 base?

Last changes to rpcuser.py were made mid 2018, so I guess logs for 0.12.3.x branch should be ok.

@UdjinM6 homebrew moved to Azure env after #2464, now need to figure out the way with travis. But have a feeling I'm almost there https://github.com/charlesrocket/homebrew-dash

Hmm, ok. Well, I don't see how failures in your build might be connected to rpcuser/rpcauth tbh, feels more like c++11 requirement isn't met.
Also, pls note that stable (master) is now 0.13.1 and we actually build dependencies like qt/boost/etc. instead of installing them, so you have to specify correct prefix in ./configure. See https://github.com/dashpay/dash/blob/master/doc/build-generic.md for more info.

@UdjinM6 That is not the output I am looking for yet, current build fails are due switch to Azure, I'm figuring out the approach with travis at the moment.


Feature/ghg emissions review

https://www.pivotaltracker.com/n/projects/2083759/stories/152432295

[x] Removed subsectors.
[x] Include a line for total values.
[x] Change graph type on calculations change.
[ ] Update tooltip label on calculations change.

I see a small issue, when we have values that are much lower than 0.0t the graph doesn't show the data properly, as the yy axis is a bit funky. See attached:

But otherwise looks good with what is built! I'm going to merge this version and get it deployed. And maybe you can check the yy axis with the remaining task of the legend.


Update index.yml

Push to live

Docs Build status updates of commit 475c0e5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


:zap: Improve cross http error handling

Improve cross http error handling

Status
Type
⚠ Core Change
Issue

Ready
Bug/Enhance
No
https://github.com/magicblock-labs/Solana.Unity-SDK/issues/129

Problem
Some failing calls when using Unity.SendRequest were not propagating the exceptions.
Solution
Better exceptions and return task handling
Connected PRs

https://github.com/magicblock-labs/Solana.Unity.Metaplex/pull/4
https://github.com/magicblock-labs/Solana.Unity-SDK/pull/131

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 32 (0.0%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 72.697%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Solana.Unity.Rpc/Core/Http/CrossHttpClient.cs
0
32
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/Solana.Unity.Rpc/Core/Http/CrossHttpClient.cs
4
8.7%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
4730

Relevant Lines:
6206

💛  - Coveralls


Tweak Makefile to support older Go versions' backported module support

go supports environmentally-toggled support for the module system introduced in 1.11.
Currently the Makefile checks for go > 1.10 to decide whether or not to use the -mod flag; for certain go installations, though, this flag is unsupported without setting GO111MODULE=on in the environment.
Compounding this is having a module that depends on go >= 1.12. If modules are disabled, everything builds fine; if they are enabled any Go version under 1.12 (even if it has backported module support) will fail.
This PR:

only enables module use for go >= 1.12
sets GO111MODULE=on if modules are enabled

Excellent; love the new approach! ❤


Allow setting /testsettings: file for MSTest runner #421

@marcosnz I just wanted to follow up with @patriksvensson comments.  Are you in a position to update this PR with the suggestions?
Thanks!

FYI this Pull Request is related to https://github.com/cake-build/cake/issues/421

@marcosnz planning next release, have you had a chance to look at the feedback given by @patriksvensson?

@marcosnz just wanted to follow up again.  Have you had a chance to look at the feedback that was provided?

Closing this PR for now.


Can't run in Windows

Hi,
Apparently there is no PySide2 python 2.7 for windows. I can install PySide, but running running your app I get an exception:
C:\Users\victo\PycharmProjects\PyFlow>py -2 C:\Users\victo\PycharmProjects\PyFlow/launcher.py
(ImportError('No module named pyrr',), 'FloatVector3Pin')
(ImportError('No module named pyrr',), 'FloatVector4Pin')
(ImportError('No module named pyrr',), 'Matrix33Pin')
(ImportError('No module named pyrr',), 'Matrix44Pin')
(ImportError('No module named pyrr',), 'QuatPin')
Traceback (most recent call last):
  File "C:\Users\victo\PycharmProjects\PyFlow/launcher.py", line 6, in <module>
    from PyFlow.App import PyFlow
  File "C:\Users\victo\PycharmProjects\PyFlow\PyFlow\App.py", line 15, in <module>
    from Core.Widget import GraphWidget
  File "C:\Users\victo\PycharmProjects\PyFlow\PyFlow\Core\__init__.py", line 8, in <module>
    from Node import Node
  File "C:\Users\victo\PycharmProjects\PyFlow\PyFlow\Core\Node.py", line 26, in <module>
    from .InputWidgets import getInputWidget
  File "C:\Users\victo\PycharmProjects\PyFlow\PyFlow\Core\InputWidgets.py", line 18, in <module>
    from ..UI import FloatVector3InputWidget_ui
  File "C:\Users\victo\PycharmProjects\PyFlow\PyFlow\UI\FloatVector3InputWidget_ui.py", line 93, in <module>
    import nodes_res_rc
  File "C:\Users\victo\PycharmProjects\PyFlow\PyFlow\UI\nodes_res_rc.py", line 10, in <module>
    from PySide2 import QtCore
ImportError: No module named PySide2

So although in the readme it says pyside or pyside2, it appears it is still asking explicitly for pyside2.
I guess this would be naturally solved with #3.
Thanks.

Hi,
The problem occurs because of pyside2-uic generated files. I'll fix this as soon as possible, tnx


VPN gateways should not phone during office hours

Currently PagerDuty will call if VPN gateways become unavailable, but only during office hours.
This is annoying because it phones a lot and is entirely unactionable. It should be critical but have no notification period so it never phones.
Creating an issue because I keep forgetting to do this.

Fixed in #4335.


[USABILITY] [DRAFT] Update text when users don't have login permission.

Placeholder task to be updated by @sandeep-ps
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Current task: Look up the current text.


NUXT SECURITY conflicts with JSON import

No way to run nuxt generate if nuxt-security plugin is present and also JSON import from file using experimental feature
Maybe related to @unplugin-remove and babel
https://github.com/babel/babel/issues/16754
nuxt-security: 2.0.0
nuxt: 3.13.2
Steps to reproduce
use this in any of your files:
import value from './value.json' with { type: 'json' };
What is Expected?
build works perfectly fine
What is actually happening?
Nuxt Build Error: [unplugin-remove-console-debugger] This experimental syntax requires enabling the parser plugin: "importAttributes". (9:32)

Yes definitely an unplugin-remove issue upstream
@Baroshem Vite can remove console and debugger natively, we might be better off with Vite’s implementation

I think that could be a better solution indeed. The unplugin has several issues and is conflicting with many solutions. Should we wait for release 3.0.0 or should we make it for 2.1.0? According to semver we should probably wait for major but if Vite delivers similar functionality we could already go for native solution instead and just mention it in the documentation.
WDYT?

I have a working POC, but it cannot be a straight drop-in replacement:

esbuild drops all console statements, whereas unplugin-remove can select the level (console.log, warn, error, etc.)
esbuild drops across all files, whereas unplugin-remove can select the files where statements are removed

I do believe that esbuild's binary approach (remove everything or remove nothing) is the right one, and I am of the opinion that too much configuration leads to issues. But it's ultimately a matter of taste.
Therefore I can implement via two different patterns:

By breaking change: The unplugin-remove options would be replaced, and removeLoggers would just be either console, debugger, both or false
By soft-deprecation: We would keep the current unplugin-remove options as well as the ability to use unplugin-remove but we would introduce a new option that allows to choose either the native Vite functionality or the plugin. Vite would be the default and we would mark unplugin-remove for deprecation

What's your preference?

According to semver, option 1 (breaking) would lead to 3.0.0 while option 2 (feature) would lead to 2.1.0
We can start with option 2, and wait for people to transition out of unplugin-remove options before breaking on 3.0

Agree, this seems like a safe and good option :)


Urllib upgrade

It fixes dependabot alerts related to outdated urllib

bors merge

bors merge

This was done in #2487


feat: Enable Comments with Hyperlinks

PR Fixes:

Implemented a regular expression to match URLs within the comment text
Opens the URLs in a new tab

Resolves #126
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

Hi @hkirat, please check the PR. Thank you.


Added Macaw router

Not really "awesome", but ok.

Code base could be improved a lot.
composer.lock should not be committed into a library project.
Not marked as library project.
Misplaced autoloader-entry-point


Syncronize the blocklist storage

Sync and store data with Firefox Account (when user is logged in otherwise works as local storage.) Sync storage is not available on current Firefox for Android, so falling back to local storage when unavailable.
https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/storage/sync

For most users, sync will just be a way to automatically backup and restore their blocklist. For others, it will be a way to get the same blocklists on multiple devices.
The extension doesn’t handle exceeding the storage limit. The sync storage is limited to 100 KB versus 5 MB on local. This is still over a thousand blockrules and browser performance would be seriously impacted before anyone reached this limit. Should probably add a warning in the UI when nearing the limit, though.
This is pull request is intentionally missing an upgrade path. Do you have any preferences regarding auto-upgraded storage or not? Maybe shouldn’t even auto-copy a non-synced storage to a synced storage without prompting users first? I believe anyone who wouldn’t want this feature has already disabled it or would never even consider logging in to an Firefox Account.
Here is a simple pseudo-upgrade logic:
// data haven't been upgraded yet
if (browser.storage.sync && browser.storage.sync.get('upgrade_version') == null) {
  // copy over data
  browser.storage.sync.set('simpleBlocker', browser.storage.local.get('simpleBlocker'))
  // successful upgrade – will only upgrade from the first client to sync
  browser.storage.sync.set('upgrade_version', '0.40.0')
}

Sync happens automatically. Note that sync conflicts are possible. Sync server will always default to choosing the most recent version. It’s possible to handle incoming sync data changes with an event listener to reduce the number of conflicts. However, since there is only one text field for inputting data … well, I don’t see an easy way to handle that non-disruptively. This will only be a problem if someone edits their blocklist on two different machines within a few seconds of each other and Firefox on both clients don’t have enough time to sync them up.


Add Authentication and Authorization

TBD

Maybe add OpenID?

https://kubernetes.io/docs/reference/access-authn-authz/authentication/#openid-connect-tokens
https://quarkus.io/guides/security-openid-connect

worth to check how HawtIO NG does it


Some PDFs throw exception after Chrome 75 update

Attach (recommended) or Link to PDF file here:
https://rockendintv.blob.core.windows.net/public/problem.pdf
Configuration:

Web browser and its version: Chrome 75 (did not occur in Chrome 74)
Operating system and its version: Windows 10
PDF.js version: 2.0.943
Is a browser extension: not sure what this means

Steps to reproduce the problem:

Set above pdf as src of PDF JS
Get a couple of console errors:

Some PDF files render without issues, but some do not (like the one above) and show a couple of console errors. Tried to debug but the src is bundled/minified but from what I see looks like related to parseInt and Content-Range.
Important Note: This did not occur when using Chrome 74, only occurred when we updated to Chrome 75. But I was able to replicate it using IE11 in the past.

This did not occur when using Chrome 74, only occurred when we updated to Chrome 75.

In that case this really sounds like a regression in the browser itself, rather than a bug in the PDF.js library, and as such you'll need to report it to the browser vendor instead (since we cannot fix bugs in the browser itself).

But I was able to replicate it using IE11 in the past.

Please note that, as outlined in https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support, support for IE11 is very limited in the PDF.js library (and it will be completely removed in the future).

Shouldn't these errors be properly handled though? One thing I noticed is that the error is not caught in the catch method of the promise. i.e.:
PDFJS.getDocument(this.src)
   .then((pdf) => {
      // logic
   })
   .catch((error) => {
      **this is not called when exception is thrown**
   });

@vicinting the redaction of your file is incomplete. Text extraction shows the word "Duffy" in the subject line.

@vicinting That's because getDocument returns a loading task object and not a promise. To get the promise, you need to use getDocument.promise.then(); see: https://github.com/mozilla/pdf.js/blob/cad0e612622a1384093006677f8e5b9b725fc2d0/examples/components/simpleviewer.js#L68

Thank you @timvandermeij, I'm not very familiar with the library and just inherited a project that used this. Should read up more on the library when I have time. Thanks!


Debugger breaks on Handled exceptions or only on class Instantiation

Describe the bug
Debugger either breaks on class instantiation instead of in class code or breaks on all raised exceptions while breaking properly in class code. When the debugger breaks  on class instantiation only there is no indication of which line actually caused the exception. In a large class this makes debugging in Visual Studio a tedious process of manually stepping through code or pressing continue for each handled exception.
Steps to Reproduce

Disable all Python Exceptions in Exceptions Settings (there is no unhandled exceptions to select in the list).
Run with Debugging. Debugger Breaks on class instantiation with no indication of where the error occurred (line 11)

Exception Details:
Message=name 'j' is not defined
Source=...\Scratch.py
StackTrace:
File "...\Scratch.py", line 14, in
H=h()
3.Enable Python Exceptions (there is no Handled Exceptions option to deselect in the list). Run with Debugging: Breaks on Handled Exception (not wanted behaviour)

4. Continue to next exception. Breaks where the exception actually occurred (wanted behaviour) in the class and then on instantiation after continuing again.

After Continue

Expected behavior
The ability to skip handled exceptions and break in class code not only on instantiation. VSCode for example, by selecting break on uncaught Exceptions only the debugger breaks in the class code and skips the handled exception. In a large class this makes debugging in Visual Studio a tedious process which is why I use the VScode debugger to find bugs in large classes

Sample Code
#Handled exception
try:
raise ValueError
except:
pass
class H(object):
def init(self):
#unhandled exception
print(j)
if name == "main":
h=H()
This also occurs if the exception is not in init:

Behaviour is not seen when not using classes.

Configuration information (If you are providing a diagnostics file (see below), skip this section)
VS Version: 16.8.0
PTVS version: 16.8.20241.2
Python version:
Debugger Type (if applicable): New debugger, have not tried on Legacy yet
Diagnostics file
Diagnostic Info 2020-11-19T111217.txt

This looks like https://github.com/microsoft/debugpy/issues/399 which has already been fixed in debugpy 1.0.0.
https://github.com/microsoft/debugpy/releases
Can you please do this in both VS and VS Code:
import debugpy
print(debugpy.__version__)

and run under the debugger to see which versions you have in both.
VS 16.8 I believe has 1.0.0rc2 but VS 16.9 Preview 1 (available now) should have 1.0.0.

I'm not able to repro this with the latest VS preview and Python 3.7:

I'm not able to repro this with the latest VS preview and Python 3.7:


Produce fails to create app on iTunes Connect

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

For the second time today on completely separate apps, creating the app on iTunes Connect seems to fail. It just says Waiting for the newly created application to be available on iTunes Connect... and then eventually after 12 minutes or so, throws the following error:  Couldn't find newly created app on iTunes Connect - please check the website for more information
Complete output when running fastlane, including the stack trace and command used
[17:01:19]: ---------------------
[17:01:19]: --- Step: produce ---
[17:01:19]: ---------------------

+----------------+--------------------------+
|         Summary for produce 1.2.0         |
+----------------+--------------------------+
| username       |<EMAIL_ADDRESS>    |
| app_name       | Maitland Indaba 2016 SA  |
| app_identifier | net.hellocrowd.xfupzq8lk |
| sku            |<PHONE_NUMBER>               |
| language       | English                  |
| skip_itc       | false                    |
| skip_devcenter | false                    |
| team_id        | HL7N5T6N6H               |
+----------------+--------------------------+

[17:01:26]: Creating new app 'Maitland Indaba 2016 SA' on the Apple Dev Center
[17:01:30]: Created app 52B56K83G9
[17:01:32]: Finished creating new app 'Maitland Indaba 2016 SA' on the Dev Center
[17:01:36]: Creating new app 'Maitland Indaba 2016 SA' on iTunes Connect
[17:01:39]: Waiting for the newly created application to be available on iTunes Connect...
[17:01:50]: Waiting for the newly created application to be available on iTunes Connect...
[17:02:00]: Waiting for the newly created application to be available on iTunes Connect...
[17:02:11]: Waiting for the newly created application to be available on iTunes Connect...
[17:02:22]: Waiting for the newly created application to be available on iTunes Connect...
[17:02:33]: Waiting for the newly created application to be available on iTunes Connect...
[17:02:43]: Waiting for the newly created application to be available on iTunes Connect...
[17:02:54]: Waiting for the newly created application to be available on iTunes Connect...
[17:03:05]: Waiting for the newly created application to be available on iTunes Connect...
[17:03:15]: Waiting for the newly created application to be available on iTunes Connect...
[17:03:27]: Waiting for the newly created application to be available on iTunes Connect...
[17:03:37]: Waiting for the newly created application to be available on iTunes Connect...
[17:03:48]: Waiting for the newly created application to be available on iTunes Connect...
[17:03:59]: Waiting for the newly created application to be available on iTunes Connect...
[17:04:09]: Waiting for the newly created application to be available on iTunes Connect...
[17:04:20]: Waiting for the newly created application to be available on iTunes Connect...
[17:04:31]: Waiting for the newly created application to be available on iTunes Connect...
[17:04:41]: Waiting for the newly created application to be available on iTunes Connect...
[17:04:52]: Waiting for the newly created application to be available on iTunes Connect...
[17:05:03]: Waiting for the newly created application to be available on iTunes Connect...
[17:05:14]: Waiting for the newly created application to be available on iTunes Connect...
[17:05:24]: Waiting for the newly created application to be available on iTunes Connect...
[17:05:35]: Waiting for the newly created application to be available on iTunes Connect...
[17:05:46]: Waiting for the newly created application to be available on iTunes Connect...
[17:05:57]: Waiting for the newly created application to be available on iTunes Connect...
[17:06:07]: Waiting for the newly created application to be available on iTunes Connect...
[17:06:18]: Waiting for the newly created application to be available on iTunes Connect...
[17:06:29]: Waiting for the newly created application to be available on iTunes Connect...
[17:06:40]: Waiting for the newly created application to be available on iTunes Connect...
[17:06:50]: Waiting for the newly created application to be available on iTunes Connect...
[17:07:01]: Waiting for the newly created application to be available on iTunes Connect...
[17:07:12]: Waiting for the newly created application to be available on iTunes Connect...
[17:07:22]: Waiting for the newly created application to be available on iTunes Connect...
[17:07:33]: Waiting for the newly created application to be available on iTunes Connect...
[17:07:44]: Waiting for the newly created application to be available on iTunes Connect...
[17:07:55]: Waiting for the newly created application to be available on iTunes Connect...
[17:08:05]: Waiting for the newly created application to be available on iTunes Connect...
[17:08:16]: Waiting for the newly created application to be available on iTunes Connect...
[17:08:26]: Waiting for the newly created application to be available on iTunes Connect...
[17:08:37]: Waiting for the newly created application to be available on iTunes Connect...
[17:08:48]: Waiting for the newly created application to be available on iTunes Connect...
[17:08:59]: Waiting for the newly created application to be available on iTunes Connect...
[17:09:09]: Waiting for the newly created application to be available on iTunes Connect...
[17:09:20]: Waiting for the newly created application to be available on iTunes Connect...
[17:09:30]: Waiting for the newly created application to be available on iTunes Connect...
[17:09:41]: Waiting for the newly created application to be available on iTunes Connect...
[17:09:52]: Waiting for the newly created application to be available on iTunes Connect...
[17:10:02]: Waiting for the newly created application to be available on iTunes Connect...
[17:10:13]: Waiting for the newly created application to be available on iTunes Connect...
[17:10:24]: Waiting for the newly created application to be available on iTunes Connect...
[17:10:35]: Waiting for the newly created application to be available on iTunes Connect...
[17:10:46]: Waiting for the newly created application to be available on iTunes Connect...
[17:10:56]: Waiting for the newly created application to be available on iTunes Connect...
[17:11:07]: Waiting for the newly created application to be available on iTunes Connect...
[17:11:18]: Waiting for the newly created application to be available on iTunes Connect...
[17:11:28]: Waiting for the newly created application to be available on iTunes Connect...
[17:11:39]: Waiting for the newly created application to be available on iTunes Connect...
[17:11:50]: Waiting for the newly created application to be available on iTunes Connect...
[17:12:01]: Waiting for the newly created application to be available on iTunes Connect...
[17:12:12]: -------------------
[17:12:12]: --- Step: slack ---
[17:12:12]: -------------------
[17:12:14]: Successfully sent Slack notification
[17:12:14]: Variable Dump:
[17:12:14]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios deploy"}
[17:12:14]: Couldn't find newly created app on iTunes Connect - please check the website for more information

+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | bundle_install   | 0           |
| 2    | default_platform | 0           |
| 3    | cocoapods        | 10          |
| 4    | produce          | 653         |
| 5    | slack            | 2           |
+------+------------------+-------------+

[17:12:14]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...

➡  Couldn't find newly created app on iTunes Connect - please check the website for more information
   https://github.com/fastlane/fastlane/issues/6281 [open] 4 💬
   5 hours ago

bundler: failed to load command: fastlane (/Users/gregkockott/.rvm/gems/ruby-2.3.0/bin/fastlane)
FastlaneCore::Interface::FastlaneCrash: [!] Couldn't find newly created app on iTunes Connect - please check the website for more information
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane_core-0.52.0/lib/fastlane_core/ui/interface.rb:132:in `crash!'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane_core-0.52.0/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/produce-1.2.0/lib/produce/itunes_connect.rb:39:in `create_new_app'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/produce-1.2.0/lib/produce/itunes_connect.rb:12:in `run'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/produce-1.2.0/lib/produce/manager.rb:8:in `start_producing'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/actions/produce.rb:19:in `block in run'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/actions/produce.rb:17:in `chdir'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/actions/produce.rb:17:in `run'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:202:in `block (2 levels) in execute_action'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:187:in `block in execute_action'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:186:in `chdir'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:186:in `execute_action'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:112:in `trigger_action_by_name'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/fast_file.rb:140:in `method_missing'
  Fastfile:15:in `block (2 levels) in parsing_binding'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:218:in `execute_flow_block'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:46:in `block in execute'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:45:in `chdir'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/runner.rb:45:in `execute'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/command_line_handler.rb:30:in `handle'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane_core-0.52.0/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/commands_generator.rb:246:in `run'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/commands_generator.rb:20:in `start'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/gems/fastlane-1.104.0/bin/fastlane:5:in `<top (required)>'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/bin/fastlane:23:in `load'
  /Users/gregkockott/.rvm/gems/ruby-2.3.0/bin/fastlane:23:in `<top (required)>'

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
bundle_install

default_platform :ios

platform :ios do
    before_all do
        ENV["SLACK_URL"] = "https://hooks.slack.com/services/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"
        cocoapods
        produce(
            username<EMAIL_ADDRESS>            app_name: "HelloCrowd",
            app_identifier: "com.hellocrowd.container"
            )
        apple_id = ENV["PRODUCE_APPLE_ID"]
        cert
        sigh
    end

Environment
fastlane version (run fastlane -v): Using fastlane 1.104.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? Yes
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? rvm

I'm facing the same problem. When I run fastlane, it creates the App in iTunesConnect, but the App doesn't shows up in "My Apps" page. If you enter in the details of an App, using the search function in the top of this page, you can view the App that you just created, but in the "My Apps" page you can't. I'm waiting about 6 hours since the first run of fastlane to see my App in "My Apps" page, and then I run fastlane again to upload my App.

@gregk8288 Did these apps eventually appear on iTC? We've had some recent fluctuation in processing times on the iTC side. @gersonmendes Same question. Thanks!

@TKBurner, yes they did eventually appear. It took a few hours before they were visible but they did appear. I've uploaded 4 new apps since and have not had this problem again.

@gregk8288 Thanks for following up. I've seen processing times vary between 5minutes and several hours so this doesn't suprise me. Let me know if you see this pop up again and provide your full output. Most likely this is unavoidable and would happen in the front end as well. Thanks!

@TKBurner The last application that I publish didn't show the issue. I notice that the message "Waiting for the newly created application to be available on iTunes Connect..." was displayed about 10 times, but it didn't give timeout error. So, I think it's working properly now.
I'll keep in touch.


Inline Assembly Error in helpers.c

Hi!
When building a Rust project which uses wasmtime::Engine to run WASM binaries, linking fails. Project is built as usual with cargo. The following error occurs in runtime/src/helpers.c:78: undefined reference to `asm'
To me, it looks like this should be an empty inline assembly statement, and effectively, replacing it with __asm(""); solves the issue.
I am unaware of the build process for helpers.c but happy to provide more details if required. OS: Linux 6.2.9, CC: GCC 12.2.1 20230201

Thanks for the report! Does https://github.com/bytecodealliance/wasmtime/pull/6188 fix compilation for you? Or is __asm required instead of __asm__?

Thanks for the quick action! Indeed, this fixes it.
As a sidenote, I've now understood why it failed in the first place: I forgot having CFLAGS="-std=c17 -Wall -Wextra -Wpedantic" in my environment by default...
Sorry for the noise - in any case it's standards compliant now ;-)


Rewrite hard url_for in login()

The url_for() in the redirect for login() is unnecessarily restrictive.  I'm writing a CASified API and need it to redirect to the particular endpoint called.  The url_for() additionally doesn't support sending any data the way it's implemented.  Removing this allowed me to point the redirect to request.path, so that the request isn't broken after redirecting to CAS.
While simply removing the url_for() works for me since I wrote my own wrapper function for it, to keep the existing functionality by setting a global redirect up front, it would make sense to use the example from the Flask API doc  (http://flask.pocoo.org/docs/0.10/api/) .  This way, both url_for and direct paths can be given, which will allow for the app to also call url_for with data.
def external_url_handler(error, endpoint, **values):
    "Looks up an external URL when `url_for` cannot build a URL."
    # This is an example of hooking the build_error_handler.
    # Here, lookup_url is some utility function you've built
    # which looks up the endpoint in some external URL registry.
    url = lookup_url(endpoint, **values)
    if url is None:
        # External lookup did not have a URL.
        # Re-raise the BuildError, in context of original traceback.
        exc_type, exc_value, tb = sys.exc_info()
        if exc_value is error:
            raise exc_type, exc_value, tb
        else:
            raise error
    # url_for will use this result, instead of raising BuildError.
    return url

app.build_error_handler = external_url_handler

If this is acceptable, I can work it into a pull request.

To simplify, I mean adding the **values option as defined in the API: http://flask.pocoo.org/docs/0.10/api/#flask.url_for


Features proposal

I started using this framework in a sample project. Great work and thanks for sharing.
I spent some time myself working on something similar, as a side project, and i'm considering to switch to LayoutKit cause it is far head on what I have.
Things that I'd like to add:

Label baseline alignment: Be able to align labels by baseline in an horizontal layout
Center on a specific element of the stack:  Let's say a stack contains two layouts [A][B], if I set .center as aligment for the stack, than the stack's container will set the stack position based on the mid point of it's size. There are cases where I want to center the stack on a specifc element.

For example in this Stack I have to elements the dot and the text. That text should be centered.

A solution to this specific example could be to create an empty SizeLayout as third element of the stack with the same width than the first one. But this could be more complicated with dynamic elements and it should be possible without have to create more layout elements than necessary.

Action support: Now I can add a button as part of the layout and than regenerate the Layout in response to an user action. Could be useful to have a native support for states (Normal, Highlighted) in a way that the view could automatically update to reflect a given state. i.e. having a state parameter in the view config block
Traslation: Ability to apply a traslation to a view position after the layout phase by absolute value or by percentage on the container size.
Max/Min size constraints: Ability to apply a max/min size to a Layout, so that it can still adapt it's size to the size of it's content and at the same time allows to specify min/max constraints.

Please let me know if those features are on you list and if you think if they make sense or not.
From your architecture I see that I can develop those things has private  layouts but I'd like to know your feedbacks, if you have similar things on your todo list and eventually share my changes if they can be useful.

Thanks for sharing your ideas Luca!
It would be helpful if you could create a single issue for each idea so we can discuss and track them independently.

I created #18 to discuss min/max size constraints

Thanks!
I created #19, #20, #21 and #22 to cover those proposal. Closing this


[EGGO-42] Support arbitrary Hadoop filesystem for output.

Here's a first go at this. Most of the changes are just renames to remove "s3" from identifiers.
I tested by changing the URLs in config.py to file:/// URLs and observing that the files were created on the local filesystem. It would be good to parameterize this. @laserson, any thoughts on a good way to do this?

I opted to use an env variable EGGO_BASE_URL to control where the datasets go. It defaults to s3n://bdg-eggo.
I've tested this with success locally and on EC2 using the test dataset and I think it's good to go.

looks great, @tomwhite!

Fixed nits and manually merged in 57b2f57fcc476981b9fd43ea02821a919bb456d4.  Thanks @tomwhite!


Bug

This bugs happened sometimes

There is another bug, Hide Shorts option isn't working (I am on mobile), closed and reopened done every tricks, but not working. @prateek-chaubey

Same but I just rotate phone and it's ok fullscreen


on windows ls with no arguments results in Cannot read property 'replace' of undefined

This is because, in PowerShell, process.env.PWD is not defined: https://github.com/PowerShell/PowerShell/issues/7388
And plugin-bash-like/fs/src/vfs/delegates.ls uses that env var.

Historic note: git bash was fine, since it defines PWD


Routed mode: minor improvements

Description
This PR

adds a global setting to enable/disable the Static/Dynamic routing feature
add some unit tests

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11137

[SF] Trillian Build Failed (tid-11515)

[SF] Trillian test result (tid-11516)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 51439 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9697-t11516-kvm-ol8.zip
Smoke tests completed. 141 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11220

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11239

@blueorangutan test

[SF] Trillian test result (tid-11584)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 58361 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9697-t11584-kvm-ol8.zip
Smoke tests completed. 139 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

ContextSuite context=TestISOUsage>:setup
Error
0.00
test_usage.py

test_04_nonsecured_to_secured_vm_migration
Error
425.76
test_vm_life_cycle.py

@blueorangutan package

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11560

@blueorangutan package

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✔ debian ✖ suse15. SL-JID 11618

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 11624

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 11631

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11634

@blueorangutan test

[SF] Trillian Build Failed (tid-11810)

@blueorangutan package

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 11652

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11656

@blueorangutan test

@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11824)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 54107 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9697-t11824-kvm-ol8.zip
Smoke tests completed. 141 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File


parser_json: fix wrong LoadError warning

Which issue(s) this PR fixes:
None
What this PR does / why we need it:
If Oj is not installed, LoadError with the empty message is raised.

https://github.com/fluent/fluentd/blob/b25e989daf1501e606a6980e64670cbd3a755209/lib/fluent/plugin/parser_json.rb#L53

So, the current condition /\boj\z/.match?(ex.message) does not work and the following meaningless warning is displayed.
{datetime} [warn]: #x {id} LoadError

After this fix, the log message will be:
{datetime} [info]: #x {id} Oj is not installed, and failing back to Yajl for json parser

Docs Changes:
Not needed.
Release Note:
Same as the title.

It seems that this rescue no longer needed. It would be better to do retry at when :oj instead of rescue block.

Thanks for your review!
I have fixed this as https://github.com/fluent/fluentd/compare/151e6314a371add407f602d50cb8be777109afd1..d515b3a6a277d854378a5961223b4666fb438c31

Fixed typo: https://github.com/fluent/fluentd/compare/29ff3815c38bb3f36be0b64a9c27ecae3cdbf11a..891ce71120198fa168232a796d4267a3cdb2c91f

It looks like failing back should be falling back.
For now, this PR does not handle it.
(Changing log messages should not be done casually. For this level, it might be better to leave the existing.)

Thanks!

Thanks for your review!


Docs: 4.x New Helidon Connector

Problem Description
New Helidon connector introduced in PR #7397 needs documentation.

#7641


Additional dim_inactive option for transparent setups

Is your feature request related to a problem? Please describe.
When I set up a transparent setup, I don't like the way inactive windows are displayed. I find it especially hard to make out a popup.
Therefore I would like to use the dim_inactive option. But I, again don't like the harsh contrast between my transparent popup and the now hard background.
without dim

hard to spot
with dim

this looks awkward as well
Describe the solution you'd like
I would like the background color of inactive windows to still be transparent, but just a little more saturated.
Describe alternatives you've considered
I tried lighten or darken or leaving it as is. I will probably keep dim_inactive off if I cant fix it somehow :/
But I thought I might as well suggest the feature as I absolutely love the work you do and am willing to help make it happen <3
Additional context
I would LOVE this feature, as it would complete my setup in terms of color.
I can dedicate time to development if someone points me in the right direction as to where I would even start :)

@Lord-Leonard First of all, thanks for your love for this project! Unfortunately IMO this is technically impossible for us to implement, because the transparent background is achieved by setting the background to NONE, and what you can see is the raw background of the terminal. So, we are unable to make the transparent part look different - for the background there are only 2 choices:

colored and solid
color removed and transparent

we can't make it colored and transparent.
However, I would like to leave this issue open for the possibility that this may be achieved.

What about changing the saturation of the text foreground colors?
I don't know about what is possible in nvim, but I do know that when I first tried the dim_inactive option, I actually assumed it would be affecting the foreground text color.
I guess I am just used to having transparent background for everything.


Try to fix CI

Proposed changes
Just adding memtrace to this list hoping to unblock CI. Not a Nix expert but looks like this should do the trick?
Types of changes
What types of changes does your code introduce to HACL*?
Put an x in the boxes that apply

[ ] Proof maintenance (non-breaking change which fixes a proof regression)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New algorithm or feature (non-breaking change which adds functionality)
[ ] Improved performance (fix or feature that would improve performance of some algorithm on some platform)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[X] I have read the CODE_OF_CONDUCT.md doc
[X] I have read and agree to submit my changes under the LICENSE
[ ] I have added necessary documentation (if appropriate)
[ ] I have edited CHANGES.md (if appropriate)

@W95Psp do I understand correctly that following our discussion on slack, this is no longer needed? or should this instead be merged? your precious advice would be much appreciated... thanks!

Yeah, I think so! @pnmadelaine told me there was something else making the CI fail, but if I understood correctly it's completely unrelated.
So yes, I think you can close that PR :)


Add "last active" flag to refresh tokens table to have indication of last activity of device

Currently only the create and expire date are shown. It would be nice to also keep track of when a device has last shown signs of activity.

Already works because every time refresh tokens is synced a new one is created with a new create date. so the create date is the last active refreshdate sync.


Set set temperature

If I use the KIA app to start the airco I can set the temperature. If I use Homeassistant to start the airco the set temperature is fixed on 15 degrees, which was not enough to clean the front windows.
Is a set temperature setting available in the API? And if so can you integrate it in HA?
I am very happy with this integration, thanks for writing and maintaining the integration.

What temperature are you setting in home assistant when you call the service?

I assume the sensor.set_temperature is the value. I don’t set it, it is a sensor and reports 15 degrees. Can I set a temperature when I call the service?Met vriendelijke groet,William GeurtsOp 11 jan 2024 om 22:10 heeft cdnninja @.***> het volgende geschreven:
What temperature are you setting in home assistant when you call the service?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

You can set when you call the service.
The sensor is current value.  If not running its lowest set point.

Thanks,I installed it years ago but never used it until yesterday. Forgot the options.Met vriendelijke groet,William GeurtsOp 12 jan 2024 om 01:08 heeft cdnninja @.***> het volgende geschreven:
You can set when you call the service.
The sensor is current value.  If not running its lowest set point.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Hi, I tested the service, some settings work, some settings don't work. Set Temperature and defrost works, however the back window and steering wheel is not (these options work in my KIA connect app). Also the seat heating is not working (but this is not an option in my KIA connect app). Als the duration is not working. I'll send my debug log.
kia.debug.log
This is my automation:
alias: Kia_Airco_aan
description: ""
trigger:

platform: state
entity_id: input_boolean.kia_airco
condition: []
action:
service: kia_uvo.start_climate
data:
duration: 1
heating: "4"
climate: true
device_id: XXXXXXXXXXXXXXXXXXX
defrost: true
temperature: 28
mode: single

This issue is not closed, just clicked the wrong button. Sorry for that.

Only items that your car support will work.
Any items working via native app that don't work in ha?

Yes, the backwindow heating  and steering wheel works via the app. I also see that the airco automatically stops, but I cannot adjust that.Met vriendelijke groet,William GeurtsOp 14 jan 2024 om 13:10 heeft cdnninja @.***> het volgende geschreven:
Only items that your car support will work.
Any items working via native app that don't work in ha?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>

Work your way through heating values 1-6 to see which one gets the results you want.

The heating value “1” seems to be the only possible value. With value 1 the front and back windows and the steering wheel are switched on. All other values result in all switched off of these functions. That works good enough for me.Seats are not heated, but that is also not available in the KIA app.Met vriendelijke groet,William GeurtsOp 14 jan 2024 om 20:43 heeft cdnninja @.***> het volgende geschreven:
Work your way through heating values 1-6 to see which one gets the results you want.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>

Does that match the mobile app? Or in the app can you toggle those separately.

Yes, 2 options:1. Front window 2. Sight mirror, steeringwheel and back window.Due to a reconstruction of the road my car is parked somewhere else, it is difficult to test it. I will test it again within a few weeks.Met vriendelijke groet,William GeurtsOp 20 jan 2024 om 14:41 heeft cdnninja @.***> het volgende geschreven:
Does that match the mobile app? Or in the app can you toggle those separately.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>


Text Wrapper crashes without configuration

Running the text wrapper does not work like it is described in the Documentation: LINK
When i just run php -S localhost:8000 vendor/robmorgan/phinx/app/web.php i get a PHP Fatal error:  Uncaught Symfony\Component\Console\Exception\InvalidOptionException: The "--configuration" option requires a value.
(I run this from my project root, there is also a phinx.php located)
It works when i additionally set some Options like this. (It also seems, that default_database from the config file is ignored, and i need to set the 'environment' option.)
$app = new \Phinx\Console\PhinxApplication();
$wrap = new \Phinx\Wrapper\TextWrapper($app);
$wrap->setOption('configuration', 'phinx.php');
$wrap->setOption('parser', 'php');
$wrap->setOption('environment', 'db');

echo $wrap->getStatus();
echo $wrap->getRollback(null, 0);
echo $wrap->getMigrate();
echo $wrap->getSeed();

So ether this is a bug, that the text wrapper crashes without setting configuration, or if the text wrapper needs the configuration this should be mentioned in the documentation.
Edit: Version is 0.6.4

Same in 0.8.0

@piotr-cz If you set the path in $wrap->setOption('configuration', '/path/to/phinx.php'); does this work appropriately?

Yes, it does, like that::
$app = new \Phinx\Console\PhinxApplication();
$wrap = new \Phinx\Wrapper\TextWrapper($app, [
    'configuration' => $appSettings['root'] . '/phinx.php'
]);


Consider WebGL rendering priority.

I already implemented all UI events from neovim.  Last task is rendering using pixi.js (WebGL).
At first, I should check canvas rendering is a bottleneck of this app.

I took profiling while reading a JS file.  Neovim renders whole screen to show the file contents with syntax highlight.
Rendering time was from 6830ms to 6860ms so it took 30ms.
As the result, most time was taken to decode msgpack value from neovim via stdout.  Canvas rendering was performed on Neov...ext at 6854ms (fillText) and Ne...t at 6858ms (fillRect).
As conclusion,  it seems that decoding msgpack value is main factor.

Hmm...
If the way to profile is correct, improving canvas rendering doesn't improve performance so much.  It is better to improve decoding msgpack value (neovim client).


Add remote-execution section to userconfig.yaml

See original issue on GitLab
In GitLab by [Gitlab user @juergbi] on Jul 11, 2019, 16:48
The remote-execution section is supported for user configuration but it's not currently in userconfig.yaml. This inconsistency should be fixed.

This is no longer a requirement since the user configuration is now completely documented explicitly in the documentation, and the userconfig.yaml which is rendered in the documentation only represents the defaults.


How do i turn off the wave?

https://github.com/osrf/vrx/blob/master/wave_gazebo/world_models/ocean_waves/model.xacro
I use ubuntu 20.04 noetic
I'm in the process of controlling the movement of a ship through a basic example of vrx through roslaunch vrx_gazebo vrx.launch.
All parameters in lines 28 to 30 of the link above have been modified to 0. Nevertheless, there was no change in wave motion.
How can I get rid of wave motion?

Have you tried the two options in this tutorial for the "Flat ocean example"? - https://github.com/osrf/vrx/wiki/changing_wave_params_tutorial
I just verified that both methods work on my setup.
Make sure to run catkin_make after making any edits to xacro files.
Also, for option 1 in the tutorial above, change only the gain parameter to 0.0 and leave the other values as is.   I'm not sure the behavior with period:=0.

Closing due to inactivity. Feel free to reopen if you provide further information.


chore: float datatype typo

In my previous commit https://github.com/sqlparser-rs/sqlparser-rs/issues/931 , I think the handling of case for the PostgreSQL type aliases is incorrect. We should modify it to  first letter capitalized

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 6 (66.67%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 87.051%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/ast/data_type.rs
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/parser.rs
1
82.98%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
15516

Relevant Lines:
17824

💛  - Coveralls

This change is related to PostgreSQL alias types.  ： https://github.com/apache/arrow-datafusion/pull/7156
Maybe we can merge this, then publish a release version. @alamb


[Question] Expansion

Steps to reproduce the behavior:
sh start-all.sh
Expected behavior:
Add a master/worker node to an existing cluster
Environment Description::
dolphinscheduler：1.3.2
Hadoop version : 2.6.0-cdh5.13.3
Hive version : 1.1.0-cdh5.13.3
Storage (HDFS/S3/GCS..) : HDFS
Running on Docker? (yes/no) :no
Configuration
../conf/config/install_config.conf
masters="dxbigdata101,dxbigdata103"
workers="dxbigdata103:default,dxbigdata101:default"
Stacktrace
Cannot find the target file path, unable to start. . .
Additional context:
I am expanding the capacity to add a new node, but the installation directory is inconsistent with the existing one in the cluster. I can't find the new node directory when I execute bin/start-all.sh and I can only start the worker on the new node separately.So if I want to use start-all.sh, does the installation path of the new node have to be the same?

The installation directory of the extension node should be consistent with that of the cluster

The installation directory of the extension node should be consistent with that of the cluster

Ok thank you!


[DRAFT] Revert "Add JWT authentication"

Reverts wso2/apk#2005

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

Project coverage is 4.06%. Comparing base (248df53) to head (88a8bdb).
Report is 13 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #2089       +/-   ##
==========================================
- Coverage   26.09%   4.06%   -22.03%
==========================================
  Files          47       6       -41
  Lines        9205     713     -8492
==========================================
- Hits         2402      29     -2373
+ Misses       6672     684     -5988
+ Partials      131       0      -131

Flag
Coverage Δ

adapter
?

common-controller
4.06% <ø> (ø)

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

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


[feat] support alloc contiguous at given index, fix bug related with …

…base alignment

The CI may need to update. Warnings from here should be removed.


Refactor CI jobs to be in their own bash script instead of YML

This will let us run the regressions locally and also be much easier to maintain.

Part of #467


NORMALMODULEFACTORY after-resolve(data) paths

By some reason paths in this event some times are absolute and some times are not. What is the point here?

@bebraw it isn't question, it's more like a bug which cases bugs in plugins. Question is rhetorical here.

Having similar issue, which cause unexpected behavior for some loaders in a particular context. Any pointers so we can make the situation better?

Can you see this in webpack 2?

I'll try to check in it.

Activity.

@NekR problem still exists?

I'm not sure, I'll check with webpack 4.

/cc @NekR friendly ping :+1:


Test topics

Note: module info not added due to split package issues with kafka streams test jar.
Reviewer checklist

[x] New Modules have module-info.java files.
[x] Public types are well-designed:

[x] no public constructors.
[x] prefer interface or impl.

[x] Ensure relevant issues are linked (description should include text like "Fixes #")
[x] Ensure any appropriate documentation has been added or amended

Coverage increased (+1.1%) to 98.229% when pulling b19538f44460ca7521d8c9035fb3c644cda84b5d on test_topics into 742e81c768527ce0b2f789fbe3a85df7fcfbf685 on main.


Add missing prop types for Field, FieldArray and Fields components

Codecov Report

Merging #2709 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2709   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          67      67
  Lines        1383    1383
======================================
  Hits         1383    1383

Impacted Files
Coverage Δ

src/Field.js
100% <ø> (ø)
:arrow_up:

src/Fields.js
100% <ø> (ø)
:arrow_up:

src/FieldArray.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Published in v6.6.0.

@erikras @gustavohenke This PR creates Failed Prop Type warnings when using multiple validators passed as an array (as seen in the docs).

Forget it. Just saw this https://github.com/erikras/redux-form/commit/08a377ead23ab34c3116c8e02782b1c292b5ebec

But it's still missing for FieldArray


Zod validation support

How to use this with zod for validations?
https://zod.dev/
https://www.npmjs.com/package/nestjs-zod

The docs you mentioned should contain all the info you need. This package does not interfere with Nest's validation layer. If you notice something unexpected let me know.


Fix age name from mkcert

This will fix the name of the feature age from mkcert.

@AnimMouse thanks for noticing :) merged


Spelling Error in Settings

I also noticed a spelling error – Temperatire

Fixed in 'devel'.

Updated Keg Cop Beta to 1.1.1-Beta.2


error: Cannot determine word size

I'm trying to build this app and keep getting this error:
.../android-uvc-rtmp-stream/libraries/libuvccamera/jni/libjpeg-turbo-2.0.6/./jchuff.c:391:2: error: Cannot determine word size
#error Cannot determine word size

I'm not familiar with libjpeg-turbo, can anyone help me?
Edit: I'm on Ubuntu, is Windows required to build libjpeg-turbo?

Hey, I think it should work on linux, the one I tested and it does not build is in Windows, but I have it running on MacOS so unix, and github actions is using ubuntu, so it should work in linux

Maybe it's because I use the older version of Ubuntu. I will post the result in the future. TY

I think I know the reason. There is no x86_64 architecture variant in Android.mk for libjpeg-turbo-2.0.6.
I'm using i5-7500 so it is x86_64 architecture. The 1.5.0 version of libjpeg-turbo works fine for me.
Who should I contact with regarding this lib? Because I'm not sure who made your android one.

I made your app to run. I simply ran app on a phone instead of building the project with "Make Project" (hammer button).
It looks like the problem is in my IDE.
Sorry for bothering you.
P.S. It still would be very kind if anybody could explain to me how to make "Make Project" to not ignore abi filters.

I found the same issue, this is related to the abiFilters. Apparently x86 and probably x86_64 is not supported. You need to change the gradle file like this:
https://github.com/alejandrorosas/android-uvc-rtmp-stream/blob/master/libraries/libuvccamera/build.gradle
android {
    ndkVersion "22.1.7171670"
    compileSdkVersion 30
    externalNativeBuild {
        ndkBuild {
            path "jni/Android.mk"
        }
    }

    defaultConfig {
        ndk {
            abiFilters "armeabi-v7a", "arm64-v8a"
        }
    }

    sourceSets.main {
        jni.srcDirs "jni"
    }
}

Thanks @pabiagioli just updated the project with your suggestion https://github.com/alejandrorosas/android-uvc-rtmp-stream/pull/99