Not enough values to unpack

I'm getting an error shown below
| WARNING: 119934 samples have invalid sizes and will be skipped, max_positions=1024, first few sample ids=[92711, 1032347, 174715, 403967, 143104, 1268626, 797114, 206659, 1088957, 753465]
| WARNING: ran out of memory with exception: CUDA out of memory. Tried to allocate 3.07 GiB (GPU 0; 31.72 GiB total capacity; 29.28 GiB already allocated; 767.56 MiB free; 556.92 MiB cached);
 Skipping batch
| WARNING: ran out of memory with exception: CUDA out of memory. Tried to allocate 2.86 GiB (GPU 0; 31.72 GiB total capacity; 26.41 GiB already allocated; 2.17 GiB free; 1.99 GiB cached);
 Skipping batch
| WARNING: ran out of memory with exception: CUDA out of memory. Tried to allocate 2.96 GiB (GPU 0; 31.72 GiB total capacity; 24.85 GiB already allocated; 1.82 GiB free; 3.90 GiB cached);
 Skipping batch
pcn-7-02:343884:343884 [2] NCCL INFO AllReduce: opCount 2 sendbuff 0x2aabca255400 recvbuff 0x2aabca255400 count 65536 datatype 1 op 0 root 0 comm 0x2aabcc001af0 [nranks=4] stream 0x25e0960
pcn-7-02:343882:343882 [0] NCCL INFO AllReduce: opCount 2 sendbuff 0x2aabce297a00 recvbuff 0x2aabce297a00 count 65536 datatype 1 op 0 root 0 comm 0x2aabd4001af0 [nranks=4] stream 0x25e16d0
Traceback (most recent call last):
  File "/home/jmorton/venvs/roberta/bin/fairseq-train", line 10, in <module>
    sys.exit(cli_main())
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/fairseq_cli/train.py", line 317, in cli_main
    nprocs=args.distributed_world_size,
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/torch/multiprocessing/spawn.py", line 171, in spawn
    while not spawn_context.join():
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/torch/multiprocessing/spawn.py", line 118, in join
    raise Exception(msg)
Exception:

-- Process 3 terminated with the following error:
Traceback (most recent call last):
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/torch/multiprocessing/spawn.py", line 19, in _wrap
    fn(i, *args)
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/fairseq_cli/train.py", line 284, in distributed_main
    main(args, init_distributed=True)
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/fairseq_cli/train.py", line 80, in main
    train(args, trainer, task, epoch_itr)
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/fairseq_cli/train.py", line 121, in train
    log_output = trainer.train_step(samples)
  File "/home/jmorton/venvs/roberta/lib/python3.6/site-packages/fairseq/trainer.py", line 305, in train_step
    [logging_outputs, sample_sizes, ooms, self._prev_grad_norm],
ValueError: not enough values to unpack (expected 4, got 2)

The memory issue, is one problem - but I'm not sure why the ValueError is being thrown.
  Going to close this issue for now, and reopen if I'm able to reproduce this problem.


Trying to add a matrix blog to a sprig component

