feat(validator): Add Health Checks and Autoheal to Docker Compose

Added Health Checks and Autoheal for verifiable services like kepler, scaphandre, prometheus, and grafana.
Note for Scaphandre and Kepler Model Server, curl and wget were not installed in the image. For scaphandre, curl was manually installed. If necessary, I can also manually install curl for the Model Server.
Model Server and Estimator were not included in this implementation as I cannot curl their ports.

@KaiyiLiu1234 Shouldn't this fail while running docker compose up
services:
  kepler-metal:
    build:
      context: ../../../../
      dockerfile: build/Dockerfile
      args:
        INSTALL_DCGM: false
        INSTALL_HABANA: false

    ports:
      # NOTE: use 9888 to keep the host 8888 port free for any local testing
      # e.g. sudo ./bin/kepler
      - 9188:8881
    privileged: true
    pid: host

    entrypoint: [/usr/bin/bash, -c]

    command:
      - |
        set -x;
        /usr/bin/kepler \
          -address "<IP_ADDRESS>:8881" \
          -v "8" \
          -enable-gpu=false
    networks:
      - kepler-network

    healthcheck:
      test: curl -f http://localhost:8888/metrics || exit 1
      interval: ${HEALTHCHECK_INTERVAL:-50s}
      timeout: ${HEALTHCHECK_TIMEOUT:-30s}
      retries: ${HEALTHCHECK_RETRIES:-3}
      start_period: ${HEALTHCHECK_START_PERIOD:-1m}

as the test referring to the wrong port?

@vprashar2929 It does fail.

Health check will label services as unhealthy if the test fails. autoheal will attempt to restart. I think autoheal might be able to terminate a service when unhealthy.


Abacus Activity: Result Overlaps with Undo Full Screen Icon in Full-Screen View

Hey @llaske
Description
In the Abacus activity in Sugarizer, when in full-screen view, If the Rods are Less then 15 .the result of the abacus calculation gets overlapped by the undo full screen icon. This can make it difficult to read the result and can be confusing for users.
Steps to Reproduce
Open the Abacus activity in Sugarizer.

Choose Rods Less then 15  e.g 14
Enter a calculation in the abacus.
Click on the full screen icon to enter full-screen view.
Observe that the result of the calculation is overlapped by the undo full screen icon.

Expected Behavior
The result of the abacus calculation should be visible and not overlap with any UI elements, including the undo full screen icon.
Actual Behavior
The result of the abacus calculation is overlapped by the undo full screen icon when in full-screen view.
Screenshots

Possible Solution
One possible solution could be to adjust the positioning of the undo full screen icon or the result area to ensure that they do not overlap. Another solution could be to adjust the size of the UI elements to allow more space for the result area.
I would like to ask for your feedback on whether this request is valid and if it's feasible improve the result area in the Abacus activity. If it is, I would be interested in working on this issue

No it's a rare case and the work around is to unfull screen

Okay @llaske ,thanks for the response.

Thanks for the Response @llaske  ,


Add --ignore-certificate-errors to browser startup arguments ot prevent ssl warnings.

After discussion we're just going to add the intermediate SSL Cert for this site to the Umbra machines.


[Bug]: failed to call a procedure/function that contains out sys_refcursor

ODC version
4.2.2
OB version
not releated
What happened?
there is a procedure:
create or replace procedure abcd_test1(
var_result_info out varchar2,
value_list out sys_refcursor) IS
BEGIN
    var_result_info := 'asdasdasd';
    open value_list for
select
  1 as usercode,
  2 as username
from
  dual;
end;

I try to call it by odc:

I can execute the calling anonymous block in sql console:

What did you expect to happen?
call the procedure/function contains out ref_cursor successfully.
How can we reproduce it (as minimally and precisely as possible)?
follow 'what happened'
Anything else we need to know?
No response
Cloud
No response

as you can see:
// JdbcDataTypeUtil#getValueFromStatement
public static Object getValueFromStatement(CallableStatement statement, int index, String type)
            throws SQLException {
        JDBCType jdbcType = parseDataType(type);
        if (null == statement.getString(index)) {
            return null;
        }
...
}

we will call statement.getString before we get value from statement actually. If the value can not be encoded to string such as sys_refcursor, this calling will throw an exceotion.

pass


Change getLogger name to be optional

Issue: https://github.com/allegro/logextractx/issues/6
Now name getLogger is optional
Required test is present

thx


Trigger using  platform: template is not working (Home Assistant 0.105.3)

Hello I am running Home Assistant 0.105.3 HassOS 3.10 in a Raspberry Pi4 4Gb ram
I am trying to create an automation using a template to trigger it.
The Problem is that the automation never is triggered.
Environment

Estado del sistema

arch	armv7l

dev	false

docker	true

hassio	true

os_name	Linux

python_version	3.7.6

timezone	America/Argentina/Buenos_Aires

version	0.105.3

virtualenv	false

Lovelace

mode	storage

resources	2

views	13

Home Assistant release with the issue: 0.105.3

Operating environment Hass.io

Integration causing this issue: platform: template

My automation code:
- id: Riego000
  alias: Riego Reticulation Run Program 1
  initial_state: 'on'
  trigger:
  - platform: template
    value_template: '{{ states.sensor.time.state == (states.input_datetime.retic_program1_start_time.attributes.timestamp | int | timestamp_custom("%H:%M", False)) }}'
  condition:
    condition: and
    conditions:
    - condition: state
      entity_id: input_boolean.retic_program1_enable
      state: 'on'
    - condition: state
      entity_id: sensor.riego1_watering_day
      state: 'true'
  action:
  - entity_id: switch.riego_mitre
    service: switch.turn_on

I have already included in the confg the "time sensor"

Closing this issue as this is not directly a bug in any HA code. Please use the dicscord server or the community forum for these kind of questions.


Question about features

Dear Prof Liu，
Here are the features generated for training using the first step script. I noticed that one feature, Offset_frag,was not mentioned in the original article. It may not have been used. So I have some questions: what does Offset_frag refer to, how does it differ from Dist_frag_end, and does it facilitate model training? Thanks for your reply.
Original artical: At each CpG in each fragment in the bam file (CpG point), we can obtain three features: the fragment’slength,theCpG’s distance to the center of that fragment, and the fragment coverage at that particular CpG position in the reference genome.
chr     start   end     readName        FragLen Frag_strand     methy_stat      Norm_Frag_cov   baseQ   Offset_frag     Dist_frag_end   methyPrior
chr22   10527860        10527862        SNL144:297:HYWH3BCXY:1:1111:15154:68116 154     -       m       1.122016        35      1       1       NaN
chr22   10527872        10527874        SNL144:297:HYWH3BCXY:1:1111:15154:68116 154     -       m       1.122016        40      13      13      NaN
chr22   10527878        10527880        SNL144:297:HYWH3BCXY:1:1111:15154:68116 154     -       m       1.122016        40      19      19      NaN
chr22   10527939        10527941        SNL144:297:HYWH3BCXY:1:1111:15154:68116 154     -       m       1.122016        39      80      74      NaN
chr22   10538977        10538979        SNL144:297:HYWH3BCXY:1:2115:3237:76894  166     -       m       1.122016        39      5       5       NaN
c

Hi, could I ask you what file did you use for the CpG coordinates, or where can it be found?
Thank you in advance!!


[FRAM-2] added field for tel and mailto

https://github.com/user-attachments/assets/10f51d3d-6274-4fd8-9518-f7ca5ce2b0ba

The old version of framework had a button that would take you to the referenced record... for example if you have a assigned to: friend that references a user record, there is a button that takes you to that record:

We need to add that back... i will add a story for that...
Email and telephone number fields should have a similar button, with unique icons, that provide the mailto: or tel: functionality.
Lets remove the functionality from the table, and just have it on the field on the record view, with an explicit button.

I added back the view related record button in main... please make similar buttons for call and email... may want to make the whole tool tip + button + icon its own reusable component and use it for tel, mail and the go to related record button I just created.

I removed the functionality of taking to record upon clicking on the row of table.
Do we have to provide any other way of viewing the record from table directly? If yes, what it will be?

I'm not sure I understand the question... when you click on a row, it should take you to the record... all the fields are displayed there... and we need a call/email button next to the relevant fields...

the button should be added to email.js inside the edit function... a button after the field... see reference.jsx as an example... make sure to get the latest main.

My original question is about -
When we click on row of table, it takes us to record.
After adding email and phone call icon, if I click on the link/button the default behaviour of row will also happen.
https://github.com/user-attachments/assets/bc34fb19-12e0-4494-acb2-4b7ae3626fbd
For example in above video when I clicked on call button it performed action of tel but also took me to record page

The button should only exist on the edit page and should not exist in the table at all.

okay. Got it.

Changes are ready
https://github.com/user-attachments/assets/56034c44-cdd8-42a8-92e3-de7c9b4bb635


Window doesn't always come down completely

When I click on the icon in the address bar the window that appears with all the info doesn't always come down completely making it difficult to see the results. I have attached a screen shot of what happens. I would say this is about 80% of the time I use the plugin.
Great plugin btw thanks for making it.

Which version of Chrome are you on?

Mac 43.0.2357.124 (64-bit)
On Sat, Jun 20, 2015 at 7:36 AM, Dominykas Blyžė<EMAIL_ADDRESS>wrote:

Which version of Chrome are you on?
—
Reply to this email directly or view it on GitHub
https://github.com/h5o/h5o-chrome/issues/9#issuecomment-113748685.

--
Roger Williams
602-380-2692

Seems like it's an issue in Chrome itself: http://code.google.com/p/chromium/issues/detail?id=457887
There are more issues, that seem to be related in their tracker.
Let's wait until v44 and see if they fix it - if not - there seem to be suggested workarounds so I'll take a look.

Awesome sauce!
On Saturday, June 20, 2015, Dominykas Blyžė<EMAIL_ADDRESS>wrote:

Seems like it's an issue in Chrome itself:
http://code.google.com/p/chromium/issues/detail?id=457887
There are more issues, that seem to be related in their tracker.
Let's wait until v44 and see if they fix it - if not - there seem to be
suggested workarounds so I'll take a look.
—
Reply to this email directly or view it on GitHub
https://github.com/h5o/h5o-chrome/issues/9#issuecomment-113812320.

--
Roger Williams
602-380-2692

I'm on a Mac and using Chrome 45.0.2454.85 (64-bit), and experiencing the same issue.
Interestingly, though, the window fully comes down after several repetitive clicks on the icon.

