Codeunit 50001 Already Exists in NAV 2018

When I create a new codeunit 50001 against NAV 2018, I get the following message:
severity: 'Error'
message: 'An application object of type 'Codeunit' with ID '50001' is already declared'
at: '1,10'
source: 'AL'
code: 'AL0264'
This mystery codeunit seems to contain the following procedures:

There is no sign of this object being used in any Extension according to the NAV App Object Metadata, so I'm assuming it's an internal thing.

Do you see this codeunit in C/SIDE?

No

@StanislawStempin Are you still following this topic? This bug needs to tagged and fixed.

This must have been an issue with how the Docker image for NAV 2018 was prepared. Following these steps I cannot reproduce the issue anymore:
install-module navcontainerhelper -force
New-NavContainer -accept_eula -containerName "NAV2018" -imageName "microsoft/dynamics-nav" -includeCSide -doNotExportObjectsToText

Agreed, this seems to be fixed in CU4.


Minor: uv tool install should be able to modify which Python a tool uses.

This is loosely related to #6297 (Update and/or https://github.com/astral-sh/uv/issues/7287). I have poetry installed with the default option, which meant that it used Homebrew python. I wanted to switch to managed python.
$ pwd
/Users/ilyagr/.local/share/uv/tools/poetry/bin
$ realpath python
<EMAIL_ADDRESS>$ uv tool install poetry --python-preference only-managed --reinstall
<Installs managed python>
<Some output omitted>
Installed 1 executable: poetry
$ realpath python # Should have changed but didn't
<EMAIL_ADDRESS>
After uv tool uninstall poetry, uv tool install poetry --python-preference only-managed did work correctly.
$ realpath python
/Users/ilyagr/.local/share/uv/python/cpython-3.12.6-macos-aarch64-none/bin/python3.12

Either the original command should have changed poetry to use the correct python version, or it should have shown an error and should not have installed the managed python. In the latter case, it could suggest uv tool upgrade --python once #6297 is solved.
I'm using uv 0.4.9 (77d278f68 2024-09-10) on ARM Mac OS X.

This sounds like a bug, thanks for the report!

cc @charliermarsh the solution may be immediately obvious to you here

We fetch a matching Python interpreter upfront because we (might) need it to resolve unnamed requirements. But we then reuse the existing environment later when reinstalling the package.
I am wondering if --reinstall should never reuse the existing environment.

I think even without --reinstall if we select a different Python interpreter than the one in the environment we should replace it?

Do you think "any different Python interpreter"? Or just that we should take --python-preference into account when determining whether the existing interpreter satisfies the request (like how we would allow a Python 3.12.3 interpreter today if the user passed --python 3.12, even if Python 3.12.4 was also installed)?

(The former is way easier.)

I think "any different Python interpreter" sounds compelling though it seems a little dubious to do a reinstall when --python 3.12 is requested and there's just a different patch version. Hm.

I started looking into this and noticed that there is already some logic wired to the --python flag, which can (conservatively) decide to invalidate an environment:
https://github.com/astral-sh/uv/blob/23494d85ab7d416e7f746b28b1d5897e16b1b9ff/crates/uv/src/commands/tool/install.rs#L275-L292
If I understood the CLI logic correctly, it feels like the issue can be scoped back to "install-or-upgrade without explicit -p".
In that case, we may want to enhance the fallback case (hardcoded true in the logic above) to something smarter like:
settings.reinstall.is_none() ||
settings.upgrade.is_none() ||
(environment.interpreter().markers() == interpreter.markers())

I haven't seen better primitives to implement a more conservative comparison logic without comparing markers (e.g. based on a managed/system bit).
The heuristic above may be a bit overkill, but should definitely cover all possible cases.

environment.interpreter().markers() == interpreter.markers()

I think this wouldn't be quite enough, since the example use-case here is about managed vs. unmanaged Pythons which isn't captured in the markers.
I think we have two options: (1) always reset if the interpreter is different; or (2) upgrade python_request.satisfied to take the "preference" into account, such that we invalidate the environment if the user passes --python-preference only-managed but we used an unmanaged Python.
(2) is harder -- we don't really track whether the current Python is managed IIUC.

Seems easiest to just do (1) since it's already a new "install" invocation. If it was a more frequent operation, I'd be more concerned about invalidating too eagerly.

Makes sense, thanks for the feedback.
The whole Interpreter itself isn't Eq right now, but I think it can be made so.
Is the binary path (sys_executable) enough to compare to detect if it is the same interpreter (I think so), or is there some edge behavior that requires deep-comparing all of the fields below?
https://github.com/astral-sh/uv/blob/23494d85ab7d416e7f746b28b1d5897e16b1b9ff/crates/uv-python/src/interpreter.rs#L30-L50

For this purpose it seems fine to compare sys_executable. I'm not sure about a general Eq implementation, but @konstin would probably know.

Yeah I think you basically want is_same_executable from the satisfied check.


WebView created by browser shows httpgd viewer toolbar buttons

With the latest vscode-insider (1.58.0-insider), the toolbar of the WebView created by .vsc.browser() contains httpgd plot viewer toolbar buttons in addition to the original buttons.

.vsc.browser("https://<IP_ADDRESS>/test")

I cannot reproduce this with the latest insider build. Is there any specific sequence of opening/focussing webviews that causes the buttons to appear?
Version: 1.58.0-insider (user setup)
Commit: 7dea6d7402b55671410a129661cad24b55aed9f4
Date: 2021-06-18T13:58:43.903Z
Electron: 12.0.11
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041

The problem is gone with the latest insider build. Closing now.


Container-title isn't properly abbreviated (short) in Bibliography when using IEEE as the CSL template, for article-journal type

According to this section of the IEEE CSL template regarding the bibliography, article-journal types should have the container-title italicized and short.
        <!-- Specific Formats -->
        <if type="article-journal">
          <group delimiter=", ">
            <text macro="title"/>
            <text variable="container-title" font-style="italic" form="short"/>
            <text macro="locators"/>
            <text macro="page"/>
            <text macro="issued"/>
            <text macro="status"/>
          </group>

I found this CSL template for IEEE from zotero: https://www.zotero.org/styles/ieee  <-- That link downloads the .csl file for me,
and I searched for the Bibliography section

My example bibliography output is this however:
D. G. Tenen, L. Chai, and J. L. Tan, “Metabolic alterations and vulnerabilities in hepatocellular carcinoma,” Gastroenterology Report, vol. 9, no. 1, pp. 1–13, Nov. 2020, doi: 10.1093/gastro/goaa066.
The container-title "Gastroenterology Report" is italicized, but it's not abbreviated.
For the example, here is the CiteObject to json (with some of the irrelevant fields not included):
Wanted to highlight the type is "article-journal", and the container-title is "Gastroenterology Report."
{
  "publisher": "Oxford University Press (OUP)",
  "issue": "1",
  "DOI": "10.1093/gastro/goaa066",
  "type": "article-journal",
  "page": "1-13",
  "title": "Metabolic alterations and vulnerabilities in hepatocellular carcinoma",
  "prefix": "10.1093",
  "volume": "9",
  "author": [
    {
      "given": "Daniel G",
      "family": "Tenen",
      "sequence": "first",
    },
    etc.
  ],
  "member": "286",
  "published-online": {
    "date-parts": [
      [
        2020,
        11,
        18
      ]
    ]
  },
  "container-title": "Gastroenterology Report",
  "original-title": [],
  "language": "en",
  "score": 1,
  "resource": {
    "primary": {
      "URL": "https://academic.oup.com/gastro/article/9/1/1/5989815"
    }
  },
  "subtitle": [],
  "short-title": [],
  "issued": {
    "date-parts": [
      [
        2020,
        11,
        18
      ]
    ]
  },
  "journal-issue": {
    "issue": "1",
    "published-online": {
      "date-parts": [
        [
          2020,
          11,
          18
        ]
      ]
    },
    "published-print": {
      "date-parts": [
        [
          2021,
          3,
          16
        ]
      ]
    }
  },
  "URL": "http://dx.doi.org/10.1093/gastro/goaa066",
  "relation": {},
  "ISSN": [
    "2052-0034"
  ],
  "subject": [
    "Gastroenterology"
  ],
  "published": {
    "date-parts": [
      [
        2020,
        11,
        18
      ]
    ]
  },
  "id": "0SUohGRDV2"
}

Let me know if this example listed is helpful or if more information is needed.

It might be the case that citeproc-js cannot display the abbreviated container-title because that information is not available from the input data. As far as I know, citeproc-js does not (by default) abbreviate container titles, but does pick up the value of the container-title-short field (if available).


whitelist example

Added example how to whitelist a CROSS_ACCOUNT_ROLE violation.

:+1:

Codecov Report

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

@@            Coverage Diff            @@
##             master     #585   +/-   ##
=========================================
  Coverage     56.27%   56.27%
  Complexity      597      597
=========================================
  Files           151      151
  Lines          3385     3385
  Branches        222      222
=========================================
  Hits           1905     1905
  Misses         1395     1395
  Partials         85       85

Continue to review full report at Codecov.

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

:+1:


'react-native/no-unused-styles' rule don't always work

this snippet:
const styles = StyleSheet.create({ foo: {} });
const style = [ styles.foo ];
<View style={style} />;

triggers a 'react-native-no-unused-styles'
it looks like 'react-native/no-unused-styles' only works when you directly give it in the JSX. It shouldn't.

This is the repo/issue: https://github.com/Intellicode/eslint-plugin-react-native/issues/15

good point. thx


Plugin seems busted after Atom updated

atom-typescript 6.0.10
atom 1.0.13
Plugin was working great this morning but just restarted atom (looks like it updated) and now it's failing to load. Atom says it contains native modules compiled for an earlier version of Atom.
I tried uninstalling and installing again both through apm and within Atom. No luck.
When I try rebuilding in the app it shows this:
In file included from ../fsevents.cc:6:
In file included from ../node_modules/nan/nan.h:74:
In file included from ../node_modules/nan/nan_new.h:181:
../node_modules/nan/nan_implementation_12_inl.h:172:66: error: too many arguments to function call, expected at most 2, have 4
  return v8::Signature::New(v8::Isolate::GetCurrent(), receiver, argc, argv);
         ~~~~~~~~~~~~~~~~~~                                      ^~~~~~~~~~
/Users/rimig/.atom/.node-gyp/.node-gyp/0.30.6/deps/v8/include/v8.h:4515:3: note: 'New' declared here
  static Local<Signature> New(
  ^
1 error generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)

I just started using Atom and it's great, just need to straighten this issue out.

I lost patience after going deep into debugging what node-gyp was doing. I reinstalled Atom and the plugin and things are working now.


