On Ubuntu 23.04 - VSCODE is failing saying SDK is not installed.

Does this issue occur when all extensions are disabled?: Yes/No Yes

VS Code Version: 1.82
OS Version: Ubuntu 23.04

Steps to Reproduce:

Do a clean install of .NET SDK : sudo apt-get update &&
sudo apt-get install -y dotnet-sdk-7.0
Install completes successfully
Run dotnet --info => its says NO SDKS FOUND
Host:
Version:      7.0.11
Architecture: x64
Commit:       ecb34f85ec

.NET SDKs installed:
No SDKs were found.
.NET runtimes installed:
Microsoft.AspNetCore.App 7.0.11 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 7.0.11 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
None
Environment variables:
Not set
global.json file:
Not found

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I have the latest - reinstalled many many times

I suggest reaching out to .NET support: https://dotnet.microsoft.com/en-us/platform/support


[Bug] Inline Key:: Values don't work in middle of statements

I've this query in a file,
TABLE HbA1c
FROM "Daily"
WHERE HbA1c

And in two of my daily notes, I have HbA1c::  but consistently, only one of them is picked up by the query.

The value from the first file is always ignored.
Here's what I tried to fix it,

Copied HbA1c:: 8.1 from second file to first and it showed up.
Copied entire working line from second file and it showed up.
Matched formatting for both, the first had a divider and transcoded note below which I removed so in both files the Key:: Value is the very last thing. Still failed.

After a lot of trial and error, here's what worked: adding a period before the key:: value or putting it in a new line by itself.  So,
- [[Father]] got his HbA1c:: 15.1 doesn't work.
whereas,
- [[Father]] got his. HbA1c:: 15.1 works
and
 - [[Father]] got his.
 - HbA1c:: 15.1

works as well.
Also, if something follows the value, that is always taken as the entire value. So if I write HbA1c:: 15.1 report today, it will fetch 15.1 report today. Even if I try to delimit it using quotes like HbA1c:: "15.1" report today, it gets "15.1" report today

I should probably reconsider renaming "inline fields" to just "fields" and adding a separate convention for actual "inline fields" - an inline field has to be on it's own line - everything before the :: is the key, and everything after is the value.
The reason for this limitation is having an inline key in the middle of a sentence is ambigious without strong conventions: i.e., hello there:: how are you could be parsed as there -> how or hello there -> how or hello there -> how are you and so on. This gets worse with things like commas (which are used to write lists), and so on.
If you have a reasonable convention I can add it as an additional special case.

Yes I understand the ambiguity that can arise from this. Is there a reason why delimiting can’t work? I think if for both keys and values, there was a requirement that they be in quotes if multi-word could solve most of it no? Either that or enclosing the entire pair inside an inline code block?
Speaking of special conventions, I happen to try this and was very pleasantly surprised that it worked. I have a lot of entries in my journal where I used the tag #watched usually followed by what, a YouTube url or a link to a movie note. So #watched:: Inception working is wonderful. The query of course needs the key watched without the #. The tags solve the problem of multi-word keys, or at least have a convention that they need underscores or dashes. In my case the entire rest of the line is useful so it’s perfect as it works now but I can definitely imagine use-cases where people might want to limit the value.
Using tags for keys this way has another advantage that this makes them more portable since I can view and search by tags in any markdown app whereas only Obsidian has the brilliant Dataview. While delimiting the entire pair using inline code could make it more readable in the middle of the line as in my example, I think hashtags could be most useful in the long run, speaking this after converting a lot of my #tags to #tags:: and noticing the ease of use already.

For reference, you can now use truly inline fields of the form [key:: value] to put inline values anywhere in text. They will be rendered prettily in preview mode as well.


Update README.md export command

Quoting DATABASE_URL content variable prevents an issue from the command export. In case of a string (i.e. password) with given characters (i.e. '('), it can make the command fail. Quoting it prevents that from happening.
The issue happened on MacOS with an M1 chip.

thanks!   The irony of this is that double quotes would still process dollar signs $, back slashes \, and double quotes ", so in theory wrapping with single quotes is somewhat safer... except that in that case you would have to handle the single quote escaping :)


shouldPlaceholderFloat doesn't work

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Place holder should not float on focus.
What is the current behavior?
Placeholder floats on focus.
What are the steps to reproduce?
using master latest, this does not work to stop floating placeholder and it should based on docs:
<mat-form-field>
  <input matInput type="text" placeholder="Alias name" shouldPlaceholderFloat="false">
</mat-form-field>

try with [shouldPlaceholderFloat]="false"
Without [] you pass false as a string.

Closing as this should be managed through mat-form-field

https://material.angular.io/components/form-field/overview#floating-placeholder

shouldPlaceholderFloat: boolean is deprecated. Not sure if there are any other alternatives..

You can use floatLabel: FloatLabelType now.

What are the possible values of FloatLabelType ?

@trsh
'always' | 'never' | 'auto'
https://github.com/angular/material2/blob/d6fec3573cbc854d5bf67d920c5b0f8a6eef0c86/src/lib/core/label/label-options.ts#L16

Should be added to docs properly

For anyone curios, if you actualy dont want floating placeholder OR floating label, use this:

Very badly described in the docs, sadly!


When Split Not Able to Eat

When a player splits, no matter how large, he is not able to eat another player.
If you center your split blobs just right over the other player (like close all of your circles in on the other player), then you are able to eat the other player.
I also want to know how to make the eating more sensitive, so less of the player has to be in the other so that he gets digested.
Is there a known fix, or does anyone know how to fix this bug?
Thanks!

You can update the code below at line 600 server.js to fix the killing bug:
var otherUsers =  tree.get({x:currentCell.x, y: currentCell.y, w: currentCell.radius * 2, h: currentCell.radius * 2}, check);


Configure an HMR update strategy for multiple files

Clear and concise description of the problem
When developing a library with HMR support, I want to be able to support HMR with the least code from the end user
Suggested solution
When working with a library that is meant to be used in many files like Pinia for Vue, each HMR code needs to be placed inside of the store file to be able to handle the HMR. If placed outside, let's say in the main.ts entry point, you need to manually import all of the stores (using a glob doesn't seem to work):
import { acceptHMRUpdate, defineStore } from 'pinia'

export const useCounter = defineStore({
  // optios
})

if (import.meta.hot) {
  // acceptHMRUpdate creates a function that handles the update of the store in place
  import.meta.hot.accept(acceptHMRUpdate(useCounter, import.meta.hot))
}

