mobile menu

The menu shows all the bitovi links in bold and without hierarchy, which looks weird. It also seems to imply that the blog link is for DoneJS.
2 options.

We remove everything except one link to Bitovi.
We make the hierarchy clear with indentation.

I vote for nbr 1. Not sure the rest are needed on mobile.

@moschel Yes, you're right it does look a bit off still.
I am normally against removing things from a responsive site, if the only reason is that it's the mobile view.  Rather, I like to design an alternative solution.   But in this particular case, I do think you're right and it can be removed.  I also think that we should remove the Bitovi.com link because all of that information is all available on the About page, which is already in the menu.
Here's the proposed redesign:


memory

while labeling on image in cvat, the memory (ram) starts to increase and the software can slow down after a few minutes and hangs
what is the solution?

I have that problem when i use firefox browser. With chrome browser it's ok. As i know chrome is only supported browser.

@masoudgh85
Please, fill the issue template (CVAT version, OS, browser, etc) and provide more information about your annotation case (how many annotations, what objects, etc).


Find All References fails for CommonJS named exports in checkJs Mode

🔎 Search Terms
"export", "references", "commonjs", "checkJs", "allowJs",
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
This bugs reproduces in typescript@3,4,5

⏯ Playground Link
No response
💻 Code
Request find all references for the symbol f in f.js
// f.js:
function f() {}
module.exports = {
  f,
};

// main.js
const { f } = require("./f");
f();

Reproduction repo: https://github.com/golopot/testcommonjs
🙁 Actual behavior
Doesn't find the reference from the dependent ./main.js.
🙂 Expected behavior
Do find the reference from the dependent ./main.js.
Additional information about the issue
{
  "compilerOptions": {
    "target": "es2016",
    "module": "commonjs",
    "allowJs": true,
    "checkJs": true,
    "noEmit": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "strict": false,
    "skipLibCheck": true
  }
}

So we try to find all the occurences where the require syntax is being and it is not able to reference from where it is exported. I want to know what do we intend to do after that? should we convert all of them to import syntax?


Make electron an optional peer dependency of certa

@paulius-valiunas what does the error message look like if you try to run the electron version without adding an electron dependency?

@paulius-valiunas what does the error message look like if you try to run the electron version without adding an electron dependency?

I haven't tested that separately, but I think it would fail the same way as it did before I added the dev dependency:
https://dev.azure.com/bentleycs/iModelTechnologies/_build/results?buildId=931115&view=logs&j=00af5505-930d-50dd-3844-b167e8b4bb13&t=ba054ee8-7c31-5c9b-f621-ed022530505c&l=1160


video_player: autodetect video source format

Use the file/url extension to detect the source format and accordingly create the right media sources

@googlebot assign reviewer please.

@pyros2097 Thanks for this PR! Been trying fruitlessly to get HLS streams working on flutter all day till I saw this. Hope it gets merged soon.

@anupcowkur Yeah man, Even I need this to be merged. So what I did now is add the platform channel in my app directly. Can't wait for this to be merged to test it out.

@mravn-google Done. Thank you.

Oh man... too late someone else bumped the version to 0.6.2 and pushed sad.

0.6.3 has been released as well. You might want to rebase and bump to 0.6.4 ;)

6.3 is already out. I'll hold back on more pushes until we've landed yours.

Haha... Yeah... Just figured that out. Thanks btw.

This seems like the wrong approach... shouldn't we be dispatching based on the headers we receive from the server, rather than the extension? Paths in URLs are supposed to be opaque.

@Hixie Yes you are right. That would be the ideal solution. But then it is also possible to not send the right header so at that point we would need to fallback on the extension or manually provided format type. Also didn't dig into how to implement it using headers.
Also I looked into how react-native-video implemented it and followed their approach.
https://github.com/react-native-community/react-native-video/blob/master/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java#L285

