Incorrect number of days

Based on a countdown date, Sept. 25, 2015 from today, July 2, 2015. The months and hours display correctly. However, the amount of days return incorrectly.
%m always returns 0 regardless of the countdown date.
For kicks, I tried %M. That returns 84 days, which is correct. It returns the total number of days until the event.
However, I'm trying to display days left, taking the amount of months into consideration.
So, the countdown should read: 2 months, 22 days, 4 hours. How is it possible to render the countdown like that?

I just realized, looking at your home page, the number of days left until next year is off, too. It says 6 days. Shouldn't it be, ~26 days?

There is a gotcha with days and totalDays property, one is completely different then the other:
days:       '{int} Days left until next week',
totalDays:  '{int} Total amount of days left until final date',

@hilios Thanks for the explanation of days. I previously came from using http://keith-wood.name/countdown.html so my understanding was somewhat askew. Meaning, if there were just under 70 total days left until the event, then the countdown would output 2 months, 9 days, 16 hours left until the event. However, that doesn't seem to be the case with your plugin, right?

Yeah it would, just use the right format string:
event.strftime('%m months %d days %-H hours left');

More about at the docs:
http://hilios.github.io/jQuery.countdown/documentation.html#formatter

@hilios Thanks for your response, but by your logic days: '{int} Days left until next week' does not produce those results. According to the days implementation, there can only be 7 days max until the week restarts, and then it counts down from 7 again, correct?
For example, today is July 16, 2015. An event that starts September 25, 2015 should equal 2 months, 8 days, 8 hours from now.
But, according to this plugin, using event.strftime('%-m months %-d days %-H hours left'); the result is 2 months, 0 days, 8 hours. In other words, there is a total of 70 days (%D) left until the event. 70 total days does not equal 2 months and 0 days.
Do you understand what I'm trying to explain?

 The problem is how I calculate both months and years, check-it out:
{ //...
months    : Math.floor(this.totalSecsLeft / 60 / 60 / 24 / 30),
years     : Math.floor(this.totalSecsLeft / 60 / 60 / 24 / 365)
}

Can you see that not every month have 30 days, and neither years have always 365 days? I am very aware of this problem, and from day one I added a warning at the Formatter documentation, about it:

Due to their non linear constrains the years and months calculation are not precise and it's pretending to use as a approximation or not use at all.

Sorry about that, do you know how to do that calculation in the proper matter? I would be happy to implement or receive a pull request.
Regards!

@hilios I'd love to help you out, but sadly, I'm just a mere CSS guy. Have you checked out Keith Woods implementation?

In the end was very easy to implement, I did smalls improvements in the year and month calculation and added a new parameter to strftime and event object.
Now you are able to get the amount of days left to the month (%n), like the following example:
$('#clock').countdown('YYYY/MM/DD', function(event) {
    $(this).html(event.strftime('%m months and %n days till end.'));
});

Isn't always precise but, at least is something but either mr. Woods is.
You can grad the code at:
https://github.com/hilios/jQuery.countdown/blob/diff-dates/dist/jquery.countdown.js
Take a look to the unit test if you want to assure the implementation math:
https://github.com/hilios/jQuery.countdown/blob/diff-dates/test/unit/math_test.js#L23

@hilios Thanks for your hard work, works like charm!

Ready to launch at version 2.1.0


http_api (ticdc): Fix http api get processor panic and add some unit tests.

What problem does this PR solve?
#3840
What is changed and how it works?
Check List
Tests

Unit test
Integration test

Code changes
Side effects
Related changes
Release note
Fix http api get processor panic when the capture_id in query param is error.

/run-all-tests

/run-all-tests

/run-integration-tests

/run-integration-tests

Codecov Report

Merging #3935 (39abf5c) into master (3873d39) will decrease coverage by 1.5803%.
The diff coverage is 68.7069%.

Flag
Coverage Δ

cdc
59.4254% <68.7069%> (+1.1888%)
:arrow_up:

