Can't turn off Rating Filters.

I checked the add-on with ver.1.0.1 and the core with ver.8.5.12.
Once the Rating Filters have been enabled in the Raging Page List block, they cannot be disabled.

Even if you uncheck Rated by me, not change
Minimum number of ratings values are subject to change
Even if you uncheck Minimum number of ratings, not change

@moriaiy
Should be fixed with the above commit.

@biplobice
Once the latest version is applied, you will not be able to browse the page with the Ratings List block.
Also, the Ratings List block could not add the same error and could not add it.
Exception thrown with message ""jquery" is not a valid asset group handle"

Stacktrace:
#34 Exception in /var/www/vhosts/packages.c5j.me/concrete/src/Http/ResponseAssetGroup.php:260
#33 Concrete\Core\Http\ResponseAssetGroup:requireAsset in /var/www/vhosts/packages.c5j.me/concrete/src/Controller/AbstractController.php:101
#32 call_user_func_array in /var/www/vhosts/packages.c5j.me/concrete/src/Controller/AbstractController.php:101
#31 Concrete\Core\Controller\AbstractController:requireAsset in /var/www/vhosts/packages.c5j.me/packages/c5j_ratings/blocks/c5j_rating_btn/controller.php:45
#30 Concrete\Package\C5jRatings\Block\C5jRatingBtn\Controller:registerViewAssets in /var/www/vhosts/packages.c5j.me/concrete/src/Block/View/BlockView.php:268
#29 Concrete\Core\Block\View\BlockView:renderViewContents in /var/www/vhosts/packages.c5j.me/concrete/src/View/AbstractView.php:164
#28 Concrete\Core\View\AbstractView:render in /var/www/vhosts/packages.c5j.me/concrete/src/Area/Area.php:853
#27 Concrete\Core\Area\Area:display in /var/www/vhosts/packages.c5j.me/concrete/themes/elemental/default.php:11
#26 include in /var/www/vhosts/packages.c5j.me/concrete/src/View/View.php:109
#25 Concrete\Core\View\View:inc in /var/www/vhosts/packages.c5j.me/concrete/themes/elemental/full.php:4
#24 include in /var/www/vhosts/packages.c5j.me/concrete/src/View/View.php:288
#23 Concrete\Core\View\View:renderTemplate in /var/www/vhosts/packages.c5j.me/concrete/src/View/View.php:250
#22 Concrete\Core\View\View:renderViewContents in /var/www/vhosts/packages.c5j.me/concrete/src/View/AbstractView.php:164
#21 Concrete\Core\View\AbstractView:render in /var/www/vhosts/packages.c5j.me/concrete/src/Http/ResponseFactory.php:153
#20 Concrete\Core\Http\ResponseFactory:view in /var/www/vhosts/packages.c5j.me/concrete/src/Http/ResponseFactory.php:220
#19 Concrete\Core\Http\ResponseFactory:controller in /var/www/vhosts/packages.c5j.me/concrete/src/Http/ResponseFactory.php:371
#18 Concrete\Core\Http\ResponseFactory:collection in /var/www/vhosts/packages.c5j.me/concrete/src/Http/DefaultDispatcher.php:131
#17 Concrete\Core\Http\DefaultDispatcher:handleDispatch in /var/www/vhosts/packages.c5j.me/concrete/src/Http/DefaultDispatcher.php:59
#16 Concrete\Core\Http\DefaultDispatcher:dispatch in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/DispatcherDelegate.php:39
#15 Concrete\Core\Http\Middleware\DispatcherDelegate:next in /var/www/vhosts/packages.c5j.me/packages/c5j_pageviews/src/PageViewMiddleware.php:52
#14 C5JPageViews\PageViewMiddleware:process in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#13 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/ThumbnailMiddleware.php:76
#12 Concrete\Core\Http\Middleware\ThumbnailMiddleware:process in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#11 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/FrameOptionsMiddleware.php:39
#10 Concrete\Core\Http\Middleware\FrameOptionsMiddleware:process in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#9 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/CookieMiddleware.php:35
#8 Concrete\Core\Http\Middleware\CookieMiddleware:process in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#7 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/ApplicationMiddleware.php:29
#6 Concrete\Core\Http\Middleware\ApplicationMiddleware:process in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#5 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/vhosts/packages.c5j.me/concrete/src/Http/Middleware/MiddlewareStack.php:86
#4 Concrete\Core\Http\Middleware\MiddlewareStack:process in /var/www/vhosts/packages.c5j.me/concrete/src/Http/DefaultServer.php:85
#3 Concrete\Core\Http\DefaultServer:handleRequest in /var/www/vhosts/packages.c5j.me/concrete/src/Foundation/Runtime/Run/DefaultRunner.php:128
#2 Concrete\Core\Foundation\Runtime\Run\DefaultRunner:run in /var/www/vhosts/packages.c5j.me/concrete/src/Foundation/Runtime/DefaultRuntime.php:102
#1 Concrete\Core\Foundation\Runtime\DefaultRuntime:run in /var/www/vhosts/packages.c5j.me/concrete/dispatcher.php:45
#0 require in /var/www/vhosts/packages.c5j.me/index.php:3

@moriaiy
This issue was already been fixed in https://github.com/concrete5cojp/c5j_ratings/commit/7277d0c46aef25535861ac9622b8f7f3d3a23c94
You're using the wrong branch. Please use release/1.0.1 branch.

@biplobice
It didn't seem to be applied well.
It moved without any problem. thank you.


Do not match RFC 5114 groups without q as it is significant

This should fix the no-caching build failure on master.

Repo is frozen which prevents merging.

I am happy for this to go in to fix the build, but it is really ignoring the original problem...
i.e the decoder was doing something different to the import/export.
I do not see why if you have a p and g that match RFC5114 you would not be able to fill in the q.
If you were using this in an exchange and the q was not provided then wouldnt it make sense to be able to fill it in.
For ffdhe this is actually required in TLS as it only transmits p,g. So the only way to validate is to assume that if there is no q then it is the named group. I dont see why the same logic does not apply to any dh named group?

In the first place I'd like to see the RFC5114 groups to die completely.

Yep I agree, but backwards compatibility is still there..
I have a PR coming with a one line to fix the decoding issue..
basically a single call to
dh_cache_named_group(dh);

is required inside dh_cb() in dh_asn1.c
The dhx one calls set0_pqg() which sets the nid if it is a named group..
The dh one (where the ASN1 only contains p & g) doesnt set the nid..
So this was one of the case(s) where building q if you have p & g is correct.

Pushed.


How do I resolve this?

print("./SocialFish  \n\ni.e.: ./SocialFish.py root pass")

what problem?

Ty....I was facing problem in login..I solved it
On Tue, Apr 16, 2019 at 4:40 AM Alisson Moretto<EMAIL_ADDRESS>wrote:

what problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/UndeadSec/SocialFish/issues/142#issuecomment-483451922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AqsTmrojjqVGU3_hG8AV5EohVVmmXlBRks5vhQb4gaJpZM4csbR-
.


[Meta issue] PSUseDeclaredVarsMoreThanAssignments presents false positives

I'm assembling this issue as more of a map/canonical issue for all the issues we have today around the PSUseDeclaredVarsMoreThanAssignments rule, just so it's easier to deduplicate new issues and consolidate some of the discussion and explanation around this rule.
You might notice we have a dedicated label for this rule, and that's because its false positives come up a lot. There's an explanation of those below, but first some links to specific issues:

[ ] Unaware of cmdlets that implicitly dot-source: https://github.com/PowerShell/PSScriptAnalyzer/issues/1163
[ ] Unaware of dot-sourcing: https://github.com/PowerShell/PSScriptAnalyzer/issues/938
[ ] Unaware of specially-scoped variables: https://github.com/PowerShell/PSScriptAnalyzer/issues/663
[ ] Unaware of Pester: https://github.com/PowerShell/PSScriptAnalyzer/issues/946
[ ] Unaware of remote contexts: https://github.com/PowerShell/PSScriptAnalyzer/issues/825
[ ] Unaware of module-exported/-defined variables: https://github.com/PowerShell/PSScriptAnalyzer/issues/819

I've written an explanation of some of this before in this comment: https://github.com/PowerShell/PSScriptAnalyzer/issues/711#issuecomment-535304534. However, since this is intended to be a reference issue, I'll expand on that here.
Why doesn't PSUseDeclaredVarsMoreThanAssignments work?
PowerShell has something called dynamic scope, meaning scopes are inherited based on the runtime call stack, rather than the lexical scope of the script. So when a variable is referenced, its value is determined not by reading up the page of the editor (where was $x defined last in my script) but by the caller (when was $x defined last at runtime). This is technically impossible to analyse generally because it's possible to pick up variable values on the fly from any caller.
For example:
$x = 7

function Test-X
{
    $x
}

function Test-InnerX
{
    $x = 5
    Test-X
}

$x             # 7
Test-X         # 7
Test-InnerX    # 5 (Even though we ultimately call Test-X, it gets its value by reading up the stack and hits Test-InnerX's definition first)
$x             # 7 (Just to prove that Test-InnerX didn't set the outer $x)

How many times is outer $x referred to here? Depends on where Test-X is called, because the $x it references it resolved at call time, not at definition time like it would be in Python for example.
Also "call time" here could mean after script execution is started:
$x = 7
function Test-X { $x }

[scriptblock]::Create("Test-X").Invoke()

Or even:
Set-Content -Path ./script.ps1 -Value "Test-X"

function Test-X { $x }

$x = 111

./script.ps1     # 111

In fact this is further complicated because:

PowerShell has different variable scopes, like global:, script:, local:.

PowerShell doesn't just pick up variable values dynamically, it can also set them dynamically. Consider:
Set-Variable x 'Hello'
$x

Or indeed:
Set-Item 'variable:/x'
$x

And perhaps that could be analysed, but what about this:
$variableName = Get-Content -Raw ./varname.txt
Set-Variable $variableName 'Hello'
$x

