Create Vdisk with size multiple of 512 fail

Create vdisk with size 7* 512 as shown in payload give the following error

{
  "id": "vdisk3",
  "size": 15,
  "blocksize": 3584,
  "type": "boot",
  "templatevdisk": "ardb:///template:ubuntu-1604",
  "blockStoragecluster": "st"
}

Error
*TRACEBACK*********************************************************************************
Traceback (most recent call last):
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/tmp/actions/vdisk/009f936b6acb5bfa3d09f54960259658.py", line 79, in install
    raise j.exceptions.RuntimeError("Failed to run zeroctl copy {} {}".format(result.stdout, result.stderr))
JumpScale9.errorhandling.JSExceptions.RuntimeError: ERROR: Failed to run zeroctl copy couldn't read source vdisk template:ubuntu-1604's static config: invalid config: blockSize '3584' is not a power of 2, while that is required t=2017-08-29T10:04:09+0000 lvl=eror msg="received invalid etcd config 'template:ubuntu-1604:vdisk:conf:static' (vdisk:'')" module=global caller=source_etcd.go:151
Error: couldn't read source vdisk template:ubuntu-1604's static config: invalid config: blockSize '3584' is not a power of 2, while that is required
Usage:
  zeroctl copy vdisk source_vdiskid target_vdiskid [target_clusterid] [flags]

Flags:
      --config SourceConfig   config resource: dialstrings (etcd cluster) or path (yaml file) (default config.yml)
  -h, --help                  help for vdisk
      --same                  enable flag to force copy within the same nbd servers

Global Flags:
  -v, --verbose   log available information

 ((type:runtime.error)

Is should be multiple of 512 or power if 2 ?
Software Version
5d71c78faa37c0316e4d5f2143e9e6096d8f7fa9

@GlenDC What're the constraints that should be added for the blocksize?

@khaledkbadr the block size of all vdisks is given in bytes and has to be a power of 2, and be 512 or greater. I think that second rule of the rule isn't mentioned anywhere in the /docs folder documentation. But the first rule was already mentioned in https://github.com/zero-os/0-Disk/blob/master/docs/config.md#VdiskStaticConfig. Will also add the second rule to the documentation as well, but the first rule answers your question :)
The error message says the same as the documentation though: blockSize '3584' is not a power of 2, while that is required, so I would have though that is also clear enough in case you didn't read the documentation.
The second rule (be 512 or greater) is not as important and if for some reason you want vdisks to have a lower block size (e.g. 32, 64, 128, 256) I can change that, but it seemed unrealistic to me you would want that. However feel free to create a feature request issue for it if you would ever be in need of it.
The first rule (has to be a power of 2) however has certain implications and I would rather keep it that way. I didn't think it would be an issue as AFAIK block sizes are in our world always expressed in powers of 2. On top of that it's a rule that allows us to take it as an assumption, allowing us to keep code much simpler in certain places.
Failing to adhere to any of both rules will prevent you from mounting the vdisk.

Why you re-open this @khaledkbadr? What is not answered about this question?

In orchestrator we put tag question to mark the issue  as it's required more info, not that it always should be of the type question in itself. This issue still needs to be done in the orchestrator API to return 400 if the blocksize was not a power of 2

This issue still needs to be done in the orchestrator API to return 400 if the blocksize was not a power of 2

Don't forget that it also has to be at least 512 (on top of having to be a power of 2). In theory we could handle block sizes as small as 2, but 512 seemed me already like a very small block size that I made the minimum 512 instead of 2.


benchmarking is inaccurate if started when first filling up queue

to reproduce:

start atum / seedqueue
reset first world preview
start benchmark immediately after first couple queued previews show up

this will cause benchmark number to be greatly inflated, almost 2x in my case.

whatever issue i was having with slow starting benchmarks, i cannot reproduce it anymore, so i'm going to close this for now.


Setdgm hitran

I have added a feature to use the setdgm when using HITRAN/HITEMP database. I note that the user needs to provide the reference partial pressure array since HITRAN/HITEMP use that information. Also, the partition function ratio for T > 3,500 K is assumed to be the value at 3,500 K (in that case, the warning will be issued).
Thank you in advance.

Hello @ykawashima .

HAPI (using TIPS 2020) has Partition functions way above 3500 K for certain species.  (CO goes up to 6000 K I think ? )
In any case, I would strongly advise against using the value of 3500 K if values above 3500K are not defined. Partition function is increasing exponentially with the temperature; you would make critical errors. Better raise an OutOfRange error.

See for instance how it's computed in RADIS https://radis.readthedocs.io/en/latest/auto_examples/calculate_partition_functions_from_tips.html#sphx-glr-auto-examples-calculate-partition-functions-from-tips-py

Hello @erwanp
Thank you very much for pointing it out. I did not realize that the temperature supported by HAPI is different for each species. I will make adjustments. Thank you very much!!

@ykawashima if it's really close to the supported range, should be fine. You could add some quick (but not too dirty) solutions :

check that temperature is only <1% outside of the range; clip if it is ; raise an error if it is not
extrapolate : partition functions can be fitted by a 2 or 3 order polynomial (look at the calculation above); if outside the range you could fit an order 2 polynomial on the tabulated HAPI data; and extrapolate.  Again, raise an error if <20% outside the temperature range

@erwanp Thank you for the suggestion. I agree it would be great to implement a polynomial fit.
I considered this matter and have changed my mind (sorry). I now think that it is better not to officially provide the calculation outside the supported temperature range as it is a bit dangerous as @erwanp pointed out. So I will use the clip just for my environment and implement the polynomial fit in the future official release. Is that fine for both of you?

Yes, very safe!

While creating a test retrieval code for HITRAN/HITEMP, I realized that we first need to make Qr_layer_HAPI capable of JAX. So I will close this pull request for now and reopen it after implementing that. Sorry for the confusion. I really appreciate your suggestions!!


JEI Recipes are glitched

Forge 1.20.1, v47.3.6
Jumbo Furnace v<IP_ADDRESS>
JEI v<IP_ADDRESS>

I'm no longer maintaining 1.20.1, you can fix this by downgrading JEI


2.0.5 is generating multiple refresh requests per refresh cycle

Bug report
Describe the bug
Supabase-js 2.0.5 is generating 2 refresh requests for every refresh timer cycle.  This is with supabase-js, javascript only.
Reverting to 2.0.4 goes back to one request.
Another user is seeing similar multiple refreshes with auth-helpers in nextjs with 2.0.5 and getting refresh token reuse errors after awhile.   Discord discussion 1/2 way and below of user Karbust's related issue:  https://discord.com/channels/839993398554656828/1038545959640117289
To Reproduce
Run supabase-js with a logged in user and onAuthStateChange (optional as network tab shows same issue).
Expected behavior
One refresh request per gotrue-js refresh cycle.
Screenshots
2.0.5 console.logs with 60 second jwt expire. (note 120 seconds does same thing)

2.0.4 console.logs

2.0.5 network tab:

System information
Supabase-js 2.0.5
Multiple browsers
Javascript standalone and Nextjs with auth-helpers.
Additional context
Add any other context about the problem here.

Getting 4 requests each time with @supabase/supabase-js 2.0.5 and @supabase/auth-helpers-nextjs 0.5.1. Tried downgrading to 2.0.4 and 0.4.5, respectively, but same issue.

Believe I found the issue. Was introduced with gotrue-js v2.2.2 - which is the version defined in supabase-js v2.0.5. I'm just not sure how the maintainers want to fix it (rollback a change, or re-write the code to work differently).
Lets say you've set your JWT to expire in 240 seconds.
Here is the flow:

User logs in and _saveSession is called (https://github.com/supabase/gotrue-js/blob/f4d843f5b8a05d7b10e587056749f1841114a5df/src/GoTrueClient.ts#L986)
Inside _saveSession, on line 996, _startAutoRefreshToken is called; and (almost) always passes in a number which triggers a token refresh attempt when your JWT has 10 seconds until it expires. So in our example, it would pass in 230 since that's 10 seconds before the original 240 is up.
The refresh code first calls getSession(). It's doing this so it can grab the session's refresh_token, in order to use it to refresh the access_token. But here is where things go wrong, because of some recently updated code at https://github.com/supabase/gotrue-js/commit/cf0d32c40d67bc1137c603854583a7cec67017e0

In the getSession() code, linked to in number 3 above, it checks if the session is expired. Because of the gotrue-js v2.2.2 code change, this will always be true. Let me explain with an example:
There are three things as part of the hasExpired calculation. session.expires_at, timeNow and EXPIRY_MARGIN.
Lets say expires_at is 3000, that would make timeNow ~2990 (10 seconds till expiry, but maybe less), and EXPIRY_MARGIN is 10 per definition. So, the code is asking the question, "is 3000 less-than or equal-to 2990+10?". This will always be true.

If hasExpired equals true, getSession() will refresh the access token. That's one refresh.
Then getSession returns the session to whatever called it.
In this case it's the _startAutoRefreshToken code; which says, "oh, we have a session? let's refresh the token. That's you're second refresh.

If PR #482 is helping to resolve other issues, and is desirable to keep, then one solution to the current issue is to only call getSession() and be done.
  private _startAutoRefreshToken(value: number) {
    if (this.refreshTokenTimer) clearTimeout(this.refreshTokenTimer)
    if (value <= 0 || !this.autoRefreshToken) return

    this.refreshTokenTimer = setTimeout(async () => {
      this.networkRetries++
      const {
        data: { session },
        error
      } = await this.getSession()
      if (!error && session) {
        this.networkRetries = 0
      }
      if (
        error instanceof AuthRetryableFetchError &&
        this.networkRetries < NETWORK_FAILURE.MAX_RETRIES
      )
        this._startAutoRefreshToken(NETWORK_FAILURE.RETRY_INTERVAL ** this.networkRetries * 100) // exponential backoff
    }, value)
    if (typeof this.refreshTokenTimer.unref === 'function') this.refreshTokenTimer.unref()
  }

Rather than the current code:
  private _startAutoRefreshToken(value: number) {
    if (this.refreshTokenTimer) clearTimeout(this.refreshTokenTimer)
    if (value <= 0 || !this.autoRefreshToken) return

    this.refreshTokenTimer = setTimeout(async () => {
      this.networkRetries++
      const {
        data: { session },
        error: sessionError,
      } = await this.getSession()
      if (!sessionError && session) {
        const { error } = await this._callRefreshToken(session.refresh_token)
        if (!error) this.networkRetries = 0
        if (
          error instanceof AuthRetryableFetchError &&
          this.networkRetries < NETWORK_FAILURE.MAX_RETRIES
        )
          this._startAutoRefreshToken(NETWORK_FAILURE.RETRY_INTERVAL ** this.networkRetries * 100) // exponential backoff
      }
    }, value)
    if (typeof this.refreshTokenTimer.unref === 'function') this.refreshTokenTimer.unref()
  }

This is probably going to get resolved with #564.

I believe this already got resolved. The ticket has just remained open.


feat: detect Prisma 1

Closes: https://github.com/prisma/prisma2-private/issues/121 https://github.com/prisma/prisma2-private/issues/122 https://github.com/prisma/prisma2-private/issues/128

Closes: https://github.com/prisma/prisma2-private/issues/121 https://github.com/prisma/prisma2-private/issues/122 https://github.com/prisma/prisma2-private/issues/128


Stdout undefined. .trim error.

🐞 Describe the bug
Discovered this bug today the first time:

@maxbec @abcfy2 Does anyone know why this might have happened?
It's weird that this started happening just now.
Maybe Vercel changed their API or github changed something about the runtime?

same here

@masonmcelvain Thanks for the fork & fixes! Just switched to it and it works as it should :)
@BetaHuhn Would love you to incorporate those and generally update the project & marketplace extension. Would be willed to sponsor the repo in return :)

