Bump version to 2.12.0

We have a few changes since the last release (v2.11.1), so I thought it might be time for a new release.

Fix incorrect path suggested by RSpec/FilePath cop when second argument contains spaces.
Fix autocorrect for EmptyLineSeparation.
Add new RSpec/Capybara/SpecificMatcher cop.
Fixed false offense detection in FactoryBot/CreateList when a n.times block is including method calls in the factory create arguments.
Fix error in RSpec/RSpec/FactoryBot/CreateList cop for empty block.
Update RSpec/MultipleExpectations cop documentation with examples of aggregate_failures use.
Declare autocorrect as unsafe for RSpec/VerifiedDoubleReference.

It's a bit late on my side to make good judgements, but I have a feeling that #1308 needs to be re-discussed.
WDYT if we release without it?

👍🏼 Let’s chat in #1308, and feel free to put a “request changes” status on this PR.

Yep, let’s add that pr as well.


Support an optional user destination.

Allow the user to specify the desired final stop along the way
instead of forcing the train's own final stop. The output will
show the ETA and distance relative to the stop where the user
needs to get off. Even DB realized that this interesting and offers this
feature in the web UI.

Thanks @pkern!


Add Spring Data Redis 2.6.0 support

Done in https://github.com/redisson/redisson/commit/3e4c12cfe4255a944ecb28a46c9d716b0312dacc


Multiple swagger.json

Hello,
Is it possible to generate multiple swagger.json and serve them.
Exemple :
module1.swagger.json
module2.swagger.json
For a big api it would be handy to filter it by modules or something else.
Thanks,
Matthieu

Hello @MatthieuFereyre,
Today it's not possible to generate multiple swagger.json. What do you propose ? Can you give us an example ?

Hi @olivierlsc , same need here. We have a service with multiple modules where each module has its own purpose. One module is for internal administration, another one is specialized for our partners. We would like to have swagger documentation for the internal endpoints but don't want to expose them to our partners. Also, every partner has its own set of endpoints, so every partner needs to have different documentation.


add simple glider data example

Starting to address  #58 with an example of QC for a glider dataset. This notebook can be expanded to include qc of more variables, and the process of creating qc variables for the original glider dataset

Tests are failing due to flake8 migration to GitHub. These checks should be green once #95 is merged

Tests are failing due to flake8 migration to GitHub. These checks should be green once #95 is merged

Do you want to rebase this to make the tests pass?

I'm not sure what to do with the codespell failure. Should the notebook be restarted with cleared output when committed?

I've cleared the notebook output. Hopefully all clear now. Is the notebook itself ok as example? Do you want more detail or explanation?

@callumrollo let's avoid committing the file to the repo. I'll add it as an asset for you and send the URL in a bit. Hold on...

@callumrollo let's avoid committing the netCDF file to the repo. I'll add it as an asset for you and send the URL in a bit. Hold on...

Here you go: https://github.com/ioos/ioos_qc/releases/download/2.1.0/nrt_SEA067_M37.nc
It is versioned but I used the current release for it. Ideally, in the future, we should add it to future release via a draft release, to obtain the URLs, before making an official release.
PS: You can use pooch to manage the asset download like:
import pooch

url = f"https://github.com/ioos/ioos_qc/releases/download"
version = "2.1.0"
fname = "nrt_SEA067_M37.nc"

download = pooch.retrieve(
    url=f"{url}/{version}/{fname}",
    known_hash="sha256:06e8a79cc17a2d55bb32dbfdc85f9922c1a1cc14726df004ae971125f91b27ac",
)

downloading with pooch now

@ocefpaf any further changes you'd like to see before we can merge?

Not on my side. @kwilcox is this OK to go?

Great! I'm h for it to be merged, I don't have the rights on this repo


Specifying a person to track in a multi person video

I am using human pose tracking in Python, Windows 11, with a video that contains multiple people. I would like to track the pose of the central person only, however it tracks alternate people to the side instead. How do I specify which person to track or alternatively view just the centre of a video? I would like to do this without cropping the video outside of my Program. My program is based off the provided Mediapipe Pose Python script for the webcam/video. Cheers.

Hi @db19891 ,
Could you provide any reference video w.r.t above issue.

I couldn't get a video, but here is an image of my problem. I would like to track the powerlifter, not the spotter.

Model is not trained to select any specific person at present. We don’t have any video cropping calculator with which it can be built. we do consider it as a feature and share it with internal team.


Metadata API: add _Delegator.get_delegate_signing_status()

_Delegator.verify_delegate provides a binary answer for whether a delegated role has enough valid signatures to meet the threshold of keys defined by its delegator or not.
While this is sufficient for client validation, TUF applications might also be interested in more granular information, e.g. when implementing a distributed signing feature for TUF metadata, so they can tell users how many signatures by what keys are still missing.
Interesting information would be:

set of valid signatures
set of invalid signatures (this would require validating all signatures; verify_threshold only verifies until threshold is met)
optional: eligible keys, used keys, remaining keys (maybe out of scope)

Given that threshold verification is such a crucial part of the Metadata API and can be done wrong so easily, adding a new public function --  e.g. _Delegator.get_delegate_signing_status() -- to Metadata API seems like a good idea.

Use cases:

RSTUF: https://github.com/repository-service-tuf/repository-service-tuf-worker/issues/367 (cc @MVrachev, @kairoaraujo)
tuf-on-ci: ?? (cc @jku)

For tuf-on-ci use case I want:

list of keys that have signed correctly
list of keys that have not signed (I don't care if the sig is missing or incorrect)
has threshold been reached

Things that I don't care that much about:

the actual signatures (easy to lookup with keys if needed)
threshold (easy to lookup)
number of good sigs (easy to calculate)

One additional related use case I saw in both tuf-on-ci and RSTUF:

is a given signature valid for delegate according to delegator?

It's easy enough to implement in the application. I'm bringing it up here, because, if delegate_signing_status returns the valid signatures, it could be used for that purpose. OTOH, the validity of a given signature might be interesting by itself, regardless of other signatures. So maybe we should treat this as separate feature. Any thoughts?

Re name: I'm a bit unhappy with the verb/noun ambiguity of delegate. delegate_signing_status, to me, sounds like the activity of delegating the signing status, for whatever that means. But I'm okay, if we clarify this in the docstring.

It could be I just don't remember the specific location but I think tuf-on-ci question is (or should be) "has this signing key signed this delegated role?"

You are right, I mis-skimmed the code I was referring to. nvm

I think Jussi's proposal is complete.
Returning "invalid signatures" as well does not make a lot of sense, because the signatures could be invalid according to one delegator, but valid according to another, which is not unlikely in the case of a root update. So, to get the desired information -- "does the metadata have invalid signatures?" -- we'd need to do set operations on multiple results anyway, and this can be done with the existing fields too. E.g. root update
stat_old = old_root.delegate_signing_status("root", new_root)
stat_new = new_root.delegate_signing_status("root", new_root)

has_invalid_sigs = len(metadata.signatures) > len(stat_old.signed_keys) + len(stat_new.signed_keys)  # assume signed_keys is a set set
invalid_sigs = metadata.signatures - (stat_old.signed_keys | stat_new.signed_keys)

Yes, I agree with what you said.
I think I like the unstated assumption in your examples that the key lists are actually sets -- then you can do unions more easily, and I can see that would be useful.
The "math" in your code has some issues but I don't think they're very important:

has_invalid_sigs = len(metadata.signatures) > (len(stat_old.signed_keys) + len(stat_new.signed_keys))  # assume signed_keys is a set of keyids

That's not right (keys might be duplicate and anyway thresholds may be different). Like you said, for root you'd just have to duplicate whatever you do normally to find invalid sigs (whatever "invalid" means in this context): you'd then have two separate lists of "invalid sigs"... unsure what you would want to do with them.
I think there are more useful questions and they seem fairly easy to answer:

"which root keys have not yet signed correctly, but could still do so":unsigned_keys = stat_old.unsigned_keys | stat_new.unsigned_keys

"Which root keys may need to act for the metadata to become verified":missing_keys = set()
if not stat_old.verified:
    missing_keys |= stat_old.unsigned_keys
if not stat_new.verified:
    missing_keys |= stat_new.unsigned_keys

On the idea of using set instead of list for Keys: this does not currently work as Key is not hashable. We could easily make them hashable though

Cross-posting from slack, by "invalid signature" I meant:

there is no authorized keyid for a signature's keyid in any eligible delegator, or
there is an authorized keyid but no public key in the corresponding keystore, or
there is an authorized keyid and a public key but verification fails cryptographically

I edited my "math" in the comment above to correctly support these checks

On the idea of using set instead of list for Keys: this does not currently work as Key is not hashable. We could easily make them hashable though

Or maybe not: hashable objects are not supposed to be mutable (the hash should be a constant for the lifetime of the object). Strictly speaking that's not true for Keys even if our keys almost never mutate.
Or we could just say the Keys are immutable enough so that we can put them in this short lived set :shrug:

Or we could just say the Keys are immutable enough so that we can put them in this short lived set 🤷

Hm, I suppose it's okay, if we document the caveat. Alternatively, we could implement a custom key container, which provides all the desired set operations for contained Key objects. And which clearly documents that mutating the items breaks the container.

I think  returning set of keyids is ok and fits the rest of the API.
If someone wants to take the WIP commit above and polish, I'm totally fine with that.
As a note on the implementation, I originally included threshold in the result but decided against that: A useful operation is to "union" two VerificationResults (in the root case) and I think providing that in the library might be good... Two thresholds however cannot be "unioned".


aggregate querey, and aggregate

Coverage decreased (-0.005%) to 42.207% when pulling ea709ad106d420d48f459fb8d0b2018ad7108c9b on buman56:python-bindings into b205ed9c7415293f004826357c3183bc3564dbc9 on locationtech:python-bindings.

Coverage decreased (-0.005%) to 42.207% when pulling ea709ad106d420d48f459fb8d0b2018ad7108c9b on buman56:python-bindings into b205ed9c7415293f004826357c3183bc3564dbc9 on locationtech:python-bindings.


This plug-in cannot pop-up prompt words in sd1.5.2

Help me plz

I will need more info, everything related to tag autocomplete seems fine in your screenshot.
Open the browser console (CTRL-SHIFT-I) and tell me if there are any errors.

Is that what it looks like? It looks like a lot of mistakes, but I can't understand them

是这样的吗？看起来错误很多，但是看不懂

This pops up every time I click on a link

Yes, that was what I was looking for.
ERR_BLOCKED_BY_CLIENT usually means that the browser or a browser extension (adblocker, firewall, etc.) has prevented the request.
Are you using the "Internet Download Manager" software? I think that's what the last window is from. Another user previously had an issue where its "Advanced browser integration" feature was blocking the file loads (see the last few comments in #135).

是的，这就是我一直在寻找的。 ERR_BLOCKED_BY_CLIENT 通常表示浏览器或浏览器扩展（广告拦截器、防火墙等）已阻止该请求。 您是否使用“Internet 下载管理器”软件？我想这就是最后一个窗口的来源。另一个用户之前遇到过一个问题，其“高级浏览器集成”功能阻止了文件加载（请参阅#135中的最后几条评论）。

Thank you very much, I disable the idm browser plug-in can be!

Glad to see that that was it.
Unrelated question, what are you using as your translation settings? The content of the square brackets [] should normally not be the post count like it is in your case.

this

You have currently selected your normal tag file here, but this should be a different file containing only translations, else it will not work as intended. If you already have one downloaded you need to select it there, or else look for one (for example https://github.com/sgmklp/tag-for-autocompletion-with-translation, https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/discussions/23, or those linked in https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/216#issue-1838667191).
Then it should look more like this

Similarly, don't use danbooru.csv here.

That is only for small sets like the included "extra-quality-tags.csv". It will hinder functionality to use the main file there.


ENH: Robust Format Sniffers

Improvement Description
Based on recent discussion, it seems useful to make sniffing more robust, including the ability to raise specific errors when a sniffer fails. Also there was some talk around conditional logic within a sniffer ("if this then do this"), to possibly handle more generic directory formats for importing. This would impact end users and plugin developers.

This doesn't seem like it's going to happen


Fix server compiler test after<EMAIL_ADDRESS>update

We have failed server tests after changes in babylon. It was released in v6.11.5 several hours ago
/cc @inikulin

It seems we have problems with some functional tests in the OSX + Edge task:
[API] Selector
1) Should provide input-specific properties in element snapshots
2) Should provide `innerText` property in element snapshots
3) Should filter results with "text" options

They are failed three times in a row.
I propose to merge this PR (to fix server tests), but I'll start to investigate this tests right now
/cc @inikulin


How to use the shields button?

I don't get how to properly use the shields button. I can use this one for users, but how to do it for projects?

Projects were called "teams" until recently. Is Shields still perhaps using the old nomenclature?
https://img.shields.io/gratipay/team/XenForo-Threema-Gateway.svg

Projects were called "teams" until recently.

https://gratipay.news/from-teams-to-projects-45c46718507b, btw

Mhh, so is it intended that anonymous is shown for projects which have not received any money yet. Or why are they "anonymous"?

Dunno, I just checked the Shields homepage and teams is what they advertise.

We'll have to dig deeper into the API calls that Shields is making to Gratipay, and what those calls are returning. You motivated to do that, @rugk? :-)

Uh, not really, no. If it does not work I use a text link for now… 😉

If you're receiving $0.00, the shield defaults to "anonymous"
https://img.shields.io/gratipay/team/XenForo-Threema-Gateway.svg works is the right url.
I tipped you a penny, it shows up correctly (markdown below, not a static image):

We good here, @rugk?

@mattbk Nice!
And thanks for the penny. 😃

This seems like a bug with how public.json is being read by Shields.

I think it would be good if this can be fixed in Shields.io. Then this issue can be closed IMHO…

Looks like this has been fixed.


Block handlers affect block scanning too early

When you have two data sources (or more) in a subgraph, one with an earlier start block and one with a later start block and a block handler, like below:
dataSources:
  - source:
      startBlock: 1
      mapping:
        eventHandlers:
          ...
  - source:
      startBlock: 100
      mapping:
        blockHandlers:
          - handler: handleBlock

then the block scanning takes the block handler into account for blocks #1 - #99 already. This slows indexing of historic blocks down significantly. This is because we take the minimum start block of all data sources and then scan blocks taking all filters into account. We never call handleBlock for blocks #1 - #99 though, so the indexing execution is correct.
A more efficient block scanning algorithm would divide the block scanning into ranges where different filters apply. In the above case, this would be:

skip blocks [#0]
scan blocks #1 - #99 with just the filters from the first data source
scan blocks #100 onward with the filters from both data sources

While this really is an issue, the reason scanning for block triggers is slow in the first place is because we don't have a good way of getting a block by number from the DB. We may be able to leverage the block explorer which will land in #1383 to do that and speed up the scan.

Considering that we've decided to avoid restarting the block stream now that we have the firehose, it doesn't seem likely that we will pursue this.


test resource pool ancestry with relationship changes

https://github.com/ManageIQ/manageiq-schema/pull/510
https://github.com/ManageIQ/manageiq/pull/20564

can you add on ui-classic, and miq-providers-vmware ?
pretty sure both of those access the relationships portion of resource pools


webpack build overwrites existing files, invalidating long-term cache chunks

I figured out that, when doing a webpack build that this would overwrite existing files, even though the file has exactly the same contents (and hash).
This actually leads to a major issue – it invalidates the cache and my users get a GET 200 and fetch the whole thing again, even though the file is the same.
When I temporarily move my vendor.[md5hash].js file out of the build dir, run another webpack build, and then moved it back into the build dir (overwriting it again), I get the expected GET 304 from the file.
I guess because of the header Last-Modified.
In any case, I think we could improve a lot of stuff here by just skipping the whole build for files, when we can detect that the last output is the same.
Since webpack can keep records and stats for each build, why not check the hash of all files related to the chunk, detect a change, and then decide on what to skip for the build. This could improve production build-times a lot.

This is something that is outside of webpack's scope.
If you're using hashing for file names, then what you're actually trying to do is prevent the user from sending a lot of GET 304 requests. If your users are sending a lot of those for resources that you expect the user to pull from their local cache, then you set your server response headers incorrectly.
When you have hashed file names, you want the user to not send web requests, instead, pulling responses from cache, via GET 200 (from cache). This can be achieved by making sure your server responses include a header such as Cache-Control: max-age=31536000
Let me see if I understand your proposal correctly: you would like webpack to read the previous state of the files that it is considering bundling, and then compare that state to the current state of the files before bundling to see if bundling (a costly process) is even required.
Keeping this sort of state in-between bundles is outside of the library's scope however. You could however do this yourself using the webpack node.js api within a general build script to read/write states of files before and after bundling, to see if bundling is actually necessary. Here, I'm assuming that webpack provides a way for you to easily compare states of the files that it's about to bundle.

Actually, I've been taking a look at your proposal further, and here are 2 links that may be of use:
https://github.com/webpack/webpack/issues/250 (your proposal is an open issue)
https://github.com/markfinger/webpack-build (someone tried their hand @ an in-disk cache)


Legacy Slack API

The package github.com/bluele/slack uses a legacy Slack API, for example, calling the channels.list method returns a warning:

[WARN] This method is deprecated and is scheduled to cease functioning on 2021-02-24. Please use conversations.list or users.conversations instead. Learn more: https://api.slack.com/changelog/2020-01-deprecating-antecedents-to-the-conversations-api.

Slack App tokens don't work at all with this method...
I think it's time to move to modern libraries, for example github.com/slack-go/slack, before the utility stops working...

@bcicen It stopped working today.

So, does this mean it is totally dead?  Or is there a plan to fix it?

@frankcrawford Yes, it looks dead to me. I started to work on a simple CLI wrapper of https://github.com/slack-go/slack.


Should pull packages from bioconductor as well

http://bioconductor.org/docs/install/

hi guys: mind pointing me to the code that yanks from cran?  i will try to yank in bioconductor ... would be useful for me to keep track of which packages i am using.  cheers,

The relevant files are https://github.com/hadley/crantastic/blob/master/lib/cran.rb and https://github.com/hadley/crantastic/blob/master/lib/crantastic.rb , they are used from the rake task scripts locaed in lib/tasks


Fix bad uglify - add new update command

@keybase/react-hackers this updates webpack-ugilfy to the newest best which uses ugilfy-es. I did a local prod build of the RN js and a local package of desktop and it seems to build fine. I say we merge this and kick off builds to see if this resolves this all.
Additionally I added a new command yarn run modules which will do an install w/o generating updates to yarn.lock. The idea being all non-FE teams would use this instead of yarn

Maybe update the readme so non-FE knows what to do?

Or make


iOS - App get crashed on iPad during Sign In flow

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.24-3
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Precondition: user should be Sign In

Open app
Write a private domain email (expensifail)
Tap on Sign In
Write a magic code from email

Expected Result:
User should be successfully signed in
Actual Result:
App get crashed. If user kill and launch app the app will be crashed again.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native -IPad
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/0085d319-684a-4b60-8586-faffcbf018be
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
App crashes on ipad
What is the root cause of that problem?
this line throws cannot access findindex of undefined
https://github.com/Expensify/App/blob/82b76c1a36cf1a01b00c14510a5812a591e7f2fd/src/libs/Navigation/FreezeWrapper.tsx#L20-L24
What changes do you think we should make in order to solve the problem?
we need to safely access it

@abzokhattab are you able to find offending PR?
There was similar crash in the past where TS check didn't catch it - #32515. Fixed in #32525

@situchan  my proposal is not working so i removed .. if i got a clue on what is happening will post here

Based on a simulator build, the same crash happens on production so I don't think this is a blocker, but it would be great to confirm that

This has been resolved on staging with https://github.com/Expensify/App/pull/34396, once that's on production we'll be able to close

No payment needed here, I'm going to close it out.


Docs  translated into Chinese

The document is translated into simplified Chinese

          1 Warning

:warning:
Big PR, try to keep changes smaller if you can

  Generated by :no_entry_sign: Danger

Codecov Report

Merging #1321 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1321   +/-   ##
======================================
  Coverage      83%     83%
======================================
  Files          24      24
  Lines         753     753
======================================
  Hits          625     625
  Misses        128     128

Continue to review full report at Codecov.

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

Hey @lovesomeone. Thank you so much for this PR. This is a great amount of work and we really appreciate that!
However, I'm not sure that this translation belongs here. The amount of work we would have to do to maintain both documentations is quite big (especially if you look at how many open documentation issues are there, meaning there are not many people that want to take care of that).
I suggest that you can create your repository with Moya documentation in Chinese and we will point to that from our Readme. What do you think?
Also, I'm interested in other @Moya/contributors opinion.

@lovesomeone this is amazing – thanks so much!
I don't think it's too burdensome to keep the docs in this repo; our English docs drift behind our implementation and our contributors keep them up to date, I expect our Chinese-speaking contributors would be available to help too. Either way is fine 😄

I teared up when I saw this PR this morning 🤣 I think that having Chinese documentation is great! Anything that makes Moya more accessible to different developers is fine by me.
In regards to maintenance, it may be good to note that the Chinese documentation may not always be up to date and I think that our English documentation should only be a blocker for a breaking change.
Like Ash said, I'm sure our Chinese-speaking contributors will jump in and join the effort to keep things up to date.
@Moya/contributors and watchers: If you speak Chinese give this comment a 👍 so we can see how many contributors are fluent in the language 😃

@sunshinejr. I think it's ok to have it in my repository first 。 if it help  then we can make merge。

@sunshinejr. I think it's ok to have it in my repository first 。 if it help then we can make merge
@all    I really love this project and thank you very much for all of  your contribution。 Hope Moya becomes  better 。
By the way ， when I learn this project  ，I  think the documents are not well organized，especially   docs /README.md

I'm a Chinese. English documents always took me longer time to read and sometimes, because of my poor English, even make me misunderstand something. So I think having the Chinese documents is helpful to make this project more accessible to Chinese-speaking developers and, in turn,  could attract more contributors to improve this project including keep the Chinese documents up-to-date.

This is 🥇

Okay, okay. Maybe my first take on this one was a bit premature - Chinese docs being a little bit behind  might not be a big problem if we state so. Let's just take a look at the content there and merge it if it's ready then 👍

It looks like a few of the docs are incomplete – let's merge this, and then open an issue about how to indicate that they might be incomplete or behind, but we would appreciate any help.

Thanks a lot for contributing to Moya! I've invited you to join the Moya GitHub organization – no pressure to accept! If you'd like more information on what that means, check out our contributor guidelines and feel free to reach out with any questions.

I'm glad to be invited。Yes  ,I like this project . I‘m very happy that I can be one of contributors！


Bad inference for typeclasses

type carrier = Type -> Type

// lawless functor
type t (c: carrier) =
  #a:Type -> #b:Type -> (a -> b) -> c a -> c b

let map (#c: carrier) [|map: t c|]: t c = map

(* fails with
  `(Error 189) Expected expression of type "t c";
   got expression "map" of type
   "(#[FStar.Tactics.Typeclasses.tcresolve ()] map: t c) -> Prims.Tot (t c)"` *)
// let ( <$> ) #c [|t c|]: t c = map

(* fails with
  `(Error 120) Expected a term with 2 implicit arguments,
  but Control.Map.map has only 1` *)
let ( <$> ) #c [|t c|]: t c = map #c

At least part of the issue is independent of typeclasses, and related to unfolding types when computing the amount of implicits they have:
type q = #a:Type -> a -> a

let f : #b:Type -> q = fun #b #a x -> x

let g : #b:Type -> #a:Type -> a -> a = f

g fails with Expected a term with 2 implicit arguments, but A.f has only 1.

Oh, actually this was already addresed in #807, where I made it unfold, but did not think of recursing underneath the arrow's RHS! Trying a fix in CI now.

In master now, thanks a lot for reporting!


Added clearing of the reason

This feature was covered by the feature test, but what wasn't covered is
the textarea wasn't being cleared after the users chose the 'Yes'
option.
Added the feature that clears the textarea and the test.

There is potential to use https://github.com/crismali/magic_lamp#magic-lamp to generate actual views rather than static html.  That is a refactoring task however, this can be merged and a separate ticket created for improvements.


Exact Search

Hi. I couldn't find option for exact search. Is there any implementation for that?

You implement the search on your backend.  We just show the results.  In the examples we do the search client side because for a while there was no server in the examples.  But you should be doing it on your side and sending the results you want back in the ajax request.


Move typedefs used in cmd/tlm to the *_msg.h file

Is your feature request related to a problem? Please describe.
CFE_ES_AppInfo_t and CFE_ES_MemHandle_t are defined in cfe_es.h, but used in telemetry (cfe_es_msg.h).  All the typedefs used in telemetry should be defined in the *_msg.h file.
Describe the solution you'd like
Move CFE_ES_AppInfo_t and CFE_ES_MemHandle_t into cfe_es_msg.h
Note CFE_ES_TaskInfo_t is not used in cmd/tlm.
Describe alternatives you've considered
None
Additional context
Related to #899
Requester Info
Jacob Hageman - NASA/GSFC

I'd like to move this definition after review/merge of #917, as this changes CFE_ES_MemHandle_t.
Once decided (along with #913) then I suggest that the handle/resourceid types go into cfe_es_extern_typedefs.h and the structures go into cfe_es_msg.h.


Is it possible to use this with older stand alone versions of Photoshop, like CS6?

Is it possible to use this with older stand alone versions of Photoshop, like CS6?

@rhst1 Did you test it?

No. Didn't see how I could since the server code requires a password for the remote connection to online Photoshop.

I have no sure if it works for online photoshop.
The password required is to be used with photoshop remote access feature, see how to set up here

Thank you!


Api URL for deleting a group of files was incorrect

Description

Motivation and Context
The example has /v1/storage/groups/{group_id} but the actual URL displayed was /v1/storage/files/{group_id}
Types of changes

[x] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[x] I have read the contributing document.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.

Moved to https://github.com/saucelabs/sauce-docs/pull/1122 due to saucectl failure


fix typo in type definition

Fixes a typo in documentation

Hi @michaelchiche, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks for the contribution and sorry for the delay.


Hadoop 16890: Change in expiry calculation for MSI token provider

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
21m 12s
trunk passed

+1 :green_heart:
compile
0m 27s
trunk passed

+1 :green_heart:
checkstyle
0m 18s
trunk passed

+1 :green_heart:
mvnsite
0m 30s
trunk passed

+1 :green_heart:
shadedclient
15m 57s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 21s
trunk passed

+0 :ok:
spotbugs
0m 49s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 48s
trunk passed

-0 :warning:
patch
1m  5s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s
the patch passed

+1 :green_heart:
compile
0m 21s
the patch passed

+1 :green_heart:
javac
0m 21s
the patch passed

-0 :warning:
checkstyle
0m 14s
hadoop-tools/hadoop-azure: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
0m 24s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 17s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 19s
the patch passed

+1 :green_heart:
findbugs
0m 52s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 23s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

61m 14s

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1872

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 6e61497f53c4 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / edc2e9d

Default Java
1.8.0_242

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/2/artifact/out/diff-checkstyle-hadoop-tools_hadoop-azure.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/2/testReport/

Max. process+thread count
307 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 36s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
18m 46s
trunk passed

+1 :green_heart:
compile
17m  0s
trunk passed

+1 :green_heart:
checkstyle
2m 37s
trunk passed

+1 :green_heart:
mvnsite
1m 21s
trunk passed

+1 :green_heart:
shadedclient
19m 40s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 13s
trunk passed

+0 :ok:
spotbugs
1m  3s
Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 33s
branch/hadoop-project no findbugs output file (findbugsXml.xml)

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 30s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 41s
the patch passed

+1 :green_heart:
compile
16m 14s
the patch passed

+1 :green_heart:
javac
16m 14s
the patch passed

-0 :warning:
checkstyle
2m 36s
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
1m 19s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
14m 15s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 16s
the patch passed

+0 :ok:
findbugs
0m 30s
hadoop-project has no data from findbugs

_ Other Tests _

+1 :green_heart:
unit
0m 25s
hadoop-project in the patch passed.

+1 :green_heart:
unit
1m 33s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 49s
The patch does not generate ASF License warnings.

106m 19s

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1872

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 9795022f8637 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / edc2e9d

Default Java
1.8.0_242

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/1/artifact/out/diff-checkstyle-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/1/testReport/

Max. process+thread count
452 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-tools/hadoop-azure U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

In the test results pasted, there is failure for a testcase which is not related to this PR. Create a JIRA to track and fix test issue.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
35m 13s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
25m 54s
trunk passed

+1 :green_heart:
compile
0m 37s
trunk passed

+1 :green_heart:
checkstyle
0m 26s
trunk passed

+1 :green_heart:
mvnsite
0m 42s
trunk passed

+1 :green_heart:
shadedclient
20m 41s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 32s
trunk passed

+0 :ok:
spotbugs
1m  9s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
1m  7s
trunk passed

-0 :warning:
patch
1m 29s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 40s
the patch passed

+1 :green_heart:
compile
0m 28s
the patch passed

+1 :green_heart:
javac
0m 28s
the patch passed

-0 :warning:
checkstyle
0m 19s
hadoop-tools/hadoop-azure: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
0m 32s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
18m 50s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 27s
the patch passed

+1 :green_heart:
findbugs
1m  7s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 37s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 44s
The patch does not generate ASF License warnings.

111m 33s

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1872

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 296de404716a 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / d0a7c79

Default Java
1.8.0_242

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/3/artifact/out/diff-checkstyle-hadoop-tools_hadoop-azure.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/3/testReport/

Max. process+thread count
308 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 10s
trunk passed

+1 :green_heart:
compile
17m 18s
trunk passed

+1 :green_heart:
checkstyle
2m 38s
trunk passed

+1 :green_heart:
mvnsite
1m 20s
trunk passed

+1 :green_heart:
shadedclient
19m 13s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 12s
trunk passed

+0 :ok:
spotbugs
1m  3s
Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 34s
branch/hadoop-project no findbugs output file (findbugsXml.xml)

-0 :warning:
patch
1m 29s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 42s
the patch passed

+1 :green_heart:
compile
16m  9s
the patch passed

+1 :green_heart:
javac
16m  9s
the patch passed

-0 :warning:
checkstyle
2m 42s
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
1m 22s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
14m 13s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 14s
the patch passed

+0 :ok:
findbugs
0m 31s
hadoop-project has no data from findbugs

_ Other Tests _

+1 :green_heart:
unit
0m 32s
hadoop-project in the patch passed.

+1 :green_heart:
unit
1m 37s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 54s
The patch does not generate ASF License warnings.

109m 16s

Subsystem
Report/Notes

Docker
Client=19.03.7 Server=19.03.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1872

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 5a028e078956 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / bbd704b

Default Java
1.8.0_242

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/4/artifact/out/diff-checkstyle-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/4/testReport/

Max. process+thread count
456 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-tools/hadoop-azure U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m 27s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 52s
trunk passed

+1 :green_heart:
compile
23m  0s
trunk passed

+1 :green_heart:
checkstyle
3m 22s
trunk passed

+1 :green_heart:
mvnsite
1m 15s
trunk passed

+1 :green_heart:
shadedclient
23m 18s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 59s
trunk passed

+0 :ok:
spotbugs
1m 14s
Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 27s
branch/hadoop-project no findbugs output file (findbugsXml.xml)

-0 :warning:
patch
1m 36s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 44s
the patch passed

+1 :green_heart:
compile
20m 31s
the patch passed

+1 :green_heart:
javac
20m 31s
the patch passed

-0 :warning:
checkstyle
3m 26s
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
1m 11s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
16m 53s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 54s
the patch passed

+0 :ok:
findbugs
0m 29s
hadoop-project has no data from findbugs

_ Other Tests _

+1 :green_heart:
unit
0m 23s
hadoop-project in the patch passed.

+1 :green_heart:
unit
1m 22s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 45s
The patch does not generate ASF License warnings.

131m 15s

Subsystem
Report/Notes

Docker
Client=19.03.7 Server=19.03.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1872

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 64625decbc8e 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3afd4cb

Default Java
1.8.0_242

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/5/artifact/out/diff-checkstyle-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/5/testReport/

Max. process+thread count
309 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-tools/hadoop-azure U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/5/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m 19s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
23m 31s
trunk passed

+1 :green_heart:
compile
20m 12s
trunk passed

+1 :green_heart:
checkstyle
2m 50s
trunk passed

+1 :green_heart:
mvnsite
1m  1s
trunk passed

+1 :green_heart:
shadedclient
20m 29s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 52s
trunk passed

+0 :ok:
spotbugs
1m  3s
Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 25s
branch/hadoop-project no findbugs output file (findbugsXml.xml)

-0 :warning:
patch
1m 23s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 39s
the patch passed

-1 :x:
compile
11m  0s
root in the patch failed.

-1 :x:
javac
11m  0s
root in the patch failed.

-0 :warning:
checkstyle
2m 38s
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
0m 49s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
16m 57s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 13s
the patch passed

+0 :ok:
findbugs
0m 29s
hadoop-project has no data from findbugs

_ Other Tests _

+1 :green_heart:
unit
0m 23s
hadoop-project in the patch passed.

+1 :green_heart:
unit
1m 31s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 48s
The patch does not generate ASF License warnings.

111m 20s

Subsystem
Report/Notes

Docker
Client=19.03.7 Server=19.03.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1872

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 16fce474ffaf 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 4062217

Default Java
1.8.0_242

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/6/artifact/out/patch-compile-root.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/6/artifact/out/patch-compile-root.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/6/artifact/out/diff-checkstyle-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/6/testReport/

Max. process+thread count
313 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-tools/hadoop-azure U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m  0s
trunk passed

+1 :green_heart:
compile
16m 54s
trunk passed

+1 :green_heart:
checkstyle
2m 38s
trunk passed

+1 :green_heart:
mvnsite
1m 20s
trunk passed

+1 :green_heart:
shadedclient
19m 27s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 12s
trunk passed

+0 :ok:
spotbugs
1m  4s
Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 33s
branch/hadoop-project no findbugs output file (findbugsXml.xml)

-0 :warning:
patch
1m 30s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 42s
the patch passed

+1 :green_heart:
compile
16m 18s
the patch passed

+1 :green_heart:
javac
16m 18s
the patch passed

+1 :green_heart:
checkstyle
2m 36s
the patch passed

+1 :green_heart:
mvnsite
1m 22s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
14m 21s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 12s
the patch passed

+0 :ok:
findbugs
0m 33s
hadoop-project has no data from findbugs

_ Other Tests _

+1 :green_heart:
unit
0m 34s
hadoop-project in the patch passed.

+1 :green_heart:
unit
1m 36s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 51s
The patch does not generate ASF License warnings.

106m 47s

Subsystem
Report/Notes

Docker
Client=19.03.7 Server=19.03.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1872

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux aaf892ffd9ea 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3859fa7

Default Java
1.8.0_242

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/7/testReport/

Max. process+thread count
414 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-tools/hadoop-azure U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1872/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

In the test results pasted, there is failure for a testcase which is not related to this PR. Create a JIRA to track and fix test issue.

Done
https://issues.apache.org/jira/browse/HADOOP-16915


Add JSONField to nautobot.extras.models.models.JobLogEntry for debuging structured data

As ...
Austin - Network Automation Engineer
I want ...
The ability to have a human readable log message AND the ability to log structured data.
So that ...
This will allow for easier troubleshooting and clear delineation on use of fields in the JobLogEntry object
I know this is done when...

JSONField is added to the JobLogEntry model
UI is able to represent stringified representation of the object, log message, and JSON data

Optional - Feature groups this request pertains to.

[ ] Automation
[ ] Circuits
[ ] DCIM
[ ] IPAM
[X] Misc (including Data Sources)
[ ] Organization
[ ] Plugins (and other Extensibility)
[ ] Security (Secrets, etc)
[ ] Image Management
[X] UI/UX
[X] Documentation
[ ] Other (not directly a platform feature)

Database Changes

Add JSONField to JobLogEntry model

External Dependencies
No response

@nautobot/core what do we think of this in the light of v2?

Could be done certainly, though I'm not sure how the JobLogEntry table views would best need to be structured to potentially represent both string/Markdown and JSON data in each log entry. I'd also be a bit concerned about potential bloat of the JobLogEntry database table if we allow storage of arbitrarily large JSON in each log entry.


audio_diffusion_pytorch

hello, when following the instructions and running python cli.py
I get an error saying  No module named 'audio_diffusion_pytorch'
If pip install audio_diffusion_pytorch
I get an error saying ImportError: cannot import name 'T5Embedder' from 'audio_diffusion_pytorch'
are there some missing steps required to run this? thank you

Should be fixed with the latest commit.


Contract Creation and ICO creation issue

If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
Rinkeby
If you were able to create it, what is the URL of your crowdsale?
Contract created, crowdsale did not and did not receive download file.
Do you have screenshots showing the problem?
Yes
Do you see errors in the dev console? If yes, please include a screenshot
To open the dev console in Google Chrome, press F12, or go to View -> Developer -> Developer Tools, and open the Console tab
If you see errors, please right click on them and "Save as..". Zip saved file and attach it to the Issue.
yes

wizard.oracles.org-1522658076342.log

There are no errors in the logs. It seems you didn't wait for the response from the 3d transaction and you refreshed the page. In this case, if all 3 transactions are mined successfully you can skip transactions in Metamask, skip it in Token wizard and continue with the next steps and confirm all other transactions.


Update index.html

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
5dc63fb33621182a8124de7fbab871f54fc63770
link
/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


need help installing NANA

I am new to cmake as well as GUI toolkits and I'm finding it difficult to install NANA. I had a look through the installation guide but I got lost in all the details. Could someone pls help me set up. I'm on windows and I use cmake and mingw for buildsystems (no ide).

Before using MinGW, you need to choose a proper distro , please read the following article. https://github.com/cnjinhao/nana/wiki/Troubleshooting-MinGW
if you still have any problem, please let me know.


Memory leaks

I am seeing several memory leaks from Pantry. Please see the attached screenshots.

My code with Pantry leaks -

Thanks @sasikiran, I'll run through the whole thing before the next release.

Awesome!


Add a unique drop chance display to the raids plugin

Gives the option to display your percentage chance of receiving a unique drop at the Chambers of Xeric. This is calculated using the current amount of total points.

*Raids drop chance caps to 80%
*if you have more than 712,5k points it shows you more than 100% plus 80% is the cap. next points go for next drop chance
*"Gives the option to display your percentage chance of receiving a unique drop" you probably mean team, unless you are doing solo.

We now use the vanilla points overlay. The old RL points overlay was moved to an external plugin. If you PR this to the external plugin I will accept it.


Defining some asset fields in collections

One of the things we hard originally discussed was having an "available_assets" field. This is a useful field to define in collections, as it tells you what you can expect to find in a single member item.
There's nothing specifically that prevents this from being the case in the definition of collections, but it does make the logic of merging an item with it's collection level metadata more complex. If a collection defines some fields of an asset (the ones that are duplicated across all items such as key, file type, available keys, etc.) and the item defines just the actual URL of those items, then a client that merges them (such as sat-search ) needs to make sure it merges all of the available keys into the correct items.
For example, right now with assets as objects (may change, see https://github.com/radiantearth/stac-spec/pull/151) in the collection assets could be defined as just a dictionary of keys with empty values:
assets: {
'B1': {},
'B2': {},
'B3': {}
}
Which informs the user who is examining the collection that B1, B2, and B3 are available assets. Otherwise right now, such as in sat-api, you have to look at a specific item to even know what assets are available, and even in that case you are assuming that the one item is representative of all items in the collection, which is a bad assumption. Some items could define additional assets, but the collection should indicate which assets are available in all items.
cc @cholmes @mojodna @scisco

This still seems achievable using the key or role attribute in place of object keys, indicating which are expected to have values associated.

@mojodna Yes, it is achievable, but only if an id is constrained to be unique among all items in the list. But it also makes it very difficult to merge them as described in #151 whereas a recursive merge of dictionaries is straightforward.

Moving this to 0.7.0, as getting this in is a top priority for that release, but won't happen here.


add march otel in focus blog

lousy smarch weather.
neither rain nor sleet nor highly communicable infectious respiratory disease will keep me from my appointed rounds of writing the march community update.

Preview: https://deploy-preview-2562--opentelemetry.netlify.app/blog/2023/otel-in-focus-03/

neither rain nor sleet nor highly communicable infectious respiratory disease will keep me from my appointed rounds of writing the march community update.

🤣

I don't have much of an opinion about which post goes first. It's more important to have linkable announcements than assign an order. We can update the banner to point to the one we want the most eyes on.

Let's do this first and call-forward to it. I'm not precious about having these updates in the banner.


Documentation should be updated to reflect loss scaling for manual optimization + gradient accumulation

I think the documentation should be updated to reflect that the loss for manual optimization with gradient accumulation requires manual scaling with the accumulation factor 'N'. The current doc is a bit confusing since it specifies the use of % N for the optimizer stepping and zeroing of gradients but implicitly says nothing about scaling the actual loss and instead leaves it to the reader to scrutinize what self.compute_loss(batch) actually does.
I think it would be more instructive to have the example code specifically call this out, e.g., loss = self.my_loss_fn(batch) / N.
Originally posted by @callumhay in https://github.com/Lightning-AI/lightning/issues/12811#issuecomment-1614987379

Thanks @callumhay! Would you like to send an update for this? Explicitly dividing by N in that example should do the trick.


ci: generate test-report after tests run

:tada: This PR is included in version 0.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


change removeBinding to deal with new state format

Now we need to have removeBinding deal with the fact that we have these different "layers" of state.

; remove-binding tests
(check-equal? (remove-binding 'b 'false '(((b) (false)) ((z) (1)) ((x a) (10 2)))) '((() ()) ((z) (1)) ((x a) (10 2))))
(check-equal? (remove-binding 'z 1 '(((z) (1)) ((x a) (10 2)))) '((() ()) ((x a) (10 2))))
(check-equal? (remove-binding 'a 2 '(((x a) (10 2)))) '(((x) (10))))
(check-equal? (remove-binding 'x 10 '(((x) (10)))) '((() ())))

we don't need to remove binding for any reason, we'll just update binding: #20


DeviceControlEnable for ASR Policy

[Enter feedback here]
Based on this Documentation it is unclear for me when we are using the Reusable Settings in a ASR Policy if we need to enable Device Control which is only available in as OMA URI.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 19b5fda8-c875-aac3-385d-43c88feed731
Version Independent ID: 19b5fda8-c875-aac3-385d-43c88feed731
Content: Deploy and manage Removable Storage Access Control using Intune
Content Source: microsoft-365/security/defender-endpoint/deploy-manage-removable-storage-intune.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Some annotations in instances_trainrem.json have no iscrowd key - are they all instances?

Hey there, first of all, thank you for the great dataset! I'm actively using it in my work :)
Quick questions, just to be sure (probably no impact in practice). Is any annotation without 'iscrowd' key a normal instance, i.e. not a crowd?
Since a part of my code relied on the presence of 'iscrowd' in the annotations, I found that 354674/1093027 annotations in instances_trainrem.json have no 'iscrowd' set (7148/1093027 are crowd annotations btw). Typically, e.g. in mmdet, any annotation without 'iscrowd' will be treated as instance, i.e. as not a crowd, similar to if 'iscrowd: 0' is set. Is this assumption correct?
Thanks, Johannes

Hey Johannes, thanks for using our annotations.
You can treat any instance without iscrowd field as instance annotations i.e. iscrowd:0 . In train set 354674 instances are imported from LVIS dataset. The are instance annotations. Missing iscrowd:0 is probably an oversight on our part. Thanks for pointing that out !


Adds quic ietf v1 test

Replaces #755 with more checks about detection

Replaced by https://github.com/OISF/suricata-verify/pull/780


OpenMetadata Airflow Lineage - Okta support

The same question also goes the other way.
Is it possible to access Airflow if Airflow has configured with Okta (OAuth) ?

Fixed in #3233


Git gutter indicators not appearing in some files.

Does this issue occur when all extensions are disabled?: Yes/No
Yes

Version: 1.91.0 (Universal)
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Date: 2024-07-01T18:54:18.541Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0
Steps to Reproduce:

Have a git repo open with no files modified
Modify a file
Note that the gutter indicators on the left side of the code editor next to the numbers no longer show

View in the code editor on an ~800 line file

View in the source control panel on an ~800 line file

View in the code editor on a smaller file (~80 line file)

No errors or relevant logs appear in the dev tools js console (screenshot taken from extensions disabled mode)

Whats weird is that this doesn't happen on all large files, only some. I did a little bit of digging around the HTML of the page, and the div that contains the number of the line is missing the child div which contains the classes cldr dirty-diff-glyph dirty-diff-added on the ~800 line file. Where as the ~80 line file contains that child div, thus rendering the green gutter indicator
Codebase is company owned so I cant share any files unfortunately, but I'm happy to help with any debugging. Just not sure where to begin 😅

Also worth noting that it works fine on other colleagues macs. Ive also tried doing an app restart, a computer restart & rolling  back multiple versions and the issue still occurs after trying all those.

@MrSimmmons, is there a chance that your setup contains any symbolic links on the path?
Are you able to reproduce on files in a particular folder but not others? Thanks!

No symbolic links in that project, and has only happened on 1 particular file so far.
It is a rather large monorepo, though I don't see how that would affect things as all the other files I've opened so far work normally.

I'm not sure what could be going on here. @MrSimmmons, do you have that specific file open twice in VS Code?


Update Latest Dependencies

This is an auto-generated PR with the latest dependency updates.

Codecov Report

Merging #78 (0a239f7) into main (c3abcdf) will decrease coverage by 65.1%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##            main     #78      +/-   ##
========================================
- Coverage   99.2%   34.2%   -65.0%
========================================
  Files        105     105
  Lines       2689    2689
========================================
- Hits        2667     917    -1750
- Misses        22    1772    +1750

Impacted Files
Coverage Δ

facilyst/models/utils.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/models/optimizers/hyperopt.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/mock_tests/test_wave.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/mock_tests/test_dates.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/models_tests/test_tsb.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/models_tests/test_adida.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/models_tests/test_imapa.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/mock_tests/test_features.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/models_tests/test_bert_qa.py
0.0% <0.0%> (-100.0%)
:arrow_down:

facilyst/tests/mock_tests/test_mock_utils.py
0.0% <0.0%> (-100.0%)
:arrow_down:

... and 66 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add a possibility to validate fixedSource post macro expansion in the assertMacroExpansion

Description
In light of the discussion here, there's a need to re-evaluate the testing strategy for macro expansions, particularly concerning the application of fix-its. The current methodology asserts the expandedSource before the application of any fix-its, which may not fully validate the macro's behavior in the presence of fixable code errors.
A more robust testing process would involve the assertMacroExpansion function not only applying fix-its to the originalSource but also asserting the result of the macro expansion on the corrected source code. This approach has been effectively utilized in swift-macro-testing by mbrandonw and stephencelis, showcased here.
To align with this improved testing paradigm, I propose the addition of a new parameter—perhaps expandedSourceAfterApplyingFixIt—which would enable users to assert against the post-fix-it expanded source. This addition is crucial as macros may propose fix-its for diagnostics that do not halt the expansion process, such as those with a severity less than error.
By incorporating this feature, assertMacroExpansion would gain the capability to confirm the fixed source after the macro expansion, ensuring a more comprehensive verification process.

I'm on it

Tracked in Apple’s issue tracker as rdar://118012844


ActiveForm + Gridview = ajax call called twice

I dont know if this is intended behavior, but when I include a Gridview inside an activeform, and I click on a delete button with a confirm, I have to confirm twice. The javascript log says that yii.activeForm.js is catching the AJAX event and starting some setTimeout event. If the gridview is outside of the Form, the normal behavior is occurring.

the following is a fix, but of course has its disadvantages
'enableClientScript'=>false

same behavior I get when attaching an event to a form:
$( "#create-member" ).submit(function( e ) {
alert();
});

I guess one is the ajax validation, the other is the actual submit

I have the same problem

Confirmed. Same issue.

Same here, using DetailView and/or GridView

Disabling client validation solves the issue

multiple topic about this.


do we need an Opcache/JIT while using FrankenPHP with Laravel?

as FrankenPHP used to run in memory do we need to compile Laravel code using opcache and JIT?
we think that we don't have to use opcache, jit because Laravel code already stays compiled in memory.
please explain these things! thanks a lot🙏

Using opcache is indeed less useful in worker mode, but allows workers to restart faster after when they reboot.
JIT may still help, but I haven't performed any benchmarks.


Bug: On the settings page, the localization used from the list was not shown in combobox

Fixed by 8f80ef6 commit


Avoid NPE when ffi::archive_read_data_block returns a null block

I have no idea why libarchive does this but it's a thing

Please add a changelog entry.

Do you have a test case?

Fixed in #126.


catch Summon search api's HTTPError: 429 Client Error

Note: to test, tail the apache error.log and look for something like the following:
[Thu Apr 02 14:35:25 2015] [error] [02/Apr/2015 14:35:25] ERROR [ui.views:499] Summon error: 429 Client Error:
[Thu Apr 02 14:35:25 2015] [error] [02/Apr/2015 14:35:25] ERROR [ui.views:502] 1 retries, sleeping 1s and retrying

In my testing it has always worked the second time.  Note that this reuses the existing setting SER_SOL_API_MAX_ATTEMPTS so it won't go past three attempts.  A third failure will lead to email like we already receive.

logger.error() was not a good idea.  just remove these.


ansis:SoilSite  land management 0..1 to 0..*

check expectation re cardinalities being rolled back into ontology

All good. All cardinality changes going into ontology


Correct way to deal with --openssldir for bundled deployment

Due to some very specific reasons we need to build an application which bundles it's own openssl library together with certs, config files and engines. This means that we deploy a directory containing the main binary and a folder lib with the shared objects, among other, libssl and libcrypto. To make this application link correctly to the libraries in any directory we can of course set RPATH to $ORIGIN/lib.
The challenge we have is that during compilation of openssl we need to set the --prefix and --openssldir paths which of course is not known during compile time since these files are also bundled with the application.
./Configure shared --prefix=/library --openssldir=/lib

After this we can see that these paths gets hard coded into the library:
$ grep -nra /library/ ./lib/libcrypto.so
167534:/library/lib/ct_log_list.cnf
167649:OPENSSLDIR: "/library/lib"
167651:ENGINESDIR: "/library//lib/engines-1.1"
179919:/library//lib/engines-1.1
196978:/library/lib/private
196982:/library/lib
196986:/library/lib/certs
196988:/library/lib/cert.pem

The only way I have come up with so far that makes the library portable is to compile the library with a really long placeholder path (since the offsets in an elf-file are fixed) and then replace that string in the elf-files to the location of the application followed by trailing slashes to make the length of the strings the same before starting the application. I would hope there is a better way to this than editing the elf files.
./Configure shared --prefix=/$(printf "%0255d" 0) --openssldir=PLACEHOLDERDIR

If the location of config, module and engine paths are known relative to that of the application, you can set the env vars OPENSSL_CONF, OPENSSL_ENGINES, OPENSSL_MODULES at application startup. That will override the built-in defaults.

Thanks @selvanair! It's not optimal for me with env vars, but it's much better than what I was doing!

marking as inactive, will be closed at the completion of 3.4 dev without further input


Add descriptive metadata

Add further information to the ontology file

ORCID of creators
License information
Version property

These recommendations by TIB look quite useful in this regard: https://github.com/TIBHannover/terminology-metadata

Also relevant: https://arxiv.org/abs/2003.13084


PST files to MBOX files

Convert your PST to MBOX by using this PST to MBOX Converter tool, This tool easily Export & Convert PST file to MBOX file with all data files like: Emails, Contacts, Calendar, Tasks, and Journals etc.
You get Smoothly Restore & Convert PST to MBOX and migrate all your offline mailboxes, contacts, calendar etc from Outlook 2016 & any older version to MBOX file with best performing PST to MBOX Converter Tool.
This Software supports 20+ emails clients like: Entourage, Thunderbird, AppleMail, Spicebird, Pocomail, Eudora, Netscape, Mulberry, SeaMonkey, OperaMail, ClawsMail, Evolution, Mozilla Mail etc.
Try it free demo version: https://www.mannatsoftware.com/stellar-outlook-pst-to-mbox-converter-win.html

This channel is reserved for ‘Azure docs’ feedback; for receiving documentation feedback and driving content improvement.
I’d recommend taking a look at GitHub’s Terms of Service, specifically the section on advertising.


Status

Hi @mattfawcett, first of all, thanks for your work with this Gem.
I would like to know the current status.
We'll be using a lot Foursquare API. I already upgrade all the dependencies of the Gem and solved an annoying issue with Hashie logs, with all tests green.
I wanted to know if you're receiving pull requests, or if I can create and maintain a separate Gem and also address other issues.
Thanks in advance,

Hey @g3ortega -
I no longer have time to maintain this gem. If you would like to take over maintenance (or know someone who would), I am happy to transfer ownership. Otherwise I think a fork is probably your best option.

Hi @mattmueller, thanks for your response,
I'm willing to maintain this gem, also we are going to be using Foursquare APIs a lot in my company, so other people of the team would be helping if needed.

That's great @g3ortega ! Would you prefer me to simply add you (and anyone else from your team) as collaborators or transfer the actual repo to your account?

Hi @mattmueller, what you think it's best for you. For now for now only I'll be actively contributing from my team.

@g3ortega I've invited you as a collaborator. Closing this out for now.


Setup failed for custom integration rinnai: Unable to import component: cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_' (/usr/local/lib/python3.11/site-packages/urllib3/util/ssl_.py)

Recently updated home assistant and noticed that the integration would no longer load. The following is the log message.
Logger: homeassistant.setup
Source: custom_components/rinnai/init.py:5
Integration: Rinnai Control-R Water Heater (documentation)
First occurred: 3:57:23 PM (1 occurrences)
Last logged: 3:57:23 PM
Setup failed for custom integration rinnai: Unable to import component: cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_' (/usr/local/lib/python3.11/site-packages/urllib3/util/ssl_.py)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 215, in _async_setup_component
component = integration.get_component()
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 813, in get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in find_and_load_unlocked
File "", line 690, in load_unlocked
File "", line 940, in exec_module
File "", line 241, in call_with_frames_removed
File "/config/custom_components/rinnai/init.py", line 5, in
from aiorinnai import async_get_api
File "/usr/local/lib/python3.11/site-packages/aiorinnai/init.py", line 17, in
from aiorinnai.api import async_get_api
File "/usr/local/lib/python3.11/site-packages/aiorinnai/api.py", line 12, in
from aiorinnai.aws_srp import AWSSRP
File "/usr/local/lib/python3.11/site-packages/aiorinnai/aws_srp.py", line 19, in
import aioboto3
File "/usr/local/lib/python3.11/site-packages/aioboto3/init.py", line 5, in
from aioboto3.session import Session
File "/usr/local/lib/python3.11/site-packages/aioboto3/session.py", line 9, in
import aiobotocore.session
File "/usr/local/lib/python3.11/site-packages/aiobotocore/session.py", line 1, in
from botocore.session import Session, EVENT_ALIASES, ServiceModel, UnknownServiceError
File "/usr/local/lib/python3.11/site-packages/botocore/session.py", line 29, in
import botocore.credentials
File "/usr/local/lib/python3.11/site-packages/botocore/credentials.py", line 34, in
from botocore.config import Config
File "/usr/local/lib/python3.11/site-packages/botocore/config.py", line 16, in
from botocore.endpoint import DEFAULT_TIMEOUT, MAX_POOL_CONNECTIONS
File "/usr/local/lib/python3.11/site-packages/botocore/endpoint.py", line 22, in
from botocore.awsrequest import create_request_object
File "/usr/local/lib/python3.11/site-packages/botocore/awsrequest.py", line 24, in
import botocore.utils
File "/usr/local/lib/python3.11/site-packages/botocore/utils.py", line 32, in
import botocore.httpsession
File "/usr/local/lib/python3.11/site-packages/botocore/httpsession.py", line 10, in
from urllib3.util.ssl import (
ImportError: cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl' (/usr/local/lib/python3.11/site-packages/urllib3/util/ssl.py)

Interesting. Did this happen after an update or did you just try installing it? I am running on the newest version with no issues right now.

@explosivo22 I did just recently upgrade but I believe it may have already been broken. It used to run and I haven’t changed anything with the Rinnai configuration/device.


I currently have the following tuners. Will they be supported? DTA-2131B(Dektec), DTA-2139C(Dektec), Wintv quardHD

DTA-2131B(Dektec)
DTA-2139C(Dektec)
Wintv quardHD(Hauppauge)
This is Korea. I would like to know if I can record ATSC [QAM | 8VSB] signal.
Is it possible to use it with mirakcrun and mirakc?

mirakc (and also mirakurun) does not directly open any tuner devices. instead, it spawns a command to open a tuner device: https://github.com/mirakc/mirakc/blob/main/docs/config.md#tuners
in mirakc, you can specify a mustach template string in tuners[].command and several template parameters are available in the template string.
i'm not familiar with ATSC, but maybe its data format is different from ISDB. therefore, you cannot use mirakc and mirakurun for ATSC data stream without modification.
unlike mirakurun, mirakc does not process ts stream directly. mirakc uses mirakc-arib for processing ts streams, but mirakc-arib does not support ATSC. if you create a program which behaves like mirakc-arib for ATSC data stream, you can specify it in config.yml. search mirakc-arib in https://github.com/mirakc/mirakc/blob/main/docs/config.md#configuration.


Allow picture-in-picture for Vimeo

Updates the allow attribute to allow for picture-in-picture on Vimeo embeds.

hey @bdougherty this is a good improvement!
Do you think this would be better off as a prop?
Somethink like this?
<script lang="ts">
  import { getPadding } from '$lib/utils'
  import GeneralObserver from './general-observer.svelte'

  export let vimeoId: string = ''
  export let autoplay: boolean = false
  export let aspectRatio: string = '16:9'
  export let skipTo = { h: 0, m: 0, s: 0 }
  export let disable_observer: boolean = false
  export let allowFullscreen: boolean = true
  export let allowPiP: boolean = false

  const { h, m, s } = skipTo
</script>

<GeneralObserver {disable_observer}>
  <div
    data-testid="vimeo"
    class="vimeo-svelte-embed"
    style={`
      position: relative;
      width: 100%;
      ${getPadding(aspectRatio)}
    `}
  >
    <iframe
      title={`vimeo-${vimeoId}`}
      src={`https://player.vimeo.com/video/${vimeoId}?autoplay=${autoplay}&api=1#t=${h}h${m}m${s}s`}
      frameborder="0"
      allow={autoplay ? "autoplay; fullscreen; picture-in-picture" : "fullscreen; picture-in-picture"}
      allowfullscreen={allowFullscreen}
      webkitallowfullscreen={allowFullscreen}
      mozallowfullscreen={allowFullscreen}
      style={`
        position: absolute;
        top: 0;
        left: 0;
        width: 100%;
        height: 100%;
      `}
    />
  </div>
</GeneralObserver>

Interested to hear your thoughts

I would never disable either fullscreen or pip, so I'm probably not the best person to ask haha. Definitely they should default to true if added as props though.

Also, for what it's worth, there are lots of other embed parameters that could be added as props.

Hey, I really appreciate all the help I can get 😊
If you can suggest other areas of improvement I really appreciate it, thank you so much.
So, just for clarity here on this PR, (I'll need to research this as well so sorry if deleyed) the suggested attributes should be default?

I'll try to update this PR with some more of the Vimeo player params next week.

Hey @bdougherty I'll merge this one and add in the rest from the details in #488 thanks 👍


Blazor Debugging in Visual Studio 2019 Fails to Connect

Describe the bug
When I try to connect VS2019 to a running Blazor application I get
Unable to connect to <localhost address> Operation not supported. Unknown error 0x80070057

To Reproduce
Steps to reproduce the behavior:

Start Blazor App
Run Chrome with debugging (%programfiles(x86)%\Google\Chrome\Application\chrome.exe --remote-debugging-port=9222 http://localhost:50601/)
Attempt to attach to process in VS
Connection refused

Expected behavior
Debugger should connect.  I've been following Steves talk from NDC London but I just cannot get any of this working.  Debugging in the browser is working but attempting this from VS fails every time.
I'm running v73 of Chrome.

If you want to debug Blazor application in VS you have to use Blazor on the server (Razor Components). Blazor on the client (WebAssembly)  can be debugged directly in Chrome. Here are details:
https://docs.microsoft.com/en-us/aspnet/core/razor-components/debug?view=aspnetcore-3.0
You cannot debug Blazor WebAssembly in VS. Currently Blazor is compiled to IL code and then interpreted in the browser. It is not compiled to native WebAssembly code.

@SteveSandersonMS Are there any additional steps to reproduce your demo of attaching VS to a client-side Blazor app?

Closing as this is a non-supported scenario yet but we will be doing that in the future: #9035


[ISSUE-287] add program to solve CourseSolution problem

Issue Id you have worked upon -
#287
Briefly explain your program logic -
Approach: Topological Sorting, Cycle Detection
Let's try to think of prerequisites pairs as an edge between two nodes in a graph.
Now this problem becomes simple, we just need to find out if there is any cycle in a graph or not.
If there is no cycle, then we can finish all the courses otherwise the answer is no.
Screenshots(Attach 2 screenshots of your own input and output) -
Attach here

Checklist:
Eg - If your code follow the below guidelines. Kindly change [] to [x]
All the conditions should be fulfilled for considering your code for merging -

[x] I have mentioned the question as comment in my solution file.

[x] My code follows the guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code.

[x] My code gives the correct output.

[x] I confirm that I have not copied the code from anywhere. In case its found that I have copied even after successful merge then I can be banned from the repository and hacktoberfest.

[x] I affirm that I strictly follow contributing guidelines and code of conduct.

@SarthakKeshari Could you please review this PR?
Thanks


Error handling for PSCore

Currently this module does not work in PowerShell Core. when you attempt to run Connect-OneLogin, Invoke-restmethod returns an error that includes the value of the client secret. This needs to be fixed ASAP as a security flaw.

The error is related to the Semicolon in the authorization header.  Strict header parsing is now enabled by default on PSCore (as defined in the RFC).
-SkipHeaderValidation must be added to invoke-restmethod, or add it globally in default settings:
$PSDefaultParameterValues['Invoke-RestMethod:SkipHeaderValidation'] = $true

@crou thanks for figuring that out. I haven't really tested this module against PS Core, but I haven't prevented it being run on core either. This biggest problem for me is that the error message includes the value of the client secret, which I need to figure out how to handle properly. I'm thinking I could simply scrub text matching the client secret out of any trapped errors before they are streamed out to the user.


Mobile Keyboard Input

Here is a start for the mobile input portion, we need to work on key mapping though. Probably related but text is actually being typed into the input on mobile, that would need to be prevented.
Keyboard opens on default and full screen views. On android you can hide the keyboard with the back arrow, I have not tested on iOS.
I Dynamically created the input, but it can easily be included in the html.

Edit by mtlynch@
Fixes #46
^^^ Putting that line in the PR description auto-closes the linked issue when we merge it.

This if for issue #46

you've been busy today, I just got home looking over the changes

Nice addition! I'm running into two bugs.
It's impossible to type backspaces. Could the input start with a space character, and then we detect "backspace" by checking to see if the text is ""?
Then there's strange behavior with dashes. If I type dashes (-), they send normally, but for some reason, the next non-dash character I type includes all the previous dashes.

-l sends - and then -l
--l sends -, -, --l

Can you reproduce that behavior on your end? I'm on a Pixel2 + Chrome 85.

I can do both back space and dashes no issues
Moto G7 Android 10
Chrome v85.0.4183.101

I can do both back space and dashes no issues

Hmm, that's puzzling. The current implementation reads the value of the mobile-keyboard-input and forwards it to the backend. An <input> element can't contain a backspace, so how does it detect the backspace?
Have you tried dash + another letter? Dashes work fine, but when you type a dash and then type a letter like p after the dash, it doubles the dashes.

I do see an issue with spaces and backspace. If I do 3 spaces I need to do 4 Backspaces for it to take. But if set an alert to notify when a key is pressed it works fine with the interruption.
I changed addEventListener("input" to "keyup" but still the same issue.
I didn't notice anything strange with the dash (-) I will mess with it some more tomorrow.
I converted it back to draft until we figure out what is happening.

hmm with these changes only alpha numeric characters work for me. Space, comma, period, and all the other characters don't. They show up as undefined. Also full screen on a desktop pc stopped working now, not sure what caused it to break.

Whoops, reverting in #264.


CI: Use ubuntu-20.04 to aviod the deprecated warning

Fix upptime/upptime#635
Use ubuntu-20.04 to aviod the deprecated warning from Github Action.
Ref: GitHub Action announce as actions/runner-images#6002

I have read the CLA Document and I hereby sign the CLA


Theme

Resolves : https://github.com/codidact/co-design/issues/57 and, https://github.com/codidact/qpixel/issues/565

Dark theme

Umm! Code area (pre tag) and, user-card-meta's background is changed from cd.com/assets/stylesheets/application.scss That's why I didn't make changes to them in codidact.scss. button is-muted is-outlined is-active (activity tab) is from codidact.scss. But, when I was copy-pasting those code I forgot to change their color and, background-color. I will change check it again.
Currently, I am using separated lines just to understand those code.

Found a problem.... : texts isn't white color in fields.. And, .notice .is-warning color is white..... (Maybe, now I can say that no more work is needed in CoDesign) (activity tab should be black (leaving it as it is for now)) (Check following picture and, comment if you see any problem)

New changes

Note : Diff is showing that I made changes to light theme also. Usually, I make changes to light theme. It's all over dark theme.
To test (If you are using Linux) : If you are using Chrome/Chromium than, run that following way
google-chrome --force-dark-mode
chromium --force-dark-mode

You won't face problem for Firefox. I am not sure of Vilvera and, some others (Safari etc). Read the thread to know why you are facing the problem.
Currently, most of worked are done. I guess, there's nothing "left". Usually, it is possible to change color for each category's header. I would request someone else to make changes for category's header (it's in line 17) (You can make PR in the repo if you want). Current, category-header color isn't bad for dark theme either. But, new color for dark theme is very good.

Ohh! Sorry I didn't know changing name of branch will delete PR

Um... where do you have the source files (/src) for these changes? If you don't include them, all modifications you made would be deleted at the next build.

Maybe, i didn’t understand you properly. Are you looking where I worked? https://github.com/Istiakshovon/co-design/tree/Theme the changes are available in that branch. I have those code in my system also

@luap42 is right. You've changed the dist/codidact.css file with your changes, but nothing else. You need to make changes in the files under the src/ directory, then run the build scripts to push them into codidact.css when that's done. Otherwise, next time we run a build all your changes will disappear.

@ArtOfCode- Where (Which line you changed) you requested to make changes? It's looking like you had made changes to Light Theme. When I was running your code I saw some weird text (Unicode) in post and lot of places. And, It wasn't available in dark theme.

That's an encoding bug, don't know where from. There's no specific line you need to change - you need to move all your dark theme code into the appropriate files under src/ and then build the project to compile them into codidact.css.

@ArtOfCode- Please! Check that I am doing it correct or not.

You've got the right files now, yep. Some tips:

Instead of hard-coding colour values, add them as variables as existing colors are.
Instead of wrapping all existing code in a light-mode media query and duplicating it in a dark mode query, you can just wrap lines that deal with colours in media queries.

Ohh! I forgot whenever I was running
npm run build

I was getting some error.

error

npm install worked successfully. And, as far as I know my work is done.

Oops! I forgot to made changes to codidact.scss. i will try to work on it again ASAP.


Unpin scipy pls

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge/aesara pls merge

@conda-forge/core could someone please merge this?


Unknown opencl version

When trying to start gominer, I'm told there's no version number for opencl available to it.  Any thoughts?

@faddat Can you paste the exact output you get?

Sure-- and please know that after updating gominer, I've found that while it is still giving me the unknown opencl message, it now works.
gominer: /opt/cuda/lib64/libOpenCL.so.1: no version information available (required by gominer)
gominer: /opt/cuda/lib64/libOpenCL.so.1: no version information available (required by gominer)
gominer: /opt/cuda/lib64/libOpenCL.so.1: no version information available (required by gominer)