That useCounter is imported in Vue component or JS files all across the app.
When reading the docs, I feel like this limitation is intended but it makes it quite cumbersome to add HMR support for stores. It would be nice if we could do something like this in the entry point or one single file of the app:
import.meta.hot!.accept(import.meta.glob('./stores/*.ts',
(newModule) => {
  // handle the update
})

Alternative
I tried importing all of the modules with a glob in the entrypoint (main.ts) but that doesn't work:
// src/main.ts
import { acceptHMRUpdate, createPinia, isUseStore } from 'pinia'

// rest of the code

if (import.meta.hot) {
  const stores = import.meta.glob('./stores/*.ts')
  for (const filePath in stores) {
    console.log('configuring HMR for', filePath)

    stores[filePath]().then((mod) => {
      for (const exportName in mod) {
        const storeDef = mod[exportName]
        if (isUseStore(storeDef)) {
          console.log(`Detected store "${storeDef.$id}"`)
          import.meta.hot!.accept(
            filePath,
            acceptHMRUpdate(storeDef, import.meta.hot)
          )
        }
      }
    })
  }

It doesn't even enter the function returned by acceptHMRUpdate().

I imagine that creating a vite plugin to rewrite all of the files in a specific folder to add support for HMR is possible but it means users need to add a vite plugin when installing the lib and differently from .vue files, stores have js or ts extensions, so they need to be filtered based on their content.
Additional context
The code from above is testable at https://github.com/posva/pinia/tree/test/globalhmr with yarn play. The source code is located at playground/src and src/hmr.ts
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I am a pinia fans. 😀 I am interested in solving this issues.
the accept types is
accept(deps: readonly string[], cb: (mods: any[]) => void): void

the first params is the source file deps, I think you need a function like:
accept(source: string, deps: readonly string[], cb: (mods: any[]) => void): void

so you can add the source hmr callback on the main.ts. If in line with expectations I will go to do it.


Add Repository - inconsistent package name

URL of codelab:
https://developer.android.com/codelabs/basic-android-kotlin-compose-add-repository?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-5-pathway-2%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-add-repository#2
In which task and step of the codelab can this issue be found?
Step 3 - create data layer
Describe the problem
User is asked to create a package named "data", but it's called "model" in the sample code. See the screenshot.

Sorry I was confused as this is not the package name but an import statement.


XP-tracker: killcount when fighting controlled

When training melee combat with controlled instread of focusing on either Defence, Strenght or Attack you still get the kill count for when you're focused.
Example, a Moss Giant got 60 HP, he's worth 240 XP per kill. If you need 480 XP to level when training on a focused stat (Def / Str / Att) it correctly states "2 kills remaining" (but with the correct format).
But if you're training controlled it still states "2 kills remaining" even tho the XP is split 3-ways which means you need 6 kills to level up all three skills.

Duplicate of #6576


Chemical crystallizer - missing clear button

At some point, the chemical crystallizer lost the clear button. I don't think this was intended, so here's a bug report, lol. And yeah, I'm stuck... only way to resolve the issue is to build a new one, as it retains the fluid/gas when breaking

I actually have that button in the latest Mek version...

Thanks for your comment and help, Dawnflash! Not sure if I'm brave enough to actually try the workaround, lol - I'm op on the server so I'll probably just give me a new crystallizer. :) Hopefully the issue will be fixed on future versions. Really annoying for people without op and/or technical skills.

Shift-click the gauge with a gauge dropper, it will clear all its contents :)


TypeError: 'undefined' is not a function (evaluating 't.encode.bind(t)')

My internet connection is extremely slow, so I set HUBOT_LOG_LEVEL to debug to see what the problem was. After modifying the default timeout length to 3 minutes instead of 50 seconds, I noticed this error in the console.
phantom stdout: TypeError: 'undefined' is not a function (evaluating 't.encode.bind(t)')
phantom stdout:   https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324
  https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324
  https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324 in g
  https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324
  https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324 in g
  https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324
  https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324 in g
  https://swx.cdn.skype.com/v/1.24.74/js/fullExperience.min.js:324

(same lines as above repeated a couple more times)
It eventually times out, logs ERROR Error: SkypeWeb adapter failure in initial login! and produces the following image:

I've been able to reproduce this every time. I'm using OS X El Capitan, with Node installed from Homebrew, NPM installed separately (not by homebrew) and phantomjs installed by NPM.

I just noticed that there's a duplicate bug (#10). I'm going to close this.


blog/{blog-identifier}/following API

I am trying to use this api:
https://www.tumblr.com/docs/en/api/v2#blog-following
but It seems as though it is not implemented in pytumblr so I wrote this
        url = '/v2/blog/%s/following/' % blog_name
        response = get_client().send_api_request("get", url, values, ["limit", "offset"])

however, I always get a 404 error.  Is the documentation missing something?

Exactly. Maybe this interface has been removed.


Redirect drain events from unzip to the original response

https://github.com/langjt/node-http-proxy-json/issues/16

@matdurand @atlanteh Thank you for your PR


[e2e]: container-based workflow_dispatch main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11063794436
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container-based.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container-based.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Fri Sep 27 03:06:40 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11080549097
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container-based.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container-based.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sat Sep 28 03:28:12 UTC 2024
Tests are passing now. Closing this issue.


🌦 Allow partial CA store to be loaded

This change more closely mimics the setup we previously had with hyper_rustls, and allows Viceroy to be used even if only some root certificates could be loaded.
I believe this change will address #103, but we will have to test it to be sure.

Took your suggestions, re-✅?


Widbata:  Battery level in the current theme

its also a smaller widget at 27 pixels wide.

Thanks! I thought pretty much all the widgets used the current colour theme? Or is it that this one is just black and white so matches exactly?

The majority and a fixed GREEN interior.
This one os a bit smaller, black and white only and switches over with a
change in themes.
On Mon, Dec 6, 2021 at 8:54 AM Gordon Williams @.***>
wrote:

Thanks! I thought pretty much all the widgets used the current colour
theme? Or is it that this one is just black and white so matches exactly?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/espruino/BangleApps/pull/1007#issuecomment-986566331,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3WLEPASLMLVRSSP7YFOKTUPR26FANCNFSM5JMXUNWA
.


Pre 17L data SNC

I've taken the liberty to parse the aggregated data from a reddit post into a SNC json for my local copy of limitedgrades. Maybe you want to use it, maybe you don't.
snc.zip
(or pastebin at https://pastebin.com/DpXPjyQH )
https://old.reddit.com/r/MagicArena/comments/udry9t/someone_compiled_snc_limited_ratings_but_didnt/

Hey there, thanks for compiling that data. I could see this site eventually incorporating community grades, but I'm not sure how to implement a Web UI that displays them elegantly.
Let me think about this some more. It would be pretty cool to get grades based on 17Lands alongside community grades as well.


I can not modify the scroll direction bydir = "rtl" when moving vertically

I can not modify the scroll direction bydir = "rtl" when moving vertically,do we have other ways to change scroll direction when moving vertically?

RTL directing doesn't mean to be used for vertical direction. No, there is no way to change scroll direction, or you can set initialSlide as the last one


Jio tv is not working in kodi

Your Environment

Add-on name: [e.g. Jiotv]
Add-on version: [e.g. 2.0.0]
Kodi version: [e.g. Kodi 19]
Operating system version/name: [e.g. Windows 10, LibreElec 9.0, etc...]
Using from country: [eg. India, USA, etc...]

in jio tv not a single channel works i have a jio fiber but still its not playing any channels
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See an error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Debug log

The debug log can be found from this link:

Working good on Amazon Fire TV Stick 3rd Gen with Kodi Matrix v19.0 + Jio TV Add-on (updated 21 Jan 2023) + Jio 4G LTE Mobile Hotspot.
All Live TV channels and catchup are working good and without any buffering or delay.


Add district office data

This adds district office data for current Members of Congress, as discussed in #343 .
Contains a list of offices for each MOC, with address, phone, and fax (where available). Entries are keyed by bioguide, thomas, and govtrack ids (as is done with the social media data).

Sorry, did not intend for the last change to be included in this pull request. I closed it and will open a new request if/when we're able to address the issues in #343.


add fixes from the maxent paper

Just in case, please don't merge

Having a generic moo class would be so nice.
BTW the moo task did not support having the FR in an order other than the default...


Remove s:last_modified_signs.

Does that variable have a purpose, or is it just a leftover?
This commit removes all occurrences of this variable, since it can only have the value {}, but maybe there is a detail I am not aware of.
Edit: same remark for s:modified_signs.

good catch!


chore: DevEx updates

Please add a one-paragraph summary here, suitable for a release notes description. This will help with documentation.

Overview

Merged the jest configs and used the projects feature of jest to split up the two different sets of tests. The jest:unit and jest:component scripts can still be used to run the separate collections of tests. Running npm test will now run all tests. This simplifies our git hooks, workflows, and fixes an issue where we could not debug the component tests in VSCode.
Broke up the webpack config into separate chunks to make it easier to manage.
Removed unused build types from webpack and simplified the naming process for output files.
Re-ordered the npm scripts and removed unused ones.
Moved the scripts that need to run after webpack out of the tools/scripts directory and into tools/webpack/scripts.

Related Issue(s)

https://issues.newrelic.com/browse/NR-141670
Testing

You could run the different builds and verify the files generated in the build directory.

The size check job is expected to fail on this PR since I renamed the json/html stats file.


[feat] Add a color picker eyedrop

Describe the feature
Select a color by eyedrop

#89 covers this so I'll merge this and close


ARTEMIS-1780 Handle conversion of large ObjectMessage types

Make sure the correct buffer is used when decoding the stored Core
message that originated from the conversion of an AMQP message sent and
annotated as a JMS ObjectMessage which trips the large message boundary.

nice catch, but There are test failures on the PR that are apparently real.
@tabish121 can you look please?

I updated the patch to remove the duplicate decode which seems to have been the root cause of the other test failure.


Swapped parameteres in the sample script!

In the sample scripts restore command, two parameteres are swapped
-TargetInstanceDatabaseName $TargetInstanceName `
-TargetInstanceName $TargetDatabaseName
Should have been:
-TargetInstanceDatabaseName $TargetDatabaseName
-TargetInstanceName $TargetInstanceName

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

ID: 578ef41f-120a-a750-1340-180f7bb5f236
Version Independent ID: b27025dc-5025-af3a-3121-d2e285236fe0
Content: PowerShell example Restore Geo-backup - Azure SQL Database - Azure SQL Database
Content Source: articles/sql-database/scripts/sql-managed-instance-restore-geo-backup.md
Service: sql-database
Sub-service: backup-restore
GitHub Login: @jovanpop-msft
Microsoft Alias: jovanpop

@dennisknappe We are checking this and we will get back to you.

@dennisknappe We have created pull request to correct this.
@jovanpop-msft @stevestein Please check PR https://github.com/MicrosoftDocs/azure-docs-pr/pull/96482 and update


GEODE-4858: Update *DiskStore commands to use ResultModel and SingleGfshCommand

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

precheckin is green

@jdeppe-pivotal Seems like this is bad now. Since it's so close to the finish line, do you want to fix it and get it merged?

@jinmeiliao  @sboorlagadda @pdxrunner @PurelyApplied - if you have some time I'd appreciate a review so that this can finally be merged. Thanks!


Feature Request - Dead Link Checking by Default

I just added this functionality using HTML-Proofer to my own blog, and found a bunch of issues on a relatively small, simple site. I'd imagine most people would want this, but don't think of it/know it's available. Would it be possible to include an HTML-Proofer pass in after_build (rescuing errors to prevent workflow breaks) by default in the next version?
Downside: adds network calls and time to proof the build
Upside: significantly improves Middleman sites' quality by being on-by-default.
The downside of HTML-Proofer is that it checks the build instead of the source, so one error may appear multiple times (if, for example, a link was broken in the footer). There are many ways to create a link in source, so if someone made a new tool to check links in md and erb files it might not be as reliable. So it's a tradeoff but probably a necessary one.

Or maybe a command line argument?

I think this is best suited as an extension - https://middlemanapp.com/advanced/custom-extensions/
Certainly a useful tool.

Agreed


[DNM] qemu: Fix virtiofsd crash on RHCOS

This will fix a failure of virtiofsd trying to mount a directory on
temporary filesystem that might be read-only. It is the case in RHCOS
which has virtiofsd crashing with "operation not permitted".
Cherry-picked the following commit from QEMU:

virtiofsd: avoid /proc/self/fd tempdir (commit ebf101955ce8f8d72f)

Fixes #1176
Signed-off-by: Wainer dos Santos Moschetta<EMAIL_ADDRESS>

I tested the fix proposed on this PR on Openshift 4.6. Worked out!

@c3d You may be interested on reviewing this.

thanks @wainersm - can you forward port it ?

Interesting, I thought we were already using QEMU 5.1 on 2.x. Sure, I will forward port it then.
@devimc are you able to trigger the obs-packaging-ci job on my behalf?
Thanks for the review!

The reason why I moved to Do Not Merge:
While forward porting to 2.x I realized that the patch does not apply on upstream QEMU 5.0 tree, whereas on virtio-fs's QEMU (branch qemu5.0-virtiofs-with51bits-dax) it does. I will investigate how to handle that conflict.

/AzurePipelines run

I updated the patch so that the fix won't be applied on our build of the upstream QEMU 5.0.0.

As it's a do-not-merge, let's close it as it won't make its way into the final 1.13.0 release.


Offer to help maintain this package

Hey! I'd like to offer to help maintain this package, if you are interested.

Friendly ping

@mitchellwrosen : This is very much appreciated, I think a version of unix-compat working with unix-2.8 is urgently needed.
I sent the following email now (2023-01-18) to jacob stanley io:

Dear Jacob,
thank you for maintaining unix-compat!
The current unix-compat-0.6 does not work together with unix-2.8 which will soon become mandatory (GHC 9.6 alpha is already out).
Would you be able to release unix-compat-0.7 which works with unix-2.8 soon?  This would greatly help the Haskell community to prepare for GHC 9.6!
If you are not available now, maybe you can accept help?  It has been offered here:
https://github.com/jacobstanley/unix-compat/issues/63
There is also already a PR fixing the problem:
https://github.com/jacobstanley/unix-compat/pull/62
The minimal action needed to get a co-maintainer going is to add them on Hackage:
https://hackage.haskell.org/package/unix-compat/maintainers/
(But preferably also give them write access to github.com/jacobstanley/unix-compat.)
Best regards,
Andreas

Thanks for doing that @andreasabel, any response?

Thanks for doing that @andreasabel, any response?

No.  I think you can go to step 2 of the takeover recipe:

State your intention to take over the package in a public forum (we recommend the haskell-cafe and/or libraries list). CC the maintainer.

Thanks for the link, I've sent an email to<EMAIL_ADDRESS>

... well, I tried to, but I don't see my email anywhere in the archives: https://mail.haskell.org/pipermail/haskell-cafe/2023-February/thread.html
So maybe it has to be manually approved by someone first, or maybe I don't understand how mailing lists work. 🤷♂

I didn't receive your email either on haskell-cafe.
But you had posts there previously, last in 2016, with id: Mitchell Rosen (mitchellwrosen gmail com).

I'm not sure what to make of that. Here's a screenshot of the email I sent, which didn't bounce or anything.

Maybe just resend it, to both the cafe and the libraries list.  I also looked at https://discourse.haskell.org/ but it seems takeover requests are not published there.

Takeover request announced 2023-02-04 on Haskell cafe: https://mail.haskell.org/pipermail/haskell-cafe/2023-February/135910.html

@mitchellwrosen proceeded with the next step on 2023-02-21.

Send an email to the hackage administrators (hackage-admin@haskell.org), with a link to the public email thread.

Hehe, thanks for taking the minutes during all of this @andreasabel

added to maintainers. 👍

Excellent, thank you!

@mitchellwrosen : You can do a hackage upload now.  But hopefully @jacobstanley will show up for one of these:

Take up maintenance again.
Add you as co-maintainer here on this repo with write access.
Transfer this repo to a new location where you have write & admin access.

This is to ensure the continuity of issue numbers, for instance.

Indeed, that would be great. However, in the meantime, I don't see a great path forward other than forking the repo and pointing people away from this one.

@andreasabel Good idea. What do you think about making an org to house both of these orphaned packages, and possibly others? Something like haskell-community/?

In this case, it could maybe go directly to https://github.com/haskell (it already has unix).
Or, if you prefer a less ambitious home, https://github.com/orgs/haskell-pkg-janitors .  This one started out great, but currently only has haskell-src actively maintained (and lots of passive founding members).
I would prefer reactivating haskell-pkg-janitors over making a new organisation with similar goals.
Btw. see discussion at

https://github.com/haskellfoundation/stability/pull/12

Great, haskell-pkg-janitors sounds like an excellent home for now.

Ok, did that!


Auto culling isn't working on TileSprite

Due to a slight difference (certainly a mistake) in the _renderWebGL() and _renderCanvas() implementations of PIXI.TilingSprite, auto culling isn't working on Phaser.TileSprite.
The reason is the Phaser.AutoCull component use the renderable propertie to disable object rendering and  PIXI.TilingSprite doesn't test it before starting the rendering process.
This is the PIXI.Sprite _renderWebGL() method :
PIXI.Sprite.prototype._renderWebGL = function(renderSession, matrix)
{
    // if the sprite is not visible or the alpha is 0 then no need to render this element
    if (!this.visible || this.alpha <= 0 || !this.renderable) return;

With PIXI's sprites, renderable is checked. No problem.
PIXI.TilingSprite.prototype._renderCanvas = function(renderSession)
{
    if (this.visible === false || this.alpha === 0)
    {
        return;
    }

But PIXI's tiling sprites, will be rendered even if their renderable propertie is set to false.
Hope this help.

Thanks - fixed in dev.


Updates to loading and usage of pretrained ViTs from HuggingFace

This PR comprises of the following updates to the usage of pretrained models from huggingface:

Finetuning w/ new classifier head if num_classes don't match the classifier head of the pretrained model
export hf model config in prisma config format

This looks great! Could we add some comments that this is specifically for HF models? We also have timm ViT models that we'll have to load in too, and convert their config to the Prisma config. I like that you included that function btw.
It may be possible to load timm models through Huggingface, which in that case, this doesn't apply. Normally I load timm through
orig_model = timm.create_model('vit_base_patch32_224', pretrained=True)


About carla connection

I am quite new sorry, but how to connect with my Carla Server for manual control?

You need to make a node that gets ego_vehicle's control_cmd using PythonAPI and publish the wheel angle to this custom msg.

And I added the test code to sync the vehicle in the carla (rolename="hero" or "ego_vehicle").
Try python3 examples/carla_control.py


[Yeelight Component] Small improvement + added new effect

Converted majority of effects from ifs to dict map, which makes it easier to extend in the future. Also, added LSD effect!
The effect documentation: https://yeelight.readthedocs.io/en/latest/yeelight.html#yeelight.transitions.lsd

Hi @pagenoare,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Creating new areas by editing the configuration.yaml has no effect

Having added magic_areas successfully, restart and observe that areas exist:
magic_areas:
Now create (or edit) areas by editing the configuration.yaml, and restart.
magic_areas:
  the_new_or_existing_area:
     include_entities:
       - binary_sensor.front_door
       - binary_sensor.entrance_motion

Nothing happens, after restart the_new_or_existing_area does not exist.

Or, in the case of an existing area, the entities mentioned in configuration.yaml are not added to the existing magic config

Areas should be created on the area registry only. The configuration entry is only for configuring said area.
For existing areas, make sure the area slug is correct. You can verify this by checking the created sensor name. Please provide more information so I can help debug what's going on.

The magic sensor area_hallway has been magically created and I can see it in the developer tools, defined as:
binary_sensor.area_hallway

presence_sensors:
  - binary_sensor.entrance_motion
  - switch.area_presence_hold_hallway

I want a binary door sensor exposed via MQTT to be included in the magic area so in the configuration.yaml I have:
magic_areas:
  area_hallway:
     include_entities:
       - binary_sensor.front_door

But the front door sensor is still not included in the sensor after a restart.

Oh that's because door device class is not included by default. Check the presence_sensor_device_class documentation on Readme. You have to add this entry with all the device classes you want. This overrides the default so make sure you add them back too.

Also the slug is without area. In your case would be just hallway

It works as you have described. Thank you for your help which resolved my problem.
magic_areas:
  hallway:
     presence_sensor_device_class:
       - door
       - motion
     include_entities:
       - binary_sensor.front_door

Now the hallway magic area contains both the magically discovered area sensors AND the added door sensor, this is correct.
binary_sensor.area_hallway

binary_sensor.entrance_motion,
binary_sensor.front_door,
switch.area_presence_hold_hallway


fix: fix peer dependencies issue on node 18

Changes the format of this project peer dependencies fixing an error in node 18 (see error image below)

https://nodejs.org/en/blog/npm/peer-dependencies

@james-owen I think those checks are at the branch settings level, I'm not able to merge the PR due to those requirements, would you please merge it for me if you can?


mixin: Allow excluding individual components through configuration

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
Allow excluding individual components alerts/dashboards through mixin configuration.
Verification
Since by default all should still be included I tested that this is the case by re-generating the examples that are checked into this repo.
@kakkoyun @metalmatze

Some of the dashboard files (eg rule.libsonnet, receive.libsonnet) use the rule.title, receive.title to contribute to __overviewRows__. I believe this makes using this feature to exclude the components impossible. I suppose __overviewRows__ could use the same conditional logic?

@andrewgeller Thanks for pointing that out. The initial idea was to build up your own set of entry point by including or excluding these component-based files. Now we kind of steered away also an additional path which is fine, as you pointed we should address the issues if we caused any troubles. Could you open an issue so that we don't forget this? Or better a PR with a fix would be awesome 🤗


Tricycle controller

Hey! We at Pixel Robotics recently started our migration to ros2_control. We are in the process of creating a tricycle controller and decided to contribute back.
This PR is not yet complete but we wanted to get a first feedback round already.

Random question, out of curiosity:  does this work for (steered wheel in the front, 2 in the back) as well as (2 wheels in front, steered wheel in the back)?

Isn't what you described the same configuration turned around?

Hi @arne48. I do agree that the tricycle controller might be a special case of a more general ackermann controller that can be achieved with additional configuration.
However, I think we could add a tricycle controller as a first step and see from there how to generalize it to ackermann. I am given the time to work on the tricycle configuration because this is what my company uses; I'm not sure I'll have time to work on an ackermann controller right now and I think it would be a shame to lose this initial effort, which can be easily extended.

if the ackermann-steering-controller should come, those temporary controllers and there replacement would cause problems in future releases where this controller then got replaced.

I totally understand this point now. It's my first time contributing to a project where breaking changes affect many people so I didn't give it much thought :sweat_smile:.

While investigating on how to turn this into a more general-purpose ackermann controller I stumbled on http://wiki.ros.org/steer_bot_hardware_gazebo.
Their approach for navigating an ackermann vehicle was to generate tricycle commands with a tricycle controller (similar to the one in this PR) and transform these to ackermann commands in the hardware interface.
Do you consider the transformation tricycle->ackermann to be the responsibility of the controller or the hardware interface?
@bmagyar I'd appreciate guidance on how to continue with this PR.

Any chance of this PR going forward or should I simply close it? Frankly, I don't know if the maintainers are overwhelmed with work but I'd appreciate a simple answer if you want people to keep contributing.

@bmagyar I think we should add this controller. As it seems that in the meatime the efforts for general Ackermann controller are currently are currently stagnant, so this controller could cover most use-cases and therefore has a stand-alone value.
Plus it is rather simple and shouldn't be too hard to maintain especially because I would guess @tonynajjar at Pixel Robotics will continue to use their controller and might have a look at  potential issues that arise.
So can we proceed to integrate this controller into the package?

Also please rebase this PR against the latest master branch

Thanks for the review @bmagyar. I synced to master and also added our latest changes which were on a different branch.
This PR still needs some work, not everything is well tested, now that I have your confirmation that this is the way forward, I can work on that. Will request another review once it's ready.

You might have noticed that the rate limiters actually limit the steering angle and traction speed as opposed to the Twist (e.g in the diff drive controller). I think that Twist limiting should be done in the local planner/controller (e.g TEB does it).
I implemented it like that mainly so that our gazebo simulation could be more realistic, e.g so that the steering angle change is slower. Rate limiting on our real motors is not needed as they have that feature built-in.
Happy to hear opinions.

Ready for review again, I made a demo also so you can try it out: https://github.com/ros-controls/gazebo_ros2_control/pull/145/files

@bmagyar is there anything in the tests I need to fix? I think the failures are not related to my changes

Hi, can I know what is still needed to move this forward? It's in the back of my head for a long time now.

:ship:
Thanks for sticking through the process!

@bmagyar thank you for the review and thank you @pixel-robotics (@jplapp) for financing the time put into this. Looking forward for community feedback and improving it


Upgrade to Celery 3.1

Celery now has built in support for Django so the use of djcelery would no longer be needed. Upgrading rtd to this version would enable rtd to use the Celery API directly and no longer tie the use of the celery command to manage.py.

That surely would be good as djcelery will fade away in the long run I guess. Do you know of any pitfalls that we might encounter when transitioning?
Is that something you are interested in working on? We would really appreciate any pull requests in that regard. I think it's not high in priority on our end to make the change as long as everything works. But I'm happy to review any pull requests in that regard.

We are upgrading to celery 3.1 in the process of #1420
However we won't make go djcelery go away in that. That's still and open issue.

@gregmuellegger @ericholscher Can this be closed given that #1420 has been merged?

Closing because #3237


Rendering stats overlay disappears on reload

Repro:

Open devtools
Go to rendering tab and check Frame Rendering Stats

Should see this:

3. Reload, 🐛 it disappears until it's unchecked and checked again
If this is easy to fix I could have this on nearly all the time

@balaji-sivasakthi you can try, I suspect this involves Electron though so I expect it to be quite complex/cross-project.

@balaji-sivasakthi first step would be create a minimal repro with https://www.electronjs.org/fiddle and file a tracking issue in  https://github.com/electron/electron

@deepak1556 @Tyriar  https://github.com/electron/electron/issues/39468

@Tyriar @deepak1556 Actually, the Electron team closed the issue. It was a chromium bug so, we should file an issue in chromium.
But for now, What I'm thinking is why don't we reload the devtool in  "Reload window" event by using isDevToolOpened().

@balaji-sivasakthi the stats disappearing is relatively minor and toggling devtools is a very heavy way of working around it, so following up with Chromium if that's the cause would be the way to go.

@Tyriar I've filed an issue in Chromium https://bugs.chromium.org/p/chromium/issues/detail?id=1473964


Use of spring-restdocs/asciidoctor instead of swagger/springfox.

Saw that you all had to remove springfox due to security vulnerabilities. Did some research, and the latest version of springfox still has the vulnerabilities in question. Fortunately, spring-restdocs has no such issues. This PR is an implementation of rest documentation using spring-restdocs instead of swagger/springfox.

@pcarney8 @InfoSec812 @pabrahamsson thoughts?

@etsauer This same issue with springfox shows up on https://github.com/redhat-cop/container-pipelines/issues/76.

resolves #39


feat(all): moved EnvService to commons + exposed getXrayTraceId in tracer

Description of your changes
TBD
Fixes #1070
How to verify this change

Related issues, RFCs

Issue number: #1070
PR status
Is this ready for review?: NO
Is it a breaking change?: NO
Checklist

[x] My changes meet the tenets criteria
[x] I have performed a self-review of my own code
[x] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding changes to the examples
[x] My changes generate no new warnings
[x] The code coverage hasn't decreased
[x] I have added tests that prove my change is effective and works
[x] New and existing unit tests pass locally and in Github Actions
[ ] Any dependent changes have been merged and published in downstream module
[x] The PR title follows the conventional commit semantics

Breaking change checklist
N/A

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

E2E tests run: https://github.com/awslabs/aws-lambda-powertools-typescript/actions/runs/3271574957


Support TypeScript's new link format in terminal

Format from TS 4.5:

<relative file> <line>:<col start>-<col end>
<relative file> <line>:<col start>-<col end> <line#2>:<col start#2>-<col end#2> (stretch goal: not sure how to handle multiple lines?)

Looks like they changed it to something more common, unless I'm just not hitting the proper case to get that to print out


[FLINK-21899][table] Introduce SOURCE_WATERMARK built-in function to preserve watermark from source

What is the purpose of the change
The SOURCE_WATERMARK function doesn't have concrete implementation. The eval() function should throw a meaningful exception message to indicate users the function should only be used in DDL to generate a watermark preserved from source system.
Brief change log

Add SOURCE_WATERMARK BuiltInFunctionDefinition.
Add SourceWatermarkFunction scalar function which throws exception in eval() method.

Verifying this change

Add tests to verify the exception in TableSourceITCase.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @leonardBang


Add show ticket option

Ticket should be store and retrieve on the basis of employee code. :+1:

Sir, I'm looking forward to take up this. It would be more useful if you're more specific.

Hi, is this issue in progress or can I work on it.

you can work.
go ahead. :+1:

I'll start to work on this

Okay.

Hey Pawan, when i tried to open the app it is asking for employee code

enter 0000

You can get all these in Savedseats class


feat: add partition id to flow

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
https://github.com/GreptimeTeam/greptimedb/issues/4268
What's changed and what's your intention?
add partition id to flow, currently unused but will be used soon in future
Checklist

[ ]  I have written the necessary comments.
[ ]  I have added the necessary unit tests and integration tests.

Close for now, will redo this part when need to parallelizing flow task


Example of How to Send Image

Can someone please provide an example of how to send an image with the notification? I haven't been able to figure out how to do it.  The below does not show an image in the notification.
let message = FCMMessageDefault(     topic: "test-topic",     notification: FCMNotification(title: title, body: body),     apns: FCMApnsConfig(         options: .init(             analyticsLabel: "label",             image: "https://firebasestorage.googleapis.com/v0/b/sweetliliestest.appspot.com/o/lacos%2F1722574617287-4BYAh.jpg?alt=media&token=a5cc6580-cf55-4ded-a4ef-7b1a2351b4bc")     ) )

Have you already implemented Notification Content and Notification Service extensions? If I understand the task correctly, this is only possible by implementing these custom targets to process the incoming push and display it with the image. In these targets, you will be able to retrieve the link to the image from the payload and use it to render the notification as desired. You can explore this further by reading this Stack Overflow post, this article, or watching this WWDC session on rich notifications.


Basic CSS: Accept Single Quotes

Previously only accepted "color:red;", will now also accept 'color:red;'

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[ ] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

Hi, you will not be able to edit this pull request because its a patch. Please go though Guidelines for Contributing.
You can open a fresh one when ready.
If you need any help please reachout to Contributors Chat room.

what issues number? did they ask to change it? just wondering.


1430: Add query params to card self service form

Short description
When the user taps the “Extend Card” button in the app, the self-service portal should open with the pre-filled data.
In this PR, I added support for query parameters in the /erstellen route.
I feel a bit lost in React, so perhaps my implementation is not optimal, pls take a look.
Proposed changes

query params in the card self service form: name, geburtsdatum, ref

Side effects
no?
Testing
Open url with query params
http://localhost:3000/erstellen?name=Karla%20Koblenz&ref=123K&geburtsdatum=2003-06-10
The form should be pre-filled with the provided data
Resolved issues
Part of: #1430

Some general ideas to your pr.
Instead of updating the card in a hook in the form component, i would suggest to add this functionality in the existing useCardGeneratorSelfService hook where the card will be initilized. That also avoids unexpected rerendering.
You can just add a fkt handleQueryParams and return the needed values there and then initlialize them here. Please also provide some Error handling if birthday can not be parsed and show a toast.
if you add Nullish Coalescingwhen getting the queryParam and return undefined you can even avoid null checking while initializing
const fullName = cardQueryParams.get('name') ?? undefined

Example useCardGeneratorSelfService.ts
  const [cardQueryParams] = useSearchParams()
  const {fullName, birthday, koblenzReferenceNumber} = handleQueryParams(cardQueryParams)
  const [selfServiceCard, setSelfServiceCard] = useState(
  initializeCard(projectConfig.card, undefined, { fullName, expirationDate: null, extensions: {birthday, koblenzReferenceNumber } })
  )
  )

After generating a card successfully the queryParams should be removed. You can get a set fkt from the useSearchParamshook and do sth like
setSearchParams(undefined, { replace: true })

@f1sh1918 thanks for the feedback, I applied your suggestions, pls check if I understood you right.

I think something is not quite right yet, when I open the URL as you suggested nothing happens except the query params being removed

I forgot to update the PR description. Param names should be the same as in card config


MultipleFileUploadEditor and clone entity

Hi!
When cloning an entity that has an attachment, this error occurs.

For security reasons, only temporary files can be used in uploads!

Who knows how to solve a problem?

@Zahar661 Where is the file located ? On the client machine ?  then you need to upload it as a temporary file first and attach there - I think the issue is that chrome will not report back the file path - but instead gives it an alias ..

@stixoffire The file is already on the server in the persistent storage, it is attached to the original entity.

AFAIK cloning attachments is not supported. What should be the expected behavior anyway?
For me, not cloning any attachments is the way to go. Just override getCloningEntity in your dialog class like this:
protected getCloningEntity() {
   var clone = super.getCloningEntity();
   clone.<Your attachment field name> = null;
   return clone;
}
HTH
Hannes

@hannesb  I need it((((

@Zahar661 After you clone the entity - assign the original attachment to the cloned entity ..
clone. = MyOriginalEntity . ;
I know that is round about way but with HannesB answer the only way I know of to workaround is to copy from original - long way.

Closed due inactivity
Also check the issue guidelines.
If you still need help, you can ask this on stackoverflow with our new tag.
https://stackoverflow.com/tags/serenity-platform


Improve the doc comments.

https://github.com/thm-mni-ii/sea/blob/c13e0b877a9799f85ef3fd11e134ee41ff402860/include/sealib/graphcreator.h#L23
@1yay1 For what does the 2 stands?

The number denotes the amount of edges.
I.e. it's for multiple edges with the same endpoints.


KYLIN-5217 Fix init commit

It's better not to include rpm packages into git repository.
And for the spark log file system, it's better to find it by its path rather than use the default one.

LGTM


Want to add my open source project MESSI MANIA

Describe the project
A simple fan made web-page of LIONEL MESSI
Made by HTML CSS and JavaScript
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[x] New Project

try to make it responsive as well!

@zugzwang03 Sure!

@TusharKesarwani Merge it


Added a "god mode" button to the local dev environment  (issue #2164)

I have added a checkbox that can be used to turn on the "god mode". (#2164)

If you turn on the "god mode" then:

You will become a premium user
You can play all the levels (including preminum levels)
You will receive 100000 gems  (but if you turn off the "god mode" then you lose those gems)
You will receive 1000000 xp points (if you turn off the "god mode" then you lose those xp points)
All the heroes are unlocked

Ah, this is great–really nice work on this!

can you please do "God Mode" for my account? I really want to try all the characters and all the levels. Thank-you.

Sorry @Warlock900, can't activate God Mode on the main codecombat.com server–that'd be cheating! ;)

Can you let me run my own server on CodeCombat?
On Tue, Mar 6, 2018 at 9:17 AM, Nick Winter<EMAIL_ADDRESS>wrote:

Sorry @Warlock900 https://github.com/warlock900, can't activate God
Mode on the main codecombat.com server–that'd be cheating! ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codecombat/codecombat/pull/2313#issuecomment-370857398,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ah9gLiAbQDbrpxQU-Lu2FapizLU9MgO3ks5tbsSvgaJpZM4DgNmd
.

You can run your own CodeCombat local server as described in the dev setup instructions, but you have to create your own levels for it, since we don't include all the levels in the testing database dump, which kind of defeats the point of god mode.

thank-u
On Tue, Mar 6, 2018 at 12:25 PM, Nick Winter<EMAIL_ADDRESS>wrote:

You can run your own CodeCombat local server as described in the dev
setup instructions
https://github.com/codecombat/codecombat/wiki/Dev-Setup:-General-Information,
but you have to create your own levels for it, since we don't include all
the levels in the testing database dump, which kind of defeats the point of
god mode.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codecombat/codecombat/pull/2313#issuecomment-370916098,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ah9gLtweJ2vW-BqC3jq_q43Pt-IwmLCsks5tbvDLgaJpZM4DgNmd
.


chore/npm_and_yarn/eslint-config-prettier-8.3.0

Bump

eslint-config-prettier to 8.3.0
eslint-plugin-prettier to 4.0.0
adapt eslint config to ignore /lib and /coverage

Coverage remained the same at 100.0% when pulling d9eaab2596d28ded9685199971e0409cdf03a740 on chore/npm_and_yarn/eslint-config-prettier-8.3.0 into 44696fb1d552168d73c712c4831e211976b1827a on master.


Make some library name validation warn instead of error

When publishing a package, we validate library names:

Cannot be empty.
Can only contain identifier characters.
Must start with a letter.
Cannot be a Dart reserved word.
Should be all lowercase.

Currently, 2, 3, and 4 are errors, not warnings. After some discussion, we've decided to make those warn. (5 is already a warning, and 1 will remain an error.)

This issue has been moved to dart-lang/pub#455.


info.blockchain.api.createwallet.CreateWallet.java

typo: https://github.com/blockchain/api-v1-client-java/blob/master/src/main/java/info/blockchain/api/createwallet/CreateWallet.java#L14
[https://blockchain.info/api/create_walleti] vs [ https://blockchain.info/api/create_wallet]
what happens if the password passed here as parameter is not compliant with the internal password validation rules of the wallet? https://github.com/blockchain/api-v1-client-java/blob/master/src/main/java/info/blockchain/api/createwallet/CreateWallet.java#L21
would extract params creation in a separate function https://github.com/blockchain/api-v1-client-java/blob/master/src/main/java/info/blockchain/api/createwallet/CreateWallet.java#L45
this class know too much about the way HttpClient class works, similar to comment 5 here https://github.com/blockchain/api-v1-client-java/issues/20
the parse method throws some RuntimeEceptions https://google-gson.googlecode.com/svn/trunk/gson/docs/javadocs/com/google/gson/JsonParser.html#parse(com.google.gson.stream.JsonReader). Should we retry the call if the HttpClient.getInstance().post("api/v2/create_wallet", params) create_wallet endpoint is down? If there is a way we can help the client recover we should facilitate that https://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html

https://github.com/blockchain/api-v1-client-java/commit/fbdc51b7965222e24f9685ca51a2125328b15b66


Add autocompletion

Possibly with https://github.com/click-contrib/click-completion

I think this is now included by default in Click - https://click.palletsprojects.com/en/8.1.x/shell-completion/


The application was not what I saw in the video

What feature or improvement do you think would benefit Files?
After seeing the files app in a youtube video, I bought the app from the microsoft store, but in the customization section, there was no glass mode that I saw in the video, but instead there were a few lousy customization modes.
Requirements

This proposal will accomplish X
This proposal will accomplish Y
This proposal will accomplish Z

Files Version
<IP_ADDRESS>
Windows Version
Windows 11
Comments

The video you watch is old version. The videos are also not official made by Files.
For theming follow the instructions at https://files.community/docs/configuring/custom-themes

In particular, see the instructions for the "glass theme".


"Bulkrax identifier" custom queries & behavior doesn't belong in Hyku

Hyku has some added custom queries and conditional indexing of "bulkrax_identifier", which belong in bulkrax. The term doesn't exist on the models, so including queries and indexing isn't happing in the right place.
This code should be included in Bulkrax as part of the Valkyrization process, and removed from Hyku.
Relevant modules:

collection_indexer.rb & collection_resource_identifier.rb
hyku_indexing.rb
find_by_bulkrax_identifier.rb (app/services/hyrax/custom_queries/ and app/services/wings/custom_queries/)
find_by_bulkrax_identifier_spec.rb

Use of the term, such as adding it to models and mapping it, should also be considered and documented.
related:

https://github.com/scientist-softserv/hykuup_knapsack/issues/136

done ✅


GoViral: Provide documentation for updating the GoViral site

deploying to Heroku staging/production
using foreman

Let's plan to timebox this to 2 hours. Documentation may be brief, but we can answer questions later.


Add shared specs to pageflow-support to lint page types (13.x backbort)

Backport of #1133
This can be used by plugin engines to

check that rendering page template does not raise errors

check that rendering json seed does not raise errors

check that all required translations are defined

Make pageflow-support depend on factory_bot_rails instead of
factory_bot to make sure factories are loaded automatically.
REDMINE-16511

Coverage decreased (-0.004%) to 99.292% when pulling 92811d261b2787f3f383888d80b35828d5ef7071 on tf:lint-page-type-13 into 2b13102345b716530b5987ec20ae1a00917d9b08 on codevise:13-x-stable.


Add more context to comment

    i actually think this comment is a bit confusing with no other context

Originally posted by @martriay in https://github.com/OpenZeppelin/nile/pull/218#discussion_r986049902

i was actually vouching for removing it haha. Wasn't the comment a clarification on the diff, rather than a clarification on the code?

My intention with the comment was to add some clarification to the fact that other functions using address_or_alias normalize the number if it is not an alias, but send specifically doesn't. This is a difference in the code I think it could have been confusing. I'm inclined to let the comment because of this, refactoring it to something more informative, like the following idea:
"address_or_alias is not normalized first here, because Account.send is part of the nile public API, consequently accepting address as hex too"


Document how to get all entries in ranger

Documentation + unit tests.
entries, err := ranger.CoveredNetworks(*AllIPv4) // for IPv4
entries, err := ranger.CoveredNetworks(*AllIPv6) // for IPv6

This closes #5

Coverage increased (+0.1%) to 82.469% when pulling 3a95bdef0e48009d8e12a9bdbc8b2d4071c883f2 on iterate into 1c6c8201b51cac7e8dab570d828e8f071e488abc on master.


Match angle brackets syntactically

Remove the angle bracket blinking feature, and make it actually match < and > characters as parens in the syntax table instead.  This matching is suppressed as needed, so that less-than and greater-than operators, arrow operators, etc don't throw off the matches.
This has the following effects:

Angle brackets match like other braces/parens however they are configured, rather than blinking in a different way.
Movement commands like forward-sexp and backward-up-list acknowledge angle brackets.
electric-pair-mode works with angle brackets (also suppressed when needed.)
Fix #50 - angle brackets are matched in the right pairs; -> and other non-angle-bracket < and > characters do not attempt to match.
Fix #10 - multi-line lists inside angle brackets are indented like other lists.

Macros have arbitrary syntax and therefore it's not possible to know whether a < or > character is an angle bracket or not.  So the matching is always suppressed inside macro definitions and uses.
There are a few disadvantages: besides the fact that the code is rather hairy, it also has to detect the non-angle-brackets perfectly, or else it throws off the indentation for the whole rest of the file.  For that reason there is still a custom variable available to disable it (though with a different name than the previous one.)
Having said that, I don't know of any cases where it gets it wrong.  I tested it with this program, which compares what emacs thinks are the non-bracket </> characters with what the rust compiler thinks.  It passed for all of the rust compiler code base, as well as all the rust code in servo and as many of servo's dependencies as still compile with the latest nightly.
Also included are some bug fixes for some edge case issues in the handling of raw strings and character literals.  I found these while running the test script.  Even if the angle bracket matching itself is deemed to be too risky or hairy to be merged (and I would understand it if that turns out to be the case), you may want to merge the other commits for the bug fixes.  I've put them first to make this easy.
If this PR is accepted, close #66 (because the variable that it renames has been removed entirely) and close #74 (because post-self-insert-hook is no longer used at all.)  Both of these pertain to the old angle bracket blinking code that this PR removes entirely.
And if the PR is not accepted - hey, I still had fun writing it.

r? @pnkfelix
(rust_highfive has picked a reviewer for you, use r? to override)

I think I do want to accept this.  At the very least, I've noticed that the current bracket-blinking code totally messes up multiple-cursors mode.
cc @nikomatsakis any thoughts here?

Thanks @pnkfelix.
I just rebased after the latest other commits to master.  (Nothing else was changed.)

I have no objections -- it sounds strictly better than the hack I did. I don't quite understand how it works (but I haven't tried reading it).


Image 'contain' resizeMode not working

Hello,
I am using React Native on a real Android device.
When creating a really simple app with just the following render function on the main app component...
  render() {
    <Image
      source={{uri:'http://resizing.flixster.com/DeLpPTAwX3O2LszOpeaMHjbzuAw=/53x77/dkpu1ddg7pbsk.cloudfront.net/movie/11/16/47/11164719_ori.jpg'}}
      style={
        {
          flex: 1,
          resizeMode: 'contain',
          backgroundColor: 'yellow'
        }
      } />
  }

I get the following result on my device:

As you can see the whole background is yellow so that tells us the image element is taking the whole screen size indeed. But it is just rendered wrong.
The 'cover' resizeMode does work as expected (and so does the 'stretch' mode).
It is the 'contain' mode that is not working (the most important one from my point of view).
The problem gets even worse when placing the image on a ListView since the image does not even show.

@facebook-github-bot stack-overflow


OpenCensus Tracing Plugin Package Cleanup

Updates the package name and documentation for the OpenCensus Tracing plugin package.

@alzimmermsft I have a question about the name change that was done here. We'd gone from com.azure:tracing-opentelemetry to com.azure:azure-core-tracing-opencensus but shouldn't this have been azure-tracing-opencensus? All of our other names are azure-[-...] for example azure-identity or azure-keyvault-keys, the fact that we're azure-core-tracing-opencensus kind of implies that this is a core module and not a tracing module.


Fix createContext ID's in object properties

As per this slack report, the following code is converted to assignments to the same context ID.
input:
const contexts = {
  foo: createContext(),
  bar: createContext(),
};

output:
const contexts = {
  foo: createContext._17pejbx || (createContext._17pejbx = createContext()),
  bar: createContext._17pejbx || (createContext._17pejbx = createContext())
};

This PR detects when createContext() is invoked within an object property and includes the key in the ID. It likely breaks for computed keys, and can still cause collisions for nested keys.

FYI, the first iteration of the code (which I tried to fix), looked a little bit different:
const contexts = {};

const ensureContext = (kind) => {
  if (!(kind in contexts)) {
    contexts[kind] = createContext();
  }
  return contexts[kind];
};

const useThingie = (kind) => {
  const context = ensureContext(kind);
  return useContext(context);
};


Unexpected Error

Hi,
This has been working for me until recently where I would get connection error. I tried many times to reload the integration and it didn't help.
Today I deleted it and now when I try to add it again and want to login using my Bluelink credentials I am getting unexpected error message.
I have a Hyundai Ioniq 5 EV. I live in EU.
Please check Services, Known Bug / Issues and Troubleshooting over here first: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
Region and Brand of car
Version of the integration
Describe the bug
A clear and concise description of what the bug is.
Debug logs if an error occurred
Outlined here: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
To Reproduce
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

What version?

I have the latest one available on HACS. I did an upgrade of my HA and now it's working.


add upsert

ftr. originally implemented this for another feature but at a later revision this upsert wasn't needed there. Keeping it here in case it is needed in the future


Document new AutoCallable structured product

Fixes https://github.com/digital-asset/daml-finance/issues/1193

Ah, one more thing: it might be worth porting the change to the 3.0.0 documentation as well (unless we want to do it in bulk at some point in time)

Ah, one more thing: it might be worth porting the change to the 3.0.0 documentation as well (unless we want to do it in bulk at some point in time)

I thought about that as well. I have brought it up as a discussion point for the team meeting. My preference would be to bulk copy it over after the 2.9 release, unless we do a Daml Finance split earlier and need to maintain separate docs.

Thanks, makes perfect sense to me


lack of updates making people hesitate to install plugin

Placeholder for now - but I've gotten a number of tickets in support asking us if the plugin is defunct because it hasn't been updated in >3yrs. Common "wisdom" in the WP community is to only install plugins with recent updates. We might consider a somewhat frequent update schedule going forward.

Update: We are working with @greatislander to regain the ability to deploy the WP plugin.

@klemay Updated, and the deployment to WordPress.org will now happen automatically whenever the version number is changed in https://github.com/hypothesis/wp-hypothesis/blob/master/hypothesis.php.

Thanks so much, Ned!

Yes, thanks x1 million!

The latest updated version is 5.2. Can we bump it to a newer version?


How to setup Odoo to work with this frontend?

Hey,
I wanted to test the repo with a local Odoo instance but wasn't sure what's expected from the frontend?
would be cool if you could give some directions.
Thanks a lot!

This project is developed using Odoo 13, so to start the Odoo development server, you will need a Odoo 13 instance. Then install these modules in this repo: https://github.com/hieuhani/simpos/tree/master/addons
The required modules are:

simpos_cors: To allow the front end to connect to
simpos_token_authentication: To support user authentication vie JWT

Optional modules:

simpos_vibration_card: To record the vibration card number (in case of a coffee shop)

After installing all of these modules, you will need to install: point_of_sale module. That's it.
Sorry for the late response because I was on a holiday. Ready to work nowww 💪

@hieuhani Could you please clarify what steps we need to take on the frontend after installing these modules on Odoo?


Cool hovering effect to the donate button.

No description provided.

I think current button style in okay.


Update en_nz.json

Largely Gray->Grey regional English

Hahaha, love the wordplay! 😆
Thanks for translating!


Wrong Flask resource paths in annotation_gui_gcp

Running python3 annotation_gui_gcp/main.py /data/berlin the following content is reachable:

The output is:
* Serving Flask app 'main'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.


Cannot run game while using scrcpy, security violation.

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: macOS
scrcpy version: 1.18
installation method: brew
device model: Huawei
Android version: 5.0.1

Describe the bug
scrcpy is working fine on the device until I try to load a game, then I get the following error: Security Violation: 'ADB or ROOT Shells (ex: /System/bin/sh)' is running in the background! This app will be terminated!
After, the game will shut down. I can't seem to figure out how to bypass this. Please help!

The game checks if adb is enabled and decides to terminate itself.

This only happens on one device. I am also using the same game same build on a Motorola device and it works perfect with scrcpy. Is there any workaround?

On this particular device, if adb is enabled, but you don't run scrcpy, does it still terminate?

Are you referring to debugging inside developer?

Yes.
Basically, if you just don't run scrcpy without changing anything else, does your game terminate?

No, it only terminates when running scrcpy. Debugging is ON and it works fine.

OK, I don't know on what criteria the game decides to terminate itself.
If you just mirror without injecting input events (-n/--no-control), does it work?
scrcpy -n

Ok success! So, just to try something stupid, pulling down the notifications, I changed the USB MODE to "USB Drive" instead of the default "Files" and that seemed to work. The only problem is it is disconnecting itself from the computer after a certain time-frame. This could be cable issue or something else, so I will test that. But, it looks like some sort of progression at least. It could be that this phone is just old and finicky as well (the disconnect/reconnect).

Unfortunately, counted my chickens too soon. Not a reliable fix as I am still having the issue in either mode.


Doesn't seem to work on large files?

I have a 130 MB JSON file (from llvm-tblgen --dump-json) but unfortunately it just seems to freeze when I run it through json_typegen. I don't even get a progress bar (which I think the CLI is supposed to do?)
Any hints on how to debug this?

Huh it didn't work with the cargo install json_typegen version, but I tried compiling from master and it worked perfectly (and showed a progress bar!).
Maybe worth a new release?

Maybe worth a new release?

Oh, for sure. 😬 Thank you for the reminder. I've held off doing a release due to the master branch having a bit of a regression in terms of not being able to "singularize" well when coming up with names for types, but at this point I should probably just ship with that regression and revisit that when I have time.


Adding operators of authorizer in bonding section

Closes: https://github.com/keep-network/keep-core/issues/1792
In this PR we add operators of an authorizer in the bonding section of tBTC application.

@r-czajkowski I don't think anyone would review it other than you, so since you're the only reviewer, you can go ahead and merge :)


[Feat:Documentation] Add deployment using gitlab-ci

Feature Request
The deployment section of the documentation only present deployment on github, not gitlab. Gitlab-ci is quite a powerful tool to automatically build and deploy pages and should be added as well. I has the advantage of not requiring a second repo for the public website and is generally quite easy to put in place.
Besides that,  the use of go modules for the latest version of wowchemy is not working out of the box using the .gitlab-ci.yml template pre-configured by gitlab. Indeed, the default image used does not have golanginstalled.
After lots of reasearch, I found a working image on dockerhub: klakegg/hugo:edge-ext-alpine.
Solution
Write a small paragraph detailing how to setup gitlab-ci for auto build and deployment and provide a working minimal example of .gitlab-ci.yaml.

My current minimal `gitlab-ci.yml`
# This is similar to the default template provided by gitlab.
# The only difference is the image, in order to ensure compatibility with go modules.

image:
  name: klakegg/hugo:edge-ext-alpine
  entrypoint: [""]

variables:
  GIT_SUBMODULE_STRATEGY: recursive

test:
  script:
    - hugo
  except:
    - master

pages:
  script:
    - hugo
  artifacts:
    paths:
      - public
  only:
    - master

Note that the entrypoint definition is required with this image, see the following discussion.

Extra
I am ok to write the section myself and propose it as a PR, but I did not find the documentation repo (is it public?).

I found the docs repo. Sorry for the inconvenience. I will close this issue and propose a PR there directly.


Bower Install tafgeetjs

Could not able to download tafgeetjs with  bower install. Any help Please.!

@kishoreaoe Registered tafgeetjs on Bower you can now install it using the install command, but I need to mention that Bower themselves not recommending using bower they encourage people to move to Webpack or Yarn


Output the _rev by default in views (similar to _id)

Summary
Output the _rev by default in views (similar to _id)
Desired Behaviour
Whenever the _id shows in a view result, also show _rev (same hierarchical level).
Possible Solution
My guess is when you output the _id, the _rev is also present so wouldn't take a lot of effort to include it in the result ?
Additional context
At the moment when you query a view, you get the _id as a way to identify which record has gotten you which information. It would be very useful to also have the _rev in case one needs to make modification to the queried data.
It would prevent the user from having to query each individual _rev based on the _id, or build a new exactly similar index to get the _rev or use the include_docs=true flag, hence saving calculation time and/or data transfer.

I think this is a useful addition IF we can make it efficient to provide.
Currently, CouchDB internally needs to store the doc _id inside a view index to effectively perform view updates. Because it is already in the index, we show it with every result*. If the view index already also includes the _rev for each row (something I’m not sure about at the moment), then we could add an option along the lines of ?include_rev=true to show it as well.
If the _rev is NOT already in the view index, would not suggest we add, just for this feature for performance reasons.

there might be a valid reverse request to hide the id if it is not needed (?include_id=false maybe)

Is someone here up for checking if the _rev is already part of a view index?

Beyond my skillset I'm afraid.

To the best of my knowledge it is not.

How does couch know which _rev of each _id to use in views ?

@elChapoSing by reading the _changes feed, which has that info. My memory agrees with @kocolosk, so I’m closing this. Sorry about this! :)


Additional versions bumped for 1.5.0 suite release

Bump service broker once new version is released (see https://github.com/cyberark/conjur-service-broker/issues/159 which is prompting us to update the release artifact to remove dev and test dependencies)
Remove .net client or bump version (see https://github.com/cyberark/conjur-api-dotnet/issues/43)

Let's remove .NET for now.  Good catch.  Maybe provide a few details explaining the "why" for the two changes needed in your list above?  Thx.

there's a branch for this here: https://github.com/cyberark/conjur-oss-suite-release/tree/1.5.0-suite.1-update


Fixed downloadChunk is called within named function with wrong scope

dlChunk function is used within itself and scope for this is wrong. self is already declared with correct scope outside of function.

:+1: Thanks. Will push out a minor version update to npm now.


[Tech Debt]:

What is needed?
The app settings menu needs to be manually resized every time we add or remove an item from the list. The container should automatically resize correctly any time elements are added or removed.

The height of this menu is currently hardcoded by this line in Header.ts


Use an specific role for each main component of an Apache Kafka cluster

SUMMARY
An Apache Kafka cluster contains the following main components:

A Zookeeper ensemble (for now, as at some point Zookeeper will be removed)
A Kafka broker cluster

It could be usefull to split the current collection into 2 different roles:

roles/zookeeper: To centralize all the tasks to install, deploy, and operate the Zookeper ensemble
roles/kafka: To centralize all the tasks to install, deploy, and operate the Kafka cluster

This approach could help to mantain better each member of the ecosystem, and not add all the tasks in the same place. In the future, as soon Zookeeper is removing and others components (Kraft) are including, then new roles can play a better maintanibility.
ISSUE TYPE

Feature Idea

It was more/less on my TODO list. However, there is a lot of code duplication if we do that, so we probably need to have 3 roles amq_stream, amq_streams_zookeeper and amq_streams_commons.

Indeed! Commons, Zookeeper, and Kafka roles are a better approach.

Note that we do need to use amq_streams in front and I'm not sure about using Kafka (for © reason).

The new structure of the collection, using multiple roles especialized to cover different components, is aligned with this issue. IMHO we can close it. What do you think?
@rpelisse :point_up:

You are right! Thanks for pointing this out!


the command  func azure functionapp create no longer works

When I updated to Azure Functions Cli (1.0.0-beta.91) the scripts we use for automated setup and deploy of new functions apps stopped working.
I see this commit https://github.com/Azure/azure-functions-cli/commit/5221e9035b7c5d0f29df12cdffc76e38eaa3d4cb removed something that definitely looks like it was what we were using, and I wonder why it was removed, or perhaps more importantly, what method we should use to create function apps from the command line going forward.

Reasoning is explained in #50 I probably should've added that to the commit message.
But to summarize, the method will be through azure cli while keeping this to dev scenarios to reduce people getting confused by "why there are many CLIs for azure stuff"
We will probably rename this project to something other than cli down the line as well, though it's just a repo rename. Shouldn't affect anything else.

I'll close this issue

The azure cli is a) dependent on python, which is a dealbreaker for us. It is also, b) documented nowhere how to use it to create function apps.


[FIX]: install.sh: Do not ask user which services to restart

📑 Description

Closes #28

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed

ℹ Additional Information

@pitdagosti please review and merge. Thanks!

Thanks @pitdagosti

I have not tried it yet but LGTM

You should try it on puppypd01


Use toLowerCase on language names

In Jekyll the language names have to be written with capitalized letter at the beginning (Javascript, CSS, SCSS), this makes Prism not detect them correctly.
This small change runs the toLowerCase on the language after extracting it from the class.
I'm not 100% sure I did this correctly, but I pulled, made my change to components folder and ran gulp.

I'm not sure I understand what the issue is in the first place...?

If the class names on code-element is:
<code class="language-Javascript"

prism.js wont actually work on it. The initial check detects it, since it only checks for lang(uage)-*
var lang = /\blang(?:uage)?-(\w+)\b/i;

But this part of highlightElement saves it as "Javascript":
language = (parent.className.match(lang) || [,''])[1];

while the rest of the code uses "javascript" (with only lower case). This seems to be the same for the rest of the languages as well. By running toLowerCase the only difference is that "language-JavaScript", "language-JAVASCRIPT" or for example "language-javaSCRIPT" would be parsed to "javascript".
It's not a major issue, but as far as I have found out it's not something you can control when using Jekyll with Github Pages.

OK. I'm still not sure I understand why Jekyll would force caps in languages names, but nevermind. Your change looks good to me.

I'm not sure of that either, makes no sense to me. But when I try to use "javascript" it ignores it.

I checked quickly and couldn't find native support for Prism in Jekyll. Are you using a plugin or something?

I’m loading prism on the pages I want it and define my codeblocks in Markdown with three backticks and language name, if that's what you are thinking on.
Plugin support is very limited in Jekyll and specially on Github Pages.


Prototype sealed indirection

Resolves #136

There are caveats to this and I'm not sure what to do about it yet:

In annotation processing, this would make the processor "aggregating" because it would parse multiple levels of subtypes.
Multiple levels of sealed types become expensive to look up
What if someone has a custom adapter for the sealed subtype (i.e. not using moshi-sealed)?

Another question - what if there's a separate branching off point? Like the parent class uses one discriminator, then the next level uses a different discriminator for its own subtypes?


Installation instructions > installing cvxopt

CVXOPT package installation instructions on gpkit.readthedocs is incomplete. Need to install BLAS and LAPACK via:
sudo apt-get install libblas-dev liblapack-dev
before running sudo pip install cvxopt.
(on Ubuntu)

Does @galbramc agree?

Yes that is correct. We have those packages installed on all our testing machines for other codes, so I didn't realize they were needed for cvxopt as well.

@aechevarria1, this should be fairly easy to add to the docs.

this was fixed by #934


refactor(protocol)!: remove useless fields of block

What this PR does / why we need it:
This PR remove the call_system_contract_count and latest_checkpoint_block_hash fields in block header.
Which issue(s) this PR fixes:

Fixes #
Which docs this PR relation:
Ref #
Which toolchain this PR adaption:
No Breaking Change
Special notes for your reviewer:
NIL
CI Description

CI Name
Description

Chaos CI
Test the liveness and robustness of Axon under terrible network condition

Cargo Clippy
Run cargo clippy --all --all-targets --all-features

Coverage Test
Get the unit test coverage report

E2E Test
Run end-to-end test to check interfaces

Code Format
Run cargo +nightly fmt --all -- --check and cargo sort -gwc

Web3 Compatible Test
Test the Web3 compatibility of Axon

v3 Core Test
Run the compatibility tests provided by Uniswap V3

OCT 1-5 | 6-10 | 11 | 12-15 | 16-19
Run the compatibility tests provided by OpenZeppelin

CI Usage

Check the CI you want to run below, and then comment /run-ci.

CI Switch

[ ] Chaos CI
[x] Cargo Clippy
[x] Coverage Test
[x] E2E Tests
[x] Code Format
[x] Unit Tests
[x] Web3 Compatible Tests
[x] OCT 1-5 And 12-15
[x] OCT 6-10
[x] OCT 11
[x] OCT 16-19
[x] v3 Core Tests

/run-ci

/run-ci

/run-ci


(Question) Can we use in-code evaluation through the APIs, instead of using lm-eval in bash terminal?

(Question) Can we use in-code evaluation through the APIs, instead of using lm-eval in bash terminal?

There is an example in the previous issue:
import lm_eval

device:str ='cuda'  # 'cuda' or 'cpu'

lm_eval.tasks.initialize_tasks()
results = lm_eval.simple_evaluate(
    model="hf",
    model_args=f"pretrained={<PATH_TO_HF_REPO>}," + \
        f"tokenizer={<PATH_TO_HF_REPO>}",
    tasks=['mmlu'],
    num_fewshot=0,
    device=device)

Is this the API call you are asking for?

Thank you @LSinev for providing the example from the previous issue. Yes, that is the API call I was referring to. I appreciate your help :)


Make a redirection to previous page after logged in

Fix #403

LGTM. Merging the PR. Thanks for your contribution!


Cannot create foreign key to schema with custom primary key

A schema with a custom primary key is defined as follows:
    create table(:my_table, primary_key: false) do
      add :id, :string, [size: 34, primary_key: true]
    end

A foreign key reference to this table should be supported as follows:
    create table(:my_second_table) do
      add :foreign_id, references(:my_table), [null: false]
    end

However this results in the following compile error:
     ** (Postgrex.Error) ERROR (datatype_mismatch): foreign key constraint "my_second_table_my_table_id_fkey" cannot be implemented

After some debugging, I come to the conclusion that the error is that foreign_id in my_second_table is incorrectly assumed to be of type integer.
Is my assertion correct, and if so, is this indeed a bug (worth fixing) ?

Problem lied with me: I should've used the type option in the references() command.


Enhancement/comment template

Make the Kitsu comment template a multiline textarea so that markdown table can be supported.
Make the default a multiline text too.

swap product[name] for family in the template as product[name] in my tests.
This translates to a kitsu comment:

This PR requires  #33 or the settings will not work.
This PR is compatible with #35

Nice one!
LGTM :)