I'm on Mac 50.0.2661.102 (64-bit) and it still does this occasionally.

I am on Chrome Version 61.0.3163.100 (Official Build) (64-bit) and this is still happening. I am unable to use the plugin because of this.

This is happening to me as well now in Chrome Version 65.0.3325.181 (Official Build) (64-bit).
It seem to open properly like 5-10% of the time, the rest of them have this truncated box. The times it does work I've noticed it slides in smoothly, but when it doesn't work it looks like it tries to slide in and then jumps to the small height. Could be an issue with the final animated height being calculated before the outline is generated so it's animating to a default too-small size


UPDATE: Replace one preset color from color picker

Hi there,
Tiny change here. I wanted to add IronCalc's orange (F2994A) to the color presets. The main motivation is to use it in the examples we will be creating for our Docs soon. Besides,

we were lacking an orange, and had too many shades of red,
and the textfield can't be directly edited at the moment (I think we should fix this soon) so adding the preset seems the quickest way of doing this

Thanks!
D

he main motivation is to use it in the examples we will be creating for our Docs soon

Remember that the docs need to be created in Excel


Update App.tsx

Add scale options: 0.5x, 1.5x and 2.5x
I use sometimes 1.5 and 0.5.
1.5 for email marketing
I think this make sense and will be more productive for some users

@toledox82 thank you for your pull request. I updated the plugin


Using scope in queries.

Hi all!
When I use elastic-scout-driver - I can add model scopes to the result, like this:
$elements = Book::search('food')->query(function ($query) {
    return $query->BySubscription()->ByData();
})->paginate(
    24
);

But what If I need using elastic-scout-driver-plus  with boolSearch ?
Is exist some method for do it?

Hey @peektoseen, query is currently not supported by elastic-scout-driver-plus.

@babenkoivan Hello, may I ask if this feature is expected in the nearest future ? I really need it for my project
I have users with subscriptions, and I need to filter users with no active subscription out of elasticsearch query. I have a scope with eloquent relation, but I cannot use it together with searchQuery.
Thank you in advance!

Hey @Stalex89 and @peektoseen, you can use the refineModels method as described here.


feat: Add StringLiteral.

Description
Add StringLiteral class to allow using strings as non-type template parameters (NTTP).
Type of change

New feature (non-breaking change which adds functionality)

Checklist before requesting a review

[x ] I have performed a self-review of my code.
[x ] If it is a core feature, I have added thorough tests.
[ ] If this is a new component I have added examples.
[ ] I updated the README and related documentation.

@lhruby if you rebase now it should fix CI


Seeding improvements

Fixes #80 : use separate PyTorch generators for each image, generate random seeds explicitly, and store them into the JSON data. Also avoid using the same input seed for multiple images.
I also included a minor memory optimization (calling the gc after switching pipelines).

@wbruna Thanks for this PR


FilePathCommandTest

Coverage increased (+0.2%) to 84.576% when pulling 9e3a91572953d2dd3e487712ee969e5043fdc7ef on DaoHanLim:master into 1869e2e7522e7d40a1ebf1939c44a610eef76568 on CS2103JUN2017-T4:master.


[BUG] Rotating the screen while a photo is displayed goes back to main gallery

In the application, if you select a picture to see it fullscreen, then rotate your phone 90°, the application goes back immediately to the main page, instead of keeping the current page opened.
This is very painful to use
Expected behavior
The application should just keep drawing the current picture fullscreen and not change page.
Smartphone (please complete the following information):

Device: POCO M4 5G
OS: Android 14
Version v2.1.2 (from F-Droid)

Nope, it's on F-Droid current version (2.1.2). Will try on 3.0.0 and report if it still exists.


Missing description string for Ocular HUD

The description string for Ocular HUD reads EQUIPMENT_CRITONUSE_DESC_RISKYMOD. Made sure this wasn't a result of anything my in-progress modpack (which changes a lot of stuff) was doing.

Will upload a fix shortly.


Responsive Modals

it works
https://www.dropbox.com/s/pbitniksr0pzhya/Screenshot 2016-04-05 01.40.47.png?dl=0

Actually, it turns out react-bootstrap has a modal component already! So we can just use that :)


HSEARCH-2818 Optimise encoding of GSON elements into HTTP client buffers

Similar optimisations as proposed before but using a different approach, now more carefully taking into account the AWS digest requests.
Also taking into account flow control of the underlying buffers, this was a bug in the previous proposal.
https://hibernate.atlassian.net/browse/HSEARCH-2818

I've updated it, fixed the typos and applied several more optimisations.
The previous version would avoid all allocations "out of TLAB" - which are the most expensive.
After the second round, we don't see any allocations within TLAB either - the only remaining significant allocations are performed during response parsing.

I've rebased it and fixed the problems with missing static final and what you highlighted about close() not guaranteeing to make it repeatable.
Also promoted that disgest interface to SPI as suggested.
I didn't change the essential strategy around buffers as I'm not seeing a clearly better idea. Happy to be proven wrong but let's split that out as a different PR if you think it's worth trying.

Merged, thanks! Good to see this one in :)
I'll try to submit a follow-up PR to show what I was talking about.


I'm getting repeated responses from my azure chat bot in Slack.

I'm getting repeated responses from slack channel.

It works perfectly fine from azure web chat as well as from MS Teams. (as well as from the local bot emulator)

Hi @joynext!
I'm unable to repro this. Can  you explain more about your bot?  Is it a standard echo bot? Did you create it locally and then deploy it, or did you create it straight on Azure? What language SDK is it in?

@joynext Are you still experiencing this issue?

Thank you, it looks like the error is now gone.


Upgrade to react-dom; eliminated deprecated calls into react

In 0.14.0, React deprecated render, renderToString, and renderToStaticMarkup in the react package and moved them to react-dom and react-dom/server.
This tiny PR upgrades all the calls I could find to the old functions, making the code forward-compatible, and it eliminates console deprecation warnings I was seeing both on server and client. Cheers!

Yep. We've been meaning to do this for awhile.


Assistant capability and reverse-engineering thereof

I have had this idea for some time, but have very little information to do away with.
Thankfully, Pixel Buds Pro work well with GrapheneOS on Android, so I had been wondering: you know how these support AI assist via Google Assistant application? Now that there's many Mac Studio's and Ryzen DDR5-based inference environments in the market, on-premise cloud deployments have become more commonplace. Also: there has been improvements on-edge, namely whisper.cpp and llama.cpp builds via Android NDK are able to leverage local accelerators.
Is there a chance that the proprietary AI assist capability from Google isn't entirely proprietary?
I wonder if AI assist is ultimately implemented using some signalling protocol over Bluetooth that basically defers to recording and subsequent playback of arbitrary audio. Obviously, there's playback interrupt features but it's probably handled by the firmware itself. If this is the case, then we could potentially modify Pixel Buds application itself to use alternative inference providers.
Based on what you know about Bluetooth & Pixel Buds specifically, how hard could it be, and where would we want to start to learn specifically what's happening under the hood? If it should involve reverse-engineering the relevant apk's, would it also be tractable? If yes, what are the chances it would yield readable, meaningful results? I reckon they probably use NDK themselves, tapping into Android's bluetooth internals, and from the symbols & sniffing alone would it be possible to infer complete logic?
P.S. Great work, your code is quite tidy & indeed, would be worthwhile to investigate how what you do relates to what they do.

Hi, sorry for the late reply. Somehow I forgot about this...
First off, I agree with you that the playback interruption is likely firmware based, I think you could probably try if that still works when it's not connected to an android device.
Regarding the AI assistant feature, I'm pretty sure it just forwards the microphone to the device somehow. There are some additional protocols beyond the maestro one (for controlling settings etc.), and I think that one of those is responsible for that. But I haven't looked into them at all yet, so I can't say which one or how exactly it works.
So for implementing something like that, I think we'd first need to figure out how the pixel app/android integration does that. Again, it's probably some kind of RFCOMM bluetooth protocol, so if we can figure that out, then I'm pretty sure we can make that work. IIRC I tried to figure out how the long-press-button event is being sent, but it's not via the maestro protocol.
The way I went for the maestro/settings stuff is by reverse engineering the pixelbuds apk, so something like that could work again. Unless it's somehow a deeper integration into android itself via some device-independent protocol.

I reckon they probably use NDK themselves, tapping into Android's bluetooth internals, and from the symbols & sniffing alone would it be possible to infer complete logic?

That should be possible as well, I think. If you can manage to make that work. I briefly tried some sniffing via wireshark but that didn't work out for me.


Added sl for validating webhook alerts

This service log is used to notify customers they are attempting to remove platform protection webhook to be used with the following SOP https://github.com/openshift/ops-sop/blob/master/v4/alerts/SplunkNonSystemChangeValidatingWebhookConfigurations.md

/lgtm


perl checker first ignores g:syntastic_perl_interpreter

perl checker the very first check (while loading script) ignores g:syntastic_perl_interpreter.
I could wrestle this down with https://github.com/allter/syntastic/commit/f83e1a9586f83e748c4a76d770e54bf222db9d7a
I'm not familiar enough with syntastic internals to understand if it is a good solution...

Please explain what did you do, what did you expect to happen, and what happened instead.  Post your configuration and (hopefully) minimal test files if relevant.

No feedback, no cry.


chore(deps): bump k8s.io/kops from 1.29.2 to 1.30.0 (with generated code)

Bumps k8s.io/kops from 1.29.2 to 1.30.0.

Release notes
Commits

updated-dependencies:

dependency-name: k8s.io/kops dependency-type: direct:production update-type: version-update:semver-minor ...

Oh, the Github checks only run when the merge target is main.

Hah, didn't even notice that it was set to merge back to the dependabot branch. 😂🙈

Hmmm, compile errors, did I only do the generation 🤦🏻♂ Another PR coming up.

This one then (towards main this time): https://github.com/terraform-kops/terraform-provider-kops/pull/119


How to avoid shadowbans

I thinking of using the library I just have concern of Twitter shadowban my account.How can avoid that since I build a bot with python and I got shadowbans after each run.

Hey @mikebgrep , if you respect the twitter developer policy, you don't risk anything :)

They dont like mass following of accounts that's is sure.I will try to scale the action so they don't shadowban me again. Thanks for the replay.


Separate the images from the html file

Is it possible to separate the images from the html file to save the html file and the images in a folder?

Currently this isn't possible, but I would be open to possibly adding this as a feature.
I would need to think about how I would add this, as currently this package is supposed to return one file.
maybe something like
import { randomBytes } from "crypto";
import { writeFileSync } from "fs";

