Force OSD to continue loading lower levels

After reading through all the API docs about the "options", the viewer, and the viewport I can't seem to understand the following issue:
OSD seems to stop loading lower levels and stops at the resolution indicated in this screen capture:

HOWEVER, it is supposed to resolve to this level:

What "settings", or options are controlling this behavior?

Hmm, it should just work. Are you getting any errors in the console? Do you have a link to the page you can share?

Here is a screencapture showing the error(S) shown in the console:
(the link is: [http://coursecontent.nic.edu/bdrichards/gigapixelimages/dryfalls])

It looks like that there is some network issues. I reproduced it randomly.
You can try to increase the timeout but it is already set at 30000ms by default which is already quite long.
@iangilman it looks like the only way to change the timeout is to set:
OpenSeadragon.DEFAULT_SETTINGS.timeout = 60000;

See https://github.com/openseadragon/openseadragon/blob/master/src/imageloader.js#L41

@avandecreme Interesting... we should probably expose that in the construction options at some point.
@bdrichards Is there anything you can do to speed up that server? I suppose one possibility is that it doesn't like being hit with so many simultaneous requests. You can try something like imageLoaderLimit: 4 in the options when you create your viewer. Great image, BTW!

@iangilman  Thanks for the insights and having a look at my "virtual field-trip". The imageLoaderLimit setting is the next thing to test. I currently set the options as shown below which includes setting the timeout option to 1000000 (does not seem to help). I will speak with the network engineer, the server is a virtual machine on our campus system with tons of resources and "... 1Gbps internet that supplies plenty of outgoing bandwidth." according to the engineer; however, the server is likely not setup anyway as an "image" server. The issue NEVER occurs when I am testing on campus (connected to the same network, duh).
Here are my viewer options
    var viewer = OpenSeadragon({
        id: "openseadragon1",
                showNavigator: true,
       prefixUrl : "/bdrichards/gigapixelimages/openseadragon/images/",
        controlsFadeLength: 650,
        //maxZoomLevel: 50,
       maxZoomPixelRatio: Infinity,
       minPixelRatio: 0.15,
       preserveImageSizeOnResize: true,
       maxImageCacheCount: 500,
       timeout: 1000000, // default is 30000
       placeholderFillStyle: "#AAAAAA",
        tileSources: {
	        Image: {
	            xmlns:    "http://schemas.microsoft.com/deepzoom/2008",
	            Url:      "dryfalls02_156604x13548-copy01_files/",
	            Format:   "png",
	            Overlap:  "1",
	            TileSize: "254",
	            Size: {
	                Height: "13548",
	                Width:  "156604"
	            }
	        }
	    }
    });

Cool, let me know how imageLoaderLimit treats you. You might also try doing something different for minPixelRatio; the setting of 0.15 will make it especially aggressive about loading new tiles.
@avandecreme Looks like timeout can be used in the options after all. The code you pointed to is just setting up defaults, but the options override it. Is there something else you spotted?

The options are set here: https://github.com/openseadragon/openseadragon/blob/master/src/imageloader.js#L128-L134
I don't see timeout set.

@avandecreme  I have set the timeout: option during viewer creation (maybe this doesn't actually change the value?)
@iangilman Changing the the imageLoaderLimit option to something between 4 and 7 helps tremendously and our network engineer will look at a few settings/policies on the server for me. My colleagues may be using a VPN connection from their homes to access their campus accounts, from which they are accessing my images, which will totally kill their bandwidth.
Here is another image (of an iconic North America landmark) that was giving fits, but is now improved - how many climbers can you find? DevilsTower

@avandecreme I have set the timeout: option during viewer creation (maybe this doesn't actually change the value?)

Yeah I don't think that actually work. However setting the imageLoaderLimit seems like a better option.
I wonder if increasing the tile size (by regenerating the image with a tile size of 510 for example) could help as well?
Very nice images :+1:

@avandecreme I stand corrected! So, to fix the timeout option it would need to get passed from the Viewer into the ImageLoader and from there into the individual jobs. Seems worth fixing (or, I guess removing the timeout option from the docs). I agree using it is not the fix for this issue though... glad to hear imageLoaderLimit is working well.
I agree that regenerating the image with tile size of 510 is also a good idea. I guess it might be worth updating our "creating images" page with that recommendation across the board.
@bdrichards Another great photo! When you're ready, we can add these to our "in the wild" page.

Is there currently any way to set the image loading timeout, the one that results in "error: Image load exceeded timeout" in the console?  If I'm reading this issue right, there is currently no way to do it at all? But it defaults to 30 seconds?

default seems to be way less than 30 seconds.

Hmm... looking at the code now, it seems that the timeout option should be getting honored. It's passed from the Viewer into the ImageLoader here:
https://github.com/openseadragon/openseadragon/blob/master/src/viewer.js#L380
...and from the ImageLoader into the ImageJob here:
https://github.com/openseadragon/openseadragon/blob/master/src/imageloader.js#L217
...and used by the ImageJob here:
https://github.com/openseadragon/openseadragon/blob/master/src/imageloader.js#L89
@jrochkind Can you give it a try to see if it works? Also, if the default is less than 30 seconds for you, can you quantify it somehow?

actually trying to reproduce, i am getting timeouts at about 30s that might have been a false alarm. will continue to investigate and update if i find anything odd.

Good to hear the 30 seconds thing was a false alarm. Let me know if you get the timeout option to work. :)

@iangilman I am not certain timeout from viewer is really being passed on. I passed a timeout: 10, expecting timeout errors, but didn't get any.  Confirmed in chrome dev tools that tiles fetched were not being fetched from cache, and did take more than 10ms to fetch.
Setting OpenSeadragon.DEFAULT_SETTINGS.timeout = 10; did trigger the timeouts I expected. So that global setting does work to override timeout. But passing timeout as option to Openseadragon() viewer creation does not seem to.  Would you like me to file a separate issue?

Yeah, probably creating a new issue for that would be good. Also if you'd like to trace down the issue and create a pull request for it, that would be lovely as well :)

@jrochkind Thank you for filing the new issue. Closing this now in favor of #1279.


pkg/search/controllers_test: fix flaky test cases [2/2]

Description
In this commit, we mock the clusterDynamicClientBuilder in TestUpdateResourceRegistryEventHandler and update the group/values of resources to include apps/v1 for deployments and v1 for pods. This change is the continuation of the second part of karmada-io/karmada#5856.
What type of PR is this?
/kind flake

Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Thanks~


Add the start command

Summary
I aim to understand the internal structure of low-level container runtime and its implementation. To do so, first I am going to read youki's first-commit. I will proceed with this task with a policy of committing features little by little.
In this Issue, my objective is to implement the start command.
Goal
When the start command is implemented, this issue will be closed.
More specifically, it is when the rust-runtime start $(container_id) command is successfully executed.
References

okuda-seminar/rust_runtime/src/start.rs

Notes
None

Work time
1.5h
Report
I've already completed the implementation of the create command, which allowed me to dedicate this week to gaining a deeper understanding of the start command. While studying the start command, I learned how to use the notify socket and explored the do_exec method in create.rs.
Looking ahead to the upcoming week, my plan is to begin implementing the start command.
References

https://doc.rust-lang.org/stable/std/path/struct.Path.html
https://www.digitalocean.com/community/tutorials/execvp-function-c-plus-plus

Work time
1.5h
Report
I had understood the general workflow of the 'start' command last week, so I dedicated this week to its implementation. I've successfully completed it and verified that the 'start' command is functioning correctly.
/workspace/crate/tutorial# rust-runtime start 1
[13:32:23][DEBUG][rust_runtime::start] /run/youki/1
[13:32:23][DEBUG][rust_runtime::notify_socket] connection start
[13:32:23][DEBUG][rust_runtime::notify_socket] write finish
[13:32:23][DEBUG][rust_runtime::container::container] Save container status: Container { state: State { oci_version: "v1.0.2", id: "1", status: Running, pid: Some(1643), bundle: ".", annotations: {} }, root: "/run/youki/1" } in "/run/youki/1"
root@a8aab5597303:/workspace/crate/tutorial# [13:32:23][DEBUG][rust_runtime::notify_socket] receive :start container
[13:32:23][DEBUG][rust_runtime::utils] filename: "sleep", args: ["sleep", "5"]
[13:32:28][DEBUG][rust_runtime::process::fork] exited pid: Pid(1643), status: 0

Furthermore, I plan to decide on my next action tomorrow.

Work time
2.5h
Report
I tried to test the source code using runtime-tool, but I had an error.
/usr/local/sbin/rust-runtime: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /usr/local/sbin/rust-runtime)

Hence, I've devoted this week to investigating the root cause of this error and identifying potential countermeasures. Despite my efforts, I haven't been able to resolve the issue.
Consequently, I plan to seek assistance during the next seminar. If resolving this error proves challenging, I am considering testing the code on GitHub instead of locally.


Extension causes high cpu load

Issue Type: Performance
Extension Name: bracket-pair-colorizer-2
Extension Version: 0.0.26
OS Version: Darwin x64 18.2.0
VSCode version: 1.31.1

:warning: Make sure to attach this file from your home-directory: /Users/marcelo/CoenraadS.bracket-pair-colorizer-2-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Duplicate of #55. Please close this and post there instead.
@MarceloPincheira

Duplicate of #55. Please close this and post there instead.
@MarceloPincheira

Sorry I don't know how happened this. Closed.


add new /heartbeat endpoint

We aren't able to ping iRODS servers on the frontend for ZMT, so we would like to do it via the CPP API:
accepts (through query parameters?) hostname, port
returns: HEARTBEAT if that hostname / port sent back HEARTBEAT, else send back "FAILURE". Or this could be True and False.
implementation

(simpler, but dirtier) send an HTTP GET request to the hostname / port. if we're able to differentiate INVALID HTTP or NOT FOUND, we can tell that the hostname / port is up. though, this solution will also detect other servers that don't send back HTTP responses as real iRODS servers.
(more work, but cleaner, recommended) use TCP sockets to send a HEARTBEAT message to the hostname/port, and see if we get back HEARTBEAT.

Yes, definitely option 2.   don't want to pollute the target iRODS server's logs.
hostname and port as query parameters seem correct
returning HEARTBEAT is probably fine for now... but willing to consider more 'standard' things.  what do other APIs send/share when pinging each other's endpoints?

From what I've read, APIs can send a message like "healthy", "warning", "error" or any other string, along with the corresponding HTTP status code when doing a health check.
Before returning "healthy", the API would ping other aspects of its structure (like the database) and make sure that everything is working.

right - okay - let's just send HEARTBEAT as a response with code 200 and see how it feels/goes.

This will not be implemented in this repository.
Please see the new HTTP API:
https://github.com/irods/irods_client_http_api


Adding Philips Hue Daylo

Could you please add Philips Hue Daylo outdoor wall light:
Product ID: 1746530P7
Service ID: 269
Profile ID: 260

Hi @andtor84 and thanks for your request, it has been added to the To Do list :)

Now in test version
https://homey.app/sv-se/app/com.philips.hue.zigbee/Philips-Hue-ZigBee/test/

Seems to work perfect, @JohanBendz! Thx. 😊


[C-400] Hide bot activity

It is already done in reports. We need to hide it from the homepage and activity section. Same as team members.
From SyncLinear.com | C-400

duplicate


Fixes for sitl gazebo ground truth.

This fixes some errors in ground truth recording and also updates sitl gazebo to fix ground truth frame issues there. This is towards closing #5931.

@bkueng @LorenzMeier please review.

Jenkins test this please.

Jenkins test this please

Please rebase, thanks!


Hairline freezes when Developper Tools is opened ?

Describe the bug
When Developper Tools is opened, after zooming out on a random chart, hairline gets really laggy: it freezes and does not synchronise with the mouse cursor. As soon as Developper Tools is closed, hairline reactivity gets back to normal speed.
Feels like the hairline is causing a lot of side effects causing the tab to lag when dev tools is opened ?
Reproduction
https://codesandbox.io/s/playing-around-3-voc5c6?from-embed
Steps to reproduce
Open any of the 10 Getting Started sandbox's preview into a new Browser tab. Then open Dev Tools (F12). Then zoom the chart OUT. Then try to move the mouse over the chart. The hairline will lag.
Note: I am on Macbook Pro M1 16Gb RAM, with only 1 Chrome tab opened (the one for the test, nothing else).
Javascript Framework
no-framework (vanilla-js)
Logs
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a NightVision issue and not a framework-specific issue.
[X] The provided reproduction is a minimal reproducible example of the bug.

Yes, I experience this too. Although I have the same notebook, and it is almost unnoticeable here. Can you test trading-vue-js? https://tvjsx.github.io/trading-vue-demo/
Probably, the problem is with some dev-tool analytics, it is really hard to tell.

It has the same issue yes...

https://stackoverflow.com/questions/60573388/react-app-slows-to-a-crawl-with-chrome-developer-tools-open-works-fine-in-incog
With profiling enabled it works smoothly indeed

I confirm after profiling it works smoothly. I let you close this issue if you feel like it is out of the scope and we should just enable profiling during dev or if you prefer considering it as a solvable issue :) Thank you for your lights !


