Orb attempts to install TailScale even if it's already installed

Currently, this orb attempts to install TailScale even if it's already installed. For example in our CI/CD pipelines we use a custom alpine container for deployments that already has all the tools we need for a deployment installed, including TailScale.
It would be good if the orb detected if tailscale was already installed and skipped the install process if it was.

Good point, thanks! Approved


Add support for scheduling campaigns by timezone

The following fields need to be added here:

is_adding_recipients_at_send_time
send_strategy
delivery_time
send_date
timezone
throttling_count
sto_send_times
sto_explanation_string
sto_label_sto_sending_strategy
sto_move_condition
rltz_send_past_timezones_tomorrow
sto_is_reschedule_at_send_time

Hey, thanks reaching out and raising this issue. I'll connect with our product team to see if we can get this added to our roadmap. Please do reach out if you have any other feedback for our team, we truly appreciate it.


geometry_experimental has been renamed to geometry2

This changes all urls referring to the old repos to point to the new ones. It's just a url change and I changed the older distros for clarity. (Note github redirects everything successfully at the moment.)
Because of changing the older distros it will fail the checks for changes to old distros, but since there are no changes to the content it's fine to override that check. It's not nuanced enough to catch this case.

@ros/rosdistro-maintainers can someone else review since this requires an override of the CI.

Travis failed due to change to the metadata for Hydro:
Traceback (most recent call last):

  File "/home/travis/build/ros/rosdistro/test/test_url_validity.py", line 258, in test_function

    self.assertFalse(detected_errors)

AssertionError: [u"In file '''/home/travis/build/ros/rosdistro/hydro/distribution.yaml''': There is a change to a release section of an EOLed distribution. Lines: [2260, 2261, 2262, 2263, 2264, 2265, 2266]", u"In file '''/home/travis/build/ros/rosdistro/hydro/distribution.yaml''': There is a change to a doc section of an EOLed distribution. Lines: [2256, 2257, 2258, 2259]", u"In file '''/home/travis/build/ros/rosdistro/hydro/distribution.yaml''': There is a change to a release section of an EOLed distribution. Lines: [2248]", u"In file '''/home/travis/build/ros/rosdistro/hydro/distribution.yaml''': There is a change to a doc section of an EOLed distribution. Lines: [2233]", u"In file '''/home/travis/build/ros/rosdistro/groovy/distribution.yaml''': There is a change to a release section of an EOLed distribution. Lines: [1392, 1393, 1394, 1395, 1396, 1397, 1398]", u"In file '''/home/travis/build/ros/rosdistro/groovy/distribution.yaml''': There is a change to a release section of an EOLed distribution. Lines: [1388]", u"In file '''/home/travis/build/ros/rosdistro/groovy/distribution.yaml''': There is a change to a doc section of an EOLed distribution. Lines: [1375]"] is not false

I'm not the authority here so I'm not sure why changing an EOL'd distro causes this assertion to fail.

@jacquelinekay  We don't allow people to make releases into EOL'd distros since the packages are no longer building, so the distribution file represents the state of the repo as a snapshot. This is not a release but fixing the urls for the moved repo. The script is not specific enough to detect that it's a rename to match an external resource movement and not a new release.

So, do we need to fix the script?

No, we just need to manually review it and merge it with the CI complaining that we are changing an old section. This script is analyzing the diff to master and once it's merged there won't be a diff in the older files and it will pass future diffs.

LGTM


UInt64 duplicates functionality in guava

https://github.com/PegaSysEng/artemis/blob/master/util/src/main/java/tech/pegasys/artemis/util/uint/UInt64.java
https://github.com/google/guava/blob/master/guava/src/com/google/common/primitives/UnsignedLong.java

Yep. Totally correct. We were discussing the same thing. Thanks for the feedback

While implementing our own 64-bit unsigned int was an interesting exercise, given that we are already using Guava for our events, I see no reason to not use the Guava implementation.

Never quite understood why Guava used different method names from BigInteger (e.g. plus vs add, minus vs subtract). FWIW, https://github.com/ConsenSys/cava/blob/master/units/src/main/java/net/consensys/cava/units/bigints/UInt256.java uses the BigInteger naming. But I'd agree that keeping it simple and reusing existing things is the best place to start!


Scaleup/down limitations

Doesn't seem the limitations reported from dile_vt are the actual scale down limits. Once I run, i have no problem running at 192x108 (when tv reports scale down is 320x240, which is also weird cause that's not a widescreen resolution)

You mean - that resolution works for you when you comment out/remove these overwrites?
https://github.com/webosbrew/hyperion-webos/blob/dile_vt_getallvfb/src/backends/libdile_vt.c#L112-L113

yeah, i can scale down below that without any issue when i comment out those overwrites
"board_type": "O18_ATSC",
"hardware_id": "HE_DTV_W19O_AFABATAA",
"product_id": "OLED65C9PUA",
"core_os_release": "4.9.1-53409",
"webos_manufacturing_version": "05.00.30",


Include Karpenter-provisioned nodes into consideration

Addresses #3 : Karpenter Support
Karpenter does not provision nodes as part of a node group/pool.  However, they are still useful to see when listing groups or pools of nodes.  This development allows for nodes that have been provisioned by karpenter to be identified by the plugin.
# list
❯ kubectl nodepools list
NAME                    NODES   TYPE
(Karpenter) default         2   c6a.2xlarge
main-m52xl-2                4   m5.2xlarge

# label search
❯ kubectl nodepools nodes --label 'karpenter.sh/provisioner-name' default
NODE                                            STATUS
ip-10-62-71-26.us-east-2.compute.internal       Ready
ip-10-62-79-122.us-east-2.compute.internal      Ready

Note that multiple instance types can be present for a single karpenter provisioner, so output can look like this:
# list
❯ kubectl nodepools list
NAME                    NODES   TYPE
(Karpenter) default         2   c6a.2xlarge, m5.2xlarge
main-m52xl-2                4   m5.2xlarge

This has been achieved by restructuring how the nodepool struct is implemented, by having "Types" be a set rather than a single value.

Works great! Thank you!


Plotly.js 1.46 -> Plotly.py 3.8 -> PX 0.2

[x] hover_extra #6
[x] hovertemplate on box/violin/marginals
[x] barmode on bars
[x] barmode=stack on histograms
[x] fix ordering on 3.5-
[ ] px.strip() ?
[ ] px.sunburst()?

Hi, is sunburst still on the plan?

Yes, we will eventually support all Plotly trace types :)


Add user profile to the UI

Add Name and Email under user details for now

@Sarlin-7757

Replace icon with user icon in the side bar menu and link it to /profile


Create account along with key in one atomic request

This merge request removes the separate createAccountKeyRequest and embeds the account key into the createCredentialRequest.
This is done to prevent ending up with unusable accounts if the createAccountKey request fails.

This PR is waiting for the next server release.

@SimonBarendse Go ahead and merge it if you're also okay with it.

The PR I mentioned this thread implements the required update of the API server.

The change on the API server has been merged.

The API server with the required change has been released.


docs: update changelog in README.md

Closing since we will be storing this in the releases section.

Well, we could generate that out to a file what we commit to the repo.


Update Value.spec.lua

What's the motivation for this change?

This change does not seem meaningful. Returning to it now I do not see any reason why this should be at all functionally different, and since no explanation has been given, I have no choice but to reject this PR.

and since no explanation has been given, I have no choice but to reject this PR.

this was explained several times, but ignored on each. https://discord.com/channels/385151591524597761/895437663040077834/982713104574079037
https://discord.com/channels/385151591524597761/895437663040077834/980596243317272596
And a very simple look at the code would have shown it too. Passing a state directly into a Computed is not a valid way to use it. The test is clearly written to use a ForValues to test the garbage collection behaviour.

and since no explanation has been given, I have no choice but to reject this PR.

this was explained several times, but ignored on each. https://discord.com/channels/385151591524597761/895437663040077834/982713104574079037
https://discord.com/channels/385151591524597761/895437663040077834/980596243317272596
And a very simple look at the code would have shown it too. Passing a state directly into a Computed is not a valid way to use it. The test is clearly written to use a ForValues to test the garbage collection behaviour.

Right so this is why I would have preferred the explanation to be here rather than buried in Discord chat. It is impossible to keep track of a pull requests history like that; while I was going through old PRs last night there was no explanation attached here and I had no idea of your intention whatsoever. Don't trust me to remember, please put the information where I (and perhaps more importantly, others) can find it.
I will look at this again later when I'm done with work.

Apologies for the former lapse in judgement.


fix: guardduty setup and tests

Definition of done (v0.0.2)

[ ] Automated integration test
updates permissions for the SSM execution for setting up GuardDuty

will close in favor of #327. Tests are flaky. After the mentioned issue is merged, we will add more testing retries (stabilize the tests #275) and remove the magic sleeps.


Tooltip: Skip delay

Describe the bug
No more option for skip delay duration
<TooltipProvider> is gone, so there is no way to set skip delay duration anymore
This would be great to add back somehow

@onmax  I realized we don't have <TooltipProvider> for that component, however I believe we can just add skipDelayDuration to the <TooltipRoot>, and provide the value from there.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.9.276",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b4565a8a2d6bffb05bfbec11399d261ec16fe373"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "b4565a8a2d6bffb05bfbec11399d261ec16fe373",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "watchdog: sc520_wdt: Fix possible use-after-free in wdt_turnoff()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.276 by commit b4565a8a2d6bffb05bfbec11399d261ec16fe373. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001449


Npm miss LexicalAutoEmbedPlugin directory in components directory

I found that the code on NPM is missing the LexicalAutoEmbedPlugin directory. LexicalAutoEmbedPlugin exists in the directory I built locally

Would you like to open a PR?

This is exported in latest versions


Update Doppler provider to accept Project and Config params

Updates the Doppler provider to accept a Project and Config parameter. The previous usage remains unchanged (i.e., if you use a Service Token where the project and config can be inferred), but if you use any token type other than a Service Token without providing a project and config param, you'll get an error now.
const secrets = require("gitops-secrets");

