Tracking issue for DefaultAzureCredential (azure-identity) support in azure-batch

Is your feature request related to a problem? Please describe.
In the past the Azure library ecosystem was fragmented in terms of credential handling. An infamous error when trying to work with the alleged standard DefaultAzureCredential is:
AttributeError: 'DefaultAzureCredential' object has no attribute 'signed_session'

According to this StackOverflow question, the goal is to clean up the credentials handling:

As of May 2022, all SDKs have been re-released with native support for azure-identity. If you still encounter this error with a given SDK on its latest version, please open an issue asking for a re-release of that SDK here: https://github.com/Azure/azure-sdk-for-python/issues

azure-batch as of its latest version 13.0.0 (released on Nov 9th 2022) still does not support DefaultAzureCredential.
This issue has been raised a few times before:

https://github.com/Azure/azure-sdk-for-python/issues/23583
https://github.com/Azure/azure-sdk-for-python/issues/28739

The issues vaguely mention that this feature will come eventually (one comment suggesting by the end of 2022, which apparently hasn't happened), but the tickets have been closed, without actually being resolved.
It would be great we can have a proper "tracking issue" that actually gets closed, once the feature really is there. This way, users can really react to the change. Closing the issues without really having resolved the issue only leads to confusion (implying that it might work already), and misses an opportunity to use the issue ticket as an "announcement" to its watchers via the closing action.
Describe the solution you'd like
Re-release azure-batch with DefaultAzureCredential support and keep this issue open until that point.

thank you for opening this issue @bluenote10 we will take a look at this. Also tagging @xiangyan99 to make sure this isn't an identity issue

What makes this issue worst is that originally the necessary work-around with the credentials wrapper was documented on this page:
https://learn.microsoft.com/en-us/azure/developer/python/azure-sdk-authenticate?tabs=cmd
But the documentation of the work-around has now been removed, which is fine for the majority of the Azure ecosystem, but just not Azure batch, i.e., currently even the work-around is undocumented.
Also note that this is creating confusion even for Microsoft engineers. For instance, the original author was under the impressions that

100% of Python SDKs have now support for azure-identity natively, this snippet is not recommended nor necessary anymore as of today

But later corrected that it isn't really 100% due to Azure batch.

Arrived here researching a potential use-case for Batch after reading that, although DefaultAzureCredential() could be used in Automation runbook, such runbook cannot traverse other Azure service firewalls to persist data.  Since Batch can't use DefaultAzureCredential() looks like I'm stuck with expensive databricks solution, unless anyone can advise different.

Not sure if this was the previously-provided workaround, but this worked for me:
from azure.identity import DefaultAzureCredential
from msrest.authentication import BasicTokenAuthentication
from azure.batch import BatchServiceClient

token = {'access_token':DefaultAzureCredential().get_token('https://batch.core.windows.net/.default').token}
credentials = BasicTokenAuthentication(token)
batch_client = BatchServiceClient(
    credentials,
    batch_url=batch_url)

If anyone stumbles across this in the future, the example from Raphtor will stop working after the access token expires. This uses the pipeline to provide credentials as opposed to a static token.
class __TokenProvider(HTTPPolicy):
    def send(self, request, **kwargs):
        credentials = DefaultAzureCredential()
        token = credentials.get_token('https://batch.core.windows.net/.default')
        request.http_request.headers['Authorization'] = 'Bearer ' + token.token
        return self.next.send(request, **kwargs)

The workaround above looks reasonable to me, but FYI we are working on releasing a beta version of the azure-batch package which supports DefaultAzureCredential natively. Hoping to have the first version out in June. (Work is ongoing under this PR)

I'm still seeing this issue, using BatchServiceClient with a DefaultAzureCredential in a locally running Azure function (func start).
[2024-10-15T20:19:17.439Z] An error occurred in "render_begin": 'DefaultAzureCredential' object has no attribute 'signed_session'
Traceback (most recent call last):
  File "C:\Dev\Mozaik\MozaikAzureRender\function_app.py", line 284, in render_begin
    batch_client.job.add(job_params) # returns None
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Dev\Python\Python311\Lib\site-packages\azure\batch\operations\_job_operations.py", line 903, in add
    response = self._client.send(request, stream=False, **operation_config)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Dev\Python\Python311\Lib\site-packages\msrest\service_client.py", line 336, in send
    pipeline_response = self.config.pipeline.run(request, **kwargs)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Dev\Python\Python311\Lib\site-packages\msrest\pipeline\__init__.py", line 197, in run
    return first_node.send(pipeline_request, **kwargs)  # type: ignore
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Dev\Python\Python311\Lib\site-packages\msrest\pipeline\__init__.py", line 150, in send
    response = self.next.send(request, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Dev\Python\Python311\Lib\site-packages\msrest\pipeline\requests.py", line 65, in send
    self._creds.signed_session(session)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'DefaultAzureCredential' object has no attribute 'signed_session'

$ az --version
azure-cli                         2.65.0

core                              2.65.0
telemetry                          1.1.0

Dependencies:
msal                              1.31.0
azure-mgmt-resource               23.1.1

Running pip install -U --force msrest didn't seem to help either.

Not sure if this was the previously-provided workaround, but this worked for me:
from azure.identity import DefaultAzureCredential
from msrest.authentication import BasicTokenAuthentication
from azure.batch import BatchServiceClient
token = {'access_token':DefaultAzureCredential().get_token('https://batch.core.windows.net/.default').token}
credentials = BasicTokenAuthentication(token)
batch_client = BatchServiceClient(
credentials,
batch_url=batch_url)

Works like a charm! Thank you!


v3.0 Query Translation Error for SqlServer provider?

I have a fairly lengthy EF query that was previously working fine before the 3.0 update.  It's essentially a query to load a user and all related rows.
Since 3.0, this query now returns ~50k duplicate rows and takes over 4 minutes to execute.

Am I doing something wrong (other than asking for a lot of joins) or is there something wrong with the API?
Is there a more reasonable/performant manner in which to query all this related data under the new API?
Thanks in advance!
EF Core version: 3.0
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: e.g. .NET Core 3.0
Operating system: Win 10 Pro
IDE:  Visual Studio 2019 Pro 16.3.2

I have same problem and i dont like orderby every field which kills query performence this version is not stable.

Duplicate of #18022

@smitpatel Is it though?  My query should only return a single record, but returns over 50k duplicates.

@smitpatel Is it though? My query should only return a single record, but returns over 50k duplicates.

are you sure? includes will result in duplicated results since you want to obrain data like courses, roles etc for each row you will get result
example https://www.w3schools.com/sql/trysql.asp?filename=trysql_select_join

@smitpatel Is it though? My query should only return a single record, but returns over 50k duplicates.

No, it will not. You start with a user, then go on including courses (more than one per user), and payments.
This gets translated into one query with significant fields repeated over and over - that is how joins work in SQL. There is no real way to do that efficiently and I SERIOUSLY doubt yo ureally want this mother off all queries to start with - looks like extremely broken design from a UI perspewctive.
At minimum you can kill that into multiple separate queries for every part instead of querying all withotu really needing it.

You're right, after closer examination.  That's my fault.  I guess it's easy to jump to conclusions with this much stuff broken and out of whack.  I need to take more time in evaluating stuff before assuming "it's just another thing not working after the upgrade".

They are, but i would flag this query in code reviews with or without those changes.
See, you only pull data you need. If you need all that in different parts of the UI - i want to see that UI ;) That is a LOT of only so so correlated data for one screen. Mutliple tabs? Tabs can ask for data WHEN NEEDED.

They are, but i would flag this query in code reviews with or without those changes.
i want to see that UI ;)

Yeah, I hear you... but this is a very specific client request to have everything show up on one page in a particular way.  I'll end up re-writing it somewhat to mitigate as much as possible, but some requirements can't be argued against when it comes to getting checks signed.  ;-)

I hate to tell you, it is NOT a client request that all this shows up on a page, unless that page is like covering awhole wall. I can udnerstand asking for certain top lines, but then the data amount would be less and you would ask for only top x of any navigation property.
This query can totally be broken down to smaller amounts, with multiple requests running in parallel.

They are, but i would flag this query in code reviews with or without those changes.
i want to see that UI ;)

Yeah, I hear you... but this is a very specific client request to have everything show up on one page in a particular way. I'll end up re-writing it somewhat to mitigate as much as possible, but some requirements can't be argued against when it comes to getting checks signed. ;-)

You can always load data asynchronously i bet its beter to load data overtime instead all with waiting multiple seconds to load page

Sure.  I'm not confused about how to fix it, now that it needs fixing.  But, the fact is (despite your objection), the client did (against all advice) very specifically ask for all data to be loaded on one giant wall of text , with as little white space as possible, and preferably above the fold, as fast as possible.
Some people are just that specific in what they want and how they want it to work based on their work-flow.  So as to avoid premature optimization and unnecessary work, we started off with a naively written query, mostly to see if/how EF Core would handle it.
The results, in 2.x, were acceptable, even with the query written "badly".  Sometimes purity loses out to pragmatism.
Clearly, at this point, we'll either re-write the query to load the data in multiple round-trips manually, or we'll have to move to chunked asynchronous loads and the client will have to live with the loading delays.


Meta Attributes no longer work for seemingly no reason

I noticed that BoxGroups no longer works on my scripts. I thought it was something in that specific script I made, but I couldn't find anything wrong there. I then checked the example scene and it doesnt work there neither. I removed NaughtyAttributes from my project then reimported it, but it doesnt fit the issue. It used to work before on this exact setup with this exact Unity version. I did not touch the NaughtyAttributes scripts.
Version is 2.1.4
My Unity version is 2021.3.9f1
Upon some further investigation, it seems that it affects Meta Attributes as the EnableIf/DisableIf and ShowIf/HideIf also don't work. In case of "ReadOnly", on the sample script, readonly int doesnt work but the rest do (see screenshots below)
Any idea what might be causing this?
Screenshot from the example scene:

