chore(router): Transition to canary images where it makes sense

Complements deis/router#146

@krancour doesn't this depend on deis/router#146?

Waiting for merge of #146 to produce it's first canary image before I merge this.


Errors caused by breaking changes in lean4:v4.3.0-rc2

Hi Mac @tydeu,
I just noticed the changes in lean4:v4.3.0-rc2 to the directory structures. They caused a few errors in LeanDojo and LeanInfer, which I'm trying to fix. This line was
https://github.com/lean-dojo/LeanInfer/blob/dc8e2b7f4deb648733cd20f913bca812ea0ed3f0/lakefile.lean#L54
, but I changed it to
https://github.com/lean-dojo/LeanInfer/blob/b2925d5f99b35fb7b1c3ef8ad506916c4fa3fa52/lakefile.lean#L54
However, I got the following error when running lake build in a downstream package depending on lean4:v4.3.0-rc2 + LeanInfer:
error: > LEAN_PATH=./.lake/packages/std/.lake/build/lib:./.lake/packages/Qq/.lake/build/lib:./.lake/packages/aesop/.lake/build/lib:./.lake/packages/Cli/.lake/build/lib:./.lake/packages/proofwidgets/build/lib:./.lake/packages/mathlib/.lake/build/lib:./.lake/packages/LeanInfer/.lake/build/lib:./.lake/build/lib LD_LIBRARY_PATH=/home/kaiyu/local/usr/lib:/home/kaiyu/clang+llvm-13.0.1-x86_64-linux-gnu-ubuntu-18.04/lib/x86_64-unknown-linux-gnu:/home/kaiyu/clang+llvm-13.0.1-x86_64-linux-gnu-ubuntu-18.04/lib:/usr/local/cuda/lib64::./.lake/packages/LeanInfer/.lake/build/lib:./.lake/packages/LeanInfer/.lake/build/lib /home/kaiyu/.elan/toolchains/leanprover--lean4---v4.3.0-rc2/bin/lean --load-dynlib=./.lake/packages/LeanInfer/build/lib/libonnxruntime.so --load-dynlib=./.lake/packages/LeanInfer/build/lib/libctranslate2.so ./.lake/packages/LeanInfer/././LeanInfer/Frontend.lean -R ./.lake/packages/LeanInfer/./. -o ./.lake/packages/LeanInfer/.lake/build/lib/LeanInfer/Frontend.olean -i ./.lake/packages/LeanInfer/.lake/build/lib/LeanInfer/Frontend.ilean -c ./.lake/packages/LeanInfer/.lake/build/ir/LeanInfer/Frontend.c --load-dynlib=./.lake/packages/LeanInfer/.lake/build/lib/libleanffi.so
error: stderr:
libc++abi: terminating due to uncaught exception of type lean::exception: error loading library, ./.lake/packages/LeanInfer/build/lib/libonnxruntime.so: cannot open shared object file: No such file or directory
error: external command `/home/kaiyu/.elan/toolchains/leanprover--lean4---v4.3.0-rc2/bin/lean` exited with code 134

Presumably, the error is because s!"-L{__dir__}/build/lib" doesn't exist for lean4:v4.3.0-rc2. Depending on the Lean version, either s!"-L{__dir__}/build/lib" or s!"-L{__dir__}/.lake/build/lib" exists, but not both. Is there a way to make the project work for both lean4:v4.3.0-rc2 and older versions of Lean?
Thanks!

https://github.com/leanprover/lean4/pull/2749

@yangky11

Is there a way to make the project work for both lean4:v4.3.0-rc2 and older versions of Lean? Thanks!

One somewhat hacky way to do this is to condition the paths based on the Lean version definitions (e.g., Lean.version.major / Lean.version.specialDescr). However, it should probably be noted that Lean is currently still at the point where different versions of Lean are not presumed to be compatible, so adapting to the most recent versions is currently still consider the standard approach.
Also, hopefully, Lake will have better FFI support in the future that would elide the need to hard code the build directory at all in the configuration file.

adapting to the most recent versions is currently still considered the standard approach

That makes sense!

better FFI support in the future that would elide the need to hard code the build directory at all

Looking forward to it. Thanks!


feat: deepgram language detection

Closes https://github.com/appwrite/appwrite/issues/4469

@christyjacob4 please your add review

Thank you so much for the PR 🤩. We're adding the hacktoberfest-accepted label to ensure this PR counts towards your Hacktoberfest contributions count. With that said, please stay active on this PR to address any comments once you receive a review. Happy Hacktoberfest! 🎃

Hey there 👋
We are temporarily closing your PR as there has been no activity on it. Feel free to re-open it when you're ready to start working on it again 😇


fabric-sdk: do not add resolvers for Fabric peers

This PR updates NWO to remove from the resolvers references to Fabric peers.
The FPC integration was relaying in these resolvers. To fix this, the PR updates the FPC integration to leverage Fabric Discovery.
In addition, a flaky unit-test has been disabled.
Signed-off-by: Angelo De Caro<EMAIL_ADDRESS>

I didn't remove all resolvers. They are still needed to have some of the integration tests working.
Let's take the IOU test. Alice asks the Approver to approve. The Approver signs using a Fabric identity. Alice must check that this signature is valid, therefore Alice needs to know which key the approver will use. This key must be in Alice's resolvers.

Let's take the IOU test. Alice asks the Approver to approve. The Approver signs using a Fabric identity. Alice must check that this signature is valid, therefore Alice needs to know which key the approver will use. This key must be in Alice's resolvers.

Ok - makes sense to me.
However, in that case it's wired to look for these identities in the fabric.endpoint.resolvers section. I would expect to have this in a fabric.identity.resolvers section.

I understand your point but it is out of scope for this PR to change that configuration path.
I would prefer to dedicate a PR to the configuration restructuring accompanied by proper documentation.
Wdyt?

BTW Can't we use the org ca cert to check these identities?

what do you mean?

what do you mean?

If Alice forms a transaction and requires Bob signature, in particular, any signature from Bob's org, for the endorsement. So instead of looking up the identity of Bob, could Alice simply check the Bob's cert (attached with the endorsement) belongs to Bob org? Anyway, this seems orthogonal to this PR.

do you need any additional change then? :)

@alexandrosfilios , please, have a look ASAP. Thanks :)


Range no longer available

Hi Everyone,
as I said in the title, the sensor range is no longer available and even the others similar doesn't work anymore. Is it a known bug? (All the other sensors are normally working) Thank you in advance for the help.

Audi Q3 2023 S-Tronic Business Edition (Diesel)

Hi Everyone,
as I said in the title, the sensor range is no longer available and even the others similar doesn't work anymore. Is it a known bug? (All the other sensors are normally working) Thank you in advance for the help.

Audi Q3 2023 S-Tronic Business Edition (Diesel)

Is this still happening? It works for me, the three of them.

Sorry I don't know how to close the thread. It started working again without doing nothing thank you :)


Dependency (Platform-Folders) does not work on ARM arch

Error:  (mach-o file, but is an incompatible architecture (have (x86_64), need (arm64e))).

issue closed: https://github.com/aziontech/azion-edge-functions-vscode-extension/pull/5


bad argument

error on archchart.lua:50: bad argument #1 to 'floor' (number excepted, got nil)