C3P0配置项 'checkoutTimeout' 单位为毫秒，无需转换

http://www.mchange.com/projects/c3p0/index.html#checkoutTimeout 这个配置项在C3P0中单位已经是毫秒，无需在转换成maxWait时做转换。

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.liangxf seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

Current coverage is 73.37% (diff: 100%)

Merging #1439 into master will decrease coverage by 0.01%

@@             master      #1439   diff @@
==========================================
  Files           835        835
  Lines         63468      63468
  Methods           0          0
  Messages          0          0
  Branches      11825      11825
==========================================
- Hits          46578      46568    -10
- Misses        12603      12613    +10
  Partials       4287       4287

Powered by Codecov. Last update 9481c8d...6e2c949


fix(Webhooks): Types for InteractiveWebhookMessageNfmReply

Using InteractiveWebhookMessageNfmReply is broken because the type unions are not being combined correctly.

// Works now:

const interactiveWebhookMessageNfmFlowReply: InteractiveWebhookMessageNfmReply<"flow"> = {
	body: "Sent",
	name: "flow",
	response_json: "..."
}

const interactiveWebhookMessageNfmAddressReply: InteractiveWebhookMessageNfmReply<"address_message"> = {
	// optional in this case
	body: "...",
	name: "address_message",
	response_json: "..."
}

const interactiveWebhookMessageNfmUnknownReply: InteractiveWebhookMessageNfmReply<"apparently-there-are-other-types"> = {
	// optional in this case
	body: "...",
	// optional in this case
	name: "apparently-there-are-other-types",
	response_json: "..."
}

Thanks @lukas-becker0 !


so = ath.dataset.imc_quickstart()

Hi,
I tried to load the example dataset, but got an error:
AttributeError: module 'athena.dataset' has no attribute 'imc_quickstart'
My installed Athena version is 0.1.2. DId I miss something?

Hi, sorry for my late replay, I was on holidays.
Yes my bad, I forgot to upload the latest version to pypi, after I created the quickstart.
Happy if you could try again, it should work now.
Best,
Adriano


Switch back to using our subgraph endpoint

What does this pull request do? Explain your changes. (required)
Switches us to our new self-hosted subgraph endpoint
Specific updates (required)
Updates the URLs in the explorer
How did you test each of these updates (required)
Tested the explorer locally, tested the subgraph extensively over last week
Does this pull request close any open issues?
Fixes #378

Confirmed inside GraphiQL the transcoders active field is being correctly indexed again. 👍 🚢


Remove remaining containerd fuzz and clean up build.sh

Fix https://github.com/containerd/containerd/issues/7066
Equivalent fuzz in upstream: https://github.com/containerd/containerd/blob/main/contrib/fuzz/containerd_import_fuzzer.go
Signed-off-by: Jin Dong<EMAIL_ADDRESS>

Thank you. LGTM. Could you change "Romve" to "Remove" in the title?

Do we need to fix this script? oss-fuzz's containerd Dockerfile no longer uses cncf-fuzzing.
https://github.com/google/oss-fuzz/blob/master/projects/containerd/Dockerfile

https://github.com/google/oss-fuzz/blob/master/projects/containerd/build.sh
Oh right... just saw the cncf-fuzzing build.sh is removed from oss-fuzz's build.sh. :) I must have seen some stale commit...
In that case, should I just remove both the remaining fuzzer and this build.sh, (or the whole containerd folder)?
Thanks.

I'm planning to port https://github.com/cncf/cncf-fuzzing/blob/main/projects/containerd/containerd_import_structured_fuzzer.go to containerd, without bringing the dependencies.

Do we need to fix this script? oss-fuzz's containerd Dockerfile no longer uses cncf-fuzzing.
https://github.com/google/oss-fuzz/blob/master/projects/containerd/Dockerfile

We can remove the whole folder instead like @djdongjin suggested.

@kzys I might miss something but does this one bring new dependency to containerd? Also, it seems identical with containerd_import_fuzzer.go in containerd except some syntax.
Thanks!

Is this one ready?


Fixed memory leak.

I was seeing ~200MB of memory leaking when generating PNGs from ~70 ANSi files (.ans, .xb). I did some poking around the libansilove source and this was my best guess at the fix. I don't have any experience with the codebase, so there may be a better way to fix this leak. In my limited testing this fixes the leak without any apparent side-effects.

Merged, thanks for reporting the issue. This is indeed the correct way to fix this.
I also added calls to gdImageDestroy() when generating Retina or DOS aspect ratio output.


bug: docs for plugin definition syntax missing attributes

I was reading https://docs.meltano.com/reference/plugin-definition-syntax and noticed that there are some attributes that are missing from the syntax list. We might not be wanting to list every possible option but a few are missing that are important, comparing against the hub schemas https://github.com/meltano/hub/tree/main/schemas/plugin_definitions:

executable
settings_group_validation
prereq
description
definition
etc. There might be more but thats what I saw from a quick skim

@pnadolny13 good catch. @edgarrmondragon @aaronsteers is there a way to automate validation of these docs with teh JSON schema  at some point in the future so that these don't drift?

is there a way to automate validation of these docs with teh JSON schema at some point in the future so that these don't drift?

@tayloramurphy There are no tools that I know of to do this easily that play well with Jekyll, but we could always just use templating + walking the JSON schema tree to generate the page.
Though, the schema for Hub plugin definitions lives in meltano/hub and it's split by plugin type so that makes it harder to use here in meltano/meltano. Also, my personal preference, since we usually edit those schema files by hand, would be for them to be written in yaml instead of json, since it's slightly more readable.

Still relevant though it looks like prereq is the only one missing.
Note you may want to update this when adding gold / silver / bronze @pnadolny13

Still relevant


Pulling script

This script pulls sim4life images (s4l-core-lite, sym-server-dy) to all GPUs node on the selected deploy. It is compatible with all current Osparc deploys.

The scrips has been merge in osparc-external (internal gitlab)


Class04

This took about 20 minutes, It was simple to implement into my portfolio after all the time I spent working with it during the lab


chore(deps): upgrade project dependencies

Upgrade all project dependencies except coverage.

:tada: This PR is included in version 1.0.1-rc.1 :tada:
The release is available on:

v1.0.1-rc.1
GitHub release

Your semantic-release bot :package::rocket:

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

v1.0.1
GitHub release

Your semantic-release bot :package::rocket:


Replace two HTTP logo URLs with HTTPS URLs

I noticed that every PR in this project fails the automated checks because of mixed HTTP/HTTPS content. This has apparently been an issue for a while. Upon closer inspection, the offending content is two logos: the logo for DASCutils and the logo for THEMISasi.
I decided to take executive action on this and host these two logos securely. This PR swaps the old HTTP URLs for new HTTPS ones, which will fix the automated checks for all our PRs. 👍

LGTM, Shawn. 👍


Sibling anonymous namespaces are incorrectly consolidated in MSVC programs

Describe the bug
When Ghidra reconstructs namespaces within MSVC programs, it gives each anonymous namespace the name of `anonymous namespace' (or something similar) within its parent namespace. Because each anonymous namespace is given the same name (within its namespace), when a namespace contains multiple anonymous namespaces, Ghidra incorrectly combines them into one anonymous namespace. If both anonymous namespaces contain classes of the same name, these may be incorrectly combined as well.
To Reproduce
Steps to reproduce the behavior:

Create a new project and import the attached example program (with the recommended settings).
Open the CodeBrowser on the newly-imported program.
Analyze the program with default settings. (You may get some warnings; these are not relevant to this issue AFAIK.)
In the symbol tree, navigate to Namespaces/`anonymous_namespace'/Example.
Observe that the recovered Example class has two RTTI type descriptors. Both type descriptors contain different strings, indicating that they belong to different classes, but are placed by Ghidra under the same class.

Expected behavior
Both anonymous namespaces and their Example classes would be separate from one another.
Attachments
See this ZIP file for an example program that can be analyzed to reproduce the issue alongside its source code files.
Environment:

OS: Windows 11 23H2 (22621.3737)
Java Version: 21.0.2
Ghidra Version: 11.1.1
Ghidra Origin: GitHub distro

Thanks for submitting this issue. I've seen this too and worked on part of it, but it slipped my mind to change the analyzer.  My plan is to just use the underlying anonymous namespace in the mangled symbol (e.g., A0x987654321).  The demangled string used for plate comments would still show the ````anonymous namespace'``` string, as that is what other demanglers, such as undname, show for the namespace and this helps with testing our underlying demangling model against them.

After digging in a little further, I think the issue here is another manifestation of what I had been seeing with the Demangler, but I think yours is something specific to PDB.  MSFT is outputting the `anonymous namespace' component of the namespace for both say_hello methods.  I'd have to dig into this further to see if I can figure out if I can find the explicit owner namespace/class, and if so, see if it has the explicit underlying anonymous notation (A0x987654321) in a mangled string.  If the mangled string is available, I'd prefer that so we have a universal answer whether coming from Demangler or PDB... if not, it could be possible to change the name to something that reflects which namespace/class.  This is an unknown amount of work and might come along slowly with other work in the pipeline that needs similar attention.

@Tkain I've been working on Demangler and PDB portions of this ticket in parallel. Likely will finish/merge Demangler portion first, which will make some analysis results look work until the PDB portion is done/merged. This ticket will get closed with the Demangler ticket.


Tag dropdown list style is not correct

Hi,
Thanks for creating the great theme!
BTW, I found a bug in it.
The style of the tag dropdown list looks not correct like this:

Can you please fix it?

Hey,
Thanks for the feedback. I've already fixed it!
Take care!

It worked! Thanks so much🙏✨


New Macstadium Pods for the New Datacenter [WIP]

WIP
What is the problem that this PR is trying to fix?
See https://github.com/travis-pro/team-blue/issues/736
We don't want to terraform-apply the existing macstadium-shared-* environments to the new datacenter.
What approach did you choose and why?
cp -r the macstadium-shared-* directories to macstadium-pod-* directories
How can you test this?
make plan , see if it works,
What feedback would you like, if any?

We have 1 additional SAN in each pod, so wondering if we need to declare a 2nd datastore variable for each env?
Document in README some of the workflow gotchas that come with having to use a 0.9.* release of terraform to get the vsphere provider that has been working for us. (Relevant to macstadium-* only envs)

@ryndaniels and I were able to do a successful make plan on both macstadium-pod-{1|2} with identical outputs.  We'd like to merge this without doing a make apply as we prefer to add more work to the hosts before applying, while keeping PRs separate and small/thematic.


Add -proto option to change the default protocol to clone with

This allows to switch between git:// and https:// but defaults
to git to stay compatible with current behaviour

Awesome, thanks!


