Flaky TestL7NetworkPolicy e2e tests

The TestL7NetworkPolicy in e2e tests framework failed often. Here is a report from @antoninbas 's data collection. https://github.com/antoninbas/antrea-flaky-tests/blob/main/results/2023_10_23/results-90.txt
In the past 90 days, the sub test TestL7NetworkPolicy/TLS failed 7 times, we may need investigate it's a code issue or test issue, therefore, we can reduce the rerun efforts and improve test efficiency.

@luolanzone This issue has been fixed already: https://github.com/antrea-io/antrea/issues/5296
The test is no longer failing now, and I expect that it won't show up in the 90-day report starting next week (the fix was merged on July 26).

OK, got it, thanks


Release Google.Cloud.DiscoveryEngine.V1 version 1.0.0-beta02

Changes in this release:
New features

Add data store, engine and site search engine services (commit 2125414)
Support search summarization with citations and references (commit 2125414)
Add suggestion deny list import/purge APIs (commit 2125414)
Add engine support for multi-turn search and search APIs (commit 2125414)

Documentation improvements

Keep the API doc up-to-date with recent changes (commit 2125414)

Created release for Google.Cloud.DiscoveryEngine.V1-1.0.0-beta02


How to use?

I've setup our mattermost server with that plugin and also configure the server, but somehow I can't find any function referencing to the jitsi plugin.
How it should work, if everything is right?
Mattermost: 5.2

Closing as there has been no update for 3 weeks.


Source Control menu showing wrong branches of worktrees contained in bare repository

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

VS Code Version: 1.73.0-insider
OS Version: MacOS 12.4

Steps to Reproduce:

Clone a bare repository. (ex: git clone --bare git@github.com:microsoft/vscode.git)
Go into the directory of the cloned bare repository. (ex: cd vscode.git)
Create a trees folder in the bare repository folder. (ex: mkdir trees)
Add a worktree for multiple valid branches (ex: git worktree add trees/1.70 release/1.70; git worktree add trees/1.71 release/1.71; git worktree add trees/1.72 release/1.72)
Add the folders trees/1.70, trees/1.71, and trees/1.72 to a VSCode workspace.
Open the Source Control menu.
See that each each worktree folder shows up as a distinct repository, but that they all show the primary branch as though it were the branch that is checked out instead of their actual checked out branch. (ex: all would be main but should be release/1.70, release/1.71, and release/1.72)

Screenshot included is from the example instructions above where none of these folders have main checked out, yet all show main as their checked out branch:

I can confirm that the correct branch names were displayed at least as of 1.70.2 but I have not yet tried more versions in-between.

I'm having the same issue with a non-bare repository. I have an additional worktree and today's VSCode update is showing the checked out branch of the main worktree instead of the current directory's worktree. This worked fine in v1.72, and is now broken in v1.73. This also messes up the GitHub Pull Requests extension since it is using the wrong branch to get PR information.

This was working correctly in the prior version, but today when I applied the newly available v1.73 I am seeing this problem is all my secondary worktrees.

This appears to be caused by #162572, specifically here where it's getting the HEAD branch from the filesystem (instead of using git commands):
https://github.com/microsoft/vscode/blob/9c802415e11bf11230720bc4a93397c338121da8/extensions/git/src/git.ts#L2086
this.dotGit.commonPath seems to refer to the main worktree's .git path, and this.dotGit.path is the current working directory's .git path. This should be checking path before commonPath:
diff --git a/extensions/git/src/git.ts b/extensions/git/src/git.ts
index 7c49b545f8c..1538a356a31 100644
--- a/extensions/git/src/git.ts
+++ b/extensions/git/src/git.ts
@@ -2083,7 +2083,7 @@ export class Repository {
 	}

 	async getHEADFS(): Promise<Ref> {
-		const raw = await fs.readFile(path.join(this.dotGit.commonPath ?? this.dotGit.path, 'HEAD'), 'utf8');
+		const raw = await fs.readFile(path.join(this.dotGit.path ?? this.dotGit.commonPath, 'HEAD'), 'utf8');

 		// Branch
 		const branchMatch = raw.match(/^ref: refs\/heads\/(?<name>.*)$/m);

I have the same problem with VS Code 1.73.0. This issue also breaks GitLab extension since it gets wrong branch

Can the builtin extensions be updated independently from updating vscode? In that case this shouldn't be hard to fix.

@brainz80, it cannot. I am looking at having this fixed in Insiders early next week.

I'm having this same issue in 1.73.0 (user setup).
I've got 3 repositories each having 4 active git-worktrees in a multi-root workspace, and each worktree seems to indicate the same checked out branch.

I'm also having a problem in 1.73.0 that appears to be the same root cause.
I have a single repo with three working trees checked out, and VS Code always thinks that I'm on the primary working trees.
This is causing problems for the GitHub Pull Requests and Issues extension (I can only review PRs when using the primary working tree).

yep, me too!

same issue

The fix will be included into Monday's Insiders release. Apologies for the inconvenience.

@lszomoru  Any idea when this will be in the regular release? I'd rather not have to switch to the insiders build.

Verification steps:
mkdir main && cd main
git init .
echo a >> a
git commit . -m 'init'
git worktree add -b dev ../dev # important!
code ../dev

Expected: VS Code status indicator should show dev as the branch name


[ListItem] Nested items api changes

Breaking Changes

Nested list items are now explicitly passed in using the nestedItems prop instead of children.
The open prop has been renamed to initiallyOpen.

Fixes #1105

@hai-cea Looks good to me.

Thanks @jkruder


[BUG] Spawned Node3D sometimes revert to earlier setting

Godot version
v4.2.2.stable.official [15073afe3]
Plugin version
1.3.2
Platform
Windows 10
Issue description
In my scene I have set up a few types of bushes and trees. For a bush I initially set up collision from another tree as Spawned Node3D. Later I changed it to another scene that fits more to the shape. However, sometimes it randomly reverts to the scene I initially set it to.
Steps to Reproduce
Unfortunately I haven't been able to notice any rhythm or reason as to how this happens...
Minimal reproduction project
See above. This might be one of those hard to catch bugs since it happens very sporadically, and for some reason on one plant at that.

Have a few ideas where this may be coming from: there is an array that is shared among all octree nodes, containing the list of meshes and scene to be used for different LODs. Probably something goes wrong when updating this array (possibly related to how Godot caches resources?).
Will investigate, but not urgently.

Yeah I think it's not urgent as it doesn't happen not too often and it might be hard to track down. I'll post more info if I notice something new.


HTP 403 Unauthorized when I can login via Browser

Please follow the guide below
Get the error below:
[udemy: course] Downloading login popup
ERROR: Unable to download webpage: HTTP Error 403: Unauthorized (caused by <HTTPError 403: 'Unauthorized'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

My Plugin is up to date:
pip install -U youtube-dl
Requirement already up-to-date: youtube-dl in c:\program files\python37\lib\site-packages (2018.11.7)

Please investigate.
I can log in with same credentials via the browser.
Thank you very much
Ameya Agashe

So where is this tracked if it is a duplicate? Is there a fix being developed? or is this a workaround?

any solve for this problem ?


update to ESLint 3+ rule format

http://eslint.org/blog/2016/07/eslint-new-rule-format (see part about the auto-transform tool)
@ljharb made an interesting point on the PR for the React plugin about maybe not being too aggressive/hasty about this.
I'm planning to do this as part of the semver-major bump to 2.x for this plugin, though there is nothing else to really gain from being 3.x+ only with ESLint, other than that I want to drop support for Node 0.10 and 0.12.
But it's not obvious to me why anyone would want to stay on ESLint 2 if they are using Node 4+, either.
So it feels like a major release would be the right time to bump to support ESLint 3.
Feedback (especially arguments against this) desired/welcome.

My preference would be to retain both eslint 2 + 3 compat, as well as node 0.10 compat - ideally, at least one version exists for the entire setup such that those who have not yet upgraded (and there are many valid reasons why someone may not have) can still have a smooth path to upgrading - ie, they can upgrade their linting deps, and then, separately, upgrade node - and then, separately, upgrade their linting deps again to the one that's functionally equivalent but drops old node/eslint.

related: https://github.com/benmosher/eslint-plugin-import/commit/a55cd67dabae15ae6f95361e4452f46e0df69ebb#commitcomment-18156683

Correct me if I'm wrong, but I get the feeling that both ESLint 2 and ESLint 3 are compatible with both rule formats.

If that's true then of course we should change it, but I can't conceive of how a brand new format would be supported by an old version.

Docs don't confirm or deny that, AFAICT. Just that both formats are supported in 3.x.
Have you tested? It's not obvious to me how (or why) that would work.

https://gitter.im/eslint/eslint?at=577e7ebce483756e106004ad
https://gitter.im/eslint/eslint?at=577e82e359cfbd4c5e3e8378
cc @sindresorhus @jamestalmage @novemberborn in case you're interested

I'm surprised the blog post about it was coupled with the v3 release, but that's great news. Upgrade away!

fixed in 20079c6, will deploy via v2 anyway


Depends on channels package

I got this message:
/venv/project_name/lib/python3.4/site-packages/celery/loaders/base.py", line 252, in autodiscover_tasks
    related_name) if mod)
  File "/opt/venv/project_name/lib/python3.4/site-packages/celery/loaders/base.py", line 273, in autodiscover_tasks
    return [find_related_module(pkg, related_name) for pkg in packages]
  File "/opt/venv/project_name/lib/python3.4/site-packages/celery/loaders/base.py", line 273, in <listcomp>
    return [find_related_module(pkg, related_name) for pkg in packages]
  File "/opt/venv/project_name/lib/python3.4/site-packages/celery/loaders/base.py", line 299, in find_related_module
    return importlib.import_module('{0}.{1}'.format(package, related_name))
  File "/opt/venv/project_name/lib/python3.4/importlib/__init__.py", line 109, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1471, in exec_module
  File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed
  File "/opt/venv/project_name/lib/python3.4/site-packages/django_nyt/tasks.py", line 7, in <module>
    from channels import Group
ImportError: No module named 'channels'

After install channels everything seems to work.

Okay I see.
This is because you have Celery installed which will auto-load application.tasks -- so actually django-nyt knows that channels isn't installed, it's just Celery's behavior.
I'm going to fix it, but I really dislike Celery, so I'll wait for other more interesting patches before releasing and announcing something.

The latter was meant with a wink ;)


Refactor: router