@BetaHuhn Just pushing this up :)


GRO-251: Adding Jest tests to new Auctions components

This is mainly to go through and add some react component testing to the components being built out for the new Auctions2 route.

Updated with all the suggested feedback.

Looks A+, thanks for the updates 👍


Re-enabling ignored test AnalyzeHealthcareEntitiesTestWithAssertions

Resolves #21796.
The service team has changed the values in the swagger spec to PascalCase, thus aligning with what is returned by the server:
https://github.com/Azure/azure-rest-api-specs/blob/338ccc7bfc79689760959765543387e58b0e4855/specification/cognitiveservices/data-plane/TextAnalytics/stable/v3.1/TextAnalytics.json#L1884

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


[Feature Request] Frontend UI to show case CAMEL

Required prerequisites

[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[ ] Consider asking first in a Discussion.

Motivation
develop simple web app to showcase CAMEL's core module including agent, role-playing and workforce
Solution
No response
Alternatives
No response
Additional context
No response

maybe refer to other web app solution like openweb ui

Hey @Wendong-Fan when developing the UI for CAMEL, please ensure it aligns with CAMEL Design Library. You can refer to the library here
I can help with the visual and design check after you finish the frontend development.

Hey @Wendong-Fan, I see adding an embedding model on Webflow is possible. I am not sure what's your plan to host the CAMEL demo. (It probably doesn't make sense to add them in CAMEL Docs) Just a heads up, if we want to add the frontend demo on our landing page, it will require a HTML custom code embedding or deploying as iframe. (Referencing to traditional chatbot)

@xinyuguan3 will help with the implementation for model and agent setting part
selector:
model platform type
model type
text input:
model api key
system message
user message
text output:
response from ChatAgent

Finish Frontend
#TODO:
1.Backend terminal API integration
2.Design Library Improvement


Building curl

Hi @nkolban ,
With your config files for building curl for ESP IDF - ESP 32, I could get my code working.
But now, after downloading the newest curl from github, I get this issue:
https://github.com/curl/curl/issues/1827

Would you please help me understand what I am doing wrong and how to use curl with ESP IDF?
I rely on this for my project to work!
Apreciate your help!!

@nkolban possibly related:
Changes made for the next curl release in October will require premade configuration files to have the values of SIZEOF_LONG and SIZEOF_CURL_OFF_T due to curl/curl@80d9e35. If you have any related problems please let us know at curl/curl#1816.

Yes, jay. Thank you! Back to previously curl versions, I was able to build.
But with the new versions, it isn't working, as you saw above!
Best regards.

Howdy guys ... been on vacation for last week ... flying home today.  Normal service/response will resume this evening.

Howdy, again ... sorry tor the delay.  I made the changes recommended by @jay and got a new clean compile.  I have checked in the changes and if we can follow the recipe and try it again, lets see how far we get now.

Thank you @nkolban ! I am going to give that a try and come back to report!

Excellent dear @nkolban !
Thank you for your effort and quick response!
I am very glad to have contacted you, because you have saved my life/file again!
See you!

Howdy @Renata27  he he he ... hopefully not your "life" ...
Glad all is well ... come back anytime with bug reports and we'll try and knock them out quickly and for questions, use the ESP32 forum at esp32.com.
Close this issue when happy.


Incorrect "invalid prop" warning with prop of type Symbol

Version
2.5.16
Reproduction link
https://github.com/seanmcoleman/vuejs-bug
Steps to reproduce
Create simple component with a required prop of type Symbol. Pass a Symbol to this component.
What is expected?
No warnings.
What is actually happening?
A warning is given:
[Vue warn]: Invalid prop: type check failed for prop "symbolProp". Expected , got Symbol.

The warning message itself is wrong. In the message "expected" type is empty (space before comma).

Um...because in this case you are using Symbol polyfill, and vue did not recognize it properly during prop types checking.

@jkzing I didn't explicitly add a Symbol polyfill as this is a new, barebones Vuejs build. From my understanding of the documentation, Vuejs supports Symbol as a prop type out of the box. I can't seem to find any information on a different way to use Symbol prop types.

Seems to be working with native Symbol: https://jsfiddle.net/h7727urk/
When you use a build setup, babel-preset-env probably polyfills Symbol based on the browser targets you are targeting. It's typically sub-optimal to use Symbol polyfills, so if you are only targeting browsers that have native Symbols, make sure to tweak your browser target for babel-preset-env in .babelrc.
Either way, this is not a bug in Vue core, likely a setup issue for the vue-cli 2.x webpack template.

@yyx990803 sounds good, I will try that. Perhaps there is still a bug in how the warning message is generated though.
[Vue warn]: Invalid prop: type check failed for prop "symbolProp". Expected , got Symbol. I think you can see that the "expected" prop type is is rendered blank (right before the comma).


Custom Skeleton-based Dataset

@yysijie ,hello, sorry to interrupt you, when i train the st-gcn model by:
mmskl configs/recognition/st_gcn/dataset_example/train.yaml.
And the result:
Load configuration information from configs/recognition/st_gcn/dataset_example/train.yaml
/home/rihuisun/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv-0.6.1-py3.7-linux-x86_64.egg/mmcv/runner/epoch_based_runner.py:168: UserWarning: Runner was deprecated, please use EpochBasedRunner instead
'Runner was deprecated, please use EpochBasedRunner instead')
/home/rihuisun/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv-0.6.1-py3.7-linux-x86_64.egg/mmcv/runner/base_runner.py:59: UserWarning: batch_processor is deprecated, please implement train_step() and val_step() in the model instead.
warnings.warn('batch_processor is deprecated, please implement '
Traceback (most recent call last):
File "/home/rihuisun/anaconda3/envs/open-mmlab/bin/mmskl", line 7, in
exec(compile(f.read(), file, 'exec'))
File "/home/rihuisun/下载/mmskeleton/tools/mmskl", line 124, in
main()
File "/home/rihuisun/下载/mmskeleton/tools/mmskl", line 117, in main
call_obj(**cfg.processor_cfg)
File "/home/rihuisun/下载/mmskeleton/mmskeleton/utils/importer.py", line 24, in call_obj
return import_obj(type)(**kwargs)
File "/home/rihuisun/下载/mmskeleton/mmskeleton/processor/recognition.py", line 110, in train
runner = Runner(model, batch_processor, optimizer, work_dir,log_level)
File "/home/rihuisun/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv-0.6.1-py3.7-linux-x86_64.egg/mmcv/runner/epoch_based_runner.py", line 169, in init
super().init(*args, **kwargs)
File "/home/rihuisun/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv-0.6.1-py3.7-linux-x86_64.egg/mmcv/runner/base_runner.py", line 88, in init
raise TypeError(f'logger must be a logging.Logger object, '
TypeError: logger must be a logging.Logger object, but got <class 'int'>。
I can't solve the problem，TypeError: logger must be a logging.Logger object, but got <class 'int'>。Looking forward to your reply!

@xiehaizheng Did you slove this problem? I got the same problem

@YeTaoY Sorry. I didn't solve the problem. If you find a solution, I look forward to your sharing

@xiehaizheng Did you slove this problem? I got the same problem

@xiehaizheng I sloved this problem by transforming "log_level" to "logging.Logger" through "logging.getLogger", in /home/rihuisun/下载/mmskeleton/mmskeleton/processor/recognition.py  before "runner = Runner(model, batch_processor, optimizer, work_dir,log_level)"

@YeTaoY Thank you very much

@xiehaizheng I sloved this problem by transforming "log_level" to "logging.Logger" through "logging.getLogger", in /home/rihuisun/下载/mmskeleton/mmskeleton/processor/recognition.py before "runner = Runner(model, batch_processor, optimizer, work_dir,log_level)"
n to solve that problem.
pi
There is another solutiop uninstall mmcv
pip install mmcv==0.4.0


pivCCU remains STOPPED with RPI-RF-MOD

Hello all,
I have been running a CCU3 for quite some time and originally wanted to switch to Docker and run the CCU as a container alongside Deconz and other programs. While researching, I came across pivCCU, which I now wanted to put into operation. In advance I would like to thank you for the great development work.
As hardware I use a RP4 with RPI-RF-MOD installed on GPIO.
Linux raspberrypi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux
Unfortunately I can't get the RPI-RF-MOD to run now and the pivCCU remains in STOPPED state.
I used a pre-built image and put it on a formatted SD card using Etcher.
In the meantime, I've spent a couple of hours trying around, so I've decided to open an Incident.
Let's get to the facts:
 pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.61.6-62
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  unknown
 Board serial:  unknown
 Radio MAC:     unknown
HMIP Hardware:  unknown
 SGTIN:         unknown
 Radio MAC:     unknown
State:          STOPPED

pi@raspberrypi:~ $ cat /boot/cmdline.txt
console=tty1 root=PARTUUID=c4e253d9-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
pi@raspberrypi:~ $ cat /boot/config.txt
....
[all]
#dtoverlay=vc4-fkms-v3d

dtoverlay=miniuart-bt
enable_uart=1
force_turbo=1

dtoverlay=pivccu-raspberrypi

pi@raspberrypi:~ $ systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-12-11 22:30:28 CET; 2min 50s ago
  Process: 636 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
 Main PID: 856 (code=exited, status=1/FAILURE)

Dec 11 22:30:27 raspberrypi piVCCU3[684]: HMIP hardware was not detected
Dec 11 22:30:27 raspberrypi start_container.sh[636]: <12>Dec 11 22:30:27 piVCCU3: HMIP hardware was not detected
Dec 11 22:30:28 raspberrypi start_container.sh[636]: kernel.sched_rt_runtime_us = -1
Dec 11 22:30:28 raspberrypi start_container.sh[636]: lxc-start: lxc: lxccontainer.c: wait_on_daemonized_start: 842 Recei
Dec 11 22:30:28 raspberrypi start_container.sh[636]: lxc-start: lxc: tools/lxc_start.c: main: 330 The container failed t
Dec 11 22:30:28 raspberrypi start_container.sh[636]: lxc-start: lxc: tools/lxc_start.c: main: 333 To get more details, r
Dec 11 22:30:28 raspberrypi start_container.sh[636]: lxc-start: lxc: tools/lxc_start.c: main: 336 Additional information
Dec 11 22:30:28 raspberrypi systemd[1]: Started piVCCU.
Dec 11 22:30:28 raspberrypi systemd[1]: pivccu.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 22:30:28 raspberrypi systemd[1]: pivccu.service: Failed with result 'exit-code'.

pi@raspberrypi:~ $ ls -la /dev/raw-uar*
crw------- 1 root root 236, 0 Dec 11 22:29 /dev/raw-uart
pi@raspberrypi:~ $ dmesg | grep raw
[    0.724130] hid: raw HID events driver (C) Jiri Kosina
[    2.427354] generic_raw_uart: loading out-of-tree module taints kernel.
[    2.430309] pl011_raw_uart fe201000.serial: there is not valid maps for state default
[    2.430436] pl011_raw_uart fe201000.serial: I2C adapter of configured RTC device is not yet initialized
[    2.430444] pl011_raw_uart fe201000.serial: failed to initialize generic_raw_uart module
[    2.476709] pl011_raw_uart fe201000.serial: there is not valid maps for state default
[    2.476822] pl011_raw_uart fe201000.serial: I2C adapter of configured RTC device is not yet initialized
[    2.476831] pl011_raw_uart fe201000.serial: failed to initialize generic_raw_uart module
[    2.498680] pl011_raw_uart fe201000.serial: there is not valid maps for state default
[    2.498790] pl011_raw_uart fe201000.serial: I2C adapter of configured RTC device is not yet initialized
[    2.498797] pl011_raw_uart fe201000.serial: failed to initialize generic_raw_uart module
[    2.557711] pl011_raw_uart fe201000.serial: there is not valid maps for state default
[    2.557821] pl011_raw_uart fe201000.serial: I2C adapter of configured RTC device is not yet initialized
[    2.557828] pl011_raw_uart fe201000.serial: failed to initialize generic_raw_uart module
[    2.571394] pl011_raw_uart fe201000.serial: there is not valid maps for state default
[    2.571518] pl011_raw_uart fe201000.serial: Missing I2C driver of rtc device, trying to load
[    2.571527] pl011_raw_uart fe201000.serial: Requesting module i2c:rx8130-legacy
[    2.608969] pl011_raw_uart fe201000.serial: Detected RPI-RF-MOD, using alternative reset pin
[    2.818232] pl011_raw_uart fe201000.serial: Initialized pl011 device; mapbase=0xfe201000; irq=36; clockrate=48000001
[   14.062106] raw-uart raw-uart: Reset radio module
[   40.624052] raw-uart raw-uart: Reset radio module

pi@raspberrypi:~ $ detect-raw-uart /dev/raw-uart
-bash: detect-raw-uart: command not found
pi@raspberrypi:~ $ dmesg | grep rtc
[    2.571518] pl011_raw_uart fe201000.serial: Missing I2C driver of rtc device, trying to load
[    2.600607] rtc-rx8130 1-0032: Enabling charging of external capacitor
[    2.600946] rtc-rx8130 1-0032: Update timer was detected
[    2.602739] rtc-rx8130 1-0032: registered as rtc0
[    2.603760] rtc-rx8130 1-0032: setting system clock to 2021-12-11T21:29:57 UTC<PHONE_NUMBER>)
[    2.606247] rtc-rx8130 1-0032: Enabling charging of external capacitor
[    2.607827] rtc-rx8130 1-0032: registered as rtc0
[    2.608883] rtc-rx8130 1-0032: setting system clock to 2021-12-11T21:29:57 UTC<PHONE_NUMBER>)