Version v0.1.5 RC

:package: :rocket:

This change is

Builds ready [e773558]builds: chrome, firefox, opera
bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
dep viz: background
all artifactsPage Load Metrics (688 ± 83 ms)PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)ChromeNotificationfirstPaint58104741927domContentLoaded5787526866083load5797546886083domInteractive5777526866083


Require admin auth for new oracles

https://github.com/telosnetwork/telos-ping/blob/9cc546e773c5b9dffa91b3cc23fa1a6ed18e78f7/contracts/requestor/src/requestor.cpp#L86
this lets anyone become an oracle and can be exploited.  Maybe check oracle auth on modify path, and check admin auth on emplace path.

@tomtomcrypto would you mind double check if this is already in place and close it if it is?


{NICK} formatted in HTML in Telegram goes back to normal formatting after an Edit in Discord

Which version of matterbridge are you using?
Matterbridge v1.5.1
Please describe the expected behavior.
I'm using Discord <--> Telegram bridge only, don't know how this is on other bridges
After editing a message in Discord it should edit normally in Telegram without screwing the formatting of the Nicknames.
It should look like this after editing:

Please describe the actual behavior.
When a message is edited in Discord, the same message is edited in Telegram, this works fine.
But in my configuration file, I have:
(For Telegram)
MessageFormat="HTML"
and
RemoteNickFormat="{NICK}:\n"
So a sent message looks like this:

However, after editing, it looks like this:

Any steps to reproduce the behavior?
1- Add MessageFormat="HTML" to a Telegram protocol in the config file
2- In RemoteNickFormat= make use of HTML formatting
3- Run (Discord connected to Telegram)
4- Send a message in Discord (Check if it appeared on Telegram)
5- Edit that message in Discord (It should be edited on Telegram with the now non-HTML formatted nickname)
Please add your configuration file
###################################################################
#discord section
###################################################################
[discord]

[discord.server1]
Token="D_TOKEN1"
Server="Server1Name"
RemoteNickFormat="**{NICK}:** "
ShowEmbeds=true

[discord.server2]
Token="D_TOKEN2"
Server="Server2Name"
RemoteNickFormat="**{NICK}:** "
ShowEmbeds=true

###################################################################
#telegram section
###################################################################
[telegram]

[telegram.group1]
Token="T_TOKEN1"
MessageFormat="HTML"
RemoteNickFormat="{NICK}:\n"
UseFirstName=false

[telegram.group2]
Token="T_TOKEN2"
MessageFormat="HTML"
RemoteNickFormat="{NICK}:\n"
UseFirstName=false

###################################################################
#Gateway configuration
###################################################################

[[gateway]]
name="gateway1"
enable=true

[[gateway.inout]]
account="discord.server1"
channel="channel"

[[gateway.inout]]
account="telegram.group1"
channel="-123456789"

[[gateway]]
name="gateway2"
enable=true

[[gateway.inout]]
account="discord.server2"
channel="channel"

[[gateway.inout]]
account="telegram.group2"
channel="-123456789"

So, this also happens with normal messages that use HTML formatting as well.
If I send this message from discord:  HTML Formatting test
It shows up like:

As it should.
But then, after I edit it:

It shows up like that.

Should be fixed in master you can download a dev binary from https://bintray.com/42wim/nightly/Matterbridge/v1.5.0-13-gf561632#files
(I don't use telegram so I can't test it)

It works now! Great


[WIP] Add deploy cmd.

Currently the deploy were a default behavior under root command, and the manifest and deployment flag are global flags, we need to separate deploy/undeploy and corresponding
flags under each command. Add this issue to separate the refactor progress.

Let's keep the deploy command in root for now.  I remember now that wskdeploy deploy is awkward.  however, we should definitely have an undeploy command wskdeploy undeploy


Simplify MP JWT header and claim requirements

Fixes #128.
The goal of this PR is to improve/clarify the text around the required headers/claims and it will be followed up with a few more TCK tests once we agree on the final text.
Here is a summary of the problem. In the current text:

alg (and enc in case of the encrypted token), kid  and typ headers are required.
iat, exp, iss, one of upn/preferred_username/sub, jti claims are required in one place, iss - in the other place.

IMHO these are all very sound requirements but required must really be TCK enforced as it is important for some integrations that the spec requirements are enforced , but I suspect if we start enforcing it all  now we will break many user applications. So I've tried to find the middle ground. It is important that MP JWT has some position about some claims as opposed to making everything optional and accepting empty tokens. We can tighten things in MP JWT 2.0. So, in this PR:

Headers

Required: alg and in case of the encrypted tokens also enc - this is essential and can not be optional
Optional: kid - it is redundant unless JWK is used to verify the token. It really must be present  if JWK is used to verify but there is a border line case where only a single JWK is available without kid and can be used to verify the token without kid so I'd be a bit concerned with TCK enforcing that a kid header is present in such cases. Perhaps we can tighten it up for MP JWT 2.0
Optional: typ it does not add any security information so it is a good practice to have it but I think it is fine to make it optional

Claims

iat and exp are still required - it simply does not make sense to accept the unlimited lifetime tokens (if no exp is available),  and also very risky to accept the tokens without iat (was it issued 5 years ago ? who knows...), every OIDC issuer will set it and it is straightforward to set for the self-issuing clients. Sometimes users don't want to set exp to make things easier to test, let then set a max long number, but at least with the iat requirement the implementations will have a chance to block the tokens which have been around forever... There is no practical reason for a token not to have iat and/or exp
iss - this is required, without it the services simply have no idea who posted it, this is a fundamental JWT verification requirement. Again, every OIDC server will set it, and any self-issuing client can set it to something random.
a principal must be available in the token (upn, or preferred_username or sub) - without it Java Principal getName will return nothing and the spec just can't allow it. Perhaps I should add a line suggesting the name can be optionally deduced from the other claims if none of these 3 claims is available.
Optional: sub - (unless it is required as a name fallback), it is a number most of the time
Opitonal: jti - this one should really be required but it can be enforced for Mp JWT 2.0 with TCK, as I'm not 100% sure if all the OIDC servers set it (the self-issuing clients can set it without problems)

Missing Iss tests - I've removed them because I don't understand what they actually test, specifically the test where a token iss does not match a configured issuer seems just incorrect.

@rdebusscher, @starksm64, @radcortez @darranl, others, comments are welcome :-)

Or, another option, just leave it as is until MP JWT 2.0 and TCK enforce the required claims then

I'm going to open for review since we need to agree on a decision quickly enough. As I said I will add a few more TCK updates once the text is agreed upon

@radcortez It is still not possible to request your review. Also CC @darranl, others

Hi All, just to would to summarize again why some headers/claims are made optional with this PR:
Headers:
typ:: MP JWT only expects JWT. Given that JWT is basically just JSON where any top level element is a `claim`, having `typ` does not add to the security of the token - it is recommended to set this header to keep to keep indicating that well, it is not just random JSON but was created by the OIDC server or self-issuing client which did mean to issue JWT.
kid:: Mainly effective with the multi-key JWK set - and even in this case I'm not seeing the users requiring the use the certificate thumbprint `x5t` as an alternative

Claims:
sub:: It is supposed to be a unique number so it is not something that would be useful to return to the human user as part of the UI interaction and it is really of interest to the OIDC server introspecting the token, not much can be done about it during the local verification. It is only required as a fallback when no `upn` or `preferred_username` is available
jti:: hard to enforce it at the MP JWT spec level beyong just checking it exists - enforcing the replay constraints is better be left to the OIDC server or the custom local implementation. Perhaps we can do some general recommendations going forward.
aud:: I'd have no problems with enforcing it but setting it correctly is a bit harder for the self-issuing clients, and not all OIDC issued tokens may have them, so for now it is optional

@sberyozkin I'm have permissions now, so I added myself as a reviewer :)

@radcortez @rdebusscher @teddyjtorres
I have added 3 TCK tests and this is probably enough for now.

401 is expected if no exp is available
401 is expected if iat is older than exp (Teddy, as per our discussion, before the age property is introduced)
401 is expected if the token has no name available

Hey @radcortez, thanks, I'm going to verify TCK tests before merging.
@rdebusscher Rudy, any concerns - just ping us please :-).

The added TCK tests have been verified, merging shortly


Set proper maxAge headers for /static files

Files in the /static dir seem to not have the proper expire headers. They serve as "max-age=0".
The user's browser does a request to static files on each page load, which is not best practice. Also, services like CloudFlare won't pick up on those files and so you miss their CDN capabilities.
This PR fixes that.

Codecov Report

Merging #755 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #755   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          13     13
  Lines         567    567
=====================================
  Hits          567    567

Impacted Files
Coverage Δ

lib/nuxt.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Hi @jvandenaardweg
Thanks for the PR, I talked with @pi0 and this default option seems more problematic since the filenames won't change if the content is changes.
serverStatic already offers ETAG headers to send back 304 response.
We will add an option render.static to allow the user to give parameters for serverStatic middleware.

Sounds perfect!
Temporary using this as a workaround. Might be of help for others.
app.get('*', (req, res, next) => {
  // Manually set proper expire headers for fonts
  if (req.url.includes('/fonts/') || req.url.includes('/images/') || req.url.includes('manifest.json')) {
    res.setHeader('Cache-Control', 'public, max-age=' + cacheTime)
  }

  next()
})

etag is better cache static fIle solution , you should try .

@ausir0726 etag is also enabled by default with serve-static :)

@pi yes, I saw your push yesterday . thank you .

@ausir0726  will look into etag, thanks for the tip!


Update consensus logs and make sure to await the build handle. WIP

This change is

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

#2929  👈 (View in Graphite)
#2891
#2876
#2873
main

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


fix: package issue with focus-trap causing jest test failure

Description
tabbable package does not support js-dom and that's why the tests for our ColorPickerV2 component were failing. This PR make sure that we make use of version 5.2.1 of tabbale package which is found to be compatible with our tests.
Fixes #13555
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manually

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/colorpicker-tests

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
56.56 (0.07)
38.26 (0.28)
35.91 (0.05)
56.8 (0.07)

:green_circle:
app/client/src/components/ads/ColorPickerComponentV2.tsx
78.85 (26.29)
72.14 (49.25)
75 (18.75)
78.77 (27.4)

:red_circle:
app/client/src/utils/WorkerUtil.ts
88.98 (-0.78)
70.59 (0)
100 (0)
92.38 (-0.95)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.71 (-0.23)
40.83 (-0.84)
36.21 (0)
56.74 (-0.25)

/ok-to-test sha=c03cc6e

/ok-to-test sha=f3eb7f6


support node:module and createRequire

