Added html headers for *.html endpoints

Sometime there is need to have simple html pages to render the out put of commands(e.g. with -sse option). Proposal here is have naming convention that if endpoint ends with *.html prefix send proper header. in this way it could be severed html files with something like this:  shell2http -output -sse /my_client.html "cat my_client.html"

Thank you for your request:)


Make skill and stat functionality during leveling optional through config

This pull request adds the possibility to disable skill, stat, reset, and key bindings functionality through config values.
This is done to have flexibility for someone who does not want to these functionalities enabled. E.g. knowing better what and howto allocate, having specific items which, set up the key bindings beforehand etc.
At least personally I've experienced sometimes bot messing up with key bindings and puts TP on F5 and armor on F4. It's easier to set everything myself once and forget about it, however make sure that these will not be reset again accidentally.

This sounds very good, honestly I would like to spend some time working on the leveling tool and have some ideas, maybe at some point if I have some time after bugfixing. I will take a look at the PR tomorrow, but feel free to join the discord https://discord.gg/RWuQ78P7


feature requests

I saw that you added a graphic that tells you the direction to the waypoint. It would also be ideal to mark the COG.
something like the number 3 picture.

add average wind direction gauge something similar as the opencpn gauge

B&G has something similar with average wind direction and average wind speed.

add gauge like this app with distance to start line. Sailgrib RS is the app. There are different apps but this is very simple.

Good ideas. Could you split this feature in two? One for wind widget COG and another for a new widget with average variations chart?


[Python] Error repeating df.to_parquet in pytest: "pyarrow.lib.ArrowKeyError: A type extension with name pandas.period already defined"

Describe the bug, including details regarding any error messages, version, and platform.

E   pyarrow.lib.ArrowKeyError: A type extension with name pandas.period already defined

pyarrow/error.pxi:91: ArrowKeyError
========================================================= short test summary info =========================================================
FAILED python/tests/test_minimal.py::test_pyarrow_issue_2 - pyarrow.lib.ArrowKeyError: A type extension with name pandas.period already defined

It seems to have something to do with how pytest orchestrates its tests. Here is my minimal example:
test_minimal.py
import pytest
import pandas as pd

pytest_plugins = ["pytester"]

def test_pyarrow_issue(testdir, tmp_path):
    path = str(tmp_path / "test.tar")
    df = pd.DataFrame()
    df.to_parquet(path)

def test_pyarrow_issue_2(testdir, tmp_path):
    path = str(tmp_path / "test_2.tar")
    df = pd.DataFrame()
    df.to_parquet(path)

Running pytest test_minimal.py then triggers the error.
Notably, the error does not occur if either test is run independently, and it does not occur if the testdir fixture is removed or replaced with some other fixture. So I guess it has something to do with whatever testdir is doing under the hood. Presumably to do with how pandas/pyarrow get imported.
In my real case I would really quite like to keep using the testdir fixture, though I can probably find a different way to do things. But nonetheless this behaviour seemed worth reporting. Not sure if it is a pyarrow issue though, or whether it is more of a pytest issue, or maybe even pandas.
Component(s)
Parquet, Python

@bjfar thanks for the report! This is a bit bizarre .. So when pandas' to_parquet gets called for the first time, pandas will call pyarrow.register_extension_type(..) to register its extension types. This is defined in a python submodule in pandas, so I would expect that normal python execution will ensure this code from importing the submodule is only run once.
But maybe that assumption is not true in all cases, or the pytest fixture meddle with the import mechanism? In any case, if we should protect this from happening, that's something that needs to be done on the pandas side. Would you want to report it there?

Even, I also face the same issue
I am just trying to read a huggging face dataset my-issues-dataset
import pandas as pd df = pd.read_parquet('hf://datasets/devopsmarc/my-issues-dataset/data/train-00000-of-00001-0695a20c4fb24663.parquet')
getting this error -> [pyarrow.lib.ArrowKeyError: A type extension with name pandas.period already defined]


When a listing doesn't return any resources show an explicit message

Currently when a listing (jobs or datasets) doesn't have any resources it shows an empty list but we might want to show a explicit message instead.

Should we display No resources found. instead of the table header?

We should specify the resource name (job or dataset)


notifications context processor query DB on every request

This context processor
https://github.com/django-oscar/django-oscar/blob/f9ff1588c1b4719d3cae3e1f9f2a8806aa3d0cb7/src/oscar/apps/customer/notifications/context_processors.py#L6-L12
query DB on every request even when num_unread_notifications is not used. So I think it might make sense to either make it callable or rework it as template tag.

num_unread_notifications is used in oscar/partials/nav_accounts.html which is included in layout.html, so by default it is used on every view apart from the dashboard.
If you've overriden the templates and don't use the variable, then you can avoid the cost by just not including this context processor in your TEMPLATES setting.


[Utility] extend FuncOp to FunctionOpInterface

FunctionOpInterface support tt.func and func.func

why would we ever have func.func there?

why would we ever have func.func there?

in our use case for intel(gemm with block ptr), we will keep the tt.make_tensor_ptr in the final tritongpu IR,
and then when convert to llvm, we convert tt.make_tensor_ptr to a memory descriptor.


Adapt to the ideascube packaging changes

I'm working on some changes in the ideascube packaging. Mostly adding to the package some stuff we're doing here.
It's not all done yet, I'm still working on it.
However, when that's done, we'll be able to simplify the ansible tasks to install ideascube.
I'm just opening this issue to remind myself it needs to be done.

The packaging changes are now in: https://github.com/ideascube/ideascube/pull/272
Once that's merged, we can start removing stuff from here, since the package already does them. :smile:

ideascube/ideascube#272 is now merged :)


add verify prod and refactor terraform check/deploy

Fixes #54
retry to fix https://github.com/octo-sts/app/actions/runs/9134061913/job/25118829336
also added the working-dir as env variable

@k4leung4 can you take a look here when you have some free cycle? thanks in advance


fixed category

Thank you again; I just realized that I put it in the wrong category; this should be more correct 🙏

Well spotted!


feat: Shrink

This PR adds a new ResizableSize configuration, labeled shrink.
This new size will "shrink" to fit its content during the initial layout, taking into consideration the min/max size values (if present).
The new layout logic flows as follows:

Calculate the sizes of all statically-sized children
Begin layout
Create a GlobalKey for each child
Layout children

If a child has a static size, use that size with a SizedBox wrapper
If a child has a "flex" size (shrink or expand), use an appropriate wrapper widget and allow Flutter to size it accordingly
In each scenario, supply the GlobalKey to the child's wrapper

After layout, use the GlobalKeys to check the final sizes of each child
Update the ResizableController with all child sizes

Functionality is in place and seems to work appropriately, but I still need to add some tests before this is ready.


Feature/ds endpoints sites villages

Description

Adding /sites endpoint to return clean (based on 08252020 status) site_assessment information.

Adding /villages endpoint to return clean (based on 08252020 status) gov. village and ID information.

Consolidating /raw files into this commit/pull request, to fit the same file structure, and allowing easier merging.

[ ] This is a bugfix.

[x] This is a new feature.

[x] This is part of a feature.

Organization

[x] Have you linked this pull request to a Trello card?

Review

[x] Have you added two reviewers to this pull request?
[ ] Is this a work in process?
[x] Is this ready to be reviewed?

 Setting up /sites and /villages endpoints to return clean site_assesement and gov. village name/IDs data.

Should be relatively straightforward to review. The .CSV datasets are based of the latest notebook. Please pay attention to raw.py, sites.py, villages.py in project/app/api
The URL to datasets will require modification after everything is merged on main branch.

I saw your post, your codes run pretty well. After review your codes, your codes are clear and tidy and no duplicated and unnecessary codes. Only add a little more comments maybe let readers read fast and easily.


Enable topology to fix e2e windows tests

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.7%) to 44.575%

Totals

Change from base Build<PHONE_NUMBER>:
1.7%

Covered Lines:
189

Relevant Lines:
424

💛  - Coveralls


docs: update notebook env dependencies

Notebook tests pass: https://github.com/langchain-ai/langchain/actions/runs/11939705036


Restrict invite, see pending and see team to owner

Hey,
maybe it would be good to have some configurations (maybe on a per team basis even) to restrict the invite, pending and see members methods to the owner only. Or specific members?
Maybe there could be a canInvite(), canSeeMemembers(), canSeePending() method, which by default just checks for the owner but could be customized with any logic (e.g. when using a permission system).
This idea is still a bit hazy, but if you think it is interesting I will put some more thought into it (or maybe you already have a very clear idea of it).

Hm. I think that this is more part of the implementation logic you would
need to provide. So when you allow in your application to invite others,
you would need to check against that anyways.
How do you think this would be beneficial for this package to simplify
things?
Lukas Oppermann<EMAIL_ADDRESS>schrieb am Fr., 26. Aug. 2016,
11:50 vorm.:

Hey,
maybe it would be good to have some configurations (maybe on a per team
basis even) to restrict the invite, pending and see members methods to the
owner only. Or specific members?
Maybe there could be a canInvite(), canSeeMemembers(), canSeePending()
method, which by default just checks for the owner but could be customized
with any logic (e.g. when using a permission system).
This idea is still a bit hazy, but if you think it is interesting I will
put some more thought into it (or maybe you already have a very clear idea
of it).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mpociot/teamwork/issues/50, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAxHTEOZE019pjLtIE6oLzcOYEQrIkFAks5qjrb8gaJpZM4Jt6xc
.

Well, firstly if the Teamwork Model would have this methods it would provide a default case.
Lets say there are configs like 'restrict_invite' => true, if set to true the canInvite($user) default implementation would check if the user who is currently trying to run the inviteToTeam() method is the owner of the team. I think this use case is very common, you see it on nearly every page, e.g. github itself lets only special people invite people to a team.
If I need different checks, e.g. every user with permission invite-to-team can invite people, I can just overwrite the check within the canInvite($user) method to check for the given permission myself. However, I do not have to implement the logic to throw an exception, or whatever, etc. if the canInvite($user) method returns false.
I hope you see how this can make it much easier.
I think a verification would be part of this package, while of course now showing something, etc. would be part of the logic.
I guess seeing pending & members is possible not something that needs to be restricted by the package itself, as it is solely a show method and does change stuff.
However Invite is similar to delete as in, it changes the state of the team, thus I think it should be controlled.


