Deprecate allowing http OR http.request in transport.request

We allow http OR http.request as the first argument to transport.request to support callers of non-public methods (e.g. _refresh or _revoke) that passed http.request instead of http (from httplib.Http objects).
This should be more restrictive but we should support both to avoid breakage.

FYI I created this to reference it from #602

I'd say let's rip the band-aid off and remove the argument all together. But @nathanielmanistaatgoogle might disagree.

No disagreement... but I don't yet entirely understand how removing the argument altogether would work?

Since the transport library can handle all of the http stuff itself, there's no need to pass http objects into refresh(), etc.

I don't see how the world @jonparrott keeps talking about could work, but I'm not closed off to the idea.

Haha. Okay, yeah, let me think of a better way to explain this.

We can move this discussion to #128 if needed, but what I'm getting at is this:
Presently, several methods on Credentials takes http as parameter:

authorize()
get_access_token()
refresh()
retrieve_scopes()
revoke()

I'm proposing we go ahead and remove the http parameter from everything but authorize. The necessary methods should just call transport.request(uri, method, ...). Transport should handle getting an appropriate http object to make the request.
authorize()'s http argument should eventually be changed to support other http libraries, but can just work with httplib2 for now.

Let's discuss on #128. I don't think that will make people happy, unless they can toggle a switch on oauth2client.transport to make it use their desired transport under the covers.

Raising this from the dead, I'm gonna remove the ability to pass httplib2.Http.request instead of just and httplib2.Http. Might as well do it since it's a major version change.

(Also it allows me to restrict and solidify the interface)

On second thought this may just be an implementation detail of the httplib2 transport. I'll revisit later.

implementation detail of the httplib2 transport

Indeed. I left it in there to avoid breaking people who had used the private methods and passed http.request. As far as the public interface, no one should be passing http.request instead of http.

@dhermes so right now the only times this occurs that I can tell is when the transport itself passes orig_request in during the replacement request function.
I'm leaning towards the "http object" being completely opaque to all of oauth2client except for the transport. So in the case of httplib2 transport there's two valid http objects, but for urllib3 that might not be the case. :)

so right now the only times this occurs that I can tell is when the transport itself passes orig_request in during the replacement request function.

Yes. I really wanted to eliminate that in the unit tests but couldn't find a good way, though I toyed around with making a __call__-able class for those wrapped http.request values.

Thank you for creating this issue, however, this project is deprecatedand we will only be addressing critical security issues. You can read moreabout this deprecation here.
If you need support or help using this library, we recommend that you ask yourquestion on StackOverflow.
If you still think this issue is relevant and should be addressed, pleasecomment and let us know!


Active Defenses Table - Add Link to option

Add link to:
Skill, Technique, Spell, Weapon, Power/Talent
Additional fields
Modifier and reason for modifier
auto-calculate defense.

Completed by duplicate issue


建议升级插件的webpack

warning "vue-cli-plugin-cube-ui ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=3".
warning "vue-cli-plugin-cube-ui ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>= 3".
warning "vue-cli-plugin-cube-ui ><EMAIL_ADDRESS>has unmet peer dependency "babel-plugin-transform-modules@>= 0.1.1".

本机安装的webpack不是>=3的吗

这个错误很奇怪，好像是提示我没有装全局的webpack，我先关闭


Initial Documentation

Added some initial documentation for types and functions
Set up CI to build webpage (see langfzac.github.io/NbodyGradient/dev/)

Once this is merge, we just need to point the deploydocs function to ericagol/NbodyGradient (rather than my fork). Also, need to add a link in the README.

Great!


SidekiqScheduler::Manager enormous inspect output

Trying to inspect an instance of SidekiqScheduler::Manager produces around 5k lines of output on our system because it holds references to a bunch of other complex objects and eventually starts printing large chunks of internal sidekiq and rails objects.
This is doubly annoying because with debug-logging enabled on sidekiq, the SidekiqScheduler::Manager instance is inspected/logged at sidekiq startup.
It's easy enough to monkey-patch with something like:
module SidekiqScheduler
  class Manager
    def inspect
      "SidekiqScheduler::Manager"
    end
  end
end

But there should probably be some debugging information included, and I don't know what values are worth logging here.

