ERR_STREAM_WRITE_AFTER_END in Bulk2 Query for CampaignMember

I'm trying to migrate from using Bulk API v1 to v2, but I'm experiencing some issues specifcally when trying to fetch CampaignMembers
I'm using @jsforce/jsforce-node 3.3.1.
If I use Bulk API v1 to run a CampaignMember query, "Stream ended" is shown in console as expected:
    const stream = await connection.bulk.query("SELECT Id FROM CampaignMember WHERE SystemModstamp >= 2024-07-01T00:00:00.000Z")

    stream.on('record', () => {})
    .on('end', () => console.log('Stream ended'))
    .on('error', (error) => {
        console.log('Stream error:', error)
    })

   // "Stream ended" shown in console

However, If I try the same query, but using Bulk API v2 I get an error:
    const stream = await connection.bulk2.query("SELECT Id FROM CampaignMember WHERE SystemModstamp >= 2024-07-01T00:00:00.000Z")

    stream.on('record', () => {})
    .on('end', () => console.log('Stream ended'))
    .on('error', (error) => {
        console.log('Stream error:', error)
    })

This throws:
node:events:497
throw er; // Unhandled 'error' event
^
node:events:497
      throw er; // Unhandled 'error' event
      ^

Error [ERR_STREAM_WRITE_AFTER_END]: write after end
    at _write (node:internal/streams/writable:481:11)
    at Writable.write (node:internal/streams/writable:502:10)
    at DuplexifiedStream.ondata (node:internal/streams/readable:1007:22)
    at DuplexifiedStream.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at DuplexifiedStream._readStream (D:\Repositories\demandlab\insentric-sfdc\node_modules\@jsforce\jsforce-node\lib\util\stream.js:81:18)
    at PassThrough.<anonymous> (D:\Repositories\demandlab\insentric-sfdc\node_modules\@jsforce\jsforce-node\lib\util\stream.js:64:18)
    at PassThrough.emit (node:events:519:28)
Emitted 'error' event on PassThrough instance at:
    at PassThrough.onerror (node:internal/streams/readable:1026:14)
    at PassThrough.emit (node:events:519:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'ERR_STREAM_WRITE_AFTER_END'
}

Note that the error is not emitted by the stream.
It seems that this only happens for querying CampaignMember using Bulk API v2. If I use v2 to bulk query other objects it works as expected. This shows "Stream ended" in console as expected
    const stream = await connection.bulk2.query("SELECT Id FROM Account WHERE SystemModstamp >= 2024-07-01T00:00:00.000Z")

    stream.on('record', () => {})
    .on('end', () => console.log('Stream ended'))
    .on('error', (error) => {
        console.log('Stream error:', error)
    })

hey, sorry for the late reply.
How many CampaignMember records do you have? I'm not able to repro but just have a few thousands

In total, I have ~ 1.6 million CampaignMember
However, I'm filtering by SystemModstamp, and even if I get CampaignMember from a single day (less than a thousand records), I still get the same error.
But now, while re-testing with @jsforce/jsforce-node 3.4.1 I noticed that if I don't add the SystemModstamp filter the query works, I can see the records being processed by using stream.on('record', console.log) but then the stream ends silently when I reach 999.999 records (probably related to #697)
If I add SystemModstamp filter to the query, I get the [ERR_STREAM_WRITE_AFTER_END]: write after end without seeing any records being processed.


Validate objects/instances are registered in Send Request.

This aims to implements : #1472

@JaroslawLegierski any opinion about this feature ? do you want to review it ?

@JaroslawLegierski any news about it ? I would like to know if I can integrate it in master ?

@JaroslawLegierski any news about it ? I would like to know if I can integrate it in master ?

Yes, of course - it's a very good idea to add this feature to the 'master' branch


allow the script to run infinitely

At the moment we can only run this script with set number of transactions. Therefore in cases where we want continuously keep sending transactions over unspecified time we aren't able to do so. Perhaps we can allow to set transaction-count to something like -1 to continuously run the loop?

implemented in #7


Add vending machine restock packs

About the PR
On some long rounds, especially like on MRP Salamander, it wouldn't hurt to allow janitors to restock some of the vending machines.

Sprites ported from tgstation
Can restock completely or partially empty machines after a doAfter
Ordered from cargo (prices will probably need to be tweaked)

Future additions if desired:

Packs for more machines like for Mr. Chang
Drop some inventory of the pack when destroyed (will probably need locked crates for engi/sec packs)

Screenshots

Changelog

:cl:

add: Added restock packs for vending machines. Order them from cargo.

superseded by #11506


Context not working with recursive custom elements and standard decorators

Which package(s) are affected?
Context (@lit/context)
Description
I am creating an HTML-based plugin using Lit. I have a recursive custom element that works like this:
<custom-element>
  <custom-element></custom-element>
</custom-element>

To pass data from one <custom-element> to the other down the tree, we need to define both a provider and a consumer on the same element. Using standard decorators, it looks like this:
import {html, css, LitElement} from 'lit';
import {createContext, provide, consume} from '@lit/context';
import {customElement, property} from 'lit/decorators.js';

const foo = createContext<string>(Symbol('foo'))

@customElement('custom-element')
export class CustomElement extends LitElement {
  @provide({ context: foo })
  accessor provider = 'provided consumer value'

  @consume({ context: foo })
  accessor consumer = 'default consumer value'

  render() {
    return html`
      ${this.consumer || 'undefined consumer value'}
      <slot></slot>
    `;
  }
}

I'd expect to see provided consumer value in the inner <custom-element>, but it displays undefined consumer value instead. With TypeScript decorators, there doesn't seem to be an issue but when using standard decorators, TypeScript throws an error:
Unable to resolve signature of property decorator when called as an expression.
The runtime will invoke the decorator with 3 arguments, but the decorator expects 1-2.