pubsub.run_in_thread : extra loop requested, for reuse purposes of the pubsub thread when switch to another redis server is needed

Hi,
We have a requirement to change running processes to another redis instance on another server on the fly (without restarting a process, and without introducing new threads). This happens within a redis pubsub event. After the event handler has ended, the event handler must be registered to the pubsub channel of the new instance.
We implemented this (works great), but it needed a small hotfix on redis-py. Below is the change (not using git atm -hg-, but I could supply a github pull request in a couple of days if requested).
Please change (client.py):
        pubsub = self.pubsub
        sleep_time = self.sleep_time
        while pubsub.subscribed:

to:
        pubsub = None
        while not self.pubsub is None and not pubsub is self.pubsub:
            pubsub = self.pubsub
            sleep_time = self.sleep_time
            while pubsub.subscribed:

This enables re-assigning the pubsub object to another one while reusing the same thread (and if desired: reuse the original event handler dictionary). The inner loop is restarted again if the self.pubsub member is set to another object during execution of the event handler.
Kind regards, TW

@tw-bert Why not make a PR with the changes and propose it that way?

In your proposed change, how does the inner loop exit? There's nothing in the code you posted that causes the existing pubsub object to become unsubscribed.
I don't see how this works if sleep_time=None unless you're calling unsubscribe() from somewhere else.
Given you're constructing a new pubsub object to substitute, why not just do something like:
class PubSubThreadManager(object):
    def __init__(self):
        self._thread = None

    def use_pubsub(self, pubsub):
        if self._thread is not None:
            self._thread.stop()
        self._thread = pubsub.run_in_thread()

Instantiate this in your code base as a singleton. At startup or whenever the Redis server changes simply construct a pubsub instance and feed it to the use_pubsub method.

Hi Andy, it works with sleep_time=None because the request comes from the outside, incoming in the pubsub socket. So you stay inside the loop, but disconnect all and reconnect another, and then sleep_time=None will have it's effect in the select() of the new socket.
I can't use your proposed PubSubThreadManager, because I have no control over the main thread (which isn't python -> embedded python interpreter). And if I would initiate yet another thread to control it, the old thread will never die on OS level. Even _thread.stop() does not do that for you. At least not on AIX. The result would be that each switch a thread would be added.

Note that the PubSubWorkerThread.stop simply unsubscribes from all channels and patterns. It doesn't actually forcibly stop the thread.
But I get that this solution won't work given that you're handling the reconnection in response to a message.
My issue with your proposal above is that it's just not very general purpose. The code doesn't do anything without the associated handler. I'm fine introducing new code, but let's make something others can actually use.

I agree that it has to be general purpose. The code I suggested makes it possible to change the pubsub object in an event handler. But I agree that my implementation is not intuitive, at least not without comment. Maybe add a method to the client, swap_pubsub() ?
I also looked into alternatives like inheriting from PubSubWorkerThread and have my own run_in_thread, but that way we deviate a lot from the standard redis-py implementation.


Korean is steal broken

i fetch from origin repo
and rebuild gradlew.bat but korean is steal broken like below link.
https://imgur.com/a/ZitxELS

https://drive.google.com/open?id=1zZoPLmatSqqGl3_hhSsXy2rUJkpuN8Rs

In the comment to the issue 'Attach files by dragging & dropping...'.
But before, could you please update and rebuild it and try again - I pushed another fix, that specifies the encoding.

now korean is not broken it fixed


How to set app name when build apk and aab

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
build apk with this command
flet build --project "ABC Def" --product abcdef --org abcd.feg --build-number 1 --build-version 1.0.0 --template-dir C:/Users/abcd/flet-build-template-main apk
install apk and the app name is abc_def
the name should be ABC Def
Code sample
flet build --project "ABC Def" --product abcdef --org abcd.feg --build-number 1 --build-version 1.0.0 --template-dir C:/Users/abcd/flet-build-template-main apk
To reproduce

Build apk
install apk
the app name wrong

Expected behavior
No response
Screenshots / Videos

Captures
[Upload media here]

Operating System
Windows
Operating system details
windows 11
Flet version
0.24.1
Regression
No, it isn't
Suggestions
No response
Logs
Logs
[Paste your logs here]

Additional details
No response

Why close?

Has found solution
change the android: label can change the app name

Right, but how did you do that with flet build, copied template?

yes, I download this
https://github.com/flet-dev/flet-build-template

OK, it should be possible to fix via flet build though.

Wait a second, I see it's already using product-name for filling label value: https://github.com/flet-dev/flet-build-template/blob/0.24.1/{{cookiecutter.out_dir}}/android/app/src/main/AndroidManifest.xml#L24
which is correct. --product-name is "project display name that is shown in window titles and about app dialogs".
You command should be changed to:
flet build --project abcdef --product"ABC Def"

maybe my template is old version


JVM crash when websocket is closed from client

I'm using vert.x 3.2.0 with Netty 4.0.33.Final(tried 4.0.34.Final as well).
Whenever I close browser window, which has active websocket connection to server, JVM crashes.
These are last lines from application log:
2016-02-04 20:33:41.151 [vert.x-eventloop-thread-1] DEBUG io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=8 2016-02-04 20:33:41.153 [vert.x-eventloop-thread-1] DEBUG io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder - Decoding WebSocket Frame length=2
Attached hs_err_pid.log file
hs_err_pid26167.txt
$uname -a
Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux
java -version
java version "1.8.0" Java(TM) SE Runtime Environment (build 1.8.0-b132) Java HotSpot(TM) Client VM (build 25.0-b70, mixed mode)
I had no such issues running on the same platform using vertx 2.1.5 with Netty 4.0.21.Final

@tmihalcin can you share the app that allows to reproduce this ?

Actually I think I see where the problem is... Let me fix it

If you still need sample app, just let me know

No all should be good. I'm right that you can only reproduce it on the PI?

Am 05.02.2016 um 07:16 schrieb tmihalcin<EMAIL_ADDRESS>If you still need sample app, just let me know
—
Reply to this email directly or view it on GitHub.

@tmihalcin also can you share which raspberrypi and which linux you are using ? Would be interested to  know.

@tmihalcin this should fix it: https://github.com/netty/netty/pull/4845

Yes you're right. No issues on Windows machine.
I'm using RPI2 with Raspbian.
Thank you for quick fix.

@normanmaurer I have patched netty-buffer with your fix and I confirm that it works.
Thank you.


Add field created when create function via PUT

Coverage increased (+0.04%) to 92.084% when pulling 0d3a9232b1537b92e14db62cf9ff7a706f0e7528 on MayconDionisio:put-created into e1585efce39533c54fb55128fc44b9a9d0d77ba0 on backstage:master.

Great! Can you just add some test for this specific case.

Yes! I'll do this

Coverage increased (+0.04%) to 92.084% when pulling 97bb94b299919d6e9f1adb1f21dc5f9e7ca3c474 on MayconDionisio:put-created into e1585efce39533c54fb55128fc44b9a9d0d77ba0 on backstage:master.

Looks awesome for me!

Coverage increased (+0.04%) to 92.084% when pulling 54febfee2f69ab5ba0a26eb34f7e8d5fcbdbdcee on MayconDionisio:put-created into e1585efce39533c54fb55128fc44b9a9d0d77ba0 on backstage:master.


Remove the use_std feature

It has been deprecated for a while and it's good time to remove.

:pushpin: Commit 4364c3b56fa7d1ebecf4cce897b6fe9541eb1d7f has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 4364c3b56fa7d1ebecf4cce897b6fe9541eb1d7f with merge 1abc2e47107e03eab1757b8dcb24b1095f6aeeb9...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 1abc2e47107e03eab1757b8dcb24b1095f6aeeb9 to main...


Split the contributing page

