[HOW-TO] prevent image auto adjusting

Please only ask one question per issue!
Describe what it is that you want to accomplish
I'm using a new v3 camera module in a small film scanner unit, and seeing something I don't quite understand, where each frame has some sort of adjustment going on. I think its focal, but as far as I can tell I've set to manual focus.  Even if the image is out of focus, I would prefer it to stay as-is, so that I can adjust the settings on the 20x magnification lens or the physical position of the camera itself.
Describe alternatives you've considered
I've looked through the manual PDF and tried tuning a few settings, and checked that the focus value isn't changing somehow, but the problem persists.
I'm using this little test:
from picamera2 import Picamera2, Preview
from libcamera import controls
import time
from time import sleep

Picamera2.set_logging(Picamera2.DEBUG)
picam2 = Picamera2()
picam2.start_preview(Preview.QT, x=100, y=200, width=1024, height=768)
picam2.start()
picam2.set_controls(
    {
        # controls for main frame: disable all regulations
        "AeEnable": False,  # AEC/AGC algorithm
        # disable noise reduction in main frame because it eats stars
        "NoiseReductionMode": controls.draft.NoiseReductionModeEnum.Off,
        # disable automatic white balance algorithm and set colour gains manually
        "AwbEnable": False,
        "AfMode": controls.AfModeEnum.Manual, "LensPosition": 10.0,
    }
)

while True:
  sleep(1)
  print(picam2.capture_metadata()['LensPosition'])

The while loop was just to check the position (which remains at 10), same issue without the loop. Issue remains with different lens position values.  Camera seems fine for normal 'long range' type shots.
Additional context
It seems each frame the image is different, perhaps these images help:

I don't think its related, but I seem to get a stack trace too, but I think this is just on the stream closing by the looks of it:
[Sat Mar 18 11:41:03 2023] Call trace:
[Sat Mar 18 11:41:03 2023]  __media_pipeline_stop+0x8c/0xa0 [mc]
[Sat Mar 18 11:41:03 2023]  media_pipeline_stop+0x34/0x50 [mc]
[Sat Mar 18 11:41:03 2023]  unicam_stop_streaming+0x78/0x170 [bcm2835_unicam]
[Sat Mar 18 11:41:03 2023]  __vb2_queue_cancel+0x3c/0x220 [videobuf2_common]
[Sat Mar 18 11:41:03 2023]  vb2_core_queue_release+0x2c/0x58 [videobuf2_common]
[Sat Mar 18 11:41:03 2023]  _vb2_fop_release+0x88/0xa8 [videobuf2_v4l2]
[Sat Mar 18 11:41:03 2023]  unicam_v4l2_release+0x58/0xe0 [bcm2835_unicam]
[Sat Mar 18 11:41:03 2023]  v4l2_release+0xc8/0x108 [videodev]
[Sat Mar 18 11:41:03 2023]  __fput+0x78/0x258
[Sat Mar 18 11:41:03 2023]  ____fput+0x18/0x28
[Sat Mar 18 11:41:03 2023]  task_work_run+0x88/0xe0
[Sat Mar 18 11:41:03 2023]  do_exit+0x320/0xa90
[Sat Mar 18 11:41:03 2023]  do_group_exit+0x3c/0x98
[Sat Mar 18 11:41:03 2023]  get_signal+0x87c/0x8d0
[Sat Mar 18 11:41:03 2023]  do_notify_resume+0x30c/0x448
[Sat Mar 18 11:41:03 2023]  el0_svc+0x80/0x88
[Sat Mar 18 11:41:03 2023]  el0t_64_sync_handler+0x98/0xc0
[Sat Mar 18 11:41:03 2023]  el0t_64_sync+0x18c/0x190
[Sat Mar 18 11:41:03 2023] ---[ end trace<PHONE_NUMBER>000000 ]---

In your set_controls you fix a lot of settings.
Have you tried to fix the ExposureTime?

Hi - thanks for the suggestion, unfortunately doesn't seem to have cracked it. I saw in the exposure_fixed example that analog gain was set too, so I tried adding:
"ExposureTime": 4000,
"AnalogueGain": 1.0,
(as well as without AnalogueGain being set) and issues persists same as before

Ah.. I might have found it.
I was trying libcamera-hello locally with a screen plugged in, and noticed the image wobble was alot quicker. I've got a fan mounted on the side of the case to keep the equipment inside, and it looks like this is causing some resonance. If I dampen things down with my hand, it seems alot better.


Have shuttle parse multiple ssh_config files

Requested by @skebi69
ssh_config files are ubiquitous it would be nice if shuttle could parse more than one file with ssh_config syntax.
Your system can only read the primary file ssh_config (unless to conjugated them into one) but it would be beneficial for shuttle to make menus from multiple ssh_configs
Possible example in shuttle's JSON
“Spouses Servers” : “ssh_config_file” = “~/.ssh/spouse_config"

+1

maybe a include option for another config file would be great. Something like:
"hosts": @include:myHostFile.json

I was thinking more of adding this to the global settings section something like:
"ssh_config_1": "~/.ssh/work-config",
"ssh_config_2": "~/.ssh/spouse-config"

"json_config_1": "~/.shuttle-work.json"
"json_config_2": "~/.shuttle-presonal.json"

+1 to adding ssh_config_1 to the global settings.

@skebi69 Thanks, I too think that this is the best way to handle this. I expect to get around to this sometime this summer.

I would also love to be able to define an alternate location for the .shuttle.json configuration; probably somewhere like ~/.config/shuttle/config.json so as to de-clutter my home directory from excessive dotfiles.

@cthoyt if your looking change the path of .shuttle.json you can do this here https://github.com/fitztrev/shuttle/wiki/Settings-and-Configuration it requires the creation of a dotfile
In your home directory create a file called ~/.shuttle.path In this file should be a single line with the path to the JSON settings file.

That's a nice tweak that I'm sure is useful for other purposes, but that would leave my +/- on the number of files in the home directory at 0 😂 Thanks for the help though

+1, at work we are required to symlink the shuttle config from a shared file, I'd like to add my personal entries to the menus (thus extending the default config file)

Starting with ssh 7.3 (released on August 1st, 2016), an Include directive is available in ssh config files.

Include: Include the specified configuration file(s). Multiple path names may be specified and each pathname may contain glob wildcards and shell-like "~" references to user home directories. Files without absolute paths are assumed to be in ~/.ssh. An  Include directive may appear inside a Match or Host block to perform conditional inclusion.

