warn("Using a coordinate with ws.cell is deprecated. Use ws[coordinate] instead")

/venv/lib/python3.4/site-packages/openpyxl/worksheet/worksheet.py:303: UserWarning: Using a coordinate with ws.cell is deprecated. Use ws[coordinate] instead
warn("Using a coordinate with ws.cell is deprecated. Use ws[coordinate] instead")
Can't export.

I have confirmed this warning. The problem about being unable to export was not reproducible. I could see exported files with content. How do you run the command (please give parameters)?
This warning comes from how the tablib lib uses another library: https://github.com/kennethreitz/tablib/issues/298
I'm a bit doubtful about upgrading my dependencies (if tablib releases a fixed version) as this only seems to be a deprecation warning.

I'm also getting this error
tablib=12.1
openpyxl=2.4.9
python 3.5
yahoo-ticker-downloader=2.4.1
python.exe YahooTickerDownloader.py stocks -E AX -m au
running from command line inside fresh virtual env

@DaneEdwards , Can you confirm it terminates right away? If so can you provide a full console log?


go/types, types2: broken invariants with respect to generic receiver types

Our handling of receiver type on generic methods in go/types and types2 is confusing, and arguably incorrect.
While type checking method declarations, the type checker checks the receiver expression T[P1,...PN], resulting in a receiver type that is instantiated with its receiver type parameters, and then assigns this receiver type to the signature being type-checker. This has two surprising consequences:

The receiver type of methods on a generic type is not itself generic: it is instantiated with receiver type parameters.
Because the receiver type is treated as an instance, it is recorded in the Info.Instances map, and its methods are subsequently re-substituted. This means that the defined method F (the thing in Info.Defs!) is not contained in the method set of F.Type().(*types.Signature).Recv().Type()!

Of these, I think (1) is a perhaps peculiar choice that we must stick with, and (2) is a bug -- a consequence of our choice to treat the receiver as an instance and a later decision to instantiate methods on instances.  I think this is probably not that difficult to fix: we should avoid naively type checking the receiver parameter list. It is certainly a release blocker to decide what to do here.
@griesemer, do you agree?
CC @timothy-king, who encountered this while working on go/ssa.

