Output is different when connected to a shell vs a pipe

wasmtime has a different output depending on whether it is run normally or through a pipe (for example, tail).
Test Case
See the wasm.test file here:
wasm-test.zip
Steps to Reproduce
Normal case:
$ wasmtime run test.wasm
line written using C puts
hello world!

Output is redirected to a pipe:
$ wasmtime run test.wasm | tail
line written using C puts

For comparison, I tested the same thing in wasmer and it has the correct (first) output in both cases.
Expected Results
Output should be the same, regardless of where stdout is redirected.
Actual Results
The last line is somehow lost when stdout is redirected to a pipe (in this case, passing it to tail but I've also seen this issue when running from inside Go os/exec).
Versions and Environment
Wasmtime version or commit: wasmtime-cli 17.0.0
Operating system: Linux (Fedora Asahi)
Architecture: aarch64
Extra Info
This is a relatively big test case, I can try to make it smaller if needed.
For example, I've found it reproducible using fwrite("test\n", 5, 1, stdout);.

Thanks for the report! I can reproduce this behavior as well with the uploaded wasm. That being said though I'm not certian that this is a bug in Wasmtime. Through WASMTIME_LOG=trace in the non-piped case (tty stdout) the module is calling fd_write more times than in the piped case. In other words, in the piped case, the module itself isn't even requesting a print. The main difference here is that the module calls fd_fdstat_get and the tty version returns fs_filetype: CharacterDevice while the piped version returns fs_filetype: Unknown meaning that the module may use this to act differently.
Would you be able to share the source code of this module? The bug may be in TinyGo's standard library, but it might also be in wasi-libc. This may also be a bug that's since been fixed in wasi-libc and may require a newer build than you might be using. Hard to tell! If you're able to share the original source we can try to help dig in further.
Furthermore you mention fwrite("test\n", 5, 1, stdout); reproduces this behavior for you. Locally however I do not see a reproduction with a simple program doing that. This may indicate that this was a bug in wasi-libc that's since been fixed. Could you share the full source of the program (perhaps the module too) with fwrite and the version of wasi-sdk that you're using?

That being said though I'm not certian that this is a bug in Wasmtime.

Yeah, since reporting this bug I started to realize it's more likely to be a bug in wasm-libc.

The main difference here is that the module calls fd_fdstat_get and the tty version returns fs_filetype: CharacterDevice while the piped version returns fs_filetype: Unknown meaning that the module may use this to act differently.

Thanks! I wasn't aware that WASI allowed inspecting the output file type.

Would you be able to share the source code of this module?

It's essentially just testdata/cgo in https://github.com/tinygo-org/tinygo/pull/4101/files but without the fflush workaround.
Unfortunately, when I tried to reproduce it today I couldn't get it to fail. I don't remember updating anything (like wasmtime) so not sure why this is the case. Closing, I'll reopen the issue once I manage to reproduce it again.

Nevermind, that was a silly mistake on my side.
I can reproduce it using the following steps (this assumes you already have a working TinyGo build):

Check out the cgo-printf branch of TinyGo.
run go install, tinygo clean
Comment out the fflush call at the bottom of testdata/cgo/main.c. (You can also uncomment most of the main function in testdata/cgo/main.go if you'd like).
Build a binary using tinygo build -o test.wasm -target=wasi ./testdata/cgo
Run it using wasmtime run test.wasm | tail.

That's rather involved just to reproduce this issue, I can try to make a reproducer that doesn't use TinyGo.

This may also be a bug that's since been fixed in wasi-libc and may require a newer build than you might be using.

Tried again with the main branch of wasi-libc, same issue. So whatever it is, it doesn't look like it's fixed there.

Update: I can't seem to reproduce this with a simple 'hello world', this needs a bit more investigation.


Access level to Edalzell\Mailchimp\ServiceProvider::bootConfig() must be protected or weaker

What is happening?
When attempting to install the Mailchimp addon via composer running the command composer require silentz/mailchimp into a v4 install of Statamic, you get the error:
Access level to Edalzell\Mailchimp\ServiceProvider::bootConfig() must be protected (as in class Statamic\Providers\AddonServiceProvider) or weaker

This impacts both fresh installs and v2/3 upgrades.
What should be happening?
The composer installer should complete without errors.
Did you RTFM?
Yes, Erin. I RTFM'd. 😂
How to reproduce

Run composer create-project statamic/statamic demo
cd into demo
Run composer install to ensure all default composer packages install correctly.
Run composer require silentz/mailchimp.
See the error during package discovery.

Environment
Statamic: 4.1 and Statamic 4.0
PHP: 8.1

Thanks Ben, I'll get a release out this weekend.

@edalzell – not that I'm aware of. I'll double check with the rest of the team.

Closing in favour of #93


Version 0.2.3

@mathiasrw January is over. We have many changes and fixed issues. Let's release!

What is the next name? :)

For sure it will be "Spetses" :) https://github.com/agershun/alasql/issues/533#issuecomment-172294390
Have you found a solution for getting it to the athmospherejs thing (Meteor)?

Ohhh - I get your question - its the 2.4 you ask for.
Let it be "Exogi" - where I first felt a true Greek dance circle at the town celebration :)

Hmm. Getting errors on debian for test 429 and 430. I have to sort this out before releasing...

Hmmmm - First time the test is running its ok, but next time we get
  1) Test 429 Localstorage DELETE with WHERE clause:

      AssertionError: [ { str: undefined },
  { str: undefined },
  { str: undefined },
  { str: undefined },
  { str: undefined },
  { str: undefined deepEqual [ { str: 'b' } ]
      + expected - actual

       [
         {
      -    "str": [undefined]
      -  }
      -  {
      -    "str": [undefined]
      -  }
      -  {
      -    "str": [undefined]
      -  }
      -  {
      -    "str": [undefined]
      -  }
      -  {
      -    "str": [undefined]
      -  }
      -  {
      -    "str": [undefined]
      -  }
      -  {
           "str": "b"
         }
       ]

      at Context.<anonymous> (test429.js:23:10)

  2) Test 430 UNIQUE keyword in localStorage "before all" hook:
     Error: localStorage: Cannot create new database "test430g1" because it already exists
      at Function.LS.createDatabase (/Users/mrw/alasql/dist/alasql.js:16107:10)
      at yy.CreateDatabase.execute (/Users/mrw/alasql/dist/alasql.js:12856:43)
      at Function.alasql.drun (/Users/mrw/alasql/dist/alasql.js:4197:45)
      at Function.alasql.dexec (/Users/mrw/alasql/dist/alasql.js:4174:18)
      at Function.alasql.exec (/Users/mrw/alasql/dist/alasql.js:4111:17)
      at alasql (/Users/mrw/alasql/dist/alasql.js:120:18)
      at Context.<anonymous> (test430.js:13:5)

  3) Test 430 UNIQUE keyword in localStorage "after all" hook:
     TypeError: Cannot read property 'engineid' of undefined
      at yy.DetachDatabase.execute (/Users/mrw/alasql/dist/alasql.js:12905:39)
      at Function.alasql.dexec (/Users/mrw/alasql/dist/alasql.js:4166:45)
      at Function.alasql.exec (/Users/mrw/alasql/dist/alasql.js:4111:17)
      at alasql (/Users/mrw/alasql/dist/alasql.js:120:18)
      at Context.<anonymous> (test430.js:18:4)

Still looking into it...

Resetting the test429.json will remove the errors.
So I have to find out what the idea behind
https://github.com/agershun/alasql/blob/88e5c43207c5ad7940b3ad1438e6aded2e33d934/test/test429.js#L5 is.
I have .skiped the test 429 and 430


Update deploying_notary.md

Add an ending period for step 1 as it is a complete setence and step 2 and step 3 both end with a period.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Fair enough, thanks @scjane :)


Implement handling fee tax for taxable payment methods

Implement handling fee tax for FI70, FI72, FIIN and FIBI payment methods

Tested orders with multiple variations with ALV24 and ALV10 products. Status query and refunds tested too.


Adding authentication overview for Azure SDK for Go

#assign-reviewer:JImacoMS4

Closing:  made this request on the main repo instead of pr.


HTML

#HTML
##User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
##Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

can you please explain more on the

associated notes listed


Simplify characters iteration

Just to illustrate the issue better,
let text = '👌';
for (let i = 0; i < text.length; i += 1) { console.log(text[i]); } // FAIL: prints two incorrect characters
[...text].forEach(c => console.log(c)) // PASS: prints one character
for (const c of [...text]) { console.log(c); } // PASS
for (const c of text) { console.log(c); } // PASS
Also curious to know why https://github.com/papandreou/subset-font/commit/84ac1955987f5197b0f037d6cf0dde1622d73397 was needed yet this won't revert that and just simplifies it.

Pull Request Test Coverage Report for Build 806572052

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 765171076:
0.0%

Covered Lines:
36

Relevant Lines:
36

💛  - Coveralls

Ah, you're right that the spread isn't necessary, thanks 🎉
I added 84ac195 because forEach is "old school" now that we have for...of, not because there was a functional problem with it.

Released in 1.2.1.


EditorFileSystemDirectory can't see directory contents.

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3.0
Issue description:
EditorFileSystemDirectory appeared unable to see any of the files or subdirectories in my resource folder.
Steps to reproduce:
Take an existing project that has files and folders inside it already.
Create an empty scene with a Node, and the following built-in script:
extends Node

func _ready():
    var dir = EditorFileSystemDirectory.new()
    print(dir.get_file_count())
    print(dir.get_subdir_count())
    for i_file in range(0,dir.get_file_count()):
        print(i_file, "> Path: ", dir.get_file_path(i_file))
        print(i_file, "> Name: ", dir.get_file(i_file))
        print(i_file, "> Type: ", dir.get_file_type(i_file))
    print(dir.get_path())
    print(dir.get_name())

Save the scene to your res:// directory, and then run it. It will print:
0
0
res://

...when it should print a LOT more information.