Is your feature request related to a problem? Please describe.
I think that this single contributing page in its current form may be overwhelming for new users; it certainly was for me not so many months ago 😅
Describe the solution you'd like
After reading some of the contributing pages on other projects (through the discussion in https://github.com/pvlib/pvlib-python/issues/2202), I feel like our contributing page would benefit from being broken up into several pages.
These pages would still all be under the same "Contributing" section, but they could be navigated through using the sidebar (like the user guide?)
In this way, we could keep the really basic basics on one (the first) page, then move other details such as code style, testing, virtual environments, etc. onto separate pages rather than just separate sections on the same page.
I think having the new pages split somewhere along the lines of the current sections would be a good starting point. I am interested to hear if anyone has any other suggestions for a structure, or for any entirely new sections.
Additional context
There are ongoing discussions on standardising the reference style (#2202) and standardising the typesetting of units (#2205). I think that the new (split) contributing section could include a style guide page with all of this new information on documentation style, as well as existing style information related to code style that we already have.
I am +1 for @AdamRJensen's suggestion to include a template function and I think the aforementioned style guide section would be a good place for this.
One potential new section (besides the style guide) could be a "Contact" page (later discussion in #2200) where readers are advised to create a new issue if they want to reach out. I am thinking a dedicated new page rather than a sentence in another page might be better because a couple of screenshots showing how to create a github issue might be helpful for new users.
If the community thinks this idea for restructuring would be useful, I'd be happy to have a crack at it.

Is your feature request related to a problem? Please describe. I think that this single contributing page in its current form may be overwhelming for new users; it certainly was for me not so many months ago 😅
Describe the solution you'd like After reading some of the contributing pages on other projects (through the discussion in #2202), I feel like our contributing page would benefit from being broken up into several pages.
These pages would still all be under the same "Contributing" section, but they could be navigated through using the sidebar (like the user guide?)
In this way, we could keep the really basic basics on one (the first) page, then move other details such as code style, testing, virtual environments, etc. onto separate pages rather than just separate sections on the same page.
I think having the new pages split somewhere along the lines of the current sections would be a good starting point. I am interested to hear if anyone has any other suggestions for a structure, or for any entirely new sections.
Additional context There are ongoing discussions on standardising the reference style (#2202) and standardising the typesetting of units (#2205). I think that the new (split) contributing section could include a style guide page with all of this new information on documentation style, as well as existing style information related to code style that we already have.
I am +1 for @AdamRJensen's suggestion to include a template function and I think the aforementioned style guide section would be a good place for this.
One potential new section (besides the style guide) could be a "Contact" page (later discussion in #2200) where readers are advised to create a new issue if they want to reach out. I am thinking a dedicated new page rather than a sentence in another page might be better because a couple of screenshots showing how to create a github issue could be included to help new users.
If the community thinks this idea for restructuring would be useful, I'd be happy to have a crack at it.

+1 to splitting it up.  I would keep the "This documentation" and "Code of Conduct" sections on the first page instead of splitting them into their own pages.

Mind if I work on this? I want to propose more changes to the contribution guidelines, thou I will keep that in a separate PR unless you tell me otherwise.

@echedey-ls ah I have made a start locally already, just not opened the PR(s) on GitHub yet.
To speed up the process (possibly make reviews easier too) I could keep the first PR focused on splitting up the page, then if you have new suggestions for the contributing guidelines you can start revising what's already there without a problem. I can move the creation of new section(s)/text, such as documentation style guide for references that I proposed, into a separate PR after the splitting.
How does that sound?

Sounds reasonable and wonderful. I suppose there are other views on doing so many changes in one PR, but I prefer to start with the brainstorm early (will be moving that to #2067 and #2081 once I gather all my ideas).

a "Contact" page (later discussion in #2200) where readers are advised to create a new issue if they want to reach out.

Would this be best placed as:
a) a new page within the contributing section
b) a new page within some other section
c) a new section (new tab at the top of https://pvlib-python.readthedocs.io/en/stable/)
d) a line or two on some other page within the contributing (or other) section
e) not existing
What I think this addition would include is couple of lines two encouraging people to get in touch if they have any questions, and links to the Github repo (or direct to issues page) and the Google page.  Besides the obvious benefit of inviting engagement, it could also be a way to nudge non-Github users (potential contributors) onto Github 👀

a "Contact" page (later discussion in #2200) where readers are advised to create a new issue if they want to reach out.

Would this be best placed as: a) a new sub-page within the contributing page group b) a new sub-page within some other page group c) a new page group (new tab at the top of https://pvlib-python.readthedocs.io/en/stable/) d) a line or two on some other sub-page within the contributing (or other) page group e) not existing
What I think this addition would include is couple of lines two encouraging people to get in touch if they have any questions, and links to the Github repo (or direct to issues page) and the Google page. Besides the obvious benefit of inviting engagement, it could also be a way to nudge non-Github users (potential contributors) onto Github 👀
A new tab at the top appeals to me but it seems like a big deal for very little (although important) content so I am 60/40 leaning in that direction. I think my next preference would be a subpage within the (new) contributing page group. I am interested to hear what others think.

This may be resolved by #2224, so perhaps I should close this issue as completed by #2219?


Adds a high level API for pose-relative landmarks

This is an compiling, but non-functional API proposal for #244.

/cc @mofef, @jihoonl This is our suggestion for a public API for pose-relative constraints. This is just the API and no implementation. Do you think you can take this from here or do you require some pointers for the implementation?
Also, this is only tracking -> landmark. Landmark -> landmark would need to go into the SPA interface, but at our meeting it seemed sensible to start with this and see if you can model your problem in this frame of reference. Should this be infeasible, we can revisit the landmark -> landmark constraints again. Agreed?
/cc @macmason Has TRI an opinion on this?

LGTM.

Thanks! To us this looks sufficient for now. I didn't find time to think about the detailed implementation yet, but it doesn't seam to be a very complex task. I will get back to you if I run into troubles.

Looks good to me too.

This has bit rotted quite a bit and there is some agreement that this design is not sufficient. Closing for now as we have no immediate plans of implementing this.
If somebody wants to see this happen, please ping here or on the mailinglist again and we can start putting together a better design.

I'm very interested in tracking external landmarks (say, AR tags) to enhance submap construction but also for loop-closure purposes and think this would be of use to others, as well.
I'm aware of the work on fixed-frame constraints (e.g. GPS, VICON), however they do not help in tracking (initially unknown) identificable landmarks.
Maybe @SirVer could briefly explain me his ideas on how to implement it - or provide pointers.
I'm happy to contribute.

Depending on what you want to achieve in detail, you might be good to go. Some tracking of map-fixed constraints has recently be added by @zjwoody. See the commits here: https://github.com/googlecartographer/cartographer/commits?author=zjwoody

FYI @pifon2a is looking into implementing this already.

Thanks for the pointers!


Proposal for Pulsar Backend versioning system

Since lately there have been lots of discussions on how to resolve our issues regarding the management of the versions of packages, I make a proposal which I think is the best compromise about

being permissive on publishers
having a quite easier management of versions
allowing to implement additional release channels in the future.

A part of the following post is meant to be copied and pasted in a document as guidelines for publishers.
TLDR: Almost the same system as now plus the created timestamp and a few changes which require a refactoring on database queries.
Main guidelines

Pulsar package system requires the versions of the published packages to adhere to MAJOR.MINOR.PATCH format (which from now on we call "main tag") of the semver specification.
Pulsar backend performs a control ensuring MAJOR.MINOR.PATCH format is respected prior to the publication, therefore any version not following the above point is considered bad and it's rejected.
Any version can optionally have extension labels in the format MAJOR.MINOR.PATCH-extension to support alpha/beta/pre-release alternatives.
Pulsar backend is not enforcing publishers to respect the rules of the semver specification regarding the extension labels and no controls are performed on them because it's too hard for the dev team to follow those rules. The publisher is responsible to release a version with the correct extension, if present.

Publishing guidelines

A publisher can use the existing API to publish versions in the default stable release channel.
In the future additional endpoints will be deployed to publish also in optional supplementary channels (alpha/beta/pre-release). Guidelines for this will be explained by the dev team when everything is ready.
Considered all the versions of a single package, their tags MUST be UNIQUE. This means all versions of a package have different tags and if a publisher deletes a version, they can't publish a new one with the same deleted tag.
Considered the same release channel, two or more versions can have the same main tag MAJOR.MINOR.PATCH as long as they differs with the extensions. I.e., publishing 1.0.0, 1.0.0-1 and 1.0.0-2 is possible.

Determining the latest release

Pulsar backend has its own way to determine the latest release of a specific channel which we recommend the publisher to understand in order to avoid misunderstandings.
Taken two versions of the same channel of the same package, the highest is the one that comes first in the natural descending order of the main tag. I.e., 0.10.0 is higher than 0.9.0.
The dev team strongly discourage the publication of two or more versions with the same main tag. But that is not forbidden. Anyway we recommend to read the following point.
Taken two versions of the same channel of the same package with the same main tags, the highest is the one that has been published more recently on the backend. I.e., 0.1.2-1 published today and 0.1.2 published tomorrow means that 0.1.2 will be considered higher than 0.1.2-1. Publishers have to know that and, taken into account that the publication of multiple versions with the same main tag is still discouraged, the dev team won't accept any complaining on this behavior.

How to migrate to the new versioning system
versions table refactoring

[x] Unique constraint in versions table should be rolled back to (package,semver) rather than (package,semver_vx, ...). This is because we will support different extensions for the same main tag, so we need to ensure all tags are different for a single package.
[x] Package handlers functions that are considering semver array rather semver plain string should be rolled back too.
[x] Generated columns semver_vx are kept as they are since we need them to sort the main tags.
[x] Implement created and updated columns for versions the same way they were added to the packages table.
[x] While sorting the versions in descending mode, the created timestamp will be considered so that two versions with the same main tag can be sorted and the latest released is the highest of them.

Drop versions.status column

[ ] Do not take into account the status column of the versions table. This column will be dropped along with its enum type. The reason is quite simple: we sort the versions on the database, so we don't need to signal the latest. It's also misleading when channels will be deployed because there will by multiple latest, one for each channel. published and deteled status are redundant and will be replaced by the following point. Optionally a new status column could be used in the future to signal the state of the version (no issues, bugged, unsecure, etc...)
[ ] Implement a new bool column deleted in versions table. Its meaning is self explanatory: true if the version is deleted. Initialize it setting to true if status is deleted; false is its default.
[ ] Rewrite all queries that uses the versions.status column so that it can be definitely dropped. We know how to sort and get the latest version properly.

Drop redundant package metadata

[ ] Drop JSONB data in packages table. At first sight this might be a disruptive change, but it's not. packages.data is redundant data because it's just the package of the latest version, which we already have in versions table. Besides with the introduction of the channels, it's misleading having the package of the latest versions in packages table (which channel does it belong?). If we want it, we can join the versions table and we can do it for any channel.

Manage the duplicated versions for already published packages

[ ] We have resolved the issue of duplicated versions looking at the created timestamp, there's still a problem for the already published versions. That's because when we deploy the created column in the versions table, it is initialized with the timestamp of the creation of the column, so it won't contain the effective time of the publication of the version. But we can workaround this issue adding an interval to the versions that are marked as latest before dropping the status column, so those versions keep resulting as the latest in case there are other duplicate main tags.

If you have some doubts or thoughts, feel free to point them out.

@Digitalone1 This is beautiful!
I sincerely appreciate the work and thought that went into this. And for this solution I am 100% on board.
This looks fantastic, and while keeping things sane, allows us the most flexibility now and in the future.
Everything here looks awesome, and would be happy to help out wherever possible to get this working properly.

As for your last point about already published versions. Once we add the tag to the DB, I'd be more than happy to investigate manually into the published versions to find their actual publication date based on GitHub Tag creation date. I believe it was about 60 items that need this care, so ideally wouldn't take to much time.

List of changes to make on the database. @confused-Techie mark this steps when you port the new db state on production.

[ ] Add new created and updated column to versions

ALTER TABLE versions ADD COLUMN created TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT CURRENT_TIMESTAMP;
ALTER TABLE versions ADD COLUMN updated TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT CURRENT_TIMESTAMP;

As for your last point about already published versions. Once we add the tag to the DB, I'd be more than happy to investigate manually into the published versions to find their actual publication date based on GitHub Tag creation date. I believe it was about 60 items that need this care, so ideally wouldn't take to much time.

It would be awesome to have the real publication date of every version, also those imported by atom, but I don't think this is possible.
Anyway I'd like to add an index on semver_vx generated columns and created timestamps. This is not mandatory, but can speed up the sorting stages. But at the moment this won't work because equal semver_vx triples will have the same created timestamps (default at column creation).
If we want this, you will have to change manually the timestamps (even adding 1 only ms is enough). This would also help to retrieve the correct latest version for ones that have the same main tag.
If there are too many, you can deleted the duplicated non-latest and sort only the latests.

I can certainly try to update the duplicated non-latest versions.
If it does become too much I'll look at either scripting it or (as long as you don't delete the branch) your previous script to do so.
But first I'll add the DB changes tomorrow so we can begin that step.
And ideally we could script up a one time task that will look through each package, contact the GitHub API and insert proper creation dates into everything. But that can always come later.

#65 and #66 covered all steps except the last two which I'd like to manage when the changes applied to the database are pretty stable. So for now let's see how this changes behave on the database (I hope good, at least from the tests I don't see nothing wrong).

So, after the merge of #62, #65 and #66, an issue came out.
The issue

The response package sent out by the backend does not respect the format of the package short/full.

The problem

It's not strictly related to how the merged changes were designed, but by the fact that when we imported the atom database, the version.metadata contained only the packageJSON, while the packages.data contains also the repository object and the readme.
the latest changes are stuffing repository object and readme into versions.meta, but for already stored records, those data are missing, so they have to be imported from packages.data into versions.meta in order to deprecate packages.data.

New versions table design
After a talk on Discord, we agreed to add new columns to make it easy to construct the response objects sent out by the backend:

a new readme TEXT column containing the readme of the related version
a new git_type column of type provider ENUM, which at the moment will contain only git, then we will add others when supported

Besides, the meta JSONB column will contain only the packageJSON, i.e. the object retrieved by vcs provider.packageJSON with tarball info appended to it.

Apply new column to versions table

[ ] add readme

ALTER TABLE versions ADD COLUMN readme TEXT NOT NULL DEFAULT '';

[ ] add repo_url

ALTER TABLE versions ADD COLUMN repo_url TEXT NOT NULL DEFAULT '';


Only try to extract images if the image uploader is enabled

Pull request checklist:

[ ] CHANGELOG.md was updated, if applicable

Description
Tries to be a bit smarter for when to just paste regular old text instead of an image
Needs some thorough testing with mixed clipboards
Fixes #4245

tested on macOS Ventura 13.1
When disabled. Pastes Excel style text

When enabled fails with

Going to merge this in as is - there's some more logic we could do to ensure text always pastes but that would fit better as a feature enhancement than a bug fix

Can confirm this works on sway v1.7 as described in the OP!


Plugin error after flutter upgrade

Steps to Reproduce

I have the same issue as described in #46807
I did a flutter upgrade and are now unable to build my project.

Unable to find a matching configuration of project :url_launcher_macos
Unable to find a matching configuration of project :path_provider_macos
Unable to find a matching configuration of project :shared_preferences_macos
Unable to find a matching configuration of project :shared_preferences_web

url_launcher: 5.4.10
shared_preferences: ^0.5.7+3

Logs

AILURE: Build failed with an exception.
[   +1 ms] * What went wrong:
[        ] Could not determine the dependencies of task ':app:lintVitalProductionRelease'.
[        ] > Could not resolve all artifacts for configuration ':app:developmentDebugRuntimeClasspath'.
[        ]    > Could not resolve project :url_launcher_macos.
[        ]      Required by:
[        ]          project :app > project :url_launcher
[        ]       > Unable to find a matching configuration of project :url_launcher_macos:
[        ]           - None of the consumable configurations have attributes.
[        ]    > Could not resolve project :path_provider_macos.
[        ]      Required by:
[        ]          project :app > project :path_provider
[        ]       > Unable to find a matching configuration of project :path_provider_macos:
[        ]           - None of the consumable configurations have attributes.
[        ]    > Could not resolve project :shared_preferences_macos.
[        ]      Required by:
[        ]          project :app > project :shared_preferences
[        ]       > Unable to find a matching configuration of project :shared_preferences_macos:
[        ]           - None of the consumable configurations have attributes.
[        ]    > Could not resolve project :shared_preferences_web.
[        ]      Required by:
[        ]          project :app > project :shared_preferences
[        ]       > Unable to find a matching configuration of project :shared_preferences_web:
[        ]           - None of the consumable configurations have attributes.

flutter analyze:
No issues found! (ran in 7.0s)

flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Mac OS X 10.15.4 19E287, locale nb-NO)
• Flutter version 1.12.13+hotfix.8 at /Applications/flutter
• Framework revision 0b8abb4724 (4 months ago), 2020-02-11 11:44:36 -0800
• Engine revision e1e6ced81d
• Dart version 2.7.0
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0-rc2)
• Android SDK at /Users/borgelotre/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 30.0.0-rc2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.4.1, Build version 11E503a
• CocoaPods version 1.9.0
[✓] Android Studio (version 3.6)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 45.1.1
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
[✓] IntelliJ IDEA Ultimate Edition (version 2018.1.8)
• IntelliJ at /Applications/IntelliJ IDEA.app
• Flutter plugin version 31.3.1
• Dart plugin version 181.5656
[✓] VS Code (version 1.41.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.8.0

Hi. @borgelo
Looks like you're using 4 months old stable channel
Please upgrade to latest Channel stable, v1.17.1 and try agaiin
If the problem persist after upgrade,  can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Upgrading to v1.17.1 fixed it. Thank  you!


fix: not play animation when first entry

Summary
Don't call the startViewTransition when transforming between the same display name (from route path) component.
In the original issue(#123), @chenjiahan reported a behavior where there are two animations when jumping to a page with a hash. The reasons for this happening are:

The page jumps within the markdown do not use , but , which means the browser will reload when someone clicks on the link.
The view transition animation is played even when jumping within the same page (same route path).

Fixing the second issue is quite easy. However, it becomes challenging when trying to fix the first one.
I was working on the navigation between pages with a hash, for example, from guide/start to config/repress#nav. I needed some time to dispatch an event so that the sideEffect.ts would know that the DOM is attached to the browser. Otherwise, the scroll position and animation would be incorrect. To find the logic that handles this event, you can search for RspressReloadContent in this codebase. I decided not to include the logic here because I wanted the handling of scroll and position to be in one place to avoid confusion.
Details

[x] Not paly animation when first entry.
[x] Link component within the same site just should use push state rather than href.

Related Issue
#123
Checklist

[x] I have added changeset via pnpm run change.
[x] I have updated the documentation. // There is no need to update the documentation.
[x] I have added tests to cover my changes.

@sanyuan0704 I need your help on this.

@sanyuan0704 I need your help on this. Would you mind reviewing the change in packages/core/src/theme-default/logic/sideEffects.ts

ok

@chenjiahan Would you mind checking this? Would love to know your opinion!

@sanyuan0704 I need your help on this. Would you mind reviewing the change in packages/core/src/theme-default/logic/sideEffects.ts

ok

I added more context on the top

The transition effects between pages are now very smooth. 😄
However, when I click on an anchor within a page, the anchor does not seem to work. Here is a case:

open https://deploy-preview-125--aquamarine-blini-95325f.netlify.app/guide/advanced/custom-theme.html
click "Redevelop a custom theme"

https://github.com/web-infra-dev/rspress/assets/7237365/eaaf0266-4e4d-49ae-9f23-09b2c935cc72

@chenjiahan Now visit https://deploy-preview-125--aquamarine-blini-95325f.netlify.app/guide/advanced/custom-theme and the hash link effect is normal

LGTM👍🏻


Fix exploit

do you mean you can pickup anything?

do you mean you can pickup anything?

Yep. You can just set any entity. This exploit is gaining popularity on RP servers.

I have limited the distance and are checking that you are in the same PVS. You can use the hooks to limit it further.

Oh sorry I thought this was an issue. I checked the code and you should also add PVS and distance checking in some similar way as I did here https://github.com/Metastruct/vrmod-addon/blob/79978bef137c162e25d1971cfaaf3f9cc1d90376/lua/vrmod/vrmod_pickup.lua#L219


Use @phpstan-ignore instead of ignoring entire line if possible

Closes #86.

Awesome! I'll give it a test soon (including the pro part) and if all is well we can merge it afterwards.

Awesome, it works! Including the pro part. If you remove the TODO we can merge it :)

Done!


How do we select/deselect the items programmatically?

I have this multiple choice Choices (v9.0.1) instance that I have no control of, it's initiated by a WP form builder plugin and we're adding extra functionalities to it. We've developed a custom selector element to hide the Choices element itself so we'll only use it in the background.
I'd like to be able to select and deselect the available options programmatically. So let's say my custom selector element has a data attribute called "data-value" with the value "option-x" and when I click on it, my function will find the Choices item with the value "option-x" and click on it or call the proper method to select or deselect it.
On Choices v9.0.1, triggering the 'mousedown' event on the Choices item does the job but it doesn't work on the newer versions of the library. setChoicesByValue() method doesn't seem to be doing anything as well.
And for some reason, most of the methods I've tried on the console don't seem to be working (see screenshot below) is it because I'm trying to init an already initiated instance, or what I am doing wrong here? Any help is much appreciated, thank you.
Screenshots

Can you provide a simplified jsFiddle or code examples?
There's no reason that setChoicesByValue should not be doing what you're looking for (I assume you're using something like removeActiveItemsByValue(value) when an option is deselected as well).

is it because I'm trying to init an already initiated instance

Yes, this is why, you need to access the original Choices instance, or in your debugging, initialise it yourself in the console before the WP plugin does it.

Can you provide a simplified jsFiddle or code examples?

Thanks for the reply Matt. I was just setting up a jsFiddle for you and yeah you're right, the problem is that I'm trying to assign it to a new variable that's why it isn't working.
Like I said, modifying the original instance isn't an option so do you think destroying and creating a new instance with the same values would be an option?

For those who are having the same issue, that's how I've had fixed it.
1 - Found the JS file which the plugin dev creates the instance, copied the instance options and found what their selector was, in my case it was a class called "ff_has_multi_select"
2 - Identified the handle of the JS file and dequeued it inside the get_footer action and enqueued my own JS file in between it so I can remove the selector of my element and initiate it myself before the plugin does, see below.
`add_action('get_footer', function(){
wp_dequeue_script('fluent-form-submission');
wp_enqueue_script('xc-fluent-form-custom-functions');
wp_enqueue_script('fluent-form-submission');

}, PHP_INT_MAX);`
3 - Initiated the instance in my JS file with the same options I've copied from the plugin's own initiator.
I know this only applies to WP but you can try that destroy and re-init idea I've mentioned above, good luck.


Is it necessary to add an enabled signal for outputUTXO to support the situation where there is only one output UTXO?

https://github.com/hyperledger-labs/zeto/blob/8547ca56f8e8d0a9a8bd1230825e39aa840b4e19/zkp/circuits/anon_enc_nullifier.circom#L44

Thanks @yushihang for the question. I assume you were referring to the enabled array corresponding to the elements in the input commitments array (since that controls whether the merkle proofs for the input commitments should be checked inside the circuit or not).
The circuit itself always needs to be parameterized with the size of the inputs, because a ZKP circuit must always result in the same amount of computation regardless of the different combination of input values. This means we have a dilemma between efficiency of the circuits vs. complexity of the circuit maintenance. We could have different circuits for the different combinations of input sizes:

circuit #1: 1 input, 1 output
circuit #2: 2 input, 1 output
circuit #3: 1 input, 2 output
circuit #4: 2 input, 2 output
...

But this makes code maintenance much harder. So instead today we have a single circuit with 2 inputs and 2 outputs that supports the different combinations. This means the enabled array will always be of size 2, as are the arrays for input commitments and output commitments.

@jimthematrix  Thank you very much for your response.
I understand that maintaining multiple circuits as listed below will increase complexity:

Circuit 1: 1 input, 1 output
Circuit 2: 2 inputs, 1 output
Circuit 3: 1 input, 2 outputs
Circuit 4: 2 inputs, 2 outputs

Since the current circuits provide an enabled signal for the nullifier of the input, my understanding is that we could use the same circuit to achieve:

Circuit 3: 1 input, 2 outputs
Circuit 4: 2 inputs, 2 outputs

However, in some cases, we also have the need for the following situations:
Circuit 1: 1 input, 1 output
Circuit 2: 2 inputs, 1 output
For example, Alice uses two UTXOs/nullifiers with both value of 1 as inputs, and then generates a UTXO with a value of 2 to transfer to Bob.
In this case, because two output UTXOs are required in the circuit, I have to generate a UTXO with a value of 0 as the second output UTXO to send back to Alice herself when writing test cases. （I'm not sure if there are other methods that could better achieve this requirement.）
This might increase the complexity when verifying the ZKP in the contract and consume more gas.
So I was wondering if we could also introduce an enabled signal for the output UTXO. This way, by combining the enabled signals for the inputs and outputs, we could implement the following four scenarios while minimizing gas consumption:

Circuit 1: 1 input, 1 output
Circuit 2: 2 inputs, 1 output
Circuit 3: 1 input, 2 outputs
Circuit 4: 2 inputs, 2 outputs

I’m not sure if my understanding of zeto is correct. If there are any errors, please help me correct them. Thank you very much!


New update

I kept only the new component and Tools.cs
In the new update Grasshopper must updated to V 7.32.23215.19001
Net Framework 4.8.1
System.Windows.Forms
1- The new component have 3 inputs: Mesh from Deconstruct file
2- Name from the file to be used as prefix
using System.IO; string fileName = Path.GetFileNameWithoutExtension(fullPath); Name = fileName;
Maybe you can add an output in Read File or Deconstruct file to show the name of the bim file.
3- Bake
4- Right click menu to enable or disable Create layers (false by default)
5- The baking is slow with large files: tested with BeamBridgeExample.bim

The icon used:

Cool, I will check it out, but please revert deleted files, just the way they are in the master branch, because right now we have 62 changes:

We should have something like 5 changes only (like last time :))
When you remove files on your branch I also get a pull request that also tell me to remove this files :)
I know it might be annoying, so let me know if you don't want to do that, I'll try to do it myself somehow, maybe by copy-paste :)