Per virtual in-person discussion, I agree that we need to address this. The receiver type handling is a historical accident: before generics, the most expedient way to type-check a method signature was to treat the receiver parameter list just like any other parameter list.
This didn't work anymore for parameterized method receiver types because they look like an instantiated type - yet they are really declaring their own type parameters. Rather than completely changing the original code, I added some pre-amble to extract and declare those type parameters beforehand, so that the receiver type could be type-checked as an instantiated type (and the rest of the code didn't need to change). That code was pretty simple originally, but over time has become more and more complex, with unintended side effects (like what we're observing now). In retrospect, it would have been better to treat receiver parameter lists specially from the start (at least if they have a generic receiver).


Versioning: tagging does not create new helm chart

tagging does not create new helm chart

Done in https://github.com/HIRO-MicroDataCenters-BV/rhio/pull/106


Make a tag/release for PyHEP 2022 "proceedings"

Hello @masonproffitt, can you kindly prepare the tag/release so that I then use it to mint a DOI on Zenodo and attach it to the workshop "proceedings" https://zenodo.org/communities/pyhep2022? Advance thanks.

Sure, I've created a release now: https://github.com/masonproffitt/pyhep-2022-abcd-pyhf/releases/tag/v1


[Accessibility]A11y_VSCode_ViewExtensions_Keyboard:Keyboard focus is lost after Installed toolbar.

Environment Details:
VSCode Version : 1.24.1
OS Version : WIN10
Additional Details:
Keyboard,MAS2.4.3,ScreenReader-MAS1.3.1,MACOS High Sierra 10.13.5 Beta (17F70a)
Repro Steps:

Launch VS Code.
Navigate to View(Alt+V) menu option and select "Extensions" from dropdown.
Navigate to Installed Toolbar.
Check the keyboard navigation.

Actual:
Keyboard focus is lost after the Installed Toolbar and NVDA also reads as extension treeview which not showing on the screen.
Same issue observed in MAC also.
Expected:
Focus should go to Recommended toolbar after the Installed Toolbar.
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
User unable to know where is the focus.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={0de7fbe1-ad7e-48e5-bcbb-8d986691e2b9}
Does this issue occur when all extensions are disabled?: Yes
Attachment For Reference
[Accessibility]A11y_VSCode_ViewExtension_Keyboard1.pptx
[Accessibility]A11y_VSCode_ViewExtension_NVDA.pptx

Dup of https://github.com/Microsoft/vscode/issues/52596


Re-implement map_over_datasets

The main changes:

It is implemented using zip_subtrees, which means it should properly
handle DataTrees where the nodes are defined in a different order.
For simplicity, I removed handling of **kwargs, in order to preserve
some flexibility for adding keyword arugments.
I removed automatic skipping of empty nodes, because there are almost
assuredly cases where that would make sense. This could be restored
with a option keyword arugment.

I wonder if we should also change map_over_datasets from being called like map_over_datasets(func)(*args) to map_over_datasets(func, *args), which would be more consistent with apply_ufunc.

I removed automatic skipping of empty nodes, because there are almost
assuredly cases where that would make sense. This could be restored
with a option keyword arugment.

I will look at this in more detail in a bit, but there are definitely issues on the original datatree repo caused by not skipping empty nodes.


feat: add _trustedboot and _ephemeral features

_trustedboot provides the core trustedboot functionality; it requires an additional feature to provide handling of mutable data
_ephemeral provides the default implementation of this, it is implemented in a seperate feature to allow overriding with alternatives (using feature excludes)

Please add some README.md to the features. Take a look at kvm

that's part of #2344 since it is a combined doc for both trustedboot and tpm, so would make no sense to have this here already


Errors when importing dae model

Godot version:
3.1 b17e71b
OS/device including version:
Windows 10
Issue description:
When I try to import dae model(only this one attached to minimal project), then a hundreds of error  is shown:

ERROR: get_quat: Condition ' !is_rotation() ' is true. returned: Quat()
At: core/math/matrix3.cpp:603
ERROR: orthonormalize: Condition ' determinant() == 0 ' is true.
At: core/math/matrix3.cpp:80

Minimal reproduction project:
AA.zip

I'm looking into this issue, right now.
I reproduced the issue and I reviewed the COLLADA document.
The document contains animations where the animation output are transforms where the upper-left triangle is all zeroes (id-anim-65, id-anim-66, id-anim-67....)
...
I think that having a transform where the scale is zero is valid, if uncommon. But it does mean that there is no rotation information to extract from the transform. So, I propose detecting the zero scale vector during the COLLADA animation import and not extracting an orientation quaternion from the transform - to avoid spamming the user.


External import statements in swiftinterface doesn't respect -fmodule-map-file compiler option

Describe the bug
I came across a compiler issue for .swiftinterface with external import dependencies. The dependency is an Objective-C module with custom modulemap. Typically, we can use the -fmodule-map-file compiler option to specify custom modulemap. This is also heavily used in CocoaPods. However, .swiftinterface module resolution seems not support this option.
Steps To Reproduce
To demonstrate the issue, I have a minimal reproducible example at https://github.com/Kudo/Swift-Module-Issue . Although it's getting little complicated, if there's anything unclear, please let me know. Thanks!
Expected behavior
the case App -> ModuleContainer (swiftinterface) -> ModuleB in the repro should not have build errors.
Screenshots
screenshot from the repro

Environment (please fill out the following information)

OS: macOS 12.6
Xcode Version/Tag/Branch: Xcode 14.0.1 (14A400)
Apple Swift version 5.7 (swiftlang-<IP_ADDRESS>.4 clang-14<IP_ADDRESS>)

Additional context
same as https://github.com/apple/swift/issues/58268 but tested on xcode 14. it is still broken.

@Kudo Did you fix it by any chance?

@maciejburda no, i don't know much for swift compiler internally and have no context for the fix.


How do i make menubg not change its color to pink on main menu?

What is your question?
im making a fnf mod. and i dont like. how the menubg changes it color to pink. is there anyway to make it stay yellow?

if your on source code you can remove this line I think

if your on mods folder then ig just make the image as the same as the yellow one

thanks


Add MacClean.app latest version

Start Daily Clean-Up on Your Mac from One Simple, Quick & Free Click http://www.imobie.com/macclean/

Looks good, thanks! :+1:


Recent empty state needs padding

"You have not listened to anything so far"
https://github.com/vpaliyX/Flash-MusicPlayer/blob/1b45bae1e081fe26cf37778f45771e134ff71a3b/app/src/main/res/layout/fragment_home.xml#L18

I have added left/right margins to this.


Functions always undefined

NO matter how many times I describe a function it always comes up undefined when i hit 'learn test'. What should I do?
And it's not letting me attach files.

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Remove inexistent rule

This rule definitely exists: https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-space-before-closing.md
Try updating the version of eslint-plugin-react that you're using.


6.2.x

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

I think this PR has been opened by mistake


CUDA 7.0

We should think about moving to CUDA7 soon. It has powerful features like streams support for Thrust, NVRTC (see @szagoruyko 's on the fly apply kernels, pretty powerful).
@clementfarabet @dominikgrewe what are your timelines to upgrade to CUDA7 internally? (It is fully backward-compatible with 6.5/5.5 afaik)

We're planning to upgrade to CUDA 7 soon.

In relation to my feature request in torch7, it would be useful to implement a "CudaHalfTensor" with the upcoming CUDA 7.5, with or without a "HalfTensor" in the main library.


iOS 12 compatibility error

Just upgraded to Xcode 10.0 and get the following error:
dyld: Symbol not found: __T0BOWV
Referenced from: /private/var/containers/Bundle/Application/FE262A78-23EA-4235-87EF-6FBDE57A7457/LinkReactNative.app/Frameworks/FileBrowser.framework/FileBrowser
Expected in: /private/var/containers/Bundle/Application/FE262A78-23EA-4235-87EF-6FBDE57A7457/LinkReactNative.app/Frameworks/libswiftCore.dylib
in /private/var/containers/Bundle/Application/FE262A78-23EA-4235-87EF-6FBDE57A7457/LinkReactNative.app/Frameworks/FileBrowser.framework/FileBrowser

Thanks @stevencurtis for raising the issue.
I have tested the same on my xcode 10 and it is working as expected. Can you please try the library sample example and verify it once. Please let me know in case you still face the same issue.
Thanks
</ Pranav >


Worked on main todo list page app-index.hbs

Not done yet just a start They all work tho just needa finish the stylin yk

and add a feature where the person can create multiple lists instead of just having 3 as default


proposals: add processing metrics for major steps

Motivation
add information about time spent on proposal processing

bors merge

bors merge

bors merge


magrittr-like syntax

See #15

As a side note, I'm finding it irksome that my code for @as_first and @as_last is identical except for one line. Is there a more elegant way to do it in Julia that avoids duplicated code?

See ChainMap.jl for this functionality.


[Features] Docker Registry

Dear Rancher Team,
here some enhancements that we would appreciate to see concerning the integration of custom docker registries:

Nice to have:  Ability to define cross-projects registries to avoid having to maintain the same information several times ;
Nice to have: Displaying  password when entering credentials ;
Mandatory:  Including the following statement automatically within the yaml file when deploying an image as already stated by other people in other messages.

imagePullSecrets:
  - name: <my registry>

Sincerly,
Ludovic

Useful
Info

Versions
Rancher v2.1.1 UI: v2.1.4

Route
authenticated.project.registries.index

Dup: https://github.com/rancher/rancher/issues/1738

Closing in favor of 1738


FOUC on initial load

For a dark themed site, I have a minimal setup for a theme config and adding background to body
Problem
I see flash of unstyled content on body, starting white and then dark.
Deployed example
https://stiches.vercel.app/
Repo
https://github.com/emadabdulrahim/stitches-example
Should I be doing things differently?

Hey @emadabdulrahim 👋
Thanks for submitting this issue. I would love to have a look but unfortunately, the repo link you provided seems to be broken.
but yeah I think this is a known issue that we also have on our official stitches website so we're definitely aiming to fix it

@hadihallak The repo link should work now.
Thanks for taking a look

I dont think this is specific to Stitches. It happens on SSR websites with dark mode, where dark mode is not the default theme.
Some more information:

https://brianlovin.com/overthought/adding-dark-mode-with-next-js
https://blog.maximeheckel.com/posts/switching-off-the-lights-part-2-fixing-dark-mode-flashing-on-servered-rendered-website

I need to fix this on here too https://github.com/modulz/stitches-site/issues/17 😄

I'll close this issue, and you can follow https://github.com/modulz/stitches-site/issues/17 instead for the fix

So it seems that this may be a legit bug. We need to validate it.
The theory right now is that the theme CSS is not injected at the right time.
More info in the issues on the stitches-site repo

@biowaffeln maybe you can provide more information

Hey, sorry for the late response!
I did some investigations of the bug a while ago, and the problem seems to be the following:

using the noflash.js script, a class name is applied to the body of the document before any Next.js code is executed. This seems to be working fine, i.e. the body has the dark theme class name applied to it.
Then, the css variables are injected as part of the toString method on the theme object, see here.
In a production build, however, the code for inserting the variables is only executed after the inital render, thus causing the flash of light mode. Here is a link to a little demo demonstrating the effect.
I think that one solution could be to generate the theme styles as part of the styles returned from the getStyles method here, so that it would get injected during the setup of _document.tsx. I tried debugging it, but unfortunately not very familiar with that part of the codebase. Perhaps @hadihallak @christianalfoni you guys want to take a look at it?

Closing this in favour of https://github.com/modulz/stitches/issues/279
Thanks @biowaffeln that was super helpful 👍


Update README.md

Minor fixes, mostly capitalization fixes.
Also changed URLs linking within the repo to be relative links.
KonduitServerMain changed to KonduitServingMain due to dead link, I'm not sure if this is correct.

+1 LGTM


Added colcon ignore file to remove errors when sourcing workspace.

The oxts tests aren't true ROS packages it seems so they generate errors when built in a workspace and try to source it. I'm not sure what needs to be done to avoid the errors but figured that we don't need them in our fork at all times, so I added a COLCON_IGNORE file. You can still remove the file manually if you still want to build and run the tests.

Alright


[Feature] Users and guest accounts

A user management system needs to be introduced to safely enable remote connections. Remote connections must have a valid login. There will be two user levels: owner and guest. The owner has access to movie/episode patching to mutate the .nfo states for progress and watched tracking. Guests do not have these privileges. There is no tracking whatsoever for guest users.

Consider introducing a mechanism to track watch progress for guest users. This could be a custom XML element in the .nfo:
<ulmas>
  <trackingNameOfPerson1>
    <watched>true</watched>
  </trackingNameOfPerson1>
  <trackingNameOfPerson2>
    <resume>
      <position>1200</position>
      <total>1931</total>
    </resume>
  </trackingNameOfPerson1>
</ulmas>

This relies on a unique, non-changeable trackingName in a User object. Intentionally detach this from a userName so login names can be changed, but tracking remains intact for the user. This change would introduce elements into the .nfo that aren't easily migrated to other applications. So, the main user should not use this custom element at all. This only applies to guests.
Finally, the primed cache can then be split into separate files, e.g.:
series.anime-series.tZt-tzH6hrHEC-QbRiSXuXyjE6g.json
series.anime-series.tZt-tzH6hrHEC-QbRiSXuXyjE6g.main.json
series.anime-series.tZt-tzH6hrHEC-QbRiSXuXyjE6g.trackingNameOfPerson1.json
series.anime-series.tZt-tzH6hrHEC-QbRiSXuXyjE6g.trackingNameOfPerson2.json

If a user then needs his data, two requests are fired: one for the series/movie/list data, and one for personal tracking.
I'm still considering whether to give guests tracking at all. Thoughts and feedback are most welcome.


Please just add the refreshToken to the acquireTokenByCode api

Core Library
MSAL Node (@azure/msal-node)
Wrapper Library
Not Applicable
Public or Confidential Client?
Confidential
Description
I have code such as this:
const { idToken, idTokenClaims, accessToken, expiresOn } = await app.acquireTokenByCode({
  code,
  scopes: DEFAULT_SCOPE,
  redirectUri,
})

But I need it to return the refreshToken as well. I know you're getting it and intentionally omitting it but its really frustrating and I just need to get the refresh token.
I've looked at a lot of your samples for the caching and I have to say after reviewing it and using this library for multiple years now I just don't think it makes any sense at all the way you're doing it. All of your examples and even your wrapper library @azure/msal-node-extensions are attempting to do caching of the refresh tokens to disk and even if I were to build my own cache plugin its expecting me to be caching all of these refresh tokens in a database and I have to say it just doesn't make any sense to me.
For one thing, caching anything to a servers disk is a huge error. Nothing should be caching into a servers disk, my servers don't even have writiable disks at all so none of that makes any sense. Also I have more than one server, what good is caching to disk going to do? So why you all even have these disk cache examples is beyond me.
Secondly, caching to a database similarly makes no sense to me. I'll have to give the user an id of the cached entry no? I don't think its safe to use anything off of an expired token so that means they'll need a secret... and at that point I'm wondering why I didn't just give them a dang refreshToken, now they need a token to get the refresh token.
You know whats easy? Just giving the user the refresh token and having them cache it however they want. Super easy. No database calls, no complexity, no caching.
I'm looking here and it says:

Note that MSAL does not expose refresh tokens by default and developers are not expected to build logic around them, as MSAL handles the token refreshing process itself.

I think its fine if you want to support that but its really frustrating that not only do you not expose it by default but you're omitting it entirely and not exposing it at all. I've been struggling with this for a while and I can't tell you how much better it would be if you would please just return the refreshToken along with all the other tokens in this function.
I really can't stress enough how much better this library would be if it would alter this opinion and stop doing all the caching at this layer. I really think if you want to have some fancy no-refresh caching system then make a new library which focuses on that but please just don't consume and hide the refresh token.
Maybe I'm just missing some massive piece of the vision here? I'm open to having it explained to me like a 5 year old but the above is just not cutting it for me. You say what you're doing but not why and I'm really skeptical that you're correct.
These examples by the way do not instill a lot of confidence, the code looks like it was written by an intern with no prior knowledge of javascript or nodejs. A couple of critiques:

You're using req.session in this example. Try to write an example which doesn't not utilize the session at all, make it completely stateless.
Assume you will have two (or more) servers. Do not utilize the memory or disk for caching.
Use typescript.
In the msalCachePlugin.js file, use the export and class keywords. Use async file system apis.
Your cache plugin api seems to serialize the entire cache to the same file every time. What if you have multiple users? What if you have millions of users? Do I have a different app and different cache for every single user? This example does not show how during the cache persistence step it should be able to tell which user its being serialized for?
What if multiple requests for the same user are happening in parallel on different machines? If the whole cache is just being serialized and persisted on each request then how is that race condition being resolved?

Source
External (Customer)

Adding @bgavrilMS @sameerag @EmLauber for feedback on acquireTokenbyCode and refresh tokens.

@justinmchase thanks you very much for the detailed feedback. I think we have caused a misunderstanding with our use of the word "disk" -this was meant to be "non-in-memory" cache, any medium to save the cache other than the memory, e.g. a database or a redis cache. We certainly did not mean the actual disk for the server side apps. Apologies for the confusion, I'll look into revising wording in cache docs.
On a more general note, samples under this repo are primarily meant to showcase msal APIs in action for automated and manual testing, and none of them deals with server side issues like scaling unless explicitly mentioned (neither they showcase the larger IAM best practices, but that's another matter). To help with the scaling issues, we've put forward a few distributed caching samples recently. I'm curious about your take on them:

client-credentials-distributed-cache
on-behalf-of-distributed-cache
auth-code-distributed-cache (this one is in PR -would appreciate any reviews)

We have also updated the docs on caching recently (not sure if you came across them):

Caching
Performance

Regarding session usage. The session middleware used in the samples is storing the user session server-side, which you can opt-in to use together with a distributed session store. Could you help me understand why would that be an issue for scaling, and what a stateless approach would look like instead?

The other source of confusion is the use of the session and session id for persistence. I don't have a session at all and am intentionally not using the session. So I've tried to implement a MongoCachePlugin but there is no "id" available to use to save the state to. The id of the user is the logical id to use but the plugin doesn't give me the account information clearly in the cache plugin.
And again, I can't really state this emphatically enough, even with caching of the tokens enabled I still need the refresh token. I really wish you guys would please just start returning the refresh token along with the other tokens it would make my life so much simpler its not even funny. By all means people can also use the caching and ignore the refresh token if they want but if you do want it and can't get it... its brutal.
Also, sorry to be so rude in the original issue, I was getting frustrated. But I will say that a lot of these  samples would be greatly improved with TypeScript and some other code quality pass overs. I see some functions for example returning promises and using .then().catch() instead of using async/await and functions in places where classes should be used... It would help quite a bit to put in some effort to modernize some of the javascript in here.

Are you trying to integrate MSAL with Express?

Yes, exactly.
Based on some of this feedback I am altering my app to create a new ConfidentialClientApplication() on every request for now... though I really don't think this should be necessary it seems like it should be easily possible to use a single instance, I would definitely prefer to not construct throw away objects on every request if it can be avoided.

The cache key is essentially the user id.

But in that example it seems to be getting the userid from the session. I would be really interested in seeing a non-session based solution, I can't seem to figure it out.

@justinmchase sorry for the late response. the reason we are making use of sessions in the web app samples is twofold:

Before the token request takes place, you don't have any artifacts (e.g. ID token) to identify the user, so you don't have a way to do a cache lookup. So using a persistent server side session helps to identify the user to do a cache lookup before making the token request.
Token acquisition with msal-node is a 2 legged process, where you first make a request to the authorization endpoint, and then obtain the authorization code from its response to make a request to the token endpoint (after which AAD responds to your redirect Uri). Since the execution context is lost when a redirect happens, sessions are utilized to to keep some state about the user (for instance, which page to redirect the user after auth takes place).

With respect to (1), I think it should be possible to do hybrid flow to receive an ID token directly from the authorize endpoint, which would give you the user id to do the cache lookup before the access token request. For (2), I don't have anything on top of my mind -open to suggestions.
Let me try to put together a working example and share it here.

Ok I see, I'll probably try that.

Can anyone please tell me how to get a refresh token?
I instantiate MSAL instance with:
new msal.ConfidentialClientApplication(msal_config);

I log the response returned from:
const response = await confidential_client_application.acquireTokenByCode(
      token_request
    );

It returns an object that does not contain a refreshToken property.
I have read that this is 'by design' but there must be a solution.
There are so many posts on this topic throughout the internet, but I haven't found a solution.

Hi @oshihirii - MSAL manages the refresh token internally. Just call AcquireTokenSilent and MSAL will:

return any cached access token
if the cached access token exists but it is expired, it will use a cached refresh token to get a new access token and give it to you
if none exists, an UiRequiredError will be thrown

Ultimately, you don't have to agree with out SDK choice to hide refresh tokens from app developers. Entra ID is fully OIDC compliant and you can use any OIDC library to fetch tokens.

@bgavrilMS thank you very much for your reply.
These are the 3 MSAL Node methods I use in my app to return a token:
01) acquireTokenByCode()

req.session.int_idp_access_token_app_reg_B2C_SignIn
(INTERNAL users from an Azure AD tenant set as an IDP in Azure AD B2C, returned after signing in to B2C)

req.sesson.int_access_token_ad_signin_Internal_User
(INTERNAL users automatically signed into their own tenant, in order to get a token to be used for an OBO token request)

02) acquireTokenOnBehalfOf()

req.session.int_access_token_app_reg_InternalUser_M365_Access
(INTERNAL users given a token from an Azure App Registration that specifies permissions in their own tenant)

03) acquireTokenByClientCredential()

