[FEATURE REQ] Add support for sandboxPipelineRuns/runId/sandboxActivityRuns

Library name
Microsoft.Azure.Management.DataFactory
Please describe the feature.
Add support to call Sandbox Pipeline Run information and SandboxActivitiyRuns.
Odds are if you are integrating with the API then you will need to test using Debug runs. These methods are not available in the SDK but are available via the Management Rest API and Azure ADF.
base url:
https://management.azure.com/subscriptions/{subscription_id}/resourcegroups/{resource_group_name}/providers/Microsoft.DataFactory/
... factories/{factory_name}/querydebugpipelineruns?api-version=2018-06-01
(with no other parameters)
....factories/{factory_name}/sandboxPipelineRuns/{run_id}/sandboxActivityRuns?
with parameters
startTime
endTime
api-version
If this functionality does happen to exist (or its undocumented but is a method then please direct).

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @shiftychris, I didn't find the corresponding API in the swagger spec, could you please share some documents such as the Management Rest API doc?

Hi @Yao725 - Agreed, I cant see it in the documentation but this call is made in ADF when viewing debug pipeline runs:
https://management.azure.com/subscriptions/[subscription]/resourcegroups/[resource-group]/providers/Microsoft.DataFactory/factories/[factory-name]/querydebugpipelineruns?api-version=2018-06-01

This should be a service-related issue, marked it as Service Attention.

This issue is related to the service side and not the SDK side, so we are not able to help you with it. Therefore, we are closing this issue for now. If you need more assistance, please open an Azure support request. We apologize for any inconvenience this may cause you.
We value your feedback and we want to make sure that your problem is solved. If you think that we have misunderstood your issue or closed it incorrectly, please feel free to comment on this thread and reopen the issue. We will be happy to assist you further. Thank you for your understanding and cooperation.


Ruby on Rails capstone project - Budget app

This Pull request includes all the following Project requirements check:
Design

Followed these design guidelines, including:

Colors.
Typography: font face, size and weight.
Layout: composition and space between elements.

Interactions

Splash screen

A simple page with the name of your app (yes, you need to choose one), and links to the sign up and log in pages.
Sign up and log in pages
The user should be able to register in the app with full name, email and password (all mandatory).
The user can log into the app using email and password.
If the user is not logged in, they can't access pages that require the user to be logged in (all the pages described below).

Home page (categories page)

When the user logs in, they are presented with the categories page.
For each category, the user can see their name, icon and the total amount of all the transactions that belongs to that category.
When the user clicks (or taps) on a category item, the application navigates to the transactions page for that category.
There is a button "add a new category" at the bottom that brings the user to the page to create a new category.

Transactions page

For a given category, the list of transactions is presented, ordered by the most recent.
At the top of the page the user could see the total amount for the category (sum of all of the amounts of the transactions in that category).
There is a button "add a new transaction" at the bottom that brings the user to the page to create a new transaction.
When the user clicks on the "Back" button (<), the user navigates to the home page.

"Add a new category" page

The user fills out a form to create a new category, indicating their name and icon (both mandatory).
The user clicks (or taps) the "Save" button to create the new category, and is taken to the home page on success.
When the user clicks on the "Back" button (<), the user navigates to the home page.

"Add a new transaction" page

The user fills out a form to create a new transaction with:
name (mandatory)
amount (mandatory)
categories (mandatory at least one)
The user click (or taps) the "Save" button to create the new transaction, and is taken to the transactions page for that category.
When the user clicks on the "Back" button (<), the user navigates to the transactions page for that category.

Testing requirements

Created unit and integration tests for all the most important components of RoR application.

Technical requirements

Used Postgres as your database.
Used devise for authentication.

Project documentation

Recorded a video presenting the features of the project:
Video Link

@Alfredbis29 Thanks for the appreciation and your time. 💮


Add support for reconnecting to running Yarn app after driver restart

Added support to GobblinYarnAppLauncher to be able to reconnect after restart to the Yarn application it launched previously. The way it works is straightforward: upon starting, it checks if a file storing the previous Yarn application ID exists, and if so, it reads the previous application ID and checks if the ID matches any active Yarn application. If so, it simply starts the application state monitor. Otherwise, it submits a new application and persist the application ID.
Switched to MetricRegistry for JVM metrics in GobblinApplicationMaster and GobblinWorkUnitRunner since MetricContext no longer supports registering Dropwizard metric instances.
Added some unit tests. More to come once I figure out how to test the parts that interact with Yarn and Helix.

Signed-off-by: Yinan Li<EMAIL_ADDRESS>

@zliu41 @ibuenros @sahilTakiar can you review?

Can we move all processing of the applicationId (storing, reading, deleting the applicationId) behind an interface. That way we can change out where the applicationId is stored in the future. For example, we may decide that instead of storing the applicationId in a file on HDFS, we want to store the applicationid in Zookeeper.

@sahilTakiar updated.

@sahilTakiar updated 9f25a4c.

LGTM

@zliu41 updated 276e858.

Seems java 8 build is consistently failing.

Synced up with @ibuenros. We realized since the file storing the application ID is under a directory named after the application name, if it happens to have two instances from the same user with the same application name (maybe by mistake), the two instances will try updating the same file. So storing the application ID offers no real benefit over simply using the application name to match the application. So I'm gonna remove ApplicationIdStore and FsApplicationIdStore and rely on application name.

Updated 3d72580.

LGTM other than one comment.


RHSTOR 2516: in-transit encryption for internal and external mode of deployment + details page

External mode of deployment

validations still active on the connection details constraint

Internal mode of deployment

when it is disabled

details page

from installed operator

ceph cluster

/assign @bipuladh
/assign @SanjalKatiyar
/assign @GowthamShanmugam

@debjyoti-pandit plz update the PR with list page changes...

enabled encryption

disabled encryption

@debjyoti-pandit we need to add the kebab item at one more place: default StorageSystem list page (check "Add Capacity", exactly same as that)...

/hold
need to remove kebab item as per new requirements (no after deployment scenario now)...

button disabled as the connection details were not entered

the button is still disabled as encryption is optional

/test odf-console-e2e-aws

@SanjalKatiyar can we remove hold label now?

@SanjalKatiyar can we remove hold label now?

/hold cancel

/approve
/lgtm

/lgtm

/test images

/test ci/prow/odf-console-e2e-aws

/test odf-console-e2e-aws

/retest

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

@SanjalKatiyar can we check if the failure is because of the fix or not?

@SanjalKatiyar can we check if the failure is because of the fix or not?

yesterday our odf-console CI was broken, so all the failures were due to that... CI is fixed now, so now it is mostly infra related issues... let;s wait for one more round, if it fails again @debjyoti-pandit rebase the PR once with latest master and push again.

Please re-tag it now, I have rebased it

/lgtm

/retest

/retest

/test odf-console-e2e-aws

Merging as the ci is flaky.


Regex matching filters are not working

Describe the bug

To reproduce

Create a filter using the content message.content match r"\d\d" (took directly from the official documentation).
Screenshots

Chatterino version

Chatterino 2.2.3-beta2 (commit 6499b7c12)
Operating system

macOS Big Sur 11.2 (20D64)
Additional information

Regex filters were merged into master in 5a29198, while you are only on 6499b7c. I think that the nightly build should include regex filters.

Yes, it works in the nightly versions.


Support .depfile.yml as default configuration file

It is also very common to have dotfiles for this kind of tool configuration. In my case that would help to be a bit consistent.
No big deal though.

feel free to use deptrac.phar analyze .depfile
for now i prefer depfile.yml over .depfile.yml.
best practice is NOT HAVING a "default" configuration, because there is no "default" view on software.

feel free to use deptrac.phar analyze .depfile

But I'm lazy :P

for now i prefer depfile.yml over .depfile.yml.

In the end it's more a matter of personal preferences, that's why most accept both: .blackfire.yml, .travis.yml, .phpcs, .phpmetrics.yml, ... Hence the idea of allowing both out of the box.


if statement inside a for loop fails to compile

Putting an if statement fails inside of a for loop.
I was writing some "find the index of the closest vector" code which wouldn't compile, and found this to be the source of the problem.
This works:
    from numba.decorators import jit
    import numba
    @jit(arg_types=[numba.double], ret_type=numba.double)
    def is_five(some_value):
        if some_value == 5.0:
            return 1.0
        else:
            return 0.0

This fails:
    @jit(arg_types=[numba.double], ret_type=numba.double)
    def is_REALLY_five(some_value):
        for i in range(5):
            if some_value == 5.0:
                return 1.0
        return 0.0

This is how it fails:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-15-3b23f7331ceb> in <module>()
----> 1 @jit(arg_types=[numba.double], ret_type=numba.double)
      2 def is_REALLY_five(some_value):
      3     for i in range(5):
      4         if some_value == 5.0:
      5             return 1.0

/Library/Frameworks/EPD64.framework/Versions/7.3/lib/python2.7/site-packages/numba/decorators.pyc in _jit(func)
     77                   "garbage collected!" % (func,))
     78         t = Translate(func, *args, **kws)
---> 79         t.translate()
     80         __tr_map__[func] = t
     81         return t.get_ctypes_func(llvm)

/Library/Frameworks/EPD64.framework/Versions/7.3/lib/python2.7/site-packages/numba/translate.pyc in translate(self)
    926                     # Ensure we are playing with locals that might
    927                     # actually precede the next block.
--> 928                     self.check_locals(i)
    929
    930                 self.crnt_block = i

/Library/Frameworks/EPD64.framework/Versions/7.3/lib/python2.7/site-packages/numba/translate.pyc in check_locals(self, i)
   1135                 else:
   1136                     assert next_locals is not None, "Internal compiler error!"
-> 1137             self._locals = next_locals[:]
   1138
   1139     def get_ctypes_func(self, llvm=True):

TypeError: 'NoneType' object has no attribute '__getitem__'

