how to handle the others command line tools in the env bin

Problem description
Hi there,
before doing a pixi installation I have not thought about the big amount of commandline tools of all the other libs adding to my package. Our project has 421 in the bin dir. A few of them we do use when we are in an env.
It sounds like we should have a description which of them we need. I am not sure if "entry_points" is the best place, because they don't belong to the project. I would prefer a different "other_entry_points" where I can define which gets exposed on global installation. These should get then the namespace of the project as prefix.
https://github.com/Open-MSS/MSS/issues/1922

Hi @ReimarBauer :) if the environment contains some tools in the bin/* folder, you can just run them with pixi run myprogram --help. E.g. you can still run pixi run python even if you don't explicitly expose python as a task.
Does that make sense?

Hi @wolfv
I tried
pixi global install mss
✔ Installed package mss 8.2.0 py310hff52083_0 from conda-forge
  These apps are now globally available:
   -  .mss-post-link
   -  .mss-pre-unlink
   -  mscolab
   -  mss
   -  mssautoplot
   -  msui
   -  mswms
   -  mswms_demodata

this gives
ls -a /home/reimar/.pixi/bin/
.  ..  mscolab  mss  mssautoplot  .mss-post-link  .mss-pre-unlink  msui  mswms  mswms_demodata  pixi

But in ls /home/reimar/.pixi/envs/mss/bin are way more.
I could think about a wrapper script to enter e.g. keyring to my entry points. Would that be the best solution?

Hey @ReimarBauer alright, got it! We don't have a really good solution for this yet. This works nicely if you have a "pixi project" with a pixi toml somewhere. And also mss and friends should be able to find the other CLI programs if it needs them.
But we don't have a way to add more entry points / additional "bin" files yet.
Of course one could install them seperately (but then they'll live in seperate virtual environments, too).

ps. we should probably also get rid of the -post-link and pre-unlink executables in the global install! :)

Closing as stale and in favor of the new pixi global: https://github.com/prefix-dev/pixi/milestone/9


No need to enable RuntimeClass feature gate since it is a GA feature

RuntimeClass feature gate is GA in 1.20. According to feature gate document, a GA feature cannot be disabled and the feature gate is no longer needed. The explanation below can be removed.

Ensure the RuntimeClass feature gate is enabled (it is by default). See Feature Gates for an explanation of enabling feature gates. The RuntimeClass feature gate must be enabled on apiservers and kubelets.

https://kubernetes.io/docs/concepts/containers/runtime-class/#setup

triage/accepted

triage/accepted

/language en

/language en

/triage accepted

/triage accepted

/assign

/assign


(GH-1650) What are Exit codes

CLA signed by all contributors.

@puppetlabs/bolt This is potentially a breaking change, in that it passes 'correct' exit codes when before it just emitted a 0 or 1. I suggest we have a diverse set of people test this in different modules/use cases.

To me, while this is technically a breaking change I don't think it warrants waiting until 3.x to release it. I assume most users check whether the output is nonzero, not explicitly whether it's 1. This seems more like a bugfix to behave the way one would expect than a new feature that would break user workflows.

Hi all,
I test the concat module with bolt(including this PR) and I can fully confirm that this PR solves our problem. Tests on windows platforms pass and tests on Linux platforms pass also.
Please check the results:
appveyor: https://ci.appveyor.com/project/puppetlabs/puppetlabs-concat/builds/36151980
travis: https://travis-ci.org/github/puppetlabs/puppetlabs-concat/builds/741615148
kind regards,
@adrianiurca

Closes: #2318


You can not read and write fields if the serialized field is nil

I think this one is outdated. Closing it for now


[P0] [BUG] Error in Setup Script opening the AKRI Security script in VS.Code

Error in Setup Script opening the AKRI Security script in VS.Code

This should be fixed now with the commit 5d50f43

Fixed, closing the issue.


Update Element Parent and Ancestor methods

Added the ability to select different methods for the Element functions. This requires an update to MDXpy

Thanks, @rclapp, and @Kevin-Dekker!
I will add a comment to the element_is_ancestor function about when to use which MDX.


GIMP Recipe is broken due to broken packages errors

Hi,
Your GIMP Recipe seems to be broken and I'm not just saying that based on build results on my local machine, Travis-CI is backing me up. Look at this build error https://travis-ci.org/fusion809/AppImages/builds/175738234. I copied your current (as of 8 September 2016) revision of the GIMP Recipe as it is slightly out-of-date (2.9.4 is out) and tried to build it, so don't worry it's not just me using an old version of your Recipe.
Thanks for your time,
Brenton

Try with:
ingredients:
  pretend:
    - libcups2 1.7.2-0ubuntu1

This instructs the recipe to assume that this particular version is part of the base system.

Ah but this is a Recipe not a yaml... https://github.com/probonopd/AppImages/blob/master/recipes/gimp/Recipe

https://github.com/probonopd/AppImages/blob/master/recipes/meta/GIMP.yml


Port themes to hubzilla?

Looks like a config.php is required for each theme in order for these themes to be ported in hubzilla.
Is that all that's required or is it a huge job? Anyone working on it?
https://hub.spaz.org/display/1c83b57f38aec1a155e01a668e09f5c87d6195d6a235e35cf27734ea74e58c76@hub.spaz.org?zid=bamfic%40hub.spaz.org

Update: looks like it's not, and they're usable without a config.php file at all.
They just need to be copied into the directory and permitted in the admin screen.

If it helps, I would be happy to make sure all of my themes are compatible.
Out of curiosity, is Hubzilla the main development tree now? I'm currently running Red on my hub, and am eager to switch over.

Hubzilla seems like where all the development action is these days, it's the follow-on to red.
We're running it, and chasing HEAD on git daily, and the team seems very diligent about not committing breaking changes, so it's been very solid so far.
I was able to get the themes to run in hubzilla without a config.php file, but I had to manually add them to the list of allowed themes using the config command line, and also it seems like the user override of CSS isn't working on the red themes.
They're great themes; we're using stumble as the default at the moment.

Just wanted to let everyone know that this is in-progress. See here<EMAIL_ADDRESS>

Switched over; thanks.


VQEClient Runtime callback issue

This was commented as a behavior of the VQEClient on the external Qiskit Slack https://qiskit.slack.com/archives/CB6C24TPB/p1632150351317600
In summary the following seems like incorrect behavior in that the callback is mal-functioning under network error conditions

It seems when using VQE runtime if there is a web socket drop then the callback function returns empty arrays for the iterations and eigenvalues.

There's the option to reconnect the callback after the stream broke with job.stream_results(callback) though that's something the VQEClient would need to take care of since we don't expose the job. However I'm not sure if that's the right approach, since users/we aer usually interested in the history and don't care so much about the data being sent back in real time.

Closing this as per https://github.com/Qiskit/qiskit-nature/pull/1124


Create area with loklak info to show up on bottom of right hand sidebar home, search, report etc.

[x] Add button line as in comment and image https://github.com/loklak/loklak_webclient/issues/424#issue-98722644
[x] © 2015 loklak
[x] About (link to /about)
[x] Blog (link to http://blog.loklak.net) - new tab
[x] Github (link to http://github.com/loklak) - new tab
[x] Facebook (link to http://facebook.com/loklakmessages) - new tab
[x] Match twitter design with white background

Done with the PR above


[docs] Publish: Add note about Babel decorators transform

In docs/_guide/publish.md
npm install --save-dev @babel/core
npm install --save-dev @babel/plugin-proposal-class-properties
npm install --save-dev @babel/proposal-decorators

justinfagnani 3 hours ago  Member
We need to add a note about this Babel decorators transform. The new decorators spec (Stage 2 decorators) are is finalized, and may change, and so might the transform. We test with version ^7.2.0 right now.
@justinfagnani  FYI

That page also recommends decoratorsBeforeExport: true, but that has been accepted as false, ref: https://github.com/tc39/proposal-decorators/issues/69#issuecomment-455538637.
Also related: https://github.com/babel/babel/pull/9360

Now covered on the lit.dev site: https://lit.dev/docs/components/decorators/#decorators-babel


[bug report] Table merged cell data missing

Element UI version
2.13.2
OS/Browsers version
MacOS / 83.0.4103.106
Vue version
2.5.3
Reproduction Link
https://codepen.io/trevorys/pen/GRorMPY
Steps to reproduce
使用arraySpanMethod 当数组为[1,4]时后面的数据后移。
What is Expected?
怎么让数据正常
What is actually happening?
怎么让数据正常

I found it's just merged, Doesn't remove old child.


Implemented Room message and reply methods

Since the room message API call is a subset of the notification call, it makes more sense to redirect to the reply call (with an empty parentMessageId) which looks more like a standard user message.

@successamp Can you take a look at this? I'm in desperate need of this functionality.

Looks fine to me.  I'll publish a new package with this and more updates in a bit.


lsp_server_configuration not working for rls

I am only having this issue with the rust language server. If I try to set server configuration option
  set global lsp_server_configuration rust.clippy_preference="on"

right after lsp-enable Nothing happens. However if I opt-in to clippy with
#![warn(clippy::all)]

At the top of my file it works just fine, indicating that the server understands the option and responds correctly. For some reason its just not the getting trigger through my kakrc. I tried following your instructions for generating an error log but I can't seem to generate the log. Perhaps this is only a feature in master? I'm on 6.2.1

just a little update, I tried setting the option from kak-lsp.toml instead of kakrc using
[language.rust.initialization_options]
clippy_preference = "on"

but it also has no effect. I built master and it still has this issue. I was able to get a log file now though.
https://pastebin.com/raw/p26wdAEh

This seems to be an issue with NixOS and not kak-lsp after upgrading using mozillas rust overlay, everything is working fine. Sorry for the false positive.


how can we integrate Alligator into Play framework?

minor question, how can I use alligator when cooerating with Play framework?

This is not a minor question and is something that should have been done more than two months ago.

If you clone this project you will have everything to run it. I have done it by myself and works perfectly with IntelligentIdea.


Problem show nested tooltip after mouseclick on multiple tooltips

Hi,
I have a problem with multiple nested tooltips.
I have two links which are showing a tooltip with a stack of links. These links can show a tooltip again (nested tooltip).
So on this works well.
But if I have a second link with this construction, I got the problem that the tooltips only work well on the first link. But after I have clicked one of the link inside the tooltip, the nested tooltips on the other link will not showing further. Its hard to recognize what the problem is. But I think it is the mouseclick. What is makes really strange is, that the problem is not appearing every time I have clicked inside the tooltip, sometime the problem comes up first on the second or third mouseclick.
JsBin Beispiel
I have attached a animated gif to show you what the problem is:

Cheers

Hi, this is most likely due to how you wrote your own code, unfortunately I cannot provide support for debug. Thank you.


Detach non-transitioning nodes immediately - #2027 - RFC

Description of the pull request:
This adds a check at the beginning of the transition cycle for nodes that are not up- or downstream of a transitioning node and goes ahead and detaches them immediately.
I'm not entirely sure what this means for nested batches and transitions, but a quick run through looks like it won't release zalgo. I have a feeling that to be 100% accurate this would have to also check parent (and child) manager nodes and transitions, but I also have the feeling that there's no way to cover every corner as parent managers won't be able to check all of their children that may spring into existence.
Thoughts?
Fixes the following issues:
#2027
Is breaking:
I don't think so.

Yessss! #2027 is really annoying. Caused all sorts of weird flickering and layout issues.

Turns out that checking up and down the transition manager hierarchy is necessary so that components don't get dropped before they're ready. So managers that have children when they are started will not kick off immediate removal for now. I think that's a realtively uncommon case. The fix is probably to collect all the nodes and transition up and down the hierarchy when checking for immediate removal, but it's only a one-way association right now and I'm not sure it's worth the refactor for that particular corner case. Of course, I have a long and storied history of being wrong. :smile:

I somehow completely missed the children collection on the transition manager. I think it was the counters that threw me. At any rate, this now checks the whole hierarchy of transitions when considering whether or not a node can be detached immediately.
Does that look ok?

Are we expecting fairly small numbers of outros at any given time that we'd have to dig through?

I would think so, at least not more than a hundred or so. I'd guess more than a few tens would make most browsers stutter pretty badly anyways.


Outline_Shader.tres missing

Skill_Tree_Node.tscn and Skill_Tree_Test.tscn refer to Outline_Shader.tres, but it isn't included in the repo
Thanks for making this!

Just commited it, thank you for pointing it out!
And happy to help!

And go ahead and create some issues tickets if you are interested in certain kinds of features in the skill-tree, then i would go about and try to implement them and then i can explain how they work if needed/wanted

I noticed, that i wasnt even using the outline-shader in the example, as the shader wouldnt show, as the icons are the same size as the sprite-äsize itself, as godot doesnt draw shader-effects outside the bounds of the sprite.
Closing this issue. And Thanks!


Widgets leak the container (in the flex example)

We overflow by default when we can't satisfy a layout. It might make sense for the textbox to have a default max width, though?

Not sure. I would expect:

either the box and the window to grow as the text does
or the sized of the things to be static and the text be truncated e.g. similar to in CSS with ellipsis: https://developer.mozilla.org/en-US/docs/Web/CSS/text-overflow

By design, piet does not support text truncation, because it was going to be a hassle to come up with an API that we could implement reasonably well across the various platforms. The decision was that piet would just lay out the text in the provided space, and then handling overflow would be a job for the next level up in the stack.
There is some hacky support for the window to be sized based on content, but that was not originally part of the design of the layout system, and doesn't really solve the problem in a general sense; eventually your window is the size of your screen, and then you'd have a decision to make.
My personal instinct on this is that the druid user, when designing their layout, should be aware of situations where arbitrary text might be displayed, and account for this. In the context of a TextBox, this would mean providing some size constraints. By default, a single-line textbox will size itself to the size of the text, and if you want it to start scrolling before then you'll need to provide it with an explicit width. In the context of a label, there is a provided LineBreaking enum that lets you specify behaviour on horizontal overflow: clipping, wrapping, or overflowing.
A proper truncation API will be a goal for the next iteration of our text API, but that's out of scope for a while.

Thank you for the thorough explanation.
Do you see anything actionable in this issue?

Only possible that this should be better documented? 🎭 In any case I'll close, sorry again for the slow response.


It's very hard to tell which services are connected

They used to and are supposed to
http://bit.ly/x2O8c5
UPDATE: See below for new mock.

This is the original spec, which is clearer than the implementation:
However I think that this is a better solution:

+1 on "connect more"

I like the second one as well, I think it would be clearer to say "CONNECTED SERVICES" rather than "YOUR SERVICES".

Maybe "already connected" and "connect more"?

Let's just say "Connected" and "Connect More"

I thought it might be more visually distinct if they didn't both start with
"Connect", but it's your call.
On Thu, Jan 19, 2012 at 12:52:15PM -0800, Merci Victoria Grace wrote:

Let's just say "Connected" and "Connect More"

Reply to this email directly or view it on GitHub:
https://github.com/LockerProject/Locker/issues/575#issuecomment-3574015

--

mdz

I thought the word "already" looked a wee bit strange:

updated the issue title and text to reflect the new direction here.

Nice - I like that. Let's use "Connected" and "More Services" :-) Thanks elsmorian!


Fix unit test hash reference and bump cobra and go-containerregistry

Fixes one of the test references and bumps cobra and go-containerregistry.
Closes: #154
Closes: #155

coverage: 69.308%. remained the same
when pulling a4f5d2614aef3263112f4cd36aa1a9221d341539 on fix-test
into b19d259a16023ecfb5101c59787e43a0bdfb6dec on main.


Web - URL address in link preview marked as null for IP address as URL

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open https://staging.expensify.com/
Send a message of an IP address as URL (for example https://<IP_ADDRESS>/)
Wait for the link preview and examine the URL address on the generated preview

Expected Result:
The URL address should be filled with the IP address, like URL with domain
Actual Result:
The URL address for the link preview is filled with "null"
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.41-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @kerupuksambel
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689414673939729
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a0a74fdeb2df46b3
Upwork Job ID:<PHONE_NUMBER>456423936
Last Price Increase: 2023-07-19

It's very important to note that this is "null", not null. It's not distinguishable from an intended publisher with the name "null", however unlikely. Effectively making it a backend issue, as this "null" string does not originate form the front-end.

@sonialiap several have suggested that this is a backend issue so I am gonna make it Internal. Seems kind of on the rare side to enter an ip URL as a preview. I will also ask Microlink.io guys about this to see if they can fix it on their end.

@marcaaron any update on Microlink taking this on?

Yeah I will put a HOLD on this for now and assign myself. They are looking into it so no further action needed for now.

Hi, sorry for bumping on this issue, but I found out that this bug is resolved (either by the Microlink or the backend-related fix) in our production version. (v<IP_ADDRESS>)

Cool thanks! heads up we are putting this feature behind a beta and won't be accepting new bug reports for it moving forward.

This issue was resolved by microlink. @sonialiap we may need to just give @kerupuksambel a reporting bonus.

I am reopening this issue so @sonialiap can issue payment and close when that is completed.
Sonia, could you please finish up the reporting bonus here for @kerupuksambel? Thanks!

@sonialiap - Let me know if you want me to take care of the payment here and I will.

Back from OOO 👋
@kerupuksambel offer for reporting issue $250
New Upwork link: https://www.upwork.com/jobs/~0171e95f4e3a023942


[MSG] Use new RN inquiry modal from artwork VC

This can't be merged yet ofc, because it relies on an Emission update, but when that's good to go so should this be! :)

@alloy @orta the beta says I added new routing for inquiries when this hasn't been merged (or same work added to PR #2379 e.g.) 😅

          1 Error

:no_entry_sign:
Could not find the commit 54a8bd7e6436b0225e18956bb7bd4243aed940f2 in artsy/eigen-artefacts.
You need to git push in the Pods dir.

  Generated by :no_entry_sign: Danger


Handle partial transmits in WSASend (Compatibility with WINE).

Handle partial transmits in WSASend (Compatibility with WINE).
#28472
Associated implementation doesn't stall anymore in WINE.
I tested a significant data transfer: No stalls and works as expected.
The code doesn't handle the fact that the Buffer is on the stack yet which seems in violation with the API of WSASend. In the blocking scenario, this buffer would get out of scope before WSASend is completed.
I  think the buffer could be corrupted before all bytes are asynchronously send. Also the WSAOVERLAPPED information on the stack doesn't seem to influence later use of that buffer by the kernel.
I didn't detect a buffer/stack corruption which I assume would lead to exceptions (reading invalid length and pointers from the stack).
N.B. This PR is not intended to be merged right away.

@ctiller

Duplicate of #28432 really.

@drfloob probably your call on where this goes

Duplicate of #28432 really.

I think this is the same problem, judging the patch and description.

#28524

Thanks @Schramp , sorry I didn't catch the duplication. Let's use the other PR to collaborate on this.


Improve Intellisense for parameters of type Option

As the title describes: the ToolTip on TransactionModel is misleading.
Creating a new test function and wanting to set the TransactionModel the ToolTip shown in VSCode tells me:
TransactionModel(TransactionModel: TransactionModel)
Filling in, for example, AutoRollback after the colon will show an error:
TransactionModel(TransactionModel: AutoRollback )
So I tried the scope operator ::
TransactionModel(TransactionModel::AutoRollback )
And this is fine. SO the Tooltip has to be changed to
TransactionModel(TransactionModel::TransactionModel)

Hi @lvanvugt, this is actually by design and works as inteded. The syntax used on hover is the following one:
AttributeWithSignature(AttributeArgumentName: AttributeArgumentType)

We always show the type and the name of the expected attribute arguments and not how to declare them. This also follows the syntax used by signature help.
For instance, when declaring an EventSubscriber, the tool tip is also as follows:
EventSubscriber(ObjectType: ObjectType, ObjectId: Integer, EventName: Text, ElementName: Text, SkipOnMissingLicense: Boolean, SkipOnMissingPermission: Boolean)

Where the ObjectType also defines an option, for instance: ObjectType::Page.
As the TransactionModel attribute expects one argument named TransationModel of type TransactionModel, the signature is as follows:
TransactionModel(TransactionModel: TransactionModel)

Hi @qutreson makes snese, but it's a darn job to find out what to exactly provide/fill in and intellisense is of no help here.

I'll use this issue in order to track later improvement for IntelliSense when suggesting options.
Probably we could include the scope operator :: when selecting the option TransactionModel among the suggestions for the attribute argument. So that you would directly get TransactionModel(TransactionModel:: and you would then only need to trigger IntelliSense a second time in order to choose which value you want to use.

Agree. And ... intellisense should already show me TransactionModel as the (only) possible value for the property.

What's the status on this right now?


Upate eq-translations to latest commit

What is the context of this PR?
Characters from list keys were being converted to individual translation messages. Additionally, warnings are being shown for translations that don't exist during the build process.
How to review
Check if travis completes correctly and look through the warnings it generates to confirm blank and list characters are no longer shown.

 Answers not translated to Welsh - Sex proxy and remove person


feature: add option for changing docker daemon cpu shares

add Cgroup support for changing docker daemon cpu shares, this will
also restrict cpu usage of all the containers.
two reasons why this option is necessary:

docker daemon SHOULD belong to "docker" cgroup logically, not the
root cgroup as the current version does, and we should supply the capability
to restrict the docker daemon resources.

now we can restrict the cpu shares and cpuset for each container,
but we can't restrict sum of all the containers. To restrict the total
usage of all running containers is useful because we can enable docker
containers can get enough but not too much resource, including cpu,
memory etc.

this patch will start Cgroup support for docker daemon from cpu-shares.
Signed-off-by: Zhang Wei<EMAIL_ADDRESS>

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:HammerOfThor/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

@GordonTheTurtle  it has an "Signed-off-by" field, I'm not sure what's the problem?

I think it's fine sorry
On Friday, February 27, 2015, HammerOfThor<EMAIL_ADDRESS>wrote:

@GordonTheTurtle https://github.com/GordonTheTurtle it has an
"Signed-off-by" field, I'm not sure what's the problem?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/11074#issuecomment-76513819.

ping @jfrazelle , what do you think of this feature, any suggestions?

Replaced by https://github.com/docker/docker/pull/11273
@HammerOfThor in future, could you please update the PR in stead of creating a new one. Also when closing a PR in favor of a new one, please add a message (like above), this makes it easier for people to find "what happened" :smile:

@thaJeztah OK, got it. Thank you for your kind reminder! :)

@HammerOfThor you're welcome. Was just browsing through issues and remembered the new PR you created, no harm done! :smile:


cwl dynamic resource requirement bug

I am trying use the dynamic resource requirement feature in gridEngine which was merged in #1810 and found an issue.
To reproduce the issue, please add the below lines to toil/src/toil/test/cwl/revtool.cwl  and run "cwltoil --no-container --retryCount 0  --batchSystem gridEngine revsort.cwl revsort-job.json"
requirements:
  - class: InlineJavascriptRequirement
  - class: ResourceRequirement
    ramMin: $(inputs.input.size)

Below is the worker log for sorttool
---TOIL WORKER OUTPUT LOG---
INFO:toil:Running Toil version 3.13.0-3cb535425306955028ed7604114f772990d00440.
Traceback (most recent call last):
  File "/work/toil/src/toil/worker.py", line 301, in main
    job = Job._loadJob(jobGraph.command, jobStore)
  File "/work/toil/src/toil/job.py", line 902, in _loadJob
    return cls._unpickle(userModule, fileHandle, jobStore.config)
  File "/work/toil/src/toil/job.py", line 931, in _unpickle
    runnable = unpickler.load()
  File "/work/toil/src/toil/job.py", line 1735, in __new__
    return cls._resolve(*args)
  File "/work/toil/src/toil/job.py", line 1747, in _resolve
    value = pickle.load(fileHandle)
  File "/work/toil/src/toil/job.py", line 1735, in __new__
    return cls._resolve(*args)
  File "/work/toil/src/toil/job.py", line 1747, in _resolve
    value = pickle.load(fileHandle)
  File "/work/toil/src/toil/job.py", line 1827, in __setstate__
    "this job as a child/follow-on of {jobName}.".format(jobName=jobName))
RuntimeError: (RuntimeError(RuntimeError("This job was passed a promise that wasn't yet resolved when it ran. The job 'file:///work/toil/src/toil/test/cwl/revtool.cwl' rev that fulfills this promise hasn't yet finished. This means that there aren't enough constraints to ensure the current job always runs after 'file:///work/toil/src/toil/test/cwl/revtool.cwl' rev. Consider adding a follow-on indirection between this job and its parent, or adding this job as a child/follow-on of 'file:///work/toil/src/toil/test/cwl/revtool.cwl' rev.",), <class 'toil.job.Promise'>, (u'file:/tmp/tmp14goWU', 'N/u/tmpF1_VvA.tmp')), <class 'toil.job.Promise'>, (u'file:/tmp/tmp14goWU', 'O/g/tmp_Mr8W3.tmp'))
ERROR:toil.worker:Exiting the worker because of a failed job on host host01
WARNING:toil.jobGraph:Due to failure we are reducing the remaining retry count of job 'file:///work/toil/src/toil/test/cwl/sorttool.cwl' sort J/b/jobhOqgt1 with ID J/b/jobhOqgt1 to 0

As per my understanding, there are two steps revtool and sorttool in the revsort workflow. Two wrapper jobs are created for both of them. The revtool_wrapper spawns the actual revtool job, but also sorttool_wrapper job is started. Since sorttool wrapper does not have its promise fulfilled the workflow fails.

Hello @pkp124 and thank you for your report. Is this reproducible using the latest dev version of Toil?
http://toil.readthedocs.io/en/3.12.0/gettingStarted/install.html#building-from-source

Hello @mr-c , thanks for the quick response. I was able to reproduce the same issue on the latest commit of the master branch, although i had to rerun multiple times (~ 10) to reproduce the issue.

@pkp124 Thanks. I am also now able to reproduce and I will continue my investigation.

@pkp124 Does https://github.com/BD2KGenomics/toil/pull/2049 work for you?

@pkp124 I think we fixed it! Thanks again for alerting me to this issue and for the easy to reproduce example; that was very helpful.

@mr-c , thanks for the effort. I did some quick tests today and unfortunately, found that the error still persists :)  Again, the issue can be reproduced with the same files, by running multiple times.

Okay, @DailyDreaming @ejacox and others, I need your help.
When in toil-cwl-runner we have dynamic resource requirements we add a CWLJobWrapper to the job graph so we can attach the real job with the current memory, cpu, and disk requirements once the inputs are known.
In an attempt to address this issue I added a follow on link between the existing children of the CWLJobWrapper and the new "real" job:
https://github.com/BD2KGenomics/toil/blob/ad1a097f45d5019540972da36d44a805b1104b72/src/toil/cwl/cwltoil.py#L400
Seems like this isn't enough. Any suggestions?

One thing I noticed, the CWLJobWrapper does not seem to have any children.

@pkp124 Yes, and it is missing the reference to its predecessors as well. Perhaps a pickling error?

To be fair, I was using a non-public member of Job; seems that accessing the children is not a feature of Toil right now: https://github.com/BD2KGenomics/toil/blob/ad1a097f45d5019540972da36d44a805b1104b72/src/toil/job.py#L1092
However, we can modify the Workflow runner to make the descendants of the CWLJobWrapper as "follow ons" and not "children": https://github.com/BD2KGenomics/toil/pull/2053

Not sure about this, but, couldn't all the jobs be followOns regardless of wrapper or not?

@pkp124 Possibly, but I don't know all the consequences of that, so I'm trying to make minimal changes


tapdb: improve batch marshalling

Addresses #1125 .

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

1 of 3 (33.33%)  changed or added relevant lines in 1 file are covered.
13 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.003%) to 40.402%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tapdb/asset_minting.go
1
3
33.33%

Files with Coverage Reduction
New Missed Lines
%

commitment/tap.go
1
83.64%

tapdb/addrs.go
2
79.04%

tappsbt/create.go
2
53.22%

universe/interface.go
4
50.22%

tapdb/universe.go
4
80.91%

Totals

Change from base Build<PHONE_NUMBER>8:
0.003%

Covered Lines:
24214

Relevant Lines:
59933

💛  - Coveralls


Book list

Add a book list to my site that includes "most influential" reads and why they were influential

Instead of a book list, it may be more valuable to write blogs on "core concepts" and then reference books that have helped me understand these core concepts.
I recently learned Naval Ravikant and I have the same reading style. I pick up many books and pick through them - not always finishing the books. I'll be reading many many books at the same time.
I used to look at this as a failure - not having completed all the books. It's valuable to free myself of this and just focus on pure learning. As long as I grasp the core concepts - I've achieved my goal and do not need to finish the book in order to get a trophy.


Questions about the Stack-LLaMa

Hi, I see the https://github.com/lvwerra/trl/tree/main/examples/stack_llama/scripts and found it a good RLHF tutorial. However, there are some steps I can't figure out.
The first step is "Supervised fine-tuning of the base llama-7b model to create llama-7b-se", and the second step is "Reward modeling using dialog pairs from the SE dataset using the llama-7b-se to create llama-7b-se-rm".
Why do you train the reward model based on llama-7b-se, rather than llama-7b?
And I see the model loading scripts(from https://github.com/lvwerra/trl/blob/main/examples/stack_llama/scripts/reward_modeling.py) is :
model = AutoModelForSequenceClassification.from_pretrained(
    script_args.model_name, num_labels=1, torch_dtype=torch.bfloat16
)
model = get_peft_model(model, peft_config)
model.print_trainable_parameters()

the model_name seems to be the llama-7b-se path, which is a LoRA weights path, is this the right way the load a LoRA model? And does this mean that in the reward modeling step, a new LoRA model is added to the first SFT LoRA model?
I'm not sure if I put it clearly, lol. Looking forward to your reply, many thanks!

Why do you train the reward model based on llama-7b-se, rather than llama-7b?

In practice, it helps if the base model was already fine-tuned on the target data, such as llama-7b-se, so the reward model gets a bit better.

the model_name seems to be the llama-7b-se path, which is a LoRA weights path, is this the right way the load a LoRA model? And does this mean that in the reward modeling step, a new LoRA model is added to the first SFT LoRA model?

We merged the adapters into the base model before the RM training with the merging script. Then the training script simply adds a new adapter on top of that model
Hope this helps!

Got it! Thanks!

Closing this as the questions seems answered - feel free to re-open if not!

Hi @lvwerra , I'm tuning the PPO training these days but found the training is quite unstable. Could you please give some advice of the parameter setting?
My problem is that after several iterations, the model seems start to generate empty outputs which however have high rewards:

And this seems to lead to an error: autodetected range of [nan, nan] is not finite.
I guess there're some hyper-params that I can tune to aviod this behavior, could you give my suggestions? Thanks!

Hi @lvwerra , I'm tuning the PPO training these days but found the training is quite unstable. Could you please give some advice of the parameter setting?
My problem is that after several iterations, the model seems start to generate empty outputs which however have high rewards:
And this seems to lead to an error: autodetected range of [nan, nan] is not finite.
I guess there're some hyper-params that I can tune to aviod this behavior, could you give my suggestions? Thanks!

Having the same issue autodetected range of [nan, nan] is not finite. I've tried some combinations of mini_batch_size and gradient_accumulation_steps according to https://github.com/huggingface/trl/issues/545#issue-1812590848, but I still can't figure out a solution.
@lvwerra Could you please help with some advice? Thank you.

Maybe you should add a term to the reward function that penalises short responses? You can also force the generate function to at least produce n tokens.

Maybe you should add a term to the reward function that penalises short responses? You can also force the generate function to at least produce n tokens.

So does this mean that short responses are easier to lead to something like gradient explosion causing the nan error?

I have a workaround: https://mp.weixin.qq.com/s/O5dfAfgNO7TudQIGqxg6Dw
which simply adds the EOS token to the begin_suppress_tokens parameter.

You can set the eos_token_id=-1 in the generation kwargs to guarantee that the model doesn't stop generating even if an EOS token occurs. You can decide how to handle that case then in the reward function: maybe to compute the reward you cut-off everything after the eos token or you give a penalty to it.

It appears that adjusting min_new_tokens to prevent short responses is effective. Thank you all!

Note that it can lead to negative KL issues so the suggested approach is safer with max_new_tokens and eos_token_id=-1. See https://huggingface.co/docs/trl/main/en/how_to_train#what-is-the-concern-with-negative-kl-divergence


DIAC-137 Add logs to Payments create service request API

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DIAC-137
Change description
Add logs to Payments service request API call
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Raised #328


Always virus scan uploaded files

Previously a virus scan was only triggered if the file had "changed" according to ActiveModel::Dirty. However, this seemed to have been based on whether the filename of the file had changed rather than whether the content had changed which seems to be the more relevant issue. This meant that (as described in #72) it was possible to update an existing asset with a file having the same name, but different content and for the asset to remain in the "clean" state. This seemed like a security hole.
Initially I investigated triggering a virus scan when the file content changed. However, this proved awkward due to the way both state_machines and carrierwave gems work. So after discussion with @chrisroos & @chrislo, I decided to trigger a virus scan whenever the Asset#file attribute is changed. While this means virus scans will sometimes be triggered unnecessarily, I don't think it should happen too often and it seems better to do this than allow unscanned files to be served to the citizens.
I'm not sure this is the most elegant solution, but since the Asset#file= method already existed, it seemed simplest to make use of it. A better solution might involve persisting an MD5 digest of the file content which has been virus scanned and then only re-scan the content if it has changed. However, the extra complexity doesn't seem warranted.
Fixes #72.

@chrisroos: Thanks for reviewing.
Merging.


Support for int8 mma for sm75

Implement int8 dot for Turing
Ampere: a single mma.sync.aligned.m16n8k32.row.col.satfinite.s32.s8.s8.s32 instruction
Turing: 4 x mma.sync.aligned.m8n8k16.row.col.satfinite.s32.s8.s8.s32 instructions that combine computation to emulate the Ampere instruction above

looks generally ok but I think now we're at the point where it makes sense to have subroutines for differen modes (turing, etc.)


Points to our fork of tipsi-stripe #trivial

We need to point to point to our fork of tipsi-stripe because we pulled in this fix for this issue (it'll be included in an upcoming release of tipsi-stripe, so I'm fine still pointing to my own fork). Previously, we did this in Eigen, but was removed in the RN upgrade infrastructure PR:
https://github.com/artsy/eigen/pull/2962/files#diff-4a25b996826623c4a3a4910f47f10c30L101
This was causing the bug (app crashes when entering credit card number) to re-occur.
This adds it back, using that new infrastructure mechanism. I took a look at the other RN pods that we were pointing to forks on, and it appears all the changes we'd made are now included in their upstreams, so we're good to go 🙌

Took off the MOG label to apply this change first:
https://github.com/ashfurrow/tipsi-stripe/commit/aeb742baf1a8329ba371d9c94c7650104a112807
We were pointing Yarn to my fork, but it was pointing CocoaPods back to the main source 😭 I verified the code change was included in the Objective-C this time (the bug doesn't present in the Emission Example app).

:rocket: PR was released in v1.19.11 :rocket:


updateEmail failure returns same response code for email in use and jwt error

Currently in the web-sdk we will receive the following error responses from the updateEmail function:

the email is already in use - we receive status code 400 and a message {"msg":"Cannot change user  to . New email already exists","code":"EmailAlreadyExists","params":null} - its worth noting here that we don't have access to this message from the response callback of the updateEmail function
the JWT token is not authorized - we receive status code 400 and a JWT specific error message

This means we have no way to distinguish when we can ignore the call (the email already exists we just ignore the response) and when we need to refresh our jwt token.

hey @danwbyrne, the error shape is an AxiosError, so when you are catching your promise errors you can get access to the Iterable response like so:
import { AxiosError } from 'axios'
import { IterableErrorStatus } from '@iterable/web-sdk';

updateUserEmail(...args)
  .then((response) => response)
  .catch((error: AxiosError) => {
    const iterableCode: IterableErrorStatus = error.response.data.code;

    if (!!iterableCode.match(/emailalreadyexists/gi)) {
      /* do something */
    }

    if (!!iterableCode.match(/jwt/gi)) {
      /* do something else */
    }
  });