pi@raspberrypi:~ $ sudo detect_radio_module /dev/raw-uart
Error: Radio module was not detected
pi@raspberrypi:~ $ sudo detect_radio_module --debug /dev/raw-uart
Sending HM frame: fd 00 03 fe 00 01 14 1e
Received HM frame: fd 00 0f fe 00 05 01 48 4d 49 50 5f 54 52 58 5f 42 6c 68 c7
Sending HM frame: fd 00 03 fe 01 01 92 1d
Received HM frame: fd 00 0f fe 01 05 01 48 4d 49 50 5f 54 52 58 5f 42 6c e9 c5
Sending HM frame: fd 00 03 fe 02 03 18 12
Received HM frame: fd 00 04 fe 02 05 00 87 3b
Sending HM frame: fd 00 03 00 03 00 12 00
Received HM frame: fd 00 04 00 03 04 03 19 0e
Sending HM frame: fd 00 03 fe 04 01 8c 1d
Received HM frame: fd 00 0f fe 04 05 01 48 4d 49 50 5f 54 52 58 5f 42 6c ec c0
Sending HM frame: fd 00 03 fe 05 03 8a 11
Received HM frame: fd 00 04 fe 05 05 00 07 54
Sending HM frame: fd 00 03 00 06 00 0c 00
Received HM frame: fd 00 04 00 06 04 03 19 4a
Sending HM frame: fd 00 03 fe 07 01 86 1d
Received HM frame: fd 00 0f fe 07 05 01 48 4d 49 50 5f 54 52 58 5f 42 6c ef c3
Sending HM frame: fd 00 03 fe 08 03 24 12
Received HM frame: fd 00 04 fe 08 05 00 87 b3
Sending HM frame: fd 00 03 00 09 00 2e 00
Received HM frame: fd 00 04 00 09 04 03 19 86
Error: Radio module was not detected

My biggest problem is currently, when I flash the SD card with a Raspberrymatic, the LED on the module is permanently red and a connection of devices or the communication to the existing devices no longer works.
Thank you in advance for your time to read through everything and your reply.
Greetings
Christian

I tested the board on a second RPI4 and could not get it to work here either. I conclude that the radio board is defective and therefore close the incident. .


DateRangePicker, locale, i18next

Hi,
I'm using i18next languages to translate dynamically DateRangePicker:
moment.locale(i18n.language);
all days and format are changed with language , but months stay in English.
"react-dates": "16.4.0",
"react": "16.2.0",
"moment": "2.21.0",

@wijdench where in your component are you setting the locale? Is the issue that the text remains in English or that the format remains MMMM YYYY? This is how the month title is formatted --- https://github.com/airbnb/react-dates/blob/master/src/components/CalendarMonth.jsx#L167

Hi,
the issue is that the text remains in english.
i used the locale in render component
  render() {
moment.locale(i18n.language);
return (
<DateRangePicker
  startDate={this.state.startDate}
  startDateId="start_date_id"
  endDate={this.state.endDate}
  endDateId="end_date_id"
  onDatesChange={({ startDate, endDate }) => this.setState({ startDate, endDate })}
  focusedInput={this.state.focusedInput}
  onFocusChange={focusedInput => this.setState({ focusedInput })}
/>
);
}

// yarn add moment
// your locale - current -> turkish
// For german -> import deLocale from 'moment/locale/de';
import trLocale from 'moment/locale/tr';
import moment from 'moment';
render() {
// current -> turkish
moment.locale('tr', deLocale);
return ( <DateRangePicker ........ />);
}

Hi,
Is there any updates in this issue.
thanks for your help.

// yarn add moment
// your locale - current -> turkish
// For german -> import deLocale from 'moment/locale/de';
import trLocale from 'moment/locale/tr';
import moment from 'moment';

render() {
// current -> turkish
// for german -> moment.locale('de', deLocale);
moment.locale('tr', trLocale);

return ( <DateRangePicker ........ />);
}

Thanks! Actually just the locale import fixed this for me: import "moment/locale/en-gb"; - I didn't need to set moment.locale("en-gb").

Guys, how change the input text 'Start Date' and 'End Date'?

Guys, how change the input text 'Start Date' and 'End Date'?

https://github.com/airbnb/react-dates#daterangepicker, look at the input related props.
Those could be,startDatePlaceholderText and endDatePlaceholderText.


Update README.md

add contact info

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.95%.  Consider uploading reports for the commit 61ba32e to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             develop      #28   +/-   ##
==========================================
  Coverage      81.95%   81.95%
  Complexity        88       88
==========================================
  Files             21       21
  Lines            327      327
  Branches          19       19
==========================================
  Hits             268      268
  Misses            54       54
  Partials           5        5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Utilized global usings and organized

Global usings statements are utilized to organize all using statements in the program.cs class

Thank you for the contributions. I am integrating some of the other formatting and code cleanup with another PR. However, at this time, we won't use the 'global usings' feature.


make dependencies more detailed

more noob-friendly ReadMe ;)

The note about creating a C++ project first is not really true - you can select the C++ toolset when instalilng, and I think the readme should reflect that :smile: Otherwise its good.

ah ok, that's just how i fixed the problem ;D i had cmake from chocolatey, but not in PATH, and Visual Studio 2015, but no C++ compiler and it took me forever to figure out why it wouldn't build


Using the common behaviour when use command+shift on text line for osx

On press left+command+shift or right+command+shift it should behave like shift+home or shift+end and select the text
Using home and end events as reference

Please make pull requests against the master branch - that's where all development has to happen first.
When relevant, it can then be cherrypicked for stable branches by release maintainers.

For sure @akien-mga hey sorry for that, unfortunately, the master branch has some issues on my mac I have to take a look why is not compiling right now

I changed the base and force pushed a rebased commit on the master branch.

Thanks!

Cherry-picked for 3.2.2.


 I thought you are a bot that automatically checks everyone's repo.

nah man you were carefully selected for url inaccuracy 🤓

thanks for merging


Cannot connect to IRC server with password

In an attempt to work around #210, I decided to see if I could put my bot through ZNC.
Unfortunately, even though I added the PASS command to the autoSendCommands section of the config, the bot is unable to connect.
As the log output is incredibly sparse, I don't have any debug info for you, sorry.

Update: I noticed that node-irc requires the port in its options object, so I moved it there, and I do now have an error.
error: Received error event from IRC prefix=irc.znc.in, server=irc.znc.in, command=err_passwdmismatch, rawCommand=464, commandType=error, args=[<nick>, Password required]

Figured it out, password is a poorly-documented (but valid) option for node-irc


[BUG] Overflow Issue on Tooltip and Description

Environment
Self-Hosted (Docker)
System
Chrome 108
Version
2.1.1
Describe the problem
There are some overflow issues with the global theme when there might be long random text in the item description. Did some tests and perhaps consider incorporate below styles to the global theme?
.tile-title {
    overflow: hidden;
}

.item-wrapper.wrap-size-large {
    overflow: hidden;
}

.tile-title p.description {
    overflow: hidden;
}

.tooltip-inner {
    overflow-wrap: break-word;
}

Additional info
Before

After

Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

still relevant


Separate Ty and TyKind like in Chalk

Currently Ty just wraps TyKind, but this allows us to change most
places to already use intern / interned.

bors r+


stream returned from b.bundle() should be readonly.

Ensure the output of this method and event match the documentation, per #1044.

@substack not sure why the "$NODE_PATHS" test fails in node 0.8.

