Add version option to envcloak command in CLI

Hi,
This PR introduces the --version command to the envcloak CLI, as requested in Fixes #9 – Introduce --version command

Hi Robeto 👋,
Thank you for your help, indeed this line solves the problem. 💪
All the best!


Migrate to CircleCI

Since support has been dropped off dd-tracer-rb, I've followed the path because I think that it's our guideline, but I want to confirm with my team first. Thanks for the review!

Goodbye 2.0 and thanks for all the fish ;)

@ivoanjo concerning 2.0 support: I'll add a warning in 5.3.0 + some deprecation notes in the README that we will drop its support in 5.4.0
Meanwhile; I've added a job capable of running the tests with latest ruby 2.0, it's failing here since it needs #211 first.


test(client-tree): ESM test focus and fix

use ESM __dirname workaround
enable general ESM test by default (perf already was)
update id-compressor build dependencies

I don't see the "update id-compressor build dependencies" mentioned in the description.

I don't see the "update id-compressor build dependencies" mentioned in the description.

These are at the bottom of package.json.
			"build:test:cjs": [
				"...",
				"@fluidframework/id-compressor#build:test:cjs" // <-- now explicitly :cjs
			],
			"build:test:esm": [
				"...",
				"@fluidframework/id-compressor#build:test:esm" // <-- now explicitly :esm
			],


Generating wit from dependencies

First off, fantastic work!  Worked out of the box and am excited to help with the project.
One issue I ran into is trying to generate wit from a dependencies.  Within the project worked wonders, but I'm guessing the the cli is only checking the source files of the current project.
Without this, I'm wondering if there is a way to publish the wit with cargo?
Again great work and look forward to getting this in the hands of devs working with NEAR smart contracts!

To be sure I fully understand your need if you have a repository with reproductible example it could help me. What I understood so far for now is for example you have a main project with witgen as dependency and some functions and structs marked with #[witgen] but also in the dependency of this project you have another one which also include witgen in its deps and using #[witgen] on their own records. And you want to generate 2 .wit files from your main project right ?
About publishing the wit with cargo, for now I don't have too much ideas but maybe you could have an exported constant string or bytes from your own published crate. To generate this exported constant string you could use something like include_str! macro from std lib. Just a suggestion, maybe we can find better ideas or maybe I'm missing the context :)

Here is an example branch: https://github.com/willemneal/near-sdk-rs/tree/feat/witgen
If you check out the last commit you'll see I added the macro to the deps for the NFT standard.  Then in the examples/non-fungible-token you can generate the wit file but it is missing the deps type.
This isn't a huge deal since I can copy the deps output manually, but generally was wondering what the plan here was.
Personally I think generating a singe big wit file is the way to go currently.  I want to generate JS from the wit file and I've found that if your wit file uses use to import the types of the other file those functions don't get included when generating the interface.

Ok I got your point. BTW I spotted a bug in the indentation of record fields, it will be fixed.
Let me suggest a quick fix, you'll tell me if you think it's a good idea or if you have better ideas feel free.
Indeed it also builds wit files for your deps but in your case it's a specific case because your dependency is part of your workspace.
I can show you how you can reproduce the way cargo witgen works, for example if you make a cargo clean and try to run WITGEN_ENABLED=true cargo check in your nft directory. You'll see in the target dir of your workspace you'll have a target/witgen with different wit files corresponding to each record and function marked with witgen.
What I suggest is to implement a kind of option of cargo witgen like cargo generate -d A_TARGET_DIR_CONTAINING_WITGEN_BUILD to let you build a new wit file generated for your workspace. Doing this you'll be able to have 2 wit files, one directly generated for your nft project and one for your dependency in your workspace. Keep in mind it's a kind of workaround for now because the final solution would be to find a way to automatically handle this kind of behavior by default for cargo witgen but I don't have a final solution for now.

I spotted a bad indentation here in your wit files https://github.com/willemneal/near-sdk-rs/blob/feat/witgen/examples/non-fungible-token/nft/witgen.wit#L7
But it's not a bug coming from witgen but directly from your code here https://github.com/willemneal/near-sdk-rs/blob/feat/witgen/examples/non-fungible-token/nft/src/lib.rs#L50 you have bad indentation. You should format your code with rust fmt and use rust-analyzer in your code editor

Ah yeah the project as a whole does this and every requires for PRs, but since examples are not part of the workspace they aren't caught.  Good catch!


Migrate to .NET Core

As mentioned by @smikis in #16 - building the library in .NET Core would increase the longevity of the APIReader since .NET Core is the standard of ASP.NET which is more commonly being used for new development. Have created a separate issue for this to be able to better track the progress, and discussions of the migration.
Relevant resource:
Migrate from ASP.NET to ASP.NET Core

This is now a .net core project


Add SpaceUI by @256ArtsDeveloper

[x] Project URL: https://www.jaydenirwin.com/spaceui/
[x] Update contents.json instead of README
[x] One project per pull request
[x] Screenshot included
[x] Avoid iOS or open-source in description as it is assumed
[x] Use this commit title format if applicable: Add app-name by @github-username
[x] Use approved format for your entry

Thx!


Add example to delete multiple measurements at once

On this page:
https://docs.influxdata.com/influxdb/cloud/write-data/delete-data/
Describe how to delete multiple measurements at once. For example "Delete all measurements that matches a regex". Refer to Delete Predicate Syntax: https://docs.influxdata.com/influxdb/cloud/reference/syntax/delete-predicate/#delete-points-by-measurement

The delete predicate syntax does not allow you to delete multiple measurements at once or by regex. Currently, the only comparison operator support by the delete predicate syntax is =, so it has to be an exactly string match. The only supported logical operator is AND. You need an OR logical operator to delete multiple measurements.
The supported logical and comparison operators are documented here: https://docs.influxdata.com/influxdb/cloud/reference/syntax/delete-predicate/#logical-operators.

thanks, @sanderson! fyi, this originated from docs feedback...updated issue above to clarify.


🐛 Bug Report: Techdocs iFrame hook isSafe does not support relative paths

📜 Description
The current implementation of the isSafe function assumes all src attributes in iframe elements contain absolute URLs because the full hostname is needed to compare against the allowed iframes configuration array.
Regex is not supported, wildcards are not supported, and we're stuck with having to be a full absolute path.
However, when an iframe has a relative path (e.g., ./something.html), the URL constructor throws an error, leading the function to return false, marking the iframe as unsafe regardless of its validity within the host environment.

Note: The Techdocs specific iframe allowed sources was not intuitive. Expectation was CSP framesources would be the "safety" check needed or the default allowed list. That'd require wildcard expression support for the allowed frame sources, which I can add as a new feature request if this morphs into something larger.

This creates issues when working in environments where relative paths are valid or required.
https://github.com/backstage/backstage/blob/master/plugins/techdocs/src/reader/transformers/html/hooks/iframes.ts#L30
👍 Expected behavior
Links, images, and other elements that link to internal or external content have paths re-written in the addBaseUrl function a few directory above in the html folder. https://github.com/backstage/backstage/blob/a4d9d5786d3c632098c06dd4d091313fa3981f26/plugins/techdocs/src/reader/transformers/addBaseUrl.ts#L86
Expectation is to be able to support a structure such as:
simple-docs/
├── catalog-info.yaml
├── mkdocs.yml
└── docs/
    ├── index.md
    └── emails/
        └── examples/
            └── html_template.html

Using the npx @techdocs/cli generate and npx @techdocs/cli serve show the Docker container has the html_template.html in the correct folder location.
Not supporting relative iFrame source paths blocks being able to render required assets in Backstage techdocs.
👎 Actual Behavior with Screenshots
Functionally working in mkdocs and iframe works with relative paths.

👟 Reproduction steps
simple-docs.zip
📃 Provide the context for the Bug.
We have some services that publish HTML templates of the content they offer or create for review by the developers to ensure it meets their requirements. Specifically with HTML email templates.
Being able to embed relative path content to the HTML templates is needed but not currently supported by Backstage due to issue outlined above.
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

I assume that it's more nuanced than simply checking whether the fs.isAbsolute on the source link and allowing it due to the routing / base url re-writing.
If it isn't (haven't had cycles to test local package change / import) I had Mr GPT do a quick refactoring on the TS to support relative paths. But you know how the results go lol ... no expectation of functioning without the existing test checks
/**
 * Checks whether a node is an iframe.
 * @param node - Can be any element.
 * @returns true if the node is an iframe.
 */
const isIframe = (node: Element): boolean => node.nodeName === 'IFRAME';

/**
 * Attempts to construct a URL, using the document base URI if src is relative.
 * @param src - The source URL or path.
 * @returns Parsed URL or null if invalid.
 */
const parseUrl = (src: string): URL | null => {
  try {
    return new URL(src, document.baseURI);
  } catch {
    return null;
  }
};

/**
 * Checks if an iframe's src is within allowed hosts.
 * @param src - The src attribute of the iframe.
 * @param hosts - Allowed host names.
 * @returns true if the iframe is safe.
 */
const isSrcAllowed = (src: string, hosts: string[]): boolean => {
  const url = parseUrl(src);
  return url ? hosts.includes(url.host) : false;
};

/**
 * Removes unsafe iframes based on allowed hosts.
 * @param hosts - List of allowed hosts.
 * @returns A function that removes unsafe iframes.
 */
export const removeUnsafeIframes = (hosts: string[]) => (node: Element): Element => {
  if (isIframe(node) && !isSrcAllowed(node.getAttribute('src') || '', hosts)) {
    node.remove();
  }
  return node;
};

^^ techdocs/cli serve

Hi @CiscoRob @Coderrob, I found out a way to implement this by modifying the mkdocs configuration (mkdocs.yml):
---
site_name: Simple Docs
nav:
  - 'Home': './index.md'
docs_dir: docs
repo_url: https://localhost:3000/
edit_uri_template: edit/main/data/docs/simple-docs/docs/{path}
plugins:
  - techdocs-core
markdown_extensions:
  - md_in_html
extra_templates:
  - emails/examples/html_template.html