In this scenario, there's no way to know if $x was set without examining the local filesystem. And we could make it worse, because we could get the variable name from a web API or from Active Directory or absolutely anything and the only way to know the value would be to run the script, which probably does things, so we can't do that (and if we could, how do we know we'd get the same results -- the web API might return something different for example). Meaning we simply can't know.

But of course there are some scenarios where a human can read the script and know, meaning that a sufficiently enlightened analyser could also know. What's the solution there? Probably to special-case those scenarios, but that takes time and work and diligence (things that seem simple to read as a human are often quite painstaking to implement as a PSScriptAnalyzer rule).
If it's not possible for it to always get things right, what's the point?
So based on the above, we've said this is an impossible problem to solve in general. Maybe we can special case things, but what's the point if there are always going to be things we can't determine?
Well there are a few reasons:

PowerShell is a very dynamic language. There are a number of other rules that are also undermined by how hard to analyse PowerShell actually is. So if we apply logic about being able to formally decide in every scenario whether a violation has occurred there are a number of rules in use today that we'd need to strip out and probably a number of people are going to be unhappy. We've already committed to doing to good job here, so we just have to do our best.

As a heuristic, this rule is actually pretty helpful. Most of the time it helps to flag actual bugs. And that's generally in keeping with the philosophy of PSScriptAnalyzer.

More than that, most of the open issues about this rule are about specific cases that we could work around, rather than the particularly pathological examples given above. So it could be made more helpful.

Finally, like with all linters, the point is also to help you improve your code style. If you hit a case that's bad enough that PSUseDeclaredVarsMoreThanAssignments gets it wrong, it's also an indicator that your code is hard to analyse (possibly also to a human), and that it might be worth reconsidering the pathological construct you've used. An example:
$x = 10
Invoke-Expression 'x is $x'

Here the rule can't see into Invoke-Expression's string argument to know that $x is being referenced,
but the scripter really shouldn't be using Invoke-Expression, so the warning is helpful if a bit indirect.

Ok, so what now?
Well we've consolidated the issues into a few scenarios, and in some cases there have even been some attempts to fix them:

Dot-sourcing awareness: https://github.com/rjmholt/PSScriptAnalyzer/tree/declaredvariable-childscope (stuck trying to get parameter binding right for cmdlets)
Pester awareness: https://github.com/rjmholt/PSScriptAnalyzer/tree/pester-variable-analysis (got rather complicated trying to special-case Pester's structure)

We have a reasonable idea of what the cases are, but the work-to-result ratio has meant we haven't been able to prioritise the work. On the other hand, PSScriptAnalyzer always accepts contributions and the maintainers are here to help!

A nice option would be to allow us to control when this rule (or any other) is suppressed or not. Right now we can only do this in functions or cmdlets via Diagnostics.CodeAnalysis.SuppressMessageAttribute.
If we had some way of doing this at a script level would benefit and allow author to control ignoring rules they do not want (or know can't cover the structure in the script). I'm in the boat of Pester so it is the one rule that comes back right now on every file.
At most if I had the ability to tell VS Code to ignore this rule for *.tests.ps1 files would help clear the problems panel 😬 .

@wsmelton I've added your scenario to https://github.com/PowerShell/PSScriptAnalyzer/issues/1483

A couple of the examples given in the initial post seem like scenarios that would merit a warning to the writer that they've done something else wrong (overshadowed from outer scope, double-assigning before reference, etc). Or is that the kind of analysis that you're referring to? If not, those seem a bit out of scope.
Aside from that, I'm in favor of the Pester route.

I had to fully disable the rule because I couldn't get a suppress attribute to work anywhere in this pester test (The UpdateGithubReleaseCommonParams gets used as a splat in future It statements and it's not getting recognized). Guidance would be appreciated but I don't think it'll work.
https://github.com/JustinGrote/Press/blob/main/Source/Public/Update-GithubRelease.Tests.ps1

I had to fully disable the rule because I couldn't get a suppress attribute to work anywhere in this pester test

Yeah, ScriptAnalyzer doesn't understand Pester syntax, so it can't tell that those script blocks all execute in the same context...

@jaykul A workaround is to set the variables in the BeforeAll at Script scope it seems.

This may have already been pointed out, but I've noticed that when this issue occurs (with preference variables at least, e.g. $Transcript), in addition to assigning the variables in BeforeAll, another workaround seems to be assigned the variable's scope.
So, for example:
Where assigning (but never using) $Transcript is identified as an error in VS Code, alternatively assigning $script:Transcript or $global:Transcript does not get the dreaded red squigglies.


Revert "Fix key's typo to NSFileGroupOwnerAccountName"

Reverts apple/swift-corelibs-foundation#245
(https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/2046/)

The failure is with NSNotificationQueue, which admittedly sparks my own curiosity:
`["TestFoundation/TestNSNotificationQueue.swift:127: error: TestNSNotificationQueue.test_notificationQueueLifecycle : XCTAssertNil failed: "<NSNotificationQueue: 0x00007fbd780009f0>" - "]
["Test Case 'TestNSNotificationQueue.test_notificationQueueLifecycle' failed (0.0 seconds)."]
["Executed 6 tests, with 1 failure (0 unexpected) in 0.011 (0.012) seconds"`


fix: make unproject_layout do nothing (just return original layout)

This reverts our form hydration feature originally added in https://github.com/dask-contrib/dask-awkward/pull/184. It appears to have triggered #313 and #314. We need more testing of the feature before it's ready.
This PR is an alternative to #317. In that PR we not only revert unproject_layout's action, but we also introduce more touching in the column optimization to make up for what unproject_layout was trying to accomplish. Unfortunately using shape_touched from the typetracer report causing over-touching of data.
cc @lgray

ran tests on coffea and it looks like we're good


Unifying the range type into FStar.Range

I've updated this on top of taramana_no_steel and refreshed the snapshot. Would be good to merge.. as bootstrapping this is somewhat difficult.

Thanks Guido, I've been using this in another branch and it looks good to me. Going to merge it.


Catch handler not invoked

I've got this code (simplified):
return [PMKPromise promiseWithResolverBlock:^(PMKResolver resolve) {
	resolve([NSError cancelledError]);
}].catch(^(NSError *error) {
	NSLog(@"I expected this to be printed");
});

I expected the catch handler to run, since the promise resolves with NSError, but that doesn't happen. I have been using PromiseKit a bit and I thought I understood it more or less: what am I doing wrong?

tl;dr: use anything EXCEPT cancelledError and the catch handler will be called.
You chose to use cancelledError so probably you should understand what that means.
Documented here: http://promisekit.org/PromiseKit-2.0-Released/
Question: why did you use cancelledError?

Thank you. The actual code shows a UIAlertController in the first promise, and cancelledError is used to handle cancellation. I had looked at the documentation before, and was tricked by the swift example which handles that case in its catch branch. Next time I will read the text between the samples in the docs before wasting your time :P

np, I appreciate these tickets as I worry about the whole cancellation thing catching people out and need to be aware of how to document these things so people can use the library effectively.


Add negative test cases for multi-tenancy VMODL API

Add negative test cases for multi-tenancy VMODL APIs. For examples, we need test cases to verify the API to throw InvalidArgument, NotFound, VcsFault, etc.

This issue has been solved in https://github.com/vmware/docker-volume-vsphere/pull/859


Can't specify multiple files

My log directory has files from different sub domains

default.access.log
user.access.log
etc

I don't want all of them combined. I want to see one sub domain at a time.
This works fine if there's only one file for a particular subdomain.
rhit default.access.log

But (after log rollover) there's multiple files for the same sub domain

default.access.log
default.access.log.1
etc.

I can do one at a time, no problem, but I want a combined view of a single sub domain. I tried:
rhit default.access*

but I get Unrecognized argument: default.access.log.1
So it seems rhit is finding the other file but is not treating it as a file to read, but rather like some other argument.
Any ideas? Thanks

I'm not sure I understand what you want. You'd want all the tables for the first file, then all the tables for the second file ?

If I do rhit  (no args) in the log directory, it gathers and combines info from all files, figures out the dates, paths, bytes, etc. across all of the files. However, this isn't what I want. I don't want to combine all sub domains into a single report.
If I do rhit default.access.log, it gathers info from a single file.
What I want is to gather and combine info from all files that start with (for instance) default.access, hence the rhit default.access* that I tried.
I could configure nginx to put logs for different sub domains into separate sub directories, but I was hoping to find a way to do it when all logs are in a single directory.
Since you can specify a file, I thought I could specify multiple files using a wildcard.

OK, I get it.
I'll see what I can do for that.

Thanks. By the way, I forgot to mention that I'm using v 1.6.0 which seems to be the latest version. I downloaded it directly from your web site.


Emmets Vendor prefixer cannot be disabled on SASS

   "preferences": {     "css.autoInsertVendorPrefixes": false,   } }
This command does not work on Sass files. If I press CTRL + E it only inserts the basic command. There should be an option to prevent this.  I understand that this is the default option for CSS files, but somebody using Sass is likely to have autoprefixer too .. And while, yeah, not everybody will , there should be an option to disable it.

They aren't disabling on CSS for sure. For Sass or SCSS format, you need to do them like this:
{
	"preferences": {
		"css.autoInsertVendorPrefixes": false,
		"sass.autoInsertVendorPrefixes": false,
		"scss.autoInsertVendorPrefixes": false
	}
}


[RFC] We need a better error system

Is your feature request related to a problem? Please describe.
Recently we observed more and more limitation pushed out by WeChat. In some cases, connection to WeChat server got kicked out. It would be better that we emit these cases as errors so developers could handle them properly.
Currently all the error messages emitted is an Error instance, only one message on it, so it is really hard to set a solid error type for the error. So here is this issue, I would like to bring this issue up and talk about the design for WechatyError or something else :P
Describe the solution you'd like
We could have a parent error type as WechatyError, then PuppetError extends the parent, then each puppet has its own error class.
How about this design:
class WechatyError extends Error {
  public readonly type: WechatyErrorType
  public readonly message: string
  constructor (
    type: WechatyErrorType,
    message: string,
  ) {
    super()
    this.type = type
    this.message = message
  }
}