req.session.int_access_token_app_reg_Admin_M365_Access
(INTERNAL users given a token from an Azure App Registration that specifies elevated permissions in their own tenant)

req.session.ext_access_token_app_reg_ExternalUser_M365_Access
(EXTERNAL users given a token from an Azure App Registration that specifies limited permissions in the INTERNAL tenant)

I am currently in the middle of trying to implement a middleware function that checks if a token is about to expire.
If it is about to expire, I want to refresh all the user's tokens.
So I am hoping that acquireTokenSilent:
https://azuread.github.io/microsoft-authentication-library-for-js/ref/classes/_azure_msal_node.ClientApplication.html#acquireTokenSilent

Will be able to extend the expiry of access tokens that were originally created with those 3 methods:

acquireTokenByCode()
acquireTokenOnBehalfOf()
acquireTokenByClientCredential()

Works with Confidential Client Applications

Can handle the idp_access_token that is associated with the initial Azure AD B2C signin.

So I will try that now, fingers crossed.
Thanks again.


Clean up stale entries from upgradeSegments table

The upgradeSegments table contains entries of pending segments allocated by tasks with APPEND locks when there was a REPLACE lock held over the interval.
This PR aims to clean the entries from the metadata store after the task with the REPLACE lock completes.
The CleanMetadataAction can be extended to clean other entries in the metadata store such as stale pending segments.
This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

@kfaraz, thank you for the feedback.

Rolling Upgrade: A task running on an upgraded version would fire the new action but an old Overlord would not be able to recognize it.

Apologies, I had missed this.
Do you have a suggestion to make the TaskAction work during a rolling upgrade?
An alternative could be to invoke the cleanup from TaskLockbox directly when the task is removed from the set of active tasks instead of using a new task action.

An alternative could be to invoke the cleanup from TaskLockbox directly when the task is removed from the set of active tasks instead of using a new task action.

Is there any cleanup which is currently performed by the TaskLockbox?

Is there any cleanup which is currently performed by the TaskLockbox?

@AmatyaAvadhanula , let's keep it simple. Since the new task action is responsible only for cleanup of upgrade segments (something which doesn't happen in the current version anyway), let's just put the submission of the task action in a try catch. If it succeeds, cool. If the OL cannot identify the task action and throws an exception, we just log the exception saying that the OL is probably on an old version. This would ensure that the task itself doesn't fail if the OL is on an old version.
Also, please make sure you test out this scenario.

@kfaraz , Thank you for the review!
Merging since failures are unrelated


full page image?

Hi, I understood that full page can be fragile, but my use case really needs it. How can I take a long full page screenshot? I have looked into the documents of CasperJS and PhantomJS but didn't seem to find anything useful. Changing the viewportSize height didn't help too. Thanks!

Does selecting the html or body tag not do what you're after here?
casper.then( function () {
    phantomcss.screenshot('html', 'whole page');
} );

I think a screenshot of the 'body' tag will be unbounded by viewport. You could try taking multiple segments using coordinates (assuming you know/ can get the page height and width)
phantomcss.screenshot({
   top: 100,
   left: 100,
   width: 500,
   height: 400
}, screenshotName);

dfgue you may want to try updating and changing the viewport again.
This is working for me:
    casper.start(baseUrl, function () {
        casper.viewport(2549, 3307)
            .then(function () {
                phantomcss.screenshot('html', 'whole page');
            });
    });

Running casperjs 1.1.0-beta3, phantomcss 0.10.4, OSX Yosemite

I'm having the same issue, can't seem to set the height for the viewport. Here's what I'm working with:
casper.start().eachThen(pageURLS, function(response) {
		var pageTitle = this.getTitle().replace(pattern, '_');

		// Loop through viewports
		this.each(viewports, function(casper, viewport) {

			// Set viewport
			this.then(function() {
				console.log(viewport.viewport.width + ',' + viewport.viewport.height);
				this.viewport(viewport.viewport.width, viewport.viewport.height);
			});

			// Go to each URL and wait for a response before taking screenshots
			this.thenOpen(response.data, function(response) {
				this.wait(2000);
				phantomcss.screenshot('html', 'page_' + viewport.name + pageTitle);
			});
		});

		// Compare the screenshots
		casper.then(function now_check_the_screenshots() {
			phantomcss.compareAll();
		});
	});

Closing issue, problem is not solvable within library itself


Archivematica dashboard logs you out every time we redeploy

I think it's because we set the Django SECRET_KEY variable based on the ECR repo URI, which means:

It's not particularly hard to work out if you know how we construct those URIs
It changes regularly and breaks all the existing cookies

We should fix it so it doesn't break so often, and is actually secret!

Pretty sure this is fixed.


How can I know the status of group？

If some nodes separate from cluster because of network isolation. How can I know how many nodes are not health and which of these?

It is your application's responsibility to keep monitoring the node & network status.


Make "Pusher" gem available outside development dependencies

Also update Ruby and Pusher versions
This pull request closes issue #243

@chrismccord Do you know how to fix this problem with CI not running SimpleCov?

I fixed the travis build in a previously PR #230

@Godoy Thanks! Now we just wait for your PR to be merged, right?


fix: make authorization module dynamic in order to pass permission provider

Allow AuthorizationModule to be initialized once via register and a permissionProvider options which expects a type. Use registered module via use to get reference to the initalized module.

:tada: This PR is included in version @kittgen/nestjs-authorization-v1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @kittgen/nestjs-authorization-v1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Could you add UpdateTool?

Feature request: Add UpdateTool. Referencing issue: https://github.com/mynttt/UpdateTool/issues/70

Closed by #50


Fails to build Python API on aarch64 platform

What happened?
Building the Python API failed because the sse2 and avx2 extensions are not relevant in the aarch64 environment.
How to reproduce the issue
git clone https://github.com/quantumlib/Stim.git
cd Stim/
cmake .
make stim
python -m venv stim_env 3.8
. ./stim_env/bin/activate
pip install --upgrade pip pybind11 pytest
python setup.py bdist

