Save(<data/...>) returned error

Output of restic version
restic 0.9.5 compiled with go1.12.4 on linux/amd64

How did you run restic exactly?
% sudo restic --password-file /root/.password-restic-steffi -r /media/steffi/BACKUP01/restic-backup/himalia-home-steffi backup /home/steffi/Bilder /home/steffi/Dokumente /home/steffi/Schreibtisch
repository 5f46e1b5 opened successfully, password is correct
found 5 old cache directories in /root/.cache/restic, pass --cleanup-cache to remove them
Save(<data/749b65af15>) returned error, retrying after 367.839216ms: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/749b65af15>) returned error, retrying after 544.140027ms: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/749b65af15>) returned error, retrying after 1.090508832s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/749b65af15>) returned error, retrying after 2.480888057s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/749b65af15>) returned error, retrying after 3.099937081s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/749b65af15>) returned error, retrying after 4.416389563s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/749b65af15>) returned error, retrying after 5.284942272s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/8196008d0a>) returned error, retrying after 526.554676ms: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/749b65af15>) returned error, retrying after 10.767026883s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/8196008d0a>) returned error, retrying after 652.785148ms: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/8196008d0a>) returned error, retrying after 1.534896651s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/8196008d0a>) returned error, retrying after 1.630640764s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/8196008d0a>) returned error, retrying after 2.674096621s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/8196008d0a>) returned error, retrying after 3.602792445s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/8196008d0a>) returned error, retrying after 2.973312526s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/749b65af15>) returned error, retrying after 6.530304006s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/8196008d0a>) returned error, retrying after 10.639365553s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/749b65af15>) returned error, retrying after 27.816732895s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory
Save(<data/8196008d0a>) returned error, retrying after 7.254793648s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Save(<data/8196008d0a>) returned error, retrying after 26.89927355s: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/81/8196008d0a595692888972cc1a77b22844f9e0ef1605f8a6749ec5079734e686: not a directory
Fatal: unable to save snapshot: OpenFile: open /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/74/749b65af15473cc484d39c033a50fba5f8145993d5fd6002f708e8679d96e08e: not a directory

What backend/server/service did you use to store the repository?
External USB HDD with NTFS.
Expected behavior
Create a backup / snapshot by fixing the problem automatically or tell the user what to do.
Actual behavior
Fails to create a backup:
Fatal: unable to save snapshot

Do you have any idea what may have caused this?
steffi@himalia ~ % ls -l /media/steffi/BACKUP01/restic-backup/himalia-home-steffi/data/ | tail -n 30
drwx------ 1 steffi steffi  8192 Mai  6 12:43 e2
drwx------ 1 steffi steffi 24576 Mai  6 18:42 e3
drwx------ 1 steffi steffi 16384 Mai  6 14:42 e4
-rw------- 1 steffi steffi     0 Aug 16  2018 e5
drwx------ 1 steffi steffi 12288 Mai  6 17:42 e6
drwx------ 1 steffi steffi 16384 Mai  6 12:43 e7
drwx------ 1 steffi steffi 16384 Mai  6 12:43 e8
drwx------ 1 steffi steffi 12288 Mai  6 18:43 e9
drwx------ 1 steffi steffi 16384 Mai  6 17:42 ea
drwx------ 1 steffi steffi 16384 Mai  6 21:47 eb
drwx------ 1 steffi steffi 16384 Mai  6 18:42 ec
drwx------ 1 steffi steffi 24576 Mai  6 21:46 ed
drwx------ 1 steffi steffi 24576 Mai  6 21:45 ee
drwx------ 1 steffi steffi 12288 Mai  6 19:34 ef
drwx------ 1 steffi steffi 12288 Mai  6 16:42 f0
drwx------ 1 steffi steffi 16384 Mai  6 19:42 f1
drwx------ 1 steffi steffi 12288 Mai  6 16:42 f2
drwx------ 1 steffi steffi 16384 Mai  6 21:45 f3
drwx------ 1 steffi steffi 16384 Mai  6 20:44 f4
drwx------ 1 steffi steffi 28672 Mai  6 21:46 f5
-rw------- 1 steffi steffi     0 Aug 16  2018 f6
drwx------ 1 steffi steffi 16384 Mai  6 18:42 f7
drwx------ 1 steffi steffi 12288 Mai  6 21:44 f8
drwx------ 1 steffi steffi 12288 Mai  6 21:45 f9
drwx------ 1 steffi steffi 24576 Mai  6 17:42 fa
drwx------ 1 steffi steffi 16384 Mai  6 19:34 fb
drwx------ 1 steffi steffi 16384 Mai  6 19:34 fc
drwx------ 1 steffi steffi 16384 Mai  6 20:45 fd
drwx------ 1 steffi steffi 16384 Mai  6 21:45 fe
drwx------ 1 steffi steffi 16384 Mai  6 13:42 ff

The external HDD was once unplugged without unmounting. This forced me to do a filesystem check which rendered the restic repository unusable. As far as I can remember, I created a new repository but my memory could trick me. Anyway, the failing backup seems to be caused by the empty files and I do not know where they came from.
restic is actually called automatically via cron and the backup silently failed for quite some time now. As this is a "simple" workstation I do not have any monitoring and mail system configured, so I think I need some time to gain back some trust in the backup system. So the main points are:

What could possibly cause this empty files?
How can we avoid that?
Backup runs should not fail.

(Please be aware that I just updated restic today. The previous backups were taken with older versions of restic.)
Do you have an idea how to solve the issue?
My workaround was to delete the empty files (zsh(!)):
  steffi@himalia ..restic-backup/himalia-home-steffi/data % ls -l *(.)
  -rw------- 1 steffi steffi 0 Aug 17  2018 21
  -rw------- 1 steffi steffi 0 Aug 16  2018 74
  -rw------- 1 steffi steffi 0 Aug 16  2018 81
  -rw------- 1 steffi steffi 0 Aug 16  2018 82
  -rw------- 1 steffi steffi 0 Aug 16  2018 b1
  -rw------- 1 steffi steffi 0 Aug 17  2018 c1
  -rw------- 1 steffi steffi 0 Aug 16  2018 e5
  -rw------- 1 steffi steffi 0 Aug 16  2018 f6
  steffi@himalia ..restic-backup/himalia-home-steffi/data % rm *(.)

Did restic help you or made you happy in any way?
I love restic and I want it to work as reliable as possible (that is why I filed this bug even my spare time is running short and although I found a workaround).

What could possibly cause this empty files?