Description
Previously each page had its route defined separately, making it difficult to test.
Now it has been replaced with a more declarative and safe way.

Created a router in a different class, this file contains all the routes.
The names of the routes were defined in an abstract class, and the go navigation was replaced with goNamed.

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[x] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Codecov Report

Merging #10 (2295f32) into main (a4ac69c) will increase coverage by 0.65%.
The diff coverage is 84.61%.

@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   93.10%   93.75%   +0.65%
==========================================
  Files          76       77       +1
  Lines        1522     1522
==========================================
+ Hits         1417     1427      +10
+ Misses        105       95      -10

Impacted Files
Coverage Δ

lib/activity/view/activity_page.dart
100.00% <ø> (+10.52%)
:arrow_up:

lib/home/view/home_page.dart
100.00% <ø> (+5.26%)
:arrow_up:

lib/planner/view/planner_page.dart
90.47% <ø> (+17.39%)
:arrow_up:

lib/routine/view/routine_page.dart
100.00% <ø> (+13.33%)
:arrow_up:

lib/schedule/view/schedule_page.dart
100.00% <ø> (+28.57%)
:arrow_up:

lib/sign_in/view/sign_in_page.dart
100.00% <ø> (ø)

lib/sign_up/view/sign_up_page.dart
100.00% <ø> (+42.85%)
:arrow_up:

lib/authentication/bloc/authentication_bloc.dart
76.00% <50.00%> (-5.82%)
:arrow_down:

lib/app/router/app_router.dart
77.14% <77.14%> (ø)

lib/activity/widgets/activity_header_buttons.dart
100.00% <100.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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


Recurring tasks should have a new recurrence if clicked "done" in the file view

Given that I am in the file markdown preview of a file that has tasks in it
When I click the checkbox of a recurring task
The next occurrence should be added above the original task
But instead only the original task gets marked "done" and no new event is added
When logging the call to the file writer, it correctly includes both lines of the new occurrence and the original task. However, it is not reflected in the file after calling vault.modify.

Fix: event.stopPropagation()


v12: Revert "refactor(x/mint): truncations pt 2 - provisions split in params and minter (#2500)"

Closes: #XXX
What is the purpose of the change
The new mint changes will go into v13. As a result, we are removing the currently unused logic from the next release.
This reverts commit 5caabd673cbc1f17f9909a7f02ede78222f4b17b.
Original PR: https://github.com/osmosis-labs/osmosis/pull/2500
The change is still present on main.
Testing and Verifying
This change is already covered by existing tests
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? no
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? no
How is the feature or change documented? not applicable

We should wait wit this until the new v12.x is cut

Should I go ahead and review this since v12.x is cut?


Fixed a typo in example GraphQL query

@pvlg I merged this and then realized this PR doesn't target the appropriate docs.  Can you please resubmit this - don't think you can reopen.  The docs change should be on all versions and on the current src, which is used for current and future versions.


API service

The slowest path in the overall process is building pages for single issues: this grows linearly with the number of issues.
We could serve an issue's data with an API and have a single page using requests to fill the template

I can suggest this as starting point https://github.com/emergenzeHack/covid19italia_api

The slowest path in the overall process is building pages for single issues: this grows linearly with the number of issues.
We could serve an issue's data with an API and have a single page using requests to fill the template

We don't need any intermediate API, you can directly get a JSON serialisation of the github issues through the GET https://api.github.com/repos/<ORG>/<REPO_NAME>/issues endpoint. E.g.: https://api.github.com/repos/emergenzeHack/europehelp.info_segnalazioni/issues
With a bit of client-side javascript it should be easy to extract the data we need.
However, SEO may be hurt by this approach

La pagina ukrainehelp.emergenzehack.info/issues_react/ usa React.js per fare il rendering di tutto il JSON. Se ci fosse un'API che fornisce i dati, sarebbe molto più semplice

https://docs.github.com/en/rest/reference/issues#get-an-issue può aiutare?

ma possiamo anche "scrivere" oltre che leggere?


[DOCS] Restore format

Restore the incorrectly changed format in https://github.com/apache/pulsar/pull/8920/files.

@Jennifer88huang Does it work in the restored / updated version in this pr? If it does work in both ways, then we can keep it.

@sijia-w Thank you for your efforts. I'm afraid the restore is not totally correct.
@RobertIndie fixed the token issues in #9313 for the upcoming 2.8.0 release. As discussed and confirmed in #9187, except token, others support JSON format before 2.7.0 release. So you do not need to restore other changes (except token) in this PR. You can double confirm it with @RobertIndie on it.

As discussed with @sijia-w , I think it is better to change other authentication parameters to string type. While other authentication supports the JSON format in more recent versions, they may not have been supported in the early version.


Onboarding migration

Migrating the onboarding from Gitlab into new and revamped lessons within the pro_apify_scraper_development folder.

Done making any further large changes to this PR. Will only make changes based on comments.

@mstephen19 did you test this using the ?version thing? Looks like there's something wrong with the structure since it returns a 500 error

@mstephen19 did you test this using the ?version thing? Looks like there's something wrong with the structure since it returns a 500 error

Yeah I thought that was just an issue with the ?version thing. I'll take a look at it. No linting errors being thrown and all the paths seem to be fine, so a bit confused on why this is happening

Yeah I thought that was just an issue with the ?version thing. I'll take a look at it. No linting errors being thrown and all the paths seem to be fine, so a bit confused on why this is happening

The version doesn't lie 🙂 but if it stops working in the future, please let the web team know - it's important that it keeps working.
From a look at the structure I see that you have a solutions directory but no solutions.md file here:

@m-murasovs Should be fixed now :D

Accidentally clicked on close

Excuse the last commit. Didn't mean for :wq to be the message ahaha. There was an error because I forgot to pull latest from the branch before pushing.


Support for create procedure / create functions ?

Hi,
Just wanted to know if node-sql supported the create function / create procedure statements ?

:+1:

I don't think it does yet, but contributions are super welcome here!


allowing Queryable to be used with multiple table names

Related to https://github.com/diesel-rs/diesel/discussions/3779
Couldn't get cargo test --features "postgres" to work in my machine but opening the PR. Getting back to this later today

Should be good now. Sorry about the spam, didn't spend much time checking why the tests wouldn't compile locally

I'm confused about this one, master branch has this change intact while listing diesel_derives on 2.1.0, yet diesel from crates.io version 2.1.4 is referencing derives 2.1.1, which doesn't have this change.
Am I missing something?

We just did not increase the derive version on the master branch after issuing patch releases from the 2.1.x branch. Changes land usually on the master branch. If necessary they are sometimes backported to the latest release branch. Releases are then issued from there.

Any good reason not to have it backported?

