[Docker] Add checkout cmd line to install last stable version

With this, you sould add tag in docker hub for each version.

Now, there is 2 tags for docker images:

stable: for the latest stable release
latest: for the development version

Both images can be downloaded from Docker Hub, see https://github.com/fguillot/kanboard/blob/master/doc/docker.markdown#use-the-stable-version


Pipelines: De-emphasize ContainerOp in documentation

Many pages of our documentation use ContainerOp in examples.
ContainerOp usage has a number of problems, so we should probably de-emphasize it and replace with components wherever possible.
The main problem of ContainerOp is that it does not define a reusable component. By creating an instance of ContainerOp, the user creates an ad-hoc task object. That task is not a component. It cannot be shared or loaded. Some information is lost or missing (e.g. the input names and types). Even though the ContainerOp remains as an underlying implementation of a Task  entity, the users should be discouraged from instantiating ContainerOp themselves. Instead they should use load_component* and func_to_container_op.
The user should create a component definition. It takes about the same number of lines of code.
106 - Creating components from command-line programs
The initial tutorials should start with using external/existing components, then python components (func_to_container_op -> component.yaml) and container components (component.yaml).
See the Organize Pipelines samples and tutorials in an ordered curriculum for a proposed structure and order of tutorials.
/cc @sarahmaddox @amygdala

Should this remain open?...


New version: ROCAnalysis v0.3.2

Registering package: ROCAnalysis
Repository: https://github.com/davidavdav/ROCAnalysis.jl
Created by: @davidavdav
Version: v0.3.2
Commit: 45dbe46dfe381f0796f160c3d73c9ddb1003c95d
Reviewed by: @davidavdav
Reference: https://github.com/davidavdav/ROCAnalysis.jl/commit/45dbe46dfe381f0796f160c3d73c9ddb1003c95d#commitcomment-49197429

@davidavdav can you please see the message above?
[noblock]

This doesn't work obviously

This is probably one of the most frustrating experiences with Julia ever

I'm not sure I understand what you're talking about
[noblock]

Dear Mosè,
I think I am giving up on this, this process just is too complicated and
untransparent for me.  I've tried to trigger the version registration from
numerous commits, but I still get these errors that I fixed.
—david
On Wed, Apr 7, 2021 at 1:30 AM Mosè Giordano @.***>
wrote:

@davidavdav https://github.com/davidavdav can you please see the
message above?
[noblock]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JuliaRegistries/General/pull/33652#issuecomment-814497951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJ6DVZJTH4VUJOLLZYGVZLTHOKPXANCNFSM42OZLIOQ
.

--
David van Leeuwen (다빛, 大卫, دافد)

Well, you should register this revision, but you spelled @JuliaRegistrator wrong. I have a saved reply for this, alternatively you can look to JuliaHub
[noblock]

I'm not sure I understand what you're talking about
[noblock]

The automerge details give an error, Error: Dependency "SpecialFunctions" does not have a compat entry that has an upper bound but I fixed this.
How am I getting this registrator to look at this commit?  I've tried to trigger the registrator from that commit, but nothing happens.

Well, you should register this revision, but you spelled @JuliaRegistrator wrong. I have a saved reply for this, alternatively you can look to JuliaHub
[noblock]

Thanks for your patience and for pointing this out to me!
[noblock]


docs: handle deprecation warning wrt. emojis

Summary of Changes
Update Material for Mkdocs configuration to handle a deprecation warning.

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

v0.17.0
GitHub release

Your semantic-release bot :package::rocket:


feature/JENKINS-35828 - status colors

Related to issue #JENKINS-35828
Summary of Changes:

Add some generic classes for setting fill, background-color or color of an element in either normal or light theme color, based off result/status name. This should help us avoid having to remap our brand colors to numerous different classes.


[FIX] fix price error

Release Checklist
Pre-Release

[ ] Check migrations

No database related infos (sqldb-xxx)
Impact on GS (new/removed columns)

[ ] Check for linter errors (in PR)
[ ] Test basic user operations (on DFX services)

Login/logout
Buy/sell payment request
KYC page

Post-Release

Test basic user operations
Monitor application insights log

auf DEV getestet, dieses Update behebt das Problem 👌


Exploring a "cargo-script" in rustup

Would appreciate feedback on my research and proposal.

Closing as this was more intend to ping people.  Let's continue any discussion in the linked issue or its repo

FYI I've finally got back to this and created a Pre-RFC

@epage Thanks - I missed this previously!
Looks interesting and useful, nice work driving this.
Is the initial proposal here to bundle this by default when a user installs rust using rustup, or would it be an optional, additional install?