isHLS from #607 ... I want it back.
video_player plays m3u8 format on both platforms, but it just plays all quality streams at once instead of progressively loading with network streams.
It works well with JWPlayer but not with the video_player plugin :-(


Mac OS support

I see some hardcoded paths that indicates this is a Windows only app. I tried changing the path to see if it works on Mac but had no luck.
So was wondering if its doable and if so how would one go about making that enhancement and potentially creating a PR.
Thanks

@Kichi779 i have a fix ready, but i need permission to make a new branch and PR

can u please fork this repo? im on macos too with m1 and im searching for this!

@x3r4n0 i will give you access, but its a private repo since id like to just push to this code.


NETOBSERV-2005: Add webhook check to prevent CIDR duplication when configure multi rules filtering

Description
prevent users from using duplicate CIDR when configure multi filter rules
Dependencies

n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labeled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/label qe-approved

Verified wh does not allows creation of filters with duplicate CIDR


[material-ui][Stepper] Generate class for nonLinear prop

This PR adds the nonLinear utility class to the Stepper component when the nonLinear prop is used.
Deploy preview: https://deploy-preview-42620--material-ui.netlify.app/material-ui/react-stepper/#non-linear
Closes #42360

[x] I have followed (at least) the PR section of the contributing guide.

@alexismo can you add test case for change in this file https://github.com/mui/material-ui/blob/next/packages/mui-material/src/Stepper/Stepper.test.tsx. Refer to existing test cases on how to write a test

Thank you @DiegoAndai for the review 🙏 The example you're showing in CSB looks correct. It will be even better with styleOverrides.


New version: LinwoodDev.Flow.Nightly version 0.3.0

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installer Verification Analysis Context Information:
Specified hash doesn't match.
Actual hash:   EC53E28EBB075E7B37C48EED5463CBCC5E5587B4A8B386B196C2DC319FE31E84
Expected hash: 84c534e6368a0d41ab4652ea32aacb5f23c10e8ac104804a964c54f67ee94d50

5/27/2024 6:01:46 PM

Installer Validation

(Automated response - build 881.)

Automatic Validation ended with:

2024-06-03 01:28:05.744 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

(Automated response - build 882.)


Gradle build:

Enabled linked-projects (Expecting some still to fail).
FIxed cleaning issue for linked projects
Build Ant plugin without rebuilding common.

Can one of the admins verify this patch? (see README)

Merged, thanks!


Develop: Add advanced search

As a user, I want to be able to search for mail from a specific sender without searching the full mail text.
Acceptance Criteria

User can specifically search the "Sender" field with a search keyword
User can specifically search the "ImageText" field with a search keyword
Document any relevant content in the Programmer guide (draft thoughts of usage and importantly the "Why")
Updates SRS and STP (and other docs if necessary)
Add/Update relevant unit tests

tested on android

tested on iPhone

tested on iPad

Verified - Test PASS


Switching between assets doesn't update

Describe the bug
When switching between some assets, the UI doesn't update to the selection.
https://share.vidyard.com/watch/mGR6J3d4R3BzPMj5BALDu7?

fixed


Template disappears if you paste text and then want to edit it

If you want to submit a request => https://fragdenstaat.at/anfrage-stellen/ and paste or write something in the form, and then click to edit the whole letter ("vorlage bearbeiten"), the text provided by the template disappears.
This does not appear to happen if you click "vorlage bearbeiten" while you haven't written or pasted anything into the form.

That happens to enable switching back and forth between the modes - either you write everything, or you get the boilerplate. Would be hard to enable switching back otherwise. Working as intended, IMO.


Error: Failed to decode downloaded font

When I run the page in production mode (combined, and minified), I get a repeating console warning that looks like this:
Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Thin.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Light.ttf
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff2
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.woff
localhost/:1 Failed to decode downloaded font: http://localhost:9000/font/roboto/Roboto-Regular.ttf

Are you sure the fonts are accessible from http://localhost:9000/font/roboto/ ?

I have the same problem. I'm use Rails and Ember CLI. I'm able to open all fonts in chrome resource panel, so they are accessible.

I just add next mime types to my Rails config/mime-types.rb and the problem went away.
Mime::Type.register 'application/x-font-woff', :woff
Mime::Type.register 'application/font-woff2', :woff2
Mime::Type.register 'application/x-font-ttf', :ttf

I think this issue should be closed because it is absolutely not related to materialize.

Closing this as we haven't heard back from @krisalexander and @siriniok's issue has been resolved.
@krisalexander you can comment again here to reopen the issue if necessary.


Add test runner for html5lib-tests tokenizer tests

Can be run via zig build test-html5lib

Adds https://github.com/html5lib/html5lib-tests as a submodule in test/html5lib-tests
Adds a test runner for the tokenizer test files in that repo

Note: None of the test files currently pass in their entirety yet; making these tests pass are just something to shoot for
Not all of the test files are included yet, since either the test runner doesn't support something yet (e.g. doubleEscaped) or the tokenizer doesn't support something yet (e.g. lastStartTag)

Additional notes:

I'm not certain that all the html5lib test cases are 100% spec compliant

EDIT: Worth noting that web-platform-tests (which seems to be part of WHATWG/W3C) generates some of its parser tests from the html5lib tests, so that should mean they're relatively authoritative/spec compliant

I left in quite a few std.debug.print calls; I think they might be helpful when debugging/fixing the broken test cases
I noticed that EOF handling is a big part of why a lot of these tests are failing (e.g. eof-in-doctype, eof-in-cdata, etc, are never emitted/handled currently). That's one area that might lead to a big improvement in the number of passing test cases quickly.

This is awesome. If you wouldn't mind, could you pull master and fix any issues that may have arisen from the changes I was working on yesterday? I'll merge this as soon as things are working correctly and then work on getting all the tests passing. I have the stuff in place for proper EOF handing, it's just going to take a bit of doing.

Updated


Image in Documentation Not Loading

In the documentation for gated linear unit here, the image of the gated linear unit is not loading.
Inspecting the HTML code reveals that the image is stored at this url which works perfectly fine and it actually displays the following image:

which seems to be the correct image.
I don't know why the image is not loading in this case. Any ideas?

Loading the docs URL (Gated Linear Unit) in incognito mode, I can reproduce the issue and see the 403 when the browser tries to load the image from this google cloud storage location.
@bandish-shah - can you look into the permission set for the image?


Can't run example

I created and connected 3 directories
model_out:/model_out
profile_results:/profile_results
model_repository:/models
The add_sub model is located in the model_repository directory
docker run -it --rm --gpus all -v //var/run/docker.sock:/var/run/docker.sock -v D:/triton-inference-server/model_repository:/models -v D:/triton-inference-server/model_analyzer/model_out:/model_out -v D:/triton-inference-server/model_analyzer/profile_results:/profile_results --net=host nvcr.io/nvidia/tritonserver:23.03-py3-sdk
then I run the analysis
model-analyzer profile --model-repository /models --profile-models add_sub --triton-launch-mode=docker --output-model-repository-path /model_out/out --export-path /profile_results --run-config-search-max-concurrency 2 --run-config-search-max-model-batch-size 2 --run-config-search-max-instance-count 2 --override-output-model-repository
[Model Analyzer] Initializing GPUDevice handles
[Model Analyzer] Using GPU 0 NVIDIA GeForce RTX 2070 with UUID GPU-7e946a10-0fdc-a67e-6007-87ab98cf2333
[Model Analyzer] Starting a Triton Server using docker
[Model Analyzer] No checkpoint file found, starting a fresh run.
[Model Analyzer] Profiling server only metrics...
[Model Analyzer]
[Model Analyzer] Creating model config: add_sub_config_default
[Model Analyzer]
[Model Analyzer] Model add_sub_config_default load failed: [StatusCode.INTERNAL] failed to load 'add_sub_config_default', failed to poll from model repository
[Model Analyzer]
[Model Analyzer] Creating model config: add_sub_config_0
[Model Analyzer]   Setting instance_group to [{'count': 1, 'kind': 'KIND_GPU'}]
[Model Analyzer]   Setting max_batch_size to 1
[Model Analyzer]   Enabling dynamic_batching
[Model Analyzer]
[Model Analyzer] Model add_sub_config_0 load failed: [StatusCode.INTERNAL] failed to load 'add_sub_config_0', failed to poll from model repository
[Model Analyzer]
[Model Analyzer] Creating model config: add_sub_config_1
[Model Analyzer]   Setting instance_group to [{'count': 2, 'kind': 'KIND_GPU'}]
[Model Analyzer]   Setting max_batch_size to 1
[Model Analyzer]   Enabling dynamic_batching
[Model Analyzer]
[Model Analyzer] Model add_sub_config_1 load failed: [StatusCode.INTERNAL] failed to load 'add_sub_config_1', failed to poll from model repository
[Model Analyzer] Saved checkpoint to /workspace/checkpoints/0.ckpt
[Model Analyzer] Profile complete. Profiled 0 configurations for models: []
[Model Analyzer]
[Model Analyzer] WARNING: Inference output field "perf_throughput", has no data
[Model Analyzer] WARNING: Inference output field "perf_latency_p99", has no data
[Model Analyzer] Exporting server only metrics to /profile_results/results/metrics-server-only.csv
[Model Analyzer] WARNING: Requested top 3 configs, but none satisfied constraints. Showing available constraint failing configs for this model.
[Model Analyzer] WARNING: Requested top 3 configs, but found only 0. Showing all available configs for this model.
[Model Analyzer] WARNING: Requested top 3 configs, but none satisfied constraints. Showing available constraint failing configs for this model.
[Model Analyzer] WARNING: Requested top 3 configs, but found only 0. Showing all available configs for this model.
[Model Analyzer] WARNING: Requested top 3 configs, but none satisfied constraints. Showing available constraint failing configs for this model.
[Model Analyzer] WARNING: Requested top 3 configs, but found only 0. Showing all available configs for this model.
[Model Analyzer] WARNING: No data found for model add_sub, skipping export summary.
[Model Analyzer] WARNING: Requested top 3 configs, but none satisfied constraints. Showing available constraint failing configs for this model.
[Model Analyzer] WARNING: Requested top 3 configs, but found only 0. Showing all available configs for this model.
[Model Analyzer] To generate detailed reports for the 0 best add_sub configurations, run model-analyzer report --report-model-configs  --export-path /profile_results

See the bullet at the end of step 2:
Important: You must ensure the absolutes paths are identical on both sides of the mounts (or else Tritonserver cannot load the model)
So, instead of linking in like this: -v D:/triton-inference-server/model_analyzer/model_out:/model_out
You need to link in directories with the full path like this: -v D:/triton-inference-server/model_analyzer/model_out:/triton-inference-server/model_analyzer/model_out

I was able to resolve the issue
it was not obvious to me that the output model directory should not exist on the host
Here is a similar question
https://github.com/triton-inference-server/model_analyzer/issues/120
Here is an example of a correct docker command
docker run -it --rm --gpus all -v //var/run/docker.sock:/var/run/docker.sock -v D:/triton-inference-server/model_repository:/models -v /model_out:/model_out -v D:/triton-inference-server/model_analyzer/profile_results:/profile_results --net=host nvcr.io/nvidia/tritonserver:23.03-py3-sdk


Upgrade cdock to v8.3

It is so satisfying to see things getting moved off of SourceForge :smile:

Thank you for the contribution. It was merged directly as 5ffbdc7eec3befe4301c68e60607a8e31f76f967 to keep commit history cleaner. Your contribution is still credited to you.


Don't squash path dependencies with same package name

Fixes #13862
Dependencies with same package name in the Cargo.lock was squashed in EncodableResolve::into_resolve().
e.g. In the problem reproduction repo's Cargo.lock, there are two entries:
[[package]]
name = "once_cell"
version = "0.1.0"

[[package]]
name = "once_cell"
version = "1.19.0"

However, they were squashed in build_path_deps(), then we endup getting two package ids with same path like this:
PackageId { name: "once_cell", version: "0.1.0", source: "pwd/vendor/once_cell_1_19" }
PackageId { name: "once_cell", version: "1.19.0", source: "pwd/vendor/once_cell_1_19" }

This package version inconsistency triggers patch update introduced in https://github.com/rust-lang/cargo/pull/8248 everytime you compile this crate.

Note: I just did a quick scan of the issue (and commit structure).  I've not looked at the test or code change in detail yet

It seems that CI failure is caused by check-cfg https://github.com/rust-lang/cargo/actions/runs/8964218728/job/24615675343?pr=13863
Related: https://github.com/rust-lang/cargo/pull/13571

ping @weihanglo

:umbrella: The latest upstream changes (presumably #13931) made this pull request unmergeable. Please resolve the merge conflicts.

Sorry for the late reply. Thought epage was on it. Feel free to open a new one whenever ready.


Neocities

HI - Great App, thanks for the job !
I would like to ask if there is a way to use cms.js without htaccess/apache, because i would like to use it with a free neocities.org account.
Don't know if neocities use apache, but if they do, with a supporter account we can upload restricted files maybe like htaccess.
Cheers - nibreh

If you're looking at a supporter account, wouldn't it just be better to sign up for a normal host? For example, Cloudways  has $5 bundles.

Not sure if this is still relevant. Going to close for now.


Correction for the #35115 issue

Correction to the link in cross-rg-deployment

@omiossec : Thanks for your contribution! The author(s) have been notified to review your proposed change.

thanks for catching this!

Interpreting @JnHs comment as a sign-off (and it looks good based on context); merging.


Remove empty language files and copy script

Minecraft already defaults to English (en_us) if the translation key has no translation. Therefore having copies of the language file is unnecessary, makes the file size larger (though not the greatest contributor), makes it more difficult to see what is and isn't translated and makes it easy to forget to move changes on en_us to other files.
This PR removes the unnecessary lang files (checked contents were equals and there's been no PRs for them) and the copy script (that was actually being packaged in the jar too although never used from it).

I don't know how i didn't know this
This looks good to me 👍
Thank you :D


Check native-image tool compatibility with JWT package

Description:

$Subject

Describe your task(s)

[x] List the third party libraries used in jwt package
[x] Analyze the code base regarding the Java dynamic features
[ ] Test jwt BBE with native image
[x] Test jwt module bal tests with native image
[ ] Test performance using a load-test (Optional)
[x] Create a PR to add any native image configurations and update dependency versions

Related Issue:
Check GraalVM native-image tool compatibility #3315

BBEs are coupled with HTTP/WebSocket/GraphQL/gRPC. So these BBEs will be tested when the testing is done for these other modules


Popup a dialog when user clicks "x" to exit the tool

When user closes the application by clicking cross(X) button on top right, pop up a dialog
"Do you want to exit the application?"
Add one checkbox also , "I understand, Don't ask again".
If this checkbox is checked, never show this dialog again.

If the user wants to close the dialog box instead of clicking "ok"  ... If user clicks on the cancel button or on cross button ... Then also the tool is closing.

Fixed the bug on commit number :-> a138754c7f8cef56a464dd9cfcf75e9d413bad11


add troubleshooting information to the overview doc

Added troubleshooting section to the BindingsOverview doc.

CosmosDb trigger has a MS doc for troubleshooting common issues: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/troubleshoot-changefeed-functions. Maybe we can create a similar doc.


Outposts

Must display all outposts and their names
Ideally works with more/less outposts, in case some are added/removed

There are only 15 outposts atm so we can just hard code it.

I will do this since it actually has API support.

@ItsNeil17 can I have your opinion on this? My problem is I can't center the names properly since their length is variable.

@Owen-Griffin I had something else in mind regarding this. I thought of an idea where the name would be at the top, with a capture button below it. I have attached a screenshot below for reference. Ofcourse it won't be 1:1 but I would want something like this.

@ItsNeil17 can I have your opinion on this? My problem is I can't center the names properly since their length is variable.

Also length would be 25 characters max, so if we're going forward with the idea above, we just allow extra space for 25 chars.

Alright, I'll look at implementing that.

okay so its 300 lines of code, but it works.


Decided what to do with ProtobufRawMessage

It seems to currently have a bunch of TODOs.  So should it be completed, or should something else take it's place?
If we have a CodedInputStream type class, the same type of parsing is pretty easy to implement oneself.
Likewise, if a developer did a proto2 syntax file with a message having no fields, it would work to parse everything into the unknowns and that could be used for the same type of functionality.
Anyway, before it becomes part of a 1.0 release that has to be maintained, decide what it should be.

This was motivated by a particular use case that is extremely memory-constrained and has to handle a very large number of message types.  An initial implementation with generated code was far too large, a subsequent attempt using C++ descriptor-based dynamic messages was also a disaster due to the overhead for expanding even a single descriptor at a time.  Stream-based parsing might work, but in this particular use case the message is already a block of data in memory so we might be able to do slightly better.
Deleting it for 1.0 would be entirely reasonable.

The memory comment is interesting; since it seems to still keep everything in a map in memory. I guess the difference is the submessages (if they aren't done as a group), they would be length delimited blobs, so I guess that's the memory expansion you mention.  The empty message approach should model that memory footprint.

since it seems to still keep everything in a map in memory

That's a bug, actually.


Adding custom formatting options doesn't work in v4.0.4 and above

I recently upgraded to v4.0.4 of powerbi-visuals-tool  from 3.1.18. Previously, I followed the tutorial to Add Formatting options to my custom visual and it worked fine.
After the update, my custom visual loads fine in the developer more and with the package .pbiviz but the custom settings don't show up in the format pane. On debugging the issue, I found it fails to create the VisualSettings object and fails here: https://github.com/microsoft/powerbi-visuals-utils-dataviewutils/blob/master/src/dataViewObjectsParser.ts#L47
with the below callstack:-
TypeError: Class constructor DataViewObjectsParser cannot be invoked without 'new'
at new VisualSettings (:740:47)
at Function.getDefault (:16518:16)
at Function.parse (:16527:41)
at Visual.update (:822:51)
at e.update (https://app.powerbi.com/13.0.18129.59/scripts/customVisualsHost.bundle.min.js:19:130291)
at https://app.powerbi.com/13.0.18129.59/scripts/customVisualsHost.bundle.min.js:19:187695
at t.trackVisualTime (https://app.powerbi.com/13.0.18129.59/scripts/customVisualsHost.bundle.min.js:19:190879)
at t.update (https://app.powerbi.com/13.0.18129.59/scripts/customVisualsHost.bundle.min.js:19:187644)
at o. (https://app.powerbi.com/13.0.18129.59/scripts/customVisualsHost.bundle.min.js:19:167008)
at https://app.powerbi.com/13.0.18129.59/scripts/customVisualsHost.bundle.min.js:19:1671
I downgraded to 3.1.18 again, and it started to work again.
Please help resolve this issue for v4.0.4

Env details:
node- v16.5.0
powerbi-visuals-api- 3.8.0

Verified that the formatting options are functional till v4.0.2

Could you, please, try it on the new version of the tools, since I wasn't able to reproduce it on my end?


Fix the frame rate in ivf

Some demuxers will cry foul if the framerate is 0/60.

Yeah I had to do this for my live stream but forgot to pr it.


Fatal Error

Error when trying to generate anything using pretrained CKPT on V2 768. I was able to run them earlier today on the 768 version of V2.
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
FATAL: this function is for sm80, but was built for sm750
Colab paid products - Cancel contracts here
You are not subscribed. Learn more.
Available: 73.76 compute units
Usage rate: approximately 0 per hour
You have 0 active sessions.
Want more memory and disk space? Upgrade to Colab Pro
Not connected to runtime.

Ok! No worries thanks for the heads up
On Wed, Nov 30, 2022 at 9:46 PM, Ben @.***> wrote:

the colab will be ready in less than an hour, it's not stable at the moment
—
Reply to this email directly, view it on GitHub
https://github.com/TheLastBen/fast-stable-diffusion/issues/779#issuecomment-1333080773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4A3AP6BDBKLVLRTE6C5ZWDWLAGPJANCNFSM6AAAAAASQI5WGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Error messages on key claim and key upload

Currently the code is issuing the same error message for key claim errors:
https://github.com/cds-snc/covid-alert-app/blob/31dd079e4069828bbd14ce5090bd3345ca148322/src/screens/datasharing/DataSharing.tsx#L26-L28
and similar for upload errors
https://github.com/cds-snc/covid-alert-app/blob/31dd079e4069828bbd14ce5090bd3345ca148322/src/screens/datasharing/DataSharing.tsx#L33-L36
This does not take into account some of the more common potential scenarios such as not being able to reach the server because of network issues, expired keys on the server, or potentially other edge cases.
The server will return a number of different error codes based on various scenarios:
https://github.com/cds-snc/covid-alert-app/blob/31dd079e4069828bbd14ce5090bd3345ca148322/src/services/BackendService/covidshield/covidshield.proto#L29-L35
and
https://github.com/cds-snc/covid-alert-app/blob/31dd079e4069828bbd14ce5090bd3345ca148322/src/services/BackendService/covidshield/covidshield.proto#L77-L94
that could be used for more informative error codes.

cc: @smcmurtry @katewilhelm
Let's get some 👀  on this when we can - more granular error messages :)

At a minimum, heads up, server team is setting an SLO of 80% uptime. Y'all have been warned. ;)


Some functionality broken in Firefox

Could you test the bookmarklet in Firefox? For me, the following controls do not work:

Contrast
Link text
Labels

and these errors appear in the console:

Seconded, Firefox 38.0 on Linux here.
Though only having problems with the Contrast control, the Link text and Labels seem to be working.

Yep, I can confirm this one. It's failing to compute the background color for some elements - will investigate.

+1 Contrast fails on the demo for me in latest FIrefox on windows

Might be prevalent in IE11 as well based on twitter feedback. I'll dive in today.

enjoy! :)
Steve Lee
OpenDirective http://opendirective.com
On 2 July 2015 at 15:08, Jordan Scales<EMAIL_ADDRESS>wrote:

Might be prevalent in IE11 as well based on twitter feedback. I'll dive in
today.
—
Reply to this email directly or view it on GitHub
https://github.com/Khan/tota11y/issues/32#issuecomment-118045346.

Okay I'm going to begin opening up separate issues and tracking them there. We've got a few separate issues. Not closing this right away.

@simevidas Hey Sam, mind showing me an example for the link text and labels plugins failing? I suspect that it's not a Firefox issue but something along the lines of #35.
Contrast is definitely FF, though, and I've got #37 to track it.

@jdan Link text and Labels works now in Firefox/Windows for me. 😄 (I had to re-install the bookmarklet. )

@simevidas not 100% on what changed, but if it pops up again and isn't related to #35 let me know :)
Going to close this now in favor of #37. Thanks again for reporting.

9ccac407f06c509d21ada463dac30a71d5d0c52d has the contrast fix for those curious :)


Support non-hashicorp authors

Add new AUTHOR argument to support non-hashicorp provider authors
Re-order input arguments to make AUTHOR the second argument
Fix unzip command to find docs if they do not reside in website/docs

Tested locally with the following providers:

AWS (no arguments)
Snowflake (EDITOR=glow terradoc snowflake Snowflake-Labs)
Databricks (EDITOR=glow terradoc databricks databricks master)

Love it.
Thank you!


[Directline] Very slow to establish websocket

Our customers are having intermittent issues sending messages to their bots. This normally begins with a long initial connection.
Response Time: around  80,000 ms
GET wss://directline.botframework.com/v3/directline/conversations/5GvoKcen2xv4tLBWLYZHS5-0/stream
Conversation ID: 5GvoKcen2xv4tLBWLYZHS5-0
x-ms-request-id |e41973cbdf82584f9d3d238b6fa4641f.77d6027c_
Timestamp: 2019-11-20T03:53:14.638Z

Are your bots deployed on Azure? If so, are they set to 'always on'?

Assigning to @mickeydjw for triage. This will be the classic, non-duplexed, WebSocket on DirectLine SaaS. I took a quick look in our logs and couldn't find any tracing for the conversation mentioned above.

Are your bots deployed on Azure? If so, are they set to 'always on'?

Yes, deployed on Azure and set to 'always on'. We don't see this long request in our logs

Is this issue still occurring for your customers?

Hi @Crazedpeanut are you still experiencing this problem? We would like to take a look but have not been able to find details about the one example you sent. It has also been removed from our logs so we would need a more recent instance to investigate further. A conversation ID or a URL like you sent in your first post should be sufficient.

Closing due to lack of response


Update 0103-oracle-hex-boosting.md

Made small fixes to the table.
Please wait to merge this PR until after the MWG session on 1/11/2024

@abhay not yet, will DM you when it’s ready. Sorry for the delay.


How to Create Ionic Page in a library?

Hi there!
When I try to create a page using nx generate @nxtend/ionic-angular:page it wants to create the page in the apps folder.
I thought that everything in NX should be in libraries.  How do you create a page in a library?
Thanks
-Page

I've had the same issue and I have to do something like this.
I go to the VS Code file explorer and Copy Relative Path of the lib in which I want the new page to exist.

This gets it close enough. I still usually move the contents of the created folder into its parent because there's no --flat option, and then delete the empty folder.

Thanks!  I ended up creating a library and then a page or component using the your path trick :)

Glad it helped, but you could still leave the issue open because it would be nice if the generator worked a bit better.


EurekaBase potential for NullReferenceException when no instance id exists

If the applications XML contains an application without an instanceId element, Steeltoe correctly has an instanceId of null, however this causes a problem as the Applications.cs file (line 147)
instances[info.InstanceId] = info;
this code will attempt to add a key to the ConcurrenctDictionary (instances) which is null. This in turn causes an exception. The result being that this exception causes other application objects with valid instanceId's to not get loaded/registered with Steeltoe and hence trying to get them results in a null return value.
I raised this issue previous (https://github.com/SteeltoeOSS/steeltoe/issues/13) and it's not related to the fix highlighted within that thread.
I have a fork with a commit and test for this, will raise a PR if you wish to accept or it will highlight the issue hopefully.

Raised PR, feel free to ignore/reject it's more to demonstrate the problem https://github.com/SteeltoeOSS/steeltoe/pull/177


Made Logo for rollcall.

Issue #1

@janvi01 , can we use a different color and for automatic attendance part , either keep all initials capital or small

Please check now, is it fine?

yes @janvi01  but please follow pr guidelines mentioned in discord channel of rollcall


Saleor 2.0 and docs

Hi,
I was wondering if there was any plan into updating the docs as Saleor 2.0 was updated.
First of all: the logo.
Then, maybe adding a bit of CSS to remove the hard blue with something else, same with the dark area if needed.
Is there any other change we should/ could do to make the docs fit with the 2.0 or anything planned?

Sure, docs styling should be adjusted accordingly, we've discussed this internally, but not sure if we already have a vision on how we want them to look like, as we wanted to do something more than just a simple color change. Sphinx gives us lots of possibilities in here.

Yes, we're definitely planning a larger docs overhaul. Saleor's lead, @maarcingebala, is still in SF after attending the GraphQL Summit so expect the pace to pick up again next week.

Alright, thanks for the info! Sounds great.
I will close this as it's already something that is planned.


Bug processing private fields in hammerhead

What is your Scenario?
Testing an application containing a class with private fields.
What is the Current behavior?
The browser console gives the following result of the application when it is launched from TestCafe:

What is the Expected behavior?
The same application run without TestCafe gives a different result:

What is your public website URL? (or attach your complete example)
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
</head>
<body>
    <script>
        function fn (resolve) {
            setTimeout(resolve, 400, 42);
        }

        class CL {
            static #promise;

            static async #fn1 () {
                const value = await this.#promise;

                console.log(`should be eql 42: ${value}`);
            }

            static fn2 () {
                this.#promise = new Promise(resolve => fn(resolve));

                this.#fn1();
            }
        }

        CL.fn2();
    </script>
</body>
</html>

What is your TestCafe test code?
import { Selector } from 'testcafe';

fixture `New Fixture`
    .page `path/to/app`;

test(`New Test`, async t => {
    await t.debug();
});

TestCafe version
1.20.1-rc.2
Command-line arguments
testcafe chrome test.js

Hi folks,
TestCafe runs tests using the URL-rewritten proxy.
This approach is good. However, there is a way to improve the stability and speed of test execution - the native browser automation API.
We have a test execution mode uses native browser automation - we call it the 'Proxyless' mode.
In 'Proxyless' mode, a few issues are already fixed.
By the way, this issue was also fixed in 'Proxyless' mode.
Try running your tests in 'Proxyless' mode and let us know the results.
This option is available in all interfaces:
// Command-line
testcafe chrome tests --experimental-proxyless

// Programmatic
testcafe
    .createRunner
	.src('tests')
	.browsers('chrome')
	.run({ experimentalProxyless: true });

// Configuration file
{
   "experimentalProxyless": "true"
}

Note that at present it is an experimental mode.
Also, the 'Proxyless' mode is implemented only in Google Chrome. It will not work correctly if you run tests in a non-Chrome browser or in a combination of other browsers.

Fixed in https://github.com/DevExpress/testcafe-hammerhead/pull/2883


Spec: KubeVirt Integration

Overview
I would like to explore the integration of NSM with KubeVirt. In addition to VIM integration, being able to take advantage of KubeVirt's ability to have K8s schedule VMs while NSM provides a robust L2/L3 networking model leads to strong long term potential.
NSM + KubeVirt would allow for the use of the VM resource type, enabling declaratively scheduled VMs in K8s, as well as mitigate some of the restrictions the VM currently inherits through the K8s networking model.
The long term implication being that K8s not only handles containers for end-users but also VMs, potentially replacing the need for additional VIMs and their 3rd party networking intermediaries such as NSX/Neutron/etc.
Link to the Google Docs document
Place holder: https://docs.google.com/document/d/1V2IF7FWVT2BitWG5e9PWVaj1pUCwsn3XHYONoKxbXFk/edit
References
https://github.com/kubevirt/kubevirt
https://github.com/kubevirt/ovs-cni

I can see vhost-user sitting behind the corner here :)

I shouldn't have called out KubeVirt specifically to be honest. The spec is
more specifically looking to explore K8s scheduled VMs with NSM plumbed
networking. KubeVirt was just the plugin that first jumped into my mind.
On Thu, Mar 7, 2019 at 11:11 AM Nikolay Nikolaev<EMAIL_ADDRESS>wrote:

I can see vhost-user
http://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/ sitting
behind the corner here :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/networkservicemesh/networkservicemesh/issues/815#issuecomment-470634344,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGsP2-NvTbxbcVApPUyd-3svcwcxw82Qks5vUVY1gaJpZM4bjp-t
.

@nerdengineering Do you want to preserve this against the merciless onslaught of stale-bot? :)

Yes, I'm sorry for the delay on this, just a lot of other stuff going on. I'll begin work on this once I tie up a few other things with Frederick.

@nerdengineering All good, just didn't want stale-bot reaping it :)


Unable to make delegation tx in evmos via Ledger

Error: Can't sign cosmos sign doc by ethereum app on ledger (app.evmos.org)


dracula: Add bright colors

This change adds some of the bright colors for the Dracula theme so that they're not they aren't the same shades.
These values are copied from the Base24 Dracula scheme at https://github.com/tinted-theming/schemes/blob/spec-0.11/base24/dracula.yaml
Doesn't rebuild the scripts at all, as I didn't know how to do such a thing.

Reviewing the official Dracula page, I see that the current theme in Gogh is quite different from their official version.
https://draculatheme.com/gnome-terminal
https://github.com/dracula/gnome-terminal/blob/master/colors/Dracula/palette
I believe it would be best if it aligned more closely with the original theme.
What do you think?

https://github.com/Gogh-Co/Gogh/pull/478

Thanks so much for pushing this forwards, @Mgldvd :+1: Much better than what it was before.


Add service model for AnsibleTower ConfigurationScript

Add the missing service model for AnsibleTower ConfiguraitonScript introduced with #7943.
@gmcculloug @bdunne please review

@bzwei Can you also add the missing service_model for ManageIQ::Providers::ConfigurationManager::InventoryRootGroup.

Thanks @bzwei  👍


Only prints once

After successfully printing a receipt once, subsequent attempts to print again are unsuccessful.

@eric-sison did you use the latest version?

The same thing happens with the example provided. I am using epson TM-P20 printer

hi, same here
1st print success
2nd become

3rd print success again
any one solve it?
this is my code
if (macAddredd != null) {
/// do print
await controller?.print(address: macAddredd, keepConnected: true).then(
(value) async {
List intList = [0x1D, 0x56, 0x00];
Uint8List cutCommand = Uint8List.fromList(intList);
FlutterBluetoothPrinter.printBytes(address: macAddredd!, data: cutCommand, keepConnected: true).then(
(value1) async {
await FlutterBluetoothPrinter.disconnect(macAddredd!);
},
);
},
);
}


HTTPCLIENT-2305: SSLConnectionSocketFactory allows socket.connect to be decorated

https://issues.apache.org/jira/browse/HTTPCLIENT-2305

Thanks for the review, @ok2c!


update the badges link in README.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
24 unchanged lines in 9 files lost coverage.
Overall coverage increased (+0.05%) to 66.865%

Files with Coverage Reduction
New Missed Lines
%

com/baidu/bifromq/basecluster/memberlist/AutoSeeder.java
1
84.43%

com/baidu/bifromq/inbox/server/InboxService.java
2
79.68%

com/baidu/bifromq/basecluster/fd/FailureDetector.java
2
89.8%

com/baidu/bifromq/basekv/raft/RaftNodeStateLeader.java
2
87.0%

com/baidu/bifromq/basekv/client/scheduler/BatchQueryCall.java
2
71.76%

com/baidu/bifromq/basekv/store/range/KVRangeFSM.java
2
78.57%

com/baidu/bifromq/basekv/raft/exception/LeaderTransferException.java
3
76.92%

com/baidu/bifromq/basecluster/transport/TCPTransport.java
4
86.93%

com/baidu/bifromq/basekv/raft/RaftNodeState.java
6
91.3%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
20897

Relevant Lines:
30415

💛  - Coveralls


Update to a comma-separated list of mount points

Switch to using a comma-separated list of mount points instead of a List trait (which is not very practical).
This means that instead of doing:
--XeusAddon.mounts directory1:drive1 --XeusAddon.mounts directory2:drive2

One can do:
--XeusAddon.mounts directory1:drive1,directory2:drive2

Lots of whitespaces changes, it's easier to review with https://github.com/jupyterlite/xeus/pull/19/files?diff=split&w=1

thanks!


Does RedissonRedLock support Redis cluster Master/Slave mode?

In this issuehttps://github.com/redisson/redisson/issues/1333#issuecomment-371817371  I found that RedissonRedLock supports Redis cluster mode. In the Redlock algorithm https://redis.io/topics/distlock,I don't think it supports  Master/Slave mode.The description is:

In the distributed version of the algorithm we assume we have N Redis masters. Those nodes are totally independent, so we don’t use replication or any other implicit coordination system.

For example:
The Redis cluster 1 is as follows:
Master1 Slave1
Master2 Slave2
Master3 Slave3
The Redis cluster 2 is as follows:
Master1
Master2
Master3
I am troubled. Does it support  type of  Redis cluster 1 ?
.If it supports then how do I add a configuration, whether the master and slave are added or only the master configuration is added.
For example :
Add as type1
Config config = new Config();
config.useClusterServers().addNodeAddress(Master1, Master2,Master3, Slave1,Slave2, Slave3);
RedissonClient redisson = Redisson.create(config);
RLock lock1 = redisson.getLock(lockName + "1");
RLock lock2 = redisson.getLock(lockName + "2");
RLock lock3 = redisson.getLock(lockName + "3");
RLock lock4 = redisson.getLock(lockName + "4");
RLock lock5 = redisson.getLock(lockName + "5");
RLock lock6 = redisson.getLock(lockName + "6");

Add as type2
Config config = new Config();
config.useClusterServers().addNodeAddress(Master1, Master2,Master3);
RedissonClient redisson = Redisson.create(config);
RLock lock1 = redisson.getLock(lockName + "1");
RLock lock2 = redisson.getLock(lockName + "2");
RLock lock3 = redisson.getLock(lockName + "3");

Add as type3
Config config = new Config();
config.useClusterServers().addNodeAddress(Master1, Master2,Master3, Slave1,Slave2, Slave3);
RedissonClient redisson = Redisson.create(config);
RLock lock1 = redisson.getLock(lockName + "1");
RLock lock2 = redisson.getLock(lockName + "2");
RLock lock3 = redisson.getLock(lockName + "3");

Which type should I choose,or they are all wrong?
Redis version
3.x

I think they all right, providing the naming scheme (lockName + sequence) is able to distribute the lock evenly one each node.

@jackygurui thank you  I will  try it.

@faceany
In your examples locks won't be spread by nodes automatically. It's up to developer to select proper name located at concrete Redis node.

@faceany i think if the node(msater) has slave, and the master is hung, the slave will be changed to master .
And, what is the result of the type1, type2 and type3

RLock lock1 = redisson.getLock(lockName + "1");
RLock lock2 = redisson.getLock(lockName + "2");
RLock lock3 = redisson.getLock(lockName + "3");
can not ensure  lock1、lock2、lock3  having lock of  Master1 、Master2 、Master3

You can use predetermined value in the key name and use {} to force the key slot calculation onto your desired node.


Problem Installing, unrecognized command line option ‘-fstack-protector-strong’

Hi,
Trying to install nxppy on Raspberry 2 this error occurs:
All goes well untill :
running build_ext
building 'nxppy' extension
creating build
creating build/temp.linux-armv7l-2.7
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Ineard-explorenfc-0.9/nxprdlib/types -Ineard-explorenfc-0.9/nxprdlib/intfs -I/usr/include/python2.7 -c Mifare.c -o build/temp.linux-armv7l-2.7/Mifare.o -O1
cc1: error: unrecognized command line option ‘-fstack-protector-strong’
error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

I did some research but can't find anything.
I need some help.
Thanks in advance !

It seems : arm-linux-gnueabihf-gcc is an gcc 4.9 option.
And my gcc was 4.8 version. I updated it but I got still that error

Which OS distribution and version are you using?  I'll see if I can
reproduce this.  That part of the command line is put together by the
Python distutils, so there may be some version incompatibility there.
Also, which version of python?
On Wed, Apr 27, 2016 at 7:44 AM matthieuvisian<EMAIL_ADDRESS>wrote:

It seems : arm-linux-gnueabihf-gcc is an gcc 4.9 option.
And my gcc was 4.8 version. I updated it but I got still that error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/svvitale/nxppy/issues/34#issuecomment-215087539

Hi again,
I'm using Raspberry PI 2 with the latest version of Jessie.
Python version : 2.7.9

This should be resolved in the latest release (1.4.0).  Closing this issue for now, please re-open if you still encounter issues after upgrading.  Note that I haven't done any recent testing on Wheezy, only Jessie.


Bug:  useApp () not working

Current Behavior
Hi,
I am trying to use useApp () hook, but it is throwing up an exception, not sure if I am using it right,  just checked the documentation below:
https://reactpixi.org/hooks#useapp
invariant.js:24 Uncaught Invariant Violation: No Context found with PIXI.Application. Make sure to wrap component with AppProvider
at invariant (http://localhost:3004/static/js/bundle.js:484:15)
at useApp (http://localhost:3004/static/js/bundle.js:21143:3)
at MyComponent (http://localhost:3004/static/js/bundle.js:115:66)
at renderWithHooks (http://localhost:3004/static/js/bundle.js:44313:22)
at mountIndeterminateComponent (http://localhost:3004/static/js/bundle.js:47599:17)
at beginWork (http://localhost:3004/static/js/bundle.js:48895:20)
at HTMLUnknownElement.callCallback (http://localhost:3004/static/js/bundle.js:33905:18)
at Object.invokeGuardedCallbackDev (http://localhost:3004/static/js/bundle.js:33949:20)
at invokeGuardedCallback (http://localhost:3004/static/js/bundle.js:34006:35)
at beginWork$1 (http://localhost:3004/static/js/bundle.js:53880:11)
`
Expected Behavior
Use app constant to access the application
Steps to Reproduce
Execute next chunk of code:
`
import { BlurFilter } from 'pixi.js';
import { Stage, Container, Sprite, Text, useApp } from '@pixi/react';
import { useMemo } from 'react';
const MyComponent = () =>
{
const blurFilter = useMemo(() => new BlurFilter(4), []);
const app  = useApp ();
return (

<Sprite
image="https://pixijs.io/pixi-react/img/bunny.png"
x={400}
y={270}
anchor={{ x: 0.5, y: 0.5 }}
/>
  <Container x={400} y={330}>
    <Text text="Hello World" anchor={{ x: 0.5, y: 0.5 }} filters={[blurFilter]} />
  </Container>
</Stage>

);
};
export  default MyComponent;`
`
Environment

@pixi/react version: 7.0.1
pixi.js version: 7.1.0
React version: 18.0.0
ReactDOM version: 18.0.0
Browser & Version: * Chrome*

Possible Solution
No response
Additional Information
No response

useApp is a hook which must be called inside an AppProvider. You can either create this yourself, or use the default one provided through the Stage component. This means you need a Stage component around MyComponent.

@AndreasWintherMoen , thanks a lot for helping with it.
Yep, I was missing the App provider in App.tsx:
`
import React, { useEffect, useRef } from 'react';
import * as PIXI from 'pixi.js';
import ReactPixi, { PixiRef, useTick, useApp, AppProvider } from '@pixi/react';
import GameBoard from './components/Board/Game';
const pixiApp = new PIXI.Application({});
function App() {
return (

);
}
export default App;
`

Probably this is an opportunity to improve documentation.


exposed IsEqualCompressingWhiteSpace.string in protected getString in…

… order to facilitate use in subclasses
#198

@krichter722 i'm happy for this to be merged, sorry it was a blanket update on all tickets
merge of #198


check if patched

check if evenlet or gevent are installed and if socket / everything is monkey patched. If so, raise an error

Won't work with our test suite that uses eventlet. Maybe it is not that bad?


Write the "Ownership" concept

Official docs:
https://book.cairo-lang.org/ch04-00-understanding-ownership.html

Exercism Concepts docs:
https://exercism.org/docs/building/tracks/concepts

Hi can I take this?

@Falilah sure thing! Ping if you need any guidance

That is correct!


i686-unknown-uefi has started failing

With latest nightly, compilation is failing with:
  = note: rust-lld: error: /safeseh: /tmp/rustcsn785E/symbols.o is not compatible with SEH
          rust-lld: warning: section name .debug_frame is longer than 8 characters and will use a non-standard string table

(from https://github.com/rust-osdev/uefi-rs/runs/6198792816?check_suite_focus=true)

I'm running cargo-bisect-rustc now to find where it failed...

Filed a rust bug: https://github.com/rust-lang/rust/issues/96498

Rust bug has been fixed, and CI is passing again.


Use Rsync Job instead of Pod

Use Job instead of bare Pods for Rsync to allow easy re-scheduling in case of node failures.

I am not sure about using any sort of controller to run the pods instead of pvc-migrate itself managing the pod. The reason is as follows:

One of the sub-goals of pvc-migrate was to weed out the infrastructure-related problems that were hidden while migrating with CAM. In the customer scenario yesterday, there were multiple infrastructure problems identified, one the node was not ready, another beint the kubelet was unable to attach the volumes to the pod (OCS). Managing the rsync pod with a higher level resource IMO leads to some sort of indeterministic state with questions like what would happen if the PVCs are bound to the old pod and new pod at the same time? Would it mask a few of these errors by simply creating a new copy of the pod and attempting to copy the data on a different pod?

One of the most attractive features of a replication controller is that if one pod is failing and a new pod is created, we should transparently see the traffic being served from the new pod. However, in this case, I am assuming the client side rsync is a single blocking call to destination pod. Even if the replication controller does create new pod, the hand off from old to new pod will not be transparent because of the long blocking rsync call. Theoretically, it will fail the current run of the ansible playbook and we lose this benefit as well

There were some concerns with deployment not being able to give us the necessary root level permissions to make sure that the exact file permissions from the source are being preserved on the destination in the past. I am not sure if the same would apply for Jobs, but that was one reason why #49 was closed.


Canonical homophone is always the longest word

https://github.com/knausj85/knausj_talon/blob/ffeaa0269487510e99db11e7d8bcefe05157b135/code/homophones.py#L38
Per discussion in #help, phones is picking the longest word of a set as the canonical. Proposed alteration is canonical_list.append(words[0]) and then sorting the sets of homophones by frequency and possibly length.
https://talonvoice.slack.com/archives/C7ENXA7C4/p1609792196126300

It seems like the reason this matters is that the canonical versions of each group get turned into phones $WORD commands, so it's important that the canonical words be ones that are recognised well, eg. "bite" is better recognised than "bight".
I wonder if there's some reason why the canonical one is chosen to be longest?

It seems like the reason this matters is that the canonical versions of each group get turned into phones $WORD commands, so it's important that the canonical words be ones that are recognised well, eg. "bite" is better recognised than "bight".
I wonder if there's some reason why the canonical one is chosen to be longest?

Something I was thinking about lately is if it would be good to have the homophones handler rewrite the csv entry after a selection is made, so the default match becomes whatever you last selected based on the assumption that it's what you frequently want. but the above has me wondering if we should write modified homophone lists to some secondary copy, so we can also track frequencies of all words in a per-user json file. then populate the selector window and default word used by talon (whenever a homophone is encountered) based on the content of json list, but still have the static list for initial distribution and populating the phones command with the canonical word. this may be suited for another issue though

Something I was thinking about lately is if it would be good to have the homophones handler rewrite the csv entry after a selection is made, so the default match becomes whatever you last selected based on the assumption that it's what you frequently want. but the above has me wondering if we should write modified homophone lists to some secondary copy, so we can also track frequencies of all words in a per-user json file. then populate the selector window and default word used by talon (whenever a homophone is encountered) based on the content of json list, but still have the static list for initial distribution and populating the phones command with the canonical word. this may be suited for another issue though

In the chat there is a word frequency list we could probably use for one-off sorting of a default list.
Caveat: I made the case to get the issue documented, but I don't really use phones functionality myself.

In the chat there is a word frequency list we could probably use for one-off sorting of a default list.
Caveat: I made the case to get the issue documented, but I don't really use phones functionality myself.

The word frequency list is at https://bochs.info/~aegis/popular-words.txt (for future reference in case it leaves slack history)

This should be fixed by https://github.com/knausj85/knausj_talon/pull/318

This should be fixed by https://github.com/knausj85/knausj_talon/pull/318

I'm going to close this as resolved for now. The plan on dynamic updating of phones priority is cool, and probably best addressed as a new broader issue IMHO.

I'm going to close this as resolved for now. The plan on dynamic updating of phones priority is cool, and probably best addressed as a new broader issue IMHO.


Fix LLVM vs Apple LLVM version numbering confusion, for $avx512ifma

Apple LLVM has a different version numbering scheme than upstream LLVM.
That makes for quite a bit of confusion.
https://en.wikipedia.org/wiki/Xcode#Toolchain_versions to the rescue,
they have collected quite a lot of useful data.
This change is concentrated around the $avx512ifma flag
Fixes #16670 for the master branch

This is the upport of #19352

Hi I will help you with everything you need but you have to subscribe to
the youtube channel and I will fulfill all your requests
https://youtu.be/aIaqr4eq18g
Pada Jum, 7 Okt 2022, 4:41 PM Richard Levitte @.***>
menulis:

Apple LLVM has a different version numbering scheme than upstream LLVM.
That makes for quite a bit of confusion.
https://en.wikipedia.org/wiki/Xcode#Toolchain_versions to the rescue,
they have collected quite a lot of useful data.
This change is concentrated around the $avx512ifma flag
Fixes #16670 https://github.com/openssl/openssl/issues/16670 for the
master branch
You can view, comment on, or merge this pull request online at:
https://github.com/openssl/openssl/pull/19361
Commit Summary

7764c92
https://github.com/openssl/openssl/pull/19361/commits/7764c922f59d86ec880b90630368b7611fe542d0
Fix LLVM vs Apple LLVM version numbering confusion, for $avx512ifma

File Changes
(3 files https://github.com/openssl/openssl/pull/19361/files)

M crypto/bn/asm/rsaz-2k-avx512.pl
https://github.com/openssl/openssl/pull/19361/files#diff-90203a1cceab1d6702514e89cf15693ac434debe6ee9fe3564f3cb23a6ce5468
(13)
M crypto/bn/asm/rsaz-3k-avx512.pl
https://github.com/openssl/openssl/pull/19361/files#diff-6f3b139ebc5c1ffbc248f23182742743a913ab6b90bf7cfe12f425a5df9ba61e
(13)
M crypto/bn/asm/rsaz-4k-avx512.pl
https://github.com/openssl/openssl/pull/19361/files#diff-5102c0254e063ed1d0d21f044d3edc3d9684397c416184d085b4b770d6bf9c76
(13)

Patch Links:

https://github.com/openssl/openssl/pull/19361.patch
https://github.com/openssl/openssl/pull/19361.diff

—
Reply to this email directly, view it on GitHub
https://github.com/openssl/openssl/pull/19361, or unsubscribe
https://github.com/notifications/unsubscribe-auth/APESUCV65SWQTKWSFQMYY3LWB7OZ5ANCNFSM6AAAAAAQ7L562E
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This pull request is ready to merge

Merged.

@paulidale are you sure you've merged this? The tree was frozen before the release.
And rightly so I do not see the commit being pushed.

Unfortunately @levitte already deleted the branch so I am unable to reopen this.

No, the merge failed.  The frozen repo caught me out.  @levitte, can you undelete the branch please?

Branch is back.

Is this ready for merge?

Merged to master branch finally. Thank you.


chore: bdd-sbhg-1583399265 to 0.0.1

chore: Promote bdd-sbhg-1583399265 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Maya: Refactor to new publisher

Brief description
Refactor Maya to use the new publisher with new creators.
Description

[x] Legacy instance can be converted in UI using SubsetConvertorPlugin

[x] Fix support for old style "render" and "vrayscene" instance to the new per layer format.

[ ] Make Create Animation hidden to the user (should not create manually?)
[x] Correctly detect difference between 'creator_attributes' and 'instance_data' since both are "flattened" to the top node.

Additional info
Here's a fun little PR - I wonder at what amount of lines of code changed we'll end.
Screenshots
Publishing:

New pointcache instance in attribute editor:

New pointcache instance in channel box:

Testing notes:

Start Maya
Publish all the things!

I've converted almost all creator classes now - there were so many - it's crazy! :)
The Create Render and Create VRayScene ones will be a bit trickier since well, those creators have quite a lot of logic involved.

I have requested an early review of the PR.
The state is still early (do not use in production!) but it shows how conceptually the refactor works for the Creators. You should be able to publish a simple model or alike.
Would love to hear feedback on the:

code changes overall
how the creator is implemented

since a lot relies on the base 'MayaCreator' I think the plugin.py is likely most relevant to check. The individual creators usually are just refactored to match the new attribute definitions, etc. Nonetheless, please do a quick check on it.

would love a thorough review on how "Create Render" works, also see the discussion on Instance Splitting where I've shared more questions and details. I believe it's likely just 'plain wrong', some things that stand out in the changes:

the subset names are pretty hardcoded,
the instances can have asset/task changed, but really 'that should never be the case'.
The renderlayers now each have their own set of settings regarding e.g. the Primary Pool, Secondary Pool, etc. So it's not for the full render globals but per render instance.
The UX looks odd for the settings for renderlayers - things aren't organized logically.
It's a bit weird that removing a renderlayer instance removes all because it'd remove the single CreateRender instance.

Did some updates:

Host context is now retrieved/stored
Legacy instances can now be converted
Create workfile now uses new-style auto creator
Tested some more publishing, see top checklist.

Still some crucial input needed - so please do a code check.
Also need information on how to correctly name e.g. the subsets for CreateRender renderlayers.

@mkolar Any chance this can get a review on just the code? There's a lot of maya development and the longer this lingers the more conflicts will arise.

Did successfuly publish few categories of instances but having hard time with render instance.
I have it already in my scene and when trying use Convert legacy instances action nothing happens and no render instance converted.

Also when trying the New Publisher from not latest workfile but older version (which is perfectly fine in old publisher)  it causes following Collecting errors

So I have tested to publish rig instance via new Publisher and all went ok but after that when trying to load rigMain via Asset Loader it loads but gives me these errors:

This is correct. This is the open task: Rig loader correctly generates a new style animation creator instance
It's because loading a rig automatically generates an Animation instance, but I wasn't sure what the easiest way was to create an animation instance through code using the new creators.

Also when trying the New Publisher on Xgen instance from not latest but older workfile version (which is perfectly fine in old publisher) it causes following collecting errors

Thanks. Interesting. That's odd.
Current file should be collected here and then scene version retrieved here.
What does this print for you in that scene?
from maya import cmds
print(cmds.file(query=True, sceneName=True))

I've sometimes seen that return None when the scene open actually had errors, e.g. an unknown plugin was found.

Thanks, yeah I have realized there was a "skeleton in the closet" in form of good ol' mentalray nodes acting as unknown nodes :D ..as Im using some downloaded asset from the web.
I have cleaned up the rig workfile and published it. so should be ok in that manner.
Also tested new publisher with Yeti Rig instance which works (conversion from old instance) but fails when trying to publish yetiRigMain. However its tied to this PR so when merged should be working too.
https://github.com/ynput/OpenPype/pull/4554#discussion_r1123065328

Regarding your question on Xgen publish scene:

Still gives me the same error as already reported

When trying delete RenderMain instance and create new one via New Publisher it gives error
Creator: Render (io.openpype.creators.maya.renderlayer)

Error: A Render instance already exists - only one can be configured.

Even when no active renderMain in outliner or when creating for ie RenderSecondary. Still error shown

Reminder to self: add back in the strict error checking toggle I removed in the merge conflict -> move it to the Maya deadline submitter as attribute definition.

Can't create render instance issue fixed with https://github.com/ynput/OpenPype/pull/4388/commits/479e0bdf2237b0212db8ebcaeeff92cc54f89981

Xgen collect scene version issue I can't reproduce.
I got failures on extracting which I think are bugs in the Xgen Extractor:

It doesn't support the source geometry to be top level (parented to world)
It doesn't work entirely smooth for scenes with non-unique object names due to how maya.cmds.listRelatives is used.
Not sure what "palette" is in xgen but the xgenm.importPalette(temp_xgen_path, []) returns an empty string for me and thus it getting deleted after the context manager errors for me.

I'll make a separate PR for that I think.

I fixed issue of loading rigs with this commit https://github.com/ynput/OpenPype/pull/4388/commits/9976d7bc95b9af3e954c1cd7d1b4ea274786869e however the animation subset is now based on the correct logic from variant making quite an odd naming convention by default. We'll need to decide how we want to best deal with this backwards incompatible change. Old instances are converted keeping their names I believe, but newly loaded rigs will adhere to the new Creator naming adhering to the subset naming conventions set in settings.
Here's a loaded rig now:

Can't convert legacy render instance to new style instance:  Convert legacy instances action nothing happens forrender instance converted.
I'm pretty sure this conversion issue is still broken.
However after this commit I've been able to at least get a render submission to deadline. Quick and dirty however and will require a lot of testing of the different settings. The validator, like "Validate Render Settings" isn't very nice either - you'll need to go through the logs to really see what's wrong with your scene.

I've assigned a few people to this PR because I suspect I'll need some close eyes from those people to get this to a decent state to continue with. So please feedback on everything that stands out, even if still weird. A lot works, but more than likely even more is going to be broken so please report what you can!

Arnold Ass works with the new Publisher well...

I've resolved merge conflicts once again. Would love to get input on this PR to avoid having to resolve merge conflicts for the next few months as it remains open.
Please let me know what I should focus on to make this worth testing on from this point forward. @iLLiCiTiT @antirotor @tokejepsen @moonyuet likely already have some notes based on the code changes alone.

Did a first pass of review

@BigRoy I'm assigned to this but dont know what to do about it?

I'm assigned to this but dont know what to do about it?

It was mostly for checking the code changes and maybe proposing ideas for better code style regarding the new creators/validations style. However @mkolar mentioned they'd be proposing changes for the new publisher soon (within a day or so).
Since that might influence how things are coded for the better I think it's worth the wait for that and then maybe with that functionality in place have a more thorough review with you, @iLLiCiTiT, @antirotor and @mkolar maybe on the code for this PR once it's aligned with that proposal or alike.
For now I'll unassign you in favor of waiting for the publisher changes.

But I am not sure if we should wait for it. I think it would be better to handle additional changes coming from that in another PR? Because this refactor is now influencing anything coming to Maya publishing. Unless there are things coming from the publisher changes that are essential for this functionality ofc.

I think we'll need to wait - there's just no other sensible approach. Merging this with 'a few fixes' would mean it'd be as broken as Houdini currently is - having very bad validation reports making day to day production extremely hard for artists. Plus what we'd be hacking in to get validations maybe to an ok standard would likely be undone by the design changes presented in that topic so we'd have to revert or refactor some things again.

Tested rendersetup in Maya 2023 successfully.

FYI Working on resolving the conflicts atm.

Tried to resolve the conflict here; https://github.com/BigRoy/OpenPype/pull/13

Did try finaly publish UE assets.
When trying export UEskeletal Mesh I got following error:

Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\extract_unreal_skeletalmesh_abc.py", line 92, in process
    extract_alembic(file=path,
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib.py", line 1228, in extract_alembic
    cmds.AbcExport(j=job_str, verbose=verbose)
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\extract_unreal_skeletalmesh_abc.py", line 2, in AbcExport
RuntimeError: No valid root nodes were specified.

Did test Vray and its
VrayProxy - here is all good and publish works fine
VrayScene - there is an error shown during Publish

ERROR: Export vrscene not enabled
ERROR: Template for file name is wrong
Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\validate_vray_translator_settings.py", line 29, in process
    raise RuntimeError("Found invalid VRay Translator settings!")
RuntimeError: Found invalid VRay Translator settings!

[ ] Unreal Skeletal Mesh export fails on Alembic extraction: I suspect this is not a new issue in this PR but already existed previously. The logic seems to be expecting that in the instance objectSet it also contains the top level nodes for your export (the root nodes) which yours doesn't have, it only contains sets in your instance. You'll need to add model_GRP into the instance. Can you confirm that's the case with this PR and before? If so, then mark this checkbox please and create a dedicated issue if the Unreal workflow isn't clear enough for artists.
[x] V-Ray Scene Translator Settings validation should now report correct validation errors
[ ] [Conversion of legacy render instance is indeed todo] as in the PRs description too. I'll look into it soon.

Thanks again for the testing!

@LiborBatek Could you test the conversion from legacy render instances again? It's a bit quick and dirty but I think it works.

@BigRoy I've updated I think all of the validators to at least use the correct validation error so they present themselves in the report, rather than as actual error. Seems I angered a dog though.

Also checked the Crashed plugins Tab and found these:

Maybe we missing these integrations merged in this PR causing issues?! Just guessing :-)

Also checked the Crashed plugins Tab and found these:

These are totally fine - they are the plug-ins in deadline module which aren't intended to work with Maya. The plugin logic still tries to import these but fails due to being unable to import e.g the houdini, max or nuke python libraries. This is no different than how it is now prior to this PR (even though it doesn't have such a "Crashed" tab.)

However there are no visible Render instances afterwards in the Publisher...even when reopened again so I guess it fails somehow.

The render instance should've been created, yes. So this is definitely wrong. Unfortunately the LOGs don't show anything about the conversion having even occurred. I don't know what's failing unfortunately.

I will put here any findings during another tests....
Model instance publishes ok
Rig instance also fine
Ass instance gives following error during creation of the instance in Publisher

Speaking of Look Instance... when converting obsolete instance to the new one suitable for New Publisher it sets multiple attribs for texture conversion which later causes validation issue because both of these Maketx and Rstex are On

Should be set just to one of these or nothing so Validation of Look instance would pass through and Publish ok.

Render instance working fine and successfully published with finnished rendered images and reviewables.

When trying to Publish Review it gives following error:

@LiborBatek That should be handled by this commit - did you pull latest changes?

@antirotor I have just checked out this PR...should I merge develop into it? Before testing??

With the new publisher managing the per layer objectSets at publish time through the Creator, does that mean we can remove the RenderSetupListObserver logic. We've had scenes where this turned very slow (with many many renderlayers, hehe) and also where it just plain failed to actually make sure it's still in sync (with opening scenes, etc.). It would be very nice if the new style creators now allows us to remove all these render setup observers and callbacks.

With the new publisher managing the per layer objectSets at publish time through the Creator, does that mean we can remove the RenderSetupListObserver logic.

We could remove it, but first we need to solve how to use renders as review for subset (that was done by moving for example model instance set under render layer set) - but it would be nice to make it more simple anyway.

It seems that it does still work, the only issue is that it doesn't create the set representing render layer immediately. But once it does, this setup behaves as expected:

It seems that it does still work, the only issue is that it doesn't create the set representing render layer immediately

That's correct - it only updates/generates on any "save" of the publisher. It's more direct and requires much less callbacks going on in Maya.

That's correct - it only updates/generates on any "save" of the publisher. It's more direct and requires much less callbacks going on in Maya.

I still think that it would be nice for artist to just check the checkbox, select the camera or render layer and that would be enough for attaching review to subset. But that is not in the scope of this PR.
There are still few minor issues where asserts should be replaced with PublishValidationErrors, but that can be done in additional PRs. I've fixed the ASS issue @LiborBatek mentioned and with that, this should be ready to merge.

When trying to publish Review from scene it got error (I have created fresh new review instance) I have also model instance nested inside review (see scrngrb)
My fps and frame range also matches the values in DB. So no mismatch in those.

Hmm, seems like animation data are not collected from review instance but from the model that is obviously missing it...

Tests so far with success

[ ] ass
[ ] model
[ ] reviw
[ ] animation
[ ] pointcache
[ ] render

I have found an Issue when creating Look instance it has enabled both conversion MakeTx and MakeRSTexBin which then fails during Validation

and during Publish

I guess these should be rather turned off when creating the Look instance. One of the reasons being that even not usable for ie when using Vray renderer so these doesnt make sense then. Or to test if those renderers are enabled for rendering...

I've fixed the fps issue in review and default settings for look creator, so it should be ok.

@Innders Lovely! :)
How can I test it? I guess on ayon.dev not mine server, right?

WTF! This is huge!


add more checks for keylen

Part of #22

$ node -v
v5.6.0
$ node
> require('crypto').pbkdf2Sync('password', 'salt', 1, NaN)
TypeError: Bad key length
$ nvm use 0.10
$ node -v
v0.10.42
$ node
> require('crypto').pbkdf2Sync('password', 'salt', 1, NaN)
<SlowBuffer >

Different behavior for different node versions :(

updated

... all failed except Node 4? Interesting

 1) node pbkdf2 pbkdf2-compat pbkdf2Sync sha1 should throw Bad key length:
     AssertionError: Missing expected exception..
      at Function._throws (assert.js:301:5)
      at Function.assert.throws (assert.js:318:11)
      at Context.<anonymous> (test/index.js:95:24)

What version of node v4 you are using? May be your version not include https://github.com/nodejs/node/commit/4c8d96bc30281d77ab556adfe9cc1f91e0db4522 ? (checks on NaN and Infinity was added there)

@fanatid I'm referring to the CI.
Every version except Node 4 are failing this.

@dcousens I'll fix with this PR after https://github.com/nodejs/node/pull/5397 will be merged and released

merged as part of #27


Package build order

[x] make
[x] perl
[ ] m4 -- problems with gnumake
[x] autoconf
[x] automake
[x] xz
[x] bzip2
[x] zlib
[x] expat
[x] ncurses -- strip command is missing??? fixed by creating a fake link to strip
[ ] libtool -- same issue as m4
[ ] rhash -- same issue as m4
[x] libuv (needs libtool)
[x] help2man
[x] flex -- I probably did this one wrong, it is really weird to test this one.
[x] pkg-config
[ ] bison (needs flex)  -- same problem as m4 with gnumake
[x] ca-certificates
[x] openssl
[x] libssh2 !!! circular dependency, depend on ubuntu's
[ ] python 2.7 (krb5) <- why does krb5 need such a high level program.
[ ] krb5 (curl) <- this seems to be optional for curl
[x] curl
[ ] cmake (needs libuv)
[ ] texinfo  -- seems to need a c compiler (send issue upstream too)
[ ] libffi (needs texinfo)
[ ] readline (needs ncurses)
[ ] sqlite -- removed readline dependency in favor of libedit, nobody needs readline.
[ ] tk  needs too many cdts, just skip, jjhelmus, what repo did you have to include???

Now we get to build python

[ ] python 3.7  (remove xorg cdt and tk)
[ ] python 3.6  (remove xorg cdt and tk)
[ ] python 2.7  (remove xorg cdt and tk)

Now we get to start building the python ecosystem.

[ ] setuptools
[ ] pip

[ ] wheel (requires setup tools)

[ ] six
[ ] conda

[ ] conda-env >=2.6  <- just remove this dependency.
[ ] enum34                 # [py<34]
[ ] futures >=3.0.0        # [py<34]
[ ] pycosat >=0.6.3
[ ] pyopenssl >=16.2.0

[ ] cryptography

[ ] requests >=2.12.4,<3
[ ] ruamel_yaml

@jjhelmus do you have a good list of the order to follow?
I've already run into many issues with make, perl, and m4, I'm not sure how much I can automate this process.

When make is found to be necessary, document it here:
https://github.com/conda-forge/docker-images/issues/78

The order that I build the bootstrap packages can be found in the conda4aarch64 repository.  I'll update the order as I rebuild the packages in a CentOS 7 container.
I'll be uploading the packages from this build out to the c4aarch64 channel.  GCC 7.3.0 compilers are available there that run on CentOS 7.  This should be preferred over the ones in the aarch64_bootstrap label.

Are you cross compiling? I had major issues with GNUMakefile

I'm building inside a Docker container running on a baremetal  aarch64 machine.  Recipe are in the conda4aarch64 repository if you want to compare.

m4 recipe is at https://github.com/jjhelmus/conda4aarch64/tree/master/recipes/m4-feedstock/recipe

Is there a way to sync our efforts?
My goal is to follow conda-forge really closely, eventually cleaning up my changes and submitting them back.
Will you be doing a graphical stack?

Yeah, I have the same m4 recipe, it is something weird about either my ubuntu image, or the specific version of crosstools I have :/
Do I need to rebuild all my package with the Centos7 compiler in https://anaconda.org/c4aarch64/repo ? or should it be compatible with the one that worked only on ubuntu 18.04

My plan was to build everything needed for conda, conda-build, constructor and anaconda-client.  I want to submit the modification back to conda-forge but working in a single repo initially is easier.

Do I need to rebuild all my package with the Centos7 compiler in https://anaconda.org/c4aarch64/repo ? or should it be compatible with the one that worked only on ubuntu 18.04

The packages existing package should be alright but switching to CentOS 7 base image without compilers or other build tool would be good.  I'll add the image I'm working from to conda4aarch64.

Ok, I'll switch, I just have to change my mods to conda-smithy. Maybe that will fix my m4 issues. If those m4 issues get fixed, then I think we have a good case to seriously start pushing some patches.
I've got the Readme and some basic rerendering down. I'm trying to see if I am going to need to include the arch in the .ci_support files. I think it would be prudent to, but will cause the names to explode.

https://github.com/jjhelmus/conda4aarch64/tree/master/docker/pkg_builder has the Dockerfile I'm using for builds, I installed an aarch64 miniconda clone that I have locally.

How did you build that aarch64 miniconda? Using the previous bootstrap tags you had? If that is the case, then it is the same as Archiconda3 I think.

Yes, the miniconda I used had packages from the bootstrap, Archiconda3 should be the same.

Did you figure out of shippable has an automated method for registering repositories?  Or is that still a manual step?

So I run that fork repo script with the names of the packages I want, and it does everything from fork, creating the branch, re rendering, quite often, I’ve had to add make to the requirements.
It can take many repos in parallel, though I haven’t used that much since I’ve hit many packages that require some kind of mod.
Finally, as you know, this early in the process there is only one thing to build at a time


syntax sugar for map instantiation with string keys

In Ceylon, instantiation of a Map with strings as keys looks like this:
map { "name" -> "Trompon", "weight" -> 6000, "color" -> #808080 }

A feature that some languages offer, especially dynamic languages (I was reminded of this looking at the Groovy docs) is the ability to create a map with strings as keys using a nice syntax, for example:
[ name: "Trompon", weight: 6000, color: #808080 ]

(Note that in JavaScript this same code instantiates an "object", not a "map" as such, but JavaScript objects are essentially just maps by nature.)
Now, it turns out that we already hacked a form of this syntax onto the language, as a part of the support for dynamic typing. We can write:
dynamic elephant = dynamic [ name = "Trompon"; weight = 6000; color = #808080 ];

However, there is no exactly equivalent syntactic construct for regular typesafe Ceylon code, something that always felt a little strange to me.
What if we adopted this syntax as a sugar for ceylon.language::map()? We could write:
Map<String,Object> elephant = [ name = "Trompon"; weight = 6000; color = #808080 ];

This could, in principle, be a nonbreaking change but in practice what I might need to do would be to disallow assignments to variable values in sequence instantiation expressions, just like what we already do in named argument lists. That's completely intellectually consistent, and highly unlikely to break any real Ceylon code, and I'm not bothered by it.
AFAICT, this feature would be pretty trivial to implement.
Thoughts?

I’m very skeptical about the usefulness of this. It seems to me like a very restricted feature: create an immutable map with a completely static set of string keys. Not only is this much less flexible than map (which offers any key type and, with streams and comprehensions, a very dynamic key set), but it also overlaps a lot with named arguments. In fact, I think that a named arguments instantiation is also the better analogy for most dynamic [] objects, including the one from your example (in elephant, name, weight and color are completely unrelated things and more similar to attributes than entrieis).

@lucaswerkmeister well an example of where it could be useful is in something like ceylon.json. One could create a ceylon.json-like package where Object is an alias for Map<String,Value> and Array is an alias for Value[], and get a rather nice literal syntax.
Now, OTOH, that would create significant pressure to add an alternative syntax for accessing kap items my string-valued keys, i.e. elephant.name, and TBH I don't really see how we could make that work well.

Now, OTOH, that would create significant pressure to add an alternative syntax for accessing kap items my string-valued keys, i.e. elephant.name, and TBH I don't really see how we could make that work well.

So I guess the argument would be that this feature should go hand-in-hand with a streamlined syntax for map["key"] if it's to be useful.

I suppose the conventional solution would be to syntactically distinguish "symbols" from identifiers, i.e.:
value elephant = [ $name = "Trompon"; $weight = 6000; $color = #808080 ];
value name = elephant.$name;

However, it seems clear that this makes the whole concept much less interesting.

That comment just made me realize that this is even more restricted than I thought: the keys must be Ceylon identifiers, not arbitrary strings. (Lowercase only?)

the keys must be Ceylon identifiers, not arbitrary strings.

Right, that's the point: you can avoid the quotes because the scanner already knows how to treat an identifier. It's the same in other languages which have this feature.

Lowercase only

rm, I don't see why, but I have not checked the grammar.

So what do you use when you want to create a map using declarations as keys? With something like true/false or smaller/larger, etc?

I suppose you continue to use map { false -> 0, true -> 1 }.

I suppose you continue to use map { false -> 0, true -> 1 }.

Right, of course.

Upon reflection, we probably don't want to do this, since one day we might want to use this syntax for creating instances of structurally-typed records. And that's actually a closer match to what the dynamic instantiation expression syntax means today.
Closing this.


add filtering capabilities

You can now control the data that comes to Sumo Logic.  First, you can use the annotation sumologic.com/excludeFromSumo to prevent a pod from going to sumo.  In addition, you can add some environment variables to the fluentd.daemonset.yaml to filter logs from the cluster.  You can do this by providing a regex pattern to apply to the namespace, pod, container or host.

Great! This is awesome. Could you also add some examples to documentation? So that new people can see and replicate :)

Definitely.  Once @stevezau gives a quick sanity check I will update the read me.

I was thinking of just adding support for the tail exclude path as an env var? http://docs.fluentd.org/v0.12/articles/in_tail
Then adding support for annotations sumologic.com/exclude. Not sure all the regex is really required?

I tried to give more fine grained controls.  There may be entire namespaces I want to exclude and this way I can exclude by namespace (or pod/container/host) and not have to muck with the file path.  The downfall of this I suppose is that the data actually gets to fluentd as opposed to if we filter by the tail plugin, it never makes it.  Agreed on the excludeFromSumo bit, will rename to exclude.

I see value in the regex params to filter by pod/container/namespace/host and have already chatted with someone who needed this, so I am gonna leave that.  However, I will add the ability to pass in some file paths to the config as well. This should provide the most robust control.

Changes made and readme updated, however, I am waiting on access to the docker hub to push the latest image as I have fixed another issue.  Once I get access I will merge and push to Docker Hub.


changefeed resolved ts can not go on after restart all pd、tikv and tidb

What did you do?
1、create changefeed
2、run sysbench
3、kill all pd、tikv and tidb
What did you expect to see?
after pod start，changefeed status can recover and resolved ts can go on
What did you see instead?
after pod start，changefeed resolved ts can not go on  and changefeed status was abnormal

Versions of the cluster
./cdc version
Release Version: v8.2.0-alpha
Git Commit Hash: fe19cd9c9e4044d3ae70b32134ce521e39a3feb2
Git Branch: heads/refs/tags/v8.2.0-alpha
UTC Build Time: 2024-04-22 11:37:02
Go Version: go version go1.21.6 linux/amd64
Failpoint Build: false
current status of DM cluster (execute query-status <task-name> in dmctl)
No response

/remove-area dm
/area ticdc
/severity major

The root cause of this issue is PR #10928:

When initialization fails, the processor only reports warn, and then every time it ticks, it enters the TryInitialize logic and returns the same error, leading to an endless loop in processor goroutine.
https://github.com/pingcap/tiflow/blob/72646f6825a7288131b553f4cb67b9ea3b0662b4/cdc/async/async_initializer.go#L80-L82
For the owner goroutine, it will advance the checkpointTsAdvanced in each tick because the resolvedTs is stuck. Therefore, changefeed will not be set to failed state even if checkpointTs does not advance for a long time.
https://github.com/pingcap/tiflow/blob/72646f6825a7288131b553f4cb67b9ea3b0662b4/cdc/owner/feed_state_manager.go#L455-L472


Add option to run integration tests using remote node

What should be done?
Currently integration tests expect a locally running node. Some users want to have a remote note that they run the tests against. We should provide the ability to do so
How should it be done?
We should add a config file for integration tests / using the same config file but with an integration test profile
When is this task done?
when you can run integration tests using either a local or external node.
Additional context
No response

closing as the PR already got merged


Insecure coding pattern: Missing default case in switch statements

Greetings,
We are security researchers and we are looking for insecure coding patterns and configurations in the microservice architecture repositories. In your repository, we have found that your code does not have a default case in the switch statement. According to the Common Weakness Enumeration organization, this is a security weakness. See the link https://cwe.mitre.org/data/definitions/478.html
Source:https://github.com/fastnsilver/grivet/blob/master/core/deployables/query/src/main/java/com/fns/grivet/service/NamedQueryService.java
Fix: Fix #91
I am interested to know if you agree with the findings. Any feedback is appreciated.

Addressed in d81c619.