Problem displaying metadata on LCD if using esp board package version 2.0.2.

Thanks a million for this brilliant library, I'm just having a slight issue finishing a project I'm working on. Having made the track title and artist scroll across an LCD screen quite nicely using the following code (using the latest library zip and esp1.0.6, in arduino IDE 1.8.19 and 2.0):
void avrc_metadata_callback(uint8_t id, const uint8_t *text) {

  char lcd_buf[40];  // Check the size you need
  char lcd_buf1[40];  // Check the size you need
  if (id == 0x1)
    snprintf(lcd_buf, 40, "%s                                ", text);

  if (id == 0x2)
    snprintf(lcd_buf1, 40, "%s                                ", text);
  lcd.setCursor(0, 0);
  lcd.print(lcd_buf);

  lcd.setCursor(0, 1);
  lcd.print(lcd_buf1);

  Serial.printf("==> AVRC metadata rsp: attribute id 0x%x, %s\n", id, text);
}

With this in the loop:
{ for (int positionCounter = 0; positionCounter < 16; positionCounter++) {
      //      scroll one position left:

      if (millis() - times > 250)

      {

        lcd.scrollDisplayLeft();
        times = millis();           //and reset time.
      }
    }

When I added some volume functionality and updated the ESP board package to 2.0.2 to include the extra AVRC commands, the lcd stopped displaying the metadata, just some garbled symbols scrolling super fast for the most part with the odd correct word or two (but it was still coming through to the serial monitor ok). I've tried different boards in the board manager (also versions 2.0.0 and 2.0.1) and used the LCD with both serial and I2C interfaces with no luck. Any help would be greatly appreciated.
Cheers.

Yes, standard 2x16 LCD, address is 0x27, SDA=GPIO21, SCL=GPIO22 (I changed the default I2S pin to 23 from 22 to accommodate this). I didn't think it was the I2C interface though, as I've tried it without the IC2, using LiquidCrystal lcd(19, 23, 18, 17, 16, 15);
Also, it displays a static welcome message I've put in the setup function fine and only gets confused with the metadata its being sent.
Originally I was prototyping without the I2C interface as I didn't have one to hand, then I encountered this problem and ordered an interface thinking it might solve it.

Ahh, that makes sense, thanks. So it was probably fluke that it worked in the first place.
When I tried using the above code but moving lcd.print(lcd_buf)  to the loop, I get 'lcd_buf' was not declared in this scope
Could you give me a pointer as to how to save and recall the variables? I'm very much a beginner in all this, as you can tell.


[CEG-1719] updated sfn abi & added functions

@vsai I removed those functions & upgraded the version, please review.


Updated the biz questions and added the InputPasted event

Calculator Diagnostic Data Spec
Feature Pitch Link: Microsoft/calculator#525

FYI, you probably want to merge this directly into master at this point, since this is just a minor spec update.

Also, we should remove the diagnosticData feature branch.


Add support for flink 1.9

I am running some experiments lately using flink-siddhi and I saw that flink 1.9 is not supported. Is suppoting flink 1.9 in the near-feature roadmap? If so, I might be interested in collaborating with this.

Hi @salvalcantara Great to know that you are interested in collaborating on flink 1.9, your contribution is very welcome.

@haoch Thanks for assigning, I will hopefully work on this during next week.

Good to know that and look forward to your PR @salvalcantara 👍

Ey @haoch just to inform that I've been busier than expected....I will finally start working on this next week. Also (off-topic), have you considered offering a UDF as part of your library (for instance, a coprocess function?) ... I have been experimenting with this approach lately and seems a plausible alternative to relying on the lower-level Operator API.

Hi @haoch, the offensive lines when trying to run on Flink 1.9 come from the DynamicPartitioner class, which implements the StreamPartitioner interface. The thing is that, in Flink 1.9, the selectChannels method has changed to selectChannel as illustrated below:
    // Original: working for Flink 1.7
    //@Override
    public int[] selectChannels(SerializationDelegate<StreamRecord<Tuple2<StreamRoute, Object>>> streamRecordSerializationDelegate,
                                int numberOfOutputChannels) {
        Tuple2<StreamRoute, Object> value = streamRecordSerializationDelegate.getInstance().getValue();
        if (value.f0.isBroadCastPartitioning()) {
            // send to all channels
            int[] channels = new int[numberOfOutputChannels];
            for (int i = 0; i < numberOfOutputChannels; ++i) {
                channels[i] = i;
            }
            return channels;
        } else if (value.f0.getPartitionKey() == -1) {
            // random partition
            returnChannels[0] = random.nextInt(numberOfOutputChannels);
        } else {
            returnChannels[0] = partitioner.partition(value.f0.getPartitionKey(), numberOfOutputChannels);
        }
        return returnChannels;
    }

    // New: required by Flink 1.9
    @Override
    public int selectChannel(SerializationDelegate<StreamRecord<Tuple2<StreamRoute, Object>>> streamRecordSerializationDelegate) {
        Tuple2<StreamRoute, Object> value = streamRecordSerializationDelegate.getInstance().getValue();
        if (value.f0.isBroadCastPartitioning()) {
            /*
            It is illegal to call this method for broadcast channel selectors and this method can remain not
            implemented in that case (for example by throwing UnsupportedOperationException).
            */
        } else if (value.f0.getPartitionKey() == -1) {
            // random partition
            returnChannels[0] = random.nextInt(numberOfChannels);
        } else {
            returnChannels[0] = partitioner.partition(value.f0.getPartitionKey(), numberOfChannels);
        }
        //return returnChannels;
        return returnChannels[0];
    }

The dynamic partitioner is used within one of the cql method like this:
public ExecutionSiddhiStream cql(DataStream<ControlEvent> controlStream) {
    DataStream<Tuple2<StreamRoute, Object>> unionStream = controlStream
        .map(new NamedControlStream(ControlEvent.DEFAULT_INTERNAL_CONTROL_STREAM))
        .broadcast()
        .union(this.toDataStream())
        .transform("add route transform",
             SiddhiTypeFactory.getStreamTupleTypeInformation(TypeInformation.of(Object.class)),
             new AddRouteOperator(getCepEnvironment().getDataStreamSchemas()));

      DataStream<Tuple2<StreamRoute, Object>> partitionedStream = new DataStream<>(
          unionStream.getExecutionEnvironment(),
          new PartitionTransformation<>(unionStream.getTransformation(), new DynamicPartitioner())
    );
    return new ExecutionSiddhiStream(partitionedStream, null, getCepEnvironment());
}

At this point I am still thinking which would be the cleanest solution. Maybe you already have some ideas, if so please let me know!

@haoch Closing the ticket since support was already added in #59.


tmpwatch: add fuser support

This unlocks the option --fuser which checks if files are in use by
other processes before deleting them.

@GrahamcOfBorg build tmpwatch


Add pulumi refresh tip.

pulumi refresh worked for me.

@cnunciato @lblackstone should this be merged?


CSUB-1231: Use --profile=production for all builds & CI jobs

Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

These changes look right.
Just to make sure, we're fine with CI runs taking 1.5x longer than before right?

Can you be more precise? Which jobs are taking 1.5x because I'm not able to spot anything obvious ?

Production builds take quite a bit longer than release builds so I was envisioning only using production for final image builds.

Multiple integration tests with the --profile=production build are currently failing, https://github.com/gluwa/creditcoin3/actions/runs/10305191630/job/28527968917?pr=437 and IMO the only way to have some confidence in these builds is to actually exercise them before we ship. Otherwise we end up in the situation where we test one target, however we ship a different target which is completely untested - not good IMO.

Runtime upgrade testing -> https://github.com/gluwa/creditcoin3/actions/runs/10317027713/job/28566440763 seems to me to be working fine.
The rest of the testing is in this PR which also appears to be looking good. Will port to creditcoin3-next and close this one shortly after!


Insomnia is getting more JSON replies

Expected Behavior
I'm using javascript with axios. If I manually make an axios request or I use Insomnia Generate Code feature it should give the same json response
example:
{ "codecType": "h264", "definition": "720p", "bitrateInfo": [ "something" ], "author": {} }
Actual Behavior
I'm using javascript with axios. If I manually make an axios request or I use Insomnia Generate Code feature it gives DIFFERENT REPLIES
example in Insomnia:
{ "codecType": "h264", "definition": "720p", "bitrateInfo": [ "something" ], "author": {} }
example with Axios:
{ "codecType": "h264", "definition": "720p", "author": {} }
In this case "bitrateInfo" totally disappear
Reproduction Steps
No response
Is there an existing issue for this?

[x] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2022.1.0
What operating system are you using?
Ubuntu
Operating System Version
Ubuntu 22.04 LTS
Installation method
Through deb package downloaded from Insomnia website
Last Known Working Insomnia version
No response

I solved it. Default Insomnia requests have "Send cookies automatically", so I did it with Axios.


Feat shorten proposals body

Changes proposed in this pull request:

Add feature that will shorten proposal body when longer than 260px. This will help users who don't want to read the whole proposal and just want to vote.
Also added a prop noFocus for UiButton to prevent focus when not needed (focus is used when inputs are inside a button)

Proposals for testing:
samuv.eth/proposal/0x29cc8ff83eec805ecf0fd1064cea03ebc3af1388cfcfcaf0364af01328ec41a4
samuv.eth/proposal/0x15d37029ed708f9078fd2a297b7b5ca2f7c634bb242e4d69eb7d284e19153525
samuv.eth/proposal/0x62779a3b751a069ec0eae3d5b0a680dfbe8e6fb98c0f9bda670b96caa2662ea4
sismo.eth/proposal/0x2032ac1b0bc07ca4f3e22982c5f7fb774588ce19749302e2dad600c3b3f73fd6

Maybe we can avoid situations where there's just one or two line hidden, by setting the trigger height a bit lower than the collapse height. You know what I mean?

Maybe we can avoid situations where there's just one or two line hidden, by setting the trigger height a bit lower than the collapse height. You know what I mean?

Added that, but the other way around 😛


fix: update hapi bindings to v21

Which problem is this PR solving?

https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1383

Short description of the changes

Change compat to v21 and up and change the type libraries to use hapi internal

Firstly, thank you @toddtarsi!
I ran npm run compile so I could test this in our own project. However, it errored. Here is the output:
npm run compile

><EMAIL_ADDRESS>precompile
> tsc --version && lerna run version:update --scope @opentelemetry/instrumentation-hapi --include-dependencies

Version 4.4.4
lerna notice cli v5.5.2
lerna info versioning independent
lerna notice filter including "@opentelemetry/instrumentation-hapi"
lerna notice filter including dependencies
lerna info filter [ '@opentelemetry/instrumentation-hapi' ]
lerna info Executing command in 1 package: "npm run version:update"
lerna info run Ran npm script 'version:update' in '@opentelemetry/instrumentation-hapi' in 1.2s:

><EMAIL_ADDRESS>version:update
> node ../../../scripts/version-update.js

lerna success run Ran npm script 'version:update' in 1 package in 1.2s:
lerna success - @opentelemetry/instrumentation-hapi

><EMAIL_ADDRESS>compile
> tsc -p .

node_modules/@hapi/hapi/lib/types/route.d.ts:2:68 - error TS2307: Cannot find module 'joi' or its corresponding type declarations.

2 import { ObjectSchema, ValidationOptions, SchemaMap, Schema } from 'joi';
                                                                     ~~~~~

node_modules/@hapi/hapi/lib/types/server/server.d.ts:4:22 - error TS2307: Cannot find module 'joi' or its corresponding type declarations.

4 import { Root } from 'joi';
                       ~~~~~

Found 2 errors.

Just noting, I was looking at it this weekend and I definitely just need to do the taz thing. Without that up, I am just going in circles a bit, sorry all!

@toddtarsi sorry to bother, are you planning on finishing this one? I was working on something of my own and noticed that installing open-telemetry would downgrade hapi to v20. I can pick it up and take a look.

@IAmVisco - Nah. I'm not sure what the taz stuff is tbh.

@IAmVisco - Nah. I'm not sure what the taz stuff is tbh.

Sorry, mind linking what taz is? I don't see anything in the PR and you mentioned it first in your earlier comment.

@IAmVisco - Nah. I'm not sure what the taz stuff is tbh.

Sorry, mind linking what taz is? I don't see anything in the PR and you mentioned it first in your earlier comment.

https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1491#discussion_r1188749397

Is there any chance this can get released?

Looks like 2 tests failing. My guess it that this needs to be fixed, but also that there may need to be a new major or minor version to release a new version that depends on Hapi 21. One build can not unfortunately easily work for multiple versions of Hapi without a lot of casting to essentially use un-typed JS to get the job done, so not sure how TAV applies here.
Trying to debug the errors, but the monkey patching is a little complicated.
  23 passing (262ms)
  2 failing

  1) Hapi Instrumentation - Core Tests
       Instrumenting Hapi Routes
         should update rpcMetadata.route information:
     AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected

