Updated the runtime to python 3.6

Codecov Report

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

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   53.69%   53.69%
=======================================
  Files           5        5
  Lines         149      149
=======================================
  Hits           80       80
  Misses         69       69

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 d159a04...298b9e9. Read the comment docs.

@samuzzal-choudhury Your image is available in the registry: docker pull quay.io/openshiftio/rhel-fabric8-analytics-f8a-api-gateway:SNAPSHOT-PR-55


[DOC] Review doc about Longhorn on K3s and update if necessary

We have some specific steps for installing Longhorn on a K3s cluster. This page https://longhorn.io/docs/0.8.1/advanced-resources/os-distro-specific/csi-on-k3s/ should be reviewed to make sure the custom setup is still necessary, because there have been some fixes since the document was written.

Check https://staging.longhorn.io/docs/0.8.1/ instead since it will become the next v1.0.0.

Validations:

[x] The lastest Longhorn doesn't work on k3s of which the version is lower than v0.10.0 without extra configs.
[x] The lastest Longhorn works fine on k3s of which the version is lower than v0.10.0 with the configs mentioned in the doc.
[ ] The lastest Longhorn works fine on k3s of which the version is v0.10.0 or higher without extra configs.

Here, works fine means I can launch pods with Longhorn volumes via the storageClass.
@yasker Do we still need to check the compatibility for Longhorn v0.7 with k3s?

@shuo-wu Sounds good. And no, we don't need to check v0.7.0.


Rename assert_eq to assert_return

This matches recent changes in the spec repo. I left assert_eq as an
alias for assert_return to accomodate existing tests for now (although
the semantics for FP compares are subtly different), but renamed the
enums and event names to assert_return. I also left the d8
and spec tests alone for now.

I can't get the v8 native prototype to build right now. Is it broken or is it me?
Should I also update the spec and d8 tests?

I think v8-native needs to be updated to the latest version. The version that I have pinned right now doesn't build against the latest v8. I'll update it today.

Hm, looks like it is failing with a new error using variable sized arrays in wasm/encoder.cc. Not sure why this isn't failing on v8-native-prototype travis build.

Different warning settings for clang? It builds fine with v8's normal make
procedure.
On Wed, Oct 7, 2015 at 9:47 PM, Ben Smith<EMAIL_ADDRESS>wrote:

Hm, looks like it is failing with a new error using variable sized arrays
in wasm/encoder.cc. Not sure why this isn't failing on v8-native-prototype
travis build.
—
Reply to this email directly or view it on GitHub
https://github.com/WebAssembly/sexpr-wasm-prototype/pull/3#issuecomment-146308374
.

What do you think about this patch in particular? It shouldn't break anything in v8-native or spec tests.

lgtm, I'll rebase it manually (I hate merge commits :-)

OK. I assume you mean that you have local work which raced with this? If you pushed more frequently that would be less likely. Just sayin' :)

And if not, does github just do fast-forward merges by default, like git itself does? Or is there always a 'merge PR#XXX' commit?