Also just FYI, the SDK will try to get a new JWT for you and retry the original failed request automatically if you get a 401 response, as documented here, but it sounds like you're getting a 400 for a bad JWT?

Thanks for this, closing the issue


Add Proxy Capability

Opening pull to add capability to proxy based on the HTTP_PROXY environment variable using the superagent-proxy module.

need to do some additional follow up


(WIP) Modify unary & ternary function fields in number protocol

This revision modify unary & ternary functions in number protocol.
At the beginning, this PR starts for fixing power, inplace_power as ternary operation.
Unary operation modifying may be discarded at the last.

If you'd like to split pow bugfixes as a separated PR, I will merge it before this PR is done.

Sorry for delaying. It seems no more unary ops to fix left. After fixing several issues (what I commented as todo) and unittests tomorrow, I'll make this PR ready 😊

@youknowone rebase done!

Thanks a lot!


Added support for user home variable in settings

eg "cursorless.private.hatShapesDir": "C:\\Users\\Andreas\\repositories\\pokey-dotfiles\\cursorless-hat-shapes",
Checklist

[/] I have added tests
[/] I have updated the docs and cheatsheet
[/] I have not broken the cheatsheet

@pokey poke!


What is the added value of the Fluent API generator to e.g. Immutable

Could you please give us a summary of use cases when the usage of the Fluent API generator is better than a value object builder? For example Google's Immutable