My best guess is that this is due to using accessor, but I don't know enough about accessors to make a firm determination.
Reproduction
TypeScript decorators reproduction (works)
Standard decorators reproduction (doesn't work)
Workaround
Aside from switching the entire project to TypeScript decorators, I have not found a workaround.
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
Failing in<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Browser/OS/Node environment
Browser: Version 125.0.6422.142 (Official Build) (arm64)
OS: macOS Sonoma 14.4.1
Bun version: 1.0.36
Vite version: 5.3.1
TypeScript version: 5.4.5

The lit.dev playground isn't a good test bed for this because it's hardwired for experimental decorators. We have tests of @provide and @consume with standard decorators, if there's a bug we need more coverage, but we see that they compile.
I think the error you're seeing in the playground is that the decorators might not work with experimentalDecorators: true and the accessor keyword.
They are intended to work in this configuration as a way to incrementally migrate toward standard decorators, but we don't seem to have tests for that combination.

Thanks for the quick follow-up @justinfagnani! I'd be a bit surprised if it's TypeScript, as I'm able to use decorators with accessor just fine. Here are the relevant values in my tsconfig.json:
{
    "experimentalDecorators": false,
    "useDefineForClassFields": true
}

After some investigation, it looks like when using standard decorators, the provider needs to be set manually (e.g., in constructor(), connectedCallback(), etc.). If that doesn't happen, the consumer doesn't receive the initially-provided value. This seems to be happening with custom elements broadly, not just recursive ones, so that part of my previous post is irrelevant. Again, this only seems to be happening with the standard decorators.
Could it be due to the decorator function not considering the initial value?

Seeing the same behavior, and using the same workaround (move init to constructor).
Stepping through provide.ts, I see that init is called before the initializer that sets the ContextProvider.

Stepping through provide.ts, I see that init is called before the initializer that sets the ContextProvider.

Good find  @dstoc !
I wonder if the instantiation of the new ContextProvider should move the the init() block and use the value available there as an initialValue option to the ContextProvider constructor.


Code Error？

In the "More About Training" section of your README.md, it mentions:
"# Stage 4 - Do final evaluation (and trim the model by removing the denoising head)
python run configs/pcqm/tgt_at_200m/gap_pred/tgt_at_tp_rdkit.yaml"
Is this a correct Python command? Do you mean by that：
python run_training.py configs/pcqm/tgt_at_200m/gap_pred/tgt_at_tp_rdkit.yaml?

You are right. This is a typo and you have the correct command. I have fixed it in the README. Thank you for pointing this out.


Pass --functions flag to @netlify/config

- Summary
Fixes: https://github.com/netlify/cli/issues/960

- Test plan

- Description for the changelog
Pass --functions flag to @netlify/config when parsing

- A picture of a cute animal (not mandatory but encouraged)
🐶

Closing due to inactivity.


add MPC support for discrete systems

the branch got ported from bitbucket and is now available here

Closing, since this is stale and will most likely not be worked on.


I get extremely large training perplexity

I clone the lastest version from the github and follow the char-rnn.ipynb'step. But I get a very large training perplexity as same as below and it seems that each batch mini-batch's Train-Perplexity is the same value. Why?!
Summary of dataset ==================
bucket of len 129 : 8290 samples
mxnet-20160531-lastet\example\rnn\bucket_io.py:184: VisibleDeprecationWarning: using a non-integer number instead of an integer will result in an error in the future
bucket_plan = np.hstack([np.zeros(n, int)+i for i, n in enumerate(bucket_n_batches)])
[16:37:56] d:\chhong\mxnet\src\operator./reshape-inl.h:227: Using target_shape will be deprecated.
04:37:56 INFO:Start training with [gpu(0)]
[16:37:56] d:\chhong\mxnet\src\operator./reshape-inl.h:227: Using target_shape will be deprecated.
[16:38:02] d:\chhong\mxnet\src\operator./reshape-inl.h:227: Using target_shape will be deprecated.
[16:38:02] d:\chhong\mxnet\src\operator./reshape-inl.h:227: Using target_shape will be deprecated.
04:38:54 INFO:Epoch[0] Batch [50]       Speed: 31.41 samples/sec        Train-Perplexity=10000000000.010738
04:39:46 INFO:Epoch[0] Batch [100]      Speed: 30.42 samples/sec        Train-Perplexity=10000000000.010738
04:40:39 INFO:Epoch[0] Batch [150]      Speed: 30.15 samples/sec        Train-Perplexity=10000000000.010738
04:41:33 INFO:Epoch[0] Batch [200]      Speed: 29.70 samples/sec        Train-Perplexity=10000000000.010738
04:42:28 INFO:Epoch[0] Batch [250]      Speed: 29.39 samples/sec        Train-Perplexity=10000000000.010738
04:42:37 INFO:Epoch[0] Resetting Data Iterator
04:42:37 INFO:Epoch[0] Time cost=275.005
04:43:33 INFO:Epoch[1] Batch [50]       Speed: 28.98 samples/sec        Train-Perplexity=10000000000.010738
04:44:31 INFO:Epoch[1] Batch [100]      Speed: 27.67 samples/sec        Train-Perplexity=10000000000.010738
04:45:24 INFO:Epoch[1] Batch [150]      Speed: 30.51 samples/sec        Train-Perplexity=10000000000.010738
04:46:16 INFO:Epoch[1] Batch [200]      Speed: 30.70 samples/sec        Train-Perplexity=10000000000.010738
04:47:08 INFO:Epoch[1] Batch [250]      Speed: 30.63 samples/sec        Train-Perplexity=10000000000.010738
04:47:17 INFO:Epoch[1] Resetting Data Iterator
04:47:17 INFO:Epoch[1] Time cost=280.155
I really don't know what's wrong with it. Could any one help me?
Any explanation will be greteful!

@liuzhi136 You can try to run the lstm_bucketing exmple

@sxjscience It still very large.
2016-07-22 17:20:10,289 Epoch[0] Batch [50]     Speed: 266.81 samples/sec       Train-Perplexity=9999999999.999542
2016-07-22 17:20:14,221 Epoch[0] Batch [100]    Speed: 407.02 samples/sec       Train-Perplexity=9999999999.998825
2016-07-22 17:20:19,001 Epoch[0] Batch [150]    Speed: 334.79 samples/sec       Train-Perplexity=9999999999.999622
2016-07-22 17:20:23,412 Epoch[0] Batch [200]    Speed: 362.72 samples/sec       Train-Perplexity=9999999999.999296
Do you know the reason? I really upset about it.

@liuzhi136 I've just tried and the result is reasonable. Are you using the latest MXNet version?

@sxjscience Yes, at first I didn't use the lastest version. Then, I get this problem, I download the lastest version and perform the code. It still happen. Could I have your weChat ID or other communication number? I want to talk to you directly.

@liuzhi136 You can first try the image classification examples and see whether they work or not.

@sxjscience I have tried the MNIST example and other image CNN examples. They worked very well. This problem just occur when I run the lstm'code.

@liuzhi136 We can communicate via email first.

@sxjscience<EMAIL_ADDRESS>this is my email. Thank you so much for help me a lot. You are so kind. I'm thinking a problem. I download the version is pre-built version in win7. How's your version? Do you build it by yourself and set envrionment manually?

@liuzhi136 I'm usinh win10 and I've built from source. You can try building from the latest Github source first.

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


[SPARK-8192] [SPARK-8193] [SQL] [WIP] udf current_date, current_timestamp

I'll add unit test/function registry/codegen after #6782  get in.

Merged build triggered.

Merged build started.

Test build #35674 has started for   PR 6985 at commit 9e4bca5.

Test build #35674 has finished for   PR 6985 at commit 9e4bca5.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class CurrentTimestamp() extends Expression
case class CurrentDate() extends Expression

Merged build finished. Test FAILed.

Close it because https://github.com/apache/spark/pull/6782#issuecomment-116888516 for now

@adrian-wang   can you do this one first? This one is simple enough that there is no debate. Update it to address my comment with test cases, and then we can merge it.

Merged build triggered.

Merged build started.

Test build #36384 has started for   PR 6985 at commit 427d9dc.

Test build #36384 has finished for   PR 6985 at commit 427d9dc.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class CurrentDate() extends LeafExpression
case class CurrentTimestamp() extends LeafExpression

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36385 has started for   PR 6985 at commit 98e8550.

Test build #36385 has finished for   PR 6985 at commit 98e8550.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class CurrentDate() extends LeafExpression
case class CurrentTimestamp() extends LeafExpression

Merged build finished. Test FAILed.

I think it again, and since System.currentTimeMillis is not so close to what's inside, I designed to put it back.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36472 has started for   PR 6985 at commit e11ae75.

Test build #36472 has finished for   PR 6985 at commit e11ae75.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class CurrentDate() extends LeafExpression
case class CurrentTimestamp() extends LeafExpression

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36478 has started for   PR 6985 at commit 27c9f95.

Merged build triggered.

Merged build started.

Test build #36483 has started for   PR 6985 at commit 6a20b64.

lgtm

Test build #36478 has finished for   PR 6985 at commit 27c9f95.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class CurrentDate() extends LeafExpression
case class CurrentTimestamp() extends LeafExpression

Merged build finished. Test PASSed.

Test build #36483 has finished for   PR 6985 at commit 6a20b64.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class CurrentDate() extends LeafExpression
case class CurrentTimestamp() extends LeafExpression

Merged build finished. Test PASSed.

Thanks - I've merged this.


Incorrect moons price

Describe the bug
All moon displasy as 0 cost
To Reproduce
Steps to reproduce the behavior:

I have AdvanceCompany V1.1.1 with Lastest LLL version then i update to lastest version of AdvanceCompany
Access terminal to get moons list
See error

Expected behavior
Show corrected moons price.
Screenshots
before

after

Additional context
Logfiles
LogOutput.log
Player.log
Add a list of all of your mods
Please provide a list of all mods you have installed.
Go to Settings and select "Show dependency strings" and copy the text here.
Exporting your profile and attaching it to the issue might also help.

Will be fixed in next version but will only work with my fork ALL as LLL decided to be incompatible by pure choice.

Will be fixed in next version but will only work with my fork ALL as LLL decided to be incompatible by pure choice.


Address compiler warning in 'core' subproject

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.


API to get all known rule systems under a provider

This will help in the discovering all rule system when used under rulette-server

Resolved by #78


Feature request: GitHub Action to install and setup APKO

It would be great if there was an easy-to-use import for github actions that builds the apko image, which could look like this:
- name Build apko image
  uses: chainguard-dev/apko-builder@<hash>
  with:
    path: <image_definition>.yaml
    registry: <some_registry>
    ...

@leongross I think this covers what you need, let me know if the action is missing something you need:
https://github.com/chainguard-dev/actions/tree/main/apko-build

Just came here to post that it seems https://github.com/chainguard-images/actions/blob/main/apko-publish/action.yaml is the correct one, ref. deprecation warning in the action puerco posted.
Also, someone just mentioned this confusion in https://github.com/chainguard-images/actions/issues/146.


API issue with UnknownOption

We have a bit of an API issue with the UnknownOption
The fact that this doesn't work, is perhaps a little unexpected:
        let mut opts = DhcpOptions::new();
        opts.insert(DhcpOption::Unknown(UnknownOption {
            code: 1,
            data: vec![192, 168, 1, 1],
        }));
        let opt = opts.get(OptionCode::SubnetMask);
        dbg!(opt); // None

We can modify From<&DhcpOption> for OptionCode' so that the key in the map is a OptionCode::SubnetMask by changing the unknown branch from:
Unknown(n) => OptionCode::Unknown(n.code),

to
Unknown(n) => n.code.into(),

This way you don't need to retrieve the option value with OptionCode::Unknown(1) which feels pretty weird. But the value you will get back after making the above change for the original code will be:
[src/v4/options.rs:1950] opt = Some(
    Unknown(
        UnknownOption {
            code: 1,
            data: [
                192,
                168,
                1,
                1,
            ],
        },
    ),
)

Again, this feels a little strange. The Unknown option could have been inserted programmatically and unbeknownst to the programmer, if let Some(DhcpOption::SubnetMask(_)) = opts.get(OptionCode::SubnetMask) will not work.
We could decode UnknownOption on insert but that feels pretty icky and would likely require re-allocated to prefix the code u8 at the beginning of the data section.
If anyone has some better ideas, feel free to share
edit:
Another option, we could use the repr(u8) for OptionCode and store the keys as the u8 value. That would solve half of this problem. We may want to do this as part of more general option generating macros described in  #43

I can maybe take a look at this!

Sure! I have not really come to any conclusions about what to do, but I'm open to suggestions. If you have ideas, maybe suggest what that could look like here before you sink time into it. We could also merge the repr change as a first step and go from there, at least then .get(Unknown(1)) would work regardless of how the option was inserted.
Another thought:
It might be interesting to not actually parse the option data section at the time of message decode. Instead, we could concat any long form encoding opts but keep everything as UnknownOption, then on get we could parse the result? Or maybe, get always returns Option<&UnknownOption> but there is a way to decode/convert into its specific variant, or just a method on UnknownOption that returns its parsed data.
We could provide this as a GenericMap along with the one we have today, where the generic version doesn't decode each options data section as above.


Flickering, especially in byobu.

I'm running ptop on a:
2011 Macbook Pro 16GB RAM
running in Mac terminal.app
vagrant ssh
Minimised the issue by customising the CPU refresh time to 2000 with -csrt 2000
Great job with it so far, though.

Is there a significant flickering ? I rarely a face a very little sometimes. Can you attach a gif/image/video if possible ?


Getting it to work with pretty url's

Am currently using https://github.com/Teddy95/EasyRouter to make pretty url's.
I had problem to even login 'cause it keeps getting stuck on /?login so i've changed this lines:
if(!$openid->mode) {
    //if(isset($_GET)) {
    if($_GET['page'] == "?login") {
        $openid->identity = 'http://steamcommunity.com/openid';
        header('Location: ' . $openid->authUrl());
    }
    echo "<form action=\"?login\" method=\"post\"> <input type=\"image\" src=\"http://cdn.steamcommunity.com/public/images/signinthroughsteam/sits_".$button.".png\"></form>";
}

But now it keeps getting stuck on this after login on steam
function __get($name)
{
    switch ($name) {
    case 'identity':
        # We return claimed_id instead of identity,
        # because the developer should see the claimed identifier,
        # i.e. what he set as identity, not the op-local identifier (which is what we verify)
        return $this->claimed_id;
    case 'trustRoot':
    case 'realm':
        return $this->trustRoot;
    case 'mode':
        /*----------here----------*/
        /*$this->data['openid_mode'] IS EMPTY here but anywhere else it returns correct value*/
        return empty($this->data['openid_mode']) ? null : $this->data['openid_mode'];
    }
}

my $this->data is
$this->data = ($_SERVER['REQUEST_METHOD'] === 'POST') ? $_POST : $GLOBALS["true_get_params"];
according to EasyRouter doc
$true_get_params = EasyRouter\main::get_true_params();
Any way to get it to work with pretty url's? Maybe I should change Teddy95/EasyRouter to something different?

Why do you need the pretty url?

emm to have pretty url's? like /user instead of /user.php etc

Oh k

can u try it with out the variable changing thing?

i've get it to work by using https://github.com/mrjgreen/phroute instead

K
Sent from my iPhone

On Feb 25, 2016, at 8:01 PM, jakoboo<EMAIL_ADDRESS>wrote:
i've get it to work by using https://github.com/mrjgreen/phroute instead
—
Reply to this email directly or view it on GitHub.

Closed, but for future reference see #131.


GitHub Action to lint Python code

Output: https://github.com/cclauss/monolens/actions
Future PRs should remove || true from:

[ ] isort --check-only --profile black . || true
[ ] pytest . || true

Hi, linting is done by pre-commit. There is no need to pyugrade. Thanks for the patch anyway.


Incorrect rect area in capsule88.patch ?

void b2CapsuleShape::ComputeMass(b2MassData* massData, float32 density) const
+{
+ 	// Area of rectangle + 2 half circles
+	float32 rectHeight = (m_vertices[1] - m_vertices[0]).Length();
+	float32 rectMass = density * rectHeight * m_radius;

should be
float32 rectMass = density * rectHeight * (m_radius * 2);

Sorry, that code is not supported and no longer exists in master.

Any plans to add capsule shape to Box2D. Of course, I can use a box and two circles, but this sometimes causes some problems, such as clinging to corners.


fix DB file handling of tests

do not use user directories because jrp.db is deleted every time a test is run
download wnjpn.db each time you run a test and it take so long time, so evict wnjpn.db for tests that expect wnjpn.db to not exist

do not treat this issue instead of #74


TypeError: window.plugin.bookmarks.bkmrksObj.portals is undefined

TypeError: window.plugin.bookmarks.bkmrksObj.portals is undefined
intel?l....529874 (Zeile 354, Spalte 4)
latest test build, latest test build bookmarks plugin
just try to bookmark a loaded portal, in my case this portal: https://www.ingress.com/intel?ll=48.449179,-68.531822&z=16&pll=48.450162,-68.529874

This doesn't seem to be happening anymore, I can't cause it on mine anyway. Are you still having this issue?

@jonatkins I think this can be closed, doesn't seem to be happening.


[Stormlib] UNICODE needs to be PUBLIC

Usually UNICODE can be set or not without issues. However in the case of stormlib, TCHAR is part of the API, which can lead to issues.
By default CMake uses MBCS instead of unicode:

https://gitlab.kitware.com/cmake/cmake/-/blob/v3.27.7/Source/cmLocalVisualStudio7Generator.cxx#L805
https://gitlab.kitware.com/cmake/cmake/-/blob/v3.27.7/Source/cmVisualStudio10TargetGenerator.cxx#L1516
https://gitlab.kitware.com/cmake/cmake/-/blob/v3.27.7/Source/cmVisualStudioGeneratorOptions.cxx#L137

This means that a project using CMake defaults would see sizeof(TCHAR)==1 while stormlib would see sizeof(TCHAR)==2.
Make the define PUBLIC so that targets linking stormlib::stormlib will automatically define it too.
Ideally, we would remove the use of this define entirely (this is something that must be controlled by the user, for example using a toolchain file), but this would break current users. We also can not use a feature to togggle this behaviour due to https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md#features

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

@microsoft-github-policy-service agree

https://github.com/microsoft/vcpkg/blob/a1212c93cabaa9c5c36c1ffdb4bddd59fdf31e43/ports/stormlib/vcpkg.json#L4
Please change port-version to 6 and run command ./vcpkg x-add-version stormlib and commitr again

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

#38834 removed the CMakeLists.txt entirely to replace it with the upstream version.
The upstream version does not seem to set the UNICODE macros anymore (which is thus a breaking change), so I will close this pull request.
However I still find it a bit concerning that such changes to ABI (as opposed to API) can happen so easily. But I think that we now have the correct behaviour (keep CMake/toolchain defaults). Perhaps ports with libraries that use TCHAR in their interface should have UNICODE be part of the ABI checks somehow ?


Add validation data to custom domain create option in CDN

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

Checklist completed

Hi @amarzavery  is this ready to be merged?

@fearthecowboy @olydis,
Can anyone help to merge this change?

No modification for Python

No modification for NodeJS

 https://github.com/Azure/azure-sdk-for-ruby/pull/617


Move to AWS v3 library

As the world turns, so do library versions.  Move to AWS v3 - note that this has ONLY been tested on my integration test rig, which means only ec2 / custom networking / vpc, s3, and elb have been tested, however I'm pretty confident in the safety given that those required no changes beyond the gemfile.
That said, I did bump the major version since v3 aws is a major change that affects gem dependencies.  It would work as v2/v3 allowed, if we wanted to do that, though I haven't done that in this PR due to test coverage issues (I wanted something testable in my environment...)
It probably depends on the PR for provisioning being removed from DK, since DK uses aws v2 (though their PR says they want to use v3 as well, and prov-aws is holding them back, so shrug)
Someone other than me should probably test this before merging :)

Updated to not hard require v3, but rather allow it as an option, and remove some cruft comments that I added to the patch

Looks like you can squash this down to a single commit. There's also some Travis failures going on.

@tas50 both facts - the travis one caught a corner case which I had not.  huzzah for tests.  (also squashed now)

@jjlimepoint I'd really like to migrate this gem to the V3 library, but I'd like to make sure we use the individual gems instead of the monolithic gem. There's a lot of code we can shed off if we move to the appropriate v3 gems. Is that something you want to tackle or should I close this out and take a stab myself?

I can do that tomorrow most likely - I mostly avoided it initially in a vain attempt to maintain v2 compatibility - but i'm not super inclined to care about support for v2 if no-one else is!

I'm working to get V3 into kitchen-ec2 and we'll need to do the same thing with inspec. It requires all 3 to land at the same time. Total pain, but we have to do it sometime.


Gather test coverage

Is your feature request related to a problem? Please describe.
Currently, the @guardian/libs coverage is pointing to the now-archived repo.
Describe the solution you'd like
I would like up-to-date coverage reports to be available and badges to work.
Describe alternatives you've considered
We can build our own coverage report if we do not want to rely on external tools such as coveralls.

coveralls doesn't support monorepos.
codecov does but we'd need to go through the tech council

this could be useful development, from tech council pov https://about.codecov.io/blog/codecov-is-joining-sentry-heres-what-you-need-to-know

https://github.com/guardian/CSTI-team/issues/65


How to set the number of words in the answer

Currently we cannot limit the length of the generated answer, it depends on the API provided by Cursor.

If your conversation is cut off due to it being too long, you can try sending a prompt like "Please continue" during the chat to let the AI complete the missing dialogue.


Potential KeyValueProcessor feature: tag_on_failure

When a kv operation causes a runtime exception to be thrown within the processor, the operation is safely aborted without crashing the processor, and the event is tagged with the provided value.
Default is keyvalueprocessor_failure
See: https://www.elastic.co/guide/en/logstash/current/plugins-filters-kv.html#plugins-filters-kv-tag_on_failure

This requires #629 first. And it is another good reason for us to include a tagging related feature.

Relevant links for example of adding tags on json parse failure in the parse_json processor

https://github.com/opensearch-project/data-prepper/blob/3d8d01babf1e4822926f260fa24ca95f69ea6d9f/data-prepper-plugins/parse-json-processor/src/main/java/org/opensearch/dataprepper/plugins/processor/parsejson/ParseJsonProcessor.java#L56
https://github.com/opensearch-project/data-prepper/blob/3d8d01babf1e4822926f260fa24ca95f69ea6d9f/data-prepper-plugins/parse-json-processor/src/main/java/org/opensearch/dataprepper/plugins/processor/parsejson/ParseJsonProcessor.java#L92


Add receipts and assumptions to Bonsai SDK

This PR changes the Bonsai SDK to incorporate composition:

[x] Add the option to include a list of UUID representing receipts as part of the create_session payload
[x] Add the upload_receipt route
[x] Add the test to both new additions
[x] Update alpha_async crate
[x] Update Bonsai SDK crate
[x] Update ethereum crate
[x] Update rest-api-mock-crate

LGTM. Should we also update upload_img to not require the image_id to be passed?

We need the image_id because we use it as the key of pre-signed URLs.

I think the idea @mothran had was we could do the compute_image_id behind the upload_img function so that in the future we could change the primary key/identifier for the REST call later.

I think the idea @mothran had was we could do the compute_image_id behind the upload_img function so that in the future we could change the primary key/identifier for the REST call later.

We don't have access to the byte array in the REST handler because we have users submit directly to s3 to avoid the payload size requirements. There are currently a few factors that are making this pattern annoying so I am considering swapping it out, TDB on what that will look like though.


Your mod is titled under 1.16.4 but does not work with minecraft 1.16.4

Your Cooking For Blockheads mod is titled to use with Minecraft 1.16.4 but file version is 1.16.3-9 which is not compatible.

The 1.16.3 version is compatible with Minecraft 1.16.4.

The 1.16.3 version is compatible with Minecraft 1.16.4.


Price $-0.00

When i pick 3 items in bot inventory and unpick it on  bots offer price on Bot`s offer showing $-0.00.
Please, fix this bug.

What is the problem? The value is still 0.

Does that issue break anything fundamental on the website? If it's really bothering you the step to fix this issue is Math.abs() the price values.


Source map support

Are there any plans to support source maps in Vulcanize? Like any other transformation tool, it'd be really valuable to be able to trace code back to the original source.
I'm not aware of any other tool creating source maps for HTML yet (as opposed to the usual CSS/JS), so the spec might need some adapting in terms of how the source map is referenced from a comment at the end of the generated source file.

+1 to this feature request

+1

+1

+1 for feature request

+1 what's the status on this?  would it likely entail a lot of work?
for things like Chrome's downloads or settings page, we'd probably want some way of reversing a trace back to original code line number as we get a lot of bugs in the wild that are hard to reproduce ourselves

+¹

+1 tracking bugs in production is a PITA without sourcemaps.

I don't believe any browser is capable of understanding anything like an HTML sourcemap at the moment, but I'll evaluate as I go.

@azakus This is a datapoint of one, but the size of my elements are 10:1 JS:HTML/CSS.  When used in conjunction with CSP ....

I've officially run into two bugs in production that I can't reproduce without running it through Vulcanize/Polybuild. The lack of source maps makes Polymer unsuitable for production use and this ticket should at least be prioritized.

@indolering are you combining vulcanize with any html/css minifiers? they can often cause subtle bugs

@robdodson No, but I ran into a bug in Polybuild's CSS minifier too.

In Polymer Starter Kit we had issues with polybuild and switched back to using Vuclanize by itself. Have you tried that?

I combine only babel 5.x and than vulcanize together

@robdodson Turning CSP back on fixed it, I had manually disabled it.  I'm just afraid that something is going to break in the future and I will be unable to troubleshoot it properly.  I can't risk releasing something into production that I might have to pull because I can't troubleshoot what's wrong with the minifier.

related in a stackoverflow: http://stackoverflow.com/questions/34921477/how-to-implement-error-tracking-in-a-polymer

according to https://github.com/PolymerLabs/polybuild polybuild tool is the same as:
vulcanize --inline-css --inline-scripts --strip-comments index.html | polyclean | crisper --html index.build.html --js index.build.js
the order is:

vulcanize produces one html formatted file.
polyclean uses uglifyjs internaly and perform some cleaning
crisper is used to separate already uglyfied and minified js from html

my idea is to change the order of polyclean and crisper and modify polyclean to allow using external options for uglifyjs2:
new order:

vulcanize produces one html formatted file.
crisper is used to separate formatted js from html.
polyclean uses uglifyjs internaly and perform some cleaning (in this case we need to use on both js and html files)

So first you will have html file and formatted js file and only then you can use uglifyjs2(call from polyclean or standalone?) with --source-map and --source-map-include-sources options.
Now you can keep tracking your errors using produced source-map which already contains formatted copy of js file produced in step #2.

+1

+1

+1

+1

+1

+1

Please stop spamming my notification feed with +1 posts, use an emoticon reaction to signal your support and the star button to track it.


artalk: 2.8.6 -> 2.8.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ArtalkJS/artalk/releases.
meta.description for artalk is: A self-hosted comment system
meta.homepage for artalk is: https://github.com/ArtalkJS/Artalk
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.8.7 with grep in /nix/store/c1bh4j4fiqwlyyhwf3pi4n17ppp5nn2s-artalk-2.8.7
found 2.8.7 in filename of file in /nix/store/c1bh4j4fiqwlyyhwf3pi4n17ppp5nn2s-artalk-2.8.7

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

artalk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c1bh4j4fiqwlyyhwf3pi4n17ppp5nn2s-artalk-2.8.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A artalk https://github.com/r-ryantm/nixpkgs/archive/5fca6e1eafa6db00a22a139bc02089b667569ea7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5fca6e1eafa6db00a22a139bc02089b667569ea7#artalk

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c1bh4j4fiqwlyyhwf3pi4n17ppp5nn2s-artalk-2.8.7
ls -la /nix/store/c1bh4j4fiqwlyyhwf3pi4n17ppp5nn2s-artalk-2.8.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

artalk

Maintainer pings
cc @Moraxyc for testing.

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


If no results then show a message

No results found message is displayed on the page if no results are fetched on user selected criteria


Eng/pr getters setters

In this patch, we add the ability to import struct getters/setters
example:
struct X {
    int getX() const {}
    void setX(int) {}
};

// will be:
var Object = X()
Object.x = 1

@swift-ci please smoke test.

I'd specifically like to see some tests that check for the following cases:
void getX();
void get();
int getX();
int get();
int getfoo();
int getFOO();
int GetFoo();
int Getter();

And
void setX();
void set();
int setX(int);
void set(int);
...

And at least one test when we have a setter but no getter.

Another test case: make sure that it doesn't matter which order getters/setters are defined in (i.e., you can define the setter first).

It would be nice to still be able to call the getters or setters explicitly

Yes, I think we should always continue to import the original method. Maybe we want to add a deprecation, though. I think this happens for some Objective-C enums. Maybe something for the forums to decide.

@swift-ci please smoke test.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

It's worrying to see any tests passing... this shouldn't compile.

@egorzhdan want to take another look over this?

@swift-ci please test.

@swift-ci please test.


Create a filter to exclude files from tests

We're adding and removing files from imagegroup directories. Mostly these are json files,  which iiif needs for delivering media.
They get in the way of audit tool tests, because they are counted in sequences, and attempted to read in image processing.
Describe the solution you'd like
Build a filter in shell.properties which specifies a list of regexps to ignore.
Describe alternatives you've considered
The best alternative is to take these files out of "images" and put them somewhere else. We've discussed inverting the way we store all the different versions of our media:
Now it's work major, with Work > {sources|raw|images|archive}/ImageGroup/{img}{*}|{something}{*}.
Additional context
Add any other context or screenshots about the feature request here.

 Filter test subjects

General case of #29, so I'm going to close, undone.


Document recommended target block size

We should define a recommended target block size. This could be defined as block size that is expected to be always accepted by other peers.
Blocks may be any size; however if they are too big, they won't be requested and stored into the peer's global blockchain cache. There is the config setting CacheMaxBlockSize.
For the decentralized search this is important - for each result it may need to fetch the block.
Pro smaller block size:

Fast transfer when requested
Allows caching of more unique blocks

Cons large block size:

More overhead when there are many files: Requires more disk space, is more inefficient in transfer.

Pro large block size:

More files per block

Overhead info:

Each block is signed and the signature takes up 65 bytes.
The block's total header is 115 bytes.
A block record (which follows the header) has a basic size of 13 bytes + the payload data.
A file record uses at least 101 bytes.

Min. block size for storing 1 file (with no additional metadata) = 115 + 13 + 101 = 229 bytes.

-> it should be safe to store a file in 1 KB: This includes a description of ~300 bytes + additional 500 bytes available for other metadata.

Pictures can be resized to smaller than 4 KB and still can be recognized: https://stackoverflow.com/questions/51353422/compressing-an-image-to-make-it-less-than-4kb


Impossible to turn off mqtt light after changing entity name in frontend

Home Assistant release with the issue:
0.84.2
Last working Home Assistant release (if known):
Not sure, 0.83.x or 0.82.x
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian/Python 3.6/virtual_env
Component/platform:
mqtt/light
Description of problem:
Changing the name of the light entity in the frontend makes it impossible to turn off that light. After turn off the light, it stays in HA on.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
light:
  - platform: mqtt
    name: 'Sonoff Basic 1740'
    command_topic: 'homeassistant/light/sonoff-1740/cmnd/power'
    state_topic: 'homeassistant/light/sonoff-1740/stat/POWER'
    availability_topic: 'homeassistant/light/sonoff-1740/tele/LWT'
    unique_id: 'sonoff-1740'
    payload_available: 'Online'
    payload_not_available: 'Offline'
    payload_on: 'ON'
    payload_off: 'OFF'
    qos: 1
    retain: true

Additional information:
Reproduce the issue:

Changing the name of the entity of mqtt light using the frontend

Turning off the light of the newly created entity in the frontend
The light will stay on.
After the HA restart, the light works correctly.

The same issue exists for other components (tested with switch.mqtt), and also if the entity has been autodiscovered instead of added manually.


More info on step 7 - Connection string

in step 7 “When an input box appears, enter your IoT Hub connection string." more information is needed on where to add the connection string. Should be clear that is at the top of VS code.
"In Cloud Shell, you can get the connection string from ~/clouddrive/lva-sample/appsettings.json."
Should also be made more clear where to get the connection string from. Guide people on how to get there. Same screen grabs of the a "cat" of this file in cloud shell for example.

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

ID: 8c6611e1-23a3-48b0-d7e9-b7034bc3be9e
Version Independent ID: b05e4e17-70e7-59eb-3c75-d54efea6aa75
Content: Get started with Live Video Analytics on IoT Edge - Azure - Live Video Analytics on IoT Edge
Content Source: articles/media-services/live-video-analytics-edge/get-started-detect-motion-emit-events-quickstart.md
Service: media-services
Sub-service: lva-edge
GitHub Login: @Juliako
Microsoft Alias: juliako

@tiagonmas Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#please-close see https://docs.microsoft.com/en-us/azure/azure-video-analyzer/video-analyzer-docs/transition-from-video-analyzer


Support database schemas specified in SQL.CONNECTION

Pull requests:

https://github.com/Senzing/init-postgresql/pull/21


privilege issues with admin

EDIT:
python 2.7.6
Django 1.8.12
django-oneall 1.1.2
Using django-oneall for admin login logs the user in just fine, but for some reason the user doesn't have any of their privileges.   I'm merely assigning privs to Groups, and assigning Users to Groups, I haven't tried setting privs for individual users, to know if it's only the group privs, or all privs that are missing.
Of course everything works fine if I setsuperuser my user, but you shouldn't need to be a superuser to user the admin, merely staff and have privs to do things.  Anyway, I can't be using setsuperuser to get admin access as different staff users have different privs, and I don't want them to automatically have all privs.
I haven't dug into Django's source code, but I'm wondering if the privs are cached along with the User in the session or something, rather than looking them up at each request.  Perhaps, they need to be associated to the User object prior to returning it from an authentication function?  Just a wild guess...

The following change to auth.py seems to fix the issue regarding permissions:
#class BaseBackend(object):
class BaseBackend(ModelBackend):
    def __init__(self, existing_user=None):
        self.user = existing_user

    # @classmethod
    # def get_user(cls, user_id):
    #     """
    #     Retrieve user by user ID
    #     :param user_id: User ID
    #     """
    #     return ModelBackend().get_user(user_id)

I'm thinking that by simply subclassing ModelBackend and merely overriding the methods you need to, means you don't need to implement the all the accessor methods for user and group privileges.  I haven't looked deeper into the Django code, so it's still a black box to me, but based on the behavior, but I'm guessing that it might be doing a hasattr for these privilege related accessor methods, and if not found, simply returning an empty set or something like that.

I've added PR #18 which fixes this

Version 1.2 published to PyPI includes this fix.


[DevOps] See if Hauler Can Be a Tool to help airgap process

See if:
https://github.com/rancherfederal/hauler
Can be a viable tool for our workflow to help airgap all images.

closing in favor of:
https://github.com/harvester/tests/issues/1277


[MB] Week of April 19

[ ] Review any pull requests from Hassan

Deliverable: Reviewed pull requests with comments as necessary
Estimate:
Actual:

[ ] Help Hassan with reproducing Blei’s work?

Deliverable: contributions to notebook from #97
Estimate:
Actual:

[x] More work on presentation

Deliverable: Updated presentation
Estimate: 2hrs
Actual: 1hr

[x] More refactoring work

Deliverable: Updated notebooks with assertions at the bottom of the notebook and rewritten functions
Estimate: 4hrs
Actual: 4hrs

[x] Weekly Meeting

Estimate: 2hrs
Actual: 1hr

Closing this from last week.


Interp freq first

Faster performance when using beam_list and the freq is not in the beam.freq_array.

Thanks @r-pascua, that was a useful review.
So, I ended up ALWAYS interpolating to freq if its a UVBeam -- I think that operation is short-circuited properly inside of interp if the frequency is in the data array already (taking into account a tolerance). Plus, that was the only way to ensure that I could safely remove the freq_array on line 300 (otherwise some of the beams would interpolate at all native frequencies).

Ah, okay, that makes sense. It looks like my suggestion of removing the specification of freq_array in the call to interp on line 300 was bunk, since UVBeam.interp apparently requires freq_array. I had assumed this was optional—sorry for suggesting a buggy change.


png quality has weird behaviour

https://github.com/claviska/SimpleImage/blob/2.6.0/src/abeautifulsite/SimpleImage.php#L645
According this line the max quality is 9 (on a scale of 0-100 for the parameter). If I want to update the quality I'm going make it explicitly or to use some pngquant.
Is it done on the purpose ? If yes, why ?

PNG is lossless and therefore doesn't technically have a quality level like JPEG. However, the imagepng() function does accept a $quality argument, but it's used for compression instead of image quality. Per the docs, acceptable values for this argument are 0-9.
My guess is that the PHP manual uses the term $quality instead of something like $compression to be consistent with the imagejpeg() function.
So why not use 9 all the time for PNGs if the quality will be the same? Because higher compression requires more time, and if you're running batch processes it can become very expensive :)
Thus, the SimpleImage library accepts quality as a 0-100 percentage to normalize the "quality" argument that imagepng() (0-9) and imagejpeg() (0-100) both use. This lets you set a relatively similar quality without having to be conscious of the image's format.

Makes sense :+1:


Provide Resend verification email only for DB connections

AD/LDAP connections (and maybe others) can have unverified email addresses, but the verify email action only works for DB connections. So the link to Resend verification email should only be shown to users coming from a DB connection.
API v1's send_verification_email does not check that, but the link sent by email will cause an error when the user tries to use it.

Fixed in #447 and merged into dev


Unable to reach primary cluster manager

I had deployed shipyard in two nodes, when I stop the node1 shipyard-swarm-manager, webui shows below:
{"data":"Unable to reach primary cluster manager (dial tcp <IP_ADDRESS>:3375: getsockopt: connection refused): <IP_ADDRESS>:3375\n","status":500,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"/containers/json?all=1","headers":{"Accept":"application/json, text/plain, */*","X-Access-Token":"??"}},"statusText":"Internal Server Error"}

At node2, shipyard-swarm-manager has started,
{
        "Id": "71c0108b705470668434117e3db47c424707e9bdb40360795e71b6b51766c12a",
        "Created": "2016-12-01T11:51:34.046474735Z",
        "Path": "/swarm",
        "Args": [
            "m",
            "--replication",
            "--addr",
            "<IP_ADDRESS>:3375",
            "--host",
            "tcp://<IP_ADDRESS>:3375",
            "etcd://<IP_ADDRESS>:4001"
        ],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 8540,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2016-12-01T11:51:34.508639829Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        ...
        ...
        ...
        ...

At shipyard-discovery
[etcd] Dec  1 09:30:04.633 WARNING   | Using the directory 3d57cb1eb5bd.etcd as the etcd curation directory because a directory was not specified.
[etcd] Dec  1 09:30:04.634 INFO      | 3d57cb1eb5bd is starting a new cluster
[etcd] Dec  1 09:30:04.635 INFO      | etcd server [name 3d57cb1eb5bd, listen on :4001, advertised url http://<IP_ADDRESS>:4001]
[etcd] Dec  1 09:30:04.635 INFO      | peer server [name 3d57cb1eb5bd, listen on :7001, advertised url http://<IP_ADDRESS>:7001]
[etcd] Dec  1 09:30:04.635 INFO      | 3d57cb1eb5bd starting in peer mode
[etcd] Dec  1 09:30:04.635 INFO      | 3d57cb1eb5bd: state changed from 'initialized' to 'follower'.
[etcd] Dec  1 09:30:04.635 INFO      | 3d57cb1eb5bd: state changed from 'follower' to 'leader'.
[etcd] Dec  1 09:30:04.635 INFO      | 3d57cb1eb5bd: leader changed from '' to '3d57cb1eb5bd'.
[etcd] Dec  1 10:42:48.546 WARNING   | Using the directory 3d57cb1eb5bd.etcd as the etcd curation directory because a directory was not specified.
[etcd] Dec  1 10:42:48.666 INFO      | Peer URLs in log:  / 3d57cb1eb5bd (http://<IP_ADDRESS>:7001)
[etcd] Dec  1 10:42:48.667 INFO      | etcd server [name 3d57cb1eb5bd, listen on :4001, advertised url http://<IP_ADDRESS>:4001]
[etcd] Dec  1 10:42:48.667 INFO      | peer server [name 3d57cb1eb5bd, listen on :7001, advertised url http://<IP_ADDRESS>:7001]
[etcd] Dec  1 10:42:48.668 INFO      | 3d57cb1eb5bd starting in peer mode
[etcd] Dec  1 10:42:48.668 INFO      | 3d57cb1eb5bd: state changed from 'initialized' to 'follower'.
[etcd] Dec  1 10:42:48.994 INFO      | 3d57cb1eb5bd: state changed from 'follower' to 'candidate'.
[etcd] Dec  1 10:42:48.994 INFO      | 3d57cb1eb5bd: state changed from 'candidate' to 'leader'.
[etcd] Dec  1 10:42:48.994 INFO      | 3d57cb1eb5bd: leader changed from '' to '3d57cb1eb5bd'.
[etcd] Dec  1 10:50:33.871 INFO      | 3d57cb1eb5bd: snapshot of 10004 events at index 10004 completed
[etcd] Dec  1 11:08:04.050 WARNING   | Using the directory 3d57cb1eb5bd.etcd as the etcd curation directory because a directory was not specified.
[etcd] Dec  1 11:08:04.124 INFO      | Peer URLs in log:  / 3d57cb1eb5bd (http://<IP_ADDRESS>:7001)
[etcd] Dec  1 11:08:04.125 INFO      | etcd server [name 3d57cb1eb5bd, listen on :4001, advertised url http://<IP_ADDRESS>:4001]
[etcd] Dec  1 11:08:04.125 INFO      | peer server [name 3d57cb1eb5bd, listen on :7001, advertised url http://<IP_ADDRESS>:7001]
[etcd] Dec  1 11:08:04.125 INFO      | 3d57cb1eb5bd starting in peer mode
[etcd] Dec  1 11:08:04.125 INFO      | 3d57cb1eb5bd: state changed from 'initialized' to 'follower'.
[etcd] Dec  1 11:08:04.495 INFO      | 3d57cb1eb5bd: state changed from 'follower' to 'candidate'.
[etcd] Dec  1 11:08:04.495 INFO      | 3d57cb1eb5bd: state changed from 'candidate' to 'leader'.
[etcd] Dec  1 11:08:04.495 INFO      | 3d57cb1eb5bd: leader changed from '' to '3d57cb1eb5bd'.
[etcd] Dec  1 11:08:07.195 INFO      | 3d57cb1eb5bd: snapshot of 12309 events at index 12309 completed

When I add a new node, the port 3375 how to configure when the shipyard-swarm-manager master is down?

If you lose the manager then there is no way for it to elect as it's in  deadlock.  This is a limitation of etcd.  The easiest solution is to re-crerate the cluster and ensure you have at least 3 nodes for HA.  You can also search for etcd recovery to force a leader but that can sometimes have trouble too.

Thanks, what service the every node need installs?


Ability to see the tags of a deployed application

Hi,
in order to move around some applications on some nodes (so that not every app ends up at the first node), I scaled them with tags so they ended up spread in the cluster:
flynn -a myApp scale web=1,host=flynn2

I then removed again the tags (I think):
flynn -a myApp scale web=1

And according to flynn-host ps, the application stayed at the node flynn2.
Now the question: If I later want to check, with what tags an application is deployed?
And I assume, if the application goes down and no more nodes fulfill the tags, then it won't restart?

@philiplb

If I later want to check, with what tags an application is deployed?

We don't currently expose that, I have opened #2809.

if the application goes down and no more nodes fulfill the tags, then it won't restart?

Correct, a job will remain pending if it has tags which cannot be satisfied.

@lmars
Ok, cool. Thank you!

Closing in favour of #2809.


Discussion about evaluate untranslatable queries on the client

@rowanmiller @divega  Can we please have a discussion about the we do not know how to translate the code to be evaluated on the server, we'll do it on the client instead feature?
I for one, think it's a very risky feature, that will cause people significant performance issues when they'll go live-production.
Instead of evaluate on the client and log a warning (most people I believe won't even see them) I suggest throw an exception and log an error and in the exception itself say "we can't translate your code to a query, you can evaluate the code on the client (e.g. ToList() before your , but beware it can be significantly slow operation on large amount of data" (or something like it).
What do you think?

The behavior can be changed with following code in OnConfiguring method
new SqlServerDbContextOptionsBuilder(optionsBuilder).QueryClientEvaluationBehavior(QueryClientEvaluationBehavior.Throw);
Visibility is questionable.

@smitpatel
A. I agree it's not visible at all.
B. It should be the default. EF Core should be safe by default, not the other way around.
C. It should be explicit per query, you might not be aware of all the places you'll get hit by this.
D. It shouldn't exist at all IMHO... I think my suggestion is better, forcing the developer on each query to explicitly say he wants to evaluate the query on the client (with ToList, ToArray etc.).

Customer feedback can always bring new data and help us revisit issues, change our minds and make better decisions. In this case AFAIR we discussed the default behavior and intentionally landed where we are now. I don't remember all the details of the discussion right now but I am sure we considered all the points above, plus the complexity of writing those queries explicitly as client (which assumes knowledge of what a specific EF provider won't be able to translate), plus supporting providers that won't necessary support the same query richness as SQL databases, plus the fact that client evaluation can be ok if the results are bounded (BTW, related to this, we have also considered adding the ability to throw or warn on unbounded results, tracked by #5089 in the backlog).
These two assertions together make me wonder if we need better/stronger guidance on how to take an application into production:

I for one, think it's a very risky feature, that will cause people significant performance issues when they'll go live-production.

Instead of evaluate on the client and log a warning (most people I believe won't even see them)..

Perhaps the solution is to throw by default, but I would certainly recommend all customers to profile their applications and look for warnings on their logs before taking any application to production.

I think it's nice that EF can do this now, especially since it can reorder queries to do as much as possible on the server, which isn't the case with forcing ToList. And #5089 seems to perfectly address the major concern about client eval.
But to address the concerns named here, i would suggest to provide a WithPartialClientEvaluation(bool) [naming WiP] akin to AsNoTracking(). This provides the greatest flexibility combined with the QueryClientEvaluationBehavior setting.

The unbound feature is indeed nice, but not enough.
Besides of returning too many results, if only parts of the query will be translated to SQL(or whatever NoSQL language), the server might not use existing indexes.
@Suchiman I'm not sure why you prefer having WithPartialClientEvaluation instead of simply ToList.

@gdoron

I think it's nice that EF can do this now, especially since it can reorder queries to do as much as possible on the server, which isn't the case with forcing ToList.

That means that you can have Where(runningOnServer).Where(runningOnClient).Where(runningOnServer) and EF takes care of ordering the query in a fashion that allows the first and last Where to execute on the server while only the second executes on the client. It also abstracts away which parts can actually be translated to the server which may vary by store and version.
Also calling ToList will not allow the result set to be streamed, e.g.
Where(runningOnServer).ToList().Where(runningOnClient).FirstOrDefault()

@Suchiman

That means that you can have Where(runningOnServer).Where(runningOnClient).Where(runningOnServer) and EF takes care of ordering the query in a fashion that allows the first and last Where to execute on the server while only the second executes on the client.

Since EF builds Expression tree, it doesn't matter (AFAIK) if the conditions are chained with separate Wheres or in a single Where.

It also abstracts away which parts can actually be translated to the server which may vary by store and version.

That's a bad thing. You should be very aware and excplicit about what won't run on the server as it can have a huge impact on the performance.

Also calling ToList will not allow the result set to be streamed

You can then use AsEnumerable instead of ToList

@gdoron

Since EF builds Expression tree, it doesn't matter (AFAIK) if the conditions are chained with separate  Where s or in a single  Where.

Yes correct, my sample is missing a bit of context, it was associated with the second sample:
EF cannot reorder the query if you insert something to force client eval
Where(runningOnServer).AsEnumerable().Where(runningOnClient).Where(couldRunOnServer)

That's a bad thing. You should be very aware and excplicit about what won't run on the server as it can have a huge impact on the performance.

I'll side here with @divega. It's certainly something you should keep an eye on but we could also start forbidding LINQ at all because it doesn't scale in some scenarios and puts intense pressure on the GC.
Having a choice between

Everything must evaluate server side, even if it requires strong coupling with the data store and raw SQL [QueryClientEvaluationBehavior.Throw, FromSql(string)]
I decide which exact parts i want to run server side and when i start client eval [QueryClientEvaluationBehavior.Throw, AsEnumerable()]
I may target multiple stores or client side applications with 5MB SQLite databases are unlikely a bottleneck, let EF choose for me, i can act if there are signs of decreasing performance [AsEnumerable(), WithPartialClientEvaluation(bool)]

doesn't seems like a bad choice for me, considering that EF Core is no longer a "Server only" framework.

@gdoron @smitpatel Just to clarify on the API for disabling client-eval: It can also be set in the options lambda passed to UseSqlServer().

Client-side evaluation is a very important feature:

It provides LINQ 2 SQL compatibility. I am still stuck on L2S with a significant codebase because rewriting all queries to not use this feature is not feasible. I'm hoping for EF7 to provide relief. Please help us abandoned L2S customers to finally migrate away!
It is very convenient.

L2S was only capable of evaluating a final Select partially on the client.
query.Select(x => new { x.SomeCol, C = CreateClass(x.Col2) })
automatically became
query
.Select(x => new { x.SomeCol, x.Col2 }) //Only fetch relevant columns!
.AsEnumerable()
.Select(x => new { x.SomeCol, C = CreateClass(x.Col2) })

This was efficient as it gets and is super convenient when working with MVC view models. Sometimes, you really need to run some helper code to instantiate or compute something.

So far, we still feel like we have the right defaults.
If you don't like the default, then it can easily be changed. The following code can go in  OnConfiguring  (or in the call to  AddDbContext  in  Startup.cs  if you are working in ASP.NET Core)
optionsBuilder
        .UseSqlServer(...)
        .DisableQueryClientEvaluation();

Agreed that there should be a way to specify whether client eval is OK/not-OK on a per-query basis - this will most likely be post v1.0.0.
Leaving this issue open a little longer to allow further discussion.

@rowanmiller - I couldn't find DisableQueryClientEvaluation() function. 😢

That was the name in RC1. If you are using our nightly builds, then the method is QueryClientEvaluationBehavior(...).

@rowanmiller @divega  Another (very good IMHO) argument for allowing/disallowing client side evaluation on per query level:
Lets say there is a query that I'm aware of it being (partially) locally evaluated and I'm OK with that, I don't want EF to raise warnings and "pollute" my logs with warnings I aware and OK with them.
Am I right?

@gdoron yes that is the primary scenario for per-query overrides.

Got bitten by this quite a few times in the last couple of months. I wish it had been off by default.
I'll try that setting on the optionsBuilder for now.

@rowanmiller  I can't find QueryClientEvaluationBehavior (still on RC2)
services.AddDbContext<ApplicationDbContext>(options =>
	options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection"), b => b.MigrationsAssembly("xxxxxxxx.Web")));

Am I missing a using statement or was it moved to somewhere else?

Here is the code for RC2...
        optionsBuilder.UseSqlServer(
                "<connection string>",
                options => options.QueryClientEvaluationBehavior(QueryClientEvaluationBehavior.Throw));

My apologies if this has been covered elsewhere, but my bing-fu must be weak if it was.  Now that we are on RTM, it appears that this has been removed/renamed. This issue [https://github.com/aspnet/EntityFramework/pull/5396] discusses removing the QueryClientEvaluationBehavior, but I'm just not clear on the replacement mechanism.

@skimedic See here: https://docs.efproject.net/en/latest/querying/client-eval.html#disabling-client-evaluation

@ajcvickers Thank you! My midi-chlorian count must indeed be low.  I missed that several times.

If I turn off client evaluation in db context options, is there any method to explicit turn it on for a specific query?

Unfortunately, currently there's none. 😭

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


[SAMPLE_APP_UPDATES] [Feature] Added rate limiting on Apollo Client

WHY are these changes introduced?
To encourage responsible API usage.
Currently there is no built in way to handle rate limiting. This causes unneeded stress on Shopify's api as well as dropped requests from the user's perspective.
WHAT is this pull request doing?
This pull request is leveraging @apollo/client to wait for available points if applicable, dynamically responding to the shop's refresh rate, available bucket size, etc
Introduced dependencies
zen-observable 80kb, 6M weekly downloads, 0 dependencies. Very safe
Test case
Below is a test case to run up the GQL limit in order to demonstrate the functionality. Feel free to insert your own.
const PRODUCTS_QUERY = gql`
  {
    products(first: 100) {
      edges {
        cursor
        node {
          id
          title
          onlineStoreUrl
        }
      }
    }
  }
`;

  const [productQuery, productQueryState] = useLazyQuery(PRODUCTS_QUERY)

  useEffect(() => {
    for (let index = 0; index < 1000; index++) {
      console.log(index)
      productQuery({variables: {time: Date.now().toString()}});// adding date as unused var prevents request caching
    }
  },[])

@JaKXz Sorry to tag you here, PR's don't usually get responses because of the express build but I wanted to clarify that this is for the express build. Thanks

Sorry for the inconvenience, but this got closed because we're getting ready to merge the sample_app_updates branch as the default (main), so you might need to rebase it.
That being said, I quite like these changes and I think we could look into merging them. Unfortunately, I can't bring this PR back because the base branch doesn't exist any more, but if you decide to redo it, ping me and I'll expedite it!

@paulomarg this has been rebased to #831 831

@paulomarg this has been rebased to #831 831


Modern D tree-sitter grammar and queries

[ x ] Added an entry to CHANGELOG.md if this change could be valuable to users

I'm the author of the tree-sitter-d crate (and the grammar itself), and have provided this grammar for other editors.  I did test this and it seems to work, whereas the stock build I downloaded does not seem to have syntax highlighting for D at all, which was very disappointing (as I use D in my day job).

tree-sitter grammars are now dynamically loaded and I can see D is included in it. So you don't need to add the tree-sitter dependencie. The only thing you'll need to add is the queries.

tree-sitter grammars are now dynamically loaded and I can see D is included in it. So you don't need to add the tree-sitter dependencie. The only thing you'll need to add is the queries.

So how does it know how to find the grammar itself?  Maybe I'm missing something here, but I was following (I thought) the pattern used for other grammars.

Ah, I see now, gishadow used a fork of my grammar, but unfortunately it doesn't have the right queries.  That's because the highlights query there is probably not ideal for lapce.  The default highlights is based on the highlighting used by upstream.

Closing this.  I don't think it will move forward, and maybe now it doesn't need to.


WSO2AM 4.2.0 login failed while using LDAP secondary user stores

Description
It's impossible to login into admin/publisher/and devportal using LDAP secondary user stores.
It works with the primary user store
It works with both primary and secondary user stores in CARBON
Tried to login with :

myaccount
UserStoreDomain/myaccount
myaccount@mydomain

Steps to Reproduce

Configure  LDAP secondary user stores in CARBON

Check Users and Roles

Give ALL PERMISSIONS to all Roles

Configure scopes assignement in ADMIN

Try to login using secondary user stores

Fail !
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
RHEL 8
WSO2 4.2.0 distributed deployment
gateway in docker
control-plane in docker
Docker 26.0.0
Relevant Log Output
TID: [-1234] [2024-04-05 07:24:19,292]  INFO {AUDIT_LOG} - Initiator : myaccount | Action : Login | Target : ApplicationAuthenticationFramework | Data : { "ContextIdentifier" : "17533d4b-6da9-454c-9ddb-47d50cd3218e","ServiceProviderName" : "apim_publisher","RequestType" : "oidc","RelyingParty" : "Dra8r34IYrec15dIPe8939xI9u0a","StepNo" : "1","User Agent" : "null","RemoteAddress" : "null","UserStoreDomain" : "MYDOMAIN.COM" } | Result : Failed

Related Issues
No response
Suggested Labels
publisher login

I just installed a fresh new standalone 4.3.0 version, and it doesn't work !
Can someone have a look on it ?

Same here in apim 4.2.0.
After debuging class found search filter is uid, not sAMAccountName.
Fixed by adding claim mappings.
Carbon - Identity - Claims - List -  http://wso2.org/claims.
Add secondary store User Attributes.

Username - Edit - Mapped Attribute - Add Attribute Mappings:
SECONDARY.STORE.NAME - sAMAccountName
User Principal - Edit - Mapped Attribute - Add Attribute Mappings:
SECONDARY.STORE.NAME - sAMAccountName

Amazing, thank you so much @vitalytchernykh
Your fix works.


[Performance] Move normalized ApolloStore write transactions to background thread.

Question.
We noticed a significant performance regression (particularly on large responses) after the Apollo 2.x upgrade, and the switch  androidx/sqldelight database while using the normalized sql cache.
Part of this can be mitigated by running the database actions in a transaction like the old sql cache, but even with that we noticed a perf hit with the new db.
A more complete solution is to make the ApolloCacheInterceptor perform the response saving on a new thread - there may be a minute risk that a new request that is executed after a response of a previous request will read before the first request has dispatched it's save, but that seems quite unlikely, and the worst case is that you get a cache miss.
Overall it seems pretty safe as:

The Store is already thread safe

All side effects of saving a response are already dispatched on a new thread

Does anyone see any issues with making this change?

We should be able to reach the same performance without adding new threads, right?
Or is there a more fundamental difference between SQLDelight and the Android DB? I'm always a bit reluctant to adding threads if not 100% necessary as it's another source of race conditions and sneaky bugs.

I know the lack of the transaction is one reason of the slowdown, I need to do a bit more research into what else changed. Agree that we should optimize performance of the database regardless.
However, from a design perspective, it doesn't seem correct that a database write blocks an already parsed response from being used. We have been searching for a while why migrating to GraphQL generally causes performance to regress on a page, and I am pretty sure this is the cause.

I've made a small benchmark that writes a query to the cache 100M times. The query is a list of Github repositories containing "lorem ipsum" in the description.
Results are (run on a Pixel 3 XL):

1.4.5 -> 12417ms to write 100M queries
2.2.1 -> 13544ms to write 100M queries

That's ~10% slower if I do the maths right. Is that the same level of degradation you observe on your end?

We saw a 4 second P95 slowdown parsing slow down

@martinbonnin So I dug a bit deeper into the issue - before the 2.1.0 upgrade, we actually had our normalized cache configured wrong, and were only getting the in memory cache. So the upgrade was more akin to re-enabling the sql cache.
We have some queries with 2000 records, which means we are performing 2000 read/write operations on a sql database. It does make sense that re-enabling a transaction will help a bit and could account for the 10% profile change you see (particularly on the write path), but that volume of operations is definitely going to result in a perf hit compared to not using the sql cache.
Blocking a response by up to 4 seconds by enabling sql cache seems like pretty compelling support for moving forward with making the apollo store operations non-blocking (or at least a configurable option).

Will explore more if we can improve the efficiency of the sql cache in general. A 4 second operation on a non-blocking thread isn't fantastic either.

A couple things about the performance example need to be updated:

execute is never called on the write operation, so it isn't doing anything
The dispatcher needs to be set to be blocking to simulate the api which is used while writing a response, as the write operation api uses a dispatcher

After making those changes, and dropping the iterations down to 100 I get (At cache record size of ~1000):

1.4.5 -> 80258 millis or 802ms per operation
2.2.1 -> 81505 millis or 815 ms per operation

So there doesn't seem to be a big performance difference between versions, but 800ms overhead is substantial

Adding back the transaction block brought the performance to a comparable 429 ms per operation. I'll go ahead an put up a PR to fix that.

Regarding making the writes non-blocking, we should keep the guarantee that a read after a write returns the updated value:
val response1 = client.query(SomeQuery()).responseFetcher(ApolloResponseFetchers.NETWORK_ONLY).toDeferred().await() // returns as soon as the network response is received and writes the cache in the background
val response2 = client.query(SomeQuery()).responseFetcher(ApolloResponseFetchers.CACHE_ONLY).toDeferred().await() // should always succeed, no matter the timings

Maybe it can work with some kind of "memory-barrier" that waits until all writes are performed before a read can be done?

So long as the dispatcher that is used with Apollo executes tasks in the order they are submitted, I think we can achieve the ordering requirement pretty easily if we change ApolloInterceptor to use enqueue vs execute when it reads from cache.
This would mean that a cache write is guaranteed to be enqueued before any subsequent cache read. (Additionally the store employs a read/write lock, but it does seem like we need to guarantee the write starts before a later read)

Other less pressing ideas of how to improve performance:

batch all the record reads in the normalized cache (unverified, but I imagine reading a row one at a time in a loop is slower than selecting the entire set)
have a more robust read/write lock system, that allows reads while a disjoin write is occurring. I believe that even if we offload this expensive work to a new thread, multiple operations executed in close succession face a risk where the expensive write blocks the read, essentially delaying the read by the original cost of the write we see in this thread


Improve host to device memory copy

This PR removes CPU overhead.

Jenkins CI test failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit
222b16dae669c3be4bdcfa029bc7d3a0f34a1a50) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit
c27c3d45489701cb422c050eab4a76dac0e775fb) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

@okuta Could you check Jenkins test failures?

Jenkins CI test (for commit 1faceabf5272be9d04888fa3c3beec70d8ba8372) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit 50e9150ac452ca3170885fa3fba3200611a543a1) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Cloud you merge #1385 first?

Jenkins, test this please.

Jenkins CI test (for commit 50e9150ac452ca3170885fa3fba3200611a543a1) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 50e9150ac452ca3170885fa3fba3200611a543a1) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

@okuta Could you check #1393 to fix jenkins failure?

Jenkins CI test (for commit 0b9dec6f48b92b5f5c723da8136d4f0e88c2631e) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 0b9dec6f48b92b5f5c723da8136d4f0e88c2631e) succeeded without errors!

I benchmarked this PR with this code and confirmed performance improvement! 🎉
Current master:
====== ========== ======== ======== ========
--              in_order / out_order
------ -------------------------------------
 ndim    C / C     C / F    F / C    F / F
====== ========== ======== ======== ========
  1      1.53ms    1.47ms   1.46ms   1.40ms
  2      1.44ms    1.47ms   1.51ms   1.43ms
  5      1.49ms    3.78ms   2.34ms   2.91ms
  8     750.61ms   4.62s    1.36s    4.04s
====== ========== ======== ======== ========

This PR:
====== ========== ======== ======== ==========
--               in_order / out_order
------ ---------------------------------------
 ndim    C / C     C / F    F / C     F / F
====== ========== ======== ======== ==========
  1      1.31ms    1.30ms   1.37ms    1.29ms
  2      1.41ms    1.47ms   1.34ms    1.40ms
  5      1.47ms    2.38ms   2.35ms    1.55ms
  8     594.14ms   1.08s    2.39s    635.28ms
====== ========== ======== ======== ==========

Thank you for your performance tests.
I fixed.

Thanks! Jenkins, test this please.

Jenkins CI test (for commit f65a4c510b134c70abb0d686a257ce275b06c80c) succeeded without errors!

LGTM!

Jenkins CI test (for commit f65a4c510b134c70abb0d686a257ce275b06c80c) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Added Permutive

Adding Permutive to README.md, big fans of Circe!

Codecov Report

Merging #1091 into master will increase coverage by 0.2%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #1091     +/-   ##
=========================================
+ Coverage   84.03%   84.23%   +0.2%
=========================================
  Files          76       76
  Lines        2436     2436
  Branches      184      184
=========================================
+ Hits         2047     2052      +5
+ Misses        389      384      -5

Impacted Files
Coverage Δ

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0%> (-2.71%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
79.11% <0%> (+0.63%)
:arrow_up:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
92.5% <0%> (+2.5%)
:arrow_up:

...d/src/main/scala/io/circe/NonEmptySeqDecoder.scala
100% <0%> (+8.33%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
: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 788f23c...b218061. Read the comment docs.

Great, thanks @Joe8Bit!


Refs #32508 -- Raised TypeError/ValueError instead of using "assert" in encode() methods of some password hashers.

Thanks, @felixxm

Thanks y'all for checking :+1:


Several RUSTSEC vulnerabilities in openssl

A cargo audit reveals the following vulnerabilities for the latest hyper-tls 0.5.0
I've opened an issue on native-tls which will need to be resolved first - see https://github.com/sfackler/rust-native-tls/issues/257
Dependency tree:
openssl 0.10.45
└── native-tls 0.2.11
├── hyper-tls 0.5.0
Crate: openssl
Version: 0.10.45
Title: openssl SubjectAlternativeName and ExtendedKeyUsage::other allow arbitrary file read
Date: 2023-03-24
ID: RUSTSEC-2023-0023
URL: https://rustsec.org/advisories/RUSTSEC-2023-0023
Solution: Upgrade to >=0.10.48
Crate: openssl
Version: 0.10.45
Title: openssl X509NameBuilder::build returned object is not thread safe
Date: 2023-03-24
ID: RUSTSEC-2023-0022
URL: https://rustsec.org/advisories/RUSTSEC-2023-0022
Solution: Upgrade to >=0.10.48
Crate: openssl
Version: 0.10.45
Title: openssl X509Extension::new and X509Extension::new_nid null pointer dereference
Date: 2023-03-24
ID: RUSTSEC-2023-0024
URL: https://rustsec.org/advisories/RUSTSEC-2023-0024
Solution: Upgrade to >=0.10.48

None of these need to be tracked here, because hyper-tls can be used with the newer version of native-tls.


Error: Invalid value for option "module".

When I update typedoc to 0.5.5 and execute command-line:
typedoc --mode modules --module commonjs --target ES5 --out ./document ./src/scripts

Then, I got the messages:
Error: Invalid value for option "module".
Error: Invalid value for option "target".

I received no errors before I updated.
Would you mind to check this issue?

@ShiMeiWo, what version were you updating from?

I don't remember the version for certain, v0.5.3 or v0.5.4, maybe.

I wonder if this is related to #373. Something about how those two options are being passed it does not like. Before v0.5.4 it ignored the command line options if they were in the tsconfig.json.
Do you have the module and target options set in a tsconfig.json? If so you don't need them in the command line.

Do you have the module and target options set in a tsconfig.json? If so you don't need them in the command line.

my tsconfig.json is:
{
  "compilerOptions": {
    "sourceMap": true,
    "target": "ES5",
    "outDir": "chunk",
    "module": "commonjs",
    "lib": ["es6", "dom", "ES2015"],
    "baseUrl": ".",
    "paths": {
      "*": [
        "src/scripts/lib/*",
        "src/scripts/*"
      ]
    },
    "declaration": false,
    "locale": "ja-JP",
    "experimentalDecorators": true,
    "traceResolution": true,
    "noImplicitAny": false,
    "removeComments": false
  },
  "include": [
    "./src/scripts/**/*.ts"
  ],
  "exclude": [
    "node_modules",
    "typings"
  ]
}

and I've tried just now:
typedoc --mode file --out ./document ./src/scripts
but I received same error messages:
Error: Invalid value for option "target".
Error: Invalid value for option "module".

I re-installed TypeScript some times, the issues seemed to be fixed few times. I wondered why and checked package.jsons in my workspace and /node_modules/typedoc. And I got some knowledges:

When the version of TypeScript in /node_modules/typedoc/package.json is "2.1.5" and run typedoc, the issues never happen.
When I update that version to "^2.2.0-devYYYYMMDD"(to use Fetch API), the issues happen.
Even there is difference between my workspace's TypeScript version and TypeDoc's TypeScript version, it causes no critical issues.

So, I decided to not update TypeScript version in TypeDoc for the present.
And please note that updating TS 2.2 may cause similar issue.
Thanks a lot, @aciccarello !

Updating the version of TypeScript used by TypeDoc often causes problems because TypeDoc is dependent on TypeScript apis that may have breaking changes between minor versions.
As always, PRs to add support for new TypeScript versions are welcome!


Naive Questions:

Hello,
Can someone answer some naive questions:

Why agents have "backstory" and Task have "Description". Why do not we have only one? In the task, we provide agent then cann't it use Agent's backstory?
Why we need to provide both agents and tasks to the Crew? We are providing an agent to the task then why don't we use it internally? Can it be potentially dangerous if the agents list and task list do not match?  Say in the example posted on the web, the first task is task1 in the tasks array and by mistake, in the agents in write [writer, researcher] then what could happen?

Thanks

don't forget we have https://chat.openai.com/g/g-qqTuUWsBY-crewai-assistant to help and also the discord community https://discord.com/invite/X4JWnZnxPb

The backstory is the system prompt , while the description is the user's prompt ,so you need both of them to help the llm understand what to do exactly  .

2.The reason is that when you define the agents in the task  you just telling it what agents it should use for this exact task , while in the Crew you are telling it to load all the agents that it will need for the entire thing , so the Crew loads them and the task choses which one it needs from them .


Update Slice Subject Reports to take advantage of 'schedules' feature

Currently, the Slice Subject overview report is quite long (Optimal-HF is 22 rows wide); it would be useful, and more compact if Slice was able to use schedules in lieu of individual designs to display this information.
In theory, I would envision it being subjects down the side and schedules or events at the top, with each subject having either a percent completed of a given design (without even taking into account individual sheet completion percentage) or having just a fraction of the forms completed

Subject
Pre-Screening
Screening
Randomized
HLSE
HLSE-O
HLSE-ASV
HLSE-PAP

293478
2/2
2/2
8/19
N/A
N/A
3/4
N/A

Add position to schedules to allow ordering of schedules.

Most reports should have a new application-full.html.haml layout to better make use of screen real-estate.

Counts should be based on existing sheets only rather than sheets that are at 100%


how to open wallet with seeds

See the sample code: https://github.com/monero-ecosystem/monero-javascript#sample-code

When creating a wallet, you can provide mnemonic, or primaryAddress, privateViewKey, and privateSpendKey.


Upgrade Mantine to version 7

Docusaurus 3 interactions with Mantine and the required prism-react-renderer 2+ upgrade have disable syntax highlighting on the landing page.

Why only the landing page and the Reference Manual are affected? I see it is working on the rest of sections.

Closing since GitHub can't merge issues, since the writeup on #90 is much better.


troubleshooting steps for online apps missing

troubleshooting steps for online apps installation on machines such as download issues with error 0x8024500c
would be helpful. Thank you

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

ID: 79d6d496-a7c2-a414-eccc-f1f3a289882e
Version Independent ID: 90fd043b-f4f7-8823-e2f1-61c692699bf2
Content: Troubleshoot MSfB integration - Configuration Manager
Content Source: sccm/apps/deploy-use/troubleshoot-microsoft-store-for-business-integration.md
Product: configuration-manager
Technology: configmgr-app
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @sainirak for the feedback

I checked with our support team, and all of the instances of support cases on this specific error code point to the “Do not connect to any Windows Update Internet locations” GPO blocking WU access

Hi Aaron,
Thank you very much for the quick response. Yes, looks like the issue is with the GPO mentioned.
Regards
Rakesh saini
Get Outlook for Androidhttps://aka.ms/ghei36

From: Aaron Czechowski<EMAIL_ADDRESS>Sent: Tuesday, 7 January 2020, 03:50
To: MicrosoftDocs/SCCMdocs
Cc: sainirak; Mention
Subject: Re: [MicrosoftDocs/SCCMdocs] troubleshooting steps for online apps missing (#2102)
I checked with our support team, and all of the instances of support cases on this specific error code point to the “Do not connect to any Windows Update Internet locations” GPO blocking WU access
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/SCCMdocs/issues/2102?email_source=notifications&email_token=AN6B7OADLUPU66M76WXEOCLQ4OVD3A5CNFSM4KBSVFQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIG7TTY#issuecomment-571341263, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN6B7ODKLGV5CUTHS3XBL3TQ4OVD3ANCNFSM4KBSVFQQ.


HeaderViews with no clickstate

I tried to make them clickable, dispatching touch events directly to decorator headerviews, but the state isn't changed.
Any help?
Right now, the click state passes through the decoration.

It has a click listener and therefor it should also have different states. You could make your own listener that we can use, like if the OnTouchListener gets triggered by MotionEvent.ACTION_DOWN we can do what we want until it changes state.


An outputs folder is needed

There are a lot of scripts in this repo, so a way to keep track of all of them is needed.
Each script should save outputs to it's own folder like how AUTOMATIC1111 webui saves images is necessary for hundreds/thousands of outputs generated. E.g. When using "gradio_canny2image.py", it should be saved in an output folder named something like "canny2image".
Also, the way AUTOMATIC1111 webui names the image's filenames in the output folder would be much more helpful determining how the output was generated. The settings used to generate the image are also embedded in the generated PNG file which include the prompt, negative prompt, steps, sampler, CFG scale, seed, size, and model hash.

+999

+1


test/utils/github_spec: fix artifact URL test

GitHub completely wipes the existance of old CI runs after a couple years.
This'll probably break again in a couple years. Maybe should mock the response or something

Thanks @Bo98!


ULP-RC integration 2.0

Tasks identified for integration as of now -

[ ] Create a schema to store did of issuers Issuer
[ ] Create a service to generate and save, resolve did, resolve issuer did by name, IDService
[ ] Create a service to extract and save the credentials schema CredentialSchemaService

[ ] Make expiration date mandatory in a Credentials Schema
[ ] Use IDService to generate and save issuer did,name, use that to save the schema

[ ] Create a service to issue credential, retrieve, revoke and verify a credential CredentialService
[ ] Write unique tests for all the services created ensuring all the changes


Cannot write to ostream at offset 2097152, e.what() = DB::Exception (from <IP_ADDRESS>:59183) (in query:

ClickHouse 18.16.1

ClickHouse 18.16.1
query sql:


Switch staticpod unit tests to use validateActions instead of messing with reactors

A follow-up for https://github.com/openshift/library-go/pull/70
https://github.com/openshift/service-serving-cert-signer/blob/master/pkg/controller/apiservicecabundle/apiservice_cabundle_controller_test.go#L24

/assign @mfojtik


How to use with bower?

Hi.
I have installed riot from bower and using browserify.
When I'm trying transform with riotify,
var riot = require("../bower_components/riotjs/riot");

require("./dashboard.tag");
require("./navbar.tag");

I have problem:
➜  web git:(master) ✗ browserify -t riotify app/scripts/app.js
Error: Cannot find module 'riot' from '/Users/e/Development/Coiny/web/app/scripts'
    at /usr/local/lib/node_modules/browserify/node_modules/browser-resolve/node_modules/resolve/lib/async.js:51:17
    at process (/usr/local/lib/node_modules/browserify/node_modules/browser-resolve/node_modules/resolve/lib/async.js:159:43)
    at /usr/local/lib/node_modules/browserify/node_modules/browser-resolve/node_modules/resolve/lib/async.js:168:21
    at load (/usr/local/lib/node_modules/browserify/node_modules/browser-resolve/node_modules/resolve/lib/async.js:99:43)
    at /usr/local/lib/node_modules/browserify/node_modules/browser-resolve/node_modules/resolve/lib/async.js:105:22
    at /usr/local/lib/node_modules/browserify/node_modules/browser-resolve/node_modules/resolve/lib/async.js:22:47
    at Object.oncomplete (fs.js:108:15)

My hierarchy:

Sorry. I have no idea how bower works, but from the error message, it seems like "riot" is not installed.

Yep, it's not in node_modules, but in app/bower_components/riotjs.

Then I don't think this is a riotify issue. riotify is just a transformer. It cannot tell browserify where to look for modules.

But it's work when I remove riotify. For example, when I delete line require("./dashboard.tag"), everything is ok, output.js is https://gist.github.com/theaqua/c5ee4db1ca2ea6cfc70c

@theaqua: Does browserify work with any other transformers, such as coffeeify? As in, have you managed to get bower to work with browserify and any other transformers?

Not sure if this makes sense (as I don't know bower), but have you tried bower install --save riotify ?

Thanks, I removed bower and install riot as npm dependency 😂.
Now it works fine!


comment: false does not work

Hi! comment: false does not work (comment is created), but comment: "" works. I guess that's because getInput() returns string and string "false" is considered true.

Thanks for reporting. Would you like to send a PR?


Fixes image, image-minus, image-plus & image-off

In order to get rid of all design guideline violations, the sun needed to be scaled up and the mountain's left slope needed to be shifted by one unit. In order to completely fulfill the guidelines and still keep the right slope of the mountain visible on image-off the mountain also had to have a 2px rounding (see below - red: original, green: fixed):

100% view:
original:

fixed:

100% view. Damn do we have these guidelines for a good reason.

Made image-off appear more like before, but in order to do so, I had to introduce a minuscule design violation (a tiny bit less padding than 2px between the sun + mountain and the plus sign and the mountain):

100% view comparison:
original:

fixed:

Come to think of it, this violation is also present in the previous version of the icon:

One solution would be to add the standard 2px rounding to the mountain shape, although I'm totally not sure if that's the best course of action:

Looks great @karsa-mistmere 👍
But the half-stroke in image-off icon looks bit off to me.

Yeah this looks even better!