Backport do need someone that drives the backport forward and prepares a new release. That hasn't happen for this PR.
If you are interested in a patch release that includes this fix feel free to prepare a PR that backports this (and the other PR's marked as maybe-backport) and that contains a draft for the release notes. If that happens I can cut a release afterwards.

I tried to look through some other backport PRs to see how it's done but I'm not sure if I understand it right. Is there any kind of documentation for how you do it? I use git all the time but my knowledge on it only goes an inch deep -- just enough to do what i need to do.

https://github.com/diesel-rs/diesel/pull/3803 is an example for such backport PR. Essentially these are created by:

Checking out the target branch (git checkout 2.1.x)
Creating a new backport branch based on the target branch (git checkout -b backports/2.1.4)
Cherry-picking the releveant merge commits in chronological order to the (git cherry-pick commit-hash)
Bumping the versions in the relevant crate
Filling in a section in Changelog.md to describe which fixes are in this PR
Opening the PR


[WIP] Change deps to make CI green

Yeah, already tried that. Didn't work locally either!  We have to figure out why @babel/register is not working correctly any more

Yeah, already tried that. Didn't work locally either! We have to figure out why @babel/register is not working correctly any more

This one actually worked locally, but failed on CI. This was just a quick experiment. It seems that the error have sth to do with deps versions.
BTW, why do we specify Node.js version to '12' in tsetSuite.sh:
if [ $VERSION -lt 12 ]

?
In other words, why 12, and not i.e. 15?

Fixed in https://github.com/iLib-js/ilib-address/pull/4


Add name to MPVariable binding for inspect and printing

Thanks for creating and maintaining the gem.
The changes add the name field of the MPVariable class to the binding, allowing the inspect method to work how they do for the other variable classes. This is currently broken.

Thanks @tbolender!


Icons with greater width than height loaded as image with getImageSource are cropped wrong in Android

I created an icon font with Icomoon from SVG-files. The font looked great.
I use the IconSet to load the icons in an Image with IconSet.getImageSource. Worked great on iOS, also works great on Android for most of the icons. But as you can see in the next screenshot, not for all:

So this is on Android. For iOS it's like this:

At first, I couldn't, for the life of me, figure out why some icons were cut of and others not. Now looking at the icons that are cut off, I think it has to do with the height and the width. When I look at the font itself, it looks perfectly normal:

But the height of the icon itself is less than the width. So it looks like the Android code just takes the height, just for the pixels that are not "transparent" and also uses this for width and crops the icon.

https://github.com/oblador/react-native-vector-icons/blob/a76a9a57f6e8087d80cb61ef8f01595d688d2ad7/android/src/main/java/com/oblador/vectoricons/VectorIconsModule.java#L70
I put this code in an Android app (non react native) and it works great.
    val custom_font = Typeface.createFromAsset(assets, "fonts/icomoon.ttf")
    val paint = Paint()
    paint.setTypeface(custom_font)
    paint.textSize = 256f
    paint.setAntiAlias(true)
    val textBounds = Rect()
    val glyph = '\uE90C'
    paint.getTextBounds(glyph.toString(), 0, glyph.toString().length, textBounds)

    val bitmap = Bitmap.createBitmap(textBounds.width(), textBounds.height(), Bitmap.Config.ARGB_8888)
    val canvas = Canvas(bitmap)
    canvas.drawText(glyph.toString(), (-textBounds.left).toFloat(),(-textBounds.top).toFloat(), paint)
    imageView.setImageBitmap(bitmap)

So maybe it's the compressing or something.


[WIP] Private RSS feed

WIP! Nothing here is final.
refs #9001

[ ] reconsider core settings vs private setting - where should the hash live?
[ ] add admin ui change - show the direct link for the private rss feed
[ ] describe how this feature works
[ ] describe any alternative approach and their problems (e.g. rss as app, dirty require rss etc..)
[ ] add more tests
[ ] code quality check

@kirrg001 do you have an idea how the private RSS hash can be exposed to the client? Right now the core settings aren't accessible so it's not possible for the client to use hash to show the private RSS url.

@kevinansfield Yeah is on my list 👍

reconsider core settings vs private setting - where should the hash live?

Ready for review!


Shopping list

Hello,
There is an mistake on the shopping list.
The link for the sound card is used twice.
The link for the USB A Male to Female Extenstion Cable with Switch On/Off is missing.
Regards
Daniel

Thanks for pointing this out. This is the link, fixed in Readme file. http://amzn.to/2hHrvkG


need proper deployment in reverse proxy nginx

Symfony is one of library that laravel use to serve the apps in server, however as we deploy it in reverse proxy, symfony doesnt know if the server secure or not so the app route cant use https for request
for minimal fixing im forcing the apps to use https  when production mode

this issue has been fixed for latest commit


Failing website link on github

Hi.
Just a small info / request not related to the code itself, but to your project hosted on github.
While I have seen updates to the readme, just recently, a very prominent link is not working and probably needs an update too:
The website link of the github repo.

Looking forward to check out this repo further!
Cheers Fabian

I fxed it to https://ficto-healthtech.vercel.app/ for now - @IvanKiral for notice :)

Thank you @Cyclodex for the report and @Simply007 for the fix. I will close this issue now. If you'd like to discuss anything else feel free to reopen it or create another one.


Workflow tree is not usable if workflow has a lot of nodes

Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
What happened: Workflow tree should be improved to render large workflows. Attached screenshot demonstrates issue:

Environment:

Argo version: v2.2.1

As I'm working on workflows that are quite big and require lots of parallelization, I'm facing a similar problem. Would it be possible to merge all parallel nodes together and display a small "number of tasks" icon over it (like apple mail does it with unread emails in the dock)?
I think the visualization gets a little more interesting if one of the tasks fails..
I'm using a dag instead of tasks. I'm achieving my parallelism by using the withSequence keyword. However when using a level of parallelism of 18, the graph is already packed. If I go up to 128 or more the graph is not very helpful anymore (even on 30% zoom level).
I guess for the withSequence option the same argument applies as for the tasks and parallelism attribute, right?
The following screenshot demonstrated that it's impossible to identify the relationships between certain tasks as the ordering is messed up as well. And I was only using a parallelism of 4 here. I guess you can imagine what it'll look like when using a parallelism of 128.

Hopefully fixed by #2319 and #2349


check the old deadlines

it would be great if we can see the old deadlines

For now, I don't have a clean way of preventing the page from getting too long and keeping old deadlines. Let me know if you have suggestions / ideas on that.

Closing this for now, feel free to re-open / suggest if you have ideas on this.


Support admonition-callout syntax

Hi!

[!NOTE]
I mean if we could have something like this

As seen this is supported by both Github and Obsidian

I think it's a neat idea, but I don't think I'm going to be the one to add it.
This plugin relies heavily on treesitter to do all the real parsing, and for the most part just the vanilla markdown parser.
Identifying these callouts as a result of them not being part of the syntax is going to be tricky, since it'll end up clashing with block_quotes and incomplete links.
Though since it is valid markdown (at least I think it is, the whole incomplete link thing might be a problem), the parser should be able to read it. At that point writing a query to find block quotes where the first line is a link with no actual link could be pretty doable.
In either case if anyone feels like picking this up I'm more than happy to look over the PR.

Have added support for the callout text here: https://github.com/MeanderingProgrammer/markdown.nvim/commit/43bbefd410333a04baf62ddfa8bb2a2d30a1bbc1
There is still the issue of matching the highlight of the quote marker to the callout which I'll track here: https://github.com/MeanderingProgrammer/markdown.nvim/issues/24
I'm not really sure if I'll be able to get that working in general, but will give it a shot.
I figured in either case having the text on its own would be nice, even if the quote markers all remain the same color.

That's awesome, thank you for reconsidering  !


Check count matrix is an integer

Check that integer read counts are stored as integers not numerics, which is more accurate and should save memory/space. Check in two places:

reads_to_list in bam_to_h5.R, which produces the count matrix initially and places into the h5 file
generate_stats_figs.R, including new function get_gene_datamat which reads these matrices from the h5 file

relevant to #32 and #68, in which branch get_gene_datamat is defined

For reference:  get_gene_datamat function has been changed to: GetGeneDatamatrix in generate_stats_figs.R.
This check for integer read counts is NOT implemented in pull request #85 currently but this change could be included as part of remaining refactoring required for #32

Something that needs to be covered with #213 testing sweep probably?
Note that GetGeneDatamatrix function has been moved to rscripts/read_count_functions.R alongside other key functions from generate_stats_figs.R.
#61 refactoring bam_to_h5.R should also take note of this test for integer storage in reads_to_list as mentioned above.

This came up while @FlicAnderson was addressing #153.
After closing #153, we can do a separate sweep to check the integer-ness of these count matrices.
Relevant to #238 - AFAIK all these values in the h5 file should be integers, so that's worth thinking about during the tests.

This came up while @FlicAnderson was addressing #153.
After closing #153, we can do a separate sweep to check the integer-ness of these count matrices.
Relevant to #238 - AFAIK all these values in the h5 file should be integers, so that's worth thinking about during the tests.


Update MMX libraries and replace scala_tools.time

Update MMX libraries versions
Replaced scala_tools.time by nscala_time since scala_tools.time doesn't support Scala 2.12 and nscala_time is being actively maintained

Seems like new finagle 6.35.0 is failing for scala 2.10 version: https://groups.google.com/forum/#!msg/finaglers/Q86RGwoHHmQ/QKNNGQ--CwAJ
We can't drop scala 2.10 support, at least because we still on old samza version.

I found what causes OOM exception in tranquility tests. It's because of this line: https://github.com/druid-io/tranquility/blob/1905a5027896889ddd0af750f916079dde3bdf13/core/src/main/scala/com/metamx/tranquility/finagle/FinagleRegistry.scala#L89-L89. I think we have next options:

Make failFast true by default in FinagleRegistryConfig. It affects clients who rely on default behaviour.
Make failFast true in tests. This helps to make tests pass, but clients, who use scala 2.10 and finagleEnableFailFast false will fail with OOM.
Drop Scala 2.10 support. This leads to update samza and kafka versions.
Build our own finagle version with fix.

I don't think first option might be applied here, but I've put it in the list just to show that we have it. For me personally third option looks as the best choise. @gianm what do you think about it?

Created PR https://github.com/druid-io/tranquility/pull/221 to remove scala 2.10 first

Can we depend on old finagle for scala 2.10?

If we want to update to the latest scala-util we can't use old finagle because it will be incompatible with scala-util code.

@logarithm hmm, I think dropping 2.10 support is fine. Are you going to have to upgrade Samza first? If so could you confirm that a new setup (new Scala + new Tranquility + new Samza) is working at your site before we do an OSS tranquility release?

@gianm thanks for the review! I'll run tests on real data in the next couple of days and let you know about results.

thanks @logarithm !

@gianm I've tested tranquility with scala 2.11, samza 0.12, kafka <IP_ADDRESS> and other updated libraries. It works in our test cluster. So, I think we ready to merge #221 first and then this PR.


proposal: Go 2: nillability annotations

Background
By far the most common cause for panics (for me at least) is nil pointer dereferences - the billion dollar mistake.
This problem isn't unique to golang, but a number of languages are designed from the ground up to avoid it - FP languages for example, as well as rust. They use discriminated unions to mark which objects can be nil, and which can't. However these solutions are difficult to retrofit on a language that's more than a decade old.
C# took a different approach - using annotations to mark which references could be null, and warning if you ever dereferenced a nullable reference. Flow analysis could promote a nullable reference to a non-nullable one. See here for more details.
This approach was an enormous amount of work for the C# team, but extraordinarily successful. Whilst there are a long tail of cases where the flow analysis isn't quite sophisticated enough to realize a reference can't be null, or flow analysis holes where the compiler thinks a null reference is non-null, overall NullReferenceExceptions have basically become practically non-existent.
It's also had another useful advantage - developers can now safely use null as a marker type, without having to document first that the method can return null, and hoping that the developer actually reads the docs.
I think it would be valuable for go to consider a similar approach.
Example
I would suggest a ? prefix before a type to indicate that the type allows nil as a valid value.
var str1 ?*string
_ = str1[0] //warning - nillable pointer

if someCondition {
    str1 = &"hello world"
    _ = str1[0] // no warning - str1 is not nil here
}

var str2 *string = str1 // warning - cannot assign nillable pointer to not nil pointer

if str1 != nil {
    str2 = str1 // no warning - str1 is not nil here
}

Syntax
Type      = TypeName | TypeLit | "(" Type ")" | "?" Type.
TypeName  = identifier | QualifiedIdent .
TypeLit   = ArrayType | StructType | PointerType | FunctionType | InterfaceType |
	    SliceType | MapType | ChannelType .

It would be illegal for a type to have multiple "?" annotations, but the subparts might all be annotated separately. E.g. ?*?map[?interface{}]?func(). This would be a nillable pointer to a nillable map from nillable interfaces to nillable funcs.
Semantics
Flow analysis is used to determine at all points whether a storage location is nillable or not. Nillability is updated when a location is assigned to, or when a location is checked to see if it's nil.
A warning will occur when a storage location which is currently nillable is

dereferenced
assigned to a variable marked as not nil
passed as a parameter to a func if the parameter is marked as not nil
appended to a slice where the slice element type is not nil
used as key/value in a map where the key type/value type is marked as not nil
used as a receiver of a func if the reciever is marked as not nil
etc.

It will be possible to suppress such warnings via some syntax, possibly by appending ! to the expression like C#.
When initializing a struct it would be required to initialize all non-nillable fields. For example:
type MyStruct struct {
    *string Field1
    ?*string Field2
    string Field3
}

_ = MyStruct{} // warning: Field1 is nil
str := "Hello World"
_ = MyStruct{Field1: &str1} // no warning

Slices
Slices made with make appear to have a type hole:
slice := make([]*string, 5)
_ = *slice[0] // panic: nil pointer dereference

As a result it should be illegal to use make to create a slice with non-0 length of a non-nillable type. This should be perfectly acceptable as there is a trivial workaround - set the capacity to the desired total size, and then append the elements one by one.
Error Handling
When a method returns a non-nil error, any other return values which are usually non-nillable would not be required to be nil.
As a result, accessing such a value before checking if the err is nil, will lead to a warning.
E.g.
func getString(succeed bool) (*string, error) {
    if succeed {
        str := "Hello World"
        return &str, nil
    }
    return nil, errors.New("Failed") // no warning
}

str, err := getString()
_ = *str // warning: nil dereference
if err != nil {
    return err
}
_ = *str // no warning

Breaking changes
This proposal requires adding warnings in places where there previously weren't any. On the other hand it should not change semantics of any existing code, just add extra diagnostics.
C#s solution to this was to gate the feature behind a compiler switch, which could be enabled at the level of a line, a file, a project, etc. In C# 9.0 this was off by default, and in C# 10 it was enabled by default, giving some time to migrate. By now most maintained projects have this feature enabled, at least for some code.
Go could go for a similar solution here, but I would fully understand if this is too unpalatable.
Template Questions
Would you consider yourself a novice, intermediate, or experienced Go programmer? intermediate
What other languages do you have experience with? Significant work experience with C#, Scala, Python. Passing familiarity with a number of others.
Would this change make Go easier or harder to learn, and why? It would add an extra concept to learn, but reduce the number of panics encountered by beginners, which will make the learning experience smoother and less frustrating. Overall a bit of a wash.
Has this idea, or one like it, been proposed before? A brief search couldn't find anything similar.
Who does this proposal help, and why? This should help all users by reducing a common kind of bug.
What is the cost of this proposal? This has a very high cost in compiler work. For C# this was the second most expensive feature ever added, after generics. Go is a simpler language, so it should be less expensive, but still a lot of work. It also requires updating all existing code to get the full benefits of this proposal.
What is the compile time cost? This requires a flow analysis pass which is the main cost. It's not insignificant, but is a very well understood problem, with lots of algorithms which can do this efficiently as the analysis can be conservative.
What is the run time cost? None
Can you describe a possible implementation? C#/roslyn would be the best example too look at for possible implementations
Is the goal of this change a performance improvement? no
Does this affect error handling? Yes, as described above.
If so, how does this differ from previous error handling proposals? No connection
Is this about generics? No
Other
I have done significant work on nullable reference types in the C# compiler (roslyn) and am friendly with most of the team. If you are interested in looking at roslyn as prior art, I can help or put you in touch with members of the team.

In Go, nil is a lot less problematic than in other languages, because it doesn't affect method dispatch:
func (v *someType) foo() {
   if v == nil {
      // do something safe
   }
   ...
}

That's nice and all, but the do something safe path is almost never available, which is why most code does not do this, including the stdlib:
https://play.golang.org/p/Q_wU4fMOp7G

Go already has non nullable types. Just don't use pointers, but prefer value types in stead.
https://play.golang.org/p/JRE-bsK1GMt
The real problem is not the fact that there are null pointers, but that pointers are used too often. Unlike many languages, Go language makes value semantics feasible.

@beoran there are legitimate reasons to use pointers, while still having nil values be undesirable. waiving that away by saying "use values" isn't really helpful.

As far as we can tell this proposal is not backward compatible.  Today many types are nillable.  Adding a notation to mark which types are nillable doesn't seem possible today.  That said, perhaps we could instead add an explicit marker for types that are not nillable.
As mentioned above, there are issues with zero values.  Go relies on zero values in many ordinary cases, such as declaring variables, calling make with a slice element type that is or contains non-nillable types, append on such a slice type.  Banning all uses of these ordinary operations for non-nillable types would be a major change to the language.
It may be troublesome to add flow control specifications to the language specification.  And it would have to be added to the spec; we don't want different compilers to give different nilability errors, as that would be mean that Go programs would build with some compilers but not others.

Based on the discussion above, this is a likely decline.  Leaving open for four weeks for final comments.

No further comments.


Setup Error on Windows

Hello, i first got the same error as francoissabot, i used your solution and it compiled, but then it returned this error.
./install.sh: line 35: /c/Users/frede/Ablage/Coding/Git Reps/pocket2rm/cmd/pocket2rm-setup/main: cannot execute binary file: Exec format error
Im sorry if its me whos causing, i never used go before and im using windows were i use cmder.exe to run it

sorry to hear it's not working. the installation in still very much DIY and since im on a mac i cannot easily check the windows side of things. if i ever get to it (or someone wants to help), i want to provide pre-compiled binaries


Inheritance version controller

I have a controller like this:
namespace WebApplication1.Controllers.V1
{
    [ApiVersion("1")]
    [RoutePrefix("api/v{version:apiVersion}/values")]
    public class ValuesController : ApiController
    {
        // GET api/values
        public virtual IEnumerable<string> Get()
        {
            return new string[] { "value1 v1", "value2 v1" };
        }

        // GET api/values/5
        public virtual string Get(int id)
        {
            return $"value{id} v1";
        }
    }
}

and another controller that inherits from V1.ValuesController like this:
namespace WebApplication1.Controllers.V2
{
    [ApiVersion("2")]
    [RoutePrefix("api/v{version:apiVersion}/values")]
    public class ValuesController : V1.ValuesController
    {
        // GET api/values
        public override IEnumerable<string> Get()
        {
            return new string[] { "value1 v2", "value2 v2" };
        }
    }
}

but when I make a request to  http://localhost:51909/api/v2/values/5 , I got this response:
{
    "error": {
        "code": "UnsupportedApiVersion",
        "message": "The HTTP resource that matches the request URI 'http://localhost:51909/api/v2/values/5' does not support the API version '2'.",
        "innerError": {
            "message": "No route providing a controller name with API version '2' was found to match request URI 'http://localhost:51909/api/v2/values/5'."
        }
    }
}

Is there any whay to do this? I mean inherit code from a base controller to avoid duplicated code.

Based on your setup, I don't conceptually see a reason why it wouldn't work. I suspect it may have something to do with your routing configuration. Are you using attribute or convention-based routing? Hopefully, you're not using both. I strongly discourage both; it's confusing. In addition, after many failed attempts, I've concluded that there is no real way to support API versioning for a single service using both routing styles. You can only mix styles if you use the same style for all API versions of a service that your controllers implement.
I mention that because I only see [RoutePrefix].  The route prefix does not define a route.  That means your example has no routes. If it works or ever worked, it must be due to convention-based routing. You should be able to prove that by ensuring the following:

Make sure your configuration does not call MapHttpRoute (which the default template does)
Make sure your configuration does call MapHttpAttributeRoutes

At that point, you should see that no routes work with or without API versioning.  To fix things, you should be able to do one of the following:

Change [RoutePrefix] to [Route]
Add [Route] to each action

With all of that in place, I expect that things should be working for you, including the inheritance bits.

Change [RoutePrefix] to [Route]
Both the V1 and V2 controller mush have the [Route]  ?

I believe not because the RouteAttribute is inherited.

I tried your recomendations, this is how the controllers and the WebApiConfig look like:

V1 Controller

namespace WebApplication1.Controllers.V1
{
    [ApiVersion("1")]
    [RoutePrefix("api/v{version:apiVersion}/values")]
    public class ValuesController : ApiController
    {
        // GET api/values
        public virtual IEnumerable<string> Get()
        {
            return new string[] { "value1 v1", "value2 v1" };
        }

        // GET api/values/5
        public virtual string Get(int id)
        {
            return $"value{id} v1";
        }
    }
}

V2 Controller

namespace WebApplication1.Controllers.V2
{
    [ApiVersion("2")]
    public class ValuesController : V1.ValuesController
    {
        // GET api/values
        public override IEnumerable<string> Get()
        {
            return new string[] { "value1 v2", "value2 v2" };
        }
    }
}

WebApiConfig

 public static void Register(HttpConfiguration config)
        {
            // Web API configuration and services

            // Web API routes

            var constraintResolver = new DefaultInlineConstraintResolver()
            {
                ConstraintMap =
                {
                    ["apiVersion"] = typeof( ApiVersionRouteConstraint )
                }
            };

            config.MapHttpAttributeRoutes(constraintResolver);
            config.AddApiVersioning(options =>
            {
                options.ReportApiVersions = true;
            });

        }

but I'm getting the same response UnsupportedApiVersion calling /api/v2/values/5
If I change [RoutePrefix] to [Route] I get the error on both the V1 and V2 controller.

I found the issue. It's within ASP.NET Web API itself. Despite the [Route] and [RoutePrefix] attributes being inheritable, the platform intentionally ignores them.  Have a look at the DefaultDirectRouteProvider.cs file and you'll see that inherited attributes are not considered. The framework implements IDirectRouteFactory through attributes. We all commonly call it attribute routing, but the name of the feature is actually direct routing.
 I suspect the reason for this behavior is that inheritance would never work the way you are using it without API versioning. Web API would just barf and say the routes are ambiguous. To overcome the built in behaviors, you need to replace the IDirectRouteProvider with an implementation that will considered inherited attributes. I'll attached the world's simplest demo and it worked for me.  Give it a go for yourself and let me know how it works out.
InheritanceDemo.zip

Did this solution work for you? Just want to make sure your issue was resolved before closing. Thanks.

Sorry, this didn't, tomorrow I will upload an example of what exactly I
need to do.
On Mon, Jun 19, 2017 at 9:44 PM Chris Martinez<EMAIL_ADDRESS>wrote:

Did this solution work for you? Just want to make sure your issue was
resolved before closing. Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/aspnet-api-versioning/issues/142#issuecomment-309620580,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIGiBy-c-NkBcTJgcRVO13Mcz1Bq3RhHks5sFyP9gaJpZM4N5FPi
.

This is the example app:
Call example to /api/v1/values

Call example to /api/v1/values/2

Call example to /api/v2/values

Call example to /api/v2/values/2

WebApplication1.zip

I looked your example, but the approach you are trying to use will never work. You can inherit an implementation, but you cannot inherit the API version mapping. Doing so would result in ambiguous routes.
Using your method (if I understand what you are asking):

V1.ValuesController

GET = /api/v1/values
GET = /api/v1/values/1

V2.ValuesController

GET = /api/v1/values
GET = /api/v1/values/1
GET = /api/v2/values
GET = /api/v2/values/1

Using my method (as previously posted)

V1.ValuesController

GET = /api/v1/values
GET = /api/v1/values/1

V2.ValuesController

GET = /api/v2/values
GET = /api/v2/values/1

I think I understand what you're trying to solve, but admittedly I'm not a fan of using inheritance to solve this problem. Regardless, it's impossible to have more than one controller type and/or action that map to the same route and API version combination. That will result in runtime failures because they are ambiguous.
For clarity and maintenance, my suggestion would be to only use inheritance to share common functionality among all your controllers and leave the routing and API version mapping explicit per controller. If all your routes will be the same and only the implementation varies by API version, then you can use the extensions I demonstrated to realize that. Other than that, I'm not sure how you can achieve your goal.
Let me know if I've misunderstood something.

Just a few things:
Using my method:
V1.ValuesController
GET = /api/v1/values
GET = /api/v1/values/1

V2.ValuesController
GET = /api/v2/values /// since this actions is overiden
GET = /api/v2/values/1 /// since this action is inherited from V1.ValuesController but not overiden

The only way I cand reach this is overriden Get(int id) method on V2.ValuesController but jus invoking base.Get(id), something like this:
V1.ValuesController
namespace WebApplication1.Controllers.V1
{
    [ApiVersion("1")]
    [RoutePrefix("api/v{version:apiVersion}/values")]
    public class ValuesController : ApiController
    {
        // GET api/values
        [HttpGet]
        [Route("")]
        public virtual IEnumerable<string> Get() => new[] { "value1 v1", "value2 v1" };

        // GET api/values/5
        [HttpGet]
        [Route("{id:int}")]
        public virtual string Get(int id) => $"value{id} v1";
    }
}

V2.ValuesController
namespace WebApplication1.Controllers.V2
{
    [ApiVersion("2")]
    [RoutePrefix("api/v{version:apiVersion}/values")]
    public class ValuesController : V1.ValuesController
    {
        // GET api/values
        [Route("")]
        public override IEnumerable<string> Get() => new[] { "value1 v2", "value2 v2" };

        [Route("")]
        public virtual string Get(int id) => base.Get(id);
    }
}

Of course this dont look very useful, but in a real scenario the response will be a model that could be the same in each version..

Correct; that will work. If you use extended IDirectRouteProvider I provided, you can get away with only overriding the methods; you won't have to re-specify the [RoutePrefix] and [Route] attributes. Beyond that I think you may be up against how Web API works.
My suggestion would be to make a collaborator the thing that is reused rather than the controller. IMO, it will also make it easier to rationalize what a controller implements when someone looks at the source.
For example:
namespace V1
{
  [ApiVersion( "1.0" )]
  [RoutePrefix( "api/v{version:apiVersion}/values" )]
  public class ValuesController : ApiController
  {
     readonly IRepository<Model> repository;
     public ValuesController( IRepository<Model> repository ) => this.repository = repository;

     [Route]
     public async Task<IHttpActionResult> Get() => Ok( await repository.GetAll() );

     [Route( "{id:int} " )]
     public async Task<IHttpActionResult> Get( int id ) => Ok( await repository.GetSingle( id ) );
  }
}
namespace V2
{
  [ApiVersion( "2.0" )]
  [RoutePrefix( "api/v{version:apiVersion}/values" )]
  public class ValuesController : ApiController
  {
     readonly IRepository<Model> repository;
     public ValuesController( IRepository<Model> repository ) => this.repository = repository;

     [Route]
     public async Task<IHttpActionResult> Get() => Ok( await repository.GetAll() );

     [Route( "{id:int} " )]
     public async Task<IHttpActionResult> Get( int id ) => Ok( await repository.GetSingle( id ) );
  }
}

Your repository and/or model might change between API versions or you might have multiple repositories.
Naturally, this is just one more variation of numerous possibilities. There are several solutions here that will work, but I'm not sure any of one of them individually gets you everything you want. I think you're reaching the edge of what's possible without changing a significant amount of Web API plumbing.

Ok, thanks!

The problem will go away if you do something like this i guess. @jcmordan
 [RoutePrefix( "api/v{version:apiVersion}/[controller]/[action]" )]

Thanks for the suggestion @irowbin , but unless I'm wrong the support for the [controller] and [action] replacement tokens were added in ASP.NET Core. This context here is for Web API. Your suggestion should work in Core.

It seems like you have what you need @jcmordan . If you continue to run into any issues. Feel free to reopen this issue. Thanks.

This is very interesting topic! I am looking for a solution how that gives me a possibility to override just some endpoints in the version 2. I have tried to modify you solution, but it the routing of not overrided endpoint fails with this error.
No route providing a controller name with API version '2' was found to match request URI 'http://localhost:21956/api/v2/values/4'.
I am also attaching adjusted version of my desired setup
InheritanceDemo.zip


imaginary lighter item

it's like a lighter but imaginary

Asset:

https://drive.google.com/file/d/1-5B224Fn2i0w3aU1cGTpfQiY6fO57Yyi/view?usp=sharing

Do we need to wait until after we implement the asset to close the issue?

Credit: cherryberry24 / Sparkle Spark


chore(test): increase thread count for ParallelParameterized

The tests are mostly IO bound, it should be safe to increase the number of threads to be higher than the number of cores.
Integration runtimes
Before
[WARNING] Tests run: 739, Failures: 0, Errors: 0, Skipped: 424, Time elapsed: 354.955 s - in com.google.cloud.storage.conformance.retry.ITRetryConformanceTest

After
[WARNING] Tests run: 739, Failures: 0, Errors: 0, Skipped: 424, Time elapsed: 96.439 s - in com.google.cloud.storage.conformance.retry.ITRetryConformanceTest

I checked the cpu usage of the build host while the build ran wand we were still only using ~60% of the CPU.


Delete using empty  ARM templates

[Enter feedback here]
Good Morning - it may be useful to include the method helpfully referenced here
https://www.codeisahighway.com/effective-ways-to-delete-resources-in-a-resource-group-on-azure-in-2021/
to use a blank ARM template ?
That way; one would be able to utilise the Azure DevOps pipeline  to clear resources as well.
Thank you

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

ID: e30e8626-d145-a638-e3ad-6948f7897dec
Version Independent ID: a261c750-16ff-ee26-8024-50f724feb291
Content: Delete resource group and resources - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/delete-resource-group.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@anjaneshbabu - thanks for this suggestion. That approach works but it creates some confusion where people inadvertently delete resources they had not intended to delete. We will continue showing how to explicitly delete the resource group. Deployment Stacks might be an option in the future.
#please-close


Release PATCH support and backport it

Fix or minor version?

@joanromano do you have time?

Minor IMO

What about #133 ?

👌
@hernangonzalez FYI

btw yup I have time I can do it

#133 still waiting for the PR, you can do it if you still have Xcode 7 and have time or we can just wait

So @MP0w agree with releasing 2.1.0 (Swift 3) and 1.1.1 (Swift 2.3) ?

@joanromano you mean 1.1.0?

Yep sorry @MP0w

2.1.0 is out! 🎉 https://github.com/devlucky/Kakapo/releases/tag/2.1.0

Aaaaaand 1.1.0 is out https://github.com/devlucky/Kakapo/releases/tag/1.1.0


Newbie - stuck on syntax errors

Hi folks. I've tried this a few times now - everything is OK up until I go to test the Lambda function, and for the life of me I can't figure out what's wrong. Zip file created without /src, I've checked the index.js etc in Notepad++ and all looks OK but I keep getting this syntax error:
Syntax error in module 'index': SyntaxError
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/var/task/index.js:18:18)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
If anyone can help I would be extremely grateful
Thanks