Ok, i will update the README and add a section about when to use generic builders and when to use this library.


Add ESLint shareable config, remove JShint

Part of https://github.com/AnalyticalGraphicsInc/cesium/pull/5431.

Add .eslintrc.json files in place of .jshintrc's
Update the package.json as appropriate
Add eslint hints where necessary to make sure npm run eslint passes.
Remove .idea/jsLinters/jshint.xml

This is part of an effort to move to shareable configs: https://www.npmjs.com/package/eslint-config-cesium

@mramato How does this look? I'll apply the same "treatment" to the other repos if this looks OK.

Coverage remained the same at 93.842% when pulling 3c9e74c483d5149321d6dfdb81c3a6ecd182f9d1 on omh1280:eslint_node into 109946e5d694f9af1e4f8f7fc3d370f7668eac0c on AnalyticalGraphicsInc:master.

Bump

Coverage decreased (-0.002%) to 93.841% when pulling 30d340f9d3c9b7d222f59431bd1e11a5f078c952 on omh1280:eslint_node into 109946e5d694f9af1e4f8f7fc3d370f7668eac0c on AnalyticalGraphicsInc:master.

Coverage decreased (-0.002%) to 93.841% when pulling 30d340f9d3c9b7d222f59431bd1e11a5f078c952 on omh1280:eslint_node into 109946e5d694f9af1e4f8f7fc3d370f7668eac0c on AnalyticalGraphicsInc:master.