I prefer you copy/ paste the files :)

Ok, will let you know when I will find some time for testing :)

This is the full project
https://www.dropbox.com/scl/fi/ths0elimr78mpn2bqt7uy/dotbimGH.zip?rlkey=z5qtqvhevsnxp3612iwdpnkq5&dl=0

Hey @seghier, I'm playing around with it already. My thoughts:

Because of the .net framework + GH nuget update I'll have to wait to merge it, till new version of plugin (2.0.0) as it won't work for GH6 anymore (still lot's of people stuck with RH6).
Personally I prefer version without layer baking much more :)
Personally I'd build this component similiar to "Bake File From Path" with Path and Bake input only to make it more consistent :)

Thank you once again for contribution :)

Hi @paireks
Thanks, creating layers is optional , the purpose of the component is to create materials for rendering.

3. Personally I'd build this component similiar to "Bake File From Path"

I didn't do that because the conversion to mesh take some time, that's why i used the output meshes from Deconstruct file.


re-add query.sql for movies example

Looks like .gitignore prevented query.sql from ever getting added, as it doesn't show up with
git log -- examples/movies/query.sql

This re-adds it with git add -f, but maybe there's something more to do (remove *.sql from .gitignore?)
Is it worth adding tests to actually try running the examples?

+1 users following the tutorial doc are hitting this problem.
I support the idea of running the kapsels as part of testing, but propose that be in a separate PR.