This will host the file on the backend, in this case http://localhost:7007/api/techdocs/static/docs/default/resource/simple-docs/emails/examples/html_template.html. I implemented some changes to the iframes.ts in order to support parsing the relative URLs in the following PR: #27923
The issue is that the X-Frame-Options header needs to be changed in order to allow iframes from localhost:7007, which I suppose is a different host from localhost:3000. Setting that header manually would be a simple workaround rather than reimplementing the techdocs to upload the template to localhost (unless there's an easier way I'm not aware of!).
Let me know your thoughts 🙂


[JetChat] Text selection does not work in text fields

Compose alpha05 introduced some changes which disabled text selection in all of TextFields, perhaps it's not a bug but a feature and needs to be addressed in a proper way, but there is no mention of this in compose change logs.

Seems to work in alpha08.


Improve cursor focus / blur

Hi, I wonder if there is a way I can disable the cursor blinking?

Hello @YangchaoYi 👋
It seems to be planned here : https://github.com/isontheline/pro.webssh.net/issues/602#issue-1213433652
Have a nice day ☀


update chaos mesh && minor fix on stress attack

Signed-off-by: xiang<EMAIL_ADDRESS>

@cwen0 PTAL

@WangXiangUSTC Can we set this log level to debug and add a flag to control the log level? We can create an another pr to do it.
[2020/12/25 18:12:16.685 +08:00] [INFO] [stress_attack.go:81] ["stressors normalize"] [arguments=" --cpu 1 --cpu-lo
ad 10"]
[2020/12/25 18:12:16.686 +08:00] [INFO] [stress_attack.go:95] ["Start stress-ng process successfully"] [command="/u
sr/bin/stress-ng --cpu 1 --cpu-load 10"]

@WangXiangUSTC Can we set this log level to debug and add a flag to control the log level? We can create an another pr to do it.
[2020/12/25 18:12:16.685 +08:00] [INFO] [stress_attack.go:81] ["stressors normalize"] [arguments=" --cpu 1 --cpu-lo
ad 10"]
[2020/12/25 18:12:16.686 +08:00] [INFO] [stress_attack.go:95] ["Start stress-ng process successfully"] [command="/u
sr/bin/stress-ng --cpu 1 --cpu-load 10"]

OK


Using SOCKS on Linux causes CPU utilisation to jump to 100%

Describe the bug
Starting the SOCKS functionality on a Linux deployment of the Athena agent causes CPU utilisation for the Athena process on the agent host to jump to 100%. This persists even if the SOCKS module is stopped. Tested on Ubuntu 16.04 and 20.04 using both the websocket and http C2 profiles.
To Reproduce
Steps to reproduce the behavior:

Generate an Athena agent for Linux. I chose all default build parameters, included the socks command to be built into the agent, and included either the websocket or the http C2 profile
Launch the agent on the target Linux system and wait for the active callback
Set sleep delay and jitter to 0 and 0 using the 'sleep' command to provide effective channel for SOCKS traffic
Monitor CPU utilisation using 'top' on the Linux system running the agent while running a few random commands on the agent through from the Mythic UI to simulate activity - utilisation on the Athena process is around 1-4% at this point during my testing
Run the 'socks' command on the agent to start a SOCKS proxy on port 7000 or similar - observe utilisation on the Athena process which immediately jumps to around 100%
Stop the SOCKS proxy using the 'socks stop' command. Observe utilisation on the Athena process which remains at around 100% until the process is killed

Expected behavior
CPU utilisation for the process is less than 100%
Happy to provide more info as required

Weird, I don't even know where to start with this, but I'll take a look. Thanks!

Id be happy to help further with this, e.g. with more intensive testing and/or code fixes/PR depending on what you need, however wont have the bandwidth to do so for probably a few weeks (sorry). Will jump back in at that point if you still need an assist

Appreciate it, I plan on looking at it today, so hopefully I figure it out. But any help is appreciated :)

I know it's been a while, but I think I have an idea on the cause of this now. So once I can figure out the fix I'll be able to implement it

I've just overhauled the socks profile functionality with custom stuff, from my testing it's been pretty resource friendly. So this should be fixed now.


SEAB-5183: created notebooks page and added to sitemap

Description
Created notebooks page dockstore.org/notebooks and added the link to the sitemap.
Review Instructions
Verify the new page renders and is implemented correctly and can be accessed from the sitemap.
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-5183
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that your code compiles by running npm run build
[ ] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[ ] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[ ] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[ ] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[ ] Do not use cookies, although this may change in the future
[ ] Run npm audit and ensure you are not introducing new vulnerabilities
[ ] Do due diligence on new 3rd party libraries, checking for CVEs
[ ] Don't allow user-uploaded images to be served from the Dockstore domain
[ ] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[ ] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

Will need to wait for https://github.com/dockstore/dockstore/pull/5327 to be merged for the tests to pass


“'TopErrorBoundary' cannot be used as a JSX component.

When cloning this repo, running yarn, and then yarn start - I receive the following error and cannot interact with the app once it loads.
#10 0.501 yarn run v1.22.19 #10 0.571 $ REACT_APP_DISABLE_SENTRY=true react-scripts build #10 3.468 Creating an optimized production build... #10 116.8 Failed to compile. #10 116.8 #10 116.8 /opt/node_app/src/excalidraw-app/index.tsx #10 116.8 TypeScript error in /opt/node_app/src/excalidraw-app/index.tsx(716,6): #10 116.8  “'TopErrorBoundary' cannot be used as a JSX component. #10 116.8   Its instance type 'TopErrorBoundary' is not a valid JSX element. #10 116.8     The types returned by 'render()' are incompatible between these types. #10 116.8       Type 'React.ReactNode' is not assignable to type 'import("/opt/node_app/node_modules/@types/react-dom/node_modules/@types/react/index").ReactNode'. #10 116.8         Type '{}' is not assignable to type 'ReactNode'. #10 116.8           Type '{}' is missing the following properties from type 'ReactPortal': key, children, type, props  TS2786 #10 116.8 #10 116.8     714 | const ExcalidrawApp = () => { #10 116.8     715 |   return ( #10 116.8   > 716 |     <TopErrorBoundary> #10 116.8         |      ^ #10 116.8     717 |       <CollabContextConsumer> #10 116.8     718 |         <ExcalidrawWrapper /> #10 116.8     719 |       </CollabContextConsumer>
I was able to work around the issue by updating the resolutions in package.json
"resolutions": {     "@typescript-eslint/typescript-estree": "5.10.2",     "@types/react": "17.0.2",     "@types/react-dom": "17.0.2"   },
Is there a different way I should be resolving the issue?

Interesting! I just tried doing a fresh install and it worked fine. Did yarn install work for you smoothly ? whats the yarn version you are using ?

I'm seeing the same issue with yarn 1.22.19.
Failed to compile.

/Users/myuser/git/excalidraw/src/excalidraw-app/index.tsx
TypeScript error in /Users/myuser/git/excalidraw/src/excalidraw-app/index.tsx(707,6):
'TopErrorBoundary' cannot be used as a JSX component.
  Its instance type 'TopErrorBoundary' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'React.ReactNode' is not assignable to type 'import("/Users/myuser/git/excalidraw/node_modules/@types/react-dom/node_modules/@types/react/index").ReactNode'.
        Type '{}' is not assignable to type 'ReactNode'.
          Type '{}' is missing the following properties from type 'ReactPortal': key, children, type, props  TS2786

    705 | const ExcalidrawApp = () => {
    706 |   return (
  > 707 |     <TopErrorBoundary>
        |      ^
    708 |       <CollabContextConsumer>
    709 |         <ExcalidrawWrapper />
    710 |       </CollabContextConsumer>

Earlier today I upgraded yarn from classic to the latest version (3.x) in my dev environment for reasons.  I saw the build broken from the same error @rogeti reported above.  I applied the fix @rogeti suggested, but found that eslint was then complaining (incorrectly) about unused imports of types.
I realized this might all be a big mistake, reverted to yarn classic (v1.22.19), but I again saw the same type error regarding TopErrorBoundary, as reported by @greg-keene, even after I deleted node_modules, ran "git reset --hard" and re-ran "yarn; yarn start".
I then noticed that yarn 3.x had rewritten yarn.lock, and I had accidentally committed the modified yarn.lock to my repository.  The new yarn.lock resulted in the incorrect versions of packages being installed, causing the type error.  After reverting yarn.lock to its previous state and re-running "yarn; yarn start", I was able to resolve this issue.


Word used in sentence is inappropiate

This is a Bug Report
Problem:
The sentence A CSI driver allowing volumeAttributes that are typically restricted to administrators is NOT suitable for use in an inline ephemeral volume. in the page https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#csi-driver-restrictions has used word "NOT" which looks like the abbreviation of something.
Proposed Solution:
The "NOT" should be in lowercase.
Page to Update:
https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#csi-driver-restrictions

/language en
/sig docs

/assign

/assign

The word ”not” in that sentence is the English word “not”, written in uppercase for emphasis. This is idiomatic. We might use bold instead of uppercase for the emphasis.
/priority awaiting-more-evidence

The word ”not” in that sentence is the English word “not”, written in uppercase for emphasis. This is idiomatic. We might use bold instead of uppercase for the emphasis.
/priority awaiting-more-evidence

I think that will look fine if we use the idiomatic word in bold instead of uppercase.

/close


how install

hi, I have tried pip install it's not working to use this help pleas.
thanks

Hi @abbadmus,
Thank you for taking interest in this package. You cannot install CLOCer from pip  since I have not published it to pypi. I'll add a wiki on how to use this project in another project ASAP. Meanwhile what you can do is,

First clone this repo.

git clone https://github.com/Niweera/CLOCer.git

Copy the clocer directory which is inside the CLOCer directory to your project.

Copy the content from the requirements.txt file to your own requirements.txt file.

Now you can install the requirements.

Then inside your own code,

from clocer import CLOCer

if __name__ == "__main__":
    CLOCer.setup()
    CLOCer.run("https://github.com/Niweera/CLOCer")

add the above code.

That's it.


[VL] Daily Update Velox Version (2024_04_04)

Upstream Velox's New Commits:
efb7e7731 by Jimmy Lu, Allow LocalWriteFile::size to be called after close (9350)
6f8b8cfd2 by Masha Basmanova, Document operations on decimals (9337)
bbbe22432 by Kevin Wilfong, hamming_distance can hang or produce incorrect results (9349)
f0f598642 by Deepak Majeti, Remove unused headers in Type.h (9338)

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_master_04_04_2024_time.csv
log/native_master_04_03_2024_b5b454fc7_time.csv
difference
percentage

q1
35.40
35.27
-0.126
99.64%

q2
23.72
27.39
3.664
115.44%

q3
36.61
37.18
0.573
101.57%

q4
37.84
39.81
1.965
105.19%

q5
67.97
69.72
1.752
102.58%

q6
7.47
7.32
-0.151
97.98%

q7
84.55
85.36
0.802
100.95%

q8
87.60
82.86
-4.743
94.59%

q9
122.06
122.48
0.422
100.35%

q10
43.27
44.45
1.181
102.73%

q11
20.40
20.37
-0.030
99.85%

q12
27.93
26.26
-1.674
94.01%

q13
47.04
47.94
0.901
101.92%

q14
18.36
19.88
1.521
108.28%

q15
29.69
34.27
4.577
115.41%

q16
16.59
13.60
-2.992
81.96%

q17
101.63
104.21
2.582
102.54%

q18
143.19
143.00
-0.190
99.87%

q19
14.63
13.79
-0.848
94.21%

q20
28.85
28.36
-0.493
98.29%

q21
234.12
228.06
-6.065
97.41%

q22
14.07
13.93
-0.140
99.01%

total
1243.01
1245.50
2.487
100.20%


Flatpack applications are not displayed

Unlike rofi, flatpak apps are not displayed in Illia. Note that Snap seems to work correctly.
[regolith 2.0 and ubuntu jammy]

Should be fixed by latest commit above

Awesome job, thanks (it works)


a11y red-flags: live regions

Description
Since MOVE is a single-page application where content is dynamically loaded into regions of an already-loaded page, we need to take extra care to ensure ARIA live regions are marked appropriately.
This is especially important for areas containing dynamic notifications.
Acceptance Criteria

[ ] figure out aria-live use for location search bar;
[ ] announce dialogs / modals via aria-live;
[ ] announce snackbars via aria-live.

Additional Notes
See MDN Aria Live Regions docs for more details, and Accessible App for SPA-specific information.

Removing this from beta milestone for now, as NVDA doesn't always respect aria-live - and so we have no reliable way to test it.
When we get a11y red-flags test results back from the Digital Accessibility Team, we can either resurrect / continue this or WONTFIX it (depending on said results).

Closing this for now - we'll open more specific tasks once a11y prioritization is done.

Closing this for now - we'll open more specific tasks once a11y prioritization is done.


Adding custom components

Hey, I have a question, because I tried to implement it, but I can't figure it out. Is there any way, to add custom components to the svelte-exmarkdown?
Lets imagine we have h1 text called "Test". You would type it normally as
# Test

But is there a way to f.e add a button below, that acts like a svelte component, from the text itself?
For example
# Test
<CustomButton/>

(So the user can type this and server can import these components if necessary)

Thanks for your question!
You can implement like this: https://stackblitz.com/edit/svelte-exmarkdown-custom-component?file=src%2FApp.svelte

use rehype-raw module as rehypePlugin.
create your custom component.
create bridge component.

Warning
There are a few things to keep in mind.

When setting up a renderer for a plugin, the keys must be all lowercase
Component properties must be lowercased as well
You cannot use self-closing syntax like <CustomButton/>

@ssssota is this still the optimal way to accomplish this? It seems like quite the workaround.

@jacoblukewood Yes.
(From svelte-exmarkdown v3), you don't need to create bridge component.
New example is here!
https://stackblitz.com/edit/svelte-exmarkdown-custom-elemtents?file=src%2FApp.svelte&terminal=dev

It seems like quite the workaround.

You are right. This way is powerful. With great power comes great responsibility.
If you don't like it, you can use MDsveX.


Event Should not be formated like the other pieces of data

When an event is delivered by a subscription it is likely not obvious to new users as the Event field is formated in a way that is consistent with all the other dats fields.

Event is not a piece of data on the ticket and is the reason you're seeing the post. This should be made to stand out more.

@aushwin just posting for visibility that this is not resolved by https://github.com/Brightscout/mattermost-plugin-servicenow/pull/121 Keeping issue open.
To be explicit I don't see this being a blocking issue but would be nice to have.

@DHaussermann fixed in PR https://github.com/mattermost/mattermost-plugin-servicenow/pull/169. Please verify once

@mickmister @DHaussermann Can we close this issue?

@raghavaggarwal2308 Is there a merged PR that fixes the issue?

@mickmister Apologies, I didn't see that the PR was open.


include_top has reverse meaning

From the docs: include_top: whether to include the fully-connected layer at the top of the network.
However, if True, it is actually not including the layer.

keras.applications.* provides 2 sets of weights: with and without head.
To mimic such behaviour and keep "include_top" flag the model always builds with head, but if include_top=False another model reslices everything from input to last non-head layer.


[RFR]Update line that was pointing to the erstwhile ./website/addons now .…

No ticket. Found issue while debugging another issue.
Purpose
Fix Karma tests
Changes
One line in website/static/js/tests/tests.webpack.js was pointing to ./website/addons which is now no more. However, many/most developers may still have ./website/addons///*.local.py s in their environments. Which has masked this issue.
Side effects
None
Ticket
No ticket. Found issue while debugging another issue.

This looks like it fixes https://openscience.atlassian.net/browse/OSF-8278 .

However, keeping that ticket open for now until we run JS tests on Travis.


Traefik not picking up Docker container

Bug
What did you do?
I'm using Docker containers to run Synapse, a homeserver for the Matrix protocol. One container runs the primary process while some others run so-called workers. Everything was working fine until I updated to Traefik 2.3 (curiously a downgrade does not fix my issue, though!).
Since then, while the primary container is recognised just fine by Traefik via the labels in my compose file, the workers aren't recognised anymore at all. They don't appear in the dashboard nor can they be routed to. The containers themselves are running just fine and are functional, though.
I'm completely unable to see what might be wrong and I've been experimenting for days now. Since asking for advice in your community (https://community.traefik.io/t/traefik-2-3-0-not-picking-up-docker-container/7936) didn't yield any results and there was one person on Reddit who had the same issue (https://www.reddit.com/r/Traefik/comments/j22034/traefik_230_not_picking_up_docker_container/), I assume they and I are hitting some obscure bug.
Here's the docker-compose yaml configuration for the main process which does get picked up by Traefik:
https://mailstation.de/~krueger/traefik/main_process-working.yaml
Here's the worker configuration that does NOT get picked up by Traefik:
https://mailstation.de/~krueger/traefik/worker_unseen_by_traefik.yaml
Should you need any additional information, please just let me know.
What did you expect to see?
The worker should be displayed in Traefik's dashboard and - more importantly - routed to.
What did you see instead?
Neither of my above expectations were fulfilled.
Output of traefik version: (What version of Traefik are you using?)
Version:      2.3.1
Codename:     picodon
Go version:   go1.15.2
Built:        2020-09-29T15:49:06Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
[global]
  checkNewVersion = true
  sendAnonymousUsage = true

[entryPoints]
  [entryPoints.web]
    address = ":80"

  [entryPoints.web2]
    address = ":81"

  [entryPoints.websecure]
    address = ":443"

  [entryPoints.matrix-login]
    address = ":8448"

[log]
  level = "WARN"
  filePath = "/var/log/traefik/traefik.log"

[accessLog]
  filePath = "/var/log/traefik/access.log"

[api]
  insecure = false
  dashboard = true

[ping]

[providers.docker]
  endpoint = "unix:///var/run/docker.sock"
  exposedByDefault = false

[certificatesResolvers.le.acme]
  email =<EMAIL_ADDRESS>  #caServer = "https://acme-staging-v02.api.letsencrypt.org/directory"
  storage = "/etc/traefik/acme/acme.json"
  [certificatesResolvers.le.acme.httpChallenge]
  # used during the challenge
  entryPoint = "web"

[providers]
  # Enable the file provider to define routers / middlewares / services in file
  [providers.file]
    directory = "/etc/traefik/dynamic"
    watch = true

[pilot]
    token = "removedXXX"

I can also confirm this bug on multiple systems. But the bug seems not to be limited to version 2.3.1. I have downgraded to version 2.2.11 and I have the same behaviour there too.
What I noticed is that normally the Docker Containers appear in Traefik after a few seconds, but at the moment it takes about 5 minutes until they appear in the list and can be accessed via Traefik.
###Output of traefik version:
Version:      2.3.1 Codename:     picodon Go version:   go1.15.2 Built:        2020-09-29T15:49:06Z OS/Arch:      linux/amd64
What is your environment & configuration (arguments, toml, provider, platform, ...)?
`logLevel = "ERROR"
defaultEntryPoints = ["https", "http"]
[entryPoints]
[entryPoints.http]
address = ":80"
[entryPoints.https]
address = ":443"
[providers]
[providers.file]
directory = "/etc/traefik/dynamic"
watch = true
[providers.docker]
endpoint = "unix:///var/run/docker.sock"
network = "vhosts"
exposedByDefault = false
watch = true
[log]
filePath = "/var/log/traefik/traefik.log"
level = "WARN"
[api]
insecure = false
dashboard = true`

Just to be clear: My container as specified in the original report doesn't ever show up in Traefik.

Hello @Philantrop,
Thanks for your interest in Traefik !
To go further in troubleshooting, can you paste you dynamic config file and the output of the endpoint /api/rawdata ? For that I am assuming that you have a router that routes to api@internal in your dynamic file.
Also the full debug logs would be great to trace down the problem.

Also, i just notice that you used regular expressions in your rules for the not picked up container.
Thus it seems that the it is not respecting the expected format, as stated in the documentation:

In order to use regular expressions with Host and Path expressions, you must declare an arbitrarily named variable followed by the colon-separated regular expression, all enclosed in curly braces. Any pattern supported by Go's regexp package may be used (example: /posts/{id:[0-9]+}).

Thanks for getting back to me, @rtribotte!
I've fixed the regexp issue, I think, (cf. https://mailstation.de/~krueger/traefik/worker_unseen_by_traefik.yaml), restarted the container and after having ensured the container is running, Traefik itself with debug loglevel.
Dynamic config: https://mailstation.de/~krueger/traefik/rules.toml and https://mailstation.de/~krueger/traefik/redirect.toml
Debug log (in which I see Traefik thinks the container is "unhealthy" (which is simply wrong)): https://mailstation.de/~krueger/traefik/traefik.log
/api/rawdata:
{"routers":{"api@docker":{"entryPoints":["websecure"],"middlewares":["keycloak@file"],"service":"api@internal","rule":"Host(\"auth.mailstation.de\")","tls":{"certResolver":"le"},"status":"enabled","using":["websecure"]},"auth@docker":{"entryPoints":["websecure"],"middlewares":["keycloak@file"],"service":"auth@docker","rule":"Host(\"auth.mailstation.de\")","tls":{"certResolver":"le"},"status":"enabled","using":["websecure"]},"bitwarden@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"service":"bitwarden@docker","rule":"Host(\"bw.mailstation.de\")","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"bw-websockets@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"service":"bw-websockets@docker","rule":"PathPrefix(\"/notifications/hub\")","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"calibre@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","keycloak@file","replacepath-root-calibre@file"],"service":"calibre","rule":"PathPrefix(/calibre) || Host(calibre.mailstation.de)","priority":200,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"cops@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","keycloak@file"],"service":"apache","rule":"PathPrefix(/cops)","priority":150,"tls":{},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"cweb@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","keycloak@file","replacepath-root-cweb@file","cwebscript@file"],"service":"cweb","rule":"PathPrefix(/cweb)","priority":150,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"dimension@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"service":"dimension-dimension@docker","rule":"Host(dimension.mailstation.de)","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"hawking@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file"],"service":"apache","rule":"Host(hawking.mailstation.de)","priority":9,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"heimdall@docker":{"entryPoints":["websecure"],"middlewares":["keycloak@file"],"service":"heimdall@docker","rule":"Host(\"family.mailstation.de\")","tls":{"certResolver":"le"},"status":"enabled","using":["websecure"]},"ipa-ca@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file"],"service":"apache","rule":"Host(ipa-ca.mailstation.de)","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"ipa@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file"],"service":"ipa","rule":"Host(ipa.mailstation.de)","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"keycloak@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file"],"service":"keycloak","rule":"Host(keycloak1.mailstation.de)","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"ma1sd@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"service":"ma1sd-ma1sd@docker","rule":"PathPrefix(/_matrix/client/r0/login) || PathPrefix(/_matrix/identity) || PathPrefix(/_matrix/client/r0/user_directory/)","priority":450,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"mailstation@file":{"entryPoints":["websecure"],"middlewares":["std-headers@file"],"service":"apache","rule":"Host(mailstation.de)","priority":1,"tls":{"certResolver":"le"},"status":"enabled","using":["websecure"]},"matrix-monitor-bot@docker":{"entryPoints":["websecure"],"middlewares":["std-headers@file"],"service":"matrix-monitor-bot@docker","rule":"PathPrefix(/mmb)","tls":{"certResolver":"le"},"status":"enabled","using":["websecure"]},"maubot@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"service":"maubot@docker","rule":"PathPrefix(\"/_matrix/maubot\")","priority":400,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"mx-puppet-twitter@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"service":"mx-puppet-twitter-mx-puppet-twitter@docker","rule":"PathPrefix(/_matrix/twitter/webhook)","priority":500,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"phpmyadmin@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","keycloak@file"],"service":"apache","rule":"PathPrefix(/phpMyAdmin)","priority":150,"tls":{},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"ping@internal":{"entryPoints":["traefik"],"service":"ping@internal","rule":"PathPrefix(/ping)","priority":2147483647,"status":"enabled","using":["traefik"]},"pwm@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","replacepath-pwm@file"],"service":"pwm","rule":"PathPrefix(/pwm) || PathPrefix(/ssp)","priority":150,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"redirecttohttps@file":{"entryPoints":["web"],"middlewares":["httpsredirect@file"],"service":"noop","rule":"HostRegexp({host:.+})","status":"enabled","using":["web"]},"riot-web@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["riot-web@docker","element-web@docker","std-headers@file"],"service":"riot-web-riot-web@docker","rule":"(PathPrefix(/riot) || PathPrefix(/element)) \u0026\u0026 (Host(mailstation.de) || Host(hawking.mailstation.de))","priority":150,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"rspamd@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","keycloak@file"],"service":"rspamd","rule":"Host(rspamd.mailstation.de)","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"saxophonissima@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file"],"service":"apache","rule":"Host(saxophonissima.de) || Host(www.saxophonissima.de)","priority":5,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"spotweb@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","keycloak@file"],"service":"apache","rule":"PathPrefix(/spotweb)","priority":150,"tls":{},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"synapse@docker":{"entryPoints":["matrix-login","web","web2","websecure"],"service":"synapse","rule":"Host(mailstation.de) \u0026\u0026 ( PathPrefix(/_matrix) || PathPrefix(/_synapse) )","priority":300,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"traefik-dashboard@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","keycloak@file"],"service":"api@internal","rule":"Host(hawking.mailstation.de) \u0026\u0026 (PathPrefix(/dashboard/) || PathPrefix(/api))","tls":{},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"well-known-IPA-LE@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","replacepath-well-known-IPA-LE@file"],"service":"apache","rule":"(Host(ipa.mailstation.de) || Host(<IP_ADDRESS>)) \u0026\u0026 PathPrefix(/.well-known/acme-challenge)","priority":150,"status":"enabled","using":["matrix-login","web","web2","websecure"]},"well-known-dav@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file","replacepath-well-known-dav@file"],"service":"apache","rule":"PathPrefix(/.well-known/carddav) || PathPrefix(/.well-known/caldav)","priority":150,"tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]},"www@file":{"entryPoints":["matrix-login","web","web2","websecure"],"middlewares":["std-headers@file"],"service":"apache","rule":"Host(www.mailstation.de)","tls":{"certResolver":"le"},"status":"enabled","using":["matrix-login","web","web2","websecure"]}},"middlewares":{"add-cops@file":{"addPrefix":{"prefix":"/cops"},"status":"enabled"},"cwebscript@file":{"headers":{"customRequestHeaders":{"X-SCHEME":"https","X-SCRIPT-NAME":"/cweb"}},"status":"enabled","usedBy":["cweb@file"]},"element-web@docker":{"replacePathRegex":{"regex":"^/element/(.*)","replacement":"/$1"},"status":"enabled","usedBy":["riot-web@docker"]},"gzip-compress@file":{"compress":{},"status":"enabled"},"httpsredirect@file":{"redirectScheme":{"scheme":"https"},"status":"enabled","usedBy":["redirecttohttps@file"]},"keycloak@file":{"forwardAuth":{"address":"http://traefik-forward-auth:4181","trustForwardHeader":true,"authResponseHeaders":["X-Forwarded-User"]},"status":"enabled","usedBy":["api@docker","auth@docker","calibre@file","cops@file","cweb@file","heimdall@docker","phpmyadmin@file","rspamd@file","spotweb@file","traefik-dashboard@file"]},"matrix-monitor-bot@docker":{"stripPrefix":{"prefixes":["/mmb"],"forceSlash":true},"status":"enabled"},"replacepath-pwm@file":{"replacePathRegex":{"regex":"^/ssp/(.*)","replacement":"/pwm/$1"},"status":"enabled","usedBy":["pwm@file"]},"replacepath-root-calibre@file":{"replacePathRegex":{"regex":"^/calibre/(.*)","replacement":"/$1"},"status":"enabled","usedBy":["calibre@file"]},"replacepath-root-cweb@file":{"replacePathRegex":{"regex":"^/cweb/(.*)","replacement":"/$1"},"status":"enabled","usedBy":["cweb@file"]},"replacepath-well-known-IPA-LE@file":{"replacePathRegex":{"regex":"/.well-known/acme-challenge/(.*)","replacement":"/LE/.well-known/acme-challenge/$1"},"status":"enabled","usedBy":["well-known-IPA-LE@file"]},"replacepath-well-known-dav@file":{"replacePathRegex":{"regex":"/.well-known/(card|cal)dav","replacement":"/owncloud/remote.php/dav/"},"status":"enabled","usedBy":["well-known-dav@file"]},"riot-web@docker":{"replacePathRegex":{"regex":"^/riot/(.*)","replacement":"/$1"},"status":"enabled","usedBy":["riot-web@docker"]},"std-headers@file":{"headers":{"customRequestHeaders":{"Server":"","X-Powered-by":"","X-SSL":"on"}},"status":"enabled","usedBy":["calibre@file","cops@file","cweb@file","hawking@file","ipa-ca@file","ipa@file","keycloak@file","mailstation@file","matrix-monitor-bot@docker","phpmyadmin@file","pwm@file","riot-web@docker","rspamd@file","saxophonissima@file","spotweb@file","traefik-dashboard@file","well-known-IPA-LE@file","well-known-dav@file","www@file"]}},"services":{"apache@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>/"}],"passHostHeader":true},"status":"enabled","usedBy":["cops@file","hawking@file","ipa-ca@file","mailstation@file","phpmyadmin@file","saxophonissima@file","spotweb@file","well-known-IPA-LE@file","well-known-dav@file","www@file"],"serverStatus":{"http://<IP_ADDRESS>/":"UP"}},"api@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:80"}],"healthCheck":{"path":"/ping","followRedirects":true},"passHostHeader":true},"status":"enabled"},"api@internal":{"status":"enabled","usedBy":["api@docker","traefik-dashboard@file"]},"auth@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:4181"}],"passHostHeader":true},"status":"enabled","usedBy":["auth@docker"],"serverStatus":{"http://<IP_ADDRESS>:4181":"UP"}},"bitwarden@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:80"}],"passHostHeader":true},"status":"enabled","usedBy":["bitwarden@docker"],"serverStatus":{"http://<IP_ADDRESS>:80":"UP"}},"bw-websockets@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:3012"}],"passHostHeader":true},"status":"enabled","usedBy":["bw-websockets@docker"],"serverStatus":{"http://<IP_ADDRESS>:3012":"UP"}},"calibre@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8352/"}],"passHostHeader":true},"status":"enabled","usedBy":["calibre@file"],"serverStatus":{"http://<IP_ADDRESS>:8352/":"UP"}},"cweb@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8083/"}],"passHostHeader":true},"status":"enabled","usedBy":["cweb@file"],"serverStatus":{"http://<IP_ADDRESS>:8083/":"UP"}},"dashboard@internal":{"status":"enabled"},"dimension-dimension@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8184"}],"passHostHeader":true},"status":"enabled","usedBy":["dimension@docker"],"serverStatus":{"http://<IP_ADDRESS>:8184":"UP"}},"heimdall@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:80"}],"passHostHeader":true},"status":"enabled","usedBy":["heimdall@docker"],"serverStatus":{"http://<IP_ADDRESS>:80":"UP"}},"ipa@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>/"}],"passHostHeader":true},"status":"enabled","usedBy":["ipa@file"],"serverStatus":{"http://<IP_ADDRESS>/":"UP"}},"keycloak@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:58080/"}],"passHostHeader":true},"status":"enabled","usedBy":["keycloak@file"],"serverStatus":{"http://<IP_ADDRESS>:58080/":"UP"}},"ma1sd-ma1sd@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8090"}],"passHostHeader":true},"status":"enabled","usedBy":["ma1sd@docker"],"serverStatus":{"http://<IP_ADDRESS>:8090":"UP"}},"matrix-monitor-bot@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8080"}],"passHostHeader":true},"status":"enabled","usedBy":["matrix-monitor-bot@docker"],"serverStatus":{"http://<IP_ADDRESS>:8080":"UP"}},"maubot@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:29316"}],"passHostHeader":true},"status":"enabled","usedBy":["maubot@docker"],"serverStatus":{"http://<IP_ADDRESS>:29316":"UP"}},"mx-puppet-twitter-mx-puppet-twitter@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8536"}],"passHostHeader":true},"status":"enabled","usedBy":["mx-puppet-twitter@docker"],"serverStatus":{"http://<IP_ADDRESS>:8536":"UP"}},"noop@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>"}],"passHostHeader":true},"status":"enabled","usedBy":["redirecttohttps@file"],"serverStatus":{"http://<IP_ADDRESS>":"UP"}},"noop@internal":{"status":"enabled"},"ping@internal":{"status":"enabled","usedBy":["ping@internal"]},"pwm@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8080/pwm/"}],"passHostHeader":true},"status":"enabled","usedBy":["pwm@file"],"serverStatus":{"http://<IP_ADDRESS>:8080/pwm/":"UP"}},"riot-web-riot-web@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:80"}],"passHostHeader":true},"status":"enabled","usedBy":["riot-web@docker"],"serverStatus":{"http://<IP_ADDRESS>:80":"UP"}},"rspamd@file":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:11334/"}],"passHostHeader":true},"status":"enabled","usedBy":["rspamd@file"],"serverStatus":{"http://<IP_ADDRESS>:11334/":"UP"}},"synapse@docker":{"loadBalancer":{"servers":[{"url":"http://<IP_ADDRESS>:8008"}],"passHostHeader":true},"status":"enabled","usedBy":["synapse@docker"],"serverStatus":{"http://<IP_ADDRESS>:8008":"UP"}}}}