async function main() {
  const payload = await secrets.providers.doppler.fetch({ dopplerProject: "example", dopplerConfig: "dev");
}

This will allow for Service Account tokens to be used.
Fixes #39.

The only concern is that we are identifying if a token is a service token or a service account token by parsing the contents. Can we use an API to identify token types? If no API exists, then token parsing is the only possible way.
PR looks good to me. Thanks, @watsonian

The only concern is that we are identifying if a token is a service token or a service account token by parsing the contents. Can we use an API to identify token types?

@ivorynoise The prefix on tokens is designed to be able to determine the type, so this is a pretty standard method of determining the type. We could make an API request to do that, but there's no real point in performing an extra request and the associated roundtrip to determine something we can get by inspecting the token directly. In any case, per @nmanoogian's suggestion, we're dropping that check entirely. The API will return an appropriate error if a required param is missing, so there's no need for special handling.


Hi there is some suggestions for you.

I'm happy to see a python obfuscate project updated by you, the gihub repo doesn't have much younger or maybe still upgrade projects, except Pyarmor. i think you should learn from them and you can do better.

Tell me what the bug is and I will try to help you.

it was working until i want to make it with itreations
failed
return back to the and failed
probably i need just to check out to the first commit lol

PS C:\Users\bdrkh\Documents\Python\EnigmaLang> & C:/Users/bdrkh/AppData/Local/Programs/Python/Python312/python.exe c:/Users/bdrkh/Documents/Python/EnigmaLang/test_code/helloworld_obfuscated.py 550c6f8511f688c051afa136e2a215b88312d774e06f262708734ba6b8d42c23
Traceback (most recent call last):
File "c:\Users\bdrkh\Documents\Python\EnigmaLang\test_code\helloworld_obfuscated.py", line 7, in
exec(loaded_bytecode)
File "filename", line 3394, in
File "filename", line 3389, in decrypt_and_execute_dfjqBWwQSq
File "C:\Users\bdrkh\AppData\Local\Programs\Python\Python312\Lib\site-packages\Crypto\Util\Padding.py", line 92, in unpad
raise ValueError("Padding is incorrect.")
ValueError: Padding is incorrect.
PS C:\Users\bdrkh\Documents\Python\EnigmaLang>

Sorry, I'm quite busy these days, when I'm free, I'll try.


Updated security.txt

Fixes https://github.com/nginx/unit-docs/issues/77.

Huh, I had no idea this file is duplicated!
It might make sense to store it in the main repo, and fetch it from there on the publishing step once we move to Netlify?

I like that idea more. I'll add that to my todo list and close this PR.


Blade

Blade templating. This PR is going to be dependent on WP 4.7, specifically this section of code. If you'd like to test, either use WP 4.7 or grab this code and add it to your installation. If you're using Bedrock, you can set the version requirement of johnpbloch/wordpress to 4.7.x-dev.
Currently, .blade.php files are used, and they are being added to the list of files to load via the previously mentioned new hook.
For plugins, the same issues I believe will apply that have been in Sage for the last few versions - plugins are able to load their own templates, but the same issues with calls to get_header() and get_footer() will still show deprecation warnings. You'll want to add a Blade template according to the WP template you need to override.
Looking for feedback and opinions on the current setup.

Wouldn't this fit well as a soil module? And then sage or other themes can opt in to use blade templating (or timber which I'm using).

I also like the idea of it being a soil module which allows for a user to choose between Timber or Blade.

Since you are reconstructing the templates array, could it be made available elsewhere so for instance a header or sidebar could be retrieved based on the first match on the template hierarchy?

this won't be a soil module, partly because soil is a paid plugin and partly because we don't think it fits in there
@kalenjohnson has suggested we create a composer package for it within this repo, similar to how laravel does in all of these subfolders

Also added @asset() Blade directive
It uses App\asset_path() to grab cache-busted URL

Thanks so much for your work on this! What do you think about creating some custom directives for the typical use cases such as have_posts(). There is quite a lot of php just hidden in blade syntax.
https://laravel.com/docs/5.3/blade#extending-blade

Can't wait to try this out! Would it be possible to allow injecting data into the views? I see that the template method accepts data but it doesn't appear to be used in the render. Perhaps a filter could be used.

Awesome work! I just love the blade engine and can't wait to start building stuff :)
Did a quick test run and it seems like the page.blade.php loads even though I select template-custom.blade.php.
Yes, I did make changes to the custom template.


Test dummy data

Dummy data is used to populate a new database in dev mode. Currently it goes untested. Would be good to check that all data properly inserts to database.

Yeah, I think it'd suffice to just test that the dummy data add runs successfully on an empty db


fiddle site does not use max-width like the rest of the website

It seems there's no max-width on the fiddle page:

Every other page on the site does use a max-width, it seems that just wasn't applied here.

On website where the issue is being located

there is some issue on the fiddle page


log file path

In troubleshooting articles like this, I think it would be best to include the default path to log file locations when referencing a log file that should be used in this process, or a link to another article that describes the purpose and default locations for the log file when available. Many people don't know the locations of such log files when searching out troubleshooting steps, if they did they might not be searching for the troubleshooting information to begin with.
Analyze the Microsoft Protection Log
In MPLog-xxxxxxxx-xxxxxx.log**(WHERE?)**, you can find the estimated performance impact information of running software as EstimatedImpact:

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

ID: 6a08b6ae-6445-ab2b-d380-627df46cf3d5
Version Independent ID: c855d3af-002e-aff2-b2d6-8c6e549850a2
Content: Troubleshoot performance issues
Content Source: microsoft-365/security/defender-endpoint/troubleshoot-performance-issues.md
Product: m365-security
Technology: mde
GitHub Login: @schmurky
Microsoft Alias: maccruz

@CAT-hs  i wil update tomorrow , I found that log file.


Extract "rel=stylesheet" data from HTML files

I'd like for for rollup-plugin-html to extractStylesheets as well as extractModules.
I'm not sure if wanting to put the page CSS in the HTML is a byproduct of my stubbornness to support old practices, the desire to force most (hopefully all) import styles from './styles.css' to support LitElement (though rollup-plugin-postcss also doesn't seem to support the include/exclude options common to Rollup that I think I'd want to start with to be able to work out conditional processing there) or something else that I'm missing, but I think I want to put <link rel="stylesheet"> tags in my HTML and have it extract them both for possible postCSS processing and to ensure the build takes any files referenced and puts them into dist automatically.
If this made sense to you too, I'd be happy to start putting together a PR with a little guidance on how you thought that could best be added to the plugin.

I agree this would be good to add to the HTML plugin. I think it's good to start with some use cases we have in mind here, for example some people may want to concatenate multiple stylesheet links into one file while others may want to just inline the stylesheet into the HTML.

Good call! Do you keep a map of how we're managing various <script> tag realities? I think this would probably line up 1 to 1 with that, but not sure. Some possibilities off the top of my head:
A single <link rel="stylesheet">
In the context of a "componentized" front-end, this would seem to be the default as an application's individual components would manage their own styles, and the page level styles would be more about load management and static HTML orchestration.

do nothing beyond ensuring the file is taken along for the ride (would this automatically put it into the rest of the Rollup pipeline?). if so, this might nullify some of the following options, as we could just allow the user to manage a CSS file themselves.

probably opt-out

surface a transform relative option so that custom processing can occur

does this nullify the minify option?

surface a minify relative option
surface an inline option to inject the CSS into a <style> tag

Multiple <link rel="stylesheet"> tags
What are the goals of a user that does this? Even a user that doesn't rely on SASS could leverage @import in raw CSS to get this same functionality, right?

options like the above
surface a bundle option to merge these files

nullified by the inline option?

Other concepts that might deserve a little thought:

Above the fold CSS injection

I've never used tools for this, and am unsure what sort of guardrails would be needed for a tool like ours to support aligning with a tool like that

Unused CSS clean up

Also a tool I've not used, theoretically, it reads the HTML for selectors and cross-references it to a CSS file, which would seem to occur right at the time that this plugin is doing its work. Could actually be pretty powerful in a Shadow DOM + MPA world in that you could rely on only the initial DOM needing to be styled 🤔

Interesting option as constructible style sheets get further along to add options to process specifically tagged <link> elements into constructible styles, but very future, IMO.
I'm sure there's a lot that I've missed.

A lot of things get simpler after the CSS files themselves are "in the Rollup build" as we have more opportunity to say "the power is yours", so we might be able to get away with an early version that ONLY supports doing that and use early adopters to help structure broader support delivery.

We can emit the CSS files as assets, other plugins can then act on this.

We only handle module script currently, they are extracted and passed through rollup. Multiple module scripts means multiple rollup entrypoints and multiple files loaded from the final HTML, we don't concatenate them. I think we can follow the same logic, and emit them as assets so that they're available for other plugins as well.
For inline content there will probably be a difference, inline JS is passed through rollup and not added back as an inline module but loaded externally. For CSS we probably don't want to do this, and the current HTML minifier already minifies inline CSS. But I'm not sure how it handles @import statements, are these even allowed in style elements? That's something we need to think about.
You're definitely right there are some really interesting use cases here for MPAs, that will take some more time to iron out so let's try and create something we could scale up later on.
By adding files to rollup as assets, other plugins can access them so like you said the power is available for others to extend the behavior.
Just like HTML we should have an option for transforming the CSS. transformCss? Should we rename transform to transformHtml? Thinking towards the future a bit, we may have different types of assets in the future such as JSON or import maps. Also there might be new ways to load assets like CSS, so the way the resource is included might make a difference. Perhaps we should have a transformAsset hook that receives the asset node type and attributes. Something to think about...
We should have some solid defaults, such as concatenating @import statements and minifying CSS. html-minifier uses clean-css for minifying inline CSS. It has an option for following @import statement: https://github.com/jakubpawlowicz/clean-css#how-to-process-remote-imports-correctly. That might be interesting, we could align the behavior for inline and external stylesheets. Do you have any experience with other tools?

But I'm not sure how it handles @import statements, are these even allowed in style elements?

This is a good point, I've never even thought to do that!

Perhaps we should have a transformAsset hook that receives the asset node type and attributes. Something to think about...

I like where you are going with that. I had a short moment where I was thinking: transform: { html, css, json, etc} but I think the more general approach is nicer to extend from a user standpoint.

html-minifier uses clean-css for minifying inline CSS.

I've been working a lot with postCSS lately, which is nice, but if we do get the CSS into the asset pipeline, something a little simpler is probably the right way to go there as a default. Also, the less we do, the more others can do with our output.
So cool, where do we start? 😉

Let's break it down into some steps (which we can probably merge separately):

Extract non-js resources, emit them as rollup assets and inject rollup asset name back into the HTML

which resources to extract? link rel stylesheet, img src, what else? probably we want to make this configurable somehow...
should this be enabled or disabled by default? smart defaults?

Add a hook for transforming the asset

A breaking change would be unfortunate, so let's create a transformAsset function:

Strawman:
export default {
  plugins: [
    html({
      transformAsset({ tagName, attributes, assetPath }) {
        console.log(tagName); // 'link'
        console.log(attributes); // { rel: 'stylesheet', href: 'theme.css' }
        console.log(assetPath); // 'theme.css'
      }
    })
  ]
}

Names are not set in stone of course. I'm not sure we need assetPath since we already have attributes, but it might be nice to know what the plugin is going to use for processing.

Create a way to inline critical CSS
I'm not sure if this should be in the HTML plugin, or if this should be in a separate plugin. We can spend some time thinking about this.

