Fix TextMatchFilterOptimizer or not behavior

Lucene's query language has a constraint where NOT operator cannot be used with just one term, since it relies on the difference of sets. Therefore, the pinot query x OR NOT y and the lucene query x OR NOT y are not equivalent. Rather, x OR NOT y in Lucene is equivalent to simply x.
This patch skips optimizing these cases to ensure query correctness.
From the Lucene docs:
Note: The NOT operator cannot be used with just one term. For example, the following search will return no results:
NOT "jakarta apache"

Codecov Report
Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (766397d).
Report is 714 commits behind head on master.

Files
Patch %
Lines

...ery/optimizer/filter/TextMatchFilterOptimizer.java
0.00%
5 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (766397d). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (766397d)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13533       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2482       +46
  Lines        133233   137213     +3980
  Branches      20636    21299      +663
=============================================
- Hits          82274        0    -82274
- Misses        44911   137213    +92302
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <0.00%> (-27.73%)
:arrow_down:

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@jasperjiaguo  - Can you help take a quick look at this for our use ?

nit: I think x OR NOT y is equal to x NOT y (from my testing)


Put debug-dump-store behind a feature-flag

When debugging https://github.com/Nitrokey/piv-authenticator/pull/12 I realized this was not removed from production firmware. Putting it behind a feature flag will ensure that it does.

I thought the consensus is to not make a feature out of the debug switches. Has this changed?

I think this is a misunderstanding.  We almost never use rustc’s --cfg flag directly, just features.  But in the source code, we use the cfg attribute to check for that feature.

I think the main difference between the two is that the addition of the debug-dump-store is purely additive, whereas the removal of encryption is not.
This flag does not change the test paths if you use --all-features, since it only adds new code.
For the encryption on the other hand, it removes code, so testing with --all-features does not test encryption.
Also removal of encryption is not something we want to encourage at any point, while features are easily discoverable, and therefore can mistakenly be enabled, which would be highly problematic.

It's also consistent with the std features, that are here only for debugging/testing. They can be features because they're additive, and not that dangerous, contrary to the encryption flag.

dump-store in production firmware sounds dangerous to me, hence the question

It makes the call available but you would still have to call it, and you would have to have the logs somehow accessible on a production device before this becomes really dangerous.

Did you come to consensus? :) Slight tendency to cfg-flag on my side (default "off" naturally).

I moved it behind a CFG. This doesn't matter much if you prefer cfg we can merge it that way.


bug(node): Error: Failed to convert JavaScript value Object [10,10] into rust type String

LanceDB version
0.10.0
What happened?
The example of table update will report an error
Are there known steps to reproduce?
import * as lancedb from "@lancedb/lancedb";

const db = await lancedb.connect("./.lancedb");

const data = [
    {x: 1, vector: [1, 2]},
    {x: 2, vector: [3, 4]},
    {x: 3, vector: [5, 6]},
];
const tbl = await db.createTable("my_table", data)

await tbl.update({vector: [10, 10]}, { where: "x = 2"})

Hello. There are two ways to pass new values in the update method: as SQL strings or as values. When you pass them in that overload, they are interpreted as SQL strings, which is why you get an error about converting to a string. If you want to pass Javascript values, instead use the values option:
table.update({ where: "x = 2", values: { vector: [10, 10] } })

https://lancedb.github.io/lancedb/js/classes/Table/#updateopts

table.update({ where: "x = 2", values: { vector: [10, -10] } })
If I change one of the values to a negative value, it will throw a new error:
[Error: lance error: Invalid user input: LanceError(IO): Only arrays of literals are supported in lance.
I encountered this issue because in my project, the vector values have both positive and negative numbers, which results in the same error. How should I solve this?

Oh that is the same as https://github.com/lancedb/lancedb/issues/1501
Which has yet to be fixed upstream: https://github.com/lancedb/lance/issues/2695
I'll prioritize fixing that soon.


Mark functions as const and 0 as NULL

Not making changes like this to the deprecated PPD compiler code...


[SPARK-18872][SQL][TESTS] New test cases for EXISTS subquery (Aggregate, Having, Orderby, Limit)

What changes were proposed in this pull request?
This PR adds the second set of tests for EXISTS subquery.

File name
Brief description

exists-aggregate.sql
Tests aggregate expressions in outer query and EXISTS subquery.

exists-having.sql
Tests HAVING clause in subquery.

exists-orderby-limit.sql
Tests EXISTS subquery support with ORDER BY and LIMIT clauses.

DB2 results are attached here as reference :
exists-aggregate-db2.txt
exists-having-db2.txt
exists-orderby-limit-db2.txt
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Test build #72208 has started for PR 16760 at commit 2473e0c.

Test build #72208 has finished for PR 16760 at commit 2473e0c.

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

cc @hvanhovell @gatorsmile @nsyca
@nsyca Thanks for reviewing.

Merged build finished. Test PASSed.

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

Did the comparison. The results match what DB2 returned. Do you think we can remove some duplicate test cases in SubquerySuite.scala?

@gatorsmile Thanks a lot for reviewing. @nsyca and i had a brief discussion about this. Yeah, we will remove the duplicate test cases from SubquerySuite.scala. However , we wanted to keep all the tests till the phase1 work is committed to ensure the full coverage i.e we don't inadvertently remove any tests for which we may have missed to add a corresponding test in sqltestquerysuite.

@dilipbiswal Does that mean your test cases cover all the EXISTS scenarios in SubquerySuite.scala?

@gatorsmile Currently for exists we are missing 1) Negative scenarios 2) Generators (there is one test case in subquerysuite) for it.

@dilipbiswal Are you planning to submit another PR for Generators or do it in this PR?

@gatorsmile Yeah Sean. Actually most likely i will need to work out a different schema than what i have currently for the generator tests. So i was planning to add the negative scenarios and generator tests in another PR.

ok. LGTM

retest this please

Test build #72558 has started for PR 16760 at commit 2473e0c.

Test build #72558 has finished for PR 16760 at commit 2473e0c.

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

Merged build finished. Test FAILed.

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

retest this please

Test build #72572 has started for PR 16760 at commit 2473e0c.

Test build #72572 has finished for PR 16760 at commit 2473e0c.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

retest this please

Test build #72585 has started for PR 16760 at commit 2473e0c.

Test build #72585 has finished for PR 16760 at commit 2473e0c.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #72602 has started for PR 16760 at commit 2473e0c.

Test build #72602 has finished for PR 16760 at commit 2473e0c.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #72621 has started for PR 16760 at commit 2473e0c.

Test build #72621 has finished for PR 16760 at commit 2473e0c.

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

Merged build finished. Test PASSed.

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

Thanks! Merging to master.

Many thanks @gatorsmile


CI: Enforce sensible timeouts.

Default timeout/duration unit is nanoseconds, so specify time.Second
where the unit was missing, and enforce minimum timeout of 10 seconds
and minimum ticker interval of 1 second in WithTimeout().
The default Ticker duration in WithTimeout was 5 nanoseconds, which
may have caused busy looping on the provided body() if the first call to
body() was not successful.
Istio test may have been failing due to this.
Microscope test also had both timeouts and ticker durations without
units (defaulting to nanoseconds), which may have contributed to the
fact that microscope test had to be disabled.
Ginkgo functions have optional timeouts (that we usually do not use),
expressed in seconds. These should not be mixed up!
Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

This change is

test-me-please

Coverage decreased (-0.02%) to 41.969% when pulling 5f9e029576625eeaff891df116926058f2b99049 on pr/test-fix-WithTimeout-helper into 087abbd318d16a7f2ac4f069d6e26c936d3f0c58 on master.

test-me-please

Catched another 1ns ticker, testing again.

test-me-please


Questions about the input of the model