I am not able to share this output, as the resulting dump of ruby objects includes a great deal of sensitive information about our code base, including e.g. our redis password. It is 2MB of text, so it is too large for me to manually redact sensitive information.
You should be able to reproduce for yourself by running bundle exec sidekiq -v on a sidekiq setup with sidekiq-scheduler. Any sidekiq version after 7.0.7 (https://github.com/sidekiq/sidekiq/issues/5822 is required) should print the config object when started with -v and will thus trigger the inspect of the scheduler-manager.

I've had this same issue also because Sidekiq would print Sidekiq.options and the scheduler instance is in those options.
My notes say the problem is with the rufus scheduler having an array of rufus jobs which all have a reference to the rufus scheduler.
We fixed this by doing this in the initializer.
module SidekiqScheduler
  class Scheduler
    def inspect
      "#<#{self.class}:0x#{object_id.to_s(16)}>"
    end
  end
end


Add basic add and remove

Install redux;
Add add and remove book functions

When I am about to do second work, I realized I have been doing second day work and skip first day work. Sorry for the reviewer, I think I opened the wrong link and do the work.


Create python_submit.txt

Good Job!!!   @iphysresearch
Python homework:

Total questions: 7
Correct answers: 2
Score: 28.00%

Good Job!!!   @iphysresearch
Python homework:

Total questions: 107
Correct answers: 2
Score: 1.00%

Numpy homework:

Total questions: 9
Correct answers: 0
Score: 0%


Fix errors becoming traps in wasi-http

This commit fixes an issue with errors in the wasmtime-wasi-http crate by using the trappable_error_type bindgen configuration option in the same manner as other WASI interfaces in the wasmtime-wasi crate. Unfortunately due to coherence the TrappableError<T> type itself could not be used but it was small enough it wasn't much effort to duplicate.
Closes #8269

Redirecting to @elliottt


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/695 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit 1722114:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-20-06-58-23 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1722114:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-20-06-58-23 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


new class and auto set document class

???

new a class,and this auto make as document class ,sometimes.


Reimplementation/mixpanel tracking

mixpanel browser tracking

This looks good to me. @vgrichina any concerns?

This looks good to me. @vgrichina any concerns?


bugfix: DeDuplicate case with null character string or white space.

Ⅰ. Describe what this PR did
bugfix: DeDuplicate case with null character string or white space.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1276 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1276      +/-   ##
==========================================
+ Coverage   15.59%   15.61%   +0.02%
==========================================
  Files         173      173
  Lines       10819    10822       +3
==========================================
+ Hits         1687     1690       +3
  Misses       9013     9013
  Partials      119      119

Impacted Files
Coverage Δ

pkg/utils/utils.go
77.53% <100%> (+0.49%)
:arrow_up:

Is what we mentioned reasonable for you? @soarpenguin
Please feel free to share with us if you have any thought. Otherwise, I am afraid we are going to close it.
While I think we still encourage you to enjoy the hacking. What you attemped to do is very valuable to Pouch Project. Thanks a lot.


Correction for raw affiliation Ethical approval: This study was reviewed by the American Institutes for Research Institutional Review Board and qualified for exempt status because it involved very minimal or no risk to study subjects.; Other disclosures: None reported.

Correction needed for raw affiliation Ethical approval: This study was reviewed by the American Institutes for Research Institutional Review Board and qualified for exempt status because it involved very minimal or no risk to study subjects.; Other disclosures: None reported.
raw_affiliation_name: Ethical approval: This study was reviewed by the American Institutes for Research Institutional Review Board and qualified for exempt status because it involved very minimal or no risk to study subjects.; Other disclosures: None reported.
new_rors:
previous_rors: 00490n048
works_examples: W2898523464
contact: d85d175f7f46e9ceb577d0cdaa41c901:6651c8757ec8dd @ air.org

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


Proposal: Change default key-value separator from :: to =

I think this is more common. What do you think about that?

With this change, you would also need to adjust some of the tests, particularly those defined here:
https://github.com/apache/incubator-tamaya-sandbox/blob/master/collections/src/test/resources/META-INF/javaconfiguration.properties#L38-L56 along with the relevant javadocs in collections/src/test/java/org/...

Thanks for feedback.
This topic is currently under discussion here: https://issues.apache.org/jira/browse/TAMAYA-345?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=16538609

This got changed from '::' to ':' based on the conversation linked at the top, and implemented in https://github.com/apache/incubator-tamaya-extensions/commit/9f38f77020a057145aa246f2ff6f121adf7a6727 .  I'm going to go ahead and close this PR in favor of that commit.


17--HTMLrats

Checklist would be nice...

More colors on your specs would be helpful in determining where the boxes are nesting...

Please delete your bower_components/ directory from src/tests/.


Custom plugin bottom dock signals won't fire

Tested versions

Reproducible in 4.2.2.stable.official

System information
macOS Sonoma 14.4.1 (23E224)
Issue description
Function connected to button press signal doesn't trigger when control is instanced in a bottom docked plugin.
Steps to reproduce
Basically:

Create an empty project
Create a new plugin from Settings
Create a Control named Dock with a button inside
Connect button pressed signal to a Dock function that prints "OK"
Configure the plugin to show in bottom dock

When executing the scene on its own, pressing the button prints OK. When pressing the button in the context of the bottom dock, the function doesn't get called (no OK prints).
The Minimal reproduction project shows this.
Minimal reproduction project (MRP)
https://github.com/pl7y/godot-plugin-bottom-dock-issue

Looks like dock.gd needs to be a @tool script, see the warning in the docs.

You are right, issue fixed, thank you so much!!!
I committed the @tool addition into the repo and added a minimal readme to point here.
Anyway it's not infrequent to spot  this kind of issues, caused by assumptions in docs which are not enforced in editor (e.g. scaled collision boxes) which drain lots of time debugging. One might wonder if there is a way to enforce this warnings as runtime checks instead.
Thanks again!


Salesforce Security Review

I see that the homepage says that this app (DLRS) has passed Salesforce's Security Review. Is there a way to get confirmation that it has passed the Security Review? I don't see the app being listed on the AppExchange and when I opened an Service Request with Salesforce, they are saying that it hasn't passed the Security Review. It would be great if you can let me know how I can verify that it has passed the Security Review.

I suppose @afawcett should answer this with certainty, but I know that DLRS is an Aloha package, it was certified back at v1.2.
Let me know if that helps.

Thanks for the comment @wes1278 . I'm not sure if certifying it as an Aloha package would mean that it has passed Salesforce's Security Review. The reason for my ask is that Salesforce Support is saying that it hasn't passed the Security Review. I would like to know if there is another way for me to verify that it has passed the Security Review.

As @wes1278 says it was passed in v1.2, but not later versions, i need to get round to resubmitted it, but DF prep is taking its toll. So i assume Salesforce is saying no to the current versions? I'll keep this case open until its been passed through review again for the latest version. You do only get Aloha if you've passed review, and you can now see under Installed packages if a package is exempt from Limits (which implies Aloha). Aloha however sticks for later versions which may not have been through review. Hope this clarifies, i'll get started submitting latest version this weekend hopefully. :+1:

Thanks @afawcett for the explanation. Please let me know once the latest version has passed the Security review.
Another related question: Is there a reason this package is not listed on the AppExchange? If it is listed, it would automatically mean that it has passed the Salesforce's Security Review, right?

Latest version 1.24 has passed security review, you can see the listing here.

Thanks for the update
On Sun, Nov 29, 2015 at 4:47 AM, Andrew Fawcett<EMAIL_ADDRESS>wrote:

Latest version 1.24 has passed security review, you can see the listing
here
https://appexchange.salesforce.com/listingDetail?listingId=a0N3000000B45gWEAR.
—
Reply to this email directly or view it on GitHub
https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/225#issuecomment-160398916
.


Application or extension failure

Steps to reproduce
The application closes or restarts
Expected behavior
The open the sleeve without closing or restarting it
Actual behavior
I enter the aplication, but when i try to open a manga from tumangaonline and lectormanga, the application closes or restarts
Crash logs
No response
Mihon version
0.17.1
Android version
Android 9
Device
Samsung j4+
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.17.1.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Send the crash log in the Mihon Discord support channel instead, this issue request provides no information about the actual crash


unpin a flexcomp at runtime

Hi,
I'm a student and I'm trying to use MuJoCo for creating a gymnasium environment for grasping deformable objects.
I'm looking for some help with unpinning flexcomp at runtime.
Here is a model which explains my question:

minimal XML
<mujoco model="insole">
	<compiler strippath="true" meshdir="meshes/" />
	<extension>
		<plugin plugin="mujoco.elasticity.solid" />
	</extension>
	<worldbody>
		<light pos="0.3 0 1.5" dir="0 0 -1" directional="true" />
		<!-- <geom name="floor" pos="0 0 -0.1" size="0 0 0.05" type="plane"/> -->
		<body name="insole">
			<flexcomp name="insole" pos=".12 -.05 .462" mass="1" type="gmsh" file="insole.msh" rgba=".1 .9 .1 1">
				<edge equality="true" />
				<pin id="22 25 27 26" />
				<plugin plugin="mujoco.elasticity.solid">
					<config key="young" value="200000.0" />
					<config key="poisson" value="0.2" />
					<config key="damping" value=".005" />
				</plugin>
			</flexcomp>
		</body>
	</worldbody>
</mujoco>

In this environment, a robot arm is used to grab a deformable insole. A few vertices in the latter part of the insole is initially fixed on a platform. After a certain simulation time, the platform is removed and the insole is allowed to fall freely for a while.
I would like to ask if there is any way to unpin these vertices after the platform is removed at runtime.
Here is a screenshot of the current environment:

MuJoCo Version: 3.1.6
OS: Ubuntu 22.04.4 x86_64
Using Python binding

Hi, you can't really unpin since pins prevent the creation of DOFs during model compilation. I can see two ways to achieve this:

Not pinning to start with, but having equality constraints that you switch off
Use the new model editing API and change the flex from pinned to unpinned in mjsFlex, then call mj_recompile

Thank you for your response, that helps a lot.
I have tried the first approach that works pretty good for my application now.
As for the second one, in mjsFlex I could not find the pinning property.

You are right, pinning is an option of FlexComp, so it's not part of mjsFlex. The equivalent operation would be to remove the joint from the bodies that correspond to the pinned vertices.


Convert MinValue's and MaxValue's to properties

To support System.Numerics.IMinMaxValue. Obviously, this is a breaking change.

See #362


[nng] Update to v1.5.1

Describe the pull request

What does your PR fix?
Update to v1.5.1.

Which triplets are supported/not supported? Have you updated the CI baseline?
All. Yes.

Does your PR follow the maintainer guide?
Yes.

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
<Yes / I am still working on this PR>

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@myd7349, thanks for your PR, have you tested these features locally?

@myd7349, thanks for your PR, have you tested these features locally?

Hi! @JonLiu1993 Thanks for your help and sorry for the long delay.
I have tested all features with:

x86-windows
x86-windows-static
x64-windows
x64-windows-static

Thanks for the help!


Adding TS0044 _TZ3000_uaa99arv

New device class that is adding the secret 0xe000 tuya cluster.
Fixes #1352

Codecov Report

Merging #1354 (f1c538b) into dev (23a1669) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev    #1354   +/-   ##
=======================================
  Coverage   81.00%   81.01%
=======================================
  Files         217      217
  Lines        6017     6020    +3
=======================================
+ Hits         4874     4877    +3
  Misses       1143     1143

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0044.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.009%

Covered Lines:
4877

Relevant Lines:
6020

💛  - Coveralls


[ FEAT ] : Add Login and Signup Page

What does this PR do?
This PR closes #198, which aim is to enhance the Auth Page.
What issues does this PR fix or reference?

Leverage React-hook-form for form management
Adding Zod for client side validations of the input
Enhancing the UI by integrating modern UI and re-usable components

Sure @codekansas

@codekansas can we use tailwind css library, instead of using seperate css module?

yes, tailwind is fine, if we can make it work well with react typescript - cc @chennisden

yes, tailwind is fine, if we can make it work well with react typescript - cc @chennisden

yeah i've done this before, tailwind plays perfectly fine with react ts

@codekansas, I've added credentials + google + github provider in the Client. If we are currently supporting github provider means, we can disable the rest of the things, in future we may need this auth credentials. Your thoughts on these ?

this looks great!! let's merge this


[Site Request]  lbry.tv

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dlcc version 2020.09.23-2
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: https://lbry.tv/@redicetv:1/upside-down-in-clown-world-order-ff-ep93:b -> Unsupported

Single video: https://cdn.lbryplayer.xyz/api/v3/streams/free/no-go-zone-louisville-riots-kyle-rittenhouse-attorneys-release-video/f1bb4bc09c1ba59d035fb552a5afbc74e9993481/919210 -> Works

Description

Hi, can you please add the site lbry.tv?
When using the original link:  https://lbry.tv/@redicetv:1/upside-down-in-clown-world-order-ff-ep93:b, it doesn't work. I get this error:
D:>youtube-dlc https://lbry.tv/@redicetv:1/upside-down-in-clown-world-order-ff-ep93:b
[generic] upside-down-in-clown-world-order-ff-ep93:b: Requesting header
WARNING: Falling back on generic information extractor.
[generic] upside-down-in-clown-world-order-ff-ep93:b: Downloading webpage
[generic] upside-down-in-clown-world-order-ff-ep93:b: Extracting information
[generic] b1fad34d1f0446f6f8e8155ac5e27f04d6347005: Requesting header
WARNING: Falling back on generic information extractor.
[generic] b1fad34d1f0446f6f8e8155ac5e27f04d6347005: Downloading webpage
[generic] b1fad34d1f0446f6f8e8155ac5e27f04d6347005: Extracting information
ERROR: Unsupported URL: https://lbry.tv/$/embed/upside-down-in-clown-world-order-ff-ep93/b1fad34d1f0446f6f8e8155ac5e27f04d6347005
BUT When using F12 in Chrome, and I check for the actual file, it can be found, the link for the video: https://cdn.lbryplayer.xyz/api/v3/streams/free/no-go-zone-louisville-riots-kyle-rittenhouse-attorneys-release-video/f1bb4bc09c1ba59d035fb552a5afbc74e9993481/919210
This link CAN be downloaded with youtube-dl.
D:>youtube-dlc https://cdn.lbryplayer.xyz/api/v3/streams/free/no-go-zone-louisville-riots-kyle-rittenhouse-attorneys-release-video/f1bb4bc09c1ba59d035fb552a5afbc74e9993481/919210
[generic] 919210: Requesting header
[download] Destination:<PHONE_NUMBER>10.unknown_video
Could you please add support so it actually works with the original website, lbry.tv?

Might want to go ahead and add it as Odysee since that's the new interface/site name they're changing to.


az postgres flexible-server list-skus returns duplicated and borked supportedIops property

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az postgres flexible-server list-skus
Describe the bug

az postgres flexible-server list-skus returns duplicated and borked supportedIops property.
To Reproduce

az postgres flexible-server list-skus --location francecentral

This is the head of returned json, notice the supportedIOPS property AND the borked supportedIops property:
[
  {
    "geoBackupSupported": true,
    "status": "Default",
    "supportedFlexibleServerEditions": [
      {
        "name": "Burstable",
        "status": "Available",
        "supportedServerVersions": [
          {
            "name": "11",
            "status": "Available",
            "supportedVcores": [
              {
                "name": "Standard_B1ms",
                "status": "Available",
                "supportedIOPS": 640,
                "supportedIops": null,
                "supportedMemoryPerVcoreMb": 2048,
                "vCores": 1
              },

This will prevent tools like pwsh ConvertFrom-Json from working:
PS /home/vagrant/Projects/pulumi-typescript-azure-native-postgres> az postgres flexible-server list-skus `
>>   --location francecentral `
>>   | ConvertFrom-Json `
>>   | Select-Object -Property zone
WARNING: For prices please refer to https://aka.ms/postgres-pricing
ConvertFrom-Json:
Line |
   3 |    | ConvertFrom-Json `
     |      ~~~~~~~~~~~~~~~~
     | Cannot convert the JSON string because it contains keys with different casing. Please use the -AsHashTable switch instead. The key that was attempted to be added to the existing key 'supportedIOPS' was 'supportedIops'.

Expected behavior

The returned JSON should not container borked properties.
Environment summary

azure-cli                         2.39.0
Additional context

route to CXP team

@rgl I am able to reproduce this issue and checking internally with the products team.

This was fixes long time ago. @yonzhan , this can be closed now.


Only try to search for the ca bundle on PHP 5.5

Can you add a changelog entry?

Yeh. I'll send a PR in bulk with all the change log entries at the end to avoid merge conflicts and wasted time. :)


Bootstrap 3 dependency?

I assume this is required? It isn't in the package.json

@project707, it is, but perhaps it would be best to add it to peerDependencies. I don't want to lock people into a specific bootstrap package. For example, developers might want to use bootstrap-sass over straight bootstrap.

Makes sense. I guess it might be worth adding some note of what it depends on and how to include/import in the readme. Closing.


OAK-8902 | Getting list of blob ids under a specific path

Could you create a PR for https://github.com/oak-indexing/jackrabbit-oak instead of https://github.com/apache/jackrabbit-oak ? That way, we would see comments from codacy as well, similar to  https://app.codacy.com/gh/oak-indexing/jackrabbit-oak/pullRequest?prid=5022787


xarray can open a nc file with open_dataset, but fails to load this nc file with load

What is your issue?
Recently, I have downloaded chla data from copernicus marine service, and tried to regrid it with xarray. The sad thing is that the data always goes wrong in the load phase.  I have checked that variables in test dataset could be plotted normally. I do know what happen to this. Any advice is appreciated.
The test code：
import xarray as xr
ds = xr.open_dataset("chla201601.nc")
ds.load()

Test dataset:
chla201601.zip
Error information:
Details

---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Cell In[3], line 1
----> 1 ds.load()

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/dataset.py:880](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/dataset.py#line=879), in Dataset.load(self, **kwargs)
    878 for k, v in self.variables.items():
    879     if k not in lazy_data:
--> 880         v.load()
    882 return self

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/variable.py:981](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/variable.py#line=980), in Variable.load(self, **kwargs)
    964 def load(self, **kwargs):
    965     """Manually trigger loading of this variable's data from disk or a
    966     remote source into memory and return this variable.
    967
   (...)
    979     dask.array.compute
    980     """
--> 981     self._data = to_duck_array(self._data, **kwargs)
    982     return self

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/namedarray/pycompat.py:134](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/namedarray/pycompat.py#line=133), in to_duck_array(data, **kwargs)
    131     return loaded_data
    133 if isinstance(data, ExplicitlyIndexed):
--> 134     return data.get_duck_array()  # type: ignore[no-untyped-call, no-any-return]
    135 elif is_duck_array(data):
    136     return data

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py:837](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py#line=836), in MemoryCachedArray.get_duck_array(self)
    836 def get_duck_array(self):
--> 837     self._ensure_cached()
    838     return self.array.get_duck_array()

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py:831](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py#line=830), in MemoryCachedArray._ensure_cached(self)
    830 def _ensure_cached(self):
--> 831     self.array = as_indexable(self.array.get_duck_array())

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py:788](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py#line=787), in CopyOnWriteArray.get_duck_array(self)
    787 def get_duck_array(self):
--> 788     return self.array.get_duck_array()

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py:651](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py#line=650), in LazilyIndexedArray.get_duck_array(self)
    647     array = apply_indexer(self.array, self.key)
    648 else:
    649     # If the array is not an ExplicitlyIndexedNDArrayMixin,
    650     # it may wrap a BackendArray so use its __getitem__
--> 651     array = self.array[self.key]
    653 # self.array[self.key] is now a numpy array when
    654 # self.array is a BackendArray subclass
    655 # and self.key is BasicIndexer((slice(None, None, None),))
    656 # so we need the explicit check for ExplicitlyIndexed
    657 if isinstance(array, ExplicitlyIndexed):

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/backends/netCDF4_.py:100](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/backends/netCDF4_.py#line=99), in NetCDF4ArrayWrapper.__getitem__(self, key)
     99 def __getitem__(self, key):
--> 100     return indexing.explicit_indexing_adapter(
    101         key, self.shape, indexing.IndexingSupport.OUTER, self._getitem
    102     )

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py:1015](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/core/indexing.py#line=1014), in explicit_indexing_adapter(key, shape, indexing_support, raw_indexing_method)
    993 """Support explicit indexing by delegating to a raw indexing method.
    994
    995 Outer and[/or](http://localhost:8888/or) vectorized indexers are supported by indexing a second time
   (...)
   1012 Indexing result, in the form of a duck numpy-array.
   1013 """
   1014 raw_key, numpy_indices = decompose_indexer(key, shape, indexing_support)
-> 1015 result = raw_indexing_method(raw_key.tuple)
   1016 if numpy_indices.tuple:
   1017     # index the loaded np.ndarray
   1018     indexable = NumpyIndexingAdapter(result)

File [/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/backends/netCDF4_.py:113](http://localhost:8888/usr/miniforge3/envs/xesmf_env/lib/python3.12/site-packages/xarray/backends/netCDF4_.py#line=112), in NetCDF4ArrayWrapper._getitem(self, key)
    111     with self.datastore.lock:
    112         original_array = self.get_array(needs_lock=False)
--> 113         array = getitem(original_array, key)
    114 except IndexError:
    115     # Catch IndexError in netCDF4 and return a more informative
    116     # error message.  This is most often called when an unsorted
    117     # indexer is used before the data is loaded from disk.
    118     msg = (
    119         "The indexing operation you are attempting to perform "
    120         "is not valid on netCDF4.Variable object. Try loading "
    121         "your data into memory first by calling .load()."
    122     )

File src[/netCDF4/_netCDF4.pyx:4981](http://localhost:8888/netCDF4/_netCDF4.pyx#line=4980), in netCDF4._netCDF4.Variable.__getitem__()

File src[/netCDF4/_netCDF4.pyx:5953](http://localhost:8888/netCDF4/_netCDF4.pyx#line=5952), in netCDF4._netCDF4.Variable._get()

File src[/netCDF4/_netCDF4.pyx:2113](http://localhost:8888/netCDF4/_netCDF4.pyx#line=2112), in netCDF4._netCDF4._ensure_nc_success()

RuntimeError: NetCDF: HDF error

Main package information:

xarray  2024.9.0
numpy  2.0.2
netCDF  4 1.7.1
h5netcdf  1.4.0
python  3.12.7

The ram information:
total        used        free      shared  buff/cache   available
Mem:           8.3Gi       2.1Gi       5.3Gi        45Mi       1.2Gi       6.2Gi
Swap:          3.9Gi          0B       3.9Gi

@onion5376 This example works perfectly fine on my linux-box with the dependencies you've given. It seems there is more involved in your real application. Please give additional information as you can. Thanks!

"HDF error" doesn't give a lot to go on, and could mean your local copy of the file is corrupted (try deleting and re-downloading), that your version of HDF5 is too old for the file (try re-installing/updating HDF5/libhdf5 in your environment; in the meantime, the HDF5/libhdf5 version should be included in the "Main package information" section, if you can find it), or that the installed version of HDF5 doesn't match what was used to compile libnetcdf/netcdf-c (that's probably a different error, but you can try re-installing/updating libnetcdf/netcdf-c; in the meantime, nc-config --version has a version for the "Main package information" section).
ncdump -h chla201601.nc and h5dump -H chla201601.nc might give more detail in their error messages; you may want to redirect the output to a file, especially if you remove the flag so the command prints the data as well.
Does the engine matter?  Does one of the following succeed and the other fail?
ds = xr.load_dataset("chla201601.nc", engine="netCDF4")
ds = xr.load_dataset("chla201601.nc", engine="h5netcdf")

Possibly the hardest to debug would be if the netCDF4 file uses a compression filter not available on your system.  I think h5dump will include the list of filters, ncdump might too if you ask nicely, but I'm not sure how to check which ones are available on your system.  If this is a system python environment, are you able to create a conda/miniconda environment to run this script in?


Custom scanner analysis

The scanner function if customizable.
It takes a path to a folder containing:

analysis.py python code used to scan a single image
*requirements.txt' any library that the analysis.py module uses
any other files needed to the scanning hase. (e.g. software.json)

'$ docker-analyser up --lambda-package=FILE`
The sctipt allow to import the package within the /deploy folder.
The scanner is built reading the imported package.


Improvements based on v21.0.1 (and other) patch releases

[ ] Show release version even on inner pages. While we show it in the footer of the main menu, once we are on a specific item we don't see it. Since we do multiple versions in patch releases, this will be useful.
[ ] Remove cobra docs sync check for patch releases
[ ] Fix link to docker actions workflow for >= v21

When the tool creates a pull request, it should include a link to the Release Issue in the pool request's main comment. Examples for pull requests that do not have a link back to the Release Issue:

https://github.com/vitessio/vitess/pull/17317
https://github.com/vitessio/vitess/pull/17324


There was an ok_or() that should have been an ok_or_else() that Clippy caught.

This will hopefully make "cargo clippy" more useful for the next person.

@cuviper These diffs are a bit gratuitous but I think they'll be a net positive. I chose to silence Clippy rather than change working code any more than necessary. Hopefully cutting down the Clippy noise will help the next person.

bors r+


developing with 5.0.x-dev

Hi there, how do I start implementing a solution on top of this version of the framework? 5.0.x-dev
When use composer install and list it under require-dev, I don't see a file named 'artisan' available. Am I missing something?

You need to clone the laravel/laravel repo, and checkout the "develop" branch, for now. That branch will become the master very soon.


How to view replays

I feel dumb asking this but I've been shuffling files around for hours and the replays copied from the server aren't appearing in the replay viewer. Is there a guide on how I'm supposed to copy things and what goes where? I'd be happy to make a PR with a README for this once everything is explained :)

Hi.
Can you attach one of the generated files so I can test it, just to make sure the files aren't corrupt?

by default you'll find the replay files under $server_folder/replay_recordings,
and you have to copy the file into the replay_recordings folder that is on your client (%appdata%/.minecraft/replay_recordings)
🤔

you can also get the recordings with the command /replay file [player/region] upload [filename] and the mod should respond with a web link to download the file

copy the file into the replay_recordings folder that is on your client

I did try that so maybe sounding like corruption? Would certain mods cause issues or break things? I couldnt find any sign of issues in logs.
replays.zip

you can also get the recordings with the command /replay file [player/region] upload [filename] and the mod should respond with a web link to download the file

Also i didnt realize the upload command meant upload to a file service for download. I thought it meant uploading local replays to the server for some reason so thanks for clarification :)

I just copied the file into my replay viewer and it's showing up in the list fine - are you making sure to take the file out of the "player/dotmrjosh/" folder before copying it to the "replay_recordings" folder?

Hmm i can't recreate the issue now. Before it would generate a folder labeled "recordings_83762945" (the numbers would be random). Do you have a process for checking if a recording is corrupted that I could use to come back with later?

It's generating that folder because it's a temp folder used for storing the replay data before it gets compressed into the replay file, meaning if it appears like that it means it's either currently in the process of compressing the recording to the .mcpr format or it was interrupted with a server shutdown.
Currently the way of checking if a replay is corrupted is by looking at the .mcpr file and opening it with a file archiver like 7-zip or winrar to ensure that it internally contains "recording.tmcpr" and "metaData.json".
Also as I have previously stated the replay you sent seems to work fine in the replay viewer, so I would just like to confirm that it works on your end if you move the file from "server_folder_here/replay_recordings/player/dotmrjosh/filenamehere.mcpr" to "minecraft_client_folder_here/replay_recordings/filenamehere.mcpr"

Yes, sorry if I didn't clarify its working on my end now. My current guess then is that the server shutdown too soon before the recording was fully saved but thanks for the insight on how to debug recordings. Am happy to close this for now and will update if something resurfaces. Thanks for your time.


Keyboard navigation for the component browser

Would be great for quicker workflows if one could use arrow and tab keys to navigate the component dropdown list.

Closing due to impending component browser rewrite


Question/feature request: Changelog generation for multiple NX projects?

I have an application in an NX monorepo. The folder structure looks something like this:

my-application

feature-a
feature-b
feature-c
feature-d
shell-application

Where each feature is a project containing a project.json in which we could add the version target.
The problem is that every feature is quite small and I just want to generate a changelog for the entire my-application, I don't want individual changelogs for each small feature. Is this possible at the moment with semver?

@zeroregard For this use case, I would recommend using the sync-mode with the --skipProjectChangelog option, so you have only one root changelog with everything.

That's the thing though - I have several applications in this mono-repo, and these applications have their own changelogs. It's just that one of the applications has several projects.

Yes, this is exactly what i expected as well. I have multiple aplication projects in monorepo and several feature libraries used from that applications. I want changelog from libraries in changelog of application which depends on that libraries.
Option --trackDeps just makes:
Dependency Updates
<lib> updated to version #.#.#

which is not much informational.


Changed all deployment labels

Changed all deployment labels

Hi Isi,
You have missed out the references on the front page. Can you change these then i can merge.
Adam

Resolve #8


Fix typo

Http/Https -> HTTP/HTTPS

@mbender-ms
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Add Develop->Integrations section

This page aims to add the integrations section

Just a couple minor things. As far as the icons and such for these pages, I've created a separate ticket to circle back to the design of these pages. So once these minor things are addressed, we can merge this and address that stuff later

All fixed. Let's merge this and then we can improve the design in a new PR


Cloud Run pulumiLabels mapped non-uniquely to terraform_labels

What happened?
Cloud Run service deployment fails with instance state: internal: Pulumi property 'pulumiLabels' mapped non-uniquely to Terraform attribute 'terraform_labels' (duplicates Pulumi key 'terraformLabels').
Example
gcp.cloudrun.Service(
    resource_name=f"test-gcr",
    args=gcp.cloudrun.ServiceArgs(
        name="test",
        location="europe-west2",
        template=gcp.cloudrun.ServiceTemplateArgs(
            spec=gcp.cloudrun.ServiceTemplateSpecArgs(
<EMAIL_ADDRESS>                containers=[
                    gcp.cloudrun.ServiceTemplateSpecContainerArgs(
                        image="gcr.io/example",
                        resources=gcp.cloudrun.ServiceTemplateSpecContainerResourcesArgs(
                            limits={
                                "memory": f"512Mi",
                                "cpu": "1",
                            }
                        ),
                    )
                ],
                timeout_seconds=60,
                container_concurrency=30,
            ),
            metadata=gcp.cloudrun.ServiceTemplateMetadataArgs(
                annotations={
                    "autoscaling.knative.dev/maxScale": "100",
                },
            ),
        ),
        autogenerate_revision_name=True,
        metadata=gcp.cloudrun.ServiceMetadataArgs(
            labels={"env": "dev"},
            annotations={
                "run.googleapis.com/ingress": "all",
            },
        ),
        traffics=[
            gcp.cloudrun.ServiceTrafficArgs(
                percent=100,
                latest_revision=True,
            )
        ],
        project="gcp-project",
    ),
)

Output of pulumi about
CLI Version      3.111.1
Go Version   go1.22.1
Go Compiler  gc

Plugins
NAME    VERSION
docker  4.5.1
gcp     7.14.0
python  unknown

Host
OS       ubuntu
Version  22.04
Arch     x86_64

Found no pending operations associated with travelshift/dev

Backend
Name           pulumi.com
Token type     personal

Dependencies:
NAME                                     VERSION
annotated-types                          0.6.0
async-timeout                            4.0.3
backcall                                 0.2.0
blacken-docs                             1.16.0
bump-pydantic                            0.7.0
Cerberus                                 1.3.5
cmapy                                    0.6.6
contourpy                                1.2.0
cycler                                   0.12.1
flake8                                   7.0.0
fonttools                                4.50.0
fqdn                                     1.5.1
get-country-street-networks              0.10.0
google-api-python-client-stubs           1.23.0
google-cloud-monitoring                  2.18.0
httpcore                                 0.17.3
isoduration                              20.11.0
jsonpointer                              2.4
jupytext                                 1.16.1
kiwisolver                               1.4.5
knowledge-graph                          0.1.0
lazy-object-proxy                        1.10.0
memray                                   1.10.0
munch                                    2.5.0
mypy                                     1.7.1
mypy-boto3-s3                            1.34.65
mypy-boto3-sns                           1.34.44
nbqa                                     1.7.1
pandas-stubs                             <IP_ADDRESS>321
pickleshare                              0.7.5
pillow                                   10.2.0
pip-api                                  0.0.30
pipreqs                                  0.4.13
playwright                               1.42.0
pre-commit                               3.6.2
psycopg-binary                           3.1.17
psycopg-pool                             3.2.1
pubsub-cleaner                           0.5.2
pydantic_core                            2.10.1
pylint                                   3.1.0
pyppeteer                                1.0.2
pyrsistent                               0.19.3
pytest-unordered                         0.6.0
pyupgrade                                3.15.1
requirementslib                          3.0.0
ruff                                     0.3.3
setuptools-scm                           8.0.4
types-google-cloud-ndb                   <IP_ADDRESS>
types-protobuf                           <IP_ADDRESS>40311
types-psutil                             <IP_ADDRESS>40316
types-PyYAML                             <IP_ADDRESS>40311
types-requests                           <IP_ADDRESS>40311
types-tqdm                               <IP_ADDRESS>
types-urllib3                            <IP_ADDRESS>
types-xmltodict                          <IP_ADDRESS>
uri-template                             1.3.0
vcrpy                                    5.1.0
webcolors                                1.13
wheel                                    0.38.4

Additional context
This happens with pulumi-gcp versions from 7.11.0 to 7.14.0.
Rolling back to 7.9.0 fixes the issue.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @xSAVIKx - thank you for filing this bug. We'll take a look as soon as we can.

we're also getting hit with this since we upgrade pulumi from 3.89.0 to 3.111.1 and pulumi-gcp from 6.67.0 to 7.14.0. Since this is blocking us from upgrading, would be good to get addressed soon!

Ok, reproed the issue in https://github.com/pulumi/pulumi-gcp/pull/1854. Looks like this is already fixed in tf-bridge master in https://github.com/pulumi/pulumi-terraform-bridge/pull/1757. I've kicked off a release and will update here once we pick it up.

https://github.com/pulumi/pulumi-gcp/releases/tag/v7.14.1 released and has a fix for the issue. LMK If you are still having issues with this.

I've had to re-create the env from scratch and migrated to cloudrunv2 package, so don't have an env to test it out. Hopefully it's gonna be fixed for others 😄


DM-40813: Refactor prepuller storage layer

Model the new separation between builder objects, services, and the Kubernetes storage layer with the prepuller, which is the simplest. Add a new PrepullerBuilder that constructs the pod that the prepuller uses, and have it use that and the PodStorage storage layer directly, so it no longer needs K8sStorageClient.
Introduce a new MetadataStorage layer, which is resposible for getting metadata about the running pod from the Kubernetes downward API, and use it for namespace and object reference information for the prepuller pods.
Stop using the namespace prefix for labs as the namespace for prepuller pods and always use the namespace from the downward API. Make the downward API information mandatory; there's really no reason not to have it.
Stop adding Argo CD annotations to the prepuller pods. Since they are children of the controller pod, they don't need any.

Yeah, the idea is that we were previously getting the controller's namespace from the magic file in its service account, but (a) we were using downward API already for everything else, and (b) this assumes that there will always be a service account available and the service account metadata will include the namespace, which is likely but not guaranteed. Since we were doing downward API anyway, I just added the namespace to the downward API specification for the controller pod and then did everything the same way.
The test suite changes are because previously we had a fallback to put the prepuller pods in userlabs (which didn't really make sense) if no service account was available, and we had fallbacks for omitting the owner reference if downward API data wasn't available. But there's no reason for it to not be available, so I just made it use downward API unconditionally, which required adding it to a few more tests.


Working great for me, but no run button for another user

I hope that all my questions and issues are useful testing rather than just super annoying.
I've been using Mass Action Scheduler very successfully at several orgs, and this week showed another user how to use a config I had set up.  He doesn't see the run button, even though he has the same user profile that I do.  I assume there's a Visualforce component somewhere that he needs access to, but I can't figure out what and where?
Thanks so much,
Anna

Hi @annacrotty,
I'm glad that the app is working well for you!
The "Run" button is just custom button added to the Mass Action Configuration page layout. The only thing I can think of if the user doesn't see the button is that they are not viewing the the correct page layout, which is strange because there should only be one layout and even more strange if you see it and they don't.
Could you provide screen shots of what you see and what the other user sees?
To confirm, the other user is in Lightning Experience and not Classic, correct?
Thanks!

I think I see the problem - it looks like he sent me a screen shot that didn't include the whole screen and so I didn't realize that he hadn't chosen a configuration yet...my apologies!
I am planning to write up a blog post on all the cool things we're doing with it.  I think people haven't appreciated how earth shakingly awesome it is to be able to efficiently deal with fringe cases without having to touch every record in a batch job!

Thanks for the update @annacrotty. Glad you were able to figure it out =)
And thank you very much for the kind feedback. I look forward to reading about the great solutions you're able to build out with Mass Action Scheduler =)


Support more browsers

Feature Request
Is your feature request related to a problem? Please describe:
Currently we only support very recent browsers.

Describe the feature you'd like:
The support may be extended by shipping polyfills for legacy browsers.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Reference: https://www.smashingmagazine.com/2018/10/smart-bundling-legacy-code-browsers/
Note that it would be better to decide the polyfill at client side. See https://github.com/browserslist/browserslist-useragent-regexp

Although we can do this, the main used library - ant design 4.0 only support the latest modern browsers: https://ant.design/docs/react/introduce-cn#兼容环境
In my opinion, the dashboard is a product toB, not toC. Unlike toC, it rarely happens that the user decides to not use this product (and TiDB) just because it can't run in its browser. I think it is fine to prompt users to upgrade their browser if the browser is outdated. And support legacy browsers will limit us to use some new web technologies. Of course, this is just my personal view.

@baurine We have already met several important clients using an old browser like a Chrome published 3 years ago. If we can support this case then it would be great.

Maybe we should declare the supported browsers list in our documentation as well likes grafana: https://grafana.com/docs/grafana/latest/installation/requirements/#supported-web-browsers

@baurine See #640

Got it and make sense. I talked with DBA, the clients may use a very old Chrome or Firefox browser (they won't upgrade it after installing), but they don't use IE anymore.

@baurine Yeah, so a fixed version list is very necessary.


Where do I find the pico apk? I only see apk for oculus and quest

In the nightly repo: https://github.com/alvr-org/ALVR-nightly/releases

alvr_client_android.apk is for pico?

Yes


Controllers not properly loaded when using Sidekiq and Padrino::Mailer?

We have a sidekiq worker which crunches some data, then builds an email. For some reason, a sidekiq worker inside the mailer cannot resolve routes in my application. If I run the underlying code for the sidekiq worker in console, it works just fine.
If someone could point me to a missing initialization step or cause, I'd greatly appreciate it. Here goes:
We use a custom url_for which lets me pre-pend the root to the generated url
# at the top of my mailer
def url_for(*names)
  ::JavelinIo::ROOT_URL+::JavelinIo::App.url(*names)
end

Our sidekiq initializer just loads config/boot.rb, which in turn loads the workers for use in the app in the 'after_load' hook (see below).
# inside 'config/workers.rb'
require File.expand_path('../boot.rb', __FILE__)

Originally sidekiq wouldn't recognize my mailer even with boot loaded, so we explicitly required mailers in the after_load hook alongside the workers, like so:
Padrino.after_load do
  DataMapper.finalize
  DataMapper.logger.level = 3
  Padrino.require_dependencies("#{Padrino.root}/app/mailers/*.rb")

  Dir["app/workers/*"].each do |file|
    puts "found file: #{file}"
    require "./"+file
  end

end

Now sidekiq recognizes the mailer but it crashes when trying to generate urls with the following error:
Padrino::Routing::UnrecognizedException: Route mapping for url(:"organization details_for_rule_set") could not be found

i noticed the routes are symbolized into one arg, but I'm not setting that anywhere
if i hardcode this url, it fails further down on another url in a different controller

Thanks in advance for your help!

I was (and am) having the same issue. I've had to forgo using url() or url_for() in any of my background mailers for this reason.

I was (and am) having the same issue.

Would you be willing to put together a small example app with Padrino+Sidekiq+a simple Mailer configured so we could take a look?

As a workaround, have you tried requiring the mailer from the job class?

Closing as lacking feedback.


[BUGFIX] Move 'Clear cart' button to the upper part of the window

Related issues
#2697
Short description and why it's useful
Move "clear cart" button to the top of the cart. Additionaly, I've added conditional to clear cart button because it was displaying when there was no products in the cart.
Screenshots of visual changes before/after (if there are any)

Which environment this relates to
Test version (bugfix to new feature).

Thanks! I belive we should consult it with the UX designer as this button shouldn’t look like the main CTA which is Go To Cart in here

A "clear cart" button can have the same style as "return to shipping" one + additional remove icon. We use this style for button through the demo as a secondary button.
To create visual clarity small 1px divider can be added beneath "shopping cart" header

Thanks, @StasiekDivante; @rafalpyska can You please adjust the styles?

@pkarw Sure.

@rafalpyska could You please provide us with the screenshots after changes?

@pkarw  I have added horizontal divider and decreased font size a little bit. But I see it's too late.


As a dev, I want a client side framework to build reusable views on

create a simple dev environment for reusable and fast client work

[x] add RX and HBS rendering
[x] add webpack for building
[x] add simple entry area
[x] add scaffolding scss

#14 completes


Inform submission about evaluation step

Inform the submission if an evaluation is going to happen at the current step or not.
See related issue: https://github.com/mlcommons/algorithmic-efficiency/issues/719
Modifications:

moved evaluation decision before update_params
added is_eval_step argument to update_params
modified all submissions to include is_eval_step

I think we can close this PR judging from the WG meeting summarized in #719 (especially https://github.com/mlcommons/algorithmic-efficiency/issues/719#issuecomment-2027805925).


Worse performance using Accelerate

System Info
- `Accelerate` version: 0.26.1
- Platform: Linux-5.14.21-150500.55.36-default-x86_64-with-glibc2.31
- Python version: 3.11.4
- Numpy version: 1.26.0
- PyTorch version (GPU?): 2.1.1+cu121 (True)
- PyTorch XPU available: False
- PyTorch NPU available: False
- System RAM: 1007.51 GB
- GPU type: NVIDIA A100 80GB PCIe
- `Accelerate` default config:
        - compute_environment: LOCAL_MACHINE
        - distributed_type: NO
        - mixed_precision: no
        - use_cpu: False
        - debug: False
        - num_processes: 1
        - machine_rank: 0
        - num_machines: 1
        - gpu_ids: 3
        - rdzv_backend: static
        - same_network: True
        - main_training_function: main
        - downcast_bf16: no
        - tpu_use_cluster: False
        - tpu_use_sudo: False
        - tpu_env: []

Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
I am trying to use Accelerate to to distribute my training across multiple GPUs and I noticed that the training loss wasn't decreasing as fast as it should so I ran a new accelerate config to create the most basic one, without distributed training, to debug.
I seem to still be facing  the same problem, where the training loss decreases much slower, compared to a version of my script using only Pytorch. Here is the first version of training script I decided to use with Accelerate:
for epoch in range(1):

    model.train()
    dropout_modules = [module for module in model.lang_encoder.modules() if isinstance(module,torch.nn.Dropout)]
    [module.eval() for module in dropout_modules] # disable dropout
    accelerator.print(f"Disabled {len(dropout_modules)} Dropout modules")

    for i, batch in enumerate(tqdm(llavar_dataloader, disable=not accelerator.is_local_main_process)):

        with accelerator.accumulate(model):

            outputs = model(vision_x=batch["vision_x"], lang_x=batch["lang_x"].to(device), labels=batch["labels"].to(device), device=device)
            loss = outputs.loss
            if accelerator.is_local_main_process:
                total_loss += float(loss.item())
            accelerator.backward(loss)

            if accelerator.sync_gradients:
                accelerator.clip_grad_norm_(model.parameters(), 1.0)

            optimizer.step()
            model.zero_grad()

            if ((i+1) % accelerator.gradient_accumulation_steps == 0 or i+1 == len(llavar_dataloader)) and accelerator.is_local_main_process:
                with open("llavar_"+args.file, "a") as f:
                    f.write(f"Epoch: {epoch}, Loss: {total_loss/args.acc}\n")
                total_loss = 0 # Reset accumulated loss

Here is the problem: the training loss of both versions, using Accelerate and Pytorch, in the first iteration is the exact same. After that the loss decreases much faster in the pure Pytorch script. Note that I am using seeds in both, so that is why the first iteration is the exact same...
To debug I decided to remove the .accumulate call and build my own gradient accumulation flow, like this:
for epoch in range(1):

    model.train()
    dropout_modules = [module for module in model.lang_encoder.modules() if isinstance(module,torch.nn.Dropout)]
    [module.eval() for module in dropout_modules] # disable dropout
    accelerator.print(f"Disabled {len(dropout_modules)} Dropout modules")

    for i, batch in enumerate(tqdm(llavar_dataloader, disable=not accelerator.is_local_main_process)):

        outputs = model(vision_x=batch["vision_x"], lang_x=batch["lang_x"].to(device), labels=batch["labels"].to(device), device=device)
        loss = outputs.loss
        if accelerator.is_local_main_process:
            total_loss += float(loss.item())
        accelerator.backward(loss / args.acc)

        if ((i+1) % accelerator.gradient_accumulation_steps == 0 or i+1 == len(llavar_dataloader)) and accelerator.is_local_main_process:
            with open("llavar_"+args.file, "a") as f:
                f.write(f"Epoch: {epoch}, Loss: {total_loss/args.acc}\n")
            total_loss = 0 # Reset accumulated loss

            accelerator.clip_grad_norm_(model.parameters(), 1.0)

            optimizer.step()
            model.zero_grad()

and the results were very similar to the results in my Pytorch script when I removed gradient clipping. I also tested commenting out the line accelerator.clip_grad_norm_(model.parameters(), 1.0) and the results were the exact same. Note that added gradient clipping in my Pytorch script changes results a bit, and I also add it right before I call optimizer.step().
It looks like this issue has something to do with how gradients are accumulated/clipped, but I can't seem to pinpoint the problem...
UPDATE: switching accelerator.clip_grad_norm_ for the regular torch.nn.utils.clip_grad_norm_ does nothing to the training loss - using any form of gradient clipping (or none) seems to yield the exact same results using Accelerate, which is the same training loss as my pure Pytorch script without gradient clipping, but adding gradient clipping in my Pytorch script further improves the training loss...
Also, here is my pure Pytorch training loop/script:
for epoch in range(1):

    model.train()
    dropout_modules = [module for module in model.lang_encoder.modules() if isinstance(module,torch.nn.Dropout)]
    [module.eval() for module in dropout_modules] # disable dropout
    print(f"Disabled {len(dropout_modules)} Dropout modules")

    for i, batch in enumerate(tqdm(coco_dataloader)):
        # Assume batch['image'] and batch['text'] are image and text tensors respectively
        outputs = model(vision_x=batch["vision_x"], lang_x=batch["lang_x"].to(f"cuda:{args.cuda}"), labels=batch["labels"].to(f"cuda:{args.cuda}"), device=f"cuda:{args.cuda}")
        loss = outputs.loss / num_accumulation_steps
        loss.backward()

        if (i+1) % num_accumulation_steps != 0:
            total_loss = loss.item() + total_loss
        # done once every num_accumulation_steps (5) steps
        elif (i+1) % num_accumulation_steps == 0:
            # Normalize loss
            total_loss = (total_loss + loss.item())
            # parameters updated
            torch.nn.utils.clip_grad_norm_(model.parameters(), 1)
            optimizer.step()
            # Reset gradient tensors
            model.zero_grad()

            with open("llavar_"+args.file, "a") as f:
                f.write(f"Epoch: {epoch}, Loss: {total_loss}\n")

            total_loss=0

Expected behavior
I expected that using the Accelerate gradient accumulation method together with accelerate gradient clipping method should yield similar results to my pure Pytorch script, but something seems to be going wrong and it looks like it has to do with the gradients themselves...

It looks like the error was model.zero_grad(). It is valid in vanilla Pytorch, but switching to  optimizer.zero_grad() achieves what I wanted. Still, I am not sure why grad clipping isn't working when I don't use the .accumulate context manager...


Rewrite Decimal Array using const_generic

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Why I prefer using const_generic on Decimal?

Decimal128 and Decimal256 are different datatype. However all of their fields have same data type except the length of the value buffer [u8; 16] or [u8; 32].  This is the situation which const_generic is very suitable.
In the Rust standard library, there is a famous type using const_generic: the Array type: https://doc.rust-lang.org/std/primitive.array.html Decimal is very similar to Array
Remove some repeated code.
More constant evaluation
Easy to extend: We might add more Decimal type in the future. For example in arrow2, there is a PR to add Decimal 32 and 64: https://github.com/jorgecarleitao/arrow2/pull/896

Will the rewriting leads to many API changes?
Yes, But for users, the answer is no. Because this is just an internal refactor.
Checked List

[ ] BasicDecimal (#2383 )
[ ] BasicDecimalArray (#2383 )
[ ] DecimalBuilder

Describe alternatives you've considered
We could not do this.
Additional context
Related to #2362 and #2274.

@HaoYang670
The refactor is reasonable for me.

Do you want to do all the checklist in the one pull request?

Do you want to do all the checklist in the one pull request?
No.
In the first PR, I will update BasicDecimal and BasicDecimalArray. I tried to make change step by step, but I have to update these 2 in one PR 😅.


WeasyPrintBundle 1.4 is not compatible with php-weasyprint ^1.0

Hi,
In WeasyPrintBundle 1.4, the bundle try to create the service "weasyprint.image", but this service does no longer exists in php-weasyprint ^1.0. This version shouldn't be accepted for this release.

Hi @romainf,
you're right, I forgot to remove 1.0 support in 1.4.0 release, I've just released a fix as 1.4.1
Sorry for any inconvenience caused.


Update balena-yocto-scripts digest to fe6beaf

This PR contains the following updates:

Package
Update
Change

balena-yocto-scripts
digest
56bb055 -> fe6beaf

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Can one of the admins verify this patch?


Can you provide related configurations for pedestrians and cyclists?

I noticed that the method in your paper can detect cars, pedestrians and cyclists, but the current code only contains the relevant configuration of car class.
Can you provide related configurations for pedestrians and cyclists?

Hi @jlqzzz , the current code only supports the detection of car categories. However, I am struggling with some new works recently. If you need them urgently, you can obtain the incomplete point clouds and corresponding GT by simply sampling objects of pedestrians and cyclists from the KITTI dataset. Then refer to #5 to train the completion network.
Hope this helps you.


Added support for InfraVnet connectivity in multitenancy CNI

What this PR does / why we need it:
Added support for InfraVnet connectivity in multitenancy CNI. Added separate package for snat and infravnet
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

@sharmasushant addressed review comments.


Browser extensions

As the new website won't have, for now, the browser extensions, we need to figure out a plan to inform current users that that won't be available.

@dasaderi We can let users know via the newsletter...


Provide Compliance Data in CSV (or other TBD)

Benefit: Users can download each of the following groupings for analysis in CSV format (Travis 9/28)
Allowance-Based Compliance (For each trading program)
NOx Averaging Compliance (ARP)
*need to determine if these groupings are appropriate

Per discussion in PI Feature Sizing on 11/3, group decided to focus on the prototype for Apportioned Emission data in PI 2. Feature was returned to the backlog for consideration in future PI.

This functionality will be provided as part of the UI and static datasets prototypes. See #514 and #172

This functionality will be provided as part of the UI and static datasets prototypes. See #514 and #172


Allow client identifier to be provided to login

Currently PodOS uses dynamic registration, which runs into the issues with solid-client-authn-js documented in https://github.com/pod-os/PodOS/issues/8
I have established that with some relatively minor changes to solid-client-authn-js a static client (using a client identifier document) is able to restore its previous session without interfering with a client on the same domain that is using dynamic registration.

For the netlify version, a client identifier document will need to be added.
To use PodOS elements as web components (or self host), the user will need to create their own client identifier document that lists the required redirect_uris.
To use PodOS as the databrowser on a pod, additional changes would also be needed if the intention is for a single redirect uri to be used for all resources.

As a first step, PodOS needs to allow clientId to be specified at least in:

login in core https://github.com/pod-os/PodOS/blob/19b8fab8cd0167e5a53b0b971ea228accf1b65a8/core/src/authentication/index.ts#L37-L41
The corresponding call in pos-login https://github.com/pod-os/PodOS/blob/19b8fab8cd0167e5a53b0b971ea228accf1b65a8/elements/src/components/pos-login/pos-login.tsx#L26

In order for the user to be able to provide their client identifier document to the login component, it appears it would make sense to add a clientId prop to pos-login.
To include the clientId in the netlify version, it may also need to be a prop in pos-app-browser  and in the Makefile.
https://github.com/pod-os/PodOS/blob/19b8fab8cd0167e5a53b0b971ea228accf1b65a8/apps/Makefile#L2

Identifying essential tests:

New authentication/BrowserSession.spec.ts describes login and tests that

it uses clientId if it is defined on BrowserSession
it uses redirectUrl if it is defined on BrowserSession
it doesn't use clientId if not defined
It uses window.location.href if redirectUrl is not defined

pos-app.spec.tsx describes handle client identifier and tests that

it sets clientId on os.session
it sets redirectUrl on os.session

This seems like the minimal implementation.
redirectUrl is needed because it may not match window.location.href due to uri fragments.
Validation of the clientId is out of scope, including checking whether redirectUrl matches that in clientId.
This feature would not be covered by an existing e2e test. A new e2e test involves

a revised Makefile that (optionally?) copies a client identifier document into dist https://github.com/pod-os/PodOS/blob/main/apps/Makefile
A test that programmatically sets clientId and redirectUrl and then logs in

The e2e test should be changed to use client identifiers, since the e2e tests are meant to test the acutal app to be deployed wich is PodOS browser as e.g. deployed at https://browser.pod-os.org. There is no need for an e2e test to cover dynamic client registration, if we switch to client identifiers for the app.


Improved support script

filtered out ucp- containers because we already get all their data in the support dump, and they don't use overlay networking which is what we are focusing on here.  Added some formatting to container inspects to make it a little easier to read
@trapier @fcrisciani

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "improved_support_script" git@github.com:adamancini/libnetwork.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354610384
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@26531e5). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master   #2039   +/-   ##
========================================
  Coverage          ?   40.1%
========================================
  Files             ?     138
  Lines             ?   22132
  Branches          ?       0
========================================
  Hits              ?    8876
  Misses            ?   11957
  Partials          ?    1299

Continue to review full report at Codecov.

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

Trap made a good point in that this should not differentiate between ucp and non-ucp - ee components are outside the scope of libnetwork

Overall changes LGTM, once you get also @trapier +1, squash all the commits together and we merge it

@adamancini: take it for a spin https://github.com/docker/libnetwork/pull/2039/commits/1e766f54c97230a9eb69a695bac49baf5f35d101

Through some testing with customers, we've found that the way we detect support for network inspect -v is broken, and fails when used on a client that doesn't support it, so we need to fix that.

LGTM

Through some testing with customers, we've found that the way we detect support for network inspect -v is broken, and fails when used on a client that doesn't support it, so we need to fix that.

Indeed.  On 17.03.2-ee-8:
...
Overlay network configuration
nnn Network p9u1hcq5wfosfpvnzzgpqviub
unknown flag: --verbose
See 'docker network inspect --help'.
...

Looking into it.

Fixed --verbose detection (https://github.com/docker/libnetwork/pull/2039/commits/2b1b3201ca193123c88b0f5b434c675f1fd1c74d).  Code was looking for grep -q to emit 0 on stdout vs exiting with 0.

LGTM

@fcrisciani support is done with this issue, can you please review an merge.
Thanks

@dani-docker @trapier @adamancini can someone squash everything into 1 commit and sign it? After that I will merge it thanks

OK, so it looks like I learned how to rebase & squash correctly.  Signed-off and squashed.

Hey @adamancini can you also clean a bit the commit message:
make sure we get bridge fdb table

Signed-off-by: ada mancini<EMAIL_ADDRESS>
Check for --verbose support
don't truncate network IDs and programmatically use --verbose flag
Knock out health check messages from status map
Don't strip error messages
Don't exit when we detect a tool is missing, just echo a message
Echo and run commands via a function to record the exact commands
invoked
Format output of container inspect to make it easier to read

Signed-off-by: ada mancini<EMAIL_ADDRESS>
support.sh: remove healthcheck output

Signed-off-by: Trapier Marshall<EMAIL_ADDRESS>
support.sh: fix --verbose detection

Signed-off-by: Trapier Marshall<EMAIL_ADDRESS>
This is the only log that we will see in git log, so it would be great if we have a meaningful clean commit description. You can just do git commit --amend -s and change it


[reconciler] Add support for types.BalanceExemption

Changes

[x] Add new handler method for exemptions
[x] Ensure difference is live-computed

If Heimdall is stuck, please click the following link: https://heimdall-public.cbhq.net/v1/pull_request/stuck?pr_number=179&repository=coinbase/rosetta-sdk-go

Pull Request Test Coverage Report for Build 8638

22 of 47 (46.81%)  changed or added relevant lines in 2 files are covered.
9 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 78.232%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

reconciler/reconciler.go
18
43
41.86%

Files with Coverage Reduction
New Missed Lines
%

storage/badger_storage.go
9
82.92%

Totals

Change from base Build 8622:
-0.3%

Covered Lines:
6638

Relevant Lines:
8485

💛  - Coveralls

Review Error for arjun-io @ 2020-10-05 22:57:48 UTC
User failed mfa authentication, public email is not set on your github profile. see go/mfa-help


Update all the android related projects to target API level 27

Motivation
Google recently announced in a blog post called Improving app security and performance on Google Play for years to come that all the new apps submitted to the play store, after August 2018,  will require to be targeting at least Android API level 26:

August 2018: New apps required to target API level 26 (Android 8.0) or higher.

November 2018: Updates to existing apps required to target API level 26 or higher.

2019 onwards: Each year the targetSdkVersion requirement will advance. Within one year following each Android dessert release, new apps and app updates will need to target the corresponding API level or higher.

This PR updates all the Android related projects (ReactAndroid, RNTester and the HelloWorld template) to target the API level 27.
I did not find any issue doing this upgrade but since RN was targeting version API level 22, the developers need to be aware that targeting any API level greater that 22 will introduce the run time permissions feature. Since this is a breaking change it should be described in the changelog.
This PR also closes https://github.com/facebook/react-native/issues/17287.
Test Plan
I tested the project and LGTM. I compiled and executed the RNTester and everything looks good.

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/react-native-website, and link to your PR here.)
Release Notes
[CLI] [FEATURE] [local-cli/generator/templates] - Generate the android app template targeting API level 27.
[ANDROID] [FEATURE] [BuildTools] - Updates the Android project to target  API level 27.

@hramos can you please help me finding someone to review the PR?

@SandroMachado can you look at the release.gradle conflicts, and make sure the test-android test passes first?

I've fixed the conflicts. Next we'd need to update the Circle tests to ensure they're using an image with the correct build tools and Android SDK versions installed.
People can still manually update their project to target API 27 so this is not considered as blocking people from mitigating the issue on their own projects.

@hramos thanks and sorry for the delay fixing the conflicts 👍

@hramos any plans to merge the PR? Do you need more changes?

This was again mentioned yesterday at Google I/O. The sooner this is merged in, the better, otherwise there will be a ton of people complaining about not being able to publish their app from August 2018 and from November 2018, publish updates to their app.

As we have announced, Google Play will require new apps (from August 2018) and app updates (from November 2018) to target API level 26 or higher. For more information and practical guidance on preparing for the new requirement, watch the I/O session, Migrating your existing app to target Android Oreo and above, and review our migration guide. If you develop an SDK or library that's used by developers, make sure it's ready to target Oreo too and sign up to receive news and updates for SDK providers.

Thanks for the PR. I'll see what needs to be done to get this merged.

@hramos @SandroMachado is there any update we are also facing this issue of upgrade target sdk

@TheCodeTalker I am waiting for  the review.

We're actively working on it. The SDK was bumped in https://github.com/facebook/react-native/pull/19257 and it has surfaced some build failures (see https://github.com/facebook/react-native/issues/19309).
If you are interested in making this work, please join the discussion in https://github.com/facebook/react-native/issues/19309 and help move the change forward, otherwise the bump to 26 may be reverted back to 23.

If you revert the version bump, what's the long term solution? This update needs to happen sooner or later anyway.

This pr also need to fix conflict.

This is approved. How does it get merged?

Let's get this merged please @reactnativeteam :)

@hellogerard anyone can leave a review on a PR, which includes approving/requesting changes. The PR still needs to be reviewed by a core contributor before it can be merged.

@hramos so the main objective is move to API level 26, since this PR is pointing to 27 it will not be merged, at least for now. Right? I can easily fix the conflicts but I want to understand if the PR will be merged.

@SandroMachado I have plan to bump SDK to 27, when ready. I and many developers experience issues when they use SDK 27, like aapt2. So we need some time to thoroughly test the SDK 27. That was my reason to choose SDK 26.

@dulmandakh understood, thanks for the clarification.

@SandroMachado you can close this PR if you are satisfied with the results/progress.

Help needed https://github.com/facebook/react-native/pull/20026

closing this PR because SDK 27 is landed in master.

Re-opening because the SDK 27 upgrade is being reverted.

@hramos can you please give more details. Why is it being reverted?

I left some comments in the commit themselves. The revert already landed, but I have a fix that should let us get back on 27. It's waiting for review and should land soon if no blockers show up.

@hramos understood! Thanks for the clarification. 👍
Commit

This is fixed now.


Third-party package risk

Problem
After seeing this attack via a third-party package, I grew curious about Glacier's use of third-party packages. In the Glacier doc, during the creation of the APP USBs, the list of packages is shown:
bitcoind_0.13.2-xenial1_amd64.deb
libboost-chrono1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb
libboost-program-options1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb
libboost-thread1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb
libdb4.8++_4.8.30-xenial2_amd64.deb
libevent-core-2.0-5_2.0.21-stable-2_amd64.deb
libevent-pthreads-2.0-5_2.0.21-stable-2_amd64.deb
libqrencode3_3.4.4-1_amd64.deb
libsodium18_1.0.8-5_amd64.deb
libzbar0_0.10+doc-10ubuntu1_amd64.deb
libzmq5_4.1.4-7_amd64.deb
qrencode_3.4.4-1_amd64.deb
zbar-tools_0.10+doc-10ubuntu1_amd64.deb

This is a list of targets for anyone attacking Glacier. How can we make sure these packages do not get malware sneaked into them? Ubuntu package management has some security checks but can we really rely on that? Is it really impossible for an attacker to slip in a change without changing the version number?
Checksums
We could provide a SHA256SUMS file, like we do for the Glacier-provided files, and instruct the user to checksum the *.deb files. But this is only robust if we can be sure the list of files will never change (for innocent reasons) over time.
Pinning
Pinning to specific versions would be required, and Glacier seems to do that pretty well. I tried the process today and found the following packages appeared:
bitcoind_0.17.0-xenial1_amd64.deb
libboost-chrono1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb
libboost-thread1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb
libdb4.8++_4.8.30-xenial4_amd64.deb
libevent-core-2.0-5_2.0.21-stable-2ubuntu<IP_ADDRESS>_amd64.deb
libevent-pthreads-2.0-5_2.0.21-stable-2ubuntu<IP_ADDRESS>_amd64.deb
libqrencode3_3.4.4-1_amd64.deb
libsodium18_1.0.8-5_amd64.deb
libzbar0_0.10+doc-10ubuntu1_amd64.deb
libzmq5_4.1.4-7_amd64.deb
qrencode_3.4.4-1_amd64.deb
zbar-tools_0.10+doc-10ubuntu1_amd64.deb

Note the differences:

bitcoind is different (as expected)
libboost-program-options is no longer there
libdb has different filename
libevent-core has different filename
libevent-pthreads has different filename

It's unclear to me if the different filenames are more-recent builds of those packages or simply renamed files.
Solutions?
I wish the installed files hadn't changed since the doc was written. That would make this a lot easier. We could checksum those package files and provide a SHA256SUMS file to verify the integrity of all of them.
I don't know enough about the Ubuntu package system to understand when and why packages might change like this, despite version pinning.
The doc is clearly out of date, though I'm hesitant to simply copy-paste the new list of installed files without more understanding of why the list has changed. (By including the new list in the doc, we are giving our approval of these changes. At least today, careful users will notice the discrepancy and ask questions, as they should.)

Is the libboost-program-options file needed?  In the 0.93 release I found the zbarcam app wasn't available and bitcoind wouldn't start.
Anyone else have these issues?

Thanks - will do


Cannot read property 'Group' of undefined

Steps
I import the Transition-Module :
import { ...,Transition } from 'semantic-ui-react';
and would like to use it like this:
 <Transition.Group animation={"drop"} duration={2000}>
       {this.props.searchStore.searchResult ? <SearchResultList />: <ElementDetails />}
  </Transition.Group>

Expected Result
No Errors :smiley:
Actual Result
I get this Error:
Cannot read property 'Group' of undefined
Version
"semantic-ui-react": "^0.72.0"

Can you make a fresh install of deps? rm -r node_modules; npm i It seems that you use another version.

works :+1: , thanks


Hackathon: ATAN2, POW, INITCAP, MD5, SPLIT_PART

All functions ready

This can be closed and replaced with https://github.com/cmu-db/terrier/pull/1114


ci: change docs destination in the website site

That PR changes docs destination in the website site from docs/specifications to the docs/reference/specification - see more https://github.com/asyncapi/website/pull/601
Related issue(s):
Part of https://github.com/asyncapi/website/pull/601 and that PR should be merged after merging mentioned PR

I already have a PR for this, please close this @magicmatatjahu

@alequetzalli 😆 Sorry, I didn't notice. But please fix your PR because there are 2 other files where you need to fix the links - see my changes :)


Coordinates implicitly created when passing a DataArray as coord to Dataset constructor

I stumbled on this while working on #5692. Is this intended behavior or unwanted side effect?
What happened:
Create a new Dataset by passing a DataArray object as coordinate also add the DataArray coordinates to the dataset:
>>> foo = xr.DataArray([1.0, 2.0, 3.0], coords={"x": [0, 1, 2]}, dims="x")
>>> ds = xr.Dataset(coords={"foo": foo})
>>> ds
<xarray.Dataset>
Dimensions:  (x: 3)
Coordinates:
  * x        (x) int64 0 1 2
    foo      (x) float64 1.0 2.0 3.0
Data variables:
    *empty*

What you expected to happen:
The behavior above seems a bit counter-intuitive to me. I would rather expect no additional coordinates auto-magically added to the dataset, i.e. only one foo coordinate in this example:
>>> ds
<xarray.Dataset>
Dimensions:  (x: 3)
Coordinates:
    foo      (x) float64 1.0 2.0 3.0
Data variables:
    *empty*

Environment:
Output of xr.show_versions()

INSTALLED VERSIONS
commit: None
python: 3.8.6 | packaged by conda-forge | (default, Nov 27 2020, 19:17:44)
[Clang 11.0.0 ]
python-bits: 64
OS: Darwin
OS-release: 20.3.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: None
LOCALE: (None, 'UTF-8')
libhdf5: 1.10.6
libnetcdf: 4.7.4
xarray: 0.19.0
pandas: 1.1.5
numpy: 1.21.1
scipy: 1.7.0
netCDF4: <IP_ADDRESS>
pydap: None
h5netcdf: None
h5py: None
Nio: None
zarr: None
cftime: 1.3.1
nc_time_axis: None
PseudoNetCDF: None
rasterio: None
cfgrib: None
iris: None
bottleneck: None
dask: 2021.07.2
distributed: 2021.07.2
matplotlib: 3.3.3
cartopy: 0.19.0.post1
seaborn: None
numbagg: None
pint: None
setuptools: 49.6.0.post20201009
pip: 20.3.1
conda: None
pytest: 6.1.2
IPython: 7.25.0
sphinx: 3.3.1

I have definitely relied on this before, I imagine its a pretty common pattern too but I could be wrong.
Note that automatically adding the index satisfies this condition which seems sensible to me
ds.foo.identical(foo)

I think a similar concern applies to .update. I find it surprising in the first place that a single mapping item ("foo") results in multiple mapping items ("foo", "x") in the returned xarray object.
That said, I agree that taking into account the (indexed) coordinates of the DataArray are important for alignment. The example below makes perfect sense:
>>> foo = xr.DataArray([1.0, 2.0, 3.0], coords={"x": [0, 1, 2]}, dims="x")
>>> ds = xr.Dataset(coords={"x": [2, 3, 4, 5]})
>>> ds.update({"foo": foo})
<xarray.Dataset>
Dimensions:  (x: 4)
Coordinates:
  * x        (x) int64 2 3 4 5
Data variables:
    foo      (x) float64 3.0 nan nan nan

I guess my concern is related to the slightly ambiguous view of the DataArray concept as a single array-like vs. a collection of data + coordinates.

the DataArray concept as a single array-like vs. a collection of data + coordinates.

Yeah  non-dim coordinates essentially make DataArrays a Dataset with one special variable =)