+ undefined
- '/users/{userId}'
      at /Users/arimus/workspace/opentelemetry-js-contrib/plugins/node/opentelemetry-instrumentation-hapi/test/hapi.test.ts:407:18
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at Context.<anonymous> (test/hapi.test.ts:394:7)

  2) Hapi Instrumentation - Core Tests
       Instrumenting Hapi Routes
         when handler is in route.options level
           should create a child span for single routes:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:

1 !== 2

      + expected - actual

      -1
      +2

      at /Users/arimus/workspace/opentelemetry-js-contrib/plugins/node/opentelemetry-instrumentation-hapi/test/hapi.test.ts:136:20
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at Context.<anonymous> (test/hapi.test.ts:126:9)

I found a fix that allows the test to pass (instrumentation.ts, line:393), although I'm not positive what the implications are on a broader level.
        const rpcMetadata = getRPCMetadata(api.context.active());
        if (rpcMetadata?.type === RPCType.HTTP) {
          // @ts-ignore - <<<<<< ADDED - set the route path onto the rpcMetadata object
          rpcMetadata?.route = route.path;

          const rootSpanMetadata = getRootSpanMetadata(route);
          rpcMetadata.span.updateName(rootSpanMetadata.name);
          rpcMetadata.span.setAttributes(rootSpanMetadata.attributes);
        }

And I haven't yet determined why the span completion count is only 1 instead of 2 in this other test. Happy to help test if @toddtarsi wants to update this pull request and get the tests passing.
Some guidance from the author(s) would be good on what is necessary to get this merged outside of getting tests passing (e.g. versioning, etc.) Worst case, I guess a new NPM module can be created to support Hapi v21 in the meantime, but keeping things here would be ideal.

Hi, @arimus.  We try to correct and run a PATCHED version of the HAPI plugin to runs correctly with HAPI 21. In your last comment, you provided a fix but we don't know how you have implemented the getRootSpanMetadata(route). Could you provide the code of that function please? It will help us a lot.

@here Is there anything that can be done to move this issue along?  Anything I could do to help?

@toddtarsi It looks to me as if the major hurdles came from upgrading type dependencies to hapi 21. What do you think about staying on @types/hapi__hapi for a little longer, but moving it to devDependencies as to not cause issues for folks?
This looks like it would work: https://github.com/nlochschmidt/opentelemetry-js-contrib/commit/a299190f24351639fe63ae1a5ce6ae1a5258e9bb. I'd be happy to provide an alternative PR for hapi v21 support based on this.

@toddtarsi I had a closer look at your PR today and I think it's possible to restore support for versions 17 to 20. My solution requires a few more any, but with tav in place now, I think that might be worth it.
https://github.com/open-telemetry/opentelemetry-js-contrib/compare/main...nlochschmidt:opentelemetry-js-contrib:update-hapi-to-v21
I added joi as a dev dependency as mentioned by @IAmVisco. I think the alternative is to use skipLibCheck: true in the hapi local tsconfig.json. I see some other modules doing the same, but I am not sure what's preferred around here.
If you want, you can pull my changes into this PR, otherwise I will create a new one.

This PR can be closed.
#1985 has been merged, which includes these changes.

This PR can be closed.
#1985 has been merged, which includes these changes.

Thanks for updating here 🙏


allow dateQuery against created and updated

API currently only does Elasticsearch dateQuery's for properties.datetime. Extend to allow vs properties.created and properties.updated.

This is already supported via using the normal query extension and using the operators eq, lt, etc.


v2alpha HA MQTT Discovery

v2alpha initial commit

Thanks for start the merge.
I've made some changes over the last couple of days but haven't committed them yet.

* The discrepancy between the Switchbot Curtain and Home Assistant where the curtain clearly says it's open, even the Home Assistant icon shows that the curtain is open but the only button we can press is Open. I'm not 100% sure if this is an issue with the discovery config or something with Home Assistant.

It appears that Home Assistant is built in a way that open is 100 and closed is 0.
You can change the position_open: 100 and position_closed: 0 and this does invert the slider for the curtain. However, the problem with the buttons are still there. If the curtain is open I can only press the open button.
I fixed this by inverting the position of the curtain so open is 0 and closed is 100. After adjusting the discovery configuration everything is working as expected.

* When I received the Meter I noticed you can change the format of the temperature (Celsius vs Fahrenheit) on the fly with just a button on the back. I'm working on a mechanism to update the discovery config when this is changed.

Almost finished with this. I'm experiencing some weird behavior where it keeps using the Celsius value even the value_template: {{ value.F }} is set.

* Split the payloads out for the Curtain and Bot state (OPEN, CLOSED, ON, OFF, 0-100) and the extra attributes (battery, position, rssi) so the state of the Curtain and Bot will show the state that we've given.
* * For example; Switchbot Bot is OFF, we toggle it ON but the state goes to OFF immediately because the state payload still says it's OFF and will only update after every  seconds.

Not done yet

* When I received the Meter I noticed you can change the format of the temperature (Celsius vs Fahrenheit) on the fly with just a button on the back. I'm working on a mechanism to update the discovery config when this is changed.

Almost finished with this. I'm experiencing some weird behavior where it keeps using the Celsius value even the value_template: {{ value.F }} is set.

Okay. after some debugging I started realizing this functionality did work but it didn't show me Fahrenheit because the server settings were configured to use Metric instead of Imperial.
At this point I'm starting to doubt if this is useful at all because it's converting the temperature to whatever setting you use in Home Assistant anyway.

Sorry if I'm going too slow, I'm doing this in the few spare hours I have after my day-job and family 😄

no problem. Priorities. People can wait a bit when it's a free solution 😁


Prerender pages in parallel