Bump!

Just those comments and then I'll merge.  Thanks @omh1280!

Thanks! Bump

Coverage decreased (-0.002%) to 93.841% when pulling 075990a10ac4436cef029979d21b4cfae1cb29fd on omh1280:eslint_node into 109946e5d694f9af1e4f8f7fc3d370f7668eac0c on AnalyticalGraphicsInc:master.

Coverage decreased (-0.002%) to 93.841% when pulling 220bcc9df4c4a8f76939636a936b89dac4c2866d on omh1280:eslint_node into 109946e5d694f9af1e4f8f7fc3d370f7668eac0c on AnalyticalGraphicsInc:master.

thanks. Bump!

Coverage decreased (-0.002%) to 93.841% when pulling 220bcc9df4c4a8f76939636a936b89dac4c2866d on omh1280:eslint_node into 109946e5d694f9af1e4f8f7fc3d370f7668eac0c on AnalyticalGraphicsInc:master.

Thanks.


Use standard adjusters from all-in-one

Fixed https://github.com/uber/jaeger-ui/issues/8

Coverage decreased (-0.0006%) to 99.073% when pulling 32772828d00a7655719f1c74c57ffcc9cb98d1ad on use-std-adjusters into f649007928740affbe2dd7916ff34868d7681818 on master.


Blog Post Publish Date Incorrect

https://ardalis.com/netcharge-notes-one-year-later
29 Jan 2007
https://beta.ardalis.com/netcharge-notes-one-year-later/
24 May 2020
This is just one example of many. Please check out this happened in the migration and correct. Thanks!

I found few and corrected them, if you have identified anymore please let me know.

Thanks. Do you know why they were incorrect?

Netlify CMS sets the current date and time for published date, that we can change as per our requirement I might have skip few of them.

Ok, cool. So if I found all the ones that had dates set in the last month,
I should be good.
On Fri, May 29, 2020 at 5:12 PM emmadigital<EMAIL_ADDRESS>wrote:

Netlify CMS sets the current date and time for published date, that we can
change as per our requirement I might have skip few of them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ardalis/ardalis-com-gatsby/issues/1288#issuecomment-636194313,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF66L4EL4B3A4633TB3J33RUAQLVANCNFSM4NNFSBMA
.

--
Steve Smith
http://ardalis.com | http://twitter.com/ardalis


Combine subpackages documentation step silently failing

Push to repositories step is failing because Combine subpackage documentation silently fails as you can see in the img above & failed run/log here.
By the time we reach the last step Push to repositories, we should have this folder structure:
build_dir/
├─ optimum/
│  ├─ main OR v.1.2.3/ # folder that contains built doc artifacts
│  ├─ _versions.yml

but we have this (without the doc built artifacts folder):
build_dir/
├─ optimum/
│  ├─ _versions.yml

because Combine subpackage documentation is failing
probably introduced in https://github.com/huggingface/optimum/pull/335
cc: @regisss @lewtun

