Segfault in blobToKzgCommitment

Description
Encountered another segmentation fault, but this time in blobToKzgCommitment:
CKZG4844PropertyTest > fuzzBlobToKzgCommitment STANDARD_OUT
    2022-12-16 15:53:01.934+00:00 | Test worker | DEBUG | CKZG4844 | Loaded trusted setup from /tmp/trusted_setup1663048493037019535.tmp
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f9ceaac6880, pid=455, tid=457
#
# JRE version: OpenJDK Runtime Environment Temurin-11.0.13+8 (11.0.13+8) (build 11.0.13+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (11.0.13+8, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libckzg4844jni.so+0x1c880]  blst_lendian_from_scalar+0x10
#

Which was caught here (needed to scroll up about 100 lines to see it):

https://app.circleci.com/pipelines/github/ConsenSys/teku/22710/workflows/ee035a90-d007-4c93-9fc2-40d110067e89/jobs/163972

This is very similar to the original issue mentioned in here:

https://github.com/ConsenSys/teku/pull/6596

Then it was a problem in blst_scalar_from_lendian, now it's blst_lendian_from_scalar.

Interesting. Need to update the binding library with the latest commits. I hope it gets fixed from this commit:
https://github.com/ethereum/c-kzg-4844/commit/cfa36097a3d0c85cebeb7c19b3789b6454589cae

Hmm I wish there were more information. Because it was a segfault jqwik doesn't provide a seed. And it would be nice if that crash file (/home/circleci/project/ethereum/spec/hs_err_pid455.log) were available. I'm having trouble reproducing it, running a billion iterations locally, haven't encountered it yet. Also, I'm having trouble finding where in the stack blob_to_kzg_commitment  calls blst_lendian_from_scalar... checking libckzg and blst.

It happened again.
https://app.circleci.com/pipelines/github/ConsenSys/teku/22714/workflows/6f15c709-04f5-40b4-9fbe-5e23ad2934fc/jobs/163995/
I could consider disabling that test until we find out what is happening.