After looking again, my Alexaskill.js was invalid - I must have miscopied that first time round.


Engine tries to lookup libs in "random" folders

Describe the bug
When building the engine from fresh download (main) the solution tries to lookup a lib in a random folder that has no association with the project.
Include a MRE
UNKOWN
Expected behavior
The engine builds
Screenshots

Desktop (please complete the following information):

OS: Windows 10 Home
Version: 10.0.19043 Build 19043

Additional context

It looks like you have an installation of vcpkg with integration into Visual Studio. This modifies where the standard path for libraries is, because the Engine ships its own libraries this can lead to problems. Please remove the vcpkg installation and try again. Note that this has most likely nothing to do with your environment variables.

Since no more information has been provided, I will close this issue. Please comment if you still experience issues


Fix current_temperature is rounded

Description:
Fix now  when temperature_unit == unit_of_measurement the convert_to_display will round it.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

See also #4522

I dont know the right way to fix the problem because in the #4522 @balloob said "Do not convert when passed in unit is already expected unit" but the problem is that my zwave radiator pass a lot of decimals in celsius and I have my home assistant temperature in celsius too.., so the code don't round it.

I think this is a reasonable fix myself, but I want to make sure we're looking at the whole history of this code in case there was some other relevant side-effect from the previous PR.
In any case showing all of the decimal places in the frontend is a defect IMO, and we need some solution.