createTranscript(channel, {
    callbacks: {
        resolveImageSrc: (imageData, ext) => {
            const id = randomBytes(20).toString('hex');
            writeFileSync(`./images/${id}.${ext}`, imageData);
            return `/images/${id}`;
        }
    }
});


Go-to-def doesn't work with component attributes

Go-to-def works with components, but not with component attributes. We should add support for this once we have a way to locate attributes within a file (probably requires some work w/C# team).

Going to use a customer facing issue to track this work. Will close this as duplicate of https://github.com/dotnet/razor-tooling/issues/5856


Add includes_all_repositories field to team API

See go-gitea/gitea#6409

structs have been moved to go-gitea/gitea


Implemented columnValuesNotNullConstraint

Description
Implemented columnValuesNotNullConstraint
General Checklist

[ ] Tests added for this feature/bug
if it was a bug, test must cover it.
[ ] Conform by the style guides, by using formatter
[ ] Documentation updated
[ ] (optional) Please add a label to your PR

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 81.226%

Files with Coverage Reduction
New Missed Lines
%

src/whylogs/proto/constraints_pb2.py
1
67.11%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
3914

Relevant Lines:
4694

💛  - Coveralls


loaded model ground truth labels

I have loaded a model using,
model = load_model('weights.h5')
prediction = model.predict(image)
the prediction returns me a numpy array of class probabilities, but I dont know which probability belongs to which class. how to figure it out??

It's the same order as when you created the model.
This issue isn't related to a bug/enhancement/feature request or other accepted types of issue.
To ask questions, please see the following resources :

https://keras.io/
https://keras.io/#support
https://gitter.im/Keras-io/Lobby

Thanks!
If you think I made a mistake, please re-open this issue.


Unreachable Control.Monad.Except's Hackage documentation

Hello,
When I am trying to reach the Control.Monad.Except's documentation (https://hackage.haskell.org/package/mtl-compat-0.2.2/docs/Control-Monad-Except.html), I have this :

Even the suggested link doesn't work : https://hackage.haskell.org/package/mtl-compat/docs/Control-Monad-Except.html

Good catch. Hackage usually renders the documentation for packages automatically when they get uploaded, but since mtl-compat only exposes Control.Monad.Except when building with old versions of mtl, there simply is no documentation to provide for newer versions. I've gone ahead and manually uploaded Haddocks for mtl-compat compiled with GHC 7.10.3, but do note that in general, the API is exactly the same as what mtl exposes in its Control.Monad.Except module.


Package manager installed tooling not detected while in virtualenv

The extension doesn't seem to recognize package manager installed tooling when the active python environment isn't the global one. I keep my general tooling installed via pacman packages, not inside of a virtualenv, so using any sort of editor-executed tooling while working with a virtualenv requires me to reinstall the tools.
Environment data

VS Code version: 1.28.1
Extension version (available under the Extensions sidebar): 2018.9.0
OS and version: Arch Linux
Python version (& distribution if applicable, e.g. Anaconda): 3.7.0
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): global / virtualenv
Relevant/affected Python packages and their versions: linters/formatters

Actual behavior
VS Code prompts me to install pylint/black/etc, even though they are installed via pacman.
Expected behavior
The extension detects the binaries in $PATH, and doesn't prompt me to install something again.
Steps to reproduce:

Have pylint/autopep8/black/etc installed via pacman on Arch Linux (python-pylint, python-autopep8, black-git on the AUR, and so on).
Create an empty virtualenv (virtualenv venv) and enter it (source venv/bin/activate).
Run code from the terminal in the virtualenv (or select the correct environment from the editor).
Save a python file, triggering a message about pylint, a formatter, and so on.

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
workbench.main.js:sourcemap:282 [Extension Host] Python Extension: Linter 'pylint' is not installed. Please install it or select another linter". Error: Module 'pylint' not installed.
	at PythonExecutionService.<anonymous> (/home/jake/.vscode/extensions/ms-python.python-2018.9.0/out/client/common/process/pythonProcess.js:96:27)
	at Generator.next (<anonymous>)
	at fulfilled (/home/jake/.vscode/extensions/ms-python.python-2018.9.0/out/client/common/process/pythonProcess.js:12:58)
	at <anonymous>
t.log @ workbench.main.js:sourcemap:282
workbench.main.js:sourcemap:2374 Linter pylint is not installed.
t.onDidNotificationChange @ workbench.main.js:sourcemap:2374
2workbench.main.js:sourcemap:282 [Extension Host] Python Extension: Linter 'pylint' is not installed. Please install it or select another linter". Error: Module 'pylint' not installed.
	at PythonExecutionService.<anonymous> (/home/jake/.vscode/extensions/ms-python.python-2018.9.0/out/client/common/process/pythonProcess.js:96:27)
	at Generator.next (<anonymous>)
	at fulfilled (/home/jake/.vscode/extensions/ms-python.python-2018.9.0/out/client/common/process/pythonProcess.js:12:58)
	at <anonymous>

FWIW, I think the issue is around here:
https://github.com/Microsoft/vscode-python/blob/79fe96e387e0717cfefc789815c2c257a05a7116/src/client/formatters/helper.ts#L41-L44
And:
https://github.com/Microsoft/vscode-python/blob/79fe96e387e0717cfefc789815c2c257a05a7116/src/client/common/process/pythonToolService.ts#L17-L23
The extension's current behavior is to treat names that aren't paths to be module names, then try to execute the tools via python -m <name>. Inside the virtualenv, this module does not exist, so executing it fails (and python -m does not go looking at the global installation for modules). Outside of the virtualenv, running something like python -m black works just fine since the interpreter is different.
I think it'd be better to try executing via execPath when moduleName fails. That way, if tooling is installed in the virtualenv, then it'll be chosen first, otherwise $PATH is searched as per usual.
Alternatively, the extension could stop executing tools via python -m entirely. AFAIK when you install a package that has an executable component with pip in a virtualenv, it goes into venv/bin, which is in $PATH when the virtualenv is active. But, I don't know how the extension executes python (either by manipulating $PATH or by running the specific path directly), or how it works in something like conda.
(Minor sidenote: I feel like it might be a bit fragile to assume that all Python-related tools can be run as modules, since someone could feasibly release faster-autopep8 written completely in C and change their pathName setting from autopep8 to faster-autopep8 assuming it would work, only to get an error about a module not existing. But, that's probably not a real concern right now -- I just thought I'd write that thought down.)

So we had issues previously when simply looking for e.g. black on PATH versus our current method of looking for python -m black. IOW this is a "damned if you do, damned if you don't" situation and this is the best solution we could come up with. This is also why we let people specify complete paths to their tools if they are installed elsewhere as binary tools.

@jakebailey nope, all those discussions took place over Teams nearly a year ago.
If you want to open a new issue for a feature request to also search for the binary we can consider it.


Use vndr for managing libnetwork dependencies

Using godep it has been difficult to update package dependencies. Moving to vndr tool for managing libnetwork dependencies.
Vast majority of the files are just renaming from Godeps/_workspace directory to vendor directory.
Some of the dependencies were directly using Godep (coreos/etcd). Updated such packages to the latest revision and updated its dependencies as well.
Makefile has been changed to directly use go tools since go tooling recognizes the vendor directory.
Signed-off-by: Santhosh Manohar<EMAIL_ADDRESS>

@aboch @mavenugo Fixed the windows build the go test to ignore the vendor directory. PTAL

LGTM

@sanimej Thanks for saving us from godep issues :-)
LGTM


popovers: Hide mark as unread button for spectators.

Since spectators cannot mark messages as unread, hide this button in message actions popover.
discussion: https://chat.zulip.org/#narrow/stream/101-design/topic/mark.20as.20unread

Merged, thanks @amanagr!


fix :bug: correct colors for wallet buttons

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #4390
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[x] I've tested it at </bsx/collection>
[x] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 20

😍 Perfect, I’ve sent the payout
💵 $20 @ 26.61 USD/KSM ~ 0.752 $KSM
🧗 FNyt7T1xdbhN7dagf7yGYCRJuE3R45VmTCE3tjzy1rKxa7y
🔗 0x82c4edb59395af1dbcac4e4bf5b6c086ccb6a9400a0beb99a50a53ce5dad611a
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


No Longer Able To Duplicate The Value of the X-B3-Traceid Header using request_headers_to_add

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
<EMAIL_ADDRESS>where the issue will be triaged appropriately.
Title: No Longer Able To Duplicate The Value of the X-B3-Traceid Header using request_headers_to_add
Description:
Under previously released versions of Envoy (<1.22) we were able to duplicate the value of the X-B3-Traceid header to another upstream header that we use internally. This is to support customers who still expect a custom header.
We achieved this using header formatting in the request_headers_to_add configuration block, like so:
  routes:
    - match:
        prefix: "/"
      route: { cluster: app }
      request_headers_to_add:
        - header:
            key: Legacy-Trace-Header
            value: "%REQ(x-b3-traceid)%"
          append: false

However, since 1.22, this behaviour has changed.
Now, there are two separate outcomes depending on the presence of the x-b3-traceid header in the downstream request:

If the header is not sent, the custom header is missing entirely
If the header is sent, the header is passed to the cluster with no modification.

Repro steps:

Clone my demonstration repo.
Run docker compose up
Load the following links up in your browser, corresponding to different Envoy versions. Notice how, on 1.22 and up, the Example-Traceid header is absent in the echoed response for all versions > 1.21.

v1.19.0
v1.20.0
v1.21.0
v1.22.0
v1.23.0
v1.24.0

Send a crafted response to http://localhost:1210 with the header x-b3-traceid set to foobar. Notice that the Example-Traceid header value seen in the JSON response is overwritten by the trace ID generated by Envoy.
Send a crafted response to http://localhost:1220 with the header x-b3-traceid set to foobar. Notice that the Example-Traceid header value seen in the JSON response is not overwritten by the trace ID generated by Envoy.

If this is not the expected way to achieve this, then we'll happily use an alternative configuration pattern to achieve the same result elsewhere.

Note: The Envoy_collect tool
gathers a tarball with debug logs, config and the following admin
endpoints: /stats, /clusters and /server_info. Please note if there are
privacy concerns, sanitize the data prior to sharing the tarball/pasting.

Admin and Stats Output:

Include the admin output for the following endpoints: /stats,
/clusters, /routes, /server_info. For more information, refer to the
admin endpoint documentation.

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Config: Available here
Logs:

Include the access logs and the Envoy logs.

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Call Stack:

If the Envoy binary is crashing, a call stack is required.
Please refer to the Bazel Stack trace documentation.

Hm. I think this is probably the likely culprit: #20503. The request_headers_to_add operations are performed in that call to finalizeRequestHeaders and the injection of the tracing span's context into the request headers no longer happens before that point. That explains why the tracing headers make it upstream but your copy to an alternate name fails. cc @wbpcode

Yeah, it's my mistake. It' an unexpected behavior change. It's easy to revert the behavior but there may be repeated injecting.

/assign I will try to make a fix.

Our users hit this issue as well. I'm thinking that (1) it's not safe to assume the order of header insertion in HCM, (2) trace ID is actually available on downstream but it's not exposed to the formatters.

Our users hit this issue as well. I'm thinking that (1) it's not safe to assume the order of header insertion in HCM, (2) trace ID is actually available on downstream but it's not exposed to the formatters.

I am thinking should we create a header mutation filter that could be configured as downstream http filter or upstream http filter. Then we can control the order of header insertion/mutation completely? WDYT cc @kyessenov

I like the idea of breaking apart the HCM features with dedicated extensions. Might be complicated because these header operations nest and inherit between routes, hosts, and actions.

I want to give it a try. May be we can make it a alternative of current headers_to_add. Anyway, a http filter will not make thing worse.

There is a valid point about moving some of the HCM features to upstream HTTP filters because then they could be "phased" after the downstream processing, and apply to non HTTP downstream (e.g. TCP). Before you make a PR, I think this might be worth discussing with @alyssawilk and others.


Introduced sentence case text transform class

Use text-sentencecase to ensure only the first character in the given
text block is shown
in uppercase.

We're no longer accepting new features into Bootstrap v3, but feel free to open a new pull request for this against the v4-dev branch for Bootstrap v4. Thanks!

Additionally, the "make everything lowercase, then just uppercase the very first letter" approach will of course only work in situations where there are no own names, brand names, acronyms etc that need to be capitalised anywhere in the sentence. And there's no way for an author to override the lowercasing if they wanted to just make an exception there.


Behavior change v-model  on input type number cast value to number by defualt

Version
3.2.26
Reproduction link
jsfiddle.net/8vqaotbx/1/
Steps to reproduce
create input element type number
the value cast to number type
On Vue version 2 it not do it by defualt , it is big chage i have big project that expected the value return is string
What is expected?
Mybe can add to core modifier numeric that not cast the value to number.
Or add flag that Vue not do it by defualt
What is actually happening?
v-model cast value of input number to number type

https://github.com/vuejs/core/blob/9c304bfe7942a20264235865b4bb5f6e53fdee0d/packages/runtime-dom/src/directives/vModel.ts#L52

This seem to be the a documented feature for vue 3, which is not vue 2 .

as a workaround  for this use case, you can use .trim modifier to get a string
 <input type="number" v-model.trim="phoneNumber">

@lidlanca
Thank for the replay and solution it work
But i think that the cast not need to be by default  is different behavior
Also the documented  in not clear "Vue can automatically  convert..." mybe "Vue automatically try to convert..."

perhaps vue should not have casted by default, keep this issue open, see what core team has to say.
feel free to suggest improvement to the docs if you find the current phrasing confusing
https://github.com/vuejs/docs/issues
also note that the docs will soon be updated to this, which if find even more misleading.

source

This was working properly in earlier 3.x versions but then the breaking change was introduced

I was also affected by this change.
Until now, the length of the string was used to detect that the input filed was empty.
After the change, if the input field is empty it will return a string type and if it is not empty it will return a number type.
In the case of type=number, there was a change to cast to a number as default, but the type is not unified.


CLR Profiling API docs: clarify which versions of .NET Framework and .NET Core the ICorProfilerInfo* interfaces support

Issue description
The doc for ICorProfilerInfo10 states that it is available starting .NET Core 3.0, but doesn't specify if it also made it into .NET Framework.
The doc for ICorProfilerInfo9 states that it is available starting .NET Core 2.2, but doesn't specify if it also made it into .NET Framework.
The doc for ICorProfilerInfo8 states that it is available starting .NET Framework 4.7.2, but doesn't specify what version of .NET Core it's supported on.
These details would be very useful for profiler implementors to have. I'd be very happy to send in a PR for this, but I couldn't find an authoritative answer to these question anywhere online. Appreciate any help. /cc @davmason
Target framework
Check the .NET target framework(s) being used, and include the version number(s).

[-] .NET Core
[-] .NET Framework
[ ] .NET Standard

Hi @OmerRaviv
ICorProfilerInfo8 and ICorProfilerCallback9 are currently the last interfaces supported on .net framework. It is very unlikely given the servicing policy of 4.8 that any future ICorProfiler interfaces will appear on .net framework.
ICorProfiler9/ICorProfilerCallback10 (and future additions) are only on .net core.


Some packages are listed in the gallery but not in registration

MvcExtensions.Unity <IP_ADDRESS>4 is listed in the gallery but not listed in registration2-gz.
Twilio 2.0.2 is listed in the gallery but not listed in registration2-gz.

MvcExtensions.Unity <IP_ADDRESS>4 issue was caused by https://github.com/NuGet/NuGetGallery/issues/3709
Probaby missed the reflow before, reflowed it now.


Keyboard always types in English regardless of selected Input Language

I tried to use xrdp in RHEL 9, AlmaLinux 9  and Fedora 36.
In all of the distros I faced the same issue with the Input Language switch in xrdp session.
Regardless of what language is selected the keyboard always types in English.
Remote Desktop client was on Windows 11 with regular windows keyboard.
These Linux distributions use xrdp 0.9.21 from epel/9 repo - xrdp-0.9.21-1.el9.x86_64.rpm
Steps to reproduce the issue:
Install minimal OS. We can use cloud instance or Virtual box (with bridged Adapter) + install ISO.
Install epel, Workstation group and xrdp as described below:
sudo dnf upgrade
sudo dnf install yum-utils
sudo dnf config-manager --set-enabled crb
sudo dnf install epel-release
sudo dnf upgrade

sudo dnf group install Workstation
sudo systemctl set-default graphical
sudo reboot

sudo dnf install xrdp
sudo systemctl start xrdp
sudo systemctl enable xrdp

sudo systemctl start firewalld
sudo systemctl enable firewalld
sudo firewall-cmd --permanent --zone=public --add-service=rdp
sudo systemctl restart firewalld

Connect to the box using Remote Desktop
Open Settings app. (in GNOME Desktop)
Go to Keyboard - Input Sources - + - Russian
Switch to “ru” using input lang selector in the top bar
Try to type smth in some field - it will type in English instead of Rus

Additional Observations:

The issue exist only in xrdp session. If I use regular graphical Gnome session (e.g. in Virtual Box) the Input Language switching works as expected.
It might look like xrdp does not switch the Input Language because keyboard still types in English in "ru" mode. However some keys print nothing in "ru" mode. So, xrdp is actually switches to something in "ru" mode which looks like English but with missing letters.
Keys which type nothing in "ru" mode:

All keys from bottom row - zxcvbnm
Other keys - `[]'

I'm a bit surprised that all RHEL-like distros are affected by this issue and nobody noticed/reported it.
I tried distros from other camp - Ubuntu 22.04 and Debian 11 - they do not have this xrdp and input language issue. Btw, they use older xrdp version - 0.9.17 and 0.9.12

Yes, we have the solution!!!
We need to change xrdp.ini to use [Xorg] instead of [Xvnc].
Step by Step instructions:
## install xorgxrdp
sudo dnf install xorgxrdp

## edit /etc/xrdp/xrdp.ini
sudo vi /etc/xrdp/xrdp.ini

## Comment out entire [Xvnc] block to Disable it.

#[Xvnc]
#name=Xvnc
#lib=libvnc.so
#username=ask
#password=ask
#ip=<IP_ADDRESS>
#port=-1

## Ucomment [Xorg] block to Enable it.

[Xorg]
name=Xorg
lib=libxup.so
username=ask
password=ask
ip=<IP_ADDRESS>
port=-1
code=20

# Save the file and Restart xrdp service
sudo systemctl restart xrdp

# Done! Input language switch should work in Remote Desktop session in GNOME now.
Tested on Fedora 36, AlmaLinux 9, CentOS Stream 9, CentOS 7

The solution was found by ZOTOVP on Mar 2023 - the article

Closing as solved.

I faced this issue on Fedora 37. The solution with uncommenting the [Xorg] block in xrdp.ini worked for me. However, is it possible to have a fix that will make language switching on Fedora work "out of the box", without manual changes in /etc/xrdp/xrdp.ini? For example, the package installer could uncomment the [Xorg] block in xrdp.ini when installing on Fedora.

@RomanMeR  - the EPEL packagers have decided to default to Xvnc as the X server. We ship it with Xorg as the default, but downstream apply a patch here to change this.
There is a good reason why the EPEL package would ship with Xvnc as the default, as the same package spec file is used on RHEL. The update cycles for RHEL and EPEL are different, and an Xorg update in RHEL could lead to breakages.
In any case we can't do anything about it here. You could make a suggestion on the RedHat Bugzilla about treating Fedora differently. I don't know if they'd go for that.

I discovered that the solution with uncommenting the [Xorg] block in xrdp.ini works only during first XRDP connection. If I disconnect and after some time reconnect, switching to Russian language stop working both with Shift+Alt and by mouse in language panel. Please help!
OS: Fedora 38

[user@fedora ~]$ dnf list xrdp*
Последняя проверка окончания срока действия метаданных: 0:01:51 назад, Ср 27 сен 2023 13:02:54.
Установленные пакеты
xrdp.x86_64                                                                                1:0.9.23-1.fc38                                                                                @updates
xrdp-selinux.x86_64                                                                                1:0.9.23-1.fc38                                                                                @updates
Имеющиеся пакеты
xrdp.i686                                                                                1:0.9.23-1.fc38                                                                                updates
xrdp-devel.i686                                                                                1:0.9.23-1.fc38                                                                                updates
xrdp-devel.x86_64                                                                                1:0.9.23-1.fc38                                                                                updates

sesman.ini.txt
xrdp.ini.txt
xrdp_keyboard.ini.txt
xrdp.log
xrdp-sesman.log

Same issue on Rocky 9.3. Uncommenting [Xorg] doesn't start Desktop Session.

Rocky 9.3. Same issue. Solution with [Xorg] section helps only for the 1st login. Switching breaks after reconnect.

I think I can see what's going on here.
If anyone monitoring this thread would like to comment on #3322, that could be useful.


Add test for individually searchable columns

Note: If there are no individually searchable columns the test will be run ->with([]) which pest intern won't run (it will be ignored). This applies to all other tests btw.

@dissto - If no columns are available; ->with([]), the test will crash/fail. This issue may also occur in other tests.

Is that again a windows thing?! The test were completely ignored when I ran with with an empty array.
->with() accepts a closure, maybe it should be run from within a closure to correctly ignore it when passing an empty array?
@CodeWithDennis

[] or fn() => [] both result in;
The data provider specified for P\Tests\Feature\BlogResourceTest::__pest_evaluable_it_can_individually_search_by_column is invalid
Empty data set provided by data provider


Mobile Design: Staff Pets index table should render in cards below width 1100 px

Currently on baja/staff/pets we render a table of pets. This is good for desktop, but not good for mobile. Instead, when the screen width is less than 1100 px, we should render each pet in a card, similar to how we do at baja/adoptable_pets. We want to keep pagination for mobile.
Create a new partial (using partials/pet_card is easiest), that includes

the first image of the pet, if available, or the placeholder image,
the pet name,
sex,
breed,
and radio buttons for pause applications, and publish.

Acceptance criteria

pets are rendered in cards if width is less than 1100px, otherwise rendered in the table

Hi @kasugaijin I can work on this issue.. Can you please assign it? Thanks

Sure thing!
I think for this we want to render both the table and the cards html at the same time but hide/show the correct markup for the screen width. Let me know if you have questions.

Sounds good.. Will implement accordingly to render card for screen width below 1100 px and otherwise table.

Quick update @sarvaiyanidhi @jmilljr24 rightly pointed out that we should just use the bootstrap grid sizing here, so could you please set the transition between cards and table to bootstrap class xl which is 1,200 px


Please provide TypeScript Type Definitions (e.g. a "index.d.ts" file)

Greetings and thanks for the excellent library.
The year is 2020, and most of the internet is migrating their projects from JavaScript to TypeScript (if they have not done so already). Thankfully, TypeScript projects can still import legacy JavaScript libraries, but there has to be a type definitions file, e.g. a "index.d.ts" file. The type definition file is is simply a skeleton file that shows the various exported functions and their return types, similar to a ".h" file in the C programming language. Here's an example from the TypeScript webpage.
Can you provide this for the autoComplete.js library? It would allow people to seamlessly use this library in their TypeScript projects.

Use it yourself npx typescript src/**/*.js --declaration --allowJs --emitDeclarationOnly --outDir types

Use it yourself npx typescript src/**/*.js --declaration --allowJs --emitDeclarationOnly --outDir types


qutebrowser: 3.0.0 -> 3.0.2

Changelog: https://www.qutebrowser.org/doc/changelog.html
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Diff: https://github.com/qutebrowser/qutebrowser/compare/None...v3.0.2

doesn't sound right

Hmm, weird, that must have been put there by nix-update. Anyway, thanks, it's fixed now.

Can confirm build on x86_64-linux.
(As this fixes some nasty qt bug for me, I'll keep running the result/bin until this is merged, as I am to lazy to patch this in my flake :stuck_out_tongue:)

Working on building this on top of master atm. Looks like qt was just updated to the 6.6 release and the caches haven't been populated so I have to build all of webengine. I'll leave it all night, but assuming there are no issues I'll go ahead and merge when it's done.

Result of nixpkgs-review pr 262277 run on x86_64-linux 1

Rebased to master, still builds fine for me without rebuilding anything.

Rebased to master, still builds fine for me without rebuilding anything.

My build failed with OOM. I should have probably built it on my system with 64G, but in any case I'll go ahead and merge since you were successful. Thanks


Mockups for design improvements

Here are a few ideas for consideration when time allows.
The start page - "Projects":

Material-icons top right: help, settings, login/profile
The list of available projects shows meta data: 32px icon, icons to link to project website and bugtracker.
Project - "Files":

Project - "Application" - translation page:

Flag of current language at top right.
Project - "Application - Edit":

As described in #15.

Implemented in 4cea484fd286158f058c2b37c67b9f503981c6ef.


fix(stepper): Fix the stepper's animation & style

:tada: This PR is included in version 9.2.3-rc.1 :tada:
The release is available on:

GitHub release
npm package (@next dist-tag)

Your semantic-release bot :package::rocket:


ERR_PACKAGE_PATH_NOT_EXPORTED error from colord

I'm unable to build my app due to an error coming from a dependency that relies on Colord. Any help with this would be appreciated!
When running npm run build, I get the following error:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './plugins/names' is not defined by "exports" in ./node_modules/colord/package.json

Just saw that v1.7.1 shipped about two hours ago, which is when everything broke for me.

Hi! Will do my best to help you. What bundler (Webpack, rollup, or another) do you use to build your app?

I'm using Webpack in a Gatsby app. Much appreciated!

What dependency pulls Colord in your project? cssnano?

The problem seems to originate with node_modules/postcss-colormin/dist/colours.js:10:37

Just installed Gatsby and with "gatsby-plugin-postcss" enabled and "npm run build" works well.
Should I config something else?
P.S. What Node.js version do you have?

I'm on 12.19 locally, then I believe it's 14 in the Codebuild job (both are failing)

Looks like this may be an issue with cssnano? I just came across this: https://github.com/cssnano/cssnano/issues/1110

Could you please share with me your Gatsby project config? Especially the thing related to CSS bundling.

The repo is private, but here's my package.json file, hopefully that helps. I'll dig through the gatsby-config file and see if there's anything helpful in there, but I'm not quite sure what I'm looking for as I'm not directly using colord or cssnano/postcss-colormin.
// ./package.json

{
  "name": "stackery-io",
  "scripts": {
    "develop": "gatsby develop",
    "build": "gatsby build",
    "serve": "gatsby serve",
    "clean": "rm -rf public && rm -rf .cache",
    "format-output": "prettier src/**/*.{js,jsx}",
    "format": "prettier --write src/**/*.{js,jsx}",
    "lint-errors": "eslint src/**/*.{js,jsx} --quiet",
    "lint": "eslint src/**/*.{js,jsx}",
    "start": "npm run develop",
    "test": "eslint . --quiet && cy:run",
    "cy:open": "cypress open --project ./functions/VerificationTests/ --config-file cypress.json",
    "cy:run": "cypress run --project ./functions/VerificationTests/ --config-file cypress.json",
    "test:e2e": "start-server-and-test develop http://localhost:8000 cy:open"
  },
  "dependencies": {
    "@babel/core": "^7.14.3",
    "@deckdeckgo/highlight-code": "^2.6.0",
    "@emotion/babel-plugin": "^11.3.0",
    "@emotion/eslint-plugin": "^11.2.0",
    "@emotion/react": "^11.4.0",
    "@emotion/styled": "^11.3.0",
    "@material-ui/core": "^4.11.4",
    "@material-ui/icons": "^4.11.2",
    "@raae/gatsby-remark-oembed": "^0.1.1",
    "@styled-icons/fa-brands": "^10.26.0",
    "@styled-icons/fa-solid": "^10.32.0",
    "algoliasearch": "^4.8.6",
    "amazon-cognito-identity-js": "^5.0.1",
    "babel-plugin-emotion": "^11.0.0",
    "babel-plugin-styled-components": "^1.12.0",
    "bootstrap": "^5.0.1",
    "colord": "1.7.0",
    "crypto-browserify": "^3.12.0",
    "dayjs": "^1.10.4",
    "dotenv": "9.0.2",
    "gatsby": "^3.5.0",
    "gatsby-cli": "^3.5.0",
    "gatsby-image": "^3.5.0",
    "gatsby-plugin-algolia": "^0.17.0",
    "gatsby-plugin-anchor-links": "^1.2.1",
    "gatsby-plugin-breakpoints": "^1.3.3",
    "gatsby-plugin-catch-links": "^3.5.0",
    "gatsby-plugin-csp": "^1.1.3",
    "gatsby-plugin-emotion": "^6.5.0",
    "gatsby-plugin-feed": "^3.5.0",
    "gatsby-plugin-gdpr-cookies": "^2.0.0",
    "gatsby-plugin-google-analytics": "^3.5.0",
    "gatsby-plugin-google-fonts": "^1.0.1",
    "gatsby-plugin-google-tagmanager": "^3.5.0",
    "gatsby-plugin-manifest": "^3.5.0",
    "gatsby-plugin-nprogress": "^3.5.0",
    "gatsby-plugin-offline": "^4.5.1",
    "gatsby-plugin-react-helmet": "^4.5.0",
    "gatsby-plugin-robots-txt": "^1.6.2",
    "gatsby-plugin-rollbar": "^1.1.0",
    "gatsby-plugin-sass": "^4.5.0",
    "gatsby-plugin-sharp": "^3.5.0",
    "gatsby-plugin-sitemap": "^4.1.0",
    "gatsby-plugin-smoothscroll": "^1.2.0",
    "gatsby-plugin-styled-components": "^4.5.0",
    "gatsby-plugin-typography": "^3.5.0",
    "gatsby-remark-classes": "^1.0.0",
    "gatsby-remark-copy-linked-files": "^4.2.1",
    "gatsby-remark-embed-video": "^3.1.1",
    "gatsby-remark-highlight-code": "^2.2.1",
    "gatsby-remark-images": "^5.2.1",
    "gatsby-remark-prismjs": "^5.2.1",
    "gatsby-remark-reading-time": "^1.1.0",
    "gatsby-remark-responsive-iframe": "^4.2.1",
    "gatsby-source-filesystem": "^3.5.0",
    "gatsby-source-graphql": "^3.5.0",
    "gatsby-theme-material-ui": "^2.0.1",
    "gatsby-transformer-remark": "^4.2.0",
    "gatsby-transformer-sharp": "^3.5.0",
    "install": "^0.13.0",
    "jquery": "^3.6.0",
    "lodash": "^4.17.21",
    "mdb-react-ui-kit": "^1.0.0-beta5",
    "mdbreact": "^5.0.2",
    "normalize.css": "^8.0.1",
    "popper.js": "^1.16.1",
    "prismjs": "^1.23.0",
    "prop-types": "^15.7.2",
    "query-string": "^7.0.0",
    "react": "^17.0.2",
    "react-bootstrap": "^1.6.0",
    "react-cookie-consent": "^6.2.3",
    "react-device-detect": "^1.17.0",
    "react-dom": "^17.0.2",
    "react-headroom": "^3.1.1",
    "react-helmet": "^6.1.0",
    "react-instantsearch-dom": "^6.11.0",
    "react-select": "^4.3.1",
    "react-typist": "^2.0.5",
    "react-typography": "^0.16.20",
    "remarkable": "^2.0.1",
    "smooth-scroll": "^16.1.3",
    "stream-browserify": "^3.0.0",
    "styled-components": "^5.3.0",
    "typography": "^0.16.21"
  },
  "devDependencies": {
    "@types/remarkable": "^2.0.1",
    "axe-core": "^4.2.1",
    "babel-eslint": "^10.1.0",
    "cypress": "^7.3.0",
    "cypress-axe": "^0.12.2",
    "eslint": "^7.26.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-config-semistandard": "^15.0.1",
    "eslint-loader": "^4.0.2",
    "eslint-plugin-import": "^2.23.2",
    "eslint-plugin-jsx-a11y": "^6.4.1",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-prettier": "^3.4.0",
    "eslint-plugin-promise": "^5.1.0",
    "eslint-plugin-standard": "^5.0.0",
    "eslint-webpack-plugin": "^2.5.4",
    "gatsby-plugin-eslint": "^3.0.0",
    "lighthouse": "^7.5.0",
    "prettier": "^2.3.0",
    "semistandard": "^16.0.0",
    "start-server-and-test": "^1.12.2"
  }
}

This is my project configuration.
{
  "name": "xxxxx",
  "version": "1.0.0",
  "scripts": {
    "ng": "ng",
    "clean": "rm -rf dist",
    "start": "ng serve --port 4201 --proxy-config proxy.conf.json --hmr",
    "build": "node --max_old_space_size=6144 ./node_modules/@angular/cli/bin/ng build --dev",
    "postinstall": "ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points && find node_modules/moment/locale -type f -not -name 'en-gb.js' -not -name 'en.js' -not -name 'ru.js' -not -name 'fr.js' -not -name 'de.js' -not -name 'kk.js' -not -name 'tr.js' | xargs rm",
    "prettier": "prettier write \"./**/*.{ts,css,scss,json,html}\""
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^11.2.14",
    "@angular/cdk": "11.2.12",
    "@angular/common": "^11.2.14",
    "@angular/compiler": "^11.2.14",
    "@angular/core": "^11.2.13",
    "@angular/flex-layout": "^11.0.0-beta.33",
    "@angular/forms": "^11.2.14",
    "@angular/material": "11.2.12",
    "@angular/material-moment-adapter": "11.2.12",
    "@angular/platform-browser": "^11.2.14",
    "@angular/platform-browser-dynamic": "^11.2.14",
    "@angular/router": "^11.2.14",
    "@fortawesome/angular-fontawesome": "^0.9.0",
    "@ngx-translate/core": "13.0.0",
    "@ngx-translate/http-loader": "^6.0.0",
    "@types/http-status-codes": "^1.2.0",
    "angular-imask": "^6.0.7",
    "classlist.js": "1.1.20150312",
    "core-js": "^3.12.1",
    "lodash": "4.17.21",
    "moment": "2.29.1",
    "ngx-captcha": "^9.0.1",
    "ngx-destroy-subscribers": "^7.0.1",
    "ngx-webstorage": "^7.0.1",
    "rxjs": "6.6.7",
    "web-animations-js": "^2.3.2",
    "zone.js": "~0.11.4"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^0.1102.12",
    "@angular/cli": "^11.2.12",
    "@angular/compiler-cli": "^11.2.14",
    "@fortawesome/fontawesome-pro": "^5.15.3",
    "@fortawesome/fontawesome-svg-core": "^1.2.35",
    "@fortawesome/free-solid-svg-icons": "^5.15.3",
    "@fortawesome/pro-light-svg-icons": "^5.15.3",
    "@fortawesome/pro-regular-svg-icons": "^5.15.3",
    "@fortawesome/pro-solid-svg-icons": "^5.15.3",
    "@types/jasmine": "3.7.4",
    "@types/jasminewd2": "2.0.9",
    "@types/lodash": "4.14.169",
    "@types/node": "^15.0.3",
    "@types/webpack-env": "1.16.0",
    "codelyzer": "^6.0.2",
    "jasmine-core": "~3.7.1",
    "jasmine-spec-reporter": "~7.0.0",
    "prettier": "2.3.0",
    "protractor": "~7.0.0",
    "replace-in-file": "^6.2.0",
    "sass": "^1.32.13",
    "ts-node": "9.1.1",
    "tslint": "~6.1.3",
    "tslint-config-prettier": "^1.18.0",
    "typescript": "4.1.5",
    "webpack-bundle-analyzer": "4.4.1"
  },
  "peerDependencies": {
    "tslib": "^2.2.0"
  },
  "resolutions": {
    "webpack": "5.4.0"
  }
}

Thx! Do you have any CSS-related settings in the "gatsby-config.js"?

I don't have any CSS-related settings, those I am using these theming packages:
gatsby-plugin-emotion
gatsby-plugin-typography
gatsby-plugin-styled-components
gatsby-plugin-google-fonts

Here's everything that uses postcss-colormin AFAIK:
gatsby-plugin-webfonts
cssnano-preset-default

But those aren't in my gatsby-config.
and from my package-lock:

    "postcss-colormin": {
      "version": "5.1.0",
      "resolved": "https://registry.npmjs.org/postcss-colormin/-/postcss-colormin-5.1.0.tgz",
      "integrity": "sha512-5s+VNfQ5CsR6yvBc6Tc8NK9cxb/c8sA547zy+8ofL04gs/GygmOcVZt2s6jJn7TvntAw0Bp6MDpq4bd51EPwdw==",
      "requires": {
        "browserslist": "^4.16.0",
        "colord": "^1.7.0",
        "postcss-value-parser": "^4.1.0"
      }

Released v1.7.2 with a simplified exports map. I assume that your bundler or Node can't process wildcarted subfolder exports, so I defined all of them manually.
Could you update colord in your lock files and check how it works?

To perform a quick test, you can run npm install<EMAIL_ADDRESS>-D in your project root. It should update "colord" that installed by "postcss-colormin".

Tested in Next.js and Parcel. Works well

Awesome, thanks so much for the quick fix! I'll start my builds again and let you know how it goes.

Tested in my Webpack and Node.js application as well. No errors, works as expected. Really hope that everything is fine in your app as well.

That worked, and our build is unblocked. Thanks again for the quick turnaround!

Thanks for helping me here and good luck with your projects!

I got the exact same issue about the same time as @bildungsroman. Thanks @omgovich! Your workaround did the trick. You saved me a lot of headache.


net/freeradius: TTLS type and LDAP in PAP

Fix the possibility to select EAP TTLS Type

Fixed in PAP the use of LDAP.

Wasn't this handled here: https://github.com/opnsense/plugins/issues/2421

thanks so there was removal missing on this end and this PR is fine I gather?

@clanto007 If you set a Default EAP Type value and a Default EAP TTLS Type value, nothing happens to the first one.
Can you optimize it a bit please?

@clanto007 If you set a Default EAP Type value and a Default EAP TTLS Type value, nothing happens to the first one.
Can you optimize it a bit please?

I'm trying, but I don't have this problem, witch values do you select that don't change?

@mimugmail I don't see the problem that you quoted on 15 november, witch values do you select that don't change?

@mimugmail I don't see the problem that you quoted on 15 november, witch values do you select that don't change?


238 - Integration single file download

What this PR does / why we need it:
This pull request establishes a connection between the file download buttons in the files table rows and the access API for downloading files.
Which issue(s) this PR closes:

Closes #238

Special notes for your reviewer:
The integration of files tabular data is currently under review:

https://github.com/IQSS/dataverse-frontend/pull/227

As a result, the tabular files' download options won't appear identical to those in the JSF frontend until the aforementioned pull request is merged. Ideally, PR #227 should be merged into the develop branch before this one so that the tabular download options align with the JSF frontend.
Suggestions on how to test this:
Step 1: Run the development environment

Run npm I
cd packages/design-system && npm run build
cd ../../
Check that you have a  .env file such as the .env.example, with the VITE_DATAVERSE_BACKEND_URL=http://localhost:8000 variable
cd dev-env
./run-env.sh unstable
To check the environment go to http://localhost:8000 and check your local dataverse installation

Step 2: Test Dataset View mode with the implemented changes to download the files

Go to http://localhost:8000
Login as admin using username: dataverseAdmin and password: admin1
Create a new Dataset
Upload some files to the dataset
From the dataset view mode copy the search parameters from the url. Ex.: ?persistentId=doi:10.5072/FK2/LHGRHP&version=DRAFT
Go to http://localhost:8000/spa/datasets and paste the search parameters. Ex.: http://localhost:8000/spa/datasets?persistentId=doi:10.5072/FK2/LHGRHP&version=DRAFT
You are currently viewing the same dataset in the SPA. In the files table, locate the "Access File" dropdown on the right of each row. From the dropdown, select the option to download the file and verify that it is successfully downloaded.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No
Is there a release notes update needed for this change?:
No
Additional documentation:

coverage: 98.462% (+0.04%) from 98.426%
when pulling d458245ce82a63c67fc1165f18087545f7fcc253 on feature/238-integration-single-file-download
into 0c9a2b86f91fac4c7f379f8ab69859a4c60e4904 on develop.

@MellyGray Please, can you resolve conflicts?

@GPortas conflicts resolved

https://github.com/IQSS/dataverse-frontend/assets/17010447/1c780e11-c4d2-4741-9493-1194000dca72

@MellyGray
Tabular files work well for both original and archival formats. But when selecting RData the following error appears:
{"status":"ERROR","code":404,"message":"datafile access error: requested optional service (image scaling, format conversion, etc.) could not be performed on this datafile."}

@GPortas The same error appears in JSF when trying to download a tabular file in RData format.
I found this in the documentation:

The Dataverse Software uses R to handle tabular data files. The instructions below describe a minimal R Project installation. It will allow you to ingest R (.RData) files as tabular data and to export tabular data as .RData files. R can be considered an optional component, meaning that if you don’t have R installed, you will still be able to run and use the Dataverse Software - but the functionality specific to tabular data mentioned above will not be available to your users.

I think we need to install R in the dev-env if we want to test that feature, although I don't think it's necessary since if the users install that option, it should work as expected

@MellyGray In my opinion the download option in R format should not be rendered if R is not configured in Dataverse. To do this we could use a public setting that allows the SPA to know if R is configured in the Dataverse instance.
It certainly happens that when testing JSF on my localhost, I see that the R option is available, although clicking it does nothing. I think this behavior should not be expected for the user. Even though JSF handles it this way, I think the SPA should use the approach I described above (conditional rendering based on a public setting).
Maybe @scolapasta, @jggautier or @pdurbin can share their thoughts on this and if there is a reason that explains why it is done that way in JSF.

By the way, I think the conditional rendering solution I described above should not block the PR at all. Whatever solution we propose, I would implement it in another issue.
For this PR I think we should catch the error that occurs (black screen) when clicking the R option, so that it does nothing (like in JSF) but doesn't break. @MellyGray

@GPortas  I can't handle the error since it's an href. Besides, the same black screen behavior is happening in JSF, so I think it should be okay like this until we decide to implement hiding the RData option if R is not installed.
https://github.com/IQSS/dataverse-frontend/assets/23359572/96f15b4d-9fda-4b01-bc4e-e0f7855da60d

In my opinion the download option in R format should not be rendered if R is not configured in Dataverse.

Yes, @BPeuch and probably others agree with you. That's almost exactly how he worded it:

https://github.com/IQSS/dataverse/issues/8711


fix: ⚡ use github for the logos

getting this error:

getting this error (although it seems to work anyway):

I have the issue as well let me check locally!

@xat Not very elegant but I think it's fixed. I set the initial value of theme to unset


#Couldn't remove temporary file#

Thank you for the amazing tool. I met a problem when I used Ratatosk.
This is my command: Ratatosk correct -v -c 16 -s transcripts.stringtie.fa -l Tam.transcripts.fa -o out_long_reads
I got the file ‘out_long_reads‘, but it said 'Couldn't remove temporary file' .Does it matter?

Hi @Catherine9826,
Thanks for reporting this issue. It does not matter for your output, it is just a warning about whether temporary data written by Ratatosk to disk but not needed anymore were successfully removed. Turns out I programmed this incorrectly and the warning message is printed if the data are successfully removed from disk :) Either way, output data is not affected by this.
I'll keep the issue open to remember to change this for the nest release.
Guillaume

Hi @Catherine9826,
The issue has (at long last) finally been fixed in the latest release. Thank you for your patience.
Guillaume


Error with autocomplete filter box

Hello,
I'm using yadcf datatable.
I have a autocomplete filter box. And this column have some links with html tags. When i try to write something on this box column content is come and html tags also shown.
Is this a bug?
Thanks

Hi,
Thats not a bug, you should use the html_data_selector and also set the column_data_type: "html" , see similar more complicated jsbin. Play with the selector to see what fits you the most, I think it should be html_data_selector: 'span' , in case of trouble post a minimal jsbin smaple

I will try. Thank you.
iPhone'umdan gönderildi
27 Kas 2015 tarihinde 17:22 saatinde, Daniel Reznick<EMAIL_ADDRESS>şunları yazdı:

Hi,
Thats not a bug, you should use the html_data_selector and also set the column_data_type: "html" , see similar more complicated jsbin. Play with the selector to see what fits you the most, I think it should be html_data_selector: 'span' , in case of trouble post a minimal jsbin smaple
—
Reply to this email directly or view it on GitHub.


Use (Val a) as a parameters for condition Equals

I want at first thank you for this amazing library. We are migrating our project technology stack from Python to Haskell and I was very happy to find such cool alternative for Python's Troposphere :)
Today I have encountered the first problem: now Equals expects two Val Bool as parameters: Equals (Val Bool) (Val Bool). Although AWS in their docs just point its as String: docs. Now with two bools I have no idea how to compare for example refs or strings even for basic cases like this from the docs:
"UseProdCondition" : {
   "Fn::Equals": [
      {"Ref": "EnvironmentType"},
      "prod"
   ]
}

Here we have to compare with string "prod" and I have no idea how to play with compiler to stop it complaining.

Hey, thanks for the kind words! :smile:
Indeed, this looks like a total oversight on my part. This should be Val a instead of Val Bool. I've opened a PR at https://github.com/frontrowed/stratosphere/pull/78


[Adblock BUG] Extension adblock.js not found

While running the commnd in windows powershell x86 the extension for adblock.js was not found wherein i copied and pasted the files as said in the marketplace.

can you pls help me with it.
Spotify version: 1.1.98
Spicetify Version: 2.14.1

You don't have the file installed.

I had the file installed and i did a mistake. Instead of pastting only the .js file i had pasted the whole zipped file😅
Now it works


test [nfc]: Cut redundant isNotNull checks before isA

Noticed this pattern here:
https://github.com/zulip/zulip-flutter/pull/363#discussion_r1382298180
This fixes all the existing cases of it.

Thanks! Merged.


Fix warning when deleting empty folders

Closes #21
Closes #16
This was caused by a bug in Unity where an incorrect path was being passed to OnWillCreateAsset. For folders the path for the meta file was given, instead of the actual folder path. Because the meta file is not an asset, its guid would be zero. When deleting the folder, the correct path is given.
I also did a small tidy on AssetProcessor.
Note that I tested this change with @ogxd's refactor branch, and it has no conflicts. (See #22)

Sorry for the (huge) delay, appart from indentation of StringUtility it looks good to me

Sorry for the (huge) delay, appart from indentation of StringUtility it looks good to me

I just merged your suggestion without testing.
btw I've been maintaining my own fork due to your inactivity (so all this stuff has been well tested by our team). Happy to move back to yours if you want to add me as a collaborator, also fine with maintaining my own fork. Pretty sure they'll be at parity after this PR is merged. There is still more work to do here, the most egregious outstanding issue is #20. I'm not actively working on this rn, but vaguely plan to come back to it at some stage.


Error while installing pangu

Hello,
I am writing to you because I am encountering the following error when trying to install pangu.
pip3 --version

pip 23.2.1 from /srv/scratch/testardqu/miniconda3/lib/python3.11/site-packages/pip (python 3.11)

git clone https://github.com/PacificBiosciences/pangu.git
cd pangu
pip install .
Cloning into 'pangu'...
remote: Enumerating objects: 174, done.
remote: Counting objects: 100% (174/174), done.
remote: Compressing objects: 100% (108/108), done.
remote: Total 174 (delta 82), reused 142 (delta 50), pack-reused 0
Receiving objects: 100% (174/174), 20.83 MiB | 20.20 MiB/s, done.
Resolving deltas: 100% (82/82), done.
Processing /home/chu-lyon.fr/testardqu/pangu
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [50 lines of output]
      WARNING setuptools_scm._integration.setuptools pyproject.toml does not contain a tool.setuptools_scm section
      configuration error: `project.dependencies[3]` must be pep508
      DESCRIPTION:
          Project dependency specification according to PEP 508

      GIVEN VALUE:
          "pandas=1.5"

      OFFENDING RULE: 'format'

      DEFINITION:
          {
              "$id": "#/definitions/dependency",
              "title": "Dependency",
              "type": "string",
              "format": "pep508"
          }
      Traceback (most recent call last):
        File "/srv/scratch/testardqu/miniconda3/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/srv/scratch/testardqu/miniconda3/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/srv/scratch/testardqu/miniconda3/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
          self.run_setup()
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 1, in <module>
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 159, in setup
          dist.parse_config_files()
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/dist.py", line 627, in parse_config_files
          pyprojecttoml.apply_configuration(self, filename, ignore_option_errors)
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py", line 66, in apply_configuration
          config = read_configuration(filepath, True, ignore_option_errors, dist)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py", line 127, in read_configuration
          validate(subset, filepath)
        File "/srv/scratch/testardqu/tmp/pip-build-env-cap7ijl2/overlay/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py", line 55, in validate
          raise ValueError(f"{error}\n{summary}") from None
      ValueError: invalid pyproject.toml config: `project.dependencies[3]`.
      configuration error: `project.dependencies[3]` must be pep508
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

I tried aswell to install the latest commit locally, but also pangu v0.2.3, pangu v0.2.2. I've also tried installing it in a Singularity image with the following recipe.
cat Singularity.def
Bootstrap: docker
From: continuumio/miniconda
Stage: spython-base

%labels
tags="Genomics"
%post

################## CONDA TOOLS ######################

conda update -n base conda \
&& conda config --add channels conda-forge \
&& conda config --add channels bioconda \
&& conda install -c bioconda python=3.9 setuptools pip git pysam=0.19.1 pyyaml numpy=1.23.3 pandas=1.5.0 scipy scikit-learn mappy=2.24

git clone https://github.com/PacificBiosciences/pangu.git \
&& cd pangu \
&& pip install .
%runscript
exec /bin/bash "$@"
%startscript
exec /bin/bash "$@"

But same result. Can you help me?
Regards.

Hi, thanks for reporting this.  I am preparing a fix that will address this as well as another bug and should be posting it in the next day or so.  In the mean time, the quick fix is to edit your local pyproject.toml file.  In the dependencies, it should have "pandas==1.5" (two "="), but there is one missing.  The other bug fix should remove the need to restrict pandas to v1.5 and allow for v2 to work.

Hello,
Indeed, it works better with "==" ... Sorry for the inconvenience.
Regards.


Self referential chain

Probably a question more than an issue...
How would you do the self referential declaration as per https://github.com/rm-hull/jasentaa#worked-example-1 ?
Noting that the 'self referentiality' comes from this chain:
search-expr -> search-term -> search-and -> bracketed-expr -> search-expr ...
Here's my experimenting that came across the scenario (noting that I want to take it somewhere else, so this is not the final destination).

(def not-parens (char/regex #"[^\(\)]"))

(def not-parens+
  (-> not-parens
      p/+many ;; NOTE that you can't put a parser that can match empty into a *many later on.
      (p/value clojure.string/join)
      ))

(declare paren-expr) ;; <---- prep

(def paren-expr
  (->
   not-parens+
   (p/alt paren-expr) ;; <------- self referential
   (p/+many)
   (p/between
    (char/is \()
    (char/is \)))
   (p/value (fn wrap [x] (if (coll? x)
                (into [] x)
                x)))))

(def capture-expr (p/*many
                   (p/alt
                    paren-expr
                    (char/is \?)
                    )))

(p/parse capture-expr "(d(fd))e")
;; It's possible to nurse the example in the repl to get the following but won't compile off the bat.
;; => '(["d" ["fd"]])

You should use p/do-parser for delayed declaration of the parser body (the declare is not needed before):
(def paren-expr
  (p/do-parser
    (->
     not-parens+
     (p/alt paren-expr) ;; <------- self referential
     (p/+many)
     (p/between
      (char/is \()
      (char/is \)))
     (p/value (fn wrap [x] (if (coll? x)
                  (into [] x)
                  x))))))


Fix image links in Discovery book

The links have already been fixed in the discovery repository and this PR just updates the CI scripts in the bookshelf repo to ignore the print.html link errors so that the bookshelf version will have the fixes too.
More information about the reason for the CI script change follows:
rust-lang-nursery/mdBook#789 causes
mdbook to generate print.html content with relative URLs that
are still relative to the individual HTML files and doesn't
correct for the fact that print.html isn't in the same folder.
This commit will verify that the relative URLs are correct in all
of the HTML output except for discovery/print.html  I am assuming
that people would like to see the images again in the Discovery
book website as they click through the various chapters, even if
the printable version is still broken.
I have already made the same change to the CI scripts in the
discovery repository along with various link fixes.
Once this PR is merged, an issue should be created to track the
fact that this change should be reverted once mdbook handles
relative links correctly in its generaton of print.html

bors try

The build for this repository is currently failing after the discovery repository was updated to use relative links: https://travis-ci.org/rust-embedded/bookshelf/builds/448915298
This PR will eliminate that build error. The successful Travis run for this PR can be seen here: https://travis-ci.org/rust-embedded/bookshelf/builds/448784057


Applying resource policy after deployment issue in us-west-1

Originally posted by @BaconAndEggs in https://github.com/awslabs/serverless-application-model/issues/514#issuecomment-493161412
My team has a project where we are implementing a private REST API.  We recently considered the benefits and drawbacks available via swagger/openapi import definition model and the definition of our API directly using the AWS::Serverless::Function definition and having SAM render the API gateway via the implicit logic.  We decided to go the AWS::Serverless::Function definition route.
To workaround this issue, we added CI/CD logic to render a resource policy and using an API Gateway create_deployment call.
Since last week (I believe May 9th 2019), in us-west-1, when running new test environment deployments, I found that the workaround of applying a resource policy after deployment is not viable there, because CloudFormation enforces that a resource policy must have a resource policy configured to complete deployment.  I don't see the same behavior in us-east-1 or us-east-2.
As an example, if I use the SAM CLI and init a new SAM project, and add these 2 lines to the default template.yaml Globals section:
  Api:
    EndpointConfiguration: PRIVATE

when I run a deployment of that default template (altered to configure a private API) to us-west-1 the create stack reaches a rollback complete with the initial error event being:
Private REST API doesn't have a resource policy attached to it (Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID: xxxxxxxxxxxxxxxxxxxxxxxxxx)

Thanks much @keetonian.
Friday I checked us-west-2, and I saw the same private API resource policy enforcement and rollback behavior as us-west-1.

In gathering notes, and running test deployments for my support case, it appears that the resource policy enforcement during cloudformation deployment behavior in us-west-1, and us-west-2, has now started being enforced in both us-east-1, and us-east-2.
I'm actually a little surprised that resource policies would be enforced on private API deployments before enforcing the same on public API deployments, because it seems the attack surface of a public API deployment would inherently be greater...

Private APIs don't function with out a resource policy applied to them. this is not being enforced in CloudFormation, but by the API Gateway CreateDeployment API, which is ultimately what is called by SAM and Cloudformation when you're seeing this issue. This deployment is separate from the idea of a stack deployment in CloudFormation and is the process which associates your API resources with the stage.
It seems that to prevent the deployment of unreachable/broken private APIs to a stage, API Gateway has decided to enforce this requirement on their CreateDeployment API.

https://github.com/awslabs/serverless-application-model/issues/514

I'm new to SAM, so after I was failing to figure out a way to get a private API created, with SAM generating the API tree via AWS::Serverless::Function API event mappings, I figured I was just missing something in the syntax, like setting AWS::Serverless::Api.Properties.Policy.  Which led me to #514 .
I commented on #514 , because I think now it is not only not possible to define a resource policy via SAM (outside of API swagger/openapi3 import model), however as of the last week or so, now I believe it is also not possible to deploy a private API at all, without it being defined via the swagger/openapi3 import model.
Again, I'm new to SAM, so it would not surprise me if I was wrong and someone could show an example with the of a template for a private API without requiring an AWS::Serverless::Api.Properties.DefinitionBody.
If I understand #514 correctly, I really like the model @brettstack described in the issue.

We ran into the same problem last week with us-east-2, where we had been able to deploy for months. My CodePipeline Deploy stage was actually a three parter though:
Part 1: Create the Change Set
Part 2: Deploy the Change Set
Part 3: Update the Resource Policy via a custom script and CodeBuild
It was Part 2 that was dying with the same error that @BaconAndEggs saw.
Interestingly, I noticed that we were only seeing it for new resource API endpoints, anything that existed previously was able to deploy just fine. For example, we had an existing /import API that wasn't showing the error, but last week's new guy, /export was.
I was able to work around this by changing the EndpointConfiguration setting in my template yaml to REGIONAL, do my deployment, switch it back to PRIVATE and then deploying again. Obviously this is a terrible workaround, but I figured I'd post it in case it helps with fixing this issue.

We are prioritizing #514 so there is a better workaround for this issue.

I'm not sure if this is the bug I'm also affected by, but it feels like it. I successfully deployed a Lambda@Edge function near the end of April to (as required) us-east-1, and more recently tried again and received:
An error occurred: ApiGatewayDeployment_____ - Private REST API doesn't have a resource policy attached to it (Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID: X-X-X-X-X).
I'm not using SAM directly, but serverless and silvermine/serverless-plugin-cloudfront-lambda-edge, is there a workaround I should be applying here? Is this the same issue?

@mike-hart this is the same issue. A private REST api requires a resource policy now after a recent APIGW update.

The support for adding api gateway resource policies was shipped with Release V1.14.0.


Visualizations Feedback!

Below are some thoughts about the visualizations in this report and some suggestions for improvement, and notes when things are done well. You should implement these in milestone4

[x] It would really have helped if you had a caption and a figure/table number for each plot. That way you can easily reference it in your text, and it's easier for readers to find

[x] Figure 1:

[x] Nice! This is a very powerful visualization that shows the reader exactly what you want to show

[x] You should round all values to 2 sig figs? will probably make it less messy and easier to read

[x] Consider setting diagonal values on your correlation map to be 0 or nan; those will really stand out otherwise.

[x] Ideally, you only want to show half the correlation map as the other half is redundant (see example here) - let me know if you figure out how to do this in Altair

[x] Figure 2:

[x] Definitely switch x and y so categorical axes are on the y-axis and it's easier to read

[x] You should rotate all x-axis labels so they're oriented correctly: alt.X('Var:N', axis=alt.Axis(labelAngle=0))

[x] Consider sorting the countries by your metric like here

[x] Figure 3:

[x] Looks great! nice work

[x] Figure 4:

[x] Defend the choice (not in your report, I mean in this issue) to connect the lines together; is this correct for your context?

[x] Consider removing the gray background with theme_bw()!

[x] Tables

[x] Too many sig figs, there's no need to show that many, it hurts readability and interpretability

[x] remove the top and right axes in your matplotlib (I think) plot. See here how to do it

[x] This is not something standard, but I personally would have created a dictionary with the column names as keys and a more human readable name as a value, then when plotting use the human readable names. This is probably too much work to do at this point, just something to keep in mind in the future. The feature names aren't super intuitive so you have to hunt around in the text for their interpretation. Another way is to add a table in the appendix with the column name and its corresponding human readable interpretation

[x] Overall the report looks very polished and clean! Great work! Excellent work with your labels, titles, and plot choices! For every plot I was immediately able to understand what you were trying to convey.

We have made most of the changes suggested here.
First we added figure captions to all plots and tables.
For fig1, we now keep only 1 sig fig, and set diagonal values to 0. Unfortunately, the redundant repeated correlation scores was not addressed due to time constraints.
For fig2, we put the categorical feature on the y-axis. We did not get to sorting the values by a specific metric.
For fig4, we changed to a scatter plot so that we don't have meaningless connected lines.
For the table, we reduced the number of decimals to 3.
For fig 5, we removed the top and right axes.
We also added a reference table in the appendix explaining each feature.
Thanks for the feedback! It has definitely helped improve the quality of our report.

Good work ! Nice work prioritizing the important ones over the extra "nice-to-haves"

FYI for future reference, here's a full code chunk to get rid of the redundant correlations (note also the .round(2) function that rounds values to 2 digits
## Section 2: Lower triangle of correlation plot with no diagonals

# This bit of wrangling creates a new dataframe with only half the elements
l1 = sorted(df_iris.corr().columns.to_list()) # sorting is needed to make sure the final correlation maps looks like an upper or lower triangle
l2 = l1.copy()
rows = []

for e1 in l1:
    for e2 in l2:
        rows.append([e1,e2, df_iris.corr().loc[e1,e2]])
    l2.remove(e1)

# Create dataframe from list of rows
newdf = pd.DataFrame(rows,columns=['Var1','Var2','Corr'])

# If you want to remove the diagonals
newdf = newdf[newdf['Var1']!=newdf['Var2']]

# Create the heatmap first
heatmap = alt.Chart(newdf).mark_rect(
).encode(
    alt.X('Var1:O', title = ''),
    alt.Y('Var2:O', title = '', axis=alt.Axis(labelAngle=0)),
     alt.Color('Corr:Q',
                scale=alt.Scale(scheme='viridis'))
)

# Add the correlation values as a text mark
text = heatmap.mark_text(baseline='middle', fontSize=20).encode(
    text=alt.Text('Corr:Q', format='.2'),
    color=alt.condition(
        alt.datum['Corr'] >= 0.95,
        alt.value('black'),
        alt.value('white')
    )
)

# Set the height, width, title and other properties
corrMatrix_chart = (heatmap + text).properties(
    width = 400,
    height = 400,
    title = "Iris variables correlation matrix",
)
corrMatrix_chart.configure_axis(
    labelFontSize=18,
    titleFontSize=24,
).configure_title(
    fontSize=24,
    anchor='start',
).configure_legend(
    labelFontSize=20,
    titleFontSize=20)


Add new variable

When creating сonversation, it would be nice to define the {action} variable. To determine what action was taken with the content when creating the сonversation

Should be fairly easy to implement because the required data is already set via XF\Service\User\Warn::withContentAction($action, array $options = []);

I have made a PR but I'm not sure how the variable will be used. Maybe create new phrases for common actions (public and delete)?

yeah, phrase groups is my suggestion. Something like warning_action.public or something