[AEMaaCS] Cannot access selector in ACS COMMONS 404 error page

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: aem-sdk 2023.1.10912.20230130T173736Z-220900
[ ] ACS AEM Commons Version: 5.7.0
[ ] Reproducible on Latest? yes

Steps to Reproduce
Please describe briefly the expected behavior, i.e. when I do X, Y should happen.
Configure ACS COMMONS Error handler feature
Create a simple component that display the sling request selectors
 <div>${request.requestPathInfo.selectors}</div>
Create a 404 HTML page that embed the "selectors" component
Access a non existing page
Expected Behavior
The selectors are displayed in the 404 error page thanks to the custom component
Actual Behavior
The selectors are not displayed in the 404 error page.

@fbonheurCap IIRC since youre in the context of a missing resource, this data isnt assumed (since it doesnt know what the resource actually is intended to be since there isnt a resource to resolve to). I believe you'd have to parse that data out of the request URI yourself (you could make a PathInfo object from it, and get the selectors off that).

Hello, just a note for anyone else who has the problem. We discovered that it was not that the selectors where getting removed that caused the problem but the additon of the .html (configured via the error-page.extension osgi property) that causes internal include to remove the selectors.
Configuring this to a blank string allowed the selectors to be passed through but created a problem for the error page cache (which is based upon the path).
In the end we overrode the 404.jsp and added the selectors from the current slingRequest into the path - so the cache key contained the selectors as well


Only commit using GPG (i.e. via signed commits)

i.e. @devseccon you need to configure your git client to use GPG , note the lack of 'Verified' on your commit. How do I know that that commit was made by you :)

See http://www.slideshare.net/DinisCruz/gpg-signing-git-commits for more details and for instructions on how to set it up

done, closing issue


Getting an error in the HAPIH.h

I am coding a cheat for a game and i keep on getting this error: 'static_cast': cannot convert from 'PointerIH' to 'size_t'
Someone please help me with this cause it's pissing me off

you're probably doing something wrong? We can't you without the code, anyway


convert-txt2al does not renumber the table to 50010 range

I run the convert-txt2al, but it does not renumber to 50100 range

@andrecavalcanti Hi, many thanks for your feedback but I would like to ask you to classify better the issues.
I think that this question fits better into Microsoft/navcontainerhelper or even into Microsoft/al.
My opinion is that it has nothing to do with NAV on Docker... If I am wrong then sorry!!!

@Koubek I have opened an issue on Microsoft/al
Thanks


Add checks for users, isolated logic -- refactored

This PR is intended as a replacement for the feature request of:   https://github.com/erikr/django-restricted-sessions/pull/2
It rebases off the trunk and adds the feature in more minimally now that the refactor is less relevant.

Coverage remained the same at 100.0% when pulling ea55d5571289b45bf5f09b12bc82ef7d41a0dbc5 on CashStar:master into 4d540d282db396b83328ba29d2179663e10320b4 on erikr:master.

@erikr This is my attempt at rebasing #2 ... hope this works for everyone but let me know.

Thanks, merged. I'll try to roll a release soon!


Revisit logging in Commands Converter

I am analysing the logs of VS Code + Extensions with trace level enabled and see if there are any logs which are taking lot of space and can be reduced. Long term goal is to capture all levels logging and have UI filters.
In the extension host log, following log statements are taking ~90% of the size. Please validate the necessity of these and see if it can be minimized.
2024-01-28 21:04:25.285 [trace] CommandsConverter#DISPOSE _typescript.applyCompletionCommand /134567
2024-01-28 21:04:25.622 [trace] CommandsConverter#CREATE _typescript.didApplyRefactoring _typescript.didApplyRefactoring /136376

https://github.com/microsoft/vscode/blob/c00f9942f5e537c2e6e3d5e85c6306eb793deef6/src/vs/workbench/api/common/extHostCommands.ts#L395
https://github.com/microsoft/vscode/blob/c00f9942f5e537c2e6e3d5e85c6306eb793deef6/src/vs/workbench/api/common/extHostCommands.ts#L402

Sorry, no plans because this helps us trace too early releasing of command data that is held in the EH. This is a reoccurring issue and the only way to drill into these issues.
I understand the pain tho, but I don't believe not logging or less logging is the answer but a proper log filter view. Whenever possible I try to show logging output in dev tools because the console allows for that


VercelPostgresError: VercelPostgresError - 'missing_connection_string'

Running into this issue after drawing something and after pressing the "make real" button.
⨯<EMAIL_ADDRESS>(158:10) @ createPool
⨯ VercelPostgresError: VercelPostgresError - 'missing_connection_string': You did not supply a 'connectionString' and no 'POSTGRES_URL' env var was found.
at uploadLink (./app/lib/uploadLink.tsx:22:60)

I was able to fix this by creating a project and database on vercel. Follow the instructions here and run the command to get the database working on your local instance.

I did this and it started to work:
docker pull postgres
docker run --name postgres-db -e POSTGRES_PASSWORD=make-real -p 5432:5432 -d postgres
export POSTGRES_URL=postgresql://postgres:makereal@localhost:5432/postgres
npm i
npm run dev

It worked, and then when I stopped the container and tried again it failed with a differently worded error. But after starting postgres again it works again.


External Traffic Policy:  Cluster and Local is not working

I have calico policy installed on kubernetes cluster.
created nginx deployment in default namespace
created service my-dep in same namespace exposed as node port
however it is using External Traffic Policy: Cluster which I changed to Local
But I could not access it using nodeip:nodeport outside of the cluster
Service: Nodeport.
Name:                     my-dep
Namespace:                default
Labels:                   app=my-dep
Annotations:              <none>
Selector:                 app=my-dep
Type:                     NodePort
IP:                       <IP_ADDRESS>
Port:                     <unset>  80/TCP
TargetPort:               80/TCP
NodePort:                 <unset>  32620/TCP
Endpoints:                <IP_ADDRESS>:80
Session Affinity:         None
External Traffic Policy:  Local
Events:                   <none>

created one more pod to check the connectivity using busybox.
created networkpolicy with below yaml file however I still could not connect it.
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  name: access-nginx
  namespace: default
spec:
  podSelector:
    matchLabels:
      app: my-dep
  ingress:
    - from:
      - podSelector:
          matchLabels:
            run: access

It may be basic question but kindly help me here.

@eselvam Calico itself doens't program the external traffic policy field for nodeports - that's done by kube-proxy, so if there is an issue it's likely not related to Calico.
That said, once you set externalTrafficPolicy: Local, you need to make sure that you're only accessing the the nodeport on nodes that are actually hosting a pod in that service. I'd double check that the node you were using actually had a pod in the service running on that node.

Thanks.  It is a issue with my setup.  Thanks for the clarification.

Thanks. It is a issue with my setup. Thanks for the clarification.
Can you tell me what the setting problem is? I also encountered this problem


Add CQs management methods to the client

This PR adds to the client new methods which allow create, show and drop continuous queries in InfluxDB more easily.

@aviau seems like docs test is really broken.

seems like docs test is really broken.

Yeah. Somebody needs to fix it.

Can you rebase this on master? The tests should now pass.

Yay, it is passing now.

@smolse the logic here is completely fine, but can you please add comments to the test functions (something basic)? We've introduced PEP257 compliance over the past few weeks, and that's the only failing test at the moment.
Once you've added, we can merge this.

@smolse - do you intend to work on this anytime soon?
AFAIU the thing to be done (apart from rebasing on master again) is to add docstrings to test cases - is that right, @sebito91 ?


Make it easier to find user and organisation when setting roles in Django Admin

When creating a UserOrganisationRole in Django admin you need to select the user and organisation from a dropdown, that only supports quick selection by a username__startswith search by starting to type in the standard Django <select> field. With the growing number of users and organisations this is becoming an increasingly difficult task.
What would help:

Being able to search for the foreign key relation (like in a raw_id_field, but without loosing the quick option; is this an option?)
By default filter out inactive users

@lexvand commented on Thu Mar 24 2022
@byrman What do you think about this issue?

@byrman commented on Thu Mar 24 2022

@byrman What do you think about this issue?

Yes, that Admin page has much to be desired. But is it still used? The same can be achieved by sending an invitation?
We can improve on the Admin page, but perhaps we should get rid of lizard-auth-client and move the concept of organisations and roles to Lizard? Most of the lizard-auth-client library is now obsolete?

still an issue. @byrman the problem is that you have to be a manager to use the management page for invites. so each time you want to make yourself or another person a manager, you have this issue.


CI for testing imports in pnpm environment

Hi!
Thanks for making this package! It's fantastic :)
I'm using pnpm as my package manager and I have been getting errors after building Sanity studio. To reproduce:
pnpm create sanity@latest

# project: test
# dataset: test
# output: test
# template: no schemas
# typescript: yes

cd test
pnpm install @sanity-typed/types

// sanity.config.ts
import {defineConfig} from '@sanity-typed/types' // <-- change this line to import from sanity-typed
// ...

pnpm run build
pnpm run start

The error I'm getting:
Uncaught error: Pe.default.div is not a function
http://localhost:3333/static/sanity-9dde895e.js:4670:40453
TypeError: Pe.default.div is not a function
    at http://localhost:3333/static/sanity-9dde895e.js:4670:40453
    at http://localhost:3333/static/sanity-9dde895e.js:7423:54634

This error resolves when I change this line back:
// sanity.config.ts
import {defineConfig} from 'sanity' // <-- change this line to import from sanity
// ...

I wasn't able to create a StackBlitz or something similar doing these steps, so I'm not sure how this reproduces on other machines. I'm using a Macbook Pro with Ventura 13.4

So I've never used pnpm and I wasn't really planning on supporting it, although it's nice to identify this issue twice as a pnpm specific issue. I have no idea what's happening. My immediate guess is that the default.div error has something to do with styled-components, which I think that sanity uses and, since sanity is a peer dependency, the issue has something to do with how pnpm handles or doesn't handle peer dependencies. Maybe you can help solve this.
Even if I were to support this, I'm not sure how to maintain it. It seems difficult to get CI to setup a repo with each package as a dependency, attempt npm/yarn/pnpm install, build, and determine that running also works (because in this case, it's actually running the studio that identifies the issue). Without this full pipeline, the chances that I re-break pnpm without knowing it are extremely high.

Got snagged by this as well 😢. It'd be nice to add a warning to the readme page saying it'll break if you use pnpm. Sanity offers pnpm as a supported option when you spin up a new project so it's likely that more people are going to stumble here. It's also tricky to figure out what's going on since it works in dev mode but breaks in prod mode. 🤦

