How to train model with my GPU

Hi,
I just want to know how can I train my DRL model with GPU. (to speed up the training process)
Thank you!

not possible

not possible

stable-baselines of tf1.14 can support GPU, but we switched to stable-baselines3 with PyTorch, still waiting for the TF 2.0 version.

stable-baselines of tf1.14 can support GPU, but we switched to stable-baselines3 with PyTorch, still waiting for the TF 2.0 version.

there are TF 2.4 here

there are TF 2.4 here


Multi-repository support for Spark/Scala code

Decide how to share *.proto files and swagger.yml between the main lakeFS repository and client repositories.

What do other people do?

https://www.bugsnag.com/blog/libraries-for-grpc-services says "just build and publish a separate library for each language" -- overkill.
https://medium.com/namely-labs/how-we-build-grpc-services-at-namely-52a3ae9e7c35 says to keep proto def files in a single repo and then add a bunch of tooling.
https://medium.com/building-ibotta/building-a-scaleable-protocol-buffers-grpc-artifact-pipeline-5265c5118c9d is already on top of a monorepo; still use e.g. lerna to manage their subdirectories there.  (Not needed by us, plus we already decided to do multirepo for reasons)

https://github.com/stormcat24/protodep is a "[d]ependency tool for Protocol Buffers IDL file (.proto) vendoring tool".  Looks good.  But needs 3rd-party users to depend on this tool, not very active.

https://stackpulse.com/blog/grpc-in-practice-directory-structure-linting-and-more/ is single-language (Go), so protos are exported as Go modules.

6.https://buf.build/ is "join our waitlist" status.  Trying to be npmjs-for-protos.

DIY.  E.g., publish to some S3 bucket with version (or revision,, for snapshots...) identifier as part of the path.  Add handwritten tooling to publish and fetch.  This requires writing some of a VCS, but hopefully one simpler than git.
git submodules.  While they have a bad rap, part of it is because they solve a hard problem (multi-repo integration).

Do nothing, just keep on copying proto definitions from treeverse/lakeFS to treeverse/spark-client until we have a better user story.  This is actually somewhat convenient for Treeverse (can forget to update the code) until a customer explicitly requests a new field.  Field discovery will also be harder for fields that never appear in the dataframe in Spark-SQL.

Back to single repo as of #1621 .


Fix port read/write asm

Using correct register sizes.
Cannot test this beyond confirming it compiles.

Thanks a lot!


Metro bundler throwing sha-1 error (rn-tester)

Description
./scripts/packager throws error at the end of bundling :
ReferenceError: SHA-1 for file react-native/node_modules/metro-runtime/src/polyfills/require.js (/react-native/node_modules/metro-runtime/src/polyfills/require.js) is not computed.
I have tried clearing npm, metro and watchman cache. Also, tried the workaround in this https://github.com/facebook/metro/issues/330. Restarting mac didn't help 👎
I have also tried changing the permission of the file (require.js) to chmod 777 but that didn't work either.
React Native version:
System:
OS: macOS 10.15.5
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 1.29 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.9.0 - /usr/local/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.14.8 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.7, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 21, 23, 25, 26, 27, 28, 29
Build Tools: 23.0.1, 25.0.0, 25.0.1, 26.0.1, 26.0.2, 26.0.3, 27.0.2, 27.0.3, 28.0.2, 28.0.3, 29.0.2
System Images: android-26 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom
Android NDK: 17.2.4988734
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
Xcode: 11.7/11E801a - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_191 - /usr/bin/javac
npmPackages:
@react-native-community/cli: ^5.0.1-alpha.1 => 5.0.1-alpha.1
react: 17.0.1 => 17.0.1
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce

Install node_modules in react native folder
Build app with command ./gradlew :packages:rn-tester:android:app:installJscDebug
Start metro with ./scripts/packager.sh
Open Rn-Tester app in simulator. It will throw error at 99.2% (metro-bundler)

Expected Results
It should bundle the app and run successfully
Snack, code example, screenshot, or link to a repository:

Running metro bundler in /packages folder through npm start fixes the issue 👍


CEP Co-Simulation using QuestaSim

I need to know how to fix this error during simulation of some instructions
cep_tb.cpuId[0].driver C_ERROR: Time out while waiting for Pass/Fail
I am using QuestaSim 2023.4 version
I followed all the steps mentioned in CEP/sims/cep_cosim/README.md
an I got this error during the step of running make runAll in CEP/sims/cep_cosim/testSuites/isaTests/Makefile

Can you verify that the steps in building the isaTests executed corrected?  I have not explicitly tested on QuestaSim 2023.4 and will need to see if I can replicated the issue.
Can you verify that the PassFail.hex for the particular test is present?
Do other of the isaTests pass?

Yes I succeeded to make the tests pass when I run them locally on my machine, however I faced this issue when I run the tests on the grid.
I am trying to debug the Error so I need to know when tests fail with this error and how to overcome this error.
In the following file CEP/sims/cep_cosimdrivers/cep_tests/cep_apis.cc: , this message "Time out while waiting for Pass/Fail" is printed when the there is no pass or fail status as shown

Hi Brendon ,
This is a kindly reminder.
Could you explain to me when this msg is flagged  "Time out while waiting for Pass/Fail" and how to overcome the issue
Thanks,
Omar

Omar,
While I am actively working on the v4.5 release, I will note that some of the tests don't work... and thus timeout.
For example, the -v- tests are known to fail, due to a lack of proper virtual mode support in our codebase.
Do some tests pass on the grid while others do not?
As to your note that they pass locally, but not on the grid... what is the configuration difference between the environments?

Hi Brendon,
Unfortunately some of -p- tests  are failing with timeout too, I am trying to investigate the issue
for example this test rv64mi-p-breakpoint
I can find PassFail.hex as shown
> @3<PHONE_NUMBER>000040 //<PHONE_NUMBER>000040 <write_tohost>:
> @1<PHONE_NUMBER>0002b4 //<PHONE_NUMBER>0002b4 :
> @0<PHONE_NUMBER>0002d0 //<PHONE_NUMBER>0002d0 :
in the transcript all CPU are passing only CPU[0] fail after timeout , I tried to increase timeout to 1000 as shown

My question here why CPU[0] didn't get an pass or fail status and fail with timeout in simulation as shown
10118909 cep_tb.cpuId[0].driver C_ERROR: Time out while waiting for Pass/Fail
10118910 cep_tb.cpuId[0].driver C_LOG: access::RunClk mSlotId=0 mLocalId=0 numClk=1000
10119912 cep_tb.cpuId[0].driver C_LOG: access::RunClk mSlotId=0 mLocalId=0 numClk=100
10120014 cep_tb.cpuId[0].driver C_LOG: ======== TEST FAIL ========== 1

Omar, I appreciate the detailed debug info.  I am curious, have you changed the chipyard configuration?
When you build the chip, did you run make -f Makefile.chipyard?  Did you leave the default subproject of cep_cosim?

Yes I Followed all the steps mentioned, and I didn't change any thing in chipyard  configuration.
I build the chip on 15 NOV 2023.

Omar,  unfortunately, I don't have an immediate answer for you.
Using Questa2023.4, I just ran the rv64mi-p-breakpoint test on CEP v4.41:
** Warning: (vsim-7032) The 64-bit glibc RPM does not appear to be installed on this machine.  Calls to gcc may fail.

Compiling<EMAIL_ADDRESS>Loading<EMAIL_ADDRESS>Loading /home/br24169/projects/CEP/CEP_v4.41/sims/cep_cosim/lib/libvpp.so