isnt that another singleton?
EditorInterface.get_resource_filesystem().get_filesystem()
# or
EditorInterface.get_resource_filesystem().get_filesystem_path(my_path)

Oh, that may very well be. I can't seem to do EditorInterface.get_resource_filesystem() or just get_resource_filesystem() though. Not sure how those are supposed be accessed. I've been trying to put in the documentation, so...XD

oh i forgot, it is
get_editor_interface().get_resource_filesystem()....  # from a EditorPlugin

i guess that class needs to be virtual.

Oh, so they have to be used from an EditorPlugin in order to work properly?
If so, I will amend the documentation I've done for those classes.

it makes sense, those are tools needed by EditorPlugins, the Directory class is for the rest.

Why are they used in place of Directory anyway? What makes them different? They seem to have limited functionality in comparison. Or is it that they can access the whole file system beyond res:// and stuff?

im not sure it seems to have some utilities only available to them, maybe because behavior optimizations for Editor stuff, but i've never used it nor checked the code, so that might be a good place to start.

Yeah, I've peeked at the code, checking the contents of the scripting API-exposed functions, but I wasn't seeing much.  Maybe I'll have to dig deeper later on.


Ticking Entity Crash

Apparently a Zombie from your mod caused this?
Was running fine for a good week or two, until this happened.
https://pastebin.com/8CV9RLeL

That is a big known issue with some animations overlapping and the api did not update to protect against it and I am not releasing any updates due to schools so you will have to excuse me until May or mid-April.

Maybe fixed, I will keep an eye on it since the api has not yet updated.


JavaScript compilation for browsers

Hi, I've been testing jco on NodeJS and it has been working well. Great project!
However, I couldn't solve how to compile JavaScript files for the browser(without import and exports). How can I do that? I dug in the docs and guides, but no explanation was there that I could find. Do I have to use Webpack or Vite to transpile ES JavaScript to Browser JavaScript?

When I run npx webpack, the following error occurs:
PS C:\Users\temed\Documents\GitHub\jco-test> npx webpack
assets by status 2.54 MiB [cached] 2 assets
asset main.js 98 KiB [emitted] (name: main)
runtime modules 4.23 KiB 7 modules
cacheable modules 77.9 KiB (javascript) 2.54 MiB (asset)
  javascript modules 77.9 KiB
    modules by path ./node_modules/@bytecodealliance/preview2-shim/lib/ 15.1 KiB
<EMAIL_ADDRESS>1.25 KiB [built] [code generated]
<EMAIL_ADDRESS>8.24 KiB [built] [code generated]
<EMAIL_ADDRESS>1010 bytes [built] [code generated]
<EMAIL_ADDRESS>4.62 KiB [built] [code generated]
    ./browser.js 94 bytes [built] [code generated]
    ./out_dir/jco_test.js 62.7 KiB [built] [code generated]
  asset modules 84 bytes (javascript) 2.54 MiB (asset)
    ./out_dir/jco_test.core.wasm 42 bytes (javascript) 2.51 MiB (asset) [built] [code generated]
    ./out_dir/jco_test.core2.wasm 42 bytes (javascript) 28.7 KiB (asset) [built] [code generated]

ERROR in<EMAIL_ADDRESS>1:0-30
Module not found: Error: Can't resolve './io.js' in 'C:\Users\temed\Documents\GitHub\jco-test\node_modules\@bytecodealliance\preview2-shim\lib\browser'
resolve './io.js' in 'C:\Users\temed\Documents\GitHub\jco-test\node_modules\@bytecodealliance\preview2-shim\lib\browser'
  using description file<EMAIL_ADDRESS>(relative path: ./lib/browser)
    Field 'browser' doesn't contain a valid alias configuration
    using description file<EMAIL_ADDRESS>(relative path: ./lib/browser/io.js)
      Field 'browser' doesn't contain a valid alias configuration
<EMAIL_ADDRESS>doesn't exist
 @ ./out_dir/jco_test.js 3:0-77 17:27-35 20:26-31
 @ ./browser.js 1:0-51 3:0-10

webpack 5.89.0 compiled with 1 error in 358 ms

Looks like io.js is missing...

Repo is available here:

https://github.com/temeddix/jco-test

Thanks for the quick reply :)
Basically, I wish to write this:
<!DOCTYPE html>

    <title>Sample HTML Page</title>

My HTML Page

instead of this:
<!DOCTYPE html>

    <title>Sample HTML Page</title>

My HTML Page

With this importmap, it looks like I need to copy the packages folder to my own project repo.

The browser says that io.js is not found, even if I provide the proper importmap. Other shim modules load fine.

In my opinion, for browsers, it will be good to open a file dialog for users to choose whenever file read/write operation is requested. Currently the support status of file operation for the browser is just written as N/A. Is this idea acceptable?

Thanks for posting, yes the browser build is currently not working. This was due to recent IO work, where the browser build is not currently tested in CI (test/browser.html).
I've added a fix to the current IO PR in https://github.com/bytecodealliance/jco/pull/244/commits/cf6de645a41ad40f0499cbd71418c266c6f9e5ed.

With the new io.js file with cf6d364 commit, the modules are loaded well. However, I'm getting this error now. May I ask what would be the cause?


testing: add ensureYellow call

Should fix the failure seen here:
https://travis-ci.org/crate/crate/jobs/118462058#L1669

ack if travis is green :)


Test setup should be automated on test project build completion.

this might require dynamoCoreRuntime being published to nuget, or downloading it from s3.


Feature/2933/cache sitemap

Some weird way of caching the sitemap using the public stage manager
Also adds the PUBLISH action/mode
I foresee the that there's going to be a lot more actions/modes. The listeners will handle the actions differently. Some may upsert, some may do nothing, some may just invalidate, etc.

Requesting re-review, changed a few things. not sure if better or worse :man_shrugging:


[Bug] The task keeps hanging in launch stage

Describe the bug
Details:
https://github.com/InternLM/InternEvo/actions/runs/8758331037/job/24131265916
Environment
python3.10
torch2.1
Other information
No response

Resolved in new version:
https://github.com/InternLM/InternEvo/actions/runs/8943615463/job/24570733409


⚠ IMAP has degraded performance

In d09f9d3, IMAP (https://news.ycombinator.com) experienced degraded performance:

HTTP code: 200
Response time: 8800 ms

Resolved: IMAP performance has improved in 4e788ce after 19 minutes.


Nuclio Function Deployment Fails with Image Pull Error in Kubernetes

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
While deploying a Nuclio function included in the CVAT repository in a Kubernetes environment, I encountered an issue where the function deployment fails due to an image pull error. The function status is marked as “unhealthy,” and the deployment does not proceed as expected.

Run CVAT and Nuclio in a Kubernetes environment.
Execute the following command to deploy the Nuclio function:  ./nuctl deploy --project-name cvat -n nuclio --path ./serverless/onnx/WongKinYiu/yolov7/nuclio --platform kube
Observe the error message in the logs.

Expected Behavior
The function should deploy successfully in Kubernetes without image pull issues.
Possible Solution
If this image is intended to be public, ensure it is accessible without authentication or provide updated instructions for handling private images. Otherwise, please clarify the required configuration for authentication to pull private images.
Context
Running the function in Kubernetes for inference purposes is essential for our setup with CVAT. Guidance on resolving this image pull issue would be greatly appreciated.
Environment
Server version: 2.22.0

Core version: 15.2.1

Canvas version: 2.20.10

UI version: 1.66.4

Kubernetes Version: v1.28.9

Deployment Platform: Kubernetes

https://docs.cvat.ai/docs/administration/advanced/k8s_deployment_with_helm/#optional-enable-auto-annotation-feature


chores(README): fenced code blocks should be surrounded by blank lines

See MD031 at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

Hi @kianmeng, thanks for your pull request!
I agree that your reference holds good reasons to stick to that rule number 31.
Maybe it is worth creating a github action that runs this lint ?
If you would like to do it, please do :) (there are many other examples in the .github/workflows directory)
Otherwise I can do it!

Maybe it is worth creating a github action that runs this lint ? If you would like to do it, please do :) (there are many other examples in the .github/workflows directory) Otherwise I can do it!

There are still some underlying issues that I can't resolve, which depends on your personal takes. Hence, it's better that you implement this. :smile:
$ mdl README.md
README.md:133: MD004 Unordered list style
README.md:137: MD004 Unordered list style
README.md:138: MD004 Unordered list style
README.md:5: MD013 Line length
README.md:21: MD013 Line length
README.md:23: MD013 Line length
README.md:29: MD013 Line length
README.md:100: MD013 Line length
README.md:133: MD013 Line length
README.md:137: MD013 Line length
README.md:138: MD013 Line length
README.md:109: MD024 Multiple headers with the same content
README.md:11: MD029 Ordered list item prefix
README.md:12: MD029 Ordered list item prefix
README.md:14: MD029 Ordered list item prefix
README.md:15: MD029 Ordered list item prefix
README.md:16: MD029 Ordered list item prefix

A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

Merged! Thanks, @kianmeng ! Finally, I decided to add a GitHub action directly in this PR so that I avoid multiple PRs ;-)

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Fix/account button responsive 2

Breaking Changes
N/A
Changes

feat: add charsStart and  charsEnd properties to wui-account-button
fix: responsive styling for wui-account-button
chore:

Screenshots
https://github.com/WalletConnect/web3modal/assets/12738697/bdb4a329-abe2-4d33-9428-7696b5f2a329

Close in favor of https://github.com/WalletConnect/web3modal/pull/1676


How to get the AP for youtube_vis?

@sukjunhwang

Hi @xjtuwh,
The annotations for validation and test sets are not open in public, so you should upload result files to Codalab servers.
The details for submissions can be found at https://youtube-vos.org

Ok, thank you very much~


Consider as general Kibana enhancement

great work - very cool was wondering would this be too specific to propose as general kibana enhancement? (it would seem its right place would be in that panel possibly? or can this be set on any time variable?
(sorry for abusing issues a bit here :) feel free to close)

