Updating to swag 1.7.2 fails with a checksum error

Describe the bug
Running GOPROXY=direct go get -u github.com/swaggo/swag in a project with swag 1.7.1 installed fails:
$ GOPROXY=direct go get -u github.com/swaggo/swag
go: downloading github.com/swaggo/swag v1.7.2
go get<EMAIL_ADDRESS>verifying module: checksum mismatch
	downloaded: h1:CA4/ezTlV00Tlfb/7Tgt97VLDtn4kfPswoew8VLs6qc=
	sum.golang.org: h1:ymR5/BHAVylGilrqxU78UNUIfVBDjBwnEWWaOeOm7aE=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

To Reproduce
Steps to reproduce the behavior:

Check out a project with swag 1.7.1 installed
Run GOPROXY=direct go get -u github.com/swaggo/swag
See error

Expected behavior
Update works
Your swag version
1.7.1, but more likely affecting 1.7.2
Your go version
1.16.5 linux/amd64

it should be fine in 1.7.3

This is now happening again, this time with 1.7.5:
$ GOPROXY=direct go get -u github.com/swaggo/swag

go: downloading github.com/swaggo/swag v1.7.5
go get<EMAIL_ADDRESS>verifying module: checksum mismatch
	downloaded: h1:ZMxuVDmGJ09Lgn9l7TGfEaT/4xWowQqAatzgjgrnOHE=
	sum.golang.org: h1:Qirr4bt+mZ+idHOsHAT5AVettx8no9KuAlQpQx9ghwA=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

ping @ubogdan

switched to 1.7.6

@ubogdan Works now, thanks!


OWNERS: Add sig/ or area/ to every OWNERS file which was missing it.

What this PR does
Before this PR: OWNERS files without label based sig or area assignment existed.
After this PR: All OWNERS files have label based sig or area assignments, this helps to make sure that this ownership is bubbling up into labels during PR reviews.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made: N/A
The following alternatives were considered: N/A
Links to places where the discussion took place:
Special notes for your reviewer
None
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[x] Design: A design document was considered and is present (link) or not required
[x] PR: The PR description is expressive enough and will help future contributors
[x] Code: Write code that humans can understand and Keep it simple
[x] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[x] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[x] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[x] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[x] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/retest

This is just adding labels.
@dhiller @vladikr @AlonaKaplan I'd appreciate a review

/retest
On Fri, Feb 16, 2024 at 2:00 PM kubevirt-bot @.***>
wrote:

@fabiand https://github.com/fabiand: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
pull-kubevirt-generate df22c58
https://github.com/kubevirt/kubevirt/commit/df22c58a43b1ffb700c67d285826d7793044566a
link
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11225/pull-kubevirt-generate/1757328787063705600
true /test pull-kubevirt-generate
pull-kubevirt-unit-test 4f51964
https://github.com/kubevirt/kubevirt/commit/4f51964879763005b61e6ecb8c2a654f236d5099
link
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11225/pull-kubevirt-unit-test/1758473292710154240
true /test pull-kubevirt-unit-test
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/pull/11225#issuecomment-1948347393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUMAHO3TP7KYGOXDRTYCTYT5J5VAVCNFSM6AAAAABDGCPOHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYGM2DOMZZGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@xpivarc @dhiller @acardace could it be that some PR got merged to main without some make generate or aliek?

thanks @phoracek I had to remove all of cluster-up anyway

@dhiller @EdDev  please review

/approve


WIP: Fixed blocking loader, switched default translation to Clear Quran