do /home/br24169/projects/CEP/CEP_v4.41/sims/cep_cosim/testSuites/isaTests/rv64mi-p-breakpoint/vsim.do
1
1
INFO:        0 cep_tb.cpuId[0].driver.force_tile_reset Forcing Tile #0 in reset...
INFO:        0 cep_tb.cpuId[1].driver.force_tile_reset Forcing Tile #1 in reset...
INFO:        0 cep_tb.cpuId[2].driver.force_tile_reset Forcing Tile #2 in reset...
INFO:        0 cep_tb.cpuId[3].driver.force_tile_reset Forcing Tile #3 in reset...
INFO:        0 cep_tb.system_driver ==== ISA RISCV_TESTS is active ===
INFO:        0 cep_tb.system_driver Reading from PassFail.hex: pass = 0x800002a0, fail = 0x80000284, finish = 0x0, write_tohost = 0x80000040, hangme = 0x0
INFO:        0 cep_tb.system_driver GetTheKey mKey = 0x00006003, mActiveMask = 0x000000000000000f from C2VKeyFile.KEY
INFO:        0 cep_tb.system_driver shMemInit: Client: shMem->InitMe Done
INFO:        1 cep_tb.system_driver BARE_MODE: Forcing scratch_word0[3:0], thus Disabling UART and SD Boot in the BootROM...
INFO:        1 cep_tb.cpuId[0].driver GetTheKey mKey = 0x00006003, mActiveMask = 0x000000000000000f from C2VKeyFile.KEY
INFO:        1 cep_tb.cpuId[0].driver shMemInit: Client: shMem->InitMe Done
INFO:        1 cep_tb.cpuId[1].driver GetTheKey mKey = 0x00006003, mActiveMask = 0x000000000000000f from C2VKeyFile.KEY
INFO:        1 cep_tb.cpuId[1].driver shMemInit: Client: shMem->InitMe Done
INFO:        1 cep_tb.cpuId[2].driver GetTheKey mKey = 0x00006003, mActiveMask = 0x000000000000000f from C2VKeyFile.KEY
INFO:        1 cep_tb.cpuId[2].driver shMemInit: Client: shMem->InitMe Done
INFO:        1 cep_tb.cpuId[3].driver GetTheKey mKey = 0x00006003, mActiveMask = 0x000000000000000f from C2VKeyFile.KEY
INFO:        1 cep_tb.cpuId[3].driver shMemInit: Client: shMem->InitMe Done
INFO:       10 cep_tb.system_driver Turning ON __shIpc_EnableMode simTime = 1
INFO:       11 cep_tb.cpuId[0].driver Calling $vpp_WaitTilStart slot = 0 cpu = 0
INFO:       11 cep_tb.cpuId[0].driver Turning ON __shIpc_EnableMode simTime = 1
INFO:       11 cep_tb.cpuId[1].driver Calling $vpp_WaitTilStart slot = 0 cpu = 1
INFO:       11 cep_tb.cpuId[1].driver Turning ON __shIpc_EnableMode simTime = 1
INFO:       11 cep_tb.cpuId[2].driver Calling $vpp_WaitTilStart slot = 0 cpu = 2
INFO:       11 cep_tb.cpuId[2].driver Turning ON __shIpc_EnableMode simTime = 1
INFO:       11 cep_tb.cpuId[3].driver Calling $vpp_WaitTilStart slot = 0 cpu = 3
INFO:       11 cep_tb.cpuId[3].driver Turning ON __shIpc_EnableMode simTime = 1
INFO:       15 cep_tb.cpuId[3].driver Entering shIpc_EnableMode Loop simTime = 2
INFO:       15 cep_tb.cpuId[2].driver Entering shIpc_EnableMode Loop simTime = 2
INFO:       15 cep_tb.cpuId[1].driver Entering shIpc_EnableMode Loop simTime = 2
INFO:       15 cep_tb.cpuId[0].driver Entering shIpc_EnableMode Loop simTime = 2
INFO:       15 cep_tb.system_driver Entering shIpc_EnableMode Loop simTime = 2
INFO:       15 cep_tb.cpuId[1].driver SingleCoreOnly = 1
INFO:       15 cep_tb.cpuId[2].driver SingleCoreOnly = 1
INFO:       15 cep_tb.cpuId[3].driver SingleCoreOnly = 1
3 cep_tb.cpuId[0].driver C_LOG: access::RunClk mSlotId=0 mLocalId=0 numClk=1000
5 cep_tb.cpuId[3].driver C_LOG: access::RunClk mSlotId=0 mLocalId=3 numClk=1000
5 cep_tb.cpuId[2].driver C_LOG: access::RunClk mSlotId=0 mLocalId=2 numClk=1000
5 cep_tb.cpuId[1].driver C_LOG: access::RunClk mSlotId=0 mLocalId=1 numClk=1000
5 cep_tb.system_driver C_LOG: loadMemory: Loading file ./riscv_wrapper.img to SCRATCHPAD RAM with maxByteCntof 655360B , fileOffset = 0B, destOffset = 0B
1007 cep_tb.cpuId[0].driver C_LOG: access::RunClk mSlotId=0 mLocalId=0 numClk=1000
1009 cep_tb.cpuId[3].driver C_LOG: access::RunClk mSlotId=0 mLocalId=3 numClk=1000
1009 cep_tb.cpuId[2].driver C_LOG: access::RunClk mSlotId=0 mLocalId=2 numClk=1000
1009 cep_tb.cpuId[1].driver C_LOG: access::RunClk mSlotId=0 mLocalId=1 numClk=1000
2011 cep_tb.cpuId[0].driver C_LOG: access::RunClk mSlotId=0 mLocalId=0 numClk=1000
2013 cep_tb.cpuId[3].driver C_LOG: access::RunClk mSlotId=0 mLocalId=3 numClk=1000
2013 cep_tb.cpuId[2].driver C_LOG: access::RunClk mSlotId=0 mLocalId=2 numClk=1000
2013 cep_tb.cpuId[1].driver C_LOG: access::RunClk mSlotId=0 mLocalId=1 numClk=1000
2068 cep_tb.system_driver C_LOG: loadMemory: flushing cache line
2080 cep_tb.system_driver C_LOG: loadMemory: Setting program loaded flag
INFO:    20835 cep_tb.system_driver Program is now loaded
3015 cep_tb.cpuId[0].driver C_LOG: access::RunClk mSlotId=0 mLocalId=0 numClk=1000
3017 cep_tb.cpuId[3].driver C_LOG: access::RunClk mSlotId=0 mLocalId=3 numClk=1000
3017 cep_tb.cpuId[2].driver C_LOG: access::RunClk mSlotId=0 mLocalId=2 numClk=1000
3017 cep_tb.cpuId[1].driver C_LOG: access::RunClk mSlotId=0 mLocalId=1 numClk=1000
4017 cep_tb.cpuId[0].driver C_LOG: OK: Program loading is completed
4019 cep_tb.cpuId[3].driver C_LOG: OK: Program loading is completed
4019 cep_tb.cpuId[2].driver C_LOG: OK: Program loading is completed
4019 cep_tb.cpuId[1].driver C_LOG: OK: Program loading is completed
INFO:    40205 cep_tb.cpuId[0].driver.release_tile_reset Releasing Tile #0 reset...
INFO:    40225 cep_tb.cpuId[1].driver.release_tile_reset Releasing Tile #1 reset...
INFO:    40225 cep_tb.cpuId[2].driver.release_tile_reset Releasing Tile #2 reset...
 Put it to sleep
INFO:    40555 cep_tb.cpuId[2].driver C2 Pass/Fail Detected!!!... Put it to sleep
INFO:    40635 cep_tb.cpuId[1].driver C1 Pass/Fail Detected!!!...
INFO:    55445 cep_tb.cpuId[0].driver C0 Pass/Fail Detected!!!... Put it to sleep
6044 cep_tb.cpuId[0].driver C_LOG: Current Pass = 0x1 Fail = 0x0 maxTimeOut = 98
6045 cep_tb.cpuId[0].driver C_LOG: access::RunClk mSlotId=0 mLocalId=0 numClk=100
6147 cep_tb.cpuId[0].driver C_LOG: ======== TEST PASS ==========
cep_tb.cpuId[0].driver InactiveStatus detected..Shutting down!!!
6148 cep_tb.system_driver C_LOG: main ======== TEST PASS ==========
INFO:    61495 cep_tb.system_driver Running for 1 more NS before terminate the simv process
** Note: $finish    : /home/br24169/projects/CEP/CEP_v4.41/sims/cep_cosim/dvt/dpi_common.incl(393)
Time: 61505 ns  Iteration: 0  Instance: /cep_tb/system_driver
End time: 07:27:06 on Jan 29,2024, Elapsed time: 0:00:10
Errors: 0, Warnings: 2
The only other thing I can think of is the the gcc version you used to build the riscv-toolchain.

Hi Brendon,
I found the reason of the issue, that When I run multiple tests in parallel some of tests fails with the following error.

C_ERROR: Time out while waiting for Pass/Fail

Did you face this issue before

Hello, Omar.  Yes, I have seen that before.  Not all of the RISC-V ISA test terminate as expected.  I have yet to debug the issue.
Our ISA test methodology is to extract the Pass / Fail state from the .dump file.  Then the simulation looks for the PC to hit either the pass or fail exit points.

Hello Brendon,
Thanks for your reply, please inform me once you have check the issue and how to pass it

Hello Omar.  Happy so to do, but I would not expect it anytime soon.  As noted, some of the tests currently pass, some do not.  My current efforts are focused elsewhere.


feat: Implement InfluxDB 2.x target

Implementing support for InfluxDB 2.x by using the new client (https://github.com/influxdata/influxdb-client-js).
I tried to do it similarly as the InfluxDB 1.x target. The only real difference is in the tests, where I had to use regex for the body matching since the new client pushes data with timestamp and I didn't find a nice way of mocking the time there.
Resolves #25

Hi @salatamartin ,
Thank you for the pull request! I'd like to suggest considering a different npm package that might offer a more lightweight solution for our needs. I recommend checking out the influxdb-v2 npm package, which is known for its minimal footprint, efficient performance and we can achieve the same functionality with a reduced impact on the overall application size and load times. It aligns well with our goal of keeping our application lean and responsive.

Hello @ASaiAnudeep,
can we proceed with this PR, please?
Thanks!

I will take a look and merge it this week.


Cable not connecting to the network and drives dead

Cable not connecting to the network
Ok this is a hell of a bug on sf3 we are using v1.2.14 and the cables will not connect link to screen shots at the bottom you can see that when I link with a cable nothing works when you link with a crafter it will work. I have also run into the bug with drives showing the item count but not being able to see them in a grid they may have been corrupted there was no server crash but I did have them in my inventory when going into and out of creative
Steps to reproduce:
in link at bottom of page
Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge:<IP_ADDRESS>010085
Refined Storage: v1.2.14

Does this issue occur on a server? [yes]
If a (crash)log is relevant for this issue, link it here:
http://imgur.com/a/2jrBX

Related to #370

fixed in 1.11. might get backported to 1.10


[wip] Use pure zsh to load bundles

The original implementation runs way more processes than are necessary.
While it is normally good practice to use standard unix conventions in
order to maintain compatability, commands that run in a zshrc file
should ideally be as fast as possible. Using sed, awk, tr, etc.
drastically slow down shell initialization time, especially on cygwin,
because processes take much longer than on a native unix platform.
This may alleviate the need for #129.

Should the other commands be updated to not create extra processes / use pure zsh?
How much should i try to use fancy zsh flags? or should i stick with regexp-replace and -antigen-arraygrep
I need help getting the tests to run, the basic pip install + make didn't work on cygwin (i'll try my linux install later)
should i just switch to using zgen?
what old versions of zsh should be supported? how much do the tests cover? (hopefully travis does this, too tired rn to look)

While I do agree that 'grep', 'sed' and so on should be used scarcely it seems it doesn't improve performance on other than cygwin environments, at least here (Fedora 22, zsh 5.0.7) the start up time is as follow:
# performance-improvements branch
$ time zsh
zsh  0.35s user 0.17s system 104% cpu 0.499 total

# master
time zsh
zsh  0.38s user 0.44s system 113% cpu 0.718 total

While the cache branch would improve start up time through out all platforms and environments.

This may alleviate the need for #128.

I don't think antigen completion as anything to do with performance.

Should the other commands be updated to not create extra processes / use pure zsh?

It should be applied uniformly through out all antigen code if possible as to not have too many ways to do one thing in the code.

How much should i try to use fancy zsh flags?

As long as it doesn't introduce backward incompatibility.

Whoops, that was supposed to be

This may alleviate the need for #129.

Yeah, it doesn't have anything to do with completion.

This doesn't alleviate the need for cache as the performance improvements it brings turn start up time from >0.40s to 0.10s and aren't platform specific.

I didn't say that it would alleviate the need for cache, I was just pondering if it would. Also, the cache branch isn't ready, and requires user intervention to get it to work (currently), will require cache invalidation, etc.. This is a much smaller, simpler, less complex change, and it does provide a significant performance increase, especially when lots of bundles are used.
To compare, here is the difference in time provided by caching on my system:
# build cache
$ time zsh
zsh  0.67s user 0.14s system 44% cpu 1.822 total

# load cache
$ time zsh
zsh  0.63s user 0.08s system 79% cpu 0.886 total

So, you can see, even on linux, my patch does lessen the need for caching; caching only provides a 15% speed increase over my performance-improvements.

