Loki OTLP ingestion doesn't properly set labels with otelcol.processor.attributes

What's wrong?
Hey everybody,
I'm trying to specify labels when ingesting logs into Loki via the otelcol.exporter.otlphttp exporter component. I want to "relabel" the service.name resource attribute to an attribute app and then add it to the loki.resource.labels or loki.attribute.labels (not sure which one is right here, i tried both). In the steps to reproduce you can see the code. For some reason, the label is not added. This is the output in the livedebugging feature (actual name in Str(...) omitted in the screenshot):

I expected this to work since many other people (and also the docs) do it this way. It's also pretty common in the upstream OTEL Collector, as can be seen here.
I got it working by using another component like this first, but I dont think both should be necessary:
    otelcol.processor.transform "default" {
      log_statements {
        context = "resource"
        statements = [
          "set(attributes[\"app\"], attributes[\"service.name\"])",
        ]
      }

      output {
        logs   = [otelcol.processor.attributes.default.input]
      }
    }

Steps to reproduce
Add this otelcol component configuration to your alloy config.
    otelcol.processor.attributes "default" {
      // Extract app name from service.name attribute
      action {
        key = "app"
        from_attribute = "service.name"
        action = "upsert"
      }

      // Generate loki labels from OpenTelemetry attributes
      action {
        key = "loki.attribute.labels"
        action = "insert"
        value = "service.name,app"  // comma separated list
      }

      output {
        logs = [otelcol.processor.batch.default.input]
      }
  }

System information
No response
Software version
Grafana Alloy Helm Chart v0.9.1
Configuration

Logs

Issue on my side. The docs dont clearly state that you have to disable the defaults for OLTP in the loki config itself.


Using wmi

This changes how the  beacon configures the folders for auditing.  Before it used powershell command set-acl which does not work on c:\Users and most importantly c:\windows.  I instead had to use WMI, which does not have that restriction.  With that I also found i need to change the remove ACE function to use WMI as well, since you also cannot remove ACEs from c:\windows using native powershell commands.
I also fixed many bugs. Most notably the bug that was using the parent path of the exclude instead of the exclude path.  Example: auditing c:\windows but excluding c:\windows\system32, would actually remove the ACEs from c:\windows, instead of the system32 folder.  Other minor bug fixes as well

Left one comment inline. Otherwise looks great.

The _remove_acl function is just removing the ACE flag that marks the folder for monitoring.  If for some reason someone wants to monitor <c:\users> and all subfolders, but not <c:\users*\desktop> and subfolders, this gives them that option.

Good catch on both of those.  Fixed in e713db20b2736d8426fc12769e602a1a000b57c6 diff


Multiple initial values for ode

Motivations:

PR #104 introduced the possibility of setting multiple values to fixed parameters
It let the user choose whether he wants a systematic exploration of all combinations of values (grid=True) or to pick only cases of interest (grid=False, default)
The same would be useful for initial values of ode

Proposition:

Implement the possibility of setting multiple values for initial values of lde (using arrays)
It will probably imply small modifications of attribute Hub.dmisc['dmulti']
Make the grid option more flexible:

now it's either grid=True for all or grid=False for all
It would be nice if the user could choose to set grid=True just for some parameters / initial values he picks. This would allow to combine cherry-picking of cases of interest with systematic exploration of some parameters only.

It'd be very practical to have the ODE initial conditions indeed !
I think the grid is not too important (compared to multisectorial/EDP) but if it's rapid for you to implement that's a good enhancement


client: don't panic if server is not running

When server is not running, goobs.New() panics.

Thank you thank you! 🙇


Consider using lvgl v7.0.0

lvgl v7.0.0 was recently released. It may be worth-while to upgrade to it, considering this project is still in it's early stages.

Good idea, shouldn't be hard to do that right now. As I was working mostly on the internal design of the library itself. Only a few (button, label) widgets are implemented.

I'm working on this.


Make Contribution Trends a pie chart

A pie chart is more observable of what you're doing. Or provide it as an opt-in for users.
/kind feature

A pie chart is more observable of what you're doing. Or provide it as an opt-in for users.
/kind feature

Hi @kerthcet，that's a good way to display the percentage of each contributions with a pie chart. Nice suggestion👍  By the way, would you like to have a conversation in our Discussions(click the Discussions near the Pull request btn)?  We can talk more about the feature design in a better way.

Done at https://github.com/pingcap/ossinsight/discussions/1000

nice issue id

Move to discussion.


Extension sending invalid queries to Apollo studio

It appears that using fragment queries with this extension attaches an extra } to the end of the fragment portion when sending to Apollo Studio, causing parse errors for the vast majority of my queries. Here's an example of what I see in Apollo Studio:

And the query in question:
fragment missingCaps on MissingCapabilities {
  __typename
  message
  required
  oneof
}
fragment pilot on Pilot {
  id
  name
}

fragment catchAll on Error {
  __typename
  message
}
query pilotList {
  operatorList(role: ROLE_PILOT) {
    ... on SpecificOperatorConnection {
      edges {
        node {
          __typename
          ...pilot
        }
        __typename
      }
      __typename
    }
    ...missingCaps
    ...catchAll
    __typename
  }
}

And what Apollo Studio sees:
fragment missingCaps on MissingCapabilities{ __typename message required oneof }} fragment pilot on Pilot{ id name }} fragment catchAll on Error{ __typename message }} query pilotList { operatorList(role: ROLE_PILOT) { ... on SpecificOperatorConnection { edges { node { __typename ... pilot } __typename } __typename } ... missingCaps ... catchAll __typename } }

Every fragment has a } added into it causing the issue.

I'll have time to fix it this week-end

Any update on this?


RedissonLock.renewExpiration will refresh forever