Strange, works for me with numba 0.48.0 but fails with latest 0.51.1...
from numba.decorators import jit
import numba
@jit(arg_types=[numba.double], ret_type=numba.double)
def is_REALLY_five(some_value):
for i in range(5):
if some_value == 5.0:
return 1.0
return 0.0

Strange, works for me with numba 0.48.0 but fails with latest 0.51.1...
from numba.decorators import jit
import numba
@jit(arg_types=[numba.double], ret_type=numba.double)
def is_REALLY_five(some_value):
for i in range(5):
if some_value == 5.0:
return 1.0
return 0.0

The numba.decorators module was removed, and you can import jit from numba instead.
If you have any further issues, please start a thread on the Numba Discourse (https://numba.discourse.group) describing your issue / question.

The numba.decorators module was removed, and you can import jit from numba instead.
If you have any further issues, please start a thread on the Numba Discourse (https://numba.discourse.group) describing your issue / question.

Thank you for your update.

I tried both versions numba 0.48.0, 0.51.1, still, the if loop is getting failed.

I tried both versions numba 0.48.0, 0.51.1, still, the if loop is getting failed.

@phanirohith thank you for bringing this to our attention. This seems like a regression. Can you please open a new issue and add the code your have as a reproducer. We will take a closer look then. Thank you!


Correction for raw affiliation Western University

Correction needed for raw affiliation Western University
raw_affiliation_name: Western University
new_rors: 02grkyz14
previous_rors: 05cgtjz78
works_examples: W4391459836;W4399709057
contact: bd1fea949f7851a03eed0632faee048f:d81bdb73 @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


fix installation package for MacOS

The path was wrong for MacOS, so I've split Linux/MacOS into two separate headings with the correct paths.

/assign @irbekrm

/ok-to-test

@wallrj thanks - done
I've tested that the downloads work OK.
I was just aware that I personally found it more user friendly to explicitly state which exact OS/arch combination is supported and which isn't. I've added this there as well. Is that better now?

@wallrj build failed because of a spellcheck - can you please advise how to fix it? Or should I just remove the bullet points to get it pass?
+++ Running spell check
    content/en/docs/usage/kubectl-plugin.md
       32 | - linux/amd64
       32 | - linux/amd64
       33 | - linux/arm64
       33 | - linux/arm64
       34 | - darwin/amd64
       34 | - darwin/amd64
       35 | - darwin/arm64
       35 | - darwin/arm64

>> 8 spelling errors found in 1412 files

@def1nity I'm sorry to hear that - the docs were brought in line with the rest of the documentation, namely https://github.com/cert-manager/website/blob/master/content/en/docs/usage/cmctl.md, which also uses go (and curl).
In the old version, you had to install curl on Ubuntu and in the new version you would have to install curl and golang. Maybe that is an overkill to just get the correct OS and ARCH. What do you propose?
@wallrj How would you recommend to proceed? Update both the kubectl-cert-manager and cmctl to only use curl without the dependency on go env? Or separate the guide for Linux and MacOS (and then possibly even for Linux/amd64 and Linux/arm64 and MacOS/amd64 and MacOS/arm64, but as discussed above this would break some reference links to the existing page headers…)

@mirogta Apologies, I'm pretty new to this whole dev, git scenery so I could only share my initial impressions. I've been fighting with linux, k3s, docker, kubectl, awx, networking, proxies, LBs, ingresses and such for a few days now. Loving the whole situation with 95% of all articles/blogs/guides/documents on basic topics being outdated and/or broken/misleading in one way or another... Anyway, I somehow got to the point where certs/https was the next big thing to tackle and while trying to figure out why I couldn't get the plugin to install I stumbled across this #807 by chance as I was following the instructions over at https://cert-manager.io/docs/usage/cmctl/#installation. I didn't encounter any other place or task until now that required or even mentioned golang, even the official looking website I came here from didn't say anything about it. Since I am fairly new, clueless and plenty frustrated at this point I had no idea it was even a thing... I completely disregarded it and now I see that the extension missing from my vm was probably why the cmd was failing... Sorry...
I understand your point about wanting to unify the documentation across common tools and it is totally legit. More info/warnings about such changes in visible places/official channels would improve the user experience a bit. Honestly in the eyes of a noob it just feels like instead of moving on with the deployment I have to stop and figure out why a plugin takes more time to work through than the actual tool :) This got a bit long so I will end with my suggestion - Either place such new requirements like "go" in more and visible places so plebeians like myself can find it easier or just keep both options as long as the old one is viable/working fine and leave the choice to the users. Thanks for asking btw, it was a nice and unexpected change of pace and I'm sorry for the long reply and if I somehow offended you! All the best!

I stumbled on this https://twitter.com/ChrisShort/status/1486436331169501190 and this https://crossplane.io/docs/v1.6/getting-started/install-configure.html#install-crossplane-cli

Looking at @crossplane_io
today. I see something I despise, curl | sh, I pull up the script expecting horrors...
It's actually very clean and makes sure you get the right version for your environment and nothing more. Less than a full screen of shell. I already like this tool.

I share those feelings. Perhaps we should copy the crossplane install script

https://github.com/crossplane/crossplane/pull/1813
https://github.com/crossplane/crossplane/blame/release-1.6/install.sh

@def1nity no worries - there is definitely a lot of potential for improvement! I had my own difficulties with the original documentation, because I've tried to follow it and it didn't work too. Had no idea that the tiny fix would end up raising more issues.
I've raised a separate issue to fix the install and the docs properly, but in the meantime if you just want to install the kubectl plugin (again), you can use this gist:
url="https://gist.githubusercontent.com/mirogta/8e79f33f6c6fa9ceafcafd1fe7e10540/raw/de023115eede47dd1f31bac92cf771db36a26b80/kubectl-cert-manager-install.sh"
curl -sL $url | sh
sudo mv kubectl-cert_manager /usr/local/bin
kubectl cert-manager --help


Dropping a directory onto the form attachments page

The issue
Right now dragging and dropping a directory of files onto the form attachments page does not work even though it may seem to. The page seems to treat the directory like a file and tries to match it to a single attachment; it does not examine the directory's files and try to match them to attachments. If you drop a directory over a single row of the table, the directory will be matched to the corresponding attachment, but then after the request is sent, an error is shown: "Something went wrong: there was no response to your request." Looking at the Backend log, it looks like the request is never even received. Maybe axios throws an error before it sends the request?
Option 1. Support dragging and dropping a directory.
We could add support for dragging and dropping a directory to Frontend. From what I've read, dropping a directory has been supported in Chrome for a while and also works in Firefox and Edge. However, it's still an experimental technology and not on a standards track, and it's not supported in Safari or IE. Given that, I'm a little hesitant to add it to Frontend: our drag and drop functionality already has some IE-specific logic, and I think adding more browser-specific functionality would not be worth the additional complexity.
Option 2. Ignore any directory that is dropped. (Don't seem to work, and don't fail.)
If we opt not to support directory drag and drop, we can still try to detect when a directory is dropped. If we detect a directory, one option is simply to ignore it. In that case, if only a directory is dropped, nothing will happen (there also won't be an error). If files are dropped in addition to the directory, Frontend will try to match the files, but it will ignore the directory.
Option 3. Show an alert if the user drops a directory.
Another option if we detect a directory is to ignore it and show a warning message indicating that directory drag and drop is not supported.
Option 4. Keep the current behavior.
Of course, we can also decide to keep the current behavior. We haven't heard about users encountering this issue, and dropping a directory is not a standardized action, so this might be a reasonable choice.

@lognaturel, @issa-tseng, I wanted to see if you had any thoughts about this issue. Do you have any preferences between options 1–4? (I think I prefer option 3 or 4.) Or can you think of an option 5?

once standardization is achieved, option 1 feels best. until then, i think option 2 is fine.


v1.5.0 regression - No File Matching error

Repo: https://github.com/jzs11/vite-regression-playground
run npm i and npm run build
You shall be able to see the following error:

Downgrade to v1.4.0 the problem is gone.
Thanks!

sorry i made a mistake, updated to 1.5.1 will fixed.

no worries, thanks for the awesome work :)

Hi dude,
I updated to the latest version, the playground repo is working fine, however, my main working repo still seems to have some problems

Any advice would be really appreciated, thanks.

Problem is gone after I installed the following extensions, closing the ticket. thanks for your help !
"eslint-config-standard": "^17.0.0",
"eslint-plugin-standard": "^5.0.0",

I'm still having this issue with v1.6.0, on an astro site. Have stripped it all the way back and confirmed it's the eslint plugin that is causing the issue, adding the standard config doesn't help
https://codesandbox.io/s/quirky-microservice-3zc032?file=/astro.config.mjs


Migration API for the command-line

isqlite create-migration <dbname> <schema-file> which will print out Python code to migrate the database to the given schema.
isqlite schema --python <dbname> which will print out a schema file that isqlite create-migration can accept.

Instead of this proposal, I'm going to have a lower-level API like isqlite drop-column, isqlite add-column etc.


Unable to connect

Below is my failing test. CDRS works (can connect and send queries), but not this driver. I am using Windows 10 and ScyllaDB is running in Docker. The test is not running in Docker.
This is how I start a ScyllaDB instance in Docker:
$ docker run --name db -p <IP_ADDRESS>:9042:9042 -p <IP_ADDRESS>:9160:9160 -d scylladb/scylla
And this is my test
mod test {
    use cdrs::cluster::{NodeTcpConfigBuilder, ClusterTcpConfig, session};
    use cdrs::load_balancing::RoundRobin;
    use cdrs::query::QueryExecutor;
    use cdrs::authenticators::NoneAuthenticator;
    use scylla::SessionBuilder;

    #[tokio::test]
    async fn goo() {
        let node = NodeTcpConfigBuilder::new("<IP_ADDRESS>:9042", NoneAuthenticator {})
            .build();
        let cluster_config = ClusterTcpConfig(vec![node]);
        let session = session::new(&cluster_config, RoundRobin::new()).unwrap();
        let _ = session.query("SELECT * FROM system_schema.keyspaces").unwrap();

        let session = SessionBuilder::new()
            .known_node("<IP_ADDRESS>:9042")
            .build()
            .await
            .unwrap();

        let _ = session.query("SELECT * FROM system_schema.keyspaces", &[]).await.unwrap().unwrap();
    }
}

This is the error:
called `Result::unwrap()` on an `Err` value: IOError(Os { code: 10060, kind: TimedOut, message: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond." })
thread 'test::goo' panicked at 'called `Result::unwrap()` on an `Err` value: IOError(Os { code: 10060, kind: TimedOut, message: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond." })', src\main.rs:22:83
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/f4eb5d9f719cd3c849befc8914ad8ce0ddcf34ed\/library\std\src\panicking.rs:493
   1: core::panicking::panic_fmt
             at /rustc/f4eb5d9f719cd3c849befc8914ad8ce0ddcf34ed\/library\core\src\panicking.rs:92
   2: core::option::expect_none_failed
             at /rustc/f4eb5d9f719cd3c849befc8914ad8ce0ddcf34ed\/library\core\src\option.rs:1266
   3: core::result::Result<core::option::Option<alloc::vec::Vec<scylla::frame::response::result::Row, alloc::alloc::Global>>, scylla::transport::errors::QueryError>::unwrap<core::option::Option<alloc::vec::Vec<scylla::frame::response::result::Row, alloc::alloc:
             at C:\Users\javisser\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\result.rs:969
   4: fortesting::test::goo::{{closure}}
             at .\src\main.rs:22
   5: core::future::from_generator::{{impl}}::poll<generator-0>
             at C:\Users\javisser\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\future\mod.rs:80
   6: core::future::future::{{impl}}::poll<mut core::future::from_generator::GenFuture<generator-0>*>
             at C:\Users\javisser\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\future\future.rs:119
   7: tokio::runtime::basic_scheduler::{{impl}}::block_on::{{closure}}::{{closure}}<tokio::runtime::driver::Driver,core::pin::Pin<mut core::future::from_generator::GenFuture<generator-0>*>>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\basic_scheduler.rs:184
   8: tokio::coop::with_budget::{{closure}}<core::task::poll::Poll<tuple<>>,closure-0>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\coop.rs:121
   9: std::thread::local::LocalKey<core::cell::Cell<tokio::coop::Budget>>::try_with<core::cell::Cell<tokio::coop::Budget>,closure-0,core::task::poll::Poll<tuple<>>>
             at C:\Users\javisser\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\local.rs:272
  10: std::thread::local::LocalKey<core::cell::Cell<tokio::coop::Budget>>::with<core::cell::Cell<tokio::coop::Budget>,closure-0,core::task::poll::Poll<tuple<>>>
             at C:\Users\javisser\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\thread\local.rs:248
  11: tokio::coop::with_budget
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\coop.rs:114
  12: tokio::coop::budget
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\coop.rs:98
  13: tokio::runtime::basic_scheduler::{{impl}}::block_on::{{closure}}<tokio::runtime::driver::Driver,core::pin::Pin<mut core::future::from_generator::GenFuture<generator-0>*>>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\basic_scheduler.rs:184
  14: tokio::runtime::basic_scheduler::enter::{{closure}}<closure-0,tuple<>,tokio::runtime::driver::Driver>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\basic_scheduler.rs:266
  15: tokio::macros::scoped_tls::ScopedKey<tokio::runtime::basic_scheduler::Context>::set<tokio::runtime::basic_scheduler::Context,closure-0,tuple<>>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\macros\scoped_tls.rs:61
  16: tokio::runtime::basic_scheduler::enter<closure-0,tuple<>,tokio::runtime::driver::Driver>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\basic_scheduler.rs:266
  17: tokio::runtime::basic_scheduler::Inner<tokio::runtime::driver::Driver>::block_on<tokio::runtime::driver::Driver,core::pin::Pin<mut core::future::from_generator::GenFuture<generator-0>*>>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\basic_scheduler.rs:176
  18: tokio::runtime::basic_scheduler::InnerGuard<tokio::runtime::driver::Driver>::block_on<tokio::runtime::driver::Driver,core::pin::Pin<mut core::future::from_generator::GenFuture<generator-0>*>>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\basic_scheduler.rs:405
  19: tokio::runtime::basic_scheduler::BasicScheduler<tokio::runtime::driver::Driver>::block_on<tokio::runtime::driver::Driver,core::future::from_generator::GenFuture<generator-0>>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\basic_scheduler.rs:136
  20: tokio::runtime::Runtime::block_on<core::future::from_generator::GenFuture<generator-0>>
             at C:\Users\javisser\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.2.0\src\runtime\mod.rs:450
  21: fortesting::test::goo
             at .\src\main.rs:8
  22: fortesting::test::goo::{{closure}}
             at .\src\main.rs:8
  23: core::ops::function::FnOnce::call_once<closure-0,tuple<>>
             at C:\Users\javisser\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
  24: core::ops::function::FnOnce::call_once
             at /rustc/f4eb5d9f719cd3c849befc8914ad8ce0ddcf34ed\library\core\src\ops\function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I confirm, I reproduced this issue yesterday on my Windows 10 installation. When running examples or tests from the latest main (075ad419649984b7d901ae04b8bfa56783340095), they hang for a while and then fail with the same error. I bisected the main branch and it looks like it started happening since d4330ef51098329e0dbdb95d4886158fb5b5983c was introduced.
I also tried the same test on Fedora and it worked correctly.

I reproduced the issue between a Windows 10 VM and a Linux VM running scylla with docker.
I had some trouble running Docker on a Windows 10 VM because it requires to run a VM inside a VM.
The error is the same so this should probably be fine.
Looking at the logs it seems that what happens is this:

We create a control connection to <IP_ADDRESS>:9042 and query cluster topology information
We query rpc_address from system.local which turns out to be <IP_ADDRESS> - the local address inside Docker
We try to connect to this internal docker address <IP_ADDRESS> - on linux this works, on windows probably fails (at least between VMs it fails)

There was some discussion about querying address from system.local in #154 - it was said that we should use the existing connection's address insted of querying it when SNI is not set.
I will fix it and open a PR.

This is fixed, thanks @cvybhu


allow bright & multiple params in ansi_string_4b

i added bright color variants to sgr_params so that you can use the bright variants of colors (brred for bright red for example). these are different to using the bright sgr param.
i also made it so that the color string is parsed as space delimited words so that you can have multiple params in a color.
for example underscore brblack will add both the underscore param and the bright black param.
none of these changes are breaking since the previous syntax for defining a color works with the space delimited words syntax (its just one word).

Looks good! Thank you!


applySchema can return a new DDF or modify it inplace

Description and related tickets, documents
fix SchemaHandler line separator
Reviewers: @zkidkid
How to test
Describe how this PR is tested. In case manual testing is required, describe how to do so.
PR Progress
Make sure all checkboxes below are checked before merged

[ ] Branch is in format prefix/description (see this)
[ ] Merge check has no conflicts. PR checks passed.
[x] Code review is done.

@zkidkid you used the wrong file separator in your IDE, please make sure it is "n"

@hai-adatao please take note that Huan has added inPlace flag in this ApplySchema function, so we will remove it in PE. (because currently PE process mutate not DDF).

@hai-adatao @zkidkid the flag in PE api will be there, I just move the logic to DDF

@zkidkid this PR has no UT, why merge this?

@zkidkid can you help add UT for this please


[CT-3191] [implementation] generate schema docs for v11

Housekeeping

[X] I am a maintainer of dbt-core

Short description
We need to generate schema docs for v11 after 1.7rc is live
https://schemas.getdbt.com/dbt/manifest/v11/index.html

moving the json files we check in from core to a directory in the getschema repo, running a script to update the index page, and checking that in

Acceptance criteria
https://schemas.getdbt.com/dbt/manifest/v11/index.html points to the docs for the v11 manifest schema
Impact to Other Teams
docs
Will backports be required?
no
Context
No response

https://www.notion.so/dbtlabs/Bump-Schema-Version-dd308bab6a044c7d8cb6935691732ab3#837de27231b747b1ac37a5d5a9d458c5


Add to set-up instructions in readme

[x] specify settings for Anaconda on install
[x] add instructions for using on HPC
[x] switch to python 3.9 when stable release is available via pyenv-win
[x] add instructions for developing on HPC
[x] separate out setup instructions into separate files, and move to \docs
[ ] add to readme 'Repository Contents'

Still need to do add to readme 'Repository Contents' check point, but will add this as a note for myself


Mongodb2 test rule I/O isolated to the target directory

Access to user home directory may cause test flakes.

Does this help fix the jenkins/travis build problem? I'm not exactly sure if it's building with the new settings or not here.

From what I've seen, you'll want to mess around with the ~/.embedmongo directory that gets created.

The painful part about putting anything in the target folder is that it gets deleted on each build. Downloading Mongo on each build is something we want to avoid IMO. I think we just need to make the user folder work...

Makes sense, closing this one out for now. Will come back to the flake when I have a moment.


Add comparison ROS vs eCAL.

Pull request type

[x] Documentation content changes

A comparison between eCAL / ROS. Please review for correctness!

Please wait for my review that I will add soon


post CSV activation changes

Wait to merge until CSV is activated. Still need to determine blockheight for BIP65 and BIP66 in chainparams.

@Pttn @clo-prime
Do either of you know if/when CSV activated on testnet?

I believe it is block 16704 on 2019-01-14. This assumes the segwit start time is set back. Otherwise the chain stalls at block 12872. Segwit activated at block 12672 on 2018-11-30. I think segwit start time needs to be earlier than 2018-11-29.

Thanks, I've altered the testnet parameters, they may need to be tuned to sync with the current testnet (if available).


Remove support for Android versions less than 24

Matter requires RIO, which is not supported on versions < 26.

@mwswartwout are there flags somewhere where we could also update things? Like changing android_sdk_version in build/config/android/config.gni ?
https://github.com/project-chip/connectedhomeip/blob/master/build/config/android/config.gni#L23

@mwswartwout are there flags somewhere where we could also update things? Like changing android_sdk_version in build/config/android/config.gni ?
https://github.com/project-chip/connectedhomeip/blob/master/build/config/android/config.gni#L23

Or Dockerfiles downloading the 21 NDK:
https://github.com/project-chip/connectedhomeip/blob/master/integrations/docker/images/chip-build-android/Dockerfile#L16


Multiple Audio Track support in video

Use case
I am writing to request a new feature for the video_player library: support for multiple audio tracks.
Feature Request: Multiple Audio Track Support
Use Case
I am developing an application that streams multimedia content to users. The content includes movies and shows available in multiple languages, as well as versions with director’s commentary. Currently, the video_player library does not support switching between these audio tracks, which limits the experience for users who wish to select their preferred audio track.
Problem Description
The inability to switch audio tracks within the video_player library has led to a suboptimal user experience. Users are unable to select their preferred language or listen to additional audio content such as commentary tracks. This is especially problematic for multilingual audiences and users who enjoy additional content.
Alternative Solutions
I have considered the following alternatives:
Using Other Libraries: I researched other video player libraries on pub.dev/flutter but found that they either lack stability or do not fully integrate with my existing application.
Custom Implementation: Implementing a custom solution to handle multiple audio tracks. However, this approach is complex and time-consuming, and it would be more efficient if the feature were natively supported by the video_player library.
Proposed Solution
I propose adding functionality to the video_player library that allows for:
Detection of Multiple Audio Tracks: Automatically detect and list all available audio tracks in the media file.
Easy Track Switching: Provide a user-friendly interface for users to switch between audio tracks.
API for Developers: Allow developers to switch tracks programmatically through the API.
This feature would greatly enhance the usability and flexibility of the video_player library.
Thank you for considering this request.
Proposal
https://pub.dev/packages/flutter_vlc_player

This feature request addresses a crucial need in multimedia streaming applications. Currently, the lack of support for switching audio tracks within the video_player library limits user experience, particularly for audiences consuming content in multiple languages or seeking additional commentary tracks. While exploring alternative solutions, such as other libraries on pub.dev/flutter or custom implementations, none seem as efficient or integrated as native support within video_player. Adding functionality to detect and switch between multiple audio tracks would significantly enhance flexibility and usability, making it easier for developers to manage diverse content types seamlessly. I strongly support this proposal and hope it will be prioritized for implementation.


An apidoc resource with slightly different error response types will generate invalid scala

I have an apidoc with a resource with the following responses:
responses: {
200: {
type: "user",
description: "the addressed user id was successfully replaced"
},
201: {
type: "user",
description: "a user was created with this id"
},
400: {
type: "[string]",
description: "This request was malformed"
},
401: {
type: "string",
description: "The user being modified does not match the user name of the authorized user in     the header"
}
}

This is accepted by the apidoc site as valid apidoc. However the scala generator includes the following:
package error {

import codalytic.models.json._

case class ValueResponse(
  response: play.api.libs.ws.WSResponse,
  message: Option[String] = None
) extends Exception(message.getOrElse(response.status + ": " + response.body)){
  import codalytic.models.json._
  lazy val value = response.json.as[Seq[String]]
}
}

package error {

import codalytic.models.json._

case class ValueResponse(
  response: play.api.libs.ws.WSResponse,
  message: Option[String] = None
) extends Exception(message.getOrElse(response.status + ": " + response.body)){
  import codalytic.models.json._
  lazy val value = response.json.as[String]
}
}

which is invalid scala.
The original api.json that generated this issue is in this gist: https://gist.github.com/infomofo/ed0372afa7d872f755a2
The offending endpoint is
PUT users/:username

Thanks for posting! This was already actually already fixed on master - will be available online soon (next few days). The actual code from master looks like:
      case r if r.status == 400 => throw new com.gilt.codalytic.v0.errors.ValuesResponse(r)
      case r if r.status == 401 => throw new com.gilt.codalytic.v0.errors.ValueResponse(r)

Released


More specific message when github auth fails

Please answer the following questions and leave the below in as part of your PR.

[x] This PR corresponds to an issue with a clear problem statement.

#237

[x] I have updated the CHANGELOG.md file with a description of the addressed issue.

[x] I have considered whether I should add more tests covering the code I've changed.

We don't currently write test that assert the contents of error messages on stdin, and I don't see a good reason to change that practice now.

Proposed solution
Invalid Github token error messages before this PR:
$ neil dep upgrade
{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest","status":"401"}
{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest","status":"401"}

Invalid Github token error messages after this PR:
$ neil-dev dep upgrade
Your neil github token is invalid or expired.
Please double check your  NEIL_GITHUB_TOKEN  environment variable.
See neil's README for more details.
Your neil github token is invalid or expired.
Please double check your  NEIL_GITHUB_TOKEN  environment variable.
See neil's README for more details.

Other changes

Behavior outside of error messages is left unchanged
I pulled the environment variables for Github tokens (eg NEIL_GITHUB_TOKEN) into a def in order to provide more specific error messages

Error message formatting
Other error messages are printed with the first line not indented, and following lines indented:
You've hit the github rate-limit (60 reqs/hr).
  You can set an API Token to increase the limit.
  See neil's README for details.

I'm not sure whether this is the desired way to print errors, or if it's accidental, eg code indenting. Clarification welcome!

Thanks!


fix: duplicate schema in type extension

Issue
#331
Summary

Modified visited output to combine ObjectTypeDefinition and ObjectTypeExtension nodes.

Verification

Use type extension in model

type Note {
  title: String
}

extend type Note {
  description: String
}

Run graphback generate and check for duplication in schema as in #331

@ankitjena Great work on this. However, extend keyword has an additional issue I want to check. IF we move to graphql modules I will need to check if dependent modules will be able to see it thru extend (because we will get limited schema. This works now because we are using global contatenated schema). Leave that with me.

@wtrocki Sure

Tried and tested


Guide

A guide to install a C lang IDE or a text editor with a C compiler plugin is much appreciated for new C programmers.

[ ] Windows users (Codeblock, DevC++...)
[ ] Linux users (manual compilation using the terminal)

For Window users: C language IDEs (C compiler GCC included)
Devcpp (DevC++): Download
Code::Blocks: Download
DevC++ Installation Guide:
Step 1) First you must download the Dev C++ on your Windows machine from the link above, you will direct to SourceForge website, and your C++ download will start automatically.
Step 2) After  you finish downloading open the installer, select English then click on "I agree" to prossed further.
Step 3) In this step:

You can see different components of Dev C++ that will be installed with this package.

Just click on “next” button.

Step 4) In this step:

By default, the destination folder is in C drive. You are free to change this destination folder but make sure you have enough memory.

Click on “Install” button.

Step 5) Launch DevC++ and start coding :)
Big thanks to @nemo256 for uploading the C codes that you can review