https://nodejs.org/api/module.html#modulecreaterequirefilename
Many third-party libraries use this API to read version information, but require cannot be optimized by the bundler
import { createRequire } from 'node:module';
const require = createRequire(import.meta.url);

const { version }= require("./package.json")

console.log(version)

This simple implementation should cover most scenarios, but it is better to refer to the implementation of node and deno
export function createRequire(){
  return globalThis.require
}

require is a very common global function, and could probably be added to llrt_module as well.

This is already implemented: https://github.com/awslabs/llrt/blob/a161f394391b396aaa6980053de1da1acccf886a/llrt_core/src/modules/module.rs#L20

It seems to be a problem caused by path processing on Windows
pub fn join_path(parts: Vec<String>) -> String {
    let mut result = PathBuf::new();
    let mut empty = true;
    for part in parts.iter() {
        if part.starts_with(MAIN_SEPARATOR) && empty {


support position_ids  as input for fa

It seems like we need to add patch for position_ids

done. btw, in transformers version >= v4.47.0, model_flash_attention_utils._flash_attention_forward has changed its interface and add five params, but it seems old patch can still work. maybe need to change in the future.
new interface
def _flash_attention_forward(
    query_states: torch.Tensor,
    key_states: torch.Tensor,
    value_states: torch.Tensor,
    attention_mask: torch.Tensor,
    query_length: int,
    is_causal: bool,
    dropout: float = 0.0,
    position_ids: Optional[torch.Tensor] = None,
    softmax_scale: Optional[float] = None,
    sliding_window: Optional[int] = None,
    use_top_left_mask: bool = False,
    softcap: Optional[float] = None,
    deterministic: bool = None,
    cu_seq_lens_q: Optional[torch.LongTensor] = None, # support passing fa params directly
    cu_seq_lens_k: Optional[torch.LongTensor] = None,
    max_length_q: Optional[int] = None,
    max_length_k: Optional[int] = None,
    target_dtype: Optional[torch.dtype] = None, # use for type conversion for peft
):

old interface
def _flash_attention_forward(
    query_states: torch.Tensor,
    key_states: torch.Tensor,
    value_states: torch.Tensor,
    attention_mask: torch.Tensor,
    query_length: int,
    is_causal: bool,
    dropout: float = 0.0,
    position_ids: Optional[torch.Tensor] = None,
    softmax_scale: Optional[float] = None,
    sliding_window: Optional[int] = None,
    use_top_left_mask: bool = False,
    softcap: Optional[float] = None,
    deterministic: bool = None,
):


Refactor core/[data,metadata,export]/init.go to combine duplicated code

What caught my attention was the database bootstrap code but there could be other. Post Delhi, of course.

I would like some improvement in this area as well. It's a challenge because of two things:
1.) There's no base class from which we could derive a service's implementation. Usually the base class would contain the DRY logic leveraged by the service instance.
2.) In some cases, there is coupling to specific types that prevents re-use without generics.
I'm open to ideas.

Closing due to inactivity.


Add support for whitespace inside build args

Utilise a bash array to expand the parameters correctly for the img command.
We've been facing an issue where if we have a build argument that contains whitespace, img will think the second word is the context.
$ build_args="--build-arg VAR=some var"
$ img build --no-console -t image:latest $build_args .
...
failed to solve: failed to resolve dockerfile: error from sender: failed to resolve : lstat var: no such file or directory

Changing to a bash array allows us to do parameter expansion:
$ build_args=( '--build-arg' 'VAR=some var' )
$ img build --no-console -t image:latest "${build_args[@]}" .
# builds as expected with `VAR` set to `some var`

makes sense! would you mind signing the commit to make the DCO bot happy?: https://github.com/concourse/builder-task/pull/23/checks?check_run_id=126348364

Hi @vito, I've rebased the PR to signoff the commits.
I've also fixed whitespace when using build_args_file.
This introduce a small behaviour change, so BUILD_ARG_* and BUILD_ARGS_FILE can be used at the same time.
Let me know if I should change it back to the previous behaviour where BUILD_ARG_* is ignored when BUILD_ARS_FILE is set


should check the availability of DevModeHandler for prod mode check in LaunchUtil

In LaunchUtil, it's calling the method from DevModeHandler directly, but it could happen that DevModeHandler is not in the classpath, e.g. vaadin-dev-server is excluded from the production profile.
Seems sth like below would make it work.
try {
    Class.forName("com.vaadin.flow.server.DevModeHandler");
    return DevModeHandler.getDevModeHandler() == null;
} catch (ClassNotFoundException e) {
    return false;
}

This has been fixed


Feature/atexit shutdown

Added atexit callback to BasePlanner which will attempt to gracefully shutdown upon unexpected exit.
It is off by default and can be turned on by setting shutdown_at_exit parameter to true.

Sweet cheers!


Atlassian c2c Source

Purpose of this pull request
This pull request is to create source doc for our new Atlassian C2C source.
Select the type of change

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions, updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)
C2C - Atlassian - Update Docs

Converting this PR to draft as we are still unsure about the release date of this source.

@JV0812, I added this new source to the product list (see commit "Add Atlassian Source to product list").


MWPW-136802: CaaS Configurator UI controls update

This PR adds some minor css tweaks to the CaaS Configurator tool.
It also resolves the issue reported on Jira ticket  MWPW-131760 where the max-height of the accordion is limiting the number of elements an author can add.
Resolves: MWPW-131760 & MWPW-136802
Test URLs:

Before: Content as a Service - Thursday, August 3, 2023 at 15:24 (no-lazy) (See filters panel)
After: https://ui-controls-update--milo--adobecom.hlx.page/?martech=off

There are still some linting issues, please check, thx.

There are still some linting issues, please check, thx.

Looks like the lint error is unrelated to this PR changes:
Check failure on line 71 in libs/ui/controls/formControls.js

GitHub
Actions
/ Running eslint

[eslint] reported by reviewdog 🐶
Unary operator '++' used.


docs validation fixes

and when this gets cherry-picked, we need to remmember to add an alias in the daemon.md file to create a dockerd.md redirect.
@thaJeztah

LGTM, thanks!


SPFX Teams app blank screen when you open it for second time

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[X] other (enter in the "Additional environment details" area below)

Additional environment details
browser version Teams desktop App
SPFx version 1.13
Node.js version V 12.13
etc
Describe the bug / error
When you load your custom sfpx teams app for second time after clicking in any other section in teams it doesn't load up and it shows white screen.
After digging in the developer tools i've seen this error

Steps to reproduce
You have a custom spfx teams app ,   you click on the app and it's loads fine

Later you click in any option in the menu like calendar ,  teams chat

You click in teams app again and then it show up white screen

Expected behavior
The app it works fine without taking in count where do you click or if you want to return to the app after doing any other action.

more information regarding the error

We are using custom app manifest following this guideline
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/deployment-spfx-teams-solutions#developer-provided-microsoft-teams-app-manifest--package
Here the url under it  https://xxx.sharepoint.com/_layouts/15/teamslogon.aspx?spfx=true&dest=/SitePages/Viva-Home.aspx?app=portals

Hi @Rtoribiog - thanks for reporting this one.
Could you please share your custom manifest either here or you can send it to me<EMAIL_ADDRESS>

you have it in the email.  Thanks

Thank you @Rtoribiog!
I don't see ?app=portals in your manifest.
Are you saying it is added when navigating back to the app?
Also, the manifest is not completely correct. As pointed out in the article you've mentioned, in webApplicationInfo you should set resource as https://{teamSiteDomain}, not the actual domain name.
Could you please also update the manifest and test it again?
Thanks!

hello @AJIXuMuK ,  sorry my fault,  i've sent you old version of the app.   Because all the things you mentioned were fixed some time ago.  I sent you current version by email again.  Thanks

hello @AJIXuMuK ,  have you seen anything that can be wrong or it's a bug as i'm thinking.  Adding also @GrahamMcMynn to the thread, maybe he knows what is going on.  Thanks

Hey @Rtoribiog - we're looking into it and will update the thread as soon as have further details.

@Rtoribiog - this has been fixed and will be rolled out WW in the next couple of weeks.

thanks so much

hello @AJIXuMuK , the deployment to teams app was released week ago. But still is not working properlly.  Now when you click again in the app open the browser of the url instead of open the app inside teams.
Attached screenshot with the problem , feel free to reach me for more info

That seems to be a separate bug.
I will create a new one to track it properly.


When use the SD1.5 adapter, an error occurs.

ValueError: A dict of processors was passed, but the number of processors 0 does not match the number of attention layers: 32. Please make sure to pass 32 processor classes.

Can you provide more detailed information? Such as, config file.

I just ran the example code as follows:
import os
import torch
from diffusers import AutoPipelineForText2Image, DPMSolverMultistepScheduler
from resadapter.model_loader import load_resadapter_mini

model_path = "/media/ssd8T/cxn/hugging_face_models/stable-diffusion-v1-5"
resadapter_path = "models/res_adapter/sd1.5-i"

prompt = "cinematic film still, photo of a girl, cyberpunk, neonpunk, headset, city at night, sony fe 12-24mm f/2.8 gm, close up, 32k uhd, wallpaper, analog film grain, SONY headset"
n_prompt = "ugly, deformed, noisy, blurry, nsfw, low contrast, text, BadDream, 3d, cgi, render, fake, anime, open mouth, big forehead, long neck"

# load baseline pipeline
pipe = AutoPipelineForText2Image.from_pretrained(model_path, torch_dtype=torch.float16, variant="fp16")
pipe.scheduler = DPMSolverMultistepScheduler.from_config(pipe.scheduler.config, use_karras_sigmas=True, algorithm_type="sde-dpmsolver++")
pipe = pipe.to("cuda")

# inference baseline
width, height =512, 512 # for sdxl-based model, 512x512 represent resolution interpolation
image = pipe(prompt, negative_prompt=n_prompt, width=width, height=height, num_inference_steps=25).images[0]
image.save("./image_baseline.png")

# load resadapter for baseline pipeline
pipe = load_resadapter_mini(pipe, resadapter_path)

# inference resadapter
image = pipe(prompt, negative_prompt=n_prompt, width=width, height=height, num_inference_steps=25).images[0]
image.save("./image_resadapter.png")

Thanks! The problem was solved after the environment was upgraded.

Actually，we recommend you generate lower-resolution image with only resolution_lora. We will delete resolution norm in lower-resolution image generation.


use Library as DB path on ios

In the Last PR i used tag v2.1.2 as base for my 'fix', now its up to date with your master.

Nice. Many thanks. Merged


Scripts to support Issue #2457

Fixes:

https://github.com/digitalocean/netbox/issues/2457

Please see my comments on #2457.