Any news about this? Even a way to (temporarily) work-around the symptom by telling Traefik to ignore the health check result would be immensely helpful as a stop-gap measure.

Hello @Philantrop,
Sorry for the delay, but it's difficult to troubleshoot your issue since it's not minimal reproducible example.
I wonder how did you checked the health of your container, can you produce the output this command ?
docker inspect --format "{{json .State.Health }}" <container name> | jq

Also, could you provide more information about your Docker installation (version, ...)

I wonder how did you checked the health of your container, can you produce the output this command ?
docker inspect --format "{{json .State.Health }}" <container name> | jq

{
"Status": "unhealthy",
"FailingStreak": 0,
"Log": []
}
So, ok, Docker, too, thinks it's unhealthy. Nevertheless, Traefik should let me be the judge about that and provide an option to ignore (potentially) faulty health checks.
As for my Docker version: Docker version 19.03.11, build 42e35e6

Hello @Philantrop,
Thanks for your inputs, as already guessed, Traefik rely on this status to state if a container is healthy or not.
I understand that you are proposing a new behavior to be allowed to by-pass this status.
I please you to open a new issue to detail your proposal to be able to discuss about it.
I'll close this issue accordingly as a question.
Thanks for your interest in Traefik !

Feel free to open such an issue yourself. Seeing this kind of support in this kind of timeframe sadly let me lose all interest in Traefik.