For Window users: C language IDEs (C compiler GCC included)
Devcpp (DevC++): Download Code::Blocks: Download
DevC++ Installation Guide:
Step 1) First you must download the Dev C++ on your Windows machine from the link above, you will direct to SourceForge website, and your C++ download will start automatically. Step 2) After you finish downloading open the installer, select English then click on "I agree" to prossed further. Step 3) In this step:
1. You can see different components of Dev C++ that will be installed with this package.

2. Just click on “next” button.
   ![image](https://user-images.githubusercontent.com/43763935/204911568-fd8471dc-83d7-4a3a-831c-94f1ccf01d36.png)
   **Step 4)** In this step:

3. By default, the destination folder is in C drive. You are free to change this destination folder but make sure you have enough memory.

4. Click on “Install” button.

Step 5) Launch DevC++ and start coding :)
Big thanks to @nemo256 for uploading the C codes that you can review

Vercy well documented.


nix-update: 0.5.0 -> 0.5.1

Description of changes

Things done
https://github.com/Mic92/nix-update/releases/tag/0.5.1

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 173583 run on x86_64-linux 1

1 package built:

nix-update


.NET Core 3: Patching strategy of client apps

Hi,
This is a question about client security.
How is client security handled in  .Core 3.x ?  In .NET classic the is all handled in Windows via Windows updates which works pretty well.
I mean, if you look at the slew of security patches MS released the last few years with minor and major security issues. Like this one for example.
The reason that I asked this question is that vendors/developers who in the future distribute there .NET software with the Net Core 3 framework could expose there clients to an enormous risk when a security breach in .Net Core happens. This could happen because MS is not patching anymore (which is kind of one of MS goals).
For example:
I, as a software vendor, distributes xaml .Net 4.x software to > 200 clients (some major companies).  .Net security patches gets fixed by MS so all is good.  My clients do not need to worry because MS watches the .Net security space.  If I update the application to .Net core 3 this is not the case anymore? Do I need to watch the security bulletins about .Net and update all the time ?
If this is the case I see a potential big risk because I (an many other vendors with me) don't want to do this (takes too much time, effort) and the risk is to great when it is forgotten. Companies will also not buy my software anymore.
Maybe i'm wrong but it looks like the strategy regarding this one is very flawed and a disaster in the making.