Question
Need a hand. Trying to add a matrix block ids as variable to a component. Keep running into Key "id" for array with keys "0,1,2,3" does not exist errors.
{# most requested #}
{% set element = craft.entries().type('serviceLocations').one() %}
{% set blocks = element.serviceLocations.orderBy('RAND()').limit(4).all() %}
{% if blocks|length %}

{# component: large screen #}

    {{ sprig('_components/sprig/sprig-most-requested', {'blocksId': blocks.id}) }}

{# component: small screen #}

    ...

{% endif %}

{# component _components/sprig/sprig-most-requested #}
{% for block in blocksId %}

         {% for row in block.listOfServicesKeywords %}

{{ row.keywords }}

         {% endfor %}

{% endfor %}

In the code above, blocks is an array of matrix blocks, so you cannot call .id on it.
Is there a reason you need two components here? If it was me, I would put all of your code into a single component and make life easy for yourself.

Avoiding duplicate queries. I'm using one component for small screen sizes and the other one for bigger screens. Just using CSS to hide and show, but the result of this approach is that I got duplicate queries, raising the load times.

Duplicate queries can be easily avoided by storing the query result in a variable. For example:
{% set entries = craft.entries.section('handle').all() %}

{# component: large screen #}

    {# Use `entries` #}

{# component: small screen #}

    {# Use `entries` #}

Didn't think about that solution. Solved!


Make failure messaging a bit more friendly

Replaces 👎 with ⚠ for failures and 👎 with 🕐 for a "waiting" message

❤ this is great


Start breaking out code into functions for the keyboard handling - still WIP

Need to consider writing tests for the new functions.

Codecov Report

Merging #20 (06a5a29) into main (de40626) will decrease coverage by 5.70%.
The diff coverage is 15.09%.

@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   99.59%   93.90%   -5.70%
==========================================
  Files          14       14
  Lines         734      787      +53
  Branches      104      113       +9
==========================================
+ Hits          731      739       +8
- Misses          1       46      +45
  Partials        2        2

Impacted Files
Coverage Δ

python3/gameoflife/main.py
67.78% <15.09%> (-29.09%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Support TS 4.7 instantiation expressions

TS 4.7.0 (currently in beta) will bring in "Instantiation Expressions" (see https://github.com/microsoft/TypeScript/pull/47607).
Essentially this means that you can write things like:
function foo<T>(val: T) {}
type Foo<T> = typeof foo<T>
// type Foo<T> = (val: T) => void

The application for Zod schemas is as detailed here (https://github.com/microsoft/TypeScript/issues/40542), in particular that we can now write such things as:
// the dateSchema param could be a schema for an ISO 8601 string or a Date object, or even some custom date-like type
const fooSchema = <T>(dateSchema: z.ZodSchema<T>) => z.object({
  name: z.string(),
  date: dateSchema
})
type Foo<T> = z.infer<ReturnType<(typeof fooSchema)<T>>>
// expected result: type Foo<T> = { name: string, date: T }

Unfortunately this does not "Just Work" by upgrading to TS 4.7.0-beta:
import { z } from "zod";

function genericFooSchema<T>(inner: z.Schema<T>) {
  return z.object({
    type: z.literal("foo"),
    inner,
  });
}

type Foo<T> = z.infer<ReturnType<typeof genericFooSchema<T>>>;

function useAFoo<T>(foo: Foo<T>): string {
  switch (foo.type) {
    // Hovering over foo.type gives:
    // ```
    // (property) type: z.objectUtil.addQuestionMarks<{
    //     type: "foo";
    //     inner: T;
    // }>["type"]
    // ```

    case "foo":
      return "TS should infer that this switch is exhaustive";
  }
}

Related: https://github.com/colinhacks/zod/issues/153

bump

Hey guys, why is this issue closed?

@dilame as you can see, it is closed because @stale decided to close it and nobody cared enough to bump


Removing unused option checkDelay

checkDelay and related timer are not used anymore.
It has been replaced by isBuildFinished sync method:
https://github.com/tes/bosco/blob/master/src/ExternalBuilders/SpawnWatch.js#L47-L62

Coverage decreased (-0.05%) to 21.443% when pulling e7faddc2a4d4faf96b6e4602320ca0bd479c7ee6 on checkdelay-cleanup into 1aa0aea1e3ab1894a2bd233b3b324b903435031f on master.


Redid some tests and update DG

Codecov Report

Merging #243 (87daa52) into master (3f090c8) will decrease coverage by 0.03%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##             master     #243      +/-   ##
============================================
- Coverage     65.02%   64.99%   -0.04%
- Complexity      844      845       +1
============================================
  Files           137      137
  Lines          3122     3122
  Branches        413      413
============================================
- Hits           2030     2029       -1
- Misses          951      952       +1
  Partials        141      141

Impacted Files
Coverage Δ

...main/java/seedu/address/model/student/Student.java
81.44% <ø> (ø)

...c/main/java/seedu/address/ui/StudentValuesBox.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
67.34% <100.00%> (ø)

...n/java/seedu/address/model/student/Attendance.java
75.00% <100.00%> (ø)

...ava/seedu/address/model/student/Participation.java
80.00% <100.00%> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
9.75% <0.00%> (-2.44%)
:arrow_down:

Continue to review full report at Codecov.

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


totalCount on relatedConnection not fetched when part of a fragment

I'm experiencing an issue upgrading plugin-prisma above v3.30.0. I have a relatedConnection with the totalCount option set to true. My query which includes the totalCount field previously worked but is now failing with "Cannot return null for non-nullable field".
I had a play around and realised the totalCount field is included in the query as part of a fragment, like this:
{
  viewer {
    todos {
      edges {
        node {
          id
        }
      }
      ...TodoFooterFragment
    }
  }
}

fragment TodoFooterFragment on UserTodosConnection {
  totalCount
  completedCount
}

If I include it as part of the query directly it works.
Digging around I think the issue may lie here:
https://github.com/hayes/pothos/blob/main/packages/plugin-prisma/src/prisma-field-builder.ts#L267
It seems getSelection(['totalCount']) is returning null when totalCount is not included in the query directly.
Really appreciate your work on a great library, thank you!

Thanks for reporting this.  Just pushed a fix, should be published in a few minutes

Wow that was fast, working great now. Thank you!


Only redraw after zooming is finished (bug 1661253)

Right now, the visible pages are redrawn for each scale change. Consequently, zooming with mouse wheel or in pinching can be pretty janky (even on a desktop machine but with a hdpi screen). So the main idea in this patch is to draw the visible pages only once zooming is finished.

I'm not sure how I feel about it, and it's not really a complete patch yet, but we might be able work-around #15812 (comment) with something along the following lines[1]: master...Snuffleupagus:pdf.js:cancel-extraDelay
[1] Where we e.g. use the postpone-parameter as an argument when calling paintTask.cancel() in the PDFPageView code.

After having thought about that, my feeling is that your patch is not that bad.
Right now, once zooming is finished we almost wait for 100ms to to continue or really cancel the getOperatorList thing because we expect that a draw could happen just once the zooming is finished.
So I'd say that we should delay the cancellation by AppOptions.get("defaultZoomDelay") + 100ms maybe.
In reading your comment here:
https://github.com/mozilla/pdf.js/pull/11106#issue-486803248
I think it makes sense to have two distinct values w.r.t scrolling/zooming.

It sounds like you're suggesting that the RenderTask.cancel-method, in the official API, should just accept a custom extra-delay. If so that feels like it could be a pretty big foot-gun, given the things that third-party users sometimes do, and we'd probably need to place an upper limit to prevent things from breaking; so how about the updated patch?
master...Snuffleupagus:pdf.js:cancel-extraDelay

Could we just immediately cancel when we're scrolling and just have this computed delay when zooming/rotating ?
When scrolling is there any advantages to not cancel right  now ?
I'm thinking about my own usage of the pdf viewer on my phone, and sometimes I quickly scroll the pdf to go to the page I'm looking for and in such a case I've the feeling that this delay would be a penalty.
About zooming, what do you think about postponing the cancel only when we've one page to render ? I'm wondering if it could be a penalty in general to postpone with several rendering pages.
That said, these different points could be addressed or not, in some follow-ups.
And your patch looks good for me.

Could we just immediately cancel when we're scrolling and just have this computed delay when zooming/rotating ?
When scrolling is there any advantages to not cancel right now ?

Yes, if you quickly change scroll direction it may still make sense to slightly delay cancelling. E.g. consider a case where you scroll just past the page(s) you wanted to see and then scroll back quickly.

About zooming, what do you think about postponing the cancel only when we've one page to render ? I'm wondering if it could be a penalty in general to postpone with several rendering pages.

I'm not sure how much of a problem that is, and anyway if there's multiple visible (or even cached) pages we really don't want to cancel their worker-thread parsing right away since that could easily regress performance (and it's somewhat difficult to imagine every possible edge-case here).
In general, I very much prefer that we don't complicate the API side of things (or even the viewer) too much regarding the cancelling. Especially given the how much things are now "moving" in this code, with the potential risk of breakage.

That said, these different points could be addressed or not, in some follow-ups.

We could possibly try to slightly reduce the default cancel-delay, to e.g. 50 ms instead, however with so many other related changes that's not really something that I think we want to do right now.

And your patch looks good for me.

I'll submit a separate PR, however probably not today since I'm currently sick with a cold.

I'll submit a separate PR, however probably not today since I'm currently sick with a cold.

Take care of yourself.

/botio integrationtest

/botio-linux preview

/botio integrationtest

/botio-linux integrationtest


Compound Script TimeoutError

I just started using the bot today (only the compound script basically) and in general it seems to work fine. However, sometimes, I'm getting an error, saying the the connection to the 3commas API timed out...
Steps to reproduce the behavior:

Run Compound script
Settings in compound.ini:

[settings]
timezone = Europe/Berlin
timeinterval = 3600
debug = False
logrotate = 7
default-profittocompound = 1.0
3c-apikey = abc123
3c-apisecret = abc123
notifications = True
notify-urls = ["tgram://abc123/?image=False&detect=yes&silent=no&preview=no&format=html&overflow=upstream&rto=4.0&cto=4.0&verify=yes"]

[bot_myBotID]
compoundmode = boso
profittocompound = 1.0
usermaxactivedeals = 5
usermaxsafetyorders = 5
comment = CHZ/USDT Bot

12 more bots with the same settings (just other comment and botID)

Please find a part of the log here:
No (new) deals found for this bot!
2022-11-07 13:47:12 - compound - WARNING - Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)")': /public/api/ver1/bots/botID/show
2022-11-07 13:47:24 - compound - WARNING - Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)")': /public/api/ver1/bots/botID/show
2022-11-07 13:47:35 - compound - WARNING - Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)")': /public/api/ver1/deals?scope=finished&bot_id=botID&limit=100&order=closed_at
2022-11-07 13:47:47 - compound - WARNING - Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)")': /public/api/ver1/deals?scope=finished&bot_id=botID&limit=100&order=closed_at
2022-11-07 13:47:49 - compound - INFO - Fetched bot start BO '10.0', SO values '10.0' and max. active deals '1'
2022-11-07 13:47:49 - compound - INFO - Finished deals: 0 total profit: 0.0
2022-11-07 13:47:49 - compound - INFO - Profit available to compound: 0.0
2022-11-07 13:47:49 - compound - INFO - Profit available after applying percentage value (1.0): 0.0
2022-11-07 13:47:49 - compound - INFO - Binance AVAX/USDT
No (new) profit made, no BO/SO value updates needed!
2022-11-07 13:47:59 - compound - WARNING - Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)")': /public/api/ver1/bots/botID/show
2022-11-07 13:48:11 - compound - WARNING - Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)")': /public/api/ver1/bots/botID/show
2022-11-07 13:48:26 - compound - WARNING - Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)")': /public/api/ver1/bots/botID/show
2022-11-07 13:48:36 - compound - ERROR - Error occurred updating bots: Other error occurred: HTTPSConnectionPool(host='api.3commas.io', port=443): Max retries exceeded with url: /public/api/ver1/bots/botID/show (Caused by ReadTimeoutError("HTTPSConnectionPool(host='api.3commas.io', port=443): Read timed out. (read timeout=10)"))
2022-11-07 13:48:36 - compound - INFO - Next update in 1:00:00 at 14:48:36
2022-11-07 13:48:36 - compound - INFO - Notifying 1 service(s) asynchronously.
2022-11-07 13:48:36 - compound - INFO - Sent Telegram notification.

However, it runs since about 5 hours and this doesn't happen all time - even in that snippet, you can see, that for some bot it worked. It also updated all bots succesfully already.
I'm running the bot on a RasPi with Python3.7 and Raspbian GNU/Linux 10 and the newest release of the bot.
Any idea what the problem is?
Thanks in advance!

It seems 3commas is goofing up again it seems... maybe it will work in a bit

Okay, so nothing we can do right now, rather then waiting - got it :)

And is it fixed after the 3commas issues were resolved?

Yeah, seems to be back working fully :)

For those who do not know, I recommend that you subscribe to the 3commas status newsletter
status.3commas.io
there you will receive by mail all the minor or serious notifications of the 3C server health


refactor: dir package [1]

// The relative path to {NOTATION_CONFIG}
const (
    PathConfigFile  = "config.json"
    PathSigningKeys = "signingkeys.json"
    PathTrustPolicy = "trustpolicy.json"
)

func LocalKeyPath(name string) (keyPath, certPath string)
func X509TrustStoreDir(items... string) string

var (
    SystemConfigDir  string // Aboslute path of system level {NOTATION_CONFIG}
    SystemLibexecDir string // Aboslute path of system level {NOTATION_LIBEXEC}
    UserConfigDir    string // Aboslute path of user level {NOTATION_CONFIG}
    UserLibexecDir   string // Aboslute path of user level {NOTATION_LIBEXEC}
)

// ConfigFS and PluginFS can be an union fs
func ConfigFS() SysFS
func PluginFS() SysFS

type SysFS interface {
    fs.FS

    SysPath(items ...string) (string, error)
}
    func NewSysFS(roots ...string) SysFS

Please review this PR before others.
Signed-off-by: Junjie Gao<EMAIL_ADDRESS>

Codecov Report

Merging #179 (46aa865) into main (55b8746) will decrease coverage by 2.05%.
The diff coverage is 67.64%.

@@            Coverage Diff             @@
##             main     #179      +/-   ##
==========================================
- Coverage   82.37%   80.31%   -2.06%
==========================================
  Files          23       23
  Lines        1821     1727      -94
==========================================
- Hits         1500     1387     -113
- Misses        254      266      +12
- Partials       67       74       +7

Impacted Files
Coverage Δ

config/base.go
55.00% <ø> (-18.92%)
:arrow_down:

verification/verifier.go
83.41% <0.00%> (+0.43%)
:arrow_up:

config/config.go
32.00% <40.00%> (-50.36%)
:arrow_down:

config/keys.go
34.78% <40.00%> (-45.22%)
:arrow_down:

verification/helpers.go
88.46% <62.50%> (-4.40%)
:arrow_down:

dir/fs.go
66.66% <66.66%> (-11.12%)
:arrow_down:

dir/path.go
88.88% <93.75%> (-3.42%)
:arrow_down:

dir/path_unix.go
100.00% <100.00%> (ø)

plugin/manager/manager.go
81.81% <100.00%> (ø)

verification/verifier_helpers.go
68.19% <100.00%> (ø)

... and 5 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


iOS 16 breaks camera view

Looks like now that I have iOS 16 installed on stuff it wont scan, added a debug button that dumps a image on page of the canvas from Quagga.canvas.dom.image; and the content is just a black box, preview still works so looks like the JS can't capture the image stream.
I am playing around with custom capture of the video element and see what I can find.

I am writing to a image element by calling this to see the camera input, looks fine on non iOS 16 devices so looks like a video render bug it might be due to new changes or might just be a iOS bug so can keep an eye on this going forward and report if I notice it get fixed in any future Developer Beta.
var video = document.getElementsByTagName("VIDEO")[0];
var datauri=getScreenshot(video, 1);
function getScreenshot(videoEl, scale) {
scale = scale || 1;
  const canvas = document.createElement("canvas");
  canvas.width = videoEl.clientWidth * scale;
  canvas.height = videoEl.clientHeight * scale;
  canvas.getContext('2d').drawImage(videoEl, 0, 0, canvas.width, canvas.height);

  return canvas.toDataURL();

}

This is not a problem in the stable version of iOS and the new beta builds from what I can see.

My apologies for not seeing this one before.  Time since June has been really busy.  I'm glad that Apple seems to have fixed the issue though :D :D Thanks for reporting back.
Much appreciated.


Remove Post Priority Feature Flag

Summary
Remove the Post Priority feature flag. This is no longer needed as it has been enabled for a while and it now relies on the ServiceSettings.PostPriority config setting
Ticket Link
https://mattermost.atlassian.net/browse/MM-48931
Device Information
This PR was tested on:
Related PR
https://github.com/mattermost/mattermost/pull/23735
Release Note

None

Since which version was removed? Remember the mobile app can connect to a multitude of server versions. Does it matter?

Since which version was removed? Remember the mobile app can connect to a multitude of server versions. Does it matter?

It's being removed in parallel in this PR https://github.com/mattermost/mattermost/pull/23735 with the next server version.
The feature still is checked against a permanent config setting for PostPriority so that should be enough for backward compatibility, right?

Since which version was removed? Remember the mobile app can connect to a multitude of server versions. Does it matter?

It's being removed in parallel in this PR https://github.com/mattermost/mattermost/pull/23735 with the next server version, so possibly it will go out without the FF in v8.1 and mobile 2.7
The feature still is checked against a permanent config setting for PostPriority so that should be enough for backward compatibility, right?

If the feature flag is available on a previous server version where it is enabled, then it would not be enough

If the feature flag is available on a previous server version where it is enabled, then it would not be enough

If it was enabled then the config would be enabled as well so that would cover it? The only rare case would be that the Feature Flag would be enabled but not the Post Priority config setting which seems invalid.

So basically you saying that the config setting is always present with and without the feature flag?

So basically you saying that the config setting is always present with and without the feature flag?

Yes, see https://github.com/mattermost/mattermost-mobile/blob/d4bb010b57eb7588d9d6a37a8af49661e39c1d3c/app/queries/servers/post.ts#L246 and the change in this PR it now always relies on the config which was introduced at the same time as the FF here: https://github.com/mattermost/mattermost-mobile/pull/6620

Since which version was removed? Remember the mobile app can connect to a multitude of server versions. Does it matter?

@enahum How about the over way around? An old mobile app that connects to the new server? Is that an option? How is that handled?
Because in that case if an old mobile app that still looks for the Feature Flag and connect to >v8.1 will return false to that flag and the feature is missing.

@marianunez yes that would be a possible scenario, but easily fixed by asking the end user / customer to update

Building app in separate branch.


RFC: removing docker build

Purely exploratory issue. Is anyone using the docker build?
From what I can tell, distros prefer packaging without docker. Docker might be more convenient for newcomers to the project, but we're essentially supporting dual build systems. If we remove docker support, it could unify our efforts and make everyone happier in the long term.

What was the consensus of this one? I am new to bpftrace and find it convenient to build a statically linked bpftrace binary which is portable. Though now I have a syntax error on master:
[ 20%] Building CXX object src/CMakeFiles/bpftrace.dir/clang_parser.cpp.o
/data00/fam/bpftrace/src/clang_parser.cpp: In member function 'void bpftrace::ClangParser::parse(bpftrace::ast::Program*, bpftrace::StructMap&)':
/data00/fam/bpftrace/src/clang_parser.cpp:223:8: error: expected unqualified-id before '[' token
   auto [ksrc, kobj] = get_kernel_dirs(utsname);
        ^
/data00/fam/bpftrace/src/clang_parser.cpp:224:7: error: 'ksrc' was not declared in this scope
   if (ksrc != "")
       ^~~~
/data00/fam/bpftrace/src/clang_parser.cpp:225:55: error: 'kobj' was not declared in this scope
     kflags = get_kernel_cflags(utsname.machine, ksrc, kobj);
                                                       ^~~~

What is our supported C++ version? Should I be looking at fixing the docker image or the source code? Should I look for a more proper setup to build bpftrace?

@famz I had the same problem. I've updated my gcc and c++ to version 8.

@famz we just landed #423 and #433, which should fix the issues when building statically on the Alpine container. Please note that there are some known issues with the static build binary though: https://github.com/iovisor/bpftrace/issues/266


Is it possible to commit our idea to git

hi, is it possible to commit our idea to git? which branch we should use?

Sure, I just added the contribution part on readme part.
Just share your ideas here I can create a branch, or create it on your fork and open a pull request.

Very tnx
I had a idea for connecting cards to real tweet by a link, and also we can have a retweet link on retweet icon
I already tested this idea , it’s a small commit that you can make it too.

We will do that in the next phase, but if you are a Vue.Js feel free to contribute.

Dear vahid, i have commited on my fork. and i will share my idea with you same as this issue. very tnx


proposal: affected/package: Add ternary operator in golang

BACKGROUND
Writing multiple if and else is redundant, It increases LOC(Lines of Code) which I don't think is a good idea.
I am a big fan of the ternary operator in C/C++.
var index int
if val > 0 {
    index = val
} else {
    index = -val
}

PROPOSAL
Make it 1 Liner, It will save tons of LOC for sure.

index int := val > 0 ? val : -val

OR

int index = val > 0 ? val : -val

OR

index := val > 0 ? val : -val

OR

index := val > 0 ? val "if : operator not fit, use of your choice but make it work" - val

Saw somewhere on stackoverflow,
func If[T any](cond bool, vtrue, vfalse T) T {
    if cond {
        return vtrue
    }
    return vfalse
}

for this

min := If(i > 0, i, 0)

See https://go.dev/doc/faq#Does_Go_have_a_ternary_form

Missing the ternary and bit inversion operator makes little sense in a language that is meant for system programming. The alternatives (if/else and XOR) are quite cumbersome. I hope they will change their minds about it eventually.

For the record, Go does have a unary bit inversion operator: ^.

I really like Go but I can see so many developers need to maintain their own patch such as ternary, try-catch, string toUpper/Lower, math max, min, check exist key in map in 1 LOC instead of 3, ...
Each team has its own style of implementation so it makes Go more unreadable and fragmented


[GitSync and GitClone] Use shallow clone and single branch

What is your feature request?
For the Git Sync and Git Clone it would be helpful to use shallow clone (only clone the blobs and not the entire history) this goes with the single branch option.
https://git-scm.com/docs/shallow
https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---depthltdepthgt
What alternatives have you considered?
Moving DAGs out of the monorepo into a separate repository.

Hello @gsemet  and @thesuperzapper thank you for your effort, this helm chart has been very useful.
I have a simple change that would be very helpful in my use case. We have a massive monorepo and syncing all the history doesn't make much sense.

Hello @gsemet  and @thesuperzapper thank you for your effort, this helm chart has been very useful.
I have a simple change that would be very helpful in my use case. We have a massive monorepo and syncing all the history doesn't make much sense.

completely forgot about this one, sorry for the delay I'll try to finish it this week.

This is now the default behaviour after version 8.0.0 of the chart, you can customise it with the dags.gitSync.depth value.


Consider to remove migrateFromOldCachedViewContainersValue

Just noticed this code which we can maybe remove by now:
https://github.com/microsoft/vscode/blob/0b1cd268f1a2753ba02ab1a0754f7d4a0528b7b3/src/vs/workbench/browser/parts/activitybar/activitybarPart.ts#L1025-L1037

Removed the method.


Option to prevent automatic update of /etc/hostname

Please fill out the below information:

Your Windows build number:  18936

As a feature request, could we have an additional option in wsl.conf, similar to the existing
generateHosts = false
to prevent WSL from overwriting the /etc/hostname file with the Windows hostname on startup?
Background:
Since the WSL 2 lightweight VM uses a separate network interface and hence IP address from the Windows host, that they share a hostname creates various unexpected interactions when trying to communicate between them.
I work around this with a small systemd service which renames the host with a '-wsl' suffix and updates the nameserver when it starts up (see https://github.com/cerebrate/wsl-ip ), but renaming the WSL host on every startup is a rather an ugly kluge and doesn't help people who aren't using baroque systemd-enabling techniques.

Seems like a reasonable request, however more is involved with the hostname than just the /etc/hostname file.  We also call sethostname to update the kernel state.  What might make more sense is the ability to override the host name with a string.  @cerebrate - Does that sound ok to you?  Do you have any issues with still setting the domainname setdomainname and also in /etc/hosts.

Ah, yeah, init would have to do that, wouldn't it?
Overriding it with a string in wsl.conf would be a much better option for me, then, yes. That'd clear all this up nicely.

Cool, I see this as a useful addition to wsl.conf anyway and it will be very straightforward to do. Thanks for the suggestion.

Thinking about this a bit more, it probably makes sense for this to be in a config file with other options that modify VM-level settings.  A config file like this exists, but the functionality is not present in the Insider build (yet).
Either that, or each distro should be launched in a UTS namespace.  What are your throughts @cerebrate?

Hm. Well, I think the setting probably need to be per-distro (I'm presuming the VM-level config file wouldn't be?). With multiple distros running in multiple VM instances, they're going to have discrete IP addresses, etc., and I'd expect multiple-distro users to want to distinguish them from each other hostname-wise for essentially the same reasons.

Distros all run in the same VM in the same Network namespace.

Oops. (I confess virtually all of my use has been one distro at a time, so I haven't looked into that as thoroughly as I might have.)
That being the case, I have no problem with it being with the other VM-level settings.

A config file like this exists, but the functionality is not present in the Insider build (yet).

Other stuff too. Ref #4232, which I realized right after I posted over there few weeks back that sysctl.conf(5) is problematic, nevermind hostname(5).

Either that, or each distro should be launched in a UTS namespace. What are your throughts @cerebrate?

A UTS namespace and a NET namespace with veth(4) and SimpleBridge. Probably also the new 4.6 cgroup namespace too if each systemd wants to believe it is the boot init, contrast a container systemd as with systemd-nspawn, LXC, Docker, and the rest which adhere to systemd's Container Interface.
Long story short, if this could be done with a one liner they wouldn't hold conventions on the topic.
To the specific ask:

but renaming the WSL host on every startup is a rather an ugly kluge

The standard approach taken by systemd-nspawn etc is to bind mount over /etc/hostname, not rename it. It isn't a kludge. It's a necessity, because the hostname is established before systemd starts not after. That's the purpose of this line in wsltub from last spring.

I'm still on the fence if we want a separate network namespace. Our eventual goal is to be more similar to the WSL 1 model where the IP address is the same as Windows.

Right; I think I mushed together some context above. Perfectly okay if 'WSL' (ambiguity quotes) wants to lean toward a one-user-one-distro-one-network kind of model, dare I say like Cygwin, that is running as a equal peer beside Windows.
The answer I gave about NET namespace with veth and the works was in the context of folks wanting to run systemd, with it's whole suite of daemons, let's say smbd or sshd, or let's go crazy dhcpd, that cannot by definition play nice with Windows trying to do the same thing in the same namespace. Or consider killer app ~BitTorrent~ Skype, which has to punch NAT holes.
If you've got the same localhost then the whole question in this thread collapses because you wouldn't need to muck /etc/hostname (the UTS namespace) in the first place. Nothing wrong with that either (simple=good). I was answering in the context of the question.

Speaking only for myself on the general questions:
My concern with systemd, etc., has very little to do with those assorted network daemons, and a lot more to do with the increasing number of tools (snappy being the most immediately obvious) that have taken hard dependencies on systemd, and to a lesser extent with those which require hacky workarounds if it's not there, and to an even lesser extent with not having to fill my .profile with a bunch of manually maintained service-starting clauses.
So for myself, while I appreciate the elegance of sharing the same network namespace as the Windows host, I'd trade that away in a second for those three things, especially the first, but by no means ignoring the reduction in admin overhead from the second and third.
(If I were to construct a hypothetical WSL architecture just for me and my preferences, I'd launch each distro in its own UTS, network, cgroup, pid, etc., namespace with its native init as pid 1, as the easiest way to get to where I want to be, but I do realize that y'all have to cater to the preferences of everyone else, too. :) )

(I should also probably have been more clear: while doing the bind mount, etc., is fine for genie/systemd users, especially since it conveniently affects processes running outside the bottle also when a UTS namespace isn't used, I was thinking of the manual renaming is an ugly kluge for those who aren't going that route.)

My concern with systemd, etc., has very little to do with those assorted network daemons

Fair enough. But you could, in the hypothetical, kinda care, at least a little. See 'cause a functioning suite of those esoteric networking daemons would obviate the need for updatewslip, which you cared about enough about to create. I mean, how else are your Genie users gonna get a zeroconf debian.wsl.local name, and also deal with those users firing up their VPN tunnel, which swaps their upstream DNS (long after after your updatewslip script has run), in order to download ~Game of Thrones~ a Linux .iso image with bittorrent? Amirite?
Which is supposed to be a deliberately comedic scenario. Except for the fact there's an open github ticket for every step in that last sentence.
[Reminds me. Those dots in the Store distro names (f.e. Ubuntu-18.04) need to go.]
Point taken though. If snapd is your itch, it is yours to scratch. Beauty of putting code where your mouth is. 🏆

As a side-note, in the course of futzing around with trying to find a workaround for the network issues mentioned in #4342 , I can now confirm that systemd-networkd and systemd-resolved do indeed work under WSL 2.
(The former isn't any use for network configuration unless you hack your WSL virtual switch to be an external/bridged network instead of the WSL NAT, and the latter requires DNS configuration in /etc/systemd/resolved.conf because - without the former hacking - it won't get any from the former, but nonetheless, they do work.)

I would also be interested in a simple way for WSL2 to have a different hostname.

Build 20180 or greater has this feature. Add the following two lines in that /etc/wsl.conf file.
[network]
hostname = HelloWorld

This option is distro specific. So one need to add the file for each distro. init binary uses sethostname(2) before initializing an instance. You can do this to find if your init binary has this feature.
$ readelf -p 1 /init | grep -i "network\."
  [   e18]  network.generateResolvConf
  [  654e]  network.hostname
  [  69ca]  network.generateHosts

Does WSL1 also get this feature? I would assume any changes made to /etc/wsl.conf would need to work with both.

Yes it also works with WSL1.

Thanks for the feature ! And thanks to everyone for the interesting read in this thread.
Does this mean I can use the following to successfully access my  windows VcXsrv ??
export DISPLAY=$HOSTNAME:0
Instead Of  DISPLAY=$HOSTNAME.$WIN-DOMAIN:0

Yes $HOSTNAME is set to according to the value provided in hostname field as I said above. Make sure you are using latest Windows insider build.

Build 20180 or greater has this feature

Setting the host name in /etc/wsl.conf works for me in Windows 10 Version 1909 Build 18363.1082.
$ readelf -p 1 /init | grep -i "network\."
  [   cbb]  network.generateResolvConf
  [  60a3]  network.hostname
  [  6479]  network.generateHosts


Add query support

Parson already has dotget and dotset functions which I admit are minimal and sufficient as API.
Even so, many of JSON will contain both objects and arrays, in a way it'll be easier to have the accessing syntax to traverse JSON handling both objects and arrays together just like JavaScript.
value = json_value_query_string(root_value, ".list[0].data.prop");
value = json_value_query_string(root_value, ".list[0][data].prop");

Please provide a full sample with json/fullcode. thanks.
@kulikala

Hi @kulikala,
I need to think about this feature first. It does seem reasonable but I'd rather not rush into adding anything to the API without thinking of all the pros/cons first.
Regards,
Krzysztof

This feature looks desirable, if we can test this feature thoroughly and make sure it does not introduce bug into old APIs. After all, the ease of use directly contribute the popularity of an open source project.

+1

Dear @kgabis,
When you call json_value_query_value function, it just returns a pointer to single JSON_Value instance in the given JSON tree.
I guess the point of this argument is lying here.
Here are the pros and cons I can think of:
pros

Retrieving a value from a JSON object/array become requiring less code
json_value_query_value does not allocate new memory,
so json_value_query_value is fast, one pass run, and
you can cleanup all code with single json_value_free call
The query is similar to JavaScript accessor and intuitive

cons

json_value_query_* brothers only accept pointer of JSON_Value;
this approach may conflicts in a way with API's main approach, json_object_* sisters
The query is not strict at all: ".", "..", "...", "[]", ".[]" all return the root value
The query ".." looks like the descendant operator of E4X proposal but it's not
The query looks like JSONPath but it's not
Maybe object keys wrapped with brackets [] might be with single quotes '':
.object[key][1] might be .object['key'][1]
The query would create another JSON_Value instance, should return multiple values with JSON_Array

I'm still not convinced this should end up in the library. The only use case I can think of when array notation will be useful is when you know exactly how many elements an array has which I assume is not that common. It might be nice to have this functionality in dotget/dotset functions (although I like name query a lot more, but it's too late to change that) however I'd rather not add a whole new set of functions just for that. It might confuse library users because there will be 2 ways to accomplish a similar goal. The only downside of using dotget/dotset functions is that they must be called on objects so it won't be possible to call them on an array.
The other reason not to merge this pull request is that there is a memory leak here and here and I don't like the fact that query syntax is not strict.
I've made an issue (not really an issue though) for this feature at https://github.com/kgabis/parson/issues/57.


unknown fuction 'format'

Hello,
I've been trying to wrap my head around these modules.  When I do terraform get and terraform apply, terraform barks the following at me:
Error creating plan: 1:23: unknown function called: format in:
${lookup(var.all_amis, format("%s-%s-%s", var.channel, var.region, var.virttype))}
Also is it necessary to cd into .terraform/modules/<sha i'm assuming> and run make?  If so I think it would be useful to add that to the README.  Thanks for the help and good work!

format was added in terraform 0.4.0, you need to be using at least this version for this module to work :)
And you're right about the make - I have a common pattern I've written about (on my blog at bobtfish.github.io) which I always use, but that wasn't in the documentation here - I've added a note now!