So, ok, Docker, too, thinks it's unhealthy. Nevertheless, Traefik should let me be the judge about that and provide an option to ignore (potentially) faulty health checks.

@Philantrop I'm sorry about the misunderstanding. As this issue was submitted as a bug and instead looks like you're requesting a feature, the team decided to close it. The functionality you're encountering here is by design to allow Traefik to know the service's state before routing. If that's something you'd like to workaround, we can discuss that on our community forums built for end-user support.

@notsureifkevin: Please take a look at my original post at the top (mind the dates as well, if you seriously want to understand) and then follow through this thread and you might understand my frustration about the support experience on several media (including your forums).
Not sure how I'm personally going to proceed here but it likely won't include Traefik in the long run. I think all has been said here so I'm going to stop responding now.


Investigate use of sync.ErrGroup for error propagation within goroutines

https://godoc.org/golang.org/x/sync/errgroup

This seems mostly useful for parallel tasks, so it may be a good addition to #49

This issue is too generic. In case we introduce some parallelization, we should consider ErrGroup, but for now this is not needed


fix(routing): add connection type on mediation grant

Small update to the feature added in #994 to aggregate the connection type when a connection is related to a mediation grant.
Previously, it was setting only ConnectionType.Mediator, so if the connection was previously tagged with another type, it would be lost.
Also fixes typing for connectionType in ConnectionRecord in order to be able to properly query for connections matching one or multiple types.

