pause command pauses globally

Currently, the pause command pauses globally. Should an option to pause just for the current terminal session be added?
The way I see it there are three options:

leave things as they are.
make the pause command pause for the current terminal session only.
make the pause command able to pause for the current terminal session or globally using flags.

Personally, I think option three makes the most sense as more options are generally a good idea.

Personally, I think option three makes the most sense as more options are generally a good idea.

I think I'll do this by adding a file inside the terminal sessions log dir. This file can act as a flag for the status of the terminal session (if it contains the phrase "paused" then the tool is paused in that terminal session, other wise the tool is active)

this functionality was just added to the dev branch with commit 428db2c but still needs to be tested before merging into main.

implemented in commit b0916b2


Person Category

Person Category Issues:

It is defaulting to Faculty when null
You can't set the category to Faculty from null unless you change it to something else and then to Faculty (Don't have to save between these)

Simple solution might be to add a value to the dropdown -- Not Set -- for nulls. As long as that string value doesn't get saved

Or include a "Default" like we have on equipmentType.


[FLINK-15352][connector-jdbc] Develop MySQLCatalog to connect Flink with MySQL tables and ecosystem.

What is the purpose of the change
Develop MySQLCatalog to connect Flink with MySQL tables and ecosystem.
Brief change log
Develop MySQLCatalog to connect Flink with MySQL tables and ecosystem.

Adds MySQLCatalog class.
Adds MySQLCatalogITCase
Supplements /dev/table/connectors/jdbc/ & /dev/table/catalogs pages in English edition and Chinese edition.

Verifying this change
This change added tests and can be verified as follows:

Adds MySQLCatalogITCase

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@wuchong @bowenli86 Could you help me to review this PR ? Thank you very much.

Thanks for the contribution @RocMarshal. It sounds like a useful addition but I'm wondering whether we should rather offer a generic JdbcCatalog. I was not involved in the original discussion that created FLINK-15352. Could you elaborate what is special about this catalog?

Offering a generic JdbcCatalog is a good idea. However, a generic JdbcCatalog requires adding more interfaces to JdbcDialect which is still an internal interface. So, there is no much differences between the two approaches. Therefore, I'm
fine to first introduce this MySqlCatalog.
We can discuss and re-design a public-purpose JdbcDialect in another issue which can offer a generic JdbcCatalog.

I'm fine to postpone this refactoring but still I would like to reduce code duplication as much as possible. Esp. for documentation it copies a lot from the JDBC catalog examples. It would make more sense to explain the differences between various JDBC catalogs and have a general section above.

Yes. I think in documentation we should call them Jdbc Catalog, e.g. "Jdbc Catalog for MySQL", "Jdbc Catalog for PostgreSQL".
We can refactor the implementation later.

@wuchong  @twalthr Thank you for your suggestions.  I'll simplify the related documentation in this PR.
Looking forward to the refactoring next.

@wuchong @twalthr Thank you for your suggestions. I'll simplify the related documentation in this PR.
Looking forward to the refactoring next.

@wuchong @twalthr I updated the part of the documentation mentioned above. Could you help me to check it ? Thank you.

Hi, @wuchong .  Could you help me to check it if you have time? Thank you very much.

Hi, @wuchong . I made some changes in the ITCase part of the PR.  Could you help me to review this PR if you have free time? Thank you.

Hi, @MartijnVisser @Airblader , I made some changes based on your suggestions. Would you like to review it for me? Thank you so much for your attention.

@alpinegizmo Could you help me to review this PR ? Thank you very much.

Thanks @Airblader @MartijnVisser for the review.
Hi, @wuchong , @xintongsong @twalthr . Could you help me to merge it if there are nothing inappropriate ? Thank you for your help.

Could someone help me to advance it ? Thx

@Airblader Thank you  so  much for the review. I made some change. Could you help me to check it again?

@flinkbot run azure

@flinkbot run azure

@MartijnVisser @Airblader Excuse me, Could you help me to check it if you have free time ? Thanks a lot.

@RocMarshal Thanks for the update. I do think that it's better to not keep asking for reviews, especially pinging multiple people. Committers always look out for PRs that they can review and/or merge, but there is only so much available time and they can't process all PRs as soon as everyone would like.

I'm very sorry for the action. It's really not my intention to led to the trouble.
Thanks for your @MartijnVisser  reply and reminding.
Best Wishs.

@RocMarshal No worries, I can also understand your desire to get this reviewed and merged. We wouldn't be anywhere without contributions and the community, so we all try to get PRs reviewed and merged as soon as possible.

@flinkbot run azure

@zentol Would you mind helping me to advance the PR if you have a moment ? Thanks.

@RocMarshal Most of the maintainers on the SQL side of things are quite busy at the moment. Everyone is trying to review as much PRs as possible and they will review your PR.

@flinkbot run azure

Sorry for interrupting. @AHeise Could you help me to review the PR if you have moments ? Thank you very much.

@RocMarshal I have put this PR on my TODO list. I will do a final review this week. We hopefully can merge this beginning of next week.

@twalthr Sorry for the interruption. Is there any new progress in this PR?  If any improvement is needed, I am very happy to advance it. Thank you.


[v3] Problem with "list-index" and class "simple-list"

Please note that this problem only occurs with version 3 of Framework7 and not with version 4 (beta).
In the "list-index" with
 the group titles do not have a sticky position when scrolling within a single group.
Probably because the CSS property "position: relative" of the element ".list.simple-list li" overwrites the CSS property "position: -webkit-sticky" of the element "li.list-group-title".
Forcing "!important" on the property "position: -webkit-sticky" of the element "li.list-group-title", the problem does not occur.

Please note that this problem only occurs with version 3 of Framework7 and not with version 4 (beta).
In the "list-index" with
 the group titles do not have a sticky position when scrolling within a single group.
Probably because the CSS property "position: relative" of the element ".list.simple-list li" overwrites the CSS property "position: -webkit-sticky" of the element "li.list-group-title".
Forcing "!important" on the property "position: -webkit-sticky" of the element "li.list-group-title", the problem does not occur.

I have same problem


[SMALLFIX] Initialize ClientContext on two basic operations examples

Otherwise client will use localhost as master address if it's failed to navigate system and configuration properties.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8923/
Test PASSed.

LGTM. Thanks for the fix.

LGTM


Blog monthly analytics

@lpgoldstein Blog June monthly analytics are ready for your review:
https://github.com/DOI-ONRR/blog-nrrd/wiki/Analytics
Check excel here


dev-alert website: unable to remove species (linked observations!)

Pacifastacus leniusculus
Orconectes limosus
Elodea nuttallii

also to think about: what should be the logic in production, for such cases?

The curent constraint is probably too strict. When removing a species, it probably makes sense to remove all its observations.

Works, I've now removed the 3 species from dev-alert.


Fix error with the non-native method Promise.defer() in callableFork.js

Fix error with the non-native method Promise.defer() in lib/utils/callableFork.js.
// promise-defer
// https://github.com/moll/js-promise-defer
function Deferred(Promise) {
  if (Promise == null) Promise = global.Promise
  if (this instanceof Deferred) return defer(Promise, this)
  else return defer(Promise, Object.create(Deferred.prototype))
}

function defer(Promise, deferred) {
  deferred.promise = new Promise(function(resolve, reject) {
    deferred.resolve = resolve
    deferred.reject = reject
  })

  return deferred
}

