Auto-Power-On after Power Loss

As this board will most likely be utilised as a server-type device and be mounted in a rack in some dark corner, is here a way to get the board to Auto-Power-On after power loss? It may not be convenient to have to physically press a button to get the board powered on if not easily accessible.

The board has a switch "Always On". I haven't tested it but I assume that's what you describe. I'll try to test if I don't forget :D


Removing VirtualMachineSizeTypes enum as updating the sizes is not maintainable

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run automation - sdk

This would be a breaking change for all of the SDKs
CC @ChenTanyi @qiaozha @allenjzhang @changlong-liu could you please have a review on this from the corresponded SDK's perspective?

@xccc-msft for awareness. May need to auto-gen by API.

Yes, I think changing type from enum to string is a breaking change. And involving breaking change in stable api-version should be cautious!
CC to @msyyc

/azp run automation - sdk

Yes, I think changing type from enum to string is a breaking change. And involving breaking change in stable api-version should be cautious!
CC to @msyyc

@changlong-liu hardwareProfile.properties.vmSize was defined as a string type previously and that remains unchanged. Previously provided enum for the possible values is being deprecated. Can you please elaborate on "I think changing type from enum to string is a breaking change"?

Hi @avinashakka ,
Previous defined enum in swagger brings enum definitions in SDK (for instance for Python:  https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/compute/azure-mgmt-compute/azure/mgmt/compute/v2020_06_01/models/_compute_management_client_enums.py#L374).
Deleting the definition of that enum will break custom code which use these enum values. So it's a breaking change in theory.

/azp run

Hi @avinashakka any updates?


Add chicoma-gpu

Following pm-gpu, we want to add files to support chicoma-gpu.

We're deprioritizing this.


Update documentation for using databases using Space API

Done. Will be released along with v0.17.0


Extract AbstractTestTask logic into a service

Part of the native work for supporting XCTest was to reuse the JVM testing infrastructure. Most of the common logic was extracted to AbstractTestTask. It requires test framework integration to extends AbstractTestTask and implement createTestExecutionSpec and createTestExecuter.
Expected Behavior
By extracting the logic into a service, we can simplify the requirement for test framework integration and remove internal type leaked through protected method. The base class AbstractTestTask should only provide generic APIs commons between test frameworks.
Current Behavior
New test framework integration relies on extending the base class as opposed to composing.

I think a better title for this issue would be something like 'expose fewer internal services from the testing tasks'. Using a service would be a way to solve this.


The inbound traffic statistics of the LAN interface are incorrect.

The inbound traffic statistics of the LAN interface are incorrect.

DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='23.05.0-rc3'
DISTRIB_REVISION='r23389-5deed175a5'
DISTRIB_TARGET='x86/64'
DISTRIB_ARCH='x86_64'
DISTRIB_DESCRIPTION='OpenWrt 23.05.0-rc3 r23389-5deed175a5'
DISTRIB_TAINTS=''

Not a LuCI issue, we merely report what the kernel is reporting.


Custom loader in addition to bar?

Hi,
Is there a simple way of adding a 'custom spinner' in addition to the loading bar?
Thanks,
Daniel

You can do that with below
angular.module('myApp', ['angular-loading-bar'])   .config(['cfpLoadingBarProvider', function(cfpLoadingBarProvider) {     cfpLoadingBarProvider.spinnerTemplate = '
Loading...
';   }])

Thanks @bhushangahire


New (beta) github file view is slightly broken

I'd opt to leave it untouched for now until the feature is final. I really hope that the way they apply their styling isn't going to stay like this once the feature reaches production.. Because if it does it will be a hell to style properly.

Seems the feature has been released

Also applies to search results

It's still in the preview section for me … so I can disable it.
I really don't wanna deal with annoying inline styles. GitHub please.

This is definitely broken
(Hover doesn't work either)


Missing Elevation / Shadow for Bottomsheet

Isn't this bottom sheet missing the elevation? As defined here

Good catch, we're working on it!


Rename the stack_load / stack_store formats

I think the stack_load format should be renamed, as it is used for stack_addr here too.

Originally posted by @bjorn3 in https://github.com/CraneStation/cranelift/pull/1160
It's a good idea, but I can't think of a right name right now. Format naming can sometimes be inconsistent.
The stack_load format is used by two instructions:

the stack_load instruction (load from the stack)
the stack_addr instruction, which computes the address of a stack slot.

The stack_store format is used only the instruction that has the same name.
For consistency with other operators, I thought about renaming stack_load => UnaryStack, and stack_store => BinaryStack, but I feel it hides part of the information (which is why I'm not a huge fan of BinaryImm in the first place).
Maybe an alternative is to rename stack_load into stack_read, and keep stack_store as is?
(Let the bikeshed begin!)

No one seems to have strong opinions about this bikeshed needing to be painted a different color, and I'm cleaning up old issues, so I'm going to go ahead and close this; but, suggestions of this sort are always welcome if anyone has new ideas :-)


Add questions tag

Because I find myself pointing people to Asking Good Questions regularly.

What do you think it needs? The page it links to has comprehensive detail and I didn't want to just repeat any of that.

Blocked for further discussion, please open an issue in python-discord/meta.

Staff consensus in today's meeting is that we don't want to go forward with it, largely for the same reasons we removed the old !ask tag. The link doesn't clarify what exactly is wrong with the question asked, which is very context specific, and has a high chance of being used passive-aggressively by being dumped at people (sometimes several times) with no further explanation, as we have seen with the old tag.


apostrophe-pubmed and apostrophe-pubmed-import updates

Is this a bug fix? An enhancement? Any movement (since it's been a while)?

@boutell apostrophe-pubmed-import is broken - working on a fix

No longer broken for large data sets - still working on enhancements to make it more useable. Issues opened in the module repo.


Xio code2

we need to make some changes

text should not leak underneath the copy button
copy button should have the svg
there should be some padding

closed for lack of activity


Use sensu-settings 10 & utilize settings hexdigest

Description
Use sensu-settings 10.0.0, which decoupled state management from loading, and added settings hexdigest. This pull-request utilizes the settings hexdigest in the Sensu server registry and Sensu API /info endpoint, to help users determine if a Sensu server's configuration differs from the rest.
Related Issue

Motivation and Context
Decoupling state management from loading enables some Sensu Enterprise improvements.
Exposing Sensu server settings hexdigests via the API allows users to determine if a Sensu server's configuration differs from the rest (snowflake).
How Has This Been Tested?

Screenshots

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

I'm in love with hexdigests! 😍


Check whole report

I have added a small paragraph regarding the % of private functions in the SIG feedback. I also wrote the section about the service-worker cache in section 7.3.

Change references to the product,  tool,  system to preview code when it's sufficiend.


Easy way to update  and other elements using Frames

Hi, when using data-turbo-frame="some-frame" then <title> in <head> is not updated.
Also, I would like to update <meta name="csrf-token" content="..."> which changes on each request.
Also <link rel="canonical" href="https://example.com/some-page-xyz"> should be always updated.
Also <footer>Our site was visited {{ get_day_visits() }} times today.</footer> should be always updated.
And so on...
One workaround is to include <turbo-stream> to html template, however that duplicates elements and it is very verbose:
/* in head */
<meta id="csrf-token" name="csrf-token" content="{{ get_csrf_token() }}">
<title id="title">{{ get_title() }}</title>

/* in frame */
<turbo-stream action="update" target="csrf-token">
    <template>{{ get_csrf_token() }}</template>
</turbo-stream>
<turbo-stream action="update" target="title">
    <template>{{ get_title() }}</template>
</turbo-stream>

What is better solution to solve this problem using Frames?
I was thinking that a new attribute data-turbo-fresh could be created. It could always try to update that element (it should have id attribute) when new data arrive to client.
<title id="title" data-turbo-fresh>{{ get_title() }}</title>

So, title would be always updated/replaced if the new HTML data contains #title element. If the new HTML data does not contain matching element, then no change should be done.
Maybe method could be specified: data-turbo-fresh="update" or data-turbo-fresh="replace"

I like the idea of updating some of these attributes in a more automated way.
The canonical URL one is interesting. If a crawler is indexing your page and following links which are in frames is it possible that you could be royally messing up your search ranking if the link destination / URL does not match the canonical URL?

If the crawler is advanced and renders JavaScript in a way that is indistinguishable from a web browser, then yes - it indexes wrong data. I am not aware that Turbo tries to detect JavaScript crawlers... However it is better to assume that crawler is as capable as web browser. However, in principle, it does not matter - what matter is that a page as seeb by anyone has WRONG canonical URL and WRONG content of some elements. As a result, crawler could index it wrong. And as a result, other JavaScript scripts could work with WRONG canonical URL and other elements.

The behavior should be changed according to the value of data-turbo-action.
https://turbo.hotwired.dev/handbook/frames#promoting-a-frame-navigation-to-a-page-visit

What if I want to have advance (push new history record) and at the same time to update some elements like  ?

Anyway, I found Hotwired Turbo to be not very flexible for general of PJAX use cases and it contains inconsistent behaviour related to scrolling-to-top as of latest release 7.1.0 from 2021, so I moved to https://github.com/MoOx/pjax

For the maintainers of this project, I have created my frame with <turbo-frame data-turbo-action="advance"> which does correctly change the URL but the title and other <head> fields do not change. It's an interesting spot because if the frame's response doesn't include the head's information then how could the front-end alone know to update that without some help from the back-end? Perhaps this could be addressed in turbo-rails?

@misog: If I understand you right, you're suggesting the updated <title> value is included in the frame response? Where? Within the <turbo-frame> tag?

@kendagriff  My response contains full  content. The <title> is in <head> which is not wrapped in turbo-tag.

Just wanted to follow up and mention this is still an issue with v7.3.0 (and turbo-rails 1.4.0). Based on the release's description I sort of thought that would have fixed this issue by letting you use content_for (in Rails) to update <head> attributes on specific pages but it didn't.
This is problematic when using frames because:

For authenticated pages:

Being able to update the title is important so folks know what page they're on in your app

It comes off as buggy if this doesn't update

For anonymous pages:

Crawlers pay close attention to the title and meta description
There's also the canonical URL link tag which is very important to be up to date
There's also OpenGraph cards and other meta data that's really important to be correct

I found the same problem using a turbo-ios app with Turbo enabled.  I was please to find that when  I implemented a top native menu using strada-ios, the title changes correctly on every page. This happens without any special code to do this.


Issue #33 - Fix broken links in some addon READMEs

Quick fix for broken links in some addon folders: cockpit, cors etc.

LGTM :+1:

Thanks @agajdosi


MarkerWithLabel do not work, cannot read property 'removeChild' of null

A few days ago MarkerWithLabel stopped working
Before that everything worked fine
In the browser, I noticed an error ...
Uncaught TypeError: Cannot read property 'removeChild' of null
    at MarkerLabel_.onRemove (index.js:325)
    at Ez.ug (overlay.js:4)
    at Gz (overlay.js:1)
    at Object.Xk (overlay.js:5)
    at js?v=3.exp&key=AIzaSyBt_qVRW8YYbccOObNdiN_MPskqQcUeu7A&libraries=visualization,places&language=uk:140
    at Object._.Q (js?v=3.exp&key=AIzaSyBt_qVRW8YYbccOObNdiN_MPskqQcUeu7A&libraries=visualization,places&language=uk:62)
    at MarkerLabel_._.Xg.map_changed (js?v=3.exp&key=AIzaSyBt_qVRW8YYbccOObNdiN_MPskqQcUeu7A&libraries=visualization,places&language=uk:140)
    at Tc (js?v=3.exp&key=AIzaSyBt_qVRW8YYbccOObNdiN_MPskqQcUeu7A&libraries=visualization,places&language=uk:50)
    at MarkerLabel_._.m.set (js?v=3.exp&key=AIzaSyBt_qVRW8YYbccOObNdiN_MPskqQcUeu7A&libraries=visualization,places&language=uk:122)
    at MarkerLabel_.setMap (js?v=3.exp&key=AIzaSyBt_qVRW8YYbccOObNdiN_MPskqQcUeu7A&libraries=visualization,places&language=uk:53)
    at MarkerWithLabel.setMap (index.js:591)
    at Cluster.addMarker (markerclusterer.js:502)
    at MarkerClusterer.addToClosestCluster_ (markerclusterer.js:1458)
    at MarkerClusterer.createClusters_ (markerclusterer.js:1517)
    at MarkerClusterer.redraw_ (markerclusterer.js:1373)
    at MarkerClusterer.repaint (markerclusterer.js:1319)
    at MarkerClusterer.componentDidUpdate (MarkerClusterer.js:139)
    at measureLifeCyclePerf (ReactCompositeComponent.js:75)
    at ReactCompositeComponent.js:728
    at CallbackQueue.notifyAll (CallbackQueue.js:76)
    at ReactReconcileTransaction.close (ReactReconcileTransaction.js:80)
    at ReactReconcileTransaction.closeAll (Transaction.js:209)

I've also seen this behavior as well, I managed to trace down the issue to MarkerClusterer I think. This code works:
{markers!.map((marker: MapTypes.MapMarker, index: number) => (     <MapMarker history={history} marker={marker} key={index} /> ))}
But this code doesn't work:
{markers && (     <MarkerClusterer averageCenter={true} enableRetinaIcons={true} gridSize={60}>         {markers.map((marker: MapTypes.MapMarker, index: number) => (             <MapMarker history={history} marker={marker} key={index} />         ))}     </MarkerClusterer> )}

Same here. Definitely something to do with MarkerClusterer

Are there any workarounds? My client keeps crashing because of it.

There is a solution posted in the MarkerWithLabel repo, but I haven't tested it locally yet (we just commented out the clusterer). YMMV.

I solved it by changing the version of the google api from the experimental version to v3.31
before:
export const GOOGLE_API = 'https://maps.googleapis.com/maps/api/js?key=AIzaSyDk-SZbgOovJvTafj7feDjxUIXUrW0L9vY&v=3.exp&libraries=geometry,drawing,places'
after:
export const GOOGLE_API = 'https://maps.googleapis.com/maps/api/js?key=AIzaSyDk-SZbgOovJvTafj7feDjxUIXUrW0L9vY&v=3.31&libraries=geometry,drawing,places'

wow.. That's works. That's awesome.
On Wed, Mar 7, 2018 at 7:04 AM, pdarvas<EMAIL_ADDRESS>wrote:

I solved it by changing the version of the google api from the
experimental version to v3.31
before:
export const GOOGLE_API = 'https://maps.googleapis.com/
maps/api/js?key=AIzaSyDk-SZbgOovJvTafj7feDjxUIXUrW0L9vY
&v=3.exp&libraries=geometry,drawing,places'
after:
export const GOOGLE_API = 'https://maps.googleapis.com/
maps/api/js?key=AIzaSyDk-SZbgOovJvTafj7feDjxUIXUrW0L9vY
&v=3.31&libraries=geometry,drawing,places'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tomchentw/react-google-maps/issues/774#issuecomment-370872737,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBeptXE5o-BTmFot0r4_pzDDzO4-LT0ks5tbs-qgaJpZM4SG8rT
.

In case it could help others, I wrote this monkey-patch last week: https://gist.github.com/kentaromiura/6bb9d0061c92087792f289dfde4989cd
I only found this issue today, thanks for suggesting changing the url from experimental to a fixed version, that fixed another issue I was having.

The solution with 3.31 does not work anymore.
"Versions 3.0 to 3.31 have been deleted."
https://developers.google.com/maps/documentation/javascript/versions#choosing-a-version-number

I'm receiving this error since yesterday.
I've been using version 3.31 of google maps.
I've updated the Google Maps version to 3.32 (and tried also at 3.33 & 3.34) and the error still occurs.
The solution mention above (changing the markerLabel's on remove method) fixes the problem but only locally. I need a fix that does not include changing the node modules.
Does any one else started experience this problem since yesterday?

Same here, since yesterday
I'm receiving this error every time the UI render the markers in
Any solution for that?

@kentaromiura's monkey patch worked great for me - not ideal obviously, but just created a js file, included a <script> tag with it right under my Google API script load and the problem stopped.

Where can i find this patch?

this comment has it. Weird thing is this morning, though no one on engineering can replicate, we still are seeing errors reported on production, so may not be a silver bullet.

Ok, so we're still trying to iron this out, but may have found something that seems to fix this:
componentWillUnmount () {
    this.setState({ markers: [] })
}

I noticed this problem is very easy to replicate locally (without the monkey-patch above) by running HMR, so I assumed it must be something with lifecycle. Explicitly setting our markers to an empty array as shown above seems to stop the error, but will update if I find more information.

thanks, this patch works really well!

I don't know. I just included it after the clusterscript.

The problem was not in this library, but in jesstelford/node-MarkerWithLabel  library, which is in react-google-maps dependencies.
I have made a PR to jesstelford/node-MarkerWithLabel that was approved a few hours ago with the proper fix.
I have also made a PR to react-google-maps that update the markerWithLabel library.
Until this PR is Approved, another solution is to npm install markerwithlabel to your package.json so your version will override the react-google-maps's version of markerWithLabel.

@mlautin, I forgot the --save
try:
npm install --save markerwithlabel

@Avivhdr Do you have any solution for the angular-google-maps library?

@mlautin, I've cancelled the pull request. it is not needed.
In react-google-maps, markerwithlabal is listed as a dependency with the following version:
"markerwithlabel": "^2.0.1"
the ^ sign means that whenever the package is being installed,  it will be installed it in the latest patch version.
Which means the every new version of markerwithlabel smaller then 2.1.0 will be automatically installed.
Short explanation here.

@lironbar
No, sorry.

@lironbar did you find a solution for angular-google-maps?


Re-implementing and optimizing core analysis algorithms in Rust

Adds the necessary infrastructure for a mixed python/rust project using maturin and pyo3 bindings
Initial performance speed-up without concurrency: ~6x

Since this is my first experience with a mixed python/rust project and rust programming in general, this branch is considered highly experimental, with an unstable API and logic that is subject to change.
Feedback is welcome and much appreciated.

This is quite a cool start.
I'm always busy writing my own mod tools for other people; so I unfortunately never get to use this stuff; but I always wanted to see a native version of this. Letting someone just drop a music file, finding the loop points and making a very quick conversion into a game's native music format is a very cool use case.

Thanks for the vote of confidence @Sewer56. A GUI may be come sooner than later since it has been planned for a while. Unfortunately, supporting game native music formats and conversion is too big of a scope to handle as the only maintainer, but that said, contributions are always welcome!
Part of the reason I wanted to move the essential logic to a rust crate for a while is to ultimately create a foobar2000 plugin. It'd be a properly seamless experience then, as an alternative to the single track repeat within a rich music player ecosystem. It's still very far off and I'm not sure if it's feasible, but ultimately the tool shouldn't be constrained to a single file in a CLI. In fact, there is technically nothing stopping the ability to loop or mix different tracks altogether, which would be, personally speaking, a very interesting direction for the project to take.


Adds ability to specify version increment non-interactively on cli

This will enable people to use oao as part of a continuous deployment environment, where selecting the next version on interactively isn't possible.
Usage
oao publish --no-confirm --increment-version-by <major|minor|patch|rc|beta|alpha>

I'm open to feedback/changes to make this PR more consistent with the rest of the project if needed.

Not sure why the build failed, i don't think it's related to my changes:
'/home/travis/.nvm/versions/node/v8.1.0/lib/node_modules/.staging/http-signature-44735bc1/.dir-locals.el'
npm ERR! Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?

Thanks for the PR! I'll review it asap; I think it's a really nice idea and contribution to the project.
As to the build error, I'm also unsure as to what's causing this. I haven't tried to build oao on Node 8.x, so will need to check locally. Thanks for your patience!

It looks like it fails on installing yarn. It seems travis-ci now has yarn by default: https://blog.travis-ci.com/2016-11-21-travis-ci-now-supports-yarn, I'll modify travis.yml and try again.

Coverage increased (+0.4%) to 86.892% when pulling f8dcc806398e168e1b948f327690859aed343a14 on gordlea:automatic-increment into 3098ab0586a2ceac6da90612b5765849b433c378 on guigrpa:master.

@guigrpa Any timeline on getting this reviewed? I'd like to start using it on our CI build. Totally okay if you're too busy at the moment, I'd just like an idea of when it might be in for planning purposes. 😄

Right now I want to get some perf improvements out (oao bootstrap, so it will probably be useful to you as well on CI) and will probably release tonight (CET). I'll review this PR after that, I guess this week.

Out of curiosity, are you going to use it for an OSS project, or internally?

Out of curiosity (II): how do you tell Travis what kind of version bump you want (major, minor, patch, etc.)?

@guigrpa we're planning on using it internally for now. If we release any oss we will consider it.
I'm going have a script that does something like this:

Find the PR (using the github api) that was merged into master to kick off the current build.
Parse the title of that PR for [major], [minor], [patch]. If no increment is found in the title, default to minor.
Pass the parsed value to  --increment-version-by.

If someone isn't using github, they could do something similar with changelogs or something.

LGTM, thanks for this improvement to oao and for the insight on your publishing process. I'll try to cut a new release in a few days.


Feature request: remember local port

Remember the local port previously used for specific connect target and suggest it on the subsequent connect.
Users will have DB connections saved locally so it's important to use same port.

Right now, you can use a set of predefined commands to connect to your targets quickly:
basti connect --rds-instance <instance-id> --local-port 54322

However, the feature is valid and will be added soon!


Investigate Pay Lines

http://wizardofodds.com/play/slots/atkins-diet/atkins-diet.pdf

Issue moved to ishaan-puniani/Online-Casino #13 via ZenHub


⚠ Samsung has degraded performance

In 449c971, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2204 ms

Resolved: Samsung performance has improved in 6220787.


Unsupported callback API version: version 2.0

Seems that plugin not work with version 2.1.0 of  paho-mqtt, downgrading to 1.6.1 solves the bug

Logs:
[2024-06-07 19:09:03,973] [INFO    ] Unverified SSL context created.
[2024-06-07 19:09:03,973] [INFO    ] Network interface MAC Address: 64:00:6a:3d:5c:21
Traceback (most recent call last):
  File "/homebridge/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv.py", line 6, in <module>
    __main__.main()
  File "/homebridge/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv/__main__.py", line 130, in main
    with tv:
  File "/homebridge/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv/__init__.py", line 124, in __enter__
    self._mqtt_client = mqtt.Client(self.client_id)
  File "/usr/local/lib/python3.10/dist-packages/paho/mqtt/client.py", line 772, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see docs/migrations.rst for details

Plugin Config:
{
    "ifname": "enp2s0",
    "devices": [
        {
            "id": "hisensetv43",
            "name": "TV",
            "ipaddress": "<IP_ADDRESS>",
            "macaddress": "44:D8:78:8A:E9:5C",
            "sslmode": "default"
        }
    ],
    "platform": "HiSenseTV"
}

Screenshots:

Environment:

Plugin Version: v2.0.2
Homebridge Version: 1.8.2
Node.js Version: v20.12.2
NPM Version :10.5.0
Operating System:Docker

I've checked network interface, changed SSL to disabled also I run the pair script and I got the same error so it can't pair

Thx for reporting. @MrAsterisco already added that part in the readme :)

And I also created a PR to the python plugin here to fix this issue for newer versions of paho-mqtt.
But just to clarify:
These changes won't make it into this plugin anymore.
In the next few days I am going to merge the PR #62 here which entirely removes the python plugin, and instead does all the communication natively in JS. It will improve the responsiveness and some other things. (When its ready, the config needs to be updated so watch out for that)
I will let this issue stay open and add another comment when I created a release for v3. To keep you up to date ;)

@Luccio96 I just released a beta for version 3. You can update to it in homebridge, if you go to the plugins and click on manage versions :)
Would be great if you read through the readme here again as the config changed a bit.
For example you need to replace the ifname with your homebridge MAC address and so on...
Please also leave a comment here if it works ;)

Linked PR on the Python plugin is merged!

@Luccio96 I just released a beta for version 3. You can update to it in homebridge, if you go to the plugins and click on manage versions :)
Would be great if you read through the readme here again as the config changed a bit. For example you need to replace the ifname with your homebridge MAC address and so on...
Please also leave a comment here if it works ;)

Is possible to have the changelog between 3.0.0 and 2.0.2 version?

@Luccio96 I just released a beta for version 3. You can update to it in homebridge, if you go to the plugins and click on manage versions :)
Would be great if you read through the readme here again as the config changed a bit. For example you need to replace the ifname with your homebridge MAC address and so on...
Please also leave a comment here if it works ;)