Figure out how to handle inline resources
We already minify inline CSS, and customizing it can be done by modifying the HTML minifier. I think that's ok to start, we can spend some time thinking how/if we want to improve on this. Especially to support @import in inline styles, if it works at all.

I've implemented this in the new HTML plugin here: https://github.com/modernweb-dev/web/pull/774


App crashing when trying to export

Sometimes when I load something and then I try to export it, the app crashes and closes

uTinyRipper has been abandoned, but you can try my AssetRipper fork. In the event that AssetRipper encounters issues while ripping your files, feel free to post an issue on that repository.
AssetRipper is actively being developed with the intent to recover games as best as possible. Weekly releases are normally on Sunday or Monday. I encourage you to help out if you're able and willing. Code contributions can be submitted via pull requests.
If you like the work I've done and want to see it continue, please consider sponsoring me. It really does help with development. These are some of the notable things I've implemented since taking over development:

2020+ support
APK, XAPK, and IPA reading with SharpZipLib
Dummy shaders (so everything isn't pink when you open the project)
IL2Cpp support via an integration of Cpp2IL
Better game platform support
Full script decompilation with the ILSpy decompiler
Cross-platform support
Multiple configuration options
Numerous performance improvements
Support for all asset types

Sponsorship Links:

GitHub Sponsors
Patreon
Paypal


Quick and dirty fix for high cpu usage.

Here is a quick fix for the high cpu load. It is not the best solution but I think we need to improve the waiting for the messages or go a other direction and do it like I did it with this implementation https://github.com/JoDehli/PyLoxone_beta

@lawrenceakka As you wrote on Discord it is for now the best solution. So i will merge it.


Move connection out of execution

Fixes #8933
Basically the long term plan is to remove the JupyterExecution.
Creating connection information and validating connections to remote jupyter servers isn't a responsibility of the JupyterExecution. the class is kinda overloaded.
Moved connection related stuff into JupyterConnection class.

Codecov Report

Merging #9918 (783f02b) into main (efa8fc5) will decrease coverage by 19%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           main   #9918     +/-   ##
======================================
- Coverage    63%     44%    -20%
======================================
  Files       203     203
  Lines      9834    9834
  Branches   1566    1566
======================================
- Hits       6244    4345   -1899
- Misses     3091    5192   +2101
+ Partials    499     297    -202

Impacted Files
Coverage Δ

src/platform/common/refBool.node.ts
16% <0%> (-84%)
:arrow_down:

src/platform/common/application/documentManager.ts
8% <0%> (-75%)
:arrow_down:

src/platform/activation/activationManager.ts
27% <0%> (-73%)
:arrow_down:

src/platform/common/application/notebook.ts
15% <0%> (-72%)
:arrow_down:

src/platform/export/exportUtil.node.ts
16% <0%> (-72%)
:arrow_down:

src/platform/export/exportToPythonPlain.node.ts
16% <0%> (-72%)
:arrow_down:

...tform/debugger/debugLocationTrackerFactory.node.ts
21% <0%> (-72%)
:arrow_down:

...tform/interpreter/display/visibilityFilter.node.ts
20% <0%> (-71%)
:arrow_down:

...atform/debugger/jupyter/kernelDebugAdapter.node.ts
5% <0%> (-65%)
:arrow_down:

src/platform/progress/statusProvider.ts
10% <0%> (-64%)
:arrow_down:

... and 93 more


Matter JS mouse events on React Native

Hello friends. I am making a slingshot with React  Native Game Engine and matter js.
However, I could not find the response of the mouse pull and release events on the mobile screen. How can I use Pull and Drop events with React Native, can you help?

Unfortunately this is out of scope of this project, sounds like you'll likely need to log this with the React Native Game Engine project instead.


Braindump: Kahoot Clone

@altimario This PR begins to prototype what an onchain clone of the popular education / classroom game kahoot.it might look like.
The code is based on this transaction lifecycle diagram I came up with at lunch.

This PR should not be merged here. Rather the code is to share ideas. If it is to be kept, it should move to Mario's own project repo. But I thought it might get better review from Tuxedo experts here.

Would be great to have this to be used at the PBA

Hello @coax1d and the whole Tuxedo team, this "Kahoot clone" is Bounder (Bet On Understanding) and is a component of the decentralised e-learning platform I'm building.
I presented the platform at the Hong Kong PBA, have a look
https://docs.google.com/presentation/d/1DwoJDHCmf8IPLnEfao-nlgykQifxMVUhFh4i4UyHYVI/edit?usp=sharing
Bounder is not trivial and I'm applying for the Decentralized Future grant program, I would like your support there if you believe it is a valid project. This is the draft description, let me know your thoughts.
https://docs.google.com/document/d/1vZakz535gO8b0y3IGZ5JAWRKCPNwBTuqKW01feBl3xE/edit

@JoshOrndorff,
Thanks. I could not understand the writings on the above dig, could you please me to label it or rewrite it for easy understanding?

Yeah, that back-of-the-receipt diagram is pretty rough lol. I wanted to make sure I didn't lose it so I posted it. Here is a legend for the notation. I'm starting to like this notation a lot.

Here is also a somewhat better version of the diagram. It is not only fixing the scribbles, it also changes some things reflecting my more recent thinking. I think we can optimistically allow the question reveals to be off-chain and only require an on-chain reveal when there is some availability problem.

Hi @JoshOrndorff ,
Thank you for the above dig.
Below is my understanding of the above diagram, Please feel free to correct me.
BounderPiece :
Bounder piece is having below transaction type or operation of constraint checkers :
1. CreateGame operation
Inputs:
Teacher UGL deposit (fee), UGL, game metadata (hash) stored off-chain.
On chain validation - constraint checker :
Creates a new game UTXO with committed questions or hash of questons.
Generates UTXO representing Pending Game.
Outputs:
UGL: UTXO representing Universal Game Logic.
Pending Game: UTXO representing the pending game with committed questions.
Note : The game metadata hash can be a reference to the off-chain information about the game, like question sets, difficulty, etc.
2. JoinGame operation
Inputs:
Student token deposit (bet), pending game.
On chain validation - constraint checker :
Students declare intent to join the game by depositing tokens.
Updates state with participants who have joined.
Outputs:
UGL spent (bet), "joined game" state stored in a student's UTXO.
This will verify the pending game exists and deducts the bet from the student's balance.
3. StartGame operations
Inputs:
UTXO representing the Pending game joined games (student UTXOs representing the participants who have joined.) for the game.
On chain validation - constraint checker :
Initiates the game.
Creates UTXO representing an open game.
Generates answers corresponding to each student.
Outputs:
"Open game" state i.e UTXO representing the ongoing game.
UTXO representing the answers corresponding to each student.
4. Settle Operation:
Inputs:
Student Answers: UTXO represents the answers submitted by students.
Open Game: UTXO represents the ongoing game.
On chain validation - constraint checker :
Validates and settles student responses against correct answers.
Simultaneously handles settlement.
Outputs:
Settled Answers: UTXO representing the settled answers for each student.
Pending Settlement: UTXO representing the ongoing settlement process.
5. CloseGame Operation:
Inputs:
Settled Answers: UTXO representing the settled answers.
Pending Settlement: UTXO representing the ongoing settlement process.
On chain validation - constraint checker :
Completes the settlement process.
Transfers deposits from losing participants to the winners.
Outputs:
Game Results: UTXO representing the results of the game.
Winners' Deposits: UTXO representing the deposits awarded to the winners.
================================================
I think it may be difficult to achieve everything on-chain due limitation of storing large quiz content (questions, answers, explanations, images, etc.) directly on-chain looks expensive due to storage fees.
So we can have Hybrid approach:
Off-chain Game Logic:
Develop the game logic (question presentation, answer selection, scoring, etc.) off-chain (e.g., server-based application).
This application will manage interactions with players, track game state, and generate outputs for on-chain transactions.

Your summary is close. One mics point: My diagram says "UGC" for universal game creator, not ugl.

I want you to carefully consider the use of the word "input". It has one definition that means UTXOs consumed by a transaction. It has another definition that means data that the user supplies to the process. It is important not to mix these up.
For example when you are summarizing the game creation (fixing the ugc issue):

Teacher deposit (fee), UGC, game metadata (hash) stored off-chain.

The teacher deposit and the universal game creator are really inputs in the UTXO sense. They are pre-existing state that is consumed by this transaction. However, the game metadata is completely different. It is not previously stored on chain and therefore cannot possibly be an input. The point of this transaction is to put that metadata on chain. It is an output in the utxo sense. (Admitted that it is an input of data from the user).

Another thing I noticed is that you mention closing the game outputting a UTXO that represents the results. Why do you want to do this? Once the game is settled and payouts are made, why have this results UTXO always taking up storage? The blockchain itself already keeps a permanent record of the result (and even the entire game play) so there is no need to also keep it in state.


add Avatar

Project URL

https://github.com/wvabrinskas/Avatar
Category

Images
Description

Generate random user Avatar images using CoreGraphics and QuartzCore.
Why it should be included to awesome-ios (optional)
Avatar is quick and easy to use. It's rather popular on Cocoapods.org too. https://cocoapods.org/pods/Avatar
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 4 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

5
Dupe
https://gitter.im/vsouza/awesome-ios

1724
502
https://github.com/Cleveroad/CRPageViewController

2259
502
https://github.com/MedvedevMax/MMSegmentSlider

2701
503
https://boombox.io/

  Generated by :no_entry_sign: Danger

Hey @wvabrinskas, thanks for contributing 👍

No problem!!!


Auto Broadcast Multiple Variables Fails

When using multiple variables in an auto-broadcast message, it fails. You can only use a single variable
Example
30 Welcome to {servername} The Next Map Is {nextmap}
Results in
Welcome to {servername} The Next Map Is {nextmap}

I don't see this issue. What version are you using?

Strange, so we just updated our auto broadcast, and the following seems to work fine now on 9.4.1
30 Welcome to {servername} || The Next Map Is {nextmap} || The map rotation is {maprotation} || We Have Admins Online = {ingame_mods} - !admin <message> || Seed and get VIP for 48 hours

Closing this for now.


[raz] Add flag for autocreation of user directories

By default, the flag is turned on.
Internal Jira: CDPD-45876

@Harshg999 , as discussed, please make the needed changes for showing the error in the UI and also post the exception in the logs as ERROR.

The change is tested in the live cluster and is working fine. Other asks can be addressed in separate PRs.


fix: setup for rn-windows

Description
I added only a few basic configurations so that the autolink in react-native-windows recognizes the library. I followed the recommendations from https://microsoft.github.io/react-native-windows/docs/native-modules-setup.
Steps To Reproduce
Follow these steps at https://microsoft.github.io/react-native-windows/docs/getting-started and create a React Native app. Then, run npx react-native autolink-windows. You'll notice that the file LottieReactNative.vsxproj is not present in the solutions list.
Expected Results
The LottieReactNative.vcxproj file should appear in the list of solutions.

Hmmm. I can't run anything locally right now, since I don't have a windows machine and i am a bit hesitant about touching anything in core. I'll run the CI to see if anything breaks with this in our current setup in the meantime and maybe we can update the examples to include windows. @matinzd what do you think?

Good question, I also hesitated to make any changes to the core in an inappropriate way. To keep this as transparent and clear as possible, I will add CI to see if anything breaks on Windows. I believe this is a critical bug, as without it, lottie-react-native 6.x.x doesn't work on Windows.

Sounds good. Please add a Windows target to the existing Apps, rather than creating a new app. Keeping both Apps in check has been difficult as is, no need to add a new one

The CI failed https://github.com/lottie-react-native/lottie-react-native/actions/runs/7523023603/job/20485648831. @Victor0814gui

A basic summary of what I did in this last change: the dependency on react-native-windows in the example was at version 0.71.18 and has been updated to 0.72.24. Additionally, I modified the Example.sln file to use the correct paths for the node_modules folder, and updated the version of Microsoft.UI.Xaml  from 2.6.0 to 2.8.0. Finally, concluding with the CI correction.

A basic summary of what I did in this last change: the dependency on react-native-windows in the example was at version 0.71.18 and has been updated to 0.72.24. Additionally, I modified the Example.sln file to use the correct paths for the node_modules folder, and updated the version of Microsoft.UI.Xaml from 2.6.0 to 2.8.0. Finally, concluding with the CI correction.

Left one change that i think is important. The rest looks good. I'll let the CI run and once all the stuff is resolved, we can merge. One question though, mostly out of curiosity, does the linking for Example.sln need to be handled manually? Does RNW not have some sort of Auto linking for these?

The CI failed again. Looks like it is missing an SDK:

I fixed the absence of the SDK and added an extra step to check which SDKs are installed👍.

The Workflow file is being reported as invalid. I believe you have a typo on Line 33:
https://github.com/lottie-react-native/lottie-react-native/actions/runs/7533290462

Hi.
Any progress / things we can help with?

Closing due to a lack of activity


HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScipt with associated notes listed

Added HTML code to application


Possible for multiple scan rates without creating a "new" controller for each one?

Current Behavior

Expected Behavior

Possible Solution (Optional)

Context

Steps to Reproduce (for bugs only)

Your Environment

Package version (Use npm list - e.g. 1.0.6):
Node Version (Use node --version - e.g. 9.8.0):
Operating System and version:
Controller Type (eg 1756-L83E/B):
Controller Firmware (eg 30.11):

I would say yes. Write your own function that performs a read based upon the scan rate timeout you wish to have.

I meant natively rather than using setInterval to perform individual reads, which is less efficient than subscriptions.

I wouldn't use a setInterval. track the last time each tag was read and then get the oldest one most needing to be read. Add several to a tag group and read the tag group is also an option. A feature request for this library may be to add a scan rate to tag groups.

while( true ) {
  await getNextTagThatIsAgedEnough()
  await readThatTag()
  await extraDelayWhenNoTags()
}

A feature request for this library may be to add a scan rate to tag groups.

Great idea.  Appreciate your insight.

I always just read tag groups in a loop with a delay, similar to what Nate shows. But I do end up setting up different controllers for each tag group and even run each controller on its own server. Usually 4 total for my standard HMI framework. But some of that may be specific for my application.


Where to suggest new stuff to be shown on this repo's readme ?

Is there a way to suggest new components, boilerplates, etc... to add here, or the only way is to contribute ? If this last case, where to ask to be contributor ?
Best regards, and thanks for your work.

Or shall we fork the repo then make a pull request ?

As you said, you should make a pull request with your changes, just make sure you follow the Contribution Guideline

Yep, please for and send a PR.


App.config gets cleared when running install

Description
For one project the app.config gets cleared when running paket install.
I've been staring at it for a while but can't spot the difference.
Repro steps
1.clone: https://github.com/JohanLarsson/Gu.Reactive

run paket install and check the diff.

Known workarounds
Git revert.

where is the problematic diff?

Gu.Reactive.Tests/App.Config

latest version allows you to set "redirects: force" on group level!


Cookies: Inject fake cookie ONCE without using jar?

Hi,
I don't normally ask for help but I've googled for an hour with no luck.
I'm trying to add a fake cookie to a SINGLE request, and I want that request's header to be "Cookie: [everything in my current jar as usual]; somefakecookie=extravalue". So I want to append an extra cookie to a request, on top of whatever normal cookies are truly in the jar.
Sure, to do this I can create a SetCookie object, set its parameters, add it to my jar, do the Guzzle request, then use a try{}finally{} to ensure that I ALWAYS clean up the jar and do a clear() on that particular FAKE cookie's domain+path+name every time...
But that is super wasteful. And is true spaghetti code.
Is there some other way I can achieve this? I just need to add a single extra fake cookie value onto a few requests, preferably without affecting my real jar and without needing the complex try{}finally{} spaghetti code above.
Please dear God tell me there is a way to solve this cleanly. :-D

Steve

I've nearly solved it. Leaving this answer for others. The answer is to create a middleware which runs after the normal 'cookies' handler, and injects the additional text into the Cookies header value.
http://docs.guzzlephp.org/en/latest/handlers-and-middleware.html


Can't decrypt when load session from byte array

I log in and save the session to a file
Then I read the byte data of the file and put it into the db.
When I initialize the session directly from the byte array in the db, I get the error message
WTelegram.WTException: 'Exception while reading session file: The input data is not a complete block.
Use the correct api_hash/id/key, or delete the file to start a new session'
I have done the hard code as follows
var client = new Client(Config<EMAIL_ADDRESS>+ session.PhoneNumber + ".session"), (data) =>
{
session.Data = data;
session.UpdateDateTime = DateTime.Now;
session.Update();
});
The result is still the same error as above.
I checked the source code of the Session class and found that the way to read a file and read directly from a byte array is different
Here is how I modified the code to make it work

