Snyk reports high risk severity for acorn in react-scripts

Describe the bug
Snyk reports high severity issue with react-scripts. See details below:
Regular Expression Denial of Service (ReDoS)
Vulnerable module: acorn
Introduced through<EMAIL_ADDRESS>Exploit maturity: No known exploit
Fixed in: 7.1.1

Detailed paths
Introduced through<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Remediation: No remediation path available.
Introduced through<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Remediation: No remediation path available.
Introduced through<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Remediation: No remediation path available.

…and 14 more
Overview
acorn is a tiny, fast JavaScript parser written in JavaScript.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via a regex in the form of /[x-\ud800]/u, which causes the parser to enter an infinite loop.
This string is not a valid UTF16 and is therefore not sanitized before reaching the parser. An application which processes untrusted input and passes it directly to acorn, will allow attackers to leverage the vulnerability leading to a Denial of Service.
Did you try recovering your dependencies?
Yes.
Please paste the output of npm --version and/or yarn --version to confirm.
6.13.7
Which terms did you search for in User Guide?
Not applicable.
Environment
Environment Info:
System:
OS: Windows 7 6.1.7601
CPU: (8) x64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Binaries:
Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.21.1 - C:\Program Files (x86)\Yarn x\bin\yarn.CMD
npm: 6.13.7 - C:\Program Files\nodejs\npm.CMD
Browsers:
Internet Explorer: 11.0.9600.19301
npmPackages:
react: ^16.13.0 => 16.13.0
react-dom: ^16.13.0 => 16.13.0
react-scripts: 3.4.0 => 3.4.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
Install new version of React.
(Write your steps here:)

npx create-react-app my-app
Test with Snyk.io

I also have the same issue

As do I! Feeling less lonely now

I also have this issue.
npm audit throws that the acorn vuln is patched in version >=7.1.1. I don't know if installing directly the acorn module to the latest version with npm install acorn@latest will solve it. Gonna give it a try and share my results.

@SirMauri any results?

Setting resolutions in package.json is the better approach if using yarn as you don’t explicitly set a dependency on acorn in your project.

@bpedersen thanks for the recommendation, this clears the warnings in yarn audit.
  "resolutions": {
    "acorn": "^7.1.1"
  },

Adding the resolution worked. I came across this issue while working on a very small project using create-react-app. I'm pretty new to coding but I couldn't find a way to address this with npm. I just switched over to yarn but I'm still curious, what can be done about this in projects set up with node package manager?

@dusty @bpedersen @BMD-518
It may remove the warning to manually set the resolution, but does it affect anything in the Create React App in any way? Like, any functionality?

I haven't noticed any build issues with the patched acorn.

@dusty
And no visible bugs in any React apps?

Are there fix for this ?

Any fix for npm? I've found 17 moderate severity vulnerabilities related to react-scripts using acorn.

This needs to be fixed asap because it affect developers using create-react-app.

resolution worked for me

Running npm, I was able to fix it temporarily by
adding to package.json scripts:
"preinstall": "npx npm-force-resolutions",
and adding to package.json
 "resolutions": {     "acorn": "^7.1.1"   }
waiting for react-scripts update though.

Running npm, I was able to fix it temporarily by
adding to package.json scripts:
"preinstall": "npx npm-force-resolutions",
and adding to package.json
 "resolutions": { "acorn": "^7.1.1" }
waiting for react-scripts update though.

For others attempting this fix, please be mindful of your other dependencies that uses acorn.
Tried this solution and sadly 7.1.1 broke some of my other dependencies.
Guess I'll have to wait on actual fixes shrugs.

Running npm, I was able to fix it temporarily by
adding to package.json scripts:
"preinstall": "npx npm-force-resolutions",
and adding to package.json
 "resolutions": { "acorn": "^7.1.1" }
waiting for react-scripts update though.

For others attempting this fix, please be mindful of your other dependencies that uses acorn.
Tried this solution and sadly 7.1.1 broke some of my other modules.
shrugs, guess I'll have to wait on actual fixes.

Solved it temporary by using npm-audit-resolver

Any updates ?

any updates on this so far?

same here :
`Moderate        Regular Expression Denial of Service
Package         acorn
Patched in      >=6.4.1 <7.0.0 || >=7.1.1
Dependency of   react-scripts
Path            react-scripts > jest > jest-cli > jest-config >
jest-environment-jsdom > jsdom > acorn
More info       https://npmjs.com/advisories/1488
`
any updates ?

Same here,
I try to use the work around with the version 7.1.1, but "broke" my app, so I tried use 6.4.1 and worked it for me.
But still a work around...
"scripts": {
    **"preinstall": "npx npm-force-resolutions",**
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject",
    "lint-quiet": "eslint . --quiet",
    "start-prod": "node app.js"
  },
  "resolutions": {
    "acorn": "^6.4.1"
  }

any updates ?

https://github.com/facebook/jest/issues/9643
Update to jest v25.1.0 required in order to fix that vulnerability. It has some breaking changes, so I don't know if that's doable.

Well, I had taken the resolutions route but just removed the resolutions from my package.json and ranyarn audit after updating packages and I'm no longer getting any vulnerabilities.  So.. maybe it's been fixed?

I don't know if is a fix. I did the yarn audit.

yarn audit
yarn audit v
1.19.1
info No lockfile found.
warning @material-ui/core ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
warning react-scripts > jest-environment-jsdom-fourteen > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning react-scripts > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning react-scripts > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()
warning react-scripts > workbox-webpack-plugin > workbox-build > strip-comments > babel-plugin-transform-object-rest-spread > babel-runtime ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
0 vulnerabilities found - Packages audited: 920690
Done in 31.75s.

But, as is show, it doesn't fix, just show that is deprecated, but not upgrade or anything. Actually, I don't know what yarn did to show 0 vulnerabilities...
But when I did "npm i", in my "package-lock.json" has been change, in jsdom, the version of acorn from 6.4.1 (has no issues) to 5.7.4, that has the main problem (vulnerability issue).
But still with 0 vulnerabilities, even with acorn 5.7.4 ¯_(ツ)_/¯

Acorn 5, 6 and 7 have all had patch releases fixing it, so this shouldn't be an issue anymore

I deleted the node_modules folder, the lock files (npm and yarn) and I did:
yarn
And everything is ok, 0 vulnerabilities
After, I did npm i (why not? ¯_(ツ)_/¯)
Also 0 vulnerabilities.
To finish, yarn start and is working fine.
I think it can be close this issue.

New patch worked for me!  Ran an npm audit fix and it was able to fix the vulnerabilities with the new patch available.

Issue confirmed fixed after deleting package-lock.json, deleting node_modules, running npm install and then npm audit fix again.
Also reran Snyk test and no more acorn vulnerabilities.


adds list of imports for telemetry

Analytics
This PR adds a list of imports for our telemetry. Right now it includes the libraries listed in wandb_telemetry.proto, let me know if these should be removed from the file
I believe @raubitsj mentioned that this list needed to be batched for CircleCI to be able to deal with it, happy to make changes to handle this batching too.
------------- BEGIN RELEASE NOTES ------------------

adds list of relevant external libraries for analytics
------------- END RELEASE NOTES --------------------

From Jeff: Notes to the next person who picks this up
We need to restructure this so that we compute an intersection between the list of modules that are imported and the list of modules we care about, rather than searching through linearly. We have 67 things in the list so it can't be too slow.


Make it clear you can't copy/paste the command for installing K8s command line tools.

path export (path/to/kubernetes/platforms/...) should be formatted to indicate that you can't just copy-paste

Documentation: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/gce.md#installing-the-kubernetes-command-line-tools-on-your-workstation

use angle brackets or curly braces


Key repeat in hyper canary

[ ] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name:  MacOS 12.13 High Sierra
Hyper.app version: 2.0.4
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/pablopunk/5af1eb66a0ecd9833a252a63d38c3547
Relevant information from devtools (CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere): N/A
The issue is reproducible in vanilla Hyper.app: Canary straight out of the box

Issue
Basically pressing and holding any letter won't repeat it. Like, I press and hold k and it prints just one.
Also, if I press and hold space it does repeat this one.

Issue originates in term.js: https://github.com/sourcelair/xterm.js/issues/265

Here's a workaround: https://stackoverflow.com/questions/39972335/how-do-i-press-and-hold-a-key-and-have-it-repeat-in-vscode
While we investigate the best way to solve this.

defaults write co.zeit.hyper ApplePressAndHoldEnabled -bool false

Doesn't seem to work for me :(

I fixed it for all apps on my mac:
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool false

Then reboot and it's done!

@pablopunk thanks for sharing, do you know of any way for the below command to take affect without a reboot?
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool false

@ipatch not sure, maybe logout and login, try that.

looks like xterm recently fixed this problem on their end

Fixed in 3.10.0 of xterm last December in xtermjs/xterm.js#265
Hyper is on 3.12.0 as of #3536.
But the problem still exists for me in Hyper 2.1.2. Maybe not in stable yet? How can I find that out?


Type hints

Implement support for type hints in command functions. minicli will try to cast the string provided as an argument to the provided type.

cool


Make examples setup normally as part-way travis fix.

Update the examples with special flags to override the slow steps and ensure the yaml files are at least up to date.
Progress towards #60

Not sure what to do here, the energy evaluations which must be done for initial energy, even with no minimization and no iterations, still times out the travis tests. Not sure how to fix it. I could force reduce the number of states, but not sure that would exactly fix it.


[Feature] Chatbot for Signup form

Is your feature request related to a problem? Please describe.
A chatbot in place of Sign up forms are more interactive. Providing clients the way to register in interactive manner rather than with forms
Describe the solution you'd like
API and storage at backend. We can use a table storing which forms are required by client.
Describe alternatives you've considered
Api from the Google form or any other agent
Additional context

Hello, I would like to suggest to use GraphQL and SQLALchemy for API and storage at the backend.  GraphQL is better than REST and has many other advantages.  We can use the Graphene-Python library with supports building of GraphQL and storage with the use of SQLAlchemy.
Would like to know your feedback on this.

@Mishrasubha Yes looks fine, you can start working on a small design like only username and email address and show how chatbot can covert a form to interactive manner.