Relevant log output
running bdist
running bdist_dumb
running build
running build_py
creating python_build_stim
creating python_build_stim/lib.linux-aarch64-3.8
creating python_build_stim/lib.linux-aarch64-3.8/stim
copying glue/python/src/stim/_main_argv.py -> python_build_stim/lib.linux-aarch64-3.8/stim
copying glue/python/src/stim/__init__.py -> python_build_stim/lib.linux-aarch64-3.8/stim
running egg_info
creating stim.egg-info
writing stim.egg-info/PKG-INFO
writing dependency_links to stim.egg-info/dependency_links.txt
writing entry points to stim.egg-info/entry_points.txt
writing requirements to stim.egg-info/requires.txt
writing top-level names to stim.egg-info/top_level.txt
writing manifest file 'stim.egg-info/SOURCES.txt'
reading manifest file 'stim.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'stim.egg-info/SOURCES.txt'
copying glue/python/src/stim/__init__.pyi -> python_build_stim/lib.linux-aarch64-3.8/stim
running build_ext
building 'stim._detect_machine_architecture' extension
creating python_build_stim/temp.linux-aarch64-3.8
creating python_build_stim/temp.linux-aarch64-3.8/src
creating python_build_stim/temp.linux-aarch64-3.8/src/stim
creating python_build_stim/temp.linux-aarch64-3.8/src/stim/py
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I<site-packages>/pybind11/include -Isrc -I./stim_env/include -I/usr/include/python3.8 -c src/stim/py/march.pybind.cc -o python_build_stim/temp.linux-aarch64-3.8/src/stim/py/march.pybind.o -std=c++11 -fno-strict-aliasing -O3 -g0 -DVERSION_INFO=1.10.dev0 -mno-sse2 -mno-avx2
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mno-sse2’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mno-avx2’
error: command 'aarch64-linux-gnu-gcc' failed with exit status 1

Other information
If the sse2 and avx2 sections in setup.py are removed, the API build successfully and all tests pass.
To remove those sections, apply the attached setup.py_patch.txt:
patch setup.py setup.py_patch.txt
Environment
Stim commit 81142ac
Ubuntu 20.04, GCC 9.4.0, Ampere Altra Max without SSE, SSE2, AVX and AVX2
Note: the issue does not occur in this environment: Fedora 35, GCC 11.3.1, Intel architecture with SSE, SSE2, AVX and AVX2

This seems really difficult to fix. The purpose of building the three modules is to allow runtime machine architecture detection, and is necessary in order to distribute binary wheels that work across machines.
You might be able to use the bazel dev wheel build as a workaround?


Bug in 0.10.1a New Game Wizard

Teeny bug in 0.10.1a:  Gotta call CreateFolderIfNotExists() on the folder before you call MakeGameManagerPrefabVariant() around line 142 because otherwise it won't be there.

Fixed in #23


feat(client,api): add user tokens and route for submitting coderoad tutorials

This adds the first part needed to be able to submit tutorials through CodeRoad. It adds tokens for users that they can create and delete. It also adds a few variables for cert claiming on the back end that will be needed at some point.
Edit: This also adds the second part - the route for submitting the tutorials
I am going to open this up for review, but continue working on adding the rest of what's needed - I will probably turn that into a separate PR. I haven't worked with some of these areas of the code base much - particularly, on the back end. It might be a good idea to look a little closer at that area. The front end should be pretty solid. All advice and thoughts are welcome.
The widget only shows up on the relational databases superblock page, so you need to have the upcoming changes visible to see it.
Edit: There are two widgets, a mini one on the relational databases superBlock page - so you need to have the upcoming changes visible to see it. And a second one on the settings page - the code is in client-only-routes/show-settings, uncomment the import at the top and where it's rendered to see it.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Related to: https://github.com/freeCodeCamp/freeCodeCamp/issues/42509

Alright, I think we can probably review and merge this - I updated the PR description.

I think this is ready for review again. It shouldn't change any visible, existing functionality on the site.
There' two parts to this:

the token generation for users
and the route for submitting challenges

The token generation:
Users that haven't created a token will see a box on on the RDBMS superBlock page (superBlock still hidden via upcomingChange) saying that they "need a token to save their progress" or something. There's a button there to create one. This will add a WebhookToken collection to the database with a new token and the user Id. There will be a similar box on the settings page (hidden via comments in the PR) giving them an option to delete their token or create one if they don't have one.
The route:
This token will be passed to CodeAlly, and used by CodeRoad - when a tutorial is complete, coderoad will hit the endpoint I made, /coderoad-challenge-completed - defined in each tutorial repo. The request will include the user token and the repo name - there's an example in the PR. Then, after some validation, the tutorial will be saved to the user's completed challenges.
Some things to maybe look a little closer at in this PR:
I opened the coderoad-challenge-completed route to accept requests without an access or csrf token. I don't see a problem with that, but I'm not the security expert and I don't see another way to do it.
Database updates - I did some pretty thorough testing, it looks like it all works - but I would hate to cause problems with database entries, so maybe just look closely there.
This was not easy to test for me so if anyone wants to get together for an explanation or demo on how it works, let me know. I plan on creating a group of repos that can be used for testing.

Is the coderoad bit supposed to be working yet?

Well - ideally, it would be working. Still some bugs. I tried to load it up today and saw that - made an issue: https://github.com/freeCodeCamp/CodeAlly-CodeRoad-freeCodeCamp/issues/28 Doesn't affect this PR for now.

I've been slowly reviewing this and there are a few things I'd like to discuss before we get it in - I'll finish the review ASAP.  Sorry for the delay.

Btw, sending the token via query param is probably fine, assuming you can't do anything destructive with it.

what am I expecting to see CodeAlly?

CodeAlly adds it to the env variables. You should be able to see it using printenv in the terminal of the VM. CodeRoad must have access to those.

assuming you can't do anything destructive with it.

The only thing you should be able to do at the moment is submit challenges with it. I am thinking that we can potentially use it for submitting other challenges - like the data science stuff. Nothing destructive anyway.

what am I expecting to see CodeAlly?

CodeAlly adds it to the env variables. You should be able to see it using printenv in the terminal of the VM. CodeRoad must have access to those.

Great, thanks.  It's not doing anything with them, yet, right?

It's not doing anything with them...

It's doing what it needs to do with them. It adds them to the environment for CodeRoad to access. CodeAlly needs to update CodeRoad so it uses the new version with the webhook functionality. Basically, CodeRoad has something like: if (token) -> send request when asked. Then 'when asked' part is something I need to add to each tutorial, there's an example here

Should be good to go 👍

What exactly does 'dedicated release' mean? We deploy, then merge only this and deploy again? Just to be clear, this doesn't actually add the curriculum to the site yet, it's all still hidden.

@raisedadead Do you want to hold off merging this until we are ready to dedicate a release to it? Or, will we just cherry pick it when the time comes?
Either way, I leave it to you to merge.

I might be missing something, but I think this is safe to deploy as-is.  The new features are either new endpoints or hidden behind the feature flag, so they should be invisible to users.

Thanks again for all the review everyone 🎉 This was a big one 👍


Missing "metadata.google.internal" in /etc/hosts on ubuntu-xenial stemcell on Google

For newly created VM instances on GCP, there seems to be a
<IP_ADDRESS> metadata.google.internal  # Added by Google
record in /etc/hosts.
The same line is missing in /etc/hosts on a freshly instantiated ubuntu-xenial (google) VM created by the BOSH director for the purpose of running jobs. Saying said that, it does appear after a manual reboot of the machine.
This issue, among other things, prevents running kubeadm as it silently fails to resolve the domain and fails to spin required kubernetes-api containers.

@mikomraz have you only seen the issue on ubuntu-xenial or did it happen also on ubuntu-trusty stemcells ?

@mikomraz In CFCR we use <IP_ADDRESS> or  as DNS in cloud config. It resolves metadata.google.internal correctly.

@pivotal-jamil-shamy I haven't got the chance to check on ubuntu-trusty.
@alex-slynko I understand. But in this case I haven't used CFCR, but installed kubeadm separately.
So it may be worth to update the default cloud-config in bosh-deployment, or better yet, check why the daemons haven't done their job.

@mikomraz any new update on this issue ?

Yes. I confirmed the issue on ubuntu-trusty too.

Hi @mikomraz.
Normally, the contents of the VM metadata records are meant to be consumed by the BOSH agent. The agent will use the IP address (<IP_ADDRESS>) directly in order to bootstrap the VM. What's the use case for the DNS name in your situation?

Hello @freddesbiens,
The use case is that the package kubeadm looks for metadata.google.internal and fails to resolve it, consecutively failing to start a cluster.
I am under the impression that the record <IP_ADDRESS> metadata.google.internal # Added by Google is standard on GCP compute machines, meant to be consumed by everybody - and not BOSH agent specific. Note that on standard provisioned GCP compute the record always exists, and also that on BOSH stemcells after rebooting (allowing kubeadm to succeed in starting a cluster).
Therefore I think it's a bug that the record is missing in the first place.


Add Linting in PR pipeline

Since this project uses Linting to keep the code clean and structured according to other mu-semtech projects, we might want to enforce it in the CI systems as well, like we also do in other projects that still use Drone.

It took a few commits before the Woodpecker system was doing the correct thing. It was missing the git package in the Node with Alpine image. In the end a linting fix was needed to succeed the builds.


Why we cannot we assign a particular action method to a specific version of version neutral controller?

Hello,
I have the following requirement:

A controller has several action methods

Except for one particular action method, all the action methods should be version neutral.

I mark the controller version neutral and also that particular action method particular version. Now, it's not that obvious all the action methods should be work as version neutral and the particular action method should work for particular version as version level action method get preference should get preference than version level at the controller level.

Interesting, so you want to be version neutral, but have specific mappings for some actions. Something like this:
[ApiVersionNeutral]
[Route("api/[controller]")]
public class MyContoller : ControllerBase
{
    [MapToApiVersion("1.0")]
    [HttpGet]
    public IActionResult Get() => Ok("Hello v1");

    [MapToApiVersion("2.0")]
    [HttpGet]
    public IActionResult GetV2() => Ok("Hello v2");

    [MapToApiVersion("3.0")]
    [HttpGet]
    public IActionResult GetV3() => Ok("Hello v3");

   public IActionResult GetAnythingElse(ApiVersion version) => Ok("Hello v" + version.ToString());

    [HttpDelete("{id}")]
    public IActionResult Delete(int id) => NoContent();
}

