28 generating mipmaps

As noted in the README there are some Validation Layer issues with this but I dont have any solutions. This issue describes the same thing at the end: https://github.com/vulkano-rs/vulkano/issues/989. Essentially when blitting and the destination and source are the same, the image layout is properly transitioned.
I was experimenting with UnsafeCommandBufferBuilder and manually creating the memory barriers and image transitions but ran into a lot of issues because I also then needed to manually synchronize and submit everything, bypassing all of the nice abstractions that Vulkano has provided and I didn't include any of that. It didn't seem worth it as its not the point of Vulkano and if I'm going to be rewriting/implementing some of these core building blocks I'd rather just spend the time working on Vulkano itself itself and get it to a point where we can idiomatically handle cases like this. I linked to Ash and their version of this tutorial so users can see what a more direct 1-1 translation of this would look like in Rust.
Let me know any feedback on this, whether you think we should figure out our own abstraction on the lower level building blocks, etc. etc. And as with the other PRs, I haven't tested on mac yet. I'm planning on getting the last section, multisampling, in and then giving it a full test sweep on Windows and Mac (and maybe a few linux flavors if I'm motivated). I started running everything through Clippy and only some internal macro stuff is getting tagged.

I will think about these issues when I get here (I'll go through the tutorial as I review and merge the previous ones).
About clippy: I just merged a Github Action that runs clippy, but allows that macro issue since I didn't find a way to fix it.

I'm new to rust but it seems that the from_buffer method of the ImmutableImage have an implementation of mipmaps - could this be used? https://github.com/vulkano-rs/vulkano/blob/v0.21.0/vulkano/src/image/immutable.rs#L351


Replace object-array with something faster for JVM implementation

Did some profiling and found that Clojure's object-array is unacceptably slow for binding late-bound params, mostly because of the "intValue" invocation and the boxing/unboxing that happens. This should be replaced with a direct invocation of creating an object array. This will require some Java code.

Implemented on master


Issue 202 - Can't send data from PhantomJS to any callback under Node…

…JS process context
The description is in the issue #202

As about Contributor License Agreement - It seems that it will be better to contribute from another account/or add another email address to this account. I'll decide what to do with it tomorrow...

I signed it! for email<EMAIL_ADDRESS>that is currently set as secondary email for my GitHub account.

Test errors are due to invalid test configuration. E.g. an error EPEERINVALID occurs because of an old npm version, it should be > 3.x.


Concerned Viewer

How will the pen work without an eraser

@gichomo  Thank you for your question while I am expecting this question. I am working on the eraser functionality. It will be updated very soon.

@gichomo  updated the eraser functionality, hopefully you can check this function. Here are the using instructions
Press button "s" to stop drawing lines
press button "e" for enable eraser
press button "p" to enable pen
Please read readme.md for more informations.
Thanks,
Dip Ghosh

This feature is added on the new release.


Chrome 60 - drag start

Anyone else having problems with drag start event since the newest version of chrome (v60)?

I am as well in my own code base, but havent found any other documentation (or people) having this problem...

I'm experiencing what may be this issue. I have two computers with "identical" Chrome configurations - same profile, same extensions, same version of Chrome, same version of Windows. Drag-and-drop works fine on one, however on the other computer it does not work. I have text in my drag-and-drop rows, and on the computer where drag is not working, I can instead highlight the text.


Always on top - custom opacity

Description of the new feature / enhancement
please add a custom opacity configuration for the always on top feature. kk thxbye 💯🙏
Scenario when this would be used?
i have a live stream of discord open (always on top) and want to browse my adult film dubai summer holiday photo library in windows explorer™. well, I only have 1 screen... so the discord window covers my dirty-directory i have opened in explorer™.
damn, my english is really bad, I'm sorry. please feel free to ask any detail (except my files!) of my feature request... but I might think you know what I am talking about and everybody (maybe like 98%) knows EXACT the same scenario :O
Supporting information
No response

/dup #28072


How to set base_model_version for SpeechToTextSession class

Hi,
I'm trying to set up for SpeechToTextSession class, everything go fine such as i could set model, customizationID, acousticCustomizationID and learningOptOut in its contructor but i could not find for base_model_version property to set it up.

This is contructor of SpeechToTextSession:

In SpeechToText class, i could recognize audio with full of settings even set up for Base_model_version for its queryParameters

This is recognize funtion in SpeechToText class:

----> So How can i set Base_model_version property for SpeechToTextSession class?

@mkistler Do you know why SpeechToTextSession doesn't support the same parameters that SpeechToText does?

SpeechToTextSession is hand-written, so parameters could have been missed during development, or the parameter was added later and the session code wasn't updated accordingly.

I confirmed that we are missing a few parameters from SpeechToTextSession, as shown in the API docs. It's missing language_customization_id, base_model_version, and metadata . I'll have those added in the next release.

Fixed in Release 1.0


[v2] Tabs fail to render when they have only one child

🐛 Bug Report
(A clear and concise description of what the bug is)
Have you read the Contributing Guidelines on issues?
yes
To Reproduce
In a mdx file, write:
import Tabs from '@theme/Tabs'
import TabItem from '@theme/TabItem'

<Tabs
  defaultValue="node"
  values={[
    {label: 'NodeJS', value: 'node'},
  ]}>
  <TabItem value="node">
    asdf
  </TabItem>
</Tabs>

Expected behavior
This will fail to render with index.js?3e4b:6 Uncaught (in promise) TypeError: children.map is not a function caused by https://github.com/facebook/docusaurus/commit/8c9f9487d6e1035f1fb41f1df228e053977ca6ce and more specifically the removal of https://github.com/facebook/docusaurus/commit/8c9f9487d6e1035f1fb41f1df228e053977ca6ce#diff-5548122e1da708235c90f8d8cc552ffa69c199f1dd82ca505c9577ac7255da73L114
Adding a non-sense tab like so will fix this:
import Tabs from '@theme/Tabs'
import TabItem from '@theme/TabItem'

<Tabs
  defaultValue="node"
  values={[
    {label: 'NodeJS', value: 'node'},
  ]}>
  <TabItem value="node">
    asdf
  </TabItem>
  <TabItem value="placeholder" />
</Tabs>

Actual Behavior
Rendering should not fail
Your Environment

Docusaurus version used: alpha 69

Reproducible Demo
(Paste the link to an example repo, including a siteConfig.js, and exact instructions to reproduce the issue.)

I'm seeing evidence that this has resurfaced with the 2.3 release. We had one page with a single tab in the tabset and it was causing the TypeError: children.map is not a function error. Removed the tabset and error disappears.

Let's track the new error in https://github.com/facebook/docusaurus/issues/8591


feat(admin): add more routes for user management

:tada: This PR is included in version 2.17.0-alpha.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


functions: add sample calling a function with an ID token

cc @grayside

Does the block this PR? Looks like we already have Java, Python, and Node.js versions of this sample. We can merge and publish this one then come back and improve after.

I was not aware those had gone through. Yes we can unblock this PR.


fixed LLVM_SYS_130_PREFIX missing when launching nix devtools

@Anton-4 @rtfeldman I don't think it is worth running CI on this again, the CI failure looks unrelated.


update kubectl convert link

/assign @natekartchner

I think we probably shouldn't be trying to fix links directly in blog posts. Instead, we should update our /static/_redirects file.
@zacharysarah What do you think?
/assign @zacharysarah

@steveperry-53 Good question. ✨ I see the merit of updates to /static/_redirects, but I want to encourage blog post authors/maintainers to keep their own content up to date. I'm also OK with proceeding on a case-by-case basis until the need for a clear policy emerges.
Happy to revisit this if we need to.
/lgtm
/approve


How to clear Haneke memory cache effectively on iOS?

Main memory cache is bloating as user requests more number of images. As user session progresses, main memory size increases which applies excess pressure on memory. This is causing out of memory exception.

Can you tell how many images/requests are causing this issue ?

We are loading thumbnails in tableview cells. So After around 50-60 requests, memory allocation reach to 150MB.


Version 0.8.4: use experimentalUpdater for buildSrc consumers

Misses supports for alias to plugin versions. Also, I found a way to test locally with buildSrc, so I'll make a new PR later, possibly with other improvements.


⚠ WSINGRESOS - RECIBOPAGO has degraded performance

In 4658cc8, WSINGRESOS - RECIBOPAGO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsRecibosPagosWeb.r) experienced degraded performance:

HTTP code: 200
Response time: 14821 ms

Resolved: WSINGRESOS - RECIBOPAGO performance has improved in cf7d04b after 21 minutes.


Badge list doesn't remember the page number on refresh

Something about the pagination control is defaulting the page back to 1 despite the value being stored in session storage... I think.

👋🏼 I'd be interested in working on this!

👋🏼 I would be interested in looking into this!


fix: validateConfig validates function task return values

This PR adds more precise validation of function tasks, which should be of the form (filenames: string[]) => string | string[]. Specifically, the return value is validated by supplying the task with an array of single filename ['[filename]'].
Fixes:

[x] https://github.com/okonet/lint-staged/issues/680

:tada: This PR is included in version 9.2.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Disable RSS for content types

It would be nice to have a disableRSS = true front matter, or define which types go into the RSS feed, or similar.

Should be handled by https://github.com/spf13/hugo/issues/2828


UI/UX improvements for dialogs

All dialogs display an error state by default, when e.g. a textfield is empty at first. From a UX perspective is this not a good practice. We should highlight nothing at first and after an interaction with the form field, we highlight the error message in the error case.

fixed with 16ce6a68879ba060c682a9971ac6e49af93e6b87


How to update secrets accessKeyID and secretAccessKey?

Hello, I'm using dataset with secret-name in spec.local. Datashim operator creates it's own secrets using data from my secret.
But then go to update accessKeyID and secretAccessKey in my secret - it does not updates in secrets, that have been created by datashim operator.

@vasili-ii At the moment, we do not allow incorporate updates to the secrets once they have been used in the Dataset object. This might not be possible to do so because we will have to recreate the PVs/PVCs which may be potentially in   use by pods


Maven build error #715

Adresses #715 .
This PR does not contain the solution to the bug stated on the issue. It just contains a test that I used to successfully reproduce the error.
Some things we found out:

The bug arises when using templates-oasp4j version 2.4.1 onwards.
The triggers are correctly read.
When using a Java entity file as input, the generation is successful.

@devonfw/cobigen

If a test should be included for this, it has to be modified a bit, otherwise this pull request can be closed


output of generated tokens as text via python tiktoken script

Hacky function that takes the gen_tokens array that is created at every 20th step and generates a python script that will output the tokens as words via tiktoken (as demonstrated in the REDME.md).
For each of those steps it creates a tiktoken_step_xx.py file and prints a message that it can be used to show the output as words.
Updated .gitignore accordingly.

haha! too hacky. I think we should just do the correct thing. There is another PR for it, let me take a look :)