Great question. We're still working on our servicing plan for .NET Core 3. We'll share more information, likely on the .NET blog, when we have a well-defined plan. I understand the crux of your question, that .NET Core today is focused on the server scenario and that client apps are different. We get it.

@richlander do you need this issue open to track this or can it just be closed and referenced from where you are tracking it?

@shawnro @dleeapho, you have a place you want to track this in the github. I know its listed in the larger list of important scenarios to enable but we should keep the community up to date on the plans.

Thanks for tagging us, @Petermarcu.  Agree.  We're still working on getting everything in place for tracking and will be mindful of this as we do.

@shawnro @richlander Is managing .NET Core patches through WSUS/SCCM in the roadmap?  As an enterprise admin with responsibility for ~100,000+ PC/servers I don't want to have to reinvent the wheel.  We already have lots of infrastructure/knowledge/processes invested in WSUS/SCCM for patching and compliance monitoring.

We're analyzing the possibility to enable .net core on all our servers in order to ease migration of apps to Azure. Seeing all the (manual) work required this component in the field is quite significant. Is there any update on this?

@richlander

likely on the .NET blog

please do not do this via a blog post. Blog posts rapidly get out of date and pollute search results. In some cases this is acceptable, but not for content like this. this content should be a first class citizen in the MS owned doco, and maintained/versioned over time