Yeah its a tricky issue. I did not have the time to dig into it yet, but my suspicion is that it has something to do with the portabletext editor dependency, since that is the only one in this package that depends on styled components. I hope to be able to look into this later, but if you find out something I'm curious to hear your findings.

Also stumbled on it. 😕 Will also try to dig into it soon.
Good to know that the portabletext editor could be the issue. I will report here if I find something.

Anyone have any ideas of how to test this in CI, before we tackle solving it? I took a first swing at it, but ended up with a solution on how to build this whole repo using pnpm, which is not what I want. I want to figure out if, when another repo uses @sanity-typed/types (as an example, we can run tests for each package) and pnpm, that we don't get build errors. I'm also concerned that, even with the reported errors, it's not building the sanity studio that's failing but running it, which seems even worse to test. I'm convinced this isn't just difficult to test, but flaky to maintain.
Basically, how do other libraries that don't use pnpm internally validate when an application using the library does use pnpm?

I don't think you're disagreeing, but this library will build using npm. So I'd need to test that the completely npm build library works in a pnpm environment, which isn't as simple as switching everything over to pnpm and seeing if things work. For me, that's most of the complexity. ie, supporting pnpm is very different than having this library just use npm. Likely, similar issues might occur with yarn. Reproducing the environment required for this issue is non-trivial locally or in CI. And, if it isn't reproduced in CI, I can't claim support for it.
I'd like to isolate this specific issue about portable text so I can test for it. However, it only surfaces when someone is using pnpm, so I can't reproduce the issue without completing point number 1 anyways (it very well might be a pnpm exclusive problem, which it seems to be). And to include tests that recreate the issue will be difficult because the issue doesn't occur currently, only when in a pnpm environment which requires point number 1.
In terms of documenting this, I'm also not documenting whether or not it works in yarn for all the same reasons all packages aren't listing if they work in npm, yarn, pnpm, mynextnpmimplementation, etc. They are supposed to support all npmjs.org packages out of the box, as-is. Even if we can repro this properly, it feels like the maintenance burden is on the wrong side of the fence here.

Maybe this will help? I couldn't really sort it out but it might be helpful.

@waspeer, can you push a minimal repro of the sanity project with issues (step 3) and link it here? I'd like to see what is actually happening for myself.

https://github.com/waspeer/sanity-typed-issue
This repo includes step 1-4 in my comment. Let me know if this works for you.

This repro is doing too much to actually decipher what is happening.
Trying to rebuild a local version of @sanity-typed/types is creating it's own issues, for example. Uncaught error: The requested module '/@fs/Users/wannes/Projecten/Web/waspeer/sanity-typed-issue/sanity-typed/types/dist/index.js?t=1701806909825' does not provide an export named 'defineArrayMember' is a whole different error because you're attempting to rebuild it on your own. And then linking @sanity-typed/types to your local folder is bound to have (p)npm install do different things. Both are pretty different issues than the original one of Uncaught error: Pe.default.div is not a function.
Can you really slim this down to the error that created this issue, while using @sanity-typed/types how a normal end user would use it?:

I think we might be talking past each other here. In my last comments I was just sharing my process debugging the issue. I shared my process because this a hard issue to debug and I was hoping we might help each other navigate this that way. The step you wanted me to replicate in the repo was just an intermediate step in this process and not an attempt to replicate the exact original error.
Just to be completely clear, I'm aware there are a few imperfections in my approach, specifically that the local building and linking of the package is not representative of the actual usage of this package. I think the main point is that I got Styled Components related issues that I was able to pinpoint to the importing of the sanity package. The errors were not identical to the one in my first comment, but I do think they're related. I included the CJS/ESM stuff because I thought it was interesting that all the issues disappeared when I build the package to ESM.

I think a lot of issues (and solutions) are getting introduced all together under "pnpm issues" and I really can't approach it all as one chunk. But yes, I did miss the point of what you were doing. It also just dawned on me that you didn't have everything in one branch, but in multiple different commits for the different stages.  🤣
This is the order I'd love to accomplish things:

A minimal repro repo of an issue that only applies with pnpm.
Involving that in the testing so that CI breaks, specifically because of that issue.
Getting a fix in.

Jumping to fix 3 is going to be a ticking time bomb for a regression, so I'm trying to defer the rest until we have 1 & 2. I will end up breaking pnpm users without it in CI, so fixing it now without CI testing for it isn't something I think we should do.

I was about to try a solution involving npm pack and checking out a separate repo to test importing this, but I'm realizing I can't really even test the specific error that's occuring:

pnpm run build
pnpm run start

The error I'm getting:
Uncaught error: Pe.default.div is not a function
http://localhost:3333/static/sanity-9dde895e.js:4670:40453
TypeError: Pe.default.div is not a function
    at http://localhost:3333/static/sanity-9dde895e.js:4670:40453
    at http://localhost:3333/static/sanity-9dde895e.js:7423:54634

I have no idea how I'd even run start in CI, detect the error, and close the whole thing down with massive flakiness. puppeteer? npm pack, creating a separate repo to import it, installing with pnpm (and I'd probably do yarn too, at that point), building and starting, detecting runtime errors... I think there's a lot of room for flakiness.
I'm just going to run your steps and see if there's an easy fix for this current issue at hand and, if so, release that. But I don't really feel comfortable claiming pnpm support going forward without being able to validate it automatically.

OK, I have a super small repro:
https://gist.github.com/saiichihashimoto/1349697a7dbc64096a89ffc7c6cee771
It only fails on pnpm run start, not pnpm run dev, which is interesting.

@waspeer @shixish @mrr11k I know it's been almost a year (and I've broken some ribs in that time, FUN) but I'm starting to re-address some of these bigger issues. I'm sure you've found other solutions, but could you see if the most up-to-date versions of @sanity-typed/* don't break your pnpm environments? I'm imagining the current repros are too out of date to be relevant anymore.


How to set a favicon?

There is no documented way to set a favicon, other than to just have a favicon.ico file in the public folder, and trust the browser to read /favicon.ico.

Maybe moisout want use a URL (like for og:image).

You can use setup this in nuxt.config.ts.


Fix scriptUrl for production build

Summary
For production build regexp not matched anything and scriptURL.match(/(^.+)\/index/)[1] throws error because match was null, so i added statement for checking match and return null if not matched.

Don't forget to add yourself to contribution list!


Update artifacts with mediaType as per v1.0.0-draft.1.1

Signed-off-by: Sajay Antony<EMAIL_ADDRESS>

Good that the reference manifest schema used by ratify already has MediaType https://github.com/deislabs/ratify/blob/165ccb9784a694077fcb79fa5160d361acc8068c/pkg/ocispecs/descriptor.go#L34


null in spanner Array

spanner Array like [<null>, 1, 2] results in:
strconv.ParseInt: parsing "": invalid syntax

Since spanner allows null elements in Array, null in array should be supported.

Driver has moved to another repository, so it closes.
The continuation is here


Custom Component is not working (includes github repo)

Describe the bug
I have tried to create a Custom Dashboard as per Documentation on
https://docs.adminjs.co/tutorial-writing-react-components.html
But I am getting an error Message
Javascript Error
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports. Check the render method of `Dashboard`.
See development console for more details...

Repo is here
https://github.com/dmastag/adminjs-bug-custom-component
Installed libraries and their versions

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

clone Repo
run npx nodemon .
open http://localhost:8080/admin in a Browser

Expected behavior
Dashboard gets replaced
Screenshots

AdminJSOptions with schema
const adminJs = new AdminJS({
  databases: [],
  rootPath: '/admin',
  dashboard: {
    component: AdminJS.bundle('./my-dashboard-component')
  },
})

Desktop (please complete the following information if relevant):

OS: Windows 10 and MaxOS 12
Browser Chrome

The documentation (docs.adminjs.co) tutorials are outdated. I'm currently rewriting the documentation to be more tutorial-based but as of now there's only installation section.
Your problem can be solved by importing Box from @adminjs/design-system instead of adminjs.

Thanks
That make it work


[FEATURE]Add a note to the documentation to update doc page when creating or renaming a plugin

We are listing all available OpenSearch and Dashboards plugins on the following documentation pages:
https://opensearch.org/docs/latest/opensearch/install/plugins/#available-plugins
and
https://opensearch.org/docs/latest/dashboards/install/plugins/#available-plugins
Could we add a note to one of the Contributing or Conventions file to either update those pages or create an issue in the doc repo whenever someone creates a new plugin or updates a plugin name?

Definitely add to https://github.com/opensearch-project/opensearch-plugins/blob/main/BUILDING.md#building-plugins-with-opensearch


[Github actions] Deprecate GCB build run

Towards #2670

Updates badge in README
Disables the GCB trigger
Removes related yaml and docker configs

@gino-m  PTAL?

Amazing work, @shobhitagarwal1612 , and in record time!

@gino-m Gentle ping!


[Security]: Export security key

Codecov Report

Merging #302 (dba3712) into master (09b8c8d) will decrease coverage by 2.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #302      +/-   ##
==========================================
- Coverage   43.53%   41.42%   -2.12%
==========================================
  Files         120      120
  Lines        6103     6103
==========================================
- Hits         2657     2528     -129
- Misses       3246     3392     +146
+ Partials      200      183      -17

Flag
Coverage Δ

integration
?

unittests
41.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/messagebroker/factory.go
33.33% <0.00%> (-33.34%)
:arrow_down:

pkg/messagebroker/kafka.go
10.48% <0.00%> (-30.00%)
:arrow_down:

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 09b8c8d...dba3712. Read the comment docs.


In price filter, allow comma(,) for price in filter as in french locale float values used to be separated by , in stead of .

Bug report
Title
In price filter, allow comma(,) for price in filter as in french locale float values used to be separated by , in stead of .
Preconditions
1. framework Version. Master

Expected result:
comma should be allowed
Actual result
https://prnt.sc/tl8pup
as of customer can't use , in value while using price filter

Fixed in master


Fix #150: dateRangeChange incorrectly called

Overview
Fixes https://github.com/awslabs/synchro-charts/issues/150.
When in live mode, the viewportHandler tick cycle was passing the updated viewport back to the rendered chart. The logic was set to emit the dateRangeChange event any time the viewport changed. When in live mode this isn't the desired behavior so a flag was added to be able to check for that and block the event from being emitted.
Tests
[Include a link to the passing GitHub action running the test suite here.]
Legal
This project is available under the Apache 2.0 License.

Don't forget to squash all the commits into 1! :D


Refactoring: extract exposures.

This one reaches many goals at once:

Fixes #56: now exposures is not a hash table but an array.
Due to previous point, tree structure nested_exposures based on
flat hash table with keys like root_node__node__node is removed
because now double exposures don't rewrite previously defined
so such tree structure is simply incorrect.
NestingExposure with an array of children is introduced instead.
For ones who want previous rewriting behavior a rewrite option
for exposure is introduced.
Fixes #149: runtime options are now wrapped in an Options object.
Fixes #150: see new spec/grape_entity/exposure_spec.rb
All exposure configuration and exposing strategies are extracted to
the separate classes.
key_for, name_for internal methods are removed.
Much of the overhead is gone so performance is increased by 20-30%.

At first glance this change may seem too big. But every move here is reasonable.
For instance It's impossible to solve #56 without removing nested_exposures. Removing nested_exposures requires different way to represent nesting trees so I cannot find something better than extract exposure logic from Entity at all.

But some problem is introduced with changing exposures from hash table to an array so grape-swagger will not work with this patch. And it's even unclear how to generate documentation. Imagine this case:
expose :x, using: E1, if: :condition1
expose :x, using: E2, if: :condition2

Which one should the swagger pick: E1 or E2 ?
I can help with implementing a workaround for swagger but for now I don't know exactly how  to fix it.
Maybe bring back construction of exposures as a hash table and deprecate it?

I'd like to merge this, it needs a detailed CHANGELOG entry and we have to discuss what to do about swagger. The conflicting cases should just have some predictable behavior.

I just read through swagger specification and didn't find anything that might help gracefully solve this issue.
But:

It tries to analyze only those exposures that has a :documentation option.
It fetches exposure_options by name (which now is not unique) to get its :using option only if there is no :type field in :documentation of exposure.
Grape::Entity.documentation (which is used by grape-swagger) still has an old rewriting nature. But I think that in this case it's good. Ones who use conditional exposures with different using values are forced to specify one :type for exposures with the same key (:as value or attribute name). This :type value could be simply 'object' or some 'AbstractEntity'.
According to previous point for any keygrape-swagger should pick :type from documentation or :using (if there's no :type) from the last exposure with this key and it's already implemented in documentation.
Grape::Entity.documentation still has an issue described in #112. I propose to solve it traversing only root_exposures, not exposures.
Remove flat array of exposures. There's no need in this now.

I'd like to propose a workaround to grape-swagger based on a fact that new entities do not respond to exposures method. It would also require adding different versions of grape-entity to grape-swagger's travis matrix.
Any complains?

No complaints. Grape-swagger needs a lot of work too and as long as we offer people a path forward I'm cool with it. Please at the very least open issues with grape-swagger for anything introduced here.

@marshall-lee Lets get this merged? Amend CHANGELOG? We also probably need an UPGRADING document.

@dblock I'm working on CHANGELOG right now.
I'd like to write UPGRADING.md too. To what version we're upgrading? 0.5.0? Maybe change lib/grape_entity/version.rb in this patch too?
And what format should I use in UPGRADING?

0.5.0 makes sense

Oops, JRuby build failed. https://travis-ci.org/intridea/grape-entity/builds/72464413
Latest changes revealed some misbehavior in JRuby, I reported it here: https://github.com/jruby/jruby/issues/3178

LOL, Now Rubocop suggests me in https://travis-ci.org/intridea/grape-entity/jobs/72467983:
Pass &:nesting? as an argument to take_while instead of a block.

But take_while with &:method is buggy in JRuby as I mentioned above.

But it's okay on jruby-head, lol.

@dblock I'm almost ready. Maybe you release 0.4.6 without these changes? Or just put all pending changes to 0.5.0?

@marshall-lee You've done some great work here. I emailed you about becoming a maintainer on grape-entity. Your first order of duty could be to release 0.4.6?

:+1:

great stuff, to bad it breaks https://github.com/Gild/ruby-swagger too. How does the UPGRADE look like? next time pls deprecate the method first..

I think the line @calfzhou is referring to is: https://github.com/ruby-grape/grape-swagger/blob/03ee40d41d71063236c4b0b1d468f69978ab308e/lib/grape-swagger/doc_methods.rb#L261

ok this did the trick for me, super hacky, dirty and for sure not complete...
class BaseDecorator < Grape::Entity
    def self.exposures
      extract_exposures(root_exposures, {})
    end

    private

    def self.extract_exposures(root, hash, prefix = nil)
      root.each do |entity|
        key = "#{prefix}#{entity.attribute}"
        nested = prefix.nil? ? {} : { nested: true }
        if entity.is_a?(Grape::Entity::Exposure::NestingExposure)
          hash[key.to_sym] = {}
          extract_exposures(entity.nested_exposures, hash, key + '__')
        else
          hash[key.to_sym] = entity.send(:options).merge(nested)
        end
      end
      hash
    end
  end

@rngtng Want to give fixing https://github.com/ruby-grape/grape-swagger/issues/314 a try?

@dblock I'd love to, if I find the time...let me see..


Multiple Sound Effects Issue

Good afternoon -
I am having a issue with preloading sound effects.. I am trying to preload all of the sound effects because it seems that the initial playerhitmonster sound effect makes the game lag. So is there any way to load them when the app starts?
Thanks,
Hayden

Hi Hayden, I don't if there is one, but I don't think that the game lag is due to the audio, once SKActions run on the background...
Luiz.


Speech-to-text evaluation

Hi,
I successfully run the experiments and I am trying to evaluate the CAAT system with various values of latency. I started your agent for SimulEval but it is taking more than 2 days for the result, is it normal?
Thank you again

Hi, I am testing on MuST-C tst-COMMON and it is taking a long time compared to you. I do not know why. I am using only one GPU K80 for inference, how many GPUs have you used for testing?
I also added the tag --gpu to the SimulEval inference script to ensure the use of the GPU.
It is strange because the standard Fairseq SimulST model takes less than 1 hour in the same setting.

I use one V100 GPU for inference, but there shouldn't be too much difference in speed. the tag "--gpu" is not defined in my code and I will ignore it. I used "--cpu" to indicate model runs on CPU, or it will runs on GPU by nn.Module.cuda().
Infering speed of my CAAT should be comparable to wait-k or MMA, I don't know the detail of your standard fairseq simulST. Maybe you need to debug a little bit more, log out the cost of some special function, to find the bug reason


index: storage: don't try to version_path for non-version_aware fs

Codecov Report
Base: 57.76% // Head: 57.76% // No change to project coverage :thumbsup:

Coverage data is based on head (c50e839) compared to base (d5d8f36).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #316   +/-   ##
=======================================
  Coverage   57.76%   57.76%
=======================================
  Files          51       51
  Lines        3336     3336
  Branches      585      585
=======================================
  Hits         1927     1927
  Misses       1319     1319
  Partials       90       90

Impacted Files
Coverage Δ

src/dvc_data/index/index.py
64.05% <0.00%> (ø)

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

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


Slash commands options auto completion

This PR contains implementation of necessary interaction types and payloads for newly introduced option auto completion for slash commands.
WIP docs and showcase if anyone is interested

@CarsonHoffman fixed everything, can I get a re-review?


[torch.compile] fix cpu broken code

broken by https://github.com/vllm-project/vllm/pull/9896

error found in https://buildkite.com/vllm/ci-aws/builds/10628#0192eb5f-0793-43e6-bf18-9dd9b3ede594


Use typescript in tailwind-config package and restruct

It would be nice using typescript in tailwind-config package either.
Plus, renaming tailwind.config.js to kind of base.ts
achieving more structural consistency with others like tsconfig package.

@Jonghakseo Are you tried it before?
Cause i was saw in some place .ts or .mts don't work properly 😸

I'm not sure how necessary the above behavior is since type inference using jsdoc is supported, so it's not a high priority at this time. :eyes:


Subdomain not allowed in custom dns search list

In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}

[X] I have read and understood the contributors guide.
[X] The issue I am reporting can be replicated.
[X] The issue I am reporting can be is directly related to the pivpn installer script.
[X] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Entering a custom domain refuses subdomains. In my case i have an officially registered domain example.com and i have a local samba based AD (samba.example.com). I Provided the samba dns servers and want to provide a custom dns search domain (samba.example.com) but i can only enter example.com - after install i can change to samba.example.com manually...
setup itself runs perfectly, vpn works fine
Have you searched for similar issues and solutions?
yes
Console output of      curl -L install.pivpn.io | bash
root@vpn01:~# curl -L https://install.pivpn.io | bash
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0     93      0  0:00:01  0:00:01 --:--:--    93
100 58458  100 58458    0     0  20569      0  0:00:02  0:00:02 --:--:--  151k
:::
::: You are root.
::: Verifying free disk space...
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with PiVPN installation...
update-alternatives: using /usr/sbin/iptables-legacy to provide /usr/sbin/iptables (iptables) in manual mode
update-alternatives: using /usr/sbin/ip6tables-legacy to provide /usr/sbin/ip6tables (ip6tables) in manual mode
::: Using User: adminl
:::
::: Checking for existing base files...
:::    Checking /etc/.pivpn is a repo...:::    Cloning https://github.com/pivpn/pivpn.git into /etc/.pivpn... done!
:::
::: Stopping OpenVPN service... done.
:::
::: Installing scripts to /opt/pivpn... done.
::: Using protocol: tcp
set_var EASYRSA_ALGO       ec
set_var EASYRSA_CURVE      prime256v1
::: Building CA...
read EC key
writing EC key
Can't load /etc/openvpn/easy-rsa/pki/.rnd into RNG
140420250645632:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:98:Filename=/etc/openvpn/easy-rsa/pki/.rnd
::: CA Complete.
Note: using Easy-RSA configuration from: ./vars
Using SSL: openssl OpenSSL 1.1.1c  28 May 2019
Generating an EC private key
writing new private key to '/etc/openvpn/easy-rsa/pki/private/vpn01_82373007-bcff-4869-8c2c-8e5af1149f8d.key.AQVjXHhbVp'
Using configuration from /etc/openvpn/easy-rsa/pki/safessl-easyrsa.cnf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
commonName            :ASN.1 12:'vpn01_82373007-bcff-4869-8c2c-8e5af1149f8d'
Certificate is to be certified until Sep  2 20:35:58 2029 GMT (3650 days)
Write out database with 1 new entries
Data Base Updated
Note: using Easy-RSA configuration from: ./vars
Using SSL: openssl OpenSSL 1.1.1c  28 May 2019
Using configuration from /etc/openvpn/easy-rsa/pki/safessl-easyrsa.cnf
An updated CRL has been created.
CRL file: /etc/openvpn/easy-rsa/pki/crl.pem
net.ipv4.ip_forward = 1
net.ipv6.conf.all.disable_ipv6 = 1
cp: cannot stat '/tmp/OLD_UFW': No such file or directory
::: Install Complete...
::: Restarting services...
::: Flushing writes to disk...
::: done.
:::
::: Installation Complete!
::: Now run 'pivpn add' to create an ovpn profile for each of your devices.
::: Run 'pivpn help' to see what else you can do!
::: It is strongly recommended you reboot after installation.
:::

