More robust error message when neo4j or influxdb do not start properly

Currently neo4j will crash if the port is blocked(presumably it could also crash for other reasons). It would probably be helpful to forward any error messages from neo4j or influxdb to ISCAN so that people can know any issues with starting the database and fix them themselves.

Ok, I've added a check to whether ports are open before starting and will raise an exception now if they're not.

Thanks!
On Mon, Feb 4, 2019 at 2:22 PM Michael McAuliffe <notifications<EMAIL_ADDRESS>wrote:
Closed #180https://github.com/MontrealCorpusTools/ISCAN/issues/180.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/MontrealCorpusTools/ISCAN/issues/180#event-2116618330, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAwu0a8nVDOu89EnsqwqnSyaRI3iiymbks5vKIhbgaJpZM4adCW5.


Command not found after installing and reboot atom

Trace path
[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Ubuntu 15.04
Thrown From: node-resolver package, v1.0.1
Stack Trace
Failed to activate the node-resolver package
At Cannot read property 'command' of undefined

TypeError: Cannot read property 'command' of undefined
  at Object.exports.activate (/home/nelson/.atom/packages/node-resolver/index.js:12:21)
  at Package.module.exports.Package.activateNow (/opt/atom/resources/app.asar/src/package.js:245:19)
  at /opt/atom/resources/app.asar/src/package.js:838:25
  at Emitter.module.exports.Emitter.emit (/opt/atom/resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/atom/resources/app.asar/src/command-registry.js:226:20)
  at /opt/atom/resources/app.asar/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/opt/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:524:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/opt/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:347:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/opt/atom/resources/app.asar/src/window-event-handler.js:184:20)

Commands
     -0:22.9.0 core:move-up (ol.tree-view.list-tree.has-collapsable-children.focusable-panel.full-menu)
     -0:22.7.0 core:move-down (ol.tree-view.list-tree.has-collapsable-children.focusable-panel.full-menu)
     -0:20.9.0 editor:move-line-down (atom-text-editor.editor.is-focused)
     -0:20.3.0 core:move-down (atom-text-editor.editor.is-focused)
  3x -0:20 core:move-up (atom-text-editor.editor.is-focused)
     -0:18.4.0 editor:select-line (atom-text-editor.editor.is-focused)
  9x -0:17.3.0 core:move-up (atom-text-editor.editor.is-focused)
  3x -0:13.3.0 core:move-left (atom-text-editor.editor.is-focused)
     -0:11.4.0 go-to-line:toggle (atom-text-editor.editor.is-focused)
     -0:10.6.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:09.1.0 editor:select-line (atom-text-editor.editor.is-focused)
     -0:07.8.0 command-palette:toggle (atom-text-editor.editor.is-focused)
  4x -0:03.3.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -0:02.2.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:02.2.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:00.8.0 node-resolver:open-selected-dependencies (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "packagesWithKeymapsDisabled": [
      "node-resolver"
    ]
  }
}

Installed Packages
# User
autocomplete-modules, v1.3.0
color-picker, v2.0.13
javascript-snippets, v1.0.0
node-resolver, v1.0.1

# Dev
No dev packages

+1

+1
System: OS X 10.9.5
Atom: 1.2.4

+1
System: OS X 10.11
AtomAtom: 1.5.3

+1
System: Windows 10
Atom: 1.10.2

+1
System: Mac OS X 10.10.5
Atom: 1.12.6


Update GraphQL queries to use _dynamicUrl, pagination, and sorting

The WKND Share persisted queries should move away from _path, _authorUrl and _publishUrl and use _dynamicUrl instead.

https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/how-to/images.html?lang=en

WKND Shared persisted queries should also have example of using:

Sorting
Offset/Limit pagination
Cursor-based pagniation

As illustrated in this how to:

https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/how-to/large-result-sets.html?lang=en

Fixed by 3.0.0


Unable to run this

Hey there
i'm hoping I'm missing something small.  I am trying to get this running on my docker infrastructure.  This is what I have in my docker-config.yml and the .env I only updated the address and API key
services:
  stash-backup:
    image: ghcr.io/feederbox826/stash-backup:latest
    container_name: stash-backup
    volumes:
     - ${DOCKERCONFDIR}/stash-backup:/app/backup
    env_file:
      - .env
    environment:
     - STASH_URL=http://<IP_ADDRESS>:9999
     - STASH_APIKEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
     - CRON_SCHEDULE=*/10 * * * * # every 10 minutes
     - DISCORD_WEBHOOK="https://discord.com/api/webhooks/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
     - NOTIFY_ENABLED=true
     - DIFF_CRON=0 0 * * * # every day
     - FULL_CRON=0 0 */7 * * # every 7 days
     - CONSOLIDATE_CRON=0 0 2 * * # second of every month
     - IMG_CRON=0 0 1 * * # first of every month

When I run compose with this info I get this message
stash-backup  | jq: parse error: Invalid numeric literal at line 1, column 10
stash-backup  | No such file or directory
stash-backup  | mv: cannot stat '': No such file or directory

i'm also on the Stash Discord if you want to hit me up there
aaron

prettu sure you're just missing a /graphql on the end of STASH_URL 😅
- STASH_URL=http://<IP_ADDRESS>:9999/graphql

hopefully that does the trick

That was it. It's running now
On Wed, Jun 12, 2024, 18:56 feederbox826 @.***> wrote:

prettu sure you're just missing a /graphql on the end of STASH_URL 😅

STASH_URL=http://<IP_ADDRESS>:9999/graphql

hopefully that does the trick
—
Reply to this email directly, view it on GitHub
https://github.com/feederbox826/stash-backup/issues/1#issuecomment-2164028372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLHMYTNMEX4NRVWNRD7FH3ZHDG2FAVCNFSM6AAAAABJG5ZNW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGAZDQMZXGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


WIP: Add isOneOf method to ChiselEnum

Contributor Checklist

[ ] Did you add Scaladoc to every public function/method?
[x] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[ ] Did you specify the type of improvement?
[ ] Did you add appropriate documentation in docs/src?
[ ] Did you state the API impact?
[ ] Did you specify the code generation impact?
[ ] Did you request a desired merge strategy?
[ ] Did you add text to be included in the Release Notes for this change?

Type of Improvement

API Impact

Backend Code Generation Impact

Desired Merge Strategy