Done! :) see c165855cd331ac16de684e6d15507eabdc2f1a8d
closing

Done! :) see c165855 closing

Mighty impressive ... awesome!


telegram-desktop crashes on startup

Describe the bug
telegram-desktop crashes on startup with segfault
Steps To Reproduce
Steps to reproduce the behavior:

start telegram-desktop
experience:

error: : cannot open
error: : cannot open
error: : cannot open
qt.svg: Error while inflating gzip file: SVG format check failed
Aborted (Speicherabzug geschrieben)

Expected behavior
Telegram starts
Notify maintainers
@primeos
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.142, NixOS, 21.05.git.8b0b81dab17 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.15`
 - channels(m): `""`
 - channels(root): `""`
 - nixpkgs: `/var/src/nixpkgs`

@oxalica

6d0da63aecb701cead9322806550e44a4f82c760 could potentially help with qt.svg: Error while inflating gzip file: SVG format check failed (just as a quick FYI, I'm not maintaining the package anymore and only still listed for a smother transition).

Using telegram-desktop from unstable seems to solve the issue for me, backporting #132860 should do the trick.

I've just got this problem on NixOS 21.05.4051.9e86f5f7a19.

Doesn't crash completely for me, just doesn't open:
(.telegram-desktop-wrapped:56345): GLib-GObject-WARNING **: 11:13:30.790: cannot register existing type 'GtkWidget'

(.telegram-desktop-wrapped:56345): GLib-GObject-CRITICAL **: 11:13:30.790: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(.telegram-desktop-wrapped:56345): GLib-GObject-WARNING **: 11:13:30.790: cannot register existing type 'GtkBuildable'

(.telegram-desktop-wrapped:56345): GLib-GObject-CRITICAL **: 11:13:30.790: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed

(.telegram-desktop-wrapped:56345): GLib-CRITICAL **: 11:13:30.790: g_once_init_leave: assertion 'result != 0' failed

(.telegram-desktop-wrapped:56345): GLib-GObject-CRITICAL **: 11:13:30.790: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(.telegram-desktop-wrapped:56345): GLib-GObject-CRITICAL **: 11:13:30.790: g_type_register_static: assertion 'parent_type > 0' failed

Hangs here

Nevermind, that seems to be this issue https://github.com/NixOS/nixpkgs/issues/131963


The action does not wait for the triggered workflow anymore

Hey guys! It seems like something went wrong after releasing version 1.4.0. I just switched to v.1.5.0 after using 1.3.0 and realized that the action is not waiting for the triggered workflow anymore... I have tested v 1.4.0 - the same issue. Downgrading to v 1.3.0 solves the problem. But I need the feature from the latest release. 😄
Please take a look, maybe you can find a quick solution? Can you reproduce it at all? 🤔
Here's the screenshot of my output:

Same here

Thanks for confirming the issue @Lurrobert ! I just checked again the PR that was merged before v1.4 (#7). It's mostly refactoring around the env var's syntax. But I found this change suspicious, it's might be the cause of the issue: https://github.com/convictional/trigger-workflow-and-wait/pull/7/files#diff-6f9d41d046756f0ddc2fcee0626bdb50100d12b88f293734eff742818e03efa2L88 . Lines 88-89 were deleted, and that's why the waiting logic has disappeared I guess...

Is there any update on this? I am experiencing the same thing.

I see that my PR #17 got merged 8 days ago but the new version is not released yet. I guess that's the problem. As an option, you can use the code from the master branch, it should work I believe.
uses: convictional/trigger-workflow-and-wait@master

Do you guys plan to release a new version by the way?

Hi, I am not getting any id where I could see that curl message "curl: (92) HTTP/2 stream 1 was not closed cleanly before end of the underlying stream",
Can someone Please say if I am missing something?

I have this problem too. Can you fix it, please?

Revert to 1.3.0 resolved the issue.


Fix taint analysis for iterable block resolution

Purpose
When performing block resolution for iterable operations, taint analyzer will try to fetch the symbol of the  "iterable operation invocation" to be stored as the blocking information used for debugging purposes. In iterable operations, this information (symbol) is not available leading to a NPE. The data gathered was simplified for iterable operations with this PR.
Additional test cases were added to reflect the condition.
Additionally, this PR will improve analysis of lambda functions written within iterable operations by analyzing the lambda function regardless of tainted status of the expression (collection). This is done to detect taint-errors within the lambda body.
Example: Calling a function that returns tainted data and passing that data to a security sensitive parameter, withing the lambda body).
Unit tests are included for the improvement as well.
Resolves #9379

@anupama-pathirage I have made the changes relevant to the review comments.


Fixed git ahead/behind lib functionality

The git_commits_ahead and git_commits_behind functions break when a user enters a repository without an upstream due to lines 80 and 90, both of which are like:
local commits="$(git rev-list --count @{upstream}..HEAD)"

My fix just redirects stderr and then otherwise assume that the output is correct.

@robbyrussell do you think you could take a look at this?  Sorry to bug you but I'm not sure who else to tag.
Also, if you need some help going through old PR's and issues, I'd like to lend a hand.

I have the same Issue and made the same fix locally.
if used in themes this creates superfluous error outputs.
+1

Merged #6658 instead. Thanks for the PR though!


build: update eslint dev dependencies

PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

:tada: This PR is included in version 2.13.12 :tada:
The release is available on:

GitHub release
v2.13.12

Your semantic-release bot :package::rocket:


React.createElement: type is invalid

I kept trying the example, but all i get is the below error, can anybody help?
Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in.
Check the render method of AwakeInDevApp.
in AwakeInDevApp (at registerRootComponent.js:21)
in ExponentRootComponent (at renderApplication.js:35)
in RCTView (at View.js:128)
in View (at AppContainer.js:93)
in RCTView (at View.js:128)
in View (at AppContainer.js:92)
in AppContainer (at renderApplication.js:34)

it doesn't look like an error from this library, but somewhere in your own code, without seeing any code.

@mastermoo Thank you for your comment.
I basically put the code form this file:
https://github.com/mastermoo/react-native-action-button/blob/master/example/Basic/index.android.js
into my App.js (created by the react-native new project CLI).
All dependencies are installed.
I dont have any other code other than that file.
Any ideas?
Thank you.

closing this issue for inactivity.

@mastermoo  @alexbudin
just replace
import  {Icon} from 'react-native-vector-icons/Ionicons'
with
import  Icon from 'react-native-vector-icons/Ionicons'
could fix this problem


Vimeo 360 Stereo Is distorted and viewing incorrectly-

The 360 stereo video for the vimeo does not load correctly. See image below. it is distorted and stretched from a point. I do not  know if this is a problem with code or linking. Please help as I may need to implement this to my university final project as my original files refuse to load.

I also want to add that this is without me editing any of the code myself. It is simply from connecting my vimeo token env variable and adding in the video id.


✨ [Feature request]: Connection between IDEA and PLAY

Is your feature request related to a problem? Please describe.
Ideas are a great place to share prospects for play however today we cannot identify if play has been created/improvised from an existing idea.
The concept of this issue is to create a connection between an idea and play visually. It must be 1 to * relationship
Describe the solution you'd like
Need UI proposal
Describe alternatives you've considered
NA
Additional context
NA

Hey @koustov
How can i do it ?


fix(compiler-sfc): Keep the url logic of src and srcset mostly consistent

fix #4819

I think #4835 handles the case of mixed URLs better so I based 41d255ba off of that.


Save and restore the window dockwidget layout properly

Currently, we do not always manage to restore the saved window geometry properly

This will probably be fixed when Rusty finishes #2217 as we're deprecating dock widgets

Dockwidgets are no longer a first class feature and since this issue was created we moved to the Pane system, save and restore has been improved.


[KOGITO-4063] - Update nightly and PR check image with operator-sdk 1.2

Signed-off-by: Tarun Khandelwal<EMAIL_ADDRESS>Thank you for submitting this pull request
JIRA:  https://issues.redhat.com/browse/KOGITO-4063
Tested with test-image
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)

referenced pull request 1
referenced pull request 2
referenced pull request 2
etc.

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

Should be merged after https://github.com/kiegroup/kogito-cloud-operator/pull/695/

@Kaitou786 will this PR fix the Operator PR checks?

The PR checks should already be okay this for nightly and release :)

Tools can be configured later, but creating this directory structure so will be easier when configuring tools and adding 1.2.0 in the PATH so without any config 1.2.0 is available

Tools can be configured later, but creating this directory structure so will be easier when configuring tools and adding 1.2.0 in the PATH so without any config 1.2.0 is available


Fix shift left function was incorrect (#452)

Describe Request
The shift left function was incorrect
Fixed #452
Change Type
Fix function

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

Project coverage is 72.30%. Comparing base (496c3e4) to head (ff1c25a).
Report is 13 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #459      +/-   ##
==========================================
+ Coverage   65.58%   72.30%   +6.72%
==========================================
  Files          94      102       +8
  Lines        1537     1661     +124
  Branches      181      251      +70
==========================================
+ Hits         1008     1201     +193
+ Misses        517      448      -69
  Partials       12       12

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


make checkForgiveness a method on the edge

I changed this pull request to draft status.
This initial idea was to make forgiveness a method on the Edge in model/parts/types.
This is currently on hold, for more urgent development.


chore(Python): added binary search tree

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Algorithm: Binary Search Tree
Language: Python

I would like to contribute on this please assign it to me

I would like to contribute to this please assign it to me

Hi @Dhee2211,
This pull request is checking @Arsenic-ATG, and for contribute this repo you could add an algorithm and open a PR

Also, looks like, the program should be in a separate directory ( DSA/algorithms/Python/Tree/BinarySearchTree.py )

Hi @hashfx,
Any update?

Created a new PR with updated directory : https://github.com/MakeContributions/DSA/pull/445

Hi @hashfx,
Any updates?

Sorry for the delay, I was busy in some previous commitments. Would be resolving this PR ASAP!

Hi @hashfx,
Could you solve the conflict problem?

@hashfx, looks like you fork is a bit behind the main repo ( now There exist a "Trees" section under python for Tree DS based programs )
It is recommend for you to update your fork so that it is in sync with the main repo ( resolving any merge conflicts you encounter in your way )

I had re-forked MakeContributions/DSA. Should I again pull request?

I had re-forked MakeContributions/DSA. Should I again pull request?

Hi @hashfx,
You should make a marge from our main branch to your main branch

Hi @hashfx,
Please fix the conflict

Hi @hashfx,
Please fix the conflict

The PR is already merged through https://github.com/MakeContributions/DSA/pull/494


fixFix multiple case tables with the same name causing case failure

Fix multiple case tables with the same name causing case failure

run buildall


[Test] Change test_shift_dim to use pytest

Stack from ghstack (oldest at bottom):

#69
-> #68
#67

Codecov Report

:exclamation: No coverage uploaded for pull request base (gh/langong347/2/base@765c687). Click here to learn what that means.
The diff coverage is n/a.

@@                   Coverage Diff                   @@
##             gh/langong347/2/base      #68   +/-   ##
=======================================================
  Coverage                        ?   88.89%
=======================================================
  Files                           ?       30
  Lines                           ?     1504
  Branches                        ?        0
=======================================================
  Hits                            ?     1337
  Misses                          ?      167
  Partials                        ?        0

Continue to review full report at Codecov.

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

@langong347 has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

@langong347 has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


juniper_codegen: Drop regex & lazy_static dependencies

https://www.reddit.com/r/rust/comments/cz7u0j/psa_regex_13_permits_disabling_unicodeperformance/
The regex dependency is used in a single place, and it only validates ascii characters:
https://github.com/graphql-rust/juniper/blob/a3caf126b03533ea9b75b64056152500d38ce148/juniper_codegen/src/util.rs#L283
As such, we can drop the unicode support for faster compile times.

Hey, thanks.
It would actually be really trivial to do the validation with a simple helper method.
Then we could completely drop the dependency.

@archseer you feel like writing up the validation as a simple helper function and remove regex?

Sure! I'll see if I can come up with something simple tomorrow.

Codecov Report

Merging #424 into master will decrease coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #424      +/-   ##
==========================================
- Coverage   85.77%   85.67%   -0.11%
==========================================
  Files         110      110
  Lines       15787    15845      +58
==========================================
+ Hits        13542    13575      +33
- Misses       2245     2270      +25

Impacted Files
Coverage Δ

juniper_codegen/src/util.rs
31.72% <100%> (+0.2%)
:arrow_up:

juniper/src/types/scalars.rs
85.8% <0%> (-2.18%)
:arrow_down:

juniper/src/types/name.rs
78.26% <0%> (-1.74%)
:arrow_down:

juniper/src/types/base.rs
89.88% <0%> (-0.54%)
:arrow_down:

juniper_hyper/src/lib.rs
69.73% <0%> (-0.31%)
:arrow_down:

juniper/src/parser/tests/lexer.rs
93.34% <0%> (-0.22%)
:arrow_down:

juniper/src/validation/input_value.rs
84.57% <0%> (-0.2%)
:arrow_down:

juniper_rocket/src/lib.rs
89.87% <0%> (-0.05%)
:arrow_down:

juniper_codegen/src/derive_input_object.rs
0% <0%> (ø)
:arrow_up:

... and 20 more

Continue to review full report at Codecov.

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


Comment unused function

Codecov Report

Merging #70 into dev will decrease coverage by 0.40%.
The diff coverage is 14.28%.

@@             Coverage Diff              @@
##                dev      #70      +/-   ##
============================================
- Coverage     35.02%   34.62%   -0.41%
+ Complexity      272      270       -2
============================================
  Files            48       48
  Lines          3323     3313      -10
  Branches        272      270       -2
============================================
- Hits           1164     1147      -17
- Misses         2068     2075       +7
  Partials         91       91

Impacted Files
Coverage Δ
Complexity Δ

...nk/wecross/stub/bcos/contract/FunctionUtility.java
73.46% <0.00%> (-4.80%)
16.00 <0.00> (ø)

.../java/com/webank/wecross/stub/bcos/BCOSDriver.java
21.56% <25.00%> (-2.06%)
31.00 <0.00> (-2.00)

Continue to review full report at Codecov.

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


Improve aesthetic appearance of Error Manager Main Window

Improve aesthetic appearance of Error Manager Main Window.

The "Mark As Read" and "Mark All Errors As Read" buttons should use the system-style
The buttons should have enable-disable behaviour implemented.

"Mark As Read" should be enabled only when an unread error is selected
"Mark All Errors As Read" should be enabled only when there are one or more unread errors (regardless of which error is selected)

The MCL column header text should be centred
The MCL column header background should be a pale blue (not light grey like now)

Fix small bug: The "Mark Selected Error As Read" button should become DGO after it is pressed. Possible implementation: Create a new case named "Refresh MSEARB Enabled-Disabled Status". This case can be called from multiple locations.


Add numValidators to Native Staking confirmation view

Closes #1867
Changes

Adds numValidators field to the Native Staking transaction confirmation view.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

1 of 3 (33.33%)  changed or added relevant lines in 2 files are covered.
34 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.004%) to 46.709%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/transactions/entities/staking/native-staking-confirmation-view.entity.ts
1
2
50.0%

src/routes/transactions/transactions-view.service.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/routes/transactions/transactions-view.service.ts
34
15.57%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.004%

Covered Lines:
4763

Relevant Lines:
8250

💛  - Coveralls


Fix docs on audio feature installation

Related to #4000.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Feature request : get only metadata, not the blob itself

Hey guys,
I'm just starting to use GCP and GCS with the java sdk.
I would like to check metadata of a object, without downloading all the object.
It seems to be possible with the API, with the query param alt=json.
Maybe I miss something but i didn't find this possibility with the SDK.
It would be great to have this option available within the SDK.

Blob Storage.get(Blob blobId)  returns the Blob instance, which contains just information about the blob, not the content of the blob.

Great thank you !
I didn't realize the Blob object encapsulate the API calls to read the content. My bad.


Make scroll behaviour more similar to vim

Closes https://github.com/ambientsound/pms/issues/94
Behaviour is not identical to vim, but is much closer.
Vim has weird edge cases. Examples with scrolloff=0, a buffer with many lines, and a window 10 lines tall:

Cursor at line 1. Lines 1 to 10 are visible. ^F. Now lines 9 to 18 are visible and the cursor is at 9. ^B. Now lines 1 to 10 are visible again, but the cursor has moved down one line to 10.

Cursor at line 1. Lines 1 to 10 are visible. ^F. Now lines 9 to 18 are visible and the cursor is at 9. ^E. Now lines 10 to 19 are visible and the cursor is at 10. ^B. Now lines 1 to 10 are visible.

Cursor at line 1. Lines 1 to 10 are visible. ^F. Now lines 9 to 18 are visible and the cursor is at 9. ^E^E. Now lines 11 to 20 are visible and the cursor is at 11. ^B. Now lines 3 to 12 are visible.

Cursor at line 1. ^E. Lines 2 to 10 are visible and the cursor is at 2. ^B. Lines 1 to 10 are visible but cursor is at 3.

Cursor at line 1. ^E^E. Lines 3 to 11 are visible and the cursor is at 3. ^B. Lines 1 to 10 are visible but cursor is at 4.

I haven't tried to recreate all of this, since I'm not convinced it's actually intentional behaviour.
The behaviour I've ended up with, instead, is this:

Page up and down commands scroll the whole viewport but leave the cursor alone as much as possible.

The viewport is scrolled by a full page minus two rows in most cases. If the viewport is 4 lines high, it scrolls 3 lines. If the viewport is 3 or fewer lines high, it scrolls a full page. This is as vim.

Since if the window is five or more rows there are two lines of context, and since we leave the cursor on the same song if possible, ^F^F^B ends up with the cursor one row from the bottom, and ^B^B^F ends up with the cursor one row from the top. This is not like vim but I think it's probably the intended behaviour (at least it makes sense to me).

The half page commands move both the viewport and the cursor by half a page. These are independent, so if the viewport can only scroll two more rows, the cursor will still move further, and vice versa. This works just like vim in all the comparisons I've made, other than near the very bottom (since vim allows scrolling to continue and shows ~ rows).

I've moved the page up/down and half page up/down commands to the viewport namespace, since I think they make more sense here.

Codecov Report

Merging #96 into master will decrease coverage by 0.66%.
The diff coverage is 27.65%.

@@            Coverage Diff             @@
##           master      #96      +/-   ##
==========================================
- Coverage   54.01%   53.35%   -0.67%
==========================================
  Files          51       51
  Lines        1779     1803      +24
==========================================
+ Hits          961      962       +1
- Misses        796      818      +22
- Partials       22       23       +1

Impacted Files
Coverage Δ

commands/cursor.go
62.5% <ø> (+1.38%)
:arrow_up:

options/defaults.go
0% <ø> (ø)
:arrow_up:

commands/viewport.go
48.68% <27.65%> (-31.32%)
:arrow_down:

Continue to review full report at Codecov.

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

Will do, and then will rebase the other branch.

Thanks. There is also a bug in center mode: when using page up near the top, or page down near the bottom, the cursor is not moved to the start or end of the list.

That's not a bug in my opinion! That's how it works in vim.

My Vim only "blocks" on page up. It scrolls down to the very bottom, marking the last line and leaving only that line visible. So this behavior is dubious. I see your point on separating viewport and cursor, but in my opinion it will be more user-friendly to have the cursor move to the edge at the same time.

That behaviour at the bottom is because vim lets you keep scrolling at the bottom, showing you ~ rows. PMS doesn't do that (though it could...)
I don't agree regarding page up moving the cursor to the top. Page up moves the viewport a page up, and it's already at the top, so it's right that it shouldn't do anything. There are plenty of other ways to get the cursor to the top: gg, H, ^U. I'm back to banging the vim drum of course, but I think staying close to what vim does is best here.
Would you be on my page if we implemented the ~ rows at the bottom, resulting in ^F getting you eventually to the very last song? Vim also rings the bell if you try to ^B when already at the top. We could do that too?

With this change, PgUp will move the viewport instead of the cursor. Semantically, it is correct not to move the cursor to the top. That said, having to switch from PgUp to gg requires moving the fingers (context switching), so the correctness might come at the expense of user-friendlyness.
I don't think implementing ~ lines is useful, as the primitive in PMS is the song and not the character.
Given as Vim-like is a key selling point for users, it's important to make PMS look and feel right for Vim users. Thus, I'm going to accept your pull request. If the cursor functionality becomes important enough, it can be re-implemented as cursor [...] commands.

That said, having to switch from PgUp to gg requires moving the fingers (context switching)

Not if using ^F and ^B, which I would have thought most vim users would rather than pgup/pgdn keys. If using pgup/pgdn, there are also the home and end keys anyway.

I don't think implementing ~ lines is useful, as the primitive in PMS is the song and not the character.

I'm not sure I fully understand your line of thinking here. Could you elaborate?

If the cursor functionality becomes important enough, it can be re-implemented as cursor [...] commands.

Yes, no reason we couldn't add :cursor pageup et al back in, with their old behaviour, but I just question how useful they'd be. The weirdness of only scrolling a single row in some cases puts me off of it.
Thanks for merging!

I don't think implementing ~ lines is useful, as the primitive in PMS is the song and not the character.

I'm not sure I fully understand your line of thinking here. Could you elaborate?

What I mean is that ~ markers are useful in Vim because one can scroll further down than the file, enter input mode, and start adding text. This mode of playlist manipulation wouldn't really be practical in PMS.

Thanks for merging!

Thanks for the pull request!

Oh, I see now. So you mean scroll down so lots of ~ are in view and then add many lines of text at once without anything scrolling.


⚠ sandbox-api.piste.gouv.fr healthcheck has degraded performance

In 4645545, sandbox-api.piste.gouv.fr healthcheck (https://sandbox-api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 3076 ms

Resolved: sandbox-api.piste.gouv.fr healthcheck performance has improved in 26e634a.


Update chainlist

Handle on issue : https://github.com/Koniverse/SubWallet-ChainList/issues/275#issuecomment-2216629962

Version test : http://<IP_ADDRESS>:8900/s/LP4b9knKMHfsWJo

[ ] Update link navigate explorer for Bool testnet network
https://beta-testnet.boolscan.com/account/0xbaF8DE21a6f224abfCe6C4feb327e672edBEFCA6 ( Link navigate from wallet)
https://beta-testnet.boolscan.com/address/0xbaF8DE21a6f224abfCe6C4feb327e672edBEFCA6 ( Link on explorer)


Update Godot.gitignore for Godot 4+

Reasons for making this change:
Godot 4 Beta was recently released. It adds a .godot folder that should be ignored in git
I am an end user that used this template but it was missing the .godot folder
Links to documentation supporting these rule changes:
.gitignore file from a official godot 4 demo project:
https://github.com/godotengine/godot-demo-projects/blob/master/.gitignore

I didn't check for duplicates before creating this


Cancelling an upload returns BAD REQUEST

Using the lovely notebooks:

upload_local_datafile(datafile_path, new_collection_id, identifier)
import time
time.sleep(60)
delete_dataset(new_collection_id, identifier)

BAD request is returned even when the deletion is delayed for +2 minutes.
The mitigation is to cancel the upload in the UX. This is not a primary scenario.

This was a bug in the notebook code. Re-tested with a copy of the notebooks from @danieljhegeman 's branch in progress. The problem has been corrected.


Generic detection is preferred over detailed rich presence for a single process

I struggled to figure a way to write the title, sorry about that. This may be related to #3 but unconfirmed.
In a use case where a game has both a Rich Presence using Game SDK and an entry in detectable.json, it seems the generic detectable.json entry is chosen, showing the game name but showing no details. The Game SDK rich presence seems to be dropped and is treated as though it's not detected at all.
This is handled differently than arRPC, which just chooses to show both implimentations at once. Discord hides the detectable entry when Game SDK rich presence is present, and it seems rsRPC is doing the opposite.
I have replicated this specifically with the game ULTRAKILL. I have not tested any specific circumstances, only with the game being the only active supported process.

It seems after I hid detection for ULTRAKILL, turning it back on doesn't restore it anymore (using Dorion's build), so that seems to also be a mild issue.

Switching to the latest build from issue #7 restored game detection. This issue is still present.

[2024-12-20 21:16:12] [Client Connector] Already sent payload for activity: ULTRAKILL
Might be related?

I believe this might be related to #3, I am willing to bet you have other stuff doing rich presence which is causing the ULTRAKILL stuff to not show up (like described in that other issue). Since process detection is running separately to IPC detection, it probably is just the only thing that works (therefore giving the illusion that process detection has something to do with it, which I don't think it  does).
I figured this out because I left foobar2k open with rich presence which worked fine, and when opening ULTRAKILL it would handshake but not make it any further. Once I closed foobar2k and restarted rsRPC and ULTRAKILL, the ULTRAKILL presence worked.
I'm gonna call this a dupe of #3 but feel free to add any details there since I still don't know the exact cause :)


[Vertex AI] Update DocC comments for GenerationConfig

WIP - Updating the documentation for GenerationConfig parameters.

[x] temperature
[ ] topP
[ ] topK
[ ] candidateCount
[ ] maxOutputTokens
[ ] stopSequences
[ ] responseMIMEType
[ ] responseSchema

#no-changelog

These have been updated in https://github.com/firebase/firebase-ios-sdk/pull/13904.


Added Mobile System Design blog and Youtube links

Hi!
The www.mobilesystemdesign.com website now has a blog, I also included links to its youtube channel.
I validated the JSON, too.
Thanks for reviewing.

Thanks @daveverwer !


luci-app-statistics: cleanups of bad spacing

fixes the output of /etc/init.d/luci_statistics help

@hnyman I just noticed this glitch in the original changes, I botched the help spacing at some point during one of the edits


fhir-bulkimportexport-webapp is not in the fhir-install dependency tree

fhir-bulkimportexport-webapp is not in the fhir-install dependency tree.
in a multithreaded build, the build may JUMP (rather than skip) the build of the it before the fhir-install and subsequently fail.
This also can mean an OLDER version may be PICKED and embedded in the installation.
LOG
[INFO] fhir-bulkimportexport-webapp ....................... SKIPPED
[INFO] fhir-cli ........................................... SUCCESS [  6.354 s]
[INFO] fhir-notification-websocket ........................ SUCCESS [  0.336 s]
[INFO] FHIR Server REST API Implementation ................ SUCCESS [  6.279 s]
[INFO] FHIR Server REST API WebApp ........................ SUCCESS [  1.030 s]
[INFO] fhir-server-test ................................... SUCCESS [  2.799 s]
[INFO] fhir-swagger-generator ............................. SUCCESS [  1.262 s]
[INFO] fhir-openapi ....................................... SUCCESS [  7.838 s]
[INFO] fhir-install ....................................... FAILURE [  7.283 s]
[INFO] fhir-coverage-reports .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  05:35 min (Wall Clock)
[INFO] Finished at: 2019-10-08T12:22:40Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (fhir-server-dist) on project fhir-install: Failed to create assembly: Error adding file to archive: /home/runner/work/FHIR/FHIR/fhir-install/../fhir-bulkimportexport-webapp/target/fhir-bulkimportexport.war -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :fhir-install
##[error]Process completed with exit code 1.

PR https://github.com/IBM/FHIR/pull/215


Small change to encoding to fix is_owner to work

I assume the aioredis client probably changed it's return type.

Sorry I missed this, if this is going to work we would need to check the type and handle it accordingly since people could have the previous version pinned.


Fix Tinkerbell actions docs

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

/cherry-pick release-0.16
/cherry-pick release-0.17

/cherry-pick release-0.17

/approve


Exit the game, and return to the dashboard

https://tauri.studio/en/docs/api/rust/tauri/plugin/fn.register
https://tauri.studio/en/docs/api/rust/tauri/plugin/trait.Plugin
These may help figure out something.

https://tauri.studio/en/
Multi window may roll out by the end of the third quarter, we can just launch games in a new window.


TEST: remove integration spark test with large dataset

Description
Temporarily remove Spark integration test
Motivation and Context
Spark integration test is a replicate of Spark smoke test. Use of large data sets lead to issues in the CI/CD pipeline.
Temporarily remove the tests until there are good fix.
Releated Issues
#369
Checklist:

[x] My code follows the code style of this project, as detailed in our contribution guidelines.
[x] I have added tests.
[x] I have updated the documentation accordingly.

It looks it is taking longer than 40min, so it time out:
2018-12-13T15:03:18.1314392Z
2018-12-13T15:42:17.9239285Z tests/integration/test_notebooks_pyspark.py FF
2018-12-13T15:42:17.9856461Z ##[error]The task has timed out.

probably some of the new changes make the notebook to take longer

@anargyri good point - also given characteristics of 100k and 1mil may not be homogeneous based on our observations in the evaluation results.

I think the change of TOL to 0.5 is extreme, as in PR 371. I would make sure everything is deterministic (seed, split etc.) for the tests. If you give ALS the same seed it should do the same thing every time. There is some variation due to machine precision etc. but this should not be 50%.

@anargyri will hold this PR until update of the ALS seed.

Resolved in #376


dashmate setup local is failing with an invalid IP address error

dashmate setup local is failing with an invalid IP address error:
dashmate setup local
✔ Set configuration preset
✔ Set the number of nodes
✔ Enable debug logs
✔ Set the core miner interval
✖ (HTTP code 400) unexpected - invalid IP address in add-host: "host-gateway"
◼ Configure Core nodes
◼ Configure Tenderdash nodes
◼ Initialize Platform
◼ Set default config group

Expected Behavior
Setup local succeeds
Current Behavior
Set local fails
Possible Solution

Steps to Reproduce (for bugs)
git clone -b v0.20.0-dev.3 https://github.com/dashevo/dashmate.git && cd dashmate
npm i && npm link
dashmate setup local

Context
Unable to work on local build
Your Environment

Version used: v0.20.0-dev.3
Environment name and version (e.g. Chrome 39, node.js 5.4): node.js v14.4.0
Operating System and version (desktop, server, or mobile): Ubuntu [studio] 20.04
Link to your project: N/A

@cloudwheels can you confirm if this issue is still current with v.20 on master branch or close it if it is fixed?

Will check asap...
On Tue, 7 Sep 2021, 19:14 dashameter, @.***> wrote:

@cloudwheels https://github.com/cloudwheels can you confirm if this
issue is still current with v.20 on master branch or close it if it is
fixed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dashevo/dashmate/issues/374#issuecomment-914518908,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKTEKOCBIFTA5IQCZEHOJKLUAZJA3ANCNFSM46JXAOPQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

FWIW, I'm not having this issue on 0.21-dev

Cannot reproduce on v0.20 or v0.21-dev, closing this issue.


Timers for Response of a Session

Can Titanium add Timers data into the SessionEventArgs?
Example of how to pull that information out for a test case.
`Proxy.AfterSessionComplete += delegate (SessionEventArgs targetSession)
{
                var totalRequestTime = targetSession.Timers.ClientDoneResponse -
                                       targetSession.Timers.ProxyBeginRequest;

                var clientRenderTime = targetSession.Timers.ClientDoneResponse -
                                       targetSession.Timers.ServerDoneResponse;

                var serverProcess = targetSession.Timers.ServerBeginResponse -
                                    targetSession.Timers.ServerGotRequest;

                var passThruNetwork = targetSession.Timers.ServerGotRequest -
                                      targetSession.Timers.ClientDoneRequest -
                                      TimeSpan.FromMilliseconds(
                                          targetSession.Timers.DNSTime + targetSession.Timers.TCPConnectTime);

                Log.Info(
                    "Proxy: Requested resource from URL {0} Response Code: {1} Total Time: {2} Server Milliseconds: {3} Network Milliseconds: {4}",
                    targetSession.fullUrl,
                    targetSession.responseCode,
                    totalRequestTime.TotalMilliseconds,
                    Math.Abs(serverProcess.TotalMilliseconds),
                    Math.Abs(passThruNetwork.TotalMilliseconds));
            };`

We already have some timer details available inside Session.TimeLine dictionary. We can improve this in future.
https://justcoding121.github.io/Titanium-Web-Proxy/docs/api/Titanium.Web.Proxy.EventArguments.SessionEventArgsBase.html#Titanium_Web_Proxy_EventArguments_SessionEventArgsBase_TimeLine

Do you happen to have any sample code not on Git, that can show how to get to Timeline?
It says on the docs here it is in the SessionEventArgBase, but doesn't show up the SessionEventArgs or WebSession ?     I think there might just be a bug perhaps in getting access to that data.

I was able to access this from the latest master repository example project. Are you using the latest beta build.

@darrincherry
You should be able to access it in AfterResponse. The available events are currently
args.TimeLine["Session Created"];
args.TimeLine["Request Received"];
args.TimeLine["Server Connection Created"];
args.TimeLine["Response Received"];
args.TimeLine["Response Sent"];

TimeLine currently contains  DateTime,Now values, but in some frameworks (especially older ones) it is much slower than UtcNow. (Google it, for example: https://blogs.msdn.microsoft.com/kirillosenkov/2012/01/10/datetime-utcnow-is-generally-preferable-to-datetime-now/ )
In modern frameworks it is faster, but still slower than UtcNow.
I'll change them to UtcNow to make the performace better and I think it is a better idea to store UTC values.


create db schema for games

table: games
columns: id, storyline (body), villians, side characters, map

table: games
columns: id, storyline (body), villians, side characters, map


auto-port debug paypal.

Description
Changes proposed in this pull request.
Test plan
Outline the test plan used to test this change before merging it.

Fixes #.

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "4b6600cbe950dd596dfcfe6bd499b5339ed5b515",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "971b5d606dcac7339dcb2294e038ca59300935dd",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "4b6600cbe950dd596dfcfe6bd499b5339ed5b515",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "971b5d606dcac7339dcb2294e038ca59300935dd",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "4b6600cbe950dd596dfcfe6bd499b5339ed5b515",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "e8fd1120088dff0831458f85ea82b9e0f6914250",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "4b6600cbe950dd596dfcfe6bd499b5339ed5b515",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "e8fd1120088dff0831458f85ea82b9e0f6914250",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "9a4ef806fb75f61ee855d4df7d95f836f3d2c065",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "e8fd1120088dff0831458f85ea82b9e0f6914250",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "9a4ef806fb75f61ee855d4df7d95f836f3d2c065",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "e8fd1120088dff0831458f85ea82b9e0f6914250",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "cb9836909af9678c9d2c401868ae89e9afe1a80a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "e8fd1120088dff0831458f85ea82b9e0f6914250",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "paypal-debug",
    "component": "trireme-lib",
    "pr-id": "1049",
    "commit-sha": "cb9836909af9678c9d2c401868ae89e9afe1a80a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "paypal-debug",
    "component": "enforcerd",
    "pr-id": "2190",
    "commit-sha": "e8fd1120088dff0831458f85ea82b9e0f6914250",
    "pipeline": "release-3.14.0"
  }
]


Connection Issue with Merlin

We recently got a Merlin installed on our system (JEOL 2200). I have installed Instamatic v1.9.0 on both the Merlin PC and microscope PC. The Merlin PC does not have the TEMCOM libraries, and is disconnected from the microscope PC by default.
When running Instamatic on the Merlin PC:
If I choose JEOL as the microscope in the settings.yaml file (i.e., microscope: jeol, camera: merlin, calibration: simulate) I get:
Config directory: C:\Users\Merlin\AppData\Roaming\instamatic\config
Microscope: jeol (server)
Starting TEM server (localhost:8088 on pid=4600)
Exception in thread None:
Traceback (most recent call last):
  File "C:\Users\Merlin\AppData\Local\Programs\Python\Python38\lib\threading.py", line 932, in _bootstrap_inner
    self.run()
  File "C:\Users\Merlin\AppData\Local\Programs\Python\Python38\lib\site-packages\instamatic-1.9.0-py3.8.egg\instamatic\server\tem_server.py", line 46, in run
    self.tem = Microscope(name=self._name, use_server=False)
  File "C:\Users\Merlin\AppData\Local\Programs\Python\Python38\lib\site-packages\instamatic-1.9.0-py3.8.egg\instamatic\TEMController\microscope.py", line 55, in Microscope
    tem = cls(name=name)
  File "C:\Users\Merlin\AppData\Local\Programs\Python\Python38\lib\site-packages\instamatic-1.9.0-py3.8.egg\instamatic\TEMController\jeol_microscope.py", line 61, in __init__
    temext = comtypes.client.GetModule(('{CE70FCE4-26D9-4BAB-9626-EC88DB7F6A0A}', 3, 0))
  File "C:\Users\Merlin\AppData\Local\Programs\Python\Python38\lib\site-packages\comtypes\client\_generate.py", line 139, in GetModule
    tlib = _load_tlib(tlib)
  File "C:\Users\Merlin\AppData\Local\Programs\Python\Python38\lib\site-packages\comtypes\client\_generate.py", line 178, in _load_tlib
    return LoadRegTypeLib(GUID(libid), *version)
  File "C:\Users\Merlin\AppData\Local\Programs\Python\Python38\lib\site-packages\comtypes\typeinfo.py", line 478, in LoadRegTypeLib
    _oleaut32.LoadRegTypeLib(byref(GUID(guid)), wMajorVerNum, wMinorVerNum, lcid, byref(tlib))
  File "_ctypes/callproc.c", line 935, in GetResult
OSError: [WinError -2147319779] Library not registered

I figured this is because I am missing the TEMCOM library on the Merlin PC, so tried to just proceed with a simulated microscope and the Merlin camera (i.e., microscope: simulate,  camera: merlin,  calibration: simulate, and I get the following:
C:\Users\JEOL>instamatic
Config directory: C:\Users\JEOL\AppData\Roaming\instamatic\config
Microscope: jeol (server)
Starting TEM server (localhost:8088 on pid=3912)
Connected to TEM server (localhost:8088)
Camera    : merlin (stream)
Traceback (most recent call last):
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\site-packages\i
nstamatic\camera\camera_merlin.py", line 179, in establishConnection
    s_cmd.connect((self.host, self.commandport))
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\runpy.py", line
 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\runpy.py", line
 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\JEOL\AppData\Local\Programs\Python\Python38\Scripts\instamatic.
exe\__main__.py", line 7, in <module>
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\site-packages\i
nstamatic\main.py", line 138, in main
    ctrl = TEMController.initialize(stream=True)
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\site-packages\i
nstamatic\TEMController\TEMController.py", line 60, in initialize
    cam = Camera(cam_name, as_stream=stream, use_server=use_cam_server)
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\site-packages\i
nstamatic\camera\camera.py", line 67, in Camera
    cam = cam_cls(name=name)
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\site-packages\i
nstamatic\camera\camera_merlin.py", line 54, in __init__
    self.establishConnection()
  File "c:\users\jeol\appdata\local\programs\python\python38\lib\site-packages\i
nstamatic\camera\camera_merlin.py", line 194, in establishConnection
    raise RuntimeError(
RuntimeError: Could not establish command connection to merlin, (Merlin command
port already connected).
SUCCESS: The process with PID 2272 (child process of PID 3912) has been terminat
ed.
SUCCESS: The process with PID 3912 (child process of PID 3252) has been terminat
ed.

I couldn't quite understand what was happening with the port. It seems like there is a conflicting process, but I could not identify what that was. The application to control the Merlin was not running.
In relation to the missing TEMCOM library, I have connected the PCs via an Ethernet cable, and have tried running two instances of Instamatic but still no luck. We would appreciate any information on how to establish communication between the JEOL PC and Merlin PC!

The application to control the Merlin was not running.

Ah, I think you have to start the Merlin software first.
The error here is a bit confusing, I guess it says this on all failed connection attempts. I will change it.

In relation to the missing TEMCOM library, I have connected the PCs via an Ethernet cable, and have tried running two instances of Instamatic but still no luck. We would appreciate any information on how to establish communication between the JEOL PC and Merlin PC!

I think you could try asking your JEOL engineer to set you up with TEMCOM on the Merlin PC.
If you have instamatic on the JEOL PC and run instamatic.temserver there, and put the IP of the JEOL PC under hostname on the settings.yaml of the Merlin PC. This way the two instances of instamatic should be able to communicate.
JEOL PC:
# settings.yaml
use_tem_server: True  # ignored
tem_server_host: <IP_ADDRESS>  # IP of JEOL PC
tem_server_port: 8088

Merlin PC:
# settings.yaml
use_tem_server: True
tem_server_host: <IP_ADDRESS>  # IP of JEOL PC
tem_server_port: 8088  # Must match PORT of JEOL PC

Thanks, @stefsmeets. I managed to establish communication between the JEOL PC and Merlin PC with the information provided above. Previously, I used the wrong IP address in the tem_server_host: line, but eventually found the right one.
I tested Instamatic with the Merlin software running and not running but still get the same error. The next time I test things, I will adjust the code to output the exact OSError to be more informative. Anyway, I checked the ports being used by the Merlin software when it is running, and they seem to match the ports in instamatic/config/camera/merlin.yaml, i.e. 6341 and 6342 ( and also 6343, which is not shown in this file). I am wondering if perhaps I need to change the IP address from <IP_ADDRESS> to <IP_ADDRESS>, since I am running Instamatic on the Merlin PC (and instamatic.temserver on the JEOL PC).

I got Instamatic working by changing the IP address in merlin.yaml from <IP_ADDRESS> to <IP_ADDRESS>. Will test tomorrow again to double check, and then close the thread!

Ah yes, that's a good point. I will change the default to <IP_ADDRESS> instead of the url I use for testing. I'm planning to write some documentation for how to setup the Merlin detector with instamatic soon.

Yes, I noticed that there is a new version! Works great so far!


feat: Add image channel layout support RGB and RGBA when loading imag…

Add parameter "channel_layout" to support convert uploaded images with specified layout.

LGTM and thanks for your contribution @wrongtest


adding a realdir with target to '/' creates a self-referential '' entry that makes the fs unusable

Describe the bug
My first baby steps with pyfakefs aren't going well... I am trying to populate a fake fs with custom entries under root (to test a system that expects certain files at absolute locations).
Instead of seeing the desired content, doing a simple os.walk() results in an infinite loop, seemingly because an extra, self-referential entry (the empty string '') is created under /.  If I look at the beginning of the iterator of os.walk(), I see a repeating alternation of '/' and '/tmp'.
How To Reproduce
cd $(mktemp -d)
mkdir -p data/root/foo/bar
touch data/root/foo/bar/file-{0,1,2,3}.txt
touch __init__.py

cat > conftest.py <<"EOF"
import pytest

@pytest.fixture
def myfs(fs):
    fs.add_real_directory('data/root', target_path='/')
    yield fs
EOF

cat > test_fake.py <<"EOF"
import os

def test_fake(myfs):
    print('\n\nwith fake fs')
    for _, e in zip(range(10), os.walk('/')):
        print(e)

def test_real():
    print('\n\nwith real fs')
    os.chdir('data/root')
    for _, e in zip(range(10), os.walk('.')):
        print(e)
EOF

pytest -s test_fake.py

The output of the above is:
================================================== test session starts ==================================================
platform linux -- Python 3.10.9, pytest-7.1.2, pluggy-1.0.0
rootdir: /tmp/tmp.xpzkMjworA
plugins: xdist-2.5.0, anyio-3.5.0, cov-3.0.0, pyfakefs-5.3.0, hypothesis-6.29.3, forked-1.3.0
collected 2 items

test_fake.py

with fake fs
('/', ['tmp', ''], [])
('/tmp', [], [])
('/', ['tmp', ''], [])
('/tmp', [], [])
('/', ['tmp', ''], [])
('/tmp', [], [])
('/', ['tmp', ''], [])
('/tmp', [], [])
('/', ['tmp', ''], [])
('/tmp', [], [])
.

with real fs
('.', ['foo'], [])
('./foo', ['bar'], [])
('./foo/bar', [], ['file-2.txt', 'file-3.txt', 'file-0.txt', 'file-1.txt'])
.

=================================================== 2 passed in 0.19s ===================================================

What I was expecting was to see the same output for test_fake as for test_real, but relocated under '/'.
Your environment
Linux-6.2.0-32-generic-x86_64-with-glibc2.35
Python 3.10.9 (main, Jan 11 2023, 15:21:40) [GCC 11.2.0]
pyfakefs 5.3.0
pytest 7.1.2

Probable cause
When I run the test in PyCharm's debugger, I noticed a strange entry under the root dir of myfs: the empty string ('', third line of the output below):
>>> str(myfs)
'/'(40777):
  'tmp'(40777):
  ''(40775):
  'foo'(40775):
    'bar'(40775):
      'file-2.txt'(100444)
      'file-3.txt'(100444)
      'file-0.txt'(100444)
      'file-1.txt'(100444)

Incidentally, if I try to print that in the unit test itself (rather than copying the view from the debugger above), I get:
self = <pyfakefs.fake_file.FakeDirectory object at 0x7fe0490633d0>

    def __str__(self) -> str:
        description = super(FakeDirectory, self).__str__() + ":\n"
>       for item in self.entries:
E       RuntimeError: dictionary changed size during iteration

In any case, it seems that this erroneous entry has been created during fs.add_real_directory. Inspecting it in the debugger, that entry refers to the filesystem itself. Specifically:
>>> myfs.root_dir.entries[''].filesystem is myfs
True

# or, in other words:
>>> id(myfs.root_dir.entries[''].filesystem) == id(myfs)
True

Workaround
The following produces the desired result.
cd $(mktemp -d)
mkdir -p data/root/foo/bar
touch data/root/foo/bar/file-{0,1,2,3}.txt
touch data/root/hello.txt
touch __init__.py

cat > conftest.py <<"EOF"
import os
import pytest

@pytest.fixture
def myfs(fs):
    fs.pause()
    content = [(e.name, e.path, os.path.isdir(e)) for e in os.scandir('data/root')]
    fs.resume()
    for name, path, isdir in content:
        if isdir:
            fs.add_real_directory(path, target_path=f'/{name}')
        else:
            fs.add_real_file(path, target_path=f'/{name}')
    yield fs
EOF

cat > test_fake.py <<"EOF"
import os

def test_fake(myfs):
    print('\n\nwith fake fs')
    for _, e in zip(range(10), os.walk('/')):
        print(e)

def test_real():
    print('\n\nwith real fs')
    os.chdir('data/root')
    for _, e in zip(range(10), os.walk('.')):
        print(e)
EOF

pytest -s test_fake.py

Output:
================================================== test session starts ==================================================
platform linux -- Python 3.10.9, pytest-7.1.2, pluggy-1.0.0
rootdir: /tmp/tmp.ykVCAbMQoK
plugins: xdist-2.5.0, anyio-3.5.0, cov-3.0.0, pyfakefs-5.3.0, hypothesis-6.29.3, forked-1.3.0
collected 2 items

test_fake.py

with fake fs
('/', ['tmp', 'foo'], ['hello.txt'])
('/tmp', [], [])
('/foo', ['bar'], [])
('/foo/bar', [], ['file-2.txt', 'file-3.txt', 'file-0.txt', 'file-1.txt'])
.

with real fs
('.', ['foo'], ['hello.txt'])
('./foo', ['bar'], [])
('./foo/bar', [], ['file-2.txt', 'file-3.txt', 'file-0.txt', 'file-1.txt'])
.

=================================================== 2 passed in 0.20s ===================================================

Thanks for the report and the investigation!
Mapping a real directory to root is something that I have never tested, so it is likely a bug somehow related to the special handling of the root path. I will probably have a closer look at the weekend.

So far I have not been able to reproduce your problem. I let the test run in the CI and got no errors on any system - maybe I'm doing something wrong. Here is the latest varaint of the test I have been using (modified it a bit to work on different systems):
import os
import shutil
import tempfile
from pathlib import Path

import pytest

@pytest.fixture(scope="session")
def real_dir():
    path = Path(tempfile.gettempdir()) / "data" / "root" / "foo" / "bar"
    os.makedirs(path, exist_ok=True)
    (path / "file.txt").touch(exist_ok=True)
    (path / "__init__.py").touch(exist_ok=True)
    yield path
    shutil.rmtree(path, ignore_errors=True)

@pytest.fixture
def myfs(real_dir, fs):
    fs.add_real_directory(real_dir, target_path=fs.root.path)
    yield fs

def test_fake(myfs):
    print("\n\nwith fake fs")
    for _, e in zip(range(10), os.walk(myfs.root.path)):
        print(e)

def test_real(real_dir):
    print("\n\nwith real fs")
    for _, e in zip(range(10), os.walk(real_dir)):
        print(e)

Can you please check the outcome of this test in your environment?

I am away from my desktop right now. But what I provided was a full reproducible example (including setting up of the data dir) using simple shell commands. Were you able to just execute the shell commands I provided? If so, what was the output? I'll try to use your code above when I get a chance. I assume this is with the same directory setup as I provided?

I was checking for a recursion error, but should have looked at the output which was indeed wrong. And yes, with your change I can also reproduce the recursion error, thanks!

No worries at all. I am grateful that you're willing to take a look. If I had time, I would dig in, but alas, I have zero time at the moment.

The problem is not mapping to the root dir as such, but mapping to a directory already existing in the fake directory - this is currently not supported (never come up before). This may take a bit...

There was actually a test that checked that mapping to an existing directory raises an exception - which it does, except for the root path (which was actually a bug).
Mapping to an existing directory (including root) would mean to potentially merge two directory trees, with some conflicts possible, e.g. a file already existing in the fake file system that would be overwritten, or a file existing where a directory would mapped. There may be more problems...
I'm not quite sure what the expected behavior in these cases should be - maybe you already have an idea.
I will put something together - though I guess this is not urgent, as a workaround exists, and I also have some time constraints, so it may take a few days.

I think the merge could be done in a few ways, a bit similar to some of the ways rsync can operate between a source and a destination.

Hard replace (equivalent of rsync -az --force --delete src/ dst/). It would mean that the whole target path, if existing, is removed first and replaced by the new content. In any case, the result is that the new path becomes an exact mirror of the source.
Merge when possible (e.g. both src and dst are dir, of src is file and dst doesn't exist), clobbering previous entries in cases where merge is not possible (e.g., src is file and dst is file or dir). This would be equivalent to rsync -az --force src/ dst/).
Merge only if the target doesn't exist and raise otherwise.

We would need to think about how to control this by a clear set of flags. But how does it sound in terms of the logic?

Sorry, I seem to have missed your comment and completely forgot about my PR (#903)...
The PR uses mostly the second approach. If a directory exists, the directories are merged to the extent that no files are overwritten. If a file would be overwritten (or a file exists where a directory would be created), an exception is raised (you can have a look at the PR, especially the tests). If this is ok for you, I would merge it.

@mrbean-bremen : that sounds perfect. We probably don't need the other cases. Thank you so much for doing this.

The PR uses a mix of the second and third approach. If a directory exists, the directories are merged to the extent that no files are overwritten. If a file would be overwritten (or a file exists where a directory would be created), an exception is raised (you can have a look at the PR, especially the tests which should show the behavior). If this is ok for you, I would merge it.

Good to hear! I'm waiting for another PR to be finished and probably will make a bug fix release afterwards (I wanted to do it anyway because of another fixed bug).


Update DepthAI API version

Updates Gen2 experiments with latest Gen2 API version (<IP_ADDRESS>)
Current issues:

https://github.com/luxonis/depthai-experiments/issues/162 -gen2-deeplabv3_depth experiment is not working with latest API version, sync mechanism is not updating depth frames even though they arrive. Potentially solvable by using #159 for sync
https://github.com/luxonis/depthai-experiments/issues/163 - gen2-gaze-estimation yields incorrect gaze vector
https://github.com/luxonis/depthai-experiments/issues/164 - gen2-people-tracker yields inconsistent results due to video FPS being too high for the nn to produce some valid data (but doesn't run at all with the version specified in the requirements so updated it too)
gen2-triangulation API version cannot be updated until this PR is merged - https://github.com/luxonis/depthai-python/pull/316

Thanks.  We should go ahead and push those that do work in a wave so that folks can use these and it's less likely for a customer to have the bad UX of one not working, when really the only thing preventing it is an old requirementx.txt.
CC: @Erol444

I agree with @Luxonis-Brandon, we can go ahead and merge the ones that are converted already :+1:

Sure @Luxonis-Brandon and @Erol444, I created separate issues for each of the mentioned experiments and will focus on them separately

I think it would be good to do so rather sooner than later. Maybe once we migrate all examples to Gen2 would be a good time to do so?

Thanks both.  And yes don't let removing the blobs block getting these examples out/merged/working for POE.  Do as separate effort after this is out there and we are not causing pain for our customers.


The bootstrap runtime should not be transformed during build

Babel's dumping a bunch of extra stuff into the code, but it's designed to be reasonably cross-browser compatible, so there's no need.

Primary issue is that we're dumping in the inlined source map


xray_ignore_rule error out when cves and vulnerabilities

Describe the bug
TF resource xray_ignore_rule fails on plan when cves = [] and vulnerabilities = ["XRAY-170461"] with Conflicting configuration arguments
Requirements for and issue

Xray Provider version

jfrog/xray v2.0.3

Terraform Version

Terraform v1.5.2

Terraform Code
resource "xray_ignore_rule" "ignore_rule" {
  notes           = "delete me now test ignore rule iac"
  vulnerabilities = ["XRAY-170461"]
  cves = []

}

Terraform Plan Output + Error

╷
│ Error: Conflicting configuration arguments
│
│   with xray_ignore_rule.ignore_rule,
│   on main.tf line 24, in resource "xray_ignore_rule" "ignore_rule":
│   24:   vulnerabilities = ["XRAY-170461"]
│
│ "vulnerabilities": conflicts with cves
╵
╷
│ Error: Conflicting configuration arguments
│
│   with xray_ignore_rule.ignore_rule,
│   on main.tf line 25, in resource "xray_ignore_rule" "ignore_rule":
│   25:   cves            = []
│
│ "cves": conflicts with vulnerabilities

Expected Behaviour

Plan should be successful

Additional context
If you create ignore rule from UI and you import it using terraform import xray_ignore_rule.ignore_rule <rule-id>

Your state file will have "cves": null,
If you do a plan after import, you will get 1 destroyed and cves value changed to []
So this is is conflicting

@Osazz In your example, since you don't want to have any cves then you should omit it in the TF configuration. This will also match the imported value of null.

Here is my full use case , I have existing ignore rules that were created from the UI that I would like to manage using Terraform. Here are the steps I took and how I endup here :

Import existing resource into IAC  and state file looks like this :

"instances": [
        {
          "schema_version": 0,
          "attributes": {
            ...
            "cves": null,
            ...
          }
        }
      ]

Do a terraform plan  ( this should returns no changes)

Terraform will perform the following actions:
# xray_ignore_rule.ignore_rule must be replaced
-/+ resource "xray_ignore_rule" "ignore_rule" {
      ~ author          = "dosagie" -> (known after apply)
      ~ created         = "2023-11-17T18:10:49Z" -> (known after apply)
      + cves            = (known after apply) # forces replacement
      ~ id              = "d169e985-87f8-43f5-4bb8-67f73c76f0ef" -> (known after apply)
      ~ is_expired      = false -> (known after apply)
        # (4 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

N.B running apply means new destroying existing resources and creating new one. Not ideal

Do terraform apply and then check the state file

@Osazz In your example, since you don't want to have any cves then you should omit it in the TF configuration. This will also match the imported value of null.

Here is my full use case , I have existing ignore rules that were created from the UI that I would like to manage using Terraform. Here are the steps I took and how I endup here :

Import existing resource into IAC  and state file looks like this :

"instances": [
        {
          "schema_version": 0,
          "attributes": {
            ...
            "cves": null,
            ...
          }
        }
      ]

Do a terraform plan  ( this should returns no changes)

Terraform will perform the following actions:
# xray_ignore_rule.ignore_rule must be replaced
-/+ resource "xray_ignore_rule" "ignore_rule" {
      ~ author          = "dosagie" -> (known after apply)
      ~ created         = "2023-11-17T18:10:49Z" -> (known after apply)
      + cves            = (known after apply) # forces replacement
      ~ id              = "d169e985-87f8-43f5-4bb8-67f73c76f0ef" -> (known after apply)
      ~ is_expired      = false -> (known after apply)
        # (4 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

N.B running apply means new destroying existing resources and creating new one. Not ideal

Do terraform apply and then check the state file

"instances": [
        {
          "schema_version": 0,
          "attributes": {
            ...
            "cves": [],
            ...
          }
        }
      ]

So that is why I setting cves as [] in the resources so that I dont have to destroy existing resource.

@Osazz Just so I understand correctly, the TF config you have before you import the resource contains cves: []? i.e.
resource "xray_ignore_rule" "ignore_rule" {
  notes           = "delete me now test ignore rule iac"
  vulnerabilities = ["XRAY-170461"]
  cves = []
}

If you omit cves attribute in your config, like:
resource "xray_ignore_rule" "ignore_rule" {
  notes           = "delete me now test ignore rule iac"
  vulnerabilities = ["XRAY-170461"]
}

Then import the resource. After that terraform plan shows updates for cves attribute?
The Xray APIs don't allow updating an existing ignore rule. Thus any mismatch of TF configuration and API data will mean the provider destroys and recreates new resource.

@alexhung  No that understanding is not correct. I have a TF config like this :
resource "xray_ignore_rule" "ignore_rule" {
  notes           = "delete me now test ignore rule iac"
  vulnerabilities = ["XRAY-170461"]
}

I do an import and then i get state file like this

"instances": [
  {
    "schema_version": 0,
    "attributes": {
      ...
      "cves": null,
      ...
    }
  }
]

then I do plan to make sure thing align and I get

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # xray_ignore_rule.ignore_rule must be replaced
-/+ resource "xray_ignore_rule" "ignore_rule" {
      ~ author          = "someauthor" -> (known after apply)
      ~ created         = "2023-11-17T18:30:29Z" -> (known after apply)
      + cves            = (known after apply) # forces replacement
      ~ id              = "91ced9b-bb1e-4d9c-488c-6bf093a36d64" -> (known after apply)
      ~ is_expired      = false -> (known after apply)
        # (4 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

Changes to Outputs:
  ~ author     = "someauthor" -> (known after apply)
  ~ created    = "2023-11-17T18:30:29Z" -> (known after apply)
  ~ id         = "91ced9b-bb1e-4d9c-488c-6bf093a36d64" -> (known after apply)
  ~ is_expired = false -> (known after apply)

When I go ahead to apply : I get this state file

"instances": [
  {
    "schema_version": 0,
    "attributes": {
      ...
      "cves": [],
      ...
    }
  }
]

What could have stopped the difference would have been me been able to give cves value as [] but then I am running into that conflict error which does not seems to be a conflict as cves            = [] is not same as vulnerabilities = ["XRAY-170461"]
The only work around which I could think of was to change the state file manual by making cves=[]. that resulted in No changes. Your infrastructure matches the configuration. but of course this is a bad practice and state file should never be manually updated.

@Osazz I see. Thanks for the clarification! I'll investigate this issue.

@alexhung any update on this issue?


Define preset-specific fields to be removed from the "Add field" dropdown

As of v2.12.2 we now have the option to specify additional fields present in the "Add fields" dropdown for different presets! :tada:
As kind of an inverse to #5582, could we specify certain fields to be ignored in the dropdown? Eventually some presets will have many things in the dropdown and it will get clogged up, and the defaults sometimes aren't relevant.
For example, "Parking Lot" doesn't need the Fax or Seamark fields.
Example code for "Parking Lot":
{
    "icon": "maki-car",
    "fields": [
        "name",
        "operator",
        "parking",
        "capacity",
        "fee",
        "access_simple",
        "supervised",
        "park_ride",
        "surface",
        "maxstay"
    ],
    "ignoreFields": [
        "email",
        "fax",
        "seamark",
        "tourism",
        "wikipedia",
        "wikidata"
    ],
    "geometry": [
        "point",
        "vertex",
        "area"
    ],
    "tags": {
        "amenity": "parking"
    },
    "terms": [
        "automobile parking",
        "car lot",
        "car parking",
        "rv parking",
        "truck parking",
        "vehicle parking"
    ],
    "name": "Parking Lot"
}

An alternative to this might be reducing the default fields to those that are immediately relevant to all objects.

Hi @rivermont! Now that we have moreFields, there's been talk about reducing or removing universal fields altogether. Rather than ignoring irrelevant fields, all relevant fields would be defined in either fields or moreFields for every preset.

@quincylvania Awesome! I like that idea better, and if there's already a plan there I'll close this. Is there an issue already open regarding that?

No, there's no issue that I'm aware of. The details still have to be flushed out, since it also wouldn't be great to repeat the same five fields 100 times. Feel free to create some sort of "don't show irrelevant fields" issue if you want! Then we can discuss the best solution.


Add typings entry to package.json.

Fix Typescript errors in definition file.
Allows module to work in Typescript with:
import {MapView, Marker, Polyline, Position} from 'nativescript-google-maps-sdk';

Thanks for the PR, changed merged.


Completed Excel tutorial

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?

What's in this Pull Request?
This PR adds a completed version of the Excel tutorial from Office Add-ins documentation.

Adding @ElizabethSamuel-MSFT for a review just to double check everything runs.

Thanks for the feedback @ElizabethSamuel-MSFT. I've updated the PR accordingly (as well as the corresponding PR in the Docs repo).


Add Mish

If we add softplus (see https://github.com/plaidml/plaidml/issues/1496) we can use it here

Eltwise version checked in for now

Done for now, possible followup (a softplus intrinsic) is tracked in plaidml/plaidml#1496


Added some more jsons to resources

Changes proposed:

buffs.json ~ in-game buffs; name & friendlyName
dmgSources.json ~ in-game damage sources; name & friendlyName
itemBuildTree.json ~ items builds; with friendlyNames
itemUseTree.json ~ what items are used in the creation of another item; with friendlyNames
updated matches createdAt-start & createdAt-end default

Cool!

@ClarkThyLord Wouldn't it be better to have them written as
{
        "name": "Buff_CelesteCore_Collapse",
        "friendlyName": "Core Collapse Buff",
 },

Instead of what is currently written as
{
        "name": "Buff_CelesteCore_Collapse",
        "friendlyName": "Celeste B",
 },

The friendly name should represent what the user will be outputting on their project in my opinion as opposed. For example, a project should not show the output to the user as Celeste B but instead call it by its name as Core Collapse Buff. Furthermore, the Celeste B doesn't help clarify the difference between Celeste ability and the buff.

Add meta information fields "actor": "Celeste", "category": "B" as a compromise. Both strings contain valuable information.

you guys are more then welcomed to edit those things in 🤗


story title in transcript rule response patch

The existing code has an "of" hanging; it looks like the story title was meant to go there.
This passes make check.

It's not hanging, though, surely, because when this response is issued it is immediately followed by the banner for the game, which opens with the title? This is a convention going back to the Infocom games, I believe. It doesn't look strange to me on screen once a transcript begins. Do other people think this is wrong?

After submitting that I had some misgivings that that might have been the intent. There had been discussion here:
https://intfiction.org/t/cutting-the-forced-version-command-out-of-transcript-on-process/56339
where the water was muddied by my having cleverly directed the version info to the transcript only but not the screen, so the screen was only getting "Start of a transcript of". But afterwards I had gone to an old conventional transcript and I thought the "of" looked  hanging there, too, even though the story title was underneath, separated by a blank line. So: two people with freshly skewed perspectives from having been looking at a variant thought it was wrong.  Anyway, this was only ever a small matter. Discard at will.

Would a compromise be to end the current response with a colon, i.e, to be "Start of a transcript of:"? That might make it clearer that what follows below is connected to this message.

I think that would be a small but true improvement.

Cool. I'm at the wrong desk to do this right now, but if you'd like to commit a change to this PR to put the colon in, I'll then merge.

Excellent!


Feature Request: Txt2AL should pull Application Area and Usage Category information from MenuSuite

It would be great if the Txt2AL tool would pull MenuSuite information and apply it to the generated Page and PageExtension AL files.

Put it up on GitHub :)

@JesperSchulz - didn't you guys build a tool that does exactly that?

We've written a PowerShell cmdlet which transfers the meta data from the menusuite into the C/AL pages and reports, as that step anyway needs to happen for our new search. The script will ship together with the October release. The name of the cmdlet is Set-ObjectPropertiesfromMenusuite. You would have to run that script BEFORE running Txt2AL. Does that meet your needs?

We will rely on that tool for the txt2al conversion pipeline. Closing this issue.


Cannot find module jasmine.json

I followed the steps off of the documentation for jasmine and added the following script
"scripts": {
		"test": "istanbul cover node_modules/jasmine/bin/jasmine.js"
	},

However, when I run the script I am getting back the error
Error: cannot find module c:\HA\VSTS\Applications\HA.Web.Main\spec\support\jasmine.json

I did not see anything about a specs support jasmine.json file to be added.   This is an odd issue to debug.  I am not sure if there is something that I need to change for windows 10 with jasmine and istanbul or if this is a bug.

I am closing this as I moved over to mocha

I am also having the same problem.

:+1:
I have the same error when run node_modules/istanbul/lib/cli.js cover node_modules/jasmine/bin/jasmine.js on linux.

Solved the issue you need to call jasmine init or node_modules/jasmine/bin/jasmine.js init if jasmine installed locally.


GitHub Action for testing OAS3 compliace

Issue_#4

test-pr has been tested
test-pull and gh-pages need to be tested

test-pr has been tested
test-pull and gh-pages need to be tested


WIP: feat(ui-kit): initial integration of MUI Base UI with Autocomplete example

Description of changes
This PR introduces MUI's Base UI initial integration and the first iteration of Autocomplete component.
Checklist
Before merging to main:

[x] Tests
[ ] Manually tested in React apps
[x] Changesets
[x] Approved

@felipecadavid please clean console.log from tests


Merge Stitch and Realm SDKs - phase 2

Phase 2:
[ ] custom_data incl bson support
[ ] functions
[ ] remote mongodb client
[ ] push
Details of above subtasks are described in this doc

➤ Brian Munkholm commented:
custom_data incl bson support in review


When autoSpacing (true) and swipeHorizontal(true) is used, the display is blurred

set autoSpacing(true) and swipeHorizontal(true) and pageFitPolicy(FitPolicy.BOTH) ,when render a more higher pdf view on landscape screen the display is blurred

Hi, on 3.1.0-beta.1 with landscape orientation, horizontal swipe, HEIGHT FitPolicy and autospacing, the first col is always blurred.
It seems that PagesLoader#loadVisible always calls loadPageEnd in that case. No problem in portrait mode.
            configurator.pageFitPolicy(FitPolicy.HEIGHT)
                    .autoSpacing(true)
                    .enableSwipe(true)
                    .swipeHorizontal(true)
                    .pageSnap(true)
                    .pageFling(true);

Thx.


Make net_model more like env so it can be used in PG

This pull request will contain the work to align the net_model class with OpenAI Gym's env class, so that we can use previously developed code to run the policy gradient learning.

Things got a little messy. Closing this PR because the only work so far (adding the configuration class) has been included in Siobhan's PR for the 6 bus network.


fix: update @smoya/asyncapi-adoption-metrics to 2.4.9 version

This PR will update @smoya/asyncapi-adoption-metrics dependency to the latest version.

/rtm

Seems like SonarCloud Code Analysis workflow is not triggered and that's preventing this PR from being merged. Any clue about it? @Souvikns @Shurtu-gal

Can you push some minor change here @peter-rr

/rtm


Meaning of material map numbers

I couldn't find this in the repository. Can you share the exact mapping from the numerical classes to the actual annotations for the material maps?

You are right, the file didn't make it into the repo. I'll add it and in the meantime, here is the mapping:
material_to_palette =  {
    "unassigned": 0,
    "I can't tell": 1,
    "More than one material": 2,
    "Cardboard": 3,
    "Ceramic": 4,
    "Concrete": 5,
    "Cork/corkboard": 6,
    "Dirt": 7,
    "Fabric/cloth": 8,
    "Foliage": 9,
    "Food": 10,
    "Fur": 11,
    "Glass": 12,
    "Granite/marble": 13,
    "Laminate": 14,
    "Leather": 15,
    "Linoleum": 16,
    "Metal": 17,
    "Mirror": 18,
    "Not on list": 19,
    "Painted": 20,
    "Paper/tissue": 21,
    "Plastic - clear": 22,
    "Plastic - opaque": 23,
    "Rubber/latex": 24,
    "Sponge": 25,
    "Styrofoam": 26,
    "Tile": 27,
    "splitshape": 28,
    "Wallpaper": 29,
    "Wax": 30,
    "Wicker": 31,
    "Wood": 32,
    "Stone": 33,
    "Chalkboard/blackboard": 34,
    "Carpet/rug": 35,
    "Brick": 36,
    "Skin": 37,
    "Water": 38,
    "Hair": 39,
    "no_consensus": 40,
}```