I could have sworn I had 0.4+ but alas you are correct sir!  I still had 0.3.7 sitting around.  Thanks for the feed back!


should Display.getBaseAccessibleInstance return an AccessibleInstance of a leaf most node?

As part of https://github.com/phetsims/scenery/issues/674, we found a bug where we should have been sorting the AccessibleInstances of a leaf most trail, but instead getBaseAccessibleInstance was only returning an ancestor, never the leaf. We fixed this in one of the occurrences (Display.changedAccessibleOrder) but there are others. We should make sure that none of them assume that the base accessible instance could be the leaf of the trail.

getBaseAccessibleInstance no longer has any usages, so I deleted the function. My guess is that it lost its usage when @jonathanolson refactored the a11y side of scenery to use AccessibilityTree.js Closing.


Importing from env.mjs in next project leads to infinite loading of typescript intellisense

When importing from<EMAIL_ADDRESS>typescript get reeaaally slow. It takes more than a minute to load intellisense.
Files where no env-variables are imported seems to be working fine
"@t3-oss/env-nextjs": "0.7.0"
VSCode:
Version: 1.83.1 (user setup)
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:48:05.904Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

Interesting... can you provide a repro where this happens?
I got a fairly large ts project with a big env.mjs file and haven't noticed this issue.

Interesting... can you provide a repro where this happens?
I got a fairly large ts project with a big env.mjs file and haven't noticed this issue.