Okay then I will start working on it


Update quarto and remove esm import

After doing #81 I realized that this report likely would need the same treatment.
FYI @assignUser and @raulcd

Thanks!


bitmap and gradients support

The pipeline supports uniform colors. I'd like to work on expanding that to accept bitmaps, and later on gradients. If you have any thoughts on the design, let me know. If not, I'll come up with something to start the discussion.

As it turns out, I have been thinking about this quite a bit, and did some explorations over the weekend. I'll write up my detailed thoughts later today.

As promised, here are my thoughts on adding images to the piet-gpu pipeline.
A few general thoughts, then I'll get into specifics. One characteristic of a retained-mode pipeline like piet-gpu is that all resources have to be resident at the time rendering starts. This is in some contrast to using rasterization to draw images; you can load an image, do the draw call, then the image no longer has to be resident after that. The images can only be freed after the pipeline completes (ie after the fence for the command buffer is signaled). This will require some lifetime tracking on CPU-side objects that hold handles to GPU-side texture resources.
Also, because piet-gpu is using the equivalent of an ubershader, the descriptor set provided to the fine rasterizer has to be able to access all images. There are two fundamental approaches to this. One is to use an array of textures, and build the descriptor set provided to the fine rasterizer with this array. There's a good blog on that technique. The other is to use atlasing techniques, so there is a smaller (likely bounded) number of textures, the images are copied into subregions of those textures, then the description of an image consists of a uv rectangle within one of those textures.
There are problems with each. Texture arrays are a relatively newer feature, and, while supported pretty well on Vulkan (and DX12 and recent iterations of Metal), support on older APIs is lacking. Even on Vulkan, the runtime bound on the maximum number of textures supported in an array may not be adequate for the scene being rendered, especially on older Intel GPUs and Android, and in fact the feature (VK_EXT_descriptor_indexing) is not absolutely required; support seems especially poor on Android. There may be a performance cost to large arrays, but this is less clear. Again, there's a pretty good blog that goes into more detail on descriptor indexing.
Atlasing has its own problems. There's obviously more copying, but additional concerns on top of that. The shader has to do its own logic to deal with the image bounds, making sure that reads beyond the bounds don't sample other images in the atlas (this is particularly challenging with filtered sampling, and mipmapping may not be practical). As mentioned above, all images need to be stored in these atlases, so the size of the atlas image may grow. And of course there's the complexity of allocating space in the atlas, as well as possibly additional synchronization concerns, as I think in general it's not ok to write into the atlas while it's being read, even if the regions are disjoint. Note: in Rust, a good approach to (dynamic) atlas allocation is guillotiere.
Even so, for the pipeline I'm concerned about not just images, but two other image-like resources. Gradients are mentioned above, and there are also cached glyphs, especially those rendered by the platform to match the appearance of native UI text. It's possible but not efficient to do one (small, 1D) image per gradient, but for text atlasing is almost required.
My inclination is to use arrays of textures for images, and potentially add an atlased path later for compatibility. I think ultimately it's simpler, and probably will be higher performance.
Here's my take on the impact on the pipeline stages:
Encoding
The encoding task really breaks down into two pieces: resource staging, and the encoding of an image element.
Resource staging
Getting a CPU-side image into a VkImage is a multistage process. I think the best way to do it is this:

Allocate a buffer (same as now) with host-compatible memory type
Copy image data into buffer (same as now)
Allocate an image (same as now) in device memory
Encode a command buffer that copies the buffer to the image, then does an image pipeline barrier
Submit the command

When the command completes (the fence is signaled), the buffer can then be deallocated. I was originally pretty concerned about synchronization between the image being uploaded and it being available for rendering, but I believe as long as the fine rasterizer is in the same queue as the copy (and there's an appropriate pipeline barrier), things should be ok.
Ultimately, we should probably allow image uploading from multiple threads. This will require some work but nothing terribly tricky.
Also, if lots of images are being uploaded, it is no doubt a useful optimization to batch the copy commands, particular the image transitions.
Obviously, staging with an atlas is more involved, as stated above.
Encoding an image element
The main trick of encoding an image element is figuring out how to reference the VkImage. For now, I'm not worrying about how to make those references stable across render calls, but can basically make the assumption that the scene is being encoded anew each time. In that case, I think the best approach is to count from 0, and add the image to a list of images kept in the render context. Then when it comes time to dispach the compute kernel for the fine rasterizer, build the array of images for the descriptor set from that list.
An optimization would be to recognize when the array is the same as the previous frame (likely common in UI contexts), and retain the previous descriptor set in that case.
The atlasing case is not hugely different, except for adding a uv subregion.
Middle pipeline
The middle part of the pipeline is unaffected, as for those purposes the image is an opaque object. In particular, none of the middle stages need access to image data, just the geometry (which should be present in the encoded element).
Fine rasterization
The fine rasterizer is where the image data is accessed. This should actually be pretty easy, it's little more than a texture call in the shader.
The atlasing case would definitely be more complex, as the uv coordinates would have to be compared against the.
Quality
Bilinear filtering is good enough for now, but a point for the future is that better quality is definitely possible, and desirable. Skia does bicubic, and I think it's worth chasing that. But almost all of the work for that is in the shader; all the setup and resource management should stay the same.

As mentioned in the FillImage change, I now believe images should be rendered outside piet-gpu, so they can be copied pixel-by-pixel in kernel4. In other words, I consider this issue fixed, but I'll leave it open for you to decide.

We now have gradients working, and bitmap is tracked in #176. Closing as discussed on zulup


Uncaught SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

index.js using let outside strict mode

Which version of node are you using? I'm not using babel for the project so you need node v6+ (this is in the readme)

im was in outdated node, problem solved


Possible multithread unsafe?

Which service(blob, file, queue) does this issue concern?
`from azure.storage.blob import BlockBlobService
blob_service = BlockBlobService(account_name=conf['name'], account_key=conf['key'])
`
What problem was encountered?
We are using threadpool to do async uploading to storage. We are creating single BlockBlobService and share it across our threads pool. Is it possible that BlockBlobService is not a thread safe because it creates requests.Session()  at StorageClient
EDIT
Is it possible that its threadsafe because we are working against the same storage account?
Thanks!

Hi @oak-tree, thanks for reaching out!
To clarify, we make no promise in terms of thread safety, since we could manipulate the session object (like here). Please consider creating a BlockBlobService for each thread.


Overall code quality improved, renamings applied and text animation a…

…dded for built-in text

Class names changed
Folder structures refactored
Duplicate codes removed
Text animation support added for built-int text

PS. These changes made for Runtime

I know this was already merged, but isn't Sequencer way too generic of a name? Maybe something like AnimationSequencer would be better.


feat(use-mutative): upgrade mutative version to 0.4.2

replaceResult = { . .result }; It looks like state must be a plain object.

const nextState = create(reducer)(state)  may be clearer.

replaceResult = { . .result }; It looks like state must be a plain object.

oh! that just example

const nextState = create(reducer)(state)  may be clearer.

sorry for not found that comment,
not sure what is that mean, still not released, we can update later.


merge from konsum-frontend-svelte

.github/dependabot.yml

chore: (updates)
chore: (updates)

.github/workflows/auto_approve.yml

chore: ()

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

v1.29.13
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add_child seems very slow under pure java implementation

Hi,
I'm running the following script
require 'nokogiri'
require 'benchmark'

puts Nokogiri::VERSION

doc = Nokogiri::XML::Document.new
root = Nokogiri::XML::Node.new('root', doc)

Benchmark.bm { |x|
  x.report {
    10000.times do |i|
      root << Nokogiri::XML::Node.new('randomNode', doc)
    end
  }
}

Running under 1.9.3-p125 returns the following
1.5.2
       user     system      total        real
   0.030000   0.000000   0.030000 (  0.027721)

... while running on JRuby (1.6.7, 1.7.0.preview1 and head) return uniformly
1.5.2
       user     system      total        real
  21.880000   0.100000  21.980000 ( 21.259000)

When running JRuby's profiler, it turns out that 95% of these twenty-something seconds is spent in the add_child method.
This might be an unfortunate but natural side-effect of using the Xerces library, but I haven't found any explicit documentation about this.

@yokolet @jvshahid This still appears to be a poorly performing method.
# ruby 2.3.0
<IP_ADDRESS>
       user     system      total        real
   0.020000   0.000000   0.020000 (  0.020321)

# jruby <IP_ADDRESS>
<IP_ADDRESS>
       user     system      total        real
  84.110000   0.090000  84.200000 ( 83.353718)

Any thoughts?

I'm not familiar with this issue, but i have the benchmark on my dev machine and will investigate it.

Verified that the call to relink_namepsace is taking long time. I also attached an image of a profiling session. Removing out the relink_namespace call (as pointed out previously) improves the  performance dramatically as shown below:
       user     system      total        real
   0.230000   0.000000   0.230000 (  0.190405)

I finally got time to figure out what's going on. It seems like the JRuby implementation had a bug that caused it to run in O(n2). The relink_namespace method was called on the root node every time a new node is added as a child of root. I modified the code locally and it seems to have fixed the slowness issue. I will take the opportunity to clean up the relink_namespace code and document it. i also need to figure out a way to test this behavior in order to prevent regressions.


Remove weak cipher: TLS_DH_RSA_WITH_AES_128_GCM_SHA256

Describe the bug
Remove cipher TLS_DH_RSA_WITH_AES_128_GCM_SHA256 it has been flagged as weak.  The cipher is not listed in the configuration files by default for new installs but may be present on upgrades and it is still present in some of the code as a default.

Nate,
There are still some references pending.

Fixed the bug through #1244


Create a Java counterpart for the Scala API

It turned out that Rheem's Scala API is much easier to handle, less error-prone, more efficient, easier to read (a.s.o) and at the same time as powerful as the graph-based base API. With Scala not being popular with everybody, we should offer the same capabilities in Java. At a first glance, one might argue that one could simply call the Scala API from Java applications as well. However, this is not true because of (i) Scala-specific datatypes, (ii) optional parameters, and (iii) implicit parameters, including ClassTags. In consequence, a dedicated Java API is needed.
The following ideas might help to accomplish that goal:

The Java API could be a wrapper around the Scala API.
The lack of optional parameters could be compensated by subsequent method calls, e.g., instead of lines.map(_.toLowerCase, udfCpuLoad = ...) in the Scala API, we might want to have lines.map(String::toLowerCase).withUdfCpuLoad(...). Since Operators are mostly immutable, this entails a lazy creation of those, i.e., only after we know that no such chained calls will appear any more.
Not all situations require us to know the exact datatype being handled by the execution platforms. This important due to Java's type erasure. Therefore, we could do a best effort to infer the datatype, e.g. from UDFs or from Operator connections, and allow them to be added optionally, e.g., with .withInputType(...). If we do not have a datatype, then we use a surrogate one, e.g. DataSetType.unknown().

This issue was moved to rheem-ecosystem/rheem#19


extended functionality of add_object_track_from_list to handle 2D and…

… 3D points and boxes
closes #175

@PDuckworth test when you can plz. It is as simple as.
world = World_Trace()
o1 = [(numbers), (numbers), (numbers), ...]
world.add_object_track_from_list(o1, "o1")

I've checked some simple cases. It seems to work fine.
I will use this function instead of strands_data_to_qsrlib, so I can test it with real data then.
    #3D points
    o1 = [(1,1,1), (2,2,2), (1,1,1), (2,2,2), (2,2,2), (3,3,3)]
    o2 = [(1,1,1), (2,2,2), (3,4,3), (3,4,3), (3,3,3), (3,3,3)]

    #2D BB
    o1 = [(1,1,5,5), (2,2,5,5), (1,1,5,5), (2,2,5,5), (2,2,5,5), (3,3,5,5)]
    o2 = [(1,1,2,2), (2,2,2,2), (3,4,2,2), (3,4,2,2), (3,3,2,2), (3,3,2,2)]

Paul

OK thanks. Let me know when you are happy for me to merge. TBH there is no reason to fail if the above tests work.
PS: you can also offset the timestamps by using the argument t0 ;)