fix: fix resip export by turning it into a childProcess

Download Artifacts :

win-ia32
win-x64
linux-x64

Download Artifacts :

win-ia32
win-x64
linux-x64

Download Artifacts :

win-ia32
win-x64
linux-x64

Download Artifacts :

win-ia32
win-x64
linux-x64


Status Sign don't work

Hello the Signs doesn't work... When i enter the  Command [1vs1] nothing happend

Just place an sign with on the first line
[1vs1]

Oh, my Version of the Plugin was old... Sry and Thanks!


Create Kajalmehta.md

Please review these and merge.

https://github.com/dohinaf/basic-icecream-website/pull/670 not under gssoc-ext
https://github.com/Anjaliavv51/Retro/pull/712 level 1
https://github.com/yatulearn/yatulearn/pull/491 small change
https://github.com/mansiruhil13/Bobble-AI/pull/1229 level 1
so giving level 2


Vite Support

Describe the bug and the expected behavior
When using with unstableVite, when a form with errors is submitted, a red warning error message pops up on the screen before the form re-renders with the correct error validation.
Conform version
v1.0.0
Steps to Reproduce the Bug or Issue
Repro: https://stackblitz.com/edit/remix-run-remix-k7vjbi?file=app%2Froutes%2F_index.tsx
What browsers are you seeing the problem on?
Chrome
Screenshots or Videos
https://github.com/edmundhung/conform/assets/8460808/3ed00c66-2557-401b-8d2e-bf31ed0709e2
Additional context
No response

You can close this, forgot to pass the form the form.id


Package name for async storage needs updating

Hi, thanks a lot for this library, it's super useful!
I wanted to let you know that without patching, this won't work on modern React Native setups as:
https://github.com/leoafarias/use-state-persist/blob/1219518273c5b1f9b917120b7ddf2b4809ed7959/src/storage/storage.native.ts#L1
Needs to be updated to:
import AsyncStorage from '@react-native-async-storage/async-storage';
Along with the package.json reference of course.

@markymc do you want to open a PR with the changes you propose.

@markymc do you want to open a PR with the changes you propose.

Hi! The only thing you need to do is uninstall @react-native-community/async-storage and install @react-native-async-storage/async-storage. From what I see, all the methods are the same, they just changed the repository

Thanks guys. Sorry I was planning to come back to this and submit a PR later this month when I had time. 🙇♂