Custom labels have a random number on the end, but that's not available to post-host-commands to target properly

Problem: Using custom labels creates a random number to prevent collision of two VMs with the same label pattern: https://github.com/veertuinc/anka-vm-github-action/blob/6873084a4aaa9eca9e6e0f5597321f162d0bc830/helpers.js#L37
We need to make this available as an ENV the user can target in post host commands.

We set ${GITHUB_ACTION'}_vmLabel as an ENV that's available for users. I updated the readme for this to make it clear.


Add a custom JSON field inside metadata

After some conversation with @drwasho (http://imgur.com/a/s6Unw) and @SamPatt (http://imgur.com/a/TT1Pm) a while back, I'd like to submit a pull request to add a text field for JSON which allows nodes to add any amount of structured information to their listings. Extensive third party uses of this field might inform future updates to the protocol that weren't on the radar before or up the priority of those that were.
A good example use case is for a listing posted by a handy man in Cambridge that can only service people in this area. He may want to specify some JSON which allows others to know his location like:
{
    "location" : {
        "latitude" : "52.2053° N",
        "longitude" : "0.1218° E"
    }
}

Changes Unknown when pulling ff7798b79b6e783ccdd41918209004db2f3a1574 on dsmurrell:patch-1 into ** on OpenBazaar:master**.

@dsmurrell this might work better as a protobuf any type.

Also the issue I have with this is that unless the extra data is displayed to the user in the UI, you end up with a situation where the buyer is putting his signature on a contract that he hasn't fully read and hasn't consented to. Kind of violates the reason for having a contract.

@cpacia if the intended format is JSON, would it not make sense to constrain the type to string instead of any?
I've changed the name to reflect that anything in this field is non binding.
@hoffmabc, @drwasho do you have any alternate suggestions to offer to Chris' concern? Another option would be to show this information to the buyer in the UI.

Closing because the contracts.proto has had many changes after this PR. We can open an issue and discuss the best way to handle this or if we want to do it.


U/xiaobwan/update

Address kernel 6.8 incompatible with ubuntu 22.04

@microsoft-github-policy-service agree company="Microsoft"


Inline images are rendering in ADO's Description field for one work item type but not another

Describe the problem
In the source Jira server project I have Bugs and Improvements. Some of these have inline images/screenshots in their Description field. When I import these issues into the target ADO project, the inline images render in the standard Description field of the Improvements but not the Bugs; e.g.:

To Reproduce
Extracts from the config json file:
  "process-template": "Basic",

  "type-map": {
    "type": [
      {
        "source": "Improvement",
        "target": "Myprocess.Improvement"
      },
      {
        "source": "Bug",
        "target": "Myprocess.Bug"
      }
    ]
  },
  "field-map": {
    "field": [
      {
        "source": "description",
        "target": "System.Description",
        "mapper": "MapRendered"
      },

where Myprocess is the name of my ADO process which inherits from Basic. Myprocess has Epic, Issue and Task disabled, but new work item types called Bug and Improvement. Both of these have the default System.Description field but are otherwise virtually identical. Neither WIT has a Repro Steps field (and so I don't refer to that in the config json file either).
When I look in the issue json files generated by jira-export you can see entries like this inside a Myprocess.Improvement's System.Description field:

Bob got this error in his project X today:
\n\n

...and this image renders perfectly inside the Description of the Improvement created in ADO.
But inside a Myprocess.Bug's System.Description field all you see is:

I tried running the following lines on a jupyter notebook (IDE= VS code),
\n\n

\n\n
but I've got the following error, although the graph is still plotted after showing the error.
\n
\n\n

Note the images are still imported and are visible in the Links section of the ADO Bugs; they just aren't rendered in the Description.
Tool version
3.0.442

The first thing I notice is that the Type map seems to include the Process name. Is this correct? If the Work Item Types are named simply Bug and Improvement, then the type map should look like the following:
  "type-map": {
    "type": [
      {
        "source": "Improvement",
        "target": "Improvement"
      },
      {
        "source": "Bug",
        "target": "Bug"
      }
    ]
  },

Thanks @Alexander-Hjelm. Your suggestion was actually what I tried originally. However, even though both the jira-export and wi-import tools ran without error, no work items appeared in my DevOps project! I nearly raised an issue to ask how does one map to custom WITs; I couldn't find anything in the FAQ about this.
But when I went to https://dev.azure.com/MyOrg/MyProject/_apis/wit/workitemtypes?api-version=7.1 to list the WITs in my project I could see my custom WITs were prefixed with the process name; e.g.:
   {
      "name": "Bug",
      "referenceName": "Myprocess.Bug",

and when I updated my type-map as above the imported WITs then did appear in my ADO project, as required.
Aside: Note that the Basic process doesn't actually have a Bug WIT (see here), so maybe Samples\config-basic.json needs updating not to reference it?
Everything appears to be imported into ADO correctly for both Bugs and Improvements. The only issue is that any inline images are not rendering in the Bugs for some unexplained reason!

Ok! Can you confirm whether or not this issue is related to https://github.com/solidify/jira-azuredevops-migrator/issues/851?

Just looking at the title of that issue, I would say no, because the attached images that should appear inline in the Description are still being imported as attachments. Note too this only affects the Description field of the custom Bug WIT. Any inline images in comments render perfectly well using the default mapping in the config json:
      {
        "source": "comment",
        "target": "System.History",
        "mapper": "MapRendered"
      },

I'll have a deeper look at #851 though...

No, I'm pretty sure this has nothing to do with #851. Also, in my original ADO process, which also inherited from Basic, I only had one WIT type - Issue, with a custom field for Bug or Improvement (because at that time I didn't know you could add your own WITs!). The inline images in the Description field rendered fine in the ADO issues for both the 'Bug' and 'Improvement' Issues. It's only since I've created the custom WITs that this isn't happening for the new Bug WIT.

Agreed. I addressed your point about the Bug type in the Basic template in this commit: https://github.com/solidify/jira-azuredevops-migrator/commit/3361bb8f1ef777cc7c772111878ed977ddf50d2d
Here is the CorrectDescription method for reference:
https://github.com/solidify/jira-azuredevops-migrator/blob/3361bb8f1ef777cc7c772111878ed977ddf50d2d/src/WorkItemMigrator/WorkItemImport/WitClient/WitClientUtils.cs#L442-L480
I can see that the description field seems to be hard coded for various Work Item Types. If the WI Type name is "Bug", then it seems to switch over to using ReproSteps instead of Description. Could this be the underlying issue, do you think?

@Alexander-Hjelm Thank you so much for that info! Yes, my original config json above only had the one entry for the "source": "description" field. When I changed it to this:
      {
        "source": "description",
        "target": "System.Description",
	"not-for": "Myprocess.Bug",
        "mapper": "MapRendered"
      },
      {
        "source": "description",
        "target": "Microsoft.VSTS.TCM.ReproSteps",
	"for": "Myprocess.Bug",
        "mapper": "MapRendered"
      },

then the Description field for the new Bug WIT were not populated at all once the issues were imported into ADO.
So then I changed the custom Bug WIT in ADO to add a Repro Steps field and hide the Description field:

Finally, when I ran the importer again the inline images rendered for both my custom Improvements (in the Description field) and Bugs (in the Repro Steps field). Yay, at last! (All tested using 3.0.442 still.)
I guess users just have to be careful that if they create a custom WIT called 'Bug' they have to give it a Repro Steps field rather than a Description field, but the former makes more sense anyway.
Thanks, too, for updating docs/Samples/config-basic.json.
Thank you once again for all your help. This tool is great, buttressed by your timely support, and has really offset the sudden pain of being kicked off a Jira server that's about to be shut down.

No worries. I will create a new issue to follow up on this. It feels like we should build more general handling for WI/attachment links for all issue types.


JAVA-1762: Build alternate core artifact with Netty shaded

I'm wondering: with JAVA-1787 we provided an external shaded artifact for Guava, while here we are taking the old approach of creating an alternate artifact during the build.
How is the DSE driver supposed to behave in the presence of a Netty-shaded OSS driver? I don't see how this could work since the DSE driver exposes Netty classes in internal types, e.g. DseDriverContext.buildFrameCodec(). Are we going to create an alternate artifact for the DSE driver too?

The shaded classifier for each library could rewrite the package imports but not bring in the netty classes, but instead reference the netty shaded jar.

If we can coax the shade plugin into doing that, that does indeed sound like a viable solution. But from a quick look at the doc it won't be trivial, more investigation needed.

Closing in favor of #1019


Provide a more obvious path to different deployment sources

Up for discussion.
Upon creation, somehow prompt the user to dtermine how they want to deploy their app.

@nturinski Schedule a design review for this to discuss this offline. Actually talk about it this time.


can't get short_url_length within api.configuration()

Until today I've been able to truncate my long tweets into 280 characters by assuming URLs are shortened to length of 23. Today, that's not working, and I thought perhaps the short url length had changed. It's also, more likely, because I'm using an emoji (see #1538), but I wanted to check and I see recommendations to check the Twitter API configuration, but that doesn't work.
What there a way to get API configuration values? Where did it go?

API.configuration was removed in Tweepy v4.0.0, as the Twitter API endpoint that it used was retired (see #1614).
Instead, if you're using Twitter API v1.1, you can use the indices field of the corresponding URL object to determine the length of the URL in the text of the Tweet. If you have the Tweet object, you can retrieve its URL objects through the entities field and the urls field of that Entities object.


Unable to get basic example "Making a GET request" working

I’m looking at the Making a GET request example from the reqwest docs:

For a single request, you can use the get shortcut method.
let text = reqwest::get("https://www.rust-lang.org")?
   .text()?;

println!("body = {:?}", body);

But if I try to run this example, I get three errors:
error[E0425]: cannot find value `body` in this scope
 --> src/main.rs:7:29
  |
7 |     println!("body = {:?}", body);
  |                             ^^^^ not found in this scope

error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `std::ops::Try`)
 --> src/main.rs:4:16
  |
4 |     let text = reqwest::get("https://www.rust-lang.org")?
  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot use the `?` operator in a function that returns `()`
  |
  = help: the trait `std::ops::Try` is not implemented for `()`
  = note: required by `std::ops::Try::from_error`

error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `std::ops::Try`)
 --> src/main.rs:4:16
  |
4 |       let text = reqwest::get("https://www.rust-lang.org")?
  |  ________________^
5 | |         .text()?;
  | |________________^ cannot use the `?` operator in a function that returns `()`
  |
  = help: the trait `std::ops::Try` is not implemented for `()`
  = note: required by `std::ops::Try::from_error`

error: aborting due to 3 previous errors

Some errors occurred: E0277, E0425.
For more information about an error, try `rustc --explain E0277`.
error: Could not compile `reqwest_example`.

The first seems to be a quick fix – the variable declared is text, but we’re printing body. The latter two errors are less obvious to me as a new user of the library.
Here’s a minimal project that reproduces the behaviour: reqwest_example.zip

Relevant versions:
$ cargo --version
cargo 1.26.0 (0e7c5a931 2018-04-06)

$ rustc --version
rustc 1.26.0 (a77568041 2018-05-07)

$ rustup --version
rustup 1.11.0 (e751ff9f8 2018-02-13)

$ rustup show
Default host: x86_64-apple-darwin

stable-x86_64-apple-darwin (default)
rustc 1.26.0 (a77568041 2018-05-07)

I ran rustup update before submitting this issue.

The error is about using the ? operator in a function that doesn't return a Result. Starting in 1.26, you can change the main function to let this work: fn main() -> Result<(), reqwest::Error>.
The error message from the compiler really could use some help :)

Also body isn't defined. We have let text = so one of them should change to match the other.


Feat(ES-67, ES-76): Swapped to ghcr and Alpine Linux

Reduces docker image size from 830.82MB -> 396.67MB

lgtm


Remove strong reference to attachedWindow

Fixes #59

Looks like CircleCI was not configured to build forked pull requests.  I am going to close this PR and reopen to see if this will now trigger a build.


Questions about computing flops.

How to get the reported flops in the paper? I used the scripts in tools/get_flops.py, but I only get 236.1 GFLOPs with Swin-Tiny with the image shape of (3,512,512) , while the paper is 945 GFLOPs.

hello, Do you fix it?


fix: 取消双击表格时浏览器默认的选中文本行为 close #2798

👀 PR includes

🐛 Bugfix

[x] Solve the issue and close #2798

📝 Description

🖼 Screenshot

Before
After

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 80.16%. Comparing base (ecdc9c8) to head (a68dd3c).
Report is 398 commits behind head on next.

Additional details and impacted files
@@            Coverage Diff             @@
##             next    #2800      +/-   ##
==========================================
+ Coverage   75.77%   80.16%   +4.39%
==========================================
  Files         257      180      -77
  Lines       11994    10332    -1662
  Branches     2464     2331     -133
==========================================
- Hits         9088     8283     -805
+ Misses       1398      607     -791
+ Partials     1508     1442      -66

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:tada: This PR is included in version @antv/s2-v2.0.0-next.25 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v2.0.0-next.24 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Modify indicator-based rotation.

Rotation used for the indicator should be the same as the rotation used in mobilityCommands.SendMobileBaseDirection.

Tested on a Reachy 2023, was fine.


WIP - New file, paper key, folder icons

@keybase/react-hackers

@chrisnojima Can I get another look? I had a flow error.


Import settings during signup followup

Fixes #11018

Merged, thanks @hackerkid!
Thinking about these issues around string_id, would it be better to convert this system to communicate using the realm id, rather than string_id?  I think that might be cleaner and make bugs like 96bb27fa84609e77d0d7b6c9c1bb36e4a6c35458 impossible.
(Then we could also change the on weird value for not copying to be something more like None).


Add "don't download results" functionality to new task graphs API

This adds the "don't download results" functionality that was omitted from the initial release of the task graphs API. It works just the same: By default only terminal nodes (or nodes which have local dependents) are downloaded, but the user can override it.

so this change is from a mistake I made in node starting: because the lambda does not capture the current value of the node argument but instead a reference to the value itself, we were trying to start the same node multiple times.
This explains the failures we were having on previous test runs. The new version should solve this since it pulls the lambda out into its own function where it is never re-bound.

[sc-23079]


Change Request: Codeunit 5601 FA Insert G/L Account - GetGLAcc

The function GetBalAcc in Codeunit 5601 FA Insert G/L Account should get it's parameter GenJnlLine by reference.
So instead of this:
[External] GetBalAcc(GenJnlLine : Record "Gen. Journal Line") : Integer
it should be declared as
[External] GetBalAcc(VAR GenJnlLine : Record "Gen. Journal Line") : Integer
This enables us to use this function also on temporary records and buffers. Of course you need to make sure that the originally passed record is not modified.
An alternative would be, to write the newly created Gen. Journal Lines into a separate buffer that is passed in by reference. So we have full control over what happens to the created lines.

Thank you for your request. We decided to introduce a separate function
GetBalAccBuffer(VAR GenJnlLine : Record "Gen. Journal Line") : Integer
for the described use-case. It should be available in the next update.


feat: Bounded Range

Closes #2213

#2214  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Miss the services endpoint and account name in the 'Summary' dialog when attaching one storage account via the service URL

Storage Explorer Version: 1.18.1
Build Number: 20210309.6
Branch: main
Platform/OS: Windows 10/ Linux ubuntu 18.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to Reproduce

Select one storage account -> Click 'Open in portal' -> Copy one Blob service SAS URL with full permissions and full services in the portal.
Open the connect dialog -> Click 'Storage account -> Shared access signature(SAS)'.
Paste the URL ->Observe the 'Summary' dialog.
Check whether the services endpoint and the account name show.

Expected Experience
All services endpoint show well.
Actual Experience
The services endpoint and the account name do not show.

Additional Context
This issue doesn't reproduce for one connection string attached storage account.

Verified this issue on build 20210312.1. Fixed.


🍒 Cherry pick PR #11944 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/11944 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.2.18-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Cherry-picked to staging by @OSBotify in version: 1.2.18-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @chiragsalian in version: 1.2.18-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Proper logo display

Since a update there seems to be something wrong with the upper logo:

Damn... Yes i can reproduce it at on mobile.

@giomf Desktop and mobile.

@alkock Please check again. The issue is solved for me with the last release.

@alkock Is it still an issue for you?

lgtm


Push secrets cirun

Add workflow for pushing secrets from 1password to GH for CIRUN_API_KEY. CIRUN_API_KEY is a conda-forge org level secret and only conda-forge/admin-requests should have access to it.

Also we likely want to set the option deleteBeforeReplace to false so that secrets are updated in-plce without disturbing running jobs.

We should mark reources with protect basically always I think.

Testing this out in my demo repo, turning on protection will not allow updates to be made to the secret.
Enabling retainOnDelete allows updates to be made + doesn't delete the secret when it's removed from the pulumi config.

@soapy1 LGTM!
What is the order of operations here? Your trial org runs out in two weeks, so should we try and get OSS sponsorship and then merge this? Do we merge now? I am not quite sure.

Looks like pulumi supports migrating state between backends, so I feel ok about merging this now if we are keen.
@jaimergp what is the outlook on oss sponsorship?

what is the outlook on oss sponsorship?

We need to follow https://www.pulumi.com/pricing/open-source-free-tier/, which consists of submitting an issue in https://github.com/pulumi/team-edition-for-open-source/issues. It should not take too long, but from what I can see in the closed issues, it might be a couple weeks. Also, we need some running Pulumi code in the repo to qualify. I say we merge and then I'll submit the OSS sponsorship issue?

Also, can we have some documentation in the README? Your demo repo already has some, so I think it's just a matter of copying the relevant bits for future maintainers.

@beckermr @jaimergp how do y'all want to proceed?

We need to make an org on pulumi in order to request OSS as well.
So once the README work is done, let's merge here and go ahead with making the org and putting in the request?

README has been added with instructions on how to run locally and with GHA :+1:


Add python predictor

Python wrapped predictor class

Dang, so the appveyor build is really annoying right now because it keeps showing failure - I'll turn it off until when it succeeds on my local branch.

deprecated, closing


Temporarily, in NS3 Network Interface, also use send_port as key to sim_send_waiting_hash

Refer to issue #136  for a detailed description
This PR changes the key for the map sim_send_waiting_hash from
pair<tag, pair<src_id, dst_id>> to
pair<tag, pair<src_id, dst_id>, src_port>.
One collective phase can be split into multiple messages, all of which share the same key. src_port can be used to uniquely identify these messages (which share the same tag, src_id, dst_id).
Note that this is a hacky solution. A proper (future) solution would be to split sim_send_waiting_hash into two maps, like sim_recv_waiting_hash and received_msg_standby_hash.

Checking in without review.


feat: add chained_resource to support winked out allocations (PROOF-716)

Rationale for this change
Winking out can make code simpler and faster when used correctly. See https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0089r1.pdf for reference.
This PR adds a memory resource suitable for winked out host or device allocations.
What changes are included in this PR?

Adds chained_resource that tracks allocations and deallocates everything upon destruction.
Adds counting_resource as a tool for testing custom resources.

Are these changes tested?
Yes

:tada: This PR is included in version 1.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Intermittent error when building on windows in Github actions

Hey there,
This is not specific to your project but maybe you've seen this before and might have some ideas. We are an electron app for Mac and Windows. We are having issues building Windows on Github Actions due to this intermittent error.
npm ERR! gyp: C:\Users\runneradmin\AppData\Local\node-gyp\Cache\16.13.2\common.gypi not found (cwd: D:\a\sp-menubar\sp-menubar\node_modules\electron-acrylic-window) while reading includes of binding.gyp while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (D:\a\sp-menubar\sp-menubar\node_modules\node-gyp\lib\configure.js:259:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Windows_NT 10.0.20348
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\a\\sp-menubar\\sp-menubar\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd D:\a\sp-menubar\sp-menubar\node_modules\electron-acrylic-window

Full log
npm ERR! code 1
npm ERR! path D:\a\sp-menubar\sp-menubar\node_modules\electron-acrylic-window
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node-gyp rebuild
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| win32 | x64
npm ERR! gyp info find Python using Python version 3.9.9 found at "C:\hostedtoolcache\windows\Python\3.9.9\x64\python3.exe"
npm ERR! gyp http GET nodejs.org/download/release/v16.13.2/node-v16.13.2-headers.tar.gz
npm ERR! gyp http 200 nodejs.org/download/release/v16.13.2/node-v16.13.2-headers.tar.gz
npm ERR! gyp http GET nodejs.org/download/release/v16.13.2/SHASUMS2[56](https://github.com/superpoweredapp/sp-menubar/runs/5158102324?check_suite_focus=true#step:7:56).txt
npm ERR! gyp http GET nodejs.org/download/release/v16.13.2/win-x86/node.lib
npm ERR! gyp http GET nodejs.org/download/release/v16.13.2/win-x64/node.lib
npm ERR! gyp http GET nodejs.org/download/release/v16.13.2/win-arm64/node.lib
npm ERR! gyp http 200 nodejs.org/download/release/v16.13.2/win-x86/node.lib
npm ERR! gyp http 404 nodejs.org/download/release/v16.13.2/win-arm64/node.lib
npm ERR! gyp http 200 nodejs.org/download/release/v16.13.2/win-x64/node.lib
npm ERR! gyp http 200 nodejs.org/download/release/v16.13.2/SHASUMS256.txt
npm ERR! gyp info find VS using VS2022 (17.0.32112.339) found at:
npm ERR! gyp info find VS "C:\Program Files\Microsoft Visual Studio\2022\Enterprise"
npm ERR! gyp info find VS run with --verbose for detailed information
npm ERR! gyp info spawn C:\hostedtoolcache\windows\Python\3.9.9\x64\python3.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   'D:\\a\\sp-menubar\\sp-menubar\\node_modules\\node-gyp\\gyp\\gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'msvs',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'D:\\a\\sp-menubar\\sp-menubar\\node_modules\\electron-acrylic-window\\build\\config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'D:\\a\\sp-menubar\\sp-menubar\\node_modules\\node-gyp\\addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\runneradmin\\AppData\\Local\\node-gyp\\Cache\\16.13.2\\common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=C:\\Users\\runneradmin\\AppData\\Local\\node-gyp\\Cache\\16.13.2',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=D:\\a\\sp-menubar\\sp-menubar\\node_modules\\node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=C:\\\\Users\\\\runneradmin\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\16.13.2\\\\<(target_arch)\\\\node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=D:\\a\\sp-menubar\\sp-menubar\\node_modules\\electron-acrylic-window',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'D:\\a\\sp-menubar\\sp-menubar\\node_modules\\electron-acrylic-window\\build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp: C:\Users\runneradmin\AppData\Local\node-gyp\Cache\16.13.2\common.gypi not found (cwd: D:\a\sp-menubar\sp-menubar\node_modules\electron-acrylic-window) while reading includes of binding.gyp while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (D:\a\sp-menubar\sp-menubar\node_modules\node-gyp\lib\configure.js:2[59](https://github.com/superpoweredapp/sp-menubar/runs/5158102324?check_suite_focus=true#step:7:59):16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:3[90](https://github.com/superpoweredapp/sp-menubar/runs/5158102324?check_suite_focus=true#step:7:90):28)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Windows_NT 10.0.20348
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\a\\sp-menubar\\sp-menubar\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd D:\a\sp-menubar\sp-menubar\node_modules\electron-acrylic-window
npm ERR! gyp ERR! node -v v16.13.2
npm ERR! gyp ERR! node-gyp -v v8.4.1
npm ERR! gyp ERR! not ok

Running on node 16.13.2, npm 8.1.2, node-gyp 8.4.1 and vs version 2022 (tried it with 2019 too, actions doesn't have 2017).
This doesn't seem specific to this project. Found someone else who had the same issue with another native module https://github.com/AceCentre/EyeCommander/issues/51.
Appreciate any pointers! Please feel free to close the issue if it's not relevant

same issue, pls help

I don't think any other visual studio version except 2017 will work. I tried to build the project with 2019 before (#68), and it did not work.
However, this do not look like node-gyp is breaking before even trying to build. Can you provide the actions config and try to build locally?

Sorry for the late reply and thanks v much for your help 🙏
Here is the rough config:
  build_win:
    name: Build and Deploy for Windows
    runs-on: windows-2022
    defaults:
      run:
        shell: bash

    steps:
      - name: Print node and npm info
         run: |
          node --version
          npm --version
          npm list -g

      - name: Get dependencies from package.json
        env:
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
        run: |
          npm config set '//registry.npmjs.org/:_authToken' "${NPM_TOKEN}"
          npm config set msvs_version 2022
          npx node-gyp --version
          npm install

It definitely works but only intermittently which is the weird thing. Yup, locally everything works cause the setup is 2017, as recommended. Wish could get 2017 in github actions 😞

Ended up figuring out a way to have vs2017 and node 14, everything good now.

Due to the basic setting of GitHub, it will have to be resolved in vs 2019. Let me take a look at this problem.

Turns out this will fail on March 15th when Github Actions removes support for the vs2017 version altogether. https://github.com/actions/virtual-environments/issues/4312
I have tried all possible scenarios I could think of with newer machines but nothing. Anything work for you?

Noting that this issue is also seen on Azure Pipelines. I think they are probably running on the same MS-hosted VMs so probably not that surprising.

@nikhilro what are you doing to solve this now? Just hitting it for some packages


Update Bosung's KCC 2024 photos and posters

[ ] bibtex
[ ] photo
[ ] DBpia paper link
[ ] poster file pdf
[ ] paper pdf

See https://www.dbpia.co.kr/journal/articleDetail?nodeId=NODE11861936
and https://aiml-k.github.io/publication/2024kcc-jung-kim-lee/


WARNING: erroneous pipeline: no element "gvadetect"

Hello
Please when i try to initialize the contents of gstreamer - dlstreamer elements  i get the error below.
ty@ty:~/intel/dlstreamer_gst/scripts$  source ~/intel/dlstreamer_gst/scripts/setup_env.sh
bash: source ~/intel/dlstreamer_gst/scripts/setup_env.sh: No such file or directory
Also I proceeded to running a pipeline using the code i got the error below
ty@ty:~$ gst-launch-1.0 filesrc location=$/home/ty/Downloads/person-bicycle-car-detection.mp4 ! decodebin ! gvadetect model=$~/intel/dl_streamer/models/intel/person-vehicle-bike-detection-2004/FP32/person-vehicle-bike-detection-2004.xml model_proc=${DETECTION_MODEL_PROC} device=CPU ! queue ! gvawatermark ! videoconvert ! fpsdisplaysink video-sink=xvimagesink sync=false
WARNING: erroneous pipeline: no element "gvadetect"
Can you please provide assistance i am running gstreamer from a Ubuntu VM

Can you describe your environment in more details, first, please?
You have an Ubuntu VM? Which version of Ubuntu?
Have you installed OpenVINO, which version, how? Built from source-code or installed a pre-built version?
How have you installed DL-Streamer, as part of an OpenVINO installation or separately, from source code?
Can you describe your installation procedure, please?
If you install OpenVINO as described under "https://docs.openvinotoolkit.org/latest/openvino_docs_install_guides_installing_openvino_linux.html", then make sure you enable the installation of DL-Streamer.
Ideally you have an Intel GPU and Intel CPU available as the underlying HW for your Ubuntu VM.
Where did you get the command "source ~/intel/dlstreamer_gst/scripts/setup_env.sh" from? From the error message it looks like you don't have that file, you don't have that folder structure?


Feature Request: issue forms

Gitea version (or commit ref): master/main
Git version: n/a
Operating system:

Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No

Log gist:

Description
It would be nice to have something like GitHub's issue forms to make it easier/more straightforward to add issue details when submitting a new issue.
Screenshots

Duplicated by #16353, which elaborates a bit more in detail on the issue.


WIP: Manual Frame Capture

What this adds:
This PR allows you to trigger a manual frame capture of any length. This capture is started and stopped with the shortcut CMD + Shift + C, and saves to the path set in the environment variable MVK_CONFIG_GPU_CAPTURE_OUTPUT_FILE. If this environment variable is not set, the keyboard event listener will not be started.
This feature requires both macOS 10.15 or newer and for the GPU capture environment variable to be enabled.
Why?
This feature has the potential to be incredibly useful for those debugging games running under Wine, which often do not cooperate well with Xcode, and want the flexibility of starting a frame capture at any point during gameplay.
Debug Tools commit was working, my attempt to clean it up introduced segfaults not entirely sure they're coming from I think the added environment variable definition might be to blame.

I like this idea! It should prove very helpful at runtimes. Thanks for thinking of it and working on it!
I made some inline requests to refactor this to integrate this a bit better with existing behaviour, and use existing configs. Let me know what your thoughts are about that.

Thanks for the review Bill! I'll work on integrating your changes. There's a segfault somewhere I think maybe related to the env var I added so I'll try to sus that out.


Remove redundant new() static method

I believe that this is a more concise and readable way of achieving the same result. Do you agree?
Thanks for this awesome library, and I look forward to hearing what you think!

Removing a public method is a breaking change

Gonna keep this because I hate the parentheses around (new PendingZttpRequest) and PendingZttpRequest::new() feels just a little bit more like writing in a nice language like Ruby 😅
Thanks though!


[Question/Feature Request]: Hook for adding additional webpack loaders

Is this a bug report?
No
Not sure if this is a duplicate of #99, so please just close this issue in case it is.
What do I want to achieve?
We have the "issue" in our projects that we need to eject the create-react-app just for adding this additional loader to the webpack config:
{
  test: [/cldr\/.*\.json$/, /i18n\/.*\.json$/],
  loader: 'file-loader',
  options: {
    name: 'static/media/[name].[hash:8].[ext]',
  },
  type: 'javascript/auto'
},

I would be very happy if there would be any possibility to add a set of custom loaders right before the last file loader in the standard create-react-app-config.
Implementation Idea
I could image a similar concept like src/setupTests.js and src/setupProxy.js:

Create a file src/setupAdditionalWebpackLoaders.js
This file has export a function which is returning an array of additional webpack loaders that will be added right before the file-loader.
Check in the create-react-app/packages/react-scripts/config/webpack.config.js if this file exists and spread the results into the webpack loaders array. In case if doesn't exist just spread an empty array?

Do you think this request could possibly land in create-react-app? If yes, I would be happy to submit a PR with a POC implementation.


Change anchor element

I've added anchor_element option to the defaults.
The default anchor element is A, which shows the browser status bar when
hovered, and that's not good for single page applications. With this you
can configure it to be "span", to avoid the status bar.

Sorry, I can not merge this - I would like to keep the anchor there as it assists screen readers and has way more semantical meaning than a span.
Still, since the code depends on a class name and not on a node name, changing the anchor to a SPAN will work (as you noticed), but the functionality you developed would be better suited as a plugin.
You can create a plugin that only overrides the _create_prototype_node function. If you do so I will include it in the third party plugins (and if you decide not to - I will create it myself).
Once again - thank you and sorry for not merging this.
Best regards,
Ivan

Oh and I believe the changes to the contextmenu are not necessary - the anchor nodes there are the actual items IN the contextmenu - not related to jstree in any way.

Yeah, just noticed that the contextmenu edits were not necessary.
I'm going to create a _create_prototype_node plugin the next week then. Will be better than this commit, as we can configure more options.


Fw notifications

Fixed bug (all fw notification had the same title which caused problems upon repeated connection and disconnection of the camera).

Will be resubmitted via another PR


Generate opt-in to activity graph with self-hosted atuin server

Hi Ellie,
Thanks for the great work!
I have been using atuin all the time for a couple of days with a self-hosted server, and it really solves my issues of syncing shell history across different machines. I followed this session to use docker-compose to deploy my server: https://github.com/ellie/atuin/blob/main/docs/docker.md#docker-compose
Now I am trying to generate the activity graph, by executing the following command:
curl <my-atuin-server>/enable -d $(cat ~/.local/share/atuin/session)

and it always returns:
☕
to me. So I just want to ask: is this a feature that is only available in your atuin server or did do anything wrong?
Thanks!

Hi!
Yes, the activity graph feature is only available for the official server.
It requires access to the sync database in order to see the timestamps of your commands to be able to build the heatmap.
It's also not currently open source.
I hope you understand, and thanks for the interest in Atuin!

Thanks for your quick answer @conradludgate! I can totally understand this!

I stumbled on this issue while also trying to enable the activity graph on my self hosted instance
The feature was part of why I did setup an instance, so I made one available here
https://github.com/tieum/atuin-graph

thank you for this neat tool 🙂

@conradludgate just curious if you all plan to make the activity graph you run open source too.


Remove Base Wrapper from test examples

Summary
Some code cleanup

Remove Base Wrapper from test examples
Fix dialog test script
Remove test-examples from checkbox

Thanks for contributing to Terra.
@cerner/terra

With this can base also be removed as a peer dependency from these packages?

@mjhenkes I have made dependency changes in #1612 to align with the discussion on #1583


Document Profiler Debug Tool

We added pprof support, we should document what port we listen on / how to connect for debugging

This is fixed by pr #735.

Fixed in master.


Deprecate bonnie++, aerospike, and redis benchmarks

I propose we deprecate the following benchmarks for release 1.5, and remove them for release 1.6.

if you use ...
suggested replacement

bonnie++
fio

aerospike
aerospike_ycsb

redis
redis_ycsb

I deliberately did not include cassandra_stress in this list, because while we do have cassandra_ycsb, both benchmarks are still in use.
If you have any objections to deprecating these benchmarks, please comment on this issue.

LGTM

@tedsta: does this look good to you? If so, can you go ahead and remove the source for these benchmarks?

@gareth-ferneyhough ping. Let's bring this up at the meeting today. Deleting code is always fun.


OSX CMake fixes for tests binary

These changes allow the test projects to be properly built under OSX.
Some redundant sections in CMakeLists.txt have also been removed.

Hi can you rebase from master and push to kick off a new build, please? Hopefully fixes that unit test.

The reason of test failure looks to be related to #8087. Please don't commit this before passing all tests.

I think I'm missing how it's related.  It looks like to me the latest failure was a memory corruption error.
test_ndarray.test_cached ... *** Error in `/usr/bin/python3': malloc(): smallbin double linked list corrupted: 0x00007fad500008c0 ***
script returned exit code 134

No rush to merge this one though.  I'll periodically rebase it until the tests pass.

Is this ready for merging?

Yes

Assuming CI can pass


[HIGH] ManageProject_CountriesTab

Display/Open Countries tabs

[ ] Add functionality in ARA
[ ] Add NRT

Moved to another project


Confusing with App Password, Secrets and so on...

Where to get the App ID and App Password?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cf112c0a-0400-ede4-ab7c-ce10f86d6f30
Version Independent ID: 5fa92c50-b8d1-460c-aa3c-f3f851c15da9
Content: Deploy your C# bot to Azure - Bot Service
Content Source: articles/bot-builder-howto-deploy-azure.md
Service: bot-service
Product: bot-framework
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

@djpirra Following the steps in the Create your bot channels registration section, you should have recorded your app ID and password in steps 16 and 18.

Correct. You can find the MicrosoftAppID in the Azure portal, but you can't get the MicrosoftPassword after generating it.


RenderTarget.canvas nested rendering

If RenderTarget.canvas is true, it may try to render itself in PreRender. Whether this is wanted or not, there needs to be a limit to the depth of recursion.

One suggestion is instead of rendering all Canvases per camera, assign a canvas to a single camera and then render only that canvas. Nesting canvases also allows for some basic merging of canvas rendering (for example, camera A renders canvases A and B while camera B only renders B). More complex set operations could be handled in other ways.

Merged


Repeatable on CentOS?

Hello. I wish to run a 3D software what requires RHEL/CentOS 7. I want to create a CentOS 7 image with llvmpipe integrated so that the 3D software can run in headless servers. Seems like your image is the closest one to what I need. So is the building script repeatable on other Linux distributions? Thanks.

No one's replying so I managed to compile it myself

Howdy @BrushXue! We've all been very busy but glad you got this sorted out.

Hello. Yes I kind of sorted out the installation steps. However the performance is really bad (only 1 core is enabled for some reason)


[opencv4] Fix feature openexr compilation error

Fixes https://github.com/microsoft/vcpkg/issues/42221
Add the search method of openexr and fix the following problems.
E:\vcpkg\buildtrees\opencv4\src\4.10.0-d9ca17150b\modules\imgcodecs\src\grfmt_exr.hpp(52): fatal error C1083: Cannot open include file: 'ImfChromaticities.h': No such file or directory
E:\vcpkg\buildtrees\opencv4\src\4.10.0-d9ca17150b\modules\imgcodecs\src\grfmt_exr.cpp(62): fatal error C1083: Cannot open include file: 'ImfFrameBuffer.h': No such file or directory

[X] Changes comply with the maintainer guide.
[ ] ~SHA512s are updated for each updated download.~
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version.~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

The feature openexr and usage test passed with x64-windows triplet.

Can you make sure this is submitted upstream? /cc @cenit
Thanks!

mmm how is it missed in ci? don't we test openexr feature in vcpkg-ci-opencv?

CI might pull it in as a transitive dependency.


\Zend\Feed\Reader\Reeder.php::setHttpClient

I am using Google's Gmail atom feed to present users with a preview of unread emails. The feed requires authentication and allows for OAuth. I tried to use Zend\Feed to parse the atom feed because I noticed it allows for setting a custom http client in which I figured I could place the appropriate authentication header. Unfortunately, upon importing a feed, the Reeder resets the client prior to using it. Personally, I can't imagine why this route was chosen. I would imagine (in my limited experience and wisdom) that custom headers would be the most common use case for needing to set a custom client.
As a solution I think this class should be changed to allow for easier http header modification.
Thoughts?

This issue has been closed as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


Scan list

The scan list in Replay should be a list rather than a selection via radio buttons.
requested by @skalbfleisch

Why would you prefer a list rather than radio buttons?

Moved to NSLS-II/replay#16


Documentation Update

This Document says Azure Migrate does not enable Migration of SQL server to SQL server on Azure VM. This is contradictory to the Azure Migrate documentation https://docs.microsoft.com/en-us/azure/migrate/migrate-services-overview

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 65685c6c-ad86-bf4d-e37a-d973a4fb9fbe
Version Independent ID: 7995a2b1-3cc2-b7f8-7dab-79cfd138fdd1
Content: Compare SQL data migration tools - SQL Server
Content Source: docs/sql-server/migrate/dma-azure-migrate-compare-migration-tools.md
Product: sql
Technology: dma
GitHub Login: @rajpo
Microsoft Alias: rajpo

@marykolade -- Mary, thank you for your feedback.  That is a conundrum.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@MashaMSFT -- Masha, please look into this issue.

@rabryst , would you be able to help out with this issue?
#reassign:rabryst

The following users don't have valid GitHub IDs, or are not collaborators on this repo: rabryst

oops... reassign#rwestMSFT

#please-close

#reassign:croblesm


fix issue #1

fix for #1
this commit makes sure that any streams started with play/rec/playrec
are closed before exiting to avoid segmentation faults from unreleased
PaStream objects
Added a similar try/finally to StreamBase.__exit__ to make sure with always closes the stream properly.
Don't quote me on this but I'm pretty sure it's possible that a stream that has had PaStopStream() called on it can be started again without creating a new stream object so it may make sense to add a global close function to deallocate the stream corresponding to _last_callback.

Thanks!
I'm just trying to reproduce the original problem #1 on macOS and the error doesn't seem to happen there (but your changes don't seem to hurt, either).
I'll try it later on Linux.
On which OSs could you reproduce the original error?

it may make sense to add a global close function

I don't understand. A sound started with play() is not supposed to be started again.
I think stop() should be enough. It already calls stream.close().
After stop(), there is now way (and IMHO shouldn't be) to "open" the stream again.
Maybe I'm missing something ... can you provide an example where a global close() would be used?
I think it makes sense to call stop() in the exit handler, though.

I'm just trying to reproduce the original problem #1 on macOS and the error doesn't seem to happen there

Did you try using python 2? I tested it using python 2 on Linux. Anyhow, it absolutely makes sense that the error would occur: the _last_callback stream never gets closed in the exit handler. The call to stop() I added there is the only line needed to fix this particular issue.

it may make sense to add a global close function

I don't understand. A sound started with play() is not supposed to be started again.
I think stop() should be enough. It already calls stream.close().
After stop(), there is now way (and IMHO shouldn't be) to "open" the stream again.

What I meant was, I think that you can start and stop a PaStream multiple times as long as it hasn't been closed. I'm starting to suspect that I'm wrong about this though since I haven't been able to find any examples or evidence of this. I just always figured it was the case since that's the only way I could reason having a separate PaStopStream and PaCloseStream. (If it's not restartable than why not just have PaAbortStream and PaStopStream close the stream?).
Anyhow, that's kind of a separate discussion.
One detail about the commit: Do you have any objection to the part of the commit which doesn't ignore errors on __exit__?

OK, I think this was a bug in PortAudio and it was fixed in the newest version.
Sure, I admit that I didn't properly close the stream, but PortAudio could as well have taken care of this when shutting itself down. And it looks like now it does.
Which PortAudio version did you use?
I just downgraded to (1899, u'PortAudio V19-devel (built Feb 15 2014 23:28:00)'), and with that version I can reproduce the interpreter crash on Python 3. Surprisingly, it still doesn't crash with Python 2.
But anyway, since not everyone is using the latest and greatest version yet, we should apply your fix.
This PR indeed fixes the problem, but I think it does too much.
I assumed that closing a stream implies stopping it (or rather, to be exact, aborting it). Did you encounter a situation where this wasn't the case?
I'm not sure about the stop()'n'close() combo inside of __exit__() ...
I guess you wanted to ensure closing the stream if stop() fails, right?
Were you able to provoke such a situation?
Even if this can happen, the stream would already be in a broken state, so close() would very likely fail as well, so I don't know if this makes sense.

I think that you can start and stop a PaStream multiple times as long as it hasn't been closed.

Yes, you can indeed do that.
Try this in an interactive session:
>>> import sounddevice as sd
>>> def callback(indata, outdata, *stuff):
...     outdata[:] = indata
...
>>> s = sd.Stream(channels=2, callback=callback)
>>> s.start()
>>> s.stop()
>>> s.start()

Works like a charm for me (BTW, multiple consecutive calls to stop() are fine). Once the stream is closed, it's over:
>>> s.close()
>>> s.start()
Traceback (most recent call last):
...
sounddevice.PortAudioError: Error starting stream: Invalid stream pointer
>>>

If the stream is stopped by raising an exception in the callback, it cannot be re-start()ed, though.
This is obscurely hinted to in the documentation, which I took straight from the PortAudio docs:
http://python-sounddevice.readthedocs.io/en/latest/#sounddevice.Stream.stopped
http://portaudio.com/docs/v19-doxydocs/portaudio_8h.html#a52d778c985ae9d566de7e13529cc771f

wait so you're saying that the only time that you can re-start a stream is if stop() was called on it? This seems to be the case: if I let all my callbacks finish successfully (i.e. paComplete was returned on the last callback) then stopped is still false! The portaudio docs do seem to say this but man, you'd think they'd try to make that super clear since it's not what you'd intuitively expect.

pro tip: If you use finished_callback, it will only be called if the stream status was stopped before starting the stream. i.e., if you call start() then abort() then start() again, the finished_callback will only be called the first time around. In order to get it to call your finished_callback you must call stop() after each call to start().
Phew. I'm using an older portaudio version so it's possible this was a bug that's been fixed. I'll let the portaudio people know otherwise.

wait so you're saying that the only time that stopped will be true is if stop was called on it?

Yes. At least that's how I understand it.
It seems that "stopped" doesn't just mean "not doing anything" but more strictly "somebody has actively used the stop function". Confusingly, it could also mean that nobody as used the start function yet ...
The behavior of finished_callback you described indeed sounds like a bug.
On top of somewhat vaguely specified behavior, you never know if all host APIs at least behave the same way ...

On top of somewhat vaguely specified behavior, you never know if all host APIs at least behave the same way ...
Well here's a case in point: when I abort() a stream on my redhat machine (using ALSA), IsStreamStopped returns False. (Which is what I would expect). However, I tested the same code on a windows machine with ASIO and IsStreamStopped returns True after abort() is called.

I need to go back and sync up my portaudio library versions..the one I'm using on linux is all the way from 2010.

@tgarc Would be nice to get this merged ... what are your thoughts on my comments above (https://github.com/spatialaudio/python-sounddevice/pull/75#issuecomment-284530778)?

This PR indeed fixes the problem, but I think it does too much
I think you're right. The thing is when I tried removing all the changes except for the adding of stop() in the exit_handler the program just hung inside of Pa_CloseStream. I just hadn't spent the time to figure out why this is happening yet. I have a hunch that somehow Stop/Abort/Close is being called during this call to Pa_CloseStream (or the other way around). In my experience this causes portaudio to hang indefinitely; this is not unexpected since the API is not thread safe.

so oddly enough, aborting or closing the stream inside the exit handler causes portaudio to hang. however calling PaStopStream before closing seems to fix the issue altogether. Try it out but I think this is ready for a merge. Feel free to look into why it hangs when you call close() without calling stop() first in the exit handler, but it was starting to look like a rabbit hole to me. I suspect it has to do with the non-deterministic behavior of closing down the interpreter plus portaudio, but that's about as far as I got.

Sure, I admit that I didn't properly close the stream, but PortAudio could as well have taken care of this when shutting itself down. And it looks like now it does.

True. I tried loading up a newer (2016) version of portaudio and I couldn't reproduce this issue.

@tgarc Thanks for your investigations, I could reproduce the hanging behavior and it is indeed very strange.
I wanted to suggest that you use abort() instead of stop(), because this would convey the urgency of the situation a bit better.
But alas, with abort() it also hangs!
I don't have the stamina to investigate this further, and I wouldn't even know where to start.
But since you fixed it and current versions of PortAudio don't even have that bug anymore, I'm fine with not knowing all the details.
I'm merging this, thanks again for your help!


Provide way to quickly determine image MIME type and dimensions

A common operation for an image library (especially one integrated into a file-management sequence) is to discover the MIME type of an image file (by looking at header bytes and not just the file extension) as well as the dimensions of the image as quickly as possible.
Unfortunately the only way to do this now is to decode and load the image completely into a BufferedImage (to get the dimensions) and guess at the mime type via the image type and file extension.
Fortunately there is a super-simple class written by Jaimon Mathew that can read the first handful of bytes from a file and determine exactly this information:
http://blog.jaimon.co.uk/simpleimageinfo/SimpleImageInfo.java.html
This functionality should be integrated into imgscalr directly (original license is Apache 2, so it's compatible).

Out of scope for now -- with the creation of the ExifTool project, the image metadata problem is being addressed by my efforts in that complimentary project to imgscalr.


git bash windows fzf error

Never mind how kubectx (golang version) installed, by downloading binary  or by scoop
kubectx (Enter)
it works in powershell, but don't  in git bash for windows. I guess because path should be in bash format  /c/Users/Cloud/scoop/shims/kubectx

Yeah this is an interesting case. We pass kubectx's full path to fzf, I wonder if we should if-else this for mingw.

I'm observing the same problem while running kubectx in Git Bash session in Windows Terminal:

but if I switch to PowerShell in the same Windows Terminal, then it works:

If I switch to plain Start > Git Bash, and not in Windows Terminal, then everything works:

$ kubectx --version
0.9.4
$ fzf --version
0.39.0 (2023040)

I tend to install everything with winget.

Update to my https://github.com/ahmetb/kubectx/issues/382#issuecomment-1498810043
In Git Bash in Windows Terminal, interestingly, if I pipe kubectx | fzf:

then I get no error, but this

But, selecting context and ENTER seems to have no effect.

@cloud-66  See https://github.com/ahmetb/kubectx/issues/330#issuecomment-1506657091 for working workaround


'agent-specified' needs to be an exception for environment names with dashes

… dashes

@smbambling Taking a stab at this.  Let me know if you have comments:
https://github.com/WhatsARanjit/prosvcs-node_manager/commit/e83365cf31cbf94f687ff446c43938754587d97d
You can do node_groups() and receive all of them, or node_groups('PE Master') and receive just one.  As for filtering, I'd probably leave it up to all the other functions to mess with the hash it returns.

Great I'll play with this tonight or early i. The AM

@WhatsARanjit: the node_groups() function works pretty well.  With some help from @Volcane in IRC, I'm able to return an array of Environment Groups from the classifier
$pe_environment_groups = delete(node_groups().filter |$key, $val| { $val["environment_trumps"] == true }.map |$key, $val| { $val["name"] }, 'Agent-specified environment')

Here is a gist of the class that now auto creates and removes classifier env groups based on the availability of a PuppetServer environment
https://gist.github.com/smbambling/29bac41c434274afbfa1


redirect_login should still work if base64 encoded secret is wrong, it should just log a warning

We should be able to catch the bad decode and just grab the information from user_info.  This will cause https://github.com/auth0/wp-auth0/issues/271 to resurface, but that is less of a concern than total failed logins.

we should not do this. We should in fact strongly validate this (mostly for implicit flow but for code too)

We should talk this through.  I'm not recommending we don't validate the token, I think there are better ways to do this that don't break people who have that setting wrong.  It used to work for login to have it wrong because we weren't trying to decode it.  We were using the user info endpoint so we didn't need to.
The other option is for us to have some sort of wizard or warning when you update so that people know to go and check.
Or we need to back out the change and do a major rev since it is not truly backward compatible.

Management API returns a property with that, we should be able to create a migration to check that and should do the trick

I don't think this is still and issue but please re-open if so.


Uncaught (in promise) TypeError: Cannot read property 'flip' of undefined

I have every dep updated to the latest and observed this crash with filepond 3.0.2 and its plugins.
Uncaught (in promise) TypeError: Cannot read property 'flip' of undefined
    at imageToImageData (filepond-plugin-image-transform.js:256)
    at eval (filepond-plugin-image-transform.js:780)

I also found this same problem last night when upload image. my package.json include
    "filepond-plugin-image-preview": "^3.0.0",
    "filepond-plugin-image-resize": "^2.0.1",
    "filepond-plugin-image-transform": "^3.0.0",
    "react-filepond": "^3.0.1",

I think installing the filepond-plugin-image-crop plugin should fix this temporarily (no need to set a crop aspect ratio).
I'm working on a fix in the mean time.

Just published version 3.0.1 which should fix this issue. Please let me know if it does.

Thanks, that fixes the issue for me.


now website is not broken issue solved

@codervivek5 have alook!!!!!!!!
close issue -> #641

https://github.com/codervivek5/VigyBag/assets/114687502/455cdeca-ff8f-412a-9510-b61003bae587

bro if the footer is also fixed then kindly share any output...if there will be any changes then I will suggest you

thank you @codervivek5 👍

@Sushilverma002  can you remove buttom scroll bar ??

and can you make complete home page responsive?

@Sushilverma002 can you remove buttom scroll bar ??

which one ?

this one look ate the buttom scroll bar

just tell me one this the why the content on every single product is same?

 this one look ate the buttom scroll bar

ok i will do.

i will make PR ASAP.

i will make PR ASAP.

bro try to make only homepage mobile and tablet responsive so that it can also open in mobile

i will make PR ASAP.

bro try to make only the homepage mobile and tablet responsive so that it can also open in mobile

also raise a separate issue so that you can get your points

for sure


refactor(dual-channel): style tuning and refactor first/last embedded items entering/leaving viewport effects

Notable Changes

(mobile) Add gradient mask below embedded items (See Zeplin mockup: zpl.io/VDyJvDw).
(mobile) refactor first/last embedded items entering/leaving viewport effects.
handle edge case.

LGTM


Dequeue timer expires / picamera2 crashes in dark environments

Bug description
It seems that streaming / recording really dark environments causes the following error (after some time):
[12:37:57.133376596] [5093]  WARN V4L2 v4l2_videodevice.cpp:2007 /dev/video0[15:cap]: Dequeue timer of 1000000.00us has expired!
After this error the camera is no longer working and the program must be restarted.
I've tried to configure the ExposureTime / FrameDurationLimits but nothing fixed it.
Steps to Reproduce

wget https://raw.githubusercontent.com/raspberrypi/picamera2/main/examples/mjpeg_server.py
Place camera in really dark room (almost no light)
Run python3 mjpeg_server.py
Wait some time (1-5 min) and then the error occurs

Expected behaviour
The "dequeue timer expired" - error should not occur even there is no light at all.
Console Output
[12:37:57.133376596] [5093]  WARN V4L2 v4l2_videodevice.cpp:2007 /dev/video0[15:cap]: Dequeue timer of 1000000.00us has expired!
[12:37:57.133547853] [5093] ERROR RPI pipeline_base.cpp:1374 Camera frontend has timed out!
[12:37:57.133612426] [5093] ERROR RPI pipeline_base.cpp:1375 Please check that your camera sensor connector is attached securely.
[12:37:57.133674351] [5093] ERROR RPI pipeline_base.cpp:1376 Alternatively, try another cable and/or sensor.

Hardware / Software

Raspberry Pi Compute Module 4 Rev 1.1
Cam ov5647 [2592x1944 10-bit GBRG] (/base/soc/i2c0mux/i2c@0/ov5647@36) NOIR
Debian GNU/Linux 12 /  Kernel: Linux 6.1.0-rpi6-rpi-v8 / arm64
python3-picamera2/stable,stable 0.3.14-1
/boot/config.txt

# camera_auto_detect=0
dtoverlay=ov5647,cam0

More informations
I've tested the behavior multiple times:

If the environment is "bright" enough then everything is working as expected.
If the environment is "dark" then the error occurs always (after some time,  1 - 5 minutes)
The following command shows exactly the same behavior:
libcamera-vid -t0 --width 1920 --height 1080 --framerate 10 --nopreview --codec h264 --profile high --intra 5 --listen -o tcp://<IP_ADDRESS>:8494

@naushir Any ideas on this one?

The watchdog timer should get adjusted based on the framerate the sensor is currently running, so it should not trigger in dark environments where the exposure may be longer.  It is also a 1s timeout, and our frametime is 100ms, so there's plenty of margin.  Let me see if I can reproduce this.

I have another RaspberryPI4 (not CM4) with the same camera (not the same software).
I have now removed the camera from this RaspberryPI and connected it to my CM4.
Tests are in progress...

Result: The problem persists even with a different camera (same model) and a different cable.

My board ran all night without failures.  This was on a Pi 4, not CM4 though.  Did your setup fail with the Pi4 board as well?
What kind of environment are you running the camera in?  Is there any chance of electrical interference causing this?

I would say it is a quite normal environment (basement in the house, wifi, nothing special).
I cannot test it at the moment on the Pi4 because I have to prepare an SD card first (with the same os/packages). I will test it.
However, I have noticed before that the camera pipeline also stalls on the PI4 every few days/weeks (much less than on the CM4). Unfortunately, the problem can then only be solved with a complete reboot. Either there is a problem with this camera type / batch or it is some kind of software problem....

I think there could be another cause of the problem:
The camera has two IR LEDs attached and these LEDs are automatically turned on when it gets dark (photo resistor).
Perhaps this is causing a problem with the power supply of the camera.
I'll disconnect the LEDs and see what happens...

I've spent some time and tried to analyze the behavior. The problem seems to be related to the IR LED's:
IR LED's detached
The camera is working fine and stable
IR LED's attached to camera (as designed)
In a really dark environment each IR-LED will provide the max output power of 3w (according to the spec).
In this situation the camera crashes after some time (as already describen in the issue).
Because of this behavior I've initially tought that the increased current is the culprit (voltage drop etc.).
But this seems not the case...
IR LED's attached to 3.3v rail of PI
Same situation as above (dark, 100% LED power) but the camera does not crash.
My current assumption is now that the heat generated by the LEDs is causing the problems.
What are your toughts?

Ah, ok, to this is likely because of the power limit that can be drawn over the camera connector cable.  It would definitely be recommended to use an external power source, not the rails going up the camera corrector.

I'll close this down now as I'm pretty sure we've identified the culprit.  Please reopen if you are still experiencing issues.

Hello everyone! I just encountred same issue too. I was using my Official Raspberry Pi Camera v2.1 (IMX219) on Rasp Pi 4 and it started to not respond. I have tried it with another Rasp Pi 4 and it couldn't solve the problem. I just wonder that is about hardware or something else like shortcircuit etc. I also changed the CSI cable. What could be the issue if it is about hardware? However, I don't think that is about hardware or components. Because, Rasp Pi recognize the sensor but cannot capture anything.
`from picamera2 import Picamera2
picam2 = Picamera2()
picam2.start()`
For this code, output is below.
[5:55:58.812302496] [2455]  INFO Camera camera_manager.cpp:297 libcamera v0.0.5+82-2783c8d8 [5:55:58.847497400] [2456]  WARN RPI vc4.cpp:383 Mismatch between Unicam and CamHelper for embedded data usage! [5:55:58.848479950] [2456]  INFO RPI vc4.cpp:437 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media0 and ISP device /dev/media1 [5:55:58.848594838] [2456]  INFO RPI pipeline_base.cpp:1101 Using configuration file '/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml' [5:55:58.855309539] [2455]  INFO Camera camera.cpp:1033 configuring streams: (0) 640x480-XBGR8888 (1) 640x480-SBGGR10_CSI2P [5:55:58.856078313] [2456]  INFO RPI vc4.cpp:565 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 640x480-SBGGR10_1X10 - Selected unicam format: 640x480-pBAA
However, when I try to capture an image with code that below:
`from picamera2 import Picamera2
picam2 = Picamera2()
picam2.start()
picam2.capture_file("img.png")`
It responds like that:
[5:59:18.904755857] [2472]  INFO Camera camera_manager.cpp:297 libcamera v0.0.5+82-2783c8d8 [5:59:18.937802416] [2473]  WARN RPI vc4.cpp:383 Mismatch between Unicam and CamHelper for embedded data usage! [5:59:18.938728133] [2473]  INFO RPI vc4.cpp:437 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media0 and ISP device /dev/media1 [5:59:18.938813632] [2473]  INFO RPI pipeline_base.cpp:1101 Using configuration file '/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml' [5:59:18.948974941] [2472]  INFO Camera camera.cpp:1033 configuring streams: (0) 640x480-XBGR8888 (1) 640x480-SBGGR10_CSI2P [5:59:18.949949917] [2473]  INFO RPI vc4.cpp:565 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 640x480-SBGGR10_1X10 - Selected unicam format: 640x480-pBAA [5:59:20.036045749] [2473]  WARN V4L2 v4l2_videodevice.cpp:2007 /dev/video0[15:cap]: Dequeue timer of 1000000.00us has expired! [5:59:20.036174081] [2473] ERROR RPI pipeline_base.cpp:1333 Camera frontend has timed out! [5:59:20.036214877] [2473] ERROR RPI pipeline_base.cpp:1334 Please check that your camera sensor connector is attached securely. [5:59:20.036254173] [2473] ERROR RPI pipeline_base.cpp:1335 Alternatively, try another cable and/or sensor. ^CTraceback (most recent call last):   File "/home/mehdi/seda_rpi/single_n.py", line 5, in <module>     picam2.capture_file("img.png")   File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 1230, in capture_file     return self.dispatch_functions(functions, wait, signal_function)   File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 1203, in dispatch_functions     return job.get_result() if wait else job   File "/usr/lib/python3/dist-packages/picamera2/job.py", line 77, in get_result     return self._future.result()   File "/usr/lib/python3.9/concurrent/futures/_base.py", line 435, in result     self._condition.wait(timeout)   File "/usr/lib/python3.9/threading.py", line 312, in wait     waiter.acquire() KeyboardInterrupt
I hope you guys can suggest any solutions. Thank you.

Is this also a problem that occurs only in dark environments, as per the issue title? Thanks.

Yes please. Please also report:

What kind of Pi you are using.
What OS you are running. Please report the output of cat /etc/os-release, uname -a, apt list python3-picamera2 and libcamera-hello --version.
How you are logged in to the Pi. Are you connected remotely (e.g. via ssh) or directly with a screen and keyboard?
Are you running a desktop environment?
Is there anything you've changed since the camera last worked? Such as configuration settings, or other versions of camera software.
Do libcamera-hello and libcamera-still work?
How long your ribbon cables are.
What kind of power supply are you using?
You say you've tried a different Pi and a different cable, do you happen to have a different camera to try?
If you have a spare SD card, are you able to try a clean OS installation where absolutely nothing is changed and all you do is start the camera?

Thanks!

Thanks a lot!

Thanks a lot!

Could you provide a link to the issue created as I'm experiencing exactly the same issues. Thank you!

Thanks a lot!

Could you provide a link to the issue created as I'm experiencing exactly the same issues. Thank you!

https://github.com/raspberrypi/picamera2/issues/873

Thanks a lot!

Could you provide a link to the issue created as I'm experiencing exactly the same issues. Thank you!

https://github.com/raspberrypi/picamera2/issues/873

Awesome, thanks.

Thanks a lot!

Could you provide a link to the issue created as I'm experiencing exactly the same issues. Thank you!

https://github.com/raspberrypi/picamera2/issues/873

Awesome, thanks.

Cant tell me how to fix this problem? The link is not exist now!

Thanks a lot!

Could you provide a link to the issue created as I'm experiencing exactly the same issues. Thank you!

https://github.com/raspberrypi/picamera2/issues/873

Awesome, thanks.

Cant tell me how to fix this problem? The link is not exist now!

I have changed the sensor on the board. Its issue was about the sensor or the tiny ribbon cable of it. I couldn't figure out clearly. Do not implement any procedure on the board that causes any other problems.


SPIKE - charting libraries

POC code here: https://github.com/ECMWFCode4Earth/vAirify/blob/poc/chart/air-quality-ui/src/SingleCity.tsx
Both echarts + chartjs can do what we want. Suggest we use echarts for now


I need to download, install .net core on SUSE 11 linux machine. I'm pretty new to linux.please help me

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/sles12/runtime-current
Operating System: Linux SLES 12 - x64
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

@nazeer17 If you're looking to get started, follow the install instructions at https://dotnet.microsoft.com/download/linux-package-manager/sles12/sdk-current and then work through the Getting Started guide.
There's an enormous amount of Linux tutorial information on the Internet. YouTube is your friend in this ;-)

Our machine is with  SUSE 11 version, please let me know if this version supports .Net Core?

12 is min supported version of SLES. See https://github.com/dotnet/core/blob/master/release-notes/3.0/3.0-supported-os.md.

Closing stale issue; @nazeer17 please feel free to re-open if you need more assistance.


Display date

Thanks for developing the theme, I find it very nice and functional.
I only have one small gripe: the them does not display the dates of blog posts. In the demo there seems to be the same issue: even though the markdown files have the date information, it is not displayed.
Is there some setting I can tweak to show the date on the blog posts?

Hi @piever Do you mean aside from these places?

Ups, hadn't noticed it there. Then I must be doing something wrong, as I can't visualize it in my blog, but the beginning of my markdown file has a date. Here is a sample post (date doesn't show) and here is the corresponding markdown. I'm on the latest commit of this theme and on latest hugo release.
I somehow assumed it was an ananke issue as by googling it seemd other people had it. See for example the comment immediately above the linked header:

Ananke Theme issues
You might have notice the post is displayed without a date, this issue is related to the Ananke theme.

Can you point me to your repo?

Thanks a lot! Here is the repo:
https://github.com/piever/simpleblog

Hey, @piever so it's not a bug. The date is set for posts, but not for other article types, which means any entries in the post directory (it's generally suggested to use singular folder names in content) will have a date, and others will not.
I will consider some way to make that more flexible (i've begun work on updating the theme), but in the meantime, you can either copy themes/ananke/layouts/_default/single.html into your root layout folder (so, layouts/_default/single.html) and add the date there (reference), or change your content's posts folder to post.
I'm closing this and, if you wish to follow the issue, it's referenced here on the page.

Wow, removing the "s" folder from the posts folder (it's now called post) fixed it, thanks a lot!
Not sure if there's any need to change this, but it's probably worth a mention in the README as the result of googling "ananke hugo date not displayed" was this tutorial where the put posts in the posts folder and then say: "date does not display, it's an issue with the theme"...

Good idea, thanks. And had that person bothered to dig a little deeper, as you did, before claiming the theme was just bad in a public forum, we'd all be better off.


Monitor 2.0: Eliminate use of async:false for ajax requests

Forcing ajax queries to be synchronous isn't advisable for the reasons described in the links below.  I've improved the code to work asynchronously.
I'm also working on some other improvements but I wanted to submit them as smaller PR's to make them easier to review.
jQuery.ajax(): Setting async to false is strongly discouraged as it can cause the browser to become unresponsive.
MDN: Synchronous requests on the main thread have been deprecated due to the negative effects to the user experience.
The functions that use .getJSON() in functions.js now return the jqXHR (jQuery XML HTTP Request) object.
This object implements the Promise interface, so it's possible to provide a callback for when one or more requests complete.
In most cases there was only one request to wait for so .then(handler) can be chained directly onto the request.
In some cases, there were several requests issued synchronously.
Where possible, the individual handlers were chained onto their respective request function if there were no dependencies between the requests.  (Eg. problems.js)
The overview page is the only case where many requests must all be completed before the plots can be updated.  In this case $.always() is used to wait for all requests to finish.  Using $.always() will ignore any failures and continue to update the plots.  This isn't a great solution but there are no adverse effects and I intend to improve it further in another pull request.

@cleroux Thanks for the contribution!  If you'd like to be added to the contributors page at https://accumulo.apache.org/people, please submit a pull request to update the website page at https://github.com/apache/accumulo-website/blob/master/pages/people.md with your details.


Measure address server usage

@c-castillo is this still in motion?

https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#dashboards:name=address_server_invocations-develop

Looks good!


Would you be open to a PR changing from grid layout to flexbox layout?

Love the minimalist style, but it's bothering me that the content div is overflowing and creating a scrollbar. I've looked through the stylesheet a bit and played around, and I believe the cause is due to the way the grid layout is used (although I'm not 100% on this).
If you prefer to stay with the grid style, that's cool. I'll keep my forked version for my own usage.

Do you have some example how you would like to have it? Not sure what the layout change would look like.

I'm fine reducing the size again. In fact the list used to be shorter.

This can be closed then, right?


Support For RTP/RTSP

Hi @jgh-, I'd like to add support for RTP/RTSP to VideoCore. Is that a feature that would be desirable? The project looks solid and one facet of the application I'm working on shares about 60% of the same pipeline, except for the network portion. I would release the extension under the same license. Please let me know your thoughts on this.

That's the plan. I'll work on this once I'm back in the office and submit a pull request down the line.

Perfect, I'll look forward to seeing it.

would love support for RTSP too!

I got this working a while back enough for my purposes. For now, I recommend eschewing the rtmp packetizer and rtmp session objects. You receive a stream of NAL units and can use an existing rtp/rtsp library. The only caveat if you need to build an sdp is that you'll have to parse the bytestreams yourself to get the sps, pps, asc, and you will have to modify the CMTime values to your format. In addition you'll have to provide your own Simple RTP session similar to VCSimpleSession.
I don't want to introduce a large dependency to this project, but I wanted to leave some feedback for those looking to integrate with live555 or ortp.


Metadata updates for release 8.0.0

Dec 07, 2016: v8.0.0
Code changes:

Deleting deprecated methods in ShortNumberInfo that work on strings, instead
of phone number objects. These have been marked deprecated for months. Any
users of these methods should call PhoneNumberUtil.parse first to create a
PhoneNumber object, and pass this in.
Support semicolon as extension character while parsing phone numbers. This
is not applicable when you are trying to find the phone numbers.

Metadata changes:

Updated phone metadata for region code(s):
AM, BD, BR, CI, ES, IN, KI, KR, LI, MC, MM, TZ
Updated short number metadata for region code(s): KI, MV, MY
New geocoding data for country calling code(s): 227 (en), 240 (en), 255 (en)
Updated geocoding data for country calling code(s): 95 (en), 686 (en)
New carrier data for country calling code(s): 423 (en)
Updated carrier data for country calling code(s):
90 (en), 91 (en), 95 (en), 255 (en), 374 (en, ru)

This change is

I signed it!


Private-Admin can't see the lab clusters

Description:
Private-Admin can't see the lab clusters (KLAB, CLAB, KLAB2):

Now private-admin role can see lab clusters both in new and existing products:


feat(docker): install minimum packages in base stage

Description
This PR makes changes to minimize the number of packages installed with apt-get install at the base stage.
This is why we need to minimize the image size as much as possible. Having a smaller image size is beneficial.
Tests performed
https://github.com/autowarefoundation/autoware/actions/runs/9185294602
Not applicable.
Effects on system behavior

Not applicable.
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

We can merge this once https://github.com/autowarefoundation/autoware/actions/runs/9185294602 passes

Passed.


Validating page query

Fixing #10.

@weierophinney Please, hold this PR. Discovered a bug with empty collections.

Ok. Done.

Thanks, @Lansoweb; I have merged, and fixed the merge conflict (the new test introduced in #12 was improperly setup, triggering the bug you were fixing!).

My pleasure! Thanks.


Enhanced responsiveness

What does this PR do?
The website is made responsive.
Fixes #326

Type of change

Bug fix (non-breaking change which fixes an issue)
Chore (refactoring code, technical debt, workflow improvements)

How should this be tested?
Check in browser responsiveness or in other systems
Mandatory Tasks

[

Yes] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Please merge the PR ASAP

@YadavAkhileshh please merge the file to codebase asap(I have resolved conflicts).


Fix Colors syntax and  issue #246

Winston.jl:97    Issue 246   Winston.jl:97       } (     to      }(
plot.jl:572      FloatingPoint ~> AbstractFloat
renderer.jl:63   color_to_rgb(s::AbstractString) =parse(Colorant,s)

Thanks to slangular; @compat can be put at the start of a new line, but 'elseif' marks a new line in this sense.

The travis build still fails on nightly, because building Tk.jl fails.


Update setup.py

This pull request resolves #[ISSUE_NUMBER].
The pull request is in progress.
OR
The pull request is ready to be merged.
The details of the pull request:

Pull Request Test Coverage Report for Build 573

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 96.732%

Files with Coverage Reduction
New Missed Lines
%

autokeras/graph.py
2
97.21%

Totals

Change from base Build 568:
-0.1%

Covered Lines:
1717

Relevant Lines:
1775

💛  - Coveralls


API examples

Concerning the API examples found in https://github.com/pyocd/pyOCD/blob/main/docs/api_examples.md following remarks/questions:

hello world: after target.resume() my setup cannot access the core registers.  I have to do a target.halt().  Is it just me?
breakpoint: the assert fails because address read from ELF has LSB set (thumb) so TMO the assert should read "assert pc == addr & ~0x01".  Again: just me?
breakpoint: "target.remove_breakpoint()" wants an address

My setup is an nRF52840, compiler latest+ llvm.
Ok, to create some more examples (and correct the old ones) and make a PR?

It's not just you. 😞 And yes, a PR would be awesome! 😄


schedule download list

ability to make a download list and schedule it for a specific time is a great feature like the on IDM has

Will consider, Tks

i have used folx before motrix in mac os,if you add scheduled feaure  to motrix  is even beter than folx !

Any ETA? It would be awesome!


Feature/add support for swift package manager

Thanks for the PR !

You’re welcome, I was hoping to get this tagged, but it seems to have failed due to SwiftLint, and I can’t see why.
From: Pierre Felgines @.>
Date: Friday, 18 June 2021 at 07:53
To: faberNovel/ADAssertLayout @.>
Cc: Daren Hayward @.>, Author @.>
Subject: Re: [faberNovel/ADAssertLayout] Feature/add support for swift package manager (#7)
Thanks for the PR !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FfaberNovel%2FADAssertLayout%2Fpull%2F7%23issuecomment-863803272&data=04|01|darhaywa%40synamedia.com|a2e809684c144e0f69ac08d93225c454|ecdd899a33be4c3391e41f1144fc2f56|0|0|637595960046976886|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Uwz6b0UYbHpdazRy7NWU%2Fi3XlVeOzoH7xeiOvnXnauE%3D&reserved=0, or unsubscribehttps://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM4QXJ6C3XKXM6KF42ETW2LTTLUOFANCNFSM465BAHBQ&data=04|01|darhaywa%40synamedia.com|a2e809684c144e0f69ac08d93225c454|ecdd899a33be4c3391e41f1144fc2f56|0|0|637595960046986842|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=O3TikOGNsepAWD%2FcmPf7YPcISZISdn%2BCLfLm3LoYkZA%3D&reserved=0.

Ah, found it!
[06:56:44]: ▸ /Users/runner/work/ADAssertLayout/ADAssertLayout/ADAssertLayout/Classes/UIView+LayoutTest.swift:18:12: warning: Cyclomatic Complexity Violation: Function should have complexity 10 or less: currently complexity equals 11 (cyclomatic_complexity)
231https://github.com/faberNovel/ADAssertLayout/runs/2855980202#step:6:231
This change didn’t modify that though….
Can it still be tagged or does this need fixing first?
From: Daren Hayward @.>
Date: Friday, 18 June 2021 at 08:39
To: faberNovel/ADAssertLayout @.>
Cc: Author @.***>
Subject: Re: [faberNovel/ADAssertLayout] Feature/add support for swift package manager (#7)
You’re welcome, I was hoping to get this tagged, but it seems to have failed due to SwiftLint, and I can’t see why.
From: Pierre Felgines @.>
Date: Friday, 18 June 2021 at 07:53
To: faberNovel/ADAssertLayout @.>
Cc: Daren Hayward @.>, Author @.>
Subject: Re: [faberNovel/ADAssertLayout] Feature/add support for swift package manager (#7)
Thanks for the PR !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FfaberNovel%2FADAssertLayout%2Fpull%2F7%23issuecomment-863803272&data=04|01|darhaywa%40synamedia.com|a2e809684c144e0f69ac08d93225c454|ecdd899a33be4c3391e41f1144fc2f56|0|0|637595960046976886|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Uwz6b0UYbHpdazRy7NWU%2Fi3XlVeOzoH7xeiOvnXnauE%3D&reserved=0, or unsubscribehttps://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM4QXJ6C3XKXM6KF42ETW2LTTLUOFANCNFSM465BAHBQ&data=04|01|darhaywa%40synamedia.com|a2e809684c144e0f69ac08d93225c454|ecdd899a33be4c3391e41f1144fc2f56|0|0|637595960046986842|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=O3TikOGNsepAWD%2FcmPf7YPcISZISdn%2BCLfLm3LoYkZA%3D&reserved=0.

I guess you can target the branch develop until I create a new release. Will try to do it today

Version 1.0.1 is released.

Thank you!
From: Pierre Felgines @.>
Date: Friday, 18 June 2021 at 09:59
To: faberNovel/ADAssertLayout @.>
Cc: Daren Hayward @.>, Author @.>
Subject: Re: [faberNovel/ADAssertLayout] Feature/add support for swift package manager (#7)
Version 1.0.1https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FfaberNovel%2FADAssertLayout%2Freleases%2Ftag%2Fv1.0.1&data=04|01|darhaywa%40synamedia.com|89d02edb94b84a8e46ca08d9323755be|ecdd899a33be4c3391e41f1144fc2f56|0|0|637596035501345991|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=0FT6biqMJfQndv2ViHalqrjrulE2%2ByZaKZACmTApGQw%3D&reserved=0 is released.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FfaberNovel%2FADAssertLayout%2Fpull%2F7%23issuecomment-863879663&data=04|01|darhaywa%40synamedia.com|89d02edb94b84a8e46ca08d9323755be|ecdd899a33be4c3391e41f1144fc2f56|0|0|637596035501355951|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YNqMVyc113%2Byb3fl7va9igCHyeP6M2JnOgpltvI7pDg%3D&reserved=0, or unsubscribehttps://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM4QXJ4CSWMUGGN75GWQW2TTTMDFZANCNFSM465BAHBQ&data=04|01|darhaywa%40synamedia.com|89d02edb94b84a8e46ca08d9323755be|ecdd899a33be4c3391e41f1144fc2f56|0|0|637596035501355951|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=04%2Fjx4JCPohtaHZCi3Mh%2FOX%2Fud%2BSZz%2FyRjkiOLMXFOA%3D&reserved=0.


Bluetooth not work on Android 11 API 30

Any help, when I clicked scan is started status. However don't display any bluetooth found.
Noted: Bluetooth and permission is turn on status

It would appear that bluetoothadapter.java is throwing an exception. If you click into it you will see the code and find why this is the case.
Usually the stacktrace is bigger and you will find the original cause lower down(its cut off on your screenshot).
Chances are, this is an issue with android.bluetooth.BluetoothAdapter(standard android) and not an issue with the blue falcon library.
It could be a permissions issue, seems like there is a fetching of systemService from a context wrapper. - Permission with xml manifest?

Yes, I also added the permission in manifest. However I tried with other device android version 14 API 34 it's working. That's why I think the issue come from version android device.

So it works on version 14 API 34 of android. Which version of android does it not work? What is the full stack trace? you will probably find a hint of the error there

The currently android version 11 API 30 not work. The actually I try run the same source code but the version 11 of android not list bluetooth found. however it's work on version 14 API 34
Noted: both device also turn on bluetooth and clicked scan button.
Device not work

Device work

Do you have the full stacktrace? could you post it in here?

I'm not sure what is the full stack trace. However I have to explore logs file, may it's can help.
OnePlus-ONEPLUS-A6000-Android-11_2024-05-02_152223.logcat.zip

Having a look now for you

Are you sure you have the correct permissions:

    /**
     * Broadcast Action: The notifys Bluetooth ACL connected event. This will be
     * by BLE Always on enabled application to know the ACL_CONNECTED event
     * when Bluetooth state in STATE_BLE_ON. This denotes GATT connection
     * as Bluetooth LE is the only feature available in STATE_BLE_ON
     *
     * This is counterpart of {@link BluetoothDevice#ACTION_ACL_CONNECTED} which
     * works in Bluetooth state STATE_ON
     *
     * @hide
     */
    @RequiresBluetoothConnectPermission
    @RequiresPermission(android.Manifest.permission.BLUETOOTH_CONNECT)
    @SdkConstant(SdkConstantType.BROADCAST_INTENT_ACTION)
    public static final String ACTION_BLE_ACL_CONNECTED =
            "android.bluetooth.adapter.action.BLE_ACL_CONNECTED";

My guess is that you dont have the bluetooth_connect permission.
public static final String BLUETOOTH_CONNECT = "android.permission.BLUETOOTH_CONNECT";

Yes, I'm sure. Because I'm just from from your source code.

i would need to spend time looking into this properly, will have to try later when i have a moment. My guess is its something around contexts and permissions used in an older api of android.
Not the best solution but i would propose you don't support the older api bump the minimum up.

Thanks for your help

@youvita - i have tried to recreate the issue but because i dont have a physical android device on android 11, i cannot reproduce. The emulator doesnt crash but obviously it doesnt engage with bluetooth.
As a suggestion i could bump the min api level so that android 11 cannot be supported but that wont fix your problem of supporting those devices.

@Reedyuk,
I have question, it's possible to display bluetooth name instead bluetooth address?
Example: 77:D9:EE:E6:E2:52 -> U6-LR

Ble devices expose a characteristic called name, you must call this and then in your app, display the value of this characteristic.

@Reedyuk, Could you update this name bluetooth address instead characteristic as you mention above?
It's better know the name of Bluetooth device. Thank you for feedback.

No, as this is only an android thing and also this could have an impact on other users of the library.
It is up to you, the consumer of the library to do this your side.

It's possible, you can mention the example code here. Thanks for support.

Sorry, you will have to do that yourself.
The sudo is rather simple:
Detect device, request characteristic of 'name', when you get the value then display.
You could even extend the BluetoothPeripherial, to have a suspend func to get the Mac address.
Then in your client code, you could have a flow of devices mapped to by key to device e.g.
val deviceMap: MutableStateFlow<Map<String, BluetoothPeripherial>> = blueFalconClient.peripherals.map {
it.macAddress() to it
}


Recreate app in SwiftUI ?

Hello bro,
I'm a Beginner learner and hobbiest.
im currently learning how to create swift UI Based app..
I wanted some idea so I thought why not to create something that will benefit the whole Hackintosh Community I've thought about Hackintool 2.0 using swift ui but as i said I'm a beginner I don't know to how to use old libraries in swift
Please Help me
This is what I expect the new app to look like

I don't really have time to port Hackintool to Swift but you're more than welcome to give it a try!

I don't really have time to port Hackintool to Swift but you're more than welcome to give it a try!

Can you explain breif structure of your old I don't know objective c and have no idea how to include old objc libraries in swift ui

That's an interesting idea! If I will have enough time and willings to rewrite the thing in Swift and SwiftUI, I will do it, I am experienced enough with Swift and SwiftUI to do that

That's an interesting idea! If I will have enough time and willings to rewrite the thing in Swift and SwiftUI, I will do it, I am experienced enough with Swift and SwiftUI to do that

Ohhh wow we can work together should I share source code with you ? I'm not that experienced using github


Trying to deploy dev environment

Hi guys,
Can you please advise I probably missed something as I am new using nuxt but I am not able to deploy the dev environment.
followed the step on the readme and replaced in next.config.js

Tittle (just to see if my page is modified)
hostname => http://localhost:3000
API_URL => http://localhost/api/

The point is

It does not seem to chang my title html tag..
When I want to save I have a 404 error
It does not seems to create my mongodb database (even changing .env)

Any clue of what I am missing ?

I am wondering the same thing - did you solve this issue in the end?


Multi src schema in project configuration file

Hello !
I'm using the atlas version v0.8.2-42b597d-canary (using Brew)
I probably miss something but I do not succeed to use the project configuration file with an array of src.
In my folder, I have two .hcl files describing my two schemas. In this folder I also have my atlas.hcl file that describes my env
env "myEnv" {
  src     = ["schema1.hcl", "schema2.hcl"]
  url     = "postgres://postgres..."
  schemas = ["schema1", "schema2"]
}

When I try to apply
 atlas schema apply --env myEnv

I receive the following error Error: stat schema1.hclschema2.hcl: no such file or directory
Thanks for your help !

Will do ! I still have an issue when trying to create a FK references another schema.


Could not find the 'libra' module when make python

tried to run the examples: make python but failed as

@ivysc Thank you for bringing this to our attention!