I've never tried this before. It's reasonable for this to work as long as there is at least one catch all action that can satisfy the request. By claiming to be API version-neutral, you have signed up to accept any and all API versions, including none at all.  Off the top of my head, I don't see why this can't work as long as these rules are followed. It would be very weird to a client to get an error message about an unsupported API version from a version-neutral service.
An alternate way that I know will work is to do all the branching logic yourself. The ApiVersion class is IEquatable and IComparable, which makes writing the logic pretty straight foward.  For example, instead of relying on MapToApiVersion to do the mapping, you can do this:
[ApiVersionNeutral]
[Route("api/[controller]")]
public class MyContoller : ControllerBase
{
    readonly static ApiVersion v1 = new ApiVersion(1, 0);
    readonly static ApiVersion v2 = new ApiVersion(1, 0);
    readonly static ApiVersion v3 = new ApiVersion(1, 0);

    [HttpGet]
    public IActionResult Get(ApiVersion version)
    {
         // NOTE: this is the forthcoming v3 way, but you can also use
         // var version = HttpContext.GetRequestedApiVersion();

         if ( version < V1 )
         {
             return Ok($"Hello beta (v{version})");
         }
         else if ( version < V2 )
         {
             return Ok("Hello v1");
         }
         else if ( version < V3 )
         {
             return Ok("Hello v2");
         }

          return Ok("Hello v" + version.ToString());
    }

    [HttpDelete("{id}")]
    public IActionResult Delete(int id) => NoContent();
}

Version neutrality was always meant to be just that. With the exception of just knowing what the client asked for, it was never really the intent to be able to have per-version branching logic in a version-neutral controller, even though it's possible.
I'll investigate and re-evaluate whether this should be a supported scenario as you've described. My concern is purely on how this appears to a client. In terms of the mapping on the server side, that's an implementation detail and at your discretion.

Yes, I tried the first approach. It's not possible to have per-version branching logic in a version-neutral controller.   The second approach is not viable because we don't want to write a lot of api versioning code at controller level instead we do versioning using the convention outside controller.
You can think about the following scenario. If a controller has ten action methods and a certain change in one action method forces you to go for versioning. Instead of including every action methods in versioning is not it reasonable to exclude them from versioning and mark version only the action method needed to version.

to have per-version branching logic in a version-neutral controller

The investigation here is evaluating the feasibility of your ask. Your request should theoretically be possible, but I don't believe it's currently supported. The primary reason is that version-neutral means that you can support any and all versions. If your controller doesn't support a version because it's not mapped, that is an odd behavior. That would have to yield a 500 or something as a developer mistake; otherwise, I don't really see anything else immediately preventing this from being possible. I'll likely queue this up as a new feature for v3.0.
An API cannot be both versioned and version-neutral simultaneously. Mixing and matching that way is simply not supported. The current interleaving support allows roll forward behavior for newly declared API versions so that only the deltas need to be touched. If you introduce complex interleaving within a single controller, then you will naturally end up with a bunch of complex mapping as well. I recommend that interleaving be limited to small deltas.
Interleaving across types/classes is interesting and arguably useful. It sounds like this is what you are asking for. This is queued up for #230. This feature is much more complicated to implement than it is to consume. The best use case for this scenario is a DELETE action which should be effectively version-neutral despite any other action. The expected implementation will behave similar to the roll forward behavior.
Keep in mind that version-neutrality does not perform any validation on the requested API version beyond ensuring that it's well-formed. If any API is truly version-neutral, it should behave accordingly. It would be bizarre to perform DELETE on resource using an arbitrary, but well-formed API version. The desire to desire to be API version-neutral in this case is a developer convenience and not a reflection of the API itself. The enhancement is, therefore, more about simplifying the implementation details for a service author as opposed to defining an API version-neutral service or action, which is entirely different.

As expected, there was a lot of refactoring and work to get toward supporting this scenario. This scenario will be a subset of #230.
I'm still testing out all variations, but I have a baseline refactoring that works for all the existing functionality (e.g. I didn't break anything). Now, I can move on to verifying the new scenarios. The type of setup you are asking for will look something like:
[Route("api/[controller]")]
public class MyContoller : ControllerBase
{
    [ApiVersion("1.0")]
    [HttpGet]
    public IActionResult Get() => Ok("Hello v1");

    [ApiVersion("2.0")]
    [HttpGet]
    public IActionResult GetV2() => Ok("Hello v2");

    [ApiVersion("3.0")]
    [HttpGet]
    public IActionResult GetV3() => Ok("Hello v3");

    [ApiVersionNeutral]
    [HttpDelete("{id}")]
    public IActionResult Delete(int id) => NoContent();
}

In short, you'll now be able to declare API versions at the action level. This behavior is different from mapping an API version, which explicitly declares which API version an action maps to that is implicitly inferred from its declaring controller. Mixing and matching these concepts can get confusing; however, API versions declared (a la ApiVersionAttribute or ApiVersionNeutralAttribute) will always take prescedence over implicitly infer API versions declared at the controller level. This means there are new conventions to express this as well.
I should also point out that matching can never be implicit or a fall-through. The closest concept is version-neutral, but this means any and all versions, including none at all. I think using MapToApiVersionAttribute as in the original example will work because mapping an API version is not a declaration of a version. From a mapping perspective, an action can explicitly or implicitly indicate it matches an API version declared by it's defining controller. In the case of version-neutral, this would be all API versions. I'm honestly not sure how much sense that actually makes though because that means a client can send you any well-formed API version and it will be accepted. I've seen that setup in practice and it turned out to be nightmare for the service team. In fact, the team never even realized clients were sending bogus, undefined API versions until they started enforcing strong API version semantics.
I expect 3.0 Beta 2 to contain this functionality. As nearly all the issue from Beta 1 have been addressed, I anticipate that release coming in the next week or so.

@commonsensesoftware I understand your point and it's reasonable. But, there are some cases when you compelled to introduce versioning for only specific one action method and you don't want to introduce versioning for that for the rest of the action methods. Also, there is the controller which will never be upgraded and hence does not need backward compatibility support.


MWPW-126051 [Milo Block] Viewport Specific Container

https://jira.corp.adobe.com/browse/MWPW-126051
docx file
test url: https://viewport--helpx-internal--adobecom.hlx.page/content/help/en/internal/viewport-test
A few notes:

the main changes are css only. They only make it so certain classnames (that can be added to blocks in word) are hidden in certain viewport sizes.
A generic block that does nothing was added so that users have the ability to add classnames to arbitrary bits of content
The import script for viewportspecific containers were written to be run after all the other blocks have been imported.  This is just to handle regular (non-block) content that happens to be hidden in some viewport sizes.

Could you resolve the conflict plz @sharmrj

Could you resolve the conflict plz @sharmrj

@nkthakur48  done


make sure embedding model name can be specified for openai embeddings

hi, have you tried if it works? on us it does not work ok

I hope each model to be customizable, I feel terrible when I'm using gemini at the moment

When I did this edit in the local package, it worked for me. I only enabled text-embedding-3-small in my openai env and hence I got an error. Once I applied the patch, it is working for me now.

on us it does not work ok
can you be more precise?

give us the code of the example


qsort: add benchmarks from the standard library

These will let us be more confident that the qsort makes sense to use,
especially when e.g. the Go standard library introduces a new sorting
algorithm, we can compare the two.

For completeness, adding a snapshot for a run on a x86:
goos: linux
goarch: amd64
pkg: github.com/segmentio/asm/qsort
cpu: Intel(R) Xeon(R) CPU @ 2.60GHz
BenchmarkSort8/100000
BenchmarkSort8/100000   	     625	   1916996 ns/op	 417.32 MB/s
BenchmarkSort8/1000000
BenchmarkSort8/1000000  	      49	  24289400 ns/op	 329.36 MB/s
BenchmarkStdlibSort8
BenchmarkStdlibSort8/100000
BenchmarkStdlibSort8/100000         	      86	  11709887 ns/op	  68.32 MB/s
BenchmarkStdlibSort8/1000000
BenchmarkStdlibSort8/1000000        	       7	 144533331 ns/op	  55.35 MB/s


feat(meta): iterative streaming scheduler (part 1)