Failing to build torch-sys-0.1.17 on Ubuntu (16.04) (CUDA)

I have installed Anaconda and then built libtorch (1.15.0) from source using the instructions provided here.
But now my rust project encounters the following error while building :
error: failed to run custom build command for `torch-sys v0.1.7`

Caused by:
  process didn't exit successfully: `/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-9793dd7018dbafc8/build-script-build` (exit code: 1)
--- stdout
cargo:rustc-link-search=native=/home/ubuntu/anaconda3/lib
TARGET = Some("x86_64-unknown-linux-gnu")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-unknown-linux-gnu")
CXX_x86_64-unknown-linux-gnu = None
CXX_x86_64_unknown_linux_gnu = None
HOST_CXX = None
CXX = None
CXXFLAGS_x86_64-unknown-linux-gnu = None
CXXFLAGS_x86_64_unknown_linux_gnu = None
HOST_CXXFLAGS = None
CXXFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/home/ubuntu/anaconda3/include" "-I" "/home/ubuntu/anaconda3/include/torch/csrc/api/include" "-Wl,-rpath=/home/ubuntu/anaconda3/lib" "-std=c++14" "-D_GLIBCXX_USE_CXX11_ABI=1" "-o" "/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-448e51ef5f47d1fc/out/libtch/torch_api.o" "-c" "libtch/torch_api.cpp"
cargo:warning=libtch/torch_api.cpp:1:39: fatal error: torch/csrc/autograd/engine.h: No such file or directory
cargo:warning=compilation terminated.
exit code: 1
running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/home/ubuntu/anaconda3/include" "-I" "/home/ubuntu/anaconda3/include/torch/csrc/api/include" "-Wl,-rpath=/home/ubuntu/anaconda3/lib" "-std=c++14" "-D_GLIBCXX_USE_CXX11_ABI=1" "-o" "/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-448e51ef5f47d1fc/out/libtch/fake_cuda_dependency.o" "-c" "libtch/fake_cuda_dependency.cpp"
exit code: 0

--- stderr
/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-9793dd7018dbafc8/build-script-build: /home/ubuntu/anaconda3/lib/libcurl.so.4: no version information available (required by /home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-9793dd7018dbafc8/build-script-build)

error occurred: Command "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/home/ubuntu/anaconda3/include" "-I" "/home/ubuntu/anaconda3/include/torch/csrc/api/include" "-Wl,-rpath=/home/ubuntu/anaconda3/lib" "-std=c++14" "-D_GLIBCXX_USE_CXX11_ABI=1" "-o" "/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-448e51ef5f47d1fc/out/libtch/torch_api.o" "-c" "libtch/torch_api.cpp" with args "c++" did not execute successfully (status code exit code: 1).

warning: build failed, waiting for other jobs to finish...
error: build failed

Any idea what the issue is?

Did you follow the steps from the readme and set LIBTORCH to where the libtorch directory that you're building is?
Looking at the error message, some libtorch header cannot be found so it may be that this LIBTORCH is not set properly as it tells cargo/the c++ compiler where to find the header.

@LaurentMazare thanks for the swift reply.
Yes I suspected that so I double checked and it turns out there was a path error. Now I located the libtorch_cuda.so file along with others. So it turns out they're in a build (and then subdirectory lib) folder under the pytorch folder (pytorch repo cloned from GitHub to build from source).
So I've correct it and updated my LD_LIBRARY_PATH to include /home/ubuntu/source_repos/pytorch/build/lib
I did a cargo clean and attempted the cargo run again
I still get a similar error :
error: failed to run custom build command for `torch-sys v0.1.7`

Caused by:
  process didn't exit successfully: `/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-9793dd7018dbafc8/build-script-build` (exit code: 1)
--- stdout
cargo:rustc-link-search=native=/home/ubuntu/source_repos/pytorch/build/lib
TARGET = Some("x86_64-unknown-linux-gnu")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-unknown-linux-gnu")
CXX_x86_64-unknown-linux-gnu = None
CXX_x86_64_unknown_linux_gnu = None
HOST_CXX = None
CXX = None
CXXFLAGS_x86_64-unknown-linux-gnu = None
CXXFLAGS_x86_64_unknown_linux_gnu = None
HOST_CXXFLAGS = None
CXXFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/home/ubuntu/source_repos/pytorch/build/include" "-I" "/home/ubuntu/source_repos/pytorch/build/include/torch/csrc/api/include" "-Wl,-rpath=/home/ubuntu/source_repos/pytorch/build/lib" "-std=c++14" "-D_GLIBCXX_USE_CXX11_ABI=1" "-o" "/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-448e51ef5f47d1fc/out/libtch/torch_api.o" "-c" "libtch/torch_api.cpp"
cargo:warning=libtch/torch_api.cpp:1:39: fatal error: torch/csrc/autograd/engine.h: No such file or directory
cargo:warning=compilation terminated.
exit code: 1
running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/home/ubuntu/source_repos/pytorch/build/include" "-I" "/home/ubuntu/source_repos/pytorch/build/include/torch/csrc/api/include" "-Wl,-rpath=/home/ubuntu/source_repos/pytorch/build/lib" "-std=c++14" "-D_GLIBCXX_USE_CXX11_ABI=1" "-o" "/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-448e51ef5f47d1fc/out/libtch/dummy_cuda_dependency.o" "-c" "libtch/dummy_cuda_dependency.cpp"
exit code: 0

--- stderr

error occurred: Command "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/home/ubuntu/source_repos/pytorch/build/include" "-I" "/home/ubuntu/source_repos/pytorch/build/include/torch/csrc/api/include" "-Wl,-rpath=/home/ubuntu/source_repos/pytorch/build/lib" "-std=c++14" "-D_GLIBCXX_USE_CXX11_ABI=1" "-o" "/home/ubuntu/rust-foodScoring-tf-inference/target/debug/build/torch-sys-448e51ef5f47d1fc/out/libtch/torch_api.o" "-c" "libtch/torch_api.cpp" with args "c++" did not execute successfully (status code exit code: 1).

It seems to be referring to paths that don't exist like /home/ubuntu/source_repos/pytorch/build/include/torch/csrc/api/include
I checked the .../pytorch/build/include/ folder and it only contains : c10d  sleef.h

I'm not sure what this build directory is. When compiling from source, I always got lib in my pytorch directory.
Does pytorch/include exists and contains the file that the compiler complains about ? (this would be something like pytorch/include/torch/csrc/autograd/engine.h)
If that's the case maybe you just want to set LIBTORCH to the actual pytorch directory and move lib outside of build.

Okay I found the files. So the correct directory was .../pytorch/torch and that contains all the stuff needed. It built successfully now. Thanks for the help.
There's another question I wanted to ask you but instead of opening another ticket (unless you would prefer that) :
Have you tried or know about running model inference in parallel using tch-rs? I have around 4 models and the total time taken to run inference for a Tensor (of a single image) is almost 400ms.
Do you think using threads via std library or crossbeam or using rayon would help?

Glad that it ended up working.
I haven't run multiple inferences in parallel. If the model tensors are all disjoints that should be fine though. Speed improvement would certainly depend on the percentage of the gpu that your models get to use, if each of them is able to use most of the gpu, there probably won't be much of a speedup. Using threads or rayon sounds reasonable (I don't have experience with crossbeam). Note that I never tried it so it may be the case that the pytorch api is not thread-safe and you'll run into some segfaults/weird behavior.

Thanks a lot, I'll probably try this and get back with some results by next week :)


'http.get' timeout parameter

Closes #648
Add the new timeout parameter on the experimental http.get() function.

[x] Tests pass (no build errors)
[x] Rebased/mergeable

@nisley That change was already made. It's in the description at the top of this doc. If you expand the diff, you can see it. It wasn't changed in this PR so it's not showing in the default diff.


Please invite me to the GitHub Community Organization

Name
Shivansh Yadav
Discord Username (if applicable)
Shivansh Yadav#6952
Additional Context
I got to know about this amazing ⭐ organization from the commclassroom discord server, I am new to Open Source 🤓 and EddieHubCommunity is where I made my first few pull requests.
What do I like about the community ?

The EddieHubCommunity is so welcoming 🙋♂.
Super friendly with everyone 🙂.
Made it easier for me to start my open source journey 👨💻.
Super helpful people 👬.

I started my open source journey with EddieHubCommunity, I would like to continue contributing and stay with this community.

Welcome to the community!


path.resolve cannot resolve a null path

changed the uri from null to empty string due to the fact the path.resolve can't resolve a null path.

Coverage remained the same at 93.293% when pulling 82fd36d15c7f9f3159efb8a49c2897727dac26f6 on 0x4139:master into 24180416be9c2b8242a4f472b932e9c560a36e99 on vpulim:master.

I'm fine with this.  How about you @herom ?


Datasets for replication?

Hi,
I'm interested in trying your framework + replicating your results (especially on the second, "long range" dataset you added). Where is the data available? (Both yours and the Troyanskaya dataset).
Thanks!

Hi, thanks for reaching out. I am working on posting the data and some easy data accessors now to make replication easier. In the meantime, you can find the Zhou and Troyanskaya dataset at http://deepsea.princeton.edu/help/

Hi, I'm also interested in replicating the results on the Zhou and Troyanskaya dataset - but haven't been able to figure out either from the paper or the code (which as far as I can tell only defines models for the sequence labelling dataset) the details of the best performing dilated 6 architecture?


prettify the vendor information

show on which network the vendor was found (the ASN) and the timestamp
also find some more information about them

@hellais I added a data folder where I've added a placeholder object for Squid. I don't know much about the vendors, but am happy to fill in some data if I know where to look.

This is sufficient for the moment.


Player.selectFeatures does nothing

when the api calls Player.selectFeatures, no new entries in the database are made, the streak is not increased and no points are added to the player.
Also there is no exception thrown, neither in the tomcat log nor in the response from tomcat.

Steps to reproduce:

create game as organiser
play game as player and see that neither the streak nor the score has been increased

`     * Calling this method means to actually play the active round and retrieving a score.
* @param selectedFeatures Features the player has selected for this round
* @param uselessFeatures Features the player marked as unimportant
* @return Integer representing score
*/
public void selectFeatures(int[] selectedFeatures, int[] uselessFeatures) {
activeRound.selectFeatures(selectedFeatures, uselessFeatures);
public int selectFeatures(int[] selectedFeatures, int[] uselessFeatures) {
return activeRound.selectFeatures(selectedFeatures, uselessFeatures);
}
/**`

Player.selectFeatures now returns score

#27

Working on request #27

playround now returns -1

Found an issue and pushed a fix, please try again.
Related question: if there are no useless features selected, does the method call include an empty array or null as a parameter?

empty array

points are now returned, but it takes quite long
the playerStats table is updated, but in the game database no new round entries are made

Entries should now be created, please verify

rounds are now entered into the database


Update odata.org to HTTPS

Updating resource links to use HTTPS
Addressing git warning regarding pointers in the assets folder

Not sure what git warning is related to the assert folder. Git does not keep track of folders AFAIK. Is that the  reason for changes related to the png files? No changes for the binary files themselve, right?

As soon as you clone from master branch in the repo, you get a message regarding pointers. I am not able to perform git checkout -- assets and the change is still there.

Did you clone from master prior to the merge?
https://github.com/OData/odataorg.github.io/tree/2fc865c64846331606ed22245174f132f8655d87
I cloned from the commit prior to the merge and the messages shows up still.


row fails to update, LastInsertId is 0, no panic or error - mysql

I currently have a failing test despite receiving no error information.
I'm calling s.DB.MustExec like this:
res := s.DB.MustExec(
    "UPDATE readings SET readings.reading_date = ? WHERE readings.reading_id = ?",
    "test",
    51881,
)

Despite it not panicking (implying there is no error), my test was failing because I immediately retrieve the updated record afterwards to check that it has in fact been updated
res, err := s.DB.QueryRowx(
   "SELECT * from readings WHERE readings.reading_id = ?",
   51881,
)

but it is not updated. I have no idea how to debug this since MustExec does not panic and Exec returns no error, but the update is clearly failing to apply for whatever reason. For further confirmation, if I call res.LastInsertId() after calling Exec or MustExec I get 0 instead of the expected ID (51881).
Any idea why this is happening or how I can go about debugging this? Thanks

In hindsight the solution was obvious, I should not have been using a date field for my test


Fix Fast MGC, Add Demo Notebooks

Pull Request Test Coverage Report for Build 244

15 of 15 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.596%

Totals

Change from base Build 241:
0.0%

Covered Lines:
1192

Relevant Lines:
1234

💛  - Coveralls


Letter_Combination_of_a_Phone_Number.java

Issue Id you have worked upon -
Leetcode-17 Letter Combination of a Phone Number
Briefly explain your program logic -
	 ""                   [ "" ]
	  |
	 3 , 3                [d,e,f]
	  |
	23 , 2               a[d,e,f] + b[d,e,f] + c[d,e,f] -- > [ad,ae,af,bd,be,bf,cd,ce,cf]

Here, "23" is the input string , we will take out 2 and pass the remaining string i,e "3", then we will take out 3 and pass remaining string i,e, "" . (Then this will hit the base case and will return the ArrayList containing empty string) ( As Shown Above)
Now, it will make combinations of characters of 3 with returned Arraylist and so no. (As done in code)
Screenshots(Attach 2 screenshots of your own input and output) -

All the conditions should be fulfilled for considering your code for merging -
[] I have mentioned the question as comment in my solution file.
[] My code follows the guidelines of this project.
[] I have performed a self-review of my own code.
[] I have commented my code.
[] My code gives the correct output.
[] I confirm that I have not copied the code from anywhere. In case its found that I have copied I can be banned from the repository.
[] I affirm that I strictly follow contributing guidelines and code of conduct.

@Raghavarora27,
This PR will be marked as invalid by 08/10/2021(6PM). Kindly respond by either closing it or making the required changes

@SarthakKeshari  Done !! I have opened the new issue and waiting for you to assign me that


java.lang.NullPointerException in DrawableContainer.java:884

Error in mSupply Mobile
java.lang.NullPointerException in DrawableContainer.java:884
Attempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)' on a null object reference
View on Bugsnag
Stacktrace
DrawableContainer.java:884 - android.graphics.drawable.DrawableContainer$DrawableContainerState.getChild