@richlander
Hi,
It is almost a year since I started this thread.  Is there any progress on the matter?
Sincerely,
Edward

We have several issues tracking various aspects of this.  Reassigning to the folks who own this and related issues.

Updates need to be distributed according to the standard method used by each platform. That is, on windows, all updates/patches should be distributed via Windows Update.
But that's not all, there also need to be a built in feature in the .NET Core runtime which makes sure that any application who used NuGet (or something like that) to download and include .NET Core System assemblies in their distribution, and which resulted in .NET Core System assemblies now being hosted and loaded from individual directories for each of these application. Those applications cannot be allowed to load an old, unpatched version of an assembly just because they used NuGet and now have their own version of a .NET Core system Assembly.
This, or something equivalent, need to be in place before .NET Core can be used in an Enterprise Environment.
Also, I'm a bit confused by the remark by @richlander that

.NET Core today is focused on the server scenario

Why implement WinForms and WPF for server environments?
I was under the impression, .NET Core was the future of .NET, and that .NET Framework would not get  anything new and substantial added to it.
Please clarify which version of .NET is aimed for future client side development of GUI Applications, if not .NET Core, then what?
Or is the era of .NET Client side applications over, and everything on the client will be HTML in the future?

@richlander @leecow any updates on this?

As a consultant who creates and maintains client builds for customers it would be very useful to understand how the .Net Core runtime will be patched in Enterprise environments.
Unless this is addressed in Microsoft documentation to which we can refer then it will be a hard sell to recommend using .Net Core to customers until it is.

@richlander @leecow any updates on this?
.NET Core 3.1 is around the corner and our customers want to know how they are patching this when we ship them an application based on .NET Core.
Although the issue title is about client I am more interested in the server side, but the other issues all refer to this one for this topic.

.NET Core 3.1.1 landed today with fixes for critical security issues:

https://github.com/dotnet/announcements/issues/148
https://github.com/aspnet/Announcements/issues/403
https://github.com/dotnet/announcements/issues/149
https://github.com/aspnet/Announcements/issues/402

These CVEs include 3 remote code execution exploits.
@richlander it's previously been mentioned that critical security updates would be pushed out via Windows/Microsoft Update:

If management decides something is serious enough to use Microsoft Update then it will be used.

Will .NET Core 3.1.1 be pushed out via WSUS/Windows Update? It seems like this is a critical update that needs to be pushed out ASAP.

Almost 2 years have past. Still no answer or a solution for this problem. The last year there was a bunch of security problems with .core/standard.
After watching a  populair Microsoft Build presentation there was no mention at all about security of self contained executables.  Still the worries are there.
My conclusion: if there is no answer after almost 2 years there will be none.  This is a problem. It is a potential  legal problem for liability for Microsoft that none wants. Microsoft is Libel because they know about this situation and they don't do what they can to protect (at this time).
My suggestions to Microsoft before its to late is:
A) is that every developer which deploys a ‘Self contained executable’ should be aware by every deployment via a message box popup that ‘the machine is at risk if he/she is not updating his app when there is a security patch’ and that they are subscribed to a security bulletin.
Or
B) Remove the self deploying executable feature.  if explained well everyone will understand.  Its not a ‘Must have’ feature.
Hope it helps!
Edward

@Spelt
As I understand it, the whole thread was about framework dependent deployments and how Microsoft should/will patch the .net core installation that is used in this deployment method.
And I am as worried and frustrated about this situation not being addressed for such a long time as you are.
But I do not understand your last comment and the change of the issue title. When using self contained executables it is clear that the app developer has to manage security updates of .net core himself, as documented in https://docs.microsoft.com/en-us/dotnet/core/deploying/#publish-self-contained:

.NET Core Runtime (distributed with your app) can only be upgraded by releasing a new version of your app. You're responsible for supplying an updated version of your application for security patches to the .NET Core Runtime.

So the actual problem is, that even when using framework dependent deployments the .net core on the machine will not be patched with standard procedures using SCCM/WSUS/etc.
Could you remove the "self contained executables" from the title of this issue? Or do I miss some aspect here?

But I do not understand your last comment and the change of the issue title. When using self contained executables it is clear that the app developer has to manage security updates of .net core himself, as documented in https://docs.microsoft.com/en-us/dotnet/core/deploying/#publish-self-contained:

.NET Core Runtime (distributed with your app) can only be upgraded by releasing a new version of your app. You're responsible for supplying an updated version of your application for security patches to the .NET Core Runtime.

I don't really care how Microsoft do it, but since they are in 100% in control of the Windows Operating System and .NET, they can of course make sure to not load/use a .NET .dll with a known security problem.
Think about it, the opposite would be that Microsoft and Windows williningly and consinesuly load and use a .dll they KNOW contain a security flaw, and where they have a replacement dll without the security problem, perhaps even available directly there on the local machine.

I think its very stupid to not patch .net core and powershell 7 via normal infrastructure.
It might be easy for MS in short term but the shitstorm will be huge after the first wormable hole!
Many many people will miss the fact that both it's not autopatched.
Self contained runtime is the worst idea.

So the actual problem is, that even when using framework dependent deployments the .net core on the machine will not be patched with standard procedures using SCCM/WSUS/etc.
Could you remove the "self contained executables" from the title of this issue? Or do I miss some aspect here?

Two issues really.
Framework dependent relying on installed runtime are not benefitting from a major point of framework dependency, i.e. patching.
Self contained executable deployment lacks a strategy to deal with patching or should be clear that this is entirely the responsibility of the developer.
Self contained has only become an option for me because there's also no policy on an application installing the runtime with difficulty detecting the correct runtime installed, no permalinks to runtime downloads and broken missing runtime download functionality. Pre-requisits for customers to install the runtime following instructions are frequently not followed plus it's confusing with many options to choose from.
I'm unconfortable with self contained for the above reason on patching though.

Self container or whatever, Microsoft should patch it!
If the patch introduce a breaking change, then the user/admin should need to manually opt-in to continue using the flawed assembly.
There's absolutely no excuses or reasons for not doing this!
Whenever I tell my customers that they themselves are responsible of figuring out if there's any security issues with any of the Microsoft assemblies used by a .NET Core application, and then manually figure out if Microsoft has released an update which fix that security issue. If so, they then need to manually go and find and download that update, and manually make sure they get the correct version if more than one is available. Then they need to manually figure out how to deploy this new updated assembly in the correct way for this particular .NET Core application to all the affected machines, then every single one of them decide to continue using .NET Framework where this stuff just works.

Thank you for the feedback and we understand the concerns you are bringing up. We are currently working on the feasibility analysis of servicing .NET Core through Microsoft Updates and other patching strategies as well. We hope to have a direction on this shortly and I will keep this thread posted on the progress in the coming weeks.

@nakarnam How hard can it be? It's not like you haven't done this things before, right?
Here is one way to do it, that is 1000 times better than doing NOTHING for years! And it took less than 5 min to come up with it.

You know which of your assemblies you have patched for security issues.
So one way could be to add the old, unpatched assembly to be detected by Windows Defender. That takes care of the immediate security problem. Now the user or an Admin could opt-in to use the assembly if they so choose.
Transfer the new patched assembly to the client machine via Windows Update.
Whenever a .NET application tries to load the old unpatched assembly, then just copy(overwrite) the new patched assembly to the place where would have loaded the old unpatched assembly from.
If any .NET application is installed in the future which uses the old unpatched assembly and tries to install it, then let it think it has succeeded, but either you catch the install operation of the unpathed assembly when it happens, and just replace it with the new patched version, or Windows Defender catch it and removes it. Then when the application starts and tries to load the unpatched assembly, you just do another step 4.

The important thing is that you do not under any circumstances load and use an assembly you know have a security issue!
So get it done already and then after that, you can sit down and figure out if there's a better way of doing it.

I don't agree that applications should be patched by Microsoft in all cases.

Currently build default is to produce runtime-dependent applications. This means the developer relies on the installed runtime (controlled by user/admin). Microsoft indeed should give automatic security updates for this -- similar to .NET Framework patches (i.e. update mechanism of OS or e.g. enterprise environment / WSUS).

Applications are self-contained if developers opt for this. There are probably different reasons for this. One could be that they want to make sure that the software is stable. I think it is not ok to patch this automatically. This could introduce failure (if behaviour depends on bugs). I agree that in general no one wants to have this situation, but we have to deal with it somehow. It's not clear whether the bug is relevant for this software at all. Most security bugs are irrelevant if the software is running in a secure context.

Blocking DLLs and distributing with known security flaws via Defender is

I don't se

MSFT will never STOP running something - even if they know there is a security issue.
It's the same with cars. The manufacturer can tell you you should not drive, but its up to you to do it or not.
That is as it should be and fine.
I would expect MSFT to deliver patches for the installed dotnet runtimes - as with the .NET Framework.

I stumble upon this thread after scouring the web for information on how to keep the .Net Core runtime updated with the latest security patch, hoping that it was just an oversight from my part and that MS did actually offered a solution to this really important problem.
Suffice to say that after reading the whole thread (and other similar ones), I am not impressed, sadly, and I wish we knew it before moving our applications to .Net Core.
I just wish Microsoft would be more open on this, as we currently have no idea whether something will be implemented to fix this issue, or even if it's remotely considered as a slight possibility in the distant future.
I saw some people speaking about custom-made script to keep the runtimes up to date. I would love to know if they are available on Github or somewhere else. Thank you.