@bollwyvl, @havocp Are we ok to merge this? This is biting people who try to run the walkthrough.

May want to go ahead and fix .gitignore or we're asking for trouble (will we ignore this file's changes if someone changes it?). There's a way to un-ignore only this particular .sql file I believe, check out the git docs... or if we have no other sql files, remove *.sql seems ok ...

Fixed up gitignore! Will merge if/when tests pass!

👍

Ha, can't merge. @havocp, anything else you need to see here?

lgtm!

@havocp, I think you're the only one with write perms here, can you click the big green button for us?

Oops, didn't even notice which repo this was on :-)


[FLINK-4925] [metrics] Integrate meters into IOMetricGroups

This PR introduces Meters into the existing *IOMetricGroups, providing rates for the number of incoming/outgoing records/bytes.

+1 to merge.


Gurobi package name changed from gurobi to com.gurobi.gurobi in new version and cause package not found error in COMETS

I found when using COMETS with gurobi 11.0.2, there is a error cause by Gurobi.
The original error in cometspy is as follows:
RuntimeError: COMETS simulation did not complete:JAVA could not find gurobi.
try the following:
>>> import os
>>> os.environ['GUROBI_COMETS_HOME']
if there is nothing there try setting that variable
to the location of gurobi.jar, for example:
>>> os.environ['GUROBI_COMETS_HOME'] = '/opt/gurobi900/inux64'

After investigation, I identified it is a java class definition not found error raised by COMETS.
Exception in thread "main" java.lang.NoClassDefFoundError: gurobi/GRBException
        at edu.bu.segrelab.comets.fba.FBAModel.(FBAModel.java:224)
        at edu.bu.segrelab.comets.fba.FBAModel.(FBAModel.java:287)
        at edu.bu.segrelab.comets.fba.FBAModel.loadModelFromFile(FBAModel.java:2648)
        at edu.bu.segrelab.comets.fba.FBACometsLoader.loadModelFromFile(FBACometsLoader.java:2918)
        at edu.bu.segrelab.comets.fba.FBACometsLoader.parseModelFileLine(FBACometsLoader.java:1168)
        at edu.bu.segrelab.comets.fba.FBACometsLoader.loadLayoutFile(FBACometsLoader.java:316)
        at edu.bu.segrelab.comets.Comets.loadLayoutFile(Comets.java:1657)
        at edu.bu.segrelab.comets.Comets.runScript(Comets.java:541)
        at edu.bu.segrelab.comets.Comets.(Comets.java:233)
        at edu.bu.segrelab.comets.Comets.main(Comets.java:2159)

In of source of COMETS, the format used to import is no longer work in new version of gurobi.
import gurobi.GRBConstr;
import gurobi.GRBEnv;
import gurobi.GRBException;
import gurobi.GRBLinExpr;
import gurobi.GRBModel;
import gurobi.GRBVar;
import gurobi.GRB.DoubleAttr;
import gurobi.GRB.IntAttr;
import gurobi.GRB.IntParam;
import gurobi.GRB.StringAttr;

I believed these lines should be updated to the latter format.
import com.gurobi.gurobi.GRB

Or, (to users) using gurobi v10.0.0 can work with current release of COMETS.
Hope this could be help.

Thank you for the information. Yes, gurobi changed the import, and this is how it works now.

Thank you so much. Switching to gurobi v10.0.0 worked for me.


Try to remove doNotCapture from resources.

shouldn't really be necessary.
Part of #51.
Tagging @lukehoban

This has been done.


Don't rely on globals

The currently relies on an Ember global and it should not need to.

Just add ember to the manually defined AMD module?

Yup :smile:


tokenization: don't regard missed partitions

i.e. don't show them if verbose and don't break if strict_span_conversion. If tokenization is performed partition wise, the partition annotations are not required later on and entries get quite probably removed when windowing is applied, so this just pollutes the logs.

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

Comparison is base (e85a98b) 96.35% compared to head (1700c21) 96.36%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage   96.35%   96.36%
=======================================
  Files          23       23
  Lines        1730     1731    +1
=======================================
+ Hits         1667     1668    +1
  Misses         63       63

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


[IIIF-1118] Handle access level requests

Simplify DatabaseServiceImpl
Remove placeholder tests
Handle access level requests
Minor constant renaming

I felt it was fine to remove the ID there because the ID is contained (albeit percent-encoded) in the URI (which is being logged along with the message) -- it feels redundant to me, but I'm not that opinionated about it being there or not.

I'd prefer it in the log (un-percent encoded), but it's also not a deal breaker for me. I approved as it, just think making it more readily accessible would be nicer.


Yoga layout for javascript browser does not work or not as expected

Hi,
I found a js demo on this issues that, in fact, resembles the demo for yoga in the docs :
import yoga, {Node} from 'yoga-layout';

const root = Node.create();
root.setWidth(500);
root.setHeight(300);
root.setJustifyContent(yoga.JUSTIFY_CENTER);

const node1 = Node.create();
node1.setWidth(100);
node1.setHeight(100);

const node2 = Node.create();
node2.setWidth(100);
node2.setHeight(100);

root.insertChild(node1, 0);
root.insertChild(node2, 1);