Default translation now is Clear Quran with footnotes( we'll remove simple Clear Quran with next build )
Fixed loaders

Checklist

[ ] Unit tests written
[ ] Manually tested
[ ] Prettier & ESLint were run
[ ] New dependencies are included in package-lock.json

Screenshot

rebuild

rebuild

Deployed to: http://staging.quran.com:33012

Sweet! Let me know when to review!

Deployed to: http://staging.quran.com:33016

rebuild

Deployed to: http://staging.quran.com:33017

Deployed to: http://staging.quran.com:33019


Install failed because of "wheel error"

Installing on fresh Pop OS 20.04 on t480
Followed readme step by step and after executing install i have this:
  Building wheel for dbus-python (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/lenovo_fix/venv/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-2h2_e_y7/dbus-python/setup.py'"'"'; __file__='"'"'/tmp/pip-install-2h2_e_y7/dbus-python/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-kwpy38o8
       cwd: /tmp/pip-install-2h2_e_y7/dbus-python/
  Complete output (6 lines):
  usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: setup.py --help [cmd1 cmd2 ...]
     or: setup.py --help-commands
     or: setup.py cmd --help

  error: invalid command 'bdist_wheel'
  ----------------------------------------
  ERROR: Failed building wheel for dbus-python
  Running setup.py clean for dbus-python
  Building wheel for pycairo (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/lenovo_fix/venv/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-2h2_e_y7/pycairo/setup.py'"'"'; __file__='"'"'/tmp/pip-install-2h2_e_y7/pycairo/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-vg86vj70
       cwd: /tmp/pip-install-2h2_e_y7/pycairo/
  Complete output (6 lines):
  usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: setup.py --help [cmd1 cmd2 ...]
     or: setup.py --help-commands
     or: setup.py cmd --help

  error: invalid command 'bdist_wheel'
  ----------------------------------------
  ERROR: Failed building wheel for pycairo

I try to install wheel command by pip3 install wheel, it said that already installed and do nothing... tried different workarounds found on google but it wont work ((

This is just telling you that the installer is not able to build the wheel for pycairo. The venv should be fine though.

Moved to manjaro, problem gone

Installing python3.6-dev solved this for me on Pop OS.


Help with Installing Apprise

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
I want to enable notifications via Apprise & when i selected it, i get this "Status: Apprise is not installed. Read more"
When i click on that link it says to install apprise with "pip install apprise"
I am not well versed with this, but i have uptime kuma running in a docker container.
can you please help me with the steps to install apprise?
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.15
💻 Operating System and Arch
Ubuntu 22.04 running Docker
🌐 Browser
Brave Version 1.70.123 Chromium: 129.0.6668.89
🖥 Deployment Environment
Docker compose
services:
  uptime-kuma:
    image: louislam/uptime-kuma:1.23.15
    container_name: uptime-kuma
    volumes:
      - ./uptime-kuma-data:/app/data
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 3001:3001  # <Host Port>:<Container Port>
    restart: always

Hi
this is the screenshot from my install

Its enabled in Live Demo though

Since this is running in a docker VM that runs other containers as well, can there be a conflict with a port number?

Sorry, i more thing i forgot to add, I'm running the container with a cloudflare reverse proxy.
services:
  uptime-kuma:
    image: louislam/uptime-kuma:1.23.15
    container_name: uptime-kuma
    volumes:
      - ./uptime-kuma-data:/app/data
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 3001:3001  # <Host Port>:<Container Port>
    restart: always

  cloudflared:
    image: cloudflare/cloudflared
    container_name: cloudflare-tunnel
    restart: unless-stopped
    command: tunnel run
    environment:
      - TUNNEL_TOKEN=xxxxxxxxxxxxxxxxxxxxxxx

I just ran another instance without that and apprise was showing as installed.
services:
  uptime-kuma:
    image: louislam/uptime-kuma:1.23.15
    container_name: uptime-kuma
    volumes:
      - ./uptime-kuma-data:/app/data
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 3001:3001  # <Host Port>:<Container Port>
    restart: always

i have uptime kuma running in a docker container

but the docker version works fine

I guess this is resolved, or?
Feel free to reopne if you have furhter questions

Yes, i went with the docker version. Not sure why the manual install doesnt include apprise


How about adding option to enable -allow-internal-distribution for making library-evolution not supported libraries?

I just thought something from seeing this issue (https://github.com/giginet/Scipio/issues/32)
Some frameworks might be failed to build as XCFramework with enabling library-evolution.
xcodebuild command supports to make XCFramework without library-evolution, means not having .swiftinterface.
with this, the build process will be the same as to build process using packages normal way.
If using Scipio is for build cache, it works with not enabling library evolution in popular cases.
So I propose Scipo supports using a option (--allow-internal-distribution)
just like Realm doing https://github.com/realm/realm-swift/blob/master/build.sh#L166
xcodebuild -create-xcframework -allow-internal-distribution -output "$xcframework_path" \
        -framework "$os_path" -framework "$simulator_path"

this approach comes from my previous outdated work.
I was stuck in building prebuilt binary using cocoapods. some libraries failed to build with library-evolution.
Also I've seen .swiftinterface was wrong before.
And I appreciate your great work.
I hope this library helps saving build time.

I'm working on this here. https://github.com/giginet/Scipio/pull/49 😄

wow, glad to hear that! Thank you!


Add firebase-admin to the list of dependencies.

This PR adds firebase-admin to the list of build dependencies, and bumps appengineApi and httpClient  versions.

@armiol, PTAL.


Rooms Views Changed

Assign shift

See Rooms

Admin

Coverage remained the same at 95.804% when pulling 85e26ffdbb933530500b1a726348db70a65e77d7 on aljesusg:new_rooms_visual into 001a203b1a4bac1671e2fa5f70725328f37b8b50 on propedeutica:master.


Move LinalgQuantized* passes to GlobalOptimization

These passes are a better fit for GlobalOptimization given they have to
do with Linalg ops. Additionally this turns on the passes for all
frontends now that other frontends are starting to generate these ops
too.

Removed the passes from TOSA, and also moved the passes to GlobalOptimization.


v2 matches

New endpoint:
/v2/matches?count=<SIZE || 60>&locale=<LANG>

Has this replaced the former endpoint? Or just another option?

Sorry about the leak of details. This endpoint is used on the web application to fetch the matches that you currently have.

Cool -- I added it into tinder_api.py


Add breakpoints that have the ability to overwrite variables

I find myself setting breakpoints after a variable is set and then, using the debug console, I'll modify the variable to satisfy an if statement for testing. I think it would be great if there was a way to overwrite variables via breakpoints, similar to how conditional breakpoints work, but not necessarily stop the code execution.
$result = false;

// Add a breakpoint (or whatever you'd call it) with some var overwrite
// the breakpoint would then set $result = true;
if ($result) {
  // do some other stuff
  // maybe add a generic breakpoint
}

This way you could run the code over and over without having to hit the breakpoint, manually change the variable, and then tell the debugger to continue. This would be increasingly more useful as the number of variables you have to overwrite increases.

Using the JavaScript debugger I can set a conditional breakpoint to execute any code (including modifying a variable) there. Don't know if it works for PHP.

Yes, if the debugger you are using supports variable assignments in conditions, then you have the feature already.

Using the JavaScript debugger I can set a conditional breakpoint to execute any code (including modifying a variable) there. Don't know if it works for PHP.

I tried modifying a variable in a conditional breakpoint using PHP, but it doesn't seem to work.

@joshmakar I suggest to file an issue against the PHP extension.


How to authenticate yourself when using websockets

To Whom It May Concern:
Hello, I'm a newbie developer. I'm trying to use this repository to connect to binance, but I don't seem to see how to provide api_key and secret in websocket, and there doesn't seem to be any relevant prompts in the code. I would like to ask how to authenticate?
Sincerely
tiany7

Binance is blocked by the US, so you'll need a VPN before running it.


Tweak highlight range

It seems to be clearer if the highlight range will be tweaked to the method name. Currently it contains dot.
Expected
1.time {}
  ^^^^
Did you mean?  times

Actual
1.time {}
 ^^^^^
Did you mean?  times

I intentionally designed the current behavior to make it clear that it is a method call syntax, but I'm not sure which is better. Does anyone have an opinion?

I would like to close this as I have not received any similar reports. I may reconsider if the underline turns out to be uncomfortable or obviously consufing to many people.


Wsman firmware update task refine

Background
The original WSMAN based job is out of date after SMI service updated its input parameters. And also it is lack of unit test and option schema check. Currently we refine all WSMAN implementation and aimed to integrate SMI service with RackHD and replace the RACADM. We refined the WSMAN work job arch. Now it use the new common WSMAN base job as base classs and WSMAN tool as util to send out request to SMI service.
Detail
Refined the job arch to use WSMAN base job as base.
Refined payload send to SMI service.
Refined input parameter to task.
Add task schema for task parameter.
Add unit test for WSMAN control job.
Add unit test for task schema.
Test Result
Tested pass on Dell R730 server.
wsman-control.js  Unit test coverage: 97%
Review: @yaolingling @anhou @lanchongyizu @AlaricChan

Please add run-test label to trigger Concourse CI.

Please squash the commits


Add an indication that the repository is dirty.

Something like this

It would be nice. If it possible, of course (something tells me that it's impossible).

Was thinking about this myself also. Am I correct in assuming that the number would the number of commits your local branch is behind the remote branch?
Will look into after I have fixed #22

I'm thinking about number of uncommitted files, but your idea nice too.

Only now I noticed that git extenstion for VS shows both numbers.

Oh duh completely forgot about that. In that case I wouldn't want to recreate that functionality I guess


[rocksdb] add rocksdb.optionsfile property

This adds support to run RocksDB with a custom options file.
This also updates the RocksDB Maven artifact version to the latest (6.2.2).

If I have a data file for rocksdb written by version 5, will it still work when I run with the version 6 library?

From looking at the Rocks compatibility strategy and the release log, I don't anticipate any breaking issues moving from 5.11.3 to 6.2.2. Especially since YCSB is currently initializing the RocksDB options using the optimizeForLevelCompaction() helper function and will continue doing so by default, so any DB initialized by YCSB shouldn't depend on any exotic options that got deprecated.
I just tested it myself to confirm (loaded a YCSB DB with 100K records using Rocks 5.11.2, rebuilt YCSB with Rocks 6.2.2 and ran a run workload with no issues).
However, my knowledge of RocksDB internals is minimal, so It would be could if @adamretter or another Rocks maintainer could chime in.

@twblamer I think the version upgrade should be fine.

Fixed a typo and squashed commits.

@adamretter Does the PR look OK to you?

@twblamer It would be good to see a test case.

@adamretter I've added a test, please have a look.


[Improve] fix table name in cdc tests

Description
[Improve] fix table name in cdc tests
InLong Component
InLong Sort
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Fixed in https://github.com/apache/inlong/pull/6173


German translation

Hello,
I've translated "The Twelve-Factor App" into German.
Regards,
Martin Ruopp

Thank you @martinruopp !

Vielen Dank!


Remove TDE api from v5 tag

This PR reverts the TransparentDataEncryption api to an older version as the tests for it in the .Net sdk is failing.
The failed tests are by breaking change (expected) and the old swagger specs cannot meet current requirements.
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

the author added the existing static API back 'cause 2017 TDE APIs have issues and cannot pass the .NET SDK tests.
thus, the breaking changes and corresponding lintdiff errors can be ignored.
.NET SDK errors are also expected because we have not merged the fix (the same author is also working on the .NET SDK fix.)


Ability to unset column sorting

It's common to have tri-states in table design: unset, ascending, descending.
Is your feature request related to a problem? Please describe.
The current pivot table allows users to toggle between ascending and descending sort orders by clicking on a column header. However, clicking a different column header resets the sort order of the previously sorted column. We should allow users to unset a column on the third successive click.
https://github.com/user-attachments/assets/d6fcebe6-9f6b-42cc-bde4-5363ca2c82cb
Describe the solution you'd like
Allows users to easily toggle between ascending, descending, and unset states by simply clicking on the column header.
Additional context
Check the sorting example from Tanstack: https://tanstack.com/table/latest/docs/framework/svelte/examples/sorting
Code reference
Search for enableSortingRemoval in the codebase.

Is the column sorting intentionally limited to only ascending and descending options? Would you have any context? @jkhwu @djbarnwal

I think unsetting a column sort would be a helpful feature and I don't know of any reasons why we don't offer this already. Let's move forward with this, thanks!


Issue from website page Flutter文档

From URL: https://www.flutterchina.club/docs.md

May I ask if Pageview  has positionOffset method?

Hi @ccy1207
you may find the information on PageView in this documentation
Please see https://flutter.dev/community or https://flutter.dev/community/china
for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


Live view not working in Documentation - 404 error

🐛 Bug Report
The live view in docs doesn't seem to be working at the moment. I'm seeing a not found response in Dev tools. See attachment.

Hi @daryllukas
Thanks for raising this!
It is back to normal after redeploy


Is there any way to convert ".t7" into hdf5 format?

Hi,
Thank you for writing this code.
I wanted to use a pre-trained model which is in .t7 format, Is there any way I can convert this into hdf5 format in order to use it in Keras.

Try pytorch, you can use the load_lua function to read the t7 file and get a hashable_uniq_dict, which has two tensor lists named parameters and bnVars.
Then it'll be easy to convert the pytorch tensor into hdf5 format.

Hello @hzli-ucas , can you provide the script that does this operation ? I didn't find load_lua in pytorch. Thanks in advance :)

Hi @MounirB , I think pytorch has removed it from its new version. But you can still find the original .py file by searching "read_lua_file" or "load_lua" within pytorch repository, there are some commits including the file. For example, this one: https://github.com/pytorch/pytorch/blob/c6529f4851bb8ac95f05d3f17dea178a0367aaee/torch/utils/serialization/read_lua_file.py

Hello @hzli-ucas , I am getting this error :
Traceback (most recent call last):
  File "convert_t7_to_hdf5.py", line 574, in <module>
    a = load_lua("../Trained_models/c3d-sports1m-kinetics.t7")
  File "convert_t7_to_hdf5.py", line 571, in load_lua
    return reader.read()
  File "convert_t7_to_hdf5.py", line 542, in read
    typeidx = self.read_int()
  File "convert_t7_to_hdf5.py", line 440, in read_int
    return self._read('i')
  File "convert_t7_to_hdf5.py", line 431, in _read
    result = struct.unpack(fmt, self.f.read(sz))
ValueError: read of closed file

When trying to load a t7 model

@MounirB I don't know, never run into this error. Maybe you can try inserting some code to figure out what's wrong? Like inserting print(f.read(4)) in line 571 or 570 to see if you can successfully read the opened file?


setting onAlert has no effect

Hi, I received the page object and set onAlert method on each page object but that method was never called (I have a log message in that call back function).
See https://gist.github.com/yeukhon/68d807f2407c6306823e
Thoughts?
Thanks

You have to use page.set('onAlert, ...)`


Test-NetConnection vs Test-TcpConnection

I'm curious about the advantages of using your Test-TcpConnection command over Test-NetConnection. I like that your command lets me test multiple ports, but is there anything else? I'd put this information in the help and your readme file.

Will add that reasoning to both the readme and help for the function
itself. In short:

Single host, multiple ports (port scan)
Multiple hosts, multiple ports
Speed: ability to reduce default timeout on scans
Takes pipeline input from Get-ADComputer and sends output to
Get-TlsCertificate (also contained within that module).

There's likely more but that's off the top of my my head. I'll document
them as I remember.
On Tue, May 9, 2023 at 9:09 AM Jeff Hicks @.***> wrote:

I'm curious about the advantages of using your Test-TcpConnection command
over Test-NetConnection. I like that your command lets me test multiple
ports, but is there anything else? I'd put this information in the help and
your readme file.
—
Reply to this email directly, view it on GitHub
https://github.com/anthonyg-1/PSTcpIp/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHGBZJQL4RVCNCBI3GRYP5TXFI6ZFANCNFSM6AAAAAAX3IPD7U
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Pydantic 1.9.1 deepcopy breaks Redis caching, possibly other things

I'm open to the possibility that this should be treated as an issue in Pydantic because it's a breaking change there, and https://github.com/samuelcolvin/pydantic/issues/4184 appears to be a variation of this.
I have a Starlite application which configures its caching as follows (excerpt from my actual app.py):
import redis
import starlite

from .config import settings

cache_config = (
    starlite.CacheConfig(backend=redis.from_url(settings.CACHE_URL))
    if settings.CACHE_URL is not None
    else starlite.app.DEFAULT_CACHE_CONFIG
)

config.settings in this case is a pydantic.BaseSettings instance which reads the Redis URL from an environment variable, if set. The fallback logic is for local development where a Redis instance may not be running.
I recently did an upgrade of my dependency tree which moved from Pydantic 1.9.0 to Pydantic 1.9.1, and my web worker processes now fail to boot. Reverting to Pydantic 1.9.0 resolves this.
The failure occurs at instantiating the Starlite application object:
File /opt/venv/lib/python3.10/site-packages/pydantic/decorator.py:40, in pydantic.decorator.validate_arguments.validate.wrapper_function()

File /opt/venv/lib/python3.10/site-packages/pydantic/decorator.py:133, in pydantic.decorator.ValidatedFunction.call()

File /opt/venv/lib/python3.10/site-packages/pydantic/decorator.py:130, in pydantic.decorator.ValidatedFunction.init_model_instance()

File /opt/venv/lib/python3.10/site-packages/pydantic/main.py:341, in pydantic.main.BaseModel.__init__()

ValidationError: 1 validation error for Init
cache_config
  cannot pickle '_thread.lock' object (type=type_error)

The root of the issue appears to be that in Pydantic 1.9.1, Pydantic defaults to performing a copy.deepcopy() of model members during validation, which in turn fails on encountering any non-pickle-able object (as in the above traceback where it attempts to deepcopy() a Redis client instance). Pydantic 1.9.0 performed only a shallow copy.
This behavior can be disabled by setting the copy_on_model_validation option to a false-y value in the config for a Pydantic model class, or by passing it in the config dictionary of the validate_arguments decorator, and that may be the simplest workaround to apply for now while Pydantic decides what to do about this. It may also be the correct long-term choice since it's likely that non-pickle-able objects, such as caching clients, will be passed in arguments to the Starlite constructor from time to time.
This issue appears to be present in any version of Starlite which decorates Starlite.__init__() with validate_arguments, when using Pydantic 1.9.1 (I've tested Starlite 1.7.3 and 1.3.3), and disappears on reverting to Pydantic 1.9.0.

Ok, thanks for the analysis. Would you like to submit a PR?

If you'd be OK with passing "copy_on_model_validation": False as the workaround, I can put together a PR for it in the next couple days. The tricky part will be the testing -- do you have a preference for a non-pickle-able object to pass to Starlite to verify the fix?

Absolutely

Here's a repro for the pydantic side:
import tempfile
from typing import Any

import pydantic

class Container(pydantic.BaseModel):
    fh: Any

@pydantic.validate_arguments(config={"copy_on_model_validation": False})
def receives_container(container: Container) -> None:
    ...

with tempfile.TemporaryFile() as fh:
    receives_container(Container(fh=fh))

Results in:
Traceback (most recent call last):
  File "/home/peter/PycharmProjects/copy-on-model-validation/main.py", line 17, in <module>
    receives_container(Container(fh=fh))
  File "pydantic/decorator.py", line 40, in pydantic.decorator.validate_arguments.validate.wrapper_function
  File "pydantic/decorator.py", line 133, in pydantic.decorator.ValidatedFunction.call
  File "pydantic/decorator.py", line 130, in pydantic.decorator.ValidatedFunction.init_model_instance
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for ReceivesContainer
container
  cannot pickle '_io.BufferedRandom' object (type=type_error)

I created that as I found this issue: https://github.com/samuelcolvin/pydantic/issues/3284 and wanted a quick test.. and as that issue suggests @pydantic.validate_arguments(config={"copy_on_model_validation": False}) has no effect.
Setting it on the Config object on Container does fix it.

Well, if passing it to validate_arguments doesn't actually work, then I guess I won't try that.
(though when I have some time I'll verify it doesn't work before giving up on that approach)

So whats the solution? we strip validate arguments or we pin to 1.9? Or is there an alternative?

As a user, I'm pinning to Pydantic 1.9.0 until they decide what they're going to do about it. I'm not sure, and I don't presume to tell you, what the best choice is for Starlite -- both pinning and remove validate_arguments seem like they have downsides.

We should probably set copy_on_model_validation = False on CacheConfig.Config to address this specific case, and see if any other issues arise. It's not as if 1.9.1 is a new release, so there's unlikely to be many more similar issues in my opinion.

I just did a rebuild of my app using Pydantic 1.9.1 and Starlite 1.8.1, and does indeed seem to work. Thanks for the quick fix.


KeyError: u'AND'

Expected Behavior
The bot should start
Actual Behavior
Got this error
[07:47:19] Starting PokemonGo Bot....
Traceback (most recent call last):
  File "./pokecli.py", line 381, in <module>
    main()
  File "./pokecli.py", line 68, in main
    bot.tick()
  File "/Users/XXX/Documents/dev/PokemonGo-Bot/pokemongo_bot/__init__.py", line 65, in tick
    if worker(self).work() == WorkerResult.RUNNING:
  File "/Users/XXX/Documents/dev/PokemonGo-Bot/pokemongo_bot/cell_workers/pokemon_transfer_worker.py", line 73, in work
    if self.should_release_pokemon(pokemon_name, pokemon_cp, pokemon_potential):
  File "/Users/XXX/Documents/dev/PokemonGo-Bot/pokemongo_bot/cell_workers/pokemon_transfer_worker.py", line 154, in should_release_pokemon
    if logic_to_function[cp_iv_logic](*release_results.values()):
KeyError: u'AND'

Steps to Reproduce
Use a PTC account, google account seems to work
Other Information
OS:
Git Commit: (run 'git log -n 1 --pretty=format:"%H"' and paste it here)

Are you running master or dev? And pls run  " git log -n 1 --pretty=format:"%H" " and paste the out put here. Also paste your config pls.


[WIP] Flytekit Auth system overhaul and pretty printing upgrade

TL;DR
This PR introduces a new Oauth2 handling system in flytekit, that can be used in non flytekit python libraries that wish to use a standardized flow for flytekit. The standard flow is as defined in the RFC and a few additional supported methods.
The system uses client side - grpc.Interceptors. for fine control on the auth flow. It also introduces exception wrapping and retrying interceptor.
As a last time, it improves the terminal output when using pyflyte. All the output is not distilled and the error is traced correctly. Eventually we could link to docs for the errors.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[ ] Unit tests added
[x] Code documentation added
[x] Any pending items have an associated Issue

Help wanted.
cc @bethebunny / @kazesberger / @ByronHsu / @flixr / @honnix if some of you can test.
Especially @honnix you have a command based auth system

I did a quick test. I managed to run a task via FlyteRemote and I verified that auth token was created and propagated correctly.

I was able to repro the test errors in a docker container (e.g. docker run --rm -it -v $(pwd):/root python:3.10-buster "bash" and make setup && make unit_test).
Installing keyrings.alt makes the tests pass. That said, I'm not sure yet why we should require that package.


Deploy to PyPI

For the time being, only dev releases, waiting for the first tagged release (blocked mainly by #12 and #13).

Apparently PyPI does not accept packages having the following dependency type:
https://github.com/ami-iit/jaxsim/blob/3ec23717926ffbd9cb2cc6ca90d14d31e9c156ba/setup.cfg#L65
I guess this PR remains on hold until the upcoming switch to ami-iit/rod.

I've just extracted the CI part in #24 and rebased this PR on top of that branch, adding only the CD part.

switching the parser to rod has been finalized in #25
rod is finally on PyPI after https://github.com/ami-iit/rod/pull/9

After https://github.com/ami-iit/jaxsim/pull/23/commits/34fa843a876e8393fe554862cc04c9e42745da1c, PyPI can finally accept the jaxsim sdist/wheel! I've just tried to upload a test sdist and a new jaxsim page has been successfully created.
Merging now.


Empty icon mapping

Pull Request
🤨 Rationale
Grouping on an icon value isn't ideal if any of the cells don't have an icon. Specifically, the group row doesn't have a value associated with it and renders only a row count.
It would be nice if we could allow a client to leave a cell blank for certain field values but still have the group rows have a value associated with them. For example, have a column that shows either a spinner or nothing based on whether a task is in progress. When grouping, it would be nice to show a string, such as "Idle", associated with the records that have nothing in progress without cluttering the table with extra icons in cells.
This is the Future Work described in #1869
👩💻 Implementation
Updated the icon column to allow a nimble-mapping-icon to have an undefined icon. In that case, the cell renders nothing but the group row renders only the text associated with the mapping.
🧪 Testing
Manually tested in storybook.
Added new unit tests for having an undefined icon
Updated storybook/matrix tests
✅ Checklist

[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.

@m-akinc, will you buddy these changes for me?


[$500]  mWeb/Safari - Chat  - Cursor isn't seen in the input field when triggering edit mode

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.25-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/33365
Action Performed:
Scenario 1:

Navigate to staging.new.expensify.com ? log in
Navigate to any chat
Send a message and start a thread
Send additional messages
Long tap on a message within the thread
Select "Edit comment"

Scenario 2:

Navigate to staging.new.expensify.com > log in
Navigate to any chat
Send a message
Long tap on the sent message
Select "Edit comment"

Expected Result:
Cursor should be visible in the input field as soon as edit mode is triggered
Actual Result:
Cursor isn't seen in the input field when triggering edit mode
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/445693eb-9a6c-4b2a-b944-3a6318eb8569
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01732e019ea63f840f
Upwork Job ID:<PHONE_NUMBER>922673152
Last Price Increase: 2024-01-15

Scenario 1:
Navigate to staging.new.expensify.com ? log in
Navigate to any chat
Send a message and start a thread
Send additional messages
Long tap on a message within the thread
Select "Edit comment"
Scenario 2:
Navigate to staging.new.expensify.com > log in
Navigate to any chat
Send a message
Long tap on the sent message
Select "Edit comment"

Downgrading to Weekly as not that important. It'll be good to fix though.

@Krishna2323 I can reproduce:
https://github.com/Expensify/App/assets/9133401/39aef470-e417-43fa-9223-a83a72291373

This is still happening now. I'm going to downgrade, but I still think it'd be nice to have a fix here.

Okay, gonna close as we have no proposals and it's a very minor issue.


BUG: scipy test suite sometimes hangs in Slurm job

Describe your issue.
The SciPy test suite sometimes hangs when it's being run in parallel in an environment where resource usage is controlled via cgroups (for example a Slurm job).
Reproducing Code Example
python3 dev.py --no-build --install-prefix test -v -m full --parallel N # with N > 1

Error message
No error messages, test suite hangs: runs for hours and eventually gets killed due to time limit for Slurm job

SciPy/NumPy/Python version and system information
Python 3.11.3
numpy 1.25.1
scipy 1.11.1
pytest-xdist 3.3.1

The culprit here most likely is a bug in pytest-xdist, see also https://github.com/pytest-dev/pytest-xdist/issues/658
Workaround is to use --parallel 1, or not use --parallel at all (default is 1).

It sounds like this issue is closable then.

pytest-xdist parallelism is absolutely terrible, it already starts getting slower with --parallel 4. So I'm not surprised that on a cluster with a potentially large number of cores it hangs completely. I'd say this is a pytest-xdist bug.
Really I think we're waiting for someone to rewrite pytest + common plugins in Rust:)


Rust builds fail with image  20240317.1.0  but previous was fine 20240310.1.0

Description
Rust builds fail with image  20240317.1.0 ❌ but previous was fine 20240310.1.0 ✅ (on same commit)
The current suspect is image ❌ 20240317.1.0
Previous image seems to work fine ✅20240310.1.0
In the release of 20240317.1.0 the only relevant rust note I see is the upgrade of Rustup from 1.26.0 to 1.27.0
Platforms affected

[X] Azure DevOps

Runner images affected

[X] Windows Server 2022

Image version and build link
I know you won't be able to access this builds (private) but we have rust builds on windows for the same commit green on Wednesday (20 march) but failing now.
Failing build here
For exactly the same commit green build here
Is it regression?
I think so
Expected behavior
Rust build should work on 20240317.1.0 too
Actual behavior
Last image fails to build rust
Repro steps
Run rust build for the images provided for the same commit

Adding following is workaround to make our builds work again.
  - powershell: rustup update --force 1.77
    displayName: update 1.77

Hello @FrancescElies. Glad to hear that you have a workaround. Meanwhile we will try to understand what's the problem.

rust 1.77 will be released as a part of the runners next week.

@mikhailkoliada the yaml workaround I posted had version 1.77 because of me doing copy pasta, sorry if that was confusing.
Both images 20240317 and 20240310 have rust 1.76.
In our links I added in the bug description we use 1.76, with one image fails with the other one didn't.
To be clear this issue is about 1.76 and the latest vm image that was released.

I suspect something changed how rust stuff is installed in the image I would bet the same issue will be present for v.177, thus not sure new awaiting-deployment will help.

Hello @FrancescElies . Is problem still persist? If yes, can you please provide minimal repro?

@sergei-pyshnoi

Is problem still persist?

If nothing changed with image 20240317.1.0, then the answer is yes.
If undo the workaround, see here, our build job fails again.

If yes, can you please provide minimal repro?

I have provided you two links of two different builds in time that build the exact same commit, locally builds fine, so everything seems to point out in the direction of image 20240317.1.0.
A minimal repro is a fair request but given that there is not a clear easy way to do that with yaml and private projects this requires a non negligible effort from our side.
In all honesty, we are paying customers and I believe I have provided sufficient evidence that something might be wrong with your latest image.
Minimal repro is build a rust project for both images I provided, I guess the yaml for that is something you could put together.
Summarizing
We have a workaround and we don't feel the urgency for a fix, it's fin if is not high priority for you either. It's obvious that we have done our research before opening this issue and but asking for a minimal repro without showing me that you have done the same at your side feels a bit unfair to me.

More infos
In the links I provided the build fails with
info: syncing channel updates for '1.76-x86_64-pc-windows-msvc'
info: latest update on 2024-02-08, rust version 1.76.0 (07dca489a 2024-02-04)
error: component 'rust-std' for target 'stable-x86_64-pc-windows-msvc' is unavailable for download for channel '1.76'
If you don't need the component, you could try a minimal installation with:

    rustup toolchain add 1.76 --profile minimal

If you require these components, please install and use the latest successful build version,
which you can find at <[https://rust-lang.github.io/rustup-components-history>.](https://rust-lang.github.io/rustup-components-history%3E.)

After determining the correct date, install it with a command such as:

    rustup toolchain install nightly-2018-12-27

Then you can use the toolchain with commands such as:

If you run rustup toolchain list in your latest image you will see 1.76 is missing, the list is empty, thus the error.
I don't have access to your previous image anymore after the latest deployment but I would bet that listing the toolchains will show that 1.76 was avaialable back then.
if you run rustup toolchain add 1.76 the toolchain will be added and everything will work again, thus I doubt there is any kind of problem in the servers where the toolchain is downloaded from.
Please correct me if I see this wrong.

NOTE
You can select the specific rust version adding this file to a rust project.
───────┬────────────────────────────────────────────────
       │ File: rust-toolchain.toml
───────┼────────────────────────────────────────────────
   1   │ [toolchain]
   2   │ channel = "1.76"
   3   │ targets = ["stable-x86_64-pc-windows-msvc"]

After investigation I thinks that is not image related error. You starting gets error just in time when rust transfer stable tag to version 1.77 . So its can possible reason of conflicts while trying to download stable package from 1.76 channel.

Another moment, upcoming Windows-2022 update including 1.77 version of rust tools, so anyway you should keep workaround before you transfer rust project to newer version.

I think the problem is that the readme for win2022 images promises rust 1.76 but the image doesn't provide it.

When you run rustup toolchain list in the image, the list is empty, IMO this means either the readme has wrong description or the image is missing rust 1.76.
Locally if I uninstall 1.76 toolchain, I can reproduce exactly the same error.
There is no way for me to prove that the previous image had rust 1.76 because I can't longer access it after last deployment but I would bet that is the case, and the reason it started failing it's because the new one misses the toolchain specified in the readme.

Hey @FrancescElies!
Current images contain Rust 1.77.0 and Rustup 1.27.0. Correct link to the readme file: https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md

According to the rustup, rustc and cargo:
Default host: x86_64-pc-windows-msvc
rustup home:  C:\Users\runneradmin\.rustup

installed targets for active toolchain
--------------------------------------
i686-pc-windows-msvc
x86_64-pc-windows-gnu
x86_64-pc-windows-msvc

active toolchain
----------------
stable-x86_64-pc-windows-msvc (default)
(timeout reading rustc version)
rustc 1.77.0 (aedd173a2 2024-03-17)
cargo 1.77.0 (3fe68eabf 2024-02-29)

@erik-bershel we have a workaround in place, if I remove it the issue is still there.
We already moved to 1.77, current image says it contains 1.77 but when I run rustup toolchain list I get a different result.

Example build here.
Image: windows-2022
Version: 20240322.1.0
Included Software: https://github.com/actions/runner-images/blob/win22/20240322.1/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20240322.1

We still need to explicitly install 1.77 because in our project we specify the version we want to use.
───────┬─────────────────────────────────────────────
       │ File: rust-toolchain.toml
───────┼─────────────────────────────────────────────
   1   │ [toolchain]
   2   │ channel = "1.77"
   3   │ targets = ["stable-x86_64-pc-windows-msvc"]
───────┴─────────────────────────────────────────────

When list rust toolchains I would expect to see the following but we don't, are my expectations wrong?
> rustup toolchain list
stable-x86_64-pc-windows-msvc (default)
1.77-x86_64-pc-windows-msvc

I suspect this was the case for 20240310.1.0 because our same setup used to work without having to explicitely install the toolchain that was already specified in the readme but we have no way to prove it because we don't have access to that image any more.

Not sure what the issue might be, in the issue description I provided two links to same commit with two different images one passing the other one failing (20240317.1.0) thus I know the problem is not caused because of a change in our code-base.
I wish I could choose the runner image version to see if it's because of the image or some external factor, but that's not possible.
The only related change I can see between both images is the upgrade of rustup 1.26->1.27.
I am not sure how you want to proceed with this one but it seems to me either something has changed on your side or on the rustup side.
@erik-bershel how do you want to proceed with this?

The only related change I can see between both images is the upgrade of rustup 1.26->1.27.

Yep, in that release there was a new rustup. Most likely it was tool behavior that changed.

By any chance could you run rustup toolchain list in the runner image version 20240310.1.0?
@erik-bershel how do you want to proceed with this?

I'll try to. I'll be there later with the information received.

In the meantime. I think there is an error in your .toml.
You wrote next:
───────┬─────────────────────────────────────────────
       │ File: rust-toolchain.toml
───────┼─────────────────────────────────────────────
   1   │ [toolchain]
   2   │ channel = "1.77"
   3   │ targets = ["stable-x86_64-pc-windows-msvc"]
───────┴─────────────────────────────────────────────

But I think that the target and the toolchain is not the same matter. I suppose that you should use x86_64-pc-windows-msvc as a target. This is also reflected in documentation:

Toolchain file description.
Targets description.
Platforms description.

May I ask you to check your build using the next rust-toolchain.toml:
[toolchain]
channel = "1.77"
targets = ["x86_64-pc-windows-msvc"]

We had this wrong in our rust-toolchain since version 1.64, for whatever reason it exploded now that's why we didn't even consider that, maybe the format changed at some point or we had it wrong all the way since the beginning.
Anyways, even if I was convinced the problem was not on our side, as it turns out, it was.
@erik-bershel thanks for your patience and help, issue resolved with your hint about rust-toolchain.toml
Closing.


Make more nodes?

Is it possible to enlarge the model to be more than the 21 nodes used. It was observed in the MRG model that at 51 nodes there is a change in block thresholds, but not much beyond that. This will increase computation time and may not be reasonable considering the longer time scale that potassium accumulation is observed at.

Updates were made to make a 101 node model. https://github.com/joey-kilgore/kaccumulation/commit/f2a01d9c6ad5acc04474591dd99d83368168cd45


removed #contribution-review-process tag

#contribution-review-process tag in the table of contents does not point anywhere.
Closes #1271

[x ] Have you followed the contributing guidelines?
[x ] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

The check had failed, but I'm not seeing it failing due to the change in any complaints to the  CONTRIBUTING.md file contents. Not sure how to proceed.

A link http://progrium.com/blog/2015/12/04/leadership-guilt-and-pull-requests/ disappeared, that's what CI is complaining about. I'll make another PR to fix that.


Is there a way to make subtasks run in sequence?

I've run into an issue with laravel-elixir, where the next task starts before the previous one finishes. It appears it wraps my tasks into dynamically generated ones, so it basically comes down to this:
var gulp = require('gulp');
var runSequence = require('run-sequence');
var fs = require('fs');

gulp.task('default', function() {
    runSequence('t1-wrapper', 't2-wrapper');
});

gulp.task('t1-wrapper', function() {
    return gulp.start('t1');
});

gulp.task('t1', function() {
  return gulp.src('1/1.js')
    .pipe(gulp.dest('2'));
});

gulp.task('t2-wrapper', function() {
    return gulp.start('t2');
});

gulp.task('t2', function() {
  // setTimeout(function() {
    console.log(fs.existsSync('2/1.js'));
  // }, 100);
  return gulp.src('2/1.js')
    .pipe(gulp.dest('3'));
});

Do once npm install gulp && mkdir 1 && touch 1/1.js and before each run do rm {2,3}/1.js.
When I uncomment setTimeout, console.log starts outputting true.
Is there a way to make it work with subtasks?

I have no idea what is going on here.  That example script is a mess.
run-sequence can only work with tasks that are correctly configured to be asynchronous.  They either need to return a promise or stream, or they need to call the callback.  Otherwise they are assumed to be synchronous.
A task that uses run-sequence can use the callback parameter to run asynchronously (example is in the docs).
I have absolutely no idea what you are doing with the "wrapper" functions, but if you need to run an async task outside the normal Gulp dependencies, you can use run-sequence for that (in the form of runSequence('taskName', callback), which will at least block until taskName completes.

Sorry for being unable to come up with a simpler script that reproduces the issue.
Let me try again. What I'm asking here is, "Is there a way to run tasks t1-wrapper and t2-wrapper in sequence, so that t2-wrapper starts after t1 finishes, where t1 is the task started by t1-wrapper?"
I see no way to turn gulp task into a promise or a stream, so callback is indeed the only option I see. And this way it works:
gulp.task('t1-wrapper', function(cb) {
  runSequence('t1', cb);
});

Not sure what you meant by "which will at least block until taskName completes". It sounds as if there are some pitfalls with using it this way.
AFAICS, they are deprecating gulp.run and supposedly gulp.start (which, I guess, never was part of public API). So, using run-sequence must be the best option here. Unless, laravel-elixir can use dependencies for this. My guess here is that nested tasks better reflect what's going on, compared to dependencies. More semantically correct.
The bigger picture is that laravel-elixir introduces its own tasks. They get turned into gulp tasks, which run with run-sequence. And some of these gulp tasks need to call other gulp tasks. And here's why. There's laravel-elixir task called task, which is meant to call some gulp task by name. Simple as that.

What I don't understand is why you have a task that starts a single task.  ie: why is gulp.start being used at all?
If you want to perform some task after a task completes, you can use the built-in Gulp dependencies (which I recommend wherever possible over run-sequence.  run-sequence is only intended to fill in that situation where dependencies won't work).  This looks like gulp.task('t1-wrapper', ['t1'], function() ....
Otherwise, using run-sequence works if you need to run a task and need to know when it completes.

First off, let us get it out of the way, it's not me who does this. It's laravel-elixir. I haven't contributed to this package as of yet. That is, the code I provided in the original post is not what exactly happens. It's what basically happens.
laravel-elixir introduces a level of abstraction. With it you can do:
elixir(function(mix) {
    mix.sass('app.scss')
        .coffee(['app.coffee', 'controllers.coffee']);
});

Under the hood, when you run gulp, this is turned on the fly into 2 gulp tasks, which compile your assets. (default task runs the just generated tasks with run-sequence.) But when you do this:
elixir(function(mix) {
    mix.task('t1').task('t2');
});

It's basically turned into 2 gulp tasks again (the ones I called t1-wrapper and t2-wrapper). But the first task starts gulp task t1, and the second one, t2. Because that's what laravel-elixir's task task is for. It calls some other existing gulp task.
Finally, to answer your question. This might have been implemented with dependencies. Not sure how much more complex is that, if at all. But starting other task seems more semantically correct here from laravel-elixir's point of view. Since it's not really a dependency, it's laravel-elixir's task that runs gulp task.

OK, I don't know what any of this has to do with run-sequence.  My library is very simple, it just starts gulp tasks and waits for them to complete.  If those tasks are incorrectly configured, and they return without a callback, promise, or stream before they are actually complete, how would it know?  How would gulp know?
Don't use laravel-elixir, whatever that is, I guess, or call the inner tasks directly.

I had 2 assumptions in mind, when I started the question: either run-sequence doesn't do its job properly, or laravel-elixir is not properly starting subtasks. It appears to be the latter. Thanks for helping me figure that out. They are supposed to use run-sequence for starting subtasks, as in the example above.
Concerning the workaround, I already has one.


Update cmake version

Existing Sample Changes
Description
Needing to standardize cmake min version to 3.4

It seems like you have a CI failure on oneCCL_Getting_Started that might be related to your change.

It seems like you have a CI failure on oneCCL_Getting_Started that might be related to your change.

I have retracted the update,


Missing wslpath in PATH on syschdemd

Bug description

Having just updated NixOS-WSL for the first time in a while and built a new generation, there is no wslpath in my $PATH, running with syschdemd still instead of native systemd. I have a /bin/wslpath that works, but it is not in my $PATH. This is because #209 removed the wrapper from systemPackages, and I believe that this still works under native systemd, due to https://github.com/nix-community/NixOS-WSL/blob/main/modules/wsl-distro.nix#L199 inheriting all of $PATH, which syschdemd does not do, especially as wsl -e /usr/bin/env reports PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib: before my Windows paths, which includes /bin.
To Reproduce
Steps to reproduce the behavior:
Build an installer from main, install as a new temporary distro, as the configuration of the installer does not use native systemd, see that there is no wslpath command if you try to run it, but /bin/wslpath exists and works.
Expected behavior

A working wslpath on syschdemd.

Cleaning up installer files...
finding garbage collector roots...
removing stale link from '/nix/var/nix/gcroots/auto/6yfbrv8wfkyl40wq6827lamr9m29z7wg' to '/build/nix/var/nix/profiles/per-user/root/channels-1-link'
removing stale link from '/nix/var/nix/gcroots/auto/zxi8v969la5n36bg7gs016wgcif4qjhp' to '/build/nix/var/nix/profiles/system-1-link'
deleting garbage...
deleting '/nix/store/vzdmnirlszj446barmaiyv1mkla89lln-wsl-prepare'
deleting '/nix/store/qk5j2w5901d2qlp535a0z3acm6fmg3p6-tarball'
deleting '/nix/store/96vxkz49y5cnnkzfgln1nksbh0kmkwsz-installer.sh'
deleting '/nix/store/khqypqm75yd71p9xn143r528jf12r7zw-source'
deleting '/nix/store/0kmxry5la971ki1gd5zzfyqq2vq1qa7l-busybox-1.35.0'
deleting '/nix/store/2y4fz7rkdzf6rmrb1016rznwj9gg93yw-pv-1.6.20'
deleting unused links...
note: currently hard linking saves -0.00 MiB
6 store paths deleted, 367.67 MiB freed
Optimizing store...
4.63 MiB freed by hard-linking 3119 files

[nixos@nixos:/]$ wslpath
wslpath: command not found

[nixos@nixos:/]$ ls /bin
mount  sh  wslpath

[nixos@nixos:/]$ /bin/wslpath
/bin/wslpath: Invalid argument
Usage:
    -a    force result to absolute path format
    -u    translate from a Windows path to a WSL path (default)
    -w    translate from a WSL path to a Windows path
    -m    translate from a WSL path to a Windows path, with '/' instead of '\'

EX: wslpath 'c:\users'

[nixos@nixos:/]$

Did you restart WSL after the installation?

wsl -e /usr/bin/env

Please run commands interactively, directly running them through WSL is usally flaky but should work better since #234.

I first ran into this issue with my older install, but as I said, this happens with a fresh install of an installer from main. I ran that command explicitly to show the default value of PATH from WSL and that it contains /bin before NixOS/NixOS-WSL do anything, but that path entry is not kept on syschdemd on purpose, while native-systemd behaves differently. A wsl --shutdown doesn't make wsl -d nixostmp do anything different the second "boot", there's still no wslpath.

I think we wanted to remove syschmd in the future anyway since native-systemd fixes some bugs, like this one.

It doesn't work for me with nativeSystemd option as well. With latest installer from main there is no /bin in path.
Command wsl -d nixos -e /usr/bin/env shows its in path though

I think I have a related issue - it's completely broken the normal boot process
PS C:\Users\ariel> wsl
/nix/store/701bd06kvch5kqzdap5rdcwdi7pxv5mc-syschdemd/bin/.syschdemd-wrapped: line 74: getent: command not found
PS C:\Users\ariel> wsl -e /usr/bin/env
HOSTTYPE=x86_64
LANG=en_US.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/PowerShell/7:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0/:/mnt/c/Windows/System32/OpenSSH/:/mnt/c/Program Files (x86)/dotnet/:/mnt/c/Program Files/dotnet/:/mnt/c/Windows/system32/config/systemprofile/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/Program Files/usbipd-win/:/mnt/c/Program Files/PowerShell/7/:/mnt/c/Users/ariel/scoop/apps/vscode/current/bin:/mnt/c/Users/ariel/scoop/apps/gpg/current/bin:/mnt/c/Users/ariel/scoop/apps/openssl/current/bin:/mnt/c/Users/ariel/scoop/apps/corretto-jdk/current/bin:/mnt/c/Users/ariel/scoop/apps/python/current:/mnt/c/Users/ariel/scoop/shims:/mnt/c/Users/ariel/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files/AESCrypt:/mnt/c/Users/ariel/AppData/Local/Keybase/
TERM=xterm-256color
XDG_RUNTIME_DIR=/mnt/wslg/runtime-dir
DISPLAY=:0
WAYLAND_DISPLAY=wayland-0
PULSE_SERVER=unix:/mnt/wslg/PulseServer
WSL2_GUI_APPS_ENABLED=1
WSLENV=
WSL_INTEROP=/run/WSL/101987_interop
NAME=nixos
HOME=/root
USER=root
LOGNAME=root
SHELL=/usr/bin/env
WSL_DISTRO_NAME=nix
PS C:\Users\ariel>

I got the same issue . The first startup after import is fine, any subsequent boot results in the same error:
PS D:\> wsl --import NixOS .\NixOS\ nixos-wsl-installer.tar.gz --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

Cleaning up installer files...
finding garbage collector roots...
removing stale link from '/nix/var/nix/gcroots/auto/zxi8v969la5n36bg7gs016wgcif4qjhp' to '/build/nix/var/nix/profiles/system-1-link'
removing stale link from '/nix/var/nix/gcroots/auto/6yfbrv8wfkyl40wq6827lamr9m29z7wg' to '/build/nix/var/nix/profiles/per-user/root/channels-1-link'
deleting garbage...
deleting '/nix/store/bwlcjak9cgn2f359g6w9vxc64ys0qypc-tarball'
deleting '/nix/store/hvlyywx5lqnk3bjj8d8plc4y5cwg2xj6-pv-1.6.20'
deleting '/nix/store/n9znd98f2jy1x4qpliy5znlnz29xk2pq-installer.sh'
deleting '/nix/store/q4rjlwqgivvj9k5awpkk6bwpqbqx3k9n-wsl-prepare'
deleting '/nix/store/fzigg1lbrsi1yf9l0lx3zvyld4p6c88w-source'
deleting unused links...
note: currently hard linking saves -0.00 MiB
5 store paths deleted, 1217.51 MiB freed
Optimizing store...
204.82 MiB freed by hard-linking 44755 files
/etc/set-environment: line 13: warning: setlocale: LC_TIME: cannot change locale (de_DE.UTF-8): No such file or directory
[zplug] Start to install 1 plugins in parallel

 ✔  Installed!            djui/alias-tips

[zplug] Elapsed time: 0.9941 sec.
 ==> Installation finished successfully!
❯ exit
PS D:\> wsl -d NixOS
/nix/store/ixw2c5hira8if9f2hvgs6pwhp086as3b-syschdemd/bin/.syschdemd-wrapped: line 74: getent: command not found
PS D:\> wsl -d NixOS -e /usr/bin/env
HOSTTYPE=x86_64
LANG=en_US.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/Oculus/Support/oculus-runtime:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0/:/mnt/c/Windows/System32/OpenSSH/:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/Program Files/NVIDIA Corporation/NVIDIA NvDLISR:/mnt/c/Program Files/dotnet/:/mnt/c/Program Files (x86)/IVI Foundation/VISA/WinNT/Bin/:/mnt/c/Program Files/IVI Foundation/VISA/Win64/Bin/:/mnt/c/Program Files (x86)/National Instruments/Shared/LabVIEW CLI:/mnt/c/Program Files (x86)/IVI Foundation/VISA/WinNT/Bin:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files/Go/bin:/mnt/d/TDM-GCC-64/bin:/mnt/c/Users/joern/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/joern/go/bin
TERM=xterm-256color
XDG_RUNTIME_DIR=/mnt/wslg/runtime-dir
DISPLAY=:0
WAYLAND_DISPLAY=wayland-0
PULSE_SERVER=unix:/mnt/wslg/PulseServer
WSL2_GUI_APPS_ENABLED=1
WSLENV=WT_SESSION::WT_PROFILE_ID
WT_SESSION=c98f5d02-6c32-4a19-b836-b3d741464406
WT_PROFILE_ID={61c54bbd-c2c6-5271-96e7-009a87ff44bf}
WSL_INTEROP=/run/WSL/982_interop
NAME=nixos
HOME=/root
USER=root
LOGNAME=root
SHELL=/usr/bin/env
WSL_DISTRO_NAME=NixOS

My config from which I built the installer from is here: https://github.com/joernweissenborn/nixos-config/blob/main/hosts/tina-wsl/default.nix
I already set stateVersion of my nixos to 23.05, could that be an issue?

I think enabling native systemd fixed it for me
https://github.com/arichtman/nix/blob/2cd654bff9d11cbdf767412845d5dc97c311e01c/modules/nixos/wsl/default.nix#L44

I think enabling native systemd fixed it for me
https://github.com/arichtman/nix/blob/2cd654bff9d11cbdf767412845d5dc97c311e01c/modules/nixos/wsl/default.nix#L44

That didn't work for me, now I get immediate crash:
PS D:\> wsl --import NixOS .\NixOS\ nixos-wsl-installer.tar.gz --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.
PS D:\> wsl -d NixOS
Catastrophic failure
Error code: Wsl/Service/CreateInstance/E_UNEXPECTED

I see you use docker, maybe I should try that.

I started seeing this issue as well after updating nixpkgs and running sudo nixos-rebuild switch:
• Updated input 'nix-config/nixpkgs':
    'github:NixOS/nixpkgs/3ae20aa58a6c0d1ca95c9b11f59a2d12eebc511f' (2023-06-23)
  → 'github:NixOS/nixpkgs/3c7487575d9445185249a159046cc02ff364bff8' (2023-07-06)

After the switch I get when trying to launch a WSL shell:
/nix/store/0q78jsg9h19slxaxnjhwvjm6x42fygcj-syschdemd/bin/.syschdemd-wrapped: line 74: getent: command not found

[process exited with code 127 (0x0000007f)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

If I revert back to the previous nixpkgs version everything works fine again.
I can fix the issue by enabling native systemd, but then instead of getting logged in as my user, I get logged in as root when starting a new shell and if I su to my user, my user doesn't have permissions to execute anything, e.g. ls etc.

That mirrors my experience exactly. I updated my dependencies, it broke on getent, enable native systemd and it logged me into rood. Fully terminate the VM and it works fine now.

Here's a potential workaround for the getent error:
PS C:\Users\atnnn> wsl
/nix/store/701bd06kvch5kqzdap5rdcwdi7pxv5mc-syschdemd/bin/.syschdemd-wrapped: line 74: getent: command not found
PS C:\Users\atnnn> wsl --shell-type none /bin/sh -c '/nix/var/nix/profiles/system/sw/bin/ln -s /nix/var/nix/profiles/system/sw/bin/getent /bin/getent'
PS C:\Users\atnnn> wsl
[nixos@nixos:/mnt/c/Users/atnnn]$

It seems that getent was moved out of the glibc.bin derivation on unstable. It should be fixed by #267.
As for wslpath missing from PATH: It will be fixed with the upcoming syschdemd replacement, so it doesn't really make sense to fix it for the soon to be replaced version


[Feature] System analysis

Objective
Analyze and understand what we should implement.
Key results

Activity diagram.
Data model and data flow.
Top most / overview system design.
Separate the contexts and list the key features.


player related end points not working, return server error

please confirm that player related API calls are still allowed by the server. I'm getting 403 Client Error: Forbidden for url
playerdashboardbygeneralsplits

@Peppershaker This data appears to only be available in aggregate terms currently via headerless calls and we are working on a fix.
I've tried http://stats.nba.com/player/#!/203919/stats/advanced/ and the webbrowser makes a call to http://stats.nba.com/stats/playerdashboardbygeneralsplits?DateFrom=&DateTo=&GameSegment=&LastNGames=0&LeagueID=00&Location=&MeasureType=Advanced&Month=0&OpponentTeamID=0&Outcome=&PORound=0&PaceAdjust=N&PerMode=PerGame&Period=0&PlayerID=203919&PlusMinus=N&Rank=N&Season=2015-16&SeasonSegment=&SeasonType=Regular+Season&ShotClockRange=&VsConference=&VsDivision= in order to render the information.
However, If I take that call and try to make it on it's own, I get a "referral denied error" and am told I do not have permission to access the server. This is different than the other calls in the package that return JSON data sources.

thanks dude! also apparently the log level information are gone now. do you have any old files just so i can have a look what i missed out on? I just started looking at this script. Thanks again!

@Peppershaker  Here is a small sample of shot data that used to be available. Sample Data.xlsx

thanks dude, but sad to see that go...

should be fixed now outside of what the NBA blocked


Where should  libdxcompiler.so be placed?

The documentation mentions you should have the file on your environment, but merely placing it at the root of the project does not seem to allow the crate to find, it. It would be helpful for the error message to print the absolute path to where it is trying to find the .so/

On Linux the .so is loaded from the working directory:
https://github.com/Traverse-Research/hassle-rs/blob/ddcdfc6032657b2b8d75d1bc55719d186ad7e55e/src/wrapper.rs#L468-L481
In general, that's the location cargo run is invoked from. But you can also pass a custom directory or whole path to Dxc::new(Some(PathBuf::from("some/path/to/libdxcompiler.so"))).

I diged down the error stack and figured I was misreading the error message. The problem was I needed to install this:
sudo apt install libtinfo5
I will piggy back off this thread however. I managed to get things running on debug mode, but on release I get a segfault:

Thread 1 "02_skinned_mesh" received signal SIGSEGV, Segmentation fault.
0x00007fffde9e8d69 in hlsl::DxcCreateBlobEncodingFromBlob(IDxcBlob*, unsigned int, unsigned int, bool, unsigned int, IMalloc*, IDxcBlobEncoding**) () from ./libdxcompiler.so

This is the invocation:
 let spirv = unsafe {
            compile_hlsl(
                &name.as_str(),
                &source.as_str(),
                "main",
                "cs_6_5",
                &vec!["-spirv"],
                &vec![],
            )
            .unwrap()
        };
        ```

        I have not modified the .so nor the library.

I diged down the error stack and figured I was misreading the error message. The problem was I needed to install this:

Oh right, yes, libdxcompiler.so provided by Microsoft still links against ancient ncurses5, which is gone on modern Linux distros and the latest Ubuntu.

 I managed to get things running on debug mode, but on release I get a segfault:

That is quite strange, the only reason I can think of is a mismatch between hassle-rs and DXC versions since there was an ABI break (for the better, to fix wrong vtable layout). See also the support table at https://github.com/Traverse-Research/hassle-rs#supported-dxc-versions-on-non-windows. However, then it also shouldn't have worked in debug mode.

I originally got the so from embark, getting directly from the DXC gh page allows for proper error messages. i assume they compiled the library and stripped some stuff out of it. Sorry for bugging.

Kajiya has the compiler.so file, but using it was causing segfaults on release.

Yeah Kajiya is still on 0.5 even:
https://github.com/EmbarkStudios/kajiya/blob/5a124d58b8fc8795d37c933168c4ce98e986ce4c/crates/lib/kajiya-backend/Cargo.toml#LL21

I am getting confused about something. The DXC object is initialised inside compile_hlsl which does not take the path as a parameter. As a user I don;t know how to change the location of where the library will look for the so, it seems hard coded into the API by being encapsulated in the compile function.

Yes we haven't updated the compile_hlsl() signature because it's already quite packed and only useful for one-off compilations, in most cases you want to load the Dxc library and construct the compiler and library only once and reuse it for many .compile() calls. That said, feel free to PR this addition to the function :)
At the same time the return value of .compile() (and friends) is terrible, and I have a few branches lying around that try to simplify and improve the return facility (i.e. always providing error context if available, regardless of function nor result.get_status() HRESULT etc), but nothing definitive yet. At least compile_hlsl() encapsulates this in some way, but I'd rather move that into .compile().


refactor to add multiple driver, adding memory store

Attempt to fix #35

@tuananh
Hi, you might need to update the files field in  package.json as well to include new files:
"files": [
  "index.js",
  "limiter/memory.js",
  "limiter/redis.js",
]

Otherwise i guess it would cause problem when releasing to npm repo.

LGTM if we can update files field in package.json just as @towertop said :)

I will try to merge this and release a new version within this/next week :)

Hi @haoxins , do you have any idea when you'll have time to merge this? Thanks!

it seems that no any broken change, will publish a new MINOR version

v4.3.0


domain separator for address, objectID, transaction

IMPORTANT NOTE: this Issue been superseded by this https://github.com/MystenLabs/sui/issues/9544 which also results to no collisions between addresses and objects and it's not requiring breaking changes to address generation (so wallets, custodians and co are not affected.
THIS ISSUE HAS BEEN CLOSED (NOT IMPLEMENTED) please see for what goes into Sui 3.1 https://github.com/MystenLabs/sui/issues/9544

Now that we moved to 32 bytes and we're switching everything to blake2b (which is a breaking change already) we can actually mangle the last byte of the hash output and set it to:
0x.....00 for objectID (all types of objects incl dynamic and module objects)
0x.....01 for address
0x.....02 for transactionID (although we prefer base58 here and won't help a lot we'll try to enforce distinguishably here as well)
cc: @tnowacki @amnn @tzakian @dariorussi @oxade and @srinath-mysten for visibility. We might require to enlist all special objects and addresses in our system to ensure we don't break the new rule (will sync up in Move channel discussions).
NOTE: we decided to mangle the last byte (vs the first) so this change remains compatible with some fixed objects we have across our system (ie special objects at 0x01 0x2 etc).
QQ: if Move devs believe we should do provide extra distinguishability even between object types (ie modules to have another suffix Vs regular objects, please request in this GH Issue asap).
This will significantly help UI to distinguish between queryable types (typically tx, object, address), ie explorer can very quickly decide what type of search you need (@pchrysochoidis) + help as a natural domain separator (so even humans can tell the difference), wallets will know what the destination type is when we allow "transfer to object",  maybe Move development and IDEs (@awelc) can use that info for better experience.

We're not going to apply this solution for domain separation between addresses and objects. The final implementation is tracked by issue https://github.com/MystenLabs/sui/issues/9246


CUDA

Can you please make it possible to create .cu files (with syntax highlighting, etc).
Thank you.

VSCode Version: Code 1.9.1 (f9d0c687ff2ea7aabd85fb9a43129117c0ecf519, 2017-02-09T00:26:45.394Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

cpptools
ms-vscode
0.10.1

Steps to Reproduce:

Did you know we have a pretty big extension Marketplace? This sounds like a great new extension idea!

Hi, Joao
I did not know. I am very very new to VS Code.
Do you think I can expect the extension to be available soon?

You can actually make it yourself. 👍


Build failed - v 0.60 with Microsoft.EntityFrameworkCore.SqlServer

Hi,
When I tried to build the Blazor (standalone) Version 0.6.0 after installing Microsoft.EntityFrameworkCore.SqlServer the build is failing.

Steps to reproduce

Create a new Blazor (standalone) app
Install Microsoft.EntityFrameworkCore.SqlServer
Build the solution to see the error.

Verified in Visual Studio 2017 and Visual Studio code . Please help.
Thanks.

the user interface may not have any dependency on the database.
https://youtu.be/_lwCVE_XgqI

Indeed, I don't expect Microsoft.EntityFrameworkCore.SqlServer to be supported under WebAssembly.
Generally it wouldn't be applicable to use that directly from the client, because doing so would imply your database allows direct incoming connections from arbitrary clients. This is typically a serious security risk.
The normal architecture is to have your clients invoke API endpoints on a web server, and for the web server in turn to make connections to your SQL database.


Use 5 bits per character for sid, to have valid cookie value

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues
#248

Not sure why 6 bits per character was used for sid_bits_per_character configuration for the session. As pointed in php documentation 5 bits is recommended value for most environments. Anyways 6 bits per character was introducing new characters which are invalid for the cookie value, by making session id a bit more stronger.
Another way to fix this issue is to just urlencode() session id in SessionMiddleware, but I prefer not to introduce additional overhead there.
P.S. I'm planning to review Session class and session handling a little bit later on, and will make sure to have a way to use 6 bits per character if the user wants (but will keep 5 as default as recommended by php).

5 bits should be enough. 6 was used just in case...

Thanks!


Update README with correct semantic ui package

The now deprecated nooitaf:semantic-ui package was replaced in this commit: https://github.com/matteodem/meteor-boilerplate/commit/51a14a99c760fee298cdc3b387f73053defb835f
The README should be updated to reflect this.

Thank you


feat(speech): add listen and speak creation operators

Hey! 👋
This is a migration of rxjs-tts and rxjs-stt libraries
This PR adds support for Web Speech API:

fromSpeechRecognition creation operator that wraps SpeechRecognition
originally this method was called listen

and speak creation operator that wraps SpeechSynthesis
couldn't come up with a better name: fromSpeechSynthesis doesn't sound exactly right since it's rather a generation, not subscribing for events

Both have dedicated README-s with basic API examples. I suggest either including those in the root README, or linking child readmes from the root.
Please, review 🙂
Thanks

Had to update prettier config to match linter: drop parenthesis on arrow functions
And set .md to be ignored by prettier — as we often need custom formatting in code samples we give in READMEs

The build is still failing on runners with node v < 12 due to globalThis usage (which is kinda expected as only 12+ versions support it)
Why do we need tests run on different node versions: IMO, one latest version should be enough since the lib is targeted on web platforms rather then node?
@niklas-wortmann please, advise what to do with failing build.

Hi sorry for the late reply, thanks for your contribution. I really appreciate it. To be honest, I am poorly prepared for contributors right now, so the experience kinda sucks. I am really sorry about this. Please don't mind the failing pipeline I will take care of this.

Can you also help with naming?
I feel like both either should be listen/speak or fromSpeechRecognition/fromSpeechSynthesis. What do you think?

I actually like listen and speak, let's start with that and see how it goes

@kosich could you do me the favor and rename the operators as discussed, when you pushed those changes, I would be extremely happy to merge this pr.

Hey, Jan-Niklas! I'm sorry about this delay. I was procrastinating and postponing testing that FF delay.
I've tried some scenarios on FF and Chrome and it seems that 4ms delay was useless so I removed it.
Not sure why I added it in the first place 🤷♂
And I've renamed the speech-to-text fn back to listen.
CI on node 13 & 12 passes, node 11 & 10 fails (as expected).
The PR is ready for merge
Please, ping me if I missed something 🙂

Whooop woop thanks a lot for your work! I appreciate it a lot!

🙌 Glad to collaborate 🙂
I will deprecate my packages in favor of rxjs-web
Now that this is merged, I'd also suggest redesigning README.md for better library consumer landing / docs navigation.
(well, and to make it sexy)


Add conceptual content to Visualize data with the InfluxDB UI

Update the Visualize data with the InfluxDB UI doc to say the UI is automatically installed with influxdb, and include url to access. "With InfluxDB running, open localhost:8086 to access UI."
Feedback: There is no information here on whether the UI comes already installed with InfluxDB or how to access it. I'm working with an Influx instance set up by somebody else in a Docker container and need to know how to see whether the UI is installed, and if so how to launch it.

oops didn't see https://github.com/influxdata/docs-v2/issues/4494
will close this

add somethign like this:


html-minifier high security vulnerability

# npm audit report

html-minifier  *
Severity: high
kangax html-minifier REDoS vulnerability - https://github.com/advisories/GHSA-pfq8-rq6v-vf5m

node_modules/html-minifier
  vite-ssg  >=0.5.0
  Depends on vulnerable versions of html-minifier
  node_modules/vite-ssg

How would you go about swapping these if using NPM, since it's a dependency for a dependency?

Hi, Kangax html-minifier has no update on npm for 5 years. From this issue kangax/html-minifier#1135 some people recommand to use a fork https://www.npmjs.com/package/html-minifier-terser

Exactly! Thank you as I was swinging by here to bring over this comment link:
https://github.com/kangax/html-minifier/issues/1135#issuecomment-2110516434
I think this might have to be solved by switching the deps in this project. I'm not sure how to do that yet though, as antfu uses/used a different environment that I don't work with much as an old schooler... so I never really got over the initial learning curve to even try and help out with this project constructively. :(
If any one can send me a tut link for this flavor of a local development stack used here in vite-ssg, i can try to carve out an afternoon to finally wrap my head around it and then take a stab at swapping out the vulnerable dep for the html-minifier-terser one that's being maintained more.
Otherwise, cheers and happy hacking, everyone!

How would you go about swapping these if using NPM, since it's a dependency for a dependency?

The first thing to try in a downstream repo dependent on this repo, would probably be this approach:
https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides
Note, have not tried that yet though. But this would be the path of least resistance, theoretically. cheers!


mpg123: Refactor, 1.26.5 -> 1.28.2

Motivation for this change
Started out as a small change to only add audio support on Darwin, turned into a slightly bigger refactoring & bump.
Dunno how to test mpg123 itself but I tested libout123 via sidplayfp:
nix-build -E 'with import ./. { }; sidplayfp.override { out123Support = true; }'
curl -Ls 'https://hvsc.csdb.dk/MUSICIANS/L/Linus/I_Dug_Some_Graves_Youll_Never_Find.sid' | ./result/bin/sidplayfp -

JACK errors are fine since I'm not running a JACK server. I don't get these messages on macOS despite it loading the JACK module, not sure if something's borked there or if it just fails silently instead.

CC @Radvendii I touched your changes for cross-compiling to Windows abit without testing, I think everything should still be fine?

stdenv.targetPlatform AFAIU is mostly for stuff like compilers that produce further binaries while stdenv.hostPlatform should be correct in this case, see https://nixos.org/manual/nixpkgs/stable/#ssec-cross-platform-parameters
restricting alsa-lib to isLinux makes more sense to me than !isDarwin && !isWindows

Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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

[x] Fits CONTRIBUTING.md.

We can target master here.

We can target master here.

Done, sorry for all the automatic review requests.

It's too large for me to run a nixpkgs-review on, maybe you can give it a try?

Result of nixpkgs-review pr 134349 at 4f4a9ca1 run on x86_64-linux 1

4 packages marked as broken and skipped:

impressive
odpdown
termplay
vdrPlugins.xineliboutput

1 package failed to build:

worldofgoo

297 packages skipped due to time constraints:

Sylk
_1oom
_20kly
adapta-gtk-theme
ahoviewer
altair
anki-bin
appimage-run
apple-music-electron
aravis
...

101 packages built successfully:

SDL2_mixer
_90secondportraits
abbaye-des-morts
alarm-clock-applet
audio-recorder
baresip
bashburn
blobwars
brasero
brasero-original
bubblemail
byzanz
cataclysm-dda
chromium-bsu
cozy
dablin
dir2opus
evince (gnome.evince)
farstream
fheroes2
freerdp (freerdpUnstable)
gmrender-resurrect
gmu
gnome-network-displays
gnome.cheese
gnome.gnome-music
gnome.gnome-shell (gnome.gnome_shell)
gnome.gnome-sound-recorder
orca (gnome.orca)
gnome.sushi
gnome.totem
yelp (gnome.yelp)
gradio
gscrabble
gspeech
gst_all_1.gst-plugins-good
haskellPackages.mpg123-bindings
haskellPackages.sdl2-mixer
instead
jumpnbump
kaidan
kazam
lagrange
libextractor
libsForQt5.kamoso (libsForQt515.kamoso ,plasma5Packages.kamoso)
libsForQt5.phonon-backend-gstreamer (libsForQt515.phonon-backend-gstreamer ,plasma5Packages.phonon-backend-gstreamer)
lollypop
love (love_0_10)
love_0_7
love_0_8
luakit
lutris-unwrapped
mailnag
mailnagWithPlugins
mar1d
methane
mousai
mp3gain
mpg123
mrrescue
nottetris2
nxengine-evo
nyxt
opendune
orthorobot
pantheon.elementary-camera
pantheon.elementary-videos
parlatype
peek
picard
pidgin
pithos
python38Packages.pygame
python38Packages.pysdl2
python39Packages.pygame
python39Packages.pysdl2
qt-video-wlr
qutebrowser
qxmpp
rapid-photo-downloader
recapp
renoise
rimshot
rocksndiamonds
sfrotz
sienna
solfege
sound-juicer
spice-gtk
split2flac
squeezelite
taisei
trackballs
transcribe
uget
ultrastardx
vapor
vgmstream
vocal
whatsapp-for-linux
xneur

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


PanDat.init uses defaults to handle missing columns

Pretty sure this is consistent with TicDat.init if the data is provided as dicts with inner data row dicts.
I think its fair for one difference between PanDat and TicDat is the use of default values, with PanDat being able to populate primary key fields with defaults and TicDat being unable to do so.

Look for  fill_missing_fields in the create_pan_dat functions. I think we just want to make those default to True, and make sure they are everywhere.

PanDat init handled with d30fa7b

Looks like the TicDatFactory readers scream on missing fields, so thats fine default behavior.


Increase GPT4o context size budget

Is there any server-side changes that we need to make here? If nobody knows from the top of their head, I will check it myself before merging.
See: https://nian.llmonpy.ai/ on data for gpt4o recall
Test plan

CI will test

No other backend concerns. Showtime! https://sourcegraph.slack.com/archives/C05497E9MDW/p1715878673939979?thread_ts=1715851421.420119&cid=C05497E9MDW


Question about repeated images correspond to different labels.

Hi, thanks for your open-source!
I'm a little confused about the dataset. For some images containing multiple targets, the dataset chooses to duplicate the images and each one corresponds to a different individual label as shown in the Fig. I don't think this one-to-many labeling makes sense, how did you solve this problem in your implementation? Thxs!

Here's one example.


[Bug] Search for references error when no definition of the searched symbol is found

This happens when searching for references, but no definition is found (maybe because server has no search definition capabilities):
Error executing vim.schedule lua callback: ...k\packer\start\navigator.lua\lua\navigator\reference.lua:156: attempt to get length of local 'result' (a nil value)
stack traceback:
	...k\packer\start\navigator.lua\lua\navigator\reference.lua:156: in function 'handler'
	...\packer\start\navigator.lua\lua\navigator\lspwrapper.lua:159: in function 'handler'
	...\MEGA\Portable\Neovim\share\nvim\runtime\lua\vim\lsp.lua:1025: in function 'cb'
	vim/_editor.lua:256: in function <vim/_editor.lua:256>

The culprit could be here, when looking for the definition of the symbol:
https://github.com/ray-x/navigator.lua/blob/d990da84a6c267bd8684535d392e551333d7a919/lua/navigator/reference.lua#L156
If result is nil, then the error occurs. A fix could be made to handle that case.

This seems to fix it, but I'm not sure it would be the best/correct way:
if result ~= nil then
  for i = 1, #result do
    if result[i].range == nil and result[i].targetRange then
      result[i].range = result[i].targetRange
    end
  end
end

fixed.


⚠ Contemporanea B2B has degraded performance

In 25615a3, Contemporanea B2B ($SITE_CNTMB) experienced degraded performance:

HTTP code: 200
Response time: 12659 ms

Resolved: Contemporanea B2B performance has improved in bfb8242.


Increment version to next development iteration, v2.1.1.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Increment version to next development iteration, v2.1.1.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

🎉  https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/client/opensearch-java/2.1.1-SNAPSHOT/

Thanks!
Also, did we cut a 2.1 branch for 2.1.0 release?

No, do we need to? We have a tag, could turn it into a branch as needed.


Invoking Stored Procedure and get OUTPUT

Hi guys,
Perhaps this is not a bug and you may have a trick for it.
I have a stored procedure on mysql database where I have IN and OUT arguments.
I am invoking that stored procedure with knex.raw() but how do I get the OUT arguments?

There is older issue about this. I cannot remember if there was some problems in knex side with this. Passibg out arguments depends on database driver. Have you looked driver’s docs?

@elhigu yes. That is why I am using the raw() method. But may be there something more specific that I didn't see.
CALL StoreProcedure('value1', 'value2', @a);
SELECT @a;

If I would run the query directly on my Workbench the code above works. I am trying to check how I can create the @a and get its value in one call to raw().
I am using this:
const a = knex.raw("call StoreProcedure('value1', 'value2');");
But this way makes MySQL complain about the number of my arguments. Naturally.

I found the solution:
const val = await knex
    .raw("call insertCompetition('value1', 'value2', @a)")
    .then(val => return JSON.stringify(val)))
    .catch(err => console.log(err));