dm
52.1967% <ø> (-3.8378%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #3935        +/-   ##
================================================
- Coverage   57.0741%   55.4938%   -1.5804%
================================================
  Files           478        486         +8
  Lines         56551      59758      +3207
================================================
+ Hits          32276      33162       +886
- Misses        20978      23206      +2228
- Partials       3297       3390        +93

/run-integration-tests

/run-integration-tests


Test issue notifications

Expected Behaviour
Tes issue to check notifications
Actual Behaviour
The team will get notified about this issue being created
Reproduce Scenario (including but not limited to)
N/A
Steps to Reproduce
N/A
Platform and Version
N/A
Sample Code that illustrates the problem
N/A
Logs taken while reproducing problem
N/A

Used to test notifications... Closing


Exporting a file with performance issue (transparency issue) [Animated GIF]

Sprite details

number of frames: 18
sprite resolution: 330 x 500
session duration: 1 hour

Trying to export a high quality pixel file WITH transparency but performance issues occurs, saying its too many pixels being used:
How can i lower the amount of colors (it says i have too many colors and even when i erase most colors or instead take some out it still says too much? Or is there a way to help boost performance for this program it so it can export high quality + transparency?
Trying to find a work around for this that wont destroy the quality of my animated gif or have  a background to it.

I had the same issue when I tried to export a file called cape.PNG.gif. I realized the issue was the following two things:

Multiple Layers

It doesn’t support transparency with more than one layer. Try merging the layers together once you are ready to export.

Your browser

Certain browsers don’t support perfect exporting. If you are using Apple Safari, any Webkit-based browsers, IE, or a NodeJs Electron Browser, try switching to Edge or Firefox.

Color amount

You noticed that it didn’t like the color amount. You probably have more than 30 colors if thats the case or swap too frequently. Instead of erasing certain colors, try using them less.

Try checking those and see if any of these suggestions help. If you clarify which browser you use, it would probably help my suggestions be more accurate to your situation. Please note I am not a Piskelapp developer, but I do use HTML, CSS, and JS as my primary programs.


Allow for xmlStandalone

Added a check that $options['standalone'] = bool generates standalone declaration.
new FluidXML('books', ['standalone' => true]);
produces
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

Coverage decreased (-0.4%) to 99.456% when pulling f39aa46851d5636c4b5d1b0fa452418f0cda0c5c on copierNetwork:patch-1 into b6fb8de6ff781479c9e4fb6e9f27b5af1e87dc4b on servo-php:master.

Hello, any chance to get it merged?

I second tridcatij’s comment. This has been lying around for over two years… can we get it merged? Being able to make standalone XML documents would be a big advantage.


What kind of equivalence to use for Tasks in SchedulingPool?

Currently, only Task's id is used.
It is the fastest option(Tasks are being inserted into a Map, with Id as key), but may not be desired.

Task is equal on Facility and Service. Dispatcher will handle cases when Task that is already being generated/sent is received by setting a flag that will cause rescheduling when the current gen/send is finished.


capabilities: consider dropping 'remove' method

Two clashing definitions are given for the list of linux kernel capabilities that should be made available to the container: one explicit, one implicit.
Presumably this is because the ..._remove method is the traditional approach within LXC and therefore is the format expected within docker and other image types that appc is assumed to import from (and ultimately deprecate :question:). However, this is bad because it is non-deterministic.
A neater approach would be to convert ..._remove sets to retain sets on import.

I understand the concern about the remove set and I am not a huge fan but I don't think we can convert the remove set to retain as the kernel will add capabilities overtime.

The very fact that the kernel will add capabilities over time is why an explicit ...retain approach should be strenuously encouraged and ..._remove forcibly deprecated.
Scenario:

Kernel version 1 has capabilities A, B and C.
Kernel version 2 adds capability D.

With a ..._retain approach, a service explicitly specifying that it requires A and B capabilities will survive the upgrade to kernel version 2 without magically acquiring the new capability.
With a ..._remove approach, the same service explicitly specifying that it does not require C capability will magically acquire capability D upon kernel upgrade.
It is known correct practice to "deny all, permit explicitly" within a security context. I hope this is clear.


docs: Add sphinx-copybutton support

Resolves #462

Add sphinx-copybutton v0.5.2+ to the 'docs' extra.
Enable sphinx-copybutton support in the Sphinx conf.py.

@ketan96-m @BenGalewsky @ponyisi This is ready for review.


modify a warning

Fix a warning, I found a warning in my project

my Xcode is 8.1 ,  I'm sure there's a warning😳

@chaiyanpu Thanks a lot for your contribution! I've used part of your modifications in https://github.com/SwiftyJSON/SwiftyJSON/pull/729 and made sure tests also build without warnings. Most importantly, I avoided using force unwraps so that nothing leads to crashes. Closing this in favor of https://github.com/SwiftyJSON/SwiftyJSON/pull/729, thanks again!


Support Filters initializer with IFilter arguments

I have a class Source that contains a field IDictionary<string, string> Tags. I want to create Filters based on these tags. I would like to be able to initialize the filter like this:
new Filters(Filters.FiltersType.OR, source.Tags.Select(t =>
        new Filters(Filters.FiltersType.AND)
        {
            new Filter($"TAGS.[Key] = {t.Key}"),
            new Filter($"TAGS.Value = {t.Value}")
        }
    )
);

This requires a new initializer on Filters:
public Filters(FiltersType type, IEnumerable<IFilter> filters);

The public Filters(FiltersType type, params FormattableString[] filters) initializer can then just call the new one.

Sounds like a good idea. Would you like to create a PR for this?

Thank you for the PR!


docs(navigation): mistake in comment within ionViewCanEnter method example

Description:
Under the Nav Guards examples, the method ionCanViewEnter has a comment that says "here we can either return true or false depending on if we want to leave this view". The expected comment should be "here we can either return true or false depending on if we want to enter this view".

This issue was moved to ionic-team/ionic-site#1196


 Otherwise i can send you another Pull request.

@mariohahn I get where you are coming from, but ideally would prefer not to add any extra macro definitions when possible

Agree with @cloudkite in the future tvOS and iOS may diverge features and a joined macro is less flexible. @mariohahn if you can update the PR we'll merge it!

I changed it (:

Any News about this?

@mariohahn looks great! sorry for delay.
only change I think would be good is too include backwards compatibility for previous versions of Xcode see
https://github.com/AFNetworking/AFNetworking/blob/master/AFNetworking.podspec#L15-L27

(:

https://www.youtube.com/watch?v=ZXsQAXx_ao0 💪🏼

Thanks again !

could you please update the pod?

@mariohahn pushed :)


Why black hair noise issue more serious in WFOV mode  than in NFOV mode ?

Why black hair noise issue more serious in WFOV mode  than in NFOV mode ?
Is there any way to solve hair noise  from top down Capture depth image?

@carlhuang070 , the depth camera is a Time of flight camera, therefore, low reflectivity object tends to have more noise simply because the return signal is less compare to high reflectivity objects at the same distance.
The reason WFOV mode contains more noise on such low reflectivity objects is because the signal strength received by sensor is less than NFOV per pixel. The Azure Kinect is a USB powered device, with limited power resource, 4 different depth modes were designed for supporting different field of view and range to fulfill various users' needs. Refer to this page to understand each mode's field of view and range.

@rabbitdaxi , Can we adjust the signal intensity to reduce hair noise in WFOV?

@carlhuang070 , the signal intensity  is a hardware configuration which is not adjustable from SDK (even though it is possible to configure illumination profile and gain from the depth camera module level, but in that case, we are talking about a new hardware).
Are you using WFOV2X2BINNED or WFOVUNBINNED? the WFOV2X2BINNED should have stronger signal compare to the UNBINNED.
Other than that, your best choices here are either use NFOV modes, or move camera closer to the hair.

@carlhuang070 According to my previous experience with Kinect-v2, a workaround to a similar issue was to place a light source in front and above the users' area.

@rabbitdaxi , i using WFOV2*2binned, the distance between DK and hair about 1.5m.
and the noise is very seriously.

@rabbitdaxi , I compare Kinect DK NFOV 2*2binned mode  with Kinect V2,  DK hair noise issue is more seriously at the same distance far away Camera .
I found DK power: 5V ,2.5A
Kinect V2: 12V,2.67A

@carlhuang070 thank your for your response. Your assumption that Azure Kinect consumes less power compare to Kinect V2 is correct. Azure Kinect is design for low power consumption (just USB powered), Kinect V2 require the AC power adapter. Your issue can not be solved by software, it is what the current DK hardware design offers. You can add your feedback to the feedback hub https://feedback.azure.com/forums/920053-azure-kinect-dk

@carlhuang070  as you siad, i am using a led light tube in front and above my head, but noise still the same as before. wondering what type of illumination light source you used?

this problem seems will be solved when the kinect depth sensor has a HDR mode.


arch.sh: use community binary repository for gazebo

Describe problem solved by this pull request
This makes installation a lot faster and less error prone.
Describe your solution
Use @bionade24's arch binary repository https://wiki.archlinux.org/index.php/Unofficial_user_repositories#oscloud
Test data / coverage
I tested on two Manjaro machines. More feedback welcome @julianoes @bresch @DanielePettenuzzo

FMI Would this also be a reasonable approach for Ubuntu and other platforms?

@hamishwillee OSRF provides binaries for Ubuntu only (AFAIK) so on Ubuntu we're anyways using the official releases maintained by the authors. Other distributions and OSes need to rely on community-based deployment and this pr uses one of these opportunities for Arch.

Please don't assign me to things I'm not involved, this is annoying. Thanks.


Fix python compiler for filenames with dashes

This is consistent with how protobuf handles "-" in names.

No significant performance differences

#5226

Could you also rename proxy-service.proto to proxy_service.proto?

#11223
#11216


tests on linux-type machines failed due to bad python 3.7.4 build in conda

Issue Description
What did you expect to see happen?
What did you see instead?
Tests on linux-type machines failed
Do you have a suggested fix for the development team?
Downgrade python to 3.7.3 for now
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

related issue: https://github.com/conda/conda/issues/9084

Issue reported in anaconda: https://github.com/ContinuumIO/anaconda-issues/issues/11195

Closure checklist passed and this Issue is accepted for closure via #1038


Separate @Column (indexed = true) for methods creation and sqlite index creation

Hi, i am switching to this library, from DBFlow.
I a'm creating some table, i want to query some columns without the need to force sqlite make index on them(have methods in java but not index on table).  sometimes i want to query all fields , and many fields contains few values (ex: 0 or 1). making index on all of fields is crazy. Generating methods for querying a database  is not the same of having index on fields, this is two different things, and i think this should be separated.
A quick fix for this and to be backward compatible maybe be something like:

@Column (indexed = true)// both indexed, and gen methods
String userName;

@Column (methods = true)// just generate methods
String gender;

I like to see this in next release of this nice lib.

Thanks to the indication. It seems good to me and will implement it in a few days.
I think the interface is something like this: @Column(helpers = Helpers.ALL) where .ALL, .NONE, .FILTERS, .ORDERS, and so on.

Thank you for your respond and effort.
I have also used SquiDB, but those library was so abstract, and complex and hard to use and did't feel what your final query would look like. I have read your library code and generated classes, it easy to warp my mind around it, it has nice design.
Thanks.

This feature is released as v2.6.0. Can you give it a try?

Yeh, i have tested this, and it works as expected, thanks.


Add GTM safe apps event tracking

What it solves
Resolves https://github.com/gnosis/safe-apps-sdk/issues/309
How this PR fixes it
We are adding to the current GTM container:

4 new variables

1 trigger

1 Safe App Tag bounded to a GA4 event

1 Safe App tag specifying the Measurement ID for the Safe App property

How to test it
Analytics changes
Screenshots

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 6 (16.67%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 36.025%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/safe/components/Apps/communicator.ts
0
1
0.0%

src/utils/googleTagManager.ts
1
5
20.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
3518

Relevant Lines:
8873

💛  - Coveralls

Made some changes here after an internal discussion in the safe-apps team.

Using new variables for tracking only messages (big amount of events)
Using regular trackEvent for actions as transaction confirmed / rejected or legacy usage of apis
Removed deprecated and params variable as are not really useful (params => sentry same functionality)


#[derive(FromPrimitive)] panics on pub(crate)

From @hmvp on December 14, 2017 15:6
This does not compile:
#[derive(Debug, FromPrimitive)]
pub(crate) enum Foo {
    A = 1,
    B = 2,
}

removing (crate) makes it work
Copied from original issue: rust-num/num#352

From @hcpl on December 14, 2017 16:50
And I'd like to mention that
#[macro_use]
extern crate num_derive;

#[derive(Debug, FromPrimitive)]
pub(crate) enum Foo {
    A = 1,
    B = 2,
}

doesn't work ~because num-derive doesn't re-export traits from num-traits~ -- you also need extern crate num; (not even extern crate num-traits; can fix this because the derived code depends directly on num). This is something I'd also like to rectify when I get some time.

From @hcpl on December 14, 2017 16:3
Applying this patch to num will make the OP's code compilable:

diff --git a/derive/Cargo.toml b/derive/Cargo.toml
index 2a17ce0..94cf68a 100644
--- a/derive/Cargo.toml
+++ b/derive/Cargo.toml
@@ -11,8 +11,8 @@ repository = "https://github.com/rust-num/num"
 version = "0.1.41"

 [dependencies]
-quote = "0.1.3"
-syn = "0.7.0"
+quote = "0.3.15"
+syn = "0.11.11"

 [dev-dependencies]
 compiletest_rs = "0.2.5"
diff --git a/derive/src/lib.rs b/derive/src/lib.rs
index e75fa06..8c0f420 100644
--- a/derive/src/lib.rs
+++ b/derive/src/lib.rs
@@ -42,8 +42,10 @@ pub fn from_primitive(input: TokenStream) -> TokenStream {
                     panic!("`FromPrimitive` can be applied only to unitary enums, {}::{} is either struct or tuple", name, ident)
                 },
             }
-            if let Some(val) = variant.discriminant {
-                idx = val.value;
+            if let Some(ref val) = variant.discriminant {
+                if let syn::ConstExpr::Lit(syn::Lit::Int(value, _)) = *val {
+                    idx = value;
+                }
             }
             let tt = quote!(#idx => Some(#name::#ident));
             idx += 1;
@@ -91,8 +93,10 @@ pub fn to_primitive(input: TokenStream) -> TokenStream {
                     panic!("`ToPrimitive` can be applied only to unitary enums, {}::{} is either struct or tuple", name, ident)
                 },
             }
-            if let Some(val) = variant.discriminant {
-                idx = val.value;
+            if let Some(ref val) = variant.discriminant {
+                if let syn::ConstExpr::Lit(syn::Lit::Int(value, _)) = *val {
+                    idx = value;
+                }
             }
             let tt = quote!(#name::#ident => #idx);
             idx += 1;

@cuviper, what do you think about this code and related compatibility issues? If everything is ok, I'll send a PR containing this patch.

what do you think about this code and related compatibility issues?

The code is fine with me if it works.  What exactly are the compatibility issues?
I think bumping semver on num-derive wouldn't be a problem, if needed.  It's not the sort of crate that shows up as public dependencies -- only the traits it implements.

num-derive doesn't re-export traits from num-traits

I don't think proc-macro crates are even allowed to export anything but their #[proc_macro_derive] functions.
But I think it would be OK to make this depend on num-traits instead of num (as a breaking change).

From @hcpl on December 14, 2017 17:28

What exactly are the compatibility issues?

Well, my question was more like "is there any possibility for breaking changes to happen" if this patch gets accepted. Though you already said this is a non-issue, so we're good.

I don't think proc-macro crates are even allowed to export anything but their #[proc_macro_derive] functions.

Yeah, that was my mistake (funny thing, I crossed my part out right after you posted the comment :smile:).
The thing is, we could make num-derive to (ab)use such a Rust construct:
const _IMPL_NUM_FROM_PRIMITIVE_FOR_Foo: () = {
    extern crate num_traits as _num_traits;
    /* ... */
};

like serde_derive does so that we would only need a num-traits = "0.1" entry in Cargo.toml but not extern crate num_traits; to make this work.
Replacing num with num-traits is another matter which is not that important compared to the above one, but is a nice thing for builds that don't need all num features.

Well, my question was more like "is there any possibility for breaking changes to happen" if this patch gets accepted. Though you already said this is a non-issue, so we're good.

It probably just depends on what the rustc minimum is for the newer syn/quote, but it looks like they both have CI for 1.15.1, so that should be fine.  We could still bump for num-traits though.

(ab)use such a Rust construct: [...] like serde_derive does

I'm happy to follow serde's lead on this.


docs: Adding document and notebook for Data Balance Analysis

Codecov Report

Merging #1226 (33c55e8) into master (73c6a65) will decrease coverage by 82.77%.
The diff coverage is n/a.

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

@memoryz @mhamilton723 Where do you guys think I should host the Data Balance Analysis md? Currently, I have it in "features" under a new folder named "exploratory". However, do you guys have suggestions for better places than this?

I think having the folder structure matching the package name is a good idea. In the future, we might want to bundle this with the explainers into a rai module, so the doc can be moved together.

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run


[chore] rename method name and improve logging and comments

Proposed changes
Issue Number: close #xxx
method name, comments and logs improved in be/src folder.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Import ADR-76

Title: Handling usage of dynamically-async-created DNS records from
dependent services

@tombentley @emmanuelbernard please take a look, I think this can be merged. Thanks! It's referred to in #45 as an example of AP-13.

/lgtm

Thanks for the approvals folks. I don't have the ability to merge here, so one of you will have to do it.
I still have some follow-up TODO items for some of the stuff I mentioned above. I will get around to those soon, but those will be separate PRs, and none of them should block this from being merged, in my opinion.


Updating to @web5/credentials 0.45

Rizel's context:

Updated web5/credentials to version 0.45 per conversation found here: https://discord.com/channels/937858703112155166/1224352979113476207/1224555825339695135
Version 0.44 and above includes the VerifiablePresentation methods, so I updated the docs to reflect that.
I replaced mentions of did:key with did:dht

This PR closes #1205 and closes #1227
Generated Copilot description
This pull request includes changes primarily related to updating package versions, adding new dependencies, and updating the documentation. The most significant changes are the update of the @web5/credentials package version, the addition of new dependencies in pnpm-lock.yaml, and the changes in the documentation files fan-club-vc.mdx and presentation-exchange.mdx.
Package version updates:

package.json: Updated the version of @web5/credentials from 0.4.2 to 0.4.5.
pnpm-lock.yaml: Updated the specifier and version of @web5/credentials from 0.4.2 to 0.4.5 in the importers: section.

New dependencies:

pnpm-lock.yaml: Added new dependencies<EMAIL_ADDRESS>and<EMAIL_ADDRESS>in the packages: section. [1] [2]

Documentation updates:

site/docs/web5/build/verifiable-credentials/fan-club-vc.mdx: Various changes were made to the code snippets, including the addition of VerifiablePresentation to the import statement and changes to the id and issuer fields in the vcDataModel. [1] [2] [3]
site/docs/web5/build/verifiable-credentials/presentation-exchange.mdx: Added VerifiablePresentation to the import statement and made changes to the presentation result. [1] [2]

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1206921563121003

Things to note:

evaluatePresentation doesn't have a kotlin equivalent because it's going to change to this https://github.com/TBD54566975/web5-js/issues/426
validateSubmission in JS and Kotlin don't have equivalent logic. Need to ask devs about this

oh lmaooo @acekyd that's what I get for creating this PR at 3am. I'll update the PR title. Thanks for reviewing yall @EbonyLouis ❤


feat(generator): make idempotency policy non-abstract

The generated *IdempotencyPolicy class cannot be pure abstract. If it
is, any custom idempotency policy breaks when we generate new member
functions.

This change is

/gcbrun


[BUG] Unable to receive answer in chainlit frontend

Describe the bug
Starting from this https://github.com/HenryHengZJ/flowise-streamlit I created a new chainlit version with Claude help.
Was working without sessionid management, now no answer is shown.
Not sure how to manage this with flowise.
To Reproduce
Steps to reproduce the behavior:

copy files (see below zip files)
install dependencies
update .env file with APP_URL and FLOW_ID
launch app using "chainlit run chainlit_app.py --port 8501"
try to ask anything

Expected behavior
Receive an answer.
Screenshots

Flow
Chainlit test Chatflow.json
Setup

Installation: npx flowise start
Flowise Version: 2.1.1
OS: Linux
Browser Firefox

Additional context
chainlit_app.zip

This release seems to work, even if I need to test his stability during time
chainlit_app_unique.zip

Thanks for figuring out the correct release, by right what works on streamlit should works on other similar apps as well, we are using the standard Server Side Event (same as OpenAI)


[Bug]: Duplicate tool in the website

What happened?
I found a BUG 🐞
I was searching for some tools in the website and found that there is a duplicate tool in the webiste by the name of "futurepedia".
One of them must be removed.
Add screenshots

I'd like to work on this issue under GSSOC'23, @JasonDsouza212 .
What browsers are you seeing the problem on?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@mukul314 you can start working on this


MANAGEMENT_MODE service group no longer belongs in RPMI

Now that SBI MPXY has been made generic and no longer relies on RPMI, MANAGEMENT_MODE can be implemented directly as an MPXY message protocol. I doubt anyone plans to implement MANAGEMENT_MODE on an actual platform microcontroller, so I don't think it belongs in the RPMI spec anymore (though I don't have a suggestion for where to put it).

Talked to Yong Li previously, he want keep this in RPMI.
@yli147 can you comment on this?

Hi Holland,  the MANAGEMENT_MODE can be on an actual platform microcontroller or on a secure domain of a application processor hart.
Thus MANAGEMENT_MODE service APIs can be defined either in RPMI specification or as a separate specification just like RPMI specification .
But defining a separate specification for this "simple" MANAGEMENT_MODE service may not cost-saving at least from RVI process perspective.
Thus, the opinion is that we still keep only one copy of the MANAGEMENT_MODE service API definition in RPMI spec,  but user can implement MANAGEMENT_MODE either through using RPMI protocol or directly as an MPXY message protocol (in this case still leverage the MANAGEMENT_MODE services defined in RPMI)
by the way, there may still some vendors to extend HSM kind of subsystem to support secure execution environments.

@yli147 I am simply thinking from the process point view for example take a new SBI extension which when proposed requires a PoC. Similarly, is there a PoC exist for MM RPMI service group currently?

If PoC exist then lets keep it in the RPMI, if not then lets add it later IMO.

@pathakraul yes, the PoC is there,  let me rebase it to your latest code. Thanks

Looking at the StandaloneMM PoC (specifically https://github.com/yli147/opensbi/commit/91c57f5ca8bd2b0cee270a8024559ef09f0584fb), the protocol implemented there looks very different from the RPMI service group. There is no indirection through MM_COMM_DATA; the MPXY shared memory contents are passed directly to the other supervisor domain.
In fact, if there's no buffer indirection, we may not even need a separate spec. The MPXY spec can directly reference the UEFI spec as defining the contents of the protocol. So it shouldn't create much process overhead.

Yes, we can close this issue. Thanks for having the meeting to discuss this.


connt pull file , size over 4kb

hi ,great !
I used this nice art,it is so wonderful. thank you!
now,I find ,full file  larger than 4KB,it failed.
message: expected at least 65536, got 4096!
how can I do  it?

webadb.js:623 Uncaught (in promise) Error: PULL DONE failed on /sdcard/Pictures/1642089797468.jpg
at webadb.js:623
at async pull (adbt:33)
at async test (adbt:43)
______________
getting this, while running your test.
that's
if (decode_cmd(cmd) != "DONE" || zero != 0)
this string ^
so it loads some, then fails.
what I actually want is retrieving a screenshot, so any advises are welcome
my scenario is close to rdp, so I want something like scrcpy, only with pure javascript

Not sure if it's the same issue, but leaving it here.


MobileServiceInvalidOperationException.Value is sometimes null

I've implemented conflict resolution via IMobileServiceSyncHandler.ExecuteTableOperationAsync().
I catch MobileServiceConflictException and MobileServicePreconditionFailedException. Then I inspect the server's value via exception.Value, and decide how to handle the conflict.
Problem is, I expect that value to be populated, but sometimes it's null. I can't pin down when that happens though. Sometimes it is and sometimes it isn't!

I just found something interesting - in this example, it says that this can happen for HTTP status code 409 ("Precondition Failed").
But, is this a bug or by design??

@migig, there have been discussions on changing this behavior, but with the current implementation, this is by design. The sample you have linked to shows how to handle those conflicts, so I'll be closing this issue, but feel free to ask any questions if you need more information.

@fabiocav Thanks for the confirmation.
I'm new to this SDK. That workaround seems a little "hackish" (no offense, I'm sure there's a good reason for it), so is it expected to work always? i.e. If I implement that workaround can I just forget about this problem?

@migig It will definitely always work to do a server call to get the current value, though it's possible that the server SDK in the future would send back the conflicted value (but probably in a major revision). The reason for the behavior is that not all data providers automatically return the current value, so it can result in more database calls, which might be potentially unnecessary.

@lindydonna Thanks for explaining the by-design reasoning, it makes sense now.


Difference between how UI and Cockpit Composer UI call Amazon images

https://github.com/osbuild/image-builder-frontend/commit/404a80e59c0951c8de3fb595c385cbf529d52ff9 uses
"Amazon Machine Image (.raw)" which is shown in the UI while the Cockpit Composer counterpart uses
"Amazon Machine Image Disk (.ami)":

Closing this since the way cockpit-composer and image-builder-frontend display image types is substantially different now, by design.


Custom key ID extension missing from WUM branch.

Describe the issue:
Custom Key ID extension is missing from the IS 5.10.0 wum branch.
How to reproduce:

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 5.10.0

Optional Fields
Related issues:

Suggested labels:

@dimuthnc Is the fix available in master?

Closing as it is fixed in master


Publish ROS package actions

Purpose

Each action that is used across our ROS packages should be published so that updates can be pushed to all ROS package repositories automatically.
Changes

Create repository for lint action
Create repository for test action
Use published actions in this repository

Resources

https://docs.github.com/en/actions/creating-actions

Status:
Awaiting repo made for actions (lack of permissions)

Explore https://docs.github.com/en/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow

Explore https://docs.github.com/en/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow

Reuse network_systems CI in other repos
Possible to reuse sailbot_workspace CI in network_systems?

Should there be 2 files in total or 4?
e.g.

run network_systems CI test actions
run network_systems CI lint actions
run sailbot_workspace CI test actions
run sailbot_workspace CI lint actions
OR
run network & sailbot lint actions
run network & sailbot test actions

I have the code on my local machine but I'll want to know which one it is before a push, thank you

My checklist:

[ ] Network systems & sailbot actions are accessible by others (see
[ ] Create repository for actions? (changed plans, to re-use workflows instead)
[ ] Use published actions in this repository
[ ] Make .yml workflow to use network_systems CI
[ ] Make .yml workflow to use sailbot_workspace CI

Additional Notes:

to edit

I want to have as little duplicate code in workflows as possible. Ideally it would look like this: both sailbot_workspace and subteam repositories use workflows defined in sailbot_workspace. The subteam repositories would call it with different arguments to only run the tests that are applicable to their codebase and only run those tests on their codebase. With what you know now, do you think this is possible?

The way our current workflows in sailbot_workspace are written involves using our local actions .yml within .github/actions.
  colcon-test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v3

This means if we call our workflows from within the same repository, it's super easy, but that's not what we want here, since we want to call it from another repository (e.g. network systems), and have minimal duplicate code, which means somehow just calling sailbot_workspace workflows and not having to duplicate the action files into our .github folder
call-workflow-1-in-workflows: # Calls tests.yaml, requires to duplicate code into own workflow, so duplicate code needed
    #uses: actions/checkout@v3
    uses: UBCSailbot/sailbot_workspace/.github/workflows/tests.yaml@user/colinli02/11-Publish-ROS-package-actions

So if we want to call sailbot_workspace's workflow, we would want to be able to somehow checkout the actions into our sub-team repository. However that means we can't straight up call "tests.yaml" from sailbot_workspace, since we need to somehow checkout the ./.github/actions
All solutions:
A)
https://github.com/orgs/community/discussions/26766 Manually copy the entire .github file over into our sub-team repos, but this defeats the purpose since we want to minimize code duplication without copying sailbot_workspace's workflow over and having sailbot_workspace as a "central" workflow.
B)
Henry has a smart workaround where he "clone[s] sailbot_workspace:main so that sailbot_workspace is the root, and then clone network_systems into it and run the actions defined in sailbot_workspace". for example https://github.com/UBCSailbot/network_systems/blob/main/.github/workflows/lint.yaml This is probably our best solution, to follow Henry's method since we can still have our central workflows in sailbot_workspace, however comes at the cost of still not having a completely centralized workflow in sailbot_workspace and just calling it, since there are chunks of code where it calls another public repo's workflow
  # https://github.com/gaurav-nelson/github-action-markdown-link-check
  markdown-link-check:
    runs-on: ubuntu-latest
    steps:
    - name: Check out code
      uses: actions/checkout@v3

    - name: Run linter
      uses: gaurav-nelson/github-action-markdown-link-check@v1
      with:
        config-file: .markdown-link-check.json
        folder-path: .

which means if we were to want to change these parts, we would have to change ALL the sub-teams individually.
This also means we have to make minimal modifications to parts such as:

name: Checkout code
uses: actions/checkout@v3
with:
path: src/network_systems # change here to your repo src name

C)
If we were to want a completely centralized workflow in sailbot_workspace and call it, we would have to move these "public" repos ex:
- name: Run linter
     uses: gaurav-nelson/github-action-markdown-link-check@v1
     with:
       config-file: .markdown-link-check.json
       folder-path: .

into our sailbot_workspace into actions and call it, but from what I have so far looked into it I don't think this is possible.
TLDR: Unfortunately, from what I have researched the ability to call sailbot_workspace's workflows directly without any code duplication is not possible at this moment. (edited)
So my conclusion is if we wanted to only use sailbot_workspace's workflows, we have to copy Henry's current network_systems CI implementation methods, however unfortunately that means we don't have a way of completely having a central workflow in sailbot_workspace to "just call" since there are parts that we cannot keep in sailbot_workspace only.

Thanks for your extensive research into this matter, this is definitely not a simple problem and I'm glad to see you rise to the occasion.
Responding to the following comment:

I have taken a long look into this and unfortunately it's not as simple as just calling the re-useable workflow even with on.workflow_call implemented onto the .yaml. This is because these re-useable workflows do not require checkouts of actions like we have set-up.

Background
Current sailbot Workspace CI
  colcon-test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v3

      - name: Test
        uses: ./.github/actions/test/

Current network system CI
  colcon-test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout workspace
        uses: actions/checkout@v3
        with:
          repository: UBCSailbot/sailbot_workspace

      - name: Checkout code
        uses: actions/checkout@v3
        with:
          path: src/network_systems

      - name: Test
        uses: ./.github/actions/test/
        env:
          DISABLE_VCS: true

Goal
Update sailbot workspace CI so that it can run like current sailbot workspace CI when called by sailbot_workspace and like current network systems CI when called by network_systems.
Proposed solution
I believe that this behavior can be achieved by using jobs.<job_id>.steps[*].if and on.workflow_call.inputs.<input_id>.type.
Updated sailbot workspace CI
  colcon-test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout workspace
        uses: actions/checkout@v3
        with:
          repository: ${{ inputs.repository }}

      - name: Checkout code
        if: ${{ inputs.repository }} != ${{ github.repository }}
        uses: actions/checkout@v3
        with:
          path: src/${{ inputs.repository }}

      - name: Test
        uses: ./.github/actions/test/
        env:
          DISABLE_VCS: ${{ inputs.disable-vcs }}

Would something like this work?
Resources

https://docs.github.com/en/enterprise-cloud@latest/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow

Alright, here's an update on my current progress:
Calling Sailbot_workspace CI within network_systems:
Calling test action only
Status: ✔
Network_systems code:
# Calls sailbot ws CI within network systems
jobs:
# Calls our workflow in sailbot_workspace
# UBCSailbot/sailbot_workspace/tree/main/.github/workflows
  call-workflow-1-in-sailbot:
        uses: UBCSailbot/sailbot_workspace/.github/workflows/tests.yml@user/colinli02/11-Publish-ROS-package-actions
        with:
            config-path: .github/tests.yml
        secrets: inherit

CI Code
name: Tests

on:
  workflow_call:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

on:
  workflow_call:
    inputs:
      disable-vcs:
        required: true
        type: string
      repository:
        required: true
        type: string

jobs:
  colcon-test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout workspace
        uses: actions/checkout@v3
        with:
          repository: UBCSailbot/sailbot_workspace

      - name: Checkout code
        if: ${{ inputs.repository }} != ${{ github.repository }}
        uses: actions/checkout@v3
        with:
          path: src/${{ inputs.repository }}

      - name: Test
        uses: ./.github/actions/test/
        env:
          DISABLE_VCS: ${{ inputs.disable-vcs }}

... to edit

Useful references for the future:
https://github.com/actions/checkout
https://github.com/actions/checkout/issues/24

Issue with PR:
Now that I have squished its commit history, I can't create a PR, nor can I git pull because of its different histories.
However based on the above information, I think its easy to just manually add it in, test it to make sure it works, then commit it from the main branch. Unless there is a solution to this issue.
The only required change in code to verify it works:
        uses: UBCSailbot/sailbot_workspace/.github/workflows/tests.yml@user/colinli02/11-Publish-ROS-package-actions

into
        uses: UBCSailbot/sailbot_workspace/.github/workflows/tests.yml@umain

Just create a new branch and copy over the changes you made

Can git reset to specific commit ID


chatGPT Assistants API

... could be an alternative to #26 and #88
https://help.openai.com/en/articles/8673914-gpts-vs-assistants

Oh, I see....


Add tweedie to LightGBM

Also add the post_transform in general so that it can be used by other operators eventually.
Closes #240.

Codecov Report

Merging #242 into master will decrease coverage by 0.06%.
The diff coverage is 70.00%.

@@            Coverage Diff             @@
##           master     #242      +/-   ##
==========================================
- Coverage   93.60%   93.53%   -0.07%
==========================================
  Files          39       39
  Lines        2094     2104      +10
  Branches      378      382       +4
==========================================
+ Hits         1960     1968       +8
- Misses         71       72       +1
- Partials       63       64       +1

Flag
Coverage Δ

#unittests
93.53% <70.00%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ummingbird/ml/operator_converters/_gbdt_commons.py
94.59% <50.00%> (-2.47%)
:arrow_down:

hummingbird/ml/operator_converters/constants.py
100.00% <100.00%> (ø)

...ingbird/ml/operator_converters/sklearn/lightgbm.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Model class initialization

A question about code style.  As an example the Agent class is:
@dataclass_with_properties
class Agent(Element):
    def __init__(
        self,
        spdx_id: str,
        creation_info: Optional[CreationInfo] = None,
        name: Optional[str] = None,
        summary: Optional[str] = None,
        description: Optional[str] = None,
        comment: Optional[str] = None,
        verified_using: List[IntegrityMethod] = None,
        external_reference: List[ExternalReference] = None,
        external_identifier: List[ExternalIdentifier] = None,
        extension: Optional[str] = None,
    ):
        verified_using = [] if verified_using is None else verified_using
        external_reference = [] if external_reference is None else external_reference
        external_identifier = [] if external_identifier is None else external_identifier
        check_types_and_set_values(self, locals())

Is there a reason verified_using, external_reference and external_identifier cannot be initialized as None?
If they do need to be empty arrays instead of None, can't that be done by making the argument default = []?
Is there a reason the core dataclasses are at the top level instead of in a core directory?

We ensured that list-valued properties are always lists so we don't have to do the check for None every time we want to iterate over them (iterating over an empty list is completely fine and just does nothing as one would expect when the property is not set).
Mutable types like lists can't be used as default arguments as they would be shared between different instances of the class. See for example here.
The design decision to have core classes on top level was made because core is not really a profile on its own and so that users don't have to search for the most vital entry point into the model.

I have a few questions:

Is this issue currently in the working phase?
If we make them None or Optional, will it affect serialization? If yes, how can we resolve this issue?

Hi @harshkasat. The way I understand it, this issue a question, not a direct call for work. As I answered the question in my previous post and there has been no activity for half a year, I think this issue can be closed.
Please tell me if you disagree, and we can reopen it again.


Doesn't load .php_cs.dist

PHP-CS-Fixer 2.0 introduced the ability to keep a .php_cs.dist file in the project root; which would be loaded if there was no .php_cs file (https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/v2.0.0/UPGRADE.md#config-file)
However, atom-php-cs-fixer seems to ignore the .php_cs.dist file; I suspect its trying to hard load .php_cs, or forces its own config?

:+1: awesome


feat: support fsharp projects

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
747

Relevant Lines:
849

💛  - Coveralls


InfluxDB exporter should support URL end-point

Is your feature request related to a problem? Please describe.
From Slack:
Steve S  3:19 PM
for the influxdb exporter is it possible to just pass a URL?

Chris Grindstaff  3:21 PM
@Steve S can you give an example of what you want? you mean instead of decomposing the url into an addr and port?

Steve S  3:25 PM
correct - we have a large scale configuration behind load balancer  (so we’re not hitting a single host).

Chris Grindstaff  3:28 PM
make sense - I'll create an issue to track - if you're interested this is the line of code to change if you want to give it a try

Describe the solution you'd like
Allow me to exporter to a URL instead of address and IP

The copy paste from slack didn't carry the URL:
https://github.com/NetApp/harvest/blob/fc433fecae2c445e65c9465a3166b2960552e962/cmd/exporters/influxdb/influxdb.go#L108

Can the code be updated so we can set the url without (bucket, org, token).
influxdb version 1.8 does not have (bucket, org, token) and a bunch of people are still on the 1.8.* release because the 2.* has big changes.
If the config accepted the following... then I assume we would get support for the older version of influxdb.
Exporters:
  influx:
    use_insecure_tls: true # < also perhaps nice to have
    url: https://influxdb.my:8086/write?db=mydb&u=myuser&p=mypassword&precision=s

also you would need to make the token optional. and skip setting the Authorization header for the above influxdb1.8 fix to work.

we would also need password/username to work with 1.8, right?

in influxdb1.8 you can include the username and password in the url u= and p= else you can pass the creds using http basic authentication.
https://influxdb.my:8086/write?db=mydb&u=myuser&p=mypassword&precision=s

@steverweber we'll add InfluxDB 1.8 support to the list. As you noted, we only support 2.0 at the moment. Are you interested in trying to add this?

@cgrinds sure i'll make a PR tomorrow.

this is working on my end.
https://github.com/steverweber/harvest/commit/bb988c880cb9c8f0d694f24342b4e3d16c3da4c0
with config like:
Exporters:
  influx:
    exporter: InfluxDB
    url_raw: https://influxdb.XXXX:8086/write?db=netapp&u=admin&p=XXXX&precision=s
    addr: ''
    bucket: ''
    org: ''
    token: ''

thoughts?

Thanks @steverweber I took a look at your changes. Instead of introducing another key/value named url_raw what if we change url to be that instead? There would be no processing for url, just take whatever is entered for it, similar to what you're doing with url_raw

Suggested change in PR #115 - does that cover your use case @steverweber?

Glad you came to that conclusion. I tested your change and the code works on my end for influxdb1.8.


Adding label to a pod causes error

Internal reference: SURE-5824
Reported in 2.7.0
Issue description:
Adding label to a pod via Rancher GUI causes error.
Repro steps:
step 1
Create a pod by kubectl: $ kubectl run nginx-pod --image=nginx
step 2

Add a Label to the pod via Rancher GUI:
Cluster Manager -> local cluster -> Workload -> pods -> Edit Config -> Pod tab -> Labels & Annotations
Push Add Label button: key=foo, value=bar
Save

error occurs (error.png)

Pod "nginx-pod" is invalid: spec: Forbidden: pod updates may not change fields other than `spec.containers[*].image`, `spec.initContainers[*].image`, `spec.activeDeadlineSeconds`, `spec.tolerations` (only additions to existing tolerations) or `spec.terminationGracePeriodSeconds` (allow it to be set to 1 if it was previously negative)
core.PodSpec{
... // 11 identical fields
NodeName: "<IP_ADDRESS>",
SecurityContext: &{},

ImagePullSecrets: nil,
+ ImagePullSecrets: []core.LocalObjectReference{},
Hostname: "",
Subdomain: "",
SetHostnameAsFQDN: nil,
Affinity: nil,
+ Affinity: &core.Affinity{},
SchedulerName: "default-scheduler",
Tolerations: { {Key: "node.kubernetes.io/not-ready", Operator: "Exists", Effect: "NoExecute", TolerationSeconds: &300}
, {Key: "node.kubernetes.io/unreachable", Operator: "Exists", Effect: "NoExecute", TolerationSeconds: &300}},
... // 11 identical fields
}

@scures saw this when trying to update environment variables in Epinio:
Pod "epinio-server-5d5845745d-49ccj" is invalid: spec: Forbidden: pod updates may not change fields other than spec.containers[].image, spec.initContainers[].image, spec.activeDeadlineSeconds, spec.tolerations(only additions to existing tolerations) orspec.terminationGracePeriodSeconds (allow it to be set to 1 if it was previously negative)
This may be fixed in 2.7.2 elsewhere via Epinio work but this could be tied to a Helm deployment done not in the UI originally.

Ticket #8074 - Test Results - ✅
With Docker on a single-node instance:
Reproduced w/ Rancher v2.7.0:

Fresh install of rancher v2.7.0
Navigate to Cluster Explorer > KubeShell of local cluster
Using kubectl imperative command, create a pod:

kubectl run <pod_name> --image=nginx

Once pod is created, navigate to Cluster Explorer > Workloads > Pods, find the pod and edit config
Via RancherUI, add a new pod label and then save
Reproduced - [see screenshot]

Verified w/ Rancher v2.7-211409c9a689d8ee4d801ed1bce1d887b0fb4b00-head:

Fresh install of rancher v2.7-head
Navigate to Cluster Explorer > KubeShell of local cluster
Using kubectl imperative command, create a pod:

kubectl run <pod_name> --image=nginx

Once pod is created, navigate to Cluster Explorer > Workloads > Pods, find the pod and edit config
Via RancherUI, add a new pod label and then save
Verified - pod label successfully added via Rancher UI


how to create paramater value ?

hello,
i need to create sql with paramater value. like below
INSERT INTO tenant (tenant_name, notes) VALUES (:tenant_param, :notes_param)
can the sql builder create the values part without quotes ?
because the resulted query is :
INSERT INTO tenant (tenant_name, notes) VALUES ('':tenant_param'','' :notes_param'')
so the dataset can not find the paramater tenant_param as it is quoted
Thank you

And what is the source code that generates this query?


allow nested keyword lists for :skip_fields

It would be great to be able to annotate why certain fields are being skipped. I think the easiest way to do this is code would to be able to do something like:
assert_values_for(
  expected: user_params,
  actual: user_from_db,
  fields: fields_for(User),
  skip_fields: [
    db_generated_values: [
      :id,
      :inserted_at,
      :updated_at
    ],
    keys_different_from_params: [
      :phone_number,
      :some_random_thing
    ]
  ]
)

This is doable with minimal changes, I think (flatten and take the values?) and will allow the calls to read as better documentation and may even highlight to the coder which keys should be intentionally tested after.

Is there something specific that you're trying to address here?

I think the initial syntax you put forward is more a e s t h e t i c, and my questions were more to probe than anything else.
I do wonder what else we could do with the keys we would (otherwise) throw away. Are there places where this information could be useful in test output?
For example, let's say one of the keyword lists' contents gets programmatically generated (ala fields_for/1, Map.split/2, Enum.split_with/2, or similar). Does an empty-list value for one of these keys result in:

an error
a warning
silent tolerance

Ah, great call out. I honestly hadn't thought that far. You're right though. I think that it's highly unlike that someone would intentionally add an empty list (is there a valid use case for that?) and so it would only happen if something is erroneously generated. At that point, we are doing a service to raise an error.


Dead link + missed documentation for cta

http://prebid.org/dev-docs/adunit-reference.html#adUnit.mediaTypes.native.cta

Thanks for pointing this out. See what you mean. Checking with @mjacobsonny .

@mjacobsonny confirmed that cta is a string. Will make the update.

Fixed. thanks again @ifyapishore


Update supported OS list with current OS versions

The supported OS list doesn't list several of the current OS's. Have Windows Server 2022, and Ubuntu 20.04 and 22.04 been tested and if so can this document be updated to reflect that?

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

ID: 54f35593-3d7b-a56d-0fba-593eb9b3032d
Version Independent ID: b1e5fe22-ef19-b992-0fea-7e6848c37845
Content: Azure VM Image Builder overview - Azure Virtual Machines
Content Source: articles/virtual-machines/image-builder-overview.md
Service: virtual-machines
Sub-service: image-builder
GitHub Login: @sumit-kalra
Microsoft Alias: sukalra

@jchancellor-ms
Thanks for your feedback! We will investigate and update as appropriate.

@jchancellor-ms
I'm going to assign this to the document author so they can take a look at it accordingly.
@sumit-kalra
Can you please check and add your comments on this doc update request as applicable.

Thanks for your contribution to our documentation
We sincerely apologize for the delayed response. Unfortunately, we have been unable to review this issue in a timely manner. However, we are making overall enhancements to our content. We are closing this issue for now as there has been no activity for a while. If you feel that the problem persists, please respond to this issue with additional information.
?
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Some mistakes when calling jax.vjp

While running some test with jax.jvp and jax.vjp and running this specific test in reference to issue #5226 I'm trying to reproduce the error that should appear which is that the matrices are not squared. I do receive an error but not the one I was expecting this issue can be seen in both Jupyter notebooks and local terminal alike.

Trying to resolve this I ran into this output which is the reason I am opening this issue. I added a second pair of parenthesis to enclose the tuple and I get this output:

the highlighted parenthesis are the ones I added for better understanding. Why does it create the first DeviceArray but not the second one?

Hello - if you take a look at the call signature for jax.vjp you'll see that the expected return type is a tuple (primals_out, vjpfun), where primals_out is a DeviceArray and vjpfun is a callable (function) that evaluates the vjp.
Here's a quick demonstration:
import jax
def f(x):
  return x * 2

n = 10
key = jax.random.PRNGKey(0)
x = jax.random.normal(key, (n,))
x_out, f_vjp = jax.vjp(f, x)

print(x_out)
# [-0.744222    0.5284621  -0.36505547 -1.4736396  -0.8806077  -0.30428854
#  -1.3427072  -1.1817284   1.4633775   1.134605  ]
print(f_vjp(x)[0])
# [-0.744222    0.5284621  -0.36505547 -1.4736396  -0.8806077  -0.30428854
#  -1.3427072  -1.1817284   1.4633775   1.134605  ]

Does that answer your question?

I'm going to close this because I think the question was answered, and due to inactivity, but please reopen (or open new issues) as needed!

I'm going to close this because I think the question was answered, and due to inactivity, but please reopen (or open new issues) as needed!


VisUI: FileChooser crashes if last used location no longer exists

FileChooser was pointed at a removable drive, disconnected the drive (while the file chooser was closed) on next launch it crashed as the drive was no longer a valid path. (FileChooser.java:853) Ecountered on one of the 1.1.4-SNAPSHOT's.
(No full stack trace due to difficulty in copying the data at the moment).

Can't reproduce on 1.1.5-SNAPSHOT.

Reproduced on 1.1.5-SNAPSHOT
2016-07-23 15:33:29:0322 ERROR Thread[LWJGL Application,5,main]
Stack trace:java.lang.IllegalStateException: Provided directory does not exist!
com.kotcrab.vis.ui.widget.file.FileChooser$20.run(FileChooser.java:875)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
java.lang.Thread.run(Thread.java:745)
Selected a file from a SD card (hit okay). The file chooser closed, removed the SD card from the computer then selected another button which requests the file chooser. As it is reusing the instance/trying to return to the last used folder which no longer is a valid path it crashes.

From your first post I assumed you meant crashing between app launches, that's why you should provide stacktrace and/or reproduction steps, anyways it's fixed now.


Remove references to "xaps"

There is a lot of references to xaps, especially and visibly in datasource defintions, in freeacs. Must be removed, since its difficult to know what its all about.

This is very intrusive change seen from the inside. But we dont need this naming legacy. So the gist of it is as it stands now to rename XAPS and XAPSUnit and all other "xaps" code to Freeacs and FreeacsUnit accordingly. Might also just call it ACS and ACSUnit

Closed in #99


Don't monitor Cinder Volume LVs for disk util.

The disk utilisation monitoring will monitor cinder volumes if they are
attached to an instance and you run the MaaS play again.
We need to avoid this by ensuring that the model of moniitored disks is
not 'VIRTUAL-DISK'.
Closes-Issues: #38
(cherry picked from commit 57493ffb7ac11633635680dcaf772fbbde565ba2)

This failed with
17:11:46 failed: [jrpcaio-1a6_ceph_mon_container-c2663b69] => (item=/etc/ceph/ceph.client.admin.keyring) => {"checksum": "da39a3ee5e6b4b0d3255bfef95601890afd80709", "dest": "/etc/openstack_deploy/ceph_fetch/febf87de-7c04-4cf1-b48a-4fe6e7280c9a/etc/ceph/ceph.client.admin.keyring", "failed": true, "file": "/etc/ceph/ceph.client.admin.keyring", "item": "/etc/ceph/ceph.client.admin.keyring", "md5sum": "d41d8cd98f00b204e9800998ecf8427e", "remote_checksum": "a0b39d5a583c7283f011dca776a723053ac99b0a", "remote_md5sum": null}

over at this location.

Thats an unrelated issue.

@andymcc sorry that my comment wasn't clear. I was trying to illustrate that point exactly.

recheck - failed on ceph race that has been fixed.

recheck - curl timed out

@d34dh0r53 why was this closed?

@sigmavirus24 I deleted the kilo-r11.1.0 branch, can you retarget the backport for kilo?


Small numbers interpreted wrongly

When loading 'small' numbers (i.e. my 5 minute load averages), tessera displays these wrongly:
renderer: flot:

renderer: graphite:

If you're referring the y-axis label, it's not incorrect - it's just a different format that you're getting from Graphite by default. The values are rendered by d3.format with metric prefixes --  400m is the same as 0.40.

Fair point, however, in cases like this or others where small datapoints are being tracked it would be useful if it was possible to 'ignore' the default formatter.

We can add the ability to specify the y-axis format string, but you'll still be limited by what you can do with  a d3 format string. Implementing different formats according to value ranges is pushing into a level of complexity that the current editing UI can't really handle, however.


Crash with alsa-lib 1.2.3-1 on ArchLinux

After upgrading and rebuilding polybar with alsa-lib 1.2.3 when I try to use the mouse to adjust volume causes the bar crash
Expected behavior:
Volume adjust without bar crashing
Actual behavior:
Volume not adjusted and bar crash
Was it working before?

Did you also experience this bug in an earlier version of polybar?
No

To Reproduce
[bar/tst]
modules-right = volume

[module/volume]
type = internal/volume

format-volume-underline = ${colors.underline}

label-volume-foreground = ${colors.foreground-alt}

format-volume = <label-volume> <bar-volume>
label-volume = 

format-muted-prefix = " "
format-muted-foreground = ${colors.foreground-alt}
label-muted = --
format-muted-underline = #DCDCDC

bar-volume-width = 8
bar-volume-foreground-0 = #FF
bar-volume-foreground-1 = #FF
bar-volume-foreground-2 = #FF
bar-volume-foreground-3 = #FF
bar-volume-foreground-4 = #FF
bar-volume-foreground-5 = #FF
bar-volume-foreground-6 = #FF
bar-volume-gradient = false
bar-volume-indicator = |
bar-volume-indicator-font = 2
bar-volume-indicator-foreground = #AA5000
bar-volume-fill = ─
bar-volume-fill-font = 2
bar-volume-empty = ─
bar-volume-empty-font = 2
bar-volume-empty-foreground = ${colors.foreground-alt}

Try to adjust volume using mouse scroll
Polybar Log
double free or corruption (fasttop)
[1]    8562 abort (core dumped)  polybar tst

Environment:

WM: i3
Distro: ArchLinux
Output of polybar -vvv:

polybar 3.4.3

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Build type: Release
Compiler: /usr/bin/c++
Compiler flags: -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -Wall -Wextra -Wpedantic -O3 -DNDEBUG
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

Trace
Starting program: /codes/polybar/build/bin/polybar tst
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
notice: Parsing config file: /home/.config/polybar/config
[New Thread 0x7ffff63c5700 (LWP 8710)]
warn: No monitor specified, using "eDP1"
warn: internal/volume is deprecated, use internal/alsa instead
[New Thread 0x7ffff1bc4700 (LWP 8711)]
[New Thread 0x7ffff13c3700 (LWP 8712)]
[New Thread 0x7ffff0bc2700 (LWP 8713)]
warn: No fonts specified, using fallback font "fixed"
notice: Loaded font "fixed" (name=DejaVu Sans, offset=0, file=/usr/share/fonts/TTF/DejaVuSans.ttf)
warn: Dropping unmatched character  (U+e04e) in ''
[New Thread 0x7fffd3e4e700 (LWP 8722)]
[Thread 0x7fffd3e4e700 (LWP 8722) exited]
double free or corruption (fasttop)

Thread 5 "polybar" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff0bc2700 (LWP 8713)]
0x00007ffff757d355 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff757d355 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff7566853 in abort () from /usr/lib/libc.so.6
#2  0x00007ffff75c0878 in __libc_message () from /usr/lib/libc.so.6
#3  0x00007ffff75c7d3a in malloc_printerr () from /usr/lib/libc.so.6
#4  0x00007ffff75c9035 in _int_free () from /usr/lib/libc.so.6
#5  0x00007ffff7c9e806 in ?? () from /usr/lib/libasound.so.2
#6  0x00007ffff7c9724e in snd_config_update_free_global () from /usr/lib/libasound.so.2
#7  0x0000555555ab7be0 in polybar::alsa::mixer::mixer (this=0x7fffdc063290, mixer_selem_name=...,
    soundcard_name=...) at /home/codes/polybar/src/adapters/alsa/mixer.cpp:23
#8  0x000055555598c64f in polybar::modules::alsa_module::input (this=0x555555c58100, cmd=...)
    at /home/codes/polybar/src/modules/alsa.cpp:236
#9  0x000055555593824f in polybar::controller::process_inputdata (this=0x555555c391c0)
    at /home/codes/polybar/src/components/controller.cpp:398
#10 0x0000555555937d32 in polybar::controller::process_eventqueue (this=0x555555c391c0)
    at /home/codes/polybar/src/components/controller.cpp:348
#11 0x0000555555951923 in std::__invoke_impl<void, void (polybar::controller::*)(), polybar::controller*> (
    __f=@0x555555c9de10: (void (polybar::controller::*)(polybar::controller * const)) 0x555555937b30 <polybar::controller::process_eventqueue()>, __t=@0x555555c9de08: 0x555555c391c0)
    at /usr/include/c++/10.1.0/bits/invoke.h:73
#12 0x0000555555951865 in std::__invoke<void (polybar::controller::*)(), polybar::controller*> (
    __fn=@0x555555c9de10: (void (polybar::controller::*)(polybar::controller * const)) 0x555555937b30 <polybar::controller::process_eventqueue()>) at /usr/include/c++/10.1.0/bits/invoke.h:95
#13 0x00005555559517d5 in std::thread::_Invoker<std::tuple<void (polybar::controller::*)(), polybar::controller*> >::_M_invoke<0ul, 1ul> (this=0x555555c9de08) at /usr/include/c++/10.1.0/thread:264
#14 0x000055555595178e in std::thread::_Invoker<std::tuple<void (polybar::controller::*)(), polybar::controller*> >::operator() (this=0x555555c9de08) at /usr/include/c++/10.1.0/thread:271
#15 0x00005555559516b0 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (polybar::controller::*)(), polybar::controller*> > >::_M_run (this=0x555555c9de00)
    at /usr/include/c++/10.1.0/thread:215
#16 0x00007ffff795ab74 in std::execute_native_thread_routine (__p=0x555555c9de00)
    at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:80
#17 0x00007ffff7713422 in start_thread () from /usr/lib/libpthread.so.0
#18 0x00007ffff7640bf3 in clone () from /usr/lib/libc.so.6

I can't reproduce this, even with the exact same alsa-lib version. Does this happen consistently for you?
The function that actually causes the double free (snd_config_update_free_global) looks to me like it's safe to call it multiple times because it sets the things it's deleting to NULL. But the documentation for it isn't great, so I don't really know for sure whether we are using it wrong.

Oh, also how does your sound setup look like? Do you use alsa together with pulseaudio?

I can't reproduce this, even with the exact same alsa-lib version. Does this happen consistently for you?

Yes, always happens with alsa-lib 1.2.3-1 version. Earlier today I performed a downgrade to alsa-lib 1.2.2-1 and since then it has been working as intended.

Oh, also how does your sound setup look like? Do you use alsa together with pulseaudio?

I do use pulseaudio but I'm not sure about what you mean with "sound setup" . If you want me to run any command that may help the debug process I'll do.

I was able to reproduce this now. I needed to have the pulseaudio-alsa package installed for the crash to occur.
This is gonna be a pain to debug since the crash doesn't happen in our code. If anyone has experience with the libasound api, I'd appreciate the help. The problem is probably that we somehow use the libasound api wrong.

It happens to me after some updates in archlinux. It happens while moving volume au and down with the mouse. I get this exact errror:
double free or corruption (fasttop) [1]    8562 abort (core dumped)  polybar tst

I also got the same error, also on arch.
double free or corruption (fasttop)
[1]    119486 abort (core dumped)  polybar topbar

A quick workaround was setting type to internal/pulsaudio, it doesnt fix the bug, but at least my bar is usable

If you use pulseaudio, you should use the pulseaudio module anyway since the alsa module doesn't always work that well together with pulse (for example muting/unmuting).

For what it's worth I'm also using this on arch with an alsa/pulseaudio setup, except the behavior occurs when muting/unmuting—it'd work once before crashing, maybe a second time if you gave it time. This behavior is new after a full system upgrade to alsa-lib 1.2.3-1, so whatever path muting/unmuting hits is affected as well.

I'm hitting the same error on fedora:
double free or corruption (fasttop)
Aborted (core dumped)

alsa-sof-firmware-1.5-1.fc32.noarch
alsa-ucm-1.2.3-8.fc32.noarch
alsa-plugins-pulseaudio-1.2.2-1.fc32.x86_64
alsa-lib-1.2.3-8.fc32.x86_64
alsa-utils-1.2.3-3.fc32.x86_64
polybar-3.4.3-1.fc32.x86_64

I also got the same error with module type = internal/alsa

in Void, having pulseaudio installed on system crashes polybar when volume sliders are changed even if using/adjusting with alsa module. removing entirely pulseaudio fixes at least the crash.

It started crashing for me too after upgrading to alsa-lib-<IP_ADDRESS>-1. To reproduce it, all I have to do is mute, unmute, and mute again (module/alsa). It crashes at the second mute.

Seems to be fixed by upgrading to alsa-lib-<IP_ADDRESS>-1.
Fixed for me at least.
Can mute, unmute, mute unmute. Increase/decrease volume

Upgrading to alsa-lib-<IP_ADDRESS>-1 in Arch seems to have fixed it :)
(@flowHater you can use pacman to install alsa-lib, it's in extra. Also, you should do -Syu instead of just -Sy)

I can also confirm that version <IP_ADDRESS> fixes this. I did a bisect between <IP_ADDRESS> and 1.2.3 and it was commit https://github.com/alsa-project/alsa-lib/commit/20e003a63d14edabd59e40e5d0b8ed2f11f8c9b8 that fixed it. The issue that the commit was supposed to fix is also consistent with the issue here, so I believe this is actually fixed and I will close this issue.


Context not compiling in Typescript

Creating singletons signals but to avoid index.js:354 computations created outside a createRootorrender will never be disposed warning wanted to move to a context provider however using typed version of example won't build.
import { createState, createContext } from 'solid-js';

export const CounterContext = createContext([{ count: 0 }, {}]);

export interface CounterProviderProps {
    count?: number
}
export function CounterProvider(props: CounterProviderProps) {
    const [state, setState] = createState({ count: props.count || 0 }),
        store = [
            state,
            {
                increment() {
                    setState("count", c => c + 1);
                },
                decrement() {
                    setState("count", c => c - 1);
                }
            }
        ];

    return (
        <CounterContext.Provider value= { store } >
        { props.children }
        < /CounterContext.Provider>
  )
}

Getting these errors

Wierd it's like it doesn't recognize it as JSX. Are you using the a .tsx extension? Or set the tsconfig to allow JSX in non-TSX files. I can dig a bit more into this later but that's what I'm reading from the errors. It's treating JSX <> as some sort of TypeScript operator either for generics or namespace or something.

It is in a .tsx file.  I had made a shim to avoid a host of other errors
declare namespace JSX {
    interface IntrinsicElements {
        [elemName: string]: any;
    }
}

It sounds like something very unusual is going on and not sure how to pinpoint it. I made a simple webpack build with TS if that helps: https://github.com/ryansolid/solid-ts-webpack

@delaneyj What should we do with this issue? Did you make some progress with getting a working setup?

yeah we are good now after the discussion on gitter with the addition of ForIn


Safari Support?

It looks like there might be a visualization / display issue with Safari...
I see the UI at http://git-school.github.io/visualizing-git/ on Chrome 52.0.2743.116 and Firefox 47.0.1, but on Safari 9.1.3 (11601.7.8) I get a blank screen.
This is on Mac OS X 10.11.6.

Thanks @IanLee1521! We noticed this just today ourselves. I'll be taking a look shortly.

@IanLee1521 Should be good to go! You may need to clear your caches.

Looks good! Thanks!
Side note, I love this tutorial, this repo just made the entire tutorial for me. Thank you!

@IanLee1521 That's great to hear, thank you! So glad you found it useful!! :)


Larastan is getting confused with db enums and a bunch of if statements.

level: 4
version: latest release available
let's say I have a db enum field, with this possible string values:
$field = 'A'|'B'|'C';
and the following code, I will write the output and where I think the error is:
            \PHPStan\dumpType($field); // correct output  'A'|'B'|'C'
            if (... unrelated comdition ...) {
                \PHPStan\dumpType($field);  // correct output  'A'|'B'|'C'
                if ($field != 'C') {
                    \PHPStan\dumpType($field);  // correct output  'A'|'B'
                    return false;
                }
            }
            \PHPStan\dumpType($field); // correct output  'A'|'B'|'C'
            if ((... unrelated comdition ...) {
                \PHPStan\dumpType($field); // bad output 'C' 👈🏻
                if ($field != 'C'') {
                    \PHPStan\dumpType($field); // bad output *NEVER*
                    return false;
                }
            }

Imo the errors comes from the 4th dumpType.

Thank you for your report!
Please share the full source code of the second if with us. (which may be related)

both ifs are something like this
$type = []; // either human or animal or both
if(\in_array('human', $type, true) ...
if(\in_array('animal', $type, true) ...

If this does not help, I can try next week to make a demo project

Without the source code it is not possible to help you how $field is reduced to 'C'

This doesn't seem to be related to Larastan.


Akinator package

What type of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactor
[ ] Documentation
[ ] Not Sure?

Does this PR introduce breaking changes?

[ ] Yes
[x] No

List any relevant issue numbers:
Description:
Implements the Akinator game.

Hello @Imperator26,
It looks awesome! Regarding the answer in the same context, this is where this feature request  will be useful.
Because for the moment, it only works according to hard coded answer from the user such as "yes", "no", etc. And in English only.

Hello @Imperator26,
It looks awesome! Regarding the answer in the same context, this is where this feature request  will be useful.
Because for the moment, it only works according to hard coded answer from the user such as "yes", "no", etc. And in English only.

Yep that would be perfect

Hello !
You should consider renaming your akinator package into a games package, and keeping your module inside.
It would be better for those who want to add other games.
Thanks for contributing !

Due to the complete new rewrite with the new skills architecture. This PR does not work and an Akinator skill has been built with the new architecture already :smiley:


Transaction is not current for this thread

I am getting Transaction is not current for this thread. I have integrated Hibernate ORM and OGM, though Neo4J OGM is running as different REST service.
org.neo4j.ogm.exception.TransactionManagerException: Transaction is not current for this thread
at org.neo4j.ogm.session.transaction.DefaultTransactionManager.commit(DefaultTransactionManager.java:109) ~[neo4j-ogm-core-2.1.5.jar:na]
at org.neo4j.ogm.transaction.AbstractTransaction.commit(AbstractTransaction.java:85) ~[neo4j-ogm-api-2.1.5.jar:na]
at org.neo4j.ogm.drivers.http.transaction.HttpTransaction.commit(HttpTransaction.java:78) ~[neo4j-ogm-http-driver-2.1.5.jar:na]
at org.springframework.data.neo4j.transaction.Neo4jTransactionManager.commit(Neo4jTransactionManager.java:50) ~[spring-data-neo4j-4.1.2.RELEASE.jar:na]
at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:518) ~[spring-tx-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:292) ~[spring-tx-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) ~[spring-tx-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673) ~[spring-aop-4.3.13.RELEASE.jar:4.3.13.RELEASE]

OGM Version used: 2.1.5
Java Version used: 1.8
Neo4J Version used: 3.2.1
Bolt Driver Version used (if applicable): 3.0.3

Could you please provide some additional code snippets and explain what you are trying to do.
Besides this it is not a good approach to mix the OGM versions like you do with core 2.1.5 and OGM Bolt driver 3.0.3.

I got same issue.
call asyncGraph(...)
codes:
`private void asyncGraph(Account from, Account to, Transfer t) {
neo4jImportExecutor.submit(() -> syncGraph(from, to, t));
}
private void syncGraph(Account from, Account to, Transfer t) {
Session session = sessionFactory.openSession();

AccountNode fromNode = buildNode(from);
AccountNode toNode = buildNode(to);
....

session.save(fromNode);
session.save(toNode)
session.save(t);

}`

I found that is a bug
while query error occurs, transaction rollback and remove thread local Transaction
public void rollback(Transaction transaction) {
		if (transaction != getCurrentTransaction()) {
			throw new TransactionManagerException("Transaction is not current for this thread");
		}

		for (Object object : ((AbstractTransaction) transaction).registeredNew()) {
			((Neo4jSession) session).context().reset(object);
		}

		TRANSACTION_THREAD_LOCAL.remove();
	}

and throw another exception,in the next exception catch block, transaction rollback agin
if (transactionRequired && newTransaction) {
                tx.rollback();
                tx.close();
                throw e;
 }

now, thread-local transaction is already gone, getCurrentTransaction() is null
if (transaction != getCurrentTransaction()) {
	throw new TransactionManagerException("Transaction is not current for this thread");
}

replace txManager of Neo4jSessionwith custom txmanager works

Do you still see this problem in Neo4j-OGM or did you already upgrade to a more current version?

Thanks for your response.


What this PR does / why we need it:

See https://github.com/openshift-knative/hack/pull/94 for more.
Reverts #520

/hold for https://github.com/openshift-knative/hack/pull/94 and the ci config to be merged.

Nothing was generated https://github.com/openshift/release/pull/45963 is empty. Unholding.

/unhold


Add hacbs integration-service apiexport to support kcp

The code come from https://github.com/dirgim/infra-deployments/tree/hacbs-1150-test by @dirgim
Signed-off-by: Hongwei Liu<EMAIL_ADDRESS>

I can't add reviewer on this PR. So @dirgim @johnbieren could you take a look at this PR as well? Thanks!

@hongweiliu17 I would merge this PR, the PR with update of integration-service should be created automatically when it will be merged.

@Michkov agreed, merging this PR.

Currently integration-service pod is failing on:
1.6656468401220474e+09	INFO	setup	Looking up virtual workspace URL	{"api-export-name": ""}
1.6656468401531231e+09	INFO	setup	api-export-name is empty - listing	{"api-export-name": ""}
1.6656468401569276e+09	ERROR	setup	error looking up virtual workspace URL	{"api-export-name": "", "error": "error listing APIExports: apiexports.apis.kcp.dev is forbidden: User \"system:serviceaccount:integration-service:default\" cannot list resource \"apiexports\" in API group \"apis.kcp.dev\" at the cluster scope"}
runtime.main
	/usr/local/go/src/runtime/proc.go:250
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1519c37]

goroutine 1 [running]:
main.main()
	/workspace/main.go:107 +0x5b7

That's about configuration in integration-service repo. But this code is working so Approving.

@hongweiliu17 note that at this apiexport permission should be easy to fix in the integration-service repo (and iirc is already part of your PR). However, if integration-service is like release-service (it seems to be in most fashions), the controller is not going to be able to see any of the CRDs in the APIExport. I thought this had to do with our controllers using a cache, but it does not. I am still trying to figure this one out and I will tag you and Kruno on PRs when I do

@johnbieren Thanks! Could you also paste some error log then I can learn it?

1.6656638818202572e+09 ERROR controller-runtime.source if kind is a CRD, it should be installed before calling Start {"kind": "Release.appstudio.redhat.com", "error": "no matches for kind \"Release\" in version \"appstudio.redhat.com/v1alpha1\""} The Release CRD is not used in our cache and is part of our APIExport (via apiresourceschema, not permission claim), so something is up. I just don't know what yet


[en] Delete repeated paragraphs

Signed-off-by: Gao Qian<EMAIL_ADDRESS>

After looking at the original page, https://kubernetes.io/docs/concepts/cluster-administration/flow-control/ ,
I don't believe these are duplicates and should not be removed
/hold

I agree. I'm going to close this PR @gaogao101 because I'm confident the paragraphs should stay.
If you want to open a new PR to highlight what's different (seats vs requests), we'd definitely consider making a highlighting change: I can see the potential for confusion.
/close


[WIP] [SPARK-8117] [SQL] Move codegen implementation into Expression

This PR move codegen implementation of expressions into Expression class itself, make it easy to manage.
It introduces two APIs in Expression:
def gen(ctx: CodeGenContext): GeneratedExpressionCode
def genCode(ctx: CodeGenContext, ev: GeneratedExpressionCode): Code

gen(ctx) will call genSource(ctx, ev) to generate Java source code for the current expression. A expression needs to override genSource().
Here are the types:
type Term String
type Code String

/**
 * Java source for evaluating an [[Expression]] given a [[Row]] of input.
 */
case class GeneratedExpressionCode(var code: Code,
                               nullTerm: Term,
                               primitiveTerm: Term,
                               objectTerm: Term)
/**
 * A context for codegen, which is used to bookkeeping the expressions those are not supported
 * by codegen, then they are evaluated directly. The unsupported expression is appended at the
 * end of `references`, the position of it is kept in the code, used to access and evaluate it.
 */
class CodeGenContext {
  /**
   * Holding all the expressions those do not support codegen, will be evaluated directly.
   */
  val references: Seq[Expression] = new mutable.ArrayBuffer[Expression]()
}

Merged build triggered.

Merged build started.

Test build #34224 has started for   PR 6660 at commit 3ff25f8.

Test build #34224 has finished for   PR 6660 at commit 3ff25f8.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34227 has started for   PR 6660 at commit e57959d.

Test build #34227 has finished for   PR 6660 at commit e57959d.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class EvaluatedExpression(var code: Code,
class CodeGenContext
abstract class CodeGenerator[InType <: AnyRef, OutType <: AnyRef] extends Logging

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #34229 has started for   PR 6660 at commit 8c6d82d.

Test build #34229 has finished for   PR 6660 at commit 8c6d82d.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build finished. Test FAILed.

Merged build started.

Test build #34231 has started for   PR 6660 at commit c5fb514.

Test build #34231 has finished for   PR 6660 at commit c5fb514.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code,
class CodeGenContext
abstract class CodeGenerator[InType <: AnyRef, OutType <: AnyRef] extends Logging

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34232 has started for   PR 6660 at commit 12ff88a.

Test build #34232 has finished for   PR 6660 at commit 12ff88a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code,
class CodeGenContext
abstract class CodeGenerator[InType <: AnyRef, OutType <: AnyRef] extends Logging

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34247 has started for   PR 6660 at commit 2344bc0.

Test build #34247 has finished for   PR 6660 at commit 2344bc0.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code,
class CodeGenContext
abstract class CodeGenerator[InType <: AnyRef, OutType <: AnyRef] extends Logging

Merged build finished. Test PASSed.

One idea I have is to use numeric type for the null term. In that case, for a lot of expressions we no longer need conditional branches.
To compute null term: && becomes &, || becomes |, xor becomes ^.

BTW - I sent a pull request against your branch with some review comments.

Merged build triggered.

Merged build started.

Test build #34294 has started for   PR 6660 at commit b5d3617.

Test build #34294 has finished for   PR 6660 at commit b5d3617.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code,
class CodeGenContext
abstract class CodeGenerator[InType <: AnyRef, OutType <: AnyRef] extends Logging

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #34306 has started for   PR 6660 at commit 02262c9.

Test build #34306 has finished for   PR 6660 at commit 02262c9.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code, var nullTerm: Term, primitiveTerm: Term)
class CodeGenContext

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34308 has started for   PR 6660 at commit 86fac2c.

Merged build triggered.

Merged build started.

Test build #34313 has started for   PR 6660 at commit e03edaa.

Merged build triggered.

Merged build started.

Test build #34320 has started for   PR 6660 at commit bad6828.

Test build #34308 has finished for   PR 6660 at commit 86fac2c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code, var nullTerm: Term, primitiveTerm: Term)
class CodeGenContext

Merged build finished. Test PASSed.

High-level comment: we should have a checklist / guide at the top of codegen/package.scala which gives some general guidelines on how to write codegen code (e.g. code formatting, uniqueness of variable / term names, etc.)

Test build #34313 has finished for   PR 6660 at commit e03edaa.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code, var nullTerm: Term, var primitiveTerm: Term)
class CodeGenContext

Merged build finished. Test PASSed.

Test build #34320 has finished for   PR 6660 at commit bad6828.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code, var nullTerm: Term, var primitiveTerm: Term)
class CodeGenContext

Merged build finished. Test PASSed.

Merged build triggered.

Merged build triggered.

Merged build started.

Merged build started.

Test build #34357 has started for   PR 6660 at commit f42c732.

Test build #34357 has finished for   PR 6660 at commit f42c732.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code, var isNull: Term, var primitive: Term)
class CodeGenContext
case class Pow(left: Expression, right: Expression)
case class Rint(child: Expression) extends UnaryMathExpression(math.rint, "ROUND")
case class ToDegrees(child: Expression) extends UnaryMathExpression(math.toDegrees, "DEGREES")
case class ToRadians(child: Expression) extends UnaryMathExpression(math.toRadians, "RADIANS")

Merged build finished. Test FAILed.

Test build #34358 has started for   PR 6660 at commit 9adaeaf.

Test build #34358 has finished for   PR 6660 at commit 9adaeaf.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class GeneratedExpressionCode(var code: Code, var isNull: Term, var primitive: Term)
class CodeGenContext
case class Pow(left: Expression, right: Expression)
case class Rint(child: Expression) extends UnaryMathExpression(math.rint, "ROUND")
case class ToDegrees(child: Expression) extends UnaryMathExpression(math.toDegrees, "DEGREES")
case class ToRadians(child: Expression) extends UnaryMathExpression(math.toRadians, "RADIANS")

Merged build finished. Test FAILed.

Now that https://github.com/apache/spark/commit/5e7b6b67bed9cd0d8c7d4e78df666b807e8f7ef2 has merged, can this be closed?