Menu has an offset

Menu has an offset. Godot 4.2.

Hmm this happens because the menu is made for 1152*648 viewports. If you wish to use different ratios you'd need to set those here:

For reference here's my project settings (also works in fullscreen)

Ui should be adaptable and independent to any ratio. In other case it's buggy, I'm afraid.

Was testing this today, resizing seems to work correctly as of latest, I'll close this issue for now.


Nominee name data migration task for FormAnswers

Also removed legacy rake task that said "Remove after use"

:+1:


Actually include no-native in the rules

I tried to use this against a project, but since I want to use the no-native rule I just got an error against every file:
  1:1  error  Definition for rule 'promise/no-native' was not found  promise/no-native

Can this be merged and a new version pushed up to npm please?

Eek! Thanks!
On Thu, May 26, 2016 at 5:56 PM Lucas Parry<EMAIL_ADDRESS>wrote:

I tried to use this against a project, but since I want to use the
no-native rule I just got an error against every file:
1:1  error  Definition for rule 'promise/no-native' was not found  promise/no-native
Can this be merged and a new version pushed up to npm please?
You can view, comment on, or merge this pull request online at:
https://github.com/xjamundx/eslint-plugin-promise/pull/15
Commit Summary

Actually include no-native in the rules

File Changes

M index.js
https://github.com/xjamundx/eslint-plugin-promise/pull/15/files#diff-0
(3)

Patch Links:

https://github.com/xjamundx/eslint-plugin-promise/pull/15.patch
https://github.com/xjamundx/eslint-plugin-promise/pull/15.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xjamundx/eslint-plugin-promise/pull/15, or mute the
thread
https://github.com/notifications/unsubscribe/AAPBf2pUzrWfx177DCGAEdTjZfAYH2M3ks5qFkEzgaJpZM4IoFWR
.

+<EMAIL_ADDRESS>


Filter by date

Hi there, is it possible to add a filter by date like "month", "week" or "24 hours" ? Currently it's searching by all time. Please let me know if there's already a way to do this!