Yeah this looks good. Thanks for the fix 🐬

Cherry-picked into the 0.42 branch


feat: Added the favourite tweet of jordanwilfry

Please what changes i'm to do! Because i keep following the step but I am
still receiving request for changes!
Le mer. 26 oct. 2022 à 01:05, Steve Yonkeu @.***> a
écrit :

@.**** requested changes on this pull request.
.
—
Reply to this email directly, view it on GitHub
https://github.com/Developer-Student-Clubs-UBa/GDSC-Uba-Tweets/pull/84#pullrequestreview-1155692159,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVGFUTL7SWU537ZA5AALFN3WFBYUHANCNFSM6AAAAAARONKJU4
.
You are receiving this because you were mentioned.Message ID:
<Developer-Student-Clubs-UBa/GDSC-Uba-Tweets/pull/84/review/1155692159@
github.com>


Feature request : add support for SQL

Daft seems like a cool project and it has enough functionalities to be considered useful enough, but for a lot of new users, learning a new API is  annoying, it would be really nice to expose a SQL Interface

Thanks @djouallah! We're actively considering this and there are a lot of people recently asking for it...
What do you think if Daft only support SQL queries (DML), but none of the other DDL or persistence stuff like:

Table management CREATE/DROP TABLE, CREATE INDEX
Manipulating data: INSERT/UPDATE/DELETE/MERGE INTO

I'm imagining an API like this to start with:
df = daft.read_deltalake(...)

df = daft.sql(f"""
SELECT x + 1 FROM {df} WHERE x == 1
""")

df.to_pandas()

ideally this
df = daft.read_deltalake(...)
daft.register("table1",df)

daft.sql(f"""
SELECT x + 1 FROM table1 WHERE x == 1
""").show()