.NET Core refers to several technologies including .NET Core, ASP.NET Core, Entity Framework Core, and more. .NET Core provides Long Term Support (LTS) releases that get three years of free support and release every other year. You choose when to update your application with a release. Patches to LTS releases are compatible which eliminates risk adversely affecting applications.

Source: https://dotnet.microsoft.com/platform/support/policy/
So here is my summary for now:

The runtime will be patched with hotfixes
The patching itself is up to you

I would really like to see an opt-in way of installing the latest patches automatically.
@terrajobst to the rescue?

@lennybacon :
The question is: who is "you".
I think "you" means the developer of product X that is using .NET Core.
Result: I'm as the administrator of the system (admin of the windows server) that uses product X can't patch .NET Core.

you != Microsoft
you could be:

A developer who compiles a new version of a product against the patched SDK.

If self contained that's it
If not self contained the machine where the software will run needs an update to its runtime.

An administrator who updates the .NET runtime on the machine where a product runs.

If it is a patch or minor update ({major}.{minor}.{patch}) it will be compatible.
The {app}.runtimeconfig.json must be edited as with the example below.

Example:
{app}.runtimeconfig.json for .NET core 3.0:
{
  "runtimeOptions": {
    "tfm": "netcoreapp3.0",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "3.0.0"
    }
  }
}

{app}.runtimeconfig.json edited for .NET core 3.0:
{
  "runtimeOptions": {
    "tfm": "netcoreapp3.1",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "3.1.0"
    }
  }
}

It's a little bit unrealistic that an administrator scans all harddrives to find self contained .net apps and modify them manually.
I've created the following app ,Net core console app, targeting core framework 3.0
`
using System;
namespace ConsoleApp
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine("Version: {0}", Environment.Version.ToString());
}
}
}
`
and published it that way:
dotnet publish -c Release -r win-x64 --self-contained true
I've modified the {app}.runtimeconfig.json
to this:
{
"runtimeOptions": {
"rollForward": "Major"
}
}
The app is not running on version 3.1 but 3.0.3
If I replace additionally the published framework files in the directory the app is not starting at all
Error:   An assembly specified in the application dependencies manifest (ConsoleApp11.deps.json) was not found:     package: 'runtimepack.Microsoft.NETCore.App.Runtime.win-x64', version: '3.0.3'     path: 'mscordaccore_amd64_amd64_4.700.20.6603.dll'
Am I missing something?

self contained: Recompile and redeploy
NOT self contained: Update runtime and edit {app}.runtimeconfig.json

And that is meaning for a self contained app I as an administrator can't patch the runtime, only the developer can. -> very very bad

Admins going through editing runtimeconfig.json is a non-starter.
Self-contained apps recompile & redeploy is going to result in a lot of out of date unpatched apps. From experience a lot of customers don't update their apps, even if they have prompts to do so.
Auto updating is on option, but in server environments this may not be possible and in some enterprise environments the servers are isolated from the Internet and are strictly managed by IT for updates. Some companies don't like apps auto updating as they control and certify an application for roll out to production.
Though that much control, they'd do likewise with patches to the framework, but at least they can roll out the patches they want and expect applications using them to pick them up. Just not with .NET Core.
Then there are apps that go out of support, the company that made it stops providing updates, or it's an open source app that's gone stale.

@ckruegerkpmg
In Self-Contained apps the .NET Core libraries are handled the same as every other 3rd party lib and the application itself. No one is patching all the included (open source) libs and nobody is patching the .NET Core libs themselfes, other than the developer itself. As the developer opted for this packaging option, he is the one responsible for the entire package. In this case admins need to see the whole piece of software as one thing that needs to be patched, and not only the .net core within it.
In the other options, the developer relies on .NET Core installed by the admin of the machine before installing the app itself. So in this case the admin is the one responsible for updating both .NET core and the app, but can do this separately.
While Self-contained is not my first choice I see several good use cases for this option. But I do not quite understand the argument that the admin should be able to patch the .net within because he is not patching all the other libs within. Just patch the app itself. It he developers don't provide the necessary update for new .NET Core versions they are not providing update for all other libs as well, so you have to stop using the software at all.

The .Net Core framework is not any library but the foundation.
I would argue that when you watch the history of .net framework classic and especially the introduction of something like UseStrongCrypto it's a bad idea to treat the framework like a common lib.
In an ideal world every developer would patch every problem right away, in reality it won't happen and even if the developer is patching the unpatched timeframe is for the enduser is expanding.
For the NOT self contained variant it's illusory that admins are modifying {app}.runtimeconfig.json
That said and combined with the fact that .Net Core updates are not distributed through regular microsoft update channels it's only matter of time until a cluster security fuckup will happen.

Trying to figure out where this thread is going.  If the .Net core group isn't going to support actual patch management via common tools like SCCM, should we route the developers to using self-contained apps?  (I'm asking specifically for web applications).  As a sysadmin I have compliance requirements to manage, I can't spend all my time chasing down .Net core versions on dev/test/staging/prod every couple of weeks when a new release is dropped.

There are already several patches for .NET Core 3.1 runtime for security fixes (up to 3.1.5 now as of writing) since releasing a product using Framework Dependent deployment. Our installer uses a fixed link to the runtime to download and install the runtime, but this is 3.1.1 as there's no link to direct to the latest (without having the user manually choose from the runtime download page). It appears this isn't going to get patched unless the end user does it themselves and a lot will not.
So this leaves us with going the self contained route. We have a slow release cycle unfortunately so it's very unlikely we are going to be able to release patches at the frequency the runtime has been patched. This is leaving customers open to vulnerabilities.

Analyze the installer script from MS to find the latest patch:
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script

Analyze the installer script from MS to find the latest patch:
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script

"The install scripts do not update the registry on Windows. They just download the zipped binaries and copy them to a folder. If you want registry key values to be updated, use the .NET Core installers."
So it wouldn't appear in add/remove programs or any admin tools on auditing the system for potential patches?

@tjmoore :
Yes, that's the sad truth.
I've found .net core installations that where not added to "add/remove programs" with the execution of:
dotnet --list-sdks
dotnet --list-runtimes
If you wan't the real reality I think you have to write something like a file system scanner that enumerates all .exe and .dll files :-(

I’m wondering now if future anti-virus or intrusion detection software will go off and remove the dll’s because they are out of date/insecure.

Op 16 jun. 2020 om 17:07 heeft ckruegerkpmg<EMAIL_ADDRESS>het volgende geschreven:

@tjmoore :
Yes, that's the sad truth.
I've found .net core installations that where not added to "add/remove programs" with the execution of:
dotnet --list-sdks
dotnet --list-runtimes
If you wan't the real reality I think you have to write something like a file system scanner that enumerates all .exe and .dll files :-(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I’m wondering now if future anti-virus or intrusion detection software will go off and remove the dll’s because they are out of date/insecure.

@Spelt This will never happen. How could a anti-virus system know if the system is air gapped or isolated and maybe not a risk?
Removing *.dlls results in business processes being stopped - which will lead to the demand for payment of damages and lost profits. No anti-virus will ever do this (without the demand of customers - and business focuses on business, not security).

@nakarnam - it's four months later, is it really that hard to get minor versions automatically patched by windows update? Do you have an update for us?
In the meantime, can I at least get an email sent to me when a security patch is released for dot net core 2.1 or 3.1? How else am I supposed to be able to keep these things up to date?

We are moving to SCD as a corporate strategy.  I don't even install the .net core runtimes on the web server, so it becomes an 'application issue'.  Essentially we are treating the web app as a stand alone entity - security issues that arise in .net core are no different than issues that arise from jQuery or any other dependency.
This way .net core never shows up on a nessus scan as a 'system problem'.  I sympathize with sysadmins or devops engineers who feel the dev teams will 'fire and forget' on apps.

I have been working the last year on .Net core.  Initially 2.0, but recently, 3.1.
Specifically, my apps are delivered by AWS as a part of Lambda functions.  Actually getting these AWS functions through multiple layers of testing and change control iterations is not a small job.  Especially when you consider that this work is all for Government!
I have read all of the above, and agree that there are concerns with patching.  However, I don't think there has been mention of patching in the Linux (i.e. AMI) world.  Normally AWS manages all Server patching, but with .net core, that method is lost.
What now?  Do I move to Python or some other terrible alternative?

@nakarnam @richlander - any updates for us?

I will keep this thread posted on the progress in the coming weeks.
It's almost 5 month later - to many "coming weeks" to my mind..

I mentioned our approach earlier in this thread but wanted to provide some additional details (with the hope they will help others).
My main concern on this topic has been manageability.  It isn't feasible to patch dev/test/staging/prod at scale every time the .NET core folks decide to come out with a new release.  In the .NET framework days this was handled by Windows Update (and we as system people could handle it via WSUS, SCCM, etc).  There doesn't seem to be a straightforward way to handle .NET core (I've looked at options like Chocolatey but they weren't ideal either).
.NET core allows web applications to be built/deployed via SCD (Self Contained Deployments).  By including all the .NET core goodness in the application itself, I don't have to install the .NET core runtimes on the IIS server at all.  Per the documentation: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-3.1#install-the-hosting-bundle
I can install IIS
Install-WindowsFeature -Name Web-Server -IncludeManagementTools
and then install the hosting bundle without any of the runtimes:
dotnet-hosting-3.1.5-win.exe OPT_NO_RUNTIME=1 OPT_NO_SHAREDFX=1 OPT_NO_X86=1
.NET Core (the runtime) isn't installed on my IIS servers and doesn't have to be managed.
Now I'm sympathetic to those who say 'what about vulnerabilities that are uncovered in .NET core'?  My response is straightforward:  How do you handle XSS vulnerabilities in the web application?  How do you handle SQLI issues in the web application?  How do you handle vulnerabilities in jQuery or Boostrap or anything else in the web application?  We have to draw a line between what is maintained by the systems/devops team and what is maintained by the development team.  I can't fix an injection vulnerability (nobody wants me digging through source code).  My responsibilities include OS patches, IIS configuration, etc.  The web application itself (including anything specific to .NET core) fall on the dev team (just like any of the vulnerability possibilities I included above).