Console output of      pivpn add or pivpn add nopass
root@vpn01:~# pivpn add
Enter a Name for the Client:  vpnclient01
How many days should the certificate last?  1080
Enter the password for the client:
Enter the password again to verify:
spawn ./easyrsa build-client-full vpnclient01
Note: using Easy-RSA configuration from: ./vars
Using SSL: openssl OpenSSL 1.1.1c  28 May 2019
Generating an EC private key
writing new private key to '/etc/openvpn/easy-rsa/pki/private/vpnclient01.key.uST97UiKhU'
Enter PEM pass phrase:$1pisaX%
Verifying - Enter PEM pass phrase:
Using configuration from /etc/openvpn/easy-rsa/pki/safessl-easyrsa.cnf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
commonName            :ASN.1 12:'vpnclient01'
Certificate is to be certified until Aug 20 21:02:59 2022 GMT (1080 days)
Write out database with 1 new entries
Data Base Updated
Client's cert found: vpnclient01.crt
Client's Private Key found: vpnclient01.key
CA public Key found: ca.crt
tls Private Key found: ta.key
========================================================
Done! vpnclient01.ovpn successfully created!
vpnclient01.ovpn was copied to:
/home/adminl/ovpns
for easy transfer. Please use this profile only on one
device and create additional profiles for other devices.

Console output of      pivpn debug
root@vpn01:~# pivpn debug
::: Generating Debug Output
::::            PiVPN debug              ::::
::::            Latest commit            ::::
commit d0c10db6ec391961b7201fb564055c1176ca73e3
Author: 4s3ti<EMAIL_ADDRESS>Date:   Tue Sep 3 10:09:48 2019 +0200
install.sh: apt-get with , uninstall.sh: added var PKG_MANAGER and replaced apt-get with

=============================================
::::        Installation settings        ::::
/etc/pivpn/DET_PLATFORM -> Debian
/etc/pivpn/FORWARD_CHAIN_EDITED -> 0
/etc/pivpn/HELP_SHOWN ->
/etc/pivpn/INPUT_CHAIN_EDITED -> 0
/etc/pivpn/INSTALL_PORT -> 443
/etc/pivpn/INSTALL_PROTO -> tcp
/etc/pivpn/INSTALL_USER -> adminl
/etc/pivpn/NO_UFW -> 1
/etc/pivpn/TWO_POINT_FOUR ->
/etc/pivpn/pivpnINTERFACE -> ens3
::::    setupVars file shown below       ::::
INSTALL_USER=adminl
UNATTUPG=
pivpnInterface=ens3
IPv4dns=
IPv4addr=<IP_ADDRESS>
IPv4gw=<IP_ADDRESS>
pivpnProto=tcp
PORT=443
ENCRYPT=256
APPLY_TWO_POINT_FOUR=true
DOWNLOAD_DH_PARAM=false
PUBLICDNS=REMOTE
OVPNDNS1=<IP_ADDRESS>
OVPNDNS2=<IP_ADDRESS>
::::  Server configuration shown below   ::::
dev tun
proto tcp
port 443
ca /etc/openvpn/easy-rsa/pki/ca.crt
cert /etc/openvpn/easy-rsa/pki/issued/vpn01_82373007-bcff-4869-8c2c-8e5af1149f8d.crt
key /etc/openvpn/easy-rsa/pki/private/vpn01_82373007-bcff-4869-8c2c-8e5af1149f8d.key
dh none
topology subnet
server <IP_ADDRESS> <IP_ADDRESS>
Set your primary domain name server address for clients
push "dhcp-option DOMAIN laurenz.ws"
push "dhcp-option DNS <IP_ADDRESS>"
push "dhcp-option DNS <IP_ADDRESS>"
Prevent DNS leaks on Windows
push "block-outside-dns"
Override the Client default gateway by using <IP_ADDRESS>/1 and
<IP_ADDRESS>/1 rather than <IP_ADDRESS>/0. This has the benefit of
overriding but not wiping out the original default gateway.
push "redirect-gateway def1"
client-to-client
keepalive 1800 3600
remote-cert-tls client
tls-version-min 1.2
tls-crypt /etc/openvpn/easy-rsa/pki/ta.key
cipher AES-256-CBC
auth SHA256
user nobody
group nogroup
persist-key
persist-tun
crl-verify /etc/openvpn/crl.pem
status /var/log/openvpn-status.log 20
status-version 3
syslog
verb 3
#DuplicateCNs allow access control on a less-granular, per user basis.
#Remove # if you will manage access by user instead of device.
#duplicate-cn
Generated for use by PiVPN.io
=============================================
::::  Client template file shown below   ::::
client
dev tun
proto tcp
remote REMOTE 443
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
tls-version-min 1.2
verify-x509-name vpn01_82373007-bcff-4869-8c2c-8e5af1149f8d name
cipher AES-256-CBC
auth SHA256
auth-nocache
verb 3
::::    Recursive list of files in       ::::
::: /etc/openvpn/easy-rsa/pki shows below :::
/etc/openvpn/easy-rsa/pki/:
Default.txt
ca.crt
crl.pem
ecparams
extensions.temp
index.txt
index.txt.attr
index.txt.attr.old
index.txt.old
issued
openssl-easyrsa.cnf
private
renewed
revoked
safessl-easyrsa.cnf
serial
serial.old
ta.key
vpnclient01.ovpn
/etc/openvpn/easy-rsa/pki/ecparams:
prime256v1.pem
/etc/openvpn/easy-rsa/pki/issued:
vpn01_82373007-bcff-4869-8c2c-8e5af1149f8d.crt
vpnclient01.crt
/etc/openvpn/easy-rsa/pki/private:
ca.key
vpn01_82373007-bcff-4869-8c2c-8e5af1149f8d.key
vpnclient01.key
/etc/openvpn/easy-rsa/pki/renewed:
private_by_serial
reqs_by_serial
/etc/openvpn/easy-rsa/pki/renewed/private_by_serial:
/etc/openvpn/easy-rsa/pki/renewed/reqs_by_serial:
/etc/openvpn/easy-rsa/pki/revoked:
private_by_serial
reqs_by_serial
/etc/openvpn/easy-rsa/pki/revoked/private_by_serial:
/etc/openvpn/easy-rsa/pki/revoked/reqs_by_serial:
::::            Self check               ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] OpenVPN is running
:: [OK] OpenVPN is enabled (it will automatically start on reboot)
:: [OK] OpenVPN is listening on port 443/tcp
::::      Snippet of the server log      ::::
Sep  5 23:05:09 vpn01 ovpn-server[450]: library versions: OpenSSL 1.1.1c  28 May 2019, LZO 2.10
Sep  5 23:07:11 vpn01 ovpn-server[450]: Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Sep  5 23:07:11 vpn01 ovpn-server[450]: Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Sep  5 23:07:11 vpn01 ovpn-server[450]: Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Sep  5 23:07:11 vpn01 ovpn-server[450]: Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Sep  5 23:07:11 vpn01 ovpn-server[450]: TUN/TAP device tun0 opened
Sep  5 23:07:11 vpn01 ovpn-server[450]: TUN/TAP TX queue length set to 100
Sep  5 23:07:11 vpn01 ovpn-server[450]: /sbin/ip link set dev tun0 up mtu 1500
Sep  5 23:07:11 vpn01 ovpn-server[450]: /sbin/ip addr add dev tun0 <IP_ADDRESS>/24 broadcast <IP_ADDRESS>
Sep  5 23:07:11 vpn01 ovpn-server[450]: Could not determine IPv4/IPv6 protocol. Using AF_INET
Sep  5 23:07:11 vpn01 ovpn-server[450]: Socket Buffers: R=[87380->87380] S=[16384->16384]
Sep  5 23:07:11 vpn01 ovpn-server[450]: Listening for incoming TCP connection on [AF_INET][undef]:443
Sep  5 23:07:11 vpn01 ovpn-server[450]: TCPv4_SERVER link local (bound): [AF_INET][undef]:443
Sep  5 23:07:11 vpn01 ovpn-server[450]: TCPv4_SERVER link remote: [AF_UNSPEC]
Sep  5 23:07:11 vpn01 ovpn-server[450]: GID set to nogroup
Sep  5 23:07:11 vpn01 ovpn-server[450]: UID set to nobody
Sep  5 23:07:11 vpn01 ovpn-server[450]: MULTI: multi_init called, r=256 v=256
Sep  5 23:07:11 vpn01 ovpn-server[450]: IFCONFIG POOL: base=<IP_ADDRESS> size=252, ipv6=0
Sep  5 23:07:11 vpn01 ovpn-server[450]: MULTI: TCP INIT maxclients=1024 maxevents=1028
Sep  5 23:07:11 vpn01 ovpn-server[450]: Initialization Sequence Completed
::::            Debug complete           ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.txt
:::
Have you taken any steps towards solving your issue?
changing manually dns suffix in /etc/openvpn/server.conf
[...]
push "dhcp-option DOMAIN samba.example.com"
[...]

This issue also happens for .co.uk domains. Looking at the regex used in the installation script:
^[a-zA-Z0-9][a-zA-Z0-9-]{1,61}\.[a-zA-Z]{2,}$