Bundled by default. As I called out, there is still room for rustscript for extra caching and --expr flag (as I'm reserving that for the repl).
Btw I caught that windows bug because I ported the test scripts to Rust. Feel free to checkout my tests directory to see how I do it with snapbox.


Use base64 Credential-IDs

compatibility with hex maintained by regex-if-fork

A general comment: We have a https://github.com/solokeys/solo-python/blob/master/CHANGELOG.md, PRs should be accompanied by an entry there (under "Unreleased"), especially when the public facing interface is modified.

Okay I was not aware that PRs enter into the changelog


[SPARK-10648] Proposed bug fix when oracle returns -127 as a scale to a numeric type

In my environment, the precision and scale are undefined in the oracle database, but spark is detecting them to be 0 and -127 respectively.
If I understand those two values correctly, they should never logically be defined as less than zero, so the proposed changes should correctly default the precision and scale instead of trying to use erroneous values.
If there is a valid use case of a negative precision or scale, then I can re-work this to test for the exact 0 AND -127 case and handle it appropriately.

Can one of the admins verify this patch?

So I understand, the goal of this patch is that if an invalid value is returned (e.g. a precision or scale <= 0), then the defaults are used yes?

Yes, that is the intention. Is this the proper way to address that issue?
On Wed, Sep 16, 2015, 5:14 PM Holden Karau<EMAIL_ADDRESS>wrote:

So I understand, the goal of this patch is that if an invalid value is
returned (e.g. a precision or scale <= 0), then the defaults are used yes?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/8780#issuecomment-140896861.

I'm not super sure on that, one question would be if this is reasonable behavior for all databases or only Oracle.

I'm not sure if oracle can be associated with anything reasonable, but sometimes you have to play the hand you are dealt. :)
I can only answer your question with a question... Would there ever be a use case in the Decimal() class where the precision and/or the scale would be set to a negative value?
If not, then I'd have to imagine that this patch makes the intention of the code more accurate across the board. If yes, then I may have to explore an oracle-only type of patch, which may or may not ever be committed back, depending on it's usefulness to the community.
I'd have to assume that there isn't a use case for negative values given the way precision and scale are used and defined, but you'll have to forgive any ignorance on my part as I'm still fairly new to scala. I hadn't even browsed the source for spark until about one week ago. I'm still in the alpha stages of even testing spark in general, so while it's seemingly solved the problem for me in my testing, I could easily be overlooking something.

Actually scale can be negative. It just means the number of 0s to the left of decimal point.
For example, for number 123, precision = 2 and scale = -1, then 123 would become 120.

(I actually don't know if Spark implements this correctly -- we should test it)

That is exactly what I was afraid of. Would the patch make more sense to only check precision for a zero value? Does it ever make sense to have a precision of zero (or less than zero for that matter)? Could we safely enforce defaults if precision is zero (or less) regardless of scale? That would solve my problem still, hopefully without compromising functionality for everyone else.

That should work.
On Sep 18, 2015, at 7:15 AM, Travis Hegner<EMAIL_ADDRESS>wrote:
That is exactly what I was afraid of. Would the patch make more sense to
only check precision for a zero value? Does it ever make sense to have a
precision of zero (or less than zero for that matter)? Could we safely
enforce defaults if precision is zero (or less) regardless of scale? That
would solve my problem still, hopefully without compromising functionality
for everyone else.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/8780#issuecomment-141462484.

Working on a new patch... Would it ever be possible to have a case where precision is 0 (essentially undefined), but scale is still intentionally set? Or is it that setting the precision is required in order to set a scale?

They would all be null then. It doesn't make sense to have precision < scale.

 Is that something that should be tested for, and overridden with defaults if true?
This also would fix my problem without DB specific hacks.

Oh actually - let me correct it.
If scale is positive, then precision needs to >= scale.
If scale is negative, then precision can be anything (>0).
I'm not sure if precision == 0 makes any sense, since that effectively means null value.

OK, after looking at this a little further, it seems that DecimalType.bounded() should be called regardless of precision and scale values in JDBCRDD.scala, and then let the .bounded() method validate the precision and scale values. If it finds invalid values, it can return defaults, or throw an exception, depending on which condition is met. I'm going to move in that direction for this.
 Wouldn't it be invalid to have a precision = 10, but a scale = -20? Wouldn't that always result in a null value, or am I still completely interpreting precision and scale incorrectly?

precision = 10 and scale = -20 should be fine.
scala> Seq((121, 134)).toDF("a","b")
res0: org.apache.spark.sql.DataFrame = [a: int, b: int]

scala>  import org.apache.spark.sql.types._
import org.apache.spark.sql.types._

scala> res0.select($"a".cast(DecimalType(2, -1))).show()
+------------------------+
|cast(a as decimal(2,-1))|
+------------------------+
|                  1.2E+2|
+------------------------+

scala>

scala> res0.select($"a".cast(DecimalType(1, -2))).show()
+------------------------+
|cast(a as decimal(1,-2))|
+------------------------+
|                    1E+2|
+------------------------+

I'm making sure the new version builds, but here are the rules:
  private[sql] def bounded(precision: Int, scale: Int): DecimalType = {
    if (precision <= 0)
      DecimalType.SYSTEM_DEFAULT
    else if (scale > precision)
      DecimalType(min(precision, MAX_PRECISION), min(precision, MAX_SCALE))
    else
      DecimalType(min(precision, MAX_PRECISION), min(scale, MAX_SCALE))
  }

For both Decimal and Numeric types in JDBCRDD.scala, it now will call the DecimalType.bounded() regardless the values of precision and scale. This allows all of the validity checks to happen inside of that function. The rules above are simply if precision is invalid, return a SYSTEM_DEFAULT. if scale > precision then force scale = precision. And all else retains previous behavior.
Once I verify that it builds and runs, I will update the pull request. Does this look accurate?

So any thoughts on merging this?

cc @davies to take a quick look

I met this problem before, and actually it's not spark that detect them to be 0 and -127, but JDBC. My solution is just adding a OracleDialect to handle this sepcial case:
case object OracleDialect extends JdbcDialect {
  override def canHandle(url: String): Boolean = url.startsWith("jdbc:oracle")
  override def getCatalystType(
      sqlType: Int, typeName: String, size: Int, md: MetadataBuilder): Option[DataType] = {
    if (sqlType == Types.NUMERIC && typeName == "NUMBER" && size == 0) Some(LongType) else None
  }
}

......

JdbcDialects.registerDialect(OracleDialect)

So if we want to support oracle officially, we can add OracleDialect into spark like we did for mysql, postgre, etc. Or @travishegner you can try OracleDialect to fix your problem without changing spark code.

The problem with Oracle is that you can define numbers without providing precision or scale:
column_name NUMBER  (this is the only case that doesn't work very well for Oracle support)
	has a precision of 0 and scale of -127 in JDBC ResultSetMetaData
	"If a precision is not specified, the column stores values as given."  http://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#i16209

column_name NUMBER(10)
	has a precision of 10 and scale of 0 in JDBC ResultSetMetaData

column_name NUMBER(10,2)
	has a precision of 10 and scale of 2 in JDBC ResultSetMetaData

I think the best solution is to handle this in a OracleDialect since this is a quirk of Oracle.  I've done that for my own code but it would be nice to have two changes in Spark:

Access to more of the metadata fields (e.g. scale) in the dialect.getCatalystType call (currently the precision is provided but the scale is not)
Change line 406 in JDBCRDD to support creating a Decimal without a predefined precision/scale.  It seems that this would work in cases where there is a consistent
precision/scale for a field and also this Oracle nuance where the precision/scale differ per row.

For now, this is what I've done in my own OracleDialect:
object OracleDialect extends JdbcDialect {
  override def getCatalystType(sqlType: Int, typeName: String, size: Int, md: MetadataBuilder): Option[DataType] = {
	// Handle NUMBER fields that have no precision/scale in special way because JDBC ResultSetMetaData converts this to 0 procision and -127 scale
	if (sqlType == Types.NUMERIC && size == 0) {
	  // This is sub-optimal as we have to pick a precision/scale in advance whereas the data in Oracle is allowed
	  //  to have different precision/scale for each value.  This conversion works in our domain for now though we
	  //  need a more durable solution.  Look into changing JDBCRDD (line 406):
	  //    FROM:  mutableRow.update(i, Decimal(decimalVal, p, s))
	  //    TO:  mutableRow.update(i, Decimal(decimalVal))
	  Some(DecimalType(DecimalType.MAX_PRECISION, 10))
	} // Handle Timestamp with timezone (for now we are just converting this to a string with default format)
	else if (sqlType == -101) {
	  Some(StringType)
	} else None
  }
}

@cloud-fan @bdolbeare @davies I'm certainly open to doing this in an oracle specific way if that is what is required. I was simply hoping to solve my problem while simultaneously making the whole project more robust. I completely understand if you don't believe that it's the right direction. Thanks for looking into it with me!

@travishegner looks like it is best to just do it in the oracle dialect.

@travishegner Will you have time to continue your work? I think our resolution is to create a oracle dialect and we automatically register it (see https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/jdbc/JdbcDialects.scala).

Test build #1986 has started for PR 8780 at commit d11141c.

Test build #1986 has finished for PR 8780 at commit d11141c.

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

Please see PR #9495 for the oracle dialect solution proposed above.


Issue: The program closes when you try to close the empty tab.

Steps:

open "Option" menu (Tools>Options)
activate the function "Exit the application when the last tab is closed" in "General" tab
confirm the change and close the menu
click on "Close", "Close all" or "[X]" button
Actual Result: the program is closed
Additional Information:
https://drive.google.com/open?id=0BzzoMjyImOxLSkpITFY2MjZOZXc

Hmm, which part of "Exit the application when the last tab is closed" is difficult to understand?


Minimum required version of "six" package doesn't work

https://github.com/prkumar/uplink/blob/cca6f787dfb5c40a5093182560699ad7d56da159/setup.py#L18
Upon importing uplink, when I have uplink 0.9.5 installed with version 1.12.0 of the "six" package, I am seeing an error like:
AttributeError: module 'six.moves' has no attribute 'collections_abc'
Upgrading "six" to version 1.13.0 works though.

What version of Python are you using?

I noticed this when installing to a python 3.7.12 environment

Should be fixed with v0.9.6


Binary Comparison in meshopt_generateVertexRemap fails because of padding bytes

My Vertex struct is like so:
struct Vertex {
    glm::vec3 pos; // sizeof(glm::vec3) == 16
    glm::vec3 color; // sizeof(glm::vec3) == 16
    glm::vec2 texCoord; // sizeof(glm::vec2) == 8
    // invisible 8 bytes of padding
} // sizeof(Vertex) == 48

The binary comparison for 2 Vertexes with the same values for pos, color, and texCoord is still failing because the 8 padding bytes contain different garbage data, but are still being compared as part of hashUpdate4 which looks at the sizeof the entire struct.
I think it would be worth documenting in meshopt_generateVertexRemap comment that this behavior can occur, and for the user to explicitly zero those padding bytes. OR you could provide separate stride size and struct size parameters to avoid comparing those bytes at all.
edit: the parameter vertex_size and vertex_stride are already separate in VertexHasher, but vertex_size is passed for both from meshopt_generateVertexRemap. I was able to fix the issue by adding an overload with the vertex_stride parameter.

Actually now I'm worried about sizeof(glm::vec3) being 16. I feel like it should be 12, which means there are 4 bytes of padding in between the vec3's also, which could theoretically also have random garbage. Maybe I should just memset the whole struct before use.

But to memset 0 before setting any struct values I would lose my nice one liner to generate a new Vertex, which looks like this:
    vertexes.emplace_back(Vertex{a, color, {0, 0}});

It appears that other people have been aware of this problem before - padding isn't required to be initialized when you use initializer lists https://gustedt.wordpress.com/2012/10/24/c11-defects-initialization-of-padding/
A topic discussed in the comments is to use operator== for the struct instead of memcmp. In my code I define both operator== as well as a std::hash implementation for use with std::set and std::multiset. This was used to deduplicate vertices in a different place. But you have opted to instead use a custom hash based on binary representation. Do you think there would be a significant performance loss if I hacked up the code to just use std::set with my defined operators instead?

So this is definitely worth calling out in documentation. I'll look through the functions that use structural equality and add the relevant notes.
As you note, while it's possible to specify the stride separately, it doesn't fully solve the problem because padding may appear between the elements. In your case you could use glm::packed_vecN types to work around the issue.
Alternatively you can of course use std::unordered_set if you already are defining equality/hashing. This isn't a great addition to the library for a few reasons (C ABI & FFI concerns around callbacks, performance), but vertex remapping is one of the simpler algorithm the library provides so you should feel free to replace it with alternative implementations if it's inconvenient.


IVT - Invalid Start bite - Unable to integrate.

Describe the bug
It is not possible to integrate the device. An error pops up that the IP address or password is wrong.
To Reproduce
IVT --> HTTP --> Enter data --> ERROR
Expected behavior
Don't get an error.
Screenshots

Version

HA version? - Latest
HA Bosch component version? - Latest
Python Bosch HTTP client version? - Dont Know

** Debug SCAN **
** IMPORTANT **
Go to Developer tools in Home Assistant, choose Service tab and choose bosch.debug_scan
Not Found
Additional context

I changed the password, just numbers and letters in lower case, I can log into the app but not here. The next question is what, see screen, is the token.

I've tried the top long number with and without dashes, but it doesn't work.

The same here! App works, HA don't. The update of today changes - nothing! Not able to integrate; "device is null" 😩

Added the device several times. Now it is on HA available. But only two entities: dhw1 and hc1.

Ok, its working...... Password must be the same as PWD into your mobile app (logicaly) and that TOKEN is "Password" from that sticker from LAN module.
Token is in format "xxxx-xxxx-xxxx-xxxx" WITH !!! dashes...

Strange ... my Token is without dashes.
@hcm183   try to remove the Bosch Thermostat integration, then restart ha and do a fresh install.

New installation did it! Don't know how. But only success is important😁.
Thanks for the Support!
HCM
Am 4. Dezember 2023 20:41:58 MEZ schrieb honikos @.***>:

Strange ... my Token is without dashes.
@hcm183   try to remove the Bosch Thermostat integration, then restart ha and do a fresh install.
--
Reply to this email directly or view it on GitHub:
https://github.com/bosch-thermostat/home-assistant-bosch-custom-component/issues/351#issuecomment-1839354320
You are receiving this because you were mentioned.
Message ID: @.***>


Tooltips With Bounds considering also screen bounds (window frame)

:boom: Breaking Changes

N/A

:rocket: Enhancements

now it consider window frame. If chart is only half visible the tooltip will adjust to window frame and not get cut.

:memo: Documentation

N/A

:bug: Bug Fix

N/A

:house: Internal

N/A

Thanks for this @manuelrocha88. I want to take some time to understand the problem a bit more before I merge this. First thought is it makes sense. Just want to be safe and make sure I fully grasp why this is a win for everyone 😄

@hshoff I give you a shortcut on the issue analysis.
From @vx/tooltip package if we make only use of the Tooltip component we get something like this:

As We can see the tooltip gets out of the chart bounds and get cut.
If we replace the Tooltip component by the TooltipWithBounds we get a different, and success, reposition of the Tooltip and it's inside the chart bounds, as we can see at this picture:

But, this TooltipWithBounds package is only considering the chart bounds. What If the chart has part of it outside of the bounds of the frame screen (A small screen?!)?
You get something like this:

If you see the bubble is half visible only. When I make my mouse over it the Tooltip gets cut because is still inside chart bounds but outside frame screen bounds.
With the change I have on PR you will get something like this:

As you can check the Tooltip now is inside the bounds of chart and frame screen.

Sounds good


Fix typo for stream in README.md

Found a typo in readme where it said stream#pause() instead of stream.pause()

Actually we should change both to Stream# as # indicates instance methods. https://stackoverflow.com/questions/736120/why-are-methods-in-ruby-documentation-preceded-by-a-hash-sign

Interesting, I thought it was a typo. Thanks for taking the time to look up an explanation.
If I understand it correctly, by writing Stream#pause() readers will know that they should do
const stream = redis.scanStream();
stream.pause()

Instead of something like this?
const pausedStream = redis.scanStream().pause();

Updated according to comment and all checks are green


TreeView - Drag&Drop

Feature request type
Enhance component
Component name
TreeView
Is your feature request related to a problem?
no
Describe the solution you'd like
It would be nice to have a Drag&Drop option in the TreeView component.
Maybe it can be achieved with the MudDropZone.
I think, the best way to achieve this is to implement, alongside with the visual behavior, an event called "OnDrop".
The following subjects should be evaluated:

OnDrop can be intercepted
OnDrop should be cancelable (undo action)
OnDrop should deliver information about where it was dragging from and where it is dropped into (Node objects)
OnDrop should be working within async manner (That way, we can implement remote side operations, such as reordering a datasource via REST)
If dropping a node object into another leaf node that hasn´t been loaded (ServerSide data) - it should be removed
Should the dropping behavior follow the same principles and rules as the MudDropZone component? Or do we have niche cases?
Should a dragged node expand a leaf node while it is hovering on it and the leaf node is in collapsed state?

What do you think about the feature? Please let me know.
Have you seen this feature anywhere else?
No response
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Telerik UI for Blazor has this functionality  and I'd be interested in having it available in MudBlazor.

The best I've been able to do as a workaround with MudBlazor is to include buttons to move nodes up & down in the tree, see here for a sample:
https://try.mudblazor.com/snippet/cEcRElbPJcenyCMX
For this task, it's a problem MudTreeView uses a HashSet for items, which is explicitly unordered. I've worked around this by using a list underneath and rebuilding the HashSet from the list when needed.
Doesn't feel like a great solution, if anyone has a better option I'd be interested to see it.

I think you can somehow place the DropZone into the TreeView component, but I don´t think this is perforamce wise a good choice. The TreeView component seems pretty basic and you would end up creating x DropZone components for each node. Also this would result into an entire rework of the TreeView. I definitely need this feature but I doubt if I could get it working "properly" - also in near future.

I started out trying to get something working with the DropZone component but it didn't seem like it was going anywhere promising so I fell back to the workaround above. This is good enough for my needs right now, but it would be great to have a better solution at some point.

+1 for this feature

+1 for this feature

+1 here as well.

+1 please add this

+1 for the feature

a drag and drop options for the Mudtreeview is necessary.

+1 for this feature

+1


Updated Dataframe.to_excel and Dataframe.to_latex

For both, header accepts boolean or a list of strings.

Looking into this, it seems that we are not supporting Series.to_excel() and Series.to_latex(), so we should fix these here as well.
Can you take to_excel() and to_latex() out of frame.pyi and then use just a common stub in core/generic.pyi ?

Can you take to_excel() and to_latex() out of frame.pyi and then use just a common stub in core/generic.pyi ?

Hey @Dr-Irv,
To be honest, I'm not sure what I had to do other than removing to_excel() and to_latex() from frame.pyi because they both were already present in generic.pyi. Did I misunderstand something?

To be honest, I'm not sure what I had to do other than removing to_excel() and to_latex() from frame.pyi because they both were already present in generic.pyi. Did I misunderstand something?

No, but I wanted to make sure that the stubs in generic.pyi were the same as the ones in frame.pyi, and they were, so we're all good on that front.


[FEATURE] add hover effect on social icons

Description
added color changing and scaling effect on the social media icons.
Fixes #77
Type of change

[x] New feature (non-breaking change which adds functionality)

Test Required (Yes / No)

No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

Style

Enhanced hover effects for social media icons in the footer for better visual interaction.
Adjusted copyright text formatting for improved readability.

Refactor

Unified import statements to use double quotes for consistency.

Thank you but pleas ask it to be assigned first. other 2 people already requested it

Thank you but pleas ask it to be assigned first. other 2 people already requested it

Sorry about that; I'll remember next time

it's o, I will keep this PR for a while in case the other people don't work on it

already done by #77


kbfs_ops: avoid a deadlock on concurrent TeamNameChanged calls

Deadlock:

First call to KBFSOps.TeamNameChanged takes opsLock.
Calls go FolderBranchOps.TeamNameChanged().
Releases opsLock.
FolderBranchOps.TeamNameChanged() takes headLock.
Second call to KBFSOps.TeamNameChanged takes opsLock.
Calls FolderBranchOps.getRootNode, which blocks trying to acquire headLock.
FolderBranchOps.TeamNameChanged() calls KBFSOps.changeHandle().
KBFSOps.changeHandle() tries to acquire opsLock.
DEADLOCK.

Instead, make sure we don't hold opsLock when calling getRootNode.
Issue: KBFS-2565

thanks for fixing it so quickly. we'll look into the other issue of why two calls get fired. i think i have a theory


Fix bidi mirror handling

What does the pull request do?

When FlowDirection was RightToLeft paired brackets were not appropriately mirrored. This PR fixes that.
What is the current behavior?

Paired brackets are not mirrored and therefore are displayed in the wrong order.
What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Fixes: #8991

You can test this PR using the following package version. 11.0.999-cibuild0023943-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0023971-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0024039-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0024090-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Code completion + linter

Maybe I am doing something wrong. When I do a DO it auto completes, however, the linter is given the wrong indentation on it.

I take it you have the linter enabled in the settings. The errors are correct there.
Do you have an existing rpglint.json file somewhere? Use this command to open up the lint configuration file it is using.

Also, read these notes on the linter: https://github.com/halcyon-tech/vscode-rpgle#linter


Added command for retrieving world news

Integrate News API into Personal Robot Butler Script
Overview
This pull request introduces the integration of a news API into the existing "Alexis - YOUR PERSONAL ROBOT BUTLER" Python script. The update allows users to fetch the latest news headlines via a simple voice or text command.
Changes

News API Integration: Added a function get_latest_news to fetch news from a selected news API service.
Command Handling: Extended the main command loop to include a "news" command, triggering the news fetching functionality.

Usage
Users can now retrieve the latest news by inputting the command "news" in the script interface.

Looks good, thanks


nrfutil: python37Packages -> python3Packages

Clean up build so it tracks latest python3Packages,
instead of being pinned to python37Packages.
Nrfutil builds and works fine with python38 on Darwin and Linux.
Signed-off-by: Sirio Balmelli<EMAIL_ADDRESS>

Result of nixpkgs-review pr 112894 at c280c158 run on x86_64-linux 1

1 package built:

nrfutil

Result of nixpkgs-review pr 112894 at c280c158 run on aarch64-linux 1

1 package built:

nrfutil


Improvement for k8s.io/docs/tasks/configure-pod-container/assign-cpu-resource/

As a cluster admin,
I need to understand what happens when CPU requests and limits are not set at the pod or namespace level,
So that I can better understand k8s CPU scheduling when pods will attempt to consume more CPU than is available.
As a cluster admin,
I need to understand how the above scenario impacted when autoscaling is enabled
So that I can properly administer namespace and pod requests and limits within a large landscape.

Seems like a valid thing to want to document to fully understand the behavior. Looking at the page currently there is this section, which part is inadequate for your first point, is it that there is:

No explicit references to CPU requests at Pod/Namespace level and only container level
No explicit mention of what happens if a (for example) Pod with no limit could exceed the CPUs available on the Node?

The second point seems a valid thing to document for cluster autoscaling:
Proposed Solution (for second point): Document Pod behavior for these four scenarios:

Cluster Autoscaling Enabled
Pod CPU Requests Enabled

Yes
Yes

Yes
No

No
Yes

No
No

It sounds like readers would also like to learn about the behavior with HorizontalPodAutoscaler and VerticalPodAutoscaler.
@ddycus what did you have in mind when your reported this?


Attach DataType to GhidraClass

Is your feature request related to a problem? Please describe.
While I am aware that this enhancement isn't actually fixing the problem, it is the best I could come up with that would require a minimal amount of changes to the way this is currently handled.
It is currently possible for VariableUtilities::findOrCreateClassStruct to return the wrong Structure and thus __thiscall functions will use the wrong structure for the this parameter. I have been aware of this for quite some time but since it is a result of something I am doing I have neglected to open an issue as a bug for this. This can occur as a result of a user moving the Structure around in the program's DataTypeManager. If you have two GhidraClasses, one 'Dummy' in the global namespace and another in 'DummyNamespace', VariableUtilities::findOrCreateClassStruct may return the Structure for the GhidraClass in the DummyNamespace when the Structure for GhidraClass in the global namespace is requested. This is a result of how DataTypeUtilities::findDataType handles the global namespace.
Describe the solution you'd like
The ability to attach a Structures UniversalID to the GhidraClass and a method to retreive the UniversalID or datatype from the GhidraClass to prevent this from occuring.
Describe alternatives you've considered
Keep demangled structures where they are within the DataTypeManager and leave everything unsorted?
Additional context
From analyzing libstdc++ this error occurs for 45 out of 256 -> 17.6% of GhidraClasses in the library. These results were obtained from the reporting of the method which may be seen here. Each class that passed through this were added to a set and each one which returned the wrong structure was added to a different set. The resulting sizes of the two sets were then compared for the above results.

@astrelsky Until we overhaul how we handle classes so that the class namespace and associated class data type location are tied together, you can use program.setPreferredRootNamespaceCategoryPath(String categoryPath) so that it will attempt to find and use class structures from the given preferred data type manager folder instead of  picking the first it finds.

@astrelsky Until we overhaul how we handle classes so that the class namespace and associated class data type location are tied together, you can use program.setPreferredRootNamespaceCategoryPath(String categoryPath) so that it will attempt to find and use class structures from the given preferred data type manager folder instead of picking the first it finds.

Sounds good. It would probably be a good idea to tackle #1431 as well when this is overhauled.


Pull in redacted font license

https://github.com/christiannaths/Redacted-Font
Inside the fonts directory.

I'll add this in with my next push.

that was quick 👍


disable PR push to quay

We can't safely push the image to quay because there is no way to securely provide login credentials for PR Travis jobs. This is only possible if PR is opened from the branch in the same repository.
https://docs.travis-ci.com/user/encryption-keys/

replaced by https://github.com/openshift/odo-init-image/pull/68


Integrate Clair

Portainer is awesome, thanks for creating it!
Clair is a project for static analysis of vulnerabilities in Docker containers and it looks like perfect match to Portainer.
Wouldn't it be a good idea to integrated Clair into Portainer so that there would be a section for launching the vulnerability scan and seeing reports?

Agree it looks good... we couldnt integrate into Portainer because of license restrictions, but we may be able to integrate with this.. will give it some thought
Rgds,
Neil Cresswell
On 29/09/2017, at 7:00 AM, Mart Sõmermaa <notifications<EMAIL_ADDRESS>wrote:
Portainer is awesome, thanks for creating it!
Clairhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_coreos_clair&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=Mhq5kfutrs1TrEYtXBV9UqRKvYC4yt8hkJrWD0oanAQ&s=VYEhzPbGbynP_jTtGBWjxJOQQHFuRUzRuKQZ1sCAcgQ&e= is a project for static analysis of vulnerabilities in Docker containers and it looks like perfect match to Portainer.
Wouldn't it be a good idea to integrated Clair into Portainer so that there would be a section for launching the vulnerability scan and seeing reports?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_1246&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=Mhq5kfutrs1TrEYtXBV9UqRKvYC4yt8hkJrWD0oanAQ&s=M1gqd6GmU6iXJMChNfjoXpjw9Ljac9n9laFwIxTpqdo&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlYWyXKh9q3OzG5uHixIC9WbdTiGgks5sm96agaJpZM4PnqBJ&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=Mhq5kfutrs1TrEYtXBV9UqRKvYC4yt8hkJrWD0oanAQ&s=9pbjJWTXg3QkHsEeyhS476D3Oj29UksMDxzrIYTz7ug&e=.

Thanks @mrts ! Never heard of Clair before, looks great.
I'm going to close this issue and refer it inside #713 which I think is related. Feel free to comment in #713

Thanks @deviantony, better to keep the discussion in one place!


Add passive_columns gem to the list

thanks @headmandev! sorry for delay :(

No, It is fine. No worries! Thank you for the merge @ekremkaraca


is graphql spring boot compatible with spring security?

Dear all as the title said
is graphql spring boot compatible with spring security?
and if there is a sample for this

Does the discussion on #29 help?

Thank you for pointing to that issue,
I will try it today with Oauth2 and let you know

@hkashlan did that work for you?

Sorry but I didn't work on it yet, I went back to restful API :(


Http Integration Tests: Create tests to support HTTP(6)

This issue involves creating the below test cases for HTTP as well:
Source: integration_tests/commands/async/

hdel_test.go
hello_test.go
hget_test.go
hgetall_test.go
hlen_test.go
hset_test.go

Steps:

Create the corresponding tests for these commands in integration_tests/commands/http.
Use set_test.go as a reference, and how to alter the input and output to match JSON structures from RESP.
Run the tests and fix issues with command parsing in HTTP.

If you need to do anything custom to support HTTP, let @pratikpandey21 @lucifercr07 know.

@pratikpandey21  Please assign this to me.

I don't have the permissions to assign you, but please go ahead and start @N3XT14

Hello @N3XT14,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

Hi @arpitbbhayani .
I was working on playground web so missed on this.  Have started working on it.

@JyotinderSingh @lucifercr07
Why do we have below behaviour with reserved keywords. The print statements are from the eval function of HSET. Isn't it supposed to follow one pattern?
Am i missing something here?
{
			name: "HSET multiple fields and HDEL them",
			commands: []HTTPCommand{
				{Command: "HSET", Body: map[string]interface{}{"key": "key", "field1": "value1", "field2": "value2"}},
				{Command: "HSET", Body: map[string]interface{}{"key": "key1", "field": "field3", "value": "value1"}},
				{Command: "HSET", Body: map[string]interface{}{"key": "key1", "field3": "value1", "field4": "value3"}},
				{Command: "HSET", Body: map[string]interface{}{"key": "key2", "field3": "value1", "value": "value3"}},
				// {Command: "HDEL", Body: map[string]interface{}{"key": "key", "field1": "value1", "field2": "value2"}},
			},
			expected: []interface{}{TWO, TWO},
		},

Starting the test server on port 8083
{"level":"info","addr":":8083","message":"HTTP Server running"}
=== RUN   TestHDEL
=== RUN   TestHDEL/HSET_multiple_fields_and_HDEL_them
Hello, in evalset
HashMap SET
field2 => value2
field1 => value1
HashMap End SET
0 2 float64
Hello, in evalset
HashMap SET
field3 => value1
HashMap End SET
1 1 float64
Hello, in evalset
HashMap SET
field3 => value1
field4 => value3
HashMap End SET
2 1 float64
Hello, in evalset
3 ERR wrong number of arguments for 'HSET' command string
--- PASS: TestHDEL/HSET_multiple_fields_and_HDEL_them (0.00s)
--- PASS: TestHDEL (0.00s)
PASS
{"level":"error","error":"empty JSON object","message":"Error parsing HTTP request"}
{"level":"info","message":"Skipping AOF dump."}
{"level":"info","message":"Http test server encountered an error: http: Server closed"}
ok      github.com/dicedb/dice/integration_tests/commands/http  (cached)

Hello @N3XT14,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.


Location of a JSON value in the submitted text

Is there any way to retrieve the starting location of a JSON value in the original text (line and column)? This would be particularly useful when the parsed value is JSON compliant but incorrect with respect to the host application. In such case, I would like to be able to notify to the user where the error occurred in its text. For instance, let an interval declared in a JSON file as follow:
{
          ...
  { "lower" : 1.0, "upper" : -1.0 },
          ...
}

I would like to print that the interval is invalid and where it is defined. This would help the user to fix this issue.

It's not currently possible. I also don't think it's worth adding because it would add unnecessary overhead to each value for a very limited use case.


Wrong label for Riyal saudi in french

Describe the bug
The label of the "Riyal Saudi" is written "Riayl saudi" for french at different parts of the code:
https://github.com/Microsoft/Recognizers-Text/blob/02bd15fd07cc6696b8b7c7e03d7f6e81eb22448d/Python/libraries/recognizers-number-with-unit/recognizers_number_with_unit/resources/french_numeric_with_unit.py#L113
https://github.com/Microsoft/Recognizers-Text/blob/02bd15fd07cc6696b8b7c7e03d7f6e81eb22448d/Java/libraries/recognizers-text-number-with-unit/src/main/java/com/microsoft/recognizers/text/numberwithunit/resources/FrenchNumericWithUnit.java#L127
https://github.com/Microsoft/Recognizers-Text/blob/02bd15fd07cc6696b8b7c7e03d7f6e81eb22448d/JavaScript/packages/recognizers-number-with-unit/src/resources/frenchNumericWithUnit.ts#L13
https://github.com/Microsoft/Recognizers-Text/blob/02bd15fd07cc6696b8b7c7e03d7f6e81eb22448d/.NET/Microsoft.Recognizers.Definitions/French/NumbersWithUnitDefinitions.cs#L129
https://github.com/Microsoft/Recognizers-Text/blob/4b1ca7d44f89c2b75e9c7ce40dabf3a058a1898e/Patterns/French/French-NumbersWithUnit.yaml#L178

Thanks for catching it! Issue was due to a type on the YAML file.
I'm closing this issue as there is already an approved PR that solves it.


Single player

None of the single player stuff is showing up on the rdmap like dinosaurs bones, dream catchers, etc . Iam clicking on them but when I go to the map nothing is on it

That is iconography, not the markers. Iconography is the text or icons on the map that appears on high zoom lvl like this:

That is iconography, not the markers. Iconography is the text or icons on the map that appears on high zoom lvl like this:


BuildAcquireLeasesCommand fails; _az_func_ChangeVersion is NULL

Inserting changes into a function's lease table is failing because _az_func_ChangeVersion  is null:
Failed to check for changes in table '[dbo].[Endeavor]' due to exception: Microsoft.Data.SqlClient.SqlException. Exception message: Cannot insert the value NULL into column '_az_func_ChangeVersion', table 'test.az_func.Leases_207b01944e72935c_544720993'; column does not allow nulls. UPDATE fails.

Digging through the code, it looks like a null _az_func_ChangeVersion is one of the conditions to pull changes:
BuildGetChangesCommand, lines 791-815 SQL:

                DECLARE @result int;
                EXEC @result = sp_getapplock @Resource = '_az_func_Trigger',
                            @LockMode = 'Exclusive',
                            @LockTimeout = 30000
                IF @result < 0
                BEGIN
                    RAISERROR('Unable to acquire exclusive lock on _az_func_Trigger.
That query results in:

So there seems to be a mismatch on the query that pulls changes (which allows _az_func_ChangeVersion to be null) and the lease table definition (where _az_func_ChangeVersion  cannot be null).
This is the lease table definition:
CREATE TABLE [az_func].[Leases_207b01944e72935c_544720993](
	[endeavorID] [int] NOT NULL,
	[_az_func_ChangeVersion] [bigint] NOT NULL,
	[_az_func_AttemptCount] [int] NOT NULL,
	[_az_func_LeaseExpirationTime] [datetime2](7) NULL,
PRIMARY KEY CLUSTERED
(
	[endeavorID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO

Follow-up:
Kept digging in and found that the JSON that gets generated from rows (SqlTableChangeMonitor<T>, line 897) has odd capitalization:
[
	{
                [...]
		"syS_CHANGE_VERSION": 7,
		"syS_CHANGE_OPERATION": "I",
		"_az_func_ChangeVersion": null,
		"_az_func_AttemptCount": 3,
		"_az_func_LeaseExpirationTime": "2022-12-13T15:43:10.8872838"
	}
]

Notice syS_CHANGE_VERSION. OPENJSON is used in the SQL is case-sensitive so this breaks things.  I tried using the overload on JsonConvert.SerializeObject to pass in a default JsonSerializerSettings, but that also did not fix the problem (ie JsonConvert.SerializeObject(rows, settings: new JsonSerializerSettings())).
Looking into why this is happening.