Or we could make this parent error as an abstract class, then all the other errors extends this one.
Describe alternatives you've considered
Haven't considered any alternatives...
Additional context
I've implemented one temporary solution in wechaty-puppet-padpro, but that's just a test, you could check it here:
https://github.com/botorange/wechaty-puppet-padpro/commit/47d8de1bf885201629c8dd6dd34aaf721260d1c5
Here is a small piece of code that how I use it:
bot
.on('error', error => {
  const errorMessage = error.message
  const subMessages = errorMessage.split(' ')
  if (subMessages[0] === 'PADPRO_ERROR' && subMessages[1] === 'LOGIN') {
    console.log(`-----------------------------------------------------
    AutoLogin Error:
    type: ${subMessages[2]}
    message: ${subMessages[3]}
    ------------------------------------------------------`)
  }
})
.start()

To be honest, this is ugly, but just treat this as 【抛砖引玉】(don't know how to translate this :P)
Let's make wechaty better and better.
[enhancement]

Thanks for the RFC, it's a very good proposal.
Could you be able to provide 3 of the best examples that you could find in other open source projects, and points out which part do you think they are the best?
I believe we need more 砖 to study first, then we will be able to discuss deeper based on them.

I could try to find some good examples. And will post it in the issue.
In the mean time, how about tensorflow, what kind of error classes do they have? Since you've been working on that project for a period of time, could you please share a little about that?

I could try to find some good examples. And will post it in the issue.
In the mean time, how about tensorflow, what kind of error classes do they have? Since you've been working on that project for a period of time, could you please share a little about that?

After thinking this RFC for the past 12 months, I believe that we can move forward to continue discussing how to implement it because we will have some huge improvements for the Wechaty recently after we landing the Multi-language Wechaty.
@windmemory Would you like to share some more thoughts from your experiences in the past year? I believe it would be a great help for us to understand what is the best design of our Error system.

From the previous experience, I think there are two key properties needs to be reported when an error happened. They are:

error type (used to distinguish different errors)
whether is recoverable (so we can decide whether we should retry the operation)

Error type
I think we can achieve this feature in two ways

add a property type to the error class, we can distinguish the error by the type
extend the base error class with different class, we can distinguish the error by instanceof function

Recoverable
This can be solved in similar ways as above.

add a property recoverable to the error class
extend the base error class, create RecoverableError and NonRecoverableError, then all the other error needs to extends these two classes.

Other topic needs to be considered and discussed

where should we declare and implement these errors?
how a developer extends the errors we have currently
how to transfer these class to different languages?
since we want use grpc protobuf as the union type for different language, shall we also declare the error using protobuf? But seems like there is no standard Error syntax supported by protobuf. We need to create the error model ourselves. I am not quite familiar with this part, @huan  could you please share some insights related to protobuf?

Discussion Draft
enum WechatyErrorType {
  UNKNOWN = 0,
  NO_PAYLOAD = 1,
}

puppet.on('error', data => {
  const e = new WechatyError(data)
})
class WechatyError extends Error {

  public static from (data: grpcError) {
    payload = JSON.parse(data)

    const e = new this(payload)
    return e
  }

  public to() {
    return {
      message: this.message,
      name: this.name,
      stack: this.stack,
      type: this.type,
    }
  }

  private type: WechatyErrorType

  private constructor (
    payload: any
  ) {
    this.type = WechatyErrorType[payload.type] ?? WechatyErrorType.UNKNOWN
  }
}


The FAN seems not working on a new CORAL DEV BOARD

Description
The Fan works for a few seconds during the boot and then the Fan is not running anymore.
When I run the GStream example the board is shutting down when it reach the temperature of 65 degree which is not what the documentation says, the FAN should start at 65 degree and the board should shutdown at 99 degree.
I updated the software following the documentation but nothing changed.
Can you provide a solution
Click to expand!
Issue Type
No response
Operating System
No response
Coral Device
No response
Other Devices
No response
Programming Language
No response
Relevant Log Output
No response

I had to change the power supply, it's fine


Cannot not pass paymentPlan in initializer

The payment plan is not going through on payment for recurring billing . All other data is present on the dashboard. I suspect the key in the initializer is supposed to be payment_plan and not paymentPlan.

Hi @wilburt possible to help check this out?

The right key (payment_plan) was being used, the issue was that the payment plan wasn't being received in the initialization of the Payload object.
Pushing a fix soon.


fix: local fetch in docker

This needs some more testing. For me Local setup broke with this for some reason and Docker did not work either. Reverted for now will investigate later but not prio 1.


Books (WIP)

Do not merge this, please.
Just looking for a maybe invalid JSON, also if you want to do something here you can see my progress

continues to merge it anyways

continues to merge it anyways

just no

continues to merge it anyways

just no

:)

Im doing a new pr for this if its rdy


[docs] Add warnings about doc changes between releases

@ncdc PTAL
As discussed in Slack earlier this morning, I've added warnings/extra commands to encourage people to work off of a release rather than master.
Let me know if this seems effective and/or if any phrasing should be changed.

@skriss please review too

@ncdc @skriss standardized the version warnings (for both main README and cloud provider configs doc), also added a section to the build-from-scratch doc (re the "latest" tag stuff discussed previously)
let me know what you think!

updated

Please wait for feedback from @skriss

Updated @skriss @ncdc PTAL when you get a chance

Looks fine to me. Alternately we could just instruct users building from scratch to modify the deployment to point to their registry, which is a little less roundabout, but let's just get this merged.


Arrow key navigation

Pressing the up or left arrow key with the top list item selected leads to open the email. This seems like unexpected behaviour.
Opening the selected email by pressing enter should be a feature.

Double click fix
Before the fix in #186 emails could only be opened by double clicking. The action got called when #selectedEmail: got called on a selected email (Selecting it twice in a row). This created the problem that pressing Up at the Email at the top opened it, because it got selected when it was already selected. We removed this behavior and instead called #openEmail: directly by passing it to the #doubleClick method of the TreeSpec.

Why open Emails with key o?
The list is implemented with a PluggableTreeMorph, which uses Enter to reset its filter. All other ToolBuilder-Morphs which provide list-behavior do the same. Since Right gets captured too, we decided to use $o. The letter can be changed in ICFolderDialog class defaultOpenEmailChar

We had the idea of rebuilding the account and email list closer to how the code browser is implemented, since that behavior is much more natural for the Squeak ToolBuilder. In the same manner, dirty hacks like the "Click email to load more email" could be reworked.


Worker pod termination

We currently don't take any steps to terminate worker pods when the broker stops, and ideally we would be able to flag all the worker pods as Completed when the broker pod is. If anyone has ideas please comment here. This issue was originally discussed (with a few ideas) here: https://github.com/kubernetes-sigs/kueue/issues/716

One recommendation by @ahg-g is to use https://github.com/kubernetes-sigs/jobset to separate the broken into its own job.
However, the migration might not be worth if you plan to eventually use https://github.com/kubernetes/kubernetes/issues/117600
So, what is the right solution? The question you need to answer is whether it makes sense for the broker to be significantly different from the rest. For example, workers might need GPUs, but not the broker, or the broker might need more/less CPU.
If the answer is that the broker could be different, then jobset is the right answer. If not, then Indexed Job will be simpler and faster to manage.

The main impetus (aside from the broker having different logic, which you can see tangled up here) is controlling order / timing of creation - it would be really nice for the broker to reliably come up first! That said, I don't see that this is possible yet? It looks like the potential contents of the list in replicatedJobs come up at the same time.
For the termination issue, @mimowo mentioned that we could use the (TBA) successPolicy on the main driver as shown in this doc. to easily say "when the broker is completed this JobSet is done/successful." But you're right - this could work too.
So I understand - right now I could develop this / try it out by installing JobSet to my cluster manually. But in the future (how far?) it will ship with Kubernetes? I just subscribed to https://github.com/kubernetes-sigs/jobset/issues/82 so minimally I think I could test it out when that is added. I'm not totally sure which approach is right yet, but it would be fun to test both. I'd argue they should generate a setup that is very similar anyway, with the JobSet having a few more handles to control custom logic and order.

Pinging @grondo and @garlick on this for discussion next week! Please do fun things over the weekend and do not think about Flux!
We experimented today with the following pattern to check for a non zero exit code, and if one was found, to continue the loop:
# pseudo-code
while true:
   try to connect to the main broker
    - if fails, keep looping
    - if exit with 0, assume success and exit
   always sleep 15

With very basic testing, I saw all the pods in the COMPLETED state. This was immensely satisfying. But when I scaled it up to a production cluster to test, I saw unexpected behavior - for even a size 2 cluster, the broker and worker would both start, and somehow still appear to be waiting for one another. This was transient, because sometimes it worked, but the first time it didn't, the automated jobs came to a standstill. I stepped back, and then tried a design similar to the first, but with a shorter sleep
while true:
   try to connect to the main broker
   always sleep 1

This actually didn't work either! It was only when I returned to the original design with a longer sleep did I see the pods consistently working as they did before.
while true:
   try to connect to the main broker
   always sleep 15