Yeah, GH never does ff merges, AFAIK. :-(

I have not seen it either, I think you have to do it this way
Jc
From: Ben Smith<EMAIL_ADDRESS>Sent: Wednesday, October 07, 2015 1:05 PM
To: WebAssembly/sexpr-wasm-prototype
Subject: Re: [sexpr-wasm-prototype] Rename assert_eq to assert_return (#3)
Yeah, GH never does ff merges, AFAIK. :-(
—
Reply to this email directly or view it on GitHubhttps://github.com/WebAssembly/sexpr-wasm-prototype/pull/3#issuecomment-146313005.


Only BuildAndUploadArtifacts on a merge to main?

BuildAndUploadArtifacts currently always runs if BuildAndTest succeeds. Should not run on pull request open or change.

Actually, I do want to build the distribution files/artifacts and publish them to the pipeline so they can be tested. I only want to push them to Azure Artifacts on a merge to main provided that the version is bumped.

#15 publishes artifacts to pipeline. Do a bumpver to publish it to Azure Artifacts too.


feat: tipping extension data flow

resloves COIL-952
resolves COIL-910
resolves COIL-909

Finalized tipping data and formatted it for use in the UI

minTipLimit
tipCredits
tipping > limitRemaining
featureEnabled for tipping-beta

Fixed minor issues with queries
Added the origin url to the initiateTip
Updated button colors
Changed copy

@njlie
Seems like @traviscrist wants the full url:
https://coiltech.slack.com/archives/C01MTJ37Y4D/p1617911934007000
Though I am just scanning that channel, so I could have misread

Yeah I thought it needed the full url. I'll double check the notion doc and
slack.
On Wed, May 5, 2021, 7:31 PM Nicholas Dudfield @.***>
wrote:

@njlie https://github.com/njlie
Seems like @traviscrist https://github.com/traviscrist wants the full
url:
https://coiltech.slack.com/archives/C01MTJ37Y4D/p1617911934007000
Though I am just scanning that channel, so I could have misread
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/coilhq/web-monetization-projects/pull/1862#issuecomment-833159649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJL75I47F3IPEOGTHPHNS3TMHWPJANCNFSM44BONDVQ
.

Yeah I thought it needed the full url. I'll double check the notion doc and slack.
…
On Wed, May 5, 2021, 7:31 PM Nicholas Dudfield @.***> wrote: @njlie https://github.com/njlie Seems like @traviscrist https://github.com/traviscrist wants the full url: https://coiltech.slack.com/archives/C01MTJ37Y4D/p1617911934007000 Though I am just scanning that channel, so I could have misread — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1862 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJL75I47F3IPEOGTHPHNS3TMHWPJANCNFSM44BONDVQ .

@mwill8886  Yep it should be the full URL: https://www.notion.so/coil/Tipping-Closed-Beta-5a738a2dc0e8473c80d772f8bbf20462#eb97d5397c194ada8130f9e5d8729358


DOCS: either example is wrong or explanation of handler stack is unclear

This is an issue in the docs.
From here: https://github.com/Seldaek/monolog/blob/main/doc/01-usage.md#core-concepts

Every Logger instance has a channel (name) and a stack of handlers. Whenever you add a record to the logger, it traverses the handler stack. Each handler decides whether it fully handled the record, and if so, the propagation of the record ends there.

Question: traverses the stack in what direction? Bottom to top or top to bottom? Note that the concepts of "bottom" and "top" or "up" and "down" in a stack are well-defined: what you add first is at the bottom, what you add last is at the top, that is by definition. In other words, "pushing" to the stack means adding at the top, "popping" means taking from the top.
Let's read on and see if the question is answered.

This allows for flexible logging setups, for example having a StreamHandler at the bottom of the stack that will log anything to disk, and on top of that add a MailHandler that will send emails only when an error message is logged.

Ok so, in the example, the StreamHandler is explicitly said to be at the bottom of the stack, and the MailHandler is said to be on top of it. My intuition would tend to suggest that the StreamHandler is called first, given that in this example it logs everything, and then it passes the message on to the "next" handler which is the MailHandler, which only handles a subset of the messages. So, this would mean that the stack is traversed from bottom to top.
However, then it continues:

Handlers also have a $bubble property which defines whether they block the record or not if they handled it.

<ASIDE>
Now first of all (and this is besides the point of this issue), when you say that there is a boolean property X that determines whether or not something, you should express it in such a way that when X is true, something is true. In this case, it is reversed. Obviously, $bubble=true means it bubbles, that is, it does not block the record. But I only know that because I am already familiar with the concept of bubbling (in other contexts) and I know that bubbling is the opposite of blocking (when you block something, you stop it from bubbling). If I only read $bubble as a variable name with no intrinsic meaning and were to deduce the behavior from that sentence, I would either get it wrong (i.e. $bubble=true means to block the message), or I would not know (as in "$block defines whether or not to block: which one is true and which one is false?").
</ASIDE>
Ok let's ignore that and get back to the issue.
I was saying, it continues:

Handlers also have a $bubble property which defines whether they block the record or not if they handled it.
In this example, setting the MailHandler's $bubble argument to false means that records handled by the MailHandler will not propagate to the StreamHandler anymore.

Now I am confused, because I was assuming that the stack was being traversed bottom-up, so, changing $bubble to false for the MailHandler wouldn't make a difference in this example (not as far as the two handlers mentioned are concerned).
So, assuming it's not an error in the docs, it must mean my previous assumptions were wrong.
Then the stack is traversed from the top down. Then it makes sense: the MailHandler is met first, and if its $bubble property is false, the message does not propagate to the StreamHandler below it.
But then it would mean that bubbles travel from the top down, which is counterintuitive as hell. In all the contexts where I've ever seen the concept of bubbling (e.g. event frameworks), bubbling is always conventionally pictured as going up, not down. That's why it's called bubbling, because bubbles in real life usually go upwards (at least air bubbles in a liquid).
So now I'm led to seriously question if you actually made a mistake somewhere and switched "top" with "bottom" or "StreamHandler" with "MailHandler" somewhere.
If not, then it means that the stack is traversed from the top down (which is not clearly stated and one has to deduce through an awful lot of reasoning), and that that the verb "to bubble" is used, counterintuitively, to depict the passing of message in the downwards direction.
Or it is an upside-down stack, one that grows downwards.
Note that I'm not being pedantic. I am genuinely not sure, at this stage, in which order I need to push the handlers into the stack to get the desired result.

The stack is indeed correctly built, and as per your expectations, which you can see here:
https://github.com/Seldaek/monolog/blob/3962ebfe206ac7ce6c754c79e2fee0c64bf1818d/src/Monolog/Logger.php#L184-L203
The stack is then traversed top to bottom, as per this code:
https://github.com/Seldaek/monolog/blob/3962ebfe206ac7ce6c754c79e2fee0c64bf1818d/src/Monolog/Logger.php#L289-L328
I am not entirely sure what lead you to believe the opposite:

Ok so, in the example, the StreamHandler is explicitly said to be at the bottom of the stack, and the MailHandler is said to be on top of it. My intuition would tend to suggest that the StreamHandler is called first, given that in this example it logs everything, and then it passes the message on to the "next" handler which is the MailHandler, which only handles a subset of the messages. So, this would mean that the stack is traversed from bottom to top.

You make a big assumption there with the fact that StreamHandler passes records to the next handler. The top level handlers all receive the records in order (top to bottom of stack) until bubbling is interrupted.
--
As for the bubbling down, instead of up.. well there I gotta say you got me, I really did not consider this nomenclature fuckup back then (I guess my mental representation is more one of bubbling to the next, rather than up per se) and I don't really see what can be done to fix it except documenting it better. I see your point about Handlers also have a $bubble property which defines whether they block the record being unclear as hell, but the reason I phrased it like that was that I am not sure how to otherwise explain bubbling to someone not familiar with the concept.
If you feel like sending a PR with doc improvements now that you hopefully grasp things better, that would be great.


Clean up warning regarding OCMVerify due to init issue

See #390 for details on init issue.
Not sure if you'd prefer to keep the warning or mask it for the time being with this fix.

It's easy to forget to remove this later, and I assume this will be fixed. So, I'd rather not merge this.


React async compatible SelectList

Part of #216
Follows the react docs guide for this kind of migration here https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html#updating-state-based-on-props

Deploy preview for gestalt ready!
Built with commit c3fd1300448a6749404c330a7bfdc776efd3e57f
https://deploy-preview-221--gestalt.netlify.com

Warnings

:warning:

Bundle size increase

Filename
Size Diff
Gzip Diff
Prev Size
Current Size
Prev Gzip
Current Gzip

gestalt.js
:small_red_triangle: 0.0%
:small_red_triangle: 0.1%
264.48 KB
264.54 KB
58.98 KB
59.05 KB

gestalt.es.js
:small_red_triangle: 0.0%
:small_red_triangle: 0.1%
261.93 KB
261.99 KB
58.62 KB
58.68 KB

  Generated by :no_entry_sign: dangerJS

Codecov Report

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

@@           Coverage Diff           @@
##           master     #221   +/-   ##
=======================================
  Coverage   61.05%   61.05%
=======================================
  Files          40       40
  Lines         796      796
  Branches      186      186
=======================================
  Hits          486      486
  Misses        219      219
  Partials       91       91

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 293ea85...c3fd130. Read the comment docs.


Doesn't work on th-ch

I click the "import custom css file", but it doesn't work at all.
(th-ch v3.2.2)

@uynilo9 I just came across this issue myself. The issue looks to be with trying to reference the style using @import. It should work if you go into the css file you want in this repo and copy its contents into a css file on your machine.
There doesn't look to be any feedback in the app when the css file is imported but you need to go to Navigation > Restart App after importing the file.
Hope that helps you!

@MikeVensel It actually works. Thank you so much for help <3

No, I did that and it still does not work. No theme gets applied. Using th-ch on Mac


The capital of "settling in MB" is small

Describe the issue and expected behaviours. If this is a bug, describe the steps to reproduce the problem, what you observe, and what you expected to observe.
Acceptance Criteria

[ ]

Steps for QA:

Open Learn all about Manitoba or recommended topics: settling in MB should be Settling in MB. It should start with a capital.

Dupe of #1593


improve import matching

Currently the import command matches very few resources, which results in lots of recreated resources after importing. There are a couple of routes we can take with this, and maybe we even want a hybrid of both:

We could go down a more complex auto-matching route which downloads existing resources and compares them to desired resources.
We could let the user manually import each matching resource and directly tell Mantle which ones match. This is what Terraform does (see https://www.terraform.io/cli/import).

Adding this to milestone v1.0.0 because import should be considered stable for production use


Window is restored after each computer unlocking

Windows Terminal version
1.17.11461.0
Windows build number
10.0.22621.0
Other Software
No response
Steps to reproduce

Enable the setting "New instance behaviour": "Add to most recently opened window on this desktop"
Open a terminal window
Minimise it
Lock the computer
Unlock the computer

Expected Behavior
The minimised window doesn't move and stays where it is, minimised.
Actual Behavior
The Terminal window is now restored and visible on my screen after unlocking. Every time.
I suspect the mentioned setting has something to do with it. I could only observe this after setting it. I did this to reduce the number of windows for multiple long-running background console applications. Other than that, it's a normal and fresh Windows 11 setup with all hardware drivers, including AMD.
I also suspected a scheduled task to be run as console application after locking or unlocking the computer. That might explain why the Terminal window gets restored. After disabling all of them the behaviour remains though. So even if it's caused by this or not, the behaviour is still undesired. The Terminal must be able to remember and keep its window state unless the user interacts with it.

I have seen the AMD driver software attempting to spawn a console window on login or wake from sleep. I do not know whether it uses a scheduled task.
Unfortunately, this is not something we can ultimately control: if we provide a setting that suppresses all console application foreground requests, we will invariably encounter users who turn it on and are then deeply confused or concerned that they don't get console windows any longer.
There is no way for us to determine that a given console application is not, in fact, trying to be in the foreground.
Oh wait, there is.


Stuck in Rancher/Homestead dashboard, tray menu no longer works

The only Tray menu that I'm interested in in this context is "Preferences", but the UI stays on the Homestead dashboard.
No error or warning messages in appear in the starting terminal session or in the dev-tools console.
This is with commit https://github.com/rancher-sandbox/rd/commit/35d7edd28e5899a846d0c843c52cf0531c8641a4 (basically merging #106 into main)

can't repro after a clean rebuild


doc: Update HTTP/2 METADATA documentation.

This commit updates the documentation for HTTP/2 METADATA in Envoy,
particularly the class names referenced in the metadata flow.
Signed-off-by: Dianna Hu<EMAIL_ADDRESS>
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @alyssawilk

Thanks for the review! And whoops yeah, I'll aim for 100 chars next time (will hold off on that here to avoid even more diffs :P) Thanks!


setEddi ON or OFF

Is there a node to turn the Eddi ON or OFF ?
I have been using NodeRed for months to control my Eddi, but I am suddenly getting an error
RequestError: write EPROTO C0D71D74427F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:355:
I simply have a http request node to turn the Eddi ON with https://s18.myenergi.net/cgi-eddi-mode-E[myeddi]-1 or OFF with https://s18.myenergi.net/cgi-eddi-mode-E[myeddi]-0
Is there any chance of a setEddi node for NodeRed ?

From what I can see, you are probably using node-red-contrib-myenergi which seems to lack the support for setEddiMode.
A good idea is to create an issue in that repository, or event submit a pull request.

Sorry, are you saying that your DOES have a SetEddi mode ?

Sorry I don't have an Eddie to test with, but if someone wants to raise a pull request il happily merge it


DRILL-7206:using primitive int list at right or full join case

This change is to avoid the unneeded box ,unbox operation.

There is no link to Jira (PR name and commit message are invalid).

@arina-ielchiieva thanks for the tip.

@Ben-Zvi could you please review?


improvement(tar_toolchains): also search for bsdtar on host platform

Fixes #788

Type of change

Bug fix

Test plan
No change in test coverage.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

In nix, bsdtar is provided by the libarchive package:
$ which bsdtar
/nix/store/w9m2y5kpmgs342fnmksirvhiqrmqh08j-libarchive-3.6.2/bin/bsdtar

Thanks! But our plan has been to provide a pre-built bsdtar binary for darwin as well - this is replaced by https://github.com/aspect-build/bazel-lib/pull/804


feat: Add TypeScript definitions for status flags

This PR adds the new status flags to the type definition as discriminated unions

@JakeGinnivan I just started using this library in a project and this was the first pain point I came across. Thanks for addressing this! 🎉

@JakeGinnivan Hey, thanks for PR something I was looking for. I also have a question do you think it's a good idea to make status an exportable type?
export type Status = 'loading'| ect.'

:tada: This PR is included in version 2.0.0-next.7 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed all Android tests

This pull request makes sure all existing Android / Java unit tests run successfully.
It also contains an abstraction of the CameraCharacteristics class which makes it easier to mock these values when testing methods in the Camera class.

Awesome job!! This is great to see. Thank you.

My (working)day is almost at an end. I will continue tomorrow and start writing more methods to test the Camera class.


ctrl+f and ctrl+b broken after upgrade to Atom 1.1

Please provide more details about your setup; OS, installed packages, etc.

Sure thing -- OSX El Capitan (pretty standard setup) and here's a dump of my plugins. Downgrading fixed the issue.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

@damassi can you reproduce with safe mode? You can launch Atom in safe mode with atom --safe in the terminal or Application: Open Safe in the command panel.

I was going to propose the same, but vim-mode is not a core package, so it'll be disabled when running in safe mode.

Whoops!

Yeah, my setup is nothing special. Could someone please see if paging works with 1.1?

I'm seeing that the editor scrolls correctly, but the cursor doesn't move correctly as you scroll. Is that what you're seeing @damassi?

Exactly. Like if you page down or up the cursor will stay behind

+1

Also seeing this with Ctrl+D, Ctrl+U on Atom 1.1.0 and atom-vim 0.62.0. The cursor doesn't follow the paging which it should.

+1, seeing this as well

Hey everyone, sorry for not noticing this before we shipped v1.1.0. I believe this is fixed in vim-mode 0.63. Thanks for the reports.

Thanks for the fix!


$sqrt[number]

Type

[x] Functions: $sqrt

Description
Finds the square root of the entered number.
$sqrt[num]
$sqrt[81] //9
$sqrt[2] //1.41421356237

@falsisdev $math[9**2]
¯_(ツ)_/¯

uh  😔

Do I find the square root of 81 as 81//2 xd

Do I find the square root of 81 as 81//2 xd

$math[81**(1/2)]

no because i made a code to find the square root of 81 not 9².

Do I find the square root of 81 as 81//2 xd

$math[81**(1/2)]

k wait

Do I find the square root of 81 as 81//2 xd

$math[81**(1/2)]

yes thx

Thanks for adding this, it's very nice!

Ah but I guess it was already done and I'm sorry about that :(

Cool function

A function that can be done with Math.sqrt(key)

A function that can be done with Math.sqrt(key)

or $math[$message2]
or $djsEval[42;yes]

Ok, no need 😄

Still i liked his efforts and am using it for my bot. Good job bro :)

very thx ♥😄


Missing OCR text for many images

A few examples:

702198b — text on brown backing paper
706410b — brown backing with text
709457b — grayscale with text but no OCR
729236b — grayscale with text but no OCR
711642b — Missing text from color image
711564b — Missing text from color image
716490b — Missing text from color image
731966b — Missing text from gray image (why?)
703429b — Missing text from color image

Based on my survey, ~20% of images have text on the back that was not OCR'd.

In that list, 8/9 were missing from the NYPL's S3 bucket. 731966b was actually the front of the image.
@riordan There were 30,413 back of the card images in the S3 bucket, but ~43,000 photos in the CSV file that Matt originally sent me. Is there any chance we could recover more of them?

I'll try.


tado switching on/off does not work

Home Assistant release with the issue:
0.90.1
Last working Home Assistant release (if known):
0.86
Operating environment (Hass.io/Docker/Windows/etc.):
docker
Component/platform:
tado climate component
Description of problem:
I recieve a 422 from my.tado.com when I switch to off
Additional information:
HTTP Error 422:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/websocket_api/commands.py", line 122, in handle_call_service
    connection.context(msg))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_component.py", line 188, in handle_service
    self._platforms.values(), func, call, service_name
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 314, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 328, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/tado/climate.py", line 214, in turn_off
    self._control_heating()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/tado/climate.py", line 365, in _control_heating
    self._store.set_zone_overlay(self.zone_id, CONST_OVERLAY_MANUAL)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/tado/__init__.py", line 122, in set_zone_overlay
    self.tado.setZoneOverlay(zone_id, mode, temperature, duration)
  File "/usr/local/lib/python3.7/site-packages/PyTado/interface.py", line 287, in setZoneOverlay
    data = self._apiCall(cmd, "PUT", post_data)
  File "/usr/local/lib/python3.7/site-packages/PyTado/interface.py", line 81, in _apiCall
    response = self.opener.open(req)
  File "/usr/local/lib/python3.7/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/usr/local/lib/python3.7/urllib/request.py", line 641, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/local/lib/python3.7/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/usr/local/lib/python3.7/urllib/request.py", line 503, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python3.7/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 422:

I just saw, that no tado-mode is working anymore. I have to do further investigations :/

would be great to get this solved as I used an automation which switched between OFF and Tado-mode as a function of opening/closing windows

I can only work on the weekend on this, because I have to test it with a different hass installation (I am using hass os)

Add me to the list aswel :(
'''
Traceback (most recent call last):
File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 122, in handle_call_service
connection.context(msg))
File "/usr/src/app/homeassistant/core.py", line 1138, in async_call
self._execute_service(handler, service_call))
File "/usr/src/app/homeassistant/core.py", line 1160, in _execute_service
await handler.func(service_call)
File "/usr/src/app/homeassistant/helpers/entity_component.py", line 188, in handle_service
self._platforms.values(), func, call, service_name
File "/usr/src/app/homeassistant/helpers/service.py", line 314, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/app/homeassistant/helpers/service.py", line 328, in _handle_service_platform_call
await getattr(entity, func)(**data)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/tado/climate.py", line 214, in turn_off
self._control_heating()
File "/usr/src/app/homeassistant/components/tado/climate.py", line 365, in _control_heating
self._store.set_zone_overlay(self.zone_id, CONST_OVERLAY_MANUAL)
File "/usr/src/app/homeassistant/components/tado/init.py", line 122, in set_zone_overlay
self.tado.setZoneOverlay(zone_id, mode, temperature, duration)
File "/usr/local/lib/python3.7/site-packages/PyTado/interface.py", line 287, in setZoneOverlay
data = self._apiCall(cmd, "PUT", post_data)
File "/usr/local/lib/python3.7/site-packages/PyTado/interface.py", line 81, in _apiCall
response = self.opener.open(req)
File "/usr/local/lib/python3.7/urllib/request.py", line 531, in open
response = meth(req, response)
File "/usr/local/lib/python3.7/urllib/request.py", line 641, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/local/lib/python3.7/urllib/request.py", line 569, in error
return self._call_chain(*args)
File "/usr/local/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/usr/local/lib/python3.7/urllib/request.py", line 649, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 422:
'''

For me the same:
home assistant v0.90.2
HTTP Error 422:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/websocket_api/commands.py", line 122, in handle_call_service
    connection.context(msg))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_component.py", line 188, in handle_service
    self._platforms.values(), func, call, service_name
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 314, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 328, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/tado/climate.py", line 214, in turn_off
    self._control_heating()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/tado/climate.py", line 365, in _control_heating
    self._store.set_zone_overlay(self.zone_id, CONST_OVERLAY_MANUAL)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/tado/__init__.py", line 122, in set_zone_overlay
    self.tado.setZoneOverlay(zone_id, mode, temperature, duration)
  File "/usr/local/lib/python3.7/site-packages/PyTado/interface.py", line 287, in setZoneOverlay
    data = self._apiCall(cmd, "PUT", post_data)
  File "/usr/local/lib/python3.7/site-packages/PyTado/interface.py", line 81, in _apiCall
    response = self.opener.open(req)
  File "/usr/local/lib/python3.7/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/usr/local/lib/python3.7/urllib/request.py", line 641, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/local/lib/python3.7/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/usr/local/lib/python3.7/urllib/request.py", line 503, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python3.7/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 422:

for some reason I'm still struggling with switching my Tado off even in one newest release.
the error message looks a bit different

It's the same error message and it's because this is not yet released.

OK, I thought that the PR was merged. I actually manually modified the two files according to then PR but then my climate objects are gone. Do i also have to update something else in addition?

It will be in 0.91.2

I'm on Home assistant 0.98.2 and I still have this issue:
When I try to change the mode to heating, auto or somethings else:
homeassistant.components.websocket_api.http.connection.1789631152] HTTP Error 422:


Align center tag content

Hi!
Congratulations for the library, it´s amazing. I would like to ask if there is any way to center horizontal tags, instead of floating them left (align left). Or if you have any clue where I may be working around to get it.
Thank you!.

I would also like to know how to do this


Issue: Entity extraction using custom rules

Issue you'd like to raise.
I would like to perform a query on a database using natural language. However, running direct queries is not possible, and I have to do it via an API. For that, given a sentence, I'd like to extract some custom entities from it.
For example, if the sentence is: "How many more than 20 years old male users viewed a page or logged in in the last 30 days?"
The entities are:
<gender, equals, male>,
<age, greater than, 20>,
<event name, equals, view page>,
<event name, equals, login>,
<event timestamp, more than, 30 days>

The first element of each entity (triplet) comes from the list of columns
The second element is inferred from context (nature of the operator if it's a single value or array to compare with)
The third element is also inferred from the context and must belong to the chosen column (first element)
I'm not able to restrict either of these elements for the entity. I'd like an agent first to check all the columns that are available, choose one and view their unique values. Once it gets that, either choose that column (first element) and value (third element) or look again and repeat these steps.
Any help on this would be great!
Suggestion:
No response

Not sure whether I interpreted it correctly or not, but this is what I tried out -
import json
from pprint import pprint
from langchain.llms import OpenAI
from langchain import PromptTemplate

llm = OpenAI(temperature=0, verbose=True)

template = """You need to extract entities from the user query in specified format.
Extracted entities always should have valid json format, if you don't find any entities then respond with empty list.

Entity Format: List of dict, where each dict having format as {{"entity":"{{entity key}}", "operator":"{{valid sql operator}}", "value":"{{value of entity}}"}}

You need to extract below mentioned entities:
gender: str or list, possible values = [male, female]
age: int, represent age in years
event_name: str or list, possible values = [login, view_page, home_page, contact_us]
event_timestamp: int, represents days for comparing with current date

Use the following format:
User Query: Question here
Entities: Extracted entities in valid json format here

User Query: {query}
Entities:
"""

prompt_template = PromptTemplate(
    input_variables=["query"],
    template=template
)

Example 1:
query = "How many more than 20 years old male users viewed a page or logged in in the last 30 days?"

resp = llm(prompt_template.format(query=query))
pprint(json.loads(resp))

[{'entity': 'gender', 'operator': '=', 'value': 'male'},
 {'entity': 'age', 'operator': '>', 'value': '20'},
 {'entity': 'event_name', 'operator': 'IN', 'value': ['login', 'view_page']},
 {'entity': 'event_timestamp', 'operator': '<', 'value': '30'}]

Example 2:
query = "How many users have visited home page in last week?"

resp = llm(prompt_template.format(query=query))
pprint(json.loads(resp))

[{'entity': 'event_name', 'operator': '=', 'value': 'home_page'},
 {'entity': 'event_timestamp', 'operator': '<=', 'value': '7'}]

You can modify the prompt by updating possible values for each of the entity.
You can create agent with custom tools as specified below:

Tool 1 - Wrap this logic as a initial entity extraction tool
Tool 2 - API integration to get actual result

Hope this helps!
Let me know your thoughts

@shashankdeshpande
Thanks for this elaborate response. It definitely does work as expected.
However, what I've not mentioned clearly (my bad:() is that the number of columns can be variable, and so can the values in them. Hence, whenever a prompt comes, one agent should find the entities and iterate over them. A second agent should look at all the columns, and a third agent should look at agent2's chosen column's unique values. Together by feedback passing, they should concur at a correct column name and the value (i.e., first and third values of the triplet, respectively).

Thanks for your response.
Can you handle it using below custom tools?

Columns Identifier - Custom function which will retrieve all possible columns and respective values
Entity Extraction - Make use of above mentioned prompt after modify it by using output of column identifier tool
API call - Use output of entity extraction to call relevant api and get desired results

Ultimately answer will be derived by calling an API (internally database query), so columns and values can be identify initially is what I thought.

@shashankdeshpande
I see. Yes, this is exactly what I thought of doing. So there are two tools as of now

Get column names - A custom function which gets all the column names
Get all values - A custom function that gets all the unique values of a particular column

Thanks to your answer, I'll add your prompt as a separate agent (LLM based). I was previously using it in the agent's prompt.
The problem with this is that the agent is not able to iterate across the discovered entities. It takes a single pass through the whole dataset, never calls the second tool (get all values) and returns as is.
Some novice questions

Say I add an LLM (your approach) and get all the entities. How do I use the other tools (schema and unique values) to solidify the selections that are made
Can I get the entities first (by using the knowledge of the database i.e., column names and unique values) and then iterate on these entities for a second time to refine them?

@saswat0 I understand your perspective.
Here is my proposed approach. Follow these steps sequentially:

Retrieve all available columns and their corresponding possible values at once.
Update the entity extraction prompt with all these details and extract all entities.
Utilize the extracted entities to call the API and obtain the desired result.

It seems like you are considering extracting each entity individually and refining them by matching with possible values. However, an alternative approach would be to provide all the information to LLM at once, allowing it to make decisions and extract the entities. Further refinement may not be necessary.
To implement this, you can modify the agent prompt to instruct the LLM to consistently invoke the specified tools (Column & Values Identifier, Entity Extractor, API) sequentially.

@shashankdeshpande
If I provide all the column names and their unique values, I'm afraid that might exceed the input token length. Also, when/where will these tools be used then? Or am I not understanding you correctly?

@saswat0
I understand your concern about number of tokens.
However if you want to experiment with proposed approach, below mentioned resources might be helpful -

Create custom agent - https://python.langchain.com/docs/modules/agents/how_to/custom_agent.html
Create custom tools - https://python.langchain.com/docs/modules/agents/tools/how_to/custom_tools.html


Weirdness with pagePrelude

Using <%! img-local .... %> in a page.
When the img.tcl is loaded in the page, via <% interp-source img.tcl %> all is fine, i.e. the image is in the page. If the command to source img.tcl is in the pagePrelude the image reference is rendered as a markdown code block instead ...
Aha, found the issue!
I wrote the prelude like a Tcl block, nicely indented in the website.conf.
So it ended in a new line of just 4 spaces. i.e.
        pagePrelude {
          <%! interp-source ... %>
        }

When it got assembled with the actual page these 4 spaces indented the first line of the page, which had the logo reference. Markdown then saw the indented line and said, ok, this is code, and rendered it as such.
When I rewrote the prelude to
        pagePrelude {<% interp-source ... %>}

i.e. eliminated the trailing spaces the render was ok again.
I believe that the general fix would/should be to trim trailing spaces from the prelude, and separate it from the regular content by at least a single empty line.

Unable to verify.
My fork is uptodate with a9d269c (actually one past that), and has no local changes.
Changing the prelude back to be without trailing spaces and it is ok again.
I will have a look and submit a pull request after I figure this out.
Together with an issue on another page where I see my macro code generating two tables, yet only the first appears in the output I might actually have a larger pull request implementing a dump feature where ssg dumps all stages of processing a file into a temp dir for analysis, i.e. input, past macro processing, past markdown, setup/past the templating stages, etc.

I am able to verify the change of variables to settings however, and that works, after me updating my shortcuts, so that is good.

Good prelude
==> website/tmp/logo_d2Vic2l0ZS9pbnB1dC9wYWdlcy9sb2dvLm1k.content-0-raw <==
<%!iref logo%>

==> website/tmp/logo_d2Vic2l0ZS9pbnB1dC9wYWdlcy9sb2dvLm1k.content-1-2expand <==
<% interp-source shortcuts.tcl ; interp-source img.tcl %><%!iref logo%>

==> website/tmp/logo_d2Vic2l0ZS9pbnB1dC9wYWdlcy9sb2dvLm1k.content-2-markdown <==

"Bad" prelude
==> website/tmp/logo_d2Vic2l0ZS9pbnB1dC9wYWdlcy9sb2dvLm1k.content-0-raw <==
<%!iref logo%>

==> website/tmp/logo_d2Vic2l0ZS9pbnB1dC9wYWdlcy9sb2dvLm1k.content-1-2expand <==
        <% interp-source shortcuts.tcl ; interp-source img.tcl %>
    <%!iref logo%>

==> website/tmp/logo_d2Vic2l0ZS9pbnB1dC9wYWdlcy9sb2dvLm1k.content-2-markdown <==

Input (0-raw) is the same. With prelude (1-2expand) added the iref gets indented from the prelude content. This indentation is left after expansion (2-markdown), and markdown renders it as code block.
My fix is to put a newline between prelude and content.
That works.
Dropping the whole trim-indentation works as well, as long as there is a newline between prelude and actual content.
Note: [join [list $a $b $c] ""] is the same as  $a$b$c, just not as readable IMVHO.

My fork is uptodate with a9d269c (actually one past that), and has no local changes.
Changing the prelude back to be without trailing spaces and it is ok again.
I will have a look and submit a pull request after I figure this out.

I should have been more clear about what this update does. It does not remove trailing spaces from the prelude, rather, it just unindents it by as many spaces as possible and removes those lines at the beginning and the end of the text that turn out empty as a result. This means it will help with
    pagePrelude {
      <% interp-source img.tcl %>
    }

but won't with
    pagePrelude {<% interp-source img.tcl %>      }

The reason for this approach was to allow the user to use the prelude that would modify the first line of the content if that's what he wants. On second thought, this is too arcane to matter.
I will keep the trim-indentation and insert a newline after the prelude. The reason trim-indentation is there is so that
pageSettings {
    pagePrelude {
        Content:

        <%! some-command %>
    }
}

wouldn't produce fixed-width content but
pageSettings {
    pagePrelude {
        Content:

            <%! some-command %>
    }
}

would.

Note: [join [list $a $b $c] ""] is the same as $a$b$c, just not as readable IMVHO.

I find
[join [list [long-command-1 ...]\
    [long-command-2 ...]] ""]

more readable than
"[long-command-1 \
    ...][long-command-2 ...]"

when line wrapped and it is harder accidentally introduce a space this way. Note that I do not use string cat for 8.5 compatibility (which is a goal for Tclssg).

Heh. My preference in such a case then becomes to use helper variables to get the strings and then assemble the final form from these variables. Partially a master of taste.

My preference in such a case then becomes to use helper variables to get the strings and then assemble the final form from these variables.

That's probably a better solution in most cases. The only downside is if you use it in a proc like compile-website where there are lots of local variables that you might accidentally affect. (Though I suppose you could make those variables constants after they are first set by tracing attempts to write to them and raising an error.)

Another possibility is to give either the proc-local or namespace variables some sort of prefix in their name which makes them quickly identifiable (In OO work I like to name instance variables as "my..." to identify them).


Not render long field

What happened?
I checked all the previous versions. This problem began starting with 5.0 versions, at 4.26 this problem does not.
DQL
No response
JS
No response
Dataview Version
0.5.36
Obsidian Version
0.14.15
OS
Windows

Related: #1201

Should be fixed in 0.5.37.


Return a Java/Scala data structure instead of DataFrame for queries with Spark?

What kind an issue is this?

[ ] Bug report. If you’ve found a bug, please provide a code snippet or test to reproduce it below.
The easier it is to track down the bug, the faster it is solved.
[x] Feature Request.

Feature description
Is it possible , or desirable for the connector to return a regular data structure (like a List) instead of a data frame?
For example , I have a Dataframe containing a list of cities as following :
val cities    = sc.parallelize(Seq("New York")).toDF()
Now , for each city , I would like to query Elastic and build a set of results similar to the following logic :
val cities    = sc.parallelize(Seq("New York")).toDF()
   cities.foreach(r => {
    val city = r.getString(0)
    val dfs = sqlContext.esDF("cities/docs", "?q=" + city ) //returns a DataFrame which triggers a null pointer in Spark
    })

Problem is that Spark does not allow nested operations that return dataframes. I think this problem could be resolved if I could get a regular data structure out of the Elastic connection (like a List)

Closing this because it's a feature that is not within scope of ES-Hadoop. For synchronous read operations within a Spark function you should use the Java Rest Client.
This is elaborated further on the forum post: https://discuss.elastic.co/t/how-do-i-build-results-dinamically-from-a-dataframe-apache-spark/162366


More detailed documentation please

I'm interested in getting notifications for every Sentry error in my project. This appears to be my only hope to notify Sentry errors in Telegram.
However I'd like more detailed documentation on how to set this up. I have no idea where to install this package (somewhere on Sentry or locally, and if locally how would it work).

Hello!
Thank you for your message.
I suppose that you may mean sentry.io - "cloud" version sentry as a service. Is it?
If so, there is no way to use this plugin with cloud-sentry, unfortunately. You may use it with self-hosted Sentry only.
Talking about Sentry.io, you may ask support about the on-demand installation of the plugin, but I'm not sure that the support will be able to do it for you.

I wasn't aware that Sentry has two different versions. Thanks!


button not working

When  i've done everything i clicked the button  "Run tests", but it did not work. Also the button was staying green, when i clicked in the editor it started again being white

@leonidiudakov, please provide the challenge name and your code. Also include which tests pass and which don't.

Please clarify as requested.


Buttons don't have inset shadow on active.

The Bootstrap 4.6 spec says

Buttons will appear pressed (with a darker background, darker border, and inset shadow) when active

On inspecting I didn't see any inset box shadow being applied. Not only that, doing ctrl + F on the whole bootstrap css file  for inset keyword doesn't match anything.
Are we really supposed to have an inset/inner shadow, or is it a typo?

Nearly all shadows are disabled by default. We could update the docs messaging to reflect that.

@mdo On top of that there should be at least one demo of how would the button look like after setting the scss variable yes for the inset shadow. People might make a decision on the basis of looks, rather recompiling the scss yourself to see how it looks with inset shadow and then probably not deciding to use it.

Fixed by #34966


V7.1-contentshare : fixes broken images on content share

@bzang does any of this look like it'll cause problems with the widgets?

From a widget perspective, this shouldn't cause any issues.

can this be closed?

Merged and closed with https://github.com/ciscospark/spark-js-sdk/pull/585


Separate service unavailable and replica error

When an engine had no available backend, the controller emitted a message stating "...no available backend...". Afterward, the volume controller blindly marked all replicas as failed.
To create a RWX volume, it was first created on node A, and then the sharemanager resource was created with node A as the owner. The sharemanager controller then created a sharemanager pod, which might be located on node B. After the pod was created, the sharemanager resource's owner was transferred to node B, causing the volume to detach from node A and attach to node B.
However, if replicas were deleted because of detachment, the in-progress engine instance's startup would fail due to the "...no available backend..." error. This caused all replicas to be marked as failed (healthyAt is empty and failedAt is set), and they could not be salvaged anymore. As a result, the volume became faulty.
To avoid the blindly marking failed operation, we should separate the recoverable and unrecoverable error. For a recoverable error, for example, the replica instance is deleted, the replica is not really failed, the replica should not be marked as failed directly.
To prevent blindly marking replicas as failed, recoverable and unrecoverable errors can be separated. The manifest corruption can be regarded as a unrecoverable error. For a recoverable error, for instance, if a replica instance is deleted and the controller is disconnected with it, it should not be marked as failed directly since the replica are somehow stopped rather than corrupted. In this case, avoiding marking all replicas failed can help the volume not trapped in a faulty state and reattach to a node.
Longhorn/longhorn#5537

But what if the replica is running for just several seconds then get failed? For example, the work directory is read-only, I haven't tested this example if this is possible but we cannot guarantee the similar issues won't happen...

If the replica server can error out and does not die accidentally, the error is regarded as unrecoverable. Then, the replicas can still be marked as failed.

GRPC UNAVAILABLE definition.

The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff. Note that it is not always safe to retry non-idempotent operations.

f the replica server can error out and does not die accidentally, the error is regarded as unrecoverable. Then, the replicas can still be marked as failed.

Yes, this is just a current error handling.

@Mergifyio backport v1.3.x v1.4.x


Segment list should not be created for feature flag which doesn't exist

Issue:
In the add list, we can only select a segment if it exists with the same context as the feature flag, but while importing, we haven't applied any validation to make sure the segment list that is getting created already exists. This might apply to groups as well.
(For this case warning should be shown on import while creating but was not showing)

A validation was also added to check multiple imports of duplicate files as the second file will try to create on key already used and throw an error.

segment list should be ignored if it doesn't exist but here that's not happening and it is getting created.
Also, the segment list validation is just checking the id and attaching a list to a segment with a different context which shouldn't be allowed.

I will QA this

QA passed


Missing semicolon in _search.scss

Line 35 of _search.scss is missing an ending semicolon in v1.0.0-beta.36.

thanks @ajbroadbent #697


ORC-899: Archive Apache ORC 1.4.x in releases page

What changes were proposed in this pull request?
This PR aims to mark Apache ORC 1.4.5 as archived instead of stable.

http://localhost:4000/docs/releases.html

Why are the changes needed?
Most community are currently using Apache ORC 1.5.x and moved on Apache ORC 1.6.9 already.

2021-07-02 Apache ORC 1.6.9 is released.
2021-07-02 SPARK-35992: Upgrade ORC to 1.6.9
2021-07-16 ICEBERG: Upgrade ORC to 1.6.9
2021-07-26 HIVE-25384: Bump ORC to 1.6.9
2021-07-30 ARROW-13506: Upgrade ORC to 1.6.9
2021-07-31 Apache Druid: Upgrade ORC to 1.6.9
(Under Review) FLINK-23551 Bump ORC to 1.6.9

Apache ORC 1.4 was released on 2019-12-09 and it's time to mark it archived because we are not going to maintain it.
Apache ORC 1.0/1.1/1.2/1.3 are marked as archived explicitly.
How was this patch tested?
N/A

Could you review this, @omalley , @pgaref , @wgtmac , @williamhyun ?
I saw ORC-896 is filed against Apache ORC 1.4.4, but we are not maintaining it.
We had better update our website.

Could you review this, @omalley , @pgaref , @wgtmac , @williamhyun ?
I saw ORC-896 is filed against Apache ORC 1.4.4, but we are not maintaining it.
We had better update our website.

Yeah, had the same thoughts when looking at ORC-896

Thank you, @pgaref .
BTW, Java16 failure is due to GitHub.com connection timeout. It seems that were a network issue from GitHub.com. Since it's irrelevant, I'll merge this.
Error: fatal: unable to access 'https://github.com/apache/orc/': Failed to connect to github.com port 443: Connection timed out
  The process '/usr/bin/git' failed with exit code 128


hole punching alternative

I have read in your webpage that the latest release of TomP2P does not support hole punching. I would like to know if TomP2P has any alternative to send direct messages between to peers in different networks, that is, between NAT-ed LAN networks, either implemented in the library or planned to be in the future. If it exists, is there any example available?

You can check this example
TomP2P/examples/src/main/java/net/tomp2p/examples/ExampleHoleP.java

I tested it a few weeks ago, but throws me a NullPointerException at line 43, when it sends a message from "unreachable1" to "unreachable2". I don't know if is a library problem or my dev environment. However, thanks for your help!

Any progress on this?

Still no answer from main developers :-/

Sorry for the delay, we are working on https://github.com/jonaswagner/sctp4j, which will make hole punching much easier. The idea is to have SCTP tunneling over UDP. That means if we have a UDP connection we can "upgrade" to SCTP. That also means we will ditch TCP and use UDP and SCTP only.


Fail in using OpenCVSharp VideoWriter

I can successfully read picture from a video file and edit and show the picture, but when I try to
save some pictures in a video file, I failed. After the programme is runed, there is no
"video_save.avi" file. If you are familiar with OpenCVSharp VideoWriter, would you please
do me a favor and find out where comes the problem.
The software is Visual Studio 2017. Codes are as follow:
VideoCapture capture = new VideoCapture(@"E:\video.mp4");
Mat image = new Mat();
capture.Read(image);
Cv2.ImShow("output", image);
OpenCvSharp.Size frame_size = new OpenCvSharp.Size(960, 544);
FourCC codec = FourCC.MPG4;
VideoWriter video_save = new VideoWriter(@"E:\video_save.avi", codec, 60, frame_size, true);
int i = 10;
while (i > 0)
{
i--;
capture.Read(image);
Cv2.ImShow("output2", image);
video_save.Write(image);

//MessageBox.Show(i.ToString());

}
video_save.Release();

Are you using OpenH264 dll to write your video.
you need to place the openh264 dll in your debug folder where the application is running.

I generated the OpenH264.dll files using MinGW and place the file in debug folder, but it doesn't work seemingly. After the program is run I still can't get the “video_save.avi” file. I try to add the OpenH264.dll as a reference in VS but VS report error. Maybe the way I use OpenH264.dll is wrong?

Hi, Thank you for your advice. I generated the OpenH264.dll files using MinGW and place the file in debug folder, but it doesn't work seemingly. After the program is run I still can't get the “video_save.avi” file. I try to add the OpenH264.dll as a reference in VS but VS report error. Maybe the way I use OpenH264.dll is wrong?

Just place the dll directly in the debug folder. and make sure the openhdll version is compatible with OpenCVSharp version

Thank you very much! I download OpenH264.dll file, place it in debug folder and creat the video file using C# console application. The video file can be played successfully. But when I turn to C# Windows Forms Application. The program still can't creat the video file.

Thank you very much! I download OpenH264.dll file, place it in debug folder and creat the video file using C# console application. The video file can be played successfully. But when I turn to C# Windows Forms Application. The program still can't creat the video file. Error is reported as follow:
[ERROR:0] global C:\lib\opencv2\modules\videoio\src\cap.cpp (419) cv::VideoWriter::open VIDEOIO(CV_IMAGES): raised unknown C++ exception!

Thank you very much! I download OpenH264.dll file, place it in debug folder and creat the video file using C# console application. The video file can be played successfully. But when I turn to C# Windows Forms Application. The program still can't creat the video file. I'm very confused...

@seaboye  any update?

I have found that I have to set the System.Environment.CurrentDirectory variable to where the native dlls are located when writing videos (in F# scripts).
let path =<EMAIL_ADDRESS>System.Environment.CurrentDirectory <- path

Please close this issue.


initial attempt at an Open API description of TAP

this is TAP-1.1 with parameters
the UWS portion is incomplete but enough to see how to ref the VOSI portion is incomplete but includes some of the user table stuff that is intended for TAP-next
the commented out URLs in openapi.yaml work if the yaml is located at a reachable URL (currently not)

tap-params.yaml -  I was trying to make a single "set of parameters" but could not find a valid way to $ref that in the 3 places it is needed, but maybe the individual parameter definitions are better (more reusable) anyway. I kept this file for now but it is not used.


Publishing Module to Packagist from inside /Modules

I have created a few modules inside of the main Modules folder but i want them to be reused across all my applications. Submitting to packagist using the normal methods requires me to have that module alone in a repo but im sure there was a way to publish withing the Modules using the terminal. Can anyone help here

I have not tried this myself, but I do think it should be possible to link to a module using a composer repository with a local path: https://getcomposer.org/doc/05-repositories.md#path
Let me know if that works!

I don't think there is a way to do this, I always copy the modules into their own repo and release from there.


Py3 compatibility

https://pythonclock.org/
I got the tests to pass with a single change in nodes/chunk.py and a couple of coercions to integer in the test code.
If there's good reasons (like dependency issues) for keeping things old school, that's fine (and it'd be good to document that here, and in the README and other docs), but if it's not likely to be huge amounts of work then I can give it a crack.
Points for clarification:

[ ] Classic division. I've imported future division in every file which did any division, for consistency - it seems from existing coercions that true division is wanted practically all of the time anyway. The only case where I'm not sure this is true is in Coordinate (division dunder methods) and Roi (get_center).

Thanks a lot for looking into that. The current development branch is release-v0.3, I think it would be best to make this one Python 3 compatible as it will replace master soon.
In this branch, Coordinate is also restricted to hold integer values, which means we'd want floor divisions there.

Coordinate is also restricted to hold integer values

Excellent, that answered another of my questions. I'll take a look.

In terms of expected behaviour: should all divisions of a Coordinate or ROI round towards negative infinity and produce an integer? If they are intended to support world coordinates at some point, true division will be required, but if they're pixel-spaced for now maybe holding them to integers is what's wanted.
Maybe a WorldCoord/WorldROI would be the way forward later.

Yes, Coordinate and ROI should always be integer, and round to floor.
They are already used to represent world units, deliberately forcing integer. The reason is that otherwise the definition of intervals gets tricky: We want to be able to express half-open ranges [begin,end) unambiguously. Having integer coordinates makes that easier, and for all the examples we encountered so far, world units could easily be scaled such that they are integer.  For Points, the location is allowed to be float (we don't use Coordinate for point locations, but a simple ndarray of float).

gunpowder is, since (at least?) v1.0, Python 3 compatible. Thanks for bringing this up!


Atom crashes randomly when interacting with tree view

Atom keep crashing, the crash is random, but it happens to me about about 10-30% of the time I interact with the tree view via right-click menu and choosing things like "copy project path", "new file" among others. I get crashes many times in an hour an this is very annoying.
I know this bug report is not very helpful, because it is not reproducible. But is there a way to get a crash report and find exactly what caused the crash? I looked at Console.app, but it does not have "User Reports" option mentioned in Debugging.
Thanks
Atom 1.44.0 on MacOS 10.15.3.
(Atom was crashing for me for several months in older versions as well)

could be part of #20034

@UziTech thanks, sorry for the duplicate.


Cherry-pick recent CDC changes to release-4.0 branch

Development Task
Ensure all bugfix commits in the release-5.0 branch are cherry-picked to release-4.0 https://github.com/tikv/tikv/commits/release-5.0/components/cdc/src

I have checked the following commits (commits after Jan 22, 2021)：

515df8d
58c9c5e
eca434d
bbc6bff
ffd6812
cfd7840
df3b405

Among them, the 1、2、5、6、7 th commits have been confirmed by the authors that they do not need to be  Cherry-pick to the 4.0.0 branch.
The 2th commit's  author said whether this commit will be Cherry-pick to release 4.0.0 depends on whether it will affect subsequent fixes.
The 3th commit is not important ,  so there is no need to merge to version 4.0.0.
My conclusion is that there are no bug fixes that need to be Cherry-pick to release 4.0.0 after Jan 22, 2021.


chore: update dependencies

@pmdartus The CI failing to checkout successfully. I followed this project in circleci(which usually fixes this sort of issue). May be I do not have the right access to this repo? Can you please add me as a team member to the project?


CAD-2746 tracers:  add the local mux tracer

Local socket mux used to be nullTracer.
This adds a more useful one, that is also off by default.

bors r+

bors r+


[SPARK-8698] partitionBy in Python DataFrame reader/writer interface should not default to empty tuple.

LGTM

Merged build triggered.

Merged build started.

Test build #35967 has started for   PR 7079 at commit 8513e1c.

Test build #35967 has finished for   PR 7079 at commit 8513e1c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.


Where are the results of the Evaluation?

where are the results of the evaluation?
Results writes to /tmp/tmp3ntpwyqw/results/result.json
Where is this document, please?

This is a temporarily generated file during training and will be removed when evaluation is done. If you want to generate this file for future processing, you may need to add a flag like that to your execution command:
--eval-options 'jsonfile_prefix=[path to desired folder]/result.json'

Closed due to inactivity. Please feel free to reopen if you feel it necessary.


Wrong html for a list item with nested list and a paragraph

Marked returns wrong html for this simple markdown:
* section one

    * item one
    * item two

    This is the first section

* section two

    * item one
    * item two

    This is the second section

The expected html for this should be:

section one

item one

item two

This is the first section

section two

item one

item two

This is the second section

But in reality what I get is:

section one

item one

item two

This is the first section

section two

item one

item two

This is the second section

The problem here is that the paragraphs below the nested lists are included inside the 2nd list item of the nested list, instead of being siblings of the nested lists.
I'v checked the result of this markdown in different online editors and they all return the correct html.
Here's the relevant thread in stack overflow.

I am having a similar problem with with nested lists where a list with nested items merges into a single list.
Like:
1.  one
    *   Item
    *   Item
2.  two
    *   Item
    *   Item

Becomes:

one

Item

Item

two

Item

Item

This is happening when running my code through docco to generate documentation for my code.

#982


Builds should fail on Linting warnings

In order to produce cleaned or standardized code I think that on linting errors (Sass lint, Eslint) and warnings Travis or CodeClimate (which ever does the check) should fail.

This is no longer needed, we will use Hound for this.


maybe stop chaning things without a built in method to update the existing, little annoying based on recent marketing changes to move everyting from naming to placement around for no reason.  sounds like busy work without someone thinking.  im on board for new items but new items without a plan for migration ... nope.  move what we have make it work.  at least have some plan other then its busted after this.

maybe stop chaning things without a built in method to update the existing, little annoying based on recent marketing changes to move everyting from naming to placement around for no reason. sounds like busy work without someone thinking. im on board for new items but new items without a plan for migration ... nope. move what we have make it work. at least have some plan other then its busted after this.

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

ID: bd934939-4dbb-3a92-f996-56b9557f49ac
Version Independent ID: 3cda6b81-26e8-c9ac-e768-d912636a461b
Content: Grant controls in Conditional Access policy - Microsoft Entra
Content Source: articles/active-directory/conditional-access/concept-conditional-access-grant.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@SquirrelAssassin
Thanks for your feedback! We will investigate and update as appropriate.

@SquirrelAssassin
Thank you for your time and patience!
Thank you for your feedback!
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an Azure support request. Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
Teams Q&A forum for technical questions about the configuration and administration of Microsoft Teams on Windows.
Microsoft Teams Community forum
Thank you for your time and patience throughout this issue.


Stop responding to Address Queries after consecutive tx failures to child.

Reset consecutive failure count on receiving a 15.4 Data Request message.

As discussed in #672.

Current coverage is 71.95% (diff: 100%)

Merging #757 into master will decrease coverage by 0.34%

@@             master       #757   diff @@
==========================================
  Files           106        105     -1
  Lines         15786      15780     -6
  Methods        2154       2150     -4
  Messages          0          0
  Branches       1874       1874
==========================================
- Hits          11413      11354    -59
- Misses         3758       3809    +51
- Partials        615        617     +2

Powered by Codecov. Last update 883794a...ea02d6c


:bug: Always send to cluster local Ksvc, when using in-cluster-sender

Changes

:bug: Always send to cluster local Ksvc, when using in-cluster-sender

/kind bug
Fixes #145

/hold
Waiting for decision on how to fix #145

Based on slack discussion and  https://github.com/knative/serving/issues/12533 I think it's safe to assume that for now we should align with Eventing, and just use URI returned from address resolver. That's exactly what this PR is doing.
/unhold

/cc @rhuss
/cc @dsimansk
/cc @vyasgun

thanks !
/approve
/lgtm


update readme

Codecov Report

Merging #34 (df8ba7f) into master (ecdf065) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #34   +/-   ##
=========================================
  Coverage     73.86%   73.86%
  Complexity      152      152
=========================================
  Files            24       24
  Lines          1580     1580
  Branches        255      255
=========================================
  Hits           1167     1167
  Misses          266      266
  Partials        147      147

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 ecdf065...df8ba7f. Read the comment docs.


allow all Keystone V3 auth param combinations

Hi,
currently only user-name, domain-id and project-name are supported.
Would be nice to have the full combination set of user-name/-id & domain-name/-id & project-name/-id.
As before, when time allows I will send a PR ;)
Cheers,
Maurice

Hi Maurice,
👍 , Yes that would definitely offer more flexibility!
I'll see if I can do that in the next few days or take yours if not.
Thanks,
Gilles

Thanks!

@Carthaca, you're welcomed!


don't set User-Agent on web

Pull Request
Related issue
Fixes #256
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Thanks for raising this issue. Indeed we had a similar issue in the JS SDK. So to fix it, we introduced a different user agent called https://github.com/meilisearch/specifications/blob/9eb937f1113c2f11bffd87929001aa68497bfc65/text/0034-telemetry-policies.md#x-meilisearch-client-header.
So, I propose a different solution to your PR @ahmednfwela
Add this header X-Meilisearch-Client instead of the User-Agent and set the value to ["Meilisearch Dart Web (vX.X.X)", "Meilisearch Dart (vX.X.X)"] when it is inside of a web environment. It will help me to understand the value of supporting both platforms!

Thanks @ahmednfwela 🤘


Using RLS with CustomData(), over Gateway, to on-prem SSAS is can work

Using RLS with CustomData(), over Gateway, to on-prem SSAS is can work by making the gateway do "AD Account switching".
See workaround here:
https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/17768485-ssas-gateway-data-source-customdata-setting-is-bro

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

ID: 61878b62-89e5-e60a-4995-74d9650ca3e6
Version Independent ID: 378733df-8807-3274-dcf3-3e2aa40a78c0
Content: Use row-level security with Power BI embedded content - Power BI
Content Source: powerbi-docs/developer/embedded-row-level-security.md
Service: powerbi
Sub-service: powerbi-developer
GitHub Login: @rkarlin
Microsoft Alias: rkarlin

Thanks for your comment, @mitchonfire . This issue has been assigned to the doc author for review.

@mitchonfire,
Thank you for your feedback! We will investigate and get back to you with the relevant info.
@rkarlin for awareness.

@KesemSharabi

Hi @MicrosoftDocs, thanks for pointing this out! As this is not a documentation question I'm closing the case.


[Question] Is Apple Silicon Neural Engine (ANE) and Core ML model package format supported?

❓ General Questions
Hi, I can't find it in the documentation, and the issue tickets are unclear.
Is Apple Silicon Neural Engine (ANE) and Core ML model package format supported?

Currently ANE is not supported


Automatic releases

Ideally, the conversion from .md to .tex should be done on the server, and both templates should be released as (versioned) artifacts.

Done.


How to modify a ACL group?

I know that we can crate a acl group like this:curl -X POST http://kong:8001/consumers/{consumer}/acls --data "group=group1";
But how to modify or delete the group?

for deletion you would add ensure: "removed"
I don't think there is any "Modify" action implemented since there is only one property to the whole object (group).

While using kongfig, you would  would add ensure: "removed" for deletion.
Something like :
`
  username: "test"
  ensure: "present"
  credentials:
    - name: "key-auth"
      ensure: "present"
      attributes:
        key: "1234"
  acls:
    -
      ensure: "removed"
      group: "test"

`
I don't think there is any "Modify" action implemented since there is only one property to the whole object (group).
I might be wrong tho !

Have you tried using PATCH or PUT?


Make content_for raise an exception in case of silently overwriting content

This addresses #704

Could you add tests for this, and remove the commented-out code?

OK, done

Thanks!


Confusing error message when altering the type of "data"

When using writing a fuzz target, one can change the signature of data from &[u8] to something else, which does not work, but prints a confusing error message.
Example:
fuzz_target!(|data: &[usize]| {
    // stuff
}

In all cases, the error message printed is
error[E0463]: can't find crate for `arbitrary`
 --> fuzz/fuzz_targets/fuzz_target_1.rs:5:1
  |
5 | / fuzz_target!(|data: &[u16]| {
6 | |     // stuff
7 | | });
  | |___^ can't find crate
  |
  = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)

This seems rather confusing, as it isn't clear that the change to the type is the reason for the missing crate.
Note that I am on cargo 0.24.0-nightly (abd137ad1 2017-11-12) and using cargo-fuzz 0.5.0 on Mac OS X.

Sorry this error is confusing, but it says exactly what the problem is. It is necessary to specify the dependency on arbitrary crate in your Cargo.toml to use arguments other than &[u8]. An example fuzz target using the arbitrary support is available here. The list of types supported by arbitrary can be seen in the "Implementors" list here.
That being said, be aware that using arbitrary types can make program flow more opaque to the fuzzer and thus fuzzing take longer than if you converted the data yourself in a more naive way.

Note that by default arbitrary crate is not an included dependency specifically because most fuzz targets do not need this support and they just convert the data naively.

Ah, I see, thank you for pointing me in the right direction!


Update .*rc file for all shells

Solves issue #2508
Solved the issue with not updating the .*rc file when not installed with BASH. I have tested this with ZSH on Ubuntu.
Note: this fix still requires user to close current terminal & reopen another one.

I understand what you mean. It worked for me so I thought about sharing. 😅 Works on my machine kind of scenario. Sorry for wasting your time.


In-source zinc's LM integration code

This requires a new version of Zinc in order to build (tested using local source dependencies).

A validation involving this pull request is in progress...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4617/head
sbt/sbt@9674e4a6e9c45eab96331a9af21715255d26179c

zinc
pull/658/head
sbt/zinc@0b6470f2b8558e5c8b77e2942f02aca19e3bbad8

io
develop
sbt/io@ca966bcd6c73400b11c7a78e8604ea211f32e3d8

librarymanagement
develop
sbt/librarymanagement@f073dde812848ef443619578f55e290f3863bcaa

util
develop
sbt/util@473d42ac782f9449dbd7c7940a67208abbff1861

:x: The result is: FAILED
(restart)

A validation involving this pull request is in progress...

Could we keep git history somehow?

Sure, I'll do the same thing I did in https://github.com/sbt/sbt/pull/3302.
I'll probably get round to it in a few days.

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4617/head
sbt/sbt@7466ee4913d5281b99130c217c7bac02347adb76

zinc
pull/658/head
sbt/zinc@0b6470f2b8558e5c8b77e2942f02aca19e3bbad8

io
develop
sbt/io@ca966bcd6c73400b11c7a78e8604ea211f32e3d8

librarymanagement
develop
sbt/librarymanagement@f073dde812848ef443619578f55e290f3863bcaa

util
develop
sbt/util@473d42ac782f9449dbd7c7940a67208abbff1861

:x: The result is: FAILED
(restart)

A validation involving this pull request is in progress...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4617/head
sbt/sbt@7466ee4913d5281b99130c217c7bac02347adb76

zinc
pull/658/head
sbt/zinc@0b6470f2b8558e5c8b77e2942f02aca19e3bbad8

io
develop
sbt/io@ca966bcd6c73400b11c7a78e8604ea211f32e3d8

librarymanagement
develop
sbt/librarymanagement@f073dde812848ef443619578f55e290f3863bcaa

util
develop
sbt/util@473d42ac782f9449dbd7c7940a67208abbff1861

:x: The result is: FAILED
(restart)

[sbt212] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[sbt212] [warn] 	::          UNRESOLVED DEPENDENCIES         ::
[sbt212] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[sbt212] [warn] 	:: org.scala-sbt#compiler-bridge_2.13.0-M5;1.3.0-bin-20190418T141950: not found
[sbt212] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[sbt212] [info] ZincComponentCompilerSpec:
[sbt212] [info] - should compile the bridge for Scala 2.10.5 and 2.10.6 *** FAILED ***
[sbt212] [info]   sbt.internal.inc.InvalidComponent: The compiler bridge sources org.scala-sbt:compiler-bridge_2.10:1.3.0-bin-20190418T141950:compile could not be retrieved.

head scratch

Is the bridge published?

I guess not?  The head scratching comes from why it wants the 2.13 bridge in the 2.10 test case.  I'll iterate locally and fix the tests (I only iterated on tests compiling).

A validation involving this pull request is in progress...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4617/head
sbt/sbt@044ced544fa2422fa4761efccff17f9b207db756

zinc
develop
sbt/zinc@a5c269c729100140981e1c9ea49568a256fa92f2

io
develop
sbt/io@dda58a019335c1d8480a516bdd1e97ede0b7bdcb

librarymanagement
develop
sbt/librarymanagement@f073dde812848ef443619578f55e290f3863bcaa

util
develop
sbt/util@3568b13a2e257f33957dd32c51c56ce9c378c9f9

:x: The result is: FAILED
(restart)

[sbt212] [error] /home/jenkinssbt/workspace/sbt-validator/target-0.9.16/project-builds/sbt212-7282eaf24b43dd9e598d0d45a868acfe5552410f/internal/util-complete/src/main/scala/sbt/internal/util/LineReader.scala:90:26: not found: value ScrollUp
[sbt212] [error]     if (showProgress) s"$ScrollUp$DeleteLine" + prompt
[sbt212] [error]                          ^
[sbt212] [error] /home/jenkinssbt/workspace/sbt-validator/target-0.9.16/project-builds/sbt212-7282eaf24b43dd9e598d0d45a868acfe5552410f/internal/util-complete/src/main/scala/sbt/internal/util/LineReader.scala:90:26: not found: value ScrollUp
[sbt212] [error]     if (showProgress) s"$ScrollUp$DeleteLine" + prompt
[sbt212] [error]                          ^
[sbt212] [info] No documentation generated with unsuccessful compiler run
[sbt212] [error] one error found
[sbt212] [error] one error found
[sbt212] [error] (completeProj / Compile / compileIncremental) Compilation failed
[sbt212] [error] (completeProj / Compile / doc) Scaladoc generation failed

weird

A validation involving this pull request is in progress...

Rebased and re-ran sbt-validator.

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4617/head
sbt/sbt@15e9356e27958f669c04e8140031652c1e5d8738

zinc
develop
sbt/zinc@a5c269c729100140981e1c9ea49568a256fa92f2

io
develop
sbt/io@dda58a019335c1d8480a516bdd1e97ede0b7bdcb

librarymanagement
develop
sbt/librarymanagement@f073dde812848ef443619578f55e290f3863bcaa

util
develop
sbt/util@3568b13a2e257f33957dd32c51c56ce9c378c9f9

:x: The result is: FAILED
(restart)

🙄
[sbt213-io] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[sbt213-io] [warn] 	::          UNRESOLVED DEPENDENCIES         ::
[sbt213-io] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[sbt213-io] [warn] 	:: org.scalatest#scalatest_2.13.0-M5;3.0.8-RC2: not found
[sbt213-io] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::

The rest of it was successful:
[info] Project sbt210-io-------------------: SUCCESS (project rebuilt ok)
[info] Project sbt210-util-----------------: SUCCESS (project rebuilt ok)
[info] Project sbt210-zinc-----------------: SUCCESS (project rebuilt ok)
[info] Project sbt211-io-------------------: SUCCESS (project rebuilt ok)
[info] Project sbt211-librarymanagement----: SUCCESS (project rebuilt ok)
[info] Project sbt211-util-----------------: SUCCESS (project rebuilt ok)
[info] Project sbt211-zinc-----------------: SUCCESS (project rebuilt ok)
[info] Project sbt212----------------------: SUCCESS (project rebuilt ok)
[info] Project sbt212-io-------------------: SUCCESS (project rebuilt ok)
[info] Project sbt212-librarymanagement----: SUCCESS (project rebuilt ok)
[info] Project sbt212-util-----------------: SUCCESS (project rebuilt ok)
[info] Project sbt212-util-interface-------: SUCCESS (project rebuilt ok)
[info] Project sbt212-zinc-----------------: SUCCESS (project rebuilt ok)
[info] Project sbt213-io-------------------: FAILED (RuntimeException: )
[info] Project sbt213-zinc-----------------: SUCCESS (project rebuilt ok)
[info] Project scala-210-------------------: SUCCESS (unchanged, not rebuilt)
[info] Project scala-211-------------------: SUCCESS (unchanged, not rebuilt)
[info] Project scala-212-------------------: SUCCESS (unchanged, not rebuilt)
[info] Project scala-213-------------------: SUCCESS (unchanged, not rebuilt)
[info] >>> The dbuild result is----------------: FAILED (failed: sbt213-io)

Ok, I'll recover the commit history now.

[info] Project sbt213-io-------------------: FAILED (RuntimeException: )

This is likely due to sbt-validator using Scala 2.13.0-M5 instead of RC1.

https://github.com/sbt/sbt-validator/commit/7071546c9344a5ff29ea34520a51998e04f89635

A validation involving this pull request is in progress...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4617/head
sbt/sbt@15e9356e27958f669c04e8140031652c1e5d8738

zinc
develop
sbt/zinc@a5c269c729100140981e1c9ea49568a256fa92f2

io
develop
sbt/io@dda58a019335c1d8480a516bdd1e97ede0b7bdcb

librarymanagement
develop
sbt/librarymanagement@f073dde812848ef443619578f55e290f3863bcaa

util
develop
sbt/util@3568b13a2e257f33957dd32c51c56ce9c378c9f9

:white_check_mark: The result is: SUCCESS
(restart)

Ready for review, @eed3si9n

Zinc 1.3.0-M4 is out. See https://github.com/dwijnand/sbt/pull/2

Thank you, Eugene, for helping me land this.


fix: allow ManualTrustRoot to have multiple rekor keys

ManualTrustRoot implements the TrustRoot trait, which requires the implemented to have multiple rekor keys. The ManualTrustRoot struct has now been updated to handle that, prior to that only one Rekor key was stored inside of a ManualTrustRoot instance.

@Xynnn007 this is ready for another round of review


Overhaul Makefile

The Makefile should probably be made a little better as it's very basic at the moment.
The project does not compile on display03 and seems to give lots of errors, I suspect this to be caused by the Makefile being too simplistic and not accounting for the header files or something similar to this.

Simplified Makefile dramatically, hopefully it's ok in its current form.
Will reopen this issue if it turns out to be too simplistic and isn't recompiling for file changes...


API tests added

Hi @ignasbol. Could you raise an issue to cover the need to add tests so we can link the pull request to the issue, and also describe in the pull requests the approach that you've taken so that its possible to evaluate whether that's the right design/architecture/implementation?

LGTM. With 1.0.7 going out, we can merge this now.

Thanks @ignasbol for resolving the conflicts.


Add debug info and fix spelling

This change is

Coverage increased (+0.01%) to 45.925% when pulling 62fcc400b8907a1799054fbb90588f0e24286eb0 on tonglil:static-ip-debug into 4c0a616f5c7e9870ed2aa74dfa9284bc5e0e0539 on kubernetes:master.


Regression in 2020.11.15 failing to install editable package in deploy + user mode with non root user

Hello,
Issue description
I have an annoying issue with pipenv version 2020.11.15 (not present in 2020.11.4).
The setup is the following: I have an app with dependencies declared in setup.py that is installed in an "editable" fashion (kind of what is described in https://github.com/pypa/pipenv/issues/4542 but simultaneously with PIP_USER=1 and --deploy and a non-root user).
The install fails with weird pip errors.
Among of which:
    raise InstallationError(exc_msg)
pip._internal.exceptions.InstallationError: Command errored out with exit status 1: /usr/local/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/some_user/app/setup.py'"'"'; __file__='"'"'/home/some_user/app/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps --user --prefix= Check the logs for full command output.

(but the command in question works fine when run outside of pipven and when investigating the logs of pip, it was talking about trying to uninstall files from /usr/local/lib/python3.8/site-packages/ which it cannot do as it is not a root user...).
Unfortunately, I couldn't understand what is going on with the comparison of the verbose output between the last two pipenv versions.
Expected result
The installation works just like with pipenv 2020.11.4.
Actual result
The installation fails.
Here are pipenv & pip logs:
pipenv_logs_pipenv_2020.11.15.txt
pip_logs_pipenv_2020.11.15.txt
Vs
pip_logs_pipenv_2020.11.4.txt
Steps to replicate
Here is a simple full-docker setup to replicate (hard to do otherwise):
example_docker_setup.zip
Unzip and run:
docker build --rm --no-cache .

You can edit the dockerfile to compare different pipenv versions.
Thanks for your help.

$ pipenv --support (from inside the docker image)
Pipenv version: '2020.11.15'
Pipenv location: '/usr/local/lib/python3.8/site-packages/pipenv'
Python location: '/usr/local/bin/python'
Python installations found:

3.8.6: /usr/local/bin/python3.8
3.8.6: /usr/local/bin/python3

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.8.6',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '5.4.0-59-generic',
 'platform_system': 'Linux',
 'platform_version': '#65-Ubuntu SMP Thu Dec 10 12:01:51 UTC 2020',
 'python_full_version': '3.8.6',
 'python_version': '3.8',
 'sys_platform': 'linux'}

System environment variables:

PIP_LOG
USER
HOSTNAME
PYTHON_PIP_VERSION
HOME
GPG_KEY
USER_UID
PIP_USER
PYTHON_GET_PIP_URL
PATH
PIP_NO_CACHE_DIR
LANG
PIPENV_SYSTEM
PYTHON_VERSION
WORKDIR_PATH
PWD
PYTHON_GET_PIP_SHA256
USER_GID
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:

PIPENV_SYSTEM: 1

Debug–specific environment variables:

PATH: /home/some_user/.local/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG: C.UTF-8
PWD: /home/some_user/app

Contents of Pipfile ('/home/some_user/app/Pipfile'):
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]

[packages]
bug = {path = ".", editable = true}

[requires]
python_version = "3.8"

Contents of Pipfile.lock ('/home/some_user/app/Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "85cfd057bb59713d5b0a79c7a5a98eb1824b14b03ad805c1ba6dcf5bcfbfced7"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.8"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "bug": {
            "editable": true,
            "path": "."
        }
    },
    "develop": {}
}

Very much related to https://github.com/pypa/pipenv/issues/4551 ?

I am inclined to think it could be related to #4551 but then I also tried your example Pipfile and setup.py using pipenv==2021.11.23 and got a different result, it wasn't a flat out failure.  Could you recheck on latest pipenv @FloChehab ?
mdavis@matt-VirtualBox:~/shared-projects/pipenv-4583$ pipenv install --deploy --verbose

Using python: 3.8

Path to python: /home/mdavis/.pyenv/versions/3.8.12/bin/python3.8

Creating a virtualenv for this project...

Pipfile: /home/mdavis/shared-projects/pipenv-4583/Pipfile

Using /home/mdavis/.pyenv/versions/3.8.12/bin/python3.8 (3.8.12) to create virtualenv...

⠸ Creating virtual environment...created virtual environment CPython3.8.12.final.0-64 in 160ms

  creator CPython3Posix(dest=/home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN, clear=False, no_vcs_ignore=False, global=False)

  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/mdavis/.local/share/virtualenv)

    added seed packages: pip==21.3.1, setuptools==58.3.0, wheel==0.37.0

  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!