Signed-off-by: Bugen Zhao<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
(as explained in #7420) This PR introduces a brand new streaming scheduler which is done by automatic iteration based on a Datalog syntax. In short, by simply pre-defining some rules, the scheduler can directly derive the distribution (or vnode mapping) for the given fragment graph and fill the exchange with correct dispatchers, without thinking about the topological order or handling edge cases anymore.
https://github.com/risingwavelabs/risingwave/blob/b5b70668cf275a83b169b0088e3403686173697d/src/meta/src/stream/stream_graph/schedule.rs#L83-L98
In this PR, we only utilize this new scheduler in parallelism assignment, while the derived distribution itself is ignored. This can be fixed by removing the old scheduler in the next PRs.
By making the scheduling phase ahead of time, we can also simplify the logic like actor ID assignments, as we're building actors after we know the total count of them.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

#7420

cc @chenzl25 I've reverted the changes of the build order and parallel_degree derivation for delta-join and it seems to work pretty well. 🤤🚀


More robust error handling

See #15.
The most obvious use case this improves is previously in-app purchases would never get a callback if the user cancelled the purchase from the confirmation popup.

Thanks for the PR. It's a breaking change that we now send the error callback on cancel. Can you document that as well?
We can bump the major version then.

Hey, re: RCTUtils, I think you can just:
switch (transaction.transactionState) {
   case SKPaymentTransactionStateFailed: {
     NSString *key = RCTKeyForInstance(transaction.payment.productIdentifier);
     RCTResponseSenderBlock callback = _callbacks[key];
     if (callback) {
         callback(@[RCTJSErrorFromNSError(transaction.error)]);
         [_callbacks removeObjectForKey:key];
      } else {
          RCTLogWarn(@"No callback registered for transaction with state failed.");
      }
     [[SKPaymentQueue defaultQueue] finishTransaction:transaction];
     break;
}

@fisch0920 can you incorporate @grabbou feedback?

Ping

@grabbou Could you please explain what does it mean? How I should to update your code to get it working?

wrap it with @(...) - that converts int to NSNumber which is an Obj-c object. Looks like a bug in my snippet!

It seemed just missed out RCTUtils.h :)

I've created alternative PR to move this fix forward.

Thanks for all the help here guys!


Tags for resource get deleted on second azd up execution which blocks Azure Functions deploy from working

[X] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
azd version 1.10.1 (commit 31409a33266fb4a5fdbb644bc83988e725d6c7c9)
Describe the bug
Running azd up on a project that has a Function App (Flex Consumption) works the first time but shows the following on subsequent calls:
ERROR: error executing step command 'deploy --all': getting target resource: resource not found: unable to find a resource tagged with 'azd-service-name: processor'. Ensure the service resource is correctly tagged in your infrastructure configuration, and rerun provision
So, after running azd up the first time the app has the tags and deploys correctly:

But after attempting azd up the second time, it fails at the deploy stage because the tags are not there:

To Reproduce
This shows up from time to time. I have just reproduced this with the E2E DURABLE-FUNC-ORDER-PROCESSING sample for Azure Functions Flex Consumption when reviewing this PR so you can use that PR (or the sample from brain if the PR is already merged by the time of reviewing this).
Get the code of the sample down, run azd up, test the app as per readme, then make a small code change and run azd up  again.
Expected behavior
Repeated azd up should correctly re-deploy the app.

I can see the resource is tagged correctly in the Bicep file. Will need to investigate further.

@weikanglim - I have just run into this one again, this time with the https://github.com/Azure-Samples/azure-functions-java-flex-consumption-azd sample. I had run just earlier that sample with SKIP_VNET set to true. Then I did an 'azd down' and deleted the .azure folder. Then tried azd up again but this time without setting SKIP_VNET. Got this:

Then I ran azd up again and this time it publishes fine:

It does seem like there's something strange with the tag search.

@nzthiago Thanks for reporting the second instance of the issue. I apologize but I haven't had a chance to take a real look at this.
I'm wondering if something along the following is happening:

For the second instance, it may be perhaps that there is a delay in ARM resource tags actually showing up when queried for after provisioning (we have not seen this reported widely though, which perhaps makes this unlikely).
There may be some automation in the subscription that is somehow updating tags outside of Bicep
There may be something related to flex-consumption functions that updates the tags outside of Bicep

I'd recommend for debugging purposes, when this happens again, to leave the Azure resources as-is in their state. Perhaps if we looked at the Activity log of the resource in the Portal, we can see if there are updates being initiated outside of the Bicep provisioning and see if tags are being modified.

I'll remember to keep the assets around next time I run into this, it does happen from time to time so it's not an isolated thing.

@weikanglim moving to backlog. Once, we get a repro/environment please pull this back into the sprint.

I have a current instance of this issue. In the resource group activity log I see this entry, that seems to removing both tags and properties.tags from the Microsoft.Web/sites resource?

The "Event initiated by" shows as empty for that specific "UpdateWebSite" operation. So does the CreateWebSite which was initiated by AZD:

@nzthiago In your Bicep files for this particular deployment, is httpsOnly specified at all?
I really do think the policy that is tied to the actor CloudGovRemediationWe.. is the likely culprit here. Investigation notes below:

The update on 2:05 pm PDT only set httpsOnly from false to true. While doing this, it also cleared the tags that was set on the resources.
The update on 2:05pm PDT is 10 minutes after the app settings update on 1:55pm PDT.

From the second screenshot, I am unable to correlate the events, but based on the how recent column named "Time", I can see that:

UpdateWebSite as you highlighted from azd happened at 42 minutes ago
UpdateWebsite from CloudGovRemediationWe.. happened at 32 minutes ago

which is the 10 minutes interval we see from screenshot 1.
This leads me to believe that CloudGovRemediationWe.. is the policy that's causing the behavior you're seeing.
As a foot note, I do think you're seeing an issue as a result of azd's resource discovery mechanism relying on resource tagging -- which is susceptible to the unfortunate underlying issues that you're seeing. I think it'd be best if resources discovery just happened as part of provisioning, rather than leveraging metadata being set on these resources.

@weikanglim - Aha, you might have found the reason why this is happening then! Looks like the policies being auto applied by that application are clearing the tags from the app. I will try figuring out who owns that policy/entra app to let them know. But glad to finally understand why this was happening.
I agree that this resource discovery based on tags might not be the best approach, perhaps a way to do it by actual resource id would be better. Happy for you to close this thread this as we found the root cause, but feel free to start a separate discussion on that. Thanks!!


Add an option in the gradle.properties for html junit reports

This is a simple enhancement that makes it easy to enable the html test report that gradle would normally produce (but we disable to save a few seconds). I frequently have a NO_COMMIT change list containing this, and so I've finally got around to formalizing it into a gradle.properties option so others can use it if they like.
I find it far faster to click on the link displayed at the end of a failed build. YMMV, but now you won't have to edit anything that's version controlled to try it.

This is small, and build only, So I intend to merge/port in a day or two unless I get feedback.


feat: add built-in pipes for basic cases

Description
As a developer I would like a set of pipes to be built-in inside the library to ensure correctness for the most common cases.
These pipes should also expose a callback when throwing an error to allow the user to choose the exception to throw.
Requirements

[ ] ParseIntPipe
[ ] ParseDoublePipe
[ ] ParseDateTimePipe
[ ] DefaultValuePipe
[ ] ParseBoolPipe
[ ] ParseListPipe

Rejected because it cannot be attached to a specific property (path parameters, query parameters, body), they would be implemented with a weird syntax and implementation.
Go back to this task when the pipes change implementation.


Running part of your wasm in a web_sys::Worker?

Summary
What is the best architectural approach to have a 'pure' wasm web application that runs part of the calculations in a web worker?
Additional Details
I am still fairly new to Rust and especially web_sys. However I find the concept of wasm really exciting and I am currently trying out to build an easy web app. It needs to react to clicks on a canvas, some buttons etc., but then there are heavier calculations which should run in the background.
Initially, I followed the Wasm Game of Life tutorial and found a good first entry point there. After reading this guide, I designed my app to handle the user interaction part in JS. The background calculation was running actually in the foreground but returned very regularly, giving a false impression of responsiveness.
Next I read about web_sys and especially building wasm apps that can be deployed without a bundler. Now I rewrote the user interaction part almost purely in Rust and web_sys. Knowing that there is probably no native multiprocessing in wasm as of now, web workers are the only alternative.
My dream scenario would be to spawn a web_sys::Worker and hand it a struct with a method or a function callback to run. However it looks like a web worker expects a URL to execute (1, 2). Loading in any local JS via the URL works, but not a wasm module.
If I create a worker in my main wasm app
pub fn setup_worker() {
    Worker::new("worker.js");
    console::log_1(&"Created a new worker".into());
}

and have this minimal worker.js:
import Dummy from './pkg/my_wasm_app.js';

I get the error SyntaxError: import declarations may only appear at top level of a module. This might have JS reasons (not so familiar with JS ^^). Though maybe someone could point me in the right direction? Which one of the following options is possible? And which one is best?

Setup a separate wasm project with target so that I can load an init. I think it is not possible to have two wasm targets in the same cargo.toml so it would be annoying to maintain two project folders for essentially one projects. Also I would need to figure out a better way to load it given that the above approach at least for some imported module was not allowed in the worker.
Pass a struct to a worker that is being created and glue the interaction with Worker::set_onmessage etc. - this seems best to me but I am not sure if it is possible at all.
Setup the worker code in JS (like e.g. here and just call it from web_sys. I don't like this option very much because it would mean having to dig deeper into JS for me.

Are there any good tutorials on this? I know about the Parallel Raytracing example but I could not really extract how to use the web_sys::Worker from it. Also this WASM Fractal Generator seems to have the worker and canvas interaction in JS, so it is not really what I am looking for.
Any hint/explanation would be greatly appreciated!

Alright, thank you any way @alexcrichton :slightly_smiling_face:  I will take a closer look at the raytrace example then.

I could not let it go and finally figured it out! :smiley: One of the main blockers for me was that Firefox does not support importing ES modules in workers - with my limited JS knowledge, it took me a while to nail down the problem as this.
To be able to go back to it, I created four example starting from a very basic example with modules (which only works in Chrome) over using --target no-modules to a minimal 'full' example in which I spawn a web worker with web_sys from Rust and interact with it in a useful way. You can find the example in this repo. Do you think the fourth example could be helpful for others as well @alexcrichton ? Then I would create a PR for wasm-bindgen/examples and put it up for review.

More examples always seems good to me!

Great, I opened a pull request :) Since it is my first contribution to wasm-bindgen, I hope I followed all the conventions that I could deduce from other examples. Would be great if you or someone else could review!


Nested range causes false positive "Range statement [..] does not reinitialise the variable"

Repro:
https://gist.github.com/prashantv/9febe96e7df2b0d5311fa3b4aedb3059
Using the latest release of paralleltest (1.0.3) raises an incorrect issue:
[...]/foo_test.go:27:2: Range statement for test TestFoo does not reinitialise the variable tt2

tt2 is reinitialized:
https://gist.github.com/prashantv/9febe96e7df2b0d5311fa3b4aedb3059#file-foo_test-go-L31
This seems related to https://github.com/kunwardeep/paralleltest/issues/8 (though the last comment on the issue indicates the issue is fixed)

Hey @prashantv, unfortunately, I am not doing active development on this., but I would be more than happy to look at a PR if you have one.

Hey @prashantv would you be able to test this with the latest fix?


[Feature]: Support table sorting process

Description
Currently, the self-optimizing process on the table does not sort the data in the table. If a sorting process is added, it can improve the performance of filtering queries on the sorted fields.
Use case/motivation
Support configuring sorting rules on tables. The data will be sorted according to the rules to improve the query performance of the table.
Describe the solution

Support configuring sorting rules for table rows.
Automatically sort the data.
Support multiple sorting methods, such as regular sorting and z-order sorting.

Subtasks
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@zhoujinsong I'm glad to help with this one. Please assign it to me if no one is working on it.


Add keeping language state in the URL.

#224

this did not fix the issue #224. Directly after switching the language, the URL briefly shows the new value, but as soon as the data is updated, the value in the URL is reset to the old one


【Inference】optimize preprocess

PR types

Performance optimization
PR changes

Others
Description

Others

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.root seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


"Process name" field is duplicated in C7

Describe the bug

Steps to reproduce

Select a participant
now this happens

Expected behavior
No duplication.
Environment

OS: [e.g. MacOS 10.2, Windows 10]
Camunda Modeler Version: 5.23.0
Execution Platform: Camunda 7
Installed plug-ins: [...]

Additional context
Reported at https://camunda.slack.com/archives/C032H77434N/p1716895553188809

This was introduced via https://github.com/bpmn-io/bpmn-js-properties-panel/pull/1043


Mark correct side of binop on failed type check

Signed-off-by: Julius Volz<EMAIL_ADDRESS>

Going to merge this, @Nexucis please review after vacation :)