Thanks @genaris! Could you add some tests to make sure it correctly adds instead of overwrites?

Done and also fixed the typing as discussed in #1145. Could you quickly review these new changes?


ISPN-8670 Add a configuration storage for standalone servers

Created a test case the verify if the configuration remains the same
after the server has been restarted when shared equals true.

Looks good, thanks @diegolovison


How can i extract the def.proto

hey guys, I think newly created whatsapp accounts is using the proto version 17, as far is know, this .proto is for version 15, can you guys give me hints to extract or create the new protobuff classes?

See my comment here.

looks like the update to 0.3.3330 broke the extractor.
the new module names seem to be ["bgiachiigg", "bfifcddbbg", "bbcaggdbc"] but i cant get it to extract after tweaking them.
possibly something in the acorn parser.
any ideas?


docs: filtering vulnerabilities with trivy

Added docs for filtering vulnerabilities with Trivy
Closes #214

ah yes, looks like that was a bug. it should be v0.1.x

@anubhav06 can you update https://github.com/project-copacetic/copacetic/blob/main/website/versioned_sidebars/version-v0.1.0-sidebars.json too?


change the endpoint for updating gamepasses, resolving #211

Fixes #211

making this fix in #214 (needed to fix cargo fmt)


BRS-896: Updated facility edit, form, details page for winter warning flag

Jira Ticket:
BRS-896
Jira Ticket URL:
https://bcparksdigital.atlassian.net/browse/BRS-896
Description:
Updated facility edit, form, details page for winter warning flag

Need to make change to adjust the winterWarning flag to be at the park level and not facility level. Will reopen later.


feat: add dealer fetch model api

releases #250 that missed a semantic release commit message

cc @maersu


Port #20109 to master

@RyanCavanaugh

@billti Lint failures
src/server/editorServices.ts
ERROR: src/server/editorServices.ts:159:13 object-literal-key-quotes Unnecessarily quoted property 'match' found.
ERROR: src/server/editorServices.ts:160:13 object-literal-key-quotes Unnecessarily quoted property 'exclude' found.
jake aborted.


Fix progress when using VAD chunking

Previously progress would jump around as the same progress object was used for every chunk. Now every chunk is added as a child progress with equal unit count.
fixes #151

This looks great, can you explain how the progress will look in the UI? In other words, on what event does the percentage increase? Maybe a video recording would help if you are able.

The progress update happens at the same time still, after each mel>encode>decode loop, but previously each transcribe task would go from 0->1 simultaneously, resulting in random updates.
Now each task is a child progress of the total progress, with an equal weighting, so the progress increases properly as each child progress goes from 0->1.

 I will update the timeout if those succeed locally

Not having any issues with the tests locally, the same test command passes. Not sure what the issue is with the CI.

Ok the errors are due to the simulator not booting fast enough, will update with a fix in a follow up PR that resolves #100

FYI just merged this https://github.com/argmaxinc/WhisperKit/pull/180 there seems to be an issue with the combine stuff on watchOS, so I limited the test to not run on that platform. Not sure whats causing it but its only happening on macOS 13 runners.


feat: upgrade crossterm to 0.27.0

The current crossterm version has a dependency to a mio version that has a vulnerability: https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7
This upgrade introduces a breaking change, as all results returned by crossterm are now standard std:io::Result, so there is no need to map crossterm errors anymore.
This PR would also close the dependabot PR: https://github.com/dalance/termbg/pull/16

Thank you for your contribution!
I'll merge this, and release new version.

Thanks @dalance 🙏


Support environment variables?

Keystone currently supports detecting S3 options in process.env - see https://github.com/keystonejs/keystone/blob/master/index.js#L75-L77
I think it would be worth continuing to support these, like this: https://github.com/keystonejs/keystone-email/blob/master/lib/transports/mailgun/getSendOptions.js#L7-L12
We may remove support in Keystone for the s3 config option though..? Would probably be awkward to support and breaks separation of concerns between the packages