Expected behavior
If the lock key no longer exist the refresh should cease
Actual behavior
The renewExpiration() method ignores the return value of renewExpirationAsync() and reschedules itself forever
Steps to reproduce or test case
Should be as simple as manually removing a lock entry key from redis.
Redisson version
3.10.6
On a side note, another thing we noticed while looking into this is that renewExpirationAsync() does a scripted call that returns 0 or 1 depending on HEXISTS. It seems unnecessary as according to the redis docs about PEXPIRE, it does the same thing out of the box in a single command call (https://redis.io/commands/pexpire).

Thanks for report! This is a regression since 3.10.5 version.

Fixed


Remove "spins" flag from diagnostics

We're removing the spins flag from the node stats API in 6.0 (see https://github.com/elastic/elasticsearch/issues/24390) and I think you include this flag in visualizations so I just wanted to give you a heads-up so the support tools don't break.

@danielmitterdorfer Thanks. It's not currently used, but I had considered including it so thanks for the heads up.

You're welcome. I think we can then close the issue again @nemonster?

@danielmitterdorfer Absolutely. Got sidetracked for bugpool. Closing now.


Add ACVP tests

For FIPS validation purposes - Automated Cryptographic Validation Protocol (ACVP) tests need to be performed. (See https://github.com/usnistgov/ACVP). These tests are very similiar to the old CAVS tests.
This PR uses a hardwired subset of these test vectors to perform similiar operations,
to show the usage and prove that the API's are able to perform the required operations.
It may also help with communication with the lab (i.e- The lab could add a test here to show
a unworking use case - which we can then address).
The EVP layer performs these tests instead of calling lower level API's
as was done in the old FOM.
Some of these tests require access to internals that are not normally allowed/required.
The config option 'acvp_tests' (enabled by default) has been added so that this
access may be removed.
The mechanism has been implemented as additional OSSL_PARAM values that can be set and get. A callback mechanism did not seem to add any additional benefit.
These params will not be added to the gettables lists.

Checklist

[ ] documentation is added or updated
[x] tests are added or updated

This is not is a reviewable state yet - just up here as a reference while I rebase.

rebased..
ping

Travis failure appears relevant.

Updated PR to address review comments.

rebased and removed doc for setting DH_group_name

Travis failure looks relevant (md nits)

Travis failure is now not relevant.

ping

This pull request is ready to merge

Thanks. Merged to master.


Implemented Replay Buffer requests/events

Accidentally included some files I didn't mean to. Had to do a force push on my repo, I'll open another pull request.


[SourceKit] Include trailing where clause in SourceRange

This PR updates the SourceRange (sourcekit structure key.offset/key.length) calculation for cases where the last thing in a declaration is a where clause [or a throws, found in passing].
This is pretty rare - protocol members and typealias/assoctype with where.
The current behavior skipping the where means that downstream tools using SourceKit doc structure can miss out the throws/where parts when chopping up files.
Added tests - previously these would put the </ifunc> etc. too early.
@nkcsgexi could you review please?

@swift-ci please smoke test


fix bug about webflux broken trace

Please answer these questions before submitting a pull request

Why submit this pull request?

[x] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.
https://github.com/apache/skywalking/issues/5184
the trace of webflux application which use @RequestBody is broken
https://github.com/apache/skywalking/issues/4957
skywalking has some problem with webflux
How to fix?
I put the stopSpan operation in DispatcherHandlerHandleMethodInterceptor from  beforeMethod to afterMethod

New feature or improvement

Describe the details and related test reports.

@ascrutae I will wait for your confirmation.

@wu-sheng  The #5184 and #4957 is not caused by webflux plugin, it cause by that the spring plugin doesn't active.

@ascrutae I close this for now. Wait for your fix.

Got it!
On Aug 18, 2020, 10:19 AM +0800, 吴晟 Wu Sheng<EMAIL_ADDRESS>wrote:

@ascrutae I close this for now. Wait for your fix.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Is this webflux use @requestbody with problem solved?  i have same question, Can you give me some ideas?

@wu-sheng @ascrutae any update?

any update? I had the same problem... @wu-sheng @ascrutae


fix(indexes): allow None primary_key in add_or_update function

Pull Request
Related issue
Cannot pass None value to add_or_update function
What does this PR do?
Replace impl AsRef<str> to &str
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Hi @curquiza , sorry for the late response. I added the test case.

bors try


Feat/user admin

Pull the branch into local for testing.

run yarn install than yarn run serve

On the UI - click on Sign In button from the header view.

Use the credentials - "username - admin", "password - JW24G.xR" and login.

The admin panel can be viewed similar to that of prototype.

I don't have much experience with front-end development. Did you change the package manager from yarn to npm? Can both be used interchangeably or in parallel, or did you just get that mixed up?

I think i got mixed up while adding new packages to the repo and installing the dependencies. Will remove the package-lock.json file and update the PR. Continue using yarn instead of npm for better performance of installing larger package files.

ok, thanks for explaining and the changes.
btw: I started reviewing this pull-request, but it will take time. Previously I thought it would be better if you just push directly to develop, but I changed my mind. I think it is a good idea for me to review this because I need to learn more about the front-end.

ok, thanks for explaining and the changes. btw: I started reviewing this pull-request, but it will take time. Previously I thought it would be better if you just push directly to develop, but I changed my mind. I think it is a good idea for me to review this because I need to learn more about the front-end.

Sure, just for an overview - the new feature changes related to Sign In button were in src/layout/navigation-menu -> index.vue, and in components module login and modal were added new. Apart from that, all the other components are added from the admin repo. No logical changes in here.

Ok, I am through with looking at this pull request. I am a impressed that you could move all code from the previous admin-frontend to the user-frontend without problems. Here are some things that you could maybe change:

src/axios-config.ts: you set baseURL to http://ola-hd.sub.uni-goettingen.de/api/. I think you did this for testing but forgot to remove before committing. Btw, that is the "old" Prototype backend, maybe our dev-server (http://<IP_ADDRESS>/api/) or staging-server (http://<IP_ADDRESS>/api) would be better, but currently no big difference.
src/router/index.ts: route dashview (Line 63). 3 child-components are set. One has path "", name "home" and component "Dashboard". I don't know much about vue and everything but maybe this has to be Home as a Component like in line 20? And I think I get warn-messages about this when using dev-tools, but I'm not sure.
After login, I would prefer the dashboard to be shown without the search on top, but I think that is a decision of PO
In the table of the dasboard the PID of an uploaded archive is a link. Previously in the Dashboard, this fact was a bit more visible from my point of view, because the PID was in blue other than the other columns. Maybe you can make it more visible (blue?) that this PID can be clicked like previously.

Ok, I am through with looking at this pull request. I am impressed that you could move all code from the previous admin-frontend to the user-frontend without problems. Here are some things that you could maybe change:

src/axios-config.ts: you set baseURL to http://ola-hd.sub.uni-goettingen.de/api/. I think you did this for testing but forgot to remove before committing. Btw, that is the "old" Prototype backend, maybe our dev-server (http://<IP_ADDRESS>/api/) or staging-server (http://<IP_ADDRESS>/api) would be better, but currently no big difference.
src/router/index.ts: route dashview (Line 63). 3 child-components are set. One has path "", name "home" and component "Dashboard". I don't know much about vue and everything but maybe this has to be Home as a Component like in line 20? And I think I get warn-messages about this when using dev-tools, but I'm not sure.
After login, I would prefer the dashboard to be shown without the search on top, but I think that is a decision of PO
In the table of the dasboard the PID of an uploaded archive is a link. Previously in the Dashboard, this fact was a bit more visible from my point of view, because the PID was in blue other than the other columns. Maybe you can make it more visible (blue?) that this PID can be clicked like previously.

fixed warning error of routing in console dev tools, changed pid text color to use blue and changed base url in axios config file.
The search on top is a part of the current user story Search Implementation, so once this is added, than we can view the dashboard without search on top.

Ok I testet the changes LGTM now execept the thing about src/axios-config.ts, sry for possible confusing. Next try of explanation:
What a said was just about the local development environment. If you want to use the frontend for development and start it with yarn on your own machine, /api will not be available so you insert what you did into the src/axios-config.ts as a workaround to be able to test how everything works in conjunction with the backend. But when we deploy the whole programm (backend + frontend) on our vms we need the code that i posted there.
About search, sry, I maybe dimly rember you already said that in one of our meetings.

Ok I testet the changes LGTM now except the thing about src/axios-config.ts, sry for possible confusing. Next try of explanation: What a said was just about the local development environment. If you want to use the frontend for development and start it with yarn on your own machine, /api will not be available so you insert what you did into the src/axios-config.ts as a workaround to be able to test how everything works in conjunction with the backend. But when we deploy the whole programm (backend + frontend) on our vms we need the code that i posted there. About search, sry, I maybe dimly rember you already said that in one of our meetings.

Yes, for frontend testing purpose i have used the dev-server url. I have changed to use /api/ and updated the PR.


Feature Request: account for a space between ! and command for example ! motivation

[q:master] 1 new commit by Michael Henry:
bb2db8e Added logic to account for space after ! which is amazingly provided by AutoCorrect - Michael Henry


Create groovy Shared libraries for Jenkins pipeline.

In order to reduce code duplication in Jenkinsfile, we need to create libaries according to https://jenkins.io/doc/book/pipeline/shared-libraries/

Created initial libraries herer https://github.com/istio/istio-testing/tree/master/src/org/istio/testutils

I think the initial libraries are sufficient. We can create an issue for specific library needs. Closing this.


V2 Metadata Audit for Images

Purpose
Review incoming Sierra metadata for Images and make recommendations for testing #3693
In scope
info hierarchy and grouping, rewording, any data clean up
TODO

[x] Review Work ID Definitions
[x] Review Item examples
[ ] Make recommendations

Audit
https://docs.google.com/spreadsheets/d/1ZLoPOnVBpNS40gYjCfTcp_M-YaEALkTkEoAWvxQr3sA/edit?usp=sharing
Concepts
WC_V2 MetaData Audit - Concept.pdf

Concepts

WC_V2 MetaData Audit - Concept1.pdf
WC_V2 MetaData Audit - Concept2.pdf

Update from the meeting with Silver
For Silver

Review Work Type and Genre with Experience team
Cover SubFields in the domain model meeting
Share the list of data fields that may be useful for Works

For Experience Team

Analysis of 'Title' fields length
Analysis of most commonly catalogued fields

Update V2 @gestchild

Group 'Physical description', 'Extent' and 'Dimension' fields as a single component
Display 'Production' data as a single component (Places, Agents, Date)
Remove link from 'Dimension'
Remove 'Type' field


Sample v20170701/kubernetes.json can't be generated

Is this a request for help?:
Yes
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes, v 1.6.6
What happened:
I would like to generate the kubernetes sample with kubernetes v1.6.6. I got the folliwing error messsage.
root@db91de4dd3b3:/gopath/src/github.com/Azure/acs-engine# ./acs-engine generate examples/v20170701/kubernetes.json
FATA[0000] error parsing the api model: unrecognized APIVersion '2017-07-01'

What you expected to happen:
I'm expecting the generation works fine with the given samples.
How to reproduce it (as minimally and precisely as possible):
pull master branch
run scripts/devenv.ps1
(inside the container) run ./acs-engine generate examples/v20170701/kubernetes.json

My bad, I do not re-run the requireds commands before re-generate this sample.
make prereqs
make build


Add a new issue template for crashes

[ ] Should explain where log files are found (At the top of the text! In the current template it's at the bottom where it's easily missed)
[ ] Should add an special label to the issue

@R3voA3 Thanks for the suggestions, we specifically leave out the labels because we found that users often used to the wrong template when creating issues. It saves more time when we add labels to the issues ourselves. Do you want to make the change with the instructions for the log files?

<!---⬆Select Preview for easier reading⬆
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. Issue might get deleted if it is not following the template
2. Only post one issue per bug report
3. Try to avoid duplicates. Do a quick search before posting
4. Add a descriptive title
--->

**Describe the bug**
A clear and concise description of what the bug is.

**To reproduce**
Steps to reproduce the behavior:
1. Go to '....'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Log file**
Please upload the log file here so that we can understand your issue better.
* You can access it from Settings->About->Open log location.
or
* `%localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState`

You should see a file in this directory called debug.txt or/and debug_fulltrust.txt.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**System Information**
 - OS Version: [e.g. Windows 10 20H2 19042.804] (Press WIN + PAUSE/BREAK, use the copy button at them bottom)
 - App version: [e.g. v1.0] (In the app, go to Settings -> About, the version is shown at the top)

**Additional context**
Add any other context about the problem here. Does this problem occur again after restarting the app?

That's how I would change it.

It's a bit shorter now, less reading required
Added shortcut to get the system information quicker
Log entry was moved up to it's not missed (Scrolling was needed before)

Raw text

Preview*

@R3voA3 Thank you!


For types under stateful metrics, it is not forcing both a check that the string exists and also that it is a string value

I was able to have an actual int type instead of the string for example

Need to add the json


Stack does not exist any more, I can't remove it, but it is still in the list

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
Hello,
I somehow managed to add a stack, but after it failed to deploy, and I exited the window, so the stack should not be saved, a stack was created but is totally empty.
Wenn I open it shows the error:
Failure
could not get the contents of the file 'docker-compose.yml'
The docker-compose file does not exist, and nothing changes if I create it manually.
I can't remove it, because it says:
Failure
failed to remove a stack:
No container is running.
What can I do to remove the stack, I don't want to reinstall portainer and all my stacks.
I deleted the portainer container and recreated it, but the error seems to be in de portainer database.
Expected Behavior
I want to delete the stack.
Actual Behavior
I can't delete or repair the stack.
Steps to Reproduce
I don't know how to reproduce, because after that I created other stacks that worked fine.
Portainer logs or screenshots
No response
Portainer version
2.18.4
Portainer Edition
Community Edition (CE)
Platform and Version
Ubuntu 22.04 LXC in Proxmox 8.0.4
OS and Architecture
Ubuntu 22.04 LXC in Proxmox 8.0.4
Browser
All Browsers
What command did you use to deploy Portainer?
No response
Additional Information
No response

I'm having an almost identical issue. A stack could not be removed (I do not remember the error message). After removing all parts of the stack (containers, images), it still could not be removed. Unfortunately, I could not find any instructions on how to remove the stack manually in any way. Also, it cannot be edited/updated.
When opening the stack, I get this error message
Failure
could not get the contents of the file 'docker-compose.yml'

When trying to remove the stack, I get this error message:
Failure
failed to remove a stack: docker compose command failed: chdir /data/compose/1: no such file or directory

Ok, here is a workaround for this problem. The message "could not get the contents of the file 'docker-compose.yml'" refers to a missing folder under /var/lib/docker/volumes/portainer_data/data/compose. The corresponding folder number is the number in "failed to remove a stack: docker compose command failed: chdir /data/compose/1: no such file or directory". In this case, it is number 1. I copied an existing folder in /var/lib/docker/volumes/portainer_data/data/compose and renamed it to 1, for example. After that, I was able to remove the stack.

Ok, here is a workaround for this problem. The message "could not get the contents of the file 'docker-compose.yml'" refers to a missing folder under /var/lib/docker/volumes/portainer_data/data/compose. The corresponding folder number is the number in "failed to remove a stack: docker compose command failed: chdir /data/compose/1: no such file or directory". In this case, it is number 1. I copied an existing folder in /var/lib/docker/volumes/portainer_data/data/compose and renamed it to 1, for example. After that, I was able to remove the stack.

That worked for me too, thank you!

I just stopped a stack in Portainer and deleted it straight away.... then I got the message that it couldn't be deleted. ... how do I get rid of it? it is empty but still in the list.

After I shut down and restarted everything (containers and host) the stack was gone. Still don't know what happened.

+1

Ok, here is a workaround for this problem. The message "could not get the contents of the file 'docker-compose.yml'" refers to a missing folder under /var/lib/docker/volumes/portainer_data/data/compose. The corresponding folder number is the number in "failed to remove a stack: docker compose command failed: chdir /data/compose/1: no such file or directory". In this case, it is number 1. I copied an existing folder in /var/lib/docker/volumes/portainer_data/data/compose and renamed it to 1, for example. After that, I was able to remove the stack.

To add, if portainer has set up data persistence, check the number directory under the compose directory in the data persistence directory, and add the corresponding number directory and docker-compose.yml here.

Im in the same situation after manually deleting some versions of the docker-compose stacks.
I was thinking that by deleting them portianer will also "forget" them but it doesnt actually parse the directory to check the versions that exist, it stores the information in some kind of DB and search for the paths he takes form there.
We need either a way to scan the main directory or edit the paths our selfs. in the same logic we can also delete old versions..
I dont find any reason to keep 20 versions of the same stack without having a way to remove them.
*I will make a new issue as well and reference this one as this issue will fix both situations.

Just had this happen again, did the old method, worked.
Portainer 2.20.1
Docker version 26.0.2, build 3c863ff

Ok, here is a workaround for this problem. The message "could not get the contents of the file 'docker-compose.yml'" refers to a missing folder under /var/lib/docker/volumes/portainer_data/data/compose. The corresponding folder number is the number in "failed to remove a stack: docker compose command failed: chdir /data/compose/1: no such file or directory". In this case, it is number 1. I copied an existing folder in /var/lib/docker/volumes/portainer_data/data/compose and renamed it to 1, for example. After that, I was able to remove the stack.

This worked. I have a bind mount for /data in docker-compose.yml for portainer-ee
Had to look at the error, navigate to /data/compose/"error message location" directory add a few folders and docker-compose.yml then was able to delete in portainer.
This happened around when i was stopping and deleting the container too fast in portainer UI I suppose.
I updated docker and portainer to see if it would fix but it did not. So fixed, hopefully doesn't happen again, since I was on a version earlier, and today they just released 2.20.2 portainer.

Same here on Portainer version 2.20.2.
The solution by @cwm77 works.

Same issue on Portainer version 2.19.5
In my case the woraround from @cwm77 also worked :)

same here.
How many more confimations they need?

same here, i try to delete a stack, the container are deleted, but the stack is not. then it cannot be removed, updated or started

is there any fix to this other than to mimic recreating the paths? This bug is notorious.

I cannot create any stack on Portainer using "Repository" build method.
Any idea? I try solution from @cwm77 but unfortunately it is not working.

Stack 3 is working stack build using "web editor" not "repository". I tried copy stack "3" and create "35" but this operation do not fix it unfortunately. Any idea?

Please note that by default Portainer looks for a .yml file and not a .yaml file

Same issue

still happens. I think if the compose path is broken for a stack, we should still be allowed to delete the stack as it's rogue anyway. The only solution Ive found to delete it is to mock up the path that's missing so it can be deleted.

Ok, here is a workaround for this problem. The message "could not get the contents of the file 'docker-compose.yml'" refers to a missing folder under /var/lib/docker/volumes/portainer_data/data/compose. The corresponding folder number is the number in "failed to remove a stack: docker compose command failed: chdir /data/compose/1: no such file or directory". In this case, it is number 1. I copied an existing folder in /var/lib/docker/volumes/portainer_data/data/compose and renamed it to 1, for example. After that, I was able to remove the stack.

This worked for me on Business Edition 2.19.5

maybe irrelevant, just for someone else in the future: try restarting docker service.
ref. https://github.com/portainer/portainer/issues/10036#issuecomment-1766194787

The workaround doesn't seem to be working for me, I'm getting the message chdir /data/compose/211/3c1b7d20efc7fb6d7be6e1421ba833af84bd2181: no such file or directory so created the directory and copied over contents from another one in the 211 dir but I'm still getting the same error.

Also have this issue - Restarter docker and still showing
Failed to remove a stack: docker compose command failed: chdir /data/compose/14/f902249ebc27a1397bc8e03ef56b99bfd7402b08: no such file or directory

I have a similar issue. The stack can be queried via rest api, but the endpoint does not exist anymore. so i can't delete the stack, because it gives me the message: Unable to find the endpoint associated to the stack inside the database

I really wish they would fix this. It's very annoying. Any update?

Same here, please fix this.

Same issue tried copying a directory as suggested but didn't work for me.

I just stopped a stack in Portainer and deleted it straight away.... then I got the message that it couldn't be deleted. ... how do I get rid of it? it is empty but still in the list.

I have exactly the same issue with the same number. My stack is integrated with gitlab.com


would like a unique key in event json to simplify ticketing/event aggregation system.

We are sending sensu events to sentry (getsentry.com) for logging/event aggregation. Something that would be useful for us (and I think other people if they try tying sensu into a ticketing system) is a unique value (stored as part of the event output) that is generated/stored on the sensu server on the first 1 or 2 status and remains the same until the status returns to 0.
That way we can categorize/aggregate events based on this value so that a check disk usage % will have the same ticket associated with it from a warning state, to critica,l to resolved...
Thanks!

+1

On Mar 22, 2016, at 6:19 PM, Joshua Zitting<EMAIL_ADDRESS>wrote:
We are sending sensu events to sentry (getsentry.com) for logging/event aggregation. Something that would be useful for us (and I think other people if they try tying sensu into a ticketing system) is a unique value that is generated/stored on the sensu server on the first 1 or 2 status and remains the same until the status returns to 0.
That way we can categorize/aggregate events based on this value so that a check disk usage % will have the same ticket associated with it from a warning state, to critica,l to resolved...
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub https://github.com/sensu/sensu/issues/1196

Event IDs (uuid values) already exist (although they aren't documented anywhere), however not in a way that would be useful in this context. Currently event IDs are unique to each occurrence of the event, which isn't necessarily incorrect behavior, but it's also not very useful. Furthermore, event IDs are not used anywhere else in Sensu, so there's no reason we can't make event ids more useful by making them correspond to a specific event.
:+1:

https://github.com/sensu/sensu/blob/master/lib/sensu/server/process.rb#L447
Make it:
:id => stored_event ? stored_event[:id] : random_uuid,

Sweet! I cant wait for this one to be merged! Thanks guys!!

Related: https://github.com/sensu/sensu/issues/849

Just about time to merge https://github.com/sensu/sensu/pull/1248 :+1:

https://github.com/sensu/sensu/pull/1248 has been merged, the change will be available in the upcoming 0.24 release!


No binary after installing bundler

I'm using rbenv 1.0.0-21-g9fdce5d.
I have problems installing bundler. These are my commands I used:
$ rbenv versions
  system
  2.1.5
* 2.3.0 (set by .../.ruby-version)
$ gem install bundler
Successfully installed bundler-1.12.3
1 gem installed
$ rbenv rehash
$ bundle install
rbenv: bundle: command not found

The `bundle' command exists in these Ruby versions:
  2.1.5
$ rbenv whence bundler
2.1.5

What can I do to fix this? Thank's!

I switched to chruby and ruby-install. It works fine with that.

Hi, I'm not sure what the issue was (it seems that you've done everything correctly), but I'm glad that you found a solution that works for you!


Add screw-holes on the corners of the bottom PCB for standoffs/feet

An example setup I like from my previous keyboard: they have some pads, with an optional "tilt" screwhole spots for a higher raised feet set on the back.

Having some screw-in feet that are interchangeable/adjustable would be super lovely.

Implemented by 14b9a9be80fa695a1f35e55d81ed551870d70178


ArraySegment usage

When reading the events, the sample calls the method ToArray() to create an array from ArraySegment, what defeats the benefits of using ArraySegment and creates another copy of the array:
Console.WriteLine("\tRecevied event: {0}", Encoding.UTF8.GetString(eventArgs.Data.Body.ToArray()));
It should be:
Console.WriteLine("\tRecevied event: {0}", Encoding.UTF8.GetString(eventArgs.Data.Body.Array, eventArgs.Data.Body.Offset, eventArgs.Data.Body.Count));
it is also more consistent with other docs:
https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-dotnet-standard-get-started-send-legacy#receive-events
https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-event-processor-host#ieventprocessor-interface

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

ID: c4c6d63e-95f5-de2c-972b-4da5fe71a6a6
Version Independent ID: 338bbd1b-d86d-ff48-0b8a-1d48cb9547f2
Content: Send or receive events from Azure Event Hubs using .NET (latest) - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

@felipepessoto  - Thanks for your contribution, I've addressed this issue in PR: MicrosoftDocs/azure-docs-pr/pull/130692
The changes should be live soon once author reviews them. In future, if you see any minor bug fixes in the doc, feel free to click on the edit button and submit a PR to update. we love to take community contributions.

The PR link is broken

PR is merged now, document shows latest changes when publishing completes. I am closing this issue, please feel free to post for further queries.

@spelluru - Kindly take a look and share your thoughts.

@felipepessoto - Thanks for the feedback. Have you tried the suggested change with the quickstart that uses the Azure.Messaging.EventHubs package? Thanks.

With the Microsoft.Azure.EventHubs package, Body is of type ArraySegment
With the latest Azure.Messaging.EventHubs package, Body is of type ReadOnlyMemory

My bad, I was using the Microsoft.Azure.EventHubs package.
Thanks

@felipepessoto - No problem at all. Regards


[iPad] GestureDetector gets stuck in a "pressed" state if pressed when the keyboard is hiding

Steps to Reproduce

Run sample on iPad (landscape mode, but portrait should be broken too)  (see "Code sample" section below)
Click TextField (Red area) and make sure the keyboard appeared
Press the button ("Do Nothing\nButton") and hold a second till the keyboard is gone
Release the button
Or even try just clicking over the button without the "long press."

Expected results:
Should work consistently with iOS/Android/Web (at least)
The button becomes unpressed; dialog should be shown (click handler)
Actual results:
The button remains "pressed", and no dialog is shown (click handler)

Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key});
  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: SafeArea(
        child: Column(
          crossAxisAlignment: CrossAxisAlignment.stretch,
          children: [
            Expanded(
              child: SingleChildScrollView(
                child: Column(
                  children: [
                    ColoredBox(
                      color: Colors.red,
                      child: TextField(
                        minLines: 100,
                        maxLines: 100,
                        onTapOutside: (_) => FocusScope.of(context).unfocus(),
                      ),
                    ),
                  ],
                ),
              ),
            ),
            OutlinedButton(
              onPressed: () => showDialog(
                  context: context,
                  builder: (context) => AlertDialog(
                        title: const Text('Alert Dialog'),
                        content: const Text('This is an alert dialog.'),
                        actions: [
                          TextButton(
                            onPressed: () => Navigator.of(context).pop(),
                            child: const Text('OK'),
                          ),
                        ],
                      )),
              child: const Text('Do Nothing\nButton'),
            ),
          ],
        ),
      ),
    );
  }
}

Logs
[✓] Flutter (Channel stable, 3.7.7, on macOS 13.0 22A380 darwin-x64, locale en)
    • Flutter version 3.7.7 on channel stable at /Users/andrei/Desktop/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2ad6cd72c0 (5 days ago), 2023-03-08 09:41:59 -0800
    • Engine revision 1837b5be5f
    • Dart version 2.19.4
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/andrei/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.76.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (3 available)
    • iPad (10th generation) (mobile) • C5E95963-35D5-4306-A28D-D37780516E1F •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
    • macOS (desktop)                 • macos                                •
      darwin-x64     • macOS 13.0 22A380 darwin-x64
    • Chrome (web)                    • chrome                               •
      web-javascript • Google Chrome 111.0.5563.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Issue is reproducible using the code sample provided above. The bug reproduces only on iPad, on my iPhone it worked just fine. See the recordings below.
Labeling for further investigation.

recordings

iPad
iPhone

flutter doctor -v
[✓] Flutter (Channel stable, 3.7.7, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.7.7 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2ad6cd72c0 (6 days ago), 2023-03-08 09:41:59 -0800
    • Engine revision 1837b5be5f
    • Dart version 2.19.4
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.4
    • Dart plugin version 223.8888

[✓] VS Code (version 1.76.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (4 available)
    • M2007J20CG (mobile)  • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E                  • ios            • iOS 16.3.1 20D67
    • macOS (desktop)      • macos                                      • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)         • chrome                                     • web-javascript • Google Chrome 111.0.5563.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[!] Flutter (Channel master, 3.9.0-1.0.pre.184, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.9.0-1.0.pre.184 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ac4a1d294a (2 hours ago), 2023-03-14 02:22:24 -0400
    • Engine revision be5f826135
    • Dart version 3.0.0 (build 3.0.0-322.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.4
    • Dart plugin version 223.8888

[✓] VS Code (version 1.76.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (4 available)
    • M2007J20CG (mobile)  • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E                  • ios            • iOS 16.3.1 20D67
    • macOS (desktop)      • macos                                      • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)         • chrome                                     • web-javascript • Google Chrome 111.0.5563.64
    ! Error: Dean’s iPad is busy: Fetching debug symbols for Dean’s iPad. Xcode will continue when Dean’s iPad is finished. (code -10)

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

cc @Renzo-Olivares


Unstoppable playbook runtime if target channel renamed

Hi there
Steps to reproduce:

start a playbook runtime
rename target channel
press "Go to channel" from runtime page

By the end we have endlessly runtime with "freezed" state. and this writes messages to members every day. without ability to stop runtime
Official way to stop it: press "Go to channel" button and execute '/playbook finish'. But then target channel was renamed you have "Channel Not Found" error
I try to archive parent playbook but this runtime still run
Seems like there is no "simple" way to drop it
May be you can told me legitimately query to DB for delete this runtime like WA?

@woodman733 Would you be open to re-opening this in the Playbooks repo with details on your Mattermost server version https://github.com/mattermost/mattermost-plugin-playbooks/issues?


Missing the occasional row or column of pixels -- possible DPI issue?

Windows Terminal version (or Windows build number)
1.8.1444.0
Other Software
No response
Steps to reproduce
Have output in the terminal.
I suspect this is DPI related, as I have the following set:

Expected Behavior
Font rendering is consistent in all rows and columns, and matches legacy terminal:

Actual Behavior

(I promise that's unmodified except for adding the arrows in mspaint.)

I remember there's a dup issue for rendering issues caused by custom DPI but I couldn't find it...

The support for custom DPI is currently not that good atm. You'll be fine if you're using 150% or 200%, but there might be some rendering glitches (for example #4591) if you're using 114% (really?) or something like that.

This does look like a /duplicate of #4591; thanks for bringing this up!

if you're using 114% (really?) or something like that.

Yes.  I set the DPI to what the screen's DPI actually is, whether in Windows or GNOME or ...
(Was the "(really?)" necessary?  It doesn't seem unreasonable to expect a "modern" terminal application to be doing DPI correctly.)

@scottmcm Sorry for the vibe of my response if that made you uncomfortable. Yeah it's totally reasonable to expect Windows Terminal to be handling DPI correctly. Just that terminal is still a rather "young" project comparing to the other competitors. There's a lot of things need polishing right now.
I speak for my own and not my company. Also I'm not part of the dev team of the terminal.


Minor fix

> void Misc::fakeBan(bool set) noexcept {
>     static bool shouldSet = false;
>     if (set)
>         shouldSet = set;
>     std::stringstream ss;
>     ss << " \x01\x0B\x07 " << config.misc.banText << " \x01 ";
>     if (shouldSet && interfaces.engine - > isInGame() && changeName(false, ss.str().c_str(), 5.0 f))
>         shouldSet = false;
> }

It looks like a change to the Fake Ban, Please make a Pull Request with Specific details on what you changed. Thank you,

What does it fix?

@danielkrupinski The color of the fake ban is displayed correctly

If that's the case, I believe it's fine the way it is. No errors have occurred when I tried it. And the color displays correctly.

If that's the case, I believe it's fine the way it is. No errors have occurred when I tried it. And the color displays correctly.


SSO Event Protection (Old 19)

In gitlab by @A-Lawrence on Aug 31, 2015, 01:10
When member's login from an IP that's been used by someone else (recently) they should have to re-enter their Network password or staff password, whichever is necessary.

In gitlab by @A-Lawrence on Aug 31, 2015, 01:18
Resolved issue #488658 (18) issue #19 issue #488657 (20) issue #21 issue #488656 (22) issue #23
ÔåÆ <<cset 9e27bee878b9>>
ALawrence66 - 2013-07-27T17:32:10.838007+00:00


Markdown Compatibility Request

Any chance of this happening?
I've gone through so many vanilla javascript wysiwygs and yours is my favorite implementation by far, just a shame it doesn't support Markdown.

I am also interested in this feature although some fetaures of @wysiwygjs would ethier not work for example background color or the need to expand markdown to enable it

Sorry, this is only a "What You See Is What You Get" editor.
There is no support for Markdown/BBCode/...


Update web documentatioin to explain gotcha

Update the web documentation to explain a gotcha when loading components that are within the router folder. Also update the example so it is using a location that hints towards a different folder.
I encountered this problem myself and initially raised an issue for it: #2484

thanks a lot :)


Re-implement sky fog from vanilla

Hiya, this mod appears to overwrite the vanilla behavior for applying fog to the sky, so I re-added it.
Vanilla applies a fog layer for both the sky and terrain.  Custom Fog currently does not render the former at all, so the horizon appears as a distinct band, much more noticeably with very far fog starts (or disabled fog).  Here's an image album with comparisons: https://imgur.com/a/wnRik9G
Thanks for considering!

very nice! I'd like to check the code myself (tomorrow, unfortunately - very tired tonight) to see if there's a better way to handle it than setting the fog distance uniformly like this for the sky; I'm mostly just curious if there's a way to remove the banding effect without hardcoding the sky fog.

very nice! I'd like to check the code myself (tomorrow, unfortunately - very tired tonight) to see if there's a better way to handle it than setting the fog distance uniformly like this for the sky; I'm mostly just curious if there's a way to remove the banding effect without hardcoding the sky fog.

well regardless of if there's some Magic Better Way™, this is definitely an improvement over the way it works now; my only complaint is that your implementation currently sets the fogStart, fogEnd, and fogMode to the vanilla sky settings, which is what they're already set to just before the mixin is invoked. In fact, we could return early all the way back during the first line in the setFogFalloff() method, which would both make it behave itself more if some other mod also mixes into BackgroundRenderer#applyFog and changes the skybox fog, and be just a bit faster (since it can avoid getting the config when rendering a skybox).
TLDR: I think it would be worthwhile to move the if (fogType == SKY) check to the first line of setFogFalloff.

well regardless of if there's some Magic Better Way™, this is definitely an improvement over the way it works now; my only complaint is that your implementation currently sets the fogStart, fogEnd, and fogMode to the vanilla sky settings, which is what they're already set to just before the mixin is invoked. In fact, we could return early all the way back during the first line in the setFogFalloff() method, which would both make it behave itself more if some other mod also mixes into BackgroundRenderer#applyFog and changes the skybox fog, and be just a bit faster (since it can avoid getting the config when rendering a skybox).
TLDR: I think it would be worthwhile to move the if (fogType == SKY) check to the first line of setFogFalloff.

Thanks for the feedback, done.  I had half a thought with the fogType check in changeFalloff, was thinking one might be able to allow users to also set the fog mode for the sky fog; but it would probably be a fair amount of trouble for a relatively small visual effect that would probably be obscured by the terrain fog on any non-zero fog start or density.

Thanks for the feedback, done.  I had half a thought with the fogType check in changeFalloff, was thinking one might be able to allow users to also set the fog mode for the sky fog; but it would probably be a fair amount of trouble for a relatively small visual effect that would probably be obscured by the terrain fog on any non-zero fog start or density.

looks good! I'm gonna merge it today, and I'll make a new release within the next couple days - there was some other change I wanted to make first (that I've now forgotten :/ )

looks good! I'm gonna merge it today, and I'll make a new release within the next couple days - there was some other change I wanted to make first (that I've now forgotten :/ )

Cool, thank you!  Appreciate the work you've done with this mod! :D

Cool, thank you!  Appreciate the work you've done with this mod! :D


Update requirements.txt

Update to redvid 2.0.1 to avoid .vtt files with new Reddit API changes

Awesome, thank you for this and redvid!


z-index request

Hi your plugin is great but I think a data-z-index would make it better again.
What do you think ?

+1

This seems like a great suggestion! No dev time from us at the moment but go ahead and make a PR and I'm happy to merge.

+1
I'm using this with 'on hover' event and wish there was an easy way to bring an element to the top.

Should this issue be closed now that PR #77 is merged?


Increment version to 2.0.1

Signed-off-by: Zelin Hao<EMAIL_ADDRESS>Is your feature request related to a problem? Please provide an existing Issue # , or describe.
Increment version to 2.0.1
Describe the solution you are proposing
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@zelinh Thanks for the PR. There are additional files that needs version change,
https://github.com/opensearch-project/performance-analyzer-rca/blob/main/docker/Dockerfile#L32
https://github.com/opensearch-project/performance-analyzer-rca/blob/main/INSTALL.md
https://github.com/opensearch-project/performance-analyzer-rca/blob/main/src/main/resources/plugin-descriptor.properties#L45

Codecov Report

Merging #190 (c0828d4) into 2.0 (04b640b) will decrease coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Current head c0828d4 differs from pull request most recent head 2ba3daa. Consider uploading reports for the commit 2ba3daa to get more accurate results

@@             Coverage Diff              @@
##                2.0     #190      +/-   ##
============================================
- Coverage     71.44%   71.43%   -0.01%
+ Complexity     2940     2938       -2
============================================
  Files           376      376
  Lines         18769    18769
  Branches       1445     1445
============================================
- Hits          13409    13408       -1
  Misses         4770     4770
- Partials        590      591       +1

Impacted Files
Coverage Δ

.../org/opensearch/performanceanalyzer/core/Util.java
62.50% <0.00%> (-8.34%)
:arrow_down:

...nalyzer/rca/net/handler/PublishRequestHandler.java
75.51% <0.00%> (-8.17%)
:arrow_down:

...performanceanalyzer/collectors/StatsCollector.java
92.59% <0.00%> (-0.75%)
:arrow_down:

...nsearch/performanceanalyzer/rca/RcaController.java
82.81% <0.00%> (ø)

...erformanceanalyzer/rca/framework/core/RcaConf.java
57.34% <0.00%> (+1.39%)
:arrow_up:

...nceanalyzer/rca/samplers/MetricsDBFileSampler.java
84.09% <0.00%> (+9.09%)
:arrow_up:

Continue to review full report at Codecov.

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


Readme examples compile now

Added couple missing semicolons and added all variants to the match statements. I also updated the dependencies to use crates.io instead of github.

Thanks!


Other backbones

Thanks for your work.
Do you have the weight files of other backbone networks that you have trained? Such as WideResNet28 and ResNet10.

Hello,
Unfortunately, we only train for ResNet12 in the paper. However, the code is ready for WideResNet28 and you can use it to train a WRN-28 by setting  --model 'wideresnet' in the training command.
Hope this helps,
Best,

Ok, I know this command, but it takes too much time to train a pretrained model.
Thanks for your reply.

hello, i have a question.
for the wideresnet28 and fc100, the following command can be ok?
python main.py  --dataset-path /home/dataset  --dataset FC100  --model  wideresnet   --milestones 100   --epochs 0   --manifold-mixup 600   --cosine   --gamma  0.9   --rotation   --batch-size 64   --device cuda: 0   --preprocessing  ME   --skip-epochs 550 --save-model /home/1.pt1 --n-shots 5
what's the setting of --epochs, manifold-mixup and  --skip-epochs ,the values are  right?


figure out a process to autobuild releases

...because it's really annoying to do this manually.

You could create a separate tag or a branch for releases and maybe use this https://docs.travis-ci.com/user/deployment/releases ?

Yes, very nice, it seems to be working with Conditional Releases.


Add Python 3 support

ctypes.CDLL(ctypes.util.find_library('c')).if_nametoindex always returns 0 on Python 3.7 for me (which results in a "No such device" error when trying to open the socket), but it looks like this method now exists in the socket module:
https://docs.python.org/3/library/socket.html#socket.if_nametoindex
Using it instead (if it exists) makes the code work on both Python 2 and 3. The only other change needed was xrange() -> range().
(eap_proxy) $ python --version
Python 3.7.3
(eap_proxy) $ pylint eap_proxy.py
************* Module eap_proxy
eap_proxy.py:375:0: R0205: Class 'EdgeOS' inherits from object, can be safely removed from bases in python3 (useless-object-inheritance)
eap_proxy.py:533:0: R0205: Class 'EAPProxy' inherits from object, can be safely removed from bases in python3 (useless-object-inheritance)

@tobiasmcnulty please verify that the proxy now works correctly for you with Python 3. Thanks.

@jaysoffian Sorry for the delayed response; I was away on vacation.
I finally had a chance to test this and it looks like it's mostly working. I missed one thing, which is that ord() causes a logging failure on Python 3 with this error: https://stackoverflow.com/questions/30076240/ord-expected-string-of-length-1-but-int-found?rq=1
Unfortunately removing it as suggested seems to break Python 2. If I have a chance I'll look around for another solution, but let me know if you find a fix first.

Please try again, I just pushed a fix for the ord issue.

@jaysoffian That works - many thanks for the quick fix!


Add docstring and update tests

I think you can also just push directly to my branch, since a maintainer can add commits to the PR.


libsamplerate, libdvdcss: fix darwin build

Things done:

[ ] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[ ] NixOS
[x] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

More
I started with intent to get Handbrake building on darwin, but that turned our more difficult than anticipated. It seems to pretty heavily depend on Xcode.
I did manage to fix these two in the process, though. They build for me locally just fine. The nox-review fails for me while building doxygen, which seems pretty unrelated.

Anything keeping this from being merged? Any other info I can provide?

@ryanartecona considering there weren't any more replies I don't think there is anything that should keep it from merging. Could you rebase and cc me?

Thanks, @FRidh!
It looks like libsamplerate has been fixed on darwin separately already in e2fdd74a41fb8859f72e4f26636df79b046caee5. I removed the commit which did basically that same thing in this branch.
I rebased the libdvdcss commit onto current master. A local darwin build after the rebase seems to still work.

@ryanartecona its just a minor issue, but could you also undo the change that @joachifm pointed at.

@FRidh Sure thing. Done.


Escaping non-unicode section names

I found a few samples like this one which are causing this error in debloat
>>> import debloat.processor
>>> import pefile
>>> import os
>>> file_path = "1b7babe5fde91a44f8488aef2873078cc9f4ac5810625bcd6c271cf13e8d6145"
>>> binary = pefile.PE(file_path, fast_load=True)
>>> file_size = os.path.getsize(file_path)
>>> debloat.processor.process_pe(binary, out_path="out", last_ditch_processing=False, cert_preservation=True, log_message=print, beginning_file_size=file_size)
Section: .text   Compression Ratio: 250.98%     Size of section: 1024 bytes.
Section: .rdata  Compression Ratio: 204.8%      Size of section: 512 bytes.
Section: .data   Compression Ratio: 116.04%     Size of section: 38.5 MB.
Section: .rsrc   Compression Ratio: 261.76%     Size of section: 266.0 KB.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File ".../debloat/processor.py", line 578, in process_pe
    result, result_code = check_section_compression(pe, data_to_delete, log_message=log_message)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../debloat/processor.py", line 358, in check_section_compression
    section_name = section.Name.decode()
                   ^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9b in position 0: invalid start byte

After this small fix, they will show the following:
>>> file_path = "1b7babe5fde91a44f8488aef2873078cc9f4ac5810625bcd6c271cf13e8d6145"
>>> file_size = os.path.getsize(file_path)
>>> binary = pefile.PE(file_path, fast_load=True)
>>> debloat.processor.process_pe(binary, out_path="out", last_ditch_processing=False, cert_preservation=True, log_message=print, beginning_file_size=file_size)
Section: .text   Compression Ratio: 250.98%     Size of section: 1024 bytes.
Section: .rdata  Compression Ratio: 204.8%      Size of section: 512 bytes.
Section: .data   Compression Ratio: 116.04%     Size of section: 38.5 MB.
Section: .rsrc   Compression Ratio: 261.76%     Size of section: 266.0 KB.
Section: \x9b\xa3\xff\xa3u       Compression Ratio: 128.63%     Size of section: 16.5 KB.

No automated method for reducing the size worked. Please consider sharing the
sample for additional analysis.
Email<EMAIL_ADDRESS>Twitter: @SquiblydooBlog.

0

I can change it to not specify the encoding if preferred, and/or a different error handling.
Thank you!

I am merging another branch today with other improvements. This change will be documented in the change-log and the version number will be incremented.
The next release will include changes from both branches.


Error when using AutoEnvs in Julia

Hi I tried the installation and encountered this issue. Could you please help me with this? Thanks. I was running on Ubuntu18.04 with Julia 1.1.0
julia> using AutoEnvs
[ERROR: LoadError: LoadError: UndefVarError: EntityQueueRecord not defined
Stacktrace:
 [1] top-level scope at none:0
 [2] include at ./boot.jl:326 [inlined]
 [3] include_relative(::Module, ::String) at ./loading.jl:1038
 [4] include at ./sysimg.jl:29 [inlined]
 [5] include(::String) at /home/meng/.julia/packages/AutoRisk/g60Ag/src/AutoRisk.jl:2
 [6] top-level scope at none:0
 [7] include at ./boot.jl:326 [inlined]
 [8] include_relative(::Module, ::String) at ./loading.jl:1038
 [9] include(::Module, ::String) at ./sysimg.jl:29
 [10] top-level scope at none:2
 [11] eval at ./boot.jl:328 [inlined]
 [12] eval(::Expr) at ./client.jl:404
 [13] top-level scope at ./none:3
in expression starting at /home/meng/.julia/packages/AutoRisk/g60Ag/src/evaluation/simulation.jl:29
in expression starting at /home/meng/.julia/packages/AutoRisk/g60Ag/src/AutoRisk.jl:30
ERROR: LoadError: Failed to precompile AutoRisk [c91b7102-3640-11e9-1a5c-f77073b5ac95] to /home/meng/.julia/compiled/v1.1/AutoRisk/XxXFG.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1197
 [3] _require(::Base.PkgId) at ./loading.jl:960
 [4] require(::Base.PkgId) at ./loading.jl:858
 [5] require(::Module, ::Symbol) at ./loading.jl:853
 [6] include at ./boot.jl:326 [inlined]
 [7] include_relative(::Module, ::String) at ./loading.jl:1038
 [8] include(::Module, ::String) at ./sysimg.jl:29
 [9] top-level scope at none:2
 [10] eval at ./boot.jl:328 [inlined]
 [11] eval(::Expr) at ./client.jl:404
 [12] top-level scope at ./none:3
in expression starting at /home/meng/ngsim_env/julia/src/AutoEnvs.jl:3
ERROR: Failed to precompile AutoEnvs [b0c92c82-45e2-5f35-82fd-3b99a2ee9dd8] to /home/meng/.julia/compiled/v1.1/AutoEnvs/gVIxo.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1197
 [3] _require(::Base.PkgId) at ./loading.jl:960
 [4] require(::Base.PkgId) at ./loading.jl:858
 [5] require(::Module, ::Symbol) at ./loading.jl:853

There are some warnings which I guess might cause the issue (because I cannot find those attributes in AutomotiveDrivingModels repo: https://github.com/sisl/AutomotiveDrivingModels.jl):
[ Info: Precompiling AutoEnvs [b0c92c82-45e2-5f35-82fd-3b99a2ee9dd8]
WARNING: could not import AutomotiveDrivingModels.update! into AutoRisk
WARNING: could not import AutomotiveDrivingModels.pull_features! into AutoRisk
WARNING: could not import AutomotiveDrivingModels.get_name into AutoRisk

@raunakbh92 @djp42

I also meet the same issue


Remove need for host and project_id in .gitreview

The Gitlab project_id is not really needed to access the Gitlab API for the project.  The url-quoted project path can be used too, and the project path is available from the url of the remote.  The Gitlab host URL can be gleaned from the remote's url as well.
Removing the need for these two settings makes the .gitreview file more portable, and potentially completely optional (although the code has not been updated to handle a missing .gitreview file or one that doesn't have a section for the remote in question).
Other changes:

Renamed global_vars.host to global_vars.host_url to better reflect what it contains (a url, not a hostname).

global_vars.branch_url is defined, for use in a future commit.

I could use assistance settling on what should be in README.md now.


update conan install instructions

v0.1.0 is not yet available in conan-center-index but I am working on it. This PR updates the documentation according to the new configuration options that will be added in the new version.

Thanks for the cmake simplification!
Interesting, the Ubuntu build is missing the djinni_main.cpp implementation (what I can see via mobile)

This is expected to fail for JNI. It requires changes in the djinni-generator to work.


Add pycln to pre-commit for plugins

Based on @goanpeca requests https://github.com/napari/napari/pull/5359#issuecomment-1326783124 adds pycln pre-commit hook to cookiecutter template.

The ruff F401 Rule covers it. Maybe I should close this PR and remove pycln from the main repository?

Sure, that sounds alright :)


basic code area and basic code entry examples broken on artix linux 6.12.1

basic code area and basic code entry examples will not launch from meta_example.rb
Both fail with similar errors:
Basic Code Area
** (ruby:23218): CRITICAL **: 23:18:04.740: [libui] ../common/control.c:88:uiControlVerifySetParent() You have a bug: You cannot give a uiControl a parent while it already has one. (control: 0x5d53f7bed4d0; current parent: 0x5d53f880b470; new parent: 0x5d53f79d88a0)
Basic Code Entry
** (ruby:25525): CRITICAL **: 23:25:45.878: [libui] ../common/control.c:88:uiControlVerifySetParent() You have a bug: You cannot give a uiControl a parent while it already has one. (control: 0x5a92088709d0; current parent: 0x5a92087cd080; new parent: 0x5a920867cd00)

Hello, we tried to solve the issue.
This is what we did:
Modify the meta_example.rb file to correctly handle the creation and display of basic code area and basic code entry examples without causing parent-related errors.
You can review changes in this commit: https://github.com/mnmnk43434/AndyObtiva-glimmer-dsl-libui-70/commit/20abda1743c85d6f7756f23e8e02e328a282c4ce.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


bug:[CORE-1844] admin policy filter changes

Description
HOLDING THE PR SINCE WE MAY HAVE A GENERIC SOLUTION FOR THESE ISSUES.
In admin policy, when we fetch the policy column values, we get list of names and id of policy which in case of same name is an ongoing issue in ui. To handle it here, we are going with the approach that backend will return only display name of policy and will take display name in request payload.

Issue :

Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Chore (no code changes)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also
list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] My commit message/PR follows the contribution guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Other information:
List any documentation updates that are needed for the Wiki

Not needed.


ocamlPackages.csexp: 1.3.1 -> 1.3.2

Motivation for this change
Bump version. This version lowers the requirement of dune to 1.11:
https://github.com/ocaml-dune/csexp/blob/master/CHANGES.md#132
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions: Ubuntu

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build dune-release jackline liquidsoap


Handle triple clicks.

When we use contenteditable=false islands, tripple clicking on a paragraph only selects to the bounds of that island, which is not desired. Instead we should implement our own behavior when a triple click happens. See Visual Editor.
Additionally we want to avoid that triple clicking leads to a container annotation. So if we had this handler we can also do that here.

Will try to land this one in Beta3....

See first attempt: #349 works quite well as long as you don't click between the lines, where no mousedown event is triggered. Why is that? :/

Thx. Doing this on Surface works perfectly.


onInput callback for Form.TagPicker or Form.Dropdown

Describe the feature and the current behavior/state.
It'd be nice that Form.TagPicker or Form.Dropdown includes an onInput callback so that we can execute an action each time the user enters text in these fields. The main use case would be for searching in a list that might return a lot of options.
For example, in the Linear extension, the API returns the 50 first results by default for the queries. This causes a problem for Linear workspaces with more than 50 labels since all labels wouldn't be shown. While it's possible to increase this number, this wouldn't solve the issue since it's not possible to know in advance what's a reasonable number of labels. Instead, it's better to allow users to search for labels directly in the picker or dropdown. That way, they can search for the label they want. (cf Slack thread)
Will this change the current API? How?
This would be purely additive to the API. No breaking changes to expect.
Who will benefit from this feature?
Any users who want to execute some kind of action when the users enters text in Form.TagPicker or Form.Dropdown

In the next release, we are going to add onSearchTextChange to Form.Dropdown. Going to think about the TagPicker

As Mathieu said, onSearchTextChange is now available in Form.Dropdown https://developers.raycast.com/api-reference/user-interface/form#props-6
This isn't the case for Form.TagPicker though. @mathieudutour Is this under consideration?

I'd love to see that for Form.TagPicker as well.
Consider this use case: You want to present the user a list of tags to choose from but want to allow them to also add tags that aren't part of the list yet. In oder to react to that, you would either listen for onSearchTextChangeEvent and add the tag when the tab key is triggered or when a coma character has been inserted.
If there is already a way to do that, please let me know. Cheers!
Here's how Notion does it:

@thomaslombart @peduarte @mathieudutour
Any update on adding onSearchTextChange and throttle to TagPicker?

This component is tricky, making it more difficult to add these props to it. We're thinking of alternative ways to solve the underlying use cases 🙂


Remove reliance on polymer-cli

PWA starter kit example with WebPack: https://github.com/Polymer/pwa-starter-kit/tree/webpack
LitElement https://lit.dev/docs/v1/tools/build/#build-requirements
Blocks #528.

[ ] Remove all mentions of polymer in gulpfile.js variables and messages

Being developed in branch rollup-build

Verified service-worker from old to new works in a production deploy.


Unified memory in nvcomp question

Hi nvcomp team,
Does nvcomp uses cuda unified memory or any other mechanism to deal with files larger than GPU memory ?
Thanks,

Hi @benjha,
nvCOMP does not allocate GPU memory itself, and instead relies on the calling code to allocate GPU memory. There are several requirements that different memory passed into the API is accessible either from the CPU or GPU. You can pass in unified memory to these APIs and they will work fine. You may see decreased performance if page migration needs to take place (as is generally the case for unified memory).
Does this answer your question?

Yes, thanks!


Invisible main menu, black text and background

Issue Type: Bug
When VSCode has the focus the main menu is not visible, but it is accessible if you click on its location.
If another window is selected the menu appears. Ubuntu 18.10.
VSCode on focus:

VSCode blured:

VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:07:43.495Z)
OS version: Linux x64 4.18.0-11-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 x 2838)

GPU Status
2d_canvas: unavailable_softwarechecker_imaging: disabled_offflash_3d: unavailable_softwareflash_stage3d: unavailable_softwareflash_stage3d_baseline: unavailable_softwaregpu_compositing: unavailable_softwaremultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarewebgl: enabled_readbackwebgl2: unavailable_off

Load (avg)
0, 2, 2

Memory (System)
15.55GB (10.15GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

xml
Dot
2.3.2

json-pretty-printer
eus
1.0.1

php-debug
fel
1.12.6

vscode-language-pack-es
MS-
1.29.2

vetur
oct
0.13.0

vscode-workspace-switcher
sad
1.9.0

I have some problem on Ubuntu 18.10. How to fix?

Another solution is to change the type of tittle bar to custom. By the way I noticed that this problem only on Yaru. On Yaru-dark all well.

Changing bar style works for me, thanks for the tip.

I have some problem on Ubuntu 18.10. How to fix?

My temporary solution is to change the Ubuntu theme, instead of Yaru use Adawaita. Adawaita shows the top of the window (title and menú bar) with light background instead of dark.

This worked for me but it's worth noting that, unless I'm missing something, it requires installing GNOME Tweaks (at least on Ubuntu 8.10).

Duplicate of #62593


How can I make a shorcut to an .exe open in cmd in WT

I use command line tools but I have shortcut to them but they open in the cmd not WT(Windows Terminal)
Can I make a shortcut that opens the .exe in WT?

Currently no, unfortunately. This is a feature that's being tracked by #492
/dupe #492


'return' keyword should have different color

Function 'return' keyword should have different color.
See attachment for reference.

what was the file-type or language in which this issue was found? Also what version?

I am using PHP language and file type was .php

I think this should be resolved in 1.0. Feel free to re-open if you still see a problem.


The final HTML DOM should not have any props from JSX Wrapper except with using attrs

Version
2.1.0

Reproduction

https://www.webpackbin.com/bins/-KtVOP6OYjAfjyqgdtrs

Steps to reproduce
See my screenshot and https://www.webpackbin.com/bins/-KtVOP6OYjAfjyqgdtrs
Expected Behavior
<section data-react-root class="sc-bwzfXH gzMTbA">
Actual Behavior
<section data-reactroot height="300" width="300" dir="rtl" class="sc-bwzfXH gzMTbA">

This is expected behaviour, we maintain a whitelist of valid DOM attributes and pass them through.

@geelen this would be an interesting solution to the whitelist problem? Did you consider removing the whitelist and only passing through props from .attrs?

Based on the question you ask @geelen, I want to know if you think it is nice to have this behavior. If so, I am going to fix that. My point is I think height="300" width="300" dir="rtl" should come from the attrs only. And I am concerned about the priority of attrs and the props from the Wrapper

The idea behind the whitelist is that's it's a much nicer DX, see #731 and all the linked discussion for the context around the question.


SidePanels, at both left and right, leads to accessibility issue The  element has the id "c4p--side-panel-outer" that is already in use

What package(s) are you using?

[x] Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)
[ ] Legacy/CDAI
[ ] Legacy/Security

What did you want to know?
I am using SidePanels, at both left and right,
anyone familiar with the accessibility issue The <div> element has the id "c4p--side-panel-outer" that is already in use
Providing unique id to different SidePanels does not help, c4p--side-panel-outer is some inside class of SidePanel
Relevant information
###Screenshorts

@lee-chase can you help investigate this? Surprised to see c4p--side-panel-outer as an ID instead of a class? 👀

Seems like we just need to add a uuid/useId here.

Can i work on this?

@RafflesiaKhan a fix has been pushed to address this and should be in the next release


complete README example usage

As mentioned in #552

Coverage remained the same at 97.727% when pulling a44bad41cbdbd71bf5e50f680ff5909b4b9ad3c7 on Omega-Ariston:addDocExample into 8fc5b926846cd4ef9a2dbccd411705e0c110a708 on Leonidas-from-XIV:master.

Coverage remained the same at 97.727% when pulling a44bad41cbdbd71bf5e50f680ff5909b4b9ad3c7 on Omega-Ariston:addDocExample into 8fc5b926846cd4ef9a2dbccd411705e0c110a708 on Leonidas-from-XIV:master.


RestApi won't update properly when using openapi

What happened?
When updating resources using openapi spec on the RestApi resource, the config gets reverted back to the original-deployed config but the state still makes it look like the config was updated.
When digging into the terraform provider it looks like they have logic to try and ensure your RestApi config from resource inputs will overwrite the config from openapi, but I'm wondering if that logic is unintentionally rolling back the openapi config when it changes.
I am unable to figure out if this is a pulumi or terraform provider problem as I have only tried this out with pulumi so far.
Steps to reproduce
Use openapi to create a Rest API with a policy via pulumi.
Update the IP address in the policy of the openapi config and run another pulumi up.
See the policy has not changed.
Here is a sample pulumi code for a RestApi with openapi
const apigatewayBody = pulumi.output({
  openapi: '3.0.3',
  info: {
    title: 'test-api',
    version: '0.1.0',
  },
  paths: {
    '/test': {
      post: {
        responses: {
          200: {
            description: '200 response',
            content: {
              'application/json': {
                schema: {
                  $ref: '#/components/schemas/SuccesfulReturn',
                },
              },
            },
          },
          500: {
            description: 'Internal Server Error',
            content: {
              'application/json': {
                schema: {
                  $ref: '#/components/schemas/ErrorModel',
                },
              },
            },
          },

        },
        'x-amazon-apigateway-integration': {
          httpMethod: 'POST',
          uri: '{MY LAMBDA ARN}',
          responses: {
            default: {
              statusCode: '200',
            },
          },
          passthroughBehavior: 'when_no_match',
          contentHandling: 'CONVERT_TO_TEXT',
          type: 'aws_proxy',
        },
      },
    },
  },
  components: {
    schemas: {
      SuccesfulReturn: {
        type: 'object',
        required: [
          'message',
          'body',
          'statusCode',
        ],
        properties: {
          message: {
            type: 'string',
          },
          body: {
            type: 'string',
          },
          statusCode: {
            type: 'integer',
            minimum: 200,
            maximum: 300,
            default: 200,
          },
        },
      },
      ErrorModel: {
        type: 'object',
        required: [
          'message',
          'statusCode',
        ],
        properties: {
          message: {
            type: 'string',
          },
          statusCode: {
            type: 'integer',
            minimum: 100,
            maximum: 600,
            default: 500,
          },
        },
      },
    },
  },
  'x-amazon-apigateway-policy': pulumi.jsonParse(aws.iam.getPolicyDocumentOutput({
    statements: [
      {
        effect: 'Deny',
        principals: [{
          identifiers: ['*'],
          type: 'AWS',
        }],
        actions: ['execute-api:Invoke'],
        resources: ['execute-api:/*/POST/*'],
        conditions: [
          {
            // TODO: Protect against what VPCs can hit this as well
            test: 'NotIpAddress',
            variable: 'aws:SourceIp',
            values: [
              '<IP_ADDRESS>', // test
            ],
          },
        ],
      },
      {
        effect: 'Allow',
        principals: [{
          identifiers: ['*'],
          type: 'AWS',
        }],
        actions: ['execute-api:Invoke'],
        resources: ['execute-api:/*/POST/*'],
      },
    ],
  }).json),
})

new aws.apigateway.RestApi('test-api', {
  body: pulumi.jsonStringify(apigatewayBody),
  endpointConfiguration: {
    types: 'EDGE',
  },
  name: apigatewayBody.info.title,
})

Expected Behavior
I expect the openapi config to change parts of the RestApi that are not configured at the resource level.
Actual Behavior
The RestApi config is not updated in AWS.
Output of pulumi about
CLI
Version      3.50.0
Go Version   go1.19.4
Go Compiler  gc
Plugins
NAME            VERSION
aws             5.26.0
aws-apigateway  1.0.1
nodejs          unknown
Host
OS       darwin
Version  12.6.1
Arch     arm64
This project is written in nodejs: executable='/Users/me/.asdf/shims/node' version='v16.19.0'
Dependencies:
NAME                    VERSION
@pulumi/aws             5.26.0
@pulumi/aws-apigateway  1.0.1
@pulumi/pulumi          3.51.0
@types/jest             29.2.5
@types/node             14.18.36
eslint                  8.31.0
jest                    29.3.1
ts-jest                 28.0.8
typescript              4.9.4
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

The same behavior holds upstream: https://github.com/hashicorp/terraform-provider-aws/issues/38515

It is possible to apply the workaround of replaceOnChanges: ["body"] resource option to the RestAPI. This will cause a complete replacement of the resource. Let us know if this unblocks your scenario.


Upgrade Github CodeQL to V2

Upgrade Github CodeQL to V2 since V1 will be deprecated in December 2022 and receive no updates
Fix the the pipeline failing for cpp files not found.

Codecov Report

Merging #65 (8c1635b) into main (1e1ffc5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #65   +/-   ##
=======================================
  Coverage   86.31%   86.31%
=======================================
  Files          10       10
  Lines        1900     1900
=======================================
  Hits         1640     1640
  Misses        260      260

Impacted Files
Coverage Δ

src/picologging/handlers.py
93.82% <0.00%> (ø)

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

thanks!


openstack: add get_user method

openstack: add get_user method
Description
libcloud's OpenStack compute nodes have a userId value in node.extra.
Add a new get_user() method to the OpenStackIdentityConnection v3 class to look up this user by the user ID value.
This allows callers to discover more information about the user that created a node (for example).
Status
done, ready for review
Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[x] Documentation
[x] Tests
[x] ICLA (required for bigger changes)

Thanks! Merged in trunk. ✨


Fix background not flashing when using easter egg functions

This is a CSS related issue but I believe it can be bypassed using the javascript. when I was making changes to the new page design i used #mainpage and #wrap in CSS instead of using .body (because using .body didnt work for some reason, even when using !important).
@airforce270 ASSISTANCE PLS <333

now if .body is fixed (somehow) i dont need to rely #mainpage and #wrap for colors, this also fixes another bug involving the easter egg and party button

Fixed by commit in #42


Lazy loading localeMessages fetches several times when the page changes

Environment

Operating System: Windows_NT
Node Version:     v18.12.0
Nuxt Version:     3.9.1
CLI Version:      3.10.1
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      ssr, css, app, modules, i18n, sitemap, image, device, site, nitro, build, security, devServerHandlers, runtimeConfig, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
This is the code that I wrote
Link to StackBlitz
Describe the bug
When the app mounts, the localeMessages with the default locale fetches normally. However, when I navigate to certain pages, such as localhost:3000/u/some-user-name or /some-company-name (I have dynamic routes in the pages folder), it fetches again. Sometimes, lazy loading fetches an entirely different locale.
Additional context
No response
Logs
No response

I had a component that I intended to use across multiple sites. Consequently, I created a page and utilized it as a widget component in my current project with iframe. However, the locale messages were fetched twice when the app was mounted within an iframe and I entered pages that used this widget.
Problem solved)

Problem solved)

Seems like this issue has been resolved? I'll close this issue, let me know if you're still experiencing this issue and I'll reopen!


Export data from GA to add to hub

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/126
Originally created by @tayloramurphy on 2021-10-01 21:37:32

We should be able to pretty quickly generate a yaml file from the data in https://analytics.google.com/analytics/web/?authuser=1#/report/content-event-events/a132758957w192718180p188392047/_u.date00=20210701&_u.date01=20210901&_r.drilldown=analytics.eventCategory:meltano elt&explorer-table.plotKeys='Reference to deleted milestone 5'B%5D&explorer-table.rowCount=1000/
to showcase number of times a connector was called over the past 6 months. I'm keen to do at least a 3 month window as that would give us time to iterate on the real data pipeline, but I think doing a one-off to add it to the hub prior to taptoberfest would be good.

View 19 previous comments from the original issue on GitLab


Masterkeys Pro L ENTER Key not Lighting Up

What are you experiencing an issue with?

[ ] Aurora
[ ] Aurora supported game, (Fill in the game)
[ ] Aurora Wrapper
[ ] Aurora Profile
[x ] Aurora supported device, (CoolerMaster MasterKeys Pro L)
[ ] Aurora Scripts
[ ] Aurora Updater
[x ] Aurora Lighting issue
[ ] Other, (Fill in another issue here)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[ ] Visual bug
[ ] Localization issue
[ ] Enhancement suggestion
[x ] Device issue
[ ] Other, (Fill in another type of issue here)

Expected behavior:
I expect the ENTER key to light up
Actual behavior:
The ENTER key does not light up
How often does this problem occur?

This problem occurs... (Every time)
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:

Plug in the device
Try to light up key
key will not light up

What is the version of Aurora you are experiencing this issue with?

My version is... (v0.6.1-dev4)

Damn it, after last patch fixed the numpad, I hadn't noticed Enter not being lit.
Same here.

Same exact problem on Masterkeys Pro M. After some digging, I confirmed that build 0.6.1-dev4-286 does not have this issue. Some later build broke the Enter key on CM keyboards. I recommend reverting back to the older build until this issue is re-addressed.

Thanks for the confirmation im gonna revert back to the old build.

Just a heads up, if I recall 6 on number pad didn't light up, hence the need for the beta build.
I believe any changes you make for num6 apply to num5, any to num5 apply to num4.
Or it was 4 didn't light up and it went the other way but you'll see.

@ryanmeblin thanks for the confirmation, I just reverted back to this build and it worked.

Could someone with this issue test on the latest build? It's got changes for the MK750, not sure if it will work for the others. I don't know why builds after 286 would specifically break the enter key, if it was going to break anything I would have thought it'd be a lot more significant, as I haven't changed the code related to the enter key.

@simon-wh That 308 build seems to have fixed it. Enter is good, as is 4,5,6 and on numpad.
I'm not seeing any blank keys.

@Thelgow Is this build in the latest release?  The builds mentioned are all after dev4.

@simon-wh Didn't fix it unfortunately

@husseinfahmy Could you try the latest build? There have been some more changes to CM stuff.

@simon-wh The new build didn't automatically fix it, but I realized that if I change my layout from automatic to US, it fixes it.

Aaaand now my right arrow key is dim...


Local engine run on android_debug_unopt_x64 doesn't find POM

flutter run --local-engine android_debug_unopt_x64 gives
The file /Users/.../engine/src/out/android_debug_unopt_x64/x86_debug.pom wasn't found in the local engine out directory.
But there's a x86_64_debug.pom file in android_debug_unopt_x64. Probably a tooling issue.
cc @blasten

are you attached to an x64 device? If the device supports multiple ABIs, it looks like the tool is picking up x86.

It's an emulator. Is there a way to force x64? Can't build android_debug_unopt_x86 these days on newer versions of macOS I think.


Introduction of Competitive Programming

Description
Introduction of Competitive Programming
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


Password-less SSL certificates

We need to accept password-less SSL certificates. Right now the password is required.

Closing this as the work done by DeadZen is now in Cowboy.


Updated UniPlaneMeshGenerator.Editor.asmdef to include only Editor platform

Otherwise, the build process always fails if this package is added to the project due to no access to the UnityEditor namespace

Thank you for nice PR!