If you paste that into https://regexr.com youll see that it does not match subdomains or any other domain that doesnt end in com i.e. .co.uk (issue im experiencing myself)
can somebody have a look at improving the regex?
Heres what i found online:
[-a-zA-Z0-9@:%._\+~#=]{1,256}\.[a-zA-Z0-9()]{1,6}\b([-a-zA-Z0-9()@:%_\+.~#?&//=]*)

Source: Stack Overflow

i am working in some stuff ill try to fix and add this on test branch this week

ok .. bene playing with this .. @zkhan96MSM the regexp you posted is far too permissive for a domain, however it helped to make an adaptation from that one and this is what i have  came up with:
[-a-zA-Z0-9.\+]{1,256}\.[a-zA-Z0-9()]{1,6}\b([-a-zA-Z0-9()\+.]*)
this regexp is the one i am going to push to test today to unblock that kind of issue, however i have the feeling it still needs a lot of improvement and another way to validate a proper domain, here is why:
Example bogus domains:
a_domain.com
#domain.com
@domain.com
domainwtf_123.co.uk
<EMAIL_ADDRESS>
if we pick up those crafted bogus domains and test them ...
we know no domain should be allowed to be created with those characters however, users are creative and with that regexp, everything after the non-matched characters will still be valid and therefore it will still consider a valid domain which might cause further issues elsewhere, if a user makes a typo or something.
I guess we need to find a better way to validate a domain.

actually after some practical testing seems that one won't work really well either, so this will have to remain unchanged until i or anyone figures out a proper way of doing it, i am sorry for that =/

PR: #848 Pushed into test branch.
This PR fixes this issue and makes domain validation rock solid.
thanks @rrobgill

this has been merged today into Master branch.
Closing


[Bug]: VLLM's output is unstable version==0.5.1

Your current environment
using version==0.5.1 docker images:
command:
using model qwen2-GPTQ-Int4
docker run -it --rm --gpus  '"device=0,7,8,9"'  -p 8090:8090 -e NCCL_P2P_DISABLE=1 -e NCCL_SHM_DISABLE=1 -v /nfs2:/nfs2  -v /var:/var  -v /nfs3:/nfs3 -v /nfs5:/nfs5 --shm-size 20g XXXXXXXXX:XXXXXXX python3 -m vllm.entrypoints.openai.api_server --host=<IP_ADDRESS> --port=8090 --model=XXXX/source/deps --served-model-name=qwen2-GPTQ-Int4 --gpu-memory-utilization 0.9 --tensor-parallel-size 4 --seed 42;
🐛 Describe the bug
I generated 50 results by using http://XXXX/v1/chat/completions with params like:
   "model": "qwen2-GPTQ-Int4",
    "temperature": 0,
    "n": 1,
    "best_of":1,
    "presence_penalty":0.0,
    "frequency_penalty":0.0,
    "repetition_penalty":1.0,
    "top_p": 1.0,
    "top_k":1.0,
    "min_p":0.0

But I got different results eventhough most of them are the same(>90% are same)， .
Results LIKE:
['P41T33', 'P76T139', 'P76T140', 'P77T142', 'P111T257', 'P111T260', 'P111T261']
['P41T33', 'P76T139', 'P76T140', 'P77T142', 'P111T257', 'P111T260', 'P111T261']
['P41T33', 'P76T139', 'P76T140', 'P77T142', 'P111T257', 'P111T260', 'P111T261']
['P41T33', 'P76T139', 'P77T142', 'P111T257', 'P111T260', 'P111T261']
The instability increases with inputs larger than 8K. When I use 30K inputs, less than 70% of the results are stable
I'm not sure what's causing this.
Is it due to the quantized version, or something else?
Could you please help check if there's an issue with the parameters?
If stability in output is desired, where can I make adjustments?

I think this is a duplicate issue related to (#5404). Also, it has nothing to do with version 0.5.1, this bug has been discussed many times across previous versions.
In your case, I believe quantization is the problem. The hidden_state inputs for the logits_procesor are unstable for identical prompts. Maybe you can test with an unquantized version and see if this bug could be reproduced.

The efficient GPU algorithm implementation of GPTQ quantization models, many of which are not deterministic algorithms, such as autogptq implementation or exoma implementation, both use atomikadd. Different order of floating-point number accumulation can lead to result fluctuations due to accuracy errors. AWQ can be considered to avoid it, and our testing shows that it is feasible


Cannot read property 'length' of undefined

Using VSCode 1.10.2 I'm getting this error.

[Remark]
TypeError: Cannot read property 'length' of undefined

Do you use plugins?

Yes, but I disabled all of them and nothing changed.

You can provide your remark settings? Most likely your issue related to https://github.com/mrmlnc/vscode-remark#about-error-handling.

With this or without still the same.
remark.format":` {
        "rules": {
        "commonmark": true
    }}

Thank you for the clarification. Looks like a bug. I'll work on it very soon.
Last question: If you specify this config:
remark.format":` {
  "rules": {
    "commonmark": true
  },
  "plugins": []
}

The error continues to appear?

Well, it's weird.

Open file only - remark don't work
Open folder with same file - remark is working

https://gfycat.com/HonestUntidyAgama

I think there is a problem:
return vscode.workspace.findFiles('**/*remarkrc', '**/node_modules/**').then((files) => {

There is fix for that bug #8

Should be fixed in 1.1.0.


[update-checkout] remove master-rebranch

lldb\master-rebranch doesn't exist anymore
swift\master-rebranch doesn't serve any purpose anymore, I think?
the dated branches are still actively used for clang & llvm, and if swift needs changes from either repo it still needs to be cherry-picked into the dated branches to show up on stable.
This will fix PR testing for those respective branches/repos.

Thanks for taking care fo this, Cyndy!


Always increase instruction pointer

This is mostly an experiment.
There is currently a mismatch between what happens when a ? is thrown or a error is returned with break 'inst, this fixes that. I'm not sure if this is even needed, hence the draft

Once again we are running down the same paths. I was half way through fixing this, and making skipping errors an option I could toggle when I saw your PR. ended up borrowing the closure idea because I completely forgot that the block break and the ? operator would have different effects so thanks for reminding me.

you know what they say about great minds ;)


Dependencies fail to install under node v0.10.32

I didn't delve to deep to see why, but I can get this behaviour consistently on computers (Ubuntu Trusty 64 and OSX 10.9.5) using node v0.10.32, (also tested with npm v2.0.2. and v1.4.28)
npm ERR! Darwin 13.4.0
npm ERR! argv "node" "/Users/couto/.nvm/v0.10.32/bin/npm" "install"
npm ERR! node v0.10.32
npm ERR! npm  v2.0.2
npm ERR! path /Users/couto/.npm/f9748a33-adable-stream-1-0-32-package-tgz.lock
npm ERR! code EEXIST
npm ERR! errno 47

npm ERR! EEXIST, open '/Users/couto/.npm/f9748a33-adable-stream-1-0-32-package-tgz.lock'
File exists: /Users/couto/.npm/f9748a33-adable-stream-1-0-32-package-tgz.lock
Move it away, and try again.

npm ERR! Darwin 13.4.0
npm ERR! argv "node" "/Users/couto/.nvm/v0.10.32/bin/npm" "run" "dev"
npm ERR! node v0.10.32
npm ERR! npm  v2.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>dev: `npm install && gulp dev`
npm ERR! Exit status 47
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.
npm ERR! This is most likely a problem with the fabricator package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm install && gulp dev
npm ERR! You can get their info via:
npm ERR!     npm owner ls fabricator
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/couto/Development/MusikkiUI/musicphotos.org/npm-debug.log

and the npm-debug.log contents:
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/Users/couto/.nvm/v0.10.32/bin/npm', 'run', 'dev' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info predev<EMAIL_ADDRESS>6 info dev<EMAIL_ADDRESS>7 verbose unsafe-perm in lifecycle true
8 info<EMAIL_ADDRESS>Failed to exec dev script
9 verbose stack Error<EMAIL_ADDRESS>dev: `npm install && gulp dev`
9 verbose stack Exit status 47
9 verbose stack     at ChildProcess.<anonymous> (/Users/couto/.nvm/v0.10.32/lib/node_modules/npm/lib/utils/lifecycle.js:212:16)
9 verbose stack     at ChildProcess.emit (events.js:98:17)
9 verbose stack     at maybeClose (child_process.js:756:16)
9 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:823:5)
10 verbose pkgid<EMAIL_ADDRESS>11 verbose cwd /Users/couto/Development/MusikkiUI/musicphotos.org
12 error Darwin 13.4.0
13 error argv "node" "/Users/couto/.nvm/v0.10.32/bin/npm" "run" "dev"
14 error node v0.10.32
15 error npm  v2.0.2
16 error code ELIFECYCLE
17 error<EMAIL_ADDRESS>dev: `npm install && gulp dev`
17 error Exit status 47
18 error Failed at the<EMAIL_ADDRESS>dev script.
18 error This is most likely a problem with the fabricator package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error     npm install && gulp dev
18 error You can get their info via:
18 error     npm owner ls fabricator
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

If you need more information, please feel free to ask.

This is resolved by upgrading your npm: https://github.com/npm/npm/issues/6309


Potential SortJsFileImport bug

Hi @kristijanhusak
I have prettier formatter that formats import similar to this:
import {
  CircleButton,
  Button,
  Spinner,
  FormGroup,
  Centered,
} from './components/lib'

SortJsFileImport sorts it like so:
import {jsx} from '@emotion/core'

  Button,
  Centered,
  CircleButton,
  FormGroup,
  Spinner,
import Logo from './components/logo'
import React, {useState} from 'react'
import styled from '@emotion/styled'
import useCallbackStatus from './utils/use-callback-status'
import VisuallyHidden from '@reach/visually-hidden'
import {
import {Dialog} from '@reach/dialog'
import {useAuth} from './context/auth-context'
} from './components/lib'

This might be a pretty involved fix and it's not critical for me. I can disable sorting, but wanted to bring it to your attention.

Yeah there's already an issue for that. https://github.com/kristijanhusak/vim-js-file-import/issues/11 . I never spend a lot of time on it since it's not crucial.


[Channel idea]: Open AI (or another LLM)

Add another channel for small talk that utilizes AI...possibly hardcode something like What are fun things to do around ${location} as the prompt.
Potentially helpful reference on how to do this in Lambda

I think I wanna try this with AWS Bedrock since I've got those sweet sweet AWS credits to spend.


Improvements for gowin support

I had these changes laying around, thinking I'd submit a PR once it was "complete", but seems @dh73 and others are actually doing stuff with them, I figured better get it upstream now.
My branch has:

bram init
lots of dff types
some fixes
updated for Gowin IDE 1.9

@pepijndevos yes, please merge in latest master into this branch and try adding new tests for gowin (in yosys/tests/arch/gowin) . For simplicity just copy giles from efinix and check for proper expected results. Ping me if there are questions

Compared to efinix, the following tests are incomplete:

Latches are not implemented yet
FSM has a similar bug to efinix and seems too complex to pin down in numbers
Memory maps to dram due to small size, only the number of dram cells is tested.
Tribuf is not implemented yet

So I just added some tweaks to the ALU sim model as suggested by @daveshah1, and somehow it changed the number of LUTs used in the MUX test. Just to indicate how fragile these tests are...

Okay, I've added the byte-enable as @daveshah1 suggested. Here are some other things I'm aware of that are missing