Thanks for the investigation @mishig25!
After exploring a bit more, it happens that Make Optimum doc silently fails even before combining all docs. This occurs because there is no default clone URL, my mistake.
It's easy to fix, I'm going to do it tomorrow.

@regisss sounds great! Could we also make the errors non-silent?

totally, lets handle it in separate PR 👍


Set custom gas for active web3 used (ie: useWeb3Contract())

Is there a way to set user defined gas (for example to provide the user with slow, average, fast) gas options? If so, what would be the best way to do so!
Hope I am not missing something on my end that should be straightforward.

As an add-on to this, is there a good way to access the underlying web3 provider with this boilerplate to set gas or other parameters {from:0x, value:123, gas: 123}

Hi @ss5nathan ! You can't set it if you use useWeb3ExecuteFunction() now. You can get a wev3 provider from Moralis:
import { useMoralis } from "react-moralis"

const { web3 } = useMoralis

Take a look at https://github.com/MoralisWeb3/react-moralis#web3

Ah, thank you! Exactly what I was looking for. Love the work your team is doing on this!

Happy BUIDLing


Sticky only if parent is of a minimum height

Sometimes the parent container is so small that making the header sticky just doesn't make sense. Would love an option to set a minimum parent height before sticky enables.

Ping @simonihmig

@knownasilya thanks for pinging, sorry I somehow missed that!
The parent height logic seems quite tailored to this specific use case. What about we make this more generic, like just having an enabled property? The user could then implement his own logic for when to enable or disable.
I guess you are asking for this component here, right? https://github.com/ember-learn/ember-api-docs/pull/336/files#diff-34fdee68b53d5293a6d632b6a8d79636
I guess it could easily measure its own height, and implement something like stickyEnabled: gt('ownHeight', 100) to pipe that into the sticky element's enabled property.
Does that make sense?

Perfect 👍


Adding parameter optional to show typing status

#275

Any updates on this? There needs to be a FuncSubscribePresence as well, because chat.markComposing only works when the remote contact is online (and we don't know their presence by default).


Code cleanup following recent PR about driver errors and delta connection

Some of this stuff came up in #8964 so I'm putting a quick PR out to address it.

Reduce duplicated typing info across driver error types, and add doc comments
Remove TODO comment saying we should remove a valid check of this._readonlyPermissions (at least it looks valid to me)
Remove 2-year-old back-compat code around nack messages with no content.  See #1814.  I checked MS internal telemetry for good measure and didn't see any of these errors.
nackHandler - Avoid unnecessary call to reconnectOnError when we just closed the container.
BONUS:  A bug fix where asserts fired under reconnectOnError would be unhandled rejections and we would never reconnect.

can we split this up. it hard to review all these disparate changes. at a minimum we should split refactoring and functional changes.

@anthony-murphy I get that as a principal, but really?  This isn't a huge PR, just trying to clean some things up and move on.  If there's a particular part of the change you'd like to see/discuss separately, lmk, but otherwise it doesn't feel worth the friction.

I looked again at this in light of the ask to split into behavior changes v. refactoring.  Each change is unrelated to the others and they are all explained in the PR comment here, so with that in mind I wouldn't think it would be that difficult to review.  But at the same time, it's not difficult for me to break into 2 PRs so I am willing to do that.

@anthony-murphy I get that as a principal, but really? This isn't a huge PR, just trying to clean some things up and move on. If there's a particular part of the change you'd like to see/discuss separately, lmk, but otherwise it doesn't feel worth the friction.

i don't have context on theses changes. i see contract breaks, interface changes, and functional changes. i review all those things differently, and for the functional and interface changes i will need to look deeper at each to understand usage, and the context of the change. I'm happy to not review here if there is another reviewer with more context. I was just trying to help things make progress by grabbing some PRs that needed reviewing.

I pulled out #9125 and #9121 to separate PRs


Enhancement: Account for block document references with default values when resolving schemas

Description
Adds a new resolver for schemas that resolved default values properties that have block document references. As well as accounts for properties that are type block that might have a default value.
Supersedes: https://github.com/PrefectHQ/prefect-ui-library/pull/1324

@desertaxle I'd like to get your approval on this as well. Just to verify this fixes your issue.


improve memory usage for archived or compressed files

Summary
This is a "meta issue" to link to specific issues around a chronic issue.
Current behavior
Currently, some files are entirely read into memory. When dealing with large files and/or many files then the process can use too much memory and possibly crash due to Out Of Memory errors (OOM).
Reading from a large amount of archived files was the original motivating use-case for this project, i.e. many "tars of logs" from related systems. It's too bad this use-case can cause OOMs.
Specifically, these circumstances read much or all of a file into a memory at one time (memory use is O(n))

.xz files must be entirely read into memory during Blockreader::read_block_FileSz
This requires storing all data up to the passed blockoffset value, so O(n) memory usage.

see #12

.xz files must be entirely read into memory during Blockreader::new
However, this does not store all of the data read, simply that it requires reading the entire file once which is slow.

.gz files must be entirely read into memory up to the requested offset. This may be a problem when a user passes a datetime filter --dt-after for a large file. The searching algorithm for plain text files is a binary search algorithm. That searching algorithm is used for the decompressed data. The search for the first datetime after that --dt-after value may require reading from disk at least half of the uncompressed file (if the first datetime in block 0 is before the passed --dt-after value). However, before that search among the decompressed data can occur, the all data prior to the requested file offset must be read (and is held in memory). This is due to how gzip compresses data as a stream. In other words, you cannot decompress a block of compressed data at an arbitrary offset without first decompressing all preceding blocks of compressed data in the "gzip data stream".
If a user does not pass --dt-after then gzip decompressed data is read from block offset 0 and then as further blocks are read, old blocks are dropped (so memory usage does not scale to the size of the file).

.tar file contained file must be entirely read into memory during the first call to BlockReader::read_block_FileTar
see #13
In other words, the file contained within the .tar file is entirely read into memory, e.g. the entire file syslog from logs.tar but not the entire file logs.tar

*.evtx files with "out of order" events must be entirely read into memory
relates to #86

Suggested behavior
Have some O(1) ceiling for memory usage for all cases.
Relates to #14

The current implementation
SyslineReader::find_sysline_at_datetime_filter binary search
The SyslogProcessor::find_sysline_between_datetime_filters calls SyslineReader::find_sysline_at_datetime_filter
which does a binary search over the entire file during the "find datetime" stage (Stage2FindDt). This stage occurs before any log messages
are printed to the console (during stage Stage3StreamSyslines).
The intention here is that when a user
passes a --dt-after value then the first qualifying value can be found quickly by skipping the reading and
processing of unnecessary data (any syslines before the --dt-after datetime). This was one of the
original insights that motivated writing a custom BlockReader and it's attendant classes; very large log
files read over slow communication links could be search very quickly for log messages between some narrow band of time.
underlying BlockReader and drops
The underlying BlockReader does not know which stage is currently in progress (as it should not; stages are only a concept to the SyslogProcessor). So the BlockReader does not know when it should drop any held blocks. Nor could the BlockReader decide to drop it's own blocks because the user of the BlockReader, the LineReader holds BlockP points to the Blocks held by the BlockReader. In other words, even if the BlockReader decided to be clever and drop some of the Blocks it is storing, there would still be pointers to those Blocks (an Arc<Vec<u8>>) held by the LineReader instance. And the BlockReader should not try to get into signaling the LineReader to drop those BlockP pointers (a BlockReader should know nothing about a LineReader).
Signaling the BlockReader to drop data is currently initiated by the driver function in bin.rs, exec_syslogprocessor.
The calls to SyslogProcessor::drop_data_try is done during the log printing stage Stage3StreamSyslines.
To review: during the binary search done early on during stage Stage2FindDt (again, only needed if the user passes --dt-after) there is one call to SyslineReader::find_sysline_at_datetime_filter. There are no attempts to tell the BlockReader to drop old data.
And during this stage, it is possible for an entire .xz file or an entire .gz file to be held in memory if, for example, the user passes --dt-after datetime value that is after all log messages in the decompressed log data.
Idea: BlockReader only holds N blocks at a time
So the next idea would be to modify the BlockReader so that it only ever holds some N amount of Blocks
Problem
But that's difficult because remember the controlling LineReader hold it's own copies of pointers to those Blocks as well (BlockP instances) so the underyling Vec<u8> wouldn't drop as there are outstanding pointers to it. Additionally, it would be a bad design to try to have the BlockReader callback to the LineReader (now the BlockReader needs to understand what a LineReader is and that get's too messy).
Idea: BlockReader proactively drops blocks when handling xz files
Another idea is to modify the BlockReader::read_block_FileXz such that it procatively drops blocks that are not needed. Function read_block_FileXz does a linear search, storing Blocks as they are decompressed, and only passes back one BlockP when it is done. So the BlockReader could quietly drop "old" Blocks of data as new Blocks are decompressed.
For example, given a call to read_block_FileXz(9) to read the tenth Block of data, that requires decompressing all prior Blocks of data (as xz can only perform a "stream" of compression/decompression). The function could be modified such that as Block two is read then Block one is dropped, and so on, up to the tenth Block (so nine prior decompressed Blocks would have been dropped).
Problem
But then the problem is another call from the overlying SyslineProcessor within binary search function find_sysline_at_datetime_filter may later call read_block_FileXz(5). If Blocks one through six were droped previously, then the entire file must read and decompressed again (reading the sixth Block requires reading the prior five Blocks). So the initial binary search with O(log(n)) time now has O(n*log(n)) time.


[bug] isDarkTheme from useThemeContext always returns false

🐛 Bug Report
In the default template for docusaurus, I am trying to use theme context to get isDarkTheme's value. It is always set to false, even when I change to dark theme and then reload.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
(Write your steps here:)