Hey, so to fix this the first thing to ask is do you have mpstat installed?
If so, can you provide screenshots of the outputs of the following commands:
mpstat | awk '{if(NF>=13 && $13 ~ /[[:digit:]]/) print 100-$13}'
and
free -m | awk 'NF==7 {print $3/$2*100}'
If one of those two produces no output or errors out (aka. mpstat isn't installed), that is definitely the issue. Assuming you are using arch linux, you can install mpstat by installing the following package: sysstat. The full command is: sudo pacman -Sy sysstat.


[MINOR][DOCS] Python docs also require Pandoc

What changes were proposed in this pull request?
Clarify in the README for building docs that the Python API docs also require Pandoc, not just R.
Why are the changes needed?
Attempting to build the Python API docs without Pandoc installed will yield the following error:
reading sources... [  0%] getting_started/quickstart_connect
Notebook error:
PandocMissing in getting_started/quickstart_connect.ipynb:
Pandoc wasn't found.
Please check that pandoc is installed:
https://pandoc.org/installing.html
make: *** [html] Error 2
                    ------------------------------------------------
      Jekyll 4.3.2   Please append `--trace` to the `build` command
                     for any additional information or backtrace.
                    ------------------------------------------------
.../spark/docs/_plugins/copy_api_dirs.rb:130:in `<top (required)>': Python doc generation failed (RuntimeError)

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Via trying to build the Python docs without Pandoc.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @HyukjinKwon for this quick PR on building the Python docs.

Merged to master.


Broken with current micropython >= 1.9

Pin methods were renamed from high/low to on/off on some ports.
AttributeError: 'Pin' object has no attribute 'low'

Release 1.9

I correct:

replace deprecated Pin.high()/low() methods with .call(1/0)

I included a fix to that (amongst a few others) for the 2in9b e-paper display in https://github.com/chevdor/eink


Software or tool used for the firmware

Hi,
I saw got Lepton 3 working on ESP32. How did you program the code into the ESP32? Was it a Linux system? Can you give some information on that. I'd appreciate that.
Also, what is the max frame rate you could get from this firmware model?
Thanks,
Akshay

This project uses the ESP-IDF toolchain to build & flash onto ESP32 hardware, so that'd be a good place to start =)
As for maximum framerate - really difficult to say I'm afraid. I expect it achieves close to if not above the 9Hz update rate of the Lepton though.

Damo


fixes https://github.com/AntreasAntoniou/kubejobs/issues/10

I'm fixing a few other things, so let's wait to merge this

Nevermind, there was nothing else to fix 🙂 everything works in other namespaces out of the box!


Add hyperlinks from PDB-Dev website to raw data

The PDB-Dev website currently links to the mmCIF file itself (allowing visualization in ChimeraX) and the accompanying publication. However, there currently is a good deal of data in the mmCIF file which isn't visualized in ChimeraX (such as links to input scripts, raw data not in repositories, experimental data not currently handled by ChimeraX) and so isn't visible to a casual user (who isn't going to load the mmCIF file in a text editor and search for it). It would be useful to extract any such  DOIs from the mmCIF file and display them as hyperlinks on the PDB-Dev website. For example, the Nup84 entry in PDB-Dev should link to its Zenodo entry.

Thanks for pointing it out. This has been implemented.


Why are da.chunks and ds.chunks properties inconsistent?

Basically the title, but what I'm referring to is this:
In [2]: da = xr.DataArray([[0, 1], [2, 3]], name='foo').chunk(1)

In [3]: ds = da.to_dataset()

In [4]: da.chunks
Out[4]: ((1, 1), (1, 1))

In [5]: ds.chunks
Out[5]: Frozen({'dim_0': (1, 1), 'dim_1': (1, 1)})

Why does DataArray.chunks return a tuple and Dataset.chunks return a frozen dictionary?
This seems a bit silly, for a few reasons:

it means that some perfectly reasonable code might fail unnecessarily if passed a DataArray instead of a Dataset or vice versa, such as
def is_core_dim_chunked(obj, core_dim):
    return len(obj.chunks[core_dim]) > 1

which will work as intended for a dataset but raises a TypeError for a dataarray.

it breaks the pattern we use for .sizes, where
In [14]: da.sizes
Out[14]: Frozen({'dim_0': 2, 'dim_1': 2})

In [15]: ds.sizes
Out[15]: Frozen({'dim_0': 2, 'dim_1': 2})

if you want the chunks as a tuple they are always accessible via da.data.chunks, which is a more sensible place to look to find the chunks without dimension names.

It's an undocumented difference, as the docstrings for ds.chunks and da.chunks both only say
"""Block dimensions for this dataset’s data or None if it’s not a dask array."""
which doesn't tell me anything about the return type, or warn me that the return types are different.
EDIT: In fact DataArray.chunk doesn't even appear to be listed on the API docs page at all.

In our codebase this difference is mostly washed out by us using ._to_temp_dataset() all the time, and also by the way that the .chunk() method accepts both the tuple and dict form, so both of these invariants hold (but in different ways):
ds == ds.chunk(ds.chunks)
da == da.chunk(da.chunks)

I'm not sure whether making this consistent is worth the effort of a significant breaking change though :confused:
(Sort of related to https://github.com/pydata/xarray/issues/2103)

The honest answer is that I didn't think too carefully about this when originally implementing Xarray's Dask wrapper back in 2015.
DataArray.chunks forwards to chunks on Dask arrays (a tuple), but that didn't make sense for Dataset.chunks due to the lack of a dimension ordering.

The honest answer is that I didn't think too carefully about this when originally implementing Xarray's Dask wrapper back in 2015.

I guessed that might be the case!

I'm not sure whether making this consistent is worth the effort of a significant breaking change though

Still leaves this question though ^ . I made a draft PR in https://github.com/pydata/xarray/pull/5846.


Update README with comments on running in VirtualBox

This is to make sure no one else suffers the pain of #692.
Let me know if there's a better spot to put this. It might only apply to Linux or sufficiently new GCC versions or something, too; that's hard to debug.

I don't think you meant #692. I believe you meant #693.
This looks fine for now, can you add a similar note to the tutorial in its install section?
Thanks!


Find a Template for Meeting Notes and Add Notes for The First Meeting

To Do:

Come up with a suitable meeting notes template with the help of the previous year's repositories. The template should contain the 'Details' section for date, location, duration, and attendees, the 'Agenda', 'Discussion', and 'Action Item' sections.
Add the meeting notes of our first meeting to the Meeting Notes page.

You can find our first meeting notes here.


conn pool: use hostnames of endpoints as SNI values

Commit Message: conn pool: use hostnames of endpoints as SNI values
Additional Description: optional support for usage of upstream cluster endpoints' hostnames as SNI values
Risk Level: Low
Testing: integration
Docs Changes: added information about new mechanism of SNI derivation
Release Notes: https://github.com/dmitriyilin/envoy/blob/b8e8a4537e537da66925f442cd5aeb45094cc3c9/changelogs/current.yaml#L377
Platform Specific Features: N/A
Fixes #15839

I see that "Publish and verify" checks fails in other PRs as well. Is anything required from me?

Just realized that "auto_san_validation" functionality is not consistent with the new mechanism. I'll fix it.

@mattklein123 , @abeyad I've fixed SAN validation. Can you review the changes?

FYI, I'll be OOO for a couple weeks, so if this PR has API changes again that need further review, you probably want to find another API reviewer, thanks!

@mattklein123 , can you help finding a new member of API shepherds for reviewing the change? Does @envoyproxy/api-shepherds referencing work?


Issue with paket's doc process

anyone any ideas what I need to do here?

it's probably because I uninstalled VS 2019. Sigh

Reinstalling VS2019 fixed it. FML


Information to add to "flutter doctor"

Based on flutter-dev discussions, the following things might be useful to add to flutter --version, or maybe flutter --diagnostics or some such:

[ ] whether dart and dartanalyzer are on the path.
[ ] version of dart and dartanalyzer
[ ] the whole $PATH
[ ] the shell that was used to run the tool (can we find that?)
[x] dart --version output, if dart is on the path
[ ] whether adb is on the path.
[ ] adb version output, if adb is on the path
[ ] adb devices -l output
[ ] uname -a, if uname is on the path
[ ] lsb_release -a, if lsb_release is on the path
[x] version of engine downloaded by our tools

We should add this to flutter doctor instead.

Turns out flutter_tools tests fail if the dart in your path is not the one from flutter (or is older than 1.16.0).

Yeah, it would be really useful to be able to tell if the dart that's on the path is the same as the dart that's used by flutter.

For external devs using both AngularDart and Flutter, I can easily see them having a dart in path which is not the one inside the Flutter SDK. Do we now want to support that?

Do we now want to support that?

Yes.  Flutter should be hermetic about its use of the Dart SDK.
We mostly are hermitic.  The flutter_tools tests are not hermetic, apparently.  We should fix that, but it's not a huge deal because end-developers don't run flutter_tools tests.

... external devs ...

One more thing: there's no such thing as an "external" dev.  There are just developers, our beloved customers.

We're going to close this and add these on a case by case basis when we find we need them.


Submission portal- soil template- soil types

soil_taxonomic/local classification method
soil_taxonomic/local classification
soil_type
soil type method
soil_taxonomic/FAO classification
link to classification information
These slots are very similar. We should discuss these slots and provide clearer separation between the types and better guidance on how to use / identify
Resolution

[ ] Provide Montana an export from NCBI of metadata records that included this field and how they wrote it (@turbomam )
[ ] Evaluate usage of these slots across database and determine if all are being used / how (Montana)
[ ] examples and guidance are added to slot usage (Montana)
[ ] Implement these changes to NMDC submission portal (Mark & Kitware

fao_class
local_class
local_class_meth

from

Environmental package
agriculture
soil

Structured comment name
local_class
local_class

Package item
soil_taxonomic/local classification
soil_taxonomic/local classification

Definition
Soil classification based on local soil classification system
Soil classification based on local soil classification system

Expected value
local classification name
local classification name

Value syntax
{text}
{text}

Example

Requirement
C
X

Preferred unit

Occurrence
1
1

MIXS ID
MIXS:0000330
MIXS:0000330

value
count

not collected
432

not applicable
415

3% humus, 22 % clay, 38 % silt
324

clayish
293

Freeon silt loam
264

Wahiawa
253

Medial-skeletal, amorphic, mesic Humic Haploxerand
243

Waialua
232

sandy loam, 3.5 % humus
216

sandy loam
204

Coarse-loamy, mixed, superactive, mesic Humic Dystroxerept
200

Rego Black Chernozem
192

2% humus, 21 % clay, 32 % silt
180

Loamy-skeletal, mixed, superactive, mesic Typic Haploxerept
177

silty clay loam
166

dark brown forest soil
162

NA
137

KaC
135

OsD
135

Rendzina (RR)
120

histosol
105

Orthic Humo-Ferric Podzol
99

Flanagan silt loam
96

Bloomfield
90

Brown coniferous forest soil
67

missing
65

Typic Argiudoll
54

Typic Argiudoll, with a silty clay texture
47

Typic Dystrudepts
45

Fluvaquentic humaquept
36

Sandy loam
30

Entic Haplustoll
27

Argic Pelludert
27

Aquic Glossudalfs
23

Histic Pergelic Cryaquepts
23

Mesic Ultic Haploxeralfs
23

Brunisolic Gray Luvisol
21

Orthic Dystric Brunisol
21

Rudisol
20

na
18

candler fine sand
17

Sterling-Sheep Creek-Richmond-Foxol-Elzinga-Agassiz (s7785)
16

loess chernozem over limestone
16

Dermosol
15

Brown Andosol
14

Histic pergelic cryaquept
12

Nielsen-Dranyon-Dra (s2168)
12

Latossolo vermelho
12

Lithocalcic Calcarosol
12

Clay loam to silty clay loam over clay with flints
12

Gravelly Vitrisol
11

taylorsflat loam
8

Typic cryorthent
6

Rock outcrop-Henefer-Harkers-Gappmayer (s7849)
6

Rock outcrop-Mower-Lundy-Lizzant-Hamtah-Agassiz (s8168)
6

Travessilla-Rock outcrop-Midfork family (s7972)
6

Stafford loamy fine sand
6

Steed-Redola-Provo-Pleasant View-Pleasant Vale-Keigley (s7862)
6

Yeates Hollow-St marys-Moweba-Hoskin-Holmes (s7833)
6

Vertosol
5

aeolian sediment
5

Calcarosols
4

Calcarosol
4

Roundy-Fitzgerald-Daybell (s7884)
3

Yeates Hollow-Lucky Star-Hoskin-Horrocks-Gappmayer-Cloud Rim-Bradshaw-Ant Flat (s7886)
3

Lithic Udorthents
2

Vertosol (grey)
2

Tenosols
2

Paleudult
2

Paleudalf
2

db.getCollection("biosample_set").find( { local_class : { $exists : true } } );

0

Environmental package
agriculture
soil

Structured comment name
local_class_meth
local_class_meth

Package item
soil_taxonomic/local classification method
soil_taxonomic/local classification method

Definition
Reference or method used in determining the local soil classification
Reference or method used in determining the local soil classification

Expected value
PMID,DOI or url
PMID,DOI or url

Value syntax
{PMID|DOI|URL}
{PMID}|{DOI}|{URL}

Example

Requirement
C
X

Preferred unit

Occurrence
1
1

MIXS ID
MIXS:0000331
MIXS:0000331

value
count

USDA Soil Survey Taxonomy (2003)
620

Swiss Federal Research Stations FAL RAC FAW, 1996. Swiss Reference Methods of the Federal Agricultural Research Stations. Soil and Substrate Research for the Fertilizer Advisory Service (Arable, Fodder, Fruit Farming, Viniculture and Horticulture), vol. 1. Swiss Federal Research Stations.
504

not collected
432

not applicable
415

SoilWeb
270

USDA soil classification
264

VDLUFA Methodenbuch, D 2.1, ISO 10694:1995
216

http://soils.usda.gov/technical/classification/taxonomy
214

NA
137

Bodenkundliche Kartieranleitung (Ad-hoc-Arbeitsgruppe Boden der Staatlichen Geologischen Dienste und der Bundesanstalt für Geowissenschaften und Rohstoffe)
120

INTA soil map (http://geointa.inta.gov.ar/visor/?p=model_suelos)
108

NRCS
96

missing
65

Australian Soil Classification
30

na
19

World Reference Base for Soil Resources (WRB)
16

Isbell, 2002, The Australian Soil Classification, revised edn (CSIRO Publishing: Melbourne)
15

EMBRAPA
12

Isbell, R.F. 2002 The Australian Soil Classification. Melbourne, CSIRO Publishing.
12

websoilsurvey.sc.egov.usda.gov/App/WebSoilSurvey.aspx
6

Santos, H.G., Jacomine, P.K.T., Anjos, L.H.C. dos, Oliveira, V. ., Lumbreras, J.F., Coelho, M.R., Almeida, J.A., Cunha, T.J.F., Oliveira, J.B., 2014. Sistema brasileiro de classifica o de solos, 4th ed. Embrapa, Bras lia, DF.
6

Argiudol typic/USDA Soil Taxonomy
5

Argiudol vertic/USDA Soil Taxonomy
4

Haplustol entic/USDA Soil Taxonomy
4

db.getCollection("biosample_set").find( { local_class_meth : { $exists : true } } );

0

Environmental package
agriculture
food-farm environment
soil

Structured comment name
soil_type
soil_type
soil_type

Package item
soil type
soil type
soil type

Definition
Soil series name or other lower-level classification
Description of the soil type or classification. This field accepts terms under soil (http://purl.obolibrary.org/obo/ENVO_00001998).  Multiple terms can be separated by pipes.
Description of the soil type or classification. This field accepts terms under soil (http://purl.obolibrary.org/obo/ENVO_00001998).  Multiple terms can be separated by pipes.

Expected value
soil type name
ENVO_00001998
ENVO_00001998

Value syntax
{text}
{termLabel} {[termID]}
{termLabel} {[termID]}

Example

plinthosol [ENVO:00002250]
plinthosol [ENVO:00002250]

Requirement
M
X
X

Preferred unit

Occurrence
1
m
1

MIXS ID
MIXS:0000332
MIXS:0000332
MIXS:0000332

value
count

Cambisol
1815

pine_forest
1632

Luvisol
1281

M21
1266

fine sandy loam
733

silt loam (2-4% slopes; fine-silty, mixed, superactive, mesic mollic oxyaquic hapludalf)
708

Inceptisol
636

not applicable
609

Pond Creek fine sandy loam (Pachic Argiustoll)
530

loam
466

not collected
437

Crop
390

NA
385

Rozetta silt loam
336

forest
319

50:50 mixture of steam-sterilized native soil and Metro-Mix 200 growing media
314

Agricultural Mollisol from a Fallow Casssava Field
312

Rhizosphere
309

Thrice Heat Steriled River Sand
306

Bulk
296

sandy loam
291

bulk
282

desert
270

grassland
266

Freeon silt loam
264

Rendzic Leptosol and Chromic Cambisol
256

arable sandy soil
254

SoilB
248

SoilA
245

Andesite
243

Strip
240

away
234

alfisol
227

Luvisol WRB
222

Orthic Black Chernozem
222

Pecatonica silt loam
216

Udalfs
214

alluvial sandy soil
213

Coarse-loamy.mixed.active.mesic_Typic_Dystrudepts
211

Eluviated dystric brunisol
210

Granite
200

Missing: Not provided
190

rhizosphere
189

Sandy
185

Haplic Phaeozem
184

Basalt
177

fine mixed thermic Cumulic Haplustoll
176

Xerolls
175

American ginseng continuous cropping obstacle soil
174

control
172

Arensols and Luvisols
170

canna coco
170

SoilC
168

-
168

SoilD
168

Albi-Boric Argosols
162

Coarse-loamy_over_sandy_or_sandy-skeletal.mixed.active.mesic_Typic_Dystrudepts
161

sandy soil
160

Eutric Fluvisol
159

Chernozem
156

promix
150

home
139

Not applicable
136

Hoytville silty clay loam
133

bulk soil
132

Kokomo silty clay loam
132

unfamiliar
131

10% field soil inoculum
124

Rendzina (RR)
120

sandy clay loam
120

Sand
119

Alluvial
110

Haplic Kastanozem
108

water
108

missing
101

familiar
97

Greyzemic Phaeozem Albic
97

Cultivated soil
96

Fallow soil
96

loam Acrisol
96

Loring B2 series
96

clay Acrisols
95

Lush serpentine
94

rhizosphere soil
92

Maury silt loam
90

Harsh serpentine
86

Non-serpentine
84

Ultisol
81

Mollisol
81

Orthic Humic Gleysol
80

phaeozems
80

histosol
78

sandy silty clay
78

clay
74

Rich Lake
73

loam Acrisol with long periods of stagnating water
72

Silty Clay Loam
72

Typic Ustivitrands
72

Ultic Hapludalf/Typic Fragiudult
72

saline-alkali soil
70

loamy sand
69

Brown Forest soil
68

Bori-Udic Cambosols
67

Typic Mesisol
65

loess chernozem over limestone
64

Regosol
63

Fort Collins loam
61

Mollisols
60

O
60

Hyposodic Vertisol
60

Chromic Luvisol
60

Interface
60

Luvic-Phaeozem
60

Loamy Sand
60

Residual
57

Gleyic-Fluvisol
56

SG
56

Typic Argiudoll
54

saneli silty clay loam
54

cambisol
53

FF
52

Soddy podzolic
52

black earth
52

Arenic-Luvisol
52

Mor
51

Bulk_soil
49

Leptosol
49

Submerged_zone
48

cultivated soil
48

agricultural
48

corn
48

RV
48

nitisol
48

Top_sediment
48

clay acrisol
48

coarse loamy inceptisol
48

switchgrass
48

Shady
47

loam acrisol
47

luvisol
46

Dystric cambisol
45

Clay
44

D
40

L
40

red_soil (south of China)
40

soil_type not involve
40

black_soil (north of China)
40

Nonserp
40

Silty_Clay_Loam
39

S+NSmic
39

Sandy_Loam
38

Brownzems raw-humic illuvial-humic
38

calcareous ?uvo-aquic soil
37

Sodosol
37

1
37

Mountain-meadow soddy
36

Rice Soil
36

Serp
36

Manure
36

Loamy
36

Forest Soil
36

NS+Smic
36

Rich
35

Poor
35

silty clay
35

Silt
35

Stagnosol
34

Xeralfs
34

Gray Brown Luvisol
33

Eutric Fluvisols
33

Cancienne silt loam
32

Leaf litter residuum
32

mycobiome
32

Canton
30

Mesic Typic Argiudoll
30

Sandy loam
29

Calcisol
28

stony silty clay loam
28

Loessal Soil
28

silty clay loam
28

Eum-Orthic Anthrosols
28

Albic Luvisol
28

calcareous fluvo-aquic soil
27

Mor-moder
27

cambsiol
27

Captured Dust
27

Argic Pelludert
27

Gypsum
27

Sandy_loam
27

Bulk Soil
27

Elstow orthic dark brown loam
27

Silty Loam
27

sand
27

Entic Haplustoll
27

Vertisol
24

Limnic Humisol
24

Silt loam
24

Acrisol
24

Mollic Psammaquent
24

continuous cropping soil
24

Haplic Planosol
24

rotational cropping soil
24

Cast
24

Rhizo
24

Orthents
23

pristine peat soil
23

clayey
23

soil sample
23

Silty
23

Medium Soil
21

silt
21

Andosol
21

Alluvials saturated
21

"CA"
21

N/A
20

black soil
20

Cutanic Luvisol developed from glacial till
20

Gray lowland soil
20

"CL"
19

Loam
19

3
19

mollisol
19

sandy clay
19

Mountain-meadow sod-peaty
19

na
18

Black soil
18

Podzol soil
18

Rich Soil
18

A
18

clayey sand
18

G
18

S
18

Sediment
18

Orthic Gray Luvisol
17

mineral soil
17

inceptisol
17

Groundwater sediment
17

Soil fertilised with sludge
17

Soil fertilised with slurry
16

Macdonald
16

monomicrobial soil
16

Soil fertilised with mineral
16

Stages of soiling
16

mixed microbial soil
16

Organic
16

control (sterilized) soil
16

Leptosol /Sand
16

Soil fertilised with usw
16

oxisol
16

BNC
15

BRR
15

CAG
15

Poor Soil
15

BPP
15

Gloucester
15

Loess
15

BB
15

CCS
15

6
14

Chernozems leached mycelial-calcareou
14

Broun Forest soil
14

Xerepts
14

podzol
13

aridisol
13

Leptosol Umbric Petrocalcic Gleyic/Sand
12

unplanted soil
12

drained peat soil
12

typical Clay loamy Fe-leachic-gleyic-stagnic anthrosol
12

Rhizosphere soil of watermelon planted in forest soil
12

Rhizosphere soil of watermelon planted in rice soil
12

Leptosol Umbric Calcaric /Sand
12

Karshner
12

acid red
12

Without pathogens
12

Standard soil Lufa 2.3
12

Rhizosphere soil of cucumber planted in forest soil
12

Soil of apple orchard
12

basalt of volcanic origin
12

sandy-loam from silicate substrate
12

stony clay loam
12

stony silty clay
12

Rhinebeck silt loam
12

Leptosol Umbric Calcaric Nudilithic/Sand
12

Rhizosphere soil of cucumber planted in rice soil
12

Leptosol Umbric Calcaric Gleyic/Sand
12

4
11

Alluvials compact
11

2
11

Orthic Gleysol
11

Fill
10

5
10

Root soil interface
10

Bastsil
10

Upper Scarp Complex
9

NS+Smic+Ni
9

Marine
9

Fernwood (Arenosol)
9

Ferric-Udic Cambisols
9

Griffin (Gleyic Acrisol)
9

Typic Hapludands
9

"ST"
9

Bekenu
9

Merit
9

NS+Smic+Drought
9

Histic Epiaquands
9

Leptosol/Sand
8

Pinedene (Helvic Acrisol)
8

silt loam
8

Clay loam
8

Clay loamy endogleyic-Fe-leachic-stagnic anthrosol
8

Nyalau
8

potting soil
8

moraine
8

Humults
8

Phaeozem Luvic/Loam
8

Organic Soil
8

Peat
7

Rendzina
6

Aquepts
6

Rhizosphere soil of celery planted in rice soil
6

Rhizosphere soil of celery planted in forest soil
6

Poor Lake
6

not collection
6

with F.oxysporum
6

sod podzol
6

Original rice soil
6

Saprists
6

Argids
6

red earth
6

PLcomparison
6

Bath
6

Original forest soil
6

Hudson silt loam
6

Ferric-Ustic Luvisols
6

Podzol
6

Stafford loamy fine sand
6

Houston
6

Olnes
6

sandy
5

furrow soil of potato plant with low common scab severity level
5

silty loam
5

geocaulosphere soil of potato plant with high common scab severity level
5

rhizosphere soil of potato plant with low common scab severity level
5

Anthroposol
5

ultisol
5

andisol
5

Nixon Sandy Loam
5

Aquents
5

rhizosphere soil of potato plant with high common scab severity level
5

root-zone soil of potato plant with high common scab severity level
5

root-zone soil of potato plant with low common scab severity level
5

geocaulosphere soil of potato plant with low common scab severity level
5

Williamson
5

Water
4

Mesic Organic Cryosol
4

eutric endostagnic cambisol
4

n/a
4

gelisol
4

furrow soil of potato plant with high common scab severity level
4

Portneuf silt loam
4

Sandy Loam
4

entisol
4

Albeluvisol
4

gleyed slightly humic
4

Leptosol/ Sand
4

Lordstown
4

Langford
4

deep sandy loam (top soil) 30cm, med-heavy clay (80-100cm)
3

Typic Torriorthent
3

granite
3

Pe+LTNDT N1K1 Field
3

Clay Loam- Clacium Carbonate
3

Typic Vitrandept
3

Pe+LTNDT M1P1 Field
3

LTNDT M1P1 Field
3

Pe+LTNDT N1P2K2 Field
3

Loam over clay over limestone
3

High sand sandy loam over yellow/red clay
3

Loam over clay
3

Loam over red clay
3

Deep Friable Gradational clay loam
3

M
3

Hapludox
3

Entic Cryandept
3

Pe+LTNDT N2P2K2 Lab
3

Bubbly loam
3

Thick sand over clay
3

LTNDT M1P1 Lab
3

Dystric Xerocrept
3

Initial soil, with no fertilization nor chemical nor organic
3

Sandy loam over yellow Pudsolic clay
3

Clay Loam over red clay
3

None
3

Red/brown earth - stone fragments -strong clay over shift
3

Typic Haplohumult
3

alluvium
3

LTNDT N1K1 Field
3

healthy soil
3

LTNDT N1P2K2 Field
3

Meadow dirt- high organic carbon content
3

Red brown earth over red clay
3

Sand over red clay
3

Erie
3

Pe+LTNDT M1P1 Lab
3

Dry soil
3

LTNDT N2P2K2 Lab
3

water control
3

Shallow top soil- red clay/Limestone
3

clay loam over red clay with various calcium carbonate layers
3

Sandy loam over blocky clay
3

Red/Brown earth
3

Sand over yellow/orange clay
3

Sandy alluvial
3

agricultural soil
2

tar sand
2

desert gypsum
2

Mixed Waste Organic Output
2

pine forest
2

Lts
2

Volusia
2

blank
2

spodosol
2

Harper series, thermic Lithic Haplustolls, Mollisol
2

Ornithic Leptosol
2

Kendaia
2

Eckert series, thermic Lithic Haplustolls, Mollisol
2

tundra soil
2

Gray Solodized Solonetz
2

Biochar
2

Real series, thermic Typic Calciustolls, Mollisol
2

db.getCollection("biosample_set").find( { soil_type : { $exists : true } } );

0

Environmental package
agriculture
food-farm environment
soil

Structured comment name
soil_type_meth
soil_type_meth
soil_type_meth

Package item
soil type method
soil type method
soil type method

Definition
Reference or method used in determining soil series name or other lower-level classification
Reference or method used in determining soil series name or other lower-level classification.
Reference or method used in determining soil series name or other lower-level classification

Expected value
PMID,DOI or url
PMID,DOI or url
PMID,DOI or url

Value syntax
{PMID|DOI|URL}
{PMID}|{DOI}|{URL}
{PMID}|{DOI}|{URL}

Example

Frederick series; Weikert series

Requirement
M
X
X

Preferred unit

Occurrence
1
1
1

MIXS ID
MIXS:0000334
MIXS:0000334
MIXS:0000334

value
count

Gray
708

parent material
620

USDA taxonomy
555

not applicable
536

not collected
438

NA
373

WRB
353

Canadian System of Soil Classification
290

USDA soil classification
264

USDA Soil Taxonomy system
254

According to soil characteristics
174

FAO 1998
170

-
168

Bodenkundliche Kartieranleitung (Ad-hoc-Arbeitsgruppe Boden der Staatlichen Geologischen Dienste und der Bundesanstalt für Geowissenschaften und Rohstoffe)
120

Webster_silty_clay_loam
120

INTA soil map (http://geointa.inta.gov.ar/visor/?p=model_suelos)
108

missing
101

USDA soil taxonomy
73

World Reference Base system
72

IUSS
72

Web Soil Survey, USDA
61

World Reference Base System
61

USDA
49

soil_type_meth not involve
40

US Taxonomy
33

The Canadian System of Soil Classification, 3rd edition
33

Web of soil survey
32

FAO-WRB
28

more contaminated
27

less contaminated
27

Method described by FAO (2014)
26

Community_P
24

Community_U
24

sand
18

na
18

World Reference Base for Soil Resources (WRB)
16

USDA web soil survey and soil taxonomy
16

Sedimentation
14

Organic Soil
8

NRCS Soil Survey Manual
7

websoilsurvey.sc.egov.usda.gov/App/WebSoilSurvey.aspx
6

Köhn, M. (1929). Korngrößenbestimmung mittels Pipettanalyse. Tonindustrie-Zeitung, 55:729–731. and Ad-Hoc-AG Boden (2005). Bodenkundliche Kartieranleitung 5 (KA5). Schweizerbart’sche Verlagsbuchhandlung, Stuttgart, 5 edition.
5

db.getCollection("biosample_set").find( { soil_type_meth : { $exists : true } } );

0

Adding to current sprint per Mark. Need feedback from @mslarae13

@turbomam is it possible to export these in an excel file so I can look at them side by side?

@mslarae13 you can copy markdown tables from GH issues and paste into Excel and they will look pretty good.
If I need to create some new tables for you, what is it that you want to see side by side?

Thanks Mark!
I didn't realize this would copy-paste so well.
"Soil taxonomy is a hierarchical soil classification system with six categories, or levels: order, suborder, great group, subgroup, family, and series. Soil taxonomy is a morphogenetic soil classification system using diagnostic horizons and features to infer pathways of soil genesis and formation." - From this paper
Looking at these slots and what people have submitted, here's my conclusions.
1: FAO class is very specific. This should be an enumeration.
2: local_class is the classification.

Appears to be in progress based on recent comments. Moving to new sprint.

No update this sprint. Removing from sprint. Backlog label was already added 2 weeks ago. Blocked on SubPort board.

Requirements to unblock:

From this comment, link_class_info should be gone, but I still see it in the documentation.

Confirm, is it gone?
Deprecate it from NMDC documention

Should we remove local_class
Unclear from MIxS how local_class and soil_type are supposed to be different.


Update Composer dependencies (2021-10-13-00-03)

Visual regression test passed!
View the visual regression test report


Consider adding matrix of prisma version x db version compatibility

It would be helpful to have a matrix which demonstrates the compatibility of Prisma versions with Databases.
This can also be extended to demonstrate preview features timeline, this would help users in visualising the prisma versions from which the feature was in early access and from which version it went into GA.

👋 Hi there,
We're reviewing and tidying up our backlog to focus on the most relevant and impactful issues. After careful consideration, we're closing issues that haven't had any recent activity or align with our current priorities.
If you believe this issue is still important or unresolved, you're welcome to reopen it or create a new one with updated details. Your feedback is always valued and we're here to help ensure our docs continue to improve.
Thank you for your understand and contributions!


netty指标

Expected behavior 可否新增一个配置开关，启用等于暴露所有metric，默认关闭
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
JVM version (e.g. java -version)
OS version (e.g. uname -a)

Netty does not know which metrics people want to expose and how. Netty is also a library split across multiple modules, so people can pick and choose their features. So I don't think it's feasible to just "expose all metrics".


Support for External Agent connection using Ingress.

Version - 2.0.0-Beta1
LitmusCTL connection we can provide the ingress IP, During the registration, it would still use NodePort for subscriber communication.

Closing in favor of https://github.com/litmuschaos/litmus/pull/2598


Fix bug where errors are only shown for hidden forms.

Fixes #262

This is not a bug. Field errors for hidden fields are shown as part of the form errors. Fields that are visible display their own errors.

Non-field errors include also the validation errors thrown by (custom) clean() implementations. They have nothing to do with hidden fields?


Could you do a version that is like the current default one, but dark gray (see Photoshop for reference)?

I will continue fix details for the Arc themes.
The theme editor in godot is not good enough to make a theme to suit all DPIs

Is this one ok?

Nope, I was hoping for one that is the same as current official, just desaturated to darkish grey (keeping all the shading and fonts).
This one was close, still has a bit of the purple color in it though: https://dl.dropboxusercontent.com/s/ky2spr2087h7ima/shot_161218_164529.png
It one replaced the current one for a while in the repository, but sadly it was reverted.


 I currently use DigitalOcean, with Jekyll building on git commit/push.
I thought I'd start a bit of a discussion and discovery to whats needed to get Pretzel working on mono.
So far, to get it building

Mono doesn't have nuget support? Or nuget is built to a not nuget profile, I'm not sure, removing the nuget task from the csproj makes it build as all the references were there as I'd previously built on .NET. Apparently nuget does have mono support, so perhaps the nuget.exe in the repo is out of date?

It doesn't have to be removed, but the ILMerging does not work. This can be left to 'error' out or removed from the csproj. IL-Repack or Fody.Costura might be options.

Because the ILMerging doesn't work, the MEF stuff doesn't work.
Specifically,   var first = new AssemblyCatalog(Assembly.GetExecutingAssembly()); would need to be changed to
  AggregateCatalog first = new AggregateCatalog();
  first.Catalogs.Add(new AssemblyCatalog(Assembly.GetExecutingAssembly()));
  first.Catalogs.Add(new AssemblyCatalog(Assembly.GetAssembly(typeof (SanityCheck))));

Ideally some sort of ILMerging that works with mono would be best
Fixed
Todo

[x] Confirm working on *Nix
[ ] ILMerging/equiv for single exe
[x] Nuget all the things.
[x] fixing paths - baking (and thus serving up via taste) fail pretty epically

Its actually NuGet.Targets, in this case, that was the issue. LogStandardErrorAsError was throwing an error, removed that from the Exec statements in NuGet.Targets, and it works again.

Trying to find the root cause, but mono doesn't seem to be picking up @(MainAssembly), which makes ILRepack fail.
This means instead of
 /out:bin\Debug\Pretzel.exe "obj\x86\Debug\Pretzel.exe" <list of assemblies to merge>

It gets
/out: "obj\x86\Debug\Pretzel.exe"   <list of assemblies to merge>

Changing it from @(MainAssembly) to $(OutputPath)$(AssemblyName).$(OutputType) with ILRepack is not overly elegant, but works with both mono and .net

There is/will be issues with various file system access where slashes are involve. ie fileSystem.File.WriteAllText(Path.Combine(directory, @"_layouts\layout.cshtml"), Properties.RazorWiki.Layout); uses the 'wrong way' slash for *nix.
It should be something like (Path.Combine(directory, "_layouts", "layout.cshtml"). This is going to be more of an issue with creating new site/templates/etc than general operation, I think.

Build issues on linux:

case sensitivity in various paths relating to nuget. ie, needs to be NuGet.exe
Permission errors on restoring, +777 (I know this is bad?) to the whole source folder let me restore files
Resources (ResX) work funny and are currently failing

As of fb35bacee31d82cdb3361193639e3d47323b81d4 it compiles and embeds on Ubuntu, but it does not work as it cannot find NDesk (Could not load file or assembly 'NDesk.Options ...'

Nice work and writeup @vikingcode!

Alright, there is an issue with embedding via IL-Repack, which I'm trying to figure out. It has nothing to do with NDesk - if I drop NDesks file in, it'll then move onto another DLL, and so on and so forth until they're all present.
Based on the filesize alone, Pretzel.exe does contain everything, but it's not finding it properly.

Without VS for Linux, it's much harder to debug this, but paths are wonky which in turn is causing most of the issues once its actually running (if I disable the embedding/use the MEF work around).
Pretzel looks fairly different from when I last contributed to it in any sort of significant way so it's taking me awhile to figure out where this could be coming from. I suspect most, if not all, file operations will need to be rejiggered because of paths. However, I should point out that its rendering HTML fine out of the box.

I suspect most, if not all, file operations will need to be rejiggered because of paths.

That wouldn't surprise me either :cry:

Excellent work! :smiley:

So this is where my branch is up to:
It works on mono/ubuntu, including taste (web server) given the following constraints

MonoDevelop hates me and only half works
CHMOD +777 for nuget folder at a minimum
May need sudo to get around file permissions when generating the site
Can't get it do properly ILMerge/ILRepack, which requires the modified code in program.cs in the first post

The last point is probably the one main issue with getting it merged in/before I send a pull request. Alternatively we could possibly do some shenanigans where it tests whether its a single exe (Windows) or multiple (Linux) yet still works. While a single exe is preferable, working at all on Linux is kinda better than nothing.

The changes to nuget (ie, dropping Targets) made this much easier. The problem I have now is basically mono itself, be it on Windows or Linux.
I can embed all the assemblies into Pretzel.exe like we are now using xbuild or msbuild, and on .NET it'll run fine (no matter what compiles it), but on the mono runtime it can't "unpack" the assemblies for lack of a better word. It simply can't find the other assemblies.
I get errors like
Unhandled Exception:
System.IO.FileNotFoundException: Could not load file or assembly 'NDesk.Options, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
File name: 'NDesk.Options, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null

[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not load file or assembly 'NDesk.Options, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
File name: 'NDesk.Options, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null

MonoDevelop crashes when I attach a debugger on Ubuntu, and Xamarin Studio can't even clean the directory, let alone compile (!), so I'm not able to get any further with debugging it. Building via CLI is the only way to go.
Any suggestions?

Taking a quick look with dotPeek to the assemly compiled from your branch and the official branch it can be confirmed, that mono may indeed be right: the assemby is not merged properly, or at least not the same way as in the official one.
Also note: commenting a reference to LockFile in the Pretzel.Tests csproj file was needed to be able to build your branch. Please confirm by trying to build a clean checkout.
 I have commented it on the changeset in your branch. Please consider reviewing those parts.

assemby is not merged properly, or at least not the same way as in the official one.

Thats pretty much what I've been saying for the last few posts. The same code compiles on xbuild and msbuild, but on xbuild it doesn't embed or extract the other assemblies properly. Doesn't matter if its Windows or Linux, xbuild (mono) is the one causing problems, so I largely gave up on it as I don't know enough about IL merging on mono to figure it out.

Also note: commenting a reference to LockFile in the Pretzel.Tests csproj file was needed to be able to build your branch. Please confirm by trying to build a clean checkout.

Given LockFiles an exe, I have pretty much no confidence of getting that to work on linux. Tests are irrelevant until the above point is addressed - one issue at a time.

LockFiles doesn't work on Linux but have been ditched so it's not a problem.


Add Github workflow for deployment preview

Current Behavior
Currently, we don't have any GitHub workflow defined for deployment preview of Sistent site.
Check this PR -> https://github.com/layer5io/sistent/pull/182
Desired Behavior
-> Add  GitHub workflow for deployment preview.
Implementation

Acceptance Tests

Mockups

Contributor Guide

🎨 Wireframes and designs for Layer5 site in Figma (open invite)

// @leecalcote

I think @coder12git we need to add the workflow inside your  branch or otherwise we will having conflicts

I think @coder12git we need to add the workflow inside your branch or otherwise we will having conflicts

Okay, but is it possible to make an another branch in sistent dedicated for site? In this way we can merge my PR into that branch and then can do changes there.


rpm post install script can't be run during kickstart/pxe install

all of the influxdb, telegraf, kapacitor has the same post install scripts and all of them fail during pxe/kickstart install.
unfortunately the spec file for building rpm are not public even though the whole source and open source. it'd be very useful if you can add the rpm's spec files to the source since in this case anyone can test it, debug it and fix it.
currently on a running RHEL/Fedora system if you install influxdb...rpm it's working properly, but unfortunately if it's installed during a kickstart/pxe install part of the operation system it's not working. unfortunately i'm not able to identify the bug itself (until someone share the spec file with me).
imho the bug somewhere the sjell incompatibility. since the postinstall script run by /bin/sh while it's first line show :
#!/bin/bash
and when it's try to determine which distro it's running:
if [[ -f /etc/redhat-release ]]; then
    # RHEL-variant logic
    if command -v systemctl &>/dev/null; then
        install_systemd
    else
        # Assuming sysv
        install_init
        install_chkconfig
    fi

it seems that even on a rhel/centos-7 system it's call install_init instead of install_systemd.
if someone share the spec file with me i can test/debug it and send the fix for it.

thanks @lfarkas!
I checked internally and we are using FPM to build them, which doesn’t involve spec files. Maybe @mark-rushakoff can explain in a little more detail.

It's been a very long time since I've touched FPM for this kind of thing, but you can take a look at https://github.com/influxdata/influxdb/tree/master-1.x/releng/packages, and in particular https://github.com/influxdata/influxdb/blob/master-1.x/releng/packages/fs/usr/local/bin/influxdb_packages.bash, for how we compose the packages with FPM.
Fixes would be especially welcome if you could update the test for the packages too: https://github.com/influxdata/influxdb/blob/master-1.x/releng/packages/spec/clean_install/run.bash

Hi! I maintain fpm. Is this still an issue for y'all? Maybe we can work together to figure out how to make it work.


Refactor mapvote details menu

Draw the map details with an actual menu item using ownerdraw
Details panel now updates as you select a new map in the list, instead of requiring a new click on details button
Fix levelshot aspect ratio, was 1:1 when it should be 4:3
Add text scroll to map briefing if text doesn't fit, also used in Host Game menu

https://streamable.com/dutgcu

The text now fades out when going out of bounds, instead of harshly disappearing https://streamable.com/qq9ynu


unable to import flash_attn_cuda

I found I was unable to import flash_attn_cuda after running python setup.py install.
--- details ---

I run python setup.py install with a prefix pointing to the root dir of flash-attention.
I set PYTHONPATH=$PWD also with the absolute path of the root dir of flash-attention.

Any suggestions / comments would be greatly appreciated. Thanks a lot for your time!
ERROR MESSAGE:
yujia.zhai@docker-n148-083-133:~/flash-attention$ PYTHONPATH=/data00/home/yujia.zhai/flash-attention python3 benchmarks/benchmark_flash_attention.py
Traceback (most recent call last):
  File "benchmarks/benchmark_flash_attention.py", line 11, in <module>
    from flash_attn_interface import flash_attn_func
  File "/data00/home/yujia.zhai/flash-attention/flash_attn_interface.py", line 5, in <module>
    import flash_attn_cuda

Did the python setup.py install command finish successfully?
Compiling CUDA extension for Pytorch can be a bit tricky (e.g. sometimes the nvcc version needs to match the CUDA version that Pytorch was compiled with).
What's your nvcc version (nvcc --version) and Pytorch CUDA version (torch.version.cuda)?
I'm trying to figure out how to build wheels so that users don't have to compile the package.

Thanks for the response!

python setup.py install finished successfully.
yeah you're correct. torch.version.cuda. does not match with my nvcc --version. Let me try to sync them with the same cuda version and see what would be going on.

Thanks!

Great news! After sync the cuda versions between torch and nvcc, we've got it run.
Thank you!

ImportError: ~/.local/lib/python3.10/site-packages/flash_attn_2_cuda.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZNK3c106SymIntltEl
nvcc --version:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Mon_Apr__3_17:16:06_PDT_2023
Cuda compilation tools, release 12.1, V12.1.105
Build cuda_12.1.r12.1/compiler.32688072_0
And torch.version.cuda: 12.1
Any idea ?


Add cghlewis.com

I added my website, cghlewis.com to the blog folder.

Thank you, I'll look it! :) If you're not already part of it, would you be OK with being added to a Bluesky starter pack for R-Ladies? :)

@Cghlewis Thank you, I'll look it! :) If you're not already part of it, would you be OK with being added to a Bluesky starter pack for R-Ladies? :)

Thank you! I believe I'm already in the R-Ladies starter pack!

Ref: #97 If not already in the starter pack, please also add Crystal :)

Awesome, thanks! I tagged you (just in case) to double check and add you if you're not already in it :)


Parallelize metadata processing and reduce metadata footprint

We noticed that we were not managing the metadata most efficiently:

The _delta_log/ was read multiple times to rebuild the same data structure
We started to have issues when the metadata was too big
We were forcing a lot of computation in the Driver by executing .toLocalIterator in QueryExecution

Moving much of the computation to the Dataset API instead of using core classes (independent of Spark) should help reduce the number of tasks and improve resource usage.

This issue is to keep track of the changes on PR #335, which has grown more than expected.
We measured the performance improvement by running a Sampling query over a telemetry dataset.
spark.sql("SELECT count(*) FROM logs_tpc TABLESAMPLE( 0.1 PERCENT)").show()

With a single node:

The previous version (v0.6.0) took more than 20 seconds, and it produced all these tasks

Then I tested this PR, and it took ~6 seconds, generating only these tasks.

Fixed by #335


pycrtm Installation Error ModuleNotFoundError: No module named 'distutils.msvccompiler'

Error Description:
Recently I tried to install pycrtm on Ubuntu 22.04.4 using Python 3.10.12 and encountered the following error:
ModuleNotFoundError: No module named 'distutils.msvccompiler'

Attempted Solutions:
The following proposed solutions from here did not fix the problem:
pip3 install setuptools

and
pip3 install --upgrade setuptools

Fairly bizarre, why does it insist on ms visual c++?

Maybe force scikit-build to use something sane using --plat-build ?
https://scikit-build.readthedocs.io/en/latest/

Also maybe, try forcing it to use gcc by setting environment variables CC, CXX, and FC to gcc and gfortran?

It looks like this is because setuptools introduced a breaking change that affects pycrtm.
I found the solution here.
So, downgrading setuptools to version 61 fixed the problem for me:
pip3 install setuptools==61


[hotfix] fix deprecated method getRootCause() in assertj.

Search before asking

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

Motivation
getRootCause() is deprecated
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@zhuangchong Could you assgine to me，thanks~


An official tutorial is not working. Is it a bug?

link ：https://solidity.readthedocs.io/en/latest/solidity-by-example.html

I fill in the data  ["ABC","JPL"]
Report error：creation of Ballot errored: Error encoding arguments: Error: invalid bytes32 value (arg=undefined, type="string", value="ABC")
I'm sure the data is correct. Is this a bug? Or can developers run success

that's because we changed the param encoder library. now bytes32 requires the input to be hex value.
['0xab', '0xac'] should work

closing this one


Versioning refinements

This intended to tighten up versionability detection and plug some holes.  It's not perfect, but hopefully an iterative improvement.
The changes include addressing versionability of a type separately from versionability of an object (i.e. an instance of a type).  This was kind of blurred before: STIX objects would be checked for presence of versioning properties; dicts would be checked for support from their object type.  This presents opportunities for bugs and misleading error messages.
For example, if a custom STIX type were created whose versioning properties were optional, and you didn't provide sufficient properties on an object, you'd get an error that you "cannot create new version of object of this type".  That's actually incorrect: you can creation new versions of instances of the type, you just have to provide sufficient properties on the object.  Also, if you tried to version a dict of a versionable type, didn't provide an explicit "modified" property for the new version as a kwarg, and it was also missing from the dict, you would get a crash because code just assumed the "modified" property would be in the dict.  In the first case, versionability of the object was checked but not the type; in the second case, versionability of the type was checked, but not the object.  So both types of error are made.
There is also the question of what to do if someone tries to version a dict of an unregistered STIX type.  Without registration, we can't tell what properties the type supports, so we can't determine its versionability.  Do we allow versioning?
Behavior included with this PR:

If an object has all versioning properties, it is considered versionable.  Versionability of the type is not checked in this case.  This allows versioning properties to be added as custom properties as necessary, to enable versioning on an otherwise unversionable object.
Versionability determination of a STIX type is the same as before.  All versioning properties must be supported.
If a STIX type has not been registered and one attempts to version a dict for that type, a lax approach is taken, and the type will be considered versionable.  (This does not mean a particular instance of the type is versionable.)
Except for the first bullet item, versionability determination of an object is only done if the type has been deemed versionable.  An object of versionable type is considered versionable if it has the "created" property.  If it does not have a "modified" property, it is assumed equal to "created", and the new version will have a "modified" property added with a timestamp greater than the created property.
Exception types have been added to be clearer about why versioning fails.  You should no longer get an error saying a type is not versionable, when it is.  You should also no longer get a generic KeyError crash if a versionable instance of a versionable type does not have a "modified" property, and one was not given as a kwarg to new_version().

Possible future work: what if neither the type nor instance is considered versionable according to the above criteria, but together, the support/presence criteria are met for versionability?  E.g. type supports modified/revoked but not created, and instance has a custom "created" property but has neither "modified" nor "revoked".  The type would not be considered versionable, so versionability of the object would not even be considered.  But presence of the object's custom "created" property together with the type's support for "modified" and "revoked" put all the ingredients in place for versioning.

Codecov Report

Merging #458 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #458      +/-   ##
==========================================
+ Coverage   98.24%   98.25%   +0.01%
==========================================
  Files         142      142
  Lines       15740    15838      +98
==========================================
+ Hits        15463    15562      +99
+ Misses        277      276       -1

Impacted Files
Coverage Δ

stix2/exceptions.py
100.00% <100.00%> (ø)

stix2/test/v20/test_versioning.py
100.00% <100.00%> (ø)

stix2/test/v21/test_versioning.py
100.00% <100.00%> (ø)

stix2/versioning.py
100.00% <100.00%> (+1.02%)
: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 5a34d52...bc8fdcd. Read the comment docs.

I checked the spec (e.g. sections 3.2 and 11.2), but couldn't find anything that put an all-or-nothing requirement on the usage of versioning properties for custom STIX types.  E.g. if you use "revoked", you must also use "created" and "modified".  It does say "The revoked property is only used by STIX Objects that support versioning...".  There is similar description for "modified", but not for "created".  That implies a policy which was used by spec authors for spec-defined objects.  There is not a "must" or "should" directing creators of custom types to add the other two properties.
It would be an odd situation to have a "revoked" property on an object/type you can never revoke, because it's unversionable.  I also don't think you're allowed to use properties named the same as common properties for purposes other than what the spec describes(?).  So, odd situation but it seems like the spec allows it.
Btw, I edited the PR description (updated the behavior bullets).  I hadn't quite got the correct behavioral description... maybe that is an indication of how tricky it is to get the logic right :)

Codecov Report

Merging #458 (ac99e12) into master (03b3423) will decrease coverage by 0.16%.
The diff coverage is 92.75%.

@@            Coverage Diff             @@
##           master     #458      +/-   ##
==========================================
- Coverage   89.27%   89.11%   -0.17%
==========================================
  Files         146      146
  Lines       16032    15768     -264
==========================================
- Hits        14313    14052     -261
+ Misses       1719     1716       -3

Impacted Files
Coverage Δ

stix2/exceptions.py
58.08% <56.25%> (+0.23%)
:arrow_up:

stix2/versioning.py
82.56% <92.30%> (+1.76%)
:arrow_up:

stix2/test/v20/test_versioning.py
100.00% <100.00%> (ø)

stix2/test/v21/test_versioning.py
100.00% <100.00%> (ø)

stix2/test/v20/test_datastore_filesystem.py
99.20% <0.00%> (-0.02%)
:arrow_down:

stix2/test/v21/test_datastore_filesystem.py
99.22% <0.00%> (-0.02%)
:arrow_down:

stix2/test/v21/test_deterministic_ids.py
99.21% <0.00%> (-0.01%)
:arrow_down:

stix2/test/v20/conftest.py
100.00% <0.00%> (ø)

stix2/test/v21/conftest.py
100.00% <0.00%> (ø)

stix2/test/v20/test_tool.py
100.00% <0.00%> (ø)

... and 68 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #458 (ac99e12) into master (03b3423) will decrease coverage by 0.16%.
The diff coverage is 92.75%.

@@            Coverage Diff             @@
##           master     #458      +/-   ##
==========================================
- Coverage   89.27%   89.11%   -0.17%
==========================================
  Files         146      146
  Lines       16032    15768     -264
==========================================
- Hits        14313    14052     -261
+ Misses       1719     1716       -3

Impacted Files
Coverage Δ

stix2/exceptions.py
58.08% <56.25%> (+0.23%)
:arrow_up:

stix2/versioning.py
82.56% <92.30%> (+1.76%)
:arrow_up:

stix2/test/v20/test_versioning.py
100.00% <100.00%> (ø)

stix2/test/v21/test_versioning.py
100.00% <100.00%> (ø)

stix2/test/v20/test_datastore_filesystem.py
99.20% <0.00%> (-0.02%)
:arrow_down:

stix2/test/v21/test_datastore_filesystem.py
99.22% <0.00%> (-0.02%)
:arrow_down:

stix2/test/v21/test_deterministic_ids.py
99.21% <0.00%> (-0.01%)
:arrow_down:

stix2/test/v20/conftest.py
100.00% <0.00%> (ø)

stix2/test/v21/conftest.py
100.00% <0.00%> (ø)

stix2/test/v20/test_tool.py
100.00% <0.00%> (ø)

... and 68 more

Continue to review full report at Codecov.

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


Set max buffer size to maximum allowed

I'm evaluating this library for an application that sends ~60kb size UDP messages. Without this setting the messages are cut off at the default message size.
This is probably something you'd want to set with const socket = dgram.createSocket('udp4', { maxBufferSize: 'UINT16_MAX' }). I've modified the library to automatically choose the largest allowed size GCDAsyncUdpSocket allows (which is 64kb).

@marcusstenbeck might as well also do setMaxReceiveIPv6BufferSize?

Sure, I committed both now.
https://www.quora.com/What-is-the-maximum-size-of-a-UDP-datagram
Side note: Unfortunately I did not get the performance I needed together with the rest of my app. I'm receiving ~30kb packets containing some byte data and a jpeg image. I'm slicing that packet and then sending the image to OpenGL/WebGL. Doing the data handling natively including handling UDP was the way to go in the end.

@marcusstenbeck thanks! Will merge asap.
and yes, the RCTBridge can be a performance-killer


Refresh tokens are stored in plain text

The refresh tokens introduced in v0.2.0 are stored in plain text in the DB. In case someone gets access to them, he/she can impersonate any user on the site.
Storing a hashed version of the refresh tokens, just like it is done with passwords, would make them useless for an attacker.
Anyways, thanks for your great work on this project!

Hi  @rangermeier, thanks and sorry for the delay in my response.
Passwords should be hashed but refresh tokens do not, it irreversibly destroys data.
I think this might be the main reason why django-rest-framework or django-oauth-toolkit store API keys in clear text.
Anyway I've created a PR #57 that provides a way to implement it yourself, including a basic example using SHA256 algorithm.

Hi @mongkok you said

I think this might be the main reason why django-rest-framework or django-oauth-toolkit store API keys in clear text.

but such as i know django-oauth-toolkit also needs Client ID and Client Secret when user want to renew access token and refresh token and according to oauth2 we should  store refresh token as plain text but we have Client ID and Client Secret too.


Feature request: Upgrade Grav to a specific version using Grav Package Manager

Maybe I missed something but, at this time, it seems that the CLI bin/gpm self-upgrade is not able to use an argument for explicitly specify a definite version.
For version 1.6, the documentation only states that self-upgrade (…) allows (…) to update Grav to the latest available version.
I would like to be able to explicitly state a version and not use automatically the latest available one. Indeed, because of numerous successive recent changes, I would prefer to check plugins interoperability and themes compatibility step by step on a local installation and not directly have to deal only with the most recent release.
Would it be possible to consider in the future such an option, as it exists for Composer? For example, after the version 2 was released, it was still possible to continue updating the previous version by executing composer self-update --1.

At this time Grav can only update to latest releases, this is by design, to a certain degree, since we always encouraged Grav instances to run latest. And so GPM is not capable of understanding multiple stable releases, only different dependencies requirements.
However as we are starting to think Grav2, we most definitely want to provide a way for people to stick to 1.7 and for us to to still be able to provide updates for targeted channels as we move along with 2.0, but this is nowhere in the near future unfortunately.
One thing you can do, though, is to use the direct-install command, bin/gpm direct-install <url> (also available in admin), which will allow you to point to a specific version and perform the installation as you want.
Little known is that all our core/plugins/themes/skeletons  downloads can be reached by version. To grab the latest update package you can go to https://getgrav.org/download/core/grav-update/latest ... and so if you wanted to grab the latest 1.6 update version you could reconstruct the url as https://getgrav.org/download/core/grav-update/1.6.31
We are aware how this is not exactly ideal but at least it is a way, right now our goal is to ensure everyone gets on board with 1.7 that has some important architectural and performance updates, but also will ease the process of splitting stable releases when the time will come.
I hope this helps!

Hello @w00fz,
Thanks for your detailed response.

One thing you can do, though, is to use the direct-install command, bin/gpm direct-install <url> (also available in admin), which will allow you to point to a specific version and perform the installation as you want.

I think I will probably try this method, which seems to me quite close to the idea I initially had in mind.

I hope this helps!

I hope so too. If this method runs properly, I will close this issue (even if such a feature could indeed be considered for a next major release).

(...) and so if you wanted to grab the latest 1.6 update version you could reconstruct the url (...)

So, I used the admin panel with this reconstruction method to update to the last iterations of minor version 1.6 step by step. Everything worked fine, apart from version 1.6.29 which had to be skipped due to the following error:
Error while trying to download (code: 302): https://getgrav.org/download/core/grav-update/1.6.29
I now close this issue considering that the method suggested by @w00fz works properly. I'll let you consider if you want to open it back in case that such a feature will be workable in a future major version.
Thanks for your help. 👍🏼


Feature request : preview delta table

congratulation on this amazing product, getting authentifucation sorted is always a pain for business users.
now that you have the workspace guid, and the lakehouse guid, it will be nice to be able to preview the data, using something like delta_rs or duckdb, I know, it will introduce and extra dependency, but i think it will be a popular feature

Nah, just a simple preview 10 rows will be more than enough:)

so after thinking about this over the weekend I came to the conclusion that this should not be part of Fabric Studio.
Delta Lake is not only relevant for Fabric but also other tools like Databricks or Spark in general hence it would make much more sense to build another solution that works with all those tools and is not limited to Fabric Studio (or OneLake) only
for Parquet there are already some tools that visualize it i VSCode (https://marketplace.visualstudio.com/search?term=parquet&target=VSCode&category=All categories&sortBy=Relevance), however, none of them seem to work with Custom File System Providers that are used by Fabric Studio and OneLake extension.
I will open support tickets there and link them here for reference

Parquet Explorer (marketplace): https://github.com/adamviola/parquet-explorer/issues/31
this seems to be the most promising as it is based on DuckDB and allows you to specify individual SQL queries on top of the parquet!

or Parquet Visualizer (marketplace): https://github.com/luusluus/vscode-parquet-visualizer/issues/133
this looks even more promising as it also exposes metadata, schema, etc.


Usage of commit-and-tag-version within a CI/CD pipeline

Hi,
I'm planning to use commit-and-tag-version within my CI/CD pipeline to automate it when a release is triggered.
Do you have recommendations for setting it up ? I've scan the docs but didn't found any reference to CI/CD.
Specially regarding how to make a good usage of Github & Gitlab "release" feature.
Thanks !

Good point! We really should add something on this in the documentation.
It depends a bit on your workflow, but you can see an example of an automated workflow here. That script is triggered by a repository dispatch - and has a slight disadvantage in that there's a race between the commit and push it does and anyone else merging - which might not work for everyone.
I usually make the release after pushing the tag - but it can make more sense to do it the other way around - where the changelog is merged, and then the tag is generated.


Fixed NaN propagation from channel paddings on GPU

Non-pointwise (i.e. kernel size != 1x1) convolutions with "SAME" padding return incorrect results when applied after element-wise division. This occurs only when both tensor operands of division have the same number of channels C, where C is not a multiply of 4, because of zero-padding applied to such tensors.
The source of the problem is performing division on channel pads which are filled by zeros - since both sides of division are zeros this operation returns NaN (see: The OpenCL Specification: 6.3 Operators & IEEE Standard for Floating-Point Arithmetic: 7.2 Invalid operation).
The problem is not restricted to division. In case of pow function it is even more dangerous: instruction pow(0., 0.) returns 1 (see: The OpenCL Specification: 7.5 Edge Case Behavior), so there's no such a clear indicator of error.

To reproduce the mentioned behavior, convert the simple toy model constructed by the TensorFlow code below:
import tensorflow as tf
x = tf.placeholder(tf.float32, [1,4,4,1], name='x')
y = tf.placeholder(tf.float32, [1,4,4,1], name='y')
z = tf.truediv(x, y, name='z')
t = tf.nn.conv2d(z, tf.ones([3,3,1,1]), [1,1,1,1], 'SAME', name='t')

with t as an output node and feed it with the following input values:
x = np.ones([1,4,4,1])
y = np.ones([1,4,4,1])

Instead of the expected result, you will get the tensor of a shape [1,4,4,1] filled by NaNs.

@liyinhgqw do you know more or less when this PR will be processed - a week, two, longer?

Thanks for the great work.


UpdateOrder: Add 'startIndex', some collections' index starts at different number (not 0).

Description
In my real application, I need to UpdateOrder my Collection with startIndex is 1.
I did some changes to my local project. It worked perfectly.
How Has This Been Tested?
I ran default tests. I don't know how to add new tests.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Hi @dattiphu2022
This extension method does not need another parameter since it already has the zone offset. I've modified the example a bit to fit your use case
var fixedCollectionOffset = 1;
var indexOffset = dropItem.DropzoneIdentifier switch
{
	"2"  => _serverData.Count(x => x.Selector == "1"),
	_ => 0,
};

_serverData.UpdateOrder(dropItem, item => item.Order, fixedCollectionOffset  + indexOffset);

I close this PR.


Atlassian Document Formatting rendering doesn't handle inline elements and wrapping cleanly

The interaction between the default wrapped text renderer and multiple SameLine elements breaks down into being one wide, multiline cell, then a cell beside that with the SameLine element, finally any remaining text in a 1 char wide column.

This has been raised in https://github.com/ocornut/imgui/issues/2313 and the suggestion is to handle the wrapping manually.
For this ticket, we probably want to manually calculate some of the wrapping manually, which may require splitting texts up into wrapped whole lines, and rendering any lines with multiple components manually.

https://github.com/mekhontsev/imgui_md/tree/main Is a solid example of rich markdown in CPP, which is close to what needs to be done here


Readme Rst is broken

https://travis-ci.com/github/SymbiFlow/sphinxcontrib-verilog-diagrams/builds/172946780
Checking dist/sphinxcontrib_verilog_diagrams-0.0.post79-py3-none-any.whl: FAILED
  `long_description` has syntax errors in markup and would not be rendered on PyPI.
    line 81: Warning: Bullet list ends without a blank line; unexpected unindent.
Checking dist/sphinxcontrib-verilog-diagrams-0.0.post79.tar.gz: FAILED
  `long_description` has syntax errors in markup and would not be rendered on PyPI.
    line 81: Warning: Bullet list ends without a blank line; unexpected unindent.

Guess we should figure out how to test for that in a pull request?

https://packaging.python.org/guides/making-a-pypi-friendly-readme/#validating-restructuredtext-markup

Oh that's what travis is currently doing


Add the option to disable all page-view restriction options, sitewide

Is your proposal related to a problem?
In https://github.com/wagtail/wagtail/issues/11536 we got the behaviour where the option to use a shared ad-hoc password as a way to restrict page access. What remains is the facility to allow access based on the state of an authenticated User.
I would find utility in an extension of this kind of behaviour to either
a) only allow ad-hoc password-based restrictions and not an authenticated User
or, ideally, because it's significantly simpler:
b) disable the option to protect pages altogether
This is because I would like to deploy an entirely cookieless Wagtail site, which is technically possible now, but if an Editor sets a page to be protected and picks a page to be restricted based on some authenticated User's state, this will require a session cookie etc. Depending on how I handle the enforcement of a cookieless page/site, this would either just not work, or blow up.
Describe the solution you'd like
If we go with option a), a new setting called WAGTAIL_ALLOW_PAGE_RESTRICTION_VIA_AUTH_PAGE (default True) that removes the two options for auth-based access (logged in, or logged in and in a specific group) from the options, leaving Public or the password-protected options. If WAGTAIL_ALLOW_PAGE_RESTRICTION_VIA_AUTH_PAGE and WAGTAIL_ALLOW_SHARED_PASSWORD_PAGE are both set, this effectively means there are no possible options, and should raise a configuration error.
If we go with b), a new setting called WAGTAIL_PERMIT_PAGE_ACCESS_RESTRICTION (default True) that simply hides the entire permissions-setting UI in the admin and causes the page-view restriction code to skip, allowing access (regardless of what permission may have been set in the past.)
Working on this
This might be something I can contribute myself, but my time will be limited until later in the year (2024)
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

I have asked the core team their thoughts also and will for now add needs decision label to get a bit more consensus.
My opinion is that we should just have two new settings:

WAGTAIL_ALLOW_PRIVATE_PAGES OR WAGTAIL_ALLOW_RESTRICTED_PAGES
WAGTAIL_ALLOW_PRIVATE_COLLECTIONS OR WAGTAIL_ALLOW_RESTRICTED_COLLECTIONS

This hopefully simplifies the amount of settings to consider for this feature, but will not let a 'shared password only' scenario exist. Which is probably good as we do not want to make it too easy to have less secure features.
An alternative approach would be to adjust the settings added in https://github.com/wagtail/wagtail/issues/11536 / https://github.com/wagtail/wagtail/pull/11582 to maybe a List like approach.

WAGTAIL_PRIVATE_PAGE_OPTIONS = ['SHARED_PASSWORD', 'AUTH_GROUP', 'AUTH']
WAGTAIL_PRIVATE_COLLECTION_OPTIONS = ['SHARED_PASSWORD', 'AUTH_GROUP', 'AUTH']

This way the list could be modified to be any combination of the three privacy options, and an empty list would mean that the privacy features for those models would be disabled completely.
Since the settings in that PR are not yet released, we have a window of opportunity to change these, without a breaking change for developers. We could also make the List order reflect in the form (but that could be a different PR).

Discussed this today and there is a general consensus with the core team that we should revise the setting introduced in https://github.com/wagtail/wagtail/issues/11536 to be a bit more flexible (a dictionary) so that if/when we add more complex disabling of private pages/collections we can in the future.


console tools

ask password
ask choice
ask multichoice
ask yes no
ask multline
ask list
ask string
ask int

something like github.com/Mckinsey666/bullet

verified


Fix color selection operations in conhost

In conhost there is a keyboard shortcut that applies colors to the
selected range of text, and another shortcut that searches for the
selected text, and applies colors to any matching content. The former
operation doesn't work correctly when the selection is wrapped, and both
have problems when the selected text spans DBCS characters. This PR
attempts to fix those issues.
The problem with the color section was that it applied the color to a
simple rect spanning the start and end points of the selection. I've now
updated it to use the Selection::GetSelectionRects method, which
correctly handles a wrapped range of lines, and makes sure that double
width characters are fully covered.
The problem with the "find-and-color" operation was in the way it
obtained the search text from the selected screen cells. Since it
retrieved one cell at a time, and a DBCS character can span two cells,
that resulted in some characters being repeated in the search text. I've
now corrected that code to take the width of the characters into
account.
Validation Steps Performed
I've manually verified that the test cases described in #8572 and #8574
are now working correctly.
Closes #8572
Closes #8574

Good call. Thank you.


Android build fails: "Could not find Adb"

I git cloned this repository, and followed instructions for Android here. I have an up-to-date Android Studio.
The build failed. Here is the text from the "Build Output" panel in Android Studio.
> Task :app:buildCMakeDebug[arm64-v8a] FAILED
Execution failed for task ':app:buildCMakeDebug[arm64-v8a]'.
> com.android.ide.common.process.ProcessException: ninja: Entering directory `C:\Users\rober\Workspace\Vulkan-Samples\build\android_gradle\app\build-native\Debug\j366x1w5\arm64-v8a'
  [0/2] Re-checking globbed directories...
  [1/13] Update shaders in external storage
  FAILED: app/CMakeFiles/sync.shaders.stamp C:/Users/rober/Workspace/Vulkan-Samples/build/android_gradle/app/build-native/Debug/j366x1w5/arm64-v8a/app/CMakeFiles/sync.shaders.stamp
  cmd.exe /C "cd /D C:\Users\rober\Workspace\Vulkan-Samples\build\android_gradle\app\build-native\Debug\j366x1w5\arm64-v8a\app && C:\Users\rober\AppData\Local\Android\Sdk\cmake\3.22.1\bin\cmake.exe -DCMAKE_MODULE_PATH=C:/Users/rober/Workspace/Vulkan-Samples/bldsys/cmake C:/Users/rober/Workspace/Vulkan-Samples/bldsys/cmake/module -DFOLDER_DIR=C:/Users/rober/Workspace/Vulkan-Samples/app/../shaders/. -DDEVICE_DIR=/sdcard/Android/data/com.khronos.vulkan_samples/files/shaders/ -P C:/Users/rober/Workspace/Vulkan-Samples/bldsys/cmake/android_sync_folder.cmake"
  CMake Error at C:/Users/rober/AppData/Local/Android/Sdk/cmake/3.22.1/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
    Could NOT find Adb (missing: ADB_EXECUTABLE) (Required is at least version
    "1.0.39")
  Call Stack (most recent call first):
    C:/Users/rober/AppData/Local/Android/Sdk/cmake/3.22.1/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
    C:/Users/rober/Workspace/Vulkan-Samples/bldsys/cmake/module/FindAdb.cmake:50 (find_package_handle_standard_args)
    C:/Users/rober/Workspace/Vulkan-Samples/bldsys/cmake/android_sync_folder.cmake:26 (find_package)

There does seem to be an "ADB" in my Android Studio installation. Here in powershell...
PS C:\Users\rober\Workspace\Vulkan-Samples> ls C:\Users\rober\AppData\Local\Android\Sdk\platform-tools\

    Directory: C:\Users\rober\AppData\Local\Android\Sdk\platform-tools

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         1/11/2024  10:35 AM        5920544 adb.exe
-a----         1/11/2024  10:35 AM         108320 AdbWinApi.dll
-a----         1/11/2024  10:35 AM          73504 AdbWinUsbApi.dll
-a----         1/11/2024  10:35 AM         439584 etc1tool.exe
...

Is adb available in your path?

Is adb available in your path?

I don't think so. It seems to be part of Android Studio so I didn't think I'd need to set environment variables. I'm not too familiar with Windows, but it seems there is a way to set system-wide Path environment variable in the settings.

The you need to make it available via the path. Otherwise the build process for the samples simply can't find it.

Thank you. I added it to the PATH env var and restarted Android Studio. Seems to have worked.


Update Error

When selecting "Check for Updates" from the BitBar dropdown menu, I get an update error:

I am on the latest version of BitBar (1.9.2), running on MacOS 10.13.3 (17D102), and currently only use one plugin:
Weather by Daniel Seripap

I have the same error

It's probably due to this: https://githubengineering.com/crypto-deprecation-notice/
But there's no new release/version anyway, and it seems unlikely there will be one soon.

This is still an issue.

There are two problems: first, Sparkle is too old and, second, URL used to update don't works -and is hardcoded: https://github.com/matryer/bitbar/blob/master/App/BitBar/AppDelegate.m#L36-L39
I created a release with a "new" version (v1.9.3) resolving these problems, because I see that project is abandoned 😞
https://github.com/alexandregz/bitbar/releases/tag/1.9.3


Two primary keys?

I'm wondering if it's possible to have two Primary Keys for some tables, like:
CREATE TABLE "public"."players" (
  "id" int8 NOT NULL DEFAULT nextval('players_id_seq'::regclass),
  "tenant_id" int8 NOT NULL,
  "name" varchar COLLATE "pg_catalog"."default" NOT NULL,
  CONSTRAINT "players_pkey" PRIMARY KEY ("tenant_id", "id"),
  CONSTRAINT "players_tenant_id_fkey" FOREIGN KEY ("tenant_id") REFERENCES "public"."tenants" ("id") ON DELETE NO ACTION ON UPDATE NO ACTION
)

I cannot find any info for this.

Hey @frederikhors 👋
Ent does not support composite primary keys for nodes currently (unlike edge schemas).
Technically, the implementation does not require significant changes in Ent because edge schemas already support it. However, I decided not to support it atm (until we'll finalize the design) because it won't play nicely with many of the integration we provide today with Ent. e.g. entgql - a Node in the graph must have an ID (it's also called ID in your tables). If users want to set up a unique constraint on two or more fields for now, they can use index options.
I think we can close this as it's a duplicate of https://github.com/ent/ent/issues/400.


Start iOS Simulator Not Shows after updating Flutter 1.22

Steps to Reproduce

Choose Device to Run the App
Only Shows Create Android Emulator
Previously its shows both Start iOS Simulator & Create Android Emulator

Expected results:
It should show Start iOS Simulator & Create Android Emulator both options.
Actual results:

Note: I have installed Flutter v1.22 and XCode 12 with iOS 14

Hi @Safnaj
"
Do you have an iOS simulator in your doctor -v?
No issues with VSC 1.49.2  on v3.15.0 VS Code Flutter  extension

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.0, on Mac OS X 10.15.7 19H2, locale en-GB)
    • Flutter version 1.22.0 at /Users/tahatesser/Code/flutter_stable
    • Framework revision d408d302e2 (3 days ago), 2020-09-29 11:49:17 -0700
    • Engine revision 5babba6c4d
    • Dart version 2.10.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 50.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.15.0

[✓] Connected device (1 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios • iOS 14.0.1

• No issues found!

Following the indication of VS Code Flutter Extension, the correct way to address the problem is to open an issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

@TahaTesser in flutter doctor -v the device is appears if i only start the simulator. As in the image you shared above it's not showing the "Start iOS Simulator".

@TahaTesser I have updated the XCode 2 days back. Will cause this issue ??
And do we need to have XCode Command line tools as well ?

@Safnaj
Yes, that's how it should be, If the simulator is launched it will show in doctor -v
Since this is VS Code plugin menu, please fille issue on their GitHub as mentioned https://github.com/flutter/flutter/issues/67074#issuecomment-702627589

@TahaTesser Seems still this issue isn't fixed

@TahaTesser Seems still this issue isn't fixed


Read message functions

(peer_message, num_peers) read_peer_message(void* data, size_t num_bytes)
ask_message read_ask_message(void* data, size_t num_bytes)

read peer_message should be a tuple of peer_message and the number of messages because it's not a fixed sized message (maybe make a new struct)
And then also a function to determine the message type:
int message_type (void* data, size_t num_bytes)

these should be added to https://github.com/olincollege/p2p-networking/blob/main/src/message.h


Improve cache key to better discriminate among caches

Pull Request Template
Checklist

[x] Confirm that run-checks script has been executed.

Changes
This PR improves the cache key taking into account Rust version and test environment

I think the Rust version is already factored in: https://github.com/marketplace/actions/rust-cache#cache-details
Separate caches for std/non-std should be an improvement, and the total cache size across the 4 seems to be about 6GB, which is under the 10GB limit.

@dae
Yep, I agree with your analysis. This size could become a problem when we will add Windows and MacOS actions, but we can evaluate at that time in my opinion. My goal was to solve this error
Failed to save: Unable to reserve cache with key v4-rust-Linux-rust--tests-23d4eae1-894e3aac, another job may be creating this cache. More details: Cache already exists. Scope: refs/heads/main, Key: v4-rust-Linux-rust--tests-23d4eae1-894e3aac, Version: 95cda81848c40b56b71b455f4462d3fda43719d53b2cb3305caf419a71f4d12c


Truncation tests

A more complete set of truncation tests and some guards to avoid panics.
Closes #39.

Mostly I just dropped the ball, but the review is definitely appreciated.


Support storing multiple cells with different metadata in the same HDF5

The recently-added ability to add multiple cells worth of data per HDF5 creates a problem: what if we need different metadata to describe each cell?
Right now the solution is "don't store cells with different metadata in the same file," but I bet we could do better.

Fixed awhile ago


Fixed regression from speed refactor -- Show placeholder names unescaped

👍

Coverage increased (+1.08%) to 90.203% when pulling 0b0339bd3bfba54de0c516a1a5ad46db283a9826 on czpython:fixes/3.4/escaped-placeholder-name into 617c2c4088498ce4e76006ab9d8241ee7f15bd4d on divio:develop.


Custom Zip

Is it possible to create a custom zip and include non go files like templates and such?
I saw in the config file that you can provide a custom zip file, which i created by generating the go binary and placing it in a zip with my template but no dice.
Any suggestions?

Apologies, I read through the code and saw that my mistake was not setting the name of the go binary correctly.

Yea, there's the option to specify a specific zip file. That would leave you on the hook for building and zipping the binary and all the assets yourself rather than letting the deploy command doing it for you. I wanted to leave that flexibility in there for these kinda scenarios.
Typically I use something like go-bindata to embed assets into the binary itself...But you can of course include other files in the zip file.
Since AWS supported Go natively, there are actually no files to zip up other than the binary now. It may be worthwhile to specify some sort of "assets" directory to also include in the zip file wholesale. Or a key in the yaml with an array of files underneath perhaps (more typing to do in your config).
Please feel free to open an issue requesting that if you find it useful or submit a pull request. It's something that would make sense in the deploy command. It's just something I never needed.


Deflake leave-via-kick/ban faster joins tests

We need to allow the homeserver under test to finish making requests to
the Complement homeserver before tearing it down, otherwise the
homeserver under test may mark the hostname:port combination as down and
refuse to contact it in subsequent tests.
Signed-off-by: Sean Quah<EMAIL_ADDRESS>
NB: you can tease out the flakes by forcing Complement to reuse ports whenever possible:
diff --git a/internal/federation/server.go b/internal/federation/server.go
index ed7974d..4c4ccbe 100644
--- a/internal/federation/server.go
+++ b/internal/federation/server.go
@@ -455,7 +455,10 @@ func (s *Server) Listen() (cancel func()) {
        var wg sync.WaitGroup
        wg.Add(1)

-       ln, err := net.Listen("tcp", ":0") //nolint
+       ln, err := net.Listen("tcp", ":63333") //nolint
+       if err != nil {
+               ln, err = net.Listen("tcp", ":63334") //nolint
+       }
        if err != nil {
                s.t.Fatalf("ListenFederationServer: net.Listen failed: %s", err)
        }

otherwise the homeserver under test may mark the hostname:port combination as down and refuse to contact it in subsequent tests.

Should we add some kind of escape hatch for this? E.g. an admin API which could be used to mark a destination as up, that complement could call whenever a test begins? (Not ideal, but we seem to hit this class of flake a lot...)

otherwise the homeserver under test may mark the hostname:port combination as down and refuse to contact it in subsequent tests.

Should we add some kind of escape hatch for this? E.g. an admin API which could be used to mark a destination as up, that complement could call whenever a test begins? (Not ideal, but we seem to hit this class of flake a lot...)

We could do. It's very Synapse and faster joins test-specific though. We only hit this class of flake because we reuse the same Synapse with lots of different Complement instances in the faster joins test suite.


Penv 262 api search

- What I did
- How I did it
- How to verify it
- Description for the changelog

Codecov Report

Merging #60 into master will increase coverage by 0.86%.
The diff coverage is 97.50%.

@@            Coverage Diff             @@
##           master      #60      +/-   ##
==========================================
+ Coverage   73.03%   73.90%   +0.86%
==========================================
  Files          40       40
  Lines        2355     2433      +78
==========================================
+ Hits         1720     1798      +78
  Misses        518      518
  Partials      117      117

Impacted Files
Coverage Δ

api/handlers.go
86.74% <97.36%> (+3.46%)
:arrow_up:

testutils/models.go
85.96% <100.00%> (ø)

api/mappers.go
100.00% <0.00%> (ø)

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 7db3789...9c5c4a5. Read the comment docs.


ci: use host kubectl in k8s-all

test-missed-k8s

test-missed-k8s

We got hit by a known k8s-all flake, otherwise looks really good! Let's merge.

Added missing commit message

test-missed-k8s

previous failure https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/3782/

test-missed-k8s

same test failed: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/3783/
I think it's out of scope of this PR, will merge this one and we can continue fixing K8sVerifier Runs the kernel verifier against Cilium's BPF datapath in another one


Added Windows 95 style buttons in the Specials

Hey, I created another button type, which closes Issue #433
These are Windows 95 style vintage buttons.
I am using a font from Google Fonts.
Do let me know how you think of it!

I suggest using this font instead: https://fonts.google.com/specimen/VT323?category=Monospace

Looks good thank you!


Need a test to ensure specific files are saved as grids and not maps

The amount of times nukieplanet + infiltrator + centcomm have broken because they were saved as maps instead of grids is too damn high.

Duplicate of #11674  ?


FR: Detect manifest changes and automatically run lock

Currently, the lock generation is manual, and sometimes forgotten after manifest changes, it would be nice to detect manifest changes. and trigger lock generation and update the lockfile in place.

A thought - If/when we do this, could we have a lockfile mode similar to bzlmod, where you can make it fail if the manifest has changes rather than auto-updating?  Otherwise we can end up with spurious diffs being generated into source in CI runs, for example.
Thank you


Review updates v3

back to top link
minor styling changes

@matthewringer the update of re-using the existing "top" id element is implemented along with minor css change.