in FetchJobLinksUser.ts make this correction
const searchParams: { [key: string]: string } = {     keywords,     location,     f_TPR: "r604800", //r604800 = 1 week, r86400 = 24 hours, r2592000 = 1 month     start: numSeenJobs.toString(),     f_WT: fWt,     f_AL: 'true'   };


fix(streaming): do not write batch for a single insert in ManagedTopNState

What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
ManagedTopNState currently only guarantees that a single write batch does not include two same keys, however, it is required that all the write batches of a single epoch must not include two writes with the same keys.
This PR buffers the rows inserted(one particular branch) into the flush buffer instead of writing them down into the storage directly.
Refer to a related PR or issue link (optional)
closes #1841

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Hold for a second... Let me test it more.


periodic payment cron job for proposer and challenger

This PR implement a feature to cli SDK for proposer and challenger to start a cron job which withdraw their pending withdraw from state contract.
as part of the implementation it fixes few existing bugs:-

fix state contract addPendingWithdrawal function - not to override existing added pendingWithdraw for an address
update nightfall_deployer migration files to do state.setFeeL2TokenAddress function
fix optimist router.get('/pending-payments') api to work with address not passed in lower case. As in our optimist DB we save EOA address in lowercase unlike  in ethereum where address in case sensitive
fix optimist router.get('/withdraw') api:- to  router.post('/withdraw') also correct logic to call withdraw function from state contract, before api had logic to call non-existing withdraw from proposer contract
fix optimist router.post('/payment')

Does this close any currently open issues?
https://github.com/EYBlockchain/nightfall_3/issues/1237

Can you clear the conflict please?


chatglm2 GPU版本的int4、int8量化模型预测结果异常

maybe there is a bug in an early commit， now it is ok in the main branch.


Refactoring for implementing the template method

Hi,
I found your project, looking for something to automate some tasks and on discord.js.
When, I went to understand what the project is about. I saw a perfect opportunity to apply the Template Method design pattern. Because your objective fits perfectly with the idea of the project and I felt that your architecture is not yet very mature.
My only goal was to apply the design pattern, I tried to keep the application as originally built.

Hello,
Thanks for your amazing pull request! And for showing me about the Template Method, certainly helped a lot in the code. 😉


Follow up on JHU data

Actual Behavior:
Calling (via R package)
covidcast_signal("jhu-csse","deaths_incidence_num", geo_type = "state")

Produces many warnings, all of the form:
Fetching deaths_incidence_num from jhu-csse for 20200322 in geography '*': no results

From 1/22--2/19, there are 51 states in the API with data. From 7/28-10/16, there are 52 states. In between, nearly all data is missing. The only available data in between are 19 unique dates with values for MO. All of these MO values have issue data 10/15.

Confirmed; this is due to me not updating the is_latest_issue column when I dropped the bad issues on Saturday. @korlaxxalrok and/or @melange396 can you take a look and either repair the db directly or propose a fix?

Curious results.
These are the queries I ran on Saturday:
MariaDB [epidata]> delete from covidcast where source="jhu-csse" and `signal`="confirmed_incidence_prop" and geo_type="state" and issue>=20201007;
Query OK, 35219 rows affected (5 min 30.71 sec)

MariaDB [epidata]> delete from covidcast where source="jhu-csse" and `signal` in ("confirmed_cumulative_prop", "confirmed_7dav_cumulative_prop", "confirmed_incidence_prop", "confirmed_7dav_incidence_prop", "deaths_cumulative_prop", "deaths_7dav_cumulative_prop", "deaths_incidence_prop", "deaths_7dav_incidence_prop") and geo_type="state" and issue>=20201007;
Query OK, 245674 rows affected (15 min 53.07 sec)

Neither query should have impacted any of the num signals.
Nevertheless,
MariaDB [epidata]> select time_value,sum(is_latest_issue) from covidcast where source="jhu-csse" and `signal`="deaths_incidence_num" and time_value>20200219 and time_value<20200230 and geo_type="state" group by time_value;
+------------+----------------------+
| time_value | sum(is_latest_issue) |
+------------+----------------------+
|   20200220 |                    0 |
|   20200221 |                    0 |
|   20200222 |                    0 |
|   20200223 |                    0 |
|   20200224 |                    0 |
|   20200225 |                    0 |
|   20200226 |                    0 |
|   20200227 |                    0 |
|   20200228 |                    0 |
|   20200229 |                    0 |
+------------+----------------------+

We would have expected sum(is_latest_issue) to be 1 for each time_value, so something has to have horked up that column assignment.

we have fill_is_latest_issue.py which can fix that column...  i can add some stuff to it to narrow it down to just the JHU data and split up by time_value and/or signal in the interest of being kind to the DBMS.
do we want to run this for just source="jhu-csse" and geo_type="state" and 20200220 <= time_value <= 20200727?  seeing as how @krivard 's SQL statements shouldn't have caused this problem, perhaps we should not assume its limited to this subset of the data?
i would also like to propose storing the ids that need to be set to is_latest_issue, then committing those writes in a transaction outside of the large JOIN operations.  i could be mistaken, but i think this should spend less time with a lock on the table BUT we will need to make sure no other writes happen during this time because consistency.  comments greatly appreciated.

I think we want to run it for all of source="jhu-csse". My hypothesis is that the problem in the num signals was introduced during the cache repopulation job I ran on Friday, which was done for all signals and geo levels outside of Automation's purview. There was a collision when Automation started up an ingestion run while JHU was still working through the archive diff, which modifies the receiving directory in place at the same time that Automation is trying to read files out of the same directory. I thought I had caught it in time with a suspend signal, but it looks like the Automation job failed. If that happened before the is_latest_issue column update could be run, that would explain the problems in num, and it would mean that the prop problems would extend beyond state.
I like the idea of doing the update in a separate transaction from the JOINs. JHU is currently on hold*, so there shouldn't be any conflicting writes even if the CSV import job runs while we're doing the fill. If we want to be 100% sure, we can pause Automation while the fill is running. @korlaxxalrok thoughts?
*(it ran this morning because I'd only pushed it forward to Tuesday, but I'm about to clear away what it left in receiving. I've pushed the next run to Saturday morning; before EOD Friday we should either push it forward again or re-sync the cache)

Is it worth trying to simulate this on staging? Maybe load the jhu data and run through it?

That would be wise. Do you think we can get through that with enough time to complete the fix on prod by Friday morning?

Might be possible to do this with Mariabackup. We'd basically be doing a physical restore from production. That may be also be generally useful so that whatever we end up doing more of in staging has relatively refreshed data to work with.

I can look to see how possible it would be to get it in there. Some of the time needed will be taking the backup and then moving it around and all that. Not sure how big it will be. I'll check.

I'm copying over a backup now. Will see if I can have it in place by eod/early tomorrow (in case it takes forever).

i ran (on staging) a slightly hand-edited version of the generated fix i have in a PR https://github.com/cmu-delphi/delphi-epidata/pull/260...  it went stupidly fast -- so much so that it left me a little shocked.  is my filtering being overly selective or something?? (it is source='jhu-csse' AND time_type='day' AND geo_type='state')
repeating Katie's query from above on a "fixed" staging database:
select time_value,sum(is_latest_issue) from covidcast where source="jhu-csse" and `signal`="deaths_incidence_num" and time_value>20200219 and time_value<20200230 and geo_type="state" group by time_value;
+------------+----------------------+
| time_value | sum(is_latest_issue) |
+------------+----------------------+
|   20200220 |                   52 |
|   20200221 |                   52 |
|   20200222 |                   52 |
|   20200223 |                   52 |
|   20200224 |                   52 |
|   20200225 |                   52 |
|   20200226 |                   52 |
|   20200227 |                   52 |
|   20200228 |                   52 |
|   20200229 |                   52 |
+------------+----------------------+
10 rows in set (12.902 sec)

which seems reasonable as there are 50 states + PR and DC
to execute this on prod, run mysql --verbose -p epidata < jhu_islatest_fix.sql
the table jhu_islatest_fix will also need to be removed after the process is finished, but it would be nice to keep it around a bit for sanity checking.

Update from last night's Slack stream:

running with all geo_types has a much more reasonable runtime of at least 3 hours and probably 6-7 (which makes sense; 3k counties ~= 60x 50 states)

I'm going to poke at the staging results and check that it did the right thing, then we'll set off the fix in prod.


DEP: add deprecation warning for kwargs nyq / Hz in firwin*

Reference issue

closes gh-16253
What does this implement/fix?

Adds deprecation warning to kwargs nyq and Hz that were previously deprecated in docstring only
Additional information

@tupui thanks for that, I keep messing that formatting up! I realise now that the formatting in #16265 and #16258 is incorrect should I make a flow up pr?

No worries 😃 It's not a priority but feel free. If you do, you could address all occurrences in the doc (not that many).

@j-bowhay can you merge with upstream/main to see if that fixes CIs? It would be nice to be able to verify things are correct in the doc build

According to CircleCI some examples need to be updated
/home/circleci/repo/build-install/lib/python3.8/site-packages/scipy/signal/_fir_filter_design.py:docstring of scipy.signal._fir_filter_design.kaiserord:67: WARNING: Exception occurred in plotting scipy-signal-kaiserord-1
 from /home/circleci/repo/doc/source/reference/generated/scipy.signal.kaiserord.rst:
Traceback (most recent call last):
  File "/home/circleci/.pyenv/versions/3.8.13/lib/python3.8/site-packages/matplotlib/sphinxext/plot_directive.py", line 517, in _run_code
    exec(code, ns)
  File "<string>", line 36, in <module>
  File "/home/circleci/repo/build-install/lib/python3.8/site-packages/scipy/signal/_fir_filter_design.py", line 393, in firwin
    nyq = 0.5 * _get_fs(fs, nyq)
  File "/home/circleci/repo/build-install/lib/python3.8/site-packages/scipy/signal/_fir_filter_design.py", line 31, in _get_fs
    warnings.warn(msg, DeprecationWarning, stacklevel=3)
DeprecationWarning: Keyword argument 'nyq' is deprecated in favour of 'fs' and will be removed in SciPy 1.12.0.
/home/circleci/repo/build-install/lib/python3.8/site-packages/scipy/signal/_fir_filter_design.py:docstring of scipy.signal._fir_filter_design.minimum_phase:102: WARNING: Exception occurred in plotting scipy-signal-minimum_phase-1
 from /home/circleci/repo/doc/source/reference/generated/scipy.signal.minimum_phase.rst:
Traceback (most recent call last):
  File "/home/circleci/.pyenv/versions/3.8.13/lib/python3.8/site-packages/matplotlib/sphinxext/plot_directive.py", line 517, in _run_code
    exec(code, ns)
  File "<string>", line 7, in <module>
  File "/home/circleci/repo/build-install/lib/python3.8/site-packages/scipy/signal/_fir_filter_design.py", line 854, in remez
    warnings.warn(msg, DeprecationWarning, stacklevel=2)
DeprecationWarning: 'remez' keyword argument 'Hz' is deprecated in favour of 'fs' and will be removed in SciPy 1.12.0.
/home/circleci/repo/build-install/lib/python3.8/site-packages/scipy/signal/_fir_filter_design.py:docstring of scipy.signal._fir_filter_design.remez:97: WARNING: Exception occurred in plotting scipy-signal-remez-1
 from /home/circleci/repo/doc/source/reference/generated/scipy.signal.remez.rst:
Traceback (most recent call last):
  File "/home/circleci/.pyenv/versions/3.8.13/lib/python3.8/site-packages/matplotlib/sphinxext/plot_directive.py", line 517, in _run_code
    exec(code, ns)
  File "<string>", line 29, in <module>
  File "/home/circleci/repo/build-install/lib/python3.8/site-packages/scipy/signal/_fir_filter_design.py", line 854, in remez
    warnings.warn(msg, DeprecationWarning, stacklevel=2)
DeprecationWarning: 'remez' keyword argument 'Hz' is deprecated in favour of 'fs' and will be removed in SciPy 1.12.0.

(or the deprecation warning is not being emitted correctly / under the correct conditions -- not sure which is the case)

@larsoner docs now rendering correctly, CI failings seem unrelated?


"npx whisper-node download" downloading a broken file

Running "npx whisper-node download" is downloading a broken ggml-base.en.bin file with
Invalid username or password.

This is the logs when I ran npx whisper-node download:
> npx whisper-node download

| Model     | Disk   | RAM     |
|-----------|--------|---------|
| tiny      |  75 MB | ~390 MB |
| tiny.en   |  75 MB | ~390 MB |
| base      | 142 MB | ~500 MB |
| base.en   | 142 MB | ~500 MB |
| small     | 466 MB | ~1.0 GB |
| small.en  | 466 MB | ~1.0 GB |
| medium    | 1.5 GB | ~2.6 GB |
| medium.en | 1.5 GB | ~2.6 GB |
| large-v1  | 2.9 GB | ~4.7 GB |
| large     | 2.9 GB | ~4.7 GB |

[whisper-node] Enter model name (e.g. 'base.en') or 'cancel' to exit
(ENTER for base.en):
[whisper-node] Going with base.en
Downloading ggml model base.en from 'https://huggingface.co/datasets/ggerganov/whisper.cpp' ...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    29  100    29    0     0    207      0 --:--:-- --:--:-- --:--:--   216
Done! Model 'base.en' saved in 'models/ggml-base.en.bin'
You can now use it like this:

  $ ./main -m models/ggml-base.en.bin -f samples/jfk.wav

[whisper-node] Attempting to compile model...
sysctl: unknown oid 'hw.optional.arm64'
I whisper.cpp build info:
I UNAME_S:  Darwin
I UNAME_P:  i386
I UNAME_M:  x86_64
I CFLAGS:   -I.              -O3 -std=c11   -fPIC -pthread -mf16c -mfma -mavx -mavx2 -DGGML_USE_ACCELERATE
I CXXFLAGS: -I. -I./examples -O3 -std=c++11 -fPIC -pthread
I LDFLAGS:   -framework Accelerate
I CC:       Apple clang version 14.0.0 (clang-14<IP_ADDRESS>)
I CXX:      Apple clang version 14.0.0 (clang-14<IP_ADDRESS>)

make: Nothing to be done for `default'.

And this is the error logs for when I try to call whisper(...) with the broken model:
$ tsc && node ./build/test.js
[whisper-node] Transcribing: /Users/ruben/Desktop/audio.mp3

[whisper-node] No 'modelName' or 'modelPath' provided. Trying default model: base.en

[whisper-node] Problem: whisper_init_from_file: loading model from './models/ggml-base.en.bin'
whisper_model_load: loading model
whisper_model_load: invalid model data (bad magic)
whisper_init: failed to load model
error: failed to initialize whisper context

undefined
✨  Done in 3.66s.

After copy-pasting the model directly from whisper.cpp repo in /node_modules/whisper-node/lib/whisper.cpp/models/, it worked.

@rubengt01  you could try this package , i fixed all these bugs and also it will convert audio to wav format which i needed for whisper.cpp https://www.npmjs.com/package/nodejs-whisper


[PE-D][Tester D] Broken link to glossary

After clicking the hyperlink to glossary, it sends me to FAQ

Labels: severity.VeryLow type.DocumentationBug
original: yuvrajaryan/ped#1

After checking the User Guide on our website, all the links are working fine. However, in the pdf version for the user guide, it seemed that the links will bring the reader to some where near the section but not exactly at the start of the section
This might be due to printing the pdf file at 75% scale. After printing out the UG at default scale, the links work fine but the page breaks and table formatting for parameter details will look awkward.


Cent os gpu enabled

fix installation bugs for gpu driver conflict. see "hwo_to_prepare_centos_gpu_enabled_image_for_ROS_perception_module.md"

fixed previous baidu docs typos

add "how_to_understand_architecture_and_workflow"

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello Please review

Nice work! @yiakwy

Hi @yiakwy  could you please do a git rebase to upstream master before push?

@Capri2014 I have rebased the branch on origin master latest commit '384c3aa370a637d2ef970f64d4a7bb293615fa05'.  Hope it works!

@ycool, @Capri2014  Hi, I have fixed the errors and rebase the branch onto the origin master latest commit "384c3aa370a637d2ef970f64d4a7bb293615fa05". Any other suggestions to help me to make it work? Thank you!

The lint check is failed. Could you verify using "bash apollo.sh check"?

Thanks a lot for your contribution. I am going to merge your CL and we will fix the lint problem. And next time you need run bash apollo.sh check before pushing. Thanks.


Support autodoc_class_signature

autodoc_class_signature

This value selects how the signature will be displayed for the class defined by autoclass directive. The possible values are:
"mixed"
Display the signature with the class name.

"separated"
Display the signature as a method.

The default is "mixed".

https://github.com/sphinx-extensions2/sphinx-autodoc2/blob/13933a5b25a780e03f227414d432420706962212/src/autodoc2/render/rst_.py#L58
😅


Fix build on macOS M1

Hi,
Fixed a linker not found error on macOS
Reference: https://pyo3.rs/v0.18.1/building_and_distribution#macos

Oh, I built using 'cargo build' in the root and venv setup by Intellij.
I was looking to use the core in Rust though, not Python.
Tried  'make build-develop' which gives this error.
(venv) h7kanna@Harshas-MBP-6 pgpq % make build-develop
rm -rf .venv
python -m venv .venv
./.venv/bin/pip install -e ./py[test,bench]
ERROR: File "setup.py" or "setup.cfg" not found. Directory cannot be installed in editable mode: /Users/h7kanna/Repos/crates/pgpq/py
(A "pyproject.toml" file was found, but editable mode currently requires a setuptools-based build.)
WARNING: You are using pip version 21.2.4; however, version 23.0.1 is available.
You should consider upgrading via the '/Users/h7kanna/Repos/crates/pgpq/.venv/bin/python -m pip install --upgrade pip' command.

If you want to build just the rust part then cd into the core directory and treat it as a pure Rust project there. cargo build will work in that directory. cargo build does not just work for the python package, that's just how PyO3 works.
That said, from the error you're getting I'm guessing you're using an older version of Python and definitely an older version of pip (it looks like 21.2.4), I'm guessing without PEP 517 support (hence why it won't recognize the pyproject.toml and insists on a setup.py).

Ok, I will just build the core crate, just wanted to try the python tests for example usage.
Please close this PR if not needed.
(venv) h7kanna@Harshas-MBP-6 pgpq % python --version
Python 3.9.6

Python 3.9.6

Try running python -m pip install -U pip then 😄


How can I add exercise minutes manually in the Health app?

I paired my iPhone simulator with Apple Watch simulator. I want to read exercise minutes with this library but how can i do that?

To get the exercise minutes from the health kit you need to modify the plugin.
It currently supports some of the health kit parameters such as step_count, distance_walk, etc.

Fortunately, I have modified the plugin to do that 😁
Use this in the pubspec.yaml as fitkit plugin.
fit_kit:
  git:
    url: git://github.com/dinithherath/FitKit.git

And in your code to get the exercise_minutes use this snippet.
if (!permissions) {
  log.d('RequestPermissions: Denied');
} else {
  try {
    final now = DateTime.now();
    FitDataStatistics resultAllSteps;
    FitDataStatistics resultAllExercise;
    try {
      resultAllSteps = await FitKit.readStatistics(
        DataType.STEP_COUNT,
        dateFrom: DateTime(now.year, now.month, now.day),
        dateTo: now,
      );
    } catch (e) {
      resultAllSteps = null;
    }
    try {
      resultAllExercise = await FitKit.readStatistics(
        DataType.EXERCISE_TIME,
        dateFrom: DateTime(now.year, now.month, now.day),
        dateTo: now,
      );
    } catch (e) {
      resultAllExercise = null;
    }
  } on UnsupportedException catch (e) {
    print(e.toString());
  }
}

This reads data from the health kit using the iOS cumulative sum method which will eliminate duplicates from your phone and apple watch.
If you get the work done please star my repo of Fitkit  and follow me on github ❤
Thanks.


Merge PHP-7.0-Linux changes into merged-codebase

Coverage increased (+3.3%) to 42.789% when pulling<PHONE_NUMBER>3c6726bec2692d9983b8a2c69a7d80 on v-dareck:merged-codebase into 1b35af7c8bdff3c4314f9873e8f975c626131d7a on Microsoft:merged-codebase.

Coverage increased (+3.3%) to 42.789% when pulling 674e7736acd548d88bb85fdb53587716ec77db6e on v-dareck:merged-codebase into 1b35af7c8bdff3c4314f9873e8f975c626131d7a on Microsoft:merged-codebase.

Coverage increased (+3.3%) to 42.789% when pulling ea445f4a181ab4616305aad94e0c656db8b66067 on v-dareck:merged-codebase into 2185215aa667896dff4a2917e10da36631abb85a on Microsoft:merged-codebase.

Coverage increased (+3.3%) to 42.794% when pulling 044836b0485dc4261489bf228287011d1610f6a4 on v-dareck:merged-codebase into 2185215aa667896dff4a2917e10da36631abb85a on Microsoft:merged-codebase.

Coverage increased (+3.3%) to 42.794% when pulling 1f9d1583d1521b0edaf70eb10345e287d656e87d on v-dareck:merged-codebase into 2185215aa667896dff4a2917e10da36631abb85a on Microsoft:merged-codebase.


Rustup, expand collection tests

@bors r+

:pushpin: Commit e61be0b8b8c0409ea2c7afac50bfd6afc09cf811 has been approved by RalfJung

:hourglass: Testing commit e61be0b8b8c0409ea2c7afac50bfd6afc09cf811 with merge a6741b0592a2b0645a8f0352db890474fd58e23e...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing a6741b0592a2b0645a8f0352db890474fd58e23e to master...


connect to Wikidata to pull ethnicity data across

Wikidata IDs a 'Q' codes, e.g. Sir Christopher Wren == Q170373 https://www.wikidata.org/wiki/Q170373
Use python or ruby to enhance the data
Is ethnicity data even fully available?
This must be re-runnable because the raw data csv will be updated.
Write tests and run them whilst developing

Qwikidata library working. I have found that if you make repeated requests quickly most don't come through quickly. Using pandas to read data from the csv.

Initial citizenship field pulled from wikidata

Not many of the wikidata entries contain the ethnic group as a field - only 184 out of ~ 2000.


Example needs to be updated.

It looks like your user name has changed.
bankflip to bankfliptech
uses: **bankflip**/deploy-to-render@v1

Thanks for letting us know, just updating the example.


add kill method to CrateCollector and remove JobCollectContext from doCollect

a first step towards removing the circular referencing of Context/Collector.

ack


Set all cron jobs to retry 3 times

Standardize all cloud scheduler jobs to retry 3 times.

What's the retry strategy that cloud scheduler uses?

The default is immediately after failure. We can customize it if we want: https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_scheduler_job#retry_count


Add more SIP editors

Adds the following SIP editors by adding their GitHub handles to the CODEOWNERS file:

@hmalik88
@Montoya
@rekmarks (yours truly)

You should add them to SIP-1 too.


Compile a list of references for machine learning / named entity recognition/extraction

Requested by Alexis, to better understand what we are doing. Cliff will compile this

I have begun a page on the project wiki on using NER for discovery


Doc route 2

Bring back the DocRoute changes.
⚠ This is the crashing version. Do not merge unless the fix is merged into this branch. ⚠
Edit: the fix has been merged into this branch. It's good to go now.

This is now ready for review and merge and we should finally be able to move forward with the canonical document changes.

There's a decent chance that this was the culprit: https://github.com/vapor/routing-kit/pull/130
I'll retest the crashing version with the upstream change once it's released.

The crashing version still crashes despite the routing-kit fix. (In hindsight, that fix was unlikely to be the root cause anyway.)

Deployed as 2.103.0. Looking good, no crashes:


What does this code mean

This is estimating the accuracy of random choices, and the accuracy of each question is the reciprocal of the number of options

Hi, we will close this issue. Feel free to contact us if you have other questions.


Bug when using GitHub OAuth Token Secret declared in another Stack.

I have two stacks, Credentials and Pipeline. My Credentials Stack creates the Secrets so I can re-use them across many pipelines. Pipeline provisions a DelivLib pipeline and references the secrets created in the Credentials Stack.
If I use publishToGithub:
this.pipeline.publishToGitHub({
  githubRepo: repo,
  signingKey: props.signingKey,
  dryRun: true,
});

Then I get the following error.
Resource ask-sdk-github-automation-oauth-qQ8x5Z must be in ARN format or "*". (Service: AmazonIdentityManagement; Status Code: 400; Error Code: MalformedPolicyDocument; Request ID: 61b04b4f-1594-49db-96e0-c5fae15fe356; Proxy: null)

It looks like this code is mapping my ARN to its secretName :
https://github.com/cdklabs/aws-delivlib/blob/e1260dc3055ccf00dac455f30b69dc2ab98a2e20/lib/shellable.ts#L342-L353
Which is then used in aws-codebuild's Project class to create the IAM Policy:
https://github.com/aws/aws-cdk/blob/41b831a6698ee6c7a3c8968bff8273a0c7f35448/packages/%40aws-cdk/aws-codebuild/lib/project.ts#L974-L977
Except this must be an ARN and not the name. Why is the ARN mapped to a name when creating the IAM policy? Am I doing something wrong?
It's hitting this code path (if that helps)
https://github.com/aws/aws-cdk/blob/41b831a6698ee6c7a3c8968bff8273a0c7f35448/packages/%40aws-cdk/aws-codebuild/lib/project.ts#L912-L951

Hi, blocked on the same issue?
Any suggestions?


[Bug]

Is this a new bug?

[X] I believe this is a new bug
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Hi! I have problem with loading data to pinecone with spark connector. I’ve tried to follow this page from documentation. But in the article metadata is defined as plain string:
schema = StructType([
    StructField("id",StringType(),True),
    StructField("values",ArrayType(FloatType()),True),
    StructField("namespace",StringType(),True),
    StructField("metadata", StringType(), True),
    StructField("sparse_values", StructType([
        StructField("indices", ArrayType(IntegerType(), False), False),
        StructField("values", ArrayType(FloatType(), False), False)
    ]), True)
])

In my case I want to define metadata as object with 2 fields, as:
StructField(
    "metadata",
    StructType(
        [
            StructField("A", ArrayType(StringType(), False), False),
            StructField("B", StringType(), False),
        ]
    ),
    True,
),

But after such a definition I got error when trying load data into Pinecone:

Cannot write 'metadata': struct<A:array,B:string> is incompatible with string

Expected Behavior
I' like to be able to import object as metadata, since I could do that in plain python.
Steps To Reproduce
Try to import data with metadata, as:
StructField(
    "metadata",
    StructType(
        [
            StructField("A", ArrayType(StringType(), False), False),
            StructField("B", StringType(), False),
        ]
    ),
    True,
),

Relevant log output
- Cannot write 'metadata': struct<A:array<string>,B:string> is incompatible with string

Environment
- **OS**:
- **Language version**:
- **Pinecone client version**:

Additional Context
No response

Hi,
If you look at the source code, it's expecting the the JSON string representing the vector's metadata.
To get it, you can use the sql function to_json. It will convert your metadata (StructType) to a JSON string.
from pyspark.sql.functions import to_json

df.select(
        col("id"),
        col("namespace"),
        col("values"),
        to_json(col("metadata")),
        col("sparse_values")
)

Thanks @lugonthier for responding! @JanKulbinski closing this issue but if you have any further issues, feel free to open this or a new one.


pull request for e2e test at 11/22/2016 17:56:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Question]: No module named 'RAGFlow'

Describe your problem
according  https://ragflow.io/docs/v0.15.0/python_api_reference#stop-parsing-documents
after
 pip install ragflow-sdk

then
from ragflow_sdk import RAGFlow

meet  it thows :
No module named 'RAGFlow'

why? and how
``
from RAGFlow import DataSet
?

thanks.

I tried and it's OK. You'd better to check your environment.
(ragflow_env) weilongma@ThinkBook:~/Documents/development/ragflow/huggingface.co/InfiniFlow/deepdoc$ pip install ragflow-sdk
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting ragflow-sdk
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/7e/96/4c7f2e73bb12127db5f32dbe294ac029aba65077e4a97adeffb8e72afd7e/ragflow_sdk-0.15.0-py3-none-any.whl (11 kB)
Requirement already satisfied: beartype<0.19.0,>=0.18.5 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from ragflow-sdk) (0.18.5)
Requirement already satisfied: pytest<9.0.0,>=8.0.0 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from ragflow-sdk) (8.3.4)
Requirement already satisfied: requests<3.0.0,>=2.30.0 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from ragflow-sdk) (2.32.2)
Requirement already satisfied: iniconfig in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from pytest<9.0.0,>=8.0.0->ragflow-sdk) (2.0.0)
Requirement already satisfied: packaging in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from pytest<9.0.0,>=8.0.0->ragflow-sdk) (24.2)
Requirement already satisfied: pluggy<2,>=1.5 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from pytest<9.0.0,>=8.0.0->ragflow-sdk) (1.5.0)
Requirement already satisfied: charset-normalizer<4,>=2 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (3.4.0)
Requirement already satisfied: idna<4,>=2.5 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (3.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (2.2.3)
Requirement already satisfied: certifi>=2017.4.17 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (2024.8.30)
Installing collected packages: ragflow-sdk
Successfully installed ragflow-sdk-0.15.0
(ragflow_env) weilongma@ThinkBook:~/Documents/development/ragflow/huggingface.co/InfiniFlow/deepdoc$ python
Python 3.11.6 (main, Apr 10 2024, 17:26:07) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from ragflow_sdk import RAGFlow
>>>

I tried and it's OK. You'd better to check your environment.
(ragflow_env) weilongma@ThinkBook:~/Documents/development/ragflow/huggingface.co/InfiniFlow/deepdoc$ pip install ragflow-sdk
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting ragflow-sdk
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/7e/96/4c7f2e73bb12127db5f32dbe294ac029aba65077e4a97adeffb8e72afd7e/ragflow_sdk-0.15.0-py3-none-any.whl (11 kB)
Requirement already satisfied: beartype<0.19.0,>=0.18.5 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from ragflow-sdk) (0.18.5)
Requirement already satisfied: pytest<9.0.0,>=8.0.0 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from ragflow-sdk) (8.3.4)
Requirement already satisfied: requests<3.0.0,>=2.30.0 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from ragflow-sdk) (2.32.2)
Requirement already satisfied: iniconfig in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from pytest<9.0.0,>=8.0.0->ragflow-sdk) (2.0.0)
Requirement already satisfied: packaging in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from pytest<9.0.0,>=8.0.0->ragflow-sdk) (24.2)
Requirement already satisfied: pluggy<2,>=1.5 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from pytest<9.0.0,>=8.0.0->ragflow-sdk) (1.5.0)
Requirement already satisfied: charset-normalizer<4,>=2 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (3.4.0)
Requirement already satisfied: idna<4,>=2.5 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (3.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (2.2.3)
Requirement already satisfied: certifi>=2017.4.17 in /home/weilongma/ragflow_env/lib/python3.11/site-packages (from requests<3.0.0,>=2.30.0->ragflow-sdk) (2024.8.30)
Installing collected packages: ragflow-sdk
Successfully installed ragflow-sdk-0.15.0
(ragflow_env) weilongma@ThinkBook:~/Documents/development/ragflow/huggingface.co/InfiniFlow/deepdoc$ python
Python 3.11.6 (main, Apr 10 2024, 17:26:07) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from ragflow_sdk import RAGFlow
>>>

still not working on macosx M1 :(


v3.7.1 updates

Merge using a merge commit
(Do not squash)

Revert the mistaken merge of main into v3.7.x (875e890)
Cherry-pick area weighted memory fix (c6151e819189ca213b370ddf4ff38d8511c7e012)
Update What's New

Combined, this should update v3.7.x to the state at v3.7.0 plus the change in #5767.

Thanks @bjlittle!


[add to app][multiple_flutters]how to pass params to Flutter module

how can I pass params from Native to Flutter with Flutter Engine Groups API?
@pragma('vm:entry-point')
void topMain() => runApp(const MyApp(color: Colors.green));
for example. I want to run with Flutter "topMian" with a param "BookId"
➜  ~ flutter doctor
[✓] Flutter (Channel stable, 2.8.1, on Mac OS X 10.15.7 19H2 darwin-x64, locale
zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version
31.0.0-rc4)

@xuyisheng
I suggest you to ask this question on support channels like StackOverflow since this is more of a how to question.
If you don't get any solution and would like this to be added into add2app documentation, write in comments and I'll reopen it.

I searched in StackOverflow and I did not find any solution, there is a 'options' param in @pragma('vm:entry-point'), but there is no way to pass param in Java/Kotlin code, pls show me how to do it, and added to the documentation

Thanks for the feedback. Reopening.

Can you take a look at this github examples and see if they help ?

Can you take a look at this github examples and see if they help ?

yes, this is the example I'm referring to, but it doesn't pass any parameters when launching the FlutterActivity

Can you take a look at this github examples and see if they help ?

yes, this is the example I'm referring to, but it doesn't pass any parameters when launching the FlutterActivity

code in the demo:
EngineBindings(activity = this, delegate = this, entrypoint = "main")

there is no way to pass any parameters

Any progress?

Any plan to support it ,i was waiting this day after day


Fixed bug when the file from goToDefinition is not in subdirectory

the definition feature didn't work when the file returned by the server wasn't in the working directory, as is often the case with dependencies. This commit fixes this bug.

If I'm not mistaken, that line was in there so that the name of the file wouldn't appear too long in the status bar / tab bar. One thing we could do is test whether the file path starts with the cwd and only truncate it then. The other thing we could do is set the name of the buffer separately from the path, and truncate the name however we want.

@akriegman : yes correct. What about if the path is calculated as a relative path from where the cwd is? That should keep it not much longer than it is right now without loosing the ability to open stuff outside the cwd.

That's not a bad option. I like the idea of truncating the name if it's too long, since for example with cargo my dependencies are all in a folder whose name is a long github url. So we could do something like (in pseudocode):
bp.path = filename -- absolute path
bp.name = filename.relative_to(cwd)
if #bp.name > 30 {
    bp.name = ".." .. bp.name.truncate_right(30)
}

or, if there isn't some easily accessible function for calculating relative paths, we can do:
bp.path = filename
bp.name = if filename.starts_with(cwd) {
    filename.strip_prefix(cwd)
} else if #filename > 30 {
    ".." .. filename.truncate_right(30)
} else {
    filename
} -- optionally also try to replace home folder with ~

I like the second solution! That would make it easy enough to implement and at the same time look nice. However, if the truncate_right is applied, I would suggest to use three periods (so "..." instead of "..") to indicate that there is something before it. This should make it easier to identify that it is not the relative path but an ellipsis of a path.

Any updates?

Hey @hikkidev , @akriegman  - based on our discussion above, I created a new PR-43 to implement the changes accordingly. Please take a look and let me know if you see any issues.

@AndCake Thank you


Add a wait method in components/flux_led/

This improve stability, waiting for device to change state beforeanything.
Description:
Related issue (if applicable): fixes #27755
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

Hi @chocobn69,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @chocobn69,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Work to do:

[ ] Turn flux_led compoments async
[ ] Add a parameter delay to control waiting time (default 1sec ?)
[ ] Change documentation according to this


Docs/enhance translation script

Enhance translation script to respect markdown formatting.
Using DeepL's XML capabilities, transforming markdown formatting into XML tags and reverting after translation.

Includes updated German usage documentation files
There were only two errors in formatting links that needed to be resolved manually. One grammatical change (German verbs move to the very end :roll_eyes: ) introduced a bare link (cve-usage.de.md) and one XML tag not handled correctly (cvss_v3-usage.en.md).

Adds German spec documentation files
Some manual adjustments had to be made for links (some tags not handled correctly) and for quotes (> introduced for >)


[FormBuilder] Support more validators

Ideally we would have the most common types of field and they would come with sensible defaults including validation as standard.  I was wondering about using validator.js for this:
https://github.com/chriso/validator.js
https://www.npmjs.com/package/@types/validator
Like you know how in html a Form at it's most basic is:
  <form>
    <input name="name" placeholder="Name" />
    <input name="email" placeholder="Email" type="email" />
    <input type="submit">
  </form>

I wonder if we could make BasicFields (maybe in Fulma?) as close as possible to this sort of simple experience, but of course with all the power of F# and this library behind the simple interface
Apologies this has little to with React, more to do with "optimized experience"
Originally posted by @fergusmeiklejohn in https://github.com/MangelMaxime/Thoth/issues/90#issuecomment-442742896

the most common types of field

I think we already support the most common types of field. By that, I mean input, radioButton, select, textarea, checkbox.

with sensible defaults including validation as standard

About adding more validators yes this is possible. The ideal would be to either use an existing JavaScript library or create our own so we can extends it.
And I don't think creating an BasicEmailInput, BasicNumberInput, etc. is a solution because there will have a lot of code duplications.
I would prefer to go with something like:
BasicInput
    .Create("email")
    .WithType("email")
    .IsEmail()
    .IsRequired()
    .WithDefaultRenderer()

And yes it probably possible to make it mark type = "email" when you use IsEmail, but it can be difficult to provide a good UX doing that. Because then some of the configuration because implicit and so the user need more knowledge about it.

I wonder if we could make BasicFields (maybe in Fulma?) as close as possible to this sort of simple experience, but of course with all the power of F# and this library behind the simple interface

The BasicFields, will never depends on Fulma because I want everyone to be able to use it and if Fulma is a dependencies then it is a no go. There will be a dedicated FormBuilder library for Fulma.
The most powerful feature of FormBuilder is that the core is able to manage any type of Input and you can create your own depending on your needs:
For example, at work I needed a sort of color picker, I have been able to create my specific field in 30 minutes. And use it in several places of my application "for free" now.

I moved this issue to another repository, and further work will take place there.


Make annotations compile-time only

Would it be possible to make all new-style meta-based macro annotations be compileTimeOnly automatically? Or else, at least to require them all to have that annotation? It seems like a good time to do it now, before "the ship has sailed on this" (as discussed in the comments on http://docs.scala-lang.org/overviews/macros/annotations.html) too.

That's a very good suggestion. I'll make sure to fix this before a stable release.

Fixed in https://github.com/scalameta/paradise/commit/b8840b5902052d7194ce48b9a3efa2860079a8e3#diff-4c99817556e14f4c8003b48cf6f40fedR45.


Support for sending email via SMTP

What
This change adds the support for sending the email via SMTP.
Why
This is particularly useful when the user wants to test the email locally using mailcatcher.
How this works
It utilizes the SendGrid API to retrieve the template based on the template id, perform necessary substitutions on the email body and send it using Mail.
Notes
The implementation is still sketchy though but it works.

I was talking with Justin and I'm not sure we understand the value of this - we can already use this in development if the email is on sendgrid and send it to any email address. Sure it won't go through mailcatcher but it is closer to the real world scenario - also as we're reimplementing part of the substitution code it seems much more error prone. @nistujri any opinions?

@JamesWatling having read this. I understand it better now. I'm more okay with it. This is using the ::Mail (i assume that's ActionMailer by default). This would allow me to get it in mailcatcher instead of having to "go out" and check dev_catchall.
There needs to be a minor version bump.
A small point - dev_catch_all should probably be renamed to force_mail_to w/ backwards compatibility if we're looking to make this more official.
I actually have trouble with requiring the initialize/sendgrid_mailer.rb. By default that should be part of the gem, self-init, and only be overridden if necessary.

@nitsujri that's the intention of all these. In development, I don't feel like really sending the email. I would say it's pretty narrow use-case, but somewhat convenient for testing. If the :smtp is not the right naming of the delivery_method, maybe we could call it :debug.
Agree on renaming the dev_catch_all to something else, I'm good with the suggested alternative name.
In sum, I would

[ ] - Bump version
[ ] - Rename dev_catch_all
[ ] - Tinkering with the initializer

Bump version to 0.2.0 but renaming dev_catch_all to force_mail_to seems to break backward compatibility. 😅


pull Elasticsearch:latest image fail

Expected behavior
Downloading Image of Elasticsearch
Actual behavior

Information about the Issue
Env: Mac Mojave 10.14.1
Steps to reproduce the behavior

Open the Kitematic app
Click "NEW" and select the Elasticsearch
The 404 stuff happens while when I did the same on a, maybe MongoDb image, the downloading Image page shows up

Same issue here.

Dupe of #4171.


"Write after end" error

Hi,
i'm using prerender (version 1.3.0) on my NodeJS+Express app, and i have this crash after some requests:
events.js:85       throw er; // Unhandled 'error' event             ^ Error: write after end     at ServerResponse.OutgoingMessage.write (_http_outgoing.js:413:15)     at ServerResponse.res.write (/home/scx-page/app/node_modules/compression/index.js:95:17)     at ServerResponse.res.end (/home/scx-page/app/node_modules/compression/index.js:112:14)     at ServerResponse.send (/home/scx-page/app/node_modules/express/lib/response.js:191:8)     at fn (/home/scx-page/app/node_modules/express/lib/response.js:896:10)     at Function.exports.swig.render (/home/scx-page/app/node_modules/consolidate/lib/consolidate.js:247:5)     at /home/scx-page/app/node_modules/consolidate/lib/consolidate.js:146:25     at /home/scx-page/app/node_modules/consolidate/lib/consolidate.js:99:5     at fs.js:334:14     at FSReqWrap.oncomplete (fs.js:95:15)
To reproduce this bug:

Open www.mydomain.com/test?escaped_fragment=
The node app crash.

Without prerender it works correctly.
Thank you.

Can you try upgrading to the latest version of Prerender? That's a really old version.

@thoop it's true, the latest version fixes the bug. Thank you.

hi @thoop, i have deeply tested the latest version "2.2.0" and i found that it's affected by the same bug reported.
Thank you.

I fixed the bug updating Express framework.

The latest version of Prerender as of writing this is 4.0.5. Glad you fixed it by upgrading Express!


make the banlist display the reasoning for all the times someone has been banned if they have been banned more than once

make the .banlist command display the reasoning for all the times someone has been banned if they have been banned more than once
This suggestion was created by a user and sent by the bot:
jukebox-botto#8602

while possible, out of scope for the command just used as a help for searching bans and reasoning


Update to Kamon 0.6.1

Updated to Kammon 0.6.1 and akka 2.4.8
Updated Readme file to include new docker image installation for statD+graphite+grafana

Awesome. Thanks 😃


Refactor CI/CD scripts, remove vendor directory and migrate circleci to github workflow

Issue- https://github.com/litmuschaos/litmus/issues/2481
Changes

migrate circleci to github workflow
Remove vendor directory
remove go-multiarch-build.sh and move its logic in Makefile
remove push script and move its logic to github workflow
Simplify and clean the Makefile
Refactor Github workflow and add Trivy GitHub action

Need to setup credentials as GitHub secret @ksatchit @rajdas98

Also, a binary test ARM would help!

@uditgaurav For ARM

Image- imrajdas/chaos-operator:ci


Support reauth dialog on Bad Credentials

Implements the new reauth functionality.

Current issue, should only show once.

Need to have a look at https://github.com/home-assistant/core/pull/48962 :-)

Superseded by #452.


Temp Fix getStatus

In progress fix for the Tyler GetStatus Issues.
I won't be able to finish it until at least Jun 14th or 15th, as I'll be away from my computer.
Here's the full error in case I lose it:

response_code: 500, data: {'cause2': 'com.sun.istack.SAXParseException2; lineNumber: 0; columnNumber: 0; unexpected element (uri:"urn:tyler:efm:services:schema:Common", local:"Status"). Expected elements are <{urn:tyler:efm:services:schema:Common}RestrictFiling>,<{urn:tyler:efm:services:schema:Common}Role>,<{urn:tyler:efm:services:schema:Common}RestrictFilingComment>,<{urn:tyler:efm:services:schema:Common}Email>,<{urn:tyler:efm:services:schema:Common}IsUndeliverable>,<{urn:tyler:efm:services:schema:Common}FirstName>,<{urn:tyler:efm:services:schema:Common}LastLoginDate>,<{urn:tyler:efm:services:schema:Common}LastName>,<{urn:tyler:efm:services:schema:Common}MiddleName>', 'cause1': 'jakarta.xml.bind.UnmarshalException\n - with linked exception:\n[com.sun.istack.SAXParseException2; lineNumber: 0; columnNumber: 0; unexpected element (uri:"urn:tyler:efm:services:schema:Common", local:"Status"). Expected elements are <{urn:tyler:efm:services:schema:Common}RestrictFiling>,<{urn:tyler:efm:services:schema:Common}Role>,<{urn:tyler:efm:services:schema:Common}RestrictFilingComment>,<{urn:tyler:efm:services:schema:Common}Email>,<{urn:tyler:efm:services:schema:Common}IsUndeliverable>,<{urn:tyler:efm:services:schema:Common}FirstName>,<{urn:tyler:efm:services:schema:Common}LastLoginDate>,<{urn:tyler:efm:services:schema:Common}LastName>,<{urn:tyler:efm:services:schema:Common}MiddleName>]', 'cause3': 'jakarta.xml.bind.UnmarshalException: unexpected element (uri:"urn:tyler:efm:services:schema:Common", local:"Status"). Expected elements are <{urn:tyler:efm:services:schema:Common}RestrictFiling>,<{urn:tyler:efm:services:schema:Common}Role>,<{urn:tyler:efm:services:schema:Common}RestrictFilingComment>,<{urn:tyler:efm:services:schema:Common}Email>,<{urn:tyler:efm:services:schema:Common}IsUndeliverable>,<{urn:tyler:efm:services:schema:Common}FirstName>,<{urn:tyler:efm:services:schema:Common}LastLoginDate>,<{urn:tyler:efm:services:schema:Common}LastName>,<{urn:tyler:efm:services:schema:Common}MiddleName>', 'cause0': 'jakarta.xml.ws.soap.SOAPFaultException: Unmarshalling Error: unexpected element (uri:"urn:tyler:efm:services:schema:Common", local:"Status"). Expected elements are <{urn:tyler:efm:services:schema:Common}RestrictFiling>,<{urn:tyler:efm:services:schema:Common}Role>,<{urn:tyler:efm:services:schema:Common}RestrictFilingComment>,<{urn:tyler:efm:services:schema:Common}Email>,<{urn:tyler:efm:services:schema:Common}IsUndeliverable>,<{urn:tyler:efm:services:schema:Common}FirstName>,<{urn:tyler:efm:services:schema:Common}LastLoginDate>,<{urn:tyler:efm:services:schema:Common}LastName>,<{urn:tyler:efm:services:schema:Common}MiddleName> ', 'message': 'jakarta.xml.ws.soap.SOAPFaultException: Unmarshalling Error: unexpected element (uri:"urn:tyler:efm:services:schema:Common", local:"Status"). Expected elements are <{urn:tyler:efm:services:schema:Common}RestrictFiling>,<{urn:tyler:efm:services:schema:Common}Role>,<{urn:tyler:efm:services:schema:Common}RestrictFilingComment>,<{urn:tyler:efm:services:schema:Common}Email>,<{urn:tyler:efm:services:schema:Common}IsUndeliverable>,<{urn:tyler:efm:services:schema:Common}FirstName>,<{urn:tyler:efm:services:schema:Common}LastLoginDate>,<{urn:tyler:efm:services:schema:Common}LastName>,<{urn:tyler:efm:services:schema:Common}MiddleName> ', 'url': '/jurisdictions/illinois/adminusers/user', 'status': '500'}

Ah, does appear to be a lot of sorting changes. Wonder why the ordering changed..? 🤔 Changes look pretty good to me.
I did notice that the WebServiceClient WSDL locations changed from classpath to file resources. Is that intentional?
Example of New Value:
@WebServiceClient(name = "EfmUserService",
                  wsdlLocation = "file:illinois-EFMUserServiceSingle.svc.wsdl",
                  targetNamespace = "urn:tyler:efm:services")

Previously:
                  wsdlLocation = "classpath:wsdl/EFMUserServiceSingle.svc.wsdl",

Ah, does appear to be a lot of sorting changes. Wonder why the ordering changed..? 🤔

:shrug: I think it has something to do with how wsdl2java works, I assume it's using Sets or something unsorted internally during code generation. It'd be so nice if that wasn't an issue, but eh.

I did notice that the WebServiceClient WSDL locations changed from classpath to file resources. Is that intentional?

That's not! That is another wsdl2java makes for you, and we have to manually revert.


license for de-ae

Hi. Thank you for sharing this amazing works.
I noticed that this repository is licensed under Apache-2.0. However, I couldn't find any specific mention regarding the license for the model's weights of de-ae (https://huggingface.co/mit-han-lab/dc-ae-f32c32-in-1.0).
Is it available for commercial use?
Thanks in advance!

Seems like the weights are apache 2 too: https://huggingface.co/mit-han-lab/dc-ae-f32c32-sana-1.0-diffusers/discussions/2

Yes, the license is also Apache-2.0.

HEy can you please share the training cost / gpu hour
rough estimates will work for me


Support for T5

Do you have plans to support encoder-decoder models like T5? It will be great to have T5 with flash attention 😃

What specific model would you like supported? We would only take this on if we saw sufficient interest (but in practice we see heavy movement towards decoder-only models).

Decoder only models are great for generative use cases but T5 family is the work horse for many discriminative tasks. For example, the flan-t5-base model has 2M downloads on Huggingface in the last month. Support for flan-t5 will add a huge value to the community.

It'd be great to have T5 models here as well.

I'm going to try to turn MaxText into encoder-decoder anyway, so native support is of course also appreciated :)

https://github.com/p-doom/maxtext/tree/colab_temp
We finally came around to implement encoder-decoder models in our maxtext fork. The synthetic data pipeline seems to work. Will add support for the real data pipeline later today.

okay I was a bit too fast, still have to fix a few things.


[Feature] command completion for zsh

As soon as rez installation is finished, the following message is shown:
You may also want to source the completion script (for bash):
source /home/sntshk/rez/completion/complete.sh

That directory contains 2 files, for bash and for csh.
I'm not quite sure how autocompletion is handled in zsh (autocompletion is the selling point of zsh). But there must be some way we can autocomplete package name after rez env?
Note: This issue is also related to #451.

I have a WIP zsh plugin attempt I plan to PR soon.

Fixed by #711


missing GHSA advisories

There are some advisories that are in GitHub but not in OSV, @oliverchang mentioned that there might be some encoding issues but possible bugs as well.
GHSA-x4rg-4545-4w7w
GHSA-v62j-cxhh-fq22
GHSA-2w7w-2j92-44hx
GHSA-g2qw-6vrr-v6pq
GHSA-fj6c-prgj-gr3r
GHSA-5pg8-f89x-wjcx
GHSA-789v-h9hw-38pg
GHSA-wh77-3x4m-4q9g

Following up on this:
Thanks to @another-rex and @michaelkedar, 4 of these have been fixed (GHSA-v62j-cxhh-fq22, GHSA-g2qw-6vrr-v6pq, GHSA-5pg8-f89x-wjcx, GHSA-789v-h9hw-38pg)
The rest appear to be due to data quality issues from GitHub that we'll follow up on.

All affected GHSAs are now in the OSV.dev database.


Boids example not loading

I just installed 2022.2.2. Clicked on the Examples, press play, nothing happens.

I think the example is just the action graph and is missing the scene setup (e.g. 2023-12-21 00:07:51  [Warning] [omni.graph.core.plugin] Could not find node type interface for 'omni.graph.action_nodes.OnLoaded'
To clarify, I am not using the omnigraph node, I am just clicking on the example file

When adding a Tick in the graph, it asks for an updated warp

after that, it asks to updated usdrt

But there doesnt seem to be that option in 2023.2.2 beta

Hi @cadop , this specific sample indeed requires a version of Composer USD that isn't released yet, so it won't run on current versions. We need to make this clearer somehow. Apologies for the inconvenience caused!

I guess it shouldn't have been included in the release?  Can the release of warp get updated to remove the example? It's not possible to run it all, so kinda weird.

@christophercrouzet Is this fixed now?

It should work with Kit 106.0, which has just been released, but USD Composer hasn't been updated yet.

I can open the usda file directly in IsaacSim 4.0 and it works.
A note though; the link on the graph object is broken.

Goes to: https://docs.omniverse.nvidia.com/extensions/latest/ext_omnigraph/node-library/nodes/omni-warp/warpsampleprimflocking-1.html

Thanks @cadop! This seems to be the case for other nodes as well (not only Warp ones), I'll report this to the corresponding team.


Revamp Transport so they always build a full Response object

This should fix #1048.
It'll be released as a major version with breaking changes.

@davidbrochart If you have a moment, it could be great if you could install this branch on your project and check if the CookieTransport works as expected.
I've checked on my side and everything looks ok, but I just want to be sure I don't break things again :)
You can install it like this:
pip uninstall fastapi-users
pip install git+https://github.com/fastapi-users/fastapi-users.git@transport-responses

The GitHubTransport class should be changed like this:
class GitHubTransport(CookieTransport):
    async def get_login_response(self, token: str):
        response = await super().get_login_response(token, response)
        response.status_code = status.HTTP_302_FOUND
        response.headers["Location"] = "/lab"
        return response

I get this error:
  File "/home/david/github/davidbrochart/jupyverse/plugins/auth/fps_auth/backends.py", line 164, in current_user
    await cookie_authentication.login(get_jwt_strategy(), active_user, response)
TypeError: AuthenticationBackend.login() takes 3 positional arguments but 4 were given

If I change to:
await cookie_authentication.login(get_jwt_strategy(), active_user)

The error disappears but cookie authentication still doesn't work.

I guess the problem comes from this implementation:
async def current_user(
    response: Response,
    token: Optional[str] = None,
    user: User = Depends(
        fapi_users.current_user(optional=True, get_enabled_backends=get_enabled_backends)
    ),
    user_db=Depends(get_user_db),
    auth_config=Depends(get_auth_config),
):
    active_user = user

    if auth_config.collaborative:
        if not active_user and auth_config.mode == "noauth":
            active_user = await create_guest(user_db, auth_config)
            await cookie_authentication.login(get_jwt_strategy(), active_user, response)

        elif not active_user and auth_config.mode == "token":
            global_user = await user_db.get_by_email(auth_config.global_email)
            if global_user and global_user.hashed_password == token:
                active_user = await create_guest(user_db, auth_config)
                await cookie_authentication.login(get_jwt_strategy(), active_user, response)
    else:
        if auth_config.mode == "token":
            global_user = await user_db.get_by_email(auth_config.global_email)
            if global_user and global_user.hashed_password == token:
                active_user = global_user
                await cookie_authentication.login(get_jwt_strategy(), active_user, response)

    if active_user:
        return active_user

    elif auth_config.login_url:
        raise RedirectException(auth_config.login_url)

    else:
        raise HTTPException(status_code=status.HTTP_401_UNAUTHORIZED)

I'm not sure I totally get the purpose of this function. It seems to both melt the logic to return the active user and set the cookie?

Yes, depending on the authentication mode, a cookie is set. For instance, no cookie is set if the mode is noauth. In this case, we always get an active user.

Ok, I see. The tricky part is that you only use the .set_cookie effect of the login method, but actually don't really care about the response itself.
What I could do is to put the set_cookie part in a separate method you could call on your response 🤔

Not sure to understand, but I can help with testing in jupyverse.

Here is the problem:

FastAPI has a quite special mechanism allowing you to customize the response headers, status code or cookies through dependency injection; while still having the ability to just return data (like a Pydantic object) at the end of the handler. Typically:

@app.get("/")
async def get_item(response: Response):
    response.set_cookie(...)
    response.headers["Foo"] = "Bar"
    return {"item": "foobar"}

Here, the response will be handled by FastAPI and return a proper JSON response with {"item": "foobar"} but we'll do have our cookie and the Foo header. We just had to use this "virtual" response object from the dependency injection.

Sometimes however, we need a full control of how the response is built. In this case, we build and return a full response object ourselves:

@app.get("/")
async def get_item():
    response = JSONResponse({"item": "foobar"})
    response.set_cookie(...)
    response.headers["Foo"] = "Bar"
    return response

In this case, the manually built response takes precedence. If we were doing operations on the "virtual" response object, they would be entirely lost.
Until now, the CookieTransport was using the "virtual" response approach. However, it was causing some issues and weirdnesses. In this PR, we change this to use the "manual response object" approach.
This is why it breaks your current_user function: you were relying on the behavior allowing us to add cookies on the virtual response object but still return your own response.
Your case is a bit special, and I'm not entirely convinced by this function that basically does two things: login the user and return it. Would it be possible for the Jupyter server to first reach a login endpoint that would check for the right user configuration, set the cookie, etc. and keep the current_user dependency dead simple?

Thanks for the explanation.

Would it be possible for the Jupyter server to first reach a login endpoint that would check for the right user configuration, set the cookie, etc. and keep the current_user dependency dead simple?

Maybe, I would need to look at it but I'm not sure when I will find the time.

Will this break fastapi-users-tortoise? @frankie567 @Tobi-De

Will this break fastapi-users-tortoise? @frankie567 @Tobi-De

No, I don't think so, it doesn't touch anything to the database logic.

I've been thinking about it and the thing is that in Jupyter we can log in at any endpoint if e.g. we provide a token in the URL. In our current_user implementation, we could redirect to a login endpoint and forward the token, but we would need to come back to the original endpoint. I don't know if it's the right approach or if it's possible.

I've been thinking about it and the thing is that in Jupyter we can log in at any endpoint if e.g. we provide a token in the URL. In our current_user implementation, we could redirect to a login endpoint and forward the token, but we would need to come back to the original endpoint. I don't know if it's the right approach or if it's possible.

Ok, I see. I'll make some changes to my PR so you can keep a similar approach.
I'll be on holiday for the next two weeks, so don't expect any news on this subject for a few days 😉

Thanks so much François, envoy your holiday!

@davidbrochart I'm trying to come up with the best solution for jupyter. Could you give me an overview of the different ways of authentication on the server? I see there is a difference between a "collaborative" mode and a non-collaborative one.

Currently, when not in collaborative mode (i.e. only one user can work on a document), there is:

noauth: no authentication, all the endpoints are unprotected.
token: token authentication, the server generates a token that the client must include in the first request as a query parameter. This sets a cookie and the token query parameter is not needed anymore in subsequent requests.

In collaborative mode, we need a notion of identity because a user editing a document will see e.g. the cursors of other users editing the same document. This is still a work in progress, until we use an identity provider and get proper identities. But for now, we do the following:

in noauth: we create a "guest" user with a random ID and set a cookie which identifies that user. The guest user inherits the settings of a "global" user but a changing them won't change the global user settings (they are copied).
in token: we use a "global" user that exists in the database, and that has the token as its hashed password. When the user sends the token in their first request, we check it with the global user hashed password, and if it matches we create a guest user and set a cookie.

Simple, isn't it? :smile:
I had to look up the code, I don't remember how we ended up with this solution. It may be too complicated, and we are not experts for sure, but that's the current state.
The thing is that we have to cover a lot of use cases, from completely unprotected to (soon) fully authenticated/authorized users (hopefully using Fief). But feel free to suggest other solutions, we value your feedback a lot.

Thanks @davidbrochart! That's indeed a bit weird, but I understand it's a transitive state :)
In the current state, I'm really wondering if FastAPI Users is useful for you; it looks to me it adds more problems than it solves 🙃
If I understand you correctly, you have no use for registration or login routes, right? I'm not even sure you need to actually store those "fake" users in a database 🤔

The goal is to provide real user authentication and authorization, and we made some progress in that direction at some point, where we could authenticate with a GitHub account. I'm not sure it still works, but this is still the goal. Fief would be a good candidate too, as we will need RBAC.
So registration and login will be needed, and the database is needed to store user settings, even though currently users are kind of fake.

What are plans for the idea behind the PR considering issue raised in #1037

I'll (finally) go forward with this as I think it's more sensible to implement it this way. It'll be released in v11 as a major breaking change.

@davidbrochart I've added private methods to CookieTransport so you can easily adapt your implementation of current_user. So this part:
await cookie_authentication.login(get_jwt_strategy(), user, response)

will become:
token = await get_jwt_strategy().write_token(user)
cookie_authentication.transport._set_login_cookie(response, token)

I checked that with these changes everything is fine in Jupyverse, thanks @frankie567 !


[Doc] Move order of fields listed in table to fill google IDP details according to the UI

It's better to reorder the fields in Table listed under 4th step of 'Configure Google' [1] according to the UI in Identity Server side while configure Google as IDP. So the idea order should be 'Enable', 'Default', 'Client id', 'Client Secret', 'Callback url' and 'Additional Query Parameters'.
[1] https://docs.wso2.com/display/IS540/Configuring+Google

This is already fixed in docs.


add mc-cc-scripts.github.io to domains

Also fixes spacing for consistence.

SCM is a Script Manager to easily install programs from GitHub or Pastebin without having to care about libraries too much.

Can you revert the changes to the other lines please? Just makes it easier to track the history.

Sure, I've undone the previous changes and now only pushed the single line.
Hope it's ok now!

Thanks!


Only bundle NullL10n in GENERIC builds (bug 1859818)

Please note: This needs the Fluent PR to land first, since currently e.g. the Firefox-l10n depends on the web/l10n_utils.js file.

/botio test


Adding SSHKeyPath to drivers so it's listed in the inspect output

Fixes #1207
Signed-off-by: Dave Henderson<EMAIL_ADDRESS>

/cc @ehazlett @nathanleclaire @efrecon

I'm not quite sold on this.  I don't really want to keep expanding the scope of inspect, it was originally added simply as a way to quickly debug and figure out what had been marshalled to disk after a create.  More fields in the structs == more state to keep track of == more things which are likely to go wrong IMO.  There's a lot of code duplication as well.
It sounds like a --ssh-dry-run option like I mentioned might solve @efrecon's use case better, no?  IIRC they are interested in getting access to an ssh command with the proper arguments to use with rsync.

--ssh-dry-run (or perhaps just --dry-run?) would solve my use case. As long as it is possible to access the ssh command, any way would do. In machinery, I have already made use of this twice:

Once to guess the scp command when there was no docker-machine scp yet.
Now to give away the command to rsync for copying trees.

On the other hand, @nathanleclaire, even though I fully understand your point, it feels like the identity information is the only missing part from inspect. There is already information about the port number for example... I let you decide, since you all have the big picture, as said before --dry-run solves my use case(s).

Yeah I'm on the fence as well.  Although the key info is static so it does seem to make sense in inspect -- but I agree I don't want to keep creeping things in to it.

Been mulling over @nathanleclaire's comments for a little while, and I've been flip-flopping between both sides of the fence... I think I still want to put SSHKeyPath in inspect's output, though.
I guess the underlying problem here is inspect was originally meant as a debugging tool, but there seems to be growing demand for people to be able to use it to integrate Machine into other tools. For my part, I think this is a good thing... inspect is essentially public API now (well, as much as it can be in a 0.x release ;)), and I think it'd be good for it to be useful beyond just debugging purposes.
I can understand the reluctance to track more state, but IMO in this case it makes sense. What we're doing right now is creating a key pair (i.e. more state), but we're not tracking that key pair's location except by the assumption that the driver's GetSSHKeyPath() function will always return the right path. IMO this isn't a good assumption, because if the currently-hard-coded-in-all-drivers value of "id_rsa" ever changes for a driver (or if a user wants to use their own key pair for some reason), existing machines will be broken.
I also totally agree that all the code duplication is a bad thing. But I think that's something that needs to be addressed separately (there's lots of other fields that get duplicated).
Oh, and one last point - the generic driver already exposes its SSHKey field to inspect, so there's already a precedent.

I should clarify that upon reflection, I'm not really opposed to showing the SSH key path in inspect, in fact showing things like this, driver status, etc. could be quite useful, but I think we have two main hurdles we need to deal with before adding more functionality to inspect like this:

Hardcoded path values in the machine config are problematic in general.  If we stored them in a fashion which was more akin to "SSHKeyPath": "${STORE_PATH}/machines/${MCN_NAME}" (just spitballing on this syntax) and did custom de-marshalling (remember Windows in this puzzle as well), we could be a step closer to portable config.  Putting this on disk just exacerbates the problem.  We've been seeing issues lately where, say, users try to move their ~/.docker/machine directory to another computer, and can't use their machines because the paths are all wrong in the config (even though it could probably work with cloud providers).  To resolve these problems we need a better way of saying, "Go look for this value before you show it to the user".
Code / functionality duplication in the drivers.  We're long overdue for consolidating common fields like SSH user, memory, etc. in general into an embedded base struct, and things like this will just make it harder to do.  I think we need to fix our situation with that first before adding more stuff.  Unfortunately, it's been my experience that if things don't get fixed up now, they never will and they will cause problems down the line.

I can understand the reluctance to track more state, but IMO in this case it makes sense. What we're doing right now is creating a key pair (i.e. more state), but we're not tracking that key pair's location except by the assumption that the driver's GetSSHKeyPath() function will always return the right path. IMO this isn't a good assumption, because if the currently-hard-coded-in-all-drivers value of "id_rsa" ever changes for a driver (or if a user wants to use their own key pair for some reason), existing machines will be broken.

Accurately returning the SSH key's location is a promise that the struct makes when it fulfills the interface.  If that method misbehaves, it is a bug.

Oh, and one last point - the generic driver already exposes its SSHKey field to inspect, so there's already a precedent.

That driver has to do that: the others don't.

@nathanleclaire - thanks :)

Hardcoded path values in the machine config are problematic in general. If we stored them in a fashion which was more akin to "SSHKeyPath": "${STORE_PATH}/machines/${MCN_NAME}" (just spitballing on this syntax)

Yeah - I like that idea. How about using templates and storing something like "SSHKeyPath": "{{StorePath}}/machines/{{MachineName}}"? Not sure if this would be any better than the sh-like syntax, but it's an idea ;)

Code / functionality duplication in the drivers. We're long overdue for consolidating common fields like SSH user, memory, etc. in general into an embedded base struct, and things like this will just make it harder to do.

Yes, absolutely :) I started messing around with this yesterday at https://github.com/hairyhenderson/machine/tree/default-driver-impl - I'll turn that into a PR at some point soon.

Accurately returning the SSH key's location is a promise that the struct makes when it fulfills the interface. If that method misbehaves, it is a bug.

Agreed, but my thinking was more that the current behaviour makes it difficult to ever change the location or allow users to specify a custom location. But de-duplicating the drivers will mitigate this.

From an outside point-of-view and without knowing the internals of docker-machine, I think that using templates is a very good idea, especially since Go seems to have good support for templates. That would open for future more complex (internal?) scenarios without bringing much more complexity to the code. As long as docker-machine inspect return the state at the time of the call and given the current configuration, it is all good for all external tools that wish to automate docker-machine in one way or another.

@nathanleclaire +1 for templating -- being more portable is a great thing

Just rebased this to merge in the changes from #1273 - makes this significantly simpler... But also breaks stuff ;) I'll get back to this... eventually...

@hairyhenderson is this still actual, or do you feel the latest master fixes the problem? (in light of https://github.com/docker/machine/issues/1207#issuecomment-118990751 )

@dmp42 - I'd still be interested in getting this merged. I addressed one of @nathanleclaire's concerns (about duplication) in #1273, and I think the other main concern (hard-coding paths) absolutely needs to be addressed (we can't have portable configs without addressing that). I don't think that needs to be a blocker of this PR though, since we have a whole pile of other hard-coded paths already. IMO one more won't kill us, and a solution needs to be generic enough to handle all the paths anyway, not just this one.

@hairyhenderson looking at some of the code here, it's something I'm already doing as part of generic cleanup.
I'll submit it soon and see you over there in a moment ;)

@hairyhenderson would you still want to this PR merged? If so, can you take a look at why the tests are failing? Thanks a lot!

@dgageot unfortunately we rolled back #2033 which was covering that as well.
Let's keep this open for the time being while I re-PR.

@hairyhenderson The PR @dmp42 is talking about is https://github.com/docker/machine/pull/2117

Ok, thanks. Once #2117 lands I'll rebase and see what's left.

Heh. So I rebased after #2117, and there's one piddly change left - really just a removal of an unreferenced function. It's no longer relevant at all to the original point of the PR. So I'm going to :skull: this.
There's probably other unreferenced functions that we could ferret out later as a clean-up PR ;)

Thanks @hairyhenderson !
More cleanup incoming indeed.


Identify Tor Browser

TB/FF differ in window and nav props in both desktop and Android

diff: https://jsoneditoronline.org/#left=local.mepoqa&right=cloud.2bcb76714a3f4e719af28522a6a5a37d

Android:
TB on the left

issue began @ d9eff24


Could you add a function for plotting a reverse y-axis like GIOTTO? mirror or mirrorImg is not enough. Maybe a Mirror_Y_axis function To facilitate drawing and bridge the gap between different softwares

The problem really is that behind the scene, Voyager's plotting functions use geom_sf, which doesn't work with scale_y_reverse. So mirror is the way to go, unless you encountered problems with that. In order to add an argument to reverse y in the plotting functions, I would need major changes to the plotting functions though it shouldn't be too hard.


Datepicker is generating TextInput contains an input of type text with both value and defaultValue

[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version

I am initializing the Datepicker to be empty, however, I am getting a warning on the console with: _TextInput contains an input of type text with both value and defaultValue props. Input elements must be either controlled or uncontrolled (specify either the value prop, or the defaultValue prop, but not both).
const [selectedDate, setselectedDate] = useState<Date | null>(null);
<Datepicker className="datepicker-buttons w-full" value={selectedDate} label=""></Datepicker>

Changing the label to =" " make the warning go away

I've got the same issue, is there any possible way to avoid that error occurency?
In my case it's appear only during first render.
Changing the label to =" " didn't help.
Context
Nextjs project running locally and testing on Chrome 131.0.6778.109.

@rluders


[Suggestion] Visualty indicate that a link it not what it looks like

Hi,
Sometimes I get e-mail (valid or SPAM) with a web link in it which does not link to where it looks like it would/should link. Can you follow? Let me explain:
In the email the link looks like http://blabla.example.com
But the actual HREF link is something like: http://cloudmedia.us11.list-manage2.example.com/track/click?u=dfg4g3ghh5h34h34h34h34h3h&id=safg3hhwef=sdggh34h3h
This is the kind of links I personally hate to click (because of tracking or just fake) and I'd rather copy/paste the URL I see. But sometimes I forget to check and fall for it...
Would it be possible for RainLoop to visually indicate somehow that the link in the email differs from the link text? I'm afraid that an in-line indication will mess too much with email itself, but perhaps a big warning banner above the email? :)

Maybe a little css decoration (like a little 1ex red box with an exclamation point, positioned at the top right of the link like a superscript)?


Remove "Song"

Companion to https://github.com/arduino/library-registry/pull/2386

Done here https://github.com/arduino/library-registry/pull/2386#issuecomment-1403965645