Release Notes

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (3.2.x, 3.3.x, 3.4.x, 3.5.0) ?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is a great start and thanks for picking up this issue, @chiplet !
The next step would be to add some tests for the new method here: https://github.com/chipsalliance/chisel3/blob/master/src/test/scala/chiselTests/StrongEnum.scala
If you are using IntelliJ, you should see a green arrow next to each test that lets you run it. If you are using sbt directly, the sbt testOnly command can be used to execute individual tests. In you case something like: sbt testOnly chiselTests.StrongEnumSpec should execute all tests in the StrongEnumSpec class.
Please let me know if you have any questions. And please let me know if you need me to run the continuous integration tests. Github now requires us to give first-time contributors the OK to run CI tests. Apparently they had some problems with people mining bitcoins :(

I've now added a test for the new method. The most use cases should be covered, but I'm not sure about how isOneOf should behave with the non increasing enum example found in the tests.
object NonIncreasingEnum extends ChiselEnum {
   val x = Value(2.U)
   val y = Value(2.U)
}

Should NonIncreasingEnum.x.isOneOf(NonIncreasingEnum.y) evaluate to true or false?
@ekiwi You could try running the CI tests now 👍

When starting to develop the tests I forgot the stop() call which resulted in the tester creating around 1.5GB large dump.vcd file under test_run_dir for each run. Should there be e.g. some sort of a timeout to prevent this?

Should NonIncreasingEnum.x.isOneOf(NonIncreasingEnum.y) evaluate to true or false?

I think it should be true.
They way to think about this, is that x and y are aliases and thus it should be possible to use them interchangeably.

Should NonIncreasingEnum.x.isOneOf(NonIncreasingEnum.y) evaluate to true or false?

I think it should be true.
They way to think about this, is that x and y are aliases and thus it should be possible to use them interchangeably.

Upon closer inspection there's a test that disallows instantiating non-increasing enums so NonIncreasingEnum.x.isOneOf(NonIncreasingEnum.y) doesn't even compile.

can you add some description of this to the website docs for ChiselEnum?

You mean in this file /docs/src/explanations/chisel-enum.md right?
I think currently the ChiselEnum naming and organization are quite confusing. I've seen the names StrongEnum, ChiselEnum and EnumFactory floating around and it was very unclear to me where to find the documentation for ChiselEnum when I was starting to use it. For example, when trying to search for ChiselEnum the API docs (like this) there are currently no results. The same applies when searching for StrongEnum. EnumFactory is the only class that can be found from the API doc, but even it doesn't contain any scaladoc comments. Maybe it's worth opening a new issue regarding this.

Maybe it's worth opening a new issue regarding this.

I think the only thing that needs to be solved in this issue regarding documentation would be to add some simple javadoc comment to the two methods. (/**   this method does ... */).
Besides that it would be great if you could rebase your commit on the latest master branch and resolve any conflicts.
Looking good!

I've added the related documentation so AFAIK this should be ready to merge.


tf.data.Dataset API how to batch un-same size images

System information
tensorflow1.5.0
Describe the problem
tf.data.Dataset API how to batch un-same size images?
Source code / logs
I don't want pad or crop to resize original image, how to batch all images using dataset api. if I call it directly:
train_data = tf.data.Dataset.from_tensor_slices((tf.constant(all_images), tf.constant(all_labels)))
    train_data = train_data.map(input_map_fn)
    train_data = train_data.batch(tf.contrib.data.batch_and_drop_remainder(2))

error says:
InvalidArgumentError (see above for traceback): Cannot batch tensors with different shapes in component 0. First element had shape [3543,3543,3] and element 1 had shape [1024,768,3].

Seems due the un same size of images.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.
If you think we've misinterpreted a bug, please comment again with a clear explanation, as well as all of the information requested in the issue template. Thanks!


Consider scoping tests to supported browsers

When running --project=sw-offline-google-analytics I see a lot of tests failing in Safari (which doesn't support Service Worker). Selenium assistant can find any and all browsers available, we just need to check them against a browserId.

This is just a case of restricting tests to only browsers that we wish to target which has been done now.


Specifying json_mode in with_structured_output for Custom Schemas in LangChain

Is it possible to pass in our defined schema and specify the use of json_mode, like in this example?
https://python.langchain.com/v0.1/docs/modules/model_io/chat/structured_output/
structured_llm = model.with_structured_output(Joke, method="json_mode")

It sounds to me like a good improvement.
Would you be open to send a PR for that?

@lkuligin Do you still need that PR? Seems like it was merged into the library?

This should also be added to ChatGoogleGenerativeAI
Reference: https://ai.google.dev/gemini-api/docs/structured-output


Added form editor

Hello, I hope you Z# have an feature like this:

yes, but it would need to use gtk because that also works on other platforms not just windows.

I don't ever plan on adding this functionality


Devbox 0.10.0 upgrade fails on process-compose install due to changed nix

What happened?
Description
Upgrade to devbox 0.10.0 and on first devbox services up we get the error nix profile remove": error: 'nix profile' no longer supports indices ('0') when trying to upgrade process-compose
A workaround (there might be better ones)

Find the process-compose package in devbox's nix profile nix profile list --profile ~/.local/share/devbox/util/profile
Note the package's name (for us it was aarch64-darwin which seems... wrong?)
run nix profile remove --profile  ~/.local/share/devbox/util/profile aarch64-darwin (replacing aarch64-darwin with your package name)

Other notes

this didn't happen on a M1 running nix 2.18.1, the change in cli must have been introduced sometime between that and 2.20.3

Steps to reproduce

Ensure you have a new-ish nix install (was observed on a macOS machine running 2.20.3)
Install devbox 0.9.1 or earlier, run devbox services up somewhere to ensure you have process-compose
upgrade to devbox 0.10.0 and run devbox services up somewhere to update to newer process-compose
See error upgrading "nix profile remove": error: 'nix profile' no longer supports indices ('0')"

Command
No response
devbox.json
No response
Devbox version
0.10.0
Nix version
2.20.3
What system does this bug occur on?
macOS (Apple Silicon)
Debug logs
➜  temp devbox services up
✓ Computed the Devbox environment.
Upgrading process-compose to v0.85.0...
Error: error running "nix profile remove": error: 'nix profile' no longer supports indices ('0')
: exit status 1
Error: There was an internal error. Run with DEVBOX_DEBUG=1 for a detailed error message, and consider reporting it at https://github.com/jetpack-io/devbox/issues
Error: exit status 1

Looks like a breaking change in 2.20 that wasn't covered in our profile upgrade. Have a PR that i'm testing now.


change arg type to atom in print and trace

with this change one can print what actually is during expression evaluation
this program will print now (woman $Y) vs printing False without these changes
(= (woman $X) False)
(= (sisters (woman $X) (woman $Y)) (trace! (woman $Y) True))
!(let $W (sisters $X $Y) $W)

I considered this before, but decided not to change the argument type of println! to Atom, because it is not too usable:

if you want to print the result of some calculations, they will be reduced in any case.
if you want to avoid wrapping println! into let each time you want to print the results of calculations, the type of println! argument should not be Atom. And this is quite a common use cae.
For example, if the argument type is Atom, and we want to print get-atoms result, ! (println! (get-atoms &self)) will print (get-atoms &self), which is useless, while ! (let $atoms (get-atoms &self) (println! $atoms)) will still output the reduced atoms. Thus, Atom-type argument makes only sense to print the exact provided expression. This is a less frequent case than printing the result of evaluation. If one wants to print an unreduced expression, it can be quoted, e.g.

(: TRACE (-> Atom Atom))
(= (woman $X) False)
(= (sisters (woman $X) (woman $Y)) (trace! (TRACE (woman $Y)) True))
!(let $W (sisters $X $Y) $W)

I'm not sure, maybe printing atoms as is in case of trace! can be more demanded. I don't have a strong opinion here. But it looks questionable for println!. @vsbogd , @luketpeterson , do you have any opinion?

I agree with @Necr0x0Der arguments about println! it is probably not convenient to use let each time and usually you need to reduce atom before printing.
Regarding trace! I would ask @ngeiswei opinion because he introduced trace! and probably most active user of it. I almost always use trace! to print atom without reducing it, and I use quoting to reach it. If it is more frequent use-case then I think making first argument of trace! atom may help.

Quotation solves problem for me, i tried quote from standard library before doing PR but it didn't work

But I'd also like to hear @ngeiswei opinion. Maybe, Atom in trace! can indeed be convenient.

It looks like I'm always using trace! with fully reduced first argument.  And one can always wrap a let around trace! to reduce its first argument if needed.  So I guess it wouldn't hurt to have its type be Atom.  But Just keep in mind that it is not how Idris or Haskell trace works.
Maybe we should consider introducing quotes instead of having to decide at the type level how a function should behave.

OK, if @ngeiswei has no preferences for Atom type, then let's keep it as is. Some official quoting operation in stdlib would be useful for sure.


Unable to run latest in all LTS node versions and unable to pin back

Describe the bug
There are two parts:

Ability to run previous major versions of create-react-app to support node LTS (in this case v12 which was dropped in 5.x)
The error message which implies it is a global install when it is not

For number one, the ecosystem relies on popular libraries supporting node LTS versions while they are still maintained. Dropping support 4 months early is tough. That said, if this was like a normal dependency which just allowed you to pin back it would not be an issue. Which leads me to my bug report that you cannot run 4.x to continue to running in node@12.
For number 2, it took us a bit to verify what was actually going on because the error message mentions "We no longer support global installation of Create React App.", which is a red herring here (see steps below which are not a global install but still trip the log).
Steps to reproduce
$ cd /tmp
$ npm install<EMAIL_ADDRESS>$ npx --no-install create-react-app my-app

You are running `create-react-app` 4.0.3, which is behind the latest release (5.0.0).

We no longer support global installation of Create React App.

Please remove any global installs with one of the following commands:
- npm uninstall -g create-react-app
- yarn global remove create-react-app

The latest instructions for creating a new app can

Expected behavior
That a user who explicitly installs and runs 4.x will still get the experience they expected out of that major version line.
Actual behavior
The latest check fails and the process exits.
Ideas for improving
The below command "works" if you manually patch the check here so that it does not log/exit.
create-react-app --scripts-version 4.0.3 my-app --template https://registry.npmjs.com/cra-template/-/cra-template-1.1.2.tgz

My thought was that if you added a --skip-latest-check which circumvented that semver comparison it would enable users to continue with the LTS until it's support actually expires.
Secondly, the logs could be updated to only print the message about a global install if it is actually a global install. The most reliable way to do this I know of is to compare to the node path path.dirname(process.execPath) === path.resolve(path.dirname(module.filename), '..') (or some other method to get the entry script, I think that is args._ from yargs maybe?)
If these ideas sound good we can probably open some PRs for them.

ASIDE: This is a breaking change in cra-template and should have been a major not a patch.

Seconded, this check basically prevents our users from using older versions of our packages that are not compatible with the Webpack 5 by default (which is one of the changes the create-react-app@5 brings).
I do not see any legitimate reason why I should not be able to run
npx create-react-app@4 my-first-app

just because there is a newer major version released. I understand that this is to nudge users to use the newest and greatest versions, but there are certainly situations this is unreasonably draconic:

having the create-react-app as part of a guide for using packages that are not compatible with React 17/Webpack 5/what have you in older versions (this is actually what is our issue, the instructions on our documentation page do not work and we have no way of making them work)
integration tests environment: you may want to run a specific version of create-react-app to bootstrap an app an then run tests (for the same reasons as in the first bullet)

I think implementing the --skip-latest-check @wesleytodd is suggesting would be a good way forward to remove what is basically a soft-lock of all the versions prior to 5.

React


Change repository settings

I think it makes sense to enable branch protection rules (or newer rulesets) to require CI to pass.

IMO looks good.

I think "Require branches to be up to date before merging" should be enabled, too. More importantly, right under it specific CI jobs should be required.
Right now, we have this:

What we should have is this:

Got it. Well, I don't have a strong preferences here but let's require them. IMO vuln shouldn't be required.

Proof:

Fixed


Assembly Version: *

You cannot put a wildcard in the assembly version in Visual Studio 2017.

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

ID: d868fc5c-dbe0-e662-fb8f-6931ed0f1aab
Version Independent ID: cf346c2b-04e8-9075-1034-632499a5ffeb
Content: Troubleshoot Office solution deployment - Visual Studio
Content Source: docs/vsto/troubleshooting-office-solution-deployment.md
Product: visual-studio-windows
Technology: office-development
GitHub Login: @John-Hart
Microsoft Alias: johnhart

#please-close this is now fixed


build(node): Bumping to Node 20

SUMMARY
Docs already require node 20. More and more dependencies need it. It'll be needed for various other upgrades too. Time to make the leap!

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Hey future Evan (or whoever)! When you bump Node again, make sure you get this, too.


Update language-support.md (About Japanese Support)

I confirmed that the model can be trained by both text and audio in Japanese.
Related Q & A
https://docs.microsoft.com/en-us/answers/questions/594885/we-would-like-to-know-noises-effect-to-speech-to-t.html

Confirming with PM

I am sorry but I noticed there is an assertion in the dialog.

So maybe Japanese audio is not supported for training...

#reassign @eric-urban

@LittleWat - We confirmed Japanese currently only supports Text customization. Only the text transcript from uploaded audio is used for adaptation and the audio part is being ignored. So we should not add “Audio” to that list. Thanks for double checking!

#please-close

@eric-urban Thank you for checking!


Resolve JSX intrinsic elements to index signature symbols

fixes https://github.com/microsoft/TypeScript/issues/5984
fixes https://github.com/microsoft/TypeScript/issues/10996
fixes https://github.com/microsoft/TypeScript/issues/55240

@typescript-bot test this
@typescript-bot run dt
@typescript-bot test top100
@typescript-bot perf test this

DT failure was just one of the runners having an npm install failure again, so I'll merge this. @sandersn did we not manage to actually fix that, or did we just decide that issue was transient and probably not our fault/responsibility?

Moving DT to a modern monorepo structure is blocked on Jake getting the perf infrastructure working, since he was working around a couple of pnpm limitations still left before we can make the switch.


[CARBONDATA - 1159] Batch sort loading is not proper without synchronization

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/292/

add to whitelist

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2414/

LGTM


Fix unreachable code warnings in GpuCast

After #3162 the build emits an unreachable code warning:
[WARNING] [Warn] /spark-rapids/sql-plugin/src/main/scala/com/nvidia/spark/rapids/GpuCast.scala:482: unreachable code

This removes a few of the match cases that will never be reached to resolve the build warning.

build

premerge CI seemed to fail before it even started.  Kicking again.

build

Couldn't find any revision to build. Verify the repository and branch configuration for this job.

Looks like git failed to fetch the merged PR from github, could be github inconsistent issue (data sync up delay)


Fix cmr search after key error

Hello!
During debugging adding readable_granule_name filter, I ran into key errors when making a request that returns zero hits. In these cases it looks like the CMR Search api does not send back cmr-search-after in the headers as expected in the code.
Added a fix, and new recorded tests that would have caught this
Please let me know if you have any questions or concerns

Thank you for your contributions @tyler-c2s . For the future, please create an entry in the 'Unreleased' section of the CHANGELOG summarizing what changes you have made (more info on what should go in the changelog can be found here: https://keepachangelog.com/en/1.1.0/)
Again, thank you!


Unknown Method

When i change default controller to auth. the result is '405 Method Not Allowed'
i have insert a data to my db.

because there're no GET in auth controller. maybe you can add implementation index_get function in controller.


Switch from pygithub to github3

Fix #77
Ref: http://github3py.readthedocs.io/en/latest/ and https://github.com/sigmavirus24/github3.py/ (looks like they have BSD 3-clause?)
Proof-of-concept that the script to update astropy-helpers work with this PR: spacetelescope/synphot_refactor#141 and spacetelescope/stginga#151

Ping...

@pllim - sorry, I haven't had a chance to look yet, will try and do so soon!


Evaluate NNTrainer with full network & unit tests

We have to evaluate nntrainer with full network. Compare with tensorflow output.

[ ] Check Layer by Layer

[x] implement python code to generate golden data with tensorflow
[x] Conv2D
[x] Fully Connected Layer
[x] Pooing 2D Layer
[x] Flatten Layer
[x] Optimizer : SGD
[x] Optimizer : ADAM
[x] Loss Calculation : MSE
[x] Loss Calculation : Cross-sigmoid
[x] Loss Calculation : Cross-softmax
[x] Weight decay
[x] Learning rate decay
[x] Batch normalization

[x] Evaluate with Full Network

[x] MNIST

[x] MNIST implementation ( NNtrainer & tensorflow )
[x] Comparison

[x] VGG (#200)

[ ] Mobilenet v1 (#201)

[ ] Mobilenet v2 (#201)

:octocat: cibot: Thank you for posting issue #350. The person in charge will reply soon.

Close and make another issues for mobilenet

Close and make another issues for mobilenet


⚠ wiki.minetest.net has degraded performance

In 7aef2e0, wiki.minetest.net (https://wiki.minetest.net/Main_Page) experienced degraded performance:

HTTP code: 200
Response time: 2791 ms

Resolved: wiki.minetest.net performance has improved in a6980a9 after 44 minutes.


Add support for arm64 Docker images

Kindly requesting to support arm64 builds :-)

Happy to point you at some of our multi-arch examples if you need a hand with this. We are currently moving from the Docker Hub + Travis to GHCR + GitHub Actions with buildx

Thanks @alexellis that would help a lot!

I suggest starting here https://github.com/openfaas/faas-netes/commit/bf7fb6d2b6ed01cc308b0dd5e79bb2bb6ced8d24

All right. Looks like this is good to go.
@tegk, can you verify the arm64 images work on your end?
https://hub.docker.com/r/connecteverything/nats-operator/tags


[fix] correctly swapping opcode

[x] issue #130
[x] follows contribution guide
[ ] code change includes tests

This follow changes implemented in #147

This bug was fixed as part of this PR so I will close this . https://github.com/keep-starknet-strange/shinigami/pull/147


OSF Data versions and onlineData_url links

- `b1_dam.MRIinputs = {'SF60','SF120'}`
- `b1_dam.Prot = []`
- `b1_dam.onlineData_url = https://osf.io/8ypzw/download`
+ % Changes to the b1_dam, patched, version 2.0.12 --> 2.0.13
+ `b1_dam.MRIinputs = {'SFalpha','SF2alpha'}`
+`b1_dam.Prot = struct('Alpha',struct('Format',{'FlipAngle'},'Mat',60));`
+`b1_dam.onlineData_url = https://osf.io/8ypzw/download`

Problem
After these changes, Travis test won't pass given that qMRGenBatch will be looking for SFalpha.nii.gz and SF2alpha.nii.gz, but the OSF data will be still containing SF60.nii.gz and SF120.nii.gz.
If I update the b1_dam OSF data, then people who have qMRLab version < 2.0.13 won't be able use qMRGenBatch or DownloadExample smoothly. Because https://osf.io/8ypzw/download is always pointing to the latest version of the data on OSF (this is the link in all former versions we assign to the onlineData_url attribute).
Reminder
OSF allows us to freeze data version in download links such as https://osf.io/8ypzw/download?version=2, which we should have been using so far instead of using the latest.
Solution
I will upload b1_dam_v2_0_13/b1_dam.zip (contains SFalpha.nii.gz and SF2alpha.nii.gz)  to OSF and update b1_dam.onlineData_url with the link pointing to (the version-1 of)  that file. This way:
i)   Ppl using qMRLab < 2.0.13 will still be able run examples smoothly
ii)  Travis will pass for qMRLab == 2.0.13
iii) Ppl using qMRLab >= 2.0.13 will be able to run examples smoothly
In addition to this, I will add version tags to the onlineData_url attributes of all models. This way, if we need to change something in the models that requires renaming respective OSF files, we won't break retro-compatibility.

I think that works. So should we change the links to all other methods so that the point to a specific version # right now?
@jcohenadad @tanguyduval how do you feel about this proposed solution by @agahkarakuzu ? I don't know if this will necessarilly be a problem that might occur frequently (model parameter/input names should and have been defined in a general way from their creation; Double Angle B1 mapping seems to be an odd case that slipped through the cracks; only dealing with FA = 60 and 120 was much to specific from the beginning)

I don't have strong feelings about this issue. Creating new zip files if the filenames changed is not a big deal. Agah solution looks good

Thanks @tanguyduval, fa297c401759c7c4d7efd0cfb152ead7ded1a288 seems doing good. I will close this issue upon merging #290


Critical vulnerabilities in JSON Web Token libraries

Im not sure if this is relevant but i came across this article on jwt.io and i'm not sure if this package is affected or not?
https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/
Thanks!

There's been some discussion of this before. See the Security Notes at the top of the README file. tl;dr: As long as you verify the signing method matches your expectation, you should be fine. This library attempts to make it easy to do the right thing while keeping it possible to do less standard things. If you follow the examples, you should be fine.

Sorry i never saw the notice.
thanks for your response and suggestion!

Would you consider (a) adding the security note to doc.go, (b) removing the jwt.Parse and jwt.ParseWithClaims top-level functions, and (c) erroring at https://github.com/dgrijalva/jwt-go/blob/master/parser.go#L30 when ValidMethods is nil?
It seems a little tricky to me to find the actually-secure way to use this library, and if you're starting from e.g. https://godoc.org/github.com/dgrijalva/jwt-go and aren't already familiar with this issue, it seems very easy to find a "parse" method that has this vulnerability.


Add Footer in Connection Reader Page

Related Issue
Footer is  ot available in Connection Reader page.
Fixes:  #3592
Description
As you can see before in Connection Reader Page no footer is available so i add new footer section in it, also alaign it properly and add all navigation page link in footer.
Type of PR

[x] Bug fix
[x] Feature enhancement

Screenshots / videos (if applicable)
Before footer is not added in this page
https://github.com/user-attachments/assets/b9212373-4cd2-4328-aefc-b1cedf674a33
After adding Footer in Connection Reader Page

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@atmajaa  Thanks for merging my commit.
I request you to please add labels in it.
Hacktobesfest-accepted
level 2
gssoc-ext


Fixed icons for linux direct install

Testing on fedora it fixes the issue. Id just verify that it doesn't mess up any of the other parts using snap or anything

With testing it fixes this issue #106.
If you install it using the gui, it doesn't show up but after installing it shows up in the menu which is what matters.

Thank you @sekwah41  for the effort. But I did not see any difference.
You just renamed the icon file and changed the category for linux packages.
Did you try to build it first and test if it's working before modifying the code?

That's actually all there is to it. I changed the Linux icon to point at the folder and then it looks for a icon file. It also looks for specific ones such as icon256x256.png.
The issue was the rpm was outputting it to a folder called 0x0 which isn't a valid size. Now it outputs two. One in the 256x256 and another in 64x64 or something like that (I forget the other one)
https://www.electron.build/icons#linux
Try building them before and after and use something like 7zip to explore the packages.
I can reinstall it to double check if you arn't seeing them pop up in the 256x256 folder like I mentioned.

Though I'll have to test removing the 256x256 and see if the auto resizer fully kicks in

Yes, I really appreciate what you did.
Before these issues came up. The original code is like this;
"icon": "./src/assets/logo-dark.png"

I realized that this does not pointing to the correct build folder included in the packaging.
So I changed it like this

As we can see build folder contains all the assets for production build.

That's why I ask if you tried to build the code from the master's branch and test it if it works because I already modified it and the only thing that lacking is testing it to a real fedora os.

Ohhhhhhhhhh yea I tested it before. You need the name specifically to be icon not logo. It's weird but that's what fixed it. It's the actual name that's the problem. Also I pointed it to the folder as it auto detects the files named icon or if you add the Mac icons file. The current master branch does the 0x0 behaviour I mentioned before.

I understand. If that's the only way to fix it.
But we don't actually need to change the<EMAIL_ADDRESS>because it is intended for MacOS.
What we can do to not mess around with other files is renaming the logo-dark.png to logo-dark256x256.png .
And making it sure that it only affects the rpm package.

Please let me know your thought too about this.

Checking and yea its all fine now on fedora with the new edits.

Just to clarify I reverted the changes and made the specific edits you'd said :) that all works fine.

Thank you @sekwah41 . Sorry for the late action.


As a user I can add recurring tasks

So that I can avoid duplicate work and adding daily/weekly/monthly tasks multiple times

The feature will not be implemented after discussion.


Godot4.0.2 import glb file too slow

Godot version
4.0.2.stable
System information
Windows 11, CPU: 1th Gen Intel Core i7-11700F,  Renderer: Forward+, GPU: NVIDIA GeForce RTX 3060
Issue description
Version: Godot4.0.2.stable
importing .glb file too slow, cost at least 3minutes. however using 3.5.x version is very fast.

Steps to reproduce
1.create a new project
2.create a floder named "t1"
3.drap s22.glb file to floder "t1"
Minimal reproduction project
test1.zip

however using 3.5.x version is very fast.

How long does it take? To give an idea of the slowdown

3.5.1.stable cost about 2 seconds.

however using 3.5.x version is very fast.

How long does it take? To give an idea of the slowdown
3.5.1.stable cost about 2 seconds.

however using 3.5.x version is very fast.

How long does it take? To give an idea of the slowdown

3.5.1.stable cost about 2 seconds.

Cannot replicate on latest version, debug build, it takes no longer than 10 seconds (didn't measure exactly)
Can you test with the latest release candidate?

Cannot replicate on latest version, debug build, it takes no longer than 10 seconds (didn't measure exactly, but nowhere near 3 minutes), I'm running AMD so could be NVIDIA related if it persists
Can you test with the latest release candidate or latest snapshot?

both 4.0.3 RC 2 & 4.1-dev2 take 3~4 minutes.
by the way, console error log of 4.1-dev2

That was fixed by #76910 but thank you for pointing out!

Could we get some testing from other people with AMD and Intel/NVIDIA hardware to see if there's a pattern there, could be any number of factors on my end but that is one potentially big one, NVIDIA in #64751 as well

What makes it so slow is the Embree BVH Intersector, it consumes 98% of the entire processing time.

What makes it so slow is the Embree BVH Intersector, it consumes 98% of the entire processing time.

This is due to LOD generation, which calls Embree to improve its quality.

Duplicate of https://github.com/godotengine/godot/issues/64751 (same cause).


feature :  Adding VigyBag Help Page

for this shopping app, it is very necessary to add help page for the new visitors who may get stuck somewhere in the transaction or in delivery the product or many more problems

hey @codervivek5
please assign me this issue

Thank You for assigning
I will do it as soon as possible


Bump backstage to 1.17.4

Initially, the backstage packages have been upgraded to the latest version, as well as bumped another package requested in the upgrade-helper.
Then, I needed to fix an issue with the config.d.ts, which is not allowing the type Record<string, string[]> anymore. So now the allowedBuckets have a different format, which needs to the define the platform as well.
The backend just works the same way, but I needed to make a few adjustments in the types so that everything works fine again. If this is not changed, then we get an error like this when backstage is started:
[0]   Record<string,string[]> stack=Error: Invalid configuration schema in config.d.ts, the following definitions are not supported:

That schema change is interesting, looks like the old schema was "ignored" before: https://github.com/backstage/backstage/pull/18837

That schema change is interesting, looks like the old schema was "ignored" before: backstage/backstage#18837

Yes... Seems that in this release they added a bunch of extra configuration/api checks to be more strict. However, this broke our config unfortunately, and also some catalog API calls which have been fixed in several patched versions (that's the reason why now it's the 1.17.4)


Tab completion not working with Accessibility Keyboard

Describe the bug

As the title says tab completion is not working with the Accessibility Keyboard.
Versions

Copilot for Xcode: 0.27.0
Xcode: 16.1
macOS: 15.1

Steps to reproduce

Open the Accessibility Keyboard in Settings -> Accessibility -> Keyboard -> toggle Accessibility Keyboard on
start typing in xcode and try to tab complete with the on-screen Accessibility Keyboard

Screenshots

https://github.com/user-attachments/assets/9990d285-b882-4543-b874-919aea852796
Logs

Additional context

Hi @tensei, thanks for trying out Copilot for Xcode and sharing a detailed bug.
Confirming I can reproduce this ✅ We will look into it.
As a workaround, you can assign an alternate keyboard shortcut to GitHub Copilot > Accept Suggestion in Xcode preferences:

@devm33 Thank you for the quick response, I’ll patiently wait for a fix 🙏

@tensei after looking into this, there is a limitation in macOS that the Accessibility Keyboard does not emit key events that we can observe. I have raised a Feedback with Apple for this.
I can confirm that setting a keybinding in Xcode preferences for the GitHub Copilot - Accept Suggestion action does work with the accessibility keyboard.

Describe the bug
As the title says tab completion is not working with the Accessibility Keyboard.
Versions

Copilot for Xcode: 0.27.0
Xcode: 16.1
macOS: 15.1

Steps to reproduce

Open the Accessibility Keyboard in Settings -> Accessibility -> Keyboard -> toggle Accessibility Keyboard on
start typing in xcode and try to tab complete with the on-screen Accessibility Keyboard

Screenshots
CleanShot.2024-10-29.at.21.54.29.mp4
Logs
Additional context


[Backport 2.8] Windows can't install apps in airgap setup

backport of: https://github.com/rancher/rancher/issues/44949

This issue is highly likely to be a manifestation of SURE-8159, introduced by this PR, which changed how charts are handled in air-gapped clusters. A PR is open to revert this change in 2.8-head. Once that PR is merged I will move this ticket into 'ready for qa' so that we can confirm that this is not a windows specific issue.

The PR has been merged into 2.8-head, so this issue is ready to be retested

tested on v2.8.6-rc1:

provisioned a cluster in airgap setup using latest k8s version available (v1.28.11 +rke2r1)
installed monitoring chart v103.1.1+up45.31.1  - pass
installed latest version of logging - pass


Rendering bug.

The pixel matrix has some minor bugs. I have noticed that the problem occurs only in X dimension. For example, some rows consist of 130 pixels, while another consist of 128. Probably that's the reason why they are blanks when drawing the vertical lines of the border.

I dont see this problem on my system , can you upload a picture of it? These look fine to me:

The bitmap seems fine as you can see, there still gaps though.
When I tried to render a cube using draw_line function I had to change the origin of x sometimes  in
order to render a perfect shape.
I m gonna check it again.

The gaps you see between each 4 lines are probably caused by your font, every braille character is basically 8 dots arranged in 2x4 pattern, but the font decides where those dots are in the character - if there is some space on top or bottom, the character in next line will look like it is some distance away, there is no way I can control that.


feat: center the Latest on medium text

Description of the change

Center the Latest on medium text.

Screenshots

Before:

After:

Checklist

[x] Added description of the change
[x] I've read the contributing guidelines
[x] Search previous suggestions before making a new PR, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes (optional):

I think in the design the button wasn't in the centre 🤔

I think in the design the button wasn't in the centre 🤔

Yeah, but to be honest, it looks better like this. 🙂


NCATS returning "unknown" on Workflow C query

0fd681f9-4b08-43d4-b7a3-cf6e561d49af

Opened in error


Legend at bottom of graph show on more than one line.

I draw graph having 7 data sets, use ChartLegendPositionBelowChartCenter for position of legend. Because legend length is so long, can't show all in one line, I want to show in 2 lines. How can we do it?

I guess you might want to custimze it? I remember we don't support the wrapping lines right now?
My workaround is I had my own legend implementation and put it in a scroll view. I once suggest @danielgindi to put the legend in a scroll view.

If I remember correctly wrapping lines is supported
בתאריך יום חמישי, 5 בנובמבר 2015, Xuan<EMAIL_ADDRESS>כתב:

I guess you might want to custimze it? I remember we don't support the
wrapping lines right now?
My workaround is I had my own legend implementation and put it in a scroll
view. I once suggest @danielgindi https://github.com/danielgindi to put
the legend in a scroll view.
—
Reply to this email directly or view it on GitHub
https://github.com/danielgindi/ios-charts/issues/532#issuecomment-153927873
.

Just set legend.wordWrapEnabled = true

I have a stacked bar graph and want the labels in the legend to come below each other in a vertical stack
have used
graphView.legend.maxSizePercent = 0.70
graphView.legend.wordWrapEnabled = true
still doesnt work

Is it possible to trim the legend view , to be able to display limited number of  lines only , specific height or limited number of values.

@a-radwan I guess not, take a look at ChartLegend


FourierOp Norm

I thought to norm of FourierOp should always be 1?

Note to myself:
wondering if this could also cause issues with self-supervised training.
Should check if F(subset of trajectory)(image) = F(image)[subset] -- which might also be a good test.

Also, what was the outcome of #381 ?

I thought to norm of FourierOp should always be 1?

I don't think this holds for arbitrary FourierOps. If a FourierOp only yields an undersampled k-space then the Norm will not be 1. Also if padding or cropping of image-space/k-space is required (mismatch of recon_matrix and encoding_matrix) the norm will not be 1.
Here I verified that FFT and NUFFT lead to the same result:
https://github.com/PTB-MR/mrpro/blob/3c6d873cd72afe1feda0abba93d677036d783b9f/tests/operators/test_non_uniform_fast_fourier_op.py#L51
for recon_matrix == encoding_matrix and fully-sampled k-space.
The oversampling-parameter of the NUFFT I am not sure about. All the packages I know do not ensure that the norm is independent of this parameter but this does not mean it is the correct thing to do.

It should also match for all of the common MR trajectories. Otherwise, a tiny trajectory change would result in a scaled image -- which would be quite surprising.
Ill try if I can make these tests pass..

I thought to norm of FourierOp should always be 1?

I don't think this holds for arbitrary FourierOps. If a FourierOp only yields an undersampled k-space then the Norm will not be 1. Also if padding or cropping of image-space/k-space is required (mismatch of recon_matrix and encoding_matrix) the norm will not be 1.
Here I verified that FFT and NUFFT lead to the same result:
https://github.com/PTB-MR/mrpro/blob/3c6d873cd72afe1feda0abba93d677036d783b9f/tests/operators/test_non_uniform_fast_fourier_op.py#L51
for recon_matrix == encoding_matrix and fully-sampled k-space.
The oversampling-parameter of the NUFFT I am not sure about. All the packages I know do not ensure that the norm is independent of this parameter but this does not mean it is the correct thing to do.

For the Fast Fourier operator, the operator norm should always be be one (if norm="ortho" is used, which we always have, right?), regardless of full or undersampling. For the general FourierOp, the norm will indeed not always be one.


Multiple errors when trying to use cubemap rendertargets

We are getting Metal validation errors when trying to:

render to a cubemap (one face at a time, using image view with VK_IMAGE_VIEW_TYPE_2D and subresourceRange.baseArrayLayer 0..5)
generate mipmaps for a cubemap (by blitting from face to face)

For the first issue, we get this Metal error:

validateAttachmentOnDevice:267: failed assertion `Slice is 1, but the texture has only 1 slices'
durring vkCmdBeginRenderPass

For the second issue, we get this Metal error:

validateFunctionArguments:3377: failed assertion `Fragment Function(fragCmdBlitImageF): incorrect type of texture (MTLTextureType2DArray) bound at texture binding at index 0 (expect MTLTextureType2D) for texture[0].'
from vkCmdBlitImage

It looks like the texture that we create is somehow classified as either a 2D texture or maybe a texture array instead of a cube texture? We create the texture with VK_IMAGE_TYPE_2D, arrayLayers=6 and VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT flag; after this we create the image view with type VK_IMAGE_VIEW_TYPE_CUBE; after this we create 6 image views with type VK_IMAGE_VIEW_TYPE_2D (to render into each individual face).

Closing as fixed.


FutureWarning when exporting  fancy table

This is my code in the netbook:
import pandas as pd
# styles for tables

titre = {
    "selector":"caption",
    "props": [("color", "black"),("text-align","center"),("font-size","14px")]
}
index_names = {
    "selector": ".index_name",
    "props": [("background-color", "#800000"),("font-style","italic"),("color","white"),("font-weight","normal")]
}
headers = {
    "selector": "th:not(.index_name)",
    "props": [("background-color", "#800000"),("color","white"), ("text-align", "center"),("padding", "12px 30px"),("font-size","14px")]
}
headers_small = {
    "selector": "th:not(.index_name)",
    "props": [("background-color", "#800000"),("color","white"), ("text-align", "center"),("padding", "8px 20px"),("font-size","14px")]
}

properties = {"border": "0.5px solid lightgrey", "width": "100px", "text-align": "center"}

data_f={'modello 1':['A1','-','-','D1','-'],
            'Res1':['0,622','-','-','0,344','-'],
            'modello 2':['A2','B2','C2','D2','E2'],
            'res2':['0,902','0,800','0,850','0,910','0,781'],
            'range 1':['0,4 - 0,1','-','-','5,2 - 21,4','-'],
            'range 2':['0,4 - 0,1','0,4 - 0,6','0,1 - 2,32','5,2 - 21,4','1 - 6'],
       }
df_f = pd.DataFrame(data_f,index=['P1','P2','P3','P4','P5'])

df_f.style.set_table_styles([titre,index_names,headers_small])

I have 3  problems:
1 - when exporting, the Res1 and Res2 columns loose the comma - so instead of 0,633 i get 622
2 - when exporting the table formatting (colours etc ) is lost
3 - when exporting I get this future Warning:
  /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/jupyter_docx_bundler/converters.py:81: FutureWarning: Passing literal html to 'read_html' is deprecated and will be removed in a future version. To read from a literal string, wrap it in a 'StringIO' object.
  df = pd.read_html(s)[0]

I can live with the two first problems - i just go and correct the data and change the formatting
problem 3:  I would not like to lose the possibility of having nice looking tables in the browser instead of pure markdown, and be able to export them
All my modules are updated as of today.
Thank you

add-on : it fails with pandoc 3.1 works perfectly with pandoc 2.17
I see you ave an open issue with pandoc 3 so I think this is the same problem.
best

Glad, you could figure out yourself. Right now my spare time is quite limited.


when I build images from Dockerfile--11,it's failed

the error is :

sed -ri s/#(create_main_cluster) .*$/\1 = false/ /etc/postgresql-common/createcluster.conf
apt-get install -y postgresql-11=11.6-1.pgdg90+1
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '11.6-1.pgdg90+1' for 'postgresql-11' was not found

please help check it

then,I try other version,it's have the same error,like version Dockerfile-10

sed -ri s/#(create_main_cluster) .*$/\1 = false/ /etc/postgresql-common/createcluster.conf
apt-get install -y postgresql-10=10.11-1.pgdg90+1
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '10.11-1.pgdg90+1' for 'postgresql-10' was not found

https://github.com/docker-library/postgres/issues/678#issuecomment-586403467
Duplicate of https://github.com/docker-library/postgres/issues/677

but my system is CentOS7.6 , How to do

If you want to docker build it, you need to use the newest version of the Dockerfile. Upstream has updated their apt repo and it only contains the latest of each release (which the Dockerfiles have been updated to use):
https://github.com/docker-library/postgres/blob/4dc16e44d16480d9c8e5eb705c15468d65366e43/10/Dockerfile#L78
https://github.com/docker-library/postgres/blob/4dc16e44d16480d9c8e5eb705c15468d65366e43/11/Dockerfile#L78


Notify inkwell of order of conditional branch operands

The documentation of LLVM suggests the operand order of predicate, true_block, false_block. However, inkwell switches the order of true_block and false_block. We should suggest inkwell add this to their documentation.

See https://github.com/TheDan64/inkwell/issues/399.


x/build/cmd/releasebot: provide binary release for darwin/arm64 for 1.16

Based on discussion in a release meeting, I understand our current plan is to aim to provide binaries (and installer) for darwin/arm64 in time for the Go 1.16 release.
I'm making this as the tracking issue which reflects the current state: there are release-blocker, NeedsInvestigation, okay-after-beta1 labels applied, and the Go1.16 milestone set. Perhaps this will need to change as time passes.
 If that builder cannot be added in time, we may need to implement this via a temporary workaround.
CC @golang/release, @cherrymui, @aclements, @FiloSottile, @rsc.

Our recently-updated plan here is to try to get this in before beta 1 this week. Removing okay-after-beta1 to reflect that status.

With issue #39782 being resolved now, CL 278436, and additional internal release workflow changes to codesign and notarize macOS binaries, and testing, the work needed be able to provide a binary release for the new darwin/arm64 port has been done.
The upcoming Go 1.16 Beta 1 release and further Go 1.16 releases will have go*.darwin-arm64.pkg installer and go*.darwin-arm64.tar.gz archive files provided at https://golang.org/dl/. Closing.


Skip contents of symlinked directories in clean

Fixes https://github.com/sbt/sbt/issues/5852
The clean task was previously deleting the contents of directories that
were symlinked into the target directory. This was an oversight because
it never occurred to me that users might symlink a directory whose
contents they did not want deleted into the target directory.

Thanks a lot!


pls: 5.0.0 -> 5.1.1

Description of changes
https://github.com/dhruvkb/pls/tags

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

pls

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

1 package built:

pls


fix: Remove use of deprecated trait IntoCow

The trait IntoCow was deprecated in Rust 1.7.0

Coverage decreased (-0.5%) to 91.157% when pulling 6f68d413a58f74f330623cd809b4c2d4e622fc00 on icorderi:master into 6401347dd92602e7e7897b9c717f31b0c65bb277 on GGist:master.

Thanks, didn't notice the breakage since 1.7.0. I'll merge this now and push a new minor version out once I make a few other changes.
Cheers!


Add the corresponding comments for each selected option.

Are you requesting a feature, reporting a bug or asking a question?
Ask a question
What is the current behavior?
The current function is to add comments to the entire problem by adding the hasComment attribute.
What is the expected behavior?
So how do you implement a question like dropdown, radiogroup, and checkbox where each answer is selected to add a comment? Thank you
How would you reproduce the current behavior (if this is a bug)?
I want to do this by adding hasComment attributes to the choices attribute, but it doesn't work at this point.
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code

      {
            type: "radiogroup",

            choices: [
              { value: "Yes", hasComment:true},
              { value: "No", hasComment:"false"}
            ],
            isRequired: false,
            name: "1000007",
            popupdescription: "Select the operating system you are currently using.",
            title: "Do you use any front-end framework like Bootstrap?",
            page: "page2"
          },

Specify your

browser:
browser version:
surveyjs platform (angular or react or jquery or knockout or vue):
surveyjs version:

@ShuQingGit It would be hard to imlement. In fact, you would have to create your own custom widget. You may look at this repo for more information.
Another solution is to use the matrix dropdown question with two columns, where the first column will be checkobx and the second column is a comment, the comment can be visible/invisible by some rules.
Thank you,
Andrew


No such file or directory

Steps to reproduce

Go to AssetLib
Find and install NativeLib
Go to Project Settings and enable NativeLib
Go to the NativeLib tab
Set the path to Python.

Result:
NativeLib not found.
Log:
"No such file or directory: 'C: \ Users \ user \. Nativelib \ master.tar.gz'"
Decision:
Create .nativelib folder manually and press NativeLibCLI

@tigz19 Could you show me the full log of first start godot with addon?

@tigz19 Could you show me the full log of first start godot with addon?

@tigz19 Thank you for report! The issue was fixed in NativeLib-CLI v0.3.2

@tigz19 Thank you for report! The issue was fixed in NativeLib-CLI v0.3.2


Improve formatting

Currently, the page-header always creates additional columns for the session-scope and logout button. Although, these components are not always built. However, even if these components are not built the columns are present, which create unwanted wrapping within the header.
To Do:

Either create logic within the existing header or a new header that is built with a single column when the session-scope and logout buttons are not built

After investigating, the CSS styling of streamlit apps ads a gap of 1rem to all containers. Anytime new columns are created, a new horizontal container is generated. The multiple horizontal containers were causing additional spacing within the header.


Increase formation modifier for Building

Change Building formation AV modifier from 25% to 50%, so engineers don't automatically lose to everything if interrupted mid-construction.

I'm going to change the rate that AV drops from 2 to 1 as well, so it's a more steady decrease in fighting efficiency. Column and pressed formation drop at 2 and 3 respectively, but that makes more sense as it's a marching formation and forced march respectively. I can imagine engineers being dedicated to construction being taken by surprise by attackers, but they would not be as exhausted/unprepared as if they were focused on marching at full speed.


RFE: implement switching roots and sub-images (aka nested builds)

as per our discussion in the links below the proposed change is
# the same tag passed to docker build
SWITCH_ROOT <other_image> <new_root> ...
# add -<tag-suffix> to the tag up to :
TAGGED_SWITCH_ROOT <tag-suffix> <other_image> <new_root> ...

I'm not sure about SWITCH_ROOT_N_PUBLISH or SWITCH_ROOT_W_TAG or TAGGED_SWITCH_ROOT
but the idea that the build root is kept, if no SWITCH_ROOT it will be used and tagged,
if there are at least one SWITCH_ROOT the build root is kept a side and a new image is used as root for the tag passed, for TAGGED_SWITCH_ROOT which can be used multiple times, new_root are still with respect to build image which is not yet discarded.
RUN make install SERVER_PREFIX=/dest/server CLIENT_PREFIX=/dest/client
RUN cp /bin/server-extra /dest/server/bin/
RUN cp /bin/client-extra /dest/client/bin/
SWITCH_ROOT busybox /dest/server
TAGGED_SWITCH_ROOT client busybox /dest/client

using the above with docker build -t foobar:2.5 would result two images foobar:2.5 and foobar-client:2.5
we even can support a special <other-image> that start with self
RUN make install SERVER_PREFIX=/dest/server CLIENT_PREFIX=/dest/client
RUN mkdir -p /dest/server2/bin/ && cp /bin/server-monitor /dest/server2/bin/
RUN cp /bin/client-extra /dest/client/bin/
SWITCH_ROOT busybox /dest/server
TAGGED_SWITCH_ROOT slave self /dest/server
TAGGED_SWITCH_ROOT slave-monitor self-slave /dest/server2
TAGGED_SWITCH_ROOT client busybox /dest/client

the idea originates from RPM SPEC-file
here is an example http://pkgs.fedoraproject.org/cgit/mariadb.git/tree/mariadb.spec
# for mariadb
%files
# for mariadb-libs
%files libs
# for mariadb-config
%files config
# for mariadb-common
%files common
# for mariadb-server
%files server

https://github.com/docker/docker/issues/7115#issuecomment-133548130
https://github.com/docker/docker/issues/15271
https://github.com/docker/docker/issues/14298#issuecomment-129616725

Hi @muayyad-alsadi. Thanks for opening this issue.
I'm not a fan of having a build publish multiple images - I think there should always be only one result at the end. I'm also not a fan of having a build instruction that sets an image name or tag - that should be done separately after the build and is easier to reason about when there is only a single resulting image.
While I really like the SWITCH_ROOT/PIVOT_ROOT concept I thing it would be better to split it into separate commands that give more flexibility over what's in the resulting image: another FROM <image> instruction to begin a new build with the given base image using the previous container root filesystem as the context. The SWITCH_ROOT behavior would then be this followed by a COPY instruction. We would then only need to handle context switching and copying between containers (probably just through the client for now) in order for to get this to work.

I'm not a fan of having a build publish multiple images

me neither. I don't like starting from a single dockerfile and ending with multiple images. but there is a real-world use case. A monster code-base that result in so many sub-images (as in sub-packages).
for example in ubuntu a single source for libreoffice builds more than 150 binary deb packages.
although this is too much and less likely to be the most common use-case docker but still it's a real world example.
a more realistic example would be a common code-base for both server and client or for server and its replication daemon ..etc.
since dockerfile is a single file, it's more like specfile in rpm world than debian's directory rules. that's why I think we should look at it for inspirations (it took decades to become what it's now and it's part of linux standard base), here I'm talking about
%package client which would build base-client.rpm so TAGGED_SWITCH_ROOT client busybox /dest/client would result in an image called base-client (where base is what was passed by the user)
I'm not going to use multiple images but I'm sure someone would need it, it's a valid use case. and it won't cost us any thing to implement.
to make it clean TAGGED_SWITCH_ROOT is not followed by full [REPOSITORY[:TAG]] but rather the suffix to be added to the base tag

While I really like the SWITCH_ROOT/PIVOT_ROOT concept I thing it would be better to split it into separate commands that give more flexibility over what's in the resulting image: another FROM  instruction to begin a new build with the given base image using the previous container root filesystem as the context. The SWITCH_ROOT behavior would then be this followed by a COPY instruction. We would then only need to handle context switching and copying between containers (probably just through the client for now) in order for to get this to work.

exactly we would have to start with build container = working container and do all the build/commit in the build container, until we face SWITCH_ROOT, in that case build container will remain the old one but working container will point to a new one with fresh FROM (scratch, busybox, ...etc) then copy the following arguments to SWITCH_ROOT from the build container (which is available to us using CP).
why not use COPY? well, you need to know that we have 3 locations:

host (directory with dockerfile)
build container (the one before pivot)
working/destination container

I don't think overloading COPY and ADD commands is right (COPY HOST:/src/ /dest and COPY BUILD:/src/ /dest)
supporting multiple builds (not really nested) is trivial as there is always one single working/destination container and one single fixed build container. and all paths after SWITCH_ROOT refer to the build original build container.
each SWITCH_ROOT or TAGGED_SWITCH_ROOT  will do docker commit to apply the tag and at the end of the file we do the final commit and tag.
SWITCH_ROOT is only allowed once, while TAGGED_SWITCH_ROOT can be specified multiple times.
both SWITCH_ROOT  and TAGGED_SWITCH_ROOT do not inherit any thing from build image except maintainer in other words exposed ports, volumes, cmd, entry point and current directory ..etc are not inherited from build image (they are reset to that of the pivot image and the only exception is the maintainer)
exposed ports, volumes, cmd, entry point are not allowed before SWITCH_ROOT or  TAGGED_SWITCH_ROOT

but there is a real-world use case.
...
for example in ubuntu a single source for libreoffice builds more than 150 binary deb packages.
...
a more realistic example would be a common code-base for both server and client or for server and its replication daemon ..etc.
...
I'm not going to use multiple images but I'm sure someone would need it, it's a valid use case. and it won't cost us any thing to implement.

Container image building is not and should not be a solution to everything. A Dockerfile is used to produce a single container image. If you need multiple container images you can have several different Dockerfiles and even have common base images if you want to (this is a recommended pattern). If you do have a "monster code-base" with several sub directories that each produce their own container image (which a lot of people do have - including myself) then you can have a separate Dockerfile for each container image you need to build. If you want to automate the process of building all of these images together then you can use a variety of other tools to accomplish that task (many people use Makefiles for this).

I don't think overloading COPY and ADD commands is right (COPY HOST:/src/ /dest and COPY BUILD:/src/ /dest)

I wasn't proposing overloading them, they would behave the same, it's just the context which changes. The source path is always relative to the context directory (which can be local or in a container) and the destination is always in a container.

If you do have a "monster code-base" with several sub directories that each produce their own container image (which a lot of people do have - including myself) then you can have a separate Dockerfile for each container image you need to build. If you want to automate the process of building all of these images together then you can use a variety of other tools to accomplish that task (many people use Makefiles for this).

no, it's not just about automating or scripting this with Makefiles. it's a completely different use case.
not just a different images from same code base, but from the same makefile and same build, take a look at Fedora's MariaDB SPEC-file, the lines below will compile both mariadb server and mariadb client tools
%cmake . \
         -DCMAKE_INSTALL_PREFIX="%{_prefix}" \
# ....
make %{?_smp_mflags} VERBOSE=1
# ...
make DESTDIR=%{buildroot} install

if you want to create to separated images for mariadb server and client one need to either to compile it twice for each image (ie. compile every thing in first pass then discard every thing and keep the server, then compile everything again, then discard every thing except client) or to use the proposed method
let's get back to the LibreOffice/OpenOffice example (which has a server by the way, and it's used by many other services like BigBlueButton). Last time I compiled OpenOffice it took more than 8 hours (since fedora has a policy not to include any pre-built thing including jars). Having 150 Dockerfiles each takes 8 hours to build.
go projects takes no time to compile maybe this is why you don't see why some people might need this. but there are some elephantine legacy projects that takes forever to compile and repeating this for every component is not a good idea and putting them in a single container in many cases is not the docker way (single process per container, although mariadb example was ok, because only server would be running)
sometimes a project requires you to build all components at once because there are some compile-time mapping for plugins ..etc.
currently what people do, is to build outside docker at host or downloaded package files rpm, deb or use ubuntu PPA ..etc.) then use ADD/COPY to put them.

I wasn't proposing overloading them, they would behave the same, it's just the context which changes.

after pivot we have COPY conf/server.conf /etc/foo.conf does this mean copy conf/server.conf from build container or from current directory on host.
sorry for the long post, it's a matter of taste and I'm not trying to change your mind, I'm just trying to give you vision so that you make your mind while knowing all aspects.

...
go projects takes no time to compile maybe this is why you don't see why some people might need this. but there are some elephantine legacy projects that takes forever to compile and repeating this for every component is not a good idea and putting them in a single container in many cases is not the docker way (single process per container, although mariadb example was ok, because only server would be running)
...

The fast go compiler is nice to have, but I'm very familiar with the problem of long compile times for big projects. I used to work on WebKit which sometimes took almost a couple of hours to compile from scratch (depending on build flags and how many cpu cores you had dedicated to it - it typically took 20-30 minutes on the beefiest build machines with 12 cores and 24GB of memory). I don't expect every containerized component of LibreOffice be build from scratch and take several hours each. There's always been a way to compose your builds to try to optimize for not rebuilding things. You can do it with multiple Dockerfiles and sharing base images. I'll try an example:
Say you have a client/server application that you want to build container images for, the client and server each having separate images that you can spawn containers from to use independently. You're client and server are both from a pretty big C/C++ codebase and because you're a great code architect you make sure that the client and server share as much code as possible. When you build both the client and server locally it takes about an hour, and you want your resulting images to not have the source code in them either, only the binaries.
The first thing you would do is write a Dockerfile which copies in all of the source code and compiles the shared libraries only. You might want to call this "my-app-core" or something similar. This image on its own isn't very useful. It contains all of your codebase and dependencies and the compiled shared object code but doesn't have either your client or server binary yet.
Next you'll want to build the client and server binaries separately. You'll write 2 more Dockerfiles: one for the client and one for the server. Starting with the client, you write a Dockerfile which is FROM my-app-core and then write more instructions to continue compiling the client binary. These steps are relatively fast because the base image "my-app-core" already contained a lot of the compiled code that goes into the client. The rest of the Dockerfile drops down to a nested build and copies the client binary into a new empty filesystem.
The Dockerfile for the server would be similar: FROM my-app-core, followed by the steps to compile the server binary which is boosted by the fact that so much of it was pre-built in the base image, then a nested build that creates a final image which contains only the server binary and any other small files you might need.
You'll probably find that building your images this way is much faster than if you have built the client and sever separately from scratch. The total build time is reduced by the fact that you used the common core base image which contained the pre-built shared libraries and you only had to build it once. Depending on how you do it, changes to only either the client or server code requiring rebuilds may be even faster because you can take advantage of build cache and never have to rebuild the common core base image.
When you want to publish your application to your users you only need to release the resulting minimal client and server images and not the bloated intermediate "my-app-core" image.

I actually do something similar, I currently have a system that uses fabric/ansible and my base image has supervisord and openssh disabled. my build script uses docker exec to start sshd then then inject host public key, then run fabric/ansible build, then start another base docker images then scp or pipe tars between containers then disable sshd and cleanup then commit.
docker exec -i container1 bash -e "cd /dest && tar -cf - ." | docker exec -i container2 tar -xvf -

people in atomic project has their own integrated builder called reactor (integrates with koji the cloud builder in fedora infrastructure that compiles all fedora/EPEL rpms and push them ..etc.)
https://github.com/projectatomic/atomic-reactor
but I believe a small simple TAGGED_SWITCH_ROOT would eliminate all of those things and make them much more simpler.

Hi, everyone. We found that being able to have multiple FROM instructions in a single Dockerfile is very convenient. Take a look at https://github.com/grammarly/rocker

Regarding rocker with multiple from like this one
FROM google/golang:1.4
MOUNT .:/src WORKDIR /src
RUN CGO_ENABLED=0 go build -a -installsuffix cgo -v -o rocker.o rocker.go
run image
FROM busybox
ADD rocker.o /bin/rocker

First it's a nice thing that just work and accomplish the job
But I have concerns:
It opens the gates too wide,  people would tend to do crazy things on the
host and attach it to the container. For example they might inject setuid
binary in the mounted volume.
My objective is to leave the host alone. You should not depend on what is
installed on it nor you pollute the host. The host status after the build
should be the same as before it.
On Tue, Sep 8, 2015, 10:52 PM Yuriy Bogdanov<EMAIL_ADDRESS>wrote:

Hi, everyone. We found that being able to have multiple FROM instructions
in a single Dockerfile is very convenient. Take a look at
https://github.com/grammarly/rocker
—
Reply to this email directly or view it on GitHub
https://github.com/jlhawn/dockramp/issues/1#issuecomment-138681751.


Added merge to db doc. Renamed read db to just 'read'

The database merge function was missing from the documentation, so it was added.
While in the routine, also tidied up some other docstrings.
One change to note: the db.read_img_info_from_db_file   had a very clunky name. It was renamed to db.read.  The old name still references the new fucntion and this works.

#38 is for documentation improvements


Splines: skip DrawGaussian when sigma is 0, prevents possible divide-by-zero

This seems to be the preferred approach discussed in https://github.com/libjxl/libjxl/issues/129
(Name added to AUTHORS as per contributing checklist.)

(note: Sami is OOO until Monday)


SQL panel points a query in an included template to the same line of its parent template

Tested with:
views.py
from test_debug_toolbar.models import Question

def index(request):
    return render(request, 'index.html', {'questions': Question.objects.all()})

index.html
{% extends 'base.html' %}

{% block content %}

Hello there! This is a test for debug toolbar.

Below is an included template that makes a SQL query. But in debug toolbar, it is signified in "index.html", while it should be in "inner.html".

{% include 'inner.html' %}

{% endblock content %}

inner.html

Here's inner.html:

All questions:

{{ questions }}

The SQL query of Question.objects.all() is executed at the line 5 of inner.html, but in the SQL panel, it is incorrectly pointed to the line 5 of its parent template index.html:

Tested with current master and develop branch, and Django 1.10.4.
For the complete test Django project: https://github.com/lingxiaoyang/test_debug_toolbar

I investigated a little of this issue. The problem seems to exist only on Django 1.9 and later, most probably because of the following code (reference to utils.py):
def get_template_context(node, context, context_lines=3):
    source = getattr(node, 'source', None)
    # In Django 1.9 template Node does not have source property, Origin does
    # not reload method, so we extract contextual information from exception
    # info.
    if source:
        line, source_lines, name = get_template_source_from_source(source)
    else:
        line, source_lines, name = get_template_source_from_exception_info(
            node, context)

It is very possible that function get_template_source_from_exception_info doesn't work accurately on include template tag.
Then I tested the same code with Django 1.8, and the template tracking is working correctly:

Further investigation shows that Django 1.10.6 itself has the same problem when dealing with template exception, which is fixed in 1.11b1. However, Django debug toolbar gives wrong result for both versions. On an older version 1.8.11, both Django and Django debug toolbar work as expected.
Here's the comparison table:

Django versionDjangoDjango debug toolbar

1.8.11CorrectCorrect

1.10.6IncorrectIncorrect

1.11b1CorrectIncorrect

I'll see what Django has changed in its code and perhaps submit a PR on this later.

Questions to the package maintainers:
At the Django side, the bug concerning {% include %} and {% extend %} indeed exists in versions 1.9 and 1.10, and is being fixed in 1.11 LTS. However, this bugfix will not be backported to 1.9 and 1.10 (most probably because they will be out of support soon, according to Django roadmap). References: tickets 27584 and 27956.
At present, django-debug-toolbar copies the same code in Django to extract the template source. This code will need a small fix in order to work correctly in Django 1.11, but a more significant change will be required if we want it working with 1.9 and 1.10. You may compare the code of the bugfix and debug_toolbar/utils.py.
The question is therefore: do we want this fix to only work with Django 1.11 LTS and keep how it is now with versions 1.9 and 1.10; or do we also provide another solution for these two older versions?
A 2nd question: do we need a unit test on this, or is it fine to just keep it the same with Django's code?

I think doing the same thing the Django maintainers do is fine; I'm alright with only being correct on 1.11 upwards.
That being said, if someone wants to do the work of supporting 1.9 and 1.10 as well despite Django itself being incorrect there I certainly won't stop them.
Unit tests are always good, and if it's possible to easily construct an unit test then it should be done (tm). If it's hard or nobody wants to invest the time then following Django is fine. If we do more than Django does by fixing the reports on 1.9 and 1.10 an unit test would clearly be a requirement though, because I expect the code involved would be more complex and we would certainly want to avoid inadvertent breakage.

i'm still seeing the issue with django-debug-toolbar 1.11 and django 1.11.23


Possibly two bugs with Loop and centeredSlides

Check that this is really a bug

[x] I confirm

Reproduction link
https://codesandbox.io/s/netflix-vue-swiper-forked-9k3fq2?file=/src/components/HomePage.vue
Bug description

centeredSlides & loop bug.

In my example, i made the active slider bigger. if i'm in mode loop: false, and centeredSlides: false,
It will not go to the last few elements and the active stop before reaching the last few element and i need the active to make a
action event later.
You can use the keyboard arrow to test (To make it work, be sure that the cursor is not stuck in the edition mode then triple click on the result view but outside the Swiper to disable the cursor from the edit).
I want it to look like Fire TV or most Smart TV and the last few slides should go the extreme left too.
Everything is ok in centeredSlides: true, mode or loop: true,.

But there's a second bug the i can't explain.

If you hold the left or right keyboard Arrow  <-   -> in loop: true, it will go slower, but it go faster on loop: false, mode.
If it got fixed, it may be cool to have a keyboard Arrow hold speed option.
Also, if you click on the left or right arrow very fast repeatedly, it will go as fast as you go on the keyboard in loop: false, mode but not in loop: true,.
These bugs are the same on every framework like vue or without any external framework.
https://codesandbox.io/s/netflix-vue-swiper-forked-9k3fq2?file=/src/components/HomePage.vue
Expected Behavior

On loop: false,, the last few slides should go the extreme left too.
Speed option on keyboard arrow and same speed in loop: false, or loop: true,

Actual Behavior

On loop: false,, the last few slides stop in the middle and do not reach the left and are not active slider anymore.
Slider speed are not the same in loop: false, or loop: true, and on keyboard on fast tap on arrow keyboard or on arrow hold too.

Swiper version
7.0
Platform/Target and Browser Versions
Cordova
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Swiper v9 comes with fully reworked and now different loop functionality. If you have similar issues in Swiper 9, open a new issue with a CodeSandbox showing the issue.


feat: update to webpack4+

In webpack 4, Tapable#apply and Tapable#plugin raise a deprecation notice.

Tapable#apply(plugin) must be replaced by a call to plugin.apply
Tapable#plugin(hook, fn) must be replaced by a call to hook.tap (or hook.tapAsync)

Note: This is breaking change because it drops webpack < 4 compatibility.
For more info:

Highly suggest to refractor with Target design which uses webpack native plugins such as JsonpTemplatePlugin. This leads to incompatibility with lower webpack version.
Update wxapp-boilerplate  needed.
webpack4+ does not support node <= 4, need to delete Travis CI  test version.

Finally all checks have passed. @Cap32 Please check this when you get free.


enh: adding light & dark mode

Hi,
I worked on adding the light & dark mode to the project.

Hi @AryanNayak,
Please check the deployment error

Yes,@ming-tsai let me have a look

Hi @AryanNayak,
Any updated?


⚠ Bofrost.de has degraded performance

In b310c2b, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 899 ms

Resolved: Bofrost.de performance has improved in 41ca3ad after 2 hours, 5 minutes.


Issue for requesting a review of the Kanban board

This is the link to our Kanban Board: https://github.com/iKuartz/item-catalog-ruby/projects/1
There are three people on our team.
Team Member #1: @awaisanwar544
Team Member #2: @41hulk
Team Member #3: @iKuartz

**STATUS: APPROVED  🟢 **

Hi team,
Your project is complete! .

Cheers and Happy coding! :clap: :clap: :clap:
Feel free to leave any questions or comments in the PR thread by mentioning my Github username if something is not 100% clear.

As described in the Code reviews limits policy you have  limited number of  reviews per this project. If you think that the code review was not fair, you can request a second opinion using this form.


Optionally expose WebAssembly.Module object for wasm ESM

Feature request
What is the expected behavior?
Ideally it would be somehow possible, when importing a wasm file as an ESM, to get a hold of the WebAssembly.Module object. Currently, however, I believe that the instantiation of the WebAssembly.Instance is hidden in weback (that's good!) but it ends up burying the instance of WebAssembly.Module and WebAssembly.Instance, not allowing JS code to grab ahold of it and manipulate it.
What is motivation or use case for adding/changing the behavior?
The main motivation for this use case is the upcoming threads proposal in WebAssembly. With threads one visions for idiomatic usage is to post a WebAssembly.Module to a set of worker threads (along with a SharedArrayBuffer). All worker threads would then use the exact same compiled code and shared memory, allowing for reduced resource usage and faster instantiation as the module no longer needs to be fetched and compiled once per thread.
To that end, the moviation here is implementing a method for Webpack to be used while also enabling this method of multithreaded wasm, posting a WebAssembly.Module instance to worker threads.
How should this be implemented in your opinion?
There's unfortunately no great way to implement this mapping to the ESM spec for wasm. I've opened an issue on the wasm ESM integration repository for this feature, but there's not consensus yet on what to do. The idea, though, is that just like how an wasm "ESM" can export its own memory it could also export its own instance/module (somehow).
In any case in the meantime I'm hoping that we could polyfill https://github.com/WebAssembly/esm-integration/issues/14 somehow or otherwise enable it. I'd personally be ok with "magic names" that automatically and synthetically get added to a wasm ESM export list (like __webpack_webassembly_module).
Are you willing to work on this yourself?
I can try! I'd need some assistance though in navigating around.
cc @xtuc, you likely have thoughts on this!

Instead of this manual way of using wasm in a worker I would like to evaluate an alternative way:
This need to be added to the spec, but browser could also implement it without spec change:

When using compileStreaming or instantiateStreaming browser should keep the compiled WebAssembly.Module in their own Cache (Code Cache). When using compileStreaming or instantiateStreaming again and the request can be fulfilled from the memory or file cache browser should skip compiling the WebAssembly.Module and instead use the compiled code from the cache.

This would result in the following behavior:
Just use the same url for the wasm in the Worker and it will work. No manual posting of the module via postMessage. The worker could use esm-integration too.

agreed with @sokra, especially since "structured cloning" of the WebAssembly.Module seems not wanted in the spec, the user won't need to have access to it.
What are the other use-cases of exposing WebAssembly.Module?

I'd personally be ok with "magic names"

I'm not really fan of that idea; bad UX, might be overriden, difficult to debug, etc.

Even if the module can get the same performance characteristics via other means the shared memory always has to be posted, right?
I was struggling to figure out a way for webpack to totally transparently handle wasm in workers with shared memory and would love to have a way! In the meantime though my best thinking was to provide enough hooks for the main thread to do it


Thanks!


How to use local path to deploy model?

Prerequisites

[X] I have read the ServerlessLLM documentation.
[X] I have searched the Issue Tracker to ensure this hasn't been reported before.

System Information

ServerlessLLM 0.5.0
Linux with 2 GPUs

Problem Description
In quick start guide(https://serverlessllm.github.io/docs/stable/getting_started/quickstart), the deploy command is "sllm-cli deploy --model facebook/opt-1.3b".
I can not connect to HuggingFace for now, but I have the model in my local disk, how can I use the local path to deploy model?
Steps to Reproduce
Code snippets:

Steps to reproduce:
1.
2.
3.
Expected Behavior
No response
Additional Context
No response
Usage Statistics (Optional)
No response

It seems that I can not just simply use absolute path in deploy config.json "pretrained_model_name_or_path" field, like
"pretrained_model_name_or_path": "/root/models/xx/"

Thank you for your feedback! We're aiming to implement this missing feature in the next one or two releases.
In the meantime, you can work around this by converting the Transformers model checkpoint to sllm format and saving it to the designated model path (e.g., the default path is ./models/transformers/). This approach works because the model downloader will skip downloading if it detects that the required model already exists in the specified path. For reference, see the relevant code here:
https://github.com/ServerlessLLM/ServerlessLLM/blob/da683eefe109da5c803841137cbf291733189a16/sllm/serve/model_downloader.py#L43-L48
Below is an example script for converting a local Transformers model:
from sllm_store.transformers import save_model

# Load a model from a local path
import torch
from transformers import AutoModelForCausalLM
model = AutoModelForCausalLM.from_pretrained('YOUR_LOCAL_MODEL_PATH/facebook/opt-1.3b', torch_dtype=torch.float16)

save_model(model, './models/transformers/facebook/opt-1.3b')

This should help for now! Let us know if you have further questions or run into any issues.

Thanks for your detailed answer, I can work around now by your solution.


MemoryError: needs a '--no-cache-dir' install option

Fails with a Memory Error when using pipenv install on a machine without large memory - e.g. a minimal docker image, (although it appears to have adequate memory for most development - 800Mb / 1Gb available, and the same package works ok on most other environments) - see stack trace below
It appears to be a problem with pip itself.
Excessive memory use when caching large packages #2984
Stack overflow: memory-error-while-using-pip-install-matplotlib
The recommended approach, pip install --no-cache-dir can be used as a workaround to allow this to run without reading the whole package into memory.
Is it possible to supply that argument using pipenv? Are there any other ways to fix it?
Pipfile
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true

[packages]
mapnik = "*"

MemoryError
# pipenv install
Creating a virtualenv for this project...
⠋New python executable in /root/.local/share/virtualenvs/opt-zvmYt2-H/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /root/.local/share/virtualenvs/opt-zvmYt2-H
No package provided, installing all dependencies.
Pipfile found at /opt/Pipfile. Considering this to be the project home.
Installing dependencies from Pipfile.lock...
An error occured while installing! 7/30 - 00:00:34
Collecting mapnik==0.1
  Downloading mapnik-0.1-cp27-none-any.whl (37.4MB)

Exception:
Traceback (most recent call last):
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/basecommand.py", line 215, in main
    status = self.run(options, args)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/commands/install.py", line 335, in run
    wb.build(autobuilding=True)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/wheel.py", line 749, in build
    self.requirement_set.prepare_files(self.finder)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/req/req_set.py", line 380, in prepare_files
    ignore_dependencies=self.ignore_dependencies))
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/req/req_set.py", line 620, in _prepare_file
    session=self.session, hashes=hashes)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/download.py", line 821, in unpack_url
    hashes=hashes
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/download.py", line 659, in unpack_http_url
    hashes)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/download.py", line 882, in _download_http_url
    _download_url(resp, link, content_file, hashes)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/download.py", line 603, in _download_url
    hashes.check_against_chunks(downloaded_chunks)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/utils/hashes.py", line 46, in check_against_chunks
    for chunk in chunks:
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/download.py", line 571, in written_chunks
    for chunk in chunks:
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/utils/ui.py", line 139, in iter
    for x in it:
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/download.py", line 560, in resp_read
    decode_content=False):
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/response.py", line 357, in stream
    data = self.read(amt=amt, decode_content=decode_content)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/response.py", line 314, in read
    data = self._fp.read(amt)
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/_vendor/cachecontrol/filewrapper.py", line 63, in read
    self._close()
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/_vendor/cachecontrol/filewrapper.py", line 50, in _close
    self.__callback(self.__buf.getvalue())
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/_vendor/cachecontrol/controller.py", line 275, in cache_response
    self.serializer.dumps(request, response, body=body),
  File "/root/.local/share/virtualenvs/opt-zvmYt2-H/local/lib/python2.7/site-packages/pip/_vendor/cachecontrol/serialize.py", line 87, in dumps
    ).encode("utf8"),