[ ] Wide LUTs.
[ ] DSP stuff.
[ ] More BRAM modes, especially SDPX9. My current understanding is that single port and true dual port don't map to Yosys.
[ ] More DRAM modes.
[ ] MUXes, but they make synthesis worse, so not really.
[ ] Different ALU modes, but not sure how they map to Yosys. Currently using ADDSUB which maps nicely to $alu cells.
[ ] Tri-state buffers.
[ ] Latches. Seems nobody uses them but there is always this "support latches" issue on every HDL thing ever.

 I had my editor set wrong, and while trying to fix it, vim decided it was ok to reformat inside comments and strings. So after a few tries fixing the problem manually, I used some git fu from https://stackoverflow.com/questions/5669358/can-i-do-a-partial-revert-in-git to just... revert all the madness.
In other news, I've added wide luts with optional abc9. But for this specific case, abc9 actually seems to do worse:
=== 4 luts, abc ===

   Number of wires:                267
   Number of wire bits:            293
   Number of public wires:           3
   Number of public wire bits:      16
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:                285
     IBUF                            8
     LUT2                           39
     LUT3                           25
     LUT4                          205
     OBUF                            8

=== wide luts, abc ===

   Number of wires:                162
   Number of wire bits:            188
   Number of public wires:           3
   Number of public wire bits:      16
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:                180
     IBUF                            8
     LUT2                            1
     LUT4                           85
     MUX2_LUT5                      42
     MUX2_LUT6                      21
     MUX2_LUT7                      10
     MUX2_LUT8                       5
     OBUF                            8

=== 4 luts, abc9

   Number of wires:                286
   Number of wire bits:            312
   Number of public wires:           3
   Number of public wire bits:      16
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:                304
     IBUF                            8
     LUT2                           49
     LUT3                           26
     LUT4                          213
     OBUF                            8

=== wide luts, abc9

   Number of wires:                246
   Number of wire bits:            272
   Number of public wires:           3
   Number of public wire bits:      16
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:                264
     IBUF                            8
     LUT4                          128
     MUX2_LUT5                      64
     MUX2_LUT6                      32
     MUX2_LUT7                      16
     MUX2_LUT8                       8
     OBUF                            8

The area benefit from abc9 when using wide LUTs comes from the support for LUT libraries with per-input delays. Without these it's fundamentally got the same broken model as abc to work with.

Okay, I've added the byte-enable as @daveshah1 suggested. Here are some other things I'm aware of that are missing

[x]  Wide LUTs.

[x]  Tri-state buffers.

[x]  TBUF
[x]  IOB

[ ]  DSP stuff.

[ ]  More BRAM modes, especially SDPX9. My current understanding is that single port and true dual port don't map to Yosys.

[ ]  More DRAM modes.

[ ]  Different ALU modes, but not sure how they map to Yosys. Currently using ADDSUB which maps nicely to $alu cells.

[ ]  Latches. Seems nobody uses them but there is always this "support latches" issue on every HDL thing ever.

[ ]  MUXes, but they make synthesis worse, so not really.

This is only an advice: I would work on all those, let's call it, "advanced features" right before having the "basic ones" already working in the end-to-end flow (Yosys->NextPNR). Because, for example, to get the best from abc9, you need to know primitive delays, and that's the info you got by fuzzing/knowing the device. I would not add support for all types of memories and DSP yet, to Yosys, unless I really need them for a design that I'm actually using for fuzzing configuration bits of that specific primitive.
LUT models, RAM16S4/SDP, IO buffers are sufficient for a PoC. Once you reach that point, fixing the QoR must be the next goal.

This is why counting instances might not be a very good testcase: https://travis-ci.org/YosysHQ/yosys/builds/603937909
So current status of the tests are:

Latches are not implemented yet
FSM has a bug in equivalence
Memory maps to dram
Mux test is unstable and has an equivalence bug with wide muxes


Docs: Remove 'Restarting router pods running a previous version of th…

…e image' information from upgrading doc
Type of change
Select the type of your PR

Documentation

Description
Remove the restarting router pod information from the upgrading section of the docs, since it is no longer needed with fix from PR #3256
Checklist
Please go through this checklist and make sure all applicable tasks have been done

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[X] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@lulf Can you approve please?


Table Export to CSV?

You can export a chart contents to CSV but not a table?  This project is 99% of what we need for some internal reporting, this would be the remaining 1%...
Great project, btw.  Been using ART (Another Reporting Tool), but your report creation process is much easier for end users.

Thanks for using Poli! I just tried it  and I do see the export CSV button when I hover the cursor over the top right corner of the table widget. Could you try it and let me know it works for you?
I checked the doc and it just mentions click the export button but not hover the cursor. I will fix that.

Zhonglu,
That is awesome.  I hadn't created a chart yet, so I thought that CSV export button was there (no hovering).  I did verify that I was able to find and select that button by hovering and then clicking the  CSV button.
Selecting it seemed a little flakey with Chrome 75.0.3770.142 on Windows 10.  When you got close, the button would appear, but when you attempt to center over it, it disappears.  I just clicked in that area and it did download (quite quickly - nice!).
Is there a default setting somewhere for the filename that is generated?  Selecting the export downloads a file called csv with no extension.  Under Windows, that requires either locating the downloaded file and renaming it or selecting a program to open an unknown file type.
Thanks for your prompt reply!
Mike

About the flakey problem, I tested it and I believe the cause is when the table has no title, the CSV button is kind of overlapping with the right edge of the table which triggers the column width adjustment event. I will take a look into that.
The CSV file name has a bug. If the component has no title, the file is supposed to be downloaded as
poli.csv otherwise "component title".csv. There was another request asking for providing a pop up to edit the file name before export the file. I will add that dialog to fix this issue.

Verified that providing a title to the component resulted in an export to a file with the same name with a CSV extension.  Awesome.

v0.9.1 is now released which contains the fixes for renaming CSV file and export CSV button.


ISPN-1801 - Virtual nodes should be enabled by default

https://issues.jboss.org/browse/ISPN-1801
Also t_1801_51 for the 5.1.x branch.
I set the default number of virtual nodes to 48.
I added a test for key distribution with various numbers of virtual nodes,
48 seems to be a reasonable default.

@Sanne I wanted to keep the existing behaviour - all I needed was to reduce the number of calls to LogFactory.getLog() to make my test go faster.
I think we had a discussion about not logging subclass names on the mailing list, but I don't remember if we reached a conclusion...


Edited Timer Layout

Edited Timer Layout
Added Timer inputs hrs,Minutes and Seconds.
Added Category selector in report Page.

Done.

Time form field in hours minutes and seconds


Add http connection timeout as a configuration to all autoscaler components