View full stacktrace
Created automatically via Bugsnag

Spinner? Navigation?

Closed several similar issues throughout different versions. Going to be hard without a source map in bugsnag. Might be RN issue.


React 16 update

This package requires a peer of<EMAIL_ADDRESS>but react 16 was released.
I saw that it was updated in react-burger-menu but not in this one.
Do you plan any update ?
Thanks for your work,

Done (update in 0.2.3). Thanks for reporting, and sorry for the delay :)


Transitive dependency on es5-ext causes socket.dev / snyk errors

What is the current behavior?
Currently due to websocket having a dependency on es5-ext the deepgram package is causing failures in builds that rely on socket.dev and snyk for dependency scanning.
The issues is that es5-ext publishes protest banners. I have zero interest in the politics, but from my perspective it's a breach of trust that makes it a supply chain risk.
Steps to reproduce
Run a build with socket.dev.

See https://socket.dev/npm/package/@deepgram/sdk
Expected behavior
No critical errors.
Fixes
This can be resolved by adding this to your package.json:
  "resolutions": {
    "es5-ext": "0.10.53"
  },

Wow, thanks. I'll review this first thing and get a patch out
We have a draft PR for removing that websocket library, should be released as 3.4.x this week

release for this and another vuln just pushed out


Add link on opendata.bosa.be to oSoc

Create a link to this osoc repo on the opendata.bosa.be website

Added a link to github and osoc project page on opendata.bosa.be


check for 'empty' ticket updates

If the user pushes the 'update this ticket' button we should check whether any new information has been supplied or whether anything about the ticket has changed. Otherwise new users tend to spam the system with empty updates while 'trying things out'.

fixed in https://github.com/kotowicz/django-helpdesk/commit/11283741a23d6a1f31c3d4f14af45f3907640642


is it support to both android and ios ?

is it support to both android and ios ?

MapView.setApiKey("google_map_key");
which api key to add ?
android api key or ios ?

Did you find a way to provide both keys?

Sorry for that, I just updated the README
You need a Web API key. Here
And Android or iOS API key won't work.


Blazor Support

First of all, thank you for this amazing search tool.
My question is, is Blazor going to be supported like meilisearch-blazor ?
Thank you.

Hello @ahmetkocadogan
I moved your issue into the right repo! I let @brunoocasali answer to this question :)


az resource show fails for Azure Compute Gallery image versions with API 2022-01-03

Describe the bug
az resource show --ids /subscriptions/<sub>/resourceGroups/<rg>/providers/Microsoft.Compute/galleries/<gal>/images/<name>/versions/<version> fails with error:
(InvalidParameter) The value of parameter api-version is invalid.
Code: InvalidParameter
Message: The value of parameter api-version is invalid.
Target: api-version
Inner error: {
    "internalErrorCode": "ParameterValueInvalid"
}

Same error is returned if --api-version 2022-01-03 explicitly specified. The command works as expected with --api-version 2021-10-01.
To Reproduce
Run command az resource show --ids /subscriptions/<sub>/resourceGroups/<rg>/providers/Microsoft.Compute/galleries/<gal>/images/<name>/versions/<version>
Expected behavior
The resource JSON is returned.
Environment summary

Azure Cloud Shell:
azure-cli                         2.34.1

core                              2.34.1
telemetry                          1.0.6

Extensions:
azure-devops                      0.18.0
ai-examples                        0.2.5
ssh                                1.0.0

Dependencies:
msal                              1.16.0
azure-mgmt-resource               20.0.0

ARM

This should be a service related issue. @kangsun-ctrl Do you know who can help us investigate this issue?

@stefanes Can you please try upgrading to latest version of azure CLI? Its working for me with both versions of API 2021-10-01 and 2022-01-03 and without explicitly specifying the versions too. I am using 2.35.0 and the latest is 2.36.0

I can confirm this now seems to work with the Azure CLI version in Azure Cloud Shell:
PS /home/stefan> az --version
azure-cli                         2.37.0

core                              2.37.0
telemetry                          1.0.6

Extensions:
quota                              0.1.0
azure-devops                      0.18.0
ai-examples                        0.2.5
ssh                                1.1.1

Dependencies:
msal                            1.18.0b1
azure-mgmt-resource             21.1.0b1


Sana - not work - grey image

me get yellow empty image!!

And black for me...

I'm doing a full rewrite of most of the code here, though unsure if it fixes it. It's not really ready for testing yet https://github.com/city96/ComfyUI_ExtraModels/pull/92
From the screenshot my only real guess would be some issue with either package versions (upgrading transformers for the tenc might help) or maybe an issue with running it on cuda (leaving it on CPU/auto should be fine, Gemma 2B is fast enough)

When it finishes, it looks like there is this error:
ComfyUI\nodes.py:1534: RuntimeWarning: invalid value encountered in cast
img = Image.fromarray(np.clip(i, 0, 255).astype(np.uint8))

I'm doing a full rewrite of most of the code here, though unsure if it fixes it. It's not really ready for testing yet #92
From the screenshot my only real guess would be some issue with either package versions (upgrading transformers for the tenc might help) or maybe an issue with running it on cuda (leaving it on CPU/auto should be fine, Gemma 2B is fast enough)

I try already cuda or cpu i got the same black image or gray image as result! i have a rtx 4090

Same problem here... also on a 4090 only grey image

GUYS, I found the solution for black/grey/output!
Uninstall Extra Models for ComfyUI.
Restart ComfyUI.
Go to Install Missing Custom Nodes:
Click Install gemma...
BUT for Extra Models for ComfyUI, click Install via Git URL and add:
https://github.com/Efficient-Large-Model/ComfyUI_ExtraModels
Restart again and hit Queue. It will download the correct models automatically.
And DONE!
All the love!

Hymaera's fix worked for me too

Ok! It works also form me, but i had to put this node like this:

Looks like he want download the VAE and not let chose the alredy existing on your directory

GUYS, I found the solution for black/grey/output!
Uninstall Extra Models for ComfyUI.
Restart ComfyUI.
Go to Install Missing Custom Nodes:
Click Install gemma... BUT for Extra Models for ComfyUI, click Install via Git URL and add:
https://github.com/Efficient-Large-Model/ComfyUI_ExtraModels
Restart again and hit Queue. It will download the correct models automatically.
And DONE!
All the love!

ComfyUI Desktop won't let me Install via Git URL, I click it and nothing happens :(

@DavidAllenNeron, please check if you have received a message about security restrictions from ComfyUI. In my case, I had to add "security_level = weak" in the following file: custom_nodes\ComfyUI-Manager\config.ini

GUYS, I found the solution for black/grey/output!
Uninstall Extra Models for ComfyUI.
Restart ComfyUI.
Go to Install Missing Custom Nodes:
Click Install gemma... BUT for Extra Models for ComfyUI, click Install via Git URL and add:
https://github.com/Efficient-Large-Model/ComfyUI_ExtraModels
Restart again and hit Queue. It will download the correct models automatically.
And DONE!
All the love!

following his fix, work perfect now all is working well! thank you mate

