Specifying bytecode's ABI

When using the -c option, I'm guessing Mythril doesn't know which public functions can be called on the contract.
Is there an option to specify a JSON ABI to help Mythril find the functions to analyze?

Hi @franklinsch, it does identify public functions automatically. This happens implicitly because only public functions have entries in the function hash table.
At the moment there are no plans to add ABI support to the myth utility. We're planning to create a separate tool meant for developers that will have better support for use cases where you have access to the source code and/or ABI.

I haven't found any documentation on this either. But the bytecode of a compiled contract starts with a jump table (sequence of JUMPI instructions) that compares the first 4 bytes of the calldata with each function signature hash. external and public functions are included in that table, but internal and private ones aren't -> thus they cannot be called.

Ah, that's quite neat. This is specific to Solidity contracts, though. I wanted to use Mythril for Flint (https://github.com/franklinsch/flint) contracts, for which the bytecode is laid out differently.

Interesting! In principle Mythril should follow all executable code paths no matter what language was used, but it wouldn't be able to recognize the start of a function unless there is a Solidity-type jump table.
Do you have some example bytecode?

In this gist, I've uploaded a Flint contract, its IR form as inline assembly in a Solidity file, and the final binary.

Hmm the CFG for Mythril generates for that bytecode doesn't look right.
$ myth -g graph.html --max-depth 128 -c "[bytecode]"

Is this the contract creation bytecode or the runtime bytecode (the one that ends up in the contract account)?
Also, can you explain briefly how function calls are resolved in Flint?

This is the contract creation bytecode. (running solc --bin on the Solidity IR file).
Function calls are also resolved by looking at the first four bytes of Keccak hash (like Solidity). This is performed in the fallback function of a Solidity function (see line 213, which is the entry point of all function calls)

Closing issue, as it is over a year old and is stale. Feel free to open a new issue if specifying the ABI for a contract will provide a significant improvement.


Error Segmentation fault (core dumped)

Please first make sure you have looked at:

Documentation: https://github.com/mkleehammer/pyodbc/wiki
Other issues

Environment
To diagnose, we usually need to know the following, including version numbers.  On Windows, be
sure to specify 32-bit Python or 64-bit:

Python: 2.7.12
pyodbc: latest
OS: ubuntu 16.04
DB: Oracle

Issue
Often it is easiest to describe your issue as "expected behavior" and "observed behavior".
Hi, I followed the wiki in order to check the connection to a remote oracle db.
here are my files:
odbcinst.ini
[Oracle]
Description=ODBC for Oracle
Driver=/usr/lib/oracle/11.2/client64/lib/libsqora.so.11.1
UsageCount=1
FileUsage=1

odbc.ini
[ejabberd]
Driver = Oracle
DSN = Oracle
ServerName =  //x.x.x.x:1521/DB_SID
UserID = admin
Password = admin

I tried to check the connection with:
python -c "import pyodbc; print(pyodbc.connect('DRIVER=Oracle;DBQ=//x.x.x.x:1521/DB_SID;UID=admin;PWD=admin'))"

but I received first:
Segmentation fault (core dumped)
than
<pyodbc.Connection object at 0x7f94cbfdd2e8>.
What is wrong? please help. Thanks

Could you run python with gdb and give a stack trace (bt) when it crashes?

Closed due to inactivity. Feel free to re-open with current information if necessary.


[ARM] Fix #12199 Workround for template exception handling

#12199
Error is:
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/arm.py", line 103, in handle_template_based_exception
    raise CLIError(ex.inner_exception.error.message)
AttributeError: 'str' object has no attribute 'message'

Signed-off-by: Nye T. Liu<EMAIL_ADDRESS>

Only reasonable workaround is here, since getting MS to not use smart quotes is likely impossible:
https://github.com/Azure/azure-cli/issues/12199#issuecomment-588350758


Fixed the p5.dom library link

Fixes #757
Before Changes:

After Changes:

@Rahulm2310 your PR fixes the issue, but i am not sure why we are getting a conflicting file for this PR, any idea why?


Rename module core -> presentation

The functionality of the core module covers all logic related solely to the presentation layer.
It needs to be renamed accordingly due to the possibility of adding other shared modules specific to new configurable layers.

fixed in v0.2.0


Support overriding default memory functions

When developing Nokolexbor, I needed to use ruby-specific memory functions ruby_xmalloc, ruby_xrealloc, ruby_xcalloc and ruby_xfree instead of malloc, realloc, calloc and free to make it work well with ruby GC behavior.
A setup function similar to xmlMemSetup will be handy so that users can override default memory functions.
lexbor_memory_setup(ruby_xmalloc, ruby_xrealloc, ruby_xcalloc, ruby_xfree);

Not sure if naming corresponds to Lexbor conventions.

A side question:
Since memory.c are identical in posix/lexbor/core and windows_nt/lexbor/core, can we move it out?

Hi @zyc9012
Thanks for the parch!
I left a couple of comments, please take a look.

@lexborisov Thanks, I've updated the namings.

@zyc9012
Awesome, thanks for the patch!


ApiException.Content is always null when a response type is defined.

ApiException.Content is always null when calling an endpoint that returns a Task<Response> but works fine when the endpoint has no return type i.e. Task.
This is my API Interface:
public interface IUserApi
{
	[Post("/api/user")]
	Task<CreateUserResponse> CreateUser([Body] CreateUserRequest request);

	[Post("/api/user/{userId}/_change-email")]
	Task ChangeEmail(Guid userId, [Body] ChangeEmailRequest request);
}

This is my error response class:
public class ErrorResponse
{
    public string[] Errors { get;set; }
}

This is how I am calling the API:
try
{
    var createUserResponse = api.CreateUser(user);
}
catch(ApiException ex)
{
   var error = ex.GetContentAs<ErrorResponse>();
   // error is null
}

ApiException.Content has the correct content when I call IUserApi.ChangeEmail however when I call IUserApi.CreateUser it is always null even though the server is returning content.
I have traced it down to this line here https://github.com/paulcbetts/refit/blob/8e602ef25aedf3d38b4dddf0bd9d9fbb7d2f82bf/Refit/RequestBuilderImplementation.cs#L357. Because HttpCompletionOption.ResponseHeadersRead is passed to SendAsync the content is not read by the time the ApiException.Create method checks if it is null https://github.com/paulcbetts/refit/blob/master/Refit/RestService.cs#L112 so it is never read. Removing the HttpCompletionOption.ResponseHeadersRead parameter resolves the issue however that would break any code that tries to use the cancellation token to prematurely stop the request.
I unfortunately do not have anymore time to investigate the issue at the moment, I may be able to find some time in the coming days or if someone else has a good fix for it that would be great.

Did you ever find a way around this or end up working on it?

Unfortunately not, I did not have enough time to look into it further at the time so we gave up on using Refit and went back to our original RestSharp implementation and I have not found another use for Refit since then. I might look into it again soon if I find time.


add limited support for

Currently only triangles and lines are supported.  However, it should be possible to support polylist primitives that happen to be all triangles, i.e. the <vcount> data is all 3's.  Such is the case in at least one model I found online.

Added in commit 3feef72bf4337ede4c9331c31cd96dadbc620148


Add support for metadata change events and APIs

Eventing
State of metadata in OpenMetadata changes due to user activity, such as updating the description of a dataset, changing ownership, or adding new tags. Metadata also changes due to activities at the metadata sources, such as a new dataset was created, a dataset was deleted, or the schema of a dataset is modified, which is ingested using Ingestion bot. When the state of metadata changes, an event is produced. These events can be used to build apps and bots that respond to the change from activities.
An event must provide the following information in order write bots/applications around it:

The entity that changed
Type of change - a new entity is created, an entity is deleted, or an entity is modified.
User/bot that made the change.
Activity that caused the change as a result of API operation on an entity.
The time when the change occurred
Value of entity before and after the change. A way to easily determine the fields of the entity (attributes and relationships) that changed.

Changes/operations can be categorized into two broad categories:

Operations that change the version of an entity - Some API operations change the metadata version of an entity, such as updating an entity description, adding new tags to an entity, some changes as a schema for a table was updated or a query was updated for a report, etc.
Operations that don’t change the version of an entity - Some API operations change the metadata associated with an entity that are not core attributes of an entity. Such changes do not result in a version change, such as an entity was followed/unfollowed, usage details or data profiler information for an entity is updated.

Additionally, a change event might apply to a single entity, such as description of a table changed or multiple entities, such as a user followed a table, where the event is attributed to two entities - table and user.
AuditLog vs. Change Events
AuditLog logs the details of an operation - what operation was performed, who performed it, when was it performed, what was the result of an operation (success or failure). Audit logs capture operations, whether they resulted in a change or not. Audit logs also capture other operations, such as user logged in and logged out that are relevant for auditing.
Change events are the result of successful operation and do not track failed operations as they don’t result in any change. Even a successful operation that did not result in a change is not relevant for change events. For example a PUT operation that made no change is still relevant to AuditLog but may not result in any change events).
Change event schema
Eventing functionality is heavily based on the entity versioning work that was done earlier in #736. Changes made to an entity during PUT, PATCH are captured as changeDescription from entityHistory.json.
Following changes will be captured:
All events will include the following common information - user who made the change, entity type (table, dashboard etc.), entityId (UUID of the entity), current version of the entity after the change, pervious version of the entity before the change, and change details.