Same label for output_element_serie but shows up two times in legend of chart

For the CO2 emissions chart (#46) I have added the CO2 emissions of bunkers in 1990 and also for the present and future. These are the series of this chart:

I have given the CO2 emissions of bunkers in 1990 and also for the present/future the same label groups.bunkers, because I wanted to show 'international transport' only once in the legend. However, it shows up 2x:

Is it possible to show it only 1x?

Is it possible to show it only 1x?

You mean the duplication of "International transport" in the legend?
I think this is the result of you adding it for both 1990 and for the future. Alternatively, you could add the 1990 value directly to the total (grey) bar. This would be consistent with how we show the other sectors now.

You mean the duplication of "International transport" in the legend?

Yes

Alternatively, you could add the 1990 value directly to the total (grey) bar. This would be consistent with how we show the other sectors now.

Yes that would be consistent. However, I think it is better to keep international transport apart from the rest of the emissions of 1990, since it is never included in the statistics. What do you think, @jorisberkhout ?
I can also change it back to how it was with a separate legend 'CO2 emissions international transport 1990':

I have discussed with Chael that I am going to give the CO2 emissions international transport 1990 another colour to make the distinction.


Regulatory annotation download link is hardcoded

Hello!
https://github.com/snakemake-workflows/cyrcular-calling/blob/ccd556ac3e007e1f5ffc039a9c2550b067c27dc3/workflow/rules/ref.smk#L74
The number between regulatory_features and .gff.gz  in the url varies between releases. Attempting to wget https://ftp.ensembl.org/pub/release-{params.release}/regulation/homo_sapiens/homo_sapiens.GRCh38.Regulatory_Build.regulatory_features.20220201.gff.gz if the release version is set to 110 on the config file will cause this to fail, since the proper url for release 110 would be https://ftp.ensembl.org/pub/release-110/regulation/homo_sapiens/homo_sapiens.GRCh38.Regulatory_Build.regulatory_features.20221007.gff.gz

Do you happen to know of a programmatic way to get that date correct? Everything else can easily be derived/specified, but the date cannot be known in advance, unless you either check the ftp directory / there is an overview file with release <-> freeze date information.

I'm pretty new to programming in general, which is why my first instinct is probably to regex hammer it - wget does have an option for it, I could play around with that.


when upgrade NodeJS up to v20+ local proxy not work

Describe the bug
I have come across a issue with vite proxy like this

using fnm: the issue only repo on NodeJS >=20
NodeJS v22.2.0 + pnpm 9.1.1 repo
NodeJS v20.13.1 + pnpm 9.1.1 repo
NodeJS v19.9.0 + pnpm 9.1.1 not
NodeJS v18.20.2 + pnpm 9.1.1 not
Reproduction
tring to create the demo
Steps to reproduce
No response
System Info
System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1 Pro
    Memory: 227.63 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.13.1 - ~/.volta/tools/image/node/20.13.1/bin/node
    Yarn: 1.22.22 - ~/.volta/tools/image/yarn/1.22.22/bin/yarn
    npm: 10.5.2 - ~/.volta/tools/image/node/20.13.1/bin/npm
    pnpm: 9.1.1 - ~/.volta/tools/image/pnpm/9.1.1/bin/pnpm
  Browsers:
    Chrome: 125.0.6422.61
    Chrome Canary: 127.0.6486.0
    Edge: 125.0.2535.51
    Safari: 17.5
  npmPackages:
    @vitejs/plugin-basic-ssl: ^1.0.1 => 1.0.1
    @vitejs/plugin-react: ^3.0.0 => 3.1.0
    vite: ^4.5.3 => 4.5.3

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I prepared the mini repo demo
https://github.com/rawbin-/vite4-proxy-repo
But when I set the proxy target to a debug address like localhost:8080, everything seems goes well. And when I set back, it show up again.  So it seems a target releated issue.
When I turn off the SecureLink, all thing goes well...


Unpin hub

What does this PR do?
Hub team put a fix in yesterday on the backend to fix the related failures. As a result we can safely unpin it again :) (this also fixes the failing integration test on main)
Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@SunMarc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Analyze Profiler Output

This ended up being way more detailed than I anticipated.
profile.txt

Well, right off the bat it looks like:
(call)|         1|      2.70472|      2.70472| 71.79%|# /private/var/folders/00/vp4bg2md3ng4sqkg3hrz_j1003frjd/T/pip-build-iHBwmU/Django/django/init.py:8 setup
70% of the time is spent setting up Django. That seems like a good starting point.
The majority of the rest is in
(call)|         1|      1.04399|      1.04399| 27.71%|# /private/var/folders/00/vp4bg2md3ng4sqkg3hrz_j1003frjd/T/pip-build-iHBwmU/Django/django/core/handlers/wsgi.py:162 call
and everything else looks pretty trivial.

In setup(), populate eats the most..

Poking @stephrdev in case you have any insights/magic tricks you can think of to throw at this!

Ticket for upstream discussion: https://code.djangoproject.com/ticket/26284

We got this down to ~30ms.

@Miserlou can you provide more details on how you optimized this?

Hi @sridhar562345 The new, official, and actively managed Zappa project is here.
You can post your issue.


Write Blurb for "Word Embeddings" (github repo)

(see syllabus for instructions).

Word Embeddings
Word embeddings demonstrate how a word’s semantic context changes across time and location. The word embedding process at its finest answers questions like, “How did the United States Congress discuss race during the Civil War in comparison to the Civil Rights Movement?” or, “In what ways do school boards in Texas discuss gun violence when compared to schools in New York?”
The embedding process starts with word vectors, which take note of which words in a document have similar meanings. These vectors successfully associate phrases like ‘Mark Antony’ with ‘Rome’ or ‘Louis XIV’ with ‘Versailles.’ Moreover, historians can use word embeddings to compare how people discussed words over time. For instance, scholars can analyze how the British Parliament discussed the term, ‘India’ during the 1857 Indian Uprising in comparison to how Britain discussed the country during the 1919 Amritsar Massacre. Scholars can also analyze how speakers use words today as one politician in California may discuss the term, ‘abortion’ differently than a politician in Georgia may utilize the same word.


datetime.datetime.utcnow is deprecated in Python 3.12

See https://github.com/python/cpython/issues/103857
utils.utcnow() creates a timezone-aware datetime in the recommended way so it is fine to use as an alternative in most cases.
For an exact replacement, utils.utcnow().replace(tzinfo=None) can be used.
Most instances of utcnow and utcfromtimestamp were already fixed prior to the creation of nextcord, however one was still found.
index 725f498a76..c40a6ebbae 100644
--- a/nextcord/member.py
+++ b/nextcord/member.py
@@ -801,7 +801,7 @@ async def edit(
                 if not suppress:
                     voice_state_payload[
                         "request_to_speak_timestamp"
-                    ] = datetime.datetime.utcnow().isoformat()
+                    ] = utils.utcnow().isoformat()
                 await http.edit_voice_state(guild_id, self.id, voice_state_payload)

I found another instance in the same file:
https://github.com/nextcord/nextcord/blob/b3b249e313adb46de76ce35da1cf65aff3769c3d/nextcord/member.py#L854


[jtwig] Add jtwig template engine skeleton

Thanks @majorpasza. @alzuma was supposed to take over this commit, it's missing a way to configure the engine at the moment. Have you had time to look at it @alzuma?

@tipsy nope didn't have spare time for this yet. Will look into it asap.

@tipsy take a look at https://github.com/tipsy/javalin/pull/222 sorry for delay :)

No worries, thanks for your contribution !


Synchronize shared configuration

This pull request was created automatically by the sync-shared-config workflow.

Homebrew/.github#183


[ART-5142] Support patch_version defined in assembly config

If we have assembly config like this:
  art5142:
    assembly:
      type: custom
      basis:
        assembly: 4.12.99
        patch_version: 99

The release name will become 4.12.99-assembly.art5142.
In case patch_version is not defined, let our automation to look at the chain of assembly inheritance to determine one, e.g.
  art0000:
    assembly:
      type: custom
      basis:
        assembly: 4.12.88
  art0001:
    assembly:
      type: custom
      basis:
        assembly: art0000
  art0002:
    assembly:
      type: custom
      basis:
        assembly: art0001

The patch_version of art0002 will default to 88 because release 4.12.88 is the closest ancestor of type standard.

@thegreyd Yes, I will update docs later.


How to use condition expressions in a query?

Hey. I have a question about using Condition expressions with Dynamoid.
See https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.ConditionExpressions.html
I have a users table with name: String and settings: Map attributes. Settings could contain a lot of different nested maps. I need to filter my query and find only users which has color setting in settings map, something like:
FilterExpression = 'attribute_exists(#0.#1)',
ExpressionAttributeNames = {
    "#0": "settings",
    "#1": "color"
},

Is it possible to add such condition to Dynamoid where query on using some plain AWS sdk call? Thanks :bow:

I will check if it's possible to do it with QueryFilter/ScanFilter request parameters (that are deprecated now).