@blakeduffey how do you keep the hosting bundle up to date, do you manually update that every time a new one is released?

I think that's a fair question.  Without the hosting bundle installed, IIS doesn't understand .NET core applications at all (you simply get a 500 error if I remember correctly).  Since in this model we don't install the runtimes - I wonder if it is necessary to keep the hosting bundle updated?  (if it is simply some configurations for IIS to be able to run .NET core)
I honestly haven't tried installing an older version of the hosting bundle - I can try to provide a better answer next time it is updated (oh look - a new release dropped YESTERDAY 3.1.6, dropped on 7-14).
I'll update the thread when I have more info.

Now I'm sympathetic to those who say 'what about vulnerabilities that are uncovered in .NET core'? My response is straightforward: How do you handle XSS vulnerabilities in the web application? How do you handle SQLI issues in the web application? How do you handle vulnerabilities in jQuery or Boostrap or anything else in the web application? We have to draw a line between what is maintained by the systems/devops team and what is maintained by the development team. I can't fix an injection vulnerability (nobody wants me digging through source code). My responsibilities include OS patches, IIS configuration, etc. The web application itself (including anything specific to .NET core) fall on the dev team (just like any of the vulnerability possibilities I included above).

Not using the system runtime is no option.
We are deploying .Net Core micro services to Service Fabric.
There is a huge overhead (memory & storage) if every micro service deploys it's own .Net Core framework.

In my experience the SCD (self contained deployments) applications do indeed have larger disk footprints than FDD (framework dependent deployments) - but not substantially larger.  I think the application we are using SCD was something like 150MB larger?  I'd have to look.  If someone is running hundreds or thousands on a system maybe it would make a difference?
I'd be interested in hearing if someone has actually profiled an application (FDD vs SCD) and can provide a comparison regarding memory overhead?

The last few comments all miss a main point of this issue: Client applications.
What if you users can't/won't update to newer versions of your app? Then self contained deployment doesn't help at all.

What if you users can't/won't update to newer versions of your app? Then self contained deployment doesn't help at all.

A common situation with corporate customers. Many don't like to rock the boat and won't update something that works. Some will have a complex process of test & validation on software updates which in some cases can take weeks, months or longer!
Although some may be more accepting of patch releases where only security fixes are included, but the vendor is responsible for issuing these each time the .NET runtime has a security release, yet there's no other change to the product.
Official security releases via WU/WSUS etc still may have the approval/test process but often get through IT processes quicker as they're more trusting of patches direct from Microsoft than third party software vendors, and easier to manage.
That said, what about non-Windows? Products I'm working on currently are moving to .NET Core for cross-platform support and will be deploying on Linux as well as Windows. With Linux, there are package managers, and does the same situation apply or will fixes be brought in with package updates? (and if so, why not on Windows?).

Yes, let's not forget corporate customers.  Everyone is saying how easy it is for baking it into your build process is totally ignoring .NET Core (and soon to be 5) on client PCs and corporations that purchase software from 3rd partes.  An accountant who bought a .NET Core client application from a 3rd party isn't going to have a clue about what a .NET is and getting new builds of their accounting software potentially every month.  With .NET Framework, we can at least patch the runtime for clients.
This is going to eventually lead to a big issue when there is some wormable RCE in the .NET Framework that causes a mass headache like what happened with Java in 2013.