root.calculateLayout(500, 300, yoga.DIRECTION_LTR);
console.log(root.getComputedLayout());
// {left: 0, top: 0, width: 500, height: 300}
console.log(node1.getComputedLayout());
// {left: 150, top: 0, width: 100, height: 100}
console.log(node2.getComputedLayout());
// {left: 250, top: 0, width: 100, height: 100}

however the results are quite different to the expected ones!
{left: 0, right: 0, top: 0, bottom: 0, width: 500, …}
{left: 0, right: 0, top: 50, bottom: 0, width: 100, …}
{left: 0, right: 0, top: 150, bottom: 0, width: 100, …}

So Yoga is not adjusting the Nodes to left but at least creates a column, so weird but good enough, so I changed to:
const root = Node.create();
root.setWidth(500);
root.setHeight(100);
root.setJustifyContent(yoga.JUSTIFY_CENTER);

const node1 = Node.create();
node1.setWidth(100);
node1.setHeight(100);

const node2 = Node.create();
node2.setWidth(100);
node2.setHeight(100);

root.insertChild(node1, 0);
root.insertChild(node2, 1);

root.calculateLayout(500, 100, yoga.DIRECTION_LTR);
console.log(root.getComputedLayout());
// {left: 0, top: 0, width: 500, height: 300}
console.log(node1.getComputedLayout());
// {left: 150, top: 0, width: 100, height: 100}
console.log(node2.getComputedLayout());
// {left: 250, top: 0, width: 100, height: 100}

and the result is very weird:
{left: 0, right: 0, top: 0, bottom: 0, width: 500, …}
{left: 0, right: 0, top: -50, bottom: 0, width: 100, …}
{left: 0, right: 0, top: 50, bottom: 0, width: 100, …}

Its adjusting the nodes outside of the content even having plenty of space at the container's width.
I would expect in reality the output in the example for Node1 and Node2
{left: 150, top: 0, width: 100, height: 100}
{left: 250, top: 0, width: 100, height: 100}
I'm I missing something?

Ok, I have spent a while to have the same results. Playground has been very useful.
const root = Node.create();
root.setWidth(500);
root.setHeight(300);
root.setFlexWrap(yoga.WRAP_WRAP);
root.setFlexDirection(yoga.FLEX_DIRECTION_ROW);
root.setJustifyContent(yoga.JUSTIFY_CENTER);

const node1 = Node.create();
node1.setWidth(100);
node1.setHeight(100);

const node2 = Node.create();
node2.setWidth(100);
node2.setHeight(100);

root.insertChild(node1, 0);
root.insertChild(node2, 1);

root.calculateLayout(500, 300, yoga.DIRECTION_LTR);
console.log(root.getComputedLayout());
// {left: 0, top: 0, width: 500, height: 300}
console.log(node1.getComputedLayout());
// {left: 150, top: 0, width: 100, height: 100}
console.log(node2.getComputedLayout());
// {left: 250, top: 0, width: 100, height: 100}

You need to set
root.setFlexDirection(yoga.FLEX_DIRECTION_ROW);
and to maintain aspect of the nodes.
root.setFlexWrap(yoga.WRAP_WRAP);
So I recommend to update the standalone.md file and the docs

Defaults are now documented at https://www.yogalayout.dev/docs/styling/#default-styles and the new Playground now makes it explicit whether web defaults are being used (defaulting to not used).


[question] opinion about CSS Modules?

I think CSS Modules is a great idea to produce CSS that is scoped to the current component. Is anyone interested in it?
The upside is Webpack has really great tooling with css modules, the style loader, post css, etc. But of course it's not type safe (like purescript-css).

I would recommend using the style element or style attribute to do scoped CSS. See https://www.purescript-pux.org/docs/css


Fix mariadb root@% password issue

This PR fixes the issue mentioned in #115.

Tested and merged.


LaTeX in EstimatorResult.repr_html() is not rendered correctly

In fixing #1880, I noticed that many of our notebooks (e.g. estimation-hardcoded-circuit, estimation-random-circuit and others) don't render resource estimation details using the widget, but just directly using a pattern such as:
result = qsharp.estimate("RunHardcodedCircuit()")
result

This shows a table where the markdown isn't rendered correctly even with the linked fix in place (as that only applies to widgets), e.g.

In investigating the root cause for this, there are two issues to address:
Firstly, we have the below code in our pip package, but nothing in our docs or samples mentions requiring these packages, and no error or output is displayed to tell users to install them. We should document or provide output on this requirement if needed.
try:
    # Both markdown and mdx_math (from python-markdown-math) must be present for our markdown
    # rendering logic to work. If either is missing, we'll fall back to plain text.
    import markdown
    import mdx_math

    has_markdown = True
except ImportError:
    has_markdown = False

Secondly, even installing those packages didn't resolve the markdown rending in the table as shown in the screen shot above, so that needs to be fixed anyway.
CC @msoeken and @ivanbasov

One approach would be to move fully to widgets, which don't have this issue. If _repr_html() is to continue to be used, then there's a bug, though.


Repo merge

I merged all of the public config directories/repos into here!
First, I renamed the config-travis directory to dryad-config-example and merged the contents of that directory into it.
Then, I rewrote the script symlink_config.sh to do a couple things: if there isn't a ~/dryad-config directory already, it copies over the new dryad-config-example directory to it. Then, for the symlinking, it creates the same symlinks as before for the yml files, but it also creates a symlink directly for tenants, instead of making individual symlinks for the tenants.
Finally, the travis_prep script can just call on the symlink script now, instead of having to do a different copy of the .config-travis directory.
You can test this (hopefully) on your own machine, and you can test it on a vagrant machine too, assuming that you delete the ~/dryad-config directory and then re-running the symlink script again. Travis should pass this.

Oh, and by the way, I wonder if updating your chrome webdriver would help.  I think it gets installed by a gem.  You could try chromedriver-update in your application to see if it helps.  This is the github page for the gem that installs the chromedriver.  https://github.com/flavorjones/chromedriver-helper


🍒 Cherry pick PR #13703 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/13703 to staging 🍒

This pull request has merge conflicts and can not be automatically merged. :disappointed:
Please manually resolve the conflicts, push your changes, and then request another reviewer to review and merge.
Important: There may be conflicts that GitHub is not able to detect, so please carefully review this pull request before approving.