Yeah I was wondering about that while writing it. The test suite uses environment variables.
I think generally it should be up to the application to configure the S3 options. The question is between writing:
var storage = new keystone.Storage({
	adapter: require('keystone-s3'),
	s3: {
		key: process.env.S3_KEY,
		secret: process.env.S3_SECRET,
		bucket: process.env.S3_BUCKET,
	},
})

... or leaving that out. Tbh I can't think of any strong reason to leave it out - if you want to manually configure those properties you can either not specify environment variables or just override them in your configuration.


Usage instructions are slightly defective (at README.md)

Hi,
The extract code commands don't work:
(base) mojtabaeshghie@mojtabaeshghie-mbp teether % python bin/extract_contract_code.py test.code > test.contract.code
WARNING:root:No CODECOPY in this contract!!
Traceback (most recent call last):
  File "bin/extract_contract_code.py", line 48, in <module>
    contract = extract_contract_code(code)
  File "bin/extract_contract_code.py", line 18, in extract_contract_code
    p.cfg.trim()
  File "/Users/mojtabaeshghie/.pyenv/versions/3.8.13/lib/python3.8/site-packages/teether-0.1.10-py3.8.egg/teether/project.py", line 45, in cfg
  File "/Users/mojtabaeshghie/.pyenv/versions/3.8.13/lib/python3.8/site-packages/teether-0.1.10-py3.8.egg/teether/cfg/cfg.py", line 12, in __init__
KeyError: 0

My contract source is:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract Test {
    struct Transaction {
        address to;
        uint amount;
    }

    mapping(bytes32 => Transaction) transactions;

    address owner;

    constructor() {
        owner = msg.sender;
    }

    function setOwner(address newOwner) public {
        owner = newOwner;
    }

    function newTransaction(address to, uint amount) public returns (bytes32) {
        bytes32 token = keccak256(abi.encodePacked(to, amount));
        Transaction storage t = transactions[token];
        t.to = to;
        t.amount += amount;
        return token;
    }

    function approve(bytes32 token) public {
        require(owner == msg.sender, "Only the owner can approve transactions");
        Transaction storage t = transactions[token];
        payable(t.to).transfer(t.amount);
        delete transactions[token];
    }

    // Fallback function to receive ether
    receive() external payable {}
}

Hi @mojtaba-eshghie,
could you paste the contents of the file test.code?
It should contain the hex-encoded bytecode of the contract under test, not the Solidity source code.


docs(guide/Using $location): Replace invalid link.

The provided URL incorrectly links to a W3C page about HTML history (retrospective), not about HTML5 Browsing History API. The proposed change is to replace it with correct link to WHATWG HTML5 standard.

I signed a CLA as an individual.

LOL, good catch !


Research & improve patience setting

Many exchanges will return results for the latest incomplete candlestick intervals. There's no way to tell if a received latest candlestick is gonna change or not (other than checking the current time and guessing). Experiments are required to see how much delay should be applied before allowing a given time's candlestick can be considered final.

I ended up running a script that uses crypto-candles to get the latest available candlesticks for BTC/USDT on all supported exchanges and for the smallest intervals, to see which ones change and how close to the current time they do.
Empirical evidence from the experiments show that, on the 1m interval, the last completed minute is unreliable on all exchanges. For the most part this is it, but e.g. for FTX, the 2nd most recent minute is also unreliable albeit is much less common. You'd have to test it for hours to see a change.
The race condition that causes past minutes to change is unavoidable without knowing more details about each platform's pipeline, so candlesticks can be cached but one cannot assume with 100% certainty that the caches are always correct.
The results of the experiments were encoded into the Patience setting of all exchanges.


Document the new API

As we have added a new api version here
It is important to document these APIs properly. Ideally make an OpenAPI document for this

closed by #481


{path} resolves to source path instead of destination path

Hi,
First of all thank you very much for this free and open source project! I know it takes a lot of time to manage and maintain such projects and it is highly appreciated!
I'm using the currently latest version (1.4.2) on Mac and tried to move a file and open it afterwards like in the Advanced Usage Example. Unfortunately the {path} placeholder resolves to the source path instead of the destination path and therefore the file can't be opened after it has been moved.

Awesome! Thanks!


NEXT: Installation page misspells "configure" twice

Link to the Page
https://next.skeleton.dev/docs/get-started/installation
Describe the Issue (screenshots encouraged!)

Of course we would miss that - it's only been front end center for us over the last week! :)


Ability to disable 'no options' text and window if options are empty.

When I have an async autocomplete I dont want to see 'No Options' window and text until user inputs something.
I tried to set noOptionsText prop to null if options.length === 0 but the empty window still shows up.

You can control the open state


Feature request: moment.utcOffset

Sorry to trouble you, this is not an issue, but a feature request.
Now, we can set locale globally:
moment.locale('zh-cn');

But, it seems that we cannot set UTC offset globally. I had found moment-timezone, but it is too large to use in browser.
So, could moment provide something like moment.utcOffset to set UTC offset globally? What's more, most of programs just need one timezone...

I can see the desire to set it globally would be useful.  A PR would be welcome.
I'll say though that even though many programs may just need one time zone, that time zone may need multiple offsets to handle DST.  Though for countries like India or China, or other places that have relatively stable single-offset time zones, it might be desired to set the offset globally.

@benjycui you are aware that you can manually package only the timezones you need for moment timezone? You don't have to pull them all in.
Also, you are aware that if you use moment by itself, it will handle the time zone of the browser without the moment timezone add on?
Finally, as Matt pointed out, this doesn't work in many time zones because they observe DST. If this would fix your problem, may I ask, what problem does it fix?

Before anyone starts work on this - I'd like a poll from the community on whether this would be a useful feature for you, and why.  Please +1 or -1 this comment appropriately. :)

Keep in mind also that you can always set the offset on a per-instance basis.  In fact, there's a second parameter on the utcOffset function that is useful for this.  (We need to document it)  For example:
moment([2016,0,1,12,30]).utcOffset('+08:00', true)  // true makes sure the original local time values persist

@maggiepint yep, I knew that we can import moment-timezone/moment-timezone.
But, for Chinese, or other countries that don't need to handle DST, moment.utcOffset is enough and this will reduce bundle size.
Thanks 😄

This is purely a personal reaction (not representing Moment), but I'm mildly -1 on this (at least until the deprecated #zone API is gone).
I can see the potential value, so I'm not strongly against it.  But many developers already conflate UTC offset with "timezone", and so I think it might invite developer error if we build an API that makes it easier to apply an offset globally than a DST-sensitive timezone.  I suppose this concern could be ameliorated somewhat if we also added a global default timezone setter in Moment Timezone, but then this starts to feel like a bigger implementation project.

I'm -1 on this. Lucas covered it.

-1; why not just implement a wrapper function to generate Moments with that fixed offset?
function zhMoment(){
  return moment.apply(null, arguments).utcOffset('+08:00', true);
}

Well, the jury is in. We're not going to implement this.


Table: init filters.

Please makes sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

#4005

测试挂了

修复了 🤗🤗🤗


Trove Classifier Request: Typing

Request to add a new Trove classifier.
The name of the classifier you would like to add
Something like this:

Programming Language :: Python :: Typing

But I'm sure this isn't perfect name, so I'm open to bikeshedding.
Why do you want to add this classifier?
This should show, that source code either covered by type annotations, or has a .pyi files that accompany sources. Also package should include py.typed file as far as I understand.

highlighting a selection of top contributors from the typing module itself to solicit opinions on this classifier name, thought it seems reasonable to me.
@gvanrossum @ilevkivskyi @ambv @vlasovskikh

I'm not sure how we would spread the word that people should add this classifier.
I'd name it "Typed" rather than "Typing".

I'm not sure how we would spread the word that people should add this classifier.

Looks like this: http://py3readiness.org/ was a great idea, and may be repeated.

I'd name it "Typed" rather than "Typing".

When searching a list I was looking for mypy and typing not sure if I would find Typed. Anyway, may be full name like this would be nice:

Typing :: Typed

Another thought, we may want to distinguish type bindings using .pyi and fully typechecked modules. But I'm not sure if it makes sense.

"Typing :: Typed" is fine.
Distinguishing between the two approaches seems overkill, and in fact it's
totally fine to use a mixture (or use .pyi files to cover extension modules
but inline annotations for the rest).

In aiohttp we have both stubs and inline annotations

FWIW I am equally fine with both Typing and Typed.

Just to clarify, y'all would like: Programming Language :: Python :: Typing :: Typed as your classifier?

I expected bare Typing :: Typed.

Programming Language :: Python makes sense for me

There's no precedent in specifying features of the language used in a project by classifiers under "Programming Language :: Python". I think what we're after here is closer to what "Framework ::" is doing. Thus, I would like to see a bare "Typing :: Typed".

Typing :: Typed has been added on pypi.org and test.pypi.org
happy annotating!

Great, thanks!


Add Matatika ‘analyzer’ plugin

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2720
Originally created by @aphethean on 2021-04-22 15:50:06

Problem to solve
We need to add ‘matatika’ as a plugin of type ‘analyzer', so that meltano users can publish models and reports to the matatika platform from the CLI.
https://www.matatika.com/docs/
Target audience

DevOps / DataOps. A user who defines data models and manages organisation data.
Data analysts. A user who defines data models and creates visualisations.

Further details
As a data analyst, once I have designed a model in meltano I would like a simplified way to 'publish' my models to the matatika 'analyzer'

meltano is well position to centralise the catalog of models
meltano user want to keep meltano models as the single source of truth
meltano is used to 'publish' models in a source controlled / data ops methodology

As a data analyst, once I have designed a report in meltano I would like my report to immediately appear in the matatika platform

meltano UI was used by the data analyst to create a model
meltano UI was used by the data analyst to create a report
meltano user want to keep meltano reports as the single source of truth
meltano is used to 'publish' reports in a source controlled / data ops methodology

As a data analyst, once I have designed a report in meltano I would like my report be converted to the matatika dataset