#3065
This PR enables prerendering pages in parallel.
When enabling prerendering the entries are now batched and prerendered in parallel. Errors emerged when running more than 10 entries at once, thus the batch size. The batch size should maybe be configurable or not needed.
SyntaxError: Unexpected token < in JSON at position 0
  at JSON.parse (<anonymous>)
  at Response.json (file:///Users/felix/Projects/kit/packages/kit/dist/install-fetch.js:4868:15)
  at runMicrotasks (<anonymous>)
  at processTicksAndRejections (node:internal/process/task_queues:96:5)
  at async getAllEntities (file:///Users/felix/Projects/kit/examples/web/.svelte-kit/output/server/chunks/wordpress-cb2619c2.js:12:16)
  at async getAllProductsWithFilterParams (file:///Users/felix/Projects/kit/examples/web/.svelte-kit/output/server/chunks/woocommerce-a9f9aaa5.js:41:34)
  at async Promise.all (index 0)
  at async get (file:///Users/felix/Projects/kit/examples/web/.svelte-kit/output/server/chunks/_slug_.json-c5701545.js:10:40)
  at async render_endpoint (file:///Users/felix/Projects/kit/examples/web/.svelte-kit/output/server/chunks/app-52ab529a.js:96:20)
  at async resolve (file:///Users/felix/Projects/kit/examples/web/.svelte-kit/output/server/chunks/app-52ab529a.js:1259:56)

dev:basics tests are currently failing but to my understanding that's just for my setup and not any project specific. Tests regarding the default options are all passing.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check
[ ] Pass tests

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Thank you! To maximise efficiency, it's better to use a queuing mechanism than batches. Consider a case where you have a batch size of 2 and 5 pages A, B, C, D and E, where A, C and E take 1 second to render but B and D take 10 seconds. With batching, it takes 21 seconds total, with lots of time spent idle:
A                  |C                  |E
B-B-B-B-B-B-B-B-B-B|D-D-D-D-D-D-D-D-D-D|

With a queuing mechanism, that can be reduced to 12:
A|C|D-D-D-D-D-D-D-D-D-D
B-B-B-B-B-B-B-B-B-B|E

It won't normally be that extreme, but there'll always be some idle time, as long as there's variability in how long a page takes to render.
I've implemented a queuing mechanism in #3120 (and changed the option to kit.prerender.concurrency, so that people can adjust the value and find what works best for them), so I'll close this.


Correct Typo in Azure Blobs Description

A massively scalable object store for text and binary data (instead of "binary day")

@qnal - Thank you for making that fix.
#sign-off


Update SQL Server type mappings for strings

Fixes #19327
Create fixed-length type mappings by default, and then use the correct DbType in the parameter if the length of the value matches the parameter length. This has a better chance of hitting an index. In other cases, change the DbType to match what we did before so that SQLClient doesn't truncate or pad.
Fixes #14555
If the parameter value length is greater than the max length but less than the max bounded length, then using the max bounded length rather than going immediately to unbounded.

@AndriySvyryd Filed #19429


how to reset password?

I installed Kaiwa via the DO droplet, I access it by IP address directly; every time I enter my u/p it says "connect" and then reverts to homepage. How do I reset the password? Also on what IP do I access the Prosody server directly?

I'm having the same issue but I know my password is correct. "connecting..." and then redirect to login with no errors thrown.


bundleId change

Hi, i have test where my bundleId change during test.
My question:

Is there a way to change bundleId when driver is initialized?
Do i have to create new driver? That means, quit one driver, open new with new bundleID (which i don't like as solution, cause it will affect all my pageObjects).

Thx.

1

Do you mean you want to change the bundled of the app under test? (Not WDAMac)
Then, no.

2

You can keep running WDAMac with appium:webDriverAgentMacUrl capability.

Hi, thanks for answer @KazuCocoa. I will try to describe my problem better. I am using Java and Appium.

Start appium server
Install tested mac app
Create appium Driver with -> bundleID = exampleBundleId1
Login to app and do setup of app (still same bundleId)
After login, app reopens and my app now have different bundleId = exampleBundleId2

From point 5. i can't do anything with app, since driver was created with bundleId = exampleBundleId1
Here is my code:
        caps.setCapability("platformName", "mac");
        caps.setCapability("automationName", "mac2");
        caps.setCapability("deviceName", "Mac");
        caps.setCapability("bundleId", "exampleBundleId1");
        caps.setCapability("newCommandTimeout", 3000);
        new AppiumDriver(new URL(SERVER_URL), caps);

So i want to be able to change capabilities (bundleId) of already created driver or find a way to be able to handle mentioned case.

I do not understand how bundle id can be in real time but maybe command "macos: activateApp" can help with this? (this command is described in main doc https://github.com/appium/appium-mac2-driver)

Okay, then, you can use activateApp Dmitry (thanks) to achieve After login, app reopens and my app now have different bundleId = exampleBundleId2

@KazuCocoa Thanks! I will try that :-)

Hey, i just wanted to let you know that it worked! :-) Thx again.


google.ima.AdEvent.Type.VIEWABLE_IMPRESSION isn't trigger

Hi all,
from two days ago, the "google.ima.AdEvent.Type.VIEWABLE_IMPRESSION" isn't triggered anymore..
What's the problem???
I will wait an answer..
Thanks
A.

Hi @ibraalek10 ,
Looking at the IMA AdEvent docs, it looks like you might be looking for google.ima.AdEvent.Type.IMPRESSION
Please let me know if that resolves your issue.

Hi, I'm having a similar issue currently. The google.ima.AdEvent.Type. VIEWABLE_IMPRESSION used to fire along with the google.ima.AdEvent.Type.IMPRESSION event but not anymore. Did the google.ima.AdEvent.Type. VIEWABLE_IMPRESSION event get removed recently? I can't find any release notes that mention it being removed

Hi all,
google.ima.AdEvent.Type.IMPRESSION is the only event in our documentation that deals with impressions. I recommend listening for that event.
Changes to non-public APIs may not be published, and so it is recommended to only use those that are publicly available.

@Kiro705 I see that the google.ima.AdEvent.Type.IMPRESSION is the only event listed in the documentation, but I can see that the google.ima.AdEvent.Type.VIEWABLE_IMPRESSION does exist in the ima3.js file as an AdEvent Type, but isn't listed in the documentation for whatever reason.

Hi @christianbkoehler ,
You are correct, and the reason for that is the google.ima.AdEvent.Type.VIEWABLE_IMPRESSION event is not meant for external use and changes to it may go unpublished.

Great, thank you for that information!

Hi all,
I understand but i need this event for measuring viewability..
Until a few days ago, this event was triggered very well..
What's the matter now??? How can I solve my problem with video viewability?
I will wait your answers..
Thanks a lot,
A.

Hi @ibraalek10 ,
You will have to use google.ima.AdEvent.Type.IMPRESSION to measure viewability. If that is not working for you, can you provide sample code that demonstrates the problem you have. I think that would be the best way for me to help with a solution.
Thanks,
Jackson
IMA SDK DevRel

Hi @Kiro705,
Thanks for the answer but I must tell you some things..
google.ima.AdEvent.Type.IMPRESSION is fired when the impression is called while google.ima.AdEvent.Type.VIEWABLE_IMPRESSION was fired when the impression was called and the video stay in viewport for 2 seconds..
This was the important difference of this two events..
I will wait your answer..
Thanks in advance,
A.

If you would like, I can file a feature request of the IMA SDK for a public event for viewable impressions. But for now this does not appear to be an issue with the videoJS-IMA plugin.
Otherwise, I would suggest having your app watch for the video to stay within the viewport as a workaround.

Hi @Kiro705,
it would be fantastic if this event became a public event..
Please can you forward a request to the IMA SDK?
Thanks a lot,
A.

Hi @ibraalek10 ,
An update from the IMA team:
The VIEWABLE_IMPRESSION event will not be reimplemented. It was removed as an upcoming change would make it infeasible for the IMA SDK to track this. It is recommended that you measure viewability from your ads manager or your own viewability script.


Redesign the Movies page to match the new designs

Redesign the existing movies page(screenshot attached) to match the new design we are utilising.

Update:


point-cloud-laz example error

I'm trying to view this example and I get errors for missing modules in mjolnir.js.

ERROR in ./~/mjolnir.js/dist/event-manager.js
Module not found: Error: Can't resolve 'babel-runtime/helpers/classCallCheck' in 'W:\October\deck.gl\examples\point-cloud-laz\node_modules\mjolnir.js\dist'
@ ./~/mjolnir.js/dist/event-manager.js 11:23-70
@ ./~/mjolnir.js/dist/index.js
@ ./~/deck.gl/dist-es6/react/experimental/orbit-controller.js
@ ./~/deck.gl/dist-es6/index.js
@ ./app.js
@ multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./app.js
ERROR in ./~/mjolnir.js/dist/event-manager.js
Module not found: Error: Can't resolve 'babel-runtime/helpers/createClass' in 'W:\October\deck.gl\examples\point-cloud-laz\node_modules\mjolnir.js\dist'
@ ./~/mjolnir.js/dist/event-manager.js 15:20-64
@ ./~/mjolnir.js/dist/index.js
@ ./~/deck.gl/dist-es6/react/experimental/orbit-controller.js
@ ./~/deck.gl/dist-es6/index.js
@ ./app.js
@ multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./app.js
ERROR in ./~/mjolnir.js/dist/event-manager.js
Module not found: Error: Can't resolve 'babel-runtime/core-js/object/assign' in 'W:\October\deck.gl\examples\point-cloud-laz\node_modules\mjolnir.js\dist'
@ ./~/mjolnir.js/dist/event-manager.js 7:14-60
@ ./~/mjolnir.js/dist/index.js
@ ./~/deck.gl/dist-es6/react/experimental/orbit-controller.js
@ ./~/deck.gl/dist-es6/index.js
@ ./app.js
@ multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./app.js
ERROR in ./~/mjolnir.js/dist/inputs/wheel-input.js
Module not found: Error: Can't resolve 'babel-runtime/helpers/classCallCheck' in 'W:\October\deck.gl\examples\point-cloud-laz\node_modules\mjolnir.js\dist\inputs'
@ ./~/mjolnir.js/dist/inputs/wheel-input.js 11:23-70
@ ./~/mjolnir.js/dist/event-manager.js
@ ./~/mjolnir.js/dist/index.js
@ ./~/deck.gl/dist-es6/react/experimental/orbit-controller.js
@ ./~/deck.gl/dist-es6/index.js
@ ./app.js
@ multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./app.js

Fixed it using
npm install --save babel-runtime --save


Create variant with FPM

Needs #20 to be done

Bugs to fix in the way:

remove supervisor from install


Farmlist without using game option

It will be nice to have the possibility to send raids to farm that are not in the farmlists like the txt option of the python bot

so you mean the non Travian plus version ?
it could be that this will be easier to notice for the multi hunters, since you are performing a lot of actions.
thanks for the request. next feature will be to show the logs in the interface so I can better fix bugs and I consider adding this afterwards, since it won't be that difficult :)


Redis Actors Example

Thanks for looking into this @shaded-enmity.
I will just remove the buildah binary before merging this PR. Also, I'll make sure to create a tracking issue if I don't manage to use a supported image.


refactor: context module factory resolve hook

Summary

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6008  👈
#6003
#5998
#5997
#5995
#5990
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ahabhgk and the rest of your teammates on  Graphite

!eco-ci

!bench

!eco-ci

!bench

!bench


http://zizzamia.com/ng-tasty/ page is down

http://zizzamia.com/ng-tasty/ page is down
can you fix it?

@senzacionale it's back!


Replace the use of "provide" with a simpler alternative as per Vale recommendation

Vale recommends use of a simpler alternative to "provide"

Task: Search across Vizro docs (vizro-core and vizro-ai) for instances of provide and replace with discretion.
If there are genuine cases where lower case python is more appropriate, use the following to switch Vale off/on in situ
<!-- vale off -->
Legitimate use of provide
<!--vale on-->

Hello, I'd like to work on this. Can you please assign this to me.

Hello @antonymilne,
I apologize for the delayed response. I have just returned from GHC and haven't had the chance to check my notifications. I've made the necessary changes on my local machine, but I'm encountering some issues while creating the pull request. Please give me 2 days to figure out the problem with my GitHub.

Hi @i-lahari, no worries at all for the delay - welcome back! And thank you for your interest in contributing 🙏 Just let us know if you need any help raising the PR.

Resolved by https://github.com/mckinsey/vizro/pull/848


log display: "Clear" button always disabled

The clear button uses the wrong binding for its disabled-state, so that it cannot be used.

Fixed on master (v0.1.0).


[KOGITO-6683] - Optionally run Kogito Process BuildItems for Knative Add-On

In this PR, we optionally run the Kogito Process BuildItems when Knative Add-On is added to the classpath. In examples with DMN, for example, we won't need it to run.
See https://issues.redhat.com/browse/KOGITO-6683
Signed-off-by: Ricardo Zanini<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Your code is properly formatted according to this configuration
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

(tests) - kogito-apps job #950 was: UNSTABLE
Possible explanation: This should be test failures
Test results:

PASSED: 2391
FAILED: 2

Those are the test failures:

org.kie.kogito.index.inmemory.ProcessDataIndexInMemoryIT.testProcessInstanceEvents
java.lang.RuntimeException: java.lang.reflect.InvocationTargetExceptionCaused by: java.lang.reflect.InvocationTargetExceptionCaused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource org.kie.kogito.index.quarkus.DataIndexInMemoryQuarkusTestResource@64da1449Caused by: java.lang.RuntimeException: Unable to start Quarkus test resource org.kie.kogito.index.quarkus.DataIndexInMemoryQuarkusTestResource@64da1449Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failedCaused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exceptionCaused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start containerCaused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [49321] should be listening)

org.kie.kogito.index.ProcessDataIndexInfinispanIT.testProcessInstanceEvents
java.lang.AssertionError: 1 expectation failed.JSON path errors doesn't match.Expected: null  Actual: [{path=[UserTaskInstanceAttachmentUpdate], extensions={classification=DataFetchingException}, locations=[{line=1, column=12}], message=Exception while fetching data (/UserTaskInstanceAttachmentUpdate) : Index 0 out of bounds for length 0}]

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/950/display/redirect

jenkins rerun kogito-apps test

Jenkins rerun kogito-apps tests

Jenkins rerun kogito-apps tests


Implement "new widget" modal

The "new widget" the scope will focus on implementing the functional requirements, any visual and nice-to-have details will be pushed out of scope for this first iteration.
Minimum functional requirements include:

[x] Can have a modal working (same as for current dashboard)
[ ] Column title + selected state
[ ] A type should only be visible if there is at least one option available (e.g. times-series will only work if there's at least one date column)

Must-haves:

[x] Port modal code to new editor
[ ] PoC of adding a widget, using a single type (e.g. formula)
[ ] Apply tab component to render more than one type (e.g. histogram)
[ ] Implement remaining types (category, time-series, …)
[ ] Error handling

Nice-to-have:

[ ] Selections summary in the footer

FYI @urbanphes I'll track progress here

Postponed until the new designs are ready, so moving to backlog…
#6601 contains the stuff finished so far at least (the modal part).

@urbanphes the basic functionality is done (once the last PR is merged), meanwhile I encountered some issues, see the "Needs further discussion" in the desc of this PR. Let me know when we can talk about these, meanwhile I'll continue with the bugs/remaining features.


Add setUserIdentity signature in index.d.ts

short description
This PR adds a missing signature about function setUserIdentity that can be invoked both with token or with email & name.
:beetle: It also fixes a bug on Android side about the usage of parameter botName: although it is declared as optional field, native code assumes it is always present.

Maybe you should split the pr-s in two: useridentity and the andriod fixes


docs: correct grammand and improve consistency

This commit corrects some grammar bugs (your vs you're) and makes the
comparison lists more consistent by starting each point with if.
Signed-off-by: Lucas Servén Marín<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


BitBar process has a constant CPU usage (of ~1%) even when idle

Platform: MacOS 10.13.2
Version: 1.9.2
Given BitBar with 2 plugins installed with a refresh interval of 10 minutes each
Then the BitBar expected CPU usage should be 0% during the idle time
And should raises only when the 10 minutes elapse.

Current implementation of BitBar has a notable impact on the battery usage.

Any updates to this?  I'm noticing this as well.  Why is CPU so high for an idle bitbar?

I built the current code and ran it through Instruments, and nothing looked obviously wrong. Most time is spent system calls on the Main Thread:

NSApplication, 75% of the time

CFRunLoop, 60%

Observers, 25%
Timers, 20%
Queue, 15%

I had a quick look through the code and I have seen slightly better CPU usage by changing:
https://github.com/matryer/bitbar/blob/master/App/BitBar/ExecutablePlugin.m#L80
from
DISPATCH_QUEUE_PRIORITY_DEFAULT
to
DISPATCH_QUEUE_PRIORITY_BACKGROUND
Feel free to try that and report back?


List all partition keys of an application

Is your feature request related to a problem? Please describe.
Right now, burr does not provide an interface to list all partition_keys of an application.
Quoting from the documentation:

In the case of a chatbot, the app_id could be a uuid, and the partition_key could be the user’s ID or email, etc. Note that partition_key can be None if this is not relevant. A UUID is always generated for the app_id if not provided.

Imagine we are implementing an admin page for the system managing the chatbot, and need to display all the users' chat sessions, that the interface to retrieve all the partition_keys from an application should become necessary.
Describe the solution you'd like
Maybe a method from the application to retrieve all the partition_keys?
Describe alternatives you've considered
Direct data retrieval from the storage where the states of the application are persisted.
Additional context
None

@shun-liang question, what filters would you want if any on this? I'm just thinking ahead because all partition keys could be expensive in certain situations.
E.g. get me active ones since X timestamp, or get me all created since X timestamp, etc.

True. However this does require the user to dig into the persister implementation to understand they work.

I was thinking you'd maintain a separate DB table, or something. E.g. something tied together with your auth system. Since generally the parition_key should map to some "user Id" or other identifier. In which case you could then use that to figure out what partition_keys would exist.

what filters would you want if any on this?

I would imagine it being very integral with the state, maybe something like how a condition is defined?

Oh interesting. That might be too slow since we'd be dealing with serialized data (we'd have to think about custom indexes or some other data structure to help facilitate this). My first thought was around timestamps at the minimum.

what filters would you want if any on this?

I would imagine it being very integral with the state, maybe something like how a condition is defined?

Oh interesting. That might be too slow since we'd be dealing with serialized data (we'd have to think about custom indexes or some other data structure to help facilitate this). My first thought was around timestamps at the minimum.

IMO it's more likely that you'd want a paginated API -- E.G. a way to grab the first 100 users, etc... Then you'll also want a way to search for users. For less than, like, 100k, you can likely send them all over the wire and process it client-side, so it might be that just a list_all is good.


datastore.secure boolean values seem to be case sensitive in rally.ini

Specifying datastore.secure = true in rally.ini gives the misleading error message:
esrally.exceptions.SystemSetupError: ('Could not connect to your Elasticsearch metrics store. Please check that it is running on host [https://<url>] at port [9243] or fix the configuration in [<home_dir>/.rally/rally.ini].', None)
].

It works when setting it to True, but we should be case insensitive when parsing boolean values in this file.

cc @dakrone


Issue with Types when stitching schema

Hi. I tried doing fetchRemoteSDL and retrieving the SDL from the remote service instead of doing introspection as mentioned here: https://github.com/gmac/schema-stitching-demos/blob/master/01-combining-local-and-remote-schemas/index.js#L30 and it worked well.
But there was a typings issue as below:

where the object is nothing but same as in the example:
return {
    schema: buildSchema(remoteSchema),
    executor: httpExecutor
  };

Currently, working around this by adding a ts-ignore like this:
subschemas: [
      // @ts-ignore
      {
        schema: authService.schema,
        executor: authService.executor
      }
]

Thanks.
CC: @gmac

I guess I don’t follow the problem here. Looks like you haven’t converted the example into typescript, which I assume you are using? These examples are plain JavaScript. You’d need to add casting information as appropriate to your version of TypeScript. I’m intentionally using JavaScript as a lowest-common denominator.
Please let me know if I’m missing something else here that is technically inaccurate in the example.

@gmac Thanks for the clarification. I assumed that it was compatible with Typescript out of the box. Will fix it on my end then 👍

@gmac Btw, I just had to mark the return type as AsyncExecutor and the error above went away 🎉
import { AsyncExecutor } from '@graphql-tools/delegate';

const makeRemoteExecutor = function(url:string) : AsyncExecutor {
  return async ({ document, variables }) => {
    const query = typeof document === 'string' ? document : print(document);
    const fetchResult = await fetch(url, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({
        query, variables
      })
    });
    return fetchResult.json();
  };
};

Sounds about right! Is Stitching starting to make more sense now with some concrete examples? I personally find it to be fairly intuitive given that the subservices are all plain GraphQL, versus Federation where there’s a bunch of magic happening at every layer of the stack to bring it all together.

@gmac Stitching - Yes, Typemerging - In Progress . While I understood the concepts properly with both of ur help and have it setup as part of the stack, I am working to see how I can fit it for my usecases. Will share my progress as I go along.


[SPARK-3862] [SQL] [WIP] MultiWayBroadcastJoin for LeftSemi & Inner JOIN

Assume we have table x, y, z, and the x is the fact table with large mount of data, and y, z are dimensional tables.
SELECT x.a, y.a, z.a FROM x JOIN y ON x.a = y.a AND y.a < 3 JOIN z ON x.a = z.a AND z.a > 1

To compute the result, it's required multiple times reading / writing data for fact table(large amount of data) if we do that as binary join way; this PR (multiple way broadcast join) will reduce the IO overhead significantly by reading all of the data once, as well as the filtering effect of the multiple join filters.
This PR is for earlier feedbacks, some TODOs as below, but probably can be done in another PRs

Multiway-join for JOINs in identical equi-join.
Join Reordering.
Integrated with Sort-Merge-Join in Multiway JOIN.
Code Clean Up, to unify the JOIN code by removing the binary join(replaced with multiple way join)

Restrictions

The fact table should be in the left-most, we can improve that in Join Reordering.

Benchmarking result will be provided soon...

Test build #29591 has started for   PR 5326 at commit b4cbabd.

Test build #29591 has finished for   PR 5326 at commit b4cbabd.

This patch fails Scala style tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

case class DimensionJoin(

case class JoinFilter(joinType: JoinType, filter: Expression)

case class JoinKey(leftKeys: Seq[Expression], rightkeys: Seq[Expression])

trait CompactBufferBuilder extends java.io.Serializable

class IteratorBufferBuilder extends CompactBufferBuilder

class HashedBufferBuilder(relation: HashedRelation) extends CompactBufferBuilder

class CorrelatedBufferBuilder(key: Projection, relation: HashedRelation) extends CompactBufferBuilder

class ConstantBufferBuilder(row: Row) extends CompactBufferBuilder

trait MultiwayJoin

 class MultiBuild extends HashSet[Int] with BuildSide

This patch removes the following dependencies:

RoaringBitmap-0.4.5.jar
activation-1.1.jar
akka-actor_2.10-2.3.4-spark.jar
akka-remote_2.10-2.3.4-spark.jar
akka-slf4j_2.10-2.3.4-spark.jar
aopalliance-1.0.jar
arpack_combined_all-0.1.jar
avro-1.7.7.jar
breeze-macros_2.10-0.11.2.jar
breeze_2.10-0.11.2.jar
chill-java-0.5.0.jar
chill_2.10-0.5.0.jar
commons-beanutils-1.7.0.jar
commons-beanutils-core-1.8.0.jar
commons-cli-1.2.jar
commons-codec-1.10.jar
commons-collections-3.2.1.jar
commons-compress-1.4.1.jar
commons-configuration-1.6.jar
commons-digester-1.8.jar
commons-httpclient-3.1.jar
commons-io-2.1.jar
commons-lang-2.5.jar
commons-lang3-3.3.2.jar
commons-math-2.1.jar
commons-math3-3.1.1.jar
commons-net-2.2.jar
compress-lzf-1.0.0.jar
config-1.2.1.jar
core-1.1.2.jar
curator-client-2.4.0.jar
curator-framework-2.4.0.jar
curator-recipes-2.4.0.jar
gmbal-api-only-3.0.0-b023.jar
grizzly-framework-2.1.2.jar
grizzly-http-2.1.2.jar
grizzly-http-server-2.1.2.jar
grizzly-http-servlet-2.1.2.jar
grizzly-rcm-2.1.2.jar
groovy-all-2.3.7.jar
guava-14.0.1.jar
guice-3.0.jar
hadoop-annotations-2.2.0.jar
hadoop-auth-2.2.0.jar
hadoop-client-2.2.0.jar
hadoop-common-2.2.0.jar
hadoop-hdfs-2.2.0.jar
hadoop-mapreduce-client-app-2.2.0.jar
hadoop-mapreduce-client-common-2.2.0.jar
hadoop-mapreduce-client-core-2.2.0.jar
hadoop-mapreduce-client-jobclient-2.2.0.jar
hadoop-mapreduce-client-shuffle-2.2.0.jar
hadoop-yarn-api-2.2.0.jar
hadoop-yarn-client-2.2.0.jar
hadoop-yarn-common-2.2.0.jar
hadoop-yarn-server-common-2.2.0.jar
ivy-2.4.0.jar
jackson-annotations-2.4.0.jar
jackson-core-2.4.4.jar
jackson-core-asl-1.8.8.jar
jackson-databind-2.4.4.jar
jackson-jaxrs-1.8.8.jar
jackson-mapper-asl-1.8.8.jar
jackson-module-scala_2.10-2.4.4.jar
jackson-xc-1.8.8.jar
jansi-1.4.jar
javax.inject-1.jar
javax.servlet-3.0.0.v201112011016.jar
javax.servlet-3.1.jar
javax.servlet-api-3.0.1.jar
jaxb-api-2.2.2.jar
jaxb-impl-2.2.3-1.jar
jcl-over-slf4j-1.7.10.jar
jersey-client-1.9.jar
jersey-core-1.9.jar
jersey-grizzly2-1.9.jar
jersey-guice-1.9.jar
jersey-json-1.9.jar
jersey-server-1.9.jar
jersey-test-framework-core-1.9.jar
jersey-test-framework-grizzly2-1.9.jar
jets3t-0.7.1.jar
jettison-1.1.jar
jetty-util-6.1.26.jar
jline-0.9.94.jar
jline-2.10.4.jar
jodd-core-3.6.3.jar
json4s-ast_2.10-3.2.10.jar
json4s-core_2.10-3.2.10.jar
json4s-jackson_2.10-3.2.10.jar
jsr305-1.3.9.jar
jtransforms-2.4.0.jar
jul-to-slf4j-1.7.10.jar
kryo-2.21.jar
log4j-1.2.17.jar
lz4-1.2.0.jar
management-api-3.0.0-b012.jar
mesos-0.21.0-shaded-protobuf.jar
metrics-core-3.1.0.jar
metrics-graphite-3.1.0.jar
metrics-json-3.1.0.jar
metrics-jvm-3.1.0.jar
minlog-1.2.jar
netty-3.8.0.Final.jar
netty-all-4.0.23.Final.jar
objenesis-1.2.jar
opencsv-2.3.jar
oro-2.0.8.jar
paranamer-2.6.jar
parquet-column-1.6.0rc3.jar
parquet-common-1.6.0rc3.jar
parquet-encoding-1.6.0rc3.jar
parquet-format-2.2.0-rc1.jar
parquet-generator-1.6.0rc3.jar
parquet-hadoop-1.6.0rc3.jar
parquet-jackson-1.6.0rc3.jar
protobuf-java-2.4.1.jar
protobuf-java-2.5.0-spark.jar
py4j-<IP_ADDRESS>.jar
pyrolite-2.0.1.jar
quasiquotes_2.10-2.0.1.jar
reflectasm-1.07-shaded.jar
scala-compiler-2.10.4.jar
scala-library-2.10.4.jar
scala-reflect-2.10.4.jar
scalap-2.10.4.jar
scalatest_2.10-2.2.1.jar
slf4j-api-1.7.10.jar
slf4j-log4j12-1.7.10.jar
snappy-java-<IP_ADDRESS>.jar
spark-bagel_2.10-1.4.0-SNAPSHOT.jar
spark-catalyst_2.10-1.4.0-SNAPSHOT.jar
spark-core_2.10-1.4.0-SNAPSHOT.jar
spark-graphx_2.10-1.4.0-SNAPSHOT.jar
spark-launcher_2.10-1.4.0-SNAPSHOT.jar
spark-mllib_2.10-1.4.0-SNAPSHOT.jar
spark-network-common_2.10-1.4.0-SNAPSHOT.jar
spark-network-shuffle_2.10-1.4.0-SNAPSHOT.jar
spark-repl_2.10-1.4.0-SNAPSHOT.jar
spark-sql_2.10-1.4.0-SNAPSHOT.jar
spark-streaming_2.10-1.4.0-SNAPSHOT.jar
spire-macros_2.10-0.7.4.jar
spire_2.10-0.7.4.jar
stax-api-1.0.1.jar
stream-2.7.0.jar
tachyon-0.5.0.jar
tachyon-client-0.5.0.jar
uncommons-maths-1.2.2a.jar
unused-1.0.0.jar
xmlenc-0.52.jar
xz-1.0.jar
zookeeper-3.4.5.jar

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

Test build #29595 has started for   PR 5326 at commit 3954ba4.

Test build #29596 has started for   PR 5326 at commit 987bbc3.

Test build #29595 has finished for   PR 5326 at commit 3954ba4.

This patch fails Spark unit tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

case class DimensionJoin(

case class JoinFilter(joinType: JoinType, filter: Expression)

case class JoinKey(leftKeys: Seq[Expression], rightKeys: Seq[Expression])

trait CompactBufferBuilder extends java.io.Serializable

class IteratorBufferBuilder extends CompactBufferBuilder

class HashedBufferBuilder(relation: HashedRelation) extends CompactBufferBuilder

class CorrelatedBufferBuilder(key: Projection, relation: HashedRelation)

class ConstantBufferBuilder(row: Row) extends CompactBufferBuilder

trait MultiwayJoin

 class MultiBuild extends HashSet[Int] with BuildSide

This patch does not change any dependencies.

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

Test build #29596 has finished for   PR 5326 at commit 987bbc3.

This patch fails Spark unit tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

case class DimensionJoin(

case class JoinFilter(joinType: JoinType, filter: Expression)

case class JoinKey(leftKeys: Seq[Expression], rightKeys: Seq[Expression])

trait CompactBufferBuilder extends java.io.Serializable

class IteratorBufferBuilder extends CompactBufferBuilder

class HashedBufferBuilder(relation: HashedRelation) extends CompactBufferBuilder

class CorrelatedBufferBuilder(key: Projection, relation: HashedRelation)

class ConstantBufferBuilder(row: Row) extends CompactBufferBuilder

trait MultiwayJoin

 class MultiBuild extends HashSet[Int] with BuildSide

This patch does not change any dependencies.

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

Test build #29613 has started for   PR 5326 at commit e60b7a1.

Test build #29613 has finished for   PR 5326 at commit e60b7a1.

This patch fails Spark unit tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

case class DimensionJoin(

case class JoinFilter(joinType: JoinType, filter: Expression)

case class JoinKey(leftKeys: Seq[Expression], rightKeys: Seq[Expression])

trait CompactBufferBuilder extends java.io.Serializable

class IteratorBufferBuilder extends CompactBufferBuilder

class HashedBufferBuilder(relation: HashedRelation) extends CompactBufferBuilder

class CorrelatedBufferBuilder(key: Projection, relation: HashedRelation)

class ConstantBufferBuilder(row: Row) extends CompactBufferBuilder

trait MultiwayJoin

 class MultiBuild extends HashSet[Int] with BuildSide

This patch does not change any dependencies.

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

Test build #29650 has started for   PR 5326 at commit e62be3b.

Test build #29650 has finished for   PR 5326 at commit e62be3b.

This patch passes all tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

case class DimensionJoin(

case class JoinFilter(joinType: JoinType, filter: Expression)

case class JoinKey(leftKeys: Seq[Expression], rightKeys: Seq[Expression])

trait CompactBufferBuilder extends java.io.Serializable

class IteratorBufferBuilder extends CompactBufferBuilder

class HashedBufferBuilder(relation: HashedRelation) extends CompactBufferBuilder

class CorrelatedBufferBuilder(key: Projection, relation: HashedRelation)

class ConstantBufferBuilder(row: Row) extends CompactBufferBuilder

trait MultiwayJoin

 class MultiBuild extends HashSet[Int] with BuildSide

This patch does not change any dependencies.

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

Closing it for now.


[Ready] Fixes the osfToggleHeight initialization in user settings

Purpose
Fixes JIRA issue: OSF-4265
Where the application of the osfToggleHeight plugin to addon node list was unreliable.
Changes
There are two types of data load methods for addons

Those that get added by backend and mako file addon_permissions.mako
-- For these the document.ready function was used to apply
Asyncronous loading with ajax after load
-- For these the initialization was added where nodes have been applied

Side effects
None

I'm checking out the travis fail

@caneruguz update this with develop when you get a second and it'll pass the TCI builds

CR 1 looks good :+1: Moving back to in progress and assigning @caneruguz. Once brought up to speed with develop it can be moved to CR 2 and await the next reviewer.

This looks good to me too! Done with second pass @caneruguz :octocat:


Language translator

Description
Added language translator
Checklist

[x] I am making a proper pull request, not spam.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
Closes #338
I guess difficulty level for this pr should be increased...
Add relevant screenshot or video (if any)

any changes u want??


Python 2 Support

Hi there,
Based on the Pweave documentation, it looks like there is Python 2.7 support. I was a little confused when comparing this to the README which suggests that Python 3 is required since Pweave only works with Python 3. Would you mind clarifying?

@rlaverde?

According to http://mpastell.com/pweave/
Features:
Python 2.7, 3.4 and 3.5 compatibility

So until PWeave 0.3 is out we need to support Python 2. The thing is PWeave 0.3 only supports Python 3.

@rlaverde, we need a 0.1.1 release for this. Also, we need to find all places where we use str and change them to to_text_string.

We develop this plugin with Pweave 0.3 in mind, as @ccordoba12 says it only supports python3
I thought the release of Pweave 0.3 will happen soon, Seeing at Pweave repo it looks like that the next version is almost ready, for that I decided to drop python2 support.

we need a 0.1.1 release for this. Also, we need to find all places where we use str and change them to to_text_string.

I'll work on this, also we need to add a container testing with python2.7

@rlaverde all of our plugins should be to the best extent as possible Py 27/ Py 35 and Py 36 compatible :-)

I'll work on this, also we need to add a container testing with python2.7

Yep, that's true too. I'll open a new container for that.


Android studio crashes when installing Google sceneform Tools (Beta) 1.6.0

Getting this warning..
WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
Affected Modules: app

Hi @BharathBunty - Thank you for the report.  The getMergeAssets warning is from the Sceneform gradle plugin and should not cause the Android Studio plugin to crash.  The crash is likely caused by something else - will you try enabling the 1.7 Google Sceneform Tools plugin in Android Studio, restarting (to trigger the crash), and then when you open Android Studio after the crash (it should disable the plugin again), please go to Help > Show Log in Explorer, and share out the idea.log file?
Also if you could note the platform you're running on that would be helpful.

Hi @tpsiaki  i have uploaded my idea.log file.. i am using android 3.3.1 new release , sorry to inform that it crashes for 1.7 Google Sceneform Tools Plugin also..
idea.log

Hi @BharathBunty - Thank you for the report. The getMergeAssets warning is from the Sceneform gradle plugin and should not cause the Android Studio plugin to crash. The crash is likely caused by something else - will you try enabling the 1.7 Google Sceneform Tools plugin in Android Studio, restarting (to trigger the crash), and then when you open Android Studio after the crash (it should disable the plugin again), please go to Help > Show Log in Explorer, and share out the idea.log file?
Also if you could note the platform you're running on that would be helpful.

Hi @tpsiaki
As you have say about getMergeAssets warning is from Sceneform gradle plugin but, its now from that plugin. It error comes when your are using gradle plugin 4.10.1 version for any android project.
And Android Studio crashed due to the plugin update after 1.4.0 which is faced by many developers. And we are not be able to update this plugin after version 1.4.0. For that see #409  issue. We have mention it with our development  configurations.
And today I am trying to update my JDK version and the try this plugin with different version after 1.4.0 to still latest one. But in all 3 version android studio crashed after restarting android studio. And here I am sharing my log file. Please check it and help us to resolve issue.
My current JDK version is: jdk_1.8.0_201 (This is after updating jdk) and before that I have used version jdk_1.8.0_101 and before this version I am using jdk_1.8.0_65.
idea.log


go work panic

What version of Go are you using (go version)?

$ go version
go version devel go1.18-c239790 Sat Nov 13 03:33:55 2021 +0000 darwin/arm64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN="/Users/sylvain/go/bin"
GOCACHE="/Users/sylvain/Library/Caches/go-build"
GOENV="/Users/sylvain/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/sylvain/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/sylvain/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/homebrew/Cellar/go/1.17.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/homebrew/Cellar/go/1.17.2/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.17.2"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/sylvain/git/go-cache/examples/metered/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/19/d_hlhyz50bs8pbrg6_xn43km0000gp/T/go-build3653344954=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Tried to test go mod workspace and ended up with a panic.
$ cd /tmp
$ git clone https://github.com/sylr/go-cache go-work-panic
$ cd go-work-panic
$ git checkout origin/go-work-panic
$ cd examples/metered
$ gotip build .
panic: in workspace mode, but pruning is not workspace in newRequirements

goroutine 1 [running]:
cmd/go/internal/modload.newRequirements(0x0, {0x0?, 0x0, 0x5?}, 0x0)
	/Users/sylvain/sdk/gotip/src/cmd/go/internal/modload/buildlist.go:118 +0x5d8
cmd/go/internal/modload.LoadModFile({0x100bf2f38, 0x140001a4000})
	/Users/sylvain/sdk/gotip/src/cmd/go/internal/modload/init.go:695 +0x538
cmd/go/internal/modload.LoadPackages({0x100bf2f38?, 0x140001a4000}, {{0x0, 0x0}, 0x14000020060, 0x0, {0x0, 0x0}, 0x0, 0x1, ...}, ...)
	/Users/sylvain/sdk/gotip/src/cmd/go/internal/modload/load.go:341 +0x19c
cmd/go/internal/load.PackagesAndErrors({0x100bf2f38?, 0x140001a4000?}, {0x0?, 0x0?, 0x0?}, {0x1400019e170, 0x1, 0x1})
	/Users/sylvain/sdk/gotip/src/cmd/go/internal/load/pkg.go:2647 +0x120
cmd/go/internal/work.runBuild({0x100bf2f38, 0x140001a4000}, 0x1400002c390?, {0x1400019e170, 0x1, 0x1})
	/Users/sylvain/sdk/gotip/src/cmd/go/internal/work/build.go:398 +0x78
main.invoke(0x100ebe440, {0x1400019e160, 0x2, 0x2})
	/Users/sylvain/sdk/gotip/src/cmd/go/main.go:218 +0x2b0
main.main()
	/Users/sylvain/sdk/gotip/src/cmd/go/main.go:175 +0x770

What did you expect to see?
What did you see instead?

this is a duplicate  https://github.com/golang/go/issues/49591

Duplicate of #49594

Hi, I haven't had time to look at it, but I'm wondering how we know this is a duplicate of #49591? Do we know that they're happening for the same reason?

I assumed they were dups based on the identical panic message and stacktrace

I will reopen this to provide a better error message.


Workspace support?

Inlining the repro.sh I have in my MRE repo for this issue:

cargo-makedocs looks like an interesting tool, but it doesn't seem to work with Cargo workspaces yet.
Steps to reproduce:

Create a new workspace with a single member -- for the sake of example, let's call this binary and make it a new Cargo binary.

dir="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd -P)"
cd "$dir"
NEW_WORKSPACE_NAME="new-workspace"
NEW_MEMBER_NAME="binary"
if [ -e "$NEW_WORKSPACE_NAME" ]; then
	rm -rf "$NEW_WORKSPACE_NAME" || exit $?
fi
cargo new "$NEW_WORKSPACE_NAME" || exit $?
cd "$NEW_WORKSPACE_NAME" || exit $?
rm -rf *
cat > Cargo.toml <<-EOF || exit $?
	[workspace]
	members = ['$NEW_MEMBER_NAME']
EOF
cargo new --bin $NEW_MEMBER_NAME || exit $?

Build the workspace. This shouldn't fail.

cargo build || exit $?

Sanity check: run cargo makedocs on workspace root, expecting it to fail because a concrete workspace member should be used to generate docs.

TEMP_CARGO_INSTALL_ROOT="$dir/cargo-install-root"
if [ -e "$TEMP_CARGO_INSTALL_ROOT" ]; then
	rm -rf "$TEMP_CARGO_INSTALL_ROOT" || exit $?
fi
mkdir "$TEMP_CARGO_INSTALL_ROOT" || exit $?
export PATH="$PATH:$TEMP_CARGO_INSTALL_ROOT/bin"
cargo install --root "$TEMP_CARGO_INSTALL_ROOT" cargo-makedocs || exit $?
cargo makedocs && { echo "expected \`cargo makedocs\` to fail at workspace root!"; exit 1; }
echo "^ This failure is expected -- it's the workspace root. :)"

Change directory into the newly built binary workspace member. Let's try to use makedocs on it, expecting this to work.

cd "$NEW_MEMBER_NAME"
cargo makedocs || exit $?

Unfortunately, the above invocation fails, complaining that Cargo.lock couldn't be found. Cargo.lock DOES exist, but at the workspace root and not this working directory. This seems to indicate that makedocs simply isn't aware of workspaces yet.

You're right, workspaces isn't a feature I've really used much and I partially forgot it existed, heh.
Looking at the behaviour of running cargo doc in the plain workspace, it will document all dependencies for all crates, and running it in a crate will cause it to only document that crate's dependencies. cargo-makedocs should do the same. I'll get to work on it, shouldn't take too long.

I've rolled up a fix in 57dd5f0, which seems to work. It passes the repro and as far as I can tell works just fine. If you could confirm that it works in your original workspace I'll happily publish it.

That particular commit works for me when I do cargo install -f --git https://github.com/Bunogi/cargo-makedocs --rev 57dd5f0, so I think this can be resolved! :) Thanks for the fast turnaround.


Empty SELECT multiple

I try to get a  with notging is checked/selected.
But the function skip this type of element.
I add :
                if (isArray(val)) {
					if(!val.length) // this generates a entry with "null"
						return { name: el.name, value: null, el: el };
                    return $.map(val, function(val) {
                        return { name: el.name, value: val.replace(rCRLF, "\r\n"), el: el };
                    } );

But I got an JSON like:
{selectfield:["null"]} eg {selectfield:[null]}
Otherwiese a {selectfield:[]} would be nicer, but how I can configrue that?
Thanks a lot!

I don't understand the question. Maybe you could try to edit and format using some Markdown? Do you want to deal with empty values? There are options in the README file for that. What is not working exactly?


[Bug]: TTS & SST (Speech) configuration shows up a list of all models instead of configured ones

What happened?
Config Version (librechat.yml): 1.1.4 (1.1.5)
LibeChat Version: v0.7.3
I try to configure SST & TTS over Azure AI. If I add the speech: section in the configuration, LibeChat shows a list of all models (Azure or OpenAI) instead of the models configured in the config.
If the section is added (see screenshot), the log shows missing configuration and TTS schema.
Not sure how to handle this and documentation is not very clear here.
Steps to Reproduce

Upgrade to 0.7.3 and use new config like provided in librechat.example.yml with adjusted parameters as mentioned in https://www.librechat.ai/docs/configuration/stt_tts#azure-whisper-wip
Run the new setup

What browsers are you seeing the problem on?
No response
Relevant log output
LibreChat-TEST | 2024-07-17 07:51:06 error: Failed to get voices: Configuration or TTS schema is missing
LibreChat-TEST | 2024-07-17 07:51:07 error: Failed to get voices: Configuration or TTS schema is missing
LibreChat-TEST | 2024-07-17 07:51:09 error: Failed to get voices: Configuration or TTS schema is missing
LibreChat-TEST | 2024-07-17 07:51:14 error: Failed to get voices: Configuration or TTS schema is missing

Screenshots
Part of the configuration (1.1.4/1.1.5):

Wrong:

Correct (after configuration):

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, thank you very much for updating docs.
I now used azureOpenAI instead of azure in the speech section, but the problem still exists.

Hi @berry-13, thank you very much for updating docs! I now used azureOpenAI instead of azure in the speech section, but the problem still exists.

Sorry about that, I didn't catch the whole message. Unfortunately, you're still out of luck because we still haven't released 0.7.4 yet. You can either wait or pull the latest image for now

Ok. Thank you very much! Then I will wait for 0.7.4. Have a great day!


[Bug Report] The change event does not return the correct value when drag the Slider

Element UI version
0.1.0
OS/Browsers version
谷歌最新版
Vue version
2.6.10
Reproduction Link
https://codepen.io/2ue/pen/QWLQBGM
Steps to reproduce
1.Drag the Slider forward the appropriate distance
2.Release the slider
What is Expected?
when drag, the actual position of the current slider is printed, not affected by the value change
What is actually happening?
What the value value of change returns is not the actual position of the slider, but the value in real time (at this time, the value is affected by the change of other factors, which is inconsistent with the value of the position of the slider).

I meet the same bug,too.
另外希望可以加上滑块本身的事件回调

I am using version 2.15.1 of element-ui and this bug still exists.


[ffigen] Add protocol methods to interfaces

If an interface implements a protocol, but doesn't declare or implement the protocol's methods in the same file, then they won't appear as methods directly on the interface in the AST. This is actually the typical case in most APIs, where the implementation is in a separate file to the interface. This means we don't codegen those methods, so they aren't invocable from Dart, even though they do have implementations and are invocable from ObjC.
The fix is just to parse all the protocols that the interface implements, and copy their methods to the interface.
The only wrinkle is that protocols can have optional methods, which the interface might not implement. If we generate the same Dart bindings for optional methods as we do for required methods, then invoking these methods may cause a crash at runtime with no useful stack trace. There's a special message we can send to the object to check if it has an implementation for a method: respondsToSelector:. So we just have to check if the object responds to the selector, and throw an exception if it doesn't.
Fixes https://github.com/dart-lang/native/issues/1487

coverage: 91.483% (+0.6%) from 90.901%
when pulling eb31baac83fdf94e1d9e60fcf8ee266eecf48528 on protomethod
into c216889fc24e43c59108de05a9f9a2ba05c3cd1d on main.

Out of curiosity, why is this built into the generated code? An Obj-C developer has to do that check themselves, and if they don't and call it anyway it will crash. It seems odd to have a different pattern in Dart, especially since anyone familiar with Obj-C is likely going to assume they need to check, resulting in everything being checked twice (once by the developer, and once by the generated code).

It's not really a different pattern imo. In ObjC if you call an unimplemented method it does crash, but you at least get a stack trace:
** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[ObjCProtocolImplMissingMethod optionalMethod:]: unrecognized selector sent to instance 0x600003b98440'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007ff812230dc6 __exceptionPreprocess + 242
	1   libobjc.A.dylib                     0x00007ff811d209dd objc_exception_throw + 48
	2   CoreFoundation                      0x00007ff8122d6434 -[NSObject(NSObject) __retain_OA] + 0
	3   CoreFoundation                      0x00007ff81219e129 ___forwarding___ + 745
	4   CoreFoundation                      0x00007ff81219ddb8 _CF_forwarding_prep_0 + 120
	5   protocol_test.dylib                 0x00000001129937bc -[ProtocolConsumer callOptionalMethod:] + 76
	6   ???                                 0x000000011290713b 0x0 +<PHONE_NUMBER>    // ^- Useful
)

Without the check in the Dart code, you still get the crash, but the stack trace doesn't include the Dart frames, so it's essentially useless:
** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[ObjCProtocolImplMissingMethod optionalMethod:]: unrecognized selector sent to instance 0x6000002b7830'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007ff812230dc6 __exceptionPreprocess + 242
	1   libobjc.A.dylib                     0x00007ff811d209dd objc_exception_throw + 48
	2   CoreFoundation                      0x00007ff8122d6434 -[NSObject(NSObject) __retain_OA] + 0
	3   CoreFoundation                      0x00007ff81219e129 ___forwarding___ + 745
	4   CoreFoundation                      0x00007ff81219ddb8 _CF_forwarding_prep_0 + 120
	5   ???                                 0x000000010b20713b 0x0 +<PHONE_NUMBER>    // ^- Useless
)

To emulate this stack trace behavior in Dart, I have to check respondsToSelector, but that's an implementation detail. I could change it in future to catch the ObjC exception and rethrow it as a Dart exception. If devs want to use the same pattern as they do in ObjC, where they check respondsToSelector before making the call, that's fine (tho I probably need to expose SEL more in package:objective_c to facilitate this).

but the stack trace doesn't include the Dart frames

Ah, right. Thanks for the explanation!


[Diagnostics]: Diagnostics.AspNetCore3 for supporting ASP.NET Core 3.1

Sanity check for now.
There are a lot of commits, but they are small and self contain. As usual, one at a time.

I'm still making some changes to integration tests, which are not yet included in the PR.
Project regeneration might fail, I've been updating apis.json but still might have missed something.

Towards #4750

Will look on Monday

Cool - I'm happy for you to handle the *.cs wildcard however you see fit; I hadn't thought about the obj directory.
The netcoreapp3.1 targeting is fine by me, and makes sense - it was mostly a matter of checking it was intentional.
I'm happy for you to merge when you've fixed the tabs-to-spaces issue in whatever way you choose :)

@jskeet This is ready for review now.
No changes in production code since you last reviewed.
New commits from integration tests onward https://github.com/googleapis/google-cloud-dotnet/pull/5399/commits/a907c06d687bc920471c568ca152908de08a273b. It's all green on local.
Maybe take a closer look at the documentation commit https://github.com/googleapis/google-cloud-dotnet/pull/5399/commits/b4fb515f00f5905003fcbeaed6eec0875c6de8d1.
Also, suggestions welcomed on how to best squash these commits for merging. Not sure we want to keep all the mid steps.

Cool. Will look tomorrow


PluginManager plugin info printing

Also removes @Test in keeping with Elasticsearch's slow migration away from
the annotation in favor of test methods named testSomeThing.

@kubum, I think my recommendation to look at testing this with vagrant with totally misguided. I picked up this to merge and had a second look at how it could be tested and found the perfect class! PluginManagerIT was the perfect place to test this and already had all the moving bits. Feel free to do with this whatever you like - if you merge it then it'll become part of the pull request back to elasticsearch. If you want to tweak the test then either merge this and make another commit on top of it or don't merge this and reimplement. Its all fine!

@nik9000 it looks just perfect! Thanks a lot for your hard work around it. I just merged it, I don't think there is anything more to add :)

Thanks! I'll go merge the other sie.


Added Service bus message additional fields

Hello,
I had a requirement while doing a project and thought on few things that led to this change.
I understand if it's not on the project's scope and it gets rejected. I just had the idea of how to implement it so I just wrote it down:

I've added some properties that might be helpful when reading the messages. I have used service bus specific naming, which we can rename to accommodate rabitmq, for example the Label property functions as Subject. I have added CorrelationId and SessionId which will be very helpful for developers.
Added some basic unit tests, I don't know if it covers enough or if it follows the styling.

My reasoning behind this is that we can use more properties of Message class the same way ScheduledEnqueueTimeUtc exists.
What do you guys think?
I can always create and inject my own Message Factory, but I think this can lead to a better project.
I have more plans for this in the upcoming weeks.
Cheers

I like the idea, let me review your changes and I'll get back to you.

The problem is that those properties are specific to the service bus message and can't be added to the generic IBusMessage interface

We could just add a dictionary<string, object> and each provider will decide what to do with those properties.

Exactly, that's the only think I was thinking about, but then I saw ScheduledEnqueueTimeUtc . Which is Service bus specific.
Should we mark it as Obsolete?
I'll re-write the fields and see how it looks. ** Grabs wine **

You are right, we might move ScheduledEnqueueTimeUtc as well.

What about this @lucabriguglia ? it does not use reflexion and might be good enough to cover most cases.

I have created a new issue (#55)  and branch (issue/55-bus-message-custom-properties) for this.


OneDrive kopia-assisted incrementals deadlock

Backups that use kopia-assisted incrementals deadlock when backing up OneDrive. From inspecting the code, the most likely cause appears to be a mismatch in the expectations of what items will be read between kopia and the observe package. OneDrive currently creates an observe reader (with a WaitGroup counter) for each item, but does not detect if the item will actually be uploaded to kopia. Since kopia may skip unchanged files, this likely leads to a deadlock
observe package progress function with WaitGroup
OneDrive code that creates readers with progress bar when before it's known if the item data will be required
Delaying making the progress reader until it's known the item data is required will likely fix the deadlock

after testing the above, there's also probably more to the issue than just the observe package. It would probably be more efficient to delay fetching the actual item data until it is known the data is actually needed

after more thought, it most likely is an issue with the WaitGroup in the observe package. The thing I missed previously though is that even if data is not uploaded to kopia, a Reader still needs to be handed to kopia because kopia's StreamingFile initializer requires it. Therefore, ToReader is not a good indicator of whether or not data will be uploaded to kopia

Possible solutions:
1 - Kopia Patch
Allow StreamFile to passthrough a call to produce an io.reader, here:  https://github.com/kopia/kopia/blob/04fcedad1267f9d9ecfab27fb38c3f9aa1d6308f/fs/virtualfs/virtualfs.go#L178
This would allow deferral of a reader (and thus the streaming of data) until kopia requests it.
2 - wrapped reader in Observe
Create a LazyItemProgress(io.ReadCloser, etc...) => io.readCloser func in the observe package that wraps ItemProgress: https://github.com/alcionai/corso/blob/main/src/internal/observe/observe.go#L205.  Defer the itemProgress call (and thus the bar/wg creation) call until Read is called.

@meain - I recommend we go with option #2 above i.e. wrap observe.ItemProgress here in a reader that only initializes that on the first Read

Pushed a PR here https://github.com/alcionai/corso/pull/2126


Build DNSCrypt with gccgo on Solaris 10

Build DNSCrypt with gccgo on Solaris 10 - is it possible in principe? May be, have some documentation, how to build from sources?

Probably.
It compiles fine with regular Go, though, so solaris/amd64 binaries can be added to the list of official precompiled binaries available for download.

Also, would like to run not only on Solaris 11, but also on Solaris 10 which have gccgo, and on Solaris/sparc. If required, I have SPARCv9 server under Solaris 10 with GCC 5.5 (and gccgo, of course).

Solaris/sparc requires gccgo indeed. I have no idea how to do that and if it works, though since gccgo is always running a bit behind upstream go.

It has. OpenCSW has both gccgo, for x64 and SPARC.

Unfortunately I have no idea about how to do this, but maybe you can find help in more specialized forums about Go and Solaris.
If you ever find how to do this, adding the procedure to the documentation would be great!

Don't think so good idea to waste time for compatibility issue for only one service. All other software I'm running written on compatible C/C++, has good compiler, and builds and runs on all servers without issues.
May be, when I have free time, I'll trying to find any solution. Can't guarantee I'll want to waste time for that.
But IMHO it is a very bad idea - decrease service compatibility whenever any benefits and gains.
As old IT maxima said: "Compatibility is more important than performance".


bug: migrate interactive mode

See attached video of the issue. The issue is this function: https://github.com/rehearsal-js/rehearsal-js/blob/c75a696b5042b5d2cf4ca1bc032bd0bc0daf9016/packages/utils/src/index.ts#L539-L551
TL;DR we aren't catching this bug because this is only a visual bug with the rendering of the git diff after package selection. Our tests around interactive mode focus on input keys (which still work). We might be able to leverage something like https://github.com/americanexpress/jest-image-snapshot with dumpDiffToConsole, we need to be able to snapshot interactive mode in addition to the current output stream spy's.
At 0:24 notice the diff renders correctly. After Accept the terminal no longer renders future diffs correctly. All keys and interactivity work just fine; however the user is left in the dark as to selection and diff:
https://user-images.githubusercontent.com/10506014/223703604-3528fd91-389d-4c2e-9c0c-63354f08e8ae.mov

I just quickly debugged this. The issue is coming from chalk. eg this fixes the issue (we still do need to colorize the diff)
export function prettyGitDiff(text: string): string {
  const lines = text.split('\n');
  return lines
    .map((line) => {
      if (line[0] === '+') {
        return line;
      } else if (line[0] === '-') {
        return line;
      }
      return line;
    })
    .join('\n');
}

whats interesting is even with raw control characters I can replicate the issue eg.
const green = '\x1b[32m';
const red = '\x1b[31m';
const reset = '\x1b[0m';

export function prettyGitDiff(text: string): string {
  const lines = text.split('\n');
  return lines
    .map((line) => {
      if (line[0] === '+') {
        // return line;
        return `${green}; ${line} ${reset};`;
      } else if (line[0] === '-') {
        return `${red}; ${line} ${reset};`;
        // return line;
      }
      // return line;
      return `${reset}; ${line} ${reset};`;
    })
    .join('\n');
}


Add Xcode9 and update to 6-29 snapshot on travis #1121

Description

Motivation and Context

How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Codecov Report

Merging #1126 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1126   +/-   ##
=======================================
  Coverage   90.06%   90.06%
=======================================
  Files          36       36
  Lines        1762     1762
=======================================
  Hits         1587     1587
  Misses        175      175

Flag
Coverage Δ

#Kitura
90.06% <ø> (ø)
: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 a026ff1...6f0006f. Read the comment docs.


Update cloudinary extension

Description
Hey! This updates the extension to remove pngpaste as a dependency. Also updates the README which was outdated since this was published.
Shoutout Milena for helping me find the option in the API to replace ti with.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

something funky was going on with the update flow of trying to pull in contributions and update the fork
not sure if i was doing something wrong but had to update the main fork after pulling in contributions through the CLI and then ended up getting conflicts which apparently added some stuff back in without throwing a conflict
anyways, i think it should be good to go now

We'll take a look regarding this, thanks for flagging