Which models do you delete? I deleted the vae and it doesn't auto-download it again.

GUYS, I found the solution for black/grey/output!
Uninstall Extra Models for ComfyUI.
Restart ComfyUI.
Go to Install Missing Custom Nodes:
Click Install gemma... BUT for Extra Models for ComfyUI, click Install via Git URL and add:
https://github.com/Efficient-Large-Model/ComfyUI_ExtraModels
Restart again and hit Queue. It will download the correct models automatically.
And DONE!
All the love!

This worked fine!! Thanks!!

Added a note to the readme that links out to their readme/fork for the time being.

WOW working ! THX :)

@DavidAllenNeron, please check if you have received a message about security restrictions from ComfyUI. In my case, I had to add "security_level = weak" in the following file: custom_nodes\ComfyUI-Manager\config.ini

I did that but it still won't do anything.. I click the button and nothing happens.
I'm getting this in the console (devtools): 9
comfyui-manager.js:762 Uncaught
Error: prompt() is and will not be supported.
at HTMLButtonElement.onclick (comfyui-manager.js:762:17)
comfyui-manager.js:762 Uncaught
Error: prompt() is and will not be supported.
at HTMLButtonElement.onclick (comfyui-manager.js:762:17)

Thank you, Hymaera, installing from repo and the problem was solved.

After doing @Hymaera method ive been getting this error
ExtraVAELoader
No module named 'diffusers'


Fix test settings import when running docker-tests

I have been experiencing a test settings import error when running docker tests locally. This PR is to address this issue by using con.test_settings instead of con/test_settings.

It looks like this is the proper syntax for DJANGO_SETTINGS_MODULE, good catch. I'm just wondering why no one else has seen this issue locally (or in CircleCI for that matter)?

Probably the two syntaxes  were valid up until a recent pytest release/update.


Clarify internal attrs type parameters

This tiny PR improves some types for internal function, and also fixes an Argument of type 'MarkType' is not assignable to parameter of type 'never'.ts(2345) typescript error. It doesn't affect the external API (i.e. .d.ts files).

It's weird how TypeScript behavior for inference of array types keeps changing (TS 5.3.3 is fine with the array in gatherMarks). But these look reasonable — merging.


String-based flags should be replaced with enums

i.e. "overlay" should become BlendMode::Overlay
Between the discussion on Reddit and what I previously covered with error types, I'm sure you were expecting this. I've actually already finished implementing this; I'm only opening this issue to assure that efforts aren't needlessly duplicated. I would open the pull request for you to review, but I based it from the changes in my existing pull request, so it will have to wait.

Prev pull req was  merged. Your good to go


ECR-1703 Add text/plain content-type to string replies

Overview
Add text/plain content-type to string replies.

See: https://jira.bf.local/browse/ECR-1703
Definition of Done

[ ] The continuous integration build passes

I've added it here https://github.com/exonum/exonum-java-binding/pull/294


fix schema change may cause mow duplicate key

Proposed changes
Issue Number: close #xxx
#29386 fixed an issue that may cause duplicate key, but it breaks some schema change cases.
Then #29733 reverted some change of #29386, which also brought back this issue.
issue description:

all rowsets written to the new tablet with TABLET_NOTREADY state, are skipped the step of delete bitmap calculation
after the new tablet created, double write start writing rowsets to new tablet
alter process will calculate a version on base tablet, for the rowsets that need to be converted to new schema, and clean all rowsets older than that version on the new tablet, before start converting the historical data
but the max_version of new tablet may lag behind base tablet, e.g. new tablet's max version is 6, and base tablet's max convert version is 10. So after the rowset clear operation of step3, double write may still write version 7,8,9,10 into new tablet
after the historical data conversion, alter process will add new converted rowsets into new tablet, but it will fail while adding rowsets between version 7 and 10, because these version already existed
the delete bitmap of rowsets between 7 and 10 is not calculated, so duplicate key happened.

solution:

#29386 return failure when such situation happened, but it will break some schema change cases
In this PR, I propose to update the variable real_alter_version to 6 (see previous case), recalculate delete bitmaps on all rowsets that older than real_alter_version

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

LGTM

run p0

run p1

run buildall

run buildall

run buildall


recognise other nuxt community contributions

nuxt-modules
nuxt-community
3rd party modules from modules API?
discussions?

Sorry if it's not suitable place to say, but it seems like I am blocked from the server or something? Can't join to the server.
id: gruce8889.
Thank you.

nuxt-modules
nuxt-community
3rd party modules from modules API?
discussions?

For the modules we could piggy-back on the nuxt-modules and count all the listed modules.
I agree with discussions


Add module for removing etcd nodes

Depends on https://github.com/kubic-project/salt/pull/82

@inercia: What do you think about merging this? We have already etcd grain merged


Updated minimum memory

Under Build the Windows 10 reference image, I have added the minimum memory requirement for Windows 10
Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/1980

Hi @nenonix and @JohanFreelancer9 copy review please. Thank you.

Hi @greg-lindsay kindly review and approve this PR. Otherwise, let us know if further amendments need to be made. Thank you so much.

Hi @greg-lindsay , do you have any update on this for us? Kindly merge if approved. Thank you.


How to install?

HexEnhanced+ is expected to go public this week. At the moment, Github is just using for auto-update functionality in the Closed Beta. As soon as it goes public, installation instructions will be available both on the HE1 forums and here on Github.

Installation instructions have been added to the readme.


Factory Method and Abstract Factory patterns are the same

It seems to me that they're the same and there is no actual difference between them.

Couple of words about factories: https://medium.com/@mlbors/a-word-about-factories-25b777e9d6c7

:+1:

I reworked both of the patterns and I think the difference between them is now more obvious than before. Have a look if you want.


Simplifying jac slow for large systems

For large systems, the expression tree representing the Jacobian is very large, and simplifying it symbolically can be slow. Question: does to_python do some simplifications (e.g. multiply by zero)? Do some testing to see when to use simplifications

to_python will evaluate subtrees of the expression tree if they are constant, and thus simplify that way. But that is the only simplification.
At the moment the simplify is done in a bottom-up fashion, which is very slow. Performance would improve a lot if there was an initial simplify sweep top-down, for example pruning the tree when it finds a multiply by zero.

closing this as it is no longer slow if you use casadi (which is the default)


Get all service endpoints across the organization

Currently it's not possible to list down all service endpoints in the organization since project is mandatory. It's difficult when there are 100s of projects and 1000s of service endpoints scattered and duplicated across many projects.
It would be great if --project is made optional in az devops service-endpoint list command.

route to service team


Security patches

Description

Fixes some security vulnerabilities discoverd by @dependabot

Fixed vulnerabilities

CVE-2022-37603
CVE-2022-37599
CVE-2022-46175
CVE-2022-3517
CVE-2021-3803

I'm not sure if the vulnerabilities will be fixed. The yarn audit says it's good to go, but I'm not sure if dependabot will automatically close the issues
Probably will need to come back to this later


Theme doesn't work for Pop_OS! 21.04

The theme doesn't show up on gnome tweaks nor lxappearance. Trying to activate the theme via the terminal doesn't work either.

Could you be more specific? What steps did you take thus far? The theme only shows up after moving it to the appropriate directory for example.


Future Elasticsearch Image plans

Wondered if there was a plan to handle the fact that the pires/docker-elasticsearch-kubernetes repo is abandoware at this point.

Is it gonna happen?
(he's referring to https://slack.com messenger)

Ah.. I see :) no idea.

https://www.elastic.co/blog/security-for-elasticsearch-is-now-free

Yeah I saw that @mleklund, the question now is should this operator exist now that elastic has an official one?

Once the official one is tested and known to provide all the needed
features id imagine the answer would be no. What is your thoughts?
On Tue, May 21, 2019 at 10:00 AM Steve Sloka<EMAIL_ADDRESS>wrote:

Yeah I saw that @mleklund https://github.com/mleklund, the question now
is should this operator exist now that elastic has an official one?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/upmc-enterprises/elasticsearch-operator/issues/276?email_source=notifications&email_token=AATPVQVAUTW63SML5ZKKZ7DPWP6AJA5CNFSM4GOZUIO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4ACUY#issuecomment-494403923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATPVQUXVRH3DHHMSPWTPP3PWP6AJANCNFSM4GOZUIOQ
.

That's my thinking, but need to investigate the current solution to verify features. I don't think it makes sense to invest in multiple solutions that accomplish the same thing and given there's a vendor solution, I think it makes sense to move to that.

Zalando team have their own ES operator, but it seems the main focus is on scaling https://github.com/zalando-incubator/es-operator. Of course, it would be great if we have only one operator to rule them all, but I don't see that happen anytime soon.

I also might see about moving this to a generic org/repo. Would be nice to have all the code in one place (e.g. operator, cron, image, etc)

@stevesloka any updates on this?

https://www.elastic.co/blog/security-for-elasticsearch-is-now-free

Free but not open. Its in the basic tier, not the open source tier.
The open distro folks seem to be maintaining images too. maybe those would work?
https://hub.docker.com/r/amazon/opendistro-for-elasticsearch

I tried installing the official one, never worked for me... Still using yours

The open distro folks seem to be maintaining images too. maybe those would work?

It works with the operator with minor modifications, https://github.com/komljen/opendistro-for-elasticsearch-k8s
I removed the security plugin here.


add Uni Localization

General

✏ Mark the necessary items without changing the structure of the PR template.

[x] Pull request template structure not broken

Type

ℹ  What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[x] Fix
[x] Feature

Checklist

ℹ  Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉  Put an x in the boxes that apply.

[x] Title as described
[x] Make sure you put things in the right category!
[x] Always add your items to the end of a list

Open Source

[x] Link description does not contain a link to an author / third-party resource
[x] The documentation (README) contains a description of the project, illustration of the project with a demo or screenshots and a CONTRIBUTING section
[x] The documentation is in English.
[x] The project is active and maintained.
[x] The project accepts contributions.
[x] Not a commercial product

Apps/Websites

[x] The website is available without errors or ssl certificate problems, and load in a reasonable amount of time.
[x] The website is using vuejs intensively. It should detect vue with vue-devtools.

If you cannot detect vue with vue-devtools due to work at non public pages (e.g. for enterprise website), you can send Pull Request with screenshot that detected it.

[x] The website is original and not too simple. For that reason, blogs and simple landing pages are rejected.
[x] A commercial product using Vue, provided that guests could reasonably check out how Vue was used (i.e. A headless CMS which uses Vue for the Admin/editor Area and offers a free tier).

fix: shorten description


Tap action 'more-info' is not working anymore