Is possible to have the changelog between 3.0.0 and 2.0.2 version?

Sure. After upgrading in the homebridge-ui its visible or here
This config should do the same, as the one you provided in the issue (if the ssl mode 'default' worked for you). You just need to input the mac address of your homebridge instance:
{
    "macaddress": "<your homebridge mac address>",
    "devices": [
        {
            "id": "hisensetv43",
            "name": "TV",
            "ipaddress": "<IP_ADDRESS>",
            "tvType": "default",
            "showApps": false,
            "apps": [],
            "macaddress": "44:D8:78:8A:E9:5C",
            "sslmode": "default"
        }
    ],
    "platform": "HiSenseTV"
}

Hey @Luccio96 did you install the beta?
I am currently the only one testing the plugin, so thats why I am asking.
If yes did it work?

Yes I did, updated also paho-mqtt to version 2.1.0 without errors. (Yes I know you have removed the usage of python plugin but want to test it..)
Nice have to switch to all apps! 😀

Ahh thats nice to hear :)
All apps are like 200 on my system and I don't know why. Never installed these xD
But the good thing is you can filter them if you put the app name in the apps array like
"devices": {
      ....
      apps: ["Netflix", "Prime Video"],
     ....
}

If you encounter any problems, please open an issue again 👍


netbird: 0.32.0 -> 0.33.0