meltano UI was used by the data analyst to create a model
meltano UI was used by the data analyst to create a report
meltano user want to one time convert the meltano report, and manage the dataset in matatika format going forward
matatika-cli is used to 'publish' reports in a source controlled / data ops methodology

Proposal
DevOps / DataOps (meltano master of models)

Create a meltano model via IDE / text editor, meltano ui, or by extractor dependency
Merge from 'dev' branch to 'production' branch
$ meltano add analyzer matatika
$ meltano invoke matatika publish model [LIST OF MODELS]
meltano has called the 'matatika analyzer' to publish the models

DevOps / DataOps (meltano master of reports)

Create a meltano report via meltano ui, or by extractor dependency
Merge from 'dev' branch to 'production' branch
$ meltano add analyzer matatika
$ meltano invoke matatika publish report [LIST OF REPORTS]
meltano has called the ‘matatika analyzer’ to publish the report

DevOps / DataOps (matatika master of reports)

Create a meltano report via meltano ui, or by extractor dependency
Merge from 'dev' branch to 'production' branch
$ meltano add analyzer matatika
$ meltano invoke matatika convert-report [LIST OF REPORTS]
meltano has called the ‘matatika analyzer’ to convert the report
$ matatika publish datasets/[dataset].yaml

What does success look like, and how can we measure that?
Users are able to choose Meltano or Matatika to 'master' both models and reports and be used in a devops / dataops pipeline to manage the release and rollback of models & reports.
Regression test
(Ensure the feature doesn't cause any regressions)

[ ] Write adequate test cases and submit test results
[ ] Test results should be reviewed by a person from the team

Links / references
Related to meltano-core dependency as this analyzer will need to get model and report metadata inside the plugin venv to publish and convert - #2711
Related to Superset Analyzer - #2605
Related to Jupyter Analyzer - #2595

View 5 previous comments from the original issue on GitLab


Members page Items per page gets bugged

Scenario: Items per page is set to 3
and there are 6 users overall (User 1, ..., User6).

When adding a new user (ex. AddedUser1) all 7 users
(aka. User1, ..., User6, AddedUser1) become visible
even though Items per page is still set to 3.
Also, the Items per page settings stop working entirely and
the page needs to be reloaded.

When removing a user (ex. User1) all 5 users
(aka. User2, ..., User6) become visible
...

this issue is identical with the list sorting issue (waiting on backend)


Enable unchecked and deprecation warnings

Enable unchecked and deprecation warnings.
Fix code to eliminate warnings where possible.
Suppress warnings with comments where elimination is not possible.

Ha... yeah, I kept meaning to at least see what it was complaining about.


Minor docs cleanup

I noticed that there were a few docstrings that had an empty line between them and the method they were documenting. This empty line detaches the docstring from the method so Documented does not include it in the Library (Documenter does not know that those docstrings belong to those methods).
I removed the disclaimer from the Docs/Appendix/Library page. @jagoosw is there still methods/types whose docs don't appear in the library page? Note that since we have private = false, only exported methods/types should appear here.

I also removed the tilmestep wizard from the first example. I thought it's better to keep it as simple as possible for the first example one sees. The particular buoyancy front example keeps CFL < 0.3 with Δt =  2sec.

@jagoosw I don't know if I messed up with the edits in eea66e9. Have a look.

cool, feel free to merge :)

I just thought, given that the Eady problem example has random initial conditions, it might stop it from intermittently failing if we set a random seed.


Improve Result's Display impl for extension values

Previously, the Display impl for vk::Result did not include handling for extension values. For example, VK_ERROR_OUT_OF_DATE_KHR would display simply as "-1000001004".
With this change, we fall back to the Debug impl of the Result if the value is unknown (i.e. from an extension). This preserves the current nice messages for non-extension values, and the numeric output for truly unknown values, but displays the enum variant name (e.g. "ERROR_OUT_OF_DATE_KHR")  for extension-provided enum variants.

@theo3 Awesome, thanks! Merging as soon as the CI succeeds.


Iteration1

Let's merge Iteration1 !

Good job my self! However, your website still looks dumb please add more CSS


[BUG] - ARGO_TOKEN, HERA_TOKEN bug

Describe the bug
https://github.com/nebari-dev/nebari/pulls?q=is%3Apr+sort%3Aupdated-desc+is%3Aclosed had a bug.  The Argo and hera tokens now have an extra "Bearer " at the beginning.

Expected behavior
no extra "Bearer "
OS and architecture in which you are running Nebari
Linux x86-64
How to Reproduce the problem?
see above
Command output
No response
Versions and dependencies used.
No response
Compute environment
None
Integrations
No response
Anything else?
No response

Nevermind, I had a .bash_aliases file that was messing things up


Remove social network JS-bloat and move social buttons to sidebar

Instead of linking those heavy JS-libraries from Facebook or Twitter, I used the simple link-method.
The buttons should work the same way as before and are represented as the logos from FontAwesome.
The "downside": It's a pretty simple integration, so there is no "37 friends of you already likes this"-FB message shown.
On the pro-side:

No more privacy issues.
Cleaner looking page
Faster rendering, because no JS is involved
Saves client bandwith
easier styling

... and because of the last point I moved this part to the sidebar:

This will go live with our next deployment. Thanks for a great contribution @robertmuehsig !


Fix validation to allow parameter object in parameters

Release 0.26.0 has broken validation that doesn't allow Parameter Object in parameters but expects Reference Object. This bug was introduced in https://github.com/zalando-stups/swagger1st/pull/85.
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#operation-object

Codecov Report

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

@@           Coverage Diff           @@
##           master      #92   +/-   ##
=======================================
  Coverage   82.48%   82.48%
=======================================
  Files          12       12
  Lines         902      902
  Branches       17       17
=======================================
  Hits          744      744
  Misses        141      141
  Partials       17       17

Impacted Files
Coverage Δ

src/io/sarnowski/swagger1st/validation.clj
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 f8c949c...bdba3c2. Read the comment docs.

:+1:

👍

👍


PHOENIX-6493 MetaData schemaPattern handling errors

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 23s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

-1 :x:
mvninstall
15m 21s
root in 4.x failed.

+1 :green_heart:
compile
1m  7s
4.x passed

+1 :green_heart:
checkstyle
0m 37s
4.x passed

+1 :green_heart:
javadoc
0m 49s
4.x passed

+0 :ok:
spotbugs
3m 30s
phoenix-core in 4.x has 958 extant spotbugs warnings.

_ Patch Compile Tests _

-1 :x:
mvninstall
6m 31s
root in the patch failed.

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

-1 :x:
checkstyle
0m 35s
phoenix-core: The patch generated 12 new + 420 unchanged - 10 fixed = 432 total (was 430)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 47s
the patch passed

+1 :green_heart:
spotbugs
3m 28s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
200m 26s
phoenix-core in the patch passed.

+1 :green_heart:
asflicense
0m 10s
The patch does not generate ASF License warnings.

236m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1247

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 8517f9228586 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 3836a91

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/1/artifact/yetus-general-check/output/branch-mvninstall-root.txt

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/1/artifact/yetus-general-check/output/patch-mvninstall-root.txt

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/1/testReport/

Max. process+thread count
5143 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

rebased to master HEAD

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
5m 46s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
20m 29s
4.x passed

+1 :green_heart:
compile
1m  5s
4.x passed

+1 :green_heart:
checkstyle
0m 34s
4.x passed

+1 :green_heart:
javadoc
0m 46s
4.x passed

+0 :ok:
spotbugs
3m 20s
phoenix-core in 4.x has 957 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
11m 54s
the patch passed

+1 :green_heart:
compile
1m  6s
the patch passed

+1 :green_heart:
javac
1m  6s
the patch passed

-1 :x:
checkstyle
0m 35s
phoenix-core: The patch generated 2 new + 430 unchanged - 0 fixed = 432 total (was 430)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 47s
the patch passed

+1 :green_heart:
spotbugs
3m 31s
the patch passed

_ Other Tests _

-1 :x:
unit
240m 20s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 47s
The patch does not generate ASF License warnings.

293m 42s

Reason
Tests

Failed junit tests
phoenix.end2end.AuditLoggingIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1247

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux cc0cb4ef3eb6 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 494afff

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/2/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/2/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/2/testReport/

Max. process+thread count
5373 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1247/2/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Exit code -1073741819 - Can't download secure file self-hosted agent.

Question, Bug, or Feature?
Type: Bug
Enter Task Name: Pre-job: DownloadSecureFile, DownloadSecureFile@1
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment

Server - Azure Pipelines or TFS on-premises?

If using TFS on-premises, provide the version: Azure Pipelines with self hosted agent. Agent v2.202.1

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:
DSSINC4, TRM Plus Web, code_test/code_sign_test, #20220518.1

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name:

If using private agent, provide the OS of the machine running the agent and the agent version:
Windows Server 2019, Agent v2.202.1