// lib/utils/callableFork.js
function promiseDefer () {
  let deferred = Deferred(Promise)
  deferred.polygoat = polygoat.bind(this, deferred.promise)
  return deferred
}

Fixed by be9ec84


fix timezone and localtime

Currently the directories /etc/localtime/  and /etc/timezone/ exist on the system.
It would be perfect if they would be files and not directories even if they are empty.
 Important: image verification is a tech preview feature and should not be relied on to provide security.

Digest: sha256:76fdd96ebcdece6a38b4caffc6e2fabf4e1934e944c792269b497f3edfeaa376
Status: Downloaded newer image for mongo:latest
Error response from daemon: Cannot start container 7c052ef5cd148dc94a16a4ae86af79b5bd03fff1a0a45881edddadd773976b01: [8] System error: not a directory
[colin@trymon boot2docker-xhyve (master)]$

Workaround:
docker@boot2docker:~$ sudo rm -rf /etc/localtime/
docker@boot2docker:~$ sudo touch /etc/localtime
docker@boot2docker:~$ ^D
[colin@trymon boot2docker-xhyve (master)]$ docker run -v /etc/localtime:/etc/localtime:ro -it --rm mongo bash
root@3bab6adb227a:/#


Custom 404 error page

Fixes #131
Description
Added a custom 404 error page.
Other information
Added a custom 404 error page using only texts and styled using CSS.

Checklist:

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[x] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Looks good!

@kgodey Thank you, mam, I would now work on adding blogs to be part of series.

Sounds good


How to read all saved keys ?

Hello, I try to find method to read all saved keys:
Something like this:
let keychain = KeychainSwift()
for key in keychain.allKeys() {
   let data = keychain.getData(key)
}

How I can do this ?

Hello @filippovdev, good question. Unfortunately the library does not have this feature. If you need it, feel free to submit a pull request.


Aspects Beta Feedback

This epic is to capture feedback from beta testers, though not necessarily every piece of feedback will make it into v1 we can link tickets in various repos from here.
Data WG Demo Feedback 2023-09-20:

General - We may want to add section / subsection filters and/or prepend problem / video / etc. names with the section and subsection and sort by them (https://github.com/openedx/tutor-contrib-aspects/issues/436)
Course Enrollment - Clarify text around enrollment mode changes if they are impacting the “Events per day” numbers (moving between modes can create implicit unenroll/enroll events)
Problem Engagement - Responses per problem may be bonkers with a large course
Problem Performance - Answer name, especially multi-select answers get unreadably long. Andy suggested a dimension per answer which seems reasonable
Problem Performance - Distribution of attempts and Distribution of hints would make more sense if we could overlay the number attempts / hints allowed for the problem. Maybe something similar for Distribution of Problem Grades, where true/false will always bucket into 0-9% and 90-100%, but other problems may have more nuance
Video Engagement - Transcripts text should be updated to indicate whether we get an event only when a user clicks or if we get one any time they watch a video with it enabled (I believe it’s the latter). We should include a language breakdown for transcripts / cc as well
Ensure that all date charts have date labels on them, otherwise it's unclear that date filters are in play
Make block labels on charts into links back to Studio or LMS so it's easier to find them. This is likely to require a custom visualization, but probably worth it

I'm going to close this in favor of the work @crathbun428 has done with user interviews, but feel free to make tickets for anything you think we should keep in mind Chelsea.


Make graph reversible

We're going to have to make the graph reversible in order to to query in the opposite direction of the FST. We should probably rename _traverse and whatever the new method is to use the up or down distinction like foma does. To traverse the reversible graph, you're going to want to iterate on the accepting states, and then use each of those accepting states as your starting point in the traversal.

This should actually be handled by #4 now I think.

Closing as now irrelevant.


Yaml path fix

This PR will fix the yaml path inconsistencies while testing the quickstart guide of ianvs. It fixes the pcb-aoi. https://ianvs.readthedocs.io/en/latest/guides/quick-start.html#step-3-ianvs-execution-and-presentation
@creativityH @MooreZheng

Thank you @octonawish-akcodes your work is appreciated
It looks like the CI is failing and @hsj576 might take a look at it

/assign @MooreZheng

/assign @MooreZheng

/assign @MooreZheng

/assign @hsj576


question about class_name

Can Medsam directly obtain the category of the segmented region ? During finetuning, there were no categories with regions included

HI @dswahu ,
NO. SAM-like model doesn't consider the category information.


setup vitest & fix: type check

Hello, I'm a member of the gru.ai team. To use gru for writing unit tests for big-AGI, I made the following adjustments:

Installed Vitest as the unit testing tool.
Fixed existing TypeScript type issues.

Thanks @jojoLockLock, merged.


Fix/nwps 1435 be cards download no error shown

Show Error of 10MB limit for documents in Download cards

Not required as it is brXM product bug


polyup duplicates comments

Example:
<polymer-element name="example-element">
  <script>
    Polymer('example-element', {
      ready: function() {
        var foo = 1;

        /* This is an example block comment which is intended
         * to refer to the block of code below. */
        var bar = 2;

        // This is a line comment which refers to the block below.
        var baz = 3;
      }
    });
  </script>
</polymer-element>

Gets converted to:
<dom-module id="example-element">
</dom-module>
<script>
  Polymer({
    is: 'example-element',
    ready: function () {
      var foo = 1;  /* This is an example block comment which is intended
                     * to refer to the block of code below. */
      /* This is an example block comment which is intended
       * to refer to the block of code below. */
      var bar = 2;  // This is a line comment which refers to the block below.
      // This is a line comment which refers to the block below.
      var baz = 3;
    }
  });
</script>

Huh, interesting! Thanks for the bug report, I can reproduce this.

Seeing this too


fix(sales-dashboard): prevent 500 error when user doesn't exist on sales dashboard search

Changes
Prevents a 500 error when searching the sales dashboard for a user email address that doesn't exist. In fact, if that is the case, it grabs the domain and searches for organisations belonging to users with that domain.
Note that the reason this can't be simplified to e.g. users__email__endswith is because of this PR: #4377.
How did you test this code?
Added a new unit test.

grabs the domain and searches for organisations belonging to users with that domain.

This behaviour is super useful, but I don't like it as a fallback, especially for public domains such as gmail.com, icloud.com, etc. Returning 0 results when searching for a specific user in this case is desirable.
Instead, we could make this explicit when searching for a domain, like @example.com, which would return all organisations that have users with a domain of example.com.

grabs the domain and searches for organisations belonging to users with that domain.

This behaviour is super useful, but I don't like it as a fallback, especially for public domains such as gmail.com, icloud.com, etc. Returning 0 results when searching for a specific user in this case is desirable.
Instead, we could make this explicit when searching for a domain, like @example.com, which would return all organisations that have users with a domain of example.com.

Yeah, I tend to agree. I was just being lazy. I'll update.


Testing a klyva-app

If we assume jest, and optionally some jest-extension, what developer experience should there be for testing an app built with klyva?
Maybe something like klyva.resetAll() to move klyva state to initial? How would this be done with a redux-based app?

Ooh interesting idea.
I think in a redux-based (or any app that contains the state within a react context-provider, such as jotai and recoil), the state of the "store" is restored between tests, because a new Provider is loaded.
I'm thinking this would be really nice, but I'm wondering about implementation details.
Approach 1: A global callback, i.e. klyva.resetAll()
For us to make a resetAll-function, we need first store the "first" stored value for all "primitive" atoms, which is fine. But then we need to subscribe to a global "reset" event, which I wonder how we can do without memory leaks, the subscription needs to end when the atom ends? Possibly, we can use a Weak map or atom, I'm not sure, since they are not iterable.
Approach 2: Use jest as a platform
It's possible to use jest resetmodules or isolatemodules (https://jestjs.io/docs/en/jest-object.html#jestresetmodules) to accomplish this. How do we do this neatly? We at least need to make some official documentation that shows how to d othis.
@sesam , how do you feel about these approaches?

Just sketching here, but a really cool way of doing this would be something like this:

Klyva module contains a let resetVersion = 0, klyva exports a resetAll() or similar.
Klyva PrimitiveAtom's always store the value that they were constructed with constantly. They also keep a local state which says which resetVersion they were created at.
Klyva PrimitiveAtoms when subscribed to, subscribe to changes to the resetAll, and unsubscribe when unsubscribed to. When resetAll is called, they 1. reset to their initial value, and 2. update their resetVersion
When getValue is called on a primitive klyva atom, it FIRST checks if the resetVersion is the same as the previous resetVersion, if not, they skip all other work and just reset to their initial value.

This actually elegantly fixes the "dream code" scenario of just providing a klyva.resetAll() without any memory leaks.

I don't think this is a bad idea,
From a memory-management perspective this is optimal:

Only base atoms store the initial value, all other derived atoms are just derived from it.
The base atoms only store a reference to the value anyway.

I'll have more confidence in my opinion once I've added tests for the components in the Klyva TodoMVC implementation, but spontaneously I'm sceptical towards a .resetAll method from a testing perspective.
What would the gains be? Sharing atoms between tests just to call .resetAll in each is functionally the same as just giving each test a new atom instance. Except in the former scenario you run the risk of accidentally sharing state.
Right now in the TodoMVC implementation we simply pass atoms down from the top of the component pyramid, meaning the atoms are received as props making testing a breeze. Since splitting atoms is SO easy with Klyva, I imagine prop-drilling will feel like less of a hassle, and that you can get away without a provider mechanism even in medium-sized apps.
In a large app I would likely just provide the central atom via a global system. If React I'd use context and a Provider, and for the tests I'd wrap Testing Library's render method in a testRender util that takes the initial atom state I want to provide, just like I would do for a Redux app (see example here).
But it might well be that I just miss the point and the advantages of .resetAll! 😄
On that topic - say that .resetAll did exist, what would a test using that look like?

+1, I think starting fresh with new state is conceptually much simpler than trying to reset an existing state. In React I really like context-based state management, because it's very easy to reason about for testing, and also generally easy to manually set up whatever state you need in a particular situation. I'm skeptical that prop drilling would be practical in more than a trivial app, but maybe @krawaller's right about klyva's advantages here.

I'm skeptical that prop drilling would be practical in more than a trivial app, but maybe @krawaller's right about klyva's advantages here.

Hmm. Actually I've come around and think you're right, @uhoh-itsmaciek. I'll try rewriting the TodoMVC example with context instead to see how it feels.

how to do without memory leaks

A job for WeakMap perhaps? :)
I use resetAll (jest.resetAllMocks) to get back to the initial state with minimal test code. I agree it might be an edge case in many situations.
I had thought that klyva-based code would avoid prop drilling / triggering a Context that in turn alerts the whole tree below. I was thinking that performance profiling a klyva app would "light up" only components subscribed to something that changed.
I didn't think through how to inject / replace with fresh atoms in a tree of components, but I guess avoiding testing too deep structures at once is a good idea, then I guess reset is less needed. Probably best to leave the related PR unmerged until we find someone really needs it :)