@forivall I looked at your configs (thanks for pointing them out). Given your configs nothing is being cached as 'antigen bundle' is used instead of 'antigen bundles'.
Changing the configuration would give the following stats:
$ time zsh
zsh  0.66s user 0.92s system 119% cpu 1.326 total

$ time zsh
zsh  0.38s user 0.09s system 102% cpu 0.461 total

@desyncr I hadn't pushed my changes yet. It does use the cache. Check again.

@forivall I'm sorry -zcache-start and -zcache-done should only be called inside antigen, not from outside. I don't know how it would behave when using it in a non-standard way.

It behaves exactly the same.  I have my dotfiles stored on a hybrid hdd.

Screw it, I'm switching to zgen. It's just as fast as my tweaks, and I don't have to deal with this memester.

If somebody wants to take this and clean it up, that's fine by me, but any further involvement from me will be minimal.

@HeroCC You can also try out this branch; it makes safer changes than the cache branch for similar performance gains.

I've been using this branch for sometime now, no problems can we get this merged in?

+1 for merging this.

This looks to be a dead project, time to clone and branch it into a new one.

@blairham I would suggest looking at zgen, zplugin or antibody

Thanks @forivall ;) I feel you're frustration on this project. it's been working fine but the lack of activity on it bothers me. I hadn't switched yet as I really like how antigen works.

For the reason exposed above and the lack of interest in maintaining/cleaning this PR I'm closing this out.
Thanks for using and contributing to Antigen.


fixed No user found then Slack API paginates

If Slack workspace contains more than 1000 user, "users.list" API call response will be paginated. users_list function did not accounted for this. If INCIDENT_BOT_NAME username is not on first page, application will throw
  File "manage.py", line 21, in <module>
    main()
  File "manage.py", line 17, in main
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 345, in execute
    settings.INSTALLED_APPS
  File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 76, in __getattr__
    self._setup(name)
  File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 63, in _setup
    self._wrapped = Settings(settings_module)
  File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 142, in __init__
    mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/opt/project/myincidentresponse/settings.py", line 185, in <module>
    INCIDENT_BOT_NAME
  File "/usr/local/lib/python3.7/site-packages/response/slack/client.py", line 79, in get_user_id
    raise SlackError(f"User '{name}' not found")
response.slack.client.SlackError: User '<userbame>' not found```

Hello @mattrco,
Could you take a look at this PR?

Hi we had the same issue. Would been for you to merge this and it works with ours too.

@ChrisAnn @evnsio @milesbxf Any ideas when this can be merged? Need it in the module


Faster connection error detection.

Infinite timeout in poll()s.

Hi @fourtytoo, can you review the comments above? This patch looks good if you can address those issues. Thanks!

Oh, I think I see what you are going for: If timeout < 0, then this code will give better socket error detection that otherwise would be ignored and cause a delay?

Ookay, I got it- infinite timeout is what you were going for, in addition to the extra errfd checks. This sounds good. Will merge. Would you be able to do a documentation update if you have a chance, e.g., in the README:
void poll(int timeout = 0); // timeout in milliseconds

to
void poll(int timeout = 0);
    // Timeout in milliseconds when > 0.
    // Non-blocking when 0.
    // Blocks indefinitely when < 0.

Yikes!!! Really sorry to flop on this, but I am now unclear about the use case for efds:
http://stackoverflow.com/questions/1342712/nix-select-and-exceptfds-errorfds-semantics

It says "It is sometimes thought that exceptfds is needed to detect errors, but that is a misconception. Errors will be flagged in readfds ..." . Though I don't really see any harm in using efds, it sounds like it might be extraneous. Could you explain about how your use case is using the efds? Thanks!

Actually, I was taken aback when the README actually already documented
that feature:
// Function to perform actual network send()/recv() I/O:// (note: if
all you need is to recv()/dispatch() messages, then timeout can be//
used to block until a message arrives. By default, when timeout is 0,
poll()// will not block at all.)
but I couldn't find a way to specify an endless timeout.
BTW the C++11 version it wasn't touched by my patch.
On Wed, 9 Sep 2015 at 13:59 David Baird<EMAIL_ADDRESS>wrote:

Ookay, I got it- infinite timeout is what you were going for, in addition
to the extra errfd checks. This sounds good. Will merge. Would you be able
to do a documentation update if you have a chance, e.g., in the README:
void poll(int timeout = 0); // timeout in milliseconds
to
void poll(int timeout = 0);
// Timeout in milliseconds when > 0.
// Non-blocking when 0.
// Blocks indefinitely when < 0.
—
Reply to this email directly or view it on GitHub
https://github.com/dhbaird/easywsclient/pull/42#issuecomment-138887598.

Yeah, I agree with you that a block-indefinitely feature would be an improvement, and would like to merge this patch. Would you be able to address the question above about the use case for efds?

That's exactly what I learned from the Stevens' book, but it wasn't the
behavior of OSX.
Actually, in our use case, the server was running on a virtual machine;
without select(), the "power-off" of the machine wasn't detected until
minutes later.
Frankly, I don't know what to say.  Just leave out that part if you aren't
comfortable with that.
On Wed, 9 Sep 2015 at 14:11 Walter C. Pelissero<EMAIL_ADDRESS>wrote:

Actually, I was taken aback when the README actually already documented
that feature:
// Function to perform actual network send()/recv() I/O:// (note: if all you need is to recv()/dispatch() messages, then timeout can be// used to block until a message arrives. By default, when timeout is 0, poll()// will not block at all.)
but I couldn't find a way to specify an endless timeout.
BTW the C++11 version it wasn't touched by my patch.
On Wed, 9 Sep 2015 at 13:59 David Baird<EMAIL_ADDRESS>wrote:

Ookay, I got it- infinite timeout is what you were going for, in addition
to the extra errfd checks. This sounds good. Will merge. Would you be able
to do a documentation update if you have a chance, e.g., in the README:
void poll(int timeout = 0); // timeout in milliseconds
to
void poll(int timeout = 0);
// Timeout in milliseconds when > 0.
// Non-blocking when 0.
// Blocks indefinitely when < 0.
—
Reply to this email directly or view it on GitHub
https://github.com/dhbaird/easywsclient/pull/42#issuecomment-138887598.

Naah, I won't leave it out. But I want to have an idea of why it is in there in case someone else wants to take it out, and I can justify it to them! :)

Are you sure that with efds, in OS X, it actually does give it the ability to detect that the other machine was powered off?

I don't have the figures with me, but I believe tonight I'll be able to
repeat some tests with a sample program.
Please bear with me.
On Wed, 9 Sep 2015 at 14:24 David Baird<EMAIL_ADDRESS>wrote:

Are you sure that with efds, in OS X, it actually does give it the ability
to detect that the other machine was powered off?
—
Reply to this email directly or view it on GitHub
https://github.com/dhbaird/easywsclient/pull/42#issuecomment-138893019.

Awesome; I'm patient. Also, thanks a lot for looking into this. I really appreciate it!

It seems that either way (with efds and without) the unplug of the server
running on the virtual machine is not detected.
The test has been done with poll(-1).  With a timeout, the death of the
socket is detected with or without efds.
Ergo, there is no difference, and the Stevens' can be put back on the altar.
So it appears that our tests had been done in different circumstances (with
and without timeout, I suspect).
Sorry about that.
On Wed, 9 Sep 2015 at 14:29 David Baird<EMAIL_ADDRESS>wrote:

Awesome; I'm patient. Also, thanks a lot for looking into this. I really
appreciate it!
—
Reply to this email directly or view it on GitHub
https://github.com/dhbaird/easywsclient/pull/42#issuecomment-138894717.

No worries! I'd still like to merge the indefinite timeout though. If you are still interested, would you be able to re-submit the patch with just that part?

You should have received the pull req.
On Thu, 10 Sep 2015 at 03:47 David Baird<EMAIL_ADDRESS>wrote:

No worries! I'd still like to merge the indefinite timeout though. If you
are still interested, would you be able to re-submit the patch with just
that part?
—
Reply to this email directly or view it on GitHub
https://github.com/dhbaird/easywsclient/pull/42#issuecomment-139092022.

Merged #43. Thanks!


Design a logo for this application

This logo is to be used in the splash screen and title bar.

Hello @QAZIMAAZARSHAD . Kindly assign this issue to me. I would like to contribute to this issue.

I'll assign you this issue when the contribution period starts from 10th June, then you can start working on this issue.

Thank you

Hi @QAZIMAAZARSHAD i would like to contribute to this issue. Please assign me yhis issue.

Hii @QAZIMAAZARSHAD  i wanna work with this logo shall i

I'll assign you this issue when the contribution period starts from 10th June, then you can start working on this issue.

Hey, @starrohan999 I'm a participant of LGMSOC'21 I would like to contribute to this issue will you please assign it to me

Nice @Sakalya100.
But don't make PR's now.
Others are also working on this issue let's see their designs as well. The best will be accepted.

Okay...So what should I do after making the logo. When Can I make the PR. Can you please tell @QAZIMAAZARSHAD

When everyone is done with their logo designs and your design is the best then I will inform you to make PR.

I would like to work on this issue. please assign it to me under LCM Soc21.

Everyone @kshitija-2001, @Sakalya100, @SahityaRoy, @ambivert-sam, @techabhi08  who have designed their logo can make PR now.
Create a folder named logo and add your logo in that folder.
No change in code,

I would like to work on this issue. please assign it to me under LCM Soc21.

I would like to work on this issue. please assign it to me under LCM Soc21.

Issue already resolved.


Azure.Identity Question

Library name and version
Azure.Identity 1.8.0
Query/Question
I am able to use v1.7.0 of Azure.Identity with no problems.  My situation is I have an AKS cluster using pod identity which is configured to a user assigned managed identity.  I use the Microsoft.Extensions.Azure library to configure all of my Azure clients such as Blob client, ServiceBus client, etc.
While using v1.7.0, occasionally my application may attempt to bootstrap before the identity is available to the pod to use and gets the occasional error only during startup which is fine because the pod won't be considered ready until it successfully starts.
However, with v1.8.0 I get stuck in an infinite error state and get stuck with millions of logged failures that look like the following:
ManagedIdentityCredential authentication failed: The json containing instance metadata does not contain details about the authority in use: login.microsoftonline.us. See https://aka.ms/msal-net-custom-instance-metadata for more details.  See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/managedidentitycredential/troubleshoot The json containing instance metadata does not contain details about the authority in use: login.microsoftonline.us. See https://aka.ms/msal-net-custom-instance-metadata for more details.
The links are of no help.  I'm not sure what changed between 1.7.0 and 1.8.0, but could someone please explain what was changed and why this may be occurring?
Environment
No response

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

We hit the same issue, for us it manifested as this error:

Unhandled exception. Azure.Identity.AuthenticationFailedException: ManagedIdentityCredential authentication failed: Configure either region discovery or custom instance metadata. Custom instance discovery metadata overrides region discovery.
See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/managedidentitycredential/troubleshoot
---> MSAL.NetCore.<IP_ADDRESS>.MsalClientException:
ErrorCode: region_discovery_with_custom_instance_metadata
Microsoft.Identity.Client.MsalClientException: Configure either region discovery or custom instance metadata. Custom instance discovery metadata overrides region discovery.
at Microsoft.Identity.Client.ConfidentialClientApplicationBuilder.Validate()
at Microsoft.Identity.Client.AbstractApplicationBuilder1.BuildConfiguration()    at Microsoft.Identity.Client.ConfidentialClientApplicationBuilder.BuildConcrete()    at Microsoft.Identity.Client.ConfidentialClientApplicationBuilder.Build()    at Azure.Identity.MsalConfidentialClient.CreateClientAsync(Boolean async, CancellationToken cancellationToken)    at Azure.Identity.MsalClientBase1.GetClientAsync(Boolean async, CancellationToken cancellationToken)
at Azure.Identity.MsalConfidentialClient.AcquireTokenForClientCoreAsync(String[] scopes, String tenantId, Boolean async, CancellationToken cancellationToken)
at Azure.Identity.MsalConfidentialClient.AcquireTokenForClientAsync(String[] scopes, String tenantId, Boolean async, CancellationToken cancellationToken)
at Azure.Identity.ManagedIdentityClient.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
at Azure.Identity.ManagedIdentityCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)

The newer version 1.8.1 has not fixed the issue. We have the same exception after upgrading to v1.8.1.
ManagedIdentityCredential authentication failed: The json containing instance metadata does not contain details about the authority in use: login.chinacloudapi.cn. See https://aka.ms/msal-net-custom-instance-metadata for more details. \nSee the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/managedidentitycredential/troubleshoot","Data":null,"InnerException":{"$type":"Microsoft.Identity.Client.MsalClientException, Microsoft.Identity.Client","IsRetryable":false,"ErrorCode":"invalid-custom-instance-metadata","Message":"The json containing instance metadata does not contain details about the authority in use: login.chinacloudapi.cn. See https://aka.ms/msal-net-custom-instance-metadata for more details. ","Data":{"$type":"System.Collections.ListDictionaryInternal, System.Private.CoreLib"},"InnerException":null,"HelpLink":null,"Source":"Microsoft.Identity.Client","HResult":-2146233088,"StackTrace":"   at Microsoft.Identity.Client.Instance.Discovery.UserMetadataProvider.GetMetadataOrThrow(String environment, ILoggerAdapter logger)\r\n   at Microsoft.Identity.Client.Instance.Discovery.InstanceDiscoveryManager.GetMetadataEntryAsync(AuthorityInfo authorityInfo, RequestContext requestContext, Boolean forceValidation)\r\n   at Microsoft.Identity.Client.Instance.AuthorityManager.RunInstanceDiscoveryAndValidationAsync()\r\n   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.FetchNewAccessTokenAsync(CancellationToken cancellationToken)\r\n   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.ExecuteAsync(CancellationToken cancellationToken)\r\n   at Microsoft.Identity.Client.Internal.Requests.RequestBase.RunAsync(CancellationToken cancellationToken)\r\n   at Microsoft.Identity.Client.ApiConfig.Executors.ConfidentialClientExecutor.ExecuteAsync(AcquireTokenCommonParameters commonParameters, AcquireTokenForClientParameters clientParameters, CancellationToken cancellationToken)\r\n   at Azure.Identity.AbstractAcquireTokenParameterBuilderExtensions.ExecuteAsync[T](AbstractAcquireTokenParameterBuilder1 builder, Boolean async, CancellationToken cancellationToken)\r\n   at Azure.Identity.MsalConfidentialClient.AcquireTokenForClientCoreAsync(String[] scopes, String tenantId, Boolean async, CancellationToken cancellationToken)\r\n   at Azure.Identity.MsalConfidentialClient.AcquireTokenForClientAsync(String[] scopes, String tenantId, Boolean async, CancellationToken cancellationToken)\r\n   at Azure.Identity.ManagedIdentityClient.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)\r\n   at Azure.Identity.ManagedIdentityCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)"},"HelpURL":null,"StackTraceString":"   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)\r\n   at Azure.Identity.ManagedIdentityCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)\r\n   at Azure.Identity.ManagedIdentityCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)\r\n   at Azure.Identity.DefaultAzureCredential.GetTokenFromSourcesAsync(TokenCredential[] sources, TokenRequestContext requestContext, Boolean async, CancellationToken cancellationToken)\r\n   at Azure.Identity.DefaultAzureCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)\r\n   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)\r\n   at Azure.Identity.DefaultAzureCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)\r\n   at Azure.Identity.DefaultAzureCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)\r\n   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.AccessTokenCache.GetHeaderValueFromCredentialAsync(TokenRequestContext context, Boolean async, CancellationToken cancellationToken)\r\n   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.AccessTokenCache.GetHeaderValueAsync(HttpMessage message, TokenRequestContext context, Boolean async)\r\n   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.AccessTokenCache.GetHeaderValueAsync(HttpMessage message, TokenRequestContext context, Boolean async)\r\n   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.AuthenticateAndAuthorizeRequestAsync(HttpMessage message, TokenRequestContext context)\r\n   at Azure.Security.KeyVault.ChallengeBasedAuthenticationPolicy.AuthorizeRequestInternal(HttpMessage message, Boolean async)\r\n   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async)\r\n   at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async)\r\n   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async)\r\n   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async)\r\n   at Azure.Core.Pipeline.HttpPipeline.SendRequestAsync(Request request, CancellationToken cancellationToken)\r\n   at Azure.Security.KeyVault.KeyVaultPipeline.SendRequestAsync(Request request, CancellationToken cancellationToken)\r\n   at Azure.Security.KeyVault.KeyVaultPipeline.GetPageAsync[T](Uri firstPageUri, String nextLink, Func1 itemFactory, String operationName, CancellationToken cancellationToken)\r\n   at Azure.Core.PageResponseEnumerator.FuncAsyncPageable1.AsPages(String continuationToken, Nullable1 pageSizeHint)+MoveNext()\r\n   at Azure.Core.PageResponseEnumerator.FuncAsyncPageable1.AsPages(String continuationToken, Nullable1 pageSizeHint)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()\r\n   at Azure.AsyncPageable1.GetAsyncEnumerator(CancellationToken cancellationToken)+MoveNext()\r\n   at Azure.AsyncPageable1.GetAsyncEnumerator(CancellationToken cancellationToken)+MoveNext()\r\n   at Azure.AsyncPageable1.GetAsyncEnumerator(CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()\r\n `