or add as "input panel" ? :) https://github.com/elastic/kibana/pull/13314

@jccq There is an open issue for moving the time slider piece into kibana as an input control. https://github.com/elastic/kibana/issues/14177.

cool that covers it :) closing


[IOT4] - Make the www site work for S3.

Terraform keeps making changes to the API and its infuriating.
Description
Make sure the PR is against the main branch (see Contributing).
Make sure to set the corresponding milestone in the PR.
Please include a summary of the change(s) and which issue(s) it addresses. Please also include relevant motivation and context.
Fixes # (issue)
Type of change
Select the relevant option(s):

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works (optional)
[ ] New and existing unit tests pass locally with my changes

terraform plan and apply ran


handling of atom feeds

can this handle atom as well as rss.  very similar.

Yes, atom also works.


Configuring provider dags in the main catalog.yaml file results in None being passed downstream

Configuring data providers in the main catalog plus collections in a separate catalog (e.g. as in bodleian) works but when the provider is configured only in catalog.yaml I get dags with None in the name since no collection level key exists. I confirmed this is the issue by moving ifpo configurations into a separate file and adding a collection level key.

after discussing this with @aaron-collier and @jacobthill this morning, we've decided to close this ticket as moot.  there are no longer any configs in this state, and we don't anticipate moving back to having more configuration inline in catalog.yaml, as that file is already getting large, so keeping provider specific configs split out into their own files should keep things more readable.


feat: add semantic release

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


Added import metrics for better observability

Description
Please include a description of changes introduced in this PR.
Checklist
Please ensure that each of these items has been addressed:

[x] I have tested these changes in my local environment
[ ] I have added/modified tests as applicable to cover these changes
[x] (Atlassian contributors only) I have removed any Atlassian-internal changes including internal modules, references to internal tickets, and internal wiki links

The latest version of @forge/runtime uses a version of the "ws" package that has an ongoing VULN so for the builds to pass I had to add a resolution.


Add cifs-utils to allow mounting cifs fileshares

To allow mounting of fileshares, as described in minishift/minishift#316, we need to add cifs-utils to the image.

Unlike minishift/minishift-centos-iso#99, mount -t cifs gives no output if this is not supported.

Unlike minishift/minishift-centos-iso#99, mount -t cifs gives no output if this is not supported. This means we can not test for support, instead I check for /sbin/mount.cifs and the output.

Fair enough. Is there otherwise no sort of package management command one could use? I guess not?

package management command

not sure if tce-load registered the package as it was unsquashed into the root filesystem. Likely it did, ... will check.

The actual problem is dependency resolving. Earlier packaged versions of cifs-utils relied on a package called samba3-libs (and more). In later releases this was renamed to samba-libs. Because we prepare the image, we can not rely on the dependency resolution process. We have to do this manually.  I want to make sure the binary can actually run. For the CentOS image we do not have this problem, as the actually run an install process from during the livecd creator.


Change to fixed-size grid elements

Changed the grid from variable-width to fixed-width to ensure consistency in the images and predictable box size. Justified grid elements in center and use flex-box. Also changed hovering over the images to increase in size and reduced the degree to which the images were darkened on hover.

Some width changes to be made specifically for mobile, but otherwise great, I'll go ahead and merge it.


feat: add ckb-jsonrpc-types

PR Content

Copying and pasting the ckb-jsonrpc-types into this project. We propose that the ckb-sdk-rust should maintain its own jsonrpc-types, facilitating the addition of developer-friendly features.
Extensions have been made to the local version of jsonrpc-types to provide deserialization-friendly enhancements for ResponseFormat and BlockResponse.
Based on the local version of jsonrpc-types, we've refactored methods in CkbRpcClient that are related to ResponseFormat
and BlockResponse.

Deprecation Notice
Building on the aforementioned changes, a deprecation notice has been added to the pub trait ResponseFormatGetter, in preparation for its future deprecation in upcoming versions.
pub trait ResponseFormatGetter<V> {
    #[deprecated(note = "This method is being phased out in favor of `ResponseFormat::get_value`.")]
    fn get_value(self) -> Result<V, crate::rpc::RpcError>;
    #[deprecated(note = "This method is being phased out in favor of `ResponseFormat::get_hex`.")]
    fn get_json_bytes(self) -> Result<JsonBytes, crate::rpc::RpcError>;
}

More Details
based on pr

https://github.com/nervosnetwork/ckb-sdk-rust/pull/80

add methods for ResponseFormat
/// Retrieve the data in JSON format from the ResponseFormat
pub fn get_json(self) -> Result<V, String> {
    match self.inner {
        Either::Left(v) => Ok(v),
        _ => Err("Not in JSON format".to_string()),
    }
}

/// Retrieve the data in molecule serialized hex format from the ResponseFormat
pub fn get_hex(self) -> Result<JsonBytes, String> {
    match self.inner {
        Either::Right(json_bytes) => Ok(json_bytes),
        _ => Err("Not in hex format".to_string()),
    }
}

add method for BlockResponse
/// Get the regular block response.
///
/// Returns `Ok` with the wrapped `ResponseFormat<BlockView>` if the variant is `Regular`,
/// otherwise returns `Err` with an error message.
pub fn get_regular(self) -> Result<ResponseFormat<BlockView>, String> {
    match self {
        BlockResponse::Regular(regular) => Ok(regular),
        _ => Err("Not a Regular variant".to_string()),
    }
}

/// Get the block response with cycles.
///
/// Returns `Ok` with the wrapped `BlockWithCyclesResponse` if the variant is `WithCycles`,
/// otherwise returns `Err` with an error message.
pub fn get_with_cycles(self) -> Result<BlockWithCyclesResponse, String> {
    match self {
        BlockResponse::WithCycles(with_cycles) => Ok(with_cycles),
        _ => Err("Not a WithCycles variant".to_string()),
    }
}

Replace this PR with #92


TreeGrid not working in Common.GridEditorBase

I am Trying to show in my form order and orderItems. The order item will be loaded in a grid.Certain orderitems have a parentId which will be id of an item in same table.But for some reason treeGrid mixin is not working in GridEditorBase.But it works fine with EntityGrid.I am adding my code
GridEditor

OrderItemROw

OrderRow with masterdetail relation

I already saw two posts here with some solutions.But i cant understand it or how they got it to work

TreeGridMixin works at onViewProcessData event, which does not happen for in memory grids. See source of TreeGridMixin and try to implement something similar.

Thnx for clarifying.I will try a custom implementation


Passing no consumable to the powershift action still tries to use a nil item.

not a big issue just annoying message in chat, need to check for nil.

fixed


[Change Request] codeunit 905 "Assembly Line Management" - Event "OnCopyAssemblyDataOnAfterToAssemblyLineInsert" - Add parameter "FromAssemblyHeader" : Record "Assembly Header"

Describe the request
Hello, can you please add to the procedure "OnCopyAssemblyDataOnAfterToAssemblyLineInsert", the input parameter FromAssemblyHeader: Record "Assembly Header", in codeunit 905 "Assembly Line Management" ?
FROM :
[IntegrationEvent(false, false)]
local procedure OnCopyAssemblyDataOnAfterToAssemblyLineInsert(var AssemblyLine: Record "Assembly Line"; var ToAssemblyLine: Record "Assembly Line")
begin
end;
TO :
[IntegrationEvent(false, false)]
local procedure OnCopyAssemblyDataOnAfterToAssemblyLineInsert(var AssemblyLine: Record "Assembly Line"; var ToAssemblyLine: Record "Assembly Line"; FromAssemblyHeader: Record "Assembly Header")
begin
end;
Additional context
We need to check some values on "Assembly Header" record after "Assembly Line" was inserted.
Internal work item: AB#554321

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 25639.


Unable to store notifications in indexDB

in messaging.setBackgroundMessageHandler() method i am trying to store the messages in indexDB. it is not storing.  Below is my code in service worker
const messaging = firebase.messaging();
var setupDone = false;
 var storage = {
        setup: function() {
            return new Promise(function(resolve, reject) {
                var request = indexedDB.open('notidb', 1);
                request.onsuccess = function (e) {
                    setupDone = true;
                    var db = e.target.result;
                    storage.db = db;
                    resolve();
                };
                request.onupgradeneeded = function (e) {
                    storage.db = e.target.result;
                    if (storage.db.objectStoreNames.contains('notifications')) {
                        storage.db.deleteObjectStore('notifications');
                    }
                    storage.db.createObjectStore('notifications', {
                        keyPath: '_id'
                    });
                };
            });
        },
        transaction: function (mode) {
            var trans = storage.db.transaction('notifications', mode);
            return trans.objectStore('notifications');
        },
        add: function (notification) {
            return new Promise(function(resolve, reject) {
                var request = storage.transaction('readwrite').put(notification);
                request.onsuccess = function () {
                    resolve(notification);
                };
                request.onerror = function() {
                    reject();
                };
            });
        }
    };