entityCreated - this event includes the entity that was created in the event itself. This can be used by applications getting the events to initialize the state about an entity from the change event itself.
entityUpdated - these events captures details of what fields were added and the new value of the field, what fields were updated with old and new value of the field, and finally what fields were deleted and old value of the field.
entityDeleted - this event just informations the the entity is deleted (with all the common event details).

changeEvent schema is as follows:
{
  "$id": "https://open-metadata.org/schema/type/auditLog.json",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "ChangeEvent",
  "description": "This schema defines the change event type to capture the changes to entities. Entities change due to user activity, such as updating description of a dataset, changing ownership, or adding new tags. Entity also changes due to activities at the metadata sources, such as a new dataset was created, a datasets was deleted, or schema of a dataset is modified. When state of entity changes, an event is produced. These events can be used to build apps and bots that respond to the change from activities.",
  "type": "object",
  "javaType": "org.openmetadata.catalog.type.ChangeEvent",

  "definitions": {
    "eventType" :{
      "javaType": "org.openmetadata.catalog.type.EventType",
      "description": "Type of event",
      "type": "string",
      "enum": [
        "entityCreated",
        "entityUpdated",
        "entityDeleted"
      ]
    },
    "eventFilter": {
      "type": "object",
      "javaType": "org.openmetadata.catalog.type.EventFilter",
      "properties": {
        "eventType": {
          "description": "Event type that is being requested.",
          "$ref": "#/definitions/eventType"
        },
        "entities": {
          "description": "Entities for which the events are needed. Example - `table`, `topic`, etc. **When not set, events for all the entities will be provided.**",
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "required": ["eventType"]
    }
  },
  "properties" : {
    "eventType" : {
      "$ref": "#/definitions/eventType"
    },
    "entityType" : {
      "description": "Entity type that changed. Use the schema of this entity to process the entity attribute.",
      "type": "string"
    },
    "entityId": {
      "description": "Identifier of entity that was modified by the operation.",
      "$ref": "basic.json#/definitions/uuid"
    },
    "previousVersion" : {
      "description" : "Version of the entity before this change. Note that not all changes result in entity version change. When entity version is not changed, `previousVersion` is same as `currentVersion`",
      "$ref" : "entityHistory.json#/definitions/entityVersion"
    },
    "currentVersion" : {
      "description" : "Current version of the entity after this change. Note that not all changes result in entity version change. When entity version is not changed, `previousVersion` is same as `currentVersion`",
      "$ref" : "entityHistory.json#/definitions/entityVersion"
    },
    "userName": {
      "description": "Name of the user whose activity resulted in the change.",
      "type": "string"
    },
    "dateTime": {
      "description": "Date and time when the change was made.",
      "$ref": "basic.json#/definitions/dateTime"
    },
    "changeDescription" : {
      "description": "For `eventType` `entityUpdated` this field captures details about what fields were added/updated/deleted. For `eventType` `entityCreated` or `entityDeleted` this field is null.",
      "$ref" : "entityHistory.json#/definitions/changeDescription"
    },
    "entity" : {
      "description": "For `eventType` `entityCreated`, this field captures JSON coded string of the entity using the schema corresponding to `entityType`"
    }
  },
  "required": ["eventType", "entityType", "entityId", "dateTime"],
  "additionalProperties": false
}

Generating change events

POST API requests - POST requests create an entity.  The entityCreated event is generated with entity JSON as the payload.
PUT API requests - PUT requests can create an entity when it does not exists or update an existing entity. When entity is created, entityCreated event is generated as done in POST. When an entity is updated, entityUpdated event is generated with changeDescription that includes field change information.
PATCH API requests - PATCH updates an existing entity. As with PUT requests during updated, entityUpdated event is generated during PATCH.
DELETE API requests - DELETE deletes an entity. The event entityDeleted is generated that identify entityType, and entityID, and entityVersion.

Storing change events
Change events are stored so that other applications can pull the change events to get the changes and react to them. They events are stored in the following table:
CREATE TABLE IF NOT EXISTS change_event (
    eventType VARCHAR(36) GENERATED ALWAYS AS (json ->> '$.eventType') NOT NULL,
    entityType VARCHAR(36) GENERATED ALWAYS AS (json ->> '$.entityType') NOT NULL,
    userName VARCHAR(256) GENERATED ALWAYS AS (json ->> '$.userName') NOT NULL,
    dateTime TIMESTAMP GENERATED ALWAYS AS (TIMESTAMP(STR_TO_DATE(json ->> '$.dateTime', '%Y-%m-%dT%T.%fZ'))) NOT NULL,
    json JSON NOT NULL,
    INDEX (dateTime),
    INDEX (eventType),
    INDEX (entityType)
);

APIs are change events
Following API is supported for pulling change events:
GET .../events?entityCreated=<entities>&entitiesModified=<entities>&entitiesDeleted=<entities>&date=<eventTime to get change events since>

An application can use the above API to get specific eventTypes for the entities they are interested in and catch up by pulling the events since they left off.
Future work

Add support for push based events where an application can register a webhook using event subscription api to be notified of change events.
Use change events to create notification and alerts to the users using feeds API.
Add support for Kafka sink for change events for deployments that need such a setup.

Issue breakdown:

GET .../events?entityCreated=<entities>&entitiesModified=<entities>&entitiesDeleted=<entities>&date=<eventTime to get change events since>

Would it be better to support fromTimestamp and toTimestamp (instead of since date), with toTimestamp being optional?

Marking this issue as closed


No menu for https://python.plainenglish.io

There is no menu like "Open in google cache" for URL https://python.plainenglish.io/automated-project-documentation-python-f880f19ad13b

Actually , there is a menu as expectation after a while.
Close issue for no more question


Pandoc based converters

This re-enables several converters that are based on Pandoc:

jats
docx
odt
latex

There is still some legacy code in src/pandoc-bilge.js and src/pandoc which we should either delete or make use of before merging this PR.
There are also plenty of TODOs that could be addressed or removed and turned into issues.
The main piece of functionality to be renabled is the handling of Table nodes.
You can test conversion like this:
npx ts-node --files src/cli.ts ./test.md ./test.docx

@alex-ketch See the jats converter for an example of how to specify and put a template for docx

Codecov Report

Merging #56 into master will decrease coverage by 0.36%.
The diff coverage is 89.18%.

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
- Coverage   90.53%   90.17%   -0.37%
==========================================
  Files          13       20       +7
  Lines        1363     1801     +438
  Branches      373      452      +79
==========================================
+ Hits         1234     1624     +390
- Misses        123      169      +46
- Partials        6        8       +2

Impacted Files
Coverage Δ

src/pandoc-types.ts
100% <100%> (ø)

src/rpng.ts
97.05% <100%> (-0.05%)
:arrow_down:

src/pandoc-binary.js
100% <100%> (ø)

tests/fixtures/article-simple.ts
100% <100%> (ø)

src/boot.ts
77.27% <100%> (ø)

src/jats.ts
100% <100%> (ø)

src/odt.ts
100% <100%> (ø)

src/docx.ts
100% <100%> (ø)

src/index.ts
92.7% <33.33%> (-7.3%)
:arrow_down:

src/pandoc.ts
85.15% <85.15%> (ø)

... and 8 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 2110242...90586a9. Read the comment docs.

:tada: This PR is included in version 0.33.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


python diff_inference.py get OutOfMemoryError

I first generated the pictures using the diff_inference.py
python diff_inference.py  -nb 4000 --dataset laion --capstyle instancelevel_blip --rand_augs rand_numb_add
while I met
File "/home/anaconda3/envs/diffrep/lib/python3.9/site-packages/diffusers/models/cross_attention.py", line 314, in call
attention_probs = attn.get_attention_scores(query, key, attention_mask)
File "/home/anaconda3/envs/diffrep/lib/python3.9/site-packages/diffusers/models/cross_attention.py", line 253, in get_attention_scores
attention_probs = attention_scores.softmax(dim=-1)
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 3.16 GiB (GPU 0; 15.46 GiB total capacity; 11.31 GiB already allocated; 2.48 GiB free; 11.39 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
while I still have a lot of gpu, thanks for your suggestion

Is it possible to do a single image inference of stabilityai/stable-diffusion-2-1 model on your GPU?
Most of my experiments are conducted on A5000/A6000.
For the case you are testing, it is a simple SD 2.1 inference with modified prompts, you can perhaps change some hyperparameters here to see if the code runs.

Thanks for your suggestion, while I set im_batch=1, num_inference_steps=5, nbatches set 4, still have this error


perf: prioritize the main bundle over <link rel=preload>s

Description
After https://github.com/appsmithorg/appsmith/pull/21933, the main bundle started to compete for bandwidth with the preloaded chunks. On pages without the preloads, the bundle would take ~2s to load (on 4G) (request no. 3):

whereas on pages with the chunks, it will take ~3s (request no. 13):

This PR fixes that by:

removing the defer attribute, which bumps the main bundle’s priority from Low to High (reference: https://addyosmani.com/blog/script-priorities/)
and setting fetchpriority="low" on the preload chunks

This changes the waterfall to look like this instead:

Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing
How Has This Been Tested?

[x] Manual – tested different attributes in WebPageTest + implemented them locally without perf testing

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

/ok-to-test

Alright, so to merge this, we need to:

Merge https://github.com/appsmithorg/design-system/pull/480
Publish the new version of design-system-old and update it in this branch
Re-run the tests (should pass once the new design-system-old is used)

@iamakulov , We are no longer using design-system-old.
@tanvibhakta , @albinAppsmith can you work with Ivan to close this.

/ok-to-test

/build-deploy-preview

/ok-to-test

/build-deploy-preview

Tested this PR.
No tooltips are appearing for any of the Editable text fields or for Filepicker v2. Please note that we do not see tooltips in release as well for these components.
https://www.loom.com/share/198e9e93a3f94c1c9d836865cfe3daa3

As discussed with @tanvibhakta this PR cannot be tested because:

Tooltips are not visible for Editable text & FilePicker v2
We are not able to see the title bar & hence the tooltips on page name cannot be tested.

(Should I try adding tooltips to some components just for the test purposes?)

We are not able to see the title bar

Wait hmmm no, this is what’s the actual issue with this PR (and also a thing that’s failing Cypress tests). This is weird, looking into this now.

Alright, fixed the header not being rendered (very silly omission; https://github.com/appsmithorg/appsmith/pull/23556/commits/c22ac385fbc051016ccac4efa6c98fb7984843a3) and checked that there are no more top-level document. calls in the repo.
The tooptip seems to work:

/ok-to-test

/ok-to-test

/ok-to-test

I’m extremely puzzled why this CI in this branch suddenly caught much more ESLint errors than in release, despite release also having these errors. In any case, fixing these errors.

 Not sure why exactly; might be the automatic yarn dedupe, might be something else?

Oh well. So due to https://github.com/palantir/blueprint/issues/3248, removing the defer attribute from the <script> (while keeping it in <head>) means popovers won’t render.
The root issue is here:
https://github.com/palantir/blueprint/blob/3dcbb0113f7f58637dec57a85c445011d51bafb6/packages/core/src/components/portal/portal.tsx#L59
This code gets executed when the bundle runs for the first time – and sets container to null, as document.body is not defined yet at that moment.
Sounds like we’ll have to figure out a different approach to prioritize the bundle without making it render-blocking.

Superseded by https://github.com/appsmithorg/appsmith/pull/24374!


WIP Fix broken time-step ellision

Closes #681

What will be next steps? I guess I should write some haskell code which going to be compiled into js via ghcjs and then evaluated in nodejs as test?

Thinking about how I could patch Driver.hs to use with ghcjs.
I think need

get some code like https://code.world/haskell#PPUTRWUDaX3tF9KMQYGTS-w
write different Driver.hs primitives, which allow success to state per step besides execution. something like runNStepsTest :: Int -> world -> (Event -> World -> World) -> IO [World]
make function which collect results for test. collect :: [World] -> Either SuccessMsg ErrorMsg
compile this with ghcjs
run with nodejs as HUnit tests.

Just wanted to point out that you can run unit tests with GHCJS without that wrapper.  The unit test should be the client code, and you can do this:
cd codeworld-api
cabal configure --ghcjs --enable-tests
cabal test

You'll want to write your tests directly against codeworld-api (that is, in the style of http://code.world/haskell), but that should be fine.

I just merged a couple commits to get this started. It's a lot harder than I thought it would be.  https://github.com/google/codeworld/commit/193b9aef09a8db59b923105ba377fd1a3ffc1e88 is a good pattern for the unit test, and https://github.com/google/codeworld/commit/700645a19b1b1ed75eb99d03f84f59eba7190dd4 gets some of the way toward abstracting over the underlying graphics environment.  The latter change was way harder than I though because unfortunately blank-canvas lacks a built-in MonadIO instance, so I had to hack around that to get a functioning one.

From your email
"Unfortunately, I didn't get far enough to take advantage of this work by simplifying the CodeWorld.Driver module. There's still a lot to be done before that's possible.  We need some abstraction over how we obtain the original canvas, and how we deliver events."

What means "original" canvas? For browser obtaining canvas is getElementById. For nodejs it should be like some dummy element which swallow all commands to it. Should I use conditions with #ifdef as described here https://guide.aelve.com/haskell/cpp-vww0qd72 to tell in which environment execution are?

What is delivering of event? In snippet from original issue generated js application spawns TimePassing events from browser. Also KeyPress, etc. Event handler describes how to react to event, but event generated by "user" as I see here https://github.com/google/codeworld/blob/master/codeworld-api/src/CodeWorld/Event.hs#L58 . Even TimePassing is generating by "user". Is " some abstraction over ... how we deliver events" is about possibility to mock events with stub canvas in tests? E.g. generate fake KeyPress event in tests?

Yes, in both cases, I'm referring to the top-level code that handles the event loop, listeners, etc.  This is the last bit of code that needs work so that it can be tested with a stubbed graphics implementation.  Unfortunately, this is where the logic you need to test lives.
It's difficult to explain precisely what needs to be done here without just doing it.  I'm figuring it out myself as I go.  So if you think you understand how to make this work, go for it.  Otherwise, I cam happy to just merge the StubCanvasM implementation you have, and work on the unit test myself.  I don't think I'm too far off, really.  Once there's a failing test, it could be much easier for you to dig into why it's failing and work on a solution.
If you think you can make progress on your own, though, then go for it!

Ok :)

I meant I want to continue fix this. Issue not resolved.

Sorry, I didn't mean to close the issue.  Just to merge the stub so that I can work on building a failing unit test to demonstrate the issue.

Issue is reopened.


Suggestions for pipes

Now the new pipes are released, I have a couple of suggestions for QoL.
Vertical pipes. Although gizmo rotation mods appear to take care of this.
1 meter pipe, to allow more compact builds.
Pipe filter, to allow routing of multiple item types through the pipe network.

Everything besides pipe filtering has been implemented in the last few updates but that's still planned. It will probably use the same filtering as the hoppers, it's kinda a pain pipes can't be filtered at the moment.

This can be closed now, pipes behave like hoppers in 2.0.0


Thomas's TODOs

[ ] fix the arrow when nav bar collpases
[x] fix the expand function in faq section
[x] mouse click to hover over?
[ ] marketing
[x] create IG account
[ ] Add About
[ ] Add Vision

Combining issues and todos, closing this comment.


update(Thumbnail): Thumb without external libraries

What this PR does 📖
1. Updated the code, to just use crates and not necessary more external libraries to upload thumbnails from videos and pdf files
a. External libraries can let app with bigger size and can affect performance
b. Difference will be more on video thumbs, a little bit different from previous version

Which issue(s) this PR fixes 🔨

Resolve #488

Special notes for reviewers 🗒
Additional comments 🎤

Is there any reason not to use image crate for thumbnails for media files?

Is there any reason not to use image crate for thumbnails for media files?

When you say media, is images and video files?

That is correct. Looking at the dependency used, it looks like they also use image for producing thumbnails too (would have to double check though)

With the release coming up we are going to close this, and come back to it after we make the public builds.


TEP-0011: Add StdoutConfig and StderrConfig to steps.

Changes
Implements Option 1 of TEP-0011
Resurrects #3103
Closes #2925
Signed-off-by: Brad Beck<EMAIL_ADDRESS>Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Docs included if any changes are user facing
[x] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in
(if there are no user facing changes, use release note "NONE")

Release Notes
Users can specify `stdoutConfig` and `stderrConfig` in steps to capture steps' stdout and stderr to local files. This feature can be used to capture stdout and stderr into task results.

/ok-to-test

/test pull-tekton-pipeline-alpha-integration-tests

LGTM, the only question I have is wether we want to add this behind a feature-flag or not — as it is additive only, I think it is fine to add it directly, but maybe we want to hide it behind the alpha feature flag.
@bradbeck 👍🏼

@vdemeester Thanks for the feedback. Working on understanding what it takes to put this behind the alpha feature flag.

/kind feature

Close/re-open to re-trigger CI (seems to be super flaky today :/)

/retest

Hey @bradbeck, I have started reviewing this PR. I ran the sample taskRun from the example which exited with success but noticing error in the entrypoint initialization:
 kubectl get tr
NAME             SUCCEEDED   REASON      STARTTIME   COMPLETIONTIME
step-stream-tr   True        Succeeded   80s         64s

kubectl logs pod/step-stream-tr-pod --all-containers
digest:
error: 2022/07/08 18:45:29 Entrypoint initialization
2022/07/08 18:45:30 Decoded script /tekton/scripts/script-1-smv9r
sha256:b3abe4255706618c550e8db5ec0875328333a14dbf663e6f1e2b6875f45521e5

The controller logs (in case if they are helpful):
{"level":"info","ts":"2022-07-08T18:45:23.148Z","logger":"tekton-pipelines-controller.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TaskRun\", Namespace:\"default\", Name:\"step-stream-tr\", UID:\"7e7f595f-793c-44ea-93af-684483e48511\", APIVersion:\"tekton.dev/v1beta1\", ResourceVersion:\"300068\", FieldPath:\"\"}): type: 'Normal' reason: 'Started' ","commit":"df2da84"}
{"level":"info","ts":"2022-07-08T18:45:29.136Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 29, 136094579, time.Local)}, Reason:\"Pending\", Message:\"Pending\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"b13a265a-cffe-4d0b-a5bd-c5eb2ce965e9","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:29.136Z","logger":"tekton-pipelines-controller.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TaskRun\", Namespace:\"default\", Name:\"step-stream-tr\", UID:\"7e7f595f-793c-44ea-93af-684483e48511\", APIVersion:\"tekton.dev/v1beta1\", ResourceVersion:\"300068\", FieldPath:\"\"}): type: 'Normal' reason: 'Pending' Pending","commit":"df2da84"}
{"level":"info","ts":"2022-07-08T18:45:29.173Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 29, 173500781, time.Local)}, Reason:\"Pending\", Message:\"pod status \\\"Initialized\\\":\\\"False\\\"; message: \\\"containers with incomplete status: [prepare place-scripts]\\\"\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"e055ed46-f114-477f-9108-aeda4a54f998","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:29.173Z","logger":"tekton-pipelines-controller.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TaskRun\", Namespace:\"default\", Name:\"step-stream-tr\", UID:\"7e7f595f-793c-44ea-93af-684483e48511\", APIVersion:\"tekton.dev/v1beta1\", ResourceVersion:\"300083\", FieldPath:\"\"}): type: 'Normal' reason: 'Pending' pod status \"Initialized\":\"False\"; message: \"containers with incomplete status: [prepare place-scripts]\"","commit":"df2da84"}
{"level":"info","ts":"2022-07-08T18:45:29.182Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 29, 181995502, time.Local)}, Reason:\"Pending\", Message:\"pod status \\\"Initialized\\\":\\\"False\\\"; message: \\\"containers with incomplete status: [prepare place-scripts]\\\"\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"a4c3a972-b4eb-4ff9-84ab-2aeec599284d","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:30.737Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 30, 737238732, time.Local)}, Reason:\"Pending\", Message:\"pod status \\\"Initialized\\\":\\\"False\\\"; message: \\\"containers with incomplete status: [place-scripts]\\\"\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"467cdc99-ca87-4d68-a6ec-0ef63d3578e9","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:30.737Z","logger":"tekton-pipelines-controller.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TaskRun\", Namespace:\"default\", Name:\"step-stream-tr\", UID:\"7e7f595f-793c-44ea-93af-684483e48511\", APIVersion:\"tekton.dev/v1beta1\", ResourceVersion:\"300085\", FieldPath:\"\"}): type: 'Normal' reason: 'Pending' pod status \"Initialized\":\"False\"; message: \"containers with incomplete status: [place-scripts]\"","commit":"df2da84"}
{"level":"info","ts":"2022-07-08T18:45:30.746Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 30, 746915004, time.Local)}, Reason:\"Pending\", Message:\"pod status \\\"Initialized\\\":\\\"False\\\"; message: \\\"containers with incomplete status: [place-scripts]\\\"\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"ba1c11b9-41d7-461c-ad70-9374a01e8a37","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:31.756Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 31, 756021274, time.Local)}, Reason:\"Pending\", Message:\"pod status \\\"Ready\\\":\\\"False\\\"; message: \\\"containers with unready status: [step-digest-step step-log-results]\\\"\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"39af9044-9c78-49a5-90fc-ef63dd869e4a","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:31.756Z","logger":"tekton-pipelines-controller.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TaskRun\", Namespace:\"default\", Name:\"step-stream-tr\", UID:\"7e7f595f-793c-44ea-93af-684483e48511\", APIVersion:\"tekton.dev/v1beta1\", ResourceVersion:\"300093\", FieldPath:\"\"}): type: 'Normal' reason: 'Pending' pod status \"Ready\":\"False\"; message: \"containers with unready status: [step-digest-step step-log-results]\"","commit":"df2da84"}
{"level":"info","ts":"2022-07-08T18:45:31.768Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 31, 768109633, time.Local)}, Reason:\"Pending\", Message:\"pod status \\\"Ready\\\":\\\"False\\\"; message: \\\"containers with unready status: [step-digest-step step-log-results]\\\"\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"90099006-dfa4-4ed0-b44c-609ca1ff474b","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:36.845Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 36, 845126854, time.Local)}, Reason:\"Running\", Message:\"Not all Steps in the Task have finished executing\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"1338e08e-b2ef-4132-ab29-49214b322ed8","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:36.845Z","logger":"tekton-pipelines-controller.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TaskRun\", Namespace:\"default\", Name:\"step-stream-tr\", UID:\"7e7f595f-793c-44ea-93af-684483e48511\", APIVersion:\"tekton.dev/v1beta1\", ResourceVersion:\"300100\", FieldPath:\"\"}): type: 'Normal' reason: 'Running' Not all Steps in the Task have finished executing","commit":"df2da84"}
{"level":"info","ts":"2022-07-08T18:45:36.853Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"Unknown\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 36, 0, time.Local)}, Reason:\"Running\", Message:\"Not all Steps in the Task have finished executing\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"a3494fea-112f-4645-9790-b9bbf1712f3c","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:39.888Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:503","msg":"Successfully reconciled taskrun step-stream-tr/default with status: &apis.Condition{Type:\"Succeeded\", Status:\"True\", Severity:\"\", LastTransitionTime:apis.VolatileTime{Inner:time.Date(2022, time.July, 8, 18, 45, 39, 888581187, time.Local)}, Reason:\"Succeeded\", Message:\"All Steps have completed executing\"}","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"3a0f0e2e-1e1f-475a-8309-146ca78ca719","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:39.888Z","logger":"tekton-pipelines-controller.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TaskRun\", Namespace:\"default\", Name:\"step-stream-tr\", UID:\"7e7f595f-793c-44ea-93af-684483e48511\", APIVersion:\"tekton.dev/v1beta1\", ResourceVersion:\"300121\", FieldPath:\"\"}): type: 'Normal' reason: 'Succeeded' All Steps have completed executing","commit":"df2da84"}
{"level":"info","ts":"2022-07-08T18:45:39.920Z","logger":"tekton-pipelines-controller","caller":"taskrun/taskrun.go:122","msg":"taskrun done : step-stream-tr \n","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"ea39672a-69b5-471b-b1c7-4bd34bda2907","knative.dev/key":"default/step-stream-tr"}
{"level":"info","ts":"2022-07-08T18:45:39.921Z","logger":"tekton-pipelines-controller","caller":"controller/controller.go:550","msg":"Reconcile succeeded","commit":"df2da84","knative.dev/controller":"github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler","knative.dev/kind":"tekton.dev.TaskRun","knative.dev/traceid":"ea39672a-69b5-471b-b1c7-4bd34bda2907","knative.dev/key":"default/step-stream-tr","duration":0.001252753}

I am trying to check if this is a legit failure or not.

Never mind, its part of the task result itself 🙃 was a little confused without any separation 😄

What is the expectation when stdout and stderr are extracted into task results? I do not see them populated in the taskRun status. digest and error are task results and was expecting to have them initialized and populated in the status.
kubectl get tr step-stream-tr -o json | jq .status.taskResults
null

| jq .status.taskResults

I typically use tkn tr describe step-stream-tr -o json | jq .status.taskResults

| jq .status.taskResults

I typically use tkn tr describe step-stream-tr -o json | jq .status.taskResults

This is what I think you are looking for:
kubectl get tr step-stream-tr -o json | jq .status.taskResults
[
  {
    "name": "digest",
    "type": "string",
    "value": "sha256:b3abe4255706618c550e8db5ec0875328333a14dbf663e6f1e2b6875f45521e5\n"
  },
  {
    "name": "error",
    "type": "string",
    "value": ""
  }
]

You'll need to make sure you have the alpha feature flag enabled...
apiVersion: v1
kind: ConfigMap
metadata:
  name: feature-flags
  namespace: tekton-pipelines
data:
  enable-api-fields: "alpha"

Also, you may need to actively delete the task run before trying to re-run it:
$ tkn tr delete step-stream-tr
$ kubectl apply -f examples/v1beta1/taskruns/alpha/step-stream-support.yaml
$ tkn tr logs --last -f
[digest-step] sha256:b3abe4255706618c550e8db5ec0875328333a14dbf663e6f1e2b6875f45521e5

[log-results] digest: sha256:b3abe4255706618c550e8db5ec0875328333a14dbf663e6f1e2b6875f45521e5
[log-results]
[log-results] error:

$ kubectl get tr step-stream-tr -o json | jq .status.taskResults
[
  {
    "name": "digest",
    "type": "string",
    "value": "sha256:b3abe4255706618c550e8db5ec0875328333a14dbf663e6f1e2b6875f45521e5\n"
  },
  {
    "name": "error",
    "type": "string",
    "value": ""
  }
]

Thank you @bradbeck for this 🙏 I am still reviewing these changes. It's very exciting to see this feature being implemented. A couple of items I would like to be addressed (not necessarily the same PR) if they are not already included:

Please create a section under Defining Steps to include detailed documentation on this feature and highlight caveats of using stderr/stdout with task results which are mentioned in the proposal. It's reasonable to get these details from the proposal directly.
Some form of validation around task result redirection. The controller can report an error if a step is trying to redirect stdout/stderr to a task result which is not defined in the task. This can cause failures when a pipeline has a task trying to consume stdout of a step in form of a task result.
More examples including: 1 - multiple steps with stdout and stderr in a task, 2 - stdout and stderr redirected to a file in a workspace, 3 - stdout and stderr set to the same task result

Once again thank you so much for this PR and thank you for your patience 🤗

/retest

yay, tests passing now!! 😎


improve read me file to have a few pictures of the project along with girlscript banner

I would like to work on this issue under gssoc .
@RituKumari98

I would like to contribute for this project. Please assign this task to me under GSSoC'24 with required labels.


should archived pkgs be removed?

e.g., i just archived this pkg https://cranchecks.info/pkgs/crevents and the data is still there, i guess each day now has the last day of data that existed?
often though pkgs can be archived by cran, then submitted again, etc.  - so we wouldn't want to lose history for that pkg.

For email notifications - it'd be ideal i think to skip any pkgs that are archived - would need a foolproof way to sort out if a pkg is archived

For email notifications - it'd be ideal i think to skip any pkgs that are archived - would need a foolproof way to sort out if a pkg is archived

https://github.com/ropensci/fulltext also has a CRAN OK badge despite being archived on CRAN.

Thanks for letting me know @maelle
I should probably fix this


Updated DiabetesNotebook.ipynb

#16

Trained the model on Simple Linear Regression algorithm
Predicted the Test set results
Displayed the difference between actual and predicted values.

The Update README.md commit was for issue number #9, but don't know how it got committed to this issue. How can I resolve this?

Hey @aayushibansal2001 there are conflicts in this branch resolve them.

Hey, @aayushibansal2001 you have to make different branches for different issues and never do changes in the main branch.I cannot merge this PR as in this the changes were done in the main branch of your local repo. Kindly make a different PR for both the issues, take your time, and if you want any kind of help contact the mentors or me. Happy Coding

Sure! Will do that. Thanks for pointing out the mistake.


Could not install on macOS 10.14.6

Description:
Tried to install cell acdc on macos 10.14.6. During pip install stage, received this error:
`Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Building wheels for collected packages: opencv-python-headless
Building wheel for opencv-python-headless (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for opencv-python-headless (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [84 lines of output]
  --------------------------------------------------------------------------------
  -- Trying 'Ninja' generator
  --------------------------------
  ---------------------------
  ----------------------
  -----------------
  ------------
  -------
  --
  CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.Not searching for unused variables given on the command line.

  -- Configuring incomplete, errors occurred!
  --
  -------
  ------------
  -----------------
  ----------------------
  ---------------------------
  --------------------------------
  -- Trying 'Ninja' generator - failure
  --------------------------------------------------------------------------------

  --------------------------------------------------------------------------------
  -- Trying 'Unix Makefiles' generator
  --------------------------------
  ---------------------------
  ----------------------
  -----------------
  ------------
  -------
  --
  Not searching for unused variables given on the command line.
  -- The C compiler identification is unknown
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - failed
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc - broken
  CMake Error at /private/var/folders/n0/y06cp9mx3s337p18h34s6lxw0000gp/T/pip-build-env-4y3vda9o/overlay/lib/python3.10/site-packages/cmake/data/share/cmake-3.30/Modules/CMakeTestCCompiler.cmake:67 (message):
    The C compiler

      "/usr/bin/cc"

    is not able to compile a simple test program.

    It fails with the following output:

      Change Dir: '/private/var/folders/n0/y06cp9mx3s337p18h34s6lxw0000gp/T/pip-install-yhanh8ka/opencv-python-headless_baa1a604e81e4c19a20823886af04044/_cmake_test_compile/build/CMakeFiles/CMakeScratch/TryCompile-tpT8gH'

      Run Build Command(s): /private/var/folders/n0/y06cp9mx3s337p18h34s6lxw0000gp/T/pip-build-env-4y3vda9o/overlay/lib/python3.10/site-packages/cmake/data/bin/cmake -E env VERBOSE=1 /usr/bin/make -f Makefile cmTC_205f2/fast
      xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

    CMake will not be able to correctly generate this project.
  Call Stack (most recent call first):
    CMakeLists.txt:3 (ENABLE_LANGUAGE)

  -- Configuring incomplete, errors occurred!
  --
  -------
  ------------
  -----------------
  ----------------------
  ---------------------------
  --------------------------------
  -- Trying 'Unix Makefiles' generator - failure
  --------------------------------------------------------------------------------

                  ********************************************************************************
                  scikit-build could not get a working generator for your system. Aborting build.

                  Building MacOSX wheels for Python 3.10 requires XCode.
  Get it here:

    https://developer.apple.com/xcode/

                  ********************************************************************************
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for opencv-python-headless
Failed to build opencv-python-headless
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (opencv-python-headless)`
Seems to require xcode, which requires a macos 14 to install.
Way to reproduce:
No response
(Optional) Link to data to reproduce error:
No response
Terminal output:
No response
Log file:
No response
Version information:
No response

Hi Jordan, unfortunately, that looks like an error with the package opencv-python-headless and it sounds like they stopped supporting macOS 10.14.
However, I would still try something. Can you try from conda? Are you in a conda environment? If yes, you can try this command

It seemed to have solved that problem, but I ran into another one. When I try to run acdc, it wants to install QtPy, but I run across an error when it tries to install it:
Cell-ACDC needs to install a GUI library (default library is PyQt6`).
You can install it now or you can close (press "n") and install
a compatible GUI library with one of the following commands:
* pip install PyQt6==6.6.0 PyQt6-Qt6==6.6.0
* pip install PyQt5 (or `conda install pyqt`)
* pip install PySide2
* pip install PySide6

Note: if PyQt6 installation fails, you could try installing any of the other libraries.
Do you want to install it now ([y]/n)? y
Requirement already satisfied: PyQt6==6.6.0 in /opt/anaconda3/envs/acdc/lib/python3.10/site-packages (6.6.0)
Requirement already satisfied: PyQt6-Qt6==6.6.0 in /opt/anaconda3/envs/acdc/lib/python3.10/site-packages (6.6.0)
Requirement already satisfied: PyQt6-sip<14,>=13.6 in /opt/anaconda3/envs/acdc/lib/python3.10/site-packages (from PyQt6==6.6.0) (13.6.0)
Traceback (most recent call last):
File "/opt/anaconda3/envs/acdc/bin/acdc", line 8, in
sys.exit(run())
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/main.py", line 49, in run
run_gui()
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/main.py", line 61, in run_gui
_setup_gui_libraries()
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/_run.py", line 242, in _setup_gui_libraries
import pyqtgraph
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/pyqtgraph/init.py", line 18, in
from .colors import palette
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/pyqtgraph/colors/palette.py", line 1, in
from ..Qt import QtGui
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/pyqtgraph/Qt/init.py", line 184, in
import PyQt6.QtCore
ImportError: dlopen(/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/PyQt6/QtCore.abi3.so, 2): Symbol not found: _objc_opt_class
Referenced from: /opt/anaconda3/envs/acdc/lib/python3.10/site-packages/PyQt6/Qt6/lib/QtCore.framework/Versions/A/QtCore (which was built for Mac OS X 11.0)
Expected in: /usr/lib/libobjc.A.dylib
in /opt/anaconda3/envs/acdc/lib/python3.10/site-packages/PyQt6/Qt6/lib/QtCore.framework/Versions/A/QtCore`

Oh ok, PyQt6 also doesn't seem to be supported on macos 10. I would try pyqt from conda with conda install -c conda-forge pyqt.
You have to uninstall PyQt6 first with pip uninstall PyQt6.
Also, it might be easier to start from scratch.
First check the location of the acdc environment folder with the command conda env list
Then to remove the environment deactivate it and run the command conda env remove -n acdc and check that the acdc folder is gone. If not delete it manually.
You can then restart from scratch and remember conda install -c conda-forge pyqt before running acdc.
Let me know if it works thanks!

PS: I said "Hi Jordan", but I meant "Hi Jacob", my apologies 😄

No worries.
We tried re-creating the environment, and got past the issue. But now, we get another error right before acdc loads. We get a flash of the logo before getting this error message:
(acdc) DN0a230841:~ skotheimlab$ acdc Traceback (most recent call last):   File "/opt/anaconda3/envs/acdc/bin/acdc", line 8, in <module>     sys.exit(run())   File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/__main__.py", line 49, in run     run_gui()   File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/__main__.py", line 99, in run_gui     app, splashScreen = _run._setup_app(splashscreen=True)   File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/_run.py", line 361, in _setup_app     from . import load   File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/load.py", line 6, in <module>     import cv2   File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cv2/__init__.py", line 181, in <module>     bootstrap()   File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cv2/__init__.py", line 153, in bootstrap     native_module = importlib.import_module("cv2")   File "/opt/anaconda3/envs/acdc/lib/python3.10/importlib/__init__.py", line 126, in import_module     return _bootstrap._gcd_import(name[level:], package, level) ImportError: dlopen(/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cv2/cv2.abi3.so, 2): Library not loaded: @loader_path/.dylibs/libavcodec.60.31.102.dylib   Referenced from: /opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cv2/cv2.abi3.so   Reason: no suitable image found.
I would try an older version then, maybe something less than 4.10 or even older.
To do so run conda install -c fastai opencv-python-headless<4.10.
Here you can find the list of all the versions ever released https://anaconda.org/fastai/opencv-python-headless/files?page=1
Let me know if something works thanks!

You could also try to uninstall opencv-python-headless (with the command conda remove opencv-python-headless and install the non headless version (also try older ones) with the command conda install -c conda-forge opencv-python

using the non headless version worked. Thanks!

Sorry, we got a new error when trying to run the segmentation module, when installing tensorflow. we get this message:
`        File "/private/var/folders/n0/y06cp9mx3s337p18h34s6lxw0000gp/T/pip-install-exvx5q3o/grpcio_5685efc0990c4aedbf37be26d17800df/src/python/grpcio/support.py", line 76, in _expect_compile
raise commands.CommandError(
commands.CommandError: Diagnostics found a compilation environment issue:
  Could not find <Python.h>. This could mean the following:
    * You're on Ubuntu and haven't run `apt-get install python3-dev`.

    * You're on Windows and your Python installation was somehow corrupted
      (check your environment variables or try re-installing?)

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for grpcio
Running setup.py clean for grpcio
Failed to build grpcio
ERROR: Could not build wheels for grpcio, which is required to install pyproject.toml-based projects

File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/myutils.py", line 2512 - 14:13:55:
Traceback (most recent call last):
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/myutils.py", line 2480, in check_install_package
import_module(import_pkg_name)
File "/opt/anaconda3/envs/acdc/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1004, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'tensorflow'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/myutils.py", line 2504, in check_install_package
_install_tensorflow()
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/myutils.py", line 2743, in _install_tensorflow
subprocess.check_call(args, shell=shell)
File "/opt/anaconda3/envs/acdc/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/opt/anaconda3/envs/acdc/bin/Cell-ACDC', '-m', 'pip', 'install', '-U', 'tensorflow']' returned non-zero exit status 1.
`

Hi Jacob,
I would try to install tensorflow from conda with conda install -c conda-forge tensorflow.
If it works you will need to install yeaz without dependencies because otherwise it would try to install tensorflow too (because yeaz is only with pip and pip cannot see what was installed with conda).
To do that run pip install --no-deps yeaz. It might be that one or two packages are still missing from yeaz dependencies but I'm not sure. If yes, install the missing package too.
Let me know if it works thanks

We get another error when we do that. it looks like we don't have tensorflow.keras? I looked it up and it looks like we need tensorflow ver 1.14?
`Downloading YeaZ (if needed)...
Downloading YeaZ model(s) to "/Users/skotheimlab/acdc-appdata/acdc-YeaZ"
Importing YeaZ...
2024-07-12 10:21:24.148217: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
Traceback (most recent call last):
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/myutils.py", line 2894, in import_segment_module
acdcSegment = import_module(f'cellacdc.models.{model_name}.acdcSegment')
File "/opt/anaconda3/envs/acdc/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/models/YeaZ/acdcSegment.py", line 10, in
from .unet import model
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/models/YeaZ/unet/model.py", line 12, in
from tensorflow.keras.models import Model
ModuleNotFoundError: No module named 'tensorflow.keras'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/_main.py", line 1597, in launchSegm
self.segmWin.main()
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/segm.py", line 518, in main
acdcSegment = myutils.import_segment_module(model_name)
File "/opt/anaconda3/envs/acdc/lib/python3.10/site-packages/cellacdc/myutils.py", line 2899, in import_segment_module
model_path = cp[model_name]['path']
File "/opt/anaconda3/envs/acdc/lib/python3.10/configparser.py", line 965, in getitem
raise KeyError(key)
KeyError: 'YeaZ'`

I'm using v1 because it seems to work better than v2. We can try v2 though.
we have tensorflow ver 2.16.1
ill try installing keras 2.1

If YeaZ v1 works better than stick to it absolutely.
Also try older versions of tensorflow, the 2.16  is from 10 days ago and I don't exclude they did not test it on older macos versions. Tensorflow <2.8 should also work. Let me know how it goes, thanks

2.1 didnt work, but it said tensorflow needs keras 3.0.0, so I tried that, and it seems to work. Thanks!

Great! Note that 2.1 is different from 2.16 because the 16 is actusy 15 versions newer that 1.
Anyway I'm happy it works! Kind of cumbersome but developers are abandoning support to older versions of macos unfortunately.


Update Test-Network.ps1

More like a proposition to use system itself to tell us if it is connected to Internet. its quite fast!
Proposed Changes

replacing looped pinging with method available from Windows Vista/Windows Server 2008. System could tell if it has access to Internet or not.

Related Issues

none, I'm just blocking www.msftncsi.com and www.msftconnecttest.com in my network. Current method signals offline state and WAU simply stops.

Lovely now it is clean :)

We do not want to WAU stopping if no internet connexion. If configured at start-up, sometimes network is not up, and WAU never starts...

I found an orphaned discussion https://github.com/Romanitho/Winget-AutoUpdate/discussions/394
It seems that proposed windows method could be useful after all (thanks to a good back-compatibility with OSes)


dollar sign substitution is not working if the .env file is located in a custom path

In a react project

An environment file named as .env.uat is located at ./env.
In the environment file, there's a variable with dollar sign value. Eg: REACT_APP_TEST=${TEST}
The "start" script is having the following command, "env-cmd -f ./env/.env.uat react-scripts start".
Run the "start" script as follow, "TEST=HELLO npm run start".
However, the value shown in the app is "${TEST}", instead of "Hello".

Yeah, so this program does not work that way. You are supposed to put the HELLO in your .env file. If you wish to pass environment variables via the command lineTEST=HELLO npm run start, look at combining env-cmd with cross-env


Add exclude option for penthouse forceExclude config

Summary
Added option to exclude certain css selectors from the critical css using the forceExclude option in penthouse.
QA notes
We can run the critical-css.yml workflow from the iFixit/ifixit side (with this branch specified) to verify it still works.
qa_req 0
connects #47316

QA 🚛 tested the changes in https://github.com/iFixit/ifixit/pull/47367#issuecomment-1505796048

dev_block 🚛

un_dev_block 🚛 fixed https://github.com/iFixit/css-gather/pull/9#discussion_r1165975217 in https://github.com/iFixit/css-gather/pull/9/commits/89f826b2ee03e83ac613e1d0e8d9cd24c9624e47

Steps used to test:

Before excluding any elements from the critical css, confimed that #mainBody css exists.

Then ran the run.rb script with --exclude=/mAiNbOdy/gi option:
./run.rb https://www.ifixit.com/ --exclude=.skip-to-content --exclude=/mAiNbOdy/gi --exclude=/invalidregex > after
Then verified that passing regex with gi flags works properly now.
|

QA 🚛

un_deploy_block 🚛 the pull on iFixit/ifixit side got reviewed


How to supply arguments to dnx . run on mono linux?

I have the following code but args keeps null
Anyone have an idea?
public class Program
{
	public async Task<int> Main(string[] args)
	{
	}
}

How do you invoke the program? It should work by just passing the arguments like you do it for any other application

I use dnx . run myarg

Does it work without async/task?
What mono version are you using?

Sorry, now that I know that it should work I overlooked my code again thoroughly and it was the statement just before the args that threw the null pointer. Maybe I miss the debugger :-)
Everything works as expected also the async way.


Trying to accelerate playback start

Hi, I'm trying to accelerate the start of playback, but shaka downloads several chunks before starting to play.
Just to test, I'm configuring the player like this:
player.configure({
	streaming: {
		rebufferingGoal: 1,
		bufferBehind: 1,
		bufferingGoal: 1,
		retryParameters: {
			maxAttempts: 5,
		},
	},
})

Segments are about 1.5~3 seconds. Why shaka downloads 4~5 segments before starting, when it could start playing with the first one?
Thank you

Hi,
Shaka starts playback as soon as it has downloaded and inserted the init segment and first media segment of each initial Stream chosen (e.g., middle bitrate audio and low bitrate video), regardless of the buffering goals. After it downloads these segments, it will fetch the init segments of each <Representation> in the manifest in the background. However, multiple media segments could be downloaded before playback begins, since there will always be some delay between when Shaka inserts media segments and when the video element begins playback.
To help rule some things out, can you enable verbose logging and add
video.addEventListener('playing', function() { console.log('PLAY'); });
video.addEventListener('loadedmetadata', function() { console.log('LOADED_METADATA'); });

before loading the manifest and check how many fetchAndAppend_ calls there are before "PLAY" is logged?

I forgot to mention that Shaka will download the segment which precedes the one it actually needs (based on the manifest) after seeking and when beginning a live presentation. This is done because the timestamps in the actual media segments may be slightly ahead or behind what is specified in the manifest; by fetching an earlier segment we reduce the possibility of introducing a gap between the playhead and the segment inserted.
So, if your stream is live, this may explain why there are some additional segments being downloaded.

@aletorrado Is this still an issue for you, or can we close it?

@aletorrado, since we haven't heard from you in a while, I'm closing this issue now.  If you need further support, just let us know and we'll be happy to help.


Allow YAML to load hashes and arrays

This aims to resolve #2476

I suspect this might be better solved by ensuring that the data is not serialised as ActiveRecord::HashWithIndifferentAccess to begin with.
I haven't looked in detail yet.

This is being closed because @adamcooke has done a better job of tracking down the issue and will follow with a proper fix.


docs: optimize examples for propagating results

The previous example did not actually output results, leading to the misconception that it was not effective.

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[ ] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind documentation

/ok-to-test

/test pull-tekton-pipeline-integration-tests

/retest-required

/cc @JeromeJu
Could you please take a look at this PR?
It's also related to documentation.
It's been created for over a month now. 😆


add devfile.yaml for java-plugin test

Would like to create a branch instead pr, so closing this pr


Support Python 3

Given Python 3 support was only added to Django after they added  prefetch_related how useful if adding Python 3 support to batch select?
Also I'm not actually using Python 3 in anger yet, so pull requests and help would be nice...

Maybe I've misunderstood django-batch-select, please clarify: When I use
django-batch-select, does it add another query (like Django's
prefetch_related) or does it fetch by adding more SQL code to the
existing query (like Django's select_related)?
On Fri, Feb 27, 2015 at 11:52 AM, John Montgomery<EMAIL_ADDRESS>wrote:

Given Python 3 support was only added to Django after they added
prefetch_related
https://docs.djangoproject.com/en/1.7/ref/models/querysets/#django.db.models.query.QuerySet.prefetch_related
how useful if adding Python 3 support to batch select?
Also I'm not actually using Python 3 in anger yet, so pull requests and
help would be nice...
—
Reply to this email directly or view it on GitHub
https://github.com/lilspikey/django-batch-select/issues/12#issuecomment-76366038
.

Oh, I see now that it adds an extra query, sorry, I should have read the
docs. So it doesn't help me, I was looking for a way to do it without
adding another query. Thanks anyway!
On Fri, Feb 27, 2015 at 1:24 PM, Ram Rachum<EMAIL_ADDRESS>wrote:

Maybe I've misunderstood django-batch-select, please clarify: When I use
django-batch-select, does it add another query (like Django's
prefetch_related) or does it fetch by adding more SQL code to the
existing query (like Django's select_related)?
On Fri, Feb 27, 2015 at 11:52 AM, John Montgomery <
<EMAIL_ADDRESS>wrote:

Given Python 3 support was only added to Django after they added
prefetch_related
https://docs.djangoproject.com/en/1.7/ref/models/querysets/#django.db.models.query.QuerySet.prefetch_related
how useful if adding Python 3 support to batch select?
Also I'm not actually using Python 3 in anger yet, so pull requests and
help would be nice...
—
Reply to this email directly or view it on GitHub
https://github.com/lilspikey/django-batch-select/issues/12#issuecomment-76366038
.


Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
8GB
What version did you experience this issue on?
2.3.1
What happened?
Collecting torchmetrics (from InvokeAI)
ERROR: HTTP error 403 while getting https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl (from https://download.pytorch.org/whl/cpu/torchmetrics/)
ERROR: Could not install requirement torchmetrics from https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl (from InvokeAI) because of HTTP error 403 Client Error: Forbidden for url: https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl for URL https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl (from https://download.pytorch.org/whl/cpu/torchmetrics/)
Screenshots

Additional context
Collecting torchmetrics (from InvokeAI)
ERROR: HTTP error 403 while getting https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl (from https://download.pytorch.org/whl/cpu/torchmetrics/)
ERROR: Could not install requirement torchmetrics from https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl (from InvokeAI) because of HTTP error 403 Client Error: Forbidden for url: https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl for URL https://download.pytorch.org/whl/torchmetrics-1.0.3-py3-none-any.whl (from https://download.pytorch.org/whl/cpu/torchmetrics/)
Contact Details
<EMAIL_ADDRESS>

您可以安装然后再次尝试安装程序吗？pip install torch metrics

Thanks


Error: Could not find a suitable provider for elasticsearch_role/elasticsearch_user_roles

Module version: 6.3.3
Puppet version: 4.10.8
OS and version: Red Hat Enterprise Linux Server release 7.5 (Maipo)

Bug description
When installing elasticsearch on an all-in-one development box together with many applications (and thus many modules), the following error messages pop up regularly and lead to a failed puppet run:

Error: Could not find a suitable provider for elasticsearch_role
Error: Could not find a suitable provider for elasticsearch_user_roles

This is due to the way, how these users are created, which triggers a bug in puppet when collecting resources.
We worked around this issue by using file resources for "${elasticsearch_home}/config/${instance}/x-pack/users", "${elasticsearch_home}/config/${instance}/x-pack/users_roles" and "${elasticsearch_home}/config/${instance}/x-pack/roles.yml" instead of using the defined types elasticsearch::role and elasticsearch::user for the file based users and defined our own defined types which create roles and users via curl calls to the API.
Attached examples are stripped down/simplified.
auth_snippet.pp.txt
role.pp.txt
roles.yml.epp.txt
user.pp.txt
users.epp.txt
users_roles.epp.txt

Despite not using elasticsearch::user and elasticsearch::role any more, Puppet still shows an error when building a machine from scratch:
27/11/2018 09:30:22     default: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Virtual Query, Could not autoload puppet/type/elasticsearch_user_file: Could not autoload puppet/provider/elasticsearch_user_file/oss_xpack: no such file to load -- puppet/provider/elastic_parsedfile at /etc/puppetlabs/code/environments/vbox/modules/elasticsearch/manifests/init.pp:555:6 on node box-krn0-vbx-v01.sf-bk.de

Could not autoload  +1

I had a similar Issue:
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Virtual Query, Could not autoload puppet/type/elasticsearch_user: Could not autoload puppet/provider/elasticsearch_user/esusers: no such file to load -- puppet/provider/elastic_user_command at /etc/puppetlabs/code/environments/production/modules/elasticsearch/manifests/init.pp:544:3 on node mynode
wrote about it in the puppet slack: https://puppetcommunity.slack.com/archives/C0W298S9G/p1549546357003900
I used the sugseted work around: I replaced require with require_relative in the file elasticsearch/lib/puppet/provider/elasticsearch_user/elasticsearch_users.rb line 1. This fixed my Problem! I suggest, read the thread from slack I posted above and you see the complete discussion.

+1

FYI, we just facing this exact same problem and we found why. Maybe its not gonna solve the issue for you, but it worked for us.
The problem was coming from the fact that in the "modules" puppet directory, we had the new version of the module in the "elasticsearch" folder, and the older version in the "elasticsearch.ori" folder. And in 99% of puppet run, we get the error because the loaded provider was coming from "elasticsearch.ori".
Since I removed this folder, to get ONLY one elasticsearch module folder, no more error. Every puppet run are ok.
Maybe it can help. Maybe not !


⚠ Bofrost.si has degraded performance

In 69f736d, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 2883 ms

Resolved: Bofrost.si performance has improved in 832da0f after 7 minutes.


Fix intermittent test failures for serverHasBeenUpSinceResourceCached

Adds fake timers to the cache-headers tests for serverHasBeenUpSinceResourceCached, fixes #2571

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against c7e8b512effe7a546f0c6598538d85915f31ff78


Rebuild the landingpage

Really just a placeholder right now, needs a rework.
Could go for a grainy texture option like this: https://codepen.io/Juxtopposed/pen/BaqLEQY (made using this tool: https://fffuel.co/nnnoise/).

Done & pushed to main.


Restructure folder as one python package

Hey Andy,
To most effectively make this whole project installable, I'm thinking that I'll need to restructure the whole folder a bit. Let's talk tomorrow about this - it's not a requirement, but I think makes things better. I just think I should merge your changes first, then restructure, then merge my changes into your branch, so that it happens in one fell swoop.

Notes on this:

[ ] Toolbox mapping code seems to not work - but not sure if this is related to the move
[ ] installer doesn't properly check dependencies yet
[ ] R isn't fully set up for this - need to set up R and provide lib for connecting

Folder is restructured.


Use locally defined email for commits

Currently the backport tool uses the globally defined email when for the backport commit. Instead it should use the locally defined email address.
The email address for the local repo can be retrieved with git config user.email and updated with git config --local user.email<EMAIL_ADDRESS>

Hi,
Why has this issue been closed?
I'd be interested in retrieving user email and username from local branch (or from the user's backport config file), because I don't want to define global git properties to define them.
Is that possible with the current version.
Today, I end up with this error:
remi > backport
? Select commit #506 (4c36bfb6)
? Select branch V5_3
✔ 100% Cloning repository (one-time operation)

Backporting to V5_3:
✔ Pulling latest changes
✖ Cherry-picking: story(API): optimize persist and mass update data request processing (#506)
Cherrypick failed:
Command failed: git cherry-pick -x 4c36bfb653a6b6ad040a3694599274ea62733b9f
Performing inexact rename detection: 100% (409500/409500), done.

*** Please tell me who you are.

Run

  git config --global user.email<EMAIL_ADDRESS>  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'remi@remi-example.(none)')


Mark checkbox removes bold Markdown formatting

Executing Mark checkbox on
- [x] this is a **bold** action

incorrectly removes the bold Markdown formatting, resulting in
- [ ] this is a bold action

instead of just unchecking the checkbox and keeping the rest:
- [ ] this is a **bold** action

Environment: Visual Studio Code 1.79.2 on Windows 10, Markdown Checkbox 1.9.0

In the current version the problem is still there.
Name: Markdown Checkbox
Id: PKief.markdown-checkbox
Description: With this extension you can create checkboxes in markdown and mark them quickly.
Version: 1.9.1
Publisher: Philipp Kief
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=PKief.markdown-checkbox

It's more simple: Markdown: Mark checkbox removes any asterisks, even one:

[x] test*

into

[ ] test


Vectorised print commands not disabling implicit output

When using the v command to vectorise print commands, the print commands do not disable implicit output.
Example: Try it Online!

well dang.

Try it Online!

It looks like this is actually a different issue. If you use O to disable the implicit output, nothing gets printed. Try it Online! If you then add an extra , after the vectorised print, it prints the same unexpected output, so it looks like the vectorised printing is actually modifying the list somehow. Try it Online!

This is a bigger issue than just vectorised printing.


forge inspect --help does not list fileds

Component
Forge
Describe the feature you would like
When running forge inspect --help it would be nice to see a list of the available fields that can be used without having to check this page in the book
Is there a particular reason why they're not included? I would like to try to work on it and submit the PR myself if there's no issue.
Additional context
No response

no reason,
could be added easily


built version

Is there a built file and can put into my shell path?
or perhaps somewhere to learn how to build this project or lua projects in general.
Looks like a great tool, would like it in my terminal

I added a page to the wiki explaining installation, it's copied directly from wrk, the project wrk2 is based on.


Print warnings to stderr

Description of the change
As detailed in https://github.com/spacchetti/spago/issues/256
This PR renames echo and echoStr to output & outputStr for stdout operations
(if there was a different expectation about the implementation details of output let me know)
It also adds logDebug, logWarning, and logError (and removes echoDebug).
This appeared to break two tests, which have an adjusted implementation to account for both stderr and stdout.
Checklist:

[x] Added the change to the "Unreleased" section of the changelog
[ ] Added some example of the new feature to the README
[x] Added a test for the contribution (if applicable)

P.S.: the above checks are not compulsory to get a change merged, so you may skip them. However, taking care of them will result in less work for the maintainers and will be much appreciated 😊

I'll do a follow up PR with the logInfo fn

hmm,  looks like a couple tests may that failed in CI may be related to the changes here,  I'll try and address later today

@Benjmhart it might be that you missed the update for some of the fixtures. Note that in the failing tests there are two different fixtures being checked, depending on the presence of psa on the path:
https://github.com/spacchetti/spago/blob/336b5edc7cd5b3a03a440b09a0c1a54df063ad6c/test/SpagoSpec.hs#L523-L526

hmm these tests fail for different reasons on my local environment, but I'll make adjustments based on the CI results.
@f-f  - I'm getting several tests failing with this IOException of type invalidArgument
is there some missing environmental dependency for tests that you can think of that should be documented, perhaps in the CONTRIBUTING.md file?

@f-f not quite sure what the root of this is,  all these control characters weren't present in the original text file.  maybe this was being emitted to stderr before and it wasn't being tested?

for the moment I'll just add a function to either clear or unescape the ANSI codes so it can be sanely compared to the fixture file

hm,  at this point i'm going to stop until I can get the test suite running correctly.  let me know if you have any idea what the cause of the original invalid byte sequence might be

ok, looks like I've resolved the issues in pipeline.  sorry for that.

@Benjmhart sorry for the trouble! The escape sequences should be there because psa uses color in the output. So I'd say let's not have the stripAnsi machinery, as we can just match on the output
..if the encoding is correct, which is what you figured afterwards.
However, rather than asking users/devs to set envvars to run tests, let's just set UTF8 encoding by default. The way we do it in other places is by calling GHC.IO.Encoding.setLocaleEncoding GHC.IO.Encoding.utf8
I think for setting this up with our test machinery is the following (documented here):

the test/Spec.hs file should contain {-# OPTIONS_GHC -F -pgmF hspec-discover -optF --module-name=Spec #-}
the test/Main.hs should contain the following:module Main where

import Test.Hspec.Runner
import Test.Hspec.Formatters
import qualified Spec
import qualified GHC.IO.Encoding

main :: IO ()
main = do
  GHC.IO.Encoding.setLocaleEncoding GHC.IO.Encoding.utf8
  hspecWith defaultConfig Spec.spec

Could you try to see if this works?

@f-f unfortunately stack will not compile the test suites using that technique, at least on my system,  I'm getting an error:
...
Building test suite 'spec' for spago-<IP_ADDRESS>..
illegally!
[6 of 6] Compiling Spec

<no location info>: error:
    output was redirected with -o, but no output will be generated
because there is no Main module.

I assume this is a GHC error resulting from the options in the HSpec docs.  if you're not sure how to resolve I may open an issue with Hspec, as I don't see any documentation on this issue
This was with the /test/Spec.hs file and /test/Main.hs file as you described
anyhow, I've resolved conflicts, run a test build, and removed the stripAnsi machinery.  the test passes locally.
let me know if these needs further adjustment, or if you'd like me to pursue the issue on HSpec, I'm happy to put in more work to get this where it needs to be.

@Benjmhart right, I forgot to mention that you need to add main: Main to the test suite in the package.yaml to make this work. Anyways don't worry about this, let's merge this PR now and we can take care of the rest in subsequent PRs
Thank you for the great work! 💯

@f-f facepalm I knew it was something obvious.  thanks for your help & patience.
I'll start work on a PR for application output vs application logging over the next few days.

@Benjmhart you're welcome 🙂


pkg/asset: Update calico/cni to v1.11.2

Meant to include this with #818, we bump the calico and sidecar image together.

coreosbot run e2e

coreosbot run e2e

This change doesn't affect the e2e (i.e. flannel) setup, these are the same TestCheckpointer flakes we've been seeing before.

@dghubble is there an opening issue tracking the failure?

coreosbot run e2e

@xiang90 #816


Added support for lookup fields, which isn't a site column

When a lookup field is created/update the List attribute is temporarily removed.
In this case the field cannot be created if RelationshipDeleteBehavior is set.
I've fixed this issue and is also making sure Indexed attribute is set to True if RelationshipDeleteBehavior is either Cascade or Restrict.

Hi @SchauDK, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Thank you for your submission! Much appreciated.


Deliver errors in onError for Rx

The way the api is written errors come the same method as successes. It makes it difficult to write a chain of map, flatmap, debounce or other operations if you have to filter or check out errors first, and completely defeats the purposed design of going reactive.

Thanks for the input. I originally tried using onError, but I found that I like the current design better. The reason is that authentication failures aren't exceptional, and most don't end the event stream. The information passed to onError ends up being the same as to onNext, just held inside an exception, and you need to display that information to the user either way.
I'm not opposed to switching back to using onError for fatal authentication failures, but can you give me an example of what you're trying to do that's not possible but the current design, but would be with onError?

When you're writing your operation, it would look like
getUI().getClicks()
         .flatmap(view -> Observable.zip(Observable.just(someUserInfo), RxReprint.authenticate(), zipToPair()))
         .flatmap(zipped -> getApi().callForAuth(zipped.first, zipped.second))
         .map(doDataMassaging())
         .toList()

Except that for error types it'll also go to the api because the data looks the same, your chain breaks unless you write code to separate from the error cases.
getUI().getClicks()
         .flatmap(view -> Observable.zip(Observable.just(someUserInfo), RxReprint.authenticate(), zipToPair()))
         .flatmap(zipped -> if(itsNotError()) { getApi().callForAuth(zipped.first, zipped.second) } else {  return Observable.empty()})
         .map(doDataMassaging())
         .toList()

    getUI().getClicks()
         .flatmap(view -> Observable.zip(Observable.just(someUserInfo), RxReprint.authenticate(), zipToPair()))
         .filter(noErrorCases())
         .flatmap(zipped -> getApi().callForAuth(zipped.first, zipped.second))
         .map(doDataMassaging())
         .toList()

Right. Correct me if I'm wrong, but it looks like you want onNext to be called only on authentication success, and onError to be called in all other cases. I think the issue with that is that authentication failures aren't errors. A failure might be because a fingerprint wasn't read completely, or the sensor is locked out temporarily. In every case, you need to update your ui. But in the first case, the sensor is still running, and more events can get emitted, so onError isn't appropriate since it would terminate the stream.

You have to let the user decide what to do when an error is received, including unsubscribing oneself by letting the chain die.
If the sensor is still open and could potentially deliver a correct value, retry() or retry with a policy will reconnect the observable after that first error. doOnError to update UI exist precisely for the cases mentioned.

I do stop delivering onNext and cancel the operation after an unsubscribe. I can see that value in having onNext only fire on successful authentication. The problem with implementing that, though, is that there is no way to have the fingerprint sensor on without receiving events from it. I suppose we could cancel the authentication request every time we get a non-fatal error, but I like that currently the user doesn't ever have to restart the call themselves.

Fair enough, if that's the design choice.

With commit 85d66e, I decided to leave the callback based api as it was, but I changed to reactivex contract to only call onNext for a successful authentication, and onError in all other cases.
@pakoito let me know if this still doesn't work for your use case.