Daft could take one of several approaches to supporting SQL — each of which presents future opportunities.
Approach A — DataFusion (recommended)
The DataFusion SQL crate is likely the best first-step to Daft SQL support. The logical algebra should be easier to translate to Daft builders than the sqlparser AST. This library effectively does the algebra translation for us.

This crate provides a general purpose SQL query planner that can parse SQL and translate queries into logical plans. Although this crate is used by the DataFusion query engine, it was designed to be easily usable from any project that requires a SQL query planner and does not make any assumptions about how the resulting logical plan will be translated to a physical plan. For example, there is no concept of row-based versus columnar execution in the logical plan.

There is existing support for handling multiple input dialects with sqlparser, and we could evolve a custom Daft SQL Analyzer (semantic analysis / logical planning only) without changing the parser (sqlparser) library.
Approach B — sqlparser + Daft Analyzer
This approach is effectively Approach A sans Datafusion SQL; that is, we effectively fork datafusion-sql to have full control over the sqlparser AST to logical algebra translation/analyzer. I understand that this approach gives full control over semantic analysis, but I think this may be too ambitious for a first-pass.
My reservations with Approach B are..

I am not aware of datafusion-sql limitations that warrant the extra effort.
If they exist, we'll find them when it matters ... aka we are limited by them
Any limitations present an opportunity to work with the datafusion community to improve that project.
Approach A is an incremental step to Approach B

Approach C — SQLGlot + Daft Analyzer (python)
This is much like Approach B but coming at it from the Python side. That is, we use the SQLGlot as the SQL parser to support its various (21) dialects, but then add the missing analyzer/planner piece.

However, SQLGlot does not aim to be a SQL validator, so it may fail to detect certain syntax errors.

This analyzer would be written in Python and leverage catalog metadata libraries such as PyIceberg to perform the necessary semantic analysis. Like Approach B this would be a bit more ambitious, so I still recommend Approach A. I also believe that a SQLGlot layer could be decorated on top of Approach A — that is, suppose there's a stabilized "Daft SQL" dialect and we want to support multiple inputs .. we can implement a SQLGlot custom dialect that we redirect the input to.
Something like,
df = daft.sql("SELECT ....")  # approach A

# later releases..

df1 = daft.sql("SELECT ...") # approach A still exists
df2 = daft.sql("SELECT ...", dialect="duckdb") # invoke SQLGlot with input="duckdb-sql" and output="daft-sql"

@RCHowell after some internal discussion, I think we are leaning towards something similar to "Approach B". The first one requires a dependency on datafusion, which would greatly increase our compile time and build size. "Approach C" requires keeping the logic in python, and we've been actively trying to move more of our core logic into rust.

The first one requires a dependency on datafusion, which would greatly increase our compile time and build size

I believe we would only need the datafusion-sql crate rather than the full datafusion crate. I'm not sure if that changes your assessment.

I believe we would only need the datafusion-sql crate rather than the full datafusion crate.

yes, unfortunately since we use a custom arrow implementation (a fork of arrow2) we can't pull in any datafusion crates without pulling in multiple heavy dependencies such as arrow-rs and parquet

Understood, thank you for the clarification!


Add logging module for Micronaut 4

Off to work through the checklist

Yeah, it's done now so I've added the SONAR_TOKEN back in 👍


createMetadataContainerIfNotExistsForMasterKeyAuth

Adding support for creating metadata container if not exists when using masterKey auth, for other auth types (AAD), it will throw an exception.

API change check
API changes are not detected in this pull request.

/azp run java - cosmos- kafka

/azp run java - cosmos - kafka


Left border on mat-button-toggle

In the original material button toggle, https://material.angular.io/components/button-toggle/overview, we can see that when the second item is selected, there is not left border of different color

However in the linked project that uses blui, we can see that the left border of the selected button is slightly darker than the others.

mat-button-toggle-group-bug.zip
It seems to come from this rule

Is this styling as intended ?

Thanks for opening this issue; I'm thinking this should be fixed within our themes so I'll migrate this issue over to there.


install this theme of start,something is wrong

info Creating new site from git:
https://github.com/gregberge/smooth-doc-starter.git
Cloning into 'website'...
remote: Enumerating objects: 16, done.
remote: Counting objects: 100% (16/16), done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 16 (delta 1), reused 13 (delta 1), pack-reused 0
Receiving objects: 100% (16/16), 366.55 KiB | 1.49 MiB/s, done.
success Created starter directory layout
info Installing packages...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/gatsby
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/smooth-doc
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   1 more (react-dom)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>| ^17.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/smooth-doc
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/sunfeipo/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
ERROR
Command failed with exit code 1: npm install
Error: Command failed with exit code 1: npm install

error.js:60 makeError
[21aee85bd6ee71e0]/[execa]/lib/error.js:60:11

index.js:118 handlePromise
[21aee85bd6ee71e0]/[execa]/index.js:118:26

task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5

init-starter.js:135 install
[21aee85bd6ee71e0]/[gatsby-cli]/lib/init-starter.js:135:7

init-starter.js:202 clone
[21aee85bd6ee71e0]/[gatsby-cli]/lib/init-starter.js:202:3

init-starter.js:343 initStarter
[21aee85bd6ee71e0]/[gatsby-cli]/lib/init-starter.js:343:5

create-cli.js:489
[21aee85bd6ee71e0]/[gatsby-cli]/lib/create-cli.js:489:9

I used the following commands in two places to install and test. One is a macbook and the other is aws, both of which have errors. How to do it?
npx gatsby-cli new website https://github.com/gregberge/smooth-doc-starter

I don't provide support on installation sorry.


Add Create-React-App Example

(#94 must be merged first)
Added a Create-React-App and Eel example. The README walks through how to integrate the two stacks and utilizes the new features proposed in #94. This should close #30.

I numbered this example 7 because it looks like #70 might be merged which includes an example 6

Was there any reason you made it 07 instead of 06?

Yeah, PR for #70 already had an example 6 and looked like it might be merged once there was a decision on a better fix for 10:


[Bug] Registry check does not work in the case of multiple registrations and subscriptions at the application level, and provider export error causes Dubbo to fail to start

Pre-check

[X] I am sure that all the content I provide is in English.

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
dubbo3.2.16;
jdk openjdk21
Steps to reproduce this issue
Dubbo3.2.16 uses two Nacos clusters as registration centers to implement application level multi subscription and multi subscription, and configure regirty.check=false. When one of the Nacos clusters is unavailable, dubbo serviceConfig. export reports an error causing startup failure, with the error message 'this.registry is null'
What you expected to happen
When a Nacos cluster is unavailable, it should be possible to export services normally on another Nacos cluster and ignore the other Nacos cluster
Anything else
No response
Are you willing to submit a pull request to fix on your own?

[x] Yes I am willing to submit a pull request on my own!

Code of Conduct

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

Can you show the complete error message?

ServiceConfig#doExportUrl -> RegistryProtocol#export方法中，this.getRegistry(registryUrl)获得的Registry 是null,后面的逻辑没有判断这个值是否null，在RegistryProtocol#register方法中报空指针异常

其他场景也有类似的问题，有的场景会判断Registry是否为null，而正常结束； 有的就类似现在启动export时报空指针异常

我这个是多注册中心的高可用场景，如果多注册支持高可用的话，这里循环其中一个注册中心不应该异常退出

我的配置如图

配置如图

是的，我查看了这个问题，并确定它是存在的。我们应该提交一个合并请求来修复它。 @AlbumenJ

大佬 有计划什么时候修复吗 @AlbumenJ @walkinggo


Job Submission: file selector

Version: 3.2.9 beta
URL: https://www.beta.patricbrc.org/app/SeqComparison
User ID: KPNs_4_Houston
I have two fasta files called KPN1530ec.  One a fasta of the contigs and
the other is a fasta of the plasmid proteins.  Since the proteome
comparison tool abbreviates the path in the genome selection, I can't tell
the difference.

One file is in:  "home/KPN_Annotations”, and the other is in "home/KPN_Plasmid_Spades”.  My main complaint is that "home/../something” is almost entirely useless since (until we can share) everything will be in your home directory.  My genomes should have shown up as "../KPN_Plasmid_Spades/KPN1530ec", and "../KPN_Annotations/KPN1530ec”.
Looking them up with the folder icon works by the way, but it is likely that I didn’t even try because of how many genomes I had.  I am attaching a screen shot, because I just discovered that you can sort them by clicking the column headers (which makes it easier) but the little arrow icon doesn’t appear unless you click on the column header, so you wouldn’t know that it sorts.
PastedGraphic-15.png

@mshukla1 Could you clarify the requirement for this issue? The name label in the drop down list is implemented the same way for all app services. Do you want the label display to include more text (characters) in the drop down list or you want the selection table to show bigger arrow for sorting? The label display has limited space. Currently, only partial path is displayed.  I see that using the same sub-folder and file names can result in the same text display and can be very confusing. What's your suggested change?

@chmao1 I just checked, it seems this issue has been addressed by providing mouseover tooltip on the dropdown items, which show complete file path, instead of abbreviated one.
I am closing the issue.


Strange issues /w install and update

Hi,
So I've installed arkmanager following the instructions, although on Archlinux instead of Ubuntu or Fedora. It seems to work fine, the servers are configured and working but I had a few issues and will fail again soon.. ok first issue.
"arkmanager install" did not actually do much, it made the directory structure ie, "~/ARK/ShooterGame/" but didn't actually put any files inside those directories. I couldn't find an error message in any logs that I know about. But I had a copy of the game downloaded earlier so I just put the files in place and it worked...
.. until an update came out, where it deleted the server binary. arkmanager.log and arkserver.log show no errors, running arkmanager update --verbose shows no errors, but doesn't download any files ever. Manually running "steamcmd +login anonymous +force_install_dir /home/$USER/ark/ +app_update 376030 validate +quit" does fix it temporarily, until the next update comes out.
Interestingly, installing or updating a mod actually works totally fine.
I'm not sure where to look for solving this issue. My first thought was permissions but they seem to be fine. Besides, if there was a permissions issue it would effect installing and updating mods.
Any suggestions on where to look for the problem?

Do you have a staging directory set up?
If so, is there anything in that staging directory, and can the user write to it?

OK I wanted to do some testing to be sure, the problem was I had a copy of steamcmd installed from the package manager and it seemed to be running that copy, when I removed the distro copy and just used steamcmd in a directory as the instructions suggest it seems to be working fine.
Before I did this, I did test with and without a staging directory. Seems odd it installed mods fine but its fixed now anyway. :)