Will try to provide a minimal repro this week.

Closing as stale. Feel free to re-open with a reproduction repo.


Netflix browser issue

The latest release comes up as unsupported browser by multiple services.

Fix is in place via commit 6900a2d and will put in a new release soon


MWPW-126559

Removing #value from review urls to prevent errors.
Resolves: MWPW-126559
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://MWPW-126559--milo--adobecom.hlx.page/?martech=off

This has been in draft for 2 weeks, is this still an interesting PR or can it be closed for now? @Blainegunn

This has been in draft/stale for 2 weeks, is this still an interesting PR or can it be closed for now? @Blainegunn
It could be useful but not needed
i'll close


Gluon multigpu notebook

@ilkarman  @miguelgfierro Here is the Gluon multi-gpu notebook
Are you guys interested in me running all the notebooks on V100 and V1004x V1008x? AWS has a nice Deep Learning AMI with the latest frameworks installed and CUDA9/CuDNN7 😄
Key points
Environment
OS:  linux
Python:  3.6.4 |Anaconda, Inc.| (default, Jan 16 2018, 18:10:19)
[GCC 7.2.0]
Numpy:  1.13.3
MXNet:  1.1.0
GPU:  ['Tesla V100-SXM2-16GB', 'Tesla V100-SXM2-16GB', 'Tesla V100-SXM2-16GB', 'Tesla V100-SXM2-16GB']
CUDA Version 9.0.176
CuDNN Version  7.0.5

Training
...
Batch 300: Sigmoid Binary Cross Entropy Loss: 0.5456
Epoch 4, 0.9851 test_accuracy after 115.13 seconds
CPU times: user 31min 10s, sys: 13min 17s, total: 44min 27s
Wall time: 9min 43s