internal sealed class ActionStore : MemoryStream
{
public override long Length { get; }
private readonly byte[] _header = new byte[8];
private int _nextPosition = 8;
Action<byte[]> _save;
public ActionStore(byte[] initial, Action<byte[]> save) : base(initial ?? [])
{
_save = save;
if (base.Read(_header, 0, 8) == 8)
{
var position = BinaryPrimitives.ReadInt32LittleEndian(_header);
var length = BinaryPrimitives.ReadInt32LittleEndian(_header.AsSpan(4));
base.Position = position;
Length = length;
_nextPosition = position + length;
} } public override void Write(byte[] buffer, int offset, int count) => _save(buffer[offset..(offset + count)]);
public override void SetLength(long value) { } }

*.sessions file contains the session data in a specially-optimized format, not just the raw session bytes.
So indeed you can't take such file and store it to DB or use its content with the custom load/save constructor like you tried.
You can however use that custom constructor, without initializing with bytes from a session file but instead with a null or empty initial content, it will create a new session and allow you to save its bytes.
Or you can use the recommended way to deal with database:
https://wiz0u.github.io/WTelegramClient/EXAMPLES#store-session-data-to-database-or-elsewhere-instead-of-files


🐛 Resolve type of eslint annotation comment

Overview

Resolve type of eslint annotation comment

Note

tests/linted/default$/indent-in-infix-expression.js

tests/linted/default$/no-unexpected-multiline.js

Tasks

[ ] 🐛 Resolve type of eslint annotation comment in tests/linted/default$/indent-in-infix-expression.js
[ ] 🐛 Resolve type of eslint annotation comment in tests/linted/default$/no-unexpected-multiline.js

There is no reproducibility in VS Code, thus close this issue.


Support mesos primitives for availability

This PR makes marathon drop those resource offers from agents that are set in maintenance.
Find more information here: https://jira.mesosphere.com/browse/MARATHON-3216

Fantastic job @alanbover !

@janisz  thanks for the comments, the changes have been done!
The PR is a little bit noisy now, mostly because it required some changes to make matchResources be able to receive marathon configurations

@janisz thanks for your comments! It's already changed!

Hey @alanbover,
thank you again for this contribution, we really appreciate it.
We discussed this PR internally a while ago and we would love to merge this with a related feature flag to opt in for this behavior, something like --enable_maintenance_mode or something similar. This is a little bit annoying and also this PR currently do have some merge conflicts. Would it be ok for you if I would add and resolve those and open a PR against your fork?

hey @unterstein!
Yes, I'm happy if you want to end up last details so it can be merged! Thanks a lot for that :)

Ok, great!
Short update: I already resolved the merge conflicts and currently adding one tiny commit to hide this feature behind a feature flag. Should be ready soon :)

@unterstein This PR get preety big. Nearly 150 commits and over 300 changed files. Is there any chance to split it into smaller patches? It's really hard to review.

@janisz corrected the commit.

Hey @jdef, @timcharper, @jeschkies,
could you have a look at this pr now? I added the wished feature flag, resolved merge conflicts and added more tests 🎉
Cheers
Johannes

Also I added a phabricator diff trigger ci https://phabricator.mesosphere.com/D1069

Thanks @meln1k and @zen-dog, please see last change to address your feedback :)