(Here is the link to the resolved bug report, that also includes the patch: https://bugzilla.mindrot.org/show_bug.cgi?id=1585#c24)
Would be nice if this was supported! It seems cleaner (and solves my use case, which is the same one as @Pimentoso's) than the proposed solution.

I have wrote a cli ssh connection manager which based on .ssh/config, so I have a heavily configured file. Today I found shuttle, docs say it will read ssh/config file, but I find it not. After I add some hosts to .shuttle.json, all the local port forwarding config is lost.

@lovelock I think this is a separate issue.

Hi @thshdw @fitztrev first of all, thanks for your awesome work on Shuttle so far.
I would like to take a look at this issue (support for ssh's Include directive). Would you be willing to merge if I submit a PR?

@otherguy @Pimentoso, check out #238 and let me know if this solves your use case.

Awesome! Thanks @julien-c

@julien-c awesome, thanks! 👍
Any way to get a new release (for my work computer)?


Issue:27

Issue: 27
Short description of what this resolves:
URL pattern for AnswerView
fixed typo of add_now to auto_now_add (pub_date as it is going to be constant always) in models.

    {
        "user": "sibashi",
        "created_at": "2022-12-22",
        "updated_at": "2022-12-22",
        "content": "dasdasdasdasdasd",
        "upvotes": 9,
        "downvotes": 3,
        "question_related": 1
    }

It gives question_related as the foreign key id ,
it would be better to return the question title instead
it should get changed by a small tweak at serializer or in view itself 🙂

done & tested
{
"user": "admin",
"created_at": "2022-12-22",
"updated_at": "2022-12-22",
"content": "xx",
"upvotes": 1,
"downvotes": 1,
"question_related": "ques1"
}

    {
        "user": "sibashi",
        "created_at": "2022-12-22",
        "updated_at": "2022-12-22",
        "content": "dasdasdasdasdasd",
        "upvotes": 9,
        "downvotes": 3,
        "question_related": 1
    }

It gives question_related as the foreign key id , it would be better to return the question title instead it should get changed by a small tweak at serializer or in view itself 🙂

done & tested
{
"user": "admin",
"created_at": "2022-12-22",
"updated_at": "2022-12-22",
"content": "xx",
"upvotes": 1,
"downvotes": 1,
"question_related": "ques1"
}


(Fix) - Identicons fix

Closes #955
Description:

After a long research I couldn't find why the migration to ts break the old blockies code. @fernandomg suggested that's something related with the bundle but we are not sure.
I tried with several dependencies, finally found this one (thanks Fer)

Travis automatic deployment:
https://pr1004--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1004--safereact.review.gnosisdev.com/app

This should not be merged, we need to use the component from safe-react-componentes.


Pointer events struggle on Windows Phone 10

Scrolling does not work on Windows Phone 10 (Windows Phone 8 OK). Pointer events and touch events seems to not cascade the same way on WP10.
Hot fix :
https://github.com/Mappy/iscroll/commit/d275166c64f24e41c7c701cd4d41fed4f7f11fbf
Thanks.

iscroll has a bug about pointer event binding.
if you use pointer event, you face a problem.
iScroll isn't actively maintained. so, I forked iscroll 5.1.3
https://github.com/naver/egscroll
you can download from bower
bower install egscroll#master

I hope that iscroll project will be activated.
but, I have no choice, now


BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.

When serving in a new Angular 16 project I get the following error:
./node_modules/json2csv/lib/JSON2CSVTransform.js:5:4-21 - Error: Module not found: Error: Can't resolve 'stream' in 'mypath\node_modules\json2csv\lib'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }

I get the same error 4 times for:
./node_modules/json2csv/lib/JSON2CSVAsyncParser.js:5:4-21 - Error: Module not found: Error: Can't resolve 'stream' in 'mypath\node_modules\json2csv\lib'
./node_modules/json2csv/lib/JSON2CSVBase.js:3:11-24 - Error: Module not found: Error: Can't resolve 'os' in 'mypath\node_modules\json2csv\lib'
./node_modules/json2csv/lib/JSON2CSVTransform.js:5:4-21 - Error: Module not found: Error: Can't resolve 'stream' in 'mypath\node_modules\json2csv\lib'
./node_modules/json2csv/lib/formatters/stringQuoteOnlyIfNecessary.js:1:11-24 - Error: Module not found: Error: Can't resolve 'os' in 'mypath\node_modules\json2csv\lib\formatters'

"json2csv": "^6.0.0-alpha.2",

Please see the new repo https://github.com/juanjoDiaz/json2csv

@knownasilya Thanks for the quick response.
Apologies I did not read the notice at the top in NPM.
Any instructions on how to install from here as I normally use npm install?

Figured it out
https://juanjodiaz.github.io/json2csv/#/quick-start
import { Parser } from '@json2csv/plainjs';


Refactoring suggestions

Here is the high level code review:

[ ] Only create one testController, not test controller per project
[ ] Do not flatten the folder hierarchy when listing files, users might want to run all tests in folder
[ ] Keep folder / file / suite tree items canResolveChildren = true so that UI did not expand them on load, but when resolveHandler is called, don't run playwright - you already have all the information.
[ ] Spawn npx instead of node + cli.js, explicitly use workspaceFolder for cwd. Don't run Node, don't assume cwd, that way we know we use workspace node and playwright.
[ ] Use vscode.workspace.findFiles('playwright.config.*') to locate configs, after that map configs to vscode.workspace.workspaceFolders, that's how you know where to run npx for these configs.
[ ] When serving the request to run tests, craft the command line that runs exact folder / file / suite / test
[ ] Create your own reporter --reporter=vsCodeExtensionReport.js. Create all ids in that reporter, you'll be using the same report when tests run. You'll anyways need a streaming one to report results dynamically.

I'll take a stab at some of the items, currently looking into the streaming reporter.


New IA Design implementation

User story
As a user, I want the ReportStream website to match my mental model.
Background & context
We don't know if the site is structured in a way that allows users to find what they need and complete the task at hand.  We don't have a scalable framework for launching and housing new features.
Primary purpose: Determine WHERE on the site all of this new information goes on the site and how it is organized.
Open questions

Specific implementation needs (until card sort and research is done)

Working links
Planning doc
##Acceptance criteria

[ ] Findings from previous IA work applied - specifics TBD

Close per Jillian


imagepipe: Don't know how to decode image

I want to convert ARW files to JPG format, and I used the command raw-to-img -o ./jpeg ./_DSC6738.ARW. However, I encountered the following issue:
Decoding "./_DSC6738.ARW"
Unable to decode "./_DSC6738.ARW": "imagepipe: Don't know how to decode image"
Found no files to process in "./_DSC6738.ARW"

What could be the problem?

I think there are three main issues here:

If you only convert one image raw-to-img expects a filename as -o parameter. It  might work with ./jpeg, but definitely not the way you would expect it to.
 Found no files to process in "./_DSC6738.ARW" is clearly wrong, as it has found files, but wasn't able to convert them. This bug should fixed in b76c180a3d8f382d55f3afef9c0e57fc2f552a5f, but it only regards the message.
As for your actual problem ("imagepipe: Don't know how to decode image") I am afraid I cannot help you without a sample file. I have tried converting an .ARW file without issue. Maybe your file is somehow corrupted?

I've uploaded a sample file on Google Drive Could you please help me test it?
Also, I'm using an M1 MacBook, and I'm not sure if that's relevant.

Hello, I can reproduce your issue. Sadly I think there is nothing I can do, except reporting the issue upstream. I will give you an update once I have opened a ticket there.
One other question just out of curiosity: Is this the only file you cannot convert or do you have the same issue with all your files?

I tried another file, which was taken with a Sony A7M3, and it converted successfully.

Thank you very much for your reply. So, I won't rush to use this component for now since I only have an A6400.


Make a tag invisible to ContentEdit

I want to show some information or inline tools in some elements as sub elements.
I can do this by registering an mount event listener and then add my custom stuff. But they should be invisible to ContentEdit and html() method of element should NOT include them.
I have read about Static elements but I don't think that is what I want.
One solution that I came up with was to add right click popup, but that does not give me the UI/UX  that I want.
What would be a good solution in this case?

So a number of the editable elements already do this type of thing (e.g Video and Image), this is done by having mount() do one thing and html() do another.
The best approach will be to override the html and mount methods against the class that you want to add this behaviour to (e.g ContentEdit.Text - I'm assuming this is at least one of the elements you want to customize). Remember though that behaviour is inherited so if that's a problem you may want to consider inheriting from the class instead and replace it in the tags names:
class MyNewElement extends ContentEdit.Text

    # My custom text elemment
    ...

# Associate my new class with all text elements
ContentEdit.TagNames.get().register(
    MyNewElement,
    'address',
    'blockquote',
    'h1',
    'h2',
    'h3',
    'h4',
    'h5',
    'h6',
    'p'
    )

Whether you override just the methods or the entire class you will need to change mount's behaviour to output more than html. For example if you're just looking to display information then you might consider the approach taken by images for size, here a data-... attribute is set against the element when mounted and that information is then displayed using a :before pseudo element and the CSS content: attr(data-...); rule, the attribute is not stored in the list of attributes for the element so on output html does not include this attribute.
If you need something more complex than this you will most likely need to mount additional DOM elements, and if so you'll also need to look at modifying the _syncContent method so that instead of the entire content of the text element being selected using this._domElement.innerHTML that any additional nodes mounted are excluded.
I hope this sets you in the right direction, I'm happy to provide more guidance but a concrete example of what you're attempting to do would be useful in providing more specific advice.

As you can see in the image, the control bar at top of my elements is not inside that element, its over it and I align them via javascript. it works fine but having them inside their corresponded element itself would be much better.
Now I should keep them visually and logically in sync (which I don't think is a good solution). I want to add other tools into that bar as well. Tools that are provided by the CMS.
So if there was an API that could give me the ability to add inline toolbar (or I would call it shadow element) to a element but never get included in html, then that would be more than great.
The image you see is a screenshot of the content form of my CMS

OK so support for attaching the toolbar to the current selected region has been suggested before and I think it will be a necessary task when we move to mobile, however I don't think I'd look to inline the toolbar inside the content itself, I think I'd do as you are doing now and use JavaScript to keep it's position and size in sync. Whilst this is more effort for the browser it's cleaner IMHO as it keeps ContentTools and ContentEdit decoupled. ContentEdit shouldn't need to know how to handle a ContentTools toolbar ideally.

Ok, so I will try to optimize my code to increase performance.
Thank you :)


Entry point is not getting set for example programs

I'm trying to build blinky example with default configuration. But it seems that the entry point is not getting set by the compiler.
Output of readobj:
➜  stm32f103xx-hal git:(master) ✗ cargo readobj --example blinky  -- -file-headers
    Finished dev [unoptimized + debuginfo] target(s) in 0.09s
ELF Header:
  Magic:   7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
  Class:                             ELF32
  Data:                              2's complement, little endian
  Version:                           1 (current)
  OS/ABI:                            UNIX - System V
  ABI Version:                       0x0
  Type:                              EXEC (Executable file)
  Machine:                           ARM
  Version:                           0x1
  Entry point address:               0x0
  Start of program headers:          52 (bytes into file)
  Start of section headers:          2108984 (bytes into file)
  Flags:                             0x5000200
  Size of this header:               52 (bytes)
  Size of program headers:           32 (bytes)
  Number of program headers:         3
  Size of section headers:           40 (bytes)
  Number of section headers:         16
  Section header string table index: 14

Output of size:
➜  stm32f103xx-hal git:(master) ✗ cargo size --example blinky --release -- -A
    Finished release [optimized + debuginfo] target(s) in 0.14s
blinky  :
section              size   addr
.debug_str          39258    0x0
.debug_loc           4323    0x0
.debug_abbrev        1993    0x0
.debug_info         40641    0x0
.debug_ranges        6200    0x0
.debug_macinfo          2    0x0
.debug_pubnames     11026    0x0
.debug_pubtypes     13001    0x0
.ARM.attributes        50    0x0
.debug_frame         1508    0x0
.debug_line         17848    0x0
.comment               18    0x0
Total              135868

We need a repo to reproduce your problem.
Try this: https://github.com/TeXitoi/blue-pill-quickstart

No, it depends on the version of cortex-m-rt that you are using in your Cargo.toml. The examples on this repo use 0.5, and blue-pill-quickstart use the last version 0.6.

Ok, so 0.5 is not working I guess. I'm going to stick with 0.6 for now. Thanks for the quick replies.

I didn't change the version or cortex-m-rt. It is 0.5.2, and the entry macro is used in the example. But it doesn't work (at least in macos).

I can analyze this if you give a full project, but as you have something working, that may not be important.


[RFC] Combine Appender.Add and AddFast into a single Append method.

This moves the label lookup into TSDB, whilst still keeping the cached-ref optimisation for repeated Appends.  Effectively we merge the two function into one that is given both the labels and any cached ref.  If the cached ref is valid, that is used - otherwise a (potentially new) series and ref is found/created using the labels.
This makes the API easier to consume and implement.  In particular this change is motivated by the scrape-time-aggregation work, which I don't think is possible to implement without it as it needs access to label values.
I don't believe this should have any performance impact, and am running benchmarks to confirm right now.
Signed-off-by: Tom Wilkie<EMAIL_ADDRESS>

Yeah, no impact on benchmarks - 4.49s vs 4.91s is within the noise for my computer.
➜  prometheus git:(append) ✗ git checkout master
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
➜  prometheus git:(master) ✗ go build ./cmd/promtool
➜  prometheus git:(master) ✗ ./promtool tsdb bench write --metrics=100000 tsdb/testdata/20kseries.json
level=info ts=2021-02-15T17:04:00.714396Z caller=head.go:668 msg="Replaying on-disk memory mappable chunks if any"
level=info ts=2021-02-15T17:04:00.71446Z caller=head.go:682 msg="On-disk memory mappable chunks replay completed" duration=5.395µs
level=info ts=2021-02-15T17:04:00.714467Z caller=head.go:688 msg="Replaying WAL, this may take a while"
level=info ts=2021-02-15T17:04:00.715027Z caller=head.go:740 msg="WAL segment loaded" segment=0 maxSegment=0
level=info ts=2021-02-15T17:04:00.715057Z caller=head.go:745 msg="WAL replay completed" checkpoint_replay_duration=32.219µs wal_replay_duration=551.153µs total_replay_duration=596.712µs
level=info ts=2021-02-15T17:04:00.716098Z caller=db.go:1388 msg="Compactions disabled"
>> start stage=readData
>> completed stage=readData duration=137.814505ms
>> start stage=ingestScrapes
ingestion completed
>> completed stage=ingestScrapes duration=4.492824812s
 > total samples: 60000000
 > samples/sec: 1.3354603087996313e+07
>> start stage=stopStorage
>> completed stage=stopStorage duration=137.387856ms

➜  prometheus git:(master) ✗ git checkout append
Switched to branch 'append'
➜  prometheus git:(append) ✗ go build ./cmd/promtool
➜  prometheus git:(append) ✗ ./promtool tsdb bench write --metrics=100000 tsdb/testdata/20kseries.json
level=info ts=2021-02-15T17:03:20.521251Z caller=head.go:668 msg="Replaying on-disk memory mappable chunks if any"
level=info ts=2021-02-15T17:03:20.521312Z caller=head.go:682 msg="On-disk memory mappable chunks replay completed" duration=4.531µs
level=info ts=2021-02-15T17:03:20.521319Z caller=head.go:688 msg="Replaying WAL, this may take a while"
level=info ts=2021-02-15T17:03:20.521667Z caller=head.go:740 msg="WAL segment loaded" segment=0 maxSegment=0
level=info ts=2021-02-15T17:03:20.521683Z caller=head.go:745 msg="WAL replay completed" checkpoint_replay_duration=32.636µs wal_replay_duration=326.064µs total_replay_duration=374.353µs
level=info ts=2021-02-15T17:03:20.5227Z caller=db.go:1388 msg="Compactions disabled"
>> start stage=readData
>> completed stage=readData duration=141.07832ms
>> start stage=ingestScrapes
ingestion completed
>> completed stage=ingestScrapes duration=4.915914142s
 > total samples: 60000000
 > samples/sec: 1.2205240251674764e+07
>> start stage=stopStorage
>> completed stage=stopStorage duration=123.654169ms

/prombench master

Thanks! I think it makes sense as Add was calling AddFast anyway.
cc @bwplotka as another consumer of the TSDB

/prombench cancel
Prombench is OK.

This change will introduce a major performance penalty in Cortex ingesters. The way it works in cortex is:

Labels are YOLO strings
We lookup our ref cache using series labels as YOLO
If the series is in the ref cache, we call AddFast(). However, it could fail. If it fail we do a copy of labels and call Add().

After this change, we don't know if labels will be retained or not by Append() so we'll always have to copy it. This will have a major performance penalty in the ingesters.

I am happy to revert this back for now and reconsider how can it be merged into a single method without hurting Cortex perf.

To give more context, when we introduced the ref cache in Cortex ingesters (using labels as YOLO strings to lookup the cache), memory allocations were reduced by -25%:
https://github.com/cortexproject/cortex/pull/2057

PR to revert this https://github.com/prometheus/prometheus/pull/8519

We lookup our ref cache using series labels as YOLO

Can you store another copy of the labels in the ref cache?  This is effectively what Prometheus does (store a copy of the labels in the scape cache, and use them on subsequent calls to Add).

Can you store another copy of the labels in the ref cache? This is effectively what Prometheus does (store a copy of the labels in the scape cache, and use them on subsequent calls to Add).

Good point. Yes, we should be able to solve it this way.

Let me know if this works! If not we can find another way.  I'd not that if you know the ref, you can pass null for the labels... but this is abusing the code a bit...

Yes, this is impacting Thanos a bit as well, I believe this PR could be done more carefully instead of merging so quickly. Let me schedule some experiment on Thanos side.

I hadn't noticed this change, but came up with an idea to remove the refcache - see #8600 and https://github.com/cortexproject/cortex/pull/3951

Am I right in thinking the only way a reference can become invalid is via head compaction?

Am I right in thinking the only way a reference can become invalid is via head compaction?

Yes


arc distance in knnW

I may be missing something, but it seems to me that knnW in Distance.py is assuming that the distances are Euclidean and does not allow for arc distances. In practice, this will likely seldom come up as a problem, since, e.g., knnW_from_array (in user.py) takes a radius argument and passes a distance_metric argument to pysal.cg.KDTree before calling the worker bee knnW function, thus passing the correct KDTree.
However, when knnW is called directly (in Distance.py) there doesn't seem to be a way to pass a distance_metric argument and when only an array of coordinates is provided, the KDTree is called with only one argument (u) - on line 122.
Does this need to be addressed or is it taken care of in another way? One way to deal with this is to restrict knnW to always take a KDTree as an argument and remove the option to pass an array. This would then require a small helper function that creates the tree and deals with the distance_metric argument.

What about adding the arcdistance=False flag to the knn function.  If arc distance is passed as true, we can either (1) unpack the data from the current KDTree and load a ps.Arc_KDTree or (2) take the array and create a ps.Arc_KDTree?  If this check occurred prior to the current if (line 111 in Distance.py) we could first check for arc, then for a subclass, and finally for datatype.  This should maintain the logical ordering.
I can make this change if it looks like it will serve.

+1 on the change. I think this would allow knnW to use arc distances if needed.

Now that I am digging in wanted to bounce some ideas around:

In order to use the arc distance, we need to provide a radius.  Right now this defaults to 1.0, but suspect that most people will want to specify ~6371.0(km).  This would mean that supporting arc distance via this method would require the addition of arcdistance=False and radius=1.0.  This is becoming less of a clean addition.

Some options:

Accept an optional **kwargs and pass through.  I dislike this because it is significantly less clear to the user what is going on.
Include both kwargs.  Not a huge fan of adding two flags.  The user could pass arc distance and never specify radius.  With r=1.0 the issues at the poles with KDTrees are likely to still be present.
Include just the radius option.  If you pass a p argument, we use euclidean and if you pass a radius argument we use arc distance.  I like this as it is only a single change, but it makes the API a little less clear.

The coincident point check used for raw data makes a lot of sense.  We can abstract that out into a private method so that it only exists in a single place.  Right now, I see the addition of two if/else statements: (1) if radius and isinstance(data, pysal.cg.KDTree) we unpack the data and create a new ArcKDTree and (2) if radius and isinstance(data, (np.ndarray, np.generic) we simply create a new ArcKDTree.

Do we add the coincident point check in both instances?  I think we should, but this is not something that we do if the user passes in an already created KDTree.

I think adding the optional kw parameter radius=None is the cleanest solution. If that is specified with a radius then arc distance is used.
I'm not sure about the second point you are raising. Presumably, if the user wants to use arc distances, the tree should be built with ArcKDTree - they wouldn't have constructed a regular KDTree and then passed that in as the first argument to knnW. Maybe I'm missing what you are getting at?

On the second point, we support passing in a KDTree.  Should the logic be, if data is a KDTree (not an ArcKDTree) and radius is specified, we throw an error or should we try to handle that by unpacking the existing KDTree and repacking into an ArcKDTree?
Assuming we want to support that (for the confused user), do we run the coincident point check as well during the unpack, repack process?

Maybe Luc's original suggestion is cleaner?

change the API for knnW to take only a KDTree as an argument. Internally we can then check if its arc based or euclidean and do the correct thing

add small helper functions to build the trees.

Given the philosophy of PySAL as a library, I think it would be cleaner to let knnW just build the weights, given a KDTree as the argument. How that KDTree is constructed (Euclidean or Arc) is not considered by knnW. In fact, this is pretty much what happens in practice when one of the knnW_ user functions is invoked. They take care of the logic of array to KDTree conversion using the correct distance metric.
So I would argue for restricting knnW proper to only allow a KDTree as an argument, making it agnostic to how that tree is constructed and adding a couple of specific array to tree conversion function (to the extent that they are not there already).
I think right now there is a bit of tension between the objective of knnW being a core ("base") function and its design as more of a user function (with all the checks). What we've tried to do in spreg (although it's by no means perfect) is to limit the options and arguments for the base functions to the absolute minimum, and do all the checking and alternative entry points in the user function/class.

This example demonstrates how we can currently first build a KDTree using spherical coordinates and then pass it to knnW. If you load the linked files into qgis and follow along you will see that the calculations are correct in terms of distances.
So changing the api of knnW proper as @lanselin suggests seems a good way to go.


Enhance test coverage (topological, utils)

Better test coverage for:

[x] Topological collector
[x] Collector utils

:heavy_plus_sign:  Simplified a bit of topological worker by refactoring duplicate code.
:arrow_forward: From 25 test cases to 76 :+1:

Codecov Report

Merging #45 into master will increase coverage by 27.28%.
The diff coverage is 98.45%.

@@             Coverage Diff             @@
##           master      #45       +/-   ##
===========================================
+ Coverage    54.4%   81.68%   +27.28%
===========================================
  Files          15       17        +2
  Lines         500      748      +248
===========================================
+ Hits          272      611      +339
+ Misses        228      137       -91

Impacted Files
Coverage Δ

tests/collector/test_utils.py
100% <100%> (ø)

tests/collector/test_topological_inventory.py
100% <100%> (ø)

collector/topological_inventory.py
93.69% <55.55%> (+68.91%)
:arrow_up:

collector/utils.py
95% <0%> (+32.5%)
:arrow_up:

Continue to review full report at Codecov.

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

Looks great! Merging...


feat(event-edit): updated icon color

Description
Please include a summary of the change.
fixes # (issue)
Screenshots
If applicable, add screenshots about your changes
Type of change
Please delete options that are not relevant.

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

How to test it
If applicable, describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Go to '...'
Click on '....'
Scroll down to '....'

Checklist:

[ ] Doesn't break the current code.
[ ] Passes linters and test, also is building.
[ ] Doesn't have spelling or grammatical problems.
[ ] Doesn't have unnecessary comments or debugging code.
[ ] The branch is updated with the last dev branch changes.

Review completed, icon has changed color. Good work.


Fix detection of editable packages

Introduced in #1812. The values aren’t always dict, but can be strings… Also fix the editable_dev_packages call that is probably also wrong.

Hm yeah I keep forgetting people hand generate pipfiles.


Raid boss not workin in raids/dungeons after patch

After the most recent update my raidboss alert and timeline do not initiate in dungeons or raids what so ever. They work fine in Summerford farms. I already reinstalled and built everything the way I had it before.

You need an updated ffxiv plugin.  This will happen after every patch.

Awesome thank you 👌🏽


AppIntro runs everytime I open the app

AppIntro Version: 4.2.2

Device/Android Version: Works great on every device. I use Yu Yureka as physical and Nexus 5X as emulated device for testing.

Issue details: I've implemented how to run the AppIntro slides only for the first time from the AppIntro Wiki. I also added the Manifest declaration  but still, everytime I open the app from my physical or emulated device, it runs each time! How do I resolve this?

Your Code: My MainActivity.java (actually it's EarthquakeActivity.java)-
//Start the intro slide with an intent
        Intent intent = new Intent(this, IntroActivity.class);
        startActivity(intent);

        /* Start the intro only once */
        //  Declare a new thread to do a preference check
        Thread t = new Thread(new Runnable() {
            @Override
            public void run() {
                //  Initialize SharedPreferences
                SharedPreferences getPrefs = PreferenceManager.getDefaultSharedPreferences(getBaseContext());

                //  Create a new boolean and preference and set it to true
                boolean isFirstStart = getPrefs.getBoolean("firstStart", true);

                //  If the activity has never started before...
                if (isFirstStart) {

                    //  Launch app intro
                    final Intent i = new Intent(EarthquakeActivity.this, IntroActivity.class);

                    runOnUiThread(new Runnable() {
                        @Override public void run() {
                            startActivity(i);
                        }
                    });

                    //  Make a new preferences editor
                    SharedPreferences.Editor e = getPrefs.edit();

                    //  Edit preference to make it false because we don't want this to run again
                    e.putBoolean("firstStart", false);

                    //  Apply changes
                    e.apply();
                }
            }
        });

        // Start the thread
        t.start();

My Manifest file-
<activity android:name="com.example.android.quakereport.IntroActivity"
            android:label="@string/app_intro" />

I've added a new String resource in Strings.xml-
<string name="app_intro">Intro</string>

I'm sorry, but this is not an AppIntro issue -- yes, looks like the wiki needs to be expanded further for those that are making use of preferences for the first time, but we can't take the time to guide everyone who uses the library on how to open an activity only when needed.
Stackoverflow has plenty of questions regarding this subject and it is the resource I recommend all developer to query (not post).


[Docs] Improve README documentation

Hi @CrisGrud, let's use this issue to track what we think needs to be added to the initial documentation.
There is a branch dedicated for this: update-documentation
Each time the branch requires work first let's sync it with main branch.

:tada: This issue has been resolved in version 1.29.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Printbed Cardboard Spool

Printbed PLA
1 kg Spool
Print temp varies, for plack it's ~210C
50C Bed temp
64mm Wide
200.4mm tall (outer Diameter)
57.4mm Hole diameter
High gloss PLA, manufactured in Sterling Heights, MI, can order in 200g, 1kg, 5kg spools. has indicator opening on side, displaying how much approx filament left, does not have any filament retaining systems (ships with a sticker to keep end of filament in place)

Thanks, will try to add this week (a bit busy right now)
y.

I completely forgot about this, will get to this soon. Thanks again and apologies

No need to apologize to me my man! Love the work you're doing!
On Fri, Aug 2, 2024, 9:47 AM jtrmal @.***> wrote:

I completely forgot about this, will get to this soon. Thanks again and
apologies
—
Reply to this email directly, view it on GitHub
https://github.com/jtrmal/spoolz/issues/18#issuecomment-2265440853, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHOFBOGUUYWOF6RXBDDO24LZPOEVXAVCNFSM6AAAAABHY7T3OWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRVGQ2DAOBVGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Merged, thank you!


Docs: document message order on queues issue

On the standard address space, message order is not guaranteed on queues.
On the brokered address space, released messages can lose their order.

PR https://github.com/EnMasseProject/enmasse/pull/1970

PR merged


Add webhook notifications for admins when a seller submits a plugin for approval

Until now the only way for an admin to know when a plugin is waiting for approval was to look at it on the page or if the seller sends you a message, this code automatically notificates the admin when a new plugin is waiting for approval.


LegionProf: missing tasks with -s

On control_replication, doing
legion_prof.py -s /home/bandokihiro/Public/DebugLegionProf/prof_0.gz

misses one of my task iface_residual_task. For example, reverting back to commit f96e7d2562db0abbeda05f60237e2bf1456004c5 fixed it.
Feel free to use this file on sapling to reproduce.

I am using the legion prof summary to measure the performance of my tasks and one task of interest is missing because of this bug. Is there an ETA on a fix?

I am using the legion prof summary to measure the performance of my tasks and one task of interest is missing because of this bug. Is there an ETA on a fix?

I'll look at it today

I'll look at it today

pushed a fix in master https://gitlab.com/StanfordLegion/legion/-/commit/343ba085b05e54012df54e6fa4887fa57f92d5ef

pushed a fix in master https://gitlab.com/StanfordLegion/legion/-/commit/343ba085b05e54012df54e6fa4887fa57f92d5ef

fixed, thanks

fixed, thanks


Support Typescript

While writing the types, I noticed the return values of makeCCW and removeCollinearPoints where undocumented, so I amended the readme.

@schteppe it would be awesome to have these typedefs! Could you merge this PR and publish a new version to npm?


Text selection Issue - when dragging past the end-of-line

Attach (recommended) or Link to PDF file here: compressed.tracemonkey-pldi-09.pdf
Configuration:

Web browser and its version: Chrome Version 77.0.3865.90 (Official Build) (64-bit)
Operating system and its version: Windows 10 Pro (64 bit)
PDF.js version: Latest on PDF.js Demo (2.3.198)
Is a browser extension: No

Steps to reproduce the problem:

Go to https://mozilla.github.io/pdf.js/web/viewer.html
Wait for the example document to load (compressed.tracemonkey-pldi-09.pdf)
Place the mouse pointer on the first text line of the second text column, starting with "and is used for"
Drag the mouse to the end of the second line, ending with "Zimbra Col-", selecting the text in the process.
Move the mouse further out to the right, towards the right side edge of the document
Observe the selection highlight, selecting either remaining text above or below the mouse pointer.

What is the expected behavior? (add screenshot)
Text selection highlight should be inline with the horizontal of the mouse (this is how PDF viewers and google pdf viewer highlights). So when the mouse moves beyond the end of the line, the highlight still remains inline with the mouse. This makes the selection more predictable and easier to use; especially for those with accessibility issues.
Fox Reader - Highlight Example (pointer wasn't grabbed by the screenshot)

Chrome PDF Reader - Highlight Example (pointer wasn't grabbed by the screenshot)

What went wrong? (add screenshot)
Highlighting function selects remaining text, above or below, the starting position - depending on the mouse location - when the drag selection is past the line return.

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): https://mozilla.github.io/pdf.js/web/viewer.html

Probably a duplicate of e.g. issue #9843.

I already tried:
PDFViewerApplication.preferences.set('textLayerMode', 2);
but it does not solve the issue


Spelling Mistake Fix

Modify exmaple to example

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jingze seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


toObservable followed by toSatisfyOnFlush created double calls.

  describe('toSatisfyOnFlush', () => {
    it('should verify mock has been called', () => {
      const mock = jest.fn();
      const coldObservable = cold('blah|');
      const stream$ = coldObservable.pipe(tap(mock));
      expect(stream$).toBeObservable(coldObservable);
      expect(stream$).toSatisfyOnFlush(() => {
        expect(mock).toHaveBeenCalledTimes(4);
      });
    });
  });

This test fails with call times actually 8 not 4. Even though it technically can be understandable, is is not intuitive when reading the test.
workaround is to separate this into 2 separate tests.

What I did was to put the toBeObservable Code inside the toSatisfyOnFlush block. But I agresse, it is counterintuitive.
      expect(stream$).toSatisfyOnFlush(() => {
          expect(stream$).toBeObservable(coldObservable);
          expect(mock).toHaveBeenCalledTimes(4);
      });

I came here for the same problem, I followed your suggestion @Blafasel3, but when inside the toSatisfyOnFlush(), the expect().toBeObservable() always pass, whatever the coldObservable I'm testing...
For instance, this fails as expected, but triggers the observable several times :
    const stream$ = hot('a', { a: myAction(payload) });
    const coldObservable = cold('b', { b: undefined });

    expect(stream$).toBeObservable(coldObservable);
    expect(stream$).toSatisfyOnFlush(() => {
      expect(mock).toHaveBeenCalledTimes(4);
    });

But this pass while it shouldn't:
    const stream$ = hot('a', { a: myAction(payload) });
    const coldObservable = cold('b', { b: undefined });

    expect(stream$).toSatisfyOnFlush(() => {
      expect(stream$).toBeObservable(coldObservable);
      expect(mock).toHaveBeenCalledTimes(4);
    });

I have other asserts in the toSatisfyOnFlush that fail when I change them, so I don't understand why the expect doesn't fail...
I'm using Jest 28.1.3 & jest-marbles 3.0.2

@killergege Interesting, I'll take a look.

I came here for the same problem, I followed your suggestion @Blafasel3, but when inside the toSatisfyOnFlush(), the expect().toBeObservable() always pass, whatever the coldObservable I'm testing...
For instance, this fails as expected, but triggers the observable several times :
    const stream$ = hot('a', { a: myAction(payload) });
    const coldObservable = cold('b', { b: undefined });

    expect(stream$).toBeObservable(coldObservable);
    expect(stream$).toSatisfyOnFlush(() => {
      expect(mock).toHaveBeenCalledTimes(4);
    });

But this pass while it shouldn't:
    const stream$ = hot('a', { a: myAction(payload) });
    const coldObservable = cold('b', { b: undefined });

    expect(stream$).toSatisfyOnFlush(() => {
      expect(stream$).toBeObservable(coldObservable);
      expect(mock).toHaveBeenCalledTimes(4);
    });

I have other asserts in the toSatisfyOnFlush that fail when I change them, so I don't understand why the expect doesn't fail... I'm using Jest 28.1.3 & jest-marbles 3.0.2

Oh, I never actually tested that. Thanks for pointing that out!


MOUSE ACCELERATION.

Description of the new feature / enhancement
I'd like the mouse wheel be able to scroll faster by spinning the mouse wheel faster.
Scenario when this would be used?
In Excel the  default mouse speed in too fast if you have row heights that are taller than normal.
It would be nice to have the page scroll one (or even fewer) line at a time when the mouse wheel moved slowly.
I believe this functionality comes with certain mouses (mice?).
There are lot of other scenarios but I think you get the point.
Supporting information
No response

/dup #5088


Don't depend on the cache contents for simplifying joined trees

@raulraja please take a look.
This opens the door to using custom caches that don't remember all the elements, for instance caches with an LRU policy. Also if we where using a custom remote cache (like memcached) that is unreachable and thus we cannot read from it (return None from DataSourceCache#get), fetches will continue without problem querying the data source.
Previously wasn't possible to use a custom cache that forgot elements so I'd like to cut a release with these changes.
Closes #47

LGTM!


wp remove index

This is to remove passing in index so it doesn't override the index when doing sheer reindex.

@cfarm Sorry for being bad on doing this PR in a non-standard way.  Basically the line that was removed will override the setting we have for index, so it will cause journey to look at an incorrect index.
Please add to this if I misspoke @rosskarchner


Can't load manga from 'Merged Source'

Look like Neko needs new workaround for their "anti-hotlinking"?
Device information

Tachiyomi version: <IP_ADDRESS>

Steps to reproduce

Find manga with mergeable chapters (for my case: Übel Blatt)
Merge with M4L (the only alternative source Neko provide)
Trying to read Merged Chapters

Expected behavior
The manga should be loaded fine, like reading from their site

Actual behavior

Other details

Tried with DoH On/Off
log, with me trying to read some chaps from merged source and Chapter 161 from MD at the end.

Has nothing to do with hotlinking.  Mangalife is blocking tachi and neko at this time.

fixed in <IP_ADDRESS> with a harsh rate limiting.

How to fix this?

Has nothing to do with hotlinking

before i open this issue, i got caught in CF's anti-hotlink (error 1020) every single times. so, i just assume that. lol

Mangalife is blocking tachi and neko at this time.

this might be it, since "now" i seems to be able to hotlink M4L's mangas fine on browser. yet Neko <IP_ADDRESS> still can't load.

can't fix at this time.  The owner said they would unblock tachi/neko once Dex is more stable.

It's been unblocked I'll need to lower the rate limit a little though it's pretty slow


Incorrect personalization flag attributes

Issue in ./help/web-sdk/personalization/display-events.md
On this page, there are mentions of personalization.sendDisplayNotifications and personalization.includePendingDisplayNotifications flags, but I don't see these flags in the alloyJS code.  I am guessing these should be personalization.sendDisplayEvent and personalization.includeRenderedPropositions. Please clarify and add corrections to the docs if needed.

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-212878.

We've updated the documentation with the correct attributes. Closing the issue.


[Feature][UI Next][V1.0.0-Alpha] Fix startup global params not init bug

close #8741

Codecov Report

Merging #8749 (f7a638c) into dev (6e2c2ad) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #8749      +/-   ##
============================================
- Coverage     45.30%   45.29%   -0.02%
+ Complexity     4077     4075       -2
============================================
  Files           702      702
  Lines         27112    27112
  Branches       2897     2897
============================================
- Hits          12284    12280       -4
- Misses        13676    13678       +2
- Partials       1152     1154       +2

Impacted Files
Coverage Δ

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.70% <0.00%> (-2.82%)
: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 6e2c2ad...f7a638c. Read the comment docs.


BloodEffect On monster take damage

monster now flash and display blood effect when take damage.

No. We did not intend on adding blood effects this way.


python310Packages.pypiserver: 1.5.1 -> 1.5.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pypiserver is: Minimal PyPI server for use with pip/easy_install
meta.homepage for python310Packages.pypiserver is: https://github.com/pypiserver/pypiserver
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.2 with grep in /nix/store/vy0ll9akwzvfb59k38pdmzah4jjdcb3c-python3.10-pypiserver-1.5.2
found 1.5.2 in filename of file in /nix/store/vy0ll9akwzvfb59k38pdmzah4jjdcb3c-python3.10-pypiserver-1.5.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
pypiserver
python310Packages.pypiserver
python311Packages.pypiserver

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vy0ll9akwzvfb59k38pdmzah4jjdcb3c-python3.10-pypiserver-1.5.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pypiserver https://github.com/r-ryantm/nixpkgs/archive/2e4bd78a4690654e15f6d0345170c80fc5d60021.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vy0ll9akwzvfb59k38pdmzah4jjdcb3c-python3.10-pypiserver-1.5.2
ls -la /nix/store/vy0ll9akwzvfb59k38pdmzah4jjdcb3c-python3.10-pypiserver-1.5.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

pypiserver (python310Packages.pypiserver)
python311Packages.pypiserver

Maintainer pings
cc @austinbutler for testing.

Result of nixpkgs-review pr 247898 run on x86_64-linux 1

4 packages built:

pypiserver (python310Packages.pypiserver)
pypiserver.dist (python310Packages.pypiserver.dist)
python311Packages.pypiserver
python311Packages.pypiserver.dist


Update core: SA-CORE-2021-002

Summary

Metadata

Question
Answer

Did you use a meaningful pull request title?
yes/no

Did you apply meaningful labels to the pull request?
yes/no

Did you perform a self review first?
yes/no

Documentation reflects changes?
yes/no

CHANGELOG reflects changes?
yes/no

Unit/Functional tests reflect changes?
yes/no

Did you perform browser testing?
yes/no

Risk level
Low, Medium, High

Relevant links
JIRA issue, bug reports, security alerts, etc.

Looks good!
/approved


Incorrect code marked correct

The following code was marked correct in  challenges/waypoint-create-bootstrap-wells
http://www.freecodecamp.com/challenges/waypoint-create-bootstrap-wells

jQuery Playground

Dear camper, your issue is related to:
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/2541
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/2417
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/2399
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/2398
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/2393
Please see Help I've Found a Bug.

Hey @AEA2002 why shouldn't that be marked as correct?

@benschenker
There should only be two class="col-xs-6" divs
Also there  a extra div with class="well" (third line)

Closing as this has been merged in #3129


Support External Elasticsearch

Deprecate existing STF-deployed ES
New CRD properties for external ES
Adjust SG and Grafana to use new vars

This passes smoke tests with OBSERVABILITY_STRATEGY=use_hybrid and an STF deployment to match. I can see from the smoketest logs that events were flowing:
*** [INFO] Get documents for this test from ElasticSearch...
[2023-06-12 19:12:05] Notification: severity = OKAY, host = stf-smoketest-smoke1-qc9rx, plugin = interface, plugin_instance = lo, type = if_octets, message = Host stf-smoketest-smoke1-qc9rx, plugin interface (instance lo) type if_octets: All data sources are within range again. Current value of "rx" is 0.000000.
*** [INFO] Found 34 documents

This means that all the new ext* usage in the templates and the default values are all aligned and haven't broken anything. I haven't actually tested connecting to a non-STF deployed ES yet, though.

I just tested grafana (same use_hybrid setup as above) and it works after some fixes. Both ES data sources pass the "Save and Test" in Grafana.
Working on a true test of a separately deployed ES next.

This has now been tested with an independently deployed Elasticsearch and observabilityStrategy: use_redhat. I deployed Elasticsearch via ECK in another namespace and created a route that leads to it so I could connect the smartgateway via that "external" route.
Here is my ES config in the STF object:
$ oc get servicetelemetry default -o jsonpath='{.spec.backends.events.elasticsearch}' | jq
{
  "enabled": true,
  "extHostUrl": "https://es-route-es.apps.ocp413-csibbs.<...>.redhat.com",
  "extTlsSecretName": "es-ca",
  "extUseBasicAuth": true,
  "extUseTls": true,
  "extUserSecretName": "es-user"
}

Construct the TLS secret like this (just the required CA cert here, but it can also contain an mTLS cert + key):
$ openssl s_client -servername es-route-es.apps.ocp413-csibbs.<...>.redhat.com -connect es-route-es.apps.ocp413-csibbs.<...>.redhat.com:443 -showcerts

[ COPY/PASTE THE SIGNING CERT INTO ES-CA.pem ]

$ cat ES-CA.pem | openssl x509 -text | grep CN
        Issuer: CN = ingress-operator@1680638728
        Subject: CN = ingress-operator@1680638728

$ oc create secret generic es-ca --from-file=ca.crt=ES-CA.pem
secret/es-ca created

Construct the User Secret for BasicAuth like this:
 oc create secret generic es-user --from-literal=elastic=$ESPASS

I get a working system with two events SGs both connected to Elasticsearch:
$ oc get po | grep event
default-cloud1-ceil-event-smartgateway-7f9986698c-t6js9   2/2     Running     0          5m
default-cloud1-coll-event-smartgateway-656dd6b875-2fpdn   2/2     Running     0          5m

$ oc logs default-cloud1-ceil-event-smartgateway-7f9986698c-t6js9 -c sg-core
2023-06-20 03:37:36 [INFO] initialized handler [transport pair: socket0, handler: events]
2023-06-20 03:37:36 [INFO] loaded transport [transport: socket0]
2023-06-20 03:37:36 [INFO] loaded application plugin [application: elasticsearch]
2023-06-20 03:37:36 [INFO] storing events and(or) logs to Elasticsearch. [plugin: elasticsearch, url: https://es-route-es.apps.ocp413-csibbs.<...>.redhat.com]
2023-06-20 03:37:36 [INFO] socket listening on /tmp/smartgateway [plugin: socket]

Unfortunately the smoketest won't pass against my external ES setup because it has hard-coded endpoint and secret name values. (Existing automated smoketests in use_hybrid mode should continue to work fine with the defaults)

test

Depends-On: https://github.com/infrawatch/smart-gateway-operator/pull/142

Going to have to spend some time going through the changes and looking at them, but I did another quick pass for anything syntactically weird, and all of that looks good to me.

test

test

I think I'm done with this now. I would appreciate additional review so I can merge it. It's passing CI and it passes my local testing as shown above (I redid basically the same thing with the newly moved parameters). I will be following up this work with adjustments to CI testing that actually exercise the events system again based on this work (currently we are just testing metrics)  and any additional problems should get shaken out during that work.

I think I'm done with this now. I would appreciate additional review so I can merge it. It's passing CI and it passes my local testing as shown above (I redid basically the same thing with the newly moved parameters). I will be following up this work with adjustments to CI testing that actually exercise the events system again based on this work (currently we are just testing metrics) and any additional problems should get shaken out during that work.

I have this on my list of tasks for tomorrow. I will be sure to go through this thoroughly before I am out on Friday.

Before I merge this, I'd like to do the following test:

Install STO from master and deploy w/ use_community (like existing STF 1.5 installs)
Update to the version from this branch
Change to use_redhat
Check that everything continues to work
Remove the ES config (other than "enabled") - Expect no effect, continues to work

I understand that we are deprecating all the params related to STF managed ES. I assume that after some releases, we will remove those params from this CRD. Is there a way to mark those params as deprecated officially?

Yes, the intention is probably to remove support for them in STF 1.5.4. I don't know of any way to mark them deprecated "offifically" but I'll do some more spec reading and maybe ask someone who is closer to OLM.

Should we update versioning somewhere?

Haha, yes, probably. It looks like our CRD is still saying "v1beta1". I am personally a big fan of using semantic versioning to signal feature additions and backwards-incompatibility, but AFAICT we have never observed any sort of conventions here for our CRDs, and I feel like other operators are in the same boat. Maybe I've just been ignorant. @leifmadsen do you have any idea about this? Should I bump this to "v1beta2", for example, and then we make it "v2" when we remove support for managing the community ES deployment?

What would be the preferred upgrade path for STF users? Do we expect them to create an external instance for ES, migrate they data, and then point the STF object to that ES instance?

For existing users with existing event data, upgrading will cause STF to stop managing the ES object, but otherwise nothing else will change. Users will be able to modify the ES object and rely on the community ECK operator to deal with it instead of having it flow through STF.

I see Leif and you discussing the three scenarios of hybrid, community or redhat, why do we make that distinction? External is external, no matter what is the source, no?

We are talking about the observability_strategy parameter, which can be set to:
none - only deploy smart gateways, no PromOp, no ECK, no grafana
use_community - Community PromOP, ECK, and grafana - this is the current way that all STF 1.5.1 installs are done
use_redhat - PromOp from RHOBO, no ECK, no grafana - this is the "fully supported install" we are trying to achieve
use_hybrid - PromOp from RHOBO, plus Community ECK, and grafana - ECK integration remains deprecated and support for managing the ES object will be removed from a future release.
Forwarding to an external ES should work in all cases. The testing and discussion has been around ensuring that is the case.

I understand that we are deprecating all the params related to STF managed ES. I assume that after some releases, we will remove those params from this CRD. Is there a way to mark those params as deprecated officially?

Yes, the intention is probably to remove support for them in STF 1.5.4. I don't know of any way to mark them deprecated "offifically" but I'll do some more spec reading and maybe ask someone who is closer to OLM.

I think this is something we can bring to the PM. I'm not sure if we should remove functionality in STF 1.5 or not. I would agree that STF 1.5.4 is probably the proper target if we communicate it correctly. Having the ability to "orphan" the existing managed deployment during the STF 1.5.3 cycle and updating the CR in-place (manually or otherwise) to switch to a forwarding mechanism should allow us to do this. We can then remove the related Ansible tasks and simplify the CRD.
I'm adding it to my list of discussion items for next week with PM.

Should we update versioning somewhere?

Haha, yes, probably. It looks like our CRD is still saying "v1beta1". I am personally a big fan of using semantic versioning to signal feature additions and backwards-incompatibility, but AFAICT we have never observed any sort of conventions here for our CRDs, and I feel like other operators are in the same boat. Maybe I've just been ignorant. @leifmadsen do you have any idea about this? Should I bump this to "v1beta2", for example, and then we make it "v2" when we remove support for managing the community ES deployment?

So I am also a fan of semantic versioning where possible, but I've found CRDs are a bit different. I swear I had found something at one point that somewhat discouraged changing CRD versions in certain ways, like simply extending the API interface, and only changing the version if the interface changed in such a way that existing CRs would no longer be compatible. I have yet to find such a document. Perhaps that was a Leif-ism...
At one point I did change the version of the CRD. It moved from v1alpha2 to v1beta1. Unfortunately that was a bit of a nightmare, because Ansible Operators don't have the ability to do webhook conversions, which is the interface that allows you to write a controller and do automatic in-place migrations of Custom Resources to the latest CRD.
See https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/
Also since we have to self-manage the CRD instead of having them generated with decorators in the code, along with some other nice things you get when running a Golang operator, it seemed to make the version changing more overhead than it seemed to be worth.
So should we have better CRD versioning and not be afraid of increasing the versions when we make significant changes? Likely yes. Is it really worth the overhead to self-manage and make sure we don't break existing production deployments during a z-stream? Possibly not.
With that being said, I think STF 2.0 should be a fresh start to our CRD, and we should absolutely create a v2 CRD and remove items we consider legacy, and come up with a possibly cleaner interface. We'll need to have an architectural discussion about how we'll migrate from v1 to v2 CRD, since we're not going to have the benefits of having webhook conversions to do manage the migrations for us.

What would be the preferred upgrade path for STF users? Do we expect them to create an external instance for ES, migrate they data, and then point the STF object to that ES instance?

For existing users with existing event data, upgrading will cause STF to stop managing the ES object, but otherwise nothing else will change. Users will be able to modify the ES object and rely on the community ECK operator to deal with it instead of having it flow through STF.

+1
New deployments would configure the forwarding section along with setting observabilityStrategy: use_redhat which gets them OBO + unmanaged ES (forwarding). As of STF 1.5.4 I think we can just remove the community bits from our code base and simply have use_redhat and none as the observability strategies.
This is something else I'll add to the PM discussion though to make sure there aren't any issues with that. The primarily problem I can think of is because the Operator will self-upgrade on publish to the index image and OLM pulling a new index image periodically, is some potential issue we cause on a product deployment. Having use_redhat as the default strategy and some well worded documentation around our support methods, but leaving the existing strategies seems possibly valid as well though. That might give customers a bit more time to plan a migration if necessary, even if we effectively EOL the use_hybrid and use_community strategies from downstream product.
If we plan to EOL STF 1.5 say in 2024-Q3 or Q4 in favour of an STF 2.0, it might not necessarily be worth dropping all the existing functionality, since we'd be doing that anyways shortly after the final STF 1.5 release and it goes into maintenance mode prior to STF 2.0 GA. Nothing is set in stone here though, and we have time to discuss the pros and cons of each of the approaches and then make a decision, and communicate that to the field.

I see Leif and you discussing the three scenarios of hybrid, community or redhat, why do we make that distinction? External is external, no matter what is the source, no?

We are talking about the observability_strategy parameter, which can be set to: none - only deploy smart gateways, no PromOp, no ECK, no grafana use_community - Community PromOP, ECK, and grafana - this is the current way that all STF 1.5.1 installs are done use_redhat - PromOp from RHOBO, no ECK, no grafana - this is the "fully supported install" we are trying to achieve use_hybrid - PromOp from RHOBO, plus Community ECK, and grafana - ECK integration remains deprecated and support for managing the ES object will be removed from a future release.
Forwarding to an external ES should work in all cases. The testing and discussion has been around ensuring that is the case.

+1, nothing to add here.

(simulated) Upgrade testing
Start from super clean. Not sure where packageserver comes in, but nothing remotely STF-deps related here.
$ oc get csv -A
NAMESPACE                              NAME            DISPLAY          VERSION   REPLACES   PHASE
openshift-operator-lifecycle-manager   packageserver   Package Server   0.19.0               Succeeded

$ oc get sub -A
No resources found

$ ansible-playbook build/run-ci.yaml -e __local_build_enabled=true -e __service_telemetry_snmptraps_enabled=true -e __service_telemetry_storage_ephemeral_enabled=true
[...]
        "* [info] CI Build complete. You can now run tests."

ES and Event SGs are healthy.
$ oc get elasticsearch
NAME            HEALTH   NODES   VERSION   PHASE   AGE
elasticsearch   yellow   1       7.16.1    Ready   3h42m

$ oc get po | grep event
default-cloud1-ceil-event-smartgateway-7549f78d75-nkwz6   2/2     Running     2 (20m ago)    41m
default-cloud1-coll-event-smartgateway-85d4f5d484-4xr2x   2/2     Running     10 (19m ago)   41m

Rebuild and restart
$ git checkout csibbitt_STF-1385_external_es

$ ./build/build.sh

$ oc delete po service-telemetry-operator-5fc75d5986-s64d7
pod "service-telemetry-operator-5fc75d5986-s64d7" deleted

$ oc get po | grep service-telemetry-operator
service-telemetry-operator-2-build                        0/1     Completed   0                52m
service-telemetry-operator-3-build                        0/1     Completed   0                6m17s
service-telemetry-operator-5fc75d5986-qgngj               1/1     Running     0                40s

Switch to fully supported mode, observe the new prometheus container
$ oc patch stf default --patch '{"spec":{"observabilityStrategy":"use_redhat"}}' --type merge
servicetelemetry.infra.watch/default patched

$ oc get po | grep prometheus-def
prometheus-default-0                                      3/3     Running     0               38s

$ oc get prometheus.monitoring.rhobs
NAME      VERSION   DESIRED   READY   RECONCILED   AVAILABLE   AGE
default   v2.43.0   1         1       True         True        14m

ES and Event SGs are healthy.
$ oc get elasticsearch
NAME            HEALTH   NODES   VERSION   PHASE   AGE
elasticsearch   yellow   1       7.16.1    Ready   58m

$ oc get po | grep event
default-cloud1-ceil-event-smartgateway-ccd57c969-m868p    2/2     Running     0               5m17s
default-cloud1-coll-event-smartgateway-86f6f76dcd-h6vwr   2/2     Running     0               5m18s

Delete all the ES config

$ oc edit stf default
[...]
  backends:
    events:
      elasticsearch:
        enabled: true
servicetelemetry.infra.watch/default edited

ES and Event SGs are healthy.
$ oc get elasticsearch
NAME            HEALTH   NODES   VERSION   PHASE   AGE
elasticsearch   yellow   1       7.16.1    Ready   7m

$ oc get po | grep event
default-cloud1-ceil-event-smartgateway-ccd57c969-m868p    2/2     Running     0               14m
default-cloud1-coll-event-smartgateway-86f6f76dcd-h6vwr   2/2     Running     0               14m

So I think it works the way we want. Note that I didn't have much luck getting it to pass smoke tests at the initial stage, but I must be doing something wrong since they pass in our actual CI.... but fair warning. :)

test


[Bug] 'Database is locked' error when calling mbtiles files after using disk_to_mbtiles

The following error is thrown if I immediately access an MBTiles file created with disk_to_mbtiles (here when converting the MBTiles file to PMTiles):
2024-08-06 15:36:39,281 - root - ERROR: Exception for sqlite3 operational error,
...
  File "C:\art\disk_to_pmtiles\env\Lib\site-packages\pmtiles\convert.py", line 59, in mbtiles_to_pmtiles
    for row in cursor.execute(
               ^^^^^^^^^^^^^^^
sqlite3.OperationalError: database is locked

The problem appears to be that the database connection is not closed after connection. The fix seems to be to add con.close() at the end of disk_to_mbtiles.


ChatGPT error 500: {"detail":"Hmm...something seems to have gone wrong."}

Verify latest release

[X] I verified that the issue exists in the latest chatgpt release

Verify webapp is working

[X] I verify that the ChatGPT webapp is working properly for this account.

Environment details
Windows 10
Describe the Bug
I keep getting this error, accessToken is fresh, no matter what reverse proxy url I try:
 ⨯ ChatGPTError: ChatGPT error 500: {"detail":"Hmm...something seems to have gone wrong."}
    at fetchSSE (file:///D:/Project/Business/Azen/node_modules/chatgpt/build/index.js:55:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  statusCode: 500,
  statusText: 'Internal Server Error',
  page: '/api/text/chat/[id]',
  [cause]: Response {
    [Symbol(realm)]: null,
    [Symbol(state)]: {
      aborted: false,
      rangeRequested: false,
      timingAllowPassed: true,
      requestIncludesCredentials: true,
      type: 'default',
      status: 500,
      timingInfo: [Object],
      cacheState: '',
      statusText: 'Internal Server Error',
      headersList: [HeadersList],
      urlList: [Array],
      body: [Object]
    },
    [Symbol(headers)]: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    }
  }
}

This is my function:
const queryChatBot = async (prompt, conversationId, parentMessageId) => {
    console.log("ACCESS TOKEN:");
    console.log(process.env.OPENAI_ACCESS_TOKEN);

    // Unofficial
    const api = new ChatGPTUnofficialProxyAPI({
        accessToken: process.env.OPENAI_ACCESS_TOKEN,
        apiReverseProxyUrl: "https://ai.fakeopen.com/api/conversation"
    });

    let res;
    if (conversationId || parentMessageId) {
        res = await api.sendMessage(prompt, {
            conversationId: conversationId,
            parentMessageId: parentMessageId,
        });
    } else {
        res = await api.sendMessage(prompt);
    }

    console.log(`SUCCESS: ${res.text}`);

    return {
        convoId: res.conversationId,
        message: {
            text: res.text,
            id: res.id,
            createdAt: new Date(),
        }
    };
};

{
"error": {
"message": "Internal server error",
"type": "auth_subrequest_error",
"param": null,
"code": "internal_error"
}
}
what's wrong ? can anyone help me ?

{
  "error": {
    "message": "Internal server error",
    "type": "auth_subrequest_error",
    "param": null,
    "code": "internal_error"
  }
}

what's wrong ? can anyone help me ?

UPDATE: I saw that OpenAI had an outage for around 3 hours, so the package is not at fault :)


Prevent unauthorized talk message sending.

Before going through with a %publish command, checks whether source of the poke is in our ++team.
(We don't crash/throw an error because we don't want to bother the user with the useless efforts of whoever is trying to be malicious.)
Solves #208. I believe this is the fix #221 was looking for.
Authorized messages to and from ships and their channels seem to still function fine with this change. I believe I'm catching the right case in the right part of the code here, but as always it'd be cool if someone could verify.

The one place we exploit this behavior is on the web ship. We create session-specific comet names and spoof the author. The web ship acts as a proxy.
More or less the same thing happens for fora posts.
@ohAitch, what do you think? This makes patch makes sense. Maybe we just want to run custom talk code on the web ship.
Sent from my phone

On Feb 25, 2017, at 7:33 AM, Fang<EMAIL_ADDRESS>wrote:
Before going through with a %publish command, checks whether source of the poke is in our ++team.
(We don't crash/throw an error because we don't want to bother the user with the useless efforts of whoever is trying to be malicious.)
Solves #208. I believe this is the fix #221 was looking for.
Authorized messages to and from ships and their channels seem to still function fine with this change. I believe I'm catching the right case in the right part of the code here, but as always it'd be cool if someone could verify.
You can view, comment on, or merge this pull request online at:
https://github.com/urbit/arvo/pull/355
Commit Summary
Prevent unauthorized ships from publishing talk messages using your ship.
File Changes
M app/talk.hoon (5)
Patch Links:
https://github.com/urbit/arvo/pull/355.patch
https://github.com/urbit/arvo/pull/355.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


LM Studio support?

I have my code working with the built-in vLLM model using localhost:8000, but if I try running against the LM Studio server using the meetkai/functionary-small-v2.5-GGUF/functionary-small-v2.5.Q8_0.gguf model, it returns text not function calls.
Is it the prompt format?  If so, which prompt format to use with LM Studio?

Hi, LM Studio's server does not support function-calling. You can refer to #148 for more information on how to work with functionary via handling the raw text prompt and generated response directly.

Thanks for the response.


update NER example readme on module prediction

Description
Fix https://github.com/apache/incubator-mxnet/issues/11859
Added an inference section in README to point to the right example on how to do prediction using BucketingModule
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

Update README

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-label-bot [pr-awaiting-review, Example]

@nswamy addressed comments. Please help merge it if looks good. Thanks!

@mxnet-label-bot update [pr-awaiting-merge]

@piyushghai @nswamy PR looks good to merge to me - could you review the updated diff?


UI - Allowed to enter chat messages  when user has not taken any action on a confirm message from previous chat  resulting thread getting to unresponsive state.

gptscript version - v0.0.0-dev-0c73f4b8-dirty
Steps to reproduce the problem:

Launch UI for remote script -gptscript --ui --workspace ./newthread --disable-cache github.com/gptscript-ai/cli-demo

Start a chat message that requires confirmation for tool repo.

Do not take any action on the confirmation prompt.

Type another chat message and send it (Enter)

This results in no response being received for this message:

Following error seen in console:
 ⨯ unhandledRejection: Error: Run must in creating, continue or error state, not running
    at Run.nextChat (file:///Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/node_modules/@gptscript-ai/gptscript/dist/gptscript.js:234:20)
    at Socket.<anonymous> (file:///Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/server.mjs:138:43)
    at Socket.emit (node:events:519:28)
    at Socket.emitUntyped (/Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/node_modules/socket.io/dist/typed-events.js:69:22)
    at /Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/node_modules/socket.io/dist/socket.js:704:39
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
 ⨯ unhandledRejection: Error: Run must in creating, continue or error state, not running
    at Run.nextChat (file:///Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/node_modules/@gptscript-ai/gptscript/dist/gptscript.js:234:20)
    at Socket.<anonymous> (file:///Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/server.mjs:138:43)
    at Socket.emit (node:events:519:28)
    at Socket.emitUntyped (/Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/node_modules/socket.io/dist/typed-events.js:69:22)
    at /Users/sangeethahariharan/Library/Caches/gptscript/repos/161cfbb4c63e7d55f8cd41dd6f428b222251be44/tool.gpt/node21/node_modules/socket.io/dist/socket.js:704:39
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

Even if we go back and accept the confirmation prompt for the previous message, it gets stuck in "calling tool.." and we are not able to recover from this state. Further messages sent also end up not being processsed.

Expected Behavior:

Should not be allowed to enter anther chat message when waiting for confirmation on the previous chat.

Tested with Version 0.10.0-rc2 (0.10.0-rc2)
This issue is still not fully addressed.

Make any chat conversation that involves a tool call so that you are presented with conform prompt
I am allowed to enter messages when I have not acted on the confirm prompt yet.

Though i see inprogress state in the chat message field, i am able to click on it twice on it and see the call to LLM succeed.

But after this if I go to the confirm prompt from step 1 and allow, tool call gets stuck for ever in calling state

Should we restrict users from being able to send another message when no action is taken for the confirm prompt?

There is another issue that tracks the same issue - https://github.com/gptscript-ai/desktop/issues/183.
Closing this as duplicate.


[BUG] Keymap keep existing even after removing plugin

Describe the bug
Even after removing elin plugin, set keymaps by enabling elin_enable_default_key_mappings continues to exist...
To Reproduce

use neovim and lazy.nvim
install elin with enabling elin_enable_default_key_mappings
remove the plugin
see keymaps by :map

Expected behavior
keymap removed when disabled or deleted
Environemnt (please complete the following information):

Editor: Neovim
Editor version: 0.10.2
Babashka version: 1.12.195

Additional context
I often use neovim plugin rather vim plugin so such keymap remaining can be normal or maybe your expected behavior. If so please close this. :)
Also I have not fully investigated the situation so it might not be reproduced by above, if so I will find minimum config/steps to reproduce. Thank you.

@Peeeaje
The keymap will not be registered unless the plugin remains in neovim's runtimepath.
So I suspect lazy.nvim is caching something.
Please try checking the current runtimepath with :set rtp.
If there is anything related to elin left, could you clear the cache on the lazy.nvim side.
cf. https://github.com/folke/lazy.nvim/issues/29

Feel free to reopen if you have any other problems :)


Port it to SeaMonkey

It ought to be possible to fix this together with issue #12 (Port it to Thunderbird) and/or #13 (Port it to Fennec) but I'm creating the issue so that (if ever this extension gets any support again, of which I'm far from hopeful since "simple" issues one year old are still unattended) SeaMonkey doesn't get forgotten.
I would expect this addon to work in Thunderbird and SeaMonkey after adding either one additional targetApplication tag for each app, or one for<EMAIL_ADDRESS>or both.
See http://forums.mozillazine.org/viewtopic.php?f=19&t=1355415 for details.

Current release supports all three of Firefox, Thunderbird and SeaMonkey. Actually it works better in SeaMonkey than in Firefox AFAICT (both at Gecko/Toolkit 47.0a1).

Oops! Wrong repository.


Update README.md

Just an update on README.md, so that copying/pasting code from Basic Usage example will work

Yeah the readme is currently that of main branch for 3.0, maybe I should set the default branch to 2.x for now..


Add support for Filamentmanager plugin

Hey @gdombiak it‘s me again🙈 Since a few days I‘m using the Filamentmanager Pluging.
https://plugins.octoprint.org/plugins/filamentmanager/
Would ist be possible to implement it to OctoPod? It would be nice only to change the Filament which is presettet on Octopi.
Best regards✌🏼

Thanks @ScharV for this great idea. I like it in particular that this is about selecting the current spool for an extruder/tool. I checked the plugin and it has the required API so this should be feasible. Will add it to the next release since I'm trying to wrap up 3.2 that comes with Apple TV support.

@gdombiak thanks for your fast reply, Sounds very good 😬


Reproducing results from your paper

Hi! Thank you for sharing the code for your model.
I'm having troubles to reproduce the results you have published in your paper.
Here are the scores I get on Coco dataset using the checkpoint provided in your paper:
{'Bleu_1': 0.22440850959728406, 'Bleu_2': 0.11753228266783161, 'Bleu_3': 0.06043320902662557, 'Bleu_4': 0.0321128847993337, 'METEOR': 0.09099773362803487, 'ROUGE_L': 0.16770810280576667, 'CIDEr': 0.11203192991375235}
As you can see, they are significantly lower. I'm using nlg-eval package as you have mentioned here.
What model does your checkpoint corresponds to in the paper, base or long? How do you initialize it for evaluations? Here is my setup:
model = Magma.from_checkpoint(
config_path=os.path.join(model_path, "configs/MAGMA_v1.yml"),
checkpoint_path="mp_rank_00_model_states.pt",
device="cuda:0",
)
As a prompt message I'm using "A picture of " - is that correct?
I'm using temperature=0.7, and also setting manual seed in torch to 42.
Is there anything I'm missing or doing wrong here? If everything looks fine, could you please share your evaluation scripts that would reproduce results?

Hi,
thanks for your interest in our work. Regarding your questions:

The checkpoint provided in this repo is only a demo checkpoint, although configuration wise it is the same as the FF 4 adapter ablation we reported in the paper. I never evaluated this specific checkpoint. MAGMA base and long are trained on an entirely different dataset and are not really comparable.
For the prompt instruction it is very important to NOT have a whitespace at the end, so it should be "A picture of" instead of "A picture of "
Temperature 0.7 is maybe a bit high for eval, I don't exactly recall what we used but I would not go higher than 0.1. Greedy decoding (temp. 0.0) should also work I think.

Please understand that I cannot share further resources, although using nlg-eval should be rather straight forward. With lower temperature and without whitespace at the end of the prompt I would expect results to improve.

Thank you! Changing prompt and temperature helped to improve scores, although still lower than reported in the paper:
{'Bleu_1': 0.39627885456680473, 'Bleu_2': 0.2550440831428488, 'Bleu_3': 0.16363634146091482, 'Bleu_4': 0.10697364143823233, 'METEOR': 0.1581395520589721, 'ROUGE_L': 0.3094927895838829, 'CIDEr': 0.3734865136851766}


Overcommit relies on unmainted/broken childprocess gem

Installing on ruby 2.6.0 no longer works because:
The internal error was:
	(NoMethodError) undefined method `[]' for nil:NilClass
ERROR:  While executing gem ... (NoMethodError)
    undefined method `[]' for nil:NilClass

I traced this to installing the childprocess gem. It has been in maintenance mode for a while, and from about March 2018 unmaintained.
https://github.com/enkessler/childprocess/issues/131
It looks like it's time to depend on a different gem.

Hey @Br3nda, thanks for opening an issue. When I gem install overcommit on Ruby 2.6.0 I don't get any such error. Nor do I get that when I gem install childprocess explicitly.
Can you clarify what you're doing to see that error? Also, can you confirm the output of:
ruby --version

gem --version

bundler --version

For context, on my system I get:
⨠ ruby --version
ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-darwin18]
⨠ gem --version
3.0.1
⨠ bundler --version
Bundler version 1.17.3


Fixing issue with wrong offsetTop in state after scroll

Can be merged after this PR: https://github.com/namespace-ee/react-calendar-timeline/pull/199
Now if timeline is nested inside another div with overflow: scroll - it doesn't handle canvasDoubleClick and other click events correctly - because of the wrong offsetTop in state. We should listen to parent scroll and update offsetTop.

I'm going to close this PR but reopen it if others run into this issue.  I don't think many users are placing the timeline inside a scrollable div and I would encourage them not to do so.
Moreover, the way this timeline currently handles reporting item clicks i believe will change and will not be related to yPosition to determine group


Update Custom Set test order

To address the change merged https://github.com/exercism/x-common/pull/257

Dupe of #139


Team advanced search

As part of https://github.com/gratipay/gratipay.com/issues/3127, it might be useful to open up queryable information a little more.

tags
number of team members
giving
receiving

Target audience might be people looking to join an open project rather than those looking to donate, but could serve both.

+1 from https://github.com/gratipay/gratipay.com/issues/4460#issuecomment-301607440 for dealing with traffic:

Rather than listing all the teams on the homepage, maybe we should beef up the search capabilities with additional filters?


Person Detection issue in Android App Using tenserflow Lite

Hi i am Using Android Detection Example App , here  i want to monitor a person in or out activity.
but my problem is it take more time to detect when a person walk ,some time cnt detect person.
another problem is that after detecting cant track properly ..
is this is the issue of camera video quality..?
how can i change the quality and  brightness of  camera in this app..?

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

yes i have written custom code on Multiboxtracker.java class.
N/A
N/A
N/A
Sir i am using tenserflow Lite on android mobile phone , i am using tenserflow Lite demo app downloaded from  github (tensorflow/tensorflow/examples/android/). my issue is in this app.

This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.
If you think we've misinterpreted a bug, please comment again with a clear explanation, as well as all of the information requested in the issue template. Thanks!

thanks sir ,


avoid using bool in Dataset attributes

Like it is the case for '_xsimlab_master_clock' and '_xsimlab_snapshot_clock'. Instead use, e.g., uint8.

Fixed in 0f34bef.


Add code examples for CodeStar, AppStream, and CodePipeline

Context
My team maintains a SDK code example repo which contains examples in 11 languages. We do not support CloudFormation, the AWS CLI, or the CDK.
Meanwhile, this repository is the most "official" AWS code example repository for CloudFormation and is maintained by the CloudFormation team, making it the de facto location for consolidating any out-of-place CloudFormation examples.
Problem/Solution
We have a total of three (3) out-of-place CloudFormation code examples that will be deleted because they are out-of-scope for my team; however, we'd like to move these instead of discarding them.

Thank you @ford-at-aws - this repository contains samples for CloudFormation extensions such as resource types, hooks, and modules in relevant sub-directories.  The content of this PR does not contain samples for CloudFormation extensions, and is then out-of-scope.


tweak print_saved_residuals

Small tweak to this utility (the printing details of which are untested, though its internals are tested and unchanged by this PR).
Given this code:
def g(W, x):
  y = jnp.dot(W, x)
  return jnp.sin(y)

def f(W1, W2, W3, x):
  x = g(W1, x)
  x = g(W2, x)
  x = g(W3, x)
  return x

W1 = jnp.ones((5, 4))
W2 = jnp.ones((6, 5))
W3 = jnp.ones((7, 6))
x = jnp.ones(4)

jax.ad_checkpoint.print_saved_residuals(f, W1, W2, W3, x)

Before this PR, we'd print:
f32[5,4] from the argument 'W1'
f32[6,5] from the argument 'W2'
f32[7,6] from the argument 'W3'
f32[4] from the argument 'x'
f32[5] from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[5] from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[6] from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[6] from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[7] from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)

After this PR, we'll print:
f32[5,4] from the argument 'W1'
f32[6,5] from the argument 'W2'
f32[7,6] from the argument 'W3'
f32[4] from the argument 'x'
f32[5] output of sin from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[5] output of cos from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[6] output of sin from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[6] output of cos from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)
f32[7] output of cos from /usr/local/google/home/mattjj/packages/jax/ckpt.py:46 (g)

Also, if we put a jax.jit on g, we'll get:
f32[5,4] from the argument 'W1'
f32[6,5] from the argument 'W2'
f32[7,6] from the argument 'W3'
f32[4] from the argument 'x'
f32[5] output of jitted function 'g' from /usr/local/google/home/mattjj/packages/jax/ckpt.py:50 (f)
f32[5] output of jitted function 'g' from /usr/local/google/home/mattjj/packages/jax/ckpt.py:50 (f)
f32[6] output of jitted function 'g' from /usr/local/google/home/mattjj/packages/jax/ckpt.py:51 (f)
f32[6] output of jitted function 'g' from /usr/local/google/home/mattjj/packages/jax/ckpt.py:51 (f)
f32[7] output of jitted function 'g' from /usr/local/google/home/mattjj/packages/jax/ckpt.py:52 (f)

We could instead recurse into jitted functions, but I decided not to because:

that would be a bigger change, and
if we imagine the jitted functions are e.g. jnp functions, then it's probably more informative to print the jitted function name rather than printing the name of some primitive in its implementation (which may be less clear to the user).

We could instead recurse into jitted functions, but I decided not to because: [...]

Agreed on both.


Idea for future: Any way to automate adding default argument values in roxygen headers?

We'd like a way to take this info directly from the Usage box rather than manually repeating the info:

Any clever ideas from the admiral community for this?? For now we're going to remove the repeated default values under the arguments section as it's difficult to maintain and subject to manual error.

Closing to centralize as denoted in https://github.com/pharmaverse/admiraldev/issues/290


{BOT} Test github app

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

Describe the bug

To Reproduce

Expected behavior

Environment summary

Additional context

Hi @wangzelin007, Since the current milestone time is less than 21 days, this issue will be resolved in the next milestone

@wangzelin007 please take a look.

@wangzelin007 please take a look.


Cannot read property 'isFlipped' of undefined

I've been trying to implement Flip into my Shopify Slate site and I'm getting this message in my console:

Cannot read property 'isFlipped' of undefined

My code is closely like:

            First Card Content
           Forgot Password

            Second Card Content
           Cancel

$(".form-cards").flip({
  trigger: 'manual'
});
$("#card-flip").flip('toggle');

i had same issue

if you use the specific version of jQuery mentioned, you'd not get the issue. Think it is tied to a specific version of jQuery


[Disco] Implement num_workers property for disco.Session

Prior to this commit, while the num_workers argument was provided to the disco.Session object, it could not be determined from an existing disco.Session object.  As a result, functions that interacted with a multi-GPU setup frequently required separate num_workers and disco_session argument, which could erroneously be out-of-sync (e.g. passing the incorrect num_workers, or omitting the disco_session argument when num_workers>1).
To remove this class of errors, this commit adds a disco.Session.num_workers property.  The separate num_workers argument is no longer necessary, as it can be determined from the disco.Session instance.

Closing this PR, as it is identical to https://github.com/apache/tvm/pull/16978.  I think that means I have too many open PRs, and any help in reviewing them would be appreciated.


package.josn has syntax problems in the 'window' system

Run 'yarn dev' and 'yarn build' on the mac system, and the packaged files are OK, but on the window mac system, it was not run 'mvsw-dev.ts' and 'mvsw-prod.ts'.

I also encountered the same problem.


Parsed date not correct

I found a weird bug when parsing dates. 2034-02-28 and earlier dates are being parsed correctly. But all dates after that specific day are always one day behind.
phantomjs> new Date('2034-02-28')
"2034-02-28T00:00:00.000Z"
phantomjs> new Date('2034-03-01')
"2034-02-28T00:00:00.000Z"
phantomjs> new Date('2034-03-02')
"2034-03-01T00:00:00.000Z"

I'm using version 2.0.0.

How very peculiar.
This is a bug in Webkit, please report it directly to them: https://www.webkit.org/quality/reporting.html