Evaluation
Full AUC [0.81589024029848356, 0.87498761193629493, 0.8041636531647901, 0.89052264500750433, 0.88501296203404789, 0.92916879812866482, 0.73471103154651096, 0.83967921019772007, 0.62516541650660296, 0.85854952947797802, 0.75761101151841093, 0.79412911609967263, 0.76616626555774625, 0.89359549149683082]

Validation AUC: 0.8192

Synthethic Data
...
Batch 300: Sigmoid Binary Cross Entropy Loss: 2.7731
Epoch 4, 100.12 seconds
CPU times: user 29min, sys: 12min 42s, total: 41min 42s
Wall time: 8min 11s

Thomas that's brilliant thanks so much! I'll run on the slow P100s to get some timings. Sure if you get a chance on the Voltas that would be amazing. The V1008x looks crazy


Successfully connected to http://localhost:9090 but it doesn't look like a valid ML backend.

Successfully connected to http://localhost:9090 but it doesn't look like a valid ML backend. Reason: 500 Server Error: INTERNAL SERVER ERROR for url: http://localhost:9090/setup.
Check the ML backend server console logs to check the status. There might be
something wrong with your model or it might be incompatible with the current labeling configuration.

Hi @swatijibhkatesj
Could you please show your ML backend logs?

For what it is worth. I spun up a docker container that I used a few months ago and ran into this issue. Initially, I though it was because I didn't have the api.py file configured.
Take what I say next with a pinch of salt, but I think that if you don't have labels set up for a project it looks for the localhost:9090/setup endpoint and if not set up you get the error above.
When I manually set up labels for the project my old code worked again


repo sync

This is an automated pull request to sync changes between the public and private repos.
:robot: This pull request should be merged (not squashed) to preserve continuity across repos, so please let a bot do the merging!

please close this account an stop invading mine an my childrens privacy my devices havee  been hacked an i want this stoped. the email it hooked to has me locked out so replulying to that does t work please close this an stop what ever is happening

please close this account an stop invading mine an my childrens privacy my devices havee  been hacked an i want this stoped. the email it hooked to has me locked out so replulying to that does t work please close this an stop what ever is happening


Implement peek command

close #14

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (869a0de) to head (d0e71a8).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##            master       #21   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          305       334   +29
=========================================
+ Hits           305       334   +29

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Extended with code preview + MathJax

Added support to preserve whitespaces and enable inline MathJax rendering of equations.

@HermitPixel did this fix your issues? Would you mind testing?

I will try tonight for you.
Sent from my iPhone

On Dec 28, 2015, at 12:35 PM, csholmq<EMAIL_ADDRESS>wrote:
@HermitPixel did this fix your issues? Would you mind testing?
—
Reply to this email directly or view it on GitHub.

It works for me on Windows 8.1 now with this release from you.
On Mon, Dec 28, 2015 at 12:35 PM, csholmq<EMAIL_ADDRESS>wrote:

@HermitPixel https://github.com/HermitPixel did this fix your issues?
Would you mind testing?
—
Reply to this email directly or view it on GitHub
https://github.com/webBoxio/atom-html-preview/pull/84#issuecomment-167635643
.


Update the Datree Centralized Policy Article

Hey @Shivam-Katare!
Thanks for the suggestions, this page did need a touch up:)
I altered some of them, I think it looks better now 👍🏼


Connect hardware wallet

When signing with a hot key in a multisig this pop up for a hardware wallet appears after clicking the sign button. After closing the pop up things work fine

Is one of the other keystores in the multisig a connected hardware wallet?

As of 29cd3217, Sparrow will avoid showing the USB signing dialog for watch only keystores in multisig wallets.


Allow Illinois courses to use this as a service

Created a process for Illinois courses to be added to the queue (this may be just a dumb web form that e-mails someone)
Advertise that process in the README