My bad for the failure in Node 0.8, not linked to your code at all, fixed in [https://github.com/substack/module-deps/pull/78].

merged in 9.0.5 and fixed the module-deps issue upstream


Update implement-merge-sort.english.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@RandellDawson Could you elaborate?
Also I didn't find any typos in the PR.


Eliminate the horizontal scroller bug in blog page.

I eliminate the blog page horizontal scroller bug for small screen device.
As you seen in the attached video.
As I raised the ISSUE #955
https://github.com/user-attachments/assets/6ee60153-5efd-419b-b907-3a625a50a00e
@sanjay-kv    Please marge it. And don't forget to add all the labels as per ISSUE #955

can you resolve the conflicts

@sanjay-kv Solved. Marge it.

@sanjay-kv    Sir please marge it. Along with all the labels as per ISSUE #955


Update ghcr.io/fluxcd/kustomize-controller Docker tag to v0.9.1

This PR contains the following updates:

Package
Update
Change

ghcr.io/fluxcd/kustomize-controller
minor
v0.8.0 -> v0.9.1

Release Notes

fluxcd/kustomize-controller
v0.9.1
Compare Source
CHANGELOG
v0.9.0
Compare Source
CHANGELOG
v0.8.1
Compare Source
CHANGELOG

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (v0.9.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Implement file uploads

The default app functionality is the ability to upload small binary files like pictures. The user should be able to upload files ( upload limit 5MB? ) using the default UI of the app.

Further ideas / requirements:

show file uploads to the public and private filesystems
we can link to a view for the data on ipfs - public will be viewable, private will be an encrypted blob
display the files in the app
restricted to images


Uncaught TypeError: e.getModifierState is not a function

Description

I think this is not caused by browser extensions, as I have closed all of them that I could.
Reproduce:

Open a repo, and click add new file.
At the input box of filename, select LICENSE from the list:

Gitea Version
latest
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
build
Database
None

I think it's https://github.com/microsoft/monaco-editor/issues/4213

I think https://github.com/microsoft/monaco-editor/issues/4325 is better and they are trying to fix it.

I downgraded to 0.44.0 and am happy with it.

Bug seems to not affect Firefox at least.


[build] Update to latest revisions of upstream layers

Will be updated to include new meta-ros revisions to include https://github.com/ros/meta-ros/pull/809

Also in build-next:
6ea252c1f..e88327c42  build -> build-next


[tsp-client] Add an option to specify an alternate main entry file

Allow specifying a custom entry file, for example: "client.python.tsp"
This will add flexibility for files that contain different client configurations.

Will leave this in the backlog until we get more feedback on whether this is useful


fix: make records serializable

Signed-off-by: Timo Glastra<EMAIL_ADDRESS>

Codecov Report

Merging #448 (30cf1a4) into main (55c0fa0) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #448      +/-   ##
==========================================
- Coverage   85.93%   85.93%   -0.01%
==========================================
  Files         253      253
  Lines        5433     5432       -1
  Branches      804      804
==========================================
- Hits         4669     4668       -1
  Misses        764      764

Impacted Files
Coverage Δ

packages/core/src/storage/BaseRecord.ts
70.58% <ø> (-1.64%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 55c0fa0...30cf1a4. Read the comment docs.


NixOS 20.09: evdi-v1.7.2 fails to build against linuxPackages_5_11

Describe the bug
evdi kernel module fails to build against linuxPackages_5_11.
To Reproduce
Steps to reproduce the behavior:

Add something that depends on evdi (e.g. displaylink, add "displaylink" to services.xserver.videoDrivers list)
Set boot.kernelPackages = lib.mkForce pkgs.linuxPackages_5_11;
Call sudo nixos-rebuild switch

Expected behavior
nixos-rebuild successfully rebuilds and kernel modules that are depending on evdi are working as expected.
Additional context
It fails to build with linuxPackages_5_11 (which refers to 5.11.13 kernel version at the moment, and linuxPackages_latest is pointing to this version) but successfully builds with linuxPackages_5_10 for me.
Here are logs chunks that have the information about the failure:
/build/source/module/evdi_drv.c:96:3: error: 'struct drm_driver' has no member named 'gem_free_object_unlocked'
   96 |  .gem_free_object_unlocked = evdi_gem_free_object,
      |   ^~~~~~~~~~~~~~~~~~~~~~~~
/build/source/module/evdi_drv.c:96:30: error: initialization of 'void (*)(struct drm_device *)' from incompatible pointer type 'void (*)(struct drm_gem_object *)' [-Werror=incompatible-pointer-types]
   96 |  .gem_free_object_unlocked = evdi_gem_free_object,
      |                              ^~~~~~~~~~~~~~~~~~~~
/build/source/module/evdi_drv.c:96:30: note: (near initialization for 'driver.lastclose')
/build/source/module/evdi_drv.c:100:3: error: 'struct drm_driver' has no member named 'gem_vm_ops'
  100 |  .gem_vm_ops = &evdi_gem_vm_ops,
      |   ^~~~~~~~~~
/build/source/module/evdi_drv.c:100:16: error: initialization of 'void (*)(struct drm_device *)' from incompatible pointer type 'const struct vm_operations_struct *' [-Werror=incompatible-pointer-types]
  100 |  .gem_vm_ops = &evdi_gem_vm_ops,
      |                ^
/build/source/module/evdi_drv.c:100:16: note: (near initialization for 'driver.unload')
/build/source/module/evdi_drv.c:100:16: error: initialized field overwritten [-Werror=override-init]
/build/source/module/evdi_drv.c:100:16: note: (near initialization for 'driver.unload')
/build/source/module/evdi_drv.c:114:3: error: 'struct drm_driver' has no member named 'gem_prime_export'; did you mean 'gem_prime_import'?
  114 |  .gem_prime_export = drm_gem_prime_export,
      |   ^~~~~~~~~~~~~~~~
      |   gem_prime_import
/build/source/module/evdi_drv.c:114:22: error: initialization of 'int (*)(struct drm_device *, struct drm_file *, int,  uint32_t *)' {aka 'int (*)(struct drm_device *, struct drm_file *, int,  unsigned int *)'} from incompatible pointer type 'struct dma_buf * (*)(struct drm_gem_object *, int)' [-Werror=incompatible-pointer-types]
  114 |  .gem_prime_export = drm_gem_prime_export,
      |                      ^~~~~~~~~~~~~~~~~~~~
/build/source/module/evdi_drv.c:114:22: note: (near initialization for 'driver.prime_fd_to_handle')
/build/source/module/evdi_drv.c:114:22: error: initialized field overwritten [-Werror=override-init]
/build/source/module/evdi_drv.c:114:22: note: (near initialization for 'driver.prime_fd_to_handle')
/build/source/module/evdi_drv.c:115:3: error: 'struct drm_driver' has no member named 'gem_prime_get_sg_table'; did you mean 'gem_prime_import_sg_table'?
  115 |  .gem_prime_get_sg_table = evdi_prime_get_sg_table,
      |   ^~~~~~~~~~~~~~~~~~~~~~
      |   gem_prime_import_sg_table
/build/source/module/evdi_drv.c:115:28: error: initialization of 'struct drm_gem_object * (*)(struct drm_device *, struct dma_buf *)' from incompatible pointer type 'struct sg_table * (*)(struct drm_gem_object *)' [-Werror=incompatible-pointer-types]
  115 |  .gem_prime_get_sg_table = evdi_prime_get_sg_table,

/build/source/module/evdi_drv.c:115:28: note: (near initialization for 'driver.gem_prime_import')
/build/source/module/evdi_drv.c:115:28: error: initialized field overwritten [-Werror=override-init]
/build/source/module/evdi_drv.c:115:28: note: (near initialization for 'driver.gem_prime_import')
cc1: all warnings being treated as errors
make[4]: *** [/nix/store/bqr9q4zsi01wj2h4qk0j3nbv8fkd4pbg-linux-5.11.13-dev/lib/modules/5.11.13/source/scripts/Makefile.build:279: /build/source/module/evdi_drv.o] Error 1
make[3]: *** [/nix/store/bqr9q4zsi01wj2h4qk0j3nbv8fkd4pbg-linux-5.11.13-dev/lib/modules/5.11.13/source/Makefile:1820: /build/source/module] Error 2
make[2]: *** [/nix/store/bqr9q4zsi01wj2h4qk0j3nbv8fkd4pbg-linux-5.11.13-dev/lib/modules/5.11.13/source/Makefile:185: __sub-make] Error 2
make[2]: Leaving directory '/nix/store/bqr9q4zsi01wj2h4qk0j3nbv8fkd4pbg-linux-5.11.13-dev/lib/modules/5.11.13/build'
make[1]: *** [Makefile:77: module] Error 2
make[1]: Leaving directory '/build/source/module'
make: *** [Makefile:8: all] Error 2

builder for '/nix/store/jp6ldzag8vpxx6zl5s4j3icrhlcilvm4-evdi-v1.7.2.drv' failed with exit code 2

cannot build derivation '/nix/store/rsc3xf6zm5g635z6binjq1ls90hx03z3-kernel-modules.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/r5r3fj6j3sc91cgljrb4w7hxynkrj88r-linux-5.11.13-modules.drv': 1 dependencies couldn't be built

Notify maintainers

@thoughtpolice (linuxPackages_5_11.kernel)
@eyJhb (linuxPackages_5_11.evdi)
@nshalman @abbradar @peterhoeg @eyJhb (displaylink)

Metadata
Please note that I’m using linuxPackages_5_10 because I couldn’t build it with linuxPackages_5_11.
nix-shell -p nix-info --run "nix-info -m"

system: "x86_64-linux"
host os: Linux 5.10.29, NixOS, 20.09.3834.c7e905b6a97 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.10
channels(root): "nixos, nixos-unstable"
channels(wenzel): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

The channel pin is: https://releases.nixos.org/nixos/20.09/nixos-20.09.3834.c7e905b6a97
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
- linuxPackages_5_11.kernel
- linuxPackages_5_11.evdi
- displaylink
# a list of nixos modules affected by the problem
module:

https://github.com/NixOS/nixpkgs/pull/119664 fixed in newer version of evdi.

@unclechu appreciated if you have the time to test it out ;)

This should be merged now, please try again and reopen if the issue persists. :)

@eyJhb sorry, I was busy to test it, but I’m planning to. Do you know if this is going to be backported to release-20.09?

@eyJhb sorry, I was busy to test it, but I’m planning to. Do you know if this is going to be backported to release-20.09?

Sorry, I will reopen this again. Didn't think about 20.09. I will just check what the best way is to go about that :)

@unclechu  I have opened a backport PR, can you test it out? https://github.com/NixOS/nixpkgs/pull/121176

Backported and everything, should work fine. Closing. Feel free to reopen if there is still a issue!

@eyJhb sorry, I didn’t have time to test this. Now tested against NixOS 20.09, it compiles with latest kernelPackages and works fine after restart :+1:


Use tox Setup + 👷♂Add Github Action for Unit Tests Python 3.7-3.11

Ideally merge #1 first (because this code requires the requirements.txt to be present)

Closed the PR by mistake.


New container mrtrix3 3.0.4

There is a new container by @stebo85, use this command to test:
bash /neurocommand/local/fetch_and_run.sh mrtrix3 3.0.4 20240316

If test was successful, then add to apps.json to release:
https://github.com/NeuroDesk/neurocommand/edit/main/neurodesk/apps.json
Please close this issue when completed :)

@joelleinkauf - can you test if this container works?

Works well now, thank you so much!

Great :) The new verison is now released and is available through the Application menu after clicking on update:

and it's available through the module system:

Thank you for finding this problem and proposing a solution!

Sorry to bother again, but it seems as though the issue is not yet resolved. After module load I tried the command but it again did not find the liblapack3 and showed me again: " ACPCdetect not installed". Do you have any idea why this could be?

Can you post here, which commands exactly you are running? Could it be that you installed ACPCdetect outside of the mrtrix container separately?

OK, so I think I know what's going on: You have acpcdetect installed outside of the mrtrix container and when calling 5ttgen through the module system you cannot see this binary:
acpcdetect needs to be installed inside the mrtrix container. I will try that now.