FAB doesn't render properly

Turns out it was because .md-fab-bottom-right was appended to the wrong element.
Before:
<md-fab-speed-dial class="md-fling">
  <md-fab-trigger>
    <md-button class="md-fab md-primary md-fab-bottom-right">
      ...
    </md-button>
  </md-fab-trigger>
  ...
</md-fab-speed-dial>

After:
<md-fab-speed-dial class="md-fling md-fab-bottom-right">
...
</md-fab-speed-dial>


Adding CoC guidelines for enforcing incidents in public forums that don't require an official report

Hey all - a few times now we have had people show up on the community forum (I think this has happened on the listserv as well but we don't really have control over the tech there as much) being rude, unhelpful, or otherwise confrontational.
I have a personal approach to how I deal with these situations (generally, a polite note of what the person is doing wrong and locking the thread) but I think it'd be helpful for Jupyter to have guidelines for how people should handle these situations in general.
I believe that these kinds of situations don't merit an official CoC violation report, since usually it is from people who aren't active in the community and going through an official process for every jerk on the internet would be a time-consuming process. Instead some language about "if you fail to abide by XXX rules in public forums that Jupyter controls, you can expect YYY to happen" would be helpful.
What do people think about this? If folks are +1 I can add some language in a PR.

I think you handled a recent situation really well, and I agree that adding some language about possible ways to address things like locking threads with an example coment would be helpful, so thanks!
In addition to what you've said in a recent situation, I would also add an explicit invitation to please open a new issue/post with a more constructive take, i.e., reassure the person that we do want to discuss their honest concerns, and that we are only locking because of the way they expressed things.
I also think it's important to close/lock an initially disrespectful post and reset the tone of the conversation in a new post, even if a person comes back and wants to interact more constructively in the original post. Closing the original post and opening a new post explicitly signals to the community the standards of interaction, and starting off fresh in a more positive way lets us move on and forgive, rather than having the initial post's tone and ensuing conversation always hanging over the discussion as it develops.

A quick clarification question - if there were a PR to the CoC, would that require quorum + 80% SC vote like in #66 ?

And just a note to what you said above - I totally agree with you about the importance of a "reset" rather than a "block" on the conversation.
That said, I'd like to avoid implying that the person responding to the CoC violation is also responsible for re-engaging conversation in a different thread. It's enough mental and emotional energy dealing with negativity on the internet (and I definitely don't have the energy for it) so I'd like to separate out the expectations for "putting a stop to CoC violations and preventing conversations spiraling downward" vs. "following up to improve the behavior in the future". Does that make sense?

That said, I'd like to avoid implying that the person responding to the CoC violation is also responsible for re-engaging conversation in a different thread.

Very good point. Yes, example language walking that line would be much appreciated!

A quick clarification question - if there were a PR to the CoC, would that require quorum + 80% SC vote like in #66 ?

That's how I read the governance procedures in a strict sort of way.
Though since this is more of a helpful suggestion rather than a binding governance detail, I personally would have no objection to something like this being merged with less strict vote of approval.

Sounds good - I am happy to make a PR to propose some language for public forums etc, though I don't know that I have the energy to engage in a long debate process that needs to find 14 votes :-/

though I don't know that I have the energy to engage in a long debate process that needs to find 14 votes :-/

Again, since it is a suggestion rather than a binding procedure, I think you'll probably have an easier time than #66.

I support this & am likely to approve it quickly. I don't think it is likely that you will get much resistance, just inaction. I would support a less strict approval requirement.

ok cool, I'll try and whip something up next week


As a pigeon, if a valset update has insufficient fee, the transaction should be replace-by-fee

Background

Due to congestion on the target blockchain, validator set updates or any message sent by a pigeon may not have enough fees to be included in the block of the target chain. Today https://etherscan.io/tx/0xe035d3c5edf7fe371f4fec1b7ce5776813291f5b27a9694388b3cb485e4d9fb3 was over 10 hours unconfimred due to a low fee of 8gwei vs. minimum fee of 21 gwei.
Due to the blocked transactions, valset updates continue to be pending state as the last transaction is confirmed. This puts the security of the network at risk if a valset change has occurred.

Done when

[ ] valset updates that are more than one pending in a row will receive a replace_by_fee command from a pigeon to unblock the pending transaction with a higher fee. This replace_by_fee will only occur if a check on the previous transaction by a pigeon is shown as still pending on the same output account.

this has not been an issue for a while, closing for now


Add offset and window frame controls to preview windows

The Qt-based preview windows now have x and y parameters so that users
can force a particular offset. Also the "frameless" parameter allows
the window to appear without a surrounding frame. The previous
behaviour (with a frame) is preserved as the default.
An extra example of this and some extra documentation are also
provided.
Signed-off-by: David Plowman<EMAIL_ADDRESS>

I've removed the control to create "frameless" windows. I'm not sure it's useful, and it's easy to add if it turned out anyone wanted it. I've left the x/y window offsets as I think we probably should provide those (indeed the DrmPreview has them already).


Bump bootstrap-sass in response to CVE-2016-10735 and CVE-2019-8331

It's OK to bump bootstrap-sass from v3.3.6 to v3.4.1. I have checked against era and it works fine. ndr_ui in era is now at v2.0.2 (up-to-date).

@timgentry please don't forget to release it on RubyGems after merging the PR


JetPack 5.x rootfs slot A/B update

Working PoC for AGX Orin. please comment
Only rootfs update, bootloader update is missing.
Happy path only, rollback is not working yet.

Closed, replaced by https://github.com/mendersoftware/meta-mender-community/pull/394


Relocate invocation images

Also allow for images not to have digest fields set.
Fixes https://github.com/deislabs/duffle/issues/706

(The only things that changed in master since this PR was opened is the documentation PR, so I think it's safe to merge even if this is out of date.)

(The only things that changed in master since this PR was opened is the documentation PR, so I think it's safe to merge even if this is out of date.)

Agreed, but rebased so that everything is up to date.


Feature request: Leave edit mode using up or down arrow key

Replicate

Visit https://bossanova.uk/jexcel/examples
Double-click B2 (Classe B)
Change to Class
Press Down arrow.

Expected Results
The current cell is saved as Class and the active cell moves one cell down.
Actual Results
The up and down arrow keys have no effect.
Additional Details

Start Excel or OpenOffice Calc
Edit a cell.
Press the Down arrow key.

The editor leaves edit mode and moves the active cell one cell down.

This is already available in the last commit to the master repo.


sicky-sidebar causes repo sidebar to overlay readme

Description

I'm not sure what happened since this was working an hour ago but now the sidebar overlays the repo's readme.
How to replicate the issue + URL

Visit https://github.com/altdesktop/playerctl
Scroll

Extension version
23.8.3
Browser(s) used
Firefox

Duplicate of https://github.com/refined-github/refined-github/issues/6408

Perhaps sticky-sidebar should be disabled in Firefox. Lets had a supportsHasSelector filter to the include array


Documentation for GET Crop Stage Default Values endpoint

Added a path in swagger.json for crop-stage-parameter-values/:cropId endpoint (tried to keep it in line with PR by @zenkaeser  to avoid merge conflicts)
(related to issue #64 )

@kfazinic Have you verified that this is working?

@kfazinic Have you verified that this is working?

@senner008 It is, here's a screenshot :)


Add a configurable stabilisation delay before resolving alerts

Proposal
Currently, there is the for attribute in alerts to avoid spurious/flappy expressions triggering on a too small time period, but there is nothing to guard against the parallel problem of an alert resolving too quickly.
This can be a problem when you have data loss for a minute (so that a typical sum(rate(metric[1m])) > 0 query returns nothing), or you have some other retrigger issues on HA alertmanagers (maybe https://github.com/prometheus/alertmanager/issues/1546), or just in general use alerts on expressions that take some time to truly settle down.
All these cases could benefit from a grace period  / stabilisation delay such that alerts that momentarily seem fine from the expr POV, are not immediately resolved during active incidents, but given at least some configurable time to settle.
This would avoid confusing resolved messages being propagated through alertmanager and confusing oncallers.
Prior art; stabilizationWindowSeconds in Kubernetes HPAs.

We would move to have this.

Yes please. It was quite a surprise to see that I could define how long a rule needs to return true to alert, but not be able to define how long it needs to return false to be resolved.

What's left to do here?

keep_firing_for is not mentioned in the documentation at all.

At https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/#rule I see it under "The syntax for alerting rules is:"
Maybe you mean it should be on https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/.  (Which I would agree with).  Would you like to make a PR ?

Hello from the bug scrub.
@alexgreenbank to make the docs PR to add this.


Ability to have alternate versions of the same image to annotate with RoiPolygon

Why
In biomedical images there are usually different image modalities of the same object. For example different weightings in MRI for the same slice or different staining / immunofluorescence channels with different proteins in the same specimen in microscopy.
Just having the possibility to make a ROI selection based on one modality limits the use of label-studio.
Conditional Labeling with choices provides an Opportunity but cannot share the annotation across different images.
Solution
One possibility would be to give Annotation objects the ability to attach toName to a list of objects
<PolygonLabels name="label" toName=["image_x", "image_y", "image_z"]>
Or Group the images together, since only one can be displayed at every time anyway
  <View visibleWhen="choice-selected"
        whenTagName="image_modality" whenChoiceValue="Vx">
  	<Image name="image_x" group="image" value="$image_z" zoomControl="true" zoom="true"/>
  </View>
  <View visibleWhen="choice-selected"
        whenTagName="image_modality" whenChoiceValue="Vy">
  	<Image name="image_y" group="image" value="$image_y" zoomControl="true" zoom="true"/>
  </View>

<PolygonLabels name="label" toName=image>

@theudas We have discussed this issue with the team, I hope we implement it soon.

@hlomzik Have you any news?

@p-sodmann Sorry for a late answer, but we have implemented a multi-layer image approach finally:
https://github.com/heartexlabs/label-studio-frontend/pull/164
I think we will include it into release 0.9.1.
Feel free to reopen this issue if you have any problems.


New states for expanding and collapsing

I need extra states for Expanding and Collapsing, to react when the navigation bar is about to show and hide.
Or, another delegate method that alerts when states are about to change.
I can submit a MR for this - which approach would you prefer?

Hi @eliasbagley
A PR would be great.

@andreamazz turns out that's not quite the API I need. Basically, I have a bottom bar in my UI that I want to hide simultaneously when the navbar hides.
I think instead the API that I need is an optional delegate method that informs on the navbars current offset or % completion. This way I can hook into this API and if the user slowly drags, both top and bottom bars can start to gradually animate at the same time.
What do you think?

Sounds like a good addition, the percentage would be great. Can you hack it in a PR?

The percentage is now in master.


Extension Delete Itself

Steps to reproduce

Open app
Open Manhwa but can't because extension not install
Install extension
Read normally
Close the app
Reopen the app and extension deleted
Need to reinstall to proceed to read

https://github.com/user-attachments/assets/c9fa2bc8-fa5b-4383-9978-a552c59d297f
Expected behavior
Shouldn't delete by itslef whenever I close the app
Actual behavior
Extension deleted by itself every time app close.
Crash logs
N/A
Mihon version
0.17.0
Android version
Android 15
Device
Redmi K70
Other details
N/A
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.17.0.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Issues with Xiaomi devices:

Mihon encounters a variety of issues with MIUI/HyperOS due to Xiaomi's nonstandard practices.
Learn more here to reduce the chances of Mihon being killed in the background.

When using Mihon:

Use an alternative file manager when restoring your backup into Mihon, do not use MIUI's file manager.
In your Phone Settings > Developer Options, turn off system optimization/MIUI Optimization

If you don't see this setting, at the bottom of Developer Options, tap "Reset to default values" multiple times until it appears.

Extra step for HyperOS users:

This extra permission is only on certain regional versions of HyperOS, if you don't see this optional permission, ignore this portion of the message.
Go to Mihon app info (not in-app), and in the Permissions > Other Permissions, set "Access List of Installed Apps" to Always Allow.


[FLINK-13495][table-planner-blink] blink-planner should support varchar/char/decimal precision to connector

What is the purpose of the change
Now there is an exception when use DataTypes.DECIMAL(5, 2) to table source when use blink-planner.
Some conversions between DataType and TypeInfo loose precision information.
Verifying this change
TableSourceITCase
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@JingsongLi As we discussed offline, SinkCodeGeneratorcheckRowConverterValid also needs to be updated, otherwise only system default decimal(38, 18) is supported.

@JingsongLi As we discussed offline, SinkCodeGeneratorcheckRowConverterValid also needs to be updated, otherwise only system default decimal(38, 18) is supported.

@lirui-apache I updated PR, I add all new-api it cases to ensure everything running well. You can take a look to ensure hive connector running well.

@godfreyhe addressed your comments, please take a look again.
@wuchong can you take a look too?

@wuchong Thanks your advice, comment addressed now, What do you think?

Merging...

Commits have been merged via:
49202e2cf849dce7df3856ec9f40b1b5596a7ae9
ebf18db29b9b8480459e20b307e07980657e75e5
9dddae827e3f117b3527254701119c10909a3ac5
e2a8b95e4703e77a963cee5641bffe2e5b8a6f49
5b90b16b1d2d4dc48a0edfd12844ab1ada871586


s6-man-pages: sync with s6 v<IP_ADDRESS> documentation changes

Thanks for your contribution!
Please amend the commit message to simply say "Update to <IP_ADDRESS>", to match the style of previous commit messages for project-wide updates based on s6 version updates. Once that's done, we should be good to merge. :-)

Fixed.

Merged, thanks!


FIX: Add bottom alignment for the Visible/Hidden buttons on Helpful Links

Describe the bug
The Visible/Hidden buttons are not vertically aligned when there are Helpful Links that have different content lengths for the description.
Screenshots

To fix this, we should fix the height of the favicons (or the container that holds the image) so that we make sure that all of the cards are the same height.

Ah... good catch.


Improve docs

Add some documentation to the main module and create a test file of simple parser invocations.

I wasn't sure of the convention you wanted on comments having a leading/trailing ///. Let me know I'll make it uniform.

Ah thank you! 💕


Updated validatorjs to be able to use isBoolean

Thanks for the contribution. I would like to group this with https://github.com/ctavan/express-validator/pull/139 so it is only one minor version bump. Once that PR has been merged (should be tonight or tomorrow at the very latest), I'll get this one in and deploy to npm.

I couldn't automatically merge this PR, so I made the change here: 261337a8a479b806f66f2cb2a819c748a53568ec
This is now available in v2.12.0.


Creating an eHRAF 'society set' in D-PLACE

Rationale for including eHRAF as a society set in D-PLACE:
Both D-PLACE 1.0 and 2.0 were linked to eHRAF where possible. However, we felt eHRAF should be included in D-PLACE as a stand-alone 'society set' for a number of reasons:

eHRAF is an incredible resource (digitized, searchable ethnographies in which every paragraph has been tagged with one or more subjects as well as with a large amount of meta-data (focal year to which paragraph refers, author of paragraph, qualifications of author (anthropologist? missionary?) etc.), yet not all eHRAF societies are currently represented in D-PLACE

even when eHRAF societies are included in an existing D-PLACE dataset (e.g., the Ethnographic Atlas, or Binford Forager dataset), users cannot quickly 'eyeball' the spatial distribution of all eHRAF societies on the D-PLACE global map, or filter the main D-PLACE 'societies' table to look only at eHRAF societies

as with many cross-cultural datasets, eHRAF's 'cultural 'units' (cases) do not always correspond 1:1 with 'cultural units' in other datasets. For example, a single eHRAF case may include documents describing a number of closely related 'cultures', each of which has received its own ID and codes in datasets like the EA and SCCS. The advantage of eHRAF is that its "data" is simply raw text, i.e., cultural observations in HRAF are not reduced or summarized as "codes". By identifying which eHRAF texts (documents) refer to which subgroups, it is therefore possible to de-aggregate HRAF 'data' and to help users identify which texts are likely to best complement coded data for particular 'societies' in other D-PLACE datasets.

Steps taken to link eHRAF to D-PLACE
Much of the work linking HRAF to D-PLACE datasets was done by the HRAF team, and in publications such as Ember (2007). However, this early work did not (generally) attempt to de-aggregate HRAF cases that described multiple language or cultural groups. eHRAF cases also were not linked to glottocodes or to latitude/longitude coordinates, limiting the ease with which eHRAF could be combined with the linguistic phylogenies and environmental data that are corner stones of D-PLACE. To prepare eHRAF for inclusion in D-PLACE we thus:

split eHRAF cases corresponding to distinct D-PLACE societies; named these new "subcases" and modified their HRAF OWC IDs to include a suffix (e.g., AN01 became AN01a and AN01b), such that subcases could be referred to by their unique identifiers.

identified the language- (or dialect-) level glottocode(s) for each eHRAF case/subcase

identified latitude-longitude coordinates for each subcase, using a combination of Glottolog language coordinates, geographic coordinates for other D-PLACE societies, and web-based triangulation

identified, where possible, the HRAF document numbers that should be linked to a particular subcase (ongoing!)

decided on a set of eHRAF cases to exclude, until more information on the focal population/geographic location/years to which the descriptions refer can be collected. This includes many of eHRAF's 'North American Regional Ethnic Group cases (e.g., Italian Americans, Hmong Americans), with the exception of those that are strongly linked to both a language and geographic location (e.g., Sea Islanders; Appalachians).

We also excluded HRAF microfiche cases that are not on HRAF's "planned list" of cases to be digitized.

DATA COMING SOON...
References
Ember, C. 2007. Using the HRAF Collection of Ethnography in Conjunction with the Standard Cross-Cultural Sample and the Ethnographic Atlas. Cross-Cultural Research 41: 396.

@kirbykat  - what would this take to complete?

I estimate 2.5 days. It is a case of "the last 2%" of the work. It is very close to done.


Updating inventory on order not on shipping & configurable products that don't create individual products

Is your feature request related to a problem? Please describe.
When setting this up I've ran into these 2 major issues. Here is the use case:
I run Bagisto, but I make customized products and have limited inventory.
Here are the issues:

Updating the inventory count after the order is shipped allows for more orders than products I have in inventory to happen.

Customizing a product that doesn't create multiple variations of the same product. For example, let's say I have 10 units in inventory of an item that can be engraved with 1 of 5 different phrases after the order is placed. That would create 5 different products where I have to set the inventory individually, but I only have 10 items available total

Describe the solution you'd like

A setting in the admin to set what action updates the inventory. On Order Complete, On Shipping Etc.

Attributes that can be added to a single product that don't create multiple products.  Like a text input that allows a user to enter a note, or a select form that lets them select an option before they add it to cart.

Describe alternatives you've considered
No response
Additional context
No response

Disregard on #1. I've learned how it how it handles Pending Orders.


Support for requests with HTTP-method "OPTIONS"

Before a POST request can be sent, a "preflight" request in form of a OPTIONS request is made. So the API should allow OPTIONS requests as well. Otherwise the original POST request fails.
See https://www.html5rocks.com/en/tutorials/cors/ for reference.

Also see https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS:

Additionally, for HTTP request methods that can cause side-effects on server's data (in particular, for HTTP methods other than GET, or for POST usage with certain MIME types), the specification mandates that browsers "preflight" the request, soliciting supported methods from the server with an HTTP OPTIONS request method, and then, upon "approval" from the server, sending the actual request with the actual HTTP request method.

and https://spring.io/understanding/CORS#pre-flight-requests:

The preflight request is essentially asking the server if it would allow the DELETE request, without actually sending the DELETE request.

Workaround is to create a WebConfig to allow CORS explicitly in org.wickedsource.coderadar.security package. See the attached file:
WebConfig.java.txt

When I activate the CORS config from your example, I get 403 Errors when issuing an OPTIONS request. Let's talk about this some more, so I understand it correctly.

Is that still a thing?


OpenSSL accepts a certificate which has duplicate certificate policy IDs without any warning

Summary: As for a certificate, its certificate policy IDs should not be duplicate. However, OpenSSL accepts such a certificate.
Versions of OpenSSL: 1.0.1u, 1.0.2j, and 1.1.0b
Operating System: [Ubuntu v1604-LTS x64]
Steps to reproduce:  openssl verify -CAfile ca.pem 43.pem
Actual results: 43.pem: OK
Expected results: OpenSSL should reject such a certificate.
The attachement contains ca.pem and 43.pem.
Please rename the file "test cases.txt" as "test cases.zip" and extract it.
test cases.txt

In general it's pretty unreasonable to detect and reject duplicates in all the cases where the spec says that duplicates are not allowed. In particular, the extra work to reject duplicates requires extra code which means more room for vulnerabilities. Therefore I think bug reports like this should be closed as "works as intended" unless the duplicate values actually lead to a real security problem.

I am afriad I cannot agree with briansmith's comment "In particular, the extra work to reject duplicates requires extra code which means more room for vulnerabilities. "  Developers should make their programs more and more robust and bugs will be eliminated early or late. Threefore, in my opinion, OpenSSL should give warnings for this case at least. Not all bugs lead to security problems but bugs should be fixed once they are found.

Not all bugs lead to security problems but all bugs should be fixed once they are found.

Does RFC 6818 say that the receiver (verifier) of a certificate chain is required to reject duplicates? IIRC, it doesn't require that. It only requires that the producer to ensure there are no duplicates. The receiver/verifier isn't required to check that the producer did everything correctly.

We disagree.  Unless or until duplicate policy OID's are found to be a security flaw, there is nothing wrong with the current behavior.

@brainsmith  According to Sec 4..2.1.4 of RFC 5280, "A certificate policy OID MUST NOT appear more than once in a certificate policies extension". Here "MUST NOT" indicates absolute prohibitions of specifications.

Yes.  But we will do it anyway.  There are many real-world cases where specs are not followed.

@brainsmith According to Sec <IP_ADDRESS> of RFC 5280, "A certificate policy OID MUST NOT appear more than once in a certificate policies extension". Here "MUST NOT" indicates absolute prohibitions of specifications (RFC 2119).

Yes, one MUST NOT produce such a certificate. However, there is no requirement that one MUST reject such a certificate. It's a requirement on the producer, not the consumer.

@briansmith
Do producer and consumer rules have definitions? If not, how to understand them? Can rules involving "conforming CAs" or "CAs conforming ..." be regarded as producer rules. Are there other cases?

Do producer and consumer rules have definitions? If not, how to understand them?

The robustness principle: Be conservative in what you do, be liberal in what you accept from others, a.k.a Postel's Law. More information


Cannot install to Symfony 3

I've added to composer.json "hautelook/alice-bundle": "dev-master",, but it cannot install because it requires  nelmio/alice ~2.1 and it cannot work with Symfony 3.
Composer install log
  Problem 1
    - Installation request for hautelook/alice-bundle dev-master -> satisfiable by hautelook/alice-bundle[dev-master].
    - hautelook/alice-bundle dev-master requires nelmio/alice ~2.1 -> no matching package found.

Please change requirements in your dev-master to nelmio/alice dev-master - it supports Symfony 3.

Yes this bundle is not compatible yet with Symfony3. Sadly I have no time at the moment, maybe this weekend, but PR are welcomed. There should not be much to do to ensure the compatibility actually. Maybe @Soullivaneuh has more time?^^

Please change requirements in your dev-master to nelmio/alice dev-master - it supports Symfony 3.

Changing nelmio/alice to dev-master is not up to us. You can force requirement on your composer.json, or add a conflicts key.

Yes this bundle is not compatible yet with Symfony3.

What is missing?

Note sure, let's find out: https://github.com/hautelook/AliceBundle/pull/169/files

Found two BC break on LoadDataFixturesCommand and AbstractLoader. Will take a look.

AbstractLoader is already fixed.

For LoadDataFixturesCommand, this is more complicated because this class extends ContainerAware that will be removed in SF 3.0. The solution is to use trait, but we will drop php 5.3 support.

Not sure of what you mean LoadDataFixturesCommand extends Command rather

Well, I say the inverse of what I was thinking. AbstractLoader is problematic, not LoadDataFixturesCommand.
Will submit a PR right now. :+1:

For a moment I've made a fork and put in composer.json this forked repository
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/luchaninov/AliceBundle"
        }
    ],

I've changed only one line - https://github.com/luchaninov/AliceBundle/commit/2a8883d5f689d1dd7cc274c9f6b2c35e94f2e021
This may be not good solution but works for me - I've tested, my fixtures load good and I can use Symfony 3.0.

I insist, you have to put this require on your project composer.json file.
This fork works, but this is a painless way.

Example:
{
    "name": "my/project",
    "require": {
        "php": ">=5.4.0",
        "hautelook/alice-bundle": "~2.1"
    },
    "conflict": {
        "nelmio/alice": "<=2.1.1"
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

With this, nelmio/alice will be automaticaly updated to dev-master until a new stable release is coming.

By the way nelmio/alice just release the 2.1.2 ;)

BTW, 2.1.2 is out: https://github.com/nelmio/alice/releases/tag/2.1.2
So you should not have this problem anymore.
Closing.

    "conflict": {
        "nelmio/alice": "<=2.1.1"
    },

works great. Thanks!


@embed does not accept quoted identifier

What version of CUE are you using (cue version)?

$ cue version
cue version v0.10.0

go version go1.23.0
      -buildmode exe
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
cue.lang.version v0.10.0

Does this issue reproduce with the latest stable release?
yes (but it's an experimental feature)
What did you do?
env CUE_EXPERIMENT=embed
exec cue -e a.b eval
cmp stdout golden

-- a.cue --
@extern(embed)

package example

a: "b": _ @embed(file=c.txt)

-- c.txt --
c

-- golden --
"""
    c

    """

(test.testscript.txt)
What did you expect to see?
PASS
What did you see instead?
can only define functions for fields with identifier names, found "b"

It seems like this restriction in internal/core/runtime/extern.go has been in place for over a year, and isn't directly caused by the addition of the embed experiment:
name, isIdent, err := ast.LabelName(f.Label)
if err != nil || !isIdent {
	b, _ := format.Node(f.Label)
	errs = errors.Append(errs, errors.Newf(x.Pos(),
		"can only define functions for fields with identifier names, found %v", string(b)))
	return true
}


Unicode handling in to_latex. Needs encoding?

I can't seem to get this one to work and to_latex doesn't allow a user-specified encoding. I think this might need a look.
I have it in unicode, so try that way.
pd.DataFrame([[u'au\xdfgangen']]).to_latex('test.tex')

Nope. Ok, so let's encode it as a utf-8 string
pd.DataFrame([[u'au\xdfgangen']]).apply(lambda x : x.str.encode('utf-8')).to_latex('test.tex')

Nope. It looks like it's getting coerced back to unicode in formatter._to_str_columns() then tries to write it as ASCII...

I just encountered the same problem with pandas 0.17, so I guess the fix has not been included?

I never got around to submitting a pull request. Feel free to do so if you want! My fix above might work (would need to be tested), but it might be better to tie this in with how to_csv handles encodings (not sure, haven't looked).

Good point. On the same vein, I just noticed that the decimal option is available for to_csv but not for to_latex...
I'll have a look.

There’s a possibility that we’ll be able to replace some of the to_latex code with a Jinja template, similar to the Style stuff. So don’t spend too much time on it :)

On Nov 20, 2015, at 8:27 AM, Nicolas Bonnotte<EMAIL_ADDRESS>wrote:
Good point. On the same vein, I just noticed that the decimal option is available for to_csv but not for to_latex...
I'll have a look.
—
Reply to this email directly or view it on GitHub https://github.com/pydata/pandas/issues/7061#issuecomment-158414930.

to_csv uses csv.writer, with an adapter to intercept the output and convert it to utf-8. It would be possible to factorize code so that the same may be used for both to_csv and to_latex, but it would require a bit of work.
Considering this, and your previous remark, and the simplicity of your solution, I'll just implement the latter. But the encoding parameter of to_csv defaults to ascii with Python 2 and to utf-8 for Python 3, so I'll do that for to_latex.

@nbonnotte yes, this just requires a encoding argument. you may want to add a LatexFormatter (as a sub-class of DataFrameFormatter) as this will allow some re-factoring to be internally done later on.

closed by #11914


No USB PTP device found

I want to use ptpy to communicate with my Sequoia.  When I plug the sequoia into my Mac via USB and run the example, python ./trigger.py, I get a ptpy.ptp.PTPError:
E 439 ptpy.transports.usb[MainThread:__available_cameras:119] No USB PTP device found.
E 440 ptpy.transports.usb[MainThread:__available_cameras:119] No USB PTP device found.
Traceback (most recent call last):
  File "./trigger.py", line 4, in <module>
    camera = ptpy.PTPy()
  File "/Users/adelinehillier/anaconda3/lib/python3.6/site-packages/ptpy/__init__.py", line 133, in __new__
    instance = PTPy(device=device)
  File "/Users/adelinehillier/anaconda3/lib/python3.6/site-packages/ptpy/ptp.py", line 712, in __init__
    super(PTP, self).__init__(*args, **kwargs)
  File "/Users/adelinehillier/anaconda3/lib/python3.6/site-packages/ptpy/transports/usb.py", line 92, in __init__
    self.__acquire_camera(devs)
  File "/Users/adelinehillier/anaconda3/lib/python3.6/site-packages/ptpy/transports/usb.py", line 125, in __acquire_camera
    for _ in self.__available_cameras(devs):
  File "/Users/adelinehillier/anaconda3/lib/python3.6/site-packages/ptpy/transports/usb.py", line 120, in __available_cameras
    raise PTPError(message)
ptpy.ptp.PTPError: No USB PTP device found.

When I use a Raspberry Pi instead, I get the same error. In both cases, the sequoia is not recognized as a USB device under lsusb. Ideas?

For raspbian, if you're using the desktop environment it is likely that the camera auto-mounts as a drive.
This uses PTP behind the scenes and claims the device until it is unmounted.
If it looks like the camera is mounted on the file browser, unmount it and try again.
If that does not work, please show the output for lsusb -v -d 19cf: on your raspi with the camera connected (it lists all of Parrot's USB devices).
Be aware of the power requirements of the camera, it might be necessary to have a powered hub.

I am getting the same error on a Windows 10 machine and a oneplus 6T in PTP mode. The phone is connected and unlocked. I also installed the libusb-32 drivers using zadig installer.
Is there anything else that I am missing? Please help.

@ohbhatt, you will need to verify that the device in PTP/MTP mode has been assigned the libusb drivers. Android devices often change their USB PID depending on the mode they are in.
You can further check that the libusb driver is indeed in use through the Device Manager.

Dear Mr,@domenzain, First of all, I would like to express my gratitude towards you and the team for developing such APIs and utilities for the community.
After I installed the driver, the device shows as a serial device and not under cameras or as some other PTP/MTP device, I have replaced the drivers with all the options from zadig installer, but none of them seems to work. Can you tell what the device should look like in the device manager?

Hi @ohbhatt,
I've used the libUSBK driver in the past.
In that case the device should appear under "libusbK USB Devices", a category on the same level as keyboards.
In any case, you should make sure that it does not appear as a serial port.


Export/Import of application causes inline-errormessages to disapear

The inline error-messages are not shown inside plugin when application is exported and imported again.

Reason: Seems to be the data-template-id="xxxx"

Uses now same data-template-id as for other fields with inline error.


Radiation Suit too cheap

The radiation suit has the same durability and protection as iron armor, and allows players to use this as cheap armor in the early game

Well the radiation suit is not that easy to craft. You need to smelt resonating ore and then purify it. That is a lot more complicated then just iron

I'm on Deep Resonance 1.2.5 and you only need to smelt it, maybe you changed it in the last two versions but I didn't see anything on the changelog

Ah well that's possible. But even then. Resonating ore is a whole lot less common then iron ore. So why shouldn't it at least give same protection?

You end up getting a lot of it when you are diamond mining, and you are not using it for anything else in the early game.

But then you also end up getting a lot of iron ore as well. I don't see the problem really

If you have to purify it, that is fine for me.


[BUG] CRC fails on macOS 12.6.3 (image from Github Actions)

CRC fails on macOS 12.6.3.
General information
* OS: macOS 12.6.3 (Image from Github Actiions: https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md)
  * Hypervisor: vfkit
  * Did you run crc setup before starting it (Yes/No)? Yes
  * Running CRC on: Laptop
CRC version
# Put `crc version` output here
CRC version: 2.15.0+72256c3c
OpenShift version: 4.12.5
Podman version: 4.3.1```

## CRC status
```bash
# Put `crc status --log-level debug` output here
DEBU CRC version: 2.15.0+72256c3c
DEBU OpenShift version: 4.12.5
DEBU Podman version: 4.3.1
DEBU Running 'crc status'
CRC VM:          Running
OpenShift:       Unreachable (v4.12.5)
RAM Usage:       5.078GB of 9.399GB
Disk Usage:      14.06GB of 32.74GB (Inside the CRC VM)
Cache Usage:     36.82GB
Cache Directory: /Users/vncuser/.crc/cache

CRC config
# Put `crc config view` output here
- consent-telemetry                     : no
- pull-secret-file                      : /Users/vncuser/pull-secret

Host Operating System
# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows
ProductName:	macOS
ProductVersion:	12.6.3
BuildVersion:	21G419

Steps to reproduce
1.
  2.
  3.
  4.
Expected
Actual
Failed to update pull secret on the disk
Logs
Before gather the logs try following if that fix your issue
$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug  on https://gist.github.com/danielmenezesbr/13997ffd0e539dbdf73c7bea69c14483 and post the link in the issue.
Mac-1679343208412:~ vncuser$ ssh -i /Users/vncuser/.crc/machines/crc/id_ecdsa -p 2222<EMAIL_ADDRESS>Red Hat Enterprise Linux CoreOS 412.86.202302170236-0  Part of OpenShift 4.12, RHCOS is a Kubernetes native operating system  managed by the Machine Config Operator (`clusteroperator/machine-config`).
WARNING: Direct SSH access to machines is not recommended; instead,make configuration changes via `machineconfig` objects:  https://docs.openshift.com/container-platform/4.12/architecture/architecture-rhcos.html
---
[core@crc-9ltqk-master-0 ~]$ KUBE_CONFIG=/opt/kubeconfig kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?

Is this running on bare metal? Or is this a macOS VM where you are trying to run crc? This error from the end of the log is seen often in nested virtualization setups:
DEBU error: Temporary error: pull secret not updated to disk - sleeping 2s
DEBU retry loop: attempt 94
DEBU Running SSH command: <hidden>
DEBU SSH command succeeded
DEBU error: Temporary error: pull secret not updated to disk - sleeping 2s
DEBU RetryAfter timeout after 95 tries
Failed to update pull secret on the disk: Temporary error: pull secret not updated to disk (x95)
Mac-1679343208412:~ vncuser$

Not sure if this is an environment with nested virtualization. The environment is the same as the CRC uses in Github Actions.
@cfergeau, do you know if CRC is ready to use after "crc start" used in CRC build for MacOS?

do you know if CRC is ready to use after "crc start" used in CRC build for MacOS?

Note that in this link/action, the podman preset/bundle is used, not the openshift/okd preset. The error message about pull secret can only occur with an openshift cluster. If you are trying to run a full openshift cluster from a github action, I'd guess you'll need your own powerful runner?


Travis changes to begin testing.

Uncomment the testing part in travis file.

Sorry, it just passed my test. See #11

The PR addresses the testing part. This was commented in the PR #8, though there is nothing much to test when additional functionality is added we do not need to re edit again. And also #11 adds a badge  and does not trigger the build of the package and thereby testing the package.

Also let us stick to the version 0.4, allowing the build on 0.5 to fail.

Travis works ! Squashing and merging ...

Sure. Move on to v0.5 next month.

Okay, so can the branched be deleted and the PR's closed ? So many things happening in parallel. :confused:

@sahmed95 once travis CI passes and it is reviewed, it is ready to be merged and once merged we can delete the branch as the branch is specific to the user creating the PR. PR's merged automatically tagged as closed.

Okay !


Enhance RIGHT DB actions for clusters where user has limited rights but DB prepared for mirroring

In case if user has limited DB level permissions - like can work with tables but can't change DB attributes - some actions/statements needs to be configurable for successful mirroring:

Skip the ALTER DB [MANAGED]LOCATION statement(s) if it would be the same as what already set for the existing DB or if the user sets a spec session option
Skip the ALTER DB OWNER statement is user sets a spec session option

The DB location change could cause issues if altering location is skipped and tables would be mirrored to new location, but then this could be more complex like:

if location is changed in a way that old/new managed/external location would switch that could cause conflicts
mirroring a set of tables from one source into a DB where other set of tables are mirrored from other source with mixed locations could cause conflicts

In these cases I think the user needs to set up proper 'relocation' configuration rather expect hms-mirror to handle automatic mapping. The only auto-mapping could be changing managed table locations from custom locations to the strict MANAGEDLOCATION in newer hive versions


speedtest --list result with ping

HI, great work!
Would it be possible to add the ping time in the --list result?
Additionally would it be possible to sort list by ping?
Only for stats..
Thank you!

I don't have any plans on adding that.
From a list, I see 5921 servers.  To get a ping average, that is 3 requests per server, which would result in 17763 HTTP requests.  Those happen serially, and would take a really long time.
We already ping the 5 closest servers, and pick the one with the lowest ping.


Unable to launch new Browser after installing Python 26

Originally submitted to Google Code by infant.gerald on 31 Mar 2009

Please find the attached file and Error Logs. I am getting this consistent
error on all the New Machines I have been installing of late.
Issue 273 was raised under RobotFramework and Got closed stating it
belonged to Selenium Queue
I am completely blocked and any help will greatly help me in proceeding
further
Installation Steps:

Install JRE ( Java Runtime Environment )
http://java.com/en/download/manual.jsp
Recommended Installation path – DEFAULT
Install Python 2.6 available at
http://www.python.org/download/releases/
Recommended Installation path - DEFAULT
Install latest Robotframework installers available at
https://code.google.com/p/robotframework/downloads/list
Current Latest Version: robotframework-2.0.4.win32.exe
Install latest Selenium Library for RobotFramework available at
https://code.google.com/p/robotframework-seleniumlibrary/downloads/list
Current Latest Version: robotframework-seleniumlibrary-2.1.2.win32.exe
Install Python Win 32 Extensions for Excel operations
http://sourceforge.net/project/showfiles.php?
group_id=78018&package_id=79063&release_id=661475

Originally submitted to Google Code by infant.gerald on 7 Apr 2009

Please close this bug as the mistake was opening URL
www.irctc.co.in - fails because of missing Http://
http://www.irctc.co.in passes


Show the creation time in the ORT runs table

Currently, the ORT runs table only shows the date when a run was created. Also show the time, because the date alone is not sufficient information when many runs were started on the same day.

Somewhat related, after reading though this I wonder whether we should stop using new Date() and rather use a library that could also be used to replace our own calculateDuration(), which I'd like to show days as well. @mmurto any opinion?

I think we're relatively safe with the native Date as all timestamps come from the database and I'd assume they're well and consistently formatted. I've used date-fns for more advanced stuff, it's good.
Where did you run to showing days? Isn't it currently used for run durations, I'd like to believe they're more in the minutes and hours range. :D

Where did you run to showing days?

Check global run ID 6 in our instance 😉