I wasn't planning on testing it on real data for a while, so I'm happy for it to be merged. It doesn't look like you broke anything :)


glib-macros: Don't produce unnecessary braces in `clone!(async move {…

… x })`
This would wrongly suggest to remove the braces, which is invalid syntax, because the macro already adds another layer of braces around the body of the async block.
To avoid this, don't output the braces of the async block in the macro expansion and instead only use the braces added by the macro.

This also affects the old macro but I can't be bothered to fix it there


Feature/minimal account center

Description

Checklist

[x] The version field in package.json is incremented following semantic versioning
[x] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[ ] This PR passes the Circle CI checks

How would a dev configure which component they would like to use for the minimized state of account center?
And how would they configure different ones for desktop and mobile?

is there a way to test this on the demo?

Added some requested changes from looking at the code.
Also I can't see in the diff changes to the Onboard initialization code that allow for accountCenter mobile configuration and the extra field in the desktop configuration and the associated validation?

The width of the open account center component is different depending on which minimized component you use. This should not be the case.

I'm seeing the Micro.svelte component rendering with a size of 84 x 56 px. This designs specify 80 x 56 px.
I'm also still seeing Mimimized.svelte and Maximized.svelte components rendering with different widths. This should not be the case. They should have the same width.

The current validation doesnt allow for setting minimal
const initOptions = Joi.object({
    wallets: walletInit,
    chains: chains.required(),
    appMetadata: appMetadata,
    i18n: Joi.object().unknown(),
    accountCenter: Joi.object({
        desktop: Joi.object({
            enabled: Joi.boolean(),
            position: accountCenterPosition
        }),
        mobile: Joi.object({
            enabled: Joi.boolean(),
            position: accountCenterPosition
        })
    })
});

The current validation doesn't allow for setting minimal

Hi @funiimunii,
We do have the current validation for minimal. You can look at the changes tab. We've also had it merged in the main branch:
const initOptions = Joi.object({
  wallets: walletInit,
  chains: chains.required(),
  appMetadata: appMetadata,
  i18n: Joi.object().unknown(),
  accountCenter: Joi.object({
    desktop: Joi.object({
      enabled: Joi.boolean(),
      minimal: Joi.boolean(),
      position: accountCenterPosition
    }),
    mobile: Joi.object({
      enabled: Joi.boolean(),
      minimal: Joi.boolean(),
      position: accountCenterPosition,
    })
  })
})

aghh okay. we are using @web3-onboard/react npm package 2.1.6. Will upgrade to 2.1.7 and hopefully these made the cut?


How to properly config pusher notifications web with Vercel hosted PWA application?

Hello. I am recently creating a PWA application to send notifications with pusher. For some reason in the localhost the notifications works, but when I deployed to vercel and teste on browser and PWA installed version, none of them works. I searched a lot and could not find a proper tutorial or some docs that could help me.
The error is this from the image below:

As it says could not find the function, because of this, I think the script from pusher is not been loaded. This is my next config:

Also, what is the minimum code for my service worker?

You can find instructions on the service worker at https://pusher.com/docs/beams/getting-started/web/sdk-integration/#create-a-service-worker.
The error message looks like the code has been minified, which makes following the stack trace impossible. Are you able to run a build without this and share the error?
What device/browser are you using for this test?

You can find instructions on the service worker at https://pusher.com/docs/beams/getting-started/web/sdk-integration/#create-a-service-worker.
The error message looks like the code has been minified, which makes following the stack trace impossible. Are you able to run a build without this and share the error?
What device/browser are you using for this test?

Hello, sorry for the late reply, I was testing some stuff and probably my service worker was wrong, but even now that I think I made everthing fine, it still doesn't work :/
About the error, yes, probably is because minification. I never made a pwa app so I just followed the instructions using https://www.npmjs.com/package/next-pwa, but essentially I made a folder worker with index,js and inside importScripts('https://js.pusher.com/beams/service-worker.js') just like https://github.com/shadowwalker/next-pwa/tree/master/examples/web-push but using the worker for pusher.
Now, my nextjs.config is this:

And the when running build, it creates three files sw,js and the two workbox.

So the pusher script is called sw.js insted service-worker.js as your doc link says... Could be it the issue I am having?

I found that next-pwa does not support app router from Next 13. And because of this, the service worker is acting weird. I am gonna close this issue because it is not related to Pusher


UnrecognizedPropertyException in ScheduledEvent

I have a working application using Spring Cloud 2020.0.6 that runs in AWS Lambda.
But when I upgraded spring cloud to 2021.0.3 its not starting because of this error:
Cannot convert event stream: java.lang.IllegalStateException
java.lang.IllegalStateException: Cannot convert event stream
    at org.springframework.cloud.function.adapter.aws.SpringBootStreamHandler.convertStream(SpringBootStreamHandler.java:87)
    at org.springframework.cloud.function.adapter.aws.SpringBootStreamHandler.handleRequest(SpringBootStreamHandler.java:54)
Caused by: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "version" (class com.amazonaws.services.lambda.runtime.events.ScheduledEvent), not marked as ignorable (8 known properties: "detail", "region", "resources", "detailType", "account", "source", "time", "id"])
 at [Source: (ByteArrayInputStream); line: 1, column: 13] (through reference chain: com.amazonaws.services.lambda.runtime.events.ScheduledEvent["version"])
    at com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)
    at com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:1127)
    at com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:2023)
    at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperty(BeanDeserializerBase.java:1700)
    at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownVanilla(BeanDeserializerBase.java:1678)
    at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:319)
    at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:176)
    at com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:323)
    at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4674)
    at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3666)
    at org.springframework.cloud.function.adapter.aws.SpringBootStreamHandler.convertStream(SpringBootStreamHandler.java:83)
    ... 1 more

My pom.xml is attached:
pom.txt

The SpringBoot*Handlers were long deprecated in favor of FunctionInvoker. Basically there is no longer a need to implement anything other than Java Function. Please look at this Getting Started guide - https://docs.spring.io/spring-cloud-function/docs/current/reference/html/aws.html#_getting_started

For the record, that how I solved this issue:

Changed dependency to spring cloud 2021.0.3
Deleted my class that extended org.springframework.cloud.function.adapter.aws.SpringBootStreamHandler
Changed the handler to "org.springframework.cloud.function.adapter.aws.FunctionInvoker::handleRequest" (in serverless.yml)
Removed FUNCTION_NAME environment variable (in serverless.yml)


Reading the chipid gives nonzero "random" number.

When starting st-util on my F4 discovery board, I got:
WARN src/stlink-common.c: unknown chip id! 0xe0042000
Chip ID is 00000000, Core ID is  00000000.
which I know spells trouble. But when I see some non-zero numbers for the "chip id" I think I have a connection to the target. Turns out that is not the case: When I switched back to my target I got the same 0xe0042000 chip id, even when the target was not powered.
My STM32F407 on my discovery board might be fried, I don't know yet. I'll just use the F4DISCOVERY as my STLINK for now.
It'd be nice if the "detection" of "no chip connected" was a bit better. Apparently "chip id = 0xe0042000, ... core id = 0" means "no chip"....

I'm closing this old issue. As it should now be tested against master. Please reopen a new issue when similar problem exists.

Can someone verify that this has been fixed?

The weirdness still exist.It seems I was still "new" to stm32 when I reported this. It is now firmly implanted in my brain that the 0xe004200 means "no chip".
assurancetourix:~/stm32/stlink.git> ./st-util -m
2020-02-26T18:36:19 INFO src/common.c: Loading device parameters....
2020-02-26T18:36:19 WARN src/common.c: unknown chip id! 0xe0042000
assurancetourix:~/stm32/stlink.git>

@rewolff: Feedback like yours gives me the impression and feeling that it is really worth it to review all closed issues of this project for leftovers no matter when they occurred. I am really sorry that you had to deal with this problem for such a long time - very unsatisfiable indeed. Trying to push the priority up for this.

@rewolff: Your proposal seems very reasonable to me. If you fancy, you may submit a PR for this which is linked to this issue.

BTW: I assume there may be more of these "hidden" error codes that could see some "decription" as well.

Working on it....
FYI, I had trouble getting an STM recognized. Probably an older version of stlink. Getting latest now.
assurancetourix:~> st-util -m
2020-03-21T15:05:04 INFO src/stlink-common.c: Loading device parameters....
2020-03-21T15:05:04 WARN src/stlink-common.c: unknown chip id! 0xe0042000
assurancetourix:~> st-util -m
2020-03-21T15:05:39 INFO src/stlink-common.c: Loading device parameters....
2020-03-21T15:05:39 WARN src/stlink-common.c: unknown chip id! 0

Yes, please use v1.6.0 or even develop which itself is despite of the name also fairly stable.

Note: PRs will go into develop anyway. Please consider this when opening such in the future.

Sorry, didn't see your remark about using develop until after I finished the PR. Can you cope or do I need to redo it?

No that's ok, I can fix this as well. I know this is a bit annoying to contributors. :-/ I've already consulted texane to switch the base branch to develop what would take this additional consideration away from users. If I could, I would have done that already.

The weirdness still exist.It seems I was still "new" to stm32 when I reported this. It is now firmly implanted in my brain that the 0xe004200 means "no chip".
assurancetourix:~/stm32/stlink.git> ./st-util -m
2020-02-26T18:36:19 INFO src/common.c: Loading device parameters....
2020-02-26T18:36:19 WARN src/common.c: unknown chip id! 0xe0042000
assurancetourix:~/stm32/stlink.git>

Just FYI:
The desired situation would be that the "read chip ID" function can return -1 as "error", and that instead of printing "unknown chip id 0xfffffff" the message would read something like: Error: No chip found.

@rewolff: We should have a new ticket for this as it did not make it into PR 886.

My testing shows that it does sensible things now. That's why I didn't do anything for this.
OK... Mine now says:
2020-03-22T12:05:32 WARN common.c: Invalid flash type, please check device declaration
and doesn't consider that fatal. I can dive in and make this message "fatal", but I don't know if it maybe makes sense to have the debugger connected without knowing "flash type"? Maybe debugging works, but flashing new firmware not?


Performance on GOK-10k

Hello, first of all thank you for the good work.
I have one question: Is the performance of the ARTrack_L384 model on the got10k dataset the performance learned on the full dataset? (AO : 78.5%)

No, the GOT-10k performance we provide that only trained on GOT-10k full train sets. You can see the leaderboard of GOT-10k, we trained full datasets including LaSOT, TrackingNet, COCO2017, and GOT-10k_vottrain provide higher performance (AO: 79.6%).
I can provide other full datasets performance, ARTrack_256 about 75.5% on AO, ARTrack_384 about 77.2% on AO.

Thank you for answer. So, where is the yaml file when training a large model with only got10k dataset?

You can follow the large model yaml and set the training epoch same as base_256_got, and batch_size same as large mode's yaml. Others hyper-parameter is same as large model.

Thank you very much!


New release for Log4j fix against CVE-2021-45046 required

New exploits against the log4j JNDI vulnerabilities are found, even in Log4j v2.15.0. The new fixes in v2.16.0 are already merged, but a new release should be prepared.
More information: https://github.com/advisories/GHSA-jfh8-c2jp-5v3q

Releases v.1.0.3 with log4j 2.17.0


Update CLI Bootstrapping script to use gray instead of white for placeholder/initial values

Hi @spcbfr, thank you for the PR. The initial value should be gray by default, do you see it different?

Hey @dan5py so this turns out to be an issue with my vscode terminal colorscheme and it looks fine on alacritty, I am not sure why I immediately assumed this was an issue with shadcn/ui. I'll close the issue now!
and thanks for the quick response!


Show on the tab answers the events on the test

Implement on the tab answers the events on the tests with events triggered.

@jvJUCA  Can you specify more about this in detail? So that I can take this token.


Cuckoofilter storage to disk and loading (WIP)

This is a work in progress:

[x] store cuckoo filter buckets and fingerprints to disk
[x] load cuckoo filter state from disk
[x] cleanup

+1

Overall I don't think any of my objections should prevent this from being merged, so +1
I'll create some issues as you suggested.


Allow custom input resolution.

Hi, thank you for this wonderful repository :-)
Here is my bit which allows inference with custom input resolution (e.g. 720x1280).
BTW I have also fixed score threshold in the same way as in this pull request.
I have not tested training yet but hopefully it would work.

Hello @MartinBrazdil! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file demo.py:

Line 41:80: E501 line too long (97 > 79 characters)
Line 47:80: E501 line too long (90 > 79 characters)

In the file models/bifpn.py:

Line 192:80: E501 line too long (107 > 79 characters)


add annotation csv file

add annotation csv file

I have included a csv file;
I have updated readme file


Errors keep toggling during liveshare and cant unfollow participant

Issue Type: Bug
3 people on a rust project, cant unfollow participant and the problems keep toggling in the editor
Extension version: 1.0.3784
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19042
Remote OS version: Linux x64 4.19.0-9-amd64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (4 x 2394)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.92GB (3.15GB free)

Process Argv
--crash-reporter-id 5f32c89b-c7b8-41bc-86d2-044755b4c757

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: hfcs.csclub.uwaterloo.ca

OS
Linux x64 4.19.0-9-amd64

CPUs
AMD Opteron(TM) Processor 6272 (64 x 1505)

Memory (System)
157.40GB (15.75GB free)

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt617cf:30253240
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvsdeb440:30248342
pythonvsded773:30248341
vstes627:30244334
pythonvspyt600cf:30251589

Hey @null-sleep, thanks for reaching out to Live Share! Sorry about the problem you've been experiencing. Can you please describe the problems that are toggling in the editor? What notifications are you seeing? Also, if you could attach your logs by going to the Command Palette (ctrl+p), then executing the command "> Live Share: Export Logs", that would be helpful.

Closing due to inactivity and lack of actionable details. Please reopen if you're still having this problem.


Feature/nmea handling

This makes "NMEA" and unknown ChannelParser names survivable. A dummy NMEAParser class was added, which will eventually be replaced by something that extracts the NMEA 'sentences'.
Minor cleanup was also performed. The use of OrderedDict was made dependent on the version of Python; as dictionaries are ordered in all implementations of 3.7, only older versions will explicitly use OrderedDict. Standard dict have more readable repr() and perform slightly better.

Codecov Report

Merging #125 (7add3cb) into develop (7b0e0de) will decrease coverage by 0.02%.
The diff coverage is 70.83%.

@@             Coverage Diff             @@
##           develop     #125      +/-   ##
===========================================
- Coverage    74.17%   74.15%   -0.03%
===========================================
  Files           10       10
  Lines         3656     3676      +20
===========================================
+ Hits          2712     2726      +14
- Misses         944      950       +6

Impacted Files
Coverage Δ

idelib/parsers.py
80.89% <66.66%> (-0.64%)
:arrow_down:

idelib/attributes.py
68.08% <80.00%> (+2.17%)
:arrow_up:

idelib/transforms.py
68.62% <85.71%> (+0.14%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature request: Allow column exclude during project creation

There seems to be many ways to exclude rows but a quick way to include/exclude columns would be nice. Maybe a checkbox at the column header? The Custom Tabular Exporter looks nice :). Perhaps something like that for imports. Thanks.

Closing as duplicate of #612.


bugfix/CLS2-556-fix-v3-field-errors

Description of change
Hide archived from the v3 opensearch queries, but available in the v4 search. A future ticket is going to add archived as a filterable column, however as the v3 search endpoints use a fuzzy search with a MultiMatch query, having archived in the list of queryable columns causes a text to bool parsing issue
Checklist

[ ] Has this branch been rebased on top of the current main branch?

Explanation
The branch should not be stale or have conflicts at the time reviews are requested.

[ ] Is the CircleCI build passing?

General points

Other things to check

Make sure fixtures/test_data.yaml is maintained when updating models
Consider the admin site when making changes to models
Use select-/prefetch-related field lists in views and search apps, and update them when fields are added
Make sure the README is updated e.g. when adding new environment variables

See docs/CONTRIBUTING.md for more guidelines.

Do you know what the roadmap is for deprecating the V3 search end points in Data Hub? Would there be a potential (quick) fix in the MultiMatch end point instead? If we are going with the current exclusion method, is there a test that fails when a field is not added to the exclusion fields but that should have?

Do you know what the roadmap is for deprecating the V3 search end points in Data Hub? Would there be a potential (quick) fix in the MultiMatch end point instead? If we are going with the current exclusion method, is there a test that fails when a field is not added to the exclusion fields but that should have?

Not sure on the deprecation of the v3 endpoints, I can see quite a few usages of these endpoints still in the front end
The MultiMatch isn't an endpoint it's a type of opensearch query that lets you query across multiple indexes which is how the V3 endpoints look to work. In the V4 search each type has it's own searchable index. I can't see a way of changing the error thrown by MultiMatch, as it's a valid error. We are grouping together every searchable column, ignoring the column data type, so when the MultiMatch query runs it fails with parsing text into a boolean for the archived column
Yep, without the exclusions being added, all the tests in this file fail datahub/search/company/test/test_basic_search_views.py, plus tests in a few other files. This test is used by the v4 endpoint, and has the archived present datahub/search/test/test_query_builder.py::test_get_search_by_entities_query


Prepare November Identity Releases

Includes the first version of new azure-identity-broker package.

API change check
API changes are not detected in this pull request.


Multiple Application Insights with different connection strings using JavaScript(Web) SDK v3 giving warnings

I am trying to have multiple Application Insights(vesrion 3) with different connection strings using JavaScript(Web) SDK Loader Script on the same HTML page. I have also given different name in the configuration. But I am getting in this warning in console:
Two extensions have same priority

How can I fix this? or is there any different way to have multiple instances using loader script? In the docs, it is mentioned that we can use "name" if you need to initialize two different SDKs at the same time.

I am using the name property in the config and getting the issue as above. Loading 2 separate SDK configs using Script Loader separately with different name. I don't want to use npm package since I am not using any bundler.

Hmm, that is a little odd, its sounding like the multiple versions are "sharing" the same config object and therefore as each one is initialized it keeps "adding" to the existing values.
By default, when the SDK initializes (for version 3+) it uses the "provided" config as a template and effective clones the objects / arrays (to avoid this exact issue) as internally it "adds" objects that are being listed as duplicates... The only time it doesn't do this is if the config has already been converted into a dynamic config (it's already undergone the initialization process)...
This is the code that uses the name config, and the sdk loader doesn't use the createDynamicConfig() so this (shouldn't) be occurring... I'll need to have someone investigate this a little more, however, the person I would get to do this is currently on Leave, so it might be a while before they get to it....
If you have some time if you could do some initial debugging that would be helpful, the issue sounds like it would revolve around the handling / initializing of the SDK. One simple approach (assuming the issue is not in the SDK loader itself) is that if you change the "src" to https://js.monitor.azure.com/scripts/b/ai.3.gbl.js this will use download and use the unminified version of the SDK (although the minified one also includes the map file which is publically available) and trace into the AppInsightsCore initialize function this should be the line of code that "clones" the config while this is where we "add" the standard extensions to the provided config (which is calling the AppInsightsCore config)

Any update on this issue?

Hi @rubiks-cube, apologies for the delay - I've just returned from vacation and am taking a look at the issue now. Thank you for your patience!

Hello @rubiks-cube, thank you for bringing this issue to our attention. We were able to reproduce the problem and have identified that it is caused by a race condition. To address this, we will be releasing a new version of the snippet and SDK. Please note that this solution will not support IE and Opera Mini. However, you won't need to make any changes on your end. Thank you for your patience as we work to resolve this issue.

@siyuniu-ms  thanks for the update.

Hi, our cdn release (where our snippet live) will take around 5 days after our npm is released to make sure we didn't break anything.

any update on script loader v3.2.2? still it is fetching old version file.

@rubiks-cube  It would be released early next week. Thanks for waiting.

@rubiks-cube Both snippet package and AI 3.2.2 CDN is published which contains the newest changes.

@siyuniu-msI am still facing the above same issue with updated version. Also there is another error I see in console:

Hi, could you provide more error details? I just did a local test with two snippet inited at the same time wtih two different ikey and both track message is delivered successfully.

and below is my test code for reference

AISKU Sample

Microsoft Application Insights JavaScript SDK - AISKU

For some context, you will need both the new version "8" (see "sv": "8") of the SDK Loader AND version 3.2.2 of the SDK, if either version does not match (or greater) then the identifed race condition causing SDK A to use Loader B and Vica-versa configuration may still occur.
This is because v3.2.2 is now (optionally) using the data-tag to identify the "global" instance name (this also requires that you runtime supports the document.currentScript (as this is what it uses to get access to any passed attribute on the script tag). And only v8 onwards will add this new data attribute to the script tag.

The script loader mentioned in docs is different : Script Loader. Using the above snippet doesn't have this issue.

Yeah, not all of the documentation has been updated yet, it is included on the main readme https://github.com/microsoft/ApplicationInsights-JS/blob/main/tools/grunt-tasks/minifyNames.js and it is included in v1.2.0 of the web-snippet package https://www.npmjs.com/package/@microsoft/applicationinsights-web-snippet (which we published on friday)

Closing as released


python310Packages.us: 2.0.2 -> 3.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.us is: A package for easily working with US and state metadata
meta.homepage for python310Packages.us is: https://github.com/unitedstates/python-us/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1.1 with grep in /nix/store/hgbpk1xcp3z43sv0g61zf38s7vayg2hn-python3.10-us-3.1.1
found 3.1.1 in filename of file in /nix/store/hgbpk1xcp3z43sv0g61zf38s7vayg2hn-python3.10-us-3.1.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.us
python311Packages.us

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hgbpk1xcp3z43sv0g61zf38s7vayg2hn-python3.10-us-3.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.us https://github.com/r-ryantm/nixpkgs/archive/f5110873c8295d83fd24a88c999c5c5465768807.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hgbpk1xcp3z43sv0g61zf38s7vayg2hn-python3.10-us-3.1.1
ls -la /nix/store/hgbpk1xcp3z43sv0g61zf38s7vayg2hn-python3.10-us-3.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.us
python311Packages.us

Maintainer pings

Result of nixpkgs-review pr 252076 run on x86_64-linux 1

4 packages built:

python310Packages.us
python310Packages.us.dist
python311Packages.us
python311Packages.us.dist


Radio Button Select For a Multiphase Form

I am writing a simple internal application to determine investment risk. I love materialize and am hoping to use it as the front end framework for the forms I have displayed. Unfortunately, I cannot seem to get the radio buttons to render a select/allow any select at all of each option. I have the HTML elements broken down by name and am iterating over them in simple vanilla javascript.
I am using a multiphase form and am hoping to keep this as simple as possible for now. It's my first real javascript program, as well.
Check it out here and I would appreciate your input:
http://assetbookalex.azurewebsites.net/fire/
I noticed other articles on Stack Overflow suggesting that previous versions of Materialize required that you start the selects based on window load. Other folks stated this was fixed around March. My question is, will this work with a multiphase form as I have? If not, is there a work around available?
Excellent work on this project and I really look forward to seeing its progress.

Try to load the materialize.min.js after jQuery

What version of JQuery is recommended?

Radio buttons require their labels to have a for element to attach it to the input element because we hide the default browser ones. All you have to do to make your radio buttons work is add unique ids to each of them, then in the corresponding label you add a for attribute with that same id:
<input name="group1" type="radio" id="test2" />
<label for="test2">Yellow</label>

test2 would be the id and the value of the for attribute.

That worked, thank you!


Can't see the plugin 117HD

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 10
Bug description
i tried to delete/download runelite just to make sure it was up to date, even if i search 117HD, 117 HD or just HD i dont see it.. i tried to look if the plugin was merge with another.
Screenshots or videos

RuneLite version

Logs
No response

Hi, I am facing the same issue. I have also checked https://runelite.net/plugin-hub/ and it doesn't show 117 HD plugin there. Seems like the plugin has been removed?

The 117HD plugin was temporarily disabled due to causing various issues; it will be back soon.

https://twitter.com/OldSchoolRS/status/1648305099943313408
https://twitter.com/RuneLiteClient/status/1648309565061038081
https://github.com/runelite/plugin-hub/commit/ba4e92dc05c00ef58188ef2c685d503287ce14e3


Make all setup guides enumerated

This is worth doing sooner so we can do a thorough test.
The goal is to have anything which is a one-time setup step (or a repeated workflow step) enumerated.  Some of the ones that stand out are:

[x] Getting started manual installation: http://compare-lectures.quantecon.org/jl/getting_started.html#Installing-Julia-and-Dependencies-Manually (thought thigns were moved around)
[x] Version control setup: http://compare-lectures.quantecon.org/jl/version_control.html#Setup
[x] Go through the other ones in http://compare-lectures.quantecon.org/jl/version_control.html but I don't see other step-based workflows that jump out
[x] The new docker stuff in http://compare-lectures.quantecon.org/jl/tools_editors.html
[x] Probably the http://compare-lectures.quantecon.org/jl/testing.html#Julia-Setup steps
[x] Perhaps http://compare-lectures.quantecon.org/jl/testing.html#Collaborative-Work

But I would go through all of these to see what would be clearer as lists.  Some of them are already organized into sections, which may be more appropriate.

@jlperla Committed at XYZ. Let me know what you think. I general, I left things as sections (basically the version_control github setup) when they were essentially linear with no commentary. Otherwise, I used the numbers to distinguish actions from information.


[feature] font-awesome-4

Purpose
Closes #1204
Cause
Newer OSF pages are written to take advantage of the newest font awesome icon library v4.x. We have two competing libraries in use on the production page, this change eliminates the need for the older version.
Changes
A global search and manual replace was performed on the entirety of the OSF code base. Using the following migration guide provided by the library's author icon's were updated from the older font awesome v3 icon names to v4.
https://github.com/FortAwesome/Font-Awesome/wiki/Upgrading-from-3.2.1-to-4
Remove the old font awesome local folder servers: /static/vendor/font-awesome
Side effects
Double check icon's throughout the site to ensure they are loading properly.

Replaced by https://github.com/CenterForOpenScience/osf.io/pull/2144


fixes #97 calendar stays open while selecting dates

@patriciaho this issue  should be resolved with this PR https://github.com/adamalbrecht/ngQuickDate/pull/115

awesome, thanks!

@patriciaho If you can please close down this PR :)


you cant move cursor in inventory mode

forge 1.16.4 with optifine and no other mods, for some reason it doesn't work in inventory mode.

Same problem with Forge 1.16.3.

Same problem with Forge 1.16.3.

Try using version 0.9.1, it should be fixed now!

Try using version 0.9.1, it should be fixed now!


The objects within contextable are "shareable" between both front and backends?

Hi,
I am really starting to like the concepts used in contextable.
One thing I'd really like to make sure of. From my readings (thanks for the great docs) and if I understand everything correctly, validation that is defined on the server side can be/ is also used for the client side? In other words, certain validation rules only need to be defined once. Is this correct? If yes, can this kind of back.end/front-end sharing concept be extended to other business logic?
Scott

Yes. As long as your schema instanceMethods, classMethods and types have code that works on the server and in the browser, then you can use the same code for the server and the browser. Example... if your Schema is using e.g. mongodb package, then it won't work in browsers. Just make sure that everything your write works everywhere.

Right. That is logical that anything "mongo" won't work on the client.
So, I come back to composibility. I haven't dug at all into using contextable, so I apologize if my questions sounds naive, but I still think the context object should be composable and, for instance, be composable between front-end and back-end environments. That way, a front-end context can have many of the objects and methods that the back-end also uses, but only those that can be used on the front-end. In other words, standard validation and business logic "rules" would need some sort of flag to indicate the environment they can be used in. The context object would then be built accordingly. From your answer, I would imagine that this kind of composable context per environment isn't yet possible?
Scott

This package is unopinionated which means you are in charge for the structure and logic.

That is a good thing. I guess I'll have to make is opinionated. LOL!
Thanks again for your tips!
Scott


[SPEC] Change expected shape of end_token input for GatherTree

python_ci reported:
Result was SUCCESS
Could not update commit status of the Pull Request on GitHub.


Classes in testNg xml within  tag running depending on tests orders but not class orders

I have a TestNG file looks something like that:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >

<suite name="My Suite" verbose="2"  parallel="tests" thread-count="10">

    <test name="Some Workflow Tests" parallel="none">
        <classes>
            <class name="com.somepackage.test.MyTests1"/>
            <class name="com.somepackage.test.MyTests2"/>
        </classes>
    </test>

</suite>

In each test class I have test methods marked with Test annotation, starting with priority 1 and so on. When the tests were running, it turned out that TestNG executed all the tests with priority 1, then 2, etc and even didn't respect order of the classes within <classes></classes> tag. In my case, it looked like that : test with priority 1 from MyTests1 class -> test with priority 1 from MyTests2 class -> test with priority 2 from MyTests1 class -> test with priority 2 from MyTests2 class, etc. Should it be all the tests from MyTests1 class, only then tests from MyTests2, shouldn't it? It seems something new that probably was introduced during fixing the issue #1156.

Do you have any other dependency?
Even if it should be trueby defualt, did you try the preserve-order="true" attribute?
Even if it should not impact anything, could try the group-by-instances="true" attribute too?

No, I don't. Given TestNG file is very simple example where the issue can be easily reproduced. Test classes contain only two methods each without any dependency.
I tried setting preserve-order="true" and group-by-instances="true", but it wouldn't help me.

@slipwalker I've just tried your suite file on the master branch and it is working as expected without any modification.
Could you try with TestNG 6.10 and 6.10.1-SNAPSHOT (from https://oss.sonatype.org/content/repositories/snapshots/)?
If it is still failing, could you share a full project?

@juherr So, my test classes are very straightforward to eliminate possible impact of any dependency:
MyTests1 class:
import org.testng.annotations.Test;

public class MyTests1 {

    @Test(priority = 1)
    public void test1() {
        System.out.println("test1 from " + getClass().getSimpleName() + " class");
    }

    @Test(priority = 2)
    public void test2() {
        System.out.println("test2 from " + getClass().getSimpleName() + " class");
    }
}

MyTests2 class:
import org.testng.annotations.Test;

public class MyTests2 {

    @Test(priority = 1)
    public void test3() {
        System.out.println("test3 from " + getClass().getSimpleName() + " class");
    }

    @Test(priority = 2)
    public void test4() {
        System.out.println("test4 from " + getClass().getSimpleName() + " class");
    }
}

I've got following output from different TestNG version:
6.10.1-SNAPSHOT version. Wrong tests order:
...
... TestNG 6.10.1-SNAPSHOT by Cédric Beust<EMAIL_ADDRESS>...
test1 from MyTests1 class
test3 from MyTests2 class
test2 from MyTests1 class
test4 from MyTests2 class

===============================================
My Suite
Total tests run: 4, Failures: 0, Skips: 0
===============================================

6.10 version. Wrong tests order:
... TestNG 6.10 by Cédric Beust<EMAIL_ADDRESS>...

[TestNG] Running:
[ThreadUtil] Starting executor timeOut:2147483647ms workers:1 threadPoolSize:10
test1 from MyTests1 class
test3 from MyTests2 class
test2 from MyTests1 class
test4 from MyTests2 class

===============================================
My Suite
Total tests run: 4, Failures: 0, Skips: 0
===============================================

6.9.8 version. Need to a bit change xml file - instead of  parallel="none" use  parallel="false". Got correct tests order:
...
... TestNG 6.9.8 by Cédric Beust<EMAIL_ADDRESS>...

[TestNG] Running:
[ThreadUtil] Starting executor timeOut:2147483647ms workers:1 threadPoolSize:10
test1 from MyTests1 class
test2 from MyTests1 class
test3 from MyTests2 class
test4 from MyTests2 class

===============================================
My Suite
Total tests run: 4, Failures: 0, Skips: 0
===============================================

Ok, I didn't catch the priority part at the first read. I will try on my side asap. Thanks for the sample!

Well, in fact, the order you are showing is the new expected one.
Now, there is a different priority on ordering features. In your case, priority is more important than preserve-order then priority is respected first.
As I know, priority is not scoped in a class and that's why TestNG uses it in the global context (@cbeust Could you confirm?).

BTW, the fix is pretty easy: use dependsOnMethods feature.
I really recommend using dependsOnMethods instead of priority when possible.

It is not very convenient solution for me (and for other folks I suppose too). In case priority your tests can continue running when some tests before failed. But in case dependsOnMethods your tests will be skipped if dependent from test failed (what if I would like to have them run?). Also, that puts a restriction on each test method to have dependsOnMethods when I wanna keep some test orders, but there could be many tests methods and it's boring stuff to add it on each one.

I agree that changes are always a pain but it is much more easy to explain test orders now:

Hierarchy on order features (from less important to more important): groupByInstance, preserveOrder, priority, dependsOnGroups, dependsOnMethods
https://github.com/cbeust/testng/blob/master/CHANGES.txt#L38

Again, you are right when you say that priority and dependsOnMethods don't have the same exact behavior but they are currently working as expected (I hope so!).
We can't swap preserveOrder and priority importance because it will break priority (preserveOrder is true by default).
In your specific case, a "priority on class" is missing.
@cbeust WDYT?

@juherr is right, @Priority is global. As you point out, dependsOnMethods and dependsOnGroups should be the preferred way to order things within a class.


Add 14

I was doing some math at home and came across 14 as the next positive integer after 13.
Testing

checked it with my home calculator (TI-30XIIB)
checked https://oeis.org/A000027 and it didn't disagree

@michaelgruenewald This is a fantastic implementation, however I cannot merge it in it's current state as another contributor submitted a similar PR before this which was just merged. I therefore must close this, with regret. I would gladly reconsider if you wish to make changes and reopen it.


Draw repeat patterns or images with canvas with dart.ui

Please add support for repeating a pattern in a shape, similar to pattern fill support for the HTML canvas.
https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/createPattern
What I would like to do is draw a small pattern using the existing lines, rects, circles, and other shapes. I would then like to use this pattern as the fill for drawing other elements on the canvas, instead of just a color.
i.e., currently I can draw a rectangle with a solid fill color like so:
  void drawRect(Rectangle<num> bounds, Color fill) {
    final paint = new Paint();
    paint.color = new Color.fromARGB(fill.a, fill.r, fill.g, fill.b);
    paint.style = PaintingStyle.fill;

    canvas.drawRect(bounds, paint);
  }

Instead, I would like to have something like a PantingStyle.repeat, where I can set another canvas element (or similar construct) as the source for the pattern to repeat.

You can convert a Picture to an Image with toImage and then paint the Image multiple times with paintImage's repeat feature.

I was able to achieve the effect by using PictureRecorder to save the result of drawing on a secondary canvas to a Picture, converting it to an image, and then using paintImage to tile it. Thanks!
final pictureRecorder = new PictureRecorder();
Canvas patternCanvas = new Canvas(pictureRecorder);

// Code to draw the fill pattern on secondary canvas goes here.

Picture p = pictureRecorder.endRecording();
final forwardHatchPattern = p.toImage(12, 12);

// Draw the base shape on the main canvas that will be filled up
canvas.drawRect(boundsRect, paint);

// Now actually draw the fill pattern on top of the base rectangle.
paintImage(canvas: canvas, rect: boundsRect, image: forwardHatchPattern, repeat: ImageRepeat.repeat);

Unfortunately, it seems that the rasterization that occurs when PictureRecorder saves the temp canvas as a picture is causing some scaling problems when I go to actually fill in the main canvas. This is an example of what happens from a simple pattern. The middle bars in the chart are using a pattern fill.

Following are the relevant pieces of code.
Note that "linePainter" is a class that simply draws lines on a chart from a list of points. Without using paintImage(), it generally draws smooth lines no matter the angle on a Canvas. I am using it here on the helper pattern canvas to draw the blue line segments on the patterned bars.
I've tried scaling up the size of my pattern to generate a larger image, in the hopes that I could paint it and scale it back down (possibly based on screen density). However, I do not see any parameters to paintImage that might let me scale the image.
        // Paint in the pattern with the fill color.
        ui.Image forwardHatchPattern = _createForwardHatchPattern(stroke: fill);
        paintImage(canvas: canvas, rect: _getRect(bounds), fit: BoxFit.none,
            image: forwardHatchPattern, repeat: ImageRepeat.repeat);

    ui.Image _createForwardHatchPattern({
    common.Color stroke = common.Color.white,
    double strokeWidthPx = 4.0,
  }) {
    final pictureRecorder = new ui.PictureRecorder();
    final patternCanvas = new Canvas(pictureRecorder);

    final x0 = 12;
    final x1 = -1;
    final y0 = -1;
    final y1 = 12;
    final offset = 8;

    // Draw a line segment in the middle of the pattern.
    _linePainter.draw(
        canvas: patternCanvas,
        paint: _paint,
        points: [
          new Point(x0, y0),
          new Point(x1, y1)
        ];

    // Draw a line segment in the top left corner of the pattern.
    _linePainter.draw(
        canvas: patternCanvas,
        paint: _paint,
        points: [
          new Point(x0 - offset, y0),
          new Point(x1 - offset, y1)
        ]);

    // Draw a line segment in the bottom right corner of the pattern.
    _linePainter.draw(
        canvas: patternCanvas,
        paint: _paint,
        points: [
          new Point(x0 + offset, y0),
          new Point(x1 + offset, y1)
        ]);

    // Save the canvas as a [ui.Image] so that we can paint it.
    final p = pictureRecorder.endRecording();
    return p.toImage(8, 8);
  }

Is there some way to get smooth lines using Picture.toImage here, or do I have to fall back on manually calculating where to draw every single line segment in my bars?
If not, then my request to use another canvas as a pattern fill, instead of a rasterized image, would remain open.

cc @chinmaygarde

Can you use drawPicture instead of drawImage, and avoid the call to toImage?

Here an example of the draw Pattern, something I want to draw Image when I drag my finger in canvas.
Please give any idea how to do this.
How to use createPattern in flutter to draw repeated image.
function midPointBtw(p1, p2) {
  return {
    x: p1.x + (p2.x - p1.x) / 2,
    y: p1.y + (p2.y - p1.y) / 2
  };
}
function getPattern() {
  var patternCanvas = document.createElement('canvas'),
      dotWidth = 20,
      dotDistance = 5,
      patternCtx = patternCanvas.getContext('2d');

  patternCanvas.width = patternCanvas.height = dotWidth + dotDistance;

  patternCtx.fillStyle = 'red';
  patternCtx.beginPath();
  patternCtx.arc(dotWidth / 2, dotWidth / 2, dotWidth / 2, 0, Math.PI * 2, false);
  patternCtx.closePath();
  patternCtx.fill();
  return ctx.createPattern(patternCanvas, 'repeat');
}

var el = document.getElementById('c');
var ctx = el.getContext('2d');

ctx.lineWidth = 25;
ctx.lineJoin = ctx.lineCap = 'round';
ctx.strokeStyle = getPattern();

var isDrawing, points = [ ];

el.onmousedown = function(e) {
  isDrawing = true;
  points.push({ x: e.clientX, y: e.clientY });
};

el.onmousemove = function(e) {
  if (!isDrawing) return;

  points.push({ x: e.clientX, y: e.clientY });

  ctx.clearRect(0, 0, ctx.canvas.width, ctx.canvas.height);

  var p1 = points[0];
  var p2 = points[1];

  ctx.beginPath();
  ctx.moveTo(p1.x, p1.y);

  for (var i = 1, len = points.length; i < len; i++) {
    var midPoint = midPointBtw(p1, p2);
    ctx.quadraticCurveTo(p1.x, p1.y, midPoint.x, midPoint.y);
    p1 = points[i];
    p2 = points[i+1];
  }
  ctx.lineTo(p1.x, p1.y);
  ctx.stroke();
};

el.onmouseup = function() {
  isDrawing = false;
  points.length = 0;

Is there some way to get smooth lines using Picture.toImage

sounds similar to #21269


Allowing loading lottie content to be set from code behind

Hi folks,
I will have lotties files stored within a database, so I can't use the filename property. I would like to have something like a content property which can be set from code behind.
Any plans on this?
If not, I'm willing to implement it and share...

This is a good idea. Because of the time limitation for the moment we cannot implement new features. It's would be nice if you can do it.

Actually I found a way to implement it with the current featue set:

you need a StringReader X which holds the actual json data then
create a Y = new LottieSharp.JsonReader(X)
and then call SetAnimationAsync(y, "test")

"test" is any given name for the animation which seems to be needed for caching. The other option, calling SetAnimationAsync(Y) didn't work.
I could only provide my VB# test scripting, I current have no C# example.


GitHub Actions upload-artifacts@v2 deprecated moving to v4

Read the deprecation notice at https://github.blog/changelog/2024-02-13-deprecation-notice-v1-and-v2-of-the-artifact-actions/

There is another upload-artifact version 2 in the repo. You probably should update that too.
https://github.com/jbogard/MediatR/blob/0d3bf4c472b98e7fc72b2cbd6101907868ae09b0/.github/workflows/release.yml#L43

There is another upload-artifact version 2 in the repo. You probably should update that too.

Updated! Thanks.


little grammar correction

Correct the word "si" from conditional to affirmative mode in hooks-effect.md.

Thank you!


"google_free" returns error

Today I'm receiving errors using "translatte": "^3.0.0"
This is how I use it
text = "translate me please";
from = "en";
to = "it";
const translatedObj = await translate(text,
            {
                from,
                to,
                priority: [ "google_free" ],
                services: { "google_free": true }
            }
        ).catch(e => {
            console.warn(`Error during translation ${JSON.stringify(e)}`);
        });

The same code worked in past weeks/month, instead now I'm receiving an error
Error during translation {"google_free":"Text translation request failed"}
Do you have any idea about this issue?
Thanks

Having the same problem here ! The same code worked yesterday.

Last time the issue auto-resolved just wait and retry. It seems a flaky issue.

Has some update about this issue ?

same issue


BUILDPACK_URL deprecated, use buildpacks:set

Previously you could set a config var for BUILDPACK_URL, this value will still be used if set, though a buildpack value set through the CLI will take precedence. BUILDPACK_URL as a config var is now deprecated in favor of the buildpack value on the API and in the future will be migrated.

https://devcenter.heroku.com/articles/buildpacks#using-a-custom-buildpack

:+1:


Fix race condition

Fix race condition.

This change ends up clearing the purchase data right before we use it in the signal for marketplace service

The call can be moved under the signal, and then this issue should be fixed.


Various Improvements

I'm using your project to start work on STIG remediations for PostgreSQL.  I've made some changes that line up somewhat with the RHEL 7 STIG work you've done.
highlights:

use STIG-ID vs Vulid
indicate which tasks are not implemented
check mode improvements
per-item and per-audit variables

The commit messages do a good job of explaining what changed.
I'd prefer if you merge my pull request rather than squash.

Thanks for this!


Canvas Fallback Support

How hard would it be to implement fallback on Context-2D with the way the code is now? Is there a way to get ImGui raw buffer without relying on GL ?

I don't see why not. ImGui was designed to be disconnected from how it's rendered - whether it's rendered via opengl, directx, hand-rendered, whatever. So if you can create/draw textures, draw triangles, then it should be possible. Although via canvas context2d, you are likely to run into performance issues with complex draws/windows. Especially if it's all cpu-rendered.
See ImDraw* classes in imgui.h and GetDrawData() documentation.

As far as the GetDrawData() function goes is that it provides a set of instructions ready for openGL and the likes, I was referring to a pixel basis format because canvas is slow like you said, but canvas can render an entire array of colours. I was hoping there is something in ImGui that could convert all those triangle drawing instructions into an array of colours.

The whole point of using opengl or canvas 2d api is to rasterize those triangle descriptions into pixels that can be displayed on a screen/buffer. ImGui does not come with a rasterizer -- it's up to the user to supply that piece.
So you must either use gl, canvas 2d, or some other software render to perform the rasterization.

Yes, I’m currently attempting to make that software rasterizer. I have tried TinyGL, and haven’t been successful. At the moment I’m trying to bring Regal to javascript using emscripten. I’m having more success with that. But The rasterization process should be possible with tinyGL, I’m just not good at understanding the entire proccess itself.

An update, I asked for help on the main Dear ImGui and have replicated the problem I'm having onto a Git. If you could have a look or identify what the problem is, that would help.


Is there a diffuser version?

Is there a diffuser version?

We did not support the diffusers yet. However, I guess it is easy to combine DPM-Solver with diffusers. For example, applying DPM-Solver for stable-diffusion only needs to add this file: https://github.com/LuChengTHU/dpm-solver/tree/main/example_v2/stable-diffusion/ldm/models/diffusion/dpm_solver

The catch with 🧨diffusers is that their pipelines are written to sample things according to this Scheduler interface, and that's an interface that doesn't work well with higher-order samplers like these that need to do multiple model evaluations in a single step.
I hope we'll get diffusers to replace this with a better-suited API, but in the meantime it's possible to make yourself a pipeline that passes the model to the dpm-solver sampler. There's one such attempt to do that here: https://github.com/huggingface/diffusers/pull/857 — it needs some help but it has the potential to let you run the implementations of dpm-solver that are in k-diffusion against a diffusers model.

We did not support the diffusers yet. However, I guess it is easy to combine DPM-Solver with diffusers. For example, applying DPM-Solver for stable-diffusion only needs to add this file: https://github.com/LuChengTHU/dpm-solver/tree/main/example_v2/stable-diffusion/ldm/models/diffusion/dpm_solver

Very good work, I will try to use it on diffusers for better use

@dingjingzhen I also created a PR for stable-diffusion, and you can see the detailed modification here: https://github.com/CompVis/stable-diffusion/pull/440

The catch with 🧨diffusers is that their pipelines are written to sample things according to this Scheduler interface, and that's an interface that doesn't work well with higher-order samplers like these that need to do multiple model evaluations in a single step.
I hope we'll get diffusers to replace this with a better-suited API, but in the meantime it's possible to make yourself a pipeline that passes the model to the dpm-solver sampler. There's one such attempt to do that here: huggingface/diffusers#857 — it needs some help but it has the potential to let you run the implementations of dpm-solver that are in k-diffusion against a diffusers model.

Thanks for the help. I will try it.

Hi @keturn @dingjingzhen, I've created a pull request for diffusers that supports the multistep version DPM-Solver: huggingface/diffusers#1132
I hope it will be merged soon :)

Thanks to the great efforts of the huggingface team, DPM-Solver has been supported in diffusers! Close this issue now.


unicode issue ...

python setup.py build crashes under OSX with python3.5 with unicode error when LANG is unset

Is this closed by #310?

Actually it is related.

this is also addressed by numpy 1.11.2


BIGTOP-3583. Bump Zeppelin to 0.10.0.

https://issues.apache.org/jira/browse/BIGTOP-3583
Packaging and smoke-tests are worked on CentOS 8 x86_64.

Successfully built on Debian 10 x86_64. Worth noting that the build took several hours, a lot of time spent during dh-strip-nondeterminism. If it is not my docker config and happens to other people, we may need to add override_dh_strip_nondeterminism to the Debian rules file (but I am not super familiar with this step, will need to dig a bit more into it).

Tried with:
diff --git a/bigtop-packages/src/deb/zeppelin/rules b/bigtop-packages/src/deb/zeppelin/rules
index 6ac4cd8a..a6d61ad0 100644
--- a/bigtop-packages/src/deb/zeppelin/rules
+++ b/bigtop-packages/src/deb/zeppelin/rules
@@ -40,3 +40,5 @@ override_dh_auto_install: $(svcs)
        --doc-dir=/usr/share/doc/zeppelin \
        --source-dir=debian \
        --prefix=debian/tmp
+
+override_dh_strip_nondeterminism:
\ No newline at end of file
diff --git a/bigtop.bom b/bigtop.b

And it took 33 minutes to complete..

+1, build and smoke tests ran fine on Debian. Not sure if we should follow up on the dh_strip_nondeterminism step, it takes hours and we may not need it (but it shouldn't block this change).

Thanks, @elukey. I filed BIGTOP-3623 for dh_strip_nondeterminism. merging this.


Webserver

Is there any configuration for the server
I deploy application on my web-server the application work smoothly in the local but when i try to access it from the web there is an error
my server IP Address is public and add in bound rule for the port and open it for a public.
is there any extra configuration?

In the server, no configuration. But surely you should set server's IP/port in the client side. If it does not connect, there should be some firewall block.


BackdropFilter not working on Scroll to extreme top or bottom in Android (AndroidOverscrollIndicator.stretch)

Steps to reproduce

Wrap Text widgets with BackdropFilter to apply a blur effect.
Then, wrap Text widgets inside a ListView or Column.
On Android, when scrolling to the extreme top or bottom, you may notice that the BackdropFilter doesn't work as expected.

Expected results
BackdropFilter should work even after scrolling to the extreme top or bottom.
Actual results
BackdropFilter not working on scrolling to extreme top or bottom.
Code sample
Code sample
import 'dart:ui';

import 'package:flutter/material.dart';

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

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(widget.title),
      ),
      body: ListView(
        //   mainAxisAlignment: MainAxisAlignment.center,
        children: List.generate(
          50,
          (index) => ListTile(
            title: PrivacyBlurWidget(
              child: Text('Index: $index'),
            ),
          ),
        ),
      ),
    );
  }
}

class PrivacyBlurWidget extends StatelessWidget {
  final Widget child;
  final bool blur;
  final BuildContext? pContext;
  const PrivacyBlurWidget({
    super.key,
    required this.child,
    this.blur = true,
    this.pContext,
  });

  @override
  Widget build(BuildContext context) {
    double blurValue = blur ? 10 : 0;
    return ClipRRect(
      borderRadius: BorderRadius.circular(4),
      child: Stack(
        children: [
          child,
          BackdropFilter(
            filter: ImageFilter.blur(sigmaX: blurValue, sigmaY: blurValue),
            child: Container(
              decoration: BoxDecoration(
                color: Colors.red.withOpacity(0),
              ),
              //     child: overlay,
            ),
          ),
        ],
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[ +854 ms] VM Service URL on device: http://<IP_ADDRESS>:34345/-cx0Ah6jVP8=/
[   +1 ms] executing: /Users/a.selvan/Library/Android/sdk/platform-tools/adb -s emulator-5554 forward tcp:0 tcp:34345
[  +22 ms] 65015
[        ] Forwarded host port 65015 to device port 34345 for VM Service
[   +2 ms] Caching compiled dill
[  +32 ms] Connecting to service protocol: http://<IP_ADDRESS>:65015/-cx0Ah6jVP8=/
[ +126 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:65015/-cx0Ah6jVP8=/.
[  +75 ms] DDS is listening at http://<IP_ADDRESS>:65018/IqmsssHyXxM=/.
[  +35 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:65015/-cx0Ah6jVP8=/
[  +33 ms] DevFS: Creating new filesystem on the device (null)
[  +19 ms] DevFS: Created new filesystem on the device (file:///data/user/0/com.example.issue_app/code_cache/issue_appANKHSB/issue_app/)
[        ] Updating assets
[  +43 ms] Syncing files to device sdk gphone64 arm64...
[   +1 ms] Compiling dart to kernel with 0 updated files
[        ] Processing bundle.
[        ] <- recompile package:issue_app/main.dart 18e8b9a7-992a-4a5c-b5bb-eed5007687b9
[        ] <- 18e8b9a7-992a-4a5c-b5bb-eed5007687b9
[        ] Bundle processing done.
[  +54 ms] Updating files.
[        ] Pending asset builds completed. Writing dirty entries.
[        ] DevFS: Sync finished
[        ] Syncing files to device sdk gphone64 arm64... (completed in 57ms)
[        ] Synced 0.0MB.
[        ] <- accept
[   +3 ms] Connected to _flutterView/0xb400007827e10450.
[   +1 ms] Flutter run key commands.
[        ] r Hot reload. 🔥🔥🔥
[        ] R Hot restart.
[        ] h List all available interactive commands.
[        ] d Detach (terminate "flutter run" but leave application running).
[        ] c Clear the screen
[        ] q Quit (terminate the application on the device).
[        ] A Dart VM Service on sdk gphone64 arm64 is available at: http://<IP_ADDRESS>:65018/IqmsssHyXxM=/
[ +550 ms] The Flutter DevTools debugger and profiler on sdk gphone64 arm64 is available at: http://<IP_ADDRESS>:9102?uri=http://<IP_ADDRESS>:65018/IqmsssHyXxM=/
[+4184 ms] D/ProfileInstaller(25977): Installing profile for com.example.issue_app
[ +263 ms] D/EGL_emulation(25977): app_time_stats: avg=2196.19ms min=9.92ms max=4382.46ms count=2
[+1233 ms] D/EGL_emulation(25977): app_time_stats: avg=24.18ms min=8.45ms max=345.66ms count=51

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0.1 24A348 darwin-arm64, locale en-GB)
    • Flutter version 3.24.3 on channel stable at /Users/a.selvan/Documents/tools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (3 weeks ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/a.selvan/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16A242d
    • CocoaPods version 1.15.2

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

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

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

[✓] VS Code (version 1.89.1)
    • VS Code at /Users/a.selvan/Downloads/Visual Studio Code.app/Contents
    • Flutter extension version 3.98.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile)     • emulator-5554         • android-arm64  • Android 14 (API 34) (emulator)
    • macOS (desktop)                 • macos                 • darwin-arm64   • macOS 15.0.1 24A348 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         • macOS 15.0.1 24A348 darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript • Google Chrome 129.0.6668.90
    ! Error: Browsing on the local area network for Mr.Useless iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local
      area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

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

• No issues found!

Thanks for the report!
This is a known issue being tracked at https://github.com/flutter/flutter/issues/138940. Closing this issue as a duplicate, so please follow up on it for further updates.


FlowRouter no longer supports middleware

FlowRouter has deprecated middleware in favor of [triggers] (https://github.com/kadirahq/flow-router#triggers), so ensureSignedIn should really be a trigger to be used globally on enter:
FlowRouter.triggers.enter([ensureSignedIn], {except: ['loggedOut']});
where it takes parameters for context and redirect.  I'd try to provide a pull request, but I'm not sure I understand the UserAccounts code well enough.  I wrote one for the old AccountsEntry package that looked like:
ensureSignedIn = function(context, redirect) {
    if (!_.contains(AccountsEntryRouteList, context.route.name) && !Meteor.loggingIn() && !Meteor.user()) {
        Session.set('fromWhere', context.path);
        redirect('/sign-in');
        return Session.set('entryError', 'error.signInRequired');
    }
};

Hey @dovrosenberg, this was taken care of in the ensure-signed-in branch of this repo, but it wasn't merged yet.  I just merged everything into master so people can start using/testing it.
If you want to protect a route, you'd do this:
FlowRouter.route('/private', {
  triggersEnter: [AccountsTemplates.ensureSignedIn],
  action: function() {
    BlazeLayout.render(...)
  }
});

Or if you want to protect ALL routes:
FlowRouter.triggers.enter([AccountsTemplates.ensureSignedIn]);

I also added a helper for doing the auth check at the template level instead of depending on routes/redirects.
So, if you wanted to secure a specific template, you could add that template like this:
{{> ensureSignedIn template="myTemplate"}}

and that will render the default fullPageAtForm template from your chosen User Accounts templates package (bootstrap, materialize, etc).  Once signed in, it'll render myTemplate in place of the form.
If you want to declare a custom sign in template instead of fullPageAtForm, you would do this:
{{> ensureSignedIn template="myTemplate" auth="myLoginForm"}}

And that custom auth template just needs to include {{> atForm}} somewhere in it.  The only reason you'd use this optional feature is if you wanted to modify the layout around the atForm template (like
fullPageAtForm does).
As I type this, I'm also realizing this template helper should be in core instead of the routing package, but it's here for now, so test away!

FYI, template level content protection has been removed from this package in favor of adding it to core.  Will be available as soon as my pull request is merged.
See https://github.com/meteor-useraccounts/core/pull/496

Awesome.  Thanks!


POC of orchestrated components (multi-app)

This is a quick POC based on this comment in https://github.com/nuxt/rfcs/issues/30.  I initially looked into doing this with a module but didn't think I would have the right ability to hook in and make changes to the templates without providing custom templates (which would quickly become out of sync with general nuxt upgrades).  However, if I missed something and this could be done via a sustainable module approach, I'd be happy to try to convert it over.
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
The implementation here provides 2 new related features:

The ability to orchestrate Nuxt server-rendered components into a different application in which Nuxt/Vue may not be in control of the full page or routing - and thus would not want a full html/head/body structure in the SSR'd HTML
The ability to instantiate multiple Vue/Nuxt apps on a single page

The specific example implementation here is the use-case that my team is currently doing with our own vue-server-renderer build.  We're looking to migrate to Nuxt but this seems to be the only thing standing in our way.  We are able to get most of the way there with plugins, a custom app.html, etc - but the main thing we cannot get past is the _app.$mount('#__nuxt') aspect which sets a global limitation of a single app per-page.  Beyond that, there introduce some minor changes to the router and the ability to share a Vuex instance across the apps.
In addition to this type use-case of "plugging" Nuxt/Vue components into existing SSR apps, I think these new features could also potentially have use-cases in the micro-frontend landscape, but I haven't spent too much time thinking through those.
This addresses I think a slightly different issue that what is posed in https://github.com/nuxt/rfcs/issues/30, but looking for confirmation on that and happy to open a new RFC for discussion.
Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

(I haven't looked at tests or documentation yet, but I will if this gains any traction)

Codecov Report

Merging #8554 (36be578) into dev (0bc9d24) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #8554   +/-   ##
=======================================
  Coverage   67.53%   67.53%
=======================================
  Files          91       91
  Lines        3909     3909
  Branches     1080     1080
=======================================
  Hits         2640     2640
  Misses       1021     1021
  Partials      248      248

Flag
Coverage Δ

unittests
67.53% <ø> (ø)

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

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 0bc9d24...36be578. Read the comment docs.