I had tap_action: more-info working great but besides 2.0.0, it is not working anymore :-(.
I had tested this as well (as breaking changes said) with no success:
type: custom:battery-state-card
title: Vibración
entities:
  - entity: sensor.bateria_vibracion_buzon
    name: Buzón
    tap_action: more-info
    type: custom:battery-state-entity

YAML configuration
type: custom:battery-state-card
title: Movimiento
entities:
  - entity: sensor.bateria_movimiento_cocina
    name: Cocina
    tap_action: more-info

Screenshot

Version

2.0.1

It tuned out that the "short" way of defining the action stopped working but the proper way does. So it doesn't work when you use string as a tap_action but if you put it as an object it should e.g.:
tap_action:
  action: more-info

I will fix it in the next update

it turned out that the tap_action as string stopped working if you define it as object it should work:
tap_action:
  action: more-info

Anyway the fix is coming...

Thank you very much @maxwroc ☺


Add a JDK serializer for java.io.File

Nice @sschuberth 🙌🏼
What do you think about naming the serializer FilePathSerializer? In theory, we might want to add another file serializer down the line, which serializes the file as:
{
  "filename": "${file.name}",
  "content": "${base64encode(file.readBytes())}"
}

Sorry, I'm used to force-pushing my PRs to amend commits in order to address review comments in the commit they belong to. This overwrote the commit that @Kantis added in between. I've cherry-picked them again. but now these commits show up as "Unverified".

Sorry, I'm used to force-pushing my PRs to amend commits in order to address review comments in the commit they belong to. This overwrote the commit that @Kantis added in between. I've cherry-picked them again. but now these commits show up as "Unverified".

That's fine. We can squash the PR and it should verify the squash commit (or at least make it not require verification)

Ah, crap, I forgot to rename FileSerializerTests.kt to File*Path*SerializerTests.kt. Should I create a follow-up PR @Kantis? Or should FilePathSerializer.kt actually be renamed back to FileSerializer.kt, as it's supposed to also host non-path File serializers in the future?

I think we could keep File serializers in one place until they grow apart.. On the other hand, since we only have the single one right now, we could just rename the test for the time being.

I think we could keep File serializers in one place until they grow apart.

Yeah, I think I have a tendency of doing that, as having too many implementation files might be a bit cluttered. I'll create a follow-up PR to rename FilePathSerializer.kt to FileSerializer.kt.


Add maven wrapper

Hi, i'm trying to build the project locally but i saw that there isn't a maven wrapper included in the project.
I think it's a valuable addition for the people like me that don't like to install a build tool anymore given that both gradle and maven now offer this handy alternative of using a wrapper. If you don't know what it is, it's an official component of maven so it is safe to use it and distribute it along your project https://maven.apache.org/wrapper/.
Let me know what you think. I really like the project btw :)
Bye

@EvaristeGalois11 thank you for the suggestion! I'm happy to add the wrapper for people who don't have Maven installed :)
I did some quick research regarding best practices on distributing the wrapper. Based on the comments in https://github.com/junit-team/junit5-samples/issues/111 it should be possible to exclude the jar file from source control:
.mvn/wrapper/maven-wrapper.jar

If not present, the jar will be downloaded automatically. Would you mind removing the jar and also adding it to .gitignore?

@EvaristeGalois11 thank you for the suggestion! I'm happy to add the wrapper for people who don't have Maven installed :)
I did some quick research regarding best practices on distributing the wrapper. Based on the comments in junit-team/junit5-samples#111 it should be possible to exclude the jar file from source control:
.mvn/wrapper/maven-wrapper.jar

If not present, the jar will be downloaded automatically. Would you mind removing the jar and also adding it to .gitignore?

Ah i didn't even know that one could just exclude the jar from the repo that easily!
I have updated the PR as you asked, sorry for the double force push but i forgot to squash the two commits.


foreach sed fails with 'unknown shorthand flag' error

I get the following error when running foreach sed with turbolift 2:
`$ turbolift foreach sed -i '' 's/foo/bar/g' README.md
Error: unknown shorthand flag: 'i' in -i
Usage:
turbolift foreach -- SHELL_COMMAND [flags]
Flags:
-h, --help   help for foreach
Global Flags:
-v, --verbose   verbose output
2021/05/21 11:49:08 unknown shorthand flag: 'i' in -i`
A temporary workaround is to encapsulate the sed command in double quotes, but I think this is a bug in the way parameters are handled. (also some of the README examples do not work either)

Good catch, I reckon we need to add DisableFlagParsing: True to the command here:
https://github.com/Skyscanner/turbolift/blob/main/cmd/foreach/foreach.go#L31-L36
As per the doc:
https://pkg.go.dev/github.com/spf13/cobra#Command
	// DisableFlagParsing disables the flag parsing.
	// If this is true all flags will be passed to the command as arguments.
	DisableFlagParsing bool

I'll prep up a PR and give this a go

Ah, that's annoying. Does putting -- before the command make any difference? Eg. turbolift foreach -- sed ....
I'd need to check, and not sure if cobra handles that automatically to stop parsing flags. In theory, this might be the way, though.

@rnorth checkout https://github.com/Skyscanner/turbolift/pull/51
I think this should fix it

Sure, but what I mean is that -- seems like the standard unix way to achieve the goal.
E.g. see https://unix.stackexchange.com/questions/11376/what-does-double-dash-mean
The downside of #51, I think, is that it will make it harder to implement actual flags for the foreach command, should they be needed (eg --parallel).
I think turbolift-bash was erroneous in that it didn't require -- - but maybe it should have done...

I agree -- is the preferred POSIX compatible solution, but I'd also argue it gets in the way of the user experience. We have another case like that with #53. Similarly, adding quotes around the command works since it then considers the command string as a single parameter, it makes sense from a shell perspective, but it's not particularly elegant.
My PR was due to the absence of any flag at the moment, and the idea was to look at it when the time comes but I see your point.
The docker cli has managed to fix it somehow.

They also use the TraverseChildren thing:
https://github.com/docker/cli/blob/master/cmd/docker/docker.go#L41
They are somehow parsing the arguments differently for the run, the codebase is a bit hairy i need to look deeper into it.

Apparently the magic happens with: Flags.SetInterspersed()
https://github.com/spf13/cobra/issues/352
https://github.com/docker/cli/blob/master/cli/command/container/run.go#L50
https://github.com/docker/cli/blob/eb898d59c7c7ee7c8bdc5a4df4351ab04508ba78/vendor/github.com/spf13/pflag/flag.go#L1228
I'll give this a go. I think this is what we need.


Enable Delta Packages + Update to Squirrel 0.8.2

This PR allows you to build delta packages via passing a remoteReleases parameter which hosts your current remote releases directory (for Atom, this is https://atom.io/api/updates). This PR also upgrades Squirrel to Squirrel.Windows 0.8.3, which addresses:

https://github.com/atom/atom/issues/5295
https://github.com/atom/atom/issues/5296
Provides the options needed to solve https://github.com/atom/atom/issues/5323
https://github.com/atom/atom/issues/5109

Squirrel.Windows 0.8.3 also includes https://github.com/Squirrel/Squirrel.Windows/pull/212, which means that people should be able to copy the installed atom folder wholesale onto a USB stick and it'll still update correctly. /cc https://github.com/atom/atom/issues/2939

Awesome, thanks


Warn about unused imports

I don't see a bug for this already, but it would be nice to have a warning for unused imports.

So far, my experience has been that these warnings are mostly very annoying. I don't want to have to re-tune my imports after every change to make sure they precisely cover the things I'm actually using.
Also, import foo::bar; import bar::{a, b}; warns about unused import bar, although it is used by another import.
Reopening for discussion.

How about adding a flag like fwarn-unused-imports and turn it off by default?
Regarding the cascaded import warning, it should be a bug. I will try to look at it.

An off-by-default flag would be an improvement I guess -- one could actively polish up imports now and then, to make sure they aren't misleadingly broad, without having to constantly worry about it.

Added the flag in 32868f0.

I rebased master to fix the merge conflict. And the incorrect warning bug is fixed also. Please review.
3945548 rustc: Add a flag '--warn-unused-imports'
32cf972 rustc: Fix warn on unused import bug

Thanks! Integrated your patches.


Issue in compiling install.sh

Hello,
Thank you for providing the code. I was trying to compile the install.sh file but Im getting the following error:-
in _build
    raise VerificationError('%s: %s' % (e.__class__.__name__, e))
cffi.error.VerificationError: LinkError: command 'gcc' failed with exit status 1

I have edited my mask.sh file with the nvcc path as
nvcc -c -o correlation_cuda_kernel.o correlation_cuda_kernel.cu -x cu -Xcompiler -fPIC -arch=sm_52 -I ${TORCH}/utils/ffi
My nvcc --version gives me:-
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2017 NVIDIA Corporation
Built on Fri_Sep__1_21:08:03_CDT_2017
Cuda compilation tools, release 9.0, V9.0.176

Could you kindly assist me with this issue? Thanks a lot

Hello =) I've met the same problem as you. Did you solve this issue?
Thanks!

I had this problem. too.
I find there is another error " fatal error: cuda.h: No such file or directory" before this error.
Then I fixed it with this command "sudo ln -s /usr/local/cuda-8.0 /usr/local/cuda".
Then it can be compiled correctly.

I had this problem. too. I find there is another error " fatal error: cuda.h: No such file or directory" before this error. Then I fixed it with this command "sudo ln -s /usr/local/cuda-8.0 /usr/local/cuda". Then it can be compiled correctly.

oh,thanks,maybe I have resolved it before


Update Dockerfile to install dependent python packages.

Sorry for the piecemeal update, in the last update docker finished building without error but I didn't actually test running truvari thought it yet. Looks like the project toml needs to be copied over for all the python dependencies to be picked up by pip.

Makes sense. Thanks for picking this up. I don't have testing around the docker so I didn't catch it.


Enable uv to replace and delete itself on Windows

Summary
On Windows, we can't delete the currently-running executable -- at least, not trivially. But the self_replace crate can help us here.
Closes https://github.com/astral-sh/uv/issues/1368.
Closes https://github.com/astral-sh/uv/issues/4980.
Test Plan
On my Windows machine:

maturin build
python -m venv .venv
.venv/Scripts/activate
pip install /path/to/uv.whl
uv pip install /path/to/uv.whl
uv pip uninstall uv

Wow, this is amazing, it should probably looked to see if pip (or distlib) can implement the logic of self_replace, because this remains an issue on Windows if you call pip instead of python -m pip.


Add <track> element to the Video component for accessiblity

See https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/112261cbc84f5b7d74de9b427b529a10b41faece/docs/rules/media-has-caption.md

Related comment https://github.com/Shopify/hydrogen/issues/59#issuecomment-922929371