Use `const {isDarkTheme} = useThemeContext()
add console.log for isDarkTheme
turn on dark theme and reload

Expected behavior
Should provide true when dark theme is set
Actual Behavior
isDarkTheme is false even when dark them is on
Your Environment

Docusaurus version used:2.0.0-alpha.56
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Node version: v12.17.0
Operating system and version (desktop or mobile): Ubuntu 16.04

See #2646. It might be caused by the same issue.

@SamChou19815 Thanks a lot. This does fix the issue. Maybe it needs to be documented better.

docs has been updated here by @Drewbi : https://github.com/facebook/docusaurus/pull/2934
still think it would be cool if the code did actually warn the user in case of using the hook without a provider (could throw with a link to the docs)


Evaluate iOS 15 issue with launch images

Apparently the markup for launch images does not work anymore in iOS 15. Maybe the media queries need to be adjusted.
Tested with: iPhone 12 Pro, iOS 15.0.1 (19A348)

The issue persists in iOS 15.1.1 (19B81).
If there is no fix on either my side or Apple’s side until iOS 16, I will deprecate this tool as Apple apparently abandoned apple-touch-startup-image.

See also: https://developer.apple.com/forums/thread/698389


Pin cloud provider’s TLS certificates

We should pin GCE to the Google corporate CA, AWS to its CA, etc.

@Demi-Marie sorry for missing this issue! Sounds good but not sure how to implementit, should be done at the terraform level, right?

I would assume so.


why is 'show file history' removed from context menu?

already used to its presence, it's such a useful command, is it possible to bring it back? really miss it
('show file in remote' is in context menu, but I don't see it particular useful. why would you open github for source code while you have vscode which is a much more powerful tool?)
(understand I can ctrl + shift + G, H, but, still miss the context menu option)

It is off by default to try to reduce the amount of menu items GitLens' adds out of the box. But if you open the GitLens settings editor (GitLens: Open Settings from the command palette) and switch into Advanced mode at the top, you can configure the menu items with decent granularity.

Hope that helps.


Randomized Merkle tree leaves in tests

This PR was motivated by https://github.com/AleoHQ/snarkVM/issues/280, where a test was using technically invalid test values (as there were non-unique Merkle tree leaves), which initially led to some misleading results. While that specific test is going away when https://github.com/AleoHQ/snarkVM/pull/298 gets merged, there are still some tests that are using dummy values as inputs; with this PR, randomized values for Merkle tree leaves are used instead, improving the quality of the affected tests.
note: this PR was done against the upcoming testnet2 branch, in order to avoid any conflicts with it.

While working on this PR I noticed that there are many tests that are using a specific, seeded Rng (this PR changes one instance of XorShiftRng::seed_from_u64(1234567) to plain thread_rng); doing so results in the affected tests having the same input values with every run, which reduces the probability of detecting potential "problematic" values; I'll be happy to alter those if desirable, at least in tests which aren't checking for a very specific outcome.

I think this is a desirable change! For now, I would modestly switch from SeedableRng to a thread_rng. For things that are high-level abstractions (like PoSW), feel free to swap out for thread_rng everywhere.

Rebased and added more ThreadRng in posw as suggested.
This PR can wait until https://github.com/AleoHQ/snarkVM/pull/298 goes in.

Once this PR is rebased, it looks ready to go

Rebased.

LGTM, thanks for adding the tests! They will improve our reliability :)


Fix EVP_PKEY_get_size() doc and error handling

Attempting to use a provider that does not implement OSSL_PKEY_PARAM_MAX_SIZE
fails on CMS/PKCS7/SMIME signing with the -noattr option,
while not even an error queue entry is provided.
This PR fixes the documentation to point out

the interrelation of EVP_PKEY_get_size and OSSL_PKEY_PARAM_MAX_SIZE (an the same for two similar pairs of functions and parameters)
the fact that  providers need to implement OSSL_PKEY_PARAM_MAX_SIZE for supporting some (e.g, CMS) use cases.

It also fixes the error handling and reporting on failure of EVP_PKEY_get_size() and friends.

BTW, looks like providers that implement the gettable OSSL_PKEY_PARAM_MAX_SIZE keymgmt parameter
als need to implement OSSL_FUNC_SIGNATURE_SET_CTX_PARAMS and OSSL_FUNC_SIGNATURE_SETTABLE_CTX_PARAMS, at least with an empty list of 'known' parameters.
Is this due to a bug of the specific provider or of the underlying OpenSSL provider support?

Thanks for the swift approvals.

Quite possibly provider support assuming the function is implemented...

@paulidale I assume your comment was meant in response to my question:

BTW, looks like providers that implement the gettable OSSL_PKEY_PARAM_MAX_SIZE keymgmt parameter also need to implement OSSL_FUNC_SIGNATURE_SET_CTX_PARAMS and OSSL_FUNC_SIGNATURE_SETTABLE_CTX_PARAMS, at least with an empty list of 'known' parameters.
Is this due to a bug of the specific provider or of the underlying OpenSSL provider support?

@all, I'd find it weird that a provider implementing parameter getter functionality
also has to implement querying parameter setter functions.
According to https://www.openssl.org/docs/man3.0/man7/provider-signature.html the statement:
OSSL_FUNC_signature_set_ctx_params and OSSL_FUNC_signature_settable_ctx_params are optional, ...
Yet for instance
openssl cms -provider ... -sign -in ... -inkey ... -signer ... -out ... -noattr

fails if OSSL_FUNC_SIGNATURE_SET_CTX_PARAMS and OSSL_FUNC_SIGNATURE_SETTABLE_CTX_PARAMS are not implemented.
In such use cases, both the cms and pkcs7 libs attempt to set the digest parameter.
(Without the -noattr option, neither the setter query functions nor the getter for OSSL_PKEY_PARAM_MAX_SIZE are needed.)

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Oh, meanwhile backporting includes 3.2
Yet why no more 3.0 - I thought it has LTS?

Aargh... that removal of the 3.0 label was uintended. I've botched something.


DataRow doesn't work with Array

Description
I have a test method like in the example, which I fill via DataRow. In this method I should test if all elements from an array or a list are added to my list.
I get a strange result. Only the first test is executed and in the UI you can see only one test. It doesn't matter what kind of collection I use. They are all different parameters, so no duplicates.
Since I have the Enterprise version, I also have Live Unit Testing, where the same problem occurs.
Steps to reproduce
I work with a similar method. However, with this one I get the same bug:
        [TestMethod]
        [DataRow(new[] { 1, 2, 3, 4 })]
        [DataRow(new[] { 1, 2, 3, 4, 5, 6, 7, 8, 9 })]
        [DataRow(new[] { 1, 2, 3, 4, 5, 6, 7, 8, 9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 1, 2, 3, 4, 5, 6, 7, 8, 9 })]
        public void AddRangeTest(int[] addArray)
        {
            List<int> integers = new();

            integers.AddRange(addArray);

            Assert.AreEqual(addArray.Length, integers.Count);
        }

Expected behavior

I expect all my three arrays to be tested.

Actual behavior

As a result, only one test is displayed in the UI and only the first one is executed.

Environment

Windows 10 Build 19043.1237
Visual Studio 2019 Enterprise 16.11.3
MSTest.TestFramework Version: 2.2.7 | MSTest.TestAdapter Version: 2.2.7 | Microsoft.NET.Test.Sdk Version: 16.11.0
Other installed packages: Moq & Coverlet

Thank you for reporting this issue. It's caused by the changes on how we handle tests with data sources after version 2.2.3. Please update to version 2.2.6 and opt-out out of this behavior as described here.


ci: Updated JDK of pipeline for sonarcloud

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] Implemented tests for new features.
[x] I tested the features already implemented.
[x] Added usage examples in the readme.

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


🧵 Project structure

Hierarchy
Boilerplate

predefined package json with necessary packages
(optional) Example content
(optional) entrypoint for js code (with typescript)

Title
Package with configs, fonts dependencies, title pages
Converter
Is a core package that converts markdown to latex.
Manager
Initializes project (available from npx), provides a toolchain for code-generating (converted, title package) and building latex

[ ] Move into docs


new architecture image

resolves #824

@mobinni do you think it would be helpful to elaborate a little more on the nature of backend.ts? Maybe just mentioning that it runs inside the angular application context, and that it also builds the router tree (or maybe just that it does 'things like this').

@stevenkampen good idea! Done :)

@mobinni awesome. Can you resize that shape so it doesn't cut the text off?

Fixed! :D

@mobinni Great. :shipit: :)


Retention Period?

If there is Retention Period do exist in SR History, please mention it somewhere in the document please.
If not, please mention in the document that SR History won't be deleted by time.

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

ID: a977f678-4268-cb72-3c94-7fc6ac25cec0
Version Independent ID: 362294c0-d91c-3c73-e879-805d6d75dc1f
Content: Azure Role-Based Access Control (RBAC) to control access rights to create and manage support requests
Content Source: articles/azure-supportability/create-manage-support-requests-using-access-control.md
Service: microsoft-docs
GitHub Login: @ganganarayanan
Microsoft Alias: gangan

Thanks for the feedback! We are currently investigating and will update you shortly.

@ganganarayanan can you take a look at this one?

@MicahMcKittrick-MSFT I had a question for you regarding deleting this article as RBAC for support is now a built in role and this might not make sense anymore.

@ganganarayanan
I send you E-mail, please check.

#please-close


Add all players to game upon joining

When a new client joins, they do not see the preexisting players.

New clients now load preexisting players.  For now it, uses the 'names' variable from the room, because 'game.players' doesn't populate with anything at the moment.  This can be changed later when desired.


Avoid unhandled error when used with aliases

Grunt doesn't provide an easy way to access the list of tasks associated with an alias.  Instead of an unhandled error, the task should fail.
See #59.

hi
Same issue here. Is there a way to launch the two tasks within a watch ?
    watch: {
      options : {
        interrupt: true
      },
      js: {
        files: [...],
        tasks: ['newer:jscs', 'newer:jshint']
      }
    }

Does not work for me
Thanks

It doesn't seems to be related to grunt-newer plugin, it looks like something to be looked up in grunt-contrib-watch docs.

Yeah just asking...
    watch: {
      options : {
        interrupt: true
      },
      jscs: {
        files: [...],
        tasks: ['newer:jscs']
      },
      jshint: {
        files: ['Same files'],
        tasks: ['newer:jshint']
      }
    }

Works but is a little bit verbose


Wrong border location

Can't reproduce this; but borders don't work properly in Ventura either way.

Similar issue when opening finder app


Cannot get bitmap with transparent background

Hi guys. First of all thanks for a great library. Its responsive brush is really cool. And its really easy to get the bitmap. However, I am having a problem when I get the bitmap with transparent background. Instead of getting transparent background, I am getting black background. Please help me in this.

are you just trying to render it to a view, or export it to a file type?

I am saving it as file in sd-card, then showing it in ImageView.

If you are writing to a file, and you can see the signature on top of a black background, then you are able to extract the bitmap on a transparent background. I would instead check that you are saving the image correctly, as a PNG with a transparent layer.

Closing, as issue not believed to be with library, but rather how image was being persisted to disk.


Unable to use RefreshAccesToken() to get a new access token after the current one expires

Trying to invoke the RefreshAccessToken() manually after the access token expires gives me the following error on the browser console

However attempting use the get a new token by sending the same refresh token via an API call (via Postman) to the Asgardeo Server is successful
Is this by design?

I encountered the same issue. Upon investigating the asgardeo-auth-spa-sdk, I noticed that beforerefreshAccessToken is called, there is a check for authentication at the following locations:
refreshAccessToken()
public async refreshAccessToken(): Promise<BasicUserInfo | undefined> {
    await this._validateMethod();

    return this._client?.refreshAccessToken();
}

_validateMethod()
if (validateAuthentication && !(await this.isAuthenticated())) {
    return Promise.reject(
        new AsgardeoAuthException(
            "SPA-AUTH_CLIENT-VM-IV02",
            "The user is not authenticated.",
            "The user must be authenticated first."
        )
    );
}

I believe it would be beneficial to have an option to bypass this check when attempting to refresh an expired access token.

+1 same issue here
What is the point of check access token expired before excute refresh token ?

A workaround would be to downgrade the SDK version to 3.0.2

@nisuraaa downgrade an major version can lead to a lot of other issues too 😢

Hi @nisuraaa and @davidtranjs, I too believe that it doesn't make sense to have isAuthenticated check before refreshing the access token.
@brionmario thoughts?

+1 to remove the check.
With https://github.com/asgardeo/asgardeo-auth-js-core/pull/242, we are now checking the expiry time. Hence, it'll fail when the time is exceeded.

+1 to remove the check. With asgardeo/asgardeo-auth-js-core#242, we are now checking the expiry time. Hence, it'll fail when the time is exceeded.

Ack. will send a fix.


secrets.json file not found. and there is no directory in assets folder with name "data"

there is no folder with the name of data in assets directory, also secrets.json file is missing

Please pull/checkout again the branch master


Added if statement to check if instance is aws

After chatting with @redhatrises  - this issue was an oversight when copying over from the functionality from another script. There are 2 options that we can use to fix this:

The current fix simply ensures that we don't call the aws_ssm_parameter function unless it's an aws_instance.
Or..rather than use the aws_instance variable check, we can opt to use an environmental variable such as FALCON_AWS_SSM      (default: false), and then call the aws_ssm_parameter function when this env variable is true.

I'm open to suggestions.

I think option 1 could still have the same issue you saw this morning except now it only happens when you run on AWS instances.
Providing cid in the current script is optional since it just looks it up when not provided https://github.com/CrowdStrike/falcon-scripts/blob/042d38af15b699c17c925bc6ff3123f913936d58/bash/install/falcon-linux-install.sh#L34-L39
So if this script was ran on an aws instance (maybe as user-data) without FALCON_CID set and the IAM role doesn't have access to SSM or these secrets do not exist in the aws account the error will still print, and the run will still be successful.
Option 2 may be seen as a breaking change (assuming people are using this functionality) since we are taking current existing functionality and making it opt-in.
Maybe option 1 plus removing the error for when a cid is not provided since we are and have been defaulting to whatever the api returns. Printing a note out saying we are falling back to the api may be useful also. (throwing an error if the api returns no CID is appropriate)

@ffalor okay so tested this on an aws instance and the message I get is the following:
++ response='{"__type":"UnrecognizedClientException","message":"The security token included in the request is invalid."}'
++ grep -q '^.*"InvalidParameters":\[\].*$'
++ echo '{"__type":"UnrecognizedClientException","message":"The security token included in the request is invalid."}'
++ die 'Unexpected response from AWS SSM Parameter Store: {"__type":"UnrecognizedClientException","message":"The security token included in the request is invalid."}'
++ echo 'Fatal error: Unexpected response from AWS SSM Parameter Store: {"__type":"UnrecognizedClientException","message":"The security token included in the request is invalid."}'
Fatal error: Unexpected response from AWS SSM Parameter Store: {"__type":"UnrecognizedClientException","message":"The security token included in the request is invalid."}```