🚀 Cherry-picked to staging by @yuwenmemon in version: 1.2.41-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @yuwenmemon in version: 1.2.41-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Nothing worked when install library

        File "/home/user/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/user/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 149, in prepare_metadata_for_build_wheel
          return hook(metadata_directory, config_settings)
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 396, in prepare_metadata_for_build_wheel
          self.run_setup()
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 507, in run_setup
          super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 341, in run_setup
          exec(code, locals())
        File "<string>", line 301, in <module>
        File "<string>", line 297, in setup_package
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/numpy/distutils/core.py", line 135, in setup
          config = configuration()
        File "<string>", line 188, in configuration
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/numpy/distutils/misc_util.py", line 1050, in add_subpackage
          config_list = self.get_subpackage(subpackage_name, subpackage_path,
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/numpy/distutils/misc_util.py", line 1016, in get_subpackage
          config = self._get_configuration_from_setup_py(
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/numpy/distutils/misc_util.py", line 958, in _get_configuration_from_setup_py
          config = setup_module.configuration(*args)
        File "/tmp/pip-install-9bcr26h3/scikit-learn_03259c91ba89469ab60fa048076e6e61/sklearn/setup.py", line 83, in configuration
          cythonize_extensions(top_path, config)
        File "/tmp/pip-install-9bcr26h3/scikit-learn_03259c91ba89469ab60fa048076e6e61/sklearn/_build_utils/__init__.py", line 70, in cythonize_extensions
          config.ext_modules = cythonize(
        File "/tmp/pip-build-env-29w4ha_7/overlay/local/lib/python3.10/dist-packages/Cython/Build/Dependencies.py", line 1125, in cythonize
          result.get(99999)  # seconds
        File "/usr/lib/python3.10/multiprocessing/pool.py", line 774, in get
          raise self._value
      Cython.Compiler.Errors.CompileError: sklearn/ensemble/_hist_gradient_boosting/splitting.pyx

Im having the same problem, this you solve this issue ?


[Feature] Add the calculator for calculating prime numbers in a given range

Description
Add a calculator that identifies and lists all prime numbers between two user-defined values and also counts the total number of prime numbers in that range. This feature will help users not only find the primes but also understand the quantity within any specified range.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Can i work on this issue?

Can i work on this issue?

I will work on it after assigning it to me.


Breaking main React loop

Hi,
I have a following use case:
I'm using php-pm for request-response flow with psr7-adapter. So, my main class (application) is invoked with PSR7 request and response objects as any other middleware. An expected return value for middleware must be an instance of PSR7-Response. Since I'm using React HTTP client to call some APIs in my app I'm forced to use php-block-react so the PSR7-Response will be returned after all promises are done and data from APIs will be placed in PSR7-Response mentioned above. In simple words:

I receive PSR7-Request
I run few promises to call external APIs
I set await function to wait for all promises and block returning empty PSR7-Response
I parse promises response and fill my PSR7-Response with proper data
I return ready PSR7-Response object

I hope all here is clear and now my issue ;)
await function calls $loop->run() internally for obvious reasons. After all conditions for await functions are meet (promises fulfilled), the $loop->stop() is called (I also understand why it must be done like that). So, after await function my main React loop is turned off and my whole application is shutted down, since there is now way to turn React loop on again. Below I post simple example (different code, but the same principle):
{
  "name": "vendor_name/package_name",
  "description": "description_text",
  "minimum-stability": "stable",
  "license": "proprietary",
  "authors": [
    {
      "name": "author's name",
      "email"<EMAIL_ADDRESS>    }
  ],
  "require": {
    "clue/block-react": "^1.1.0"
  }
}

<?php

require_once 'vendor/autoload.php';

$loop = \React\EventLoop\Factory::create();

// postpone await, so main loop can be started
$loop->addTimer(0.5, function () use ($loop) {
    $promise = \React\Promise\Timer\resolve(6, $loop);
    $promise = $promise->then(function() {
        echo 'timer promise done' . PHP_EOL;
    });

    echo 'await loop start' . PHP_EOL;
    \Clue\React\Block\await($promise, $loop);
    echo 'await loop end' . PHP_EOL;
});

$loop->addPeriodicTimer(1, function() {
    echo 'test' . time() . PHP_EOL;
});

echo 'main loop start' . PHP_EOL;
$loop->run();
echo 'main loop end' . PHP_EOL;

I resolved this by creating second, internal React loop to handle every new request. By this I gain possibility to shutdown only internal loop (not the whole app), but in the time of processing request (and all external API calls), my main React loop is blocked, so obviously not a great, final solution :/
Any help is appreciated, maybe I'm doing something totally wrong here :/ Maybe I'm doing all right, this library is also totally correct, but the problem lies in absence of $loop->resume() function which will set $loop->running = true as stop() method sets it to false.

Thanks for filing this interesting ticket, but I'm really not sure there's much we can here, unfortunately.
As a rule of thumb, mixing async and sync code is never a good idea and should generally be avoided in the first place.
In this particular case, I would probably suggest keeping a second, inner loop which should indeed resolve most of the issues you're seeing. However, this will in fact block the outer loop and this is not something that can easily be avoided with your current middleware design.
In the longer run, I would suggest keeping an eye on https://github.com/reactphp/http/issues/28 where we will very likely promote a sightly modified middleware approach where each middleware can actually return a promise which eventually resolves to a response.
I hope this helps :+1:

In the longer run, I would suggest keeping an eye on reactphp/http#28 where we will very likely promote a sightly modified middleware approach where each middleware can actually return a promise which eventually resolves to a response.

Yup, this actually should help. Thx

I got same issue.
Why not just resume loop, after await finished?
// functions.php
function await(PromiseInterface $promise, LoopInterface $loop, $timeout = null)
{
// ...
    while ($wait) {
        $loop->run();
    }

    if($loop instanceof \React\EventLoop\StreamSelectLoop) {
        $reflection = new \ReflectionClass($loop);
        $property = $reflection->getProperty('running');
        $property->setAccessible(true);
        $property->setValue($loop, true);
    }
// ...

@Tatikoma This may or may not work in your particular setup, but there's really no way to support this on a general level because the event loop assumes control over your program flow.
See also my above comment, but as a rule of thumb, mixing async and sync code is never a good idea and should generally be avoided in the first place.

@clue Thanks. I understood that (mixing async and sync code is never a good idea) after few hours debugging. I'll nevermore mix sync & async code.

All of my code is async and I do not mean to block the whole process. I wanted to add this loopy waiting inside a promise that has a resolver and that resolver could run when this waiting has finished. It's basically about running a bunch of jobs (querying a server in sequence) and waiting for the last one to finish.
I've solved it by using a resolver that calls the original function on every partial resolution, but that builds a stack AFAIK, so it's not optimal. It would have been so much cleaner to introduce a local blocking inside a for, a wait() that worked similar to select() which allowed for other tasks in the loop to run asynchronously and once they were done, the wait() would get a signal from the loop controller and then that local code could proceed from there and finally resolve the main promise it was in.
Does this make sense?

@BitBargain Your suggested solution sounds like a perfect replacement :+1:
Don't worry about building up a stack as your promise resolution handlers will usually be called from different loop ticks and the stack will reset :+1:


Don't show my full name #6

Fix for #6

We need to change the name stays just before the input box.

Fixed with https://github.com/kadirahq/storybook-addon-comments/commit/397a4bb558bee9e6563aebf8b544e6bc173e4b7a


Set the correct nullability modifier on DartTypes in the output of CFE

The objects of subtypes of DartType in the output of CFE should have the nullability modifier set according to the compiled source code.
The implementation entails threading the attributes from the source code into the corresponding DartType subclasses' instances in both outlines and member bodies and correcting all of the algorithms that update types such as substitution, cloning, and inference.

Blocked on https://github.com/dart-lang/sdk/issues/37689, because generating function types from typedef types requires substitution.

The core of the issue is resolved.  All remaining inaccuracies are supposed to be fixed due to side effects of the other issues resolution.


index.html.md:31: Create documentation for what embedme...

The puzzle 9-ca3c2712 from #9 has to be resolved:
https://github.com/raboley/the-heroes-journey/blob/842c6bf4b756df9b36e8c4dda40442b3718e9fcb/source/index.html.md#L31-L31
The puzzle was created by @raboley on 05-Jul-20.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 9-ca3c2712 has disappeared from the source code, that's why I closed this issue.


Is reMarkable OS 3 supported yet?

Inquiry:
As of the last report I've seen, Toltec still doesn't support ReMarkable Version 3.anything, and says that at least one of the problems was an open issue in Oxide's support for this environment.
My tablet is currently at <IP_ADDRESS>6. I would love to open it up for more versatile use -- as a music book/songbook in particular -- but I don't see a path forward. And I don't know of a way to roll it back to (and hold it at) an earlier ReMarkable release.
Any chance of a path forward? Or a path back?
Context:
(https://github.com/toltec-dev/toltec/discussions/673)

#337 and #342 added folio support to oxide, which will add support to oxide for 3.3.2. This is in the unreleased 2.8 version, but it may be a while before I release it.
The following issue is tracking 3.x support in toltec: https://github.com/toltec-dev/toltec/issues/820

...And I don't know of a way to roll it back to (and hold it at) an earlier ReMarkable release.
Any chance of a path forward? Or a path back?

https://remarkable.guide/faqs.html#can-i-downgrade-to-a-different-os-version

Great- many thanks (and apologies for spamming the ReMarkable projects, but it wasn't clear how an answer to one would interlock with the others )
--
/_  Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/   https://www.amazon.com/dp/B09WJ3H657/
Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant.

From: Nathaniel van Diepen @.>
Sent: Monday, January 29, 2024 1:56:07 PM
To: Eeems-Org/oxide @.>
Cc: Joe Kesselman @.>; Author @.>
Subject: Re: [Eeems-Org/oxide] Is reMarkable OS 3 supported yet? (Issue #346)
#337https://github.com/Eeems-Org/oxide/pull/337 and #342https://github.com/Eeems-Org/oxide/pull/342 added folio support to oxide, which will add support to oxide for 3.3.2. This is in the unreleased 2.8 version, but it may be a while before I release it.
The following issue is tracking 3.x support in toltec: toltec-dev/toltec#820https://github.com/toltec-dev/toltec/issues/820
...And I don't know of a way to roll it back to (and hold it at) an earlier ReMarkable release.
Any chance of a path forward? Or a path back?
https://remarkable.guide/faqs.html#can-i-downgrade-to-a-different-os-version
—
Reply to this email directly, view it on GitHubhttps://github.com/Eeems-Org/oxide/issues/346#issuecomment-1915364382, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7OJ6W4PZO2WSYKLNZXBVBLYQ7WEPAVCNFSM6AAAAABCP6BY5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGM3DIMZYGI.
You are receiving this because you authored the thread.Message ID: @.***>


[DPUL/production] NoMethodError: undefined method `metadata' for #IiifService::ManifestParser::IIIF3Manifest:0x0000562b485b21f0

Backtrace
line 120 of [PROJECT_ROOT]/app/values/manifest_metadata.rb: metadata_hash
line 106 of [PROJECT_ROOT]/app/services/iiif_manifest.rb: manifest_metadata
line 8 of [PROJECT_ROOT]/app/services/iiif_manifest.rb: to_solr

View full backtrace and more info at honeybadger.io

Params:
{
  "context" => "Job raised exception",
  "job" => {
    "class" => "ActiveJob::QueueAdapters::SidekiqAdapter::JobWrapper",
    "wrapped" => "Spotlight::ReindexJob",
    "queue" => "default",
    "args" => [{
      "job_class" => "Spotlight::ReindexJob",
      "job_id" => "e354c20d-d637-4b63-9b1a-49cdb62bc5da",
      "provider_job_id" => nil,
      "queue_name" => "default",
      "priority" => nil,
      "arguments" => [
        {"_aj_globalid" => "gid://pomegranate/IIIFResource/218025"},
        {
          "reports_on" => {"_aj_globalid" => "gid://pomegranate/Spotlight::JobTracker/477788"},
          "validity_token" => nil,
          "_aj_ruby2_keywords" => ["reports_on"]
        }
      ],
      "executions" => 0,
      "exception_executions" => {},
      "locale" => "en",
      "timezone" => "UTC",
      "enqueued_at" => "2022-07-28T14:30:20Z"
    }],
    "retry" => true,
    "jid" => "6f883a131d277e430f8d05df",
    "created_at" =><PHONE_NUMBER>.1127348,
    "enqueued_at" =><PHONE_NUMBER>.2460225,
    "error_message" => "undefined method `metadata' for #<IiifService::ManifestParser::IIIF3Manifest:0x00007f90f0d19fb0>",
    "error_class" => "NoMethodError",
    "failed_at" =><PHONE_NUMBER>.8611636,
    "retry_count" => 13,
    "retried_at" =><PHONE_NUMBER>.1231792
  },
  "jobstr" => "{\"class\":\"ActiveJob::QueueAdapters::SidekiqAdapter::JobWrapper\",\"wrapped\":\"Spotlight::ReindexJob\",\"queue\":\"default\",\"args\":[{\"job_class\":\"Spotlight::ReindexJob\",\"job_id\":\"e354c20d-d637-4b63-9b1a-49cdb62bc5da\",\"provider_job_id\":null,\"queue_name\":\"default\",\"priority\":null,\"arguments\":[{\"_aj_globalid\":\"gid://pomegranate/IIIFResource/218025\"},{\"reports_on\":{\"_aj_globalid\":\"gid://pomegranate/Spotlight::JobTracker/477788\"},\"validity_token\":null,\"_aj_ruby2_keywords\":[\"reports_on\"]}],\"executions\":0,\"exception_executions\":{},\"locale\":\"en\",\"timezone\":\"UTC\",\"enqueued_at\":\"2022-07-28T14:30:20Z\"}],\"retry\":true,\"jid\":\"6f883a131d277e430f8d05df\",\"created_at\":1659018620.1127348,\"enqueued_at\":1659109777.2460225,\"error_message\":\"undefined method `metadata' for #<IiifService::ManifestParser::IIIF3Manifest:0x00007f90f0d19fb0>\",\"error_class\":\"NoMethodError\",\"failed_at\":1659018620.8611636,\"retry_count\":13,\"retried_at\":1659081131.1231792}"
}

This one also isn't syncing https://figgy.princeton.edu/catalog/4e4bf086-a7bd-4448-a2a4-6c31d554ae89; expect to find it in https://dpul.princeton.edu/performances

might be the same as #1362

The manifest loads fine, then DPUL follows the seeAlso to get the jsonld, which returns a 406 "Not Acceptible" here: https://github.com/pulibrary/dpul/blob/6dce643808098684c6ce3dbb91ec896b5d1299e5/app/values/manifest_metadata.rb
However, there doesn't appear to be an issue with Accept headers or anything, because a browser loads it fine in a logged-in window but gets the 406 in an incognito window.
It seems like we need to handle authorization of jsonld show pages the same way we handle authorization of manifests. i.e. if can :manifest then you should be able to see the jsonld.

Or maybe jsonld should show if can :discover

collection looks like it indexed correctly. retried jobs in dpul's retry queue and they went through.


Fix FutureWarning for missing label

Passing list-likes to .loc or [] with any missing label will raise
KeyError in the future, you can use .reindex() as an alternative.
See the documentation here:
https://pandas.pydata.org/pandas-docs/stable/indexing.html#deprecate-loc-reindex-listlike
return self._getitem_tuple(key)

Fixed in 6a8ecfb.


Added Kazan Federal University

https://kpfu.ru/
https://kpfu.ru/sveden/education/
https://kpfu.ru/sveden/files/000788.pdf

@almaz-it First stage of verification passed, official domain is kpfu.ru as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://kpfu.ru/staff_files/F_987276766/08648556.pdf

@almaz-it Unfortunately, your request cannot be processed further because JetBrains doesn’t provide product or services to territories subject to applicable EU, UN or US sanctions or under comprehensive export control restrictions due to legal, compliance and other commercial related risks.

Students from different countries study here. thanks


Poor text detection on source code

Environment

Tesseract Version: 4.00.00alpha
Platform: Ubuntu Docker image

Current Behavior:
When I give it the following image, the text detection is really bad.

It outputs the following:
Warning. Invalid resolution 0 dpi. Using 70 instead.
## Parancters
= buser® = A User struct.

## Examples

user = MUser{nanes "Alice Winston}
User. first. nane(user)

"Mice"

def first_name(user) do
user

17 Bout
1° first
end

adec !
Get the last name of a user.

## Parancters

'user® - A User struct.

enero oE \ s |

Expected Behavior:
It outputs the correct text.
Suggested Fix:
I don't know how Tesseract works in its core but the image contains clear and readable characters, even in English.

Tesseract works best on 300 dpi black and white images.
Preprocess your image, you will get better result.
See attached.

Here is the OCRed result using
Tesseract Open Source OCR Engine v4.00.00dev-549-g2b854e3 with Leptonica
13
14 ## Parameters
15
16 _- 'user' - A User struct.
17
18 - ## Examples
19
20 user = %User{name: "Alice Winston" }
21 User. first_name(user)
22 "Alice"
23 serts
24 - def first_name(user) do
25 user
26 [> Bplit
27 [> first
28 end
29
30 @doc nnn
31 Get the last name of a user.
32
33 ## Parameters
34
35 - 'user' - A User struct.
user. exs unix < utf-8 < elixir _ 50%

Yeah, that's a lot better. Thank you!

@Shreeshrii What have you used to preprocess the image? I tried it with imagemagick but the result isn't quite good and therefore the OCR result too.

I used irfanview interactively to resize the image to a larger size, increase dpi to 300, convert to grayscale, reduce color depth to 2 and invert the colors.
You should be able to do similar conversion using imagemagick.

@Shreeshrii The best I can get is this:

Using this command:
convert -units PixelsPerInch input.png -resize 1200 -density 300 -colorspace gray -depth 1 -negate output.png

Not sure if imagemagick can do better.

I had resized to 1920 x 1080 and 300 dpi.
You have to experiment with the settings and see what works best. See
https://github.com/tesseract-ocr/tesseract/wiki/ImproveQuality for more
tips.
ShreeDevi

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com
On Tue, Jun 20, 2017 at 1:04 PM, Phillipp Ohlandt<EMAIL_ADDRESS>wrote:

@Shreeshrii https://github.com/shreeshrii The best I can get is this:
[image: frame_24721-2]
https://user-images.githubusercontent.com/3123549/27321677-64de42d2-559b-11e7-8d3a-f405b18d5fbf.png
Using this command:
convert -units PixelsPerInch input.png -resize 1200 -density 300 -colorspace gray -depth 1 -negate output.png
Not sure if imagemagick can do better.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/997#issuecomment-309669745,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_o-0wgvHJPxFAHCJURDfSBTRHEUMzks5sF3XzgaJpZM4N-Jpf
.


Port librealsense to UWP (for Windows IoT)

Required Info

Camera Model
R200, F200 or SR300

Firmware Version
Any

Operating System & Version
Windows 10, Windows 10 IoT

Kernel Version (Linux Only)

Build System
VS2015

It would be really nice to have this library working for UWP Apps.
Having it for Windows 10 (full) is important, but on that operating system we can use the full sdk already.
Porting it to UWP would allow us to run on Windows 10 IoT on devices like the Intel Joule.
I tried to recompile it for UWP, but I got this error:
#error:  KS.H must be included before KSMEDIA.H (compiling source file ....\src\uvc-wmf.cpp)	librealsense.uwp	C:\Program Files (x86)\Windows Kits\10\Include\10.0.14393.0\shared\ksmedia.h	18
Is it feasible?
Cheers!

Appreciate your feedback. It is a possible direction we are considering, but it is not planned at the moment.
This would require adding a new backend type (uvc-wmf.cpp just won't not do) and finding some work-around for WinUSB (not supported to the best of my knowledge)
So it would be challenging to get right.


Create Your First Application with SAP Cloud SDK for JavaScript

Tutorials: https://developers.sap.com/tutorials/s4sdkjs-odata-service-cloud-foundry.html
In step 4
The attribute "requestBuilder" does not exist on type "Typeof BusinessPartner".

Hi @junkukaka,
We've released a new major version update recently which might make the tutorials temporary outdated. We plan to migrate them to our documentation in the nearest future. In the meanwhile, I'd recommend looking at our getting started guide here: https://sap.github.io/cloud-sdk/docs/js/getting-started
You can also check our sample apps here:
https://github.com/SAP-samples/cloud-sdk-js
I'll be closing this issue for now as it's 19 days old. Don't hesitate to get back to us if you still have any questions.
In case you have already developed with the SDK, you can find support in our official GitHub repository: https://github.com/SAP/cloud-sdk-js/issues


SyntaxError on home view at first install

On setting up the app (on a fresh phone) and logging in for the first time, I get this screen:

The error message is "Uncaught SyntaxError: Unexpected identifier".
Going to a stream works normally; after doing that and sending a message I returned to the home view, and it loaded fine.
This is on an Android phone, with version 6.5.52.

See also reports today. (I'm on 7.6.60, and others say they're updated.) Hard to tell as a user if this is the same bug or just a similar one.

Oh hey, there's already a new version. :-)
On 8.1.62, it took some more doing. But after I scrolled way up in #test here, then way back down, and scrolled up some more looking for repros of #1800 -- eventually I saw it again:

(Maybe the SyntaxError after scrolling a lot is a separate issue from the SyntaxError at startup -- feel free to make a separate issue for it and close this one.)


Proposal: Switch v2.0 versions to use same base as RancherOS v2

Continuation to #88 but with different approach.
It looks to be sure now that we will see RancherOS v2 and in the fact first test version is already available on https://github.com/rancher/os2/releases/tag/v0.0.1-test01 but as their strategy is support Kubernetes only there is still room for BurmillaOS.
As we have not ever released anything else than beta versions under v2.0 schema can still change architecture for it. So I created prototype version to https://github.com/burmilla/os2/releases/tag/v0.0.1-test01-burmilla which contains Docker instead of Kubernetes.
What is interesting is that they have ended up to quite similar solution than which I proposed on https://github.com/burmilla/os/issues/88#issuecomment-839804934 with two root partitions and read-only overlay on top of it.
This approach would:

Simplify maintenance work as most of the code would be common with them.
Add UEFI support #8
Be clear answer to  #47 and we can instruct all Kubernetes users to use RancherOS v2 instead of BurmillaOS.

Biggest open question is that how much work is needed to make ros upgrade working with that one and create migration/upgrade path. (Partial solution already exist on https://rancher-sandbox.github.io/cos-toolkit-docs/docs/getting-started/upgrading/ )

This sounds like a sensible approach that does a good job of balancing features and maintainability.

RancherOS v2 looks to be stuck on alpha phase but now SUSE released this one as beta which we probably should investigate? https://news.opensuse.org/2022/04/05/leap-micro-beta-available-for-testers/

RancherOS v2 looks to be stuck on alpha phase but now SUSE released this one as beta which we probably should investigate? https://news.opensuse.org/2022/04/05/leap-micro-beta-available-for-testers/

The Harvester docs replaced K3OS with Elemental ~6mos ago.  As this was (I think?) the impetus for RancherOS 2 (which was just tagged with another release today) it may be premature to remove that option.  Also, os2 feels more open/accessible than Leap but that could be me not really understanding the OpenSuse way...

The Harvester docs replaced K3OS with Elemental ~6mos ago. As this was (I think?) the impetus for RancherOS 2 (which was just tagged with another release today) it may be premature to remove that option.

True. On https://github.com/harvester/os2 it looks to be still updating.  However it is also based on openSuse Leap https://github.com/harvester/os2/blob/ae38642196eedbd919a984f3aa89c72800f14599/Dockerfile#L3

Also, os2 feels more open/accessible than Leap but that could be me not really understanding the OpenSuse way...

Yes that is quite big disadvantage. Bugs need to be reported using Bugzilla and I found source codes as rpm packages only. However as Rancher is now part of Suse it is clear that they are looking for sharing best practices so let's hope that Suse will be more open in future.

Move to suse leap micro for harvester looks to be official now
https://github.com/harvester/os2/pull/40

Yea and they looks to be renamed RancherOS v2 to Elemental which development continues on https://github.com/rancher/elemental

Closing for now as no one is working on this area.


Container building for https://registry.opensuse.org

Deploy preview for openbuildservice ready!
Built with commit 8358a0a3aaee2836e09943b6f5e2bcaa85ce9e59
https://deploy-preview-152--openbuildservice.netlify.com