messaging.setBackgroundMessageHandler(function(data) {
if (!setupDone) {
        storage.setup().then(function() {
            storage.add(data);
        });
    }
    else {
        storage.add(data);
    }
return self.registration.showNotification(notificationTitle,notificationOptions);
}

you need to return a full promise chain (i.e. you are just leeting the storage.*() calls just start without waiting for them to finish. The service worker could be killed before indexdb does it work.
This is also not an issue with the sample or SDK and stackoverflow would be a better place for this question.


ForEachFeatureAtPixel gives layer null

Describe the bug
Calling ForEachFeatureAtPixel returns layer as null when layer is added to layer group with group.getLayers().push()
To Reproduce
Create map with layer group
Add layer to group with function push
Try to use ForEachFeatureAtPixel
Feature is returned correctly, but layer comes as null
Expected behavior
Layer should be returned correctly by the function

Thanks for the report! Can you provide a minimal example on codesandbox that shows the error? You can use the edit button in any example on https://openlayers.org/en/latest/examples/ to get a starting point.

Thanks for the report! Can you provide a minimal example on codesandbox that shows the error? You can use the edit button in any example on https://openlayers.org/en/latest/examples/ to get a starting point.

Sorry for the delay but caught up on another project. After some more in depth research I was able to conclude the problem was not on the .push() method but it was caused by the Modify interaction. I will try to redo the steps which led to the features having a null layer when the layer was source of the modify interaction, sorry for the mistake!


Build peewee for WebAssembly

[ ] https://github.com/emscripten-forge/recipes/issues/295

Is there a difference in building for Pyodide and XEUS-Python?

While Pyodide provides many scientific computing packages, its monolithic distribution model does not allow to specify package versions

https://blog.jupyter.org/mamba-meets-jupyterlite-88ef49ac4dc8
Open questions:

[ ] do packages with C extensions need to be added differently?
[ ] how can I install from the emscripten-forge channel?
[ ] can I install upon build/at runtime?
[ ] how does this work with the XEUS-python kernel?

Empscripten-Forge
As per (15-03-2023) the instructions at Setup Local Build are intended to work only on Linux X64. For Apple ARM, use this workaround: https://github.com/emscripten-forge/recipes/issues/277.

Build process on ARM appears to be working with the fixes here:

[x] https://github.com/emscripten-forge/recipes/issues/277

...potentially relevant for file structure:

[ ] https://github.com/jupyterlite/jupyterlite/issues/1041


NURBS patch quadrature

This PR introduces new features for numerical integration optimized on NURBS patches rather than elements, for NURBS spaces. Integration rules can be defined in various ways on patches. One option is to compute reduced (sparse), approximate integration rules on patches, using a new NNLS (non-negative least squares) solver for the under-determined systems consisting of the constraints defined by each 1D rule in a tensor product rule applied to the 1D basis functions. For patches, there can be many more basis functions than integration points, giving the potential for reduction in the number of points.
Sample runs show that considerable speed-up is obtained from using patch-wise integration rather than element-wise, and reduced rules give further speed-up.
There is an assumption that the NURBS weights are all 1, which is common in NURBS meshes but not always a valid assumption.
Tasks for future work include

parallel support,
GPU support for NURBS PA kernels,
diagonal assembly (for Jacobi preconditioning),
support for NURBS with non-unit weights,
more robust reduced rule computation.

The issue of ensuring "more robust reduced rule computation" is that the computation of reduced rules with NNLS fails in some cases. In order for the system to even be well-posed, the FEM order (affecting the number of basis functions) and integration order (affecting the number of integration points) must be valid choices. When invalid choices are made, the code will fail, and it would be better to simply use the full integration rule.
In NURBSExtension, the new data members p_dof and patch_ijk are set by NURBSExtension::Generate3DPatchDofTable() but are never used in this PR. They seem worth keeping as potentially useful data.
A couple of functions are included, which are inefficient and not used. They were written initially as simple implementations, later optimized in the functions that replaced them. The original, inefficient versions can be removed before this PR is merged. The only reason to include them is to help readers understand how the patch-wise assembly works. Those functions are AssemblePatchMatrix_simpleButInefficient and AddMultPatchPA_inefficient.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3088
@dylan-copeland
@tzanio
@psocratis + @mlstowell + @v-dobrev
1/8/23
⌛due 1/22/23
⌛due 1/29/23

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

I can confirm that there are large gains te be made. So this PR seems very good news.
It seems quite involved so I will try to unpack it carefully.

I noticed that I did not finish my review from some time ago. I have hit the finish button just now and I have removed comments which are not relevant anymore.
This looks like a lot of work you have done!

High-level comments:

I like the idea of switching from integration over elements to integration over a patch. I was thinking about changing the integration rule (and ip count)  every element, but that is horrible. This seems like the way to go.

I have not looked at the NNLS solver and quadrature rule itself, but I think that will be more a courtesy thing then something else.

I am not convinced yet by the PatchDofTable addition to the NURBS class. I will clone the PR and have a closer look, and wait for some clarifying answers.

I think the NNLS solver class might need some tidying up.
I have some questions/comments regarding the NNLS solver:

It does not inherent from Solver, opposite to most other solvers. I can see this might be due to  upper and lower limits for the solve  resulting the a-traditional call:

  void Solve(const DenseMatrix& matTrans,
              const Vector& rhs_lb,
              const Vector& rhs_ub, Vector& soln);

However....
2) In bilininteg_diffusion_patch.cpp there is a call
 void SolveNNLS(DenseMatrix & Gt, Vector const& w, Vector & sol)
I think this routine needs to move to the NNLS solver class. Moreover, this call can be made analogous to the other solver Mult calls.  I think.

The interfacing of parameters seems different then on the other solver classes. It seems preferable to make them inline with the other solvers.
Additionally, the delta in SolveNNLS is currently hardwired.

I think it would be beneficial to add a unit test to test the NNLS solver.

Perhaps the NNLS solver class can be handled in a separate PR? This might streamline the process and get other (solver oriented) reviewers involved.

Similar to the issues raised with the NNLS solver I have some comments on the intrules.

In bilininteg_diffusion_patch.cpp  there is a routine GetReducedRule. I think this shoudl be moved to  intrules.cpp
The new reduced integration rule  should have a unit test.

The miniapp ./nurbs_patch_ex1 does not always work. Perhaps I am doing something stupid....
I see what is the issue.
The -iro value needs to be large enough wrt the -incdeg value. You need soem minimal integration order to make sure the NNLS system has the correct dimensions.
I think this should be better documented, or better yet the iro should be modified to the minimal working order with a warning message perhaps.

Thank you @IdoAkkerman for your suggestions. You are right that the NNLS class could be improved. It is adapted from another code outside MFEM, without the MFEM Solver class in mind. Some issues with making it derived from the Solver class are (i) as you mentioned, SolveNNLS would need to become the Mult function, assuming that the upper and lower bounds should be computed as in that function, which limits the generality of usage of NNLS; (ii) the operator must be a DenseMatrix in order to access entries; (iii) NormalizeConstraints scales the rows of the DenseMatrix.
These issues are addressed now in the following ways: (i) SolveNNLS is now the Mult function, and Solve is still a public function, so that it can be called for any upper and lower bound functions a user may want to use; (ii) a type cast verifies the type DenseMatrix; (iii) instead of scaling the DenseMatrix, NNLS now stores the row scaling in a vector.
I also added a small unit test for NNLS, but the miniapp is a better test. Note that regression testing on the miniapp sample runs should also ensure NNLS is not broken.
In the case that insufficient integration points are used in NNLS, there is now an error message informing the user to increase the number of points by increasing the order of integration. I don't think we can do more than printing an error message, i.e. we cannot pass this information back to the driver code through the integrator API.
I added some documentation for GetReducedRule but did not move it to intrules.cpp, because it is very specific to DiffusionIntegrator.

What happens when patch assembly is requested for a non-NURBS mesh?
I think the assembly will be skipped and an obscure error is given due to it.
Perhaps it is better to omit the option is it can not be used -- plus a message of ignoring the flag.

@IdoAkkerman Good point, that the failure for a non-NURBS mesh was not informative. I added an MFEM_VERIFY with an error message in BilinearForm::Assemble, since that function applies the integrators to a mesh. The integrators themselves do not know what mesh will be used, so we cannot check when defining the integrator.

@dylan-copeland Please inform me if I have overstepped the netiquette, but I changed some of the interfaces with the
NURBSExtension class. As mentioned before I did not see the need for some of the additions. In closer look there seemed a large overlap with already provided features. I think it helps for future maintenance and extensibility that the code is a concise and uniform as possible. So i hope you see the value of my "addition".

Thanks @IdoAkkerman for your interface changes. I agree that your changes are an improvement.

Ping @v-dobrev @psocratis

@dylan-copeland, I'll try to review the PR this week. Can you please resolve the conflicts with master?

Ping @v-dobrev @psocratis

@psocratis and @v-dobrev -- are you interested in reviewing this?

@psocratis and @v-dobrev -- are you interested in reviewing this?

Yes I will take a look at it this week

I have some small comments here and there, but overall this looks very good. I am not so familiar with nurbs so I did the best I could. Btw, what would it take to support this in parallel?

Thanks @psocratis for your review. In addition to parallel support, there are several other future tasks listed in the PR description. I am not sure yet what that implementation will entail. It will be simpler if NURBS patches are not partitioned in parallel, in which case it may be straightforward.

@dylan-copeland , there is a test failing due to the latest commit

It looks like we hit another status letter combination in branch-history that is not handled: RA, see https://github.com/mfem/mfem/actions/runs/5722539954/job/15505752072?pr=3088.
Maybe we should treat it the same way we treat MA? @pazner, what do you think?

It looks like we hit another status letter combination in branch-history that is not handled: RA, see https://github.com/mfem/mfem/actions/runs/5722539954/job/15505752072?pr=3088.
Maybe we should treat it the same way we treat MA? @pazner, what do you think?

I think something like this patch should do it:
diff --git a/tests/scripts/branch-history b/tests/scripts/branch-history
index f0c038df7..5b9539839 100755
--- a/tests/scripts/branch-history
+++ b/tests/scripts/branch-history
@@ -157,6 +157,6 @@ foreach my $sha (@commits) {
         $blob_size += $sz1 < $sz2 ? $sz1 : $sz2; }
-      elsif ($mode eq "AM") {
+      elsif ($mode =~ m/A[MR]/) {
         my $sz2 = int(`git diff -U0 --binary $src2 $dst | gzip -c | wc -c`);
         $blob_size += $sz2; }
-      elsif ($mode eq "MA") {
+      elsif ($mode =~ m/[MR]A/) {
         my $sz1 = int(`git diff -U0 --binary $src1 $dst | gzip -c | wc -c`);

@tzanio, this PR should be ready for merging in next.

Merged in next for testing...


Helm config question

Hello, I have a question about config when using helm install vgpu.
https://github.com/4paradigm/k8s-vgpu-scheduler/blob/master/docs/config.md
For schedular.defaultMem, I am a little confuse about the meaning.
Is that means the limit of GPU resources that I can assign to schedular for scheduling GPU?
for example, if I have a nvidia 2060 super with 8G memory, should I set the config as follew?
schedular.defaultMem=8000
I'm afraid that I misunderstand about the config,
Your prompt reply would be greatly appreciated.

oh, I figure out is gpu device memory👌


invalid capacity 0 on image filesystem

When running microk8s.kubectl describe node ubuntu I am getting the following error
Warning  InvalidDiskCapacity      2m54s  kubelet  invalid capacity 0 on image filesystem
Normal   Starting                 2m54s  kubelet  Starting kubelet.
Warning  InvalidDiskCapacity      2m42s  kubelet  invalid capacity 0 on image filesystem
Normal   Starting                 2m42s  kubelet  Starting kubelet.
Normal   Starting                 2m30s  kubelet  Starting kubelet.

Normal   Starting                 2m5s   kubelet  Starting kubelet.
When describing pod - I get the following error Warning FailedScheduling 30s (x33 over 41m) default-scheduler 0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.
From what I know I am not running ZFS on my Raspberry Pi 4 - but I have a 128gb sd card with an ext4 filesystem. I have tried this guide - but I don't have a ZFS pool....
Not sure where to go from here.

I have the same issue here. Also running on Raspberry Pi 4 (2G RAM, 128G SD card) with Ubuntu Server 20.04.


Specifying translation namespace on the component level

Hello,
We are currently using ngx-translate the way we specify namespace together with the translation key for each line:

{{'Admin_Member_EditForm.FirstName' | translate}}

Back in the past when we were working with AngularJS, angular-translate plugin would allow us to do to this:

{{'FirstName' | translate}}

Above is the pseudo-code how it might look with ngx-translate.
The goal is to eliminate specifying namespace in every directive/pipe, but instead to specify it once on the component level (actually on the parent HTML element).
Is this supported by ngx-translate?
If not, are there any plans for this / any workarounds that we could do to make this happen?

#1284

#1284


Change Debt value for TopLevelPropertyNaming, UnusedImports & UnusedPrivateMember.

I really like that the Debt is shown in the reports now however I feel like the estimates should be closer to how much you actually spend removing the code smell.
Ideally, the overall debt could be a realistic estimate how much time you'd need to spend in a new code base which isn't using Detekt yet.
Probably before 1.0 we should go through all of the issues and do some planning poker :D

I think 1 minute is a bit too short for fixing an issue (opening IDE, have a second thought about the smell, committing). This might be feasible in a small project but certainly not in an enterprise level project.

I don't think we should include opening the IDE and comitting the changes into the debt values.

TopLevelPropertyNaming is a simple rename that can be done by the IDE
UnusedImport is as simple as deleting the line. If you know your way with sed you can even remove thousands of those within seconds.
UnusedPrivateMember Simple removal of something. Although something like 2-3 minutes might be more realistic if you want to gauge whether this should be used or not.

I think we should be more conservative. 5 minutes is minimum if you consider choosing a good commit message, opening a PR, review the changes and merge them upstream.

Hmm seems like I could not convince you so I'll close this and just mentally divide that debt number by something between 2 and 5. (zwuenf :D)

:)
Thanks for bringing up the discussion though.


Don't allow LF or CR in the middle of TextFormat string literals.

Update the conformance failures list to match.
Fixes #1085

This one was much easier.  😄
The conformance test is just \n, but I went with both LF and CR to play it safe.


Updated container base image to use node 4.4.4

I noticed that this container was broken, it suffered from the issue below.  I've updated it to use node 4.4.4, thought you might be interested.  Cheers!
https://github.com/joeferner/redis-commander/issues/168

I was hoping to keep this image based on Alpine Linux to keep it smaller.  Is the issue that the version of node is not new enough?

I believe the issue was that the latest version of node is too new/incompatible with redis commander.  I bet you could get it to work with Alpine, this was just easier for me to get things running.  You should check if your container works still, perhaps something changed in a repo you reference?  When I built it it would fail on the first HTTP request.

OK, I will take a look at this and see if I can get it working properly based on Alpine.
Thanks @bobbotron

Have a look at https://github.com/mhart/alpine-node
You could probably use mhart/alpine-node:4.4.5 as a base image.

Will do.  That looks like a good solution

I changed the base image as suggested, which has fixed the issue.

Great, thanks!  👍 :)

Nice, thanks.


added configuration for self debugging

shouldn't this have "preLaunchTask": "npm" to compile the .ts files to .js first?

fixed


Adding Jamf Connect License Status

Would it be possible to include if Jamf connect is licensed?

@dornoam41 definitly - should be able to decode and show the state. Will consider adding this in next release

@dornoam41
Would this be something that's helpful?

Yep, looks good, thanks for adding that 👍

Added in version 2.1.0


babel6

refactored project with babel6, all had been configured and working, babel6 needs extraconfiguration to make it works but it's all done, hope this keeps the project current

LGTM

.babelrc had to be added to make gulp work with es6 but if you add the presets in webpack.config
       {
          test: /\.js$/,
          exclude: [/app\/lib/, /node_modules/],
          loader: 'ng-annotate!babel',
          query: {
             plugins: ['transform-runtime'],
             presets: ['es2015', 'stage-0']
          }
       }

you will have errors
/home/blackend/WebstormProjects/NG6-starter/node_modules/webpack-core/lib/LoadersList.js:54
if(!element.loader || element.loader.indexOf("!") >= 0) throw new Error("Cannot define 'query' and multiple loaders in loaders list");
^
Error: Cannot define 'query' and multiple loaders in loaders list
at getLoadersFromObject (/home/blackend/WebstormProjects/NG6-starter/node_modules/webpack-core/lib/LoadersList.js:54:65)
at LoadersList. (/home/blackend/WebstormProjects/NG6-starter/node_modules/webpack-core/lib/LoadersList.js:78:12)
at Array.map (native)
at LoadersList.match (/home/blackend/WebstormProjects/NG6-starter/node_modules/webpack-core/lib/LoadersList.js:70:19)
at Tapable. (/home/blackend/WebstormProjects/NG6-starter/node_modules/webpack/lib/NormalModuleFactory.js:81:64)
at /home/blackend/WebstormProjects/NG6-starter/node_modules/webpack/node_modules/async/lib/async.js:251:17
at done (/home/blackend/WebstormProjects/NG6-starter/node_modules/webpack/node_modules/async/lib/async.js:132:19)
at /home/blackend/WebstormProjects/NG6-starter/node_modules/webpack/node_modules/async/lib/async.js:32:16
at /home/blackend/WebstormProjects/NG6-starter/node_modules/webpack/node_modules/async/lib/async.js:248:21
at /home/blackend/WebstormProjects/NG6-starter/node_modules/webpack/node_modules/async/lib/async.js:572:34
that's why need the .babelrc out
{
  "presets": ["es2015", "stage-0"]
}

Closing this since we already use babel6


LF normalization disabled in .gitattributes

I see this in .gitattributes:
# Disable LF normalization for all files
* -text

Why do we do this?  When I git clone the repo on Linux and test/edit files, the line endings are screwed up in VI.

When I git clone the repo on Linux and test/edit files, the line endings are screwed up in VI.

What do you mean by "line endings are screwed up in VI"? I would expect it to detect CRLF files without issue.

Why do we do this?

In short, because I didn't want to deal with a commit to normalize line endings in the repo (merge conflicts for every open PR). That said, I just stumbled on merge.renormalize (which has existed since 2010?!) that should help mitigate that issue. I wonder if GitHub supports that by default?

All of the source files show ^M (carriage return) in VI on Ubuntu.  Normally, the repo would clone down on Linux with just LF for new lines.  Not a huge deal.  Was just wondering if it would be worth changing this for an eventual 1.0.0 release as I (and hopefully others) edit & test the module directly on Linux.


[Coverity CID :203441]Null pointer dereferences in /subsys/bluetooth/mesh/transport.c

Static code scan issues seen in File: /subsys/bluetooth/mesh/transport.c
Category: Null pointer dereferences
Function: bt_mesh_heartbeat_send
Component: Bluetooth
CID: 203441
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

Marked as false positive in Coverity


Gml 3.2 support

We have tried to access the WFS features from the federal of tyrol from
https://gis.tirol.gv.at/arcgis/services/Service_Public/OGD/MapServer/WFSServer?request=GetCapabilities&service=WFS
and recognized, that the WFS layers are provided as GML version 3.2.
After dissecting the GML3 parsers of ol3, we came up with a patch for adding GML-3.2 read support in a way, that it does not seem to heavily interfere with existing code.
Please review our changes and give us feedback. This is our first contribution to openlayers, so be graceful, whatever regrets may be, we have done our best ;-)
Best Regards, Wolfgang Glas

Sorry, that we bothered travis for the first part, hopefully I've fixed these issues now.

If you do not have a requirement to use WFS 2.0, you can use WFS 1.1.0 and get GML 3.1, which is fully supported by OpenLayers: https://gis.tirol.gv.at/arcgis/services/Service_Public/OGD/MapServer/WFSServer?request=GetCapabilities&service=WFS&version=1.1.0
Since XML based feature formats are not really efficient for transporting vector features to a client, you might also want to look into using GeoJSON as transport format.

Hello Andreas,
Thanks for your advice,  I was really blind concerning the downgrade capability of out tyrolean service implementation.
Unfortunately, the guys there do not offer application/json as an output format, that's why we started with alls the GML hazzle :-/
BTW, we've improved and extended a django project for delivering WFS layers as XML and JSON, see https://github.com/wglas85/django-wfs ;-)
However, I think that my patch (apart from the newbie travis problems, sorry again) is quite consistent and cleans up other issues in the GML3 code such as using the constant ol.format.GMLBase.GMLNS instead of eternally replicating the string constant 'http://www.opengis.net/gml'.
So please consider to merge it, maybe we should state 'basic support for reading GML-3.2 features is provided' in the docs.
Best Regards, Wolfgang

@bartvde is the OCG format expert, so I think he should decide.

I'm not sure about this whole ol.format.GML3.makeNamespaceMap_ stuff, why is it needed? KML has multiple namespaces as well for instance https://github.com/openlayers/openlayers/blob/master/src/ol/format/kml.js#L117:L122

Hello Bart,
My makeNamespaceMap_ function is an exact duplicate of ol.xml.makeStructureNS, of which I was unaware.
The reason for assembling the maps from namespace to handler function in this way is, that you may want to reuse constants like ol.format.GMLBase.GMLNS, which is impossible, if you directly instantiate a javascript object by the {key: value,....} syntax, because - according to my experience - there are only string constants allowed as keys, not complex expressions like ol.format.GMLBase.GMLNS.
I will refactor the patch to use ol.xml.makeStructureNS, so the GML code is in line with the coding practice of the KML module.
Regards, Wolfgang

OK, I brought my gml-3.2 patch in line with the KML practices,
Regards, Wolfgang

this looks better @wglas85 only wondering now if there is a way to keep the GML3.2 specific stuff out of the base class?

Hello Bart,
I think, that we could make the GML base class unaware of the detailed GML namespaces, if we refactor the method ol.format.GMLBase.prototype.readFeaturesInternal, currently parses FeatureCollection, featureMembers, featureMember(GML) and member(GML-3.2) tags.
When debugging, I recognized that this method occurs twice in the call stack, because the FeatureCollection parser calls  ol.xml.pushParseAndPop, which in turn comes back to ol.format.GMLBase.prototype.readFeaturesInternal when hitting member tags.
I've no clue, whether this call structure is needed for other variants of GML and a refactoring of this method seems to be unrelated to my GML_3_2, but maybe you find a better solution rightaway.
Maybe the refactoring of ol.format.GMLBase.prototype.readFeaturesInternal  could be discussed in the aftermath?
What's your opinion?
Regards, Wolfgang

how is the status of this? i might need to load WFS2.0.0/GML3.2 data with openlayers
and might not be able to fall back to WFS1.1.0

GML-3.2 support was deemed to be not so important, so the maintainers refused to merge my pull request, maybe you might convince them.

@wglas85 got a similar problem with gml3 Data flipped coordinate  (see my pull request)
They ignored my issue Ticket first,
But my change break on the test cases

@bartvde What do you think about this in its current state? To me it looks good, and it does not add complexity. But I'm lacking the in-depth insight into our XML parsers.


Specific save on quit, will cause double-saving

Probably worth it to figure it out, versus potentially having other issues as reported.
@Maxopoly  @rourke750

well considering that the longer this lasts the worse fixing it is going to get I am for putting this online.
Is it safe to merge this and roll it out?


Fixed assertion in one of the test and optimized retrieval of authentication header

Fixed an assertion in AppServiceLoginHandlerTests/CreateToken_CreatesExpectedToken for validating timespan between issue and expiration of token.
Optimized retrieval of authentication header from header with single call to TryGetValue.

Hi @chintans, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

Hi @chintans. If you go ahead and remove that using Sysetm.Diagnostics, we can get this merged in. Thanks!

@brettsam I have removed using System.Diagnostics; as per your instruction. Can we merge it now?

Looks good. Thanks for the contribution!


JVM allocation on NodePools

As i can see, we always declaring the JVM to be "-Xmx512M -Xms512M" unless the client as declared else inside of the CRD (nodepool.jvm) .
That's means that if a client is resizing the RAM allocation inside of the NodePool, if he didnt updated the JVM as well, it will still be hardcoded "-Xmx512M -Xms512M".
I think that we need to add a logic in the code that takes the request and limit of the MEM inside of a node pool, divide it by 2 (or other calculation that we will agree on) and put that value under the JVM opts.

This looks similar to what was discussed in #171 in context of RAM percentage. Can it (RAM percentage configuration) be used there on pod side by default to avoid extra actions on operator side?


OpenCL error -37 (CL_INVALID_HOST_PTR)

Hello Ryan,
I compiled successfully, but when I run I get the following error:
Frame: 0
StepTime: 0.0333
Update Fluid Cells:             0
Num Fluid Cells:    95767
Num Marker Particles:   735903
Reconstruct Fluid Surface:      0
Update Level set:               0
Reconstruct Output Surface:     0
ERROR: Creating position data buffer (-37)
fluidsim: src/clscalarfield.cpp:423: void CLScalarField::_checkError(cl_int, const char*): Assertion `err == 0' failed.
Aborted (core dumped)
I compiled on Ubuntu 15.10 with nvidia opencl 352
Unfortunately that is all the info I can give.

Hello Gottfried,
Thank you for letting me know about this issue. Would it be possible for you to rerun the program on the "debug_clscalarfield" branch and copy the output? I'm hoping that the output will help me understand what is causing this error.
https://github.com/rlguy/GridFluidSim3D/tree/debug_clscalarfield
Greatest Regards,
Ryan

I ended up running into the same error during a simulation and was able to debug and resolve the error. The master branch has been updated with the correction in this commit.
Hopefully this fixes the error you were running into.

Thank you for your efforts, will test once I'm back at my workstation!

Hello, I fetched the debug_clscalarfield branch. Running fluidsim now yields the following output:
Initializing OpenCL Device:
Num platforms: 1
Found first preference CL device.
fluidsim: src/fluidsimulation.cpp:1017: void FluidSimulation::_initializeCLObjects(): Assertion `_scalarFieldAccelerator.initialize()' failed.
Aborted (core dumped)

hmm, the output above was on a fresh build. after doing a make clean and make again, here is the new output:
./fluidsim
Initializing OpenCL Device:
Num platforms: 1
Found first preference CL device.
30-Apr-2016 16h10m18s
Frame: 0
StepTime: 0.0333
Update Fluid Cells:          	0
Num Fluid Cells: 	95767
Num Marker Particles: 	735903
Reconstruct Fluid Surface:  	0
Update Level set:           	0
Reconstruct Output Surface: 	0

Computing velocity scalar field for direction: 0
Using CL device:
CL_DEVICE_NAME:                GeForce GTX 580
CL_DEVICE_VENDOR:              NVIDIA Corporation
CL_DEVICE_VERSION:             OpenCL 1.1 CUDA
CL_DRIVER_VERSION:             352.63
CL_DEVICE_OPENCL_C_VERSION:    OpenCL C 1.1
CL_DEVICE_TYPE:                GPU
CL_DEVICE_MAX_CLOCK_FREQUENCY: 1544MHz
CL_DEVICE_GLOBAL_MEM_SIZE:<PHONE_NUMBER>
CL_DEVICE_LOCAL_MEM_SIZE:      49152
CL_DEVICE_MAX_MEM_ALLOC_SIZE:  805224448
CL_DEVICE_MAX_WORK_GROUP_SIZE:<PHONE_NUMBER>
CL_DEVICE_MAX_WORK_ITEM_SIZES: 1024 x 0 x 1024
Adding 735903 point values to scalar field:
Grid Dimensions: 65 x 64 x 64
Scalar field Dimensions: 65 x 64 x 64
Weight field Dimensions: 65 x 64 x 64
Cell size: 0.125
Particle Radius: 0.125
Field offset: 0 0.0625 0.0625
_initializePointValues():
Num Points: 735903
Num Values: 735903
Num PointValues: 735903
_getWorkGroupGridDimensions():
_chunkWidth: 6
_chunkHeight: 6
_chunkDepth: 6
WorkGroup grid dimensions: 11 x 11 x 11
_insertParticlesIntoWorkGroupGrid():
Num particles: 735903
Inserted 1742785 particles into grid.
Counting particles in grid:
Num particles: 1742785
_initializeWorkChunks():
Num WorkChunks: 2260
Num particles in work chunks: 1742785
_getMaxChunksPerWeightPointValueComputation():
pointDataSize: 16000
fieldDataSize: 1728
offsetDataSize: 12
numPositionAllocItems: 50326
numFieldAllocItems: 465986
numOffsetAllocItems: 67102037
allocLimitCount: 50326
totalDataSize: 17740
globalMemLimitCount: -60546
hardwareLimit: -60546
softwareLimit: 5000
Max chunks: -60546
Computing 0 WorkChunks:
_computePointValueScalarWeightField():
Num WorkChunks: 0
Max particles in work chunk: 0
Initialize DataBuffer:
Num Particles: 0
Num WorkChunks: 0
_getHostPointValueDataBuffer():
numParticles: 0
numElements: 0
Num WorkChunks: 0
Buffer size: 0
_getHostScalarFieldDataBuffer():
buffer size: 0
_getHostChunkOffsetDataBuffer():
buffer _getHostChunkOffsetDataBuffer: 0
_initializeCLDataBuffers():
buffer.pointDataH.size(): 0
buffer.scalarFieldDataH.size(): 0
buffer.offsetDataH.size(): 0
pointDataBytes: 0
scalarFieldDataBytes: 0
offsetDataBytes: 0
ERROR: Creating position data buffer (-37)
fluidsim: src/clscalarfield.cpp:479: void CLScalarField::_checkError(cl_int, const char*): Assertion `err == 0' failed.
Aborted (core dumped)

Hello Gottfried,
Thanks for the output! It looks like the error you were encountering was caused by an integer overflow error. The error has been corrected in the master and debug_clscalarfield branch.
I hope that this fixes the error you were receiving!
Best Regards,
Ryan

thank you so much, works like a charm now!

Hi Gottrfried,
this is a bit offtopic, but I hope you might share the one or other hint.
I stumbled across this thread by accident; having troubles with a program running into openCL error - 37.
Further I do understand this is no related to your app at all. I'm just curious if you might have an idea on how fixing such an error.
Due to another error upfront I had to install Mesa3D drivers to fix another issue.
The idea, could Mesa3D be used to fix the openCL 37 error(?) without having access to the source of the initial "app" causing the error.
Any thoughts are very welcome - thank you.

Hello! The errors in this issue were triggered by the program attempting to reserve invalid amounts of memory such as reserving 0 bytes or a negative number of bytes. The cause of these bugs were due to logic errors during implementation.
What could cause this error code in your application could be specific to the program, so I'm I'm sorry to say that I'm not sure of any solutions.
I'm not sure if there is a fix for this in your situation on the user-side of your application. This is something that may need to be fixed in the application source code by the developers.


Core data initialization

Check if protected data is available prior to setting up the database
Verify that the database was opened properly before moving on to the app
Removed background fetch

Pull Request Test Coverage Report for Build 229

0 of 93 (0.0%)  changed or added relevant lines in 1 file are covered.
19 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 5.742%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Mage/AppDelegate.m
0
93
0.0%

Files with Coverage Reduction
New Missed Lines
%

Mage/AppDelegate.m
1
0.0%

Pods/mage-ios-sdk/MAGE/Observation.m
18
0.0%

Totals

Change from base Build 223:
-0.02%

Covered Lines:
1262

Relevant Lines:
21978

💛  - Coveralls


Restart claudb with persistence enabled, overwrite old persistence

When I start claudb with persistence enabled and then I quit claudb (and I can see both AOF and RDB files in the directory) , once restarted it looks like claudb overwrite the old files and in this way everything cached in the past is lost

It seems that there's an issue when claudb restores the state using redo file. It seems that rdb file is restored correctly
Exception in thread "main" java.lang.ClassCastException: com.github.tonivade.resp.protocol.AbstractRedisToken$StringRedisToken cannot be cast to com.github.tonivade.resp.protocol.AbstractRedisToken$ArrayRedisToken
	at com.github.tonivade.claudb.persistence.PersistenceManager.importRedo(PersistenceManager.java:107)
	at com.github.tonivade.claudb.persistence.PersistenceManager.start(PersistenceManager.java:60)
	at com.github.tonivade.purefun.type.Option.ifPresent(Option.java:82)
	at com.github.tonivade.claudb.ClauDB.start(ClauDB.java:79)
	at com.github.tonivade.resp.RespServer.start(RespServer.java:90)
	at com.github.tonivade.claudb.Server.main(Server.java:50)

Version 1.5.0 released with the persistence fixed, please @advancedlogic test it and let me now if its solved.
Thanks!


Bump harvester-load-balancer to v0.2.5

To fix https://github.com/harvester/harvester/issues/5137, the harvester-load-balancer image has a new v0.2.5 release.
Bump a new chart v0.2.5 release to Harvester.

Yes, you are correct. If a chart doesn't change, we just need a PR to bump the image tag in release branches: https://github.com/harvester/harvester/blob/f8469881441b92a71c6e58a493f433eccf5f3ba1/deploy/charts/harvester/values.yaml#L458, can you help create a PR for it? Thanks.
Bumping a chart when its image changes is also OK, but it is only useful when you use the chart without harvester or for testing/dev purposes.

The harvester-load-balancer chart is not used out of Harvester cluster. Instead of releasing a new chart version, just bump the image tag in Harvester v1.3 branch.
This PR is replaced by https://github.com/harvester/harvester/pull/5354


Feature gyro

@smo-key Please test and sign off :smile:

@Oksisane Code looks good - let's test tomorrow at lunch.

@smo-key @oksisane you two are welcome to test on the 4290 bot.
On Thu, Oct 22, 2015 at 8:43 PM, Arthur Pachachura<EMAIL_ADDRESS>
wrote:

@Oksisane https://github.com/Oksisane Code looks good - let's test
tomorrow at lunch.
—
Reply to this email directly or view it on GitHub
https://github.com/lasarobotics/FTCLibrary/pull/32#issuecomment-150404021
.

Thank you, @ethan-schaffer!

No problem @smo-key!
On Thu, Oct 22, 2015 at 9:04 PM, Arthur Pachachura<EMAIL_ADDRESS>
wrote:

Thank you, @ethan-schaffer https://github.com/ethan-schaffer!
—
Reply to this email directly or view it on GitHub
https://github.com/lasarobotics/FTCLibrary/pull/32#issuecomment-150411023
.

@Oksisane Tested. Please make a few changes:

All methods should return a signed integer. signed = (unsigned >= 65526/2) ? 65525 - unsigned : unsigned; should work, maybe some binary logic would be better
Fix the stall when calling resetHeading() from init()

Also, the gyro is inaccurate when it moves really fast. Can you limit this somehow?

@homu r-

:umbrella: The latest upstream changes (presumably #35) made this pull request unmergeable. Please resolve the merge conflicts.


Zoom to world

legacy gui - warp list
L 234
zoom to world is no longer accepted method now
player.zoom_to_world(position, 1.5)

Player List, L121, same issue


"Permission denied to access property" after reload()

When I try to do vcRecaptchaService.reload() it seems to work but in my js console I get this every time I click my mouse or generally interact with my app in any way:

Error: Permission denied to access property '10_1417377045946'

I found a solution here (https://groups.google.com/forum/#!topic/recaptcha/CZNuFp1ct_Y) but it's a hack: $('.pls-container').remove();.
I did try to pass a widgetId but because of #39 I was only getting widgetId = 0. Despite this, I don't see why I shouldn't be able to just call reload().
Any ideas?

You mean like this ?

Ah, okay. But still, isn't that kind of an endorsement of a hack? I mean, it works, but for how long?

Until Google fixes the issue.  You can file a bug for them to implement a way to remove/destroy the instance of recaptcha like the v1 API had.  For now, v2 doesn't have that ability and everything has to be a work-around or hack.

Fair enough, thanks. Feel free to close this issue now or when the code is released.


Collect kubelet containers network addresses

What does this PR do?

Add NetworkAddress (tuple ip/port/protocol) list to the container object
Fill this list for the Kubelet collector

Motivation
Share network information with the process agent

Codecov Report

Merging #2664 into master will decrease coverage by 0.14%.
The diff coverage is 73.91%.

@@            Coverage Diff             @@
##           master    #2664      +/-   ##
==========================================
- Coverage   56.62%   56.47%   -0.15%
==========================================
  Files         379      379
  Lines       24049    24072      +23
==========================================
- Hits        13617    13594      -23
- Misses       9513     9560      +47
+ Partials      919      918       -1

Impacted Files
Coverage Δ

pkg/util/kubernetes/kubelet/containers.go
42.85% <73.91%> (+8.71%)
:arrow_up:

pkg/clusteragent/custommetrics/provider.go
0% <0%> (-61.91%)
:arrow_down:

pkg/forwarder/worker.go
92.5% <0%> (-1.25%)
:arrow_down:

This is definitely good for us to get started thanks!

Looks good to me @hkaj, thanks a lot!


ContentControls.Add() is trimming space from user selection

I am trying to select some text and add a content control to this selected text as below.
selection.Range.ContentControls.Add(WdContentControlType.wdContentControlText);
This is trimming out the preceeding space from the selection. Thus converting only the part of the text excluding the trailing space into a control.
How do I achieve this without tampering the existing selected text. With some of the solutions I tried the existing control within the selection is getting removed.

Hi, I'm pretty sure this is not from OfficeIMO as I haven't added anything around ContentControls. Is it part of OpenXML SDK maybe?


Improve documentation in general

I'm finding it very difficult to use the firebase-query element because the documentation is very thin. Most of the properties have little to no documentation at all.

I completely agree. We need it much more detailed demos of how to use the different firebase elements together.

Also note-app demo is too complicated for a demo imo.

+1! The auth element is pretty complex and documentation doesn't cover barely anything but element creation. Can I help somehow?

Could you guys upgrade the documentation for firebase-query? I'm finding it very difficult to use.

Could you guys upgrade the documentation for firebase-document too.

Yep. Could not get started with the module.


Follow the lite build docs, build failed

https://github.com/alibaba/sealer/blob/main/docs/build/build_zh.md
RUN wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.2.0/aio/deploy/recommended.yaml
COPY recommended.yaml manifests # will not found
CMD kubectl apply -f manifests/recommended.yaml

so sorry for the confused , currently, we only support copy file and trigger layer value handler from the build context. i will update the doc later. and sealer will support "copy from" near the future.


Buffer.alloc is not a function

$ npm run test

<EMAIL_ADDRESS>test /disk/src/3d/obj2gltf
gulp test

[14:45:34] Using gulpfile /disk/src/3d/obj2gltf/gulpfile.js
[14:45:34] Starting 'test'...
Started
Jasmine started
F
createGltf
✗ simple gltf
- TypeError: Buffer.alloc is not a function

@rodebiet it looks like you may be using a very old version of Node.  obj2gltf requires a recent version of Node 4.x, 6.x, 8.x, all of which contain the Buffer.alloc function.

$ node --version
v4.2.6

Yes, that version does not have the required functionality.  (It also has known security issues).  You need to be running at least 4.5.0, but I highly recommend you switch to the latest 6.x, as 4.x will no longer be maintained by the Node Foundation starting in October.

$ node --version
v6.11.0
it now works, this issue can be closed.
mramato, thank you very much for your very fast support!


[YUNIKORN-2042] REST API for specific queue

What is this PR for?
Expose a REST API for specific queue:
/ws/v1/partition/%s/queue/%s/
Other modifications:
1
Modify the test items, which were not actually tested originally.
pkg/scheduler/objects/queue_test.go TestGetPartitionQueueDAOInfo function
2
In pkg/webservice/handlers_test.go
change some hard code string to const
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/projects/YUNIKORN/issues/YUNIKORN-2042
How should this be tested?
example:http://localhost:9080/ws/v1/partition/default/queue/root.namespaces.level1.level2
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

@wilfred-s @chia7712
Sorry for the late reply, thanks for the review.
A few changes:

In pkg/scheduler/objects/queue.go, change GetPartitionQueueDAOInfo() to GetPartitionQueueDAOInfo(exclude bool)
exclude is true, which means there is no children Queue Object, and only the children's queue path will be recorded.

In pkg/webservice/handlers_test.go, assertAppStateAllow function rename to assertAppStateNotAllow

In pkg/webservice/handlers_test.go, assertActiveStateAllow function rename to assertActiveStateNotAllow

In pkg/webservice/handlers_test.go, add new function assertQueueInvalid

Also, I would like some clarifications.
Do we recommend renaming the QueueName of PartitionQueueDAOInfo to QueuePath?
Because it is actually QueuePath
queueInfo.QueueName = sq.QueuePath

@wilfred-s Thank you for your review. I modified.


Compile for web with standalone flag

Allows for using the version with:
<script src="mam.web.js"></script>
Instead of:
<script src="mam.web.js"></script>
<script type="text/javascript">
      var Mam = require('mam.web.js');
</script>

Please resolve conflicting files and move generated mam.web.js library from lib to web folder, then we can merge this PR

Added flag and merged


Auto indent when move line up or down

When using Alt+Up or Alt+Down to move lines in code, automatic adjustment of indentation would greatly benefit languages like Python, where correct indentation does matter and saves time. Currently, as shown in the gif below, I must manually readjust indentation using TAB or Space after moving lines.

Hi @aiday-mar
My partner, @ldaanish, and I are currently students at the University of Michigan, who are interested in contributing to this issue for our software engineering project. After reviewing this issue https://github.com/microsoft/vscode/issues/224569, we were able to recreate the bug and estimate the location of the code for this issue:
https://github.com/microsoft/vscode/blob/main/src/vs/editor/contrib/linesOperations/browser/moveLinesCommand.ts
It would be great if we could both be assigned to this issue. We will ensure that we follow all of the coding and contributing guidelines. Let us know if you have further information regarding this bug.
Thank you for considering our request!

Hi @iamdereky thank you for the comment. The functionality of indenting lines on moving them up and down already exists in VS Code and I have previously incorrectly labeled this issue. This is controlled by the setting editor.autoIndent

Hi thanks for filing this issue, I was indeed able to verify your issue. Indeed moving the lines up and down does auto-indents for TypeScript files, but does not auto-indent for Python files. I debugged this a bit and discovered this happens because our inbuilt Python extension does not have indentation rules support. These should be defined at some point.

If the problem is related to the Python extension, it seems to me that this issue is related to that extension and it's better to be sent in the issues of that extension. Am I right?
https://github.com/microsoft/vscode-python

This is an issue mainly related to the inbuilt VS Code Python extension which contains a language configuration file that determines indentation rules. The extension you link could be providing its own language configuration file.


Volatile emits and rooms

Hi. I've read everywhere about volatile messages (90% of times it is all about Bierber tweets). My issue is simple.
socket.volatile.emit(...)

Seems to work without problem, but these all do not:
io.to('fooroom').volatile.emit(...)
Io.volatile.to('fooroom').emit(...)

They all return error (undefined volatile). My question is, how can I send volatile mesaages to all users in a room?
P.S. I've done some tests, and it turns out that if a user gets suddenly disconnected , and then, after hours or so, he connects again, he receives the messages that were sent in that off period, like if Socket.io were savijg them in some sort of buffer. I'm facing serious memory leaks issues, and I think this have something to do.
Thanks.

Hi @rauchg , could you please provide a reason for closing the issue?
I'm also interested in sending volatile messages to a room but it seems there's no API for that.

Closing


Update editor.md

Description of the change:
Reason for the change:
Link to original source:

Closes #

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @drespinoza,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Hello @drespinoza,Thanks again for the PR!                                         We noticed that you have earned 3 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold.                                         Also, please be sure that you have officially registered here.                                         Thank you and Happy Hacktobering!                                         Team SendGrid DX


Date is not more valid

hi there!
i have an app scheduling to notification on some special dates that i get theme from a offline database.
when i set a notification i got  the warning in my debug console " Date is not more valid".
what does it mean?

This means that the appointment date you set is in the past. In this way your notification is discarded.

This means that the appointment date you set is in the past. In this way your notification is discarded.

thanks for your response.
so what should i do?in my code in initstate i check if there is a date on today or no if no then i set the next date.

I put some scheduling examples in the Example app, maybe one of them could be useful for you.
You can find it inside the example folder here on GitHub.

Hi, can you assign this issue to me ?

Hi, can you assign this issue to me ?

how can i do this?

I put some scheduling examples in the Example app, maybe one of them could be useful for you. You can find it inside the example folder here on GitHub.

thank you i Rafael,i'll watch examples,, but another question i have that is when: i want to set next datetime i should use getNextDate or i call createnotification again?

getNextDate is just a query method to discovery what will be the next schedule date. To set a next schedule, you must use createNotification again


Use GitHub Action inputs instead of separate yml file

Why require that we check in a .mergepal.yml file when you can just as easily take those settings as action inputs?

hey, there are few patterns of how this action can be applied: more fundamentally you can have tests performed within the GHA or mergeability rules can be affected by some other events: labeling pr, approving pr, finishing some tests in thirdparty CI.
in this instance you'd end up having multiple workflow files with duplicated settings. having dedicated file in the repo allows you to simply plugin in the action in various workflow while keep the config detached


installing process

Hello.
Thank you to contributor this feature look fantastic.
I'm just a newbie with qubes OS. i would like the screen sharing functionality.
I try this to install :
sudo qubes-dom0-update qubes-video-companion
but it indicates a no match.
i think there is somthing i did not understand in installation process. is someone can light me?

As said in README.md this package is WIP, currently you need to build the package yourself, the install instructions you tried are for a future readily-built version.


Managing Versions across projects

What are the guidelines around versioning a group of projects. I see the project.json file has the version attribute in it.  However, if I want to change the version id once, across a group of projects, how can I do this?
The docs reference Shared Files... "To share code, like shared assembly info, you would create a common project with the shared code files referenced in the shared section. After that any project that references your common project will have the files compiled into it as if it was source in their project."
So I was thinking I would create a shared project and add a AssemblyInfo.cs to manage version ids.  However, the group of projects would only share . part of the version and the .<Build#> would differ through out.  How is this accomplished with DNX?  Basically, externalize the version id and maybe just reference it as a variable in the project.json. Nuget does this with $version$.   Is the AssemblyInfo.cs totally gone now and represented in the project.json?

There's a current issue open on the dnx for adding the ability to inherit project.json versions (https://github.com/aspnet/dnx/issues/1100). Today there's no automatic way to do this other than having your build script update the project.json file manually. That said, you can still use a shared assembly info and opt out of auto versioning via the project.json version attribute. You're packages will be out of sync with your assembly version in that case but it'll be no worse than it is today.
We'll need to bring back the versioning ability likely in global.json and giving you the ability to override tokens in project.json via flags passed to dnu. This isn't planned right now.

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.


Deprecate NDArrayCollector and instead use ResourceScope

Description
This PR now removes all usages of NDArrayCollector throughout the code and deprecates it as of the 1.5.0 release.
It also updates the ResourceScope to recursively move NDArrays to outer scope when in hierarchical structure of Traversables (list, set, map, etc.) and Products (tuples). It adds a method to check if the ResourceScope contains a value and fixes a bug where moveToOuterScope would move a value to the outer scope despite it not being in the inner scope in the first place.
This contains additions originally part of #14666 that were split out.
@lanking520 @andrewfayres @nswamy
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@mxnet-label-bot add [Scala, pr-awaiting-review]

@zachgk could you check the CI build?
@nswamy @lanking520 for your review


Fixed crash when unused Japanese keys are pressed.

With Japanese physical keyboard and English layout, pressing the extra keys can cause FreeRDP crash.

Looks good.
Side note: perhaps the lines above with (keysym == XK_Shift_L) || (keysym == XK_Shift_R)... would be covered by your if too and could be removed ? @awakecoding any opinion on this ?

@freerdp-bot test


extra point in bulk action example?

with some update there came a point into the grid?

yep see this here also - with Chrome at least.
@volkanceylan : I see this additional dot also in a brand new Serene test project.
In your demo project on serenity.is this is not there.
With kind regards,
John

increasing the width of the checkbox columns might be solved this issue.


Bug: Not Found Error at login

Prerequisites

[X] I have searched the repository’s issues and Kinde community to ensure my issue isn’t a duplicate
[X] I have checked the latest version of the library to replicate my issue
[X] I have read the contributing guidelines
[X] I agree to the terms within the code of conduct

Describe the issue
Followed the SDK examples and at login receive an error before it navigates to the Kinde login. I have this happening in two different projects. One project it then triggers an error handler that makes for a poor user experience.
Library URL
https://github.com/kinde-oss/kinde-sveltekit-sdk
Library version
1.3.0
Operating system(s)
Windows
Operating system version(s)
Ubuntu 24.04
Further environment details
No response
Reproducible test case URL
No response
Additional information

Validated with a clean setup of SDK: https://github.com/kinde-starter-kits/sveltekit-starter-kit/issues/11

Validated also.

This also occurs when trying to switch organizations with the follow URL format:
goto('/api/auth/login?org_code={<your_org_code>}')


Add .inspect_ptx() to cuda device function

as titled.
See usage example in notebook: https://gist.github.com/sklam/e7ad0f2151872f47d72c2ea9e674806b

Started CUDA smoketest build #46

Need to skip the test in the CUDA simulator.


Permission 'storage.buckets.get' denied on "apache-beam-ml" bucket

DirectRunner executed with "make run-direct" fails to run because public users do not have storage.buckets.get permission to the apache-beam-ml bucket.
Since DirectRunner uses model files and datasets stored in apache-beam-ml bucket as input, it seems that permission 'storage.buckets.get' to this bucket is necessary.
I work around this problem by copying the data to a bucket I have created in my project.

This should be fixed with Beam 2.55.0 (https://github.com/apache/beam/pull/30205)


Update for Spring 3.x

Creating to track a PR.
Spring 3.x has dropped support for /META-INF/spring.factories and jumps to Java 17 (javax -> jakarta). I found the current project did not work without making the change of the AutoConfigured class to @AutoConfigured and creating META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports

Hi @el8ted new version 1.1.0 released that slis compatible with Spring Boot 3.x.