✨ Riders sign up for deliveries via app

Problem Statement
This is tracking everything we need to do to go from where we are now to having

(non-dispatcher) Rider can login via their phone into Bike Brigade
Given a link (from https://bikebrigade.ca/deliveries) a Rider can sign up for a delivery.

Miro board: https://miro.com/app/board/uXjVO_hw8Go=/
Core Issues
### Tasks
- [x] https://github.com/bikebrigade/dispatch/issues/135
- [x] #133
- [ ]  Create a separate changeset for profile for added security
- [x] https://github.com/bikebrigade/dispatch/issues/134
- [x] https://github.com/bikebrigade/dispatch/issues/136
- [ ] When a delivery detail page expires show the distance and metadata but not the link in itinerary, to hide people's addressese
- [ ] https://github.com/bikebrigade/dispatch/issues/137
- [ ] #139
- [ ] #140
- [ ] Choose a sample campaign or two and slow launch rider-facing signup (issue TBD)
- [ ] Full launch of rider-facing campaign signup (issue TBD)
- [x] #241
- [ ] Opt-in into the leaderboard (riders can choose to show their name on the leaderboards)
- [ ] https://github.com/bikebrigade/dispatch/issues/261

Nice to haves / Future work
- [ ] https://github.com/bikebrigade/dispatch/issues/138
- [ ] #128
- [ ] Show all the opportunities inside the app? (possibly linking to existing sheets, or wait till we switch everything over)
- [ ] Milestones and badges

Variations in signup requirements

Rider specifies ONLY how many deliveries that can take (Foodshare)
Rider chooses day of delivery (PCFB)
Drop off location not known at opportunity creation (SNAP)
Rider specifies number of units they can take (MAP, OOTC, ESN, Moss Park CTS)
Split pickup time (PCFB)
Rider chooses drop off location (various CFTO programs)
Grouped deliveries - same building (ALAB, SPAFYCC)
Alternating schedule - bi-weekly (SOH)

Variations in signup requirements
~- Rider specifies ONLY how many deliveries that can take (Foodshare)~

Rider chooses day of delivery (PCFB)
Drop off location not known at opportunity creation (SNAP)
Rider specifies number of units they can take (MAP, OOTC, ESN, Moss Park CTS)
Split pickup time (PCFB)
Rider chooses drop off location (various CFTO programs)
Grouped deliveries - same building (ALAB, SPAFYCC, FYFB)
Alternating schedule - bi-weekly (SOH)
Routes with no address (EYMOW, Dixon, WNH)
Campaigns that don't use signups (EYMOW, Dixon, WNH)
Pre-assigned rides, dispatcher assigns regular riders

@mveytsman, cc @teesloane this is where the signup variuations are. They may not make a lot of sense on their own. A couple screens from https://xd.adobe.com/view/e64dceb0-2df2-400f-8971-405ce662631f-b31e/ show some basic wireframes related


Undo mistaken RTM cab change

Realized that the RTM CAB version was actually correct - <IP_ADDRESS> for both SPS and SRS
We were looking at the wrong branch and file for the shipped version yesterday.
Actually installing the RTM version, we found what we missed.

@Aniruddh25 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Feat network steps

Description of changes:
Port over common connectivity steps from EF to OTF, which are used by several tests that are being ported into repositories using OTF as a dependency
Why is this change necessary:
Without it we can not simulate scenarios were the network connection is lost.
How was this change tested:
Built OTF locally and used the step on a test that is being ported for the log manager.

UAT Test Passing: https://github.com/aws-greengrass/aws-greengrass-testing/actions/runs/3690242190/jobs/6247046788 on external_pr_173 branch


[bug]: LAN Interfaces limited to ~20

Prerequisites

[X] I have searched for existing issues that already report this problem.

embassyOS Version
0.3.2
Device
Laptop/Desktop
Device OS
Linux
Device OS Version
5.19
Browser
Firefox
Browser Version
102
Current Behavior
Running more than ~20 LAN interfaces breaks Avahi:
Could not add CNAME record to Avahi entry group: "Too many entries"
thread 'main' panicked at 'Failed to load Avahi services', src/bin/avahi-alias.rs:98:17
Expected Behavior
Can run at least as many LAN interfaces as are available on prod market
Steps to Reproduce

Run 20+ LAN interfaces
All LAN interfaces go down

Anything else?
No response

Please check here.
If I am reading this correctly, I believe you may be able to utilize the following to adjust the maximum mdns records per client:
objects-per-client-max= Takes an unsigned integer. The maximum number of objects (entry groups, browsers, resolvers) that may be registered per D-Bus client at a time. If the maximum number is reached further object creation will be refused until at least one object is freed.

Was this fixed by https://github.com/Start9Labs/embassy-os/pull/1869?

Yes


Add: Rakyat Bengkulu Televisi [ID]

Channel Name
Rakyat Bengkulu Televisi
Alternative Names (optional)
RBTV
Network (optional)
No response
Owners (optional)
No response
Country
ID
Subdivision (optional)
No response
City (optional)
Bengkulu
Broadcast Area
c/ID
Languages
ind
Categories (optional)
general
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://rakyatbengkulu.disway.id/
Logo
https://i.ibb.co/DCNZyPH/RBTV-Bengkulu.png
Notes
No response

Already in the database: https://iptv-org.github.io/channel?id=RakyatBengkuluTV.id


Additional German translations added

After seeing the discussion regarding the name "Administrative entity" i've made another commit where it translates to "Autonomous System Name". If you decide to stay with your original name you can take this commit instead.

Thanks!


Builder with context

I need of the context in widgets on builder
BuilderWhen(
  condition: condition,
  isTrue: (context) => Text(
    'Condition is TRUE',
    style: TextStyle(fontSize: 24, color: Colors.green),
  ),
  isFalse: (context) => Text(
    'Condition is FALSE',
    style: TextStyle(fontSize: 24, color: Colors.red),
  ),
)

It seems good


Black Screen on fedora 35 Wayland

Describe the bug
When opening the latest rpm installation of lens, a window will open, but the content will be just black
To Reproduce
Steps to reproduce the behavior:
dnf install https://api.k8slens.dev/binaries/Lens-5.3.3-latest.20211223.1.x86_64.rpm
(rm -rf ~/.config/Lens/ # Already tried that )
/opt/Lens/lens

Expected behavior
A window with content will open.
Screenshots

Environment (please complete the following information):

Lens Version: 5.3.3
OS: Fedora 35
Installation method: rpm
GPU: Nvidia
Driver: 495.46
Displayprotocoll: Wayland

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
info:    ▪ 📟 Setting Lens as protocol client for lens:// +0ms
info:    ▪ 📟 Protocol client register failed ❗ +11ms
info:    ▪ [APP-PATHS]: initializing +1ms

Before updating:
[118536:0119/101658.830345:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
Will provide if necessary, but since app doesn't crash I don't think it's relevant

Additional context
Cannot try without wayland right now unfortunately, but I suspect that it would work as expected.

Are those your full logs? You should have a log line similar to "Window manager starting" if you are getting a window open.

info:    ▪ 📟 Setting Lens as protocol client for lens:// +0ms
info:    ▪ 📟 Protocol client register failed ❗ +10ms
info:    ▪ [APP-PATHS]: initializing +1ms
info:    ▪ 🚀 Starting Lens from "/opt/Lens/lens" +52ms
info:    ▪ 🐚 Syncing shell environment +0ms
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
info:    ▪ 💾 Loading stores +178ms
info:    ▪ [USER-STORE]: LOADING from  ... +2ms
info:    ▪ [USER-STORE]: LOADED from /home/modzilla/.config/Lens/lens-user-store.json +19ms
info:    ▪ [CLUSTER-STORE]: LOADING from  ... +1ms
info:    ▪ [CLUSTER-STORE]: LOADED from /home/modzilla/.config/Lens/lens-cluster-store.json +15ms
info:    ▪ [HOTBAR-STORE]: LOADING from  ... +0ms
info:    ▪ [HOTBAR-STORE]: LOADED from /home/modzilla/.config/Lens/lens-hotbar-store.json +2ms
info:    ▪ [EXTENSIONS-STORE]: LOADING from  ... +0ms
info:    ▪ [EXTENSIONS-STORE]: LOADED from /home/modzilla/.config/Lens/lens-extensions.json +1ms
info:    ▪ [FILESYSTEM-PROVISIONER-STORE]: LOADING from  ... +0ms
info:    ▪ [FILESYSTEM-PROVISIONER-STORE]: LOADED from /home/modzilla/.config/Lens/lens-filesystem-provisioner-store.json +0ms
info:    ▪ [WEBLINK-STORE]: LOADING from  ... +1ms
info:    ▪ [WEBLINK-STORE]: LOADED from /home/modzilla/.config/Lens/lens-weblink-store.json +1ms
info:    ▪ 🔌 Starting LensProxy +7ms
info:    ▪ [LENS-PROXY]: Proxy server has started at <IP_ADDRESS>:45961 +16ms
info:    ▪ 🔎 Testing LensProxy connection ... +1ms
info:    ▪ ⚡ LensProxy connection OK +9ms
info:    ▪ 🖥  Starting WindowManager +1ms
APPIMAGE env is not defined, current application is not an AppImage
info:    ▪ 🧩 Initializing extensions +22ms
info:    ▪ [EXTENSION-DISCOVERY] loading extensions from /home/modzilla/.config/Lens +0ms
info:    ▪ [WINDOW-MANAGER]: Loading Main window from url: http://localhost:45961 ... +125ms
info:    ▪ [EXTENSION-INSTALLER] installing dependencies at /home/modzilla/.config/Lens +51ms
info:    ▪ [EXTENSION-INSTALLER] dependencies installed at /home/modzilla/.config/Lens +634ms
info:    ▪ [EXTENSION-DISCOVERY] watching extension add/remove in /home/modzilla/.k8slens/extensions +1ms
Native extraction module not loaded, msgpackr will still run, but with decreased performance. Cannot find module 'msgpackr-extract'
Lens Cloud Extension activated
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +57ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /home/modzilla/.config/Lens/extension-store/lenscloud-lens-extension/auth-token-store.json +1ms
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +1ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /home/modzilla/.config/Lens/extension-store/lens-survey/preferences-store.json +1ms
telemetry main extension activated
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +31ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /home/modzilla/.config/Lens/extension-store/lens-telemetry/preferences-store.json +1ms
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +3ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /home/modzilla/.config/Lens/extension-store/lenscloud-lens-extension/select-space-store.json +1ms
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +10ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /home/modzilla/.config/Lens/extension-store/lenscloud-lens-extension/startup-store.json +1ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+0ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+65ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+1ms
info:    ┏ [IPC-RENDERER]: adding extension listener +2ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'deleteOneCluster',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'deleteOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┗ [1] { channel: 'logOut', extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' } }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'createWeblink',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'deleteOneWeblink',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'loadRemoteSpacesClusters',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'createOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'leaveOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┗ [1] { channel: 'selectSpace', extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' } }
info:    ┏ [IPC-RENDERER]: adding extension listener +12ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'network:offline',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'network:online',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
error:   ▪ [CLUSTER-MANAGER]: failed to add cluster: Error: EISDIR: illegal operation on a directory, read +1ms
error:   ▪ [CLUSTER-MANAGER]: failed to add cluster: Error: EISDIR: illegal operation on a directory, read +0ms
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'provisionDevCluster',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'removeDevCluster',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'stopDevClusterEvent',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'startDevClusterEvent',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.3-latest.20211223.1' }
info:    ┗ [4] }
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+1ms
info:    ▪ [WINDOW-MANAGER]: Main window loaded +371ms
info:    ▪ [KUBECONFIG-SYNC]: starting requested syncs +361ms
info:    ┏ [KUBECONFIG-SYNC]: starting sync of file/folder +0ms
info:    ┗ [1] { filePath: '/home/modzilla/.config/Lens/kubeconfigs' }
info:    ┏ [KUBECONFIG-SYNC]: starting sync of file/folder +0ms
info:    ┗ [1] { filePath: '/home/modzilla/.kube' }
error:   ▪ [CLUSTER-MANAGER]: failed to add cluster: Error: EISDIR: illegal operation on a directory, read +1ms
info:    ▪ 📡 Checking for app updates +1ms
info:    ▪ [AUTO-UPDATE]: electron-updater: Checking for update +0ms
error:   ▪ [AUTO-UPDATE]: electron-updater: Error: Error: ENOENT: no such file or directory, open '/opt/Lens/resources/app-update.yml' +4ms
error:   ┏ [UPDATE-CHECKER]: failed with an error +0ms
error:   ┗ [1] { error: "Error: ENOENT: no such file or directory, open '/opt/Lens/resources/app-update.yml'" }
error:   ▪ [CLUSTER-MANAGER]: failed to add cluster: Error: EISDIR: illegal operation on a directory, read +5ms
error:   ▪ [CLUSTER-MANAGER]: failed to add cluster: Error: EISDIR: illegal operation on a directory, read +6ms
error:   ▪ [CLUSTER-MANAGER]: failed to add cluster: Error: EISDIR: illegal operation on a directory, read +14ms
warn:    ┏ [KUBECONFIG-SYNC]: encountered errors while loading config: "value" must be of type object +4ms
warn:    ┃ [ 1] {
warn:    ┃ [ 2]   filePath: '/home/modzilla/.kube/kubectx',
warn:    ┃ [ 3]   details: [
warn:    ┃ [ 4]     {
warn:    ┃ [ 5]       message: '"value" must be of type object',
warn:    ┃ [ 6]       path: [],
warn:    ┃ [ 7]       type: 'object.base',
warn:    ┃ [ 8]       context: { type: 'object', label: 'value', value: 'kubernetes-lab-admin@kubernetes-lab' }
warn:    ┃ [ 9]     }
warn:    ┃ [10]   ]
warn:    ┗ [11] }
info:    ▪ [WINDOW-MANAGER]: Main window has reported that it has loaded +10ms

Okay I don't quite see anything wrong there. Given that a window is opening. Would you be able to force open the developer tools and post the console logs from that?

Okay it seems to be a nvidia issue... The gpu accelleration doesn't yet work in chrome on wayland. By disabling the gpu with or without the wayland platform will result in a working app.
DISPLAY="" /opt/Lens/lens -enable-features=UseOzonePlatform -ozone-platform=wayland -disable-gpu

Thanks nevertheless!


Implement environment variables

Resolves #97
Fixes #93
Description:
Introduces 3 new env vars
Changes made:
56de767a82122e780df2d0fc474603b3e781120a solves #97, adds t("Join at") {link} to /game page
586dfd1c170e7f5402b9977425a80892aa4e649c adds csv and image max upload size vars
29003cee8aba3d42d9b69972fab9430b91b19d0c fixes a setTimeout bug
e0db5e2c85e4f2d17640ea4fdb4a707f0c576c72 solves #93 by checking actual file extension, also introduces utils/ folder for commonly used JS functions
c8cf2b382a9f45bd2bffa25caaea381238a04471 adds prettier config so contributors can format with the same settings

The title page logo/title sizing needs an overhaul, I've made a band-aid fix to it, but it should be simpler than what is currently done

Waiting for #109


doc: translate strict mode to zh-hant

doc: translate strict mode to zh-hant

@neighborhood999 Just updated based on suggestion. Thanks


Move IdentityOptions from Microsoft.AspNetCore.Builder to identity namespace

I guess it has been in Microsoft.AspNetCore.Builder all this time, this used to be the pattern so intellesense would work before we switched consistently to lambdas everywhere...  Seems like we should welcome the options class home.  This realistically shouldn't break many apps, as its rare for the options type to be used by itself without any other identity classes...  Maybe something we can do post preview 2...  @ajcvickers

The benefit isn't that big, so I don't think its worth adding any build stability issues to try and slam it in right now

If you do that, please also consider moving all the scheme handlers options (in aspnet/Security) to their respective repos :smile:

You mean moving the options for the security/auth handlers to the right namespace?  I think they are in the right repo today :)