Virtualenv location: /home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN

Installing dependencies from Pipfile.lock (bfced7)...

Writing supplied requirement line to temporary file: '-e .'

Installing 'bug'

$ /home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/bin/python -m pip install --verbose --upgrade --no-deps --exists-action=i -r /tmp/pipenv-yllclo44-requirements/pipenv-xog4kc7d-requirement.txt -i https://pypi.org/simple

Using source directory: '/home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/src'

Using pip 21.3.1 from /home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/lib/python3.8/site-packages/pip (python 3.8)

Obtaining file:///home/mdavis/shared-projects/pipenv-4583 (from -r /tmp/pipenv-yllclo44-requirements/pipenv-xog4kc7d-requirement.txt (line 1))

  Installing build dependencies: started

  Installing build dependencies: finished with status 'done'

  Checking if build backend supports build_editable: started

  Checking if build backend supports build_editable: finished with status 'done'

An error occurred while installing -e .! Will try again.

  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 1/1 — 00:00:03

Installing initially failed dependencies...

Writing supplied requirement line to temporary file: '-e .'

Installing 'bug'

$ /home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/bin/python -m pip install --verbose --upgrade --no-use-pep517 --no-deps --exists-action=i -r /tmp/pipenv-yllclo44-requirements/pipenv-ctz2pe2k-requirement.txt -i https://pypi.org/simple