I got a crash log (though it's not that useful). I had a hunch that panned out.

hs_err_pid1112105.log

It doesn't crash on arm64 systems. Had to run the fuzzer on amd64 for this.
I'll try to get the input blob now.

Thanks. Got one as well. The CI seems to fail often, so just raised a PR and printed out every blob. This one fails:
0x7c748addf4e969f60bfc1e15f80a7e2d945f942016a4c9a60bc1ff8179f34de8d27e87bae656f8fdfb1925f90496e4f9727bfbfc1f75f5d9ff0f016900cccd8500530222540d0745df061cf8daf40b026eff02811a918023f8e747b3fad26e8fee0271a8ee0abcc0d8f96c02f5c80cdcdfd0f501f50d46e16d7ceef215b1f924f49cfea505495eb1ede0c290f31a05e40ff300e667c1f60c221a00f3e8f5031dfbe60d4e0a0bfaf3f2fa042602ad150112feae0946f6006a6583f9d60bebf720f1057ef3fd01faf3daf5f759e1d6130f1e9bd8ee450c068af5

It seems to pass with latest version of c-kzg. Will release a new version of the jc-kzg library and this should fix it.

Hmm something is happening. Now getting segfault sporadically for the following blob 0xfd82d8
It works most of the time with C_KZG_BADARGS error but if I ran it 1000 times in a loop, I get segfault error at some point.

Interesting. I have also been trying to figure it out, but to no avail. It doesn't seem to be reproducible with a certain blob. In the test, I would append each blob to a file before calling blobToKzgCommitment on it. When it would eventually crash, I would try again with that blob and it works fine. I would run the last 10, 100, 1000, 10000 blobs and it would still work. I'm starting to think it has less to do with a particular blob and more to do with the number of calls. Maybe there's an underlying memory issue; like it's allocating space for something, never freeing it, and eventually running out.

I suspect some memory issue in the base ckzg lib.
Running even a very minimal test looks like it leaks some bytes.
#include <stdio.h>
#include "c_kzg_4844.h"

FILE *fp;
KZGSettings s;

int main() {
    fp = fopen("trusted_setup.txt", "rb");

    load_trusted_setup_file(&s, fp);
    free_trusted_setup(&s);

    fclose(fp);
    return 0;
}

The Valgrind result is not quite clean:
==3738== Memcheck, a memory error detector
==3738== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==3738== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==3738== Command: ./a.out
==3738==
==3738==
==3738== HEAP SUMMARY:
==3738==     in use at exit: 32 bytes in 1 blocks
==3738==   total heap usage: 9 allocs, 8 frees, 1,596,248 bytes allocated
==3738==
==3738== LEAK SUMMARY:
==3738==    definitely lost: 0 bytes in 0 blocks
==3738==    indirectly lost: 0 bytes in 0 blocks
==3738==      possibly lost: 0 bytes in 0 blocks
==3738==    still reachable: 32 bytes in 1 blocks
==3738==         suppressed: 0 bytes in 0 blocks

The number of allocs and frees should match, and there should be zero bytes lef tover.
I'll take a proper look into this a bit later.

This might help. I'll do some more extensive memory leak testing shortly.

This might help. I'll do some more extensive memory leak testing shortly.

Thanks Ben 🙂 I will give it a test

Maybe worth mentioning that the fuzzing test only loads the trusted setup once per property test and reuses that instance for all 1000 iterations, so I wouldn't expect that particular fix to solve the issue.

Yes, agreed, except that memory can be fickle. I didn't find any other memory issue in the blob_to_kzg_commitment() primitive. I'll take a look at the Java bindings and see what's there.

This issue has been fixed in https://github.com/ethereum/c-kzg-4844/commit/d06df97716a47bbec2ed83f488e6bc60bead6517 . Thanks to @benjaminion for the help. After releasing a new version of the library, will re-enable the property test and close this issue.


Switch from Poison to Jason

Poison has gone several months without a merge or update, and newer projects appear to prefer Jason for performance reasons. Since forcex only uses Poison in 3 or 4 locations, I'm hopeful that the conversion would be straightforward.

One point that caught my eye was that the current calls to Poison.decode!/2 look like this:
Poison.decode!(body, keys: :atoms)

The keys: :atoms option is supposed to use atoms for the map keys in the output. However, I reviewed the repo history and when it switched from JSX to Poison (https://github.com/jeffweiss/forcex/commit/c19d34fa4492bc501b24251253e7922529a2169a), that option was not already in use on the JSX call.  This is relevant because as far as I can tell, Jason does not offer an option to use atoms as keys when decoding.

Also, I learned that Jason added the keys: :atoms option in a later version than the one I was viewing, so the transition is very clean.


TimePicker not working

Describe the bug
Imported the Vue-Datepicker into my project and added it to my main.ts in order to use it globally
But if I use the TimePicker, there's the elements to input the time missing:

To Reproduce
Steps to reproduce the behavior:

Use npm install @vuepic/vue-datepicker on your project

Add the Datepicker globally in your main.ts

Use the Code example from here: https://vue3datepicker.com/api/props/#timepicker
Added it like that

Open the view to see the first screenshot

Desktop & mobile (please complete the following information):

Browser: Google Chrome Version 101.0.4951.67 (Official Build) (64-bit)
Library version: @vuepic/vue-datepicker 3.2.1

No errors in the console sadly, the content of the box is just empty
How did u import the project into the sandbox?
Maybe I can try that to import it into my project

You can check the sandbox for code, just pasted your config.

After a good while of finding the issue:
Turns out if u got :
*, *::before, *::after {   position: relative; }
in your code, the buttons for the Clock will just disappear

Got it now but gotta find a workaround for the other elements then


Add support to list type

Add support for read/write collection list column
Add support for querying with parameter of array type (e.g., select ... in <array>)

Currently [Int8], [Int16], [Int32], [Int64], [Float32], [Double], and [String] are supported.
Resolves https://github.com/apple/swift-cassandra-client/issues/24

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please


Finalize kapacitor flux tasks API & UX

After https://github.com/influxdata/kapacitor/pull/2555 , we have flux tasks working, provisionally at API endpoint kapacitor/v1/fluxtasks/... instead of 2.x's api/v2/tasks .
Need to figure out the actual correct api endpoints (probably kapacitor/v1/flux/tasks ?) and figure out how the users will actually access this API - will the influx client work or should we add this to the kapacitor client?

hmmm... I'm using this as a reference: https://docs.influxdata.com/influxdb/v1.8/tools/api/
to review how we handled the compatibility between v1 and v2 for the read and write paths on InfluxDB.
any reason not to do /api/v2/tasks  where the  bit is the base path?


Mention the needed permissions

The article doesn't mention the needed permissions, in my testing by using a service principal (service principal is creating an application) I found that it requires permissions for the API Application.ReadWrite.All . If it's a user that create the application, they should have Application administrator or Application Developer. Or allow all the users to register applications in the user settings.

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

ID: 3b877a4c-5a97-c923-424a-516b22f34684
Version Independent ID: 84b2cbcb-1f11-9a6d-23fd-5c8d76453fa8
Content: Create an Azure service principal with Azure PowerShell
Content Source: docs-conceptual/azps-1.2.0/create-azure-service-principal-azureps.md
GitHub Login: @sptramer
Microsoft Alias: sttramer

Required permissions depend on what the service principal will be used for, and change from user to user. Users who need to look up role information can do so by reading the linked RBAC documentation.
This section will be edited to remove guidance suggesting that Reader is the ideal default role to assign a service principal, and make it clearer that role guidance depends on what the service principal is intended to be used for.

I agree with this original comment. I understand that some roles need certain applications, but what permissions are needed to call something generic like Get-AzADServicePrincipal?


can get request id with koa-morgan

So I am trying to include the request-id in my logging, but it doesn't work with koa-morgan.
Here's my code:
import Koa from "koa"
import morgan from "koa-morgan"
import rTracer from "cls-rtracer"

const app = new Koa()
app.use(rTracer.koaMiddleware())
app.use(getMorgan())

app.use(() => {
  console.log("it works here", getReqId())
})

app.listen(8080)

const getReqId = () => {
  return (rTracer.id() ?? "") as string
}

const getMorgan = () => {
  morgan.token("reqId", getReqId)
  return morgan("it doesn't work here  :reqId")
}

then when I run the app
> curl --location --request GET 'localhost:8080/'

it works here fc7170b0-b328-11ed-b4d4-11d1313525c1
it doesn't work here -

I end up setting the echoHeader option to true and getting the request-id from the response header.  Works for me.
import Koa from "koa"
import morgan from "koa-morgan"
import rTracer from "cls-rtracer"

const app = new Koa()
app.use(rTracer.koaMiddleware({
    echoHeader: true,
  })
)
app.use(getMorgan())

app.use(() => {
  console.log("it works here", getReqId())
})

app.listen(8080)

const getReqId = () => {
  return (rTracer.id() ?? "") as string
}

const getMorgan = () => {
  morgan.token("reqId", (req, res) => {
    return (res.getHeader("x-request-id") ?? "") as string
  })
  return morgan("now it works :reqId")
}

Thanks for sharing the workaround! Unfortunately, not all libraries play nicely with ALS.


F/memberui base

touching up FAQs

Deploy preview processing.
Built with commit fbd9221a90967588c53fcb4fcfb58472ab6c37a9
https://app.netlify.com/sites/voteflux/deploys/59c094caa700c43dd1442f29


Can't launch. "fusion360.exe" is not responding.

I don't know how to even begin to troubleshoot. All seemed to install smoothly from the install script, but when I try launching Fusion 360 I get this:
Any ideas of where to begin?

s:

You must wait.  🙂 This issue exists only systems with the Gnome desktop environment.


Added 'Catppuccin' Colorscheme

Added Catppuccin Theme, Mocha (Dark Mode) and Latte (Light Mode). This Colorscheme is very popular among obsidian users and you want your structures to match the theme you are currently using with obsidian.
Here is the preview of how it looks:

I'm refactoring codes to enable multiple cores, and the theme settings will be affected. I will include this theme once new version of settings are ready.


[engine] Sync Flutter 3.13.1 source code

Copy embedder.h and DEPS from the Flutter 3.13.1 engine source tree.
engine: https://github.com/flutter-tizen/engine/tree/flutter-3.13.1

Changes to SystemChannel.

[ ] https://github.com/flutter/flutter/pull/96637
[ ] https://github.com/flutter/flutter/pull/121378
[ ] https://github.com/flutter/flutter/pull/126075
[ ] https://github.com/flutter/flutter/pull/122885

https://github.com/flutter-tizen/embedder/pull/36/commits/b0bd1112ec05f36019d74f8012fceb1864b4d3c9


Update font

Choose condensed font to avoid overflows in width of blockquotes. Also make dark gray (222) instead of black.

Fixed by shrinking font to 85% in code blocks, decided to stick with pure black.


Merge "bundle configuration" and "configuration reference" documentation sections

@SimonMellerin @Lonnytunes should we keep this opened? I like having both basics and reference.


Check if table tag is closed in PD_1.html

In the mock PD_1, the table isn't closed.  Check if that's correct.

There isn't a table of countries in the real PD_1. Will delete it from mock data.

Okay, then map should be the only topic of interest for us.


Audio Glitches when multiple notes are playing at once

When I have a longer audio file going and play a different audio, they both start making clipping sounds, when the second audio file finished, the first is left with the clipping. playing more audio files at once really glitches them all out

I plan on using audio notes to play sound effects for a dnd game, I like to have a droning ambience sound playing in the back, but when I play multiple audio files issues occur.

Hey @CowChunks, currently the app is only designed to play a single sound file at once. This would be a great addition but would require a significant amount of rework, so this is unlikely to happen soon.


Update of testcase generator to latest JSON format

Hey, as already discussed in Slack I have created a draft for the new version of the test case generator. I have also included the code covering #2055 (I have used code from #2276 and adjusted it a bit). Summary of what I have done:

Collection of all test cases from the canonical-data.json and group by the value of the field property
Removement of the test cases with inclue=false in the tests.toml
Removement of the version info in the header of  cases_test.go as the info is not provided in the canonical-data.json anymore (#1678)
Generator expects now a struct for each of the groups defined by property (fields that have multiple data-types for one field have to be handled with an interface{} and have then to be handled by each specific generator)
I have removed property.json as I think this is not needed anymore

To check if we have forgotten anything I have refactored the following generators:

bowling: shows how multiple values for property can be handled to generate multiple cases with different structures and also how to handle an interface{} directly in the generator
diamond: no special purpose, but I tried it as I made some changes to this one some days ago
forth: shows how to handle an interface{} in the generator (I have also refactored the forth_test.go a bit as I don't think the info about the groups is really needed here and I also made use of t.Run and improved the error-messages)

NOTE: The use of multiple data types for one field mostly happens values and errors are used like here (expected is a struct and a number):
 {
      "uuid": "29220245-ac8d-463d-bc19-98a94cfada8a",
      "description": "an unstarted game cannot be scored",
      "property": "score",
      "input": {
        "previousRolls": []
      },
      "expected": {
        "error": "Score cannot be taken until the end of the game"
      }
    },
    {
      "uuid": "656ae006-25c2-438c-a549-f338e7ec7441",
      "description": "should be able to score a game with all zeros",
      "property": "score",
      "input": {
        "previousRolls": [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
      },
      "expected": 0
    },

Hey @junedev and @andrerfcsantos, could you please have a look at the implementation and the changes on the test case generator and give me some feedback

Hey regarding #2056: I have done the following things:

updated tests.toml
created a new test-case generator
implemented the tests of the generator

Here is what I faced: when using the code from the example.go to run the tests, all tests of the problem-specifications failed and all with the same problem. Here an example:
Input:
4 5 4
3 5 5
1 5 4

Expected output in problem-specifications:
 "expected": [
        {
          "row": 1,
          "column": 2
        },
        {
          "row": 2,
          "column": 2
        },
        {
          "row": 3,
          "column": 2
        }
      ]

-->[]Pair{{1, 2}, {2, 2}, {3, 2}

As this test was also implemented in the existing test-cases here the expected value there:
[]Pair{{0, 1}, {1, 1}, {2, 1}

As you can see each value is incremented by 1, compared to the problem-specifications (index instead of position). This is also the case for all other test cases. Possible solutions:

we adjust the example solution to match the expected problem-specifications
we increment each value of the expected result by 1, by using the following template:

{{printf "%d+1" .Row}},
{{printf "%d+1" .Column}},

Please tell me what you expect here

You are right, we should split Gen a bit up and add some tests. Please open a new issue for that

Hey regarding #2056: I have done the following things:

updated tests.toml
created a new test-case generator
implemented the tests of the generator

Here is what I faced: when using the code from the example.go to run the tests, all tests of the problem-specifications failed and all with the same problem. Here an example: Input:
4 5 4
3 5 5
1 5 4

Expected output in problem-specifications:
 "expected": [
        {
          "row": 1,
          "column": 2
        },
        {
          "row": 2,
          "column": 2
        },
        {
          "row": 3,
          "column": 2
        }
      ]

-->[]Pair{{1, 2}, {2, 2}, {3, 2}

As this test was also implemented in the existing test-cases here the expected value there:
[]Pair{{0, 1}, {1, 1}, {2, 1}

As you can see each value is incremented by 1, compared to the problem-specifications (index instead of position). This is also the case for all other test cases. Possible solutions:

we adjust the example solution to match the expected problem-specifications
we increment each value of the expected result by 1, by using the following template:

{{printf "%d+1" .Row}},
{{printf "%d+1" .Column}},

Please tell me what you expect here

What about this question? This is the reason why CI is currently failing

we adjust the example solution to match the expected problem-specifications

I like this better, because it makes the student's solution match the position numbers provided in the example and in the tests.
It seems that this exercise originally had the table in the example using 0-based indexes, and when the exercise was introduced in the track, both description and tests were written with that assumption. However, with https://github.com/exercism/problem-specifications/pull/1429 the description and canonical data were updated to use 1-based indexes in problem specs. Then with the change to v3, the exercises' descriptions for the Go track were updated to use the latest version by https://github.com/exercism/go/pull/1410, but the tests were not updated.

Hey, is it OK to handle this add the end by adding 1 to the index-based values, or do we want to handle this somewhere else?

Hey, is it OK to handle this add the end by adding 1 to the index-based values, or do we want to handle this somewhere else?
I removed the old tests, as the ones from problem-specifications have more test cases and cover similar problems.

@eklatzer I'm not sure I understand the question. If you are referring to how to handle this in the example solution then you are free to handle this however you like. The example solution does not have to be a very good solution, it only needs to be a solution that passes the tests for CI purposes.

Two more things I forgot to mention:

THANKS! :slightly_smiling_face:
Please create an issue about updating/extending the README regarding generators. With this new system there are some things to be aware of when writing a generator that should be pointed out (e.g. that cases are flattened, that the key is the property).

Two more things I forgot to mention:

THANKS! 🙂
Please create an issue about updating/extending the README regarding generators. With this new system there are some things to be aware of when writing a generator that should be pointed out (e.g. that cases are flattened, that the key is the property).

Thanks for the feedback🙂

The Gen function is getting quite big and it's doing a lot. It might be worth separating it into several smaller functions that are more testable. However, I'm fine with this being a separate PR - that shouldn't block this one. Let me know what you think, and if you agree in making this a separate PR, I'll create the issue for it.

Ok, then please create a new issue about updating the exercise generator files that describes the 2 reasons there are issues (the one with the changes signature and the other one with the new canonical data format you noticed earlier).

We should maybe wait with updating the exercise generators until we have split up the func Gen.
Here a script to get all exercises with a gen.go formatted as task (has to be started at root of project):
# ! /bin/bash

find ./exercises/ -name 'gen.go'|while read fname; do
  exercise=$(echo "$fname" | cut -d/ -f4)
  echo "- [ ] $exercise"
done


Partial ratings

The rating process is somewhat lengthy, with 5 different star ratings and an optional text review:
        uint32 overall                      = 8;
        uint32 quality                      = 9;
        uint32 description                  = 10;
        uint32 deliverySpeed                = 11;
        uint32 customerService              = 12;
        string review                       = 13;

Should we allow the user to skip one or more of the start ratings? For example, what if a buyer just wants to make a star rating for overall? Or what is a buyer just wants to leave a text review?

@drwasho thoughts?

There are at least two UX reasons to do this:

I have implemented @morebrownies's feedback page. Notice the "Post Review" button at the bottom right. When the page is first loaded, the "Post Review" button is clickable because we allow no review. However, after a first star rating has been made, the "Post Review" becomes non-clickable until all star ratings are completed. It's a bit awkward.
Sometimes the star rating is irrelevant. For example, rating delivery may not be relevant for digital goods. Sometimes even quality is not relevant. Have a look at the first rating on this page. The buyer put a 4/5 stars and wrote:

Since this was a present to my sister, I can't really rate the quality

I think it would be ok to make the star ratings optional. There are certain times when customer service isn't relevant either, especially when purchasing digital goods that have automatic delivery. I would probably rate the Vendor a 5 in those scenarios, but it is a bit misleading.
Waiting to hear from @drwasho on this as well.


Scrollbar thumb moves to inconvenient position when zooming

Describe the bug
When using the library on a div element that has scrollbars, the position of the scrollbar thumb at a higher zoom level hinders viewing the whole element.
To Reproduce
Steps to reproduce the behavior:

Go to the following sandbox link

https://codesandbox.io/s/recursing-cherry-n7jn8r?file=/src/App.js

Scroll down to the middle of the element and zoom. You'll notice that the vertical scrollbar thumb shortens but also moves up, which is inconvenient since you can't really view the text at the top of div at that zoom level. The same happens to the horizontal scroll bar.  It'd be great if there's a way to position the thumb at the same scroll position when zooming in, so that we could navigate the whole element.

I've tinkered with TransformWrapper functions, but no modification seems to change the default behavior. Any ideas or suggestions regarding this would be helpful !

Hi @prc5 I tried a few different methods to adjust the scrollbar while zooming, but couldn't come up with anything useful. Can you please suggest a way to solve this issue?


docs: Move registry auth to helm provider in karpenter example

Description
Move the oci registry configuration to the helm provider block in the karpenter example
Motivation and Context
Helm 2.8 (https://github.com/hashicorp/terraform-provider-helm/releases/tag/v2.8.0) allows an oci registry configuration in the provider block. This change means that the password field in helm_release doesn't change with every plan.
Breaking Changes
Required update to helm provider in example
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

this looks great.
however I have a question:
how is this better than using repository_username/repository_password on helm_config ?


Link to model weights

Hi,
would you mind sharing your model weights on other cloud where no registration is required?
I tried hard but can't make it work.
thanx

Same issue here. I seem to get an error when I try to download the weights provided in this link using the provided password: 1ri5.
Many thanks in advance.

I downloaded and uploaded it on google drive link. Hope it helps when waiting for official link from the author.

what architecture is used? There are differences in parameter names

all right I just loaded as he did in main.py.
Thanks @phamtrongthang123


Use workflow name as default release name

Instead of using the Branch name, using the Workflow name as default name would be more useful
RELEASE_NAME="${INPUT_NAME}"
if [ -z "${RELEASE_NAME}" ]; then
  RELEASE_NAME="${GITHUB_WORKFLOW}"
fi

  --argjson name              "$(toJsonOrNull "${RELEASE_NAME}")"       \

Branch name leakage was a bug, that I've fixed here: https://github.com/meeDamian/github-release/commit/635d8d8db698f7fb13b57e4eb85db6b4ff809e01 .
Can't imagine scenarios where naming releases after workflow file would make sense - care to elaborate?

If you are producing multiple libraries from a repo, it is handy.  Check this out https://github.com/cilerler/ruya/releases (by the way, generated those with the way I suggested.

Alright, gotcha!
I think doing it by default might be confusing as I would guess it's not a very common case, would exposing a this option as a corresponding var env help?

Definitely! Be able to use ENVVAR would solve most of the problems I reported.


fold code: show bottom arrows

Type: Feature Request

please
show bottom arrows is a very very nice feature
VS Code version: Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:09:22.859Z)
OS version: Windows_NT x64 10.0.19045
Modes:

/duplicate of #60670
PR #77363 is awaiting a response from @aeschli

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

/duplicate of #60670
PR #77363 is awaiting a response from @aeschli

I have searched at the PR and issues, and it has been many years. Is it possible for this feature to be added in future versions？


Facebook login as custom provider not working

Describe the bug
Following the directions for Facebook login at https://learn.microsoft.com/en-us/azure/static-web-apps/authentication-custom?tabs=facebook leads to Facebook error page: "Feature Unavailable/Facebook Login is currently unavailable for this app." which leads to "The domain of this URL isn't included in the app's domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings."

then when you click OK, it goes to

A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to https://dungeondraw.shiningsword.org/
Click on "Login" and then "Facebook" in the upper-left corner
Observe error

The Facebook app is configured according to Azure Static Web App documentation for custom auth providers (AppDomain and redirect URI, plus a few other redirect URIs just in case), but apparently the redirectUri of https://identity.2.azurestaticapps.net/.auth/login/facebook/callback is causing Facebook to reject the request anyway.

Expected behavior
I expected the static web app to work the same way with Facebook as it does with AAD, which in this case would just print the user's name in the top-left:

Device info (if applicable):

Browser: Chrome

Additional context
I suspect this is actually a Facebook issue and I filed a bug at (https://developers.facebook.com/support/bugs/1317495038787988/), but they seem at a loss what to do about an app that isn't using Facebook's own JavaScript SDK to log in. In particular they seem surprised that Azure Static Web Apps specifies redirect_uri=https%3A%2F%2Fidentity.2.azurestaticapps.net%2F.auth%2Flogin%2Ffacebook%2Fcallback in the HTTP request.
If this is something that Azure Static Web apps can fix, I would like to know it; if it is something that is impossible for now, I would like  the documentation at https://learn.microsoft.com/en-us/azure/static-web-apps/authentication-custom?tabs=facebook to be updated to say it's impossible. If I'm the only one who encounters this issue I would like to know that too.

Additional datum:
Even though I have my FACEBOOK_APP_ID in the configuration file set to<PHONE_NUMBER>89063, the URL generated by https://identity.2.azurestaticapps.net's 302 redirect has a different clientId (client_id=1284854938630033).

GET request URL: https://www.facebook.com/dialog/oauth?response_type=code&**client_id=1284854938630033**&redirect_uri=https%3A%2F%2Fdungeondraw.shiningsword.org%2F.auth%2Flogin%2Ffacebook%2Fcallback&scope=public_profile%2Cemail&state=redir%3D%252F.auth%252Flogin%252Fdone%26nonce%3D21ad9cf61f8d45068e134fbb0d7f7bb5_20221026185935

Potential (untested) workaround: maybe if I use Bring-Your-Own-Functions (https://learn.microsoft.com/en-us/azure/static-web-apps/functions-bring-your-own) it might not have the same issue as static web apps do.

Could you please provide your app name/default hostname? We can look at our logs and give you the proper guidance on your auth setup. If you do not feel comfortable sharing that info with us here, feel free to file a support ticket.

@mkarmark The Static Web App is named DungeonDraw, and the auto-generated domain name is wonderful-mud-00aeae01e.2.azurestaticapps.net. Is that what you meant by "default host name"? Screenshots below.

I have this issue also. Try hitting whosum dot com slash .auth slash login slash facebook. It's just the standard Blazor auth (nothing custom-written). Works for Twitter and Github.

I got the Facebook auth to work.
First I had to switch from the free hosting model to paid.
Then, I had to specify the scopes. Without the scopes I had no success.
{
    "auth": {
        "identityProviders": {
            "facebook": {
                "registration": {
                    "appIdSettingName": "FACEBOOK_CLIENT_ID",
                    "appSecretSettingName": "FACEBOOK_CLIENT_SECRET"
                },
                "login": {
                    "scopes": [
                        "public_profile",
                        "email"
                    ]
                }
            }
}


Store Notebook controller ID in top-level metadata

I have a notebook type with different controllers. One controller is more suitable for some notebooks than another.
I was expecting the selected controller/kernel of a document to be part of the top-level metadata of the Notebook data, but it seems the metadata does not change based on the selection of the kernel.
Can the ID of the selected controller be saved in the metadata of the notebook?

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Fix B's Twitter link

Missing a / :smile:

thanks @dacort!

No problem! Thanks for publishing this, it's an amazing resource.


perf: implement coalescing for onPageScroll on iOS

Summary
Found inspiration in https://github.com/software-mansion/react-native-gesture-handler/pull/997:
This pull request implements event coalescing on onPageScroll event on iOS.
Event coalescing is a built-in mechanism from React Native's event-emitter that merges several events together when events are generated faster on the native thread than they can be handled on the Javascript thread. This prevents accumulating lag when JS thread is under heavy load (or on low-end devices).
NB: coalescing is the default on Android so no changes on Android were required
This PR basically implements the same behavior on iOS.
Test Plan
What's required for testing (prerequisites)?
The code below uses the fibonacci function to simulate a busy JS thread
function fibo(n: number): number {
  return n <= 2 ? n : fibo(n - 1) + fibo(n - 2);
}

const AnimatedViewPager = Animated.createAnimatedComponent(ViewPager);

const App = () => {
  const [text, setText] = useState(0);

  const scrollOffset = useRef(new Animated.Value(0)).current;
  const position = useRef(new Animated.Value(0)).current;

  return (
    <>
      <Text style={styles.text}>{text}</Text>
      <AnimatedViewPager
        style={styles.viewPager}
        initialPage={0}
        onPageScroll={Animated.event([{ nativeEvent: { offset: scrollOffset, position } }], {
          listener: ({ nativeEvent: { offset, position } }) => {
            fibo(35);
            setText(offset + position);
          },
          useNativeDriver: true,
        })}
      >
        <View key="1" style={{ backgroundColor: "yellow" }}>
          <Text style={{ fontSize: 30 }}>First page</Text>
        </View>
        <View key="2" style={{ backgroundColor: "blue" }}>
          <Text style={{ fontSize: 30 }}>Second page</Text>
        </View>
      </AnimatedViewPager>
    </>
  );
};

What are the steps to reproduce (after prerequisites)?
Here are GIFs demonstrating before and after the fix:

Before Fix
After Fix

Without event coalescing, the text label continues to be updated long after the gesture is actually ended. With event coalescing, it stops updating as soon as the scrolling ends, since there is no event accumulation in the native thread's event-queue.
Compatibility

OS
Implemented

iOS
✅

Android
✅ (no changes required)

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Thank you @Almouro for 2 great PR ❤
Could you resolve conflicts ?

Thanks @troZee, the pleasure was mine 🎉
Solved the conflict :)

For iOS, it works like a charm.
It does not work on Android

When I remove fibo(35), it work on Android, too.
Would like to fix android ?

Probably, you need to add below chunk https://github.com/software-mansion/react-native-gesture-handler/pull/997/files#diff-e6b4a0b8d8f24f0ab4b92f46c7c47355R34
to fix android

@troZee my guess is that fibo(35) is too much to calculate for the emulator, so the JS thread is completely locked and can never reach the setText line.
(you can enable the perf monitor to double check that)
Here's what I've tried to make sure coalescing is indeed working on Android:
In android/src/main/java/com/reactnativecommunity/viewpager/PageScrollEvent.java, add those lines in the class to explicitly disable coalescing:
@Override
public boolean canCoalesce(){
  return false;
}

Results on Samsung S10 Android 10, using fibo(32) instead of 35

Current behavior
Coalescing explicitly disabled with the above

In conclusion, event coalescing is the default for events on Android already as we can see here :)


[SPARK-19766][SQL] Constant alias columns in INNER JOIN should not be folded by FoldablePropagation rule

What changes were proposed in this pull request?
This PR fixes the code in Optimizer phase where the constant alias columns of a INNER JOIN query are folded in Rule FoldablePropagation.
For the following query():
val sqlA =
  """
    |create temporary view ta as
    |select a, 'a' as tag from t1 union all
    |select a, 'b' as tag from t2
  """.stripMargin

val sqlB =
  """
    |create temporary view tb as
    |select a, 'a' as tag from t3 union all
    |select a, 'b' as tag from t4
  """.stripMargin

val sql =
  """
    |select tb.* from ta inner join tb on
    |ta.a = tb.a and
    |ta.tag = tb.tag
  """.stripMargin

The tag column is an constant alias column, it's folded by FoldablePropagation like this:
TRACE SparkOptimizer:
=== Applying Rule org.apache.spark.sql.catalyst.optimizer.FoldablePropagation ===
 Project [a#4, tag#14]                              Project [a#4, tag#14]
!+- Join Inner, ((a#0 = a#4) && (tag#8 = tag#14))   +- Join Inner, ((a#0 = a#4) && (a = a))
    :- Union                                           :- Union
    :  :- Project [a#0, a AS tag#8]                    :  :- Project [a#0, a AS tag#8]
    :  :  +- LocalRelation [a#0]                       :  :  +- LocalRelation [a#0]
    :  +- Project [a#2, b AS tag#9]                    :  +- Project [a#2, b AS tag#9]
    :     +- LocalRelation [a#2]                       :     +- LocalRelation [a#2]
    +- Union                                           +- Union
       :- Project [a#4, a AS tag#14]                      :- Project [a#4, a AS tag#14]
       :  +- LocalRelation [a#4]                          :  +- LocalRelation [a#4]
       +- Project [a#6, b AS tag#15]                      +- Project [a#6, b AS tag#15]
          +- LocalRelation [a#6]                             +- LocalRelation [a#6]

Finally the Result of Batch Operator Optimizations is:
Project [a#4, tag#14]                              Project [a#4, tag#14]
!+- Join Inner, ((a#0 = a#4) && (tag#8 = tag#14))   +- Join Inner, (a#0 = a#4)
!   :- SubqueryAlias ta, `ta`                          :- Union
!   :  +- Union                                        :  :- LocalRelation [a#0]
!             This leads to the data of inner join being wrong.
After fix:
=== Result of Batch LocalRelation ===
 GlobalLimit 21                                           GlobalLimit 21
 +- LocalLimit 21                                         +- LocalLimit 21
    +- Project [a#4, tag#11]                                 +- Project [a#4, tag#11]
       +- Join Inner, ((a#0 = a#4) && (tag#8 = tag#11))         +- Join Inner, ((a#0 = a#4) && (tag#8 = tag#11))
!         :- SubqueryAlias ta                                      :- Union
!         :  +- Union                                              :  :- LocalRelation [a#0, tag#8]
!

Can one of the admins verify this patch?

@hvanhovell

ok to test

Test build #73588 has started for PR 17099 at commit 4463648.

Test build #73592 has started for PR 17099 at commit fc819f8.

Test build #73588 has finished for PR 17099 at commit 4463648.

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

Merged build finished. Test FAILed.

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

Test build #73594 has started for PR 17099 at commit c197b20.

Test build #73592 has finished for PR 17099 at commit fc819f8.

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

Merged build finished. Test PASSed.

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

Test build #73594 has finished for PR 17099 at commit c197b20.

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

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

Merged build finished. Test PASSed.

Could you add a test case to FoldablePropagationSuite? Thanks!

Test build #73659 has started for PR 17099 at commit 15fae50.

Test build #73659 has finished for PR 17099 at commit 15fae50.

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

Merged build finished. Test FAILed.

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

Thanks for @gatorsmile 's help.
ConstantFolding will affect other test cases in FoldablePropagationSuite.
It's fine without adding ConstantFolding.
Before fix:
[info]   !'Join Inner, ((a#0 = a#0) && (1 = 1))        'Join Inner, (('tb.a = 'ta.a) && ('tb.tag = 'ta.tag))
[info]   !:- Union                                     :- 'SubqueryAlias ta
[info]   !:  :- Project [a#0, 1 AS tag#0]              :  +- 'Union
[info]   !:  :  +- LocalRelation <empty>, [a#0, b#0]   :     :- 'Project ['a, 1 AS tag#0]
[info]   !:  +- Project [a#0, 2 AS tag#0]              :     :  +- LocalRelation <empty>, [a#0, b#0]
[info]   !:     +- LocalRelation <empty>, [a#0, b#0]   :     +- 'Project ['a, 2 AS tag#0]
[info]   !+- Union                                     :        +- LocalRelation <empty>, [a#0, b#0]
[info]   !   :- Project [a#0, 1 AS tag#0]              +- 'SubqueryAlias tb
[info]   !   :  +- LocalRelation <empty>, [a#0, b#0]      +- 'Union
[info]   !   +- Project [a#0, 2 AS tag#0]                    :- 'Project ['a, 1 AS tag#0]
[info]   !      +- LocalRelation <empty>, [a#0, b#0]         :  +- LocalRelation <empty>, [a#0, b#0]
[info]   !                                                   +- 'Project ['a, 2 AS tag#0]
[info]   !                                                      +- LocalRelation <empty>, [a#0, b#0] (PlanTest.scala:99)

After fix:
[info]   !'Join Inner, ((a#0 = a#0) && (tag#0 = tag#0))   'Join Inner, (('tb.a = 'ta.a) && ('tb.tag = 'ta.tag))
[info]   !:- Union                                        :- 'SubqueryAlias ta
[info]   !:  :- Project [a#0, 1 AS tag#0]                 :  +- 'Union
[info]   !:  :  +- LocalRelation <empty>, [a#0, b#0]      :     :- 'Project ['a, 1 AS tag#0]
[info]   !:  +- Project [a#0, 2 AS tag#0]                 :     :  +- LocalRelation <empty>, [a#0, b#0]
[info]   !:     +- LocalRelation <empty>, [a#0, b#0]      :     +- 'Project ['a, 2 AS tag#0]
[info]   !+- Union                                        :        +- LocalRelation <empty>, [a#0, b#0]
[info]   !   :- Project [a#0, 1 AS tag#0]                 +- 'SubqueryAlias tb
[info]   !   :  +- LocalRelation <empty>, [a#0, b#0]         +- 'Union
[info]   !   +- Project [a#0, 2 AS tag#0]                       :- 'Project ['a, 1 AS tag#0]
[info]   !      +- LocalRelation <empty>, [a#0, b#0]            :  +- LocalRelation <empty>, [a#0, b#0]
[info]   !                                                      +- 'Project ['a, 2 AS tag#0]
[info]   !                                                         +- LocalRelation <empty>, [a#0, b#0] (PlanTest.scala:99)

I just fix the test case("tb.tag" -> "tb.tag".attr).

Test build #73669 has started for PR 17099 at commit df11cc4.

LGTM

Test build #73669 has finished for PR 17099 at commit df11cc4.

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

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

Merged build finished. Test PASSed.

Thanks! Merging to master/2.1

@stanzhai Could you submit another PR to backport it to Spark 2.0?

ok


Unify the PROJECT folder name

In some .smk-s, we now changed that the "Project" folder name is defined in the config, but in some of them we still call it "Project"

Done


ERROR Except thrown while pulling user data:No JSON object could be decoded

填好api后 python servers.py
显示
Aug 27 17:38:04 INFO Multi-User Shadowsocks Server Starting...
Aug 27 17:38:04 INFO Current Server Version: 3.1.1-12-g43249c6
Aug 27 17:38:04 INFO Now using MultiUser API as the user interface
Aug 27 17:38:04 INFO Now starting manager thread...
Aug 27 17:38:09 INFO Now starting user pulling thread...
Aug 27 17:38:09 ERROR Except thrown while pulling user data:No JSON object could be decoded
一脸懵逼。。
配置文件
# !!! Please rename config_example.py as config.py BEFORE editing it !!!

import logging
# !!! Only edit this line when you update your configuration file !!!
# After you update, the values of CONFIG_VERSION in config.py and
# config_example.py should be the same in order to start the server
CONFIG_VERSION = '20160623-2'

# Manyuser Interface Settings
# ---------------------------
# If API is enabled, database will be no longer used
# The known app that supports API is SS-Panel V3
# Be careful and check whether your app supports this API BEFORE you enable this feature
API_ENABLED = True  #False  #True

# Database Config
MYSQL_HOST = 'localhost'
MYSQL_PORT = 3306
MYSQL_USER = 'xx'
MYSQL_PASS = 'xx'
MYSQL_DB = 'xx'
# USUALLY this variable do not need to be changed
MYSQL_USER_TABLE = 'user'
# This is also the timeout of connecting to the API
MYSQL_TIMEOUT = 30

# Shadowsocks MultiUser API Settings
API_URL = 'http://ss.aiwo.cf/mu'
# API Key (you can find this in the .env file if you are using SS-Panel V3)
API_PASS = 'xx'
NODE_ID = '1'

# Time interval between 2 pulls from the database or API
CHECKTIME = 30
# Time interval between 2 pushes to the database or API
SYNCTIME = 120
# Choose True if youi want to use custom method and False if you don't
CUSTOM_METHOD = True

# Manager Settings
# ----------------
# USUALLY you can just keep this section unchanged
# It is not necessary to change the password if you only listen on <IP_ADDRESS>
MANAGE_PASS = 'passwd'
# if you want manage in other server you should set this value to global ip
MANAGE_BIND_IP = '<IP_ADDRESS>'
# make sure this port is idle
MANAGE_PORT = 65000

# Network Settings
# ----------------
# Address binding settings
# if you want to bind ipv4 and ipv6 please use '::'
# if you want to bind only all of ipv4 please use '<IP_ADDRESS>'
# if you want to bind a specific IP you may use something like '<IP_ADDRESS>'
SS_BIND_IP = '::'
# This default method will be replaced by database record if applicable
SS_METHOD = 'aes-256-cfb'
# Choose whether enforce Shadowsocks One Time Auth (OTA)
# OTA will still be enabled for the client if it sends an AUTH Address type(0x10)
SS_OTA = False   #False #True
# Skip listening these ports
SS_SKIP_PORTS = [80]
# TCP Fastopen (Some OS may not support this, Eg.: Windows)
SS_FASTOPEN = False
# Shadowsocks Time Out
# It should > 180s as some protocol has keep-alive packet of 3 min, Eg.: bt
SS_TIMEOUT = 185

# Firewall Settings
# -----------------
# These settings are to prevent user from abusing your service
SS_FIREWALL_ENABLED = True
# Mode = whitelist or blacklist
SS_FIREWALL_MODE = 'blacklist'
# Member ports should be INTEGERS
# Only Ban these target ports (for blacklist mode)
SS_BAN_PORTS = [22, 23, 25]
# Only Allow these target ports (for whitelist mode)
SS_ALLOW_PORTS = [53, 80, 443, 8080, 8081]
# Trusted users (all target ports will be not be blocked for these users)
SS_FIREWALL_TRUSTED = [443]
# Banned Target IP List
SS_FORBIDDEN_IP = []

# Logging and Debugging Settings
# --------------------------
LOG_ENABLE = True
SS_VERBOSE = False
# Available Log Level: logging.NOTSET|DEBUG|INFO|WARNING|ERROR|CRITICAL
LOG_LEVEL = logging.INFO
LOG_FILE = 'shadowsocks.log'
# The following format is the one suggested for debugging
# LOG_FORMAT = '%(asctime)s %(filename)s[line:%(lineno)d] %(levelname)s %(message)s'
LOG_FORMAT = '%(asctime)s %(levelname)s %(message)s'
LOG_DATE_FORMAT = '%b %d %H:%M:%S'

= =发代码之前能先用三个反引号圈起来么....这被github当作MD处理了
我这从你的配置文件也看不出什么问题，貌似API配置是正确的

@fsgmhoward  试过了
还是显示

Except thrown while pulling user data:No JSON object could be decoded
网页访问：域名/mu/users?key=<API
KEY>  。
显示

{"ret":1,"msg":"ok","data":[{"id":1,"email":"xxx@163.com","passwd":"xxx","t":1473273639,"u":0,"d":839852585,"transfer_enable":107517837312,"port":xxx,"switch":1,"enable":1,"type":1,"last_check_in_time":1472567900,"reg_date":"2016-09-08 02:40:39","invite_num":1,"expire_time":0,"method":"aes-256-cfb","custom_method":1,"custom_rss":1,"protocol":"auth_sha1_v2","protocol_param":"","obfs":"tls1.2_ticket_auth","obfs_param":""}]}

会不会是vps问题。。。

前端是dev版？

@fsgmhoward 是啊  用默认的也这样。。

看上去没有问题，返回的数据也是正确的JSON。你有设置什么防火墙防CC之类的东西么？

@fsgmhoward  木有。。默认开通8000到20000端口号。。。 用lnmp搭建的。。

遇到一样的问题，之前用着好好的，然后我把ss-panel迁移到另外一台服务器，然后在新ss-panel上面创建的账号一个都获取不到，包括管理员账号，但是通过访问http://xxx/mu/users?key= 是能正常获取账号信息的，目前只能通过用数据库方式访问喽。

@xxsxx 我找到了我这边的原因了，是因为我对我的ss-panel在web服务器做了Ip访问限制导致了这个问题，将ip访问限制取消就好了😭
<Directory /opt/lampp/htdocs/ss-panel/public>
       AllowOverride All
       Order Deny,Allow
       Allow From all
       #Deny From all
       #Allow From <IP_ADDRESS>
       #Allow From x.x.x.x
       #Allow From x.x.x.x
    </Directory>

@wonderful60  Deny From all 这个注释掉就可以了吗？  我试试。。

@xxsxx 可以通过这个方法检查是否是IP限制导致无法获取：
在SS服务器上执行curl http://<Your Domain Name>/mu/users?key=<Your API Key>
检查一下返回的信息是否是一个标准的JSON字符串。

@fsgmhoward 我遇到了相同的问题，curl 返回的信息是一个 json 字符串。

我用了百度的免费CDN，连接报错……取消了后就行了....垃圾百度

@wonderful60  大佬 请教一下 这个**<Directory /opt/lampp/htdocs/ss-panel/public>
AllowOverride All
Order Deny,Allow
Allow From all
#Deny From all
#Allow From <IP_ADDRESS>
#Allow From x.x.x.x
#Allow From x.x.x.x
**
在哪儿呢

由于您主站采用了CDN，导致服务端无法正常通过API接口与主站互通。去掉CDN即可解决！
我是这样弄好的...咸鱼一条,爬帖弄好的,啥也不懂,不知道能不能帮到你.
2017-06-28 13:33 GMT+08:00 panjian-win<EMAIL_ADDRESS>
@wonderful60 https://github.com/wonderful60 大佬 请教一下 这个**<Directory
/opt/lampp/htdocs/ss-panel/public>
AllowOverride All
Order Deny,Allow
Allow From all
#Deny From all
#Allow From <IP_ADDRESS>
#Allow From x.x.x.x
#Allow From x.x.x.x
**
在哪儿呢
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsgmhoward/shadowsocks-py-mu/issues/24#issuecomment-311560980,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZYx6OiWstjjc-mSBo1HYPi77-J5iL6Aks5sIeXHgaJpZM4JuqL7
.

@panjian-win 这是我这边用apache做web服务器的配置，里面设置了哪些ip可以访问这个web项目，如果curl没信息返回就查看一下是否web服务器设置的IP策略或者所在服务器是否设置了防火墙策略

通过浏览器直接访问 http://xxx.com/mu/users?key=xxx  出现500 Internal Server Error错误，是什么原因？ 我看了日志，应该是在我重启该服务器之后，从200 OK 变成500 Internal Server Error错误的，是不是哪个进程没拉起来？多谢了。

@kilobps ss-panel的问题请去ss-panel的repo发issue问。
https://github.com/orvice/ss-panel


Detect and download arm64 architecture

Fix install script to support Linux aarch64 and Darwin/MacOS arm64 when detected.
From this stack overflow answer, arm64 and aarch64 are the same thing, just Apple decided to name theirs arm64.
Also, containerd normalizes the names to the same thing in their source code.
Tested:

[x] Linux: Arch x86_64
[x] Linux: Ubuntu Server aarch64 (Raspberry Pi 4)
[x] Darwin: x86_64
[ ] Darwin: arm64

Closes #26


Fixed typos and punctuation

Summary
This PR addresses some typos discovered after I had a read through some of the Voluntary Product Accessibility Template documentation.

Hello @banaboi,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@cwarnermm reverted. Glad I could contribute!

@jamiehurewitz, adding you for review because there are some punctuation changes to this which I'd like to ensure don't change the meaning of the content. :)

Looks good.

Thanks for participating in Hacktoberfest! You can claim your sticker set here: https://get.printfection.com/hacktober21/4144583267 @banaboi


always kill tree

I'm running an app using node-cluster http://learnboost.github.com/cluster/. When I stop this app using forever stop or forever stopall the worker nodes are killed.
This change uses pstree at all places where processes are killed.

any chance this gets in?

@mmalecki @indexzero at https://github.com/nodejitsu/forever/pull/160/files#L0L122 I added a try...catch around the JSON.parse and check for empy data vars...
This was giving us A LOT of SyntaxErrors on our systems...

@mikedeboer This try .. catch is already fixed in my #163.

This looks good. I'm going to cherry-pick the first commit.

cherry-picked in 7ab97bd16b5129ecd8f6f493cfbafee2e4ba1b05

I think that this patch breaks stopAll functionality. Please run vows test/tail-test.js. On current master (with this patch applied) it leaves 2 children behind, even tho stopAll event gets fired. On e4f2b090b9012fe2d4a4b99654852a4581fc2101 (right before this patch), no children are left behind.
Can someone verify that?

The problem here was that since killTree was always enabled and @fjakobs didn't change the iteration in forever.stop and forever.stopall to be async the process was exiting before the children were actually killed.
Fixed in 60a576a58fd68cddddcb280ab8571ec88766dcaa


Building Quality Assistance + Coaching with Levels 1-4

This is a significant reworking to identify the different value I am looking to gain from Quality Coaches contributing from Level 1-4.
How to review

As a quality coach, is this guidance practical and concrete?
Would I be happy holding myself and my teammates to account?
Is the differentiation between L2-4 sensible and align with the principles we used for software-engineers?
Are there any glaring gaps in the value we want from quality coaches?

This is a great write-up ❤ . Thanks a lot of taking time out and putting it together. It will provide a lot of guidance to me and new quality coaches.

I think I've addressed everything including Confluence pages. Good enough to merge?

LGTM 👍


init() entry point lacks 2 parameters. Only 14/16 are defined => error when calling metadata() and other.

When calling the metadata() function an error is raised that says the NFT_METADATA_KIND is not set.
METADATA_MUTABILITY is also not found in storage.
I think I have identified the reason for this issue and will try to resolve it.
The attached screenshots show that the 2 missing parameters are passed to the init() function, but are not defined as parameters for the init() entry point => this explains why they are not set.
I test my fix tomorrow and propose a commit.

Hi @jonas089 thanks for your report.
I believe this has been fixed meanwhile in this commit https://github.com/casper-ecosystem/cep-78-enhanced-nft/commit/f5c93830e75320935ce17b0f5384017191a32396#diff-bb08d6927664d81e3bb0c97846211dc11b8ccd735a98fea518b59ffe397adae7R1396
from this PR https://github.com/casper-ecosystem/cep-78-enhanced-nft/pull/87 adding the missing parameters in init entry point.
Those tests are covering that logic https://github.com/casper-ecosystem/cep-78-enhanced-nft/blob/dev/tests/src/metadata.rs#L222-L364 if you find anything left that I may have missed then please let me know back thanks.


Ability to report posts/replies

[ ] All users should be able to report a post or reply.
[ ] Admins and moderators (after issue #3) should be able to see unhandled reports and act on them.

What should available actions be? Edit and delete good enough?

[ ] Cleanly handle multiple reports
[ ] Keep report history and action taken

Possible enhancement: have the flow separate the concept of "inappropriate" (for admins/moderators) with "enhancement for author" (typos/suggested warnings)

Related: ability to suggest tags for a post.


chore: release v0.0.13

:robot: I have created a release beep boop
0.0.13 (2024-01-14)
What's Changed

fix(ci): vendor openssl to support cross-compilation on CI hosts by @coffeebeats in https://github.com/coffeebeats/gdpack/pull/83
feat(ci/cargo-build): allow passing additional build arguments via extra_args by @coffeebeats in https://github.com/coffeebeats/gdpack/pull/85
fix(cmd): improve command handling and when gdpack triggers a reinstallation of addons by @coffeebeats in https://github.com/coffeebeats/gdpack/pull/86

Full Changelog: https://github.com/coffeebeats/gdpack/compare/v0.0.12...v0.0.13

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/coffeebeats/gdpack/releases/tag/v0.0.13 :sunflower:


Runtime Permission

Thank you this library.
I fixed sample app.

Thanks for the PR, but this functionality has been removed from the library in the 2.0.0 release


Small changes fixing a few bugs

@Bai-Li-NOAA Could you make the changes to the create_template test to fix the issue of failing checks? It has to do with how I have changed the path from the R default to the working directory (or whatever the person has added).

Add test to test file_dir in create_template before merging

@Schiano-NOAA

The failed GHA workflows have been fixed by sorting file names from expect files and created files.
The create_template()-created files will now be automatically removed at the end of the tests using on.exit().
A new test has been added to validate the file_dir() function.

All tests have successfully passed. The changes are ready to be merged into the main branch.


Contact Us page Not working

Contact Us page is not working, it's either doesn't exist or not working,
I'll design the whole contact page and add form functionality as well.

Assign me this issue, also add labels of Hacktoberfest, gssoc-ext, level3

/assign

Contact Us page is not working, it's either doesn't exist or not working, I'll design the whole contact page and add form functionality as well.

Assign me this issue, also add labels of Hacktoberfest, gssoc-ext, level3

It doesn't exists.
and Currently we don't require that page.


Mixed Content in the Changelog theme demo on the Hugo website

Hello @jsnjack   I am one of the maintainers of the Hugo Themes repository.
Your theme's demo causes a  Mixed Content browser warning on the Hugo website because in line 4 of /layouts/partials/head.html there is a reference to an insecure URL. The Hugo website is served under HTTPS.
To fix this warning either change to <link href="https://gmpg.org/xfn/11" rel="profile"> or delete it, if it's no longer needed.
Once you do the above please let me know.
Thanks

Hi @onedrawingperday ! Thank you for reporting it! I have just removed the link


Improvements on Windows setup

fixes #311

@degrammer would love to get your review on this. I moved the environment variable out of the call and it works now for me on my Windows VM.


WebUI start error

Hey so I try running the webUI but i get this error when i try run it and I have tried 3 different times to run it, any help would be amazing
/usr/local/lib/python3.9/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension: libtorch_cuda_cu.so: cannot open shared object file: No such file or directory
warn(f"Failed to load image Python extension: {e}")
[libprotobuf FATAL google/protobuf/stubs/common.cc:83] This program was compiled against version 3.9.2 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.19.6).  Contact the program author for an update.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "bazel-out/k8-opt/bin/tensorflow/core/framework/tensor_shape.pb.cc".)
terminate called after throwing an instance of 'google::protobuf::FatalException'
what():  This program was compiled against version 3.9.2 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.19.6).  Contact the program author for an update.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "bazel-out/k8-opt/bin/tensorflow/core/framework/tensor_shape.pb.cc".)

Uninstall protobuf then re-run the installer:
pip uninstall -y protobuf

thank you so much, last question, will this work in google colab?

thank you so much, last question, will this work in google colab?

There's a lot of options for Colab, try https://github.com/TheLastBen/fast-stable-diffusion


RuntimeJobFailureError with ECR instruction on IBMQBackends (Eagle Processors)

Encountered a RuntimeJobFailureError related to the ECR instruction on various Eagle processor IBMQBackends using pytket-qiskit versions 0.41.0, 0.43.0, and 0.42.0. The error does not manifest with IBMQEmulatorBackend.
Example error message for backend = IBMQBackend("ibm_nazca")
RuntimeJobFailureError: 'Unable to retrieve job result. INSTRUCTION NOT IN BASIS GATES: INSTRUCTION: ECR, QUBITS: [2, 1], PARAMS: []

I looked into this a bit yesterday. I'm not whether its an issue with pytket-qiskit or on the IBM side.
from pytket import Circuit
from pytket.extensions.qiskit import IBMQEmulatorBackend
backend = IBMQEmulatorBackend("ibm_nazca")
circ = Circuit(3, 3)
circ.X(1).CZ(0, 1).CX(1, 2).measure_all()
circ = backend.get_compiled_circuit(circ)
handle = backend.process_circuit(circ, n_shots=1000)
# assert backend.persistent_handles
print(str(handle))
counts = backend.get_result(handle).get_counts()
print(counts)

This works fine on the IBMQEmulatorBackend as was pointed out above. However if I use IBMQBackend I get a RuntimeJobFailureError as above which is puzzling.
Nasca uses the new IBM gateset of {X, SX, Rz, ECR} which I added support for in pytket-qiskit in version 0.40.0.
Whats weird is that the circuit seems to be valid in the sense that it satisfies the gateset and connectivtity constraints but fails upon execution with the RuntimeJobFailureError.
For the circuit above I can check validity with IBMQBackend.valid_circuit and it seems to be fine. Compilation to the {X, SX, Rz, ECR} gateset is tested on CI here but we don't run any jobs.
I also get a similar issue with the Cusco device which also uses {X, SX, Rz, ECR}.

Works for me now too :) Looks like you were right and it was a temporary issue on the IBM side.
Glad to hear it isn't a bug in our IBM backend code

Works for me now too, thank you!

Works for me now too, thank you!


Added Random support, cleaned up Test console

Cleaned up the Test console to be more friendly for developer testing
(added menu, etc).
Added support to get random post.
Only one piece of code makes me uncomfortable, and would like input if you have any. The /random.json endpoint appears to be the first Non-Listing endpoint being called, and the results are returned as a json Array of Listing objects. I don't know if we want to change the architecture (it would be significant) to identify what the expected type of return would be for the Listing.WebAgent.GetResponseString, or, if you already have a more succinct way to do it in your codebase which I'm not familiar with, OR, if it's fine like it is right now and in a few years someone else will deal with it ;)

If I'm seeing this correctly, calling /random.json results in the same json as calling .json on any given post. As in, they all return an array containing a listing. Were you running into an error just deserializing it as a Post?

Let me take a look - like I said, I didn't study the whole API, probably just missed something.

Have you had a chance to look in to this again?

I looked a little more when you gave me the suggestion to init a Post instead of a listing but didn't get it working.
Maybe I'll pick it up again in a few days, or maybe you can give me a little more information about the Post structure, and how to init one independently.

/random may return the / listing if there are no "fresh enough".

Going to go ahead and close this. Someone else feel free to look into this again.


Cannot add multiple categories

This is happening on a production wiki.
https://github.com/user-attachments/assets/f14956e4-78c4-41ab-bb7b-091dacbc86f6

This is also not working locally. But more specifically, it looks like it does not work when there are multiple users:
Screencast_20240806_111229.webm

This is also not working locally. More specifically, I cannot add multiple categories for more users when there are multiple users.
https://github.com/user-attachments/assets/a64b34e9-a898-4bf2-a361-52f1f061643b

weird bug. I just added 2nd category to my user on production, but indeed, I cannot add a second one to the other users.


Automator: update proxy@master in istio/istio@master

Generated by Automator - 2020-09-17T21:19:12+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
448f48179e84cd14d78c665d49dbb36e3d391fd5
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
448f48179e84cd14d78c665d49dbb36e3d391fd5
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
d6615fce83167f41b58c868fe391b9df3a044b5f
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
d6615fce83167f41b58c868fe391b9df3a044b5f
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
d6615fce83167f41b58c868fe391b9df3a044b5f
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
d6615fce83167f41b58c868fe391b9df3a044b5f
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
304373684d2d6b38fe96e1270ab614db63940aae
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
304373684d2d6b38fe96e1270ab614db63940aae
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
304373684d2d6b38fe96e1270ab614db63940aae
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
4d21c3c58b113dbf9d5a85e42921435b029eb71a
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Fixed ability to skip CSRF filtering through configuration

The previous implementation tried to read a string, not a string array. Apache Commons Configuration's behaviour when asking for a string in what essentially is an array defaults to returning the first element of the array.

Looks good to me. Can you please open a JIRA for this ?


ci: release trigger

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


.travis.yml: remove 10.9

@jawshooah Any issue with removing this? It’s the one that most often fails, and for dumb reasons like not being able to get bundler.
We mention somewhere in the documentation we try to support the current OS X version and the previous one, so removing this would keep in line with that.

ACK :+1:

Want to go ahead with the removal? I don't see any particular problems.
That being said, I noticed fewer 10.9 failures recently, so maybe Travis fixed issues on their end?

That being said, I noticed fewer 10.9 failures recently, so maybe Travis fixed issues on their end?

It seems some days are worse than others. There was a bad day recently. Let’s go ahead and merge, yes.


grpc: fix cross

Motivation for this change
I couldn't find any alternative to setting _gRPC_PROTOBUF_PROTOC_EXECUTABLE. protobuf.cmake uses find_program when cross-compiling, which finds the host platform's protoc instead of the build platform's.  I even tried giving protobuf multiple outputs and not including the one with the binary in buildInputs, but it didn't help.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

pkgsCross.aarch64-multiplatform.grpc builds for me


compatibility with tensor rt8

thanks for such a efficient work but when I run on my system ;
Nvidia Xavier AGX
Jetpack 4.6
Cuda 10.2
Tensor rt8
It throws out error as below

Any idea to fix it?

Hi @tlgkyn06,
May I know how you ended up solving this issue? Thanks. =

@derektan95  converting codes scripts are old for trt8 use newer scripts like : https://github.com/jkjung-avt/tensorrt_demos/tree/master/yolo


force_2d documentation

https://github.com/shapely/shapely/blob/7d068a50f3aacc81c41b9a2a48d3a6a1cd24cdb0/shapely/_geometry.py#L817
Seems to me from shapely import force_2d is missing from the force_2d() example => https://shapely.readthedocs.io/en/stable/reference/shapely.force_2d.html

@esgn thanks for the report. This is indeed missing, but that's actually the case in almost all our docstrings. We started writing docstrings with never importing the function itself, and importing other things.
Now, that is potentially confusing and also makes you can't simply copy-paste the example and run it in a terminal. So I think it would be better practice to always import it as well (or use it as shapely.<func>, and assume that shapely would already be imported).


Health Check PoC

This my first pass at a health check. I thought about re-using an existing tokio Core, but if we use tokio-pool (or something like it) then we have a Core per thread. I don't see how we can get away with not having a dedicated thread to do health checks.
We may need to introduce some basic configuration at this point so the uri path for the health check is not hard-coded. I have to think about that a bit too.

I am looking at storing a Server object in the pool. This will allow us to keep track of states, such as Active, Down, etc. This will allow the health check to keep checking a down server. It should also allow me to record some stats on the server too. I am working out the borrow details. For example: how does a normal request borrow a Server from the pool, make a request and increment some stat counters while other threads may be asking for the same Server. Especially when the health check thread wants to mark it Down.

Yes, I had the same idea. I was thinking if we should store the information from the user (Server config) and the runtime information at different places or in a mutable structure.
I was working on secure connection to backends, and I also need more information (https vs http). And we will need more information in the future (health check config, routing?)

The health checks are working, but naive. They always check / every 1 seconds and will remove the server if a check fails. I want to do more, but I realized that Pool is the wrong abstraction. Currently, we get a Server from the Pool. This causes a lot of problems with Rust's ownership model. Instead, we should be passing the request into the Pool. This would hide the logic of how a Server is chosen, make sure the same Server is used for pipelined requests, centralize the place where stats will be counted and enforce the health checks.
As that is a pretty big change, I do not want to hold this up. This one of the last item for a 0.1 release.


spike: investigate Caddy as a service

Caddy is now very close to default.  We should now be able to provide a basic Caddyfile that works with an already built Caddy container to provide a rough approximation of a service.  CaaS!  ;)

The level of abstraction required isn't worth the hassle.  We have a very reasonable Dockerfile that's pretty easy to adapt.  Good enough!


106 update readme and documentation

updated documentation and readme for more exhaustive method descriptions

Codecov Report

Merging #107 (a170e15) into main (3bf4b9a) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main     #107   +/-   ##
=======================================
  Coverage   97.77%   97.77%
=======================================
  Files          30       30
  Lines        6012     6012
=======================================
  Hits         5878     5878
  Misses        134      134

Files Changed
Coverage Δ

src/traits/container/container.rs
90.21% <ø> (ø)

src/traits/interval/coordinates.rs
96.77% <ø> (ø)


Show issue in Changelog

Should add PR link to commits - should be supported in conventional-commits (https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog/CHANGELOG.md)
Action code is here - https://github.com/taskany-inc/release/blob/main/index.js


Curies

I've been looking around and there doesn't seem to be much support for "curies" in this project.
At first I thought it would be OK to just create a new Link with rel "curies" and then the rest of the info, but it turns out that the reserved "curies" rel is meant to be an array / collection of elements instead of a single link.
Have I missed a way to specify curies? And if not: would you be interested (short-term) in a PR?

Ok, I just realized: you can add multiple links to the same "rel" and it will automatically create a collection.
The thing is that the "curies" rel is always meant to be a "set of links", based on the [formal specification|https://tools.ietf.org/html/draft-kelly-json-hal-07#section-8.2].

Closing in favor of https://github.com/zfcampus/zf-hal/pull/163


Results page supports Hepatitis-C test results

Why should we do this?

(current experience) The Test Results screen in SimpleReport does not display Hepatitis-C results, leading to an incomplete representation of test data for users.
(why we want to make this change) By adding support for Hepatitis-C results on the Test Results screen, we can provide a comprehensive view of all test data, including Hepatitis-C, allowing users to access and review Hepatitis-C test results alongside other test results.

User story
As a SimpleReport user, I want to view Hepatitis-C test results on the Test Results screen so that I can easily access and review Hepatitis-C test data alongside other test results for accurate patient monitoring and management.
Action Requested
Update the components on the Test Results screen to include support for displaying syphilis results.  This includes:

adding Hepatitis-C as a selectable condition in the Condition filter
including a Hepatitis-C column in the "Download results" spreadsheet
showing Hepatitis-C on the printed page for "Print details,"
displaying Hepatitis-C information on the modal for "View details."
ensure that Hepatitis-C is supported for emailing and texting results.

Treat Hepatitis-C in the same manner as HIV and Syphilis - if the result is positive/reactive, then AOE questions are required.

for syphilis, these are the required fields for positive result: gendersOfSexualPartners, pregnant, syphilisHistory, symptomaticForDisease

Acceptance Criteria
Review

[ ] Reviewed with design and/or design lead
[ ] Reviewed with content strategist for final approval
[ ] Reviewed with product and engineering

Additional Context

Concern that this might also complete #7441.  Note to verify if thats the case


Update - refactor telemetry tracking logic in oss

Description
This PR refactors the telemetry tracking logic in OSS.
Related Issue
Closes #199_ag-cloud

@devgenix can you please test the implementation (serve from cli (current version) then use in web cloud version to check for any bugs). Thank you!

Thanks for the quick PR @aybruhm ! Code wise, I approve it. However, there are failing tests. Can you please look into this.

@mmabrouk, the failed frontend tests are a result of our OpenAI quota.

@devgenix please see above

@devgenix can you look more into this?!
What's the container outputs? Who is calling this module error? ...

@devgenix can you look more into this?! What's the container outputs? Who is calling this module error? Does this happen when you checkout your main?...

I just checked out main and it's happening there too.

@devgenix and?


GraphOutput when you enter a SubGraph is mispositioned

It doing that thing

Caused by canvas.bgcanvas.width being miscalculated as per lgraphcanvas.js drawSubgraphPanelRight()


Easier Word List for the Default Game

The problem
Words like the following, which are currently part of the game, are not in a lot of native speakers' active or even perhaps passive vocabulary, so the game may not be so fun, and would be particularly difficult for children and those speaking English as a non-native language.
aahed, aalii, aargh, abaca, abaci, aback, abaft, abaka, abamp,, abaya, abbas, abbes, abele, ables, abmho, abohm, aboil, aboma, aboon, abris, abuts, ...
A possible solution
To keep this more game-like, with more successes, limit the words to higher-frequency words.
A possible list
Here is a possible list of words.
Though a much lower number of words, there should still be enough words to make it challenging and fun.
I choose these words from the headwords of the NGSL. (http://www.newgeneralservicelist.org/)
This list could be expanded by adding the other words in the same "word family" for each of these.
File 1: 468 words - All are headwords from the NGSL
File 2: 603 words - An additional list with some words in the same word families.  Note that this would need to be cleaned up a bit because it contains items such as weren (from weren't), haven (from haven't), and maybe more.
NGSL 5-letter words.zip

@ckjpn

aahed, aalii, aargh, abaca, abaci, aback, abaft, abaka, abamp,, abaya, abbas, abbes, abele, ables, abmho, abohm, aboil, aboma, aboon, abris, abuts, ...

none of those words are in the answer list.
That list has already been manually filtered down to common words. If there are specific words from that list that you think should be removed, you can open an issue or PR.

Sorry, I misunderstood the code.
I think I got it working OK on my one website now, limited to the first 250 five-letter words on the NGSL.
http://www.manythings.org/wm/
I misunderstood the words at Se = { ....
And, now realize it's the we = [ ... words that are the answers.
Thanks for making this open source and using teh MIT license.

Here are a couple of other levels.
http://www.manythings.org/wm2/
Limited to 134 5-letter words found on a Junior High School word list. (What Japanese JHS students learn.)
http://www.manythings.org/wm3/
594 five-letter words from NGSL, including some of related words in the word families.
Once you've seen these, please delete this message and the earlier one with my URL, since I'm not sure if I should really make them publicly available yet.
Instead of this way of doing it, it would likely be better to have the different levels in their own external .js files and load in the different levels that way.  I don't have time to look into that now.
Thanks once again.


Add support for strikethrough

I realize this library is primarily meant for internal use at GitHub, but it's come in handy on a project I'm working on. I would really like love to see support for strikethrough formatting, though! 😉
This PR:

Updates src/index.ts to add support for md-strikethrough.
Updates examples/index.html to add strikethrough to the example toolbars.
Updates test/test.js accordingly.

@keithamus @koddsson Is there anything you need from me before this is merged? I don't mean to be a nuisance, just would really like to see these changes included in a release. 😃 Thanks again.

Sorry about the delay @mattmikolay. I'll merge and release now :tada:

Released as 1.4.0


[Feature] : Introduction to shipyard

Describe the feature you'd like to request
Shipyard is the place to collaborate and ship dope stuff together.
Describe the solution you'd like
Create a component/section highlighting the fosscu shipyard. Also include the details about the already shipped project
Describe alternatives you've considered
No response
Additional context
No response

@codecShivam I would like to work on this issue
Where can I get the details of the shipped products

@codecShivam I would like to work on this issue Where can I get the details of the shipped products

Go ahead!

@codecShivam I would like to work on this issue Where can I get the details of the shipped products

@piyusesh has already opened a pull request related to this issue, #241.

fixed in #241, thanks @piyusesh


fix: correct event details type, include provider name

We made this change in the spec: https://openfeature.dev/specification/sections/events#requirement-523
But neglected to update it in "types"... it's already implemented in most SDKs.

Merging since this is small, and a bug (inconsistency).


Cannot install MEGA files.

i wish i have time to fix every bug this extension has currently. maybe one day.


Flesh out the Schema AST

The constructors for schemas aren't implemented yet (see this definition for example).
We'll probably need more constructors like the one already defined (for records fields at least).
Also, the monocle dependencies (for things like Getter, Optional and so on) isn't defined yet, it needs to be added to the build.sbt

I'd like to take this one.

As said in #14, we'll keep this issue open until we have tests for it

Tests have been added by #15


libngspice is not built for darwin

Describe the bug
libngspice is currently not built on darwin
this prevents kicad from being built on darwin (official builds of kicad for MacOS are available)
libngspice appears to support darwin
To Reproduce
Steps to reproduce the behavior:
0. on darwin, nix-build '<nixpkgs>' -A libngspice
Expected behavior
libngspice to build on darwin and be usable by kicad there
Additional context
i maintain the kicad package and already tried pinging the libngspice maintainer
Notify maintainers
@bgamari if you already investigated after the kicad PR ping, nothing relevant changed since.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: libngspice
# a list of nixos modules affected by the problem
module:

addressed by https://github.com/NixOS/nixpkgs/pull/95513


chore: remove recompose and symbol-observable

looks like we only had direct dependencies on them to express some types - which
typescript can do even better without us explicitly casting stuff.

does not work. @dcos/data-service does need this while not specifying it a dependency 🤔


Frends.Salesforce.ExecuteQuery

Task for executing of Salesforce queries.
Ask Jefim for concrete example for doing this, no need to go through SF docs - we already have an implementation in subprocess form.
Task parameters:

Username/password/security token for authentication
Use test login or normal login (different URLs on SF side for sandbox environments)
Query itself

Task output:

The content of HTTP response Body.records as array (in jtoken form).

Other:

Lets aim for automated tests and having integration tests automated
No performance tests needed, SF is the main bottleneck
For authentication - would be nice to cache the bearer token for any additional use

Initial implementation of the task completed.


Fix Manifest race condition

The anonymous function spawned in ElixirLS.LanguageServer.Dialyzer.Manifest
was not guaranteed to stop before it's parent (ElixirLS.LanguageServer.Server).
In the tests this would manifest itself as an occasion error when the Manifest
spawned process would try to read from an ETS table owned by the server after
the server was already dead which resulted in an ArgumentError. An example of
this error occurring can be found at:
https://travis-ci.org/elixir-lsp/elixir-ls/jobs/612862401
By changing the spawn_link to a Task.start_link we ensure that the spawned
process (now a task) is properly supervised and is brought down before its
parent is, thus eliminating the race condition with the ETS table ownership.

While this is still a good change, this may have not actually fixed the race condition. Occasionally while running the tests I'll still see an error like:
07:42:28.667 [error] Task #PID<0.728.0> started from #PID<0.438.0> terminating
** (ArgumentError) argument error
    (stdlib) :ets.select_trap({#Reference<0.961851318.3211919361.122260>, 7003, 0, #Reference<0.961851318.3211919365.119819>, [{{:hipe_x86_registers, :is_precoloured, 1}, {{:c, :atom, [false, true], :unknown}, [:any]}}, {{:digraph_utils, :subgraph, 2}, {{:c, :opaque, [{:opaque, :digraph, :graph, [], {:c, :tuple, [{:c, :atom, [:digraph], :unknown}, {:c, :union, [{:c, :atom, :any, :unknown}, :none, :none, :none, :none, :none, :none, :none, {:c, :opaque, [{:opaque, :ets, :tid, [], {:c, :identifier, [:reference], :unknown}}], :unknown}, :none], :unknown}, {:c, :union, [{:c, :atom, :any, :unknown}, :none, :none, :none, :none, :none, :none, :none, {:c, :opaque, [{:opaque, :ets, :tid, [], {:c, :identifier, [:reference], :unknown}}], :unknown}, :none], :unknown}, {:c, :union, [{:c, :atom, :any, :unknown}, :none, :none, :none, :none, :none, :none, :none, {:c, :opaque, [{:opaque, :ets, :tid, [], {:c, :identifier, [...], ...}}], :unknown}, :none], :unknown}, {:c, :atom, [false, true], :unknown}], {5, {:c, :atom, [:digraph], :unknown}}}}], :unknown}, [:any, {:c, :list, [:any, {:c, nil, [], :unknown}], :unknown}]}},
<snip>
:elixir_code_server, :call, 1}, {:any, [...]}}, {{String.Unicode, :split_at, ...}, {{...}, ...}}, {{:cerl_sets, ...}, {...}}, {{...}, ...}, {...}, ...], 4000})
    (stdlib) ets.erl:736: :ets.tab2list/1
    (language_server) lib/language_server/dialyzer/manifest.ex:43: anonymous fn/6 in ElixirLS.LanguageServer.Dialyzer.Manifest.write/6
    (elixir) lib/task/supervised.ex:89: Task.Supervised.do_apply/2
    (stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3
Function: #Function<7.78335674/0 in ElixirLS.LanguageServer.Dialyzer.Manifest.write/6>
    Args: []


Update bundled gems

TODO: protocol-http1 1.15.1 is not picked up yet. :thinking:

TODO: protocol-http1 1.15.1 is not picked up yet. thinking

Fixed.


pageSize is not available from TS

Docs contains information about pageSize property and I may see it from debugger.
However It is not available from TS.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9d40f22d-3206-3b47-5cbe-0e557fa0bd07
Version Independent ID: 1d5b0fbd-9b5d-d605-6553-138d0f7e2316
Content: Paging - Power Apps
Content Source: powerapps-docs/developer/component-framework/reference/paging.md
Service: powerapps
GitHub Login: @Nkrb
Microsoft Alias: nabuthuk

Thanks for the feedback. Please raise the issue in the community forum. Our developers will help you resolve the issue. Closing the issue.


SmtpMessageSender is not using injected SmtpClientFactory

As requested I opened a separate issue for my findings that the SmtpClientFactory was creating a new SmtpClient by invoking the SmtpClient constructor directly instead of using the injected factory.

I'm preparing a pull request to solve this.


[graph] improve the graph building.

remove graph-related logic in torch function ops. Use a decorator @register_colo_graph to build the DNN compute graph.
`


vr-bgp: separate afi argument for announce?

Received prefixes are kept in a data structure that is keyed on AFI / SAFI so it's easy to see what is announced as ipv4 unicast NLRI etc. Should we make the AFI explicit when announcing? Right now I guess ExaBGP looks at the prefix and places it in the right AFI / SAFI automagically..

I don't think the ExaBGP API supports specifying AFI/SAFI right now. Reading https://github.com/Exa-Networks/exabgp/wiki/Controlling-ExaBGP-:-interacting-from-the-API is says "when announce   is introduced"...
We explicitly negotiate the correct AFI/SAFI per neighbor, i.e. the IPv4 TCP session will only carry BGP ipv4 unicast NLRI information and vice versa for IPv6 so there's no real point in forcing the user to specify it other than it in general is good to be explicit.
Since things are working for now and I don't see a risk of it stopping working I'm just going to close this.


Firebase adapter

Type of change
New feature
Description
An adapter to work with firebase. A single firebase project can be used with many projects. We are working on a feature to deploy assets to firestore storage.

Thanks for the PR, looks great!
Would you mind reverting your changes to the README? Can then add Firebase docs to the main docs repo

@bedeoverend do we need to finalise (and document, but at least finalise) adapter interface, before merging this? In case of breaking changes

@seaneking I am with you. I think its better to finalise adapter interface. If all the adapters are merged, it might increase the size of js. Better finalise the architecture. Also working on deploy to firebase with functions and SEO. Might as well not need github to store data. We can store that json in realtime database. @bedeoverend will update the docs.

I did write an initial Readme - https://github.com/heresy/simpla Sorry that I changed the README. We might have to revert it back to original and append this to it. I will do that.

If I may also suggest, can we split this to different packages ? I can write the storage functionality and https(using their socket instead of the rest API) library for firebase. People can install saying @simpla/firebase-auth @simpla/netlify @simpla/firebase-hosting or @simpla/github-hosting

Happy to wait until we’ve finalized adapter architecture, though I’m not too concerned about breaking changes while the adapters are about of Simpla’s core. On that point, once we do settle up on architecture, anyone can create a package outside of core. Unless we do a mono repo, @seaneking thoughts?
Also FWIW definitely worth thinking about storage adapter, not just authentication - agree it’d be great to add firebase storage!

Also with Christmas and New Years probably  won’t have time to look at this until mid Jan

Just re: docs - sorry if it wasn't clear, but we're not using the README here for documentation (the snippet with Netlify is just an example to give people a glimpse of Simpla). We'll need a PR with a guide and API reference in Simpla's docs. Use SimplaNetlify adapter docs as a template.
And yep as @bedeoverend touched on, we'll be soon opening up the storage interface as well (#77), at which point you could make a seperate Firebase adapter for that. Haven't settled on a naming convention yet, but I'd guess something like FirebaseAuth and FirebaseStorage for them.

If I may also suggest, can we split this to different packages ? I can write the storage functionality and https(using their socket instead of the rest API) library for firebase

Missed this comment before - we did consider making all adapters separate packages, but in the end decided it was too much overhead for no real gain. Bundling adapters doesn't add any weight for the user, since they only pull in what they need, and makes maintenance much easier.
That said you're more than welcome to turn this into your own package rather than a PR against the core lib. At some point we'll probably put up a list somewhere of community adapters as well as the 'official' bundled ones.

Made this a package - https://github.com/heresy/simpla-firebase-auth . I guess we can close this PR. @seaneking

:+1: Let us know if you'd like to make it part of the core bundle, we'd be happy to help maintain it if it was.

Also feel free to make a PR against docs for your adapter (for discoverability), can make an official/community distinction there.

Its just one function and file. We can do as you please. I will write update the doc.