I figured out what caused this. It's an asset called NG Missing Script Recovery, that, as soon as I import it, will break MetaAttributes.


Added xSPAntivirusSettings and xSPFarmAdministrators

Added the resources xSPAntivirusSettings (Issue #93) and xSPFarmAdministrators
(still under discussion, currently only a demo)

Hi @ykuijs, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@ykuijs, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

@kilasuit - I see what you mean and I agree. But what about a situation where you want to add an account to the Farm Administrators group, but do not "care" about any other users in the group? Or if you want to prevent a specific user to be added to the Farm Administrator group, but the rest of the members are flexible. With these two properties you have the flexibility to do that, that is why I added them. You can use DSC to "Make it so" :-)
The code contains a check to prevent you from using Members and any of the other two parameters at the same time.

@ykuijs - What are your thoughts on changing the farm administrators one to a more generic group one so that it can be used to add a user to any specific group in any site collection? At a quick glance it appears the logic should work for that scenario, then we can include documentation in the resource (I'm working on shipping this at the moment as well) that details how to add users to the farm administrators group.

From my POV the group resource could essentially have DOMAIN\Domain Users in there as a MembersToExclude and therefore force all accounts in the Domain out of the group which therefore is not a suitable use case IMO.
@BrianFarnhill Which Team/Repo looks after that resource from so that I can feed the above back to?

I.e We have to equate for the people in all situations that may include this as a "best practice" in their resources and that really isn't a suitable scenario at all

@kilasuit Keep in mind though, we aren't resolving groups from AD in here, just adding the entry, so if I added domain users like you describe, that would just make there that "DOMAIN\Domain Users" wasn't in the SharePoint group here, but would leave the other entries in tact, so really it would stop you from adding "everyone" to the group essentially, not blocking us from adding others to the group at all. That's all based on the concept that there is no concept of a "Deny" permission in SharePoint.

Ok so from a Config Mgmt POV you would have a V1 (Farm build) config determined - after that you are making V1.0.1 - Where you should only be amending the smallest possible aspect at a time - which in this case would be if you had in the Members Variable would perhaps be Domain\SPFarmAdmins,Domain\DomainAdmins (as it has a type of String) however if Managed via AD then the changes would infact be done in AD not in SP and therefore making the need for MembersToInclude & MembersToExclude completely irrelevant as the actual work is done in AD?
Even if we remove AD and think Claims then doesnt the same principle apply?

@kilasuit if you are managing the values in AD then you are correct, but not all customers choose to manage the membership of these groups in active directory and instead choose to manage them directly in SharePoint (especially if we talk about making this resource something for all groups instead of just the farm admins, as an AD group wont resolve the members when it comes time to assigning a task from workflow to a SharePoint group for example) so there are scenarios where the AD group thing won't really apply

Even if not managed in AD then the String value for Members should be an array and there would still be no need for MembersToInclude and MembersToExclude
Either way it should accept either a Singular String for a single group - further resolved by AD or the accepted Identity management solution or should accept multiple entries.
And in this instance we are at Farm level Admin so it makes sense to make this as simplistic as possible without thinking about Item Level going forward for this resource in my opinion.

@kilasuit But back to the point made earlier, if you want to use it like that then you'll have a property for that, where you can define a specific list of users or groups from whatever your identity solution is and it will make sure that is what is applied, but if you want to manage it through a list of ensuring some are in and some are not and let exceptions to that be manually managed you can use the two other properties instead. So really we are providing two ways to do it based on however the administrator wants to manage it. I accept your point about wanting to keep it simple, but there are others who argue that the other two options is the better one for them as well - and since they aren't mutually exclusive and it lines up with how the group resource works we can do the same thing here.

I agree with Brian on his last comment. From my POV it is all about providing flexibility in using the resource.

If you want to enforce a specific list of users, great use the Members property. I think I would use this option the most.
If you want to prevent a specific user or group from being added to the list, great use the MembersToExclude property.
If you have the need for a specific user or group (for example a security department) to always be in the list, but would like to leave the rest up to the admins, great again: use the MembersToInclude property.

@BrianFarnhill Let me look into the question about making it generic for groups. This might be an interesting once, since for the Farm Administrators you are specifically requesting the CentralAdmin web application. From a code perspective this is easy, but how to make the different in the DSC configuration easy to understand for the users of the resource. Any suggestions?
And I am thinking about making things clear: The xSPFarmAdministrators resource is for changing just one group, the Farm Admins and that is it. The name says it all.
We can then reuse the same logic/code for a new resource xSPGroup (or whatever we call it) where we can add/remove groups in site collections and maintain the members of it.

@ykuijs - I've finished my reivew, some notes on what is here:

When adding files to the project make sure you save the visual studio project as well and include it in the commits
All resources must have corresponding unit tests

I got on a roll when reviewing it and wrote these for you - you should see a pull request in your repo to pull from one of my branches in to your dev branch with these fixes - have a look over them and when you push them in to your dev branch they should turn up here automatically. After that I'll get this merged in to the main dev branch.

@BrianFarnhill - I have been using Powershell ISE so far, instead of Visual Studio so I have not edited the Visual Studio project. Will check this out and switch over to VS.
Am not familiar with creating Unit tests. Will check your pull request on what you have done and make sure I include these in the future. Might be coming back to you with questions on this topic ;-)

@ykuijs No worries - email me questions as needed :)

@ykuijs Thanks for merging the changes in on this one, I'll merge and close this off now.


"WARNING: Outdated server version (VF2), expecting VF3. Please update your chroot."

Running Ubuntu Trusty with XFCE on my Samsung ARM Chromebook.
Since updating to the latest ChromeOS version, I get the warning "WARNING: Outdated server version (VF2), expecting VF3. Please update your chroot." every time I start my Ubuntu Crouton.
What does it mean and what do I need to do to update my chroot?
Chrome version is:
Version 43.0.2357.125
Platform 6946.58.0 (Official Build) stable-channel daisy

I got the same issue on Pixel after I update it to DEV channel Chrome as follow:
Version 45.0.2431.0 dev (64-bit)
Platform 7173.2.0 (Official Build) dev-channel samus
Firmware Google_Samus.6300.128.0

Fetch a new crouton installer, run sudo sh ~/Downloads/crouton -u to upgrade your chroot.

Thx for tonyxue
It works but you need to specify your chroot_name if it is not "precise"
sudo sh ~/Downloads/crouton -n chroot_name -u

You also need to specify your chroot name when doing the upgrade.  So for Trusty, this would be:
sudo sh ~/Downloads/crouton -u -n trusty


[0][Hard][App] Pear Creator Feature