[#160241806]

the setting should be http_client_timeout instead of http_request_timeout

@boyang9527  updated.


Selection not working inside code blocks

Reproduction steps:

Go to https://docs.npmjs.com/cli/v9/using-npm/workspaces#defining-workspaces
Try to select part of the code and copy it
It is not possible to select and copy code

Expected Behaviour
It is possible to select and copy code.
Actual Behaviour
It is not possible to select and copy code.

Is this issue still there, cause I am able to copy  a part of the code.

The issue is still reproducible for me in Chrome 114 as well as Firefox 115 on Ubuntu 23.04.

Ok. So what I did was:- double click the code and move the pointer vertically to the selection instead of moving it horizontally.
Or, you can just double click the code and move the selection with the help of up and down arrow keys.
Try this, I think it will work.

Thanks for your help, when using arrow keys the selection works!
Still I feel like something odd is going on with mouse selection. Please check out the screencast:
https://github.com/npm/documentation/assets/23744935/a0f34769-39b4-402e-bdbf-a4b39ec264ee
While selection works normally for text, I can only select one character or the whole code block.
I believe the issue might have something to do with this absolute positioned div element:

When I removed this element using devtools, selection for code blocks started working normally.


Font Inscription Preview

We need a way to view font inscriptions. This PR adds an editable textbox in the iframe that loads the font in the preview from the inscription so you can test it out and see it.

this is dope

@elocremarc I just read that the format() declaration is optional, so I think we can just omit it, and the browser will auto-detect the font type.

@casey way more elegent. It works! Just pushed changes.

Made some style tweaks broke it out into a css file again. See if your satisfied with how the CSS renders on the iframe and preview page.


The anonymous user feature causes the app to crash on production with newArch enabled

Report
Plugin Version
6.15.1
On what Platform are you having the issue?
ios and android
What did you do?
Enabled the New Architecture and build
What did you expect to happen?
I expected the RNAppsFlyer.anonymizeUser() to return boolean
What happened instead?
I got this error
AppsFlyer Error [Error: RNAppsFlyer.anonymizeUser(): Error while converting JavaScript argument 0 to Objective C type BOOL. Objective C type BOOL is unsupported.]

Same here.
Solve it temporarily by removing the unneeded pointer of a boolean parameter at the POD: (react-native-appsflyer/RNAppsFlyer.m):
Replace this:
RCT_EXPORT_METHOD(anonymizeUser: (BOOL*)b callback:(RCTResponseSenderBlock)callback) {     [AppsFlyerLib shared].anonymizeUser = b;     callback(@[SUCCESS]); }
with this:
RCT_EXPORT_METHOD(anonymizeUser: (BOOL)b callback:(RCTResponseSenderBlock)callback) {     [AppsFlyerLib shared].anonymizeUser = b;     callback(@[SUCCESS]); }


Add parameter to kubectl explain for searching field descriptions

What would you like to be added:
I would like kubectl explain to be able to function like find so that I can quickly search for a field that has certain description text.
Why is this needed:
I love kubectl explain. I use it often. I like to use it as a tool to quickly find if a CRD supports certain functionality. For example: I might want to quickly determine if a new operator supports custom TLS options. This often involves a process like:
kubectl explain {{CRD}}
kubectl explain {{CRD}}.spec | grep tls
kubectl explain {{CRD}}.spec.networking | grep tls
etc, etc

Depending on the size and formatting of the CRD this can be a long process.
I think it would be really helpful if I could use kubectl explain like kubectl explain {{CRD}} --find "tls" and the tool would find the fields with "tls" in the description and return explain output for each field. For example if kubectl explain {{CRD}} --find "tls" discovered reference in {{CRD}}.spec.tls then it would return output from kubectl explain {{CRD}}.spec.tls
kubectl explain {{CRD}} --recursive does not satisfy this requirement as it only lists field names and data type.
I am curious if there is any appetite for a feature like this to be added to kubectl.

That seems like a very specific use-case, and I could see a verbose recursive version would possibly make more sense IMO, since you would be able to grep tls in the whole list and then find what you need?

I don't think that's so much work. Can we come-up with a better way to observe the level of nesting? Some ascii-art to show the structure? Maybe colors?

Sure let me check it out a little bit, i'll share my findings here soon

I think intent is the best way to show this kind of document, we can discuss about adding colors but personally i am not fan of colors in terminal, rather read it in black and white(seems easier for me but IDK), so i cleaned up the example i showed earlier and this is the result.
Lets say we have a flag named verbose-nested
for verbose-nested=0 or undefined act as what it is right now:
KIND:       Pod
VERSION:    v1

DESCRIPTION:
    Description

FIELDS:
  field_name	<field_type>
    Description of this field

  field_name	<field_type>
    Description of this field

for verbose-nested=1  we add one level of details :
KIND:       Pod
VERSION:    v1

DESCRIPTION:
    Description

FIELDS:
  field_name	<field_type>
    Description of this field

    FIELDS:
      field_name	<field_type>
        Description of this field

      field_name	<field_type>
        Description of this field

  field_name	<field_type>
    Description of this field

for verbose-nested=2  we add another level of details :
KIND:       Pod
VERSION:    v1

DESCRIPTION:
    Description

FIELDS:
  field_name	<field_type>
    Description of this field

    FIELDS:
      field_name	<field_type>
        Description of this field

      field_name	<field_type>
        Description of this field

        FIELDS:
          field_name	<field_type>
	    Description of this field

          field_name	<field_type>
	    Description of this field

  field_name	<field_type>
    Description of this field

and for verbose-nested=-1 or something else we can do this until we show all the detail of this resource.
The main difference with --recursive label is that we have more detail and we add \n for better readability but also we can change those too.
I'm very open to suggestions to make it better and also willing to help implement this.

I generally agree that colors are pointless, but I was more thinking of something similar to git log --graph. I would try something like this, in which case I think making each line in a different color would have a lot of value:
KIND:       Pod
VERSION:    v1

DESCRIPTION:
    Description

FIELDS:
* field_name	<field_type>
|   Description of this field
|
|   FIELDS:
|   * field_name	<field_type>
|   |   Description of this field
|   |
|   * field_name	<field_type>
|   |   Description of this field
|   |
|   |   FIELDS:
|   |   * field_name	<field_type>
|   |   |   Description of this field
|   |	|
|   |   * field_name	<field_type>
|   |   |   Description of this field
|   |   |
* field_name	<field_type>
|   Description of this field

Its for sure interesting but i'm not sure which visual is easier to read for end user, if you agree we can discuss this at regular meeting and ask about other ones opinion as well, for example maybe using little dashes - to style it like yaml file can be interesting too.
At least we are on same page to print FIELDS like this.

My problem is that counting the spaces in a terminal is really confusing/hard, especially once we get much deeper inside the recursion.

/triage accepted
@ah8ad3 if want to take this that would be appreciated but if not we can leave this accepted and someone else can pick it up. This may be a bit of a complicated implementation, though.

Thanks @mpuckett159, i'll take it but i am not sure about implementation, yesterday unfortunately i wasn't available to the meeting, i wanted to ask about your'e opinion about implementation of what @apelisse suggest. I'll assign myself and start working on it.
/assign

It's almost implemented, i have a questions about it.
We already have a recursive flag that prints only key value of fields without descriptions.
What name do you suggest for the flag to print all the details(description) for recursive flag? @apelisse @mpuckett159
And also the final view is something like this:
*  secretRef    <LocalObjectReference>
|  |  secretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it
|  |
|  *  name      <string>
|  |  |  Name of the referent.  Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it
|  |


Shutting down an Integration Daemon causes a null pointer exception

If an integration daemon has encountered an error during startup either configuration or runtime exception, the server hosting Integration Daemon will start successfully.
However shutting down the same same server will cause a null pointer exception to be thrown.
from the audit log
Wed Dec 02 09:46:54 GMT 2020 postgresConnectorServer Shutdown OMAG-ADMIN-0007 The postgresConnectorServer server has detected an java.lang.NullPointerException exception during server shutdown.  The error message was null
and as a response to the stop command
{
"class": "VoidResponse",
"relatedHTTPCode": 500,
"exceptionClassName": "org.odpi.openmetadata.adminservices.ffdc.exception.OMAGConfigurationErrorException",
"exceptionCausedBy": "java.lang.NullPointerException",
"actionDescription": "deactivateTemporarily",
"exceptionErrorMessage": "OMAG-ADMIN-500-001 Method deactivateTemporarily for OMAG server postgresConnectorServer returned an unexpected exception of java.lang.NullPointerException with message null",
"exceptionErrorMessageId": "OMAG-ADMIN-500-001",
"exceptionErrorMessageParameters": [
"postgresConnectorServer",
"deactivateTemporarily",
"java.lang.NullPointerException",
null
],
"exceptionSystemAction": "The system is unable to configure the OMAG server.  No change was made to the server's configuration document.",
"exceptionUserAction": "This is likely to be either an operational or logic error. Look for other errors.  Validate the request.  If you are stuck, raise an issue."
}

resolved so closing the issue.


⚠ Bofrost.be has degraded performance

In 5ae22b6, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1076 ms

Resolved: Bofrost.be performance has improved in 74dd2ba after 13 minutes.


[Feature]

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Invalid issue.


Unable to view Cloudtrail events in Global Region

IAM actions and other global services log records in us-east-1 of Cloudtrail, because of GLB1 of 4.8.2. Sensitive policy users are unable to diagnose issues within IAM.
https://github.com/aws-samples/landing-zone-accelerator-on-aws-for-tse-se/blob/bd511d46aee84dbffd33c9052e5800223bc43419/config/service-control-policies/LZA-Guardrails-Sensitive.json#L216-L288
This affects usability and end users are presented with the below when viewing Cloudtrail within us-east-1:
User: arn:aws:sts::XXX:assumed-role/AWSReservedSSO_AWSAdministratorAccess_2903639fd9b44a7f/richard.keit.lza.2.sso is not authorized to perform: cloudtrail:LookupEvents with an explicit deny in a service control policy

Hi Richard,
Thank you for creating this issue. I will bring this to the team, and we will review.

This made it into the v1.11.0-a release. Thanks!


Clarify readme about searching in the admin

The readme says: "Supports common filtering lookups, such as field__icontains so that Django Admin search_fields works out of the box."
In reality only exact matches work in the admin: the code in lookups.py tries to interpret the full string that was entered in the search box as a hashid, if it cannot then the search returns no items (or raises an exception depending on HASHID_FIELD_LOOKUP_EXCEPTION ).
Given that only an integer id is stored in the database (and not the hashid string), it makes sense that partial searches dont work (that would require generating all hashid values starting at one, and comparing to the search string). What I suggest is clarifying the docs.

Thank you for pointing this out. I think when I wrote the docs I was thinking of the fact that a basic search in the admin runs an __icontains query, so I made efforts to make that at least work when pasting in hashids. I will clarify the docs to specify that it works with an __icontains and others, but they do full-string matches and are case sensitive per the way that Hashids works.


Tests fail that have nothing to do with my changes. What should I do?

When I run rake I'm getting 1 failure and 7 errors. This is right after cloning the project so I know I didn't break this gem. I made the changes, tested (and got no new errors other than those it currently had) and did a pull request but the pull request failed because Travis CI determined there was an error in the build. It looks as though under many versions of Ruby the gem is passing tests with the exception of Ruby version 2.1.10. I'm running  Ruby versions 2.1.5 and 2.4.0 and tested the gem under both with the same error.
The error is:
NoMethodError: super: no superclass method backward' for Faker::Time:Class`
multiple times in the faker/time.rb file.

Is this still an issue? I have pulled the most recent master branch and don't have any failures.
I ran rake test from a docker container, so it is a clean environment.
To run the tests from a container you can just start a new disposable container and start bash:
docker run -it -v "C:\Projects\Github\faker":/myapp -w /myapp ruby:2.1.10 bash (you will probably have to change the path to your local faker folder)

Seemed to work okay with 2.4.0.

The Time class should allow calls to super because it is a subclass of the Date faker class. All it does is add some additional time data :+1:

Closed by #971


How can I get the word embedding from Transformer

Hi,
I need the word embedding of Transformer,
but I donot know how to get word embedding.
Can anyone help me?
Thanks

Sure, the weight we save at every epoch contains the word embedding weights.
Starting with checkpoint = torch.load('your_saved_model.pt'), and you could find the key corresponding to the target embedding weight in the checkpoint.


Minimap overlaps with other dropdown menus

Minimap overlaps with other opened dropdown menus, such as Help & Resources (perhaps Profile menu too, when/if it gets longer):
.

Never mind background color, i had DarkReader enabled :)


📝 Add External Link: Explore How to Effectively Use JWT With FastAPI

Added Article on how to Effectively Use JWT With FastAPI

📝 Docs preview for commit 3da75be36cd7860d5c4b9985cda1101fb955a54c at: https://7feb498e.fastapitiangolo.pages.dev

Nice! Thanks @aanchlia 😸
And thanks for the review @hasansezertasan ✌


Add the ABOUT section on website

I want to add the about section. Please assign me this issue under GSSOC'23.

try to refer figma from readme and use that color code

Hi @codervivek5, could you please assign this issue to me because no PR has been created for this issue since 2 weeks.
Please assign this issue to me under GSSOC'23, I have understood the issue and will quickly create the PR for this once you assign it to me 🙏

heyy Can I work On this Issue


marathon add not resolving / finding Package.swift

When doing the following
marathon add https://github.com/kareman/SwiftShell
marathon add https://github.com/kylef/PathKit
I get
💥  Could not resolve the name of package at 'https://github.com/kylef/PathKit'
👉  Make sure that the package you're trying to add is reachable, and has a Package.swift file
Both are reachable and have Package.swift in their root directories - is there possibly some other thing making them incompatible that isn't being shown in the error message?

@mathieutozer Hi, and welcome to Marathon 👋 You need to give the add command a Git URL to add. So in this case, simply append .git to the URLs that you want to add and it'll work. We can definetly improve the error message Marathon displays to give you better information on why adding these packages failed 👍

That worked, but for SwiftShell's case I am now getting
marathon add http://github.com/mathieutozer/SwiftShell.git
🏃  Cloning http://github.com/mathieutozer/SwiftShell.git...
Resolving latest major version for http://github.com/mathieutozer/SwiftShell.git...
💥  Could not resolve the latest version for package at 'http://github.com/mathieutozer/SwiftShell.git'
👉  Make sure that the package you're trying to add is reachable, and has at least one tagged release
It looks like the project does have tagged releases https://github.com/kareman/SwiftShell/tags

@mathieutozer You are missing an "s" in "https" in your URL 🙂 Use this command and it will work:
marathon add https://github.com/mathieutozer/SwiftShell.git

oops ☺

@mathieutozer 😄 Cool if I close this?