Which means you are probably right that this could fail with improper IAM permissions and such.. need to investigate more


churn-ed peerconnections break when RtcToNet closes data channels

Steps to reproduce:

start Simple SOCKS, with churn enabled
run this command a few times: curl -x socks5h://localhost:9999 http://www.armoryonpark.org/css/screen.css

You will see messages to the effect of:
curl: (18) transfer closed with 20272 bytes remaining to read

And after running this several times the proxy will fail to respond to any more requests.
This kinda looks like this issue, except here the proxy basically dies after a few such requests:
https://github.com/uProxy/uproxy/issues/1033

OK, I was able to come up with a workaround: RtcToNet should never close channels on churn-ed peerconnections.
It seems that if RtcToNet closes a channel then messages will be dropped on the SocksToRtc side. Additionally, the connection is somehow broken: chrome://webrtc-internals tells me that for each createLocalDataChannel event there is no corresponding onRemoteDataChannel event.
That is...worrying. @iislucas and @mollyling maybe we can brainstorm why this might be happening?
BTW, this does seem to be limited to RtcToNet closures; I get the bad behaviour if I hack it the other way around, i.e. only RtcToNet closes channels.

Hmm. I've been running (non-churning) Simple SOCKS for several days on my machine and ~5 minutes ago the RtcToNet side of the peerconnection also stopped receiving createLocalDataChannel events. We might have a bigger issue here that churn is simply making more obvious.

Huh. Do the logs show how high the stream IDs went? Could we have exhausted
all 1023?
Cheers,
$ ls
On Mar 18, 2015 1:23 PM, "trevj"<EMAIL_ADDRESS>wrote:

Hmm. I've been running (non-churning) Simple SOCKS for several days on my
machine and ~5 minutes ago the RtcToNet side of the peerconnection also
stopped receiving createLocalDataChannel events. We might have a bigger
issue here that churn is simply making more obvious.
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1113#issuecomment-83067415.

Huh, are there timing issues exacerbated by churn?  The events are
transmitted by OPEN messages on the same SID, with control-typed messages.
There could be an interaction with the stream reset that happens when we
close a stream.
Cheers,
$ ls
On Mar 18, 2015 1:13 PM, "trevj"<EMAIL_ADDRESS>wrote:

OK, I was able to come up with a workaround: RtcToNet should never close
channels on churn-ed peerconnections.
It seems that if RtcToNet closes a channel then messages will be dropped
on the SocksToRtc side. Additionally, the connection is somehow broken:
chrome://webrtc-internals tells me that for each createLocalDataChannel
event there is no corresponding onRemoteDataChannel event.
That is...worrying. @iislucas https://github.com/iislucas and @mollyling
https://github.com/mollyling maybe we can brainstorm why this might be
happening?
BTW, this does seem to be limited to RtcToNet closures; I get the bad
behaviour if I hack it the other way around, i.e. only RtcToNet closes
channels.
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1113#issuecomment-83063161.

I suspect timing issues.
@bemasc suggested packet loss might be exaggerated by churn, too, which is conceivable. I haven't tested that yet.
Any idea how we'd test stream resets?

They're triggered by closes. You can trap them easily in
SctpDataMediaChannel, like the OPENs.  What's nasty about them is that you
can only have one outstanding at a time, so any other closes get queued.
If it takes a while, you can have a bunch of SIDs locked up in the
process.  1024 is way too high, but who knows?
More likely some latent bug of mine...
Cheers,
$ ls
On Mar 18, 2015 3:34 PM, "trevj"<EMAIL_ADDRESS>wrote:

I suspect timing issues.
@bemasc https://github.com/bemasc suggested packet loss might be
exaggerated by churn, too, which is conceivable. I haven't tested that yet.
Any idea how we'd test stream resets?
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1113#issuecomment-83133146.

So, I don't detect any packet loss with churn. @mollyling do you think changing the order of packets might somehow cause something like this? BTW, when this occurs I've only created 1 or 2 datachannels, nowhere near 1024.

Again, dead simple way to reproduce this:
curl -x socks5h://localhost:9999 http://www.armoryonpark.org/css/screen.css

Then try to curl any URL...it won't work.
Hack RtcToNet to not close data channels seems to fix it most of the time. However, I have seen the peerconnection still break when under very heavy load so I think we need to understand what's happening here.

I put in some print statements.  Working off of trevj-turn, I get 'onclose' events for each data channel close when using simple-socks-chromeapp with chrome as a socks client.  I'll try to simulate the remote-close case to verify that the onclose events happen there too.

I only see this issue with certain webservers, e.g. www.armoryonpark.org. They close the TCP connection before the SOCKS client. What happens when you try to fetch a URL from that server, specifically?

Discussed with @mollyling we'll add a small integration test for this (using our own local server).

Lots of discussion on this earlier today. Thanks to a mammoth debugging effort by @mollyling and @bemasc it turns out there's is a fundamental problem with how datachannel closures are implemented in WebRTC. In short, close events are signalled outside of the same reliable, ordered stream as open and data events.
This really isn't anything to do with churn: it's probably exacerbated by how churn seems to cause packets to be batched (probably not packet re-ordering). This almost certainly explains much of the occasional peerconnection breakages we've observed over time, too.
Proposal for now is to add some sort of application-level channel sentinel, e.g. a string message of "close" to indicate that the SOCKS session should be discarded, while we either fix the implementation or the standard.
I really wish we didn't need the application-level fix but it seems unavoidable; let's strive to make it backwards compatible and that at some point in the future, when this issue is fixed in WebRTC, we can silently remove it.

@mollyling and @bemasc, would one of you mind adding a short description of the actual solution we took?

The (attempted) fix in https://github.com/uProxy/uproxy-lib/pull/153 works by delaying any calls to rtcDataChannel.close() until after dataChannel.bufferedAmount == 0.  This requires polling rtcDataChannel.bufferedAmount, which we do every 20ms if dataChannel.close() has been called (once the javascript buffer is empty, which is driven by its own 20ms polling loop).


"extraneous input '' Error Occurred While running the ballerina http services on Windows environment

Description:

While running the ballerina http services on Windows environment, it is unable to find the exact path for certification key files. Please refer the following error message.
"extraneous input '' expecting {'0', '"', '\', '/', '\b', '\f', '\n', '\r', '\t', ALPHA, ' ', '-', '.', '"', '_', ':', ',', '/', ''', '=', '#', '[', ']', '{', '}', DIGIT19, BASICUNESCAPED, '+', '0x', '0o', '0b', 'e', 'inf', 'nan', 'true', 'false', 'T', 't', 'Z'}"
Steps to reproduce:

Run the ballerina http service on Windows environment or run ballerina integration test suite(http services).

Affected Versions:
Ballerina 0.982.0
OS, DB, other environment details and versions:
Windows
Related Issues (optional):

Suggested Labels (optional):
Ballerina Integration Tests

Suggested Assignees (optional):
Pubudu Fernando

Had a look at this with @KasunAratthanage. The issue here is with the TOML parser which doesn't seem to be able to handle the \ character. Will have a look at this.