@jsquire @schaabs @christothes
I checked 1.8.1 still have the issue, could we reopen?
The error comes out in a different place:
With 1.8.0:
at Microsoft.Identity.Client.Instance.AuthorityManager.RunInstanceDiscoveryAndValidationAsync()
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.FetchNewAccessTokenAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.ExecuteAsync(CancellationToken cancellationToken)

With 1.8.1:
at Microsoft.Identity.Client.ClientApplicationBase.CreateRequestParametersAsync(AcquireTokenCommonParameters commonParameters, RequestContext requestContext, ITokenCacheInternal cache)
   at Microsoft.Identity.Client.ConfidentialClientApplication.CreateRequestParametersAsync(AcquireTokenCommonParameters commonParameters, RequestContext requestContext, ITokenCacheInternal cache)
   at Microsoft.Identity.Client.ApiConfig.Executors.ConfidentialClientExecutor.ExecuteAsync(AcquireTokenCommonParameters commonParameters, AcquireTokenForClientParameters clientParameters, CancellationToken cancellationToken)

Hi @karataliu - This is fixed in the PR referenced above so it will be in the next version of the package.

@christothes when will the next version with the fix be released?

@christothes could you please suggest which PR do you mean?
The PR is picked into 1.8.1 https://github.com/Azure/azure-sdk-for-net/pull/33478 , but it doesn't fix the issue.
Is there another PR here?

I think there might be several different issues here, as I'm pretty sure the following line fixes the one we ran into (see stacktrace I posted above): https://github.com/Azure/azure-sdk-for-net/pull/33478/files#diff-e8bef522f24b413fc37ec666d0d5e305a1e472252cacf66b2e4cf1f225de64a8R107

It should be fixed in #35544 - Note you can test this version by trying the latest dev package versions here.

FYI this is fixed in Azure.Identity 1.8.2: https://github.com/Azure/azure-sdk-for-net/releases/tag/Azure.Identity_1.8.2


Add handlers packages

Codecov Report

Merging #33 into master will decrease coverage by 0.24%.
The diff coverage is 72.72%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
- Coverage   85.76%   85.52%   -0.25%
==========================================
  Files          37       39       +2
  Lines         815      829      +14
  Branches      175      180       +5
==========================================
+ Hits          699      709      +10
- Misses         58       59       +1
- Partials       58       61       +3

Impacted Files
Coverage Δ

packages/rawmodel-handlers/src/index.ts
66.66% <ø> (ø)

...rawmodel-handlers/src/handlers/mongo-uniqueness.ts
72.72% <72.72%> (ø)

Codecov Report

Merging #33 into master will decrease coverage by 0.24%.
The diff coverage is 72.72%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
- Coverage   85.76%   85.52%   -0.25%
==========================================
  Files          37       39       +2
  Lines         815      829      +14
  Branches      175      180       +5
==========================================
+ Hits          699      709      +10
- Misses         58       59       +1
- Partials       58       61       +3

Impacted Files
Coverage Δ

packages/rawmodel-handlers/src/index.ts
66.66% <ø> (ø)

...rawmodel-handlers/src/handlers/mongo-uniqueness.ts
72.72% <72.72%> (ø)

Codecov Report

Merging #33 into master will decrease coverage by 0.24%.
The diff coverage is 72.72%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
- Coverage   85.76%   85.52%   -0.25%
==========================================
  Files          37       39       +2
  Lines         815      829      +14
  Branches      175      180       +5
==========================================
+ Hits          699      709      +10
- Misses         58       59       +1
- Partials       58       61       +3

Impacted Files
Coverage Δ