dnd: dragging/sorting item in the nested cdkDropList always goes to the outermost cdkDropList

What are you trying to do?
Dragging or sorting inside/outside the nested droplist.
Allow items in the nested droplist sorting inside/outside itself, even drag into the nested droplist of nested droplist and vice versa.
P/S: All droplists are linked to each other.
The current behaviour is that when to start dragging a nested list item, it will instantly get and move to the outmost container/droplist instead of within the nested droplist. It takes the outermost container because of the cursor is also located in it and according to _getSiblingContainerFromPosition function, it will take the first sibling container (which is outermost container) and ignore the inner containers.
Also, the function only considers getting the siblings and ignores the current container itself causing that we cannot do any sorting in the nested container and always move to the first outermost container.
What troubleshooting steps have you tried?
I tried to modify the  _getSiblingContainerFromPosition which is not recommended solution.
I do not know is there any way to achieve it but it works perfectly after I modify the function.
_updateActiveDropContainer should call _getContainerFromPosition which includes current container itself and also sibling containers, and resort it ascending order by the number of the droplist contains (find function will get the innermost container first instead of the outermost container).
Please advise. Thank you so much :)
Reproduction
We can only help if we can reproduce the problem ourselves.
https://stackblitz.com/edit/components-issue-dmuqfv?embed=1&file=app/zoo/zoo.component.ts
Steps to reproduce:

Items can be drag into another droplist.
Only items under the outer container can do the sorting.
When doing sorting for nested droplist items, it will move to the outer container.

P/S: Please ignore other buggy things since this sample code is to demonstrate for the mentioned issue only.
Environment

Angular: 8
CDK/Material: Drag and Drop
Browser(s): Google Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows Server 2016

@Splaktar thank you so much!

Any news about this? Maybe a workaround or something.

@heshamelsawaf Just struggled a few days with this too.
If you can't get around with using another library (we ended up using https://swimlane.github.io/ngx-dnd/), the only real workaround is too flatten the list, and use multiple layouts based on the meta-data. It takes a lot more work, and it's not worth it imo.

Would be great to have nested drag drop support

Duplicate of https://github.com/angular/components/issues/16671.


Exercise: Review JS Best Practices.

Hey, my learning partner, I have done the following changes and I want to implement these:

Added index.html
Added styles.css
Added script.js
Added README.md

Thanks a lot for the positive feedback. Best Regards


Create support us modal

On clicking support us button present anywhere on the website, a support us modal should pop up.
first link should open linkedin
second link should open djangoindia.org github
third link should should open djangoindia.org issue section.
Design:

Hi, I am working on this.

closed via #51


Check normalization of source mass for dose evaluation in FISPACT

Check if the dose rate is or is not always computed for 1g source in FISPACT v.5.
If not, then scaling by mass is applicable to the dose values.
Now we assume that there's always 1g.

Stale issue message


MDMAPP-1426: Remove IDFA from phohegap-plugin-push

Remove FirebaseMessaging pod
Remove FirebaseMessaging Objective-C code
Add new logs
Fetch always silent pushes

Is cool, maybe i would remove many of the logging, but i guess is also fine

Mmmm for me the logging is OK. it's easy to debug if there is any problem and is not reporting any sensitive information.


Looking for a starter example or Documentation

Is there any starter example or documentation for oak with reactjs?

hi 👋  basic usage can be found here: https://github.com/p3ol/oak/tree/master/packages/oak-react and if you need a more complex example: https://github.com/p3ol/oak/blob/master/packages/oak-react/lib/index.stories.js


Right click menu for parking areas to change their color manually

we should discuss about menu for each group of curbstones within an area.

@ortroyaner -  Please set a milestone to this issue.

Not relevant to this version of the project, has been closed.


Wrong class installed via composer

Hi, i'm getting a wrong class when I try to install this lib in my project.
I am using php 7.4
I run composer require josantonius/session --prefer-source  and I get this class:

which is "slightly" different from this:

That is correct. For PHP 7.4 the last available version is 1.1.9 (deprecated). As of version v2.0.0 it was completely restructured, as you can see in the CHANGELOG.

Thank you! I saw now the requirements too

Is there a chance for a version compatible with php 7.4 ?

It is not ideal, but you could replace the code in the files. By removing the mixed data types and making a few small changes, it would already be compatible with PHP 7.4 (tests will not work).
I share with you the modified files 😉
Session.txt
Facades-Session.txt

Thank you so much! I appreciate!


Run osg-test out of minefield when GitHub repo/branch aren't specified

The only reason people use osg-test out of the repos these days is to test the osg-test RPM itself

I was amused by keeping the comments at osg 3.1, 3.2  :D


Release <IP_ADDRESS>

OpenSearch 2.10.0 has been released, see release notes.
Official OpenSearch release ticket: https://github.com/opensearch-project/opensearch-build/issues/3743
Checklist:

[x] Compatibility Matrix is updated (#232)
[x] Release <IP_ADDRESS> tag is present in the repo
[x] Release artifacts are available and downloadable
[x] Release notes published
[ ] Forum announcement published

Forum announcement: https://forum.opensearch.org/t/prometheus-exporter-plugins-2-10-0-0-and-1-3-13-0-released/16072


[feat/fix]: Make the hero.png image size bigger

Related Issue

Information about the related issue

Closes #10.
Describe the changes you've made

Make the hero.png image size bigger so it doesn't look blurry.

Hopefully, it will work. 😅

Type of change
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] 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?

Checklist

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Original
Updated

original screenshot
updated screenshot

Looks much better but is still blurry. Working on that.

How does it look like this? I'm using 2/5 option. I think this looks very good.

Using the image that the website currently has.


Better documentation on features & config is needed

Issues include:

How to define a req file
Modifiers v single cookie adjustments
What does a bot mod do? (actions on behalf of others and default reqs)
etc etc

currently working on this issue


Add manual.

if you have a work computer, it is recommended to use only 80% of the RAM.
All settings are specified for a working computer!
bPfile must be a multiple of 32 (Gb memory * 134217728)
Create a file for 2 GB memory with a dual core processor: ./bPfile 268435456 ./bPfile.bin -t 2
P .S: On Windows, use PowerShell.
dear developers, please check my numbers and if they are correct it may be worth adding them to the description for other people to understand.
+-----------------------------------------------------------------+
|   Gb memory | - k     | bPfile  (134217728 * gb)  | Size gb HDD |
+------------ | --------| --------------------------| ------------+
 | 2          | 64      | 268435456                 | 8,192       |
| 4           | 128     | 536870912                 |             |
| 8           | 256     |<PHONE_NUMBER>                |             |
| 16          | 512     |<PHONE_NUMBER>                |             |
| 24          | 768     |<PHONE_NUMBER>                |             |
| 32          | 1024    |<PHONE_NUMBER>                |             |
| 64          | 2048    |<PHONE_NUMBER>                |             |
+-------------+---------+---------------------------+-------------+

If the -n parameter is specified, these values change according to the situation.

all this can be calculated by running the program without the -p flag. It is enough to look at bloom filter 1 and start creating a table with filter 1 parameters.

I do not pretend to be complete, but for those who want to try but little knowledge, I think it will be useful!

The value of the -k flag can be different  -k 200 and -k 220 or -k 240. It is better to always look at the number of bloom filter 1 elements and generate a table according to your values.

Thanks guys i will check those values.
Best regards

The calculations in the table are not correct.
I have To 2500 and the memory is occupied by 35.9 GB and bPfile<PHONE_NUMBER>.
And according to table K, it should be about 1100.
Also, the data on the bPfile table simply does not start.
For example, with my K 2500 bPfile 895825408-starts.

Thanks guys i will check those values.
Best regards

The calculations in the table are not correct.
I have To 2500 and the memory is occupied by 35.9 GB and bPfile<PHONE_NUMBER>.
And according to table K, it should be about 1100.
Also, the data on the bPfile table simply does not start.
For example, with my K 2500 bPfile 895825408-starts.


Cleanup dask.array.reductions

Improve dtype compatibility with numpy, increase testing of functions.

I'm not sure what the error is caused by - for me this failure happens on current master, and has nothing to do with the changes I made.

I've been bad and pushing to master a bit lately.  This might be my fault.  Will check it out.

It's due to a new version of pandas being released - we're missing a "name" for the series in the result that pandas now has. Looking into why this happens now.

This seems fine to me.  OK to merge?


repeated 'selectNextOccurrence' commands cause tab to freeze

Open https://codemirror.net/demo/sublime.html
Paste in the first ~600 lines of codemirror.js
Put cursor into a 'var' token
Press down ctrl/cmd+d

Expected:
Selections add up until all 'var' tokens are selected.
Actual:
Selections start adding up, but part way through the file the performance gets bad enough that the tab freezes for O(minutes).
Reproduces on Chrome 48, Mac and Ubuntu.

This triggered a rather bad layout trashing, which attached patch addresses. I wasn't able to get it to hang for minutes, but I did get 5 second hang, which was reduced to 400ms by this patch. Could you test this and see if it yields decent performance in your use case?

It still gets super slow if I have 200 lines of "var foo = var foo = var foo = var foo = var foo". Then if I again have my cursor in 'var' and hold ctrl+d, it goes at a constant speed till around line 50-60, and then quickly gets much slower and grinds to a halt around 90-100.

The time seems to be mostly spent in positioning all the individual selection elements. The way CodeMirror handles selection updates involve redrawing the whole thing on every update, which becomes significant work once you have 500 selected ranges, since it involves finding the position of each of those ranges. I did some poking around and this doesn't appear to be a case of an accidental expensive computation (as it was before) -- this is just what tons of selections cost, in CodeMirror's implementation. The code isn't really designed with that many selections in mind (most of it was written before we had multiple selections), and I don't see any low-cost changes that would solve this (updating selections lazily would introduce a bunch of new complexity, and still not help when code above the selections changes, unless we somehow anchor them to the text, which isn't something CSS makes easy).

This is positioning in the HTML, as opposed to abstractly computing the locations at which selections should appear? Since CM draws only (roughly) the viewport-visible part of the code, whould it also be possible to limit selection-drawing to only those that intersect the viewport?
This may also be a relevant read.

whould it also be possible to limit selection-drawing to only those that intersect the viewport?

That's what my previous patch attached to this issue (0291f72325ebd74cf56) implements. However, if you have a lot of tightly packed selections, as in your test case, it doesn't help enough. The issue is also that holding down a key is going to need to update the display for every event -- you can create and draw 500 selections in under a second, but creating 500 selections and drawing them on every update (500 / 2 * 500 = 125k drawn selection) is a lot more work.