(This is a subset of the work that is likely done under #19)

@wadefagen is this any different from #23?

Oops -- I read @genevievehelsel #19 and was like "yes, this is great, I should make sure to write this SaaS thing down", but I already did.
Thanks!


Foreign languages support

Hello,
Is it planned to translate the full solution into foreign languages ? (ex : French for example !)
Thanks.

Hello, @nicolasmattioni ,
We don't have any announcements to make about support for additional languages in the Accelerator.
Today, the solution only supports English. However, you can add translations via additional solution layers.


Headers removed when using request_serializer :json

Hi,
I need to post to a service that expect body to be in json format but also this service expect headers like:

'Content-type', 'application/json'
'Accept', 'application/vnd.service-v0.1+json'
'Authorization', "Basic #{key}"

If I don't use the request_serializer :json my service receive the headers but content is not send as json, if I add request_serializer :json content is sent as json but headers are missing.
    AFMotion::Client.build('http://<IP_ADDRESS>:4567') do
      header 'Content-type', 'application/json'
      header 'Accept', 'application/vnd.service=v0.1+json'
      header 'Authorization', "Basic #{key}"

      #request_serializer :json
      response_serializer :json
   end

I'm not sure what I'm missing here, if this is the right behavior or if this is a bug.

I just got bitten by this behavior :rage:
Not at all what was expected and it goes completely against everything documented in the README.

Could we re-open this issue until either a fix is implemented or the documentation has been updated?

@zmillman I'd happily accept a PR which changes the README - I'm not sure if this is a bug or not (I don't recall the default behavior when doing the same with vanilla AFNetworking), but if you do want to investigate more I'd definitely merge that PR as well

Seems like issue is that request_serializer in AFMotion::ClientDSL initializes a new serializer which doesn't retain any of the configuration of the serializer it's replacing which was set up earlier in the clobk.
In Obj-C, you have to be very explicit about which serializer you're configuring headers for so you wouldn't even be able to call the equivalent of header until after you called the equivalent of request_serializer. It's surprising as a developer that the client DSL is not order-agnostic, and the examples in the README are the reverse of proper configuration.
I'm not sure whether order mattering in the DSL is truly a "bug" (or just a vicious gotcha) but I'll definitely throw together a PR to clarify the documentation.


Time filter is not applied in Query builder mode for calculations (Min, Max, Mean...)

Expected Behavior

Using Time series or Stat panels, I expect to use the calculations such as Min, Max, Mean and see the correct values depending on the selected timeframe
Screenshot below is showing correct values in Legend over the last 3 hours:

Current Behavior

Using Time series or Stat panels, the calculation values are in fact the one corresponding the whole series, as if the time filter were not applied for these calculation only.

This is becoming more clear in table view:

The table contains all the values, not only the last 3 hours

Workaround

As a workaround, I switched to the Code mode for the query, and added the timeFilter macro manually:

The result is now working as expected:

Context

Grafana version: 9.2.4
BigQuery plugin version: 1.2.6

This might be linked (or duplicated) with https://github.com/grafana/google-bigquery-datasource/issues/137

hey @pkoeltz,
did you create your query with the query builder?

Hi @zoltanbedi , thank you for looking into this.
Yes the query was created with the query builder and resulted in this issue. Switching to code and adding the timeFilter macro in the query resolved the issue.

timefilter should indeed be added by the query builder..

This is the same as https://github.com/grafana/google-bigquery-datasource/issues/139 so I'm going to close this.


fix(mempool): change "mempool is full" log level to debug

it happens in benchmark or production when traffic is high, the log frequency is very high because it's triggered by p2p tx propagation message.
Solution:

change it to debug level

https://github.com/cometbft/cometbft/pull/4125

Saying that, should the log level also change on this line? I'd think that would also flood the log (it's not Info but if Error level is set it might also cause the issue.

yeah, but it's less frequent since most of the requests should have been blocked at the beginning.

can we backport this to 0.38.x which we are using.
and do I need to add a changelog for this?

should the log level also change on this line?

I would say yes 👍

should the log level also change on this line?

I would say yes 👍

changed too.

looks like you forgot to format the Go code

looks like you forgot to format the Go code

done


2D editor view does not highlight selected nodes when scene extends a Dialog class

Tested versions

Reproducible in v4.2.1.stable.official [b09f793f5]
Reproducible in v4.3.stable.official [77dcf97d8]

System information
Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - integrated Intel(R) UHD Graphics 630 (Intel Corporation; <IP_ADDRESS>4) - Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (16 Threads)
Issue description
When editing a scene that extends AcceptDialog or any of its descendent classes in the 2D view, selecting a node in the Scene tree does not show the red "selected" border around the selected node.
Steps to reproduce
Create a new Scene from top Menu or FileSystem RBM
Select AcceptDialog as the Root Type
Enter new scene name
Click OK
Double click the new scene in the Filesystem tree
Switch to the Scene tree
Click the "Toggle Visibility" button on the scene root node
Select the 2D editor
Add any child control to the Dialog (e.g. LineEdit)
Select the child control node in the Scene tree
The selected control is not indicated in the 2D editor window
Minimal reproduction project (MRP)
N/A

Thank you for reporting, consolidating in:

https://github.com/godotengine/godot/issues/79289

See there for more details, if you think something was missed about this and it's not the same issue, please comment here and it can be reopened


CV: More innovative presentation

Use multiple columns, some data viz.

Restore custom header and just open the CV link in a new window. Skip it in the keyboard navigation.

Probably need the data model in #71 before attempting this.

#71 Is done! Will need to do some more tidying of CV data too, but that's orthogonal to the visual redesign.


Feature request: syntax highlighting for Brython

https://brython.info/

Interesting, I didn't know about it.


NodeJS : Building a Vanilla NodeJS Rest API

Description
Description
I want to make a documentation on building a basic vanilla NodeJS Rest API without using other npm packages.
Domain
MERN
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign

@Shaviaditya

Kindly follow the Contributing.md.
Use proper naming of your issue. (eg. MERN_Nodejs: 2.3 ...)
Follow the roadmap, already shared in Discord.
or discuss with any of the mentors or supervisors, before creating the issue.
- As we have to follow a proper roadmap, and this topic is not in the Roadmap.

@hardikk2002 thanks a lot for the info, the naming convention just slipped through by mind..


Fix duplicate database queries

@leandrocfe Can this PR be merged?

@leandrocfe Can this PR be merged?

Hi,
Sure. Could you explain this issue please?

@leandrocfe Can this PR be merged?

Hi, Sure. Could you explain this issue please?

Without this change the getOptions method was called twice, so we have duplicated queries for every chart.

@leandrocfe Can this PR be merged?

Hi, Sure. Could you explain this issue please?

Without this change the getOptions method was called twice, so we have duplicated queries for every chart.

Ok, I'll check. Thank you 👍

@leandrocfe Great, thank you!


Testing silent login

Hi - I am not sure my silent login is working. My understanding is that this happens if the service worker is killed by the browser?
Is there a way to simulate this happening? I have tried stopping and unregistering the service worker from dev tools but the library seems to just fetch a new token via silent refresh / refresh token flow (successfully), rather than do a silent login which is what I need to test?
Thanks

Hi @beanovar Thank you for the issue :)
Silent login trigger in fact a silent signin. It the same.

When you kill the service worker, the silent signin/login use cookies via an iframe to retrieve again new tokens.
Your test is passing. The drawback of silent login is taht now you need to be on the same domain than oidc server on safari because cross domain cookies are blocked by default.

Thanks ! Confirmed.


Review checklist for PRs

This is a proposal for a PR review checklist (created together with @ranocha). Its purpose is to make everyone's life easier by

providing guidelines for PR creators on what to do before requesting a review
helping reviewers (experts and novices alike) to know what to look for
reducing the time and effort between having a first implementation and getting a PR merged.

To make it as usable as possible in practice, we tried to be concise and to include only measurable/actionable items (as far as possible). The items are sorted such that also a less experienced reviewer can go through the list top to bottom and provide valuable feedback on most items (the "Performance" and "Verification" sections were put last, since they might be the hardest to check).
As usual, this is just a first draft and open for discussion, and comments, suggestions, criticism are welcome! This is a document for and by our community - if nobody finds it useful (or usable), it will have missed its goals 🙂

Review checklist
Purpose and scope

[ ] The PR has a single goal that is clear from the PR title and/or description.
[ ] All code changes represent a single set of modifications that logically belong together.
[ ] No more than 200 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

[ ] The code can be understood easily.
[ ] Newly introduced names for variables, functions etc. are self-descriptive.
[ ] There are no redundancies that can be removed by simple modularization/refactoring.
[ ] There are no leftover debug statements or commented code sections.
[ ] The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

[ ] New functions and types are documented (docstring or top-level comment).
[ ] Inline comments are used to document longer or unusual code sections.
[ ] Comments describe intent ("why?") and not just functionality ("what?").
[ ] If the PR introduces a significant change or new feature, it is documented in NEWS.md.

Testing

[ ] The PR passes all tests.
[ ] New or modified lines of code are covered by tests.
[ ] New or modified tests run in less then 10 seconds.

Performance

[ ] There are no type instabilities or memory allocations in performance-critical parts.
[ ] If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

[ ] The code is correct.
[ ] If new equations/methods are added, a convergence test has been run and the results are posted in the PR.

Concerning Documentation: Pointing to literature/publications whenever possible

I'd suggest

explaining what is expected in "code correctness". Does this mean a verification of correctness?
maybe a short note that formatting and spelling errors will be caught by CI

Concerning Documentation I suggest something like "Pointing to literature/publications whenever possible"

How about

[ ] Relevant publications are referenced in docstrings (see example for formatting).

?

I'd suggest
* explaining what is expected in "code correctness". Does this mean a verification of correctness?

How about

The correctness of the code was verified using appropriate tests.

* maybe a short note that formatting and spelling errors will be caught by CI

I agree that this information should be available. However, I'd rather add it to some review guidelines and not to the checklist itself, just to keep it short.

Maybe point to the benchmarking part of the Trixi docs on the “improve performance…time measurements” point. https://trixi-framework.github.io/Trixi.jl/stable/performance/#Manual-benchmarking

I've included all changes discussed so far in the checklist above - please check if my changes adequately address your issues.

LGTM. Thanks for adding those!

Maybe add something regarding consistency? This is quite hard to formulate in a way such that this is clearly verified or not. Maybe we could focus on consistent variable names. As an example, this could mean that we always denote the conservative variables of the swe by h and v, the wave celerity sqrt(equations.gravity * h) by c, that we add a suffix _ll and _rr to variables at left and right interfaces and similar things. However, this could also go to the style guide.

Yes, sounds very good!

✅

This checklist looks good to me. Thanks for tackling this fundamental and important logistic task @ranocha @sloede ! I had one remaining question. Where should this information "live" within our ecosystem. Would it become part of the Trixi docs in the "Development" section or so? Or is it possible to "pin" this PR in some way for fast reference for current and future contributors to the Trixi?

One suggestion was as a PR template https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.

@sloede and I are experimenting with it right now. Status quo: it will probably be posted in each new PR by a bot

I really do not like making it a PR template. I have seen something like this in other repos and was always annoyed when making a PR there since I had to read a wall of text that would be posted in my name. That's much more bureaucratic than I would like Trixi.jl to be.

Shall we add a small introductory sentence to it so that people who were not involved in creating the list know what is going on? Maybe something like
Review checklist
The following checklist is added automatically to each new PR. It is meant to assist both reviewers (to guide them in a structured review process) and creators of PRs (to let them know what reviewers should typically look at). It is not necessarily complete and can does not need to be checked explicitly (be experienced reviewers).
Purpose and scope
[as before]

For me, the checklist barely fits on a single screen, thus I am ambivalent about making it even longer. However, I do see the need to clarify that this is meant to help people, not to deter them. Thus maybe we can rephrase it a little to make it sound even less scary, e.g.,

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

At the bottom, maybe we can add something like

Created with :heart: by the Trixi.jl community :whale:

because, c'mon, who doesn't like the friendly blue whale ?!?

Sounds good to me. Let's do it like this :+1:


MQTTX连接 Rabbitmq MQTT 问题

Rabbitmq 版本：RabbitMQ 3.13.2
Rabbitmq MQTT插件已启用

Ip与端口都是通的，使用mqtt://方式连接Rabbitmq 服务器报错

使用ws://方式连接Rabbitmq 服务器报错 IP端口都是通的

Hello @NullWan
I couldn't reproduce the issue you mentioned. I successfully enabled the MQTT plugin on RabbitMQ and connected both through MQTTX CLI and Desktop without any problems.

From the error messages you've shared, the issue might be related to the mqtt_v5 plugin not being enabled on your RabbitMQ server. Alternatively, try changing the MQTT version in MQTTX to 3.1.1 and see if that resolves the issue.
Additionally, you might find this official RabbitMQ blog post helpful for more insights: https://www.rabbitmq.com/blog/2023/07/21/mqtt5
Thanks f.or using it. Please let me know if this helps or if you need further assistance.

感谢回复并帮助我解决了困惑，MQTT版本切换成3.1后正常连接，再次感谢


Idk if this counts as an issue, but is there a fabric version of this? i use prefer fabric over forge, but idk if there's a place to download a fabric version.

I will never support a Fabric version of any of my mods ever.
There were a Fabric port at one point though, as the mods license is MIT. So anybody can do whatever they want with the code.
Im however not sure if the port is updated.


Now, there are other behaviors we could imagine for const_eval_select, besides "UB if the two branches disagree". One proposal made earlier in this thread was to require that compile-time behavior(s) must be a subset of possible run-time behaviors. This could be achieved by saying that at run-time, const_eval_select will non-deterministically pick either option. But that is terrible! People will want to use this in situations where they really want the "fast branch" to be taken at run-time. Sure, we could promise that reasonable performance-oriented Rust compiler will never pick the compile-time branch at run-time, but if we do that then saying that "compile-time behavior(s) must be a subset of possible run-time behaviors" becomes a sweet lie.
So really the best option seems to be to guarantee that compile-time and run-time take different branches, and impose no further requirements on the language level. Of course functions would still generally be expected to behave the same in both contexts, unless explicitly documented otherwise.

For this, I have an immature suggestion to add a compile-time context beyond the constant context, limit its progression from compile-time, we can call it in context_eval_select and other locations that must be executed at compile-time, and this may benefit from compile-time reflection in the future

Maybe I shouldn't discuss it here
, I want to talk about my idea of compile-time reflection. Exposing reflective interfaces that can only be called in the compile-time context, the user will know that these abstractions are unoverhead and if the user needs to do runtime reflection, they will transcribe the compile-time reflection information to runtime data. Furthermore, the constant context will act as a bridge between the runtime context and the compile-time context, which can be called by two and treated as one of both, or const_eval_select

Yeah that all sounds pretty out-of-scope for this RFC.

one place where const_eval_select might want to take the const path even at runtime is when running it with miri, so imho that's a more reasonable justification for saying "we could take the const path at runtime but generally won't"

The fact that Miri uses const eval machinery is purely an implementation detail. Miri would have to use the runtime path to be correct, so the CTFE engine would probably need a flag for that. It should work though I think.

Sure, Miri can easily take the runtime path, and currently it will. I think what @programmerjake was saying is that it might make sense for Miri to take the compiletime path instead, e.g. to avoid unsuppored SIMD operations. That would only be legal if the spec for const_eval_select said that either branch may be taken at runtime.
But... I am not convinced this is a good default. It's kind of the status quo with align_to, and I think people still hate it. Miri taking vastly different code paths than real code is surprising and can mean UB is being missed. We also already have a mechanism for that: cfg(miri). So I think people can opt-in to have a "shared compiletime and Miri codepath", but I think that should involve some explicit use of cfg(miri) and not happen implicitly with const_eval_select.

Apparently Clang/C++ will sometimes constexpr evaluate if conditions which are (I think) not lexically constant evaluated; e.g. https://gcc.godbolt.org/z/WPnvj633n fails with a constexpr evaluation gas exhaustion. (I'd stick an if consteval in there to see how observable this is, but I'm on mobile currently.)
From a tangentially relevant discussion on irlo: https://internals.rust-lang.org/t/why-does-a-const-eval-not-taken-branch-still-generate-llvm-ir/18378?u=cad97. This user questions why we don't use const evaluation to constant propagate the if scrutinee and avoid emitting LLVM IR for the never-taken branch, including in debug mode.
floating-point side note
const| NaN has another undiscussed potential issue: even if we fold all const-evaluated NaN to a single NaN, we'd *prefer* for f32::NAN` to be a qNaN. We can choose the IEEE-recommended qNaN, or we can try to guess and use the target qNaN if
...but this is off-topic, as this is IMHO still a good change to make even independent of floating-point semantics. I only put it here for lack of recalling a better place to put it.

A final(?) remark on the floating point thing: I agree with Muon, by and large. Though I think people absolutely are evaluating "interesting numerical code" in consteval already! This is in fact a standard sillybusiness in C++ with constexpr, especially for games programmers. Though they might want nondeterminism in floats too simply so that their const float evaluation can be more accurate instead of less in case they do, in fact, target thumbv7neon or whatever...
But I agree with Nilstrieb that this is "not about floats". Not only const_eval_select, but it also has to do with anything with implicit nondeterminism between const time and runtime that we want. For instance, we probably want a const-time heap. Without allowing nondeterminism in general, we have to carve out the specific exception that, yes, a programmer can allocate 100 GB on their 128GB RAM powerhouse workstation and use that as an intermediate input into a const evaluation, but then at runtime your program may have only 1GB available to it. So you're not allowed to have a single reasoning about system resources because the compilation and execution can literally happen on different systems... despite improved ability to reason about system resources being one of the benefits of Rust over many other languages.
Sure, exact system resources at runtime are inherently nondeterministic in many cases, but that really just makes it so much worse to be able to burn through a bonus set during consteval. We already have the complication that when LLVM elides a too-large allocation, that also can introduce a flavor of nondeterminism: a program that should have failed, doesn't, and that difference may be based on optimization level.

Resource exhaustion is a bit different, that's only non-deterministic about whether const-eval succeeds at all. A lot of heap-using code still has the property "if it gives an answer, it's always the same" (at compiletime and runtime).

That's true! That's why I left on the note of the HashMap and its randomness... such as its iteration order, despite being something you shouldn't poke at... suddenly becoming of significant impact and observability. Though I suppose const heap could simply exclude that, but as thin as libstd is, it seems kind of painful to have to exclude one of our premiere collections from code paths that could light up during both CTFE and runtime.

I do understand the motivation and think it's probably a necessary step, but I really dislike this. With the current restriction, const indicates that the function is pure, and that allows cool things like writing more efficient sorting algorithms: By having a const Ord bound, cmp can never return different values for the same inputs, thereby allowing optimizations like unguarded insertion (where you compare against the firsts element first, and then use the result of comparing the to-be-inserted element to the other elements as the only loop condition to shift the element in the right place. Very efficient, but currently not possible in safe Rust). It seems a shame to need a separate pure specifier for this, when currently, const satisfies this need elegantly.

By having a const Ord bound, cmp can never return different values for the same inputs, thereby allowing optimizations like unguarded insertion (where you compare against the firsts element first, and then use the result of comparing the to-be-inserted element to the other elements as the only loop condition to shift the element in the right place. Very efficient, but currently not possible in safe Rust).

You only need a formal guarantee that comparison is pure/consistent if that condition being true is necessary in order to fulfill some unsafe precondition, and failure to uphold sort order consistency could result in unsoundness/UB and not just logic errors and/or "safe misbehavior[^mb]". The Ord trait already has a safe requirement that comparison is consistent. Violating that contract will result in standard library routines misbehaving.
[^mb]: Defining "safe misbehavior" in a satisfactory way is an open question.
As an extra note, simply k#pure Ord isn't strictly enough either, if you ever call other code with access to &T, since T could encapsulate some shared mutability.
std already contains the pattern for this with unsafe trait TrustedLen: Iterator, which refines trait Iterator with a trustable guarantee that Iterator::size_hint is accurate. An on-pain-of-UB guarantee of Ord implementing a consistent total order should similarly be provided by unsafe trait TrustedOrd: Ord, not by const Ord. If having a separate trait for it is too heavy, we could also consider allowing using T: unsafe Trait like T: const Trait works[^opt], which makes the trait bound trustable as an unsafe impl.
[^opt]: I'm personally not fully up-to-date on how/why "keyword generic" traits opt into being able to accept a keyword being applied to them. unsafe Trait would absolutely require an opt-in on the trait before being permitted, though, since it makes documentation (i.e. of the trait requirements/guarantees) much more impactful than for safe traits.

So what is our plan with this RFC? It looks like the lang team would prefer to have this discussion as part of a concrete motivating feature. What could that be?

For float, I made their const behavior part of a recent Pre-RFC. The Pre-RFC suggests to allow compile-time evaluation to make arbitrary choices whenever float operation would be non-deterministic at runtime (i.e., whenever a NaN is produced).
For const_eval_select, I guess that would be a separate RFC?
And then we have align_offset and align_to. If we specify those to guarantee best possible alignment at runtime but not at compiletime, that would basically let one implement  const_eval_select.

Just looking at the backlinks above, this seems to solve many problems that we're having right now. Among them:

https://github.com/rust-lang/rust/pull/121201 requires it
https://github.com/rust-lang/rust/issues/113219 is blocked on it
https://github.com/rust-lang/rust/pull/107624#discussion_r1101911091 doesn't require it, but it helps there
the float semantics RFC already requires this behavior anyways: https://github.com/rust-lang/rfcs/pull/3514/files#diff-98e38594549196fcf747cdb59300226f9d158da53b23fd25a71a30fa8947fa86R212

I think accepting this RFC today would have significant benefit already, even without very design-heavy work like designing the API for stable const_eval_select. I don't see a downside to accepting this RFC, it seems clear to me that we want to allow this behavior. Not accepting it risks that future discussions will have to bring up the points here again, instead of just accepting it, and it will unblock things that are already designed today (like const_cstr_from_ptr).

https://github.com/rust-lang/rust/pull/121201 requires it

Not quite; only doing that plus also exposing align_offset to const fn without subtle soundness requirements needs it.

https://github.com/rust-lang/rust/issues/113219 is blocked on it

Is it? The issue you link just says that it uses const_eval_select, not that it uses it in a way that violates the "both cases must behave the same way" requirement. It's not clear to me why this RFC was added to the blocking list for that tracking issue, it may have been a mistake.
But to add to your list, the soundness requirement in const_eval_select that this RFC aims to lift is the reason why assert_unsafe_precondition has a strange requirement that debug_assert_nounwind does not have, and a bunch of review time and docs effort is spent on keeping that all straight.

Quoting from this discussion

This is the first time we stabilize a usage of const_eval_select that is not just changing assertions. While it is absolutely benign here (basically inlining a naive strlen impl for const eval), this means if we'd remove const_eval_select, we'd need to either take a perf hit in the runtime code by using the same code or make strlen a lang item.

then we should "stabilize" const_eval_select as a perma-unstable libs function, to affirm that no matter whether it is exposed or not to end users it would still exist in the standard library, if such a thing is desirable.

Maybe the RFC should be re-phrased as that? That would make it more concrete, which might alleviate the concern t-lang had last time we tried to push this.

@rust-lang/lang would you be interested in that?

@Nilstrieb I wouldn't hold my breadth to get an answer like this. :)  There's a reason we nominate issues for them -- just pinging doesn't work as they are all drowning in notifications.
If you have the time I'd suggest you work on rewording the RFC. I'd be happy to give feedback. Maybe do it in hackmd so collaborative editing becomes easier. The important point is to make sure that all concerns they raised last time are resolved.

Also: Given that this already has >100 comments, making this a new RFC might be better than updating this one. But ofc if there are important points that were raised in this thread they should be carried over into the new RFC.

#3514 already integrates the most important part and we've just changed the internal rules for const eval select anyways to make it safe. So I'm gonna say "task failed successfully" and close the RFC.
I still don't understand why this wasn't just accepted, there seemed to be consensus that it's good 🤷

Note that const eval select is safe in an unstable way. An RFC like this is still required before it can be stabilized, or used by stable code in an observable way.

Is there presently another issue for tracking stabilization of const eval select? Or should we just wait for a prospective stabilization RFC like @RalfJung is suggesting?

I have created a tracking issue: https://github.com/rust-lang/rust/issues/124625


beanie initialization takes long time often several minutes sometime

Hi
beanie initialization takes long time often several minutes sometime
await init_beanie(database=client.db_name, document_models=[Product])
On debugging it was found that the delay was due to the function await asyncio.gather(*collection_inits) in the file beanie/odm/utils/general.py
The last line in the init_beanie source code
async def init_beanie(
database: AsyncIOMotorDatabase,
document_models: List[Union[Type["DocType"], str]],
allow_index_dropping: bool = True,
):
"""
Beanie initialization
:param database: AsyncIOMotorDatabase - motor database instance
:param document_models: List[Union[Type[DocType], str]] - model classes
or strings with dot separated paths
:param allow_index_dropping: bool - if index dropping is allowed.
Default True
:return: None
"""
collection_inits = []
for model in document_models:
if isinstance(model, str):
model = get_model(model)
collection_inits.append(
model.init_collection(
database, allow_index_dropping=allow_index_dropping
)
)
await asyncio.gather(*collection_inits)

please advise on steps to resolve the issue . At times init beanie is taking upto 3+ minuites . i am loading around 9 model files in beanie
Is this affected by other asynchronous processes being initialized ? i have kafka initialization being done
and other asyn processes being executed as part of initialization as well

Hi @pi194046 ,
It would be great if you can provide a code example with this slow behavior (with Kafka things and etc). If this is possible for sure.
It works fast in my projects, but probably this bottleneck is wide enough for my cases and I don't see it.
Thank you very much for raising this issue.

Thanks for the response . It works fast in other projects , but in this particular project init_beanie functions takes a long time to respond and await asyncio.gather(*collection_inits) is cause of the hang .  what is purpose of this function await asyncio.gather(*collection_inits) in init_beanie implementation code , also what impact does specifying allow_index_dropping=true have in intialization code ? . Will try to post a code example shortly of the issue being faced

If you use pyinstrument, you can see a call graph of what's taking so long

@app.on_event("startup")
async def startup_event():
    from pyinstrument import Profiler

    start_profile = Profiler()
    start_profile.start()
    client = motor.motor_asyncio.AsyncIOMotorClient(settings.mongo_connection)
    await init_beanie(
        database=client[settings.mongo_db], document_models=__beanie_models__
    )
    start_profile.stop()
    start_profile.print()
    app.include_router(address_router, prefix="/address", tags=["address"])

My App is suggesting that all the time is spent copying the indexes
2.853 _run  asyncio/events.py:78
├─ 2.783 init_collection  beanie/odm/documents.py:575
│     [14 frames hidden]  beanie, motor, asyncio, concurrent, t...
│        2.783 collection_factory  beanie/odm/utils/collection.py:29
│        └─ 2.779 [await]

Hey @a5r0n ,
It manages indexes on the init step. So, it is impossible to make it sync, as motor do it in the async way inside.


Revert "MM-12949 - Updating team sidebar and plugins (#2590)"

This reverts #2590 . It was breaking the team sidebar on desktop app.

FYI @asaadmahmood

@jwilander can we get a screenshot of that?

See https://community.mattermost.com/core/pl/ijqiq77y5j8xf8ozht7675jtqc


Paladins and Rangers can't memorize spells

Paladins and Rangers can't memorize spells. They disappear on rest.

Thanks for reporting, and welcome!

Ok, the issue seems to be with Paladins/Ranger at level 4 or 5 only get a 1st level spell slot due to their stat bonus (or level 8 for level 2 spell and so on). Fixed.


NA Map R2 (2017-11-09) pre-release test - Error running Analysis Tools - 1 (Wave Atlas)

Error running analysis tool
Renewable Energy/Wave/Australian Wave Energy Atlas/Analysis Tools/Annual Bivariate Probability Distribution

Custodian notified. Known fragility of services.


Add Adventure Flowchart Snippet

See reddit post: Adventure Flowchart Suggestion

Does anyone have a screenshot of what these look like in the 5e source books that they could share?  I'm wondering if it's more like a linear timeline (easy), or a branching flowchart (hard to impossible without something like Mermaid).

I found this one, which is [reportedly] from Waterdeep: Dragon Heist.

"Flowchart"....psh.

Yeah, less a flowchart and more just a line.
It did get me thinking of an article I read many, many, MANY years ago now, about the design philosophy of the puzzles of The Secret of Monkey Island. The philosophy went that there should be some obstacle (a building guarded by angry dogs, for example) which requires multiple elements to be solved (meat to feed the dogs, found in the town; and herbs to drug the meat, found in the forest).
The players exist in this bubble, where they can attempt to progress either/any/all of the obstacles, but cannot proceed until all of them have been resolved (dogs will eat the undrugged meat but not be calmed, dogs won't eat herbs by themselves).
So the kind of flowchart that I use - because, on reflection, this is often how I design my adventures - would need to have two or three of these boxes detailing the puzzles ("meat" and "herbs"), which lead to a single obstacle block ("guard dogs"), which then repeats.
...I'm going to have to think about how I could formalize that in a brew, now.

I made this with divs and flex

A basic timeline like in the source book is easy, but I wouldn't recommend doing anything with complex flowcharts.  Something like mermaid would be needed.

Lodash's throttle function might be useful - I used {leading:true, trailing:false} for the brewJump function to scroll a given page into view, but I suspect the reverse might work for executing a function - like popping a notification - after a given amount of time, while simultaneously blocking any other calls to that function before the timer expires.

Integrating Mermaid would be very nice, and (at first glance) should be pretty easy.

Even though Mermaid will solve real flowcharts, i got a snippet for this, you can see it in this brew
preview:

the ones at the bottom look messed up bc of the zoom level the screenshot was taken at.

Updating on my last comment, the new syntax for this would be pretty simple:
## Adventure Flowchart

{{flowchart,--width:200px,--spacing:25px

|Chapter 1:
 A Friend in Need|
|-|
|Volo gives the adventurers a quest and an estate as their reward.|

|Chapter 2:
 Trollskull Alley|
|-|
|Adventurers settle into their new estate and meet the neighbors.|

|Chapter 3:
 Fireball|
|-|
|A fireball explodes in Troll-
skull Alley, setting off an investigation.|

|Chapter 4:
 Fireball|
|-|
|Adventurers join the race to find and unlock the Vault of Dragons.|
}}

with the following css:
.page .flowchart table{

  width:var(--width);

  display:block;
	min-height: 100px;
  max-width:;
	border: 15px solid transparent;
	border-image: url(https://raw.githack.com/5e-Cleric/Images/main/border%20flowchart.svg) 41 fill round;
	text-align: center;
	margin:var(--spacing) auto;
	position: relative;
  font:inherit;

  & thead {

    & th {
      font-family: MrEavesRemake;
      font-weight: 800;
      color: var(--HB_Color_HeaderText);
      font-size: .458cm;
      line-height: 1em;
      padding-bottom:10px;
    }
  }

  & tbody {

    & tr {
      background: none !important;

      & td {
        padding: 0;
      }
    }
  }

  &:has(+ table):after {
  display:block;
	width:2.5px;
	height:var(--spacing);
	content:'';
	background:#c1c474;
	position:absolute;
	left: 50%;
  bottom:calc((var(--spacing) * -1) - 15px);
	z-index:-3;
  }

}

Outputs:

Pros and Cons of this method

Pros
Cons

Good UX
Tables are not meant for this

Width and spacing fully customizable
can't input text between charts

Only need one curly block

I made this timeline about nine or ten months ago, to sum up the background of a character for a one shot.
This brew is a simplified version that has only a single content box, that is visually closer to the original timelines.

In my opinion, if you add anything like a flowchart, you’d better be ready for the question “how do I split the flow”.
reframing this as a Timeline snippet is a good first step, since there isn’t an expectation of alternate flows.

a Timeline snippet

When I was preparing some NPCs for my current campaign, I set some of them up with timelines, something like:
NPC: Alyss Stormheart, Cleric of Torm
History: Fourth daughter of a Noble family. Currently chaperoning orphans on a visit to Baldur's Gate.

At Campaign start: In caravan with party
On reaching Baldur's Gate: Leaves to provide for her orphans
Future: Working in taverns in BG

What I realized was that some NPCs - like Alyss here - would have different paths, depending on the party's help (or hindrance). With help, she works in Upper City, a respectable cleaner and sometime cook at the Three Old Kegs.
Without help, she works in Lower City, having received assistance from the Thieves' Guild, fencing stolen items and other black market items.
So an actual forkable flowchart would have been nice.
But it is the pretty much only time I've ever really wanted one.

Just dropping these here for posterity: these images are from Baldur's Gate: Descent Into Avernus:
A straight, non-forking timeline:

An actual fork in the decision tree:

From The Guildmaster's Guide to Ravnica:
This actually looks like an actual flowchart?

There is another:

From Storm King's Thunder

I was just looking around about what kind of control you can get with mermaid.js, considering there is likely going to be a lot of styling questions about it if we include it.  I was concerned particularly about the styling of the lines between boxes-- much of the documentation has curved lines.  I'm just going to paste this open Issue here for further reading for whoever starts working on this: https://github.com/mermaid-js/mermaid/issues/3260

Haven't really looked at it yet, what kind of style control does it give? does it allow for dashed and dotted lines? does it give control over the spacing between dashes/dots? can you put symbols in the lines? can you split a line halfway?

The styling appears to be determined by CSS, so ... yes.

So. Simple question. Do we want to solve this with CSS or mermaid?

A flowchart like this needs to be able to handle non-linear structure, so it seems like a better fit for Mermaid.

Okay. I'll beat on the mermaid plugin more.


Doesn't work with Fidelity's website

After you enter your credentials on Fidelity's website, you're asked for a code that gets texted to your cell.
The website blocks your ability to paste the code you received on your cell into the website. Overriding this with DFWP isn't working :(

@richardpowellus,
Sorry you're experiencing this problem. Unfortunately, I don't have a Fidelity account in order to figure out what's going on. One this to note: this extension make copy/cut/paste functionality work, but if the site is also interfering with the keyboard shortcuts associated to those actions this extension doesn't fix that. You should still be able to paste from the context menu (right click) or from the Edit menu.

Closing due to inactivity.


add docs-site to README

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

Current dependencies on/for this PR:

main

PR #144

PR #145   👈

This stack of pull requests is managed by Graphite.

Merge activity

Dec 27, 1:30 AM: @rphmeier started a stack merge that includes this pull request via Graphite.


[Why?!] What is the point of moving into HAWQ?

I have found libhdfs3 not so long ago and I loved it since the original libhdfs drove me crazy with its "java-business" and I tried to avoid it as much as possible.
The thing I liked even more about libhdfs3 is that it is an independent project with its own test suite and wiki/documentation. It is easy to pull libhdfs3 and fix bugs if any happens or build packages for third-party platforms (e.g. Anaconda).
Why do you merge a nice code-base into a bigger project?
P.S. By the way, I couldn't find any useful information about libhdfs3 following the link provided in README. I have even tried to search the HAWQ wiki, but nothing is there... :(

libhdfs3 is a component developed in hawq. Now hawq is in apache. And to have a release, apache has a requirement that apache project should have known standard dependencies. But libhdfs3 is not. Please see the discussion here<EMAIL_ADDRESS>And we will improve the doc in HAWQ for independent external usage.

Hmm, while I do understand the point of providing libhdfs3 binaries or static linking inside HAWQ package, I haven't found any reason for source files go into HAWQ code-base. Wouldn't git submodule solve the problem for the build-system?
NOTE: I'm not complaining or anything. Thank you for sharing this great project!

it looks a good idea to add libhdfs3 as a submodule, but the code needs to be in apache. otherwise, it is still a unknown dependency from apache side. currently, there is only one repo allocated in apache for hawq. we can explore the possibility to have another repo in apache.

Vote to close this issue and move further discussion here.


Math.abs(random.nextInt() % 99999999) in broker can be optimized

It should be replaced with ThreadLocalRandom.current().nextInt(99999999)

Merged


Add function to run_occlum_passed_test.sh

[x] Have you followed the guidelines in CONTRIBUTING.md?
[x] Have you formatted and linted your code?
[x] Have you added relevant tests?
[x] Have you added appropriate Fixes & Updates references?
[x] If yes, please erase all these lines!

TEST