packages/rawmodel-handlers/src/index.ts
66.66% <ø> (ø)

...rawmodel-handlers/src/handlers/mongo-uniqueness.ts
72.72% <72.72%> (ø)


Support sprint metrics based on sprint participants

Description
As a PM, I want to see each sprint participant's schedules and the completion rate of a sprint, such as how many codes have been committed, how many issues have been assigned and accomplished, etc.
Metrics to be supported

[ ] Dev Eq: Dev Eq of each sprint participant
Definition: Find all the issues that the sprint participant participated in under the sprint and the time period in which they participated, and calculate the sum of the issue-associated commits whose authored_date belongs to this time period.
[ ] Issue(C): Count of completed issues in which the sprint participant has participated
[ ] Issue(P): Count of participated issues in which the sprint participant has participated
[ ] Story Point(C): Sum of the story points of completed issues in which the participant has participated
[ ] Story Point(P): Sum of the story points of issues in which the participant has participated
[ ] Worktime(A): Actual work logged by each sprint participant
[ ] Fixed Bug: Count of fixed bugs in which the sprint participant has participated
[ ] Fixed Incident: Count of fixed incidents in which the sprint participant has participated
[ ] Avg Incident lead time: Avg fixing time of fixed incidents that sprint participant has participated
[ ] Avg Bug lead time: Avg fixing time of fixed bugs that sprint participant has participated

Note:

keep worktime(A) and remove worktime(P)
remove metric workload as it's too vague

Describe the solution you'd like
Please make sure the domain layer schema supports the metrics above.
There might be few things to check

[ ] If the raw data for those metrics exist in the domain layer. If not, collect it.
[ ] Is the existing schema easy to calculate those metrics. If not, design middle tables such as issue_assignee_history to make the metrics easier to query.

Already done.


adding chmod in sftp feature

Hi,
I have added 'chmod' feature on sftp (due after send, to execute script), I don't know the process to pull an update of the code, so it's only in sftp.php:
/**
 * Creates a directory
 *
 * @param  string $filename The filename to resolve
 * @param  int     $mod       The permissions on the new filename
 *
 * @return Boolean
 */
public function chmod($filename, $mod = 0600)
{
    return ssh2_sftp_chmod($this->getResource(), $filename, $mod);
}

Br,
Gilles

I am implement this feature and create a pull request.
Thank @GillesCrebassa


[BOT-79] enable postback button clicks

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


Optimise caching

@newhoggy What are we waiting for to merge this PR? Bors timeouts are again plaguing us in other PRs.

LGTM. I'm still suspicious of the GH Actions. But for a first approximation of correctness this should be fine. My core concern is that this is not identical to how we build our artifacts we distribute.

Yes, I consider this PR to be a intermittent alleviation of our CI woes, and I am looking forward to running the testing artifacts built by Hydra :+1:

bors r+


bug: useEditor returns null instead of Editor when it's not used in <EditorContent>

Provide environment information
System:
OS: macOS 15.1.1
CPU: (10) arm64 Apple M1 Pro
Memory: 116.63 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 21.2.0 - ~/.nvm/versions/node/v21.2.0/bin/node
Yarn: 1.22.22 - ~/.yarn/bin/yarn
npm: 10.8.1 - ~/.nvm/versions/node/v21.2.0/bin/npm
pnpm: 9.6.0 - ~/.nvm/versions/node/v21.2.0/bin/pnpm
bun: 1.1.0 - ~/.bun/bin/bun

Describe the bug
I described the bug and the workaround in this issue.

I had a menu bar from Tiptap component I used before but I couldn't get it to work as useEditor() doesn't return proper Editor instance.
I ended up using onCreate of Editor Contet and using a state to handle editor, then I can use my menu bar.
<EditorContent
extensions={extensions}
      onCreate={({ editor }) => {
        console.log("Editor created");
        setEditor(editor);
      }}
         ...
    >

I need editor in other parts as well but haven't found an easier/better way to do it than lifting up the state.
Link to reproduction
.
To reproduce
Try using useEditor in your project and log the results. Using useEffect didn't help either.
Additional information
No response

I noticed it works fine if it's called from a component in <EditorContent>.
The issue is that I want to show the Toolbar outside of the Editor Content. Right now it's shown below the cursor (even though it's the first component inside the EditorContent.

I got the same error, it seems Provider in EditorContent instead of EditorRoot.
Just workaround:
...
const [editor, setEditor] = useState<any | null>(null)

# set editot on update
<EditorContent
    onUpdate={({ editor }) => {
        setEditor(editor)
        setCharsCount(editor.storage.characterCount.words())
        console.log(editor.getHTML())
  }}
/>
....

Thanks @ancs21 , tried a similar approach but it's not ideal.
Are you creating a state for each of the relevant props?
setCharsCount(editor.storage.characterCount.words())


indent_style for control working incorrectly

Summary
The indent_style configuration option does not behave correctly for control flow.
Reproduction