Ok, can you try again? Before you try your script, can you check that acpcdetect is found and is pointing to  /cvmfs/neurodesk.ardc.edu.au/containers/mrtrix3_3.0.4_20240319/acpcdetect
(base) jovyan@neurodesktop-:~$ ml mrtrix3
(base) jovyan@neurodesktop-:~$ ml

Currently Loaded Modules:
  1) mrtrix3/3.0.4

(base) jovyan@neurodesktop-:~$ which acpcdetect
/cvmfs/neurodesk.ardc.edu.au/containers/mrtrix3_3.0.4_20240319/acpcdetect
(base) jovyan@neurodesktop-:~$

Thank you for your time, and indeed I was wondering that too! Now I tried it like you told me to: "ml mrtrix3/3.0.4" , "which acpcdetect" - and it was pointing to the container path- "/cvmfs/neurodesk.ardc.edu.au/containers/mrtrix3_3.0.4_20240319/acpcdetect", then I tried running 5ttgen normally "5ttgen ..." and I got the same error again: "ACPCdetect not installed".

When I run 5ttgen after that module load I am not getting this error. Can you send me a minimal example that produces this error?

(base) jovyan@neurodesktop-:~$ ml mrtrix3/3.0.4
(base) jovyan@neurodesktop-:~$ which acpcdetect
/cvmfs/neurodesk.ardc.edu.au/containers/mrtrix3_3.0.4_20240319/acpcdetect
(base) jovyan@neurodesktop-:~$ 5ttgen hsvs /home/jovyan/freesurfer-subjects-dir/sub-02_connectome_recon/ 5ttTry.mif
5ttgen:
5ttgen: Note that this script makes use of commands / algorithms that have relevant articles for citation; INCLUDING FROM EXTERNAL SOFTWARE PACKAGES. Please consult the help page (-help option) for more information.
5ttgen:
5ttgen: Generated scratch directory: /home/jovyan/5ttgen-tmp-TNG5C7/
Command:  mrconvert /home/jovyan/freesurfer-subjects-dir/sub-02_connectome_recon/mri/aparc+aseg.mgz /home/jovyan/5ttgen-tmp-TNG5C7/aparc.mif
5ttgen: Changing to scratch directory (/home/jovyan/5ttgen-tmp-TNG5C7/)
Command:  mrconvert /home/jovyan/freesurfer-subjects-dir/sub-02_connectome_recon/mri/norm.mgz T1.nii -stride -1,+2,+3
5ttgen: [WARNING] ACPCdetect not installed; cannot segment anterior commissure

Here is the snippet:
(base) jovyan@neurodesktop-:~$ ml mrtrix3/3.0.4
(base) jovyan@neurodesktop-:~$ which acpcdetect
/cvmfs/neurodesk.ardc.edu.au/containers/mrtrix3_3.0.4_20240319/acpcdetect
(base) jovyan@neurodesktop-:~$ 5ttgen hsvs /home/jovyan/freesurfer-subjects-dir/sub-02_connectome_recon/ 5ttTry.mif
5ttgen:
5ttgen: Note that this script makes use of commands / algorithms that have relevant articles for citation; INCLUDING FROM EXTERNAL SOFTWARE PACKAGES. Please consult the help page (-help option) for more information.
5ttgen:
5ttgen: Generated scratch directory: /home/jovyan/5ttgen-tmp-TNG5C7/
Command:  mrconvert /home/jovyan/freesurfer-subjects-dir/sub-02_connectome_recon/mri/aparc+aseg.mgz /home/jovyan/5ttgen-tmp-TNG5C7/aparc.mif
5ttgen: Changing to scratch directory (/home/jovyan/5ttgen-tmp-TNG5C7/)
Command:  mrconvert /home/jovyan/freesurfer-subjects-dir/sub-02_connectome_recon/mri/norm.mgz T1.nii -stride -1,+2,+3
5ttgen: [WARNING] ACPCdetect not installed; cannot segment anterior commissure

Ok, I think I found the problem. 5ttgen doesn't actually check if acpcdetect is installed, it looks for an environmentvariable called ARTHOME
so setting this:
export SINGULARITYENV_ARTHOME=/opt/acpcdetect_V2.1/

before running 5ttgen works
Can you quickly test and then I will build that into the image

Great, tried it with module load and "export SINGULARITYENV_ARTHOME=/opt/acpcdetect_V2.1/" and it works well now!

Great :) Thank you for confirming. It's released now and incorporated in the mrtrix3_3.0.4_20240320 container and you don't need the export SINGULARITYENV_ARTHOME=/opt/acpcdetect_V2.1/ anymore :)


Fix runner for code_freeze_week tool

Coverage remained the same at 28.42% when pulling 34dfe4fe37a783c9e1e6e16cc177649be56e2c47 on calixteman:fix_runner into 07b15083cd32b2dff07e27677469ac8b82fe0e25 on mozilla:master.


CIF-1287 - Filling the category cache is slow

This is a preparatory PR to clean up some code features before the actual solution.
Verification is not needed.

Description

cleanup of generics

Related Issue
CIF-1287
Motivation and Context
Simplification of code.
How Has This Been Tested?
Unit tests.
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[X] All unit tests pass on CircleCi.
[X] I ran all tests locally and they pass.

@dplaton , thank you.


Support "@validate" decorator

Support @validate() decorator.
@property
@validator((v: string) => v.length < 100)
name: string = '';

// ...

static validate = createValidate();

[ ] Need to update README

-[] Handle optional properties properly
-[] createValidate() should be createValidate(Entity) for future updates.
-[] validate() returns an array, however, it might get more convenient if it throws Error.

Codecov Report

Merging #4 (fdb9aa1) into develop (adcc24f) will increase coverage by 0.09%.
The diff coverage is 97.67%.

@@             Coverage Diff             @@
##           develop       #4      +/-   ##
===========================================
+ Coverage    96.81%   96.91%   +0.09%
===========================================
  Files           12       14       +2
  Lines          220      259      +39
  Branches        54       63       +9
===========================================
+ Hits           213      251      +38
- Misses           7        8       +1

Impacted Files
Coverage Δ

src/Factory.ts
98.50% <96.15%> (-1.50%)
:arrow_down:

src/CustomError.ts
100.00% <100.00%> (ø)

src/DataObjectError.ts
100.00% <100.00%> (ø)

src/Decorator.ts
97.05% <100.00%> (+0.39%)
:arrow_up:

src/ValidationError.ts
100.00% <100.00%> (ø)

src/index.ts
94.11% <100.00%> (+0.36%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update adcc24f...fdb9aa1. Read the comment docs.

Validation for each property is processed in "factory()", and "factory()" may throw ValidationError.


[Bug]: Test image pipeline“error log：ModuleNotFoundError: No module named 'timm”：Unable to generate vectors

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Only towhee/image-embedding-resnet50 and towhee/image-embedding-resnet101 can generate vectors, the rest cannot generate vectors：
pipeline：{    "towhee/image-embedding-efficientnetb5",
"towhee/image-embedding-efficientnetb7",
"towhee/image-embedding-resnet101",
"towhee/image-embedding-resnet50",
"towhee/image-embedding-swinbase",
"towhee/image-embedding-swinlarge",
"towhee/image-embedding-vitlarge" }
error log：
1、
2、
3、
4、
5、

Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):0.3.1.dev18
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

@jingkl I've added package dependencies in requirements.txt. Please test again now.

My environment does not have automatically generated local folders @jaelgu

I started a new environment to install towhee error

blocked by ：#346

Results of the new test：

Finally I installed the appropriate package, but still reported an error

I think we should add a message indicating the success of the vector generation

@jingkl Please open a new issue/enhancement for that.

@jingkl Please open a new issue/enhancement for that.

ok


proc: remove custom celery task states

Original thinking for custom states was that DVC exps would update state during each exp subtask. This should be done if/when needed in DVC and not dvc-task.

Codecov Report

Merging #54 (574b65a) into main (30ae62f) will decrease coverage by 4.66%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #54      +/-   ##
==========================================
- Coverage   86.77%   82.11%   -4.67%
==========================================
  Files          19       19
  Lines         711      710       -1
  Branches       98       75      -23
==========================================
- Hits          617      583      -34
- Misses         75       99      +24
- Partials       19       28       +9

Impacted Files
Coverage Δ

src/dvc_task/proc/tasks.py
100.00% <100.00%> (ø)

tests/test_utils.py
71.42% <0.00%> (-28.58%)
:arrow_down:

tests/proc/test_manager.py
88.88% <0.00%> (-11.12%)
:arrow_down:

src/dvc_task/proc/manager.py
67.82% <0.00%> (-8.90%)
:arrow_down:

src/dvc_task/worker/temporary.py
77.58% <0.00%> (-8.63%)
:arrow_down:

src/dvc_task/utils.py
38.09% <0.00%> (-7.94%)
:arrow_down:

src/dvc_task/proc/exceptions.py
86.66% <0.00%> (-6.67%)
:arrow_down:

tests/worker/test_temporary.py
93.93% <0.00%> (-3.04%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 30ae62f...574b65a. Read the comment docs.


checking rows doesn't work in 1.3.2 and 1.3.3

Clicking on the checkbox for a row does not select it, clicking repeatedly will select all checkboxes.
This is reproducible in the official demo
In my particular case (1.3.3), if I click repeatedly after all rows have been selected, the row I click on is being duplicated.

@alexandrei892 fixed on v1.3.4


Kitura response times include very high outliers

When driven with constant load (on Linux), some of the outlier response times from Kitura are excessive, and there is generally a much higher variance in response times compared to other frameworks.
We should investigate what is causing this.
TODO:  check whether the same behaviour is present on OS X.
Zewo example:
App:  numactl --physcpubind=0,1,2,3 --membind=0 bbmark/swift/zewo/runmany.sh 4
(starts 4 copies of Zewo, sharing cores 0-3)
Driver: numactl --cpunodebind=1 --membind=1 wrk --timeout 30 --latency -t16 -c128 -d60s http://<IP_ADDRESS>:8080/plaintext
Running 1m test @ http://<IP_ADDRESS>:8080/plaintext
  16 threads and 128 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.27ms    2.68ms  81.65ms   95.45%
    Req/Sec     4.28k   549.71     8.45k    76.17%
  Latency Distribution
     50%    1.81ms
     75%    2.29ms
     90%    2.94ms
     99%   16.17ms
  4093018 requests in 1.00m, 304.47MB read
Requests/sec:  68149.47
Transfer/sec:      5.07MB
Kitura example:
App:  numactl --physcpubind=0,1,2,3 --membind=0 /home/djones6/git-projects/bbmark/swift/kitura/.build/release/kitura
Driver:  numactl --cpunodebind=1 --membind=1 /home/djones6/kiturabench/wrk --timeout 30 --latency -t16 -c128 -d60s http://<IP_ADDRESS>:8080/plaintext
Running 1m test @ http://<IP_ADDRESS>:8080/plaintext
  16 threads and 128 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    10.24ms   86.18ms   3.21s    97.52%
    Req/Sec     1.70k     1.58k   11.76k    74.37%
  Latency Distribution
     50%  275.00us
     75%  342.00us
     90%  688.00us
     99%  200.24ms
  1287744 requests in 1.00m, 141.23MB read
  Socket errors: connect 0, read 1287742, write 0, timeout 0
Requests/sec:  21443.97
Transfer/sec:      2.35MB
Wrk uses sampling to derive the latency statistics, so they do not encompass all requests (and so the measure of outliers is not accurate).  In this example, the highest outlier recorded was 3.21 seconds,  although on other runs I've seen >25 seconds.

When I ran the tutorial on github page with Siege, I guess I have found bug in sock.c that could be related to increase in latency?
5 connections appear to be fine:
MacBook-Pro:kitura194 yanli$ siege -b -c 5 -t 30S http://localhost:8090

More than 5 connections and you get Broken pipe:
MacBook-Pro:kitura194 yanli$ siege -b -c 10 -t 30S http://localhost:8090
[alert] Zip encoding disabled; siege requires zlib support to enable it
[error] socket: 3211264 unknown network error.: Connection reset by peer
[error] unable to write to socket sock.c:634: Broken pipe
[error] unable to write to socket sock.c:634: Broken pipe

Hi, thanks for reporting this. It looks like a different problem to me - please can you raise a separate issue?

If it helps narrow it down, I'm seeing similar results in my FastCGI implementation using either Nginx or Apache 2.4 (Event) w/ proxy_fcgi as the HTTP front-end.
Running 1m test @ http://<IP_ADDRESS>
  16 threads and 128 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     1.76s   677.86ms  15.47s    92.04%
    Req/Sec     9.43      8.39    50.00     65.29%
  Latency Distribution
     50%    1.77s
     75%    1.85s
     90%    1.94s
     99%    4.35s
  4393 requests in 1.00m, 2.53MB read
Requests/sec:     73.10
Transfer/sec:     43.19KB```

Latency looks OK to me given the hardware it's running on (two cores of a Xeon E5-2650L v3 @ 1.8ghz) and the fact that this is HTTP->FastCGI->Kitura without benefit of keep-alive on the FastCGI side.

The latency distribution doesn't bother me either... but that max request time is troubling.

Try as I might I can't narrow it down to my FastCGI implementation so I was assuming it was further up the the chain.

I've seen this on both OS X and Linux with 2016-06-06. I didn't test Apache/proxy_fcgi on OS X but given I was seeing it uniformly I didn't think it was Nginx causing the issue.

I'm closing this issue as I believe it was related to delay in accepting new connections under stress conditions.  Implementing keepalive has eliminated these outliers (Kitura response time maximum is now consistently in the 200ms range for Hello World).
If I find any more specific cases of high response times with other workloads / environments, I'll raise more targeted issues.


Proxying to an internal resource using internal and proxy does not serve the correct MIME type

1. What version of Caddy are you running (caddy -version)?
0.9.1
2. What are you trying to do?
Proxy access to a static file using the internal and proxy directives.
3.
5. What did you expect to see?
Expected /redirect to serve /css/style.css with a mime type of text/css.
6. What did you see instead (give full error messages and/or log)?
/css/style.css served with a mime type of text/html, causing CSS to not be parsed.
7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
Clone this repository and follow the instructions in the readme:
https://github.com/adamwathan/caddy-mime-bug

Doing this exact same thing with 0.8.3 does work correctly, for what it's worth.

What happens if you add mime .css text/css to your Caddyfile? (Sorry I know it's dumb.)

Still comes back as text/html:

Oh... that's probably because the URL doesn't have .css in it. Hmmm...

Yeah I tried to look through the source to see if I could figure out what would need to change to get the old 0.8.3 behavior back but not good enough at Go :)
But to me it sounds like the important thing is to treat the value of the X-Accel-Redirect header as the file name, not the URL that then proxied to that file, does that sound right to you?

If I change the file I'm requesting to be /redirect/style.css, then it does load semi-properly but only if I have manually added the mime directive.
It's still giving an error though, because it's being server with two Content-Type headers:

I've updated the repo that shows how to reproduce so that you'll see the double header bug when running it:
https://github.com/adamwathan/caddy-mime-bug

@adamwathan I finally had a chance to check this out, and I pulled your repro repository here and confirmed that it works as expected. (Maybe you didn't build this branch?)

Thanks for making that repo, by the way! Made it easy to confirm.
@tw4452852 Thank you for this! I will probably merge soon.

Ah you're right, I had cloned it down and couldn't get the dependencies installed to build, then pulled it down instead using go get and forgot to pull in the branch.
I am still seeing an issue though, it only works if you have the mime directive specified in the Caddyfile like you mentioned here:
https://github.com/mholt/caddy/issues/1086#issuecomment-243926768
If you pull down the latest version of that sample repo, you'll see the CSS is coming back as text/html again:
https://github.com/adamwathan/caddy-mime-bug/commit/48333943982fe8cb6e5d447bd7f527b05b30a809
If I pass an empty Content-Type header through, Caddy also preserves that instead of determining the content type itself (not sure what should happen here, I just know it happened to work in getting nginx to re-detect the content type on it's own).
Can you think of a way to get Caddy to detect the content type on it's own without having to hardcode the mime directive in the Caddyfile? Wouldn't want to do that for this whole list 😳
https://github.com/laravel/valet/blob/master/cli/mimes.php

Hmm, well I can tell you that Go won't detect the mime type for ALL of those on its own... but we can probably have it look for the Content-Type as a special case. @tw4452852 what do you think about that? https://golang.org/pkg/net/http/#DetectContentType maybe?

@mholt Honestly not too worried about catching all of them, haha... Whatever I had working in 0.8.3 was fine 😊
I'm sure it would work well enough if it was possible to tell PHP FPM to send no content type header at all, but unfortunately the best I've been able to do is send an empty Content-Type header, which does trigger FPM not to send the default text/html value, but I can't figure out how to suppress it entirely.

Man, a lot changed between 0.8.3 and 0.9. I'm not sure which change caused this to happen...
Wait, why does php send the wrong content-type header?

It's not that it sends the wrong content type header really, it's that it is trying to say "hey Caddy can you just deal with this?" by using the X-Accel-Redirect feature.
I could send the correct mime type by detecting it in PHP but it seems like overkill when everything works fine as long as I send no content-type header so Caddy knows to deal with it on it's own.
I did figure out that I can disable the default_mimetype setting in PHP, just not sure what the consequences of that could be. It does make everything work though!
The nice thing about nginx was that I could send a content-type header of "" (empty string) and nginx would interpret it the same as no content-type header being present at all.
Does that make sense? Haha, sorry for all this man 😬

Ok so I think I feel confident that in Valet anyways, we can disable that default_mimetype setting and everything will be fine using the changes from this PR 👍🏻
The goal of what we were trying to do is send Caddy an HTTP response from the PHP proxy that contained only the X-Accel-Redirect header and nothing more, so Caddy would notice and say "Oh PHP wants me to take care of this file, no problem."
The problem was that if we didn't send a Content-Type header, PHP FPM was adding a default Content-Type header, and then Caddy was saying "Oh I see you already have a content-type header, I will keep that."
Nginx would let me explicitly send an empty Content-Type header, and treat it the same as the header not even being sent (who knows if this is even intentional, I just noticed it worked).
Caddy treats an empty Content-Type header as a header, and preserves the value.
I figured out how to not send the Content-Type header at all, which then triggers Caddy to figure it out, and everything works great.
I wish there was a way for me to choose to suppress the default header programmatically, but it seems like I have no choice but to do it PHP-wide at the config level. That sucks, but I think it'll still be fine, because Caddy seems to detect text/html fine for rendered PHP pages even if PHP doesn't send a content-type along anyways.
TLDR with some things tweaked on our side, I think this PR solves our problem. Thanks so much to you guys for helping us on this one!

Phew, okay, we'll start by merging that PR and then see about improving it from there. Let me know if it's still not quite right... thanks!

We've merged the fix but since it's not 100% perfect yet I will mark this as deferred so we can remember to pick this up later. Thanks.

Is there any way to keep upstream Server header without appending Server: Caddy?

Is there any way to keep upstream Server header without appending Server: Caddy?

You may modify the source.
https://github.com/mholt/caddy/blob/master/caddyhttp/httpserver/server.go#L389


[Usage]: doubt on computational complexity

TODO: The current hashing function is O(L^2). We should optimize this in the future.
return hash((tuple(self.data.get_token_ids()[0:num_tokens]), self.lora_int_id))
May I ask why is O(L^2) here?

For a string prompt, we do not hash it incrementally.
For example, (for illustrative purpose), string ABCD is hashed: hash("A"), hash("AB"), hash("ABC"), hash("ABCD") to produce 4 hash values and used for prefix detection.
This is O(L^2) because each hash is O(L). However, the hash can be computed incrementally, namely: hash("AB") = incremental_hash("B", hash("A"))

btw if you're interested in fixing this, see https://github.com/vllm-project/vllm/issues/4536


🐛 Bug Report: Todo Search Filter in Entity page

📜 Description
In Backstage Application, When the Users select any of the Entity, when the user navigate to Todo , We are getting 400 error if no todos are available while filtering it.
👍 Expected behavior

👎 Actual Behavior with Screenshots
We are getting 400: InputError

👟 Reproduction steps
Step:

Go to Live Backstage Application https://demo.backstage.io/catalog/default/component/playback-order/todos
Now user can able to see the catalog Page
Click any of the entities
In entity page, In top we have some tabs(Overview, Ci/Cd, etc...)
Navigate to TODOS
User can able to see the filter options in the todos page(Default its empty)
Enter some values in filter options(Expected: No result found, Actual: 400: InputError)

📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

I have also seen this same error occurring to me when I try to reproduce this steps.

have a look => https://github.com/backstage/backstage/blob/master/plugins/todo/README.md

@Rugvip , can you help me with how to encode filters here.
https://github.com/backstage/backstage/blob/8f48d188a12616d20aa2df95f9213a4220e173b8/plugins/todo/src/api/TodoClient.ts#L70
filter should be "text%3D%2Axyz%2A" but instead fetching "text%3Dxyz"

Thank you for the report! I ended up fixing this directly in #19321, sorry 😅. It turned out to be a quite weird issue where everything is URL encoded as much as it needs to be on the frontend, but the request is still rejected by the OpenAPI validator. Perhaps there's something we can configure in how the OpenAPI validators to make them more permissive? CC @sennyeya

@Rugvip There's an 'allowReserved' option for parameters that adds non-URL encoded characters that I use in catalog-backend. https://swagger.io/docs/specification/describing-parameters/
I'm on mobile right now so can't share a link, but it should be on the filter parameter there as well.

@sennyeya nice, thank you! 👍 As mentioned in the PR it would be nice to have some form of broader solution, but I think it's enough to add that option where needed for now.


install dependencies of local project

Would it be possible to add a command line option that would install all the dependencies of a module (but not the module itself) and if that could work for the project in the "current directory"?
That would be very useful for someone who clones a repository of a module and wants to test the module (and maybe even patch it), but does not want to install it.
panda installdeps .

This is what i've been using for Travis-CI testing:
perl6 -MJSON::Tiny -e 'shell("panda install "~from-json("META6.json".IO.slurp).<depends>)'

There's a pull request open https://github.com/tadzik/panda/pull/128 to do this.

Pull request now merged; thanks!


bugfix:  ZK 加密工具多操作系统路径判断错误 (closed #1214)

Codecov Report

:exclamation: No coverage uploaded for pull request base (V2.2.32-rc@82c8b09). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             V2.2.32-rc    #1216   +/-   ##
=============================================
  Coverage              ?   73.28%
=============================================
  Files                 ?      357
  Lines                 ?    24029
  Branches              ?        0
=============================================
  Hits                  ?    17609
  Misses                ?     6420
  Partials              ?        0

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


[WIP] Fixing error on docs command

Please describe the changes this PR makes and why it should be merged:
Status

[ ] Code changes have been tested.

Semantic versioning classification:

[ ] This PR includes new feature, methods or parameters

[ ] This PR includes breaking changes (feature, methods, parameters removed or renamed)

[ ] This PR only includes non-code(typo, documentation etc.) changes

tested with zero width space, it works.

bot sends Nothing Found even source returns normally


workshop page for reykjavik, rm from Planned

adding workshop page for Reykjavik, removing it from Planned. Typeform link is correct (i.e. a new one)

I will confirm financing very soon but let's merge it already. Thanks!


Update warning message for Data Packages

When publishing a Data Package that has no mappings, the IPT issues a warning:

Source data or Darwin Core mappings missing. No data archive generated. Please note that this is perfectly normal if you are publishing a metadata-only resource.

I think this should at least be updated to:

Source data or Data mappings missing. No data archive generated. Please note that this is perfectly normal if you are publishing a metadata-only resource.

Note: "Data Mappings" is name we gave the heading. The last sentence could maybe be removed too.

Thanks Peter.
I think we have to forbid publishing datapackage resources without mappings.

Deployed

Confirmed fixed.

When trying to publish without any resources, you are stopped and get:

Before you can publish a resource you must provide data mappings.

When trying to publish with some but not all resources, the publication starts but fails with:

Publishing version #4.0 of resource test failed: Archive generation for resource test failed: All required schemas must be present: [deployments, media, observations]


Sample player crashes in _64klang_Render (

Hello,
I am facing an issue when trying the sample player.
An exception is raised in _64klang_Render (access violation while reading at location 0x0000000000000010).
I am using Windows 10 / VS 2019.
I am investigating ... But if you have any idea it would be really helpful.
Thank you very much, and below is an extract of the stack, if it can help.
Player.exe!OSCILLATOR_tick(SynthNode * n) Ligne 1598	C++
Player.exe!BQFILTER_tick(SynthNode * n) Ligne 1771	C++
Player.exe!VOICEROOT_tick(SynthNode * n) Ligne 1142	C++
Player.exe!VOICEMANAGER_tick(SynthNode * n) Ligne 1099	C++
Player.exe!NOTECONTROLLER_tick(SynthNode * n) Ligne 561	C++
Player.exe!MUL_tick(SynthNode * n) Ligne 2106	C++
Player.exe!CHANNELROOT_tick(SynthNode * n) Ligne 532	C++
Player.exe!NOTECONTROLLER_tick(SynthNode * n) Ligne 561	C++
Player.exe!GLITCH_tick(SynthNode * n) Ligne 3701	C++
Player.exe!GLITCH_tick(SynthNode * n) Ligne 3701	C++
Player.exe!GLITCH_tick(SynthNode * n) Ligne 3701	C++
Player.exe!GLITCH_tick(SynthNode * n) Ligne 3701	C++
Player.exe!MUL_tick(SynthNode * n) Ligne 2106	C++
Player.exe!MUL_tick(SynthNode * n) Ligne 2106	C++
Player.exe!_64klang_Render(float * dstbuffer) Ligne 748	C++

Looks like node for OSCILLATOR_UDETUNE is null.
By adding a check in the NODE_CALL_INPUT it does not crash any more, but the player is not acting very good ... Stopping the music after a few secs :(

fixed :)

i assume you used the provided demo song. i forgot to update the demo song with an export of the lastest version of 64klang in which i changed (added an input) the oscillator node. please pull and test again.

As discussed on Slack, it seems like it is an issue with VS 2019 compiler/linker.


Change return value on PCD_DumpVersionToSerial if comm fails

Hi Folks,
While testing the library on an ESP32, I found out  PCD_DumpVersionToSerial which is very nice function, because it allows us to see weather or not the comms are working correctly.
I'd like to add a different return value if the test fails, so that the program flow could be easily changed.
If it's ok for everyone I could make a pull request or send a patch file here.
Cheers,
Carlo

Hi,
PCD_DumpVersionToSerial is just for debugging by serial output. So no return should be provided.
Best

@CarloMara I thought about your suggestion. I think you want void PCD_Init(); to return the status of the initialization process?
So a change to bool PCD_Init(); where return of true indicates a successful initialization and false an error?
Otherwise you may use bool PCD_PerformSelfTest(); to check the mfrc522.
Best regards

Yes, you stole my words.
From what I gather by looking at some examples PCD_PerformSelfTest(); returns the same thing if the chip doesn't respond or it's an unknown firmware.
I would have imagined that bool PCD_Init(); could give us some finer controls, like telling me that we can communicate, even if it can't detect the version of the firmware.
Thanks,
Carlo

I guess maybe the code from MFRC522::PCD_DumpVersionToSerial is enough:
byte v = PCD_ReadRegister(VersionReg);
// When 0x00 or 0xFF is returned, communication probably failed
if ((v == 0x00) || (v == 0xFF))
return false;
return true;

But maybe there is a better way? Would be good if you can check the mfrc522 documentation. Your pull request will be welcome.

I checked the documentation and I'm not sure I found a better way.
Those that I found:

Status2Reg::ModemState[2:0]: the problem with this it can be in any state, if a PICC is nearby, not just in idle.
ErrorReg: mostly for PICC related errors.
Test buses would be an overkill and for those we have to access to pin AUX1 or AUX2.

Implemented this for PCD_Init at the fork.


fix broken check in case of element not having a ownerDocument property

Hi Thomas,
After running some checks, also the suggested implementation is not giving the right results.
While looking for better implementations the safest seems to be:
if (typeof element !== 'object' || element === null || typeof element.ownerDocument !== 'object' || element.ownerDocument === null )
Slightly verbose, but seems to be closest to what we need. I wonder if we could use element.ownerDocument instanceof HTMLDocument, but I'm not sure that works in non browser context.
For test results, see https://jsfiddle.net/mbsqmedu/1/ against various test scenarios.
The one that will go in the next version will be version checkOne and the suggested implementation is checkTwo.
Thanks for your time!


[DO NOT MERGE] [BEAM-7590] Converting JDBC Pipeline Options Map to PipelineOptions.

There were two representation of pipeline options in JDBC Driver. This will combine them and we will keep only PipelineOptions Class.
This will slightly change the JDBC set command. Previously if we had set an incorrect option it would ignore it until the execution of an actual query; whereas now, it will throw exception if you try to set an incorrect pipeline option.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.


Added parameters to allow insecure forwarding to a local resolver

These small changes allow unbound to be configured to forward requests to another local resolver. The current use case for this is allowing a forward zone for "consul" to "<IP_ADDRESS>@8600" to make use of the dns api provided.
These changes all default to their original values, so there should be no incompatibility with 1.0.0.

Just wanted to check if there was anything else I need to do to move towards getting this merged.
Thank you!


Missing config.js.example

According to doc

Copy config.js.example to config.js and edit appropriately..

We need config.js.example this file, but I can't easy find that.
That must be returned back.

Looks like it was erroneously removed. See #217.


FID evaluation in IRVI benchmark

Hi, thanks for your great work! This is a good contribution. Could you please advise me on how you calculated the FID score for your benchmark?
Thank you!

Hi,
I wonder the same. my guess is that they scaled the numbers by 100. because I tested their pretrained model on traffic dataset and calculated the FID on using both pytorch-fid repo (using batch size 50) and torchmetrics (batch size 1) and here are the numbers respectively, 43.59 and 45.40. So these numbers are pretty close to what they put in the paper which is 0.4425, and if you multiply by 100 = 44.25.
Looking to other FID scores in Table 3 suggests the FID scores are not scaled to [0, 1] but divided by a constant.
This is my guess :) I am not sure whether this is the case or not. Hope the author(s) will elaborate on this.


fix: do not use require.main in cli preset

🔗 Linked issue
Part of implementing #2466
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
The generated server/index.mjs is no longer dependent on the require. I don't think there is a valid way to check if the file is the main with ES modules?
Also, it uses Object.entries for result headers.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Would you please rebase it to v2 branch?
Also trick for ESM main check: https://github.com/unjs/unenv/blob/main/test/node-coverage.ts#L75

Uhh... sorry, need to fix more...


[Do not merge] ARKit prototype

Required Xcode 9 to build, so #2500
Takes the work from https://github.com/lazerwalker/art-on-walls-prototype and integrates it in the simplest way possible. There's a lab option that adds a switch to flip between the normal VIR and the ARVIR.
https://github.com/artsy/eigen/commit/6b81e485ec205ffc8dd9e11fbbed321a5de830d4
https://github.com/artsy/eigen/commit/43e03b266b0e7bbb72477a30194eb1a4a8f34c25

          1 Warning

:warning:
Needs testing on a Phone if change is non-trivial

  Generated by :no_entry_sign: Danger

Shockingly - deployment is a tad complex.
See: https://circleci.com/gh/artsy/eigen/tree/beta

xcodebuild -list -project Artsy.xcodeproj is went from a second or two, to a minute or two ( https://twitter.com/orta/status/945814848096612352 ) causing me to update a bunch of ENV vars: FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT and FASTLANE_XCODE_LIST_TIMEOUT
Something to do with code signing

[16:36:17]: ▸ ❌  [BCEROR]Code Signing Error: "Artsy" requires a provisioning profile with the Push Notifications and Associated Domains features. Select a provisioning profile for the "Debug" build configuration in the project editor.
[16:36:17]: ▸ Clean Succeeded
[16:36:18]: ▸ Building Artsy/Artsy Stickers [Store]
[16:36:18]: ▸ Check Dependencies
[16:36:25]: ▸ Processing Info.plist
[16:36:28]: ▸ Touching Artsy\ Stickers.appex
[16:36:29]: ▸ Signing /Users/distiller/Library/Developer/Xcode/DerivedData/Artsy-fsevwkngbhoaihabyoyfvqcsmzrs/Build/Intermediates.noindex/ArchiveIntermediates/Artsy/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Artsy\ Stickers.appex

and
[16:34:32]: $ set -o pipefail && xcodebuild -workspace ./Artsy.xcworkspace -scheme Artsy -destination 'generic/platform=iOS' -archivePath /Users/distiller/Library/Developer/Xcode/Archives/2017-12-26/Artsy\ 2017-12-26\ 16.34.32.xcarchive clean archive | tee /tmp/circle-artifacts.bjXzqJR/gym/Artsy-Artsy.log | xcpretty
[16:36:11]: ▸ 2017-12-26 16:36:11.629 xcodebuild[9023:32204]  DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-13522/DVTFoundation/Utilities/DVTFileSystemUtilities.mm:142
[16:36:11]: ▸ Details:  lstat('/Users/distiller/Library/Developer/Xcode/DerivedData/Artsy-fsevwkngbhoaihabyoyfvqcsmzrs/Build/Products/Debug-iphoneos/Artsy Stickers.appex') failed with errno 2 (No such file or directory)
[16:36:11]: ▸ Function: DVTRecursiveMkdirResult dvt_recursiveMkdir_returningErrorString(NSString *__strong, NSString *__autoreleasing *)
[16:36:11]: ▸ Thread:   <NSThread: 0x7fc4c1b66dc0>{number = 14, name = (null)}
[16:36:11]: ▸ Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
[16:36:11]: ▸ Cleaning Pods/AFNetworking [Debug]
[16:36:11]: ▸ Check Dependencies
[16:36:11]: ▸ Cleaning Artsy/Artsy Stickers [Debug]
[16:36:11]: ▸ Check Dependencies
[16:36:11]: ▸ ❌  [BCEROR]Code Signing Error: "Artsy Stickers" requires a provisioning profile. Select a provisioning profile for the "Debug" build configuration in the project editor.


Vsphere Docs: No import sections are provided.

What happened?
Other providers include a pulumi import section for each resource.
The vSphere docs are missing this.
It's not intuitively obvious what the resource type is (appears to be of the form vsphere:index/ResourceType:resourcetype
and it's not clear what correct vsphere IDs look like.
So having this documentation would be very helpful.
Expected Behavior
Have import sections for he resources.
Steps to reproduce
Go to the vsphere provider docs and pick a resource, e.g. https://www.pulumi.com/registry/packages/vsphere/api-docs/virtualmachine/
Look for an import section like seen else where (e.g. https://www.pulumi.com/registry/packages/aws/api-docs/iot/thing/#import).
Output of pulumi about
N/A
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

FYI: Import for VM looks like:
pulumi import vsphere:index/virtualmachine:VirtualMachine name /DATACENTER/RESOURCEPOOL/vm/VMNAME

Thanks @MitchellGerdisch. We have added this to our docs quality epic.

Any progress on this? I want to bring our VMWare environment under Pulumi management but am unable to import resources, which is blocking that effort.
The example @MitchellGerdisch kindly provided isn't working for me - I get "error: Preview failed: unrecognized resource type (Read): vsphere:index/virtualmachine:VirtualMachine" when I try that.

Any progress on this? I want to bring our VMWare environment under Pulumi control but not being able to import existing resources is hampering that effort.
The command @MitchellGerdisch kindly provided isn't working for me. When I try that I get "error: Preview failed: unrecognized resource type (Read): vsphere:index/virtualmachine:VirtualMachine"

Ah, I found the problem with the command @MitchellGerdisch posted - it needs to be:
vsphere:index/virtualMachine:VirtualMachine
I figured that out by creating a test VM and looking at the resulting URN in Pulumi.
I can do that for other resources but I don't think I'd ever have figured out the ID format.
Also, I'd prefer not to have to do all this by guessing/trial and error.

@JCBlouin Sorry about the typo and thanks for providing the corrected version.
I'll edit my original comment accordingly.

Since this thread helped get me started, I'll edit this post, adding other resource import type/name formatting which worked for me below.

Datacenter: pulumi import vsphere:index/datacenter:Datacenter dc_name "/DATACENTER"
Cluster: pulumi import vsphere:index/computeCluster:ComputeCluster cluster_name "/DATACENTER/host/CLUSTER"

Another thing is importing resources that require information about other resources. Like trying to import a Distributed Virtual Switch requires providing a datacenter
pulumi import vsphere:index/distributedVirtualSwitch:DistributedVirtualSwitch dvs VmwareDistributedVirtualSwitch-dvs-62
Previewing import (dev):
     Type                                       Name     Plan       Info
     pulumi:pulumi:Stack                        it-dev              1 error
 =   └─ vsphere:index:DistributedVirtualSwitch  dvs  import     1 error

Diagnostics:
  vsphere:index:DistributedVirtualSwitch (dvs-csq):
    error: Preview failed: importing VmwareDistributedVirtualSwitch-dvs-62: error locating DVS: please specify a datacenter

  pulumi:pulumi:Stack (it-dev):
    error: preview failed

The ID for each resource is different too. Some take a UID, some a folder location.

I suspect that this will be fixed by https://github.com/pulumi/pulumi-vsphere/pull/597. I'll add needs-triage as a reminder to check after vsphere has been published with new docs.


Use the 'at' method instead of 'flat' method

The implementation of #119.

Please run grunt to generate output.txt file. That file contains the lengths of resulting characters. Then play with alignment (adding 0, NaN, 'true', 'false', 'undefined' at the start of the expression to reduce number of characters required to get index). For example: (<something>)[9] => (0+<something>)[10]


Blasting every N words

I have to make speed reader .... a set of three words gets highlighted ... how can i achieve this quickly ?

try asking on stackoverflow :)


x/crypto/ssh: interaction between PublicKeyCallback and public key acceptability queries is not obvious

The documentation for PublicKeyCallback says:
// PublicKeyCallback, if non-nil, is called when a client attempts public
// key authentication. It must return true if the given public key is
// valid for the given user. For example, see CertChecker.Authenticate.

A person not familiar with the details of SSH public-key authentication might assume that it works similarly to TLS, unless the x/crypto/ssh API or documentation suggests otherwise. To them, saying that PublicKeyCallback "is called when a client attempts public key authentication" implies that the client is actually trying to authenticate with the public key passed in, i.e. the client actually possesses the corresponding private key and has signed something with it (and the server has verified the signature). This would mean that, in some ways, PublicKeyCallback could be used similarly to crypto/tls's VerifyPeerCertificate.
Such a person might further assume that, if NewServerConn returns success, the public key that the client used to successfully authenticate was the one passed to the last invocation of PublicKeyCallback, or at least the last invocation that returned success. So said person might try to retrieve that public key by supplying a closure as PublicKeyCallback and storing the public key in a local variable in the outer function, and reading from that variable after NewServerConn returns.
However, this doesn't work: unlike TLS clients, SSH clients can query for the acceptability of a public key by merely presenting it without signing anything, and those queries invoke PublicKeyCallback just like a proper auth attempt, and the serverAuthenticate method uses pubKeyCache to avoid calling PublicKeyCallback more than once for the same public key on a given connection. So a server making the faulty assumptions above could be tricked by a malicious client that queries for the acceptability of a public key for which it lacks the corresponding private key.
A correct server must not assume that the client can or will actually authenticate with the public key passed to PublicKeyCallback. Currently, the only correct way to determine the public key actually used to authenticate is to have PublicKeyCallback store it (or something derived from it) in the Permissions it returns, and then retrieve it from the Permissions on the ServerConn after NewServerConn returns. Those Permissions will correspond to the public key that did successfully authenticate.
None of this is a bug in (the code of) x/crypto/ssh. And a quick google doesn't find any code that uses PublicKeyCallback incorrectly like this, and does find several examples that correctly return the public key in the Permissions.
But I do feel the documentation could be improved. In particular, the documentation for PublicKeyCallback should make it clear that the client is not necessarily attempting to authenticate with the public key passed in. And the documentation for Permissions doesn't really suggest why one would ever need to use them, other than setting any CriticalOptions that x/crypto/ssh enforces. But in fact they must be used in order to correctly store information about the auth credentials used. Adding a bit more description and using Permissions in the ServerConn example would help here.
Beyond the documentation, it would be even easier to handle this correctly if ServerConn made information about the auth credentials (not just the username) directly accessible, but maybe that would be awkward given the several auth methods supported. Also, the PublicKeyCallback API could be changed to distinguish between acceptability queries and real auth attempts (and to call it again on a real auth attempt), but that would obviously be a larger change.

I don't understand. What kind of assumptions would your code make (what would your code do differently) for acceptability vs. auth attempts.

Sorry for the unclear description.
The wrong assumption would be that, as I said, "if NewServerConn returns success, the public key that the client used to successfully authenticate was the one passed to the last invocation of PublicKeyCallback, or at least the last invocation that returned success."
My colleague actually wrote and we nearly shipped a broken server that made this assumption, similar to this:
func runServer(conn net.Conn) error {
	var pubkey string

	config := ssh.ServerConfig{
		PublicKeyCallback: func(conn ssh.ConnMetadata, key ssh.PublicKey) (*ssh.Permissions, error) {
			pubkey = ssh.FingerprintSHA256(key)
		},
	}

	serverConn, chans, reqs, err := ssh.NewServerConn(conn, config)
	if err != nil {
		return err
	}
	// now make decisions based on pubkey
}

From the x/crypto/ssh documentation alone, it's not obvious why this is broken. But it is--this server could assume that the client authenticated with a public key that it merely proposed but didn't/can't actually authenticate with.
A correct server must instead return any information derived from the public key in Permissions.Extensions and retrieve it from ServerConn.Permissions.Extensions. But the documentation doesn't suggest why one would ever use Permissions.Extensions outside of the "common" extensions it mentions, namely "permit-agent-forwarding" and "permit-X11-forwarding", which are likely irrelevant to many/most users of x/crypto/ssh.
At least one other person has asked about this on golang-nuts; evidently it wasn't obvious to them either.
So I would suggest a few documentation changes, as I mentioned before:

Change the documentation for PublicKeyCallback to make it clear that the client is not necessarily attempting to authenticate with the public key passed in, and may not possess the corresponding private key. The current wording is misleading, especially to someone unfamiliar with the details of SSH auth. More widely-understood protocols like TLS that also have public-key auth don't have anything like acceptability queries.
Clarify that Permissions.Extensions can and should be used to store arbitrary information derived from the auth credentials and retrieve it from the ServerConn after auth finishes. And in fact this is the only correct way to store this kind of information: using side channels like captured/global variables from inside PublicKeyCallback is wrong because it will be confused by acceptability queries.
Make it clear that the names of Extensions are completely user-defined and don't have to be common or well-known, since x/crypto/ssh doesn't act on them, unlike CriticalOptions[1]. Consider not mentioning extensions that OpenSSH supports that aren't relevant to x/crypto/ssh (unless the user reimplements them in their own code, in which case they could use any extension name they want).
Make use of Permissions.Extensions in the example for ServerConn to store the public key and retrieve it (e.g. log it) after NewServerConn returns. This will illustrate the correct implementation of functionality that is security-critical for many users of x/crypto/ssh.

I can potentially submit a review for this, though it will take some time.
[1] x/crypto/ssh enforces at least one CriticalOption, but it doesn't fail when there are CriticalOptions that it doesn't recognize, which is confusing and potentially dangerous--what if a user mistypes "source-address"?

regarding typos: we could add a RecognizedCriticalOptions field in ServerConfig. The ugly part is that we already have this in CertChecker, but potentially we could break existing behavior.
(The real problem is that x/crypto/ssh doesn't implement a full-fledged canonical server, so there is both lack of good example code, and we may be missing some hooks.)

sent https://go-review.googlesource.com/45311

BTW, the verbiage around enforcing critical options is there because they can be part of a certificate, and it might be that the certificate signing software might not know there is a x/crypto/ssh library processing the certs, ie. the critical option is -in a way- provided by the untrusted user, and therefore must be treated with suspicion.

I see...the comment about CriticalOptions was a bit offhand and I didn't know about CertChecker.SupportedCriticalOptions. My focus has been much more on the auth callback ---> ServerConn path, with no user certificates, and as you see it's Extensions that are really relevant to me. So I won't offer further opinions about CriticalOptions. :-)
Thanks for your attention!