I assume "Framework Dependent" deployment on Linux depends on the relevant .NET Core runtime having been deployed by some other mechanism. Ideally on a general-purpose system, this would be a .deb or .rpm-based package manager. .NET Core 2.1 and .NET Core 3.1 are published either through distro repositories or MS's own repository. It seems .NET 5 previews aren't being published to repositories yet.
So coming from the other direction, it makes sense that Windows Update would be able to update a system-install of .NET Core (as used by "Framework Dependent" applications), since Linux systems can (.NET Core 2.1 and .NET Core 3.1), or will (.NET 5) be able to.
Unless the team have dropped support for system-wide installs in .NET 5, have no plans to publish .deb and .rpm files, and just haven't told anyone yet? ^_^
Personally (and addressing the ticket title) I would not expect security updates to touch Self Contained Deployments, as in that case I am taking on the responsibility of tracking updates to .NET and distributing them to users.
That said, I wouldn't use SCD for applications I give to other people to install, but it makes perfect sense when I'm building things in containers, since I'm also taking on that responsibility for every other part of the container as well. There's already a container security-scanning ecosystem which I would hope would gain support (if it doesn't have it already) for telling me that my SCD .NET applications need updating.

The thing is, this title used to be more clear (.NET Core 3: Patching strategy of client apps) and is now VERY misleading for newcomers.
The OP never talked about SCD, and every other issue concerning the .Net Core patching strategy leads to this one (and were closed). Yet, its name does NOT reflect that.
@Spelt  I believe the name should be changed (yes, again...) to reflect the current state of the debate, which is about the patching strategy of .Net Core (either 2, 3 or 5) as a whole (including SCD, of course, but not limited to).

Based on this thread, we conducted surveys, interviews and sought further customer feedback over the past few months. As per the findings, there are three key efforts we are focusing on, for .NET Core Update acquisition, deployment and servicing strategies, in the .NET 5 timeframe:

Offering .NET core updates via Microsoft Update Channels
Tooling for .NET core update discovery, detection and clean up
ClickOnce support for .NET Core Apps

Majority of the Customers were interested in .NET Core Updates being offered via the Microsoft Update Channel (MU). There was interest in the updates being offered via Automatic updates, WSUS and Microsoft Catalog channels. This plan is under review currently for the infrastructure changes, cost and timelines.  This proposal for offering .NET Core updates via Microsoft Update is applicable to Framework dependent deployments only for .NET Core. We have a new issue open to track this effort and provide further details & updates as we move forward. Please post any comments/feedback on the plan here.
For customers that want greater control and do not wish to leverage Microsoft Update, we are also working on tools for update discovery, detection and uninstall, in the .NET 5 timeframe. Planning for a command line experience which utilizes release metadata to recommend updates and provide details, based on user query or what's installed on the machine and can also be deployed at scale to know what's installed across an Enterprise, aiding in uninstalling older/insecure versions.  Initial scope for .NET 5 would include both desktop and server scenarios for Windows platform. I will create a new issue to provide more details and reference it here.
For Self-contained deployments, where .NET Core runtime is bundled as part of an application - the app developer will continue to be responsible for servicing this. We are working on ClickOnce support for .NET Core apps – more details are available in the Deployment Tools repo here.
Will close out this issue and track feedback on these specific efforts separately.

Thanks for the update @nakarnam, I am going to close this issue out in favor of the new, more specific ones.

Hi Jamshedd,
Why did you close it?  Its not solved at all. This is beneath Microsoft.
The above proposal is that developers are still responsible for patching security holes in MS software. There will be a click-once publishing option in VS. Nobody uses Click-once and still Developers need to update years old software.
Not a solution at all !
REOPEN.

I suggest you do not use SCE packaging when developing software or disallow it in your operating environment if you want or need patching capabilities using windows updates. Microsoft provides both alternatives, self-contained and runtime-dependent methods to give developers and admins the choice.
Any developer doing SCE must be aware of the responsibility of patching, and any admin rolling SCE software into his/her servers or clients must accept this (or reject it).
I am glad we have runtime-dependent publishing model starting with .NET Core 3, since I am not a big fan of SCE. However, SCE serves a purpose and is a good tool to have in your workbelt for certain scenarios.

@spelt - @ernstscheithauer summarized this well. What we're giving is options - if an enterprise or LOB developer wants Microsoft to take care of patching, then the framework dependent deployment model is what they should go with. If on the other hand they want to retain tight control over the deployment environment and want to decide when and how to patch an app then the self-contained model would be more suitable.
In the former case the Microsoft ships an update, in the second the app developer is responsible for updating the runtime bits included with their app. Lack of support for such a self-contained deployment was a drawback of the old .NET Framework update model for some of our customers like banks with highly locked down environments and we got many asks for this. We understand this model is not something that works for everyone, so we still have the Framework dependent deployment model for those that prefer something closer to the old way.

Starting in December 2020, we will be delivering .NET Core updates on Windows via Microsoft Update.

https://devblogs.microsoft.com/dotnet/net-core-updates-coming-to-microsoft-update/


AzureFunctionApp@1 Reports Success, But Function is Not Showing Up in Azure Portal

Required Information
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzureFunctionApp@1
Environment

Server - Azure Pipelines or TFS on-premises?

If using TFS on-premises, provide the version:

If using Azure Pipelines, provide the account name, team project name, build definition name/build number: cybot, Infrastructure, #20200304.1

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name: windows-latest

Issue Description
Snippet from pipeline:
- task: AzureFunctionApp@1
  displayName: 'Deploy to Azure Functions'
  inputs:
    azureSubscription: '$(azureSubscription-prod)'
    appType: functionApp
    appName: $(functionAppName-prod)
    package: '$(Pipeline.Workspace)/drop/$(Build.BuildId).zip'

I'm using the above config to publish my function to Azure. Everything seems to work, it's even showing a successful deployment in the app settings for the function app. However, when I try to look at the function, it's not showing up.
I've tried publishing the function through Visual Studio, which works just as expected, so it's not the function app that's the problem.
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Error logs
[Insert error from the logs here for a quick overview]
logs_10384.zip
From deployment log:
[
  {
    "log_time": "2020-03-04T10:53:07.1518526Z",
    "id": "6a0f2e5b-28a5-4c8d-8a23-582a6b989aa7",
    "message": "Updating submodules.",
    "type": 0,
    "details_url": null
  },
  {
    "log_time": "2020-03-04T10:53:07.3862384Z",
    "id": "dfddd6b3-a9d5-41ed-9511-205148569e63",
    "message": "Preparing deployment for commit id 'b8f3450f19'.",
    "type": 0,
    "details_url": null
  },
  {
    "log_time": "2020-03-04T10:53:08.0897722Z",
    "id": "721c4642-ba21-4e93-bca8-fc6c778afb68",
    "message": "Skipping build. Project type: Run-From-Zip",
    "type": 0,
    "details_url": null
  },
  {
    "log_time": "2020-03-04T10:53:08.292898Z",
    "id": "a82c6f88-9ca2-4f63-ad78-0e3fe6b41e0c",
    "message": "Skipping post build. Project type: Run-From-Zip",
    "type": 0,
    "details_url": null
  },
  {
    "log_time": "2020-03-04T10:53:08.4804212Z",
    "id": "54e73939-9d1c-428c-a89b-b5e02ad086d1",
    "message": "Triggering recycle (preview mode disabled).",
    "type": 0,
    "details_url": null
  },
  {
    "log_time": "2020-03-04T10:53:11.2744705Z",
    "id": "28845174-8e41-44ed-9980-1e8e868283a8",
    "message": "Syncing 0 function triggers with payload size 2 bytes successful.",
    "type": 0,
    "details_url": null
  },
  {
    "log_time": "2020-03-04T10:53:11.5088803Z",
    "id": "04f7e7d5-43d7-4de6-aafc-e33904a66b01",
    "message": "Deployment successful.",
    "type": 0,
    "details_url": null
  }
]

@KSiig Are the new functions not visible in azure portal?
Access scm site for your app service. You package gets deployed under home/site/wwwroot. Can you compare the content after deployment via visual studio and post deployment via task. Please share your observations.

Yes the functions are not visible in Azure Portal.
I went into the SCM site, and I think I found the problem. When deploying the from Visual Studio, it's the contents from [projectFolder]/bin/Debug/netcoreapp3.1, and puts it into wwwroot, which is how I think it's supposed to be, and the functions are working.
When deploying via Azure Pipelines, it puts the entire git repository into wwwroot. So technically it has uploaded the files, it's just uploading too many.

Sorry about that, turns out it was my fault in the end. I'm still quite new to Pipelines, and forgot that it isn't this task that packages the zip. I changed the rootFolderOrFile variable in my ArchiveFiles action, to point at the $(System.DefaultWorkingDirectory)/bin/Debug/netcoreapp3.1 directory instead of just $(System.DefaultWorkingDirectory), and that solved the issue.

I am facing the same issue in puthon function app. Any help would be much appreciated

@nadesu , @chshrikh for follow up

@nadesu , @chshrikh for follow up

@Arun7even is this issue still valid for you?

Getting this issue when deploying from bitbucket.

hi i'm facing an issue in my github actions workflow, both build and deploy got success without an error but while i check on azure portal my function app(which is created by github) is not displaying i dont know how to resolve this can anyone help me


Indent

Indent seems to have still some issues when indenting large chunks. For example the last row don't have indentation and some rows may have indentation after the first character.

Fixed.


Odoo dependency libraries

Re-posting into the appropriate project, ref from https://github.com/cloudfoundry/python-buildpack/issues/51
Would you consider adding these deps libpq-dev libxml2-dev libxslt1-dev python-ldb-dev libldap2-dev libsasl2-dev to the rootfs?

These libraries are already in the rootfs:

libpq-dev
libxml2-dev
libxslt1-dev
libldap2-dev

We can consider including libsasl2-dev, particularly since we include libsasl2.
python-ldb-dev is more interesting; rather than including the rootfs version, we may want to consider how the python buildpack can provide these headers.

A quick peek at apt-get reveals that python-ldb-dev pulls in a bunch of others:
cflinuxfs2@a2148315200b:/# apt-get install python-ldb-dev

[snip]

  libldb-dev libldb1 libpython2.7 libtalloc-dev libtalloc2 libtdb-dev libtdb1
  libtevent0 python-ldb

Hmm. I don't think we want to install python into the rootfs without really thinking about it.
Again, I'd like to investigate how we might address this need by providing the proper python dev headers with the python buildpack.

Story to include libsasl2-dev: #130826489
Story to investigate python development dependencies in the python buildpack: #130826731
@charyorde would including python-ldb-dev in the python buildpack address your use case?

CF didn't raise a need for python-ldb-dev when I encountered the error. However, installing Odoo on a vanilla box requires it. I think it's better to be installed now than have the buildpack report a build failure later on.

A few sites (here, here) call it out as a dependency, but it would great to know for sure if you need it so that I can prioritize the story accordingly.

Cool. Thanks

+1 for libsasl2-dev

libsasl2-dev is now on version 1.89.0 of stacks and up: https://github.com/cloudfoundry/stacks/releases/tag/1.89.0.
This is incorporated in v1.38.0 and up of the cflinuxfs2-rootfs-release: https://github.com/cloudfoundry/cflinuxfs2-rootfs-release/releases/tag/v1.38.0

Great. @RochesterinNYC Would this make it into the next CF release?

@charyorde From the looks of the current release candidate: https://github.com/cloudfoundry/cf-release/tree/release-candidate that includes this commit https://github.com/cloudfoundry/cf-release/commit/777072097ac04a22714fe2f92325aaaff39e37c1 bumping the rootfs to 1.89.0, I would say yes.

Very good news. Thanks @RochesterinNYC

Closing due to inactivity, but please keep us updated on how your upgrade goes!


New package: ICEMortgageTechnology,Inc.Encompass version <IP_ADDRESS>

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

This application did not have a silent install switch, however did have /exenoui which was used for the silent install switch.

Manual Validation ended with:

@wingetbot run


Docker image for Windows missing?

reproduction steps

working on Windows / Docker
goal is to include dejavu into docker-compose

# docker version
Client: Docker Engine - Enterprise
 Version:           18.09.4
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        c3516c43ef
 Built:             03/27/2019 18:22:15
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Enterprise
 Engine:
  Version:          18.09.4
  API version:      1.39 (minimum version 1.24)
  Go version:       go1.10.8
  Git commit:       c3516c43ef
  Built:            03/27/2019 18:20:29
  OS/Arch:          windows/amd64
  Experimental:     false

issue
When I try to run
docker run -p 1358:1358 -d appbaseio/dejavu

I get an
docker: image operating system "linux" cannot be used on this platform.

question
Do I make a silly mistake here or is there no dejavu/Docker deployment support for Windows?
Thx for your help
Peter
(=PA=)

@spex66 Thanks for the issue. We don't have windows support right now. But we are open to adding this.
Are you interested in adding support for this, or once we add, helping us verify if it works correctly?

thx for your quick response!
I'm happy to help you verify it, when available.
Sadly I'm not having the skillset to add support for it on my own.
(=PA=)


Populate dropdown onclick

The fact that the <select> remains in DOM and the plugin is adding the same content is a SEO issue, I would love an option to generate <li>'s   onclick event.
Any opinions about this?

You might try using the container option - e.g. data-container="body". When the container option is used, the menu and its inner li elements are generated dynamically each time the menu is opened (rather than being inserted into the DOM by default.

I've tried that, the inner li are first generated @ doc ready then moved in that container. I've modified the script to suit my needs, but i think it's a very usefull option to have.


update CI workflows to use Ubuntu 22.04 instead of Ubuntu 18.04

The Ubuntu 18.04 GitHub Actions runner image has been deprecated on 2022-08-08 and will be removed on 2023-04-01. For more information see https://github.com/actions/runner-images/issues/6002.
Therefore, this pull request switches to the newer runner image.

thanks!


is this lib under development?

Hi there
I've just found this nice lib.
Would like to make a proof of concept for a app i'm planning to do.
Is this lib under development? I'm just asking because there is not a lot of activity (which might also be a good sign :) )
Are there reference projects which are using this lib?
Thanks for any enlightment

Hey, I was wondering also.  @fopsdev Check out hyperx (vdom+string literals) and hyperhtml (dom+string literals), lit-html, and choo.  There are others I can't remember.  This helps too https://rawgit.com/krausest/js-framework-benchmark/


Extension doesn't find achievements from RetroAchievements

Hello, I have configured SS to work with RA but no matter what game I try to find achievements for, SS isn't finding anything for any game that RA supports. The achievements themselves work in all emulators, and my API key and name are correct in Playnite, but it changes nothing.

Hey,
So what you are going to want to do is set everything to their proper platform and not just have everything on them.
This example should help.

Oh my god thank you, it finally worked! It's been months, I had lost hope!


python3Packages.pwntools: Patch check for gdb-multiarch

Motivation for this change
Make pwntools and gdb work to debug non native binaries.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 122873 at 1176e0c9 run on x86_64-linux 1

2 packages built successfully:

pwntools (python38Packages.pwntools)
python39Packages.pwntools

1 suggestion:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/pwntools/default.nix:83:0:
   |
83 |     description = "CTF framework and exploit development library";
   | ^


No gitmessage found when in a sub directory or root directory

This addresses the issue #31
It looks like the main issue is the git version is not extracted correctly.
The fallback command does not work in a window terminal. Perhaps that should be changed as well.

I tried the suggested steps to normalise the line endings but for some reason, there was nothing to commit. I've updated my git settings, so hopefully, this is no longer an issue for further commits.

The fallback command does not work in a window terminal. Perhaps that should be changed as well.


Automated test execution with each Push

Hey @anoop1409 , Please do the required changes, have to merge it asap, read my comments.

@hamhaingaurav I tried to update this same PR with the changes but doesn't seem to work. I created a new one. Please have a look. I am closing this one,