Create a file (let's call it "c.rs" for the rest of the issue) containing the following content, which is based on the example in Configurations.md.

fn main() {
    if lorem_ipsum && dolor_sit && amet_consectetur && lorem_sit && dolor_consectetur && amet_ipsum && lorem_consectetur
    {
        // ...
    }
}

"Block" Variant

Create a rustfmt.toml file containing indent_style = "Block".
Do cargo run --bin rustfmt -- c.rs --write-mode=diff.

Result:
 fn main() {⏎
-    if lorem_ipsum && dolor_sit && amet_consectetur && lorem_sit && dolor_consectetur && amet_ipsum && lorem_consectetur⏎
+    if lorem_ipsum && dolor_sit && amet_consectetur && lorem_sit && dolor_consectetur && amet_ipsum⏎
+        && lorem_consectetur⏎
     {⏎
         // ...⏎
     }⏎

"Visual" Variant

Create a rustfmt.toml file containing indent_style = "Visual".
Do cargo run --bin rustfmt -- c.rs --write-mode=diff.

Result:
 fn main() {⏎
-    if lorem_ipsum && dolor_sit && amet_consectetur && lorem_sit && dolor_consectetur && amet_ipsum && lorem_consectetur⏎
+    if lorem_ipsum && dolor_sit && amet_consectetur && lorem_sit && dolor_consectetur && amet_ipsum⏎
+       && lorem_consectetur⏎
     {⏎
         // ...⏎
     }⏎

Expected
The two variations were similar, but not identical. They differ by one space.
I'm not sure what is expected. I'm guessing that the "Visual" variant should have produced something like:
 fn main() {⏎
-    if lorem_ipsum && dolor_sit && amet_consectetur && lorem_sit && dolor_consectetur && amet_ipsum && lorem_consectetur⏎
+    if lorem_ipsum && dolor_sit && amet_consectetur && lorem_sit && dolor_consectetur && amet_ipsum⏎
+        && lorem_consectetur {⏎
         // ...⏎
     }⏎

However, there's been some consolidation of configuration options that resulted in all of these things being covered by indent_style, so it's possible that this is not to be part of indent_style.

I think this is mostly as expected. Visual vs block indent is about how many spaces we indent by. Block indent should always be 4 spaces, visual indent aligns with the previous line (in this case, 3 spaces because the && gets aligned with lorem_....
We probably could leave the opening brace on the same line in visual indent mode because there is one space difference between the condition indent and the body indent, but actually a newline before the brace probably makes things clearer.

You said it's "mostly as expected", and the only open question is what to do with the brace. You think it's more clear to have it on a new line (like it is now), and I'm not strongly in favor of it being on the same line for "Visual". I placed it on the same line because that more closely matches the other examples of formatting for "Visual".
Unless someone is strongly in favor of having the brace on the same line it seems like this should be closed as by design.


eror

i trying to use this but getting error

Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "C:\Users\Danil\AppData\Local\Programs\Python\Python311\Scripts\tiktok-uploader.exe_main.py", line 7, in
File "C:\Users\Danil\tiktok-uploader\src\tiktok_uploader\cli.py", line 20, in main
result = upload_video(
^^^^^^^^^^^^^
File "C:\Users\Danil\tiktok-uploader\src\tiktok_uploader\upload.py", line 41, in upload_video
auth = AuthBackend(username=username, password=password, cookies=cookies)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Danil\tiktok-uploader\src\tiktok_uploader\auth.py", line 39, in init
raise InsufficientAuth()
tiktok_uploader.auth.InsufficientAuth:
Insufficient authentication:
> TikTok uses cookies to keep track of the user's authentication or session.

Either:
    - Use a cookies file passed as the `cookies` argument
        - easily obtained using https://github.com/kairi003/Get-cookies.txt-LOCALLY
    - Use a cookies list passed as the `cookies_list` argument
        - can be obtained from your browser's developer tools under storage -> cookies
        - only the `sessionid` cookie is required

but i fill txt file
(like this:
xxxxxxxxxxxxx
xxxxxxxxxxxxx)

The text file should be filled with your cookies. I would recommend the top option which it gives you

Use a cookies file passed as the cookies argument
- easily obtained using https://github.com/kairi003/Get-cookies.txt-LOCALLY

If you are still getting this error, this means that you are not passing the file path to 'upload_videos'.
The program needs to know where to get the cookies.


Fix for '[HMR] You need to restart the application!' on server sided error

When you make an error (e.g. undefined variable) somewhere in the server.js, you need to restart the application. To prevent this you should only restart the server when there's no errors.

@crosscompile does this happen to us too?
cc @thelarkinn any ideas about what would break HMR ?

Note: This is for server sided errors only.
Try generate an error in the server.js file. With a fresh Razzle project it will log the [HMR] You need to restart the application! message

ReferenceError and SyntaxError both block HMR for me on the server-side, with and without this patch. I never end up in the catch()

My bad. I didn't include the whole solution. It should work now.

@jaredpalmer did this actually work for you? It didn't make a difference for me. HMR was erroring before it called module.hot.accept

@crosscompile is investigating this today.

This is working for me locally, nice stuff @Bram-Zijp!
@gregmartyn are you sure you have the entire patch?  Initially I missed changing the server import to a require and for some reason that allows the server to reload.
let app = require('./server').default;

I did something similar. Tried again and it's working. Thanks!


httpserver/all: Clean up and standardize request URL handling

1. What issue(s) is this pull request related to?
I'm hoping this will address issues with #1624, #1584, #1582, and others.
2. What does this change do, exactly?
The HTTP server now always creates a context value on the request which
is a copy of the request's URL struct. It should not be modified by
middlewares, but it is safe to get the value out of the request and make
changes to it locally-scoped. Thus, the value in the context always
stores the original request URL information as it was received. Any
rewrites that happen will be to the request's URL field directly.
The HTTP server no longer cleans /sanitizes the request URL. It made too
many strong assumptions and ended up making a lot of middleware more
complicated, including upstream proxying (and fastcgi). To alleviate
this complexity, we no longer change the request URL. Middlewares are
responsible to access the disk safely by using http.Dir or, if not
actually opening files, they can use httpserver.SafePath().
3. What documentation changes (if any) go along with this PR?
Nothing of note, except instructions for middleware authors:
Middlewares should NOT do this:
os.Open(filepath.Join(siteRoot, filepath.FromSlash(r.URL.Path)))

But this is safe:
jailedDisk := http.Dir(siteRoot)
jailedDisk.Open(r.URL.Path)

If not opening files, you can use SafePath():
httpserver.SafePath(siteRoot, r.URL.Path)

But SafePath() is good for when you don't need to open the file.
4. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, and functions or non-obvious lines of code
[x] I am willing to help maintain this change if there are issues with it later

I'm considering having SafePath() take the entire *http.Request rather than just a string (so right now you have to pass req.URL.Path) - but it's not a big deal.
This is a big change, but the highlights are:

The only context key relevant to path rewriting is httpserver.OriginalURLCtxKey ("original_url") which stores a copy of the original url.URL value before any middlewares even see the request.
The HTTP server no longer sanitizes paths.
http.Dir or httpserver.SafePath() should be used by middlewares that want to access the disk.
Improved the handling in the static file server as well.
Overall, this should lead to much simpler code and fewer problems. (I hope. Please test.)

I think this provides a much more straightforward way of dealing with OriginalURLCtxKey which is great.

@tw4452852 Feel free to approve (or request changes to) the PR when you have a chance. I can get this out later today if so. Thanks so much for your time!

LGTM.


Feature/variadic options

Addresses #37.

Nice work @djbe. This looks great, just left a question above and this looks good to go.

The only thing I'm stuck with is unit tests, as the current ones directly call the parser, and this is built on top of it.

@djbe If you'd like to write some tests, you could just invoke VaradicOption and call parse providing an ArgumentParser with example arguments. Then you could assert that the result is correct.

Awesome, nice work here @djbe. I've merged these changes and I'll try make a release later today. I appreciate the PR, thank you for adding these changes.

Np, thank you for the project! 👍


Translate tasks/manage-gpus/scheduling-gpus/ into Japanese

This is a Feature Request
What would you like to be added
Translate tasks/manage-gpus/scheduling-gpus/ into Japanese.
Why is this needed
This page has not been translated.
Comments
/language ja
/assign

/close


Support for hoisting in rotations

Hi folks.  Is there any plan for, or existing work on, implementing hoisting in SEAL? That is, ordering the constituent parts of the rotation algorithm (for CRT batched plaintexts) so that some of those parts can be reused (instead of recalculated) in subsequent rotations? This is described in Section 5 of Faster Homomorphic Linear Transformations in HELib by Halevi and Shoup.
Hoisting would be very useful to me. I am considering implementing it myself, but (what I believe is) the relevant function is a bit... involved, so I don't want to dig in until I'm sure no one else has done it already.
Or perhaps there's a way to achieve hoisting with the current interface that I have missed? If so, please let me know!
Thanks in advance and thanks heaps for your work on SEAL.

In HElib, hoisting is useful when you want to perform different rotations on the same ciphertext. It is faster than previous methods because "breaking into digits" (namely, decomposition in SEAL) is really time consuming. It is time consuming in HElib because all polynomials are kept in DoubleCRT form (similar to the RNS NTT form in SEAL) and requires transformation before being "broken into digits". It is an HElib-specific optimization, and is unnecessary in SEAL.
In SEAL BFV, which, I assume, is the scheme you are interested in using, these operations are different from HElib. First of all, ciphertexts (polynomials) are kept in RNS form rather than RNS NTT form. That means no inverse NTT transforms is required during decomposition. Decomposition therefore has negligible computational overhead. Introducing hoisting to SEAL leads to extremely small benefit. My suggestion is to use the rotation in SEAL as you wish even on the same ciphertext.
In SEAL CKKS, ciphertexts are kept in RNS NTT form. Within rotation, a ciphertext need to be converted to RNS form with inverse NTTs. If you want to perform different rotations on the same ciphertext in CKKS, you will have to tweak the code by yourself. This special usage does not align with our goal to design a easy-to-use API at the moment. Besides, those inverse NTTs have limited contribution to the overhead of rotation. Also, the tweak is not complicated at all.

Thanks heaps for the clarification, Wei.


refactor(module: graph): refactor some apis and support to disable animations

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
Break Changes

Before Method
Current

autoFit()
fitCenter()

nzShowArrow
removed(Default is shown)

Features

support custom edges
support nzNoAnimation

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[x] Yes
[ ] No

Other information

Useage

support zooming and disabling animations
<nz-graph nzNoAnimation nz-graph-zoom [nzGraphData]="data">
</nz-graph>

Problems still not resolved

performance of animations
minimap support(including performance and styles)

@Airblader could you please show us how you use the graph component? If the problem still exists, we can fix it in this PR.

It would also be nice to have an API to re-render / re-layout the graph. I need this for nodes which are interactive and can change in size when the user interacts with it. I currently trigger the re-render by calling setData again. Even cooler would be if nz-graph observed size changes of nodes itself and updated the graph accordingly, but I'm not sure how easily that can be achieved, so an explicit re-render / re-layout API would also be OK.

FWIW, I've written this directive which will do this automatically, but you can see that it would be nice if I could just trigger a re-layout rather than calling setData, and also if nz-graph could (maybe just optionally) do this, it'd be even better.
/** Observes the host for resizes and relayouts the parent nz-graph when it happens. */
@Directive({
  selector: '[nodeUpdateOnResize]',
})
export class NodeUpdateOnResizeDirective implements OnInit, OnDestroy {
  private readonly destroy$ = new Subject<void>();

  constructor(
    @Optional() private readonly nzGraph: NzGraphComponent,
    private readonly elementRef: ElementRef,
    private readonly cdRef: ChangeDetectorRef
  ) {
    if (!this.nzGraph) {
      console.warn(`Failed to inject host nz-graph component.`);
    }
  }

  public ngOnInit() {
    this.createResizeObserver()
      .pipe(
        distinctUntilChanged((prev, curr) => {
          const { width: prevWidth, height: prevHeight } = prev;
          const { width: currWidth, height: currHeight } = curr;
          return prevWidth === currWidth && prevHeight === currHeight;
        }),
        debounceTime(10),
        takeUntil(this.destroy$)
      )
      .subscribe(() => {
        // FIXME: It would be nice if ng-zorro had a "trigger a re-layout" API
        this.nzGraph?.nzGraphData?.setData(this.nzGraph?.nzGraphData?.dataSource);
        this.cdRef.markForCheck();
      });
  }

  public ngOnDestroy(): void {
    this.destroy$.next();
    this.destroy$.complete();
  }

  private createResizeObserver() {
    const stream$ = new Subject<DOMRectReadOnly>();
    // Remove `as any` after https://github.com/microsoft/TypeScript/issues/37861 is merged
    // tslint:disable-next-line:no-any
    const ResizeObserver = (window as any).ResizeObserver;
    if (ResizeObserver) {
      const resizeObserver = new ResizeObserver(entries => {
        for (const entry of entries) {
          if (entry.target === this.elementRef.nativeElement) {
            stream$.next(entry.contentRect);
          }
        }
      });

      resizeObserver.observe(this.elementRef.nativeElement);
      this.destroy$.subscribe(() => resizeObserver.disconnect());
    }

    return stream$;
  }

}

FWIW, I've written this directive which will do this automatically, but you can see that it would be nice if I could just trigger a re-layout rather than calling setData, and also if nz-graph could (maybe just optionally) do this, it'd be even better.

@Airblader Cool, I will check your comments and I think some of thems really should be supported by the component.

One more thing, when I use something like nz-tabset or nz-list inside a custom node, I need to set its z-index to 1 or something for it to show up. I'm not entirely sure why this happens (didn't check since the solution is so easy), so also not sure if anything can be done for that.

@simplejason Another couple things:
nz-graph will throw a bunch of errors if the window is so small that the host element has zero dimensions. I think it should either throw a single, reasonable error, deal with the error, or, as a simpler fix, just include this:
nz-graph {
  // This prevents errors from being thrown if the window is so small that there's no space to render the graph
  min-height: 1px;
}

I've also had to add this style in order for a box-shadow on my custom nodes to work. I didn't observe any negative side effects, so not sure hidden overflow is needed in nz-graph to begin with?
.nz-graph-node-rect {
  // This is needed for box-shadows on the nodes to work
  overflow: visible;
}

And finally, when I use custom nodes, there's still styling on the nodes. I had to add the following to get rid of them so that only my custom node is visible. I'm not sure whether this is intended or not?
.nz-graph-node-wrapper {
  border: none;
  background: none;
}

I'm also encountering an issue where if a node is partially off-screen and I e.g. hover over it, the browser seems to not re-render the entire object (presumably because it's not visible), and subsequently panning the node into view it hasn't rendered correctly. This is fixed once I hover over the node again after it's on-screen. I'm assuming this is more of an issue with d3 or even the browser and not ng-zorro, though. :-/
Here's two pictures to demonstrate it. One picture is what the node looks like fully rendered, the other one is what it looks like when it was rendered while partially off-screen and then panning it into view.

About that directive I've shown above, I've had to modify this to work in a different way. When using this on a custom node that can expand or collapse, it only worked reliably for expand, but not collapse. The reason is that the zone becomes stable before the directive can update the data, and since nz-graph waits for the zone to be stable to auto resize nodes this won't happen (until some later update happens).
The only way I could make that work is calling detectChanges from a parent of nz-graph at least one tick after having updated the data.
Since the design above was also suboptimal because all nodes could cause frequent concurrent updates, my directive now emits on an output instead so that these events are routed through my parent component which then performs the data update and the detectChanges call.


Pass parameter to node-gyp for different C library

Container 1:

Node Version:  ```
root@dce09bd4ca6c:/# node -v
v10.14.1
root@dce09bd4ca6c:/# npm -v
6.4.1

* **Platform**: ```
root@dce09bd4ca6c:/# uname -a
Linux dce09bd4ca6c 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux*
```**Compiler**:

root@dce09bd4ca6c:
/# cc -v
Using built-in specs.
COLLECT_GCC=cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18+deb9u1' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)

Module: node-sass

container 2:

Node Version: node v8.11.4, npm v5.6.0
Platform: Linux 78f30054eb2c 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 Linux
Compiler:

 # apk info
musl
busybox
alpine-baselayout
alpine-keys
libressl2.5-libcrypto
libressl2.5-libssl
libressl2.5-libtls
ssl_client
zlib
apk-tools
scanelf
musl-utils
libc-utils
libgcc
libstdc++
libc6-compat
ca-certificates
libssh2
libcurl
expat
pcre
git

Module: node-sass

details:

log:

ERROR in ./src/styles/styles.scss
    Module build failed: Error: Missing binding /tests/sound/node_modules/node-sass/vendor/linux_musl-x64-57/binding.node
    Node Sass could not find a binding for your current environment: Linux/musl 64-bit with Node.js 8.x

    Found bindings for the following environments:
      - Linux 64-bit with Node.js 8.x

This usually happens because your environment has changed since running `npm install`.`

Hey all, I'm new to nodejs and node-gyp world. I have a scenario where I need to build machine/container (buildpack-deps:stable) and runtime machine/container (alpine linux) configuration is different. nodejs has native modules, so when I'm trying to use the binary generated by build machine I'm getting failure in run machine (while doing npm start) which is obvious. My question is how should I pass parameter to node-gyp so that it can generate binary as per target os configuration. I checked your repo (I may have missed or overlooked) but haven't seen any parameter that can be passed to node-gyp for different Linux distro.
Note: I'm not interested doing "npm rebuild" or anything as such on runtime containers
Can anyone suggest/help me on that?

There is --target but I don't think that's what you're after. The problem here I'm guessing is that you're compiling in Debian but running in Alpine so you're hitting the musl libc problem (i.e. Debian uses glibc, Alpine uses musl, a compatibility nightmare). The best solution is to be building in a musl environment (cross compiling for musl is a pain in the backside and I'd avoid trying to do it if I were you tbh). Make a special build container with Alpine, put build tools in it (make, g++) and build your addons in there and then ship them into your trimmed-down Alpine container.

@rvagg What about for just downloading a precompiled version? It would be great if we can set override glibc with a flag, as we will be downloading binaries there won't be any build issue.

Node-sass is deprecated.  Would the recommend upgrade to Dart-sass be a possibility?

@cclauss Actually I commented here due the title: Pass parameter to node-gyp for different C library, I'm not even using sass, just want the possibility to download the binaries for other platform/c library.
Also, I noticed that now binaries are called $package.node instead of $package-$arch.node, so we can't have multiple arch binaries as downloading new ones will overwrite current one, may I ask why was that approach preferred?


util/ck_errf.pl: add detection of unknown libcrypto and libssl libs

The list of known libs are readily available in crypto/err/openssl.ec,
so lets use it to figure out if all error function codes belong to
known libs.

This is an alternative for #6452

Heh, you know that if you approve with a change request like that, I will ask you to reconfirm...
Comment looking good?

comment is nice. reconfirm.

Merged.
a21180b70f6372fee836557df187d72f7a91b686 util/ck_errf.pl: add detection of unknown libcrypto and libssl libs

I like the solution.
Just two minor drawbacks (compared with the initial solution, which had other drawbacks):

The error message just says 'unknown' - would be nice if it also said: 'in crypto/err/openssl.ec'.
In case there is no error in at the LIBerr() invocations but in oenssl.ec,  one error line would be sufficient.
On the other hand I see the advantage of the new solution that it can also spot issues with the individual invocations.

 Will fix in a new PR, where I will teach the script to take the same config file option as mkerr.pl.

(also, it seems our Travis script is flawed, or this fault would have been discovered before merging)

These inconsistencies are likely not the only ones, in particular when new sub-libraries/modules are added, given the rather intricate way they are integrated,in the crypto lib with the various meta files that need to be kept in sync. Well, this is supported by various Perl scripts, yet they have their complexity in themselves and non-trivial interactions also with the Makefile.
Would be nice if sub-library/module integration could be defined and managed more centrally, minimizing redundancies.

Would be nice if sub-library/module integration could be defined and managed more centrally, minimizing redundancies.

YES!  Can you open an issue for this?  Let's try to address it in one place with one file.

Done.


feat(signals-preact): useLiveSignal

Resolve #366
This adds useLiveSignal as a way to wrap a signal passed into a component which can change reference.

Oohh interesting. I hadn't thought of this kind of use case before. Thanks for bringing this up!
One thought about this new hook is that it requires the child component (Todo in the Readme example) to handle if its parent might pass in a new signal object as a prop. It seems to me all components might want to call useLiveSignal instead of useSignal to handle getting a new signal object since it can't know how it might be called. Could the number of .values you have to deference depend on how many calls to useLiveSignal your parents have invoked on that signal?
I wonder if there are other patterns we could instead encourage to handle the scenario mentioned in the Readme. It appears there are two signals that hold  a value for which there is another "current" value. Could this "current" value be a signal, i.e. currentDate? The current date depends on the on React state so wherever it is updated the currentDate signal would also need to be updated. So the button would become something like <button onClick={() => { setDisplayed(!on); currentDate.value = !on ? dateA : dateB;}>.
Though having to change state twice (once for React state and another for signal state) isn't great. It'd be nice to just do useComputed(() => on ? dateA : dateB); or something but since on is React state and not a signal, this computed value won't rerun when on changes. This problem makes me think another issue we have is mixing & synchronizing React state and Signal state. I wonder if we should add a hook to help that situation to encourage people to not change signal instances and instead create computed signals to represent the final value. Perhaps something like const [ state, setState, stateSignal] = useSignalState() which looks and behaves like React.useState but also exposes the state as a signal that can be used in things like useComputed (though synchronizing the UI when some UI updates synchronously (UI powered by stateSignal) and others update asynchronously (UI powered by setState) (maybe using useSyncExternalStore could help us here?
I'd be curious if there are other situations where switching signal instances in rendering may be relevant cuz perhaps I need to dwell on it a bit more to better understand it use cases.
Anyways, that's a lot of thoughts. Would love to hear what you think!

Why we cannot do it like that?
import { useComputed, useLiveSignal, useSignal } from '@preact/signals';

// The signal representing props.date can change
// when i.e. someone presses a butotn
function Todo({ date }) {
  const formattedDate = useComputed(() => formatDate(liveDateSignal.value));
  return <span>{formattedDate}</span>;
}

function App() {
  const dateA = useSignal(0);
  const dateB = useSignal(1);
  const on = useSignal(true)

  return (
    <main>
      <button onClick={() => {on.value = !on.peek()}}>
        Toggle
      </button>
    	<Todo date={useComputed(() => on.value ? dateA.value : dateB.value)} />
    </main>
  );
}

I think in most cases when we are writing component powered by signals we should stick with then and do not use it without meaningful reason

@andrewiggins I see your point, I honestly dislike the .value.value consequence of having to access it this way. The main problem here becomes that the reference to the signal isn't safe so maybe just incorporating this in useSignal is the most intuitive way of incorporating this however that probably would need to be stateful i.e. rather than useSignal using useMemo to just create a signal once it would need to create it in state and check whether it's referentially equal on each invocation. WDYT?

@JoviDeCroock maybe it can be solved with eslint plugin for signals that will enforce stable reference to signals


KAFKA-3421: Update docs with new connector features

@ewencp @gwenshap Docs. I also tried to clean up some typos. However, it seems that the we don't have two words without space in between in the source yet they showed up as no space in between in the generated doc.

@Ishiihara It looks like KAFKA-3461 might have already caught the typos I had mentioned to you, I just missed that commit when it happened.

@Ishiihara I had a few suggestions on tweaking wording, but mostly looks good.
Since we don't have pause/resume/restart yet, we may need a follow up JIRA if we don't get those committed and included in this patch. Note that the restart patch is landing right now (but w/o docs), and pause/resume should follow soon.

@ewencp Addressed review comments. Will file another JIRA with the pause/resume/restart APIs.

LGTM, thanks!


Update pkcs11-psa submodule to align with TF-M v1.6.0

Update pkcs11-psa submodule to align with TF-M v1.6.0
Description

The PR to update pkcs11-psa to integrate with TF-M v1.6.0 has been merged. This PR is to have the submodule updated.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks

/bot run checks

/bot run checks

/bot run checks


@superset-ui/switchboard NPM package has no esm or lib directory

The new package @superset-ui/switchboard 0.18.26-1 published on NPM doesn't work.
It has no esm or lib directory.
If I do npm install<EMAIL_ADDRESS>everything works.
JB

Similar trouble with new version of @superset-ui/switchboard
Error:
ERROR in<EMAIL_ADDRESS>8:19-54
Module not found: Error: Can't resolve '@superset-ui/switchboard' in '/app/node_modules/@superset-ui/embedded-sdk/lib'

Reverting to the previous version of @superset/embedded-sdk didn't help.

For those of you who are still having the problem!
I have managed to solve it for now with installing the following package without changing anything.
"@superset-ui/switchboard": "^1.5.0"

Closing this as stale since it's been silent for so long (we're on Switchboard 2.1 now), and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions please re-open this issue, open a new Issue with updated context, or raise a PR to address the problem. Thanks!


Update generate.js

fix the cmd to inject the args as new syntax - deconstruction.
Motivation/Description of the PR

fix the cmd to inject the args as new syntax - deconstruction.
Relates #2538

Applicable helpers:

[ ] WebDriver
[ ] Puppeteer
[ ] Nightmare
[ ] REST
[ ] FileHelper
[ ] Appium
[ ] Protractor
[ ] TestCafe
[ ] Playwright

Applicable plugins:

[ ] allure
[ ] autoDelay
[ ] autoLogin
[ ] customLocator
[ ] pauseOnFail
[ ] puppeteerCoverage
[ ] retryFailedStep
[ ] screenshotOnFail
[ ] selenoid
[ ] stepByStepReport
[ ] wdio

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[ ] Local tests are passed (Run npm test)

please add a test @PeterNgTr


"IMU not found at port" when launching razor-pub-and-display.launch

My Razor SEN-14001 is showing up correctly as /dev/ttyACM0 when I plug it in. I've uploaded the Razor_AHRS firmware successfully, and I'm able to see the IMU chatter when I cat or screen on /dev/ttyACM0. But when I try to run "roslaunch razor_imu_9dof razor-pub-and-display.launch", I get this error: "[ERROR] [1525842655.072800]: IMU not found at port /dev/ttyACM0. Did you specify the correct port in the launch file?"
As far as I know, I've done everything correctly, and data is available on /dev/ttyACM0. The only thing that seems a little weird is that the owner of /dev/ttyACM0 is root/dialout. Maybe it's a permissions problem?
I'm running ROS kinetic on Ubuntu 16.04 LTS.

Figured it out. I needed to add my account to the "dialout" group, in order to have permissions on /dev/ttyACM0.
Resolving.


add: rust program for meters to miles

Why:

Closes #293
What's being changed:
added a rust program that takes input from user at command-line (in meters) and returns the equivalent miles

Hey @chinmaykumbhare,
I just noticed that you are pushing change from the master branch. Highly recommend you to start over and refer to the Make Change Section.
Thank you!!


Changes to cleanup grpc connections on aborting VIs

Changes made in this PR are:

Added a new LV callback for RTSetCleanupProc. This would be used to setup cleanup procs which run when a VI goes to Idle.
Changes in the grpc_client to register a cleanup proc when we create a grpc client and de-register it when we delete the client object.
Now the grpc_client also keeps track of all the client calls that are active. This was needed since we need to cancel all these before we close the client connection.
Changes in the grpc_server to register cleanup proc when we create the grpc server object. Now we pass a deadline of system_clock::now() to the server shutdown call so that we also shutdown any ongoing RPC calls immediately.

@ccifra I am merging this change. If you have any concerns/reviews on this please let us know.


i have an idea for a feature

I often have an issue where i cant find a bit of code when looking through it.
Maybe there could be a feature where you drag a block into search bar of sorts and it highlights all of those blocks in your code.  That'd be very helpful, at least for me.
for example, right now im looking for a part of my code that  starts with "when B button pressed", but i cant find it.  With this feature, I could drag a "when B button pressed" block into the search bar and it would highlight any code that started with it.  of course you should be able to change drop downs and insert other blocks into it if the code youre looking for has those.

Related? https://github.com/microsoft/pxt-arcade/issues/3490

Related? #3490

i didnt see your issue (if you posted yours first) but it seems like we had a similar idea!

Closing this as duplicate of https://github.com/microsoft/pxt-arcade/issues/3490


nereids support date_floor/ceil function

Proposed changes
add date_floor/ceil function
@sohardforaname PTAL, very thanks.
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

@zclllyybb PTAL, thanks

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.24 seconds
stream load tsv:          503 seconds loaded<PHONE_NUMBER>9 Bytes, about 141 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.9 seconds inserted 10000000 Rows, about 346K ops/s
storage size:<PHONE_NUMBER>4 Bytes

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.79 seconds
stream load tsv:          502 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>8 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.11 seconds
stream load tsv:          502 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>8 Bytes


[Feature Request] --embed-info-json option which does not require --write-info-json (or removes the file afterwards)

Checklist

[X] I'm reporting a feature request
[X] I've verified that I'm running yt-dlp version 2<IP_ADDRESS>. (update instructions)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
As far as I can tell, from reading the documentation and doing some experiments, there is no way to embed an infojson without also writing it to a separate file, which will not be deleted afterwards (short of using a custom exec to rm it). It would be nice to have an --embed-info-json consistent with --embed-subs, which would remove the .json file after it has been successfully embedded (and the user has not also specified --write-info-json)

Makes sense. The json embedding was ported from animelover's fork and honestly I havent put much thought into it. I will also add an option to disable the json embedding while keeping both --write-infojson and --add-metadata


Update HACS URL

I updated the HACS Badge URL to the new hacs/integration

Looks like a mistake. I updated the url 🙂


Rag no deep 2

This goes along with @elronbandel 's comment:  (https://github.com/IBM/unitxt/pull/1087#pullrequestreview-2222076506)
Another important implication: metrics are different because internal-variable changes can affect other metrics that expect unchanged instances. This means that the at the point of metrics invocation we should make sure every metric get the original untouched instance.

From this perspective it is not the reposibiliy of the MetricPipeline to restore the instance but the responsibility of whoever invoked that metric. Meaning the unitxt invocation of metrics one after the other.

In other words: unitxt intervenes in python's interpretation, changing 'natural' meaning, only where unitxt is responsible: the launching of metric after metric, assuring for each metric that it is treated as an 'only child' and can change the instance as it sees fit; it is aware and it bears the consequences.. and all -- only for itself, as unitxt encapsulates it from the other metrics.
Other surprising deepcopies, like in InstanceFieldOperator, for each and every invocation thereof, are removed. And so is the deepcopy in ListFieldValues that is surprising, not part of the definition, and not explicitly requested.
All in all, performance is expected to improve, while 'observing the law'..
(in reference to issue https://github.com/IBM/unitxt/issues/987 )

May be re-considered when the excessive deepcopies will start hindering performance, or confuse users by their unexpected interpretation of copy as deepcopy.

Try to profile the performance difference

Going in loops when trying to rebase on main. Will generate a whole new branch from main


Do not append, instead clobber.

I found it much more useful in my fork of npm-hooks, to clobber instead of append the file. Do you agree this should be a supported mode?

Yep you're probably right. Could allow clobbering via option. Not sure what the default should be.
I haven't used this module in awhile. Initially I was wanting to create a module that would track installed modules. A sort of analytics module.

I found an incredibly important use case for this (or hooks in general). We created a far superior postinstall for the purpose of architecture specific compilation, but it could be used for any build step in postinstall. It's called esy.

Parallel builds among all packages.
Caches artifacts across projects (important for native compilation which takes minutes/hours).
Recoverable builds.
Out of source builds - doesn't touch your actual node_modules and write artifacts into them.

Here's what the package.json would look like:
{
  "name": "testtop",
  "version": "1.0.0",
  "scripts": {
    "install": "esybuild"
  },
  "esy": {
    "build": ["your commands here"]
  },
  "dependencies": {
    "esy": "*"
  }
}

Here's where I use my fork of this library to do that. What it does is, it attaches a hook to ensure that only the top level package's post install runs, which kicks of the parallel builds from the top down in a system we control, not npm.


 It is triggered by some esoteric conditions that I would rather just fix than explain further. Essentially, the arrays should contain Element where Element == Element.Element or its contents should be reinterpreted as Element.Element in these methods (the ones based on Contiguous sequences). The latter is more expressive, so I'll try that.
let _ = U32(load:   [] as [DoubleInt<U16>])
let _ = U32.init(   [] as [DoubleInt<U16>])
let _ = U32.exactly([] as [DoubleInt<U16>])

let _ = U64(load:   [] as [DoubleInt<U32>])
let _ = U64.init(   [] as [DoubleInt<U32>])
let _ = U64.exactly([] as [DoubleInt<U32>])

Hm. I suppose I have some other options: I can require T == T.Element in DataInt<T>. Alternatively, I could change all reinterpretation beanches to compare T.Element.size instead (or fiddle with alignment). The former prohibits DataInt<U256> but it is much easier to reason about.

I suspect that requiring T == T.Element is the reasonable and responsible option because any type that declares T != T.Element signals to the world that T is an unsuitable Element type.

Looks like I've already put the T == T.Element constraint on InfiniInt<T>—so there's some precedence for it.

T == T.Element is the way. The type system immediately goes to work and tells me these 3 lines of code are bad. Love it.

Tangentially, I had a design at some point with an additional Section associated type (although I'm not sure it ever made it into the public git history). In that design, the U256.Section == U256 while U256.Element == U64. It's basically a super-Element. It enables things like InfiniInt<U256> and it makes some generic reinterpretation strategies more powerful. But, it's more complicated and the benefit of it is small.


Atom for windows error when install exe

windows 7 sp 1 x64
Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	Update.exe
  Problem Signature 02:	<IP_ADDRESS>
  Problem Signature 03:	5522fa9e
  Problem Signature 04:	mscorlib
  Problem Signature 05:	4.0.30319.36213
  Problem Signature 06:	5348974f
  Problem Signature 07:	10fc
  Problem Signature 08:	6f
  Problem Signature 09:	PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:	6.1.76<IP_ADDRESS>.768.3
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

i'll try zip version now

Hi @rebornishard, could you please share the contents of SquirrelSetup.log?  Thanks.
/cc @paulcbetts

@50Wliu yes, but where i can find it ?
thanks

C:\Users\username\AppData\Local\SquirrelTemp

@paulcbetts  thanks, now i sysmlinks that folder
btw, i can install atom after i reinstall windows, strange
maybe broken windows make error somewhere


Move everything loaded from a CDN into the project to avoid calling 3rd parties.

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>


Fix userData handling for Windows Machine

The Windows userData is in powershell script format, but not the ignition data format. Also Currently the WMCO already include the logic to enforce VM hostname to be set to the same as the Machine name, for Nutanix.

/test e2e-nutanix

@yanhua121 I suspect the nutanix e2e tests are broken:
 INFO[2023-04-24T23:14:59Z] 2023-04-24 23:13:49+00:00 - Creating CSI manifests...
customresourcedefinition.apiextensions.k8s.io/nutanixcsistorages.crd.nutanix.com created
namespace/ntnx-system created
secret/ntnx-secret created
operatorgroup.operators.coreos.com/ntnx-system-r8czl created
subscription.operators.coreos.com/nutanixcsioperator created
nutanixcsistorage.crd.nutanix.com/nutanixcsistorage created
storageclass.storage.k8s.io/nutanix-volume created
Error from server (NotFound): deployments.apps "nutanix-csi-controller" not found
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:79","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2023-04-24T23:14:59Z"}
error: failed to execute wrapped command: exit status 1
INFO[2023-04-24T23:14:59Z] Step e2e-nutanix-operator-ipi-install-nutanix-csi failed after 1m20s.
INFO[2023-04-24T23:14:59Z] Step phase pre failed after 45m53s.

Issue is:
"constraints not satisfiable: no operators found in package nutanixcsioperator in the catalog referenced by subscription nutanixcsioperator, subscription nutanixcsioperator exists"

The nutanixcsioperator is not present in the certified-operators  CatalogSource. Ref: subscription

nutanix test failures are a know issue related to csi, they are not related to this change.
/approve


Fandom cleanup filter suggestion

What filter does this issue target?
https://letsblock.it/filters/fandom-cleanup
What changes should be made?
Fandom's "Gamespot Expert Reviews" section isn't currently blocked by the fandom cleanup filter.

Did you write a uBlock filter solving this?
fandom.com##.reviews
Additional notes
No response

Thanks for your contribution @woodiertexas! It's now available at https://letsblock.it/filters/fandom-cleanup

You're welcome