Sorry for bothering @andrykonchin , but maybe any update on this? Found filter_expression_convertor (https://github.com/Dynamoid/dynamoid/blob/6d53f100f0478bc04c7c45646771182df603fdc8/lib/dynamoid/adapter_plugin/aws_sdk_v3/filter_expression_convertor.rb#L54 ) don't know if it's possible to reuse it for my case.

It seems QueryFilter/ScanFilter don't support conditions on collections like List and Map:

This parameter does not support attributes of type List or Map.
https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Scan.html#DDB-Scan-request-ScanFilter
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.QueryFilter.html

But recently where was switched from them to the Expressions style, that does support such conditions.
So right now 'settings.color.not_null' => true should not work but it seems easy to add. Will try add it soon and release in the next release.

Hi @andrykonchin . I see new version is here, I checked https://github.com/Dynamoid/dynamoid/pull/655/files but not sure how correctly to pass params to the .where method to filter by the Map fields which has some key :disappointed:  Can you please help with that? Maybe we also need some READE section with how-to section on how to use new expressions

OK I see Dynamoid::Criteria::Chain doesn't allow it via def field_condition which does the following:
name, operator = key.to_s.split('.')

So for where("settings.color.not_null": true) it returns  => ["metadata", "screen_scores", "not_null"]

The work is in progress (#696) - I will come back to it soon.


enter_modify

fix #324
Make the curveadm enter command enter the leader container without parameters

@LYPWYT BTW, squash into one commit first.

BTW, please push it to develop branch again.


Add Practice Exercise: word-count

Problem specification:
https://github.com/exercism/problem-specifications/tree/main/exercises/word-count
TODO:

generate the exercise with ./bin/fetch-configlet && ./bin/configlet create --practice-exercise word-count
check if any of the existing tracks (examples below) implement the exercise and you can reuse the implementation:

Go: https://github.com/exercism/go/tree/main/exercises/practice
Rust: https://github.com/exercism/rust/tree/main/exercises/practice
Python: https://github.com/exercism/python/tree/main/exercises/practice

use exercise's canonical-data.json to see which test cases to implement:
https://github.com/exercism/problem-specifications/blob/main/exercises/word-count/canonical-data.json

Let me work on this.

Absolutely!


KPI ranges

Hello,
how can i make different ranges for each KPI, for example if i want for KPI1 the green color when the result above 90% while for KPI2 the green color when the result above 70%.
another issue, what the effect  when i choose compare with target and compare with minimum in the score calculation and also the maximum and minimum values.

now only one Color settings, no way do it.
but you can modify expression ( BSC_RPT_EXPR0005 ) force change KPIs color on Report ( vision, Perspective,Objective cannot force change color).
view the example:
modify expression ( BSC_RPT_EXPR0005 )

change result

compare with target or with minimum will effect the status icon on BSC/KPI-Report.
you can custom the expression change the effect
please view the issues :
https://github.com/billchen198318/bamboobsc/issues/23
Warning : if you want modify/update expression , please first backup you database. because the wrong expression bambooBSC system will crash.


chore: add TypeScript definition file

Pull Request Test Coverage Report for Build 11

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

Totals

Change from base Build 10:
0.0%

Covered Lines:
77

Relevant Lines:
78

💛  - Coveralls

Thank you, @Quramy. Looks great!
@FerrielMelarpis, agree - good start. We can alway improve in time.

Published as v1.1.0


upload dumps to STAGING

Add loading dumps to STAGING Crash2 server.
For now I specified just 2 necessary parameters: product (product name) and version. We can extend this list for future. Also Henning mentioned that it would be a good idea to use version generated by git with git describe --always --tags instead of using OrbitVersion::GetVersion. So I'm going to change version in near future.
https protocol is not supported for Linux (got Check failed: scheme == "http"), so I used http for Linux.

Ah. I didn't know about OrbitVersion::GetVersion. I think that's fine.

Looks good. Just one last thing: Can we disable the crash handler by default for now and add an ABSL_FLAG (https://abseil.io/docs/cpp/guides/flags) to enable it when needed? Uploading crashdumps without the user's consent - even if it's temporarily - feels a bit strange.


aws:sqs FIFO queue 'name' option is mandatory, update the doc

Hi there. I think this is basically concerning the Documentation.
My short story how I got there is this:
AWS SQS requires queue name to have '.fifo' suffix for FIFO queue.
I have set the option fifoQueue: true .
When I name my queue 'messages-dev.fifo' I got this error:
aws:sqs:Queue (messages-dev.fifo):
    error: aws:sqs/queue:Queue resource 'messages-dev.fifo' has a problem: only alphanumeric characters and hyphens allowed in "name"

So I remove '.fifo' suffix and again error
aws:sqs:Queue (messages-dev):
    error: Error validating the FIFO queue name: [FIFO queue name should end with ".fifo": messages-dev-eb6b723]

Here is my code of queue creation
  const queue = new aws.sqs.Queue(`messages-${config.ENV_STAGE}.fifo`, {
    fifoQueue: true,
    visibilityTimeoutSeconds: 1,
    messageRetentionSeconds: 345600, // 4 days
    maxMessageSize: 262144, // 256 KiB
    contentBasedDeduplication: true,
    delaySeconds: 0,
  });

Then in the issue #447 I saw the name property given in options. I tried and it worked.
Just added name: 'messages-dev.fifo' in options
My suggestion is to update this doc.
Related to the issue #967

Based on the testing I'm doing with the latest version (3.32.1) this appears to be an issue still. However, the related issue was closed and a PR was done to fix this. This issue seems to be present even when running what is documented in the example of how to create an SQS FIFO queue.

Hi @abrahampcmb
We shipped a patch release for this yesterday that fixes a regression of autonaming of fifo queues - so this piece of code will now work as expected:
const queue = new aws.sqs.Queue(`messages-${config.ENV_STAGE}`, {
    fifoQueue: true,
    visibilityTimeoutSeconds: 1,
    messageRetentionSeconds: 345600, // 4 days
    maxMessageSize: 262144, // 256 KiB
    contentBasedDeduplication: true,
    delaySeconds: 0,
  });

Notice I didn't have to add ".fifo" anywhere in the name - Pulumi will detect it is required and ensure it is added
Please let us know if this continues to be a problem
Paul


Specify packaging version to be more than 17.0

Older version of the packaging module cause an error when saving model checkpoint.
The error is in the atomic_save: if Version(torch.__version__).release[:3] == (1, 6, 0):
For old version of packaging (e.g., 16.8) the call produce the following errror:
AttributeError: 'Version' object has no attribute 'release'
What does this PR do?
Specify packaging version to be grater or equal to 17.0 in order to avoid bug in the atomic checkpoints save
I tested packing version from 17.0 to 20.9 (latest at the time of writing) and the bug is fixed
How to reproduce the bug

pip install packaging==16.8
Run any training that save a checkpoint

or reproducing the call at line: https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pytorch_lightning/utilities/cloud_io.py#L61

pip install packaging==16.8
python

import torch; from packaging.version import Version

Version(torch.version).release[:3]

@awaelchli @Borda @carmocca @justusschock any suggestion of why some tests is failing?


Concensus: Aleph or not?

Suggestion details
A method for determining concesus in the blockchain must be implemented. Originally, this could have been (and may still be) Aleph. For a variety of reasons, this has not been realized.
This ticket is about implementing concensus

[ ] Evaluate the continued use of aleph or not

Use aleph

[ ] Integrate aleph
[ ] become expert

Not use aleph

[ ] Design communication semantics
[ ] design concensus semantics (even if very simple)
[ ] Implement

Additional details
No response

The consensus algorithm will continue to improve, which is a long-term task.


React support

Does meteoris support react component rendering?
There is this ReactLayout package

tl;dr
looks like ReactLayout is outdated for newest meteor version..
https://github.com/kadirahq/react-mounter

Soon I have plan on it. But not for now


chore : refractor  drawable adaptor

Fixes #164
Changes:

separate the logic of changing card background to viewholder
changing card backgrounds using notifyItemChanged which doesn't update the whole list
applying kotlin code practices

Screenshots for the change:

@iamareebjamal  please review


(fix): Fixes parsing of latest datafiles in 2.x.x

Summary

This adds support to handle and parse both single leaf node and arraylist of audience conditions.

Changes made, please review now.


Is it supported to add custom ITelemetryInitializers in Isolated Azure Func(v4)?

Adding telemetry initializers into isolated v4 AZF doesn't seem to work:
            IHostBuilder host = new HostBuilder()
                .ConfigureFunctionsWorkerDefaults()
                .ConfigureServices(services =>{
                    services.AddSingleton<ITelemetryInitializer, MyInit>();  // MyInit doesn't seem work
                });
            IHost app = host.Build();
            app.Run();

What is the correct way to register ITelemetryInitializers for all Azure Function Telemetries? Or is it not supported? How about it in ClassLib mode?

This is supported if you're using the preview of the isolated worker App Insights support: https://github.com/Azure/azure-functions-dotnet-worker/pull/944#issue-1282987627.
However, note that logs emitted by Functions include those from two processes: the Functions host and the isolated worker. And any customizations added to the worker will only apply to the worker and not to those logs emitted by the host.

Hey @brettsam, thanks for pointing me in the right direction. I don't fully understand logs emitted by the workers or by the host.  I tried the package, and here's what I saw:
        [Function("Func1")]
        public HttpResponseData Run(
            [HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")] HttpRequestData req)
        {
            using (IOperationHolder<RequestTelemetry> operation = _telemetryClient.StartOperation<RequestTelemetry>("Func1Request"))
            {
                try
                {
                    // Warning will be sent to application insights.
                    _logger.LogWarning("This is a warning!");

                    // Other code
                }
                catch
                {
                    operation.Telemetry.Success = false;
                    throw;
                }
            }
        }

Do I understand the situation correctly?

The telemetry for the Function named Func1 would not have any telemetry initializer (emitted by host?), right?
The telemetry for the manually authored operation of FuncRequest will have the telemetry initializers applied - worker?
The warning out of ILogger would have the telemetry initializers applied - worker,

@xiaomi7732 https://github.com/Azure/azure-functions-dotnet-worker/issues/1292#issuecomment-1419473909 might provide additional insights

@brettsam moving this to sprint 141, but please feel free to change if not appropriate.

@xiaomi7732 in your sample, that is all code in the worker process - so yes your telemetry initializer will apply to those items. However, in dotnet isolated there is another process, the "host" process, which also emits telemetry items. The host process is what controls the lifetime of your worker and dispatches function invocations to it. It is telemetry items coming from the host process which your telemetry initializers will not affect.
You will need to follow @brettsam's link for sample code on how to setup AppInsights on the worker.

The telemetry for the Function named Func1 would not have any telemetry initializer (emitted by host?), right?

This is fairly broad. But yes, there will be several telemetry items which apply to Func1 which originate from the host, and so the initializer does not apply.

The telemetry for the manually authored operation of FuncRequest will have the telemetry initializers applied - worker?

Correct

The warning out of ILogger would have the telemetry initializers applied - worker,

Correct

That makes sense. Thank you.