restic creates these directories once and then only adds packs to them but for sure it won't replace those with empty files.
The conversion from directories to empty files (I'd be surprised if the directories were empty before) was probably caused by a filesystem error triggered by the unexpected unplugging. This tells me that the NTFS implementation used on your Linux system is not crash safe at all: Basically all somewhat modern filesystems (including NTFS) have a filesystem journal to avoid metadata corruption after a system crash or when a disk disappears. The empty files, however, show that this obviously did not work at all. This error might also show up again the next time the system crashes or when the disk disappears.
I highly doubt that the backup repository is still intact: It has lost 8/256 = 3% of its data which means that several or basically all snapshots are likely to miss data (unless you've only backed-up a few hundred MB of data). You want to run restic check --read-data to check the integrity of the whole backup.
There's not much restic can do in this case: When the backup repository just looses a substantial fraction of its data, then restic will have problems. I'd count the "empty files instead of directories" as an obscure enough problem that someone should have a closer look at it instead of letting restic try to fix this automatically. (Just silently removing the empty files is a bad idea, as their existence indicates that the repository is broken which would require repairs before the backup can continue. That way restic would degrade from "fail with an error" to "fail silently" which would be even worse. And restic is currently nowhere near being able to automatically repair arbitrary repository damages.)

Closing this as there's not much we can do when the underlying filesystem looses files. The only option of adding redundancy to the repository is already tracked in #256 and #804.


Brightness settings only work on primary display

Hello. I have two external monitors connected.  One via Thunderbolt 2, and one via HDMI.  (2015-era MacBook Pro running latest Mojave).
When I use the dimming, fade to black option, it only works on the main display.
LOVE the work.  Great job!

Correct. Only the physical laptop screen dims.  :-)

Ok thanks, just to confirm too, if you use the brightness keys on your Macbook, do all of the screens dim ?
Here with DVI over DP, external screens don't change brightness either for example. I'm not sure every monitor can have it's brightness control over every interface, will look more into it.

Ah.. this makes sense.  Using the brightness button on my laptop does only change the actual laptop display.  So, if you're using that methodology, I'd understand why that doesn't work.

Yeah we use macOS' system brightness controls, so if they don't work with your monitors, Aerial won't be able to do more.
As far as I know, you could control external Apple monitors too, but probably not other brands through those system settings. It may depend on the interface used too (maybe the LG 5K monitor supports this ?)

@jakecovert , I have added a description of how the brightness dimming works in the readme. I'll keep in mind if I can do something else about this at some point, but macOS doesn't seem to help a lot on this. Thanks !


Make defining recursive twice error

Why do you want to disallow this?

The existing panic in the recursive define method implies it is meant to be an error to define it twice. Doing so overwrites the first usage and is, in most situations, I imagine an undesired behavior (And, if OnceCell is stabilized in the future, possibly becomes impossible at that point anyways). If there's a use case, the panic message could instead be changed, and the implementation could simply use a RefCell instead of a OnceCell.

Thanks!


Sourcemaps cannot be read from external .map files

I noticed that ng-annotate is hard-coded to read inlined source mappings, would it be possible to add a configuration for reading sourcemaps from an external source/file (e.g. a .map file)?

+@smrq

Or pass in a sourcemap object for that matter...

https://github.com/olov/ng-annotate/issues/245


How to protect all routes

Stack:
Front End - Angular 12
|-- Leveraging Angular/MSAL to integrate with Azure AD for authentication
Back End
|-- Node JS  V14.17.6
|-- Express 4.17.1
|-- Passport-Azure-AD V4.3.0 (passport-azure-ad is a collection of Passport Strategies to help you integrate with Azure Active
|-- Authentication Strategy - BearerStrategy (Protects APIs and Resources)
Directory)
|-- Passport V0.3.2 (Passport version leveraged by Passport-Azure-AD)
Back End Project Structure (Excerpt shown for brevity)
Root Directory
|-- src
|-- routers(Sub directory that holds all modularized routes per entity in individual .js files e.g. users.js, actions.js)
|--index.js(Application entry point)
I'm looking for a way to protect all my routes/api endpoints, rather than having to apply the passport.authenticate to each route handler within each of the route endpoints which could be "N" number of routes per modularized route .js files as expressed above. I have tried the following below to no avail.

Within the index.js file, i.e. the applications entry point, in which I use e.g. const users = require('./routers/users') and app.use('/api/v1/users', users) to mount my route handlers, I introduced the following app.use(passport.authenticate('oauth-bearer', { session: false })) since passport is a middleware but no joy

Within the modularized route handling files, I tried the following as well: router.all('',passport.authenticate('oauth-bearer', { session: false })) based on the express documentation, router.all should apply a middleware or provided function/handler at a path for all request methods and in this case the '' should match all paths, but still this only worked for the base path '/' and not others in the file e.g. '/relationships'

If anyone can prescribe a way to protect all routes, it will be greatly appreciated.

Option number 1 is exactly what should do it. If it is not, I really don't have any other suggestions, as that is the answers. Perhaps there is something else going on in the app that is not evident from the description, though. The only way to get a specific answer is to provide the code and instructions for how to run it and make the given reqeusts and how you expect them to act.

Hi @nubianMONK thanks for sharing your solution!


No way to pass environment information to compiler flags defined in Cargo configuration

The  .cargo/config file, through its build.rustflags key, allows you to add arbitrary compiler flags, which are appended to those passed by Cargo at build-time. These flags, however, are not parsed or evaluated in any way, which means that no environment information can be used in these flags.
Steps

Create a new Cargo binary project:

cargo new --bin test-case

Insert into .cargo/config:

[build]
rustflags = ["-C", "link-arg=-Wl,--defsym=FOO=${BAR}"]

Export BAR:

export BAR=0

Build the binary:

cargo build

Note the output of the error, which shows that the ${BAR} variable was not expanded:

  = note: /usr/bin/ld:--defsym:1: ignoring invalid character `{' in expression
          /usr/bin/ld:--defsym:1: syntax error
          collect2: error: ld returned 1 exit status

Possible Solution(s)
There are two obvious solutions to this:

Expand rustflags before passing them to the compiler.
Allow build.rs to override arbitrary compiler flags.

Notes
Output of cargo version: cargo 1.39.0-nightly (fe0e5a48b 2019-09-04)
The original issue that prompted this is that there is no way to pass the Cargo output directory as a part of the -Map linker flag, which means that the map file is always generated in the source directory (highly undesirable).

It would be amazing if either this or https://github.com/rust-lang/cargo/issues/5376 happened. For our project we have to pass a dynamic sysroot through RUSTFLAGS ('-C link-arg=--sysroot=$SYSROOT') which means we have to pass the entire RUSTFLAGS through our build system rather than just the one argument (or having it set an env var to be expanded by Cargo).

Side note: #12193 requests other ways of modifying RUSTFLAGS


Rally should be able to check the correct version for tracks

Sometimes the track format needs to change. So in addition to being able to find the correct track version for an Elasticsearch version, we need to find a possibility to avoid that older versions of Rally fail, when the track format changes. Basically, we could add a meta-info file at the repository root with a lookup table that maps a Rally version (or track format version) to the last good commit hash for that version. To avoid that this turns into a maintenance night mare we should also script this process.

No priority at the moment, hence closing.


CLI query commands alignment

Purpose of Changes and their Description
Link(s) to Ticket(s) or Issue(s) resolved by this PR
https://linear.app/alloralabs/issue/PROTO-2967/cli-query-commands-alignment
Are these changes tested and documented?

[ ] If tested, please describe how. If not, why tests are not needed.
[ ] If documented, please describe where. If not, describe why docs are not needed.
[ ] Added to Unreleased section of CHANGELOG.md?

Still Left Todo
Fill this out if this is a Draft PR so others can help.

May need to update the CHANGELOG.md :)

Done!


Shared BreadCrumb

Issue #: /bcgov/entity#10232
Description of changes:

Implements Shared BreadCrumb

Added BreadCrumb interface

BreadCrumb Stories

Currently thinking of what/if unit test is applicable here..
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the business-filings-ui license (Apache 2.0).

Issue #: /bcgov/entity#10232
Description of changes:

Implements Shared BreadCrumb
Added BreadCrumb interface
BreadCrumb Stories

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the business-filings-ui license (Apache 2.0).

Could you please attach some screen shots of the different variations? (So we don't have to build locally to test ;) )

Could you please attach some screen shots of the different variations? (So we don't have to build locally to test ;) )

Totally, can do! I wish i could share it in Storybook as a preview some how...

Could you please attach some screen shots of the different variations? (So we don't have to build locally to test ;) )

See pics below!

Could you please attach some screen shots of the different variations? (So we don't have to build locally to test ;) )

See pics below!

Looks amazing!


does this support printerStatus ( out of paper, over heated, cover of the printer is not closed status etc)?  if not how can we add this functionality in this existing library?

does this support printerStatus ( out of paper, over heated, cover of the printer is not closed status etc)? if not how can we add this functionality in this existing library?
@Surile
your help would be much much appreciated.

@Rehankhalil462 It is not currently supported. You can fork this project and add the corresponding code to the sunmi printer module

@Surile Thanks for your swift reply . Ok I will try to add this functionality in this library.


Feat/new themes

Added 3 new themes - ubuntu, arch, matrix
added validation and execution function for theme related functionality.
Run theme to get list all commands associated to theme.
Run theme list to get list all available themes.
Run theme set <theme_name> to set theme to <theme_name>

Nice work. I really like the implementation.
Can you take care of the following-

We are migrating all features of Homepage to Profile page as Homepage will be rebuilt. Please migrate this feature to the Profile page.
Ideally, the full command should be stored in history. It's just storing the first word.

I'm super excited for this feature.

Changes are on their way

Fix: : Migrated theme functionality to Profile.tsx and fixed incomplete command history entries.

Migrated theme change functionality from Home.tsx to Profile.tsx
history command shows complete theme command as passed by user

@thtauhid all changes have been made as per requested earlier. Can you quickly look into it and merge it?

@Vilayat-Ali checking this now.

@Vilayat-Ali nice work.


Bump sentry SDK to 8.9.3

Rebase bcny-patches on top of upstream tag 8.9.3.

Should we also add to the changelog suggested here?

Not sure, it will cause conflicts on every rebase, since it is the same file used by sentry. The ultimate goal is to get rid of this fork and upstream the widevine change, instead of having more changes, so I think adding to the changelog locally is not necessary.

For simplicity, i did this using the Github UI (Sync Fork on the bcny-patches branch), so I will discard this PR.


Removed outdated anticheats

I've removed all anticheats that are not updated anymore.

Can I add the latest update date of each anticheat in this PR or do you want me to make another one ?

Feel free to update those here

Is it good now ?


Fix #1635 - Add visual feedback on API address form

Saw that there was a help wanted tag on #1635, thought I could lend a hand!
Changes

Add error text to API address settings form (ApiAddressForm.js)
Populate error message for invalid addresses and connection errors (ApiAddressForm.js)
Add outline to ApiAddressForm to indicate address validity (ApiAddressForm.js)
Add apiAddress to "could not connect" message ("Could not connect to the IPFS API (/ip4/.../tcp/5001)") (ipfs-provider.js)
Add "pending first API connection" handlers to ipfs-provider (ipfs-provider.js)
Add full page loader when pending first connection (SettingsPage.js)

Demo
Tried to submit an invalid IPFS API address

Tried unsuccessfully to connect to an IPFS API

(Video) Filling out an API address
Video (filling-out-address.webm)
TODO

[ ] Polish off successful state (right now it just shows no error message, but that's not nice enough)
[ ] Remove new ApiAddressForm.css file in favor of tachyon utility classes (I don't do anything special in the CSS)

Thanks, @jack-michaud! Assigning some folks to have a look. Please note this week is a little hectic but we'll act as speedily as we can!

Thanks for the prompt triage @jessicaschilling !
Totally get that it's hectic, so no rush. I'll be chipping away at the remaining TODOs to polish it off in the meantime.

Hi @jack-michaud -- sounds like a plan. Drop a comment when you're ready for a final review. 😊
I didn't dig into the code, but the video and screenshots look excellent! The only nit is that we're using snackbars for error messages (example pasted below), so for consistency's sake, probably best to present the error messages that way. (For emphasis, leaving the red border around the entry box until it's cleared by something else - like entering another address - will be helpful.)

(FWIW, that error was invoked by entering /ip4/<IP_ADDRESS>/tcp/4001/p2p/QmbBHw1Xx9pUpAbrVZUKTPL5Rsph5Q9GQhRvcWVBPFgGtC in the "Add Connection" modal on the Peers screen.)

Thanks for the feedback and review @jessicaschilling and @rafaelramalho19 --
I updated the PR to use the snackbar for errors:
Fail

Success

I also used the internationalization keys in to eventually give this a custom translation... the notify.json locale file has new keys ipfsConnectSuccess and ipfsConnectFail. Are there other steps to get this into Transifex?

That's it for Transifex!
For the fail state, could you please give the input box a red highlight border?

For the fail state, could you please give the input box a red highlight border?

@jessicaschilling Absolutely!
Video demo
I pulled another feature from the peer "add connection" dialog behavior. For invalid multiaddrs, the submit button is disabled.
Also, like you suggested, when you submit a value and it fails to connect, the input box will remain red until new values are typed
Thank you for bearing with me in these iterations.

@jack-michaud This is awesome - thank you!
@lidel and @rafaelramalho19, do you mind a review when you're able?

Thanks, @jack-michaud — merged!
We very much appreciate your work! If you have the inclination, please feel free to pick up any other issues labeled help wanted in this repo ... or for a higher-level view across all 13 GUI-related repos, check the Quick Fixes column of this ZenHub board.


🐛 : Cross-Domain Authentication Issue with Third-Party Cookies Blocked

Describe the bug
Unable to login using any authentication method when third-party cookies are blocked. This issue occurs as our database and application are hosted on different domains.
To Reproduce
Steps to reproduce the behavior:

Go to the login page.
Attempt to login using any authentication method.
Error occurs when third-party cookies are blocked.

Expected behavior
User should be able to login using any authentication method even when third-party cookies are blocked.
Screenshots
https://github.com/langxapp/langx/assets/3280475/fe253107-0785-4f38-8c2c-f37d485a0fda
Desktop (please complete the following information):

OS: macOS
Browser: Chrome
Version: 121.0.6167.184 (Official Build) (arm64)

Additional context
The issue was resolved when third-party cookies were allowed. This setting was manually turned on by the user and is not a default browser setting. The issue seems to be related to cross-domain requests between our application and database.
Contributor: @xbloodyknight from Discord
If you want speed up process of this issue, please send 🚀 as a reaction.

Closed with https://github.com/langxapp/langx/releases/tag/v0.9


Error when deploying chaincode: Path to chaincode does not exist

When I deploy chaincode with command
c.chaincode_deploy("$GOPATH/src/github.com/czk_chaincode")
this error happened. My chaincode is indeed in this path.
Could you please tell me why ?
Thanks !

I have solved it !


Can't add new location

Describe the bug
I can't add a new location when creating a new spool or editing an old spool.
To Reproduce
I go to spools, click create, press the location field, then I get a "No data" box showing, but the field is not active/I can't write anything in it.
Expected behavior
I expected to be able to write the name of the location.
Desktop (please complete the following information):

OS: Ubuntu 22.04LTS
Browser: Firefox
Version: 121

Additional context
This is a new install with the latest docker image.

Just below where it says No Data you should have a text input where you can type in a new location. I just tried it in firefox and it works fine for me.

Do you see this field?

Yes, I missed that one. Sorry about that. It was easier to see once another location had been added.


error in typescript

I've tried to install and got this issue.

What version of TypeScript are you using?

Closing this due to inactivity.
My guess is you have TypeScript version older than 3.8 installed, which doesn't support import type syntax.
Update it.  Currently the latest version is 4.6.4, which has many improvements over old versions.


Use Jug instead Jar for the sample

Because Jar is confusing in a way that people may think that it refers to "Java Archive" instead of the bottle or jug thing in the sample ...

82848ab4eef1188befdcd61f54bec731f5da5210


Allow disabling automatic patches

There are some use cases that state sync is not necessary at all.
Currently, the following doesn't have the expected behavior:
this.setPatchRate(null);
this.setPatchRate(0);

By passing such values on setPatchRate, the automatic patch broadcasts should be disabled.

@endel I am looking into this issue as my first pull request, and am wondering if the following test is sufficient for the expected behavior that you are looking to reconcile in this issue?
`it('should disable "patch" interval', function () {
var room = new DummyRoom();
room.setPatchRate(null);
  assert.equal("object", typeof ((<any>room)._patchInterval));
  assert.equal(-1, (<any>room)._patchInterval._idleTimeout, "patch rate should be disabled, set to -1");
});`

Where -1 is the resultant value after using clearTimeout() to disable the patch timer. I believe I have a fix, and it does pass this test, but I'm not sure if I am missing something.

I have also tested this using the colyseus-examples repository, which resulted in successfully disabling the patch timer. All other tests continue to pass.

what about
use patchRate property instead of setPatchRate() method.¶
OLD
constructor (options) {
this.setPatchRate(1000 / 50);
}
NEW
class MyRoom extends Room {
patchRate = 1000 / 50;
}


End Client is able to get information about 5 most recent voting result

[!NOTE]
This is a sub-issue of #81

AS A Service manager
I WANT TO to provide that the End Client is able to get information about 5 most recent voting result
SO THAT I can provide that the End Client is able to get information about 5 most recent voting result
Acceptance Criteria

[ ] End Client is able to get information about 5 most recent voting result. Result contain information about what was on voting and the result. /api/votings/last

https://github.com/buerokratt/Common-Services/pull/144

Works as intended


Multiple views need to be updated post-route

A page of widgets. The URI changes. Each widget need to know.
//cc @megawac
p.s. self, also think of those widgets I made at OneTwoSee.

This solution will be more closely considered in a different routing lib.

Didn't have any luck with this one?

I didn't spend much time looking into it, tbh. I'm working on a far better routing library than what you can build on top of the BaseRouter, though.


⚠ Bofrost.be has degraded performance

In 53dbba8, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1126 ms

Resolved: Bofrost.be performance has improved in 64bddfa.


[BugFix] Fix the bug that causes incorrect pindex data when the key length is very long

Why I'm doing:
Pindex maybe return error result if the key is very long. We will calculate a hash value for each key, and use this hash value to determine which shard, page, and bucket the key will be distributed to.  And we will record the bucket info (include pageid, packid and size) in the BucketHeader. However, the pageid in BucketHeader is store as uint16_t and the max page num should be not greater than 65536. But now it's possible that the number of pages exceeds 65536. A typical example is following:

Assuming each key has a length of 3000 characters.
The page size is 4096 right now and each page can only keep one key right now.
We determine shard num by the total bytes of all the keys and we will try to generate a immutable pindex.
Since we use hashing to determine which page a key should be placed in, it's possible that different keys will be placed in the same page. If that, we will increase the page num and retry until each page only has on key at most. At this time, the page num maybe increase very fast and exceeds 65536.

What I'm doing:
IMO, A 4k-sized page isn't suitable for storing very long keys, as this leaves little tolerance for hash collisions, resulting in many empty pages and causing performance degradation and storage space waste and When the key length is not very long, the likelihood of exceeding the limit of the number of pages is very small.  So, I supported larger pages to ensure that each page can store at least kRecordPerBucket (default value is 8) records to tolerate hash collisions. When the number of pages exceeds the limit, an error will be returned.
Fixes #issue
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

Should we support such long key length? It think it will be bad for performance even if we support it.

If you want to backport this pr to 3.1, remember to set PERSISTENT_INDEX_VERSION_5 when lake persistent index load from tablet.

@mergify backport branch-3.1


Sort statements by package name, ignore ‘import’ vs ‘from … import’

A sensible ordering for import statements is alphanumerically by the package name. This should ignore whether the statement is ‘import’ or ‘from … import’.
Currently, ISort insists on separating ‘import’ versus ‘from … import’, resulting in statements that jumble the sequence of package names:
import apidiscing
import euismod
from dolor import consecteur
from ex import metus

Instead, ISort should order these statements by the package name:
import apidiscing
from dolor import consecteur
import euismod
from ex import metus

There does not seem to be any combination of ISort settings that will obey this sequence.

I think the default behavior is correct and usually the preferred one.
@timothycrosley do you think it's a possible candidate for enhancement to enable sorting only by the package name? Possibly via some cmd line flag?

Can you accomplish this force_sort_within_sections? If that does not work maybe you would also need force_alphabetical_sort. (isort settings wiki page)
$ isort --help
  ...
  -fas, --force-alphabetical-sort
                        Force all imports to be sorted as a single section
  -fass, --force-alphabetical-sort-within-sections
                        Force all imports to be sorted alphabetically within a
                        section
  ...
  -fss, --force-sort-within-sections
                        Force imports to be sorted by module, independent of
                        import_type
  ...

@timothycrosley timothycrosley added the enhancement label 14 hours ago
@timothycrosley timothycrosley closed this 14 hours ago
@timothycrosley timothycrosley added the question label 14 hours ago

Adding the “enhancement” label makes sense, this is a request for enhancement.
What are we to understand from closing this request, without an implementation of the enhancement?

Hi @bignose-debian,
I've been trying to go through and categorize issues, and closing any that I thought where complete. When I saw your message above that --force-sort-within-sections retained the desired ordering I read that as the desired feature was already implemented with that flag and thus it was an enhancement request that turned into a question that had since been answered. Is my understanding of the issue incorrect?
Thanks!
~Timothy

When I saw your message above that --force-sort-within-sections retained the desired ordering I read that as the desired feature was already implemented with that flag […]

You're quite right, this request is already met by that option. This issue can be closed (and IMO the “question” label removed), sorry for the noise.

Hi @bignose-debian,
No worries! Thank you for the confirmation!
The question label is only there so I can filter through any areas of confusion and make a comprehensive FAQ document in the future.
Thanks!
~Timothy


added shadows to cards [RFR]

Added drop shadows as per https://www.pivotaltracker.com/story/show/97115062

@lifehackett made the changes to dry it up.  Didn't do the mixin because I would have needed to add the elements.less file, call it, etc. which seemed a bit of overkill since we were only using one element which can be covered in one line of code.  I can add it though if you want.  There are conflicts so I will do the merge and deal with them once you've given me the ok.


Make provisioningUtility configurable in Terraform configs for AWS

What this PR does / why we need it:
While testing cluster provisioning on AWS, I discovered that some legacy Flatcar tests are failing because of the user-data limits. In the past, we fixed that by using cloud-init provisioner and removing SSH keys from MachineDeployments. We reverted that when switching to OSM because that's no longer needed.
I added a new test definition called aws_flatcar_cloud_init which uses cloud-init instead of Ignition and disables deploying SSH key to the worker nodes. With this test definition, affected Flatcar tests are passing.
What type of PR is this?
/kind cleanup
Does this PR introduce a user-facing change? Then add your Release Note here:
NONE

Documentation:
NONE

/lgtm
/approve


EDDI crashing immediately

Faulting application name: EDDI.exe, version: <IP_ADDRESS>, time stamp: 0x5c6642b2
Faulting module name: KERNELBASE.dll, version: 10.0.17134.556, time stamp: 0xadca2670
Exception code: 0xe0434352
Fault offset: 0x001118a2
Faulting process id: 0x6c8
Faulting application start time: 0x01d4d2ed3f96c074
Faulting application path: C:\Program Files (x86)\VoiceAttack\Apps\EDDI\EDDI.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 3106a4ee-ac07-46de-82fc-b85a1f0c5a97
Faulting package full name:
Faulting package-relative application ID:

I tried deleting the credentials file as suggested in a similar thread.  There was no credentials file.  I restarted the computer.  I uninstalled and reinstalled the program.

it's better to follow the EDCD/EDDI page, the last release is 3.3.6:


Error "'dict_values' object does not support indexing" while compiling .proto files

It seems like some python2 syntax is in nanopb_generator.py:
https://github.com/nanopb/nanopb/blob/9f57cc871d8a025039019c2d2fde217591f4e30d/generator/nanopb_generator.py#L990
This will lead to the error in the title.

Yeah, looks like this code path is uncovered by current test cases.

It seems that there is an even bigger issue around this line. Then "fixing" this python2 syntax line via list(dynamic_sizes.values())[0] non compilable code will be generated.

Do you have a .proto file that triggers this?

I can reproduce this with the following set of proto files:
syntax = "proto3";

import "LogMessage.proto";

message DataPacket {
    oneof packet {
        LogMessage log_message = 1;
    }
}

syntax = "proto3";

message LogMessage {
    string msg = 1;
}

The error only occurs if the messages are defined in different files.

Hmm yeah, and it even occurs when both files are passed to the generator together. I'll try to find time to take a closer look at this.

@Psy-Kai Do you have a .proto file that reproduces the problem with "Then "fixing" this python2 syntax line via list(dynamic_sizes.values())[0] non compilable code will be generated."? For the file posted by @lopsided98 that fix appears to work correctly.

Sorry of the very late answer. I will attach some files which represents the bug (which still exists if you have a deeper structure)
nanopb_generator_bug.zip

@Psy-Kai Thanks, I was able to reproduce that bug now. Looks like it has a problem with finding the dependencies of the dependencies.

@PetteriAimonen I just tested generating files with generator from master and it works for my proto definitions now. Thanks :)
This also fixed an size-macro ordering issue I got now ^^

Glad to hear that :)

Fix released in 0.4.5.


One more try at merge queues CI.

Failed merge run is at https://github.com/shakenfist/shakenfist/actions/runs/11956521005


loggerd: c++ test cases

What's the benefit over the python test?

it can do functional testing

I'd like this to supplement the python tests. Let's keep the existing python test cases.

closed. move to c++ logger #21877


Fix image tag

Accidentely didn't take enough charachters :\

Merging without waiting for approval because the change is trivial and I'm blocked


TextField Keyboard AutoCorrection

I cannot figure out how to disable AutoCorrection for TextField.
Is this a hidden property.
I considered accessing the underlying UITextField but could not figure that out either.
Any idea?

Not currently. Feel free to implement and PR. :-)


Rename SpaceTuxLibrary-<IP_ADDRESS>.1.ckan to SpaceTuxLibrary-<IP_ADDRESS>.ckan

LGG made us aware of this typoed version number, and asked us to freeze it.
It should have been <IP_ADDRESS>, but was <IP_ADDRESS>.1.
I think that just renaming it works just as well to get it into the right sorting order again, without loosing this version completely.
The version on SpaceDock still has the additional zero, but it's not a big deal since the download link stays the same.
It might confuse some user seeing this version on CKAN and trying to find it on SpaceDock (or the other way around), but it would be the first user to take a close look at version numbers.
And it's also not even the most release for this version of KSP (1.8.0), so it's unlikely that anyone would ever try to install it in the future.

#2017 :1st_place_medal:

Ah come on! :laughing:

I even created a "Fix versioning" label! (Always wanted to have one!)


Cells with Multilines don't merge

I think the underlying problem is
julia> Multiline(["A"]) == Multiline(["A"])
false

Fixed by #29


[Bottom Bar] Some devices don't show the labels below the icons

Hey @teolemon I would like to work on this issue:)

Hey @teolemon I would like to work on this issue:)

@teolemon Can you please tell which emulator are you using?

@teolemon Can you please tell which emulator are you using?

obsolete


chore(package): update eslint to version 3.8.0

https://greenkeeper.io/

Coverage remained the same at 89.0% when pulling 88b68096945f6c46a55fec2dc6e3b56b66cc1bf0 on greenkeeper-eslint-3.8.0 into 3e94717f6a4d5990aba33429ac19ef344bc7f1cd on master.


Import statement for latest react native version

Could you please combine your two PRs in one and update RN peer dependency to 0.40?
In this case the other 2 similar PRs will be redundant.

Will update in single PR


You Can Use Leads In Spec

Describe the bug
If I'm holding an animal on a lead and go into spectator mode the animal is somehow still attached. I can fly around with the animal still attached to the lead.
To Reproduce
Steps to reproduce the behavior:

Leash an animal
Go into chat and run /s
Fly around. As long as you aren't too fast the animal will stay connected

Minecraft version
1.16.4-1.16.5
Console error
No error
Expected behavior
Lead comes unattatched

This is a vanilla behavior but a config value has been added to prevent this (enabled by default). I had no idea about this so thanks for the report.


Kramdown align.center problem

When using  jekyll-theme-primer on markdown-based github pages with kramdown enabled, sizing an as the first image on a page works using a kramdown tag:
![logo](./images/logo.png){: height="50%" width="50%" }

However, adding the .align-center tag does not center (but the sizing still works).
![logo](./images/logo.png){: .align-center height="50%" width="50%" }

There does seem to be support for .align-center in the jekyll-theme-primer CSS, but there must be something subtle going on where it isn't happening.
Ideas?

Still an issue.


refactor: Use a more engineering-oriented error code wrapper

I change the files in ./app/search_engine. Use "github.com/pkg/errors" to wrap error. In a word, If a function doesn't need to return an error, print the error and stack information with logrus, otherwise wrap the error and append some information.

can you fix the golangci-lint error first ? It maybe caused by the sort of import pkg.

can you fix the golangci-lint error first ? It maybe caused by the sort of import pkg.

I sort the import pkg , but it seems doesn't work


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1517 ms

Resolved: Bofrost.de performance has improved in 6d18f57 after 8 minutes.


Feature/tracking

addressing issue #2. Implemented logging to es

@dicko2 I updated PR with  #1  issue addressed


Feature Request: Stop deleting 'dist' directory on 'ng serve' (SILENTLY)

Bug Report or Feature Request (mark with an x)
- [X] feature request

Versions.
@angular/cli: 1.0.0-rc.1
node: 6.10.2
os: win32 x64
@angular/common: 2.4.9
@angular/compiler: 2.4.9
@angular/core: 2.4.9
@angular/forms: 2.4.9
@angular/http: 2.4.9
@angular/platform-browser: 2.4.9
@angular/platform-browser-dynamic: 2.4.9
@angular/router: 3.4.9
@angular/cli: 1.0.0-rc.1
@angular/compiler-cli: 2.4.9
Repro steps.
run "ng build" then "ng serve"
Desired functionality.
'ng serve' silently deletes the hard-coded 'dist' directory and should not.
Mention any other details that might be useful.
'ng serve' currently deletes the dist directory contents despite having nothing to do with the 'dist' directory.   AND IT DOES THIS SILENTLY.  The user might build into a different directory and store important information in the dist directory, which they would lose when calling 'ng serve'.  People might use the dist directory for a lot of things.  They might WANT to check in their weekly builds, either into the same repository or as a submodule so it can be imported into another project to serve the files.  They might have a standard at their company to store things in a dist directory and build into a different directory, then 'ng serve' would delete files it has zero rights to delete.
If this is just done because people mistakenly think that 'ng seve' is serving the contents of the 'dist' directory it is a user education item and should be handled by a message when running 'ng serve' explaining this, not by silently deleting files.
A command line parameter like ng serve --keep-dist would be ok.  At the very least there should be a message when running ng serve telling the user that it is deleting the contents of a directory.

For our workflow we serve the angular-cli app inside an ASP.NET Core web application.  The 'dist' directory is a submodule of our angular-cli project and also of the ASP.NET Core web application (in the wwwroot directory).  So when we have a new version of the angular code, we do a build, then commit the changes in the submodule (with a tagged version, etc).  Then in our ASP.NET Core application we simply update the submodule.
We initially did this because angular-cli wouldn't build in Azure when pulling our project from source control.  If that has changed we might go back to just including the angular project as a submodule directly, but still deploys would take an extra couple minutes to build the cli project.

I can tell that you put a lot of thought into writing this issue, but I'm sorry to have to tell you that it's still a dupe of https://github.com/angular/angular-cli/issues/4366, and what had to be said about this subject has been said there (you even commented there yourself).
If you're keeping important things in your dist/ dir, then you have to change outDir in your .angular-cli.json so that the CLI uses another folder for build artifacts it on build/serve commands. Starting in 1.1.0-rc.0 you also have the --delete-output-path flag, defaulting to true.

Ok, you laid down the law.  Despite it not being the best option for some people you still want to delete a directory and have no option to avoid this.
At the very least you should inform the user when they run 'ng serve' that it is deleting a directory.  I don't know how you can say it's a good practice to delete a directory without informing a user.  A directory they know was created and populated when they ran 'ng build', or maybe a directory they put non-build related files in themselves when they changed the build output to go to another directory.  I don't know how any user wouldn't be surprised when those contents were suddenly gone unless they are reading these issues.

The command line option ( --delete-output-path, which you can set to false) currently exists though, and I don't think a message every time ng build/serve/e2e run is very useful - it just becomes white noise after one or two times.
I do agree that it might be unexpected in some setups (like the one you described), but I think that in a lot of setups it's not surprising at all that the output directory for the build system is wholly transient and that there are a lot of commands to wipe/rebuild it.
You're quite right that this is poorly documented. I'll add a note to the build command docs.

@filipesilva what version did this go in to?

Running "ng build --output-path='../'" , instead of creating a directory in the parent named "dist", just deleted 12 hours of my work.
A little warning, or maybe an error message would have been nice.
Instead, AFTER my entire project was deleted, I got a cheery little message saying "Path must be a string. Received null"


simplify Provenance representation

Provenance is reified into QScript to be used by bucketed operations, autojoin, etc.
The current representation is verbose and includes unnecessary components. We need a new representation that separates the parts that we need during QScript compilation (for correctly generating autojoins) and the parts that need to be reified for bucketing.

@sellout wondering if this ticket could be broken into multiple tickets.
This ticket was partially completed with the merging of #1592, which reifies only the provenance information that is needed past the compile phase.
So I'm thinking, perhaps it makes sense to close this ticket since #1592 is merged, and then add new tickets giving the details of the remaining provenance simplification work? Since only the reification work was initially described here, we could use descriptions of the remaining work.

@sellout after this release is out, could you describe the remaining work in this ticket? I'm not sure exactly what further work you have in mind to be completed.


[CI] Temporarily disable lightning kokkos builds

Due to: https://github.com/actions/runner-images/issues/8659

Thanks @dime10!
One alternative solution might be to disable clang with C_COMPILER=$(which gcc) and CXX_COMPILER==$(which g++) make variables until this is fixed in actions/runner-images#8659.

I don't mind either way, you're the one who proposed disabling kokkos tests 😅

Yeah, I'm just saying this is an alternative option. But I don't have any strong preference here :)

@dime10 Accepting my suggestion may resolve the Codecov failure :crossed_fingers:


For anoter ed?

Hi
Maybe theme can be 'ported' to Cudatext [uvviewsoft.com]?

Sorry, I'm only supporting Atom at this time.


labservices-track1

@nickdepinet I see there're a lot of operations get removed. Are you sure it's expected https://github.com/Azure/azure-sdk-for-js/pull/18156/files#diff-aba890a18c105b53ea64abbb122d701370468bc6fdf7759e3372c2d704a6a8e6L43-L51

Yes, this is expected - this is a large change release for us.
Can we change the release date from 11/8 to 11/22 to align with customer communications + blog posts?


change to utils

Test the admin change github action
changing utils

.go only, the check passes
the check fails once we change admins.go

@sampocs no action required, just fyi


Update images.mdx

Description (required)

add Picture to note about required alt attribute

https://docs.astro.build/en/guides/images/#properties-1

 accepts all the properties of the  component

I think this sentence is the reason why the  properties don’t explicitly mention they apply to  but I see that accepts doesn’t specify exactly requires


Fine-tune iOS's scroll start feel

Fixes #16529
This makes sure on iOS that:

Slow creeping scroll moves still don't gradually drift from finger
Hesitant drag starts don't jump by too many pixels initially
Determined drag starts has closer to the inertia feeling on iOS
Strong flings don't lose the responsive feel
Scroll position is still somewhat 'sticky' when becoming stationary

How does this code end up only affecting iOS?

Only the iOS's scroll behaviour physics sets a motionStartDistanceThreshold on the ScrollDragController. Otherwise, all drag motions transparently falls through to applyUserOffset.

One thing we might want to do is change our gesture recognizers to not do the jump, by having them start at zero offset when they "win". (Presumably we'd make that configurable, and the question here is just what the default configuration should be for those created by a GestureDetector.)
cc @HansMuller who was interested in that particular idea.

I think it's sensible to make it tiered (partially gated here and partially gated in the gesture detector) and also add something similar to the gesture detector.
We'd indeed want them to be configurable. Otherwise, winning at zero will make deliberate flings feel sluggish.
In the long run, I still want to model iOS scrolls specifically to #13171 (it's just really hard to reverse engineer it) but that wouldn't apply to general gesture detectors so we still need 2 paths I think.
But having it on gestures will solve a similar problem with things like back swipe which also 'jumps' in Flutter and doesn't natively.


Allow zoomControl position in default map options

When you init L.map, you can provide a zoomControl boolean as to whether the map should have the zoom control by default or not. This automatically places it in the top left. For our use case, we want it in the bottom left, but there's no clear way to do this in the default. Currently, we pass zoomControl: false to the default options, and then create a separate zoom control to be added after the initialize:
L.control.zoom({ //L.control extension for (+/-) on the map
    position: 'bottomleft'
  })

It would be great if you could pass in the position to the default options to get around this.

You can just do map.zoomControl.setPosition('bottomleft').


Update default TLS cipher to use ANY_TLS12_OR_HIGHER

The default Cipher for the developer image TLS enabled channels is ANY_TLS12. This restricts TLS communications to those channels to just TLS 1.2 ciphers and so does not allow people to connect clients with TLS 1.3. This is unnecessarily restrictive and so we should use ANY_TLS12_OR_HIGHER instead.

@arthurbarr any chance to review/merge?

This PR had gotten out of date, so changes made under this PR instead


dockview setTitle method

          Doesn't seem to be working anymore. Example:

const Component = (props?: IGridviewPanelProps) => {

    useEffect(() => {
        const interval = setInterval(() => {

            console.log('component_id', global.layout.getPanel(props.api.id).api.title); //works
            global.layout.getPanel(props.api.id).api.setTitle("ASDASDASD"); // not working, no error given

        }, 1000);

        return () => {
            clearInterval(interval);
        };
    }, []);

    return <ComponentChild/>;
};

On the other hand, this piece of code changes the title but I got a TS error:
global.layout.getPanel(props.api.id).setTitle("ASDASDASD");
TS2339: Property 'setTitle' does not exist on type 'IDockviewPanel'.
Originally posted by @amirmamaghani in https://github.com/mathuo/dockview/issues/5#issuecomment-1438800750

setTitle is a method that exists on the DockviewPanel object, however it is intended to be a private method now. The reason being is that all interactions should be via the panel.api to simplify the logic going forwards.
The intended behaviour is that the user calls panel.api.setTitle(...) however there seems to be a bug with this approach which I will fix.
For now though you can still set the title via an alternative approach which is a rather generic method exposed for advanced cases, but it does provide a way to update the title. Once fixed though it would be better to set this via panel.api.setTitle(...)
panel.update({ params: { title: 'my_title' } });

Fixed in release 1.6.0

Hi, first of all - thank you so much for your work!
It appears that in version 1.14.1 neither one of the suggested solutions work.
However, using a combination of both update and setTitle work, for example:
      const panel = containerApi.getPanel(panelIdToGet);

      panel?.update({ params: { title: titleToSet } });
      panel?.api.setTitle(titleToSet);

We're using React 18.2 with Vite 4.5.2 if that helps.
Thanks again! This library is a blast to use!

Fix released in 1.14.2.
See https://dockview.dev/docs/core/panels/add for an example of title updating.
Title should be updated via api.setTitle(...)


Added Linear Search and Binary Search Algorithm

What does this PR do?
This PR adds the Linear-Search and Binary-Search Algorithm
Related PRs and Issues
#498
Have you read the Contributing Guidelines?
YES

Hey @AnubhavPabby Ive raised this same issue before so you have to wait according to guidelines.


BUG: Multiple Repeated Prepare Statement Queries

This follows on from #2979, testing for query replication.  I am unable to repeat the issue with hierarchical traversal causing multiple repeated queries, however PREPARE statements are repeated.  It would make sense to cache these.
Steps to reproduce at time of writing:
Install SilverStripe as normal in a browser, downloading code as follows:
composer create-project --keep-vcs --dev silverstripe/installer www dev-master

Log database queries at the MySQL level. To do this enable the following 2 lines in /etc/mysql/my.cnf (if using Debian based distribution).  Restart MySQL after this configuration change.
general_log_file        = /var/log/mysql/mysql.log
general_log             = 1

Populate the tree manually, as SilverSmith does not work with SilverStripe 3.2  For the numbers below I went with a branch four deep that had four leaves (i.e. pages without children)
Delete the MySQL query log, restart MySQL, load a leaf page and parse the logs for duplicate queries:
sudo rm /var/log/mysql/mysql.log
sudo service mysql restart
curl -i http://ss32.silverstripe/tree-of-pages/level-1/level-2/level-3/level-4/level-5-4/
cat /var/log/mysql/mysql.log | ruby ../files/parse_mysql_log.rb  | sort | uniq -c | sort -h | less

The Ruby script to concatenate MySQL log statements into a single line is as follows
# Keep reading lines of input as long as they're coming.
def is_number? string
  true if Float(string) rescue false
end

current_line = ''

ARGF.each_line do |line|
  # Construct a string that begins with the length of this line
  # and ends with the content. The trailing newline is #chop'ped
  # off of the content so we can control where the newline occurs.
  # The string are joined with a tab character so that indentation
  # is preserved.
  line.strip!
  next if line.length == 0
  tLine = line.strip.split ' '
  start = tLine[0]
  splits = start.split ' '
  possibleNumber = splits[0]
  if is_number? possibleNumber
  	#number is a new line
  	puts "\n\n"
  	current_line.gsub!("\n", ' ')
  	 current_line.strip!
  	puts current_line.split(' ').drop(1).join(' ')
  	current_line = line
  else
  	current_line << line
  end
end

puts current_line.split(' ').drop(1).join(' ')

Resulting output is as follows:
5 Prepare SELECT DISTINCT "SiteTree_Live"."ClassName", "SiteTree_Live"."LastEdited", "SiteTree_Live"."Created", "SiteTree_Live"."URLSegment", "SiteTree_Live"."Title", "SiteTree_Live"."MenuTitle", "SiteTree_Live"."Content", "SiteTree_Live"."MetaDescription", "SiteTree_Live"."ExtraMeta", "SiteTree_Live"."ShowInMenus", "SiteTree_Live"."ShowInSearch", "SiteTree_Live"."Sort", "SiteTree_Live"."HasBrokenFile", "SiteTree_Live"."HasBrokenLink", "SiteTree_Live"."ReportClass", "SiteTree_Live"."CanViewType", "SiteTree_Live"."CanEditType", "SiteTree_Live"."Version", "SiteTree_Live"."ParentID", "SiteTree_Live"."ID", CASE WHEN "SiteTree_Live"."ClassName" IS NOT NULL THEN "SiteTree_Live"."ClassName" ELSE 'SiteTree' END AS "RecordClassName" FROM "SiteTree_Live" WHERE ("SiteTree_Live"."ID" = ?)  AND (("SiteTree_Live"."ID" != ? OR "SiteTree_Live"."ID" IS NULL)) AND ("SiteTree_Live"."ShowInMenus" = ?)  AND ("SiteTree_Live"."URLSegment" = ?)  AND ("SiteTree_Live"."ParentID" = ?) ORDER BY "SiteTree_Live"."Sort" ASC

This clearly indicates that Prepared statements are not being re-used.

I have what appears at first glance to be a working fix, in that the CMS and website work correctly and prepare statements are not repeated.  I've smokescreened by running a few of the unit tests which are now passing.  It looks though like I will have the test suite overnight to confirm that the change does not break anything.

I will run tests overnight on this branch, https://github.com/gordonbanderson/silverstripe-framework/tree/PREPCACHE, to confirm if anything has been newly broken.  If the tests pass I will rebase that branch and submit a pull request.

framework tests pass

I’m not sure that this is really a “bug”, it’s just something that wasn’t added when the database layer was rebuilt.
I’m not aware of any reason why we couldn’t re-use the statements, though I’m not sure how much benefit there is either - I believe that preparing statements is far a less expensive operation than actually executing them. We’d also be trading memory usage for speed again with this change, something else  to bear in mind. It would be good to see performance benchmarks (XHProf or similar) on a few sites of varying size/complexity :)
@tractorcow any thoughts?

This is an exciting / frustrating topic for me, because originally we DID have statement caching in MySQLiConnector class. It was in fact removed due to segfaulting issues that persisted over a period of about 1 year. You may find that statement caching works fine when running the framework tests in isolation, but fail when running alongside CMS.
See https://github.com/silverstripe/silverstripe-framework/commit/81c0a3499bea4aa4191011616e2cbaf9ed075748?w=1 for the commit where this was removed for the MySQLiConnector class.
What I discovered, much much later, is that any prepared statements would become invalidated after ANY DDL (data definition language) changes on the current connection. This includes truncate, which is considered DDL.
If you look at the work I did in https://github.com/silverstripe/silverstripe-framework/commit/ce3b5a5ace556f65a23348ed6e7bd50dd639f9e0 to resolve this, you'll see that I have updated PDOConnector to flush all cached statements on these queries. It required a little bit of a refactor, since the statement cache must interact with a new query categorising mechanism that was added late in the release cycle.
// Flush if necessary
if($this->isQueryDDL($sql)) {
	$this->flushStatements();
}

Where isQueryDDL included all alter, drop, create, or truncate statements.
If you like, you could probably revert the first commit, and make sure that the logic from the second commit was placed on top, so that MySQLiConnector statements would be managed / flushed the same way as per PDOConnector. :)
We are looking at getting out 3.3.0 in a week or two, so if you want to give it a shot it can probably make it into that release.

Also, thanks to @gordonbanderson for keeping up the good work on the query benchmarking. We appreciate the input (and critique. :P)

You might also have to solve the issue of multiple MySQLStatement instances sharing the same mysqli_stmt object. :) https://github.com/silverstripe/silverstripe-framework/blob/e8d6f15f2883b765bf17bb7027013ebd2a79cf9c/model/connect/MySQLStatement.php
I'm not sure how easy that would be!

@tractorcow:
"What I discovered, much much later, is that any prepared statements would become invalidated after ANY DDL (data definition language) changes on the current connection. This includes truncate, which is considered DDL." << that's a good catch!
How does the segfaulting manifest itself?  In tests or CMS usage?
"You might also have to solve the issue of multiple MySQLStatement instances sharing the same mysqli_stmt object. :)"
By the above do you mean likes of executing a statement likes of 'SELECT * FROM SiteTree_Live where ParentID = ?' (in order to get the children of a Page), iterating the results and running the same query on the children to get the grandchildren?  [i.e. same PreparedStatement, different parameters at the same time].  Currently this would indeed break, my plan was to add a new test for this scenario (and then subsequently fix) once I'd confirmed that the initial caching change didn't cause total mayhem.
Observations from making changes to framework as per https://github.com/gordonbanderson/silverstripe-framework/tree/PREPCACHE are:

CMS tests pass
Framework tests pass
Report tests pass
SiteConfig tests pass
CMS and public site acting as expected (I can make changes on Page content, and see these changes reflected in the publicly visible site)

Next, to test the PDO database option bearing in mind your experiences mentioned above.

How does the segfaulting manifest itself? In tests or CMS usage?

Only in CMS tests, apparently, because of DDL that alters the schema in a few tests specific to CMS.

By the above do you mean likes of executing a statement likes of 'SELECT * FROM SiteTree_Live where ParentID = ?' (in order to get the children of a Page), iterating the results and running the same query on the children to get the grandchildren? [i.e. same PreparedStatement, different parameters at the same time]. Currently this would indeed break, my plan was to add a new test for this scenario (and then subsequently fix) once I'd confirmed that the initial caching change didn't cause total mayhem.

That is the problem but I'm not sure the best way to solve it. You could allow multiple prepared statements and have a "pool" for each, but that'd be hell to maintain.
My solution is just use PDO and not bother with this connector. :)

Maybe your last comment should be included on the installer page ;)

Yip, I can't think of an easy solution to the duplicate query issue.  There was unfortunately a bug I introduced in my haste to start running the tests before I went out last night that prevented caching... eats humble pie.
With a fix for this in place, and double checking queries logged by MySQL are indeed creations of new prepared statements,  I am seeing tests in cms/tests/models fail if I run them all at once, but pass if I run them individually.  This may be related to the DDL issue you mentioned,  I've not investigated.
The test framework/tests/models/MySQLDatabaseTest.php also fails due to a duplicate query in the test.  This is a simpler test case than the 'nested same query' one mentioned earlier.
It does seem that prepared statement caching is a harder problem than it initially seems.  Time to park I think.

If we didn't need to support libmysql then we could solve this problem easily.
Maybe you should make a new MySQLNativeConnector that is optimised to work with MysqlND?
You could use http://php.net/manual/en/mysqli-stmt.get-result.php instead of binding statements to actual result objects, meaning you can re-use them straight away (solves the pooling issue).

@gordonbanderson have a look at the code I changed in https://github.com/silverstripe/silverstripe-framework/commit/e8d6f15f2883b765bf17bb7027013ebd2a79cf9c
The code BEFORE this commit used the below logic which only worked with mysqld, but didn't monopolise prepared statements.
if($result = $lastStatement->get_result()) {
	return new MySQLQuery($this, $result, $lastStatement);
}

Hope that gives you some hope!

@gordonbanderson closed - Noooo. Don't do it! I've been quietly following this for some time (SS Peformance has been a "right pain" for the projects I've been working on recently. It'd be a crying shame to park this now.

On second thoughts, if we can't fix this for MySQL ND then it probably can't be done in core. =(
@phptek  have you tried using the PDOConnector? It should give you optimal performance.


PR: Fix texts out of pattern in the preferences

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Correct some texts that were out of pattern in the preferences tab

Issue(s) Resolved

Fixes #9616
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Steff456

@steff456, please revert all changes you made to our pot files. You don't need to touch those files to solve this problem.

There are some translations that have the texts out of pattern, that's why I changed some pot files.
https://github.com/spyder-ide/spyder/blob/1c795a749b73ab39184fc7f54188502c967526ab/spyder/locale/de/LC_MESSAGES/spyder.po#L3149

I understand that, but translators should update those texts after we provide them with new Pot files (a process that's done by a couple of scripts I ran before a final release). So there's no need for us to touch those files.


Update to service-template-node v0.5.4

Brings in changes to the service template since 0.3.0, which appears to be
the last update incorporated here.

Not for merging yet...
Notes to self:

Restore bunyan-prettystream
Figure out why this breaks tileratorui

JS errors in the Chrome console in tileratorui:

Refused to apply inline style because it violates the following Content Security Policy directive: "style-src *". Either the 'unsafe-inline' keyword, a hash ('sha256-BT3agjNTa2F2qJ52KoiWO+2qHFe2bnfzJeEMHpzpedM='), or a nonce ('nonce-...') is required to enable inline execution.

Refused to execute inline script because it violates the following Content Security Policy directive: "default-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-26QHxfARMTwEJ6/Ygbpv/xt+FvgQ1zXRdu/G0btP8JE='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'script-src' was not explicitly set, so 'default-src' is used as a fallback.

These are not present on master.

The advantages of changing to eslint-config-node-services, as I see them, are (1) improving consistency with other node services maintained in whole or in part by WMF, and (2) making it easier to pull in template updates when we want to do so in the future.  That said, I'm fine sticking with the current ESLint rules, too.  Will update.

OK, this is now ready for review.  The Kartotherian ESLint config is restored and the remaining changes are substantive.

(Side note: I agree that the template update process is clumsy.  To the extent there are common utilities that need updating from time to time, those should probably go into an imported module.)

@nyurik Sorry, was the change you requested to restore the Kartotherian ESLint config, or not to do a template-upgrade commit at all?  There is a bit more work I could do to trim this one down (like restoring the Grunt stuff) but I won't bother if the PR is DOA in any case.
This was really meant as more of a hygiene-type patch and not as high in priority as stuff like https://phabricator.wikimedia.org/T177019 / https://github.com/kartotherian/tilerator/pull/34.

@mdholloway I would like to get the original eslint config for this project, but you may want to exclude files from eslinting that are mostly copy/paste from the template.

Back to  kartotherian eslint config, backed out the Grunt removal, added .eslintignore for files from the template.

Please resubmit to https://github.com/kartotherian/kartotherian


Turn a window into the trouble list

Hi. I've spent minimal time with trouble so far, so apologies if this is somewhere I haven't found yet.
I want a way to turn an existing (empty) buffer into the trouble list. (Ideally I'd love to also have trouble use part of a buffer that is also being used for other things, but that I assume is more complex).
Does at least the former exist? What I see so far just looks like allowing trouble to do the split itself via LspTroubleOpen/Toggle, but I haven't fully read through the Lua API yet.
And thanks!

It's not meant to be used like this. Trouble needs to fully own it's window and buffer to work properly. Even when you open a new buffer inside the Trouble window, we break out the new buffer to another window instead.
Closing this, as this is out of the scope of this project.


Score model dosen't usse model_wrapper

You stated in README that the model_fn's output should be noise for dpm solver. However, the example in example_v2/score_sde_pytorch doesn't use model_wrapper to turn the score into noise. Is it wrong or do I misunderstood something?
I would appreciate it a lot if you could reply to me.

Hi @C0cytus ,
Actually in Yang Song's implementation of score-sde, the model output is noise, not score. He used a wrapper function to convert the model output to score, and the training procedure is actually "predicting noise".
You can check these functions:
https://github.com/LuChengTHU/dpm-solver/blob/449a192092f5f22587c5310cdedd9b0f59f123c2/example_v2/score_sde_pytorch/models/utils.py#L158  This is Yang Song's wrapper function for score.
https://github.com/LuChengTHU/dpm-solver/blob/449a192092f5f22587c5310cdedd9b0f59f123c2/example_v2/score_sde_pytorch/models/utils.py#L129 This is my wrapper function for noise pred model.
So actually we use model_wrapper of noise for score-sde code base.

Thanks for your responding.
Forgive me for not making it clear at first,  actually I want to use  dpm-solver with VESDE. So I still have some questions.

Why does  the get_score_fn just return model output in VESDE's case.
Since get_noise_fn doesn't support VESDE now, so I first get score through  get_score_fn. Then use model_wrapper to turn it into noise. Is it right?


Fix product customization logic in the listing

This PR fixes following issue https://github.com/PrestaShop/PrestaShop/issues/16551

Hi @Hlavtox
Look like you fix two bugs in the same PR.
Could you do it in separate PR please?

@PierreRambaud
Hi Pierre, I screwed it up somehow, now it's separated, sorry :-D
I made a separate PR for the tax issue. 👍 https://github.com/PrestaShop/ps_emailalerts/pull/29

Hello @Hlavtox
Thank you for your contribution.
I found an error when I'm try to pay. You can see the screenshot.

@sarahdib Can you tell me how did you reproduce it? How many products, how many were customized?
One or more customizations on a single product?

@Hlavtox
I follow the step here : https://github.com/PrestaShop/PrestaShop/issues/16551#issue-528763521
2 products customized with customization and 1 product customized without customization.

@sarahdib
Hi Sarah, I extended the code a bit. I just tested it on clean <IP_ADDRESS> and it works as I should. (I don't know how, but in my case, on PHP 7.3, it worked even without the fix. 🤷♂😄)
Just to be sure - I did two different customization field, two differently customized products and one not customized. Try it, should work!!! 🎉

@sarahdib @PierreRambaud bump

@eternoendless It was fixed?

@Hlavtox My bad, something went wrong when I merged dev on master, the dev branch was deleted automatically and with it all open PRs were closed silently. I restored the branch immediately but I didn't realize it would have closed all PRs. Sorry.

Hello @Hlavtox
Do you think you can continue with this PR? or open new one if you don't want to rebase? ;)


SocketException: OS Error: Connection reset by peer, errno = 104, address = <IP_ADDRESS>, port = 3103

I am developing the server side of the command-line application.
The application uses Socket TCP.
I compile the server and run it on my local machine with ubuntu.
Within about an hour, the application terminates with an error:
SocketException: OS Error: Connection reset by peer, errno = 104, address = <IP_ADDRESS>, port = 3103
Now I have no idea what options to investigate to identify the cause of the error.
Searching for me brought up similar errors, but there is no useful information there:
https://github.com/flutter/flutter/issues/48175
https://github.com/flutter/flutter/issues/86486
I am wondering what errno = 104 might mean and if there is a hint in which direction to explore.
Dart SDK version: 2.14.2 (stable) (Wed Sep 15 12:32:06 2021 +0200) on "linux_x64"

after researching this https://github.com/dart-lang/sdk/issues/25518
found an error while using

await ServerSocket.bind('<IP_ADDRESS>', port).then((serverSocket) async {
...
}

after fixing, i don't see any error.
It may take longer to find out if this was the reason


Warning: a promise was rejected with a non-error: [object String]

Hi,
I'm getting the following warning a few seconds after the captcha response comes back (full stack at end of this message): Warning: a promise was rejected with a non-error: [object String]
It doesn't appear to break anything but I'm wondering if/how I can suppress it. I found what looks to be an identical issue captured here: https://github.com/petkaantonov/bluebird/issues/990.
Any help is appreciated.


[YUNIKORN-213] Init source code for yunikorn web-site v2

Outline
Init source code for yunikorn web-site v2,
Preview
https://apacheyunikorn.github.io/

hi @yangwwei @sunilgovind, this is an inital version, https://apacheyunikorn.github.io/

hi @lamberken
I am looking at https://github.com/BigDataArtisans/incubator-yunikorn-site/tree/yk-213, which might be easier. I don't see a README for me to build, and test. WEB-README doesn't seem to. work. Could you please add a README file for the project?
Another thing is, please add Apache License header for all source code files. That's probably the first comment I have : ).

hi @lamberken
I am looking at https://github.com/BigDataArtisans/incubator-yunikorn-site/tree/yk-213, which might be easier. I don't see a README for me to build, and test. WEB-README doesn't seem to. work. Could you please add a README file for the project?
Another thing is, please add Apache License header for all source code files. That's probably the first comment I have : ).

Done, thanks

hi @wilfred-s, thanks for your review

The community, roadmap and download pages are showing up as versioned pages like the docs in this setup which they should not be.

Right, from docusaurus document, it support create separated community, roadmap, etc. pages.
IMO, it's not a problem to keep them in docs.
https://v2.docusaurus.io/docs/creating-pages

The menu structure seems to be driven of the starting letter of the document.

As I mentioned, document names are prefixed with letters for categorization. If add a new doc, need update sidebars.js also.

Last point what I do not see yet is the build and publish instructions

After run yarn build, the web site will be generated at build folder.

Right, from docusaurus document, it support create separated community, roadmap, etc. pages.
IMO, it's not a problem to keep them in docs.
https://v2.docusaurus.io/docs/creating-pages

The location we store them is not really a problem. The problem is the fact that they are marked as versioned. We cannot mark these files as versioned. We need to do create static files for all the files that are not part of the normal doc revision cycle.
The community, roadmap and download pages are not versioned and there should only ever be one version on the site available. When we create a new revision of the docs we need to exclude them too.

As I mentioned, document names are prefixed with letters for categorization. If add a new doc, need update sidebars.js also.

This needs to be explained and documented somewhere. We should not require a contributor to figure this all out. What we at least need in the documentation is:

how to name a document
what tags to add inside the document
which config to update

Last point what I do not see yet is the build and publish instructions

After run yarn build, the web site will be generated at build folder.

The question then becomes: does it have all data needed and is that build directory clean enough to commit to the asf-site branch? How do we commit that: i.e. do we recursively copy just the build dir as the new content of the asf-site branch?
We can create a staging setup in the repository which get deployed to an apache staging web server to check if it all works.

hi @wilfred-s,

The community, roadmap and download pages are not versioned

I have different opinions on this.

how to name a document

The new site is based on https://v2.docusaurus.io , so developers can read docusaurus directly

The question then becomes: does it have all data needed and is

You're right, it's ok to copy just the build dir as the new content of the asf-site branch.

hi @wilfred-s, had updated the pr according to your comment, review again, thanks

I have merged these updates to site-v2 branch.
I played a bit and I have fixed the problem @wilfred-s mentioned, for pages like downloads, roadmap, we do not need a version. I have fixed that on the branch.  That leverages the blog plugin, so they are still built via md files, but without versions.
I am doing some more optimizations, but mostly I think it is good. I plan to try to deploy a new version shortly to ASF based on site-v2 branch.

Merged to site-v2 branch. Let's use this branch for some temp time before wiping out the master.
Thanks a lot @lamberken !

It's ok, welcome. I know blog plugin. I think it's ok to let the download, roadmap to link to next version.


spaghetti should handle native cg.Point/Chain objects

Currently, input for instantiating a network.Network and network.PointPattern can be accomplished with either a .shp file or a geopandas.GeoDataFrame.  However, passing in native pysal.cg objects is not an option. As spaghetti is a member of the pysal federation, this functionality should be available.

[x] network.Network accepts cg.Chain objects for instantiation
[x] network.PointPattern accepts cg.Point objects for instantiation

Tests

[x] tests/test_network.py -- test_network_from_cg(self)

[x] cg test against known
[x] shp against cg

[x] tests/test_network_api.py -- test_network_from_cg(self)

[x] cg test against known
[x] shp against cg

Docs

[x] re-run docs

#217


Remove hard-coding of BCH polynomial

The hard-coded polynomial was taken from bchlib's example. This limits the supported range of fuzziness thresholds and should rather be chosen dynamically based on the FCS parameters.

Polynomial is made user-definable in 1621ea6f0cb081a831d858232d21f010cc02a84f

Hi,
is this argument mean n in BCH(n,k,t)? or what does it mean?
Also, why I can't change the polynomial arg.? , an error arise while changing this arg,
"can't change this argument,bad parameter?

@lolib11 The argument specifies which polynomial is used for the BCH code.
As you can see in the code, it is directly passed to bchlib. So I suggest you go there for more information about what are valid polynomials and how to select them.
https://github.com/jkent/python-bchlib


Keyboard shortcuts behave unexpectedly, and differently depending on OS and browser

Symptom: Keyboard shortcuts behave unexpectedly, and moreover differently depending on OS and browser
For example,
Mac OS X, FireFox and Chrome: ctrl-x cuts a step on a canvas, cmd-x cuts text on a step dialog.
Mac OS X, Safari: ctrl-x cuts a step on a canvas, cmd-x cuts a step on a canvas and cuts text on a step dialog.
Windows 7, Chrome and IE11: ctrl-x cuts a step on a canvas.
How to reproduce

File > New > Transformation
Activate keyboard shortcuts by opening "Edit" menu
Draw "Modified Java Script Value" step to the canvas and open its dialog
Select text and try ctrl-x (or cmd-x)

Workaround: not found yet.

Resolved by c0fa26f70fb9b95d65e92ae33a0db9eb8a3a3ac4.
Here is the test results.


Can't count devices (foundDevices.getCount() doesn't work

Please help me, I do scanning for Bluetooth device with my esp32, as seen in the picture there are 2 devices founded but why the "device found" count still 0? Thanks in advance.

I'm getting the same problem.

Down grade your board to version 1.0.4, it works for me

You cant use AdvertisedDeviceCallbacks and getCount at the same time.
Either dont use getCount, or dont use the callback.


Generic segmentation

Hi @MaureenZOU ,
I have quick question about where is in the code for the arrow from Text Encoder to Semantic Output when inference.

THe arrow from text encoder to semantic output simply means the dot product between the text embeddings and semantic outputs decoded from our X-Decoder. Please refer to this function: https://github.com/microsoft/X-Decoder/blob/8f245b052a38d8d5410888d1bb52391050b4f726/xdecoder/language/vlpencoder.py#L174


Create new BB: Hero Section with Side Links

This is a Building Block for our upcoming News/Magazine Kit. For anyone who wants to contribute some building blocks to the site, feel free to assign this to yourself to let us know you're taking this one on!
Description/Interaction: A hero section with a featured article on one side and article links on the other.
Example:

@canterberrie Sounds kinda easy .... will wait .... for others to look into this ....
If no one will take this up .... I will go for it!

@canterberrie .... Looked around and seems like this is already added by @abdullahsalem
http://foundation.zurb.com/building-blocks/blocks/featured-blog-posts-panel-iframe.html
=> Jump to Featured Posts (Grid)

@IamManchanda You're right, must have missed it! Thanks for pointing this out. Closing this PR now.

It wouldn't hurt to add this one separately and re-arrange the components. @abdullahsalem can you add this?

Oh sorry -  i see that is below. Would be good to have them as two separate ones still. Thoughts?

Would be good to have them as two separate ones still. Thoughts?

Yes @rafibomb

@rafibomb I guess that it could be within the same building-block.
@canterberrie Is it OK to reassign it to me, if you have not yet started?

@abdullahsalem I've already started on a BB for this but feel free to create a variation! Wouldn't hurt to have it in different formats. Mine will look something like this:

(from usatoday.com)

@abdullahsalem There are also some other BBs that we need help building, if you feel like taking on some other ones.

It's OK @canterberrie! enjoy coding yours, I am already working on another BB, however I will take a look at the BBs that need help asap.