WIP
Extra modal in PearAI that opens up in side panel (in the future can have full screen mode). Within, have the ability to prompt, which then generates files and code. Users can choose to save changes, reject or apply changes. Why the extra modal? This makes it much easier to make changes to the generated files and code and re-prompt because they appear in a "different context window" than the rest of the files. This is going to be somewhat similar to Cursor's Composer feature, but we're gonna make it open source for everyone to have!
We're trying out a new thing 👀:
OPEN-SOURCE BOUNTY (read more here: https://trypear.ai/blog/open-source-bounties):
Merged: $400
Worthy Attempt: $100

Aight done pay up 400 bucks


"Does not have clipboard access" when using the copy button in data output.

After running a query and trying to copy the data output using the copy button in the UI I get a small message stating "Does not have clipboard access".
I would be nice to be able to do that.

I'll ask to Docker Desktop dev teams how to fix that,
As a workaround you could use PGAdmin tool using a browser at http://localhost:59080/browser/, on that situation clipboard copy works fine.
Marcelo.

Works for me when using browser, thanks @marcelo-ochoa 👍


How to Serve static content(React), use node/express or caddyv2 or nginx?

Describe the task
How is the frontend bundle in frontend/ going to get served?  We mostly want this in actual OCP deploys, it's fine if localhost just has npm run dev and runs a local dev server.
Having a node/express server on the frontend (eg Nest) would provide more flexibility as we have a whole web server, can customize routes.  This pattern is called "backend for frontend" or BFF. (cf https://blog.frankel.ch/backend-for-frontend/  - and https://microservices.io/patterns/apigateway.html)
Caddy is golang, has certs built into it.
Nginx (engine-x) is probably more powerful, but harder to configure.
Acceptance Criteria

[ ] Answer how we're going to host static react content.

SME/User Contact
(may want to use a persona to fill this in)
Additional context

any additional details that could not be captured above

https://microservices.io/patterns/apigateway.html


Can't use npx next build with fastly's js sdk

Following the instructions to use edge dictionaries, this is also reproducible in this repository's example project.
In package.json:
"dependencies": {
  "@fastly/js-compute": "^1.3.4",
  ...
}

In e.g. _app.js:
import { ConfigStore } from "fastly:config-store";

tsc compiles fine. webpack does not:
> npx next build --no-lint
warn  - Linting is disabled
info  - Checking validity of types
info  - Creating an optimized production build
Failed to compile.

fastly:config-store
Module build failed: UnhandledSchemeError: Reading from "fastly:config-store" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "fastly:" URIs.
    at /Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:395974
    at Hook.eval [as callAsync] (eval at create (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:13:28771), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:13:25925)
    at Object.processResource (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:395899)
    at processResource (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:1:267616)
    at iteratePitchingLoaders (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:1:266975)
    at runLoaders (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:1:270879)
    at NormalModule._doBuild (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:395761)
    at NormalModule.build (/Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:397789)
    at /Users/nieldrummond/projects/next-compute-js/examples/my-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:81243

Import trace for requested module:
./pages/_app.js

> Build failed because of webpack errors

What's the recommended approach?

Hi @fussybeaver, thank you for reporting this issue. Could you please post your webpack config? You may have to "tell" webpack how to handle fastly:*-namespaced module imports, this way specifically:
  externals: [
    ({request,}, callback) => {
      // Allow Webpack to handle fastly:* namespaced module imports by treating
      // them as modules rather than try to process them as URLs
      if (/^fastly:.*$/.test(request)) {
        return callback(null, 'commonjs ' + request);
      }
      callback();
    }
  ],

Thanks for the hint.
In this case, I am using the one in this repository: https://github.com/fastly/next-compute-js/blob/main/examples/my-app/next.config.js
I've added the externals stub, but it complains of an unexpected property. This is using next 12.3.0.
npx next build --no-lint
warn  - Linting is disabled
warn  - Invalid next.config.js options detected:
  - The root value has an unexpected property, externals, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, future, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).

See more info here: https://nextjs.org/docs/messages/invalid-next-config
info  - Checking validity of types
info  - Creating an optimized production build
Failed to compile.

fastly:config-store
Module build failed: UnhandledSchemeError: Reading from "fastly:config-store" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "fastly:" URIs.
...

Do I need to use a specific webpack version ? I can see some documentation on the externals field when I google around.

Hi @fussybeaver, apologies for the delay in responding. I think you'll need to update next.config.js with an amendment to the webpack config it uses under the hood. Let me know how you get on with this gist: https://gist.github.com/doramatadora/377450b576d79a5b9c30e22d17ba5166


generate error about "headers"

npm run generate

my pages

list.vue

what's wrong and how to fix ???

This error comes when you try to access req.headers somewhere (maybe in a middleware for your project).
When using nuxt generate, keep in mind that req & res are undefined. See https://nuxtjs.org/api#context

@Atinux thanks for your reply.
you are right. But still don't understand.
I write a middleware for get user-agent, and use in layout.
export default function (context) {
  if (context.isServer) {
    let ua = context.req.headers['user-agent']
    context.app.store.state.isWX = !!(/micromessenger/.test(ua.toLowerCase()))
  }
}

I just get some info ,  didn't change any thing.
How can I improve the code??

After thinking , I try get userAgent in client.
so generate done without error.
but I think it's should running in server.

@didiself it cannot run on the server-side since no server is run when nuxt generate & no navigator is used to generate the route.


[language][move] Added typing tests [part 5]

Motivation

Added tests for typing pass.
Tried to cover +/- cases for each check. Covers:

Acquires
Type Inference
Subtyping

Test Plan
ran em

@bors-libra r=tzakian

:pushpin: Commit 5436bf0 has been approved by tzakian

:hourglass: Testing commit 5436bf043eb155df0b35dd5652b8adffc79d5dc3 with merge 59fd3fea45c32292c13721c58491ae32c8786a8b...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: tzakian
Pushing 59fd3fea45c32292c13721c58491ae32c8786a8b to master...


Add template badge

Description
👀
Related Issue

This PR fixes or closes issue: fixes #
Motivation and Context

How Has This Been Tested

Types of changes

[ ] 🐛 Bug fix (non-breaking change which fixes an issue)
[x] 🚀 New feature (non-breaking change which adds functionality)
[ ] 🌎 Translation (addition or update a translation)
[ ] ⚙ Tech (code style improvement, performance improvement or dependencies bump)
[ ] 📚 Documentation (fix or addition in the documentation)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have tested the change locally.
[ ] I followed the steps if I add a new language .

Is it possible to change the background color of the card?
When using mushroom-chips-card, I use card_mod to set the background color like this:
    card_mod:
      style: |
        ha-card {
          --chip-background: rgba(255,0,0,0.25);
        }

As badges are not cards, I don't think it's possible to apply style using card mod.

Oh, that's a same.
Thank you for this budge, it is very nice!

That's the biggest thing I miss in this card set, being able to apply styles or at least, the color scheme to the background too :(


Serve assets from public/ instead of .

By serving assets from the root directory you cannot have routes that have names the same as the folders built in such as src or any other you add to the app.
If we put index.html and all other static assets within a public folder this would only expose the assets that are needed.

A little sad that issue 503 isn't a crashing bug 😞

By serving assets from the root directory

Are we serving assets from root directory? If we are, we should disable that. We never intended this to be the case.

eg hitting http://localhost:3000/src/ it will show the contents of the folder and any file within is shown.

Um, this certainly was not the intention.
Would you like to send a PR to disable this?
I imagine some WDS option does it.

Would you be opposed to the creation of a public directory to house all static assets? Honestly not 100% sure if there's another way to do this other than making an assets folder that would house all static assets and be accessible via localhost:3000/assets/my-asset.jpg

What is the use case for doing that, as opposed to importing asset files from JS?

If I understand this bug correctl, serving favicon like files for things like iOS etc requires something like it:
<link rel="apple-touch-icon" sizes="180x180" href="/static/icons/apple-touch-icon.png">
<link rel="icon" type="image/png" href="/static/icons/favicon-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="/static/icons/favicon-16x16.png" sizes="16x16">
<link rel="manifest" href="/static/icons/manifest.json">
<link rel="mask-icon" href="/static/icons/safari-pinned-tab.svg" color="#0f7852">
<meta name="msapplication-config" content="/static/icons/browserconfig.xml">

I currently have a static dir in my root, and then a build task that moves the directories in that directory  in the build tree after npm build.  Don't know how else to serve those assets both in dev and prod.

@davidascher I think that use case will be addressed by #226 and #413.

Agreed, those PRs seem to be sufficient.

Looking now i dont think #226 is sufficient. I'd propose hoisting index.html into src and having the other static files included via webpack in some way.
@davidascher I stated it in #226 but having a static folder I think would be a mistake because it provides 2 places for assets to go without a clear reason for them to be in any particular location. All of the assets in your example do not require a specific name so could go though transformations to gain cdn busting abilities and a unified pipeline.
I guess this issue is really asking for a way to have webpack parse and replace static files within the index.html? as well as disable webpack dev server's serving of assets that aren't linked to properly.

That’s the approach I’m going to take in 0.5.0.


Dependent variables in the simulation should be parametric for scenarios evolving over time/trajectories

Dependent variables in the simulation that should be parametric for scenarios evolving over time/trajectories: (1) weather, (2) electricity supply mix, (3) prices of energy, (4) occupancy of buildings & schedules of occupants, (5) electricity demand

Can you provide a better description. or is it still relevant?


Add internal support for [[Get]]/[[Set]] receiver

Prerequisite for #1025, this pull adds a tv_recv argument for duk_hobject_{get|put}prop() which corresponds to the Receiver argument for [[Get]] and [[Set]], needed by several ES6+ algorithms and methods:

http://www.ecma-international.org/ecma-262/6.0/#sec-ordinary-object-internal-methods-and-internal-slots-get-p-receiver
http://www.ecma-international.org/ecma-262/6.0/#sec-ordinary-object-internal-methods-and-internal-slots-set-p-v-receiver

Checklist:

[x] Add support for Receiver argument of [[Get]]
[ ] Add support for Receiver argument of [[Set]]
[x] RELEASES entry

ES6 [[Get]] is very straightforward, Receiver is used for is the this binding of a getter call (if one is made) and nothing else.  Data properties will always be read from O, never Receiver.  So overall the changes for getprop are trivial.
Semantics for [[Set]] when Receiver !== O, however, are quite strange.  The property descriptor is taken from O, but the value is written to Receiver.  I guess this is nice in that it allows for virtualization property writes, but it seems inconsistent with [[Get]].
So in the end the necessary changes for putprop are decidedly less trivial and will need a bit more time and thought to fully implement.  Please stand by. :)

For ES6 [[Set]], two property descriptor lookups are required: Once for the target object, then again for the receiving object.  If either or both has {writable:false} then [[Set]] fails.
I think it would be best to optimize for the case where Receiver === O, as that will be the common case and can avoid the second writability check entirely.  For now the only time this won't hold is when a receiver is passed to Reflect.set() which probably won't occur that often in real-world code.

I'll need to think about this a bit. Adding the extra parameter to every property get/set may not be the best approach because the parameter is very often not needed and will impact the performance of every operation.
I'm not sure what the best alternative is though - and if there is none, this is probably a good opportunity to clean up the internal property access APIs which are not ideal in their argument/value stack handling. In particular, the internal calls take duk_tvals but in practice need to make copies of them to stabilize them against side effects.

So maybe a good intermediate step (regardless of what happens with this pull) would be to list the ES6 semantic changes and internal rework needs for property handling. This would give a better idea what needs to be done. Some rework approaches I've been prototyping with involve rewriting around 50% of the property code to make it easier to work with so it'd be best to address multiple issues at once.
Also Sets and Maps (especially WeakSet and WeakMap) are somewhat related: they need a key/value structure but the keys are objects. For footprint it might be best to implement them using the same data structure as plain objects, so that they key space would be extended from strings (just like in Lua BTW). On the other hand it would be more modular and easier for maintaining property code if they were separate.
Not saying this can't be merged BTW, just want to think about this topic a bit more before doing so :)

I actually didn't realize when I first opened this pull how deep the rabbit hole went... :)
MDN documentation for Reflect.set() says the receiver argument is used only for this in setter calls and doesn't mention the redirection behavior for data properties at all.  I know MDN is sometimes wrong but this strikes me as a major documentation deficiency that is very likely to trip someone up.
As a result I got a nasty surprise when I cross-referenced against ES6 (well... actually 7) and found that I had to do two property descriptor checks and write the property to the receiver, NOT the target object.
So no huge pressure to merge this if it doesn't make sense to do that now. :)

Skimming through ES7 real quick there seem to be only two cases where [[Set]] is called with a Receiver different from the target object:

Proxy exotic [[Set]]: http://www.ecma-international.org/ecma-262/7.0/#sec-proxy-object-internal-methods-and-internal-slots-set-p-v-receiver

Reflect.set(): http://www.ecma-international.org/ecma-262/7.0/#sec-reflect.set

Both are uncommon enough I'd imagine that taking a performance hit for even an extra branch for all property writes (fast path check) is probably unacceptable.

For the Proxy case the problem is we never know beforehand if a property read will eventually hit a Proxy. If it does, the argument needs to be available somehow.
But it is possible to optimize it so that if the receiver == target (which is almost always the case if I've understood correctly) the call site doesn't need to give it explicitly and the Proxy call site can assume the value is the same. The other call sites would need a different API which allows the values to be different.
In practice this might be unworkable because there would be two different property access paths. The argument could also be NULL and a modern compiler would technically be able to optimize the whole code path with that assumption (specific function variants with constant argument values are created by compilers) -- in practice that will almost certainly not happen for something as large as property access code and there's no standard way to "nudge" a compiler to do it.

Assuming a bit more rework:
The current internal property access API takes values as duk_tval pointers but needs to copy them to locals to stabilize the pointers against side effects. This is a workaround because I didn't first realize it's going to be so difficult to avoid with essentially any side effect potentially affecting the value stack. So it might be cleaner (and even faster) to just pass the values via the value stack instead.
Another potential need is to pass around a flags field to control property access; without that it'd be awkward to implement e.g. primitives to read properties without side effects, reading only own properties, and so on.
These two taken together mean that the receiver wouldn't need to be provided on the value stack by default and a flag DUK_PROP_RECEIVER_PRESENT could then only be checked in the Proxy case to see which value to use.
For the value stack indexing to work reasonably the receiver would need to be pushed first (if present), followed by key and value (for "set"). This way property code could assume key is at -2 and value is at -1, and receiver, if present, is at -3. Property code would only pop two keys and for the call sites where an explicit receiver is used, the call site would be responsible for popping it off.

It actually surprised me that Duktape passes tagged values around by reference internally - I'd expect them to be passed by value in most cases.  Although I guess a pointer is usually half the size on most platforms.

Passing them by value quite often leads to them being passed via the C stack rather than registers which produces pretty awkward code at least on (some) 32-bit platforms.

@svaarala If you think this change doesn't make sense in its current form, I'll close the pull to be revisited later (perhaps in a Proxy rework).


[#400] Plan details playbooks support

fixes #400
Notes

~Will squash all the WIP commits after review (reason: see 2)~ Done
~One way to test this locally is to reset --hard HEAD^^.  That will undo a cleanup commit and the commit that removes the mocked data/API responses.  Using the nightly db (or any db you have that has in progress plans), go to Plans in Progress and click on any plan.~  Things to check

Download Log dropdowns
Success notifications after "downloading" a playbook log (pre or post)
Info Popovers~

Will need help verifying playbook log download implementation
Should be merged with or after https://github.com/ManageIQ/manageiq-content/pull/355

Screens
Running Post-migration Playbook

No Playbooks

Running Pre-migration Playbook

Playbook Log Download Success

Playbook Log Download Failure

https://bugzilla.redhat.com/show_bug.cgi?id=1564250

Looks good!
Will be testing this some more on the appliance today.

Gaprindashvili backport details:
$ git log -1
commit 6d8758f2124b69374c256b42ab60187951a0966b
Author: Aparna Karve<EMAIL_ADDRESS>Date:   Tue Jul 24 12:35:08 2018 -0700

    Merge pull request #442 from michaelkro/playbooks-plan-details

    [#400] Plan details playbooks support
    (cherry picked from commit 18e320d73da6da62b5ccf316d1ca0bb666c02790)

    https://bugzilla.redhat.com/show_bug.cgi?id=1608420

@michaelkro @AparnaKarve Travis is now failing in Gaprindashvili branch. I think it's caused by this PR. Can you please take a look?
/home/travis/build/ManageIQ/miq_v2v_ui_plugin/app/javascript/react/screens/App/Plan/components/PlanRequestDetailList/PlanRequestDetailList.js
  212:3  error  renderInput should be placed after overlayTriggerClick  react/sort-comp
  238:3  error  onSelect should be placed before setPage                react/sort-comp

https://travis-ci.org/ManageIQ/miq_v2v_ui_plugin/jobs/410122179

@simaishi I've put up a PR against G to fix the errors https://github.com/ManageIQ/miq_v2v_ui_plugin/pull/524


Implement RustBackedValue as a marker trait + converters

It is incongruous that RustBackedValue is not implemented with converters.

Make RustBackedValue a marker trait.
Pick a better name for RustBackedValue.
Implement Ruby <-> Rust with TryConvert.

This ticket is obsoleted by https://github.com/artichoke/artichoke/pull/707.
Boxing and unboxing is a fundamentally different operation than type marshalling, because it must preserve the source.


Use semantic versioning for API Umbrella releases?

The 0.9 and 0.10 versions were recently released. What versioning convention is being used for API Umbrella releases? What are your thoughts about using the Semantic Versioning convention for release versioning, if it is not already in use?

Yes, we use semantic versioning (which is why despite 0.10 being pretty small, we bumped the minor version, since there were a couple of small new things).
I added some new documentation on our release process, where I clarified anyone releasing packages should use semantic versioning, but let us know if you think this should be also documented anywhere else.


Improve deletion messages so they match the native explorer ones

This is a simple one. I just changed the message in the deletion dialog to match the one when using the native vscode explorer. The message and detail are different depending on if the file is dirty or not.

Ok, I think now all the cases are handled. I wasn't sure where to place the utility functions to get the appropriate message. Maybe fileUtils.ts would have been a better place? Let me know what you think and I can change their location if you want.

I handled a few more cases and fixed a small bug. I ended up moving the confirmation logic to fileUtils.ts. I think it fits better there. This ended up being more complex than I expected but I think we are good to go.

LGTM thanks!


Code coverage and testing

We need to provide code coverage of the code in the project.
We can spilt it between backend and front end.
We ideally should test as we go. Meaning that we mock feature functions and simulate input and output.

This is something to discuss as we develop more features. David installed react testing library for the front end.

@un7c0rn we need to complete this task before we can ship the MVP.
@dzx11 would you like to make sure that we have 90% + code coverage.

@bernardbaker We have the code for exercising the backend, I'm interested in seeing coverage metrics. Any recommended tools for Python?

Hi,
Pytest-cov if you're using pytest. Which testing tools are you using?
Regards,
Bernard
On Wed, 23 Sep 2020, 21:57 un7c0rn<EMAIL_ADDRESS>wrote:

@bernardbaker https://github.com/bernardbaker We have the code for
exercising the backend, I'm interested in seeing coverage metrics. Any
recommended tools for Python?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/un7c0rn/stopthevirus/issues/26#issuecomment-697968401,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHNTTG6DYOT3SITDPCFOL3SHJOKBANCNFSM4MGNMULA
.

A simple output of the coverage is what's needed.
I'm going with cypress and instanbul on the front end.
We're aiming for 100% coverage right?
Looking forward to getting started.
Regards,
Bernard
On Wed, 23 Sep 2020, 22:01 Bernard Baker<EMAIL_ADDRESS>wrote:

Hi,
Pytest-cov if you're using pytest. Which testing tools are you using?
Regards,
Bernard
On Wed, 23 Sep 2020, 21:57 un7c0rn<EMAIL_ADDRESS>wrote:

@bernardbaker https://github.com/bernardbaker We have the code for
exercising the backend, I'm interested in seeing coverage metrics. Any
recommended tools for Python?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/un7c0rn/stopthevirus/issues/26#issuecomment-697968401,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHNTTG6DYOT3SITDPCFOL3SHJOKBANCNFSM4MGNMULA
.

@un7c0rn @dzx11 I'm blocking out time tomorrow to get UATs done.


Service workers are now proper interns.

About the PR

When you have 15 hours in in total of "civilian" role you now get locked out of picking service worker. They have always been intended to be an intern role, even to the point of not allowing you to be an antagonist, but never locked you out unlike the others.
Why / Balance

This PR makes the role consistent to the others, as a learning role instead of being a service "assistant" that quite often doesn't do much in a round or is just unclear as to what the role is.
Requirements

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl: Ubaser

tweak: You are now locked out of the service worker role when you get a total of 15 hours in service.

Damn, no more picking Service Worker on low pop so I could bartend, cook food, and handle botany at the same time. Also the service requirements are already so low for chef+bartend+botany I feel like fellas would never really choose em, the role is in a very strange spot.

бля чё это за говно ебаное

Dunno how I feel about this. Despite how it was originally envisioned, Service Worker has grown to be the “do-it-all” of the service department, and are practically the senior role that never got removed.

Why does this job even exist?

Why does this job even exist?

To allow new players to learn about most service roles, without being dedicated to a specific one.

That seems like a solution in search of a problem, they can just learn the jobs as an Assistant if they don't want to commit.

Why does Service need its' own Assistant role? Assistant already exists.

Why does Service need its' own Assistant role? Assistant already exists. New players are either going to be

reading the wiki, which tells them about the HoP
asking for help on radio, at which point a crewmember can point them to the HoP
asking for help in person, at which point a crewmember can point them to the HoP

We know, its undergoing discussion as to what should be done with the role but this is a fine QoL fix in the meanwhile.

Why are any of the intern roles locked out anyway?

Going to draft this temporarily while reworking it to be a proper role without locking you out of being antag, as per a poll I hosted internally

Why are any of the intern roles locked out anyway?

I think in the past they were used as greytide but with department access

Why are any of the intern roles locked out anyway?

I think in the past they were used as greytide but with department access

Honestly this is an issue with how department job role abandonment is viewed also really. Part of me wanted them punished more, but the other issue is that, you could be a returning player and not have access to the intern role and literally be shit on for being a "bad xyz" at whatever department because you dared take a break.

Why are any of the intern roles locked out anyway?

I think in the past they were used as greytide but with department access

Honestly this is an issue with how department job role abandonment is viewed also really. Part of me wanted them punished more, but the other issue is that, you could be a returning player and not have access to the intern role and literally be shit on for being a "bad xyz" at whatever department because you dared take a break.

  Command members are required by the rules to understand their department.(unless your an engineer and the entire station is pissed off about not having power lol)

Shouldn't be an intern because it's a completely unique role and isn't just "X role but with an A for its job logo"
Even has unique access and clothes


Magisk Canary (22002) + Riru Core (v. 23.9) + Riru Unshare Module is able to bypass root detection using isolated process

the lastest Magisk Canary (22002) + Riru Core (v. 23.9) + Riru Unshare Module by vvb2060 definitely kill the root detection by this app.
Riru unshare module allows Magisk Hide to handle isolated processes.
any idea to handle this issue?

I havent tried it yet. If it is addressed in magisk, then this app goes into the dead pool !

the lastest Magisk Canary (22002) + Riru Core (v. 23.9) + Riru Unshare Module by vvb2060 definitely kill the root detection by this app.
Riru unshare module allows Magisk Hide to handle isolated processes.
any idea to handle this issue?

Have you actually tried the Riru-Unshare Module? Can it truly bypass isolated process?


Stratus always adds zeros to the deployed contract bytecode at the end

Stratus always adds zeros to the deployed contract bytecode at the end.<PHONE_NUMBER>00000000000000000000000000000000000000000000000000000000

It was noted those were added by the EVM.

from https://cloudwalk.slack.com/archives/C066PLE20AC/p1718381466996999

I'll close this since this seems to be a non-issue.


committing changes in new branch

##Update
merging new with default --Branch-- see

--hi--

committing


Add Portfolio Projects Section

Hi there, great project. I'd like to add a section for portfolio projects but my front end dev skills are lacking. I've done my best with material-dark and side-bar in my fork but I think material-blue in particular could use a third column. I'm not sure how to do this with flexbox. Would anyone like to help me add this section to all the themes?

Here's an example

https://github.com/salomonelli/best-resume-ever/pull/5

Projects options should be there. Please consider.

I'm not sure what you're referring to n1tesh


Add sphinx based documentation

The following commits look fine:

Add exasol-toolbox as development dependency - commit 9af28476553535f83d1791e7ff6446cb27e7b018
Add Sphinx-based documentation skeleton - commit 5983c4e6dd716bd506a78375f411a288401afbaa
Convert changelog for Sphinx-based documentation - commit 22521bf051c0118a581a3c1b9a882f56b2b4b261
Remove multiversion build - commit 9c5a22916ec6ba5a979bfbec8fe2663e05e33bba
Add best practices to the user guide - commit 7c04e9fca85138a76d7b60a94f5fc46f2072c18f
Add DBAPI Compatibility Documentation - commit 8d0d11e3bdff1d5aa126e1733e479911739a6216
Add documentation for dependencies - commit 4ce0665c86c63991e26bca131c48150594afb652
Rename dbapi documentation - commit 5f2278822b02203f874a85fa0a2dff7843ac52d9
Add documentation regarding design decisions. - commit be535ea1e4301bd044257ef9a138cc6179c9429d
Convert the developer guide to RST format - commit 61ebeb288f51700760c7086f3c09e2ea1403714a
Convert encryption documentation to RST - commit c36ea4f09fae11d948dc4c4971596e286d694ae0
Convert Examples Documentation to ReST - commit 447a8e9865ba315cedd91f35cd505c153bfa53b4
Reorder the index for the user guide - commit 3bfb914fc6cd9d853de2c3b01c0b229da5652c7b

Note: For the RST format documents resulting from converting and renaming the old documents in markdown format I did not thoroughly review contents, typos, style, grammar or formatting.
I propose to do that in a seconds step after the conversion is completed.

I additionally reviewed the following commits.
Note again: For the RST format documents resulting from converting and renaming the old documents in markdown format I did not thoroughly review contents, typos, style, grammar or formatting.
I propose to do that in a seconds step after the conversion is completed.

Please fix.

Last not least: There are some Unchanged files with check annotations mentioned in the PR. Please fix.

From what I understand these are fallse, positives.

I additionally reviewed the following commits.
Note again: For the RST format documents resulting from converting and renaming the old documents in markdown format I did not thoroughly review contents, typos, style, grammar or formatting.
I propose to do that in a seconds step after the conversion is completed.


INT telemetry NApp v1 implementation placeholder

INT NApp v1 implementation placeholder.
This placeholder will be replaced when more specific tasks of blueprint EP31 gets mapped as issues and implemented.
@jab1982 I'll go ahead and assign this to you, feel free to start breaking down implementation tasks as you think it's suitable to be delivered and reviewed.

Once we have a new repo for the telemetry NApp feel free to map the issues there, I initially created here this placeholder to show up on 2023.1 filters.

The tasks have been broken down into this epic epic_telemetry_int_v1, so I'll go ahead and close this old issue that was just a placeholer.


non ascii characeter error

Describe the bug
Add Some Chinese character into node block
To Reproduce
Steps to reproduce the behavior:

Add some Non Ascii Character into node
select node
See error

Expected behavior
No Error window pop up
Screenshots

Desktop (please complete the following information):

OS: Windows
DCC Maya
Version 2020

Supporting full unicode is something we would like to do, but it currently isn't on our roadmap. Of course, we will gladly accept community contributions if you or someone else would like to take on the task.


DebugPrintable renamed issue

I install pod in my objective -c code and it's give me error like this for many class on pod file
DebugPrintable has been renamed to CustomStringConvertable

Hi @narolachirag
I've double checked this lib. There's no DebugPrintable in recent versions. Could you please update to the latest version?


Duplicating tf.keras.layers.Layer inputs to prevent "Graph disconnected" errors

To prevent disconnected graph errors, which can occur if the list input to (concatenate) layers is modified after calling them, as it a common approach to build certain types of network graphs, e.g. DenseNets.
Fixes #30355 and #32023. Similar to https://github.com/keras-team/keras/pull/6035 of standalone Keras.

The issue seems to have been fixed by @omalleyt12 's commit (816ec796ea6a96940188356628566ed11a11c186).

@csachs thanks for confirming , will be closing the PR.


[minor] Fixing syntax warnings

Minor contribution. Fixing compiler warnings:

syntax for => in 2.13
and useless expression

:+1:


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/543 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit ad3d9f4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded

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


programs/pkey/rsa_decrypt.c doesn't initialize rsa structure -- crash

This file does not call mbedtls_rsa_init and thus may crash if mbedtls_rsa_free is called before the structure is fully initialized (for example if rsa_priv.txt is missing and it jumps to the exit label).

I think this is a duplicate of #691, which has a fix in #728 that's pending merge. Please reopen or reply if you disagree.

Woops, didn't see.


Clean up errors and warnings page

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Reference/Errors-and-Warnings.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Reference/Errors-and-Warnings.md
:white_check_mark:Succeeded

docs/Tools/Package-Manager-UI.md
:white_check_mark:Succeeded

docs/Tools/media/ConsolidateTab.png
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Feature - run scans from npm pacakge name

Please check if the PR fulfills these requirements

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

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature Implemented scans from npm package name. fix #33

What is the current behavior? (You can also link to an open issue here)
NONE

What is the new behavior (if this is a feature change)?
Scorecard can scan based on npm packages

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
NO

Other information:

The e2e tests are failing in main
Random Seed:<PHONE_NUMBER>
Will run 14 of 14 specs

E2E TEST:FrozenDeps E2E TEST:Validating deps are frozen
  Should return deps are frozen
  /Users/naveen/go/src/github.com/ossf/scorecard/e2e/frozen_deps_test.go:14

• Failure [0.836 seconds]
E2E TEST:FrozenDeps
/Users/naveen/go/src/github.com/ossf/scorecard/e2e/frozen_deps_test.go:12
  E2E TEST:Validating deps are frozen
  /Users/naveen/go/src/github.com/ossf/scorecard/e2e/frozen_deps_test.go:13
    Should return deps are frozen [It]
    /Users/naveen/go/src/github.com/ossf/scorecard/e2e/frozen_deps_test.go:14

    Expected
        <*errors.errorString | 0xc000098370>: {
            s: "gzip: invalid header",
        }
    to be nil

    /Users/naveen/go/src/github.com/ossf/scorecard/e2e/frozen_deps_test.go:26


Use inline classes once JDK supports

Motivation
The inline class supported by the Valhalla project may be introduced in JDK17~Next LTS after JDK17, and will significantly improve the memory layout of value-based classes

Motivation
The inline class supported by the Valhalla project may be introduced in JDK17~Next LTS after JDK17, and will significantly improve the memory layout of value-based classes

Notes:

Use IdentityHashMap for Map<? extends PrimitiveObject, ?>

If we are lucky, we can take 1~2 days to adapt our codes (we are very familiar with the usage of primitive class) to primitive classes, specifically Primitive Objects + Unify the Basic Primitives with Objects, and we can expect they will be published in JDK 18 after viewing (btw, I have waited for the primitive object for years, if there is no this project, I may not write Turms in Java).
And takes 2~3 days to test it to ensure it won't break the code of our dependencies.
And we will just test the system by mainly sending 1 million client requests to check if any bug caused by primitive class occurs.
If it really breaks our deps, we will just try to not use the deps with primitive objects.
But the good news is: A lot of important implementations (like requests/responses of RPC, entities serialization for MongoDB, etc) are written by us, meaning we can control and adapt them to primitive objects.
Note that we don't need to expect Universal Generics(https://openjdk.java.net/jeps/8261529) because I guess it will be published as a preview in JDK 19~21. When it really comes, we will just adapt our code for it again, which is just a piece of cake.

We now start to develop turms servers based on the development version of Valhalla in https://builds.shipilev.net/openjdk-jdk-valhalla/ and we won't publish our changes for it until JEP 401 is delivered in the mainline of JDK


Top direction scroll loads whole pages in iOS Safari.

Version
2.4.4
Vue.js version
Nuxt v2.8.1
Steps to reproduce
Access https://peachscript.github.io/vue-infinite-loading/guide/top-dir-scroll.html on iPad that's easy to understand.
What is Expected?
It should work like desktop browser.
What is actually happening?
Top direction scroll loads the whole data.
So if data has 5 pages, it loads 5 times whether scroll is on the top.

#243

#243 doesn't work for ios.

This issue caused by "display: flex" and "flex-direction: column-reverse" css properties.
Fixed.


Impracticable Performance to Many Edges Creation to One Vertex

OrientDB Version: orientdb-community-3.2.7
Java Version: OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu220.04)
OS: Ubuntu 20.04.3 LTS
Expected behavior
Create many edges to one vertex with a reasonable performance.
VertexA1 -> VertexB1
VertexA2 -> VertexB1
VertexA3 -> VertexB1
...             -> VertexB1
Actual behavior
When I've tried create many edges to one vertex the performance slow down very quickly and turns to impracticable.
What can I do to guarantee a reasonable performance?
Note: I've tested with sql.graphConsistencyMode=notx_async_repair and ridBag.embeddedToSbtreeBonsaiThreshold=-1 trying to improve the performance, but the behavior was the same.
Steps to reproduce
I've used Post Command Rest Api with CREATE EDGE E1 UPSERT #rid to #rid. To create edges between vertex class that don't have a "Supernode" we have a reasonable performance.
Regards.

Hi,
At first suggestion is to update to the last hotfix 3.2.13, there have been performance improvements, over all OrientDB that should show significant boost, on the other side can you share some numbers just to try to understand what is slow and fast for you.
Regards

Hi tglman,
Thank you for your return. I'll try with this hotfix.
The best performance that I've got to this situation is 500000 edges on 8 hours, it's 17 Edges per second. With another type of Edges where I don't have one "supernode" the performance is more than 1500 edges per second.
Regards.

Hi tglman,
I'll try apply the hotfix on this week and return my sight.
Thank you so much for your help.
Regards

Hi tglman,
Sorry for late to return, but I need to apply and test the hotfix. The performance is better than the old one that I reported. We can create Edges with one vertex of destination with more than 2000 lines per second.
Thank you so much for your help.
Regards

Hi,
Thank you for reporting back, I will close this.
Regards


hostname property for WinRM::Connection

While troubleshooting a custom profile code that was parsing the hostname of the target like this:
inspec.backend.instance_variable_get(:@hostname)

I've discovered that the @hostname property is available for Train::Transports::SSH::Connection, but not for Train::Transports::WinRM::Connection:
[5] pry(#<Inspec::Resource::Registry::Ssl>)> inspec.backend
=> #<Train::Transports::SSH::Connection:0x000000039ad988
 @cmd_wrapper=nil,
 @connection_retries=5,
 @connection_retry_sleep=1,
 @files={"c:\\Windows"=>#<Train::Extras::LinuxFile:0x000000034360b8 @backend=#<Train::Transports::SSH::Connection:0x000000039ad988 ...>, @follow_symlink=true, @path="c:\\Windows", @spath="c:\\\\Windows">},
 @hostname="<IP_ADDRESS>",
 @logger=
...

[5] pry(#<Inspec::Resource::Registry::Ssl>)> inspec.backend
=> #<Train::Transports::WinRM::Connection:0x00000003cd9580
 @connection_retries=5,
 @connection_retry_sleep=1,
 @endpoint="http://<IP_ADDRESS>:5985/wsman",
 @files={"c:\\Windows"=>#<Train::Extras::WindowsFile:0x00000002461840 @backend=#<Train::Transports::WinRM::Connection:0x00000003cd9580 ...>, @follow_symlink=false, @path="c:\\Windows", @spath="c:\\Windows">},
 @logger=
...

The hostname can be extracted from @endpoint, but for consistency, it wouldn't hurt to have it in @hostname as well.

We should probably also add an accessor for that data rather than requiring people to use instance_variable_get.


Add run decision to each workflow test

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
CI update
Motivation

All test workflows should run on PR approval. Once they have passed there is high confidence that this feature doesn't create logical regressions and can be merged. This automates our existing internal process.

What is the current behavior? (You can also link to an open issue here)

There is a run_all_tests workflow which triggers on each PR approval.
However, if one test workflow fails there is no straightforward way to rerun just that failed test workflow.
Because workflows can occasionally fail due to factors outside of our control, we should be able to retry failed workflows without needing to rerun previously succeeding test workflows.

What is the new behavior (if this is a feature change)?

Removes the run_all_tests workflow, as there is no straightforward way to rerun a failed test workflow
Logic is added to each test workflow that triggers it when a PR is approved
New summary job added to each test workflow, which reflects the status of the success or failure of workflow run

We can add a branch status protection rules based on these summary jobs

Have unit tests been run against this PR? (Has there also been any additional testing?)
Manually testing and observing behaviour:

Confirmed that check_should_test_run checks out the correct branch
Confirmed that the summary fails if a run is cancelled: https://github.com/marqo-ai/marqo/actions/runs/5958530333/job/16162939432
Confirmed that the summary passes if the tests pass https://github.com/marqo-ai/marqo/actions/runs/5958633159/job/16163715330

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

Running all-non unit tests pipelines:

arm64: https://github.com/marqo-ai/marqo/actions/runs/5958947463
CUDA DIND: https://github.com/marqo-ai/marqo/actions/workflows/cuda_dind_os_CI.yml
DIND OS: https://github.com/marqo-ai/marqo/actions/workflows/dind_os_CI.yml
LargeModel unit tests: https://github.com/marqo-ai/marqo/actions/workflows/largemodel_unit_test_CI.yml
LocalOS: https://github.com/marqo-ai/marqo/actions/workflows/local_os_CI.yml


[BUG] Nodesniffer doesn't use my configuration

What is the bug?
The Sniffer seems to use a different client than the one that I defined in my bean.
The Sniffer now fails with the error because it doesn't use the HttpRequestInterceptor I defined (see code below)
2023-02-13T16:04:57.755+01:00 ERROR 47226 --- [nt_sniffer[T#1]] org.opensearch.client.sniff.Sniffer      : error while sniffing nodes

org.opensearch.client.ResponseException: method [GET], host [https://xxx.amazonaws.com], URI [/_nodes/http?timeout=1000ms], status line [HTTP/1.1 403 Forbidden]
{"Message":"User: anonymous is not authorized to perform: es:ESHttpGet because no resource-based policy allows the es:ESHttpGet action"}

But queries with the OpenSearchRestTemplate are working
How can one reproduce the bug?

create a RestHighLevelClient Bean with an Aws4Signer and an HttpRequestInteceptor

What is the expected behavior?

The Sniffer should work when the client works

Do you have any additional context?
My configuraiton:
@Configuration
@RequiredArgsConstructor
public class OpenSearchConfig extends AbstractOpenSearchConfiguration {

    private static final String SERVICE_NAME = "es";

    @Value("${opensearch.uris}")
    private String endpoint;

    @Value("${aws.region}")
    private String region;

    private final AwsCredentialsProvider credentialsProvider;

    @Override
    @Bean
    public RestHighLevelClient opensearchClient() {
        Aws4Signer signer = Aws4Signer.create();
        HttpRequestInterceptor interceptor = new AwsRequestSigningApacheInterceptor(SERVICE_NAME, signer,
                credentialsProvider, region);

        RestClientBuilder restClientBuilder = RestClient.builder(HttpHost.create(endpoint))
                .setHttpClientConfigCallback(hacb -> hacb.addInterceptorLast(interceptor));

        return new RestHighLevelClient(restClientBuilder);
    }

    @Bean
    public OpenSearchRestTemplate openSearchRestTemplate(RestHighLevelClient client) {
        return new OpenSearchRestTemplate(client);
    }
}

Maven dependency:
        <dependency>
            <groupId>org.opensearch.client</groupId>
            <artifactId>spring-data-opensearch-starter</artifactId>
            <version>1.0.0</version>
        </dependency>

@SnuK87 you create the instance of the RestClientBuilder manually, this is not going to work with sniffer since you do not use the builder provided by auto configuration. Please define the customizer instead:
    @Bean
    public RestClientBuilderCustomizer customizer() {
        return new RestClientBuilderCustomizer() {
            @Override
            public void customize(HttpAsyncClientBuilder builder) {
                 Aws4Signer signer = Aws4Signer.create();
                 HttpRequestInterceptor interceptor = new AwsRequestSigningApacheInterceptor(SERVICE_NAME, signer,
                credentialsProvider, region);
                builder.addInterceptorFirst(interceptor);
            }

            @Override
            public void customize(RestClientBuilder builder) {
                // No additional customizations needed
            }
        };
    }

    @Bean
    public OpenSearchRestTemplate openSearchRestTemplate(RestHighLevelClient client) {
        return new OpenSearchRestTemplate(client);
    }

@reta Thanks for the quick response and the explanation.
At first the signature was rejected but calling the addInterceptorLast() method on the builder did the trick.


Implementing crate dialect

I believe this is only a small amount of work for crate to be implemented on this ORM. But for now those were the only workarounds that I've found so crate would work.
Feel free to discuss anything.
The crate that I'm talking about is https://crate.io/
Signed-off-by: André Martins<EMAIL_ADDRESS>

Hey @aanm,
Thanks for this, I hadn't seen crate before.  It looks interesting!
And.. how about some unit-test integration for crate (like is available for all the other supported backends)?

@jaytaylor Are you talking about this https://github.com/jinzhu/gorm/blob/master/main_test.go

@aanm yep, that kind of stuff is what I'm referring to.

@jaytaylor Sorry, it turns out we are not going to pursuing this since it is not exactly what we need. You can close this PR or leave it open if anyone want to continue want it is missing.

@aanm thanks for following up!  I am curious about what you guys are pursuing instead, can you share?

I am going to close this one, seems like I am not a big fan of this database.
I  will open an API in the future, so you could implement dialects for other databases w/o modify gorm's source code.


Unable to install latest or second latest version

Short description of the problem:
Unable to install ionic
What behavior are you expecting?
Steps to reproduce:

npm install -g ionic

kissme:~ enri$ npm install -g ionic
(node:77231) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "ionic"
npm ERR! node v6.9.3
npm ERR! npm  v3.10.10

npm ERR! Invalid name: "@ionic/cli-utils"
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/enri/npm-debug.log

Post the output of ionic info below please
None
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)

Fixed by updating npm, sorry about it


Readme says to use nonexistent retdec-decompiler.exe ?

In the Windows section of the README it says:

To decompile a binary file named test.exe, run
$RETDEC_INSTALL_DIR\bin\retdec-decompiler.exe test.exe

However, after unpacking retdec-v4.0-windows-64b.7z I don't find a retdec-decompiler.exe. There is however retdec-decompiler.py.
I don't know if this is a README typo or an actual issue with the release?

This has to do with 2 things:

how we use GitHub (or how GitHub is in general)

that we didn't do a proper release for a long time.

You are probably looking at this README which is from the actual master. If you were to build master, there would indeed be retdec-decompiler.exe and no retdec-decompiler.py. If you downloaded v4.0 you should either be looking at the README in the package you downloaded (if it even contains a README), or this README associated with the tag v4.0. Both should hopefully correspond to what you see in the package itself.

We really ought to do another release. So much has changed from the v4.0 and I would not recommend using it at this point. I would recommend using the current master which you can get here. In fact, we plan to switch to kinda a rolling release from these master builds instead of the [not at all] regular releases like v4.0 was.

Thank you for the explanation!


Adding mouseover event to legend

Based on this post I've been able to add the event, but it's not triggered. Any idea why?
$scope.$watch('vm.chartLegend', function(){
  console.log(vm.chart);
  Chart.helpers.each(vm.chart.legend.legendItems, function(legendNode, index) {
     Chart.helpers.addEvent(legendNode, 'mouseover', function() {
       console.log('event triggered!');
      });
    });
 });

Using angularjs and chartjs 2.1.6

@Zeioth this won't work because the legend is drawn on the canvas. The legendItems objects are internal objects and not DOM nodes.
In this case, you probably want to hide the on canvas legend with
options: {
  legend: {
    display: false
  }
}

and use an HTML legend created from chartInstance.generateLegend().

Thank you for your answer! I'm going to open a ticket requesting native support for this event, since it's a pretty common interaction.


docs: Adding Define your CI/CD pipeline with Argo Workflows blog post

Motivation
Recently featured on CNCF East Asia Twitter & LinkedIn page:
Social Media Post: CNCF
This shows users a way to use Argo Workflows as a CI tool for their Internal Developer Platforms & pipelines, you can achieve this goal without having to do anything complex like setting up a Runner (which competitors like Gitlab & Jenkins require), By the way this concept allowed us to deliver at scale & was mentioned by Argo Project maintainers from Intuit during Kubecon 2022.

Fixes #TODO
Motivation

Modifications

Verification

@terrytangyuan is this pr ready? Seems like the build has now passed


why there is no field "fee" in method: "methods.balances.transfer"

when I test the ./examples/polkadot.ts, I find no place to fill the transfer fee. Does substrate calc fee self? Can we calc the fee when structuring the transaction?

Fee calculation is depends on some variables that change a little bit block to block. You can get a good estimate of the fee by dry running the transaction, which also gives some other info about the side effecst of the transaction. You can use the raw rpc call, or you could also use the Sidecar endpoint: https://github.com/paritytech/substrate-api-sidecar/blob/5936a1c9907d0a2add8c3265121a8f66d20a62f2/src/controllers/transaction/TransactionDryRunController.ts#L9). You can also use the fee estimate rpc call queryInfo, which gives a less detailed estimate of just the fee (there is also a Sidecar endpoint for this: https://github.com/paritytech/substrate-api-sidecar/blob/5936a1c9907d0a2add8c3265121a8f66d20a62f2/src/controllers/transaction/TransactionFeeEstimateController.ts#L8
To get the exact fee you need to replicate runtime logic off chain. Sidecar uses a rust crate to do fee calculations and will give you the fees of transactions included in blocks. See here: https://github.com/paritytech/substrate-api-sidecar/blob/5936a1c9907d0a2add8c3265121a8f66d20a62f2/src/controllers/blocks/BlocksController.ts#L50


UnicodeDecodeError in Python2

I would like to first thank you for the library :)
I ran into a little trouble while trying to use it with Python2. This happens when it is attempted to convert the entire data to be parsed as ascii. However in my humble opinion, I think the content to be converted need not be converted to ascii as any torrent file will obviously contain non-printable ascii characters, resulting in UnicodeDecodeError.
Python 2.7.11 (default, Mar 31 2016, 06:18:34)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import bencoder
>>> data = open("../archlinux-2016.06.01-dual.iso.torrent","rb").read()
>>> bencoder.decode(data)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "bencoder.py", line 90, in decode
    s = s.encode("ascii")
UnicodeDecodeError: 'ascii' codec can't decode byte 0xbe in position 267: ordinal not in range(128)

Removing this particular block of code, which attempts the ascii conversion, seems to make it work flawlessly in Python2.
 89     if isinstance(s, str):
 90         s = s.encode("ascii")

Attached the torrent file, I was attempting to decode.
archlinux-2016.06.01-dual.iso.torrent.zip

Should be UTF-8 I guess. But the project needs some tests IMO.


Document state of Python 2.7 support

Situation
At the moment, this project uses and supports Python 2.7. As we all know, Python 2.7 is going out of maintenance soon ("retire") and it's not clear what the project is going to do.
After disussing #160, we found out that the project doesn't have a clear statement or information regarding the retirement of Python 2.7 (neither in issues, README, nor documentation). Maybe I have missed something; in that case we can close this issue. :wink:
We are currently lacking answers of the following questions:

For how long do we want to support Python 2.7?
Which semver version(s) still support Python 2.7?
Do we want to have semver 3.x.y which supports only Python 3.x?

Suggested Solution
Whatever the project decides, we need to document it. :wink: What about the following approach?

Add a short note, paragraph, section etc. about the retirement of Python 2.7 inside our README. Maybe even link to this issue.
Focus in our documentation on Python3 only.

Apart from the documentation issues, I would also propose to indicate such a change with raising the major version of semver. For example:

2.x: would still contain the support for Python 2.7
3.x: would be the main line without support for Python 2.7 (in other words, >= Python 3.5 only)

Luckily, such major versions match with the Python version. :wink:
Would that help?
See also

https://pythonclock.org/
https://www.python.org/dev/peps/pep-0373/

My opinion (my 2cts)
We will release in the next coming days / weeks a 2.9.x version of python-semver which will support Python 2.7 and 3.x
After this, we will be working on a 3.x version of python-semver which will only support Python 3.x
I won't personally backport python-semver 3.x features to 2.x branch to urge people to leave this venerable Python 2.7 version (in life everything stops one day :wink: )
Releasing is time consuming... releasing 2 versions can be more than 2 times consuming.

I fully agree - I think we should only fix bugs in 2.x branch.
Another question - what about Python 3.4? It's marked as EOL and maybe we should remove support for that version as well in 3.x?

Another question - what about Python 3.4?

I was thinking the same. Maybe we can mark this version also as unsupported in our upcoming 3.x branch?

Agree no Python 3.4 in python-semver 3.x but Python 2.7, 3.4 in python-semver 2.9.x

Ok, great! So to summarize the needed actions:

[ ] Add the current document state/idea into the README
[ ] Create a 2.9.x release
[ ] Open a maint/2.9.x(?) maintenance release branch.
This would be only for interested people, no backporting will happen
[ ] Create a 3.x release with the subtasks:

[ ] Remove test target  py27
[ ] If needed, remove/refactor code that was introduced only for Python 2.7
[ ] If needed, "optimize" code for Python3
[ ] Focus on Python3 in the documentation

Anything else?

I'd suggest to make our user base aware of such an incompatible change and add a warning notice in our README file:
.. warning::

   Major version 3.0.0 of semver will remove support for Python 2.7 and 3.4.

   As anything comes to an end, this project will focus on Python 3.x. New
   features and bugfixes will be integrated only into the 3.x.y line of semver.

   The last version of semver which supports Python 2.7 and 3.4 will be
   2.9.x. However, keep in mind, version 2.9.x is frozen: no new
   features nor backports will be integrated.

   We recommend to upgrade your workflow to Python 3.x to gain support,
   bugfixes, and new features.

LGTM

@scls19fr
Thanks for merging it, :+1:  but it's only one part of it. I've mentioned other items in my https://github.com/k-bx/python-semver/issues/161#issuecomment-539045512.
Should we transfer the other, unresolved items into a new issue or is it better to reopen this issue?

Ok so let's reopen and adress remaining items.

The comment https://github.com/k-bx/python-semver/issues/161#issuecomment-539045512
that mentions Python 3/semver 3.0.0 is covered in a separate issue #176 now.

I'm confused by the statement in the Readme that seems to say 2.10.0 does still support Python 2.7. That's not what I'm seeing. I have a project that uses this package and runs in Py2, and as soon as it started using the 2.10 release, I started getting errors like this which look to me like what you'd get from a Py2 vs. Py3 incompatibility:
TypeError("Expected str or VersionInfo instance, but got <type 'unicode'>"
When I pin the dependency to <2.10, the error goes away.

@eli-darkly Thanks Eli! :+1: Much appreciate your bug report. I've opened #274.
If I'm not mistaken, I assume this is of some if isinstance(other, str) lines which didn't recognize the unicode datatype in Python2.

I've opened a maintenance branch maint/v2 if we need that for the semver v2 line.
I think, all tasks are done so I'm closing this issue for the time being.


Design: Ontology treatment and Ontology regimen connection within the database

Description
As a developer, I want to have a correct relationship between ontology treatment and regimen in the database for search purposes.
Acceptance criteria

[ ] designed

done, closing


Replicate geth node

We will need to replicate our sidechain to at least one or two additional nodes when on mainnet.
And we probably must do this before launching.

Here is the relevant geth issue issue: https://github.com/ethereum/go-ethereum/issues/20383
Because we do not have large traffic on this node, we can be quite a few transactions behind on a system crash and in the worst case these would not be committed to disk. That is probably not acceptable, but would be fixed by having replica geth nodes.

It would also be good to split nodes on to separate servers, between the miner that progresses the chain (and requires a Proof of Stake signature) and the access point node that we connect to at ethereum.exokit.org. Mostly this would be for resilience reasons.

Done. We have two geth nodes now, with the miner separated from the API.


Typo in ID token expiry time in console app

Describe the issue:
Typo in ID token expiry time in console app

Id Token expiry time should be changed to ID Token expiry time
How to reproduce:

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

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


Focused

[x] A)
[x] B)
[x] C)

[x] Basic

ready for the new job and you|

Congratulations on your special day today I ✅|
``` 🗓

grid1


Support supplying a token on the command line when logging in

Works like this:
read -es SECTION_TOKEN
sectionctl login

Or less securely (because the secret is stored in shell history):
sectionctl login --section-token s3cr3t:t0k3n

Ideally we'd encourage token specification methods that don't persist in shell history, or expose them to casual observation of the process tree.
Perhaps a --token-from-stdin option? Spitballing:
read -es TOKEN
printf %s "$TOKEN" | sectionctl login --token-from-stdin

I'm sure there are cleaner methods and suitable PowerShell alternatives.
You'll note that all the cloud container registry integrations with docker stopped passing creds via CLI args and switched to more secure methods.

Ideally we'd encourage token specification methods that don't persist in shell history, or expose them to casual observation of the process tree.
Perhaps a --token-from-stdin option? Spitballing:
read -es TOKEN
printf %s "$TOKEN" | sectionctl login --token-from-stdin

I'm sure there are cleaner methods and suitable PowerShell alternatives.
You'll note that all the cloud container registry integrations with docker stopped passing creds via CLI args and switched to more secure methods.

Fun fact: this PR already indirectly supports that, by setting the SECTION_TOKEN environment variable:
read -es SECTION_TOKEN
sectionctl login

Fun fact: this PR already indirectly supports that, by setting the SECTION_TOKEN environment variable:
read -es SECTION_TOKEN
sectionctl login

Fun fact: this PR already indirectly supports that, by setting the SECTION_TOKEN environment variable

IIRC, environment variables are also casually observable via cat /proc/$(pidof sectionctl)/environ but I'm not going to die on this particular hill. 🚶

Fun fact: this PR already indirectly supports that, by setting the SECTION_TOKEN environment variable

IIRC, environment variables are also casually observable via cat /proc/$(pidof sectionctl)/environ but I'm not going to die on this particular hill. 🚶


GET /statuses/home_timeline

Adjustments for the home_timeline endpoint. Authenticating user determined by props file.

Looks good. I'm going to tweak this code slightly because the documentation says that the maximum number of tweets you can get from this endpoint is 800. So, the code that loops to get 3200 tweets doesn't apply in this situation. I'll commit my changes so you can see what I did to clean this up. Thanks!


Release 1.1.2

This PR does the release of the library version 1.1.2.
Also it cleans up the remaining SLF4J dependencies.
The SLF4J binding is still present in the firebase-web project as it's required by the Firebase Admin SDK.
The SLF4J dependency was made local for the web, so any trace of SLF4J can be safely removed from config after the 1.1.2 release is done for all libraries.

@armiol PTAL.


Enable/disable with jQuery

Hi, thanks for the plugin, it's really great.
I was wondering if you can tell me how to enable and disable with jquery? I want to disable on smaller screen size (mobile).
$('.sticky-element').sticksy({
    topSpacing: 20,
    listen: true
});

Thanks

I modified the existing jQuery demo to show enabling/disabling the plugin with jQuery (It's basically the same as with normal JS)
Demo
If you need to do it with a media query, you may need to use matchMedia


update poetry to point to kubernetes 29.0.0 - 1895

[Auto generated]
Number: [#1895]

openshift-python-wrapper(99656650-3eca-11ef-89df-a6f7326ca14b)[PR 1895]: Closing issue for PR: update poetry to point to kubernetes 29.0.0.
PR was closed.


DNN-9776: do not show the user skin objects in custom error page.

ShowInErrorPage is added for backward compatible, so if customer really want to show those controls in custom error page, they have way to do it.


System.Int64 has a reference to 32-bit that should probably be 64-bit

Describe the issue or suggestion
System.Int64 has a reference to 32-bit that looks like it got overlooked when all that extra documentation was added.
Also, a commentary on terminology for clarity:
I think it would be best to avoid using the word decimal in those articles, in particular, when talking about base-10 numbers, as it could potentially be confused with the decimal type, discussed in the same section of the documentation.
Originally posted by @dodexahedron in https://github.com/dotnet/docs/issues/24287#issuecomment-2062872072

Also, both the Int32 and Int64 articles mention the unsigned variants. Would it be worthwhile to add a footnote or parenthetical callout or something to briefly mention that UInt32 and UInt64 are not CLS-compliant?

Another thought:
Binary, octal, and hex literals can get confusing when using the signed types, as it is considered an overflow to set the MSB explicitly without an unchecked expression and a cast. To me, that's a language bug, but I don't imagine that's something likely to be changed, due to breakage potential.
In any case, mentioning this restriction when talking about Int(32|64) literals in bases != 10 seems a lot better than just saying that it's a (31|63)-bit number with a sign bit. That doesn't help much when someone is writing a [Flags] enum, for example, and runs into the apparently common small but inconvenient stumbling block of something like this being illegal:
[Flags]
public enum Broken
{
  None = 0b_00000000_00000000_00000000_00000000,
  Bit0 = 0b_00000000_00000000_00000000_00000001,
  // ... And so on up to...
  Bit31 = 0b_10000000_00000000_00000000_00000000 // <--- Compile error claiming it's an Int64
}

That can be resolved by:

Using the negative base-10 representation (ugly and unintuitive)
Wrapping the literal like so: unchecked((int)0b_10000000_00000000_00000000_00000000) (ugly - messes up alignment but at least keeps binary representation)
Changing the enum to an unsigned or larger type (breaking change plus not CLS-compliant if unsigned)

@tannergooding could you PTAL?

System.Int64 has a reference to 32-bit that

Please feel free to open a PR fixing it.

I think it would be best to avoid using the word decimal in those articles, in particular, when talking about base-10 numbers, as it could potentially be confused with the decimal type, discussed in the same section of the documentation.

decimal is a common term that will exist as the natural wording across a wide range of docs. It would be far more effort than it's worth to try and ensure every doc doesn't use it and likely overall more confusing to avoid it. This is particularly prevalent when the terminology is almost always clarrified by the surrounding context, such as decimal digits and examples.

Would it be worthwhile to add a footnote or parenthetical callout or something to briefly mention that UInt32 and UInt64 are not CLS-compliant?

IMO, no. CLS Compliance exists very broadly and is exposed to users when they go read the docs for a type or member that is marked with it.
 A number of modern features have never been considered for CLS Compliance and would likely have been considered non-compliant given the original spirit of the feature. This includes things like ref structs (and therefore Span<T>), default interface members, static virtuals in interfaces, and most other new runtime functionality. There are also places where the language doesn't "properly" raise that something should be marked CLSCompliant(false), such as any of the places where it emits a modreq for a virtual member.

To me, that's a language bug, but I don't imagine that's something likely to be changed, due to breakage potential.

This is how most languages work, the representation doesn't matter only the resulting magnitude which is always interpreted as unsigned. You then only get a negative value by using the negation operator on a literal, thus 0b_10000000_00000000_00000000_00000000 is 0x8000_0000 which is<PHONE_NUMBER> and thus is outside the range of int. Negative 1 is then represented as -0b1 or -0x1 or -1, not as 0xFFFF_FFFF.
Some languages, like C, allow all kinds of implicit conversion without warning and so it "appears" to work, but in practice its just silently allowing overflow to happen (which is also strictly undefined behavior according to the language spec).

Thanks for the responses and background.
As far as the decimal term goes, I specifically meant for these documents, within that section - not as a global change - due to the proximity of the concepts. The decimal type document comes before the integer documents in that section, too.


Add authentication

https://fastapi.tiangolo.com/tutorial/security/first-steps/

Could also look at https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user  for inspiration - GitHub Apps are also just services run on our own hardware that do things on GitHub ...


Nick: Watch Honest[\W_]+Hair[\W_]+Factory(?!.com(?<=honesthairfactory.com))

Nick requests the watch of the watch_keyword Honest[\W_]*+Hair[\W_]*+Factory(?!\.com(?<=honesthairfactory\.com)). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Honest[\W_]*+Hair[\W_]*+Factory(?!\.com(?<=honesthairfactory\.com)) has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cocomac in Charcoal HQ