The fix given in PR #11181 is now merged to master. Hence closing this issue.


Email validated field does not allow typing (when using dynamic component)

Versions:

VueJs: 2.4.2
Vee-Validate: 2.0.0-rc.7

Description:
I am trying to create a system where I can define form fields declaratively, and template them using a generic component. I see great potential in easy form construction by taking this path.
For instance
data () {
    return {
        object: {},
        form: {
            email: {
                name: "email",
                component: "InputField",
                label: "E-mail",
                type: "email",
                validation: "required|email",
            },

            password: {
                name: "password",
                component: "InputField",
                type: "password",
                validation: "required",
            },

            remember: {
                name: "remember",
                component: "CheckboxField",
                label: "Remember Me",
            },
        },
    }
}

And
<form-field :field="form.email"
            v-model="object.email">
</form-field>

<form-field :field="form.password"
            v-model="object.password">
</form-field>

<form-field :field="form.remember"
            v-model="object.remember">
</form-field>

The problem: I am puzzled that the "email" validator prevents me from typing in the field.
Steps To Reproduce:
See my fiddle - https://jsfiddle.net/c4marcus/zu2ugwbz/3/
Notice in FormField that the dynamic component defines v-bind="field", this is how I pass the declarative field structure as props to the actual field component.
Additionally, I am making use of data-vv-* attributes too. Am I using this feature correctly? This issue is tangential to a previous issue I had opened.

It is because of :value="value" by binding the input value to the value prop, you are causing the component to stay locked to that value, This happens with vee-validate because it causes the component to re-render which then resets the value to the original bound one.
Generally it is recommended to use v-model instead of binding to the value and responding to the changes, since it already does all of that for you, but since you have a dynamic type property it wouldn't work.
I've employed the use of refs to fix your issue:
https://jsfiddle.net/logaretm/zu2ugwbz/7/

You did it! Thank you!!
I looked up Port Said. Beautiful place. Cheers to you

Same issue here - manifests itself with weird form-fields being cleared when typing into other fields which cause validation. I guess it's vuex in my case, which I am using with v-model (I have read the linked issues, the point about not using vuex is not relevant here, sadly.
What I'm not getting is what all the ref thing is doing, and precisely which bit of markup is causing the issue. It doesn't matter if it works, of course.
Hacking the fiddle there, I replaced my v-model of a vuex get/set field with a combination of :value to get the initial value from store, then @input to capture changes... and that seems to work. Thanks for the work-around.

@philwig The ref just allows us to set the input value initially without triggering a model change that could cause an unintended validation.
I'm actively looking for a way to prevent this issue from happening tho.

;-) I thought I had this nailed, with your example. It prevents a single field being cleared out, no problem... but if I copy the precise markup, but use a different store value in the cloned HTML, then the second "fix" doesn't work at all, I still get clearing of the field on blur.
It works ok if there was is an initial value in the field, which is why I thought I'd worked around this, but if the field is empty... the blue event is apparently writing that empty value back over the field. I guess I can look in the code and see if I can stop it doing that, but any advice on that would be welcome.
Why would a single field be fixable, but if I have two, why would one of them fail? Changing the other doesn't change which one gets cleared - it's very weird.

It appears this was in fact my problem, not vee-validate. I was failing to explicitly initialize some fields on the "store". That somehow interacts badly with vee-validate, and although the "ref" trick helped me fix one field, other fields were still being cleared on blur (if I had not explicitly initialized them, I now know).
Solution: explicitly initialize default values on Vuex store and it's all good.


Encountered an issue while looking up entity!"

Got this in new staging update <IP_ADDRESS>

Thanks for the report - consolodating this to #122

As posted in #122 - this should now be fixed on the staging branch :)


Install eventlet as well

One can switch to it by setting POOL=eventlet env. var.
Related to #2120

how did you realize this was the fix?

I didn't :-) It's just another concurrency library to try to see if the problem is in the one (or just the version) we're currently using.

Tried on stage and from https://red-hat-it.sentry.io/issues/4325660438 it seems the eventlet doesn't get along well with sqlalchemy.


No Choice for Arduino MKR Wifi 1010

Sketch creator should present the choice of Arduino MKR Wifi 1010

still no choice for MKR WIFI 1010!
please help


Check information needed task

Context
Trello ticket
Changes in this PR
Adds the above task. Note that in the absence of guidance on what happens if the user selects 'No', for now this is a normal application task that will still render on the task list as 'complete' in that case.
Screenshots of UI changes

Release checklist
As part of our continuous deployment strategy we must ensure that this work is
ready to be released at any point. Before merging to main we must first
confirm:
Pre merge checklist

[ ] Are any changes required to the e2e tests?
[ ] If you've added a new route, have you added a new
auditEvent? (see server/routes/apply.ts for examples)
[ ] Are there environment variables or other infrastructure configuration which needs to be included in this release?
[ ] Are there any data migrations required. Automatic or manual?
[ ] Does this rely on changes being deployed to the CAS API?

Post merge checklist
Once we've merged it will be auto-deployed to the dev environment.
Find the build-and-deploy job in CircleCI.
Should a release fail at any step, you as the author should now lead the work to
fix it as soon as possible.

 Check information (guidance page)


Handling of Left-to-Right Mark (U+200E) in URLs

Summary
We are evaluating the Granian WSGI server for use with our Django application. During this testing phase, we have encountered an issue with how Granian handles certain characters, specifically the Left-to-Right Mark (U+200E), when present in URLs.
Steps to Reproduce

Run a Django application using the built-in development server: python manage.py runserver
Make a request to a URL containing the Left-to-Right Mark (U+200E) character, e.g., curl http://localhost:8000/%E2%80%8E

With the built-in Django development server, the request is processed correctly, and the expected response is returned.
However, when running the same Django application with Granian as the WSGI server:

Start the Granian server: granian wsgi.app:application --interface wsgi
Make the same request to the URL containing the Left-to-Right Mark (U+200E) character: curl http://localhost:8000/%E2%80%8E

In this case, Granian triggers an error, failing to process the request correctly.
Expected Behavior
The expected behavior is for Granian to handle URLs containing the Left-to-Right Mark (U+200E) character in the same way as Django's built-in development server and other WSGI servers like Gunicorn and uWSGI.
Additional Context

Other WSGI servers like Gunicorn and uWSGI handle URLs containing the Left-to-Right Mark (U+200E) character correctly when used with the same Django application.
This issue has been observed with the latest version of Granian (v1.4.2) at the time of this report.

This appears to be a difference in the type of string passed down to Django. There is a code comment above this line:
    # Non-ASCII values in the WSGI environ are arbitrarily decoded with
    # ISO-8859-1. This is wrong for Django websites where UTF-8 is the default.
    # Re-encode to recover the original bytestring.

https://github.com/django/django/blob/e2428292abaca4758a7508175d31667fe2dff57c/django/core/handlers/wsgi.py#L197
Traceback
[ERROR] Application callable raised an exception
Traceback (most recent call last):
  File "/Users/rob/.pyenv/versions/3.11.8/envs/bedrock/lib/python3.11/site-packages/granian/wsgi.py", line 40, in _runner
    rv = callback(scope, resp)
         ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rob/git/bedrock/wsgi/app.py", line 15, in https_application
    return django_application(environ, start_response)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rob/.pyenv/versions/3.11.8/envs/bedrock/lib/python3.11/site-packages/django/core/handlers/wsgi.py", line 123, in __call__
    request = self.request_class(environ)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rob/.pyenv/versions/3.11.8/envs/bedrock/lib/python3.11/site-packages/django/core/handlers/wsgi.py", line 61, in __init__
    path_info = get_path_info(environ) or "/"
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rob/.pyenv/versions/3.11.8/envs/bedrock/lib/python3.11/site-packages/django/core/handlers/wsgi.py", line 149, in get_path_info
    path_info = get_bytes_from_wsgi(environ, "PATH_INFO", "/")
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rob/.pyenv/versions/3.11.8/envs/bedrock/lib/python3.11/site-packages/django/core/handlers/wsgi.py", line 197, in get_bytes_from_wsgi
    return value.encode("iso-8859-1")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeEncodeError: 'latin-1' codec can't encode character '\u200e' in position 9: ordinal not in range(256)

@robhudson this is confirmed, gonna work on a fix and release it in 1.4.3

Thanks very much for this @gi0baro - we really appreciate it (I'm a coworker of Rob's).

I saw the 1.4.3 release show up. Verified locally that it fixes it. Thanks so much for the quick iteration!


The target should be an array but the generated Csharp file is not

Brief Description

The target should be an array but the generated Csharp file is not
How can I solve this problem?
OS: Windows 7
Target: MSVC

We have no way of knowing if this is a pointer or an array, so we generate the pointer by default.
In this case you can manually extend your binding with an helper method that takes the arrays and forwards to the generated one.
It would also be possible to extend CppSharp itself so you could flag in the AST that this particular parameter represents an array with a given size, but that would be more involved. If you're interested in contributing that feature, we'd be happy to guide you on how to do it.


Can't configure AssumeRoleProvider to use the FIPS endpoints

There's an issue in aws-config where the AWS_USE_FIPS_ENDPOINT environment variable isn't respected for the AssumeRoleProvider, and the ConfigLoader::use_fips value doesn't flow into the AssumeRoleProvider.
Discussed in https://github.com/awslabs/aws-sdk-rust/discussions/880

Originally posted by jszwedko August 25, 2023
This came up through an issue report on Vector about it not using the FIPS endpoints when AWS_USE_FIPS_ENDPOINT=true.

@jdisanti does this need to be raised in smithy-rs instead?

We try to track SDK issues in this repo, although sometimes they end up in smithy-rs.


ci: add snyk for security scanning

adding snyk GitHub action to run when a PR is merged to the branch, This will help us to track the security scanning results and fix if anything is required and also it serves as a placeholder for security scanning results for a while.

nit: please fix the typo in the tool's name in commit header and description.

Instead of doing this on every merge, maybe do it with a daily/weekly cron schedule?

Instead of doing this on every merge, maybe do it with a daily/weekly cron schedule?

@nixpanic I didn't find any easy configuration that allows us to run CI jobs on all the branches (maintained). i thought this would be the best one for now, i would like not to have hardcoded release branch names and add new branches when we make a new release. Let me know WDYT?

You can schedule a workflow to run at specific UTC times using POSIX cron syntax. Scheduled workflows run on the latest commit on the default or base branch

From the doc

Ah, ok. In that case, maybe combine the two?

run on a daily/weekly schedule for the devel branch
run after each merged PR for release-* branches

Can you put them in a singe yaml?
on:
    schedule:
        ...
    push:
        ...