Thanks @alanbover!
    .  o ..
     o . o o.o
          ...oo
            __[]__          Shippin'
         __|_o_o_o\__         it!
         \""""""""""/
          \. ..  . /
     ^^^^^^^^^^^^^^^^^^^^


Add more keywords, add basic Docker config section support

jenkinsfilePipelineStep contents were sourced via an ugly heuristic from https://jenkins.io/doc/pipeline/steps/

@CH-DanReif wow this is very cool. Thank you! Have you tried it? Is it good to merge?

@martinda Well, let's be clear: it works for me, with the files with which I tested it.  It has quite a bit more functionality (e.g. in the jenkinsfileOptionParams syn region) that could easily malfunction if handed wonky data; e.g. a Property that includes a ) as part of its arguments somehow.
But my philosophy is, it's better to add more highlighting for the 99% of use-cases that don't do Weird Things, and the folks doing odd things can always submit their own PRs and/or repro cases.  syn off (or set syntax=groovy) is a cheap workaround for anyone really negatively affected.  Hell, even the C highlighter can produce bad output in really strange corner-cases.


AssetCloseTo parameter

asset close to parameter for TransferAsset transaction

hi @Anish-Xfinite in algo-builder we're using payFlags.closeRemainderTo parameter (for both, closing an ASA holding or emptying ALGO's from an account).
So for "asset close to", you can simply pass closeRemainderTo param in AssetTransfer transaction. Please let me know if that solves your issue

thanks. @ratik21


Sharding/Partitioning: How to?

In my application each user interacting with his own encrypted data synced across his devices, and therefore I need to have a new sqlite instance spin up for every user.. assume there are only a couple of users.. what's the easiest way to do it..
Considered alternatives:

add user_id field to each model and filter by authenticated request..

run multiple chisel processes on different ports

single chisel process dynamically choosing underlying database file by endpoint.. there is usually /dev endpoint in the URL..

If you absolutely require separate databases, then 2. is your only option right now.  But if you trust ChiselStrike to keep the users out of each other's data, consider using the match_login policy.

Another option.. partitioned tables.. can I create multiple CRUD endpoints using the same table model but unique rows?

match_login seems a good option.. but also I need to implement "sharing" feature.. how can I modify it's transformer to NOT ignore those rows which has been made public by it's author?

match_login seems a good option.. but also I need to implement "sharing" feature.. how can I modify it's transformer to NOT ignore those rows which has been made public by it's author?

We are evolving the policy language in that direction, stay tuned. :)

Another option.. partitioned tables.. can I create multiple CRUD endpoints using the same table model but unique rows?

Yes, but you'll also need custom code to implement the sharing usecase.

@7flash The policy overhaul being done by @MarinPostma is happening in PRs like this: https://github.com/chiselstrike/chiselstrike/pull/1746
The main idea is that it will be native typescript instead of YAML, and then you will be able to express your custom logic.
One use case we have in mind is to do both access control and geo-location (if users are in Europe, store data in a database that stays in Europe). I guess your use case is a variation of the latter, so it would work well.
Feedback on that work is appreciated!

hello @7flash, the work on typescript policy is still very WIP, but happy to discuss your usecase!


TQDMProgressBar refresh forces TPU to recompile compute graph

Bug description
TQDMProgressBar refresh forces TPU to recompile compute graph. This causes slow execute time.
How to reproduce the bug
import re
import time
import torch
import torch.nn as nn
import torch.nn.functional as F
import pytorch_lightning as pl
import torch_xla.debug.metrics as met
from pytorch_lightning.callbacks import TQDMProgressBar
from torch.utils.data import DataLoader, Dataset
from pytorch_lightning.callbacks import Callback

import torch_xla.core.xla_model as xm

class dummyDataset(Dataset):
    def __getitem__(self, index):
        return torch.rand(512), torch.rand(1)

    def __len__(self):
        return 10_000

class dummyModel(pl.LightningModule):
    def __init__(self):
        super().__init__()
        self.net =  nn.Sequential(
        nn.Linear(512, 512),
        nn.Linear(512, 1),
        )

    def training_step(self, batch):
        x, y = batch
        logits = self.net(x)
        time.sleep(1)
        return {'loss': F.cross_entropy(logits, y)}

    def configure_optimizers(self):
        return torch.optim.AdamW(self.parameters())

class TPUMetricCallback(Callback):
    def on_train_batch_end(self, trainer, pl_module, outputs, batch, batch_idx):
        if xm.is_master_ordinal():
            report = met.metrics_report()
            xrt_compile_count = re.search('Metric: XrtCompile\s+TotalSamples: (\d+)', report).group(1)
            print(f'XrtCompile: {xrt_compile_count}, batch_idx = {batch_idx}')

def main():
    refresh_rate = 1

    ds = dummyDataset()
    dl = DataLoader(ds, batch_size=16)
    model = dummyModel()

    metrics_callback = TPUMetricCallback()
    tqdm_callback = TQDMProgressBar(refresh_rate=refresh_rate)

    trainer = pl.Trainer(max_epochs=10,
                         accelerator='tpu',
                         devices=1,
                         callbacks=[tqdm_callback, metrics_callback])

    trainer.fit(model=model,
                train_dataloaders=dl
                )

if __name__ == '__main__':
    main()

Error messages and logs
Refresh_rate = 1
XrtCompile: 3, batch_idx = 0
Epoch 0:   0%|▎                                                                                | 2/625 [00:02<12:42,  1.22s/it, loss=0, v_num=0]
XrtCompile: 4, batch_idx = 1
Epoch 0:   0%|▍                                                                                | 3/625 [00:03<12:41,  1.22s/it, loss=0, v_num=0]
XrtCompile: 5, batch_idx = 2
Epoch 0:   1%|▋                                                                                | 4/625 [00:04<12:55,  1.25s/it, loss=0, v_num=0]
XrtCompile: 6, batch_idx = 3
Epoch 0:   1%|▊                                                                                | 5/625 [00:06<13:22,  1.29s/it, loss=0, v_num=0]
XrtCompile: 7, batch_idx = 4
Epoch 0:   1%|▉                                                                                | 6/625 [00:08<13:50,  1.34s/it, loss=0, v_num=0]
XrtCompile: 8, batch_idx = 5
Epoch 0:   1%|█                                                                                | 7/625 [00:09<14:26,  1.40s/it, loss=0, v_num=0]
XrtCompile: 9, batch_idx = 6
Epoch 0:   1%|█▎                                                                                | 8/625 [00:11<15:02,  1.46s/it, loss=0, v_num=0]
XrtCompile: 10, batch_idx = 7
Epoch 0:   1%|█▍
Refresh_rate = 5
Epoch 0:   0%|                                                                                | 0/625 [00:00<?, ?it/s]
XrtCompile: 2, batch_idx = 0
XrtCompile: 2, batch_idx = 1
XrtCompile: 2, batch_idx = 2
XrtCompile: 2, batch_idx = 3
Epoch 0:   1%|▊                                                                                | 5/625 [00:05<11:35,  1.12s/it, loss=0, v_num=0]
XrtCompile: 3, batch_idx = 4
XrtCompile: 3, batch_idx = 5
XrtCompile: 3, batch_idx = 6
XrtCompile: 3, batch_idx = 7
XrtCompile: 3, batch_idx = 8
Epoch 0:   2%|█▌                                                                                | 10/625 [00:12<12:22,  1.21s/it, loss=0, v_num=0]
XrtCompile: 4, batch_idx = 9
XrtCompile: 4, batch_idx = 10
XrtCompile: 4, batch_idx = 11
XrtCompile: 4, batch_idx = 12
XrtCompile: 4, batch_idx = 13
Environment

CUDA:
- GPU:               None
- available:         False
- version:           11.7
Lightning:
- lightning-utilities: 0.3.0
- pytorch-lightning: 1.8.2
- torch:             1.13.0
- torch-xla:         1.13
- torchmetrics:      0.10.3
- torchvision:       0.14.0
Packages:
- absl-py:           1.3.0
- aiohttp:           3.8.3
- aiosignal:         1.3.1
- antlr4-python3-runtime: 4.9.3
- async-timeout:     4.0.2
- attrs:             19.3.0
- automat:           0.8.0
- blinker:           1.4
- cachetools:        5.2.0
- certifi:           2019.11.28
- chardet:           3.0.4
- charset-normalizer: 2.0.12
- click:             7.0
- cloud-init:        22.1
- cloud-tpu-client:  0.10
- colorama:          0.4.3
- command-not-found: 0.3
- configobj:         5.0.6
- constantly:        15.1.0
- cryptography:      2.8
- cython:            0.29.14
- datasets:          2.7.0
- dbus-python:       1.2.16
- decorator:         5.1.1
- dill:              0.3.6
- distlib:           0.3.4
- distro:            1.4.0
- distro-info:       0.23ubuntu1
- entrypoints:       0.3
- exceptiongroup:    1.0.4
- filelock:          3.7.1
- fire:              0.4.0
- frozenlist:        1.3.3
- fsspec:            2022.11.0
- gcsfs:             2022.11.0
- google-api-core:   1.33.2
- google-api-python-client: 1.8.0
- google-auth:       2.13.0
- google-auth-httplib2: 0.1.0
- google-auth-oauthlib: 0.4.6
- google-cloud-core: 2.3.2
- google-cloud-storage: 2.6.0
- google-crc32c:     1.5.0
- google-resumable-media: 2.4.0
- googleapis-common-protos: 1.56.4
- grpcio:            1.50.0
- httplib2:          0.21.0
- huggingface-hub:   0.11.0
- hydra-core:        1.2.0
- hyperlink:         19.0.0
- idna:              2.8
- importlib-metadata: 5.0.0
- importlib-resources: 5.10.0
- incremental:       16.10.1
- iniconfig:         1.1.1
- intel-openmp:      2022.1.0
- jinja2:            2.10.1
- jsonpatch:         1.22
- jsonpointer:       2.0
- jsonschema:        3.2.0
- keyring:           18.0.1
- language-selector: 0.1
- launchpadlib:      1.10.13
- lazr.restfulclient: 0.14.2
- lazr.uri:          1.0.3
- libtpu-nightly:    0.1.dev20220930
- lightning-utilities: 0.3.0
- markdown:          3.4.1
- markupsafe:        2.1.1
- mkl:               2022.1.0
- mkl-include:       2022.1.0
- more-itertools:    4.2.0
- multidict:         6.0.2
- multiprocess:      0.70.14
- netifaces:         0.10.4
- numpy:             1.23.4
- nvidia-cublas-cu11: <IP_ADDRESS>
- nvidia-cuda-nvrtc-cu11: 11.7.99
- nvidia-cuda-runtime-cu11: 11.7.99
- nvidia-cudnn-cu11: <IP_ADDRESS>
- oauth2client:      4.1.3
- oauthlib:          3.1.0
- omegaconf:         2.2.3
- packaging:         20.3
- pandas:            1.5.1
- pexpect:           4.6.0
- pillow:            9.3.0
- pip:               20.0.2
- platformdirs:      2.5.2
- pluggy:            1.0.0
- protobuf:          3.19.5
- pyarrow:           10.0.0
- pyasn1:            0.4.2
- pyasn1-modules:    0.2.1
- pygobject:         3.36.0
- pyhamcrest:        1.9.0
- pyjwt:             1.7.1
- pymacaroons:       0.13.0
- pynacl:            1.3.0
- pyopenssl:         19.0.0
- pyparsing:         2.4.6
- pyrsistent:        0.15.5
- pyserial:          3.4
- pytest:            7.2.0
- python-apt:        2.0.0+ubuntu<IP_ADDRESS>
- python-dateutil:   2.8.2
- python-debian:     0.1.36ubuntu1
- pytorch-lightning: 1.8.2
- pytz:              2022.6
- pyyaml:            5.4.1
- regex:             2022.10.31
- requests:          2.27.1
- requests-oauthlib: 1.3.1
- requests-unixsocket: 0.2.0
- responses:         0.18.0
- rsa:               4.9
- scipy:             1.9.3
- secretstorage:     2.3.1
- service-identity:  18.1.0
- setuptools:        62.3.2
- simplejson:        3.16.0
- six:               1.14.0
- sos:               4.3
- ssh-import-id:     5.10
- systemd-python:    234
- tbb:               2021.6.0
- tensorboard:       2.11.0
- tensorboard-data-server: 0.6.1
- tensorboard-plugin-wit: 1.8.1
- tensorboardx:      2.5.1
- termcolor:         2.1.0
- tokenizers:        0.13.2
- tomli:             2.0.1
- torch:             1.13.0
- torch-xla:         1.13
- torchmetrics:      0.10.3
- torchvision:       0.14.0
- tqdm:              4.64.1
- transformers:      4.24.0
- twisted:           18.9.0
- typing-extensions: 4.4.0
- ubuntu-advantage-tools: 27.8
- ufw:               0.36
- unattended-upgrades: 0.1
- uritemplate:       3.0.1
- urllib3:           1.25.8
- virtualenv:        20.14.1
- wadllib:           1.3.3
- werkzeug:          2.2.2
- wheel:             0.34.2
- xxhash:            3.1.0
- yarl:              1.8.1
- zipp:              3.10.0
- zope.interface:    4.7.1
System:
- OS:                Linux
- architecture:
- 64bit
- ELF
- processor:         x86_64
- python:            3.8.10
- version:           #32~20.04.1-Ubuntu SMP Thu May 26 10:53:08 UTC 2022

More info
using TPU-VM TPUv3 on GCP, with tpu-vm-pt-1.13 image, installing this packages using pip
pytorch-lightning
torch
pytest
datasets
scipy
regex
requests
numpy
fsspec[gcs]
hydra-core
transformers
httplib2>=0.15.0
tensorboardX
protobuf==3.19.5
cc @awaelchli

It could be that this is caused by the metrics collection (the loss etc. we show in the bar), which involves tensor operations.

I've been looking into the code trying to debug the superfluous graph recompilations and noticed that there is a difference when testing on 1 vs 8 TPUs.
While using a single TPU, the single_tpu.py  strategy is used, which seems to not be wrapping the dataloader with MpDeviceLoader, which is used in the multi TPU tpu_spawn.py strategy here. One of the things that this wrapper is doing is forcing graph execution after every batch. This limits the size of the computation graph, while in single TPU case the computation graph keeps growing across multiple batches, until there is an explicit call to access tensor values, for example, while printing loss.

As for the compute graph recompilations, the running_loss accumulator, which is stored on the device, is problematic. Because it's on device, it means that there is a compute graph being built behind the accumulation logic, this line seems to be particularly not compute graph friendly.
Setting the running loss aggregation window to some low value stops the amount of graph compilations from growing, so it confirms that it's connected with the problem, but I haven't found an elegant way to fix it yet.

I don't think so, .detach() tells PyTorch that there is no need to track the gradient graph, but the graph for performing loss aggregation still needs to be built, as it is defined as a chain of operations on the TPU. Not sure how to correctly ''detach'' the TPUs computation graph, maybe a well placed xm.mark_step() to force graph compilation and execution will do the trick.

I have seen this happen with GPU too. Tried detaching everything but didnt work, in case you haven't tried that. Is there any workaround to it?

You might be interested to check #16020 which now handles the xm.mark_step() correctly. This might fix your issue.


LND error: Block not available (pruned data)

Background
Hi, I’m trying to get my LND up and running for the first time on my EmbassyOS. My node is 100% synched .
Your environment
EmbassyOS
LND 0.11.1~1
BitcoinCore 0.21.0~2
Steps to reproduce
I have transferred a small amount of funds to the wallet because I was following these instructions:
After setting up your Lightning node, make sure it is funded by sending bitcoin to your node wallet address and establishing channels with other nodes. Then you can begin participating in the network.
(from here: https://bitcoinmagazine.com/learning-bitcoin/how-to-operate-a-profitable-lightning-mode)
once I transferred, note, the transfer was successful when I look it up by the transaction ID, I thought I would see something in the RTL console, but my sats have remained at 0.
I then looked at the logs of the LND, and saw this error:
2021-03-10 22:16:43.029 [ERR] LNWL: Unable to complete chain rescan: -1: Block not available (pruned data)
Could I get some helping in getting my LND up and running? Thank you 🙏

From the error message it looks like you're running a pruned bitcoind node. That is not supported by lnd in the current version: https://github.com/lightningnetwork/lnd/blob/master/docs/safety.md#pruned-bitcoind-node

Ok thank you. I’ll talk to start9labs and see if I can change this setting from the embassy console.
Would you know how to do this on the EmbassyOS?

No idea, sorry. I'm not familiar with EmbassyOS at all.
Closing this since it's a known unsupported use case.

@nsav if you're open to testing and don't mind waiting a couple more days, I'm working on a PR to enable pruned bitcoind support.

Hi,
I have it up and running now, not sure what happened. Once I restarted it all started working.
But I should test as I dont want to lose sats testing and playing around.
I think I’ll go on a testnet
Thanks,
Nick
Sent from my iPhone

On 12 Mar 2021, at 13:35, Wilmer Paulino @.***> wrote:

@nsav if you're open to testing and don't mind waiting a couple more days, I'm working on a PR to enable pruned bitcoind support.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


use CFF abstract as zenodo description

For example:

this information was added by hand, and resulted in this text on Zenodo: https://doi.org/10.5281/zenodo.1287235.
this information was added by hand, and resulted in this text on Zenodo: https://doi.org/10.5281/zenodo.1305971

turns out I had fixed this already: https://github.com/citation-file-format/cff-converter-python/blob/435b6e98ac91eb560bc7e4f43cbf55640b76dbab/cffconvert/citation.py#L460-L461


pep8 linter was renamed to pycodestyle

The pep8 tool was renamed to pycodestyle.
Historical background detailed in this ticket (from before I switched from Atom to VSCode): https://github.com/AtomLinter/linter-pycodestyle/issues/55
The python.linting.pep8* options in this linter should probably be renamed to python.linting.pycodestyle* to reduce confusion in the future.
Happy to help update the extension, but I'm not sure of your policy on deprecating/migrating settings to new names...??

In this instance we would probably implement the new options and then leave the old ones deprecated for several releases until removing them.

See also DonJayamanne/pythonVSCode#808

I managed to workaround like this:

instal pycodestyle (no need to install pep8)
add this to settings.json:
    "python.linting.pep8Path": "pycodestyle",  // workaround to use pycodestyle instead of pep8
select pep8 as linter

✅ Validated:

[x] No pep8* settings, pycodestyle settings are available (in the UI and in a local .vscode/settings.json)
[x] Setting up linting with pycodestyle for the first time works
[x] Migrating from pep8 to `pycodestyle works
[x] Linting with pycodestyle works


replace upstream Dockerfiles with ubi dockerfiles.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes https://issues.redhat.com/browse/RHOAIENG-6506
Note: Replaced existing Dockerfiles because that file is what Konflux uses to build the images. Also, this will help track any changes to the upstream dockerfile because it will create a merge-conflict (as opposed to maintaining a separate Dockerfile.ubi8` file).
Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

tested podman build succeeds locally.

We also should update the storage initializer one.

We also should update the storage initializer one.

If I am not mistake, custo_transformers and custom_model as well.

We also should update the storage initializer one.

@israel-hdez added the storage initializer dockerfile as well.

We also should update the storage initializer one.
If I am not mistake, custo_transformers and custom_model as well.

@spolti doesn't look like we use/build those today https://github.com/opendatahub-io/kserve/blob/master/config/overlays/odh/params.env

@spolti @Jooho all comments are addressed. PTAL

/retest-required

@Jooho I checked the CI failures, the failure is not in the test. The destroy-cluster sub step timed out after the test was successful. The ci failure can be ignored. PTAL.

ci-fast show test passed but full ci failed
INFO[2024-05-30T18:59:12Z] Running step e2e-fast-e2e-fast.
WARN[2024-05-30T19:16:52Z] Failed to get namespace ci-op-zvy0gbrz for heartbeating  error=Get "[https://<IP_ADDRESS>:443/api/v1/namespaces/ci-op-zvy0gbrz](https://<IP_ADDRESS>/api/v1/namespaces/ci-op-zvy0gbrz)": http2: client connection lost
INFO[2024-05-30T19:18:34Z] Step e2e-fast-e2e-fast succeeded after 19m21s.
INFO[2024-05-30T19:18:34Z] Step phase test succeeded after 19m21s.

ci-slow show test passed but full ci failed
INFO[2024-05-30T19:09:18Z] Step e2e-slow-e2e-slow succeeded after 10m4s.
INFO[2024-05-30T19:09:18Z] Step phase test succeeded after 10m4s.

So I think we should ignore the ci failure.


Add Tech Stack Filter

Problems
The website can only filter the people/engineers only by their location. The employer might find it hard to search for specific engineers that match their requirements.
Solution

Add the Tech-Stack filter feature

Implementation

Added Svelte-Select library to provide a Select component with common features (e.g. Multi-values)
Added Tech-Stack filter component and function to filter people/engineers by inputted stacks
Repositioned filter layout (Tech-Stack and Location filter) using flex
Refactored filter function and implemented multiple filtering that triggers a single function. It would be easy to add another filter feature in the future

Wah, mantap sekali ini. Terimakasih 🙏


query to get all elements

what should I specify in the query to get all elements without filters?

Thanks for asking @ArtiikSK
Could you detail what are you trying to do?
Are you launching a web server to try?
You can add a vídeo or screenshot too if you like.


One line docker install fails

Hi All,
I ran into an error with the one-line docker install over and over again and don't know how to sort it out.

Fresh VM running Ubuntu 18.04 + Plesk.

Tried this https://github.com/helpyio/helpy/wiki/Helpy-on-Ubuntu-18.04-with-Docker-and-the-one-line-Helpy-Installer and at some point I end with the following error:

ERROR: for frontend  Cannot start service frontend: driver failed programming external connectivity on endpoint helpy_frontend_1 (084c6b8d1cd1e4d0cdeaa0dd5b72006b925e84a6e06693d6acca4f644256af3e): Error starting userland proxy: listen tcp <IP_ADDRESS>:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

sudo nedstat returns:

tcp        0      0 XX.XXX.XXX.XX:443       <IP_ADDRESS>:*               LISTEN      29976/nginx: master
tcp6       0      0 XXXX:XXXX:XXXX:XXX::443 :::*                    LISTEN      29976/nginx: master

Which I kind of understand as being the nginx proxy listening for SSL connections.
How can I get past this??

That sounds like you've got an nginx server running locally already? Perhaps Plesk comes with one. I had to change the bind port in docker-compose.yml to something else, and update my local webserver to proxy back to helpy on the other port.


Assess forking, maintaining and incorporating luafun

So luafun looks very unmaintained but REALLY cool. I'd love to slowly replace aniseed.core with it, maybe shim to it for the time being while also providing aniseed.fun as another optional module you can require...
I think it'll be a GREAT building block to ship with Aniseed, I'd love to rely on it within Conjure too. My current implementations in aniseed.core are pretty inefficient, but I haven't had to worry, I've never hit any performance issues. Now I'm thinking this could help remove any issues before they even pop up.
Exciting! I could also use a maintained fork for other things at work too, so it could help me in my day to day work.
Would probably want to convert it to Fennel too 🤔 but probably still a separate repo?

Now thinking about it, I think that much code will just impact load time pretty horribly. Just like loading the whole Fennel compiler (which I've only just managed to prevent from loading if we don't need it).

Have you tested it out?
$ du -sh aniseed/lua luafun/fun.lua
288K	aniseed/lua
32K	luafun/fun.lua

I think boost the base functions by wasting 10% load time is not that horrible.

I have not, no! Although it does seem cool. Although if I use it inside Aniseed it seems like one of those libraries that pollutes everything it touches, like using ImmutableJS. You have to go all in with it and teach your users that you have to use the special functions from the library to interact with some things. Something I'm not too keen on, so maybe it's just best to have users include it in their code if they need it? So it's truly optional?
I would only include it in Ansieed if I actually depended on it so users can share that tool if they need it too. But I wouldn't just vendor it in just so others can use it if Aniseed doesn't need it.
So, the experiment would be:

Does adding luafun into Aniseed impact loading time much?
Once all aniseed.core code has it's internals replaced with luafun calls (if possible) is it faster to load and use Conjure, or is it the same?
Can we replace lots of aniseed.core with transparent references to luafun functions? If only one or two of them can like map and filter, maybe it's not worth it.

I'll take a look if I have time.

I've added luafun to Aniseed and swapped map, filter and reduce over to use it. No idea if this breaks everything or makes any difference whatsoever, but it's there on the develop branch of Aniseed.

Okay I was wrong, I've added luafun to Aniseed develop branch but I haven't integrated into aniseed.core because the functions work very differently and return iterators, not more tables. So it is not a 1-1 conversion right now, I might be able to use these instead of my own map function etc but it won't get you the same optimisations going all in on luafun would.
So maybe I'll use luafun for Aniseed core just to remove some duplicate code, but users will have to learn and use luafun themselves to get the full speed benefit of chaining the function calls with iterators.
It's like the difference between a clojure map call and a transducer really. As far as I can tell.


GKE kube-hunter issue

I am installing the kube-hunter in gke cluster in GCP cloud.
I am using this image aquasec/kube-hunter which is present in the DockerHub
But when im applying it the kube-hunter is not working.. Its because of the IP ranges which im not able to pass through command in k8s job.yaml file.
if i run this docker file locally and passing --remote HOSTIP this will work.
kubectl logs -f pod/kube-hunter-h65g8 -n kube-hunter
2021-10-10 12:40:00,090 INFO kube_hunter.modules.report.collector Started hunting
2021-10-10 12:40:00,090 INFO kube_hunter.modules.report.collector Discovering Open Kubernetes Services
2021-10-10 12:40:00,103 INFO kube_hunter.modules.report.collector Found vulnerability "Read access to pod's service account token" in Local to Pod (kube-hunter-h65g8)
2021-10-10 12:40:00,105 INFO kube_hunter.modules.report.collector Found vulnerability "Access to pod's secrets" in Local to Pod (kube-hunter-h65g8)
2021-10-10 12:40:00,106 INFO kube_hunter.modules.report.collector Found vulnerability "CAP_NET_RAW Enabled" in Local to Pod (kube-hunter-h65g8)

Vulnerabilities
For further information about a vulnerability, search its ID in:
https://avd.aquasec.com/

Hi @mrrobothack1
Sorry for the late response. take a look at #486 see if the PR fixed your problem :)


Feature: BitmapPath

Implements this https://github.com/Mapsui/Mapsui/issues/1998

Instead of IconPath I used the name BitmapPath (Consistency because the id is called BitmapId)
I Added a Bitmap Registry to the RenderService it is called RenderBitmapRegistry, it records all Bitmaps that are registred during the rendering and when the RenderService is disposed the Regisered Images are unregistered and disposed. So that no Memory Leaks can occour.
Added three samples: Sprite BitmapPath, Symbol BitmapPath, Brush BitmapPath.
Added Unit Tests for the RenderBitmapRegistry.

Instead of IconPath I used the name BitmapPath (Consistency because the id is called BitmapId)

Good choice to be consistent. Yet we may have to rename the BitmapId as well, because it is not just a bitmap, but can be svg or SKPicture as well. But this might change entirely.

I Added a Bitmap Registry to the RenderService it is called RenderBitmapRegistry, it records all Bitmaps that are registred during the rendering and when the RenderService is disposed the Regisered Images are unregistered and disposed. So that no Memory Leaks can occur.

Good, it is important to have clear who is responsible for disposing. The general rule that we had in C++ and Delphi is that the class creating the instance is responsible for disposing it. That is a good simple rule. That rule is also used by the dispose analyzer we use. In our code we do not always apply this rule and I think we can fix that so that we do not have to suppress warnings (but there may be exceptions). In the case of caches objects exist over a longer period and it is not possible to create & dispose within a small scope. In that case the cache should be responsible for disposing, but thus also for creating. We often create on the outside and then put is in the cache which forces us to suppress a warning. Instead we should pass in a create method to the cache. I don't think that should be part of this PR.

Tomorrow I will investigate splitting out the SKPicture from the BitmapRegistery.


fixing rails4 compatibility

hey, as i needed to extend the client a bit and we're working on rails4 i first had to get the specs passing. these are the changes i made. i also had to bump the database_cleaner version to 1.0.1 (which is working with rails4 but all versions > 1.1 currently don't work with sqlite).
i'm going to open another PR for the extension i made to the client. then you can decide if this would be useful for other people as well.
cheers,
johannes.

Are there any plans to release a version of this gem that works under Rails 4? Is this gem still actively maintained/supported?

I'm not actively involved in the gem anymore, but from what I occasionally
see on GitHub and on this mailing list, a number of people are keeping it
going. Not sure what the plans are for Rails 4, but hopefully someone else
will chime in.
On Sat, Feb 21, 2015 at 1:02 PM, Jonathan Rochkind<EMAIL_ADDRESS>
wrote:

Are there any plans to release a version of this gem that works under
Rails 4? Is this gem still actively maintained/supported?
—
Reply to this email directly or view it on GitHub
https://github.com/rubycas/rubycas-client/pull/69#issuecomment-75383738.

environment.rb
CASClient::Frameworks::Rails::Filter.configure(
:cas_base_url => "http://localhost:8888/",
:enable_single_sign_out => true,
:ticket_store => :active_record_ticket_store
)
these are my settings. registrations, login are working fine.
But I am getting this error when i am signing out. any help would be appreciated
NoMethodError (undefined method `ticket_store' for #CASClient::Client:0x00000004e61578):


Add resource authorization to the POST events endpoint

Description
Initial implementation of events authorization will use hard coded attribute identificators to define correct resource in an authorization request. This is in line with how we currently do it for App events and subscriptions. The resource identifying values will be globally static. The resource registry might be needed in the future if there are authorization parameters that are different across different event producers.
Example of request is defined here: Examples for requests are specified here https://github.com/Altinn/altinn-authorization/issues/42
Consideration
How do we enable applications to post events?
Do we need to have strategies for when to require the events.publish scope?

Will we have seperate endpoints but a common service for the rest of the flow?

App events will not be handled by the new endpoint. The AccessToken used when authenticating an app will initially not be given the necessary scopes.
Tasks

[x] Specify resource attributes to specify a resource in an authorization request.
[x] Implement authorization logic for external events
[x] Implement unit tests
[x] QA
[ ] Manual test
[ ] Automated tests

Acceptance Criteria

[x] An end user should not be able to post an event for a source they are not registered to post for
[x] Posting an event without the resource property should be prohibited
[x] A request with the altinn:events.publish scope and authorized used should return 201
[x] A request with the platform access token and an authorized used should return 201

Ready for test. A significant change in this PR is the expected format of the cloud event. Resource should be on format: urn:altinn:resource:ttd-altinn-events-automated-tests

The endpoint returns 200 OK and not 201 Created. With that being said we've agreed that 200 Ok is fine in this case. The event is accepted and stored, but we don't have any endpoint to retrieve the specific event. There is nowhere for a 201 Created responss to point to in a Location header.

Removed acceptance criteria:

[ ] An end user should not be able to post an event type not registered for the event source in the registry
It's no longer true.

Manual testing completed


Hello from WireMock

Hi @satvik-s et al, thanks for this project! Duplicating and expanding my old email from this spring, because we have a few Hacktoberfest contributors who want to improve the WireMock and Node.js integrations. In
https://github.com/wiremock/ecosystem/issues/10 we are about creating a new module for Testcontainers for Node.js, and I think there are many opportunities for collaboration
In April I joined WireMock Inc. to help with building the open source ecosystem and the community around the WireMock project. So I started reaching out to maintainers and built solution pages including the Node.js one referencing this project:  https://wiremock.org/docs/solutions/nodejs/
If you have some time, it would be great to get your feedback on WireMock and the missing features, as well as any support you are looking for as a maintainer. We're currently introducing the GitHub organization with open governance that could help to simplify maintenance and onboard more contributors/maintainers - https://github.com/wiremock/ . Maybe you would be interested to move the project there.

thanks for reaching out! i have reached back over email :)

Let's keep it.
FYI @tomakehurst @leeturner

@oleg-nenashev apologies for the delay here. does the original intent indicated in the issue still stand?

Hello. Yes, I think it remains actual.

hi @oleg-nenashev! we are working to figure out what would happen to the MIT license if we were to do the transfer. will get back once I have an update.

Hi. Sure. FYI I changed the job and now may not have bandwidth to follow up. Cc @tomakehurst as the best contact point

@tomakehurst i have the approval to proceed with the transfer if the wiremock team still wants to take it over. let me know if that is the case and would be happy to discuss the next steps


add support of owned string in the FieldType of ObjectReflection

Title: add support of owned string in the FieldType of ObjectReflection
Description:
Now the FieldType only support string view and number. It's impossible to return a string that has independent lifetime.
[optional Relevant Links:]

Any extra documentation required to understand the issue.

Maybe the InlineString is a possible solution for this requirement.
cc @kyessenov

TLVs are stored as inlined character arrays, we could use string views, no? If we don't keep the field values trivial, we would have to provide more memory management, and possible bugs with it.


localization: adding "tel" and "pattern" string to "zh"

(added in the beginning of all strings.)

Please prepend the commit message with "Localisation:"

these 2 strings is not included in other language files, so i am not sure this commit should be categorized as "localization".
anyway, edited.

these 2 strings is not included in other language files, so i am not sure this commit should be categorized as "localization".
anyway, edited.

Wha do you think we need those strings when they are not part of other lang files?

these two strings refer to the input's html5 feature. i used them in my project, at least.
in my opinion, all language file should include them, especially for the "pattern" string.


Implement storage::ObjectWriteStream

Introduce a IOStream writer (a class derived from std::basic_ostream<char>)
that uses libcurl pushing to GCS as its backend. This is part of the changes for
#557 to support streaming uploads.

@houglum This is ready for review now.

@houglum ping.


Multiple data sheets

Currently it's not possible to connect to multiple sheets. When possible, this feature would be interesting in order to integrate different datasets.

This would be great!

This could be a good add, but would also add some decent complexity to the configuration of the extension flow. Each data set could have different interactivity rules that are needed to enable it to work with the Tableau dashboard.


Inconsistent table list

Hi, I'm configuring our file checker to use RAMIP tables so that the data can be ingested at CEDA.
There is an inconsistency between the table_id list in RAMIP_CV.json and the actual list of files present (there should be a RAMP_xxx.json file for each table_id entry).
Please check that the all the desired tables are present and update the list in RAMP_CV.json to match.

HI Martin,
I've removed the unused tables from the table_id list in RAMIP_CV.json.
Cheers!


esfit: table focus resets each iteration

For a parameter table with a scroll bar, the scroll bar resets to top after every iteration. This makes it impossible to follow a parameter at the bottom of the table. Seen both on Mac and on Win10.

Here is a MWE - unselect all fit parameters except the last one.
clear, clc

Sys.g = [2 2.01 2.02];
Sys.Nucs = '1H,1H,1H';
Sys.A = [10 20 30; 5 8 12; 3 15 30];
Sys.lwpp = 0.1;

Exp.mwFreq = 9.5;
Exp.Range = [334 341];

[B,spc] = pepper(Sys,Exp);

vSys.g = [1 1 1]*0.003;
vSys.A = [1 1 1; 1 1 1; 1 1 1]*4;
vSys.lwpp = 0.05;

esfit(spc,@pepper,{Sys,Exp},{vSys})

This issue can be fixed by moving completely to App Designer uicomponents, however, it seems that to maintain all of the functionality of the esfit GUI, so far it looks like the Matlab release needs to be R2019b or later. Using App Designer uicomponents simplifies dealing with other parts of the GUI as well.
To fix this issue in older versions of Matlab easily would require using undocumented features at the Java level, but it seems that Matlab is going to make it more difficult to interact with Java objects in the future, so I'm not sure how long this would then work for newer Matlab versions.
Depending on how important support of old Matlab versions is, one option could be to switch between different versions of the esfit GUI depending on the release used.

IMO we should not fix this. Using undocumented Java is going to be very brittle going forward.
I think it's worthwhile considering implementing EasySpins' GUIs using uicomponents - but that's a separate issue and doesn't have to be part of 6.0.


MWPW-135908 Add lana

Add lana
Replace consoles with lana

Resolves: MWPW-135908
Test URLs:
N/A

@meganthecoder, quick question do you know what you plan on using for tags on your messages?  It is best practice to send in at least one tag for each message, that way we can filter messages for certain tags when creating alerts.  You can see some ideas for tags here:  https://wiki.corp.adobe.com/pages/viewpage.action?pageId=3008810368
Also, all LANA messages shouldn't be sent in with empty/null tags.  Most teams have chosen to have a default tag sent in if no tag is provided.

@meganthecoder, quick question do you know what you plan on using for tags on your messages? It is best practice to send in at least one tag for each message, that way we can filter messages for certain tags when creating alerts. You can see some ideas for tags here: https://wiki.corp.adobe.com/pages/viewpage.action?pageId=3008810368
Also, all LANA messages shouldn't be sent in with empty/null tags. Most teams have chosen to have a default tag sent in if no tag is provided.

@amauch-adobe I update the code. Does that look right?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (34f33d1) 86.36% compared to head (eae7691) 91.42%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #29      +/-   ##
==========================================
+ Coverage   86.36%   91.42%   +5.06%
==========================================
  Files           2        2
  Lines         176      175       -1
==========================================
+ Hits          152      160       +8
+ Misses         24       15       -9

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

@meganthecoder, quick question do you know what you plan on using for tags on your messages? It is best practice to send in at least one tag for each message, that way we can filter messages for certain tags when creating alerts. You can see some ideas for tags here: https://wiki.corp.adobe.com/pages/viewpage.action?pageId=3008810368
Also, all LANA messages shouldn't be sent in with empty/null tags. Most teams have chosen to have a default tag sent in if no tag is provided.

@amauch-adobe I update the code. Does that look right?

yeah, that works.


fix: delete the never-arriving return non-nil err

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.006%) to 76.91%

Files with Coverage Reduction
New Missed Lines
%

pkg/cmd/destroy/options.go
7
81.86%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
9070

Relevant Lines:
11793

💛  - Coveralls


Allow to configure w3c compliant

Signed-off-by: Mior Muhammad Zaki<EMAIL_ADDRESS>

Coverage increased (+0.08%) to 84.737% when pulling 92de3472f4f2c765afa14bf39bb9260bc163a950 on w3c-compliant into 12b3f897a39504e5b5f7109ee73788c886fcece3 on 6.x.


Set Restart Policy to Always on Tethys Dockers

Set the restart policy of the Tethys dockers so that they will start automatically after a system reboot of the server they are running on.
See: https://docs.docker.com/reference/commandline/cli/#restart-policies

Done.


Replace min_worker and max_worker with num_workers

The current ClusterConfig() has a parameter for both min_worker and max_worker. These parameters are used by the Ray Cluster resource for auto-scaling. Currently, deploying Ray Clusters via Appwrapper does not support Ray auto-scaling. So, we don't actually need both of these parameters right now.
We should update the ClusterConfig() to only take one parameter for this: num_workers

Solved with #266


Node support

With these changes in place, simply importing vanilla-lazyload without using it won't crash Node by itself.
This is important for isomorphic/universal/server rendered setups where the same code runs on both the server and the browser.
(My ulterior motive is that merging this will let us stop vendoring vanilla-lazyload over at https://github.com/shopgun/incito-browser and re-add it as a proper dependency)

Hey @klarstrup,
thank you for taking the time to do the fix.
Do you have the chance to create the pull request towards a feature branch of my repo, or are you only able to pull request toward master?

Never mind, I’ve just found how to proceed here https://help.github.com/articles/checking-out-pull-requests-locally/

Done!

Do you need this in version 8.x too?

Good stuff man, keep up the great work!

Thanks! We open-source projects maintainers need kudos to keep up! 😄


S3 components.

S3 components.

Tested mvn install of new jmeter-components jar, loading all three samplers into jmeter script.
Everything works ok. Merging this pull request to master


Phantomjs threw an error when navigating a web application with the scripts containing javascript 'bind' function

Hi,
I have an issue when navigating a web application using casper js. When the scripts in the web page use 'bind'  function for binding context, i got an errow that the function is not recognized. I m using phantomjs version 1.9.0.
Any idea how fix this issue? I don't want to change all the places i m using the 'bind' function.
Thanks for your precisous help.

Update to latest phantomJS 1.9.x.
Get the polyfill https://www.npmjs.com/package/phantomjs-polyfill

add bind function in page.onInitialized
var webPage = require('webpage');
var page = webPage.create();
page.onInitialized = function() {
  page.evaluate(function() {
      //for bind()
	  var isFunction = function(o) {
            return typeof o == 'function';
        };

        var bind,
            slice = [].slice,
            proto = Function.prototype,
            featureMap;

        featureMap = {
            'function-bind': 'bind'
        };

        function has(feature) {
            var prop = featureMap[feature];
            return isFunction(proto[prop]);
        }

        // check for missing features
        if (!has('function-bind')) {
            // adapted from Mozilla Developer Network example at
            // https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Function/bind
            bind = function bind(obj) {
                var args = slice.call(arguments, 1),
                    self = this,
                    nop = function() {},
                    bound = function() {
                        return self.apply(this instanceof nop ? this : (obj || {}), args.concat(slice.call(arguments)));
                    };
                nop.prototype = this.prototype || {}; // Firefox cries sometimes if prototype is undefined
                bound.prototype = new nop();
                return bound;
            };
            proto.bind = bind;
        }
  });
};
page.open('URL', function(status) {
  console.log("Status: " + status);
  if(status === "success") {
    page.render('example.png');
  }
  phantom.exit();
});

PhantomJS 1.9.x is not being developed any more.  We are only interested in bug reports that are reproducible with 2.0.
Also, this appears to be more of a support request than an actual bug report.  For general question, code review request, build problem, or other related discussion, please post it to either:

the official PhantomJS users mailing-list
Stack Overflow (with phantomjs tag)

If you have not read it yet, please check also a few tips on Effective Q&A.


WIP: cert: Adding DER encoded support for verify command

This adds support to the verify function to allow both DER and PEM formatted certificates. Previously this only supported PEM formatted certificates.
This is a place-holder until the functionality gets merged upstream and the next version of virtee/sev is released.
Resolved: #35

Can you make this a draft pull request to ensure it doesn't get treated as a regular PR?

Otherwise LGTM.


feat: prevent  detection of web shells rules as malware by Windows Defender (955260 PL1)

Windows Defender is detecting pattern <title>Ru24PostWebShell - as Backdoor:PHP/Dirtelti.MTJ. This PR prevents it by removing -  from the end of the pattern.
Fixes #3603.

@theseion @fzipi Any hints on how to force a test to output a string with new lines?

Use encoded_request and pass the payload as base64 encoded string. That ensures that you carriage returns don't get lost as well.

We don't yet have a facility to mock responses. However, because responses are reflected we can use the request to inject at least part of the response. I quickly tested the test you wrote and the response does contain the newlines you sent in the request (pass --trace to go-ftw to see the response).

But test haven't pass, so something is wrong. Maybe it outputed \r\n instead of \n, which regex expects?

There are two problems:

the expected response is embedded, so the response body will never match ^....
line breaks are returned as literal \n sequences

We need to have a built-in facility in go-ftw for this, unfortunately.

So, is it currently possible to write a test for that rule?

No, it currently isn't possible. I would still like to keep your test. Just set enabled: false and add to the description that we cannot currently run this test with the setup we have.

@theseion Thank you!

Glad this made the cut.


get all images in detail page

currently its just the first

added all images of item with resolution
{ images: [ 0: { id: "", type: "", width: "", height: "", url: "" } ] }