MemoryError

If we were going to do this, we'd make it default for everyone, or use an environment variable, which i'm mildly opposed to doing.

open an issue with pip, to see if they'll honor an environment variable for this.

Just as a note, I believe pip will support setting this in pip.conf. I'd look into that as a possible option.

Just to add on to @nateprewitt I do believe pip.conf supports this setting.

As a workaround, I type the following in the terminal instead of using the pip.conf file:
export PIP_NO_CACHE_DIR=false
It will work. Hope it will help those who read this thread.


add note about br_netfilter and fix some typos

We had a problem getting traffic to flow back to the attacking laptop until we stumbled on the br_netfilter module.

Great work, hadn't noticed the change, think it was introduced in a new version of the *nix kernel.


I used orb to match image, but the result is too weird.

Hello, this is my first time to use opencv orb to match image, and the result is too weird. did I write wrong code or some parameters need to be change?
why there is no point on here moth?
my original image:

the target image:

the result is:

my code is:
use opencv::core::{no_array, DMatch, Mat, Vector, NORM_HAMMING};
use opencv::features2d::ORB;
use opencv::features2d::{draw_matches_with_thickness_def, BFMatcher};
use opencv::features2d::{DescriptorMatcherTraitConst, Feature2DTrait};
use opencv::highgui;
use opencv::imgcodecs;
fn main() -> Result<(), opencv::Error> {
    let mut orb = ORB::create_def()?;
    let img1 = imgcodecs::imread("girl.png", imgcodecs::IMREAD_GRAYSCALE).unwrap();
    let img2 = imgcodecs::imread("girl_mouth.png", imgcodecs::IMREAD_GRAYSCALE).unwrap();
    let mut keypoints1 = Vector::new();
    let mut descriptors1 = Mat::default();
    orb.detect_and_compute(
        &img1,
        &Mat::default(),
        &mut keypoints1,
        &mut descriptors1,
        false,
    )?;
    let mut keypoints2 = Vector::new();
    let mut descriptors2 = Mat::default();
    orb.detect_and_compute(
        &img2,
        &Mat::default(),
        &mut keypoints2,
        &mut descriptors2,
        false,
    )?;
    let bf = BFMatcher::new(NORM_HAMMING, false)?;
    let mut matches: Vector<DMatch> = Vector::new();
    bf.train_match(&descriptors2, &descriptors1, &mut matches, &no_array())?;
    let mut out_img = Mat::default();
    draw_matches_with_thickness_def(
        &img2,
        &keypoints2,
        &img1,
        &keypoints1,
        &matches,
        &mut out_img,
        1,
    )?;
    highgui::imshow("matched", &out_img)?;
    highgui::wait_key(0)?;
    Ok(())
}

I'm not such an expert in feature detection with OpenCV unfortunately, but if you manage to get a working C++ or Python code that does what you want I can help you translate it to Rust

thank you