Hi! I have some questions about the input of the model. In the 378 and 386 line in simulator.py, the call of model is like " model(inputs, training=False)" or “model(inputs, vel, training=True)”, as shown in the pic1 and pic2. (The inputs contain the "pos", "vel”,“box”,“normals ”and so on.)

But in the forward() in sym_net.py, it seems that the inputs should be “prev” and “data”. The "prev" contains “pos”,"feats","idx",“dens”, which does not seem to match the calling function.

For some unknown reason my debug mode in Pycharm can't get into the train() function, which makes it hard for me to understand what's going on and how the fluids and box's data fused together. Could you please give me some hints? Looking forward to your reply!

I solved the problem that debug mode can't get into the train() function by adding a line of code before the calling of train(), and the problem disappeard:

And everything became clear when using the debug mode.
Cheers!
``


NIMBUS-404, NIMBUS-405 :: Links not shown in grid

Description
Grid links are not showing in a few scenarios.
Overview of Changes
Added condition to deserialize the inner grid json values
Type of Change

[ ] Bug fix

You did it @sandeepmantha!
Thank you for signing the Anthem Opensource Software CLA.


Calculate the percentage

Hi. I wonder if there's a way to automatically calculate the percentage of completion from note's frontmatter.
In my case I have, with other keys,:
Total:
Seen:
for the total number of episodes in my series and how many I've already seen. So I wish to pass to the progress bar the result of (round(seen/Total*100))
I hope you can understand what I mean
Thanks in advance for any help

Hello!
I have never used frontmatter, but I will try to help.
Is there any way to create a new variable with the value round(seen/Total*100)?
Or maybe you can calculate it directly in the link: https://progress-bar.dev/{100*seen/Total}/
Let me know if any of these options work.

Given that this would normally be expressed as a fraction, ie seen/total, maybe the most logical way would to handle redirection of the form
https://progress-bar.dev/seen/Total
ie
https://progress-bar.dev/15/20
would display a 75% progress bar if you've watched 15 out of 20 (or maybe it should show 15 in the left half of the bar and 20 in the right half?)


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>
.travis.yml

chore(travis): merge from template .travis.yml

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ocamlPackages.logs: allow overriding logs

Description of changes
it's currently not possible to override logs from outside the mdx derivation. This leads to the conflicting OCaml packages detected error when using any other library that also uses logs:
       > Conflicting ocaml packages detected
       > findlib: [WARNING] Package logs has multiple definitions in /nix/store/yqjs4q77pnv1i4dmmp23bp2i3aqxxmag-ocaml4.14.1-logs-0.7.0/lib/ocaml/4.14.1/site-lib/logs/META, /nix/store/c6md31db2iw69l988kjs00yw2vfbkrwx-ocaml4.14.1-logs-0.7.0/lib/ocaml/4.14.1/site-lib/logs/META
       > Set dontDetectOcamlConflicts to true to disable this check.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

tagging @Julow for review too based on https://github.com/NixOS/nixpkgs/pull/241476


libprotobuf error google/protobuf/descriptor_database.cc:57 file already exists in database: caffe.proto

I build the PyOpenPose successfully, but when I run the test file OpLoop.py, I get this error. Could you give some advises to fix it? Thank you.

This looks like an openpose issue, it is not related to PyOpenPose. Do you have the latest openpose version checked-out? Do the openpose examples work?

Yes, I check my openpose and find that it doesn't work after I change the opencv2.4 to opencv 3.3. I change the version of opencv, because I found that pyopenpose need opencv 3.3. I guess the problem is caused by the version of opencv. Can you tell me which version of opencv and protobuf you use to build openpose?

I am using opencv 3.2 and it has been tested with 3.1 as well. I guess 3.3 should work as well. The protobuf version i use is 2.6.1 (from the ubuntu 16.04 repos).

Thanks for your reply. After using the configuration you use, I have built the pyopenpose successfully. Thank you so much!

I'm facing the same error. I'm using Opencv 3.2

After doing this : https://xiaobai1217.github.io/2017/08/07/fast_rcnn/#more
I know face a SegFault during import


Quick ray bug fix for actors

Signed-off-by: Filip Haltmayer<EMAIL_ADDRESS>

Codecov Report

Merging #1229 (bac7902) into main (d057537) will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1229      +/-   ##
==========================================
+ Coverage   68.45%   68.49%   +0.04%
==========================================
  Files         252      252
  Lines       12232    12230       -2
  Branches     2033     2032       -1
==========================================
+ Hits         8373     8377       +4
+ Misses       3325     3321       -4
+ Partials      534      532       -2

Impacted Files
Coverage Δ

towhee/functional/mixins/parallel.py
76.19% <ø> (+1.02%)
:arrow_up:

towhee/functional/mixins/ray.py
100.00% <ø> (ø)

towhee/dataframe/dataframe.py
74.15% <0.00%> (+1.04%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm
/approve


Hubot doesn't work in locked campfire rooms.

Hubot doesn't work in locked campfire rooms even when the bot is an admin.

This is working for me, I just tested it on my own instance of Hubot. I locked a room, made my Hubot user an admin, left all the channels on that user, then restarted my Hubot, it joined all the specified rooms, and could respond to commands in locked and unlocked rooms.


feat: provide docker image

:tada: This PR is included in version 1.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Connection attempt failed

Hey guys.
I use Win7 x64, VS2017, .Net Core 2.0, DSharpPlus 3.0, DSharpPlus.WebSocket.WebSocket4Net 3.0. Here is my code:
using System;
using System.Threading.Tasks;
using DSharpPlus;
using DSharpPlus.Net.WebSocket;

namespace ControlBot
{
    class Program
    {
        static DiscordClient discord;
        static void Main(string[] args)
        {
            MainAsync(args).ConfigureAwait(false).GetAwaiter().GetResult();
        }
        static async Task MainAsync(string[] args)
        {
            discord = new DiscordClient(new DiscordConfiguration
            {
                UseInternalLogHandler = true,
                LogLevel = LogLevel.Debug,
                AutoReconnect = true,
                Token = "mycorrecttoken",
                TokenType = TokenType.Bot
            });
            discord.SetWebSocketClient<WebSocket4NetClient>();

            discord.MessageCreated += async e =>
            {
                if (e.Message.Content.ToLower().StartsWith("ping"))
                    await e.Message.RespondAsync("pong");
            };

            await discord.ConnectAsync();

            await Task.Delay(-1);
        }
    }
}

I have an error like this: "Connection attempt failed, retrying is 7s". Where did I make an mistake?

I'm pretty sure you don't setup the Discord Config there...
Like I have Program.cs with that (minus the Config code) and MyBot.cs where MyBot.cs has the config and event and other code.

He is setting up the discordconfig, it's a different issue @iDerp

@SadEnergizer don't use the websocket4net implementation. It's not intended for use with .net core

Hello? Opening an issue doesn't really work if you're not going to read our answers

Ok. I tried to run the app with .Net Framework 4.5.2, 4.6.2. The result was the same.

Try removing the configureawait part, it's unnecessary

MainAsync(args).ConfigureAwait(false).GetAwaiter().GetResult();
To
MainAsync(args).GetAwaiter().GetResult();
Other than that, everything should work fine

Also, wasn't .net core incompatible with win7?
For win7 you indeed need the websocket4net.. When you're using netfx

I don't know why, but it works now with my code above. Now I use .Net Framework 4.6.1. May be it was some problems with Discord server or my router. Who knows.

As long as it works c:

I think the reason was WebSocket4Net 0.15.0-beta9. I've just tested that version and stable version 0.14.1. Only the last is work.

You shouldn't update websocket4net, just download the dsharpplus websocket4net package.


[Enhancement] Increase contrast of helper text

Although helper text currently passes AA contrast ratio requirements it is somewhat light, particularly when placed in a form context on top of Gray 5. We can increase the contrast by making the gray darker while will providing the visual distinction that we are seeking for this text. The enhancement I propose here is to update inline helper, block helper, placeholder, and disabled field text to Dark Gray (#43484e) - basically any text that we present on a Gray 05 or Gray 10 background.
Current behavior

Inline helper, block helper, placeholder text, and disabled field text
Avenir Next Regular, 16 px, Gray (#5a5d61)

Proposed behavior

Inline helper, block helper, placeholder text, and disabled field text
Avenir Next Regular, 16 px, Dark Gray (#43484e)

Screenshots

Current
Proposed

Proposed changes

Update color for inline helper, block helper, placeholder text, and disabled field text to Dark Gray (#43484e)

Visual review requested: @chaisamantha @jenn-franklin

I'm going to move this one to my team repo as I gather some more examples.

I agree with changing the color of the helper text from Gray to Dark Gray. To test the contrast between text color and background, I used the WebAIM Contrast Checker.

Gray on Gray 05 background
Dark Gray on Gray 05 background

Gray on Gray 10 background
Dark Gray on Gray 10 background

Gray does pass the contrast test for WCAG AA, which is the level that CFPB complies with. However, it does not pass WCAG AAA. Whenever possible, I think reaching for the optimal accessibility level is best.

@natalia-fitzgerald Great catch and improvement! Thanks for making this change!

"Before and after" update
Changes text from Gray (#5a5d61) to Dark Gray (#43484e).
Pagination

Before
After

Inline helper text

Before
After

Block helper text

Before
After

Placeholder text

Before
After

Disabled button

Before
After

Disabled checkbox

Before
After

Disabled radio button

Before
After

@meissadia - I am proposing a Design System update that will affect many components that we are building in our component library. My preferred process would be to update the components in the Design System and then pull them in when we pull in an updated version of the Design System. Can our team take on making this change at the source (DS) and then pulling it in with a future release? I can handle the documentation/specs updates in the DS if you can handle the code changes.

@natalia-fitzgerald Sure


[langchain] WandbTracer incompatible with langchain V2 Tracer API

Describe the bug

The langchain_community.callbacks.tracers.wandb.WandbTracer fails to log any trace or model information to WandB for langchain models. The tracer is incompatible with the latest V2 Tracer API as the Run object now inherits from langsmith.schemas.RunBase with a new schema.

from langchain_core.output_parsers import StrOutputParser
from langchain_core.prompts import ChatPromptTemplate
from langchain_openai import ChatOpenAI
from wandb.integration.langchain import WandbTracer

prompt = ChatPromptTemplate.from_messages([
    ("system", "You are a world class technical documentation writer."),
    ("user", "{input}")
])

llm = ChatOpenAI(model="gpt-4-turbo")
output_parser = StrOutputParser()
tracer = WandbTracer()

chain = (prompt | llm | output_parser).with_config(callbacks=[tracer])
resp = chain.invoke({"input": "how can wandb help with testing a RAG system built with langchain?"})
tracer.finish()

All exceptions are caught and suppressed but the warnings from processing the span and model from the run are below:
wandb: WARNING Skipping trace saving - unable to safely convert LangChain Run into W&B Trace due to: 'Run' object has no attribute 'execution_order'
wandb: WARNING WARNING: Failed to serialize model: 'int' object is not subscriptable

Additional Files
No response
Environment
WandB version: wandb==0.17.0
OS: macOS Sonoma 14.4.1
Python version: 3.11.9
Versions of relevant libraries:
langchain==0.2.2
langchain-community==0.2.3
langchain-core==0.2.4
langchain-openai==0.1.8
langsmith==0.1.73

Additional Context
No response

Hi @MarkAWard . Thanks for raising this issue. I was able to reproduce this issue and am working on a fix. I will update here soon.

Hey, @MarkAWard: This PR should fix the serialization issue with the new RunV2 API. Can you please let me know if your use-case works as expected when run from the branch? I'll tag one of the LangChain maintainers once you confirm. - All unittests pass as of now in LangChain

Thanks @parambharat my use-case did work using your branch. With the change we did lose the model_dict that was previously passed to the WandbTraceTree, it's not as important to me as having the traces/spans working properly but did want to note that.
Would you be open to injecting the serializer as an optional dependency to the WandbTracer? Currently it just uses _serialize_io, but it would be nice to be able to extend or replace the serializer. For example in my branch I had added a condition to serialize pydantic objects:
def _serialize_io(run_inputs: Optional[dict]) -> dict:
    ...
        elif isinstance(value, (BaseModel, PydanticBaseModel)):
            serialized_inputs[key] = (
                value.model_dump_json()
                if hasattr(value, "model_dump_json")
                else value.json()
            )
    ...

Thank you so much for reporting this, @MarkAWard, and thank you so much for looking into it so fast, @parambharat! Tracking this thread from the wandb support's side as well.

Hi @MarkAWard,

With the change we did lose the model_dict that was previously passed to the WandbTraceTree, it's not as important to me as having the traces/spans working properly but did want to note that.

Thanks for pointing out the missing model_dict. I have pushed new changes to re-add the model architecture to the trace logging. You should now also see the Model Architecture tab in the logged traces.

Would you be open to injecting the serializer as an optional dependency to the WandbTracer?

I've added a new argument io_serializer to the WandTracer that allows you to pass a custom serializer. I've also included PydanticBaseModels in the serializer's defaults alongside the exisiting protobufs.

Hi @MarkAWard : This PR is now merged in LangChain. Request you to check it out and close this issue at your convenience


PSA Multipart AEAD CCM Internal implementation and tests.

Description
This PR adds CCM to the algorithms supported by PSA multipart AEAD. It adds an internal implementation, and a suite of tests for it.
This completes one of the tasks of #3721, however there may be follow up work with regards to Nonce sizes.
Status
READY
Requires Backporting
No. The changes to the underlying cipher API to support multipart are only on this branch. Multipart AEAD was also not backported.
Migrations
No.
Todos

[ ] Tests
[x] Changelog updated

Steps to test
test_suite_psa_crypto should run clean, and all PSA tests should pass.

CI Fail is the previous (and now fixed) ssl issue, unrelated to this.

Code changes looks good, but CI is still failing. Will approve when CI is green.

The CI failures are due to unrelated known CI issues (timeout issues in the SSL Tests) - hence the HEAD failing, but the Merge tests generally not. The only way I could potentially resolve this would be to force update the branch, as some fixes have been merged since this PR was made.

The CI failures in pr-head are a known unrelated issue in TLS tests, now resolved. pr-merge passed. So CI is good.


Correct typo: Diagnosis => Diagnostics

And correct formatting of example in vs-2015.
Fixes #1941

@mikkelbu : Thanks for your contribution! The author, @gewarren, has been notified to review your proposed change.


SAK-29176 - Allow samigo when publishing a test, to link it to an existing non-externally maintained gradebook item.

SAK-29176
This applies when:
A non-externally maintained GB item exists and can be linked to an assesment when:
1) Is being published
2) It was published and has or not, grades already submitted into it
3) Is retracted and republishes with or without any submissions in it
Should the assessment is disassociated with the GB item, this will be removed.
For retracting the exam, the property "samigo.editPubAssessment.restricted" must be enabled for the code in ActionAuthorListener (~164) defaults to true

Some very minor comments, otherwise this LGTM. Extra points for cleaning up unnecessary boxing on some of those class members, replacing "magic numbers" with constants, and using StringUtils!

Hello @bjones86 , thank you for looking into this and your feedback. I made the suggested corrections and updated the commit.

I think this is functionality that we want and the patch seems good to me. @fgeraci are you still around to resolve the conflict here? I can try to get time to test this locally but I feel like we should get this in because it's a better overall workflow.

Yes,  i will take a look at it either this afternoon or tomorrow.
Fg
On Nov 15, 2016 11:29 AM, "Code Hugger (Matthew Jones)" <
<EMAIL_ADDRESS>wrote:

I think this is functionality that we want and the patch seems good to me.
@fgeraci https://github.com/fgeraci are you still around to resolve the
conflict here? I can try to get time to test this locally but I feel like
we should get this in because it's a better overall workflow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sakaiproject/sakai/pull/2790#issuecomment-260690762,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEnF-OdHRp3-1ljxJ4xII9lIRDAkHaDNks5q-d3GgaJpZM4IyCkh
.

Conflicts need to be resolved

Thanks Earle. I am currently out of town, returning on Monday. I will
resume this then.
Regards
Fer Geraci
On Mar 2, 2017 8:31 AM, "Earle Nietzel"<EMAIL_ADDRESS>wrote:
Assigned #2790 https://github.com/sakaiproject/sakai/pull/2790 to @fgeraci
https://github.com/fgeraci.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sakaiproject/sakai/pull/2790#event-983958711, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEnF-MdO9oaoySEG8hJGQyJvmXH8hDVWks5rhu7lgaJpZM4IyCkh
.

@fgeraci , how is this one going?

We do like this idea, but no comments for 6 months. This may need to be reviewed as part of a bigger gradebook consistency project, but I'd take it for 13 just for a short term fix too. Re-open if you resolve the conflicts.


xmlAttributeCollection

Hi,
trying to get the attribute list from an xml file, I use xmlAttributecollection but cannot get the list of attributes.
here is my code:
xmlNode: XmlNode;
xmlAttributeList: XmlAttributeCollection;
xmlAttribute: XmlAttribute;
xmlNodeList := pTableDATA.GetChildNodes();  (pTableDATA is an xmlFile as listed below)
                for i := 1 to xmlNodeList.Count do begin

                    xmlNodeList.Get(i, xmlNode);
                    xmlElement2 := xmlelement.create('Attributes');
                    xmlElement2.add(xmlNode);
                    xmlAttributeList := xmlElement2.Attributes();

                    Message('xmlAttributeList.Count ' + Format(xmlAttributeList.Count));

the message shows value of 0, here is the xml file:

I have the same issue, once I do VarXmlNodeList.Get(0, VarXmlNode) I get an error message with "0".

@thloke ,why is this marked as a question? It seems a bug to me...

@angela2389 The Get() method on XmlNodeList is 1-based like most of AL. It is also stated in the documentation https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/xmlnodelist/xmlnodelist-get-method.
The error-message is lacking and will be updated.

@abouraoui The code sample does exactly what it should.
xmlElement2 := xmlelement.create('Attributes');
Creates a new element named 'Attribute' e.g.
xmlElement2.add(xmlNode)
Add the content of xmlNode to the newly created element e.g. Content from XmlNode
xmlAttributeList := xmlElement2.Attributes();
Gets a list of attributes on the  element, which is empty and hence have Count = 0.


PostMan Collection Not UptoDate

The postman collection is currently not up to date with the library, there are some api available in postman collection that are no longer provided by the library again.

Postman Collection was published and updated today, please check: Postman Whats2API


HEASARC FITS file formats

Currently only in HDF5

I'm changing this to a catch-all issue to HEASARC FITS files, not just the response.


[fix] cms branch page : merge blank attributes

Coverage decreased (-7.6%) to 66.703% when pulling fbf16279ddb58982e3f470b41864c11f9694fac7 on itowtips:fix-branch-page into eba7a46a2c6aa4eceec9af55002fbfb60ebb1087 on shirasagi:master.


fix script

is this good to go?

With this update, I was able to run make proto-gen successfully. I think we should merge it, then pick-up the generated code updates it produces.
https://gist.github.com/levicook/85bb60592749b88d47fafce74c18f03b

This can be merged


Removed rosdep key omniorb4-idl and added omniorb-idl to omniorb

Replaces #11004.
omniorb4-idl was replaced by omniorb-idl for Ubuntu since 11.10. This PR adds the omniorb-idl debian/ubuntu package to the omniorb key and also removes the version-specific package lists for omniidl and omniorb that were only required for end-of-life distros in favor of simpler support of newer releases.

Upstream sources:

arch: https://aur.archlinux.org/packages/omniorb/
debian: https://packages.debian.org/search?keywords=omniorb-idl&searchon=names&suite=all&section=all
fedora: https://apps.fedoraproject.org/packages/omniORB-devel
ubuntu: http://packages.ubuntu.com/search?suite=all&searchon=names&keywords=omniorb-idl

+1


Start executing a specific command from editor in play mode

Right click on a command in a non-executing block and select Execute from the menu to start execution from there. Very useful for testing during development.
Requested on the forum

I want to try working on this one. Here's the start of it: https://github.com/inarizushi/Fungus/commit/b5081a530b49095066eb411c3435e05a643e1ce4
Can you tell me if I'm on the right track or if you have a specific idea of how this should go? Thanks!

So this can be closed right? :)

yup!


Make sure MeshLibrary shape array has correct number of elements

The shape array shown in the inspector increases and decreases by 2, ensuring that the last elements (when increasing) is a shape-transform pair.
Fixes: #53897

Thanks!

Cherry-picked for 3.5.

Cherry-picked for 3.4.3.


#1013 autoload all *.stories.js files in cli templates

Issue:
#1013 we should try to autoload all *.stories.js to make user's lives easier
What I did
How to test
Is this testable with jest or storyshots?
Does this need a new example in the kitchen sink apps?
Does this need an update to the documentation?
If your answer is yes to any of these, please make sure to include it in your PR.

I don't think the CLI test is set up right. Either that, or the angular storybook doesn't work. Looks like there's a lot of missing dependencies

Snapshot update should work anyway, it runs before smoke tests


Move to more recent networkx dependency

Can https://github.com/pysal/region/pull/34 be closed in favor of this one?


Add option to limit number of scrolled items to 1

Is this a bug report or a feature request?
Feature Request
Have you read the guidelines regarding bug report?
Yes
Have you read the documentation in its entirety?
Yes
Description
would be great to enable a mode where users only fling one element at a time: no matter how quick the gesture is, only the next element should be centered.
Maybe this is already possible but I haven't found it anywhere in the documentation or the examples.

Hi @marcmo,
Prop lockScrollWhileSnapping should help with that. Also, make sure to test in a production environment.
To provide a bit more context about why this is not an easy thing to accomplish, you need to know that despite being one of the most wanted feature, the React Native team have not implement yet a proper equivalent of the iOS snapToAlignment/snapToInterval combo on Android. Therefore, we are left with a bunch of hacks, workarounds and debug mode issues... I've done my best to tackle it, but some core things are either missing or buggy and I have no control at all over it.
Still, ideas and PR are always welcome ;-)

thanks for the fast reply @bd-arc ...yes I know about the snapToInterval issue in Android...a pity! that's actually the reason I tried your library ;)
I understand that this is not an issue that might not be easy to accomplish so I will close it for now.
I did try your lockScrollWhileSnapping property but had no success (still able to scroll more than 1 item when flinging).

Could we keep this open in case someone else has an alternative solution, I really need this for a project I'm working on :P

@CodeLuca Sure, but don't get your hopes too high for now ;-)
Unless the Facebook team implement a proper snapToInterval on Android and make the ScrollView component behave properly on this OS, we're kind of stuck...
FYI, I've been thinking about implementing a custom PanResponder on top of the FlatList to see if I can anyhow get the best of both worlds, but this is more work than I can handle at the moment...

@marcmo @CodeLuca Hi, do you have any solutions ?

@bd-arc Any new solutions or ideas?
I have this problem on Android :(

Sorry, please allow me to advertise for my open source library! ~
I think this library react-native-reanimated-carousel will solve your problem. It is a high performance and very simple component, complete with React-Native reanimated 2

For everyone still looking for a solution.
Use those properties from , worked wonders for me.
disableIntervalMomentum
pagingEnabled


CLI: Don't print CLI usage for common errors

e.g. user clicks on reject in the login flow.
We also print the error message twice.

+cc @jkhwu

Following options can be taken:

Silence printing help and only print the error.

Please note the help will still be printed if missing mandatory arguments/flags. This can also be fixed with custom handlers, if required(as done in gh-cli).
Print the error message and a custom help message like run project rename --help for further help.
Separate all errors into client/internal errors and print help message only in client/common errors. It will be a tedious task to separate all the errors and it may not be feasible to do so in all cases.

We will go ahead with approach 1.


Kumapage

Source name
KumaPage
Source link
https://kumapage.com/
Source language
Indonesia
Other details
No response
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

any update?

@jahe00 you can look at this issue request & see that there's no update.
Don't unnecessarily comment bump, all the work is done by contributors volunteering their time & willingness to creating/fixing the repo's extensions. There's 447~ open issues, and there's no guarantee or ETA. Wait (like you've been doing), use a different source, make it yourself, or find somewhere else.


expire after stop()

Its hard to come up with a sane expireIn time if a user is looking at a page. Who knows how long they will remain looking at it?
What if expireIn only starts after stop() is called? Thus, expireIn is the amount of time we hold on to that data after it is no longer needed. Else, we run the risk of getting rid of data before we leave the page.

That's why we don't allow(or better suggest) to do individual .stop().
It's better to clean the whole subsManager instance.
We can do something about this. Not sure exactly, what we really need to
implement.
On Wed, Mar 11, 2015 at 2:15 AM Chet Corcos<EMAIL_ADDRESS>wrote:

Its hard to come up with a sane expireIn time if a user is looking at a
page. Who knows how long they will remain looking at it?
What if expireIn only starts after stop() is called? Thus, expireIn is
the amount of time we hold on to that data after it is no longer needed.
Else, we run the risk of getting rid of data before we leave the page.
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/subs-manager/issues/31.

hmm.
if I subscribe to 1 million posts and 1 user like this:
s1 = subs.subscribe('posts', 1000000)
s2 = subs.subscribe('users', 1)

s1.ready() will ALWAYS equal s2.ready(). Meaning, the readiness of each subscription is not managed individually. It also means that both s1 and s2 will expire at the same time even if I create s2 minutes after s1...
I think this package would benefit from refactoring each subscription into its own object that manages its own expiration. As a developer who has been using this for a while, I entirely expected subscriptions to be managed independently...
I see you intent though. I really ought to create a different SubsManager for each of my subscriptions...
Any reason you don't use Meteor.setTimeout?


helm upgrade do not create new CRD in new chart.

Describe the bug
helm upgrade do not create new CRD in new chart.
To Reproduce
I have a chart with two version v1 and v2, v2  add a new CRD compared with v1

install with chart version  v1

helm install {release_name} --version v1

upgrade with chart version v2.  add a new CRD compared with v1.

helm upgrade --install {release_name} --version v2

Expected behavior
new CRD created after helm upgrade.
Versions (please complete the following information):

Ambassador: [e.g. 0.32.1]
Kubernetes environment [bare metal v1.16.2]
Version [3.2.4]

Additional context
Because release v1 has existed, so action/upgrade.go will  be executed finally, which seems not create new CRD.

This is on purpose. Changing a CRD can easily break a cluster. There is a good write-up at https://github.com/helm/community/blob/f9e06c16d89ccea1bea77c01a6a96ae3b309f823/architecture/crds.md. It explains why upgrades of CRDs are a manual step.


"TypeError: Cannot read property 'split' of undefined"  when deploy containers.

Hi everyone,
I was stucked in loading page of "http://<IP_ADDRESS>:8083/#/deploy" which shows "Launching Container" when I tried to deploy container .

Version
  shipyard version 3.0.2 (8e84bed)

  swarm version 1.0.1 (744e3a3)

configuration

a swarm cluster with 4 nodes

without docker-proxy

setup configuration

rethinkdb:
  image: registry.idc/rethinkdb:latest
  restart: always
  ports:
    - 8084:8080
  volumes:
    - ./rethinkdb_data:/data

shipyard:
  image: registry.idc/shipyard:latest
  restart: always
  ports:
    - 8083:8080
  links:
    - rethinkdb:rethinkdb
  command: server --rethinkdb-addr rethinkdb:28015 --rethinkdb-database "shipyard" --docker "tcp://<IP_ADDRESS>:3375" --enable-cors

And I found a bunch of  errors in Chrome console.

TypeError: Cannot read property 'Names' of null
    at shortestContainerName (containers.controller.js:288)
    at ContainersController.containerName (containers.controller.js:278)
    at angular.js:12474
    at Object.<anonymous> (angular.js:12883)
    at n.$digest (angular.js:14404)
    at n.$apply (angular.js:14675)
    at angular.js:16423
    at e (angular.js:4940)
    at angular.js:5328(anonymous function) @ angular.js:11706(anonymous function) @ angular.js:8619n.$digest @ angular.js:14430n.$apply @ angular.js:14675(anonymous function) @ angular.js:16423e @ angular.js:4940(anonymous function) @ angular.js:5328
angular.js:11706 TypeError: Cannot read property 'Names' of null
    at shortestContainerName (containers.controller.js:288)
    at ContainersController.containerName (containers.controller.js:278)
    at angular.js:12474
    at Object.<anonymous> (angular.js:12883)
    at n.$digest (angular.js:14404)
    at n.$apply (angular.js:14675)
    at l (angular.js:9725)
    at F (angular.js:9915)
    at XMLHttpRequest.C.onload (angular.js:9856)(anonymous function) @ angular.js:11706(anonymous function) @ angular.js:8619n.$digest @ angular.js:14430n.$apply @ angular.js:14675l @ angular.js:9725F @ angular.js:9915C.onload @ angular.js:9856
angular.js:11706 TypeError: Cannot read property 'split' of undefined
    at new ContainerDeployController (http://<IP_ADDRESS>:8083/app/containers/deploy.controller.js:18:38)
    at e (http://<IP_ADDRESS>:8083/bower_components/angular/angular.min.js:36:315)
    at Object.instantiate (http://<IP_ADDRESS>:8083/bower_components/angular/angular.min.js:36:432)
    at http://<IP_ADDRESS>:8083/bower_components/angular/angular.min.js:76:5
    at http://<IP_ADDRESS>:8083/bower_components/ui-router/release/angular-ui-router.min.js:7:23333
    at Z (http://<IP_ADDRESS>:8083/bower_components/angular/angular.min.js:70:149)
    at I (http://<IP_ADDRESS>:8083/bower_components/angular/angular.min.js:59:255)
    at g (http://<IP_ADDRESS>:8083/bower_components/angular/angular.min.js:51:335)
    at http://<IP_ADDRESS>:8083/bower_components/angular/angular.min.js:50:444
    at k (http://<IP_ADDRESS>:8083/bower_components/ui-router/release/angular-ui-router.min.js:7:22678) <div id="content" ui-view="" class="ng-scope">(anonymous function) @ angular.js:11706(anonymous function) @ angular.js:8619Z @ angular.js:8283I @ angular.js:7791g @ angular.js:7140(anonymous function) @ angular.js:7019k @ angular-ui-router.min.js:7(anonymous function) @ angular-ui-router.min.js:7n.$broadcast @ angular.js:14889y.transition.M.then.y.transition.y.transition @ angular-ui-router.min.js:7(anonymous function) @ angular.js:13318n.$eval @ angular.js:14570n.$digest @ angular.js:14386n.$apply @ angular.js:14675l @ angular.js:9725F @ angular.js:9915C.onload @ angular.js:9856

Are you sure you configured Shipyard to point to Swarm?  I've seen this
error when Shipyard is configured to use a Docker engine instead of Swarm.
On Tue, Jan 12, 2016 at 4:27 AM, Chufuyuan<EMAIL_ADDRESS>wrote:

Hi everyone,
I was stucked in loading page of "http://101143:8083/#/deploy" which
shows "Launching Container" when I tried to deploy container

Version
shipyard version 302 (8e84bed)
swarm version 101 (744e3a3)

configuration
1 a swarm cluster with 4 nodes
2 without docker-proxy
3 setup configuration
rethinkdb:
image: registryidc/rethinkdb:latest
restart: always
ports:
- 8084:8080
volumes:
- /rethinkdb_data:/data
shipyard:
image: registryidc/shipyard:latest
restart: always
ports:
- 8083:8080
links:
- rethinkdb:rethinkdb
command: server --rethinkdb-addr rethinkdb:28015 --rethinkdb-database "shipyard" --docker "tcp://101143:3375" --enable-cors
And I found a bunch of  errors in Chrome console
TypeError: Cannot read property 'Names' of null
at shortestContainerName (containerscontrollerjs:288)
at ContainersControllercontainerName (containerscontrollerjs:278)
at angularjs:12474
at Object (angularjs:12883)
at n$digest (angularjs:14404)
at n$apply (angularjs:14675)
at angularjs:16423
at e (angularjs:4940)
at angularjs:5328(anonymous function) @ angularjs:11706(anonymous function) @ angularjs:8619n$digest @ angularjs:14430n$apply @ angularjs:14675(anonymous function) @ angularjs:16423e @ angularjs:4940(anonymous function) @ angularjs:5328
angularjs:11706 TypeError: Cannot read property 'Names' of null
at shortestContainerName (containerscontrollerjs:288)
at ContainersControllercontainerName (containerscontrollerjs:278)
at angularjs:12474
at Object (angularjs:12883)
at n$digest (angularjs:14404)
at n$apply (angularjs:14675)
at l (angularjs:9725)
at F (angularjs:9915)
at XMLHttpRequestConload (angularjs:9856)(anonymous function) @ angularjs:11706(anonymous function) @ angularjs:8619n$digest @ angularjs:14430n$apply @ angularjs:14675l @ angularjs:9725F @ angularjs:9915Conload @ angularjs:9856
angularjs:11706 TypeError: Cannot read property 'split' of undefined
at new ContainerDeployController (http://101143:8083/app/containers/deploycontrollerjs:18:38)
at e (http://101143:8083/bower_components/angular/angularminjs:36:315)
at Objectinstantiate (http://101143:8083/bower_components/angular/angularminjs:36:432)
at http://101143:8083/bower_components/angular/angularminjs:76:5
at http://101143:8083/bower_components/ui-router/release/angular-ui-routerminjs:7:23333
at Z (http://101143:8083/bower_components/angular/angularminjs:70:149)
at I (http://101143:8083/bower_components/angular/angularminjs:59:255)
at g (http://101143:8083/bower_components/angular/angularminjs:51:335)
at http://101143:8083/bower_components/angular/angularminjs:50:444
at k (http://101143:8083/bower_components/ui-router/release/angular-ui-routerminjs:7:22678) (anonymous function) @ angularjs:11706(anonymous function) @ angularjs:8619Z @ angularjs:8283I @ angularjs:7791g @ angularjs:7140(anonymous function) @ angularjs:7019k @ angular-ui-routerminjs:7(anonymous function) @ angular-ui-routerminjs:7n$broadcast @ angularjs:14889ytransitionMthenytransitionytransition @ angular-ui-routerminjs:7(anonymous function) @ angularjs:13318n$eval @ angularjs:14570n$digest @ angularjs:14386n$apply @ angularjs:14675l @ angularjs:9725F @ angularjs:9915Conload @ angularjs:9856
—
Reply to this email directly or view it on GitHub
https://github.com/shipyard/shipyard/issues/723.

@ehazlett  this option  --docker "tcp://<IP_ADDRESS>:3375" pointed to a swarm manager whose role was replica.
By the way, the warm cluster has one primary manager with two replications.

I haven't seen this error.  You may try upgrading to the latest Swarm to see if it persists.

Thanks @ehazlett . I like shipyard.
And it is working fine so far even errors like below apear every time.
TypeError: Cannot read property 'Names' of null
    at shortestContainerName (containers.controller.js:288)
    at ContainersController.containerName (containers.controller.js:278)
    at angular.min.js:200
    at Object.<anonymous> (angular.min.js:108)
    at n.$digest (angular.min.js:123)
    at n.$apply (angular.min.js:127)
    at l (angular.min.js:81)
    at F (angular.min.js:85)
    at XMLHttpRequest.C.onload (angular.min.js:86)

I found "TypeError: Can not read property 'Names' of null" and the related container, when the container is null, this error occurs.
Proposed modification of the following methods:
function containerName(container)
//Check the container is not empty

Hey @dockerclub,
how did you find the container that is causing this error? I get the same, probably cause launching a container didn't work. 'docker ps' doesn't show the container, neither the image got pulled yet. But the chrome console outputs exact that message. If I debug the part it shows actually 2 containers already that are null.

@maxfriedmann  Yes, I was in the debug console when found, I feel the need to adjust all the filter container null, although I do not know how containers are null result.


0.89.4 pre release of 0.90

We're getting close. This PR has all the changes so far for 0.90.
I'm doing one more set of tests to ensure out-consolegridview is working great. If so, I plan on doing one more merge to create 0.90.0.

My accept of this SHOULD generate a new nuget package with v 0.89.4


Added computation of private jet emissions

Estimation is now based:

ICAO official numbers
consumption of the aircraft models, as advertised on websites selling private jets
research on Radiative Forcing and Life-cycle emissions

See changes to methodology.
For now only implemented for the single_day example, will push more soon.

Codecov Report
Attention: 19 lines in your changes are missing coverage. Please review.

Comparison is base (fa593c9) 82.53% compared to head (2dfb2bc) 80.49%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

src/private_emissions.rs
0.00%
13 Missing :warning:

src/consumption.rs
0.00%
6 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
- Coverage   82.53%   80.49%   -2.04%
==========================================
  Files          14       16       +2
  Lines         750      769      +19
==========================================
  Hits          619      619
- Misses        131      150      +19

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[improve][pulsar-io-kafka] Add option to copy Kafka headers to Pulsar properties

Fixes #17760
Motivation
Users of Kafka source today can't access their Kafka headers in Pulsar. This patch adds a config to enable this copy to take place in addition to some standard, useful Kafka headers.
Modifications

A new KafkaSourceConfig flag is added: copyHeadersEnabled of type boolean and default value of false
If the flag is toggle on, the following Kafka headers will be copied over to Pulsars properties.
__kafka_topic : the name of the Kafka topic consumed by the source.
__kafka_partition: the number of paritioed on the consumed kafka topics
__kafka_offset: the current offset of the kafka message currently consumed by the source
User defined header: The customer headers a Kafka producer could generated as pairs of <String, byte[]>. Since Pulsar properties are of type <String, String>, the Kafka byte[] values are based64 encoded.

Verifying this change

[X] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

Added unit tests to check the Kafka source respects the configs and generated the expected Pulsar properties map
Extended integration test for Avro Kafka source to generate headers and verify them on Pulsar side
Update : The integ test is blocked by https://github.com/confluentinc/schema-registry/issues/2390 and will be disabled for now.

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (add or upgrade a dependency) (no)
The public API (no)
The schema (no)
The default values of configurations (no)
The binary protocol (no)
The REST endpoints (no)
The admin CLI options (no)
Anything that affects deployment (no)

Documentation

[X] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

Matching PR in forked repository
PR in forked repository: https://github.com/aymkhalil/pulsar/pull/1

There is no need to add docs, as docs are automatically generated


Authentication issue

When running Connect-MSIntuneGraph -TenantName "aaa.onmicrosoft.com", and at a later stage Connect-MSIntuneGraph -TenantName "bbb.onmicrosoft.com", the new token does refreshed correctly to connect to the new tenant. I.e. it still connect to the "aaa.onmicrosoft.com"-tenant.
Running Connect-MSIntuneGraph with -PromptBehavior Always works, but then you have to authenticate every time.

That's unfortunately one of the downsides of my old auth module (that the Connect function originates from). I'm planning on switching to MSAL.PS in the next release, since ADAL as my own module/function is based on is eventually going away.

Could you please verify if the behavior is the same in version 1.3.0 that was just released? You should be able to supply the -Interactive switch now that the module uses MSAL.PS which should enforce an interactive prompt even if there's a token in the local cache.

Thanks Nicolai! I'm now able to connect to several tenants, using a multi-tenant service principal and authenticate once using the -DeviceCode switch in the first connect, and are not prompted for auth when connecting to a new tenant. Works great!

Works as expected now!


SDAG closures not opened for 'forall' header

Original issue: https://charm.cs.illinois.edu/redmine/issues/380

From Joseph Rock:
While working on my project, I noticed a neat little bug with the SDAG forall construct.
Let's say we want to execute a 'forall' inside a 'when' clause:
when entryMethodA(int totalIterations) {
  forall [i] (1 : totalIterations, 1) {
    //do work here
  }
}

The variable 'totalIterations' should be in scope for the 'forall' construct. But when we compile, the .def.h code gets a little bit wrong. It'll throw an error like "totalIterations" not in scope.
The offending line looks like: int __first = (1), __last = (totalIterations), __stride = (1);
This is the 'forall''s iteration construct. It appears that there is direct textual substitution from the SDAG code to the generated .def.h code.
Yet, the closures (such as entryMethodA) are passed to this method as parameters. Thus, the 'forall' generated code has access to the parameter called totalIterations. Instead of "totalIterations", though, it would be something like "gen0->getP0()"; (gen0 is the closure object representing the "when entryMethodA" scope)
Were 'forall's intended to have dynamic iteration? Given that it has access to its parent closures' parameters, I think it is in the realm of possibility.

Original date: 2013-12-20 16:53:05

As I noted in email:

I believe the issue described is that the closure in question should be 'opened' at the point where the forall bounds are being evaluated.
Jonathan agreed.

Original date: 2013-12-21 01:45:38

bug solved, see commit 0d5460af2a6ac48e241ec940f586bfb8f804c384

Original date: 2013-12-21 01:50:51

see gerrit issues for bug fix and corresponding test:
http://charm.cs.uiuc.edu/gerrit/#/c/26/
http://charm.cs.uiuc.edu/gerrit/#/c/27/


add KFP SDK dsl.If/Elif/Else docs

/hold
Merge after https://github.com/kubeflow/pipelines/pull/9781 is released

/assign @chensun

/assign @chensun
/hold until 2.2.0 is released

/unhold


FlatList doesnot load data after the initialNumToRender count exceeds.

Description
If the initial state of list is empty and it fills in componentDidMount the flatlsit will only render first 10 items from the list of 60.
It doenot renders the item after the initialNumToRender count.
React Native Version
0.71.5
Output of npx react-native info
System:
OS: macOS 12.6
CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
Memory: 37.58 MB / 8.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.13.0 - /usr/local/bin/node
Yarn: Not Found
npm: 8.19.3 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>53283
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.17 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.1 => 0.71.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
class MyRoomsScreen extends Component {
constructor(){
super()
this.state = {
data: []
}
componentDidMount(){
loadData()
}

loadData(){
let roomArray = []
for(let i =0; i<30;i++){
roomArray.push({id: i+1; name: `Room ${i+1}` })
}
this.setState({data: roomArray})
}

renderRoomList =({item, index}) => {
return(<Text>{item.name} </Text>)
}

render(){
return(
<View>
<FlatList data={this.state.data} renderItem={this.renderRoomList}   />
</View>
)}

Snack, code example, screenshot, or link to a repository
...

I am having this same issue and was able to create a snack showing the behavior.
Snack:
https://snack.expo.dev/wsw-_9se4
Screen Recording showing the behavior:
https://user-images.githubusercontent.com/567834/230643168-d2851cdc-6586-44ce-a605-7e18779f074e.mov

Would need to be debuged, but a likely culprit for why the lost wouldn't render content beyond initial is that something is that InteractionManager is in a Starved state and scheduled work is never run https://github.com/reactwg/react-native-releases/discussions/6.

I have done an upgrade from RN 0.67.3 to RN 0.71.4 few days ago and i got the same result. Same with a downgrade to 0.69.9.
If no initialNumToRender is set, flatList is working fine but you have to render 10 items on the launch, not the best way.
When initialNumToRender is set and we exceed the number defined, it render but nothing appear on the screen so blank screen so i think it's the same issue.

So what i saw is if i have the list in the constructor itself rather than an empty array Flatlist works as expected but if i have an empty list in constructor and updates the list in componentDidmount/useEffect it only renders the item till initialNumToRender count.

defined

I have this issue too. When I set initialNumToRender={0} it renders blank. And doesn't update later

I have done an upgrade from RN 0.67.3 to RN 0.71.4 few days ago and i got the same result. Same with a downgrade to 0.69.9. If no initialNumToRender is set, flatList is working fine but you have to render 10 items on the launch, not the best way. When initialNumToRender is set and we exceed the number defined, it render but nothing appear on the screen so blank screen so i think it's the same issue.

I have this issue too. When I set initialNumToRender={0} it renders blank. And doesn't update later

I was with the same issue few weeks ago but with 0.71.6 and even 0.71.7 with the fix of Hermes in debug mode, everything's working fine.
Give a try guys, my app SoSkills on store is working on 0.71.7 with initialNumToRender to 3 and no blank screen after this value.

I am having the same issue, it doesn't load data after  initialNumToRender count exceeds.

I had the same problem with SectionList. In my case, the problem was that I forgot to clear the InteractionManager after createInteractionHandle(). I am using react-native 0.71.6 with Expo 48.
@NickGerleman Thanks for your comment about the InteractionManager. I didn't realise it blocked the FlatList behaviour.

What i have noticed is it does not rerender if it has empty list in the constructor.
If the list is filled in constructor itself 2 rerender happens and FlatList works perfectly.

in my case for the first time, all the data was successfully rendered, but when I tried to go back until I exited the application and opened it again, only 10 data were displayed, and there was an empty space below, no data was displayed, but when I killed the app and opened it again, all of them running back to normal
I don't know why this is, this happened when I updated to React Native 0.71.XX
so now I still stay at RN 0.70.13
Has anyone experienced something similar in RN 0.71.XX?

Started running into this after updating to RN 0.72.6, which is the latest version as of today.
Something got broken in FlatLists recently

We have updated the react-native to 0.71.13 after that same issue is happening. Sometime scroll is not working, sometime all items are not rendering. These are all happening due to "initialScrollIndex" props. Please provide any solutions for it.

anyone solved this issue it has been 5 months now
it seems that the only solution till now is to not send empty data in the initial render to (flatlist/sectionlist) which will break the ListEmptyComponent behaviour

anyone solved this issue it has been 5 months now it seems that the only solution till now is to not send empty data in the initial render to (flatlist/sectionlist) which will break the ListEmptyComponent behaviour

my render not empty, but back until exit app and open again this happen. but if I killed the app and opened it again, all of them running back to normal

I have fixed this issue for my case and am sharing this if anyone has the same issue
our issue was that interactionManager was blocked due to animation and other interactions looped in the background
how do you identify that issue related to interactionManager
put this log on your screen
InteractionManager.runAfterInteractions(() => console.log("running")
if you didn't get the log that's mean you have something blocking flatlist/sectionlist from loading more items
however, after we identify the issue we go across all the app even in node_modules, and disable all animation and interactionManager also panresponder
and trying the sectionlist is all working fine
so for our issue, we starting to return all animation peace by peace to find what exactly blocking and we have
found 2 issues caused this problem
1- ShimmerPlaceholder package we are using without sending isInteraction={false}
2- we are having logic depend on PanResponder across all the app to calculate the user's inactive/active time
so on onStartShouldSetPanResponderCapture and onPanResponderGrant based on your logic you should access the interactive handler by yourself and terminate it
example to get the panresponder handler and kill it
handle = React.createRef()
 onStartShouldSetPanResponderCapture: () => {
                this.handle.current =  this._panResponder.getInteractionHandle()
                //logic
                this.handle.current !== null && InteractionManager.clearInteractionHandle(this.handle.current);
                return false;
        }

I think react-native should implement a way at least to warn developers that there are other interactive running and blocking (flatlist/sectionlist) to do their job

In my case, I replaced the FlatLists with FlashLists.
I looked for stuck interactions but couldn't find anything. Maybe some third-party library that we're using got broken recently, but it's hard to tell.

+1 I encouter this issue

{this.state.list && this.state.list.length > 0 ? <SectionList
style={{flex: 1, zIndex: -5}}
bounces={true}
sections={this.state.list}
renderSectionHeader={this._renderSection}
renderItem={this._renderItem}
keyExtractor={(item, index) => item?.id + index}
stickySectionHeadersEnabled={true}
stickyHeaderIndices={[1]}
showsVerticalScrollIndicator={false}
ListHeaderComponent={<View style={{height: 1, width: 1,}}/>}
ListFooterComponent={<View style={{height: 1, width: 1,}}/>}
/> : null}
refresh the data twice to display all the data, refresh the data once to display 10 pieces of data

@jianxinzhoutiti Thats how list work in Rn if you don't pass an initialNumberToRender props it will take its default value which is 10. and in the next rerender which is on componentDidMount it will render all the list item.

@jianxinzhoutiti这就是列表在 Rn 中的工作方式，如果您不传递 initialNumberToRender 属性，它将采用默认值 10。并且在 componentDidMount 上的下一个重新渲染中，它将渲染所有列表项。

I just open and close the page，The expectations should show all the data，But a few times it's only 10 items

This is really quite a serious issue that's preventing data from loading for users. I'm on 0.72.4, and my guess is it's not fixed even on 0.72.6.
The "hack" right now is to switch key on the flatlist so that it completely re-renders but it's such a hack! This way your ListEmptyComponent will work and you don't have to refactor too much once this actually does get fixed.

Hi There, I made a fix for this issue. Hope it will help you.
File<EMAIL_ADDRESS>Change from this:
  schedule() {
    if (this._taskHandle) {
      return;
    }
    const timeoutHandle = setTimeout(() => {
      this._taskHandle = InteractionManager.runAfterInteractions(() => {
        // Note that we clear the handle before invoking the callback so that if the callback calls
        // schedule again, it will actually schedule another task.
        this._taskHandle = null;
        this._callback();
      });
    }, this._delay);
    this._taskHandle = {cancel: () => clearTimeout(timeoutHandle)};
  }

into this:
schedule(renderWithoutInteractions_patch) {
   if (this._taskHandle) {
     return;
   }
   const timeoutHandle = setTimeout(() => {
           if(renderWithoutInteractions_patch){
                 // Note that we clear the handle before invoking the callback so that if the callback calls
                 // schedule again, it will actually schedule another task.
                 this._taskHandle = null;
                 this._callback();
             }else{
               this._taskHandle = InteractionManager.runAfterInteractions(() => {
                 // Note that we clear the handle before invoking the callback so that if the callback calls
                 // schedule again, it will actually schedule another task.
                 this._taskHandle = null;
                 this._callback();
               });
             }
   }, this._delay);
   this._taskHandle = {cancel: () => clearTimeout(timeoutHandle)};
 }

file<EMAIL_ADDRESS>Search for the function: _scheduleCellsToRenderUpdate, and change from this:
    } else {
    this._updateCellsToRenderBatcher.schedule();
  }

into this:
this._updateCellsToRenderBatcher.schedule(this.props.renderWithoutInteractions_patch);

file<EMAIL_ADDRESS>Add the prop type and proper docs:
Look for the updateCellsBatchingPeriod prop, and add the renderWithoutInteractions_patch prop type after it, together with the comment.
  /**
  * Amount of time between low-pri item render batches, e.g. for rendering items quite a ways off
  * screen. Similar fill rate/responsiveness tradeoff as `maxToRenderPerBatch`.
  */
 updateCellsBatchingPeriod?: number | undefined;

 /**
  * Only use this prop when having re-rendering issuess.
  * This prop will disable the runAfterInteractions inside the .schedule method, inside the Batchinator file.
  * Use this prop carefully :)
  */
 renderWithoutInteractions_patch?: boolean | undefined;

last thing: user the prop on your flatlist.
            <FlatList
              renderWithoutInteractions_patch
              style={styles.flatlist}
              contentContainerStyle={styles.flatlistContent}
              ... the rest of your code

thank you @iMonk777 for this investigation, it's rather surprising this issue with such a basic component is not taken seriously by react native team :/
does your patch have any unexpected side effect?
or performance issue?
it's rather hard to test it and confirm of how well it works since the issue just happens randomly and is hard to replicate

No worries @pierroo :)
I've been using the patch for around 6 months now, in three different projects, and I didn't have any performance issues or any other issues due to the patch(like crashes).
The only thing I found strange, when patching it on my latest project, I couldn't patch it properly until I manually added the dependency in the package.json like so:

It seems that npx patch-package was not happy with patching a peer dependency of react-native, if it was not added to the package.json. I'm not sure though how it worked in the past, for my other two projects ^.^

I checked the dependency @react-native/virtualized-lists of react-native, to see the correct version.
For this, go to node_modules/react-native/package.json, then look for the @react-native/virtualized-lists. copy the entire line and add it in the dependencies object of your package.json.
Make the changes you need(from my initial message), then run npx patch-package @react-native/virtualized-lists.
It doesn't seem to be a package just called @react-native instead there are a bunch of packages with this name, so they are added to this folder.

awesome, thanks for the detailed explaination.
I'm just gonna use your patch, but then are we sure just changing the file version in the name won't break?
like in your files there are lines number involved etc for patch package to know where to look for;
so IF virtualized list had any change between 0.72.8 and 0.73.4, that probably will break.
(although most probably such a core component wasn't touched in between)

@iMonk777 Your patch looks great! Are you planning to create a PR for it to be merged? 😊

initialNumToRender should be enough to fill the screen but not much more.In my case, the height of item is too small, so I set initialNumToRender={30} to fill the screen.

In my case, using Animated so frequently leads to not loading more items.
Because animation fills the interactionSet of InteractionManager, callbacks cannot be run forever.
So, I patched @iMonk777 's solution because I needed to animate my component anyway

For people still having issues you might want to check your elements aren't using margin. That makes the flat list buggy sometimes it works sometimes it doesn't without any kind of logical reason. It was failing to render properly around 20% of the time but without using margins and replacing them for padding it works perfectly all the time.

initialNumToRender should be enough to fill the screen but not much more.In my case, the height of item is too small, so I set initialNumToRender={30} to fill the screen.

thank you for this, in my case, I'm realized my item height is not set.

I was facing the same
I was not able to find any solution
I had to use the initailNumToRender to all items

in my case onEndReached not trigrered

I was facing the same (or similar) issue - tho' with SectionList. A workaround that seems to work for me is not to render a empty list (while data is loading). Other observations:

the bug was not present on a android emulator but was present on physical android phone (i.e. might be device/display dependent)
when the list is only rendering the initialNumToRender amount of items, changing the list component height "resolves" the bug and more items are rendered
the InteractionManager.runAfterInteractions(() => console.log("running") was not logging anything when the bug was present


Activity ❓❓❓

@yoshuawuyts is there any activity on this? Are we accepting contributions here? I've attempted to contribute to page.js but it's hella stagnant. Having problems using this tool with es6 imports via http://rollupjs.org . Looking to make a contribution. Thanks in advance!

Hey @snuggs. You can get your answer from https://github.com/yoshuawuyts/wayfarer/commits/master and npm as well. The last release was done 7 days ago. Feel free to send your PR!

Thanks @mcollina! Also, Is there any reason wayfarer doesn't subscribe to the window.history API? This is one feature I think would be a great addition. What say you?
https://developer.mozilla.org/en-US/docs/Web/API/History_API#Example_of_pushState()_method

wayfarer has no opinions on where it's used. If you're looking for a
specialized frontend router that handles the history API
https://github.com/yoshuawuyts/sheet-router/blob/master/history.js might be
closer to what you're looking for ✨
On Sat, Nov 26, 2016 at 6:53 AM snuggs<EMAIL_ADDRESS>wrote:

Thanks @mcollina https://github.com/mcollina! Also, Is there any reason
wayfarer doesn't subscribe to the window.history API? This is one feature I
think would be a great addition. What say you?
https://developer.mozilla.org/en-US/docs/Web/API/History_API#Example_of_pushState()_method
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yoshuawuyts/wayfarer/issues/49#issuecomment-263046054,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWlel_RrlhnLjoAdbBi4zGCeltUfGbRks5rB8lagaJpZM4K8qIK
.

oh i see @yoshuawuyts. Only thing about sheet router is the API is a bit funky. Wayfarer's is far sexier. ;-)

Thanks for the input gentlemen. @yoshuawuyts @mcollina. Closing issue.


'This Team' as the default

By default, the app shows 'Pinned List'.  Is there a way to have this screen open 'This Team' by default?

I have resolved this by adding code to select the 'This Team' button once the screen has finished loading.


Enable seccomp on ppc64le

In order to do this, allow the socketcall syscall in the default
seccomp profile. This is a multiplexing syscall for the socket
operations, which is becoming obsolete gradually, but it is used
in some architectures. libseccomp has special handling for it for
x86 where it is common, so we did not need it in the profile,
but does not have any handling for ppc64le. It turns out that the
Debian images we use for tests do use the socketcall, while the
newer images such as Ubuntu 16.04 do not. Enabling this does no
harm as we allow all the socket operations anyway, and we allow
the similar ipc call for similar reasons already.
Signed-off-by: Justin Cormack<EMAIL_ADDRESS>See #22537 #22565 for the previous enable, disable of this feature due to the tests failing.
cc @tophj-ibm

The powerpc builder looks to me like it has an older config (?) and is trying to build using gccgo, it seems fine on the Ubuntu 16.04 box I am testing on...

On the other hand janky actually seems to be erroring on a seccomp test.

retest this please

retest this please

it's all green now! LGTM
ping @jfrazelle in case you wanted to have a quick peek

Nice catch, running a test build now. Yeah, the power PR job needs some desperate updating.

@justincormack hmm you get this failure?
----------------------------------------------------------------------
FAIL: docker_cli_run_test.go:3037: DockerSuite.TestRunUnshareProc

docker_cli_run_test.go:3086:
    c.Fatal(err)
... Error: privileged unshare with apparmor should have failed with 'mount: cannot mount none' or 'permission denied', got: , <nil>

----------------------------------------------------------------------

Looks good to me, Justin is killing it :D

No I am not getting that on my machine I don't think. I have a couple of
intermittent test failures though, which I am going to look at, they didn't
look ppc specific.
On 24 May 2016 8:06 a.m., "Christopher Jones"<EMAIL_ADDRESS>wrote:
@justincormack https://github.com/justincormack hmm you get this failure?

FAIL: docker_cli_run_test.go:3037: DockerSuite.TestRunUnshareProc
docker_cli_run_test.go:3086:
c.Fatal(err)
... Error: privileged unshare with apparmor should have failed with
'mount: cannot mount none' or 'permission denied', got: ,

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/22922#issuecomment-221300031

thanks @jfrazelle

LGTM - @tophj-ibm do you want us to hold off merge until you resolve/validate the UnshareProc failure you have locally?

@estesp yeah, let me look into it a little more if you don't mind 😄

so that one probably has a lot to do with apparmor, crap I wish I still had
access to the power server we had I have ideas, 1. try running aa-status on
the host
On Tue, May 24, 2016 at 8:44 AM, Christopher Jones<EMAIL_ADDRESS>
wrote:

@estesp https://github.com/estesp yeah, let me look into it a little
more if you don't mind 😄
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/22922#issuecomment-221312372

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

Oh I know this! What is the unshare version in the container
On Tue, May 24, 2016 at 8:48 AM, Jessica Frazelle<EMAIL_ADDRESS>wrote:

so that one probably has a lot to do with apparmor, crap I wish I still
had access to the power server we had I have ideas, 1. try running
aa-status on the host
On Tue, May 24, 2016 at 8:44 AM, Christopher Jones <
<EMAIL_ADDRESS>wrote:

@estesp https://github.com/estesp yeah, let me look into it a little
more if you don't mind 😄
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/22922#issuecomment-221312372

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu
http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

ooh is this the buggy unshare that we used to test against? Unshare in the container is 2.25.2

Yeah! so we switched to the one in debian for the regular builds I wonder
if we should try that on power as well
On Tue, May 24, 2016 at 8:59 AM, Christopher Jones<EMAIL_ADDRESS>
wrote:

ooh is this the buggy unshare that we used to test against? Unshare in the
container is 2.25.2
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/22922#issuecomment-221317153

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

The only test failure I had on the last run was
FAIL: docker_cli_userns_test.go:22: DockerDaemonSuite.TestDaemonUserNamespaceRootSetting

[d22357000] waiting for daemon to start
[d22357000] daemon started
docker_cli_userns_test.go:44:
    c.Assert(err, checker.IsNil, check.Commentf("Output: %s", out))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc82298a460), Stderr:[]uint8(nil)} ("exit status 125")
... Output: dbc79b5458b7a15ce641708c2fbc8a2b7f9e1ba12c79bd457c9121c070c1464d
/go/src/github.com/docker/docker/bundles/1.12.0-dev/test-integration-cli/../dynbinary-client/docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: rootfs_linux.go:53: mounting \"/dev/mqueue\" to rootfs \"/go/src/github.com/docker/docker/bundles/1.12.0-dev/test-integration-cli/d22357000/root/427680.427680/overlay/a0294a82d960158aadccaa92b24839b8598f2182137d9e8d92057cd8252dc378/merged\" caused \"device or resource busy\"".

But the failures are intermittent. Looks like they are all unrelated, so could fix in separate PRs.

@jfrazelle if you want access to ppc64le machines you can sign up to the IBM partner program and sign up for the Power dev program and get as much access as you like...

That's a temporary issue with the 16.04 kernel and mqueue protections when in a user ns; fix is in flight and should be in an update kernel in 3 weeks.
Sent from my iPhone

On May 24, 2016, at 12:36 PM, Justin Cormack<EMAIL_ADDRESS>wrote:
The only test failure I had on the last run was
FAIL: docker_cli_userns_test.go:22: DockerDaemonSuite.TestDaemonUserNamespaceRootSetting
[d22357000] waiting for daemon to start
[d22357000] daemon started
docker_cli_userns_test.go:44:
c.Assert(err, checker.IsNil, check.Commentf("Output: %s", out))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc82298a460), Stderr:[]uint8(nil)} ("exit status 125")
... Output: dbc79b5458b7a15ce641708c2fbc8a2b7f9e1ba12c79bd457c9121c070c1464d
/go/src/github.com/docker/docker/bundles/1.12.0-dev/test-integration-cli/../dynbinary-client/docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: rootfs_linux.go:53: mounting "/dev/mqueue" to rootfs "/go/src/github.com/docker/docker/bundles/1.12.0-dev/test-integration-cli/d22357000/root/427680.427680/overlay/a0294a82d960158aadccaa92b24839b8598f2182137d9e8d92057cd8252dc378/merged" caused "device or resource busy"".
But the failures are intermittent. Looks like they are all unrelated, so could fix in separate PRs.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@estesp ah thanks.

ah cool!
On Tue, May 24, 2016 at 9:49 AM, Justin Cormack<EMAIL_ADDRESS>wrote:

@estesp https://github.com/estesp ah thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/22922#issuecomment-221332807

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

@justincormack tested it on 3 more machines including the jenkins ones and everything seems to be working correctly so seems good to me. Thanks and congrats!
@jfrazelle thanks for the help as well! I checked and the power and x86_64 unshare debian versions which the test runs seem to be the same, so I'm thinking it was just something weird with the vm I was testing on.

Note this also fixes https://github.com/docker/docker/issues/23059

Has the fix estesp mentioned been pushed out yet?

@mkaplanACS doesn't look like it's in the kernel yet, but you can view the fix here http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=master-next&id=3487456d46869b41ce13970394ab3378da49fc1a , and there is a docker issue open for it here  https://github.com/docker/docker/issues/22633


Feature/ts codesandbox

Fix some of the v6 documentation. Also use resolver instead of validationResolver in v6 codesandbox, in preparation for v6 launch.

Thank you so much all for those contributions!


Seems Django-Raster now supports python 3.8 with 0.8.1 ?

Can it be that the latest update also added support for python 3.8? Before I was not able to parse raster with 3.8 and had to downgrade to 3.6.  But then again I am also using now latest gdal docker image(osgeo/gdal:ubuntu-small-latest) .

Thanks, you might want to update then https://pypi.org/project/django-raster/   python version supported.

I accidentally used again previous version of Django-Raster(0.8) with python 3.8 and got Raster algebra errors. When upgrading again to 0.81 the problem was solved again.
I got an error with previous version(0.8)  in combination with python 3.8 when using an url like:
return /raster/tiles/${this.id}/{z}/{x}/{y}.png?colormap=${this.getFilteredColorMap()};
but not when using  a url like:
``/raster/algebra/{z}/{x}/{y}.png?layers=r:0=${this.id},g:1=${this.id},b:2=${this.id}&alpha ;


Add additional bounds to Float trait

Adding these bounds allow trait bounds on Float in dependent crates to be simplified. These simplifications were made in linfa-clustering.

I will look into the issue with argmin first, before mergin this

can confirm that this is a regression introduced by the latest nightly compiler version, can you pin the toolchain to nightly-2021-03-26 in .github/workflows/checking.yml for the time being?

you need to do the same for .github/workflows/codequality.yml

sorry I'm a bit busy right now working through my backlog :sweat_smile:


Update "community" files

Update the "community" files - such as Issue Templates, Code of Conduct, Contributing guide - so that the developer experience is improved.
Of particular importance are improvements that help new contributors to get involved.

The code quality checks can safely be ignored for this PR as they relate to the use of "[" and "]" in the Issue template.

Hey @joshghent, I added these new files based on recommendations from GitHub for supporting new contributors to an open-source project. I also added a my name and "and contributors" to the license since there's a fe contributors now.
The Code of Conduct is based on an existing popular code. It's one of the ones GH offers in their code of conduct generator. The Code of Conduct requires an email for reporting issues (of contributors not following the Code; not bug issues). I added an email address of my own but I'd advise you change it to your own (git) email.
Since this is project management / contributing stuff, I'll leave this open for your approval.

Great work mate @jamescallumyoung - thanks for writing this, nice to have a clear policy in place for these things. Well done mate 👍


operator tektoncd-operator (0.69.1)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ x Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

cc @vdemeester

/approve

/hold

/hold cancel

/merge possible

/merge possible


Add .travis.yml and fix doc tests

See https://github.com/rust-lang/rust/issues/49935
@freebroccolo Can you enable travis testing for this repo? (Or if you rather I fork this then I can enable it on the fork instead).

Should be enabled now.

By the way I am willing to transfer ownership of the repo to you if it makes it easier to manage. Let me know what you prefer.

I'd be happy to take over ownership, were going to add that I'd like to setup status checks etc as well and stuff like that may need tweaking over time.

I think for things like that it might be enough to increase the permissions on this repo though.

I just checked but I'm not seeing a way to adjust permissions at that level. I think you can do it for an organization but I'm not sure if it's possible for an individual repo. Anyway, I tried to transfer but it tells me marwes/pretty.rs already exists. I think you will need to rename your fork first.

Deleted my fork which should do it.


Proposal for Aries Bifold to join the OpenWallet Foundation

At the next Bifold UG meeting on Jan 16th I'll broach the subject of joining the OpenWallet Foundation (OWF). This will be an opportunity to speak in favour of, or agains the subject or just listen in. At the meeting following this, on Jan 30th, the maintainers can vote on the subject; should they be in favour of joining OWF, then, we will begin the process (which I'll outline on Jan 16th).
Please note that, if Aries Bifold elects to join, that outcome is not guaranteed. A favourable vote will jump-start the mechanics of the application process.
Cc. Maintainers
@amanji
@bryce-mcmath
@cvarjao
@JamesKEbert
@jcdrouin21
@MosCD3
@ryankoch13
@thiagoromanos
@wadeking98
Cc. FYI
@swcurran
@ryjones

@tkuhrt

At the last Aries Bifold UG meeting, we ratified the decision to put forward a proposal to join the OpenWallet Foundation (OWF). PR #1089 submits said proposal for posterity. Once approved and merged, the next step will be to take the document and create a pull request against the OWF project proposals and present to their technical committee.

hi, @jleach . will this be a part of credo, or a distinct project?


Add link to robojava plugin

Robojava is a Gradle plugin to integrate Robolectric tests into Android Studio

I appreciate the pull request, but I don't think this repo is the right place to advertise for your plugin.


Couldn't start the training

I am using WSL2 Ubuntu to run this tool.
The training was killed just after it started. (after 25% of loading checkpoint shards. The graphic card my PC is using is an RTX4060Ti 16Gb. I hope it is not too much for it.
(diffusion-pipe) user@my-PC:~/diffusion-pipe$ NCCL_P2P_DISABLE="1" NCCL_IB_DISABLE="1" deepspeed --num_gpus=1 train.py --deepspeed --config examples/hunyuan_video.toml
[2024-12-29 14:24:37,343] [INFO] [real_accelerator.py:222:get_accelerator] Setting ds_accelerator to cuda (auto detect)
[2024-12-29 14:24:40,116] [WARNING] [runner.py:215:fetch_hostfile] Unable to find hostfile, will proceed with training with local resources only.
[2024-12-29 14:24:40,116] [INFO] [runner.py:607:main] cmd = /home/user/miniconda3/envs/diffusion-pipe/bin/python -u -m deepspeed.launcher.launch --world_info=eyJsb2NhbGhvc3QiOiBbMF19 --master_addr=<IP_ADDRESS> --master_port=29500 --enable_each_rank_log=None train.py --deepspeed --config examples/hunyuan_video.toml
[2024-12-29 14:24:41,058] [INFO] [real_accelerator.py:222:get_accelerator] Setting ds_accelerator to cuda (auto detect)
[2024-12-29 14:24:42,384] [INFO] [launch.py:139:main] 0 NCCL_IB_DISABLE=1
[2024-12-29 14:24:42,384] [INFO] [launch.py:139:main] 0 NCCL_P2P_DISABLE=1
[2024-12-29 14:24:42,384] [INFO] [launch.py:146:main] WORLD INFO DICT: {'localhost': [0]}
[2024-12-29 14:24:42,384] [INFO] [launch.py:152:main] nnodes=1, num_local_procs=1, node_rank=0
[2024-12-29 14:24:42,384] [INFO] [launch.py:163:main] global_rank_mapping=defaultdict(<class 'list'>, {'localhost': [0]})
[2024-12-29 14:24:42,384] [INFO] [launch.py:164:main] dist_world_size=1
[2024-12-29 14:24:42,384] [INFO] [launch.py:168:main] Setting CUDA_VISIBLE_DEVICES=0
[2024-12-29 14:24:42,385] [INFO] [launch.py:256:main] process 1893 spawned with command: ['/home/user/miniconda3/envs/diffusion-pipe/bin/python', '-u', 'train.py', '--local_rank=0', '--deepspeed', '--config', 'examples/hunyuan_video.toml']
[2024-12-29 14:24:43,325] [INFO] [real_accelerator.py:222:get_accelerator] Setting ds_accelerator to cuda (auto detect)
[2024-12-29 14:24:45,680] [INFO] [comm.py:652:init_distributed] cdb=None
[2024-12-29 14:24:45,680] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
The config attributes {'tile_sample_min_size': 256} were passed to AutoencoderKLCausal3D, but are not expected and will be ignored. Please verify your config.json configuration file.
2024-12-29 14:24:47.246 | INFO     | utils.patches:load_text_encoder:64 - Loading text encoder model (llm) from: /home/user/diffusion-pipe/models/llm
Loading checkpoint shards:  25%|██████▊                    | 1/4 [00:03<00:09,  3.08s/it][2024-12-29 14:24:54,545] [INFO] [launch.py:319:sigkill_handler] Killing subprocess 1893
[2024-12-29 14:24:54,598] [ERROR] [launch.py:325:sigkill_handler] ['/home/user/miniconda3/envs/diffusion-pipe/bin/python', '-u', 'train.py', '--local_rank=0', '--deepspeed', '--config', 'examples/hunyuan_video.toml'] exits with return code = -9

When the process is killed while doing the initial model loading, it means you ran out of free RAM (not VRAM). How much memory does your computer have? I've heard that everything can work with 32GB. But I don't use WSL. Maybe you need to set some config to allocate more memory to linux? I'm not sure how that works.

Thanks for your reply. I doubt that's the issue then. My PC has only 16GB of RAM, and I allocated only 8GB to Linux.
Fortunately, that is not an expensive fix. Let me search for a new RAM in the marketplace and see if I can solve the issue. I will keep you updated.

I upgraded my PC to 64GB. The training could start. I allocated 32GB to Linux.
Although I still have an issue with my dataset, the Lora training couldn't be started. It is out of the scope of this thread, and the issue here is solved.
The RAM usage peaked at 40GB. I believe 64GB of RAM would be necessary while running with WSL.