https://github.com/netbirdio/netbird/releases/tag/v0.33.0
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 358249

x86_64-linux

:white_check_mark: 2 packages built:

netbird
netbird-ui


Standardize permissions and executions on MySQL schemata: Char %60 (`)

Current permissions on MySQL schemata do not include character %60 (`) but SuperSet uses such character in the Preview option of SQL Lab. Therefore even if a user has access to a schema the preview option will fail due to permissions.
Bug present on SuperSet 1.1.0 installed from PyPi

This happens with both mysqlclient and PyMySQL drivers.

@dpgaspar may be able to help answer 🙏

@qlands I was able to reproduce, possible bug

https://github.com/apache/superset/blob/3456dd571ca705699766473e55ededd36c6f4dc7/superset/sql_parse.py#L212
This uses sqlparse.sql.remove_quotes() which does not remove backtick `
https://github.com/andialbrecht/sqlparse/issues/628
Maybe can override that function or send a PR to sqlparse instead.

This has been fixed in sqlparse 0.4.3 but testing is required to check if sqlparse 0.4.3 does not break things

It seems we're using sqlparse 0.4.3, so I'm going to optimistically close this as resolved. If anyone still sees an issue (particularly in Superset > 1.5.2), I'm more than happy to re-open this and get more eyes on it!


Add files via upload

@Ghost001195 lib/domains/student.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@Ghost001195 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Faster audio output/processing

Possible to use this in real-time communications? Compared with just azure it's slower and I have the deepl API to talk with foreigners. I'd like to get the audio within 200 ms and output it to a sound device, if it's feasible.

Outputting to default speaker should be as fast as the demo on the trial page. If you are outputting to an audio file, it's slow.

I'm outputing to speakers and it's slower

should I switch to stream mode?

How slow is it? I didn't experience significantly large delays compared with the demo.

quarter as slow

I just did a profile:
python -m cProfile -m aspeak -t

         2860752 function calls (2854737 primitive calls) in 34.520 seconds

   Ordered by: standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000   34.021   34.021 __main__.py:1(<module>)
        2    0.000    0.000    0.399    0.199 auth.py:1(<module>)
        1    0.000    0.000    0.879    0.879 auth.py:10(_get_auth_token)
        1    0.000    0.000   32.147   32.147 functional.py:11(pure_text_to_speech)
        1    0.000    0.000   33.983   33.983 main.py:122(main)
        1    0.000    0.000    0.948    0.948 main.py:18(read_file)
        1    0.000    0.000    0.000    0.000 main.py:25(preprocess_text)
        1    0.000    0.000   32.147   32.147 main.py:46(speech_function_selector)
        1    0.000    0.000   33.095   33.095 main.py:69(main_text)
        1    0.290    0.290   32.146   32.146 provider.py:36(text_to_speech)
      2/1    0.000    0.000    0.498    0.498 runpy.py:103(_get_module_details)
        1    0.000    0.000   34.520   34.520 runpy.py:199(run_module)
        1    0.000    0.000   34.022   34.022 runpy.py:63(_run_code)
        1    0.000    0.000   31.820   31.820 speech.py:1565(speak_text)
        1    0.000    0.000   29.846   29.846 speech_py_impl.py:6148(speak_text)

34.520s is the total time.
34.021s is the time spent in main.
33.893s spent on the main.py
32.146s spent on text_to_speech function in provider.py
0.948s spent on reading from stdin
0.879s spent on getting the auth token.
31.820s spent by azure's speech package to do the actual speech synthesis work which is out of my control.

So the space for optimization is 33.893 - 31.820 - 0.948 - 0.879 = 0.24600000000000044
Actually there is almost nothing to optimize, except:
https://github.com/kxxt/aspeak/blob/e3b1b4418f8d33ba4926f8216a235cbf3dd2e996/src/aspeak/api/provider.py#L40
We could cache the synthesizer here if you are always using the same parameters for text_to_speech.

I can provide an API with cached SpeechSynthesizer in the next version but I'm very busy recently so don't expect that to arrive very soon.
You could do it yourself by building your own version of SpeechServiceProvider if you are always calling text_to_speech/pure_text_to_speech with the same set of parameters

Create and store your SpeechConfig and AudioOutputConfig in it.
Just cache the SpeechSynthesizer and recreate it using the same config in case of token expiration.
Modify text_to_speech and ssml_to_speech method on your SpeechServiceProvider to utilize the cached SpeechSynthesizer and remove the config parmeters from the methods.
Call SpeechServiceProvider.text_to_speech(text) or  SpeechServiceProvider.ssml_to_speech(ssml) to do speech synthesis (You can create ssml using the create_ssml function in aspeak.ssml)

However, frankly speaking, I don't know by how mush will the performance improve.

Actually I don't think the 200ms delay is realistic.
I opened https://eastus.tts.speech.microsoft.com in a browser and I got 268ms delay

Thanks


search-ui: consistent comma separators for large numbers

Large numbers displayed in the results/aggregations/pagination should have thousands comma separators (i.e. 12,345 vs 12345).

The issue with the facet comma separator has been fixed, but the pagination comes from the behaviour in react-semantic-ui. You can edit the examples here to demonstrate https://react.semantic-ui.com/addons/pagination/ As such we would probably need to contribute to the repository to fix this issue
The two linked pull requests solve separate but similiar issues


Develop and implement PDS CD Strategy

For both on prem and AWS services

:calendar: August status: deferred to B12.1 due to increased scope on Continuous Integration effforts

completed initial design:
EN Deployment Lifecycle.pdf

Looks good, thanks @jordanpadams! 👯


Added the documentation of Mozilla Public License 2.0

Description 📜
I have created documentation on Mozilla Public License 2.0 which gives a brief description about it and fixes #4694. Kindly look into it

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Open Source

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@Aryamanz29  I have made my PR kindly go through it


QoS test random port order

It would be nice, if order of ports in QoS was random. Please let me know if is there chance of implementing this feature in future.
Matyas Latner (CZ.NIC)

Wow


.sublime-settings detected as JavaScript

Why is .sublime-settings detected as JavaScript file?
There is everything for Sublime Text marked as JavaScript files, but a lot of them are JSON, aren't they?

Those extensions were moved in #1888 to JavaScript for syntax highlighting reasons apparently (they allow comments so technically, they are JavaScript files).


Fix dynamic linking + bump to version 3.5.1

Create a wrapper that sets LD_LIBRARY_PATH so pulseaudio and alsa are properly linked at runtime:
This fixes godot failing to load the audio driver and falling back to dummy.
Also link udev for controller hotplugging.

Update to Godot 3.5.1

Looks good, thanks!


Add crwbok in the list

Hi,
I find this list very useful and I think crowbook might be included in it : https://github.com/lise-henry/crowbook
However I've not tested it and specially how to seamlessly cite references part.
Noé

Interesting! What about the other features: latex equations, and ability to reference internal figures and sections? I tried to figure out myself, but the documentation on usage is missing. Also, the line in their README is a bit unclear:

Crowbook tries to correctly translate local links in the input Markdown files: e.g. if you have a link to a Markdown file that is part of your book, it will be transformed into a link inside the document.

It would be nice if you can have a quick test run. Pull requests are welcome by the way :)

Crowbook depends on LaTeX to produce PDF and has a lot of untested features that are required for scientific writing. I cannot see at the moment why this tool should belong in this list.


improve documentation, easily

just copy & paste https://github.com/m-ender/retina/tree/master/Examples/README.md to the wiki page! very easy

Eh, those two documents serve very different purposes, and the tutorial only covers a small fraction of the language features. I'll link to it from the wiki though.


refactor: streamline local endpoint discovery

To avoid the issues seen when setting up an iroh-net node, this allows to dynamically subscribe to endpoint changes. It also removes the other callbacks on the magicsock, which where unused.

How is progress here? This is kind of a blocker for https://github.com/deltachat/deltachat-core-rust/pull/5041


Allow custom requests for keys without file extensions

Issue #, if available:

#268
Description of changes:
Removed the regex that explicitly checks for existence of a file extension with custom requests
Checklist

[x] :wave: I have run the unit tests, and all unit tests have passed.
[ ] :warning: This pull request might incur a breaking change.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@SNagappan thanks for your contribution, and we will take a look at this one.

@SNagappan, thank you for your contribution.
We have updated our solution, and your pull request has been merged into our main branch. However, as we've merged many pull requests at this time, the source code might not exactly same as what you've done. In addition, due to our internal process, we've merged source code manually, so please understand how your effort has been merged.
You can refer to the recent changes here.


TPC-C microbenchmark

Fix #335. Exercises storage (tables, indexes, logging, GC) and concurrency control of the system.
I need to write a good readme for anyone who might want to use this later, but otherwise this is done.

Without seeing a log for the failure on tpcc_test, I have to believe it's the memory leak in the bwtree that I reported to @wangziqi2013. Still waiting on a fix for that before we merge this.

Is this ready to be setup to run nightly?

I could disable the correctness test for now if we at least want benchmark results. The failure on correctness is ASAN reporting a leak in the BwTree, but the benchmark should be valid.

Will be good in the next two days. Already fixed it, now integrating back to the repo and running regression tests.

Thanks Ziqi!


Create a test web page in sign-and-verify with deeplink and CHAPI 'get'

Create a web page in sign-and-verify (as a route that returns HTML) that provides:

a deep link into the LCW
a button that invokes a CHAPI 'get' containing a VPR

The deeplink will be preconfigured to call the forthcoming '/exchange/{exchangeId} endpoint, where the {exchangeId) will be called 'test' and the 'challenge' will also be called 'test'.  So, the deeplink would have params like so:
auth_type: 'bearer'
vc_request_url: '/exchange/test
challenge: 'test'
The deeplink will open the LCW, and the LCW will sign a DIDAuth containing the challenge and the holder DID, then call the vc_request_url (which is just another route in the same sign-and-verify as the web page).
The sign-and-verify exchange endpoint would need to recognize the 'test' exchangeId and issue a preset test credential.
The CHAPI invocation will do more or less the same thing but passing in a VPR on a CHAPI 'get' request.  The VPR will specific the endpoint and the challenge, and would likely look like this:
https://w3c-ccg.github.io/vp-request-spec/#example-example-interact-request

Closing but we will create a demo site soon using new sign-and-verify refactoring


Support loading dispatcher metadata from cached functions

Feature request
I would like to look at the dispatcher metadata information on a cached function. However, when loading from cache this data isn't written to the cache, so functions that access the metadata fail when loading from cache succeeds. Here is a reproducer:
import numba
import numpy as np

@numba.njit(cache=True, parallel=True)
def g(A, n):
    B = A + n
    return B

g(np.ones(4), 10)
g.parallel_diagnostics()

The first time this runs successfully, but the output when loading from cache is:
Traceback (most recent call last):
  File "/Users/nicholasriasanovsky/Documents/bodo/nick-numba/test_cache.py", line 10, in <module>
    print(g.parallel_diagnostics())
  File "/Users/nicholasriasanovsky/Documents/bodo/nick-numba/numba/core/dispatcher.py", line 1027, in parallel_diagnostics
    [dump(sig) for sig in self.signatures]
  File "/Users/nicholasriasanovsky/Documents/bodo/nick-numba/numba/core/dispatcher.py", line 1027, in <listcomp>
    [dump(sig) for sig in self.signatures]
  File "/Users/nicholasriasanovsky/Documents/bodo/nick-numba/numba/core/dispatcher.py", line 1019, in dump
    pfdiag = ol.metadata.get('parfor_diagnostics', None)
AttributeError: 'NoneType' object has no attribute 'get'

Any feedback you have on the best way to go about this would be greatly appreciated.

Summary from the meeting discussion. The metadata serves a general "trash can" of information that anyone can write to. The proposal is to let people contribute information that must/should be cached to a new "cached_metadata" field that will be easier to manage.

If this were to be implemented, where would be a good place to put the cached metadata?

If this were to be implemented, where would be a good place to put the cached metadata?

There's probably two parts to this:

Where and how to expose such a cache to users of Numba

I'm not sure if it's necessary to differentiate between cacheable and uncacheable metadata from the point of view of the user. I imagine users will just want to know what the data is, whether it's cached or not probably doesn't matter? Or is there some specific case where knowing this is useful? To this effect I'm wondering if the existing get_metadata on the dispatcher should retrieve this, however an issue arises through reuse of this method in that it already addresses the metadata dictionary on a compile result object and addressing two dictionaries will potentially lead to problems with duplicated keys. I think this means there either has to be a new method e.g. get_cached_metadata(), or a kwarg e.g. get_metadata(cached=True) to the method that would make it possible to differentiate between the two dictionaries, or some API added to make it clear whether metadata should be cached or not at the point of addition this permitting the hiding of the implementation details for addition/retrieval. Alternatively, the idea proposed in the public meeting by @sklam where the keys in the current metadata dictionary have a "cacheable" flag, should allow similar. This potentially needs a short discussion at the next public meeting.

Where to actually hold a reference to the cached metadata.

Assuming that this cached metadata is implemented as a new dictionary, it probably needs adding to the numba.core.compiler.CompileResult, with appropriate updates made to the _reduce and _rebuild methods.

Following on from a bit of discussion at today's public meeting, most of 1. above was me forgetting that the API doesn't accept a key into the metadata, it just retrieves the whole thing. It's therefore probably fine to just have a get_cached_metadata cf. get_metadata on the dispatcher object.


can I change setting with option: debug or release

can I change setting with filter debug or release
when I use write function, this will also change debug configuration,but i don't mean it,so can you add option?

this is resolved in 0.2
https://github.com/0xced/xcproj/issues/10
so I close this issue


Passing DevSkim Application Inspector rules can cause an index to be found that is out of range of the file

Describe the bug
As seen in https://github.com/microsoft/OSSGadget/issues/290 if you use devskim with Application Inspector rules (not officially supported) this can cause an out of bounds detection for an index.  Regardless of that the rules may not be valid - the OAT operations we implemented should not return out of bounds indexes.
To Reproduce
Run devskim with the fully packed application inspector rules against pkg:/left-pad:1.3.0 on oss-download.
Expected behavior
Indexes are all inside the file.

Will be fixed with refactor to use AI engine in 0.7

The latest DotNet devskim uses the AI engine so this is now moot.


update backup script

Summary
Related issue(s)
Fixes #

Just a reminder to update the global hub document. @ldpliu thanks.


Mobile phone scaling issues?

Some people are reporting they can't fit the diagrams in screen on their phone.
eg. https://twitter.com/AlxCoventry/status/849462418992443392

Fixed

Just saw this on my phone, it looks good 👍


chore/release: prepare 0.3.0 release

@homu r+

:pushpin: Commit 6c84d33 has been approved by hobofan

:zap: Test exempted - status


drrun only run once with a specific program and does not generate logs

Hi,
I'm trying to fuzz-test my program using the instrumentation mode of DynamoRIO. However, it looks like my program is NOT running correctly under DynamoRIO.
I'm Running:
drrun.exe -c winafl.dll -debug -coverage_module mycode.exe -target_module mycode.exe -target_offset 0xB0F00 -fuzz_iterations 10 -nargs 0 -- "<path>\mycode.exe".
This only runs my program once (I know by the number of prints) print every print inside my function (and nothing else), and exit. It does not generate any logs.
I added a print placed right before the function's end, so it does not look like my function aborts unexpectedly (no exit()). Also, Procdump does not detect any crash.
Any ideas?
Sanity Tests:

Running drrun.exe with test_gdiplus.exe instead works perfectly (run 10 times, and the log is created).
Running another simple program (that I just compiled) that only prints works fine as well (but that's not the real program I'm trying to fuzz-test).
Wrap my function with a for loop (to run 10 times), and run it manually (without drrun) from the main function works perfectly (so it does not look like there is unexpected exit()).

Additional Details:

OS Win 10 (19042) x64. [Also tried with Win7 x64 VM, and got exactly the same issue].
I compiled DynamoRIO-Windows-8.0.18585 x64 with the latest winafl.
My program is x64 and was compiled with MSVC.
The target offset was calculated using WinDbg by subtracting the module base from the function address.

Thanks!

Strange that the log doesn't get created at all as creating the log file should be one of the first thing it does when -debug is specified. Can you verify that all three (drrun.exe, winafl.dll and target) are built for the same architecture (32-bit vs 64-bit). Does drrun.exe print anything in the terminal?

Hi,
Indeed very strange. I verified the architecture of the three files again, all are x64.
drrun.exe does not print anything in the terminal other than my program prints. My program prints include prints that are at the very end of the program, as I described.
Any thoughts?
P.S.
I even did another sanity test: I also made it work by commenting out all of the code in my program (and make drrun calling an empty function with only one print).
I couldn't be able to pinpoint the exact code in my program that interferes with drrun. The program uses threads, but I don't see any limitation regarding that in the winafl docs.
Thanks!

If this really is due to some incompatiblity with DynamoRIO, an alternative is to try the newly released https://github.com/googleprojectzero/Jackalope. It uses completely different instrumentation so it might work better for you. Note that the command line is somewhat different.

Thanks, I get much further with that fuzzer; however, I still got an issue.
I think the underlying cause might be the same the same. WDYT?
Thanks!


Clickhouse auto completion doesn't work well

On version <IP_ADDRESS>810201753, when I write select * from, then I type first few letters (let's say "def"), I get database auto completion list, with default in list.
If I select default with keyboard arrows or mouse i get defaultdef, so I have to delete def from the right side in order to continue.
The same is with field names. It used to work well in previous dbeaver versions.
I am connected to the Clickhouse database.

This was already reported and 5.2.3 re-released. You need to visit dbeaver.io and download and install 5.2.3 again!

@p91paul
Well if it is reported and solved, you should increment the version, and offer it through auto update process.

I agree with you, that is why I opened bug #4490. I'm just a user here!

@ghuname This particular issue was fixed in the very same day of 5.2.3 release. Making two releases in the same day is a bit strange.
So we decided to make a hotfix build. But I agree that we need some special procedure for such cases.


rebuild r-3.6

@conda-forge/r
since https://github.com/conda-forge/r-base-feedstock/pull/89, the R package is not building an internal Rblas anymore and instead is using libblas package.
so any package compiling with -lRblas will fail on R-3.6

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

intermittent error on osx: conda.CondaMultiError: HTTP 503 SERVICE TEMPORARILY UNAVAILABLE for url <...>

@rvalieris Nice work! @croth1 @bgruening @ocefpaf Ready to merge :)


Fix current longrun

Closes #774
resulting build

[x] I have read and checked the items on the review checklist.

In the linked build, the MPI AMIP FINE runs with topo and with topo + diagedmf fail after 3 days and 1 week respectively. Aren't these the runs that we expected to run for ~300 days?


Feature/5e87

👷 Deploy Preview for zeti-tlp-dev processing.

Name
Link

🔨 Latest commit
b3962ccebb64c7bfc79c7287179cc91ab8db452f

🔍 Latest deploy log
https://app.netlify.com/sites/zeti-tlp-dev/deploys/65296f8a0cb2e80009fa001b


db-postgres: is like filter condition does case-insensitive text search and the result is equivalent to contains filter

Link to reproduction
No response
Describe the Bug
Both of is like and contains filter does case-insensitive search by postgres ILIKE operator, and the issued SQL and search results are idential.
I guess that is like should do case-sensitive search by postgres LIKE operator.
To Reproduce
You can reproduce the problem by _community app:
Filter by is like condition

SQL
select "posts"."id", "posts"."text", "posts"."title", "posts"."updated_at", "posts"."created_at", "posts__rels"."data" as "_rels" from "posts" left join lateral (select coalesce(json_agg(json_build_array("posts__rels"."order", "posts__rels"."path", "posts__rels"."media_id") order by "posts__rels"."order" asc), '[]'::json) as "data" from (select * from "posts_rels" "posts__rels" where "posts__rels"."parent_id" = "posts"."id" order by "posts__rels"."order" asc) "posts__rels") "posts__rels" on true where "posts"."text" ilike $1 order by "posts"."title" asc limit $2

Filter by contains condition

SQL
select "posts"."id", "posts"."text", "posts"."title", "posts"."updated_at", "posts"."created_at", "posts__rels"."data" as "_rels" from "posts" left join lateral (select coalesce(json_agg(json_build_array("posts__rels"."order", "posts__rels"."path", "posts__rels"."media_id") order by "posts__rels"."order" asc), '[]'::json) as "data" from (select * from "posts_rels" "posts__rels" where "posts__rels"."parent_id" = "posts"."id" order by "posts__rels"."order" asc) "posts__rels") "posts__rels" on true where "posts"."text" ilike $1 order by "posts"."title" asc limit $2

Payload Version
2.22.0 (db-postgres: 0.8.5)
Adapters and Plugins
No response

This was intentionally done. We did this to match the functionality of the MongoDB adapter. We could potentially add an additional operator for case-likeness queries, but this is not planned.


Detect IP Automatically

Hi,
Is there anyway we could let openvpn server automatically detect the host IP. Because what i'm doing is making a copy , I wondering if there's anyway to not setup or edit after doing it once?
I assume the .ovpn needs to be re-generated when the server ip changes?
Please advice.

For security reasons copies aren't recommended.
No, there is no way to automatically detect server public IP. You can use a DDNS if you don't want to make any edits, but you have to change the IP of that domain every time you want to connect to another server. So I don't think this can help you.

If there server's IP change, you have to update your .ovpn files with the new IP and import them again.


Issue with k8s.io/docs/tutorials/

This is a Bug Report

Problem:
Proposed Solution:
Page to Update:
https://kubernetes.io/...

Hi @Henry-hexijun
What wasn't right with the page you were looking at?
/triage needs-information


/giveLegacies has a misleading title

If you retype in this command, it wipes any legacies you had before. So, I did it once, and I got glacien, I put in the command, expecting more, and I got Lumen, but I did not have glacien anymore.

Yeah, it's by design. If you want to get more legacies, that's where the Loric Stone comes in. I should rename it to /regiveLegacies.

Yeah, it's by design. If you want to get more legacies, that's where the Loric Stone comes in. I should rename it to /regiveLegacies.

yeah, and have /giveLegacy ______ only for creative or something

yeah, and have /giveLegacy ______ only for creative or something

AFAIK it already should be

AFAIK it already should be


Use coverlet.collector built to master failed

Run coverallsapp/github-action@master
  with:
    github-token: ***
    path-to-lcov: ./specs/Qowaiv.Specs/**/coverage.info
    coveralls-endpoint: https://coveralls.io/
    debug: false
  env:
    DOTNET_ROOT: /home/runner/.dotnet
Using lcov file: ./specs/Qowaiv.Specs/**/coverage.info
Error: ENOENT: no such file or directory, open './specs/Qowaiv.Specs/**/coverage.info'

See: https://github.com/Qowaiv/Qowaiv/actions/runs/10856017939/job/30129839393

Seems to have been resolved by #413.

I think you're right. I was looking at an old issue, not the latest build. Me bad.


fix infinate print null point exception for trace bug #1701

resolve https://github.com/lettuce-io/lettuce-core/discussions/1701

Make sure that:

[x] You have read the contribution guidelines.
[x] You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
[x] You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
[x] You submit test cases (unit or integration tests) that back your changes.

just added a non-empty judgment

I just just added a non-empty judgment ,and I don't know why
codecov/patch — 40.00% of diff hit (target 79.71%)
these happened?(｀・ω・´)

the branch I choose  is wrong.I will close this merge.


routines:tls_process_ske_dhe:dh key too small

Hi, I'm receiving the following error from openssl (Version 1.1.1d on debian 10)
error trying to connect: error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small:../ssl/statem/statem_clnt.c:2150:

I would like to configure openssl in code to allow small keys, is there any way to do that? I have tried by changing to rustls but that generates other ssl problems.
Thanks

I don't know how to help. You could check the rust-openssl repo.

Please check the domain you are trying to connect to on https://www.ssllabs.com/ssltest/ and https://hardenize.com and ask its admin to fix it, otherwise report it to the data protection authority. Thanks ;)
(If it's some legacy device, put at least a recent nginx as reverse proxy in front of it.)


Update hibernate-resume-troubleshooting-windows.md

Added details for power service check

@mattmcinnes

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[turborepo] code generator not working.

What version of Turborepo are you using?
1.10.16
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Windows
Describe the Bug
Turborepo generators used to work well in my repo. However, after recent updates, it doesn't work.
When I run yarn turbo gen it throws following error.
>>> Unexpected error. Please report it as a bug:
error TS6053: File 'tsconfig/base.json' not found.

Repo - https://github.com/react18-tools/react18-themes
Expected Behavior
Turborepo generators should generate the expected files without throwing meaningless errors.
To Reproduce
git clone https://github.com/react18-tools/react18-themes.git
cd react18-themes
pnpm i
pnpm turbo gen

Throws error.
Reproduction Repo
https://github.com/react18-tools/react18-themes

I'm having the same issue. Please note that your repo under Reproduction Repo is not accessible (Page not found).

I'm having the same issue. Please note that your repo under Reproduction Repo is not accessible (Page not found).

Hi, thanks for the observation. I have updated it - https://github.com/react18-tools/react18-themes

Taking a look!

Thanks for the diagnosis.


Colors get stripped

I have the following scripts:
  "scripts": {
    "lint": "jshint .",
    "test": "tape test/index.js | tap-bail | tap-difflet",
    "c1:section5:example-1": "tape examples/software-testing/section5/example-1.js | tap-bail | tap-difflet",
    "c1:section5:example-2": "tape examples/software-testing/section5/example-1.js | tap-bail | tap-difflet",
    "dev": "watch --wait=5 'npm run lint && npm run test' ."
  }

When I run these scripts directly, they have color output (via tap-difflet). When I do npm run dev and use watch to launch the tasks, the colors are stripped.

I guess this is because tap-difflet does strip colors when not run as a tty. I am fixing this right now.

This should be fixed in 0.14.0. Can you confirm this?

Seems to be working now, thanks!


ACL based access

Hi,
Is there any description how to setup YiDB in a 'production like' style (if possible)?
To have REST API/Console with an authorization, role based access, etc.
Thanks in advance!

Hi,
Keystone ase source for token-based authentication and authorization look good. Probably this could be the fastest way to get YiDB with a proper ACL protection. Also it could provide 'for free' integration with LDAP, and other keystone features.


Parallel GD for infinite MPS

This PR adds some parallelization to GD using the @static and @spawn macros.

I understand that this is not a proper benchmark but I just compared the above code (executed on my desktop) with the non parallel code (executed a cluster) and got :
On the cluster
julia -t 32 with BLAS.set_num_threads(2) takes about 23 minutes for one gradient descent step
On my desktop
julia -t 16 with BLAS.set_num_threads(2) takes about 5 minutes for one gradient descent step
So this is a tremendous speedup !

These benchmarks don't really mean a lot like this, you are comparing on different machines with a completely different setup of threads... A better comparison could be:

a single-threaded run (1 julia thread, 1 blas thread)
a blas-threaded run (1 julia thread, all blas threads)
a julia-threaded run (all julia threads, 1 blas thread)
a half-half run (e.g. for 16 core machine: 4 julia threads, 4 blas threads, with MKL)

Using the first as a baseline, you would be able to deduce the efficiency of the multi-threading, i.e. performance gain per thread, comparing with how well BLAS does.

I'll do a better benchmark in the near future.
Apart from that, I don't think you ever mentioned wanting to change to OhMyThreads.jl I guess this makes this PR rather useless.
That being said, if this is something that's relevant now I could look into this. With schedulers you mean the underlying CPU scheduler right ? Or are these some settings in OhMyThreads ?

I would also be interested in seeing a breakdown of the time spent. I would assume that almost all time is spent calculating the environments, so it might be worthwhile to think about how we could parallelize those for large unit cells.

I switched out the parallelization for the OhMyThreads approach, which I think is a bit cleaner (and should be more versatile as well). Apologies that I didn't discuss this with you sooner, I thought I had mentioned this before.
It would be really nice if you could still add the benchmarks so we can have an idea if this helps, and the documentation still needs to be updated. Do you maybe have time for this @Gertian ? Let me know if something is not clear or I can help.

Looks like I did mess up something with the Grassmann stuff, given that the linesearch is complaining again...


update to 0.6.5

dataclasses-json 0.6.5 main
Destination channel: main
Links

https://anaconda.atlassian.net/browse/PKG-4683
https://github.com/lidatong/dataclasses-json/tree/v0.6.5
Relevant dependency PRs:

https://github.com/AnacondaRecipes/langsmith-feedstock/pull/3

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_650fsyejrd/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:22: missing_python: For pypi packages, python should be present in the host and run sections. Missing in {}
===== Final Report: =====
1 Error and 0 Warnings were found


Package.getActivationCommands is deprecated.

Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:
  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }

Package.getActivationCommands (/usr/share/atom/resources/app.asar/src/package.js:790:9)
Package.hasActivationCommands (/usr/share/atom/resources/app.asar/src/package.js:715:20)
<unknown> (/usr/share/atom/resources/app.asar/src/package.js:169:24)
Package.measure (/usr/share/atom/resources/app.asar/src/package.js:147:15)

Oops, I should have searched the closed issues, this one is a duplicate. But the original should be reopened, as this is still happening in version 1.4.0.

It's still happening in 1.4.0 because apparently they still haven't released a version that includes the fix :unamused:.
https://github.com/AtomLinter/linter-flake8/compare/v1.4.0...master

@dmbasso @Arcanemagus I'll release a version with fix in minutes.

@badray Thanks!

@badray Thank you. I'm curious to see what actually is the problem, because the activationCommands was defined in the package.json, though it was an array instead of an object. Could that be the cause?

@dmbasso This is the commit that fixes this issue: https://github.com/AtomLinter/linter-flake8/commit/53b8d3bbdf98884f9e3be4a6b701eb3d6ee03313

Now I understand, the fix was accepted long ago, only it was not apm published. I've seen that commit before, that's why I mentioned the possible array/object issue.

No problem :).
@dmbasso Ok I didn't know what you mean :D, as @Arcanemagus clearly said that fix wasn't released yet :).

Duplicate of #29.


cannot unmarshal !!str meta("k... into processor.confAlias

Trying to build a test from a switch-case structure which verifies a metadata key,
tests seem to having troubles parsing it
streams/check_key.yaml
input:
  label: "check_key"
  http_server:
    address: ""
    path: /path
    allowed_verbs:
      - POST
    timeout: 20s

output:
  switch:
    retry_until_success: false
    strict_mode: true
    cases:
      - check: meta("key") == "a_key"
        output:
          type: stdout

      - output:
          reject: "Message failed due to: Wrong key"
          processors:
            - log:
                level: ERROR
                message: "Wrong key"

streams/check_key_benthos_test.yaml
parallel: true
tests:
    - name: Wrong key
      environment: {}
      target_processors: check_key.yaml#/output/switch/cases/0/check
      target_mapping: ""
      mocks: {}
      input_batch:
        - content: Hello benthos
          metadata:
            example_key: a wrong key
      output_batches:
        - - content_equals: A SAMPLE DOCUMENT
            metadata_equals:
                example_key: some other value now

benthos test ./streams/check_key_benthos_test.yaml
Failed to execute test target 'streams/check_key.yaml': failed to resolve case processors from 'streams/check_key.yaml': line 15: yaml: unmarshal errors:
  line 15: cannot unmarshal !!str `meta("k...` into processor.confAlias

Hey @brivadeneira, this is because your test specifies a target processor at the path /output/switch/cases/0/check, but that path points to a bloblang mapping (the check field) and so the test is failing to parse it. Config unit tests don't support outputs right now so unfortunately there isn't much in this config that's possible to test in a useful way.

@Jeffail thanks for the quickly answer!!!


TTORRENT_HASHING_THREADS configuration read incorrectly

The static variables and blocks are executed in order they are specified in the java file. The hashing executor is created before the configuration is read from the system environment and therefore this configuration is never reflected in the code.
https://github.com/mpetazzoni/ttorrent/blob/db52f13ba709b26d9605d7ef18739cdaa7c5fc6d/common/src/main/java/com/turn/ttorrent/common/TorrentCreator.java#L364

@vswamy thanks for reporting! Do you think you'd be able to provide a PR with a fix? I'd be happy to review it and merge it!

@vswamy
Thanks you, i moved this code before creating executor. So i think now it works correctly

So fast. Thanks @Dead-off
I have another concern related to how the number of threads are created. The Executor is created when the class get's loaded by jvm and usually happens when the application is booting up that is, when most of the processors (cpu) is free.
Looking at the documentation of availableProcessors:
   /**      * Returns the number of processors available to the Java virtual machine.      *      * <p> This value may change during a particular invocation of the virtual      * machine.  Applications that are sensitive to the number of available      * processors should therefore occasionally poll this property and adjust      * their resource usage appropriately. </p>      *      * @return  the maximum number of processors available to the virtual      *          machine; never smaller than one      * @since 1.4      */
Should we be resetting the executor as the time goes by to reflect the CPU capacity available?

Thanks @Dead-off; closing this issue now then.


[bounty] make cursor not laggy

atm i have to restart cursor 10 times a day for some reason - no idea why, keeps crashing
i think it's indexing too many things
for example when i run bun tauri dev and change cloudflare backend stuff (unrelated) it would re-trigger the build, shouldn't
for the context i have apple macbook pro m4 max 128 gb ram so it should not happen
maybe it's something with tweaking some .vscode/settings.json or something else idk - maybe rust indexing too much stuff

/bounty 60

update:
i turned off all extensions except rust-analyzer and it seemed to have fixed the issue, will investigate more

update:
i turned off all extensions except rust-analyzer and it seemed to have fixed the issue, will investigate more

@louis030195 let me know which ones causes issues to fix in the config.json


ament build fails to find solution file when cmake project name differs from package manifest name

I was just attempting to build ign-math (cmake project name ignition-math4) with this package.xml file (package name ign_math) in an ament workspace on windows 10 with VS 2017. I was getting build failures expected str instance, NoneType found, that I traced to a missing solution file, which is named ignition-math4.sln. I modified the package.xml name to be ignition-math4 and then it worked.
Is this a strict requirement that the cmake project name must match the package.xml name?

Is this a strict requirement that the cmake project name must match the package.xml name?

No, but it is common practice. If you didn't use a package.xml then I think ament would have extracted the project name from CMake automatically.
I'm not sure if there is a way for us to "guess" the right solution file name each time. I guess we could do:

extract the project name

but you probably can override this setting in CMake (have a different solution file name from the project name)

look in the root build folder and assert there is only one .sln file and use that
something else?

The package manifest is the only reliable source for the package name in this case. I think it must match the project name used in CMake.

Detecting the project name based on the CMakeLists.txt will not work if the argument to project() is not a literal string.
Asserting for a single .sln is fragile. Nothing prevent a CMake project to have other projects in the same build space (might not be nice but users usually do anything imaginable).

The question is why should the name in the manifest not match the CMake project name? If I remember correctly we had a similar discussion before on some bitbucket ticket that adding the major version to the project name is a "weird" choice and that you could use the version information to query a specific version of the CMake package rather than appending the major version to the project name.
We also don't plan to support ament_tools in the future. I would suggest you should update the name in the manifest to match the CMake project. Arguably that will affect the packages declaring dependencies on this one (which is why I would suggest a naming scheme without the version number being part of the project name).

I will close this for now since I don't expect that we will support two different names for a package (manifest name being different than e.g. CMake project name). Please feel free to continue commenting here.

Sorry for replying to this old issue. Actually, I ran into a similar problem while trying to release libg2o into ROS2. I am trying to port the Bloom-ReleaseThirdParty workflow to ament. The original 3rd party package uses project(g2o) in the CMakeLists.txt while the ROS package is called libg2o, at least in ROS1. As a consequence, package and library files are installed into install/g2o/ rather than into install/libg2o.
I thought about patching project(g2o) in CMakeLists.txt, however, this requires many changes and potential dependency problems in the whole 3rd party project.
Has anyone already had experience with 3rd party packages, or is there already a best practice?


[GSB] Introduce resolveEquivalenceClass() and start using it.

Queries through the GenericSignatureBuilder about a particular type
parameter only really need information about the equivalence class in which that type parameter resides. Introduce a new entry point GenericSignatureBuilder::resolveEquivalenceClass() that only returns the equivalence class.
For now, resolveEquivalanceClass() is a thin layer over resolveArchetype().

@swift-ci please smoke test and merge


Sort matching types to the top when suggesting types

Steps:

empty profile to ensure this is not some setting I changed
have a method toString(alles: boolean, klar: number)
have local variables matching the types from another method in the class to call that method
invoke suggest

=> the list seems to be sorted in a way that does not suggest the most matching type at the position first
I think it would be great if the most matching types are sorted to the top and then I can just accept them.

The initial sorting is defined by extensions but @bpasero you can try editor.suggest.localityBonus which helps to disambiguate when all items have the same score. Then locality comes into play, it sometimes is a good workaround

It does not seem to help in this case. I have updated the description with how to reproduce by providing access to my playground source code.

Minimal example:
function foo(foo: boolean) { }

const a = 1;
const b = false;

foo()


Pytest doesn't work with IronPython

Apologies if this is something stupid, I don't have much experience with ctypes. I'm trying to figure out why pytest doesn't work with a new install of IronPython 2.7.7 and it seems like ctypes.pythonapi is missing some of its API functions. The following is adapted from here:
>>> import ctypes
>>> ctypes.pythonapi.PyString_FromStringAndSize
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Program Files (x86)\IronPython 2.7\Lib\ctypes\__init__.py", line 375, in __getattr__
  File "C:\Program Files (x86)\IronPython 2.7\Lib\ctypes\__init__.py", line 380, in __getitem__
AttributeError: function PyString_FromStringAndSize is not defined

Windows 10, IronPython 2.7.7 (<IP_ADDRESS>) on .NET 4.0.30319.42000 (32-bit)

The c API is not necessarily something we will implement. Also, please use 2.7.8

Does that mean that pytest will not work with IronPython, or is there a workaround you know about?

The IronPython2.7.8 msi installer is missing a bunch of files (including ipy.exe)

If pytest requres the C API, then it will not work with IronPython.

@slide - thanks, we are out of luck with pytest then.
@scaramallion - I used the 2.7.8 msi installer a few weeks ago and it worked fine (no luck with pytest though) - maybe your download was incomplete or something like that.

I'd like to have this open but change the title

You can probably try to work around the missing ctypes.pythonapi issue. It's only used in attr_compat.py (the attrs package).

It still doesn't work, even after doing that

Hello,
I'd like to confirm that pytest is not working on several versions of IronPython, I saw the issue already opened, I hope my investigations will help :

Tested with version 2.7.4  - no pip - no setup tools - impossible for me to install properly
Tested with versions 2.7.5/2.7.9 - raw config parser error

Tested also with 2.7.5/2.7.9 with IronPython pytest dedicated branch manual setup.py install

I/O Operation error

Tested with the X:Frames command  as explained here :
Unable to fetch the good version of pytest or pip.

Forgive me for not knowing the git-hub netiquette, this is my first time posting here.
Have a good day!

@EmmanuelTramoy Thanks for the feedback.
The RawConfigParser issue is likely the same as https://github.com/IronLanguages/ironpython3/issues/546. I believe you could bypass this by getting rid of the comments in the regex strings of backports\configparser\__init__.py.
Not sure about the I/O operation on closed file issue.

@slozier   Thanks very much, it is indeed solving the issue for this particual problem.
I am now falling back to the I/O issue unfortunately:
PS C:\Users\etramoy> & "C:\Users\etramoy\Documents\Tests\OfficialIronPython\ipy.exe" -m pytest
Unhandled exception:
Traceback (most recent call last):
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\runpy.py", line 187, in run_module
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\_pytest\config\__init__.py", line 63, in main
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\_pytest\config\__init__.py", line 206, in _prepareconfig
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\runpy.py", line 81, in _run_module_code
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\runpy.py", line 72, in _run_code
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\pytest.py", line 102, in <module>
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\pluggy\hooks.py", line 289, in __call__
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\pluggy\manager.py", line 87, in _hookexec
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\pluggy\manager.py", line 78, in <lambda$257>
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\pluggy\callers.py", line 203, in _multicall
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\_pytest\helpconfig.py", line 94, in pytest_cmdline_parse
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\site-packages\pluggy\callers.py", line 81, in get_result
  File "<string>", line 3, in _reraise
ValueError: I/O operation on closed file

@EmmanuelTramoy Did a bit of digging and it looks like the issue is essentially the same as https://github.com/IronLanguages/ironpython2/issues/92. The whole file descriptor handling of IronPython is unfortunately somewhat problematic... Was able to get around it by removing the with f: in _pytest\capture.py:
f = TemporaryFile()
with f: # remove this line!
    tmpfile = ...

It then failed with TypeError: data must be str, not bytes somewhere which is likely because str == unicode with IronPython 2.7 (instead of the str == bytes of CPython 2.7).
Perhaps the pytest-ironpython branch you linked above works around some of these issues?

@slozier ok we advance but still kinda stuck here, but maybe can you can give some insights.
I installed the Iron python version with pip install . in the official release of IronPython 2.7.9
Launch pytest, have the following error as expected :
PS C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366> & "C:\Users\etramoy\Documents\Tests\OfficialIronPython\ipy.exe" -m pytest
Unhandled exception:
Traceback (most recent call last):
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\runpy.py", line 187, in run_module
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\runpy.py", line 81, in _run_module_code
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\config.py", line 628, in pytest_cmdline_parse
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\config.py", line 702, in _preparse
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 412, in __call__
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\capture.py", line 69, in _getcapture
  File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\runpy.py", line 72, in _run_code
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\pytest.py", line 10, in <module>
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\config.py", line 28, in main
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\config.py", line 80, in _prepareconfig
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 412, in __call__
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 423, in _docall
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 314, in execute
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\helpconfig.py", line 27, in pytest_cmdline_parse
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 314, in execute
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\config.py", line 731, in parse
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 423, in _docall
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 314, in execute
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\capture.py", line 51, in pytest_load_initial_conftests
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\capture.py", line 79, in init_capturings
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\capture.py", line 252, in __init__
  File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\capture.py", line 336, in __init__
ValueError: I/O operation on closed file

Then I did the modification in capture.py and it indeed unlocked the issue, but know I found another one :
PS C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366> & "C:\Users\etramoy\Documents\Tests\OfficialIronPython\ipy.exe" -m pytest
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\main.py", line 77, in wrap_session
INTERNALERROR>     config.do_configure()
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\config.py", line 610, in do_configure
INTERNALERROR>     self.hook.pytest_configure(config=self)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 412, in __call__
INTERNALERROR>     return self._docall(methods, kwargs)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 423, in _docall
INTERNALERROR>     res = mc.execute()
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 314, in execute
INTERNALERROR>     res = method(**kwargs)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\__init__.py", line 60, in pytest_configure
INTERNALERROR>     _load_modules(mode)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\__init__.py", line 141, in _load_modules
INTERNALERROR>     from _pytest.assertion import reinterpret  # noqa
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\reinterpret.py", line 50, in <module>
INTERNALERROR>     from _pytest.assertion.oldinterpret import interpret as reinterpret_old
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\oldinterpret.py", line 3, in <module>
INTERNALERROR>     from compiler import parse, ast, pycodegen
INTERNALERROR> ImportError: No module named compiler

From what I understand, it is missing the compiler module, so for the sake of testing I tried to copy the compiler folder from the official Python (not IronPython) 2.7.9 and then :
PS C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366> & "C:\Users\etramoy\Documents\Tests\OfficialIronPython\ipy.exe" -m pytest
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\main.py", line 77, in wrap_session
INTERNALERROR>     config.do_configure()
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\config.py", line 610, in do_configure
INTERNALERROR>     self.hook.pytest_configure(config=self)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 412, in __call__
INTERNALERROR>     return self._docall(methods, kwargs)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 423, in _docall
INTERNALERROR>     res = mc.execute()
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\core.py", line 314, in execute
INTERNALERROR>     res = method(**kwargs)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\__init__.py", line 60, in pytest_configure
INTERNALERROR>     _load_modules(mode)
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\__init__.py", line 141, in _load_modules
INTERNALERROR>     from _pytest.assertion import reinterpret  # noqa
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\reinterpret.py", line 50, in <module>
INTERNALERROR>     from _pytest.assertion.oldinterpret import interpret as reinterpret_old
INTERNALERROR>   File "C:\Users\etramoy\Downloads\dahlia-pytest-ironpython-bd8990f67366\_pytest\assertion\oldinterpret.py", line 3, in <module>
INTERNALERROR>     from compiler import parse, ast, pycodegen
INTERNALERROR>   File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\compiler\__init__.py", line 27, in <module>
INTERNALERROR>     from compiler.transformer import parse, parseFile
INTERNALERROR>   File "C:\Users\etramoy\Documents\Tests\OfficialIronPython\Lib\compiler\transformer.py", line 29, in <module>
INTERNALERROR>     import parser
INTERNALERROR> ImportError: No module named parser

I'm pretty sure it's talking about this parser, but I cannot seem to find a corresponding file, doc is talking about "built'in" python module, maybe it's not accessible? I can't seem to see a matching name with matching functions (expr(), suite())
Thanks a lot for your help !

Unfortunately the parser built-in module is not implemented in IronPython so trying to use that old pytest-ironpython branch may be a dead end.
I've had some success with the latest pytest:

ipy -m pip install pytest
remove the comments from the regex in backports\configparser\__init__.py
remove the with f: in _pytest\capture.py
replace isinstance(data, six.binary_type) with isinstance(data, (bytes, six.binary_type)) in pathlib2\__init__.py
ipy -m pytest

@slozier Nice it's working on my side thanks !I just had to update to a later version of pip (18.1) to not have deprecation warnings. Also the tests take twice as long but it's working.
I'm not used to the working model here? Should I make a branch, try to push the changes for a PR?
Thanks a lot again for helping !

@EmmanuelTramoy Hmm, I'm not sure since these tweaks involve multiple 3rd party packages (configparser, pytest, pathlib2). I guess you could maintain a branch with the tweaks and all the dependencies?
Changes 2 and 3 could be addressed on the IronPython side of things by fixing the issues I referenced in previous comments. The changes required because str == unicode (such as 4) are more problematic and would probably ipy specific code in each of the 3rd party package where these issues occur.
Some other issues I ran into when testing:

_pytest\warnings.py: warning_record_to_str can get stuck in a loop and crash, was able to bypass by getting rid of the if compat._PY2 block.
_pytest\python.py: in hasinit changed to init != object.__init__ to init is not object.__init__. Cause by https://github.com/IronLanguages/ironpython2/issues/650


v0.2.0 todo

[x] default export.
[x] Figure out why import intellisense sometimes keeps suggesting the dist folder.
[ ] write more tests, to cover the function arguments as well.
[x] Change package description
[ ] start with the readme.
[x] Rename the function toChangeSet, since it refers to the type Changes and not ChangeSet.
[x] remove the type ChangeSet.
[x] Consider removing the Change and Changes types.
[x] Throw error instead of returning empty object in get() for the leaf values that do not exist; use has() instead.
[x] Return the changed leaf instead of type Change in findChanges(), given it's a special case for the mapLeaf() argument and harder to programatically read.
[x] Consider the return type of toTree(), as other than unknown. [object]

About the weird imports directly to ./dist
https://github.com/typescript-eslint/typescript-eslint/issues/5586


Charts - Increase the dapr-operator and dapr-placement delay seconds

Description
When I use Argo CD to deploy the Dapr, some components (Operator and Placement) need more time to start.
Sometimes the Argo CD may kill/restart the pods because of the health check.
So I think it's a easy and safe way to increase the initial delay and period seconds
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing

Instead of changing the defaults globally in Dapr, isn't it better to use the already configurable settings to increase the delay for your Argo deployment?

{{- if eq .Values.debug.enabled false }}
          initialDelaySeconds: 5
{{- else }}
          initialDelaySeconds: {{ .Values.debug.initialDelaySeconds }}
{{- end }}

Maybe we should accept the custom params when Values.debug.enabled = false?

{{- if eq .Values.debug.enabled false }}
          initialDelaySeconds: 5
{{- else }}
          initialDelaySeconds: {{ .Values.debug.initialDelaySeconds }}
{{- end }}

Maybe we should accept the custom params when Values.debug.enabled = false?

That's a much better idea.

{{- if eq .Values.debug.enabled false }}
          initialDelaySeconds: 5
{{- else }}
          initialDelaySeconds: {{ .Values.debug.initialDelaySeconds }}
{{- end }}

Maybe we should accept the custom params when Values.debug.enabled = false?

That's a much better idea.

PR updated~


Cursor blinks outside the textbox in IE 11

This issue had been raised quite a times but I still cannot find a fix for it.
The cursor blinks somewhere outside the input box in modal specifically in IE11, and comes in right position as soon as you start typing.
Please respond if anybody knows a work around for this.

Any particular reason you ignored our issue template?

Closing due to insufficient information & likely nothing to do with UI Bootstrap


Help with running GitHub actions?

I'm getting this error when trying to deploy my website that uses lightbox via GitHub action:
Error running filter _extensions/quarto-ext/lightbox/lightbox.lua:
_extensions/quarto-ext/lightbox/lightbox.lua:113: attempt to call a nil value (field 'is_format')

Any suggestions? I can seen lightbox if I run quarto list extensions in the action, but something appears to be wrong. Do I have to activate the extensions somehow?

It seems like locally, my document does have an is_format method, but not when using the GH action. I also had this problem when I first installed the extension, though reinstalling and updating quarto seemed to fix it. The page I'm using lightbox on does have a format:
format:
  html:
    page-layout: full
    smooth-scroll: true

So I'm unsure why it's complaining.

I believe this might have to do with quarto version used. On my local machine, I have 1.2.256, but the action will install quarto-1.1.251 even if I try to specify 1.2.256 (probably because it's a release candidate?). Potentially the problem will be fixed once quarto is updated. Unsure of if there's anything I can do on my end to be more explicit about doc format in the meantime.

The issue is related to the Quarto version (your observations are correct) - you need to be using Quarto 1.2 builds (as this extension is calling APIs that are only supported starting in 1.2). Using the Github Action, you can control what version of Quarto is setup, including using a specific version or the latest pre-release build like so:
  steps:
    - uses: quarto-dev/quarto-actions/setup@v2
      with:
        version: pre-release

More here https://github.com/quarto-dev/quarto-actions/tree/main/setup#inputs-available

Perfect, thanks! I had the right idea but was putting version in the wrong step (checkout vs. setup quarto). Works great now!


0 VPs for 0 finalCount

Also add a test :)
Currently it'll probably crash the code (as mentioned in gitter)


Fix console warning about styled components

I noticed a console warning about declaring styled components inside the render function in DependenciesView - moving the Text withComponent lines outside of the main function fixed the issue!!
Screenshot of the warning:

@joshri good catch! I cannot confirm this error because it seems it happens only for npm start and I see the following error when trying to open the app at the 4567 port after npm start now, in both the main branch and the fix branch:

But at least the app with the fix works for me as before with tilt up.