Using source directory: '/home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/src'

Using pip 21.3.1 from /home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/lib/python3.8/site-packages/pip (python 3.8)

Obtaining file:///home/mdavis/shared-projects/pipenv-4583 (from -r /tmp/pipenv-yllclo44-requirements/pipenv-ctz2pe2k-requirement.txt (line 1))

Writing supplied requirement line to temporary file: '-e .'

Installing 'bug'

$ /home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/bin/python -m pip install --verbose --upgrade --no-use-pep517 --no-deps --exists-action=i -r /tmp/pipenv-yllclo44-requirements/pipenv-ypfelxjw-requirement.txt -i https://pypi.org/simple

Using source directory: '/home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/src'

Using pip 21.3.1 from /home/mdavis/.virtualenvs/pipenv-4583-7bhEV5yN/lib/python3.8/site-packages/pip (python 3.8)

Obtaining file:///home/mdavis/shared-projects/pipenv-4583 (from -r /tmp/pipenv-yllclo44-requirements/pipenv-ypfelxjw-requirement.txt (line 1))

  ☤  ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 2/2 — 00:00:01

Closing this one as a duplicate of #4551 -- suggesting everyone get to latest pipenv and pip and re-check their projects.


adds Azerty keyboard layout

Added Azerty keyboard layout. Please let me know if any changes need to be made. I'd be happy to add additional keyboard layouts as well. Thanks!

LGTM, why ain't it merged yet?

Hi @hiamandeep,
Could you merge this pull request so french users can enjoy the website too?
Thanks!


BERT-Tiny with TTNN

Implement BERT Tiny using instructions from https://tenstorrent-metal.github.io/tt-metal/latest/ttnn/about.html

The sub-modules attention, intermediate, and output are implemented using ttnn.
Corresponding commit
Note: When the ttnn tensor in the TILE layout is converted to a torch tensor, the pcc is reduced. Therefore the layout of the ttnn tensor is changed to ROWMAJOR before converting it into torch.

The Bert-tiny model is completed using ttnn ops.
Corresponding commit

The CI tests for PR https://github.com/tenstorrent-metal/tt-metal/pull/4507 and https://github.com/tenstorrent-metal/tt-metal/pull/4508 were successful. Hence it is merged with the main.