lol yeah, I meant namespace, not repo, sorry for the confusion :sweat_smile:

@ajcvickers ok for me to move the options type to the proper namespace now?  We already moved it to a different assembly in (Extensions), might as well move it to the proper home namespace

Yes

eb3ff7fc32dbfff65a1ba6dfdca16487e0f6fc41


[WIP] Feature/click responses edge cases

 Here is an overview of what got changed by this pull request:

Clones added
============
- CurrencyConverterCalculator/UI/Calculator/CalculatorSEED.swift  1
- CurrencyConverterCalculator/UI/Bar/BarSEED.swift  1

See the complete overview on Codacy


How to set default hostname with driver.instance.name

Hi
Do you know if it's possible to set default hostname with the kitchen instance name by using kitchen configuration file ?
I read that we can use a static name ( using "driver_config:hostname" key) but it seem it's not possible to use a variable name.
My need is to use the fact %hostname with puppet to choose the right hiera file, but it's not possible with the default docker name. So it will be usefull to set hostname like kitchen instance name.
If it's not possible by using kitchen configuration file, this issue has already implemented for vagrant (https://github.com/test-kitchen/kitchen-vagrant/commit/e50d1460bbb3c7c43a6644e18a6223209ce86194 )
It's seems that we just need to add the following code in driver.rb  :
default_config :hostname do |driver|
driver.instance.name
end
Example:
$ kitchen list
Instance                     Driver  Provisioner  Last Action
default-centos-66            Docker  PuppetApply  Converged
test-A-centos-66             Docker  PuppetApply  Created
$ kitchen login test-A-centos-66
kitchen@localhost's password:
[kitchen@test-A-centos-66 ~]$
Thank you in advance !

Yes, this option would be really very useful
Thank

This would be beneficial for me as well. Attempting to test a cookbook that uses the node.name attribute, and am unable to validate using kitchen.yml with Docker.


Show header on rollup does not work with Opera

Opera Test platform:
Version: 12.18
Build: 1872
Platform: Win32
System: Windows 7

I'll have to look into this, I've not tested this theme in Opera...

I have the same problem using Firefox 48.0 on Fedora 23 Linux.

Are you both sure that <script> tag is properly included? I got a Hexo version of this theme and it was missing the theme's script. After adding it in, my once only-on-the-top navbar was there as I scrolled up.
If you take a look at the source of the example, you'll see the last script tag is
<script src="js/clean-blog.min.js"></script>

Testing https://blackrockdigital.github.io/startbootstrap-clean-blog/ using FreeBSD 11.0 with a cleanly installed Firefox 49.0 and no extensions, it works. You might be right, @PirtleShell. When I tested using Firefox 48.0 on Fedora 23 Linux, I did not check to ensure that scripts were loaded. Will test again when I'm back at my desktop computer.

Worked fine in Firefox 49.0 on Fedora 23 Linux when I tested now. Don't know what is different now from the last time I tested, aside from that I have updated Firefox from 48 to 49 in the meantime.

Still keeping an eye on this. With #49 I need to do some cross-browser testing to see what's going on here.

I'm running into the same issue (Safari 9.1.2). Any suggestions for working on a fix?

I guess I don't like the idea of forcing the .container-fluid for formatting reasons. I will keep this open for now and see if the upcoming Bootstrap 4.5 changes, and eventually Bootstrap 5, addresses this issue.


Refactor routes to an external file

remove enpoints from server.ts
create a routes.ts file
import it on server.ts

Hello can I work on this


Feature:Create footer [fixes #25]

Feature:Create footer [fixes #25]

Feature:Create footer [fixes #25]

Can you change  the bg color and align all elements at center?

What color do you need to give?

Like this-

No need to add so much feature which are not working.

Done !

Done !

Great work just one thing, About us, courses and contact us anchor tags are not working
They are not going to their respected section.

That you have redirect according to your wish.
On Mon, 10 Oct 2022 at 11:43 AM, Ayush Sarode @.***>
wrote:

Done !
Great work just one thing, About us, courses and contact us anchor tags
are not working
They are not going to their respected section.
—
Reply to this email directly, view it on GitHub
https://github.com/AyushSarode/LearningApp/pull/28#issuecomment-1272826910,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOY3HPBNSPVTWQNIOWHBR3WCOXXDANCNFSM6AAAAAARBADML4
.
You are receiving this because you authored the thread.Message ID:
@.***>

That you have redirect according to your wish.
…
On Mon, 10 Oct 2022 at 11:43 AM, Ayush Sarode @.> wrote: Done ! Great work just one thing, About us, courses and contact us anchor tags are not working They are not going to their respected section. — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANOY3HPBNSPVTWQNIOWHBR3WCOXXDANCNFSM6AAAAAARBADML4 . You are receiving this because you authored the thread.Message ID: @.>

Working on it?

Here you go !

Amazing work!

Here you go !