Issue Description
When trying to download secure file with hosted agent we get an error with node, the tool is in the agent folder and we have tried to remove and install agent again and same thing happening. I tried the job on MS Hosted agent and is able to download the file just fine, but we need this job on our own hosted agent.
Task logs
Logs here:
logs_67237.zip
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Include task name(s), screenshots and any other relevant details]
2022-05-18T14:12:31.1191852Z ##[debug]Evaluating condition for step: 'DownloadSecureFile'
2022-05-18T14:12:31.1277733Z ##[debug]Evaluating: SucceededNode()
2022-05-18T14:12:31.1289018Z ##[debug]Evaluating SucceededNode:
2022-05-18T14:12:31.1361273Z ##[debug]=> True
2022-05-18T14:12:31.1377151Z ##[debug]Result: True
2022-05-18T14:12:31.1458834Z ##[section]Starting: DownloadSecureFile
2022-05-18T14:12:31.2214245Z ==============================================================================
2022-05-18T14:12:31.2215093Z Task         : Download secure file
2022-05-18T14:12:31.2216094Z Description  : Download a secure file to the agent machine
2022-05-18T14:12:31.2216496Z Version      : 1.200.0
2022-05-18T14:12:31.2217042Z Author       : Microsoft Corporation
2022-05-18T14:12:31.2217867Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/download-secure-file
2022-05-18T14:12:31.2218857Z ==============================================================================
2022-05-18T14:12:31.2764838Z ##[debug]Using node path: C:\agent\externals\node10\bin\node.exe
2022-05-18T14:12:33.3892165Z ##[error]Exit code -1073741819 returned from process: file name 'C:\agent\externals\node10\bin\node.exe', arguments '"C:\agent\_work\_tasks\DownloadSecureFile_2a6ca863-f2ce-4f4d-8bcb-15e64608ec4b\1.200.0\predownloadsecurefile.js"'.
2022-05-18T14:12:33.3912859Z ##[debug]Microsoft.VisualStudio.Services.Agent.Util.ProcessExitCodeException: Exit code -1073741819 returned from process: file name 'C:\agent\externals\node10\bin\node.exe', arguments '"C:\agent\_work\_tasks\DownloadSecureFile_2a6ca863-f2ce-4f4d-8bcb-15e64608ec4b\1.200.0\predownloadsecurefile.js"'.
   at Microsoft.VisualStudio.Services.Agent.Util.ProcessInvoker.ExecuteAsync(String workingDirectory, String fileName, String arguments, IDictionary`2 environment, Boolean requireExitCodeZero, Encoding outputEncoding, Boolean killProcessOnCancel, InputQueue`1 redirectStandardIn, Boolean inheritConsoleHandler, Boolean keepStandardInOpen, Boolean highPriorityProcess, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.Agent.ProcessInvokerWrapper.ExecuteAsync(String workingDirectory, String fileName, String arguments, IDictionary`2 environment, Boolean requireExitCodeZero, Encoding outputEncoding, Boolean killProcessOnCancel, InputQueue`1 redirectStandardIn, Boolean inheritConsoleHandler, Boolean keepStandardInOpen, Boolean highPriorityProcess, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.Agent.Worker.Handlers.DefaultStepHost.ExecuteAsync(String workingDirectory, String fileName, String arguments, IDictionary`2 environment, Boolean requireExitCodeZero, Encoding outputEncoding, Boolean killProcessOnCancel, Boolean inheritConsoleHandler, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.Agent.Worker.Handlers.NodeHandler.RunAsync()
   at Microsoft.VisualStudio.Services.Agent.Worker.TaskRunner.RunAsync()
   at Microsoft.VisualStudio.Services.Agent.Worker.StepsRunner.RunStepAsync(IStep step, CancellationToken jobCancellationToken)
2022-05-18T14:12:33.3922954Z ##[section]Finishing: DownloadSecureFile

Hi @adurangalvis, it looks like you have an 0xC0000005 error, according to the MS Codes table -
this is an ERROR_ACCESS_DENIED error it could show up when the NodeJS process doesn't have permission to work with the
"_tmp" agent's folder (e.g.: C:\agent_work_temp in your case).
Could you check if the user under which the agent is running has all the necessary permission to work with the agent folder?
Also, I have implemented a fix to our task-lib to make the error message more user-friendly:

microsoft/azure-pipelines-task-lib/pull/845

@DmitriiBobreshev  thank  you for looking into this. The service account that is running the agent is an admin, but I went ahead and provided explicit permissions to the account to have full access control to root path of agent. I restarted the agent and tried again and unfortunately I get the same error.

I created a new agent and this time made sure I created it with the service account I want it from the beginning. I am still getting the same error, also verified the account has full control on root folder. I also looked at the logs to see the error it is stating in the powershell output put all I see is error it can't find a Java installation.

[2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> +  [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Checking: hive 'LocalMachine', view 'Registry32', key name 'Software\JavaSoft\JRE' [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Key not found. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> +  [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Checking: hive 'LocalMachine', view 'Registry64', key name 'Software\JavaSoft\Java Runtime Environment' [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Key not found. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> + _x64 [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Checking: hive 'LocalMachine', view 'Registry64', key name 'Software\JavaSoft\JRE' [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Key not found. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> + _x64 [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Checking: hive 'LocalMachine', view 'Registry64', key name 'Software\AdoptOpenJDK\JRE' [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Key not found. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> + _x64 [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Checking: hive 'LocalMachine', view 'Registry64', key name 'Software\AdoptOpenJDK\JRE' [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Key not found. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> + _x64 [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Checking: hive 'LocalMachine', view 'Registry64', key name 'Software\Eclipse Foundation\JRE' [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Key not found. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> + _x64 [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Checking: hive 'LocalMachine', view 'Registry64', key name 'Software\Semeru\JRE' [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Key not found. [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: An error occured while trying to sort subkeys for capability as versions:  java_ + <version> + _x64 [2022-06-15 13:59:36Z INFO PowerShellCapabilitiesProvider] STDOUT: Cannot index into a null array.

I also ran a powershellscript to check permissions of the root agent folder in the pipeline.

I logged in as the service account and went to the agent node10 path and tried to run the .js file and didn't get any permissions issues just its missing inputs as expected.

Hello @adurangalvis, thank you for the detailed answer and sorry for the really late response.
As I can see, you have all permissions to _tml folder and probably not with that.
Could you please provide some info about your system such as:

OS version
RAM capacity
Disk Space Capacity
are you using VM/Docker/Containers

This problem also may be related to the RAM problem, when the node process doesn't have enough memory, could you check that you haven't some global options such as --max-old-space-sizesize-in-megabytes and enough memory and disk space on your machine, this would explain the success of your pipeline on ms-hosted agents. also we upgraded task runner to node 16 in version 1.212.0, could you try to run it under node16.

Hi @adurangalvis, thanks again for reporting and sorry for the delay, I'm closing the issue rn due to inactivity, please, feel free to reopen it at any time.


Update contributing docs to use yarn

Summary
I updated the contributing docs to use yarn instead of npm.
Motivation
I was just going through the contributing doc when working on #2489. I didn't have yarn installed globally, and npm install failed...I noticed that many of the scripts use yarn...so I figured I'd update the doc to reflect that.
Test Plan
No tests required, it's just a change to the docs.

Yea, I think this is a good idea. The one thing I'm not 100% sure is using yarn link. I remember having some troubles with it in the past. Does it work correctly now?

Thank you.


chore: add devcontainer setup

This add a devcontainer setup. It means that any contributor no longer has to install various solvers before being able to work on this repo. In addition, it can serve as a reference for the required system setup when somebody wants to use different solvers.
Note that not all solvers are supported yet. I only added support for these for now:

coin_cbc
microlp
highs
lp_solve

You can test the setup by opening the project inside the dev container and then building the crate via
cargo build --features coin_cbc,microlp,lpsolve,highs

Please let me know if something is not working out of the box.

Can we install the same packages as in https://github.com/rust-or/good_lp/blob/main/.github/workflows/rust.yml, and run the tests inside it ?
I fear that if the dev container is not tested, it will just silently break at some point in the future...

This would actually have the advantage that all missing deps would be installed in the dev container

yes!

Awesome, will do!

@lovasoa I've noticed that russcip is able to ship a precompiled binary. Wouldn't it be much simpler if good_lp allowed developers to leverage this so that they don't have to install scip themselves? If yes, this would also drastically simplify the good_lp setup as we wouldn't have to install conda first.

@mmghannam what do you think ? What's the best way to depend on russcip from good-lp ?

Yes, I agree with @KnorpelSenf that it would simplify the developer experience greatly if another feature flag in good_lp would enable the bundled feature in russcip. I still wouldn't  remove the current feature flag as that enables linking to a custom SCIP installation (or linking through conda).

Godd, let's do it that way: add a new flag to goodl-lp and use it on ci

Nice! Please check out #72

@lovasoa this is ready, please TAL

Do we really have to add #[cfg(any(feature = "scip", feature = "scip_bundled"))] everywhere we depend on scip? Can we have a base feature we test against?

How about this?

Also, something is still wrong with the container setup but I don't see it.
If you open the container and run cargo build, it fails with
$ cargo build
    Updating crates.io index
  Downloaded fnv v1.0.7
error: failed to open `/usr/local/cargo/registry/cache/index.crates.io-6f17d22bba15001f/fnv-1.0.7.crate`

Caused by:
  Permission denied (os error 13)

Seems to be related to the cargo install command in the setup script, let me see how this can be fixed

Done.

Thank you!


Switch Button and Y-Axis Title Overlap in Interactive Chart Mode

Describe the bug
Wenn making the Chart mode (normal or 100%) interactive, the switch button and the title of the y-axis overlap.
To Reproduce Steps to reproduce the behavior:

Go to any project (e.g.: visualize)
Start a new visualisation
Select "Columns" or "Areas" as the chart type.
Add a segmentation column in the Chart options.
Change the Chart mode to interactive
Observe the overlapping elements.

Expected behavior
The switch button and the y-axis title should appear one below the other without overlapping.
Screenshots or video

Environment (please complete the following information):

Visualize environment and version: PROD v4.9.3
Browser and version: Microsoft Edge v130.0.2849.56

@noahonyejese i tested again on TEST and the label still overlaps. See here: https://test.visualize.admin.ch/en/v/KDLsGHe4GrX3?dataSource=Prod
If this is completed in a PR - please share the link for the PR or merge the PR to TEST so it can be reviewed. Thank you.

@noahonyejese i tested again on TEST and the label still overlaps. See here: https://test.visualize.admin.ch/en/v/KDLsGHe4GrX3?dataSource=Prod
If this is completed in a PR - please share the link for the PR or merge the PR to TEST so it can be reviewed. Thank you.

@sosiology Not sure why it didn't work I already merged is this working for you --->>> https://visualization-tool-cvh4s3xls-ixt1.vercel.app/?dataSource=Prod

sorry for the inconvenience this may have caused

LGTM, thanks!


Modal Loops usage for ContextMenu

Current solution uses modal loops which should be avoided in the future. figure out a way to use the context menu without modal loops

Context menu now works without modal loops. Current solution may cause performance issues because resized is being called every 500ms.
To revert changes: add JUCE_MODAL_LOOPS_PERMITTED=1 to the jucer file, use showAsync instead of show to display the context menu, and remove the call to resized in PluginEditor::timeCallback.