This seems to be like a tiny bug, and we need to figure out the right way to ensure that retry happens when appropriate, and that (for some cases that I don't understand yet) the broker and worker don't both start, but remain somehow unlinked.
Have a good weekend everyone! :avocado:

Another update to this issue - we were able to somehow close in on part of the reason we see longer creation times than when we didn't have the certificate generator pod. It seems that zeromq has an exponential backoff when it can't connect on first try. So (what I think) is happening is that the zeromq didn't need to wait before for the headless service, because somehow with the certificate generator pod design it was ready to go. Without that, the pods can't always see each other by the time the workers and broker starts, so this exponential backoff was kicking in. When I tested this evening setting a default value in zeromq, this parameter:

The times decreased from about 140 seconds down to 20. So that doesn't give us all of the time back (before the certificate generator pod was removed we were at 11-12 per run) but it's a big chunk of the way there. What I want to better understand is how/why the headless service was always ready to go in the first setup, but now seems to take longer to be ready (in the ballpark of 5-12 seconds).

Update: zmq connect timeout has been merged into flux! https://github.com/flux-framework/flux-core/pull/5140.

This was fixed last week https://github.com/flux-framework/flux-operator/pull/159


Show number of variables per Dataset

Also for consistency, maybe we could also show the number of variables in each Dataset?

Addressed in #116


Build fails on Ubuntu

/Packages/SwiftGD-1.1.0/Sources/SwiftGD.swift:206:19: error: use of unresolved identifier 'gdImageCopyGaussianBlurred'
if let result = gdImageCopyGaussianBlurred(internalImage, Int32(radius), -1) {
^~~~~~~~~~~~~~~~~~~~~~~~~~
Cgdlinux.gdImageGaussianBlur:1:13: note: did you mean 'gdImageGaussianBlur'?
public func gdImageGaussianBlur(_ im: gdImagePtr!) -> Int32
^
Any idea?

Are you using an old version of Ubuntu?
On Sun, 25 Dec 2016 at 09:39, Maxime De Greve<EMAIL_ADDRESS>wrote:

/Packages/SwiftGD-1.1.0/Sources/SwiftGD.swift:206:19: error: use of
unresolved identifier 'gdImageCopyGaussianBlurred'
if let result = gdImageCopyGaussianBlurred(internalImage, Int32(radius),
-1) {
^~
Cgdlinux.gdImageGaussianBlur:1:13: note: did you mean
'gdImageGaussianBlur'?
public func gdImageGaussianBlur(_ im: gdImagePtr!) -> Int32
^
Any idea?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/twostraws/SwiftGD/issues/1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALm-GKorjY7VLknv_mYJLyitsKQ9SWaks5rLjnbgaJpZM4LVX8i
.

I'm on Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-53-generic x86_64)

I suspect that's the problem: I was working with 16.10. I'll edit the
README to add a version number.
--
On Sun, 25 Dec 2016 at 09:54, Maxime De Greve<EMAIL_ADDRESS>wrote:
I'm on Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-53-generic x86_64)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/twostraws/SwiftGD/issues/1#issuecomment-269116392, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALm-BuND8aV-hDexl_cCLiytK8T_XnXks5rLj1DgaJpZM4LVX8i
.

Yes that fixed it! Thanks @twostraws

@maximedegreve Hi! I'm having the same problem. How did you get this to work?

@JonasSL: Just upgrade to a more modern version of Ubuntu.


Prevent global_tenant access in Kibana

Checklist

[x] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for changelog and subsystem label(s) applied

The way that kibana checks for tenant access eventually falls back to a list of tenants available, which includes global_tenant, and will alphabetically sort the available tenants and return them to users when they log in.
This is a problem for users that may have a tenant that is alphabetically after global_tenant.
We already disable the global tenant, so this just adds a check in the getTenantByPreference that will remove global_tenant if global tenant is disabled.
This just takes a copy of this file https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/blob/opendistro-1.6/lib/backend/opendistro_security.js and COPY into the logs-db-ui image that contains the fix (L390-L394)
The latest version of security-kibana-plugin is v1.11 and the code that performs this check is completely different, but it may also suffer from the same problem, but would need to be tested/verified if we plan to upgrade.

Closing issues
closes #2327

I don't know if this will work since we are using opendistro upstream images now.
There's a config option to disable the global tenant that probably needs to be configured?

I don't know if this will work since we are using opendistro upstream images now.
There's a config option to disable the global tenant that probably needs to be configured?

Do we not set that already with the upstream images then?
We did on the images we used to build/run, but global_tenant was still accessible (https://github.com/amazeeio/lagoon/blob/master/services/logs-db-ui/Dockerfile#L38)
So unless we aren't setting it, the bug is still present in upstream opendistro and maybe the bug needs to be raised there?

Looking at opendistro 1.10 (which is what we look to be running?) it uses the same file that is in this PR to handle the tenant selection https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/blob/opendistro-1.10/lib/backend/opendistro_security.js.
But 1.11+ it changes entirely as the file is gone entirely, so possible that it is fixed in a newer version too?

Yeah it's entirely possible that it's fixed upstream. Looking at this https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/issues?page=1&q=tenant there are a lot of recent fixes.

mhh so while this is an epic fix, we don't actually use logs-db-ui anymore in production :( it's in here just for historical reasons, but we removed it from the main branch.
It's correct that we're running opendistro 1.10 currently in production, so we might need to upgrade to 1.11 in order to test if this is fixed there?
also reminds me of https://github.com/uselagoon/lagoon-charts/issues/109 which we probably should fix soon

This won't work anymore


Building OpenRCT2: lib32-sdl2_ttf unable to build

checking whether we are cross compiling... configure: error: in /tmp/yaourt-tmp-root/aur-lib32-sdl2_ttf/src/SDL2_ttf-2.0.14': configure: error: cannot run C compiled programs. If you meant to cross compile, use--host'.

Why are you using lib32? Are you trying to run WSL with multilib tools?

I am using lib32 because I am compiling OpenRCT2 - which does not as of yet actually support building in x64, at least not in a playable state.

Did you try it in the stock WSL? If yes, did it work correctly? Multilib is generally a bad idea in (a)wsl, but maybe we can get this to work somehow.

It's impossible to build in WSL due to Ubuntu 14.04 being too old.

I've only ever did a few tests of 32bit libs and multilib in general on alwsl. I very much doubt that even if it gets beyond the checking it would build. I encountered random and completely inexplicable errors with multilib (like m4 throwing unclear errors). 32bit code seems to be deeply incompatible with WLS.
I'll investigate, some day. For now: Low priority.

At least thank you for looking into it to some degree. :+1:

So since this was posted, OpenRCT2 now builds completely x64, and no longer requires multilib. Shall I close this?


com.google.fonts/check/varfont_instance_*: Improve output

Output will now display the following:

Submit a warn if instance names are not fully parsable. It will also output the unparsable tokens.
Submit a fail if instance coordinates are incorrect for known axes
Submit a fail if the fvar contains known axes and they're not mentioned in instance names.
Submit a fail if instance name tokens are incorrectly ordered
Provide link to our documentation of these checks fail or warn

I've also had to modify the following:

Improve parse.py so it can detect unparsable tokens.
instance_parse will only produce coordinates for axes it discovers. It previously produced coordinates for all axes that we supported
Updated existing tests two handle these two new features.

Fixes #2701

When we can't parse an instance name or the checks fail, it will raise a WARN/FAIL and direct users to our documentation. We may want to improve this feature and also use it for other complex checks such as vertical metrics etc.


Cleaned up some js/css, added minor css enhancements

Looks good. I enjoy the color choices. Sorry, a lot of those changes I had meant to do in #11. But I'm planning on redoing the key frame feature this Friday to match your original plans of a bar with key frames on it. Most likely, I will delete #11.


Add image feature extraction task

For some vision archs, the default pipeline tag was updated on the Hub, see https://huggingface.co/datasets/huggingface/transformers-metadata/commit/f6b73676b57a0b6624ebfcc823fa2a86ba716b60 & https://huggingface.slack.com/archives/C02EK7C3SHW/p1708984225769709
This fixes the auto task detection for these architectures.

Merging as the failing tests now pass


Text Classification fails on first run (GPU)

System Information (please complete the following information):

Model Builder Version (available in Manage Extensions dialog): <IP_ADDRESS>2703
Visual Studio Version: 17.3.6

Describe the bug
Text classification fails
To Reproduce
Steps to reproduce the behavior:
Train text classification scenario for the first time.
Expected behavior
Model trains successfully
Additional context
MLModel1-39AA9S.txt

@luisquintanilla  what was the error message? I am not able to reproduce GPU from my end because of  out-memory issue in my machine.

NVM: you attached the log


Breakable block skips region due to placed floating element

Description
#set page(columns: 2, width: 40em, height: 40em)

#lorem(50)

#figure(placement: auto, caption: "test", v(10em))
#figure(placement: auto, caption: "test", v(10em))

+ #lorem(30)
+ #lorem(20)
+ #lorem(20)
+ #lorem(10)

Take a look at https://discord.com/channels/1054443721975922748/1056574658771681361/1227424678969348117. The first page is broken because it forgets that there's space leftover and instead spills to the second page.
Reproduction URL
No response
Operating system
No response
Typst version

[ ] I am using the latest version of Typst

I've reproduced this with a placement: auto figure before a long list containing a figure or any vertically long content. The placement: auto figure introduces the page and oddly forces the list to go to the next page, as if the list were unbreakable.

Most likely, the list is layouted without knowledge of the second figure and then it's second frame is too big to fit, so it's moved to the next region.

Minimized:
#set page(width: 120pt, height: 120pt, margin: 10pt)

#block(width: 100%, height: 50pt, fill: aqua)
#figure(
  placement: top,
  rect()
)

#list(.."ABCDEFGHIJ".clusters())


Hide EOF error in recvMsg logs

Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
2024-09-04 21:53:18.534 WARN 'ydb.driver.conn.stream.RecvMsg' => failed {"error":"EOF","latency":"1.173618216s","version":"3.77.0"}

Issue Number: N/A
What is the new behavior?
this error is not logged

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 40.97%. Comparing base (279aae7) to head (f6eeae5).

Files with missing lines
Patch %
Lines

log/driver.go
0.00%
1 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (279aae7) and HEAD (f6eeae5). Click for more details.
HEAD has 49 uploads less than BASE

Flag
BASE (279aae7)
HEAD (f6eeae5)

unit
9
2

go-1.21.x
5
1

ubuntu
10
0

go-1.22.x
5
0

macOS
3
2

go-1.23.x
6
1

windows
3
0

ydb-23.3
3
0

integration
6
0

ydb-24.1
3
0

ydb-nightly
1
0

experiment
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #1440       +/-   ##
===========================================
- Coverage   67.25%   40.97%   -26.29%
===========================================
  Files         350      349        -1
  Lines       36515    30725     -5790
===========================================
- Hits        24558    12589    -11969
- Misses      10853    17624     +6771
+ Partials     1104      512      -592

Flag
Coverage Δ

experiment
?

go-1.21.x
42.38% <0.00%> (-25.06%)
:arrow_down:

go-1.22.x
?

go-1.23.x
40.95% <0.00%> (-26.23%)
:arrow_down:

integration
?

macOS
40.97% <0.00%> (-0.06%)
:arrow_down:

ubuntu
?

unit
40.97% <0.00%> (-0.53%)
:arrow_down:

windows
?

ydb-23.3
?

ydb-24.1
?

ydb-nightly
?

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

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


Aws secretmanager secret creation from a kubernetes secret doesn't transfer all keys of k8s secret to the aws secret

Upbound provider : 0.37
Crossplane version : 1.12
Trying to create a secret manager secret using the following yaml .
My kubernetes secret has 2 fields called test and test1.
kubectl describe secret ssh-key-secret
Name:         ssh-key-secret
Namespace:    default
Labels:       <none>
Annotations:  <none>

Type:  Opaque

Data
test:   4 bytes
test1:  5 bytes

apiVersion: secretsmanager.aws.upbound.io/v1beta1
kind: Secret
metadata:
  name: atest
spec:
  deletionPolicy: Delete
  forProvider:
    forceOverwriteReplicaSecret: true
    name: atest
    recoveryWindowInDays: 0
    region: us-east-1
  managementPolicy: FullControl
  providerConfigRef:
    name: default

apiVersion: secretsmanager.aws.upbound.io/v1beta1
kind: SecretVersion
metadata:
  name: atest-ca-crt
spec:
  deletionPolicy: Delete
  forProvider:
    region: us-east-1
    secretId: arn:aws:secretsmanager:us-east-1:214812636930:secret:atest-LtThXD
    secretStringSecretRef:
      key: test
      name: ssh-key-secret
      namespace: default
  managementPolicy: FullControl
  providerConfigRef:
    name: default

The first  problem here is that the key is mandatory unlike opensource crossplane provider where key is<EMAIL_ADDRESS>In the opensource provider if we dont provide the key it creates the whole secret on AWS secret manager with all present keys in the secret. This is very useful when we use tls secrets with certificates.
The second issue is that when we try to do both keys in the secret it only puts last operations  value  in aws. We tried to add the second key as follows. But then it overrides the previous one and i can see only test1 value on AWS console.
apiVersion: secretsmanager.aws.upbound.io/v1beta1
kind: SecretVersion
metadata:
  name: atest-2
spec:
  deletionPolicy: Delete
  forProvider:
    region: us-east-1
    secretId: arn:aws:secretsmanager:us-east-1:214812636930:secret:atest-LtThXD
    secretStringSecretRef:
      key: test1
      name: ssh-key-secret
      namespace: default
  managementPolicy: FullControl
  providerConfigRef:
    name: default

So in short we are unable to push multi key-value secrets to AWS secret manager.

The way I've managed to get this working is to construct a kubernetes secret with a single key, whose value is a stringified json object containing all the key:value pairs I want to be in secretsmanager.
This is not the most intuitive interface, but it works.

Thanks for your reply. In our case we really want to push a TLS secret which is automatically created by cert manager. So we dont have control on the data structure of this secret .

+1 , this is very annoying, can we maybe open a feature request to make the secretStringSecretRef.key optional and if not exist push the whole secret in a key value format just like in the opensource crossplane provide?

+1

+1


Add CONTRIBUTING.md and reference Contributing to Chef Managed Community Cookbooks

Resolves #7

Merging into release branch instead of master. Thanks!


converting home page js and css into clean code

Describe the bug

I want to convert home page js and css into clean code

Possible solution

I will make code simple and easy to understand

Do you want to work on this issue - [Yes]

@codewithvk Please assign me the issue.


Responsive tables

Tables need to be tweaked to work better in smaller viewports. For example, try viewing the post index on a phone.

No longer require with the updates that are coming.


maintainers: add giang

Motivation for this change
Add Jellyfish, a common k-mer counter in bioinformatics.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Feel free to do this just within #143066

Included in https://github.com/NixOS/nixpkgs/pull/143066


@org_golang_x_sys does not resolve in external package

Bazel still seems unable to find @org_golang_x_sys even after adding "--build_tags=linux,amd64,darwin" to Gazelle args.
$ bazel run //:gazelle
... (passes)
$ bazel build //client
ERROR: /home/ccoalson/.cache/bazel/_bazel_ccoalson/cb8e2daf9e92ab1ccc3fd6001f083122/external/com_github_hanwen_go_fuse/fuse/BUILD.bazel:3:1: no such package '@org_golang_x_sys//unix': The repository could not be resolved and referenced by '@com_github_hanwen_go_fuse//fuse:go_default_library
...

Bazel version: 0.5.3
/WORKSPACE:
git_repository(
    name = "io_bazel_rules_go",
    remote = "https://github.com/bazelbuild/rules_go.git",
    tag = "0.5.3",
)
load("@io_bazel_rules_go//go:def.bzl", "go_repositories", "go_repository")

go_repositories()

go_repository(
    name = "com_github_hanwen_go_fuse",
    commit = "204b45dba899dfa147235c255908236d5fde2d32",
    importpath = "github.com/hanwen/go-fuse",
)

/BUILD:
load("@io_bazel_rules_go//go:def.bzl", "gazelle", "go_prefix")

go_prefix("github.com/calder/kestral")

gazelle(
    name = "gazelle",
    args = [
        "--build_tags=linux,amd64,darwin",
    ],
)

This repository does not provide support for Bazel build rules. Perhaps the proper place to file this is github.com/bazelbuild/rules_go?


Normalizing New Lines

Leaving a double new line creates a blank paragraph tag when converted to HTML

Thanks for spotting the issue. Just fixed a push for that
Fix Commit


[Help wanted]How to locate dependency using go module?

After execute go mod tidy, a dependency github.com/klauspost/reedsolomon is download and put into go.sum,but my project actually not import it. Some of my import packages might inner import github.com/klauspost/reedsolomon.
So, how can I know which package I import has imported github.com/klauspost/reedsolomon

You can use go mod graph to print out the dependency graph of module imports. Use go help mod graph for an explanation of the output.
Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions. We only use our bug tracker for tracking bugs and tracking proposals going through the Proposal Process.
Please see https://golang.org/wiki/Questions for good places to ask questions.

3q


how to auto cache url import to disk

as title

I've added a ModuleCacheProvider trait you will be able to implement in the next version to provide caching

To give more details on how this will work; RuntimeOptions now has a module_cache property
Which will be a boxed instance of a type implementing the module_loader::ModuleCacheProvider trait
You will find DefaultModuleCacheProvider in module_loader.rs as an example of how to implement it
You should be able to use that to perform disk caching how you wish

Fixed in version 0.4.0


[1 of n: Icons] Implement page icons

Reviewer: @Poltergeist

This broke tests, fixing now.

retest this please

there's a legit failure in unit tests

@kennyt derp, I thought it was integration tests for some reason.
The unit tests are fixed by #475

From a design standpoint, I gotta say I find the contrast between the sharp icon outlines and the antialiased fonts a tad incoherent. But I'm probably out of my element – feel free to ignore this, @jfurrow  @leemunroe @ashenden ?

@pierlo-upitup In the screenshot above, the fill attribute was set inline for each icon to #000 which might be to blame for the incoherent contrast. That's fixed in #471. Here's a recent screenshot (although @ashenden has suggested we bump up the opacity):

There is one thing which I do not like about the icons, and that is that there are so many of them why aren't we using SVG sprites with svg symbols?

@Poltergeist To be honest I did not see the benefit either way. I'm not opposed to using SVG sprites, but why do you prefer them?

Well with the use of the SVG to react component loader we are moving all the SVG code to the Javascript base. Which means that we are moving about 2MB of svg code into our already about 5 MB Javascript code base. Also we are adding a bit of react boilerplate onto every single svg. That is my first concern.
I do like symbols personally a lot because I only must write a very small svg element and I have my logo with the name I probably know. The styling could still be done with css. So size and color for example. This is my opinion which is not that important.
But I am very concerned about the file size of the javascript code. But anyways this is not connected to this PR it looks good to me. 🚢

@Poltergeist That's a very good point. After discussing with @rcorral, I am going to pursue that route. Good catch!

Closing to implement SVG sprite!


No error highlighting for non-existant function

TS Template added by @mjbvz
TypeScript Version: 4.2.4
Search Terms

javascript
object literal

Consider the simple code below, written for AWS Lambda:
const foobar = {
  handler: (event, _context, callback) => {
    const body = JSON.parse(event.body);
    return foobar.validate();
  },
};

module.exports = foobar;

validate() is not yet implemented, yet VSCode does not alert me to that fact. In the below screenshot, there is no highlight in regards to calling foobar.validate()

@RyanCavanaugh I'll be honest, I have no clue what that means.


[DISCUSS] - Moves the SQL Lab menu before Charts

SUMMARY
Moves the SQL Lab menu before Charts to make it workflow-oriented. Generally, the most common workflow is:

to connect with database in Data, Persona: Data scientist.
to explore raw data, cleanup and restructure data if needed, prepare data for exploration by creating virtual datasets in SQL Lab, etc, Persona: Data scientist
to explore, slice, and dice data, and to create charts for a dashboard in Explore(Chart); Persona: Data analyst
to view and edit dashboard in Dashboard Persona: Business analyst/business users.

The other possibility is to reorder the objects by usage, and the order would be the opposite. Dashboards -> Charts -> SQL Lab -> Data. This argument may seem counterintuitive to DS, as DS spends the majority of their time handling data. But the number of dashboard consumers is way larger than dashboard creators in large enterprises.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

@junlincc @rusackas
TESTING INSTRUCTIONS

Login to Superset
Check the main menu

ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

@michael-s-molina would you be able to document the motivation for the change?

Please make sure PR description has enough context.

In airbnb, SQL users and Dashboard creation users are overlapped but not same group of people. Many users come to superset only for SQL Lab.  This change is minor, but still might make them feel inconvenient and confused. Could you provide more reason for this change? thanks!

@john-bodley @ktmud I'll check with @junlincc and @rusackas about the change and provide more context in the PR's description.

Hi @john-bodley
We are trying to clearing some low-hanging fruit that previously discussed with Cartel, and approved in SIP-34.
Menu items in the top nav bar historically were not arranged in any particular order. We re-ordered the nav menu once last year and re-organize items in the sub menu as first step.
In the research with Cartel, the designer suggested that we can either arrange it by user's work flow, which is 1. to connect with database in Data, Persona: Data scientist. -> 2. to explore raw data, cleanup and restructure data if needed, prepare data for exploration by creating virtual datasets in SQL Lab,  etc, Persona: Data scientist -> 3. to explore, slice and dice data, and to create charts for dashboard in Explore(Chart); Persona: Data analyst ->4. to view and edit dashboard in Dashboard Persona: Business analyst/business users.
The other idea is to reorder the objects by usage, and the order would be the opposite. Dashboards-> Charts->SQL Lab->Data. This argument may seems counterintuitive to DS, as DS spend majority of their time in handling data. But the number of dashboard consumers is way larger than dashboard creators in large enterprises.
Given the current order, Data -> Charts -> Dashboards -> SQL lab, it seems to be less disruptive if we reorder by workflow.
We also did some user research in-house to validate our assumption, it's not directly related but could use it as a support document.
https://docs.google.com/presentation/d/182UJeK4y-BhcYkWJWYTJSA-O2_2LOXDYoAANi76-uBQ/edit#slide=id.g9743bec153_1_113

Thanks for your comment @junlincc!
@john-bodley @ktmud @graceguo-supercat I updated the PR's description with Junlin's comments. We are trying to establish the most suited workflow for the majority of organizations using Superset.
Do you agree with the change?

Personally I think it'd make more sense to order by usage than workflow:

Most users don't need the full workflow: even for Data Scientists, they seldom work through the whole workflow in one go---IMO having the full workflow in the right order is less important than having easiest access to the most used steps in the workflow.
Different users have different workflows: "Data -> SQL Lab -> Chart -> Dashboard" is just one workflow of some Data Scientists. Some more frequent workflows are:

"Chart -> Dashboard"---for Data Scientists who only use pre-configured and shared datasets (which is probably something Superset should encourage), in which case one may argue the Data tab should be hidden into "Settings" (like Redash does).
"Dashboard -> Chart -> SQL Lab"---for dashboard viewers who are also interested in how the underlying data were computed. This is somewhat similar to Looker's "Browse -> Explore -> Develop".

The order is less important in the main menu: while having the right order is important in some places, it's not like users can return to previous steps by clicking on the main menu.
Home page already orders content by usage: it's better be consistent than not.

I went back and checked, SIP-34 actually re-arranged the menu by usage order (Dashboards -> Charts -> SQL Lab -> Data). There must be some reason behind that---hope it was in line with what I described above.

@ktmud i agree. those routes you mentioned are validated in our research as well.
I personally don't have a strong preference of arranging the order by "Dashboards-> Charts -> SQL lab -> Data" or the other way around, as long as SQL lab is being placed in AN order. I know that this module was added separately and organically before without any design thinking.
Looks like we have reached an agreement here. I'm happy to change in order to move this PR forward :)

@junlincc @ktmud Thanks for your comments.
@junlincc @ktmud @srinify @john-bodley @graceguo-supercat
Can we proceed and make the change to follow SIP-34 order?
Dashboards -> Charts -> SQL Lab -> Data

I think both "Dashboards -> Charts -> SQL Lab -> Data" and "Dashboards -> Charts -> Data -> SQL Lab" make sense and don't have a strong preference of either.
The former is in line with the order by usage, but although SQL Lab may be more frequently used than Data overall, a lot of users almost never use either. For users do use SQL Lab directly from the main nav, it's a very separate workflow and they tend to use it a lot. So Keeping it as the last item also makes sense.

@michael-s-molina please reopen the PR and proceed the change with below order.
Dashboards -> Charts -> SQL Lab -> Data
thanks for everyone's discussion

@michael-s-molina please reopen the PR and proceed the change with below order.
Dashboards -> Charts -> SQL Lab -> Data
thanks for everyone's discussion

@junlincc I opened a follow-up PR to preserve the original description and screenshots of this PR. Both PRs are referencing each other.

Before we go, I'd also like to vent out something that has been brewing in my mind for a while. I've noticed many times that whenever there is a disagreement in UX changes, there is the argument that "we are doing this for the broader Superset community/the majority of Superset users", or the so-called "business users". To me, this argument feels counterproductive.
As shown above, there can be many more substantive arguments about either side of each choice. Even if you made a decision with your version of "the majority of users" in mind, it's possible that there are the other side of the coin or some deal-breaking edge cases not factored into the decision-making process. We raise our concerns based on what our users tell us (and years of experience of dealing with real Superset users), too. It's quite discouraging to have to defend these concerns as if they were only of the interest of a small group.
Let's focus on the substance and make sure all future PRs have logical and thorough reasoning clearly stated BEFORE they are up for review. "We think this is better for new/most users" is not good enough.

I agree we should have a better flow for communicating and implementing UI/UX changes, and we will make sure it happens soon.
FYI This change may seem recent, but the actual research that was done to support this change happened last year, 80% of our datapoint is actually collected from airbnb users last year, and if not all, most of the interviewee agreed with changing the order, and the research summary is in
https://docs.google.com/presentation/d/182UJeK4y-BhcYkWJWYTJSA-O2_2LOXDYoAANi76-uBQ/edit
2 Preset designers and I each talked to 6-7 users, connected by @zuzana-vej.
@graceguo-supercat @ktmud @john-bodley @willbarrett @kristw


fix: Room - Side panel does not close when clicking outside of panel.

Details

Fixed Issues
$ https://github.com/Expensify/App/issues/34394
PROPOSAL: https://github.com/Expensify/App/issues/34394#issuecomment-1888140979
Tests

Click on FAB > Start chat > Room > Workspace
Click outside of the side panel
Verify sidebar is closed
Click on FAB > Start chat > Room > Who can post
Click outside of the side panel
Verify sidebar is closed
Click on FAB > Start chat > Room > Visibility
Click outside of the side panel
Verify sidebar is closed

[x] Verify that no errors appear in the JS console

Offline tests

Click on FAB > Start chat > Room > Workspace
Click outside of the side panel
Verify sidebar is closed
Click on FAB > Start chat > Room > Who can post
Click outside of the side panel
Verify sidebar is closed
Click on FAB > Start chat > Room > Visibility
Click outside of the side panel
Verify sidebar is closed

QA Steps

Click on FAB > Start chat > Room > Workspace
Click outside of the side panel
Verify sidebar is closed
Click on FAB > Start chat > Room > Who can post
Click outside of the side panel
Verify sidebar is closed
Click on FAB > Start chat > Room > Visibility
Click outside of the side panel
Verify sidebar is closed

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/85894871/eba633cc-4485-4483-a8ab-3ad4e2481e18

Android: mWeb Chrome
https://github.com/Expensify/App/assets/85894871/e935ecda-a438-4a60-bea1-815e3f4bda38

iOS: Native
https://github.com/Expensify/App/assets/85894871/d0459d58-f752-495a-a061-f26b7bf8ee26

iOS: mWeb Safari
https://github.com/Expensify/App/assets/85894871/5ce59716-849d-48b4-83e9-245efe9ec77a

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/85894871/491b1ebe-a31d-4527-84e7-d3d22115c2c4

MacOS: Desktop
https://github.com/Expensify/App/assets/85894871/4cdd5c1b-05b8-491d-824d-f56ee96d1172

@Krishna2323 please fix the conflict so we can review and merge

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/danieldoglas in version: 1.4.55-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Krishna2323 @danieldoglas @hoangzinh — appears to be a bug in the fix per this GH 👍


⚠ SceneTime has degraded performance

In ed7fad0, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 21153 ms

Resolved: SceneTime performance has improved in d9dd864 after 5 minutes.


Editing of online posts

If a post has already been made then surely you must not be able to edit it again?

Not necessarily. E.g. request #221 "Edit message [Pump.io]" explicitly asks for this.
So this depends on a concrete Social network (both on its capability and configuration).
AFAIK Twitter and GNU Social don't support editing posts.

Oh okay. :)
Sent from my iPod

On Oct 2, 2015, at 6:03 PM, Yuri Volkov<EMAIL_ADDRESS>wrote:
Not necessarily. E.g. request #221 "Edit message [Pump.io]" explicitly asks for this.
So this depends on a concrete Social network (both on its capability and configuration).
AFAIK Twitter and GNU Social don't support editing posts.
—
Reply to this email directly or view it on GitHub.


It’s me again. Your docs and errors are still meh. QuickStart still doesn’t work.

Hello world in the QuickStart.
OllamaLLMUnit implementation.

Ok where does my Ollama server URL go?
The page about the Ollama implementation in the docs does not mention url whatsoever. Client_options is listed as an object. No further documentation on expected fields. Why should someone have to go to the code to figure out that configuration? There is a whole page for it in the documentation, and a whole spot in which the way to define the URL should live…

“ok maybe it defaults to localhost:11434. I’ll give them another chance. Ollama is running there”. I put in a random model “Nemo:4b” in as the model.name, and “forget this overcomplicated thing” as model.human_name. After restarting, there is a big ugly fatal error that mentions ‘llama’ is not a fully qualified class name. That’s confusing, because the word ‘llama’ doesn’t appear in the config. It’s a configuration issue, so why give this qualified class name junk as an error? Why not suggest the correct config? I’m a prospective casual non-python user. There are docs. Why don’t the docs have info about this in a digestible way?

Still didn’t work with OpenAI. Env var is set. Says 404 can find the process. Well, the frontend is literally sending undefined for the process ID. Stock, off the shelf main branch. SMH.

This has been the 3rd or 4th attempt in the past 6 months. I know y’all spent a lot of time and energy making this. Looks promising… can’t get it to work. I asked questions on your discord, and eventually left the server because yall never responded. Is this feedback appreciated? Are you gonna overhaul docs? Am I wasting my time? Perhaps, I’m a bit disappointed and hoping that someone will clear up the misunderstanding I have about this product. It’d help you get another follower, and it’d help me to quit counting the number of hours I’ve spent on this as wasted time.

I'm so sorry. I've been brought on to help with this specifically, but two significant family concerns have me traveling and attending to matters.
I would very much like to help you. I will be back on Tuesday. Please hang tight.
Was the Quickstart successful for any other LLM provider? I understand that Ollama is self-hosted.

@atljoseph thanks for helping us fight through the pain so we can make this a better experience. We do appreciate the feedback.
1: How are you running the server?
Are you using make docker-serve? If not I would recommend that. Running via python process is helpful for building custom tools or agent-templates, but isn't helpful when getting started or when defining agents via yaml files.
2: Did clone a new repo or are you still working from the old one?
We swapped out the quickstart repo with a new one to prevent fork-of-fork weirdness in GitHub. This might cause weird behavior if you are working off a local clone or fork and just pulled rather than re-cloning the quickstart.
3: What version of the SDK are you using?
We are in the midst of spending another cycle on our errors, but we cleaned up some of the llm errors a few versions ago. I do not think ollama was part of this yet unfortunately,
cat pyproject.toml | grep eidolon-ai-sdk
eidolon-ai-sdk = "^0.1.142"

if this particularly outdated, # 2 is likely an issue.
4: Could you check what version of the webui you are using and update it?
docker image ls | grep eidolonai/webui
eidolonai/webui                 latest    2b9a2489c5cf   3 days ago       350MB

I think this is likely out of date since you were working on the project a while back. I just checked our makefile target, and we don't grab the latest version of the webui when running via docker-serve. We aren't pinning this to a version in the example repos, but we should. I'll file a ticket.
docker pull eidolonai/webui:latest

TL:DR
I think the repo, sdk, or webui image is out of date (likely the last).
I spent some time trying to reproduce on latest main, but was unable to. I know before we revamped the dev tool we had that issue when creating a conversation if the server was not running (or the agent did not exist). If this is the case, pulling a new webui or starting a new conversation should fix the problem.
If the above does not help, could you upload your server / ui logs?
docker compose logs > combined_logs.txt

I got it working. Had already pulled latest from the git branch, but there were outdated docker artifacts, yes.

So, i deleted all old eidolon-related docker containers and images.

It works reasonably well, now, albeit, the docs could have more digestible info. Diving into Python code and finding what you need has been passed as kwargs is just chasing tail, for someone who is not a python whiz. Proper docs ensures adoption.
Initially, it would connect to chatGPT despite the config i gave it.

OLLAMA_HOST. Why is that not plastered everywhere on the OllamaLLMUnit page?????
OLLAMA_HOST=http://localhost-not-work-but-IP-did:11434
Did not include /v1, but should I? Is that a thing?

This worked (through much trial and error):

Some questions noted here, too.

kind: Reference
metadata:
  name: Gemma2
  annotations:
    - title: "Gemma 2"
spec:
  implementation: ConversationalAPU
  llm_unit:
    implementation: OllamaLLMUnit
    # ollama_endpoint:   <--- Csan i use this? Am riffing on an Azure example, here.
    model:
      implementation: llama3-8b
      name: gemma2:9b
---
apiVersion: server.eidolonai.com/v1alpha1
kind: Agent
metadata:
  name: jeff_bridges
spec:
  description: "The Dude abides."
  system_prompt: |
    Like, hey Man, that rug really tied the room together!
  title_generation_mode: auto
  actions:
    - name: "Develop a joke."
      description: "Your personal comic."
      # What goes heres?
    - name: "Chat about code."
      description: "Your cousin, who's a software engineer."
      # What goes heres?
  apu: Gemma2
  # apus:
  #   - apu: Gemma2    <--- Why does this not work? I like to swap models

if I needed multiple ollama host environment variables, how would I declare those? how would I make an agent system where one agent is on one Ollama server and another is on another Ollama server?

Hi @atljoseph I'll try my best and rely on the more technical folks to fill in what I miss. I don't have the software running right now and I confess I haven't tested this. So forgive me if there's a typo or error. But I'm pretty sure I can get you in the right direction.
One of the problems you're running into is the same that I had when I started: it wasn't clear how to edit the YAML files correctly. This is being addressed through issue #740 .
I would simplify things by creating one agent and make sure you're getting gemma2. Then you can create new APU references, and introduce them into the agent as in this multi-chatbot example.

Save all files to your /resources directory!

apiVersion: server.eidolonai.com/v1alpha1
kind: Agent
metadata:
  name: jeff_bridges
spec:
  description: "A conversational agent for dudes."
  system_prompt: |
    You can answer any question, but speak as if you are Jeff Bridges in The Dude.
    Use catch phrases whenever you can, such as:
    "Like, hey Man, that rug really tied the room together!" and
    "The Dude abides."
  title_generation_mode: auto
  apu: # from https://www.eidolonai.com/docs/components/apu/overview
    implementation: llamma3-8b
    llm_unit: # from https://www.eidolonai.com/docs/components/apu/llamma3-8b#6-property-llm_unit
      implementation: OllamaLLMUnit
        model:
          name: gemma2 # from https://ollama.com/library?sort=featured
          human_name: "Gemma 2 9B"

Once you have that going, you can create reusable APU references. Personally, I would create them as separate YAML files, but you can combine them in one if you like. Just separate them with ---.
apiVersion: server.eidolonai.com/v1alpha1
kind: Reference
metadata:
  name: Gemma2
  annotations:
    - title: "Google Gemma2 9B"
spec:
  implementation: ConversationalAPU
  llm_unit:
    implementation: ToolCallLLMWrapper
    llm_unit:
      implementation: OllamaLLMUnit
      model: "gemma2"

and another...
apiVersion: server.eidolonai.com/v1alpha1
kind: Reference
metadata:
  name: "Llama3.2"
  annotations:
    - title: "Llama 3.2 1B"
spec:
  implementation: ConversationalAPU
  llm_unit:
    implementation: ToolCallLLMWrapper
    llm_unit:
      implementation: OllamaLLMUnit
      model: "llama3.2:1b"

Then you can go back to your agent and replace the apu: section with apus:
apiVersion: server.eidolonai.com/v1alpha1
kind: Agent
metadata:
  name: jeff_bridges
spec:
  description: "A conversational agent for dudes."
  system_prompt: |
    You can answer any question, but speak as if you are Jeff Bridges in The Dude.
    Use catch phrases whenever you can, such as:
    "Like, hey Man, that rug really tied the room together!" and
    "The Dude abides."
  title_generation_mode: auto
  apus:
    - apu: Llamma3-8b # built-in
    - apu: Gemma2 # your custom reference
    - apu: Llama3.2 # your custom reference

Yeah got all that thanks

How to point one model at one Ollama host and another at another host?

Re:

Initially, it would connect to chatGPT despite the config i gave it.
OLLAMA_HOST. Why is that not plastered everywhere on the OllamaLLMUnit page?????
OLLAMA_HOST=http://localhost-not-work-but-ip-did:11434/
Did not include /v1, but should I? Is that a thing?

OpenAI is the default
I defer to the developers; I'm not experienced with Ollama yet.
Are you using virtual environments? Localhost should work if Ollama and Eidolon are running in the exact same environment.

Docker all the way.

Do y’all have a collection of what all people have made with eidolon?

How to point one model at one Ollama host and another at another host?

That's a darn good question. The best I can think of (I do not know if this will work) is to use https://www.eidolonai.com/docs/components/llmunit/ollamallmunit#client_options
apiVersion: server.eidolonai.com/v1alpha1
kind: Reference
metadata:
name: Gemma2
annotations:
- title: "Google Gemma2 9B"
spec:
implementation: ConversationalAPU
llm_unit:
implementation: ToolCallLLMWrapper
llm_unit:
implementation: OllamaLLMUnit
model: "gemma2"
client_options:
OLLAMA_HOST = "http://localhost:11434"

@dbrewster @LukeLalor please advise

Do y’all have a collection of what all people have made with eidolon?

We're working on it. I'm sorry I have to sign off now for a couple of days due to some family matters. I hope my colleagues can get you on the right track.

Thanks. It’s ok! Have a good time with the fam.
Exactly. Not sure what the possible client options actually are.

Gonna count this as done, even if there is some follow up. Thank you

filed #849 and #850


Copy to clipboard behavior

Can Clipper have a "Copy to clipboard" behavior. This would be useful for inserting into the random notes that I happen to working on at any given time.
I know I can "ctrl+A" and then "ctrl+C" on the preview but pressing the button at the bottom instead would surely save a step every time.

Can you clarify what the use case is? Have you considered using "Add to existing note" in your template?

I like to have certain notes open in Obsidian, and while doing research, place a reference to the site (in a certain format) in the note. The thing is that there isn't any one note that I would put the reference in, so creating an "add to existing note" for every note in my vault would be overkill.

This was added in 0.9.7


#1063: Begin 0.11 porting process

Version 0.11 of the bootloader crate introduces a lot of breaking changes, so time to start work on making sure that all posts are up-to-date to (hopefully) make it far easier for Phil to move forward with fixing #1063.

Decided to also fix all the broken links throughout all editions as part of this pull request, as a kind of thank-you-in-advance for merging.

Alright, trimming down the excess when I get home later — first day on a new job, so will be much busier today than I was yesterday. Expect a fix around 10PM Pacific time.

Thanks! There's no need to hurry, good luck with the new job!

Alright, just submitted a new commit that fixes the issues brought up in the line comments.

Fixed some more links that died along the way too

Uhm, for me https://web.archive.org/web/20190217233448/https://www.flingos.co.uk/docs/reference/Global-Descriptor-Table/ still works. Maybe we could include both links somehow

Uhm, for me https://web.archive.org/web/20190217233448/https://www.flingos.co.uk/docs/reference/Global-Descriptor-Table/ still works. Maybe we could include both links somehow

Yeah, I think the links fixed in 7b2efae were only temporary failures, so I think we can keep the original links.

Alright, just submitted a new commit that fixes the issues brought up in the line comments.

Thanks, looks good to me now! Sorry for the long delay.
I just merged the changes related to the third edition into the edition-3 branch in commit 79be18bf. The link fixes were already merged into main in https://github.com/phil-opp/blog_os/pull/1188.


Create BobPay payment method

In order to enable JIT install of BobPay, create a new payment method of https://bobpay.xyz/pay.

Change payment method identifier
https://bobpay.xyz/pay to point to https://bobpay.xyz/pay/payment-manifest.json
https://bobpay.xyz/pay/payment-manifest.json to include https://bobpay.xyz/pay/manifest.json as a default application.

Looks good to me! What's your test site?

https://polykart.store
I need to replace identifier first.


A Run Error

Hi kamyu104!
I am a Chinese student.I'm not good at python.
I used your code,but it runs error, what should I do?
GoogleCodeJam-2017/Round 3/mountain_tour

Can you provide C++ code?

The code for the repository was written in Python 2 several years ago.
It should run in Python 2, not Python 3.
Since the contest website was shut down, I can no longer restore my C++ code.
Additionally, this repository is no longer updated.


zsh crashes when doing multi-line editing

$ echo "
fdsfsdfds
fdsfsdfdsfs
fdsfsdfsdfsd
fdsfsdfsdfs

Just keep doing this and zsh will eventually crash but only when syntax highlighting is enabled.

Is there a solution for this?

I haven't attempted to reproduce this issue, but if you see a segfault, then there is a bug in zsh itself. (There may or may not be a bug in zsh-syntax-highlighting, but nothing it does should cause a segfault, and it doesn't contain any C code of its own.)
It should be possible to reproduce the segfault in vanilla zsh without zsh-syntax-highlighting.

I cannot reproduce this with zsh-5.0.7 or zsh-5.1. Since the duplicate issue #141 provided a very clear and unambiguous recipe, I'll go ahead and close this as an upstream bug that is presumed to have been fixed. Please reopen if you can reproduce this with a new zsh.


ns-render dataset bug for gaussian splatting

I want to render a splatfacto model using the command line
ns-render dataset --load-config=/path/to/config.yml --output-path=/path/to/render_dir --split=train+test --rendered_output_names=rgb

I obtain the following error:
Traceback (most recent call last):
  File "/home/ubuntu/contribs/nerfstudio/nerfstudio/scripts/render.py", line 898, in <module>
    entrypoint()
  File "/home/ubuntu/contribs/nerfstudio/nerfstudio/scripts/render.py", line 894, in entrypoint
    tyro.cli(Commands).main()
  File "/home/ubuntu/contribs/nerfstudio/nerfstudio/scripts/render.py", line 733, in main
    config, pipeline, _, _ = eval_setup(
  File "/home/ubuntu/contribs/nerfstudio/nerfstudio/utils/eval_utils.py", line 97, in eval_setup
    config = update_config_callback(config)
  File "/home/ubuntu/contribs/nerfstudio/nerfstudio/scripts/render.py", line 721, in update_config
    assert isinstance(data_manager_config, VanillaDataManagerConfig)
AssertionError

However, when I comment https://github.com/nerfstudio-project/nerfstudio/blob/7f9def1ff0b869dcf1d00abe475759de05cdf435/nerfstudio/scripts/render.py#L721 and https://github.com/nerfstudio-project/nerfstudio/blob/7f9def1ff0b869dcf1d00abe475759de05cdf435/nerfstudio/scripts/render.py#L740 I obtain the expected result.
Are these assertions absolutely necessary? Should they be updated to also accept the FullImageDatamangerConfig that is used by splatfacto?
I'm happy to raise a PR once this point is clarified.

Good catch! yes they should also include FullImageDatamangerConfig, I think it might have just fallen through the cracks since we don't use the dataset render often

Thanks for your feedback, it's indeed a very useful feature!
I created the following PR to fix that: https://github.com/nerfstudio-project/nerfstudio/pull/2917

Hey, this feature is valuable indeed. My issue is that the cameras dont match up after their positions get optimized during training. If those flags are turned OFF, the cameras match perfectly. Can I request the already-optimized cameras? So that even after training the cameras match?
render.py should be where this is at?

Thanks for your feedback, it's indeed a very useful feature! I created the following PR to fix that: #2917

It seems like the problem got fixed, but I still got an error and only got it to work by commenting out the lines.
assert isinstance(data_manager_config, (VanillaDataManagerConfig, FullImageDatamanagerConfig))
AssertionError


Long lines are cut in terminal

Is it possible to wrap long lines instead of cutting them?

This is not implemented at the moment. It needs probably many code changes because the code assumes that each entry uses exactly one line.


Error when building OpenFAST with c++ API enabled

Hello everyone,
I plan to use OpenFAST c++ API to develop a coupling technique between OpenFAST and in-house CFD solver.
I have successfully compiled OpenFAST package using Cygwin64 with default setting (c++ API OFF). However, when I try configuring the main CMakeList file to turn on c++ API or turning the option on via command line, I get the following:
-- A library with LAPACK API found.
-- Setting system file as: src/SysGnuLinux.f90
CMake Warning (dev) at /usr/share/cmake-3.14.5/Modules/FindMPI.cmake:1251 (if):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
details.  Use the cmake_policy command to set the policy and suppress this
warning.
Quoted variables like "CYGWIN" will no longer be dereferenced when the
policy is set to NEW.  Since the policy is not set the OLD behavior will be
used.
Call Stack (most recent call first):
glue-codes/openfast-cpp/CMakeLists.txt:20 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at /usr/share/cmake-3.14.5/Modules/FindMPI.cmake:1255 (elseif):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
details.  Use the cmake_policy command to set the policy and suppress this
warning.
Quoted variables like "CYGWIN" will no longer be dereferenced when the
policy is set to NEW.  Since the policy is not set the OLD behavior will be
used.
Call Stack (most recent call first):
glue-codes/openfast-cpp/CMakeLists.txt:20 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.
-- Could NOT find MPI_C (missing: MPI_mpi_LIBRARY MPI_open-rte_LIBRARY MPI_open-pal_LIBRARY MPI_z_LIBRARY MPI_C_HEADER_DIR MPI_C_WORKS)
-- Could NOT find MPI_CXX (missing: MPI_mpi_LIBRARY MPI_open-rte_LIBRARY MPI_open-pal_LIBRARY MPI_z_LIBRARY MPI_CXX_HEADER_DIR MPI_CXX_WORKS)
-- Could NOT find MPI_Fortran (missing: MPI_mpi_usempif08_LIBRARY MPI_mpi_usempi_ignore_tkr_LIBRARY MPI_mpi_mpifh_LIBRARY MPI_mpi_LIBRARY MPI_open-rte_LIBRARY MPI_open-pal_LIBRARY MPI_z_LIBRARY MPI_Fortran_F77_HEADER_DIR MPI_Fortran_MODULE_DIR MPI_Fortran_WORKS)
CMake Error at /usr/share/cmake-3.14.5/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find MPI (missing: MPI_C_FOUND MPI_CXX_FOUND MPI_Fortran_FOUND)
Call Stack (most recent call first):
/usr/share/cmake-3.14.5/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.14.5/Modules/FindMPI.cmake:1672 (find_package_handle_standard_args)
glue-codes/openfast-cpp/CMakeLists.txt:20 (find_package)
-- Configuring incomplete, errors occurred!
See also "/home/meow_/code/OpenFAST_sandbox/build/CMakeFiles/CMakeOutput.log".
See also "/home/meow_/code/OpenFAST_sandbox/build/CMakeFiles/CMakeError.log".
CMakeError.log
I believe HDF5 and yaml-cpp are required for OpenFAST C++ API. I installed both of them in Cygwin and still have the issue. I also have OpenMPI for Cygwin.
Any suggestion or help would be highly appreciated!

Hi @auraluck Are you still stuck on this compiling problem?


feat(ffi): add http1_allow_multiline_headers

Close issue #2885

Thanks for the PR! <3
Looks like the function names are out of sync. The hyper_clientconn_options_http1_allow_multiline_headers name seems preferable to me, since it is an HTTP/1 specific option. I think just running the gen_header.sh script should fix it up for you.

Fixed in new commit.

Would you want to add the usage in curl? If not, I can a little later, but just checking first.

I tried to add it yesterday, and noticed that curl expects the format of multiline headers to be a little different than hyper treats them, so it'll be more work than expected. I'll need to file an issue on the curl repo.


Feature request - Add skip-deps field to not include dependencies

I apologize if this isn't the place to open feature requests. Let me know if there is a better place.
Feature request
The Diff struct used by oc-mirror includes a SkipDependencies boolean which allows the curated catalog to not pull in the dependencies of the specified package. We have an edge use case that could like to take advantage of this option to be able to create an ImageSetConfiguration object with the exact versions of each dependency in the stack to ensure the same curated catalog is created whether it's run today, tomorrow, or next week.
I would expect that to align with the Diff struct, this property would be global for each catalog in an ImageSetConfiguration. For example, you can't specify that you don't want the dependency resolution for one package in a catalog while saying that you want it for others. It's an all or nothing situation.
Example usage:
apiVersion: tmp-redhatgov.com/v1alpha1
kind: ImageSetConfiguration
mirror:
  operators:
    - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.8
      skipdeps: true
      packages:
        - name: elasticsearch-operator
          versions:
            - '5.2.3-31'

Again, let me know if this is the wrong place to be requesting this or if you need more information.

Hi @nschambu, This is the perfect place for feature requests. I'll leave the details here to @estroz and @jpower432.

@nschambu can you recreate this feature request in operator-registry since the diff lib is maintained there? Thanks! We can keep this open to track dependency updates.

@estroz, sure, I can do that. Just to confirm, though, I think the diff lib already supports this. opm alpha diff has a --skip-deps flag that results in a catalog only containing the packages specified in the include file.

Sorry I meant this bit specifically

For example, you can't specify that you don't want the dependency resolution for one package in a catalog while saying that you want it for others. It's an all or nothing situation.

You are correct that you can skip dep inclusion wholesale and selectively pin dep versions right now.

Ah, got it. Thanks for the clarification. I'll create the feature request for that over there. I will say that I would put that feature as a lower priority than adding the capability to oc-mirror.

Agreed. Skipping deps globally is coming fairly soon.


ros_canopen: 0.7.9-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository ros_canopen to 0.7.9-0:

upstream repository: https://github.com/ros-industrial/ros_canopen.git
release repository: https://github.com/ros-industrial-release/ros_canopen-release.git
distro file: lunar/distribution.yaml
bloom version: 0.6.4
previous version for package: 0.7.8-0

can_msgs

No changes

canopen_402
* fix initialization bug in ProfiledPositionMode
* Contributors: Mathias Lüdtke

canopen_chain_node

No changes

canopen_master
* provided KeyHash
  for use with unordered containers
* added c_array access functons to can::Frame
* Contributors: Mathias Lüdtke

canopen_motor_node
* introduced HandleLayerSharedPtr
* Contributors: Mathias Lüdtke

ros_canopen

No changes

socketcan_bridge
* compare can_msgs::Frame and can::Frame properly
* Contributors: Mathias Lüdtke

socketcan_interface
* introduced ROSCANOPEN_MAKE_SHARED
* added c_array access functons to can::Frame
* Contributors: Mathias Lüdtke

Holding for Melodic release.